OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
Open Development Device
Certification Process
This document provides initial information related to the Verizon Wireless Open Development. All
information herein is subject to change without notice. The information provided was considered
technically accurate at the time the documents were developed, but Verizon Wireless disclaims
and makes no guaranty or warranty, express or implied, as to the accuracy or completeness of
any information contained or referenced herein. VERIZON WIRELESS DISCLAIMS ANY
IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR
PURPOSE.
The developer of any Device, service or product for use on the Verizon Wireless network
assumes all risks related to the development of such Device, service or product. Verizon
Wireless does not guarantee or warrant the availability of its network or the compatibility of its
network with any Device, service or product. Verizon Wireless disclaims liability for any damages
or losses of any nature whatsoever whether direct, indirect, special or consequential resulting
from the use of or reliance on any information contained or referenced herein.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 1
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
Document #: SP-OA-ST-08-0003
Contents
REVISION HISTORY ............................................................................................ 3
1
OBJECTIVE ................................................................................................ 65
2
GLOSSARY AND DEFINITION OF TERMS ............................................... 76
3
DEVICE COMPLIANCE PROCESS ............................................................ 98
3.1
Entrance Criteria ...............................................................................................................................98
3.2
Pre-Submission Process Flow .........................................................................................................109
3.3 OD Compliance Testing ....................................................................................................................12
3.3.1
Early Testing Process Flow ........................................................................................................12
3.3.2
OD Standard Lab Testing Process Flow .....................................................................................13
3.3.3
Additional Testing ......................................................................................................................14
3.4
Device Introduction Process Flow ....................................................................................................17
3.5
ODS Agreement Violation Process Flow ..........................................................................................20
3.6
Device Evolution or Certification Expiration Process Flow ...........................................................21
3.7
Device Maintenance & Regression Testing Process Flow ..............................................................22
3.8
Test Lab Contact information .........................................................................................................23
4
REFERENCES ............................................................................................ 26
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 2
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
Revision History
Rev.
1.0
2.0
3.0
4.0
5.0
6.0
7.0
8.0
9.0
10.0
11.0
12.0
13.0
13.1
13.2
13.3
13.4
13.5
13.7
13.9
14.0
15.0
Version 27
Revision History
Initial ODIS Testing Document
Modifications to add process details,
LBS/aGPS and ENAP
Modificationss after technical review
Modifications after legal review
Adding requirements lock down process
Adding language to address export control
concerns Section 3.8
Modifications to Device Introduction
Process Flow Section
Add MMS, Global and Telematics Device
support
RA process modifications and Vendor
meeting agenda details
Process updates
Add unit requirements, 3rd party contact
name change, edits from review
Add ODPT mailbox to Pre-submission
process flow and to Device introduction
process flow; Modifications to Unit
requirements
Replace Developer Agreement with
Certification Agreement. Updated contact
list.
Added VzW owns the test reports (Section
3.2.4)
Modifications to Device Introduction
Process Flow Section (Section 3.4)
Removed Authors names
Added forecast worksheet to DLD
Legal review additions
Update DLD Agenda
Updated per legal feedback
General updates
Removed section 3.10.
Added VPS – Vertical Solutions Provider.
Added ppt 1 pager to pre-submission forms.
Added sample Device to DLD agenda and
reqs.
Changed photo in 3.3.
Changed available activations w/ approved
Date
March 2008
June 2009
June 2009
June 2009
August 2009
August 2009
September 2009
November 2009
January 2010
February 2010
March 2010
April 2010
May 2010
May 2010
May 2010
May 2010
May 2010
May 2010
June 2010
June 2010
© Verizon Wireless 2010 -- All Rights Reserved
Page 3
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
16.0
17.0
18.0
19.0
20.0
21.0
22.0
23.0
24.0
25.0
26.0
27.0
Version 27
module to 20.
Updated SGS Contact Info to Johee from
Dawn.
Section 3.2.1 – Added Master Showcase to
required docs and DLD agenda, added
some clarity on how to register a new
Device
Section 3.5 – Mentioned new instructions
on OD Portal uploads exist on the site.
Section 3.3.3 - updated the flow and
requirement for MMSC Server Test.
Replaced CPE with NDET
Section 3.5 – updated the Device
Introduction process
Section 3.5 – Updated the Device CSV
process
Section 3.5 – Updated the wait window with
cut off time
Section 3.6 – Added sample Device
requirements
Section 3.7 – Updated the Certification
Expiration
Section 3.3.1 – Concession Accounts
All sections – Changed LBS to LBS/aGPS
Section 3.5 Updated IMEI/ICCID pair
January 2013
instructions
Section 3.2 – Updated DLD agenda
December 2013
Section 3.3 – Updated testing process
Section 3.4 – Updated time window for ESN
upload
Section 3.8 (former Section 3.9) – Added
new ITL
Section 3.1 – Updated export control link
July 2014
Section 3.2 – Added LTE M2M SIM to DLD
agenda
Section 3.4 – Removed recommendation
for EDI
Section 3.8 – Updated test lab information
Section 3.1 – Added Software Update
support for 4G devices
Section 3.1 – OTA ID info
Section 3.3.2 – Clarification on test results
Section 3.2 – Simplified DLD call agenda
November 2014
August 2015
© Verizon Wireless 2010 -- All Rights Reserved
Page 4
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
Section 3.8 – SGS address change and
added Wireles Research Center
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 5
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
1 Objective
The purpose of this document is to define and describe the Open Development Device
Certification process, Device testing and conformance requirements that Devices must
meet before they are certified for use on the Verizon Wireless Network.
This document includes requirements that cover voice Devices, voice/data Devices, and
data only Devices. This includes, but not limited to, handsets, PDAs, data cards, M2M
Devices, embedded PCs, and more.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 6
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
2 Glossary and Definition of Terms
aGPS
Assisted GPS
AM
Account Manager
B2B
Business to Business
CDMA
Code Division Multiple Access
CDG
CDMA Development Group
CA
Certification agreement
CE
Conformité Européenne, "European conformity"
CPE
Customer Premise Equipment
DLD
Device Lock Down
DMD
Device Management Database
EDI
Electronic Data Interchange
ENAP
Early Network Access Program
ESN
Electronic Serial Number
FIT
Field Interoperability Testing
GCF
Global Certification Forum
IOT
Interoperability
ITL
Independent Test Laboratory
LBS
Location Based Services
MEID
Mobile Equipment Identifier
MDN
Mobile Directory Number
MMS
Multi Media Messaging services
MMSC
Multimedia Messaging Service Center
NDET Lab
Network Device Evaluation Test Laboratory
NDRA
National Direct Revenue Assurance
NRB
Network Repair Bureau
NSRA
National SurePay Revenue Assurance
NWRA
National Wholesale Revenue Assurance
OEM
original equipment manufacturer,
OD
Open Development
ODPT
Open Development Product Team (Including Business Development
and Account management.)
ODS
Open Development Specification
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 7
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
OTA
Over The Air
PDI
Product Development and Integration
PM
Product Manager
RA
Revenue Assurance
RF
Radio Frequency
RN
Release Notes
SFN
Safe For Network
TECC
Test Entrance Criteria Checklist
VSP
Vertical Solutions Provider
WS
Wholesale
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 8
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
3 Device Compliance Process
3.1 Entrance Criteria
All Devices must be type approved and certified by the United States Federal
Communications Commission (FCC) and classified by the Department of Commerce's
Bureau of Industry and Security (BIS) before ODIS Conformance testing can commence.
All Global GSM capable Devices, requesting GSM and CDMA certification by VZW,
must receive GCF certification and CE Certification in addition to FCC certification
before ODIS Conformance testing can commence.
Each OD DEVELOPER will receive a unique VZW-ID. The VZW-ID will be used in
conjunction with a PRODUCT-ID of the submitted Device (assigned by the
DEVELOPER), the OTA-ID and the RF unit's FCC ID to form the Device tracking ID.
Verizon Wireless and OD Authorized ITL will identify individual Devices prior to
Certification using only this Device tracking ID.
The OD Device Tracking ID
 VZW-ID will be assigned for each DEVELOPER submitting a Device for
