April 2005 Client provisioning - Sony Mobile · ported by Sony Ericsson Client Provisioning on the card, ... proxy selection and parameter prioritization when ... CSD is mapped to

April 2005

Client provisioning

Developers Guideline Client provisioning

Preface

Purpose of this document

This document contains general guidelines for developers and for operators to configure Sony Ericsson handsets with settings according to OMA client Provisioning v1.1

People who can benefit from this document are:

Software developers Operators and service providers

Content providers

It is assumed that the reader is familiar with OMA-ERELD-ClientProvisioning-v1_1-20021115-C, which can be found at http://www.openmobilealliance.org.

2 April 2005

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 00 Fax: +46 46 19 41 00 www.SonyEricsson.com/

Sony Ericsson Mobile Communications AB, 2005. 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.

First edition (April 2005) Publication number: EN/LZT 108 7987 R1A

http://www.openmobilealliance.org


Sony Ericsson Developer World

On www.SonyEricsson.com/developer, developers will find documentation and tools such as phone White Papers, Developers Guidelines for different technologies, SDKs and relevant APIs. The website also con-tains discussion forums monitored by the Sony Ericsson Developer Support team, an extensive Knowl-edge Base, Tips & 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 website.

Document conventions

Products

The table below lists Sony Ericsson mobile phones with support for Client provisioning. They are referred to using generic names as follows:

Generic names Series

Sony Ericsson mobile phones

V800 V800i, Vodafone 802SE

Z800 Z800i

K750 K750i, K750c, D750i

W800 W800i, W800c

K600 K600i

3 April 2005

www.SonyEricsson.com/developer


Terminology

Typographical Conventions

Code is written in Courier font: ..

Document history

GSM Global System for Mobile communications

IMPS Instant Messaging and Presence Services

MMS Multimedia Messaging Service

MS Mobile System

OMA Open Mobile Alliance

OTA Over The Air

SMS Short Message Service

WAP Wireless Application Protocol

WBXML WAP Binary XML

WIM WAP Identity Module

WV Wireless Village (IMPS)

Change history

2005-04-29 Version R1A First version published

4 April 2005


5 April 2005

Contents

Overview ......................................................................................................................6

Architecture .................................................................................................................7 OMA Client Provisioning in Sony Ericsson phones ...................................................8 OMA Client Provisioning document reception ......................................................8 Error handling ........................................................................................................9 Security mechanisms ..............................................................................................10 Parameters and compliance ...................................................................................10 PXLOGICAL .........................................................................................................10 NAPDEF ...............................................................................................................12 BOOTSTRAP .......................................................................................................14 Applications specific settings ..................................................................................15 Browser - APPID w2 .........................................................................................17 MMS - APPID W4 .............................................................................................18 Data Synchronization (SyncML DS) - w5 .........................................................19 Device Management (SyncML DM) - w7 ..........................................................21 Email, SMTP - 25 ..............................................................................................23 Email, POP3 - 110 ............................................................................................25 Email, IMAP4 - 143 ...........................................................................................26 Streaming (3GPP) - 554 ....................................................................................28 IMPS (WV) ............................................................................................................29 General examples ...................................................................................................31 References ..............................................................................................................38


Overview

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.

With OMA Client Provisioning v1.1 it is possible for the operator to configure (bootstrap) the terminal with settings for different applications in mobile phones (Browser, Email, Streaming, SyncML, Wireless Village, and so on). The Sony Ericsson implementation supports bootstrap from SIM and over-the-air (OTA) via SMS.

The bootstrap process is initiated when an unconfigured mobile phone is started from its initial state or after a Master reset.

6 April 2005


Architecture

The OMA Client Provisioning 1.1 specification states: Provisioning is the process by which a WAP client is configured with a minimum of user interactions. In this chapter, the client provisioning implementation in Sony Ericsson mobile phones is described.

7 April 2005


OMA Client Provisioning in Sony Ericsson phones

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

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

As an option, the provisioning documents can be delivered using WIM or SIM cards. The Requester inter-face 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 storing areas sup-ported by Sony Ericsson Client Provisioning on the card, Bootstrap, Config1 and Config2.

There are mandatory rules for how the security mechanisms are to be used and how the provisioning doc-uments delivered through different channels must be combined. There are also mandatory rules for how to implement conflict resolution, error handling, proxy selection and parameter prioritization when interpret-ing the received provisioning documents. The provisioning information received by a WAP client is expected to be stored in configuration context, and there is a mechanism that can be used to control how many configuration 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.openmobilealli-ance.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. It is not allowed to overwrite a provisioned doc-ument.

