5.1.2 Communication via a Hub

5.1.2.1 Introduction

Licensees and Licensors can exchange the LicenseRequestMessage, LicenseMessage and LicenseRevocationMessage with the help of a central Hub. The standard supports two approaches to this:

  • The Hub acts solely as a router where the Message Sender addresses the message to the ultimate Message Recipient but sends the message, in accordance with Clause 5.2 or 5.3, to a Hub. The Hub then forwards the message to the ultimate Message Recipient, typically without ingesting any of the message content; or

  • The Hub acts as a message distributor where the Message Sender addresses the message to the Hub, which then determines, from the message content, the ultimate Message Recipient(s) and forwards the message.

This choreography does not allow the signalling back to the original Message Sender that the forwarding was successful.

Details for both approaches are provided below.

5.1.2.2 Hub as a Router

A prospective Licensee may send a LicenseRequestMessage to a Hub, expecting it to be delivered to a Rights Controller from which the prospective Licensee wishes to obtain a licence. The MessageHeader/MessageRecipent shall therefore contain the PartyId of the Rights Controller.

The Hub shall then forward the LicenseRequestMessage to the identified Rights Controller. If this communication is effected in accordance with this standard, the MessageHeader/MessageSender of the forwarded message shall be the Hub and the MessageHeader/SentOnBehalfOf shall be the sender of the original LicenseRequestMessage.

The same approach would be used for communicating LicenseMessages and LicenseRevocationMessages.

5.1.2.3 Hub as a Message Distributor

A prospective Licensee may also send a LicenseRequestMessage for one or more licences to a Hub addressed to the Hub, i.e. the MessageHeader/MessageRecipent shall contain the PartyId of the Hub.

The Hub shall then determine the appropriate Rights Controller(s) (by evaluating the Right Shares referenced in the LicenseRequest composite in the LicenseRequestMessage) and send new LicenseRequestMessage(s) to the identified Rights Controller(s). If this communication is effected in accordance with this standard, the MessageHeader/MessageSender of the forwarded message shall be the Hub and the MessageHeader/SentOnBehalfOf shall be the sender of the original LicenseRequestMessage.

The same approach would be used for communicating of LicenseMessages and LicenseRevocationMessages.

Search