Conformance
 Example VZW01000001
 PRODUCT-ID (Model Number) Assigned by the DEVELOPER
o Up to 10 alphanumeric characters
 OTA-ID Assigned by the DEVELOPER
o In accordance with the Open Development Specification (ODS) OTA
requirements the OTA-ID is a numeric representation of a two individual
binary components
 mob_model 8 bits
 mob_firm_rev 16 bits
o If the DEVELOPER is using a Verizon Wireless approved module, then the
module vendor’s OTA ID can be used.
o N/A for LTE Only Devices
 FCC-ID Required Prior to Open Development Conformance
o FCC Grantee ID (First 3 Characters)
o FCC Product Code (Remaining up to 14 Characters)
o https://fjallfoss.fcc.gov/eas/Eas731Welcome.do
o Example “A1C0123456789012”
 BIS ECCN and CCATS Required Prior to Open Development Conformance
o Example " 5A992, G0823456"
 http://www.bis.doc.gov/index.php/forms-documents/doc_view/142-eccnpdfOD-Certified ITL will report test results back to Verizon Wireless using only
the OD Device Tracking ID
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 9
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
All 4G LTE and 4G LTE Multi-Mode devices must have capabilities to support
Software/Firmware Update Over-The-Air.
3.2 Pre-Submission Process Flow







