A.2.3 Deployment with a Remote Controller co-located with a Control Sink sub-function
26.2383GPPRelease 17TSUplink streaming
This clause describes a deployment scenario whereby the Remote Controller is co-located with the Control Sink on the same functional entity. The Remote Control Target is deployed with the Media Source on the same device (the FLUS Source). 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, as well as performs remote control of the media capture equipment at a separate location (e.g., the event venue of a sports match or musical performance).
The FLUS Source is provisioned with the Remote Controller information via a local API. The FLUS Source receives the provisioning information of the selected F-U instantiation and the Media Sink ingest information via the Remote Control Interface.
It is possible to deploy FLUS Sink functions within a public cloud. The FLUS sink can be configured by a CTRL device, which is located behind a NAT / Firewall, such as within an enterprise network or within a PLMN. The FLUS Source functions are located on a wireless device, which is deployed within a PLMN. Traffic routing policies forbid the direct communication between the FLUS Sink and the CTRL entity.
Figure A.2.3-1: Deployment with a Remote Controller co-located with a Control Sink sub-function
It is assumed, that the CTRL device is used as the main control function. FLUS defines a framework which supports the extension of existing F-C or F-RC interfaces with implementation configurations.
It is assumed the service specific implementation extends the F-C information with additional FLUS Source configuration information, so that the CTRL device can be the origin of the FLUS Sink configuration and the FLUS Source configuration. The FLUS Source configuration is relayed by an implementation-specific function from the Control Sink into the Remote Controller using local APIs.
Annex B (informative):
Network-Based Media Processing (NBMP)
B.1. Introduction
MPEG NBMP in ISO/IEC 23090-8 [17] defines a framework that enables initializing and controlling media processing in the network. An NBMP Source describes the required media processing including the input and output formats and protocols, the required processing and configuration information. Based on this request, the NBMP Workflow Manager establishes the media processing workflow and informs the NBMP Source that the workflow is ready to start the processing. The Media Source(s) can then start transmitting their media to the network for processing.
NBMP control plane covers the following APIs (REST resources):
– Workflow API is used by NBMP Source to request NBMP Workflow Manager create and run a media processing workflow
– Function Discovery API provides the means for Workflow Manager and/or NBMP Source to discover media processing Functions that can be instantiated as part of a media processing Workflow.
– Task API is used by the NBMP Workflow Manager to configure, manage and monitor a Task at runtime.
The Workflow Description Document (WDD), Task Description Document (TDD) and Function Description Document (FDD) are exchanged using the above APIs as JSON objects.
On the media plane, NBMP describes the media formats, the metadata, and the supplementary information formats between the NBMP Source and the Task, as well as between the Tasks themselves.
Figure B.1 depicts the NBMP reference architecture depicting the above control plane and media plane interactions.
Figure X.1 – NBMP reference architecture
NBMP can be used for initiating media processing workflows such as 360 stitching, guided transcoding, overlaying on image or video backgrounds or view-dependent content customization.
B.2. NBMP Use in FLUS
The MPEG NBMP [17] Workflow Description Document (WDD) may be used to describe the media processing tasks at the FLUS sink to be performed on received media components from the FLUS source. As described in clause 5.3.6, NBMP WDD may be signalled as part of FLUS Sink Configuration properties.
Annex C (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-12 |
SA#78 |
SP-170884 |
Presented to TSG SA#78 (for approval) |
1.0.0 |
|||
|
2017-12 |
SA#78 |
Approved for Release 15 at TSG SA#78 |
15.0.0 |
||||
|
2018-03 |
SA#79 |
SP-180024 |
0001 |
3 |
F |
Corrections to FLUS Framework |
15.1.0 |
|
2018-12 |
SA#82 |
SP-180974 |
0004 |
3 |
F |
Architecture for QoS |
16.0.0 |
|
2019-06 |
SA#84 |
SP-190341 |
0003 |
6 |
B |
Remote Assist / Control Interface |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190651 |
0009 |
3 |
F |
FLUS Remote Control Procedures |
16.2.0 |
|
2019-12 |
SA#86 |
SP-190995 |
0011 |
2 |
F |
Correction of FLUS Media Indication |
16.3.0 |
|
2019-12 |
SA#86 |
SP-190995 |
0012 |
2 |
F |
Update, correction, and clarification of reference and text |
16.3.0 |
|
2019-12 |
SA#86 |
SP-190995 |
0013 |
1 |
C |
Removal of AsInf Feature |
16.3.0 |
|
2019-12 |
SA#86 |
SP-190995 |
0014 |
1 |
B |
Uplink Assistance via RAN Signaling |
16.3.0 |
|
2019-12 |
SA#86 |
SP-190995 |
0015 |
– |
B |
Amended QoS Signaling |
16.3.0 |
|
2020-03 |
SA#87-e |
SP-200037 |
0016 |
1 |
F |
Removal of deprecated clauses |
16.4.0 |
|
2020-03 |
SA#87-e |
SP-200037 |
0017 |
1 |
C |
NBMP Use in FLUS |
16.4.0 |
|
2020-03 |
SA#87-e |
Editorial Changes |
16.4.1 |
||||
|
2020-03 |
SA#87-e |
Editorial Changes |
16.4.2 |
||||
|
2020-06 |
SA#88-e |
SP-200389 |
0018 |
1 |
D |
Correction of References |
16.5.0 |
|
2020-06 |
SA#88-e |
SP-200389 |
0021 |
– |
B |
Media Codec Profile for E_FLUS |
16.5.0 |
|
2020-06 |
SA#88-e |
SP-200389 |
0022 |
– |
F |
Clarification on uplink assistance |
16.5.0 |
|
2020-06 |
SA#88-e |
SP-200389 |
0023 |
– |
F |
Update, correction and clarification of text |
16.5.0 |
|
2020-06 |
SA#88-e |
SP-200389 |
0024 |
1 |
B |
Adding Support for Remote Control |
16.5.0 |
|
2020-09 |
SA#89-e |
SP-200662 |
0025 |
2 |
F |
Correction of FLUS F-C Stage 3 |
16.6.0 |
|
2020-10 |
Post SA#89-e |
Update of Change History Table |
16.6.1 |
||||
|
2020-10 |
Post SA#89-e |
Attaching back the file – 3GPP FLUS MO.xml |
16.6.2 |
||||
|
2021-12 |
SA#94-e |
SP-211349 |
0026 |
1 |
C |
CR on the extending support for network-based media processing in FLUS |
17.0.0 |