handset requirements for roaming cdg reference document #172

Sponsored by:

Handset Requirements for Handset Requirements for RoamingRoaming

CDG Reference Document #172CDG Reference Document #172

Ft LauderdaleFt LauderdaleMarch, 2008March, 2008

2 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

Review of purpose of this document

• The IRT has defined solutions for voice, SMS, and data roaming

• It’s important to identify a clear set of handset requirements to support these solutions

• This document ensures the industry will produce handsets designed to roam

• It should be useful for both operators and handset developers

3 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

Current status of the document

• Concept introduced at Jamaica face to face meeting

• Draft reference document also provided at that time

• No comments to date

• Document now assigned a CDG reference number (#172)

4 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

Suggested Next Steps

• Allow a reasonable period of time for more review

• Discuss final comments on a conference call

• Seek approval for publication after incorporating final comments

5 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

Backup Slides: Document Contents

6 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

• Support for band classes (frequencies)• OTA provisioning of PRLs• SMS VMN and Feature Notification Message• Caller ID behavior• Standardized Roaming Indicators• Configurable Voice Mail Access• Handset Support for +Code• Mobile IP Functionality• E-PRL Support• Support for MEID/UIMID• Support for IMSI_T

Overview of Requirements

7 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

• Different operators used different frequency bands• In order to roam, the handset must be able to use frequencies

supported by the visited operator(s)• GHRC document makes similar band class requirement• Proposed recommendation: mirror GHRC bandclass requirement

– Bandclass 0, 800 MHz (A and B bands)– Bandclass 1, 1900 MHz– Bandclass 5/11, 450 MHz– Bandclass 6, 2100 MHz– AMPS, 800 MHz (A and B bands)

Support for Band Classes (Frequencies)

8 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

• Correctly designed PRLs are critical for roaming

• PRLs are fluid and require constant updates as networks and roaming partners are added

• Without some OTA process, PRLs must be updated manually, e.g. point of sale

• This is a expensive operational process with a bad customer experience

• Handsets should support an OTA update process: OTASP, OTAPA, DM, etc.

OTA Provisioning of PRLs

9 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

• Voice mail notification can be delivered to MS in one of two ways:

– SMS voice mail notification

– Feature notification message

• Some networks support one and not the other

• Handset should be capable of accepting both messages

• Allows for voice mail notification in networks using a different notification process than home network

• More information can be found in CDG document #135, “Roaming Voice Mail, Deposit, and Indicator.”

SMS VMN and Feature Notification Message

10 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

• If a subscriber receives a call while roaming from the home market, the international dialing code and country code will usually be prepended.

• This is desirable behavior as it allows the subscriber to call back the number with changing it.

• However, when comparing the number against entries in the phone book, the handset should not consider the international dialing code or country code.

• This is described in more detail in “International Roaming Caller ID”, CDG document #139.

Caller ID Behavior

11 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

• Handsets expected to roam should support all of the standard roaming indicators

• Specified in 3GPP2 document C.R1001-C, Section 8.

Standardized Roaming Indicators

12 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

• The handset should be able to be configured by the user such that the voice mail access key can be changed.

• This will allow the subscriber to modify the voice mail access key dialed digits to match what is required to reach voice mail in the visited operator’s network.

Configurable Voice Mail Access

13 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

• The handset should support the functionality required for the +code solution.

• More information is available in the “Plus Code Dialing Requirements” document, CDG document #145.

Handset Support for +Code

14 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

• The handset should support Mobile IP capability. Per the Mobile IP Resolution, Mobile IP is the agreed upon data architecture for packet data roaming.

• More information is available in the “Mobile IP Resolution” document, CDG document #140.

Mobile IP Capability

15 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

E-PRL support

• The handset should support PRL enhancements for international roaming.

• More information is available in “PRL Enhancement for International Roaming”, CDG document #86.

16 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

Support for MEID/UIMID

• Devices expected to roaming should support MEID (EUIMID for UIMs).

• More information is available in “Mobile Equipment Identifier Roaming Recommendations”, CDG document #137.

17 www.cdg.org

Ft Lauderdale, March ’08Sponsored by Verisign

Support for IMSI_T

• Devices expected to roaming should support IMSI_T.

• IRMs are running out.

• More information is available in “"MIN-based IMSI to True IMSI Migration Guidelines", CDG document #126.