Motorola IMS-DS

Version: 4.0
Last Modified: June 18 2006
 3GPP IMS Architecture
Sh

IP-Connectivity C,D,
Access Network Ut Dh Gc,Gr Legacy Networks
(I-CAN) AS SLF HSS (CS / PS)

Dx Cx

ISC

Mm
Mwº I-CSCF IP Multimedia Networks
Mw Mm (PDN)
Um Gm Mw Mr
UE P-CSCF S-CSCF MRFC
Mg
Gq Mi Mp
Other IMS Networks
Go Mj Mk
GGSN PDF MGCF BGCF BGCF

Mn PSTN

SGSN Mb CS Domain
(PSTN / PLMN)
Mb
MGW Mb
Mb
RAN MRFP

Mb

Signaling
IMS
Bearer
 IMS-DS:
Key Architecture Goals
 Leverage existing Hardware Platform – Motorola Chassis, CPCI
cards, Znyx switches, TAMs, RAIDs
 Leverage existing Software Platform – MobiOS
 Leverage existing OAMP Platform – Provisioning, Database
Framework.
 Provide ability for Cx Lookup and Update Scaling by incrementatl
addition of CPU cards
 Provide ability for capacity in millions of provisioned users
 Provide IP Based Sh and Cx Diameter Interfaces
 Current needs donot require SS7 (IS41/MAP) interface – no SS7
Card.
 Appear to the external entities one Physical IP address.
 Scaling across mutliple instances to be done through domain-name
based partitioning of users at SCSCF Diameter routing or an SLF.
 IMS-DS:
Logical Functions Implemented
HSS
-Subscriber Provisioning
-Service Profile Provisioning
-Cx Registration Procedures
-Cx Location Procedures
-Cx Notification Procedurs
-Sh Pull/Pushs
 IMS-DS:
Processes Summary
IPMH – IP Message Handler MOServer – Database Mgmt
[1 pair per chassis, 1:1 process redundancy] Enable Provisioning/Mgmt interfaces (TL1, Web,
SNMP), Manage updates, Subscriber
Message Distribution
Provisioning, Subscriber Assignment
Transport Services, Connection Mgmt.

AD – Active Directory CDE/CEM

[multiple pair per chassis, 1:1 process
redundancy, 1 one on each card.] Compute element management, OAM Message
Collection and Event distribution
Cx/Cx message services
Dynamic data store
Subscriber Ownership.
LOGCM – Log Consumer
Logging Collection, Log Writing, Log
Rotation
 IMS-DS:
Core Processes & Function Map

HSS

IPMH AD
 IMS-DS:
HSS Architecture

 OneHSS entity is implemented with two

processes:
 IPMH handles all communications outside the chassis
(1 Active-Backup pair is run per chassis).
 ADHSS is the storage process for subscribers,
implements the Cx and Dx interface.
 IMS-DS: Hardware/Processes
MoServer, XML Prov, DB

AD5 - B
AD1 - B

AD3 - B

AD4 - B
AD 2 B
AD 2

AD5
AD1

AD3

AD4
1 2 3 4 5 6

TAM IPMH AD

ZNYX Reserved Cannot Use

Active Backup Pairing

 IMS-DS:
Process Interfaces

Cx/Sh
Diameter/TCP
Logging
IPMH Web
MoServer
WinCap/SCTP Stats/Alarms

MoServer XML
AD Subscriber
AD ….. AD
AD Prov
 IMS-DS: AD

AD Module

Ft Checkpointing
Holds subscriber data
Holds service profiles
Cx Interface
Dx interface
Sh Interface

WinCap

NIM
 IMS-DS: AD

 The AD HSS has the following functions:

 Maintains subscriber info:
 SIP URI – Tel URI mapping
 Filter criteria definition – XML.
 Service profile assignment
 Other parameters as roaming, barring.
 Dynamic registration data – current SCSCF, registration tate.
 Responds to Cx / Dx quries from authorized CSCFs
 Initiates Cx / Dx Notifies to concerned CSCFs
 Responds to Sh requests from IMS Application Servers
 Initiates service profile updates and user deregistration procedures.
 FT of assigned S-CSCF.
 IMS-DS: AD: WinCap

 TheWinCap/NIM module has the following

functions (for IPMH as well):
 Establish reliables transport connection with peer over
SCTP.
 Instructs
IPMH of willingness to serve different
payloads based on process provisioning (AD HSS
subscribes to Cx/Sh).
 WinCap rovides the means to encapsulate messages
(diameter) to send to peer
 IMS-DS:AD

 Subscriber assignment
 Every subscriber is assigned a serving process id on
provisioning (MoServer) to maintain AD cards load balanced
 Every card holds its subscribers and knows of all subscribers in
the AD HSS
 Subscriber owner serves request.
 Ownership for NACK identified through hashing on subscriber
ID. NACK mechanism for invalid subscribers. Only one card
responds for invalid subscribers based on subscriber hashing.
 IMS-DS: IPMH Architecture

DIAMETER ROUTING

WINCAP
- To AD CACHE
TCP
- External
NIM
 IMS-DS: IPMH: Cx/Sh

 Broadcastsreceived messages (Cx/Sh) to all AD

HSS applications in chassis.
 IMS-DS: IPMH : Diameter

 Initiates
and maintains Diameter over TCP transport
connection to peer.
 Implements DWR/DWA (heartbeat) CER/CEA (capability
exchange) procedures.
 Based on configuration initiates as diameter client or
server.
 Capable of maintaining multiple Diameter connections.
 Identifies appropriate destination for diameter requests.
 Broadcasts received messages to all AD applications in
chassis.