Client provisioning. April 2005

Size: px

Start display at page:

Download "Client provisioning. April 2005"

Emily Summers
5 years ago
Views:

1 Client provisioning April 2005

2 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_ C, which can be found at These Developers Guidelines are published by: Sony Ericsson Mobile Communications AB, SE Lund, Sweden Phone: Fax: Sony Ericsson Mobile Communications AB, 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 R1A 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. 2 April 2005

3 Sony Ericsson Developer World On developers will find documentation and tools such as phone White Papers, Developers Guidelines for different technologies, SDKs and relevant APIs. The website also contains discussion forums monitored by the Sony Ericsson Developer Support team, an extensive Knowledge 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 V800 Z800 K750 W800 K600 Sony Ericsson mobile phones V800i, Vodafone 802SE Z800i K750i, K750c, D750i W800i, W800c K600i 3 April 2005

4 Terminology GSM IMPS MMS MS OMA OTA SMS WAP WBXML WIM WV Global System for Mobile communications Instant Messaging and Presence Services Multimedia Messaging Service Mobile System Open Mobile Alliance Over The Air Short Message Service Wireless Application Protocol WAP Binary XML WAP Identity Module Wireless Village (IMPS) Typographical Conventions Code is written in Courier font: <html>..</html> Document history Change history Version R1A First version published 4 April 2005

5 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 w MMS - APPID W Data Synchronization (SyncML DS) - w Device Management (SyncML DM) - w , SMTP , POP , IMAP Streaming (3GPP) IMPS (WV)...29 General examples...31 References April 2005

6 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, , 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

7 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

8 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 protocol, refer to Provisioning Bootstrap 1.1, Open Mobile Alliance, OMA-WAP-PROVBOOT-V1_1, 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, 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 interface design for SIM/WIM provisioning is described in Provisioning Smart Card 1.1, Open Mobile Alliance, OMA-WAP-PROVSC-V1_1, There are 3 different storing areas supported 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 documents 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 interpreting 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, 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 document. 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 successfully or not, the user receives an information report message stating for which application the settings were successfully installed or not installed. 8 April 2005

Error handling If the document parse fails the user is prompted to install the

9 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

