DOCSLIB.ORG

Automotive Ethernet: the Definitive Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Automotive Ethernet: the Definitive Guide Automotive Ethernet: The Definitive Guide Charles M. Kozierok Colt Correa Robert B. Boatright Jeffrey Quesnelle Illustrated by Charles M. Kozierok, Betsy Timmer, Matt Holden, Colt Correa & Kyle Irving Cover by Betsy Timmer Designed by Matt Holden Automotive Ethernet: The Definitive Guide. Copyright © 2014 Intrepid Control Systems. All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and publisher. Printed in the USA. ISBN-10: 0-9905388-0-X ISBN-13: 978-0-9905388-0-6 For information on distribution or bulk sales, contact Intrepid Control Systems at (586) 731-7950. You can purchase the paperback or electronic version of this book at www.intrepidcs.com or on Amazon. We’d love to hear your feedback about this book—email us at [email protected]. Product and company names mentioned in this book may be the trademarks of their respective owners. Rather than use a trademark symbol with every occurence of a trademarked name, we are using the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The information in this book is distributed on an “As Is” basis, without warranty. While every precaution has been taken in the preparation of this book, neither the authors nor Intrepid Control Systems shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the information contained in this book. Foreword by Bob Metcalfe, Inventor of Ethernet Automotive Ethernet—If You Build It, They Will Come The early Internet of 1969 ran across transcontinental trunks at 50 kilobits per second, creating what we might dub the Kilobit Internet. Advances such as fiber optics and dense wave-division multiplexing (DWDM) in the 1990s brought us forward to the Megabit Internet of today. What’s next? We network plumbers are now “gigifying” the Internet, with the Gigabit Internet promising incredible performance beyond anything most Internet users can dream of today. But what will all this power be used for? We envision that new technologies will not only expand the Internet’s speed, but also broaden its scope. The Internet of Things (IoT) will bring device connectivity on a scale unimaginable even given the current Internet’s enormous size, making good use of those gigabit connections. And another place where I see the Internet becoming ubiquitous is in the billions of microcontrollers used in modern automobiles, especially as we add new safety, convenience and entertainment capabilities, and eventually move toward driverless transportation for greater safety and efficiency. Many people don’t realize that modern cars are already heavily networked, and becoming more so every day. Planners foresee no fewer than four kinds of automotive networking in the future: © 2014 Intrepid Control Systems. All Rights Reserved. v [email protected] • www.intrepidcs.com 1. Networking within cars, to implement systems control, driver feedback, safety features, entertainment and many other functions. 2. Networking between cars, to implement capabilities such as collision avoidance. 3. Networking between cars and the road infrastructure, for greater safety and efficiency. 4. Networking from cars to the Internet, to allow passengers to get driving-related information such as maps and traffic updates in a timely manner, or simply to remain part of our always-connected world. Automobile networks are currently mostly focused on the first category—in-vehicle systems—which are presently implemented using relatively slow technologies not found outside the automotive industry. As the inner workings of cars become more intelligent and complex, they increasingly demand improvements in the networking area. But any new technology used here needs to be not just faster, cheaper, and capable of connecting many nodes—it also needs to be standardized and widely adopted, to enable compatibility and connectivity among diverse suppliers and industries. As I have been saying for 40 years: “If it’s networking that you need, Ethernet is the answer; what is the question?” In this case, we there might be consider two related questions: “What took the automotive world so long? And how will it now use Ethernet going forward?”. This book provides the answers to these questions. Ethernet comprises much of the Internet’s packet plumbing, and its reach is enormous. It has also been evolving rapidly since its invention as a personal computer LAN back on May 22, 1973, and doing so quite successfully as a set of open standards under IEEE Project 802. It has also been adapted from wired to wireless in the form of Wi-Fi, also known as “wireless Ethernet”, which will play a key role in external automotive networking in the future. More than a billion wired and wireless (Wi-Fi) Ethernet ports now ship annually, and the automotive industry represents the potential for this number to increase significantly. This book is about Ethernet, and how its many advantages and innovations will move in-car networking to the next level, setting the stage for a true revolution in the capabilities of vehicles and how we use them. It provides essential reference material for the intersection of the automotive networking world and the Ethernet world, and points the way to the future of the connected vehicle. It is a guide to the next big thing in the Gigabit Internet: Automotive Ethernet. Bob Metcalfe Inventor of Ethernet Technology Professor of Innovation, Murchison Fellow of Free Enterprise University of Texas at Austin © 2014 Intrepid Control Systems. All Rights Reserved. vi [email protected] • www.intrepidcs.com TABLE OF CONTENTS PART I: INTRODUCTION TO GENERAL AND AUTOMOTIVE NETWORKING .............. 1 Chapter 1: The Motivation for Automotive Ethernet: Advantages and Opportunities ............. 3 1.1 Introduction ............................................................................................................................................................................................... 3 1.2 Two Worlds Collide ............................................................................................................................................................................... 4 1.3 Automotive Electronics - A Market for Growth ................................................................................................................... 5 1.4 Ethernet - An Ocean of Possibilities ............................................................................................................................................ 7 1.5 Increasing Bandwidth and Future-Proof Technology ........................................................................................................... 8 1.6 Full-Duplex, Packet-Switched, Address-Based Networking ...........................................................................................10 1.6.1 Full-Duplex Operation .................................................................................................................................................................10 1.6.2 Packet Switching ..............................................................................................................................................................................11 1.6.3 Address-Based Messaging ...........................................................................................................................................................11 1.7 Electrical Isolation ................................................................................................................................................................................13 1.8 Power over Ethernet (PoE) and Power over Data Lines (PoDL) ..............................................................................14 1.9 High Speed and Low Weight ...........................................................................................................................................................15 1.10 Product Differentiation - It’s No Longer About Nuts and Bolts ................................................................................16 1.11 Wireless Functionality........................................................................................................................................................................17 1.12 Summary ....................................................................................................................................................................................................18 Chapter 2: Overview, Background and Business Requirements of Automotive Networking ..........................................................................................................................................................................19 2.1 Introduction .............................................................................................................................................................................................19 2.2 A Brief History of Automotive Networking ..........................................................................................................................20 2.2.1 The First Serial Communications ............................................................................................................................................20
Load more

