OMA Client Provisioning and Device Management

Developers guidelines

January 2008

OMA Client Provisioning and Device Managementfor Sony Ericsson phones with DM client v.1 – 3

Developers guidelines | OMA Client Provisioning and Device Management

Preface

Purpose of this document

This document describes the implementation of OMA Client Provisioning functionalities in the Sony Ericsson K310, K320, K510, K530, K550, K600, K610, K750, K770, K790, K800, K810, S500, T650, V600, V800, W200, W300, W350, W380, W550, W580, W600, W610, W660, W700, W710, W800, W810, W830, W850, W880, W900, Z310, Z525, Z530, Z550, Z555, Z558, Z610, Z710 and Z800 series of phones, and OMA Device Management in the K310, K320, K510, K530, K550, K600, K610, K750, K770, K790, K800, K810, S500, T650, V600, W200, W300, W350, W380, W550, W580, W600, W610, W660, W700, W710, W800, W810, W830, W850, W880, W900, Z310, Z525, Z550, Z555, Z558, Z610 and Z710 series.

People who can benefit from this document are:

• Software developers.• Operators and service providers.• Content providers

It is assumed that the reader has basic understanding of the OMA Client Provisioning and Device Man-agement technologies and standards.

2 January 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.

14th edition (January 2008)Publication number: EN/LZT 108 8469 R14A


Sony Ericsson Developer World

On www.sonyericsson.com/developer, developers 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.

Trademarks and acknowledgements

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

Bluetooth is a trademark or registered trademark of Bluetooth SIG Inc.

Memory Stick is a trademark of Sony Corporation.

i-mode is a trademark or registered trademark of NTT DoCoMo, Inc.

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

3 January 2008

www.sonyericsson.com/developer


Document conventions

Products

Sony Ericsson phones are referred to in this document by generic names:

Generic names Sony Ericsson phones Device Management

Series client version protocol version

K310 K310i, K310c, K310a 2.0 1.1.2

K320 K320i, K320c 2.0 1.1.2

K510 K510i, K510c, K510a 2.0 1.1.2

K530 K530i 3.3 1.2

K550 K550i, K550c, K550im 3.0K550im: 3.2

1.2

K600 K600i, K608i 1.0 1.1.2

K610 K610i, K610c, K618i, K610im 3.0K610im: 3.2

1.2

K750 K750i, K750c, K758c, D750i 1.0 1.1.2

K770 K770i 3.3 1.2

K790 K790i, K790c, K790a 3.0 1.2

K800 K800i, K800c 3.0 1.2

K810 K810i, K818c 3.0 1.2

S500 S500i 3.0 1.2

T650 T650i, T658c 3.3 1.2

V600 V600i 1.0 1.1.2

V800 V800, Vodafone 802SE N/A N/A

W200 W200i, W200c 2.0 1.1.2

W300 W300i, W300c 2.0 1.1.2

W350 W350i, W350c 3.1 1.2

W380 W380i, W380c 3.1 1.2

W550 W550i, W550c 2.0 1.1.2

W580 W580i, W580c 3.0 1.2

W600 W600i 2.0 1.1.2

W610 W610i, W610c 3.0 1.2

4 January 2008


Terminology and abbreviations

W660 W660i 3.0 1.2

W700 W700i, W700c 1.0 1.1.2

W710 W710i, W710c 3.0 1.2

W800 W800i, W800c 1.0 1.1.2

W810 W810i, W810c, W810a 2.0 1.1.2

W830 W830i, W830c 3.0 1.2

W850 W850i, W850c 3.0 1.2

W880 W880i, W888c 3.0 1.2

W900 W900i, W900c 2.0 1.1.2

Z310 Z310i, Z310a 3.1 1.2

Z525 Z525a 1.0 1.1.2

Z530 Z530i, Z530c 2.0 1.1.2

Z550 Z550i, Z550c, Z550a 2.0 1.1.2

Z555 Z555i, Z555a 3.1 1.2

Z558 Z558i, Z558c 2.0 1.1.2

Z610 Z610i 3.0 1.2

Z710 Z710i, Z710c 3.0 1.2

Z800 Z800i N/A N/A

Generic names Sony Ericsson phones Device Management

Series client version protocol version

APN Access Point Name

CP Client Provisioning. This is the process by which a WAP client is initially configured with connectivity and application access parameters. This is a non-interactive process as opposed to Device Management

CSD Circuit Switched Data

DDF Device Description Framework. This framework prescribes a way for device vendors to describe their devices so that a management system can understand how to manage the device

DM Device Management. A set of OMA (Open Mobile Alliance) standard mechanisms that enables remote interactive configuration of, for example, a phone

GPRS General Packet Radio Service

5 January 2008


Typographical conventions

Code is written in Courier font: <characteristic>...</characteristic>

String values are written inside double quotes: “Off”

GSM Global System for Mobile communications

IMPS Instant Messaging and Presence Service according to OMA standards.

MAC Message Authentication Code

MCC Mobile Country Code

MO Management Object. Management objects are the entities that can be manipulated by management actions carried over the SyncML DM protocol

OMA Open Mobile Alliance. The primary standardization organization for mobile applications. See http://www.openmobilealliance.org

OTA Over The Air

PSD Packet Switched Data

SIM Subscriber Identity Module. In the rest of the document the term SIM is used to denote the traditional GSM SIM as well as the USIM and UICC

SMS Short Message Service

SMS-C Short Message Service Centre

TLS Transport Layer Security

TPS Trusted Provisioning Server

UICC USIM Integrated Circuit Card

UMTS Universal Mobile Telecommunications System

USIM Universal Subscriber Identity Module

WAP Wireless Application Protocol

WBXML WAP Binary Extended Markup Language

WIM Wireless Identification Module

XML Extended Markup Language

6 January 2008

http://www.openmobilealliance.org


Document history

Change history

2006-01-04 Version R1A First edition published on Developer World. This document replaces the Client Provision-ing Developers Guidelines, EN/LZT 108 7987

2006-03-23 Version R2A Second edition. Information about K610, K800, K790, Z530, W300, K510 and K310 series added

2006-05-29 Version R3A Third edition. Information about W700, Z525, Z550, W850, Z710 and W710 series added

2006-08-31 Version R4A Fourth edition. Information about the K618i and the Z610 series added

2006-09-25 Version R5A Fifth edition. Information about W830, Z558 and K320 series, and the Z550a added

2006-12-04 Version R6A Sixth edition. Information about Z310 series added

2007-01-08 Version R7A Seventh edition. Information about W200 series added

2007-02-06 Version R8A Eighth edition. Information about W880, W610, K550 and K810 series added

2007-03-13 Version R9A Ninth edition. Information about W660 series added

2007-03-27 Version R10A 10th edition. Information about W580 series added

2007-06-14 Version R11A 11th edition. Information about K530, S500 and T650 series added

2007-08-21 Version R12A 12th edition. Information about K770 series added

2007-11-06 Version R13A 13th edition. Information about W380 series added

2008-01-20 Version R14A 14th edition. Information about W350 and Z555 series added

7 January 2008


Contents

OMA Client Provisioning ..........................................................................................10Introduction .............................................................................................................11

Supported standards ...........................................................................................11Document reception ................................................................................................12

OTA ......................................................................................................................12SIM ......................................................................................................................12

Security mechanisms ..............................................................................................13Parameters and compliance ...................................................................................13

PXLOGICAL .........................................................................................................13NAPDEF ...............................................................................................................15BOOTSTRAP .......................................................................................................17

Application specific settings ...................................................................................18Browser - APPID “w2” .........................................................................................20MMS - APPID “w4” ..............................................................................................21OMA Data Synchronization - “w5” ......................................................................22OMA Device Management - “w7” .......................................................................25Email, SMTP - “25” ..............................................................................................28Email, POP3 - “110” ............................................................................................29Email, IMAP4 - “143” ...........................................................................................31Streaming (3GPP) - “554” ....................................................................................32IMPS (WV) - wA ...................................................................................................33

General client provisioning examples .....................................................................35WBXML client provisioning document example .....................................................41

XML format ..........................................................................................................41WBXML encoding ................................................................................................42

OMA Device Management .......................................................................................46Introduction .............................................................................................................47

Supported standards and protocols ...................................................................48Preconditions .......................................................................................................48

DM sessions ............................................................................................................49General use case .................................................................................................49

Versioning ................................................................................................................50Authentication .........................................................................................................51Management Objects ..............................................................................................53

The basic tree structure for DM client version 1.0 ...............................................53The basic tree structure for DM client version 2.0 ...............................................53The basic tree structure for DM clients version 3.x .............................................54Device information subtree ./DevInfo ..................................................................55Detailed device information ./DevDetail

(DM clients versions 1.0 and 2.0) ................................................................................56./DevDetail/Ext/Fw/FsVariant ...............................................................................58Detailed device information ./DevDetail

(DM clients version 3.x) ...............................................................................................62SyncML DM accounts (version 1.1.2)

DM clients versions 1.0 and 2.0 ..................................................................................70DM accounts ver. 1.2 (DM clients version 3.x) ....................................................74OMA Data Sync accounts (DM client version 1.0 only) .......................................80Internet accounts (DM client version 1.0 only) ....................................................86Internet accounts (DM client version 2.0 only) ....................................................90

8 January 2008


Internet accounts (DM clients version 3.x only) ...................................................93Packet Switched Data (PSD) accounts

(DM clients versions 2.0 and 3.x) ................................................................................97Circuit Switched Data (CSD) accounts

(DM clients versions 2.0 and 3.0) ..............................................................................101Data accounts (DM client version 1.0 only) .......................................................105FUMO (DM clients versions 2.0 and 3.x only) ...................................................109Browser bookmarks ..........................................................................................111Third-party Java™ application download/installation

(DM clients version 3.x only) .....................................................................................112Internet profile for Java applications .................................................................114Streaming settings .............................................................................................114MMS application settings ..................................................................................116SMS settings .....................................................................................................120Email accounts ..................................................................................................123My Friends (Wireless Village) settings ...............................................................128OMA Data Sync accounts (DM clients versions 2.0 and 3.x) ............................130Sony Ericsson Update Service

(DM clients versions 2.0 and 3.x only) ......................................................................138Dummy tree extensions .....................................................................................139

General DM examples ...........................................................................................141Adding a new CSD data account for clients with DevInfo/DmV = 1.x ...............141Adding a new CS Data account for clients with DevInfo/DmV = 2.x or 3.0 ......143Adding a new PSD data account for clients with DevInfo/DmV = 1.x ...............144Adding a new PSD data account for clients with DevInfo/DmV = 2.x or 3.x .....146Adding a new DM account ................................................................................147Adding a new Email account .............................................................................149Adding a new Internet account ..........................................................................152

Appendix ..................................................................................................................155DM client conformance .........................................................................................156

The W550 DM client implementation conformance ..........................................156

9 January 2008


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.

10 January 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 phones (browser, Email, Streaming, OMA Data Synchronization, Device Management, Wireless Village, and so on). The bootstrap process is initiated when an unconfigured 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, that controls continuous provisioning.

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

Sony Ericsson Symbian OS™ phones (smartphones) also implement interfaces for client provisioning through provisioning documents residing in the internal file system or on a memory card, transferred via Infrared or Bluetooth™, delivered as email attachments, or downloaded from Web pages.

The basis of Client Provisioning is the Provisioning Document (ProvDoc). This is an XML or WBXML encoded message containing a list of characteristics specifying the settings to be provisioned. A ProvDoc can be “pushed” to a phone using a WAP push message. This is normally done by an operator or service provider to configure a phone owned by one of their users.

The OMA CP specification allows ProvDocs to reside on a SIM or UICC card. When the phone starts, the CP framework checks to find out if the smartcard has been used in the phone before, and if not, checks the ProvDocs it contains. If new ProvDocs are detected, they are submitted for processing.

For details on the OMA Client Provisioning v1.1 standard, see 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, see Provisioning Bootstrap 1.1, Open Mobile Alliance, OMA-WAP-PROVBOOT-V1_1, http://www.openmobilealliance.org/.

The details of the bootstrap protocol, particularly the security mechanism, depend on the technology used, but the basic mechanism which uses connectionless WAP Push refers to WAP Push OTA Specifica-tion” WAP Forum, WAP-235-PushOTA, http://www.openmobilealliance.org/. The specification also defines mandatory security mechanisms that can be used with all network technologies.

As an option, the provisioning documents can be delivered via WIM or SIM cards. The Requester interface design for SIM/WIM provisioning is described in Provisioning Smart Card 1.1, Open Mobile Alliance, OMA-WAP-PROVSC-V1_1, http://www.openmobilealliance.org/. There are 3 different storage areas sup-ported by Sony Ericsson Client Provisioning on the card: Bootstrap, Config1 and Config2.

The standards provides rules for how the security mechanisms are to be used and how the provisioning documents delivered through different channels must be combined. There are also rules for how to imple-ment conflict resolution, error handling, proxy selection and parameter prioritization when interpreting the provisioning documents received. The provisioning information received by a WAP client is expected to

11 January 2008

http://www.openmobilealliance.org/







be stored in a configuration context, and there is a mechanism that can be used to control how many con-figuration contexts may be used in the client. These aspects are covered in Provisioning User Agent Behaviour 1.1", Open Mobile Alliance, OMA-WAP-PROVUABV1_1, http://www.openmobilealliance.org/.

Note: To update a provisioning, the Internet Account PXLOGICAL/NAME and Data Account NAPDEF/NAME have to be changed for the installation to succeed. A provisioned document must not be overwrit-ten.

Document reception

Provisioning documents can be made available to the phone via several different methods and media.

OTA

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

Depending on whether the settings were successfully stored in the phone or not, the user receives a report message stating which application the settings were successfully installed for, or if they were not installed.

If the user does not accept the new settings, they are rejected and are not stored in the phone.

See WAP Push OTA Specification” WAP Forum, WAP-235-PushOTA, http://www.openmobilealliance.org. This specification also defines mandatory security mechanisms that can be used with all network technol-ogies.

SIM

Provisioning documents can be delivered via WIM or SIM cards.

This method is usually used for the initial provisioning of new phones and reprovisioning after a master reset. In these situations, provisioning needs to be done to set all basic parameter values correctly.

When the phone starts, differences between configuration settings are compared to those residing on the WIM/SIM. Three different storage areas, Bootstrap, Config1 and Config2 on the smartcard may contain provisioning documents. If the provisioning handling framework detects that provisioning needs to be done, the document on the smartcard is parsed and the read parameter settings are stored in the provi-sioning parameter tree.

The Requester interface design for SIM/WIM provisioning is described in Provisioning Smart Card 1.1, Open Mobile Alliance, OMA-WAP-PROVSC-V1_1, http://www.openmobilealliance.org/.

12 January 2008





Security mechanisms

To prevent non-authorized people from sending malicious content to users, four different alternative secu-rity features have been implemented: UserPin, UserPinMac, NetwPin, and UserNetwPin. See Provisioning Bootstrap 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 only work for the SIM they are created for.

In cases where the security mechanism requires the user to enter a PIN, the user is allowed three attempts to enter the numbers correctly, otherwise the document is rejected.

Parameters and compliance

PXLOGICAL

PXLOGICAL is mapped to the Sony Ericsson “Internet Profile”, allowing the phone to connect to the Inter-net (Web and WAP), and specifying MMS (picture messaging) settings. The Internet profile specifies what protocol, HTTP or WAP, is to be used for connections via proxies and gateways.

Note: Only K600, K750, V600, V800, W700, W800, Z525 and Z800 series can be configured to use the WAP protocol. All other phones in this document require the HTTP protocol (setting the protocol to WAP is treated as an invalid setting).

The table 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 Sony Ericsson Internet/WAP profile

PROXY-ID USED Internal reference to a certain PXLOGICAL within the docu-ment

PROXY-PW NOT USED

PPGAUTH-TYPE NOT USED

PROXY-PROVIDER-ID NOT USED

NAME USED Mandatory. Sets the name for the corresponding Internet pro-file

DOMAIN NOT USED

TRUST NOT USED

13 January 2008



MASTER NOT USED

STARTPAGE USED Sets the URL for the homepage. See also APPID “w2”

BASAUTH-ID USED For start page

BASAUTH-PW USED For start page

WSP-VERSION NOT USED

PUSHENABLED NOT USED

PULLENABLED NOT USED

PXLOGICAL : PXAUTHINFO

USED

PXAUTH-TYPE IGNORED Only supports HTTP-BASIC which is therefore the assumed value

PXAUTH-ID USED “Username” for Internet profile

PXAUTH-PW USED “Password” for Internet profile

PXLOGICAL : PORT USED PORT can either be used in PXLOGICAL or PXPHYSICAL

PORTNBR USED Default 8080. HTTP: Port number other than 9200-9207 used.WAP: 9202, 9203 used (WAP is only valid for K600, K750, V600, V800, W700, W800, Z525 and Z800 series)

SERVICE USED Parameter used CO-WSP or CO-SEC-WSP

PXLOGICAL : PXPHYSICAL

PHYSICAL-PROXY-ID USED An APPLICATION can use this parameter

DOMAIN NOT USED

PXADDR USED GW address if WAP profile. PX address if Internet profile. Can be used for GW address only in K600, K750, V600, V800, W700, W800, Z525 and Z800 series

PXADDRTYPE USED IPV4 and ALPHA interpreted as FQDN supported

PXADDR-FQDN USED Note that PXADDR is mandatory. Set it to a blank string for PXADDR-FQDN to be chosen

WSP-VERSION NOT USED

PUSHENABLED NOT USED

PULLENABLED NOT USED

TO-NAPID Mandatory. Links Internet/WAP profile to Data Account within the same document

PXPHYSICAL : PORT PORT can either be used in PXLOGICAL or PXPHYSICAL


14 January 2008


Note: Only one PXPHYSICAL within a PXLOGICAL characteristic is supported. If a second PXPHYSICAL is included, the corresponding proxy is not created.

NAPDEF

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

Note: CS data is not supported in Z310.

PORTNBR USED Default 8080, HTTP: Port number other than 9200-9207 used.WAP: 9202, 9203 used (WAP is only valid for K600, K750, V600, V800, W700, W800, Z525 and Z800 series)

SERVICE USED Parameter used CO-WSP or CO-SEC-WSP


Characteristic : NAPDEF Mapped to Sony Ericsson Data Account

NAPID USED Links Internet/WAP profile to the Data Account resulting from the current NAPDEF

BEARER USED GSM-CSD and GSM-GPRS. For 3G enabled phones GSM-CSD is mapped to 3G CS and GSM-GPRS is mapped to 3G PS