10 Security mechanisms To avoid that non authorized people send malicious content to users, four different alternative security features are implemented: UserPin, UserPinMac, NetwPin, and UserNetwPin. Refer to Provisioning Bootstrap 1.1, Open Mobile Alliance, OMA-WAP-PROVBOOT-V1_1, 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 Internet (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_ C, chapter 4.2 Overview of Data Model. Parameter Characteristic : PXLOGICAL USED Description Mapped to Sony Ericsson Internet/WAP profile. PROXY-ID USED Internal reference within the document used to refer to a certain PXLOGICAL. PROXY-PW PPGAUTH-TYPE PROXY-PROVIDER-ID NAME USED Mandatory, will set the name for the corresponding Internet profile. DOMAIN TRUST MASTER STARTPAGE USED Will set the URL for the homepage. See also APPID w2. BASAUTH-ID USED For start page. 10 April 2005

11 Parameter Description BASAUTH-PW USED For start page. WSP-VERSION PUSHENABLED PULLENABLED 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 HTTP: Port number other than 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 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 PUSHENABLED PULLENABLED TO-NAPID PXPHYSICAL : PORT Mandatory. Links Internet/WAP profile to Data account within the same document. PORT can either be used in PXLOGICAL or PXPHYSICAL PORTNBR USED Default 8080, HTTP: Port number other than used. WAP: 9202, 9203 used. SERVICE USED Parameter used CO-WSP or CO-SEC-WSP 11 April 2005

12 NAPDEF NAPDEF is mapped to the Sony Ericsson Data Account, allowing the mobile phone to connect to the Internet (Web and WAP), , and so on. The Data Account specifies what bearer the phone will use for connection (GPRS or dial-up GSM).. Parameter Characteristic : NAPDEF Description 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 NAP-ADDRESS USED APN for GSM-GPRS CSD 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 DNLINKSPEED USED CSD Data rate LINGER USED Only if bearer is GSM-CSD DELIVERY-ERR-SDU DELIVERY-ORDER TRAFFIC-CLASS MAX-SDU-SIZE MAX-BITRATE-UPLINK MAX-BITRATE-DNLINK RESIDUAL-BER SDU-ERROR-RATIO TRAFFIC-HANDL-PRIO TRANSFER-DELAY 12 April 2005

13 Parameter Description GUARANTEED-BITRATE- UPLINK GUARANTEED-BITRATE- DNLINK MAX-NUM-RETRY FIRST-RETRY-TIMEOUT REREG-THRESHOLD T-BIT NAPDEF : NAPAUTHINFO AUTHTYPE USED values are PAP or CHAP. AUTHNAME USED Data Account User name. AUTHSECRET USED Data Account Password AUTH-ENTITY SPI NAPDEF : VALIDITY COUNTRY NETWORK SID SOC VALIDUNTIL 13 April 2005

14 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. Parameter Description Characteristic : BOOTSTRAP USED NAME USED Used as title when presenting the document to the user. NETWORK COUNTRY PROXY-ID 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 NAME * 14 April 2005

15 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. APPID w2 w4 w5 w7 wa Application Browsing MMS SyncML Data Synchronization SyncML Device Management IMPS (WV) 25 , SMTP 110 , POP , IMAP4 554 Streaming Media Application references: Parameter Characteristic : APPLICATION Description All tags in the characteristic APPLICATION are supported. For the behaviour of each application, please see the specification for each APPID. APPID PROVIDER-ID NAME AACCEPT APROTOCOL TO-PROXY TO-NAPID ADDR APPLICATION : APPADDR ADDR ADDRTYPE 15 April 2005

16 Parameter Description APPADDR : PORT PORTNBR SERVICE APPLICATION : APPAUTH AAUTHLEVEL AAUTHTYPE AAUTHNAME AAUTHSECRET AAUTHDATA APPLICATION : RESOURCE URI NAME AACCEPT AAUTHTYPE AAUTHNAME AAUTHSECRET AAUTHDATA STARTPAGE Characteristic : ACCESS RULE APPID PORTNBR DOMAIN TO-NAPID TO-PROXY 16 April 2005

17 Browser - APPID w2 OMA Application Characteristic reference APPID: w2. APPID type: OMNA. Owner: OMA DM Working Group. Contact: OMA DM Working Group <OMA-DM@MAIL.OPENMOBILEALLIANCE.ORG>. Registration version: 1. Registration domesticate: Application description: Browser. Description - w2 Settings for the Browser application. The following is possible to set via the Browser. Start Page with Title for a PXLOGICAL. Bookmarks. Compliance Parameter Description Characteristic : APPLICATION APPID USED w2 TO-PROXY USED Refers to the PXLOGICAL that STARTPAGE can be set for. APPLICATION : RESOURCE 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. Example This example installs two bookmarks and sets the start page for the PXLOGICAL with PROXY-ID equal to <parm name="appid" value="w2"/> <parm name="to-proxy" value=" /> <characteristic type="resource"> <parm name="uri" value=" 17 April 2005

18 <parm name="name" value="some Operator WAP Service"/> <parm name="startpage"/> <characteristic type="resource"> <parm name="uri" value=" "/> <parm name="name" value="bookmark 1"/> <characteristic type="resource"> <parm name="uri" value=" "/> <parm name="name" value="bookmark 2"/> MMS - APPID W4 OMA Application Characteristic reference APPID: w4. APPID type: OMNA. Owner: OMA Multimedia Messaging Working Group. Contact: OMA Multimedia Messaging Working Group <OMA-MMS@MAIL.OPENMOBILEALLIANCE.ORG>. Registration version: 1. Registration timestamp: Application description: Multimedia Messaging Service (MMS). Application reference: Multimedia Messaging Service (MMS) specifications, Description - w4 Sets the Service Center and proxy for connection. Compliance Parameter Description Characteristic : APPLICATION APPID USED w4 TO-PROXY USED Reference to PXLOGICAL ( Internet account ). ADDR USED The Service Center APPLICATION : APPADDR ADDR USED Secondary way to set Service Center. 18 April 2005

19 Example This 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=" Data Synchronization (SyncML DS) - w5 OMA Application Characteristic reference: APPID: w5. APPID type: OMNA. Owner: Data Synchronization Working Group. Contact: Data Synchronization Working Group <OMA-DS@MAIL.OPENMOBILEALLIANCE.ORG>. Registration version: 1. Registration timestamp: Application description: Data Synchronization (DS). Application reference: SyncML DS specifications, SyncML Representation Protocol specification, Description - w5 Creates a synchronization account. Compliance Parameter Characteristic : APPLICATION Description 0 or 1 APPID USED w5 NAME USED The name of the account. TO-PROXY USED Reference to PXLOGICAL ( Internet account ). ADDR USED The server address. APPLICATION : APPADDR 0 or 1 ADDR USED The server address. 19 April 2005

20 Parameter APPLICATION : APPAUTH Description 0 or many AAUTHLEVEL USED APPSRV, Application server AAUTHTYPE USED BASIC, DIGEST or HTTP-BASIC AAUTHNAME USED User name. AAUTHSECRET USED User password. AAUTHDATA APPLICATION : RESOURCE 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. Example <parm name="appid" value="w5"/> <parm name="name" value="scts"/> <parm name="to-proxy" value="px "/> <characteristic type="appaddr"> <parm name="addr" value=" <parm name="aauthlevel" value="appsrv"/> <parm name="aauthtype" value="digest"/> <parm name="aauthname" value="sync"/> <parm name="aauthsecret" value="cnys"/> <parm name="aauthlevel" value="appsrv"/> <parm name="aauthtype" value="http-basic"/> <parm name="aauthname" value="client"/> <parm name="aauthsecret" value="teilc"/> <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 type="resource"> <parm name="uri" value="cal"/> <parm name="aaccept" value="text/x-vcalendar,text/vcalendar"/> <parm name="aauthname" value="cal"/> <parm name="aauthsecret" value="lac"/> 20 April 2005

21 <characteristic type="resource"> <parm name="uri" value="notes"/> <parm name="aaccept" value="text/plain,text/x-vnote;1.1"/> <parm name="aauthname" value="notes"/> <parm name="aauthsecret" value="seton"/> <characteristic type="resource"> <parm name="uri" value="todo?todo"/> <parm name="aaccept" value="text/x-vcalendar,text/vcalendar"/> <parm name="aauthname" value="todo"/> <parm name="aauthsecret" value="odot"/> Device Management (SyncML DM) - w7 OMA Application Characteristic reference APPID: w7. APPID type: OMNA. Owner: Device Management Working Group. Contact: Device Management Working Group <OMA-DM@MAIL.OPENMOBILEALLIANCE.ORG>. Registration version: 1. Registration timestamp: Application description: Device Management (DM). Application reference: OMA Device Management (Based on SyncML DM), Version specifications, SyncML DM Tree and Description specification, SyncML DM Security specification, SyncML Representation Protocol specification, Description - w7 Creates a Device Management account 21 April 2005

22 Compliance Parameter Characteristic : APPLICATION Description 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-PROXY USED Reference to PXLOGICAL ( Internet account ). 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 APPADDR : PORT PORTNBR NOT SUP- PORTED SUP- PORTED 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 characteristic. 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 multiple 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 April 2005

23 Example <parm name="appid" value="w7"/> <parm name="provider-id" value="servername"/> <parm name="name" value="mgmt Server"/> <parm name="addr" value=" <parm name="to-proxy" value="op GPRS" /> <parm name="aauthtype" value="http-digest"/> <parm name="aauthname" value="name"/> <parm name="aauthsecret" value="secret"/> <parm name="aauthlevel" value="appsrv"/> <parm name="aauthtype" value="digest,basic"/> <parm name="aauthsecret" value="serversecret"/> <parm name="aauthdata" value="servernonce"/> <parm name="aauthlevel" value="client"/> <parm name="aauthname" value="clientname"/> <parm name="aauthsecret" value="clientsecret"/> <parm name="aauthdata" value="clientnonce"/> , SMTP - 25 OMA Application Characteristic reference APPID: 25. APPID type: IANA. Owner: OMA DM Working Group. Contact: OMA DM Working Group <OMA-DM@MAIL.OPENMOBILEALLIANCE.ORG>. Registration version: 1. Registration timestamp: Application description: SMTP settings. Application reference: See RFC 2821 for SMTP definition. Description - 25 Setting for the SMTP (Simple Mail Transfer Protocol) server, that is, outgoing April 2005

24 Compliance Parameter Characteristic : APPLICATION Description 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:APPADDR Outgoing server host name, max length 31. APPLICATION : APPADDR 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. APPLICATION : APPAUTH AAUTHNAME USED Username for outgoing server AAUTHSECRET USED Password for incoming and outgoing server Example <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> 24 April 2005

25 , POP3-110 OMA Application Characteristic reference APPID: 110 APPID type: IANA. Owner: OMA DM Working Group. Contact: OMA DM Working Group Registration version: 1. Registration timestamp: Application description: POP3 settings. Application reference: POP3 is defined in RFC1939. Description Setting for the incoming server using POP3 protocol. Compliance Parameter Description Characteristic : APPLICATION 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:APPADDR Incoming server host name. Max length 31 characters. APPLICATION : APPADDR 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. SERVICE USED Empty or STARTTLS. APPLICATION : APPAUTH AAUTHNAME USED Incoming server user name. Max length 80 characters. AAUTHSECRET USED Incoming server password. Max length 40 characters. 25 April 2005

26 Example <parm name="appid" value="110"/> <parm name="to-proxy " value=" /> <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> , IMAP4-143 OMA Application Characteristic reference APPID: 143 APPID type: IANA. Owner: OMA DM Working Group. Contact: OMA DM Working Group Registration version: 1. Registration timestamp: Application description: IMAP4 settings. Application reference: IMAP4 is defined in RFC2060. Description This is the setting for the incoming server using IMAP4 protocol. Compliance Parameter Description Characteristic : APPLICATION APPID USED 143 PROVIDER-ID USED Account name. Max 20 characters. TO-NAPID USED 26 April 2005

27 Parameter Description ADDR USED ADDR can either be used in APPLICATION or APPLICA- TION:APPADDR Incoming server host name. Max length 31 characters. APPLICATION : APPADDR 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. SERVICE USED Empty or STARTTLS. APPLICATION : APPAUTH AAUTHNAME USED Incoming server user name. Max length 80 characters. AAUTHSECRET USED Incoming server password. Max length 40 characters. Example <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> 27 April 2005

28 Streaming (3GPP) OMA Application Characteristic reference APPID: 554. APPID type: IANA. Owner: Device Management Working Group. Contact: Device Management Working Group <OMA-DM@MAIL.OPENMOBILEALLIANCE.ORG>. Registration version: 1. Registration timestamp: Application description: 3GPP PSS Streaming using Real Time Streaming Protocol (RTSP). Application reference: 3GPP TS / IETF (Internet Engineering Task Force) standards on streaming RTP (Real-time Transport Protocol)/RTCP (Real-time Transport Control Protocol) RFC1889/ RTSP (Real Time Streaming Protocol) RFC2326/ SDP (Session Description Protocol) RFC2327/ Description This is the settings for the streaming application Compliance Parameter Description Characteristic : APPLICATION APPID USED 554 TO-NAPID USED Internet account ID APPLICATION : APPADDR ADDR USED The Proxy address. (Domain name or IP-address) APPADDR : PORT PORTNBR USED Connection port number to proxy server Example <parm name="appid" value="554"/> <parm name="to-napid" value="nap1"/> <characteristic type="appaddr"> <parm name="addr" value=" "/> <characteristic type="port"> <parm name="portnbr" value="8080"/> 28 April 2005

29 IMPS (WV) OMA Application Characteristic reference APPID: wa. APPID type: OMNA. Owner: OMA Instant Messaging and presence services Working Group. Contact: OMA IMPS WG Registration version: 1. Registration timestamp: Application description: Instant Messaging and presence services (IMPS). Application reference: None. Description - wa The 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 Parameter Description Characteristic : APPLICATION APPID USED wa AACCEPT USED Used to verify correct WV protocol version and XML coding (XML or WBXML). TO-PROXY USED Reference to PXLOGICAL ( Internet account ). 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

30 Parameter Description 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) APPLICATION : APPAUTH AAUTHLEVEL USED Only the value APPSRV is supported. AAUTHNAME USED Complete WV UserID (including domain). Max 50 characters. AAUTHSECRET USED Max 50 characters. Example <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=" <parm name="addr" value=" <parm name="aauthlevel" value="appsrv"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> 30 April 2005

