PTCRB Process

Permanent Reference Document NAPRD03
Version Specific Technical Overview of PTCRB Mobile/User Equipment Type Certification
Version 5.11
Date: April 3, 2012 Classification: Binding, Semi Restricted
PTCRB 1997-20082 Version 5.11
1 3 April 2012
Contents
Contents........................................................................................................ 2 Figures........................................................................................................... 5 1. Mobile Station Certification Test Requirements.................................... 8 1.1. Scope................................................................................................. 8 1.2. Introduction........................................................................................ 8 1.3. Reference Specifications................................................................. 10 1.4. Participating Organizations.............................................................. 18 1.5. List of Tests for Accredited Testing................................................. 18 1.6. Document Amendments.................................................................. 18 1.7. Key to TC Database........................................................................ 18 1.8. PTRCB Test Case Categories......................................................... 27 1.8.1. Category "A".................................................................... 28 1.8.2. Category "B".................................................................... 28 1.8.3. Category "D".................................................................... 29 1.8.4. Category "E".................................................................... 29 1.8.5. Category "N".................................................................... 30 1.8.6. Category "P".................................................................... 30 1.9. RF Performance Evaluation............................................................. 31 1.9.1. RF Performance Test Plan.............................................. 31 1.9.2. RF Performance Test Applicability..................................32 1.9.3. Applicability of RF Performance Testing to ECOs..........34 1.9.4. Receive Diversity............................................................. 35 1.9.5. Deleted............................................................................. 35 1.9.6. Audio Testing................................................................... 35 1.9.7. Radiated Spurious Emissions.......................................... 36 1.10. Test Case Execution Environment................................................ 36 1.10.1. Guideline for test case execution of Multi Band-Multi Rat test cases of RFT067................................................. 36 1.11. Classmark MessageUE Capability Audit....................................... 38 1.12. AT-Command Assessment Requirements.................................... 39
2 3 April 2012
1.12.1. AT-Command Applicability............................................ 39 1.12.2. AT-Command Test Specification................................... 39 1.12.3. AT-Command Certification Criteria............................... 39 1.12.4. AT-Command Technical Reference .............................40 1.13. Guidelines for execution of test cases for E-UTRA Test cases for RFT 076...................................................................................... 40 1.13.1. Signaling testing............................................................ 40 1.13.2. RF testing...................................................................... 40 2. Application Enablers Evaluation, General Information....................... 41 2.1.1. Application Enabler (AE) Test Applicability ....................42 2.1.1.1. AE Testing Required.................................... 42 2.1.1.2. AE Testing Not Required.............................42 2.1.1.3. AE Test Specification .................................. 42 2.1.1.4. ECOs............................................................ 42 2.1.1.5. Application Enabler Certification Criteria.....43 2.1.1.6. AE Technical Requirements........................ 44 2.1.1.7. AE Options Table/ICS/Test Case Mapping Document................................................ 45 2.1.1.8. AE Interoperability Test Results................... 45 2.2. Specific Application Enabler Test Requirements............................ 45 2.2.1. Multimedia Messaging Service (MMS)............................ 45 2.2.1.1. MMS Applicability......................................... 45 2.2.1.2. Effective Date for MMS Testing................... 45 2.2.1.3. Transition Period for MMS 1.x Certification. 45 2.2.1.4. MMS Test Specification...............................46 2.2.1.5. MMS Certification Criteria............................46 2.2.1.6. MMS Technical Requirements .................... 47 2.2.1.7. Test Case Mapping Table for Terminals supporting MMS...................................... 47 2.2.2. Video Telephony (VT)...................................................... 48 2.2.2.1. VT Applicability............................................. 48 2.2.2.2. VT Test Specification...................................48 2.2.2.3. VT Certification Criteria................................ 48
3 3 April 2012
2.2.2.4. VT Technical Requirements ........................ 48 2.2.2.5. Options Table/ICS/Test case mapping document for Terminals supporting VT. .49 2.2.2.6. MMS Interoperability Test Results ..............49 2.2.2.6.1. Conformance Test Results for Terminals supporting MMS......................................................... 49 2.2.3. Deleted............................................................................. 53 2.2.4. Deleted............................................................................. 53 2.2.5. Deleted............................................................................. 53 2.2.6. Device Management........................................................ 53 2.2.6.1. Device Management Applicability................53 2.2.6.2. Device Management Test Specification.......53 2.2.6.3. Device Management Certification Criteria. . .53 2.2.6.4. Device Management Technical Requirements ................................................................ 53 2.2.7. Secure User Plane Location (SUPL)............................... 53 2.2.7.1. Secure User Plane Location (SUPL) Applicability............................................. 53 2.2.7.2. SUPL Test Specification..............................54 2.2.7.3. SUPL Certification Criteria...........................54 2.2.7.4. SUPL Technical Requirements ...................54 2.2.8. Browsing 2.3.................................................................... 54 2.2.8.1. Browsing 2.3 Applicability............................54 2.2.8.2. Browsing 2.3 Test Specification...................54 2.2.8.3. Browsing 2.3 Certification Criteria ...............54 2.2.8.4. Browsing 2.3 Technical Requirements .......55 2.2.8.5. Browsing 2.3 Interoperability Test Results. .55 2.2.9. FUMO.............................................................................. 57 2.2.9.1. FUMO Applicability....................................... 57 2.2.9.2. FUMO Test Specification.............................57 2.2.9.3. FUMO Certification Criteria ......................... 57 2.2.9.4. FUMO Technical Requirements .................. 57 2.2.9.5. FUMO Interoperability Test Results.............58
4 3 April 2012
2.1.10. SCOMO......................................................................... 59 2.2.9.6. SCOMO Applicability.................................... 59 2.2.9.7. SCOMO Test Specification..........................59 2.2.9.8. SCOMO Certification Criteria ...................... 59 2.2.9.9. SCOMO Technical Requirements ...............59 2.2.9.10. SCOMO Interoperability Test Results........59
Figures
Figure 1 GSM Band Selection for Protocol Testing (Single Band Only) 22 Figure 2 UTRA Band Selection for Protocol Testing (Single Band Only) ................................................................................................................. 23 Figure 3 E-UTRA Band Selection for Protocol Testing (Single Band Only)........................................................................................................ 25
5 3 April 2012
Preface
The purpose of this Permanent Reference Document (PRD) is to provide version specific technical framework within which GERAN, UTRA and E-UTRA device certification can take place. Refer to the latest version of the PTCRB Program Management Document (PPMD) for the process requirements.
6 3 April 2012
7 3 April 2012
1.
Mobile Station Certification Test Requirements

1.1. Scope This section of NAPRD03 specifies a common approach to the certification testing of GSM/UTRA terminal equipment. The object of this document is to provide advice to administrators such that certification testing of terminal equipment may be performed on a common basis. This document has been developed in the PTCRB by experts from: Administrations Network operators All PVG members This document is advisory in nature but compliance with it should ensure an agreed common platform for certification testing of User Equipment. This document may be updated on a regular basis. 1.2. Introduction This document is intended to advise accredited laboratories and administrations on how to establish terminal equipment conformity with the reference specifications below. Information is presented to clearly identify which conformance requirements may be evaluated using the reference test system configuration as defined on TC Database and which conformance requirements may be evaluated using other defined methods or equipment. TC Database includes a concise report of the technical status of the reference type certification test equipment implementation. Where necessary, additional information may be presented to enable tests to be performed and the results of tests to be interpreted in a harmonized manner. TC Database provides a separate listing of the test cases. TC Database must be used as
8 3 April 2012
the primary reference for the actual test cases and applicable categories.
9 3 April 2012
1.3.
Reference Specifications
GSM:
3GPP TS 51.010 (formerly GSM 11.10) 3GPP TS 51.010-4.

UTRA:
3GPP TS 34.121 3GPP TS 34.123 3GPP TS 31.121 (USIM) 3GPP TS 31.124 (USAT) 3GPPTS 26.132 (Audio) 3GPP TS 34.108 ETSI TS 102 230 (UICC) 3GPP TS 34.124 (RSE)
E-UTRA:
3GPP TS 36.521 3GPP TS 36.523

