DOCSLIB.ORG

5G Radio Access Network Architecture for Terrestrial Broadcast Services

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
5G Radio Access Network Architecture for Terrestrial Broadcast Services IEEE TRANSACTIONS ON BROADCASTING 1 5G Radio Access Network Architecture for Terrestrial Broadcast Services Mikko Säily, Carlos Barjau Estevan, Jordi Joan Gimenez, Fasil Tesema, Wei Guo, David Gomez-Barquero and De Mi Abstract — The 3rd Generation Partnership Project (3GPP) has design. Rel-15 and Rel-16 only cover unicast, or Point-to-Point defined based on the Long Term Evolution (LTE) enhanced (PTP), transmissions. However, benefits of multicast and Multicast Broadcast Multimedia Service (eMBMS) a set of new broadcast, or Point-to-Multipoint (PTM), have been already features to support the distribution of Terrestrial Broadcast assessed as beneficial for some 5G use cases [1], [2]. services in Release 14. On the other hand, a new 5th Generation (5G) system architecture and radio access technology, 5G New The support of PTM communications is not new in 3GPP. Radio (NR), are being standardised from Release 15 onwards, Mobile broadcast as a service is already included in Long Term which so far have only focused on unicast connectivity. This may Evolution (LTE) as per the enhanced Multicast/Broadcast change in Release 17 given a new Work Item set to specify basic Multimedia Service (eMBMS). The set of specifications have Radio Access Network (RAN) functionalities for the provision of been updated to support new services such as public safety, multicast/broadcast communications for NR. This work initially Internet of Things (IoT) or Vehicle-to-Everything (V2X) [3]. excludes some of the functionalities originally supported for Terrestrial Broadcast services under LTE e.g. free to air, receive- Its most recent update comes in Rel-14 [4] and Rel-16 [5], [6] only mode, large-area single frequency networks, etc. This paper in order to support the 5G requirements for broadcast, and in proposes an enhanced Next Generation RAN architecture based particular for the provision of Terrestrial Broadcast services. on 3GPP Release 15 with a series of architectural and functional This has implied severe changes at the air-interface to enhancements, to support an efficient, flexible and dynamic implement larger Single Frequency Networks (SFNs) or the selection between unicast and multicast/broadcast transmission introduction of carriers with dedicated broadcast content. The modes and also the delivery of Terrestrial Broadcast services. The paper elaborates on the Cloud-RAN based architecture and architecture relies on the existing for eMBMS with the proposes new concepts such as the RAN Broadcast/Multicast introduction of the so-called receive-only mode for Subscriber Areas that allows a more flexible deployment in comparison to Identification Module (SIM)-free operation even without eMBMS. High-level assessment methodologies including uplink, or a new xMB interface between the eMBMS system complexity analysis and inspection are used to evaluate the and service providers. So far, eMBMS has proven limited feasibility of the proposed architecture design and compare it with success among mobile network operators due to a demanding the 3GPP architectural requirements. implementation both at the network architecture and user Index Terms — 5G, architecture, broadcast, multicast, point-to- equipment. point, point-to-multipoint, radio access network, single frequency Under the 5G System (5GS) and NG-RAN architectures, network, signal synchronisation. basic support for multicast/broadcast is expected to be introduced in Rel-17. This includes Multicast/Broadcast I. INTRODUCTION support at 5G Core Network [7] and NR-based Mixed Mode HE 3rd Generation Partnership Project (3GPP) finalised the transmissions at RAN [8]. The support of Terrestrial Broadcast T first set of 5th Generation (5G) specifications for Release 15 services is not in the scope of these specifications. However, a (Rel-15) in December 2018. This defines a new Radio Access generic architectural solution that could allocate requirements Technology (RAT) known as New Radio (NR), the Next from different domains would be beneficial to increase Generation Radio Access Network (NG-RAN) and the 5G Core deployment opportunities. Network which embrace several design principles such as: (i) One of the 3GPP system requirements for 5G is a flexible forward compatibility with future releases; (ii) control-user broadcast/multicast service for three types of devices, be they plane separation (CUPS); (iii) lean and cloud-native system enhanced Mobile Broadband (eMBB), Ultra Reliable and Low This work was supported in part by the European Commission under the Politecnica de Valencia, 46022 Valencia, Spain (e-mail: {carbare1, 5GPPP project 5G-Xcast (H2020-ICT-2016-2 call, grant number 761498). The dagobar}@iteam.upv.es). views expressed in this contribution are those of the authors and do not J. J. Gimenez is with the Future Networks Department, Institut für necessarily represent the project. Part of the material in this paper was presented RundfunktTechnik GmbH, 80939 Munich, Germany (e-mail: at the IEEE International Symposium on Broadband Multimedia Systems and [email protected]). Broadcasting (BMSB) 2019 [20]. F. Tesema is with Nomor Research GmbH, Munich, 81541 Germany (e- M. Säily is with the Standardization and Research Lab, Network & mail: [email protected]) Architecture Group, Nokia Bell Labs, Espoo, 02610 Finland (e-mail: W. Guo is with Samsung R&D Institute UK, Staines-upon-Thames TW18 [email protected]). 4QE, U.K. (e-mail: [email protected]). C. Barjau Estevan and D. Gomez-Barquero are with the Institute of D. Mi is with the 5G Innovation Centre (5GIC), Institute for Communication Telecommunications and Multimedia Applications (iTEAM), Universitat Systems, University of Surrey, Guildford GU2 7XH, U.K. (e-mail: [email protected]). IEEE TRANSACTIONS ON BROADCASTING 2 Latency Communications (URLLC) and massive Machine Type Communications (mMTC) [9]. 5G should be envisioned as a system of systems, where the Core and Transport Network Data Network alongside the RAN must accommodate a plethora of different SMF services, with stringent requirements, ranging from several N6 N4 N11 gigabits/sec (think of Augmented/Virtual reality - AR/VR) to UPF AMF low kilobits/sec throughput (think of mMTC), latencies ranging 5GC from 1 millisecond (e.g., industrial IoT) up to several seconds NG-RAN N3 N2 gNB (e.g., best-effort data delivery), mobility support to moving gNB-CU-UP E1 gNB-CU-CP Xn gNB devices, from static equipment (e.g., roof-top antennas) up to (SDAP, PDCP) (SDAP, PDCP) 500 kilometre per hour (e.g., V2X) and support for millions of F1-U F1-C users per square kilometre (e.g., massive IoT) [10]-[12]. F1-C F1-U The 5G Infrastructure Public Private Partnership (5G-PPP) gNB-DU gNB-DU project 5G-Xcast has developed a holistic implementation of (RLC, MAC, PHY) (RLC, MAC, PHY) eCPRI/xRAN 5G PTM systems [13], covering Core Network [14]-[16] and interface RAN developments from air interface [17], [18] to architecture RU RU RU RU [19]-[21] and protocols [21], [22]. This can facilitate the (PHY) (PHY) (PHY) (PHY) fulfilment of requirements from different applications [23], including traditional Terrestrial Broadcast deployments, which Fig. 1. Rel-15 NG-RAN architecture with a CU-DU split deployment. are the scope of this work. The main contributions of this work are listed as follows: Central Units (CUs) and Distributed Units (DUs) in 5G • We develop a dynamic RAN Broadcast/Multicast Areas architecture enables dynamic adaptation of QoS functions mechanism that allows the delivery of multicast/broadcast depending on the real-time radio conditions, user density and services wherever needed without the fixed deployment on dynamically controlled geographical area. top of the existing RAN. As shown in Fig. 1, the gNB functions are split into CU and • Our proposed RAN architecture design supports multi-cell DU, where CU covers higher layer protocol functions of and SFN transmissions using NG-RAN based Service Data Adaptation Protocol (SDAP) and Packet Data synchronization method fulfilling Quality of Service (QoS) Convergence Protocol (PDCP), and DU entails lower layer targets defined for traffic flows. protocol functions of Radio Link Control (RLC), Medium • We introduce a new RAN interface design to support Access Control (MAC) and Physical Layer (PHY). In a typical Terrestrial Broadcast and multicast with the minimal Cloud-RAN deployment, the CUs are placed in a computing impact on the current 5G system. hardware pool and thus form the cloud. The gNBs are inter- • We propose a detailed procedure and deployment strategy connected through an Xn interface. for our architecture design, together with high-level The F1 interface provides control (F1-C) and user (F1-U) evaluations including complexity analysis and inspection, plane connectivity between the CU and DU, enabling providing insightful and practical instructions on the deployments with C/U-plane separation. The E1 interface feasibility of our design. provides connectivity between the user plane CU-UP and The rest of this paper is structured as follows. First, the RAN control plane CU-CP, enabling deployments with C/U-plane architecture evolution to 3GPP Rel-15 is discussed in Section separation on the CU level. The interface also provides II. Next, it details in Section III our design on the new RAN separation between the radio network and transport network architecture for the Terrestrial Broadcast. Then, deployments layers, enabling the exchange of User Equipment (UE) and non- and procedures of the proposed architecture are presented in UE
Load more

