Skip to end of metadata
Go to start of metadata

What is the aim of UGC Profile?

The aim of the UGC Profile is to enable licensees to report to rights controllers information regarding the level of usage and/or revenue generated from the usage of music where content may have been uploaded to a licensee's platform by any user which is not necessarily the owner or right controller of the content.

The UGC Profile can provide a very detailed level of information for the key stakeholders at:

  • Release level (typically: the Videos);
  • Resource level (typically: the Sound Recording embodying the Musical Work used in the Release); and
  • Licensor-level (known ownership during the reporting period).

What business models does it encompass?

This format encompass two major commercial offers.

  • Ad supported streaming; and
  • Subscriptions 

The summaries provided with this profile cater for both needs.

How is a report structured?

The profile is provided in two variants. The default variant is the Multi-Record Block Variant (MRBV) where usage and/or revenues are reported using the following way:

  • A header that contains general information such as information about the sender and receiver. The header is common to all flat-file DSR formats.
  • A summary for each sales/usage context and Licensor.
    This new and powerful concept enables a licensee to report as many contexts he needs in a single report. For instance, a licensee that would like to report five commercial offers in Europe (31 territories) would need to report 5*31 contexts – leading to 155 summary records. In the main body of the sales/usage report in the report, each sales record will only need to point to a summary line instead of repeating the context information.
    The type of the summary record (SU01) or (SU02) to be used depends on the use type.
  • Blocks of detailed sales/usage information.
    These blocks are the body of the report. Each block contains all information to process it:
    • A Sound recording element;

    • The Musical Work that is embedded within the Sound Recording;

    • The list of Videos (or Releases) that embed the Sound Recording;

    • The number of Usages (Streams or views) and the Revenue generated by the Sound Recording; and

    • The Ownership of the Musical Work embedded within the Sound Recording.

  • A footer that contains information about the sales/usage report such as the number of records that are included. The header is common to all flat-file DSR formats.


DDEX has also defined a Single-Record Block Variant (SRBV) where usage and/or revenues are reported using the following way:

  • A SRBV-specific header;
  • A set of summary records;
  • A set of records where each record contains Work, Resource, Release and usage information; and
  • A SRBV-specific footer.

Additional Detail and Accuracy

In addition, the UGC Profile structure allows for new level of details and accuracy:

  • Sub-Period ownership. Older DDEX Standard only allowed for a single ownership representation per Reporting Period. Partial days ownership were therefore ignored. The UGC profile allows for sub-period ownership, Revenue and Usage representation making the overall Reporting much more accurate.
  • Multiple Rights type. With global coverage, some Music services need to adapt to very diverse Copyright legislation and practices, including the separate licensing of Performing and Mechanical Rights. With UGC profile, it is possible to represent ownership at the Right Type level and assign revenue accordingly.
  • Blocks of information: these blocks are the body of the report. Each block contains all information pertaining to a single resource (a Sound Recording for example): UGC blocks contains the relevant information for each Resource.

Scalability of UGC sales/usage reports 

The UGC profile enables licensees to report to musical work licensors usage, revenue and royalties pertaining to music in user generated content. The format, defined in Part 4 of the DSR standard, is scalable to the requirements of the sender and recipient of the message. 

If used in a way that makes use of all available functionalities within the profile, UGC sales/usage reports can become very large and thus be too large for some companies to ingest. At the other extreme, if only minimal functionality is used, the format may not provide all the data needed to meet the commercial requirements of the recipient of the message.

The UGC format allows for each “master recording” (communicated in an AS02 Record) to have n records which detail the sales/usage figures relating to the that master recording (SU03). Each of the sales/usage figures can then have m subscriber type records (ST01), which in turn can each have p licensor-specific usage records (LI01), and which in turn can each have q records detailing licensor-specific work information (MW01). 

For each master recording there can also be s resource usage records RU01 or RU02 that provide details of the UGC resources that contain the master recording. In addition, the format allows for r label copy records (LC01) that provide, for each master recording, label copy data in the form provided to the licensee that is creating and sending the UGC sales/usage report. 

The layout of such a Block is depicted below.

Even comparatively low numbers of nmpqr and s data elements can quickly lead to very long blocks. This leads to very large sales/usage reports.

However, not all of these record types have to be provided in a UGC sales/usage report. The following record types can be omitted to reduce the size of the report:

  • The label copy records LC01 can either be omitted entirely or, the number of these records can be limited to a number agreed between the licensee and the licensor;
  • The licensee and the licensor can agree to use the RU01 resource usage Record to provide details for multiple UGC recourses rather than using multiple RU02 Records which can only each provide details for one UGC resource that use the master recording;
  • The licensee and the licensor can agree to a limit of the number of UGC resources that are listed in a particular sales/usage report;
  • The licensee and the licensor can agree to a limit of the number of subscriber types that are listed in a particular sales/usage report. This may be achieved by providing separate Records of only the top five subscriber types and then collating the remaining subscriber types into a single figure for each master recording in the ST01 Records;
  • The licensee and the licensor can agree to completely omit the licensor-specific data that can be provided in the LI01 Records; and/or
  • The licensee and the licensor can agree to completely omit the licensor-specific musical work data provided to in the MW01 Records.

Each of the possible simplifications can be agreed between the licensor and the licensee and will reduce the file size and complexity. However, this will mean that less data is provided in the sales/usage report. 

The licensee and the licensor will need to strike a balance that works for them.

  • No labels