OMA Client Provisioning document reception

In the example below, the user initiates OTA browser, MMS and Streaming configuration from the internet site of the service provider (My Operator). The operator sends one or several SMS with destination port 2948 (non-secure WAP Push), these SMS are re-assemblies parsed and handled by the provisioning user agent. The user is prompted whether to install the received provisioning settings or not. The user accepts and the phone is configured with the new settings. The settings are stored as Internet profiles, Internet accounts and application specific settings. Depending on if the settings were stored in the phone suc-cessfully or not, the user receives an information report message stating for which application the settings were successfully installed or not installed.

8 April 2005

http://www.openmobilealliance.org/http://www.openmobilealliance.org/http://www.openmobilealliance.org/http://www.openmobilealliance.org/http://www.openmobilealliance.org/


If the user refuses the new settings, the settings will be rejected and will not be stored in the mobile phone.

Error handling

If the document parse fails the user is prompted to install the received Provisioning document anyway. If the user accepts, an error message will be shown to the user, Settings not valid

9 April 2005


Security mechanisms

To avoid that non authorized people send malicious content to users, four different alternative security fea-tures are implemented: UserPin, UserPinMac, NetwPin, and UserNetwPin. Refer to 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 should only work for the SIM they are created for.

In cases where the security mechanism requires the user to enter the PIN code, the user is allowed three attempts to enter the code correctly, otherwise the document will be 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 settings. The Internet profile specifies what protocol, HTTP or WAP, proxies and gateways can connect to.

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

Parameter Description

Characteristic : PXLOGICAL

USED Mapped to Sony Ericsson Internet/WAP profile.

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

PROXY-PW NOT USED

PPGAUTH-TYPE NOT USED

PROXY-PROVIDER-ID NOT USED

NAME USED Mandatory, will set the name for the corresponding Internet profile.

DOMAIN NOT USED

TRUST NOT USED

MASTER NOT USED

STARTPAGE USED Will set the URL for the homepage. See also APPID w2.

BASAUTH-ID USED For start page.

10 April 2005

http://www.openmobilealliance.org/


BASAUTH-PW USED For start page.

WSP-VERSION NOT USED

PUSHENABLED NOT USED

PULLENABLED NOT USED

PXLOGICAL : PXAUTHINFO

USED

PXAUTH-TYPE IGNORED Only support HTTP-BASIC and therefore assumed value.

PXAUTH-ID USED User Name 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.

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

PXLOGICAL : PXPHYSI-CAL

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

PXADDRTYPE USED IPV4 and ALPHA interpreted as FQDN supported.

PXADDR-FQDN USED Note that PXADDR is mandatory - set it to a blank string in order 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

PORTNBR USED Default 8080, HTTP: Port number other than 9200-9207 used.WAP: 9202, 9203 used.

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


11 April 2005


NAPDEF

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


Characteristic : NAPDEF Mapped to Sony Ericsson Data account.

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

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

NAME USED Will set the name for the corresponding 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), 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

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

12 April 2005


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 User name.

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


13 April 2005


BOOTSTRAP

The bootstrap process will be performed the first time a SIM is inserted in the mobile phone. A restart of the bootstrap process will also be done after a Master reset. After the phone is bootstrapped, an incoming provisioning document should be handled according to the table below. Note that no overwrite will be 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

14 April 2005


Applications specific settings

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

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

The following applications references are supported.

Application references:

APPID Application

w2 Browsing

w4 MMS

w5 SyncML Data Synchronization

w7 SyncML Device Management

wA IMPS (WV)

25 Email, SMTP

110 Email, POP3

143 Email, IMAP4

554 Streaming Media


Characteristic : APPLICATION

All tags in the characteristic APPLICATION are supported. For the behaviour of each application, please 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

15 April 2005


APPADDR : PORT

PORTNBR Supported

SERVICE Supported

APPLICATION : APPAUTH

AAUTHLEVEL Supported

AAUTHTYPE Supported

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


16 April 2005


Browser - APPID w2

OMA Application Characteristic referenceAPPID: w2.

APPID type: OMNA.

Owner: OMA DM Working Group.

Contact: OMA DM Working Group .

Registration version: 1.