31 General examples Settings for Browsing(w2) HTTP protocol, MMS(w4), SyncML Data Synchronization (w5) and SyncML Device Management(w7). <?xml version="1.0"?> <!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" " <wap-provisioningdoc version="1.1"> <characteristic type="bootstrap"> <parm name="provurl" value=" <parm name="name" value="operator Settings"/> <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 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 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"/> 31 April 2005

32 <parm name="appid" value="w2"/> <parm name="to-proxy " value="webproxy.operator.com" /> <characteristic type="resource"> <parm name="uri" value=" <parm name="name" value="some Operator WAP Service"/> <parm name="startpage"/> <characteristic type="resource"> <parm name="uri" value=" "/> <parm name="name" value="bookmark 1"/> <parm name="startpage"/> <characteristic type="resource"> <parm name="uri" value=" "/> <parm name="name" value="bookmark 2"/> <parm name="startpage"/> <parm name="appid" value="w4"/> <parm name="to-proxy" value="webproxy.operator.com"/> <parm name="addr" value=" <parm name="appid" value="w5"/> <parm name="name" value="scts"/> <parm name="to-proxy" value="webproxy.operator.com"/> <characteristic type="appaddr"> <parm name="addr" value=" <parm name="aauthname" value="sync"/> <parm name="aauthsecret" value="cnys"/> <parm name="aauthname" value="client"/> <parm name="aauthsecret" value="teilc"/> <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 type="resource"> <parm name="uri" value="cal"/> <parm name="aaccept" value="text/x-vcalendar,text/vcalendar"/> <parm name="aauthname" value="cal"/> 32 April 2005

