[March 20, 2002]

MSF Releases Two New Specifications For Enhancing Interoperability Of Telecom Switching Systems

The Multiservice Switching Forum (MSF) revealed that its membership has given final approval to two new Implementation Agreements (IAs) aimed at enhancing the interoperability of telecommunications switching systems. The two IAs, developed by the MSF's Media Control Working Group, profile the protocols needed for controlling media gateways from media gateway controllers and for signaling between media gateway controllers. The MSF's IAs are designed to be incorporated into the work of established international standards bodies such as the ITU.

"The approval of these agreements comes close on the heels of the MSF's first MEGACO/H.248 agreements," said Roger Ward, MSF president. "This is the clearest sign yet that the MSF is gaining momentum in its effort to define next generation communication systems. These IA's build an important foundation for the impending debut of MSF's Release2 Architecture." The MSF Release2 Architecture Framework, planned for release in 2002, is designed for use with both IP & ATM core networks as well as incorporating the functionality needed to integrate mobile and wireless capabilities.

A Multiservice Switching System (MSS) is a distributed switching method -- frame, cell or packet-based -- designed to support voice, video, private line and data such as ATM, Frame Relay and Internet Protocol (IP) services. A MSS may use a broad range of access technologies, including traditional Time Division Multiplexing (TDM), Digital Subscriber Line (xDSL), wireless data, and cable modems. MSF IAs define the requirements of the interfaces between MSS principal components.

The first of the newly released IAs, entitled MSF IP Trunking Gateway to Controller Profile is a MEGACO/H.248 profile for a media gateway controller (MGC)/trunking gateway using IP trunks. In this context, a trunking gateway provides an interface between Public Switched Telephony Network (PSTN) trunks, usually connected to a local exchange, and an IP-centric packet network.

The second new IA, Implementation Agreement for BICC, specifies a Bearer Independent Call Control (BICC) signalling path between MSF-compliant MGCs. BICC provides a common solution for the transportation of signalling messages relating to all packet network types, ATM and IP for example, while remaining independent of the underlying packet network technology.

[ Back To TMCnet.com's Homepage ]