M.3 Content Switch without SDP

26.2343GPPProtocols and codecsRelease 17Transparent end-to-end Packet-switched Streaming Service (PSS)TS

M.3.1 Successful Content Switch without available SDP

The following example depicts fast content switching without an available SDP. The client has received a content URL but has not yet retrieved the SDP. The client has probed the server features during an earlier interaction.

M.3.2 Partial successful Content Switch without available SDP

The following example depicts fast content switching without an available SDP. The client has only a content URL and still must retrieve the content description. The client has probed the server features during an earlier interaction.

In this example, the switch request (PLAY request) returns a "202 Accepted" since the server was not able to select the desired flows from the SDP files. For example, the SDP file may contain several audio tracks and the server was unable to make a selection.

M.3.3 Partial successful Content Switch without available SDP

The following example depicts fast content switching without an available SDP. The client has only a content URL and still must retrieve the content description. The client has probed the server feature capabilities during an earlier interaction.

The switch request (PLAY request) returns a "206 Partial Data" since the server was not able to send all data flows of the SDP file. The client first sets up a new transmission resource, as defined in clause 5.5.4.6 (Addition of Media components)