Open Development Device Developer (referenced as DEVELOPER) visits Web
Portal
DEVELOPER registers via Web Portal – Partner logs into the OD Portal using their
VZWID and registers the Device by “adding a new Device”. The model the Device is
registered as should match exactly what’s provided in the DMD form and should
reflect what the Device is being marketed and sold as.
http://opennetwork.verizonwireless.com/getDeviceCertified_startCert.aspx
In order for developer to access any Open Development (OD) documents,
DEVELOPER must register by providing the following:
o Name
o Company
o Title or Position
o Full mailing address to include country
o Email address
o Contact phone number(s)
DEVELOPER downloads Open Development Specification (ODS) and OD presubmission documents and takes note of any posted notes to the documentations
page.
Developer product preparation
DEVELOPER completes and submits the NDA questionnaire, Partner forecasting
worksheet, TECC form, Release notes, Device data sheet (DEVELOPER format),
Master Showcase excel document, Power Point Device / Solutions One Pager, and
DMD form. The DMD and Forecasting worksheet will be provided after agreements
are executed as applicable. Forecasting worksheet is not required for wholesale
Devices.
NDA, and/or Wholesale agreements are executed as applicable. Wholesale Devices
cannot use the Verizon mark.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 10
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS







Open Development Certification Agreement and VSP Agreement executed as
applicable. This will allow for the use of the Verizon mark. Note: This process may
take 1-3 months or longer to complete.
DEVELOPER receives a list of OD Authorized Independent Test Lab(s) (ITL) from
ODPT. DEVELOPER makes a decision on which ITL to use.
DEVELOPER sends an email to VZWOpenDevelopment-1@VerizonWireless.com
(or to the supporting VZW representative) requesting a VZW-ID, which will enable
access to the Device certification portal, with the following information:
o Channel
o Current VZW contact
o DEVELOPER’s info:
First Name
Last Name
Email
Company
Address
City
State/Province
Zip
Country
Phone
Mobile
Fax
DEVELOPER adds information regarding the new Device and its attributes onto the
portal using the company VZW ID log-in.
DEVELOPER submits all required information on the OD portal and notify their
supporting VZW representative.
A Device Lock Down (DLD) meeting will be held between DEVELOPER and VZW
team to review the Device submission. The meeting agenda will cover the following:
o Submission Overview
o Device Certification Agreements
o Documentation Review
o Discuss Test Campaign
o Testing & Schedule
o Sample Devices
o Go to Market – Verizon Process for Production Device Launch
Pending the successful completion of the DLD requirements, Verizon will notify the
selected ITL with the approval to start and the required testing.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 11
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
3.3 OD Compliance Testing
The following figure shows a high level view of the Open Development
certification process.
3.3.1 Early Testing Process Flow
DEVELOPER may request early testing depending on the need of development prior to
certification. ODPT/NDET will review the request and approve based on the need for live
network testing during development.
Early Network Access Program (ENAP)
If the DEVELOPER is using a Verizon Wireless certified module, up to 20
activations can be allowed for developmental purposes. Upon receiving the request
with the Device background information, VZW will load the Test Device(s)
MEID/ESN/IMEI in DMD. The developer should then work with their VZW sales
representative to subscribe and activate lines to connect the Test Device(s) with VZW
network. Upon being certified, the Test Device MEID/ESN/IMEIs must be uploaded to
the DMD using the OD portal or EDI feed.
Safe For Network (SFN)
If the DEVELOPER completes SFN testing successfully, up to 500 activations per
project can be allowed for further development. DEVELOPERS must submit the
Device information for ODPT/NDET to review and the testing must be conducted at a
OD Authorized ITL.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 12
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
Testing Process
 Vendor submits Device information on the portal and sends ENAP or SFN request
