How To Write A Rev.Histry Rev.Heistry

Transcription

1 Open Develpment Device Certificatin Prcess This dcument prvides initial infrmatin related t the Verizn Wireless Open Develpment. All infrmatin herein is subject t change withut ntice. The infrmatin prvided was cnsidered technically accurate at the time the dcuments were develped, but Verizn Wireless disclaims and makes n guaranty r warranty, express r implied, as t the accuracy r cmpleteness f any infrmatin cntained r referenced herein. VERIZON WIRELESS DISCLAIMS ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE. The develper f any Device, service r prduct fr use n the Verizn Wireless netwrk assumes all risks related t the develpment f such Device, service r prduct. Verizn Wireless des nt guarantee r warrant the availability f its netwrk r the cmpatibility f its netwrk with any Device, service r prduct. Verizn Wireless disclaims liability fr any damages r lsses f any nature whatsever whether direct, indirect, special r cnsequential resulting frm the use f r reliance n any infrmatin cntained r referenced herein. Versin 26 Verizn Wireless All Rights Reserved Page 1

2 Dcument #: SP-OA-ST Cntents REVISION HISTORY OBJECTIVE GLOSSARY AND DEFINITION OF TERMS DEVICE COMPLIANCE PROCESS Entrance Criteria Pre-Submissin Prcess Flw OD Cmpliance Testing Early Testing Prcess Flw OD Standard Lab Testing Prcess Flw Additinal Testing Device Intrductin Prcess Flw ODS Agreement Vilatin Prcess Flw Device Evlutin r Certificatin Expiratin Prcess Flw Device Maintenance & Regressin Testing Prcess Flw Test Lab Cntact infrmatin REFERENCES Versin 26 Verizn Wireless All Rights Reserved Page 2

3 Revisin Histry Rev. Revisin Histry Date 1.0 Initial ODIS Testing Dcument March Mdificatins t add prcess details, June 2009 LBS/aGPS and ENAP 3.0 Mdificatinss after technical review 4.0 Mdificatins after legal review June Adding requirements lck dwn prcess June Adding language t address exprt cntrl August 2009 cncerns Sectin Mdificatins t Device Intrductin August 2009 Prcess Flw Sectin 8.0 Add MMS, Glbal and Telematics Device September 2009 supprt 9.0 RA prcess mdificatins and Vendr Nvember 2009 meeting agenda details 10.0 Prcess updates January Add unit requirements, 3 rd party cntact February 2010 name change, edits frm review 12.0 Add ODPT mailbx t Pre-submissin March 2010 prcess flw and t Device intrductin prcess flw; Mdificatins t Unit requirements 13.0 Replace Develper Agreement with April 2010 Certificatin Agreement. Updated cntact list Added VzW wns the test reprts (Sectin May ) 13.2 Mdificatins t Device Intrductin May 2010 Prcess Flw Sectin (Sectin 3.4) 13.3 Remved Authrs names May Added frecast wrksheet t DLD May Legal review additins May Update DLD Agenda May Updated per legal feedback June General updates June Remved sectin Added VPS Vertical Slutins Prvider. Added ppt 1 pager t pre-submissin frms. Added sample Device t DLD agenda and reqs. Changed pht in 3.3. Changed available activatins w/ apprved Versin 26 Verizn Wireless All Rights Reserved Page 3

4 mdule t Updated SGS Cntact Inf t Jhee frm Dawn. Sectin Added Master Shwcase t required dcs and DLD agenda, added sme clarity n hw t register a new Device Sectin 3.5 Mentined new instructins n OD Prtal uplads exist n the site Sectin updated the flw and requirement fr MMSC Server Test. Replaced CPE with NDET 18.0 Sectin 3.5 updated the Device Intrductin prcess 19.0 Sectin 3.5 Updated the Device CSV prcess 20.0 Sectin 3.5 Updated the wait windw with cut ff time Sectin 3.6 Added sample Device requirements 21.0 Sectin 3.7 Updated the Certificatin Expiratin 22.0 Sectin Cncessin Accunts All sectins Changed LBS t LBS/aGPS 23.0 Sectin 3.5 Updated IMEI/ICCID pair instructins 24.0 Sectin 3.2 Updated DLD agenda Sectin 3.3 Updated testing prcess Sectin 3.4 Updated time windw fr ESN uplad Sectin 3.8 (frmer Sectin 3.9) Added new ITL 25.0 Sectin 3.1 Updated exprt cntrl link Sectin 3.2 Added LTE M2M SIM t DLD agenda Sectin 3.4 Remved recmmendatin fr EDI Sectin 3.8 Updated test lab infrmatin 26.0 Sectin 3.1 Added Sftware Update supprt fr 4G devices January 2013 December 2013 July 2014 Nvember 2014 Versin 26 Verizn Wireless All Rights Reserved Page 4