33 <parm name="aauthsecret" value="lac"/> <characteristic type="resource"> <parm name="uri" value="notes"/> <parm name="aaccept" value="text/plain,text/x-vnote;1.1"/> <parm name="aauthname" value="notes"/> <parm name="aauthsecret" value="seton"/> <characteristic type="resource"> <parm name="uri" value="todo?todo"/> <parm name="aaccept" value="text/x-vcalendar,text/vcalendar"/> <parm name="aauthname" value="todo"/> <parm name="aauthsecret" value="odot"/> <parm name="appid" value="w7"/> <parm name="provider-id" value="servername"/> <parm name="name" value="mgmt Server"/> <parm name="addr" value=" <parm name="to-proxy" value="webproxy.operator.com" /> <parm name="aauthname" value="name"/> <parm name="aauthsecret" value="secret"/> <parm name="aauthsecret" value="serversecret"/> <parm name="aauthdata" value="servernonce"/> <parm name="aauthsecret" value="clientsecret"/> <parm name="aauthdata" value="clientnonce"/> <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> <parm name="appid" value="110"/> 33 April 2005

34 <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> <parm name="appid" value="554"/> <parm name="to-napid" value="operator.com"/> <characteristic type="appaddr"> <parm name="addr" value=" "/> <characteristic type="port"> <parm name="portnbr" value="8080"/> <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=" <parm name="addr" value=" <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> </wap-provisioningdoc> 34 April 2005

