es not allow prioritization of one application (through such Internet access) over the other, although Table 3.4 DPI performance metrics. function Performance metric Speed Accuracy Dependability Resources Plane Node-internal transfer User plane delay Packet processing rate User plane Error rate User plane False-positive error rate User plane False-negative error rate User plane Rate of successfully User plane identified packets DPI inspection depth User plane TCP successful connection User plane establishment rate Number of concurrent User plane TCP connections TCP connection User plane establishment success rate Packet loss rate User plane Failover time Control plane Network management Management system (NMS) response plane Supported concurrent Management NMS number plane Energy per bit DPI node Energy per packet DPI node Number of supported User plane application types DPI PIB size at the line rate User plane Rule take effect time Control plane NMS DPI rule age report Control plane 3.7 QoS in Future Networks certain traffic management schemes (with or without DPI in use) can be beneficial to all applications served in a network neutral and best-effort manner. For example, there can be defined application-specific DPI performance metrics for HTTP, such as HTTP application transaction identification rate. It is defined as the number of HTTP transactions per second (through the given DPI node) that have been successfully established and identified by the DPI node. One may note here that an HTTP connection is successfully established, which means that the response code "HTTP 200 OK" is sent from the HTTP server to the HTTP client after the connection has been initiated with the HTTP GET request from the client to the server. The measurement unit of this metric is a reciprocal second, SO the result of 50 means that 50 HTTP connections were identified (by the DPI node) as successfully established in the time period of one second. However, this is not a key performance indicator (KPI) for the DPI node, while most of t