DG Device Mgmnt - Sony Mobile guidelines | OMA Client Provisioning and Device Management 2 August 2008 This document is published by Sony Ericsson Mobile Communications AB, without

Developers guidelines

August 2008

OMA Client Provisioning and Device Managementfor Sony Ericsson UIQ 3 phones

Developers guidelines | OMA Client Provisioning and Device Management

Preface

Purpose of this document

qÜáë=ÇçÅìãÉåí=ÇÉëÅêáÄÉë=íÜÉ=áãéäÉãÉåí~íáçå=çÑ=lj^=`äáÉåí=mêçîáëáçåáåÖ=~åÇ=lj^=aÉîáÅÉ=j~å~ÖÉãÉåí=ÑìåÅíáçå~äáíáÉë=áå=pçåó bêáÅëëçå=póãÄá~å=V=L=rfn=P=ãçÄáäÉ=éÜçåÉëK

mÉçéäÉ=ïÜç=Å~å=ÄÉåÉÑáí=Ñêçã=íÜáë=ÇçÅìãÉåí=~êÉW

√ pçÑíï~êÉ=ÇÉîÉäçéÉêë√ léÉê~íçêë=~åÇ=ëÉêîáÅÉ=éêçîáÇÉêë

√ `çåíÉåí=éêçîáÇÉêë

