| Network support of DRM separate Delivery vai MMS IN USA |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| praveen_76_1999@yahoo.com New member Username: Praveen_76_1999 Post Number: 7 Registered: 07-2005 |
Hi, Anybody know if any of the networks in USA support DRM separate delivery vai MMS other way to say is super distribution And can i receive Combined delivery and separate delivery content as MMS using Now SMS | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5079 Registered: 10-2002 |
I can answer the NowSMS part of the question. We support the sending out of "separate delivery" rights objects. These rights objects can be sent out with NowSMS via the "Send XML Settings" interface. These are "<o-ex:rights>" documents. But we do not provide any tools to create the protected content, or the rights objects. There is a thread here that discusses how to create these objects using a Nokia toolkit, and send the separate delivery message out via NowSMS: http://support.nowsms.com/discus/messages/485/7538.html -bn | |||
| praveen padmakar New member Username: Praveenpadmakar Post Number: 2 Registered: 06-2004 |
Hi Bryce, Thanks for quick reply. as i know Now SMS support sending on forward lock content via MMS or it has a option to forward lock content. same way can i send combined delivery(.dm )and seprate delivery (.dcf) file to the phone using NowSms Praveen | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5086 Registered: 10-2002 |
Hi Praveen, I've been thinking a little bit more about your question. We're planning to add quite a few new options for sending DRM content in the next major release. In particular, there will be options for specifying that content in an MMS or multimedia WAP Push should be sent using "combined delivery", where you can specify that the object can only be accessed x times, or expires after x days, or expires at a certain date. But in current releases of NowSMS, combined delivery is a little tough. I've done some limited testing, and it looks like if you create a combined delivery object, and give it a ".dm" extension, you can submit it through the web interface of NowSMS, and it will be routed properly. So if you create your own combined delivery object, you should be able to send it in current versions. If you try this, I'd suggest trying it first with WAP Multimedia Push. Then try it via MMS. The issue with MMS is that some operator MMSCs filter content types, and block (probably because they don't know any better) DRM content types. If you want to use separate delivery, that other thread I referenced has a good description of how to do it. But you have to create the objects externally to NowSMS (in the upcoming major release we plan to provide some tools to simplify creation of these objects). 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. Otherwise, the other thread does a good job of explaining how to send out the rights objects for the content, where you do this either via the "Send XML Settings" interface or PAP. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5088 Registered: 10-2002 |
I got a bit sidetracked in my reply above focusing on how to send out these content types. But I forgot to mention the other thought that has been lingering in my mind. As you mention, "superdistribution" requires that you use "separate delivery". But I'm not sure how well this will work when the protected content is sent via an MMS message. I believe that the user would need to save the protected content object from the MMS message on the phone to the handset, before they would be able to receive a rights object to unlock the content. I haven't had time to experiment with this much yet. But most phones seem to ignore rights objects that refer to unknown protected content objects. If the protected content object is within an MMS message, I'm not confident that the most (if any phones) would apply a received rights object against it until the content was extracted from the MMS message. It's definitely an area that requires more real world experimentation. -bn | |||
| praveen padmakar New member Username: Praveenpadmakar Post Number: 3 Registered: 06-2004 |
Hi Bryce, Thanks for explaining this. I have changes MMSCType.ini for DCF files and everythings just works fine i was able to receive separate delivery .dcf files using NowSms and rights too and all the things works fine. I'm using SonyEriccsion tool to genrate the content. i tried combined delivery also and looking at PDU everything looks ok. My phone is not able to handle that at this time. but it is good tool it solved my lot of setup issue. because there is no other tool available to send DRM content to phone via MMS Praveen | |||
| praveen padmakar New member Username: Praveenpadmakar Post Number: 4 Registered: 06-2004 |
one more thing i forgot to mention is when i send separate delivery files from phone using AT&T USA networks it striff off dcf file from mms message. i think they don't support superdistribution . i will have to try using NowSms, any idea if any network in UK or Europ support this? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5132 Registered: 10-2002 |
Praveen, I'm not sure about how different mobile operator MMSCs react to this type of content in their messages. We're preparing a new release of NowSMS which has check box settings on the "Send MMS Message" and "Send WAP Multimedia Message" web forms, which allow you to configure "Combined Delivery" DRM settings. But I haven't had the chance to try this through a variety of mobile networks yet. I've mostly just been trying mobile phones. My "separate delivery" experience is even weaker at this point. So I don't have much practical experience on different networks yet. Hopefully within another 4 to 6 weeks, we'll release a NowSMS update with some additional support for generating this type of content, and then gain some more practical experience. I haven't used the SonyEricsson toolkit (I'll have to try it), but I've been frustrated at times with the Nokia toolkit because when something doesn't work, I've found that it can sometimes be because the toolkit is doing something wrong. It doesn't suprise me that AT&T US is removing the DCF file from the MMS message. I believe they are using an Openwave MMSC, and I don't know if it is by configuration of that MMSC, or limitations of it, that it removes all but the most common content types. -bn | |||
