| Which devices support fully OMA DRM 1.0? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| Black Chen New member Username: Chenblack Post Number: 1 Registered: 04-2006 |
Hi all, I've tried some devices including windows mobile 5. It seems they could not get rights object from Wap Push. Could you give me a list or reference handset? Does anyone try OMA DRM successfully on windows mobile devices? Another question is: I sent a rights by NOWSMS. Below are rights contents and logs of NOWSMS. empty.dr ========================================================================= <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE o-ex:rights PUBLIC "-//OMA//DTD DRMREL 1.0//EN" "http://www.oma.org/dtd/dr"> <o-ex:rights xmlns:o-ex="http://odrl.net/1.1/ODRL-EX" xmlns:o-dd="http://odrl.net/1.1/ODRL-DD" xmlns:ds="http://www.w3.org/2000/09/xmldsig#/" > <o-ex:context> <o-dd:version>1.0</o-dd:version> </o-ex:context> <o-ex:agreement> <o-ex:asset> <o-ex:context> <o-dd:uid>cid:abcdefghijklmnopqrstuvwxyz</o-dd:uid> </o-ex:context> <ds:KeyInfo><ds:KeyValue>XhA+c5SXVX79BFBQ2M19gA==</ds:KeyValue></ds:KeyInfo> </o-ex:asset> <o-ex:permission> <o-dd:execute> <o-ex:constraint> <o-dd:count>99</o-dd:count> </o-ex:constraint> </o-dd:execute> </o-ex:permission> </o-ex:agreement> </o-ex:rights> nowsms.txt ========================================================================= 2006-04-17 11:13:19,4442F48D.req,10.12.9.10,0919981826,OK --COM4:,Binary=1;DCS=F5;UDH=0605040B8423F0;Data=870603CBAF88030E6A00C505850686078701464703312E30000101494A4648036369643A6162636465666768696A 6B6C6D6E6F707172737475767778797A0001014B4CC3105E103E739497557EFD045050D8CD7D8001 01014D50525303393900010101010101 Anyone can tell me thoes bytes meaning marked by red color? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5842 Registered: 10-2002 |
Hi, I don't know if Windows Mobile 5 supports OMA DRM 1.0 as a standard in all devices. In MSDN, it talks about OMA DRM 1.0 as an example FDRM implementation that can be implemented by device OEMs. I suspect most OEMs would implement it, but you should check the specs from your manufacturer. That said, there is a big problem with Windows Mobile devices in general when it comes to WAP Push and protocols that use WAP Push ... in that, by default, they are locked down to only receive push messages from trusted gateways. Try forward lock and combined delivery first. Verify that those are supported. If combined delivery is supported, then there is a good chance that separate delivery will be supported, but that you are encountering WAP Push related security issues getting the messages delivered. The bytes you have highlighted in red are a WSP connection-less push header. CB is the content type (application/vnd.oma.drm.rights+wbxml), and AF88 is the X-Wap-Application-ID header (x-wap-application:drm.ua). Back to the security issue with WAP Push. I haven't done any experimentation in this area with Windows Mobile 5 devices yet. But I did do some experimentation with earlier releases. And the only way that I found to get the device to accept WAP Push was to update the security settings of the device while it was in the cradle using RAPICONFIG.EXE. I can't find the posting here on the discussion board, so I'll repost details now (copying them from an old saved e-mail). It is possible to change the security settings on the device to allow more WAP Push flexibility. However, the only way that I am aware of doing this is by updating some security settings while the device is in the cradle. The attached ZIP file contains RAPICONFIG.EXE from Smartphone/Windows Mobile 2003 SDK (I'm not sure if there is an updated version for Windows Mobile 5, but it is possible this same one will work). With the device hooked up to a cradle, give the attached a try. Unzip into a directory, then open up a command prompt window into that directory. The first thing that we want to do is to make sure that we know the current security settings for the device, just in case you need to change back to the original settings for any reason. Type RAPICONFIG /p query.xml This command will produce an output file named RapiConfigOut.xml ... copy that to some other file, as we want to save this, as it will tell us what some of the original settings were for the device. Assuming no errors with the above command, next type RAPICONFIG /p unlock.xml At this point, if all is well, you should be able to send OTA out to the device if you use a USERPIN, and regular WAP Push service indications should be supported. There are more security settings that can be programmed through this interface. So you might want to use this as a starting point. If you do discover anything useful, I'd appreciate any feedback.
-bn | ||||
rapiconfig.zip