Registration domesticate: 2003-01-24.

Application description: Browser.

Description - w2Settings for the Browser application.

The following is possible to set 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.



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 will be set as START-PAGE for the TO-PROXY.

17 April 2005


MMS - APPID W4


APPID type: OMNA.

Owner: OMA Multimedia Messaging Working Group.

Contact: OMA Multimedia Messaging Working Group .


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 - w4Sets the Service Center and proxy for connection.

Compliance



APPID USED w4

TO-PROXY USED Reference to PXLOGICAL (Internet account).

ADDR USED The Service Center


ADDR USED Secondary way to set Service Center.

18 April 2005

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


ExampleThis example sets the Service Center and proxy.

characteristic type="APPLICATION">

Data Synchronization (SyncML DS) - w5

OMA Application Characteristic reference:APPID: w5.

APPID type: OMNA.

Owner: Data Synchronization Working Group.

Contact: Data Synchronization Working Group .



Application description: Data Synchronization (DS).

Application reference:

SyncML DS 1.1.1 specifications, http://www.syncml.org/technology.html. SyncML Representation Protocol specification,

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

Description - w5Creates a synchronization account.

Compliance



0 or 1

APPID USED w5

NAME USED The name of the account.


ADDR USED The server address.

APPLICATION : APPADDR 0 or 1

ADDR USED The server address.

19 April 2005

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


Example

APPLICATION : APPAUTH 0 or many

AAUTHLEVEL USED APPSRV, Application server

AAUTHTYPE USED BASIC, DIGEST or HTTP-BASIC

AAUTHNAME USED User name.

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 User name on database level.

AAUTHSECRET USED User password on database level.


20 April 2005


Device Management (SyncML DM) - w7


APPID type: OMNA.

Owner: Device Management Working Group.

Contact: Device Management Working Group .



Application description: Device Management (DM).


OMA Device Management (Based on SyncML DM), Version 1.1.2 specifications, http://www.openmobilealliance.org/documents.asp.

SyncML DM Tree and Description specification, http:www.openmobilealliance.org/tech/docs/OMA-SyncML-DMTND-V1_1_2-20030508-C.pdf.

SyncML DM Security specification, http:www.openmobilealliance.org/tech/docs/OMA-SyncML-DMSecurity-V1_1_2-20030508-C.pdf.

SyncML Representation Protocol specification, http:www.openmobilealliance.org/tech/docs/OMA-SyncML-RepPro-V1_1_2-20030505-C.pdf.

Description - w7Creates a Device Management account

21 April 2005

http://www.openmobilealliance.org/documents.asphttp:www.openmobilealliance.org/tech/docs/OMA-SyncML-DMTND-V1_1_2-20030508-C.pdfhttp:www.openmobilealliance.org/tech/docs/OMA-SyncML-DMSecurity-V1_1_2-20030508-C.pdfhttp:www.openmobilealliance.org/tech/docs/OMA-SyncML-RepPro-V1_1_2-20030505-C.pdf


Compliance



0 or 1

APPID USED

PROVIDER-ID USED Will be used as authentication name for server. Max length 80"

INIT NOT SUP-PORTED

NAME USED Used as displayable name in UI. Unique account identifier (i.e. name of the account file) will be DMAcc-0X.acc, where X is in the interval [1,5]. Max length 50


TO-NAPID USED Refers to NAPDEF that is used for connection in the account. If value is INTERNET, the default internet profile will be used.

ADDR USED Device Management server URI. Max length 255

APPLICATION : APPADDR USED

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

ADDRTYPE NOT SUP-PORTED

APPADDR : PORT SUP-PORTED

PORTNBR SUP-PORTED

Value will be stored in DM account, but currently the DM client will not use it. 32 bit number

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

AAUTHLEVEL USED CLIENT means authentication that the server will use to authenticate towards the client. APPSRV means authentication that the client will use to authenticate towards 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 User name. Max length 80

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

AAUTHDATA USED Used to specify nonce. Max length 52

22 April 2005


Example

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 - 25Setting for the Email SMTP (Simple Mail Transfer Protocol) server, that is, outgoing Email.

23 April 2005


Compliance

Example



0 or 1

APPID USED 25

PROVIDER-ID USED Account name, max length 20.

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:APPADDROutgoing server host name, max length 31.


ADDR USED ADDR can either be used in APPLICATION or APPLICA-TION:APPADDROutgoing 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

