DevDetail Configuration Service Provider

  • Article

Send Feedback

This configuration service provider handles the OMA Device Management 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 Roles and 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

  • 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. A value of zero (0) indicates that the device supports a URI of unlimited depth. The default value is zero (0).
    • 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. A value of zero (0) indicates that the device supports a URI of unlimited length. The default value is zero (0).
    • 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. A value of zero (0) indicates that the device supports URI segment of unlimited length. The default value is zero (0).

    The following table shows the default settings.

    Format Node
    Access Type Get
    Occurs One
    Scope Permanent

  • DevDetail/DevTyp
    Indicates the device type, as defined in the specification SyncML Device Information, version 1.1.2 (OMA-SyncML-DevInfo-V1_1_2). This document is available at this OMA website. Examples of the device type are Smartphone, Pocket PC, or Pocket PC Phone Edition.

    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 SyncML Device Information, version 1.1.2 (OMA-SyncML-DevInfo-V1_1_2). This document is available at this OMA website.

    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 SyncML Device Information, version 1.1.2 (OMA-SyncML-DevInfo-V1_1_2). This document is available at this OMA website.

    Microsoft provides both version of the OEM driver ROM package and the Radio stack version, separated by ";". The first is OEM driver ROM package version, the second is radio stack version.

    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 SyncML Device Information, version 1.1.2 (OMA-SyncML-DevInfo-V1_1_2). This document is available at this OMA website.

    This node value is in the format: OS major number.OS minor number.Windows Mobile Version 5.0 Build number.Windows Mobile Version 5.0 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 specification SyncML Device Information, version 1.1.2 (OMA-SyncML-DevInfo-V1_1_2). This document is available at this OMA website.

    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 SyncML Device Management Protocol, version 1.1.2 (OMA-SyncML-DMProtocol-V1_1_2). This document is available at this OMA website.

    Because Windows Mobile version 5.0 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.

See Also

Configuration Service Provider Reference for Windows Mobile-Based Devices | DevDetail DDF File | DevDetail Configuration Service Provider Examples for OMA DM

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.