5 1 Objective The purpse f this dcument is t define and describe the Open Develpment Device Certificatin prcess, Device testing and cnfrmance requirements that Devices must meet befre they are certified fr use n the Verizn Wireless Netwrk. This dcument includes requirements that cver vice Devices, vice/data Devices, and data nly Devices. This includes, but nt limited t, handsets, PDAs, data cards, M2M Devices, embedded PCs, and mre. Versin 26 Verizn Wireless All Rights Reserved Page 5

6 2 Glssary and Definitin f Terms agps AM B2B CDMA CDG CA CE CPE DLD DMD EDI ENAP ESN FIT GCF IOT ITL LBS MEID MDN MMS MMSC NDET Lab NDRA NRB NSRA NWRA OEM OD ODPT ODS Assisted GPS Accunt Manager Business t Business Cde Divisin Multiple Access CDMA Develpment Grup Certificatin agreement Cnfrmité Eurpéenne, "Eurpean cnfrmity" Custmer Premise Equipment Device Lck Dwn Device Management Database Electrnic Data Interchange Early Netwrk Access Prgram Electrnic Serial Number Field Interperability Testing Glbal Certificatin Frum Interperability Independent Test Labratry Lcatin Based Services Mbile Equipment Identifier Mbile Directry Number Multi Media Messaging services Multimedia Messaging Service Center Netwrk Device Evaluatin Test Labratry Natinal Direct Revenue Assurance Netwrk Repair Bureau Natinal SurePay Revenue Assurance Natinal Whlesale Revenue Assurance riginal equipment manufacturer, Open Develpment Open Develpment Prduct Team (Including Business Develpment and Accunt management.) Open Develpment Specificatin Versin 26 Verizn Wireless All Rights Reserved Page 6

7 OTA PDI PM RA RF RN SFN TECC VSP WS Over The Air Prduct Develpment and Integratin Prduct Manager Revenue Assurance Radi Frequency Release Ntes Safe Fr Netwrk Test Entrance Criteria Checklist Vertical Slutins Prvider Whlesale Versin 26 Verizn Wireless All Rights Reserved Page 7

8 3 Device Cmpliance Prcess 3.1 Entrance Criteria All Devices must be type apprved and certified by the United States Federal Cmmunicatins Cmmissin (FCC) and classified by the Department f Cmmerce's Bureau f Industry and Security (BIS) befre ODIS Cnfrmance testing can cmmence. All Glbal GSM capable Devices, requesting GSM and CDMA certificatin by VZW, must receive GCF certificatin and CE Certificatin in additin t FCC certificatin befre ODIS Cnfrmance testing can cmmence. Each OD DEVELOPER will receive a unique VZW-ID. The VZW-ID will be used in cnjunctin with a PRODUCT-ID f the submitted Device (assigned by the DEVELOPER), the OTA-ID and the RF unit's FCC ID t frm the Device tracking ID. Verizn Wireless and OD Authrized ITL will identify individual Devices prir t Certificatin using nly this Device tracking ID. The OD Device Tracking ID VZW-ID will be assigned fr each DEVELOPER submitting a Device fr Cnfrmance Example VZW PRODUCT-ID (Mdel Number) Assigned by the DEVELOPER Up t 10 alphanumeric characters OTA-ID Assigned by the DEVELOPER In accrdance with the Open Develpment Specificatin (ODS) OTA requirements the OTA-ID is a numeric representatin f a tw individual binary cmpnents mb_mdel 8 bits mb_firm_rev 16 bits FCC-ID Required Prir t Open Develpment Cnfrmance FCC Grantee ID (First 3 Characters) FCC Prduct Cde (Remaining up t 14 Characters) Example A1C BIS ECCN and CCATS Required Prir t Open Develpment Cnfrmance Example " 5A992, G " ITL will reprt test results back t Verizn Wireless using nly the OD Device Tracking ID All 4G LTE and 4G LTE Multi-Mde devices must have capabilities t supprt Sftware/Firmware Update Over-The-Air. Versin 26 Verizn Wireless All Rights Reserved Page 8