Recommended publications
  • Redes De Computadores (RCOMP)
    Redes de Computadores (RCOMP) Lecture 03 2019/2020 • Ethernet local area network technologies. • Virtual local area networks (VLAN). • Wireless local area networks. Instituto Superior de Engenharia do Porto – Departamento de Engenharia Informática – Redes de Computadores (RCOMP) – André Moreira 1 ETHERNET Networks – CSMA/CD Ethernet networks (IEEE 802.3 / ISO 8802-3) were originally developed by Xerox in the 70s. Nowadays, ethernet is undoubtedly the most widely used technology in wired LANs. Originally, access control to the medium (MAC - Medium Access Control) was a key issue. The CSMA/CD technique used in ethernet is not ideal, it doesn’t avoid collisions and, as such, results in low efficiency under heavy traffic. The early Ethernet networks were based on a coaxial cable to which all nodes were connected (bus topology), the most important variants were: Thick Ethernet - 10base5 - 10 Mbps / Digital Signal(1) / maximum 500 m bus length Thin Ethernet - 10base2 - 10 Mbps / Digital Signal(1) / maximum 180 m bus length Node Node Node Node Node Node Node Node Node Node (1) base stands for a baseband transmission medium, therefore digital signals must be used. Instituto Superior de Engenharia do Porto – Departamento de Engenharia Informática – Redes de Computadores (RCOMP) – André Moreira 2 ETHERNET networks – Collision Domain CSMA/CD (Carrier Sense Multiple Access with Collision Detection) requires packet collisions to be detected by all nodes before the emission of the packet ends. This introduces limitations on the relationship between the packet’s transmission time and the signal propagation delay. To ensure collision detection by all nodes, there’s minimum packet size of 64 bytes (this sets a minimum transmission time), also there is a maximum segment size (sets the maximum propagation delay).
    [Show full text]
  • Request for Proposal
    Request For Washington Proposal Metropolitan Area Transit Authority Procurement of Heavy-Duty Transit Low Floor 40 Foot Compressed Natural Gas Buses 40 Foot Hybrid/Electric Buses 60 Foot Hybrid/Electric Articulated Buses TECHNICAL SPECIFICATION PART V RFP NO. FQ12269/JWW WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY SUPPLY AND SERVICE CONTRACT RFP FQ12269/JWW TABLE OF CONTENTS WMATA/ADA REQUIREMENTS FOR HEAVY DUTY TRANSIT BUSES ...................................... 1 WMATA E&D REQUIREMENTS FOR TRANSIT BUSES IN ACCORDANCE WITH AMERICAN WITH DISABILITIES ACT (ADA) PROVISIONS ......................................................... 2 I. LEGAL REQUIREMENTS ..................................................................................................................... 2 II. DEFINITIONS.......................................................................................................................................... 2 III. REQUIREMENTS.................................................................................................................................... 2 5.1 GENERAL .................................................................................................................................. 8 5.1.1 SCOPE ..................................................................................................................................................... 8 5.1.2 DEFINITIONS ........................................................................................................................................ 9 5.1.3
    [Show full text]
  • MTU and MSS Tutorial
    MTU and MSS Tutorial Dr. E. Garcia, [email protected] Published: November 16, 2009. Last Update: November 16, 2009. © 2009 E. Garcia Abstract – This tutorial covers maximum transmission unit ( MTU ), maximum segment size ( MSS ), PING, NETSTAT, and fragmentation. Expressions relevant to these concepts are systematically derived and explained. Keywords: maximum transmission unit, MTU , maximum segment size, MSS , PING, NETSTAT 1 MTU and MSS As discussed in the IP Packet Fragmentation Tutorial (http://www.miislita.com/internet-engineering/ip-packet-fragmentation-tutorial.pdf ) and elsewhere (1 - 3), the data payload ( DP ) of an IP packet is defined as the packet length ( PL ) minus the length of its IP header ( IPHL ), (Eq 1) whereܦܲ theൌ maximum ܲܮ െ ܫܲܪܮ PL is defined as the Maximum Transmission Unit (MTU) . This is the largest IP packet that can be transmitted without further fragmentation. Thus, when PL = MTU (Eq 2) However,ܦܲ ൌ an ܯܷܶ IP packet െ ܫܲܪܮ encapsulates a TCP packet such that DP = TCPHL + MSS (Eq 3) where TCPHL is the length of the TCP header and MSS is the data payload of the TCP packet, also known as the Maximum Segment Size (MSS) . Combining Equations 2 and 3 leads to MSS = MTU – IPHL – TCPHL (Eq 4) Figure 1 illustrates the connection between MTU and MSS –for an IP packet decomposed into three fragments. Figure 1. Fragmentation example where MTU = PL = pl 1 = pl 2 > pl 3 and DP = dp 1 + dp 2 + dp 3 = PL – IPHL . © 2009 E. Garcia 1 Typically, IP and TCP headers are 20 bytes long. Thus, MSS = MTU – 40 (Eq 5) If IP or TCP options are specified, the MSS is further reduced by the number of bytes taken up by the options (OP), each of which may be one byte or several bytes in size.
    [Show full text]
  • Trends in Automotive Communication Systems
    Trends in Automotive Communication Systems NICOLAS NAVET, YEQIONG SONG, FRANÇOISE SIMONOT-LION, AND CÉDRIC WILWERT Invited Paper The use of networks for communications between the electronic windows, and, recently, entertainment and communication control units (ECU) of a vehicle in production cars dates from the equipment (e.g., radio, DVD, hands-free phones, navigation beginning of the 1990s. The specific requirements of the different systems). car domains have led to the development of a large number of auto- motive networks such as Local Interconnect Network, J1850, CAN, In the early days of automotive electronics, each new TTP/C, FlexRay, media-oriented system transport, IDB1394, etc. function was implemented as a stand-alone electronic This paper first introduces the context of in-vehicle embedded sys- control unit (ECU), which is a subsytem composed of a tems and, in particular, the requirements imposed on the commu- microcontroller and a set of sensors and actuators. This nication systems. Then, a comprehensive review of the most widely approach quickly proved to be insufficient with the need for used automotive networks, as well as the emerging ones, is given. Next, the current efforts of the automotive industry on middleware functions to be distributed over several ECUs and the need technologies, which may be of great help in mastering the hetero- for information exchanges among functions. For example, geneity, are reviewed. Finally, we highlight future trends in the de- the vehicle speed estimated by the engine controller or by velopment of automotive communication systems. wheel rotation sensors has to be known in order to adapt Keywords—Car domains, in-vehicle embedded systems, field- the steering effort, to control the suspension, or simply to buses, middlewares (MWs), networks, real-time systems.
    [Show full text]
  • List of TCP and UDP Port Numbers - Wikipedia, the Free Encyclopedia 6/12/11 3:20 PM
    List of TCP and UDP port numbers - Wikipedia, the free encyclopedia 6/12/11 3:20 PM List of TCP and UDP port numbers From Wikipedia, the free encyclopedia (Redirected from TCP and UDP port numbers) This is a list of Internet socket port numbers used by protocols of the Transport Layer of the Internet Protocol Suite for the establishment of host-to-host communications. Originally, these port numbers were used by the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP), but are used also for the Stream Control Transmission Protocol (SCTP), and the Datagram Congestion Control Protocol (DCCP). SCTP and DCCP services usually use a port number that matches the service of the corresponding TCP or UDP implementation if they exist. The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses.[1] However, many unofficial uses of both well-known and registered port numbers occur in practice. Contents 1 Table legend 2 Well-known ports: 0–1023 3 Registered ports: 1024–49151 4 Dynamic, private or ephemeral ports: 49152–65535 5 See also 6 References 7 External links Table legend Color coding of table entries Official Port/application combination is registered with IANA Unofficial Port/application combination is not registered with IANA Conflict Port is in use for multiple applications (may be official or unofficial) Well-known ports: 0–1023 The port numbers in the range from 0 to 1023 are the well-known ports. They are used by system processes that provide widely-used types of network services.
    [Show full text]
  • Iethernet W5500 Datasheet Kr
    W5500 Datasheet Version 1.0.6 http://www.wiznet.co.kr © Copyright 2013 WIZnet Co., Ltd. All rights reserved. W5500 The W5500 chip is a Hardwired TCP/IP embedded Ethernet controller that provides easier Internet connection to embedded systems. W5500 enables users to have the Internet connectivity in their applications just by using the single chip in which TCP/IP stack, 10/100 Ethernet MAC and PHY embedded. WIZnet‘s Hardwired TCP/IP is the market-proven technology that supports TCP, UDP, IPv4, ICMP, ARP, IGMP, and PPPoE protocols. W5500 embeds the 32Kbyte internal memory buffer for the Ethernet packet processing. If you use W5500, you can implement the Ethernet application just by adding the simple socket program. It’s faster and easier way rather than using any other Embedded Ethernet solution. Users can use 8 independent hardware sockets simultaneously. SPI (Serial Peripheral Interface) is provided for easy integration with the external MCU. The W5500’s SPI supports 80 MHz speed and new efficient SPI protocol for the high speed network communication. In order to reduce power consumption of the system, W5500 provides WOL (Wake on LAN) and power down mode. Features - Supports Hardwired TCP/IP Protocols : TCP, UDP, ICMP, IPv4, ARP, IGMP, PPPoE - Supports 8 independent sockets simultaneously - Supports Power down mode - Supports Wake on LAN over UDP - Supports High Speed Serial Peripheral Interface(SPI MODE 0, 3) - Internal 32Kbytes Memory for TX/RX Buffers - 10BaseT/100BaseTX Ethernet PHY embedded - Supports Auto Negotiation (Full and half duplex, 10 and 100-based ) - Not supports IP Fragmentation - 3.3V operation with 5V I/O signal tolerance - LED outputs (Full/Half duplex, Link, Speed, Active) - 48 Pin LQFP Lead-Free Package (7x7mm, 0.5mm pitch) 2 / 68 W5500 Datasheet Version1.0.6 (DEC 2014) Target Applications W5500 is suitable for the following embedded applications: - Home Network Devices: Set-Top Boxes, PVRs, Digital Media Adapters - Serial-to-Ethernet: Access Controls, LED displays, Wireless AP relays, etc.
    [Show full text]
  • Private Radio Systems Price Catalog
    All pricing is 30% off list L3Harris-Tait Products & Services Catalog August 2020 Company Proprietary and Confidential All prices and products are subject to change without notice. NOTICE! The material contained herein is subject to U.S. export approval. No export or re-export is permitted without written approval from the U.S. Government. Rated: EAR99; in accordance with U.S. Dept. of Commerce regulations 15CFR774, Export Administration Regulations. Issued: 07/30/20 Page ii https://premier.pspc.harris.com/infocenter Company Proprietary and Confidential All prices and products are subject to change without notice. Table of Contents Latest Revision 1. Customer Service and Ordering Information ......................................................................... 1.1-1 07/30/20 2. Services Support Packages ................................................................................................................. 2.1-1 07/30/20 Technical Training ............................................................................................................... 2.2-1 07/30/20 3. P25 Portables TP9600 Portables ................................................................................................................. 3.1-1 08/31/20 TP9400 Portables ................................................................................................................. 3.1-9 08/31/20 TP9400 Intrinsically Safe Portables ..................................................................................... 3.1-17 08/31/20 4. P25 Mobiles TM9400
    [Show full text]
  • Practical TCP/IP and Ethernet Networking Titles in the Series
    Practical TCP/IP and Ethernet Networking Titles in the series Practical Cleanrooms: Technologies and Facilities (David Conway) Practical Data Acquisition for Instrumentation and Control Systems (John Park, Steve Mackay) Practical Data Communications for Instrumentation and Control (Steve Mackay, Edwin Wright, John Park) Practical Digital Signal Processing for Engineers and Technicians (Edmund Lai) Practical Electrical Network Automation and Communication Systems (Cobus Strauss) Practical Embedded Controllers (John Park) Practical Fiber Optics (David Bailey, Edwin Wright) Practical Industrial Data Networks: Design, Installation and Troubleshooting (Steve Mackay, Edwin Wright, John Park, Deon Reynders) Practical Industrial Safety, Risk Assessment and Shutdown Systems for Instrumentation and Control (Dave Macdonald) Practical Modern SCADA Protocols: DNP3, 60870.5 and Related Systems (Gordon Clarke, Deon Reynders) Practical Radio Engineering and Telemetry for Industry (David Bailey) Practical SCADA for Industry (David Bailey, Edwin Wright) Practical TCP/IP and Ethernet Networking (Deon Reynders, Edwin Wright) Practical Variable Speed Drives and Power Electronics (Malcolm Barnes) Practical TCP/IP and Ethernet Networking Deon Reynders Pr Eng, BSc BEng, BSc Eng (Elec)(Hons), MBA Edwin Wright MIPENZ, BSc(Hons), BSc(Elec Eng), IDC Technologies, Perth, Australia . Newnes An imprint of Elsevier Linacre House, Jordan Hill, Oxford OX2 8DP 200 Wheeler Road, Burlington, MA 01803 First published 2003 Copyright 2003, IDC Technologies. All rights reserved No part of this publication may be reproduced in any material form (including photocopying or storing in any medium by electronic means and whether or not transiently or incidentally to some other use of this publication) without the written permission of the copyright holder except in accordance with the provisions of the Copyright, Designs and Patents Act 1988 or under the terms of a licence issued by the Copyright Licensing Agency Ltd, 90 Tottenham Court Road, London, England W1T 4LP.
    [Show full text]
  • Computer Networking Exercises
    Computer Networking Exercises Antonio Carzaniga Faculty of Informatics USI (Università della Svizzera italiana) Edition 2.4 April 2020 1 ◮Exercise 1. Consider a DNS query of type A within a DNS system containing IN class information. Using boxes to represent servers and lines with labels to represent packets, diagram an iterative request for “www.ban.mcyds.net”. The answer must be authoritative. Label any DNS servers you need to contact using a descriptive label. Label every packet with the essential information. For example, a box may be labeled “authority for .com,” while a packet might be labeled “answer, www.ban.mcyds.net, 192.168.23.45” (10’) Consider the same DNS request specified above. Now create a new diagram showing a recursive request. Once again, the answer must be authoritative. (10’) ◮Exercise 2. Given the utility functions listed below, write the pseudo-code to perform an iterative DNS lookup. dns_query_pkt make_dns_packet(type, class, flags) Creates a new DNS query packet. Flags can be combined via the ‘|’ operator. So for a query that is both authoritative and recursive, one would write: (DNS_AUTH | DNS_RECURSE). Only the DNS_AUTH and DNS_RECURSE flags are valid. Type can be A, MX, NS, or any other valid DNS type. value get_dns_answer(dns_answer_packet, n) Return the value in the nth answer of a dns_answer_pkt packet. For example, in re- ply to a MX lookup for inf.unisi.ch, get_dns_answer(pkt,1) would return the SMTP mail server for the inf.unisi.ch domain. In reply to a NS query it would return the authoritative name server. dns_answer_packet send_and_wait(dns_query_packet, server) Send the given dns_query_packet and wait for a replay from the given DNS server.
    [Show full text]
  • CAN Gateway in the Implementation of Vehicle Speed Control
    Investigation of a Flexray - CAN Gateway in the Implementation of Vehicle Speed Control A DISSERTATION SUBMITTED TO THE DEPARTMENT OF ENGINEERING TECHNOLOGY OF WATERFORD INSTITUTE OF TECHNOLOGY IN COMPLETE FULFILMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTERS OF ENGINEERING Author Brian Somers Supervisor Mr. John Manning June 2009 Dedicated to: My Mother: Ann Somers and My Father: Tom Somers Declaration I hereby declare that the material presented in this document is entirely my own work and has not been submitted previously as an exercise or degree at this or any other establishment of higher education. I, the author alone, have undertaken the work except where otherwise stated. Signed: Date: Acknowledgements I hereby acknowledge the contributions to my work and offer my thanks to people who have helped and supported me during the course of this research. My Supervisor: Mr. John Manning: I would like to thank John for his continuous supervision, encouragement and invaluable guidance in all areas throughout the course of this research. My Family and Friends: I would like to thank my family and friends for their support, encouragement and understanding throughout all of my studies. The AAEC (Advanced Automotive Electronic Control) Research Group: I would like to take this opportunity to thank all members of the research group, both past and present, whose assistance, knowledge and support has been first-rate. In particular I would like to thank Henry Acheson and Niall Murphy for their addi- tional support throughout the project. There are also many more people who have contributed in countless others way and deserve my thanks also - Thank you! Abstract As the quantity of in-vehicle electronics has increased, automotive networking has been introduced to replace point to point wiring.
    [Show full text]
  • Dynamic Jumbo Frame Generation for Network Performance Scalability
    1 JumboGen: Dynamic Jumbo Frame Generation For Network Performance Scalability David Salyers, Yingxin Jiang, Aaron Striegel, Christian Poellabauer Department of Computer Science and Engineering University of Notre Dame Notre Dame, IN. 46530 USA Email: {dsalyers, yjiang3, striegel, cpoellab}@nd.edu Abstract— Network transmission speeds are increasing at a there is a fixed amount of overhead processing per packet, significant rate. Unfortunately, the actual performance of the it is a challenge for CPUs to scale with increasing network network does not scale with the increases in line speed. This speeds [2]. In order to overcome this issue, many works on is due to the fact that the majority of packets are less than or equal to 64 bytes and the fact that packet size has not scaled with high performance networks, as in [3] and [4], have advocated the increases in network line speeds. This causes a greater and the use of a larger MTU length or jumbo frames. These works greater load to be placed on routers in the network as routing show that the performance of TCP and the network in general decisions have to be made for an ever increasing number of can significantly improve with the use of jumbo-sized packets. packets, which can cause increased packet delay and loss. In Unfortunately, the benefits of jumbo frames are limited for order to help alleviate this problem and make the transfer of bulk data more efficient, networks can support an extra large several reasons. First, the majority of packets transferred are MTU size. Unfortunately, when a packet traverses a number of 64 bytes or less.
    [Show full text]
  • List of TCP and UDP Port Numbers from Wikipedia, the Free Encyclopedia
    List of TCP and UDP port numbers From Wikipedia, the free encyclopedia This is a list of Internet socket port numbers used by protocols of the transport layer of the Internet Protocol Suite for the establishment of host-to-host connectivity. Originally, port numbers were used by the Network Control Program (NCP) in the ARPANET for which two ports were required for half- duplex transmission. Later, the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP) needed only one port for full- duplex, bidirectional traffic. The even-numbered ports were not used, and this resulted in some even numbers in the well-known port number /etc/services, a service name range being unassigned. The Stream Control Transmission Protocol database file on Unix-like operating (SCTP) and the Datagram Congestion Control Protocol (DCCP) also systems.[1][2][3][4] use port numbers. They usually use port numbers that match the services of the corresponding TCP or UDP implementation, if they exist. The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses.[5] However, many unofficial uses of both well-known and registered port numbers occur in practice. Contents 1 Table legend 2 Well-known ports 3 Registered ports 4 Dynamic, private or ephemeral ports 5 See also 6 References 7 External links Table legend Official: Port is registered with IANA for the application.[5] Unofficial: Port is not registered with IANA for the application. Multiple use: Multiple applications are known to use this port. Well-known ports The port numbers in the range from 0 to 1023 are the well-known ports or system ports.[6] They are used by system processes that provide widely used types of network services.
    [Show full text]