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

TS26.501 Clarification - Appropriate network entity for metrics error reports #66

Closed
dsilhavy opened this issue Jun 5, 2023 · 8 comments
Assignees
Labels
3GPP Rel-16 Issues relating to 3GPP Release 16 specifications. 3GPP Rel-17 Issues relating to 3GPP Release 17 specifications. 3GPP Rel-18 Issues relating to 3GPP Release 18 specifications. 3GPP TS 26.501 Issues relating to SA4's "5G Media Streaming (5GMS); General description and architecture" spec 5GMS Metrics Reporting Adopted Clarification

Comments

@dsilhavy
Copy link
Contributor

dsilhavy commented Jun 5, 2023

Problem description

TS26.501 V17.5.0 clause 5.5.3 defines the required steps for AF-based metrics reporting. Step 8 of this procedure is defined as follows:

The Media Player acknowledges its support for the collection of the required metrics of all configured schemes. If the request cannot be supported by the Media Player (e.g., inability to measure metrics according to one of the configured schemes), an error message shall be sent by the Media Session Handler to the appropriate network entity, indicating that metrics reporting for the indicated metrics scheme cannot be supported for this streaming service.

For me, it is not apparent what is meant by appropriate network entity. I assume the error report should be send to the list of 5GMS AF defined in the ServiceAccessInformation.clientMetricsReportingConfigurations.serverAddresses property?

Suggested solution

It would be great if we can clarify what is meant by the above described statement. I might have missed something here. Moreover, during the 5G-MAG SA4 developers call the question popped up if this error report needs to be send at all.

Related issues

@dsilhavy dsilhavy added Clarification 3GPP Rel-17 Issues relating to 3GPP Release 17 specifications. labels Jun 5, 2023
@dsilhavy dsilhavy added this to the 3GPP SA4#125→SA#101 milestone Jun 5, 2023
@dsilhavy dsilhavy added the 3GPP TS 26.501 Issues relating to SA4's "5G Media Streaming (5GMS); General description and architecture" spec label Jun 5, 2023
@rjb1000 rjb1000 added 3GPP Rel-16 Issues relating to 3GPP Release 16 specifications. 3GPP Rel-18 Issues relating to 3GPP Release 18 specifications. labels Jun 5, 2023
@rjb1000
Copy link
Contributor

rjb1000 commented Jun 5, 2023

Looks like an inconsistency between this stage-2 specification in TS 26.501 and the stage-3 APIs specified in TS 26.512 where no endpoint is specified on the 5GMS AF for error reporting by the Media Session Handler.

Suggest we discuss with the SA4 experts to get their take on this.

What is the purpose of reporting an error if the configured metics reporting scheme cannot be supported by a Media Session Handler? There's not much that can be done about it, but maybe it's just good to know why no metrics reporting is happening?

Any early thoughts, @gheikkila, @haudiobe, @tlohmar?

@gheikkila
Copy link

gheikkila commented Jun 5, 2023

In the last version (17.4.0) of 26.512 we did add some error reporting. I think the general idea of reporting errors is to at least allow some way for the configuring entity to get a feedback if the configuration isn't ok. Otherwise the MSH would just swallow it silently, and debugging on OAM level would be very difficult.

image

@rjb1000
Copy link
Contributor

rjb1000 commented Jun 5, 2023

In the last version (17.4.0) of 26.512 we did add some error reporting. I think the general idea of reporting errors is to at least allow some way for the configuring entity to get a feedback if the configuration isn't ok. Otherwise the MSH would just swallow it silently, and debugging on OAM level would be very difficult.

Thanks for the memory jog, @gheikkila. Yes, you're right that we added the ERROR_METRICS_REPORTING error event to the M6 client API. Looking at figure 12.2.1-1, I think this is intended to be used by the Media Session Handler to notify the 5GMS-Aware Application that an attempt to send a metrics report has failed (e.g. because the server was unresponsive and the HTTP transaction timed out).

The error condition envisaged by the text cited from TS 26.501 clause 5.5.3 by @dsilhavy appears to be more to do with the Media Session Handler reporting an error to "the appropriate network entity" (which I read as "5GMSd AF") when the Media Player doesn't support one of the metrics reporting schemes mentioned in the client metrics reporting configuration of the Service Access Information.

There's definitely a big hole in TS 26.512 at reference point M5 in this regard: no way to report the error to the 5GMSd AF.

The key question for SA4 is whether we want to fill the gap in TS 26.512 or just remove the requirement from TS 26.501.

@rjb1000
Copy link
Contributor

rjb1000 commented Jul 27, 2023

@fredericgabin: I will remove this from TS 26.501 to align stage-2 to stage-3.

@rjb1000
Copy link
Contributor

rjb1000 commented Aug 29, 2023

CR contributed to SA4#125 by @fredericgabin:

  • TS 26.501:
    • Rel-16: Not contributed.
    • Rel-17: CR0072 "CR to 26.501-0072 on Stage 2 alignment (Rel-17)" in S4-231132.
    • Rel-18: Not contributed.

@rjb1000
Copy link
Contributor

rjb1000 commented Aug 29, 2023

CR merged with Nokia/BBC CRs and agreed at SA4#125:

  • TS 26.501
    • Rel-16: CR0076r2 "Clarifications to Network Assistance feature" in S4-231515.
    • Rel-17: CR0075r3 "Clarifications to Network Assistance feature" in S4-231568.
    • Rel-18: CR0066r5 "Clarifications to Network Assistance feature" in S4-231578.

@rjb1000
Copy link
Contributor

rjb1000 commented Sep 21, 2023

CR Packs approved at SA#101:

  • TS 26.501
    • Rel-16: CR0076r2 "Clarifications to Network Assistance feature" in SP-230914.
    • Rel-17: CR0075r3 "Clarifications to Network Assistance feature" in SP-230914 (mirror of CR0076r2).
    • Rel-18: CR0066r5 "Clarifications to Network Assistance feature" in SP-230919 (not an exact mirror CR).

@rjb1000
Copy link
Contributor

rjb1000 commented Oct 18, 2023

Approved changes published and available for download:

@rjb1000 rjb1000 closed this as completed Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3GPP Rel-16 Issues relating to 3GPP Release 16 specifications. 3GPP Rel-17 Issues relating to 3GPP Release 17 specifications. 3GPP Rel-18 Issues relating to 3GPP Release 18 specifications. 3GPP TS 26.501 Issues relating to SA4's "5G Media Streaming (5GMS); General description and architecture" spec 5GMS Metrics Reporting Adopted Clarification
Projects
Development

No branches or pull requests

6 participants