Multi-media quality of service and quality of user experience optimization through voice prioritization

1. A method of communication, comprising:

measuring an available bandwidth of a communications session of a video-call comprising a video component and an audio component;

determining whether the available bandwidth is sufficient to satisfy a video Quality of User Experience (QoE) level for the video component and an audio QoE level for the audio component, the video QoE level and the audio QoE level being determined by measuring at run time data requirements of a multi-media application and dynamically generating the video QoE level and the audio QoE level; and

based on determining that the available bandwidth is not sufficient to satisfy both the video QoE level and the audio QoE level, prioritizing transmission of the audio component over the video component by placing data for the audio component on a dedicated bearer with a highest priority level and placing data for the video component on a second bearer with a lower priority level than the highest priority level.

2. The method of claim 1 , wherein the measuring the available bandwidth comprises: receiving channel information transmitted by an access network carrying the communications session of the video-call.

3. The method of claim 1 , wherein the measuring the available bandwidth comprises: measuring a transmission capacity on a client device used for the video-call.

4. The method of claim 3 , wherein measuring the transmission capacity comprises:

determining a power utilization level;

measuring a physical transmission capacity; and

determining the transmission capacity, by limiting the physical transmission capacity based at least on the power utilization level.

5. The method of claim 1 , wherein the measuring at run time the data requirements of the multi-media application comprises: receiving at a Quality of Service component a message from the multi-media application comprising the data requirements of the multi-media application, the data requirements comprising video data requirements and audio data requirements.

6. The method of claim 1 , further comprising measuring at run time data requirements of at least one non-multi-media application, wherein the video QoE level and the audio QoE level are dynamically generated based at least on a combination of the data requirements of the multi-media application and the data requirements of the at least one non-multi-media application.

7. The method of claim 1 , further comprising placing packet data for non-video-call applications on a bearer with a lower priority level than the dedicated barrier.

8. The method of claim 7 , wherein the data for the video component is placed on a second dedicated bearer with a high priority and the packet data for the non-video-call applications is placed on a separate default bearer with normal priority.

9. The method of claim 1 , wherein the data for the video component and the data for the audio component are placed on separate secondary PDP contexts.

10. The method of claim 6 , wherein the measuring at run time the data requirements of the multi-media application and the data requirements of at least one non-multi-media application further comprises: measuring at a traffic detection component a data packet volume from a transport component, the data packet volume comprising a combination of video data packets and audio data packets from the multi-media application and data packets from the at least one non-multi-media application.

11. The method of claim 7 , wherein the data for the video component and the packet data for the non-video-call applications are both placed on a default bearer with normal priority.

12. The method of claim 1 , wherein the video component comprises packet-switched data and the audio component comprises circuit-switched data.

13. The method of claim 1 , wherein the data for the audio component of the video-call is voice data.

14. The method of claim 1 , wherein a reverse link scheduler in an access network performs scheduling according to the priorities of the dedicated bearer and second bearer.

15. A client device to optimize a video-call, comprising: a processor; a memory communicatively coupled to the processor; a video-call application resident in the memory, executable by the processor; a radio; a classifier component, operably connected to the radio, the classifier component being operable by the processor to subdivide data associated with a video call session into a video data stream and an audio data stream according to a plurality of classification rules resident in the memory; at least one scheduler being operable by the processor to schedule and route the video data stream and the audio data stream by placing the video data stream and the audio data stream into different contexts having different priorities; and a traffic detection component communicatively coupled to the radio, the traffic detection component being configured to measure available bandwidth for a network connection accessible through the radio and to invoke the classifier component when the available bandwidth is insufficient to satisfy a video Quality of User Experience (QoE) level for the video data stream and an audio QoE level for the audio data stream, wherein the video QoE level and the audio QoE level is determined by the video-call application by measuring at run time data requirements of the video-call application and dynamically generating the video QoE level and the audio QoE level.

16. The client device of claim 15 , further comprising a software Quality of Service (QoS) component which is programmatically accessible by the video-call application via an application programming interface (“API”) to invoke the classifier component.

17. The method of claim 7 , wherein the packet data for the non-video-call applications is placed on a primary PDP context.