2-4 October 2007Kigali, Rwanda

ITU Forum “Bridging the ICT standardization &

development gap”

3GPP and ITU-T Cooperation and IMS as a Core Element of NGN

John Visser, P.Eng.,Chairman, ITU-T SG 19 / Nortel

Acknowledgement: Stephen HayesChair 3GPP TSG-SA / Ericsson

2-4 October 2007Kigali, Rwanda

Outline

History of IMSIMS Adoption outside of 3GPPPreventing IMS FragmentationNext Steps for IMSConclusions

2-4 October 2007Kigali, Rwanda

Why 3GPP Developed IMS (1/2)

Development of IMS started around 2000

Term IMS was not coined until laterInput from 3G.IP and MWIF

Needed services to take advantage of higher bandwidths becoming availableIP transport becoming prevalent

2-4 October 2007Kigali, Rwanda

Why 3GPP Developed IMS (2/2)

SIP/SDP existed but was inadequate by itself

Insufficient operator controlNo standardized charging mechanismsMany regulatory requirements not met

Originally not viewed as a circuit switched replacement

2-4 October 2007Kigali, Rwanda

IMS Principles

IP based transportTailored for multimedia services

Home control of services Allows operator differentiationServices the same when roaming

Access independentSecurity at 3G levelRoaming fully supported

2-4 October 2007Kigali, Rwanda

3GPP IMS Timeline

3GPP specified IMS as part of Rel 5 with improvements in Rel 63GPP specified UMA as part of Rel 63GPP added support for I-WLAN in Rel 63GPP is enhanced IMS to support fixed broadband in Rel 73GPP added robustness enhancements for multimedia in Rel 73GPP added Voice Call Continuity in Rel 7

1999 2000 2001 2002 2003 2004 2005 2006

Rel 99 Rel 4 Rel 5 Rel 6 Rel 7

2007

2-4 October 2007Kigali, Rwanda

IMS

I-CSCF

I-CSCF

P-CSCF S-CSCFMw

HSS

Cx

Cx

Other IP/IMS network

Mm3GPP Cellular Access Network

3GPP GPRS

3GPP2 Cellular Access Network

3GPP2 MDN

WLAN Access Network

3GPP WLANinterworking

DSL Broadband Access Network

TISPAN

Gi,Go,Gx,GyR5

R6R6

R7

Cable Broadband Access Network

Cablelabs

R7

IMS adoption outside 3GPP: now being used for many access types

2-4 October 2007Kigali, Rwanda

Key Rationales forTransitioning to IMS

Mobile Operators – Deploy novel services to increase usageFixed Operators – Capex/Opex reduction and competitive service offeringsIntegrated Operators – Service continuity across domains

2-4 October 2007Kigali, Rwanda

Preventing IMS Fragmentation: IMS Variations Grow

IMS has been adopted by other SDOs as the basis of their solutions, but fragmentation still exists:

Problem: Different requirements and usage scenarios from different industry segmentsProblem: Unnecessary deviations in functions related to IMSProblem: Different SDOs interpret the base IMS Standards differently

2-4 October 2007Kigali, Rwanda

IMS Collaboration Workshops (1/2)

April 3-4, 2002 (Toronto, Canada) Agreed 3GPP2 would reuse 3GPP IMSAgreement on common IMS terminology

March 30-31, 2005 (Washington, DC)Agreement that TISPAN would reference 3GPP IMS specsAgreement to incorporate IMS changes into Rel 7Agreement on early production of TISPAN required specifications

2-4 October 2007Kigali, Rwanda

IMS Collaboration Workshops (2/2)

Sept 28-29, 2006 (Palm Springs, California)

Agreement to create open IMS requirements groupAgreement on submission process for Cablelabs enhancements

2-4 October 2007Kigali, Rwanda

3GPP Initiative: Open IMS

Goal: Provide a single “place” for industry segments to meet to discuss and standardize IMS requirementsSolution: 3GPP will host the open IMS group.SA1 (the 3GPP requirements group) has been re-scoped to address generic requirements (not only mobile requirements)

2-4 October 2007Kigali, Rwanda

3GPP Initiative: Open IMS

SA1:New Charter to cover requirements from any industry segmentNew ElectionsSpecial Fairness Rules (in process of being specified)Participation requires joining 3GPP (due to IPR concerns)http://www.3gpp.org/ftp/Op/OP_17/DOCS/OP17_07.zip

