1. 1 An Analysis of 3GPP and 3GPP2 Requirements for Common IMS January 2008 Source:Aleksandar M. Gogic, Chair TSG-S WG-1

2. 2 Introduction Goal: Alignment of requirements related to Common IMS In short term, ensure consistency of capabilities already or nearly in Stage 2/3 Additional alignment of approved existing 3GPP2 requirements to take place within SA-1 SA-1 new charter - responsible for the development of Stage 1s for further evolution of Common IMS Detailed analysis of broader set of requirements is pending in SA-1

3. 3 Broad Overview There is generally no exact equivalence between a 3GPP and a 3GPP2 requirements specs [change to more positive sounding] Broadly, IMS related requirements in 3GPP2 and 3GPP are listed in the table on next slide For the moment, we focus on several key IMS capabilities, including: –VoIP and other Multimedia Conversational Services (MCS) [3GPP term is MM Telephony] –VoIP/MCS Supplementary Services –Emergency Services in IMS Many other aspects of Common IMS will be subject to refinement of requirements taking place primarily in TSG SA-1

4. 4 Requirements Specifications

5. 5 VoIP/MCS & Supplementary Services - Status 3GPP2 S.P0125-0 VoIP Supplementary Services –Completing V&V January 2008 –Publication expected March 2008 –Revision 0 contains a set of supplementary services considered essential before VoIP services can be commercially launched –Revision A to follow (some contributions submitted) S.R0106 Packet-Switched Video Telephony –Revision 0 published in April 2007 –Revision A expected to be published in 1Q’08 TS 22.173, IMS Multimedia Telephony Service and Supplementary Services - Stage 1 –Considerable progress in the latest version 8.1.0 (December 2007)

6. 6 Adjustments of TS 22.173 TS 22.173 can serve the purpose of Common IMS requirements TS 22.173 expected to expand and include more services –Many of the services defined in 3GPP and 3GPP2 are common, albeit some have different names (see next slide) –Services identified in 3GPP2 as essential should be included S.P0125-A to include more services –MAH – Mobile Access Hunting is proposed –Video Mail on the drawing board To assure continuity, these additional services should be captured in the on-going work in 3GPP SA-1 Upon agreement on the above points, editorial work needed to ensure integrity, self-consistency, and compatibility with 3GPP and 3GPP2. TS 22.173 could benefit if made into multi-part –Uniform structure, as in the CS equivalent (TS 22.08X, TS 22.09X), and S.P0125 (this can be done in future releases)

7. 7 Supplementary Services in Common

8. 8 3GPP2 Services with No Current 3GPP Equivalents Notes (1)See Section 7.12 in TS 22.228 (Support for Local Numbers in the IMS), and discussion of LCI – Local Call Indicator (2)See CDIV discussion on previous slides (3)ACR is defined in 3GPP, however, 3GPP2 considers it one aspect of a broader ICR service

9. 9 3GPP Services with No Current 3GPP2 Equivalents Notes (1)3GPP2 CS version S.R0012 contains description of “Rejection of Undesired Annoying Calls”, published Dec. 1999 (2)See CDIV discussion on previous slides

10. 10 Proposed Disposition Plan 3GPP (TS 22.173) Only Services: Keep in Common IMS –Includes CFNL, CD, CFN, CFNRc, CDIVN 3GPP2 (S.P0125) Only Services: Include in Common IMS Study CFD and possibly include in Common IMS (there may be an equivalent under a different label) Consolidate ICR/ACR Investigate LCI applicability for AD/SC, and decide treatment accordingly Perform Editorial Consolidation in TSG SA-1: –Terminology alignment –Document structure alignment –Verification of interactions, etc.

11. 11 Emergency Services - Status 3GPP TS 22.101 v8.7.0 “Service Principles” – Section 10 contains requirements for emergency services 3GPP TS 23.167 “IMS Emergency Sessions” 3GPP2 S.P0115-0 v2.0 “All-IP Network Emergency Call Support - Stage 1 Requirements” – published Oct.’07 X.P0049 – Stage 2/3 for VoIP Emergency Call Support –Projected to be published in 1Q’08 –Largely based on 3GPP TS 23.167 –Based on this, it is expected that there is generally equivalence of IMS-based Emergency Services between 3GPP and 3GPP2 in current releases –However, S.P0115 contains additional requirements which should be incorporated into Common IMS

12. 12 Disposition of Other 3GPP2 Requirements SA-1 should be asked to review and decide on disposition of S.P0115 initially, followed by other 3GPP2 requirements of relevance to Common IMS, with the goal to close any gaps (examples below) S.R0058-0: IP Multimedia Domain SRD IPv4 and IPv6 Support: See Section 5.14 S.R0121-0: Network Evolution SRD Multiple IP address assignment to a UE and simultaneous use: See section 5.2.15. S.R0120-0: Enhanced Policy SRD Numerous Requirements

13. 13 Proposed Next Steps Tentatively agree on the planned disposition in the Puerto Vallarta Workshop Validate/ratify Puerto Vallarta agreements in 3GPP and 3GPP2 3GPP TSG SA-1: Proceed with initial set of CRs on TS 22.173, 22.228 and 22.101 3GPP SA-1: Proceed to complete other tasks related to Common IMS requirements consolidation 3GPP2 TSG-S WG-1: Assist in completion of above tasks, as necessary 3GPP2 TSG-S: Validate completion of consolidated Common IMS requirements