R1-2409989
discussion
Other aspects of AI/ML for two-sided model
From Nokia
Summary
Nokia's contribution analyzes model identification and transfer/delivery aspects for two-sided AI/ML CSI compression use cases in 5G NR, presenting 5 observations and 2 proposals on how different inter-vendor collaboration options map to specific model identification procedures.
Position
Nokia advocates FOR prioritizing MI-Option 2 with dataset transfer for inter-vendor collaboration Option 4, supporting flexible model transfer mechanisms that can handle partial parameter updates and non-compiled models requiring UE-side offline engineering. They are pushing FOR clear mapping between model identification options and inter-vendor collaboration scenarios, while emphasizing that transferred models should not be ready-for-inference to accommodate UE vendor platform specifics.
Key proposals
- Proposal 1 (Sec 1): For the 2-sided models use case, RAN1 to prioritize the study on the details of the model identification MI-Option 2 steps for the purpose of the inter-vendor collaboration Option 4
- Proposal 2 (Sec 2): The model transfer/delivery Case 4 configurations for two-sided models, need to support the transfer of a model not ready for inference, including: model structure ID (indication referring to known model structure) and full or partial set of parameter values
- Observation 1 (Sec 1): Based on our analysis of MI-Option 2, the steps and the ID-X can be used for the inter-vendor collaboration Option 4
- Observation 2 (Sec 1): Based on our analysis, assuming that only the UE-part of the model structure is to be standardized in the inter-vendor collaboration Option 3 (Direction A or B), the MI-Option 3 is applicable for model identification
- Observation 3 (Sec 1): Based on our analysis, assuming that only the UE-part of the model is to be standardized in the inter-vendor collaboration Option 1 (Direction C), the MI-Option 4 with the outlined Step A-D is applicable for model identification
- Observation 4 (Sec 2): The model transfer/delivery Case 4 applies only when the inter-vendor collaboration Option 3 (Direction A or B) are adopted and requires the model identification ML-Option 3 to be used
- Observation 5 (Sec 2): The RAN1 related configurations may be considered for the transfer should be flexible enough to allow full or partial model updates, i.e. the CP config might indicate this, and the transfer needs to include UE-vendor specific meta information