Product Overview – SS7 technology

1. Product Overview – SS7 technology

2. Agenda • Overview • SS7 Boards and SIUs • Digital Signaling Converter • SG430 SIGTRAN Gateway

3. Objectives • To help you understand the different products and levels of integration • To help you understand the product capabilities

4. Connecting to SS7 Existing ISDNequipment IP equipmentor network Custom application SS7 Boards and SIUs DSC SIGTRAN Signalling Gateway SS7 Network #2 SS7 Network #1

5. SS7 boards and systems

6. Boards and SIUs • Require a developer to write an application program • SS7 components are scaleable; from small (single PC card) to large (4096/16384 circuit SS7 server) systems. • The same Application Programming Interface (API) is used for the complete range

7. SS7 Protocol support Full ITU-T and ANSIMTP1, 2, 3ISUPSCCPTCAPINAPGSM-MAPIS41 (ANSI-41)TUP Other national variants:NUP (UK-TUP)SSUTR-2 (France)Japanese ISUPChina TUP

8. Single chassis approach

9. PCCS6 (ISA) • Dual PCM port (E1/T1) SS7 interface card for ISA systems. • Dual V.35 compatible option. • 3 SS7 links • Up to 16 cards may be installed in a single chassis. • SCbus PCM highway. • Protocol contained firmware downloaded at run-time.

10. PCCS6: Architecture

11. ISA options Interface ports, either • 2 E1 BNC 75 (unbalanced) OR • 2 E1/T1 RJ45 120/100  (balanced) with optional V.35 compatible ports. Software • All protocol software may run within the SS7 card (for example ISUP or TUP or UK-TUP to control up to 1024 circuits). • For large multi-card systems higher protocol layers may run on the application processor. • Windows, Linux

12. CPM8 (Octal span) • 6U Compact PCI • Rear transition, 8 E1 or T1 (software programmable), 4 x V.11 (V.35 compatible) • Full hot swap in accordance with PICMG standards • H.110 interface • 4 SS7 links • Win NT, Linux

13. PCI4, PCI2S • Full length PCI • 4 E1 or T1 (software programmable),2 V.11 (V.35 compatible) • H.100 interface • 4 SS7 links • Win NT, Linux

14. cPCI/PCI architecture

15. Fault resilience • AIM : To eliminate single points of failure. • There are many ways that redundancy can be introduced into a system • More than one link in a link set - fault resilience is handled automatically by the MTP3 layer. • Multiple network connections (E1, T1 or V.35). • Multiple cards in a single chassis. • More than one route to a destination (use of STPs in the network to provide alternate routes) • Distributed architecture (may also be due to processor bandwidth) both for the application and the SS7 ‘front end’.

16. Redundancy • Redundancy within a single card. Load sharing between links (which would normally be on different ports) is automatic (managed by MTP3).

17. Redundancy (2) • Redundancy between two cards Handled automatically, MTP3 and above must run on the host processor

18. Distributed system Why?VOIP, heavy DSP processing demand, solution: distribute channels between platforms

19. With SS7……. Problem!How is the SS7 information relayed from Application platform 1 to the others?

20. SIU Problem! How to eliminate single points of failure?

21. Fault resilient SIU

22. SIU key features • Gives an SS7 interface to a multi-chassis application via a TCP/IP LAN. • Runs MTP, ISUP, NUP, TUP, SCCP, TCAP, MAP, INAP (CS1) and IS-41 locally. • Distributes the signalling data depending on CIC, point code (ISUP and TUP), transaction (TCAP). • Software is provided for the communication between the application program and SIU. • Two units can operate in a resilient configuration linked by SS7 and the Ethernet.

23. SIU231 (4U)24 x E1/T1/V.3532xSS7 links8xLink sets SIU520 (2U)6 x E1/T1/V.3512xSS7 links12xLink sets SIU131 (2U)4 x E1/T1/V.356xSS7 links6xLink sets SIUs (SS7 Servers)

24. SIU520 platform • NEBS certified 2U Intel® Chassis • Dual 1.2GHz Intel® Pentium ® III • Dual redundant AC or DC power

