OMA DRM 2.x Support?

OMA DRM 2.x Support? SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through January 22, 2009 » OMA DRM 2.x Support? « Previous || Next »
Author Message
New member
Username: Tester

Post Number: 2
Registered: 11-2008
Posted on Tuesday, November 11, 2008 - 03:49 pm:   

We use NowSMS 2006 to send OMA DRM 1.x rights object, but want to send OMA DRM 2.x messages as well.

Does NowSMS 2008 support DRM 2.0 RO and ROAP trigger via the Send XML Settings Document page? Or will NowSMS 2009?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 236
Registered: 08-2008
Posted on Tuesday, November 11, 2008 - 04:31 pm:   

Apart from the components that are backward compatible to OMA DRM 1.0, the new components of OMA DRM 2.0/2.1 require a public key infrastructure (PKI) implementation.

Full implementation of OMA DRM 2.x requires a specialised content server with such a PKI implementation.

It is beyond the scope of NowSMS to be able to manage that content and PKI infrastructure.

However, NowSMS can be used for sending any of the OMA DRM 2.x messages that are delivered via WAP Push.

This can be done via either the PAP interface or the "Send XML Settings" web page.

That said, you do need NowSMS 2008 to send the OMA DRM 2.1 ROAP Trigger message.

The following text comes from our NowSMS 2008 release notes:


* OMA Settings: Send XML Settings and Push Access Protocoal (PAP) interface updated to support DRM 2.1 Roap Trigger <roap:roapTrigger> documents. Note: There is a bug in the WBXML encoding as specified in the currently published DRM 2.1 Candidate specification. The specifications defines a WBXML encoding for "", which should instead be "". The OMA has agreed that this bug will be fixed for the final release of the DRM 2.1 specification (Change Request OMA-DRM-2007-0568), and the NowSMS implementation includes support for this fix. Also note that the current DRM 2.1 specification is still a candidate release, and there are numerous encoding errors in the WBMXL example in the specification, so this is definitely a work-in-progress implementation that will be updated as the final specification is released.

Posted on Friday, November 21, 2008 - 11:58 am:   

hello Tester,
could you please contact me in case you are interested in DRM2 solution. my mail is


Login Login / Register Logout Logout Search Last 30 Days Topics Topics