11 Bani Dutta Configuring Sizing OpenCall USP for Distribution

Configuring and sizing HP OpenCall signaling portfolioBanibrata Dutta June 2nd, 2008

APJ Software Bootcamp 2008

2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

OpenCall Signaling portfolio overview


Key benefits

Operate and converge with a single, more flexible environmentCDR

Signaling blueprint for solution developers


Rich set of APIs Future proof today and tomorrows connectivity Fast time to revenue Streamline operations & lower costs

mobile charging messaging video voice games

NEP applications

Key capabilities

Real-time Application ServerOC USP-M OC SIP OC DIAMETER

Full featured Unprecedented scalability, performance and reliability Proven with worldwide networks coverage3 97617

OpenCall signaling developer platform

IP-STGSS7 TDM/IP

SNSSIP/Diameter IMS

OpenCall Universal Signaling PlatformProducts overviewM2PA, M2UA, M3UA, SUA


Proxy, Registrar, Redirect, SIP Loadbalancer

TCAP, ISUP, SCCP, MTP

OC SS7 API:

C/C ++ API

JAIN SIP API

C/C ++ API

JAIN like API

OC IP-STGNSL, HSL, ATM

OC SNSOC USP SIP

OC USPOC IP-STG

OC USP SIP

OC USP Diameter

Box offering

Developer offering = OC USP

+ Suite of Services spanning: evaluation, development, deployment and operation

OpenCall USP: solid foundation to consolidate your network and build nextgen solutions4 97617

OpenCall USP and legacy signaling: SS7, SIGTRANHP solution includes:


High Availability and Scalability

High availability, scalability and performance with Developer platform with N+1distributed architecture, geographic dispersion TCAP, ISUP, SCCP, MTP3, Grow as your traffic evolves M3UA APIs, a.k.a. the Back-End IP-STG as the Front-End Service Provisioning that hosts the SS7 E1/T1 On-demand service provisioning, faster time to market connectivity Intelligent routing and traffic load-balancing serving the Off-the-shelf servers and multiple services operating systems (HP-UX, LINUX) Security Network Consolidation Proven and certified connectivity, easy evolution for existing services, provides new connectivities to prepare for the future5 97617

OpenCall USP and nextgen signaling: SIP, DIAMETERHP solution includes: SIP DIAMETER Run on operating systems: HP-UX and LINUX


HP OpenCall USP SIP State-of-the-art SIP stack, 3G/IMS ready (privacy, reason header, IPv6 support, security)

HP OpenCall USP Diameter Triple-A play. Accounting Credit Control Application and On-Line / Off-Line charging Play for Application Server, HSS, and CSCF with support of Cx, Dx, Sh for Authorization, Authentication

6

97617

OpenCall signaling network element: IP-STGHP solution includes:Signaling Gateway ITU, ANSI, CHINA protocols NSL, HSL, ATM connectivity - quad span E1/T1 board (4 ports)


Signaling Access Point or Front End by providing SIGTRAN and MTP2/SAAL HSL connectivity multiple Protocol conversions ANY-TO-ANY

Edge-STP Full STP routing capabilities at the edge of the signaling network Easy integration with core network STPs Cost reduction with signaling backhauling over IP

SIGTRAN: M2PA, M2UA, M3UA Intelligent routing: MAP, IS41, TCAP OpCode, other

Intelligent router Intelligent Router to dissociate the services layer from the network layer signaling hub to load balance traffic in a weighted way to next generation services

7

97617

OpenCall nextgen network element: SNSHP solution includes:SIP Load-Balancer Load-Balancing Proxy, Redirect, Registrar Intelligent routing


High service availability and scalability Operational integration with the OpenCall Media Platform: enables platform load-driven or weighted load-balancing and forceful/graceful shutdown Works as a layer 7 load-balancer

Proxy, Redirect, Registrar Provides advanced SIP and Diameter Proxy, SIP Redirect, SIP Registrar functions in addition to load-balancing capabilities when needed by the network