9 3.2 Pre-Submissin Prcess Flw Open Develpment Device Develper (referenced as DEVELOPER) visits Web Prtal DEVELOPER registers via Web Prtal Partner lgs int the OD Prtal using their VZWID and registers the Device by adding a new Device. The mdel the Device is registered as shuld match exactly what s prvided in the DMD frm and shuld reflect what the Device is being marketed and sld as. In rder fr develper t access any Open Develpment (OD) dcuments, DEVELOPER must register by prviding the fllwing: Name Cmpany Title r Psitin Full mailing address t include cuntry address Cntact phne number(s) DEVELOPER dwnlads Open Develpment Specificatin (ODS) and OD presubmissin dcuments and takes nte f any psted ntes t the dcumentatins page. Develper prduct preparatin DEVELOPER cmpletes and submits the NDA questinnaire, Partner frecasting wrksheet, TECC frm, Release ntes, Device data sheet (DEVELOPER frmat), Master Shwcase excel dcument, Pwer Pint Device / Slutins One Pager, and DMD frm. The DMD and Frecasting wrksheet will be prvided after agreements are executed as applicable. Frecasting wrksheet is nt required fr whlesale Devices. NDA, and/r Whlesale agreements are executed as applicable. Whlesale Devices cannt use the Verizn mark. Open Develpment Certificatin Agreement and VSP Agreement executed as applicable. This will allw fr the use f the Verizn mark. Nte: This prcess may take 1-3 mnths r lnger t cmplete. Versin 26 Verizn Wireless All Rights Reserved Page 9

10 DEVELOPER receives a list f OD Authrized Independent Test Lab(s) (ITL) frm ODPT. DEVELOPER makes a decisin n which ITL t use. DEVELOPER sends an t VZWOpenDevelpment-1@VeriznWireless.cm (r t the supprting VZW representative) requesting a VZW-ID, which will enable access t the Device certificatin prtal, with the fllwing infrmatin: Channel Current VZW cntact DEVELOPER s inf: First Name Last Name Cmpany Address City State/Prvince Zip Cuntry Phne Mbile Fax DEVELOPER adds infrmatin regarding the new Device and its attributes nt the prtal using the cmpany VZW ID lg-in. DEVELOPER submits all required infrmatin n the OD prtal and ntify their VZW representative. A Device Lck Dwn (DLD) meeting will be held between DEVELOPER and VZW team t review the Device submissin. The meeting agenda will cver the fllwing: Submissin verview Submissin Type (SFN, Full Certificatin, Maintenance Release) (AM/PM) Device Overview (OEM) Target distributin channel Direct: VSP (OEM/PM) Indirect: Whlesale/LRA, Prepaid/Pstpaid, Resellers (OEM/Reseller/AM) Dcumentatin Review (ODPT/NDET) Device Slutin One pager Device Marketing Inf Device Prfile fr Activatin Authrizatin (DMD) Device Release Ntes Device Test Entrance Criteria (TECC) Device Frecast and Pricing Need Waivers Discuss Additinal Testing Need (ODPT) MMS GCF LBS/aGPS Private Netwrk Revenue Assurance Testing & Schedule (OEM/ODPT) Versin 26 Verizn Wireless All Rights Reserved Page 10

