Onboard SS7 Protocol Conversion

Highlights

  • Solutions available between most major flavors of SS7 - ANSI, ITU-T, ETSI, Japan NTT and TTC, and China
  • There are more than 100 versions of SS7 variants throughout the world
  • Infield expertise, object-oriented software architecture and ten years experience doing SS7 conversions
  • Customers include some of the largest carrier and OEMs worldwide

Despite being a standard, there are more than 100 versions of SS7 variants in use throughout the world. PT offers protocol conversion capabilities between most major flavors of SS7 including ANSI, ITU-T, ETSI, Japan (NTT and TTC) and China in application layers such as:
 

  • ISUP
  • SCCP

Our expertise involves integrating protocol conversion with STP functionality, or providing in-line conversion where the solution is transparent (no point codes) to the interconnecting networks. Some examples of SS7 protocol converters include:
 

  • ANSI ISUP to ITU ISUP
  • Japan ISUP to ANSI ISUP
  • China SCCP to ITU SCCP

PT prides itself on being able to meet any SS7 protocol conversion need. This is a function of our infield expertise, object-oriented software architecture and extensive libraries of protocols developed from many years of experience doing SS7 conversions. Generally new variants can be accommodated within four to six weeks, although higher levels of the stack may offer unique challenges that may require more extensive development.

Why the Need for Protocol Conversion

Signaling interoperability between the various international flavors of SS7 continues to be a significant challenge to developers. Much of this relates to the fact that there were several somewhat different versions of SS7 standards and many different variations of flavors. Increasingly, telephony users are placing calls over IP as well as public-switched networks. While the IP network uses data packets, the public-switched telephone network (PSTN) uses the SS7 signaling protocol to set up and tear down phone calls or provide service features such as Local Number Portability (LNP), 800 service, Calling Name Display and others.

PTs' SEGway Signaling Gateway plays a critical role in supporting the seamless interworking between these two networks, and when this data is traveling though different geographical locales, protocol conversion may be required. The SEGway Signaling Gateway can include protocol conversion for most major flavors of SS7 and is recognized as a world leader in this area. PT has developed protocol solutions for some of the largest carriers and OEMs worldwide, who rely on us to provide workable solutions in short timeframes.

Timeline for SS7 History

The History of SS7


The SS7 standard defines the procedures and protocol by which network elements in the PSTN exchange information over a digital signaling network to perform call setup, routing and control.

Throughout the years, different variants, or flavors, of SS7 have been developed. In fact, today there are more than 100 different variants of SS7 worldwide. Of course, differences in protocols are certainly not specific to SS7 networks, there are multiple IP-side protocols being developed as well, including SCTP, M3UA, SUA, MGCP, H.248, MEGACO, SIP and H.323.

Because of these different SS7 flavors, signaling networks in one geographic area may not be able to interwork with a signaling network in another. Protocol conversion between these two flavors is necessary for intelligent routing to occur. In VoIP applications, this would ideally occur in the same signaling gateway that allows SS7 to communicate to IP. The SEGway Signaling Gateway does exactly this.