Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

5GMS over eMBMS #31

Open
dsilhavy opened this issue Dec 9, 2021 · 2 comments
Open

5GMS over eMBMS #31

dsilhavy opened this issue Dec 9, 2021 · 2 comments
Labels
5GMS Documentation Improvements or additions to documentation Enhancement New feature or request

Comments

@dsilhavy
Copy link
Contributor

dsilhavy commented Dec 9, 2021

Description

This ticket is supposed to hold all relevant information for 5G media streaming over eMBMS.

Related specifications

Architecture diagrams

image

@dsilhavy dsilhavy added Documentation Improvements or additions to documentation Enhancement New feature or request 5GMS labels Dec 9, 2021
@rjb1000
Copy link

rjb1000 commented Jan 14, 2022

Just to mention that @haudiobe is developing a draft CR in 3GPP SA4 that embellishes 5GMS Consumption Reporting with information about whether a 5GMS downlink streaming session is currently being served via M4d (i.e. unicast) or eMBMS (i.e. multicast/broadcast).

Latest working draft in contribution S4aI221283, but this will be revised in the coming weeks.

@rjb1000
Copy link

rjb1000 commented Jan 14, 2022

Separately (but to be documented in the same draft CR above as it develops), SA4 is debating options for conveying MBMS Reception Reporting information to the service provider in order to facilitate the application layer switching between unicast and multicast envisaged by 5G-MAG.

Here is a brief impact analysis:

Option A: Continue to use the MBMS-native Reception Reporting procedures as specified in clause 9.4 of TS 26.346

Two suboptions have been identified:

  1. MBMS reception reports are sent to the BM-SC (per TS 26.346 in Release 16), and xMB-C needs to be extended (or a new reference point defined) to expose this information to the "Service Provider" in the 5G-MAG deployment architecture.
  2. MBMS reception reports are sent to a different endpoint at the "Service Provider" instead of to the BM-SC by twiddling the URL in the Service Announcement. This suboption avoids any changes to the MBMS API in the client or xMB.

Option B: Extend the MBMS Metrics Reporting mechanism to convey MBMS Reception Reporting information over M5d

(The Metrics Reporting feature of TS 26.512 in Release 16 was designed from the outset to be extensible with multiple different reporting schemes operating simultaneously.)

In the option, the MBMS API in the client needs to be extended (or a new client-side reference point defined) to allow the MBMS Client to share the required information with the Media Session Handler in the 5GMS Client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5GMS Documentation Improvements or additions to documentation Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants