RAN1 / #119 / NR_AIML_air / Verify

Spreadtrum · 9.1.4.2

Other aspects of AI/ML model and data · RAN1#119 · Source verification
Claude's delta dropped vs RAN1#118bis
Spreadtrum did not participate in the current meeting, dropping out of the NR_AIML_air discussions.
AI-synthesized from contributions · all text is paraphrased
Every position summary on this site is generated by an AI from the actual Tdoc contributions. This page shows you the exact source documents Claude read to produce the summary above, so you can verify it yourself. Click any Tdoc ID to view its detail page, or click "3gpp.org ↗" to read the original on the official 3GPP server.

Contributions at RAN1#119 · 1 doc

R1-2409628 discussion not treated 3gpp.org ↗
Discussion on other aspects of AI/ML model and data
Position extracted by Claude
Spreadtrum proposes that RAN1 should not discuss data collection for UE-side model training, preferring mechanism 1a or waiting for RAN2 progress due to privacy concerns regarding network exposure. They require that model transfer/delivery Case z1 be deprioritized in Rel-19, arguing it incurs unnecessary offline cross-vendor collaboration burdens compared to Case y. They oppose considering MI-Option 1 for two-sided use cases, asserting that the data collection steps (A-C) are unnecessary for model identification and that Step E can be realized by MI-Option 2 or 3. They observe that RAN1 should focus on the content of model structure, leaving model format and signaling to other working groups. They support considering MI-Option 2, 3, and 4 for two-sided use cases, noting that MI-Option 4 depends on defining reference models.
Summary
Spreadtrum presents three proposals and four observations regarding AI/ML for the NR air interface in Rel-19, focusing on data collection, model transfer, and identification. The document argues that RAN1 should deprioritize certain model transfer cases and exclude specific model identification options for two-sided models, while deferring data collection discussions to RAN2. It emphasizes that RAN1's scope should remain on model structure content rather than signaling formats.

Prior contributions at RAN1#118bis · 1 doc · Oct 14, 2024

R1-2407697 discussion not treated 3gpp.org ↗
Discussion on other aspects of AI/ML model and data
Position extracted by Claude
Spreadtrum advocates FOR deprioritizing model transfer cases z1 and z2 in Rel-19 due to cross-vendor collaboration burdens and proprietary design disclosure risks. They support mechanism 1a for UE data collection to avoid privacy exposure to network, and promote network-controlled model identification where NW assigns model IDs. They are AGAINST redundant procedures in MI-Option 1 and prefer focusing RAN1 scope on model content rather than signaling formats.
Summary
Spreadtrum presents their views on AI/ML for NR air interface general aspects including data collection, model transfer/delivery, and model identification for two-sided models. The document contains 4 proposals and 4 observations addressing deprioritization of certain model transfer cases and procedures for model identification.
How this was derived
Claude extracted the "position extracted" field above directly from each Tdoc during summarization. For the delta summary at the top, Claude compared Spreadtrum's consolidated stance at RAN1#119 against their stance at RAN1#118bis and classified the change as dropped. Always verify critical claims against the original Tdocs linked above.