-
Notifications
You must be signed in to change notification settings - Fork 4
3GPP SA4 XCHANGE ‐ 26.10.2023
Richard Bradbury edited this page Oct 26, 2023
·
8 revisions
- Quick update on 5G-MAG activities and 5G-MAG Reference Tools
- Quick summary of progress on issues at SA4#125 Gothenburg.
- Discussion topics.
See Kanban board for overview of open issues.
-
#79 5GMSd - QoE Metrics Reporting - Inconsistency with
HTTPList.
Published as TS 26.247 V16.8.1 and V17.4.1.
None.
None.
- #87 3GPP TS 26.346 - Wrong RFC referenced for "Compact No-Code" FEC
- #66 TS26.501 Clarification - Appropriate network entity for metrics error reports.
- #75 Confusion over "nominal time period" validity for Network Assistance throughput estimations and delivery boosts
Published as TS 26.501 V16.12.0, V17.7.0 and 18.3.1.
None.
- #65 TS26.512 MetricsReportingConfiguration scheme cardinality does not match YAML definition
- #67 TS26.512 - Typo in word "Metrics" - Should be named "metrics".
- #68 TS26.512 - Clarification on the client behavior for the list of metrics which shall be reported
- #69 TS 26.512 - Handling of 3XX HTTP redirects via interface at M2d
- #71 TS26.512 - How to choose a address from clientConsumptionReportingConfiguration.serverAddresses array for consumption reporting
- #73 TS26.512 - Consumption reporting: How is aspId for POST URL generated?- #74 Possible inconsistency in specification of Service Data Flow Description
- #76 TS 26.512: NetworkAssistanceSession Request body not specified in the OpenAPI YAML for M5 createNetworkAssistanceSession operation
- #78 5GMSd - QoE Metrics Reporting - Clarification on sampling rate for buffer level
- #80 5GMS AF treatment of Network Assistance Session resource
- #81 TS 26.512: Clarification on use of optional properties in NetworkAssistanceSession
Published as TS 26.512 V16.11.0 and V17.6.0.
#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.
-
#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 in Rel-18?
-
#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?
-
#42 Specify client-facing 5GMS AF host name to be used by Media Session Handler at M5
- See TS 26.512 Rel-18 CR0036r2 in S4aI230150 clause 6.1A.2.
- (This change will probably end up in the new TS 26.510 document.)
- #89 TS 26.512 - Make externalReference and applicationSessionContext optional properties of PolicyTemplate resource
- #90 5GMSd - Consumption Reporting - Clarification on duration property
-
#91 Clarification of ConsumptionReportingUnit.mediaEndpointAddress ambiguity
- Discussion on the value of reporting endpoint address of both ends of reference point M4.
-
#97 TS 26.512 - Value of mediaPlayerEntry and mediaConsumed in Definition of ConsumptionReport format
- Discussion on virtues of explicitly specifying population of consumption reports for HLS-based media streaming sessions.
See TS 26.512 Rel-17 CR0054 in S4aI230145.
-
#86 TS 26.512: Fix inconsistent name of client metrics reporting configuration property in Service Access Information
- Corrected simple typo in YAML.
-
#88 TS 26.512 - Use of Read-only mandatory fields in PolicyTemplate resource
- Piloted use of readOnly YAML directive.
- #93 M5 Service Access Information - Inconsistency with ConsumptionReportingConfiguration.accessReporting
-
#94 Inadvisable use of response code 422 (Unprocessable Entity) by 5GMS AF at reference point M1
- Replaced with different HTTP response codes.
-
#95 Unclear binding between externalReference and Policy Template identifier in M5 Service Access Information
- Introduced new policyTemplateBindings array to explicitly bind an external reference to a Policy Template identifier.
-
#96 TS 26.512: M1 ConsumptionReportingConfiguration.reportingInterval value range not present in the OpenAPI YAML
- Updated YAML to specify reportingInterval > 0.
-
#33 Use of aspId and externalApplicationId in M1_ProvisioningSession_createProvisioningSession
- Renamed externalApplicaitonId to appId and clarified need for NEF to map external Application Identifier to internal Application Identifier.
-
#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.
- Stage-3 API proposal in TS 26.517 Rel-17 CR0010r3 in SP-230916 approved.
Published in TS 26.517 V17.4.0.
Most issues are being dealt with (at low priority) in TS 26.517 Rel-17 CR0001.
-
#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
- Still not tackled.
- Wholesale redraft in next revision of TS 26.517 Rel-17 CR0001 will hopefully flush this issue out.
-
#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
None.
December 2023?