24 April 2005


Email, POP3 - 110

OMA Application Characteristic referenceAPPID: 110

APPID type: IANA.





Application description: EMail POP3 settings.

Application reference: POP3 is defined in RFC1939.

Description - 110Setting 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).

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



APPADDR : PORT

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



AAUTHNAME USED Incoming server user name. Max length 80 characters.

AAUTHSECRET USED Incoming server password. Max length 40 characters.

25 April 2005


Example

Email, IMAP4 - 143

OMA Application Characteristic referenceAPPID: 143

APPID type: IANA.





Application description: EMail IMAP4 settings.

Application reference: IMAP4 is defined in RFC2060.

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

Compliance



APPID USED 143

PROVIDER-ID USED Account name. Max 20 characters.

TO-NAPID USED

26 April 2005


Example




APPADDR : PORT

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



AAUTHNAME USED Incoming server user name. Max length 80 characters.

AAUTHSECRET USED Incoming server password. Max length 40 characters.


27 April 2005


Streaming (3GPP) - 554

OMA Application Characteristic referenceAPPID: 554.

APPID type: IANA.

Owner: Device Management Working Group.

Contact: Device Management Working Group .



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


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 - 554This is the settings for the streaming application

Compliance

Example



APPID USED 554

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

28 April 2005


IMPS (WV)

OMA Application Characteristic referenceAPPID: wA.

APPID type: OMNA.

Owner: OMA Instant Messaging and presence services Working Group.

Contact: OMA IMPS WG .



Application description: Instant Messaging and presence services (IMPS).

Application reference: None.

Description - wAThe following settings are applicable for Wireless Village (My Friends):

UserID and Domain Password Server URL WAP Profile

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

Compliance



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 will be used. Address of WV server in URI form. Max 200 characters.

APPLICATION : APPADDR 0 or many. The first valid will be used. Lower priority than ADDR.

29 April 2005


Example

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

ADDRTYPE USED Only used to validate that it 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.


30 April 2005


General examples

Settings for Browsing(w2) HTTP protocol, MMS(w4), SyncML Data Synchronization (w5) and SyncML Device Management(w7).

31 April 2005


32 April 2005


33 April 2005


34 April 2005


Settings for Browsing (w2) WSP protocol

35 April 2005


Settings for email Email, POP3 (110) and Email SMTP (25)

36 April 2005


Settings for email Email, POP3 (110) and Email SMTP (25)

37 April 2005


References

OMA-ERELD-ClientProvisioning-v1_1-20021115-C; Open Mobile Alliance, http://www.openmobilealliance.org

OMA-WAP-ProvCont-v1_1-20021112-C, ch.4.6.11; Open Mobile Alliance, http://www.openmobilealliance.org

WAP Push OTA Specification" WAP Forum, WAP-235-PushOTA, http://www.openmobilealliance.org

Provisioning Bootstrap 1.1, Open Mobile Alliance, OMA-WAP-PROVBOOT-V1_1, http://www.openmobilealliance.org

Provisioning Smart Card 1.1, Open Mobile Alliance, OMA-WAP-PROVSC-V1_1, http://www.openmobilealliance.org

Provisioning User Agent Behaviour 1.1", Open Mobile Alliance, OMA-WAP-PROVUABV1_1, http://www.openmobilealliance.org

38 April 2005

http://www.openmobilealliance.orghttp://www.openmobilealliance.orghttp://www.openmobilealliance.orghttp://www.openmobilealliance.orghttp://www.openmobilealliance.orghttp://www.openmobilealliance.org

PrefacePurpose of this documentSony Ericsson Developer WorldDocument conventionsProductsTerminologyTypographical Conventions

Document history

ContentsOverviewArchitectureOMA Client Provisioning in Sony Ericsson phonesOMA Client Provisioning document receptionError handling

Security mechanismsParameters and compliancePXLOGICALNAPDEFBOOTSTRAP

Applications specific settingsBrowser - APPID w2MMS - APPID W4Data Synchronization (SyncML DS) - w5Device Management (SyncML DM) - w7Email, SMTP - 25Email, POP3 - 110Email, IMAP4 - 143Streaming (3GPP) - 554IMPS (WV)

General examplesReferences

Documents

April 2005 Client provisioning - Sony Mobile · ported by Sony Ericsson Client Provisioning on the card, ... proxy selection and parameter prioritization when ... CSD is mapped to