Proposal 1: Add a note that this can only work for very simple cases excluding complex VLM/LLM explicitly in the text and limited to a model size, and what use cases this can be used for that can use such smaller models.

Proposal 2: Clarify end-end latency requirements and derive required bit-rate/latency and loss profiles

Proposal 3: Clarify the correct protocol usage to support this use case and the required latency, typically not HTTP/TCP.

Proposal 4: Ask SA2 how such burst can be supported and if a new QoS profile is needed or if existing.

Proposal 5: Clarify the required support of neural network codec if any for the UE

Proposal 6: Consider adding caching and model updates in the call flow to avoid downloading a model for each task.

Extracted Proposals

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

The document contains sections titled "Introduction," "Discussion," and "Proposal," but the "Proposal" section (Section 3) does not contain any text formatted as a proposal. Instead, it only states:

"We propose to add the following changes to the main CR, or base CR to TS 26.264."

This is followed by technical content showing proposed changes to specifications (marked as "First change" and "Second change"), but these are not formatted as formal proposals in any of the standard formats (Proposal X:, Proposal X., Proposal:, etc.).

The document is a discussion and agreement document that proposes technical changes to specifications, but does not contain formally marked proposals in the expected format.

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

The document is a Change Request (CR) form for TS 26.114 related to AI/ML for IMS services. While it contains several "Editor's Notes" indicating areas that need to be updated or clarified, these are not formatted as proposals. The document primarily consists of:

1. A CR form header with metadata
2. Reason for change, summary of change, and consequences sections
3. Multiple editor's notes describing future work needed
4. A call flow diagram (AC.4.1) with numbered steps

None of these elements are explicitly labeled as "Proposal" in any of the formats specified (Proposal X:, Proposal X., Proposal:, Proposal., or Proposal ).

Proposal 1: From the perspective of a UE, it is clear that the procedures and service operations concerning the request of an application list, download of the application list, request of a selected application, and download of the selected application, are already well defined in TS 23.228 as part of the BDC setup signalling procedures.

Proposal 2: We proposed to re-use these procedures and the HTTP protocol for the same purposes in AIML_IMS-MED.

Proposal 3: The negotiation of any capability exchange between the UE and the MF (e.g. for task and/or model selection) should happen after the selection and download of a DC app, via an application data channel application for that app.

Extracted Proposals

Proposal: It is proposed to include the contents of clause 2 into clause AC.4.3 of the base CR.

Proposal: We propose to add the following change to the base CR

Extracted Proposals

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

The document contains a "Proposal" section (Section 3), but it describes what "is proposed to update" rather than using the standard proposal format (e.g., "Proposal 1:", "Proposal:", etc.). The text in Section 3 reads:

"It is proposed to update the base CR by - defining the set of negotiation messages description corresponding to the local inferencing call flow - adding a description of the associated metadata for applications, endpoint capabilities, and AI/ML models. - adding a generic negotiation message format for AI metadata exchange"

This is a descriptive statement about what the document proposes to do, rather than a formally numbered or formatted proposal that would typically appear in the "Conclusions" section of a 3GPP contribution.

The document appears to be a Change Request (CR) that provides technical details and examples for negotiation messages and metadata, but does not contain explicitly formatted proposals following the standard 3GPP proposal conventions.

Extracted Proposals

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

The document contains sections for "Discussion" and "Proposal" (Section 3), but Section 3 only states "It is proposed to add the following changes to the base CR of AIML_IMS-MED" followed by technical content describing procedures and call flows. This is a description of proposed changes rather than a formally formatted proposal statement.

The document appears to be a technical contribution discussing adaptive model delivery procedures, but it does not contain any text explicitly formatted as: - "Proposal X: " - "Proposal X. " - "Proposal: " - "Proposal. " - "Proposal "

or similar variations that would indicate a formal proposal statement.

Extracted Proposals

Proposal

It is proposed to update the base CR by

defining the set of negotiation messages corresponding to the inferencing call flow

adding a description of the associated metadata for applications, endpoint capabilities, AI/ML models, and submodel partitioning.

adding a generic negotiation message format for AI metadata exchange including negotiation message between local and remote endpoints for split inferencing.

Extracted Proposals

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

The document contains a "Proposal" section (Section 2), but it does not contain text formatted as "Proposal X:", "Proposal:", or similar proposal markers. Instead, Section 2 only states:

"We propose to add the following change to the base CR of AI_IMS_MED."

This is followed by technical specification text describing changes to be made to the document, but no formal numbered or unnumbered proposals are listed.

The document does not have a "Conclusions" section that would typically contain a list of proposals.

Proposal: Add the following text to the base CR:

The UE and the DCAS (via the MF) configure the exchanged intermediate data format parameters over ADC

The intermediate data format parameters may include information on tensors characteristics, including the compression profile identifiers.

The UE captures input media data and provides it to inference task running on the UE.

The UE executes the UE inference subtask on the input media data using selected UE submodel and generates intermediate data for continuation of the inference process at the DCAS.

The UE transmits the intermediate data to DCAS (Via MF) according to the selected intermediate data format.

DCAS executes inference task on the received intermediate data using selected Remote submodel and generates the processed media data based on the inference results.

DCAS transmits the processed media data to UE (via MF).

The UE renders the final processed media data.

Extracted Proposals

Proposal

We propose to add the following changes to a base CR.

Incorporate change 1 and 2 into a base CR

Include change 3 in a dedicated annex for illustration purpose

Extracted Proposals

This document does not contain any explicitly marked proposals. The document is a Change Request (CR) that defines normative procedures, formats, and signaling for AI/ML assisted media processing in DCMTSI, but it does not include sections with text explicitly labeled as "Proposal", "Proposal:", "Proposal X:", etc.

Proposal: Schedule a time slot for the live demonstration of the NNC web decoder, for example during a meeting break.

Proposals

Proposal: We propose to take into account the above discussion and consider the inclusion of NNC-based compression in IMS-based AI/ML services.

Proposal: Add the following changes to the common base CR for AIML_IMS-MED.

Extracted Proposals

Proposal: We propose to take into account the above discussion and consider the inclusion of NNC-based compression in IMS-based AI/ML services.