|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
5G;
Uplink streaming
(3GPP TS 26.238 version 15.1.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 1 ETSI TS 126 238 V15.1.0 (2018-07)
Reference
RTS/TSGS-0426238vf10
Keywords
5G,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 2 ETSI TS 126 238 V15.1.0 (2018-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 3 ETSI TS 126 238 V15.1.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 System architecture . 7
4.1 General . 7
4.2 System . 7
4.2.1 General . 7
4.2.2 Uplink streaming for MTSI . 9
4.2.3 Uplink streaming for PSS-based distribution . 10
4.3 Terminal . 10
4.4 Procedures . 11
4.4.1 General . 11
4.4.2 FLUS session establishment . 11
4.4.3 FLUS session update . 12
4.4.4 FLUS sink capability discovery . 12
4.4.5 FLUS session termination . 12
4.5 FLUS source systems . 12
4.5.1 Introduction. 12
4.5.2 General source systems . 12
4.5.3 Vendor-specific source system . 14
4.5.4 Default source system . 14
4.5.5 3DOF FLUS source system . 15
4.5.5.1 Introduction . 15
4.5.5.2 Coordinate system . 15
4.5.5.3 Descriptive Parameters . 16
5 Protocols . 17
5.1 General . 17
5.2 IMS-based system . 18
5.2.1 System configuration . 18
5.2.1.1 Introduction . 18
5.2.1.2 FLUS sink configuration and selection . 18
5.2.1.2.1 UE-based FLUS sink . 18
5.2.1.2.2 Network-based FLUS sink . 18
5.2.1.3 FLUS management object . 18
5.2.2 Session management . 20
5.2.3 Data transport . 20
5.3 Generic FLUS system . 20
5.3.1 System configuration . 20
5.3.2 Session management . 20
5.3.2.1 FLUS sink capability discovery . 20
5.3.2.2 FLUS session establishment . 20
5.3.2.4 FLUS session update . 21
5.3.2.5 FLUS session termination . 22
5.3.2.6 List of FLUS sink capabilitie s . 22
5.3.2.7 List of FLUS session properties . 22
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 4 ETSI TS 126 238 V15.1.0 (2018-07)
5.3.3 Data transport . 23
6 Terminal capabilities . 23
6.1 General . 23
7 Uplink Streaming Control Interface . 24
7.1 General . 24
7.1.1 Resources . 24
7.1.1.1 Sink Resource . 24
7.1.1.2 Session Resource . 24
7.1.2 Supported Methods . 25
7.1.3 Error Handling . 25
7.2 Discovery . 25
7.3 Capability retrieval . 25
7.4 Uplink streaming configuration . 26
7.4.1 FLUS session properties fetch procedure . 26
7.4.2 FLUS session update procedure. 27
7.4.2.1 Partial modification of FLUS session . 27
7.4.2.2 Full modification of FLUS session . 28
7.5 Session establishment . 28
7.6 Session termination . 29
8 FLUS Security . 30
8.1 IMS-based FLUS . 30
8.2 Non-IMS-based FLUS . 30
Annex A (informative): Change history . 31
History . 32
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 5 ETSI TS 126 238 V15.1.0 (2018-07)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The Framework for Live Uplink Streaming (FLUS) is an enabler for live media streaming from a source entity to a sink
entity. FLUS offers an IMS-based and a non-IMS-based instantiation. The IMS/MTSI-based instantiation enables the
establishment of live media streaming between two UEs or between a source entity and a sink entity, within and across
operator networks. Compared with MTSI, where limited types of QoS for speech or video media are used, FLUS can
provide a wider range of QoS operation, e.g., in the maximum delay, available bandwidth or target packet loss rate.
In the non-IMS-based instantiation, it is possible to operate FLUS as a more generic framework that is controlled
through a RESTful API and that supports other media plane protocols (i.e. not based on IMS or MTSI).
In addition to providing a wider range of QoS operation over radio links, other advanced functionalities of FLUS, such
as the signalling of immersive media, can be used to complement existing 3GPP services.
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 6 ETSI TS 126 238 V15.1.0 (2018-07)
1 Scope
The present document defines a FLUS source entity and a FLUS sink entity that can support point-to-point transmission
of speech/audio, video, and text. It defines media handling (e.g., signalling, transport, packet-loss handling, and
adaptation). The goal is to ensure a reliable and interoperable service with a predictable media quality while allowing
for flexibility in the service offerings.
A FLUS source entity, which may be embedded in a single UE, or distributed among a UE and separate audio-visual
capture devices, may support all or a subset of the features specified in this document.
When used as a generic framework, only the F-C procedures for establishing the FLUS session are required to be
supported by the source and sink entities, and no other feature or procedure specified in this document is mandated.
Impact on the service quality and network capacity is left to the discretion of the implementation and the service
utilizing the framework. For example, configuration of media formats and codecs follows the requirements of the
respective service.
When offered as part of a 3GPP IMS/MTSI service, the source and sink are required to support the IMS control plane
and media plane procedures, and the service quality is determined by the MTSI service policy.
The specification is written in a forward-compatible way in order to allow additions of media components and
functionality in releases beyond Release 15.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] Recommendation ITU-R BS.2051-1 (06/2017): "Advanced Sound System for Programme
Production".
[3] ISO/IEC DIS 23090-2: "Omnidirectional Media Format. N16824".
[4] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and
interaction".
[5] 3GPP TS 26.235: "Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols
and codecs".
[6] 3GPP TS 24.147: "Conferencing using the IM Multimedia (IM) Core Network (CN) subsystem;
Stage 3”.
[7] 3GPP TS 23.003: "Numbering, addressing and identification".
[8] 3GPP TS 33.203: "3G security; Access security for IP-based services".
[9] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[10] 3GPP TS 33.328: "IP Multimedia Subsystem (IMS) media plane security".
[11] IETF RFC 7231: "Hypertext transfer protocol (HTTP/1.1): Semantics and Content".
[12] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP)
and Session Description Protocol (SDP); Stage 3".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 7 ETSI TS 126 238 V15.1.0 (2018-07)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1].
FLUS session: A logical association between a source and a sink within which media content can be sent from the
source to the sink.
Media session: A subset or part of a FLUS session including the duration to establish the media session, the time period
during which media content can be sent from FLUS source to FLUS sink and the duration to terminate the media
session. One or more media sessions are delivered during a FLUS session. A media session may be established and
controlled by a well-defined control protocol.
Media stream: The content sent from a FLUS source to a FLUS sink within a media session.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
FLUS Framework for Live Uplink Streaming
HMD Head Mounted Display
IMS IP Multimedia Subsystem
4 System architecture
4.1 General
This clause introduces the system architecture for FLUS.
4.2 System
4.2.1 General
Figure 4.2-1 depicts the architecture showing the relevant entities for providing an uplink streaming service.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 8 ETSI TS 126 238 V15.1.0 (2018-07)
Figure 4.2-1: FLUS architecture
The uplink streaming service architecture is based on a FLUS source located in a UE and a FLUS sink located in either
another UE or in the network.
The FLUS source receives media content from one or more capture devices. In the context of this specification, the
capture devices are considered as parts of a UE or are connected to it.
When the FLUS sink is located in a UE, the FLUS sink shall forward media content to a decoding and rendering
function.
When the FLUS sink is located in the network, the FLUS sink may forward media content to a processing or
distribution sub-function. The processing and distribution sub-functions are not in scope of the present specification.
The FLUS sink may act as a Media Gateway Function (MGW) and/or an Application Function (AF).
The F reference point connects a FLUS source and a FLUS sink. The F reference point enables the FLUS source to
establish and control a single FLUS session.
The F reference point also enables the FLUS sink and the FLUS source to mutually authenticate and authorize each
other.
The F reference point shall support security function for confidentiality protection of both the FLUS control plane (F-C)
and FLUS user plane (F-U).
Details of the FLUS control plane and FLUS user plane functions are shown in Figure 4.2-2.
Figure 4.2-2: Sub-functions of FLUS
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 9 ETSI TS 126 238 V15.1.0 (2018-07)
Note that in the above diagram, hatched-filled boxes represent FLUS control plane functionality, solid line boxes
represent mandatory functionality, and dashed-line boxes corresponds to optional functionality. Also, note that F-C and
F-U denote FLUS control and FLUS user plane functionalities, respectively, and do not represent reference points.
FLUS ctrl and F-C: FLUS control plane functionality including the associated processing by FLUS sink of the uploaded
media for subsequent downstream distribution, plus FLUS media instantiation selection. F-C may also support
configuration of static metadata for the session.
FLUS media and F-U: FLUS user plane functionality which includes setup of one or more media sessions and
subsequent media data transmission via media streams. In some cases, a media session establishment protocol (e.g. IMS
session set-up for MTSI-based FLUS instantiation) is necessary.
NOTE : F-C is not needed when the FLUS sink is an MTSI client that is only capable of rendering. In such event,
logical control plane functions such as media and session descriptions and support for FLUS session
establishment are encapsulated in FLUS user plane functionality.
F-C is used to establish and control the FLUS session. F-C allows the FLUS source to
- select a FLUS media instantiation,
- provision static metadata associated with each media session present in the FLUS session,
- select and configure the processing and distribution sub-functions.
The FLUS media instantiation is defined as part of the FLUS session. The user plane (F-U) may also contain the media
stream establishment procedures when needed. Multiple media streams may be established for one FLUS session.
A media stream may contain media components of a single content type, e.g., audio, or media components of different
content types, e.g., audio and video. A FLUS session may be composed of more than one media stream containing the
same content type, e.g., multiple media streams of video.
4.2.2 Uplink streaming for MTSI
The architecture of uplink streaming for MTSI is depicted in Figure 4.2-3.
Figure 4.2-3: Uplink streaming for MTSI
The reception function of an MTSI client, i.e., the “MTSI rx client” as shown in Figure 4.2-3, is used to realize the
FLUS media receiver components in the FLUS sink. The FLUS sink may be instantiated as another UE or as an MTSI
rx client function in the network.
F-U contains all MTSI-related signalling.
The transmission function of an MTSI client, MTSI tx client, is used to realize the FLUS media sender components in
the FLUS source.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 26.238 version 15.1.0 Release 15 10 ETSI TS 126 238 V15.1.0 (2018-07)
4.2.3 Uplink streaming for PSS-based distribution
The architecture of uplink streaming for subsequent PSS distribution is depicted in Figure 4.2-4.
Figure 4.2-4: Uplink streaming for PSS
The PSS Content Source is located on the UE side and contains the FLUS source.
4.3 Terminal
The functional components of a terminal including both a FLUS source and a FLUS sink that uses 3GPP access are
shown in figure 4.3-1.
Speaker Audio Renderer Audio Decoder
Video Renderer Video Decoder
Display
Timed Media
Decoder
Media
Controller
Microphone Audio Pre-
Audio Encoder
System processor
Camera Video Pre-
Video Encoder
System processor
Media Capture Timed Media
System Encoder
User Session Setup
Interface and Control
NOTE 1: It is not required that all components of a FLUS source or a FLUS sink are included in a terminal.
Figure 4.3-1: Functional components of a FLUS source and a FLUS sink
The scope of the present document is to specify media handling and interaction,
...