25. How does the application talk to the SIU? • Through a driver provided by Intel • IP/Ethernet is transparent • Same code development/API as SS7 cards

26. Voicemail using SIU

27. Protocol Architecture (SPA) • Each protocol ‘layer’ (e.g. MTP LEVEL2, MTP LEVEL 3, USER PART, etc.) and the user application runs as a individual task. • Tasks run on an SS7 line card, SIU or on the same processor and memory as the application. • All tasks have a well defined interface and communicate using messages. (standard structures defined in C). • Communication is achieved using messages Each task has a single input queue through which it receives messages from other tasks. • Each task is identified with a unique 8 bit ‘module_id’ similar to (but not the same as!) a Unix process id (pid)

28. Software model

29. APIs • GlobalCall available for ISUP and TUP • Direct SS7 protocol Interface for other layers – message based.

30. GlobalCall for SS7 GlobalCall API available for ISUP and TUP, started in SR 5.01 (Windows) Windows 5.1.1 (now supports TUP) Supports SS7 - ISA, PCI, CompactPCI, SIU, Dual resilient SIU, Multiple host, TUP and ISUP Linux 5.1 No GC/SS7 support Engineering version working (contact luc.provoost@intel.com)

31. Card software architecture

32. Multiple (independent) cards

33. Host based layer 4 (future)

34. Multiple cards, single point code (future)

35. SIU software architecture

36. Introduction to the DSC (Digital Signaling Converter)

37. The Digital Signalling Converter Existing ISDNequipment DSC210 DSC110 DSC310 SS7 Network #2 SS7 Network #1

38. Voice & Signalling Mode

39. Signalling Only Mode

40. DSCx10 functions Signalling Converter SS7 protocols (including ANSI, ITU-T, China No 7, Japan) Access Protocols (including Q.931, QSIG, DPNSS) Convert any protocol to any other All protocols at the same time! Intelligent Switch Routing based on the dialled number Prefixing/deleting of routing digits Conversion to en-bloc signalling from overlap Automatic retry and re-route Configurable circuit selection (hunting)

41. Routing Configuration Model

42. Parameter Manipulation The DSC210 can manipulate many of the parameters used by signalling systems e.g.:- • Calling Numbers • Called Numbers • Clearing Cause • Calling Party Category • Charging Indication • Echo Cancellors • Continuity Check • ISDN Service Level • Others

43. Remote billing, statistics IP connection (Ethernet) DSC310 Remote Data Centre • Remote Data Centre (via IP) - is a software package Billing records Call failure records Traffic measurements Remote software and configuration upgrade User defined clearing cause tables

44. Number Translation = a range of fully integrated (on box) number translation capabilities (uploaded from Remote Data Centre). Number translation Number portability Calling party number validation white list Calling party number validation black list

45. Remote call modification/ handling DSC310 IP connection (Ethernet) Intelligent Service Control Intelligent service control = low cost intelligent networking type services running over TCP/IP. Off the Shelf solutions Advanced routing, Number translation, Number portability, White list / black list calling party number translation Open Interface Solutions MAP / INAP transactions, Pre-paid, Follow me

46. OAMP • Configuration • using text command based interface, e.g. • CNPCI:PCM=5-1,PCMTYPE=E1,SYNCPRI=1; • over 2 serial or 2 Telnet ports • Alarms • Alarm log • Alarm relays (Urgent and Prompt) • Front Panel Alarms • Remote reporting of alarms to a remote data centre • SNMP • for alarm and event reporting - coming soon!

47. SG430 SIGTRAN SS7/IP GATEWAY

48. Overview • 2U M3UA SS7 to IP gateway to carry SS7 traffic across IP networks • Allows SS7 traffic to be terminated by an IP client ‘backhaul’ mode • Allows SS7 traffic to be carried between gateways ‘longhaul’ mode • Includes software protocols for terminating application

49. SS7 Sigtran Backhaul - Softswitch

50. SS7 Sigtran Backhaul - wireless