Open Market Handset (OMH) Device Test and Approval

CDG Document TBD Version 1.0

January 2009

CDMA Development Group 575 Anton Boulevard, Suite 560 Costa Mesa, California 92626 PHONE +1 888 800-CDMA +1 714 545-5211 FAX +1 714 545-4601 http://www.cdg.org cdg@cdg.org

Notice
Each CDG member acknowledges that CDG does not review the disclosures or contributions of any CDG member nor does CDG verify the status of the ownership of any of the intellectual property rights associated with any such disclosures or contributions. Accordingly, each CDG member should consider all disclosures and contributions as being made solely on an as-is basis. If any CDG member makes any use of any disclosure or contribution, then such use is at such CDG members sole risk. Each CDG member agrees that CDG shall not be liable to any person or entity (including any CDG member) arising out of any use of any disclosure or contribution including any liability arising out of infringement of intellectual property rights.

<Page left blank intentionally>

Ref Doc. TBD, Ver. 1.0

January 2009

ii

Contents
1. Introduction ............................................................................................................................... 1 2. Test and Approval Group (TAG).............................................................................................. 2 3. Approval Process ..................................................................................................................... 4 4. Test Coverage ........................................................................................................................... 5 4.1 Existing Coverage prior to OMH ....................................................................................... 5 4.2 Expanded Coverage for OMH ........................................................................................... 6 5. Terminology .............................................................................................................................. 7 6. Frequently Asked Questions ................................................................................................... 8

2 3 4 5 6 7 8 9 10

11

Ref Doc. TBD, Ver. 1.0

January 2009

iii

Device Test and Approval

Contents

Revision History
Date January 2009 Version 1.0 Initial release. Description

2 3

Contributors
Company Reliance Reliance Reliance TATA TATA TATA TATA CCF CDG Q-Lab Qualcomm Qualcomm Name Trishala Nambiar Debasis Das Siddhartha Xavier Alok Chordia Ajay Manghat Rajesh Yadav PSR Krishna Thom Erickson Bill Dahnke Nilesh Patel Nakul Duggal Bryan Gurganus Contact trishala.nambiar@relianceada.com debasis.das@relianceada.com siddhartha.xavier@reliance.com alok.chordia@tatatel.co.in ajay.manghat@tatatel.co.in rajesh.yadav@tatatel.co.in psr.krishna@tatatel.co.in terickson@globalccf.org bdahnke@cdg.org npatel@qualcomm.com nduggal@qualcomm.com bryang@qualcomm.com

Ref Doc. TBD, Ver. 1.0

January 2009

iv

1. Introduction
This document describes OMH device test and approval. The document is organized into three sections as follows: Test and Approval Group description of the entity responsible for approving devices into the OMH ecosystem Approval Process description of the approval process for a device to be approved into the OMH ecosystem Test Coverage Identification of the test coverage required for a device to be approved in the OMH ecosystem

2 3 4 5 6 7 8 9 10 11 12 13

Note that details of test cases and procedures are maintained in a separate living document. The purpose of this document is to define the process and coverage areas for OMH device testing and approval.

14

Ref Doc. TBD, Ver. 1.0

January 2009

2. Test and Approval Group (TAG)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

Figure 1: Test and Approval Group Testing and approval of OMH devices is managed by a Test and Approval Group (TAG) within the OMH SIG consisting of both operator and vendors. The primary functions performed by this group include the following: Defines the scope test coverage that must be performed on OMH devices Approves devices into the OMH ecosystem upon completion of testing Informs operators when new devices are approved Provides operators with BREW Platform ID information for newly approved OMH devices that support BREW downloads Maintains an OMH ecosystem database of OMH operators and devices Approves logo usage on OMH devices and R-UIMs

Ref Doc. TBD, Ver. 1.0

January 2009

Device Test and Approval

1 2 3 4 5 6 7 8 9 10

To ensure that OMH test coverage continues to improve to meet the needs of the OMH ecosystem, the TAG functions as an ongoing forum for any and all OMH SIG participants to present new test recommendations and requirements. TAG works with CCF and 3GPP2 to standardize test coverage with a long term goal of having all test procedures available on validated commercial test equipment. However, when such commercial test solutions are not available, TAG facilitates testing by working directly with test laboratories such as QLab to ensure that test coverage is available.

Ref Doc. TBD, Ver. 1.0

January 2009

3. Approval Process

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

20

Figure 2: OMH Device Approval

21

22 23 24 25 26 27 28