11 Test Sample Guideline Testing Lab Chice Targeted Test Start and Cmpletin Date Terms and Cnditins f Inactivity Sample Devices (ODPT) Befre certificatin is finalized, Verizn Wireless must receive a sample Device. The address and cntact infrmatin fr where t send this will be cvered n the DLD. Device Intrductin Prcess fr Prductin Devices (ODPT) Device ID (ESN/MEID/IMEI) Uplad Prcess (see Sectin 3.4) OD Prtal Electrnic Data Interchange (EDI) EDI Verificatin LTE SIM Inf fr M2M devices (PM/OEM) SIM SKU SIM prcurement methd SIM Frm Factr Other Infrmatin (ODPT) Device certificatin r WS agreements Certificatin term & Recertificatin Pending the successful cmpletin f the DLD requirements, Verizn will ntify the selected ITL with the apprval t start and the required testing. Versin 26 Verizn Wireless All Rights Reserved Page 11

12 3.3 OD Cmpliance Testing The fllwing figure shws a high level view f the Open Develpment certificatin prcess Early Testing Prcess Flw DEVELOPER may request early testing depending n the need f develpment prir t certificatin. ODPT/NDET will review the request and apprve based n the need fr live netwrk testing during develpment. Early Netwrk Access Prgram (ENAP) If the DEVELOPER is using a Verizn Wireless certified mdule, up t 20 activatins can be allwed fr develpmental purpses. Upn receiving the request with the Device backgrund infrmatin, VZW will lad the Test Device(s) MEID/ESN/IMEI in DMD. The develper shuld then wrk with their VZW sales representative t subscribe and activate lines t cnnect the Test Device(s) with VZW netwrk. Upn being certified, the Test Device MEID/ESN/IMEIs must be upladed t the DMD using the OD prtal r EDI feed. Safe Fr Netwrk (SFN) If the DEVELOPER cmpletes SFN testing successfully, up t 500 activatins per prject can be allwed fr further develpment. DEVELOPERS must submit the Versin 26 Verizn Wireless All Rights Reserved Page 12

13 Device infrmatin fr ODPT/NDET t review and the testing must be cnducted at a OD Authrized ITL. Testing Prcess Vendr submits Device infrmatin n the prtal and sends ENAP r SFN request with supprtive reasns and test ESNs/MEIDs/IMEIs. RN, TECC, and Device Slutin One Pager are required fr SFN. ODPT and NDET team review and apprve the ENAP r SFN request. Fr SFN: DEVELOPER cntacts and cntracts with OD Authrized ITL. DEVELOPER enters Device int OD Authrized ITL fr SFN testing. OD Authrized ITL cmpletes testing and submits test results t NDET Lab. NDET Lab verifies Device meets all SFN requirements Upn successful cmpletin, DEVELOPER may request up t 500 activatin, and ntifies ODPT team via that they are ready t start netwrk testing Apprved test ESNs/MEIDs/IMEIs are prvisined n the netwrk fr Test Devices. DEVELOPER cmpletes OTA testing - debug /fix /retest issues. DEVELOPER is ready fr OD full cmpliance submissin ODPT ntifies DEVELOPER t discnnects test MDNs n later than 60 day after testing is cmpleted DEVELOPER ntifies ODPT that all test MDNs are discnnected OD Standard Lab Testing Prcess Flw DEVELOPER wrks directly with IOT Lab(s) n schedule, payment and cmplete IOT testing prir t r in parallel with OD required testing. DEVELOPER chses and cntacts an OD Authrized ITL frm the Verizn Wireless apprved list (see Sectin 3.8) DEVELOPER submits required Devices and prduct dcumentatin t the OD Authrized ITL. Versin 26 Verizn Wireless All Rights Reserved Page 13

