DOCSLIB.ORG

Fog Protocol and Fogkit: a Json-Based Protocol and Framework for Communication Between Bluetooth-Enabled Wearable Internet of Things Devices

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Fog Protocol and Fogkit: a Json-Based Protocol and Framework for Communication Between Bluetooth-Enabled Wearable Internet of Things Devices FOG PROTOCOL AND FOGKIT: A JSON-BASED PROTOCOL AND FRAMEWORK FOR COMMUNICATION BETWEEN BLUETOOTH-ENABLED WEARABLE INTERNET OF THINGS DEVICES AThesis presented to the Faculty of California Polytechnic State University San Luis Obispo In Partial Fulfillment of the Requirements for the Degree Master of Science in Computer Science by Spencer Lewson June 2015 c 2015 Spencer Lewson ALL RIGHTS RESERVED ii COMMITTEE MEMBERSHIP TITLE: Fog Protocol and FogKit: A JSON-Based Protocol and Framework for Communica- tion Between Bluetooth-Enabled Wearable Internet of Things Devices AUTHOR: Spencer Lewson DATE SUBMITTED: June 2015 COMMITTEE CHAIR: Professor John Bellardo, Ph.D. Department of Computer Science COMMITTEE MEMBER: Professor David Janzen, Ph.D. Department of Computer Science COMMITTEE MEMBER: Professor John Clements, Ph.D. Department of Computer Science iii Abstract Fog Protocol and FogKit: A JSON-Based Protocol and Framework for Communication Between Bluetooth-Enabled Wearable Internet of Things Devices Spencer Lewson Advancements in technology have brought about a wide variety of devices, such as embedded devices with sensors and actuators, personal computers, smart devices, and health devices. Many of these devices are categorized as “wearables,” meaning that they are intended to be carried and used on one’s body. As this category increases in popularity and functionality, developers will need a convenient way for these devices to communicate with each other and store information in a standardized and efficient manner. The Fog protocol and FogKit framework developed and demonstrated for this thesis address these issues by providing a set of powerful features, including data posting, data querying, event notifications, and network status requests. These features are defined as convenient JSON formatted messages which can be communicated between Bluetooth peripherals using an iOS device running FogKit as router and server. iv ACKNOWLEDGMENTS Thanks to: Dr. John Bellardo, my thesis advisor who provided guidance and support • throughout the project Dr. David Janzen, a member of my committee • Dr. John Clements, a member of my committee • Sam, Stephanie, and Michael Lewson, my loving family who o↵ered unending • support Neil Daniels, a friend who provided assistance with the implementation of iOS • technologies Michael DeWitt, a friend who provided feedback on the design and implemen- • tation of the FogKit and Bluetooth technologies v Contents List of Figures x 1 Introduction 1 2 Background 4 2.1 Overview of the Internet of Things . 4 2.1.1 Introduction to the Internet of Things . 4 2.1.2 VisionsoftheInternetofThings . 6 2.1.3 ApplicationsoftheIoT. 8 2.2 Wearable Technology . 9 2.2.1 Single Purpose Devices . 10 2.2.2 Multifunctional Devices . 11 2.2.3 BodyAreaNetworks ....................... 11 2.3 Overview of Bluetooth . 13 2.3.1 AboutBluetooth ......................... 13 2.3.2 Bluetooth Roles . 15 2.3.3 Bluetooth Data Representation . 15 2.3.4 Bluetooth Data Transfer . 18 2.4 OSI7LayerNetworkModel . 18 3 Related Technologies 21 3.1 IoT Stack . 21 3.2 Edge Technology Layer . 23 3.3 AccessGatewayLayer .......................... 23 3.4 Middleware Layer . 23 3.4.1 SensorMetadataAnnotations . 24 vi 3.4.2 ObservationalValueAnnotations . 25 3.5 ApplicationLayer............................. 25 3.6 Protocols . 27 3.6.1 Routing Protocol for Low-Power and Lossy Networks . 27 3.6.2 ConstrainedApplicationProtocol . 29 4 Fog Protocol 35 4.1 Discussion . 35 4.2 IdentificationInformation . 36 4.2.1 ID Attribute . 37 4.2.2 NameAttribute.......................... 37 4.2.3 TypeAttribute .......................... 37 4.2.4 Capabilities Attribute . 38 4.3 NotificationInformation . 38 4.4 MessageHeaderStructure . 38 4.4.1 Source and Destination Attributes . 39 4.4.2 Confirmation Attribute . 39 4.4.3 Message ID and Response Message ID Attriutes . 40 4.4.4 Version Attribute . 40 4.4.5 TypeAttribute .......................... 41 4.5 Event Messages . 41 4.5.1 Event Type Attribute . 42 4.5.2 Context Attributes . 42 4.6 Post Messages . 42 4.6.1 Post Attribute . 43 4.7 Query Messages . 44 4.7.1 SelectAttribute.......................... 45 4.7.2 WhereAttribute ......................... 45 4.7.3 Query Responses . 47 4.7.4 Deleting . 48 4.7.5 Updating ............................. 48 4.8 ACK and Error Messages . 49 vii 4.8.1 ACK . 49 4.8.2 Error . 50 4.9 NetworkStatusRequests. 50 4.9.1 NetworkStatusQueries . 50 4.9.2 Status Responses . 51 4.10 Comparison to Other Protocols . 52 4.10.1 Message Routing . 53 4.10.2 Message Content Complexity . 53 4.10.3 Message Size . 54 5FogKit 55 5.1 Overview . 55 5.2 Framework Design . 57 5.2.1 Central Framework . 57 5.2.2 Peripheral Framework . 60 5.2.3 Shared Code . 61 5.3 Bluetooth GATT Profile . 62 6 Expected Use Cases 64 6.1 Thought Exercises . 65 6.1.1 Wearable Sensing Devices . 65 6.1.2 Wearable Event Device . 70 6.1.3 Wearable System . 71 6.2 Demonstrations . 76 6.2.1 PostApplicationExample . 76 6.2.2 EventApplicationsExample . 79 7 Future Enhancements 83 7.1 Fog Protocol . 83 7.1.1 Value Standardization . 83 7.1.2 Protocol Optimizations . 84 7.1.3 Binary Data Transfer . 84 7.2 FogKit . 84 7.2.1 Security . 84 viii 7.2.2 Background Processing . 85 7.2.3 ImplementationTesting . 85 8 Conclusion 86 Bibliography 89 Appendix A Fog Protocol Keys 93 1IdentityMessages.............................93 2 NewDataNotificationMessage . 93 3 NetworkStatusMessages......................... 94 4 NetworkStatusResponseMessages . 94 5 MessageHeader.............................. 94 6EventMessages..............................95 7PostMessages...............................95 8QueryMessages..............................95 9QueryResponseMessages........................95 ix List of Figures 2.1 TheGartnerHypeCyclechart[35]. 5 2.2 Cisco’s prediction for number of connected devices by 2020[18]. 6 2.3 The three visions of the Internet of Things[6]. 7 2.4 The merits and demerits of di↵erent BAN technologies.[32] . 12 2.5 The characteristics of di↵erent BAN technologies.[32] . 12 2.6 The Core Bluetooth Stack[1] . 14 2.7 The Bluetooth Central and Peripheral[1]. 16 2.8 The Bluetooth GATT Profile. 17 2.9 The OSI 7 Layer Model[7]. 18 3.1 AnInternetofThingsStack[6]. 22 3.2 AScreenshotofanOpenIoTVisualization.. 26 3.3 AnexampleRPLroutingtree[36].. 28 3.4 TheLayeringofCoAP[42].. 31 3.5 Example of reliable transmission[42]. 32 3.6 Example of the requests/response model in CoAP[42]. 33 3.7 TheCoAPMessageFormat.. 33 5.1 The FogKit star topology. 56 5.2 The FogKit layers. 57 5.3 UMLoverviewofFogKitPrototypeFramework. 58 5.4 The GATT profile for a Fog Bluetooth peripheral. 62 x Chapter 1 Introduction The world is currently experiencing an “explosion” of connected devices. Advance- ments in technology and significant decreases in hardware costs have led to the mass adoption of electronic devices, collectively known as the “Internet of Things” (IoT). These IoT devices, which are constantly sensing and generating data, are all inter- connected, allowing them to communicate with each other and make decisions to help improve our lives. There are many visions of the IoT that range from the massive deployment of thou- sands of sensors and actuators to a few smart objects worn on one’s body that com- municate with each other. However, in all of these visions, unique sets of challenges arise that must be overcome. Although the IoT encompasses a wide variety of devices, from laptops and smart phones to embedded chips with sensors and actuators, the majority of them fall in the latter category. This category is characterized by devices that are typically constrained with limited energy and computational power. One class of device in the IoT is commonly referred to as wearable technology. “Wear- ables” include devices that are carried on one’s body, such as smart phones, smart watches, pedometers, and heart rate monitors. These devices often connect to a smartphone via Bluetooth and gather health information and display data or notifi- cations to the wearer[17]. As this category becomes more popular and the function- 1 ality of these devices increases in complexity, it is clear that many of these devices will need an improved protocol to communicate with each other and/or store data externally. Current protocols used in the IoT are designed to face a few key challenges in IoT networks, including efficiency and interoperability. The Internet Engineering Task Force defined the layer 3 and 4 protocols[28], RPL and CoAP, to address these chal- lenges. However, they were designed for massive networks with thousands or millions of nodes[34][42]. These layers and protocol message formats are difficult to work with and have an unnceccessary overhead for small Bluetooth networks used by wearable technology. The Fog protocol and FogKit framework developed for this thesis attempt to address these shortcomings by defining a convenient method of communication that is de- signed specifically for wearable devices operating on Bluetooth networks. This was accomplished by reviewing other protocols and technology, learning from their design decisions, and integrating these lessons into the Fog system. The Fog protocol defines a simple set of messages that are sent from device to device. These messages can be of many types, including event messages notifying a device that an event occurred, post messages that include data for the central device to store, query messages that request data, and more. For developer convenience, messages are transferred from the peripheral to the central device in an easy key-value pairing known as the Javascript Object Notation (JSON) form, and then depending on the destination, routed to the designated device or consumed by the central device itself. The Fog protocol was designed alongside its prototype implementation, FogKit. The purpose of FogKit was to act as a proof-of-concept that guided the direction and features of the Fog protocol. FogKit creates this functionality between an iOS device and multiple Bluetooth devices. In the FogKit model, the iOS device acts as a server that routes communication between the other Bluetooth devices and as an external database to store data from these devices.
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]