35 Settings for Browsing (w2) WSP protocol <?xml version="1.0"?> <!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" " <wap-provisioningdoc version="1.1"> <characteristic type="bootstrap"> <parm name="provurl" value=" <parm name="name" value="operator Settings"/> <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=" "/> <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 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"/> <parm name="appid" value="w2"/> <parm name="to-proxy " value="webproxy.operator.com" /> <characteristic type="resource"> <parm name="uri" value=" <parm name="name" value="some Operator WAP Service"/> <parm name="startpage"/> </wap-provisioningdoc> 35 April 2005

36 Settings for , POP3 (110) and SMTP (25) <?xml version="1.0"?> <!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" " <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"/> <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> </wap-provisioningdoc> 36 April 2005

37 Settings for , POP3 (110) and SMTP (25) <?xml version="1.0"?> <!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN" " <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"/> <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> <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"/> <parm name="aauthname" value="username"/> <parm name="aauthsecret" value="password"/> </wap-provisioningdoc> 37 April 2005

38 References OMA-ERELD-ClientProvisioning-v1_ C; Open Mobile Alliance, OMA-WAP-ProvCont-v1_ C, ch ; Open Mobile Alliance, WAP Push OTA Specification" WAP Forum, WAP-235-PushOTA, Provisioning Bootstrap 1.1, Open Mobile Alliance, OMA-WAP-PROVBOOT-V1_1, Provisioning Smart Card 1.1, Open Mobile Alliance, OMA-WAP-PROVSC-V1_1, Provisioning User Agent Behaviour 1.1", Open Mobile Alliance, OMA-WAP-PROVUABV1_1, 38 April 2005

Developers guidelines

Developers guidelines June 2010 OMA Client Provisioning and Device Management for Sony Ericsson phones with DM client v.5 v.6 Preface Purpose of this document This document describes the implementation