2.2.8.1.2.2.6 Fast-Path Quality of Experience (QoE) Timestamp Event (TS_FP_QOETIMESTAMP_EVENT)
The TS_FP_QOETIMESTAMP_EVENT structure is used to enable the calculation of Quality of Experience (QoE) metrics. This event is sent solely for informational and debugging purposes and MUST NOT be transmitted to the server if the TS_INPUT_FLAG_QOE_TIMESTAMPS (0x0200) flag was not received in the Input Capability Set (section 2.2.7.1.6).
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
eventHeader |
timestamp |
||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
eventHeader (1 byte): An 8-bit, unsigned integer. The format of this field is the same as the eventHeader byte field, specified in section 2.2.8.1.2.2. The eventCode bitfield (3 bits in size) MUST be set to FASTPATH_INPUT_EVENT_QOE_TIMESTAMP (6). The eventFlags bitfield (5 bits in size) MUST be zeroed out.
timestamp (4 bytes): A 32-bit, unsigned integer. A client-generated timestamp, in milliseconds, that indicates when the current input batch was encoded by the client. The value of the first timestamp sent by the client implicitly defines the origin for all subsequent timestamps. The server is responsible for handling roll-over of the timestamp.