Scalable Streaming Multimedia Delivery Using Peer-To-Peer Communication

Total Page:16

File Type:pdf, Size:1020Kb

Scalable Streaming Multimedia Delivery Using Peer-To-Peer Communication Downloaded from orbit.dtu.dk on: Oct 06, 2021 Scalable Streaming Multimedia Delivery using Peer-to-Peer Communication Poderys, Justas Publication date: 2019 Document Version Publisher's PDF, also known as Version of record Link back to DTU Orbit Citation (APA): Poderys, J. (2019). Scalable Streaming Multimedia Delivery using Peer-to-Peer Communication. Technical University of Denmarik. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. Users may download and print one copy of any publication from the public portal for the purpose of private study or research. You may not further distribute the material or use it for any profit-making activity or commercial gain You may freely distribute the URL identifying the publication in the public portal If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. PhD Thesis DRAFT Scalable Streaming Multimedia Delivery using Peer- to-Peer Communication Justas Poderys Supervised by: Jose Soler, PhD, and Prof. Lars Dittmann, PhD Technical University of Denmark Kgs. Lyngby, Denmark 2018 Cover image: c hermione13 / 123RF Stock Photo. Print license acquired. Technical University of Denmark Department Photonics Engineering Ørsteds Plads 343 2800 Kgs. Lyngby DENMARK Tel: (+45) 45 25 63 52 Fax: (+45) 45 93 65 81 Web: fotonik.dtu.dk E-mail: [email protected] Contents Abstract vii Resumé ix Preface xi Acknowledgments xiii List of Publications xv List of Figures xvii List of Tables xxi Glossary xxiii 1 Introduction 1 1.1 Thesis Organization .......................... 2 2 One-to-Many Communication 5 2.1 Network-Layer Multicast Communication .............. 6 2.2 Application Layer Multicasting .................... 8 2.3 Application Layer Multicast Protocols Operation .......... 18 2.4 Summary ................................ 27 3 Peer-to-Peer Client Structure 29 3.1 Peer-to-Peer Streaming Software Client Structure ........ 30 3.2 Tracker Interface ............................ 30 3.3 Peer Information ............................ 31 3.4 Data Storage .............................. 31 3.5 Data Requesting ............................ 32 3.6 Data Sending ............................. 32 iii iv Contents 3.7 Flow Control .............................. 33 3.8 Data Receiving ............................ 33 3.9 Multimedia Streaming ......................... 34 3.10 Multimedia Streaming Quality-of-Service Parameters ...... 39 3.11 Summary ................................ 41 4 Dataplane Congestion Control 43 4.1 Related work .............................. 44 4.2 LEDBAT Protocol ........................... 45 4.3 Experimental LEDBAT Parameters Investigation ......... 47 4.4 Using Boosted LEDBAT with PPSPP ................ 51 4.5 Integration Results .......................... 53 4.6 Summary and Discussion ...................... 55 5 Data-Requesting Algorithms 57 5.1 Requesting Algorithms in Literature ................. 57 5.2 Data-Requesting Algorithm ..................... 59 5.3 Experimental Algorithm Evaluation ................. 61 5.4 Summary ................................ 66 6 External Peers Ranking 67 6.1 Methods of evaluating nodes in the Internet ............ 68 6.2 Introduction to the ALTO Protocol .................. 72 6.3 ALTO Data-routing Cost Metrics ................... 74 6.4 ALTO Server and Experimental Setup ............... 78 6.5 Experimental Results ......................... 82 6.6 Summary ................................ 85 7 P2P Communication Over Wireless Connections 89 7.1 Wi-Fi Peer-to-Peer .......................... 90 7.2 Adapting PPSPP for streaming over Wi-Fi P2P .......... 92 7.3 PPSPP Protocol Changes ...................... 93 7.4 Feasibility study ............................ 95 7.5 Experimental Setup .......................... 97 7.6 Evaluation Results – Start-up Time ................. 98 7.7 Evaluation Results – Playback Continuity ............. 100 7.8 In-train Multimedia Streaming .................... 101 7.9 In-train Streaming Experiment Setup ................ 103 7.10 In-train Streaming – Start-up Time ................. 104 7.11 In-train Streaming - Playback Continuity .............. 106 7.12 Summary ................................ 106 Contents v 8 P2P Communication in the Long Term Evolution Networks 109 8.1 LTE Networks Primer ......................... 109 8.2 Edge Caching in the Literature ................... 111 8.3 Edge Caching Proposal ....................... 112 8.4 Performance Evaluation ....................... 115 8.5 Extending Edge-caching Solution for P2P Communication ... 117 8.6 P2P Solution Experimental Evaluation ............... 120 8.7 Conclusions .............................. 121 9 Work Summary and Future Outlook 123 A PPSPP Messages 127 A.1 Handshake procedure ........................ 127 A.2 Data requesting and exchange ................... 128 A.3 Peers information requesting and exchange ............ 129 B TCP Congestion Control Mechanism 131 Combined Bibliography 133 vi Abstract Peer-to-Peer (P2P) refers to a communication paradigm, where each communication peer can act as a client and as a server. In P2P communication, information is disseminated from an information source to all the clients. At the same time, as information is stored in the client’s device, the clients become an information source to other clients as well. The origins of modern P2P communication are closely linked to file distribution. The first P2P communication programs that were widely adopted were used primarily to share non-streaming data, such as music recordings, films, games, and computer programs. However, with streaming multimedia gaining a larger and larger share of the global Internet data traffic (soon envisioned to reach 80%), P2P communication is seen as a viable method to reduce the communication load on the streaming multimedia servers. By employing P2P communication along with distributed multimedia content delivery networks (CDN), high-quality multimedia data can be delivered to a larger number of users using the same amount of servers infrastructure. This thesis investigates how P2P communication can be used to distribute streaming multimedia among multiple users. Specifically, it investigates how different algorithms, running in the Peer-to-Peer Streaming Peer Protocol (PPSPP) client, impact the start- up time and playback continuity of multimedia streams. As P2P communication is a cooperative process, this thesis investigates how requests for outstanding data should be divided among the connected peers to achieve high streaming continuity. During P2P multimedia streaming, in addition to receiving data from a multimedia server, clients also receive data from other peers. This thesis investigates how the Low Extra Delay Background Transport (LEDBAT) protocol can be tuned for use with P2P multimedia streaming while at the same time ensuring that the Internet connections of the connected peers are not congested. This thesis also presents ways to integrate P2P multimedia streaming with communication peers ranking provided by the Application Layer Traffic Optimization (ALTO) protocol. The final two chapters of this thesis are dedicated to performance measurement of P2P multimedia streaming over different wireless communication technologies. This work investigates how P2P multimedia streaming can be performed over the Wi-Fi Peer-to-Peer connections. It also investigates methods of placing multimedia caches in the Long Term Evolution (LTE) network base-stations, along with possibilities of implementing vii viii Abstract Peer-to-Peer communication using the same LTE infrastructure. Resumé Peer-to-Peer (P2P) henviser til et kommunikations paradigme, hvor hver kommunikations deltager kan opføre sig som en klient eller en server. I P2P kommunikation bliver informationen spredt ud fra en informations kilde til alle klienter. På samme tid, fordi informationen er gemt i klientens enhed, vil klienterne blive informationskilder til andre klienter. Oprindelsen af moderne P2P kommunikation er tæt forbundet med fildistribution. Først blev de vidt udbredte P2P kommunikationsprogrammer primært brugt til at dele ikke- streaming data, som for eksempel musik, optagelser, film, spil og computerprogrammer. Men fordi streaming multimedier optager en større og større del af den globale internetdata trafik (forudsagt til at nå 80%), bliver P2P kommunikation set som en realistisk metode til at reducere kommunikationsmængden på streaming multimedie serverne. Ved at benytte P2P kommunikation sammen med distribuerede multimedie Content Delivery Networks (CDN), kan multimediedata af høj kvalitet sendes ud til et større antal brugere, når der bruges den samme størrelse serverinfrastruktur. Denne afhandling undersøger hvordan P2P kommunikation kan bruges til at dis- tribuere streaming multimedier blandt et større antal brugere. Specifikt undersøges hvordan forskellige algoritmer, som kører Peer-to-Peer Streaming Peer Protocol (PPSPP) klienten, påvirker opstartstiden og playback kontinuiteten af multimedie strømme. P2P kommunikation er en samarbejdende proces, derfor undersøger denne afhandling hvordan forespørgsler fra udefrakommende data skal opdeles blandt de forbundne deltagere, for at opnå en høj streaming kontinuitet. Under en P2P multimedie streaming modtager
Recommended publications
  • Data Link Layer
    Data link layer Goals: ❒ Principles behind data link layer services ❍ Error detection, correction ❍ Sharing a broadcast channel: Multiple access ❍ Link layer addressing ❍ Reliable data transfer, flow control: Done! ❒ Example link layer technology: Ethernet Link layer services Framing and link access ❍ Encapsulate datagram: Frame adds header, trailer ❍ Channel access – if shared medium ❍ Frame headers use ‘physical addresses’ = “MAC” to identify source and destination • Different from IP address! Reliable delivery (between adjacent nodes) ❍ Seldom used on low bit error links (fiber optic, co-axial cable and some twisted pairs) ❍ Sometimes used on high error rate links (e.g., wireless links) Link layer services (2.) Flow Control ❍ Pacing between sending and receiving nodes Error Detection ❍ Errors are caused by signal attenuation and noise. ❍ Receiver detects presence of errors signals sender for retrans. or drops frame Error Correction ❍ Receiver identifies and corrects bit error(s) without resorting to retransmission Half-duplex and full-duplex ❍ With half duplex, nodes at both ends of link can transmit, but not at same time Multiple access links / protocols Two types of “links”: ❒ Point-to-point ❍ PPP for dial-up access ❍ Point-to-point link between Ethernet switch and host ❒ Broadcast (shared wire or medium) ❍ Traditional Ethernet ❍ Upstream HFC ❍ 802.11 wireless LAN MAC protocols: Three broad classes ❒ Channel Partitioning ❍ Divide channel into smaller “pieces” (time slots, frequency) ❍ Allocate piece to node for exclusive use ❒ Random
    [Show full text]
  • Simulacijski Alati I Njihova Ograničenja Pri Analizi I Unapređenju Rada Mreža Istovrsnih Entiteta
    SVEUČILIŠTE U ZAGREBU FAKULTET ORGANIZACIJE I INFORMATIKE VARAŽDIN Tedo Vrbanec SIMULACIJSKI ALATI I NJIHOVA OGRANIČENJA PRI ANALIZI I UNAPREĐENJU RADA MREŽA ISTOVRSNIH ENTITETA MAGISTARSKI RAD Varaždin, 2010. PODACI O MAGISTARSKOM RADU I. AUTOR Ime i prezime Tedo Vrbanec Datum i mjesto rođenja 7. travanj 1969., Čakovec Naziv fakulteta i datum diplomiranja Fakultet organizacije i informatike, 10. listopad 2001. Sadašnje zaposlenje Učiteljski fakultet Zagreb – Odsjek u Čakovcu II. MAGISTARSKI RAD Simulacijski alati i njihova ograničenja pri analizi i Naslov unapređenju rada mreža istovrsnih entiteta Broj stranica, slika, tablica, priloga, XIV + 181 + XXXVIII stranica, 53 slike, 18 tablica, 3 bibliografskih podataka priloga, 288 bibliografskih podataka Znanstveno područje, smjer i disciplina iz koje Područje: Informacijske znanosti je postignut akademski stupanj Smjer: Informacijski sustavi Mentor Prof. dr. sc. Željko Hutinski Sumentor Prof. dr. sc. Vesna Dušak Fakultet na kojem je rad obranjen Fakultet organizacije i informatike Varaždin Oznaka i redni broj rada III. OCJENA I OBRANA Datum prihvaćanja teme od Znanstveno- 17. lipanj 2008. nastavnog vijeća Datum predaje rada 9. travanj 2010. Datum sjednice ZNV-a na kojoj je prihvaćena 18. svibanj 2010. pozitivna ocjena rada Prof. dr. sc. Neven Vrček, predsjednik Sastav Povjerenstva koje je rad ocijenilo Prof. dr. sc. Željko Hutinski, mentor Prof. dr. sc. Vesna Dušak, sumentor Datum obrane rada 1. lipanj 2010. Prof. dr. sc. Neven Vrček, predsjednik Sastav Povjerenstva pred kojim je rad obranjen Prof. dr. sc. Željko Hutinski, mentor Prof. dr. sc. Vesna Dušak, sumentor Datum promocije SVEUČILIŠTE U ZAGREBU FAKULTET ORGANIZACIJE I INFORMATIKE VARAŽDIN POSLIJEDIPLOMSKI ZNANSTVENI STUDIJ INFORMACIJSKIH ZNANOSTI SMJER STUDIJA: INFORMACIJSKI SUSTAVI Tedo Vrbanec Broj indeksa: P-802/2001 SIMULACIJSKI ALATI I NJIHOVA OGRANIČENJA PRI ANALIZI I UNAPREĐENJU RADA MREŽA ISTOVRSNIH ENTITETA MAGISTARSKI RAD Mentor: Prof.
    [Show full text]
  • Understanding Linux Internetworking
    White Paper by David Davis, ActualTech Media Understanding Linux Internetworking In this Paper Introduction Layer 2 vs. Layer 3 Internetworking................ 2 The Internet: the largest internetwork ever created. In fact, the Layer 2 Internetworking on term Internet (with a capital I) is just a shortened version of the Linux Systems ............................................... 3 term internetwork, which means multiple networks connected Bridging ......................................................... 3 together. Most companies create some form of internetwork when they connect their local-area network (LAN) to a wide area Spanning Tree ............................................... 4 network (WAN). For IP packets to be delivered from one Layer 3 Internetworking View on network to another network, IP routing is used — typically in Linux Systems ............................................... 5 conjunction with dynamic routing protocols such as OSPF or BGP. You c an e as i l y use Linux as an internetworking device and Neighbor Table .............................................. 5 connect hosts together on local networks and connect local IP Routing ..................................................... 6 networks together and to the Internet. Virtual LANs (VLANs) ..................................... 7 Here’s what you’ll learn in this paper: Overlay Networks with VXLAN ....................... 9 • The differences between layer 2 and layer 3 internetworking In Summary ................................................. 10 • How to configure IP routing and bridging in Linux Appendix A: The Basics of TCP/IP Addresses ....................................... 11 • How to configure advanced Linux internetworking, such as VLANs, VXLAN, and network packet filtering Appendix B: The OSI Model......................... 12 To create an internetwork, you need to understand layer 2 and layer 3 internetworking, MAC addresses, bridging, routing, ACLs, VLANs, and VXLAN. We’ve got a lot to cover, so let’s get started! Understanding Linux Internetworking 1 Layer 2 vs.
    [Show full text]
  • Linux Networking Cookbook.Pdf
    Linux Networking Cookbook ™ Carla Schroder Beijing • Cambridge • Farnham • Köln • Paris • Sebastopol • Taipei • Tokyo Linux Networking Cookbook™ by Carla Schroder Copyright © 2008 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mike Loukides Indexer: John Bickelhaupt Production Editor: Sumita Mukherji Cover Designer: Karen Montgomery Copyeditor: Derek Di Matteo Interior Designer: David Futato Proofreader: Sumita Mukherji Illustrator: Jessamyn Read Printing History: November 2007: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. The Cookbook series designations, Linux Networking Cookbook, the image of a female blacksmith, and related trade dress are trademarks of O’Reilly Media, Inc. Java™ is a trademark of Sun Microsystems, Inc. .NET is a registered trademark of Microsoft Corporation. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
    [Show full text]
  • Virtual Private Network: an Overview Type of Virtual Private Network
    Virtual Private Network : Layer 2 Solution Giorgio Sadolfo [email protected] What is virtual private network? • A virtual private network (VPN) allows the provisioning of private network services for an organization or organizations over a public or shared infrastructure such as the Internet or service provider backbone network (Cisco). Virtual Private Network: An Overview Type of virtual private network • SITE to SITE : Site-to-site VPNs provide an Internet-based WAN infrastructure to extend network resources to branch offices, home offices, and business partner sites. • Reliable and high-quality transport of complex, mission-critical traffic, such as voice and client server applications • Simplified provisioning and reduced operational tasks for network designs • Integrated advanced network intelligence and routing for a wide range of network designs Type of virtual private network • REMOTE ACCESS : Remote access VPNs extend almost any data, voice, or video application to the remote desktop, emulating the main office desktop. With this VPN, you can provide highly secure, customizable remote access to anyone, anytime, anywhere, with almost any device. • Create a remote user experience that emulates working on the main office desktop • Deliver VPN access safely and easily to a wide range of users and devices • Support a wide range of connectivity options, endpoints, and platforms to meet your dynamic remote access needs VPN Layer 2: Overview • Layer 2 site-to-site VPNs (L2VPN) can be provisioned between switches, hosts, and routers and allow data link layer connectivity between separate sites. • Communication between customer switches, hosts, and routers is based on Layer 2 addressing, and PE devices perform forwarding of customer data traffic based on incoming link and Layer 2 header information: • MAC address; • Frame Relay; • Data Link Connection Identifier [DLCI]; • and so on.
    [Show full text]
  • Collision & Broadcast Domain a Collision Domain Is a Section of A
    Computer Networking & Communication 4th Class Arranged By: Dr.Ahmed Chalak Shakir Collision & Broadcast Domain A collision domain is a section of a network where data packets can collide with one another when being sent on a shared medium or through repeaters, particularly when using early versions of Ethernet. A network collision occurs when more than one device attempts to send a packet on a network segment at the same time. A broadcast domain is a logical division of a computer network, in which all nodes can reach each other by broadcast at the data link layer. LAYER 1 - PHYSICAL LAYER Devices - Hubs, Repeaters Collision Domain: As you might have studied both these devices just forward the data as it is to all the devices that are connected to them after attenuating it (making it stronger so that it travels more distance). All the devices fall in the SAME COLLISION DOMAIN because two or more devices might send the data at the same time even when we have CSMA/CD working. So, the data can collide and nullify each other that way no one gets nothing. Broadcast Domain: These devices don't use any type of addressing schemes to help them forward the data like MAC or IP addresses. So, if a PC A sends something for PC B and there are also C,D and E PC's connected to the hub then all the devices i.e. B,C,D and E would receive the data ( Only PC B accepts it while others drop it ). This is what is being in a single BROADCAST DOMAIN.
    [Show full text]
  • Linux Networking 101
    The Gorilla ® Guide to… Linux Networking 101 Inside this Guide: • Discover how Linux continues its march toward world domination • Learn basic Linux administration tips • See how easy it can be to build your entire network on a Linux foundation • Find out how Cumulus Linux is your ticket to networking freedom David M. Davis ActualTech Media Helping You Navigate The Technology Jungle! In Partnership With www.actualtechmedia.com The Gorilla Guide To… Linux Networking 101 Author David M. Davis, ActualTech Media Editors Hilary Kirchner, Dream Write Creative, LLC Christina Guthrie, Guthrie Writing & Editorial, LLC Madison Emery, Cumulus Networks Layout and Design Scott D. Lowe, ActualTech Media Copyright © 2017 by ActualTech Media. All rights reserved. No portion of this book may be reproduced or used in any manner without the express written permission of the publisher except for the use of brief quotations. The information provided within this eBook is for general informational purposes only. While we try to keep the information up- to-date and correct, there are no representations or warranties, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the information, products, services, or related graphics contained in this book for any purpose. Any use of this information is at your own risk. ActualTech Media Okatie Village Ste 103-157 Bluffton, SC 29909 www.actualtechmedia.com Entering the Jungle Introduction: Six Reasons You Need to Learn Linux ....................................................... 7 1. Linux is the future ........................................................................ 9 2. Linux is on everything .................................................................. 9 3. Linux is adaptable ....................................................................... 10 4. Linux has a strong community and ecosystem ........................... 10 5.
    [Show full text]
  • Ethernet Basics Ethernet Basics
    2016-09-24 Ethernet Basics based on Chapter 4 of CompTIA Network+ Exam Guide, 4th ed., Mike Meyers Ethernet Basics • History • Ethernet Frames • CSMA/CD • Obsolete versions • 10Mbps versions • Segments • Spanning Tree Protocol 1 2016-09-24 Ethernet – Early History • 1970: ALOHAnet, first wireless packet-switched network - Norman Abramson, Univ. of Hawaii - Basis for Ethernet’s CSMA/CD protocol - 1972: first external network connected to ARPANET • 1973: Ethernet prototype developed at Xerox PARC - (Palo Alto Research Center) - 2.94 Mbps initially • 1976: "Ethernet: Distributed Packet Switching for Local Computer Networks" published in Communications of the ACM. - Bob Metcalfe and David Boggs - sometimes considered “the beginning of Ethernet” Ethernet goes Mainstream • 1979: DEC, Intel, Xerox collaborate on a commercial Ethernet specification - Ethernet II, a.k.a. “DIX” Ethernet - (Digital Equipment Corporation) • 1983: IEEE 802.3 specification formally approved - Differs from Ethernet II in the interpretation of the third header field • 1987: alternatives to coaxial cables - IEEE 802.3d: FOIRL, Fiber Optic Inter-Repeater Link - IEEE 802.3e: 1 Mbps over Twisted Pair wires (whoopee!) • 1990: Twisted-Pair wiring takes over - IEEE 802.3i: 10 Mbps over Twisted-Pair – 10Base-TX, 10Base-T4 2 2016-09-24 the Future is Now (next chapter) (and Now is so Yesteryear…) 1995 – Now: speed and cabling improvements • 1995: 100Mbps varieties • 1999: 1Gbps on twisted-pair • 2003-2006: 10Gbps on optical fiber and UTP • 2010: 40Gbps, 100Gbps (802.3ba) - optical fiber or twinaxial cable - point-to-point physical topology; for backbones • 2016, September: 2.5GBase-T, 5GBase-T ? - who knows? What Is Ethernet? • Protocols, standards for Local Area Networks » Ethernet II, IEEE 802.3 • Specifies Physical-layer components - Cabling, signaling properties, etc.
    [Show full text]
  • Communication & Network Security
    6/13/19 Communication & Network Security MIS-5903 http://community.mis.temple.edu/mis5903sec011s17/ OSI vs. TCP/IP Model • Transport also called Host-to-Host in TCP/IP model. Encapsulation • System 1 is a “subject” (client) • System 2 has the “object” (server) 1 6/13/19 OSI Reference Notice: • Segments • Packets (Datagrams) • Frames • Bits Well known ports Protocol TCP/UDP Port Number File Transfer Protocol (FTP) (RFC 959) TCP 20/21 Secure Shell (SSH) (RFC 4250-4256) TCP 22 Telnet (RFC TCP 23 854) Simple Mail Transfer Protocol (SMTP) (RFC 5321) TCP 25 Domain Name System (DNS) (RFC 1034-1035) TCP/UDP 53 Dynamic Host Configuration Protocol (DHCP) (RFC 2131) UDP 67/68 Trivial File Transfer Protocol (TFTP) (RFC 1350) UDP 69 Hypertext Transfer Protocol (HTTP) (RFC 2616) TCP 80 Post Office Protocol (POP) version 3 (RFC 1939) TCP 110 Network Time Protocol (NTP) (RFC 5905) UDP 123 NetBIOS (RFC TCP/UDP 1001-1002) 137/138/139 Internet Message Access Protocol (IMAP) (RFC 3501) TCP 143 Well known ports (continued) Protocol TCP/UDP Port Number Simple Network Management Protocol (SNMP) UDP (RFC 1901-1908, 3411-3418) 161/162 Border Gateway Protocol (BGP) (RFC 4271) TCP 179 Lightweight Directory Access Protocol (LDAP) (RFC 4510) TCP/UDP 389 Hypertext Transfer Protocol over SSL/TLS (HTTPS) (RFC 2818) TCP 443 Line Print Daemon (LPD) TCP 515 Lightweight Directory Access Protocol over TLS/SSL (LDAPS) (RFC 4513) TCP/UDP 636 FTP over TLS/SSL (RFC 4217) TCP 989/990 Microsoft SQL Server TCP 1433 Oracle Server TCP 1521 Microsoft Remote Desktop Protocol (RDP) TCP 3389 • http://www.iana.org/assignments/service-names-port- numbers/service-names-port-numbers.xml.
    [Show full text]
  • Broadcast Domain
    Broadcast Domain A broadcast domain is a logical part of a network (a network segment) in which any network equipment can transmit data directly to other equipment or device without going through arouting device (assuming the devices share the same subnet and use the same gateway; also, they must be in the same VLAN). A more specific broadcast domain definition is the area of the computer network that consists of every single computer or network equipment that can be reached directly by sending a simple frame to the data link layer’s broadcast address. Details on Broadcast Domains While any layer 2 device is able to divide the collision domains, broadcast domains are only divided by layer 3 network devices such as routers or layer 3 switches. Frames are normally addressed to a specific destination device on the network. While all devices detect the frame transmission on the network, only the device to which the frame is addressed actually receives it. A special broadcast address consisting of all is used to send frames to all devices on the network. The VLAN (Virtual Local Area Network) technology can also create a so-called “virtual” broadcast domain. A network built with switching devices can see each network device as an independent system. These groups of independent systems can be joined into one broadcast domain, even if the computers are not physically connected to each other. This is very useful when administrating large networks where there is the need for better network management and control. How to Restrict the Broadcast Domain Since a broadcast domain is the area where broadcasts can be received, routers restrict broadcasts.
    [Show full text]
  • The Internet of Things Meets Big Data – Is Your Network Prepared?
    Moxa’s Webinar The Internet of Things Meets Big Data – Is Your Network Prepared? Nick Sandoval Field Application Engineer Agenda Converged Networks • Internet of Things • Big Data Trends in Industrial Networks Best Practices • Edge to Core • Quality of Service • Predictive • Class Based • Multicast • Network Segmentation with Layer 3 Converged Networks What is a converged network? Network convergence is the efficient coexistence of multiple data types on a single network Offers convenience and flexibility not possible with separate infrastructures Helps leverage economies of scale Nick’s House Hot Topic: Industrial Internet of Things (IIoT) 7 Confidential Confidential Confidential Confidential Big Data Poll Question Do you currently build your network to account for Internet of Things and/or Big Data? a) Not yet, but considering b) Only looked at Internet of Things c) Only looked at Big Data d) Absolutely e) No Trend Trends in the Industrial Space Quad-Play Network Industrial Networking Paradigm Shift Legacy Pervasive Converged Device Networking Industrial Ethernet Automation Network • 1-to-N • N-to-N • N-to-N • S-to-E Gateway • Fieldbus-to-Ethernet • Native Eth. IP • Data, Command • Standalone Networks • OneNET for for Data, Control, Data, Control, Video, Voice Video, Voice SCADA center Surveillance center Network management Control Center/ Information Layer Ground Turbo Ring Turbo Chain Underground Control Saved Layer Saved Explosion- Saved proof cabinet Control & Monitoring Personnel Positioning Wireless Comm. CCTV Systems Systems
    [Show full text]
  • Chapter 5 Link Layer
    Chapter 5 Link Layer Computer Networking: A Top Down Approach th 6 edition Jim Kurose, Keith Ross Addison-Wesley March 2012 All material copyright 1996-2012 J.F Kurose and K.W. Ross, All Rights Reserved Link Layer 5-1 Chapter 5: Link layer our goals: v understand principles behind link layer services: § error detection, correction § sharing a broadcast channel: multiple access § link layer addressing § local area networks: Ethernet, VLANs v instantiation, implementation of various link layer technologies Link Layer 5-2 Link layer, LANs: outline 5.1 introduction, services 5.5 link virtualization: 5.2 error detection, MPLS correction 5.6 data center 5.3 multiple access networking protocols 5.7 a day in the life of a 5.4 LANs web request § addressing, ARP § Ethernet § switches § VLANS Link Layer 5-3 Link layer: introduction terminology: v hosts and routers: nodes global ISP v communication channels that connect adjacent nodes along communication path: links § wired links § wireless links § LANs v layer-2 packet: frame, encapsulates datagram data-link layer has responsibility of transferring datagram from one node to physically adjacent node over a link Link Layer 5-4 Link layer: context v datagram transferred by transportation analogy: different link protocols over v trip from Princeton to Lausanne different links: § limo: Princeton to JFK § e.g., Ethernet on first link, § plane: JFK to Geneva frame relay on § train: Geneva to Lausanne intermediate links, 802.11 v tourist = datagram on last link v transport segment = v each link protocol
    [Show full text]