NAME USED Sets the name for the corresponding Data Account

INTERNET NOT USED

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

NAP-ADDRTYPE USED Only support IPV4 (APN) and E164 (CSD dial string), who are therefore the assumed values

DNS-ADDR USED Parameter uses IPv4 and IPv6

CALLTYPE USED CSD dial type

LOCAL-ADDR USED GPRS IP address

LOCAL-ADDRTYPE USED Parameter uses IPv4

LINKSPEED NOT USED

DNLINKSPEED USED CSD data rate

LINGER USED Only if bearer is GSM-CSD

DELIVERY-ERR-SDU NOT USED

DELIVERY-ORDER NOT USED


15 January 2008


TRAFFIC-CLASS NOT USED

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 NOT USED

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 or CHAP

AUTHNAME USED Data Account username.

AUTHSECRET USED Data Account password

AUTH-ENTITY NOT USED

SPI NOT USED

NAPDEF : VALIDITY NOT USED

COUNTRY NOT USED

NETWORK NOT USED

SID NOT USED

SOC NOT USED

VALIDUNTIL NOT USED


16 January 2008


BOOTSTRAP

The bootstrap process is performed the first time a SIM is inserted in the phone. A restart of the bootstrap process is also done after a master reset. After the phone is bootstrapped, an incoming provisioning doc-ument should be handled according to the table. Note that no overwrite is done without user permission.


Characteristic : BOOTSTRAP

USED

NAME USED Used as title when presenting the document to the user

NETWORK NOT USED

COUNTRY NOT USED

PROXY-ID NOT USED

PROVURL USED The identifier of the context

CONTEXT-ALLOW USED Specifies how many more contexts can be installed

Characteristic : CLIENTIDENTITY

CLIENT-ID USED Fallback value of PXAUTH-ID

Characteristic : VENDORCONFIG

NOT USED

NAME NOT USED

* NOT USED

17 January 2008


Application specific settings

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

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 standards for the respective application.

The following applications references are supported.

Application references:

APPID Application

w2 Browsing

w4 MMS

w5 OMA Data Synchronization

w7 OMA Device Management

wA IMPS (WV)

25 Email, SMTP

110 Email, POP3

143 Email, IMAP4

554 Streaming media (not applicable to all phones)


Characteristic : APPLICATION

All tags in the characteristic APPLICATION are supported. For the behaviour of each application, see the specification for each APPID

APPID Supported

PROVIDER-ID Supported

NAME Supported

AACCEPT Supported

APROTOCOL Supported

TO-PROXY Supported

TO-NAPID Supported

ADDR Supported

APPLICATION : APPADDR

ADDR Supported

ADDRTYPE Supported

18 January 2008


APPADDR : PORT

PORTNBR Supported

SERVICE Supported

APPLICATION : APPAUTH

AAUTHLEVEL Supported WBXML code (0x8D) is not supported in K600, K750, V600, V800, W700, W800, Z525 and Z800 series for APPSRV values. For these Sony Ericsson phone models, inline string values must be used

AAUTHTYPE Supported WBXML codes (0x90, 0x91, 0x92, 0x93) values are not sup-ported in K600, K750, V600, V800, W700, W800, Z525 and Z800 series. For these Sony Ericsson phones, inline string val-ues must be used for the parameter, for example, “DIGEST”, “BASIC”

AAUTHNAME Supported

AAUTHSECRET Supported

AAUTHDATA Supported

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


19 January 2008


Browser - APPID “w2”

OMA Application Characteristic referenceAPPID: w2

APPID type: OMNA

Owner: OMA DM Working Group

Contact: OMA DM Working Group <[email protected]>

Registration version: 1

Registration domesticate: 2003-01-24

Application description: Browser

Description - “w2”Settings for the browser application.

It is possible to set the following via the browser:

• Start page with Title for a PXLOGICAL• Bookmarks

Compliance

ExampleThis example installs two bookmarks and sets the start page for the PXLOGICAL with PROXY-ID equal to www.operator.com.

<characteristic type="APPLICATION">



APPID USED “w2”

TO-PROXY USED Refers to the PXLOGICAL that STARTPAGE can be set for


0 or many

URI USED URL

NAME USED Title of the bookmark or start page. Max size 16

STARTPAGE USED The first RESOURCE with STARTPAGE is set as STARTPAGE for the TO-PROXY

20 January 2008


<parm name="APPID" value="w2"/> <parm name="TO-PROXY" value="www.operator.com" /> <characteristic type="RESOURCE"> <parm name="URI" value="www.operator.com/"/> <parm name="NAME" value="Some Operator WAP Service"/> <parm name="STARTPAGE"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="www.somewhere.com/ "/> <parm name="NAME" value="Bookmark 1"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="www.nowhere.com/ "/> <parm name="NAME" value="Bookmark 2"/> </characteristic></characteristic>

MMS - APPID “w4”


APPID type: OMNA

Owner: OMA Multimedia Messaging Working Group

Contact: OMA Multimedia Messaging Working Group <[email protected]>


Registration timestamp: 2003-01-20

Application description: Multimedia Messaging Service (MMS)

Application reference: Multimedia Messaging Service (MMS) specifications,http://www.wapforum.org/what/technical.htm

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

Compliance



APPID USED “w4”

TO-PROXY USED Reference to PXLOGICAL (“Internet account”)

ADDR USED Service Center

21 January 2008

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


ExampleThis example sets the Service Center and proxy.

characteristic type="APPLICATION"> <parm name="APPID" value="w4"/> <parm name="TO-PROXY" value="mmsproxy"/> <parm name="ADDR" value="http://mms.operator.com"/> </characteristic>

OMA Data Synchronization - “w5”

OMA Application Characteristic reference:APPID: w5

APPID type: OMNA

Owner: Data Synchronization Working Group

Contact: Data Synchronization Working Group <[email protected]>



Application description: Data Synchronization (DS)

Application reference:

• For K600, K750, V600, V800, W800 and Z800 series:OMA DS 1.1 specifications, http://www.openmobilealliance.org/release_program/ds_v112.html

• For other phone models: OMA DS 1.2 specifications, http://www.openmobilealliance.org/release_program/ds_v12.html

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

Description - “w5”Creates a synchronization account.

Compliance


ADDR USED Secondary method for setting Service Center



0 or 1

APPID USED “w5”


22 January 2008

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

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

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


Example<characteristic type="APPLICATION"> <parm name="APPID" value="w5"/> <parm name="NAME" value="Scts"/> <parm name="TO-NAPID" value="INTERNET"/> <characteristic type="APPADDR"> <parm name="ADDR" value="www.someserver.com:80/Sync"/> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="APPSRV"/> <parm name="AAUTHTYPE" value="DIGEST"/> <parm name="AAUTHNAME" value="sync"/> <parm name="AAUTHSECRET" value="cnys"/> </characteristic>*** The following <characteristic> is not applicable to the K600, K750, V600, V800, W700, W800, Z525 and Z800 series:

<characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="CLIENT"/> <parm name="AAUTHTYPE" value="DIGEST"/> <parm name="AAUTHNAME" value="server"/> <parm name="AAUTHSECRET" value="revres"/>

NAME USED The name of the account


ADDR USED The server address

APPLICATION : APPADDR 0 or 1

ADDR USED The server address

APPLICATION : APPAUTH 0 or many

AAUTHLEVEL USED CLIENT or APPSRVNote: K600, K750, V600, V800, W700, W800, Z525 and Z800 series: only APPSRV is supported

AAUTHTYPE USED BASIC, DIGEST or HTTP-BASIC

AAUTHNAME USED Username

AAUTHSECRET USED User password

AAUTHDATA USED


USED 0 or many

URI USED The database URI on the server

AACCEPT USED Must be a MIME type supported by a database

AAUTHNAME USED Username on database level

AAUTHSECRET USED User password on database level


23 January 2008


<parm name="AAUTHDATA" value="nonce"/></characteristic>

***

<characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="APPSRV"/> <parm name="AAUTHTYPE" value="HTTP-BASIC"/> <parm name="AAUTHNAME" value="client"/> <parm name="AAUTHSECRET" value="teilc"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="pb"/> <parm name="AACCEPT" value="text/x-vcard;2.1,text/vcard;3.0"/> <parm name="AAUTHNAME" value="pb"/> <parm name="AAUTHSECRET" value="bp"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="cal"/> <parm name="AACCEPT" value="text/x-vcalendar"/> <parm name="AAUTHNAME" value="cal"/> <parm name="AAUTHSECRET" value="lac"/> </characteristic>

<characteristic type="RESOURCE"> <parm name="URI" value="notes"/> <parm name="AACCEPT" value="text/plain"/> <parm name="AAUTHNAME" value="notes"/> <parm name="AAUTHSECRET" value="seton"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="todo?TODO"/> <parm name="AACCEPT" value="text/x-vcalendar"/> <parm name="AAUTHNAME" value="todo"/> <parm name="AAUTHSECRET" value="odot"/> </characteristic>

*** The following Bookmark synchronization settings <characteristic> is only applicable to phones with DM client ver. 3.x:<characteristic type="RESOURCE"><parm name="URI" value="bkm"/><parm name="AACCEPT" value="text/x-vbookmark"/><parm name="AAUTHNAME" value="bkm"/><parm name="AAUTHSECRET" value="mkb"/>

</characteristic>***

</characteristic>

24 January 2008


OMA Device Management - “w7”


APPID type: OMNA

Owner: Device Management Working Group

Contact: Device Management Working Group <[email protected]>



Application description: Device Management (DM)

Application reference for DM clients versions 1.0 and 2.0, protocol version 1.1.2:

• 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

Application reference for DM clients version 3.x, protocol version 1.2:

• OMA Device Management, version 1.2 specifications,http://www.openmobilealliance.org/release_program/dm_v1_2.html

• “Device Management Tree and Description” specification,http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_2-20050628-C/OMA-TS-DM-TND-V1_2-20050615-C.pdf

• “Device Management Security” specification,http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_2-20060208-C/OMA-TS-DM-Security-V1_2-20060208-C.pdf

• “Device Management Representation Protocol” specification,http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_2-20051216-C/OMA-TS-DM-RepPro-V1_2-20051216-C.pdf

Description - “w7”Creates a Device Management account.

25 January 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/dm_v1_2.html

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

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_2-20050628-C/OMA-TS-DM-TND-V1_2-20050615-C.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_2-20050628-C/OMA-TS-DM-TND-V1_2-20050615-C.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_2-20060208-C/OMA-TS-DM-Security-V1_2-20060208-C.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_2-20060208-C/OMA-TS-DM-Security-V1_2-20060208-C.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_2-20051216-C/OMA-TS-DM-RepPro-V1_2-20051216-C.pdf

http://www.openmobilealliance.org/release_program/docs/CopyrightClick.asp?pck=DM&file=V1_2-20051216-C/OMA-TS-DM-RepPro-V1_2-20051216-C.pdf


Compliance



0 or 1

APPID USED

PROVIDER-ID USED Used as authentication name for the server. Max length 80

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.Note: This parameter is not supported for K600, K750, V600, V800, W700, W800, Z525 and Z800 series

NAME USED Used as displayable name in UI. Max length 50

TO-PROXY USED Reference to PXLOGICAL (“Internet account”). This parameter should be present unless TO-NAPID=”INTERNET” is specified

TO-NAPID USED Refers to NAPDEF used for connection in the account. If value is INTERNET, the default Internet profile is used. This parame-ter should not be present if TO-PROXY is specified

ADDR USED Device Management server URI. Max length 255

APPLICATION : APPADDR USED

ADDR USED If both APPLICATION/ADDR and APPADDR exist, settings are considered invalid

ADDRTYPE NOT SUP-PORTED

Settings are considered invalid if ADDRTYPE is present. This is because only address types IPv4 and Absolute URL are sup-ported, which is implicit when ADDRTYPE is missing (IPv4 and Absolute URL are not valid values of ADDRTYPE).Note: This parameter is ignored in K310, K320, K510, W200, W300, W550, W600, W810, W900, Z530, Z550 and Z558

APPADDR : PORT SUP-PORTED

PORTNBR SUP-PORTED

The port number is ignored in the V800 series

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

26 January 2008


Example<characteristic type="APPLICATION"> <parm name="APPID" value="w7"/> <parm name="PROVIDER-ID" value="servername"/> <parm name="NAME" value="Mgmt Server"/> <parm name="ADDR" value="http://www.mgmtserver.com:8080/manage"/> <parm name="TO-PROXY" value="Op GPRS" /> <characteristic type="APPAUTH"> <parm name="AAUTHTYPE" value="HTTP-DIGEST"/> <parm name="AAUTHNAME" value="name"/> <parm name="AAUTHSECRET" value="secret"/> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="APPSRV"/> <parm name="AAUTHTYPE" value="DIGEST,BASIC"/> <parm name="AAUTHSECRET" value="serversecret"/> <parm name="AAUTHDATA" value="servernonce"/> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="CLIENT"/> <parm name="AAUTHNAME" value="clientname"/> <parm name="AAUTHSECRET" value="clientsecret"/> <parm name="AAUTHDATA" value="clientnonce"/> </characteristic></characteristic>

AAUTHLEVEL USED Protocol ver 1.1.2:CLIENT means authentication data the client sends to the server. APPSRV means authentication data the client receives from the server.Protocol ver 1.2:CLIENT means authentication data the client receives from the server. APPSRV means authentication data the client sends to the server

AAUTHTYPE USED Values can be HTTP-BASIC, HTTP-DIGEST (only valid if AAU-THLEVEL is missing), BASIC, DIGEST and/or HMAC. If multi-ple types are specified in a comma-separated list, there should be no space before or after the commas

AAUTHNAME USED Username. Max length 80

AAUTHSECRET USED Password to use together with AAUTHNAME. Max length 60

AAUTHDATA USED Used to specify nonce. Max length 52


27 January 2008


Email, SMTP - “25”

OMA Application Characteristic referenceAPPID: 25

APPID type: IANA





Application description: Email SMTP settings

Application reference: See RFC 2821 for SMTP definition

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 USED Account name. Max length 20 characters

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

ADDR USED ADDR can either be used in APPLICATION or APPLICA-TION:APPADDR.Outgoing server host name. Max length 31

FROM USED User email address. Note: K600, K750, V600, V800, W800, Z800 series and early W550 and W600 series phones do not support this parameter


ADDR USED ADDR can either be used in APPLICATION or APPLICA-TION:APPADDR.Outgoing server host name. Max length 31

APPADDR : PORT

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

SERVICE USED Empty or STARTTLS


AAUTHNAME USED Username for outgoing server

AAUTHSECRET USED Password for incoming and outgoing server

28 January 2008


Example<characteristic type="APPLICATION"> <parm name="APPID" value="25"/> <parm name="PROVIDER-ID" value="MyMail"/> <parm name="TO-NAPID" value="IAP1"/> <characteristic type="APPADDR"> <parm name="ADDR" value="smtp.mail.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="25"/> <parm name="SERVICE" value="STARTTLS"/> </characteristic> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="username"/> <parm name="AAUTHSECRET" value="password"/> </characteristic></characteristic>

Email, POP3 - “110”


APPID type: IANA





Application description: Email POP3 settings

Application reference: POP3 is defined in RFC1939.

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

Compliance



APPID USED “110”

PROVIDER-ID USED Account name. Max length 20 characters

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

29 January 2008


Example<characteristic type="APPLICATION"> <parm name="APPID" value="110"/> <parm name="TO-PROXY " value="www.operator.com" /> <parm name="PROVIDER-ID" value="MyMail"/> <parm name="TO-NAPID" value="IAP1"/> <characteristic type="APPADDR"> <parm name="ADDR" value="pop.mail.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="110"/> <parm name="SERVICE" value="STARTTLS"/> </characteristic> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="username"/> <parm name="AAUTHSECRET" value="password"/> </characteristic></characteristic>

ADDR USED ADDR can either be used in APPLICATION or APPLICA-TION:APPADDR.Incoming server host name. Max length 31 characters



APPADDR : PORT

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



AAUTHNAME USED Incoming server username. Max length 80 characters

AAUTHSECRET USED Incoming server password. Max length 40 characters


30 January 2008


Email, IMAP4 - “143”


APPID type: IANA





Application description: Email IMAP4 settings

Application reference: IMAP4 is defined in RFC2060

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

Compliance




PROVIDER-ID USED Account name. Max 20 characters

TO-NAPID USED




APPADDR : PORT

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



AAUTHNAME USED Incoming server username. Max length 80 characters

AAUTHSECRET USED Incoming server password. Max length 40 characters

31 January 2008


Example<characteristic type="APPLICATION"> <parm name="APPID" value="143"/> <parm name="PROVIDER-ID" value="MyMail"/> <parm name="TO-NAPID" value="IAP1"/> <characteristic type="APPADDR"> <parm name="ADDR" value="imap.mail.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="143"/> <parm name="SERVICE" value="STARTTLS"/> </characteristic> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="username"/> <parm name="AAUTHSECRET" value="password"/> </characteristic></characteristic>

Streaming (3GPP) - “554”

Note: Streaming is not supported in all phone models in this document.


APPID type: IANA

Owner: Device Management Working Group

Contact: Device Management Working Group <[email protected]>



Application description: 3GPP PSS Streaming using Real Time Streaming Protocol (RTSP)

Application reference:

• 3GPP TS 26.234/www.3gpp.org/ftp/Specs/archive/26_series/26.234• IETF (Internet Engineering Task Force) standards on streaming• RTP (Real-time Transport Protocol)/RTCP (Real-time Transport Control Protocol) RFC1889/

www.ietf.org/rfc/rfc1889.txt• RTSP (Real Time Streaming Protocol) RFC2326/www.ietf.org/rfc/rfc2326.txt• SDP (Session Description Protocol) RFC2327/www.ietf.org/rfc/rfc2327.txt

Description - “554”This is the setting for the streaming application.

32 January 2008


Compliance

Example<characteristic type="APPLICATION"> <parm name="APPID" value="554"/> <parm name="TO-NAPID" value="NAP1"/> <characteristic type="APPADDR"> <parm name="ADDR" value="123.124.125.126"/> <characteristic type="PORT"> <parm name="PORTNBR" value="8080"/> </characteristic> </characteristic></characteristic>

IMPS (WV) - wA

Note: Wireless Village (WV) is not supported in i-mode™ phones, DM client version 3.2.

OMA Application Characteristic referenceAPPID: wA

APPID type: OMNA

