Nokia Siemens Networks

Fixed Mobile Convergence

Deltas between FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x

Introduction & overview + OAM

CC NGVM Solution Management IMS based FMC

Nawida Martinozzi
18th June 2009

1 © Nokia Siemens Networks

Agenda

Introduction and overview of the deltas between FMC 4.x/IMS 6.x and FMC
3.x/IMS 5.x

Detailed Technical presentations of the Deltas

OAM

Charging
Shared iFC

Routing incl. Emergency, LI and Media Release

Security
Provisioning
Performance
Network Dimensioning and Planning

Summary of FMC Documentation

IMS 6.2/FMC 4.2 Key Features

2 © Nokia Siemens Networks
Agenda

Introduction and overview of the deltas between FMC 4.x/IMS 6.x and FMC
3.x/IMS 5.x ( IMPACT’s)

Detailed Technical presentations of the Deltas

OAM

Charging
Shared iFC

Routing incl. Emergency, LI and Media Release

Security
Provisioning
Performance
Network Dimensioning and Planning

Summary of FMC Documentation

IMS 6.2/FMC 4.2 Key Features

3 © Nokia Siemens Networks
Introduction and overview of the deltas between
FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x
Two types of Release upgrade (main impacts/deltas):
1. Upgrade to FMC 4 (IMS 6) w/o introduction of new Features
or functionalities:
 Charging Tickets  Layout changes, CDR field changes/new
fields
• Adaptations to 3GPP R7 (changed and new fields).
• Introduction of new features (new fields)
• The changes are not backwards-compatible ==> the billing system must be
upgraded.
 Other func. Changes  None

4 © Nokia Siemens Networks

Introduction and overview of the deltas between
FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x
2. Release upgrade to FMC 4 with introduction of new features /
functionalities
 Charging 
• as previous slide +
• New CDR fields due to new func. and features
 Routing  Changes due to new i/fs, features+func.
• E-CSCF for emergency calls
• AS Resource Management
• Interconnection Border Control
• Lawful Interception Enhancements
• TISPAN compliant handling of privacy header - CLIR
• hiQ 4200 Multi Language Announcement
• Media Release

5 © Nokia Siemens Networks

Introduction and overview of the deltas between
FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x
 Shared iFCs 
• Shared iFCs (SiFCs) are defined according to 3GPP to reduce
bandwidth requirements at the Cx interface
• Beside “normal” iFCs, a service profile can contain zero or more
instances of shared iFC Sets
• Configuration of shared iFCs in S-CSCF & HSS
• Additional parameter for configuration in the HSS as global iFC
• Configuration of shared iFCs in the S-CSCF and the HSS according to
standard compliant XML format (new provisioning interface at HSS
• Optional Features and not Mandatory

6 © Nokia Siemens Networks

Introduction and overview of the deltas between
FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x
 Half Call Model (HCM) 
• hiQ R12 (FMC 3/IMS 5) did not support Half Call Model (HCM). If originating
and terminating subscriber were hosted at same hiQ, both services were
executed.
• With hiQ R13 (FMC 4/IMS 6) both models are supported old model and new
introduced HCM.
• Introducing HCM into a running systems needs a special procedure to reduce
service degradation time. Shared iFCs could help, but are no precondition
 LI  Improvements + new features support
– Re-routing via a bearer interception capable device
– IBCF is enhanced with X1 interface
– I-BGF replicates media stream
– S-CSCF generates IRI ticket
– hiQ improvements + HCM + LI for Forwarding subs.
– Utimaco LIMS improvements in IMS 6.2 – upgrade to Utimaco 7.0

7 © Nokia Siemens Networks

Introduction and overview of the deltas between
FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x
 Support of Residential Gateways 
• IMS 6.1  IMS 6.2: TPD configuration parameters to be changed!
 Change of LAN separation
• DNS entries can‘t be change online but only via TPD
• TPD configuration parameters to be changed!
 Performance
• SPDF (PCS-5000 V3.1,3.3) increased performance
• P/I/S – CSCF and HSS same as for IMS5.0 incl. HCM
• HiQ4200 R13 .x same as for HiQ4200 R12 incl. HCM
• The performance of the BGF is the same with old HW and increases with new
HW 4500
• The configuration IMS6.1as deployed in OSP can serve appr. 400 000 subs
according to the FT TM.

8 © Nokia Siemens Networks

Introduction and overview of the deltas between
FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x
 Security
• No changes in case of no new features
• Introduction of new Features:
• Blocking of IMPUs and IMPIs after multiple unsuccessful registration
attempts
• TLS support for Gm interface
• HSS Subscriber Provisioning GUI
• IBCF (Interworking Border Control Function)
• Changes at Gm Interface
• Special LAN Separation (for FT)
• Password Encryption on the Cx interface
• hiQ R13: Security on the h8k and HiPath SOAP Server Interface
• hiQ R13: SFTP protection of CDR delivery
• hiQ R13 NWT: SIP Registration P-Access_Network-Info Header Handling for
Security

9 © Nokia Siemens Networks

Introduction and overview of the deltas between
FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x
 Provisioning 
• No changes in case of no new functionalities and features
• Introduction of new Functionalities (based on features required by
customer)
• VAS (hiQ): many new provisioning parameter using new introduced Subs
features
• IMS 5.0  IMS 6.1
• Shared IMPU (multiple IMPI/IMPU)  subscriber profile changed, new HSS
provisioning interface
• Shared iFCs  new HSS provisioning interface
• Resource management for AS selection (pooling of AS’s)
In case of multiple instances of equivalent Application/Media
Servers, the S-CSCF automatically manages the distribution of traffic and
failover to these Servers.
 iFC in subscriber profiles to be changed / migrated to support
AS pool names

10 © Nokia Siemens Networks

Introduction and overview of the deltas between
FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x
 Provisioning 
• IMS 6.1  IMS 6.2
• Support of MSRP (Message Session Relay Protocol)
A new Media Server needs to be installed and the address
needs to be provided to the appropriate subscribers profile (iFC)
• Emergency Handling
2 options were needed to find the appropriate Emergency
Center
- via LRF – Location Retrieval Function and
- via subscriber specific iFC (as backup in case of
LRF not responding)
 iFC in subscriber profiles to be changed / migrated
to support LRF backup

Detail information on the provisioning can be found in the respective product

specification/documentation.

11 © Nokia Siemens Networks

Introduction and overview of the deltas between
FMC 4.x/IMS 6.x and FMC 3.x/IMS 5.x
 OAM 
• Interfaces changes only in case of new functionalities and features
• in the southbound-interfaces (e.g. interface between @Com and NE)
• In the northbound-interface. Here there is only some expansion of the
Inventory data which can be polled via Northbound.
• @Com Element Manager is always backward compatible to previous
releases.

• no interface changes, but new configuration parameters, counters and

alarms in case of new functionalities, upgraded NE versions/packages

• During Upgrade the OAM @Com must be upgraded first.

12 © Nokia Siemens Networks

Agenda

Introduction and overview of the deltas between FMC 4.x/IMS 6.x and FMC
3.x/IMS 5.x

Detailed Technical presentations of the Deltas

OAM
Charging
Shared iFC

Routing incl. Emergency, LI and Media Release

Security
Provisioning
Performance
Network Dimensioning and Planning

Summary of FMC Documentation

IMS 6.2/FMC 4.2 Key Features

13 © Nokia Siemens Networks
Detailed Technical presentations of the Deltas
OAM
 OAM Detail summary 
• FM:
• Alarm alignment support for MRF V3.1 (but no new alarms)
• TMFFMAgentAdapter component must support all new hiQ NEs
• No TMFSouthBound changes is required for alarm catalog upload as it will
be done the same way it is done for existing hiQ NEs
• iNMC will support the alarm catalog upload of all hiQ / hiG NETypes
• ACME BGF V6.5: Integration via SNMP (OneSnmpAdc).
Impact: Extend support for new alarms
• PM:
• No new offline counters for hiQ R13
• ACME BGF V6.5: Integration via SNMP (Online counters) for all nodes.
Impact: None; no new counters

14 © Nokia Siemens Networks

Detailed Technical presentations of the Deltas
OAM
 OAM Detail summary 
• B&R:
• B&R for the hiQ / hiG NE types is done in the same way as for
e.g. hiQ 4200 CV. So no impact on B&R. Only more disk space needed
• No change for MRF

• CM (Configuration Management):
• Impacts on Installation  None
• Impact/dependencies on system resources  None
• Impacts / Dependencies on Load Model and System Resources
• Small impact due to additional PM counters
• Impact on commonly used functions (platform)  None
• Impact on User Interface  New Icon for new NE type

15 © Nokia Siemens Networks

Detailed Technical presentations of the Deltas
OAM
Basic OAM support for new network elements / new versions for FMC 4.0:

• OAM Support for new FMC 4.0 NEs

– hiQ4200 (BVoIP) V13
– hiQ4300 V13
• OAM Support for new versions
– CSCF (CFX 5000) V6.1
– HSS (CMS8000) V6.1
– hiQ4200 (CVoIP) V13
– iNMC R13 (for support of hiG/hiQ V13)
– PCS V3.1
• Alarm Alignment support
– Media Resource Function OEM: Movius V3.1
• OAM Support for new versions
• iNMC R13 FP1
• hiQ4200 (CVoIP/BVoIP) R13 FP1
• hiQ4300 R13 FP1.

16 © Nokia Siemens Networks

Detailed Technical presentations of the Deltas
OAM
Basic OAM support for new network elements / new versions for FMC
4.1:
• OAM Support for new versions
• iNMC R13 FP1
• hiQ4200 (CVoIP/BVoIP) R13 FP1
• hiQ4300 R13 FP1.

Basic OAM support for new versions for FMC 4.2

• OAM Support for new versions
– CSCF (CFX 5000) V6.2
– HSS (CMS8000) V6.2
– iNMC (hiQ4200/4200/8000) R13 EP1 / R13 EP2
– C-BGF (ACME BG) V6.5
– PCS V3.3

17 © Nokia Siemens Networks