Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Deal 1: 
    • CommercialModelType: PayAsYouGoModel
    • UseType: PermanentDownload
  • Deal 2: 
    • CommercialModelType: SubscriptionModel
    • UseType 1: Stream
    • UseType 2: ConditionalDownload

Do’s and Don’ts

 Implementers should use the combinations of UseTypes and/or CommercialModelTypes as set out in below where the exploitations they are seeking to communicate match the examples.

If the examples are not directly applicable, implementers should adapt the examples listed below to their specific circumstances.

...

In the cases where AsPerContract has to be used, implementers are encouraged to contact DDEX with a view to having the allowed-value set(s) extended as soon as possible (where such extension does not inadvertently or otherwise hint at possibly confidential terms of actual sender/receiver agreements). [2]

Generic and Specific UseTypeValues

To aid implementation and allow for backward compatibility, the Allowed Value Set for UseType includes a few generic values, described below. Each generic value can be used in place of a specific group of specific values. If a label sends a generic UseType, it should expect the recipient to interpret it to include all the respective specific values. For example, if sending Stream then the recipient is likely to interpret that to include: ContentInfluencedStream, NonInteractiveStreamOnDemandStream, and TimeInfluencedStream

...

This table explains the hierarchical relationships of three generic parent terms (note: deprecated values are not listed here):

Generic Parent Term

Specific Child Terms

Dub

DubForAdvertisement
DubForLivePerformance
DubForMovies
DubForMusicOnHold
DubForPublicPerformance
DubForRadio
DubForTV

MobileUse

UseAsAlertTone
UseAsDevice
UseAsRingbackTone
UseAsRingbackTune
UseAsRingtone
UseAsRingtune
UseAsScreensaver
UseAsVoiceMail
UseAsWallpaper
UseInMobilePhoneMessaging
UseInPhoneListening

Stream

ContentInfluencedStream
NonInteractiveStream
OnDemandStream
TimeInfluencedStream

Specific Examples

This section contains a number of typical exploitations common in the market today. DDEX expects to update this document in the future if and when new business models become wide-spread.

“A la carte” Downloads

The consumer pays for a specific Release via a one-time purchase at the DSP.

...

Code Block
languagexml
<DealTerms>
  <ValidityPeriod>
    <StartDateTime>2018-12-25T17:00:00</StartDateTime>
  </ValidityPeriod>
  <CommercialModelType>PayAsYouGoModel</CommercialModelType>
  <UseType>PermanentDownload</UseType>
</DealTerms>

Stream Subscriptions

This includes the uses of both on-demand access (the user selects and plays a recording, album etc with full control) and non-interactive access (a radio-style experience with minimal user control). As it is a subscription, the user gains additional features such as no advertisements, higher quality audio, and/or other added functionality. 

In effect this is a DSP offering any or all of the services described in Sections on On-Demand Streaming Subscriptions, Non-interactive Streaming Subscriptionsand Subscription-enabled Offline Consumption [TB1] plus Subscriptions plus any other subscription streaming offerings that are not covered in these three sections (and for which DDEX has, at this stage no specific UseTypeor CommercialModelTypevaluesspecific UseType or CommercialModelType values).

...

Code Block

...

languagexml
<DealTerms>
  <ValidityPeriod>
    <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>SubscriptionModel</CommercialModelType>

...


  <UseType>Stream</UseType>

...


</DealTerms>

On-Demand Streaming Subscriptions

The consumer pays a fee for time-limited access to the service. The fee is not tied to specific Releases and is automatically re-charged at the beginning of a new time period. There are no advertisements and there may be additional features such as higher quality audio.

...

This does not cover the case where Releases or Resources are downloaded to the consumer’s device(s). Where this is permitted, the model in the Section on Subscription-enabled Offline Consumption[TB2] [NR3] should  should be used.

...

Code Block

...

languagexml
<DealTerms>
  <ValidityPeriod>
    <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>SubscriptionModel</CommercialModelType>

...


  <UseType>OnDemandStream</UseType>

...


</

...

DealTerms> 

Non-interactive Streaming Subscriptions

The consumer pays a fee for time-limited access to the service. The fee is not tied to specific Releases and is automatically re-charged at the beginning of a new time period. There are no advertisements and there may be additional features such as higher quality audio.

...

This does not cover the case where Releases or Resources are downloaded to the consumer’s device(s). Where this is permitted, the model in the Section on in the Section on Subscription-enabled Offline Consumptionshould be used.

...

Code Block

...

languagexml
<DealTerms>
  <ValidityPeriod>
    <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>SubscriptionModel</CommercialModelType>

...


  <UseType>NonInteractiveStream</UseType>

...


</

...

DealTerms> 

Subscription-enabled Offline Consumption

The consumer pays a fee for time-limited access to the service. The fee is not tied to specific Releases and is automatically re-charged at the beginning of a new time period.

...

  • Limit access to the paid-for time period;
  • Allow use of the Releases or Resources without an internet connection to the DSP;
  • Prevent unauthorised use of the Releases or Resources.

...

Code Block
<DealTerms>

...


  <ValidityPeriod>
   <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


 <CommercialModelType>SubscriptionModel</CommercialModelType>
  <UseType>ConditionalDownload</UseType>
</DealTerms>

Ad-supported Streaming Service

