DOCSLIB.ORG

SIP-Based Emergency Notification System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SIP-Based Emergency Notification System SIP-based Emergency Notification System Knarig Arabshian and Henning Schulzrinne Department of Computer Science Columbia University October 2001 Abstract We describe how the Session Initiation Protocol can be used to implement an emergency notification system. This system offers advantages such as portability, lower resource consumption, and an additional means of reaching people in case of an emergency. 1 Introduction Emergency notification systems allow government officials to notify a community of an emergency and the subsequent precautionary measures that must be taken. They provide a quick and efficient way of informing the public of an emergency situation and for insuring its safety. It is likely that traditional modes of communication will be augmented by Internet telephones and applications in the near future. Thus, we need to have emergency notification systems established on the the Internet. The Session Initiation Protocol (SIP) [1], which is an application-layer signaling protocol, has been used for maintaining sessions of Internet multimedia conferences, Internet telephony calls, instant messaging and event notification. This paper will discuss how an emergency notification system can be developed using SIP. 2 Overview of Current Emergency Notification Systems The Emergency Broadcast System (EBS) was developed in 1963 to notify the public of emergency situa- tions. In December 1995, the Federal Communications Commission (FCC) changed the EBS to the Emer- gency Alert System (EAS). This change signified a different way state and local governments provide the emergency notification and instruction to the public. The EAS uses digital technology that functions sim- ilarly to computers. It automates the notification process and specifies the requirements of when and how to provide the emergency instruction to the public. Thus, the state and local governments can inform the public through radio, television and cable stations without the need for the broadcast industry to be present. The EAS can also transmit this information to a specific location in an emergency situation, as long as there have been predetermined arrangements of the communication links. The EAS is controlled by the government and used mostly for wide area emergency notification. How- ever, there are emergency notification networks and products that offer emergency alerting in a localized 1 area. A few examples of these are given in [3], [4], [5] and [6]. In particular, Reverse 911 [6] offers emer- gency notification service to local officials or companies who can subscribe to the network and receive any emergency notifications that occur in the nearby vicinity. The subscription includes preferences regarding the geographical location of the notification, the types of emergency alerts, and the alert method, such as sounding off an alarm or siren, flashing lights, an instant message or telephone calls. The subscriber will provide a list of local phone numbers to the notification network, which will then monitor that location of any emergency situation it had registered for and notify it in case of an emergency. 3 SIP-based Emergency Notification System SIP can be extended to provide event notification [7]. SIP clients can subscribe to a remote SIP server and request notification from it. In the case of an event, the remote server will alert the client that an event has occurred. There are two main institutions that this system will deal with: a Subscriber and a Notifier. The Subscriber represents the institution that subscribes for emergency notification services. Conversely, the Notifier is the institution that issues notifications in case of emergencies. The following paragraphs will describe how SIP SUBSCRIBE/NOTIFY messages are sent between the Subscriber and the Notifier. 3.1 Subscribe/Notify Within the SIP architecture, the Subscriber subscribes to the Notifier indicating that it wants to be notified of certain events. An example of this might be when an official organization in a local community sub- scribes to certain emergency notification agencies. These agencies could be the local police department, specialized emergency monitoring centers or similar types of organizations. Thus, the Subscriber will send subscribe requests and receive event notifications and the Notifier will receive subscribe requests and send event notifications. The SIP message will have “SUBSCRIBE” or “NOTIFY” in the method section of the SIP request. A SUBSCRIBE message resembles that of the SIP INVITE. It will have a new Call-ID, “To” field which contains the URI of the header notifier, and “From” field which contains the URI of the Subscriber. The confirmation of a subscription will be sent by the Notifier in the form of a NOTIFY message. The SUBSCRIBE request must have one “Event” header in the Header field. This will specify the type of event that is being subscribed to. In the case that the Subscriber wants to subscribe to multiple events, it will send multiple SUBSCRIBE messages to the Notifier. An example of this is if a local community wants to be notified of emergency weather alerts and any chemical spills in the area by the local emergency monitoring station. It will send two SUBSCRIBE messages to the emergency monitoring station indicating its preferences. The SUBSCRIBE messages in this case will have two different Call-IDs, which will specify that they are two distinct subscriptions. There must be one “Contact” header, which will denote where NOTIFY requests should be sent to. The SUBSCRIBE message must also contain an “Expires” header which defines the duration of the subscription. If the Subscriber wants to refresh its subscription, it just sends another SUBSCRIBE message to the Notifier which will have the same Call-ID but a different CSeq number. Conversely, if it wants to unsubscribe, it sends a SUBSCRIBE message with the “Expires” field set to zero. 2 There is an optional message body of the SUBSCRIBE request, which can signify further details of no- tification. In this case, if a message body is present, then it should have a standardized grammar to automate the processing of the subscribe request in the Notifier. Thus various fields of the message could indicate preferences such as: method of alerting (e.g. sirens, IM message, telephone call), additional instructions for evacuation procedures and precautionary measures. If the message body is not present then the subscriber will expect the default emergency notification procedure sent to it. Once the SUBSCRIBE request has reached the Notifier, it will be processed and put in a database. The “Event” header must be checked to see if the Subscriber has subscribed to valid emergency events. The Notifier should also authenticate the message received to assure that it is from a certified local community official or related organization. Once it determines that the subscription message is valid, it sends a confir- mation NOTIFY containing the same Call-ID, local URI and remote URI that the SUBSCRIBE request had ordered. Otherwise, a message to the Subscriber is sent indicating an error. In the case of an emergency, the Notifier will send a NOTIFY message to the Subscriber. As mentioned above, the “Event” header will indicate the type of emergency that it is notifying. It must also contain a “Contact” header, which will allow the Subscriber to construct “Route” headers for further subscriptions. If there is no response from the Subscriber or an error message is received, the Notifier will remove that particular contact from the subscription list and send an alert to another contact within the same subscription. If all contacts fail, then the subscription is removed from the database. As in the SUBSCRIBE message, an optional body could be included which indicates the details of the emergency situation and the precautionary measures that must be taken. Figure 1 shows the SUBSCRIBE/NOTIFY message flow during an emergency notification. 3.2 SIP Authentication Authentication of the parties in question is a vital part of this system. In our application, the Notifier needs to verify that the Subscriber subscribing to it is an authorized official capable of handling emergency notifi- cations. Similarly, the Subscriber must authenticate the veracity of the emergency alerts sent by the Notifier to prevent false alarms from occurring. SIP provides authentication of messages similar to that of HTTP. When a SUBSCRIBE message is sent to the Notifier, the Notifier responds with a 401 message, contain- ing a “WWW-Authenticate” header, which challenges the authorization of the Subscriber. The Subscriber then responds with an “Authorization” header which includes an encrypted message including its username and password. Likewise, in the event of an emergency when the Subscriber gets alerted with a NOTIFY message, it challenges the authorization of the Notifier. There are two authentication schemes used: basic and digest. The basic authentication has weak security since the username and password is transmitted onto the network in plain sight. Thus, digest authentication is a better choice since it uses a few more name-value pairs besides the username and password and via cryptographic hashes, determines the authenticity of the Subscriber. A Subscriber needs to be aware of all the local emergency alerting agencies in its area. Below, we describe several different ways of setting the system up so that the Subscriber will obtain a password to log into the server maintained by the Notifier. 3 3.2.1 Third party provides credentials In this scheme, a third party operates a directory server with all the relevant information of the local area. It maps Subscribers to local Notifiers. The directory server should be monitored and maintained by govern- ment officials who recognize these subscribers as valid institutions, such as local police, fire departments or government agencies. The Subscribers and Notifiers should subscribe to the local directory server and signify the various emergency alerts they request or support and details of that nature. There is an optional header named “Allowed-Events”, which when specified by either the Subscriber or the Notifier, indicates the list of event packages supported by it.
Load more