fí=áë=~ëëìãÉÇ=íÜ~í=íÜÉ=êÉ~ÇÉê=Ü~ë=Ä~ëáÅ=ìåÇÉêëí~åÇáåÖ=çÑ=íÜÉ=lj^=`äáÉåí=mêçîáëáçåáåÖ=~åÇ=aÉîáÅÉ=j~åJ~ÖÉãÉåí=íÉÅÜåçäçÖáÉë=~åÇ=ëí~åÇ~êÇëK

2 August 2008

This document is published by Sony Ericsson Mobile Communications AB, without any warranty*. Improvements and changes to this text necessitated by typographical errors, inaccuracies of current information or improvements to programs and/or equipment, may be made by Sony Ericsson Mobile Communications AB at any time and without notice. Such changes will, however, be incorporated into new editions of this document. Printed versions are to be regarded as temporary reference copies only.

*All implied warranties, including without limitation the implied warranties of merchantability or fitness for a particular purpose, are excluded. In no event shall Sony Ericsson or its licensors be liable for incidental or consequential damages of any nature, including but not limited to lost profits or commercial loss, arising out of the use of the information in this document.

These Developers guidelines are published by:

Sony Ericsson Mobile Communications AB, SE-221 88 Lund, Sweden

Phone: +46 46 19 40 00Fax: +46 46 19 41 00www.sonyericsson.com/

© Sony Ericsson Mobile Communications AB, 2006. All rights reserved. You are hereby granted a license to download and/or print a copy of this document.Any rights not expressly granted herein are reserved.

Second edition (August 2008)Publication number: EN/LZT 108 8156 R2A


Sony Ericsson Developer World

On www.sonyericsson.com/developer, developers will find documentation and tools such as phone White papers, Developers guidelines for different technologies, SDKs (Software Development Kits) and relevant APIs (Application Programming Interfaces). The Web site also contains discussion forums monitored by the Sony Ericsson Developer Support team, an extensive Knowledge base, Tips and tricks, example code and news.

Sony Ericsson also offers technical support services to professional developers. For more information about these professional services, visit the Sony Ericsson Developer World Web site.

Document conventions

Products

Sony Ericsson mobile phones are referred to in this document using generic names as follows:

Terminology and abbreviations

dÉåÉêáÅ=å~ãÉëpÉêáÉë

pçåó=bêáÅëëçå=ãçÄáäÉ=éÜçåÉë

mVVM mVVMáI=mVVMÅ

jSMM jSMMáI=jSMMÅ

tVRM tVRMáI=tVRMÅ

tVRU tVRUÅ

mN mNáI=mNÅ

tVSM tVSMá

dVMM dVMMáI=dVMMÅ

dTMM dTMMáI=dTMMÅI=dTMM=_ìëáåÉëë=bÇáíáçå=

^mk ^ÅÅÉëë=mçáåí=å~ãÉ

`m `äáÉåí=mêçîáëáçåáåÖK=qÜáë=áë=íÜÉ=éêçÅÉëë=Äó=ïÜáÅÜ=~=t^m=ÅäáÉåí=áë=áåáíá~ääó=ÅçåÑáÖìêÉÇ=ïáíÜ=ÅçååÉÅíáîáíó=~åÇ=~ééäáÅ~íáçå=~ÅÅÉëë=é~ê~ãÉíÉêëK=qÜáë=áë=~=åçåJáåíÉê~ÅíáîÉ=éêçÅÉëë=~ë=çééçëÉÇ=íç=aÉîáÅÉ=j~å~ÖÉãÉåíK

3 August 2008

www.sonyericsson.com/developer


Typographical conventions

`çÇÉ=áë=ïêáííÉå=áå=`çìêáÉê=ÑçåíW=<characteristic>...</characteristic>

`pa `áêÅìáí=pïáíÅÜÉÇ=a~í~

aac aÉîáÅÉ=aÉëÅêáéíáçå=cê~ãÉïçêâK=få=ëÜçêí=íÜáë=Ñê~ãÉïçêâ=éêÉëÅêáÄÉë=~=ï~ó=Ñçê=ÇÉîáÅÉ=îÉåJÇçêë=íç=ÇÉëÅêáÄÉ=íÜÉáê=ÇÉîáÅÉë=ëç=íÜ~í=~=ã~å~ÖÉãÉåí=ëóëíÉã=Å~å=ìåÇÉêëí~åÇ=Üçï=íç=ã~å~ÖÉ=íÜÉ=ÇÉîáÅÉK=

aj aÉîáÅÉ=j~å~ÖÉãÉåíK=^=ëÉí=çÑ=lj^=ëí~åÇ~êÇ=ãÉÅÜ~åáëãë=íÜ~í=Éå~ÄäÉë=êÉãçíÉ=áåíÉê~ÅJíáîÉ=ÅçåÑáÖìê~íáçå=çÑI=Ñçê=Éñ~ãéäÉI=~=éÜçåÉK=

dmop dÉåÉê~ä=m~ÅâÉí=o~Çáç=pÉêîáÅÉ

dpj däçÄ~ä=póëíÉã=Ñçê=jçÄáäÉ=ÅçããìåáÅ~íáçåë

fjmp fåëí~åí=jÉëë~ÖáåÖ=~åÇ=mêÉëÉåÅÉ=pÉêîáÅÉ=Elj^F

j^` jÉëë~ÖÉ=^ìíÜÉåíáÅ~íáçå=`çÇÉ

j`` jçÄáäÉ=`çìåíêó=`çÇÉ

jl j~å~ÖÉãÉåí=lÄàÉÅíK=j~å~ÖÉãÉåí=çÄàÉÅíë=~êÉ=íÜÉ=ÉåíáíáÉë=íÜ~í=Å~å=ÄÉ=ã~åáéìä~íÉÇ=Äó=ã~å~ÖÉãÉåí=~Åíáçåë=Å~êêáÉÇ=çîÉê=íÜÉ=póåÅji=aj=éêçíçÅçäK

lj^ léÉå=jçÄáäÉ=^ääá~åÅÉK=qÜÉ=éêáã~êó=ëí~åÇ~êÇáò~íáçå=çêÖ~åáò~íáçå=Ñçê=ãçÄáäÉ=~ééäáÅ~íáçåëK=pÉÉ=ÜííéWLLïïïKçéÉåãçÄáäÉ~ääá~åÅÉKçêÖ=

lq̂ lîÉê=qÜÉ=^áê

mpa m~ÅâÉí=pïáíÅÜÉÇ=a~í~

pfj pìÄëÅêáÄÉê=fÇÉåíáíó=jçÇìäÉKfå=íÜÉ=êÉëí=çÑ=íÜÉ=ÇçÅìãÉåí=íÜÉ=íÉêã=pfj=áë=ìëÉÇ=íç=ÇÉåçíÉ=íÜÉ=íê~Çáíáçå~ä=dpj=pfj=~ë=ïÉää=~ë=íÜÉ=rpfj=~åÇ=rf``K

pjp pÜçêí=jÉëë~ÖÉ=pÉêîáÅÉ

pjpJ` pÜçêí=jÉëë~ÖÉ=pÉêîáÅÉ=`ÉåíêÉ

qip qê~åëéçêí=i~óÉê=pÉÅìêáíó

qmp qêìëíÉÇ=mêçîáëáçåáåÖ=pÉêîÉê

rf`` rpfj=fåíÉÖê~íÉÇ=`áêÅìáí=`~êÇ

rjqp råáîÉêë~ä=jçÄáäÉ=qÉäÉÅçããìåáÅ~íáçåë=póëíÉã

rpfj råáîÉêë~ä=pìÄëÅêáÄÉê=fÇÉåíáíó=jçÇìäÉ

t^m táêÉäÉëë=^ééäáÅ~íáçå=mêçíçÅçä

t_uji t^m=_áå~êó=bñíÉåÇÉÇ=j~êâìé=i~åÖì~ÖÉ=

tfj táêÉäÉëë=fÇÉåíáÑáÅ~íáçå=jçÇìäÉ

uji bñíÉåÇÉÇ=j~êâìé=i~åÖì~ÖÉ

4 August 2008

http://www.openmobilealliance.org/


píêáåÖ=î~äìÉë=~êÉ=ïêáííÉå=áåëáÇÉ=ÇçìÄäÉ=èìçíÉëW=“OffÒ

Trademarks and acknowledgements

Symbian, Symbian OS, UIQ Technologies, UIQ and other associated Symbian marks are all trademarks of Symbian Ltd.

The Bluetooth word mark and logos are owned by the Bluetooth SIG, Inc. and any use of such marks by Sony Ericsson is under license.

Memory Stick is a trademark of Sony Corporation.

Other product and company names mentioned herein may be the trademarks of their respective owners.

Document history

Change history

OMMSJMTJMR sÉêëáçå=oN^ cáêëí=ÉÇáíáçå=éìÄäáëÜÉÇ=çå=aÉîÉäçéÉê=tçêäÇK=

OMMSJMVJNQ sÉêëáçå=oN_ jáåçê=êÉîáëáçå=~åÇ=åÉï=ÇçÅìãÉåí=ä~óçìíK

OMMSJNMJMQ sÉêëáçå=oO^ ^ÇÇÉÇ=tVRU=ëÉêáÉë

OMMUJMUJOU sÉêëáçå=oO_ ^ÇÇÉÇ=P1, W960, G900, G700 series and minor revision.

5 August 2008


6 August 2008

Contents

OMA Client Provisioning ............................................................................................7Introduction ...............................................................................................................8

Supported standards .............................................................................................8Document reception OTA ..........................................................................................9Security mechanisms ................................................................................................9Parameters and compliance .....................................................................................9

PXLOGICAL ...........................................................................................................9NAPDEF ...............................................................................................................14BOOTSTRAP .......................................................................................................16

Application specific settings ...................................................................................16Browser - APPID “w2” .........................................................................................18MMS - APPID “w4” ..............................................................................................20OMA Data Synchronization - “w5” ......................................................................21OMA Device Management - “w7” .......................................................................23Email, SMTP - “25” ..............................................................................................26Email, POP3 - “110” ............................................................................................28Email, IMAP4 - “143” ...........................................................................................29

OMA Device Management .......................................................................................31Introduction .............................................................................................................32

Supported standards and protocols ...................................................................33Preconditions .......................................................................................................33

DM sessions ............................................................................................................33General use case .................................................................................................34

Versioning ................................................................................................................34Authentication .........................................................................................................35Management Objects ..............................................................................................37

The basic tree structure .......................................................................................37Logical Branding Element subtree ./UIQ/LBE .....................................................37Externally Defined Command subtree ./UIQ/EDC ...............................................42Remote Lock & Wipe subtree ./SecureDevice ....................................................47WLan accesspoint settings ./WlanNAP ...............................................................48Group account settings ./SNAP ..........................................................................55Browser settings ./Browser .................................................................................58Proxy settings ./Proxy .........................................................................................62SyncML DM accounts ./SyncML/DMAcc ............................................................66OMA Data Sync accounts ./SyncML/DSAcc .......................................................69Network settings ./NAP .......................................................................................75Email management object ./Email .......................................................................83SMS settings ./SMS ..........................................................................................104MMS settings ./MMS .........................................................................................111Device information subtree ./DevInfo ................................................................117Detailed device information ./DevDetail ............................................................118Application lifecycle management ./Software ...................................................121


OMA Client Provisioning

OMA Client Provisioning v1.1 (WAP OMA Provisioning), is a backward compatible extension of the client provisioning functionality included in WAP 2.0 (v1.0). The new version adds support for application access provisioning as well as direct access and WAP proxy support.

7 August 2008


Introduction

With OMA Client Provisioning v1.1 it is possible, for example for an operator or service provider to config-ure (bootstrap) the terminal with settings for different applications in mobile phones (Browser, Email, Streaming, SyncML, Device Management, Wireless Village, and so on). The bootstrap process is initiated when an unconfigured mobile phone is started from its initial state or after a Master reset.

The bootstrap process normally includes configuration parameters for WAP services including the identifi-cation parameters for the Trusted Provisioning Server (TPS). This server includes a Provisioning Manager, controlling the continuous provisioning.

The Sony Ericsson implementation supports bootstrap over-the-air (OTA) via SMS.

The basis of Client Provisioning is the Provisioning Document (ProvDoc). This is a WBXML encoded mes-sage containing a list of characteristics specifying the settings to be provisioned. A ProvDoc can be 'pushed' to a device using a WAP Push message. This will normally be done by an Operator or Service Provider to configure a device owned by one of their users.

For details on the OMA Client Provisioning v1.1 standard, please refer to the documentation found at http://www.openmobilealliance.org/

Supported standards

The provisioning documents are delivered as WAP binary XML documents (WBXML) using the UTF-8 [RFC2279] character encoding set. These documents are delivered over the air using a bootstrap proto-col, refer to Provisioning Bootstrap 1.1, Open Mobile Alliance, OMA-WAP-PROVBOOT-V1_1, http://www.openmobilealliance.org/

The details of the bootstrap protocol, specially the security mechanism, depend on the technology, but the basic mechanism, uses connectionless WAP Push, refer to WAP Push OTA Specification” WAP Forum, WAP-235-PushOTA, http://www.openmobilealliance.org/. The specification also define mandatory security mechanism that can be used with all networks technologies.

There are mandatory rules for how the security mechanisms are to be used and how the provisioning doc-uments delivered through different channels must be combined. There are also mandatory rules for how to implement conflict resolution, error handling, proxy selection and parameter prioritization when inter-preting the received provisioning documents. The provisioning information received by a WAP client is expected to be stored in configuration context. These aspects are covered in Provisioning User Agent Behaviour 1.1", Open Mobile Alliance, OMA-WAP-PROVUABV1_1, http://www.openmobilealliance.org/.

Note: The Symbian client does not support multiple configuration contexts.

Note: The client provisioning settings always add to, rather than replace the existing settings. The excep-tion is for MMS settings, where the user is prompted as to whether they want their MMS settings to be replaced or not. This is because only one MMS account is supported on Symbian devices.

8 August 2008







Document reception OTA

Provisioning documents can only be made available to the Symbian mobile device using the OTA method.

One or several SMS are sent with destination port 2948 (non-secure WAP Push). These SMS are re-assemblied, parsed and handled by the provisioning user agent in the handset. The user is prompted whether to install the received provisioning settings or not. If the user accepts, the phone is configured with the new settings.

The settings will also be stored in the unified inbox and the user will have a later opportunity to apply them.

Refer to WAP Push OTA Specification” WAP Forum, WAP-235-PushOTA, http://www.openmobilealli-ance.org/. This specification also define mandatory security mechanism that can be used with all network technologies.

Security mechanisms

To avoid that non authorized people send malicious content to users, four different alternative security features are implemented: UserPin, UserPinMac, NetwPin, and UserNetwPin. Refer to Provisioning Boot-strap 1.1, Open Mobile Alliance, OMA-WAP-PROVBOOT-V1_1, http://www.openmobilealliance.org/.

The security features NetwPin and UserNetwPin are bound to the IMSI of the SIM card, so they should only work for the SIM they are created for.

In cases where the security mechanism requires the user to enter the PIN code, the user is allowed three attempts to enter the code correctly, after which the document will be rejected.

Parameters and compliance

PXLOGICAL

PXLOGICAL is mapped to the http proxy associated with a given internet account, allowing the phone to connect to the Internet (Web and WAP), and specifying MMS settings.

9 August 2008





The table below lists supported parameters in reference to OMA-WAP-ProvCont-v1_1-20050428-C.pdf, chapter 4.2 Overview of Data Model.

Parameter Description

Characteristic : PXLOGICAL

USED Mapped to the proxy associated with a given internet account.

PROXY-ID USED Internal reference within the document used to refer to a cer-tain PXLOGICAL.

PROXY-PW NOT USED

PPGAUTH-TYPE NOT USED

PROXY-PROVIDER-ID NOT USED

NAME NOT USED

DOMAIN NOT USED

TRUST NOT USED

MASTER NOT USED

STARTPAGE NOT USED

BASAUTH-ID NOT USED

BASAUTH-PW NOT USED

WSP-VERSION NOT USED

PUSHENABLED NOT USED

PULLENABLED NOT USED

PXLOGICAL : PXAUTHINFO

USED

PXAUTH-TYPE NOT USED Only HTTP-BASIC supported, and therefore assumed value.

PXAUTH-ID NOT USED Authentication is at the NAPDEF / Internet account level and not in the proxy, as reflected in the UI for internet accounts.

PXAUTH-PW NOT USED

PXLOGICAL : PORT NOT USED PORT must be associated with the PXPHYSICAL.

PORTNBR USED 4035 for http, 4036 for https.Note: PORT must be associated with the PXPHYSICAL not the PXLOGICALWAP not valid for Symbian devices.

SERVICE USED Parameter used to distinguish WAP from HTTP proxies. Since only HTTP proxies are supported on Sony Ericsson Symbian devices this parameter, if used, should be set to OTA-HTTP-TO, OTA-HTTP-TLS-TO, OTA-HTTP-PO or OTA-HTTP-TLS-PO. These values all have the same meaning (http proxy). Note if neither PORTNBR nor SERVICE is set then a HTTP Proxy will be created by default.

10 August 2008


Defining settings for more than one Internet account.The client provisioning software solution in Sony Ericsson UIQ 3 phones does not support more than one physical proxy within one logical proxy.

Therefore, one PXLOGICAL and included PXPHYSICAL is needed for each Internet account to define in a phone. The following example sets up two separate Internet accounts via two separate logical proxies set-tings:

<wap-provisioningdoc version="1.0">

<characteristic type="PXLOGICAL"> <parm name="PROXY-ID" value="www.wap1.operator.com"/> <parm name="NAME" value="Gateway WAP 1"/> <characteristic type="PXPHYSICAL">

PXLOGICAL : PXPHYSI-CAL

PHYSICAL-PROXY-ID NOT USED An APPLICATION can use this parameter. Use PROXY-ID on the PXLOGICAL instead, or NAP-ID on the NAPDEF

DOMAIN NOT USED

PXADDR USED GW address if WAP profile (not supported). PX address if Inter-net profile. If no PXADDR nor PXADDR-FQDN is given then "use proxy server" is disabled for the internet account

PXADDRTYPE NOT USED

PXADDR-FQDN USED Has the same meaning as PXADDR but has precedence over PXADDR.

WSP-VERSION NOT USED

PUSHENABLED NOT USED

PULLENABLED NOT USED

TO-NAPID USED Specifies the internet account associated with the proxy. Must be supplied.

PXPHYSICAL : PORT PORT must be associated with the PXPHYSICAL not the PXLOGICAL. Only one port per proxy is supported.

PORTNBR USED 4035 for http, 4036 for https.Note: PORT must be associated with the PXPHYSICAL not the PXLOGICALWAP not valid for Symbian devices.

SERVICE USED Parameter used to distinguish WAP from HTTP proxies. Since only HTTP proxies are supported on Sony Ericsson Symbian devices this parameter, if used, should be set to OTA-HTTP-TO, OTA-HTTP-TLS-TO, OTA-HTTP-PO or OTA-HTTP-TLS-PO. These values all have the same meaning (http proxy). Note if neither PORTNBR nor SERVICE is set, then a HTTP Proxy will be created by default.


11 August 2008


<parm name="PHYSICAL-PROXY-ID" value="PROXY_WAP_1"/> <parm name="PXADDR" value="10.138.255.129"/> <parm name="PXADDRTYPE" value="IPV4"/> <parm name="TO-NAPID" value="WAP_GPRS_1"/> <characteristic type="PORT"> <parm name="PORTNBR" value="8080"/> </characteristic> </characteristic> </characteristic> <characteristic type="PXLOGICAL"> <parm name="PROXY-ID" value="www.wap2.operator.com"/> <parm name="NAME" value="Gateway WAP 2"/> <characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="PROXY_WAP_2"/> <parm name="PXADDR" value="192.168.80.20"/> <parm name="PXADDRTYPE" value="IPV4"/> <parm name="TO-NAPID" value="WAP_GPRS_2"/>

<characteristic type="PORT"> <parm name="PORTNBR" value="8080"/> </characteristic> </characteristic> </characteristic>

<characteristic type="NAPDEF"> <parm name="NAPID" value="WAP_GPRS_1"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAME" value="operator GPRS 1"/> <parm name="NAP-ADDRESS" value="wap.operator.com"/> <parm name="NAP-ADDRTYPE" value="APN"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"/> <parm name="AUTHNAME" value="WAPOP"/> <parm name="AUTHSECRET" value="WAPOP"/> </characteristic> </characteristic>


</wap-provisioningdoc>

On the contrary, the following code attempts to use one logical proxy including two different physical proxies. This code will only setup the Internet account with settings for proxy 1. The second Internet account will not be valid.

12 August 2008


<wap-provisioningdoc version="1.0">

<characteristic type="PXLOGICAL"> <parm name="PROXY-ID" value="www.operator.com"/> <parm name="NAME" value="Gateway WAP"/> <characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="PROXY_WAP_1"/> <parm name="PXADDR" value="10.138.255.129"/> <parm name="PXADDRTYPE" value="IPV4"/> <parm name="TO-NAPID" value="WAP_GPRS_1"/> <characteristic type="PORT"> <parm name="PORTNBR" value="8080"/> </characteristic> </characteristic>

<characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="PROXY_WAP_2"/> <parm name="PXADDR" value="192.168.80.20"/> <parm name="PXADDRTYPE" value="IPV4"/> <parm name="TO-NAPID" value="WAP_GPRS_2"/> </characteristic> </characteristic>




13 August 2008


NAPDEF

NAPDEF is mapped to the Sony Ericsson “Internet account”, allowing the mobile phone to connect to the Internet (Web and WAP), email, and so on. The Internet account specifies what bearer the phone will use for connection (GPRS or dial-up GSM).


Characteristic : NAPDEF Mapped to Sony Ericsson Internet account.

NAPID USED Link to this internet account from any other AC including proxy, plus specific ACs (MMS, email etc)

BEARER USED GSM-CSD and GSM-GPRS. For 3G-able terminals the GSM-CSD is mapped to 3G CS and GSM-GPRS is mapped to 3G PS.

NAME USED Will set the name for the corresponding Internet account.

INTERNET USED If set, the Internet account will be added to the default SNAP account (usually the Internet SNAP). If the TO-NAPID or TO-PROXY for any application requiring internet access is left empty, then the default behaviour for that application will be to use the default SNAP account, except in the case of MMS set-tings.

NAP-ADDRESS USED APN for GSM-GPRSCSD dial string for GSM-CSD

NAP-ADDRTYPE USED Only support APN and E164 (CSD dial string), therefore the assumed values. This parameter must be supplied, no appro-priate default is used.

DNS-ADDR USED Can be up to 2 DNS addresses (IPv4 or IPv6) for static IP con-figurations.

CALLTYPE NOT USED

LOCAL-ADDR USED Local IP address (for static IP addresses).

LOCAL-ADDRTYPE USED IPv4 or IPv6.

LINKSPEED USED Requires deep understanding of Symbian OS. CSD accounts only, impacts on the BearerSpeed value in the DialOutISP record associated with the IAP.

DNLINKSPEED NOT USED

LINGER USED Requires deep understanding of Symbian OS. Will create a new modem bearer record for the IAP based on a template, if a bearer with the given linger value does not already exist (other-wise that bearer is selected). The field affected is LAST_SOCKET_ACTIVITY_TIMEOUT.

DELIVERY-ERR-SDU NOT USED

DELIVERY-ORDER NOT USED

TRAFFIC-CLASS NOT USED

14 August 2008


MAX-SDU-SIZE NOT USED

MAX-BITRATE-UPLINK NOT USED

MAX-BITRATE-DNLINK NOT USED

RESIDUAL-BER NOT USED

SDU-ERROR-RATIO NOT USED

TRAFFIC-HANDL-PRIO NOT USED

TRANSFER-DELAY USED GPRS Only : Requires deep understanding of Symbian OS. Sets GPRS_MIN_DELAY for the OutgoingGPRS record

GUARANTEED-BITRATE-UPLINK

NOT USED

GUARANTEED-BITRATE-DNLINK

NOT USED

MAX-NUM-RETRY NOT USED

FIRST-RETRY-TIMEOUT NOT USED

REREG-THRESHOLD NOT USED

T-BIT NOT USED

NAPDEF : NAPAUTHINFO

AUTHTYPE USED Supported values are PAP and CHAP.

AUTHNAME USED Data/CSD Account User name.

AUTHSECRET USED Data/CSD Account Password

AUTH-ENTITY USED Supported values are AAA and HA

SPI NOT USED

NAPDEF : VALIDITY NOT USED

COUNTRY NOT USED

NETWORK NOT USED

SID NOT USED

SOC NOT USED

VALIDUNTIL NOT USED


15 August 2008


BOOTSTRAP

Note: The BOOTSTRAP characteristic has no real affect on Symbian devices, it is not rejected but it does not influence any settings.

When supported, the bootstrap process will be performed the first time a SIM is inserted in the mobile phone. A restart of the bootstrap process will also be done after a Master reset.

Application specific settings

Note: All applications might not be configurable for a specific handset.

The value of the parameter APPID in the APPLICATION element identifies which application settings are to be applied. For more information about the different tags see the respective application compliance.

The following applications references are supported.


Characteristic : BOOTSTRAP

NOT USED

NAME NOT USED

NETWORK NOT USED

COUNTRY NOT USED

PROXY-ID NOT USED

PROVURL NOT USED

CONTEXT-ALLOW NOT USED

Characteristic : CLIENTIDENTITY

NOT USED

CLIENT-ID NOT USED

Characteristic : VENDORCONFIG

NOT USED

NAME NOT USED

* NOT USED

APPID Application

w2 Browsing

w4 MMS

w5 OMA Data Synchronization

16 August 2008


Application references:

w7 OMA Device Management

wA IM (Instant Messaging) not supported.

25 Email, SMTP

110 Email, POP3

143 Email, IMAP4


Characteristic : APPLICATION

For the behaviour of each application, please see the specifi-cation for each APPID.

APPID Supported

PROVIDER-ID Supported

NAME Supported

AACCEPT Supported

APROTOCOL Not sup-ported

TO-PROXY Not sup-ported

TO-NAPID Supported

ADDR Supported

APPLICATION : APPADDR

ADDR Supported

ADDRTYPE Supported

APPADDR : PORT

PORTNBR Supported

SERVICE Supported

APPLICATION : APPAUTH

AAUTHLEVEL Supported

AAUTHTYPE Supported

AAUTHNAME Supported

AAUTHSECRET Supported

AAUTHDATA Supported

APPID Application

17 August 2008


Browser - APPID “w2”

OMA Application Characteristic reference^mmfaW=ïOK

^mmfa=íóéÉW=ljk^K

lïåÉêW=lj^=aj=tçêâáåÖ=dêçìéK=

`çåí~ÅíW=lj^=aj=tçêâáåÖ=dêçìé=Ylj^Jaj]j^fiKlmbkjl_fibîif^k`bKlod[K=

oÉÖáëíê~íáçå=îÉêëáçåW=NK

oÉÖáëíê~íáçå=ÇçãÉëíáÅ~íÉW=OMMPJMNJOQK

^ééäáÅ~íáçå=ÇÉëÅêáéíáçåW=_êçïëÉêK

APPLICATION : RESOURCE

URI Supported

NAME Supported

AACCEPT Supported

AAUTHTYPE Supported

AAUTHNAME Supported

AAUTHSECRET Supported

AAUTHDATA Supported

STARTPAGE Supported

Characteristic : ACCESS NOT USED

RULE NOT USED

APPID NOT USED

PORTNBR NOT USED

DOMAIN NOT USED

TO-NAPID NOT USED

TO-PROXY NOT USED


18 August 2008


Description - “w2”Settings for the Browser application.

The following is possible to set via the Browser.

• Start Page with Title for a PXLOGICAL.• Bookmarks.

Compliance

ExampleThis example sets the start page for the PXLOGICAL with PROXY-ID equal to www.google.com.

<?xml version="1.0"?> <!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" "http://www.wapforum.org/DTD/prov.dtd"> <wap-provisioningdoc version="1.0">

<characteristic type="APPLICATION">

<parm name="APPID" value="w2"/> <parm name="TO-NAPID" value="NAP0001" />

<characteristic type="RESOURCE"> <parm name="NAME" value="TestBookmark"/> <parm name="URI" value="http://www.google.com"/> <parm name="STARTPAGE"/> </characteristic>



APPID USED “w2”

TO-PROXY NOT USED TO-NAPID used instead.

TO-NAPID USED

AAUTHTYPE USED Value HTTP-BASIC or HTTP-DIGEST

AAUTHNAME USED

AAUTHSECRET USED


0 or many.

URI USED URL

NAME USED Title of the bookmark or start page.

STARTPAGE USED Sets homepage as this bookmark.

19 August 2008


</characteristic>


MMS - APPID “w4”

OMA Application Characteristic reference^mmfaW=ïQK


lïåÉêW=lj^=jìäíáãÉÇá~=jÉëë~ÖáåÖ=tçêâáåÖ=dêçìéK

`çåí~ÅíW=lj^=jìäíáãÉÇá~=jÉëë~ÖáåÖ=tçêâáåÖ=dêçìé=Ylj^Jjjp]j^fiKlmbkjl_fibîif^k`bKlod[K=


oÉÖáëíê~íáçå=íáãÉëí~ãéW=OMMPJMNJOMK

^ééäáÅ~íáçå=ÇÉëÅêáéíáçåW=jìäíáãÉÇá~=jÉëë~ÖáåÖ=pÉêîáÅÉ=EjjpFK=

^ééäáÅ~íáçå=êÉÑÉêÉåÅÉW=jìäíáãÉÇá~=jÉëë~ÖáåÖ=pÉêîáÅÉ=EjjpF=ëéÉÅáÑáÅ~íáçåëIÜííéWLLïïïKï~éÑçêìãKçêÖLïÜ~íLíÉÅÜåáÅ~äKÜíãK

Description - “w4”Sets the Service Center and proxy for connection.

Compliance

ExampleThis example sets the Service Center and proxy.

<?xml version="1.0"?>



APPID USED “w4”

TO-NAPID USED NAPDEF for the Internet account.

ADDR USED The Service Center

NAME USED Name of MMS account

CREATION-MODE USED Values:R or Restricted-V1_2F or Free-V1_2W or Warning-V1_2

20 August 2008

http://www.wapforum.org/what/technical.htm


<!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" "http://www.wapforum.org/DTD/prov.dtd"> <wap-provisioningdoc version="1.0">

<characteristic type="APPLICATION">

 <parm name="APPID" value="w4"/>  <parm name="TO-NAPID" value="NAP0002" />  <parm name="ADDR" value="http://203.91.202.10:80/wipro=wipro" />

</characteristic>


OMA Data Synchronization - “w5”

OMA Application Characteristic reference:^mmfaW=ïRK


lïåÉêW=a~í~=póåÅÜêçåáò~íáçå=tçêâáåÖ=dêçìéK=

`çåí~ÅíW=a~í~=póåÅÜêçåáò~íáçå=tçêâáåÖ=dêçìé=Ylj^Jap]j^fiKlmbkjl_fibîif^k`bKlod[K=


oÉÖáëíê~íáçå=íáãÉëí~ãéW=OMMQJMNJMVK

^ééäáÅ~íáçå=ÇÉëÅêáéíáçåW=a~í~=póåÅÜêçåáò~íáçå=EapFK=

^ééäáÅ~íáçå=êÉÑÉêÉåÅÉW=

• OMA DS 1.1 specifications, http://www.openmobilealliance.org/release_program/ds_v112.html

• “SyncML Representation Protocol” specification, http://www.syncml.org/docs/syncml_represent_v111_20021002.pdf.

Description - “w5”Creates a synchronization account.

Compliance



0 or 1

APPID USED “w5”

NAME USED The name of the account.

21 August 2008

http://www.openmobilealliance.org/release_program/ds_v112.html

http://www.syncml.org/docs/syncml_represent_v111_20021002.pdf


Example<?xml version="1.0"?> <!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" "http://www.wapforum.org/DTD/prov.dtd"> <wap-provisioningdoc version="1.0">

<characteristic type="APPLICATION">  <parm name="APPID" value="w5"/>  <parm name="NAME" value="Sync"/>  <parm name="TO-NAPID" value="hutch_gprs"/>  <characteristic type="APPADDR"> <parm name="ADDR" value="http://www.mobical.net/sync/server"/> </characteristic> 

TO-NAPID USED Reference to NAPDEF.

ADDR USED The server address.

APPLICATION : APPADDR 0 or 1

ADDR USED The server address.

ADDRTYPE USED IPV6 or ALPHA

PORTNBR or PORT

APPLICATION : APPAUTH There can be 3 APPAUTH within the APPLICATION character-istic, one for HTTP (if AAUTHLEVEL is missing), one for CLI-ENT and one for APPSRV.

AAUTHLEVEL USED APPSRVCLIENT

AAUTHTYPE USED BASIC or DIGEST

AAUTHNAME USED User name.

AAUTHSECRET USED User password.

AAUTHDATA USED


USED 0 or many

URI USED The database URI on the server.

NAME USED

CLIURI USED

AACCEPT USED Must be a MIME-type supported by a database.

AAUTHNAME NOT USED


22 August 2008


<characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="CLIENT"/> <parm name="AAUTHNAME" value="thenmozhi"/> <parm name="AAUTHSECRET" value="tajmahal"/> </characteristic>  <characteristic type="RESOURCE"> <parm name="URI" value="./Contacts"/> <parm name="NAME" value="Contacts DB"/> <parm name="AACCEPT" value="text/x-vcard,text/vcard"/> </characteristic>  <characteristic type="RESOURCE"> <parm name="URI" value="./Calendar"/> <parm name="NAME" value="Calendar DB"/> <parm name="AACCEPT" value="text/x-vcalendar,text/vcalendar"/>

</characteristic> </characteristic>


OMA Device Management - “w7”

OMA Application Characteristic reference^mmfaW=ïTK


lïåÉêW=aÉîáÅÉ=j~å~ÖÉãÉåí=tçêâáåÖ=dêçìéK=

`çåí~ÅíW=aÉîáÅÉ=j~å~ÖÉãÉåí=tçêâáåÖ=dêçìé=Ylj^Jaj]j^fiKlmbkjl_fibîif^k`bKlod[K=


oÉÖáëíê~íáçå=íáãÉëí~ãéW=OMMPJMSJNUK

^ééäáÅ~íáçå=ÇÉëÅêáéíáçåW=aÉîáÅÉ=j~å~ÖÉãÉåí=EajFK=

^ééäáÅ~íáçå=êÉÑÉêÉåÅÉW=

• OMA Device Management, Version 1.1.2 specifications,http://www.openmobilealliance.org/release_program/dm_v112.html.

• “SyncML DM Tree and Description” specification,http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_1_2-20040113-A/OMA-SyncML-DMTND-V1_1_2-20031202-A.pdf.

• “SyncML DM Security” specification,http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_1_2-20040113-A/OMA-SyncML-DMSecurity-V1_1_2-20031209-A.pdf.

• “SyncML Representation Protocol” specification,http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_1_2-20040113-A/OMA-SyncML-DMRepPro-V1_1_2-20030613-A.pdf.

23 August 2008

http://www.openmobilealliance.org/release_program/dm_v112.html

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_1_2-20040113-A/OMA-SyncML-DMSecurity-V1_1_2-20031209-A.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_1_2-20040113-A/OMA-SyncML-DMSecurity-V1_1_2-20031209-A.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_1_2-20040113-A/OMA-SyncML-DMRepPro-V1_1_2-20030613-A.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_1_2-20040113-A/OMA-SyncML-DMRepPro-V1_1_2-20030613-A.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_1_2-20040113-A/OMA-SyncML-DMTND-V1_1_2-20031202-A.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_1_2-20040113-A/OMA-SyncML-DMTND-V1_1_2-20031202-A.pdf


Description - “w7”Creates a Device Management account

Compliance



0 or 1

APPID USED

PROVIDER-ID USED Will be used as authentication name for server. If not supplied then AAUTHNAME from the APPAUTH with AUTHLEVEL APP-SRV is used.

INIT USED Initiates a Device Management session after provisioning doc-ument has been installed. This parameter is an application specific parameter and is an extension.

NAME USED Used as displayable name in UI.

TO-NAPID USED Refers to NAPDEF that is used for connection in the account.

ADDR USED Device Management server URI.

APPLICATION : APPADDR USED

ADDR USED If both APPLICATION/ADDR and APPADDR exists settings will be considered invalid.

ADDRTYPE USED ALPHA or IPV6, the value has no affect but if something differ-ent is set then the AC will be rejected. It is OK not to send this value at all.

APPADDR : PORT SUP-PORTED

PORTNBR SUP-PORTED

APPLICATION : APPAUTH USED There can be 3 APPAUTH within the APPLICATION character-istic. One for HTTP (if AAUTHLEVEL is missing), one for CLI-ENT and one for APPSRV.

AAUTHLEVEL USED CLIENT means authentication data that the client will send to the server. APPSRV means authentication data that the client will receive from the server.

AAUTHTYPE USED BASIC or DIGEST.

AAUTHNAME USED User name.

AAUTHSECRET USED Password to use together with AAUTHNAME.

AAUTHDATA USED Used to specify nonce.

24 August 2008


Example<?xml version="1.0"?><wap-provisioningdoc version="1.1">

<characteristic type="APPLICATION"><parm name="APPID" value="w7"/><parm name="PROVIDER-ID" value="Scts"/><parm name="NAME" value="ccc"/> <parm name="ADDR" value="http://203.91.202.11:8080/Manage"/><parm name="TO-NAPID" value="NAP0004"/>

<characteristic type="APPAUTH">

<parm name="AAUTHLEVEL" value="APPSRV"/><parm name="AAUTHTYPE" value="DIGEST,BASIC"/><parm name="AAUTHNAME" value="ccc"/><parm name="AAUTHSECRET" value="ccc"/>

</characteristic><characteristic type="APPAUTH">

<parm name="AAUTHLEVEL" value="CLIENT"/><parm name="AAUTHNAME" value="ccc"/><parm name="AAUTHSECRET" value="ccc"/>

</characteristic></characteristic>


25 August 2008


Email, SMTP - “25”

OMA Application Characteristic reference^mmfaW=ORK

^mmfa=íóéÉW=f^k^K

lïåÉêW=lj^=aj=tçêâáåÖ=dêçìéK

`çåí~ÅíW=lj^=aj=tçêâáåÖ=dêçìé=Ylj^Jaj]j^fiKlmbkjl_fibîif^k`bKlod[K


oÉÖáëíê~íáçå=íáãÉëí~ãéW=OMMPJMPJOMK

^ééäáÅ~íáçå=ÇÉëÅêáéíáçåW=bã~áä=pjqm=ëÉííáåÖëK=

^ééäáÅ~íáçå=êÉÑÉêÉåÅÉW=pÉÉ=oc`=OUON=Ñçê=pjqm=ÇÉÑáåáíáçåK

