Question: In MBMS, when a UE finds its previously selected Consumption Report Server is no longer listed in the updated APD fragment, what action does the UE take regarding consumption report submissions?
Option 1: The UE continues to send consumption reports to the original server until it receives an HTTP error response.
Option 2: The UE pauses all consumption report submissions until the previously selected server is reinstated in a future APD update.
Option 3: The UE randomly selects a new serviceURI element from the updated APD's consumptionReporting element and sends reports to this new destination at the next scheduled opportunity or upon specific conditions (location change, stop, or start).
Option 4: The UE sends a query to the BM-SC for explicit instructions on which Consumption Report Server to use.
Explanation: When a UE encounters an updated APD where its previously chosen consumption report server is no longer listed, it must adapt by selecting a new server from the provided options. This ensures continuous reporting with minimal disruption, using uniform distribution for selection to potentially distribute load across available servers. Reporting to the new server occurs at the next scheduled opportunity or upon location change, stop, or start, keeping reports up-to-date and relevant.