with supportive reasons and test ESNs/MEIDs/IMEIs.
o RN, TECC, and Device Solution One Pager are required for SFN. ODPT and
NDET team review and approve the ENAP or SFN request.
 For SFN:
o DEVELOPER contacts and contracts with OD Authorized ITL.
o DEVELOPER enters Device into OD Authorized ITL for SFN testing.
o OD Authorized ITL completes testing and submits test results to NDET Lab.
o NDET Lab verifies Device meets all SFN requirements
o Upon successful completion, DEVELOPER may request up to 500 activation,
and notifies ODPT team via email that they are ready to start network testing
 Approved test ESNs/MEIDs/IMEIs are provisioned on the network for Test Devices.
 DEVELOPER completes OTA testing - debug /fix /retest issues.
 DEVELOPER is ready for OD full compliance submission
 ODPT notifies DEVELOPER to disconnects test MDNs no later than 60 day after
testing is completed
 DEVELOPER notifies ODPT that all test MDNs are disconnected.
3.3.2 OD Standard Lab Testing Process Flow

DEVELOPER works directly with IOT Lab(s) on schedule, payment and complete
IOT testing prior to or in parallel with OD required testing.

DEVELOPER chooses and contacts an OD Authorized ITL from the Verizon
Wireless approved list (see Section 3.8)
DEVELOPER submits required Devices and product documentation to the OD
Authorized ITL.
The OD Authorized ITL executes Verizon Wireless approved test plans based on the
TECC for conformance against ODIS.
The OD Authorized ITL provides test results to ODPT and NDET teams.



Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 13
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS



o Verizon Wireless owns the test results for the OD compliant Device..
NDET Lab then validates with the ITL that the submitted Device has met the
requirements of the ODIS. This step in the process is the only official
acknowledgement that the Device successfully passed the required testing.
If the Device meets the requirements of the ODIS, the Device is OD compliant::
The Verizon Wireless NDET Lab may choose to work directly with certain wholesale
channel DEVELOPERs for testing against the ODIS.
At this point, Device Lab testing is completed. Testing and DMD population with
the Device profile are required before certification. Receiving all ESN/MEIDs/IMEIs
into DMD per Section 3.4 is required before Devices can be activated.

If the Device does not meet the requirements of the ODIS:
o DEVELOPER is notified via acceptable electronic media
o DEVELOPER chooses one of the following paths forward:
 Dispute resolution (DEVELOPER does not agree with OD
Authorized ITL results)
 Device rework (DEVELOPER returns to OD Authorized ITL for retesting)
 DEVELOPER withdraws its Device.
3.3.3 Additional Testing
OD Standard Lab testing completion is prerequisites to all other testing.
3.3.3.1 LBS/aGPS Application Testing Process Flow






After OD Standard Lab Test completion, DEVELOPER may start the LBS/aGPS
process.
DEVELOPER submits the "OD LBS/aGPS pre-certification Requirements" document
(application)
ODPT and PDI review and approve OD LBS/aGPS application
ODPT works with Network PDI on target LBS/aGPS application testing.
DEVELOPER submits Test Devices for network LBS/aGPS application testing.
Network team evaluates the test results and approves the application.
3.3.3.2 MMS Device Testing Process Flow
Devices that are MMS capable and require the use of Verizon MMSC server must
complete the MMS process before Device certification.
If the Device hgg
 DEVELOPER submits the completed MMS Profile questionnaire as part of the TECC
form submission. The form is part of the TECC template
 DEVELOPER works directly with Nokia Siemens Networks (NSN) on schedule,
payment and complete MMS IOT testing.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 14
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS








DEVELOPER provides Device profile questionnaire emailed to Verizon Wireless
MMS Admin at VZWMMSAdmin@VerizonWireless.com, three weeks prior to the
start of testing at NSN IOT Lab.
VZW MMS Admin reviews and approves the MMS profile.
Verizon Wireless generates and ODPT distributes the User Agent to the
DEVELOPER.
DEVELOPER can proceed with NSN IOT testing on the set schedule date.
NDET reviews and approves the MMS IOT results report.
After approval of the MMS IOT results, DEVELOPER prepares 2 Devices for MMSC
Server Testing:
o DEVELOPER provisions each Device with the new assigned MMS User
Agent
o DEVELOPER ensures each Device is able to send, receive, forward, and
reply to a MMS.
o DEVELOPER sends the ESNs/MEIDs/IMEIs of each Device to ODPT
DEVELOPER sends 2 Devices to Verizon Wireless with batteries, data cables,
chargers and instructions to changing MMSC URL through either PST or
programming menu (name and address will be provided by Verizon).
ODPT tests to ensure the Device profile is loaded to Verizon’s network.
3.3.3.3 Revenue Assurance Testing Process Flow
Revenue assurance testing may be required to ensure the usage billing is processed
correctly and in compliance with the approved pricing.
 ODPT team shall determine RA testing can start.
 ODPT shall obtain the ESNs/MEIDs/IMEIs of the Devices to be used in RA testing
from the Developer.
 ODPT team shall contact appropriate Revenue assurance team (Wholesale, Direct)
and provide the ESNs/MEIDs/IMEIs.
 RA team shall provision those ESNs/MEIDs/IMEIs with mobile numbers.
 ODPT team shall advise DEVELOPER the Device has been provisioned and is
ready to be activated.
 DEVELOPER activates the Devices.
 DEVELOPER ships Devices directly to the appropriate Revenue Assurance testers
with the NDET Lab approved SW and HW versions.
 DEVELOPER will activate the Devices.
 Revenue Assurance team conducts the testing and approves the usage billing.
 ODPT populates individual Device’s profile in DMD based on the DMD form
completed by the DEVELOPER.
 ODPT provides DEVELOPER with Device certification approval with an expiration
date not to exceed 36 months from the time of the date of the approval per the
Certification Agreement.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 15
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
3.3.3.4 Inactivity and Test Devices



If the certification status remains inactive for more than 2 months, the Device may be
subjected to another review to be compliant with the latest Verizon Wireless
Specifications.
OEM must deactivate all Test Devices after certification completes.
Test Devices shall not be sold as final products.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 16
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
3.4 Device Introduction Process Flow
After the Device is approved and before the Device goes to market, the Device
must be entered into VERIZON WIRELESS Device Management Database (DMD)
as the certified Device to allow the future activation. This Process is known as the
Device identification upload (ESN/MEID for 3G Devices or IMEI for 4G Devices).
If the Device identification is not loaded into the DMD, the system will prevent the
Devices from activation. The DEVELOPER can upload the Device identifications using
one of the following approaches:
1. Electronic Data Interchange (EDI). A 24 hour window is needed for the
system to process the EDI upload.
2. ODI Web Portal - This option is available only for Devices using VERIZON
WIRELESS approved module. A 15-minute window is needed for the system
to process the ODI Web Portal upload.
If either of the two processes described above is not followed, the VERIZON
WIRELESS’s system will prevent the Devices from activation.
 If the Device identifications are uploaded via EDI or the OD Portal before 10:30pm,
EST, the Device identifications will map to DMD and will be ready for activation next
morning (after midnight)
o Example: File sent by 10:25pm, EST on a Tuesday, file will map to DMD
on Wednesday morning at 12am, EST
 If the Device identifications are uploaded via EDI or the OD Portal after 10:30pm, the
ESNs/MEIDs/IMEIs will map to the DMD the following 2nd business day
o Example: File sent after 10:30pm, EST on a Wednesday, will map to
DMD on Friday morning at 12am, EST
Electronic Data Interchange (EDI)
 ODPT provides DEVELOPER with Electronic Data Interchange (EDI) requirements
and credentials for accepting Device technical information submission.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 17
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS




DEVELOPER setup the EDI feed with VERIZON WIRELESS to connect the
electronic feed with VERIZON WIRELESS’s Device Management Database (DMD)
ODPT provides DEVELOPER the OD SKU number for the approved Device
DEVELOPER/ODPT verifies the EDI feed for the Device is linked to the OD SKU
properly. OEM is expected to take 5 ESNs/MEIDs/IMEIs previously loaded as Test
Devices and uploaded via the EDI feed to the Device SKU number, and send the 5
ESNs/MEIDs/IMEIs to ODPT for verification. Upon verification, VZW will change the
5 ESNs/MEIDs/IMEIs back to Test Devices.
DEVELOPER uploads individual Device specific technical data (including ESNs/
MEIDs/IMEIs/ICCIDs, Make, Model) to the provided OD SKU to populate the Device
information in the DMD.
ODI Web Portal
 DEVELOPER captures all of the Device identifications (ESNs/MEIDs/IMEIs) in a