This includes the uses of both on-demand access (the user selects and plays a Recording, album etc with full control) and non-interactive access (a radio-style experience with minimal user control). As it is advertisement-supported, the user is not paying for the service, instead gaining access by the consumption of advertisements.

In effect this is a DSP offering any or all of Ad-supported On-Demand Streaming Services or Ad-supported non-interactive Streaming Services, plus any other advertisement-supported streaming offerings that are not covered in these three sections (and for which DDEX has, at this stage no specific CommercialModelTypeor UseTypevaluesspecific CommercialModelType or UseType values).

...

Code Block
 <DealTerms>
  <ValidityPeriod>
   <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>AdvertisementSupportedModel</CommercialModelType>

...


  <UseType>Stream</UseType>

...


</DealTerms>

Ad-supported On-Demand Streaming Service

The consumer does not pay a fee to access the service, but instead is obliged to enjoy advertisements.

The DSP allows the consumer to browse and select specific Releases or Resources they wish to use. Users have full control over the releases.

...

Code Block

...

languagexml
 <DealTerms>
  <ValidityPeriod>
   <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>AdvertisementSupportedModel</CommercialModelType>

...


  <UseType>OnDemandStream</UseType>

...


</DealTerms>

Ad-supported non-interactive Streaming Service

The consumer does not pay a fee to access the service, but instead is obliged to enjoy advertisements.

The consumer cannot access specific Releases or Resources on request, but instead indicates interest in other criteria as defined and offered by the DSP. The DSP then delivers releases that it selects according to these criteria, such as pre-programmed lists or algorithmic programming. In effect this is a radio-style experience with minimal user control. 

...

Code Block

...

languagexml
 <DealTerms>
  <ValidityPeriod>
   <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>AdvertisementSupportedModel</CommercialModelType>

...


  <UseType>NonInteractiveStream</UseType>

...


</DealTerms>

RightsClaim Model

In order to communicate rights to a fingerprinting service provider, a Rights Controller needs to allow the service provider to use the Releases or Resources. The Releases or Resources will not be made available by the service provider to consumers.

...

Code Block

...

languagexml
 <DealTerms>
  <ValidityPeriod>
   <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>AdvertisementSupportedModel</CommercialModelType>

...


  <UseType>Stream</UseType>

...


</DealTerms>

User Generated Content (UGC) Model (Matched to Master Recordings)

A user uploads content (s)he has generated to a UGC site. The UGC provider then matches the uploaded content to the master recordings and/or musical works it has been provided with. The UGC provider will then make the uploaded content available to consumers based on the matched recordings’ and/or works’ rights holders’ policies.

...

Code Block

...

languagexml
 <DealTerms>
  <ValidityPeriod>
   <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>RightsClaimModel</CommercialModelType>

...


 <UseType>UserMakeAvailableUserProvided</UseType>

...


</DealTerms>

User Generated Content (UGC) Model (content-embedded)

A user uploads content (s)he has generated to a UGC site by using content that the UGC service provides to its content-creating users, who, in turn, has received the content from a record company. Once the UGC content has been uploaded to the UGC provider it will make it available to consumers based on the matched recordings’ and/or works’ rights holders’ policies.

...

Code Block

...

languagexml
 <DealTerms>
  <ValidityPeriod>
   <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>RightsClaimModel</CommercialModelType>

...


  <UseType>UserMakeAvailableLabelProvided</UseType>

...


</DealTerms>

Subscription Stream and Offline Consumption 

...

(multiple service types)

A subscription streaming service where the consumer can also keep the files on his/her local device – as long as the subscription membership is maintained.

This is a combination of the business models described in Clauses on Stream Subscriptions and Subscription-enabled Offline Consumption.

...

Code Block

...

languagexml
 <DealTerms>
  <ValidityPeriod>
   <StartDateTime>2018-12-25T17:00:00</StartDateTime>

...


  </ValidityPeriod>

...


  <CommercialModelType>SubscriptionModel</CommercialModelType>

...


  <UseType>Stream</UseType>

...


  <UseType>ConditionalDownload</UseType>

...


</DealTerms>

Virtual Gifts

Virtual gifts are described in the same manner as the “gifted business model”. The only difference to the non-gifted variety is that the payee is different from the consumer.

Multi-tier subscriptions

Some DSPs may wish to offer multiple tiers of subscription. These can be handled in multiple ways – if the difference in the tiers is simply a different pricing for different encoding quality the Dealsmight change by referencing different TechnicalResourceDetails. 

However, a cleaner approach is to communicate the service type by using a user-defined UseTypeanddefined UseType and/or user-defined CommercialModelTypedefined CommercialModelType

(Note: DDEX is working on adding support for a separate service type tag in future versions of the ERN Standard.)



[1]                    Actually, it is the developers that need to have this common understanding so that the computers can act in accordance with that common understanding.

[2]                    DDEX’s change request form is available from ddex.net/change_request.

 

 

 [TB1]We defined Stream to not include ConditionalDownload, so this “Subscription-enabled Offline Consumption” use should not be mentioned here. 

 [TB2]Without the section numbers, this would need the section name instead.

 [NR3]I thought I caught them all…

 [TB4]I think this would be ConditionalDownload here. We have deprecated the UseType value of Download.

 [NR5]Updated.

 [TB6]Do you think, to be consistent with the section title above, we should make this “Offline Consumption” rather than “Download”? 

 [NR7]I like that.