14 The OD Authrized ITL executes Verizn Wireless apprved test plans based n the TECC fr cnfrmance against ODIS. The OD Authrized ITL prvides test results t ODPT and NDET teams. Verizn Wireless wns the test results fr the OD cmpliant Device.. NDET Lab then validates with the ITL that the submitted Device has met the requirements f the ODIS. If the Device meets the requirements f the ODIS, the Device is OD cmpliant:: The Verizn Wireless NDET Lab may chse t wrk directly with certain whlesale channel DEVELOPERs fr testing against the ODIS. At this pint, Device Lab testing is cmpleted. Testing and DMD ppulatin with the Device prfile are required befre certificatin. Receiving all ESN/MEIDs/IMEIs int DMD per Sectin 3.4 is required befre Devices can be activated. If the Device des nt meet the requirements f the ODIS: DEVELOPER is ntified via acceptable electrnic media DEVELOPER chses ne f the fllwing paths frward: Dispute reslutin (DEVELOPER des nt agree with OD Authrized ITL results) Device rewrk (DEVELOPER returns t OD Authrized ITL fr retesting) DEVELOPER withdraws its Device Additinal Testing OD Standard Lab testing cmpletin is prerequisites t all ther testing LBS/aGPS Applicatin Testing Prcess Flw After OD Standard Lab Test cmpletin, DEVELOPER may start the LBS/aGPS prcess. DEVELOPER submits the "OD LBS/aGPS pre-certificatin Requirements" dcument (applicatin) ODPT and PDI review and apprve OD LBS/aGPS applicatin ODPT wrks with Netwrk PDI n target LBS/aGPS applicatin testing. DEVELOPER submits Test Devices fr netwrk LBS/aGPS applicatin testing. Netwrk team evaluates the test results and apprves the applicatin MMS Device Testing Prcess Flw Devices that are MMS capable and require the use f Verizn MMSC server must cmplete the MMS prcess befre Device certificatin. If the Device hgg DEVELOPER submits the cmpleted MMS Prfile questinnaire as part f the TECC frm submissin. The frm is part f the TECC template DEVELOPER wrks directly with Nkia Siemens Netwrks (NSN) n schedule, payment and cmplete MMS IOT testing. Versin 26 Verizn Wireless All Rights Reserved Page 14

15 DEVELOPER prvides Device prfile questinnaire ed t Verizn Wireless MMS Admin at VZWMMSAdmin@VeriznWireless.cm, three weeks prir t the start f testing at NSN IOT Lab. VZW MMS Admin reviews and apprves the MMS prfile. Verizn Wireless generates and ODPT distributes the User Agent t the DEVELOPER. DEVELOPER can prceed with NSN IOT testing n the set schedule date. NDET reviews and apprves the MMS IOT results reprt. After apprval f the MMS IOT results, DEVELOPER prepares 2 Devices fr MMSC Server Testing: DEVELOPER prvisins each Device with the new assigned MMS User Agent DEVELOPER ensures each Device is able t send, receive, frward, and reply t a MMS. DEVELOPER sends the ESNs/MEIDs/IMEIs f each Device t ODPT DEVELOPER sends 2 Devices t Verizn Wireless with batteries, data cables, chargers and instructins t changing MMSC URL thrugh either PST r prgramming menu (name and address will be prvided by Verizn). ODPT tests t ensure the Device prfile is laded t Verizn s netwrk Revenue Assurance Testing Prcess Flw Revenue assurance testing may be required t ensure the usage billing is prcessed crrectly and in cmpliance with the apprved pricing. ODPT team shall determine RA testing can start. ODPT shall btain the ESNs/MEIDs/IMEIs f the Devices t be used in RA testing frm the Develper. ODPT team shall cntact apprpriate Revenue assurance team (Whlesale, Direct) and prvide the ESNs/MEIDs/IMEIs. RA team shall prvisin thse ESNs/MEIDs/IMEIs with mbile numbers. ODPT team shall advise DEVELOPER the Device has been prvisined and is ready t be activated. DEVELOPER activates the Devices. DEVELOPER ships Devices directly t the apprpriate Revenue Assurance testers with the NDET Lab apprved SW and HW versins. DEVELOPER will activate the Devices. Revenue Assurance team cnducts the testing and apprves the usage billing. ODPT ppulates individual Device s prfile in DMD based n the DMD frm cmpleted by the DEVELOPER. ODPT prvides DEVELOPER with Device certificatin apprval with an expiratin date nt t exceed 36 mnths frm the time f the date f the apprval per the Certificatin Agreement. Versin 26 Verizn Wireless All Rights Reserved Page 15

