APPLICATION QUALITY MANAGEMENT IN A COOPERATIVE COMMUNICATION SYSTEM

• US 20140153392A1
• Filed: 12/30/2013
• Published: 06/05/2014
• Est. Priority Date: 12/22/2011
• Status: Abandoned Application

• Current Assignee: Wi-LAN Labs, Inc. (Wi-LAN Inc.)
• Original Assignee: Cygnus Broadband, Inc. (Quarterhill Inc. (f/k/a Wi-LAN Inc.))
• Inventors: Gell, David, Stanwood, Kenneth L.
• Application Number:
  US14/143,800
• Publication Number:
  US 20140153392A1
• Time in Patent Office: Days
• US Class Current: 370/230
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04W 28/0236 radio quality, e.g. interference, losses or delay
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

An application manager node in a communication network, including a transceiver module configured to monitor data communication in the communication network, and a processor coupled to the transceiver and configured to receive, from at least one terminal node, application information related to at least one application data stream associated with at least one application operating in the at least one terminal node, update, based on the application information, a relationship map that includes a relationship between each of the at least one application data stream and an access node, determine an overall quality metric value associated with the access node based at least in part on the application information received from one or more of the at least one terminal node, and select, based on the overall quality metric value, at least one mitigation option for one or more of the at least one application data stream.

Claims

1. An application manager node in a communication network, comprising:

a transceiver module configured to monitor data communication in the communication network; and

a processor coupled to the transceiver and configured to;

receive, from at least one terminal node, application information related to at least one application data stream associated with at least one application operating in the at least one terminal node,

update, based on the application information, a relationship map that includes a relationship between each of the at least one application data stream and an access node,

determine an overall quality metric value based at least in part on the application information received from one or more of the at least one terminal node, and

select, based on the overall quality metric value, at least one mitigation option for one or more of the at least one application data stream.

2. The application manager node of claim 1, wherein the relationship map further includes a relationship between each of the at least one application data stream and one of the at least one terminal node that sent the application information for the respective application data stream to the application manager node.

3. The application manager node of claim 1, wherein the overall quality metric value is based at least in part on the application information received from one or more of the at least one terminal node that are associated with the access node.

4. The application manager node of claim 1, wherein the processor is further configured to initiate the at least one mitigation option.

5. The application manager node of claim 1, wherein the overall quality metric value is compared to a threshold and the mitigation selection is conducted if the overall quality metric value crosses the threshold.

6. The application manager node of claim 1, wherein the communication link through which the access node and the terminal node communicate is one of a wireless network and a wired network.

7. The application manager node of claim 1, wherein the application information is one of a periodic report and an aperiodic report that is received from the at least one terminal node.

8. The application manager node of claim 1, wherein the application information includes application information and terminal node information and the overall quality metric value is determined based on the application information and the terminal node information.

9. The application manager node of claim 1, wherein the application information comprises at least one of a data stream quality metric and a data stream importance metric related to one or more of at least one data stream associated with a corresponding application.

10. The application manager node of claim 1, wherein the overall quality metric value is a cell-wide quality metric value that is determined based on a data stream quality metric for one or more of the at least one application data stream that is associated with a cell of the access node.

11. The application manager node of claim 10, wherein the determination of the overall quality metric value is based on an average value of the data stream quality metric for one or more of the at least one application data stream.

12. The application manager node of claim 10, wherein a weight is applied to each data stream quality metric when determining the overall quality metric value, and wherein each weight is based on at least one of a service level agreement (SLA) value, a quality of service (QoS) value and a data stream importance metric.

13. The application manager node of claim 1, wherein the overall quality metric value is determined based on a data stream quality metric for each of a subset of the at least one application data stream associated with the access node.

14. The application manager node of claim 5, wherein the selection of the at least one mitigation option is conducted if the overall quality metric value stays below the threshold for a minimum time duration.

15. The application manager node of claim 4, wherein the initiation of the at least one mitigation option includes sending a mitigation instruction message to one of the at least one terminal node that is associated with the application data stream on which the mitigation option is to be implemented.

16. The application manager node of claim 15, wherein the mitigation instruction message includes at least one of the overall quality metric value and a time duration that the overall quality metric value has been below a threshold.

