5.1 Introduction

The message protocols by which a message sender actually communicates an individual message created in accordance with this part of the RDR standard to a message recipient are defined in Part 1 of the RDR standard (RDR-C).

Figure 1 and Figure 2 show the choreography for the messages defined in this part of the RDR standard that enable the communication of data about revenue. The choreography defined in these figures is the same whether using the RevenueReport message or the RevenueDetails message on its own or in combination with the RevenueSummary message. Figure 1 shows the choreography of the messages when only a music licensing company and a rights controller or administrator is involved in the communication.

image-20240910-111216.png

Figure 1 – Choreography for the exchange of RDR-R messages between a music licensing company and a rights controller

 

Figure 2 shows the choreography of the messages when more than one music licensing company is involved either for the exchange of revenue data in respect of international mandate claims, or when more than one music licensing company or administrator has the mandate to claim in the same territory requiring one music licensing company to communicate such revenue data to a second music licensing company being it is communicated to the relevant rights controllers or administrator.

image-20240910-111206.png

Figure 2 – Choreography for the exchange of RDR-R messages involving two music licensing companies and a rights controller

 

Table 1 summarises the point in the relevant business processes when the messages are sent. The table also indicates who sends the message to whom.

Message Name

Initiating Event

Sender

Recipient

RevenueReport

A music licensing company has generated or received revenue from the use of sound recordings, and/or music videos, and/or audio-visual resources containing music, for which it has received a claim, and wishes to report these revenues to a rights controller or administrator (Figure 1).

Collecting/paying music licensing company

Rights controller or administrator that made a claim in respect of the sound recordings, and/or music videos, and/or audio-visual resources containing music to the collecting music licensing company

RevenueSummary

+

RevenueDetails

A music licensing company has generated or received revenue from the use of sound recordings and/or music videos, and/or audio-visual resources containing music, for which it has received a claim, and wishes to report these revenues to rights controller or administrator (Figure 1).

 When communicating a RevenueDetails message, instead of sending the associated summary data using the RevenueSummary message, the music licensing company may, subject to bilateral agreements, use other formats instead.

Collecting/paying music licensing company

Rights controller or administrator that made a claim in respect of the sound recordings and/or music videos, and/or audio-visual resources containing music, to the collecting music licensing company

RevenueReport

A music licensing company has generated or received revenue from the use of sound recordings, music videos, and/or audio-visual resources containing music, for which it has received a claim from a claiming music licensing company and wishes to report these revenues to the claiming music licensing company (Message 1 in Figure 2).

Collecting/paying music licensing company

Claiming/collecting music licensing company that made a claim for the use of sound recordings and/or music videos, and/or audio-visual resources containing music, to the claiming/collecting music licensing company

RevenueSummary

+

RevenueDetails

A music licensing company has generated revenue from the use of sound recordings and/or music videos, and/or audio-visual resources containing music, for which it has received a claim from a claiming music licensing company and wishes to report these revenues to the claiming music licensing company (Message 1 in Figure 2).

 When communicating a RevenueDetails message, instead of sending the associated summary data using the RevenueSummary message, the music licensing company may, subject to bilateral agreements, use other formats instead.

Collecting/paying music licensing company

Claiming/collecting music licensing company that made a claim for sound recordings and/or music videos, and/or audio-visual resources containing music, to the claiming/collecting music licensing company

RevenueReport

A claiming/collecting music licensing company has received revenue from a collecting/paying music licensing company and wishes to report these revenues to a rights controller or administrator (Message 2 in Figure 2).

Claiming/paying music licensing company

Rights controller or administrator that made a claim in respect of the sound recordings and/or music videos, and/or audio-visual resources containing music, to the claiming/paying music licensing company

RevenueSummary

+

RevenueDetails

A claiming/collecting music licensing company has received revenue from a collecting/paying music licensing company and wishes to report these revenues to a rights controller or administrator (Message 2 in Figure 2).

When communicating a RevenueDetails message, instead of sending the associated summary data using the RevenueSummary message, the music licensing company may, subject to bilateral agreements, use other formats instead.

Claiming/paying music licensing company

Rights controller or administrator that made a claim in respect of the sound recordings and/or music videos, and/or other audio-visual resources containing music, to the claiming/paying music licensing company

Table 1 – Messages in the RDR Revenue Reporting

 

Each RevenueSummary message may be accompanied by one or multiple RevenueDetails messages each providing detailed data about different content or usage types.