O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 1
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.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 2
Document #: SP-OA-ST-08-0003
Contents
1 Objective 8
2 Glossary and Definition of Terms 9
3 Device Compliance Process 11
3.1 Entrance Criteria and Certification Process 11
3.1.1 Device Entrance Criteria 11
3.1.2 Overall Certification Process Flow: 12
3.2 Certification Process 12
3.3 Required Agreements/Documents 13
3.4 OD Compliance Testing 13
3.4.1 Early Testing Process Flow 14
3.4.2 OD Standard Lab Testing Process Flow 16
3.4.3 Auto-Certification Platform Testing Process Flow 16
3.4.4 Additional Testing for Verizon Services (If features are supported by
the device) 17
3.4.4.1 LBS/aGPS/SUPL Application Testing Process Flow 17
3.4.4.2 MMS Device Testing Process Flow 17
3.4.4.3 Private Network Testing 17
3.4.4.4 4G Private Network 17
3.4.4.5 On Site (Private) 5G Network 17
3.4.4.6 Device Management Services 18
3.4.4.7 Verizon Diagnostics 18
3.4.4.8 Verizon Base-band FOTA 18
3.4.4.9 Verizon Application FOTA 18
3.4.4.10 Verizon Response Verified 18
3.4.4.11 Inbound Permanent Roaming 19
3.4.4.12 Guidelines for Penetration Testing for Parent/Child Devices 19
3.4.4.13 Guidelines for Device eUICC Certification 20
3.4.5 Inactivity 22
4 Post Certification Device ID Upload Procedure 23
4.1 EDI 23
4.2 OD ODP 23
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 3
4.2.1 Single Device ID Upload 23
4.2.2 Dual Device ID Upload 25
4.2.2.1 2 Physical SIMs mapped to a Single Device SKU 25
4.2.2.2 2 Electronic SIMS 25
4.2.2.3 1 Physical SIM and 1 Electronic SIM 26
5 OD Certification Agreement Violation Process Flow 28
6 Device Evolution, Maintenance & Regression Testing Process Flow 29
6.1 Device Evolution: 29
6.2 Device Maintenance & Regression Testing Process 29
7 Test Lab Contact information 30
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 4
Revision History
Rev
Revision History
Date
1.0
Initial ODIS Testing Document
March 2008
2.0
Modifications to add process details, LBS/aGPS
and ENAP
June 2009
3.0
Modificationss after technical review
4.0
Modifications after legal review
June 2009
5.0
Adding requirements lock down process
June 2009
6.0
Adding language to address export control concerns
Section 3.8
August 2009
7.0
Modifications to Device Introduction Process Flow
Section
August 2009
8.0
Add MMS, Global and Telematics Device support
September 2009
9.0
RA process modifications and Vendor meeting
agenda details
November 2009
10.0
Process updates
January 2010
11.0
Add unit requirements, 3
rd
party contact name
change, edits from review
February 2010
12.0
Add ODPT mailbox to Pre-submission process flow
and to Device introduction process flow;
Modifications to Unit requirements
March 2010
13.0
Replace Developer Agreement with Certification
Agreement. Updated contact list.
April 2010
13.1
Added VzW owns the test reports (Section 3.2.4)
May 2010
13.2
Modifications to Device Introduction Process Flow
Section (Section 3.4)
May 2010
13.3
Removed Authors names
May 2010
13.4
Added forecast worksheet to DLD
May 2010
13.5
Legal review additions
May 2010
13.7
Update DLD Agenda
May 2010
13.9
Updated per legal feedback
June 2010
14.0
General updates
June 2010
15.0
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 module
to 20.
16.0
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
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 5
Section 3.5 – Mentioned new instructions on OD
Portal uploads exist on the site.
17.0
Section 3.3.3 - updated the flow and requirement for
MMSC Server Test.
Replaced CPE with NDET
18.0
Section 3.5 – updated the Device Introduction
process
19.0
Section 3.5 – Updated the Device CSV process
20.0
Section 3.5 – Updated the wait window with cut off
time
Section 3.6 – Added sample Device requirements
21.0
Section 3.7 – Updated the Certification Expiration
22.0
Section 3.3.1 – Concession Accounts
All sections – Changed LBS to LBS/aGPS
23.0
Section 3.5 Updated IMEI/ICCID pair instructions
January 2013
24.0
Section 3.2 – Updated DLD agenda
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
December 2013
25.0
Section 3.1 – Updated export control link
Section 3.2 – Added LTE M2M SIM to DLD agenda
Section 3.4 – Removed recommendation for EDI
Section 3.8 – Updated test lab information
July 2014
26.0
Section 3.1 – Added Software Update support for
4G devices
November 2014
27.0
Section 3.1 – OTA ID info
Section 3.3.2 – Clarification on test results
Section 3.2 – Simplified DLD call agenda
Section 3.8 – SGS address change and added
Wireless Research Center
August 2015
28
Removed reference section, updated lab contact
October 2016
29
Updated acronyms
Added overall flow
Added new Required Agreement section
Added additional testing sub-sections
Updated links
Updated Lab contacts
Clarified other sections throughout the doc
May 2017
30
Removed ECCN link
Updated Required Agreements section
Clarified FOTA updates
Updated EDI upload section, added EID
Updated Lab contacts
March 2018
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 6
31
● Section 7. Updated Technical contact for
Tech Mahindra
● Section 7. Updated Test lab name from P3 to
Umlaut
● Section 7. Updated Contact for Nokia
Feb 2020
32
● Section 3.4.1 Updated conditions for Early
Network Access Program devices and Safe
For Network devices
● Section 7. Updated 7Layers into Bureau
Veritas
● Section 7. Added Aircom Labs
● Section 7. Merged Nokia IOT lab and Motive
lab
● Section 7. Updated information for Approved
Verizon 3
rd
party labs
July 2020
33
● Section 7. Added Carve Systems, Spirent,
Altredis Partners, and Palindrome as
approved 3
rd
party test labs.
● Section 3.4.1 Updated conditions for ENAP
devices
● Section 4.2.2 Added Dual Device ID Upload
instructions.
● Updated Section 3.1 to include statement on
Verizon FOTA support and IoT device
security compliance and testing.
October 2020
34
● Section 3.4.1 Updated conditions for ENAP
devices using approved embedded modem
● Added section 3.4.3 Auto-Certification
Platform Testing Process Flow
● Updated Section 3.4.4 for Verizon Services
(Verizon Diagnostics, Verizon Baseband
FOTA, Verizon Application FOTA)
● Updated Bureau Veritas lab information
January 2021
35
● Guidelines for Penetration testing for
Parent/Child devices
● User Account and login policies management
description per Security Audit item 4C
● IoT Security Process changes for Chipsets
and Modules (Compliance presented and
reviewed prior to DLD with approved waivers
in place for non-compliance)
● Added Private 4G and Private 5G sections
July 2021
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 7
● References provided for Verizon Response
Verified (VRV) and Inbound Permanent
Roaming processes
36
● eUICC (reference eUICC process
documentation
● IoT Security change to “Penetration Testing”
for appropriate 3rd party labs
● 3rd party lab - Aircom, PC Test and Element
Materials Technology
June 2022
37
● Update process for up to 1200 test devices if
device is using an approved module and
device OEM has PTCRB/GCG/CTIA test
reports from approved 3
rd
party labs for
Verizon LTE bands.
Sept 2022
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 8
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. “Device(s)”
means the product, equipment, parts, and components tested for OD Compliance.
This document describes the methods and procedures used to certify voice Devices,
voice/data Devices, and data only Devices. This includes, but is not limited to,
PDAs/Handhelds, data cards, M2M/IoT Devices, embedded PCs, and more.
*Available from web ODP under ‘Requirement & Test Plan Documentation
’ tab (login
required).
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 9
2 Glossary and Definition of Terms
aGPS
Assisted GPS
AM
Account Manager
B2B
BIS
Business to Business
Bureau of Industry and Security
CDMA
CCATS
Code Division Multiple Access
Commodity Classification Automated Tracking System
CDG
CDMA Development Group
CA
Certification agreement
CE
COI
Conformité Européenne, "European conformity"
Certificate of Insurance
CSV
DLD
Comma-Separated Values
Device Lock Down
DMD
DTO
Device Management Database
Device Test Owner
EDI
EID
Electronic Data Interchange
eUICC ID (Embedded Universal Integrated Circuit Card) ID
ENAP
Early Network Access Program
ESN
ECCN
Electronic Serial Number
Export Control Classification Number
ICCID
Integrated Circuit Card Identifier
IMEI
International Mobile Equipment Identifier
FIT
Field Interoperability Testing
FOTA
Firmware Over The Air
GCF
Global Certification Forum
IOT
IoT
Interoperability Testing
Internet of Things
ITL
Independent Test Laboratory
LBS
M2M
Location Based Services
Machine to Machine
MEID
Mobile Equipment Identifier
MDN
Mobile Directory Number
MMS
Multi Media Messaging services
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 10
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
ODP
Open Development Portal
ODPT
Open Development Product Team (Including Business Development,
Certification Owners and Account management.)
ODS
Open Development Specification
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
SUPL
Secure User Plane Location
TECC
Test Entrance Criteria Checklist (Test Campaign)
VSP
Vertical Solutions Provider
WS
VZW
Wholesale
Verizon Wireless
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 11
3 Device Compliance Process
3.1 Entrance Criteria and Certification Process
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 Open Development (OD) Conformance
testing can commence.
OEMs or OD Device Developers (collectively, “DEVELOPER,”) requesting Verizon
Wireless’ (VZW) certification for LTE capable Devices must receive GCF certification
before OD Conformance testing can commence.
All LTE capable Devices must support radio layer Firmware Over The Air (FOTA)
updates. All devices using an approved module that supports Verizon FOTA
capabilities must be tested to ensure that the Verizon FOTA capability of the
module is still functional.
All chipsets and modules brought for approval or devices that are brought to
Verizon for certification must provide appropriate security compliance
documentation and/or security compliance test results
prior to DLD. Any non-
compliant security features needs to be disclosed to Verizon, and if Verizon
agrees to the non-compliant features, a waiver must be submitted and approved
prior to the chipset or module DLD.
In order for DEVELOPER to access the OD web portal or OD documents, DEVELOPER
must execute a Non-Disclosure Agreement (NDA).
Each DEVELOPER will receive a unique VZW-ID after completing NDA. The VZW-ID
will be used in conjunction with the submitted Device to form the Device tracking ID.
VZW and OD authorized Independent Test Laboratory (ITL) will identify individual
Devices prior to Certification using only this Device tracking ID.
Developer user accounts are created under the company registration to allow access to
the Verizon Open Development web portal. Users will be notified after 90 days of user
account inactivity that they have 30 days to log in to the OD development web portal to
keep their user accounts active. If the user has not logged into their account for 120
days, the account will be made inactive and the user will need to contact the Open
Development team to reactivate their user account. If a user account is inactive for 180
days, the account will be deleted, per Verizon Corporate Security requirements, and the
user will need to have another user on the company account submit a new user account
request.
3.1.1 Device Entrance Criteria
The OD Device Tracking ID
● VZW-ID will be assigned for each DEVELOPER submitting a Device for
Conformance
⮚ Example VZW01000001
● FCC-ID Required Prior to Open Development Conformance
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 12
o FCC Grantee ID (First 3 Characters)
o FCC Product Code (Remaining up to 14 Characters)
o https://www.fcc.gov/oet/ea/granteecode#block-menu-block-4
o Example “A1C0123456789012”
● BIS ECCN and CCATS Required Prior to Open Development Conformance
o Example " 5A992, G0823456"
3.1.2 Overall Certification Process Flow:
Obtaining Device certification and launching a Certified Device on the VZW network
involves fulfilling technical and the contractual requirements of the CA. The CA is a
contract issued by Verizon and jointly signed by the DEVELOPER; review can occur in
parallel to device registration and testing.
●
● Developer Registration and Executing NDA – This allows full access to ODP and
detailed documents, such as requirements, test plans, etc.
● Add new Device(s) – This involves a five step process on the ODP
o New Device Info
o Marketing Info
o Forecast
o Release Notes
o Attaching all Pre-submission Documents
● DLD - Review and lockdown documents
● Testing - Send device(s) to authorized lab for testing
● FOTA – DEVELOPER to provide FOTA update documentation on a test device.
● Completing Contractual Agreements – Fulfilling CA and COI documents are
required prior to device certification.
● Device ID Upload and Launch – Loading Device IDs into Verizon Device
Management Database (DMD) system.
3.2 Certification Process
● After the DEVELOPER executes the NDA, accounts will be created to access the
ODP at https://opendevelopment.verizonwireless.com/
● DEVELOPER downloads and reviews the OD certification documentation.
● DEVELOPER adds information regarding the new Device and submits all required
information on the ODP and notifies their supporting VZW representative. The
registered device name/model number should reflect the marketing name/model
number as it appears in any FCC filing or approval.
Developer
Registration
and
executing
NDA
Add new
Device(
s)
DLD
Device
Launch
Testing
Certification Agreement (CA)
and Certificate of Insurance
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 13
● A DLD review will be held between DEVELOPER and VZW team. The review will
cover the following:
o Submission Overview
o Device Certification Agreements
o Documentation Review
o Review Test Campaign
o Review Testing & Schedule
o Review of Developer’s Sample Devices - Besides ITL, DEVELOPER is
required to send 2 samples to VZW ODPT.
o Complete required compliance testing in Verizon authorized ITL
● Pending the successful completion of the DLD requirements, VZW will upload the
Test Campaign (TECC) to the ODP and notify the DEVELOPER and selected ITL
with Approve To Start test (ATS).
● A host device is certified using an approved module or chipset. A module or chipset
is approved through the ODP. For module and chipset approval, refer to Module
Guidelines from Requirement & Test Plan Documentation section of the ODP.
3.3 Required Agreements/Documents
All Open Development Agreements must be executed prior to Device Approval.
● NDA – Execution required prior to full access to ODP.
● CA – Must be executed before device can be fully certified. This will allow use
of Verizon mark with a written request per Verizon Branded Guidelines.
● COI – Issued by the DEVELOPER and must be provided to Verizon as proof of
valid insurance.
(NOTE: As of January 2018, Verizon Wireless and companies with a current
Certification Agreement executed prior to then shall no longer execute an
addenda for each newly certified device. Certification of devices will be
memorialized in the OD Notice of Certification that contains any device specific
requirements and will include the Certification Period for the device).
3.4 OD Compliance Testing
The following figure shows a high level view of the OD required testing process known
as OD Compliance Testing:
Any Device (including a test Device) must have a FCC ID before activation on the
Verizon Network.
Review
Device info
Device
Lock Down
Approved
to Test
In
Testing
Post
Results
Results
Approval
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 14
3.4.1 Early Testing Process Flow
DEVELOPER may request early testing if development is required prior to certification.
The ODPT will review the request and approve it if there is a need for live network
testing during development.
Early Network Access Program (ENAP)
● If the DEVELOPER is using a VZW certified module, up to 20 activations can be
allowed for developmental purposes. Without a VZW certified module, up to 2
activations can be allowed for developmental purposes. Upon uploading of test
Device IMEIs to the ODP, 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. The test MDNs
must be disconnected no later than 60 day after testing is completed. In order to
obtain approval for more than 20 test device IMEI activations, the OEM must have
agreed to the terms of the Certification Agreement, and provided the Certification
Manager for the device with a detailed business justification detailing: the need for
additional test devices; a list of persons/entities who will be using the additional
devices; where the additional devices will be used; for what length of time the
additional devices be needed; and the current target date for completing device
certification. The Verizon Open Development certification team will consider the
requests for the additional test devices over the 20 device limit and will approve or
deny the request, based on the business justification, at its discretion. If the business
case is approved, the device OEM will be allowed to update the additional test
device IMEIs for approval by their assigned device certification manager.
● If the DEVELOPER is using a VZW approved embedded modem, up to 20
activations can be allowed for developmental purposes. Upon the uploading of
test Device IMEIs to the ODP, 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. The
test MDNs must be disconnected no later than 60 day after testing is completed. In
order to obtain approval for more than 20 test device IMEI activations, the OEM must
have agreed to the terms of the Certification Agreement, and provided the
Certification Manager for the device with a detailed business justification detailing:
the need for additional test devices; a list of persons/entities who will be using the
additional devices; where the additional devices will be used; for what length of time
the additional devices be needed; and the current target date for completing device
certification. The Verizon Open Development certification team will consider the
requests for the additional test devices over the 20 device limit and will approve or
deny the request, based on the business justification, at its discretion. If the business
case is approved, the device OEM will be allowed to update the additional test
device IMEIs for approval by their assigned device certification manager.
● DEVELOPER shall not activate or use test devices on the Verizon Wireless network
other than for internal testing purposes prior to device certification while such devices
are in ENAP testing. ENAP test devices are to be used by the DEVELOPER for
development and testing of devices in preparation for certification test activities only.
Such test devices should not be activated and used on the Verizon Wireless network
in connection with end customer activities.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 15
Safe For Network (SFN) Testing
● If the DEVELOPER completes SFN testing successfully, up to 500 activations
per project can be allowed for further development purposes. DEVELOPERS
must submit the Device information for the ODPT’s review and the SFN testing must
be conducted at a VZW Authorized ITL.
DEVELOPERS submit Device information on the ODP and send a test Device
request with supportive reasons and test ESNs/MEIDs/IMEIs.
o RN, TECC, and Device Solution One Pager are required for SFN.
o ODPT and NDET team review and approve the request.
Upon successful completion of SFN, DEVELOPER can request up to 500 activations of
test Devices. All the SFN activated devices must be kept under the device OEM’s
own mobile account or ECPD (Enterprise Customer Profile Database) ID account
and remain in the possession and control of the device OEM. The device OEM must
also update the device SW to the final certification version once full certification is
complete.
●
If the DEVELOPER plans to sell the test devices as commercial products after approval, the
DEVELOPER must manage these test devices as commercial products and upload them
again (e.g., Note:
Test Devices to be sold as production Devices shall be re-
uploaded by DEVELOPER as certified Devices via ODP or EDI).
Extended test devices for pilots and trials if using a Verizon approved module and
the device OEM has successfully completed PTCRB, CTIA or GCF testing on the
Verizon bands in a Verizon approved 3
rd
party lab.
● If the DEVELOPER completes PTCRB, CTIA, or GCF testing successfully on the
Verizon frequency bands at a VZW Authorized ITL, up to 1200 activations per project
can be allowed for further development purposes. DEVELOPERS must submit the
Device information for the ODPT’s review and the PTCRB, CTIA, or GCF testing
must be conducted at a VZW Authorized ITL and the reports uploaded under the
device submission.
DEVELOPERS submit the Device information on the ODP and send a test Device
request with supportive reasons and test ESNs/MEIDs/IMEIs.
o RN, TECC, and Device Solution One Pager are required for SFN.
o ODPT and NDET team review and approve the request.
Upon successful completion of PTCRB, CTIA, or GCF testing
at a VZW Authorized ITL,
DEVELOPER can request up to 1200 activations of test Devices. All the SFN
activated devices must be kept under the device OEM’s own mobile account or
ECPD (Enterprise Customer Profile Database) ID account and remain in the
possession and control of the device OEM. The device OEM must also update the
device SW to the final certification version once full certification is complete.
●
If the DEVELOPER plans to sell the test devices as commercial products after approval, the
DEVELOPER must manage these test devices as commercial products and upload them
again (e.g., Note:
Test Devices to be sold as production Devices shall be re-
uploaded by DEVELOPER as certified Devices via ODP or EDI).
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 16
3.4.2 OD Standard Lab Testing Process Flow
● DEVELOPER should work with ODPT to obtain a TECC.
● DEVELOPER works directly with IOT labs on schedule, payment and complete IOT
testing prior to or in parallel with lab conformance testing.
● DEVELOPER chooses and contacts a Verizon authorized ITL from the VZW
approved list (see Section 7).
● DEVELOPER submits required Devices and product documentation to the ITL.
● It is responsibility of the DEVELOPER to provide FOTA update documentation
(either their own/proprietary solution, from Module vendor, or from Verizon/Motive
solution). This can be submitted while the device is in testing, but required with final
results.
● The ITL executes VZW approved test campaign based on the TECC.
● The ITL provides test results to ODPT.
● ODPT reviews the test results, along with FOTA solution documentation and either
passes, conditionally passes or fails the device.
● After the Device successfully passes testing, ODPT will certify the Device and issue
an official notification.
3.4.3 Auto-Certification Platform Testing Process Flow
The Auto-Certification Platform (ACP) is a simple, cost-effective platform that
enables OEM self-testing for supported GCF and Verizon test plans for devices, chipsets
and modules.
Before the ACP can be shipped to an OEM the following conditions must be met:
● Confirm device readiness by completing Device lockdown (DLD) with
Certification manager
● Certificate of Insurance (COI) completed
● Review the ACP Prerequisites document (including Host PC requirements)
shared by Certification manager during DLD and confirming that OEM is able to
meet them
● Submit account registration at https://vzwdt.com/acpportal/
The ACP can only be shipped to business addresses in the United States, and only to
persons directly employed by the OEM. The ACP cannot be sent internationally by the
receiving company to locations outside the United States without prior approval of
Verizon. Export Regulations mandate that it can only be shipped by OEM to approved
countries. Please check with your certification manager on international shipping
destinations.
For any issues with ACP setup and testing, there is a ticketing system setup to contact
ACP support and details are provided in the Prerequisites document.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 17
3.4.4 Additional Testing for Verizon Services (If features are
supported by the device)
OD Standard Lab testing completion is a prerequisite to additional testing. Details for
additional testing are available in the Requirement and Test Plan Documentation section
of the ODP.
3.4.4.1 LBS/aGPS/SUPL Application Testing Process Flow
After OD Standard Lab Test completion, DEVELOPER may start the LBS/aGPS/SUPL
process. Refer to “
LBS/aGPS Certification Submission Package” for more
information.
3.4.4.2 MMS Device Testing Process Flow
The MMS process must be completed before Device certification for Devices that
are MMS capable and require the use of the Verizon MMSC server Refer to the
‘VZW OD MMSC Server Test Process
’ for more information.
3.4.4.3 Private Network Testing
Applicable to Devices using the Verizon Private Network. Refer to Private
Network section on ODP.
3.4.4.4 4G Private Network
Verizon’s On Site LTE is a transformative new wireless networking solution that
essentially places a fully contained, private wireless network on the premises of
customer facilities/campuses. On Site LTE is referenced in the industry as a
private LTE network, bringing small cell wireless technology to large campuses.
Applicable LTE devices supporting On Site (Private) network should follow “LTE
Data Device requirements” and “On-Site (Private) Network test plan”.
This test plan should be performed at Verizon Waltham Lab facility and should be
performed by the Verizon testing team. OEMs can contact Jagan Pandurangan
> or Raj Thambirajah
<[email protected]> at the Verizon Waltham Lab to schedule
testing and ship devices.
3.4.4.5 On Site (Private) 5G Network
On Site 5G adds 5G Ultra Wideband (UW) small cells and related capabilities to
an On Site LTE deployment. So, enterprises can specify a custom-designed,
private network that has the range and scale to match today’s needs and adapt
quickly to emerging capabilities.
Applicable 5G devices supporting On Site (Private) 5G network should follow
“LTE Data Device requirements” and “On-Site (Private) Network test plan”, in
addition to the existing Verizon macro network requirements and test process.
This test plan should be performed at Verizon Waltham Lab facility and should be
performed by the Verizon testing team. OEMs can contact Jagan Pandurangan
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 18
<[email protected]> or Raj Thambirajah
<[email protected]> at the Verizon Waltham Lab to schedule
testing and ship devices.
3.4.4.6 Device Management Services
Refer to Verizon OMADM 1.2 Reference Client Package or Verizon light weight
M2M (LWM2M) OTADM Reference Client Package on ODP.
3.4.4.7 Verizon Diagnostics
All modules and chip-on-board devices OEMs have to run LWM2M Diagnostics
testing. Refer to Reqs-LWM2M document and the ACP support team to utilize
ACP box for Verizon LWM2M Diagnostics testing.
3.4.4.8 Verizon Base-band FOTA
Verizon Firmware Over The Air (FOTA) is a Mobile Software Management
(MSM) technology in which the module’s (or chipset’s) base-band firmware can
be wirelessly upgraded by Verizon. Verizon base-band FOTA uses OMADM or
OMA LWM2M industry standards. More information can be found in the “OD
FOTA Compliance Instructions and Testing Guidelines'' document under ‘Device
Management Services’ on the OD Partner Portal.
3.4.4.9 Verizon Application FOTA
Verizon Firmware Over The Air (FOTA) is a Mobile Software Management
(MSM) technology in which the application (AP) firmware of a host device can be
wirelessly upgraded by Verizon. Verizon Firmware Over The Air (FOTA) uses
OMADM or OMA LWM2M industry standards.
3.4.4.10 Verizon Response Verified
Verizon Response Verified offers a standard process for OEMs to verify that their
devices are ready for public safety applications. It provides a centrally managed
web platform for OEMs to register, test and validate results. Plus, it gives public
safety customers a unified place to view all verified devices.
In order to qualify for the Verizon Response Verified program for public safety
customers, OEM devices need to achieve these benchmarks:
● National capability
● Available 24/7 customer care
● Dedicated separate web page associated with the device provided by
OEMs for public safety customers
● Compliance with latest published open development security
requirements
● Testing to validate compliance with Verizon device requirements
● Diagnostics available and included
● Over-the-air upgrades available and included
● Supporting sales and operations resources available
● Installation and maintenance contract either available or included
● Support of Verizon IoT Security Credentialing or equivalent
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 19
End customers will be responsible for:
● Keeping devices up to date with over-the-air updates
● Activating and operating the device on Verizon’s Public Safety Core for
network security
● Using Verizon SIM-Secure (recommended)
● Using Verizon IoT Security Credentialing (recommended)
● Complying with the terms and conditions of the public safety plan under
their approved Verizon government contract
More information can be found in the “Verizon Response Verified Certification
Process” and “Verizon Response Verified Certification Test Plan” documents
under ‘Device Management Services’ on the OD Partner Portal.
3.4.4.11 Inbound Permanent Roaming
Verizon deems devices to be non-incidentally roaming in its network if any of the
following criteria is met:
● Home operator (also referred to herein as “Connectivity Service Provider”
or “CSP” deems device to be roaming non-incidentally on the Verizon
network
● Device is not in a mobile application and fixed (e.g. alarm panels), or has
a limited range (e.g. farming equipment),
● Device is used on the Verizon network for 3 or more consecutive monthly
billing cycles and such usage exceeds 60% of the global traffic usage for
such Device; or
● Device is activated by CSP with a non-US based profile but device is
otherwise registered or licensed in the United States (e.g., an automobile
or recreational vehicle with a US-based license plate).
If these criteria are met, then there is a specific certification process to be
followed for the device certification. A detailed primer document on the Inbound
Permanent Roaming certification process can be found under the Requirements
and Test Plan documentation section of the Open Development portal.
3.4.4.12 Guidelines for Penetration Testing for Parent/Child
Devices
Some devices may require evaluation by a Verizon approved 3rd party security
evaluation company for penetration testing. Penetration testing is performed by
evaluating the device’s hardware and software structure, and designing a test
methodology to identify and exploit the device hardware and software
vulnerabilities to malicious acts. If a family of devices are approved to have a
single Parent device and one or more Child devices by the OD certification
manager and penetration testing is required, the device OEM will need to provide
a separate penetration report for each Parent and Child device.
The penetration report for the Parent device should include the following:
● Device Information (Model #, HW version, OS version, SW version)
● Scope of the penetration test for the Parent device.
● Findings and results of the penetration testing for the Parent device.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 20
o Note: If there are any findings of device vulnerabilities found
during penetration testing and they have not been corrected, a
waiver request with a plan/schedule to fix them will need to be
submitted for the Parent device.
The penetration report for the Child device should include the following:
● Device Information (Model #, HW version, OS version, SW version)
● A comparison matrix between the Parent and Child devices.
● Scope of the penetration test for the Child device based on an evaluation
of the differences between the Parent and Child devices.
o If it is determined that there is no additional testing needed
because the threat scope of the Child device is the same or a
subset of the threat scope of the Parent device, the report should
document this fact.
● Findings and results of the penetration testing for the Child device if
additional penetration testing was needed beyond what was performed
for the Parent device.
o If there are any findings of device vulnerabilities found during
penetration testing on the Child device and they have not been
corrected, a waiver request with a plan/schedule to fix them will
need to be submitted for the Child device.
● Scope of the penetration test for the Parent device. The scope can be
copied from the penetration test report of the Parent device, which
includes the Device Information of the Parent device.
● Findings and results of the penetration testing for the Parent device.
These can be copied from the penetration report of the Parent device.
o If there are any findings of device vulnerabilities found during
penetration testing on the Parent device and they have not been
corrected on the Child device, the waiver identifier from the Parent
device should be included.
3.4.4.13 Guidelines for Device eUICC Certification
Some device OEMs may choose to utilize an eUICC, which will allow the device to either
download a Verizon SIM profile remotely through Remote SIM Provisioning (RSP) or
switch between a preloaded Verizon or other MNO profile. The device may support
either the Consumer eUICC architecture (using SM-DP+) or the M2M eUICC
architecture (using SMSR and SM-DP).
If the device will be utilizing the M2M eUICC architecture, then the below prerequisites
must be met ahead of submitting for OD certification:
● Device OEMs shall comply to Verizon Wireless LTE_3GPP_B13_NetworkAccess
requirement section 1.3.1.3.15 eUICC (M2M eUICC sections only)
● Device should have the capability to change APNs using AT commands
● Device should be able to handle image configurations when ICCID switches from
one MNO to other MNO
● Device should have SIM slot (SIM adapter) and logging capability
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 21
● The eUICC should have already completed Verizon Technical Acceptance and
approval.
● If the device is using a 3rd party M2M (partner) eUICC, then the eUICC must
complete Verizon eUICC Validation, and ensure the following are in place:
○ API available for RSP functionality
○ SMPP Binds – Partner SMSR to both Verizon SMSC and Partner SMSC
○ ES3 Integration – Partner SMSR to Verizon SMDP
A detailed process guide for Device M2M eUICC certification can be found under the
Requirements and Test Plan documentation section of the Open Development portal.
If the device will be utilizing the Consumer eUICC architecture, then the OEM must
comply with the Consumer eUICC requirements in LTE_3GPP_B13_NetworkAccess
requirement section 1.3.1.3.15 eUICC (Consumer eUICC sections only). Additionally,
the OEM will need to provide information regarding the eUICC and LPA (Local Profile
Assistant) being used within the device when submitting for OD certification. There will
be a GSMA Consumer RSP Compliance Matrix to be completed and shared with the OD
certification team to determine if the eUICC will be compatible with the Verizon SIM
profile or if the eUICC has already been validated by Verizon.
If the device will be using a Verizon Technically Approved eUICC, or an eUICC that has
already been validated by Verizon, then the device will undergo the E2E Device
Consumer eUICC testing in the Verizon NDET lab for certification. If the device is using
a 3rd party eUICC (Not Verizon Technically Approved, and not validated by Verizon),
then the eUICC will first need to go through the eUICC Validation process with the
Verizon SIM profile before device testing can take place.
NOTE: If an eUICC has already been previously Validated, then the device can proceed
directly to the E2E Device Consumer eUICC testing.
A detailed process guide for Device Consumer eUICC certification
(GSMA_RSP_Consumer_High_level_Onboarding_Process) can be found in the eUICC
requirements document within the Open Development requirements package under the
Requirements and Test Plan documentation section of the Open Development portal.
Once the device has completed testing and full certification for M2M or Consumer
eUICC, the Device OEM may use any eUICC in their commercial deployment without
additional VZ testing on the device under the following conditions:
1. The eUICC needs to be already validated or Technically Approved by Verizon
2. The Device OEM or CSP should perform some sanity testing before large scale
deployment with the new eUICC
3. Any liability (of M2M or Consumer eUICC features not working) is the
responsibility of the device OEM and they will be the first point of contact for the
customer in the event there is an issue with M2M or Consumer eUICC
functionality on their device.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 22
3.4.5 Inactivity
If the testing status remains inactive for more than 2 months, the certification status will
be changed to FAIL. The Device will be subject to re-evaluation or re-submission for
certification and may require complying to most recent VZW Requirements.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 23
4 Post Certification Device ID Upload Procedure
After the Device is approved and before the Device goes to market, the Device
must be entered into the VZW DMD to allow future activation of a certified Device.
This Process is known as the Device identification upload (ESN/MEID for 3G
Devices or IMEI for 4G Devices).
The DEVELOPER can upload the production Device identifications using one of the
following approaches:
1. EDI
2. ODP
If one of the above two upload methods is not followed, the VZW’ system will
prevent activation of the Devices.
4.1 EDI
Electronic Data Interchange (EDI)
● Refer to the “Electronic Data Interchange (EDI) Document” section on the ODP for
more information
4.2 OD ODP
4.2.1 Single Device ID Upload
● DEVELOPER captures all of the Device identifications (ESNs/MEIDs/IMEIs) in a
CSV file or text 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 or .txt file:
File Name: CompanyXYZ_ProductABC_5.csv
ESN/MEID/IMEI:
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 24
o IMEI/ICCID pair:
o IMEI/EID pair (txt or csv):
● DEVELOPER logs into ODP, clicks on the “Upload ESN/MEID” link/tab next to the
approved Device.
● On the upload screen, select the format of the serial numbers that will be uploaded.
The format must be one of the following:
o IMEI (15) numeric or alpha
o MEID (14) alpha numeric only
o ESN HEX (8) alpha numeric only
o IMEI/ICCID Pair- IMEI(15) numeric or alpha & ICCID (20) alpha only
o IMEI/EID Pair – IMEI(15) numeric or alpha & 32 alphanumeric hexadecimal
● Once the DEVELOPER uploads the CSV or txt file, an email is automatically sent to
the DEVELOPER providing notice that an ESN/MEID/IMEI 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 15 minutes to load into the VZW DMD system and
will be ready for activation then.
● Test Devices to be sold as production Devices shall be re-uploaded by
DEVELOPER as certified Devices via ODP or EDI.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 25
4.2.2 Dual Device ID Upload
4.2.2.1 2 Physical SIMs mapped to a Single Device
SKU
● DEVELOPER captures all of the Device identifications (Serial Number, Device
IMEI1, Device IMEI2) in a CSV file or text file as follows:
o The Serial Numbers will start on the first line of the first column. Device IMEI1
will be stored in the second column, and Device IMEI2 will be stored in the 3
rd
column.
4.2.2.2 2 Electronic SIMS
● DEVELOPER captures all of the Device identifications (Serial Number, Device
IMEI1, EID1, Device IMEI2, EID2) in a CSV file or text file as follows:
o The Serial Numbers will start on the first line of the first column. Device IMEI1
will be stored in the 2
nd
column, EID1 will be stored in the 3
rd
column, Device
IMEI2 will be stored in the 4
th
column, and EID2 will be stored in the 5
th
column.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 26
4.2.2.3 1 Physical SIM and 1 Electronic SIM
● DEVELOPER captures all of the Device identifications in a CSV file or text file.
● The order of the device elements will be dependent on how the device OEM has
selected the SIM types in the ODP.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 27
● If the SIM is selected with eUICC support as No, only the device IMEI1 or device
IMEI/ICCID pair will required. If the SIM is selected with eUICC support as Yes, the
Device IMEI and associated EDI will need to be provided.
● The following table shows the possible combinations of SIM types and required
information.
SIM Selection in ODP
Required Identifiers in uploaded CSV or text file
Physical SIM, Electronic SIM
Device Serial Number, IMEI1, EMEI2, EID2
Physical SIM/UCCID pair, Electronic SIM
Device Serial Number, IMEI1, UCCID1, IMEI2, EID2
Electronic SIM, Physical SIM
Device Serial Number, IMEI1, EID1, IMEI2
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 28
5 OD Certification Agreement Violation Process
Flow
Upon knowledge of any Rogue Devices (unapproved Device or approved Device
harming the network), Applications or Violations to the CA with VZW the following
will take place:
● ODPT notifies DEVELOPER of Device compliance issue (rogue Devices or
applications detected, CA violations)
● Developer will ship 2 sample Devices within 48 hours upon receiving the formal
request from Verizon for network evaluation.
● VZW retains the right to restrict or deactivate the OD Device if VZW has determined
the Device to be harmful to the Network and its end users and de-certify it if
necessary.
If a Device fails to comply with the OD Specification, Verizon may de-certify the Device
or take any necessary steps to protect the Network and its end-users, including, but not
limited to, (a) no provisioning of additional units of the Device on the Network, (b)
removal of the Device from the OD website that lists current certified devices, (c)
notification to Device end-users of Network issues related to the failure to comply with
the OD Specification that impact the Device end-users’ service on the Network.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 29
6 Device Evolution, Maintenance & Regression
Testing Process Flow
6.1 Device Evolution:
At any time, in case of any updates to the certified software or hardware,
DEVELOPER must notify ODPT and provide all submission documentation to the
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 Release Testing Flow
6.2 Device Maintenance & Regression Testing Process
● DEVELOPER submits updated submission documents to the ODPT/NDET Lab
for evaluation, and coordinates with the OD Authorized ITL to execute regression
testing (in coordination with VZW NDET Lab).
● After the regression test criteria are completed for the Device, the OD authorized
ITL forwards the results to the VZW (ODPT & NDET Lab) to verify that the
Device is compliant.
● After the Device successfully passes testing, the ODPT will certify the Device
Maintenance Release and issue official notification.
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 30
7 Test Lab Contact information
Element Materials Technology Dallas Inc. (Aircom Labs)
Capabilities
APPROVED TESTING LOCATION 1 - MAIN
Business Contact:
Gwyn Bernot Email: Gwyn.Bernot@element.com
5G, 4G Lab
Conformance - See
Test Plan tabs for
detailed information
on Lab Coverage
PRE-DFIT
Phone:
859-582-8731
Email:
vzw@element.com
Technical Contact:
Maqusood Anwar Email:
Maqusood.Anw[email protected]
Phone:
Email:
vzw@element.com
Business Address:
2304 Tarpley Rd Ste 100, Carrollton, TX 75006
APPROVED TESTING LOCATION 2
Business Address: 411 Dixon Landing Road, Milpitas, CA 95035
5G, 4G Lab
Conformance - See
Test Plan tabs for
detailed information
on Lab Coverage
PRE-DFIT
Bureau Veritas (7Layers)
Capabilities
APPROVED TESTING LOCATION 1 - MAIN
Business Contact:
Bureau Verita Sales
5G FR1/FR2: RF, RRM,
Protocol, Pre-
Conformance,OTA;
LTE, Multi-Mode,
VoLTE, CA, eMBMS,
VoWiFi, OTA, NBIoT
Phone:
669-600-5293
Email:
sales.eaw@bureauveritas.com
Technical Contact:
Shubha Gopalakrishna
Phone:
949-297-8057
Email:
Shubha.Gopa[email protected]eauveritas.com
Business Address:
1293 Anvilwood Ave, Sunnyvale, CA 94089
APPROVED TESTING LOCATION 2
Business Address: 1293 Anvilwood Ave, Sunnyvale, CA 94089 OTA
Cetecom
Capabilities
Business Contact:
Amber Neves
OTA, Audio testing
Phone:
408-601-8948
Email:
Technical Contact:
Nicolas Stamber
Phone:
408-586-6234
Email:
nicolas.stamber@cetecom.com
Business Address:
411 Dixon Landing Road, Milpitas CA 95035
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 31
Ericsson
Capabilities
Business Contact:
Omkar Dalal
Interoperability (IOT)
Phone:
972-741-6696
Email:
omkar.dalal@ericsson.com
Technical Contact:
Omkar Dalal
Phone:
972-741-6696
Email:
omkar.dalal@ericsson.com
Business Address:
6300 Legacy Dr, Plano, TX 75024
Intertek
Capabilities
Business Contact:
Robbie Payne
LTE, CDMA, Multi-
Mode, VoLTE, CA, OTA,
VoWiFi, FIT
Phone:
859-388-4951
Email:
robbie.payne@intertek.com
Technical Contact:
Ron Bernot
Phone:
859-226-1000
Email:
ron.bernot@intertek.com
Business Address:
731 Enterprise Drive, Lexington, KY 40510
Nokia Lab
Capabilities
Business Contact:
Use Alias Email below
Interoperability (IOT)
Motive-bridge (FOTA)
Phone:
Email:
For new LWM2M OEMs - vzw-lwm2m-
onboard@nokia.com
For new OMADM OEMs - vzw-omadm-
onboard@nokia.com
Technical Contact:
Same as Above
Phone:
Email:
Business Address:
600-700 Mountain Ave, Room 6H-424, Murray
Hill, NJ 07974
Element Materials Technology Washington DC LLC
(PCTEST Engineering Lab)
Capabilities
APPROVED TESTING LOCATION 1 - MAIN
Business Contact:
Luis Magana Email: luis.magana@element.com
5G, 4G Lab
Conformance - See
Test Plan tabs for
detailed information
on Lab Coverage
PRE-DFIT
Phone:
410-290-6652
Email:
steve.coston@pctest.com
Technical Contact:
Andrea Zaworski Email:
andrea.zawor[email protected]
Phone:
410-290-6652
Email:
andrea.zawor[email protected]
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 32
Business Address:
7185 Oakland Mills Road, Columbia, MD 20146
APPROVED TESTING LOCATION 2
Business Address: 6660-B Dobbin Road, Columbia, MD 21045 USA
5G, 4G Lab
Conformance - See
Test Plan tabs for
detailed information
on Lab Coverage
PRE-DFIT
APPROVED TESTING LOCATION 3
Business Address: 382 Piercy Road, San Jose, CA 95138
5G, 4G Lab
Conformance - See
Test Plan tabs for
detailed information
on Lab Coverage
PRE-DFIT
RC Logixx
Capabilities
Business Contact:
Ron Cunanan
DFIT (for Field Test)
Phone:
972-922-6289
Email:
Technical Contact:
Ron Cunanan
Phone:
972-922-6289
Email:
Business Address:
2727 LBJ Freeway Suite 222, Dallas, TX 75234
SGS
Capabilities
APPROVED TESTING LOCATION 1 - MAIN
Business Contact:
Ben Kuo
LTE, CDMA, Multi-
Mode, VoLTE, eMBMS,
VoWiFi, OTA,5G FR2
RF, 5G FR2 Protocol
Phone:
858-304-9141
Email:
Technical Contact:
Gerardo Berrelleza
Phone:
858-592-7100
Email:
Business Address:
15150 Avenue of Science, Suite 300, San Diego, CA
92128
APPROVED TESTING LOCATION 2
Business Address:
12310 World Trade Dr, Suite 106/107
San Diego, CA, 92128
OTA, Audio
APPROVED TESTING LOCATION 3
Business Address:
14 Culnen Dr, Lower Level
Branchburg, NJ 08876
4G & 5G OTA
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 33
Tech Mahindra
Capabilities
APPROVED TESTING LOCATION 1 - MAIN
Business Contact:
Arunav Roy
LTE, CDMA, Multi-
Mode, VoLTE,eMBMS
Phone:
469-600-7846
Email:
arunav.roy@techmahindra.com
Technical Contact:
Hiteshkumar Gamdha
Phone:
908-239-5232
Email:
Business Address:
Tech Mahindra Americas: 500 Hills Dr, STE 203,
Bedminster, NJ 07921
APPROVED TESTING LOCATION 2
Business Address: 6092 Stewart Ave, Fremont, CA 94538
5G FR2 VZW
Supplemental RF. 5G
FR2 Protocol
UMLAUT
Capabilities
Business Contact:
Ron Housenick
DFIT (for Field Test)
Phone:
Office: 973-984-6050 Cell: 973-867-8395
Email:
Ron.housenic[email protected]
Technical Contact:
Sascha Cigoj
Phone:
+49 241 9437 399
Email:
Sascha.Cigoj@umlaut.com
Business Address:
412 Mount Kemble Ave, Morristown, NJ 07960
Wireless Research Center
Capabilities
Business Contact:
Jordan Stearns
LTE/CDMA OTA
Phone:
919-435-1051 ext.102
Email:
jordan.stearns@wirelesscenter-nc.org
Technical Contact:
Jordan Stearns
Phone: 919-435-1051 ext.x102
Email:
jordan.stearns@wirelesscenter-nc.org
Business Address:
3331 Heritage Trade Dr. Suite 101, Wake Forest,
NC 27587
IoT Security Penetration Testing Labs
Carve Systems
Capabilities
Business Contact: Max Sobell
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 34
Phone: 650-454-0072
Penetration Testing for
IoT Security
Email:
max.sobell@carvesystems.com
Technical Contact: Max Sobell
Phone: 650-454-0072
Email:
max.sobell@carvesystems.com
Business Address:
38 E Ridgewood Ave, #110 Ridgewood, NJ 07450
Spirent
Capabilities
Business Contact: Satya Patel
Penetration Testing for
IoT Security
Phone: 732-895-9486
Email: satya.patel@spirent.com
Technical Contact: Satya Patel
Phone: 732-895-9486
Email: satya.patel@spirent.com
Business Address:
101 Crawfords Corner Road, Suite 4-216 Holmdel,
NJ 07733
Atredis Partners
Capabilities
Business Contact: Josh Thomas
Penetration Testing for
IoT Security
Phone: 512-965-0287
Email:
Technical Contact:
Josh Thomas
Phone:
512-965-0287
Email:
Business Address:
3118 Allen Ave, Suite 300
ST. Louis, MO 63104-1531
Palindrome
Capabilities
Business Contact: Peter Thermos
Penetration Testing for
IoT Security
Phone: 732- 688-0413
Email:
Technical Contact:
Peter Thermos
Phone:
732- 688-0413
O
PEN DEVELOPMENT DEVICE CERTIFICATION PROCESS
VERIZON CONFIDENTIAL Version 37 © Verizon Wireless 2022 -- All Rights Reserved Page 35
Email:
peter.thermos@palindrometech.com
Business Address:
100 Village Ct., Suite 300
Hazlet, NJ 07730, USA
