Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The Bootstrap process is used to provision an unconfigured
Windows Mobile device to provide access to generic proxies and
enable continuous provisioning. For more detailed information about
Provisioning Bootstrap, see the Open Mobile Alliance (OMA)
Provisioning Bootstrap Specification Version 1.1,
OMA-WAP-ProvBoot-v1_1-20050428-C available at this
The following table shows the functionality that provisioning bootstrap provides.
Functionality | Description | ||
---|---|---|---|
ProvBoot-BPC-C-002 GSM SMS Bearer Channel is Supported |
The GSM SMS bearer data channel is supported in some form. For example: SMS point to point text. |
||
ProvBoot-B-C-001 Bootstrap Document (WAP provisioning document) Can Be Sent Over the Air by an Unconfirmed Push |
A Bootstrap document can be sent to a device over the air with a WAP connectionless unsecure push as described in "OTA Mechanism" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). The device can receive the provisioning document over the air by using Short Message Service (SMS). |
||
ProvBoot-B-C-003 A WAP-PROVISIONINGDOC May Be Received Over The Air Using a Point to Point Mechanism |
A WAP-PROVISIONINGDOC may be received over the air using a point to point communications mechanism as described in "The Bootstrap Process" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). |
||
ProvBoot-B-C-005 The Preconfigured Bootstrap Document (WAP provisioning document) Can Be Read from the Device |
A Bootstrap document can be read from Windows Mobile devices only during the cold boot procedure. |
||
ProvBoot-B-C-006 Security for the Bootstrap Document (WAP provisioning document) |
Security for an OTA Bootstrap document is implemented as described in "The Generic Security Mechanism" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). |
||
ProvBoot-B-C-008 The PROVURL Parameter is Unique Within the Device |
The configuration context, which is defined by the required PROVURL parameter, is unique to Windows Mobile devices and is implemented as described in "Bootstrap of Configuration Context" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). Windows Mobile devices support only one PROVURL. |
||
ProvBoot-B-C-009 Windows Mobile Devices Accept Multiple bootstraps without PROVURL definitions |
Multiple bootstraps without a PROVURL definitions are supported as described in "Bootstrap of Configuration Context" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). Each bootstrap must be for a different configuration.
|
||
ProvBoot-BCT-C-001 Support for GSM |
Global System for Mobile Communications (GSM) is supported as described in "Adaptation to GSM" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). |
||
ProvBoot-BCT-C-004 The Over the Air Mechanism |
The OTA mechanism is implemented as described in "The Generic Security Mechanism" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). |
||
ProvBoot-BGSM-C-004 Bootstrap Document (WAP provisioning document) Can Be Received Over SMS Bearer Channel |
A Bootstrap document can be received over the Short Message Service (SMS) bearer channel as described in "SMS" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). |
||
ProvBoot-BGSM-C-006 The Bootstrap Document is Validated Using the Generic Security Mechanism |
A Bootstrap document is validated using the generic security mechanism as described in "User Agent Behaviour" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). |
||
ProvBoot-BGSM-C-007 Only Bootstrap Document That Are Authenticated are Processed |
A Bootstrap document must be authenticated before it is processed as described in "User Agent Behaviour" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). |
||
ProvBoot-BGSM-C-013 IMSI-based Network-specific Shared Secret |
While using GSM in certain cases, the network-specific shared secret is implemented for security reasons, as described in "Adaptation to GSM" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C). |
||
ProvBoot-BSF-C-001 NETWPIN-Based Shared Secret |
NETWPIN is implemented as the basis of the shared secret as described in "The Generic Security Mechanism" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C).
|
||
ProvBoot-BSF-C-002 USERPIN-Based Shared Secret |
USERPIN is implemented as the basis of the shared secret as described in "The Generic Security Mechanism" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C).
|
||
ProvBoot-BSF-C-003 USERNETWPIN-based Shared Secret |
USERNETWPIN is implemented as the basis of the shared secret as described in "The Generic Security Mechanism" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C).
|
||
ProvBoot-BSF-C-004 USERPINMAC-based Shared Secret |
USERPINMAC is implemented as the basis of the shared secret as described in "The Generic Security Mechanism" in the OMA Provisioning Bootstrap Specification Version 1.1 (OMA-WAP-ProvBoot-v1_1-20050428-C).
|