Intelligent routing Enables new service introduction and a hierarchical topology of the services by routing on any SIP field or combination of SIP fields with complex criteria Easy scripting and customization through OpenCall RO

8

97617

OpenCall USP-M architecture


USP-M architecture (1/2) BE:

distributed architecture


Supports both PARISC and Itanium, with HP-UX Supports Proliant X86_64 (AMD and Intel), and c-Class with Linux RHEL No need for SS7 H/w in pure SIGTRAN platforms

User Developed Applications

OCSS7 APIs

N+1

ISUP SCCP TCAP M3UA/SCTP/IP

FE:

an M3UA GatewayN+1

IP-STG provides high traffic processing capacities IP-STG provides high scalability with N+1 distributed architecture and geo-dispersion with unique PC Mated-pair configuration with C-link available10 97617

Signaling Front-end IP-STG M2PA SS7 boards

SS7 IP network

SS7 TDM network

USP-M architecture (2/2)Connectivity to SS7 TDM network BE/MWTCAP TCAP SCCP SCCP ISUP ISUP M3UA M3UA SCTP SCTPIP IP


Connectivity to IP sigtran network BE/MW

FE = IP-STGNIF NIF MTP3 MTP3 MTP2 MTP2 MTP1 MTP1 SS7 SS7 Network Network

TCAP TCAP SCCP SCCP ISUP ISUP

M3UA M3UA SCTP SCTP SIGTRAN IP IP IP IP Network Network11 97617

M3UA M3UA

SIGTRAN

SCTP SCTP IP IP

IP IP Network Network

OpenCall USP-M configurations


OCUSP-M possible configurations and Fault Resilience, for 1 Point CodeAPJ Software Bootcamp 08User Applications User OCSS7 APIs Applications User Applications OCSS7 APIs User Applications OCSS7 APIs OCSS7 APIs

Deported APIs: N+1

BESimplex

User Applications OCSS7 APIs ISUP SCCP TCAP IPSP M3UA AS/SG

Or

Duplex MW

User Applications User Applications OCSS7 APIs OCSS7 APIs ISUP SCCP TCAP M3UA/SCTP/IP ISUP SCCP TCAP M3UA AS/SG IPSP

ISUP SCCP TCAP M3UA ISUP SCCP TCAP AS/SG IPSP IPSP AS/SG M3UA AS/SG

FE: N+1

Signaling Front-end IP-STG STN DNBE1 boards

Signaling Front-end IP-STG STN Signaling Front-end DNBE1 boards IP-STG STN DNBE1 boards

Signaling Front-end IP-STG STN Signaling Front-end DNBE1 IP-STG STN boards Signaling Front-end DNBE1 boards IP-STG STN DNBE1 boards

SS7 IP network

SS7 TDM network

SS7 IP network

SS7 TDM network

SS7 IP network

SS7 TDM network

Entry Level Platform13 97617

HA Duplex Platform

Fully distributed Platform

BE: Back-End ; MW: Middleware ; FE: Front-End

OCUSP-M Possible Configurations, with several Local Point CodesUSP-M

BE (Back-end cluster)

IP-STG

FE (Front-end cluster)Appli 1 LPC Y


Appli 1

Appli 2

Appli 1 Central. OAM

Appli 1 Central. OAM

Appli 1 LPC Z

Central. Central. OAM OAM

LPC X LPC X LPC Y LPC X LPC Y IP-STG as a separate network element, routing traffic to several Applications In this case, as each element has its own PC, no centralized OAM is available from USP-M to configure/monitor IP-STG

Seamless USP-M (BE and FE) cluster Share the same platform, same servers BE and FE LPC are shared between BE and FE: Centralized OAM from each BE is available to manage IP-STG14 97617

IP-STG as FE of different Applications on different USP-M BE clusters LPC are shared between BE and FE: Centralized OAM from each BE is available to manage IP-STG

Note: Maximum LPC on one BE cluster is 4, and 26 on one FE cluster

