top of page

17.06.22 - Call 1: 5G and Media, all we need to know - Target 2023

For the full context on the process please visit the following link.

 

CALL 1 - 5G and Media, all what we need to know.


DATE: Friday 17th June 2022

TIME: 15:00-16:45 CEST / 9:00-10:45 EDT / 18:30-20:15 IST / 21:00-22:45 CST

LOCATION: ON-LINE

AUDIENCE: Open participation. The attendance is free for all participants and is open to the public, whether or not 5G-MAG members.



Call 1 - Agenda - 5G & Media, all we need to know

Introduction, Scope and Roadmap Planning, by David Vargas (BBC / 5G-MAG CD-T Chair).


Rel-16 5G Media Streaming - Introduction, by Thorsten Lohmar (Ericsson) and Frédéric Gabin (Dolby and 3GPP SA4 Chair)


Rel-16 5G Media Streaming - Dynamic network QoS policies, by Thorsten Lohmar (Ericsson) and Imed Bouazizi (Qualcomm)


Rel-17 5G Media Streaming over eMBMS, by Thomas Stockhammer (Qualcomm) and Richard Bradbury (BBC)


Rel-17 Edge Applications for Streaming, by Imed Bouazizi (Qualcomm), Richard Bradbury (BBC) and Iraj Sodagar (Tencent)


Rel-17 5G Multicast Broadcast Services, by Richard Bradbury (BBC) and Thorsten Lohmar (Ericsson)


Rel-17 Event exposure framework, by Richard Bradbury (BBC), Chales Lo (Qualcomm) and Imed Bouazizi (Qualcomm)


Rel-17 eXtended Reality, by Thomas Stockhammer (Qualcomm) and Frédéric Gabin (Dolby)


What are we proposing to do now?

Next steps towards Call 2:



 

Stay tuned, Call 2 is scheduled on the 8th July 2022. Those that have attended the Call 1 do not need to register again.


Follow the process here.


What was discussed on the chat is here:

15:38:18 From Daniel Silhavy (Fraunhofer FOKUS) to Everyone:

some questions from side:

- how is the qos/premium playback (use case 1) related to network slicing?

- Use case 2: Is this limited to type2 or type 3 players where you have full control over the media player and a corresponding API to control the ABR behavior? Or is this controlled also by proxying manifests and make this work on native/type 1 players?

15:46:12 From [Verizon] Jack Arky to Everyone:

- Can QoS policies be enforced when using transparent mode in media delivery (ie no definition of media format from carrier perspective)?

15:46:21 From [Ericsson] Thorsten Lohmar to Everyone:

@Daniel: Network Slicing may be one realization to provide the separated treatment. The 5G System provider may have views or preferences, which tool is best for providing the network service for prioritization.

15:48:37 From [Ericsson] Thorsten Lohmar to Everyone:

@Daniel: on "Use case 2: Is this limited to type2". Not sure, what a type 2 vs a type 3 player is. However, there should be certainly some monitoring, whether the Player is behaving according to the policy. It is certainly possible to enforce by a traffic shaper.

15:49:45 From Daniel Silhavy (Fraunhofer FOKUS) to Everyone:

Thanks Thorsten 🙂

15:53:04 From [Ericsson] Thorsten Lohmar to Everyone:

@Jack "Can QoS policies be enforced when using transparent mode …": This is a bit tricky, which information can be shared and which information not. The concept here is to prevent sharing detailed information of the content. An MPD for example contains details information about the actual video, i.e. much more than just the format.

15:56:00 From [Verizon] Jack Arky to Everyone:

Hello Thorsten. Same! Good to see/hear you. I think there should be a use case for support of transparent mode. Understood that knowledge of media will be limited. But this was a major request of content providers in past: they want to be able to "bring their own content." Hope the reference tools group will consider this use case.

15:59:35 From [Ericsson] Thorsten Lohmar to Everyone:

Hi Jack, this was actually one guiding use-case in the work. Would be good to discuss / study, whether it fulfils the needs.

16:00:42 From [Verizon] Jack Arky to Everyone:

@thorsten. Good to know. Can you send me reference? Thanks.

16:02:08 From [Ericsson] Thorsten Lohmar to Everyone:

https://www.3gpp.org/DynaReport/26512.htm

16:02:11 From [Ericsson] Thorsten Lohmar to Everyone:

https://www.3gpp.org/DynaReport/26501.htm

16:05:21 From Thomas Stockhammer (Qualcomm) to Everyone:

No Questions on 5GMS via eMBMS ;)

16:05:27 From Thomas Stockhammer (Qualcomm) to Everyone:

I am off the hook

16:37:23 From [Verizon] Jack Arky to Everyone:

@Richard. MBS User Service information could be out-of-band correct? Conveyed to Application Provider via interface to AF (AF conveys to Application). No User Service Announcement in band?

16:55:32 From [BBC] Richard Bradbury to Everyone:

Hi Jack. We have provided options in the MBS User Services specifications to convey the User Service Announcement "in band" (i.e. at reference point MBS-4-MC), but it can also be retrieved via unicast (at MBS-4-UC).

Comments


bottom of page