neutrality will be sustained if there is no differentia- tion of particular flows or toward concrete source or destination node connected to the Internet networks (e.g. traffic to/from one website should not have priority over traf- fic to/from another website). But network neutrality does not prevent justified traffic management, such as giving certain priority (via appropriate scheduling and buffering schemes in network nodes) to one traffic type over another. One such example is giving certain reasonable priority to conversational voice traffic over Web traffic or email traffic considering the required delay budget for voice, video, Web, email, etc. There is greater satisfaction for end-users from the Internet access services through which all such OTT services are provided. Overall, traffic management for the OTT services is influenced by: the type of Internet traffic, such as voice (requires lower bitrate) or video (requires higher bitrates and it is bursty by nature), or other data such as Web as an example (it has variable bitrates and is bursty by nature); the number of users attached to the broadband/ultra-broadband access network; the deployed network capacity and the possibility to provide the specified aggregate bitrates to end-users (according to the SLA), which is simpler to do in fixed networks and more complex in mobile networks (e.g. due to mobility of users, and dependence on the available bitrates from the distance between the mobile terminals and base stations, as well as the capabilities of mobile user equipment such as supported fre- quency bands or modulation and coding schemes); the capabilities for traffic management and link capacities (on network interfaces) of network nodes such as switches, routers, gateways, base stations (in mobile net- works), etc.; existing business plans of the telecom operator (i.e. ISP) and national legislation and regulation of the Internet access service (e.g. is it network neutral or not, is differen- tiated charging for different OTT services allowed or not