16 Inactivity and Test Devices If the certificatin status remains inactive fr mre than 2 mnths, the Device may be subjected t anther review t be cmpliant with the latest Verizn Wireless Specificatins. OEM must deactivate all Test Devices after certificatin cmpletes. Test Devices shall nt be sld as final prducts. Versin 26 Verizn Wireless All Rights Reserved Page 16

17 3.4 Device Intrductin Prcess Flw After the Device is apprved and befre the Device ges t market, the Device must be entered int VERIZON WIRELESS Device Management Database (DMD) as the certified Device t allw the future activatin. This Prcess is knwn as the Device identificatin uplad (ESN/MEID fr 3G Devices r IMEI fr 4G Devices). If the Device identificatin is nt laded int the DMD, the system will prevent the Devices frm activatin. The DEVELOPER can uplad the Device identificatins using ne f the fllwing appraches: 1. Electrnic Data Interchange (EDI) 2. ODI Web Prtal - This ptin is available nly fr Devices using VERIZON WIRELESS apprved mdule. A 4-8 hur windw is needed fr the system t prcess the EDI r ODI Web Prtal uplad. If either f the tw prcesses described abve is nt fllwed, the VERIZON WIRELESS s system will prevent the Devices frm activatin. If the Device identificatins are upladed via EDI r the OD Prtal befre 10:30pm, EST, the Device identificatins will map t DMD and will be ready fr activatin next mrning (after midnight) Example: File sent by 10:25pm, EST n a Tuesday, file will map t DMD n Wednesday mrning at 12am, EST If the Device identificatins are upladed via EDI r the OD Prtal after 10:30pm, the ESNs/MEIDs/IMEIs will map t the DMD the fllwing 2 nd business day Example: File sent after 10:30pm, EST n a Wednesday, will map t DMD n Friday mrning at 12am, EST Electrnic Data Interchange (EDI) ODPT prvides DEVELOPER with Electrnic Data Interchange (EDI) requirements and credentials fr accepting Device technical infrmatin submissin. DEVELOPER setup the EDI feed with VERIZON WIRELESS t cnnect the electrnic feed with VERIZON WIRELESS s Device Management Database (DMD) Versin 26 Verizn Wireless All Rights Reserved Page 17

18 ODPT prvides DEVELOPER the OD SKU number fr the apprved Device DEVELOPER/ODPT verifies the EDI feed fr the Device is linked t the OD SKU prperly. OEM is expected t take 5 ESNs/MEIDs/IMEIs previusly laded as Test Devices and upladed via the EDI feed t the Device SKU number, and send the 5 ESNs/MEIDs/IMEIs t ODPT fr verificatin. Upn verificatin, VZW will change the 5 ESNs/MEIDs/IMEIs back t Test Devices. DEVELOPER uplads individual Device specific technical data (including ESNs/ MEIDs/IMEIs/ICCIDs, Make, Mdel) t the prvided OD SKU t ppulate the Device infrmatin in the DMD. ODI Web Prtal DEVELOPER captures all f the Device identificatins (ESNs/MEIDs/IMEIs) in a Cmma-Separated Value (CSV) file as fllwed: The ESNs/MEIDs/IMEIs will start n the first line f the first clumn. Fr Devices with IMEI & ICCID pairings the IMEIs will be placed in clumn A and ICCIDs will be placed in clumn B The name f the file shuld nt cntain any special characters (e.g. spaces, dashes, qutatin marks, etc) and must cntain the make, mdel and ttal number cunt f ESNs/MEIDs/IMEIs r IMEI/ICCIDs laded). Example f the.csv file: File Name: CmpanyXYZ_PrductABC_5.csv ESN/MEID/IMEI: IMEI/ICCID pair: DEVELOPER lgs int OD Web Prtal, click n the Uplad ESN/MEID link/tab next t the apprved Device. In the uplad screen select the frmat f the serial numbers that will be upladed. The frmat must be ne f the fllwing: IMEI (14 r 15) numeric r alpha MEID (14) alpha numeric nly ESN HEX (8) alpha numeric nly IMEI/ICCID Pair- IMEI(14 r 15) numeric r alpha & ICCID (16) alpha nly Versin 26 Verizn Wireless All Rights Reserved Page 18

