3GPP2 MMD Status for IMS Workshop - draft -

1. 3GPP2 MMD Status for IMS Workshop- draft - Jack Nasielskijackn@qualcomm.com Page 1

2. Outline • IP Multi-media Subsystem (IMS)/ Multi-Media Domain (MMD) • 3GPP/3GPP2 differences • Status of MMD work, current and future • N.B. - MMD is IMS + 3GPP2 Packet Data Subsystem Put figure 2 and figure 4 instead of the last bullet and slide 3, and first bullet of slide 10 Page 2

3. IMS in 3GPP/PP2 The green bubbles are not identical, as pointed out in the next slides. Page 3

4. 3GPP IMS Releases • 3GPP IMS Release 5, 6 complete; Release 7 in progress • IMS Release 5 • IMS Registration, routing and call flows, Security Architecture, Accounting (Offline and Online Charging), Application Server Architecture • IMS Release 6 • Presence, Conferencing, Messaging, Flow based charging (Gx and Rx), Group management, Early IMS (security + IPv4 support), Interworking non-IMS, Service based local policy (Gq interface) • IMS Release 7 • CSI - combination of CS and IMS services (parallel operation of a CS service and an IMS session between the same two users), FBI – IMS over fixed broadband, VCC – Voice Call Continuity, PCC – Policy and Charging Control, Emergency Services • IMS Release 8 • Supplementary Service interoperation with VCC, PS only core network - All-IP Network (AIPN), Enhanced Emergency Calling, Optimal Routing for IP based services, High speed interface for UICC remove Page 4

5. 3GPP2 MMD Releases • 3GPP2 MMD Rev 0, A complete, Rev B, C in progress • MMD Rev 0 • Basic IMS as in Rel 5, SIP/SDP procedures, security, offline charging, service architecture • MMD Rev A • Adds Presence, Conferencing • MMD Rev B • Includes Optimized call flows, Service Based Bearer Control (QoS mappings), VoIP/1x call delivery and handoffs, online charging, messaging • MMD Rev C – not started yet • Roaming, Security, Policy enhancements, content still open Page 5

6. 3GPP/3GPP2 differences • 3GPP IMS and 3GPP2 MMD are very similar except for some differences noted in the next few slides • The differences were defined to support deployment of IMS with 3GPP2 systems. – delete sentence • Access network specific changes • Enhance flexibility • Optimise IMS • It is believed that The differences do not affect interoperability between 3GPP and 3GPP2 systems. • Statement is not verified Page 6

7. IMS Technical Differences (1) • Access Security • 3GPP IMS mandates IPsec between UE and P-CSCF for integrity protection • 3GPP2 allows for P-CSCF and UE to negotiate other security mechanisms using RFC 3329 (like ipsec-ike, tls, digest etc) • 3GPP IMS mandates using AKA for authentication between S-CSCF and UE • 3GPP2 allows for alternate authentication mechanisms like Digest, see S.S0086-B • 3GPP2 did not specify MMD Network Domain Security • There is a new work item begun in July, 2006 to develop IMS security solutions using 2G R-UIMs (i.e. R-UIMs that only support CAVE based protocol, but not AKA). • It is desirable to avoid any conflict with the existing IMS security mechanisms while defining support for 2G R-UIM based IMS security scheme. Page 7

8. IMS Technical Differences (2) • Smart Cards • 3GPP IMS terminals have smart cards (SIM/UICC) • 3GPP2 IMS does not require a smart card • IMS information can be stored in UE or R-UIM. • 3GPP2 now supports UICC + ISIM for operators that choose that method. • P-Access-network-Info • UE includes CDMA specific information in P-Access-network-info • HRPD-VoIP to 1X-CS interworking • Behavior specific to 3GPP2 systems • 3GPP assumed dual-radio UE • 3GPP2 allows architectures with both single-RF and dual-RF • Single radio for HRPD/1x • Dual radio for WLAN/1x Page 8

