IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: VCC Brief Introduction Date Submitted: September, 18 th, 2005 Presented at IEEE session #10 in Garden Grove Authors or Source(s):Ulises Olvera, Subir Das, Vivek Gupta Abstract: Introduce 3GPP VCC concepts to

IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3

What is VCC? VCC is Voice call continuity between GSM/UMTS CS domain and IMS domain VCC is currently a study group in 3GPP SA2 The working group is currently performing a feasibility study that includes Overall requirements Architectural requirements Evaluation of potential architectural solutions, and Alternative architectures Timeline Complete study by Sept 2005 Complete Specification by Dec 2005 The latest version of the Technical Report (3GPP TR v1.3.0) is available at ftp://ftp.3gpp.org/TSG_SA/WG2_Arch/TSGS2_48_Sophia_Antipolis/Docs/

Call Continuity from IMS VoIP to CS IMS Controlled 3GPP IMS WLAN AN RAN VMSC MGCF IM-MGW MGCF IM-MGW PSTN, another IMS network, PLMN CS domain, etc Internet GSM/UMTS CS Domain IP CAN CCDF CCSF MIH IS CCCF Handover before HO after HO IS Signaling CCCF Signaling

How Fits in VCC ? Some Basic VCC Architectural Requirements How does add value to current solution? Voice call continuity between GSM/UMTS CS domain and IMS By providing link layer intelligence and higher layer information discovery about neighboring networks Automatic detection and connection to available networks (e.g., IMS, CS GSM/UMTS) even when not in voice call Network discovery through Information Service and local triggers End users experience in terms of service disruption should be minimal Can be achieved via local triggers, make before break, proactive handover decision, etc. UE shall be able to monitor IP connectivity access while in CS call and vice-versa Information service can provide knowledge of whether the AP/AR has IP level reachability to the CCCF Voice quality shall be maintainedProvide mechanisms to query QoS from different networks and help determine if acceptable QoS is available or not. Initiation of call may be based on radio/link condition can provide indications for changes in link conditions (link speed, QoS, etc) Real-time and predefined operator control shall be supported Information service ca be used to download predefined policies and real time decisions that can be communicated through the.21 command service

How Fits in VCC? Some Basic VCC AssumptionsHow does add value to current solution? The selection of access network should allow automatic connectivity to UE can allow for automatic switching over to different networks without user intervention based on changes in environment Radio layer protocols shall not be impacted i.e., Call continuity shall not rely upon radio layers that are not supported by 3GPP specifications This should be possible from perspective and enables existing deployments to be used as is. Changes should be restricted to IMS elements and UEs complies with such assumption CS core impacts should be minimal complies with such assumption Existing 3GPP security aspects shall be reused complies with such assumption UE shall be able to transmit and receive simultaneously both in the CS and IMS domains complies with such assumption UE shall be able to register both in CS and IMS domain complies with such assumption

Call Continuity CS to IMS VoIP Original Domain Control 3GPP IMS WLAN AN RAN VMSC MGCF IM-MGW PSTN, another IMS network, PLMN CS domain, etc Handover GSM/UMTS CS Domain IP CAN CCCF MIH IS Internet before HO after HO IS Signaling CCCF Signaling

VCC CS to IMS assisted UE VMSCMGCFI/S-CSCF IM-MGWCCCF/NeDS Other End {IMS} {CS} S-CSCF 2. INVITE ( To: CCCF-PSI URL; Offer UE ) 1. INVITE ( To: CCCF-PSI URL; Offer UE ) 3. UPDATE ( SDP UE ) 200 OK ACK REL Disconnect RLC Release 200 OK 4. BYE ( CS Call ref ) 200 OK Release Comp Bearer Path Interruption CS Bearer IMS Bearer Intermediate SIP message exchange and resource reservation as normal - skipped for brevity MIH User Link_Up MIH_Command (e.g., Handover_Prepare/ Initiate) Link_Down MIH_Command (e.g., Remove link) can play an important role here

VCC IMS to CS assisted Link_Available MIH_Command (e.g., Handover_ Imminent/ Initiate ) can play an important role here VMSCMGCFS-CSCFOther End {IMS} {CS} UE I--CSCF INVITE ( To: DTFCCCF-PSI URL; Offer MGCF ) Update ( SDP MGCF ) 200 OK IAM Setup ( Called #: DTFCCCF PSI ) 200 OK ACM Alerting ANM Connect Call Proceeding BYE ( IMS Call Ref ) 200 OK Bearer Path Interruption IMS Bearer CS Bearer Intermediate SIP message exchange and resource reservation as normal - skipped for brevity. ACK MIH User Link_ Handover_Complete Link_Up MIH_Command (e.g., Link_Information) MIH_Command (e.g., Remove link)

Backup Slides

VCC CS to IMS assisted

VCC CS to IMS assisted