Method and apparatus for designing, updating and operating a network based on quality of experience
View Patent ↗A software program/software tools allows end user quality of experience to be quantified and translated into network conditions required to achieve that end user quality of experience. By focusing on the Quality of Experience (QoE) for the applications that will use the network rather than the traditional bottom up approach, and then looking to design the network based on those end user requirements, the network may be designed and/or operated to achieve a high quality of experience. The program and tools may be used at different phases of the networking cycle, including design, planning, deployment, and operational phases, to allow the QoE requirements to be obtained while optimizing network cost and utilization. A QoE server may be implemented off line and used for network design/planning, or may be included on the network to monitor the network and control operation of the network to achieve the intended QoE.
1. A method of operating a network based on quality of experience, the method comprising the steps of:
determining, by a Quality of Experience server, that a Quality of Experience (QoE) violation associated with a service has occurred;
determining, by the Quality of Experience server, if the QoE violation is due to an equipment failure;
if the QoE violation is not due to an equipment failure, determining, by the Quality of Experience server, if the QoE violation is due to violation of an individual nodal Quality of Service (QoS) requirement by a node on the network, the individual nodal QoS requirement specifying how the node is required to operate to enable the service to be implemented on a network path through the network to enable the node to satisfy specified QoE requirements for the service; and
if there has been a nodal QoS violation, performing, by the Quality of Experience server, nodal optimization to adjust the manner in which the node is handling traffic to attempt to meet the QoS requirements;
if there has not been a nodal QoS violation, adjusting, by the Quality of Experience server, a class of service mapping for the service or identifying and selecting application layer control knobs for the service to enable the network to be adjusted to enable the Quality of Experience requirements for the service to be satisfied.
2. The method of claim 1 , wherein the step of adjusting a class of service mapping for the service comprises determining if the service has been mapped to an appropriate class of service.
3. The method of claim 1 , wherein nodal optimization comprises determining if an aggregate traffic profile for the service is greater than a capacity allocated to the service.
4. The method of claim 3 , wherein nodal optimization comprises adjusting a scheduler share for the service.
5. The method of claim 3 , wherein nodal optimization comprises adjusting a buffer size at the node so that a delay/loss margin for the service is not violated.
6. The method of claim 3 wherein the nodal Quality of Service (QoS) requirements are derived from a QoE allocation process for the service.
7. The method of claim 1 , further comprising the step of:
if the QoE violation is due to an equipment failure, fixing the equipment failure before modifying the service.
8. A method of allocating an impairment budget on a network path, the network path extending through first nodes in a first network and second nodes in a second network, the method comprising:
determining, by a Quality of Experience server, a set of quality of service metrics to be implemented on the network path for a service to be offered on the network path, the set of quality of service metrics being based on a required set of quality of experience parameters for the service;
determining, by the Quality of Experience server, a total impairment budget for the network path based on the quality of service metrics, the total impairment budget specifying one or more upper bound thresholds for the quality of service metrics;
allocating, by the Quality of Experience server, a first portion of the total impairment budget to the first network and a second portion of the total impairment budget to the second network; and
dividing, by the Quality of Experience server, the first portion of the total impairment budget between the first nodes to arrive at individual impairment allocations for each of the first nodes, each individual impairment allocation for each node of the first nodes specifying a quality of service budget for the node, the quality of service budget specifying how the node is required to operate to enable the service to be implemented on the network path and meet the required set of quality of experience parameters for the service.
9. The method of claim 8 , wherein the first network is an access network and the second network is a core network, and wherein the step of allocating comprises allocating the total impairment budget between the access network and the core network.
10. The method of claim 8 , wherein the step of allocating comprises allocating at least one of the quality of service metrics.
11. The method of claim 10 , wherein the allocated quality of service metric is latency.
12. The method of claim 11 , further comprising the step of determining a fixed latency for each node on the network path in upstream and downstream directions.
13. The method of claim 12 , further comprising the step of determining a variable latency for each node on the network path in upstream and downstream directions.
14. The method of claim 13 , further comprising summing the downstream variable latency for the nodes on the network path and using the sum to determine a size of a jitter buffer for the service.
15. A method of designing or updating a network based on end-user Quality of Experience requirements for a service, the method comprising the steps of:
receiving, by a Quality of Experience server, a set of parameters defining a service to be offered on the network;
determining, by the Quality of Experience server, end-to-end Quality of Experience (QoE) requirements for the service from the set of parameters defining the service;
mapping, by the Quality of Experience server, the QoE requirements to Quality of Service (QoS) requirements for the service; and
using the Quality of Service requirements for the service to design or update the network to enable the network to satisfy the end-user Quality of Experience requirements for the service;
wherein the set of parameters defining the service include context independent parameters of the service and context dependent parameters of the service; and
wherein the step of determining end-to-end Quality of Experience (QoE) requirements for the service comprises using the set of parameters defining the service to key into a Quality of Experience database to obtain preferred and acceptable values for the service.
16. The method of claim 15 , wherein the context independent parameters comprise at least one of timeliness of the service and media/modalities to be used to implement the service.
17. The method of claim 16 , wherein the context dependent parameters comprise at least one of network scenario, contact type, transmission mode, connectivity type, and terminal type.
18. The method of claim 15 , wherein the context independent parameters of the service are used to determine the preferred values for the service, and wherein the context dependent parameters of the service are used to adjust the preferred values to compute the acceptable values for the service.
19. The method of claim 15 , wherein the QoE requirements comprise a comprehensive set of metrics for the media and control path for each modality associated with the service.