Content for TR 26.925 Word version: 19.0.0
7 Characteristics and requirements for different media services on 3GPP networks
7.1 Introduction
7.2 Collection process for requirements for different media services on 3GPP networks
7.3 Summary of Responses for Streaming Services
7.3.1 Introduction
7.3.2 Used Technologies
7.3.3 Traffic Characteristics
7.4 Summary of Characteristics for haptics media
...
...
7 Characteristics and requirements for different media services on 3GPP networks p. 21
7.1 Introduction p. 21
This clause collects characteristics and requirements for different media services on 3GPP networks.
7.2 Collection process for requirements for different media services on 3GPP networks p. 22
Use cases are collected in the context of the present document. The use cases come with an analysis of certain characteristics. For this purpose a template is provided below.
| Media Service Description |
|---|
|
Name:
[e.g. StreamOn]
Date of submission:
[e.g. 18th October 2018]
Source:
[e.g. DT]
Description:
[Free text giving high level description of the service]
|
| Categorization |
|
Type:
[e.g. Third Party, Operator, Combination of both, Other]
Status:
[e.g. planned, PoC, trialed, commercially deployed]
Category:
[e.g. Download, Live streaming, On-demand streaming, Interactive, Conversational]
|
| Used Technologies |
|
Codecs:
[e.g. AAC, HE-AAC, HEVC/H.265, AVC/H.264 with Profiles and levels used]
Media types and formats:
[e.g. 4K video, HDR video, stereo or 5.1 audio]
Media protocols and containers:
[e.g. DASH, HLS, CMAF, ISOBMFF, MP4, MPEG2 TS, RTP]
Transport protocols:
[e.g. FLUTE, UDP, TCP, QUIC, HTTP 1.1, HTTP 2.0]
Clients:
[e.g. iOS or android application, browser, set top boxes, TV set]
Others:
[e.g. DRM, interactivity framework, QoE and analytics, QoS handling]
|
| Deployment Statistics |
| [e.g. number of clients, traffic volumes] |
| Traffic Characteristics |
|
Bitrate Characteristics:
[typical target bitrates, minimum required bitrate, maximum necessary bitrate,]
Other KPIs:
[end-to-end latency, tune-in times, etc.]
Potential mapping to 5QIs (5G QoS Identifier - See clause 5.7.4 of TS 23.501 and Table 5.7.4-1 copied below):
[which 5QIs among 1, 2, 3, 4, 6, 7, 8, 9, 80, e.g. 6, "video buffered streaming and TCP based"]
|
| References |
| [list of public documentation in support of the present description e.g. a URL, a scientific publication, an industry or standards organization specification] |
| Any additional information |
| 5QI Value | Resource Type | Default Priority Level | Packet Delay Budget | Packet Error Rate | Default Maximum Data Burst Volume (NOTE 2) | Default Averaging Window | Example Services |
|---|---|---|---|---|---|---|---|
| 1 | GBR
(NOTE 1) | 20 | 100 ms | 10-2 | N/A | 2000 ms | Conversational Voice |
| 2 | 40 | 150 ms | 10-3 | N/A | 2000 ms | Conversational Video (Live Streaming) | |
| 3 | 30 | 50 ms | 10-3 | N/A | 2000 ms | Real Time Gaming, V2X messages Electricity distribution - medium voltage, Process automation - monitoring | |
| 4 | 50 | 300 ms | 10-6 | N/A | 2000 ms | Non-Conversational Video (Buffered Streaming) | |
| 65 | 7 | 75 ms | 10-2 | N/A | 2000 ms | Mission Critical user plane Push To Talk voice (e.g., MCPTT) | |
| 66 | 20 | 100 ms | 10-2 | N/A | 2000 ms | Non-Mission-Critical user plane Push To Talk voice | |
| 67 | 15 | 100 ms | 10-3 | N/A | 2000 ms | Mission Critical Video user plane | |
| 75 | 25 | 50 ms | 10-2 | N/A | 2000 ms | V2X messages | |
| 5 | Non-GBR
(NOTE 1) | 10 | 100 ms | 10-6 | N/A | N/A | IMS Signalling |
| 6 | 60 | 300 ms | 10-6 | N/A | N/A | Video (Buffered Streaming) TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) | |
| 7 | 70 | 100 ms | 10-3 | N/A | N/A | Voice, Video (Live Streaming) Interactive Gaming | |
| 8 | 80 | 300 ms | 10-6 | N/A | N/A | Video (Buffered Streaming) TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) | |
| 9 | 90 | ||||||
| 69 | 5 | 60 ms | 10-6 | N/A | N/A | Mission Critical delay sensitive signalling (e.g., MC-PTT signalling) | |
| 70 | 55 | 200 ms | 10-6 | N/A | N/A | Mission Critical Data (e.g. example services are the same as QCI 6/8/9) | |
| 79 | 65 | 50 ms | 10-2 | N/A | N/A | V2X messages | |
| 80 | 68 | 10 ms | 10-6 | N/A | N/A | Low Latency eMBB applications Augmented Reality | |
| 82 | Delay Critical GBR | 19 | 10 ms
(NOTE 4) | 10-4 | 255 bytes | 2000 ms | Discrete Automation (see TS 22.261) |
| 83 | 22 | 10 ms
(NOTE 4) | 10-4 | 1358 bytes
(NOTE 3) | 2000 ms | Discrete Automation (see TS 22.261) | |
| 84 | 24 | 30 ms
(NOTE 6) | 10-5 | 1354 bytes | 2000 ms | Intelligent transport systems (see TS 22.261) | |
| 85 | 21 | 5 ms
(NOTE 5) | 10-5 | 255 bytes | 2000 ms | Electricity Distribution- high voltage (see TS 22.261) | |
|
NOTE 1:
A packet which is delayed more than PDB is not counted as lost, thus not included in the PER.
NOTE 2:
It is required that default MDBV is supported by a PLMN supporting the related 5QIs.
NOTE 3:
This MDBV value is set to 1354 bytes to avoid IP fragmentation for the IPv6 based, IPSec protected GTP tunnel to the 5G-AN node (the value is calculated as in Annex C of TS 23.060 and further reduced by 4 bytes to allow for the usage of a GTP-U extension header).
NOTE 4:
A delay of 1 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface.
NOTE 5:
A delay of 2 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface.
NOTE 6:
A delay of 5 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface.
|
|||||||
7.3 Summary of Responses for Streaming Services p. 25
7.3.1 Introduction p. 25
This clause provides a summary of the information that was collected for streaming services. The current information is based on responses from:
- Comcast VIPER
- AWS Media Services
- Hulu
- Bitmovin
- ARD Mediathek
7.3.2 Used Technologies p. 25
7.3.2.1 Codecs p. 25
The pre-dominant video codec for the services is still H.264/AVC [14]. H.265/HEVC [15] is also in deployments. Non-MPEG video codecs such as VP9 or AV1 are in use or expected to be in use, but much less prominent than MPEG codecs according to the responses.
The pre-dominant audio codec is AAC, with some variants. Also, AC-3 is used quite often to support beyond stereo experiences. No other audio codec was mentioned.
7.3.2.2 Media types and formats p. 25
Most of the services run HD video. Experiments with UHD and HDR are ongoing. Different HDR formats (i.e. HDR10, Dolby Vision, HLG, and SL-HDR) are in use.
For audio, stereo is deployed and 5.1 is also broadly used. Some initial experiments are done with multichannel audio, NGA (Next Generation Audio).
7.3.2.3 Media protocols and containers p. 26
All services deploy DASH and HLS. On HLS, the MPEG-2 TS still is maintained. For DASH, exclusively ISO BMFF based distribution is used but a convergence towards a common segment format based on CMAF for DASH and HLS is expected.
Other formats such as RTMP or RTP are maintained to some extent for legacy reasons.
7.3.2.4 Transport protocols p. 26
HTTP/1.1 with TCP/IP is used almost exclusively. Some initial tests are ongoing on HTTP/2.0 and HTTP/3 (also known as HTTP over QUIC). No received response indicates the use of multicast protocols.
7.3.2.5 Clients p. 26
All services provide client application running on iOS and Android for Browser-based playback as well as applications or native integration into set-top boxes, HDMI sticks (i.e. Apple TV™, Fire TV™, Chromecast™, Tizen™) and TV Sets. Game consoles are also targeted.
7.3.2.6 Other Technologies p. 26
Other mentioned deployed technologies are:
- DRM (Widevine, PlayReady, Fairplay) based on common encryption
- Analytics collection and QoE Measurement
- Dynamic Ad Insertion
- Watermarking
7.3.3 Traffic Characteristics p. 26
7.3.3.1 Bitrate Characteristics p. 26
Average streaming bitrate
- STBs: 4-6Mbps
- Mobile applications and browsers: less than 4-6Mbps
- 4K content: 10-15Mbps
- 6 seconds
7.3.3.2 Other KPIs p. 26
Other KPIs such as video start time, video playback failure, rebuffering ratio, connection induced rebuffering, minimum/average bitrates, ABR adaptation frequency were not reported.
7.3.3.3 Potential mapping to 5QIs p. 26
Commonly targeted 5QI values are 6 and 8. Others are considered interesting for specific services.
7.4 Summary of Characteristics for haptics media p. 27
7.4.1 Bitrate Characteristics p. 27
See clause 5.7
7.4.2 Other KPIs p. 27
7.4.2.1 Introduction p. 27
The QoS factors influencing the QoE for haptics media enhanced services as described in the use-cases of clause 5 of TR 26.854 are mostly similar to those used for traditional AV and immersive AV services (jitter, delay, packet loss, etc). The asynchronicity between haptics and other media is a prevalent parameter to be considered when using haptics along with other media. Another characteristic of parametric-coded haptics media is the presence of silent units alongside temporal and spatial units; which can be taken into account when setting PDU Set Importance.
7.4.2.2 Asynchronicity between haptics and other media p. 27
TR 26.854 reports that that haptics effects perceived prior to visual cues is less detrimental to the user experience than the reverse and that asynchronicity is more tolerable in scenarios involving passive user involvement than active user involvement.
The suitable threshold for asynchronicity is listed in Table 7.4.2.2-1.
| Use case | Media | Tolerable asynchronicity threshold (note 1) | |
|---|---|---|---|
| Haptic enhanced media distribution | audio-haptics | audio delay: 100ms | haptic delay: 50ms |
| visual-haptics | visual delay: 80ms | Haptic delay: 60ms | |
| >Haptic enhanced communication | audio-haptics | audio delay: 3 frames (25ms) | haptic delay: 1 frame (12ms) |
| Visual-haptics | Visual delay: 20ms | Haptic delay: 30ms | |
| Immersive games and Immersive multimodal XR and metaverse | audio-haptics | audio delay: 50 ms | haptic delay: 25 ms 1 frame for gaming |
| visual-haptics | visual delay: 15 ms | Haptic delay: 50 ms | |
| Immersive entertainment | audio-haptics | audio delay: 25 ms | haptic delay: 12 ms |
| visual-haptics | visual delay: 20 ms | Haptic delay: 30ms | |
|
NOTE:
For each media component, "delay" refers to the case where that media component is delayed compared to the other.
|
|||
7.4.2.3 Potential mapping to 5QIs p. 27
Whether the 5QIs defined in [10] for media streaming and communication services are sufficient to enable haptics media enhanced services may need to be studied further.
