02 CN37532EN10GLA0 IMS NSN Doc PDF

IMS NSN Realization
IMS NSN Realization
Contents
1 Network Entities and their Realization 3
2 Feature overview in the IMS of NSN 7
2.1 Network or Carrier related Features: 8
2.2 End-user related Features: 14
3 SW Clients and Terminals 19
4 Operation and Maintenance Concept 23
4.1 OAM Interfaces 24
4.2 Operation tasks 26
4.3 Configuration Management 30
4.4 Maintenance and Alarming with the Fault Management 37
4.5 Operating Manuals 42
5 Exercise 45
6 Solution 51
CN37532EN10GLA0
Copyright ©2014 Nokia Solutions and Networks. All rights reserved.
1
IMS NSN Realization
CN37532EN10GLA0
2 Copyright ©2014 Nokia Solutions and Networks. All rights reserved.
IMS NSN Realization
1 Network Entities and their Realization
CN37532EN10GLA0
3
IMS NSN Realization
Overview Network Topology and entity realization

On the opposite page the well known topology picture from the chapter 1 “IMS
fundamentals” is shown. But here the NSN type product-names are shown: e.g. the
S-CSCF is realized utilizing the CFX-5000. Network entities in a solid darker circle
are going to be discussed in this course, network entities in dashed line circles a
subject of other courses.
Symbol 3GPP NSN Platform Symbol 3GPP NSN Platform

Name Product Name Product
Name Name
P-CSCF CFX-5000 ATCA MGCF hiE9200 NSN prop
I-CSCF (Core ACPI4-B or ACPI5-A or
S-CSCF Element hiQ8000 Sun Netra T4270
BCF CSCF or or
BGCF switch) MSS ATCA
SUN Netra T5220
CMS- ATCA hiG1800 Genband

HSS-FE 8200 ACPI4-B or ACPI5-A MGW or NSN prop
(Core hiG1100
element or or
Mobility OpenBGW ATCA
Server) SUN Netra T5220
Subscriber HP Proliant BL460 VAS hiQ4200 Sun Netra X4720

Repository One-NDS or or
Sun Netra X4270 NVS ATCA
PCS- ATCA ACPI4-B

5000
PCRF (Policy or
Control
Server) SUN Netra T5220
BGF ACME NET

NET 4250 or 4500
or or
OpenBGW ATCA
MRF Mereon MS 6000
Fig. 1 Overview of IMS solution component
CN37532EN10GLA0
IMS NSN Realization
One-NDS
IMS Other IMS
BGF
ACME
Fixed, DSL
Core
MGW
hiG 1800
CMS-8200
HSS PSTN
CFX -5000
WLAN/WIMAX P-CSCF
Core SBC
incl. ATCF
(BCF)
CFX -5000 PLMN
S-CSCF hiQ 8000
incl. BGCF/
I-CSCF
MGCF
SBC (BGF)
ACME
PCS-5000
PCRF
GPRS/UMTS/
LTE Application
Core Control Server
OpenBGW
SBC (BGF)
Bearer Mereon
MRF
Fig. 2 IMS Realization
CFX5000 Cx CFX5000 CFX5000

Cx
S-CSCF
P-CSCF I-CSCF BGCF
[BCF] MCF
Gm Mw Mw Mw Mw M…
Rx
CFX5000 Cx CFX5000 Cx CFX5000

P-CSCF
S-CSCF S-CSCF
P-CSCF I-CSCF BGCF I-CSCF BGCF
[BCF] MCF
Gm Mw
Gm Mw Mw M… Mw M…
SPDF
(BCF)
Gq+ Rx
Iq
ACME BG ACME SD PCS-5000

Rx
OpenBGW PCS-5000
Iq Gx (PCRF)
Gm BCF Gm
BGF
BGF
Fig. 3 Collocation variants
CN37532EN10GLA0
5
IMS NSN Realization
CN37532EN10GLA0
IMS NSN Realization
2 Feature overview in the IMS of NSN
CN37532EN10GLA0
7
IMS NSN Realization
2.1 Network or Carrier related Features:

 Support of SLF
Subscriber Location Function is supported. Whenever the I-CSCF or the S-CSCF
need to find the address of the HSS that holds the subscriber data for a given user
identity, they query the SLF via the DX interface. The Dh interface between
application servers and the SLF are supported as well.
 SIP signaling Compression
Because of SIP signaling is a text oriented signaling, it is very bandwidth
consuming. Therefore a static (RFC3320/3486) and dynamic (RFC 3321) SIP
signaling compression between the SIP clients and the P-CSCF is provided.
 Secure IMS operator interworking
