CDMA Development Group Global Handset Requirements Team Overview of Document 155 – Wireless IP September 11, 2007 Toronto, Canada

2 Overview Document purpose and scope Relationship to other documents Document development process WIP team activities Document overview Open issues Call for volunteers Contact info

3 Document Purpose and Scope Generate a minimum set of common requirements for Wireless IP to be used by Operators and Device Manufacturers Separate access-agnostic IP requirements from access- specific requirements Wireless IP requirements focus on a base-level best effort data service Embedded and tethered devices

4 Relationship to Other Documents CDG #155 Wireless IP CDG #90 CDMA2000 (voice, SMS, and data) CDG # 148 HRPD Basic Requirements Supplementary and Service-Specific Requirements + Service Specific Requirements Voice-Over-IP, Video Telephony, BCMCS, etc… General Supplementary Requirements #142-R-UIM, #143-system selection, etc…

5 Document Development Process DSC team identifies priority – Done GHRC team approves priority – Done Document team lead and members solicited – Done Document Introduction in face to face meeting – Today Document development team activities (see next slide) Final review in subsequent face to face Meeting Document approval by GHRC CDG SteerCom 30 Day Review, Release and Posting

6 Document Development Team Activities Generate document outline Gather requirements & contributions from carriers Compile requirements into document Identify common, unique, or otherwise necessary requirements for base-level wireless IP service Create a generic requirements document Work issues on unique technical requirements with respective operators to arrive at generic requirements Present and review the generic requirements document during regular team conference calls or meetings

7 Categories of Requirements Mandatory –Handset must support Highly Desirable –Recommended and may become Mandatory eventually Optional –Handset may support Discard –Handset should not support

8 Simple and Mobile IP Reference models –IS-835-D for SIPv4 and MIPv4 –IETF RFCs for MIPv6 if supported Data service –MIP registration, re-registration after voice call, deregistration, retry on failure –Address management w.r.t. DNS, DHCP, Home or Foreign Agent Configurability –SIP configurations, fallback, PRI parameters modification

9 Mobility Management Hand-off, hand-up, hand-down, failure Handoff for active and dormant states Data session continuity Voice and SMS preemption behavior Lost packet management for handoff Location notification for handoff MIP registration for PPP session re-sync

10 Quality of Service As a base-level best effort data service, there is not much to specify Serves as a placeholder for future revisions of document with QoS

11 PPP Configuration Session connect procedures Session disconnect procedures Tethered and embedded procedures Dormancy support

12 Security Authentication based on PPP procedures NAI format and usage (if different than CDG-148) Crypto keys – nothing proposed yet TCP / UDP traffic handling for unsolicited datagram and hot-lining (block all traffic to and from device)

13 Accounting and Profiles Accounting – nothing proposed yet Data profiles – Gold / Silver / Bronze Payment method – unlimited, usage-based, etc Roaming Pre-paid packet data service

14 Radio Channel Access Establishes the link to CDG-148, 1xEV-DOrA

15 Test Mode Engineering test mode with restricted access

16 Open Issues Is IPv6 support mandatory? Simultaneous IPv4 and IPv6? Multiple IP address support?

17 Call for Volunteers Please help by taking ownership of a topic or contributing specific or general comments Subject matter areas where volunteers are needed: –PPP configuration –Crypto keys –Accounting and data profiles –Test mode Inputs need not be neat or organized

18 Contact Wireless IP team lead –Bob Giramma, CDG representative –Elizabeth Nobriga,