Extracted Proposals

This document does not contain any explicitly marked proposals in the standard 3GPP format (e.g., "Proposal X:", "Proposal:", etc.).

The document is a Change Request (CR) for TR 26.804 that adds technical content related to latency measurement and control (WT#6), but it does not include a "Conclusions" section or any text explicitly labeled as "Proposal" in any of the recognized formats.

Proposals

(No proposals found in this document)

Note: This document does not contain any explicit proposals. The document is a Change Request (CR) for TR 26.804 that adds new clauses related to "5G System-independent media streaming" as part of Work Topic #5 (WT#5). While it contains technical content describing features, architectures, and dependencies, there are no sections explicitly marked as "Proposal", "Proposal X:", "Proposal X.", etc. The document includes editor's notes and technical analysis but no formal proposals in the standard 3GPP proposal format.

Extracted Proposals

Based on my analysis of the document, I could not find any proposals explicitly marked with the standard formats: - "Proposal X: " - "Proposal X. " - "Proposal: " - "Proposal. " - "Proposal "

The document is a Change Request (CR) for 3GPP TS 26.804 concerning Common Client Metadata phase 2 (CMCD). While it contains extensive technical content including architecture mappings, call flows, gap analyses, candidate solutions, and conclusions, none of these sections contain text explicitly labeled as "Proposal" in any of the standard formats.

The document does contain a "Summary and conclusions" section in clause 5.16.7 with recommendations, but these are not formatted as formal proposals.

Result: This document does not contain any formally marked proposals.

Extracted Technical Proposals

This document does not contain any explicit proposals marked as "Proposal X:", "Proposal X.", "Proposal:", "Proposal.", or "Proposal ".

The document is a Change Request (CR) that proposes modifications to technical specification 26.804, but it does not contain formally marked proposals in the standard 3GPP proposal format. Instead, it contains technical changes to various clauses of the specification regarding SCONE (Standard Communication with Network Elements) protocol integration.

Extracted Proposals

Based on my review of the document, I could not find any explicitly marked proposals in the standard 3GPP proposal format (e.g., "Proposal X:", "Proposal:", "Proposal X.", etc.).

The document contains technical content describing rate limits in 5G Media Streaming, including descriptions, architecture mappings, call flows, gap analysis, and candidate solutions. However, there is no "Conclusions" section or any section that explicitly lists proposals using the standard proposal formatting conventions.

The document appears to be a Change Request (CR) that modifies clauses 5.25 and its subclauses in TR 26.804, but it does not contain formal proposals as typically found in 3GPP contribution documents.

Extracted Proposals

Based on my review of the document, I could not find any explicit proposals marked with the standard formats such as: - "Proposal X: " - "Proposal X. " - "Proposal: " - "Proposal. " - "Proposal "

The document appears to be a Change Request (CR) for 3GPP TS 26.802 that introduces technical content related to Combined Unicast-Multicast-Broadcast functionality (WT#4), but it does not contain a "Conclusions" section or any explicitly marked proposals within the body text.

The document contains recommendations in section 8.5, but these are labeled as "Recommendations" rather than "Proposals."

Conclusion: This document does not contain any explicitly marked proposals.

Extracted Proposals

This document does not contain any proposals. The document is a Change Request (CR) that proposes modifications to technical specification TR 26.804, but it does not include any sections explicitly marked as "Proposal", "Proposal:", "Proposal X:", "Proposal X.", etc.

The document contains a "Reason for change" and "Summary of change" sections that describe the purpose and content of the CR, but these are not formatted as formal proposals as defined in the extraction criteria.

Extracted Technical Proposals

Based on my analysis of the document, there are no explicit proposals in this 3GPP contribution.

The document contains recommendations in sections 5.18.7 and 6.18, but these are labeled as "It is recommended that:" rather than being formatted as formal proposals (e.g., "Proposal 1:", "Proposal:", etc.).

The document is a pseudo-CR (pCR) that proposes changes to TR 26.804, but it does not contain any sections explicitly marked as "Proposal" in any of the standard formats you specified.

Extracted Proposals

Based on my analysis of the document, there are no explicit proposals in this 3GPP document.

The document is a Change Request (CR) for TR 26.804 that adds technical content related to network assistance for multi-access media delivery. While it contains sections titled "Summary and Conclusions" (clause 5.18.7), these sections do not contain any text explicitly marked as "Proposal" in any of the formats specified (numbered or unnumbered, with colon, period, hyphen, etc.).

The document does contain: - Recommendations (numbered 1, 2, 3 in clause 5.18.7) - A "Summary of change" field in the CR header - Technical descriptions and candidate solutions

However, none of these are formatted or labeled as formal "Proposals" as typically found in 3GPP contributions.

Proposal 1: The use cases and collaboration scenarios for network slicing documented in clauses 5.3 and 5.4 respectively be included in an informative annex to TS 26.501 [20].

Proposal 2: The changes to the PolicyTemplate resource data model definition described in clause 6.1.2.1 be implemented in TS 26.510 [42] to support Policy Template provisioning for a plurality of Network Slices and/or Data Networks, and the corresponding alignment changes described in clause 6.1.3 be implemented in TS 26.501 [20].

Proposal 3: The Key Issue description and corresponding candidate solution on bootstrapping application invocation on a Network Slice documented in clause 6.7 of the present document be included as an informative clause or annex to TS 26.501 [20] as guidance for implementations.

Proposal 4: To support the procedure for AF-requested modification of Network Slice(s) for a UE, the following are adopted into media delivery specifications as described in clause 6.X.3 of the present document:

a. In stage-2 specification TS 26.501 [20], update of domain model for dynamic policies to illustrate provisioning of Alternate S-NSSAI, and the procedures for Dynamic Policy based on Network Slicing, for both downlink and uplink streaming

b. In state-3 specification TS 26.512 [21], add procedure descriptions for M6d and M6u for the 5GMSd/5GMSu Aware Application requesting the Media Session Handler for change of traffic treatment

c. In stage-3 specification TS 26.510 [42], update the PolicyTemplate and DynamicPolicy resource data models, and the Dynamic Policy provisioning and invocation interactions to enable AF-requested modification of Network Slice(s) of a UE

Extracted Technical Proposals

Based on my analysis of the provided 3GPP document (S4-260282), I could not find any explicitly marked proposals in the standard proposal formats you specified (e.g., "Proposal X:", "Proposal:", "Proposal X.", etc.).

The document is a Change Request (CR) for TS 26.804 that proposes modifications to the specification regarding multi-access media delivery and QoS mapping procedures. While it contains technical content describing gaps and new procedures (particularly the Non-3GPP QoS mapping procedure in section 5.18.X.X), these are presented as specification text changes rather than as explicitly labeled "Proposals."

The document does contain: - A "Reason for change" section - A "Summary of change" section - Technical procedure descriptions

However, none of these are formatted as formal proposals using the terminology and formats you specified.

No formal proposals were found in this document.