How do I deliver protected content to the phone? |
| DRM protected content must be delivered to
the handset via WAP Push (or a SMS with an embedded link/URL). |
| |
|
Can DRM protected content be delivered to the phone
via Bluetooth, IR or cable? |
Yes.
|
| |
|
How do I know if the phone I am sending to supports DRM? |
| You can check the HTTP headers of the hit
from the device to your web server, or you can subscribe to the
DRM Compatiblity Lookup service. |
| |
|
How
many phones currently support DRM? |
| There are hundreds of models on the market
today that support DRM. |
| |
|
What happens if I try to deliver a DRM protected file to a phone
that doesn't support DRM? |
| The phone will report that the content was
unviewable, unknown, content type not recognized or some similar
error. |
| |
|
Can I use your SDK to deliver DRM content to Verizon to fulfill
their requirement via my aggregator? |
| Your aggregator will most likely already be
applying the DRM. Since US aggregators offer an interface in
between you and Verizon's MMSC, they will automatically apply
the DRM for you. |
| |
|
What other U.S. carrier requirements are there for DRM? |
| For Sprint/Nextel, DRM content is not
permitted through the WAP gateway. For AT&T (formerly
Cingular), DRM is allowed/possible but not mandatory.
For T-Mobile, DRM *must* be applied on audio files/ring tones
otherwise the content cannot be downloaded and applied.
For other carriers, please check with your local
representative.
In the U.S., the MercuryXMS Mobile DRM SDK will support AT&T
and T-Mobile. When other carriers allow DRM to be applied, our
SDK will support those as well. |
| |
|
What type of content can I apply DRM to? |
| Any rich media content - images, video,
audio, etc. can have DRM applied to it. Text cannot have DRM
applied to it. |
| |
| |
