CR 26.517 CR#0037 – OpenAPI YAML Corrections (5MBP3)

Document: S4-260486, CR 0037 to TR 26.517 v17.9.1, Category F (correction), Rel-17

Problem: The cancelled property defined in the normative TS for ServiceScheduleDescription was missing from the OpenAPI YAML schema in Annex A.2.1, making it impossible to signal cancellation of MBS User Service Announcements.

Change: Adds the missing cancelled boolean property (with default: false) to the ServiceScheduleDescription schema object in the TS26517_MBSUserServiceAnnouncement.yaml OpenAPI definition.

Affected clause: A.2.1 (MBS User Service Announcement schema)

Impact: Without this fix, implementations cannot use the OpenAPI-generated code/schema to cancel MBS User Service Announcements, breaking a normatively specified feature.

No other specs affected (test specs, O&M, other core specs marked not affected).

CR 26.517 CR#0038 – OpenAPI YAML Corrections (5MBP3)

Source: BBC | Meeting: SA4#135bis-e | Category: A (mirror) | Release: Rel-18

Summary

• Problem: The cancelled property defined in the normative TS 26.517 specification for ServiceScheduleDescription was missing from the OpenAPI YAML schema in Annex A.2.1 (TS26517_MBSUserServiceAnnouncement.yaml).
• Impact: Without this property, cancellation of MBS User Service Announcements is not possible via the API.
• Fix: Adds the missing cancelled boolean property (default: false) to the ServiceScheduleDescription schema object in the YAML.
• Additional housekeeping: Copyright year updated (2024→2026), spec version reference updated in externalDocs (V18.3→V18.6.0), and YAML version field bumped to 2.1.01.
• Affected clause: A.2.1 of TR 26.517 (MBS User Service Announcement schema).
• No other specs affected (test specs, O&M, other core specs not impacted).

CR Summary: 3GPP TR 26.517 CR#0039 – OpenAPI YAML Corrections

Document: S4-260488, CR 0039, Category A (mirror correction), Rel-19, v19.1.0 Source: BBC | WI: 5MBP3

What is being changed and why

• A cancelled property defined in the normative TS text for ServiceScheduleDescription was missing from the OpenAPI YAML in Annex A.2.1 of TR 26.517.
• Without this fix, cancellation of MBS User Service Announcements is not implementable via the API.
• Tracked issue: https://github.com/5G-MAG/Standards/issues/200

Technical Details

• Affected spec/clause: TR 26.517, Annex A.2.1 (TS26517_MBSUserServiceAnnouncement.yaml)
• Schema modified: ServiceScheduleDescription
• Change: Adds the missing cancelled property: yaml cancelled: type: boolean default: false
• Minor version bump in the YAML info block (2.2.1 → 2.2.2, copyright year updated).
• No other schemas or procedures are affected.

Consequence if Not Approved

MBS User Service Announcement cancellation cannot be signalled via the OpenAPI interface, breaking a normatively specified feature.

CR 26.502 CR0049r2 – [5MBUSA] User Service Announcement Parameters Alignment and Clarifications

Source: BBC | Work Item: 5MBUSA | Category: F (Correction) | Release: Rel-17 | Spec: TS 26.502 v17.11.0

Background / Motivation

During 5G-MAG reference implementation of MBS User Services, multiple gaps and ambiguities were identified between the stage 2 definition (TS 26.502) and the stage 3 specification (TS 26.517). This CR corrects TS 26.502 to align with TS 26.517 and resolve implementation issues.

Changes Made (6 items)

1. Conformance Profiles – New parameter added to MBS Distribution Session (table 4.5.6-1) and MBS Distribution Session Announcement (table 4.5.8-1), assigned by the MBS Application Provider, referencing profiles defined in clause 12.

2. Transport Security Protection – Clarified that the flag is provisioned by the MBS Application Provider or (for the User Service Announcement Channel) by the MBSF. Assigner column in table 4.5.6-1 updated accordingly.

3. Object Acquisition Identifiers – MIME Type – Each identifier may now be accompanied by a content type; this is mandatory when the identifier is an Application Service Entry Point locator. MBSTF shall verify content type on ingest. Impacts tables 4.5.6-2 and 4.5.8-2.

4. Object Repair Back-off Parameters – New parameter defined in both MBS Distribution Session (table 4.5.6-2) and MBS Distribution Session Announcement (table 4.5.8-2), assigned by the MBSF. Clarified that Object Repair is enabled at MBSF discretion (not provisioned by MBS Application Provider); wording changed from "provisioned" to "enabled" throughout clauses 4.2.6 and 4.5.6.

5. New Reference Point MBS-1 – Formally defined in clause 4.4.1: exposure of composite User Service Announcement from MBSF to MBS Application Provider for private advertisement via MBS-8. Referenced in procedures (clauses 5.2 and 5.4).

6. User Service Advertisement Notification – Clarified in table 4.6.2-1 and clause 5.4 that the "User Service advertisement" event includes a URL for the MBS Application Provider to retrieve the full User Service Announcement bundle (not just partial information) via reference point MBS-1 when external delivery mode is indicated.

Affected Clauses

4.2.2, 4.2.6, 4.3.1, 4.3.2, 4.4.1, 4.5.2, 4.5.6, 4.5.8, 4.6.2, 5.2, 5.4, 6.1

Related Specs

TS 26.580, TS 26.581; potential impact on TS 29.580 (Nmb10/Nmb5, CT3) and TS 29.581 (Nmb2, CT4) for items 1–3 and 5–6.

Consequence if Not Approved

Stage 2/stage 3 misalignment for MBS User Services, blocking correct reference implementation.

