3GPP SA4 XCHANGE ‐ 27.07.2023

Agenda

1. Quick update on 5G-MAG activities.
   • Input to 3GPP Release 19 RAN and SA workshops: https://5g-mag.com/standards#membersviews
   • Input on concrete SA4 topics planned for December
   • Kick-off work on 5G Uplink Media Streaming
   • Everybody is invited to visit us at IBC https://www.5g-mag.com/post/5g-mag-ibc2023
     • 5G-MAG Meet & Greet on Saturday 16th September at 10 CEST: https://www.5g-mag.com/post/5g-mag-meetup-at-ibc-2023
     • Planning dedicated session around topics
     • Demos on 5G Media Streaming and 5G Broadcast
2. Quick update on 5G-MAG Reference Tools.
   • Update on projects: https://developer.5g-mag.com and https://github.com/orgs/5G-MAG/projects
3. Quick summary of progress on issues at SA4#124 Berlin.
4. Look ahead to issues for consideration at SA4#125 Gothenburg.
5. Discussion topics.

Issues to be covered at the session

See Kanban board for overview of open issues.

TS 26.247 - Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)

New issues targeting approval at SA#101 Bangalore

• #79 5GMSd - QoE Metrics Reporting - Inconsistency with HTTPList.

TS 26.501 - 5G Media Streaming (5GMS); General description and architecture

New issues targeting approval at SA#101 Bangalore

• #66 TS26.501 Clarification - Appropriate network entity for metrics error reports.
  • Unclear which entity the Media Session Handler send error reports to when it cannot satisfy the requirements signalled in the client metrics reporting configuration.
  • Should this error reporting feature be removed completely from TS 26.501 in Rel-16, Rel-17 and Rel-18 since an error reporting endpoint has never been specified at stage-3?

TS 26.512 - 5G Media Streaming (5GMS); Protocols

Issues resolved at SA#100 Taipei

• #59 Disambiguate Media Player Entry data types at M1 and M5
• #60 Clarification on TS 26.512 ServiceAccessInformation.networkAssistanceConfiguration.serverAddresses values
• #62 TS 26.512 Policy Template state reasons
• #64 TS 26.512: Signalling of domainNameAliases during server certificate creation

Published as TS 26.512 V17.5.0.

Discussions

• #49 Discussion Item: Signaling of DRM information via Service Access Information
• #63 Discussion: 5GMSd Network Assistance - Synergy with CTA-Wave Common Media Server Data (CMSD)
  • See discussion paper in S4aI230122.
• #72 Discussion: TS26.512 - How is consumption reporting triggered?
  • Daniel has already found some answers to the equivalent problem for QoE metrics reporting.
• #82 TS 26.512: Media streaming session identifier
  • The need for an identifier that allows UE data (of the same or different types) to be correlated after their exposure as Events.
  • New Rel-18 feature versus essential correction to Rel-17?
  • Need for stage-2 motivation in TS 26.501?

Issues previously adopted but carried over from a previous meeting cycle

• #45 Specify methods in the M6 Media Session Handling client API to invoke 5GMS network assistance
  • Maybe something in the next meeting cycle?
• #61 TS 26.512 Policy Template state change events
  • Maybe add something later in Rel-18?

Issues previously adopted and targeting endorsement at SA#101 Bangalore

• #33 Use of aspId and externalApplicationId in M1_ProvisioningSession_createProvisioningSession
  • Maybe include a clarification to TS 26.512 Rel-18 CR0036 or TS 26.512 Rel-17 CR0037?
• #42 Specify client-facing 5GMS AF host name to be used by Media Session Handler at M5
  • See TS 26.512 Rel-18 CR0036 in S4aI230104 clause 6.1A.2.

New issues targeting approval at SA#101 Bangalore

• #65 TS26.512 MetricsReportingConfiguration scheme cardinality does not match YAML definition
  • Apparent discrepancy to be confirmed by SA4 experts.
  • See TS 26.512 Rel-17 CR0037 in S4aI230105.