Recommended publications
  • Lesson 1 Key-Terms Meanings: Internet Connectivity Principles
    Lesson 1 Key-Terms Meanings: Internet Connectivity Principles Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 1 Publs.: McGraw-Hill Education Header Words • Header words are placed as per the actions required at succeeding stages during communication from Application layer • Each header word at a layer consists of one or more header fields • The header fields specify the actions as per the protocol used Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 2 Publs.: McGraw-Hill Education Header fields • Fields specify a set of parameters encoded in a header • Parameters and their encoding as per the protocol used at that layer • For example, fourth word header field for 32-bit Source IP address in network layer using IP Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 3 Publs.: McGraw-Hill Education Protocol Header Field Example • Header field means bits in a header word placed at appropriate bit place, for example, place between bit 0 and bit 31 when a word has 32-bits. • First word fields b31-b16 for IP packet length in bytes, b15-b4 Service type and precedence and b3-b0 for IP version • Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 4 Publs.: McGraw-Hill Education IP Header • Header fields consist of parameters and their encodings which are as per the IP protocol • An internet layer protocol at a source or destination in TCP/IP suite of protocols Chapter-4 L01: "Internet of Things " , Raj Kamal, 2017 5 Publs.: McGraw-Hill Education TCP Header • Header fields consist of parameters and their encoding which are as
    [Show full text]
  • Usenet News HOWTO
    Usenet News HOWTO Shuvam Misra (usenet at starcomsoftware dot com) Revision History Revision 2.1 2002−08−20 Revised by: sm New sections on Security and Software History, lots of other small additions and cleanup Revision 2.0 2002−07−30 Revised by: sm Rewritten by new authors at Starcom Software Revision 1.4 1995−11−29 Revised by: vs Original document; authored by Vince Skahan. Usenet News HOWTO Table of Contents 1. What is the Usenet?........................................................................................................................................1 1.1. Discussion groups.............................................................................................................................1 1.2. How it works, loosely speaking........................................................................................................1 1.3. About sizes, volumes, and so on.......................................................................................................2 2. Principles of Operation...................................................................................................................................4 2.1. Newsgroups and articles...................................................................................................................4 2.2. Of readers and servers.......................................................................................................................6 2.3. Newsfeeds.........................................................................................................................................6
    [Show full text]
  • Cisco Unified Border Element H.323-To-SIP Internetworking Configuration Guide, Cisco IOS Release 12.4T Iii
    Cisco Unified Border Element H.323-to- SIP Internetworking Configuration Guide, Cisco IOS Release 12.4T Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Structure of IEEE 802.11 Packets at Various Physical Layers
    Appendix A: Structure of IEEE 802.11 Packets at Various Physical Layers This appendix gives a detailed description of the structure of packets in IEEE 802.11 for the different physical layers. 1. Packet Format of Frequency Hopping Spread-spectrum Physical Layer (FHSS PHY) The packet is made up of the following elements (Figure A.1): 1.1 Preamble It depends on the physical layer and includes: – Synch: a sequence of 80 bits alterning 0 and 1, used by the physical circuits to select the correct antenna (if more than one are in use), and correct offsets of frequency and synchronization. – SFD: start frame delimiter consists of a pattern of 16 bits: 0000 1100 1011 1101, used to define the beginning of the frame. 1.2 Physical Layer Convergence Protocol Header The Physical Layer Convergence Protocol (PLCP) header is always transmitted at 1 Mbps and carries some logical information used by the physical layer to decode the frame: – Length of word of PLCP PDU (PLW): representing the number of bytes in the packet, useful to the physical layer to detect correctly the end of the packet. – Flag of signalization PLCP (PSF): indicating the supported rate going from 1 to 4.5 Mbps with steps of 0.5 Mbps. Even though the standard gives the combinations of bits for PSF (see Table A.1) to support eight different rates, only the modulations for 1 and 2 Mbps have been defined. – Control error field (HEC): CRC field for error detection of 16 bits (or 32 bits). The polynomial generator used is G(x)=x16 + x12 + x5 +1.
    [Show full text]
  • Wireless Real-Time IP Services Enabled by Header Compression
    Wireless Real-time IP Services Enabled by Header Compression Krister Svanbrof, Hans Hannu f, Lars-Erik Jonsson f, Mikael Degermarkf f Ericsson Research f Dept. of CS & EE Ericsson Erisoft AB Lulei University of Technology Box 920, SE-971 28 Lulei, Sweden SE-971 87 Lulei, Sweden Abstract - The world of telecommunications is currently A major problem with voice over IP over wireless is the going through a shift of paradigm from circuit switched, large headers of the protocols used when sending speech connection oriented information transfer towards packet data over the Internet. An IPv4 packet with speech data switched, connection-less transfer. For application will have an IP header, a UDP header, and an RTP header independence and to decrease costs for transport and making a total of 20+8+12=40 octets. With IPv6, the IP switching it is attractive to go IP all the way over the air header is 40 octets for a total of 60 octets. The size of the ' interface to the end user equipment, i.e., to not terminate speech data depends on the codec, it can be 15-30 octets. the IP protocols before the air interface. A major reason to These numbers present a major reason for terminating the avoid using voice over IP over the air interface has, up to IP protocols before the air interface: the IP/UDP/RTP now, been the relatively large overhead imposed by the headers require a higher bit rate and would cause IP/UDP/RTP headers of voice packets. This paper presents inefficient use of the expensive radio spectrum.
    [Show full text]
  • How the Internet Works: Headers and Data; Packets and Routing 1
    Howthe Internet Works: Headers and Data; Packets and Routing 1. Transmitting Information through the Ages Howcan you get information from one place to another? How, for example, can you get an image from one place to another? Two hundred years ago, you would have todraw, paint, or print the image on paper or canvas, then carry, on foot, horseback, boat, or wagon, this analog version of view. One hundred years later,technology had advanced. By the early part of the 20th century,fax machines existed. With fax, you could drawthe image and send it overwires. What newscientific developments made that change possible? Here are a fewmilestones: YEAR WHATWHO WHERE 1800 Invents electric battery Allesandro Volta Italy 1820 Discovers electric current creates magnetism Hans O/rsted Denmark 1837 Invents electric telegraph Samuel Morse USA Before the battery,electricity was available from lightning and by shuffling across rugs on dry days, but that static electricity could not provide a steady,evenflow.Volta’sbattery made it possible to create a steady electrical current. Twenty years later,O/rsted discovered that a steady current of electricity produced a magnetic effect. Later,Morse connected a battery,aswitch, and a coil so that closing the switch at one end of the wire would create magnetism that would attract a piece of metal at the other end of the wire. By closing the switch for short and long durations, he was able to transmit bits a long distance. This system, the electric telegraph, made long-distance, all-weather,pri- vate communication possible. This technology led to the Internet.
    [Show full text]
  • 2045 Innosoft Obsoletes: 1521, 1522, 1590 N
    Network Working Group N. Freed Request for Comments: 2045 Innosoft Obsoletes: 1521, 1522, 1590 N. Borenstein Category: Standards Track First Virtual November 1996 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract STD 11, RFC 822, defines a message representation protocol specifying considerable detail about US-ASCII message headers, and leaves the message content, or message body, as flat US-ASCII text. This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for (1) textual message bodies in character sets other than US-ASCII, (2) an extensible set of different formats for non-textual message bodies, (3) multi-part message bodies, and (4) textual header information in character sets other than US-ASCII. These documents are based on earlier work documented in RFC 934, STD 11, and RFC 1049, but extends and revises them. Because RFC 822 said so little about message bodies, these documents are largely orthogonal to (rather than a revision of) RFC 822. This initial document specifies the various headers used to describe the structure of MIME messages. The second document, RFC 2046, defines the general structure of the MIME media typing system and defines an initial set of media types.
    [Show full text]
  • TSD Header and Footer Formal-T
    Remote Public Access Connectivity Information September 2011 Technology Services Division TABLE OF CONTENTS 1. Overview of Connectivity Options 3 Option #1 – SSL-Enabled TN3270 Option #2 – Business-to-Business Virtual Private Network (VPN) 2. SSL-Enabled TN3270 Specifications 5 3. Business-to-Business Virtual Private Network (VPN) Specifications 6 4. Glossary of Acronyms & Definitions 10 Remote Public Access Connectivity Information September 2011 Page 2 1. Overview of Connectivity Options The North Carolina Administrative Office of the Courts (AOC) has two options for the public to access the enterprise server. This document provides an overview of these options. Also, estimated costs have been provided where it is realistic to do so. Actual costs may vary. OPTION #1 – SSL-Enabled TN3270 This option is designed to provide a connection for individual workstations using an SSL- enabled TN3270 client over the Internet. It is a standards-based solution that utilizes various protocols for authentication and encryption. This option may be the most affordable choice for small businesses and individuals. Basic Customer Requirements: • An Internet connection • SSL-enabled TN3270 client software installed on each workstation requiring access NOTE: Many vendors sell SSL-enabled TN3270 client software. The approximate cost is $50 to $300 per workstation. The cost depends on which vendor you select and how many licenses you need. To find a vendor, you can google “TN3270 Emulation Software.” Many vendors also offer free 30-day trials. OPTION #2 – Business-to-Business Virtual Private Network (VPN) This option is designed for business-to-business (or site-to-site) VPN connections and is not intended to provide connections for individual workstations.
    [Show full text]
  • SMS Service Reference
    IceWarp Unified Communications SMS Service Reference Version 10.4 Printed on 16 April, 2012 Contents SMS Service 1 About .............................................................................................................................................................................. 3 Why Do I Need SMS Service? ............................................................................................................................. 3 What Hardware Will I Need? ............................................................................................................................. 3 Why Would I Want More Than One SMS Gateway? .......................................................................................... 4 GSM Service ................................................................................................................................................................... 5 Tested and Supported Products ........................................................................................................................ 5 HTTP Gateway ................................................................................................................................................................ 6 Tested Products ................................................................................................................................................. 6 Reference ......................................................................................................................................................................
    [Show full text]
  • Module 6 Internet Layer Meghanathan Dr
    Module 6 Internet Layer Meghanathan Dr. Natarajan Meghanathan Associate ProfessorCopyrights of Computer Science Jackson StateAll University, Jackson, MS 39232 E-mail: [email protected] Module Topics • 6.1 IP Header • 6.2 IP Datagram Fragmentation • 6.3 IP Datagram Forwarding • 6.4 IP Auxiliary Protocols and Meghanathan Technologies Copyrights – ARP, DHCP, ICMP, VPN, NA(P)T All • 6.5 IPv6 Natarajan Meghanathan Copyrights All Natarajan 6.1 IP Header Meghanathan Copyrights All Natarajan IP Header Format (v4) © 2009 Pearson Education Inc., Upper Saddle River, NJ. All rights reserved. IP Header Format • VERS – Each datagram begins with a 4-bit protocol version number • H.LEN – 4-bit header length field specifies the number of 32-bit quantities in the header. The header size should be a multiple of 32. • The minimum integer value for the IP header length is 5 as the top 5 32-bit rows of the IP header are mandatory for inclusion. Hence, the minimum size of the IP header is 5 * 32-bits = 5 * 4 bytes = 20 bytes. • The maximum integer value for the IP header length (with 4 bits for the field) would be 15, necessitating the Options field to be at most 10 32- bit rows. The maximum size of theMeghanathan IP header is 15 * 32-bits = 15 * 4 bytes = 60 bytes. Copyrights • SERVICE TYPE – used to specify whether the sender prefers the datagram to be sentAll over a path that has minimum delay or maximum throughput, etc. A routerNatarajan that has multiple paths to the destination, can apply these service type preferences to select the most suitable path.
    [Show full text]
  • Ipv6 Header Format: • Traffic Class: Similar Role As TOS Field in Ipv4
    CS 422 Park IPv6 header format: versiontraffic class flow label 4 8 20 payload length next header hop limit 16 8 8 source address 128 destination address 128 • traffic class: similar role as TOS field in IPv4 • flow label: flow label + source address → per-flow traffic management → significant extra bits • next header: similar to IPv4 protocol field → plus double duty for option headers • note missing fields CS 422 Park • Dynamically assigned IP addresses → share an IP address pool → reusable → e.g., DHCP (dynamic host configuration protocol) → UDP-based client/server protocol (ports 67/68) → note: process/daemon based service → used by access ISPs, enterprises, etc. → where are the IP address savings? Old days of non-permanent dial-up modems ::: CS 422 Park • Network address translation (NAT) → dynamically assigned + address translation → private vs. public IP address → private: Internet routers discard them → e.g., 192.168.0.0 is private → 10.x.x.x are also private → useful for home networks, small businesses → also industry and university research labs CS 422 Park Example: network testbed intranet (HAAS G50) • intranet NICs have 10.0.0.0/24 addresses → each interface: a separate subnet • only one of the routers connected to Internet CS 422 Park • NAPT (NAT + port) → variant of NAT: borrow src port field as address bits Ex.: 192.168.10.10 and 192.168.10.11 both map to 128.10.27.10 but → 192.168.10.10 maps to 128.10.26.10:6001 → 192.168.10.11 maps to 128.10.26.10:6002 What about port numbers of 192.168.10.10 and 192.168.10.11? → e.g., client process
    [Show full text]
  • IP Packet Switching Reading: Sect 4.1.1 – 4.1.4, 4.3.5
    IP Packet Switching Reading: Sect 4.1.1 – 4.1.4, 4.3.5 COS 461: Computer Networks Spring 2011 Mike Freedman hp://www.cs.princeton.edu/courses/archive/spring11/cos461/ 2 Goals of Today’s Lecture • Connecvity – Circuit switching – Packet switching • IP service model – Best‐effort packet delivery – IP as the Internet’s “narrow waist” – Design philosophy of IP • IP packet structure – Fields in the IP header – Traceroute using TTL field – Source‐address spoofing 3 Recall the Internet layering model host host HTTP message HTTP HTTP TCP segment TCP TCP router router IP packet IP packet IP packet IP IP IP IP Ethernet Ethernet SONET SONET Ethernet Ethernet interface interface interface interface interface interface 4 Review: Circuit Switching ‐ Mulplexing a Link • Time‐division • Frequency‐division – Each circuit allocated – Each circuit allocated certain me slots certain frequencies time frequency time 5 Circuit Switching (e.g., Phone Network) 1. Source establishes connecon to desnaon – Node along the path store connecon info – Nodes may reserve resources for the connecon 2. Source sends data over the connecon – No desnaon address, since nodes know path 3. Source tears down connecon when done 6 Circuit Switching With Human Operator “Operator, please Telephone connect me to switch 555-1212” 7 Advantages of Circuit Switching • Guaranteed bandwidth – Predictable performance: not “best effort” • Simple abstracon – Reliable communicaon channel between hosts – No worries about lost or out‐of‐order packets • Simple forwarding – Forwarding based on me slot
    [Show full text]