Question: After a PAUSE request, how must a server reflect the time interval in the P timestamp when responding to a subsequent PLAY request in a 3GPP PSS session?
Option 1: The server must reset the P timestamp to zero, ignoring the elapsed time during the pause.
Option 2: The server must reflect the actual time interval elapsed between the last P packets sent before the PAUSE and the first P packets sent after the PLAY request in the P timestamp.
Option 3: The server can choose to either reset the P timestamp or continue from where it left off, depending on its configuration.
Option 4: The server should adjust the P timestamp based on the client's Range header, if provided.
Explanation: This is correct because the 3GPP PSS specification requires that the P timestamp space must be continuous along time during a session, reflecting the actual time elapsed since the beginning of the session. Therefore, after a PAUSE, the server must accurately account for the time elapsed when responding to a PLAY request by adjusting the P timestamp accordingly. This ensures seamless continuity of media playback.