| Client Provisioning v1.1 - supported in NowSMS 2006? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| Bill Turner New member Username: Dizzyfish Post Number: 3 Registered: 03-2006 |
Hi Bryce, Quick version: Is 'CP' the OMA Client Provisioning v1.1 specification and if so, is it the same as OMA Provisioning Content v1.1 (NowSMS words)? If not, does NowSMS support the OMA Client Provisioning v1.1 specification. Longer version: We've had a query about 'CP' from our Telco which comes as a result of a conversation they had with one of our competitors. They said that 'CP' (which I've rashly _guessed_ is the OMA Client Provisioning v1.1 standard) was a 'backstop' which could be used with old devices that didn't support 'OMA'. Even if the device supported OMA, you still needed 'CP' at a 'lower level' to change some settings. This came via some 'normal' (read 'non-technical') people so it is quite possibly b'lox. The question is: Is 'CP' the OMA Client Provisioning v1.1 specification and if so, is it the same as OMA Provisioning Content v1.1? The following is just yadda if the answer is 'yes'. I've scanned the web and it looks like this is what they are talking about (from the 'Enabler Package' on the OMA site [http://www.openmobilealliance.org/release_program/cp_v1_1.htm]): "Client Provisioning version 1.1 is a backwards compatible extension of the client provisioning functionality included in WAP 2.0. This version has added support for direct access (and WAP Proxy support) and application access provisioning." As soon as it mentioned 'WAP 2.0' I thought it couldn't be *that* backwards i.e. the old devices or 'backstop' our friends were talking about. It talks about using a bootstrap process to send out an XML document via a Trusted Provisioning Server. Sounds familiar... Provisioning documents are "binary encoded XML documents [WBXML] with a special MIME type that is interpreted at the application level on the (device)". Sounds even more familiar! Here is an example taken from the attached PDF: <?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="INTERNET"/> <parm name="BEARER" value="GSM-GPRS"/> <parm name="NAME" value="MY ISP GPRS"/> <parm name="NAP-ADDRESS" value="MYISP.gprs"/> <parm name="NAP-ADDRTYPE" value="APN"/> </characteristic> <characteristic type="BOOTSTRAP"> <parm name="CONTEXT-ALLOW" value="0"/> <parm name="PROVURL" value="http://www.operator.com/TPS/"/> </characteristic> </wap-provisioningdoc> To me, that looks VERY similar to the Moto example in their Provisioning White Paper. So, the question: Is 'CP' the OMA Client Provisioning v1.1 specification and is it the same as the OMA Provisioning Content v1.1 (and if so, what are *they* talking about!!!)? Thanks, Bill
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5613 Registered: 10-2002 |
Hi Bill, I would expect that "CP" in this context refers to OMA Client Provisioning, although it could also refer to Client Provisioning in a more general context. The OMA Provisioning Content spec is a subset of the set of specifications that make up OMA Client Provisioning. At least it's the main bit. The WAP 2.0 specification did include a "Provisioning Content" specification, which is considered to be the "1.0" version of the later OMA spec. "1.1" expands upon "1.0" ... mainly introducing additional parameters settings and new binary codes for those settings. NowSMS supports 1.1. If you only use settings defined in 1.0, then it should be ok with a device that only supports 1.0. To the best of my knowledge, I don't recall any devices supporting 1.0. The 1.0 Provisioning Content spec was released on 24-July-2001. Drafts of 1.1 started to be released in 2002, and it was pretty much a quasi-standard until it was formally approved in 2005. 1.1 is backward compatible with 1.0, as long as you stay away from 1.1 specific features. In particular, stay away from the following type values: APPLICATION, APPADDR, APPAUTH, RESOURCE I'll attach a copy of the 1.0 spec here.
Before devices supported OMA Provisioning Content, Nokia and (Sony)Ericsson had a provisioning standard (which we refer to as "WAP OTA" in NowSMS). And a couple of other vendors did support it in a few models (but I don't remember the details right any more). There was also an Openwave proprietary method which we never managed to get any documentation on. -bn | ||||
| Bill Turner New member Username: Dizzyfish Post Number: 4 Registered: 03-2006 |
Thanks, Bryce. Again, a vastly complete and very helpful response.  Cheers, Bill | ||||
