Lecture 07 IEEE802.2 and Ethernet IEEE 802 Architecture Baseband

Total Page:16

File Type:pdf, Size:1020Kb

Lecture 07 IEEE802.2 and Ethernet IEEE 802 Architecture Baseband IEEE 802 Architecture 802.1 Network Connection Technology Lecture 07 IEEE802.2 and Ethernet LLC Data 802.2 LLC Link Layer Kuang-hua Chen 802.3 802.4 802.5 802.6 802.9 802.11 802.12 AX3T9.5 MAC CSMA Token- Token- DQDB Isochro- Wireless 100VG- FDDI Department of Library and Information Science /CD Bus Ring nous LAN AnyLAN Ethernet PHL National Taiwan University Language & Information Processing System, LIS, NTU 7-1 Language & Information Processing System, LIS, NTU 7-2 Baseband IEEE 802.3 LANs IEEE 802.3 Cabling 10Base5 10Base2 10BaseT Language & Information Processing System, LIS, NTU 7-3 Language & Information Processing System, LIS, NTU 7-4 Network Adapter Data Link Layer in IEEE 802 Interface to station Higher • Data link layer is partitioned into two sublayers Network Layer – Logical Link Control (LLC) Adapter Logic Control – Medium Access Control (MAC) Encapsulation Data Link Layer • MAC is a protocol defining how to use the En/Decoding Physical transmission media Layer transceiver – CSMA/CD: bus structure transmit/receive – Token-Bus: token in bus structure – Token-Ring: token in ring structure Language & Information Processing System, LIS, NTU 7-5 Language & Information Processing System, LIS, NTU 7-6 LLC Specifications of LLC • The different MACs use the same LLC in IEEE • Interface between the protocol of network layer 802 • Interface between the protocol of MAC • This make the higher level protocol independent of the real structure of LAN • Protocol to the LLC of other machines • The main tasks of LLC Network Layer Network Layer – control the exchange of signal LLC LLC – control the data flow MAC MAC – interpret the requests from the higher level protocol Physical Layer Physical Layer and make responses transmission – overcome the transmission errors media Language & Information Processing System, LIS, NTU 7-7 Language & Information Processing System, LIS, NTU 7-8 Service Access Point Example of SAP • There are different protocols running in network Network Layer layer IP IPX • LLC should identify which protocol the incoming data unit belongs to • The use of SAP could smooth the process of SAPs data transfer LLC LLC Protocol Data Unit (LLC PDU) MAC 1 1 1 or 2 0 ~ n byte Physical Layer DSAP SSAP Control Field Message Language & Information Processing System, LIS, NTU 7-9 Language & Information Processing System, LIS, NTU 7-10 Interface between Network Layer Primitives • Four difference services • Request request response confirm Network – Type 1: does not provide connection oriented • Indication Layer Indication Service • Confirm • Datagram service LLC LLC – Type 2: provide connection-oriented service MAC MAC – Type 3: the same as Type 1, but will response an Physical Layer Physical Layer “acknowledgement” message – Type 4: provide the above services transmission media Language & Information Processing System, LIS, NTU 7-11 Language & Information Processing System, LIS, NTU 7-12 Type 1 Services Type 2 Services • DL_UNITDAT.request • Connection establishment • DL_UNITDAT.indication – DL_CONNECT.request – DL_CONNECT.indication – DL_CONNECT.response – DL_CONNECT.confirm • Data transfer – DL_DATA.request – DL_DATA.indication Language & Information Processing System, LIS, NTU 7-13 Language & Information Processing System, LIS, NTU 7-14 Type 2 Services (Continued) Type 3 Services • Connection resetting • DL_DATA_ACK.request – DL_RESET.request • DL_DATA_ACK.indication – DL_RESET.indication • DL_DATA_ACK_STATUS.indication – DL_RESET.response • DL_REPLY.request – DL_RESET.confirm • DL_REPLY.indication • Connection flow control • DL_REPLY_STATUS.indication – DL_CONNECTION_FLOWCONTROL.request • DL_REPLY_UPDATE.request – DL_CONNECTION_FLOWCONTROL.indication • DL_REPLY_UPDATE_STATUS.indication Language & Information Processing System, LIS, NTU 7-15 Language & Information Processing System, LIS, NTU 7-16 LLC/MAC Interface LLC Protocol • LLC uses the services provided by MAC to • Unnumbered Commands transfer LLC PDU • Information Transfer Command • MAC uses the following primitives – used to transfer Type 2 services – MA_UNITDATA.request • Supervisory Commands – MA_UNITDATA.indication – used to manage the usage of connection – MA_UNITDATA.STATUS.indication Language & Information Processing System, LIS, NTU 7-17 Language & Information Processing System, LIS, NTU 7-18 Information Transfer Command Unnumbered Commands (U-Command) (I-Command) • N(S): the sequence of this data DSAP SSAP Control Field Message • N(R): the sequence of data should be received next time from DSAP 1 1 0 0 P/F 0 0 0 Unnumbered Information Command (UI) 1 1 0 1 P/F 1 0 1 Exchange Identification Command (XID) DSAP SSAP Control Field Message 1 1 0 0 P/F 1 1 1 Test Command (TEST) 1 1 1 1 P/F 1 1 0 Set Asynchronous Balanced Mode Extended Command (SABME) 1 1 0 0 P/F 1 1 0 Unnumbered Acknowledgement (UA) 1 1 1 1 P/F 0 0 0 Disconnected Mode response (DM) 1 1 0 0 P/F 0 1 0 Disconnect Command (DISC) 1 1 0 0 P/F 0 0 1 Frame Reject Response (FRMR) 0 Send Count-N(S) P/F Receive Count-N(R) 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Language & Information Processing System, LIS, NTU 7-19 Language & Information Processing System, LIS, NTU 7-20 Sliding Window Example • N(S): sequence number of the data unit A B 7 0 7 0 • N(R): sequence number of the next data unit Send 6 1 Receive 6 1 Window Window which be sent 5 2 5 2 N(R) N(S) 4 3 4 3 A 5 3 B 7 0 7 0 • The data transmitted by A is 3 and A hopes that Receive 6 1 Send 6 1 Window Window it will receive the data with sequence number 5 5 2 5 2 from B 4 3 4 3 Language & Information Processing System, LIS, NTU 7-21 Language & Information Processing System, LIS, NTU 7-22 Example (2) Example (3) A B A B 7 0 7 0 7 0 7 0 Send 6 1 Receive 6 1 Send 6 1 Receive 6 1 Window Window Window Window 5 2 5 2 5 2 5 2 4 3 4 3 4 3 N(S) N(R) 4 3 N(R) N(S) 0 1 0 0 N(S) N(R) 1 1 7 0 7 0 7 0 7 0 Receive 6 1 Send 6 1 Receive 6 1 Send 6 1 Window Window Window Window 5 2 5 2 5 2 5 2 4 3 4 3 4 3 4 3 Language & Information Processing System, LIS, NTU 7-23 Language & Information Processing System, LIS, NTU 7-24 Example (4) Example (5) #1 message lost A B A B 7 0 7 0 7 0 7 0 Send 6 1 Receive 6 1 Send 6 1 Receive 6 1 Window Window Window Window 5 2 N(R) N(S) 5 2 5 2 5 2 4 3 2 1 4 3 4 3 4 3 N(S) N(R) N(R) N(S) 2 1 2 2 7 0 N(R) N(S) 7 0 7 0 7 0 6 1 2 3 6 1 6 1 6 1 Receive 5 2 Send 5 2 Receive 5 2 Send 5 2 Window 4 3 Window 4 3 Window 4 3 Window 4 3 Language & Information Processing System, LIS, NTU 7-25 Language & Information Processing System, LIS, NTU 7-26 Supervisory Commands Example (6) (S-Command) • Receive Ready (RR): receive side is ready A B 7 0 7 0 • Receive Not Ready (RNR): receive side is not Send 6 1 Receive 6 1 Window Window ready to receive data 5 2 5 2 4 3 4 3 • Reject (REJ): reject the request N(R) N(S) 3 1 DSAP SSAP Control Field Message 7 0 7 0 6 1 6 1 0 0 0 P/F 1 Receive Count-N(R) RR Send 1 0 0 1 P/F Receive 5 2 5 2 Receive Count-N(R) RNR Window Window 1 0 1 0 P/F 4 3 4 3 Receive Count-N(R) REJ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Language & Information Processing System, LIS, NTU 7-27 Language & Information Processing System, LIS, NTU 7-28 Construct Connection: An Overall View IEEE 802.3 CSMA/CD • Construct a connection via U-command • Sublayer of Data Link Layer – DL_CONNECT.request (s3-s2) – SAMBE (s2-d2) – MAC Service Specification – MA_UNIDATA.request (s2LL-s2MAC): encapsulate SAMBE LLC FRAME to MAC FRAME – CSMA/CD Protocol – MA_UNIDATA.indication (d2MAC-d2LLC): decapsulate MAC • Physical Layer FRAME to SAMBE LLC FRAME – DL_CONNECT.indication (d2-d3) – Physical Layer Signaling (PLS) – DL_CONNECT.response (d3-d2) – UA (d2-s2) – Attachment Unit Interface (AUI) • The connection between SSAP and DSAP is constructed – Medium Attachment Unit (MAU) • N(S) and N(R) are set to be 0 – DL_CONNECT.confirm (s2-s3) Language & Information Processing System, LIS, NTU 7-29 Language & Information Processing System, LIS, NTU 7-30 MAC Data Unit of MAC 7 1 2,6 2,6 2 4 byte • Responsible for fulfill CSMA/CD task Preamble SFD DA SA LEN LLC PAD FCS • Encapsulation – Encapsulate the data unit from LLC Preamble: 7 bytes, 101010...1010, synchronization SFD (Start Frame Delimiter): 1 byte, 10101011 – Attach the header: SFD, DA, SA, Length DA (Destination Address): 2 or 6 bytes – Attach the tailor: PAD, FCS SA (Source Address): 2 or 6 bytes LEN: 2 bytes, the length of LLC PDU • Decapsulation LCC: at most 1500 bytes PAD (Padding): if the length of LLC is less than 46 bytes, this field is stuffed with some meaningless data FCS (Frame Check Sequence): CRC-32 Language & Information Processing System, LIS, NTU 7-31 Language & Information Processing System, LIS, NTU 7-32 Collision Detection Length Consideration Packet starts Packet almost • To detect the collision, the at time 0 at B at τ-ε –2τ=51.2µsec – 10Mbps – 51.2*10-6*107= 512 bits = 64 bytes Noise burst gets • DA+SA+LEN+FCS = 18 bytes back to A at 2τ – LLC < 46, stuff it with some data Collision at • Avoid a machine occupies resource, a PDU is time τ restricted to 1518 bytes (1500+18 bytes) Language & Information Processing System, LIS, NTU 7-33 Language & Information Processing System, LIS, NTU 7-34 Destination and Source Address Multicast and Broadcast • IEEE 802.3 allows DA and SA to be 2 bytes or • Destination Address 6 bytes long • I/G = 1: Group Address • All stations in networks should use the same • Multicast: each station in the group will receive scheme I/G 15-bit Address the data I/G U/L 46-bit Address • Broadcast: all stations in the network will I/G = 0 Individual Address receive the data (all bits in DA are set to be 1) I/G = 1 Group Address U/L = 0 Globally Administered Address U/L = 1 Locally Administered Address Language & Information Processing System, LIS, NTU 7-35 Language & Information Processing System, LIS, NTU 7-36 Checksum Algorithm International Standard Polynomials • Assume the frame to be sent is M(x) • CRC-12 =+++++XXXXX12 11 3 2 1 • Let r be the degree of G(x) (here CRC-32).
Recommended publications
  • Logical Link Control and Channel Scheduling for Multichannel Underwater Sensor Networks
    ICST Transactions on Mobile Communications and Applications Research Article Logical Link Control and Channel Scheduling for Multichannel Underwater Sensor Networks Jun Li ∗, Mylene` Toulgoat, Yifeng Zhou, and Louise Lamont Communications Research Centre Canada, 3701 Carling Avenue, Ottawa, ON. K2H 8S2 Canada Abstract With recent developments in terrestrial wireless networks and advances in acoustic communications, multichannel technologies have been proposed to be used in underwater networks to increase data transmission rate over bandwidth-limited underwater channels. Due to high bit error rates in underwater networks, an efficient error control technique is critical in the logical link control (LLC) sublayer to establish reliable data communications over intrinsically unreliable underwater channels. In this paper, we propose a novel protocol stack architecture featuring cross-layer design of LLC sublayer and more efficient packet- to-channel scheduling for multichannel underwater sensor networks. In the proposed stack architecture, a selective-repeat automatic repeat request (SR-ARQ) based error control protocol is combined with a dynamic channel scheduling policy at the LLC sublayer. The dynamic channel scheduling policy uses the channel state information provided via cross-layer design. It is demonstrated that the proposed protocol stack architecture leads to more efficient transmission of multiple packets over parallel channels. Simulation studies are conducted to evaluate the packet delay performance of the proposed cross-layer protocol stack architecture with two different scheduling policies: the proposed dynamic channel scheduling and a static channel scheduling. Simulation results show that the dynamic channel scheduling used in the cross-layer protocol stack outperforms the static channel scheduling. It is observed that, when the dynamic channel scheduling is used, the number of parallel channels has only an insignificant impact on the average packet delay.
    [Show full text]
  • Draft Stable Implementation Agreement for Open
    NBS PUBLICATIONS U.S. DEPARTMENT OF COMMERCE National Bureau of Standards Institute for Computer Sciences and Technology A 11 IDE 7 E T M NBSIR 87-3674 Draft Stable Implementation Agreements for Open Systems Interconnection Protocols NBS Workshop for Implementors of Open Systems Interconnection Version 1 Edition 0 October 1987 DRAFT STABLE IMPLEMENTATION AGREEMENTS Based on the Proceeding of the NBS/OSI Implementor’s Workshop Plenary Assembly Held October 9, 1987 National Bureau of Standards Gaithersburg, MD 20899 U.S. DEPARTMENT OF COMMERCE NATIONAL BUREAU OF STANDARDS — QC 100 - U 5 6 87-3674 1987 C • 2 U.S. DEPARTMENT OF COMMERCE National Bureau of Standards Institute for Computer Sciences and Technology Research Information Center NBSIR 87-3674 National r>ureau of Standards Gaithersburg, Maryland 20899 A) BSc DRAFT STABLE IMPLEMENTATION QCtoo AGREEMENTS FOR OPEN SYSTEMS < USy INTERCONNECTION PROTOCOLS m., 1921 c.> NBS Workshop for Implementors of Open Systems Interconnection Version 1 Edition 0 October 1987 DRAFT STABLE IMPLEMENTATION AGREEMENTS Based on the Proceeding of the NBS/OSI Implementor’s Workshop Plenary Assembly Held October 9, 1987 National Bureau of Standards Gaithersburg, MD 20899 U.S. DEPARTMENT OF COMMERCE, C. William Verity, Acting Secretary NATIONAL BUREAU OF STANDARDS, Ernest Ambler, Director 21 Table of Contents 1. GENERAL INFORMATION 1 1.1 PURPOSE OF THIS DOCUMENT * 1 1.2 PURPOSE OF THE WORKSHOP 1 1.3 WORKSHOP ORGANIZATION 1 2. SUB NETWORKS 1 2.1 LOCAL AREA NETWORKS 1 2.1.1 IEEE 802.2 LOGICAL LINK CONTROL 1 2.1.2 IEEE 802.3 CSMA/CD ACCESS METHOD 1 2.1.3 IEEE 802.4 TOKEN BUS ACCESS METHOD 1 2.1.4 IEEE 802.5 Token Ring Access Method 3 2.2 WIDE AREA NETWORKS 4 2.2.1 CCITT RECOMMENDATION X.25 4 2.3 PRIVATE SUBNETWORKS 4 2.3.1 PRIVATE SUBNETWORKS' 4 3.
    [Show full text]
  • QUESTION 20-1/2 Examination of Access Technologies for Broadband Communications
    International Telecommunication Union QUESTION 20-1/2 Examination of access technologies for broadband communications ITU-D STUDY GROUP 2 3rd STUDY PERIOD (2002-2006) Report on broadband access technologies eport on broadband access technologies QUESTION 20-1/2 R International Telecommunication Union ITU-D THE STUDY GROUPS OF ITU-D The ITU-D Study Groups were set up in accordance with Resolutions 2 of the World Tele- communication Development Conference (WTDC) held in Buenos Aires, Argentina, in 1994. For the period 2002-2006, Study Group 1 is entrusted with the study of seven Questions in the field of telecommunication development strategies and policies. Study Group 2 is entrusted with the study of eleven Questions in the field of development and management of telecommunication services and networks. For this period, in order to respond as quickly as possible to the concerns of developing countries, instead of being approved during the WTDC, the output of each Question is published as and when it is ready. For further information: Please contact Ms Alessandra PILERI Telecommunication Development Bureau (BDT) ITU Place des Nations CH-1211 GENEVA 20 Switzerland Telephone: +41 22 730 6698 Fax: +41 22 730 5484 E-mail: [email protected] Free download: www.itu.int/ITU-D/study_groups/index.html Electronic Bookshop of ITU: www.itu.int/publications © ITU 2006 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. International Telecommunication Union QUESTION 20-1/2 Examination of access technologies for broadband communications ITU-D STUDY GROUP 2 3rd STUDY PERIOD (2002-2006) Report on broadband access technologies DISCLAIMER This report has been prepared by many volunteers from different Administrations and companies.
    [Show full text]
  • Medium Access Control Layer
    Telematics Chapter 5: Medium Access Control Sublayer User Server watching with video Beispielbildvideo clip clips Application Layer Application Layer Presentation Layer Presentation Layer Session Layer Session Layer Transport Layer Transport Layer Network Layer Network Layer Network Layer Univ.-Prof. Dr.-Ing. Jochen H. Schiller Data Link Layer Data Link Layer Data Link Layer Computer Systems and Telematics (CST) Physical Layer Physical Layer Physical Layer Institute of Computer Science Freie Universität Berlin http://cst.mi.fu-berlin.de Contents ● Design Issues ● Metropolitan Area Networks ● Network Topologies (MAN) ● The Channel Allocation Problem ● Wide Area Networks (WAN) ● Multiple Access Protocols ● Frame Relay (historical) ● Ethernet ● ATM ● IEEE 802.2 – Logical Link Control ● SDH ● Token Bus (historical) ● Network Infrastructure ● Token Ring (historical) ● Virtual LANs ● Fiber Distributed Data Interface ● Structured Cabling Univ.-Prof. Dr.-Ing. Jochen H. Schiller ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.2 Design Issues Univ.-Prof. Dr.-Ing. Jochen H. Schiller ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.3 Design Issues ● Two kinds of connections in networks ● Point-to-point connections OSI Reference Model ● Broadcast (Multi-access channel, Application Layer Random access channel) Presentation Layer ● In a network with broadcast Session Layer connections ● Who gets the channel? Transport Layer Network Layer ● Protocols used to determine who gets next access to the channel Data Link Layer ● Medium Access Control (MAC) sublayer Physical Layer Univ.-Prof. Dr.-Ing. Jochen H. Schiller ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.4 Network Types for the Local Range ● LLC layer: uniform interface and same frame format to upper layers ● MAC layer: defines medium access ..
    [Show full text]
  • GS970M Datasheet
    Switches | Product Information CentreCOM® GS970M Series Managed Gigabit Ethernet Switches The Allied Telesis CentreCOM GS970M Series of Layer 3 Gigabit switches offer an impressive set of features in a compact design, making them ideal for applications at the network edge. STP root guard ۼۼ Overview Management (UniDirectional Link Detection (UDLD ۼۼ Allied Telesis Autonomous Management ۼۼ Allied Telesis CentreCOM GS970M Series switches provide an excellent Framework™ (AMF) enables powerful centralized management and zerotouch device installation and Security Features access solution for today’s networks, recovery Access Control Lists (ACLs) based on Layer 2, 3 ۼۼ supporting Gigabit to the desktop for Console management port on the front panel for and 4 headers ۼۼ maximum performance. The Power ease of access Configurable auth-fail and guest VLANs ۼۼ Eco-friendly mode allows ports and LEDs to be ۼۼ over Ethernet Plus (PoE+) models Authentication, Authorization, and Accounting ۼۼ provide an ideal solution for connecting disabled to save power (AAA) Industry-standard CLI with context-sensitive help ۼ and remotely powering wireless access ۼ ۼ Bootloader can be password protected for device ۼ ,points, IP video surveillance cameras Powerful CLI scripting engine security ۼۼ ۼ and IP phones. The GS970M models BPDU protection ۼۼ -Comprehensive SNMP MIB support for standards ۼ feature 8, 16 or 24 Gigabit ports, based device management ۼ DHCP snooping, IP source guard and Dynamic ARP ۼ and 2 or 4 SFP uplinks, for secure (Built-in text editor Inspection
    [Show full text]
  • Communications Programming Concepts
    AIX Version 7.1 Communications Programming Concepts IBM Note Before using this information and the product it supports, read the information in “Notices” on page 323 . This edition applies to AIX Version 7.1 and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2010, 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document............................................................................................vii How to use this document..........................................................................................................................vii Highlighting.................................................................................................................................................vii Case-sensitivity in AIX................................................................................................................................vii ISO 9000.....................................................................................................................................................vii Communication Programming Concepts................................................................. 1 Data Link Control..........................................................................................................................................1 Generic Data Link Control Environment Overview...............................................................................
    [Show full text]
  • Tutorial on Network Communications and Security
    Lecture Notes Introduction to Digital Networks and Security Raj Bridgelall, PhD © Raj Bridgelall, PhD (North Dakota State University, College of Business) Page 1/23 Table of Contents PART I – NETWORKING CONCEPTS.....................................................................................4 1 INTRODUCTION..................................................................................................................4 2 DATA COMMUNICATIONS ..............................................................................................4 2.1 THE OSI MODEL ...............................................................................................................4 2.2 NETWORKING DEVICES .....................................................................................................5 2.3 TCP/IP ..............................................................................................................................6 3 MOBILE IP ............................................................................................................................7 3.1 FIREWALLS........................................................................................................................9 3.2 DHCP AND DNS ..............................................................................................................9 3.3 IPV6 ................................................................................................................................10 PART II – CRYPTOGRAPHY AND NETWORK SECURITY .............................................12
    [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]
  • High-Level Data Link Control
    ELEC3030 (EL336) Computer Networks S Chen High-Level Data Link Control • This class of data link layer protocols includes High-level Data Link Control (HDLC), Link Access Procedure Balanced (LAPB) for X.25, Link Access Procedure for D-channel (LAPD) for ISDN, and Logic Link Control (LLC) for FDDI • The frame format is: Flag Address Control Data FCS Flag Note that address and control bits 8 8 8 variable 16 8 can be extended to 16 bits, so bit position 12 3 4 5 6 7 8 N(S)=send sequence number N(R)=receive sequence number that sequence number is 7-bit Information: 0 N(S) P/F N(R) S=supervisory function bits P/F • Frame flag: 01111110, so bit Supervisory: 1 0 S N(R) M=unumbered function bits stuffing is used Unumbered: 1 1 M P/F M P/F=poll/final bit • Address: For multipoint operation, it is used to identify the terminal that transmits or receives the frame and, in point-to-point link, it is used to distinguish Commands from Responses (2nd bit for C/R: 0/1). The address is now extended to 16 bits (1st bit indicates long/short 16/8 bits) • Checksum: FCS contains the remainder of a 16-bit CRC calculation of the frame. It may be extended to 32 bits, using a 32-bit CRC • Control: Three types of frames, I, S and U frames. The old protocol uses a sliding window with 3-bit sequence number and the maximum window size is N = 7. The control field is now extended to 16 bits with 7-bit sequence number 60 ELEC3030 (EL336) Computer Networks S Chen HDLC (continue) • I-frames: carry user data.
    [Show full text]
  • Etsi En 301 192 V1.7.1 (2021-08)
    ETSI EN 301 192 V1.7.1 (2021-08) EUROPEAN STANDARD Digital Video Broadcasting (DVB); DVB specification for data broadcasting 2 ETSI EN 301 192 V1.7.1 (2021-08) Reference REN/JTC-DVB-367 Keywords broadcasting, data, digital, DVB, MPEG, video ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - APE 7112B Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° w061004871 Important notice The present document can be downloaded from: http://www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI deliverable is the one made publicly available in PDF format at www.etsi.org/deliver. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx Notice of disclaimer & limitation of liability The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of experience to understand and interpret its content in accordance with generally accepted engineering or other professional standard and applicable regulations.
    [Show full text]
  • Chapter 3: Datalink Layer
    Chapter 3: Data Link Layer Raj Jain Professor of CIS The Ohio State University Columbus, OH 43210 [email protected] http://www.cis.ohio-state.edu/~jain/ The Ohio State University Raj Jain 1 Overview ❑ Datalink layer design issues ❑ Error detection and correction ❑ Simple datalink protocols ❑ Sliding window protocols ❑ Example datalink protocols The Ohio State University Raj Jain 2 1 Data Link Layer Design Issues ❑ Services provided to the Network Layer ❑ Framing ❑ Error Control ❑ Flow Control The Ohio State University Raj Jain 3 Datalink Layer Services ❑ Unacknowledged connectionless service ❑ No acks, no connection ❑ Error recovery up to higher layers ❑ For low error-rate links or voice traffic ❑ Acknowledged connectionless service ❑ Acks improve reliability ❑ For unreliable channels. E.g.: Wireless Systems The Ohio State University Raj Jain 4 2 Datalink Services (Cont) ❑ Acknowledged connection-oriented service ❑ Equivalent of reliable bit-stream ❑ Connection establishment ❑ Packets Delivered In-Order ❑ Connection Release ❑ Inter-Router Traffic The Ohio State University Raj Jain 5 Framing ❑ Framing = How to break a bit-stream into frames ❑ Need for framing: Error Detection/Control work on chunks and not on bit streams of data ❑ Framing methods: ❑ Timing : risky. No network guarantees. ❑ Character count: may be garbled by errors ❑ Character stuffing: Delimit frame with special characters ❑ Bit stuffing: delimit frame with bit pattern ❑ Physical layer coding violations The Ohio State University Raj Jain 6 3 Character Stuffing ❑
    [Show full text]
  • Chapter 6: Medium Access Control Layer
    Chapter 6: Medium Access Control Layer Chapter 6: Roadmap " Overview! " Wireless MAC protocols! " Carrier Sense Multiple Access! " Multiple Access with Collision Avoidance (MACA) and MACAW! " MACA By Invitation! " IEEE 802.11! " IEEE 802.15.4 and ZigBee! " Characteristics of MAC Protocols in Sensor Networks! " Energy Efficiency! " Scalability! " Adaptability! " Low Latency and Predictability! " Reliability! " Contention-Free MAC Protocols! " Contention-Based MAC Protocols! " Hybrid MAC Protocols! Fundamentals of Wireless Sensor Networks: Theory and Practice Waltenegus Dargie and Christian Poellabauer © 2010 John Wiley & Sons Ltd. 2! Medium Access Control " In most networks, multiple nodes share a communication medium for transmitting their data packets! " The medium access control (MAC) protocol is primarily responsible for regulating access to the shared medium! " The choice of MAC protocol has a direct bearing on the reliability and efficiency of network transmissions! " due to errors and interferences in wireless communications and to other challenges! " Energy efficiency also affects the design of the MAC protocol! " trade energy efficiency for increased latency or a reduction in throughput or fairness! Fundamentals of Wireless Sensor Networks: Theory and Practice Waltenegus Dargie and Christian Poellabauer © 2010 John Wiley & Sons Ltd. 3! 1! Overview " Responsibilities of MAC layer include:! " decide when a node accesses a shared medium! " resolve any potential conflicts between competing nodes! " correct communication errors occurring at the physical layer! " perform other activities such as framing, addressing, and flow control! " Second layer of the OSI reference model (data link layer) or the IEEE 802 reference model (which divides data link layer into logical link control and medium access control layer)! Fundamentals of Wireless Sensor Networks: Theory and Practice Waltenegus Dargie and Christian Poellabauer © 2010 John Wiley & Sons Ltd.
    [Show full text]