Getting Started¶
This is a brief introduction to the Clearwire Device Activation and Provisioning Platform.- Overview
- Requirement-Level Definitions
- Requirements
- Standards Compliance
- Device Activation and Provisioning Process
- Open Source Device Management Client
Overview¶
Activation is the process of establishing a subscriber account with the respective wireless service provider. Activation allows the device to be recognized on the carrier’s network. Provisioning is the process of configuring the wireless-capable end device so that it is physically and logically capable of authenticating on the carrier network. Provisioning enables the device to actually receive and send data and voice signals.
Since many different device types are enabled by Clearwire’s WiMAX technologies, a WiMAX service provider requires a dynamic over-the-air provisioning solution to activate and enable subscription for all these device types (with or without keyboard, UICC, etc.). Devices could include notebooks, ultra mobile PCs (UMPCs), handsets, and consumer electronics.
To provide a dynamic over-the-air provisioning solution, the Clearwire Device Platform uses a standards-based approach to activation and provisioning, integrating a series of standards that are derived from several industries and organizations (see below). For more information on an organization or a standard, click on a link in the following diagram.
 |
  |
   |
The purpose of this Web content is to provide device and network platform requirements that comply with the Open Mobile Alliance (OMA) and WiMAX Forum (WMF) standards to implement an activation and provisioning platform on the Clearwire WiMAX network. Furthermore, this content proposes an end-to-end solution for dynamic over-the-air provisioning suitable for various device types (with or without keyboard, UICC, etc.) based on requirements and use-case scenarios described in Device Platform Use Cases.
This content is intended to be used by device manufacturers (software and firmware oriented) and network provisioning component providers such as AAA, OMA-DM, and BSS who want to provide solutions that allow an end-to-end activation and provisioning user experience.
Use this content to familiarize yourself with the technical details of how to:
- Activate a device online and offline.
- Re-provision a device.
- Deactivate a device.
This content is an overarching solution that encompasses many elements in the network, including devices, and is meant to provide an overall framework. It is complementary to discrete product requirements documents.
Requirement-Level Definitions¶
The following requirement-level terms are used throughout this Web content:
- “MUST”, "REQUIRED" or "SHALL" indicate the definition is an absolute requirement of the specification.
- “MUST NOT” and "SHALL NOT" indicate the definition is an absolute prohibition of the specification.
- “SHOULD” indicates there may be valid reasons in specific circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
- “SHOULD NOT” indicates there may be valid reasons in specific circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
- “MAY” indicates an item is truly optional. Vendors may choose to include the item. An implementation that does not include a particular option MUST be prepared to inter-operate with another implementation that does include the option, though perhaps with reduced functionality. An implementation that does include a specific option MUST be prepared to inter-operate with another implementation that does not include the option (except for the feature the option provides.)
Requirements¶
Before you begin perusing the content on this site, it is highly recommended that you do the following:
- Become a member of WMF. For information on WMF membership, see Resources and Tools.
- Become a member of OMA. For information on OMA membership, see Resources and Tools.
After you become a member, you can access the WMF and OMA Standards pages, and start implementing an end-to-end provisioning solution to activate and enable subscription for your device type. For more information, see Device Platform Solution.
Standards Compliance¶
The Clearwire Device Activation and Provisioning Platform makes use of the following standards defined by WMF and OMA:
- NWG OTA Prov Spec General, Rel 1.5 Ver 1.0.2
- NWG OTA Prov Spec OMA-DM, Rel 1.5 Ver 1.0.2
- Enabler Release Definition for OMA Device Management
Note: You must be a member of WMF and OMA to access the NWG OTA General Provisioning Specification and the NWG OTA OMA-DM Provisioning Specification.
Device Activation and Provisioning Process¶
The following diagram shows a high-level overview of Clearwire’s device activation and provisioning process.
The device activation and provisioning process flow is described in the following table.
| Step | Description |
|---|---|
| 1 | Device finds and connects to Clearwire network. |
| 2 | Authentication with the AAA Server is performed; no device record is found. |
| 3 | Device acquires IP address. |
| 4 | DPI hotlines unknown device to Activation Portal. |
| 5 | Optionally, device requests Provisioning Server location. |
| 6 | AAA notifies OMA-DM Server of new device network entry. |
| 7 | OMA-DM Server bootstraps device; device requests bootstrap. |
| 8 | OMA-DM Server discovers device information (manufacturer, model, device type, etc.). |
| 9 | Customer is redirected to Activation Portal. |
| 10 | Activation Portal queries device information from OMA-DM Server. |
| 11 | Customer selects offers that are filtered based on location and device type. |
| 12 | Portal submits order to BSS. |
| 13 | BSS provisions AAA. |
| 14 | Hotline is removed. |
| 15 | BSS provisions OMA-DM Server. |
| 16 | OMA-DM Server sends activation payload to device (authentication data, credentials, realm, etc.). |
| 17 | Device has open Internet access. |
For details of the device activation and provisioning process, see Device Platform Solution. For use-case scenarios, see Device Platform Use Cases.
Open Source Device Management Client¶
To support the activation and provisioning process Clearwire provides a client-side software element called the open source device management client. The developer can use the OMA client as a building block in the activation and provisioning process.
The open source device management client supports both WiMAX Initiated Bootstrap and OMA-DM bootstrap which enables the developer to receive DM Account updates and start a conversation with the OMA DM Servers in the Clearwire network. The device management client can then receive operator network profile updates (CAPL, Channel Plan, RAPL) from the OMA Server which enables the devices to scan for specific network frequencies of the preferred networks. Finally the device management client can be used to download firmware updates for the device.
On a high-level the device management client is responsible for the following activities:- OMA Tree exchanges between the device using Device Management Tree XML
- WiMAX initiated Bootstrap (WIB), and OMA-DM Bootstrap in concert with the OMA DM Server
- Provisioning, Firmware, and device configuration updates between client and the OMA DM Server.
- Collection of device diagnostics information for the Diagnostics Server.
The open source device management client requirements are based on OMA DM and WiMAX Forum standards. In the following weeks Clearwire will add more detailed technical information about the open source device management client.
Next Topics