SWP / HCI:
ETSI TS 102 694 (SWP) ETSI TS 102 695 (HCI)

A-GPS:
3GPP TS 34.171 Note 1: In the case of UTRA A-GPS test cases (3GPP TS 34.171 5.x and 3GPP TS 34.123-1 17.x), the requirements have been moved to 3GPP TS 37.571-1 and 3GPP TS 37.571-2 respectively. Cross reference information has been added to 3GPP TS 34.1231 and 3GPP TS 34.171 detailing the mapping of test cases to the new specifications.
10 3 April 2012
Note 12: PTCRB accepts the 3GPP redundancy of test cases defined in PVG.05 with the following exceptions: 3GPP TS 51.010-1/2 Requirement GSM is the redundant radio access technology 44.2.1.1.1 3, 4 GPRS attach / accepted 44.2.1.1.2 3, 4 GPRS attach / rejected / IMSI invalid / illegal MS 3, 4 44.2.1.1.3 GPRS attach / rejected / IMSI invalid / GPRS services not allowed 3, 44.2.1.1.4.3.1 GPRS attach procedure 4 / Normal GPRS attach / GPRS attach / rejected / PLMN not allowed / Test procedure 1 3, 44.2.1.1.5.3.1 GPRS attach procedure 4 / Normal GPRS attach / GPRS attach / rejected / roaming not allowed in this location area (procedure 1) 44.2.1.1.6.3.1 3, GPRS attach / 4 Abnormal cases / access barred due to access class control / Test procedure 1 44.2.1.1.7 3, 4 GPRS attach / abnormal cases / change of cell into new 3GPP TS 34.123-1 Requirement W-CDMA is the preferred radio access technology PS attach / accepted 12.2.1.1 4 12.2.1.2 4 PS attach / rejected / IMSI invalid / illegal UE 4 12.2.1.3 PS attach / rejected / IMSI invalid / PS services not allowed 12.2.1.4 Proc 1 PS attach / rejected / 4 PLMN not allowed / Procedure 1
12.2.1.5a Proc 14
PS attach / rejected / PLMN not allowed / Procedure 1
12.2.1.6 4 Proc 1
PS attach / abnormal cases / access barred due to access class control / Procedure 1 PS attach / abnormal cases / change of routing area
12.2.1.7 4
11 3 April 2012
3GPP TS 51.010-1/2 Requirement GSM is the redundant radio access technology routing area 3, 4 44.2.1.2.1 Combined GPRS attach / GPRS and non-GPRS attach accepted 44.2.2.1.5 3, 4 GPRS detach / power off / accepted 3, 4 44.2.2.2.1 GPRS detach / reattach not required / accepted 44.2.3.1.1 3, 4 Routing area updating / accepted 3, 4 44.2.3.1.2 Routing area updating / rejected /IMSI invalid / illegal ME 44.2.3.1.3 3, 4 Routing area updating / rejected / MS identity cannot be derived by the network 3, 4 44.2.3.1.4 Routing area updating / rejected / location area not allowed 44.2.3.2.2 3, 4 Combined routing area updating / MS in CS operation at change of RA 44.2.3.2.4 3, 4 Combined routing area updating / rejected / PLMN not allowed 3, 44.2.3.2.5.3.1 Routing area updating 4 procedure / Combined routing area updating /
3GPP TS 34.123-1 Requirement W-CDMA is the preferred radio access technology 12.2.2.1 4 12.4.1.3 4 12.4.1.1a 4 12.4.1.2 4 12.3.1.1 4 12.3.2.1 4 Combined PS attach / PS and non-PS attach accepted PS detach / power off / accepted PS detach / re-attach not required / accepted Routing area updating / accepted Routing area updating / rejected / IMSI invalid / illegal ME Routing area updating / rejected / UE identity cannot be derived by the network Routing area updating / rejected / location area not allowed Combined routing area updating / UE in CS operation at change of RA Combined routing area updating / rejected / PLMN not allowed Combined routing area updating / rejected / roaming not allowed in
12.4.1.4a 4 12.4.2.2 4
12.4.2.4 4 12.4.2.5a Proc 14
12 3 April 2012
3GPP TS 51.010-1/2 Requirement GSM is the redundant radio access technology Combined routing area updating / rejected / roaming not allowed in this location area / procedure 1 44.2.3.3.1 3, 4 Periodic routing area updating / accepted 3, 4 44.2.4 P-TMSI reallocation 3, 4 45.2.1.1 Attach initiated by context activation / QoS offered by network is the QoS requested 3, 4 45.4.1 PDP context deactivation initiated by the MS 45.4.2 3, 4 PDP context deactivation initiated by the network
3GPP TS 34.123-1 Requirement W-CDMA is the preferred radio access technology this location area / Procedure 1
12.4.3.1 4
12.5 4 11.1.1.1 4
Periodic routing area updating / accepted P-TMSI reallocation Attach initiated by context activation/QoS Offered by Network is the QoS Requested PDP context deactivation initiated by the UE PDP context deactivation initiated by the network
11.3.1 4 11.3.2 4
PTCRB determines that the redundancy of the above listed 2G TCs is not valid and therefore both the GSM TCs (3GPP TS 51.010-1) and the UTRA-FDD TCs (3GPP TS 34.123-1) have to be performed for PTCRB certification.
13 3 April 2012
Note 23: PTRCB follows recommended test applicability defined by 3gpp as part of the Implementation Conformance Statement (ICS) proforma specification (3GPP TS 34.1232); except, for the following test cases:
Clause 6.1.1.8 6.1.1.9 6.1.2.11 6.2.1.10 6.2.1.11 8.1.1.11 8.3.3.4 Title PLMN selection in shared network environment, Automatic mode PLMN selection in shared network environment, Manual Mode Cell reselection in shared network environment Selection of PLMN and RAT in shared network environment, Automatic mode Selection of PLMN and RAT in shared network environment, Manual mode RRC / Paging for Connection in idle mode (Shared Network environment) RRC / UTRAN Mobility Information: Shared Network Release Rel-5 Rel-5 Rel-5 Rel-5 Rel-5 Rel-5 Rel-5 Applicability C01 C01 C01 C05 C05 C01d C01d Comments UEs supporting FDD UEs supporting FDD UEs supporting FDD UEs supporting FDD and GSM UEs supporting FDD and GSM UEs supporting FDD. UEs supporting FDD. Number of TC Executions (informative) 1 Execution: CS+PS preferred 1 Execution: CS+PS preferred 1 Execution: CS+PS preferred 1 Execution: CS+PS preferred 1 Execution: CS+PS preferred 1 or 2 Executions: CS, PS 1 Execution: CS+PS
Shared Network Environment test listed in 34.123 are applicable for Rel-5 devices that supports the feature.
14 3 April 2012
15 3 April 2012
Mobile Station RF Performance Evaluation:
CTIA OTA Test Plan

