Scenarios. This section presents an evolved description of the scenarios from D3.1 with a mapping to the presented FLAME architecture and the use cases above. Throughout all scenarios, we will represent each media component by a unique FQDN using the naming convention <COMPONENT_ACRONYM>.▇▇▇▇▇▇▇▇_▇▇▇▇.▇▇▇▇▇.▇▇ Furthermore, each relationship connector between two media components illustrates a direction representing the component that initiates and the component which serves. This information flow is reflected in the naming of the require service level agreement between two media components, i.e.: <SERVING_MEDIA_COMPONENT><INITIATING_MEDIA_COMPONENT>
Appears in 2 contracts
Sources: Grant Agreement, Grant Agreement