1.3 Overview
This protocol is a proprietary protocol for publishing QoE metrics from a protocol client to a QoE Monitoring Agent.
A protocol client publishes QoE metrics for each Session Initiation Protocol (SIP) session. The QoE metrics are categorized into two types: one type capturing objective metrics during the session, and the other containing subjective metrics collected from the end user. The protocol client encodes the QoE metrics to conform to the XML schema that is specified in section 2, and then publishes the metrics in the form of a SIP SERVICE message that the protocol client sends to the QoE Monitoring Agent through a SIP proxy. QoE Monitoring Agent then converts the messages into an internal format and sends them to QoE Monitoring Server and/or a registered 3rd consumer.
Note: The routing behavior of the SIP proxy is based on the SIP routing rules that are described in [MS-SIPRE] section 3.
The QoE Monitoring Agent runs along with SIP proxy and it validates the SIP SERVICE message and returns a final SIP SERVICE response. The response is based on standard SIP rules and is either response code 202 Accepted, or an error code.
Note: A SIP 202 response indicates that the QoE Monitoring Agent accepted the report, but not that it processed the report.
This sequence of events is illustrated in the following figure in which, at the end of a session between two protocol clients, each protocol client publishes QoE metrics to the QoE Monitoring Agent through the SIP Proxy that mediated the session, and the QoE Monitoring Agent returns a SIP 202 response to each protocol client.
Figure 1: SIP message sequence from protocol client session end through QoE reporting
The QoE Monitoring Server can use QoE metrics for:
Generating alerts regarding abnormal media quality conditions.
Generating media quality and resource utilization reports.
Building a history database for advanced diagnostics and analytic applications.