GMI 2006 Carrier-Driven Interoperability February 2006

GMI 2006Carrier-Driven Interoperability

February 2006

Copyright 2006: MultiService Forum 2

MSF In The Value Chain


MSF Principal Members - 2006


MSF Framework for Collaboration

• Coherent Big Picture

• Physical Scenarios

• Closing the options

• Filling the gaps

• Test Specifications

• Protocol Interoperability Events

• Network Inter-operability Events


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


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


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.

Richard M Williams

bullets from Joe observations


Why Now – Setting the Framework for IMS Service Interoperability

Service Provider A MSF R3

Service Provider B Pure IMS

Service Provider C MSF R3

Shared Interconnection

Network

Peer to Peer Interconnects

Service Provider D Other Non-IMS

Network e.g. packet cable or ITSP’s

SIP Profile A

Profile

A

SIP Profile C

SIP Profile B

SIP

Pro

file B


MulticastVOD

Internet

Video Apps

Multi-media Apps

Verizon IP/MPLS NetworkTrunk

Gateway

Copper

LineGateway

Media GatewayController

CellularAccess

POTS

Home Subscriber Server (HSS)

ServiceManager

PSTN

IP Phone

IP Phone PBX Phone

TDM/IPPBX

Session Border Controllers

Media Server

Call SessionControl Function (CSCF)

Application Servers

Web AppsSIP Apps

AIN Apps

WiFi/Wireless

Wireless

Broadband Wireline(Enterprise/DSL/FiOS)

Broadband Wireless

© Verizon 2006 All Rights Reserved; Information contained herein is subject to change without notice

VerizonIMS Architecture


Testing Dates: October 16 – 27, 2006

High Capacity QoS Enabled

IP Global Network

GMI 2006 Host Testing Facilities


Bandwidth Manager

Static Call Agent

Routing Call Agent

Routing Call Agent

Dynamic Call Agent

Dynamic Call Agent

Access Gateway

SGB-NESGB-NE

SGB-NESGB-NE

P-CSCF

P-CSCF

R3 End PointSIP (IMS) Fixed Terminal

SIP (IMS) Fixed Terminal

SIP (IMS) Nomadic End Point

S-CSCF

I-CSCF

Home Subscriber

ServerMedia Server

SIP Applications

ServerParlay GW / OSA SCS

Parlay Applications

Service Broker

SCIM MSF R3

SGB-NCSGB-NC

MSF R3 Physical Elements


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.


Scenario 2 – Single Domain, Nomadic Subscribers, Value Added Services

Bandwidth Manager

Static Call Agent

Dynamic Call Agent - A

Routing Call Agent

Routing Call Agent Dynamic Call

Agent - BDynamic Call

Agent - B

Access Gateway

SGB-NESGB-NE

SGB-NESGB-NE

P-CSCF

P-CSCF

R3 End PointSIP (IMS) Fixed Terminal - A

SIP (IMS) Fixed Terminal - B


S-CSCF

S-CSCF

I-CSCF

Home Subscriber

Server

Media Server

SIP Applications

Server

Parlay Gateway

Parlay Applications

ServerService Broker

SCIM


Scenario 3 – IMS Interconnect

Bandwidth Manager

Static Call Agent

Dynamic Call Agent

Routing Call Agent

Routing Call Agent

Access Gateway

SGB-NESGB-NE P-CSCF

R3 End PointSIP (IMS) Fixed Terminal


S-CSCF

I-CSCF

Home Subscriber

Server

SBG-NC IMS Network

SIP (IMS) End Point


Dynamic Call Agent

Routing Call Agent

Routing Call Agent

SGB-NESGB-NE P-CSCF


S-CSCF

I-CSCF

Home Subscriber

Server

SBG-NC

IMS Network

MSF R3 network A

MSF R3 Network B


Media Server

SIP Applications

Server

Parlay Gateway

Parlay Applications

Server


Scenario 5 – Roaming with Value Added Services


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


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


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 ManagementAuthors: Ian Jenkins, BTDate: January 2006

• Testability in the NGNAuthors: Boris Ratner, Spirent Communications; Andy Huckridge, Spirent CommunicationsDate: September 2005

• Bandwidth Management in Next Generation Packet NetworksAuthors: Chris Gallon, Fujitsu; Olov Schelén, OperaxDate: August 2005

• IMS Reconciliation White Paper

Date: May 2005 • First drafts Feb 27th, 2006:

• QoS & Border Gateways

• Optimal Media Routing for IMS Roaming

Documents

GMI 2006 Carrier-Driven Interoperability February 2006