The Mw, ISC, Gi, etc. interfaces can be secured against eavesdropping etc. with
IPsec gateways.
 Transit CSCFs
CSCF can be used as a transit CSCF to route sessions originating from CS/PSTN
to a further IMS or a CS/PSTN network.
 QoS and charging rules
The dynamic end to end QoS handling is used to provide real-time and non real-
time services according to the momentary requirements of the customer.
Additionally it offers the possibility to charge the granted services accordingly.
 IPv4 and IPv6 interworking
IPv6 provides a sufficient range of IP addresses to be assigned individually to
each terminal. Nevertheless IPv4 is still predominant. These are the reasons why
both IPv4 and IPv6 are supported.
CN37532EN10GLA0
IMS NSN Realization
AS HSS
SLF
CSCF
HSS
P-CSCF
Invite
Regi
Invite
Register
ster
SIP
SIP Compression
Secure Operator Interworking

IMS IMS
Operator Operator
SIEMENS SIEMENS SIEMENS SIEMENS
CS Network
CS PSTN
Transit IMS IMS
P-CSCF
PCRF PCS-5000
QoS dependend
charging GGSN
IPv4 IPv6
IPvX
SBC
SBC
IPv6-v4 interworking
Fig. 4 Key Network features Network 1
CN37532EN10GLA0
9
IMS NSN Realization
 Security
In IMS, different user authentications like “authentication and Key agreement” or
“HTTP digest” are supported. The system is protected against attacks from
malicious subscribers, against unauthorized Operation and Maintenance access.
 Emergency Calls
The IMS offers different possibilities for emergency handling depending on the
access technology. So emergency calls can be rejected totally for mobile access
users, because no location information is contained in the setup information.
 Lawful interception
Legal interception is supported and can be customized depending on customer
requests.
 DRA Diameter Routing Agent The DRA consists of 2 functions:
the Edge Agent, which protects the operator’s NNI (Network-Network Interface) in
case of roaming subscribers and
the Diameter Load Balancer, which balances the Diameter traffic, e.g. between
different HSS-FEs according to their performance capabilities. It also simplifies the
network architecture (not requiring a fully meshed network) thus improving the
scalability and manageability of the network.
 Mr Interface support
From IMS6.0 on the Mr interface in the S-CSCF towards the Media Resource
Function is supported.
CN37532EN10GLA0
IMS NSN Realization
HTTP Digest
Authentication
and IMS
Key agreement
Emergency Calls IMS
Lawfull Interception SIEMENS SIEMENS

SIEMENS SIEMENS
IMS
DRA
AS
HSS-FE
CSCF
HSS-FE
Mr I/F
S-CSCF
CN37532EN10GLA0
11
IMS NSN Realization
 Number Portability
Number portability is supported for SIP URIs and Tel URIs containing an E164
number
 Charging
The IMS supports offline and online charging as standardized in the 3GPP
TS32.240
 Zb interface for Network Domain security
The Zb Interface adds IPSec security to all signaling interfaces within an operators
network (not between the networks of different operators; this interface is called
Za): Mw, Cx, Sh, Mi, Mj, Mg, ISC, and OAM are than optional secured with IP Sec.
 TLS support in IMS significantly improves the access security. SIP signaling is
protected by a TLS tunnel, which supports confidentially and integrity protection.
This results in a high availability of the services due to increased stability and
robustness against attacks. It enables the operator to offer new services and
attract new customers that require higher security.
 IMS Roaming Control
With the support of roaming policies according 3GPP, the operator gets the same
level of policy control as in the CS world. The operator can specify per-user
whether roaming is allowed or not and if roaming is allowed, to which roaming
partners.
CN37532EN10GLA0
IMS NSN Realization
DNS/
ENUM
SIP: URI / Tel URI w/
E164 numbering scheme
Number Portability IMS
Charging@vantage
Billing System
Charging CDR
Zb
Zb Za Zb Zb
Zb Zb
Zb
Zb
Option. Zb according to TS33.210

Mandat. Za according to TS33.210
TLS PCSCF
Visited Network (superoperator.com) Home Network (niceoperator.net)

niceoperator.net allowed
REGISTER: forbidden superoperator.com allowed
badoperator.net
niceoperator.net
badoperator.net forbidden
niceuser@niceoperator.net REGISTER:
niceoperator.net
P-CSCF I-CSCF S-CSCF
REGISTER:
badoperator.net
baduser@badoperator.net
CN37532EN10GLA0
13
IMS NSN Realization
2.2 End-user related Features:

 Voice over IP support
