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. |
This Configuration Service Provider handles the OMA DM DevDetail management object that contains device-specific parameters. These parameters are not sent from the client to the server automatically. They cannot be manipulated, but can be queried by servers using OMA DM commands.
Note: |
---|
Access to this Configuration Service Provider is determined by security roles. Because OEMs and mobile operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. For more information about roles, see Security Rolesand Default Roles for Configuration Service Providers. |
The following image shows the management object used by OMA DM.
- DevDetail
-
The root node of the DevDetail object. The DevDetail node provides the following versions:
- The OEM driver ROM package (os major number.os minor number.
OEM driver ROM package build number. OEM driver ROM Package QFE
number)
- The Radio stack version
The OEM driver ROM package version is listed first, followed by the radio stack version. The two versions are separated by a semicolon (;).
The following table shows the default settings. The default security role maps to each subnode unless specific permission is granted to the subnode.
Format
Node
Roles allowed to query and update setting
Operator
Operator TPS
Manager
Access Type
Get
Occurs
One
Scope
Permanent
- The OEM driver ROM package (os major number.os minor number.
OEM driver ROM package build number. OEM driver ROM Package QFE
number)
- DevDetail/URI
-
Universal Resource Identifier (URI). The following parameters are supported:
-
MaxDepth- Specifies the maximum depth of the management tree
that the device supports. This is the maximum number of URI
segments that the device supports. The default value zero (0)
indicates that the device supports a URI of unlimited depth.
-
MaxTotLen- Specifies the maximum total length of any URI
used to address a node or node property. This is the largest number
of characters in the URI that the device supports. The default
value zero (0) indicates that the device supports a URI of
unlimited length.
-
MaxSegLen- Specifies the total length of any URI segment in
a URI that addresses a node or node property. This is the largest
number of characters that the device can support in a single URI
segment. The default value zero (0) indicates that the device
supports URI segment of unlimited length.
The following table shows the default settings.
Format
Node
Access Type
Get
Occurs
One
Scope
Permanent
-
MaxDepth- Specifies the maximum depth of the management tree
that the device supports. This is the maximum number of URI
segments that the device supports. The default value zero (0)
indicates that the device supports a URI of unlimited depth.
- DevDetail/DevTyp
-
Indicates the device type, as defined in the specification OMA-TS-DM Standard Objects (OMA-TS-DM_StdObj-V1_2-20070209-A) available at this
OMA Web site . Examples of the device type are Windows Mobile Standard, Windows Mobile Classic, or Windows Mobile Professional.The following table shows the default settings.
Format
chr
Access Type
Get
Occurs
One
Scope
Permanent
- DevDetail/OEM
-
Indicates the Original Equipment Manufacturer (OEM), as defined in the specification OMA DM Standardized Objects (OMA-TS-DM_StdObj-V1_2-20070209-A) available at this
OMA Web site .The following table shows the default settings.
Format
chr
Access Type
Get
Occurs
One
Scope
Permanent
- DevDetail/FwV
-
Indicates the firmware version, as defined in the specification OMA DM Standardized Objects (OMA-TS-DM_StdObj-V1_2-20070209-A) available at this
OMA Web site .Microsoft provides both the OEM driver ROM package version and the radio stack version. The OEM driver ROM package version is listed first, followed by the radio stack version. The two versions are separated by a semicolon (;).
The following table shows the default settings.
Format
chr
Access Type
Get
Occurs
One
Scope
Permanent
- DevDetail/SwV
-
Indicates the software version, as defined in the specification OMA DM Standardized Objects (OMA-TS-DM_StdObj-V1_2-20070209-A) available at this
OMA Web site .This node value is in the format: OS major number.OS minor number.Build number.QFE number.
The following table shows the default settings.
Format
chr
Access Type
Get
Occurs
One
Scope
Permanent
- DevDetail/HwV
-
Indicates the hardware version, as defined in the specificationOMA DM Standardized Objects (OMA-TS-DM_StdObj-V1_2-20070209-A) available at this
OMA Web site .The following table shows the default settings.
Format
chr
Access Type
Get
Occurs
One
Scope
Permanent
- DevDetail/LrgObj
-
Indicates whether the device uses OMA DM Large Object Handling, as defined in the specification OMA DM Standardized Objects (OMA-TS-DM_StdObj-V1_2-20070209-A) available at this
OMA Web site .Because Windows Mobile does not support OMA DM large object handling, a query on this node returns false.
The following table shows the default settings.
Format
boolean
Access Type
Get
Occurs
One
Scope
Permanent
Remarks
The combination of HwV, SwV, FwV, Man, Mod, and OEM should provide a unique signature that identifies the specific version of software. This allows other implementations to make special provisions based on that identification.