4. US VoWLAN/Cellular Dual-Mode Users, 2005-2010 (Millions) Because of increased acceptance of standard cellular operation and continued increases in wireless usage where landline phones are available. Dual-mode adoption and implementation will be slower than some other industry predictions. Integrated VoWLAN/Cellular dual-mode users will grow at a CAGR of over 140 percent per year until 2010, as shown above. This will result in 9 million handsets in service. Source – Insight Research September 2005
5.
6. Wireless Integration – Voice Over Wi-Fi (VoWiFi) VoWiFi will provide a viable, low cost alternative to traditional cellular networks for roaming. Wi-Fi also promises more reliable indoor coverage and higher voice quality than traditional cellular solutions. In addition, VoWiFi may spawn a tremendous amount of new converged application development by extending enterprise applications to mobile workers and enriching those applications with new capabilities like location, presence and messaging. There are a number of high-profile announcements concerning VoWiFi deployment in large enterprise environments like distribution and warehousing centers, hospitals, and college campuses. Many of the current deployments involve integration with the enterprise PBX, whether the PBX is an IP PBX , or a traditional PBX. One method of integrating with a traditional PBX is to use a VoWiFi gateway which supports most of the leading legacy PBX vendors. Integration with the PBX allows calls to be placed to and received from the PSTN, and also supports the PBX features such as call forwarding, messaging, and conference calling. A major drawback of VoWiFi is that it still tethers the user to the wireless LAN, at least for the duration of a call or session. Furthermore, large campus environments with dead zones where the WLAN is not available may result in missed or dropped calls. For those workers in professions that are the leading candidates for VoWiFi, such as medical professionals, sales people, plant managers and other highly mobile workers, this lack of continuous coverage could stymie their acceptance of the technology. FMC No Spin Zone
7. Dual-mode CDMA – Wi-Fi Handsets Deploying a Wi-Fi/Cellular roaming solution requires dual-mode handsets that support both VoWiFi as well as cellular, and a gateway that sits in the core of the carrier’s network. The gateway connects to the mobile switching center for cellular calls, and connects to the data network for WLAN calls. The gateway manages subscriber access and handoff . As the subscriber moves within range of a wireless access point, the gateway authorizes the subscriber’s access and all network services – both voice and data – are delivered over the WLAN. When the subscriber moves outside of coverage of the current WLAN, the gateway seamlessly switches control over to another WLAN or the cellular network if an authorized WLAN is not available. Multiple vendors working on the gateways include Bridgeport with their NomadicONE, Kineto with their INC-5501, NewStep with their Converged Services Node as well as the major equipment manufacturers such as Lucent and Nortel. Several handset manufacturers have announced devices that will support roaming between cellular and Wi-Fi networks , although some are at least initially intended for roaming of data sessions. Nokia, the world’s largest handset maker is working on the Communicator 9500, which will be able to use Cisco’s Aironet access points. The Communicator 9500 is expected to be available by the end of the year. Motorola has also announced it is working on a dual-mode handset, as have NEC, NTT DoCoMo and others. FMC No Spin Zone
8. Deployment Challenges In addition to the introduction of the network gateways and dual mode handsets, there are a number of technical and operational issues that must be addressed in order for VoWiFi/cellular roaming to become a seamless and viable means of communication. First, the WLAN networks must provide the proper bandwidth and QoS to support VoWiFi deployments . Of course, QoS is an issue for VoWiFi networks even if roaming is present; however, if not addressed adequately the problem could be exacerbated when support for roaming leads to increased acceptance and use of VoWiFi. Security and privacy are other big issues that need a great deal of attention . This is a topic, which has yet to be dealt with even in traditional, wired VoIP implementations. Using wireless networks for the transmittal of sensitive voice and data increases the potential for risk dramatically. Another big hurdle is billing for hybrid VoWiFi/cellular roaming , especially in business models where carriers will charge (perhaps at a discounted price per minute) for VoIP minutes as well as for the cellular minutes. Gateway systems should be able to cut billing records for the VoIP calls, but inter-carrier settlement will have to be worked out when multiple carriers are involved. How to handle E911 calls from a roaming user is yet another issue that must be solved. Potentially, the biggest inhibitor to the success of Wi-Fi/Cellular roaming may be the wireless carriers themselves. After all, why would carriers want to provide a technology that would allow their subscribers to seamlessly roam from their revenue generating networks to free or reduced-cost networks ? Several possible business models exist. The most obvious is one in which the cellular carrier offers a plan in which subscribers can roam from their cellular network to Wi-Fi, with reduced pricing for minutes used on the WLAN . After all, it costs carriers much less to deliver service over the free, unlicensed spectrum and reduces congestion in the existing cellular network. FMC No Spin Zone
9. To Achieve Truly Seamless FMC, There Are Several Technical And Product/Service Approaches That Differ Primarily In Who Controls The Establishment Of Voice Calls Or Other Multimedia Sessions . In The Case Of Voice Calls (With Multimedia Operating Similarly), Some Of The Alternatives Are: • Mobile Operator Control: The Mobile Operator Provides Call Control For Its Dual-mode (Third-generation [3G] Cellular, WLAN) Phones, Using The Enterprise And Fixed Operator Networks Only As IP Transport Conduits For Call Control And Media Traffic. • Fixed Operator Control: The Fixed Operator Provides Call Control For Voice Over Ip (VoIP) Clients Running On Mobile Virtual Network Operator (Mvno) Dual-mode Phones, Using The Enterprise And Mobile Operator/Mvno Networks Only As IP Transport Conduits For Call Control And Media Traffic. • Enterprise Control: The Enterprise's IP-PBX Provides Call Control For VoIP Client Software Running On Dualmode Personal Digital Assistant (Pda)/Smartphones, Using The Fixed And Mobile Operator Networks Only As IP Transport Conduits For Call Control And Media Traffic. FMC No Spin Zone
10. VoWiFi/Cellular as a Competitive Differentiator Carriers may even offer those minutes for free and consider it a competitive differentiator . Or, they can capitalize on the opportunity to steal more customers away from landline carriers. Today a growing number of subscribers prefer to use their mobile phones in the home or office, anyway, as they become attached not only to the mobility it provides but also the convenience of having a single number where they can always be reached, being able to click to call any of the numbers in their contact list and missed call logs. Another compelling business model for cellular carriers involves the ability to facilitate adoption of new, higher bandwidth services. Users may be more likely to take advantage of services such as real-time video and downloading of rich content over the faster WLAN, and once accustomed to the services use them even when the WLAN is not available. There is another technology on the near horizon that offers additional capability. The 802.16 standards “WiMax” is similar to Wi-Fi, except that its range is slated to be about 25-30 miles, versus Wi-Fi’s couple of hundred feet. WiMax could eventually compete with 3G, or become a complimentary offering. FMC No Spin Zone
11. A clear trend is emerging in the form of fixed and mobile telephony convergence (FMC). The aim is to provide both services with a single phone, which could switch between networks ad hoc . Typically, these services rely on Dual Mode Handsets, where the customers' mobile terminal can support both the wide-area (cellular) access and the local-area technology. Historically Digital Enhanced Cordless Telecommunications (DECT) and Bluetooth have been used locally, although there is a clear trend towards WiFi . One example of this convergence is the BT Fusion offer in UK, where British Telecom offers a Vodafone handset capable of making calls through the ADSL line via a local wireless connection (in trials and early launch this was bluetooth but the product is now transitioning to using WiFi. Other examples are provided in France with wifi connectivity around the base station, by the BeautifulPhone from neuf cegetel by the means of a QTek 8300 or Home Zone from Wanadoo with a Nokia handset. Free (French ISP) develops a wifi mesh network of HD freeboxes to be used to provide mobile telephony and compete with traditional cellular operators. The Generic Access Network (or GAN) is a standard roaming system between WLANs and WWANs . Among the first handsets capable of this switching are the Nokia E series , which will be used by the British operator Truphone starting its service in may 2006. [1] . GAN is the name formally used by 3GPP but the technology is also known as UMA and was first developed by Kineto . At the end of the nineties, some dual mode DECT /GAP and GSM services were envisionned. In the UK, BT Cellnet launched its OnePhone offer in 1999. Ericsson and Sagem have produced a few handset models, and Ascom resold some Ericsson units. Those offers have not taken any sufficient ground and have been stopped. Six companies, British Telecom , NTT , Rogers Wireless , Brasil Telecom , Korea Telecom and Swisscom have formed the Fixed-Mobile Convergence Alliance (which as of January 2007 has 26 members) with the purpose to encourage the seamless integration of mobile and fixed-line telephone services. An alternative approach to achieve similar benefits is that of femtocells FMC According To WIKIPEDIA
33. Example 3GPP IMS Registration through WLAN DHCP AP PDG P-CSCF AAA HSS UE 1. WLAN association at L1/2 2. Access Authentication at AAA server 4. Retrieve PDG address 5. Establish tunnel to PDG 6. Obtain remote IP address and discover P-CSCF 7. Set-up security association between UE and P-CSCF 8. IMS registration and session set-up DNS S-CSCF HSS 3. Obtain local IP address from WLAN DHCP DNS WLAN access network Mobile core network
34. IP BB Voice Seamless Handover Comparisons - Currently DSLAM 802.11 WiFi (@home/ public) ISN (BRAS) DSLAM 802.11 WiFi (@home/ public) ISN (BRAS) MGW Voice ”non-moving leg” can be kept unchanged 1. CS voice <–> UMA HOs: 2. CS voice <–> Current VoIP HOs: BSC/ RNC MSC BSC/ RNC MSC UNC BSC/ RNC MSC BSC/ RNC MSC CPS Two completely separate voice call e2e set-ups are required
37. Voice Call Handover Service Evolution A possible evolution approach is to divide voice call handover service architectures into three architectural phases: A first phase based on existing and deployed standards. A second phase based on existing, but not-yet-deployed standards. And a third phase based on anticipated standards. We define the following phases: Phase 1: Voice call handover service architecture based on a Phase 1 VCC AS that operates in an R4 core network. (And by virtue of R4’s interoperation with R99, interoperates with R99 core networks as well.) A brief summary of the R4 core network is presented in Appendix D, while the voice call handover service enhancements to this architecture are presented below. (Within this document, Phase 1 VCC AS is sometimes referred to as R4 VCC AS.) Phase 2: Voice call handover service architecture based on a VCC AS implemented as an IMS Application Server (AS), that is operated within an initial IMS framework (i.e. 3GPP R5/R6), as a transition option to full R7 IMS Service deployment. Features include those provided by the Phase 1 VCC service architecture and can be expected to evolve towards those provided by a Phase 3 service architecture. A brief summary of the capabilities in R5 and R6 IMS networks is presented in Appendix C, while the voice call handover service enhancements to this architecture are presented below. Phase 3: Voice call handover service architecture based on a R7 VCC, as currently being developed in 3G Standards Development Organizations (SDOs). Phase 1 is defined relative to Release 4 because, as of mid-2006, many mobile operators are in the process of deploying “Release 4” compliant systems. (Release 4 is defined by the 3GPP document: “3GPP TS 41.101 v4.15.0”; which lists the applicable documents. Phase 3 is in the process of being standardized by the 3G SDOs (e.g. 3GPP Release 7 VCC). Phase 1 and Phase 2 proposals incorporate the essential VCC functionality required to support feasible levels of handover capability based on commercially available networks and dual mode devices.
38.
39.
40. The Phase 1 Reference Network Architecture configuration includes a GSM Release 4 CS Domain Core Network and a group of Phase 1 VCC Solution Elements, as shown in the following figure, where the Release 4 Core Network drawing is taken from [TS 23.2005]
41.
42.
43.
44.
45.
46. A Phase 2 Reference Network Architecture Configuration With VCC Is Being Developed Based On The 3GPP R5/R6 IMS Standards Specifications
52. Reference Dual-Mode UE Configuration The following figure shows the configuration of a reference dual-mode UE in a network that includes both SIP PS and Mobile CS network domains, and a VCC AS:
64. 3GPP2 has been studying VCC approaches since 2005. They have tried to keep in step with the 3GPP effort, but have developed certain approaches and extensions independent of 3GPP. Currently, 3GPP2 is focused on defining a VCC standard for a network with IMS. A summary is presented below. HRPD – High Rate Packet Data also known as 1xEV-DO. 3GPP2 Reference Architecture With VCC
65.
66.
67.
68. Party A - Black phone, Party B - Combo phone in CDMA mode Initial Call Setup SIP AS HSS - ISCP IPVLR PCS IMS Operator Network SIP AS ISC (SIP) Mobile AS SOHO BB Modem Firewall (SBC) HLR WiFi AP IS-41 S-MSC O-MSC RBOC CDMA WiFi B A (MGC) (MGW) (S-CSCF) (I-CSCF) (P-CSCF)
69. Party A - Black phone, Party B - Combo phone in CDMA mode Initial Call Setup
70. Party A - Black phone, Party B - Combo phone in CDMA mode Terminating Combo Phone move into WiFi coverage SIP AS HSS-ISCP IPVLR PCS PCS IMS Operator Network SIP AS ISC (SIP) Mobile AS SOHO BB Modem Firewall (SBC) HLR WiFi AP IS-41 S-MSC O-MSC RBOC B A WiFi CDMA (MGC) (MGW) (S-CSCF) (I-CSCF) (P-CSCF)
71. Party A - Black phone, Party B - Combo phone in CDMA mode Terminating Combo Phone move into WiFi coverage
72. [TSG-A A.S0014] Interoperability Specification (IOS) for cdma2000 Access Network Interfaces - Part 4 (A1, A2 and A5 Interfaces) [TSG-C C.S0001 ]Introduction to cdma2000 Spread Spectrum Systems - Revision D [TSG-X X.P0042] Voice Call Interoperability between IMS and Circuit Switched Systems – Stage2 [TIA-EIA-41-D] Cellular Radio Communications Intersystem Operations [TS 23.002] 3GPP TS 23.002 Network Architecture [TS 23.122] 3GPP TS 23.122 Non-Access-Stratum functions related to Mobile Station (MS) in idle mode [TS 29.002] 3GPP TS 29.002 Mobile Application Part (MAP) specification [TR 23.806] 3GPP TR 23.806 Voice Call Continuity between CS and IMS Study (Release 7) [TS 23.206] 3GPP TS 23.206 Voice Call Continuity between CS and IMS; Stage 2 (Release 7) [TS 24.206] 3GPP TS 24.206 Voice Call Continuity between the Circuit-Switched (CS) domain and the IP Multimedia (IP) Core Network (CN) subsystem; Stage 3 (Release 7) [802.11] 802.11-1999 Telecommunications and information exchange between systems – Local and Metropolitan Area networks – Specific requirements – part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications [IETF RFC3261] IETF RFC3261, SIP: Session Initiation Protocol [IETF RFC2327] IETF RFC2327, SDP: Session Description Protocol [IETF RFC3550] IETF RFC3550, RTP: A Transport Protocol for Real-Time Applications Standards
73. This document describes requirements of interworking between 3GPP2 systems and Wireless Local Area Networks (WLANs). The intent of 3GPP2 – WLAN Interworking is to extend 3GPP2 packet data services and/or capabilities to the WLAN environment.
74.
75. This document is part of a multi-part document consisting of multiple parts that together describes cdma2000 Wireless Local Area Network Interworking. The scope of this document covers support for common billing, customer care and cdma2000 based access control and accounting. WLAN interworking service provides Internet access to subscribers of cdma2000 systems via a WLAN network operated by either cdma2000 operators or Wireless LAN network operators who have a service agreement with cdma2000 operators.
76. This document describes the WLAN interworking architecture that supports scenarios 1 and 2 of the four scenarios described in the stage 1 document as follows: • Scenario 1: Common billing and customer care. • Scenario 2: cdma2000 based Access Control and Charging and Access to the Internet via the WLAN system. • Scenario 3: Access to cdma2000 Packet Data Services via the WLAN system. • Scenario 4: Session continuity. Although scenario 1 is supported in this document there are no specific interface requirements to support scenario 1. Support for scenarios 3 and 4 is specified in 3GPP2: X.S0028-200-0, Access to Operator Service and Mobility for WLAN Interworking, Charging functions are limited to accounting in this document.
77. This figure shows the high-level network architecture for support of WLAN interworking for scenario 2. The AAA infrastructure in the WLAN is connected to the cdma2000 home network either directly or via one or more AAA proxies in the intermediate broker network(s). In this architecture model, either a cdma2000 operator or a Wireless ISP may administer the WLAN. The Mobile Station (MS) gains access to the Internet via the WLAN after it is successfully authenticated by the cdma2000 home system. WLAN interworking architecture for scenario 2
78. This document defines the procedures for the support of cdma2000®1 IP data connectivity and mobility in Wireless Local Area Network (WLAN) Interworking for cdma2000networks. These procedures correspond to scenarios 3 and 4 as described in WLAN Interworking Stage 1 Requirements The main objective of this document is to provide secure access to the cdma2000 packet data services and inter/intra access mobility to cdma2000 users via a WLAN system operated by a cdma2000 operator or by a WLAN System operator who has a business relationship with one or more cdma2000 operators.