Beside other value added services VoIP is one of the most required features
requested by the end-customer. IMS supports for this feature Adaptive Multirate
Codecs, G.711 Codecs and G.729 Codecs.
 Video Telephony
Beside the simple VoIP sessions Video Telephony is supported for end users with
the corresponding devices and access possibilities (e.g. via DSL).
 Combinational Services
Combinational Services are supported by the IMS. Combinational services mean
the change of the services during an ongoing session. So for example a subscriber
has an ongoing VoIP session and wants to change to Video telephony during the
session.
 Announcements
The IMS supports Signaling announcements. Depending on the SIP responses
(RFC3261), which are returned to the initiating SIP device, the device may display
responses or play messages.
CN37532EN10GLA0
IMS NSN Realization
Access Access
Voice over IP
Access Access
Video Telephony
CS Access CS Access
PS Access PS Access
Combinational Services
e.g. address
incomplewte
SIP:4XX
Access Access
Signaling announcements
Fig. 8 End User related features 1
CN37532EN10GLA0
15
IMS NSN Realization
 Access Support
IMS supports different access types such as access from 2G/3G/4G networks via
GGSN, WLAN access via the Packet data Gateway, fixed network access and
LTE access.
 SRVCC and eSRVCC
The Single Radio Voice Call Continuity realizes the transition of a VoIP LTE call to
the CS domain. And with the enhanced SRVCC (3GPP Rel. 10) the performance
of the transition is improved.
 Supplementary Services
Supplementary services similar the services specified for ISDN or analog
subscribers are supported:
CLIP, CLIR, Call Hold, different Call Forwarding, Call Barring, Closed user group,
Call Waiting, Parallel Ringing etc.
 Multiple User identities
Each IMS user may have more than one private id using different dedicated public
ids.
E.g. one public id for the family, one for business, one for additional honorary
posts etc. Each public id different service profiles can be assigned.
 Calling line presentation and Display name
The supplementary service "calling line presentation" (CLIP) and "calling line
presentation restrictions" (CLIR) are provided. Furthermore the "Display Name"
feature as requested in the "Packet Cable" Specifications. To realize the Clip
feature one or more IMPUs are kept in the P-CSCF, stored there during
registration. In case of session setup one IMPU is selected (preferred like
requested by user or the default IMPU) and assigned to the private header
"p_asserted_id" in the Invite message. So the calling line (IMPU) can be displayed
in the called user agent's display screen. The "Display Name" works quite similar:
The "Display Name" is set up in the HSS and provided during registration to the P-
CSCF. In the Invite the display name is inserted into the "p_asserted_id"
additionally to the IMPU (see RFC3325).
CN37532EN10GLA0
IMS NSN Realization
2G/2.5G/3G
WLAN
fixed
Any Access
IMS
LTE AN
Single Radio Voice

LTE Call Continuity
handset 2G/3G CS AN
CS PLMN
MSC (MSS)
CLIP CLIP
CLIR CLIR
CW CW
CH CH
CF CF
Access Access
CB CB
CUG CUG
Supplementary
CW CW
Services
... ...
Fig. 9 End User related Features 2
Service 1
Private id 1
access1
Public id 1 Service 2
Private id 2 access2
Public id 2
Private id 1
access3 Public id 3
Private id 3 Private id 2
subscription
Multiple user ids
Private id 3
During Registration:
„Display Name“
and
„IMPU“ PSTN
HSS
P-CSCF
access
0498972241462
access Alois Himmserl
S-CSCF
During Setup:
P_asserted_id=
„Calling Line (IMPU)“
And
„Display Name“
Fig. 10 End User Features 3
CN37532EN10GLA0
17
IMS NSN Realization
CN37532EN10GLA0
IMS NSN Realization
3 SW Clients and Terminals
CN37532EN10GLA0
19
IMS NSN Realization
The following clients and/or terminals were used during System Verification. Other
clients not listed below (e.g. other SIP Phones or other mobile phones) can also be
used provided that they are able to interact with the IMS.
Clients are considered as a software component that are or can be installed into
terminal(s). Some terminals have native clients, and some clients need to be installed
into terminals separately.
 Eyebeam V1.11 as residential softclient (voice)

 Optipoint 410, V7 R1.6.0
 Nokia S60 + Cicero phone, V2.41 (for VCC)
 Nokia N95 RM-159, V30.0.015 (used for GPRS Test)
 Nokia Communication Suite V2.5.6.2 & V3.1.1.5152 (used for TLS)
 PhonerLite V1.44, 1.49 (for TLS)
 Kapanga V 1.0 Build 2180 (for Transcoding)