The TAG is responsible for approving OMH devices by verifying that the required OMH test coverage has been successfully completed. For OMH test areas that are supported by CCF and executed on validated commercial test solutions, the TAG will simply accept the CCF certification. For all other OMH test areas, the TAG will review results. Once a device has been approved by the TAG for inclusion in the OMH ecosystem, various informative actions shown in green in the above figure are triggered to ensure that the ecosystem is aware of the newly approved device.

Ref Doc. TBD, Ver. 1.0

January 2009

4. Test Coverage
4.1 Existing Coverage prior to OMH
This section identifies areas of test coverage already provided by CCF certification. This test coverage forms the foundation on which comprehensive OMH testing is based. Table 1: Existing Test Coverage Test Area C2K minimum performance C2K signaling conformance C2K Interoperability Testing (IOT) Audio (Electro-Acoustic) OTASP signaling conformance SMS signaling conformance Data signaling conformance Wireless IP Network signaling conformance HRPD minimum performance HRPD signaling conformance HRPD Rev A minimum performance HRPD Rev A signaling conformance Location minimum performance MEID Test Specification C.S0011-C C.S0031 C.S0058-A C.S0056 C.S0060 C.S0061 C.S0062 C.S0037 C.S0033 C.S0038 C.S0033-A C.S0038-A C.S0036 C.S0073

2 3 4 5

7 8

Ref Doc. TBD, Ver. 1.0

January 2009

Device Test and Approval

Expanded Coverage for OMH

1 2 3 4 5 6 7

4.2 Expanded Coverage for OMH

The areas identified in the following table are areas that have been added to the existing test coverage. These include areas that are specific to OMH functionality as well as common testing necessary to ensure consistent device behavior. The purpose for such test coverage expansion is to ensure that OMH device can be tested and approved one time without the need for additional, operator-specific testing before being launched. Table 2: Expanded Test Coverage Test Area EVRC-B (4GV) + code dialing RUIM support OMH specific CCAT Browser MMS WAP Push WAP IOT BREW PEK Java OMH IOT System Determination Location Based Services Test Specification Enhanced signaling and audio coverage New based on CDG 145 C.S0048 New based on CDG 166/167 requirements New based on C.S0035 requirements OMA Enabler Test Spec for ESMP 1.0, WCSS 1.1, XHTML 1.2 OMA Enabler Test Spec for MMS OMA Enabler Test Spec for Push v2.1 OMA Enabler Test Spec for Download OTA v2.0 New based Qualcomm BREW PEK Suite Java Test Spec Rev. 1.0.3 New based on CDG 166/167 requirements New based on CDG 143 New based on Qualcomm XTRA and V2 requirements

9 10

Ref Doc. TBD, Ver. 1.0

January 2009

5. Terminology
Term 3GPD ARPU BREW C2K CCAT CCF HRPD IOT LBS MEID MMS OEM OMH PCD QLab R-UIM SIG SMS TAG UAProf WAP Meaning 3G Packet Data Average Revenue Per User Binary Runtime Environment for Wireless cdma2000 CDMA Card Application Toolkit CDMA Certification Forum High Rate Packet Data Interoperability Test Location Based Service Mobile Equipment Identifier Multimedia Messaging Service Original Equipment Manufacturer Open Market Handset Plus Code Dialing Qualcomm Pre-certification Laboratories Removable User Identity Module Special Interest Group Short Message Service Test and Approval Group User Agent Profile Wireless Application Protocol

Ref Doc. TBD, Ver. 1.0

January 2009

6. Frequently Asked Questions

Does OMH streamline device testing? Yes. OMH testing provides a single comprehensive test and approval process that removes the need for additional acceptance testing to be performed seperately with each operator. Are applications such as MMS and Browser tested? Yes. The OMH test process includes test coverage for each feature supported in the OMH specifications. These include applications such as SMS, MMS, WAP/Browser, BREW, Java, and LBS. Is any operator testing required after an OMH device is approved? No. Once a device is approved into the OMH ecosystem, it is launched directly into the market. No additional operator testing is required. How is compatibility between OMH devices and R-UIMs ensured? OMH test coverage includes testing of the interface between device and R-UIM, as well as CDMA Card Application Toolkit (CCAT) signaling on this interface and interoperability tests that exercise this interface. Are OEMs required to have OMH devices approved? Yes. All OMH devices must be approved into the OMH ecosystem before being sold into the market and should carry an OMH logo. The OMH SIG maintains a public database of OMH approved devices. For OMH devices that support BREW downloads, the BREW Platform ID is only distributed to operators after the device has been approved. Who can I contact if I have additional questions? Please send email to OMHinfo@cdg.org.

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

37

Ref Doc. TBD, Ver. 1.0

January 2009