NewLC - Sending Multiple DRM Keys with one WAP Push - Comments

Re: Sending Multiple DRM Keys with one WAP Push

paulrenn — Wed, 23 Jan 2008 10:01:05 +0100

This topic is pretty old but IIRC, SL is not so commonly supported (i.e. permitted by the operators) in terminal side.
So maybe better to send SI and allow the terminal/user to decide whether to load the objects.

Re: Sending Multiple DRM Keys with one WAP Push

tote — Thu, 26 Apr 2007 00:32:02 +0200

Hi,

Please, bear with me - it's been years ago when I was last involved in wap push related development. However, what I remember of is that a push message could contain a multipart (related, alternative, mixed) message (see KUidWapPushMsgMultiPart, for example) that could eventually contain anything. Based on that I presumed that a WAP Push message could contain more than one DRM RO, right? Does that make any sense? I don't think that being SI or SL makes any difference here.

Tote

Re: Sending Multiple DRM Keys with one WAP Push

cypher181 — Wed, 25 Apr 2007 23:37:01 +0200

Hi tote,

Thank you for responding.

From what I understand, a WAP Push can either be a Service Indicator (SI), or a Service Load (SL). In the case of SI, user intervention is required. In the case of SL, the phone automatically consumes the message. The Rights Object I am sending down is part of the OMA DRM 1.0 specification. The RO is defined in an XML Settings document that is pushed to the phone in SL mode (OMA *.dr). I was wondering if anyone had any success in sending down multiple keys at once in one XML Settings document.

Re: Sending Multiple DRM Keys with one WAP Push

tote — Wed, 25 Apr 2007 10:00:29 +0200

Hi,

Afaik a WAP Push message contains a link to be resolved by the mobile device. I'm not sure, though, if it can contain more than one URLs. Did you try that out? And what about pointing to a multipart message? That message could contain different ROs combined in a single file.

Just an idea.

Tote

Sending Multiple DRM Keys with one WAP Push

cypher181 — Fri, 20 Apr 2007 21:18:52 +0200