Open Development Device Certification Process - Verizon Wireless

Transcription

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESSOpen Development DeviceCertification ProcessThis document provides initial information related to the Verizon Wireless Open Development. Allinformation herein is subject to change without notice. The information provided was consideredtechnically accurate at the time the documents were developed, but Verizon Wireless disclaimsand makes no guaranty or warranty, express or implied, as to the accuracy or completeness ofany information contained or referenced herein. VERIZON WIRELESS DISCLAIMS ANYIMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULARPURPOSE.The developer of any Device, service or product for use on the Verizon Wireless networkassumes all risks related to the development of such Device, service or product. VerizonWireless does not guarantee or warrant the availability of its network or the compatibility of itsnetwork with any Device, service or product. Verizon Wireless disclaims liability for any damagesor losses of any nature whatsoever whether direct, indirect, special or consequential resultingfrom the use of or reliance on any information contained or referenced herein.VERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights ReservedPage 1

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESSDocument #: SP-OA-ST-08-0003Contents1Objective72Glossary and Definition of Terms83Device Compliance Process3.110Entrance Criteria and Certification Process103.1.1Device Entrance Criteria103.1.2Overall Certification Process Flow:103.2Certification Process113.3Required Agreements/Documents123.4OD Compliance Testing123.4.1Early Testing Process Flow123.4.2OD Standard Lab Testing Process Flow143.4.3Auto-Certification Platform Testing Process Flow143.4.4 Additional Testing for Verizon Services (If features are supported bythe device)153.4.4.1LBS/aGPS/SUPL Application Testing Process Flow153.4.4.2MMS Device Testing Process Flow153.4.4.3Private Network Testing153.4.4.4Device Management Services153.4.4.5Verizon Diagnostics153.4.4.6Verizon Base-band FOTA153.4.4.7Verizon Application FOTA163.4.545Inactivity16Post Certification Device ID Upload Procedure174.1EDI174.2OD ODP174.2.1Single Device ID Upload174.2.2Dual Device ID Upload184.2.2.12 Physical SIMs mapped to a Single Device SKU194.2.2.22 Electronic SIMS194.2.2.31 Physical SIM and 1 Electronic SIM20OD Certification Agreement Violation Process FlowVERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved22Page 2

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS67Device Evolution, Maintenance & Regression Testing Process Flow236.1Device Evolution:236.2Device Maintenance & Regression Testing Process23Test Lab Contact informationVERIZON CONFIDENTIAL Version 3424 Verizon Wireless 2021 -- All Rights ReservedPage 3

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESSRevision HistoryRevRevision History1.0Initial ODIS Testing Document2.0Modifications to add process details, LBS/aGPSand ENAP3.0Modificationss after technical review4.0Modifications after legal review5.0Adding requirements lock down process6.0Adding language to address export control concernsSection 3.87.0Modifications to Device Introduction Process FlowSection8.0Add MMS, Global and Telematics Device support9.0RA process modifications and Vendor meetingagenda details10.0 Process updates11.0 Add unit requirements, 3rd party contact namechange, edits from review12.0 Add ODPT mailbox to Pre-submission process flowand to Device introduction process flow;Modifications to Unit requirements13.0 Replace Developer Agreement with CertificationAgreement. Updated contact list.13.1 Added VzW owns the test reports (Section 3.2.4)13.2 Modifications to Device Introduction Process FlowSection (Section 3.4)13.3 Removed Authors names13.4 Added forecast worksheet to DLD13.5 Legal review additions13.7 Update DLD Agenda13.9 Updated per legal feedback14.0 General updates15.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 moduleto 20.16.0 Updated SGS Contact Info to Johee from Dawn.Section 3.2.1 – Added Master Showcase to requireddocs and DLD agenda, added some clarity on howto register a new DeviceVERIZON CONFIDENTIAL Version 34DateMarch 2008June 2009June 2009June 2009August 2009August 2009September 2009November 2009January 2010February 2010March 2010April 2010May 2010May 2010May 2010May 2010May 2010May 2010June 2010June 2010 Verizon Wireless 2021 -- All Rights ReservedPage 4

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESSSection 3.5 – Mentioned new instructions on ODPortal uploads exist on the 82930Section 3.3.3 - updated the flow and requirement forMMSC Server Test.Replaced CPE with NDETSection 3.5 – updated the Device IntroductionprocessSection 3.5 – Updated the Device CSV processSection 3.5 – Updated the wait window with cut offtimeSection 3.6 – Added sample Device requirementsSection 3.7 – Updated the Certification ExpirationSection 3.3.1 – Concession AccountsAll sections – Changed LBS to LBS/aGPSSection 3.5 Updated IMEI/ICCID pair instructionsSection 3.2 – Updated DLD agendaSection 3.3 – Updated testing processSection 3.4 – Updated time window for ESN uploadSection 3.8 (former Section 3.9) – Added new ITLSection 3.1 – Updated export control linkSection 3.2 – Added LTE M2M SIM to DLD agendaSection 3.4 – Removed recommendation for EDISection 3.8 – Updated test lab informationSection 3.1 – Added Software Update support for4G devicesSection 3.1 – OTA ID infoSection 3.3.2 – Clarification on test resultsSection 3.2 – Simplified DLD call agendaSection 3.8 – SGS address change and addedWireles Research CenterRemoved reference section, updated lab contactUpdated acronymsAdded overall flowAdded new Required Agreement sectionAdded additional testing sub-sectionsUpdated linksUpdated Lab contactsClarified other sections throughout the docRemoved ECCN linkUpdated Required Agreements sectionClarified FOTA updatesUpdated EDI upload section, added EIDUpdated Lab contactsVERIZON CONFIDENTIAL Version 34January 2013December 2013July 2014November 2014August 2015October 2016May 2017March 2018 Verizon Wireless 2021 -- All Rights ReservedPage 5

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS31Section 7. Updated Technical contact for TechMahindraSection 7. Updated Test lab name from P3 toUmlautSection 7. Updated Contact for NokiaFeb 202032Section 3.4.1 Updated conditions for Early NetworkAccess Program devices and Safe For NetworkdevicesSection 7. Updated 7Layers into Bureau VeritasSection 7. Added Aircom LabsSection 7. Merged Nokia IOT lab and Motive labSection 7. Updated information for ApprovedVerizon 3rd party labsJuly 202033Section 7. Added Carve Systems,Spirent, AltredisPartners, and Palindrome as approved 3rd party testlabs.Section 3.4.1 Updated conditions for ENAP devicesSection 4.2.2 Added Dual Device ID Uploadinstructions.Updated Section 3.1 to include statement onVerizon FOTA support and IoT device securitycompliance and testing.Section 3.4.1 Updated conditions for ENAP devicesusing approved embedded modemAdded section 3.4.3 Auto-Certification PlatformTesting Process FlowUpdated Section 3.4.4 for Verizon Services (VerizonDiagnostics, Verizon Baseband FOTA, VerizonApplication FOTA)Updated Bureau Veritas lab informationOctober 202034VERIZON CONFIDENTIAL Version 34January 2021 Verizon Wireless 2021 -- All Rights ReservedPage 6

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS1 ObjectiveThe purpose of this document is to define and describe the Open Development DeviceCertification process, Device testing and conformance requirements* that Devices mustmeet 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 (loginrequired).VERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights ReservedPage 7

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS2 Glossary and Definition of TermsaGPSAssisted GPSAMAccount ManagerB2BBusiness to BusinessBISBureau of Industry and SecurityCDMACode Division Multiple AccessCCATSCommodity Classification Automated Tracking SystemCDGCDMA Development GroupCACertification agreementCEConformité Européenne, "European conformity"COICertificate of InsuranceCSVComma-Separated ValuesDLDDevice Lock DownDMDDevice Management DatabaseDTODevice Test OwnerEDIElectronic Data InterchangeEIDeUICC ID (Embedded Universal Integrated Circuit Card) IDENAPEarly Network Access ProgramESNElectronic Serial NumberECCNExport Control Classification NumberICCIDIntegrated Circuit Card IdentifierIMEIInternational Mobile Equipment IdentifierFITField Interoperability TestingFOTAFirmware Over The AirGCFGlobal Certification ForumIOTInteroperability TestingIoTInternet of ThingsITLIndependent Test LaboratoryLBSLocation Based ServicesM2MMachine to MachineMEIDMobile Equipment IdentifierMDNMobile Directory NumberMMSMulti Media Messaging servicesVERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights ReservedPage 8

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESSMMSCMultimedia Messaging Service CenterNDET LabNetwork Device Evaluation Test LaboratoryNDRANational Direct Revenue AssuranceNRBNetwork Repair BureauNSRANational SurePay Revenue AssuranceNWRANational Wholesale Revenue AssuranceOEMOriginal Equipment ManufacturerODOpen DevelopmentODPOpen Development PortalODPTOpen Development Product Team (Including Business Development,Certification Owners and Account management.)ODSOpen Development SpecificationOTAOver The AirPDIProduct Development and IntegrationPMProduct ManagerRARevenue AssuranceRFRadio FrequencyRNRelease NotesSFNSafe For NetworkSUPLSecure User Plane LocationTECCTest Entrance Criteria Checklist (Test Campaign)VSPVertical Solutions ProviderWSWholesaleVZWVerizon WirelessVERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights ReservedPage 9

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS3 Device Compliance Process3.1 Entrance Criteria and Certification ProcessAll Devices must be type approved and certified by the United States FederalCommunications Commission (FCC) and classified by the Department of Commerce'sBureau of Industry and Security (BIS) before Open Development (OD) Conformancetesting can commence.OEMs or OD Device Developers (collectively, “DEVELOPER,”) requesting VerizonWireless’ (VZW) certification for LTE capable Devices must receive GCF certificationbefore 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 FOTAcapabilities must be tested to ensure that the Verizon FOTA capability of themodule is still functional.All chipsets and modules brought for approval or devices that are brought toVerizon for certification must provide appropriate security compliancedocumentation and/or security compliance test results. The security requirementswill be determined during the DLD stage of device submission.In order for DEVELOPER to access the OD web portal or OD documents, DEVELOPERmust execute a Non-Disclosure Agreement (NDA).Each DEVELOPER will receive a unique VZW-ID after completing NDA. The VZW-IDwill be used in conjunction with the submitted Device to form the Device tracking ID.VZW and OD authorized Independent Test Laboratory (ITL) will identify individualDevices prior to Certification using only this Device tracking ID.3.1.1 Device Entrance CriteriaThe OD Device Tracking ID VZW-ID will be assigned for each DEVELOPER submitting a Device forConformance Example VZW01000001 FCC-ID Required Prior to Open Development Conformanceo FCC Grantee ID (First 3 Characters)o FCC Product Code (Remaining up to 14 Characters)o block-4o Example “A1C0123456789012” BIS ECCN and CCATS Required Prior to Open Development Conformanceo Example " 5A992, G0823456"3.1.2 Overall Certification Process Flow:Obtaining Device certification and launching a Certified Device on the VZW networkinvolves fulfilling technical and the contractual requirements of the CA. The CA is aVERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 10

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESScontract issued by Verizon and jointly signed by the DEVELOPER; review can occur inparallel to device registration and testing.DeveloperRegistrationandexecutingNDA Add newDevice(s)DLDTestingDeviceLaunchCertification Agreement (CA)and Certificate of InsuranceDeveloper Registration and Executing NDA – This allows full access to ODP anddetailed documents, such as requirements, test plans, etc.Add new Device(s) – This involves a five step process on the ODPo New Device Infoo Marketing Infoo Forecasto Release Noteso Attaching all Pre-submission DocumentsDLD - Review and lockdown documentsTesting - Send device(s) to authorized lab for testingFOTA – DEVELOPER to provide FOTA update documentation on a test device.Completing Contractual Agreements – Fulfilling CA and COI documents arerequired prior to device certification.Device ID Upload and Launch – Loading Device IDs into Verizon DeviceManagement Database (DMD) system.3.2 Certification Process After the DEVELOPER executes a NDA, accounts will be created to access the ODPat https://opendevelopment.verizonwireless.com/ DEVELOPER downloads and reviews the OD certification documentation.DEVELOPER adds information regarding the new Device and submits all requiredinformation on the ODP and notifies their supporting VZW representative. Theregistered device name/model number should reflect the marketing name/modelnumber as it appears in any FCC filing or approval.A DLD review will be held between DEVELOPER and VZW team. The review willcover the following:o Submission Overviewo Device Certification Agreementso Documentation Reviewo Review Test Campaigno Review Testing & Scheduleo Review of Developer’s Sample Devices - Besides ITL, DEVELOPER isrequired to send 2 samples to VZW ODPT.o Complete required compliance testing in Verizon authorized ITLPending the successful completion of the DLD requirements, VZW will upload theTest Campaign (TECC) to the ODP and notify the DEVELOPER and selected ITLwith Approve To Start test (ATS).VERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 11

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS A host device is certified using an approved module or chipset. A module or chipsetis approved through the ODP. For module and chipset approval, refer to ModuleGuidelines from Requirement & Test Plan Documentation section of the ODP.3.3 Required Agreements/DocumentsAll 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 useof Verizon mark with a written request per Verizon Branded Guidelines. COI – Issued by the DEVELOPER and must be provided to Verizon as proof ofvalid insurance.(NOTE: As of January 2018, Verizon Wireless and companies with a currentCertification Agreement executed prior to then shall no longer execute anaddenda for each newly certified device. Certification of devices will bememorialized in the OD Notice of Certification that contains any device specificrequirements and will include the Certification Period for the device).3.4 OD Compliance TestingThe following figure shows a high level view of the OD required testing process knownas OD Compliance Testing:ReviewDevice infoDeviceLock DownApprovedto TestInTestingPostResultsResultsApprovalAny Device (including a test Device) must have a FCC ID before activation on theVerizon Network.3.4.1 Early Testing Process FlowDEVELOPER 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 networktesting during development.Early Network Access Program (ENAP) If the DEVELOPER is using a VZW certified module, up to 20 activations can beallowed for developmental purposes. Without a VZW certified module, up to 2activations can be allowed for developmental purposes. Upon uploading of testDevice 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 subscribeand activate lines to connect the test Device(s) with VZW network. The test MDNsmust be disconnected no later than 60 day after testing is completed. In order toobtain approval for more than 20 test device IMEI activations, the OEM must haveVERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 12

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS agreed to the terms of the Certification Agreement, and provided the CertificationManager for the device with a detailed business justification detailing: the need foradditional test devices; a list of persons/entities who will be using the additionaldevices; where the additional devices will be used; for what length of time theadditional devices be needed; and the current target date for completing devicecertification. The Verizon Open Development certification team will consider therequests for the additional test devices over the 20 device limit and will approve ordeny the request, based on the business justification, at its discretion. If the businesscase is approved, the device OEM will be allowed to update the additional testdevice IMEIs for approval by their assigned device certification manager.If the DEVELOPER is using a VZW approved embedded modem, up to 20activations can be allowed for developmental purposes. Upon the uploading oftest Device IMEIs to the ODP, VZW will load the test Device(s) MEID/ESN/IMEI inDMD. The DEVELOPER should then work with their VZW sales representative tosubscribe and activate lines to connect the test Device(s) with VZW network. Thetest MDNs must be disconnected no later than 60 day after testing is completed. Inorder to obtain approval for more than 20 test device IMEI activations, the OEM musthave agreed to the terms of the Certification Agreement, and provided theCertification 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 theadditional devices; where the additional devices will be used; for what length of timethe additional devices be needed; and the current target date for completing devicecertification. The Verizon Open Development certification team will consider therequests for the additional test devices over the 20 device limit and will approve ordeny the request, based on the business justification, at its discretion. If the businesscase is approved, the device OEM will be allowed to update the additional testdevice IMEIs for approval by their assigned device certification manager.DEVELOPER shall not activate or use test devices on the Verizon Wireless networkother than for internal testing purposes prior to device certification while such devicesare in ENAP testing. ENAP test devices are to be used by the DEVELOPER fordevelopment and testing of devices in preparation for certification test activities only.Such test devices should not be activated and used on the Verizon Wireless networkin connection with end customer activities.Safe For Network (SFN) Testing If the DEVELOPER completes SFN testing successfully, up to 500 activationsper project can be allowed for further development purposes. DEVELOPERSmust submit the Device information for the ODPT’s review and the SFN testing mustbe conducted at a VZW Authorized ITL.DEVELOPERS submit Device information on the ODP and send a test Devicerequest with supportive reasons and test ESNs/MEIDs/IMEIs.ooRN, TECC, and Device Solution One Pager are required for SFN.ODPT and NDET team review and approve the request.Upon successful completion of SFN, DEVELOPER can request up to 500 activations oftest Devices. All the SFN activated devices must be kept under the device OEM’sown mobile account or ECPD (Enterprise Customer Profile Database) ID accountand remain in the possession and control of the device OEM. The device OEM mustVERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 13

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS also update the device SW to the final certification version once full certification iscomplete.If the DEVELOPER plans to sell the test devices as commercial products after approval, theDEVELOPER must manage these test devices as commercial products and upload themagain (e.g., Note: Test Devices to be sold as production Devices shall be re-uploaded by DEVELOPER as certified Devices via ODP or EDI).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 IOTtesting prior to or in parallel with lab conformance testing.DEVELOPER chooses and contacts a Verizon authorized ITL from the VZWapproved 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/Motivesolution). This can be submitted while the device is in testing, but required with finalresults.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 eitherpasses, conditionally passes or fails the device.After the Device successfully passes testing, ODPT will certify the Device and issuean official notification.3.4.3 Auto-Certification Platform Testing Process FlowThe Auto-Certification Platform (ACP) is a simple, cost-effective platform thatenables OEM self-testing for supported GCF and Verizon test plans for devices, chipsetsand modules.Before the ACP can be shipped to an OEM the following conditions must be met: Confirm device readiness by completing Device lockdown (DLD) withCertification managerCertificate of Insurance (COI) completedReview the ACP Prerequisites document (including Host PC requirements)shared by Certification manager during DLD and confirming that OEM is able tomeet themSubmit account registration at https://vzwdt.com/acpportal/The ACP can only be shipped to business addresses in the United States, and only topersons directly employed by the OEM. The ACP cannot be sent internationally by thereceiving company to locations outside the United States without prior approval ofVerizon. Export Regulations mandate that it can only be shipped by OEM to approvedVERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 14

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESScountries. Please check with your certification manager on international shippingdestinations.For any issues with ACP setup and testing, there is a ticketing system setup to contactACP support and details are provided in the Prerequisites document.3.4.4 Additional Testing for Verizon Services (If features aresupported by the device)OD Standard Lab testing completion is a prerequisite to additional testing. Details foradditional testing are available in the Requirement and Test Plan Documentation sectionof the ODP.3.4.4.1LBS/aGPS/SUPL Application Testing Process FlowAfter OD Standard Lab Test completion, DEVELOPER may start the LBS/aGPS/SUPLprocess. Refer to “LBS/aGPS Certification Submission Package” for moreinformation.3.4.4.2MMS Device Testing Process FlowThe MMS process must be completed before Device certification for Devices thatare 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.3Private Network TestingApplicable to Devices using the Verizon Private Network. Refer to PrivateNetwork section on ODP.3.4.4.4Device Management ServicesRefer to Verizon OMADM 1.2 Reference Client Package or Verizon light weightM2M (LWM2M) OTADM Reference Client Package on ODP.3.4.4.5Verizon DiagnosticsAll modules and chip-on-board devices OEMs have to run LWM2M Diagnosticstesting. Refer to Reqs-LWM2M document and the ACP support team to utilizeACP box for Verizon LWM2M Diagnostics testing.3.4.4.6Verizon Base-band FOTAVerizon Firmware Over The Air (FOTA) is a Mobile Software Management(MSM) technology in which the module’s (or chipset’s) base-band firmware canbe wirelessly upgraded by Verizon. Verizon base-band FOTA uses OMADM orOMA LWM2M industry standards. More information can be found in the “ODFOTA Compliance Instructions and Testing Guidelines'' document under ‘DeviceManagement Services’ on the OD Partner Portal.VERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 15

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS3.4.4.7Verizon Application FOTAVerizon Firmware Over The Air (FOTA) is a Mobile Software Management(MSM) technology in which the application (AP) firmware of a host device can bewirelessly upgraded by Verizon. Verizon Firmware Over The Air (FOTA) usesOMADM or OMA LWM2M industry standards.3.4.5 InactivityIf the testing status remains inactive for more than 2 months, the certificationstatus will be changed to FAIL. The Device will be subject to re-evaluation or resubmission for certification and may require complying to most recent VZWRequirements.VERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 16

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS4 Post Certification Device ID Upload ProcedureAfter the Device is approved and before the Device goes to market, the Devicemust 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 3GDevices or IMEI for 4G Devices).The DEVELOPER can upload the production Device identifications using one of thefollowing approaches:1. EDI2. ODPIf one of the above two upload methods is not followed, the VZW’ system willprevent activation of the Devices.4.1 EDIElectronic Data Interchange (EDI) Refer to the “Electronic Data Interchange (EDI) Document” section on the ODP formore information4.2 OD ODP4.2.1 Single Device ID Upload DEVELOPER captures all of the Device identifications (ESNs/MEIDs/IMEIs) in aCSV file or text file as followed:o The ESNs/MEIDs/IMEIs will start on the first line of the first column. ForDevices with IMEI & ICCID pairings the IMEIs will be placed in column A andICCIDs will be placed in column Bo 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 totalnumber count of ESNs/MEIDs/IMEIs or IMEI/ICCIDs loaded).o Example of the CSV or .txt file:File Name: CompanyXYZ ProductABC 5.csvESN/MEID/IMEI:VERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 17

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESSoo DEVELOPER logs into ODP, clicks on the “Upload ESN/MEID” link/tab next to theapproved Device.On the upload screen, select the format of the serial numbers that will be uploaded.The format must be one of the following:ooooo IMEI/ICCID pair:IMEI/EID pair (txt or csv):IMEI (15) numeric or alphaMEID (14) alpha numeric onlyESN HEX (8) alpha numeric onlyIMEI/ICCID Pair- IMEI(15) numeric or alpha & ICCID (20) alpha onlyIMEI/EID Pair – IMEI(15) numeric or alpha & 32 alphanumeric hexadecimalOnce the DEVELOPER uploads the CSV or txt file, an email is automatically sent tothe DEVELOPER providing notice that an ESN/MEID/IMEI file has been uploadedand automatically approved.The Device identification (ESNs/MEIDs/IMEIs or IMEI/ICCID pairs) provided in theCSV approved file will take up to 15 minutes to load into the VZW DMD system andwill be ready for activation then.Test Devices to be sold as production Devices shall be re-uploaded byDEVELOPER as certified Devices via ODP or EDI.4.2.2 Dual Device ID UploadVERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 18

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS4.2.2.12 Physical SIMs mapped to a Single DeviceSKU DEVELOPER captures all of the Device identifications (Serial Number, DeviceIMEI1, 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 IMEI1will be stored in the second column, and Device IMEI2 will be stored in the 3rdcolumn.4.2.2.2 2 Electronic SIMSDEVELOPER captures all of the Device identifications (Serial Number, DeviceIMEI1, 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 IMEI1will be stored in the 2nd column, EID1 will be stored in the 3rd column, DeviceIMEI2 will be stored in the 4th column, and EID2 will be stored in the 5thcolumn.VERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 19

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS4.2.2.3 1 Physical SIM and 1 Electronic SIMDEVELOPER 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 hasselected the SIM types in the ODP.VERIZON CONFIDENTIAL Version 34 Verizon Wireless 2021 -- All Rights Reserved Page 20

OPEN DEVELOPMENT DEVICE CERTIFICATION PROCESS If the SIM is selected with eUICC support as No, only the device IMEI1 or

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)