A.1 Deployment with minimal FLUS sub-functions

26.2383GPPRelease 17TSUplink streaming

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

A.1.1 Introduction

This clause describes deployments with minimal FLUS sub-functions from the standpoint that only F-U and F-C end-points are instantiated.

A.1.2 Deployment with a Media Source and a Control Source co-located in the same device

This clause describes a deployment scenario whereby the Control Source and the Media Source are implemented in the same device. The Media Source is provisioned via a local API, which includes at least the selected F-U instantiation, the Media Sink ingest information and optionally other information.

Figure A.1.2-1: Deployment with Minimal FLUS Subfunctions

It is assumed that the workflow is started from the Control Source. For example, via interaction with a User Interface (UI) and associated API, a human user causes the Control Source to set up and control the FLUS session. Additional application functions provision the Media Source (using the local API) according to the input to the Control Source.

A.1.3 Deployment with non-colocated Control Source and Media Source

This clause describes a deployment scenario whereby the Control Source and the Media Source are implemented in different functional entities. It is an example of the professional media production use case as described in TR 26.939 [22] whereby a production center facility, remotely located from the capture device, controls the establishment and termination of the FLUS session via F-C. The functional entity in which the Control Source is located is referred to as the CTRL entity.

Figure A.1.3-1: Deployment with minimal FLUS sub-functions

It is assumed that the workflow is started from the Control Source. For example, via interaction with an UI and associated API, a human operator causes the Control Source function to establish and control the FLUS session. It is assumed that the Media Source has a local GUI so that it can be provisioned, via the selected F-U instantiation, the Media Sink ingest information and other implementation-specific configurations.