Owner: OMA Instant Messaging and presence services Working Group

Contact: OMA IMPS WG <[email protected]>



Application description: Instant Messaging and presence services (IMPS)

Application reference: None




TO-NAPID USED Internet account ID


ADDR USED The proxy address. (Domain name or IP address)

APPADDR : PORT

PORTNBR USED Connection port number to proxy server

33 January 2008


Description - “wA”The following settings are applicable to Wireless Village (“My Friends” in Sony Ericsson generic phones):

• UserID and Domain• Password• Server URL• WAP Profile

When receiving an OMA Client Provisioning with Wireless Village settings, the currently active WV account is updated.

Compliance

Example<characteristic type="APPLICATION"> <parm name="APPID" value="wA"/> <parm name="AACCEPT" value="application/vnd.wv.csp+xml;1.2;1.1;1.0,application/vnd.wv.csp+wbxml;1.2;1.1;1.0"/> <parm name="ADDR" value="https://123.56.78.90"/> <parm name="ADDR" value="http://123.56.78.90"/> <characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="APPSRV"/> <parm name="AAUTHNAME" value="username"/> <parm name="AAUTHSECRET" value="password"/> </characteristic></characteristic>



APPID USED “wA”

AACCEPT USED Used to verify correct WV protocol version and XML coding (XML or WBXML)


ADDR USED 0 or many. The first valid value is used. Address of WV server in URI form. Max 200 characters

APPLICATION : APPADDR 0 or many. The first valid value is used. Lower priority than ADDR

ADDR USED Address of WV server in URI form. Max 200 characters

ADDRTYPE USED Only used to validate that ADDRTYPE is not “E164” (SMS bearer)


AAUTHLEVEL USED Only the value APPSRV is supported

AAUTHNAME USED Complete WV UserID (including domain). Max 50 characters

AAUTHSECRET USED Max 50 characters

34 January 2008


General client provisioning examples

Settings for Browsing (w2) HTTP protocol, MMS (w4), OMA Data Synchronization (w5) and OMA Device Management (w7).<?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.1"> <characteristic type="BOOTSTRAP"> <parm name="PROVURL" value="https://operator"/> <parm name="NAME" value="Operator Settings"/> </characteristic> <characteristic type="PXLOGICAL"> <parm name="PROXY-ID" value="webproxy.operator.com"/> <parm name="NAME" value="Operator Web"/> <characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="proxy 1"/> <parm name="PXADDR" value="webproxy.operator.com"/> <parm name="PXADDRTYPE" value="ALPHA"/> <parm name="TO-NAPID" value="operator.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="8080"/> </characteristic> </characteristic> </characteristic> <characteristic type="PXLOGICAL"> <parm name="PROXY-ID" value="mailproxy.operator.com"/> <parm name="NAME" value="MMS"/> <characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="Operator MMS"/> <parm name="PXADDR" value="mailproxy.operator.com"/> <parm name="PXADDRTYPE" value="ALPHA"/> <parm name="TO-NAPID" value="operator.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="8080"/> </characteristic> </characteristic> </characteristic> <characteristic type="NAPDEF"> <parm name="NAPID" value="operator.com"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAME" value="Operator GPRS"/> <parm name="NAP-ADDRESS" value="mailweb.operator.com"/> <parm name="NAP-ADDRTYPE" value="APN"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"/> <parm name="AUTHNAME" value="user"/> <parm name="AUTHSECRET" value="passwd"/> </characteristic> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w2"/> <parm name="TO-PROXY" value="webproxy.operator.com" />

35 January 2008


<characteristic type="RESOURCE"> <parm name="URI" value="www.operator.com/"/> <parm name="NAME" value="Some Operator WAP Service"/> <parm name="STARTPAGE"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="www.somewhere.com/ "/> <parm name="NAME" value="Bookmark 1"/> <parm name="STARTPAGE"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="www.nowhere.com/ "/> <parm name="NAME" value="Bookmark 2"/> <parm name="STARTPAGE"/> </characteristic> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w4"/> <parm name="TO-PROXY" value="webproxy.operator.com"/> <parm name="ADDR" value="http://mms.operator.com"/> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w5"/> <parm name="NAME" value="Scts"/> <parm name="TO-NAPID" value="INTERNET"/> <characteristic type="APPADDR"> <parm name="ADDR" value="www.someserver.com:80/Sync"/> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="APPSRV"/> <parm name="AAUTHNAME" value="sync"/> <parm name="AAUTHSECRET" value="cnys"/> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="CLIENT"/> <parm name="AAUTHNAME" value="client"/> <parm name="AAUTHSECRET" value="teilc"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="pb"/> <parm name="AACCEPT" value="text/x-vcard;2.1,text/vcard;3.0"/> <parm name="AAUTHNAME" value="pb"/> <parm name="AAUTHSECRET" value="bp"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="cal"/> <parm name="AACCEPT" value="text/x-vcalendar"/> <parm name="AAUTHNAME" value="cal"/> <parm name="AAUTHSECRET" value="lac"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="notes"/>

36 January 2008


<parm name="AACCEPT" value="text/plain"/> <parm name="AAUTHNAME" value="notes"/> <parm name="AAUTHSECRET" value="seton"/> </characteristic> <characteristic type="RESOURCE"> <parm name="URI" value="todo?TODO"/> <parm name="AACCEPT" value="text/x-vcalendar"/> <parm name="AAUTHNAME" value="todo"/> <parm name="AAUTHSECRET" value="odot"/> </characteristic> </characteristic> <characteristic type="APPLICATION"> <parm name="APPID" value="w7"/> <parm name="PROVIDER-ID" value="servername"/> <parm name="NAME" value="Mgmt Server"/> <parm name="ADDR" value="http://www.mgmtserver.com:8080/manage"/> <parm name="TO-PROXY" value="webproxy.operator.com" /> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="httpuser"/> <parm name="AAUTHSECRET" value="httpsecret"/> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="APPSRV"/> <parm name="AAUTHSECRET" value="serversecret"/> <parm name="AAUTHDATA" value="servernonce"/> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHLEVEL" value="CLIENT"/> <parm name="AAUTHNAME" value="clientname"/> <parm name="AAUTHSECRET" value="clientsecret"/> <parm name="AAUTHDATA" value="clientnonce"/> </characteristic> </characteristic></wap-provisioningdoc>

Settings for Browsing (w2) WSP protocol (Example only valid for K600, K750, V600, V800, W700, W800, Z525 and Z800 series)<?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.1"> <characteristic type="BOOTSTRAP"> <parm name="PROVURL" value="https://operator"/> <parm name="NAME" value="Operator Settings"/> </characteristic>

<characteristic type="PXLOGICAL"> <parm name="PROXY-ID" value="webproxy.operator.com"/> <parm name="NAME" value="Operator Web"/> <characteristic type="PXPHYSICAL"> <parm name="PHYSICAL-PROXY-ID" value="proxy 1"/> <parm name="PXADDR" value="111.100.100.111"/>

37 January 2008


<parm name="PXADDRTYPE" value="ALPHA"/> <parm name="TO-NAPID" value="operator.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="9202"/><parm name="SERVICE" value="CO-WSP"/> </characteristic> </characteristic> </characteristic>

<characteristic type="NAPDEF"> <parm name="NAPID" value="operator.com"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAME" value="Operator GPRS"/> <parm name="NAP-ADDRESS" value="mailweb.operator.com"/> <parm name="NAP-ADDRTYPE" value="APN"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"/> <parm name="AUTHNAME" value="user"/> <parm name="AUTHSECRET" value="passwd"/> </characteristic> </characteristic>

<characteristic type="APPLICATION"> <parm name="APPID" value="w2"/> <parm name="TO-PROXY" value="webproxy.operator.com" /> <characteristic type="RESOURCE"> <parm name="URI" value="www.operator.com/"/> <parm name="NAME" value="Some Operator WAP Service"/> <parm name="STARTPAGE"/> </characteristic> </characteristic>

</wap-provisioningdoc>

Settings for Email POP3 (110) and Email SMTP (25)<?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.1"> <characteristic type="NAPDEF"> <parm name="NAPID" value="operator.com"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAME" value="Operator GPRS"/> <parm name="NAP-ADDRESS" value="mailweb.operator.com"/> <parm name="NAP-ADDRTYPE" value="APN"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"/> <parm name="AUTHNAME" value="user"/> <parm name="AUTHSECRET" value="passwd"/> </characteristic>

38 January 2008


</characteristic>

<characteristic type="APPLICATION"> <parm name="APPID" value="110"/> <parm name="PROVIDER-ID" value="MyMail"/> <parm name="TO-NAPID" value="operator.com"/> <characteristic type="APPADDR"> <parm name="ADDR" value="pop.mail.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="110"/> <parm name="SERVICE" value="STARTTLS"/> </characteristic> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="username"/> <parm name="AAUTHSECRET" value="password"/> </characteristic> </characteristic>

<characteristic type="APPLICATION"> <parm name="APPID" value="25"/> <parm name="PROVIDER-ID" value="MyMail"/> <parm name="TO-NAPID" value="operator.com"/> <characteristic type="APPADDR"> <parm name="ADDR" value="smtp.mail.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="25"/> <parm name="SERVICE" value="STARTTLS"/> </characteristic> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="username"/> <parm name="AAUTHSECRET" value="password"/> </characteristic> </characteristic>


Settings for Email POP3 (143) and Email SMTP (25)<?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.1"> <characteristic type="NAPDEF"> <parm name="NAPID" value="operator.com"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAME" value="Operator GPRS"/> <parm name="NAP-ADDRESS" value="mailweb.operator.com"/> <parm name="NAP-ADDRTYPE" value="APN"/> <characteristic type="NAPAUTHINFO"> <parm name="AUTHTYPE" value="PAP"/>

39 January 2008


<parm name="AUTHNAME" value="user"/> <parm name="AUTHSECRET" value="passwd"/> </characteristic> </characteristic>

<characteristic type="APPLICATION"> <parm name="APPID" value="143"/> <parm name="PROVIDER-ID" value="MyMail"/> <parm name="TO-NAPID" value="operator.com"/> <characteristic type="APPADDR"> <parm name="ADDR" value="imap.mail.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="143"/> <parm name="SERVICE" value="STARTTLS"/> </characteristic> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="username"/> <parm name="AAUTHSECRET" value="password"/> </characteristic> </characteristic>

<characteristic type="APPLICATION"> <parm name="APPID" value="25"/> <parm name="PROVIDER-ID" value="MyMail"/> <parm name="TO-NAPID" value="operator.com"/> <characteristic type="APPADDR"> <parm name="ADDR" value="smtp.mail.com"/> <characteristic type="PORT"> <parm name="PORTNBR" value="25"/> <parm name="SERVICE" value="STARTTLS"/> </characteristic> </characteristic> <characteristic type="APPAUTH"> <parm name="AAUTHNAME" value="username"/> <parm name="AAUTHSECRET" value="password"/> </characteristic> </characteristic>


40 January 2008


WBXML client provisioning document example

This example illustrates the encoding of a XML client provisioning document into WBXML format.

XML format

<wap-provisioningdoc version="1.1"><characteristic type="PXLOGICAL"><parm name="PROXY-ID" value="px1" /> <parm name="NAME" value="Internet profile1" /> <characteristic type="PXPHYSICAL"><parm name="PHYSICAL-PROXY-ID" value="GPRS" /> <parm name="PXADDR" value="111.111.111.111" /> <parm name="PXADDRTYPE" value="IPV4" /> <parm name="TO-NAPID" value="NAP1" /> <parm name="TO-NAPID" value="NAP2" />

</characteristic></characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP1" /> <parm name="BEARER" value="GSM-GPRS" /> <parm name="NAME" value="Data account1" /> <parm name="NAP-ADDRESS" value="nap.address.com" /> <parm name="NAP-ADDRTYPE" value="IPV4" />

</characteristic><characteristic type="NAPDEF"><parm name="NAPID" value="NAP2" /> <parm name="BEARER" value="GSM-GPRS" /> <parm name="NAME" value="Data account2" /> <parm name="NAP-ADDRESS" value="nap2.address.com" /> <parm name="NAP-ADDRTYPE" value="IPV4" />

</characteristic>

<characteristic type="APPLICATION"><parm name="NAME" value="DM-account" /><parm name="APPID" value="w7" /> <parm name="PROVIDER-ID" value="provider id" /><parm name="INIT"/><parm name="TO-PROXY" value="px1" /><characteristic type="APPADDR"><parm name="ADDR" value="www.serveraddress.com" /><characteristic type="PORT"><parm name="PORTNBR" value="8080" />

</characteristic></characteristic><characteristic type="APPAUTH"><parm name="AAUTHLEVEL" value="CLIENT" /><parm name="AAUTHTYPE" value="BASIC,DIGEST" />

41 January 2008


<parm name="AAUTHNAME" value="clientname" /> <parm name="AAUTHSECRET" value="clientpw" /> <parm name="AAUTHDATA" value="clientnonce" />

</characteristic><characteristic type="APPAUTH"><parm name="AAUTHLEVEL" value="APPSRV" /><parm name="AAUTHTYPE" value="BASIC" /><parm name="AAUTHSECRET" value="serverpw" /> <parm name="AAUTHDATA" value="servernonce" />

</characteristic></characteristic>


WBXML encoding

Token stream Description

01 Transaction ID

06 PDU Type: Push

2F Header length

1F Value length, “long” indicator

2D Value length

B6 Media type. Assigned number for application/vnd.wap.connectivity-wbxml (0x36) encoded as short integer (0x80)

91 SEC parameter

81 Security method USERPIN (0x01) encoded as short integer (0x80)

92 MAC parameter (0x12) encoded as short integer (0x80)

34 38 31 41 38 43 43 39 34 44 30 39 37 45 36 38 37 41 31 45 34 42 35 38 33 35 33 46 36 32 45 39 31 46 43 39 37 39 46 42

MAC value is "481A8CC94D097E687A1E4B58353F62E91FC979FB", associated PIN is 1234

00 End of string for the encoded MAC value

03 WBXML version 1.3

0B Document Public Identifier: "-//WAPFORUM//DTD PROV 1.0//EN"

6A Character set UTF-8

00 String table length

C5 Element <wap-provisioningdoc> includes attribute and content

45 Attribute version...

03 ...encoded as inline string:

42 January 2008


31 2E 31 "1.1"

00 End of string

01 End of attribute list

C6 51 01 Characteristic (0x06) PXLOGICAL (0x51) includes attribute and content (11xx xxxx) and is ended by an end of attribute list (0x01)

87 15 06 Parameter (0x07) PROXY-ID (0x15) includes attribute but no content (10xx xxxx). The attribute is the value attribute (0x06)

03 70 78 31 00 01 The value is an inline string (0x03) and the string is "px1". (0x00) marks the end of the string. (0x01) marks the end of the attribute list

87 07 06 03 49 6E 74 65 72 6E 65 74 20 70 72 6F 66 69 6C 65 31 00 01

Parameter (0x07) NAME (0x07) with attribute value (0x06), inline string (0x03) "Internet profile1", ended by (0x00). (0x01) marks the end of the attribute list

C6 52 01 Characteristic PXPHYSICAL

87 2F 06 03 47 50 52 53 00 01

Parameter PHYSICAL-PROXY-ID carrying the inline string "GPRS"

87 20 06 03 31 31 31 2E 31 31 31 2E 31 31 31 2E 31 31 31 00 01

Parameter PXADDR carrying the inline string "111.111.111.111"

87 21 06 85 01 Parameter PXADDRTYPE carrying the value IPV4 (0x85)

87 22 06 03 4E 41 50 31 00 01

Parameter TO-NAPID carrying the inline string "NAP1"

87 22 06 03 4E 41 50 32 00 01

Parameter TO-NAPID carrying the inline string "NAP2"

01 End of characteristic PXPHYSICAL

01 End of characteristic PXLOGICAL

C6 55 01 Characteristic NAPDEF

87 11 06 03 4E 41 50 31 00 01

Parameter NAPID carrying the inline string "NAP1"

87 10 06 AB 01 Parameter BEARER carrying the value GSM-GPRS

87 07 06 03 44 61 74 61 20 61 63 63 6F 75 6E 74 31 00 01

Parameter NAME carrying the inline string "Data account1"

87 08 06 03 6E 61 70 2E 61 64 64 72 65 73 73 2E 63 6F 6D 00 01

Parameter NAP-ADDRESS carrying the inline string "nap.address.com"

87 09 06 85 01 Parameter NAP-ADDRTYPE carrying the value IPV4

01 End of characteristic NAPDEF

C6 55 01 Characteristic NAPDEF


43 January 2008


87 11 06 03 4E 41 50 32 00 01

Parameter NAPID carrying the inline string "NAP2"

87 10 06 AB 01 Parameter BEARER carrying the value GSM-GPRS

87 07 06 03 44 61 74 61 20 61 63 63 6F 75 6E 74 32 00 01

Parameter NAME carrying the inline string "Data account2"

87 08 06 03 6E 61 70 32 2E 61 64 64 72 65 73 73 2E 63 6F 6D 00 01

Parameter NAP-ADDRESS carrying the inline string "nap2.address.com"

87 09 06 85 01 Parameter NAP-ADDRTYPE carrying the value IPV4

01 End of characteristic NAPDEF

C6 Characteristic…

00 01 Code page switch (0x00) to code page (0x01)

55 ...APPLICATION (0x55 at code page 1)

01 End of attribute list

87 Parameter…

00 00 Code page switch (0x00) to code page 0

07 06 03 44 4D 2D 61 63 63 6F 75 6E 74 00 01

...NAME carrying the inline string "DM-account"

87 00 01 36 00 00 06 03 77 37 00 01

Parameter APPID (0x36 at code page 1) carrying the inline string "w7"

87 00 01 38 00 00 06 03 70 72 6F 76 69 64 65 72 20 69 64 00 01

Parameter PROVIDER-ID carrying the inline string "provider id"

87 05 03 49 4E 49 54 00 01

Parameter with name (0x05) defined by inline string (0x03) "INIT"

87 00 01 39 00 00 06 03 70 78 31 00 01

Parameter TO-PROXY carrying the inline string "px1"

C6 00 01 56 01 Characteristic APPADDR

87 34 00 00 06 03 77 77 77 2E 73 65 72 76 65 72 61 64 64 72 65 73 73 2E 63 6F 6D 00 01

Parameter ADDR carrying the inline string "www.serveraddress.com"

C6 53 01 Characteristic PORT

87 23 06 03 38 30 38 30 00 01

