Professional Documents
Culture Documents
2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
Key benefits
Rich set of APIs Future proof today and tomorrows connectivity Fast time to revenue Streamline operations & lower costs
NEP applications
Key capabilities
Full featured Unprecedented scalability, performance and reliability Proven with worldwide networks coverage
3 97617
IP-STG
SS7 TDM/IP
SNS
SIP/Diameter IMS
OC SS7 API:
C/C ++ API
C/C ++ API
OC IP-STG
NSL, HSL, ATM
OC SNS
OC USP SIP
OC USP
OC IP-STG
OC USP SIP
OC USP Diameter
Box offering
OpenCall USP: solid foundation to consolidate your network and build nextgen solutions
4 97617
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 future
5 97617
97617
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
97617
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
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
97617
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
OCSS7 APIs
N+1
FE:
an M3UA Gateway
N+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 available
10 97617
SS7 IP network
FE = IP-STG
NIF NIF MTP3 MTP3 MTP2 MTP2 MTP1 MTP1 SS7 SS7 Network Network
M3UA M3UA
SIGTRAN
SCTP SCTP IP IP
IP IP Network Network
BE
Simplex
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 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 IP network
SS7 IP network
HA Duplex Platform
BE (Back-end cluster)
IP-STG
FE (Front-end cluster)
Appli 1 LPC Y
Appli 1
Appli 2
Appli 1 LPC Z
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-STG
14 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
IP-STG configuration
Hardware Options
Rack-mounted c-Class SS7
E1/T1 quad board (4 trunks): Up to 124 links according to server throughput or 4 x 2 Mbits High Speed Links
ATM
Performances
4,000 TPS for High Perf board 2,000 TPS for Entry Level board
97617
16
(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
(contd)
APJ Software Bootcamp 08
Classic 64/56 kbps SS7 links 1 license token per TDM link, independently of the number E1/T1 of trunks
M2PA/M2UA capability
Add the M2PA capability to an IP-STG 1 license per node, independently of the # of equivalent links/traffic
18 97617
USP-M configuration
Connectivity Option: MTP (Back-End + Front-End)
FE
BE:
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
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
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 ( <=1 quad-port E1 card) Thus, we need 1 IP-STG with 1 quad-port E1 card, for carrying traffic, and due to N+1 architecture, need 2 IP-STGs for redundancy.
21 97617
Calculation:
Diameter Base Protocol: implementation of the IETF specification RFC 3588 Diameter AAA: Authentication, Authorization, Accounting defined by the 3GPP consortium for the IMS environment
23
97617
Evaluation license
Delivery
24
Web delivery
97617
Transport layer is the implementation of the IETF RFC 3261 A comprehensive set of additional RFCs supported for transaction, call handling, parser, etc
26
97617
license is 10-Transactions per second (10-TPS license). of 10-TPS licenses are available (5x, 10x, 100x)
Bundles
Evaluation license
Delivery
Web delivery
27
97617