Proposal: This contribution proposes preliminary licensing terms for the DaCAS-2 test script, as outlined in Section 2.1, and invites feedback from participants. The contributor list will be updated in parallel with code changes, as detailed in Clause 2.2.

Based on my review of the document, there are no proposals explicitly marked as such in this contribution.

The document is an evaluation data submission for Device 3 in the DaCAS-2 work item. It contains technical specifications, recording parameters, and database information, but does not include any sections explicitly labeled as "Proposal", "Proposal X:", "Proposal X.", etc.

The Conclusion section (Section 3) mentions that "The proposed draft database is submitted for the group's review" but this is a descriptive statement rather than a formally marked proposal.

Proposal: The source would like to propose for agreement that complexity analysis of an example solution should be conducted using metrics chosen by the proponent, and documented with sufficient details in the submission of the deliverable.

Extracted Proposals

Based on my review of the document, there are no formal proposals explicitly marked with "Proposal" in this 3GPP document.

This document (S4-260135) is a Work Plan for DaCAS (Diverse audio Capturing System for UEs) that outlines timelines, milestones, and activities across multiple SA4 meetings. While it contains many agreements, work items, and goals, none of these are formally labeled as "Proposal" using any of the standard formats (Proposal X:, Proposal X., Proposal:, Proposal., or Proposal ).

The document is structured as a timeline with activities and agreements planned for various meetings and telcos, but these are presented as work plan items rather than formal proposals.

This document does not contain any proposals. The document is a permanent document (pdoc) that serves as a template for tracking the progress of defining DaCAS example solutions and their deliverables, but it does not include any explicit proposals marked as such.

Proposal: The following components should be included in an example solution deliverable:

A list of target device(s) supported,

High-level description of data used to develop the example solution,

A list of supported output format(s),

High-level algorithmic description,

Executable or library with API (windows or linux), including a guide on how to compile (if applicable) and run,

Report of evaluation results, following at minimum the test methodologies and evaluation scenarios specified in DaCAS-2 and DaCAS-3,

Legal framework, if any, necessary by the solution provider to share the content listed above (e.g. User license for the example solution),

Supplementary information.

Extracted Proposals

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

The document is a working draft (v0.56) of a technical specification for DaCAS-2 test methodologies and requirements. It contains requirements, test methodologies, and procedures, but these are presented as normative/informative content within the specification structure rather than as formal proposals.

The document includes several "Editor's notes" indicating areas where decisions are still needed, but these are not formatted as proposals. The content appears to be at a stage where proposals have already been incorporated into the draft specification text itself.

Proposals

Proposal

The source proposes a following extension to IMPro method for realisable measurement of RIPD and support of devices with significant variations or uncertainties in microphone integration.

Extracted Proposals

Proposal 1: Agree on the following minimum set of recordings for successful device characterization, example solution development, and further evaluation of example solutions.

Minimum set of recordings

Required recordings: - Recording scenarios 1, 2 and 3 defined in [1] - At least 2 recordings of real immersive usage scenario (e.g., based on recording scenarios 5-8 defined in [1])

Recommended recordings: - At least 4 recordings of real immersive usage scenarios (e.g. based on recording scenarios 5-8 defined in [1]) - Preferably recordings of all recording scenarios defined in [1]

Proposal 2: The collection of above minimum set of recordings is finalized latest at SA4-136 meeting.

Proposal: Time plan according to Table 1 is proposed for agreement.

Proposals

Proposal 1:

All example solutions which are evaluated, described, and documented according to procedures and level of detail agreed by SA4 prior to example solution submission will be included in an informative Annex of TS 26.533.

Proposal 2:

All example solutions that additionally meet the requirements defined in TS 26.261 will be specified (including the documentation of the test results) in TS 26.533 with informative status.

Proposals

Proposal: Presented updates to the recording scenario 3 in the section 2 are proposed for agreement. The updated recording scenario would allow to align DaCAS evaluation more closely to the test methods specified in latest release of 3GPP 26.260 [2].