Parameter PORTNBR carrying the inline string 8080

01 End of characteristic PORT

01 End of characteristic APPADDR


44 January 2008


C6 00 01 57 01 Characteristic APPAUTH

87 30 00 00 06 03 43 4C 49 45 4E 54 00 01

Parameter AAUTHLEVEL carrying the inline string "CLIENT"

87 00 01 33 00 00 06 00 01 92 90 93 01

Parameter AAUTHTYPE carrying the values BASIC,DIGEST

87 31 00 00 06 03 63 6C 69 65 6E 74 6E 61 6D 65 00 01

Parameter AAUTHNAME carrying the inline string "clientname"

87 00 01 32 00 00 06 03 63 6C 69 65 6E 74 70 77 00 01

Parameter AAUTHSECRET carrying the inline string "clientpw"

87 00 01 2F 00 00 06 03 63 6C 69 65 6E 74 6E 6F 6E 63 65 00 01

Parameter AAUTHDATA carrying the inline string "clientnonce"

01 End of characteristic APPAUTH

C6 00 01 57 01 Characteristic APPAUTH

87 30 00 00 06 00 01 8D 01

Parameter AAUTHLEVEL carrying the value APPSRV

87 33 00 00 06 00 01 92 01

Parameter AAUTHTYPE carrying the value BASIC

87 32 00 00 06 03 73 65 72 76 65 72 70 77 00 01

Parameter AAUTHSECRET carrying the inline string "serverpw"

87 00 01 2F 00 00 06 03 73 65 72 76 65 72 6E 6F 6E 63 65 00 01

Parameter AAUTHDATA carrying the inline string "servernonce"

01 End of characteristic APPAUTH

01 End of characteristic APPLICATION

01 End of element <wap-provisioningdoc>, that is, end of provisioning doc-ument


45 January 2008


OMA Device Management

Note: OMA Device Management is not supported in the V800 and Z800 series.

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

46 January 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 on one specific server.

The Client Provisioning and Device Management technologies are also based on similar technologies. One important difference between the technologies 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 content 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 data transfer 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 to 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 are stored in a tree structure defined in OMA standards. The DM tree contains nodes and leaves. Leaves con-tain settings and parameter values, controlling software and hardware operations in the device. Leaves are always on the lowest level in the DM tree, and cannot therefore contain any sublevels. Groups of set-tings and parameters for a specific application are referred to as Management Objects (MO) and are rep-resented as “branches” of the DM tree. An MO is thus found as a number of subnodes and leaves emanating 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 an 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, however, implicitly creates missing nodes in newly added MOs, after the DM session ends. Therefore, when the server reconnects to the phone in a subsequent DM session, the exist-ing MOs are complete. If the server wants to modify the values of any leaves, it now has to use the Replace command.

DM Delete command is usually not allowed on single nodes within an MO, to ensure the integrity of, for example, account structures. In many cases dynamic MOs can be deleted at the placeholder level instead.

Device Management is typically implemented in a phone as follows:

1. OMA Client Provisioning is used to bootstrap the phone 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.

47 January 2008


4. Programmatically, DM sessions are always initiated by the client, 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. See the fol-lowing documents, found at http://www.openmobilealliance.org/ for details on the standards:

For DM clients versions 1.0 and 2.0, protocol version 1.1.2:

• 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

For DM clients version 3.x, protocol version 1.2:

• Device Management Tree and Description version 1.2• Device Management Protocol version 1.2• Device Management Representation Protocol version 1.2• Device Management Security version 1.2• Device Management Bootstrap, version 1.2• Device Management Standardized Objects, version 1.2• Notification Initiated Session, version 1.2

Preconditions

Common preconditions for DM sessions to take place are:

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

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

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

48 January 2008



DM sessions

A DM session can be divided into two phases:

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

• 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, see SyncML Device Management Protocol version 1.1.2, http://www.openmobilealliance.org/

General use case

A Device Management session is set up between a phone and a DM server. The server intends to config-ure 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 initiative.

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, via a timer event controlled by parameter settings or ordered by a server operator.

Example: An operator is launching a new service and, as a result of this, is restructuring its service net-work, requiring some existing customers to modify their configurations.

1. The DM server sends out a package 0 message using connectionless WAP push. (See Notification Ini-tiated Session for details on the standard)

2. The message is received and its 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 is 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 writes and reads application data to/from the phone.

49 January 2008



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 following table lists Device Management client and protocol versions implemented in Sony Ericsson phones:

The DevInfo/DmV node contains the version number of the Device Management client implementation, as specified in the table. For example, the DM client in K750 series is version 1.0, whereas the client in W810 series is version 2.0.

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 indicates a new generation of the DM client software, which usually also means changes to the DM tree structure or some new or extended management objects. For example, the 2.0 cli-ent supports FUMO (Firmware Update Management Object) and large object transfers, whereas 1.0 did not, and the AP objects are rather different in 2.0 compared to 1.0.

Every increment in the DmV value mandates the release of a new corresponding DDF on the Sony Erics-son Web site. The URL to Sony Ericsson online DDFs is wap.sonyericsson.com/ddf/<filename>.xml

The appropriate value of <filename> is constructed by concatenating the value of the DmV node in the phone with the prefix string "sonyericsson_ddf_".

Example:

A W550 phone has a DmV value of 2.0, and the corresponding DDF can be found at wap.sonyerics-son.com/ddf/sonyericsson_ddf_2.0.xml

Device Management Implemented in

client version protocol version

1.0 1.1.2 K600, K750, V600, W700, W800 and Z525 series

2.0 1.1.2 K310, K320, K510, W200, W300, W550, W600, W810, W900, Z530, Z550 and Z558 series

3.0 1.2 K550 (except K550im), K610 (except K610im), K790, K800, K810, S500, W580, W610, W660, W710, W830, W850, W880, Z610 and Z710 series

3.1 1.2 W350, W380, Z310 and Z555 series

3.2 1.2 K610im and K550im phone models (i-mode phones)

3.3 1.2 K530, K770 and T650 series

50 January 2008


Example:

A K800 phone has a DmV value of 3.0 so the DDF is found at wap.sonyericsson.com/ddf/sonyericsson_ddf_3.0.xml

Example: (hypothetical)

Assuming a software upgrade package were available for an old DmV 2.0 phone, after which the phone would be running a (hypothetical) DmV 2.1 DM client. This would require that an updated DDF be pub-lished at wap.sonyericsson.com/ddf/sonyericsson_ddf_2.1.xml

Authentication

The OMA Device Management standard defines two different security mechanisms: transport security and protocol security. Protocol security includes all authentication mechanisms defined in the DM standard, for example, Basic, MD5 and HMAC mechanisms.

In Sony Ericsson DM clients, transport security is handled by using a HTTP connection with TLS/SSL when URLs begin with "https:". If a DM account is specified to use transport security (that is, its server URL begins with "https:"), the DM server is regarded as authenticated from start, and the client does not send any protocol challenge to the server. However, the client still responds to any protocol challenges from the server.

The DM client keeps track internally of the latest authentication mechanism used by the server and sends corresponding credentials in the first client package of subsequent sessions, to try to reduce the number of authentication round trips. The server may accept these credentials if it considers them to be valid, or issue a new challenge to the client. This saved, or preferred, authentication mechanism can be read or written by the DM server via the "AuthPref" node (DM 1.1.2) or the AAuthPref node (DM 1.2) in the DMAcc object.

During the authentication phase, the DM client also accepts 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 signals the end of the session.

Server authentication in the client, and client authentication to the server are two independent mecha-nisms. That is, any credentials sent from the client to the server in the first package is independent of which authentication mechanism the client requests from the server. For incoming challenges of the DM client from the server, the client responds with the corresponding credentials.

To authenticate the server however, the client is configured to only accept at least a "lowest acceptable authentication level" for the server credentials. When the client challenges the server, it tries to use the authentication level that the server used for its challenge in the last session, unless that was a less secure level than the "lowest acceptable authentication level". That is, the client always issues challenges to the server with an authentication level at least as secure as the "lowest acceptable" mechanism.

Example:

If the "lowest acceptable level" is configured to be MD5, the client never issues challenges with less secure mechanisms to the server or accepts, for example, Basic credentials from the server, but always challenges with at least MD5 level. Since the client and server authentications are completely independ-

51 January 2008


ent, this restriction does not affect the preferred client credentials (AuthPref); the DM client remembers the last incoming challenge and sends corresponding credentials in package 1, regardless of the security level. It also tries to use the same AuthPref level to challenge the server, but with this restriction applied, that is, if AuthPref is Basic the client sends its Basic credentials but a MD5 challenge to the server.

Phones in the W600 series are configured to use MD5 as lowest authentication level. If Basic or None authentication levels are preferred (for the server authentication), transport security must be used, since the server is then regarded as authenticated by default, and the lowest authentication restriction never applies.

The HMAC authentication mechanism implies that the client accepts a new challenge for every package received from the server in order to be given a new nonce to use with the next package. The client responds with Status = 200 for the SyncHdr and a new challenge to the server with the new nonce value for the server to use with the next package. Thus, all packages during the session contain a challenge to the counterpart to set NextNonce. Credentials are transferred in the HTTP headers of the packages. This behaviour is not standardized, but agreed upon through IOT discussions at, for instance, OMA TestFests. The DM client also accepts initial HMAC challenges from the server side, even though it is specified that the server must not be the first side to initiate HMAC authentication.

With mechanisms using nonce values, the client sends a challenge if the first credentials received from the server were wrong due to unsynchronized nonces. If the second answer from the server also contains errors, the authentication is regarded as having failed (since the server received a valid NextNonce in the client challenge) and the client disconnects even if the server package contains commands.

The client does not do any digest verification of package 0 (server notification package) and starts a ses-sion regardless of whether the digest is correct or not. In sessions started with a server notification, the client always requires server DM authentication even if package 0 did contain a valid digest. However, servers using a connection with transport security are always regarded as authenticated from start.

52 January 2008


Management Objects

The basic tree structure for DM client version 1.0

The basic tree structure for DM client version 2.0

. DevInfo >>

DevDetail >>

SyncML DMAcc >>

DSAcc >>

AP NAP >>

Proxy >>

Settings ActiveProxyRef

Com.SonyEricsson Content Browser Bookmarks >>

Settings Java >>

Streaming >>

MMS >>

SMS >>

Email >>

WV >>

Ext <X>* <X>*

>>

>>

. DevInfo >>

DevDetail

SyncML DMAcc >>

AP Proxy >>

Settings ActiveProxyRef

NAP_PSD >>

NAP_CSD >>

Fw >>

Com.SonyEricsson Content Browser Bookmarks

Settings Java >>

Streaming >>

MMS >>

SMS >>

Email >>

WV >>

Sync DSAcc >>

FOTA >>

Ext >>

53 January 2008


The basic tree structure for DM clients version 3.x

Note: The nodes ./AP/NAP_CSD and ./Com.SonyEricsson/Settings/Streaming do not exist in DM client version 3.1

Note: The node ./Com.SonyEricsson/Settings/WV does not exist in DM client version 3.2 (i-mode phones).

. DevInfo >>

DevDetail >>

DMAcc >>

AP Proxy >>

NAP_PSD >>

NAP_CSD >>

Fw >>

Com.SonyEricsson Content Browser Bookmarks >>

JavaApplications >>

Settings Java >>

Streaming >>

MMS >>

SMS >>

Email >>

WV >>

Sync DSAcc >>

FOTA >>

Ext >>

54 January 2008


Device information subtree ./DevInfo

Subtree structure

./DevInfoOMA Standardized Management Object for device information.

Access Type: GetOccurrence: OneFormat: Node

./DevInfo/DevIdThe IMEI number of the phone, formatted as a string, for example, "IMEI:123456789012345".

Access Type: GetOccurrence: OneFormat: chr

./DevInfo/DmVDM Client version. The value can be used to find the correct DDF published on the Sony Ericsson Web site.

Access Type: GetOccurrence: OneFormat: chrDefault Value: “1.0”, “2.0”, “3.0”, “3.1” or “3.2”(depending on client version)

./DevInfo/LangCurrent language for the phone, for example, "en" for English.


./DevInfo/ManPhone manufacturer.

Access Type: GetOccurrence: OneFormat: chrDefault Value: “SonyEricsson”

DevInfo DevId

DmV

Lang

Man

Mod

55 January 2008


./DevInfo/ModPhone model, for example, "W600i"


Detailed device information ./DevDetail (DM clients versions 1.0 and 2.0)

Note: The corresponding Management Object for DM clients version 3.x is found in “Detailed device infor-mation ./DevDetail (DM clients version 3.x)” on page 62.

OMA standardized object

Subtree structure

./DevDetailOMA Standardized Management Object for detailed device information (with Sony Ericsson specific extensions under the Ext node).


DevDetail Ext CrashData

FreeMemory

IMSI

Fw SwVariant

SwRevision

FsVariant

FsSubVariant

Product ProductId

Network MCC

CMCC

DevTyp

OEM

FwV

SwV

HwV

LrgObj

URI MaxDepth

MaxTotLen

MaxSegLen

56 January 2008


./DevDetail/ExtSony Ericsson specific DevDetail extensions.


./DevDetail/Ext/CrashDataNote: Not applicable to DM client v 1.0. Binary representation of the Sony Ericsson crash data statistics object.

Access Type: GetOccurrence: OneFormat: bin

./DevDetail/Ext/FreeMemoryAmount of free space in the file system on the phone. Does not include space on a removable memory card.

Access Type: GetOccurrence: OneFormat: int

./DevDetail/Ext/IMSIThe IMSI formatted as an ASCII string of hexadecimal octets, for example, "01 02 03 4A 5B FF".


./DevDetail/Ext/FwDetailed firmware version information, for example, for FOTA servers.


./DevDetail/Ext/Fw/SwVariantThe software CXC number.


57 January 2008


./DevDetail/Ext/Fw/SwRevisionSoftware revision.


./DevDetail/Ext/Fw/FsVariant

File system version.


./DevDetail/Ext/Fw/FsSubVariantFile system area identifier.


./DevDetail/Ext/ProductProduct-specific information.


./DevDetail/Ext/Product/ProductIdIdentifier for customized product.


./DevDetail/Ext/NetworkNetwork information.


58 January 2008


./DevDetail/Ext/Network/MCCMobile Country Code.


./DevDetail/Ext/Network/CMCCCurrent Mobile Country Code.


./DevDetail/DevTypType of device.

Access Type: GetOccurrence: OneFormat: chrDefault Value:DM client ver 1.0: “MobilePhone”DM client ver 2.0: "phone"

./DevDetail/OEMOriginal Equipment Manufacturer.

Access Type: GetOccurrence: OneFormat: chrDefault Value: "SonyEricsson"

./DevDetail/FwVConcatenated Firmware Version identifier.


./DevDetail/SwVSoftware version.


59 January 2008


./DevDetail/HwVHardware version. This value is currently not specified and is ignored.


./DevDetail/LrgObjIndicates whether the phone supports the SyncML Large Object Handling specification.

Access Type: GetOccurrence: OneFormat: boolDefault Value: DM client ver 1.0: FalseDM client ver 2.0: True

./DevDetail/URIDetails about DM tree URI formatting.


./DevDetail/URI/MaxDepthSpecifies the maximum depth of the management tree supported by the phone. The maximum depth of the tree is defined as the maximum number of URI segments the phone supports. The value is a 16-bit, unsigned integer encoded as a numerical string. The value “0” means that the phone supports a tree of “unlimited” depth.

Access Type: GetOccurrence: OneFormat: chrDefault Value: “20”

./DevDetail/URI/MaxTotLenSpecifies the maximum total length of any URI used to address a node or node property. The maximum total length of a URI is defined as the largest total number of characters making up the URI the phone sup-ports. Note that, depending on the character set, this might not be the same as the number of bytes. The value is a 16-bit, unsigned integer encoded as a numerical string. The value “0” means that the phone supports URI of “unlimited” length.


60 January 2008


./DevDetail/URI/MaxSegLenSpecifies the maximum total length of any URI segment in a URI used to address a node or node property. The maximum total length of a URI segment is defined as the largest number of characters the phone sup-ports in a single URI segment. Note that, depending on the used character set, this might not be the same as the number of bytes. The value is a 16-bit, unsigned integer encoded as a numerical string. The value "0" means that the phone supports URI segments of “unlimited” length.


61 January 2008


Detailed device information ./DevDetail (DM clients version 3.x)

Note: The corresponding Management Object for DM clients versions 1.0 and 2.0, is found in “Detailed device information ./DevDetail (DM clients versions 1.0 and 2.0)” on page 56.

OMA standardized object.

Subtree structureDevDetail DevTyp

OEM

FwV

SwV

HwV

LrgObj

URI MaxDepth

MaxTotLen

MaxSegLen

Ext CrashData

IMSI

Device DateAndTime Date

DaylightSaving

Time

Timezone

Memory FreeMemory

Fw SwVariant

SwRevision

FsVariant

FsSubVariant

Product ProductId

Network MCC

CMCC

MNC

CMNC

ServiceProvider

Registration State

Mode

Reset

Date

HSS

62 January 2008


./DevDetailOMA Standardized Management Object for detailed device information (with Sony Ericsson specific extensions under the Ext node).


./DevDetail/DevTypType of device.

Access Type: GetOccurrence: OneFormat: chrDefault Value: "phone"

./DevDetail/OEMOriginal Equipment Manufacturer.

Access Type: GetOccurrence: OneFormat: chrDefault Value: "SonyEricsson"

./DevDetail/FwVConcatenated Firmware Version identifier.


./DevDetail/SwVSoftware version.


./DevDetail/HwVHardware version. This value is currently not specified and is ignored.


63 January 2008


./DevDetail/LrgObjIndicates whether the phone supports the SyncML Large Object Handling specification.

Access Type: GetOccurrence: OneFormat: boolDefault Value: True

./DevDetail/URIDetails about DM tree URI formatting.


./DevDetail/URI/MaxDepthSpecifies the maximum depth of the management tree supported by the phone. The maximum depth of the tree is defined as the maximum number of URI segments the phone supports. The value is a 16-bit, unsigned integer encoded as a numerical string. The value “0” means that the phone supports a tree of “unlimited” depth.


./DevDetail/URI/MaxTotLenSpecifies the maximum total length of any URI used to address a node or node property. The maximum total length of a URI is defined as the largest total number of characters making up the URI the phone sup-ports. Note that, depending on the character set, this might not be the same as the number of bytes. The value is a 16-bit, unsigned integer encoded as a numerical string. The value “0” means that the phone supports URI of “unlimited” length.


