Feedback to 3GPP
XCHANGE 09/01/2025 - Status of standards tickets by end 2024
Issues that should have been resolved earlier in the year
| [#] | Title | Assignees | Status | Labels | Milestone |
|---|---|---|---|---|---|
| #122 | QoE Metrics Reporting: M1 Provisioning - reportingInterval shall be greater than zero | rjb1000 | Published | 3GPP Rel-16, 3GPP Rel-17, 3GPP Rel-18, 3GPP TS 26.510, 3GPP TS 26.512, 5GMS Metrics Reporting, Improvement | |
| #123 | QoE Metrics Reporting - M1 Provisioning - samplingPeriod can be negative | rjb1000 | Published | 3GPP Rel-16, 3GPP Rel-17, 3GPP Rel-18, 3GPP TS 26.510, 3GPP TS 26.512, 5GMS Metrics Reporting, Improvement |
Issues with CRs approved at SA#106 (Madrid) December 2024
MCC has very recently implemented these CRs, targeting publication of new specifications by mid January. Drafts not checked yet.
| [#] | Title | Assignees | Status | Labels | Milestone |
|---|---|---|---|---|---|
| #106 | TS 26.512: Discrepancy between tables and YAML for properties marked as read-only | rjb1000, tlohmar | Approved for publication by Technical Body | 3GPP Rel-16, 3GPP Rel-17, 3GPP TS 26.512, 5GMS Content Hosting, 5GMS Dynamic Policies, 5GMS Edge Applications, 5GMS Metrics Reporting, 5GMS Network Assistance, Adopted, Improvement | 3GPP SA4#130→SA#106 |
| #146 | TS 26.512 V17.9.0: Discrepancies between normative tables and OpenAPI YAML | rjb1000 | Approved for publication by Technical Body 3GPP Rel-17, 3GPP TS 26.512, 5GMS Consumption Reporting, 5GMS Content Hosting, 5GMS Dynamic Policies, 5GMS Edge Applications, 5GMS Event | Exposure, 5GMS Metrics Reporting, 5GMS Service Access/Launch, Correction | 3GPP SA4#130→SA#106 |
| #149 | TS 26.510: Gaps identified in support for Background Data Transfer at reference point M6 | haudiobe, ibouazizi, rjb1000, tlohmar | Approved for publication by Technical Body | 3GPP Rel-18, 3GPP TS 26.501, 3GPP TS 26.510, 5GMS Dynamic Policies | 3GPP SA4#130→SA#106 |
| #148 | TS 26.512: Gaps identified in support for Background Data Transfer at reference point M7 | rjb1000 | Approved for publication by Technical Body | 3GPP Rel-18, 3GPP TS 26.512, 5GMS Dynamic Policies | 3GPP SA4#130→SA#106 |
New issues adopted in current meeting cycle
A CR has been drafted for the following new issue, and was endorsed by the SA4 MBS ad hoc meeting on 8th Jan.
| [#] | Title | Assignees | Status | Labels | Milestone |
|---|---|---|---|---|---|
| #120 | TS 26.346 FLUTE FDT Profile for 5MBS & delimiter usage | chburdinat, haudiobe, jordijoangimenez, rjb1000, tlohmar | Change contribution drafting | 3GPP Rel-17, 3GPP Rel-18, 3GPP TS 26.346, Doubt | 3GPP SA4#131→SA#107 |
Adopted issues that nobody is actively working on right now
| [#] | Title | Assignees | Status | Labels | Milestone |
|---|---|---|---|---|---|
| #104 | TS26.512: M1 Policy Template Provisioning - Return codes for error handling of put operation | rjb1000 | Adopted | 3GPP Rel-16, 3GPP Rel-17, 3GPP TS 26.512, 5GMS Dynamic Policies, Adopted, Improvement | 3GPP SA4#131→SA#107 |
| #106 | TS 29.571: regex pattern allows all non-empty strings and will not apply restrictions as intended | haudiobe, ibouazizi, jordijoangimenez, rjb1000, tlohmar, zooksy | Adopted | 3GPP Rel-17, 3GPP TS 29.571, Adopted, Correction, Improvement | |
| #35 | ProvisioningSession resource returned by 5GMS AF at M1 does not include information about all its subresources | fredericgabin, haudiobe, jordijoangimenez, rjb1000, tlohmar | Adopted | 3GPP Rel-16, 3GPP Rel-17, 3GPP TS 26.512, Adopted, Improvement | 3GPP SA4#127→SA#103 |
| #61 | TS 26.512 Policy Template state change events | fredericgabin, rjb1000, tlohmar | Adopted | 3GPP Rel-18, 3GPP TS 26.510, 5GMS Dynamic Policies, Adopted, Improvement | 3GPP SA4#127→SA#103 |
Unadopted issues
[#] | Title | Assignees | Status | Labels | Milestone – | – | – | – | – | – #49|Discussion Item: Signaling of DRM information via ServiceAccessInformation | dsilhavy, haudiobe | Pre-Acceptance 3GPP Rel-19, 3GPP TS 26.512, 5GMS Service Access/Launch, Discussion, New Feature | 3GPP SA4#127→SA#103 #63|Discussion: 5GMSd Network Assistance - Synergy with CTA-Wave Common Media Server Data (CMSD) | fredericgabin, haudiobe, rjb1000, tlohmar | Pre-Acceptance | 3GPP Rel-19, 3GPP TS 26.510, 3GPP TS 26.512, 5GMS Metrics Reporting, 5GMS Network Assistance, Discussion | 3GPP SA4#127→SA#103 #103|TS 26.512: Add missing filterType parameter to ServiceDataFlowDescription | jordijoangimenez | Pre-Acceptance | 3GPP Rel-16, 3GPP Rel-17, 3GPP Rel-18, 3GPP TS 26.510, 3GPP TS 26.512, 5GMS Dynamic Policies, 5GMS Network Assistance, Improvement | 3GPP SA4#130→SA#106 #118|FAR Apply Action “FSSM” in PFCP Session Establishment for MBS |Borjis131, jordijoangimenez | Pre-Acceptance | 3GPP Rel-17, 3GPP TS 29.244, Doubt, MBS Broadcast| #124|Identical EARFCN assignment for E-UTRA bands 106 and 107 | jordijoangimenez | Pre-Acceptance | 3GPP Rel-18, 3GPP TS 36.101, Clarification #126|Common start of the first MCCH modification period | jordijoangimenez | Pre-Acceptance | 3GPP TS 36.300, Clarification
XCHANGE 10/10/2024
Resolution of issues found in 3GPP technical specifications
5G-MAG has been collecting feedback on 3GPP specifications since our last XCHANGE with 3GPP SA4. The issues raised by developers are in GitHub: Kanban · Specifications - 3GPP - Feedback (github.com).
| [#] | Title | 3GPP TS impacted | TDoc # |
|---|---|---|---|
| #104 | TS26.512: M1 Policy Template Provisioning - Return codes for error handling of put operation | TS 26.512 Rel-17 | - |
| #146 | TS 26.512 V17.9.0: Discrepancies between normative tables and OpenAPI YAML | TS 26.512 Rel-17 | S4aI240116 |
| #141 | Lack of support for preselecting a Service Operation Point | TS 26.510 Rel-18 TS 26.512 Rel-18 | S4aI240133 |
| #148 | Gaps identified in support for Background Data Transfer at reference point M6 | TS 26.512 Rel-18 | S4aI240146 |
| #149 | Gaps identified in support for Background Data Transfer at reference point M7 | TS 26.512 Rel-18 | S4aI240147 |
Note that:
- The content of TS 26.512 Rel-17 CR0080 [S4aI240116] (issue #146) was agreed in the SA4 MBS ad hoc meeting preceding SA4#130.
- Stage-2 fixes for issue #141 were agreed at the SA4#129e meeting and approved for publication at SA#105; for stage-3, TS 26.512 Rel-18 CR0081 is to be looked at by the present SA4 MBS meeting.
- Issues #148 and #149 are raised in the context of the feasibility analysis and usage guidelines for the deployment of Uplink 5G Media Steaming (5GMSu) and RTC architectures (as mentioned above) and as described by the Discussion Paper S4aI240135.
XCHANGE 07/03/2024
Adopted TS 26.512 issues
| [#] | Milestone |
|---|---|
| #119 | 3GPP SA4#127-e-bis→SA#104 |
| #102 | 3GPP SA4#128→SA#104 |
| #104 | Milestone 3GPP SA4#128→SA#104 |
Adopted TS 26.532 issue
[#] | Milestone – | – #110 | 3GPP SA4#128→SA#104 #111 | 3GPP SA4#127-e-bis→SA#104 #112 | 3GPP SA4#127-e-bis→SA#104 #113 | 3GPP SA4#127-e-bis→SA#104 #115 | 3GPP SA4#127-e-bis→SA#104 #116 | 3GPP SA4#127-e-bis→SA#104 #117 | 3GPP SA4#127-e-bis→SA#104
Adopted TS 29.571 issues
[#] | Milestone – | – #106 | 3GPP SA4#127-e-bis→SA#104