19 It is very imprtant t select the crrect file cntent type since the uplad prcess will check the frmat accrdingly. Once the DEVELOPER uplads the Cmma-Separated Value (CSV) file f Device identificatin (ESNs/MEIDs/IMEIs r IMEI/ICCID pairs) via the OD prtal, the file is autmatically apprved and upladed if the file frmat is crrect. An ntificatin is autmatically sent t ODPT and the DEVELOPER prviding ntice that an ESN/MEIDIMEI file has been upladed and autmatically apprved. The Device identificatin (ESNs/MEIDs/IMEIs r IMEI/ICCID pairs) prvided in the.csv apprved file will take up t 1 business day t lad int the Verizn Wireless Device Management Database system. Open Develpment certified apprved Devices are available fr activatin nce the (ESNs/MEIDs/IMEIs r IMEI/ICCID pairs) are laded int the Verizn Wireless Device Management Database system. Deactivated Test Devices t be sld as prductin Devices shall be reupladed by DEVELOPER as certified Devices via OD prtal r EDI. Versin 26 Verizn Wireless All Rights Reserved Page 19

20 3.5 ODS Agreement Vilatin Prcess Flw Upn knwledge f any Rgue Devices, Applicatins r Vilatins t OPEN DEVELOPMENT CERTIFICATION AGREEMENT with Verizn Wireless the fllwing will take place: ODPT ntifies DEVELOPER f Device cmpliance issue (rgue Devices r applicatins detected) Develper will ship 2 sample Devices within 48 hurs upn receiving the frmal request frm Verizn fr re-testing. ODPT takes remedial/immediate actin t safeguard the Verizn Wireless netwrk Verizn Wireless retains the right t restrict r eliminate individual OD Device access t the Verizn Wireless netwrk if Verizn Wireless has cncerns abut harm t the Netwrk. If ODPT determines that the issues are the results f Device evlutin and the DEVELOPER had prir knwledge f the ptential impact n Device acceptance status: ODPT suspends Device certificatin status (ESN/MEID/IMEIs in the DMD are placed int a suspended state t prevent any ptentially harmful Devices frm being activated nt the Verizn Wireless Netwrk). DEVELOPER initiates and enters Device Maintenance & Regressin Testing Prcess Flw (see Sectin 3.7). Versin 26 Verizn Wireless All Rights Reserved Page 20

21 3.6 Device Evlutin r Certificatin Expiratin Prcess Flw Device Evlutin: At any time, in case f any updates t the certified sftware r hardware, DEVELOPER must ntify ODPT and prvide all submissin dcumentatins t ODPT DEVELOPER prvides all submissin dcuments with the Device changes in detailed descriptins ODPT/NDET determines the level f testing required based n the updated Device. DEVELOPER initiates Device Maintenance & Regressin Testing Flw Certificatin Expiratin: All Verizn Wireless Open Develpment Certified Devices have a certificatin perid f 3 years. The DEVELOPERs must initiate requests t retired r t extend the Device Certificatin perid fr each Device 90 days prir t the expiratin date f the current certificatin. Devices seeking recertificatin may be subjected t g thrugh Device Maintenance & Regressin Testing t be cmpliant with the latest Verizn Wireless Specificatins. If the DEVELOPER chses t retire the Device r des nt take any actins, all future Device activatins will be blcked after the Certificatin perid expires. DEVELOPER ntifies ODPT the decisin n whether t retire the Device r t extend the Certificatin 90 days prir t the Certificatin perid expires. If the plan is t retire the Device, then DEVELOPER sends the Re-Certificatin Request Frm t ODPT Verizn will nt accept future activatins f the Device. If the plan is t extend the Certificatin, then DEVELOPER sends the Release Ntes & Re-Certificatin Request Frm t ODPT ODPT/NDET determines the level f testing required based n the current Verizn specificatins. DEVELOPER submits Device fr Device Maintenance & Regressin Testing. Versin 26 Verizn Wireless All Rights Reserved Page 21