Recommended publications
  • Ipv6 Addresses
    56982_CH04II 12/12/97 3:34 PM Page 57 CHAPTER 44 IPv6 Addresses As we already saw in Chapter 1 (Section 1.2.1), the main innovation of IPv6 addresses lies in their size: 128 bits! With 128 bits, 2128 addresses are available, which is ap- proximately 1038 addresses or, more exactly, 340.282.366.920.938.463.463.374.607.431.768.211.456 addresses1. If we estimate that the earth’s surface is 511.263.971.197.990 square meters, the result is that 655.570.793.348.866.943.898.599 IPv6 addresses will be available for each square meter of earth’s surface—a number that would be sufficient considering future colo- nization of other celestial bodies! On this subject, we suggest that people seeking good hu- mor read RFC 1607, “A View From The 21st Century,” 2 which presents a “retrospective” analysis written between 2020 and 2023 on choices made by the IPv6 protocol de- signers. 56982_CH04II 12/12/97 3:34 PM Page 58 58 Chapter Four 4.1 The Addressing Space IPv6 designers decided to subdivide the IPv6 addressing space on the ba- sis of the value assumed by leading bits in the address; the variable-length field comprising these leading bits is called the Format Prefix (FP)3. The allocation scheme adopted is shown in Table 4-1. Table 4-1 Allocation Prefix (binary) Fraction of Address Space Allocation of the Reserved 0000 0000 1/256 IPv6 addressing space Unassigned 0000 0001 1/256 Reserved for NSAP 0000 001 1/128 addresses Reserved for IPX 0000 010 1/128 addresses Unassigned 0000 011 1/128 Unassigned 0000 1 1/32 Unassigned 0001 1/16 Aggregatable global 001
    [Show full text]
  • Introduction to IP Multicast Routing
    Introduction to IP Multicast Routing by Chuck Semeria and Tom Maufer Abstract The first part of this paper describes the benefits of multicasting, the Multicast Backbone (MBONE), Class D addressing, and the operation of the Internet Group Management Protocol (IGMP). The second section explores a number of different algorithms that may potentially be employed by multicast routing protocols: - Flooding - Spanning Trees - Reverse Path Broadcasting (RPB) - Truncated Reverse Path Broadcasting (TRPB) - Reverse Path Multicasting (RPM) - Core-Based Trees The third part contains the main body of the paper. It describes how the previous algorithms are implemented in multicast routing protocols available today. - Distance Vector Multicast Routing Protocol (DVMRP) - Multicast OSPF (MOSPF) - Protocol-Independent Multicast (PIM) Introduction There are three fundamental types of IPv4 addresses: unicast, broadcast, and multicast. A unicast address is designed to transmit a packet to a single destination. A broadcast address is used to send a datagram to an entire subnetwork. A multicast address is designed to enable the delivery of datagrams to a set of hosts that have been configured as members of a multicast group in various scattered subnetworks. Multicasting is not connection oriented. A multicast datagram is delivered to destination group members with the same “best-effort” reliability as a standard unicast IP datagram. This means that a multicast datagram is not guaranteed to reach all members of the group, or arrive in the same order relative to the transmission of other packets. The only difference between a multicast IP packet and a unicast IP packet is the presence of a “group address” in the Destination Address field of the IP header.
    [Show full text]
  • Optimizing Xcast Treemap Performance with NFV and SDN T
    Optimizing Xcast Treemap Performance with NFV and SDN T. Khoa Phan Joined work with David Griffin and Miguel Rio University College London Next Generation Networking workshop, July 2016 Facebook Livestream System A B source Origin server C Edge cache Live stream server Origin server D E Fig. 4: Facebook livestream system - CDN [1] • 98% of user requests can be served immediately by edge caches • Each edge cache can serve up to 200,000 users simultaneously [1] https://code.facebook.com/posts/1653074404941839/under-the-hood-broadcasting-live-video-to-millions/ 2 What is Xcast Treemap? S Breath-first tree traversal A B C D E List of IP addresses A 2 0 2 0 0 Treemap Sender S creates packets: B C A B C D E Src: S, Dest: A Payload 2 0 2 0 0 D E Unicast part Xcast treemap part (optional) Today router only understands unicast part. Xcast router lookups and forwards for each IP in the list. Xcast end-host and Xcast router software are available (in IPv6): http://www.ee.ucl.ac.uk/~uceetkp/Xcast_software.zip 3 How Xcast Treemap works? Unicast routing table at R3 Dest Next hop Full Xcast packet header created by S: C C A B C D E D D Src: S, Dest: A Payload 2 0 2 0 0 E E Dest in List dests in unicast part X6Tpart A B D S A | A B C D E B | B D | D A S C B C R1 R2 C | C D E R3 C | C D E E | E Dest Next hop D E E A A Today router B, C, D, E R2 Unicast routing table at R1 Fig.
    [Show full text]
  • AWS Certified Advanced Networking - Specialty Exam
    N E T 2 0 7 - R Understanding the basics of IPv6 networking on AWS Shakeel Ahmad Solutions Architect Amazon Web Services © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Agenda Why IPv6 Brief overview of the IPv6 protocol IPv6 in Amazon VPC IPv4 to IPv6 migration patterns Hands-on with IPv6 on AWS © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. IPv4 exhaustion IPv4 vs IPv6 address size IPv4: 32-bit / 4,294,967,296 addresses (~4.3 x 109) 11000000 00000000 00000010 00000001 IPv6: 128-bit / 340,282,366,920,938,463,463,374,607,431,768,211,456 addresses (~3.4 x 1038) 0010000000000001 0000110110111000 0000111011000010 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000001 © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. IPv4 vs IPv6 address types IPv4: Address types 1. Unicast 2. Broadcast 3. Multicast IPv6: Address types 1. Unicast 2. Multicast 3. Anycast IPv4 vs IPv6 address format IPv4: Dotted Decimal Notation + CIDR 192.168.0.1/24 127.0.0.1 IPv6: Colon-Separated Hextet Notation + CIDR 2001:0db8:0ec2:0000:0000:0000:0000:0001/64 0000:0000:0000:0000:0000:0000:0000:0001 2001:db8:ec2:0:0:0:0:1/64 0:0:0:0:0:0:0:1 2001:db8:ec2::1/64 ::1 © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon VPC—dual-stack VPC Internet gateway IPv4: IPv6: Instance Public Subnet Amazon VPC—private subnet? NAT? VPC Egress-only internet gateway IPv4: IPv6: Instance X Private subnet Amazon VPC—IPv6 routing and more .
    [Show full text]
  • Modeling and Analyzing Anycast and Geocast Routing in Wireless Mesh Networks
    (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 7, No. 9, 2016 Modeling and Analyzing Anycast and Geocast Routing in Wireless Mesh Networks Fazle Hadi∗, Sheeraz Ahmed†, Abid Ali Minhas‡, Atif Naseer§ ∗ Preston University Kohat, Peshawar Campus, Pakistan † Preston University Kohat, Peshawar Campus, Pakistan ‡ Al Yamamah University Riyadh, Saudi Arabia § Science and Technology Unit, Umm Al Qura University, Saudi Arabia Abstract—Wireless technology has become an essential part of this era’s human life and has the capability of connecting virtually to any place within the universe. A mesh network is a self healing wireless network, built through a number of distributed and redundant nodes to support variety of applications and provide reliability. Similarly, anycasting is an important service that might be used for a variety of applications. In this paper we have studied anycast routing in the wireless mesh networks and the anycast traffic from the gateway to the mesh network having multiple anycast groups. We have also studied the geocast traffic in which the packets reach to the group head via unicast traffic and then are broadcasted inside the group. Moreover, we have studied the intergroup communication between different anycast groups. The review of the related literature shows that no one has considered anycasting and geocasting from gateway to the mesh network while considering the multiple anycast groups and intergroup communication. The network is modeled, simulated and analyzed for its various parameters using OMNET++ simulator. Keywords—Mesh Network; Anycast; Geocast; Routing; Unicast Fig. 1. Basic mesh architecture [21] I. INTRODUCTION for every node considering the gateway as a source of heat) The basic aim of the wireless mesh networks (WMNs) is [2].
    [Show full text]
  • Chapter 4 Network Layer
    Chapter 4 Network Layer A note on the use of these ppt slides: We’re making these slides freely available to all (faculty, students, readers). Computer They’re in PowerPoint form so you see the animations; and can add, modify, and delete slides (including this one) and slide content to suit your needs. Networking: A Top They obviously represent a lot of work on our part. In return for use, we only ask the following: Down Approach v If you use these slides (e.g., in a class) that you mention their source th (after all, we’d like people to use our book!) 6 edition v If you post any slides on a www site, that you note that they are adapted Jim Kurose, Keith Ross from (or perhaps identical to) our slides, and note our copyright of this Addison-Wesley material. March 2012 Thanks and enjoy! JFK/KWR All material copyright 1996-2012 J.F Kurose and K.W. Ross, All Rights Reserved Network Layer 4-1 Chapter 4: outline 4.1 introduction 4.5 routing algorithms 4.2 virtual circuit and § link state datagram networks § distance vector 4.3 what’s inside a router § hierarchical routing 4.4 IP: Internet Protocol 4.6 routing in the Internet § datagram format § RIP § IPv4 addressing § OSPF § BGP § ICMP § IPv6 4.7 broadcast and multicast routing Network Layer 4-2 Interplay between routing, forwarding routing algorithm determines routing algorithm end-end-path through network forwarding table determines local forwarding table local forwarding at this router dest address output link address-range 1 3 address-range 2 2 address-range 3 2 address-range 4 1 IP destination
    [Show full text]
  • Bosch IP Video Networks
    Bosch IP Video Networks en Bosch IP Video Manual Bosch IP Video Networks Table of Contents | en 3 Table of Contents 1 Introduction 5 2 Examples for Bosch IP Video network solutions 7 3 General network concepts 13 3.1 OSI 7 Layer Model 13 3.2 Hubs and switches 13 3.3 Routers and Layer 3 switches 14 3.4 Unicast – broadcast – multicast 14 3.5 IP addresses 15 3.6 Ports 16 3.7 VLAN 17 3.8 Network models 17 3.9 Centralized or decentralized recording 20 4 Bosch IP Video key features 21 4.1 Video quality and resolution 21 4.2 Dual streaming 21 4.3 Multicast 22 4.4 Bandwidth 25 4.5 Video Content Analysis 27 4.6 Recording at the edge 27 5 Calculating network bandwidth and storage capacity 28 5.1 Network bandwidth calculation 29 5.2 Storage calculation for VRM recording 30 6 Planning Bosch IP Video networks 31 6.1 Used ports 31 6.1.1 Centralized VRM recording 36 6.1.2 Decentralized VRM recording 37 6.1.3 Centralized NVR recording 38 6.1.4 Decentralized NVR recording 39 6.2 Bandwidth calculation 39 6.2.1 Decentralized VRM recording 40 6.2.2 Decentralized VRM recording with export 42 6.2.3 Centralized NVR recording 42 6.2.4 Centralized NVR recording with export 44 6.3 Storage calculation 44 6.3.1 VRM recording and iSCSI sessions 45 6.3.2 VRM playback 45 6.3.3 VRM storage calculation 46 6.3.4 Calculation example 1 46 6.3.5 Calculation example 2 46 6.4 VLAN 46 Bosch Sicherheitsssysteme GmbH Bosch IP Video Manual - | V2 | 2011.07 4 en | Table of Contents Bosch IP Video Networks 6.5 Examples for recording solutions 48 6.5.1 Direct-to-iSCSI recording 48 6.5.2 Centralized VRM recording 50 6.5.3 Decentralized VRM recording 52 6.5.4 Centralized NVR recording 53 6.5.5 Decentralized NVR recording 55 6.5.6 Pros and Cons of the different recording solutions 57 Index 58 - | V2 | 2011.07 Bosch IP Video Manual Bosch Sicherheitsssysteme GmbH Bosch IP Video Networks Introduction | en 5 1 Introduction This manual collects important information for different target groups on the requirements that Bosch IP Video products have on networks.
    [Show full text]
  • Understanding the Interactions Between Unicast and Group Communications Sessions in Ad Hoc Networks
    UNDERSTANDING THE INTERACTIONS BETWEEN UNICAST AND GROUP COMMUNICATIONS SESSIONS IN AD HOC NETWORKS Lap Kong Law, Srikanth V. Krishnamurthy and Michails Faloutsos '' Department of Computer Science & Engineering University of California, Riverside Riverside, California 92521 {lklaw,krish,michalis}@cs.ucr.edu Abstract In this paper, our objective is to study and understand the mutual effects be­ tween the group communication protocols and unicast sessions in mobile ad hoc networks. The motivation of this work is based on the fact that a realistic wire­ less networks would typically have to support different simultaneous network applications, many of which may be unicast but some of which may need broad­ cast or multicast. However, almost all of the prior work on evaluating protocols in ad hoc networks examine protocols in isolation. In this paper, we compare the interactions of broadcast/multicast and unicast protocols and understand the microscopic nature of the interactions. We find that unicast sessions are sig­ nificantly affected by the group communication sessions. In contrast, unicast sessions have less influence on the performance of group communications due to redundant packet transmissions provided by the latter. We believe that our study is a first step towards understanding such protocol interactions in ad hoc networks. 1. Introduction Most routing protocol evaluations assume Implicitly that only the protocol under consideration Is deployed In the network. However, ad hoc networks are likely to support many types of communication such as unicast, broadcast, and multicast at the same time. Although the performance evaluation of a protocol In Isolation can lend valuable Insights on Its behavior and performance, the protocol may have complex Interactions with other coexisting protocols.
    [Show full text]
  • Design Guide For: Streaming
    Crestron Electronics, Inc. Streaming Design Guide Crestron product development software is licensed to Crestron dealers and Crestron Service Providers (CSPs) under a limited non-exclusive, non transferable Software Development Tools License Agreement. Crestron product operating system software is licensed to Crestron dealers, CSPs, and end-users under a separate End-User License Agreement. Both of these Agreements can be found on the Crestron website at www.crestron.com/legal/software_license_agreement. The product warranty can be found at www.crestron.com/warranty. The specific patents that cover Crestron products are listed at patents.crestron.com. Crestron, the Crestron logo, Capture HD, Crestron Studio, DM, and DigitalMedia are trademarks or registered trademarks of Crestron Electronics, Inc. in the United States and/or other countries. HDMI and the HDMI logo are either trademarks or registered trademarks of HDMI Licensing LLC in the United States and/or other countries. Hulu is either a trademark or registered trademark of Hulu, LLC in the United States and/or other countries. Netflix is either a trademark or registered trademark of Netflix, Inc. in the United States and/or other countries. Wi-Fi is either a trademark or registered trademark of Wi-Fi Alliance in the United States and/or other countries. Other trademarks, registered trademarks, and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Crestron disclaims any proprietary interest in the marks and names of others. Crestron is not responsible for errors in typography or photography. This document was written by the Technical Publications department at Crestron.
    [Show full text]
  • Unicast Routing Protocols (RIP, OSPF, and BGP)
    Unicast Routing Protocols (RIP, OSPF, and BGP) Chapter 11 Routing Protocols Routing Protocol is combination of rules and procedures lets routers in internet inform each other of route changes Autonomous System (AS) is group of networks and routers under authority of single administration Intradomain routing is routing inside AS Handled by interior routing protocol Interdomain routing is routing between AS’s Handled by exterior routing protocol 2 Autonomous Systems 3 Routing Protocols 4 Distance Vector Routing Uses Bellman-Ford algorithm for creating routing table for routers in AS Each node shares its routing table with its immediate neighbors periodically and when there is a change 5 Bellman-Ford Algorithm 6 Distance Vector Routing 7 Distance Vector Routing 4 3 2 Net5 , 1Net4 , 1Net2 , 1 8 Count to Infinity -- Two-Node Instability 9 Solutions to Instability Defining Infinity Define 16 as infinity Split Horizon If node B reaches X via A, then B does not need to advertise to A its (B's) distance to X Split Horizon and Poison Reverse If node B reaches X via A, then B will advertise to A that its (B's) distance to X is infinity 10 Three-Node Instability 11 Routing Information Protocol (RIP) Intradomain routing protocol Based on distance vector routing Uses hop count as metric (cost) Infinite distance defined as 16 hops 12 Example of a domain using RIP 13 RIP Message Format Command: Request (1), Response (2) Version: 1 Family: TCP/IP (2) 14 Requests and Responses Request Message Response (Update) Message Solicited response:
    [Show full text]
  • Main Theme Networks: Part II Circuit Switching, Packet Switching, the Network Layer
    Data Communications & Networks Session 8 – Main Theme Networks: Part II Circuit Switching, Packet Switching, The Network Layer Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences Adapted from course textbook resources Computer Networking: A Top-Down Approach, 5/E Copyright 1996-2013 J.F. Kurose and K.W. Ross, All Rights Reserved 1 Agenda 1 Session Overview 2 Networks Part 2 3 Summary and Conclusion 2 What is the class about? .Course description and syllabus: »http://www.nyu.edu/classes/jcf/csci-ga.2262-001/ »http://cs.nyu.edu/courses/Fall13/CSCI-GA.2262- 001/index.html .Textbooks: » Computer Networking: A Top-Down Approach (6th Edition) James F. Kurose, Keith W. Ross Addison Wesley ISBN-10: 0132856204, ISBN-13: 978-0132856201, 6th Edition (02/24/12) 3 Course Overview . Computer Networks and the Internet . Application Layer . Fundamental Data Structures: queues, ring buffers, finite state machines . Data Encoding and Transmission . Local Area Networks and Data Link Control . Wireless Communications . Packet Switching . OSI and Internet Protocol Architecture . Congestion Control and Flow Control Methods . Internet Protocols (IP, ARP, UDP, TCP) . Network (packet) Routing Algorithms (OSPF, Distance Vector) . IP Multicast . Sockets 4 Course Approach . Introduction to Basic Networking Concepts (Network Stack) . Origins of Naming, Addressing, and Routing (TCP, IP, DNS) . Physical Communication Layer . MAC Layer (Ethernet, Bridging) . Routing Protocols (Link State, Distance Vector) . Internet Routing (BGP, OSPF, Programmable Routers) . TCP Basics (Reliable/Unreliable) . Congestion Control . QoS, Fair Queuing, and Queuing Theory . Network Services – Multicast and Unicast . Extensions to Internet Architecture (NATs, IPv6, Proxies) . Network Hardware and Software (How to Build Networks, Routers) .
    [Show full text]
  • Ipv6 Address Types
    IPv6 Address Types Prefix Designation and Explanation IPv4 Equivalent ::/128 Unspecified 0.0.0.0 This address may only be used as a source address by an initialising host before it has learned its own address. ::1/128 Loopback 127.0.0.1 This address is used when a host talks to itself over IPv6. This often happens when one program sends data to another. ::ffff/96 IPv4-Mapped There is no equivalent. However, the These addresses are used to embed mapped IPv4 address can be looked Example: IPv4 addresses in an IPv6 address. One up in the relevant RIR’s Whois ::ffff:192.0.2.47 use for this is in a dual stack transition database. scenario where IPv4 addresses can be mapped into an IPv6 address. See RFC 4038 for more details. fc00::/7 Unique Local Addresses (ULAs) Private, or RFC 1918 address space: These addresses are reserved for local Example: use in home and enterprise environments 10.0.0.0/8 fdf8:f53b:82e4::53 and are not public address space. 172.16.0.0/12 192.168.0.0/16 These addresses might not be unique, and there is no formal address registration. Packets with these addresses in the source or destination fields are not intended to be routed on the public Internet but are intended to be routed within the enterprise or organisation. See RFC 4193 for more details. fe80::/10 Link-Local Addresses 169.254.0.0/16 These addresses are used on a single Example: link or a non-routed common access fe80::200:5aee:feaa:20a2 network, such as an Ethernet LAN.
    [Show full text]