• #67 TS26.512 - Typo in word "Metrics" - Should be named "metrics".
  • See TS 26.512 Rel-17 CR0037 in S4aI230105 table 11.2.3.1-1, but this really needs fixing in Rel-17 too.
• #69 TS 26.512 - Handling of 3XX HTTP redirects via interface at M2d
  • See TS 26.512 Rel-17 CR0037 in S4aI230105 but this really needs fixing in Rel-16 and Rel-17 too.
• #71 TS26.512 - How to choose a address from clientConsumptionReportingConfiguration.serverAddresses array for consumption reporting
  • Historical precedent for QoE metrics reporting in TS 26.247 annex F is random selection for load balancing.
• #73 TS26.512 - Consumption reporting: How is aspId for POST URL generated?
  • See TS 26.512 Rel-17 CR0037 in S4aI230105 proposing change to API in Rel-18 to use provisioningSessionId instead of aspId.
• #74 Possible inconsistency in specification of Service Data Flow Description
  • See TS 26.512 Rel-17 CR0037 in S4aI230105.
• #78 5GMSd - QoE Metrics Reporting - Clarification on sampling rate for buffer level
  • Proposed general solution applicable to all QoE metrics (not just buffer level) is to add samplingPeriod to M1 MetricsReportingConfiguration and M5 ServiceAccessInformation.clientMetricsReportingConfiguration.
  • This would align TS 26.512 Rel-17 with Charles Lo's final TS 26.532 Rel-17 CR0003.
  • Should this change also be made to TS 26.512 Rel-16?
• #75 TS 26.512: Network Assistance recommendation and boost time windows
  • Proposal to explicitly signal the duration of the validity window of bit rate recommendations and delivery boosts using HTTP cache control response headers.
• #76 TS 26.512: NetworkAssistanceSession Request body not specified in the OpenAPI YAML for M5 createNetworkAssistanceSession operation
  • Apparent discrepancy, but original intent needs to be confirmed by SA4 experts.
• #80 5GMS AF treatment of Network Assistance Session resource
  • How should 5GMS AF behave if a QoS is requested when creating a Network Assistance Session, but no Policy Template is cited?
  • And how should it behave if both of these are included when creating a Network Assistance Session?

TS 26.517 - 5G Multicast-Broadcast User Services; Protocols and Formats

Issues resolved at SA#100 Taipei

• #52 Specify object manifest file format for MBS User Services
• #56 Specify mechanism for discovery of MBS User Service Announcement by MBS Client
  • (See below for stage-3.)

Published as TS 26.517 V17.3.0.

Issues previously adopted and targeting approval at SA#101 Bangalore

• #53 Applicability of Schedule Description metadata unit in MBS User Service Announcement is inconsistent
  • Proposed clarification included in Qualcomm TS 26.517 Rel-17 CR0001r11 in S4aI230117.
• #54 Add a figure to illustrate JSON-based syntax of MBS User Service Announcement
  • Replacement figure included in Qualcomm TS 26.517 Rel-17 CR0001r11 in S4aI230117.
• #55 Clarify population of Schedule Description metadata unit in MBS User Service Announcement
  • Wholesale redraft in next revision of TS 26.517 Rel-17 CR0001 will hopefully flush this issue out.
• #56 Specify mechanism for discovery of MBS User Service Announcement by MBS Client
  • Stage-2 procedures clarified during previous meeting cycle in TS 26.502 V17.5.0 clause 5.4 (see above).
  • Stage-3 API proposal in TS 26.517 Rel-17 CR0010 in S4aI230124.
• #57 Clarification of Byte Range Object Repair
  • Late contribution TS 26.517 Rel-17 CR0009r2 in S4-231001 has been merged into TS 26.517 Rel-17 CR0001r11 in S4aI230117

New issues targeting approval at SA#101 Bangalore

None.

Date of next meeting

Thursday, 5th October?