1

3GPP2 IP Based Emergency CallsIETF/3GPP Hosted SDO Emergency Services Coordination Workshop

Columbia University, New York 5-6 October, 2006

Deb BarclayLucent Technologies+1.630.690.2058DLBarclay@lucent.com

5 Oct. 2006 2

Presentation Overview

– 3GPP2 Background

• Structure

• Partners

• Other collaborative efforts

– 3GPP2 IP Emergency Call Activities

• S.R0115 requirements

• Future considerations

• Challenges

                      

5 Oct. 2006 3

Introduction

The Third Generation Partnership Project 2 (3GPP2) is:

• A collaborative third generation (3G) telecommunications specifications-setting project

• Comprised of interests from the Americas and Asia developing global specifications for MAP “Wireless Radiotelecommunication Intersystem Operations” network evolution to 3G

• Focused on global specifications for the radio transmission technologies (RTTs) supported by MAP and the wireless IP core networks, together known as the cdma2000 ® family of standards.

                      

5 Oct. 2006 4

Background

– 3GPP2's specifications are developed within in the Project's four Technical Specification Groups (TSGs) comprised of representatives from the Project's Individual Member companies. The TSGs are:

• TSG-A (Access Network Interfaces)

• TSG-C (cdma2000® Air Interface)

• TSG-S (Services and Systems Aspects)

• TSG-X (Core Networks)

– All TSGs report to the Project's Steering Committee, which manages the overall work process and adopts the technical specifications forwarded by the TSGs.

– website: www.3gpp2.org

5 Oct. 2006 5

Organizational Partners (OPs)

ARIB Association of Radio Industries and Businesses (Japan)CCSA China Communications Standard Association (China)TIA Telecommunications Industry Association (NAFTA countries:

USA, Canada, Mexico)TTA Telecommunications Technology Association (Korea)TTC Telecommunication Technology Committee (Japan)

5 Oct. 2006 6

Other 3GPP2 Partners

– Market Representation Partners (MRPs)– CDMA Development Group

– IPv6 Forum

– IA450 Association

– MobileIGNITE

– Observers– ETSI

– TSACC

– ITU

– Individual Members: More than 80 companies

5 Oct. 2006 7

Other Collaborative Efforts

– 3GPP - 3GPP2 IMS Core Network specifications based on 3GPP

– IETF - base specifications on RFCs. When additions are needed, prefer to work with IETF rather than define solution/extensions unique to 3GPP2

– OMA - coordination with OMA regarding location and other services

– TIA - offered to support 3GPP2 if needed, or if any USA/regional specific requirements need to be specified outside 3GPP2

– Liaison letters regarding Next Generation Emergency Services recently received from NENA i3, NENA location and ATIS-ESIF-NGES.

5 Oct. 2006 8

IP Based Emergency Services

– Requirements: Stage 1• S.R0115 “All IP-Network Emergency Call Support” - Stage 1

requirements, produced by TSG-S; recommended for publication on Sept. 14, 2006

– Will be available on the 3GPP2 website, under the “Specifications” tab.

– Architecture/Protocol: Stage 2/Stage 3• Core network impacts will be developed in TSG-X (e.g.,

MMD)

• Access network impacts will be developed TSG-A and TSG-C (e.g., cdma2000 air interface)

5 Oct. 2006 9

S.R0115 Requirements

– Supports Voice over packet (WLAN or cdma2000) emergency call originations to legacy emergency centers (e.g., PSTN capable emergency call centers).

– 3GPP2 can not have country specific requirements, but does have optional functionality to meet the needs of local regulation.

– The All-IP Network will indicate to endpoint if emergency calls are supported

– Endpoint should indicate emergency call. If not, the All-IP Network will detect local emergency numbers.

– Support for local emergency numbers and addresses (TEL URI, SIP URI)

– Endpoint will include positioning information in the emergency call request, which may be cell/sector, geoposition, or civic location.

– Knowledge of emergency call is end to end when necessary, including intermediate points.

5 Oct. 2006 10

S.R0115 Requirements– Routing to a emergency call center based on the caller’s location and

the required type of emergency call center (e.g. fire, police, ambulance etc.)

• Routing may be based on rough initial location or accurate location

– Emergency call supported in home and roaming scenarios.• Roaming scenarios may be routed from visited network

– Only authorized endpoints are supported (implies home network subscription and roaming agreements)

– Updated position requests from emergency call center will be supported

– Callback of authorized emergency callers supported

– Call will be maintained even after handoffs between access technologies

– Accurate updated caller location following a handoff provided when requested by the emergency call center

– Service interactions that put call on hold are not allowed

– Call Detail Records supported

5 Oct. 2006 11

S.R0115 Future Considerations

– Emergency Calls to IP emergency call centers

– Support for emergency calls with other media types: e.g., text messaging, pictures, video

– Calls from unauthorized endpoints (e.g., no UIM)

5 Oct. 2006 12

Stage 2 Expectations

– Will build on existing All-IP architecture and 3GPP2 protocols – MMD (IMS), cdma2000 air interface, WLAN, Location Service

– Impact to MMD, cdma2000 air interface, WLAN, Location Services can be expected

– New servers likely to be added to the serving network – e.g. specialized SIP server (CSCF or AS) for emergency calls, separate location and routing server(s)

– Reference to or inclusion of IETF and NENA capabilities (e.g. Geopriv pidf-lo, NENA i2)

5 Oct. 2006 13

Challenges

– All IP-Network architecture and signaling protocols are different than traditional wireless voice network so geopositioning for IP emergency calls can not be assumed

– IP Access

• Which combinations should be supported for emergency calls?– Fixed IP versus Mobile IP (MIP)

– For MIP, Home Agent in the home network or allowed in the visited network

– IPv4 versus IPv6

• When roamers with an established IP connection to home network originate an emergency call, can current configuration be used or re-establish packet connection to visited network?

5 Oct. 2006 14

Challenges

– Call establishment exclusively via the visited network versus via the home network (and visited network)

– Handoff of emergency calls

– Location updates after a handoff

5 Oct. 2006 15

Summary

– 3GPP2 faces many of the same challenges as identified by other organizations and this workshop

– 3GPP2 would like to work cooperatively with other groups to achieve global solutions.

– Thank you!