Media Playback State 2 VS 3

In which cases does a FPS client send state 2 (0xa5d6739e) vs. state 3 (0x4f834330) in the media playback state TLLV? Does state 2 happen when a lease expires (for management of simultaneous streams)? If so, when does state 3 happen?


We are specifically interested if a lease renewal in order to track simultaneous streams might ever lead to player expecting a key in the CKC (following state 3) or if an update of the lease expiration without providing the key suffices (following state 2).


Thanks and

br, gerold

Replies

State 2 is sent on every lease renewal request when the client device already has a content key for a given sub-stream (tier). State 3 may happen for multi-tier streams that belong to the same asset ID, but encrypted with different keys. Example: a particular asset has two tears: SD and HD. When playback starts the content key for SD stream is acquired and lease period starts. Once network condition improve, HD tier can be played back, so content key needs to be acquired for the HD tier. In this case "State 3” will be sent in the media playback state TLLV since playback is already started for the SD tier of the asset ID but content key is required (for HD tier).

Thank you very much!


Best,

gerold