Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Bootstrapping To Return the Device Hardware ID

Windows Mobile 6.5
4/8/2010

The OMA DM server can now be bootstrapped to provide the device hardware ID to the OMA DM server, which is the IMEI for a GSM device or the ESN for a CDMA device. You can use the Microsoft custom parameter, USEHWDEVID, in the bootstrap XML to specify whether the hardware device ID is returned or a GUID. By default, an application-specific GUID is used. It is in the format of: urn:uuid:xxxx. You can use the USEHWDEVID parameter in the w7 APPLICATION Configuration Service Provider to specify that the hardware device ID is returned instead.

The following list shows the values:

  • If the USEHWDEVID node is present in the bootstrap XML, the DevID value returns IMEI for a GSM device (IMEI:xxxx), ESN for a CDMA device (ESN:xxxx), or a GUID for non radio device.
  • If the UseHwDevID node is not present in the bootstrap XML. the the DevID value returns a GUID.

Only those with Manager or Operator TPS roles can change the USEHWDEVID parameter. Parent node roles for security permissions do not apply to this node.

For more information about USEHWDEVID, see the following topics:

The following scenario shows how the Device ID would work. In this scenario, the Mobile Operator has set up an OMA DM server to remotely manage devices, and the server is linked Operator's Help desk system to provide more powerful help desk solutions

  1. The DM server starts the DM session.
  2. The first message that the server receives from the device contains the device ID.
  3. The server uses the device ID to obtain additional device profile information within the Operator's Help desk database, which allows the server to resolve the user's concern rather than contacting the Help desk.
  4. An untrusted application tries to get the IMEI from the device over an OMA DM channel. The request is rejected due to lack of proper access permission.

The following example shows how you would set the USEHWDEVID parameter in the w7 APPLICATION Configuration Service Provider to specify that the IMEI is used as the device ID for a GSM device (IMEI:xxxx), and ESN is used for a CDMA device (ESN:xxxx), and a GUID for a non-radio device.

<wap-provisioningdoc version="1.1">
   <characteristic type="APPLICATION">
      <parm name="APPID" value="w7"/>
      <parm name="USEHWDEVID"/>
      <! — other parms -- >
      <! — other characteristic -- >
   </characteristic> 
</wap-provisioningdoc>

When the USEHWDEVID parameter is in the w7 APPLICATION Configuration Service Provider, the DevInfo Configuration Service Provider returns the device hardware ID to the OMA DM server at the beginning of each OMA DM session. The device hardware ID is the DevID in the SyncBody and the Source LocURI in the SyncHdr.

The following example shows how the DM server can query a device for the hardware device ID.

<Get>
   <CmdID>2</CmdID>
   <Item>
      <Target>
         <LocURI>./DevInfo/DevId</LocURI>
      </Target>
   </Item>
</Get>

Community Additions

Show:
© 2015 Microsoft