Proposal 1: Capture the Media Application Service model in the Technical Report.

Proposal 2: Capture the 5GMS Application Service model in the Technical Report.

Proposal 3: Capture the RTC Application Service model in the Technical Report.

Extracted Proposals

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

The document is a Change Request (CR) that proposes adding a new Candidate Solution (#n) regarding "Application Server Energy Information" to TR 26.942. While the document contains technical content describing the candidate solution, including functional descriptions, architecture mappings, and proposed normative requirements, none of this content is explicitly formatted or labeled as a "Proposal" in the conventional 3GPP sense.

The document structure includes sections like "Reason for change," "Summary of change," and detailed technical specifications, but these are part of the CR format rather than standalone proposals that would typically appear in a discussion paper or contribution with a "Conclusions" section listing proposals.

Extracted Proposals

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

The document is a Change Request (CR) for TR 26.942 that introduces new clauses about energy-aware streaming, including Key Issue #7 and Solution #X. While it contains technical content and recommendations, these are not formatted as formal "Proposal" statements.

The document does contain a "Summary" section at the end (clause 7.X.4) that discusses progression of efforts and what is "proposed to progress," but this is written as narrative text rather than as formally numbered or labeled proposals.

Extracted Technical Proposals

Based on my analysis of the provided 3GPP document (S4-260053), I could not find any explicitly marked proposals in the document text.

The document is a Change Request (CR) for TR 26.804 related to Common server- and network-assisted streaming, but it does not contain sections explicitly labeled as "Proposal 1:", "Proposal:", or similar proposal markers as described in the extraction criteria.

The document contains: - A reason for change section - Summary of change section - Technical content about CMSD (Common Media Server Data) - References and annexes

However, none of these sections contain explicitly marked proposals following the formats specified (Proposal X:, Proposal X., Proposal:, etc.).

Extracted 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) for 3GPP TR 26.510 that describes technical changes and updates to Solution 5, but it does not include any formally marked proposals in the standard 3GPP proposal format.

Extracted Technical Proposals

Proposals from Section 7.11.9 (Summary)

Proposal 1: This candidate solution proposes a new mechanism allowing Media Clients to select the Media Entry Point with energy characteristics corresponding to the energy mode configured in the Media-aware Application, based on:

1. The collection of network energy-related characteristics by the Mobile Network Operator. This information is provided by the Energy Information Function and the Media AS to a new component called Energy Information AF instantiated in the Media AF.

2. The exposure of this information to the Media Client, for example from the Media AS to the Media Access Function.

3. The use of this information by the Media Session Handler in the UE to dynamically select the Media Entry Point with the desired energy characteristics.

Extracted Proposals

Based on my analysis of the document, I could not find any explicit proposals formatted as "Proposal X:", "Proposal X.", "Proposal:", "Proposal.", or "Proposal ".

The document is a 3GPP Change Request (CR) for TR 26.510/26.942, which proposes technical changes and additions to specifications related to energy management in 5G Media Streaming systems. While it contains extensive technical content describing solutions, procedures, architectures, and proposed normative changes, none of these are explicitly labeled or formatted as "Proposal" statements.

The document does contain: - A "Summary of change" section describing additions - A "Proposed normative changes" section (clauses 7.12.8.1 and 7.12.8.2) - Numbered technical specifications and requirements

However, none of these follow the standard proposal formatting conventions specified in your instructions.

Extracted Proposals

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

The document is a Change Request (CR) for 3GPP TR 26.510 (actually labeled as 26.942 in the header, which appears to be an error) that merges previously agreed CRs and adds new content related to energy efficiency in media delivery services. While it contains requirements, use cases, key issues, and technical content, none of these are explicitly formatted as "Proposals" in the standard 3GPP proposal format.

Extracted Proposals

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

The document contains recommendations in clause 9, but these are labeled as "Recommendations" rather than "Proposals". The recommendations are structured as numbered items under sections 9.2 and 9.3, but they do not use the word "Proposal" to introduce them.

Extracted Proposals

Proposal: Given the volume of contributions on FS_Energy_Ph2_MED, along with the various key points, conclusions, and recommendations to be discussed, it is proposed to delay the completion of the study by one SA meeting. Instead of finalizing the study and initiating the Stage 2 Work Item with the proposed normative work during SA4#135, the study would be completed, and the Stage 2 Work Item Description would be agreed during SA4#136.

To facilitate the Stage 2 completion in one SA meeting, it is proposed to:

Prevent the submission of candidate solutions, that have not already been discussed, after SA4#135.

Reach a consensus on a Stage 2 draft WID during the SA4#135-bis e-meeting.

Begin work on the new Stage 2 Technical Specification prior to WID approval at SA#112 in June by submitting discussion papers to the SA4#135-bis e-meeting and/or at SA4#136. These papers would include early drafts of TS 26.nnn V0.0.1/V0.0.2, based on the agreed baseline of Solution 5.

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

The document is a Change Request (CR) for TR 26.942 that updates the conclusions section. While it contains conclusions, recommendations, and consensus statements about normative work, none of these are explicitly labeled as "Proposal" in any of the formats specified (Proposal X:, Proposal X., Proposal:, Proposal., or Proposal ).

The document includes statements like "it is not recommended to pursue" and "there is consensus to address" and "No consensus has been found," but these are presented as conclusions rather than proposals.

Proposal

We propose the above Work Plan for the SA4 team's consideration.

Proposal: Based on the discussion above, it is proposed to:

• Organize a 2hours online webinar on Energy awareness in mobile streaming with hosting organizations being GoS and 3GPP SA4. We may ask GoS to execute or we may speak to 5G-MAG to organize webinar (simplifies some logistics)

• Make the event public and invite other organizations, including 5G-MAG, DVB and CTA WAVE.

• Invite other 3GPP working groups to the session and ask them for a presentation.

• Create a program that focuses on information exchange

• Target the workshop prior to the next 3GPP meeting, for example in the first week of February.

Proposal: It is proposed to take this information into account and inform other WGs about this event.

Extracted Proposals

Based on my analysis of the document, this document does not contain any explicit proposals.

The document is a 3GPP Change Request (CR) for TR 26.510 that describes a candidate solution (#10) for Key Issues 1 and 4 related to energy metrics reporting configuration. While it contains technical content describing solutions, changes, and specifications, there are no sections explicitly marked as "Proposal", "Proposal X:", "Proposal X.", etc.

The document includes sections like "Reason for change", "Summary of change", "Consequences if not approved", and various technical clauses, but none of these are formatted as formal proposals in the standard 3GPP proposal format.

Extracted Proposals

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

The document is a Change Request (CR) for 3GPP TR 26.510 that proposes technical solutions and normative changes, but these are presented as part of the CR content itself rather than as separately numbered or marked proposals in the typical 3GPP proposal format.

Extracted Proposals

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

The document is a Change Request (CR) for 3GPP TR 26.942 that proposes adding a new solution (Solution #11(b)) for Key Issues #5 and #6 related to Client-based Media Application Server selection and energy management. While it contains technical content describing a candidate solution, there are no sections explicitly labeled as "Proposal" in any of the standard formats.

Extracted 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) for 3GPP TR 26.510/26.942 that adds a solution for Key Issue #6 regarding client-driven management of media delivery service energy optimisation. While it contains technical solutions, architecture descriptions, and procedures, these are not formatted as formal proposals but rather as solution descriptions and normative requirements.

Extracted 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) for 3GPP TR 26.510 that proposes adding a solution (Solution #13) for Key Issue #6 regarding optimization of media sessions based on UE energy consumption. While it contains technical content describing the solution, functional descriptions, procedures, gap analysis, and potential normative requirements, there are no sections explicitly labeled as "Proposal" in any of the standard formats.

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 3GPP TR 26.501 that introduces a candidate solution for Key Issue #6 regarding client-driven switching between multipath and single path media delivery based on energy information. While the document contains technical content describing the solution, architecture, procedures, and proposed normative work, it does not contain any sections explicitly labeled as "Proposal", "Proposal X:", "Proposal X.", etc.

The document does contain sections like "Summary of change", "Consequences if not approved", and "Proposed Potential normative work changes" (in clause 7.X.85), but these are not formatted as formal proposals in the standard 3GPP proposal format.

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.", or "Proposal ".

This document is a Change Request (CR) for 3GPP TS 26.942, which proposes adding a solution for Key Issues 4 and 6 related to media service level degradation based on accumulated energy consumption. While the document contains detailed technical content describing the solution, architecture, procedures, and normative requirements, it does not contain any sections explicitly labeled as "Proposal" in the standard formats used in 3GPP contributions.

The document does have a "Summary of change" section and "Potential normative requirements" section (7.1x.8), but these are not formatted as formal proposals.