1 / 23

The Multiservice Switching Forum (MSF) “ Fighting for Open Architecture & Interoperability”

The Multiservice Switching Forum (MSF) “ Fighting for Open Architecture & Interoperability”. December 2001 Roger Ward MSF President. Origins of the MSF. Today’s networks are dedicated to specific services leading to Inefficient use of transmission capacity Increased operating costs

lori
Download Presentation

The Multiservice Switching Forum (MSF) “ Fighting for Open Architecture & Interoperability”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Multiservice Switching Forum (MSF) “Fighting for Open Architecture & Interoperability” December 2001 Roger Ward MSF President

  2. Origins of the MSF Today’s networks are dedicated to specific services leading to • Inefficient use of transmission capacity • Increased operating costs • Legacy investment “lock-in”

  3. Open Multiservice Switching Model Common transmission and switching infrastructure Modular, layered architecture Integration at a module level through open interfaces Multi-vendor model with 3rd party software options @ File Server Email Server Database Operating System and Processing Platform I/O Peripherals and Disk Drives Computing Analogy MSF Approach Voice Services Control Control ATM/FR Services Switch Switch Switch Adaptation Adaptation IP Services

  4. The Procurement Challenge • Carriers versus vendors ! • Carrier/ vendor specific solutions • Contacts outside existing suppliers too time consuming • Specifications for open interfaces elusive • No open “hooks” for the future • No coherent industry development framework • Procurement “tactical” given cost/time constraints

  5. Why we don’t change • Too close to the grindstone! • No time to set up pan-industry contacts to help • Global co-operation & collaboration requires time to be fruitful (1 - 2 years +) • Standards are great , but they lag end user needs & there are so many to chose from! • Individual players have little influence alone on key bodies (e.g. IETF) • Don’t know how to work a common agenda with our competitors

  6. MSF Mission To accelerate the deployment of open communication systems and to help its members realise the economic benefits which result from the flexible support of a full range of network services using multiple infrastructure technologies

  7. MSF Product Set Open Discussion Environment Architectural Framework • Coherent Big Picture Protocol Selection & Profiling • Closing the options • Filling the gaps “Inter-Op” Testing • Validated Implementation Agreements • Network Inter-operability Events Commercially Viable Physical Implementations

  8. Current MSF Members

  9. Board of Directors Processes Policies Liaison Sub-Committee Marketing and Education Committee Technical Committee Schedules Meeting Agendas Technical Direction Relationships with other industry groups Promotions, Events Industry Positioning Media Control WG Architecture WG Switch Control WG Control Interfaces to Switches Switch Management Functional/Physical Models Specification Release Plan Multimedia Control Model Interfaces to Media Gateways Management Framework WG Interoperability WG Management Architecture and Interfaces Interoperability Events Compliance MSF Organization

  10. Telecom Italia Federico Renon, Vice President Board of Directors • BT Roger Ward, President • WorldCom Chris Daniel • Nortel Networks Avri Doria • Marconi Brian Down • Siemens David Francisco • Cisco Systems Morgan Littlewood • NTT Kou Miyake • Qwest Pieter Poll • Lucent Technologies Mark Disbrow

  11. MSF Strengths • Global membership & mature organisation • Demonstrated ability to influence other bodies • e.g. H.248 carrier requirements, GSMP, BICC • Profiling/ championing protocols for interoperability • e.g. H.248 trunk & access gateways, BICC, SIP, SIP-T) • Commercially viable interoperability / demonstration

  12. MSF is not working alone! ATM Forum 3GPP MSF TMF IETF ATM Transport for Megaco MSF99.167 Signalling mechanism for LLE MSF2001. 043 & 044 Architecture Clarification MSF2000-206 ETSI ATM Bearer Management MSF2001.045 Megaco CAS BICC support for ATM bearers with H248 MSF2001.46 Management Architectures SG16 Megaco/H248 MGC profiles for SIP-T & Q-BICC ITU-T SG11 GSMP MSF99.175 Agreement to cooperate MSF99.034 Develop VB5 TIPHON Developing Techniques MSF2001.006 Object techniques & languages API’s PARLAY MGCP Requirements Legal Intercept OMG Joint interoperability testing MPLS Forum ISC

  13. Release 2: Reference Architecture RACF HOCF Service Information Function Application Plane Service Creation Environment Function di Service Logic Function sc Signaling Transport Signaling is scm sg Service Coordination Function sa Service Management Function sdm i/fs Call Signaling st ix ia Network Service Instance Control Function Sig G’wy Function Sig N’twk Function MCF bc ic Sub-Ordinate Management Function Call & Bearer Signaling mb bs' Bearer Control Function vscm bs Control Plane Network Edge Control Function Virtual Switch Control Function vsm sp vsc np sm Switching Plane Super-Ordinate Management Function Virtual Switch Function Management Plane Adaptation Plane Partitioning Function Logical Port Function

  14. Service Feature Gateway Function Service Feature Gateway Function Signalling Gateway Function Signalling Gateway Function Network Service Instance Control Function Network Service Instance Control Function Sub-ordinate Management Function Sub-ordinate Management Function Network Edge Control Function Bearer Control Function Bearer Control Function Network Edge Control Function Virtual Switch Control Function Virtual Switch Control Function Super-ordinate Mgt Function Super-ordinate Management Function Network Access Server (NAS) Function Network Access Server (NAS) Function MSF Protocol Selection & Profiling Radius, Diameter BICC, SIP-T MGCP, MEGACO, SIP, H.323 Application Plane H.248, OSPF, IS-IS, BGF, PIM-SM, MSDP, MBGP sg sg sa sa sf ix sf ia mb bc mb vscm vscm ic bs’ bs bs bs’ SNMP, COPS,HTTP,CLI CAR,CBWFQ, PQ-CBWFQ,WRED,DDR WDRR vsm vsm Control Plane GSMP np sp vsc vsc sp np Switching Plane Virtual Switch Function Virtual Switch Function sm sm Logical Port Function Logical Port Function Partitioning Function* Partitioning Function* IPSEC, GRE, L2TP, L2F, IP/IP, MPLS CR-LDP, RSVP, MPLS,GSMP, BICC, PNNI, UNI4.0 Adaptation Plane VRRP, HSRP Management Plane Management Plane NODE A NODE B

  15. Functional blocks are bundled into physical boxes for practical network deployments Networks can be built from multi-vendor boxes, interworking via open interfaces MSF profiles utilise standards-based protocols, but constrain the options to ensure interoperability H.248 MSF Architecture - Physical Mapping BICC SIP SIP-T

  16. MSF H.248 Implementation Agreements • Access Gateway(Agreed September 2001) • Media gateway controller / trunking gateway for ATM trunks • Trunking Gateway(Agreed September 2001) • Media gateway controller / access gateway for ATM trunks • Media gateway controller / IP-ATM gateway • Residential Gateways(Future Work Item) • Media gateway controller / Residential local loop emulation (LES) gateway • Media gateway controller / residential gateway

  17. Protocols used between Media Gateway Controllers The MSF is also profiling the following protocols for use between MGC,s: • BICC • SIP-T • SIP

  18. IA Validation H.248/ Megaco IA BICC IA SIP / SIP-T IA Scenario Set 1 Network Interoperability Event Architecture Release 1 Interoperability & Validation Ultimate Goal Depth MSF IA’s • Appropriate interfaces identified and profiled • Candidate services described and proven Breadth

  19. 2002 IA Validation • single protocols • detailed test specifications • 3 events in 2002 (H.248 (3 profiles), BICC, SIP/ SIP-t) IA Validation H.248/ Megaco IA SIP / SIP-T IA BICC IA Network Interoperability Event Scenario Set 1 • small feature set • full network • 1 large event October 2002 Architecture Release 1

  20. 2002 Network Interoperability Event Voice Data IP over MPLS ATM-TDM TDM-ATM-TDM TDM-IP-TDM IP-TDM Scenario Set 1 TDM Class 5 with IP Class 4 IP Class 5 with TDM Class 4 I/W) TDM Class 5 with ATM Class 4 ATM Class 5 with TDM Class 4 I/w VPN’s Scenario Set 2 IP- ATM IP- IP IP Class 5 to ATM Class 4 I/W (BT/Marconi) Full SIP (NTT)

  21. The MSF Opportunity • Bringing it all together • Help build industry consensus • Fight for true interoperability • Champion the right standards at the right time • Derive commercially viable Implementation Agreements

  22. Key Areas For Co-operation • Architecture • Protocol & profile development • Interoperability & test • Management

  23. To Find Out More Visit our web site: www.msforum.org

More Related