Comma-Separated Value (CSV) file as followed:
o The ESNs/MEIDs/IMEIs will start on the first line of the first column. For
Devices with IMEI & ICCID pairings the IMEIs will be placed in column A and
ICCIDs will be placed in column B
o The name of the file should not contain any special characters (e.g. spaces,
dashes, quotation marks, etc) and must contain the make, model and total
number count of ESNs/MEIDs/IMEIs or IMEI/ICCIDs loaded).
o Example of the.csv file:
File Name: CompanyXYZ_ProductABC_5.csv
ESN/MEID/IMEI:


IMEI/ICCID pair:
DEVELOPER logs into OD Web Portal, click on the “Upload ESN/MEID” link/tab next
to the approved Device.
In the upload screen select the format of the serial numbers that will be uploaded.
The format must be one of the following:
o
o
o
o
Version 27
IMEI (14 or 15) numeric or alpha
MEID (14) alpha numeric only
ESN HEX (8) alpha numeric only
IMEI/ICCID Pair- IMEI(14 or 15) numeric or alpha & ICCID (16) alpha only
© Verizon Wireless 2010 -- All Rights Reserved
Page 18
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS





It is very important to select the correct file content type since the upload process will
check the format accordingly.
Once the DEVELOPER uploads the Comma-Separated Value (CSV) file of Device
identification (ESNs/MEIDs/IMEIs or IMEI/ICCID pairs) via the OD portal, the file is
automatically approved and uploaded if the file format is correct. An email
notification is automatically sent to ODPT and the DEVELOPER providing notice that
an ESN/MEIDIMEI file has been uploaded and automatically approved.
The Device identification (ESNs/MEIDs/IMEIs or IMEI/ICCID pairs) provided in the
.csv approved file will take up to 1 business day to load into the Verizon Wireless
Device Management Database system.
Open Development certified approved Devices are available for activation once the
(ESNs/MEIDs/IMEIs or IMEI/ICCID pairs) are loaded into the Verizon Wireless
Device Management Database system.
Deactivated Test Devices to be sold as production Devices shall be reuploaded by DEVELOPER as certified Devices via OD portal or EDI.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 19
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
3.5 ODS Agreement Violation Process Flow
Upon knowledge of any Rogue Devices, Applications or Violations to OPEN
DEVELOPMENT CERTIFICATION AGREEMENT with Verizon Wireless the
following will take place:
 ODPT notifies DEVELOPER of Device compliance issue (rogue Devices or
applications detected)
 Developer will ship 2 sample Devices within 48 hours upon receiving the formal
request from Verizon for re-testing.
 ODPT takes remedial/immediate action to safeguard the Verizon Wireless network –
Verizon Wireless retains the right to restrict or eliminate individual OD Device access
to the Verizon Wireless network if Verizon Wireless has concerns about harm to the
Network.
 If ODPT determines that the issues are the results of Device evolution and the
DEVELOPER had prior knowledge of the potential impact on Device acceptance
status:
o ODPT suspends Device certification status (ESN/MEID/IMEIs in the DMD are
placed into a suspended state to prevent any potentially harmful Devices
from being activated onto the Verizon Wireless Network).
o DEVELOPER initiates and enters Device Maintenance & Regression Testing
Process Flow (see Section 3.7).
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 20
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
3.6 Device Evolution or Certification Expiration Process
Flow
Device Evolution: At any time, in case of any updates to the certified software or
hardware, DEVELOPER must notify ODPT and provide all submission
documentations to ODPT
 DEVELOPER provides all submission documents with the Device changes in
detailed descriptions
 ODPT/NDET determines the level of testing required based on the updated
Device.
 DEVELOPER initiates Device Maintenance & Regression Testing Flow
Certification Expiration: All Verizon Wireless Open Development Certified Devices
have a certification period of 3 years. The DEVELOPERs must initiate requests to
retired or to extend the Device Certification period for each Device 90 days prior to
the expiration date of the current certification. Devices seeking recertification may
be subjected to go through Device Maintenance & Regression Testing to be
compliant with the latest Verizon Wireless Specifications. If the DEVELOPER
chooses to retire the Device or does not take any actions, all future Device
activations will be blocked after the Certification period expires.
 DEVELOPER notifies ODPT the decision on whether to retire the Device or to