9. IMS Technical Differences (3) • Temporary Public/Private Identifiers • 3GPP creates temporary Public/Private IDs to support terminals without ISIM application. • MMD Rev 0 (first release of MMD) does not support temporary IDs • MMD Rev A supports temporary IDs • The method of generating these ID’s is different between 3GPP and 3GPP2 • E.212 vs MIN based IMSIs. • Anchored internet access point • In 3GPP, the GGSN is anchored for a given session. • In 3GPP2, the PDSN may change. Page 9

10. IMS Technical Differences (4) • HSS (Home Subscriber Server) vs AAA • In 3GPP2, AAA + databases represent an HSS. – delete or expand (databases=EIR+DSI+subscription profile+network policy rules) • In 3GPP2, HSS is used only for PS domain. • In 3GPP, HSS is used for both PS & CS domains. • P-CSCF Discovery procedures • 3GPP2 supports static configuration in addition to 3GPP defined access agnostic procedures and DHCP for P-CSCF discovery • 3GPP Rel-5 supports P-CSCF discovery through DHCP and PDP context activation. -delete • MMD supports Enhanced-Proxy-SLF in addition to Redirect-SLF defined by 3GPP • IMS Rel 5, 6, 7 roughly equivalent to MMD Rev 0, A, B respectively. - delete Page 10

11. Current Projects in 3GPP2 MMD • X.P0013 MMD Rev B • Service Based Bearer Control (SBBC) • Optimized call flows • Optimize resource reservations to speed session setup • Show QoS procedures in PDSN and RAN • Based on IS-856-A, IS-835-D • AT can pre-configure QoS reservations for SIP and RTP flows • Online Charging • Messaging • X.P0027 Presence • X.P0029 Conferencing • X.P0042 VoIP/1x interworking (voice call continuity) • X.P0048 SMS over IMS • X.P0049 MMD Emergency Calling – this is empty document: delete • WLAN/HRPD VoIP/VoIP handoffs Page 11

12. New Projects in 3GPP2 MMD • Security Enhancements – requirements just briefly discussed, completely open: delete • Policy Enhancements • Roaming • MMD Rev C (under discussion) Page 12

13. Security Enhancements • For both Multi-Media Domain and packet data network security. • Developing security requirements and the security architecture to support the following: • Methods to reuse authentication results to bootstrap keys for SIP and non-SIP applications. • Methods to detect security problems in the network • Methods to remediate problems, whether in network nodes or end-user devices • Ability to update security software on devices when required • Ability to distribute security policies throughout the system. • IETF is developing some of the protocols needed for this. • delete Page 13

14. Policy Enhancements • MMD Rev B defined Service Based Bearer Control (SBBC) which enables an operator apply policy to SIP services, and to provision flow based charging rules at the PDSN. • SBBC provides the mapping between application layer signaling and resource management in the RAN via the Tx/Ty interfaces. SBBC is somewhat limited however, in that the PDSN is the only policy enforcement point. • New proposed work item intends to expand the scope of policy • to include overall coordination of network resource usage (for SIP and non-SIP applications) • to enable policy exchange with other operators for roaming subscribers. Page 14

15. MMD Roaming • Inter-operator roaming architecture and protocols to allow MMD operators to provide services to their customers roaming on other networks. – isn’t this work at requirements level? • Includes IMS and PDS aspects. • The MMD system will provide home operator control of MMD services. It is expected that all bearer traffic is not required to be routed via the home system. This will allow for low latency of real time traffic in the visited system. Page 15

16. IMS Alignment and Evolution • Continue exchanging CRs via company contributions • Is this the agreed way forward? • Baseline agreement for VoIP and other features • Supplementary service specifications • What about this? TISPAN specified, 3GPP takes over • Develop tests for IMS core functions • such as registration and authentication, XDM, Presence, SIP RFCs etc • Ensure interop for IMS clients, internet clients, and legacy PLMN/PSTN devices Page 16

17. Links to MMD Documents • http://www.3gpp2.org/Public_html/specs/index.cfm • ftp://ftp.3gpp2.org/TSGX/Projects Page 17