Description - “25”Setting for the Email SMTP (Simple Mail Transfer Protocol) server, that is, outgoing Email.

Compliance



0 or 1

APPID USED “25”

PROVIDER-ID(NAME can be used for the same purpose.)

USED Account name. Note: NAME, if present, takes precedence over PROVIDER-ID.

TO-NAPID USED Reference to NAPDEF (“Data account”).

ADDR USED ADDR can either be used in APPLICATION or APPLICA-TION:APPADDROutgoing server host name.

FROM(RT-ADDR, Reply To Address, is also supported)

USED The user’s email address.


ADDR USED ADDR can either be used in APPLICATION or APPLICA-TION:APPADDROutgoing server host name.

APPADDR : PORT

PORTNBR USED Outgoing server port number, 16 bit unsigned number.

SERVICE USED Empty or STARTTLS.

26 August 2008


Example, SMTP and POP3<?xml version="1.0"?><!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN""http://www.wapforum.org/DTD/prov.dtd"><wap-provisioningdoc>

<characteristic type="NAPDEF">

<parm name="NAPID" value="Hutch"/><parm name="BEARER" value="GSM-GPRS"/><parm name="NAME" value="hutch_gprs"/><parm name="NAP-ADDRESS" value="www"/><parm name="NAP-ADDRTYPE" value="APN"/><parm name="INTERNET"/>

</characteristic>

<characteristic type="APPLICATION"><parm name="APPID" value="110"/><parm name="PROVIDER-ID" value="Yahoo"/><parm name="TO-NAPID" value="Hutch"/><characteristic type="APPADDR">

<parm name="ADDR" value="pop.mail.yahoo.co.jp"/><characteristic type="PORT">

<parm name="PORTNBR" value="110"/><parm name="SERVICE" value="STARTTLS"/>

</characteristic></characteristic><characteristic type="APPAUTH">

<parm name="AAUTHNAME" value="srisivajp"/><parm name="AAUTHSECRET" value="techie!"/>


<characteristic type="APPLICATION"><parm name="APPID" value="25"/><parm name="PROVIDER-ID" value="Yahoo"/><parm name="FROM" value="[email protected]"/><parm name="TO-NAPID" value="Hutch"/><characteristic type="APPADDR">

<parm name="ADDR" value="smtp.mail.yahoo.co.jp"/><characteristic type="PORT">

<parm name="PORTNBR" value="25"/>


AAUTHNAME USED Username for outgoing server

AAUTHSECRET USED Password for incoming and outgoing server


27 August 2008


<parm name="SERVICE" value="STARTTLS"/></characteristic>

</characteristic><characteristic type="APPAUTH">

<parm name="AAUTHNAME" value="srisivajp"/><parm name="AAUTHSECRET" value="techie!"/>



Email, POP3 - “110”

OMA Application Characteristic reference^mmfaW=NNM


lïåÉêW=lj^=aj=tçêâáåÖ=dêçìéK




^ééäáÅ~íáçå=ÇÉëÅêáéíáçåW=bj~áä=mlmP=ëÉííáåÖëK

