| Send WBXML encoded rights object for Separate Delivery via SMS page... |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | ||||
| Stefan Unregistered guest |
Hello! Is it possible to send an WBXML encoded rights object for DRM Separate Delivery protected contents via the SMS page?? If yes, HOW????? | ||||
| Dancy Xia Unregistered guest |
yes. use wap push tech to send it. below is an sample: first fragment--UDH: 0605040b8423f0 second fragment--WSP header: 000603cbaf88(0xCB--content type: application/vnd.oma.drm.rights+wbxml) third--WBXML rights | ||||
| vide Unregistered guest |
Hi Stefan and dancy, Can you specify more details on the pdu, I have tried several type of format and got no luck. Thanks | ||||
| Anonymous |
i need also help on this! my wsp for an vnd.oma.drm.rights+wbxml looks: 000603CBAF880 i tested also DC0603CBAF880 400603CBAF880 DC0603CB and so on fllowed by the rights object: 030E6A00C5058506860787014647033.... this realy drives my crazy. my testing phone is the nokia 6630 thanks for your help! | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4655 Registered: 10-2002 |
I can't help you with the WSP encoding, but I can explain how to do this from a NowSMS perspective (this is the support forum for NowSMS). Push Access Protocol (PAP) is the way to go, and it is described here: http://support.nowsms.com/discus/messages/485/3292.html If you want to send WBXML instead of XML, then change "Content-Type: application/vnd.oma.drm.rights+xml" to "Content-Type: application/vnd.oma.drm.rights+wbxml". Use 8-bit binary transfer encoding for your WBXML content (not hex string) within the MIME document. And be sure to use a "Content-Length:" header so that we can accurately determine the length of your binary data (and avoid being fooled by an extra CRLF). -bn | ||||
| praveen_76_1999@yahoo.com New member Username: Praveen_76_1999 Post Number: 2 Registered: 07-2005 |
Hi Bryce, Can you just send a screen shot of the screen on nowSMS where you send xml rights. becuse i just have a xml file for rights and i'm copying and pasting this on nowSMS Send XML Settings Document editor and sending it on the phone. Is i'm doing correct thing? Here is the rights file i have for one of my content. WBXML file i realy can't see and not sure how could i send this (for this i have dcr file generated using nokia tool kit) <?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:http://content-id-here </o-dd:uid> </o-ex:context> <ds:KeyInfo><ds:KeyValue>pyV+y/VLqGdVjAPgaOYPIg== </ds:KeyValue></ds:KeyInfo> </o-ex:asset> <o-ex:permission> <o-dd:play> <o-ex:constraint> <o-dd:datetime> <o-dd:start>2005-07-26T19:05:32</o-dd:start> <o-dd:end>2005-08-05T19:05:00</o-dd:end> </o-dd:datetime> </o-ex:constraint> </o-dd:play> <o-dd:display> <o-ex:constraint> <o-dd:count>4</o-dd:count> </o-ex:constraint> </o-dd:display> <o-dd:execute> <o-ex:constraint> <o-dd:count>4</o-dd:count> </o-ex:constraint> </o-dd:execute> <o-dd:print> <o-ex:constraint> </o-ex:constraint> </o-dd:print> </o-ex:permission> </o-ex:agreement> </o-ex:rights> | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4684 Registered: 10-2002 |
To use the WBXML version (.drc), you would have to use the Push Access Protocol. Adapting the example referenced in the link above, it would be: POST /pap HTTP/1.0 Content-Type: multipart/related; boundary=asdlfkjiurwghasf; type="application/xml" Content-Length: xxxxx --asdlfkjiurwghasf Content-Type: application/xml <?xml version="1.0"?> <!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.0//EN" "http://www.wapforum.org/DTD/pap_2.0.dtd" [<?wap-pap-ver supported-versions="2.0,1.*"?>]> <pap> <push-message push-id="9fjeo39jf084@pi.com"> <address address-value="wappush=xxxxxxxxx/type=user@ppg.operator.com"></address> </push-message> </pap> --asdlfkjiurwghasf X-Wap-Application-Id: x-wap-application:drm.ua Content-Type: application/vnd.oma.drm.rights+wbxml Content-Length: yyyy binary data here (followed by CRLF then boundary) --asdlfkjiurwghasf-- There's no interface to submit this binary data from the web. But, if you're using the Nokia toolkit, there's no reason that you have to use the WBXML format. The XML rights file is generated automatically, and saved with a ".dr" extension in the same directory as your ".dcf" file. Take that XML content, and send it using the "Send XML Settings" interface. Your example above should work just fine. I just went into the Nokia toolkit myself ... converted a GIF to DCF. Downloaded the DCF to my phone. Then I took the rights file for the document (".dr" file) ... and sent it to my phone using the "Send XML Settings". My phone (SonyEricsson K750) displayed a message about the object being activated, and I was then able to view it. I had the rights object configured to only allow me to view the object 5 times. And that was all the phone allowed. I then sent another rights object to extend it. Everything worked as expected. Here's the DCF file that I used:
And here is the rights object that I sent to activate it (content of the ".dr" file that the Nokia toolkit generated): <?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:mmm-beer</o-dd:uid> </o-ex:context> <ds:KeyInfo><ds:KeyValue>UVgIzTLXT1qk5WsfiM2nhg==</ds:KeyValue></ds:KeyInfo> </o-ex:asset> <o-ex:permission> <o-dd:display> <o-ex:constraint> <o-dd:count>5</o-dd:count> </o-ex:constraint> </o-dd:display> </o-ex:permission> </o-ex:agreement> </o-ex:rights> I simply pasted that content into the "Send XML Settings" document. But, you could also submit it programmatically via PAP: POST /pap HTTP/1.0 Content-Type: multipart/related; boundary=asdlfkjiurwghasf; type="application/xml" Content-Length: xxxxx --asdlfkjiurwghasf Content-Type: application/xml <?xml version="1.0"?> <!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.0//EN" "http://www.wapforum.org/DTD/pap_2.0.dtd" [<?wap-pap-ver supported-versions="2.0,1.*"?>]> <pap> <push-message push-id="9fjeo39jf084@pi.com"> <address address-value="wappush=xxxxxxxxx/type=user@ppg.operator.com"></address> </push-message> </pap> --asdlfkjiurwghasf X-Wap-Application-Id: x-wap-application:drm.ua Content-Type: application/vnd.oma.drm.rights+xml <?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:mmm-beer</o-dd:uid> </o-ex:context> <ds:KeyInfo><ds:KeyValue>UVgIzTLXT1qk5WsfiM2nhg==</ds:KeyValue></ds:KeyInfo> </o-ex:asset> <o-ex:permission> <o-dd:display> <o-ex:constraint> <o-dd:count>5</o-dd:count> </o-ex:constraint> </o-dd:display> </o-ex:permission> </o-ex:agreement> </o-ex:rights> --asdlfkjiurwghasf-- If you use PAP, you would need to fill out the "Content-Length:" header with the appropriate value. Note that I've left out second "Content-Length:" header which is not strictly required when you it is a text XML document. Also note that if you cut & paste the ".dr" file directly, Nokia leaves space characters after the content-id in the <o-dd:uid> field. NowSMS will interpret them as being part of the actual content-id, and this might cause a problem on some phones. (It works fine on the K750, but might cause a problem on some others.) So it's a good idea to remove any extra white space. -bn | ||||
| praveen_76_1999@yahoo.com New member Username: Praveen_76_1999 Post Number: 4 Registered: 07-2005 |
Hi Bryce, Thanks for quick reply. other problem i'm facing is after receiving 2-3 push messages i don't receive any puch message. i send this so many times but now i'm not able to receive any. Is it the problem with tool or some problem with service provide i'm using Cinguler SIM to send Push messages. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4739 Registered: 10-2002 |
Hi Praveen, It's hard to say. But if possible, swap SIMs around. Or try again the next day. Providers are always looking at potential abuses to the system. And I have heard of some instances where limits are placed on how many messages can be sent from the same source to the same destination during any particular time period. The idea is to prevent abusive behaviour, such as flooding someone's account. Or dealing with a potential problem of software that has gone into a loop. When testing, I'm often sending between the same two numbers. And there have been a couple of times that it just seemed to stop on me, and I haven't been able to explain it. But everything was ok the next day. -bn | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5087 Registered: 10-2002 |
Follow-up note, based on additional discussions in: http://support.nowsms.com/discus/messages/485/11691.html You can send a DCF file out via a WAP Multimedia Push (or MMS), but you need to manually edit MMSCTYPE.INI to add application/vnd.oma.drm.content=.dcf under the [MMS Content Types] header, and .dcf=application/vnd.oma.drm.content under the [Extensions] header. That way, if you post a ".dcf" file via the web interface, we'll know its content type. Or if you use a different web server for the content, you need to make sure it is returning "application/vnd.oma.drm.content" as the content type for the object. | ||||
| Ankur New member Username: Phoneynk Post Number: 5 Registered: 10-2005 |
I used Nokia NMIT to generate dcf and dr file of some gif file. Then I used the NOw SMS interface's Send XML settings to send this to some dummy smsc. This is the message send by the NOw SMS to SMSC 0605040B3F233F2006033F3F3F030E6A3F053F063F3F01464703312E300101494A4648036369643A 6C6F676F66696E616C3101014B4C3F103A1F3F3C3F3F52513F234E3F20483F3F0101014D4F520101 010101 But when I send it to my Sony erricson K700i . It si displaying it as text(binary). Non DRM supporting phones are not receiving the message. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5273 Registered: 10-2002 |
Hi Ankur, Perhaps I am missing something ... but it sounds like this is happening because you're manually sending the hex string as a text message instead of letting NowSMS send it as a binary message. NowSMS can use a K700i as a GSM modem ... let NowSMS send the message via the GSM modem. -bn | ||||
orval.dcf
