EECS 122: Introduction to Computer Networks Problems with Intserv

Total Page:16

File Type:pdf, Size:1020Kb

EECS 122: Introduction to Computer Networks Problems with Intserv EECS 122: Introduction to Computer Networks Differentiated Services (DiffServ) Computer Science Division Department of Electrical Engineering and Computer Sciences University of California, Berkeley Berkeley, CA 94720-1776 EE122 F05 Problems with IntServ Scalability: per-flow state, classification, etc. - Aggregation/encapsulation techniques can help - Can overprovision big links, per-flow ok on small links - Scalability can be fixed, but no second chance Economic arrangements: - Need sophisticated settlements between ISPs - Right now, settlements are primitive (barter) User charging mechanisms: need QoS pricing EE122 F05 2 1 Differentiated Services (DiffServ) Some traffic should get better treatment - Application requirements: interactive vs. bulk transfer - Economic arrangements: first-class versus coach What kind of better service could you give? - Measured by drops, or delay (and drops) How do you know which packets to give better service? - Bits in packet header EE122 F05 3 DiffServ (cont’d) Build around the concept of domain Domain – a contiguous region of network under the same administrative ownership Differentiate between edge and core routers Edge routers - Perform per aggregate shaping or policing - Mark packets with a small number of bits; each bit encoding represents a class (subclass) Core routers - Process packets based on packet marking Far more scalable than Intserv, but provides weaker services EE122 F05 4 2 Diffserv Architecture Ingress routers - Police/shape traffic - Set Differentiated Service Code Point (DSCP) in Diffserv (DS) field Core routers - Implement Per Hop Behavior (PHB) for each DSCP - Process packets based on DSCP DS-1 DS-2 Ingress Ingress EgressEgress EgressEgress Edge router Core router EE122 F05 5 Traffic Limitations Can’t give all traffic better service! Must limit the amount of traffic that gets better service Service Level Agreements (SLA) - Source agrees to limit amount of traffic in given class - Network agrees to give that traffic “better” service • For a price! - Economics play an important (fatal?) role in QoS EE122 F05 6 3 “Expedited Forwarding” Give packet minimal delay and loss service - E.g., put EF packets in high priority queue To make this a true “absolute” service - All SLAs must sum to less than the link speed EE122 F05 7 Is Delay the Problem? With RED, most queues are small Packets are dropped when queue starts to grow Thus, delays are mostly speed-of-light latency Service quality is mostly expressed by drop-rate Want to give traffic different levels of dropping EE122 F05 8 4 “Assured Forwarding” Packets are all serviced in order - Makes TCP implementations perform well But some packets can be marked as low-drop and others as high-drop - Think of it as priority levels for dropping EE122 F05 9 Example 10% premium traffic, 90% ordinary traffic Overall drop rate is 5% Give premium traffic 0% drops; ordinary traffic a 5.55% drop rate Large improvement in service for the small class of traffic without imposing much of a penalty on the other traffic - Count on SLAs to control premium traffic EE122 F05 10 5 DiffServ “Code Points” Use six of the ToS bits in IP packet header Define various “code points” - Alternative classes of service (drop probability and assured forwarding) Each code point defines a desired per-hop behavior - Description of the service the packet should get - Not a description of the router implementation of that service EE122 F05 11 Differentiated Service (DS) Field 0 5 6 7 DS Filed 0 4 8 16 19 31 Version HLen TOS Length Identification Flags Fragment offset TTL Protocol Header checksum IP Source address header Destination address Data DS filed reuse the first 6 bits from the former Type of Service (TOS) byte The other two bits are proposed to be used by ECN EE122 F05 12 6 DiffServ Code Point Packet Headers 000 Routine 001 Priority 010 Immediate 011 Flash 100 Flash Override 101 Critical 110 Internetwork Control 111 Network Control 4 Classes (e.g., Business, Telecommuter, Residential) plus Low/Medium/High Drop Probability plus Expedited Forwarded (EF) EE122 F05 13 Assured Service [Clark & Wroclawski ‘97] Defined in terms of user profile, how much assured traffic is a user allowed to inject into the network Network: provides a lower loss rate than best-effort - In case of congestion best-effort packets are dropped first User: sends no more assured traffic than its profile - If it sends more, the excess traffic is converted to best- effort EE122 F05 14 7 Assured Service Large spatial granularity service Theoretically, user profile is defined irrespective of destination - All other services we learnt are end-to-end, i.e., we know destination(s) apriori This makes service very useful, but hard to provision (why ?) Traffic profile Ingress EE122 F05 15 Premium Service [Jacobson ’97] Provides the abstraction of a virtual pipe between an ingress and an egress router Network: guarantees that premium packets are not dropped and they experience low delay User: does not send more than the size of the pipe - If it sends more, excess traffic is delayed, and dropped when buffer overflows EE122 F05 16 8 Edge Router Ingress Traffic conditioner Class 1 Marked traffic Traffic conditioner Class 2 Data traffic Classifier Scheduler Best-effort Per aggregate Classification (e.g., user) EE122 F05 17 Assumptions Assume two bits - P-bit denotes premium traffic - A-bit denotes assured traffic Traffic conditioner (TC) implement - Metering - Marking - Shaping EE122 F05 18 9 TC Performing Metering/Marking Used to implement Assured Service In-profile traffic is marked: - A-bit is set in every packet Out-of-profile (excess) traffic is unmarked - A-bit is cleared (if it was previously set) in every packet; this traffic treated as best-effort r bps User profile b bits (token bucket) assured traffic Set A-bit in-profile traffic Metering Clear A-bit out-of-profile traffic EE122 F05 19 TC Performing Metering/Marking/Shaping Used to implement Premium Service In-profile traffic marked: - Set P-bit in each packet Out-of-profile traffic is delayed , and when buffer overflows it is dropped r bps User profile b bits (token bucket) premium traffic Metering/ Shaper/ in-profile traffic Set P-bit out-of-profile traffic (delayed and dropped) EE122 F05 20 10 Scheduler Employed by both edge and core routers For premium service – use strict priority, or weighted fair queuing (WFQ) For assured service – use RIO (RED with In and Out) - Always drop OUT packets first • For OUT measure entire queue • For IN measure only in-profile queue Dropping probability 1 OUT IN Average queue length EE122 F05 21 Scheduler Example Premium traffic sent at high priority Assured and best-effort traffic pass through RIO and then sent at low priority yes P-bit set? high priority no yes A-bit set? no RIO low priority EE122 F05 22 11 Control Path Each domain is assigned a Bandwidth Broker (BB) - Usually, used to perform ingress-egress bandwidth allocation BB is responsible to perform admission control in the entire domain BB not easy to implement - Require complete knowledge about domain - Single point of failure, may be performance bottleneck - Designing BB still a research problem EE122 F05 23 Example Achieve end-to-end bandwidth guarantee 2 3 BBBB BBBB BBBB 7 5 1 9 6 4 8 profile profile profile receiver sender EE122 F05 24 12 Comparison to Best-Effort and Intserv Best-Effort Diffserv Intserv Service Connectivity Per aggregate isolation Per flow isolation No isolation Per aggregate guarantee Per flow guarantee No guarantees Service End-to-end Domain End-to-end scope Complexity No setup Long term setup Per flow steup Scalability Highly scalable Scalable Not scalable (each (nodes maintain (edge routers maintains router maintains only routing state) per aggregate state; core per flow state) routers per class state) EE122 F05 25 Summary Diffserv more scalable than Intserv - Edge routers maintain per aggregate state - Core routers maintain state only for a few traffic classes But, provides weaker services than Intserv, e.g., - Per aggregate bandwidth guarantees (premium service) vs. per flow bandwidth and delay guarantees BB is not an entirely solved problem - Single point of failure - Handle only long term reservations (hours, days) EE122 F05 26 13 Discussion: Factors Limiting QoS Deployment Prevalence of overprovisioning - If all links are only at 40% utilization, why do you need QoS? - The inter-ISP links are not over provisioned Primitive inter-ISP financial arrangements - QoS requires financial incentives to enforce tradeoffs - Current peering arrangements are not able to carry these incentives through in a meaningful way • Must agree on pricing and service • Currently agree on neither! End-users not used to pricing/performance options EE122 F05 27 QoS Debates Is overprovisioning enough? - If so, is this only because access links are slow? - What about Korea, Japan, and other countries with fast access links? - Disconnect: ISPs overprovision, users get bad service Is differentiated services enough? - Can one really deliver reliable service just using relative priorities? - Is EF service a viable option? It all depends on adaptability of applications EE122 F05 28 14 EE122 F05 29 15.
Recommended publications
  • Diffserv -- the Scalable End-To-End Qos Model
    WHITE PAPER DIFFSERV—THE SCALABLE END-TO-END QUALITY OF SERVICE MODEL Last Updated: August 2005 The Internet is changing every aspect of our lives—business, entertainment, education, and more. Businesses use the Internet and Web-related technologies to establish Intranets and Extranets that help streamline business processes and develop new business models. Behind all this success is the underlying fabric of the Internet: the Internet Protocol (IP). IP was designed to provide best-effort service for delivery of data packets and to run across virtually any network transmission media and system platform. The increasing popularity of IP has shifted the paradigm from “IP over everything,” to “everything over IP.” In order to manage the multitude of applications such as streaming video, Voice over IP (VoIP), e-commerce, Enterprise Resource Planning (ERP), and others, a network requires Quality of Service (QoS) in addition to best-effort service. Different applications have varying needs for delay, delay variation (jitter), bandwidth, packet loss, and availability. These parameters form the basis of QoS. The IP network should be designed to provide the requisite QoS to applications. For example, VoIP requires very low jitter, a one-way delay in the order of 150 milliseconds and guaranteed bandwidth in the range of 8Kbps -> 64Kbps, dependent on the codec used. In another example, a file transfer application, based on ftp, does not suffer from jitter, while packet loss will be highly detrimental to the throughput. To facilitate true end-to-end QoS on an IP-network, the Internet Engineering Task Force (IETF) has defined two models: Integrated Services (IntServ) and Differentiated Services (DiffServ).
    [Show full text]
  • Autoqos for Voice Over IP (Voip)
    WHITE PAPER AUTOQoS FOR VOICE OVER IP Last Updated: September 2008 Customer networks exist to service application requirements and end users efficiently. The tremendous growth of the Internet and corporate intranets, the wide variety of new bandwidth-hungry applications, and convergence of data, voice, and video traffic over consolidated IP infrastructures has had a major impact on the ability of networks to provide predictable, measurable, and guaranteed services to these applications. Achieving the required Quality of Service (QoS) through the proper management of network delays, bandwidth requirements, and packet loss parameters, while maintaining simplicity, scalability, and manageability of the network is the fundamental solution to running an infrastructure that serves business applications end-to-end. Cisco IOS ® Software offers a portfolio of QoS features that enable customer networks to address voice, video, and data application requirements, and are extensively deployed by numerous Enterprises and Service Provider networks today. Cisco AutoQoS dramatically simplifies QoS deployment by automating Cisco IOS QoS features for voice traffic in a consistent manner and leveraging the advanced functionality and intelligence of Cisco IOS Software. Figure 1 illustrates how Cisco AutoQoS provides the user a simple, intelligent Command Line Interface (CLI) for enabling campus LAN and WAN QoS for Voice over IP (VoIP) on Cisco switches and routers. The network administrator does not need to possess extensive knowledge of the underlying network
    [Show full text]
  • AES67-101: the Basics of AES67
    AES67-101: The Basics of AES67 Anthony P. Kuzub IP Audio Product Manager [email protected] www.Ward-Beck.Systems TorontoAES.org Vice-Chair Ward-Beck.Systems - Audio Domains PREAMPS.audio FILTERING.audio PATCHING.audio MUTING.audio DB25.audio VUMETERS.audio PANELS.audio MATRIXING.audio BUSSING.audio XLR.audio SUMMING.audio AMPLIFY.audio CONSOLES.audio GROUNDING.audio The least you SHOULD know about networking: The physical datalink networks transported sessions presented by the application TX RX DATA 7 - Application DATA PATCHING.audio AES67.audio MATRIXING.audio 2110-30.AES67.audio 6 - Presentation BUSSING.audio 5 - Session 4 - Transport ROUTING.audio IGMP.audio 3 - Network SWITCHING.audio CLOCKING.audio 2 - Data Link MULTICASTING.audio 1 - Physical RJ45.audio The Road to Incompatibility… Dante RAVENNA QLAN Livewire Control & Monitoring Proprietary HTTP, Ember+ TCP, HTTP HTTP, Proprietary Proprietary Proprietary Discovery Bonjour Proprietary Connection Proprietary RTSP, SIP, IGMP Proprietary Proprietary, HTTP, IGMP Management Session Description Proprietary SDP Proprietary Channel # Transport Proprietary, IPv4 RTP, IPv4 RTP, IPv4 RTP, IPv4 Quality of Service DiffServ DiffServ DiffServ DiffServ/802.1pq Encoding & Streaming L16-32, ≤4 ch/flow L16-32, ≤64 cha/str 32B-FP, ≤16 ch/str L24, st, surr Synchronization PTP1588-2002 PTP1588-2008 PTP1588-2008 Proprietary Media Clock 44.1kHz, 192kHz 44.1kHz – 384kHz 48kHz 48kHz AES67-2013 Standard for audio applications of networks: High-performance streaming audio-over-IP interoperability References
    [Show full text]
  • 5G and Net Neutrality
    University of Pennsylvania Carey Law School Penn Law: Legal Scholarship Repository Faculty Scholarship at Penn Law 2019 5G and Net Neutrality Christopher S. Yoo University of Pennsylvania Carey Law School Jesse Lambert University of Pennsylvania Law School Follow this and additional works at: https://scholarship.law.upenn.edu/faculty_scholarship Part of the Administrative Law Commons, Communication Technology and New Media Commons, European Law Commons, Internet Law Commons, Law and Economics Commons, Science and Technology Law Commons, and the Transnational Law Commons Repository Citation Yoo, Christopher S. and Lambert, Jesse, "5G and Net Neutrality" (2019). Faculty Scholarship at Penn Law. 2089. https://scholarship.law.upenn.edu/faculty_scholarship/2089 This Article is brought to you for free and open access by Penn Law: Legal Scholarship Repository. It has been accepted for inclusion in Faculty Scholarship at Penn Law by an authorized administrator of Penn Law: Legal Scholarship Repository. For more information, please contact [email protected]. 5G and Net Neutrality Christopher S. Yoo† and Jesse Lambert‡ Abstract Industry observers have raised the possibility that European network neutrality regulations may obstruct the deployment of 5G. To assess those claims, this Chapter describes the key technologies likely to be incorporated into 5G, including millimeter wave band radios, massive multiple input/multiple output (MIMO), ultra-densification, multiple radio access technologies (multi-RAT), and support for device-to-device (D2D) and machine-to-machine (M2M) connectivity. It then reviews the business models likely to be associated with 5G, including network management through biasing and blanking, an emphasis on business-to- business (B2B) communications, and network function virtualization/network slicing.
    [Show full text]
  • Net Neutral Quality of Service Differentiation in Flow-Aware Networks
    AGH University of Science and Technology Faculty of Electrical Engineering, Automatics, Computer Science and Electronics Ph.D. Thesis Robert Wójcik Net Neutral Quality of Service Differentiation in Flow-Aware Networks Supervisor: Prof. dr hab. in˙z.Andrzej Jajszczyk AGH University of Science and Technology Faculty of Electrical Engineering, Automatics, Computer Science and Electronics Department of Telecommunications Al. Mickiewicza 30, 30-059 Kraków, Poland tel. +48 12 634 55 82 fax. +48 12 634 23 72 www.agh.edu.pl www.eaie.agh.edu.pl www.kt.agh.edu.pl To my loving wife, Izabela Acknowledgements Many people have helped my throughout the course of my work on this dissertation over the past four years. I would like to express my gratitude to all of them and to a few in particular. First of all, I would like to thank my supervisor, Professor Andrzej Jajszczyk, for his invaluable comments, advice and constant support during my whole research. I am sure that without his patience, broad vision and motivation, completing this dissertation would not have been possible. I have been fortunate to meet James Roberts, the founder of the original con- cept of Flow-Aware Networking, and discuss several issues with. Our joint work on the project concerning FAN architecture was a milestone in my vision of the future Internet and strongly contributed to my understanding of the ideas and problems related to admission control, scheduling and network design. Much of my experience has been formed through the collaboration with Jerzy Domżał, my friend and collegue. His insight and remarks concerning various issues have contributed significantly to the improvement of my results.
    [Show full text]
  • Adding Enhanced Services to the Internet: Lessons from History
    Adding Enhanced Services to the Internet: Lessons from History kc claffy and David D. Clark [email protected] and [email protected] September 7, 2015 Contents 1 Introduction 3 2 Related technical concepts 4 2.1 What does “enhanced services” mean? . 4 2.2 Using enhanced services to mitigate congestion . 5 2.3 Quality of Service (QoS) vs. Quality of Experience (QoE) . 6 2.4 Limiting the use of enhanced services via regulation . 7 3 Early history of enhanced services: technology and operations (1980s) 7 3.1 Early 1980s: Initial specification of Type-of-Service in the Internet Protocol suite . 7 3.2 Mid 1980s: Reactive use of service differentation to mitigate NSFNET congestion . 10 3.3 Late 1980s: TCP protocol algorithmic support for dampening congestion . 10 4 Formalizing support for enhanced services across ISPs (1990s) 11 4.1 Proposed short-term solution: formalize use of IP Precedence field . 11 4.2 Proposed long-term solution: standardizing support for enhanced services . 12 4.3 Standardization of enhanced service in the IETF . 13 4.4 Revealing moments: the greater obstacle is economics not technology . 15 5 Non-technical barriers to enhanced services on the Internet (2000s) 15 5.1Early2000s:afuneralwakeforQoS............................ 15 5.2 Mid 2000s: Working with industry to gain insight . 16 5.3 Late 2000s: QoS becomes a public policy issue . 17 6 Evolving interconnection structure and implications for enhanced services (2010s) 20 6.1 Expansion of network interconnection scale and scope . 20 6.2 Emergence of private IP-based platforms to support enhanced services . 22 6.3 Advancing our empirical understanding of performance impairments .
    [Show full text]
  • Overview on IP Audio Networking Andreas Hildebrand, RAVENNA Evangelist ALC Networx Gmbh, Munich Topics
    Overview on IP Audio Networking Andreas Hildebrand, RAVENNA Evangelist ALC NetworX GmbH, Munich Topics: • Audio networking vs. OSI Layers • Overview on IP audio solutions • AES67 & RAVENNA • Real-world application examples • Brief introduction to SMPTE ST2110 • NMOS • Control protocols Overview on IP Audio Networking - A. Hildebrand # 1 Layer 2 Layer 1 AVB EtherSound Layer 3 Audio over IP Audio over Ethernet ACIP TCP unicast RAVENNA AES67 multicast RTP UDP X192 Media streaming Dante CobraNet Livewire Overview on IP Audio Networking - A. Hildebrand # 3 Layer 2 Layer 1 AVB Terminology oftenEtherSound Layer 3 Audio over IP • ambiguousAudio over Ethernet ACIP TCP unicast • usedRAVENNA in wrongAES67 context multicast RTP • marketingUDP -driven X192 Media streaming • creates confusion Dante CobraNet Livewire Overview on IP Audio Networking - A. Hildebrand # 4 Layer 2 Layer 1 AVB Terminology oftenEtherSound Layer 3 Audio over IP • ambiguousAudio over Ethernet ACIP TCP Audio over IP unicast • usedRAVENNA in wrongAES67 context multicast RTP • marketingUDP -driven X192 Media streaming • creates confusion Dante CobraNet Livewire Overview on IP Audio Networking - A. Hildebrand # 5 Layer 7 Application Application Application and Layer 6 Presentation protocol-based layers Presentation HTTP, FTP, SMNP, Layer 5 Session Session POP3, Telnet, TCP, Layer 4 Transport UDP, RTP Transport Layer 3 Network Internet Protocol (IP) Network Layer 2 Data Link Ethernet, PPP… Data Link Layer 1 Physical 10011101 Physical Overview on IP Audio Networking - A. Hildebrand # 10 Physical transmission Classification by OSI network layer: Layer 1 Systems Transmit Receive Layer 1 Physical 10011101 Physical Overview on IP Audio Networking - A. Hildebrand # 12 Physical transmission Layer 1 systems: • Examples: SuperMac (AES50), A-Net Pro16/64 (Aviom), Rocknet 300 (Riedel), Optocore (Optocore), MediorNet (Riedel) • Fully proprietary systems • Make use of layer 1 physical transport (e.g.
    [Show full text]
  • Differentiated Services and Pricing of the Internet MASSACHUSETTS
    Differentiated Services and Pricing of The Internet by Atanu Mukherjee Submitted to the System Design and Management Program in partial fulfillment of the requirements for the degree of Master of Science in Engineering and Management at the MASSACHUSETTS INSTITUTE OF TECHNOLOGY May 1998 ( Massachusetts Institute of Technology. All rights reserved. Signatureof the Author....... .. -... ............................................... System Design and Management Program May 20l , 1998 Certifiedby...... .... , .............. .......................... ..... ........ Dr. Michael S. Scott Morton Jay W. Forrester Professor of Management, Sloan School of Management Thesis Supervisor Accepted by .............. .............................................. Dr. Thomas A. Kochan George M. B.ker Professor of Management, loan School of Management Co-Director, System Design and Management Program OF TECHXOO, MAY 281M t L.Re6 i COWC'UVE Differentiated Services and Pricing of the Internet by Atanu Mukherjee Submitted to the System Design and Management Program on May 20"', 1998, in partial fulfillment of the requirements for the degree of Master of Science in Engineering and Management Abstract The convergence of communication mediums and the diffusion of the Intemet into the society is blurring the distinction between voice, video and data. The ability to use a single communication infiastructure is very desirable as it brings down the cost of communication while increasing the flexibility of use. However, voice, video and data have different latency and bandwidth requirements. The valying characteristics leads to inconsistent delivery of the traffic streams in the presence of congestion in the network. In a best effort network, the quality of service is unpredictable if the network is overloaded. This thesis analyzes the market and bandwidth characteristics of the Internet and develops a service differentiation model, which provides preferential treatment to traffic streams using statistical drop preferences at the edges.
    [Show full text]
  • Dialogic® Bordernet™ 4000 Session Border Controller Product Description
    Dialogic® BorderNet™ 4000 Session Border Controller Product Description Release 3.4 Dialogic® BorderNet™ 4000 Session Border Controller Product Description Copyright and Legal Notice Copyright © 2012-2016 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation at the address provided below. All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Corporation and its affiliates or subsidiaries (“Dialogic”). Reasonable effort is made to ensure the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY. Dialogic products are not intended for use in certain safety-affecting situations. Please see http://www.dialogic.com/company/terms-of-use.aspx for more details. Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries, and thus may not function properly in other countries.
    [Show full text]
  • Specialized Services and Net Neutrality
    Nokia Government Relations Policy Paper SPECIALIZED SERVICES AND NET NEUTRALITY Nokia Approaches Net Neutrality from a Market Value Perspective The network neutrality discussion remains contentious because some parties frame the issue in inflexible terms. Statements that all packets must receive identical treatment to ensure an open Internet, or that no consumer safeguards are necessary are not likely to facilitate a constructive debate or result in consensus. That is why Nokia views the discussion in more practical terms. Policymakers should seek to: Develop a regulatory framework that will protect consumers and businesses that develop Internet- based applications and services from unreasonable abuse or restrictions on their use of networks. Ensure that the framework also allows network operators sufficient flexibility in pricing and service offerings to fuel innovation. Value creation everywhere in the value chain, from infrastructure vendors and network operators to application makers and consumers is key to driving innovation. Avoiding abstract discussions is a critical component of developing a balanced plan that offers safeguards and innovation opportunities to all stakeholders in the Internet ecosystem. Market Realities Should Frame the Net Neutrality Discussion Mobile operators face an approximately 70 percent year-on-year growth in traffic. At the same time, in many markets the average revenue per user (ARPU) and return on capital employed (ROCEO) by the operators are flat or declining. Investment decisions are more challenging in this type of environment, which is one reason for the flat spending in the infrastructure sector the last few years. Specialized and differentiated services could allow operators to balance investment decisions with revenue expectations through improved monetization of network capacity.
    [Show full text]
  • Oracle Communications IP Service Activator Huawei Cartridge Guide, Release 7.4 E88218-01 Copyright © 2010, 2017, Oracle And/Or Its Affiliates
    Oracle® Communications IP Service Activator Huawei Cartridge Guide Release 7.4 E88218-01 December 2017 This guide provides detailed technical information about the Oracle Communications IP Service Activator Huawei cartridge, including supported features, device configuration, and a sample device configuration. About This Guide This guide consists of the following sections: ■ Cartridge Overview ■ IP Service Activator Huawei Cartridge Features ■ Installing the Cartridge ■ Device Configuration Audience This guide is intended for network managers and technical consultants responsible for implementing IP Service Activator within a network that uses the Huawei routers. Accessing Oracle Communications Documentation IP Service Activator for Oracle Communications documentation and additional Oracle documentation is available from Oracle Help Center: http://docs.oracle.com Related Documents For more information, see the following documents in the IP Service Activator documentation set: ■ See IP Service Activator Installation Guide for system requirements and information on installing, upgrading and uninstalling IP Service Activator. ■ See IP Service Activator System Administrator’s Guide for information and procedures related the duties a system administrator performs in monitoring and managing IP Service Activator. 1 Cartridge Overview IP Service Activator cartridges enable you to support your existing services, emerging services, and business needs. The cartridges operate in conjunction with the IP Service Activator core product. For more information,
    [Show full text]
  • Application Notes
    APPLICATION NOTES NETWORK SWITCH CONFIGURATIONS FOR DANTE & AES67 NETWORK SWITCH CONFIGURATIONS FOR DANTE & AES67 This document aims to provide general recommendations and configurations for network switches to be used with Powersoft amplifiers for Dante and AES67 connectivity, including examples. For remote control and monitoring of amplifiers, any type of network switch running on at least 100 Mbps will be sufficient. However, for transport of audio over IP via Dante or AES67, dedicated network switches and configurations may be necessary. This is specially the case in large and heavily loaded, or mixed, networks (e.g. audio + other data types). General Recommendations for Dante & AES67 For maximum Dante and/or AES67 network reliability, it is recommended that switches be/have: • Rated for gigabit Ethernet – although 100Mbps may be enough for a small and audio-dedicated network, larger and heavier installations may require a switch running on at least 1Gbps. • Non-blocking – in this type of device (almost every switch nowadays), all ports can run at full speed without any loss of data packets. The switch can handle the total bandwidth on all ports, establishing routing to any free output port without interfering with other traffic. • Managed – differently from unmanaged switches (plug-and-play), managed switches offer a series of different options and adjustments, such as the ability to prioritise the transport of certain types of data over others, and creating Virtual Local Area Networks (VLANs), which are particularly importantin mixed networks where audio is combined with other types of data. For small and audio-dedicated networks, unmanaged switches may be sufficient for Dante and AES67 operation.
    [Show full text]