17. The application manager node of claim 1, wherein the at least one mitigation option includes one or more of delaying data packets, discarding data packets, delaying acknowledgements, discarding acknowledgements, delaying new data stream initiation requests, discarding new data stream initiation requests, terminating an application, and taking no action.

18. The application manager node of claim 1, wherein the selection of at least one mitigation option associated with one or more of the at least one application data stream is based at least in part on a data stream importance metric for each of the at least one application data stream.

19. The application manager node of claim 4, wherein the selected at least one mitigation option is implemented based on a time duration that the overall quality metric value is below a threshold.

20. The application manager node of claim 4, wherein the selected at least one mitigation option is implemented based on the overall quality metric value.

21. A terminal node in a communication network having an access node, comprising:

a transceiver module configured to send data packets to, and receive data packets from, the access node via the communication network; and

a processor coupled to the transceiver and configured to;

detect at least one application data stream by monitoring the data packets sent to, and received from, the access node via the communication network,

determine, for each of the detected at least one application data stream, application information related to an application operating in the terminal node that is associated with the respective application data stream, the application information including a data stream quality metric for each respective application data stream,

send, via the communication network, the application information for each of the detected at least one application data stream,

receive, via the communication network, at least one mitigation instruction associated with one or more of the at least one application data stream, and

implement the at least one mitigation instruction for the associated one or more of the at least one application data stream.

22. The terminal node of claim 21, wherein the communication network is one of a wireless communication network and a wired communication network.

23. The terminal node of claim 21, wherein the application information for each of the detected at least one application data stream is determined based at least in part on a current terminal node characteristics data set.

24. The terminal node of claim 21, wherein the application information is sent to the access node for transfer from the access node to an application manager node.

25. The terminal node of claim 21, wherein the processor is further configured to classify one or more of the detected at least one application data stream by inspecting one or more data packets associated with the respective application data stream and assigning an application class value to the application data stream based on the inspection of the one or more data packets, and wherein the application class value is included in the application information for the respective application data stream.

26. The terminal node of claim 21, wherein the determination of application information for each application data stream includes determining a data stream importance metric for the application data stream and including the data stream importance metric in the application information for the application data stream.

27. The terminal node of claim 26, wherein the processor is further configured to generate at least one of a current application characteristics data set for each of the at least one application data stream based on current characteristics of an application associated with the respective application data stream, and a current terminal node characteristics data set based on current characteristics of the terminal node.

28. The terminal node of claim 27, wherein the data stream importance metric is based at least in part on the current application characteristics data set and the current terminal node characteristics data set.

29. The terminal node of claim 27, wherein the current application characteristics data set includes at least one or more of an application class value, a stream initiation type value, an update pending value, a display position value, a network quality of service (QoS) value and a buffer margin value.

30. The terminal node of claim 27, wherein the current terminal node characteristics data set includes at least one or more of a user attention value and a service level agreement (SLA) value and a terminal node type.

31. The terminal node of claim 26, wherein the data stream quality metric is based at least in part on an indication of missing or delayed data packets associated with the application data stream.

32. The terminal node of claim 26, wherein the data stream quality metric is based at least in part on an application quality metric value received from the application operating in the terminal node that is associated with the corresponding application data stream.

33. The terminal node of claim 21, wherein the application information for each application data stream includes at least one of an application characteristics data set related to the data stream and a terminal node characteristics data set.

34. The terminal node of claim 21, wherein the application information is sent from the terminal node to the access node on one of a periodic and an aperiodic basis.

35. The terminal node of claim 21, wherein the application information further includes one or more of a terminal node identification associated with the terminal node, a cell identification associated with the access node, and a handover metric value.

36. The terminal node of claim 21, wherein the at least one mitigation instruction includes one or more of a data packet delay instruction, a data packet discard instruction, an acknowledgement delay instruction, an acknowledgement discard instruction, a new data stream request delay instruction, a new data stream request discard instruction, and an application termination instruction.

