DOCSLIB.ORG

Real-Time Data Distribution Service (DDS)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Real-Time Data Distribution Service (DDS) Introduction to DDS OMG Real-Time Workshop Washington DC July 2008 Gerardo Pardo-Castellote, Ph.D. Co-chair OMG DDS SIG CTO, Real-Time Innovations [email protected] www.rti.com Agenda z Background: Middleware Technologies z Introduction: DDS Model & Applicability z Details: DDS in depth © 2008 RTI - All rights Reserved Introduction: Middleware Technologies z The concept of network middleware z Communications Model z Object Model z Architecture Model z Protocol © 2008 RTI - All rights Reserved With increased complexity… End User Application © 2008 RTI - All rights Reserved With increased complexity… End User Application Network Stack Routing protocols File System Kernel Device Drivers Operating System © 2008 RTI - All rights Reserved With increased complexity… End User Application HTTP Service Mail Service FTP Service Data base Network Stack Routing protocols File System Kernel Device Drivers Operating System © 2008 RTI - All rights Reserved … middleware becomes necessary End User Application Application Server Event Processing Engine Physics Engine Message Service Data base Middleware Graphics Engine HTTP Service Mail Service FTP Service Network Stack Routing protocols File System Kernel Device Drivers Operating System & Pre-Packaged Services © 2008 RTI - All rights Reserved What is network middleware? Middleware = API and service layer above operating system and below “application” code that abstracts common interaction patterns Network Middleware = Most popular class of middleware Middleware used for developing distributed applications Distributed Applications = Those requiring interaction/communication between multiple computers © 2008 RTI - All rights Reserved Network Middleware Examples z DCE/RPC, DCOM, CORBA, ICE z TIBCO, 29 West z JMS, MQ Series, ActiveMQ, SoniqMQ z DDS, RTI DDS, OpenSplice, tao-dds, GigaSpaces z New trend: – Application Servers (WebSphere, WebLogic, JBOSS) – Include network middleware as a component z NOTE: Middleware “packages” are building blocks, not stand-alone applications like… – Skype, gtalk, … – BitTorrent, eMule, … z Why aren’t ‘popular’ consumer applications built on top of middleware? © 2008 RTI - All rights Reserved Historical note: From Telephone to Blogs z Why so many flavors? z Parallels evolution of general communication patterns: – Started with point-to-point connections – Then request-reply services – Then Message Queue Services – Then Publish-Subscribe Services – Then Data-Caching services z Other examples: – FTP, email -> WEB -> Blogs, RSS -> Podcasts © 2008 RTI - All rights Reserved Middleware = Service Model + Protocol z Service model composed of: Communications – Communications model Model – Object Model – Architecture model Object Model z All these interact Architecture Model z The service model and PROTOCOL protocol are also coupled Middleware Protocols cannot be compared in isolation! They must be compared in the context of the service model © 2008 RTI - All rights Reserved Middleware Service Model Service Model = Communications Model + Object Model + Architecture Model z Communications Model: – Abstract model of how applications interact: z Remote Method Invocation z Queue Based, Pub-Sub z Data-Distribution z Replicated Data z Distributed Transactions z Object Model – Middleware entities the application uses to interact with the service: z Queues, Publishers, Domains, Caches, Federations, Remote Objects… z Architecture Model – Centralized, Brokered, Peer-to-Peer © 2008 RTI - All rights Reserved Agenda z The concept of network middleware z Communications Model z Object Model z Architecture Model z Protocol © 2008 RTI - All rights Reserved Communications Model z Abstract model of how applications interact – Remote Method Invocation – Message-Oriented, Queue Based – Pub-Sub Data-Distribution – Replicated Data – Distributed Transactions © 2008 RTI - All rights Reserved Middleware Communication Models Point-to-Point Client-Server Telephone, TCP File systems, Database, RPC, CORBA, DCOM Simple, high-bandwidth Good if information is naturally centralized Leads to stove-pipe systems Single point failure, performance bottlenecks Publish/Subscribe Messaging Replicated Data Magazines, Newspaper, TV Libraries, Distributed databases Excels at many-to-many Excels at data-mining and analysis communication Excels at distributing time-critical information © 2008 RTI - All rights Reserved RMI vs Pub-Sub/Messaging/Data-Distribution z RMI (WebServices, CORBA, DCOM) offer a remote method abstraction – Familiar OO programming model – Results in a tightly-coupled system y Forces synchronous invocations y Imposes global object model y Limited QoS (appearance of local method call) y Lack robustness: cascading points of failure – Typically built on top of TCP: y impacts scalability and time-determinism – Best-suited to smaller, closely-coupled systems Topic/Queue z Pub-Sub (Messaging Data-Distribution) offer a queue- based and/or replicated-data model – Subsystems are decoupled in time, space, and synchronization y Contracts established by verifying QoS compatibility – Supports a variety of transports including multicast UDP – Better suited for high-performance and real-time © 2008 RTI - All rights Reserved Queue versus Pub-Sub z Queue – Message sent to Queue 1 2 3 1 – Multiple readers can read from the queue 2 Queue – Each message is delivered to ONLY one reader z Readers “affect each other” 3 – Apps: z Job Scheduling z Load Balancing z Collaboration z Pub Sub – Message Sent to Topic 1 2 3 – Multiple readers can subscribe to Topic 1 2 3 with or without filters 1 2 3 – Each message delivered to ALL Topic/Queue subscribers that pass filter z Readers are decoupled 1 1 3 – Apps: z Notifications z Information Distribution © 2008 RTI - All rights Reserved Pub-Sub versus Data-Distribution z Pub-Sub – Only messages no concept of data 1 2 3 – Each message is interpreted without 1 2 3 context 1 2 3 – Messages must be delivered FIFO or Topic/Queue according to some “priority” attribute No Caching of data – 1 3 – Simple QoS: filters, durability, lifespan 1 z Data-Distribution – Messages represent update to data-objects – Data-Objects identify by a key – Middleware maintains state of each object 1 2 2 3 – Objects are cached. Applications can read at leisure – Smart QoS z Ownership z History (per key) z Deadline 1 2 3 1 2 3 1 2 3 – Subsumes messaging © 2008 RTI - All rights Reserved Other (non DDS) Commercial Pub-Sub Models z Older, but widely deployed – TIBCO (RendezVous, EMS) – IBM MQSeries z Limited deployment: – CORBA Event Service – CORBA Notification Service z Emerging standards – not really used yet – WS-Eventing – WS-Notification z Emerging – 29West – IBM LLM © 2008 RTI - All rights Reserved JMS/MessageQueue Service Model: Communication Model Provides a “Shared Queue Space” that is accessible to all interested applications. – Message are sent to an Exchange – Each message has an associated Routing Key – Brokers forward messages to one or more Queues based on the Routing Key – Subscriber get messages from named Queues – Only one subscriber can get a given message from each Queue Client Client Pub Sub Queue1 Client E Queue2 Sub Client Pub E Queue3 Client Shared Queue Space Sub © 2008 RTI - All rights Reserved DDS Service Model: Communication Model Provides a “Global Data Space” that is accessible to all interested applications. – Data objects addressed by Domain, Topic and Key – Subscriptions are decoupled from Publications – Contracts established by means of QoS – Automatic discovery and configuration Participant Participant Pub Pub Track,2 Participant Sub Sub Track,1 Track,3 Global Data Space Participant Participant Pub Alarm Sub © 2008 RTI - All rights Reserved MessageQueue Service Model : Object Model Routing key Queue AMPQ? AMPQ? Queue Publisher Exchange Binding Client Subscriber Client Queue Content Broker Server z Exchange – Receives messages and routes to a set of message queues z Queue – Stores messages until they can be processed by the application(s) z Binding – Routes messages between Exchange and Queue. Configured externally to the application – Default binding maps routing-key to Queue name z Routing Key – label used by the exchange to route Content to the queues z Content – Encapsulates application data and provides the methods to send receive, acknowledge, etc. © 2008 RTI - All rights Reserved DDS Service Model: Object Model Topic Topic Data Offered Data Requested Writer QoS Reader QoS Publisher Domain Subscriber Domain Participant Participant Global Data Space z DomainParticipant – Allows application to join a DDS Domain (Global Data Space) z Topic – A string that addresses a group of objects in the Global Data Space – Each Object is identified by a Key (some fields within the object data) z Publisher, Subscriber – Pools resources for DataWriters and DataReaders z DataWriter – Declares intent to publish a Topic and provides type-safe operations to write/send data z DataReader – Declares intent to subscribe to a Topic and provides type-safe operations to read/receive data© 2008 RTI - All rights Reserved Agenda z The concept of network middleware z Communications Model z Object Model z Architecture Model z Protocol © 2008 RTI - All rights Reserved Architecture Models z Brokered – Centralized – Segmented – Federated z Peer to Peer © 2008 RTI - All rights Reserved Centralized Broker Pub-Sub Service One central server materializes all middleware entities All traffic flows via server E.g. “naïve” implementations of JMS, CORBA Notification, etc. Client Application Server Pub-Sub Service
Load more

