Question: In a DASH-over-MBMS service, what conditions must be met for a User Equipment (UE) to switch between alternative Representations listed under `alternativeContent` in `userServiceDescription`, aside from coverage condition and policy requirements?
Option 1: Only the media container format must match, and the request can contain a byte range.
Option 2: The employed media codecs and configuration information must be identical, the request does not contain a byte range, and Segments of the alternative Representations must be time-aligned.
Option 3: The resolution of the video streams must be the same, and the audio codec can differ if it's within the same family (e.g., AAC).
Option 4: The switching is solely based on network conditions without any constraints on the media codecs or request format.
Explanation: For seamless switching between broadcast and unicast transport in a DASH-over-MBMS service, ensuring continuity and compatibility is crucial. Thus, having identical media codecs and configurations (to maintain stream integrity), not using byte range requests (which could disrupt continuous playback), and maintaining time-alignment of segments (for synchronized playback) are essential. This ensures that the UE can switch without noticeable disruptions or incompatibilities, making **Option 2** the correct answer.