GMI 2006 Carrier-Driven Interoperability February 2006

Copyright 2006: MultiService Forum 2 MSF In The Value Chain

Copyright 2006: MultiService Forum 3 MSF Principal Members

Copyright 2006: MultiService Forum 4 MSF Framework for Collaboration Coherent Big Picture Physical Scenarios Closing the options Filling the gaps Test Specifications Protocol Interoperability Events Network Inter-operability Events

Copyright 2006: MultiService Forum 5 GMI2006 – Objectives To demonstrate multi-vendor interoperability to achieve Fixed Mobile Convergence supporting the IMS service framework and validate MSF R3 Implementation Agreements covering: Roaming services across multiple network types QoS (Session Border Controller and Bandwidth Manager) 3GPP IMS & Mobile Core Network Interoperability IP Carrier Interconnect/Interworking Security interoperability 3rd party applications and service brokering Network management and OSS IPv4/6 Interworking

Copyright 2006: MultiService Forum 6 Service Provider A MSF R3 Service Provider B Pure IMS Service Provider C MSF R3 Shared Interconnect Network (GRX) Peer to Peer Interconnects GMI2006 – MSF R3 Support of IMS

Copyright 2006: MultiService Forum 7 Industry Impact of GMI 2006 Theoretical-to-Practical Migration –The GMI events are extremely beneficial to both carriers and vendors because they move deployment and interoperability issues out of the theoretical realm into the practical world. –All participants and even observers come away with a much more realistic view of what it will take to build a next-generation network. Relationship Building –GMI 2006 event is as a dress rehearsal for the opening night of what may be the next- generation multi-vendor service delivery platform. Valuable Feedback loop –The GMI creates a tremendous information source that participating companies can feed back into their engineering and product development activities. –Information gleaned from the GMI event can also be fed back into the standards bodies to refine specifications and achieve greater insight to the theoretical portion of the IMS development cycle. Serves collective Interest of Telecommunications Industry –Solving the IMS puzzle, that is moving IMS from a collection of theoretical functional modules to a physical network architecture, is in the interest of the entire industry.

Copyright 2006: MultiService Forum 8 Why Now – Setting the Framework for IMS Service Interoperability

Copyright 2006: MultiService Forum 9 Multicast VOD Internet Video Apps Multi-media Apps Verizon IP/MPLS Network Trunk Gateway Copper Line Gateway Media Gateway Controller Cellular Access POTS Home Subscriber Server (HSS) Service Manager PSTN IP Phone PBX Phone TDM/IP PBX Session Border Controllers Media Server Call Session Control Function (CSCF) Application Servers Web Apps SIP Apps AIN Apps WiFi/ Wireless Broadband Wireline (Enterprise/DSL/FiOS) Broadband Wireless © Verizon 2006 All Rights Reserved; Information contained herein is subject to change without notice Verizon IMS Architecture

Copyright 2006: MultiService Forum 10 Testing Dates: October 16 – 27, 2006 High Capacity QoS Enabled IP Global Network GMI 2006 Host Testing Facilities

Copyright 2006: MultiService Forum 11 MSF R3 Physical Elements

Copyright 2006: MultiService Forum 12 GMI 2006 Physical Scenarios Scenario 1 - Single Domain with nomadic subscribers. Includes both terminal and subscriber nomadicity. Scenario 2 - Single Domain, nomadic subscribers with Value Added Services. Builds upon Scenario 1 adding in SIP and Parlay/OSA applications. Scenario 3 – IMS interconnection between subscribers in the MSF R3 domain and ‘pure’ IMS domain. MSF R3 and IMS appear as peer IMS networks. Scenario 4 – Roaming of subscribers between MSF R3, ‘pure IMS’ and MSF R3 networks. Roaming includes both terminal and subscriber mobility. Scenario 5 – Roaming of subscribers between MSF R3, ‘pure IMS’ and MSF3 networks. Includes both terminal and subscriber mobility. Scenario 6 – Management. Provisioning of Multi Technology Inter-site VPN’s. Value Added Services –VoIP/IMS and fault management.

Copyright 2006: MultiService Forum 13 Scenario 2 – Single Domain, Nomadic Subscribers, Value Added Services

Copyright 2006: MultiService Forum 14 Scenario 3 – IMS Interconnect

Copyright 2006: MultiService Forum 15 Scenario 5 – Roaming with Value Added Services

Copyright 2006: MultiService Forum 16 Scenario 6 - Management Highly distributed architecture requires –Remote Management –Multi Technology/Multi Vendor support –Explosion of Management Data Early NGN Architectures are reliant on custom systems MSF is partnering with management experts in TMF –Will drive open architecture solutions GMI2006 will focus on 3 hot issues –Provisioning of Multi Technology VPNs (Inter-site) –Provisioning of Value Added Services –VoIP/IMS –Fault Management

Copyright 2006: MultiService Forum 17 GMI2006 Summary Moves IMS convergence from theoretical to practical Addresses key interoperability issues before network implementation Provides an industry framework for service interoperability Provides global framework that sets the stage for worldwide adoption of IMS architectures

Copyright 2006: MultiService Forum 18 More Information MSF White Papers - Address the relevance of MSF technology to hot topics in today's switching industry, focusing on how the MSF Architecture works with specific technologies NGN Control Plane Overload and its Management Authors: Ian Jenkins, BT Date: January 2006 Testability in the NGN Authors: Boris Ratner, Spirent Communications; Andy Huckridge, Spirent Communications Date: September 2005 Bandwidth Management in Next Generation Packet Networks Authors: Chris Gallon, Fujitsu; Olov Schelén, Operax Date: August 2005 IMS Reconciliation White Paper Date: May 2005 First drafts Feb 27 th, 2006: QoS & Border Gateways Optimal Media Routing for IMS Roaming