CN37532EN10GLA0
IMS NSN Realization
Siemens optiPoint 410
Mobile Personal Assistant

Com Manager Mobile
Nokia N97 Mini

•Nokia Siemens Networks
Communication Suite (NCS)
Nokia E55
Kapanga
Version 1.0 Build 2180
Nokia E75
PhonerLite 1.44, 1.49
Arris TM602A eMTA

for FMC Cable Tilgin 1311 for
FMC TISPAN
Asterisk for
FMC IP-PBX
Cisco CallManager
5.1 for FMC IP-PBX or
Express 4.3 for FMC IP-PBX
Fig. 11 Software Clients and Terminals
CN37532EN10GLA0
21
IMS NSN Realization
CN37532EN10GLA0
IMS NSN Realization
4 Operation and Maintenance Concept
CN37532EN10GLA0
23
IMS NSN Realization
4.1 OAM Interfaces

The recommended network element management system for managing the IMS NEs
is the NetAct. It is an already established and deployed NEM system. Beside this
independent NEM system also local administration interfaces directly at the network
element are present.
NetAct allows to enter and to modify in a comfortable way the daily configurations
parameter. If offers also a performance management, fault management and license
management.
Admin interfaces:
 NetAct Configuration Management, Fault Management, Performance
Management (via NE3S Nokia Enhanced SNMP security suite, a proprietary NSN
protocol); System Monitor (used for OneNDS NEs, via RMTP Reliable Message
Transfer Protocol, a proprietary NSN protocol); LM und SecM
 local OAM webgui:9881(Mgmt of the Application, e. g. IP Mgmt, Trace Mgmt)
 local TSP webgui:9099 (Mgmt at TSP Level), e. g. Conf Mgmt for TSP, System
Mgmt for TSP)
 local LEMAF webgui:9880/lemaf (local element management)
 local LUMAF webgui:9880 (local user management)
 local OAM Agent UI (NE3S)
CN37532EN10GLA0
IMS NSN Realization
OAM Management Access
User:
WebBrowser
NetAct:
OAM
DataServer
webgui:9881 ApplicationServer TSP
webgui:9099
CSCF / HSS-FE
LUMAF
webgui:9880 ssh / sftp
LEMAF OAM Agent UI putty/ psftp
webgui:9880/lemaf NE3S
Fig. 12 Interfaces Overview
User Workstation User Workstation
Web Browser Web Browser
http/https
http/https
Application Server (NetAct Core NAC)

Fault Management
Performance Mgmgt
System Monitor FM PM SysM CM LM SecM
Configuration Mgmt
License Mgmt
Security Mgmt
NE3S
Web Server NE3S / WS
System Monitor via RMTP Manager
(Reliable Msg Transfer
Protocol) to
OneNDS components only
NE3S over SNMP/XML, SOAP/HTTP, FTP/XML
NE NE
CMX-5000 CMS-8200
Application NE3S WS Agent Web Server (GUI) Application NE3S WS Agent Web Server (GUI)
ATCA / TSP platform ATCA / TSP platform
NE3S
Nokia Enhanced SNMP
Solution Suite LEMAF Local Element Mgmt LEMAF Local Element Mgmt
Application Function Application Function
Fig. 13 O&M Interfaces
CN37532EN10GLA0
25
IMS NSN Realization
4.2 Operation tasks

4.2.1 General
CFX-5000 (P-CSCF, I-CSCF, S-CSCF, BCF, BGCF, I-SBC) and CMS-8200 (HSS-
FE) are the core network elements of IP Multimedia Subsystem. This course
document describes the OAM Configuration Parameters, which are accessible via
the NetAct Configuration Management and directly via LEMAF Interface for daily
operation, administration and maintenance. During the installation process some
more parameters are specified (not described here). Depending on the access rights
assigned to the LEMAF-UID, not all of these parameters may be accessible or
modifiable. Typically parameters of class E can be administered; parameters of class
D are normally accessible by NSN service personnel via a special LEMAF-UID.
Please refer to the Operating Manual for further information on user roles and access
rights.
For CFX-5000 the following configuration data can be administered:
 CSCF data itself like: System Parameter, PDF Parameter, Performance
Parameter, Diagnostic Parameter, Timer Parameter, Operator Service Parameter,
Offline and Online Charging Parameter, Overload Parameter etc.
 protocol handler data common for IMS like: DNS, Radius, Sh, Rx interface