CR Summary: TR 26.502 CR 0050 – MBS User Service Announcement Parameter Alignment (Rel-18)

Source: BBC | Work Item: 5MBUSA | Category: A (mirror to earlier release) | Affected spec: TS 26.502 v18.5.0

Purpose

Addresses gaps and ambiguities found during 5G-MAG reference implementation of MBS User Services, where stage 3 (TS 26.517) was correct but stage 2 (TS 26.502) lacked corresponding definitions or was unclear.

Key Changes

• Conformance profiles (Change #1): Added as a new parameter (cardinality 0..*) in the MBS Distribution Session entity (Table 4.5.6-1), assigned by the MBS Application Provider. Also added to MBS Distribution Session Announcement (Table 4.5.8-1).

• Transport security protection (Change #2): Clarified in Table 4.5.6-1 that this flag is assigned by either the MBS Application Provider or the MBSF (the latter for the User Service Announcement Channel special case). Assigner column updated accordingly.

• Object acquisition identifiers – MIME type (Change #3): Clarified in Table 4.5.6-2 that each identifier may be accompanied by a content type, and that this content type shall be present when the identifier is an Application Service Entry Point locator. Reflected in Table 4.5.8-2 (Application Service Entry Point locators always paired with MIME type).

• Object repair back-off parameters (Change #4): Added as a new parameter (0..1, assigned by MBSF) in both Table 4.5.6-2 and Table 4.5.8-2. Clarified throughout (clauses 4.2.6, 4.5.6, 4.5.8) that Object Repair is enabled by the MBSF (not provisioned by the MBS Application Provider). Object repair base URL description updated to use "enabled" instead of "provisioned."

• New reference point MBS-1 (Change #5): Formally defined in clause 4.4.1 as the interface for the MBS Application Provider to retrieve User Service Announcement bundles from the MBSF for private advertisement via MBS-8. Referenced in clauses 4.3.2, 5.2, and 5.4.

• User Service Announcement bundle clarification (Change #6): Clause 5.4 (procedure C) updated to clarify that the full User Service Announcement exposed via the User Service advertisement notification and retrievable at MBS-1 is the User Service Announcement bundle (replacing "composite").

Impact

• Affects reference points Nmb10/Nmb5 (TS 29.580, CT3) and Nmb2 (TS 29.581, CT4) for changes #1–#3 and #5–#6.
• Changes #4 (back-off parameters) have no CT impact.
• Related specs: TS 26.580, TS 26.581.
• If not approved: Stage 2/stage 3 misalignment persists for MBS User Services implementation.

CR Summary: TR 26.502 CR 0051 – MBS User Service Announcement Parameter Alignment (Rel-19, Cat A)

Source: BBC | WI: 5MBUSA | Affected spec: TS 26.502 (stage 2); mirrors changes in TS 26.580/26.581

Problem

During 5G-MAG reference implementation of MBS User Services, multiple gaps and ambiguities were found between stage 2 (TS 26.502) and stage 3 (TS 26.517) definitions for User Service Announcement parameters.

Changes Made

• Conformance profiles (table 4.5.6-1 & 4.5.8-1): Added as a new parameter (0..*) assigned by the MBS Application Provider, referencing clause 12 profiles. Impacts Nmb10/Nmb5 (CT3).

• Transport security protection (table 4.5.6-1): Clarified that this flag is set by the MBS Application Provider or the MBSF (in the special case of the User Service Announcement Channel). Impacts Nmb10/Nmb5 and Nmb2.

• Object acquisition identifiers (table 4.5.6-2): Added optional MIME content type per identifier; made mandatory when the identifier is an Application Service Entry Point locator. Impacts Nmb10/Nmb5 and Nmb2.

• Object repair back-off parameters (tables 4.5.6-2 & 4.5.8-2): Defined new parameters (0..2) for in-session and post-session repair scheduling (offset time + random time period). Clarified that Object Repair is enabled by the MBSF, not provisioned by the MBS Application Provider (clause 4.2.6 updated accordingly). No CT impact.

• New reference point MBS-1 (clauses 4.3.2, 4.4.1, 5.2, 5.4): Formally defined as the interface by which the MBS Application Provider retrieves User Service Announcement bundles from the MBSF for private re-advertisement via MBS-8. Impacts Nmb10/Nmb5.

• User Service advertisement notification (clause 4.6.2, table 4.6.2-1 & clause 5.4): Clarified that the full User Service Announcement exposed in the "User Service advertisement" event notification is the User Service Announcement bundle, and that the notification includes a URL for the MBS Application Provider to retrieve it via MBS-1. Terminology updated from "composite" to "full" where appropriate.

Consequence if Not Approved

Stage 2/stage 3 misalignment for MBS User Services remains, blocking correct implementation.

CR Summary: S4-260504 — Update ETSI TS 103 973 Reference in TS 26.512

Spec affected: 3GPP TS 26.512 (Release 19, v19.2.0) Work Item: AMD_PRO-MED Category: F (Correction) Source: Dolby Laboratories Inc.

What is being changed and why

• A single editorial/reference correction in Clause 2 (References) of TS 26.512.
• Reference [77] currently cites ETSI TS 103 973 V1.1.3 (Stable Draft) — the "Coded Multisource Media Format (CMMF) for Content Distribution and Delivery."
• The CR removes the version qualifier "V1.1.3 (Stable Draft)" to align with the latest published version of the ETSI standard.

Key Detail

• The change is minimal: stripping the explicit version string from the normative reference so it points to the current published ETSI TS 103 973 rather than a specific stable draft snapshot.
• No functional or procedural changes to any 3GPP feature or procedure.

Rationale

• Leaving the stale draft version reference risks interoperability issues or incorrect/incomplete normative references in implementations.