Question: When a UE's IP-CAN type changes due to IP flow mobility, what additional information must the PCRF include for the affected service data flows in the RAR command?
Option 1: Only the new IP-CAN-Type AVP
Option 2: The new IP-CAN-Type AVP and RAT-Type AVP (if applicable) within the Flows AVP at command level
Option 3: AN-Trusted AVP, AN-GW-Address AVP, and Specific-Action AVP without flow specifics
Option 4: No additional information is required for affected service data flows
Explanation: When IP flow mobility triggers an IP-CAN type change, affecting only a subset of flows within an AF session, the PCRF must provide detailed updates for these impacted flows. This includes specifying both the new IP-CAN type and, if relevant, the RAT type, directly tied to the affected service data flows. This granular update ensures proper policy and charging control application on the modified flow set, necessitating the inclusion of this information within the Flows AVP at the command level for precise handling.