parameters etc
 platform data for the TSP platform the CSCF is based on
For CMS-8200 the following configuration data can be administered:

 HSS-FE data itself like: Mobility server database, system parameter, overload
parameter, request parameter, interface parameter, MAP parameter etc.
 protocol handler data common for IMS like: DNS, Radius, Sh, Cx interface
parameters etc
 platform data for the TSP platform the HSS-FE is based on
Other data like site specific or customer specific data can be changed or setup during
the installation by utilizing TPD sheets.
TIP
"Changeable Configuration Data: are discussed in this course; data changeable via
TPD are discussed in the IMS installation and commissioning course.
CN37532EN10GLA0
IMS NSN Realization
Administrable Data in the CFX-5000 and CMS-8200
Configuration classes:
• Class A development data

• Class B project specific data1)
• Class C site – specific data1)
• Class D Daily operation data2)
• Class E Daily operation data3)
1) Setup during Installation via TPD
2) Typically changed by Service Personal
3) Typically changed by customer
Fig. 14 Changeable Configuration data 1
CFX-5000 configuration data:

• CSCF data itself
– System Parameter
– PDF Parameter
– Performance Parameter
– Diagnostic Parameter
– Timer Parameter
– Operator Service Parameter
– Offline and Online Charging Parameter
– Overload Parameter
• Servlet Administration
• protocol handler data
– DNS parameter
– Radius parameter
– Sh-, Gq- interface parameter
• platform data for the TSP platform
CMS-8200 configuration data

• HSS data itself configuration data:
– database
– system parameter
– overload parameter
– request parameter
– Interface parameter
– MAP parameter etc.
• protocol handler data
– DNS parameter
– Radius parameter
– Sh-, Gq- interface parameter
• platform data for the TSP platform
Fig. 15 Changeable Configuration data 2
CN37532EN10GLA0
27
IMS NSN Realization
4.2.2 Technical Project Data (TPD)

Procedure
The software is produced in coordination with the customer. The procedure is as
follows (extremely simplified):
1. The customer and NSN come together to discuss the version and the kind of
product
2. NSN will use an order sheet for producing a TPD-sheet
3. Together with the customer the project data were defined (TPD=Technical
Project Data). These data were sent to the media-production.
4. Here the data were produced and delivered to the customer for installation.
CN37532EN10GLA0
IMS NSN Realization
1 4
Fig. 16 TPD production, simplified
Example TPD
On the opposite page, an example of a TPD Excel sheet is shown. The TPD sheet
handling is no point of further discussion in this course.
Fig. 17 Example of a TPD sheet
CN37532EN10GLA0
29
IMS NSN Realization
4.3 Configuration Management

4.3.1 Configuration Management with NetAct
Influencing the configuration parameters is the main task of the operating and
maintenance personnel. As the NetAct is the deployed NMS for all IMS components
the focus is on the NetAct Configuration Management. The NetAct itself is explained
in the course FN9074 - NetAct 7 Management functions for IMS. The parameter
classes which can be changed via NetAct depend on the licenses present in the
current NetAct deployment.
The NetAct configurator is never working directly on the database of the Network
Element.
1. An "actual configuration“ has to be uploaded from the NE to the NetAct. This task
is performed via the application CM Operations Manager.
2. A new plan is created which is a copy of the actual configuration, also by the
application CM Operations Manager.
3. With the application CM Editor this plan is modified and extended.
4. Again with the application CM Operations Manager, the plan is downloaded and
activated towards the NE.
NetAct 7
CM Operations Manager CM Editor
3
2 work on the
actual planned new plan
configuration configuration (modify/enter
create a new plan
config params)
1 4
upload actual provision and activate
configuration planned configuration
CFX-5000 CMS-8200
Fig. 18 Components of the NetAct
CN37532EN10GLA0
IMS NSN Realization
Fig. 19 Upload actual configuration
Fig. 20 Upload finished
CN37532EN10GLA0
31
IMS NSN Realization
Fig. 21 Creation of a new plan
Fig. 22Configuration modification within the plan
CN37532EN10GLA0
IMS NSN Realization
Fig. 23 Provisioning and activation of the plan
Fig. 24 New configuration is present now in the NE
CN37532EN10GLA0
33
IMS NSN Realization
4.3.2 Configuration Management with LEMAF