37. The terminal node of claim 21, wherein the at least one mitigation instruction includes at least one of an overall quality metric value and a time duration that the overall quality metric value is below a threshold, and wherein the implementation of the at least one mitigation instruction includes determining a mitigation action based on the at least one of the overall quality metric value and the time duration.

38. The terminal node of claim 21, wherein the implementation of the at least one mitigation instruction is based at least in part on a data stream importance metric for each of the at least one application data stream.

39. The terminal node of claim 38, wherein the respective one of the at least one mitigation instruction is implemented on the application data stream having the lowest data stream importance metric, and is then successively implemented for at least one other application data stream having the next lowest data stream importance metric.

40. The terminal node of claim 21, wherein the at least one mitigation instruction is implemented on an increasing number of the associated application data streams as a time duration of the implementation increases.

41. The terminal node of claim 21, wherein the at least one mitigation instruction is implemented based on a time duration that a quality metric value is below a threshold.

42. The terminal node of claim 21, wherein a level of implementation of the at least one mitigation instruction is based on a quality metric value.

43. A method for management of application quality in a communication network, the method comprising:

receiving, from at least one terminal node, application information related to at least one application data stream associated with at least one application operating in the at least one terminal node;

updating, based on the application information, a relationship map that includes a relationship between each of the at least one application data stream and an access node;

determining an overall quality metric value based at least in part on the application information received from one or more of the at least one terminal node; and

selecting, based on the overall quality metric value, at least one mitigation option for one or more of the at least one application data stream.

44. The method of claim 43, wherein the relationship map further includes a relationship between each of the at least one application data stream and one of the at least one terminal node that sent the application information for the respective application data stream to the application manager node.

45. The method of claim 43, wherein the overall quality metric value is based at least in part on the application information received from one or more of the at least one terminal node that are associated with the access node.

46. The method of claim 43, further including the step of initiating the at least one mitigation option.

47. The method of claim 43, wherein the overall quality metric value is compared to a threshold and the mitigation selection is conducted if the overall quality metric value crosses the threshold.

48. The method of claim 43, wherein a communication link through which the access node and the terminal node communicate is one of a wireless network and a wired network.

49. The method of claim 43, wherein the application information is one of a periodic report and an aperiodic report that is received from the at least one terminal node.

50. The method of claim 43, wherein the application information includes application information and terminal node information and the overall quality metric value is determined based on the application information and the terminal node information.

51. The method of claim 43, wherein the application information comprises at least one of a data stream quality metric and a data stream importance metric related to one or more of at least one data stream associated with a corresponding application.

52. The method of claim 43, wherein the overall quality metric value is a cell-wide quality metric value that is determined based on a data stream quality metric for one or more of the at least one application data stream that is associated with a cell of the access node.

53. The method of claim 52, wherein the determination of the overall quality metric value is based on an average value of the data stream quality metric for one or more of the at least one application data stream.

54. The method of claim 52, wherein a weight is applied to each data stream quality metric when determining the overall quality metric value, and wherein each weight is based on at least one of a service level agreement (SLA) value, a quality of service (QoS) value and a data stream importance metric.

55. The method of claim 43, wherein the overall quality metric value is determined based on a data stream quality metric for each of a subset of the at least one application data stream associated with the access node.

56. The method of claim 47, wherein the selection of the at least one mitigation option is conducted if the overall quality metric value stays below the threshold for a minimum time duration.

57. The method of claim 46, wherein the initiation of the at least one mitigation option includes sending a mitigation instruction message to one of the at least one terminal node that is associated with the application data stream on which the mitigation option is to be implemented.

58. The method of claim 57, wherein the mitigation instruction message includes at least one of the overall quality metric value and a time duration that the overall quality metric value has been below a threshold.

59. The method of claim 43, wherein the at least one mitigation option includes one or more of delaying data packets, discarding data packets, delaying acknowledgements, discarding acknowledgements, delaying new data stream initiation requests, discarding new data stream initiation requests, terminating an application, and taking no action.

60. The method of claim 43, wherein the selection of at least one mitigation option associated with one or more of the at least one application data stream is based at least in part on a data stream importance metric for each of the at least one application data stream.

61. The method of claim 46, wherein the selected at least one mitigation option is implemented based on a time duration that the overall quality metric value is below a threshold.

