Question: In RTP/RTSP-based Unicast Content Access, when a UE is MooD-capable but does not contain the MooD Configuration MO and lacks preconfiguration to always include its location, what format does the sent MooD header follow?
Option 1: <currentLocation> field-value with an appended service-id
Option 2: 3gpp-mbms-offloading: (field-name followed by a colon)
Option 3: RTSP_URL representing the USBD fragment location, preceded by 3gpp-mbms-offloading:
Option 4: A relative reference to the USBD fragment with a base URI, appended to 3gpp-mbms-offloading:
Explanation: According to the rules for RTP/RTSP-based Unicast Content Access, if a UE is MooD-capable but lacks both the MooD Configuration MO and preconfiguration to include its location in RTSP requests, it indicates its capability by sending a MooD header that contains solely the field-name 3gpp-mbms-offloading followed by a colon (:), without any additional information. This approach allows the network to recognize the UE's capabilities for potential MBMS offloading decisions without requiring unnecessary location data transmission in this context.