Content for TR 26.939 Word version: 18.0.0
6 Guidelines for non-IMS-based FLUS
7 FLUS User Plane Instantiations
8 Example FLUS Workflows
9 Guidelines for QoS usage for FLUS
10 End-to-End Message Flows
11 Guidelines for Uplink Assistance for FLUS
12 FLUS Architecture Including UE-based Control Point and FLUS Remote Assist/Control
$ Change history
6 Guidelines for non-IMS-based FLUS p. 9
6.1 Use Case: Sharing to a Social Network Service p. 9
6.2 Use Case: Live uplink video stream from drones or moving vehicles p. 9
6.3 Use Case: Breaking-News reporter p. 10
6.4 Use Case: Immersive media conversations p. 10
6.5 Use Case: Feedback-enabled Control of Uplink Streaming |R16| p. 10
6.5.1 Use Case Description p. 10
6.5.2 Working Assumptions p. 11
6.5.3 Recommended Requirements p. 11
6.5.4 Gap Analysis p. 12
6.6 Use Case: Media production |R16| p. 12
6.6.1 General p. 12
6.6.2 Variants of the use case p. 13
6.6.2.1 Remote production p. 13
6.6.2.2 Local pre-production p. 13
6.6.2.3 Local complete production p. 13
6.6.3 Gap analysis p. 13
6.6.4 Recommended requirements p. 14
6.7 Use Case: Fisheye omnidirectional video sharing |R16| p. 14
6.8 Use Case: Live uplink streaming for V2X Services |R16| p. 15
7 FLUS User Plane Instantiations p. 20
7.1 Non-IMS-based User Plane Instantiations p. 20
7.1.1 Introduction p. 20
7.1.2 fMP4-based Instantiations p. 21
7.1.2.1 Introduction p. 21
7.1.3 fMP4 over MMTP Instantiation p. 21
7.1.3.1 General p. 21
7.1.3.2 MMTP Signaling p. 21
7.1.3.3 Synchronization p. 22
7.1.3.4 Session Initiation and Description p. 23
7.1.4 fMP4-based Instantiation with HTTP Delivery. p. 24
7.1.4.1 General Description p. 24
7.1.4.2 Rate Adaptation p. 25
7.1.5 fMP4-based Instantiation using multiple segments per track p. 26
8 Example FLUS Workflows p. 26
8.1 Example Workflow using F-U MMTP p. 26
8.2 Example Call Flow for fragmented MP4 with HTTP Delivery p. 28
8.2.1 Assumptions p. 28
8.2.2 CMAF Format Example p. 30
8.3 Example workflow for a drone mounted camera |R16| p. 32
8.3.1 Introduction p. 32
8.3.2 Possible architecture p. 32
8.3.3 Example Call Flow 1 p. 33
8.3.4 Example Call Flow 2 p. 35
8.4 Example FLUS call flow with Network Based Media Processing (NBMP) |R17| p. 37
8.4.1 Overview p. 37
8.4.2 NBMP in the Application Server (All-AP) p. 37
8.4.2.1 Architecture p. 37
8.4.2.2 Call flow p. 38
8.4.2.3 Interfaces p. 39
8.4.2.4 Gap Analysis p. 40
8.4.3 NBMP in the Application Server, MPE in Sink (MPE-Sink) p. 41
8.4.3.1 Architecture p. 41
8.4.3.2 - p. 42
8.4.3.2.1 Through F1 p. 42
8.4.3.2.2 Through N3 p. 43
8.4.3.4 Gap analysis p. 44
8.4.4 NBMP Client in the Application Server, NBMP Workflow Manager, and MPE in Sink (WM-MPE-Sink) p. 46
8.4.4.1 Architecture p. 46
8.4.4.2 Call Flow p. 47
8.4.4.3 Interfaces p. 48
8.4.4.4 Gap Analysis p. 48
8.4.4.5 Mapping call flow to the standard APIs p. 49
8.4.5 NBMP Client in the FLUS Control Source, NBMP Workflow Manager, and MPE in Sink (NBMPSource-FLUSSource) p. 50
8.4.6 NBMP Client in the UA, NBMP Workflow Manager in the Application Server, and MPE in Sink (NBMPSourceUA-NBMPWMAS) p. 53
8.4.6.1 Architecture p. 53
8.4.6.2 Call flow p. 54
8.4.6.2.1 Through F1 p. 54
8.4.6.2.2 Through N3 p. 55
8.4.6.3 Interfaces p. 56
8.4.6.4 Gap analysis p. 56
8.4.7 NBMP Client in the UA, NBMP Workflow Manager, and MPE in the Application Server (NBMPSourceUA-NBMPWMSINK) p. 59
8.4.7.1 Architecture p. 59
8.4.7.2 Call flow p. 59
8.4.7.3 Interfaces p. 60
8.4.7.4 Gap analysis p. 61
8.4.8 NBMP-enabled FLUS Session Establishment using 5GMSu AF (WM-MPE-Sink-AF) p. 62
8.4.8.1 Architecture p. 62
8.4.8.2 Call flow p. 62
8.4.8.3 Interfaces p. 64
8.4.8.4 Gap analysis p. 64
8.4.9 Summary of the deployment scenarios p. 65
9 Guidelines for QoS usage for FLUS p. 66
9.1 Use-Case introduction p. 66
9.2 Discussion of the 3GPP QoS Framework p. 68
9.2.1 Introduction p. 68
9.2.2 Architectures for QoS-based Content Delivery p. 68
9.2.2.1 General |R16| p. 68
9.2.2.2 QoS Control in IMS/MTSI-based FLUS |R16| p. 68
9.2.2.3 QoS Control in non-IMS/MTSI-based FLUS, Direct Interaction between AF and PCRF/PCF |R16| p. 69
9.2.2.4 QoS Control in non-IMS/MTSI-based FLUS, Indirect Interaction between AF and PCRF/PCF via SCEF/NEF |R16| p. 69
9.2.3 Relevant 3GPP sections p. 70
9.2.4 Usage of 3GPP QoS parameters p. 71
9.2.5 Desired QoS flow ehaviour p. 72
9.2.6 Desired QoS latency behavior |R16| p. 73
9.2.6.1 Typical Latencies for Live Streaming Services p. 73
9.2.6.2 Latency of User-Generated Live Uplink Streaming to Social Networks p. 74
9.2.6.3 Determining New Packet Delay Budgets for 3GPP QCIs and 5QIs p. 74
9.2.6.4 Packet Loss Rates p. 75
9.2.6.5 New QCI/5QIs for FLUS p. 75
9.2.6.6 Media Encoding Latencies p. 76
10 End-to-End Message Flows |R16| p. 76
10.1 General p. 76
10.2 Mobile Network Operator Provided Live Uplink Streaming Service p. 76
10.3 3rd Party Provided Live Uplink Streaming Service with Downlink Distribution Handlled by Mobile Operator p. 78
11 Guidelines for Uplink Assistance for FLUS |R16| p. 79
11.1 Uplink Assistance for FLUS based on UNA mechanisms p. 79
11.1.1 Introduction p. 79
11.1.2 Network Assistance within the FLUS architecture p. 80
11.1.3 Network Assistance for FLUS workflow p. 80
11.2 Uplink Assistance for FLUS using RAN Signalling p. 81
11.3 Analysis p. 82
12 FLUS Architecture Including UE-based Control Point and FLUS Remote Assist/Control |R16| p. 83
12.1 FLUS Architecture Considering UE-based Control Point p. 83
12.2 Functionality to be Supported by F-RAC p. 84
12.2.1 Remote Command/Control Information p. 84
12.2.2 Remote Assistance Information Collection and Transfer p. 84
A.1 General p. 86
A.2 Audio p. 86
A.3 Video p. 86
A.4 Examples of SDP offers and answers p. 87
$ Change history p. 89