62. The method of claim 46, wherein the selected at least one mitigation option is implemented based on the overall quality metric value.

63. A method for managing application quality in a terminal node within a communication network, the method comprising:

detecting at least one application data stream by monitoring data packets sent to, and received from, an access node in the communication network;

determining, for each of the detected at least one application data stream, application information related to an application operating in the terminal node that is associated with the respective application data stream, the application information including a data stream quality metric for each respective application data stream;

sending, via the communication network, the application information for each of the detected at least one application data stream;

receiving, via the communication network, at least one mitigation instruction associated with one or more of the at least one application data stream; and

implementing the at least one mitigation instruction for the associated one or more of the at least one application data stream.

64. The method of claim 63, wherein the communication network is one of a wireless communication network and a wired communication network.

65. The method of claim 63, wherein the application information for each of the detected at least one application data stream is determined based at least in part on a current terminal node characteristics data set.

66. The method of claim 63, wherein the application information is sent to the access node for transfer from the access node to an application manager node.

67. The method of claim 63, further including the step of classifying one or more of the detected at least one application data stream by inspecting one or more data packets associated with the respective application data stream and assigning an application class value to the application data stream based on the inspection of the one or more data packets, and including the application class value in the application information for the respective application data stream.

68. The method of claim 63, wherein the determination of application information for each application data stream includes determining a data stream importance metric for the application data stream and including the data stream importance metric in the application information for the application data stream.

69. The terminal node of claim 68, further including the step of generating at least one of a current application characteristics data set for each of the at least one application data stream based on current characteristics of an application associated with the respective application data stream, and a current terminal node characteristics data set based on current characteristics of the terminal node.

70. The terminal node of claim 69, wherein the data stream importance metric is based at least in part on the current application characteristics data set and the current terminal node characteristics data set.

71. The terminal node of claim 69, wherein the current application characteristics data set includes at least one or more of an application class value, a stream initiation type value, an update pending value, a display position value, a network quality of service (QoS) value and a buffer margin value.

72. The terminal node of claim 69, wherein the current terminal node characteristics data set includes at least one or more of a user attention value and a service level agreement (SLA) value and a terminal node type.

73. The terminal node of claim 68, wherein the data stream quality metric is based at least in part on an indication of missing or delayed data packets associated with the application data stream.

74. The terminal node of claim 68, wherein the data stream quality metric is based at least in part on an application quality metric value received from the application operating in the terminal node that is associated with the corresponding application data stream.

75. The method of claim 63, wherein the application information for each application data stream includes at least one of an application characteristics data set related to the data stream and a terminal node characteristics data set.

76. The method of claim 63, wherein the application information is sent from the terminal node to the access node on one of a periodic and an aperiodic basis.

77. The method of claim 63, wherein the application information further includes one or more of a terminal node identification associated with the terminal node, a cell identification associated with the access node, and a handover metric value.

78. The method of claim 63, wherein the at least one mitigation instruction includes one or more of a data packet delay instruction, a data packet discard instruction, an acknowledgement delay instruction, an acknowledgement discard instruction, a new data stream request delay instruction, a new data stream request discard instruction, and an application termination instruction.

79. The method of claim 63, wherein the at least one mitigation instruction includes at least one of an overall quality metric value and a time duration for which the overall quality metric value is below a threshold, and wherein the implementation of the at least one mitigation instruction includes determining a mitigation action based on the at least one of the overall quality metric value and the time duration.

80. The method of claim 63, wherein the implementation of the at least one mitigation instruction is based at least in part on a data stream importance metric for each of the at least one application data stream.

81. The terminal node of claim 80, wherein the at least one mitigation instruction is implemented on the application data stream having the lowest data stream importance metric, and is then successively implemented for at least one other application data stream having the next lowest data stream importance metric.

82. The method of claim 63, wherein the at least one mitigation instruction is implemented on an increasing number of the associated application data streams as a time duration of the implementation increases.

83. The method of claim 63, wherein the at least one mitigation instruction is implemented based on a time duration that a quality metric value is below a threshold.

84. The method of claim 63, wherein a level of implementation of the at least one mitigation instruction is based on a quality metric value.