5.2 Definition of the Sales/Usage Report structure

When sales and/or usage is to be reported using the MRBV of the UGC Profile of the DSR standard, the following Records shall be communicated in this order:

1. One HEAD Record.

2. One or more summary Records of type SY02.04 or SY04.03+SY09.02+SY05.04.

The SY02.04 is typically used for UGC ad-supported and/or hardware audio-tier services and should not be used for UGC subscription services.

The combination of SY04.03+SY09.02+SY05.04 should be used for UGC subscription services. Exactly which of these summary Records is used is determined by the commercial model the licensee uses, which type of use and the territory any release reported in the Sales/Usage Report has been traded in.

3. One or more Blocks that contain the following Records:

(a) One Record of type AS02.04:

Each of these Records provide data describing the sound recordings, music videos or other “master” resources that have been used in creating the user-generated content that has been accessed, including basic data about the musical work(s) that are embodied in each such resource.

The musical work data shall be included in the form that the licensee uses for its processes based on the data received by the licensee about the same musical work from one or more record company(ies) or distributor(s);

(b) None, one or more Records of type LC01.01:

Each of these Records shall provide data describing the resources and/or musical works that have been set out in the AS Records described in item 3(a) above, in the form provided to the licensee by each of the record company(ies) or distributor(s) that has provided the licensee with data about the same musical work, with the identity of each such data source listed in the MusicalWorkDataProvider Cell of each LC01.01 Record.

However, the exact way in which the LC01.01 Records are populated is determined by bi-lateral agreement between the licensee and the licensor.

(c) None, one or more Records of type RU01.03 or RU02.03:

(i) The RU01.02 Record provides data describing the type and number of sales and/or usages that appear in the Sales/Usage Report for all the UGC releases that contain the resource described in the AS02.03 Record;

(ii) Instead of using an RU01.03 Record, the licensee may use one RU02.03 Record per UGC release, which provides data describing the type and number of sales and/or usages that appear in the Sales/Usage Report for each of those UGC releases that contain the resource described in the AS02.04 Record. Using multiple RU02.03 records is likely to increase the file size significantly;

(iii) It is not permissible to combine RU01.03 and RU02.03 Records in a single Block; and

(iv) The Block may contain multiple RU Records for each AS Record. If the licensee is using an RU01.02 Record then one RU01.03 Record shall be provided for each different value in the ContentCategory Cell. If the licensee is using RU02.03 Records it shall provide one RU02.03 Record for each UGC release.

(d) One or more Records, of type SU03.03:

(i) These Records provide data describing sales and/or usage;

(ii) The SU03.03 Record can be followed by one or more ST01.01 Records providing data describing sales and/or usage specific to each subscriber type;

(iii) The SU03.03 Record can also be followed by one or more Records of type LI01.04. These Records provide licensor-specific data describing the sales and/or usages already provided in the preceding SU03.03; and

(iv) Each of the LI01.04 Records is followed by none or one MW01.03 Record providing data describing licensor-specific musical work data. These Records provide data describing the musical works to which the sales and/or usage data provided in the preceding LI01.03 Record relates.

4. One FOOT Record.

The content of all the Records in a Sales/Usage Report created in accordance with this part of the DSR standard shall, unless specifically indicated otherwise, be the data in the licensee’s possession and as used by the licensee for its own processes.

Multiple SY04.03 Records which have the same value in the SubscriberType Cell and describe different sales contexts (as defined in Clause 6.5 of Part 1 of the DSR standard), may carry the same SummaryRecordId if per-subscriber minima data needs to be communicated for each of those sales contexts.

Each SY04.04 Record shall be followed by one or more groupings containing one SY09.02 Record, followed by one or more SY05.04 Records, as follows:

• 0-n SY04.04

  • 1 SY09.02

    • 1-n SY05.04

The splitting of the summary data between SY04.04, SY09.02 and SY05.02 enables a licensor to separate out per-minima calculations (SY04.04) from market share data (SY09.02) and the basic usage data (SY05.02).

It is recommended that licensees provide the summary Records in a logical order to aid human readability. This would typically mean that different types of summary Records should not be mixed together even if the Record identifiers may not appear in their numerical order. For example a sequence of SY01.03 SY01.03 SY04.03 SY02.04 SY02.04 meets this recommendation, whereas SY04.03 SY01.03 SY04.03 does not.

Figure 1 depicts the layout of the MRBV of this profile for a subscription service (left) and an ad-supported service (right). In the ad-supported service only a subset of the possible record types is shown.

Figure 1 – Layout of the MRBV of UGC Profile

The table below provides an overview of the order and cardinality of the Records to be used in this profile.