extend the Certification 90 days prior to the Certification period expires.
 If the plan is to retire the Device, then
o DEVELOPER sends the Re-Certification Request Form to ODPT
o Verizon will not accept future activations of the Device.
 If the plan is to extend the Certification, then
o DEVELOPER sends the Release Notes & Re-Certification Request Form
to ODPT
o ODPT/NDET determines the level of testing required based on the
current Verizon specifications.
o DEVELOPER submits Device for Device Maintenance & Regression
Testing.
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 21
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
3.7 Device Maintenance & Regression Testing Process
Flow
Device Maintenance & Regression Testing Flow
 DEVELOPER submits updated TECC, RN and DMD to ODPT/NDET Lab for
evaluation.
 DEVELOPER coordinates with the OD Authorized ITL to execute regression
testing (In coordination with Verizon Wireless NDET Lab).
 Verizon Wireless retains the right to, at its sole discretion, to introduce and
remove requirements from the ODIS.
 DEVELOPER submits required Devices and documentation to OD Authorized
ITL.
 OD Authorized ITL executes Verizon Wireless OD regression test plans for
continued conformance against ODIS.
 OD Authorized ITL provides DEVELOPER Device results (standardized media
and file formats).
 If the Device meets regression test criteria in ODIS, the OD Authorized ITL
forwards the results to the ODPT and the Verizon Wireless NDET Lab to verify
that the Device meetings the ODIS.
o Upon notification from the OD Authorized ITL & approval from the VZW
NDET Lab, ODPT provides DEVELOPER a new Certification Notice for a
three year period.
o DEVELOPER has option to conduct OD Best Practice testing.
 If the Device does not meet the testing criteria DEVELOPER may choose one of