LEMAF is the web-based Graphical User Interface (GUI) which is only to be used for
the local operation of @vantage-platform-based network elements (e. g. CSCF,
HSS….). It can be accessed by a web browser.
The following administrative tasks can be performed via the LEMAF GUI:
 displaying alarms/events
 displaying and monitoring component counters (performance objects)
 displaying/editing component configuration data
 administrating SS7
 starting/stopping platform processes and traces
 disaster recovery
 providing shell access to the operating system
CN37532EN10GLA0
IMS NSN Realization
Configuration
of CFX-5000
Web IF
Network Element LEMAF

e. g. CFX-5000 (TM, CM, PM, TSPM, FM, DR)
TM Trace Management
CM Configuration Management
PM Performance Monitoring
TSPM TSP Management
FM Fault Management
DR Disaster Recovery
TSP7000
Fig. 25 Architecture
The configuration data items of the system configuration are manifold. A classification
of the configuration data has been introduced to reduce the data that must be
administrated online. The classification is determined by the life cycle of the
configuration data (see the explanation in the TPD subchapter).
Tree structure
The Administration Tasks are presented in a tree structure. Below the Admin Tasks
the selection of the parts/parameters of that Admin Task is possible.
Displaying function
The result of a Display/Modify function for the selected configuration data in the
navigation tree can be displayed. Configuration data of table type are displayed in
tabular format. Configuration data of scalar type are displayed in a text field (for data
of type string, integer, long) or in a check box (for data of Boolean type).
CN37532EN10GLA0
35
IMS NSN Realization
Tree structure
Fig. 26 Tree structure
right mouseclick
or doubleclick the element
Fig. 27 Display function
CN37532EN10GLA0
IMS NSN Realization
4.4 Maintenance and Alarming with the Fault

Management
The Fault Management is used to ensure that any deviation from the expected
behavior of the node element is immediately detected and repaired as soon as
possible.
The Fault Management is the application for monitoring and processing
events/alarms, this application is available in NetAct and LEMAF likewise. A list of
events with the event states open, locked and cleared is displayed, i.e. the so-called
non-closed events, is displayed in the event table. The number of displayed events
can be reduced by using (pre)defined event filters.
4.4.1 Fault Management with NetAct

The Fault Management in NetAct is done by several visible and internal applications.
The visible and selectable application is the NetAct Monitor. The details of the
handling is explained in the course FN9074 - NetAct 7 Management functions for IMS
9.x.
Higher Level Systems
SNMP
NetAct 7 Monitor
Monitioring Desctop
Common Desctop
Alarm Event Correlation

Managed Object
Framework
Alarm Event Collection
SNMP traps via NE3S
CFX-5000 CMS-8200
Fig. 28 Fault Management with NetAct
CN37532EN10GLA0
37
IMS NSN Realization
With the Object Explorer the view to the configured NEs is opened.
NetAct Monitor  Tools  Managed Objects  Object Explorer
When this Object Explorer window is selected and opened once, it will be used as
start view when the Monitor is started the next time.
Fig. 29 Object Explorer
It is possible to display all existing Alarms: NetAct Monitor  Tools  Monitoring

Desktop  Alarm List
Fig. 30 Alarm List
CN37532EN10GLA0
IMS NSN Realization
The Result is an actual list of all alarms from the Managed Objects administered by
the NetAct. This result list can be sorted based on Severity/ Alarm Time/
ObjectClass/Distinguished Name…
A finer way is by defining a filter just for one object and applying that filter. (See Fault
Management chapter of the course FN9074).
Fig. 31 Complete Alarm List, sorted by Object Class CSCF
Fig. 32 Details of one Alarm
CN37532EN10GLA0
39
IMS NSN Realization
4.4.2 Fault Management with LEMAF

Via the LEMAF WebGUI the alarms of the corresponding Network Element can be
displayed directly. Also here the selection of the output is possible via Filters. The
Fault Management via LEMAF shall be used in exceptions only, because it does not
offer the same comfort and feature set as it is present via NetAct.
CN37532EN10GLA0
IMS NSN Realization
Fig. 33 Fault Management via LEMAF
CN37532EN10GLA0
41
IMS NSN Realization
4.5 Operating Manuals