^ééäáÅ~íáçå=êÉÑÉêÉåÅÉW=mlmP=áë=ÇÉÑáåÉÇ=áå=oc`NVPVK

Description - “110”Setting for the incoming email server using POP3 protocol.

Compliance



APPID USED “110”

PROVIDER-ID USED Account name

TO-NAPID USED Reference to NAPDEF (“Data account”).

ADDR USED ADDR can either be used in APPLICATION or APPLICA-TION:APPADDRIncoming server host name.

28 August 2008


ExampleSee “Example, SMTP and POP3” above.

Email, IMAP4 - “143”

OMA Application Characteristic reference^mmfaW=NQP


lïåÉêW=lj^=aj=tçêâáåÖ=dêçìéK=




^ééäáÅ~íáçå=ÇÉëÅêáéíáçåW=bj~áä=fj^mQ=ëÉííáåÖëK

^ééäáÅ~íáçå=êÉÑÉêÉåÅÉW=fj^mQ=áë=ÇÉÑáåÉÇ=áå=ocÒMSMK

Description - “143”This is the setting for the incoming email server using IMAP4 protocol.



APPADDR : PORT

PORTNBR USED Incoming server port number. 16 bit unsigned number.

SERVICE USED Empty, STARTTLS or 995 (=STARTTLS).


AAUTHNAME USED Incoming server user name.

AAUTHTYPE USED APOP or PLAIN

AAUTHSECRET USED Incoming server password.


29 August 2008


Compliance



APPID USED “143”

PROVIDER-ID USED Account name.

TO-NAPID USED




APPADDR : PORT

PORTNBR USED Incoming server port number. 16 bit unsigned number.

SERVICE USED Empty, STARTTLS or 993.


AAUTHNAME USED Incoming server user name.

AAUTHSECRET USED Incoming server password.

30 August 2008


OMA Device Management

OMA Device Management offers an advanced method for centralized control and management of differ-ent configuration settings in mobile devices. Device management is carried out in sessions where a man-agement server through a dialog with the mobile device client updates one or several configuration settings in the device. For example the server can install new or upgraded applications and update set-tings for Internet, MMS and email.

31 August 2008


Introduction

OMA Device Management is based on the same technology as OMA Data Synchronization (formerly known as SyncML Data Synchronization). The main difference is that, while OMA DS synchronizes two or more sets of data in two or more devices, OMA Device Management updates client device configuration settings from data stored in one specific server.

The Client Provisioning and Device Management technologies are also based on similar technologies. One important difference is the communication between server and client :

• Client Provisioning is performed in a one way communication where the server sends a provisioning document to the client. The XML contents of the file is parsed and the settings contained in the docu-ment are stored in the client device. There is no dialog between the client and server after the transfer of data has started.

• Device Management is carried out in sessions. Once a session is established, the server sends one or several WBXML encoded commands to the client, and the client responds on each command with result and status information. (The protocol allows either XML or WBXML encoding, but Sony Ericsson clients only support WBXML).

In Device Management client devices, data that can be affected by Device Management activities is stored in a tree structure defined in the OMA standards. The DM tree contains nodes and leaves. Leaves contain settings and parameter values, controlling software and hardware operations in the device. Leaves are always on the lowest level in the DM tree, and can therefore not contain any sublevels. Groups of settings and parameters for a specific application are referred to as Management Objects (MO) and are represented as “branches” of the DM tree. Thus a MO is found as a number of subnodes and leaves ema-nating from one node.

Dynamic nodes are nodes and leaves that can be added by a DM server using the Add command. The DDF often uses the Occurrence-tag to indicate whether a particular node is an important (Occurrence One) or more optional (Occurence ZeroOrOne) setting within a MO. That is, it is generally recommended that the server explicitly adds nodes with Occurrence One while optional nodes may be omitted. The Sony Ericsson DM Client will however implicitly create missing nodes in newly added MOs, after the DM session ends. Therefore, when the server reconnects with the phone in a subsequent DM session, the existing MOs will be complete. If the server wants to modify the values of any leaves, it will now have to use the Replace command.

The DM Delete command is in most cases not allowed on single nodes within a MO, to ensure the integrity of, for example, account structures. Dynamic MOs can however in many cases be deleted at the place-holder level instead.

Device Management is typically implemented in a device as follows:

1. OMA Client Provisioning is used to bootstrap the device with settings for an OMA DM account.

2. OMA DM sessions are initiated using the built-in security and authentication features.

3. During DM sessions the accounted server sends WBXML encoded commands to the client, and the client responds to these with results and status information. Data in the DM tree can be read, changed or deleted or new data can be stored in the tree.

32 August 2008


4. Programmatically DM sessions are always initiated by the client device, but a DM server may alert the client about recommended DM activities. Thus a DM use case can be regarded as initiated by either the phone (DM client) or by the DM server.

Supported standards and protocols

OMA Device Management has its origin in SyncML DM and has been standardized by OMA. Please refer to the following documents, found at http://www.openmobilealliance.org/ for details on the standards:

• SyncML Device Management Tree and Description version 1.1.2• SyncML Device Management Protocol version 1.1.2• SyncML Representation Protocol, Device Management Usage, Version 1.1.2• SyncML Device Management Security version 1.1.2• SyncML Device Management Bootstrap, Version 1.1.2• SyncML Device Management Standardized Objects, version 1.1.2• Notification Initiated Session, version 1.1.2

Preconditions

Common preconditions for DM sessions to take place are:

• The client (mobile phone) has a correctly configured DM and Internet account.

• The client is registered in a GSM/UMTS network, to be able to receive connectionless WAP push (SMS).

• The client can connect/be connected, typically via HTTP with bearers GSM/GPRS or packet switched WCDMA.

DM sessions

A DM session can be divided into two phases:

• The setup phase in which authentication and device information exchange between the client and server takes place.

• The management phase in which management actions are carried out in an iterated process. The device management server sends DM commands in WBXML format to the client and the client responds with messages containing Results and/or Status values. The server finally sends a message with no operations, to which the client manager responds by finalizing the DM session.

For detailed information about the different types of messages needed to carry out sessions according to the above, please refer to SyncML Device Management Protocol version 1.1.2, http://www.openmobileal-liance.org/

33 August 2008





General use case

A Device Management session is set-up between the phone and a DM server. The purpose for the server is to configure the phone and/or to read information from it. In this use case it is assumed that the server takes the initiative to the session, and that the phone (and possibly its user) responds to the server initia-tive.

A DM server decides that it wants to establish a DM session to perform a certain task. The decision can be made automatically. For example, an event on timer, controlled by parameter settings, or ordered by a server operator.

Example: An operator is launching a new service and as a result of this they are restructuring their service network, requiring some existing customers to modify their configurations.

1. The DM server sends out a package 0 message using connectionless WAP push. (Refer to Notification Initiated Session for details on the standard)

2. The message is received and integrity-checked in the phone.

3. Depending on internal settings in the DM account, the package 0 push is handled according to one of the following directives:

• Accept. The client accepts the package 0 message automatically, and starts the DM session with-out user interaction. However, if <ui-mode> in the message is set to “user interaction” by the server, the user will be prompted as in the Always ask alternative below.

• Never accept. The client is set to reject all package 0 messages on the current DM account. This ends the use case automatically.

• Always ask. The user is prompted (yes/no) to accept the DM session or not. The use case continues if the user answers yes.

4. The phone establishes the session. The phone displays that an activity is ongoing, and the DM session continues.

5. During the session the DM server reads and writes application data from/to the phone.

6. When the DM server has finished its task it terminates the DM session by sending an empty package to the phone. The session ends.

Versioning

The DevInfo/DmV node contains the version number of the Device Management client implementation. The DM client in the P990, M600, W950, P1, W960 series is version S1.0. The DM client in the G700, G900 series is S1.5.

Minor version increments indicate small changes, for example addition of a new management object or minor changes to existing nodes (such as a changed Format or AccessType for a node).

Major version increments indicate larger changes.

34 August 2008


Every increment in the DmV value mandates the release of a new corresponding DDF at the Sony Ericsson website. The URL to Sony Ericsson online DDFs is wap.sonyericsson.com/ddf/<devinfo/mod>"_"<devinfo/dmV>.xml. The DDF can also be obtained from the DM tree on the device in the node /DevDetail/Ext/Symbian/Ddf. This will always be absolutely accurate since it is drawn directly from the implementation.

Authentication

The OMA Device Management standard defines two different security mechanisms: transport security and protocol (session level) security. The following authentication mechanisms defined in the DM standard are supported in the Symbian SyncML framework:

• Basic authentication (session level)• MD5 authentication (session level)• HMAC authentication (transport level, used only over HTTP or HTTPS)

If a server uses an HTTPS address then the server certificate will be checked as part of the connection. If there are problems with the certificate then the user is given the choice of continuing the session or termi-nating the session. HTTPS does not apply to client authentication, that is, it cannot be used by a server to authenticate a client.

The DM client stores an authentication scheme for each DM server account. The same authentication scheme is used for both client and server authentication. This means that it is not possible to use one authentication scheme for client authentication and another for server authentication.

The DM client stores a server id (used as the server user name) and server password and separate client user name and password values. Also, nonces are stored separately for client and server authentication. By default, when a DM account is set up the nonces are initialized to empty strings.

During the authentication phase, the DM client will accept packages with only a challenge and no DM commands, as well as normal packages with both the challenge and some commands. Once authentica-tion is done however, an empty package will signal the end of the session.

Client authenticationDM requires client authentication, so Symbian SyncML Framework includes a <Cred> element in the <SyncHdr> of each initial message (and subsequent messages until the server accepts them). The valid responses from a server are:

• Status 401 – Bad credentials• Status 407 – Missing credentials• Status 200 – OK• Status 212 – Authentication accepted

Status 401 or 407 mean that the client was not authenticated and so any commands included in the mes-sage will be ignored. Status 200 means that the client was authenticated and so commands will be accepted but the same credentials must be re-sent in subsequent messages. Status 212 means that the client was authenticated and credentials need not be re-sent in subsequent messages.

35 August 2008


In the case of a Status 401 or 407 the server must include a <Chal> element in the relevant <Status> element. In the case of a Status 200 or 212 the server must also include a <Chal> element if a nonce-based authentication scheme is in use (anything but None or Basic schemes). This is to refresh the nonce value used to authenticate the client to the server. Note that if the server sends a Status 200 and a <Chal> to refresh an MD5 nonce, the original nonce is used to calculate credentials for subsequent mes-sages in the same session. The new nonce only applies to the next session. If the client is using HMAC then the new nonce is used immediately as a new nonce is supposed to be used for each message.

If the server sends any response except a Status 212 then the client will respond with credentials in the next message.

If the server responds with Status 401 or 407 four times in a row then the Symbian SyncML framework will terminate the session.

A server can change the authentication scheme by including a <Chal> within a <Status> element and the change will be accepted (unless it reduces the authentication level for server authentication to an unacceptable level - see next section).

Server AuthenticationThe Symbian SyncML framework requires server authentication for DM. Server authentication and client authentication are considered separate, that is, a server may be authenticated while the client is not or vice-versa.

In a DM session, the Symbian SyncML framework expects the DM server to send credentials in its first message (unless it is using HMAC). If the server does not send credentials then the Symbian SyncML framework will send a Status 407 - missing credentials.

If HMAC authentication is used then the credentials from the HTTP headers are checked, but any response (including Status codes and fresh nonces) is included in the SyncML message. A fresh nonce is required for each exchange and so a <Chal> is included in each message.

If the server sends credentials then they are validated against the stored server id, password and nonce. If the server credentials are valid, then the server is considered authenticated and Status 212 is returned along with a <Chal> if it is necessary to refresh the nonce. In the case of HMAC a status 200 is returned because the credentials are expected in each message header.

If credentials are missing then Status 407 is returned. If credentials are invalid then status 401 is returned. If the credentials are missing or invalid then the same Status code is returned to all commands in the mes-sage and no commands are accepted until the server is authenticated.

The Symbian SyncML framework will allow an authentication scheme of Basic, MD5 or HMAC for a DM server, the authentication scheme cannot be set to None.

Server Alerted Notification authenticationServer Alerted Notification (sometimes known as SAN or Message 0) messages can be delivered by WAP Push or other means and are used by a DM server to trigger a session. In the Symbian based Sony Ericsson DM client, digest checking of SAN messages has been disabled.

36 August 2008


Management Objects

The basic tree structure

Logical Branding Element subtree ./UIQ/LBE

Logical Branding Element, LBE, is a setting that corresponds to a permanent setting exposed by the DDF. A setting, that is, a lock, could be application or system specific. A lock is represented as boolean and can show one of two states, true or false.

Subtree structure

. UIQ LBE >>

EDC >>

SecureDevice

WlanNAP >>

SNAP >>

Browser >>

Proxy >>

SyncML DMAcc >>

DSAcc >>

NAP >>

Email >>

SMS >>

MMS >>

DevInfo >>

DevDetail >>

Software >>

LBE Apps AppLauncher DefaultFolder

GlobalLocks

DisplayType

Folders Main Locks

SortOrder

Tools Locks

SortOrder

System Themes Locks

DateTime NITZ

37 August 2008


./UIQ/LBEAccess Type: GetOccurance: OneFormat: Node

./UIQ/LBE/AppsAccess Type: GetOccurance: OneFormat: Node

./UIQ/LBE/Apps/ApplauncherApplauncher LBEs

Access Type: GetOccurance: OneFormat: Node

./UIQ/LBE/Apps/Applauncher/DefaultFolderThis setting defines the folder in which applications are placed by default.

Access Type: Get, ReplaceOccurance: OneFormat: int

./UIQ/LBE/Apps/Applauncher/GlobalLocksThis setting defines whether the user is allowed to:

• switch between list or grid view• remove or rename predefined applications• create additional folders

Access Type: Get, ReplaceOccurance: OneFormat: intAllowed values: Any combination of:0x01, Display lock, prevents user from switching display type.0x02, Predefined application lock, prevents user from moving predefined applications.0x04, Create lock, preventing users from creating new folders.

38 August 2008


./UIQ/LBE/Apps/Applauncher/DisplayTypeDefines whether the application list is rendered with a grid or list layout. This setting is a 4 bit field in the form ssmm, where ss is the folders display type and mm is the main view display type. The following dis-play types are defined:

Access Type: Get, ReplaceOccurance: OneFormat: intAllowed values:

./UIQ/LBE/Apps/Applauncher/FoldersAccess Type: GetOccurance: OneFormat: Node

./UIQ/LBE/Apps/Applauncher/Folders/MainAccess Type: GetOccurance: OneFormat: Node

./UIQ/LBE/Apps/Applauncher/Folders/Main/LocksThis setting defines whether the user is allowed to:

• remove or rename predefined folders.• add or remove applications to/from the folder.

Access Type: Get, ReplaceOccurance: OneFormat: intAllowed values: any combination of:0x01, Change lock, prevents removing or renaming predefined folder.0x02, Application add lock, prevents adding applications to predefined folder.

Display type Binary value

List view 01

Grid view 10

Folders (ss) Main view (mm) Binary value Decimal value

List view 01 List view 01 0101 5

Grid view 10 Grid view 10 1010 10

Grid view 10 List view 01 1001 9

List view 01 Grid view 10 0110 6

39 August 2008


./UIQ/LBE/Apps/Applauncher/Folders/Main/SortOrderDefines the order in which applications are sorted in the list. The application list sort order can be changed for each predefined folder. Both applications and subfolders can be sorted.

Access Type: Get, ReplaceOccurance: OneFormat: chrAllowed values: The sort order string follows the following syntax:"<appId> application_UID <handle> folder_id" where:<appId> specifies that a list of application UIDs follows.<handle> specifies that a list of folder IDs follows.application_UID: One or several application UIDs. Can be a decimal or hexadecimal value.folder_id: One or several predefined folder IDs. Decimal value.Example: "<appId> 0x10003A5C 0x10003A74 <handle> 2 4 <appId> 0x10000083 <handle> 1 <appId> 0x10003A70"

./UIQ/LBE/Apps/Applauncher/Folders/ToolsAccess Type: GetOccurance: OneFormat: Node

./UIQ/LBE/Apps/Applauncher/Folders/Tools/LocksThis setting defines whether the user is allowed to:

• remove or rename predefined folders.• add or remove applications to/from the folder.

Access Type: Get, ReplaceOccurance: OneFormat: intAllowed values: any combination of:0x01, Change lock, prevents removing or renaming predefined folder.0x02, Application add lock, prevents adding applications to predefined folder.

./UIQ/LBE/Apps/Applauncher/Folders/Tools/SortOrderDefines the order in which applications are sorted in the list. The application list sort order can be changed for each predefined folder. Both applications and subfolders can be sorted.

Access Type: Get, ReplaceOccurance: OneFormat: chrAllowed values: The sort order string follows the following syntax:"<appId> application_UID <handle> folder_id" where:<appId> specifies that a list of application UIDs follows.<handle> specifies that a list of folder IDs follows.application_UID: One or several application UIDs. Can be a decimal or hexadecimal value.folder_id: One or several predefined folder IDs. Decimal value.Example: "<appId> 0x10003A5C 0x10003A74 <handle> 2 4 <appId> 0x10000083 <handle> 1 <appId> 0x10003A70"

40 August 2008


./UIQ/LBE/SystemAccess Type: GetOccurance: OneFormat: Node

./UIQ/LBE/System/ThemesAccess Type: GetOccurance: OneFormat: Node

./UIQ/LBE/System/Themes/LocksThe UIQ Theme package consists of several groups of items, each of which can be individually locked to prevent users from changing them in order to protect branding items. The settings are Boolean, and col-lected in a single unsigned 32-bit integer that is bitwise masked for comparison. In practice this means that a decimal setting value of zero is equivalent to all groups unlocked, and to lock a specific group means adding its lock value to the total setting value.


Value Group

1 Dialog and container pop-out skins

2 Listbox skins

4 Menupane skins

8 Button skins

16 Tab skins

32 32 Label skins

64 Building block skins

128 Screen background skin

256 App title bar, Status bar and Soft Key bar skins

512 Horizontal and vertical scrollbar skins

1024 Time and IP editor skins

2048 Calendar skins

4096 Editor skins

8192 Choice list and Color selector skins

16384 Progress bar and Slider skins

32768 Checkbox and Option button skins

65536 Default ring signal sound

41 August 2008


./UIQ/LBE/System/DateTimeAccess Type: GetOccurance: OneFormat: Node

./UIQ/LBE/System/DateTime/NITZDetermine the NITZ behaviour.


Externally Defined Command subtree ./UIQ/EDC

An Externally Defined Command, EDC, is a menu item provided by an operator DM server. DM servers wishing to use this management object are advised to be familiar with UIQ OCP (Operator Customization Package) technology.

An embedded link has the following node structure in the DM tree:

.UIQ/Edc/<AppUID>/<ViewUid>/<CommandId>

The minimum leaf nodes to create are Type and LongLabel - (Plain text)

131072 New sms, mms, e-mail, fax, beamed object and voice message sounds

262144 Hardware button pressed and Screen tap sounds

524288 Beep and Error sounds

1048576 Default alarm sound

2097152 Default new message sound

4194304 AppLauncher wallpaper image

8388608 System color scheme

16777216 Folder skins

Value Description

0 Automatically

1 Ask me

2 Never

Value Group

42 August 2008


Type is one of:

enum TQikEmbeddedLinkLinkType { EQikEmbeddedLinkCall, 0 EQikEmbeddedLinkUrl, 1 EQikEmbeddedLinkSMS, 2 EQikEmbeddedLinkMMS, 3 EQikEmbeddedLinkEmail 4 };

In addtion for types: EQikEmbeddedLinkUrl, EQikEmbeddedLinkCall

Recipient is also mandatory.

Subtree structure

./UIQ/EDCAccess Type: GetOccurance: OneFormat: Node

./UIQ/EDC/XThe name of the node corresponds to the appuid for the application to which some externally defined command must be added (in hex).

Access Type: Add, Delete, Get, ReplaceOccurance: ZeroOrMoreFormat: Node

EDC <X>* <X>* <X>* Type

Priority

Recipient

CommandIcon

CommandIconId

CommandIconMask

CommandType

CommandGroupId

CommandNamedGroupLinkId

CommandNamedGroupId

CommandStateFlags

CommandCpfFlags

LongLabel

ShortLabel

Body

Subject

43 August 2008


./UIQ/EDC/X/XThe name of the node corresponds to the viewuid for the application to which some externally defined command must be added (in hex)


./UIQ/EDC/X/X/XThe uid for the command, is an integer, and the allowed range is 0x0C00 - 0x0C3F (specified in Qikon.hrh)


./UIQ/EDC/X/X/X/TypeAccess Type: Add, Delete, Get, ReplaceOccurance: OneFormat: intAllowed values: Type is one of TQikEmbeddedLinkLinkType:

enum TQikEmbeddedLinkLinkType { EQikEmbeddedLinkCall, 0 EQikEmbeddedLinkUrl, 1 EQikEmbeddedLinkSMS, 2 EQikEmbeddedLinkMMS, 3 EQikEmbeddedLinkEmail 4 };

./UIQ/EDC/X/X/X/PriorityAccess Type: Add, Delete, Get, ReplaceOccurance: OneFormat: int

./UIQ/EDC/X/X/X/RecipientType specific command argument.

Access Type: Add, Delete, Get, ReplaceOccurance: OneFormat: chrAllowed values: For URI the uri to accessFor Call the phone number to call

44 August 2008


./UIQ/EDC/X/X/X/CommandIconShould be a folder location for a MBM file or similar on, for example, the z drive.

Access Type: Add, Delete, Get, ReplaceOccurance: OneFormat: chr

./UIQ/EDC/X/X/X/CommandIconIdID of the Icon to use in the MBM file.

Access Type: Add, Delete, Get, ReplaceOccurance: OneFormat: int

./UIQ/EDC/X/X/X/CommandIconMaskID of the Mask in the MBM file.

Access Type: Add, Delete, Get, ReplaceOccurance: OneFormat: int

./UIQ/EDC/X/X/X/CommandTypeAccess Type: Add, Delete, Get, ReplaceOccurance: OneFormat: int

./UIQ/EDC/X/X/X/CommandGroupIdAccess Type: Add, Delete, Get, ReplaceOccurance: OneFormat: int

./UIQ/EDC/X/X/X/CommandNamedGroupLinkIdAccess Type: Add, Delete, Get, ReplaceOccurance: OneFormat: int

./UIQ/EDC/X/X/X/CommandStateFlagsAccess Type: Add, Delete, Get, ReplaceOccurance: OneFormat: int

./UIQ/EDC/X/X/X/CommandCpfFlagsAccess Type: Add, Delete, Get, ReplaceOccurance: OneFormat: int

45 August 2008


./UIQ/EDC/X/X/X/LongLabelLong label for the command. (as seen in menu).


./UIQ/EDC/X/X/X/ShortLabelShort label for the command (as seen in soft keys).


./UIQ/EDC/X/X/X/BodyBody content for SMS/MMS/Email.


./UIQ/EDC/X/X/X/SubjectSubject in Email / MMS


EDC exampleTo create a URL embedded link in AppLauncher create the following nodes:

./UIQ/EDC/0x100051F8 App UID

./UIQ/EDC/0x100051F8/0x1000AD31 View UID

./UIQ/EDC/0x100051F8/0x1000AD31/0x4000 CommandId

Create the following leaf nodes:

./UIQ/EDC/0x100051F8/0x1000AD31/0x4000/Type, Value: "1"

./UIQ/EDC/0x100051F8/0x1000AD31/0x4000/LongLabel, Value: "A new URL"

./UIQ/EDC/0x100051F8/0x1000AD31/0x4000/Recipient, Value: "www.uiq.com"

46 August 2008


Remote Lock & Wipe subtree ./SecureDevice

A typical use case for Remote Lock & Wipe is when a DM service provider (for example an operator or enterprise) decides that a certain phone shall be locked and initiates the lock down procedure.

./SecureDeviceThis is the only node in the lock and erase part of the device management tree.

Access Type: ExecOccurance: OneFormat: Node

The SecureDevice function makes it possible to lock the device and wipe user data.

When issuing an exec command on the node, some parameters have to be supplied in the data. The argu-ments are formatted as follows:

lock=<bool>&erase=<bool>&shutdown=<bool>&code=<deviceLockCode>, bool=true|false

deviceLockCode=8 numeric characters

If lock is true, the screen saver will be activated and the user forced to enter a device lock code before proceeding. The device lock code will also be required on boot. All comms will be shutdown and the radio switched off.

If erase is true then a master reset will be triggered. The device is rebooted in order to complete the mas-ter reset.

If shutdown is true the device will be shut down once the other actions have been applied

A correct device lock code must be supplied by the server in order for this function to be activated. The device lock code must be at least 8 digits long and must not match the factory default.

The function returns a result status after checking the device lock code and enabling the screen saver device lock and prior to initiating other functions (master reset, disabling comms). So the server has no way to know if the function has fully succeeded. The device lock code will be checked before a status code is returned to the server.

47 August 2008


WLan accesspoint settings ./WlanNAP

Note:This MO is not available on M600, W950, G700

Subtree structure

./WlanNAPAccess Type: GetOccurance: OneFormat: Node

./WlanNAP/XDescription: Placeholder for a WLAN account

WlanNAP <X>* NapId

Name

AuthInfo AuthType

EncryptionType

NetworkAuthType

InnerEncryptType

WepKeys? <X>* Key

HexKey

WepIndex?

Username?

Password?

Passphrase?

CertificateName?

Ssid

MacAddress

NetworkMode

Channel

Valid

RtsThreshold

PowerSaveMode

IPv4 LocalAddr

NetMask

DefaultGateway

AutoConfig

DNS <X>* DNSAddr

IPv6 LocalAddr

AutoConfig

48 August 2008


Access Type: Add, Copy, Delete, Get, ReplaceOccurance: ZeroOrMoreFormat: Node

./WlanNAP/X/NapIdThe identifier of this NAP object. See also ./NAP/X/NapId

Access Type: GetOccurance: OneFormat: int

./WlanNAP/X/NameHuman readable name of this NAP object.

Access Type: Get, ReplaceOccurance: OneFormat: chrDefault value: “Wlan account <n>” , where n is a value depending on how many other accounts exist.

./WlanNAP/X/AuthinfoAccess Type: GetOccurance: OneFormat: Node

./WlanNAP/X/Authinfo/AuthTypeAuthentification type for the account.

Access Type: Get, ReplaceOccurance: OneFormat: chrDefault value: “Open”Allowed values: Open, Shared, WPA, WPA_PSK, Open_EAP, WPA2, WPA2_PSK

./WlanNAP/X/Authinfo/EncryptionTypeEncryption for the account.

Access Type: Get, ReplaceOccurance: OneFormat: chrDefault value: “None”Allowed values: None, WEP, TKIP, AES, Dynamic_WEP

./WlanNAP/X/Authinfo/NetworkAuthTypeNetwork authentification for the account.

Access Type: Get, ReplaceOccurance: OneFormat: chrDefault value: “None”Allowed values: None, EAP_MD5, EAP_TLS, EAP_TTLS, PEAP, LEAP, SIM, AKA

49 August 2008


./WlanNAP/X/Authinfo/InnerEncryptTypeInner encryption for the account.

Access Type: Get, ReplaceOccurance: OneFormat: chrDefault value: “None”Allowed values: None,EAP_MD5, PAP, CHAP_V2, EAP_GTC, MS_CHAP_V2

./WlanNAP/X/Authinfo/WepKeysNode for setting WEPKeys. The node is only accessible if WEPKeys are required given the selected encryption method.

Access Type: GetOccurance: ZeroOrOneFormat: Node

./WlanNAP/X/Authinfo/WepKeys/XAllows an individual WEP Key to be set up. If the WEPKeys node as a whole is present then there are pre-cisely 4 keys available which can be set. They are ordered, first in child list is key 0, … last in child list is key 3.

Access Type: GetOccurance: 4Format: Node

./WlanNAP/X/Authinfo/WepKeys/X/KeyThe value of an ascii key. If an empty value is supplied then this key will not be used to decrypt and encrypt frames, otherwise it will be used if it is the correct length.

Access Type: ReplaceOccurance: OneFormat: chr

./WlanNAP/X/Authinfo/WepKeys/X/HexKeyThe value of a hex key. If an empty value is supplied then this key will not be used to decrypt and encrypt frames, otherwise it will be used.

Access Type: ReplaceOccurance: OneFormat: chr

./WlanNAP/X/Authinfo/WepIndexThe value used for wep key index determines which key will be used during the TX phase of data trans-mission. Please refer to IEEE 802.11 spec 1999 WEP algorithm for more information.

Access Type: Get, ReplaceOccurance: ZeroOrOneFormat: int

50 August 2008


./WlanNAP/X/Authinfo/UsernameIf this node is present then a user name is required according to the security parameters previously set.

Access Type: Get, ReplaceOccurance: ZeroOrOneFormat: chr

./WlanNAP/X/Authinfo/PasswordIf this node is present then a password is required according to the security parameters previously set.

Note: It can only be written, not retrieved.

Access Type: ReplaceOccurance: ZeroOrOneFormat: chr

./WlanNAP/X/Authinfo/PassphraseIf this node is present then a passphrase is required according to the security parameters previously set. Note: The passphrase cannot be read, only written.


./WlanNAP/X/Authinfo/CertificateNameIf this node is present then a certificate name is required according to the security parameters previously set. The certificate must be present in the certificate store. Device Management of the certificate store is not supported


./WlanNAP/X/SsidThe SSID of the network associated with the account. SSID is short for Service Set IDentifier, a 32-charac-ter unique identifier attached to the header of packets sent over a WLAN that acts as a password when a mobile device tries to connect to the BSS (see Infrastructure Mode). The SSID differentiates one WLAN from another, so all access points and all devices attempting to connect to a specific WLAN must use the same SSID. A device will not be permitted to join the BSS unless it can provide the unique SSID. Because an SSID can be sniffed in plain text from a packet, it does not supply any security to the network.

Access Type: Get, ReplaceOccurance: OneFormat: chr

51 August 2008


./WlanNAP/X/MacAddressMachine address, used in some types of WLAN server configurations to constrain access. MacAddress can be retrieved using DM in order to configure the server appropriately.

Access Type: GetOccurance: OneFormat: chr

./WlanNAP/X/NetworkModeNetworkMode for the WLAN account.

Access Type: Get, ReplaceOccurance: OneFormat: chrAllowed values: “Infrastructure”, “AdHoc”

./WlanNAP/X/ChannelChannel to use when connecting in ad-hoc mode, must be a channel previously agreed with the other party.

Access Type: Get, ReplaceOccurance: OneFormat: intAllowed values: Range 1 - 14

./WlanNAP/X/ValidAllows the server to find out whether the WLAN account is configured correctly, for example if the combi-nation of security options is acceptable. Note that the fact it is figured correctly does not mean it will nec-essarily work, but if it is not valid then it definitely will not. Refer to the WLAN UI on the device in order to find out what constitutes a valid configuration.

Access Type: GetOccurance: OneFormat: bool

./WlanNAP/X/RtsThresholdRTS threshold to use.

Access Type: Get, ReplaceOccurance: OneFormat: intAllowed values: Range 256 - 2347

./WlanNAP/X/PowerSaveModeUse power save mode for the account?

Access Type: Get, ReplaceOccurance: OneFormat: bool

52 August 2008


./WlanNAP/X/IPv4The local IPv4 address of this NAP node.

Access Type: GetOccurance: OneFormat: chrAllowed values: String in dotted-decimal notation, for example “192.168.100.200”

./WlanNAP/X/IPv4/LocalAddrAccess Type: Get, ReplaceOccurance: OneFormat: chr

./WlanNAP/X/IPv4/NetMaskThe IPv4 network address mask (subnet mask) of this NAP node.

Access Type: Get; ReplacOccurance: OneFormat: chrAllowed values: String in dotted-decimal notation, for example “255.255.255.0”

./WlanNAP/X/IPv4/DefaultGatewaySpecifies the IPv4 address of the default gateway for this NAP node.

Access Type: Get, ReplaceOccurance: OneFormat: chrAllowed values: String in dotted-decimal notation, for example “192.168.100.254”

./WlanNAP/X/IPv4/AutoConfigDefines if automatic IPv4 address configuration is in use by this NAP node.

Access Type: Get, ReplaceOccurance: OneFormat: boolDefault value: True

./WlanNAP/X/IPv4/DNSAccess Type: GetOccurance: OneFormat: Node

./WlanNAP/X/IPv4/DNS/XThis interior node distinguishes DNS Server addresses. Note that there are exactly two such nodes in the current implementation, and these are designated DNS0001 and DNS0002.

Access Type: GetOccurance: ZeroOrN (N=1)Format: Node

53 August 2008


./WlanNAP/X/IPv4/DNS/X/DNSAddrIdentifies the address of a DNS server

Access Type: Get, ReplaceOccurance: OneFormat: chrAllowed values: String in dotted-decimal notation, for example “192.168.100.200”

./WlanNAP/X/IPv6Access Type: GetOccurance: OneFormat: Node

./WlanNAP/X/IPv6/LocalAddrLocal Address IPv6.


./WlanNAP/X/IPv6/AutoConfigDefines if automatic IPv6 address configuration is in use by this NAP.

Access Type: Get, ReplaceOccurance: OneFormat: bool

54 August 2008


Group account settings ./SNAP

Group accounts are used for bearer mobility. For example the Internet group account may have a WLAN account and fall back to a GPRS account when WLAN is out of range.

Internet accounts in general usually need to be in some SNAP account in order to be usable.

Subtree structure

./SNAPAccess Type: GetOccurance: OneFormat: Node

./SNAP/XAccess Type: Add, Delete, GetOccurance: ZeroOrMoreFormat: Node

./SNAP/X/IdAccess Type: GetOccurance: OneFormat: int

SNAP <X>* Id

Name

Iap1*

Iap2*

Iap3*

Iap4*

Iap5*

Iap6*

Iap7*

Iap8*

Iap9*

Iap10*

Iap11*

Iap12*

Iap13*

Iap14*

Iap15*

55 August 2008


./SNAP/X/NameName for the SNAP account.


./SNAP/X/Iap1First IAP in the SNAP (and highest priority), references a value in NAP/X/NapId or WlanNap/X/NapId or 0 if there is no IAP in this position.


./SNAP/X/Iap2Second IAP in the SNAP.


./SNAP/X/Iap3Second IAP in the SNAP.

Access Type: Get, ReplaceOccurance: ZeroOrMoreFormat: int

./SNAP/X/Iap4Access Type: Get, ReplaceOccurance: OneFormat: int

./SNAP/X/Iap5Access Type: Get, ReplaceOccurance: ZeroOrMoreFormat: int



56 August 2008










57 August 2008


Browser settings ./Browser

Subtree structure

./BrowserThis is the root Browser settings node, parent to all Browser settings.


./Browser/AppIDIdentifies the application service available at this access point. This is always set to "W2" for Browser Set-tings.

Access Type: GetOccurance: OneFormat: chrDefault value: “W2”

./Browser/ProviderIDSpecifies a unique server identifier for the management server used in the current management session.

Access Type: GetOccurance: OneFormat: chrDefault value: “Browser”

Browser AppID

ProviderID

Name

PrefConRef

SearchPage

HomePage

Resource <X>* URI

Name

AAuthType?

AAuthName?

AAuthSecret?

ToBmFolder?

LockBm?

BmFolder <X>* Name

FolderPath

LockFolder?

58 August 2008


./Browser/NameAccess Type: GetOccurance: OneFormat: chrDefault value: “Browser"

./Browser/PrefConRefIndicates the preferred linkage to connectivity parameters. This value is used by the browser to indicate the ID of either the default Network Access Point, or the proxy. Value "/NAP/<x>" where <x> is the unnamed node below /NAP. Note that URIs referring to NAPs or Proxies should begin with “/” and not “./”


./Browser/SearchPageThis leaf defines the default search page for the browser. The returned value is an absolute URI. The value, when set, will be treated as an absolute URI.


./Browser/HomePageThis leaf defines default home page for the browser, pointing to a resource in the DM tree. The returned value is an absolute URI. The value, when set, will be treated as an absolute URI.


./Browser/ResourceThe Resource node is a container for available resources (in this case, bookmarks) and their access parameters within the application.


./Browser/Resource/XA placeholder for the bookmarks. This node name is assigned at creation, or dynamically when reading.


59 August 2008


./Browser/Resource/X/URIThe absolute URI of this bookmark.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chr

./Browser/Resource/X/NameA user readable name associated with this bookmark.


./Browser/Resource/X/AAuthTypeThe authentication method to be used when a client accesses this bookmark.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: chrDefault value: “HTTP-BASIC“Allowed values:

./Browser/Resource/X/AAuthNameIdentifies the authentication name (or user name), if any, associated with this bookmark.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: chr

./Browser/Resource/X/AAuthSecretIdentifies the password, if any, associated with this bookmark.


./Browser/Resource/X/ToBmFolderThis leaf describes a DM tree path, for example /Browser/BmFolder/Folder01. This path must be created before setting this leaf value.


Value Description

“HTTP-DIGEST” HTTP digest authentication

“HTTP-BASIC” HTTP basic authentication

60 August 2008


./Browser/Resource/X/LockBmThis leaf indicates whether the current bookmark is locked or unlocked. When locked, the bookmark can-not be changed by the user. The default value of False indicates that the bookmark is unlocked.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: boolDefault value: False

./Browser/BmFolderThis node provides a container for bookmark folders.


./Browser/BmFolder/XA placeholder for bookmark folders. This node name is assigned at creation, or dynamically when reading.


./Browser/BmFolder/X/NameIndicates the name of a bookmark folder.


./Browser/BmFolder/X/FolderPathThis leaf describes a DM tree path, for example /Browser/BmFolder/Folder01. This path must be created before setting this leaf value.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault value: “/” (the root bookmark folder)

./Browser/BmFolder/X/LockFolderIndicates whether the bookmark folder is locked. When locked, the bookmark folder cannot be changed by a user.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: boolDefault value: False

61 August 2008


Proxy settings ./Proxy

The Proxy Management Object is supplied by Symbian OS. Symbian OS supports both WSP and HTTP proxies, but Sony Ericsson supports only HTTP. Therefore care should be taken to set a new proxy up for HTTP.

A ConRef must also be supplied when adding an http proxy

Proxy type should be created as HTTP unless the ServiceName is added as "CL-WSP", "CO-WSP", "CL-SEC-WSP", "CO-SEC-WSP", "CO-SEC-WTA" or "CL-SEC-WTA", or PortNbr as one of 9200, 9201, 9202 or 9203 (which should therefore be avoided).

Subtree structure

./ProxyThis is the root Proxy Settings node, parent to all Proxy settings.


./Proxy/XSpecifies the unique object ID of a Proxy Management Object. Corresponds to a record in the Proxies table.


./Proxy/X/ProxyIdThe numeric identifier of this Proxy object. Corresponds to a record ID in the Proxies table.


Proxy <X>* ProxyId

Name

AddrType?

Addr

Ports? <X>+ PortNbr

Services? <X>+ ServiceName

ConRefs <X>+ ConRef

AuthInfo+ <X>+ AuthPW?

AuthID?

Domains? <X>+ DomainName?

ProxyParams? WAP? WSPVersion?

Startpg?

62 August 2008


./Proxy/X/NameThis is a user readable name of the Proxy object.


./Proxy/X/AddrTypeThe type of proxy address supplied as the Addr leaf node value. If omitted, the type of the Addr node value MUST be "IPv4". In Symbian implementation this field is always "IPv4".

Access Type: Get, ReplaceOccurance: ZeroOrOneFormat: chrDefault value: “IPv4”

./Proxy/X/AddrAddress of the proxy. The type of address is determined by the AddrType node. This node MUST be present in a valid proxy object. Symbian: An IPv4 address or a URL.


./Proxy/X/PortsThis optional interior node lists the ports which can be traversed via this proxy. A port number is defined for each port along with an optional list of services offered by the proxy at that port.

Access Type: Add, GetOccurance: ZeroOrOneFormat: Node

./Proxy/X/Ports/Ports0001This interior node distinguishes the ports opened by this proxy. Only one port is supported per proxy and it must be Ports0001.

Access Type: Add, GetOccurance: OneOrMoreFormat: Node

./Proxy/X/Ports/Ports0001/PortNbrThis leaf node defines the number of a single port which is opened by this proxy.


63 August 2008


./Proxy/X/Ports/Ports0001/ServicesThis optional interior node lists the services offered at the specified port.


./Proxy/X/Ports/Ports0001/Services/Services0001This interior node distinguishes the services offered at the specified port. Only one service node is sup-ported per port and it must be Services0001.

Access Type: Add, GetOccurance: OneOrMoreFormat: Node

./Proxy/X/Ports/Ports0001/Services/Services0001/ServiceNameThis leaf node identifies the name of a single service offered at the specified port. It is not necessary and neither is it advisable to set a value for this node.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault value: “CL-WSP”Allowed values: Note: Sony Ericsson does not support WSP, therefore use of any of the first 6 values in the table will not result in a usable proxy.

Value Description

“CL-WSP” WAP connection-less session service

“CO-WSP” WAP session service

“CL-SEC-WSP” WAP secure connection-less session service

“CO-SEC-WSP“ WAP secure session service

“CO-SEC-WTA“ WAP WTA secure session service (over WSP)

“CL-SEC-WTA“ WAP WTA secure connection-less session service (over WSP)

“OTA-HTTP-TO“ OTA-HTTP service (push), TO-TCP [PushOTA]

“OTA-HTTP-TLS-TO“ OTA-HTTP secure service (push), TO-TCP [PushOTA]

“OTA-HTTP-PO“ OTA-HTTP service (push), PO-TCP [PushOTA]

“OTA-HTTP-TLS-PO“ OTA-HTTP secure service (push), PO-TCP [PushOTA]

64 August 2008


./Proxy/X/ConRefsThis optional interior node lists network access points (NAPs) used by this proxy to reach a network. One proxy could utilize any of several different NAPs.

Access Type: Add, GetOccurance: OneFormat: Node

./Proxy/X/ConRefs/ConRefs0001This interior node distinguishes the connection object identifier nodes. There must be exactly one ConRef node for each of these interior nodes. Only one ConRef is supported per proxy in Symbian implementation and it must be ConRefs0001.

Access Type: Add, GetOccurance: OneFormat: chr

./Proxy/X/ConRefs/ConRefs0001/ConRefThis leaf node identifies one NAP (or other connection object) for this proxy. Each proxy might utilize any of the several different NAPs. Value: for example "/NAP/NAP0001". Note that the value must begin with “/”, not “./”.


./Proxy/X/AuthInfoThis interior node optionally provides authentication credentials to support various forms of proxy authen-tication. It is only available for WSP Proxies and not for HTTP Proxies. WSP Proxies are not supported on Sony Ericsson devices and hence the nodes beneath this are left undocumented.

Access Type: GetOccurance: OneOrMoreFormat: Node

./Proxy/X/DomainsThis is only available for WSP proxies and not for HTTP proxies. WSP proxies are not supported on Sony Ericsson devices and hence the nodes beneath this are left undocumented.


./Proxy/X/ProxyParamsOnly applicable to WSP proxies and hence not supported for Symbian based Sony Ericsson devices. The nodes underneath are therefore not documented.


65 August 2008


SyncML DM accounts ./SyncML/DMAcc

Subtree structure

./SyncML/DMAccThis node is the common parent to all SyncML DM account nodes.


./SyncML/DMAcc/XA placeholder for one or more DM accounts (profiles). This node name must be assigned by the server at bootstrap.

Access Type: Add, Delete, GetOccurance: ZeroOrMoreFormat: Node

./SyncML/DMAcc/X/AddrStores addresses of different kinds. The type of address stored is specified by the value of DMAcc/x/AddrType node below.

Note: The PortNbr value (see below) is stored as part of the DMAcc/x/Addr node value. However, its value is set and retrieved independently.


DMAcc <X>* Addr

AddrType

PortNbr

ConRef

ServerId

ServerPW

ServerNonce

UserName

ClientPW

ClientNonce

AuthPref?

Name?

66 August 2008


./SyncML/DMAcc/X/AddrTypeThis node specifies the format and interpretation of the DMAcc/x/Addr node value above. The value is encoded as an inline string that represents a numerical value, as specified in the table below.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault Value: “1”Allowed values: “1” = HTTP

./SyncML/DMAcc/X/PortNbrThis specifies the port number to use. This must be a decimal number within the range of a 16-bit unsigned integer.

As there is no separate storage for the PortNbr value, it is stored as part of the DMAcc/x/Addr node value. However, its value is set and retrieved independently.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chrAllowed values: Decimal number within the 16-bit unsigned integer range.

./SyncML/DMAcc/X/ConRefThis node is used to point to connectivity information stored elsewhere in the device. This is needed in order to locate connectivity information stored separately from the SyncML DM management object. Value "/NAP/<x>" where <x> is the unnamed node below /NAP.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chrAllowed values: a URI to a NAP, for example /NAP/NAP001, or the value "INTERNET" for default connec-tion. Note that URIs must begin with “/”, not “./”.

./SyncML/DMAcc/X/ServerIdThis node stores the server identifier for the current SyncML DM account (profile). This value is set at bootstrap and cannot be changed in a regular SyncML DM session (no Replace command can be defined for this node).


./SyncML/DMAcc/X/ServerPWThis node holds an encrypted version of the password or secret that the server uses to authenticate itself to the client. The password can be changed during a normal SyncML DM session, but cannot be read (no Copy or Get commands can be defined for this node).

Access Type: Add, ReplaceOccurance: OneFormat: chr

67 August 2008


./SyncML/DMAcc/X/ServerNonceThis node stores the next nonce value that the server will use to authenticate itself to the client.

Access Type: Add, ReplaceOccurance: OneFormat: bin

./SyncML/DMAcc/X/UserNameThis node holds the name of the user or device for use in SyncML DM authentication.


./SyncML/DMAcc/X/ClientPWThis node holds an encrypted version of the password or secret that the client uses to authenticate itself to the server. The password can be changed during a normal SyncML DM session, but cannot be read (no Copy or Get commands can be defined for this node).

Access Type: Add, ReplaceOccurance: OneFormat: chr

./SyncML/DMAcc/X/ClientNonceThis node stores the next nonce value that the client will use to authenticate itself to the server.

Access Type: Add, ReplaceOccurance: OneFormat: bin

./SyncML/DMAcc/X/AuthPrefThis is an optional node whose possible values are the names of possible SyncML authentication types. The authentication types allowed are shown in the table below.

Access Type: Add, Delete, Get, ReplaceOccurance: ZeroOrOneFormat: chrAllowed values:

Value Authentication type

“syncml:auth-basic” Basic

“syncml:auth-md5” md5

“syncml:auth-MAC” HMAC

68 August 2008


./SyncML/DMAcc/X/NameThis is an optional node used to store the user displayable name for the current SyncML DM account (pro-file).

Access Type: Add, Delete, Get, ReplaceOccurance: ZeroOrOneFormat: chrDefault value: ““ (an empty string)

OMA Data Sync accounts ./SyncML/DSAcc

Subtree structure

./SyncML/DSAccAccess Type: GetOccurance: OneFormat: Node

./SyncML/DSAcc/XAccess Type: Add, Delete, Get, ReplaceOccurance: ZeroOrMoreFormat: Node

./SyncML/DSAcc/X/AppIDAccess Type: GetOccurance: OneFormat: chrDefault value: “w5”Allowed values: “w5”

DSAcc <X>* AppID

Name

ToConRef <X>* ConRef

AppAddr <X>+ Addr

AddrType

PortNbr?

AppAuth <X>* AAuthLevel

AAuthType

AAuthName

AAuthSecret

AAuthData

Resource <X>+ AAccept

URI

Name

CliURI

69 August 2008


./SyncML/DSAcc/X/NameUser readable name of the Data Sync account.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault value: A zero length string, ““

./SyncML/DSAcc/X/ToConRefAccess Type: Add, GetOccurance: OneFormat: Node

./SyncML/DSAcc/X/ToConRef/XThe node can not be added unless a corresponding AppAddr node is also added. The unnamed node must have an AppAddr unnamed node with the same value. When an AppAddr unnamed node is added, the corresponding ToConRef unnamed node will exist. To delete a ToConRef unnamed node, the corre-sponding AppAddr unnamed node must be deleted.

Access Type: Add, Get, ReplaceOccurance: ZeroOrMoreFormat: NodeDefult value: For a Get = “ConRef”

./SyncML/DSAcc/X/ToConRef/X/ConRefThe value maps to either TO-NAPID or TO-PROXY. If the reference is to an IAP, then a link to an existing IAP must be supplied. If the reference is to a proxy, then the full address of the proxy is expected, for example, http://www.symbian.com:21


./SyncML/DSAcc/X/AppAddrAccess Type: Add, GetOccurance: OneFormat: Node

./SyncML/DSAcc/X/AppAddr/XWhen an AppAddr unnamed node is added, ToConRef and AppAuth unnamed nodes with the same node name will also exist. When an AppAddr unnamed node is deleted, the corresponding ToConRef and AppAuth unnamed nodes will also be deleted.

Access Type: Add, Delete, Get, ReplaceOccurance: OneOrMoreFormat: NodeDefault value: For a Get = "Addr/AddrType"

70 August 2008


./SyncML/DSAcc/X/AppAddr/X/AddrThe value of this must be a valid (full) URL, for example http://www.symbian.com and not www.sym-bian.com


./SyncML/DSAcc/X/AppAddr/X/AddrType

Access Type: Add, GetOccurance: OneFormat: chrAllowed values: “HTTP”, “WSP”, “IR”, “BT”, “USB”

./SyncML/DSAcc/X/AppAddr/X/PortNbr

Access Type: Add, Delete, Get, ReplaceOccurance: ZeroOrOneFormat: int

./SyncML/DSAcc/X/AppAuthAccess Type: Add, GetOccurance: OneFormat: NodeDefault value: "CLIENT/APPSRV" unless one or both of the unnamed node values has been replaced or an AppAddr unnamed node exists.

./SyncML/DSAcc/X/AppAuth/XIf the AAuthLevel leaf node is not added, then the node can not be added unless a corresponding AppAddr node is also added. The unnamed node must have an AppAddr unnamed node with the same value. In this case, the leaf node values are mapped to transport properties. This mapping is dependant on the properties for that transport type (AddrType).

When an AppAddr unnamed node is added, then the corresponding AppAuth unnamed node will exist.

To delete an AppAuth unnamed node (except for APPSRV or CLIENT nodes), the corresponding AppAddr node must be deleted.

Access Type: Add, Get, ReplaceOccurance: ZeroOrMoreFormat: NodeDefault value: For a Get = "AAuthLevel/AAuthType/AAuthName/AAuthSecret/AAuthData"

71 August 2008


./SyncML/DSAcc/X/AppAuth/X/AAuthLevelAPPSRV, CLIENT and OBEX are supported.

If AAuthLevel is not given then the AppAuth settings will be assumed to relate to an AppAddr with the same unnamed node value.

Access Type: Add, GetOccurance: OneFormat: chrDefault value: A zero length string, ""

./SyncML/DSAcc/X/AppAuth/X/AAuthTypeThis setting is only valid where the AAuthLevel is either "APPSRV" or "CLIENT". Only "BASIC" and "DIGEST" are available, all other types are not available. The highest authentication type for the APPSRV and CLIENT settings is stored and used. There is no equivalent transport (OBEX) property for this leaf node.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault value: Where AAuthLevel is APPSRV or CLIENT the default value is "DIGEST". Otherwise a zero length string, "".

./SyncML/DSAcc/X/AppAuth/X/AAuthNameIf this setting refers to an AppAddr node:

• For AddrType HTTP and WSP, the setting will access the Username property.• For IR, BT and USB there is no equivalent property.• Otherwise (not an AppAddr node), for APPSRV node it sets the server id and for CLIENT the client user

name.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault value: A zero length string, ""

./SyncML/DSAcc/X/AppAuth/X/AAuthSecretIf this setting refers to an AppAddr node then the setting will access the Password property. Otherwise, for APPSRV node the server password and for CLIENT node the client password.

Access Type: Add, ReplaceOccurance: OneFormat: chrDefault value: A zero length string, ""

72 August 2008


./SyncML/DSAcc/X/AppAuth/X/AAuthDataIf this setting refers to an AppAddr node:

• For AddrType WSP, the setting will access the TransportSecurity property.• For AddrType IR, BT and USB, the setting will access the Security property.• In all cases 0 = False and 1 = True.• For HTTP there is no equivalent property.• Otherwise, if it refers to an APPSRV or CLIENT node it sets NONCE for CLIENT/APPSVR respectively.

Access Type: Add, ReplaceOccurance: OneFormat: binDefault value: A zero length string, ""

./SyncML/DSAcc/X/ResourceAccess Type: Add, GetOccurance: OneFormat: Node

./SyncML/DSAcc/X/Resource/XThe unnamed node will not be added until the AAccept leaf node has been added and the value of the leaf node has been validated. Addition of other nodes is acceptable before the addition of the AAccept leaf node, but no other commands can be sent as this will cause the addition of the unnamed node to fail.

Access Type: Add, Delete, Get, ReplaceOccurance: OneOrMoreFormat: NodeDefault value: For a Get = "AAccept/URI/Name/CliURI"

./SyncML/DSAcc/X/Resource/X/AAcceptThe MIME type must have a valid Data Provider on the ME. Where multiple Data Providers exist on the ME, the first Data Provider for the MIME type will be used. Once set, the AAccept value cannot be changed, a new Resource must be added and the old one deleted. The unnamed node will not be added until this leaf node value has been received and validated.

When the value of this node is fetched it is not guaranteed to match the added value.


./SyncML/DSAcc/X/Resource/X/URIAccess Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault Value: A zero length string, "".

73 August 2008


./SyncML/DSAcc/X/Resource/X/NameAccess Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault Value: A zero length string, "".

./SyncML/DSAcc/X/Resource/X/CliURIAccess Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault Value: A zero length string, "".

74 August 2008


Network settings ./NAP

Subtree structure

./NAPThis is the root Network Settings node, parent to all Network settings.


./NAP/XPlaceholder node.


NAP <X>* NapId

Name

AuthInfo? AuthType

AuthName?

AuthSecret?

AddrType?

Addr?

Linger?

IPv4? LocalAddr?

NetMask?

DefGW?

AutoConfig?

DNS? <X>* DNSAddr?

IPv6? LocalAddr?

AutoConfig?

NetworkId?

BearerType?

Bearer? 3GPPPS? PDPType?

3GPPCS? CallType?

LinkSpeed?

UseCB?

CBNbr?

UsePTxtLog?

ModemInit?

CDMA? MaxNumRetry?

FirstRetryTimeout?

ReRegThreshold?

TBit?

Ext? Symbian? BearerId?

ServiceId?

75 August 2008


./NAP/X/NapIdThe numeric identifier of this NAP object.

Access Type: GetOccurance: OneFormat: int

./NAP/X/NameHuman readable name of this NAP object.


./NAP/X/AuthInfoThis interior node provides authentication information for this NAP definition.


./NAP/X/AuthInfo/AuthTypeSpecifies the authentication type used for this NAP instance.

Access Type: Get, ReplaceOccurance: OneFormat: chrAllowed values: “PAP”, “CHAP”

./NAP/X/AuthInfo/AuthNameSpecifies the authentication name used for this NAP instance.


./NAP/X/AuthInfo/AuthSecretSpecifies the authentication secret (password) used for this NAP instance.


76 August 2008


./NAP/X/AddrTypeSpecifies the type of address supplied by the Addr node.

Access Type: GetOccurance: ZeroOrOneFormat: chrAllowed values: "E164", "APN"

./NAP/X/AddrThis leaf node represents the connection address of this NAP (as opposed to a protocol address) and will represent either a telephone number (for address type E164) or a GPRS APN.


./NAP/X/LingerThis leaf node determines how long a connection should be maintained when there is no network activity. The value supplied is in seconds.


./NAP/X/IPv4Interior node, which defines the IPv4 address configuration of this NAP.


./NAP/X/IPv4/LocalAddrThe local IPv4 address of this NAP node.

Access Type: Get, ReplaceOccurance: ZeroOrOneFormat: chrAllowed values: String in dotted-decimal notation, for example, “192.168.100.200”.

./NAP/X/IPv4/NetMaskThe IPv4 network address mask (also known as subnet mask) of this NAP node.


77 August 2008


./NAP/X/IPv4/DefGWSpecifies the IPv4 address of the default gateway for this NAP node.


./NAP/X/IPv4/AutoConfigDefines if automatic IPv4 address configuration is in use by this NAP node.

Access Type: Get, ReplaceOccurance: ZeroOrOneFormat: bool

./NAP/X/IPv4/DNSThere are exactly 2 child nodes, which must be named DNS001 and DNS002


./NAP/X/IPv4/DNS/XDNS001 or DNS002.

Access Type: GetOccurance: ZeroOrMoreFormat: Node

./NAP/X/IPv4/DNS/X/DNSAddrIdentifies the address of a DNS Server.


./NAP/X/IPv6Interior node, which defines the IPv6 address configuration of this NAP.


78 August 2008


./NAP/X/IPv6/LocalAddrThe local IPv6 address of this NAP node.


./NAP/X/IPv6/AutoConfigDefines if automatic IPv6 address configuration is in use by this NAP node.


./NAP/X/NetworkIdA text string used to categorize NAP definitions. Altering this value merely changes the name for this NAP definition. It has no effect on any other parameters. It is not advisable to modify this value.


./NAP/X/BearerTypeThis leaf node determines the type of bearer used by this NAP definition. When BearerType is set or replaced then all bearer specific information previously associated with the NAP is lost. So it is important to set this value before setting up other aspects of the NAP.

Symbian OS supports the value "CDMA" but Sony Ericsson does not. However some NAP types which are supported by Sony Ericsson but not by Symbian may show up as "CDMA" in the DM tree even though they are not in fact CDMA accounts.

Access Type: Get, ReplaceOccurance: ZeroOrOneFormat: chrAllowed values: "3GPPPS", "3GPPCS"

./NAP/X/BearerThis interior node determines the type of Bearer and any bearer specific extensions used by this NAP def-inition.


79 August 2008


./NAP/X/Bearer/3GPPPSThis interior node specifies settings for the 3GPP Packet Switched bearer used by this NAP instance. If the value of the BearerType leaf node is not "3GPPPS", this node cannot be accessed.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: Node

./NAP/X/Bearer/3GPPPS/PDPTypeThis leaf node determines 3GPP Packet Data Type.

Access Type: Get, ReplaceOccurance: ZeroOrOneFormat: chrAllowed values: "IPv4", "IPv6", "PPP"

./NAP/X/Bearer/3GPPCSThis interior node specifies settings for the 3GPP Circuit Switched bearer used by this NAP instance. If the value of the BearerType leaf node is not "3GPPCS", this node cannot be accessed.


./NAP/X/Bearer/3GPPCS/CallTypeThis leaf node determines the call type used by this NAP definition.

Access Type: GetOccurance: ZeroOrOneFormat: chrAllowed values: "CSD", "HSCSD"

./NAP/X/Bearer/3GPPCS/LinkSpeedThis leaf node determines the link speed (both directions) used by this NAP definition.

Access Type: Get, ReplaceOccurance: ZeroOrOneFormat: chrAllowed values: "AutoBaud", "4800", "9600", "14400", "28800", "32000", "43200"

./NAP/X/Bearer/3GPPCS/UseCBThis leaf node defines if callback is in use. Set to true if callback is in use, False otherwise.


80 August 2008


./NAP/X/Bearer/3GPPCS/CBNbrThis leaf node determines the call number used for callback, by this NAP definition.


./NAP/X/Bearer/3GPPCS/UsePTxtLogThis leaf node determines plain text authentication is used by this NAP definition. Set to True if clear text authentication is in use, False otherwise.


./NAP/X/Bearer/3GPPCS/ModemInitThis leaf node determines Modem initialisation parameters used by this NAP definition.


./NAP/X/Bearer/CDMAThis interior node specifies settings for the CDMA bearer used by this NAP instance. If the value of the BearerType leaf node is not "CDMA", this node cannot be accessed.


./NAP/X/Bearer/CDMA/MaxNumRetryThis leaf node determines the maximum number of retries for Mobile IP registration.


./NAP/X/Bearer/CDMA/FirstRetryTimeoutDescription: This leaf node defines the elapsed time, in units of 250ms, between the first and second MobileIP Registration Requests, when no Registration Reply has been received.


81 August 2008


./NAP/X/Bearer/CDMA/ReRegThresholdThis leaf node defines the time, in minutes, before registration expiry that the device will attempt to rereg-ister.

Access Type: Get, ReplaceOccurance: ZeroOrOneFormat: intAllowed values: 1 – 63

./NAP/X/Bearer/CDMA/TBitThis leaf node defines if Reverse Tunnelling is required. Set to True if Reverse Tunnelling is required, False otherwise.


./NAP/X/ExtA text string used to categorize NAP definitions. Altering this value merely changes the name for this NAP definition. It has no effect on any other parameters.


./NAP/X/Ext/SymbianThis interior node specifies Symbian OS specific settings used by this NAP instance.


./NAP/X/Ext/Symbian/BearerIdThis leaf node defines the identifier for the Bearer Table for NAP.

Access Type: GetOccurance: ZeroOrOneFormat: intDefault value: 2

./NAP/X/Ext/Symbian/ServiceIdThis leaf node defines the identifier for the Service Table for NAP.

Access Type: GetOccurance: ZeroOrOneFormat: intDefault value: 1

82 August 2008


Email management object ./Email

Subtree structure

./EmailThis is the root email node, container of all email accounts.


Email <X>* Incoming POP3? AppID?

ProviderID?

Name?

AAccept?

AProtocol?

PrefConRef?

AppAddr <X>+ Addr

AddrType

PortNbr

Service

AppAuth? <X>* AAuthType

AAuthName

AAuthSecret?

Ext? Symbian? AutoSend?

AckRcpt?

DelDisc?

MxMsgSz?

SyncL?

PopL?

DMode?

SOpt?

DMode?

IMAP4? AppID?

ProviderID?

Name?

AAccept?

AProtocol?

PrefConRef?

AppAddr <X>+ Addr

AddrType

PortNbr

Service

AppAuth? <X>* AAuthType

AAuthName

AAuthSecret?

Ext? Symbian? AutoSend?

AckRcpt?

DelDisc?

MSeen?

Idle?

MxMsgSz?

MxAttSz?

MxBodySz?

SMbLim?

SIbLim?

IdleTO?

SRate?

FRate?

DPath?

PathChr?

FIStrat?

SIStrat?

SOpt?

Outgoing SMTP? AppID?

ProviderID?

AAccept?

AProtocol?

PrefConRef?

AppAddr <X>+ Addr

AddrType

PortNbr

Service

AppAuth? <X>* AAuthType?

AAuthName?

AAuthSecret?

EAddr

RAddr

Ext? Symbian? AddVC?

AddSig?

Rcpt?

Alias?

RcAddr?

Enc?

CCSelf?

SOpt?

83 August 2008


./Email/XThe unnamed dynamic node that contains settings related to an email account. Zero or more of these are possible.


./Email/X/IncomingThis node contains nodes relating to incoming email account settings.


./Email/X/Incoming/POP3The tree node that acts as a container of all the POP3 settings, in case the incoming mail connection is specified for a POP3 server.


./Email/X/Incoming/POP3/AppIDThe AppID identifies the type of the application service available from this type of incoming mail service. This value is expected to be globally unique.


./Email/X/Incoming/POP3/ProviderIDThe ProviderID parameter provides the application's unique identifier (in the current scope).


./Email/X/Incoming/POP3/NameSpecifies the user readable identifier/name of the POP3 Account.


84 August 2008


./Email/X/Incoming/POP3/AAcceptThe AAccept parameter lists the content types that the server is able to receive from the client. The value is a string containing comma separated list of content-type specifiers.


./Email/X/Incoming/POP3/AProtocolThe AProtocol indicates the application protocol versions supported by the server. The client application may change its behaviour or modify the settings store based on the version that it may be able to store. The list is expected to be comma separated.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: chrDefault value: “POP3”

./Email/X/Incoming/POP3/PrefConRefThe PrefConRef node value indicates the preferred linkage to connectivity parameters (proxy or network access points). In case of the email account settings, only one NAP address is allowed to be specified per account (however, these may be different for incoming and outgoing portion of the settings). Should be a URI to a node in DM tree, for example, "/NAP/NAP001"


./Email/X/Incoming/POP3/AppAddrThe AppAddr interior node is used to allow multiple server addresses (and related connection properties) to be defined for the email application settings.


./Email/X/Incoming/POP3/AppAddr/XThis is the placeholder for one or more incoming server details. However for the current version of email settings, only one such interior node is allowed.

Access Type: Add, Delete, GetOccurance: OneOrMoreFormat: Node

85 August 2008


./Email/X/Incoming/POP3/AppAddr/X/AddrThe name (IP address, or fully qualified internet domain name) of the server is expected to be specified here.

Access Type: Add, Copy, Get, ReplaceOccurance: OneFormat: chr

./Email/X/Incoming/POP3/AppAddr/X/AddrTypeAddrType node contains the format or content type of the Addr parameter.

Access Type: Add, Copy, Get, ReplaceOccurance: OneFormat: intAllowed values:

./Email/X/Incoming/POP3/AppAddr/X/PortNbrThe PortNbr node contains the port number of the server at which the service is available. The port number is expected to be an integer.

Access Type: Add, Copy, Get, ReplaceOccurance: OneFormat: int

./Email/X/Incoming/POP3/AppAddr/X/ServiceThe service parameter specifies which service is available behind the specified port number.


Value Description

1 The IPv4 formatted address (example "121.123.10.1")

2 The address in the hostname format (example: "pop3.symbian.com")

Value Description

1 PLAIN: No special security features to be expected during communications.

2 SSLSEC: A secure TLS connection will be established directly over a TLS/SSL socket when connecting to the email server.

3 SSLUNSEC: A secure TLS connection will be negotiated over an un-secure TCP socket connection when a connection is being established.

86 August 2008


./Email/X/Incoming/POP3/AppAuthThe AppAuth interior node is a container for authentication information to be used by the email application for authentication of itself (and the user) to the server.


./Email/X/Incoming/POP3/AppAuth/XThe unnamed dynamic node placeholder for holding multiple authentication information sets. However, in the current version of the email application, only one such set of settings is supported for an email account.


./Email/X/Incoming/POP3/AppAuth/X/AAuthTypeThe AAuthType node indicates the authentication method used by the application to contact the receiving server before it can receive emails.

Access Type: Add, Copy, Get, ReplaceOccurance: OneFormat: intDefault value: 1Allowed values:

./Email/X/Incoming/POP3/AppAuth/X/AAuthNameThe AAuthName node indicates the plaintext ID of the user, which has been assigned by the server at the time of creation of the email account.

Access Type: Add, Copy, ReplaceOccurance: OneFormat: chr

./Email/X/Incoming/POP3/AppAuth/X/AAuthSecretThe AAuthSecret node specifies the authentication secret. The format and use of this parameter depend on AAuthType. For APOP mode, this is the shared plain text secret to be used. For "PLAIN" AAuthType, this will be the plain-text password.

Access Type: Add, Copy, ReplaceOccurance: ZeroOrOneFormat: chr

Value Description

1 PLAIN: Plain text authentication.

2 APOP : APOP protocol is used by the incoming mail server for authentica-tion.

87 August 2008


./Email/X/Incoming/POP3/ExtThe Ext node is an interior node where the vendor (application, device or OS vendor) specific information about this particular application is being placed. Usually the vendor extension is identified by vendor spe-cific name under the Ext node.


./Email/X/Incoming/POP3/Ext/SymbianThe Symbian specific email account information that may be managed by a DM server is identified by the contents of this interior node.


./Email/X/Incoming/POP3/Ext/Symbian/AutoSendThis setting is used to specify whether queued emails associated with the same internet access point as the POP3 service will be sent first before logging onto the POP3 server. This is a Boolean setting, where true indicates auto-send is enabled.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: bool

./Email/X/Incoming/POP3/Ext/Symbian/AckRcptThis setting is used to specify whether or not to send a receipt email message to the sender when the email has been received.


./Email/X/Incoming/POP3/Ext/Symbian/DelDiscThis setting is used to specify whether the emails will be deleted from the client on disconnection (not cur-rently used by the email system).


./Email/X/Incoming/POP3/Ext/Symbian/MxMsgSzThe MxMsgSz setting specifies the maximum size of an email message in bytes that is allowed to be downloaded.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: int

88 August 2008


./Email/X/Incoming/POP3/Ext/Symbian/SyncLThe SyncL account setting is used to specify whether or not the POP3 service will synchronise with all emails on the server after connecting, or the maximum number of new messages that will be synchronised if there are new messages on the server.


./Email/X/Incoming/POP3/Ext/Symbian/PopLThis setting is used to specify the currently stored TOP population limit setting. This is used to specify what (if any) is the total number of emails that this client can handle at any one time.


./Email/X/Incoming/POP3/Ext/Symbian/DModeIf disconnected user mode is enabled (true), then the POP3 client MTM will accept message operations, such as deleting messages from a server, while the user is offline. The operations are stored and executed when the user connects again.


./Email/X/Incoming/POP3/Ext/Symbian/SOptThe MailOptions node specifies which parts of an email message to download.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: intAllowed values:

./Email/X/Incoming/IMAP4Access Type: Add, GetOccurance: ZeroOrOneFormat: Node

Value Description

1 Synchronise message headers only.

2 Synchronise complete messages.

89 August 2008


./Email/X/Incoming/IMAP4/AppIDThe AppID identifies the type of the application service available from this type of incoming mail service. This value is expected to be globally unique.


./Email/X/Incoming/IMAP4/ProviderIDThe ProviderID parameter provides the application's unique identifier (in the current scope).


./Email/X/Incoming/IMAP4/NameSpecifies the user readable identifier/name of the IMAP4 Account.


./Email/X/Incoming/IMAP4/AAcceptThe AAccept parameter lists the content types that the server is able to receive from the client. The value is a string containing comma separated list of content-type specifiers.


./Email/X/Incoming/IMAP4/AProtocolThe AProtocol indicates the application protocol versions supported by the server. The client application may change its behaviour or modify the settings store based on the version that it may be able to store. The list is expected to be comma separated.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: chrDefault value: “IMAP4”

./Email/X/Incoming/IMAP4/PrefConRefThe PrefConRef node value indicates the preferred linkage to connectivity parameters (proxy or network access points). In case of the email account settings, only one NAP address is allowed to be specified per account (however, these may be different for incoming and outgoing portion of the settings).


90 August 2008


./Email/X/Incoming/IMAP4/AppAddrThe AppAddr interior node is used to allow multiple server addresses (and related connection properties) to be defined for the email application settings.


./Email/X/Incoming/IMAP4/AppAddr/XThis is the placeholder for one or more incoming server details. However for the current version of email settings, only one such interior node is allowed.


./Email/X/Incoming/IMAP4/AppAddr/X/AddrThe name (IP address, or fully qualified internet domain name) of the server is expected to be specified here.


./Email/X/Incoming/IMAP4/AppAddr/X/AddrTypeAddrType node contains the format or content type of the Addr parameter.


./Email/X/Incoming/IMAP4/AppAddr/X/PortNbrThe PortNbr node contains the port number of the server at which the service is available. The port number is expected to be an integer.


Value Description



91 August 2008


./Email/X/Incoming/IMAP4/AppAddr/X/ServiceThe service parameter specifies which service is available behind the specified port number.


./Email/X/Incoming/IMAP4/AppAuthThe AppAuth interior node is a container for authentication information to be used by the email application for authentication of itself (and the user) to the server.


./Email/X/Incoming/IMAP4/AppAuth/XThe unnamed dynamic node placeholder for holding multiple authentication information sets. However, in the current version of the email application, only one such set of settings is supported for an email account.


./Email/X/Incoming/IMAP4/AppAuth/X/AAuthTypeThe AAuthType node indicates the authentication method used by the application to contact the receiving server before it can receive emails.

Access Type: Add, Copy, Get, ReplaceOccurance: OneFormat: intDefault value: 1Allowed values:

Value Description




Value Description


92 August 2008


./Email/X/Incoming/IMAP4/AppAuth/X/AAuthNameThe AAuthName node indicates the plaintext ID of the user, which has been assigned by the server at the time of creation of the email account.


./Email/X/Incoming/IMAP4/AppAuth/X/AAuthSecretThe AAuthSecret node specifies the authentication secret. The format and use of this parameter depend on AAuthType.


./Email/X/Incoming/IMAP4/ExtThe Ext node is an interior node where the vendor (application, device or OS vendor) specific information about this particular application is being placed. Usually the vendor extension is identified by vendor spe-cific name under the Ext node.


./Email/X/Incoming/IMAP4/Ext/SymbianThe Symbian specific email account information that may be managed by a DM server is identified by the contents of this interior node.


./Email/X/Incoming/IMAP4/Ext/Symbian/AutoSendThis setting is used to specify whether queued emails associated with the same internet access point as the IMAP service will be sent first before logging onto the IMAP server. This is a Boolean setting, where true indicates that auto-send is enabled.


./Email/X/Incoming/IMAP4/Ext/Symbian/AckRcptThis setting is used to specify whether or not to send a receipt email message to the sender when the email has been received.


93 August 2008


./Email/X/Incoming/IMAP4/Ext/Symbian/DelDiscThis setting is used to specify whether the emails will be deleted from the client on disconnection (not cur-rently used by the email system).


./Email/X/Incoming/IMAP4/Ext/Symbian/MSeenThis setting is used to specify whether the IMAP4 seen flag of new messages will be set on the server only when the message has been marked as read, or when the message has been synchronised.


./Email/X/Incoming/IMAP4/Ext/Symbian/IdleThis setting is used to specify whether to use IMAP4 idle mode.


./Email/X/Incoming/IMAP4/Ext/Symbian/MxMsgSzThis setting is used to specify the maximum size of email message in bytes.


./Email/X/Incoming/IMAP4/Ext/Symbian/MxAttSzThis setting is used to specify the maximum attachment size limit (bytes) for the partial fetch of attach-ments in an email message.


./Email/X/Incoming/IMAP4/Ext/Symbian/MxBodySzThis setting is used to specify the maximum body text size limit for the partial fetch of message body. If text/plain part + text/html part (alternative part) is less than the body text size limit then the client only fetches the text/html part else it fetches only text/plain part.


94 August 2008


./Email/X/Incoming/IMAP4/Ext/Symbian/SMbLimThis setting is used to specify whether or not the IMAP4 service will synchronise folders other than the Inbox after connecting, or the maximum number of messages that will be synchronised in the folders.


./Email/X/Incoming/IMAP4/Ext/Symbian/SIbLimThis setting is used to specify whether or not the IMAP4 service will synchronise the Inbox folder after connecting, or the maximum number of new messages that will be synchronised if there are new mes-sages on the server.


./Email/X/Incoming/IMAP4/Ext/Symbian/IdleTOThis setting is used to specify the IMAP IDLE timeout in seconds. A value of zero specifies that the IDLE command will not timeout.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: intDefault value: 1740 seconds (29 minutes)

./Email/X/Incoming/IMAP4/Ext/Symbian/SRateThis setting is used to specify the rate in number of seconds after which the Inbox is refreshed.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: intDefault value: 300 seconds (5 minutes)

./Email/X/Incoming/IMAP4/Ext/Symbian/FRateWhen downloading large attachments, data is requested (fetched) in increments. The larger the fetch size (or fetch rate), fewer fetch commands are sent to the IMAP4 server. This speeds up the attachment down-load rate, but only up to a limit. The limit is network specific. A fetch size that is too large will degrade per-formance shortly after downloading an attachment is cancelled, because the fetched data will still be incoming on the socket after cancellation.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: intDefault value: 20480 bytes (20 KB)

95 August 2008


./Email/X/Incoming/IMAP4/Ext/Symbian/DPathThis setting is used to specify the configured path of the IMAP4 mailbox on the incoming mail server if the user's primary mailbox is not in the Inbox folder.


./Email/X/Incoming/IMAP4/Ext/Symbian/PathChrThis setting is used to specify the character configured to separate hierarchical mailbox names on the IMAP4 server.


./Email/X/Incoming/IMAP4/Ext/Symbian/FIStratThe method for synchronising folder information with the server.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: intDefault value: 2 Allowed values:

./Email/X/Incoming/IMAP4/Ext/Symbian/SIStratsetting is used to specify how the client synchronises its folders with the IMAP4 server.


Value Description

1 Combined Synchronisation. Merge local and remote folder information.

2 Local Synchronisation. Update the local copy of folder information when it is received from remote IMAP4 server at the beginning of the mail session.

3 Remote Synchronisation. Update the remote copy of folder information so that it matches the local folder information.

Value Description

1 Neither. Do not alter local or remote subscription information.

2 Local. Update local copy of subscription information when it is received from the remote IMAP4 server at the beginning of the mail session.

96 August 2008


./Email/X/Incoming/IMAP4/Ext/Symbian/SOptThis setting is used to define which components of a message to fetch when copying or moving from a server.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: intAllowed values:

./Email/X/Incoming/IMAP4/Ext/Symbian/DModeIf disconnected user mode is enabled, then the IMAP4 client MTM will accept message operations, such as deleting messages from a server, while the user is offline. The operations are stored and executed when the user connects again.


./Email/X/OutgoingAccess Type: Add, GetOccurance: OneFormat: Node

./Email/X/Outgoing/SMTPThe tree node that acts as a container of all the SMTP settings, the outgoing mail connection is specified only for an SMTP server.


3 Remote. Update remote copy of subscription information so that it matches the local subscription information.

4 Both. Update remote copy of subscription information so that it matches the local subscription information.

Value Description

1 No size limits.

2 Get message body only.

3 Get message attachments only.

4 Get message body and attachments.

5 Have a cumulative size limit on downloaded parts.

Value Description

97 August 2008


./Email/X/Outgoing/SMTP/AppIDThe AppID identifies the type of the application service available from this type of outgoing mail service. This value is expected to be globally unique.


./Email/X/Outgoing/SMTP/ProviderIDThe ProviderID parameter provides the application's unique identifier (in the current scope).


./Email/X/Outgoing/SMTP/AAcceptThe AAccept parameter lists the content types that the server is able to receive from the client. The value is a string containing comma separated list of content-type specifiers.


./Email/X/Outgoing/SMTP/AProtocolThe AProtocol indicates the application protocol versions supported by the server. The client application may change its behaviour or modify the settings store based on the version that it may be able to store. The list is expected to be comma separated.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: chrDefault value: “SMTP”

./Email/X/Outgoing/SMTP/PrefConRefThe PrefConRef node value indicates the preferred linkage to connectivity parameters (proxy or network access points). In case of the email account settings, only one NAP address is allowed to be specified per account (however, these may be different for incoming and outgoing portion of the settings).


./Email/X/Outgoing/SMTP/AppAddrThe AppAddr interior node is used to allow multiple server addresses (and related connection properties) to be defined for the email application settings.


98 August 2008


./Email/X/Outgoing/SMTP/AppAddr/XThis is the placeholder for one or more incoming server details. However for the current version of email settings, only one such interior node is allowed.


./Email/X/Outgoing/SMTP/AppAddr/X/AddrThe name (IP address, or fully qualified internet domain name) of the server is expected to be specified here.


./Email/X/Outgoing/SMTP/AppAddr/X/AddrTypeAddrType node contains the format or content type of the Addr parameter.


./Email/X/Outgoing/SMTP/AppAddr/X/PortNbrThe PortNbr node contains the port number of the server at which the service is available. The port number is expected to be an integer.


Value Description



99 August 2008


./Email/X/Outgoing/SMTP/AppAddr/X/ServiceThe service parameter specifies which service is available behind the specified port number.


./Email/X/Outgoing/SMTP/AppAuthThe AppAuth interior node is a container for authentication information to be used by the email application for authentication of itself (and the user) to the server.


./Email/X/Outgoing/SMTP/AppAuth/XThe unnamed dynamic node placeholder for holding multiple authentication information sets. However, in the current version of the email application, only one such set of settings is supported for an email account.


./Email/X/Outgoing/SMTP/AppAuth/X/AAuthTypeThe AAuthType node indicates the authentication method used by the application to contact the receiving server before it can receive emails.

Access Type: Add, Copy, Get, ReplaceOccurance: ZeroOrOneFormat: intDefault value: 1Allowed values:

Value Description




Value Description


100 August 2008


./Email/X/Outgoing/SMTP/AppAuth/X/AAuthNameThe AAuthName node indicates the plaintext ID of the user, which has been assigned by the server at the time of creation of the email account.


./Email/X/Outgoing/SMTP/AppAuth/X/AAuthSecretThe AAuthSecret node specifies the authentication secret. The format and use of this parameter depend on AAuthType.


./Email/X/Outgoing/SMTP/EAddrThis setting is used to specify the configured SMTP email address of the user.


./Email/X/Outgoing/SMTP/RAddrThe ReplyTo address of the outgoing email specifies the reply address of the outgoing emails.


./Email/X/Outgoing/SMTP/ExtThe Ext node is an interior node where the vendor (application, device or OS vendor) specific information about this particular application is being placed. Usually the vendor extension is identified by vendor spe-cific name under the Ext node.


./Email/X/Outgoing/SMTP/Ext/SymbianThe Symbian specific email account information that may be managed by a DM server is identified by the contents of this interior node.


101 August 2008


./Email/X/Outgoing/SMTP/Ext/Symbian/AddVCThis setting is used to specify if the configured email alias (display name) will be sent with outbound email.


./Email/X/Outgoing/SMTP/Ext/Symbian/AddSigThis setting is used to specify whether email messages will have the user's signature text appended to the text of the messages when they are sent.


./Email/X/Outgoing/SMTP/Ext/Symbian/RcptThis setting is used to specify whether outbound email messages will contain a header that requests receipts to be returned to the address identified by RAddr node.


./Email/X/Outgoing/SMTP/Ext/Symbian/AliasThis setting is used to specify the configured email alias (display name) that will be sent with outbound email.


./Email/X/Outgoing/SMTP/Ext/Symbian/RcAddrThis setting specifies the email address to send the receipts to, when receipts are requested with outgo-ing messages.


102 August 2008


./Email/X/Outgoing/SMTP/Ext/Symbian/EncDefines how emails will be encoded when they are sent.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: intDefault value: 1Allowed values:

./Email/X/Outgoing/SMTP/Ext/Symbian/CCSelfDefines an option that allows the user to automatically email themselves a copy of all emails that are sent from the phone using this account.

Access Type: Add, Get, ReplaceOccurance: ZeroOrOneFormat: intDefault value: 1Allowed values:

Value Description

1 Text is encoded using quoted-printable encoding, and all attachments are encoded using BASE64 encoding.

2 Attachments are encoded using UUEncoding algorithm. This method would not normally be used unless the sender was sure that the receiving mail cli-ents don't support MIME.

3 Text parts of the message are sent as MIME TEXT/HTML parts, and are encoded using UTF-8 encoding system. All attachments are encoded using BASE64 encoding. Receiving mail clients that do no support MHTML mail will display the HTML message text to the user including all HTML tags, etc.

4 Each text part of the message is sent as two alternative MIME parts. The first part is sent as plain text using quoted-printable encoding, the second part is sent as a TEXT/HTML part which is encoded using UTF-8 encoding system. All attachments are encoded using BASE64 encoding. This is the standard encoding method if the user wishes to send MHTML mail.

Value Description

1 Do not send self a copy.

2 Send a copy, with the user's address added to the To: address list.

3 Send message with the user's address added to the Cc: address list.

4 Send a copy, with the user's address added to the Bcc: address list.

103 August 2008


./Email/X/Outgoing/SMTP/Ext/Symbian/SOptDefines sending options for new email messages. The option has no direct effect on the SMTP MTM, although messages in the outbox which are marked as 1 or 2 will be appended automatically to the list of messages supplied by the client.


SMS settings ./SMS

Subtree structure

Value Description

1 Send message immediately.

2 Send message when the next connection occurs.

3 Send message only when the user requests this.

SMS Val

ValFmt

Type

StatRep

Enc

Concat

IncReply

RejDup

DelvRep

IncSC

DefSC

AppAddr <X>+ Name

Addr

Ext Symbian Delivery

BAction

Bearer

SDefault

DescLen

SpecMsg

104 August 2008


./SMSThis is the root SMS node, parent to all SMS settings.


./SMS/ValThe validity period for messages (in minutes) sent by the SMS MTM. If the service centre is unable to deliver the SMS message before this time expires, a failure report may be generated by the service centre, and no further attempts will be made to deliver the message to the recipient. Validity period is only used for SMS-SUBMIT, mobile originated messages.

Access Type: Add, Get, ReplaceOccurance: OneFormat: IntDefault value: 10080 minutes (1 week).

./SMS/ValFmtThe format of the specified validity period of the message.

Access Type: Add, Get, ReplaceOccurance: OneFormat: IntDefault value: 3 (Absolute).Allowed values:

./SMS/TypeThe form in which the message should be delivered to the recipient by the service centre.

Access Type: Add, Get, ReplaceOccurance: OneFormat: IntDefault value: 1 Allowed values:

Value Description

1 Enhanced format.

2 Relative format.

3 Absolute format.

Value Description

1 Delivered as SMS message.

2 Delivered as FAX message.

3 Delivered as X.400 message.

4 Delivered as Pager message.

105 August 2008


./SMS/StatRepThis setting governs the way status reports are handled by the SMS system.

Access Type: Add, Get, ReplaceOccurance: OneFormat: chrDefault value: 1 Allowed values:

./SMS/EncSpecify the default character set used in the SMS message. Text is stored in Unicode on the Symbian OS phone and is converted into the appropriate character set when the message is sent.

Access Type: Add, Get, ReplaceOccurance: OneFormat: intAllowed values:

5 Delivered as Internet mail message.

6 Delivered as ERMES paging message.

7 Delivered as Speech message.

Value Description

1 When the reports are ignored.

2 When the reports are put in the inbox and made invisible.

3 When the reports are put in the inbox and made visible.

4 When the reports are deleted.

5 When the reports are put in the inbox and made invisible and the status report is matched against the sent message and its summary info updated.

6 When the reports are put in the inbox and made visible, and the status report is matched against the sent message and its summary info updated.

7 When the reports are deleted and the status report is matched against the sent message and its summary info updated.

Value Description

1 Use 7 Bits per character.

2 Use 8 Bits per character.

3 Use UCS2 type character encoding.

Value Description

106 August 2008


./SMS/ConcatIf true, the UI should pass a long message in one piece to the MTM. If false, it should split the message manually into 140 byte parts.

Access Type: Add, Get, ReplaceOccurance: OneFormat: bool

./SMS/IncReplySpecifies whether the editor should quote the received message at the beginning of the reply message.

Access Type: Add, Get, ReplaceOccurance: OneFormat: boolDefault value: False

./SMS/RejDupIf this is true, the service instructs the SC to reject an SMS-Submit for an SMS still held in the SC that has the same message reference number and same destination address as an previously submitted SMS from the same originating address.


./SMS/DelvRepSpecify whether a status report (TP-SRR in GSM spec 03.40) will be requested from the Service Centre. A value of true indicates that a status report will be requested.


./SMS/IncSCThe boolean flag that indicates whether the reply path (Service Centre address) should be included in the SMS-SUBMIT message (TP-RP in GSM spec 03.40).


./SMS/DefSCThe default SC. This is specified by the URI of the default SC. For example: "./SMS/AppAddr/sc1"


107 August 2008


./SMS/AppAddrAn interior node that contains a list of Service Centres that can be used. However, only one can be used at any one time.


./SMS/AppAddr/XThe SC object at runtime, this is the placeholder for defined service centres. For example, "SC1". One or more of such object can be defined, and then the default set to indicate the one currently used (see previ-ous property/node).

Access Type: Add, Delete, Get, ReplaceOccurance: OneOrMoreFormat: Node

./SMS/AppAddr/X/NameSpecifies a user displayable name for the Service Centre. For example "O2 France".


./SMS/AppAddr/X/AddrThe SC address field specifies the number to use for SMS service.


./SMS/ExtThe extensions node contains additional information, which is by nature vendor specific, that is, it con-tains vendor specific information, not part of the standard settings.


./SMS/Ext/SymbianParts of the extended settings specific to Symbian are placed under this node.


108 August 2008


./SMS/Ext/Symbian/DeliveryThis setting specifies the delivery mode once a message is submitted to be sent.


./SMS/Ext/Symbian/BActionSpecifies whether the SMS bearer setting of the service should be used to update the communications database. If set, this uses the service setting to update the global table SMS_BEARER field.

Access Type: Add, Get, ReplaceOccurance: OneFormat: boolDefault value: False (do not update settings for all messages by updating the comms settings)

./SMS/Ext/Symbian/BearerSpecifies the communications signal protocol/bearer to be used for sending SMS messages.


./SMS/Ext/Symbian/SDefaultSets whether the Service settings should be used to update the internal settings database. If set, this uses the service settings to update the relevant fields in the database, when the user changes settings for a particular message.

Access Type: Add, Get, ReplaceOccurance: OneFormat: boolDefault value: False (the database is not updated)

Value Description

1 Deliver immediately.

2 Deliver on request.

3 Delivery is scheduled for later.

Value Description

1 Packet switched.

2 Circuit switched.

3 Prefer to send packet switched.

4 Prefer to send circuit switched.

109 August 2008


./SMS/Ext/Symbian/DescLenThe maximum length of the message entry description in number of characters.

Access Type: Add, Get, ReplaceOccurance: OneFormat: intDefault value: 32

./SMS/Ext/Symbian/SpecMsgThis setting governs the way status reports are handled by the SMS system.


Value Description

1 When the reports are put in the inbox and made invisible.

2 When the reports are put in the inbox and made visible.

3 When the reports are deleted.

4 When the reports are put in the inbox and made invisible and the status report is matched against the sent message and its summary info updated.

5 When the reports are put in the inbox and made visible, and the status report is matched against the sent message and its summary info updated.

6 When the reports are deleted and the status report is matched against the sent message and its summary info updated.

110 August 2008


MMS settings ./MMS

Subtree structure

./MMSOMA Standardized Management Object for device information.


./MMS/AccountsHolds a collection of MMS Accounts.


MMS Accounts <X>* AppId

Name

Addr

CrMode?

ToProxy? <X>* Proxy

ToNapID? <X>* NapID

Ext Symbian? RcptNotify?

AutoDl?

CrModeRO?

Val?

MxDlSz?

Priority?

HideNum?

ReadRcpt?

DelvRpt?

IncMsg?

FiltAds?

DelvRcpt?

MxRetry?

RetryIntv?

MxSendSz?

FullScrPrev?

DevContClass?

MxImgHt?

MxImgWd?

DefaultAcc

111 August 2008


./MMS/Accounts/XHolds a collection of MMS Accounts.


./MMS/Accounts/X/AppIdThe MMS Application Identifier for this account.


./MMS/Accounts/X/NameThe MMS Account Name.


./MMS/Accounts/X/AddrThe MMS Account Address.


./MMS/Accounts/X/CrModeSpecifies how an MMS client should allow insertion of media items in an MMS.


./MMS/Accounts/X/ToProxyThis is the root proxy node, parent to a list of proxies.


./MMS/Accounts/X/ToProxy/XThis node represents an instance of a proxy.


112 August 2008


./MMS/Accounts/X/ToProxy/X/ProxyThe link to the DDF node of the proxy data.


./MMS/Accounts/X/ToNapIDThis is the root NAP ID node, parent to a list of NAP IDs.


./MMS/Accounts/X/ToNapID/XThis node represents an instance of a NAP ID.


./MMS/Accounts/X/ToNapID/X/NapIDThe link to the DDF node of the NAP ID data. Value "/NAP/<x>" where <x> is the unnamed node below /NAP. Note that the value must begin with “/”, not “./”.


./MMS/Accounts/X/ExtThe extensions node holds any other proprietary settings (vendor specific).


./MMS/Accounts/X/Ext/SymbianThe extensions node holds any symbian specific settings.


./MMS/Accounts/X/Ext/Symbian/RcptNotifyUsed to determine if a notification receipt should be displayed immediately to the user.


113 August 2008


./MMS/Accounts/X/Ext/Symbian/AutoDIUsed to determine if a message should be automatically downloaded, subject to any filter settings.


./MMS/Accounts/X/Ext/Symbian/CrModeROCreation mode read only settings. Determines if a user is allowed to change the creation mode or not.


./MMS/Accounts/X/Ext/Symbian/ValValidity period. Used when sending an MMS to specify how long the message is valid before it is delivered to the recipient. After that, it may be deleted.


./MMS/Accounts/X/Ext/Symbian/MxDISzDetermines the maximum permissible size of an MMS message to be downloaded when using automatic download.


./MMS/Accounts/X/Ext/Symbian/PriorityPriority value for the MMS message.


./MMS/Accounts/X/Ext/Symbian/HideNumDetermines if the user number is hidden when the sent message is displayed.


114 August 2008


./MMS/Accounts/X/Ext/Symbian/ReadRcptDetermines if read reports should be sent back to the network when the user receives an MMS.


./MMS/Accounts/X/Ext/Symbian/DelvRptDetermines if a delivery report should be sent back to the network when the user receives an MMS.


./MMS/Accounts/X/Ext/Symbian/IncMsgDetermines if the original message should be included when replying to an MMS.


./MMS/Accounts/X/Ext/Symbian/FiltAdsDetermines if advertisement MMS messages should be downloaded when using automatic download.


./MMS/Accounts/X/Ext/Symbian/DelvRcptDetermines if delivery notifications should be received.


./MMS/Accounts/X/Ext/Symbian/MxRetryDetermines how many times the application should try to download an MMS message, before it is consid-ered to have failed.


./MMS/Accounts/X/Ext/Symbian/RetryIntvDetermines the length of time between download retry attempts.


115 August 2008


./MMS/Accounts/X/Ext/Symbian/MxSendSzDetermines the maximum MMS message size that can be sent.


./MMS/Accounts/X/Ext/Symbian/FullScrPrevDetermines whether viewing of MMS should be done using full screen.


./MMS/Accounts/X/Ext/Symbian/DevContClassDetermines the content class of the device.


./MMS/Accounts/X/Ext/Symbian/MxImgHtDetermines the image height to be used when sending an MMS message.


./MMS/Accounts/X/Ext/Symbian/MxImgWdDetermines the image width to be used when sending an MMS message.


./MMS/DefaultAccHolds the DM Path for the default MMS Account. This is always ./MMS/Accounts/MMS01 on Sony Ericsson phones, since only one MMS account is supported


116 August 2008


Device information subtree ./DevInfo

Subtree structure

./DevInfoThe root node contains all the child settings and related information.


./DevInfo/ExtThe extensions node. No Items here. May be extended in the future.


./DevInfo/BearerThe bearer node. The bearer specific DevInfo branch. Currently empty.


./DevInfo/DevIdA unique device identifier (the IMEI).


./DevInfo/ManDevice manufacturer.

Access Type: GetOccurance: OneFormat: chrDefault value: “Sony Ericsson”

DevInfo Ext

Bearer

DevId

Man

Mod

DmV

Lang

117 August 2008


./DevInfo/ModDevice model.


./DevInfo/DmVDM Client version of the device. Will be revised when the DDF changes.


./DevInfo/LangThe current language setting of the device.


Detailed device information ./DevDetail

Subtree structure

./DevDetailThe root node contains all the child settings and related information.


DevDetail Ext Symbian Ddf

Bearer

URI MaxDepth

MaxTotLen

MaxSegLen

DevTyp

OEM

FwV

SwV

HwV

LrgObj

118 August 2008


./DevDetail/ExtThe extensions node.


./DevDetail/Ext/SymbianAccess Type: Add, GetOccurance: OneFormat: Node

./DevDetail/Ext/Symbian/DdfThe DDF for the device. In the event of any discrepencies between that and this document, the value in this node is guaranteed to reflect the software on the device.


./DevDetail/BearerThe bearer node. The bearer specific DevDetail branch. Currently empty.


./DevDetail/URIThe tree limitations branch.


./DevDetail/URI/MaxDepthMaximum tree depth supported by the device.


./DevDetail/URI/MaxTotLenMaximum total URI length supported by the device.


119 August 2008


./DevDetail/URI/MaxSegLenMaximum URI segment length supported by the device.


./DevDetail/DevTypType of device.


./DevDetail/OEMName of OEM (Original Equipment Manufacturer).


./DevDetail/FwVThe firmware revision of the device.


./DevDetail/SwVThe software revision of the device.


./DevDetail/HwVThe hardware revision of the device.


./DevDetail/LrgObjLarge object handling supported if value is true.

Access Type: GetOccurance: OneFormat: bool

120 August 2008


Application lifecycle management ./Software

Note:This subtree is not implemented in early releases of the P990, M600, W950.

Subtree structure

./SoftwareThis is the parent node of all the other Application lifecycle management nodes.


./Software/InventoryThe placeholder for all applications and their settings.


./Software/Inventory/NativeThe placeholder for all Native SIS packages and their settings.


./Software/Inventory/Native/XThis node represents an instance of a Native SIS package.


Software Inventory Native <X>* AppName

Vendor

Version

Midlet <X>* AppName

Vendor

Version

Install

Uninstall

121 August 2008


./Software/Inventory/Native/X/AppNameA human readable application name of the Native SIS package.


./Software/Inventory/Native/X/VendorA human readable vendor name of the Native SIS package.


./Software/Inventory/Native/X/VersionA human readable version of the Native SIS package.


./Software/Inventory/MidletThe placeholder for all Java packages and their settings.


./Software/Inventory/Midlet/XThis node represents an instance of a Midlet.


./Software/Inventory/Midlet/X/AppNameA human readable application name of the Midlet.


./Software/Inventory/Midlet/X/VendorA human readable vendor name of the Midlet.


122 August 2008


./Software/Inventory/Midlet/X/VersionA human readable version of the Midlet.


./Software/InstallThis node is used to install an application.

For native applications, a .sis file should be sent in binary format in the data associated with the exec command and with type application/octet-stream.

For java, a jar/jad file should be sent in binary format in the data associated with the exec command and with type application/octet-stream.

The user will be prompted before the installation is allowed to proceed.

Access Type: ExecOccurance: OneFormat: bin

./Software/UninstallThis node is used to uninstall an application. The URI of a node in the inventory (/Software/Inventory) or the UID of a node in the inventory as character data should be passed along with the Exec command.

Access Type: ExecOccurance: OneFormat: chr

123 August 2008

Documents

DG Device Mgmnt - Sony Mobile guidelines | OMA Client Provisioning and Device Management 2 August 2008 This document is published by Sony Ericsson Mobile Communications AB, without