22 3.7 Device Maintenance & Regressin Testing Prcess Flw Device Maintenance & Regressin Testing Flw DEVELOPER submits updated TECC, RN and DMD t ODPT/NDET Lab fr evaluatin. DEVELOPER crdinates with the OD Authrized ITL t execute regressin testing (In crdinatin with Verizn Wireless NDET Lab). Verizn Wireless retains the right t, at its sle discretin, t intrduce and remve requirements frm the ODIS. DEVELOPER submits required Devices and dcumentatin t OD Authrized ITL. OD Authrized ITL executes Verizn Wireless OD regressin test plans fr cntinued cnfrmance against ODIS. OD Authrized ITL prvides DEVELOPER Device results (standardized media and file frmats). If the Device meets regressin test criteria in ODIS, the OD Authrized ITL frwards the results t the ODPT and the Verizn Wireless NDET Lab t verify that the Device meetings the ODIS. Upn ntificatin frm the OD Authrized ITL & apprval frm the VZW NDET Lab, ODPT prvides DEVELOPER a new Certificatin Ntice fr a three year perid. DEVELOPER has ptin t cnduct OD Best Practice testing. If the Device des nt meet the testing criteria DEVELOPER may chse ne f the fllwing paths frward: Dispute reslutin (DEVELOPER des nt agree the Authrized ITL results). Device rewrk (DEVELOPER returns t OD Authrized ITL t cntinue when the Device is ready). Versin 26 Verizn Wireless All Rights Reserved Page 22

23 3.8 Test Lab Cntact infrmatin Authrized Independent Test Lab Infrmatin ITL Name 7 Layers Inc. Technlgy LTE Only Supprted Address 15 Musick, Irvine, CA, URL Cntact #1 Bris Binger Phne Fax Bris.Binger@7Layers.cm ITL Name Technlgy Supprted Address CETECOM Inc LTE Only 6370 Nancy Ridge Dr., Suite 101 San Dieg, CA / URL Cntact #1 Aml There Prgram Manager Phne Fax Aml.There@cetecm.cm ITL Name Technlgy Supprted Address Intertek Labs 2G/3G, LTE Only, LTE Multimde 731 Enterprise Drive Lexingtn, KY URL Cntact #1 Gwyn McNew - Wireless Engineering Manager Phne Fax Gwyn.Mcnew@intertek.cm Cntact #2 Rbbie Payne Phne Fax Rbbie.Payne@intertek.cm Versin 26 Verizn Wireless All Rights Reserved Page 23

24 ITL Name Technlgy Supprted Address PCTEST Engineering Labratry, Inc. 2G/3G, LTE Only, LTE Multimde Prject Mgr. Carrier/Infrastructure Testing 6660-B Dbbin Rad Clumbia, MD URL Cntact #1 Andrea Zawrski - Labratry Manager Phne Fax andrea@pctestlab.cm ITL Name Technlgy Supprted Address SGS Wireless U.S., Inc. 2G/3G, LTE Only, LTE Multimde W. Bernard Drive Suite 150 San Dieg, CA Dawn Saad LTE Operatins manager URL Cntact #1 Phne x19122 Fax Dawn.Saad@sgs.cm ITL Name Tech Mahindra (Americas) Technlgy 2G/3G, LTE Only, LTE Multimde Supprted Address STE 203, 1001 Durham Avenue, Suth Plainfield, NJ URL Cntact #1 Arunav Ry Phne Fax arunav.ry@techmahindra.cm Cntact #2 Upesh Kumar Phne Fax upeshku@techmahindra.cm Versin 26 Verizn Wireless All Rights Reserved Page 24

25 Inter-Operability (IOT) Test Labs IOT Test Lab Alcatel-Lucent Name Cntact Liza Ottesen Phne IOT Test Lab Telefnaktieblaget LM Ericssn Name Cntact Je Bruccliere Phne IOT Test Lab Nkia Siemens Netwrks Name Cntact Alisn Myers Phne Versin 26 Verizn Wireless All Rights Reserved Page 25