1 / 7

RTCP XR Report Block for QoE metric Reporting draft-ietf-xrblock-rtcp-xr-qoe-03

RTCP XR Report Block for QoE metric Reporting draft-ietf-xrblock-rtcp-xr-qoe-03. Alan Clark Roland Schott Qin Wu Glen Zorn. Document Status. This draft deals with two use cases each media sent in separate RTP stream Multi-channel audios sent in the same RTP stream

astro
Télécharger la présentation

RTCP XR Report Block for QoE metric Reporting draft-ietf-xrblock-rtcp-xr-qoe-03

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RTCP XR Report Block for QoE metric Reportingdraft-ietf-xrblock-rtcp-xr-qoe-03 Alan Clark Roland Schott Qin Wu Glen Zorn XRBLOCK IETF 85 Atlanta

  2. Document Status • This draft deals with two use cases • each media sent in separate RTP stream • Multi-channel audios sent in the same RTP stream • One issue raised in the last Vancouver meeting is • ITU-T Standards we referenced have many input parameters and option, how to accommodate this into this metric block format? E.g., how to know what codec is used. • Recent update was submitted to address • Clarify to use payload type to provide a single value index to a complicated set of input parameters including Codec. • Address the comments raised to PDV but are applied to this document as well • Get in line with ITU-T SG12, update P.NAMS and P.NBAMS • Add one new MoS calculations algorithm by referring to TCC201.01 • Two open issues brought up on the list • How to provide MoS value for both narrowband and wideband or for both lower resolution and higher resolution? • P.NAMS and P.NBAMS updating XRBLOCK IETF 85 Atlanta

  3. Open issue 1:P.NAMS and P.NBAMS reference updating • P.NAMS and P.NBAMS have been published as P.1201 and P.1202. • P.1201 is further split into P.1201.1 and P.1202.2 to support lower resolution application and higher resolution application respectively, so does P.1202. • Shall we reference P.1201 for MoS calculation method or reference both P.1201.1 and P.1202.2 for MoS calculation method? XRBLOCK IETF 85 Atlanta

  4. Open issue 2:Registry for calculation algorithm • This issue raised by Al in the last meeting is whether registration for calculation is sufficient. • One solution suggested by Colin is to have another IANA registry for MOS type and calculation type • those need to be signaled in SDP. • The XR block should then convey an identifier that relates it to the SDP. • In addition, one change to XRBLOCK format is to take out ‘segment type’bit, Mos type field, Calculation algorithm field and replace with 8 bits identifier field. • If we agree with the above change, we can signal more details that are related to the ‘Identifier’ using the SDP.

  5. Why MoS reference is needed? • MoS reference are referred to the QoE related parameter that is used to distinguish narrowband speech from wideband speech or  low resolution video from high resolution for video. • For audio, MOS values for narrowband, wideband occupy the same range. For video application, MoS values for SD resolution, HD resolution video also occupy the same ranges, therefore it is important for the QoE block to indicate what the MOS reference is. • P.NAMS, P.NBAMS, they are split to support lower resolution application and higher resolution application respectively, which also prove us that it is useful to indicate what the MoS reference is. XRBLOCK IETF 85 Atlanta

  6. Open issue 3: MoS reference Support • If we agree to use SDP to signal more details, we can signal MoS reference in the SDP. • However if we don’t rely on SDP and need to support MoS reference in the format, we should give a definition of MoS reference. • The downside is we need to expand 32 bit segment for each new option to be added. • Question: Signal MoS reference in the SDP or in the format of QoE XRBLOCK? XRBLOCK IETF 85 Atlanta

  7. Follow Up • Question? • Address these comments and go for WGLC? XRBLOCK IETF 85 Atlanta

More Related