OpenCall USP/IP-STG licensing policy


IP-STG configurationHardware OptionsRack-mounted c-Class SS7


Proliant DL380, DL360 IA32

Blade Proliant BL460c, BL465c

E1/T1 quad board (4 trunks): Up to 124 links according to server throughput or 4 x 2 Mbits High Speed Links

ATM

board: 2 ATM over E1 or T1 trunks

Software licensing Options

One SGP license per node Link based license

Performances

10,000 TCAP TPS = 20,000 TCAP MSU/sec per server SS7 IN-OUT, Sigtran IN-OUT, SS7 IN + Sigtran OUT

4,000 TPS for High Perf board 2,000 TPS for Entry Level board97617

16

OpenCall IP-STG configurationSGP license: Signaling Gateway Process

(contd)APJ Software Bootcamp 08

1 SGP license per server independently of # PC played by each server/platform SGP Licensing Scheme: 4 different licenses SGP Lite For single SGP gateway only Not scalable with additional SGP on 1 GW

SGP Distributed Entry Level From monolithic (single) to distributed gateways Allow to scale additional SGPs on 1 GW Valid if 16 links per SGP

SGP Upgrade from Entry Level to High-End17 97617

OpenCall IP-STG configuration

(contd)APJ Software Bootcamp 08

link/connectivity licensing scheme: 3 licensesSS7 narrowband legacy Link

Classic 64/56 kbps SS7 links 1 license token per TDM link, independently of the number E1/T1 of trunks

SS7 High Speed Links (HSL) 2 Mbps unchannelized or ATM HSL 1 license per HSL trunk

Additional protocols: M3UA capability (for IP-STG SFE gateway only) Add the M3UA capability to a SUA gateway 1 license per node, independently of the # of equivalent links/traffic

M2PA/M2UA capability Add the M2PA capability to an IP-STG 1 license per node, independently of the # of equivalent links/traffic18 97617

USP-M configurationConnectivity Option: MTP (Back-End + Front-End)FE


= IP-STG distribution & Fault resilience based on CPU

BE:

Connectivity Option: M3UA (no Front-End)

IP-SP or ASP mode connected to third party GW (Back-End w/o IP-STG Front-End) Capacity: 25-TPS LTU, same price than an USP/IP-STG low-speed link Distribution & Fault resilience: based on CPU

Performance

up to 28,000 TPS for Integrity MW server and 42,000 TPS for Proliant G5 MW server

19

97617

OpenCall USP-M Licensing summaryLicensing is two-fold: Back-end and Front-end


Back-End:

Front-End:

Per CPU LTU, independently of platform topology (simplex, duplex, distributed) TPS based license, in case of direct connectivity to IP SIGTRAN network SGP LTU per server:

Connectivity LTU:

SGP Lite: limited to single server, not scalable SGP distributed Entry-Level: up to 16 links, available for single and distributed configurations SGP distributed High-Perf: >16 links SGP Upgrade: upgrade from Entry-Level to High-Perf SGP Per NSL link Per HSL link M2PA LTU per SGP

20

97617

Example Sizing CalculationAPJ Size IP-STG for Prepaid Charging application, given:Software Bootcamp 08

Subscribers = 1.0M BHCA = 2.5 (per subscriber) Avg. call duration = 90 sec TCAP Txn/Call = 2.5 Max Link Loading = 0.4 Erlangs Avg. TCAP msg. size = 200 octets Total CAPS = (BHCA * Subs) / 3600 = 2.5 * 10^6 / 3600 ~= 694 Total TPS = (Total CAPS * Txn-per-Call) = 694.44 * 2.5 ~= 1736 Assumed, TPS handled/NSL = 23 TSP/NSL (assuming 0.4Erl, 200oct MSU) No. of NSLs required = 1736/23 ~= 76 NSLs (

11 Bani Dutta Configuring Sizing OpenCall USP for Distribution

Documents

Transcript of 11 Bani Dutta Configuring Sizing OpenCall USP for Distribution