Recommended publications
  • ISSN: 2320-5407 Int. J. Adv. Res. 5(4), 422-426 RESEARCH ARTICLE
    ISSN: 2320-5407 Int. J. Adv. Res. 5(4), 422-426 Journal Homepage: - www.journalijar.com Article DOI: 10.21474/IJAR01/3826 DOI URL: http://dx.doi.org/10.21474/IJAR01/3826 RESEARCH ARTICLE CHALLENGING ISSUES IN OSI AND TCP/IP MODEL. Dr. J. VijiPriya, Samina and Zahida. College of Computer Science and Engineering, University of Hail, Saudi Arabia. …………………………………………………………………………………………………….... Manuscript Info Abstract ……………………. ……………………………………………………………… Manuscript History A computer network is a connection of network devices to data communication. Multiple networks are connected together to form an Received: 06 February 2017 internetwork. The challenges of Internetworking is interoperating Final Accepted: 05 March 2017 between products from different manufacturers requires consistent Published: April 2017 standards. Network reference models were developed to address these challenges. Two useful reference models are Open System Key words:- Interconnection (OSI) and Transmission Control Protocol and Internet OSI, TCP/IP, Data Communication, Protocol (TCP/IP) serve as protocol architecture details the Protocols, Layers, and Encapsulation communication between applications on network devices. This paper depicts the OSI and TCP/IP models, their issues and comparison of them. Copy Right, IJAR, 2017,. All rights reserved. …………………………………………………………………………………………………….... Introduction:- Network reference models are called protocol architecture in which task of communication can be broken into sub tasks. These tasks are organized into layers representing network services and functions. The layered protocols are rules that govern end-to-end communication between devices. Protocols on each layer will interact with protocols on the above and below layers of it that form a protocol suite or stack. The most established TCP/IP suite was developed by Department of Defence's Project Research Agency DARPA based on OSI suite to the foundation of Internet architecture.
    [Show full text]
  • RT-ROS: a Real-Time ROS Architecture on Multi-Core Processors
    Future Generation Computer Systems 56 (2016) 171–178 Contents lists available at ScienceDirect Future Generation Computer Systems journal homepage: www.elsevier.com/locate/fgcs RT-ROS: A real-time ROS architecture on multi-core processors Hongxing Wei a,1, Zhenzhou Shao b, Zhen Huang a, Renhai Chen d, Yong Guan b, Jindong Tan c,1, Zili Shao d,∗,1 a School of Mechanical Engineering and Automation, Beihang University, Beijing, 100191, PR China b College of Information Engineering, Capital Normal University, Beijing, 100048, PR China c Department of Mechanical, Aerospace, and Biomedical Engineering, The University of Tennessee, Knoxville, TN, 37996-2110, USA d Department of Computing, The Hong Kong Polytechnic University, Hong Kong, China article info a b s t r a c t Article history: ROS, an open-source robot operating system, is widely used and rapidly developed in the robotics Received 6 February 2015 community. However, running on Linux, ROS does not provide real-time guarantees, while real-time tasks Received in revised form are required in many robot applications such as robot motion control. This paper for the first time presents 20 April 2015 a real-time ROS architecture called RT-RTOS on multi-core processors. RT-ROS provides an integrated Accepted 12 May 2015 real-time/non-real-time task execution environment so real-time and non-real-time ROS nodes can be Available online 9 June 2015 separately run on a real-time OS and Linux, respectively, with different processor cores. In such a way, real-time tasks can be supported by real-time ROS nodes on a real-time OS, while non-real-time ROS nodes Keywords: Real-time operating systems on Linux can provide other functions of ROS.
    [Show full text]
  • OSI Model and Network Protocols
    CHAPTER4 FOUR OSI Model and Network Protocols Objectives 1.1 Explain the function of common networking protocols . TCP . FTP . UDP . TCP/IP suite . DHCP . TFTP . DNS . HTTP(S) . ARP . SIP (VoIP) . RTP (VoIP) . SSH . POP3 . NTP . IMAP4 . Telnet . SMTP . SNMP2/3 . ICMP . IGMP . TLS 134 Chapter 4: OSI Model and Network Protocols 4.1 Explain the function of each layer of the OSI model . Layer 1 – physical . Layer 2 – data link . Layer 3 – network . Layer 4 – transport . Layer 5 – session . Layer 6 – presentation . Layer 7 – application What You Need To Know . Identify the seven layers of the OSI model. Identify the function of each layer of the OSI model. Identify the layer at which networking devices function. Identify the function of various networking protocols. Introduction One of the most important networking concepts to understand is the Open Systems Interconnect (OSI) reference model. This conceptual model, created by the International Organization for Standardization (ISO) in 1978 and revised in 1984, describes a network architecture that allows data to be passed between computer systems. This chapter looks at the OSI model and describes how it relates to real-world networking. It also examines how common network devices relate to the OSI model. Even though the OSI model is conceptual, an appreciation of its purpose and function can help you better understand how protocol suites and network architectures work in practical applications. The OSI Seven-Layer Model As shown in Figure 4.1, the OSI reference model is built, bottom to top, in the following order: physical, data link, network, transport, session, presentation, and application.
    [Show full text]
  • Fedramp Master Acronym and Glossary Document
    FedRAMP Master Acronym and Glossary Version 1.6 07/23/2020 i​[email protected] fedramp.gov Master Acronyms and Glossary DOCUMENT REVISION HISTORY Date Version Page(s) Description Author 09/10/2015 1.0 All Initial issue FedRAMP PMO 04/06/2016 1.1 All Addressed minor corrections FedRAMP PMO throughout document 08/30/2016 1.2 All Added Glossary and additional FedRAMP PMO acronyms from all FedRAMP templates and documents 04/06/2017 1.2 Cover Updated FedRAMP logo FedRAMP PMO 11/10/2017 1.3 All Addressed minor corrections FedRAMP PMO throughout document 11/20/2017 1.4 All Updated to latest FedRAMP FedRAMP PMO template format 07/01/2019 1.5 All Updated Glossary and Acronyms FedRAMP PMO list to reflect current FedRAMP template and document terminology 07/01/2020 1.6 All Updated to align with terminology FedRAMP PMO found in current FedRAMP templates and documents fedramp.gov page 1 Master Acronyms and Glossary TABLE OF CONTENTS About This Document 1 Who Should Use This Document 1 How To Contact Us 1 Acronyms 1 Glossary 15 fedramp.gov page 2 Master Acronyms and Glossary About This Document This document provides a list of acronyms used in FedRAMP documents and templates, as well as a glossary. There is nothing to fill out in this document. Who Should Use This Document This document is intended to be used by individuals who use FedRAMP documents and templates. How To Contact Us Questions about FedRAMP, or this document, should be directed to ​[email protected]​. For more information about FedRAMP, visit the website at ​https://www.fedramp.gov​.
    [Show full text]
  • A Comparative Evaluation of OSI and TCP/IP Models
    International Journal of Science and Research (IJSR) ISSN (Online): 2319-7064 Index Copernicus Value (2013): 6.14 | Impact Factor (2013): 4.438 A Comparative Evaluation of OSI and TCP/IP Models P. Ravali Department of Computer Science and Engineering, Amrita Vishwa Vidhyapeetham, Bengaluru Abstract: Networking can be done in a layered manner. To reduce design complexities, network designers organize protocols. Every layer follows a protocol to communicate with the client and the server end systems. There is a piece of layer n in each of the network entities. These pieces communicate with each other by exchanging messages. These messages are called as layer-n protocol data units [n-PDU]. All the processes required for effective communication are addressed and are divided into logical groups called layers. When a communication system is designed in this manner, it is known as layered architecture. The OSI model is a set of guidelines that network designers used to create and implement application that run on a network. It also provides a framework for creating and implementing networking standards, devices, and internetworking schemes. This paper explains the differences between the TCP/IP Model and OSI Reference Model, which comprises of seven layers and five different layers respectively. Each layer has its own responsibilities. The TCP/IP reference model is a solid foundation for all of the communication tasks on the Internet. Keywords: TCP/IP, OSI, Networking 1. Introduction Data formats for data exchange where digital bit strings are exchanged. A collection of autonomous computers interconnected by a Address mapping. single technology is called as computer networks.
    [Show full text]
  • Internet of Things (Iot): Protocols White Paper
    INTERNET OF THINGS (IOT): PROTOCOLS WHITE PAPER 11 December 2020 Version 1 1 Hospitality Technology Next Generation Internet of Things (IoT) Security White Paper 11 December 2020 Version 1 About HTNG Hospitality Technology Next Generation (HTNG) is a non-profit association with a mission to foster, through collaboration and partnership, the development of next-generation systems and solutions that will enable hoteliers and their technology vendors to do business globally in the 21st century. HTNG is recognized as the leading voice of the global hotel community, articulating the technology requirements of hotel companies of all sizes to the vendor community. HTNG facilitate the development of technology models for hospitality that will foster innovation, improve the guest experience, increase the effectiveness and efficiency of hotels, and create a healthy ecosystem of technology suppliers. Copyright 2020, Hospitality Technology Next Generation All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the copyright owner. For any software code contained within this specification, permission is hereby granted, free-of-charge, to any person obtaining a copy of this specification (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the above copyright notice and this permission notice being included in all copies or substantial portions of the Software.
    [Show full text]
  • The OSI Model: Understanding the Seven Layers of Computer Networks
    Expert Reference Series of White Papers The OSI Model: Understanding the Seven Layers of Computer Networks 1-800-COURSES www.globalknowledge.com The OSI Model: Understanding the Seven Layers of Computer Networks Paul Simoneau, Global Knowledge Course Director, Network+, CCNA, CTP Introduction The Open Systems Interconnection (OSI) model is a reference tool for understanding data communications between any two networked systems. It divides the communications processes into seven layers. Each layer both performs specific functions to support the layers above it and offers services to the layers below it. The three lowest layers focus on passing traffic through the network to an end system. The top four layers come into play in the end system to complete the process. This white paper will provide you with an understanding of each of the seven layers, including their functions and their relationships to each other. This will provide you with an overview of the network process, which can then act as a framework for understanding the details of computer networking. Since the discussion of networking often includes talk of “extra layers”, this paper will address these unofficial layers as well. Finally, this paper will draw comparisons between the theoretical OSI model and the functional TCP/IP model. Although TCP/IP has been used for network communications before the adoption of the OSI model, it supports the same functions and features in a differently layered arrangement. An Overview of the OSI Model Copyright ©2006 Global Knowledge Training LLC. All rights reserved. Page 2 A networking model offers a generic means to separate computer networking functions into multiple layers.
    [Show full text]
  • 1.2. OSI Model
    1.2. OSI Model The OSI model classifies and organizes the tasks that hosts perform to prepare data for transport across the network. You should be familiar with the OSI model because it is the most widely used method for understanding and talking about network communications. However, remember that it is only a theoretical model that defines standards for programmers and network administrators, not a model of actual physical layers. Using the OSI model to discuss networking concepts has the following advantages: Provides a common language or reference point between network professionals Divides networking tasks into logical layers for easier comprehension Allows specialization of features at different levels Aids in troubleshooting Promotes standards interoperability between networks and devices Provides modularity in networking features (developers can change features without changing the entire approach) However, you must remember the following limitations of the OSI model: OSI layers are theoretical and do not actually perform real functions. Industry implementations rarely have a layer‐to‐layer correspondence with the OSI layers. Different protocols within the stack perform different functions that help send or receive the overall message. A particular protocol implementation may not represent every OSI layer (or may spread across multiple layers). To help remember the layer names of the OSI model, try the following mnemonic devices: Mnemonic Mnemonic Layer Name (Bottom to top) (Top to bottom) Layer 7 Application Away All Layer 6 Presentation Pizza People Layer 5 Session Sausage Seem Layer 4 Transport Throw To Layer 3 Network Not Need Layer 2 Data Link Do Data Layer 1 Physical Please Processing Have some fun and come up with your own mnemonic for the OSI model, but stick to just one so you don't get confused.
    [Show full text]
  • Resilient Video Coding for Wireless and Peer-To-Peer Networks
    Resilient Video Coding for Wireless and Peer-to-peer Networks Resilient Video Coding for Wireless and Peer-to-peer Networks Proefschrift ter verkrijging van de graad van doctor aan de Technische Universiteit Delft, op gezag van de Rector Magnificus Prof. dr. ir. J. T. Fokkema, voorzitter van het College voor Promoties, in het openbaar te verdedigen op 2 oktober 2007 om 10.00 uur door Jacco Reynoud TAAL elektrotechnisch ingenieur geboren te Rotterdam. Dit proefschrift is goedgekeurd door de promotor: Prof. dr. ir. R. L. Lagendijk Samenstelling promotiecommissie: Rector Magnificus, voorzitter Prof. dr. ir. R. L. Lagendijk, Technische Universiteit Delft, promotor Prof. dr. ir. P. F. A. Van Mieghem Technische Universiteit Delft Prof. dr. ir. H. J. Sips Technische Universiteit Delft Prof. dr. ir. C. H. Slump Universiteit Twente Prof. dr. ir. P. H. N. de With Technische Universiteit Eindhoven Univ.-Prof. Dr.-Ing. Eckehard Steinbach Technische Universität München Dr. A. Reibman AT&T Research A This document is typeset with the LTEX ÑeÑÓiÖ typesetting system. The photo on the cover is taken in April 2006 in the pedestrians tunnel connecting the old and new part of Shanghai. This work was carried out in the ASCI graduate school. ASCI dissertation series number 155 Advanced School for Computing and Imaging ISBN: 978-90-9022238-7 Copyright c 2007 by J. R. Taal All rights reserved. No part of this material may be reproduced or transmitted in any form or by any means, electronic, mechanical, including photocopying, recording or by any information storage and retrieval system, without the prior permission of the copyright owner.
    [Show full text]
  • Physical Interfaces
    N95- 14161 "..,, .....-,, "11.... / "\ RESEARCH & APPLIC_. ONS .Y SYMPOSIUM '92 ""..... A GENERIC ARCHITECTURE MODEL FOR SI CE DATA SYSTEMS RICHARD B. WRA Y ABSTRACT A Space Generic Open Avionics Architecture (SGOAA) was created for the NASA, to be the basis for an open, standard generic architecture for the entities in spacecraft core avionics. Its purpose is to be tailored by NASA to future space program avionics ranging from small vehicles such as Moon Ascent/ Descent Vehicles to large vehicles such as Mars Transfer Vehicles or Orbiting Stations. This architec- ture standard consists of several parts: (1) a system architecture, (2) a generic processing hardware architecture, (3) a six class architecture interface model, (4) a system services functional subsystem architecture model, and (5) an operations control functional subsystem architecture model. This paper describes the SGOAA model. It includes the definition of the key architecture require- ments; the use of standards in designing the architecture; examples of other architecture standards; identification of the SGOAA model; the relationships between the SGOAA, POSIX and OSI models; and the generic system architecture. Then the six classes of the architecture interface model are summarized. Plans for the architecture are reviewed. BIOGRAPHY Richard B. Wray has a dual MS/MBA in Systems Management, Acquisition, and Contracting; a MBA with Distinction Honors in General Management; a MS in Systems Engineering and a BS in Math- ematics. He is the Vice President-Technical of the National Council on Systems Engineering (NCoSE) Texas Gulf Coast Chapter, and Chairman of the NCoSE Systems Engineering Process Working Group to define a nationally recognized systems engineering process.
    [Show full text]
  • Qoe-Aware Cross-Layer Architecture for Video Traffic Over Internet
    Published in: 2014 IEEE REGION 10 SYMPOSIUM. Date Added to IEEE Xplore: 24 July 2014. Date of Conference: 14-16 April 2014 c 2014 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. DOI: 10.1109/TENCONSpring.2014.6863089 QoE-Aware Cross-Layer Architecture for Video Traffic over Internet Safeen Qadir1, Alexander A. Kist1 and Zhongwei Zhang2 1 School of Mechanical and Electrical Engineering fsafeen.qadir, [email protected] 2 School of Agricultural, Computational and Environmental Sciences [email protected] University of Southern Queensland, Australia Abstract—The emergence of video applications and video new mechanisms recommending video rate adaptation towards capable devices have contributed substantially to the increase of delivering enhanced Quality of Experience (QoE) at the same video traffic on Internet. New mechanisms recommending video time making room for more sessions. rate adaptation towards delivering enhanced Quality of Experi- ence (QoE) at the same time making room for more sessions. This The massive demand for video anytime and anywhere has paper introduces a cross-layer QoE-aware architecture for video led to the development of adaptive streaming solutions that are traffic over the Internet. It proposes that video sources at the able to deliver video with a maintained QoE. QoE is a measure application layer adapt their rate to the network environment of the user perceived quality of a network service.
    [Show full text]
  • ISO Reference Model for Open Systems Interconnection (OSI)
    DATA PRO Data Networking 2783 1 Standards ISO Reference Model for Open Systems Interconnection (OSI) In this report: Datapro Summary OSI Standards Progress ..... 6 The goal of Open Systems Interconnection (OS!) was designed to enable dissimilar com­ puters in multivendor environments to share information transparently. The OSI structure OSI Management ................ 8 calls for cooperation among systems of different manufacture and design. There are seven layers of the OSI model that communicate between one end system and another. The layers OSI and the Future •....••....•.. 9 cover nearly all aspects of information flow, from applications-related services provided at the Application Layer to the physical connection of devices to the communications medium Note: This report ex­ at the Physical Layer. All seven layers have long since been defmed and ISO protocols plains the OSI Seven­ ratified for each layer, though extensions have been made occasionally. Although the model Layer Reference Model at has changed the way we look at networking, the dream of complete OSI-compliance has not all layers; compares OSI come to fruition. The causes are varied, but this is essentially because OSI protocols are too to other architectures; expensive and too complex compared with other protocols that have become de facto stan­ rationalizes the need for dards in their own right. Even so, it is important to understand the model because, although standards testing and veri­ the complete stack of protocols is not much used today, the model has formed the way we fication; examines the case for OSI; profiles think of the structure of networks, and the model itself is always referred to in intemetwork­ major testing organiza­ ing matters.
    [Show full text]