LTE_OTADM_Requirements_June2010
D EVIC
E R EQUIREMENTS
LTE OTADM
V ERSION 5.0
Issued: June 2010
IMPORTANT – PLEASE READ
This document provides initial information related to the Verizon Wireless Long Term Evolution (LTE) OTADM requirements. 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. Verizon Wireless is not providing any license necessary to access or utilize any source materials referenced herein. It shall be the responsibility of the developer to obtain any such licenses, if necessary.
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.
Revision History
Author Description of Changes Date Verizon Wireless Version 1.0: Initial version 11/12/2009
Verizon Wireless Version 2.0:
1.) Section 4.1.3.
2.2 Information on Certificates added.
12/17/2009
Verizon Wireless Version 3.0:
1.)Added requirements for handset form factor devices.
2.)Added user initiated device management requirements.
3.)Updates to section
4.3.
02/11/2010
Verizon Wireless Version 4.0:
1.)Added IMS node.
2.)Modified References
3.)High Severity changed to Mandatory and Low to
Optional
03/25/2010
Verizon Wireless Version 5.0:
1.)Changed server password in DMAcc Subtree.
2.)Changed APN inactivity timer from infinity to
130min.
3.)Changes server domain for LTE devices
4.)Minor clarifications
06/25/2010
T ABLE OF C ONTENTS
1INTRODUCTION (7)
1.1 A PPLICABILITY (7)
1.2 3GPP R ELEASE 8S PECIFICATIONS (7)
1.3 G LOSSARY/D EFINITIONS/A CRONYMS (7)
1.4 R EQUIREMENTS L ANGUAGE (8)
2HARDWARE SPECIFICATIONS (9)
2.1 M ECHANICAL (9)
2.2 E LECTRICAL (9)
3USER EXPERIENCE AND INTERACTIONS (10)
3.1 USER EXPERIENCE (D EVICE) (10)
3.1.1Firmware OTA Update (10)
3.1.1.1 Network-Initiated Update (10)
3.1.1.1.1 Mandatory Severity (10)
3.1.1.1.1.1 Download (10)
3.1.1.1.1.1.1 Inform User of Download (10)
3.1.1.1.1.1.2 Download Accepted (11)
3.1.1.1.1.1.3 Download Canceled after Accepted (11)
3.1.1.1.1.2 Update (11)
3.1.1.1.1.2.1 Inform User of Update (11)
3.1.1.1.1.2.2 Update Accepted (11)
3.1.1.1.1.2.3 Update Deferred (11)
3.1.1.1.1.2.4 Update Completed (11)
3.1.1.1.2 Optional Severity (11)
3.1.1.1.2.1 Download (12)
3.1.1.1.2.2 Update (12)
3.1.1.1.2.2.1 Inform User of Update (12)
3.1.1.1.2.2.1.1 Update Accepted (12)
3.1.1.1.2.2.1.2 Update Deferred (12)
3.1.1.1.2.2.1.3 Update Rejected (12)
3.1.1.1.2.2.1.4 Update Completed (12)
3.1.1.1.2.2.2 Network-Initiated During Deferred Update (12)
3.1.1.2 User-Initiated Update (12)
3.1.1.2.1 Check Status (12)
3.1.1.2.2 Check for New Firmware Update (13)
3.1.1.2.3 Update Available (13)
3.1.1.2.4 Update Package Not Available (13)
3.1.1.2.5 User-Initiated Attempt during a Deferred Update (13)
3.1.1.3 Client-Initiated Device Firmware Update (N/A) (13)
3.1.1.4 Interruptions to OTADM activity (13)
3.1.1.
4.1 No network available when initiating OTADM (User, Client or Network-
Initiated) 13
3.1.1.4.2 Connection Failure during the OTADM session (User-Initiated Session) (14)
3.1.1.
4.3 Connection Failure during the OTADM session (Client-Initiated Session)..14
3.1.1.4.3.1 User power down during the OTADM download session (14)
3.1.1.
4.4 Insufficient coverage during the download (User, Client or Network Initiated)
14
3.1.1.4.5 DM or Download Fatal Error (User, Client or Network Initiated) (14)
3.1.1.4.6 Update Fatal Error (14)
3.1.1.
4.7 Keypad interaction during Download (Applicable only to handset form factor
devices) 14
3.1.1.
4.8 All interruptions during Update (Applicable only to handset form factor
devices) 14
3.1.1.4.9 Accessory Interaction (Applicable only to handset form factor devices) (14)
3.1.2Subscriber Device Management (15)
3.1.2.1 Network-Initiated Configuration Sessions (15)
3.1.2.1.1 Device Profiling - User Input Required (15)
3.1.2.1.1.1.1 User Accepted (15)
3.1.2.1.1.1.2 User Canceled (15)
3.1.2.1.1.2 Changes to Device Settings - User Input Required (15)
3.1.2.1.1.2.1 User Accepted (15)
3.1.2.1.1.2.2 User Rejected (16)
3.2 USER I NTERFACE (D EVICE) (16)
3.2.1Firmware Update (16)
3.2.1.1 Network or Client Initiated (16)
3.2.1.1.1 New Firmware Download Notification (16)
3.2.1.1.2 Firmware Download (16)
3.2.1.1.3 Firmware Update Notification (17)
3.2.1.1.4 Firmware Update (17)
3.2.1.1.5 Firmware Update Complete Notification (17)
3.2.1.2 User Initiated (18)
3.2.1.2.1 Check Status (18)
3.2.1.2.2 Install Deferred SW (18)
3.2.1.2.3 Check New (18)
3.2.2Subscriber Device Management (19)
3.2.2.1 Predefined Texts (19)
4FIRMWARE SPECIFICATIONS (20)
4.1 C OMMON R EQUIREMENTS FOR OTADM (20)
4.1.1Compliance with Standard Protocols (20)
4.1.1.1 OMA Industry Standard (20)
4.1.1.2 Other Industry Standards (20)
4.1.1.3 Standards Compliance (20)
4.1.2OTADM Client (21)
4.1.3OTADM Tree Support (21)
4.1.3.1.1 Security parameters (22)
4.1.3.2 Transport Security (22)
4.1.3.2.1 PDN (22)
4.1.3.2.2 Data Encryption using HTTPS (22)
4.1.3.3 Authentication (23)
4.1.3.3.1 Mutual Authentication (23)
4.1.3.3.1.1 Failed Authentication Attempt Handling (23)
4.1.3.3.2 Authentication Key (23)
4.1.3.4 Digital Signature (23)
4.1.3.5 Integrity (23)
4.1.4Device Management Tree (23)
4.1.4.1 Commands (24)
4.1.4.2 Access Control List (ACL) (24)
4.1.4.3 Verizon Wireless Defined Base DM Tree (24)
4.1.4.4 DMAcc Subtree (24)
4.1.4.5 DevInfo Subtree (25)
4.1.4.6 DevDetail Subtree (25)
4.1.4.7 Managed Objects Subtree (25)
4.1.4.8 Managed Applications Subtree (26)
4.1.5DM Connectivity Requirements (26)
4.1.5.1 Network-Initiated DM Sessions (26)
4.1.5.1.1 DM Notification via SMS message (Trigger) (26)
4.1.5.1.2 Client-Initiated Download (Package not available) (26)
4.1.5.1.3 LTE Service Required (27)
4.1.5.1.4 Network-Initiated (No) Retry (27)
4.1.5.2 Client-Initiated DM Sessions (27)
4.1.5.2.1 PDN change (27)
4.1.5.2.2 LTE Service Required (27)
4.1.5.2.3 Client-Initiated Retry (27)
4.1.5.2.4 Interrupted Client-initiated Retry (27)
4.2 FOTA S PECIFIC R EQUIREMENTS (28)
4.2.1Support of Standard Protocols (28)
4.2.1.1 Device System Configuration (28)
4.2.1.1.1 OMA DM Tree Support for FOTA (28)
4.2.1.2 Update Package (28)
4.2.1.2.1 Update Package Security (28)
4.2.1.2.1.1 Update Package Security (Digital Signature) (28)
4.2.1.2.1.2 Update Package Security (Evaluation of current firmware) (29)
4.2.1.3 Download Procedure (29)
4.2.1.3.1 Download Mechanism (29)
4.2.1.3.2 OMA Download Over-the-Air (DLOTA) Client (29)
4.2.1.3.3 Download Initiation (29)
4.2.1.3.4 Secure Download (29)
4.2.1.3.5 Fault Tolerant Download (29)
4.2.1.3.6 Cancel Download (29)
4.2.1.3.8 Download Result Reporting (29)
4.2.1.3.9 Package Validation after Download (prior to update) (29)
4.2.1.4 Update Procedure (30)
4.2.1.4.1 User Reject (prior to update) (30)
4.2.1.4.2 Protection of User Data/Content and User Applications During Update (30)
4.2.1.4.3 Update Result Reporting (30)
4.2.1.4.4 Update - Fatal Error (30)
4.3 SDM R EQUIREMENTS (30)
4.3.1Support of Industry Standards and Verizon Wireless Requirements (30)
4.3.1.1 OMA Defined Managed Objects (30)
4.3.2OMA-DM Tree and Standard Commands (30)
4.3.2.1 Device Capabilities Management (31)
4.3.2.2 Diagnostic Monitor Management (32)
4.3.2.3 Connectivity Management (33)
4.3.2.4 Lock and Wipe Management (34)
5REFERENCES (36)
1I NTRODUCTION
Verizon Wireless is planning to launch LTE network service in the 3GPP Band 13 frequency band (700 MHz C Block). This document includes an Over-The-Air (OTA) device management solution for devices on this network. This publication is part of Verizon Wireless’ compliance with the FCC’s rules for 700 MHz C Block (47 C.F.R. § 27.16), as explained in the FCC’s Second Report and Order in WT Docket No. 06-150, “Service Rules for the 698-746, 747-762 and 777-792 MHz Bands” released on August 10, 2007.
In this document, the terms LTE (Long Term Evolution) and E-UTRA (Evolved Universal Terrestrial Radio Access) are considered equivalent.
1.1A PPLICABILITY
These requirements apply to all devices designed to operate on the Verizon Wireless LTE 3GPP Band 13 network. 3GPP Band 13 is per 3GPP TS 36.101: Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception.
For any questions related to this document, please contact Verizon Wireless through the Verizon Wireless Open Development website.
1.23GPP R ELEASE 8S PECIFICATIONS
Refer to the 3GPP Release 8 Specifications section of the Verizon Wireless LTE 3GPP Band 13 Network Access Requirements.
1.3G LOSSARY/D EFINITIONS/A CRONYMS
This section defines acronyms and terms used throughout the document.
Acronym/ Term Definition
ConnMO Connectivity Management Object
DCMO Device Connectivity Management Object
Management
Object
DiagMon Diagnostic
DDF Device Description Framework
Set
DMS Data
Model
DTD Document Type Definition
FOTA Firmware Over the Air
FOTC Firmware Over the Cable
FUMO Firmware Update Management Object
LAWMO Lock and Wipe Management Object
Code
Authentication
MAC Message
OMA Open Mobile Alliance
OMA-DM Open Mobile Alliance – Device Management
OTA Over-the-Air
OTADM Over the Air Device Management
PST Product Support Tool
Management
Device
SDM Subscriber
Interface
UI User
Equipment
UE User
WAP Wireless Application Protocol
WDP Wireless Datagram Protocol
Wireless
VZW Verizon
1.4R EQUIREMENTS L ANGUAGE
This document uses the following verbal forms in conjunction with requirements: ?“Shall” or “Shall not” indicates the requirement is mandatory
?“Should” indicates the requirement is recommended but not mandatory ?“May” indicates the requirement is optional
2H ARDWARE S PECIFICATIONS 2.1M ECHANICAL
N/A
2.2E LECTRICAL
N/A
3 U SER E XPERIENCE AND I NTERACTIONS
3.1 USER EXPERIENCE (D EVICE )
NOTE: If the device is a data-centric device like a USB data dongle, PC card or modem, all user
experience, alerts and interactions shall be through the User Interface of the connection manager.
For handset form factor devices, the display of the device shall be used for all user interactions.
3.1.1 F IRMWARE OTA U PDATE
3.1.1.1 N ETWORK -I NITIATED U PDATE
During a network initiated firmware update, a notification is sent to the device and the options
available to user are defined in Summary Table 3-1.
Note: Verizon Wireless shall define the severity of the update. Severity shall be selected to
define what level of control the user shall be allowed over the download/update process.
Summary Table 3-1 – Network-Initiated – Severity Levels, User Actions Download Update User Options User Options Severity
Level
A D R Timer (Accept) A D R Timer Mandatory
9 ˉ ˉ 30 secs. 9 9 ˉ 3 mins. Optional 9
9 9 3 mins. 9 9 9 N/A Legend:
A = Accept, D = Defer, R = Reject
“ˉ” = Not Applicable
“9” = Applicable
3.1.1.1.1 Mandatory Severity
If the severity of the firmware update is “Mandatory”, the download and update shall begin
based on the rules specified below:
3.1.1.1.1.1 Download
3.1.1.1.1.1.1 Inform User of Download
The user is given brief information on the update package, and is given one option with regards
to the download: Accept.
The user can either accept the download or the device shall countdown the time of 30 seconds
until the download will occur. The user cannot “escape” from this operation (except for
operations outlined in Section 3.1.1.2). At the end of the countdown, the device retrieves the
appropriate update package.
NOTE: For data-centric devices like USB data dongle, PC card or modem, the countdown timer shall not be applicable. The connection manager shall wait for user action for the download to occur.
3.1.1.1.1.1.2Download Accepted
?When the user accepts the download, the device shall retrieve the appropriate update package.
?During the download, a progress status shall be displayed to indicate “% complete”.
3.1.1.1.1.1.3Download Canceled after Accepted
If the user cancels the download, it shall be the responsibility of the server administrator to re-queue the message and re-initiate the download.
3.1.1.1.1.2Update
The update shall immediately follow a successful download.
3.1.1.1.1.2.1Inform User of Update
The user is given information on the update package, approximate time of the update, and the following options with regards to the update: Accept or Defer. The user can either accept the update or the device will countdown the time of 3:00 minutes until the update will occur. The user shall also have the option to defer the update.
NOTE: For data-centric devices like USB data dongle, PC card or modem, the countdown timer shall not be applicable. The connection manager shall wait for user action for the update to occur.
3.1.1.1.1.2.2Update Accepted
o The device performs the update.
?If the device is powered off by removing the device from the PC (or any other source of power), or the battery is low (less than 10%) for a handset form factor
device, before the update can be performed, the update shall take place as soon as
the device is plugged back to the source of power.
o During the update a progress status (progress bar and/or counter) shall be displayed to indicate “% complete”
3.1.1.1.1.2.3Update Deferred
o If the user defers the update, the user is given the option to set the time of the update along with a message instructing the user to ensure the device is on (for data-centric
devices, it should be plugged into the PC) and powered at the designated time.
o At the designated time, the device shall perform the update as in section 3.1.1.1.1.2.2
3.1.1.1.1.2.4Update Completed
Upon completion and after the device resets, the user is notified that the update was successful or has failed. User interaction is required to clear this notification.
3.1.1.1.2Optional Severity
If the severity of the firmware update is “Optional”, the download and update shall begin based on the rules specified below:
3.1.1.1.2.1Download
The download shall be treated the same as Mandatory Severity as outlined in Section 3.1.1.1.1.1 3.1.1.1.2.2Update
The update shall immediately follow a successful download.
3.1.1.1.2.2.1Inform User of Update
The user is given information on the update package, approximate time of the update, and the following options with regards to the update: Accept, Defer or Reject.
In the low severity case, user selection is required to move forward. A countdown timer shall not be provided.
3.1.1.1.2.2.1.1Update Accepted
Update accepted shall be treated the same as Mandatory Severity as outlined in Section
3.1.1.1.1.2.2.
3.1.1.1.2.2.1.2Update Deferred
Update deferred shall be treated the same as Mandatory Severity as outlined in Section
3.1.1.1.1.2.3
3.1.1.1.2.2.1.3Update Rejected
If the user rejects the update, the operation shall be terminated. The device shall not attempt to utilize the update package at a later time.
3.1.1.1.2.2.1.4Update Completed
Update completed shall be treated the same as Mandatory Severity as outlined in Section
3.1.1.1.1.2.
4.
3.1.1.1.2.2.2Network-Initiated During Deferred Update
If the device receives a Network-Initiated Firmware update during a Deferred Update, the device shall abandon the original Firmware Update and begin a new Network-Initiated FOTA.
3.1.1.2U SER-I NITIATED U PDATE
A user decides to check if a new firmware update is available for their device. Using the device or connection manager UI, they navigate to a device update function.
The user will have the option to:
Check a firmware update status
Check for new firmware update – this option is available only if there is no pending deferred Update
3.1.1.2.1Check Status
The user will be able to check the status (result) of any previous OTADM related activity.
3.1.1.2.2Check for New Firmware Update
The user will be able to check for a new firmware update package. The device contacts the network to determine if a new firmware update is available and provides the options in Summary Table 3-2, regardless of severity.
Summary Table 3-2 – User-Initiated – Severity Levels, Download/Update User Actions, Interruptions
Download Update
User Actions User Actions
Severity
Levels
Class
A D R A D R
All Optional 999999 Legend:
“9” = Applicable
A = Accept, D = Defer, R = Reject
3.1.1.2.3 3.1.1.2.4 3.1.1.2.5
3.1.1.
4.1Update Available
If the update package is available, the Download and Update will be treated the same as the “Network Initiated Download and Update (Low)” specifications defined in section 3.1.1.1.2 for all severity levels.
Update Package Not Available
If there is no update package for the device, the user is informed that there is no update package at this time.
User-Initiated Attempt during a Deferred Update
If a customer decides to check if a new firmware update is available for their device while a deferred update is pending on the device, any option to check for new update will not be available and instead the option to install the currently deferred update will be shown.
3.1.1.3C LIENT-I NITIATED D EVICE F IRMWARE U PDATE (N/A)
This is a placeholder for any future requirements for Client–initiated firmware updates.
3.1.1.4I NTERRUPTIONS TO OTADM ACTIVITY
No network available when initiating OTADM (User, Client or Network-
Initiated)
Devices not connected to any wireless network for OTADM shall not be able to perform OTADM activity.
In the case of a user-initiated download, if an LTE network is not available, the device shall notify the user of network unavailability.
In the case of a client-initiated or network-initiated download, if an LTE network is unavailable, the device shall NOT notify the user and shall queue the attempt to retry based on the requirements of the “LTE Data Retry”.
3.1.1.
4.2 3.1.1.4.3
3.1.1.
4.4 3.1.1.4.5 3.1.1.4.6 3.1.1.4.7 3.1.1.4.8 3.1.1.4.9Connection Failure during the OTADM session (User-Initiated Session)
If the LTE network is available and the device has initiated OTADM activity but there is a failure in the connection, the device shall display an error message to indicate to the user a failure has occurred. The device shall NOT attempt to automatically reconnect and resume the session.
Connection Failure during the OTADM session (Client-Initiated Session)
If the LTE network is available and the device client has initiated OTADM activity but there is a failure in the connection before the initial DM session is completed, the device shall NOT display an error message to the user. The device shall queue the attempt to retry based on “LTE Data Retry” requirements.
3.1.1.
4.3.1User power down during the OTADM download session
If the user interrupts the download session by powering the device off (by removing the battery), or by pulling out the data-centric device from the PC, the download shall resume once device is turned on again or plugged back into the PC (the source of power).
If the user powers off the device (or pulls out the data-centric device from the PC) during the download by using the END or an equivalent key, the session shall be considered ‘user canceled’ and follow user-canceled rules.
Insufficient coverage during the download (User, Client or Network Initiated)
If the device is in the middle of a download (user has already accepted) and there is loss in network connectivity, the device shall display an error message to indicate no service. The device shall NOT attempt to reconnect to resume the download.
DM or Download Fatal Error (User, Client or Network Initiated)
If the DM session or download experience a fatal error, the device shall notify the user. The device shall not retry the download in this case.
Update Fatal Error
If the update experiences a fatal error, the device may be inoperable and unable to display any warning/message to the user. If possible, the device should notify the user and server administrator of the failure.
Keypad interaction during Download (Applicable only to handset form factor devices)
Key presses shall be ignored during the download with the exception of the keys used for user cancel (e.g. END or an equivalent key).
All interruptions during Update (Applicable only to handset form factor devices) During the update the device is inoperable.
Accessory Interaction (Applicable only to handset form factor devices)
The download and update operations shall not be affected by the presence, addition or removal
of any device accessories. Exception: charging adapter plug-in to charge the device shall be required to proceed with an update when the device battery power is low (less than 10%).
3.1.2S UBSCRIBER D EVICE M ANAGEMENT
SDM sessions shall be initiated by means of network or client-initiated triggers. User-Initiated triggers for SDM related call flows are not defined.
3.1.2.1N ETWORK-I NITIATED C ONFIGURATION S ESSIONS
Network-initiated SMS messages to initiate VZW DM operations shall arrive on the device and the device silently initiates connection with the VZW DM server.
3.1.2.1.1Device Profiling - User Input Required
After initial connection and authentication, but before any SDM data is profiled and sent back to the server, the device shall prompt the user for approval to query device parameters. User input is required to proceed with SDM except while profiling for APNs and IMS parameters. See Table 3-3 for additional UI alert information.
Reference Purpose of Text User Interaction Alert User Options
1 Device
Management Server attempting to
retrieve the user device
settings for DM purposes. Verizon Wireless is attempting to
retrieve configuration settings
from your device. Proceed?
OK (default)
Reject
2 Device
Management Server attempting to
change the user device
settings for DM purposes. Verizon Wireless is attempting to
modify configuration settings on
your device. Proceed?
OK (default)
Reject
Table 3-3 – UI Alert during SDM data profiling and update.
3.1.2.1.1.1.1User Accepted
Once the user acknowledges the response to the SDM profiling message, the device shall proceed with SDM profiling.
3.1.2.1.1.1.2User Canceled
Optionally, the user may elect to cancel the SDM profiling. Device shall NOT automatically retry the session following the user cancel.
3.1.2.1.1.2Changes to Device Settings - User Input Required
Upon receiving new parameters or setting changes, but prior to implementing the changes on the device, the user shall be requested for permission to process the changes. No changes shall be accepted by the device unless the user approves the information request. See Table 3-3 for additional UI alert information.
3.1.2.1.1.2.1User Accepted
Once the user responds with approval to the SDM query message, the setting changes shall be written to the device.
3.1.2.1.1.2.2User Rejected
Optionally, the user may elect to reject the SDM setting changes. Device shall not retry to reconnect to the server following these user canceled operations.
3.2USER I NTERFACE (D EVICE)
3.2.1F IRMWARE U PDATE
Firmware update procedure (FOTA), including downloads, is required by all devices. 3.2.1.1N ETWORK OR C LIENT I NITIATED
For all devices, the following main display requirements shall be met.
3.2.1.1.1 3.2.1.1.2New Firmware Download Notification
The device shall display the following when notifying the user of an available firmware update: ?For handset form factor devices, the display shall be: “New Software Update from Verizon Wireless Starts in: 30 sec”, where 30 is a countdown timer that automatically
decrements until 0 is reached.
For data-centric devices, the display shall be: “New Software Update from Verizon
Wireless is available for download. Please accept to continue.”
NOTE: No timer is available for data-centric devices.
? A readable description of the firmware package shall be received in the download descriptor. If the description does not fit on the display, the screen should be scrollable to allow viewing of the description.
The options available on the display are:
?Only one option shall be offered which starts the download, for example OK or Continue.
?An option to defer the download and update for up to 5 days.
?An option to reject the download is available only when the firmware package priority is “Low”.
NOTE: If the priority is Low, the download timer counts down from 3:00 Minutes.
When 0 seconds is reached, the device shall advance as if it acknowledged the request.
Firmware Download
During the firmware download, the following shall be displayed:
?“Downloading Software from Verizon Wireless”
? A readable description of the firmware package shall be received in the download descriptor. If the description does not fit on the display, the screen should be scrollable to allow viewing of the description.
? A progress bar including a numeric indication of “% complete”.
No options are available for the user on the display during the download process.
If the user cancels the download, a message indicating that the download has been cancelled shall be displayed to the user.
3.2.1.1.3
3.2.1.1.4 3.2.1.1.5Firmware Update Notification
The device shall display the following when the download is complete. This message notifies the user that the firmware update is ready to start:
“Verizon Wireless Update Starts in: 3:00 Minutes”, where 3:00 is a countdown timer that automatically decrements until 0 is reached.
o For data-centric devices, the display shall be: “Verizon Wireless Update is available. Please accept to continue.”
o NOTE: No timer is available for data-centric devices
WARNING: Cannot make or receive phone calls, including 911 calls, during update.
o The warning is not applicable to data-centric devices.
Approximate update time in minutes.
A readable description of the firmware package shall be received in the download
descriptor. If the description does not fit on the display, the screen should be scrollable to allow viewing of the description.
NOTE: No update countdown is available for “Low” priority updates and user action is
required to proceed.
The options available on the display shall be:
Start the update, for example OK or Continue
Defer the update package, for example Defer
o If this is chosen, the update can be deferred for up to 5 days.
Reject the update package, for example Reject - available only when the firmware package priority is Low.
When 0 seconds is reached, the device shall advance as if it acknowledged the request.
Firmware Update
During the firmware update, the following shall be displayed:
“Updating Firmware from Verizon Wireless”
A numeric indication of percentage complete
NOTE: The status bar may not be displayed during the firmware update.
No options are available for the user on the display during the update process.
After the firmware update and just prior to the reset, the following shall be displayed: “Update Successful.”
Firmware Update Complete Notification
After the firmware update and reset, the following shall be displayed:
“Software Updated by Verizon Wireless”
A readable description of the firmware package as received in the download descriptor. If
the description does not fit on the display, the screen shall be scrollable to allow viewing of the description.
The options available on the display shall be:
Acknowledge that the update is completed, for example OK/Continue/END key press.
The device shall return to idle mode.
3.2.1.2U SER I NITIATED
The following display requirements must be met.
A Software Update feature is offered in the menu (Device or connection manager) which will give user one or two options:
Check Status or a similar message
Install Deferred Software (if deferred software update is pending) or a similar message ?Check New (if NO deferred software update is pending) or a similar message
3.2.1.2.1 3.2.1.2.2 3.2.1.2.3Check Status
The following will be displayed:
“Source:” label followed by “Verizon Wireless”
“Name:” label followed by ABC Name where “ABC Name” is an example and shall be replaced with the actual software update name.
“Status:” label and Status Message. Refer to the “Status Messages” specifications defined in the OMA FUMO v1.0, Section 6.2 Use of Generic Alert for Notifications.
“Date:” label & Date value where Date value = date when the Download/Update is performed
“Time:” label & Time value where Time value= time when the Download/Update is performed
“Description:” label followed by Description where description will be the full software update description.
Install Deferred SW
The following will be displayed:
“Verizon Wireless Update Deferred to: time”.
A readable description of the firmware package as received in the download descriptor. If
the description does not fit on the display, the screen shall be scrollable to allow viewing of the description.
“Update now?” with the options of accept or reject.
If the user chooses to accept, the device initiates the software update sequence starting at the software update notification screen in section 3.2.1.1.3.
If the user chooses to reject, the device shall send a Generic alert message to the server as defined in section “User Reject” 4.2.1.4.1
Check New
If a software update is available, the device will initiate the software update sequence as described in section 3.1.1.2.3.
If a software update is not available, the device will display the following message: “No New Software Update Available.”
The option available on the display is to acknowledge the screen.
3.2.2S UBSCRIBER D EVICE M ANAGEMENT
During OMA DM sessions the server may issue User Interaction alerts in accordance with OMA DM version 1.2. Device shall be capable of receiving and displaying these alerts.
See Section 3.1.2.1.1. for user alerts during a DM session.
3.2.2.1P REDEFINED T EXTS
Devices shall be capable of displaying all predefined texts. Additionally, the device shall be capable of displaying all alphanumeric characters and the following punctuation marks. ! @ # * ( ) - + . , ? /.
4F IRMWARE S PECIFICATIONS
4.1C OMMON R EQUIREMENTS FOR OTADM
In order for devices to have compatibility with Verizon Wireless LTE 3GPP Band 13 network for
Device Management and support FOTA and SDM, the following OMA DM requirements must
be met.
4.1.1C OMPLIANCE WITH S TANDARD P ROTOCOLS
4.1.1.1OMA I NDUSTRY S TANDARD
?OMA DM (Device Management) V1.2
4.1.1.2O THER I NDUSTRY S TANDARDS
?WAP Push OTA Specification (for notification using SMS*)
?HTTP V1.1
?WAP-230-WSP Specification (Package 0 SMS* header detail)
?WAP-259-WDP Specification (Package 0 SMS* header detail)
* The device shall support the 3GPP2 SMS format as defined in 3GPP2 C.S0015-A v1.0 “Short Message Service (SMS) f or Wideband Spread Spectrum Systems”. The support for the 3GPP format, as
defined in TS 23.040 “Technical realization of the Short Message Service (SMS)” is highly
recom mended.
4.1.1.3S TANDARDS C OMPLIANCE
The device shall support the OMA-DM standard and the sections as outlined in the following documents:
Document Reference
Section OMA Device Management Bootstrap, Version 1.2. 5.1.2.1 Customized Bootstrap
5.1.2.2 Server-Initiated Bootstrap
OMA DM Device Description Framework DTD,
Version 1.2*.
N/A
OMA Device Management Notification Initiated Session, Version 1.2. 5Server Alerted Management Session
6Structure of General Notification Initiated Session Alert
7.1Package #0 delivered using WAP Push
OMA Device Management Protocol, Version 1.2. 6.2Multiple Messages In Package – Requirements
8.1.2Session Abort – Requirement
8.2Package 0: Management Initiation Alert from
server to client
8.3Package 1: Initialization from client to server
8.4Package 2: Initialization from server to client
8.5Package 3: Client response sent to server
8.6Package 4: Further server management