./DevDetail/URI/MaxSegLenSpecifies the maximum total length of any URI segment in a URI used to address a node or node property. The maximum total length of a URI segment is defined as the largest number of characters the phone sup-ports in a single URI segment. Note that, depending on the used character set, this might not be the same as the number of bytes. The value is a 16-bit, unsigned integer encoded as a numerical string. The value “0” means that the phone supports URI segments of “unlimited” length.


64 January 2008


./DevDetail/ExtSony Ericsson specific DevDetail extensions.


./DevDetail/Ext/CrashDataBinary representation of the Sony Ericsson crash data statistics object.

Access Type: GetOccurrence: OneFormat: bin

./DevDetail/Ext/IMSIThe IMSI formatted as an ASCII string of hexadecimal octets, for example, "01 02 03 4A 5B FF".


./DevDetail/Ext/DeviceSettings and information about phone configuration.

Access Type: GetOccurrence: OneFormat: node

./DevDetail/Ext/Device/DateAndTimeCurrent date and time settings of the phone (read-only).


./DevDetail/Ext/Device/DateAndTime/DateCurrent date in the phone.

Access Type: GetOccurrence: OneFormat: chrAllowed values: String; format “dd-mm-yyyy”

65 January 2008


./DevDetail/Ext/Device/DateAndTime/DayLightSavingNumber of hours for daylight saving.

Access Type: GetOccurrence: OneFormat: intAllowed values: Integer; in range 0 to 2

./DevDetail/Ext/Device/DateAndTime/TimeCurrent time in the phone.

Access Type: GetOccurrence: OneFormat: chrAllowed values: String; format “hh:mm”

./DevDetail/Ext/Device/DateAndTime/TimezoneTime zone offset relative to GMT.

Access Type: GetOccurrence: OneFormat: intAllowed values: Integer; in range -48 to +51. Time zone offset from GMT, specified in quarters of an hour

./DevDetail/Ext/Device/MemoryMemory status of the phone.


./DevDetail/Ext/Device/Memory/FreeMemoryAmount of free space in the file system of the phone. Does not include space on removable memory card.


./DevDetail/Ext/FwDetailed firmware version information, for example, firmware update (FOTA) servers.


66 January 2008


./DevDetail/Ext/Fw/SwVariantSoftware CXC number.


./DevDetail/Ext/Fw/SwRevisionSoftware revision.


./DevDetail/Ext/Fw/FsVariantFile system version.


./DevDetail/Ext/Fw/FsSubVariantFile system area identifier.


./DevDetail/Ext/ProductProduct-specific information.


./DevDetail/Ext/Product/ProductIdIdentifier for customized product.


./DevDetail/Ext/NetworkNetwork information.


67 January 2008


./DevDetail/Ext/Network/MCCMobile Country Code.


./DevDetail/Ext/Network/CMCCMobile Current Country Code.


./DevDetail/Ext/Network/MNCMobile Network Code.


./DevDetail/Ext/Network/CMNCCurrent Mobile Network Code.


./DevDetail/Ext/Network/ServiceProviderName of Service provider from SIM.


./DevDetail/Ext/RegistrationSony Ericsson Warranty Registration information.


68 January 2008


./DevDetail/Ext/Registration/StateIndicates the current mode of the registration date.

Access Type: GetOccurrence: OneFormat: chrAllowed values:

./DevDetail/Ext/Registration/ModeClient registration mode.

Access Type: GetOccurrence: OneFormat: chrAllowed values:

./DevDetail/Ext/Registration/ResetIndicates if the real-time clock has been reset (when value is True).

Access Type: GetOccurrence: OneFormat: bool

./DevDetail/Ext/Registration/DateThe date when the phone was registered. Can only be written once.

Access Type: Get, ReplaceOccurrence: OneFormat: chrAllowed values: String; format “dd-mm-yyyy”

Value Description

“Client“ Date is relative to the phone clock

“NITZ” Date is relative to a network time reference

“DM” A registration server has set the date via DM

Value Description

“None“ Not registered

“SMS” Registration SMS sent

“DM” Registered via a DM session

69 January 2008


./DevDetail/Ext/Registration/HSSHours Since Started.

Access Type: GetOccurrence: OneFormat: intAllowed values: Integer; the number of hours since the client was started

SyncML DM accounts (version 1.1.2)DM clients versions 1.0 and 2.0

OMA Standardized Management Object. This node contains DM Accounts (1.1.2).

Note: The corresponding information for DM clients version 3.x (DM Accounts version 1.2), is found in “DM accounts ver. 1.2 (DM clients version 3.x)” on page 74.

Subtree structure

./SyncML/DMAccOMA Standardized Management Object for DM 1.1.2 accounts.


./SyncML/DMAcc/XPlaceholder node for the DM accounts.

Access Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrN (N<=5)Format: NodeAllowed values: String; max length 49

DMAcc <X>* Addr

AddrType?

PortNbr?

ConRef

ServerId

ServerPW?

ServerNonce?

UserName?

ClientPW?

ClientNonce?

AuthPref?

Name?

70 January 2008


./SyncML/DMAcc/X/AddrServer address.

Access Type: Add, Get, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 254, URL

./SyncML/DMAcc/X/AddrTypeThis value is not used by the client and can be ignored.Note: In some client software revisions the value “0” was used instead of the correct value “1”. Since the value is not used by the client, a server can avoid being affected by this error, either by (1) always using the value “0”, (2) ignoring all DM status error codes from this node, or (3) never performing Add or Replace on the node.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault Value: “1”Allowed values: (“0” = A client software error in early revisions caused the value “0” to be set)“1” = HTTP

./SyncML/DMAcc/X/PortNbrPort number used to connect to server. To “clear” the port number, replace with a value of “0” which means “unspecified”.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: DM client ver 1.0: intDM client ver 2.0: chrDefault Value: 0 (“0“)Allowed values:

./SyncML/DMAcc/X/ConRefPath to the Internet profile placeholder in the DM tree which holds the Internet profile to be used, for example, "./AP/Proxy/proxy-01".

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

Integer (chr) Description

0 (“0“) No port specified

1 to 65535 (“1“ to “65535”)

Normal port numbers

71 January 2008


./SyncML/DMAcc/X/ServerIdThis node specifies a server identifier for the management server used in the management session. The server ID cannot be replaced in an existing account. If it needs to be changed, the account is removed by deleting the placeholder and subsequently adding a new account with the new Server ID.

Access Type: Add, GetOccurrence: OneFormat: chrAllowed values: String; max length 79

./SyncML/DMAcc/X/ServerPWThis node holds the password or secret that the server uses to authenticate itself to the client.

Access Type: Add, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: String; max length 59

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


./SyncML/DMAcc/X/UserNameThis node stores the name of the user (or phone), for use in SyncML DM authentication.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: String; max length 79

./SyncML/DMAcc/X/ClientPWThis node holds the password or secret that the client uses to authenticate itself to the server.


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


72 January 2008