2-4 October 2007Kigali, Rwanda

3GPP Initiative: Common IMS

Goal: Extend the Scope of work done in 3GPP to include many areas related to IMSSolution: 3GPP Commits to address needs in areas related to IMS.

(See next slides for areas)http://www.3gpp.org/ftp/Op/OP_17/DOCS/OP17_05.zip

2-4 October 2007Kigali, Rwanda

Common IMS Scope

Core IMS

Common IMS svcs

Rsrc & AdmissionNtwk AttachIMS i/f to Web svcsIMS O&MIMS Security

Ent i/f to IMSIMS Testing

Common IMS

Candidate areas for scope of Common IMS

IMS LIIMS Charging

IMS Emulation

Res i/f to IMS

Fully under 3GPPPartially under 3GPP

Not under 3GPP

2-4 October 2007Kigali, Rwanda

Progress so far

SA1 rechartered as new generic requirements group; 1st meeting heldJoint meeting: TISPAN WG1 and SA1 to transfer TISPAN deliverables.Requirements for fixed MM services transferred from TISPAN to 3GPPDiscussions starting with 3GPP2 on merging 3GPP2 IMS work back into 3GPP

2-4 October 2007Kigali, Rwanda

Next steps for 3GPP

Integrate variations from other SDOs into 3GPP IMS (and related common IMS areas)Continue work on CS to IMS service integrationEnsure all regulatory requirements met

2-4 October 2007Kigali, Rwanda

Next Steps for ITU-T and 3GPP

Concrete and fruitful interchange of views on cooperation, exchange of information, alignment of work plans and release datesInvestigating possibilities for closer coupling of 3GPP and ITU-T NGN-GSI

Target: globally consistent IMS specsCo-located meetings?3GPP under ITU-T umbrella?

2-4 October 2007Kigali, Rwanda

Summary and Conclusions (1/2)

IMS under development in 3GPP since 2000Originally viewed as a way to develop value added services using IP technologyWide acceptance of IMS as basis for multimedia IP networks

2-4 October 2007Kigali, Rwanda

Summary and Conclusions (2/2)

Open IMS and Common IMS are mechanisms to avoid IMS fragmentation; appear to be succeeding3GPP fully committed to ensure IMS meets the needs of all industry segmentsITU-T & 3GPP investigating approaches for closer integration in support of globally consistent IMS specs

2-4 October 2007Kigali, Rwanda

Thank you for your attention!

John Visser, P.Eng.ITU-T: Chairman, SG 19

Mobile telecommunications networks

Nortel: CTO - International Wireless Standards

Email: jvisser@nortel.comTel: +1 613 763 7028Mob: +1 613 276 6096

Acknowledgement:Stephen HayesChairman, 3GPP SA

Email:stephen.hayes@ericsson.com

2-4 October 2007Kigali, Rwanda

Additional Details

2-4 October 2007Kigali, Rwanda

Common IMS Recommendations*(1/4)

Common IMS Services: Yes, but inclusion decided on case-by-case basis

IMS Based Emulation: NoResource and Admission Control

Yes for i/f used towards IMSNo for other parts, subject to further analysis

*See full report for additional information and conditions on each recommendation

2-4 October 2007Kigali, Rwanda

Common IMS Recommendations(2/4)

Network AttachmentYes for i/f used towards IMSNo for other parts, subject to further analysis

Web Services Interface for IMSYes

Operations & Maintenance for IMSYes, for O&M of functions included in Common IMS

2-4 October 2007Kigali, Rwanda

Common IMS Recommendations (3/4)

Security for IMSYes, see report for specific functions

Residential Networks Interface for IMSYes, once requirements available

Enterprise Networks Interface for IMSYes, once requirements available

Testing for IMSYes, for testing of functions included in Common IMS

2-4 October 2007Kigali, Rwanda

Common IMS Recommendations (4/4)

Lawful Intercept of IMSYes, for intercept of functions included in Common IMSNo, for regional aspects

Charging Interface towards IMSYes

2-4 October 2007Kigali, Rwanda

IMS Functionality Timeframes

Cellular Operators

Wireline Operators

Cable Operators

Basic IMS 3GPP R5 3GPP R6 (WLAN)

3GPP R7

Robust Multimedia

3GPP R7 3GPP R6(TISPAN R1)

3GPP R7

Transition Services

3GPP R7 (VCC, CSI)

? ?

Integrated Services

3GPP R8 3GPP R8 ?