the following paths forward:
o Dispute resolution (DEVELOPER does not agree the Authorized ITL results).
o Device rework (DEVELOPER returns to OD Authorized ITL to continue when
the Device is ready).
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 22
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
3.8 Test Lab Contact information
Authorized Independent Test Lab Information
ITL Name
Technology
Supported
Address
URL
Contact #1
Phone
Fax
Email
7 Layers Inc.
LTE Only
ITL Name
Technology
Supported
Address
CETECOM Inc
LTE Only
URL
Contact #1
Phone
Fax
Email
ITL Name
Technology
Supported
Address
15 Musick, Irvine, CA, 92618
www.7layers.com
Boris Binger
949-297-8054
Boris.Binger@7Layers.com
6370 Nancy Ridge Dr.,
Suite 101
San Diego, CA / 92121
www.cetecom.com
Amol There – Program Manager
858-362-2401
Amol.There@cetecom.com
Intertek Labs
2G/3G, LTE Only, LTE Multimode
Email
731 Enterprise Drive
Lexington, KY 40510
http://www.intertek.com/wireless-mobile/Devices/
Gwyn McNew - Wireless Engineering Manager
859-226-1072
859-226-1050
Gwyn.Mcnew@intertek.com
Contact #2
Phone
Fax
Email
Robbie Payne
859-226-1084
859-226-1050
Robbie.Payne@intertek.com
URL
Contact #1
Phone
Fax
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 23
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
ITL Name
Technology
Supported
Address
URL
Contact #1
Phone
Fax
Email
ITL Name
Technology
Supported
Address
URL
Contact #1
Phone
Fax
Email
ITL Name
Technology
Supported
Address
URL
Contact #1
Phone
Fax
Email
Contact #2
Phone
Fax
Email
ITL Name
Version 27
PCTEST Engineering Laboratory, Inc.
2G/3G, LTE Only, LTE Multimode
Project Mgr. Carrier/Infrastructure Testing
6660-B Dobbin Road
Columbia, MD 21045
http://www.pctestlab.com/
Andrea Zaworski - Laboratory Manager
410-290-6652
andrea@pctestlab.com
SGS Wireless U.S., Inc.
2G/3G, LTE Only, LTE Multimode
15150 Avenue of Science
Suite 300
San Diego, CA 92128
http://www.sgs.com/
Dawn Saad – LTE Operations manager
858-592-7100 x19122
858-592-7107
Dawn.Saad@sgs.com
Tech Mahindra (Americas)
2G/3G, LTE Only, LTE Multimode
STE 203,
1001 Durham Avenue,
South Plainfield, NJ 07080
www.techmahindra.com
Arunav Roy
469-600-7846
arunav.roy@techmahindra.com
Upesh Kumar
732-310-0285
upeshku@techmahindra.com
Wireless Research Center
© Verizon Wireless 2010 -- All Rights Reserved
Page 24
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
Technology
Supported
Address
URL
Contact #1
Phone
Email
OTA
3331 Heritage Trade Dr. Suite 101,
Wake Forest, NC 27587
http://wirelesscenter-nc.org/
Larry Steffann
919-435-1051 x112
larry.steffann@wirelesscenter-nc.org
Contact #2
Randle Sherian
Phone
Email
919-435-1051 x102
randle.sherian@wirelesscenter-nc.org
Inter-Operability (IOT) Test Labs
IOT Test Lab
Name
Contact
Phone
Email
Alcatel-Lucent
IOT Test Lab
Name
Contact
Phone
Email
Telefonaktiebolaget LM Ericsson
IOT Test Lab
Name
Contact
Phone
Email
Nokia Siemens Networks
Version 27
Liza Ottesen
+1 908-582-6861
Liza.ottesen@alcatel-lucent.com
Joe Bruccoliere
+1 972-583-9056
Joe.bruccoliere@ericsson.com
Alison Myers
+1 682-233-0167
alison.myers@nsn.com
© Verizon Wireless 2010 -- All Rights Reserved
Page 25
OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
4 References
1. CDG-90, Global Handset Requirements for CDMA – CDMA200 Voice, SMS, and
Data, version 2.2, September 28, 2997
2. CDG-148, CDMA Device Requirements — CDMA2000 1xEV-DO Release 0 &
Revision A, Version 1.5, December 22, 2007
3. CDG-143, Recommended System Selection Requirements for 1X and 1xEV-DOCapable Terminals, Version 1.0, March 15, 2007
4. RFC 2486 - The Network Access Identifier, January 1999
5. RFC 4784 - DMU requirements
6. 3GPP2 C.S0011-C v2.0 Recommended Minimum Performance Standards for
cdma2000 Spread Spectrum Mobile Stations, March 2006
7. 3GPP2 C.S0033-A v2.0 Recommended Minimum Performance Standards for
cdma2000 High Rate Packet Data Access Terminal, September 2007
8. 3GPP2 C.S0036-0 v1.0 Recommended Minimum Performance Specification for
C.S0022-0 Spread Spectrum Mobile Stations, March 2002
9. 3GPP2 C.S0037-0 v1.0 Signaling Conformance Specification for cdma2000
Wireless IP Network, April 2002
10. 3GPP2 C.S0038-A v2.0 Signaling Conformance Specification for High Rate
Packet Data Air Interface, April 2007
11. 3GPP2 C.S0043-0 v1.0 Signaling Conformance Test Specification for cdma2000
Spread Spectrum Systems, October 2004
12. 3GPP2 C.S0060-0 v1.0 Signaling Conformance Test Specification for Over-theAir Service Provisioning, December 2005
13. 3GPP2 C.S0061-0 v1.0 Signaling Conformance Test Specification for Short
Message Service, June 2005
14. 3GPP2 C.S0062 Signaling Conformance Test Specification For CDMA2000 Data
Services, version 1.0, May 2007
15. 3GPP2 C.S0066-0, Version 1.0, Over-the-Air Service Provisioning for MEIDEquipped Mobile Stations in Spread Spectrum Systems, August 27, 2004
16. 3GPP2 C.S0072, Version 1.0, Mobile Station Equipment Identifier (MEID)
Support for cdma2000 Spread Spectrum Systems Revision 0, July 2005
17. 3GPP2 C.S0073, Version 1.0 Signaling Test Specification for Mobile Station
Equipment Identifier (MEID) Support for CDMA2000 Spread Spectrum Systems,
September 26, 2005
18. 3GPP2 S.R0006-529-A Wireless Features Description: Emergency Services,
version 1.0, June 2007
19. 3GPP2 S.R0048-A, Version 3.0, 3G Mobile Equipment Identifier Stage 1,
September 23, 2004
Version 27
© Verizon Wireless 2010 -- All Rights Reserved
Page 26