The Operating Manuals are delivered with the products CFX-5000 and CMS-8200. It
comprises a set of Manuals. On this page the Manuals will briefly be introduced.
Safety Instructions
This document, CFX-5000 Safety Instructions
provides general information for working with telecommunication equipment from
Nokia Solutions and Networks. The information is aimed at ensuring personnel safety
and use of the correct procedures for handling technical equipment.
Operating and maintenance personnel must be informed of the safety instructions. It
is essential for the operation of the telecommunication equipment to follow these
instructions.
The safety information is repeated at relevant points in the manuals, and
complemented with handling instructions for dangerous operations.
Technical Description
The Technical description is a verbal description of IMS. It encompasses the benefits
of the system as well as the architecture, the system features, platform description
etc. It is an essential base knowledge of the current IMS solution.Operating Manual
The Operating Manual deals with the configuration and performance management of
the two network nodes: It is available for the CFX-5000 and for the CMS-8200.
Troubleshooting
This Manual describes procedures for health check, IMS RapidStat for quick
diagnosis and other emergency actions.
OAM Configuration Parameters of CFX-5000 (and CMS-8200)

This manual is used as reference in the Operating manual for the CFX-5000 and
CMS-8200 parameter description. It gives you a description of the administrable
class D and class E parameters.
You find there a short parameter description, the class, the parameter type (e.g.
integer), the range of the parameter values etc.
CN37532EN10GLA0
IMS NSN Realization
Fig. 34 IMS Operation and Maintenance documentation
CN37532EN10GLA0
43
IMS NSN Realization
CN37532EN10GLA0
IMS NSN Realization
5 Exercise
CN37532EN10GLA0
45
IMS NSN Realization
Exercise 1
Title: Network Entities
Objectives: The participant can allocate a functionality to a product
Pre-requisite: none
Task
Please answer the following questions
Query
Which one of the following statements is correct or incorrect?
The HSS is realized by the CFX-5000 Yes No
The HSS is realized by the CMS-8200 Yes No
The P-CSCF is realized by the CFX-5000 Yes No
The P-CSCF is realized by the CMS-8200 Yes No
The SPDF can be part of the CFX-5000 Yes No
The SPDF can be part of the CMS-8200 Yes No
The SPDF can be part of the HiQ 8000 Yes No
The SPDF can be an own product PCS- Yes No

5000
The MCF is part of the CFX-5000 Yes No
The MCF is part of the CMS-8200 Yes No

The MCF is an own product HiM-5700 Yes No
CN37532EN10GLA0
IMS NSN Realization
Exercise 2
Title: Features in IMS
Objectives: The participants can describe the features on a low level
Pre-requisite: none
Task
Query
SIP signaling compression is used to Yes No
convert SIP into Diameter Signaling
reduce the bandwidth consumption
IMS supports IPv4 and IPv6 Yes No
Among others the IMS supports Yes No

authentication and key agreement as a
security mechanism
IMS supports just offline charging, Yes No

onlinecharging will be introduced in later
versions
Once a user is registered and Yes No

authenticated for a certain service, there is
no need for further authentication in case
additional services are used.
To use supplementary services like CLIP Yes No

or CLIR, the user must connect via ISDN
over ATM.
CN37532EN10GLA0
47
IMS NSN Realization
Exercise 3
Title: OAM
Objectives: The participant knows the different ways to connect to the

network elements
Pre-requisite: Connection to the HSS possible
Task
Query
The HSS and the CSCF are operated Yes No

using the NetAct as a network element
manager
The NSN service personnel has by using Yes No

the “comservice” login at the NetAct, the
same rights and duties as present with the
LEMAF IF
Which one of the following configuration A
classes a customer operator typically
changes? B
C
D
E
You want to display an IMS subscriber,

which tools or interface do you use to
display it?
CN37532EN10GLA0
IMS NSN Realization
Exercise 4
Title: OAM
Objectives: The participant knows the way to display data management

information.
Pre-requisite: Connection to the P-CSCF possible
Task
Query
Connect to the P-CSCF ……………. using the correct interface, display the
configured Access Networks for this IMS.
CN37532EN10GLA0
49
IMS NSN Realization
CN37532EN10GLA0
IMS NSN Realization
6 Solution
CN37532EN10GLA0
51
IMS NSN Realization
Solution 1
Title: Network Entities
Objectives: The participant can allocate a functionality to a product
Pre-requisite: none
Task
Query
The HSS is realized by the CFX-5000 Yes No
The HSS is realized by the CMS-8200 Yes No
The P-CSCF is realized by the CFX-5000 Yes No
The P-CSCF is realized by the CMS-8200 Yes No
The SPDF can be part of the CFX-5000 Yes No
The SPDF can be part of the CMS-8200 Yes No
The SPDF can be part of the HiQ 8000 Yes No
The SPDF can be an product PCS-5000 Yes No
The MCF is part of the CFX-5000 Yes No
The MCF is part of the CMS-8200 Yes No
The MCF is an own product HiM-5700 Yes No
CN37532EN10GLA0
IMS NSN Realization
Solution 2
Title: Features in IMS
Objectives: The participants can describe the features on a low level
Pre-requisite: none
Task
Query
convert SIP into Diameter Signaling
reduce the bandwidth consumption
IMS supports IPv4 and IPv6 Yes No
Among others the IMS supports Yes No