./SyncML/DMAcc/X/AuthPrefThe authentication level preferred by the server for client credentials.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault Value: "syncml:auth-md5"Allowed values: """syncml:auth-basic""syncml:auth-md5""syncml:auth-MAC"

./SyncML/DMAcc/X/NameDisplayable name for this account.


73 January 2008


DM accounts ver. 1.2 (DM clients version 3.x)

OMA Standardized Management Object for DM 1.2 accounts.

Note: The corresponding information for DM clients versions 1.0 and 2.0 (DM accounts version 1.1.2) is found in “SyncML DM accounts (version 1.1.2) DM clients versions 1.0 and 2.0” on page 70.

Subtree structure

./DMAccOMA Standardized Management Object for DM 1.2 accounts.


./DMAcc/XThis node is a placeholder representing one DM account.

Access Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrN (N<=5)Format: NodeAllowed values: String; max length 49

DMAcc <X>* AppID

ServerID

Name?

PrefConRef?

AppAddr <X> Addr

AddrType

Port? <X> PortNbr

AAuthPref?

AppAuth? <X>* AAuthLevel

AAuthType

AAuthName?

AAuthSecret?

AAuthData?

Ext? Locked?

UserEditable?

AllowClientInitiated?

Notification?

74 January 2008


./DMAcc/X/AppIDThis node specifies the application ID for one Device Management account object.

Access Type: GetOccurrence: OneFormat: chrDefault value: “w7“

./DMAcc/X/ServerIDThis node specifies a server identifier for a management server used in the management session. The server ID cannot be replaced in an existing account. If it needs to be changed, the account has to be removed by deleting the placeholder and subsequently adding a new account with the new Server ID

Access Type: Add, GetOccurrence: OneFormat: chrAllowed values: String; max length 79

./DMAcc/X/NameThis node specifies the user displayable name for the DM account.


./DMAcc/X/PrefConRefThis node specifies a reference to the preferred Internet profile object for connectivity, for example, "./AP/Proxy/ProxyAcc/ProxyAcc-01".

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values:

./DMAcc/X/AppAddrThis node specifies management server addresses. The current implementation supports only one address.

Access Type: Add, GetOccurrence: OneFormat: Node

Value Description

"./AP/Proxy/ProxyAcc/<X>" <X> is the placeholder name for the linked account. The account must exist in the tree.

75 January 2008


./DMAcc/X/AppAddr/XThis interior node acts as a placeholder, but currently only supports one server address.

Access Type: Add, Get, ReplaceOccurrence: OneFormat: Node

./DMAcc/X/AppAddr/X/AddrThis node specifies a management server address.

Access Type: Add, Get, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 255. Address format depends on AddrType, default is URI

./DMAcc/X/AppAddr/X/AddrTypeThis node specifies a management server address type.

Access Type: Add, Get, Replace

Occurrence: One

Format: chr

Default Value: “URI”

Allowed values:

./DMAcc/X/AppAddr/X/PortThis node specifies port information for a management server address.

Access Type: Add, GetOccurrence: ZeroOrOneFormat: Node

./DMAcc/X/AppAddr/X/Port/XThis interior node acts as a placeholder to separate one or more port settings. Current implementation only supports one port number.

Access Type: Add, Get, ReplaceOccurrence: OneFormat: Node

Value Description

“URI“ Server address is an absolute URI

“IPv4”

“IPv6”

76 January 2008


./DMAcc/X/AppAddr/X/Port/X/PortNbrThis node specifies a port number.

Access Type: Add, Get, ReplaceOccurrence: OneFormat: chrAllowed values: String. The port number must be a decimal number and must fit within the range of a 16-bit unsigned integer. (That is, Range=0 to 65535)

./DMAcc/X/AAuthPrefThis node indicates which authentication type to use when connecting to the server. Authentication types are specified in the document “OMA Device Management Security, Version 1.2”,http://www.openmobile-alliance.org


./DMAcc/X/AppAuthThis node specifies authentication information.


./DMAcc/X/AppAuth/XThis interior node acts as a placeholder to separate one or more authentication settings. The implementa-tion currently supports a maximum of three unique settings - “CLCRED”, “SRVCRED” and “HTTP”. Only one setting is allowed for each type, for example, you cannot have two “CLCRED” placeholders.

Access Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrN (N<=3)Format: NodeAllowed values: String; max length 50. Placeholder node name can be max 50 characters long

Value Description

“BASIC“ DM “syncml:auth-basic” authentication

“DIGEST” DM “syncml:auth-md5” authentication

“HMAC” DM “syncml:auth-MAC” authentication

77 January 2008




./DMAcc/X/AppAuth/X/AAuthLevelThis node specifies the authentication level. The value can only be specified by a server when the node is added, existing nodes are read-only.

Access Type: Add, GetOccurrence: OneFormat: chrAllowed values:

./DMAcc/X/AppAuth/X/AAuthTypeThis node specifies the authentication type (read-only).


./DMAcc/X/AppAuth/X/AAuthNameThis node specifies the authentication name.


./DMAcc/X/AppAuth/X/AAuthSecretThis node specifies the authentication secret.

Access Type: Add, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: String; max length 60.

./DMAcc/X/AppAuth/X/AAuthDataThis node specifies the authentication next nonce.

Access Type: Add, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: String; max length 51.

Value

“SRVCRED“

“CLCRED”

“HTTP”

78 January 2008


./DMAcc/X/ExtSony Ericsson specific extensions.


./DMAcc/X/Ext/LockedIndicates if this account is locked and cannot be edited or removed. A DM server can add the node with value True when adding a new account but cannot replace the value in existing accounts.

Access Type: Add, GetOccurrence: ZeroOrOneFormat: boolDefaultvalue: False

./DMAcc/X/Ext/UserEditableIndicates if the user is allowed to edit this account via the UI.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: boolDefault value: True

./DMAcc/X/Ext/AllowClientInitiatedIndicates if this account can be used for a client-initiated session, that is, if the user can start a DM ses-sion via the UI.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: boolDefault value: True

./DMAcc/X/Ext/NotificationDetermines how the user is notified of a server-initiated session request.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault value: “ask”Allowed values:

Value Description

“ask“ The user is presented with a popup question to accept or reject the session

“accept” No popup is presented to the user; the session is always accepted

“reject” Server-initiated sessions are always rejected

79 January 2008


OMA Data Sync accounts (DM client version 1.0 only)

Note: For DM clients versions 2.0 and 3.x, the OMA DS accounts subtree is found under the ./Com.Sony-Ericsson/Settings/Sync node, see “OMA Data Sync accounts (DM clients versions 2.0 and 3.x)” on page 130.

Subtree structure

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

./SyncML/DSAcc/XAccess Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrN (N<=5)Format: Node

DSAcc <X>* Name?

Addr

ClientName?

ClientPW?

ClientNonce?

ProxyRef?

DB? Cal? RDBURI?

UserName?

UserPW?

Enabled?

PB? RDBURI?

UserName?

UserPW?

Enabled?

Notes? RDBURI?

UserName?

UserPW?

Enabled?

ToDo? RDBURI?

UserName?

UserPW?

Enabled?

80 January 2008


./SyncML/DSAcc/X/NameDisplayable name for this account.


./SyncML/DSAcc/X/AddrServer address, which must be unique among the DS accounts, that is, only one account can have any given server address.


./SyncML/DSAcc/X/ClientNameClient identity;used for client authentication.


./SyncML/DSAcc/X/ClientPWClient password; used for client authentication.


./SyncML/DSAcc/X/ClientNonceNext nonce to be used for client authentication.

Access Type: Add, ReplaceOccurrence: ZeroOrOneFormat: binAllowed values: Binary data, Max length 52 bytes

./SyncML/DSAcc/X/ProxyRefPath to the Internet profile placeholder in the DM tree which holds the Internet profile to be used, for example, "./AP/Proxy/proxy-01".

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

81 January 2008


./SyncML/DSAcc/X/DBSync databases.


./SyncML/DSAcc/X/DB/CalApplication settings for Calendar sync.


./SyncML/DSAcc/X/DB/Cal/RDBURIDatabase name.


./SyncML/DSAcc/X/DB/Cal/UserNameUsername.


./SyncML/DSAcc/X/DB/Cal/UserPWPassword.


./SyncML/DSAcc/X/DB/Cal/EnabledIndicates if this application may be synchronized.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: boolDefault Value: False

82 January 2008


./SyncML/DSAcc/X/DB/PBApplication settings for Phonebook (Contacts) sync.


./SyncML/DSAcc/X/DB/PB/RDBURIDatabase name.


./SyncML/DSAcc/X/DB/PB/UserNameUsername.


./SyncML/DSAcc/X/DB/PB/UserPWPassword.


./SyncML/DSAcc/X/DB/PB/EnabledIndicates if this application may be synchronized.


./SyncML/DSAcc/X/DB/NotesApplication settings for Notes sync.


83 January 2008


./SyncML/DSAcc/X/DB/Notes/RDBURIDatabase name.


./SyncML/DSAcc/X/DB/Notes/UserNameUsername.


./SyncML/DSAcc/X/DB/Notes/UserPWPassword.


./SyncML/DSAcc/X/DB/Notes/EnabledIndicates if this application may be synchronized.


./SyncML/DSAcc/X/DB/ToDoApplication settings for Tasks sync.


./SyncML/DSAcc/X/DB/ToDo/RDBURIDatabase name.


84 January 2008


./SyncML/DSAcc/X/DB/ToDo/UserNameUsername.


./SyncML/DSAcc/X/DB/ToDo/UserPWPassword.


./SyncML/DSAcc/X/DB/ToDo/EnabledIndicates if this application may be synchronized.


85 January 2008


Internet accounts (DM client version 1.0 only)

Note: The corresponding MO for DM client version 2.0 is found in “Internet accounts (DM client version 2.0 only)” on page 90 and the MO for DM clients version 3.x in “Internet accounts (DM clients version 3.x only)” on page 93.

Subtree structure

./AP/ProxyInternet profiles.


./AP/Proxy/XPlaceholder for an Internet account.

Access Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrN, (N<=10)Format: Node

Proxy <X>* Mode?

Name?

PxAddr?

PortNbr?

UseProxy?

NAPRef? PrefNAPRef?

SecNAPRef?

PxAuthInfo? PxAuthType?

PxAuthId?

PxAuthPW?

HomePage? Title?

URL?

WAP? BasAuthId?

BasAuthPW?

86 January 2008


./AP/Proxy/X/ModeIndicates the connection type.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault value: “http“Allowed values:

./AP/Proxy/X/NameProfile name.


./AP/Proxy/X/PxAddrProxy address.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: String; max length 255, URL

./AP/Proxy/X/PortNbrProxy port number.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: intDefault Value: 8080Allowed values: Integer; range 0 to 65535

./AP/Proxy/X/UseProxyIndicates if the proxy is used.


Value Description

“http” This is a HTTP profile

“wap” This is a WAP profile

87 January 2008


./AP/Proxy/X/NAPRefThe preferred and optional secondary data account used by this profile to connect to the network.


./AP/Proxy/X/NAPRef/PrefNAPRefPath to the data account placeholder used in the DM tree, for example, "./AP/NAP/Nap-01".


./AP/Proxy/X/NAPRef/SecNAPRefPath to a secondary data account placeholder in the DM tree, for example, "./AP/NAP/Nap-01".


./AP/Proxy/X/PxAuthInfoOptional proxy authentication information.


./AP/Proxy/X/PxAuthInfo/PxAuthTypeAuthentication type.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault Value: "HTTP-BASIC"Allowed values: "HTTP-BASIC"

./AP/Proxy/X/PxAuthInfo/PxAuthIdUsername.


88 January 2008


./AP/Proxy/X/PxAuthInfo/PxAuthPWAuthentication password.


./AP/Proxy/X/HomePageDefault browser start page.


./AP/Proxy/X/HomePage/TitleDisplayable title for the start page.


./AP/Proxy/X/HomePage/URLURL for start page.


./AP/Proxy/X/WAPAccess Type: Add, GetOccurrence: ZeroOrOneFormat: Node

./AP/Proxy/X/WAP/BasAuthIdAccess Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chr

./AP/Proxy/X/WAP/BasAuthPWAccess Type: Add, ReplaceOccurrence: ZeroOrOneFormat: chr

89 January 2008


Internet accounts (DM client version 2.0 only)

Note: The corresponding MO for DM client version 1.0 is found in “Internet accounts (DM client version 1.0 only)” on page 86, and the MO for DM clients version 3.x is found in “Internet accounts (DM clients version 3.x only)” on page 93.

Subtree structure

./AP/ProxyInternet accounts.


./AP/Proxy/XPlaceholder for an Internet account.


./AP/Proxy/X/NameDisplayable profile name.


Proxy <X>* Name?

PxAddr?

PortNbr?

UseProxy?

NAPRef? PrefNAPRef?

SecNAPRef?


PxAuthId?

PxAuthPW?

HomePage? Title?

URL?

90 January 2008


./AP/Proxy/X/PxAddrProxy address.


./AP/Proxy/X/PortNbrProxy port number.


./AP/Proxy/X/UseProxyIndicates if the proxy is used.


./AP/Proxy/X/NAPRefThe preferred and optional secondary data account used by this profile to connect to the network.


./AP/Proxy/X/NAPRef/PrefNAPRefPath to the used data account placeholder in the DM tree, for example, "./AP/NAP_PSD/NapPsd-01".


./AP/Proxy/X/NAPRef/SecNAPRefPath to a secondary data account placeholder in the DM tree, for example, "./AP/NAP_CSD/NapCsd-01".


91 January 2008


./AP/Proxy/X/PxAuthInfoOptional proxy authentication information.


./AP/Proxy/X/PxAuthInfo/PxAuthTypeAuthentication type.


./AP/Proxy/X/PxAuthInfo/PxAuthIdUsername.


./AP/Proxy/X/PxAuthInfo/PxAuthPWAuthentication password.


./AP/Proxy/X/HomePageDefault browser start page.


./AP/Proxy/X/HomePage/TitleDisplayable title for the start page.


92 January 2008


./AP/Proxy/X/HomePage/URLURL for start page.


Internet accounts (DM clients version 3.x only)

Note: The corresponding MO for DM client version 1.0 is found in “Internet accounts (DM client version 1.0 only)” on page 86, and the MO for DM client version 2.0 is found in “Internet accounts (DM client ver-sion 2.0 only)” on page 90.

Subtree structure

./AP/ProxyInternet accounts.


./AP/Proxy/ProxyAccContainer for the Internet accounts.


Proxy ProxyAcc <X>* Name?

PxAddr?

PortNbr?

UseProxy?

NAPRef? PrefNAPRef?

SecNAPRef?


PxAuthId?

PxAuthPW?

HomePage? Title?

URL?

ActiveProxyRef

93 January 2008


./AP/Proxy/ProxyAcc/XPlaceholder for an Internet account.


./AP/Proxy/ProxyAcc/X/NameDisplayable profile name.


./AP/Proxy/ProxyAcc/X/PxAddrProxy address.


./AP/Proxy/ProxyAcc/X/PortNbrProxy port number.


./AP/Proxy/ProxyAcc/X/UseProxyIndicates if the proxy is used.


./AP/Proxy/ProxyAcc/X/NAPRefThe preferred and optional secondary data account used by this profile to connect to the network.


94 January 2008


./AP/Proxy/ProxyAcc/X/NAPRef/PrefNAPRefPath to the used data account placeholder in the DM tree, for example, "./AP/NAP_PSD/NapPsd-01".


./AP/Proxy/ProxyAcc/X/NAPRef/SecNAPRefPath to a secondary data account placeholder in the DM tree, for example, "./AP/NAP_CSD/NapCsd-01".


./AP/Proxy/ProxyAcc/X/PxAuthInfoOptional proxy authentication information.


./AP/Proxy/ProxyAcc/X/PxAuthInfo/PxAuthTypeAuthentication type.


Value Description

"./AP/NAP_CSD/<X>" <X> is the placeholder name for the linked account. The account must exist in the tree

"./AP/NAP_PSD/<X>" <X> is the placeholder name for the linked account. The account must exist in the tree

Value Description

"./AP/NAP_CSD/<X>" <X> is the placeholder name for the linked account. The account must exist in the tree

"./AP/NAP_PSD/<X>" <X> is the placeholder name for the linked account. The account must exist in the tree

95 January 2008


./AP/Proxy/ProxyAcc/X/PxAuthInfo/PxAuthIdUsername.


./AP/Proxy/ProxyAcc/X/PxAuthInfo/PxAuthPWAuthentication password.


./AP/Proxy/ProxyAcc/X/HomePageDefault browser start page.


./AP/Proxy/ProxyAcc/X/HomePage/TitleDisplayable title for start page.


./AP/Proxy/ProxyAcc/X/HomePage/URLURL for start page.


96 January 2008


./AP/Proxy/ActiveProxyRefIndicates the currently selected active/default profile. It is a path to the Internet profile placeholder in the DM tree, for example, "./AP/Proxy/ProxyAcc/ProxyAcc-01"

Access Type: Get, ReplaceOccurrence: OneFormat: chrAllowed values:

Packet Switched Data (PSD) accounts(DM clients versions 2.0 and 3.x)

Note: The corresponding MO for DM client version 1.0 data accounts is found in “Data accounts (DM cli-ent version 1.0 only)” on page 105.

Subtree structure

./AP/NAP_PSDAccess Type: GetOccurrence: OneFormat: Node

Value Description

"./AP/Proxy/ProxyAcc/<X>" <X> is the placeholder name for the linked account. The account must exist in the tree

NAP_PSD <X>* NAPId?

Name?

Locked?

AuthName?

AuthSecret?

AuthPrompt?

AuthType?

DNS?

HostAddr?

APN?

ServiceMode?

DataCompression?

HeaderCompression?

97 January 2008


./AP/NAP_PSD/XAccess Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrN (N<=10)

Note: The phone supports a TOTAL of 10 data accounts, that is, the sum of PSD and CSD accounts can be up to 10.

Format: Node

./AP/NAP_PSD/X/NAPIdThe phone-assigned account ID. This node is read-only and automatically added by the client on existing accounts. It cannot be added for new accounts by the DM server.

Access Type: GetOccurrence: ZeroOrOneFormat: int

./AP/NAP_PSD/X/NameDisplayable account name.


./AP/NAP_PSD/X/LockedFurther editing of an account is prevented when it has been locked. Unlocking the account requires replacing this node, thus giving it the default value of “False”.


./AP/NAP_PSD/X/AuthNameUsername for authentication.


./AP/NAP_PSD/X/AuthSecretAuthentication password.


98 January 2008


./AP/NAP_PSD/X/AuthPromptPrompt user for password.

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

./AP/NAP_PSD/X/AuthTypeComma-separated list of any of the following authentication type strings.


./AP/NAP_PSD/X/DNSDNS IP address.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault Value: “0.0.0.0”Allowed values: String; IP number, “0.0.0.0” is Network Subscribe

./AP/NAP_PSD/X/HostAddrHost IP Address.


Value Description

"None" No authentication is needed

"Normal" Alias for PAP

"Secure" Alias for CHAP

"PAP" Password Authentication Protocol

"CHAP" Challenge Handshake Authentication Protocol

"MS CHAP" Microsoft CHAP v1

"MS CHAP V2" Microsoft CHAP v2

99 January 2008


./AP/NAP_PSD/X/APNAPN address.


./AP/NAP_PSD/X/ServiceModeService mode for this connection.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: "Exclusive""Automatic"

./AP/NAP_PSD/X/DataCompressionIndicates if data compression should be used.


./AP/NAP_PSD/X/HeaderCompressionIndicates if packet header compression should be used.


100 January 2008


Circuit Switched Data (CSD) accounts (DM clients versions 2.0 and 3.0)

Note: DM client version 3.1 does not support CS Data accounts.

Note: The corresponding MO for DM client version 1.0 data accounts is found in “Data accounts (DM cli-ent version 1.0 only)” on page 105.

Subtree structure

./AP/NAP_CSDCircuit Switched Data accounts.


./AP/NAP_CSD/XAccess Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrN (N<=10)

Note: The phone supports a TOTAL of 10 data accounts, that is, the sum of PSD and CSD accounts can be up to 10.

Format: Node

./AP/NAP_CSD/X/NAPIdThe phone-assigned account ID. This node is read-only and automatically added by the client on existing accounts. It cannot be added for new accounts by the DM server.


NAP_CSD <X>* NAPId?

Name?

Locked?

AuthName?

AuthSecret?

AuthPrompt?

AuthType?

DNS?

HostAddr?

DialString?

DialType?

DataRate?

DataCompression?

101 January 2008


./AP/NAP_CSD/X/NameDisplayable account name.


./AP/NAP_CSD/X/LockedFurther editing of an account is prevented when it has been locked. Unlocking the account requires replacing this node, thus giving it the default value of “False”.


./AP/NAP_CSD/X/AuthNameUsername for authentication.


./AP/NAP_CSD/X/AuthSecretAuthentication password.


./AP/NAP_CSD/X/AuthPromptPrompt user for password.


102 January 2008


./AP/NAP_CSD/X/AuthTypeComma-separated list of any combination of authentication type strings as listed in the table.


./AP/NAP_CSD/X/DNSDNS IP address.


./AP/NAP_CSD/X/HostAddrHost IP Address.


./AP/NAP_CSD/X/DialStringDial-up number.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: String; max length 32Phone number (valid characters: "p", "+", "#", "*" and "0"-"9")

Value Description


"Normal" Alias for PAP

"Secure" Alias for CHAP

"PAP" Password Authentication Protocol

"CHAP" Challenge Handshake Authentication Protocol

"MS CHAP" Microsoft CHAP v1

"MS CHAP V2" Microsoft CHAP v2

103 January 2008


./AP/NAP_CSD/X/DialTypeDialtype, Analog or ISDN.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault Value: “Analog”Allowed values: "Analog""ISDN"

./AP/NAP_CSD/X/DataRateData rate (bps). Note: All speeds may not be supported.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: intDefault Value: 9600Allowed values: 960014400192002880057600 Only available if the phone supports UMTS data rate

./AP/NAP_CSD/X/DataCompressionIndicates if data compression should be used.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: boolDefault Value: FalseAllowed values:

104 January 2008


Data accounts (DM client version 1.0 only)

Note: This MO corresponds to the CSD and PSD data accounts management objects for DM clients ver-sions 2.0 and 3.x, see “Packet Switched Data (PSD) accounts (DM clients versions 2.0 and 3.x)” on page 97 and “Circuit Switched Data (CSD) accounts (DM clients versions 2.0 and 3.0)” on page 101.

Subtree structure

./AP/NAPData accounts.


./AP/NAP/XNote: when adding a data account over DM, the server MUST specify exactly one of the GPRS or CSD nodes along with at least one of their respective leaf nodes. The complete account SHOULD be added within the same DM message, and preferably as a single Add command with multiple items.

Access Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrN (N<=10)Format: Node

./AP/NAP/X/NAPIdThe account ID assigned to the phone. This node is read-only and automatically added by the client on existing accounts. It cannot be added for new accounts by the DM server.


NAP <X>* NAPId?

Name

Locked?

CSD? DialString

DataRate?

DialType?

GPRS? AuthType?

Addr

APN?

AuthInfo? AuthName?

AuthSecret?

AuthPrompt?

IPv4? DNS?

105 January 2008


./AP/NAP/X/NameDisplayable account name.


./AP/NAP/X/LockedFurther editing of an account is prevented when it has been locked.


./AP/NAP/X/CSDNote: Exactly one of either GPRS or CSD nodes MUST be added, along with at least one of their leaf nodes, when a new NAP account is created over DM.


./AP/NAP/X/CSD/DialStringDial-up number.

Access Type: Add, Get, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 32, Phone number (allowed characters “p”, “+”, “#”, “*” and “0” - “9”)

./AP/NAP/X/CSD/DataRateData rate (bps).

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: intDefault Value: 9600Allowed values: 9600144001920028800

106 January 2008


./AP/NAP/X/CSD/DialTypeDialtype, Analog or ISDN.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault Value: “Analog”Allowed values: "Analog""ISDN"

./AP/NAP/X/GPRSNote: Exactly one of either GPRS or CSD nodes MUST be added, along with at least one of their leaf nodes, when a new NAP account is created over DM.


./AP/NAP/X/GPRS/AuthTypeComma-separated list of any combination of the authentication type strings in the table.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault value: “None,Normal,Secure“Allowed values:

./AP/NAP/X/GPRS/AddrNetwork address. "0.0.0.0" = Network Subscribe.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault Value: “0.0.0.0”Allowed values: String; IP number, for example, “192.168.0.1”

./AP/NAP/X/GPRS/APNAccess Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: String; max length 99, URL

Value Description


"Normal" PAP

"Secure" CHAP

107 January 2008


./AP/NAP/X/AuthInfoAccess Type: Add, GetOccurrence: ZeroOrOneFormat: Node

./AP/NAP/X/AuthInfo/AuthNameUsername for authentication.


./AP/NAP/X/AuthInfo/AuthSecretAuthentication password.


./AP/NAP/X/AuthInfo/AuthPromptPrompt user for password.


./AP/NAP/X/IPv4Access Type: Add, GetOccurrence: ZeroOrOneFormat: Node

./AP/NAP/X/IPv4/DNSDNS IP address. "0.0.0.0" = Network Subscribe.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault Value: “0.0.0.0”

108 January 2008


FUMO (DM clients versions 2.0 and 3.x only)

OMA standardized object

Subtree structure

./FwOMA Standardized Management Object for FUMO (Firmware Update over the air Management Object).


./Fw/FwPkg01Firmware update package information.


./Fw/FwPkg01/PkgNameThis node specifies the name associated with the firmware update package.


./Fw/FwPkg01/PkgVersionThis node specifies the version information for the firmware update package.


./Fw/FwPkg01/StateContains a value indicating the current state of the phone with respect to this firmware update. For a table of allowed values and their meaning, see the OMA FUMO documentation.


Fw FwPkg01 PkgName

PkgVersion

State

Download PkgURL

Update PkgData

DownloadAndUpdate PkgURL

109 January 2008


./Fw/FwPkg01/DownloadThis interior node is the target of an Exec command invoked to initiate a firmware download for the spec-ified update package.

Access Type: Exec, GetOccurrence: OneFormat: Node

./Fw/FwPkg01/Download/PkgURLThis node specifies the URL where the firmware update package or download descriptor is located.

Access Type: Get, ReplaceOccurrence: OneFormat: chr

./Fw/FwPkg01/UpdateThis interior node is a target of an Exec command invoked to initiate a firmware update for the specified update package.


./Fw/FwPkg01/Update/PkgDataThis node is the target of a Replace command when DM is used to provide the binary firmware update package directly.

Access Type: ReplaceOccurrence: OneFormat: bin

./Fw/FwPkg01/DownloadAndUpdateThis interior node is the target of an Exec command invoked to initiate a firmware download and an imme-diate update for the specified update package.


./Fw/FwPkg01/DownloadAndUpdate/PkgURLThis node specifies the URL where the firmware update package, that is to be downloaded and immedi-ately installed, or its download descriptor is located.


110 January 2008


Browser bookmarks

Subtree structure

./Com.SonyEricsson/Content/Browser/BookmarksAccess Type: GetOccurrence: OneFormat: Node

./Com.SonyEricsson/Content/Browser/Bookmarks/XAccess Type: Get, Add, DeleteOccurrence: ZeroOrMoreFormat: Node

./Com.SonyEricsson/Content/Browser/Bookmarks/X/TitleDisplayable title of the bookmark.

Access Type: Get, Add, ReplaceOccurrence: OneFormat: chrValues: String; max length 15

./Com.SonyEricsson/Content/Browser/Bookmarks/X/URLAccess Type: Get, Add, ReplaceOccurrence: OneFormat: chrValues: String; max length 512

./Com.SonyEricsson/Content/Browser/Bookmarks/X/FolderFolder in which the bookmark is grouped.

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

Bookmarks <X>* Title

URL

Folder?

111 January 2008


Third-party Java™ application download/installation(DM clients version 3.x only)

Subtree structure

./Com.SonyEricsson/Content/JavaApplicationsThis is a management object that allows listing, deleting and triggering of external download/installation of third-party Java™ applications.


./Com.SonyEricsson/Content/JavaApplications/DownloadUsed for downloading and installation of new third-party Java applications. The download mechanism works in much the same way as downloads of FOTA packets via OMA download. First a URL to a JAD or JAR file in the child node “JAD-URL” is specified, then an Execute command is performed on this node. The download starts directly after the current DM session has ended.

Currently, the only way of knowing if the download and installation were successful, is to look for the new application among the ones listed under "Installed" in a subsequent DM session.

If more than one Execute command is sent during the same session, only the first is successful but the pending download operation still starts when the DM session has ended.


./Com.SonyEricsson/Content/JavaApplications/Download/JAD-URLURL to the JAD or JAR file to download. If a URL is not specified prior to an Exec command on the Down-load node, the Execute command fails.

Access Type: Get, ReplaceOccurrence: OneFormat: chrAllowed values: String; URL

JavaApplications Download JAD-URL

Installed <X>* Name

Vendor

Version

Deletable

112 January 2008


./Com.SonyEricsson/Content/JavaApplications/InstalledThis node contains a list of the applications currently installed in the phone. New placeholders cannot be added, the only way to install new applications is to use the Download/JAD-URL mechanism. Applications flagged as “deletable” can be deleted by performing a Delete command on the corresponding place-holder.


./Com.SonyEricsson/Content/JavaApplications/Installed/XA placeholder for installed applications. The default naming convention lists applications on the form "JavaApp-XX" where XX is a running number starting with 01.

Access Type: Delete, Get, ReplaceOccurrence: ZeroOrMoreFormat: Node

./Com.SonyEricsson/Content/JavaApplications/Installed/X/NameThe name of the application.


./Com.SonyEricsson/Content/JavaApplications/Installed/X/VendorThe vendor string of the application.


./Com.SonyEricsson/Content/JavaApplications/Installed/X/VersionVersion information for the application.


./Com.SonyEricsson/Content/JavaApplications/Installed/X/DeletableFlag that indicates if the application can be removed or not. Note that deletable applications are removed without any user confirmation or even notification, so this flag should be used with care.

Access Type: GetOccurrence: OneFormat: bool

113 January 2008


Internet profile for Java applications

Subtree structure

./Com.SonyEricsson/Settings/JavaAccess Type: GetOccurrence: OneFormat: Node

./Com.SonyEricsson/Settings/Java/ProxyRefPath to the Internet profile placeholder in the DM tree which holds the Internet profile to be used, for example, "./AP/Proxy/proxy-01" (DM clients versions 1.0 and 2.0) or "./AP/Proxy/ProxyAcc/proxyAcc-01" (DM clients version 3.x).


Streaming settings

Subtree structure

./Com.SonyEricsson/Settings/StreamingAccess Type: GetOccurrence: OneFormat: Node

Value Description

"./AP/Proxy/<X>" DM client 1.0/2.0: <X> is the placeholder name for the linked account. The account must exist in the tree

"./AP/Proxy/ProxyAcc/<X>" DM client 3.x: <X> is the placeholder name for the linked account. The account must exist in the tree

Java ProxyRef

Streaming NAPRef

PxAddr

PxPortNbr

UsePx

114 January 2008


./Com.SonyEricsson/Settings/Streaming/NAPRefPath to the used data account placeholder in the DM tree, for example, "./AP/NAP/Nap-01".


./Com.SonyEricsson/Settings/Streaming/PxAddrAddress to proxy.

Access Type: Get, ReplaceOccurrence: OneFormat: chrAllowed values: String max length 511

./Com.SonyEricsson/Settings/Streaming/PxPortNbrProxy port number.

Access Type: Get, ReplaceOccurrence: OneFormat: intDefault value: 0Allowed values: Integer in range 0 to 65535

./Com.SonyEricsson/Settings/Streaming/UsePxIndicates if the proxy is used.

Access Type: Get, ReplaceOccurrence: OneFormat: boolDefault value: False

115 January 2008


MMS application settings

Subtree structure

./Com.SonyEricsson/Settings/MMSSettings for the MMS (picture messaging) application.


./Com.SonyEricsson/Settings/MMS/ReqReadRequest read report.


./Com.SonyEricsson/Settings/MMS/ReqDelRequest delivery report.


DM client 1.0 and 2.0 DM client 3.x

MMS ReqRead

ReqDel

SendRead

SendDel

ValPeriod

Pri

RejAdv

RejAno

SendVisible

AutoDownload

MMSC

ProxyRef

MMS ReqDel

ReqRead

SendRead

SendDel

ValPeriod

Pri

RejAdv

RejAno

SendVisible

AutoDownload

ActiveProfileRef

MMSProfile <X>* Name

MMSC

ProxyRef

116 January 2008


./Com.SonyEricsson/Settings/MMS/SendReadSend read report.

Access Type: Get, ReplaceOccurrence: OneFormat: chrDefault value: “Conf”Allowed values:

./Com.SonyEricsson/Settings/MMS/SendDelSend delivery report.

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

./Com.SonyEricsson/Settings/MMS/ValPeriodValidity period.

Access Type: Get, ReplaceOccurrence: OneFormat: chrDefault value: “Maximum”Allowed values:

Value Description

"On"

"Off"

"Conf" Lets the user confirm

Value Description

“1h” One hour

“12h” 12 hours

“1day” 24 hours

“1week” One week

“Maximum” Network maximum

117 January 2008


./Com.SonyEricsson/Settings/MMS/PriMessage priority.

Access Type: Get, ReplaceOccurrence: OneFormat: chrDefault value: “Normal”Allowed values: “Low”, “Normal”, “High”, “Unknown”

./Com.SonyEricsson/Settings/MMS/RejAdvReject advertisement.


./Com.SonyEricsson/Settings/MMS/RejAnoReject anonymous.


./Com.SonyEricsson/Settings/MMS/SendVisibleSender visible.

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

./Com.SonyEricsson/Settings/MMS/AutoDownloadDetermines under which circumstances Auto download is allowed.

Access Type: Get, ReplaceOccurrence: OneFormat: chrDefault value: “Always”Allowed values: “Always”, “AskInRoaming”, “NeverInRoaming”, “Ask”, “Never”

./Com.SonyEricsson/Settings/MMS/MMSC(DM client 1.0 and 2.0 only)Message server address.

Access Type: Get, ReplaceOccurrence: OneFormat: chrAllowed values: String Max length 50 (Values are defined in 3GPP TS 23.140)

118 January 2008


./Com.SonyEricsson/Settings/MMS/ProxyRef(DM client 1.0 and 2.0 only)Path to the Internet profile placeholder in the DM tree which holds the Internet profile to be used, for example, "./AP/Proxy/proxy-01".


./Com.SonyEricsson/Settings/MMS/ActiveProfileRef(DM client 3.x only)Path to the currently active MMS profile placeholder in the DM tree, for example, "./Com.SonyEricsson/Settings/MMS/MMSProfile/MMSProfile-01", if a profile named "MMSProfile-01" exists.


./Com.SonyEricsson/Settings/MMS/Profile(DM client 3.x only)Container for a number of possible MMS profiles.


./Com.SonyEricsson/Settings/MMS/Profile/X(DM client 3.x only)This node acts as a placeholder for an MMS profile.


./Com.SonyEricsson/Settings/MMS/Profile/X/Name(DM client 3.x only)Displayable name for this profile.

Access Type: Add, Get, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 16

Value Description

"./Com.SonyEricsson/Settings/MMS/MMSPro-file/<X>"

<X> is the placeholder name for the linked account. The account must exist in the tree

119 January 2008


./Com.SonyEricsson/Settings/MMS/Profile/X/MMSC(DM client 3.x only)Message server address.

Access Type: Add, Get, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 50. Values are defined in 3GPP TS 23.140

./Com.SonyEricsson/Settings/MMS/Profile/X/ProxyRef(DM client 3.x only)Path to the Internet profile placeholder in the DM tree which holds the Internet profile to be used, for example, "./AP/Proxy/ProxyAcc/ProxyAcc-01".

Access Type: Add, Get, ReplaceOccurrence: OneFormat: chrAllowed values:

SMS settings

Subtree structure

./Com.SonyEricsson/Settings/SMSSettings for the SMS (text messaging) application.


Value Description

"./AP/Proxy/ProxyAcc/<X>" <X> is the placeholder name for the linked account. The account must exist in the tree

SMS ProtocolType

SMSCenterList

EmailGatewayList

ConcatEnable

ValPeriod

ReqStatus

ReqReply

120 January 2008


./Com.SonyEricsson/Settings/SMS/ProtocolTypeProtocol type.

Access Type: Get, ReplaceOccurrence: OneFormat: chrDefault Value: “Text”Allowed values: “Text”, “Email”, “FaxGroup3”, “FaxGroup4”, “Voice”, “ERMES”, “Pager”

./Com.SonyEricsson/Settings/SMS/SMSCenterListA comma-separated list of SMS Center addresses (phone numbers). Usually a maximum of 5 numbers (depends on the limits of the SIM in use) of maximum 20 characters each, including optional leading "+". Valid characters are "0"-"9", "*" and "#". Example: "+4640107107,1234,8*4#21".

Note: If more than the maximum numbers are replaced, the DM client indicates this error with a status of 400, but the first correct numbers are accepted. Thus, a subsequent Get on the node returns the (typically) 5 first numbers of the failed replace.


./Com.SonyEricsson/Settings/SMS/EmailGatewayListA comma-separated list of SMS Email Gateway addresses (phone numbers). Usually a maximum of 5 numbers (depends on the limits of the SIM in use) of maximum 20 characters each, including optional leading "+". Valid characters are "0"-"9", "*" and "#". Example: "+4640107107,1234,8*4#21".

Note: If more than the maximum numbers are replaced, the DM client indicates this error with a status of 400, but the first correct numbers are accepted. Thus a subsequent Get on the node returns the (typically) 5 first numbers of the failed replace.


./Com.SonyEricsson/Settings/SMS/ConcatEnableAllows concatenated messages.

Access Type: Get, ReplaceOccurrence: OneFormat: boolDefault Value: True

121 January 2008


./Com.SonyEricsson/Settings/SMS/ValPeriodValidity period.

Access Type: Get, ReplaceOccurrence: OneFormat: chrDefault Value: “Maximum”Allowed values:

./Com.SonyEricsson/Settings/SMS/ReqStatusRequest delivery status report.

Access Type: Get, ReplaceOccurrence: OneFormat: boolDefault Value: False

./Com.SonyEricsson/Settings/SMS/ReqReplyRequest reply.


Value Description

“1h” One hour

“12h” 12 hours

“1day” 24 hours

“1week” One week

“Maximum” Network maximum

122 January 2008


Email accounts

Subtree structure

./Com.SonyEricsson/Settings/EmailAccess Type: GetOccurrence: OneFormat: Node

./Com.SonyEricsson/Settings/Email/XPlaceholder representing an email account.


./Com.SonyEricsson/Settings/Email/X/NameDisplayable name for the account.


Email <X>* Name?

NAPRef?

Active?

RecAccount? Mailbox?

Password?

Server?

PortNbr?

ServerProtocol?

CheckMailsInterval?

AutomaticDownload?

EnableTLS?

SMTPAccount? Name?

EmailAddr?

Server?

PortNbr?

Signature?

BCCOutgoing?

BCCOutgoingAddr?

UserName?

Password?

EnableTLS?

123 January 2008


./Com.SonyEricsson/Settings/Email/X/NAPRefPath to the used data account placeholder in the DM tree, for example, "./AP/NAP/Nap-01".


./Com.SonyEricsson/Settings/Email/X/ActiveOnly one account can be active at a time, and this setting indicates whether this is the currently active account. Replacing the value with True, automatically sets the Active node for all other accounts to False, indicating that the selected account is now active. Replacing this with False has no effect, since exactly one account always must be active.

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

./Com.SonyEricsson/Settings/Email/X/RecAccountIncoming mail settings.


./Com.SonyEricsson/Settings/Email/X/RecAccount/MailboxIncoming mailbox.


./Com.SonyEricsson/Settings/Email/X/RecAccount/PasswordPassword.


./Com.SonyEricsson/Settings/Email/X/RecAccount/ServerServer name.


124 January 2008


./Com.SonyEricsson/Settings/Email/X/RecAccount/PortNbrPort number.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: intDefault value: 110Allowed values: Integer; 0 to 65535

./Com.SonyEricsson/Settings/Email/X/RecAccount/ServerProtocolIncoming server protocol.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault value: “Pop3”Allowed values: “Pop3”, “IMAP”

./Com.SonyEricsson/Settings/Email/X/RecAccount/CheckMailsIntervalAutomatic poll interval in seconds.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: intDefault value: 0Allowed values: 0, 300, 1800, 3600, 7200, 10800, 14400, 43200

./Com.SonyEricsson/Settings/Email/X/RecAccount/AutomaticDownloadAutomatic download of new email.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: DM client v1.0: boolDM client v2.0 and 3.x: chrDefault value:DM client v1.0: FalseDM client v2.0 and 3.x: "headers and text"Allowed values DM client v2.0 and 3.x:"headers and text""headers only""headers and text and attachments"

125 January 2008


./Com.SonyEricsson/Settings/Email/X/RecAccount/EnableTLSUse TLS security.Not implemented in DM client v 1.0.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault value: “None“Allowed values: “None”, “SSL”, “TLS”

./Com.SonyEricsson/Settings/Email/X/SMTPAccountOutgoing mail settings.


./Com.SonyEricsson/Settings/Email/X/SMTPAccount/NameOutgoing name.


./Com.SonyEricsson/Settings/Email/X/SMTPAccount/EmailAddrEmail address.


./Com.SonyEricsson/Settings/Email/X/SMTPAccount/ServerOutgoing server.


./Com.SonyEricsson/Settings/Email/X/SMTPAccount/PortNbrPort number.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: IntDefault value: 25Allowed values: Integer; range 0 to 65535

126 January 2008


./Com.SonyEricsson/Settings/Email/X/SMTPAccount/SignatureSignature.


./Com.SonyEricsson/Settings/Email/X/SMTPAccount/BCCOutgoingEnable automatic BCC of outgoing mail.

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

./Com.SonyEricsson/Settings/Email/X/SMTPAccount/BCCOutgoingAddrEmail address for auto BCC.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: String; max length 80 (Valid email address)

./Com.SonyEricsson/Settings/Email/X/SMTPAccount/UserNameSMTP username.


./Com.SonyEricsson/Settings/Email/X/SMTPAccount/PasswordSMTP password.


./Com.SonyEricsson/Settings/Email/X/SMTPAccount/EnableTLSUse TLS security. Not implemented in DM client v1.0.

Access Type: Add, Get, ReplaceOccurrence: ZeroOrOneFormat: chrDefault value: “None“Allowed values: “None”, “SSL”, “TLS”

127 January 2008


My Friends (Wireless Village) settings

Note: Wireless village is not supported in DM clients version 3.2 (i-mode phones).

Subtree structure

./Com.SonyEricsson/Settings/WVSettings for the "My Friends" application (Wireless Village).


./Com.SonyEricsson/Settings/WV/UserIdUser ID.

Access Type: Get, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 50, Format: “wv:user@domain”

./Com.SonyEricsson/Settings/WV/PasswordUser password.

Access Type: ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 50

./Com.SonyEricsson/Settings/WV/SAPURIServer URL.

Access Type: Get, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 200, URL

WV UserId

Password

SAPURI

ProxyRef

AutoLogin

Roam

IsAvail

128 January 2008


./Com.SonyEricsson/Settings/WV/ProxyRefPath to the Internet profile placeholder in the DM tree which holds the Internet profile to be used, for example, "./AP/Proxy/proxy-01".


./Com.SonyEricsson/Settings/WV/AutoLoginEnable/disable auto login.


./Com.SonyEricsson/Settings/WV/RoamAllow connection if roaming.


./Com.SonyEricsson/Settings/WV/IsAvailIndicates if the application is enabled (read-only).

Access Type: GetOccurrence: OneFormat: boolDefault Value: True

129 January 2008


OMA Data Sync accounts (DM clients versions 2.0 and 3.x)

Note: For DM client version 1.0, the OMA DS subtree is found under the ./SyncML node, see “OMA Data Sync accounts (DM client version 1.0 only)” on page 80.

Subtree structure (DM client version 2.0)

DSAcc <X>* Name?

Addr

ClientName?

ClientPW?

ClientNonce?

ServerId

ServerPW

ServerNonce

ProxyRef?

DB? Cal? RDBURI?

UserName?

UserPW?

Enabled?

PB? RDBURI?

UserName?

UserPW?

Enabled?

Notes? RDBURI?

UserName?

UserPW?

Enabled?

ToDo? RDBURI?

UserName?

UserPW?

Enabled?

130 January 2008


Subtree structure (DM clients version 3.x)

./Com.SonyEricsson/Settings/Sync/DSAccOMA DS accounts.


./Com.SonyEricsson/Settings/Sync/DSAcc/XAccess Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrN (N<=5)Format: Node

DSAcc <X>* Name?

Addr

ClientName?

ClientPW?

ClientNonce?

ServerId

ServerPW

ServerNonce

ProxyRef?

HTTP_UserName

HTTP_PW

DB? Cal? RDBURI?

UserName?

UserPW?

Enabled?

PB? RDBURI?

UserName?

UserPW?

Enabled?

Notes? RDBURI?

UserName?

UserPW?

Enabled?

ToDo? RDBURI?

UserName?

UserPW?

Enabled?

Bookmarks? RDBURI?

UserName?

UserPW?

Enabled?

131 January 2008


./Com.SonyEricsson/Settings/Sync/DSAcc/X/NameDisplayable name for this account.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/AddrServer address. Note: For DM client v2.0, the server URL does not need to be unique.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/ClientNameClient identity; used for client authentication.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/ClientPWClient password; used for client authentication.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/ClientNonceNext nonce to be used for client authentication.

Access Type: Add, ReplaceOccurrence: ZeroOrOneFormat: chrAllowed values: String; max length 34 bytes

./Com.SonyEricsson/Settings/Sync/DSAcc/X/ServerIdServer identity; used for server authentication.


132 January 2008


./Com.SonyEricsson/Settings/Sync/DSAcc/X/ServerPWServer password; used for server authentication.

Access Type: Add, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 59

./Com.SonyEricsson/Settings/Sync/DSAcc/X/ServerNonceAccess Type: Add, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 34

./Com.SonyEricsson/Settings/Sync/DSAcc/X/ProxyRefPath to the Internet profile placeholder in the DM tree which holds the Internet profile to be used, for example, "./AP/Proxy/proxy-01".


./Com.SonyEricsson/Settings/Sync/DSAcc/X/HTTP_UserName(DM clients version 3.x only)Username for HTTP authentication.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/HTTP_PW(DM clients version 3.x only)Password for HTTP authentication.

Access Type: Add, ReplaceOccurrence: OneFormat: chrAllowed values: String; max length 59

./Com.SonyEricsson/Settings/Sync/DSAcc/X/DBSync databases.


133 January 2008


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/CalApplication settings for Calendar sync.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Cal/RDBURIDatabase name.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Cal/UserNameUsername.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Cal/UserPWPassword.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Cal/EnabledIndicates if this application should be synchronized.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/PBApplication settings for Contacts (Phonebook) sync.


134 January 2008


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/PB/RDBURIDatabase name.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/PB/UserNameUsername.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/PB/UserPWPassword.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/PB/EnabledIndicates if this application should be synchronized.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/NotesApplication settings for Notes sync.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Notes/RDBURIDatabase name.


135 January 2008


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Notes/UserNameUsername.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Notes/UserPWPassword.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Notes/EnabledIndicates if this application should be synchronized.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/ToDoApplication settings for Tasks sync.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/ToDo/RDBURIDatabase name.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/ToDo/UserNameUsername.


136 January 2008


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/ToDo/UserPWPassword.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/ToDo/EnabledIndicates if this application should be synchronized.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Bookmarks(DM clients version 3.x only)Application settings for Bookmarks sync.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Bookmarks/RDBURI(DM clients version 3.x only)Database name.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Bookmarks/UserName (DM clients version 3.x only)Username.


137 January 2008


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Bookmarks/UserPW(DM clients version 3.x only)Password.


./Com.SonyEricsson/Settings/Sync/DSAcc/X/DB/Bookmarks/Enabled(DM clients version 3.x only)Indicates if this application should be synchronized.


Sony Ericsson Update Service (DM clients versions 2.0 and 3.x only)

Note: Not applicable to DM client version 1.0.

Subtree structure

./Com.SonyEricsson/Settings/FOTASettings for the Sony Ericsson Update Service application.


FOTA ReminderInterval

NextReminderTime

History

138 January 2008


./Com.SonyEricsson/Settings/FOTA/ReminderIntervalThis node specifies when the next notification is presented to the user.

Access Type: Get, ReplaceOccurrence: OneFormat: chrDefault Value: “Off“Allowed values:

./Com.SonyEricsson/Settings/FOTA/NextReminderTime(Read only) The UTC DateTime for the next notification if ReminderInterval is set to "1 Month". When ReminderInterval is "Off" or "At Startup", the value is 0.

Access Type: GetOccurrence: OneFormat: intDefault Value: 0Allowed values: Integer; number of seconds since midnight 1/1 1970 to the time for the next reminder

./Com.SonyEricsson/Settings/FOTA/History(Read-only) History log of Firmware Update operations, in readable ASCII plain text.


Dummy tree extensions

Subtree structure

./Com.SonyEricsson/ExtThe Ext subtree is an area where undefined “dummy” nodes can be added. Primarily for testing purposes, these nodes are added to the DM tree but do not affect the phone or its applications in any way (other than consuming space).


Value Description

“Off” No automatic reminders

“At Startup” Reminder when the phone starts up

“1 Month” Reminder every month

Ext <X>* <X>*

139 January 2008


./Com.SonyEricsson/Ext/XPlaceholder for dummy leaves. Dummy leaves must always be placed under a placeholder Node object at this level.

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

./Com.SonyEricsson/Ext/X/XDummy leaf nodes can have any name and any format except “Node”, that is, it is only possible to have one level of interior placeholder nodes under the Ext node.

Access Type: Add, Delete, Get, ReplaceOccurrence: ZeroOrMoreFormat: null

140 January 2008


General DM examples

Adding a new CSD data account for clients with DevInfo/DmV = 1.x

This applies to DM client version 1.0 only.

Note: Example data, like server addresses, are for illustrative purposes only.

<SyncBody><Add>

<CmdID>4</CmdID><Item>

<Target><LocURI>./AP/NAP/myOperator_CSD</LocURI>

</Target><Meta>

<Format xmlns="syncml:metinf">node</Format></Meta>

</Item></Add><Add>


<Target><LocURI>./AP/NAP/myOperator_CSD/Name</LocURI>

</Target><Data>myOperator GSM</Data>

</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_CSD/AuthInfo</LocURI>

</Target><Meta>


</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_CSD/AuthInfo/AuthName</LocURI>

</Target><Data>someAuthName</Data>

</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_CSD/AuthInfo/AuthSecret</LocURI>

</Target><Data>someAuthSecret</Data>

</Item><Item><Target>

141 January 2008


<LocURI>./AP/NAP/myOperator_CSD/AuthInfo/AuthPrompt</LocURI></Target><Data>false</Data></Item><Item>

<Target><LocURI>./AP/NAP/myOperator_CSD/IPv4</LocURI>

</Target><Meta>


</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_CSD/IPv4/DNS</LocURI>

</Target><Data>10.20.30.40</Data>

</Item>

Note: It is essential that the CSD node and at least one of the subnodes, for example, DialString, are added, and that none of the GPRS subnodes are added, for this account to be created correctly. These have to be added in the same DM message as where the account placeholder is added.

<Item><Target>

<LocURI>./AP/NAP/myOperator_CSD/CSD</LocURI></Target><Meta>


</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_CSD/CSD/DialString</LocURI>

</Target><Data>+4688812341234</Data>

</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_CSD/CSD/DataRate</LocURI>

</Target><Data>9600</Data>

</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_CSD/Locked</LocURI>

</Target><Data>false</Data>

</Item></Add><Final/>

</SyncBody>

142 January 2008


Adding a new CS Data account for clients with DevInfo/DmV = 2.x or 3.0

This applies to DM clients version 2.0 and 3.0 only. DM client version 3.1 does not support CS Data accounts.


<SyncBody><Add>


<Target><LocURI>./AP/NAP_CSD/myOperator_CSD</LocURI>

</Target><Meta>


</Item></Add><Add>


<Target><LocURI>./AP/NAP_CSD/myOperator_CSD/Name</LocURI>

</Target><Data>myOperator CSD</Data>

</Item><Item>

<Target><LocURI>./AP/NAP_CSD/myOperator_CSD/AuthName</LocURI>


</Item><Item>

<Target><LocURI>./AP/NAP_CSD/myOperator_CSD/AuthSecret</LocURI>

</Target><Data>someAuthPassword</Data>

</Item><Item>

<Target><LocURI>./AP/NAP_CSD/myOperator_CSD/AuthPrompt</LocURI>


</Item><Item>

<Target><LocURI>./AP/NAP_CSD/myOperator_CSD/AuthType</LocURI>

</Target><Data>PAP</Data>

</Item><Item>

<Target>

143 January 2008


<LocURI>./AP/NAP_CSD/myOperator_CSD/DialString</LocURI></Target><Data>+4688812341234</Data>

</Item><Item>

<Target><LocURI>./AP/NAP_CSD/myOperator_CSD/DataRate</LocURI>


</Item><Item>

<Target><LocURI>./AP/NAP_CSD/myOperator_CSD/Locked</LocURI>

</Target><Data>true</Data>


</SyncBody>

Adding a new PSD data account for clients with DevInfo/DmV = 1.x

This applies to DM client version1.0 only.

Note: Example data, for example, server address, is for illustrative purpose only.

<SyncBody><Add>


<Target><LocURI>./AP/NAP/myOperator_PSD</LocURI>

</Target><Meta>


</Item></Add><Add>


<Target><LocURI>./AP/NAP/myOperator_PSD/Name</LocURI>

</Target><Data>myOperator GPRS</Data>

</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_PSD/AuthInfo</LocURI>

</Target>

144 January 2008


<Meta><Format xmlns="syncml:metinf">node</Format>

</Meta></Item><Item>

<Target><LocURI>./AP/NAP/myOperator_PSD/AuthInfo/AuthName</LocURI>


</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_PSD/AuthInfo/AuthSecret</LocURI>

</Target><Data>someAuthSecret</Data>

</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_PSD/AuthInfo/AuthPrompt</LocURI>


</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_PSD/IPv4</LocURI>

</Target><Meta>


</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_PSD/IPv4/DNS</LocURI>


</Item>

Note: It is essential that the GPRS node and at least one of the subnodes (for example APN) are added, and that none of the CSD subnodes are added, for this account to be created correctly. These have to be added in the same DM message as where the account placeholder is added.

<Item><Target>

<LocURI>./AP/NAP/myOperator_PSD/GPRS</LocURI></Target><Meta>


</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_PSD/GPRS/APN</LocURI>

</Target><Data>online.myoperator.com</Data>

</Item>

145 January 2008


<Item><Target>

<LocURI>./AP/NAP/myOperator_PSD/GPRS/AuthType</LocURI></Target><Data>None</Data>

</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_PSD/GPRS/Addr</LocURI>


</Item><Item>

<Target><LocURI>./AP/NAP/myOperator_PSD/Locked</LocURI>



</SyncBody>

Adding a new PSD data account for clients with DevInfo/DmV = 2.x or 3.x

This applies to DM clients versions 2.0 or 3.x only.


<SyncBody><Add>


<Target><LocURI>./AP/NAP_PSD/myOperator_PSD</LocURI>

</Target><Meta>


</Item></Add><Add>


<Target><LocURI>./AP/NAP_PSD/myOperator_PSD/Name</LocURI>

</Target><Data>myOperator PSD</Data>

</Item><Item>

<Target>

146 January 2008


<LocURI>./AP/NAP_PSD/myOperator_PSD/AuthName</LocURI></Target><Data>someAuthName</Data>

</Item><Item>

<Target><LocURI>./AP/NAP_PSD/myOperator_PSD/AuthSecret</LocURI>

</Target><Data>someAuthPassword</Data>

</Item><Item>

<Target><LocURI>./AP/NAP_PSD/myOperator_PSD/AuthPrompt</LocURI>


</Item><Item>

<Target><LocURI>./AP/NAP_PSD/myOperator_PSD/AuthType</LocURI>

</Target><Data>PAP</Data>

</Item><Item>

<Target><LocURI>./AP/NAP_PSD/myOperator_PSD/APN</LocURI>

</Target><Data>online.myoperator.com</Data>

</Item><Item>

<Target><LocURI>./AP/NAP_PSD/myOperator_PSD/ServiceMode</LocURI>

</Target><Data>Exclusive</Data>

</Item><Item>

<Target><LocURI>./AP/NAP_PSD/myOperator_PSD/Locked</LocURI>

</Target><Data>true</Data>


</SyncBody>

Adding a new DM account

Note: Example data, for example, server address, is for illustrative purpose only.

<SyncBody><Add>

<CmdID>4</CmdID>

147 January 2008


<Item><Target>

<LocURI>./SyncML/DMAcc/aNewDMAcc</LocURI></Target><Meta>


</Item></Add><Add>


<Target><LocURI>./SyncML/DMAcc/aNewDMAcc/Addr</LocURI>

</Target><Data>http://some.server.com/DevMan</Data>

</Item><Item>

<Target><LocURI>./SyncML/DMAcc/aNewDMAcc/PortNbr</LocURI>


</Item><Item>

<Target><LocURI>./SyncML/DMAcc/aNewDMAcc/ConRef</LocURI>

</Target><Data>./AP/Proxy/myOperatorISP</Data> 

</Item><Item>

<Target><LocURI>./SyncML/DMAcc/aNewDMAcc/ServerId</LocURI>

</Target><Data>myOperator</Data>

</Item><Item>

<Target><LocURI>./SyncML/DMAcc/aNewDMAcc/ServerPW</LocURI>

</Target><Data>SecretServer</Data>

</Item><Item>

<Target><LocURI>./SyncML/DMAcc/aNewDMAcc/UserName</LocURI>

</Target><Data>UserName</Data>

</Item><Item>

<Target><LocURI>./SyncML/DMAcc/aNewDMAcc/ClientPW</LocURI>

</Target><Data>ClientSecret</Data>

</Item><Item>

148 January 2008


<Target><LocURI>./SyncML/DMAcc/aNewDMAcc/AuthPref</LocURI>

</Target><Data>syncml:auth-md5</Data>

</Item><Item>

<Target><LocURI>./SyncML/DMAcc/aNewDMAcc/Name</LocURI>



</SyncBody>

Adding a new Email account


<SyncBody><Add>


<Target><LocURI>./Com.SonyEricsson/Settings/Email/myOperator_Mail</LocURI>

</Target><Meta>


</Item></Add><Add>


<Target><LocURI>./Com.SonyEricsson/Settings/Email/myOperator_Mail/Name</

LocURI></Target><Data>myOperator</Data>

</Item><Item>

<Target><LocURI>./Com.SonyEricsson/Settings/Email/myOperator_Mail/

RecAccount</LocURI></Target><Meta>


</Item><Item>

<Target>

149 January 2008


<LocURI>./Com.SonyEricsson/Settings/Email/myOperator_Mail/RecAccount/Mailbox</LocURI>

</Target><Data>[email protected]</Data>

</Item><Item>

<Target><LocURI>./Com.SonyEricsson/Settings/Email/myOperator_Mail/RecAccount/

Password</LocURI></Target><Data>usersecret</Data>

</Item><Item>


Server</LocURI></Target><Data>pop.myoperator.com</Data>

</Item><Item>


PortNbr</LocURI></Target><Data>110</Data>

</Item><Item>


ServerProtocol</LocURI></Target><Data>Pop3</Data>

</Item><Item>


CheckMailsInterval</LocURI></Target><Data>0</Data>

</Item><Item>


AutomaticDownload</LocURI></Target><Data>headers and text</Data>

</Item><Item>


SMTPAccount</LocURI></Target><Meta>


150 January 2008


</Item><Item>


SMTPAccount/Name</LocURI></Target><Data>User Name</Data>

</Item><Item>


SMTPAccount/EmailAddr</LocURI></Target><Data>[email protected]</Data>

</Item><Item>


SMTPAccount/Server</LocURI></Target><Data>mail.myoperator.com</Data>

</Item><Item>


SMTPAccount/PortNbr</LocURI></Target><Data>25</Data>

</Item><Item>


SMTPAccount/Signature</LocURI></Target><Data> -- Audio, Video, Disco -- </Data>

</Item><Item>


SMTPAccount/BCCOutgoing</LocURI></Target><Data>true</Data>

</Item><Item>


SMTPAccount/BCCOutgoingAddr</LocURI></Target><Data>[email protected]</Data>

</Item><Item>


SMTPAccount/UserName</LocURI></Target>

151 January 2008


<Data>SMTPusername</Data></Item><Item>


SMTPAccount/Password</LocURI></Target><Data>SMTPuserpwd</Data>

</Item><Item>

<Target><LocURI>./Com.SonyEricsson/Settings/Email/myOperator_Mail/NAPRef</

LocURI></Target><Data>./AP/NAP_PSD/myOperator_PSD</Data> 

</Item><Item>

<Target><LocURI>./Com.SonyEricsson/Settings/Email/myOperator_Mail/Active</

LocURI></Target><Data>true</Data>


</SyncBody>

Adding a new Internet account

Note: Example data are for illustrative purposes only.

<SyncBody><Add>


<Target><LocURI>./AP/Proxy/myOperatorISP</LocURI>

</Target><Meta>


</Item></Add><Add>


<Target><LocURI>./AP/Proxy/myOperatorISP/Name</LocURI>


152 January 2008


</Item><Item>

<Target><LocURI>./AP/Proxy/myOperatorISP/PxAddr</LocURI>

</Target><Data>proxy.myOperator.com</Data>

</Item><Item>

<Target><LocURI>./AP/Proxy/myOperatorISP/PortNbr</LocURI>


</Item><Item>

<Target><LocURI>./AP/Proxy/myOperatorISP/NAPRef</LocURI>

</Target><Meta>


</Item><Item>

<Target><LocURI>./AP/Proxy/myOperatorISP/NAPRef/PrefNAPRef</LocURI>

</Target><Data>./AP/NAP_PSD/myOperator_PSD</Data> 

</Item><Item>

<Target><LocURI>./AP/Proxy/myOperatorISP/NAPRef/SecNAPRef</LocURI>

</Target><Data>./AP/NAP_PSD/myOperator_CSD</Data> 

</Item><Item>

<Target><LocURI>./AP/Proxy/myOperatorISP/PxAuthInfo</LocURI>

</Target><Meta>


</Item><Item>

<Target><LocURI>./AP/Proxy/myOperatorISP/PxAuthInfo/PxAuthId</LocURI>

</Target><Data>http-authName</Data>

</Item><Item>

<Target><LocURI>./AP/Proxy/myOperatorISP/PxAuthInfo/PxAuthPW</LocURI>

</Target><Data>http-secret</Data>

</Item>

153 January 2008


<Item><Target>

<LocURI>./AP/Proxy/myOperatorISP/UseProxy</LocURI></Target><Data>true</Data>


</SyncBody>

154 January 2008


Appendix

In this appendix, the W550 series is used as an example of how the Sony Ericsson Device Management client conforms to the requirements defined by OMA.

155 January 2008


DM client conformance

In this chapter, conformance of the Sony Ericsson Device Management client implementation is specified in relation to the conformance requirements defined by OMA. Only features that are not compliant with the OMA requirements are explicitly listed in tables. The Requirement columns show requirement levels according to the normative document, for example, MUST, SHOULD and MAY.

The document Device Management Conformance Requirements specifies all DM server and DM client conformance requirements and can be found at http://www.openmobilealliance.org/release_program/dm_v112.html.

The W550 DM client implementation conformance

Representation: Common use elementsAll features are implemented according to requirements.

Representation: Message container elementsAll features are implemented according to requirements.

Representation: Data description elementsAll features are implemented according to requirements.

Representation: Protocol command elementsAll features are implemented according to requirements, except the following:

SyncML DM protocolAll features are implemented according to requirements, except the following:

Command Required of Client Implemented in Client

Receiving Receiving

Atomic SHOULD no (the command is supported, but not the feature)

Copy MAY no

Alert type Required of Client Implemented in Client

Receiving Receiving

Client Event Alert MAY no

156 January 2008




SyncML DM MetaInfoAll features are implemented according to requirements, except the following:

SyncML DM security

Secure transport classAll features are implemented according to requirements.

General transport classAll features are implemented according to requirements.

SyncML DM notificationAll features are implemented according to requirements.

SyncML DM standardized objectsAll features are implemented according to requirements.

SyncML DM bootstrapAll features are implemented according to requirements, except the following:

SyncML DM tree and descriptionAll features are implemented according to requirements, except the following:

Alert type Required of Client Implemented in Client

Sending Receiving Sending Receiving

EMI MAY MAY no no

Command Required of Client Implemented in Client

Receiving Receiving

Plain Profile MAY no

Property Required of Client Implemented in Client

Tstamp MAY no

Type (interior nodes) MUST no

Verno MAY no

157 January 2008


HTTP transportAll features are implemented according to requirements, except the following:

Method Required Implemented

OPTIONS MAY no

HEAD MAY no

PUT MAY no

DELETE MAY no

TRACE MAY no

CONNECT MAY no

General headers Required Implemented

Cache-Control: no-store, private

MUST yes, no

Connection MAY no

Date MAY no

Pragma MAY no

Trailer MAY no

Upgrade MAY no

Via MAY no

Warning MAY no

Request headers Required Implemented

Accept-Encoding MAY no

Expect MAY no

From MAY no

Host MAY no

If-Match MAY no

If-none-Match MAY no

If-Range MAY no

If-Unmodified-Since MAY no

Max-Forwards MAY no

Proxy-Authorization MAY no

Range MAY no

158 January 2008


OBEX transportNot implemented.

WSP transportAll features are implemented according to requirements.

Referer MAY no

TE MAY no

Response headers Required Implemented

Accept-Ranges MAY no

Allow MAY no

Authentication-Info MAY no

Etag MAY no

Location MAY no

Proxy-Authenticate MAY no

Retry-After MAY no

Server MAY no

Vary MAY no

Request headers Required Implemented

159 January 2008

Documents

OMA Client Provisioning and Device Management