1. Page 1TTT - May 12, 2003 3GPP IMS Standardization Update Bell Labs Innovations Lucent Technologies Room 9C-229 1960 Lucent Ln. Naperville, IL 60566 E Mail ttowle@lucent.com Lucent Technologies Thomas T. Towle Wireless Standards Development Telephone +1 630 979 7303 Facsimile +1 630 713 1921

2. Page 2TTT - May 12, 2003 Presentation Overview Status of IMS Release 5  List of Specifications/owners  Development status Content of Release 6 (IMS related work)  List of work areas/owners  Update on current status  Guess at schedule IMS Commonality & Interoperability  What is included  How topic is being addressed WLAN Interworking  3GPP Interworking scenarios  Current Status

3. Page 3TTT - May 12, 2003 IMS R5 Core Specifications IMS Stage-2/3  3GPP TS 23.218: IP Multimedia (IM) session handling; IM call model (CN1)  3GPP TS 23.228: IP Multimedia Subsystem (IMS); Stage 2 (SA2)  3GPP TS 24.229: IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3 (CN1)  3GPP TS 29.228: IP Multimedia (IM) Subsystem Cx Interface; Signalling flows and message contents (CN4)  3GPP TS 29.229: Cx Interface based on the Diameter protocol; Protocol details (CN4)  3GPP TS 29.328: IP Multimedia Subsystem (IMS) Sh Interface; Signalling flows and message contents (CN4)  3GPP TS 29.329: Sh interface based on the Diameter protocol; Protocol details (CN4)

4. Page 4TTT - May 12, 2003 IMS R5 Supporting Specifications 3GPP requirements and architecture for IMS  3GPP TS 22.228: IP multimedia subsystem; Stage 1 (SA1)  3GPP TS 23.002: Network Architecture (SA2)  3GPP TS 23.003: Numbering, addressing, and identification (CN4)  3GPP TS 23.008: Organization of subscriber data (CN4)  3GPP TS 23.221: Architectural requirements (SA2)  3GPP TS 27.060: Mobile Station (MS) supporting Packet Switched Services (CN3) 3GPP QoS management and Service Based Local Policy for IMS  3GPP TS 23.207: End-to-end QoS Concepts and Architecture (SA2)  3GPP TS 29.207: Policy Control over Go Interface (CN3)  3GPP TS 29.208: End-to-end Quality of Service (QoS) signalling flows (CN3)

5. Page 5TTT - May 12, 2003 IMS R5 Supporting Specifications (Continued) 3GPP Charging and Billing for IMS  3GPP TS 32.200: Telecommunications management; Charging management; Charging principles (SA5)  3GPP TS 32.225: Telecommunications management; Charging management; Charging data description for the IMS domain (SA5) 3GPP Security for IMS  3GPP TS 33.203: 3G security; Access security for IP-based services (SA3)  3GPP TS 33.210: 3G security; Network Domain Security (NDS); IP network layer security (SA3) UMTS/GPRS related procedures for IMS  3GPP TS 24.228: Signalling flows for the IP multimedia call control based on SIP and SDP; Stage 3 (CN1) CAMEL Support for IMS  3GPP TS 23.278: Customised Applications for Mobile network Enhanced Logic (CAMEL) - IP Multimedia System (IMS) interworking; Stage 2  3GPP TS 29.278: Customised Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification for IP Multimedia Subsystems (IMS)

6. Page 6TTT - May 12, 2003 Status of Release 5 IMS Specifications All specifications “frozen” as of September 2002 Support for basic IMS operation  Support for various SIP methods including REGISTER, INVITE, UPDATE, SUBSCRIBE/NOTIFY, etc.  Support for fundamental capabilities including Authentication/Authorization, MO/MT sessions, Service Based Local Policy, Charging, etc.  Not complete in areas of Interworking with PSTN/Internet, MGW/MRFP control, Emergency Services, and some others. Level of Change Requests  Low for most as of January 2003  Moderate activity in IMS Charging Stage-3 in March 2003  Expect high activity in IMS SIP Stage-3 till June 2003

7. Page 7TTT - May 12, 2003 Work Areas for Release 6 - IMS Core Related Commonality and Interoperability – support for use of the IMS core by other access technologies (SA2, CN1) IMS Local Services – support for access to services in visited network (SA2, CN1) IMS to PS Interworking – support for interworking with IP endpoints including IPv4/IPv6 interworking, SIP, transcoding, … (CN3) IMS to CS Interworking – support for SIP/ISUP interworking and CS roaming scenarios (CN3) IMS Conferencing – support for IMS based conference provision and control (SA2, CN1) SIP Capabilities Enhancements – support for enhanced SIP capabilities such as forking (SA2, CN1) IMS Subscriptions and Access Scenarios – requirements on various operator scenarios for IMS deployment (SA1)

