230 likes | 407 Views
Quality of Service in the Future Internet. ITU-T Kaleidoscope 2010 Beyond the Internet? - Innovations for future networks and services. J. Carapinha, R. Bless, C. Werle, V. Dobrota, A. Rus, H. Grob-Lipski, K. Miller, H. Roessler. The changing scenario of QoS. New challenges ahead:
E N D
Quality of Service in theFuture Internet ITU-T Kaleidoscope 2010Beyond the Internet? - Innovations for future networks and services J. Carapinha, R. Bless, C. Werle, V. Dobrota, A. Rus, H. Grob-Lipski, K. Miller, H. Roessler
The changing scenario of QoS • New challenges ahead: • Pervasive network-based applications – ever-increasing number of applications rely on the network • More stringent requirements – predictability, flexibility, adaptability, scalability • Increasingly dynamic network environment • Challenges call for fresh approaches
The 4WARD projecthttp://www.4ward-project.eu/ • Innovations based on a “clean slate” design and new network paradigms • Project ran from January’08 to June’10 • Holistic approach to shape the “Future Internet” towards a consistent design to satisfy requirements beyond 2015.
Evaluating the impact on QoS • Three concepts developed and studied by 4WARD are assessed from the point of view of potential impact on QoS: • Network Virtualization • Generic Path Semantic Resource Management • In-Network Management
Network Virtualization Business Model Virtual Network Operator Virtual Network Provider Infrastructure Provider A Infrastructure Provider B Infrastructure Provider C Deployment Scenario 5
Layered QoS • QoS provided by the Substrate • for isolation of different virtual networks • for creating virtual nodes and links with deterministic virtual resource capacities • QoS provided inside the Virtual Network • based on substrate QoS • homogeneous QoS solution inside possible • end-to-end QoS depends on the protocols and mechanisms inside the Virtual Network 6
QoS and Network Virtualization • Network Virtualization needs QoS support in the substrate • To become an attractive solution to deploy new innovative network architectures • Atop, new innovative QoS solutions and services can be rolled out and tested • But at a cost • Increased management overhead • Difficult monitoring / accountability • Standardization of interfaces, also with regard to QoS is required 7
Definition of INM • In-Network Management (INM) = embedding management intelligence in the network, enabled through decentralization, self-organization, embedding of functionality and autonomy. • Self-Managing Entity (SE) = a component of a system that is self managed by objective and can autonomously perform a series of management-related tasks, e.g. self-configuration and self-healing. • INM is characterized by: • SEs are envisaged to run in all network nodes. • A dedicated SE implementing QoS-specific tasks is also required
Self-Managing Entity Characteristics • Any Self-Managing Entity (SE) includes two types of communication interfaces: • The organizational interface (ORG) is used by a manager or another entity to send high level commands to a specific INM entity. • The collaboration interface (COLL) is dedicated to facilitate the communication between two management entities residing either in the same or in different nodes
INM Cross-Layer QoS • The INM Cross-Layer is a SE entity dedicated to perform QoS related tasks: • Accesses the hardware directly, through the collaboration interface • Uses two approaches when exchanging QoS information: • Bottom-up approach: will enable collecting traffic parameters like: ATR, OWD, BER, and other information that is able to characterize a specific physical link. This is an objective way of evaluating a communication channel. • Top-down approach: will impose a specific set of commited QoS parameters to the hardware using the collaboration interface.
INM Cross-Layer QoS interactions Interaction between INM Cross-Layer QoS, INM Composite Metric, hardware and other managed entities
INM Composite Metric Calculation • An immediate example of INM CLQ’s beneficiary would be the real-time composite metric calculation. • The preliminary formula used for an overall perspective of the links with the neighbors (for hop-by-hop data transport) is: • where k0 = 109 [bps], k1 = 10-5 [s] and k2 = 0 (additional tests should be performed to tune the k2 parameter). • This CM could help the management as criteria for triggering network-coding based GP activation, QoS-aware routing, etc.
INM Cross-Layer QoS and Network Coding QoS management element (specialized software) -> collects information about available resources in each strategic node (i.e. a node that includes GP). -> monitors the substrate resources between the neighboring nodes available transfer rates one-way delays -> assists congestion control mechanisms to get a global perspective and to have statistics on link status
Generic Path • New “clean slate” Internet architecture • for highly dynamic and mobile networks • between two or more end systems • leverages multiple routes, network coding, etc. • adapts transport and QoS procedures to the underlying network • Overcomes the inflexibility of the OSI model by introducing recursiveness Pune, India, 13 – 15 Dec 2010: ITU-T Kaleidoscope 2010 – Beyond the Internet? Innovations for future networks and services 14
Generic Path architecture • Much richer class of data flows, beyond TCP, UDP • State within the network, as necessary but no more than necessary • Common management interfaces, to set up and tear down flows and to query their status • Explicit identification, notably to facilitate control of multi-flow applications like videoconferencing • Mechanisms for assured performance and efficient operation • to exploit techniques like network coding and cooperative transmission • to choose the "best" paths for the considered transport • to ensure resource sharing is "fair" and meets application requirements • to manage the mobility of users, networks and information merge/ network code decode split/ balance code cooperatively join Generic path 1 Generic path 2 Pune, India, 13 – 15 Dec 2010: ITU-T Kaleidoscope 2010 – Beyond the Internet? Innovations for future networks and services 15
Generic Path Functional Architecture • Basic building blocks for IPC: • Compartment • Name space+admin border • Hooks (ports) • Entity=process of some form in an OS • Contains functional blocks • Base class with methods for • Management • Access control / name resolution • Reporting and management • Control • Resource management • Routing and mobility support • Endpoint = process in the data plane • Controlled by Entity, performs • Error, flow control • Mux/demux, forwarding Node compartment Compartment A (e.g., TCP/IP) Entity Endpoint Compartment B (e.g., LAN) Entity Endpoint 16
Generic Path Functional Architecture • The generic path is the base-class of a hierarchy of objectsequipped with basic functions common to all path types • All data transfer functionality is defined in derived classes • Error and flow control is specified in derived classes • Path instances are created using a “path factory” Generic Path multipt to multipt pt to multipt pt to pt torrent file transfer voice Pune, India, 13 – 15 Dec 2010: ITU-T Kaleidoscope 2010 – Beyond the Internet? Innovations for future networks and services 17
Advertising of Network Resource Information Principle: Provide GP level-specific network resource information, e.g. congestion etc. Resource advertising starts from the bottom-most ResourceObject GP-level (real physical resources) to vertical and horizontal adjacencies. The advertising process leads to an aggregation and/or concatenation of different and possibly heterogeneous ResourceObjects at GP-level (n-1), which results in a more abstract GP-level specific representation of the ResourceObject at GP-level(n) Aggregation, concatenation and abstraction are supported by the network resource ontology, e.g. by metrics or conversion formula. At run time the advertising is scalable as the process is limited to the set of end points (ep), which already carry flows. The initialization process of the advertising functionality with resource information is performed in the network management plane during network or cloud setup. 4 4 5 5 ep 1 1 1 1 3 3 3 ep_A ep_G 3 2 2 2 2 5 5 4 4 1 1 1 1 1 1 5 5 4 4 3 3 2 2 ep_H 4 4 ep_B ep_E 3 3 2 2 3 3 2 2 3 3 2 2 1 1 1 1 1 1 1 1 2 2 ep_J 1 1 3 3 ResourceObject ResourceObject ep_D 3 3 1 1 2 2 2 2 ep_I ep_K 3 3 2 2 1 1 2 2 1 1 ep_C ep_F node_CTC node_CTC node_CTA node_CTA node_CTB node_CTB Pune, India, 13 – 15 Dec 2010: ITU-T Kaleidoscope 2010 – Beyond the Internet? Innovations for future networks and services 18
Resource Management based on Ontologies • Network Resource Ontology providing the generic representation of the network resource information based on the main classes • Network Resource Parameter • Metric • ConversionFormula • Impact • Type • Aggregated • Relationship Pune, India, 13 – 15 Dec 2010: ITU-T Kaleidoscope 2010 – Beyond the Internet? Innovations for future networks and services 19
Resource Management based on OntologiesBenefits • Extends existing QoS and service ontologies • Bridges the network resource and service semantics • Increases the interoperability in heterogeneous networks • provides useful conceptualizations of different technology specific network resources • Aids to aggregate different network resource types • enables E2E network resource provisioning • Enables to solve mismatches • Non-functional description of network resource characteristics • Defines a machine understandable network resource vocabulary Pune, India, 13 – 15 Dec 2010: ITU-T Kaleidoscope 2010 – Beyond the Internet? Innovations for future networks and services 20
Conclusions • QoS will constitute a crucial requirement for the networks of the future; however, QoS challenges and respective solutions will not remain unchanged; • 4WARD proposed and explored novel networking approaches for the Internet of the future, including: • Network Virtualization • In-Network Management • Generic Path Semantic Resource Management • Each of these approaches brings fresh ideas and potential solutions to handle QoS, particularly taking into account requirements of dynamicity, flexibility, adaptability and scalability.