authentication and key agreement as a
security mechanism
IMS supports just offline charging, online Yes No

charging will be introduced in later versions
Once a user is registered and Yes No

authenticated for a certain service, there is
no need for further authentication in case
additional services are used.
To use supplementary services like CLIP Yes No

or CLIR, the user must connect via ISDN
over ATM.
CN37532EN10GLA0
53
IMS NSN Realization
Solution 3
Title: OAM
Objectives: The participant knows the different ways to connect to the

network elements
Pre-requisite: Connection to the HSS possible
Task
Query
The HSS and the CSCF are operated Yes No

using the NetAct as a network element
manager
The NSN service personnel has by Yes No

using the “comservice” login at the
NetAct, the same rights and duties as
present with the LEMAF IF
Which one of the following A

configuration classes a customer B
operator typically changes?
C
D
E
You want to connect to the HSS, The HTTP GUI

which tools or interface do you use to
display a subscriber?
CN37532EN10GLA0
IMS NSN Realization
Solution 4
Title: OAM
Objectives: The participant knows the way to display data management

information.
Pre-requisite: Connection to the P-CSCF possible
Task
Query
Connect to the P-CSCF ……………. using the correct interface, display the
configured Access Networks for this IMS.
Fig. 35
CN37532EN10GLA0
55
IMS NSN Realization
CN37532EN10GLA0

02 CN37532EN10GLA0 IMS NSN Doc PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

02 CN37532EN10GLA0 IMS NSN Doc PDF

Загружено:

Авторское право:

Доступные форматы

IMS NSN Realization

IMS NSN Realization

1 Network Entities and their Realization

Overview Network Topology and entity realization

Symbol 3GPP NSN Platform Symbol 3GPP NSN Platform

CMS- ATCA hiG1800 Genband

Subscriber HP Proliant BL460 VAS hiQ4200 Sun Netra X4720

PCS- ATCA ACPI4-B

BGF ACME NET

MRF Mereon MS 6000

Fig. 1 Overview of IMS solution component

Fig. 2 IMS Realization

CFX5000 Cx CFX5000 CFX5000

CFX5000 Cx CFX5000 Cx CFX5000

ACME BG ACME SD PCS-5000

Fig. 3 Collocation variants

2 Feature overview in the IMS of NSN

2.1 Network or Carrier related Features:

Secure Operator Interworking

SIEMENS SIEMENS SIEMENS SIEMENS

Fig. 4 Key Network features Network 1

SIEMENS SIEMENS SIEMENS SIEMENS

Emergency Calls IMS

Lawfull Interception SIEMENS SIEMENS

Fig. 5 Key Network features Network 2

SIEMENS SIEMENS SIEMENS SIEMENS

Number Portability IMS

Option. Zb according to TS33.210

Fig. 6 Key Network features Network 3

Visited Network (superoperator.com) Home Network (niceoperator.net)

Fig. 7 Key Network features Network 4

2.2 End-user related Features:

Fig. 8 End User related features 1

Single Radio Voice

Fig. 9 End User related Features 2

Fig. 10 End User Features 3

3 SW Clients and Terminals

 Eyebeam V1.11 as residential softclient (voice)

Siemens optiPoint 410

Mobile Personal Assistant

Nokia N97 Mini

PhonerLite 1.44, 1.49

Arris TM602A eMTA

Fig. 11 Software Clients and Terminals

4 Operation and Maintenance Concept

4.1 OAM Interfaces

OAM Management Access

LEMAF OAM Agent UI putty/ psftp

Fig. 12 Interfaces Overview

User Workstation User Workstation

Web Browser Web Browser

Application Server (NetAct Core NAC)

ATCA / TSP platform ATCA / TSP platform

Fig. 13 O&M Interfaces

4.2 Operation tasks

For CMS-8200 the following configuration data can be administered:

Administrable Data in the CFX-5000 and CMS-8200

• Class A development data

Fig. 14 Changeable Configuration data 1

CFX-5000 configuration data:

CMS-8200 configuration data

Fig. 15 Changeable Configuration data 2

4.2.2 Technical Project Data (TPD)