8. Page 8TTT - May 12, 2003 Work Areas for Release 6 – Other IMS Related Packet Based Emergency Services – support for emergency service access via packet networks (SA1, SA2, CN1) QoS and Service Based Local Policy Enhancements – support for Gq interface and non-IMS applications (SA2, CN3) IMS Group Management – support for group-enabled services e.g., chat (SA1, SA2, CN1) IMS Messaging – support for immediate and session based messaging (SA1, SA2, CN1) Bearer Level Charging – support for IP flow based accounting (SA2, SA5) WLAN Interworking – support for WLAN (SA1, SA2, SA3, CN1, CN4) Presence Capability – support for presence (SA1, SA2, CN1) Generic User Profile – support for user data management (SA1, SA2, CN4, T2)

9. Page 9TTT - May 12, 2003 Status of Release 6 IMS Related Work Stage-1 CRs mostly complete (SA1)  Initial work on IMS Subscriptions and Access Scenarios Stage-2 Documents or CRs in progress (SA2)  Commonality & Interoperability 23.228 re-org agreed, additional work on TR in progress (June)  Some CRs received on local services, messaging, conferencing, Group Management and SIP enhancements (June)  Emergency services being worked in separate TR – expect CRs in May (June)  QoS and SBLP study in progress, CRs later (Sept.)  Bearer charging TR in progress (Sept.)  Presence capability (mostly stable)  Generic User Profile (June)  WLAN Interworking (June) Stage-3 Documents or CRs (some) waiting for Stage-2 stability  IMS Conferencing started, Presence in progress (CN1)  CS and PS interworking in progress (CN3)  MGCF-MGW, MRFC-MRFP interfaces in progress (CN4) Work plan currently targeted for YE-2003 freeze (optimistic?)

10. Page 10TTT - May 12, 2003 IMS Commonality and Interoperability What the work item includes  Improve commonality between IMS systems from 3GPP, 3GPP2  Ensure users of 3GPP IMS can interoperate with others such as 3GPP2 MMD How commonality is being addressed  Core set of specifications identified for common IMS (see slide 3) - complete  Generic terminology changes adopted - complete  PCF  PDF  GPRS  IP Connectivity Access Network  PDP Context  IP-CAN Bearer  Documents restructured with “Common IMS” sections – in process  Study report being developed to look into additional areas – in process  Charging & Billing  Security  Service based policy control  IMS Boundary reference points  IP Connectivity Access Network Requirements Interoperability work is just getting underway (CN3)

11. Page 11TTT - May 12, 2003 WLAN Interworking Scenarios 6 Interworking Scenarios Identified Scenario 1 – Common billing and customer care  This is the simplest scheme of 3GPP -WLAN interworking. The connection between the WLAN and the 3GPP system is that there is a single customer relationship. The customer receives one bill and integrated customer care allows for a simplified service offering from both the operator and the subscriber’s perspective. The security level of the two systems may be independent.  This scenario does not pose any new requirements on 3GPP. Scenario 2 – 3GPP system based access control and charging  This is the scenario where authentication, authorization and accounting are provided by the 3GPP system. This may also provide means for the operator to charge access in a consistent manner over the two platforms.  No requirements are put upon the set of services to be offered in the WLAN part beyond those inherently offered by being addressable in an IP network Scenario 3 – Access to 3GPP system PS based services  The goal of this scenario is to allow the operator to extend 3GPP system Packet Switching based services to the WLAN. These services may include, for example, IMS based services, location based services, instant messaging, presence based services.  a Service continuity between the 3GPP system part and the WLAN part is not required

12. Page 12TTT - May 12, 2003 WLAN Interworking Scenarios Continued Scenario 4 – Service continuity  The goal of this scenario is to allow the services supported in Scenario 3 to survive a change of access between WLAN and 3GPP systems. The change of access may be noticeable to the user, but there will be no need for the user to re- establish the service. There may be a change in service quality as a consequence of the transition between systems due to the varying capabilities and characteristics of the access technologies and their associated networks. It is also possible that some services may not survive, as the continuing network may not support an equivalent service. Scenario 5 – Seamless service provision  a The goal of this scenario is to provide seamless service continuity, as defined in between the access technologies, for the services supported in Scenario 3.  By seamless service continuity is meant minimizing aspects such as data loss and break time during the switch between access technologies. Scenario 6 – Access to 3GPP CS services  This scenario allows access to services provided by the entities of the 3GPP Circuit Switched Core Network over WLAN. This scenario does not imply any circuit-switched type of characteristics to be included into WLAN.

13. Page 13TTT - May 12, 2003 WLAN Interworking Status Stage 1 Complete Stage 2 for Scenario 2 ~complete  Target Release 6 Stage 2 for Scenario 3 in progress  Target Release 6 Stage 2 for Scenarios 4 and 5 in very early stage (Release 7) Scenario 6 - No use cases have been identified, very low priority

14. Page 14TTT - May 12, 2003 Thank You