DOCSLIB.ORG

Unit 3 Type Your Te

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Type your text Unit 3 The Data Link Layer 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 1 Data Link Layer Design Issues • Services Provided to the Network Layer • Framing • Error Control • Flow Control 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 2 Functions of the Data Link Layer • Provide service interface to the network layer • Dealing with transmission errors • Regulating data flow • Slow receivers not swamped by fast senders 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 3 Functions of the Data Link Layer Relationship between packets and frames. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 4 Services Provided to Network Layer (a) Virtual communication. (b) Actual communication. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 5 Services Provided to Network Layer Placement of the data link protocol. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 6 Framing A character stream. (a) Without errors. (b) With one error. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 7 Framing (a) A frame delimited by flag bytes. (b) Four examples of byte sequences before and after stuffing. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 8 Framing Bit stuffing (a) The original data. (b) The data as they appear on the line. (c) The data as they are stored in receiver’s memory after destuffing. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 9 Error Detection and Correction • Error-Correcting Codes • Error-Detecting Codes 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 10 Error-Correcting Codes Use of a Hamming code to correct burst errors. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 11 Error-Detecting Codes Calculation of the polynomial code checksum. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 12 Elementary Data Link Protocols • An Unrestricted Simplex Protocol • A Simplex Stop-and-Wait Protocol • A Simplex Protocol for a Noisy Channel 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 13 Sliding Window Protocols • A One-Bit Sliding Window Protocol • A Protocol Using Go Back N • A Protocol Using Selective Repeat 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 14 Sliding Window Protocols A sliding window of size 1, with a 3-bit sequence number. (a) Initially. (b) After the first frame has been sent. (c) After the first frame has been received. (d) After the first acknowledgement has been received. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 15 A One-Bit Sliding Window Protocol Two scenarios for protocol 4. (a) Normal case. (b) Abnormal case. The notation is (seq, ack, packet number). An asterisk indicates where a network layer accepts a packet. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 16 A Protocol Using Go Back N Pipelining and error recovery. Effect on an error when (a) Receiver’s window size is 1. (b) Receiver’s window size is large. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 17 A Sliding Window Protocol Using Selective Repeat (a) Initial situation with a window size seven. (b) After seven frames sent and received, but not acknowledged. (c) Initial situation with a window size of four. (d) After four frames sent and received, but not acknowledged. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 18 Protocol Verification • Finite State Machined Models • Petri Net Models 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 19 Finite State Machined Models (a) State diagram for protocol 3. (b) Transmissions. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 20 Example Data Link Protocols • HDLC – High-Level Data Link Control • The Data Link Layer in the Internet 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 21 High-Level Data Link Control Frame format for bit-oriented protocols. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 22 High-Level Data Link Control Control field of (a) An information frame. (b) A supervisory frame. (c) An unnumbered frame. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 23 The Data Link Layer in the Internet A home personal computer acting as an internet host. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 24 PPP – Point to Point Protocol The PPP full frame format for unnumbered mode operation. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 25 PPP – Point to Point Protocol A simplified phase diagram for bring a line up and down. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 26 PPP – Point to Point Protocol The LCP frame types. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 27 Chapter 3 The Medium Access Control Sublayer 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 28 The Channel Allocation Problem • Static Channel Allocation in LANs and MANs • Dynamic Channel Allocation in LANs and MANs 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 29 Dynamic Channel Allocation in LANs and MANs 1. Station Model. 2. Single Channel Assumption. 3. Collision Assumption. 4. (a) Continuous Time. (b) Slotted Time. 5. (a) Carrier Sense. (b) No Carrier Sense. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 30 Multiple Access Protocols • ALOHA • Carrier Sense Multiple Access Protocols • Collision-Free Protocols • Limited-Contention Protocols • Wavelength Division Multiple Access Protocols • Wireless LAN Protocols 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 31 Pure ALOHA In pure ALOHA, frames are transmitted at completely arbitrary times. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 32 Pure ALOHA Vulnerable period for the shaded frame. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 33 Pure ALOHA Throughput versus offered traffic for ALOHA systems. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 34 Persistent and Nonpersistent CSMA Comparison of the channel utilization versus load for various random access protocols. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 35 CSMA with Collision Detection CSMA/CD can be in one of three states: contention, transmission, or idle. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 36 Collision-Free Protocols The basic bit-map protocol. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 37 Collision-Free Protocols The binary countdown protocol. A dash indicates silence. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 38 Limited-Contention Protocols Acquisition probability for a symmetric contention channel. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 39 Adaptive Tree Walk Protocol The tree for eight stations. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 40 Wavelength Division Multiple Access Protocols Wavelength division multiple access. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 41 Wireless LAN Protocols A wireless LAN. (a) A transmitting. (b) B transmitting. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 42 Wireless LAN Protocols The MACA protocol. (a) A sending an RTS to B. (b) B responding with a CTS to A. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 43 Ethernet • Ethernet Cabling • Manchester Encoding • The Ethernet MAC Sublayer Protocol • The Binary Exponential Backoff Algorithm • Ethernet Performance • Switched Ethernet • Fast Ethernet • Gigabit Ethernet • IEEE 802.2: Logical Link Control • Retrospective on Ethernet 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 44 Ethernet Cabling The most common kinds of Ethernet cabling. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 45 Ethernet Cabling Three kinds of Ethernet cabling. (a) 10Base5, (b) 10Base2, (c) 10Base-T. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 46 Ethernet Cabling Cable topologies. (a) Linear, (b) Spine, (c) Tree, (d) Segmented. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 47 Ethernet Cabling (4) (a) Binary encoding, (b) Manchester encoding, (c) Differential Manchester encoding. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 48 Ethernet MAC Sublayer Protocol Frame formats. (a) DIX Ethernet, (b) IEEE 802.3. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 49 Ethernet MAC Sublayer Protocol Collision detection can take as long as 2τ . 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 50 Ethernet Performance Efficiency of Ethernet at 10 Mbps with 512-bit slot times. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 51 Switched Ethernet A simple example of switched Ethernet. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 52 Fast Ethernet The original fast Ethernet cabling. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 53 Gigabit Ethernet (a) A two-station Ethernet. (b) A multistation Ethernet. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 54 Gigabit Ethernet Gigabit Ethernet cabling. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 55 IEEE 802.2: Logical Link Control (a) Position of LLC. (b) Protocol formats. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 56 Wireless LANs • The 802.11 Protocol Stack • The 802.11 Physical Layer • The 802.11 MAC Sublayer Protocol • The 802.11 Frame Structure • Services 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 57 The 802.11 Protocol Stack Part of the 802.11 protocol stack. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 58 The 802.11 MAC Sublayer Protocol (a) The hidden station problem. (b) The exposed station problem. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 59 The 802.11 MAC Sublayer Protocol The use of virtual channel sensing using CSMA/CA. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 60 The 802.11 MAC Sublayer Protocol A fragment burst. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 61 The 802.11 MAC Sublayer Protocol Interframe spacing in 802.11. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 62 The 802.11 Frame Structure The 802.11 data frame. 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 63 802.11 Services Distribution Services • Association • Disassociation • Reassociation • Distribution • Integration 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 64 802.11 Services Intracell Services • Authentication • Deauthentication • Privacy • Data Delivery 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 65 Broadband Wireless • Comparison of 802.11 and 802.16 • The 802.16 Protocol Stack • The 802.16 Physical Layer • The 802.16 MAC Sublayer Protocol • The 802.16 Frame Structure 1/4/2017 Mr Satyendra Mohan, JIT Barabanki 66 The 802.16 Protocol Stack The 802.16 Protocol Stack.
Recommended publications
  • Transparent LAN Service Over Cable

    Transparent LAN Service Over Cable

    Transparent LAN Service over Cable This document describes the Transparent LAN Service (TLS) over Cable feature, which enhances existing Wide Area Network (WAN) support to provide more flexible Managed Access for multiple Internet service provider (ISP) support over a hybrid fiber-coaxial (HFC) cable network. This feature allows service providers to create a Layer 2 tunnel by mapping an upstream service identifier (SID) to an IEEE 802.1Q Virtual Local Area Network (VLAN). Finding Feature Information Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http:// www.cisco.com/ is not required. Contents • Hardware Compatibility Matrix for Cisco cBR Series Routers, page 2 • Prerequisites for Transparent LAN Service over Cable, page 2 • Restrictions for Transparent LAN Service over Cable, page 3 • Information About Transparent LAN Service over Cable, page 3 • How to Configure the Transparent LAN Service over Cable, page 6 • Configuration Examples for Transparent LAN Service over Cable, page 8 • Verifying the Transparent LAN Service over Cable Configuration, page 10 • Additional References, page 11 • Feature Information for Transparent LAN Service over Cable, page 12 Cisco Converged Broadband Routers Software Configuration Guide For DOCSIS 1 Transparent LAN Service over Cable Hardware Compatibility Matrix for Cisco cBR Series Routers Hardware Compatibility Matrix for Cisco cBR Series Routers Note The hardware components introduced in a given Cisco IOS-XE Release are supported in all subsequent releases unless otherwise specified.
  • Ieee 802.1 for Homenet

    Ieee 802.1 for Homenet

    IEEE802.org/1 IEEE 802.1 FOR HOMENET March 14, 2013 IEEE 802.1 for Homenet 2 Authors IEEE 802.1 for Homenet 3 IEEE 802.1 Task Groups • Interworking (IWK, Stephen Haddock) • Internetworking among 802 LANs, MANs and other wide area networks • Time Sensitive Networks (TSN, Michael David Johas Teener) • Formerly called Audio Video Bridging (AVB) Task Group • Time-synchronized low latency streaming services through IEEE 802 networks • Data Center Bridging (DCB, Pat Thaler) • Enhancements to existing 802.1 bridge specifications to satisfy the requirements of protocols and applications in the data center, e.g. • Security (Mick Seaman) • Maintenance (Glenn Parsons) IEEE 802.1 for Homenet 4 Basic Principles • MAC addresses are “identifier” addresses, not “location” addresses • This is a major Layer 2 value, not a defect! • Bridge forwarding is based on • Destination MAC • VLAN ID (VID) • Frame filtering for only forwarding to proper outbound ports(s) • Frame is forwarded to every port (except for reception port) within the frame's VLAN if it is not known where to send it • Filter (unnecessary) ports if it is known where to send the frame (e.g. frame is only forwarded towards the destination) • Quality of Service (QoS) is implemented after the forwarding decision based on • Priority • Drop Eligibility • Time IEEE 802.1 for Homenet 5 Data Plane Today • 802.1Q today is 802.Q-2011 (Revision 2013 is ongoing) • Note that if the year is not given in the name of the standard, then it refers to the latest revision, e.g. today 802.1Q = 802.1Q-2011 and 802.1D
  • INTRODUCTION Client

    INTRODUCTION Client

    1 INTRODUCTION Client Server Network Fig. 1-1. A network with two clients and one server. Client machine Server machine Request Network Reply Client process Server process Fig. 1-2. The client-server model involves requests and replies. Fig. 1-3. In a peer-to-peer system there are no fixed clients and servers. 2222222222222222222222222222222222222222222222222222222222222222222222222222222 21 222222222222222222222222222222222222222222222222222222222222222222222222222222Tag1 Full name1 Example 1 1 1 1 1 12222222222222222222222222222222222222222222222222222222222222222222222222222222B2C1 Business-to-consumer1 Ordering books on-line 1 21 222222222222222222222222222222222222222222222222222222222222222222222222222222B2B1 Business-to-business1 Car manufacturer ordering tires from supplier 1 21 222222222222222222222222222222222222222222222222222222222222222222222222222222G2C1 Government-to-consumer1 Government distributing tax forms electronically 1 1 1 1 1 12222222222222222222222222222222222222222222222222222222222222222222222222222222C2C1 Consumer-to-consumer1 Auctioning second-hand products on line 1 21 222222222222222222222222222222222222222222222222222222222222222222222222222222P2P1 Peer-to-peer1 File sharing 1 Fig. 1-4. Some forms of e-commerce. 22222222222222222222222222222222222222222222222222222222222222 222222222222222222222222222222222222222222222222222222222222221 Wireless1 Mobile1 Applications 1 1 1 1 1 122222222222222222222222222222222222222222222222222222222222222No1 No1 Desktop computers in offices 1 222222222222222222222222222222222222222222222222222222222222221
  • Network Reliability and Fault Tolerance

    Network Reliability and Fault Tolerance

    Network Reliability and Fault Tolerance Muriel Medard´ [email protected] Laboratory for Information and Decision Systems Room 35-212 Massachusetts Institute of Technology 77 Massachusetts Avenue, Cambridge, MA 02139 Steven S. Lumetta [email protected] Coordinated Science Laboratory University of Illinois Urbana-Champaign 1308 W. Main Street, Urbana, IL 61801 1 Introduction The majority of communications applications, from cellular telephone conversations to credit card transactions, assume the availability of a reliable network. At this level, data are expected to tra- verse the network and to arrive intact at their destination. The physical systems that compose a network, on the other hand, are subjected to a wide range of problems, ranging from signal distor- tion to component failures. Similarly, the software that supports the high-level semantic interface 1 often contains unknown bugs and other latent reliability problems. Redundancy underlies all ap- proaches to fault tolerance. Definitive definitions for all concepts and terms related to reliability, and, more broadly, dependability, can be found in [AAC+92]. Designing any system to tolerate faults first requires the selection of a fault model, a set of possible failure scenarios along with an understanding of the frequency, duration, and impact of each scenario. A simple fault model merely lists the set of faults to be considered; inclusion in the set is decided based on a combination of expected frequency, impact on the system, and feasibility or cost of providing protection. Most reliable network designs address the failure of any single component, and some designs tolerate multiple failures. In contrast, few attempt to handle the adversarial conditions that might occur in a terrorist attack, and cataclysmic events are almost never addressed at any scale larger than a city.
  • Introduction to Spanning Tree Protocol by George Thomas, Contemporary Controls

    Introduction to Spanning Tree Protocol by George Thomas, Contemporary Controls

    Volume6•Issue5 SEPTEMBER–OCTOBER 2005 © 2005 Contemporary Control Systems, Inc. Introduction to Spanning Tree Protocol By George Thomas, Contemporary Controls Introduction powered and its memory cleared (Bridge 2 will be added later). In an industrial automation application that relies heavily Station 1 sends a message to on the health of the Ethernet network that attaches all the station 11 followed by Station 2 controllers and computers together, a concern exists about sending a message to Station 11. what would happen if the network fails? Since cable failure is These messages will traverse the the most likely mishap, cable redundancy is suggested by bridge from one LAN to the configuring the network in either a ring or by carrying parallel other. This process is called branches. If one of the segments is lost, then communication “relaying” or “forwarding.” The will continue down a parallel path or around the unbroken database in the bridge will note portion of the ring. The problem with these approaches is the source addresses of Stations that Ethernet supports neither of these topologies without 1 and 2 as arriving on Port A. This special equipment. However, this issue is addressed in an process is called “learning.” When IEEE standard numbered 802.1D that covers bridges, and in Station 11 responds to either this standard the concept of the Spanning Tree Protocol Station 1 or 2, the database will (STP) is introduced. note that Station 11 is on Port B. IEEE 802.1D If Station 1 sends a message to Figure 1. The addition of Station 2, the bridge will do ANSI/IEEE Std 802.1D, 1998 edition addresses the Bridge 2 creates a loop.
  • Layer 2 Virtual Private Networks CM-SP-L2VPN-I11-130808

    Layer 2 Virtual Private Networks CM-SP-L2VPN-I11-130808

    Data-Over-Cable Service Interface Specifications Business Services over DOCSIS® Layer 2 Virtual Private Networks CM-SP-L2VPN-I11-130808 ISSUED Notice This DOCSIS specification is the result of a cooperative effort undertaken at the direction of Cable Television Laboratories, Inc. for the benefit of the cable industry and its customers. This document may contain references to other documents not owned or controlled by CableLabs®. Use and understanding of this document may require access to such other documents. Designing, manufacturing, distributing, using, selling, or servicing products, or providing services, based on this document may require intellectual property licenses from third parties for technology referenced in this document. Neither CableLabs nor any member company is responsible to any party for any liability of any nature whatsoever resulting from or arising out of use or reliance upon this document, or any document referenced herein. This document is furnished on an "AS IS" basis and neither CableLabs nor its members provides any representation or warranty, express or implied, regarding the accuracy, completeness, noninfringement, or fitness for a particular purpose of this document, or any document referenced herein. Cable Television Laboratories, Inc., 2006-2013 CM-SP-L2VPN-I11-130808 Data-Over-Cable Service Interface Specifications DISCLAIMER This document is published by Cable Television Laboratories, Inc. ("CableLabs®"). CableLabs reserves the right to revise this document for any reason including, but not limited to, changes in laws, regulations, or standards promulgated by various agencies; technological advances; or changes in equipment design, manufacturing techniques, or operating procedures described, or referred to, herein. CableLabs makes no representation or warranty, express or implied, with respect to the completeness, accuracy, or utility of the document or any information or opinion contained in the report.
  • 7-Port Gigabit Ethernet Switch with Audio Video Bridging and Two RGMII/MII/RMII Interfaces

    7-Port Gigabit Ethernet Switch with Audio Video Bridging and Two RGMII/MII/RMII Interfaces

    KSZ9567R 7-Port Gigabit Ethernet Switch with Audio Video Bridging and Two RGMII/MII/RMII Interfaces Highlights • Five Integrated PHY Ports - 1000BASE-T/100BASE-TX/10BASE-Te IEEE 802.3 • Non-blocking wire-speed Ethernet switching fabric - Fast Link-up option significantly reduces link-up time • Full-featured forwarding and filtering control, includ- - Auto-negotiation and Auto-MDI/MDI-X support ing Access Control List (ACL) filtering - On-chip termination resistors and internal biasing for • Full VLAN and QoS support differential pairs to reduce power • Five ports with integrated 10/100/1000BASE-T PHY - LinkMD® cable diagnostic capabilities for determining transceivers cable opens, shorts, and length • Two ports with 10/100/1000 Ethernet MACs and con- • Advanced Switch Capabilities figurable RGMII/MII/RMII interfaces - IEEE 802.1Q VLAN support for 128 active VLAN • IEEE 1588v2 Precision Time Protocol (PTP) support groups and the full range of 4096 VLAN IDs - IEEE 802.1p/Q tag insertion/removal on per port basis • IEEE 802.1AS/Qav Audio Video Bridging (AVB) - VLAN ID on per port or VLAN basis • IEEE 802.1X access control support - IEEE 802.3x full-duplex flow control and half-duplex • EtherGreen™ power management features, back pressure collision control including low power standby - IEEE 802.1X access control 2 • Flexible management interface options: SPI, I C, (Port-based and MAC address based) MIIM, and in-band management via any port - IGMP v1/v2/v3 snooping for multicast packet filtering • Industrial temperature range support - IPv6
  • Analysis of Qos in Software Defined Wireless Network with Spanning Tree Protocol

    Analysis of Qos in Software Defined Wireless Network with Spanning Tree Protocol

    I. J. Computer Network and Information Security, 2017, 6, 61-68 Published Online June 2017 in MECS (http://www.mecs-press.org/) DOI: 10.5815/ijcnis.2017.06.07 Analysis of QoS in Software Defined Wireless Network with Spanning Tree Protocol Rafid Mustafiz, Abu Sayem Mohammad Delowar Hossain, Nazrul Islam+, Mohammad Motiur Rahman Department of Computer Science and Engineering +Department of Information and Communication Technology Mawlana Bhashani Science and Technology University, Santosh, Tangail-1902, Bangladesh E-mail: [email protected], [email protected], [email protected], [email protected] Abstract—Software Defined Network (SDN) is more technique. The data controlling actions are controlled by dynamic, manageable, adaptive and programmable a software or hardware based centralized controller and network architecture. This architecture separates the data forwarding task has performed by a hardware core control plane from the forwarding plane that enables the device [3]. This enables the control plane to be directly network to become directly programmable. The programmable which makes it suitable in the field of programmable features of SDN technology has research. Data plane functionality contains features such dramatically improved network efficiency and simplify as quality of service (QoS) [4]. The overall performance the network configuration and resource management. of a network topology depends mostly on the parameters SDN supports Open-Flow technology as forwarding of QoS. The present goal of SDN is to design a network function and centralized control successfully. Wireless that is capable the maximum improvement of QoS environment has recently added to the SDN infrastructure parameters. SDN supports many new types of that has rapidly emerged with Open-Flow protocol.
  • The Role of Emerging Broadband Technologies on the Converged

    The Role of Emerging Broadband Technologies on the Converged

    The Role of Emerging Broadband Technologies on the Converged Packet-Based Network Introduction The vision of network convergence toward a consolidated packet-based network has been discussed for years, though it is still not a reality. Currently, there are numerous overlay networks such as IP, ATM, FR, Ethernet, SONET, DWDM and wireless for different services. The evolution pace toward convergence has been slow due to economic, technical and regulatory issues. However, the fact is that data traffic volume is now surpassing voice traffic volume. Traditional TDM voice traffic is moving to IP packets and TDM private line is moving to Ethernet private line. The wave of broadband applications such as Internet access, VOD, and IPTV create high bandwidth requirements for the network. These applications are packet-based, but have a much lower margin of profit for the service providers when compared to traditional voice service. Today’s overlay and traditional circuit-based infrastructure will become less optimal for the new packet-based services as the profit margin decreases. Most of the wireless networks in North America today are still circuit-based because most of the current wireless service is still voice-based. However, with emerging wireless access technologies such as WiMAX and Wi-Fi, more broadband wireless data and video services can be deployed. As a result, the wireless core network evolves toward a packet-based network. Service offerings drive network evolution. As more packet-based broadband services are launched and bundled together in service offerings, service providers start to add more packet-aware features into their current network components.
  • V1.1.1 (2014-09)

    V1.1.1 (2014-09)

    Final draft ETSI ES 203 385 V1.1.1 (2014-09) ETSI STANDARD CABLE; DOCSIS® Layer 2 Virtual Private Networking 2 Final draft ETSI ES 203 385 V1.1.1 (2014-09) Reference DES/CABLE-00008 Keywords access, broadband, cable, data, IP, IPcable, L2VPN, modem 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 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org 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 only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. 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 http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.
  • Congestion Control in Resilient Packet Ring Networks

    Congestion Control in Resilient Packet Ring Networks

    New Jersey Institute of Technology Digital Commons @ NJIT Dissertations Electronic Theses and Dissertations Fall 1-31-2005 Congestion control in resilient packet ring networks Alharbi Fahd New Jersey Institute of Technology Follow this and additional works at: https://digitalcommons.njit.edu/dissertations Part of the Electrical and Electronics Commons Recommended Citation Fahd, Alharbi, "Congestion control in resilient packet ring networks" (2005). Dissertations. 670. https://digitalcommons.njit.edu/dissertations/670 This Dissertation is brought to you for free and open access by the Electronic Theses and Dissertations at Digital Commons @ NJIT. It has been accepted for inclusion in Dissertations by an authorized administrator of Digital Commons @ NJIT. For more information, please contact [email protected]. Copyright Warning & Restrictions The copyright law of the United States (Title 17, United States Code) governs the making of photocopies or other reproductions of copyrighted material. Under certain conditions specified in the law, libraries and archives are authorized to furnish a photocopy or other reproduction. One of these specified conditions is that the photocopy or reproduction is not to be “used for any purpose other than private study, scholarship, or research.” If a, user makes a request for, or later uses, a photocopy or reproduction for purposes in excess of “fair use” that user may be liable for copyright infringement, This institution reserves the right to refuse to accept a copying order if, in its judgment, fulfillment
  • Network Virtualization Using Shortest Path Bridging (802.1Aq) and IP/SPB

    Network Virtualization Using Shortest Path Bridging (802.1Aq) and IP/SPB

    avaya.com Network Virtualization using Shortest Path Bridging and IP/SPB Abstract This White Paper discusses the benefits and applicability of the IEEE 802.1aq Shortest Path Bridging (SPB) protocol which is augmented with sophisticated Layer 3 routing capabilities. The use of SPB and the value to solve virtualization of today’s network connectivity in the enterprise campus as well as the data center are covered. This document is intended for any technically savvy network manager as well as network architect who are faced with: • Reducing time to service requirements • Less tolerance for network down time • Network Virtualization requirements for Layer 2 (VLAN-extensions) and Layer 3 (VRF-extensions) • Server Virtualization needs in data center deployments requiring a large set of Layer 2 connections (VLANs) • Traffic separation requirements in campus deployments for security purposes as well as robustness considerations (i.e. contractors for maintenance reasons needing access to their equipment or guest access needs) • Multi-tenant applications such as airports, governments or any other network with multiple discrete (legal) entities that require traffic separation WHITE PAPER 1 avaya.com Table of Contents 1. Introduction ........................................................................................................................ 3 2. Benefits of SPB ................................................................................................................... 4 2.1 Network Service Enablement ............................................................................................................