Wi-Fi RF Performance Evaluation:
CTIA/Wi-Fi Alliance Test Plan for RF Performance Evaluation of Wi-Fi Mobile Converged Devices
MMS:
OMA-IOP-MMS-ETS
Video Telephony:
IMTC 3G-324M Test Specification 3G-324M Video Telephony Activity Group - Test Cases Interoperability 3G-324M Video Telephony Activity Group - Test Cases Compliance
OMA SUPL 1.0, 2.0:
OMA-ETS-SUPL-V1_0 OMA-ETS-SUPL-V2_0
IMS:
3GPP TS 34.229
OMA DM 1.2:
OMA-ETS-DMV1_2
OMA Browsing 2.3:
OMA-ETS_XHTMLMP_CON-V1_2 OMA-ETS-WCSS-V1_1
TTY:
PTCRB Bearer-Agnostic TTY Test Specification, Version 1.0 (Reference: PTCRB#56 Doc#0912156)
16 3 April 2012
2G TTY Test Specification, Rev. 4.31 TTY 3G Test Specification, Rev. 2.0 (www.ptcrb.com) Note 14: For clarification, test cases from PTCRB BearerAgnostic TTY Test Specification shall be performed for PTCRB certification instead test cases from 2G TTY Test Specification and/or TTY 3G Test Specification. Test case applicability as per PTCRB Bearer-Agnostic TTY Test Specification Section 8 shall apply.
A-GPS Radiated Performance:
CTIA OTA Test Plan

RFT 002, RFT 006:
PVG.03 (latest version)

AT-Command:
PTCRB Bearer Agnostic AT-Command Test Specification (latest version)

OMA SCOMO 1.0:
OMA ETS SCOMO V1.0

OMA FUMO 1.0:
OMA ETS FUMO V1.0 General Notes: Note 15: For clarification, the core specifications from 3GPP, OMA, and other Standards Bodies mentioned above, are the definitive statements of expected behavior. For protocol tests the TTCN developed by 3GPP or OMA is the definitive description of test cases and shall be used in the first instance by the test equipment industry to develop validated test cases.
17 3 April 2012
Other protocol test implementations are allowed as long as they are based on prose for which there is a corresponding approved TTCN test case contained in the relevant 3GPP or OMA specifications TS 34.123-3 or TS 51.010-5. This approval will take place at the 3GPP or OMA meetings as appropriate. In the event of conflicting results between test platforms, the equipment using the 3GPP- or OMA-developed TTCN will be taken as the correct implementation until proven otherwise.
1.4.
Participating Organizations Technical validation of the test systems included in this document has been conducted by the PTCRB Validation Group (PVG). A list of members can be obtained from document PVG.02.
1.5.
List of Tests for Accredited Testing TC Database shows the status of validated tests approved for certification testing. Where a variation or specific interpretation of a test specification or test method is required by the accredited laboratory, this will be recorded in the TC Database.
1.6.
Document Amendments Responsibility for this document is held by the PTCRB. Any amendment proposals should be submitted directly to the Chairman for consideration by the group.
1.7.
Key to TC Database Test Specification: A document defining the test approach for a feature or combination of features, and the initial conditions execution conditions, and the pass/fail criteria for the related tests. RFT (Request For Test): An RFT is a request by the PTCRB to include test cases for a specific requirement (i.e. feature / function). The RFT indication
18 3 April 2012
in TC Database shows the association between the test case and a specific RFT. The full collection of RFT`s is maintained in PTCRB PVG.03. Test Case: Test case as defined in the associated test specification. Note: When the test case is a multi-band or multiRAT test, it is qualified with a band combination. This qualification is contained within square brackets where the initial band of the test case is named first and subsequent band(s) follow adhering to these rules:
Technology Test Case Parameter: Example Allowed Values C00 CDMA 2k bands C01 FDD17 E-UTRA bands FDD4 TDD41 FDDII UTRA bands FDDIV FDDV FDDI 1900 GERAN bands 850 900 1800 The GSM bands with no qualification before or after the actual band definition. Note that the multi-band GSM tests are not qualified. Comment Numeric values for the bands must be used with a leading zero where required.
Numeric values for the bands must be used without any leading zeros.
Roman numerals must be used to differentiate between UTRA & EUTRA.
Test Description: Test case description as defined in the associated test specification PTCRB Cat: Test categories as detailed in Section below
19 3 April 2012
Test Platform: Test Platform number of validated test equipment. Validation Status Information: a) V (Validated): A Test Platform having fully fulfilled the validation criteria complying with the latest version(s) of the Test Specification(s). E (Exception): A Test Platform partially fulfilling the validation criteria and/or just partially complying to the latest version(s) of the test specification(s).. D (Downgrade): A Test Platform that has been downgraded and is currently not recommended to be used for the certification testing process.
b)
c)
Test Case Classifications: a) Bearer Agnostic: A test case which is independent of the radio access bearer or frequency band used during the test (typically used for Application Enablers). b) Bearer Band: A test case that has been validated for specific frequency bands and/or technology (i.e. GSM1900, FDD2, GAN). c) Network Independent: A test case which is validated without the use of a radio access bearer (i.e. SIM interface specific tests).
d) Band Independent: The performance of test cases is not influenced by the bearer band used for the test scenario. The test case can be performed with any PTCRB bearer band within a radio technology, supported by the terminal. Test Case Sub-Classifications for all Bearer Band Tests. Bearer to be tested: Defines the radio access bearer(s) and band(s) in which the device shall be tested.
20 3 April 2012
a)
Single indicates that the applicable test case (e.g. protocol testing) must be tested according to the following rules. This rule is illustrated in figure 1, 2 and 3. Note: Interband test cases must be tested if the frequency band combinations are supported by the mobile.
b) "All" indicates that the mobile should be tested in all PTCRB Bands. Test cases defined for GCF Bands should be executed as indicated within the applicable GCF-CC. Bands identified by both PTCRB and GCF are defined as PTCRB Bands and must be executed according to the PTCRB rules. InterRAT test cases should be tested in all frequency band combinations supported by the mobile. PTCRB Bands: GERAN: 850 MHz, 1900 MHz UTRA: FDD Band II, FDD Band IV, FDD Band V E-UTRA: FDD Band 2, FDD Band 4, FDD Band 5, FDD Band 7, FDD Band 12, FDD Band 13, FDD Band 14, FDD Band 17, FDD Band 24, FDD Band 25 Test cases defined for GCF Bands shall comply with the category assigned by GCF-CC. Therefore, compliance shall be ensured for all category A test cases. c) I-RAT Single indicates an InterRAT test case that should be tested in a single band combination. InterRAT test cases are split into separate test case parts for each possible band combination. InterRAT test cases must be tested in accordance with the principles shown in figures 1, 2 & 3; that is, test cases with band combinations in the 1900 MHz bands have highest priority, followed by tests in 850 MHz bands. d) multi indicates that a band combination is required, e.g. GSM1900/850 MHz bands. e) Blank indicates that the test does not require a bearer
21 3 April 2012
f) "RAT All" indicates that the applicable test case must be tested once in each supported RAT and in accordance with the principles shown in figures 1, 2 and 3 below.
Figure 1 GSM Band Selection for Protocol Testing (Single Band Only)
22 3 April 2012
Figure 2
UTRA Band Selection for Protocol Testing (Single Band Only)
23 3 April 2012
24 3 April 2012
Figure 3
E-UTRA Band Selection for Protocol Testing (Single Band Only)
25 3 April 2012
Where test cases have been identified as redundant between UTRA and GSM, or where a mixture of test capabilities for UTRA and GSM band support exist, testing shall be performed according to the following rules: If UTRA FDD is supported by the DUT and the test case in question has been validated for FDD Band II, IV, or V, then execute the test in UTRA-FDD. Selection of a band for execution of the test shall be determined by the prioritization rules depicted in Figure 2 above. Note: For instances in which the test case is only available in bands supported by GCF-CC, execution of the test in a GCFCC UTRA band is preferred over GCF-CC GERAN. If UTRA FDD is not supported by the DUT but GSM1900 or GSM850 is supported by the DUT and the test case in question has been validated for GSM1900 or GSM850, then execute the test in GERAN. Selection of a band for execution of the test shall be determined by the prioritization rules depicted in Figure 1 above.
Special Rules and Exceptions: Audio testing must be performed according to the rules as defined in section 1.9.6 of this document. GCF Certification test results for GCF Bands will be recognized as a substitute for PTCRB test results in these bands, provided the GCF lab conducting the tests is at a minimum an active observing member of the PVG. Otherwise, GCF Band test cases must be performed in a PTCRB lab. The PTCRB lab will be responsible for uploading the GCF Certification test results to PTCRBs database along with their own test results. Application enabler tests are not bearer dependant and can be performed in any frequency band supported by the terminal. If the primary PTCRB band tested on the certified parent device is disabled for any technology on the variant device, results for all single band test cases from the parent device can be reused on the variant device for certification.
26 3 April 2012
If primary band test cases were executed according to GCF-CC only in any technology on the parent device, then testing of all single band test cases must be executed on the variant device if a PTCRB band is enabled, even if the band tested according to GCF-CC is still enabled. Band prioritisation on both devices shall be decided according to the rules illustrated in figures 1, 2 and 3. For bearer agnostic testing refer to NAPRD section Application Enabler (AE) Test Applicability. Comments: This field may be used to provide comments or references as necessary. 1.8. PTRCB Test Case Categories The following test categories shall be used:
Category "A": Category "B": Category "C": Category "D": Category "E Category "N Category "P Test fully available and fully validated, testing at an accredited test laboratory required Testing at an accredited test laboratory with exceptions Reserved category Test is downgraded and is not a certification requirement Test case is validated and results are provided to CTIA. Failure of DUT to pass test case will not cause loss of certification. Not applicable New test case not yet validated or a test case that has been downgraded for more than 45 days.
27 3 April 2012
1.8.1.
Category "A"
Definition of this category: Device Conformance is tested by an accredited laboratory as indicated in the "tested band" column. Conformity of the terminal is demonstrated in an accredited laboratory using validated test programs on appropriate test equipment reference configuration listed in TC Database. Interoperability Testing: This test purpose is tested according to section 2.2, Specific Application Enabler Test Requirements. This category is used for: All test purposes covered by validated Means of Test or a defined interoperability methodology
1.8.2.
Category "B"
Definition of this category: Device conformance is tested to the extent possible by an accredited laboratory as indicated in the "tested band" column. Conformity of the terminal is demonstrated to the extent possible in an accredited laboratory using validated test programs on an appropriate test equipment reference configuration listed in TC Database. This category is used for: a) Means of Test where test purposes are not fully tested, because parts of the Means of Test are incorrect and therefore not valid for accredited testing. b) Means of Test where a "PASS" verdict is a valid verdict, but a "FAIL" verdict may not be valid. c) Means of Test not validated for a special UE configuration. Example: 1) Parts of a Means of Test are validated because some sections of the test program are faulty and therefore the referenced test purpose might be partly covered or other referenced test purposes are not covered at all. 2) A Means of Test is running up to a specific test section where more than one correct UE behavior would be possible but only one specific behavior is allowed by the test program and therefore the UE might unfairly FAIL in this section. 3) A Method of Test is written for TCH/S UE and DATA-only UE, but the test can be performed for TCH/S UE only.
28 3 April 2012
1.8.3.
Category "D"
Definition of this category: The test has previously been in category A, B or E but has been downgraded due to an issue with the test case implementation, test platform and/or test specification and there are no valid means of test available. Unless the test case issue is resolved and the test case re-validated within 45 days of approval of the test case downgrade, the test case will revert to Category P (45 day rule). This category is used for: An indication that a test case was earlier a certification requirement but has been downgraded due to an issue with the test case; and that the test case can be revalidated by 5 day rule and immediately be re-introduced as a certification requirement. Example: A PTCRB accredited lab has found an issue with a test case implementation that means the test case cannot be used for certification testing. The PTCRB lab has raised a change request by 5 day rule explaining the issue and proposing to downgrade the test case. On approval of the 5 day rule the test case category is changed to D indicating the test case is downgraded and not a certification requirement. If the test case is not corrected and re-validated with 45 days it will revert to Category P and be treated as though it was a new test case.
1.8.4.
Category "E"
Definition of this category:. Tests that have been validated but are under evaluation are allocated to Category "E". Category E tests must be performed by an accredited laboratory on terminals as indicated in the "tested band" column; the results of which will not gate issuance of an IMEI. The results of these tests must be presented as part of the certification documents presented to CTIA. The results shall also include comments pertaining to the reason of any failures experienced within a category E test case. This shall include whether the test case is believed to be at fault and an indication that the test equipment manufacturer has been contacted. If it is believed to be a terminal failure, the comment shall include what type of error was indicated by the test equipment. Where these tests have failed on a parent product these tests shall be re-run for subsequent ECO's and Variant certifications. Interoperability tests may be executed by the manufacturer as defined in 2.2, Specific Application Enabler Test
29 3 April 2012
Requirements This category is used for: Test for features that were new or not supported by all operators, will also include recently validated tests prior to being moved to category "A". Example: Tests that have been validated but have not been moved to category "A" such as new GPRS test cases or features not supported by all operators such as PBCCH or NMO I
Addition of Tests to Category "E"
A PTCRB member may request inclusion of a specific test(s) in category E. The PTCRB operator members shall vote on the test(s) and if it is approved by a majority of the PTCRB operators, the test is moved to category E. All new tests submitted by the PVG will initially become Category "E". How a test is moved from Category "E" to any other category: A PTCRB member may request the movement of specific test(s) from Category "E" into another Category (A, B). Alternatively, the test may be removed. The PTCRB operator members shall vote on the change request proposal. If the change request proposal is approved by a majority of the PTCRB operators then the test(s) would change to the proposed category.
1.8.5. Category "N"
Definition of this category: This listed test does not require any testing nor declaration This category is used for: Test execution not required Example: Band specific tests required testing in 1900 but not required in 850.
1.8.6.
Category "P"
30 3 April 2012
Definition of this category: Based on tests which have been specified by an RFT and not validated on commercially available test equipment. Validation reports shall be submitted to PVG meetings for PTCRB approval, and test cases can only change to category E in a new version of NAPRD03 as defined above. This category is used for: Instances where no test solution presently available Example: RFTs generated by the PTCRB such as the new EGRPS tests added PTCRB#30
1.9.
RF Performance Evaluation
1.9.1. RF Performance Test Plan
The test plan to be utilized for the evaluation of RF Performance of GSM 850, GSM 1900, FDD Band II, FDD Band IV, and FDD Band V is the CTIA Test Plan for Mobile Station Over-the-Air Performance. The latest version of this test plan can be downloaded from CTIAs web site at www.ctia.org/certification. A listing of labs authorized to conduct this testing can be found on the same web site (under OTA Performance authorized testing capability). If the device is required to conduct RF Performance testing as part of GCF Certification, the GCF RF Performance test results must be uploaded to the certification database in the OTA Performance Test results section. If the device supports 802.11x (note: the Wi-Fi feature checkbox must be checked in the online certification database), the device shall also be tested to the CTIA/Wi-Fi Alliance Test Plan for RF Performance Evaluation of Wi-Fi Mobile Converged Devices. The latest version of this test plan can be downloaded from CTIAs web site at www.ctia.org/certification. A listing of labs authorized to conduct this testing can be found on the same web site (under Converged Device authorized testing capability). If the device supports A-GPS (Note: the A-GPS feature checkbox must be checked in the online certification database),
31 3 April 2012
it shall be tested according to the CTIA Test Plan for Mobile Station Over-the-Air Performance. The latest version of this test plan can be downloaded from CTIAs web site at www.ctia.org/certification. A listing of labs authorized to conduct this testing can be found on the same web site (under OTA Performance authorized testing capability).
1.9.2. RF Performance Test Applicability
RF Performance Testing Required Head Phantom Only, Head and Hand Phantom, and Free-Space Devices supporting usage against the head.
Note: If a device supports multiple configurations with which to make a call, each configuration representative of end use, where the receiver is placed on the ear, shall be tested (e.g., a portrait slide phone shall be tested in both slide open and slide closed positions, a side slide phone shall be tested only in the slide closed position, a fold phone shall be tested only in the open position). Device configurations that are not representative of end use (e.g. configurations where the receiver is not placed on the ear), do not need to be tested in head phantom only, head and hand phantom, and freespace conditions. GPS OTA testing is not required in the head phantom only and free-space configurations as specified in the CTIA Test Plan for Mobile Station Over-theAir Performance. Also, the vendor shall submit to the CATL a declaration of the primary mechanical mode as referenced in the test plan.
RF Performance Testing Required Hand Phantom Only
Devices supporting data usage in the hand phantom only test configuration (devices that also support usage against the head shall also be tested per above)
Note: If a device has multiple configurations in which it can be held in the hand for data usage scenarios where the display is visible to the end user, each configuration representative of end use shall be tested as long as the device can still meet the maximum dimensions specified for the hand phantom configurations defined in the CTIA Test Plan for Mobile Station
32 3 April 2012
Over-the-Air Performance. Device configurations that are not representative of end use in the hand for data usage scenarios where the display is visible to the end user or exceed the maximum dimensions specified for the hand phantom configurations defined in the CTIA Test Plan for Mobile Station Over-the-Air Performance do not need to be tested in the hand phantom only condition. Also, the vendor shall submit to the CATL a declaration of the primary mechanical mode as referenced in the test plan.
RF Performance Testing Required Free-Space Only
Fixed wireless, telemetry, telematics, and data-only devices with an integrated, non-removable antenna attached to the device Fixed wireless, telemetry, telematics, and data-only devices with a removable antenna physically attached to the device Fixed wireless, telemetry, telematics, and data-only devices with a removable antenna connected directly to the device via an RF transmission line (such as a coaxial cable) less than 20 cm in length. Notebooks, Tablets and Ultra-Mobile PCs with embedded WWAN (Wireless Wide Area Network) radio modules. Note: Free-Space testing is optional for notebooks which qualify as Child platforms under sections 11.11.5 and 11.11.6 of the PTCRB PPMD. Large Devices These would include devices such as parking meters, vending machines etc. Note 1: Physically large or heavy devices that cannot be placed in an OTA chamber, might be tested in a configuration that represents the actual usage (e.g. antenna mounted on a ground plane 2 X 2 or other material used on the actual device) Note 2: Some devices include sensors which reduce the transmitters RF output power when in close proximity to the user. TRP measurements of any device that includes user proximity RF power reduction shall be made when the proximity sensor is not activated (e.g. device is operating at
33 3 April 2012
full RF output power). The PTCRB lab shall also measure the devices RF output power when the proximity sensor is activated. This measurement may be made using either conducted or radiated techniques, and the lab shall document the proximity sensors RF power reduction in dB.
RF Performance Testing Not Required
Note: The lab shall provide a document stating that the device falls into one of the categories listed below. In addition, the vendor shall consult with the carrier(s) to which they intend to sell the device to determine whether carrier-specific testing may be required. If no testing is conducted, the lab shall provide a detailed justification (to be uploaded to the PTCRB certification database in the test results file). Fixed wireless, telemetry, telematics, and data-only devices without a defined antenna Fixed wireless, telemetry, telematics, and data-only devices with a removable antenna that is connected to the device through an RF transmission line (such as a coaxial cable) greater than 20 cm in length and not physically attached to the host device Modules PCMCIA cards or ExpressCards USB Modems Variants, re-branded devices having no altered RF performance from their parent device
1.9.3. Applicability of RF Performance Testing to ECOs
RF Performance testing must be conducted on an ECO if the associated changes impact any of the following areas: Hardware design Calibration data/procedure Maximum output (radiated) power
34 3 April 2012
If the changes do not impact these areas AND conducted RF output power in all supported bands has not changed by more than +/- 1 dB, then RF performance testing on the ECO is not necessary. The lab shall then upload a document to PTCRBs online certification database, in the Test Results area, providing this justification (see Laboratory Test Report Content section of PPMD).
1.9.4. Receive Diversity
If the device supports receive diversity, the diversity test conditions shall be in accordance with the CTIA Test Plan for Mobile Station Over-the-Air Performance.
1.9.5. 1.9.6. Deleted Audio Testing
If the terminal implements audio according to 3GPP Release 4 or later, the audio test cases in 3GPP TS 51.010-2 applicable for Release 4 or later release shall be applied as certification criteria instead of the Audio test cases applicable for Phase 2 and up to R99 terminals. In addition to the above, terminals which support both GSM and FDD bands shall conduct the AUDIO testing in accordance with the Test Guidelines for test case redundancy for dual mode terminals as defined in PVG05. Reference test position according to section 5.3.2 of IEEE 269 2002 can be used and should accordingly be recorded in the test report. The test report shall contain the following information if appropriate and where it is not available from the manufactures PICS statement: Ear type used for testing Positioning used in the HATS, as per ITU-T P.64 Nominal volume setting used for receiving related testing
Note: The PTCRB TC database audio test specification 26.132 contains all test cases from all released specification versions.
35 3 April 2012
The test specification is release specific which is different to any other test specifications within PTCRB TC DB. So, tests may differ in their requirements depending on the release version of the test spec. PTCRB TC DB does not take this into account. Therefore, the manufacturer has to declare against which release the terminal was developed. The conclusion is that Terminals with an acoustic implementation according to a given release should be tested against the latest version of the corresponding release of 3GPP TS 26.131 and 3GPP TS 26.132.
1.9.7.
Radiated Spurious Emissions
Radiated Spurious Emissions (RSE) testing shall be conducted according to the guidelines established in PVG.04, Guideline for Spurious Emission Radiated Testing.. Radiated Spurious Emissions testing of a UE supporting GSM 850 MHz and UTRA FDD V may conduct testing in 2G (GSM) or 3G (UTRA). Radiated Spurious Emissions testing of a UE supporting both GSM 1900 MHz and UTRA FDD II may conduct testing in 2G (GSM) or 3G (UTRA). 1.10. Test Case Execution Environment Device certification shall be conducted with all frequency bands enabled according to its capabilities. Devices shall not be reconfigured for any testing purposes.
1.10.1. Guideline for test case execution of Multi Band-Multi Rat test cases of RFT067
Depending on the frequency bands that are supported by device under test a high amount of possible band configurations for Multi Band-Multi Rat test cases may occur. To reduce testing effort for certification purposes the band combinations are prioritized.
36 3 April 2012
The tests of RFT067 have to be performed according to the following flow-charts:

Start
FDD II ?
FDD V ?
GSM 900 ?
Perform [FDDII-900-FDDV]
FDD IV ?
Perform [FDDII- 900FDDIV] N
End
N Perform [FDDII-1800FDDV]
GSM 1800 ? N
FDD IV ?
Perform [FDDII-1800FDDIV] N
End
End
FDD IV ?
GSM 900 ?
Perform [FDDII900-FDDIV]
End
GSM 1800 ? N
Perform [FDDII1800-FDDIV]
End
N N
End
GSM 900 ?
Perform [FDDII900-FDDII]
End
N Perform [FDDII1800-FDDII]
GSM 1800 ?
End
End
FDD V ?
FDD IV ?
GSM 900 ?
Perform [FDDV-900FDDIV]
End
N Perform [FDDV-1800FDDIV]
GSM 1800 ?
End
N N
End
GSM 900 ?
Perform [FDDV900-FDDV]
End
N N GSM 1800 ? Y Perform [FDDV1800-FDDV] End
End
FDD IV ?
GSM 900 ?
Perform [FDDIV900-FDDIV]
End
GSM 1800 ?
Perform [FDDIV1800-FDDIV]
End
End
End
37 3 April 2012
Table 1: Test case execution plan for 6.2.1.8a.x (x=1, 2, 3) 1st part
Start
FDD I ?
GSM 1900 ?
Perform [FDDI-1900FDDI]
End
N Perform [FDDI-850-FDDi]
GSM 850 ?
End
End
Table 2: Test case execution plan for 6.2.1.8a.x (x=1, 2, 3) 2nd part
Start
FDD II ?
FDD I ?
Perform [FDDII-FDDI]
End
N Perform [FDDII-900]
GSM 900 ?
End
End
Table 3: Test case execution plan for 6.2.1.2a
1.11.
Classmark MessageUE Capability Audit For Initial Certifications and Parent products, the PTCRB Test Laboratory shall ensure that the contents of the Classmark 2 & 3UE capability Information Elements are correctly reported to the network as specified in the devices relevant PICS/PIXIT statements. This shall be achieved by successfully running the validated test cases as follows: GERAN only: TS 51.010-1 test case 26.6.11.2 GERAN/UTRA device: TS 51.010-1 test case 26.6.11.3TS 34.123-1 test case 8.1.5.7 UTRA only device: TS 34.123-1 test case 8.1.5.7 UTRA/E-UTRA device: TS 34.123-1 test case 8.1.5.7
38 3 April 2012
GERAN/UTRA/E-UTRA device: TS 34.123-1 test case 8.1.5.7 E-UTRA only device: TS 36.523-1 test case 8.5.4.1
For any PTCRB Variant / ECO Request, a Classmark Message Audit shall be conducted by PTCRB Accredited Laboratory. This audit is required for all Variant / ECO Requests where the GSM, WCDMA or LTE functionality of the device has been changed or there have been any changes to any feature group functionality. Where MMI only changes have been implemented that have no impact on these areas, the Classmark Audit will not be required. These requirements do not apply to Integrated Devices, i.e. devices embedding a PTCRB-certified module. 1.12. AT-Command Assessment Requirements
1.12.1. AT-Command Applicability
AT-Command assessment is applicable to terminals that support GSMNA AT-Commands. It is limited to all ATcommands supported by the terminal device and is limited to the PTCRB Bearer Agnostic AT-Command Test Specification.
1.12.2. AT-Command Test Specification
The evaluation of AT-Command is the PTCRB Bearer Agnostic AT-Command Test Specification. The latest specification version can be downloaded from PTCRB's web site at www.ptcrb.com.
1.12.3. AT-Command Certification Criteria
All supported AT-commands have to be assessed by the PTCRB accredited test laboratory according to the ATcommand test specification. PTCRB test labs may decide how to perform the test cases and if they wish to use a commercially available test platform. Test cases are not required to be performed under ISO 17025 accreditation.
39 3 April 2012
Test cases are not required to be validated, but it is recommended.
1.12.4.
AT-Command Technical Reference
The following AT-Command specifications are to be used as further references. 3GPP TS 27.005: "3rd Generation Partnership Project; Use of Data Terminal Equipment Data Circuit terminating Equipment(DTE DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)". 3GPP TS 27.007: 3rd Generation Partnership Project; Technical Specification Group Terminals; AT command set for User Equipment (UE) GSMNA AT Commands Specification 1.13. Guidelines for execution of test cases for E-UTRA Test cases for RFT 076
1.13.1. Signaling testing
For signaling test cases, follow the bandwidth guidelines in 3GPP TS 36. 523-1508 section 4.3.1- Test frequencies. For sections 7.1.7.x in 36.523-1, use the operating bandwidth detailed in the Pre-test conditions section for each test case.
1.13.2. RF testing
RF testing should be performed according to 3GPP TS 36.101 section 5.6.1 but using the table below as a replacement for the bandwidths to be tested in particular for the values of the lowest and highest bandwidths. The table shows the PTCRB required bandwidths, these are the only bandwidths that test cases should be performed in at this time. Test cases should be executed according to the 3GPP test specification advises using just these NAPRD03 bandwidth requirements as supported by the device. It may be not necessarily always in line with
40 3 April 2012
the most recent 3GPP core specification requirements.Test cases should be run in all bandwidths that are common between the test specification and the PTCRB required bandwidths.
Additional clarifications: If the test specification requires a test cases to be performed using the bandwidths Lowest, 5MHz, Highest, and according to the table below only 5MHz and 10 MHz are required, the test shall be performed in 5MHz and 10MHz only, (once for each BW). If the test specification shows that a test case is only applicable to 1.4 MHz and this is not shown as required in the table below, the test should not be performed.
E-UTRA RF channel bandwidth required for validation and certification for PTCRB E-UTRA band / channel bandwidth
E-UTRA Band 2 4 5 7 12 13 14 17 24 25 1.4 MHz 3 MHz Yes Yes 5 MHz Yes Yes Yes Yes Yes Yes Yes Yes 10 MHz Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 15 MHz 20 MHz
Yes
2.
Application Enablers Evaluation, General Information

This section defines the requirements for the certification of the Application Enablers that are implemented in the terminal and are required for PTCRB certification.
41 3 April 2012
2.1.1.
Application Enabler (AE) Test Applicability 2.1.1.1. AE Testing Required
All devices supporting application enablers that are applicable for PTCRB certification. Specific details on individual application enabler certification requirements are given in the following sections.
2.1.1.2. AE Testing Not Required
Devices that do not support application enablers PCMCIA cards Variants, re-branded devices having no altered AE implementation from their parent device
2.1.1.3. AE Test Specification
This section lists test specifications applicable to application enablers required for PTCRB certification. The latest approved version of the listed Test Specification shall be used. For validation; if the SDO or standardization forum who has the ownership of the test specification has approved any change requests which are yet to be incorporated into the test specification, then these change requests should be used for validations and referenced in the validation report.
2.1.1.4. ECOs
AE testing must be conducted on an ECO if the associated changes impact any of the following areas: AE Protocol implementation Underlying protocols
42 3 April 2012
If the changes do not impact these areas then AE testing for an ECO is not necessary and the PTCRB accredited lab should provide a declaration to the PTCRB Certification database stating that testing was not required.
2.1.1.5. Application Enabler Certification Criteria
Terminals supporting application enablers required for PTCRB certification shall fulfill all applicable application enabler conformance criteria. The Certification Criteria for application enabler can include both Conformance and Interoperability tests. Conformance testing must be performed in a PTCRB accredited lab, which is approved for the application enabler being tested. Interoperability test results shall be provided by the manufacturer and testing does not have to be performed by a PTCRB accredited lab. Interoperability testing can be proved through Field Trials, Bi-lateral testing and/or multi-lateral events (e.g. Test Fests hosted by OMA). The conditions for the I-lateral testing and/or multi-lateral event results to be accepted for PTCRB Certification are: The manufacturer must submit a declaration stating that the changes (if any) introduced in the implementation tested in the test event, the results of which are being presented for Certification, have not changed the behavior of the functionality tested. These results will be accepted to apply for Certification if they comply to the Certification Criteria All test results shall be submitted to the PTCRB test lab for inclusion in the test report, to obtain the Certification The test configuration must be described and made available in the Certification Declaration Manufacturers are responsible for making all the necessary arrangements to be able to disclose results of Ilateral and/or multi-lateral testing for Certification purposes
43 3 April 2012
Where test Certification Criteria includes Client-to-Client testing, manufacturers are also responsible for seeking the appropriate terminal device to test against, contacting other UE manufacturers on a "reasonable effort" basis As a general recommendation, in 'client to client' testing, the device under test should run the applicable tests against already certified devices if available. If the application enabler implementation has already obtained GCF or PTCRB certification, the manufacturer may choose to re-use the test results under the following conditions The manufacturer can guarantee that no changes in the protocol stack of the enabler for which certification is sought, and in the applicable underlying application protocol stacks like WAP, HTTP, SIP, RTP, RTCP etc., that could affect the AE functionality have been introduced from the AE client version that obtained certification. The manufacturer can guarantee that no changes in the overall AE behavior have been introduced from the version that obtained certification, and no features not included in the original version that obtained certification are added to the AE client that is seeking certification. The manufacturer shall provide all the test results from the testing that was conducted for original certification and any further latest test results, as appropriate.
2.1.1.6. AE Technical Requirements
This section gives details of the application enabler core specifications relevant for PTCRB certification. For validation; the latest approved version, if available, of all the listed specifications should be used. If the SDO or standardization forum that has ownership of the specification has approved any change requests of the content of the specification, which are yet to be incorporated into the document, then these change requests should be used for validations and referenced in the validation report.
44 3 April 2012
2.1.1.7.
AE Options Table/ICS/Test Case Mapping Document
The Options table, ICS or Test Case Mapping Table, as appropriate, is to be filled out by the manufacturer to indicate the features implemented in the client. This shall be submitted by the manufacturer to the PTCRB Certification database as part of the certification submission. If the Options table, ICS or Test Case Mapping table is contained in external specifications a reference to the document should be added to this section. All mandatory features, of the implemented enablers for which certification is sought, as specified in the applicable SDO enabler release specifications shall be implemented in the terminal.
2.1.1.8. AE Interoperability Test Results
This section details how to present IOP test results and information on tested configurations. 2.2. Specific Application Enabler Test Requirements
2.2.1. Multimedia Messaging Service (MMS) 2.2.1.1. MMS Applicability
MMS testing is applicable to terminals that support OMA MMS version 1.0, 1.1, 1.2 or 1.3.
2.2.1.2. Effective Date for MMS Testing
This requirement is effective for devices submitted to a lab for testing on or after October 1, 2004.
2.2.1.3. Transition Period for MMS 1.x Certification
Following the introduction of MMS 1.x certification in PTCRB and GCF there may be a period whereby a manufacturer would have to certify against different versions of MMS schemes for PTCRB and GCF certification due to different validity periods of the NAPRD03 and GCF-CC.
45 3 April 2012
If the situation arises that the NAPRD03 and GCF-CC versions that a manufacturer is certifying against would require different MMS certification schemes to be used, the manufacturer may choose to certify against the same MMS certification scheme as used by GCF. For ECOs, manufacturers may choose to re-certify against the original MMS certification scheme used for initial PTCRB certification.
2.2.1.4. MMS Test Specification
The test plan to be utilized for the evaluation of MMS is the OMA IOP MMS ETS. This test plan can be downloaded from OMA's web site at www.openmobilealliance.org. The following OMA MMS Core specifications are to be used as the basis for all validations:
MMS_1.0: http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.ht ml MMS_1.1: http://www.openmobilealliance.org/Technical/release_program/m ms_v1_1.aspx MMS_1.2: http://www.openmobilealliance.org/Technical/release_program/m ms_v1_2.aspx MMS_1.3:
http://www.openmobilealliance.org/Technical/release_program/m ms_v1_3.aspx 2.2.1.5. MMS Certification Criteria
The test requirements can be found in TC Database. In Client-to-Server tests, the terminal device shall be tested against (at least) three different MMSCs per test case. If there are less than three MMSCs from different manufacturers, the UE manufacturer will make the Best effort to maximize testing and ensure interoperability. PTCRB may tune the number of different MMSCs to test against depending on the test case. It
46 3 April 2012
should be noted that different network radio elements will not be considered as different configurations. In Client-to-Client tests, the terminal device shall be tested against (at least) five different independent clients per test case. If there are less than five different independent clients from different manufacturers, the UE manufacturer will make the Best effort to maximize testing to ensure interoperability. PTCRB may tune the number of different clients to test against depending on the test case. Client to client tests may be performed on a single server and client to server/server to client tests on a single client.
2.2.1.6. MMS Technical Requirements
The following OMA MMS Core specifications are to be used as the basis for all validations. MMS_1.0: http://www.openmobilealliance.org/tech/affiliates/wap/wapi ndex.html MMS_1.1: http://www.openmobilealliance.org/Technical/release_program/ mms_v1_1.aspx MMS_1.2: http://www.openmobilealliance.org/Technical/release_program/ mms_v1_2.aspx MMS_1.3: http://www.openmobilealliance.org/Technical/release_program/ mms_v1_3.aspx
2.2.1.7. Test Case Mapping Table for Terminals supporting MMS
The MMS mapping table is specified in appendix B of the OMA MMS ETS. Appendix B.3 contains the ICS, Appendix B.4 contains the IXIT statements. The ICS/IXIT statements should be completed by the manufacturer and submitted as part of the certification submission.
47 3 April 2012
The mapping table is specified OMA-ETS-ETC-MMS-V1_220060614-D and OMA-ETS-MMS_CON-V1_3-20060725-C for MMS v1.3, respectively or later versions.
2.2.2. Video Telephony (VT) 2.2.2.1. VT Applicability
VT testing is applicable to terminals that support IMTC Video Telephony.

2.2.2.2. VT Test Specification
The evaluation of VT is the IMTC 3G-324M. This test specification can be downloaded from IMTC's web site at http://www.imtc.org/activity_groups/act_3g324m/documents.asp
2.2.2.3. VT Certification Criteria
The VT Conformance test cases are captured in TC Database. In Client-to-Server tests, the terminal device shall be tested against (at least) three different VTs per test case. If there are less than three VTs from different manufacturers, the UE manufacturer will make the Best effort to maximize testing and ensure interoperability. PTCRB may tune the number of different VTs to test against depending on the test case. It should be noted that different network radio elements will not be considered as different configurations. In Client-to-Client tests, the terminal device shall be tested against (at least) five different independent clients per test case. If there are less than five different independent clients from different manufacturers, the UE manufacturer will make the Best effort to maximize testing to ensure interoperability. PTCRB may tune the number of different clients to test against depending on the test case. Client to client tests may be performed on a single server and client to server/server to client tests on a single client.
2.2.2.4. VT Technical Requirements
The following IMTC VT Core specifications are to be used as the basis for all validations.
48 3 April 2012
VT_1.0: http://www.imtc.org/activity_groups/act_3g324m/documents.asp
2.2.2.5. Options Table/ICS/Test case mapping document for Terminals supporting VT
The VT Test Case mapping tools are specified in the IMTC 3G324M Video Telephony Activity Group test specifications. The mapping table is to be found in section 5 of the Compliance test case specification, and section 8 of the Interoperability test specification. The mapping tables are specified in version 3.8 or later of the test specifications. The mapping tables should be completed by the manufacturer and submitted as part of the certification submission.
2.2.2.6. 2.2.2.6.1. MMS Interoperability Test Results Conformance Test Results for Terminals supporting MMS
Manufacturers shall submit the test results and details of tested configurations for the Interoperability Test cases (as specified in TC Database) using the following format. Note: The Client to Client Interoperability Test Cases shall be executed in both directions to test the behavior for sending and receiving. For the sending test cases the terminal to be certified will act as client A as specified in the OMA ETS and for the receiving test cases the terminal to be certified will act as client B. See example below for instructions in filling out the test results table.
49 3 April 2012
Client to Client Interoperability Test Cases
OMA MMS ETS Reference No. Description #1
Test Count #2 #3 #4 #5
Comments
1.1
Interoperability Test Case 1 Interoperability Test Case 1 Interoperability Test Case 1 Interoperability Test Case 1
C7 S2
C2
C5
C4
C6
1.2
C7 S1
C2
C5
C4
C6
1.3
C7 S2
C2
C5
C4
C6
1.4
C7 S3
C2
C5
C4
C6
Client to Server / Server to Client Interoperability Test Cases
OMA MMS ETS Reference No. Description #1
Test Count #2 #3
Comments
2.1 2.2 2.3
Interoperability Test Case 6 Interoperability Test Case 7 Interoperability Test Case 8
S1 n/a S1
S2 n/a nS
S3 n/a nS
The following abbreviations are used in the Interoperability Test Results tables to identify the Test Configuration. In the Header #1#N = Test Execution Count
50 3 April 2012
In the Entry Field

C1CN = Test Case executed, client or server with identifier N used Test Case executed, server with identifier N used Test is not applicable since the MMS Option is not supported by the terminal No further clients supporting this test are commercially available No further servers supporting this test are commercially available
S1N
n/a
nC
nS
Test Case executed means, that no fault or problem with the Device Under Test (DUT) was encountered at this Interoperability Test.
Configuration used for Client to Client Interoperability Testing
TEST CLIENTS TESTED AGAINST I C Manufacturer Model IMPS Release SW version (opt.)
1 2 3 4 5 N
51 3 April 2012
Configuration used for Client to Server / Server to Client Interoperability Testing
Infrastructure Information II 1 IM Server Details Presence Server
Manufacturer
SW Version
Manufacturer
SW Version
Group Server
SMS Server (optional)
Manufacturer
SW Version
Manufacturer
SW Version
IM Server
Presence Server
Manufacturer
SW Version
Manufacturer
SW Version
Group Server
Manufacturer
SW Version
Manufacturer
SW Version
IM Server
Presence Server
Manufacturer
SW Version
Manufacturer
SW Version
Group Server
Manufacturer
SW Version
Manufacturer
SW Version
52 3 April 2012
Note: In case the server manufacturer's server includes all services in one "IMPS" server, only IM Server needs to be filled in.
2.2.3. 2.2.4. 2.2.5. 2.2.6. Deleted Deleted Deleted Device Management 2.2.6.1. Device Management Applicability
Device Management testing is applicable to all devices that support OMA Device Management version 1.2
2.2.6.2. Device Management Test Specification
The evaluation of Device Management is the OMA ETS-DM. This test specification can be downloaded from OMA's web site at www.openmobilealliance.org.
2.2.6.3. Device Management Certification Criteria
The Device Management test cases are captured in TC Database.

2.2.6.4. Device Management Technical Requirements
The following OMA device Management Core specifications are to be used as the basis for all validations. DM 1.2: http://www.openmobilealliance.org/Technical/release_program/d m_v1_2.aspx
2.2.7. Secure User Plane Location (SUPL) 2.2.7.1. Secure User Plane Location (SUPL) Applicability
SUPL testing is applicable to terminals that support OMA SUPL version 1.0 or 2.0.
53 3 April 2012
2.2.7.2.
SUPL Test Specification
The evaluation of SUPL is the OMA ETS-SUPL. This test specification can be downloaded from OMA's web site at www.openmobilealliance.org.
2.2.7.3. SUPL Certification Criteria
The SUPL Conformance test cases are captured in TC Database.

2.2.7.4. SUPL Technical Requirements
The following OMA SUPL Core specifications are to be used as the basis for all validations. SUPL_1.0: http://www.openmobilealliance.org/Technical/release_program/s upl_v1_0.aspx SUPL 2.0: http://www.openmobilealliance.org/Technical/release_program/s upl_v2_0.aspx
2.2.8. Browsing 2.3 2.2.8.1. Browsing 2.3 Applicability
Browsing testing is applicable to all devices that support OMA Browsing version 2.3.
2.2.8.2. Browsing 2.3 Test Specification
The test plans for the evaluation of Browsing are OMA ETSETS-XHTMLMP and OMA ETS-WCSS. These test specification can be downloaded from OMA's web site at http://www.openmobilealliance.org/Technical/release_program/b rowsing_v23.aspx
2.2.8.3. Browsing 2.3 Certification Criteria
The Browsing test cases are captured in TC Database.
54 3 April 2012
2.2.8.4.
Browsing 2.3 Technical Requirements
The following OMA Browsing Core specifications are to be used as the basis for all validations. Browsing 2.3: http://www.openmobilealliance.org/Technical/release_program/b rowsing_v23.aspx
2.2.8.5. Browsing 2.3 Interoperability Test Results
The Client to Server test cases from GCF-CC need to be tested once against any web server with the OMA Browsing Test Suite
55 3 April 2012
Client to Server Interoperability Test Cases
The following abbreviations are used to identify the Test Verdict: Ex = Test Case executed, no fault or problem with the Device Under Test (DUT) was encountered. n/a = Test is not applicable since the Browser Option is not supported by the terminal Manufacturers shall submit the test results for the Interoperability Test cases (as specified in TC Database) using the following format:
OMA Browsing ETS-Reference Test Case ID Test Case Description
Comments Result
Interoperability Test Case 1 Test Procedure 1 Test Procedure 2 Test Procedure 3
56 3 April 2012
Configuration used for Client to Server Interoperability Testing
INFRASTRUCTURE INFORMATION Details
1 Manufacturer
WAP GW/ WEB Server
SW Version
Enabler Release
2 Manufacturer
WAP GW / WEB Server
SW Version
Enabler Release
3 Manufacturer
WAP GW/ WEB Server
SW Version
Enabler Release
2.2.9.
FUMO 2.2.9.1. FUMO Applicability
FUMO testing is applicable to all devices that support OMA FUMO version 1.0.
2.2.9.2. FUMO Test Specification
The test plan for the evaluation of FUMO is OMA ETS FUMO V1.0. This test specification can be downloaded from OMA's web site at http://www.openmobilealliance.org/Technical/release_program/f umo_v1_0.aspx
2.2.9.3. FUMO Certification Criteria
The FUMO test cases are captured in TC Database.

2.2.9.4. FUMO Technical Requirements
The following OMA FUMO Core specifications are to be used as the basis for all validations.
57 3 April 2012
FUMO 1.0: http://www.openmobilealliance.org/Technical/release_program/f umo_v1_0.aspx

2.2.9.5. FUMO Interoperability Test Results
The Client to Server test cases from NAPRD03 need to be executed at least once against any OMA-DM server supporting FUMO (S1S3).
The following abbreviations are used to identify the Test Verdict: Ex = Test Case executed, no fault or problem with the Device Under Test (DUT) was encountered. n/a = Test is not applicable since the FUMO Option is not supported by the terminal nS = No server supporting this test is commercially available Manufacturers shall submit the test results and details of tested configurations for the Interoperability Test cases (as specified in TC Database) using the following formats:
OMA FUMO ETS Reference No. 1 2 3 Description Interoperability test case 1 Interoperability test case 2 Interoperability test case 3 Test Count S1 S2 S3 Comments

S1 Servers tested against (S) OMA-DM/ FUMO Server Manufacturer SW Version S2 OMA-DM/ FUMO Server Manufacturer SW Version
Enabler Release Enabler Release
58 3 April 2012
S3
OMA-DM/ FUMO Server Manufacturer SW Version
Enabler Release
2.1.10.
SCOMO 2.2.9.6. SCOMO Applicability
SCOMO testing is applicable to all devices that support OMA SCOMO version 1.0.
2.2.9.7. SCOMO Test Specification
The test plan for the evaluation of SCOMO is OMA ETS SCOMO V1.0. This test specification can be downloaded from OMA's web site at http://www.openmobilealliance.org/Technical/release_program/s como_v1_0.aspx
2.2.9.8. SCOMO Certification Criteria
The SCOMO test cases are captured in TC Database.

2.2.9.9. SCOMO Technical Requirements
The following OMA SCOMO Core specifications are to be used as the basis for all validations. SCOMO 1.0: http://www.openmobilealliance.org/Technical/release_program/s como_v1_0.aspx
2.2.9.10.
SCOMO Interoperability Test Results
The Client to Server test cases from NAPRD03 need to be executed at least once against any OMA-DM server supporting SCOMO (S1S3).
The following abbreviations are used to identify the Test Verdict:
59 3 April 2012
Ex = Test Case executed, no fault or problem with the Device Under Test (DUT) was encountered. n/a = Test is not applicable since the SCOMO Option is not supported by the terminal nS = No server supporting this test is commercially available Manufacturers shall submit the test results and details of tested configurations for the Interoperability Test cases (as specified in TC Database) using the following formats:
OMA SCOMO ETS Reference No. 1 2 3 Description Interoperability test case 1 Interoperability test case 2 Interoperability test case 3 Test Count S1 S2 S3 Comments

S1 Servers tested against (S) OMA-DM/ SCOMO Server Manufacturer SW Version S2 OMA-DM/ SCOMO Server Manufacturer SW Version OMA-DM/ SCOMO Server Manufacturer SW Version
Enabler Release Enabler Release Enabler Release
S3
60 3 April 2012

PTCRB Process

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

PTCRB Process

Diunggah oleh

Hak Cipta:

Format Tersedia

Permanent Reference Document NAPRD03

Version Specific Technical Overview of PTCRB Mobile/User Equipment Type Certification

Date: April 3, 2012 Classification: Binding, Semi Restricted

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

Mobile Station Certification Test Requirements

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

3GPP TS 51.010 (formerly GSM 11.10) 3GPP TS 51.010-4.

3GPP TS 36.521 3GPP TS 36.523

ETSI TS 102 694 (SWP) ETSI TS 102 695 (HCI)

PTCRB 1997-200812 Version 5.11

PS attach / rejected / PLMN not allowed / Procedure 1

PTCRB 1997-20082 Version 5.11

12.4.2.4 4 12.4.2.5a Proc 14

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

Mobile Station RF Performance Evaluation:

CTIA OTA Test Plan

PTCRB 1997-200812 Version 5.11

CTIA OTA Test Plan

PVG.03 (latest version)

PTCRB Bearer Agnostic AT-Command Test Specification (latest version)

OMA ETS SCOMO V1.0

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

Roman numerals must be used to differentiate between UTRA & EUTRA.

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

UTRA Band Selection for Protocol Testing (Single Band Only)

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

E-UTRA Band Selection for Protocol Testing (Single Band Only)

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

Addition of Tests to Category "E"

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

RF Performance Testing Not Required

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11

Radiated Spurious Emissions

PTCRB 1997-200812 Version 5.11

The tests of RFT067 have to be performed according to the following flow-charts:

Perform [FDDII- 900FDDIV] N

N N GSM 1800 ? Y Perform [FDDV1800-FDDV] End

PTCRB 1997-20082 Version 5.11

Table 3: Test case execution plan for 6.2.1.2a

PTCRB 1997-200812 Version 5.11

PTCRB 1997-20082 Version 5.11