The document discusses Mobile IP, which allows mobile devices to change their point of connection to the internet without changing their IP address. It describes key concepts like the home agent, foreign agent, care-of address, and registration process. Mobile IP addresses issues like triangular routing and proposes optimizations like reverse tunneling to improve efficiency when a mobile node changes locations.
WANs use carrier services to connect organizational locations and provide access to external services and remote users. WANs carry various traffic types like voice, data, and video, with telephone and data services being most common. Physical equipment includes customer premises equipment (CPE) connected to the service provider's central office via local loops.
Mobile IP uses encapsulation and tunneling to forward data to mobile nodes. When a mobile node registers with its home agent while connected to a foreign network, the home agent intercepts datagrams for the mobile node and encapsulates them by adding a new IP header. This creates a tunnel to the mobile node's care-of address. Common encapsulation methods include IP-in-IP, minimal encapsulation, and GRE. Tunneling allows datagrams to be forwarded across networks while hiding the details of the encapsulated datagram. Loops can occur if the source IP matches the tunnel endpoint, so routers discard these datagrams.
The document discusses various protocols and approaches for improving the performance of TCP over wireless networks. It notes that wireless networks have higher bit error rates, lower bandwidth, and mobility issues compared to wired networks. Several protocols are described that aim to distinguish wireless losses from congestion losses to avoid unnecessary TCP reactions:
- Indirect TCP splits the connection and handles losses locally at the base station. Snoop caches packets at the base station for retransmission.
- Mobile TCP further splits the connection and has the base station defer acknowledgments. It can also inform the sender about handoffs versus interface switches.
- Multiple acknowledgments uses two types of ACKs to isolate the wireless and wired portions of the network.
-
This document discusses TCP over wireless networks. It explains that TCP was designed for fixed networks with low delay and errors, but wireless networks have high delay, errors and variable bandwidth. This causes TCP to perform poorly over wireless. The document outlines various techniques to improve TCP performance over wireless like Fast Retransmit and Recovery, Slow Start proposals with larger initial windows, ACK counting and ACK-every-segment. It also discusses protocols like HTTP, RLP that operate between TCP and the wireless transmission layers.
This document discusses subnetting, supernetting, and classless addressing. It defines subnetting as dividing a network into smaller subnetworks, and supernetting as aggregating multiple network blocks into a larger block. The key points are:
- Subnetting allows a network to have multiple hierarchical levels and partitions addresses into subnets. Supernetting combines multiple blocks into a larger block.
- The subnet or supernet mask is used with the address to determine the network or block boundaries.
- Subnets and supernet blocks must have a size that is a power of 2, and the starting address must be divisible by the block size.
- Classless addressing uses CIDR notation of an address
The document discusses Mobile IP, which allows mobile devices to change their point of connection to the internet without changing their IP address. It describes key concepts like the home agent, foreign agent, care-of address, and registration process. Mobile IP addresses issues like triangular routing and proposes optimizations like reverse tunneling to improve efficiency when a mobile node changes locations.
WANs use carrier services to connect organizational locations and provide access to external services and remote users. WANs carry various traffic types like voice, data, and video, with telephone and data services being most common. Physical equipment includes customer premises equipment (CPE) connected to the service provider's central office via local loops.
Mobile IP uses encapsulation and tunneling to forward data to mobile nodes. When a mobile node registers with its home agent while connected to a foreign network, the home agent intercepts datagrams for the mobile node and encapsulates them by adding a new IP header. This creates a tunnel to the mobile node's care-of address. Common encapsulation methods include IP-in-IP, minimal encapsulation, and GRE. Tunneling allows datagrams to be forwarded across networks while hiding the details of the encapsulated datagram. Loops can occur if the source IP matches the tunnel endpoint, so routers discard these datagrams.
The document discusses various protocols and approaches for improving the performance of TCP over wireless networks. It notes that wireless networks have higher bit error rates, lower bandwidth, and mobility issues compared to wired networks. Several protocols are described that aim to distinguish wireless losses from congestion losses to avoid unnecessary TCP reactions:
- Indirect TCP splits the connection and handles losses locally at the base station. Snoop caches packets at the base station for retransmission.
- Mobile TCP further splits the connection and has the base station defer acknowledgments. It can also inform the sender about handoffs versus interface switches.
- Multiple acknowledgments uses two types of ACKs to isolate the wireless and wired portions of the network.
-
This document discusses TCP over wireless networks. It explains that TCP was designed for fixed networks with low delay and errors, but wireless networks have high delay, errors and variable bandwidth. This causes TCP to perform poorly over wireless. The document outlines various techniques to improve TCP performance over wireless like Fast Retransmit and Recovery, Slow Start proposals with larger initial windows, ACK counting and ACK-every-segment. It also discusses protocols like HTTP, RLP that operate between TCP and the wireless transmission layers.
This document discusses subnetting, supernetting, and classless addressing. It defines subnetting as dividing a network into smaller subnetworks, and supernetting as aggregating multiple network blocks into a larger block. The key points are:
- Subnetting allows a network to have multiple hierarchical levels and partitions addresses into subnets. Supernetting combines multiple blocks into a larger block.
- The subnet or supernet mask is used with the address to determine the network or block boundaries.
- Subnets and supernet blocks must have a size that is a power of 2, and the starting address must be divisible by the block size.
- Classless addressing uses CIDR notation of an address
This document provides an overview of mobility management and key concepts in IP mobility. It discusses macro mobility protocols including Mobile IPv6 (MIPv6) and Fast Handovers for MIPv6 (FMIPv6), as well as micro-mobility protocols like Cellular IP, HAWAII, and Hierarchical Mobile IPv6 (HMIPv6). The introduction defines IP mobility and the need for mobility support in IP given that the current IP address model assumes fixed locations. It also describes how Mobile IP allows devices to move between networks while keeping the same IP address.
NAT is used to translate private IP addresses to public IP addresses to allow access to the internet. There are different types of NAT including static NAT for one-to-one mapping, dynamic NAT for mapping multiple private addresses to public addresses from a pool, and NAT overload/PAT which maps multiple private addresses to a single public address using port addressing. The document provides configuration examples for static, dynamic, and overload NAT on a Cisco router.
LTE Basic Parameters, Data Rates, Duplexing & Accessing, Modulation, Coding & MIMO, Explanation of different nodes and Advantage & Disadvantages of different nodes.
This document discusses mobility management (MM) in GPRS and UMTS networks. It describes the different MM states in GPRS (IDLE, STANDBY, READY) and UMTS (PMM-DETACHED, PMM-IDLE, PMM-CONNECTED). The MM contexts maintained by the MS, SGSN, and HLR/AUC are also outlined. Periodic and normal location update procedures performed by the MS to update its location are explained.
Mobile IP is a protocol that allows mobile devices to change location while maintaining the same IP address. It works by assigning mobile devices a permanent home address and registering a care-of address with their home agent when visiting foreign networks. The home agent intercepts packets destined for the mobile device's home address and tunnels them to its current care-of address. This allows the mobile device to stay connected to the internet as it moves between networks while keeping the same home address.
This document summarizes the Bluetooth protocol stack. It discusses the baseband protocols, link manager protocol, L2CAP, service discovery protocol, and various adopted protocols like RFCOMM, TCS, PPP, TCP/IP, WAP, and OBEX. The baseband and link control layer control the physical RF link and links can be either SCO or ACL. The link manager protocol handles link setup and power modes. L2CAP provides multiplexing and segmentation. Service discovery allows finding and searching for Bluetooth services. RFCOMM provides emulation and transport capabilities for cables replacement. TCS deals with telephony control and configurations. Adopted protocols allow communication with other Bluetooth devices and bringing internet to phones.
Mobile Originated Call Process in Simple WordsAssim Mubder
Call Setup
Different procedures are necessary depending on the initiating and terminating party:
Mobile Originating Call MOC: Call setup, which are initiated by an MS
Mobile Terminating Call MTC: Call setup, where an MS is the called party
Mobile Mobile Call MMC: Call: setup between two mobile subscribers; MMC thus consists of the execution of a MOC and a MTC one after the other.
Mobile Internal Call MIC: a special case of MMC; both MSs are in the same MSC area, possibly even in the same cell.
CCNA Routing Fundamentals - EIGRP, OSPF and RIPsushmil123
- Basics of Routing
- Static Routing/Dynamic Routing
- Classification of Dynamic Routing
- Administrative Distance and Metric
- Link State Routing and Distance Vector Routing
- Routing Information Protocol (RIP)
- Enhanced Interior Gateway Routing Protocol (EIGRP)
- Open Shortest Path First (OSPF)
Mobile Network Layer protocols and mechanisms allow nodes to change their point of attachment to different networks while maintaining ongoing communication. Key concepts include:
- Mobile IP adds mobility support to IP, allowing nodes to use the same IP address even when changing networks. It relies on home agents and care-of addresses.
- Registration allows mobile nodes to inform their home agent of their current location when visiting foreign networks. Tunneling and encapsulation techniques are used to forward packets to mobile nodes' current locations.
- Various routing protocols like DSDV have been developed for mobile ad hoc networks which have no fixed infrastructure and dynamic topologies.
The document discusses address resolution protocol (ARP) which maps logical IP addresses to physical MAC addresses on a local area network. It explains that ARP broadcasts a request to find the MAC address associated with a given IP address, and the device with that IP address responds with its MAC. This dynamic address mapping is stored in an ARP cache for future use. It also describes how different network protocols may use ARP or similar methods to perform address mapping between logical and physical addresses.
This document discusses mobile ad-hoc networks (MANETs). It defines MANETs as collections of wireless mobile nodes that can dynamically form a network without any centralized administration. The document outlines the characteristics, mechanisms, transmission standards, routing protocols, applications, and future aspects of MANETs. It explains that MANETs are self-configuring, infrastructureless networks suitable for situations where fixed networks are not available or are too expensive to deploy.
IEEE 802.11 is a set of media access control (MAC) and physical layer (PHY) specifications for implementing wireless local area network (WLAN) computer communication in the 2.4, 3.6, 5, and 60 GHz frequency bands. It provides connectivity through wireless stations organized into basic service sets (BSSs) that together form an extended service set (ESS). Key components include the MAC sublayer, physical layers using technologies like direct sequence spread spectrum (DSSS), and services that enable station mobility and quality of service (QoS).
The GSM radio interface uses FDMA to divide the frequency band into channels and TDMA to divide each frequency channel into time slots to allow multiple users, with each user assigned a single time slot. The normal GSM burst carries digitized voice data or other information in a 57-bit data field, and includes guard periods and training sequences to help with timing synchronization and equalization between the mobile station and base transceiver station. GSM networks operate at different frequencies around the world, with GSM-900 being most common in Europe and other parts of the world.
This document provides an introduction to the IEEE 802.11 wireless LAN standard. It outlines the standard's architecture including components like stations, basic service sets, extended service sets, and access points. It describes the medium access control sublayer which uses distributed coordination function and point coordination function to provide reliable data delivery and fair medium sharing. It also briefly discusses the physical layer and typical wireless LAN products.
Mobile IP allows mobile nodes to change their point of attachment between IP networks while maintaining ongoing connections. It defines entities like mobile nodes, home agents, and foreign agents to facilitate IP packet delivery to the mobile node's current location. The key operations in Mobile IP are agent discovery, registration of the mobile node's new location with its home agent, and tunneling of packets from the home agent to the foreign agent or mobile node's care-of address.
GPRS Architecture and its components are covered extensively.
The slides give a little information about gprs and also gets into deeper explanation of its architecture.
IT8602 Mobile Communication - Unit I Introductionpkaviya
This document provides an introduction and overview of mobile computing and related technologies. It begins with definitions of mobile computing and discusses characteristics like ubiquity, location awareness, and adaptation. It then covers applications of mobile computing like in vehicles, emergencies, and business. The document discusses generations of mobile communication technologies and different multiple access protocols like SDMA, TDMA, FDMA, and CDMA. It provides details on TDMA protocols including fixed TDM, Aloha, slotted Aloha, and CSMA.
This document discusses Mobile IP, which allows mobile devices to change their point of attachment between different networks while maintaining ongoing connections. It describes the key entities in Mobile IP including the Mobile Node, Home Agent, Foreign Agent, and Correspondent Node. The operations of Mobile IP are summarized, including agent discovery, registration processes, encapsulation and decapsulation of packets, and the tables maintained on routers. Problems with Mobile IP and its applications are also briefly mentioned.
This document provides an overview of mobility management and key concepts in IP mobility. It discusses macro mobility protocols including Mobile IPv6 (MIPv6) and Fast Handovers for MIPv6 (FMIPv6), as well as micro-mobility protocols like Cellular IP, HAWAII, and Hierarchical Mobile IPv6 (HMIPv6). The introduction defines IP mobility and the need for mobility support in IP given that the current IP address model assumes fixed locations. It also describes how Mobile IP allows devices to move between networks while keeping the same IP address.
NAT is used to translate private IP addresses to public IP addresses to allow access to the internet. There are different types of NAT including static NAT for one-to-one mapping, dynamic NAT for mapping multiple private addresses to public addresses from a pool, and NAT overload/PAT which maps multiple private addresses to a single public address using port addressing. The document provides configuration examples for static, dynamic, and overload NAT on a Cisco router.
LTE Basic Parameters, Data Rates, Duplexing & Accessing, Modulation, Coding & MIMO, Explanation of different nodes and Advantage & Disadvantages of different nodes.
This document discusses mobility management (MM) in GPRS and UMTS networks. It describes the different MM states in GPRS (IDLE, STANDBY, READY) and UMTS (PMM-DETACHED, PMM-IDLE, PMM-CONNECTED). The MM contexts maintained by the MS, SGSN, and HLR/AUC are also outlined. Periodic and normal location update procedures performed by the MS to update its location are explained.
Mobile IP is a protocol that allows mobile devices to change location while maintaining the same IP address. It works by assigning mobile devices a permanent home address and registering a care-of address with their home agent when visiting foreign networks. The home agent intercepts packets destined for the mobile device's home address and tunnels them to its current care-of address. This allows the mobile device to stay connected to the internet as it moves between networks while keeping the same home address.
This document summarizes the Bluetooth protocol stack. It discusses the baseband protocols, link manager protocol, L2CAP, service discovery protocol, and various adopted protocols like RFCOMM, TCS, PPP, TCP/IP, WAP, and OBEX. The baseband and link control layer control the physical RF link and links can be either SCO or ACL. The link manager protocol handles link setup and power modes. L2CAP provides multiplexing and segmentation. Service discovery allows finding and searching for Bluetooth services. RFCOMM provides emulation and transport capabilities for cables replacement. TCS deals with telephony control and configurations. Adopted protocols allow communication with other Bluetooth devices and bringing internet to phones.
Mobile Originated Call Process in Simple WordsAssim Mubder
Call Setup
Different procedures are necessary depending on the initiating and terminating party:
Mobile Originating Call MOC: Call setup, which are initiated by an MS
Mobile Terminating Call MTC: Call setup, where an MS is the called party
Mobile Mobile Call MMC: Call: setup between two mobile subscribers; MMC thus consists of the execution of a MOC and a MTC one after the other.
Mobile Internal Call MIC: a special case of MMC; both MSs are in the same MSC area, possibly even in the same cell.
CCNA Routing Fundamentals - EIGRP, OSPF and RIPsushmil123
- Basics of Routing
- Static Routing/Dynamic Routing
- Classification of Dynamic Routing
- Administrative Distance and Metric
- Link State Routing and Distance Vector Routing
- Routing Information Protocol (RIP)
- Enhanced Interior Gateway Routing Protocol (EIGRP)
- Open Shortest Path First (OSPF)
Mobile Network Layer protocols and mechanisms allow nodes to change their point of attachment to different networks while maintaining ongoing communication. Key concepts include:
- Mobile IP adds mobility support to IP, allowing nodes to use the same IP address even when changing networks. It relies on home agents and care-of addresses.
- Registration allows mobile nodes to inform their home agent of their current location when visiting foreign networks. Tunneling and encapsulation techniques are used to forward packets to mobile nodes' current locations.
- Various routing protocols like DSDV have been developed for mobile ad hoc networks which have no fixed infrastructure and dynamic topologies.
The document discusses address resolution protocol (ARP) which maps logical IP addresses to physical MAC addresses on a local area network. It explains that ARP broadcasts a request to find the MAC address associated with a given IP address, and the device with that IP address responds with its MAC. This dynamic address mapping is stored in an ARP cache for future use. It also describes how different network protocols may use ARP or similar methods to perform address mapping between logical and physical addresses.
This document discusses mobile ad-hoc networks (MANETs). It defines MANETs as collections of wireless mobile nodes that can dynamically form a network without any centralized administration. The document outlines the characteristics, mechanisms, transmission standards, routing protocols, applications, and future aspects of MANETs. It explains that MANETs are self-configuring, infrastructureless networks suitable for situations where fixed networks are not available or are too expensive to deploy.
IEEE 802.11 is a set of media access control (MAC) and physical layer (PHY) specifications for implementing wireless local area network (WLAN) computer communication in the 2.4, 3.6, 5, and 60 GHz frequency bands. It provides connectivity through wireless stations organized into basic service sets (BSSs) that together form an extended service set (ESS). Key components include the MAC sublayer, physical layers using technologies like direct sequence spread spectrum (DSSS), and services that enable station mobility and quality of service (QoS).
The GSM radio interface uses FDMA to divide the frequency band into channels and TDMA to divide each frequency channel into time slots to allow multiple users, with each user assigned a single time slot. The normal GSM burst carries digitized voice data or other information in a 57-bit data field, and includes guard periods and training sequences to help with timing synchronization and equalization between the mobile station and base transceiver station. GSM networks operate at different frequencies around the world, with GSM-900 being most common in Europe and other parts of the world.
This document provides an introduction to the IEEE 802.11 wireless LAN standard. It outlines the standard's architecture including components like stations, basic service sets, extended service sets, and access points. It describes the medium access control sublayer which uses distributed coordination function and point coordination function to provide reliable data delivery and fair medium sharing. It also briefly discusses the physical layer and typical wireless LAN products.
Mobile IP allows mobile nodes to change their point of attachment between IP networks while maintaining ongoing connections. It defines entities like mobile nodes, home agents, and foreign agents to facilitate IP packet delivery to the mobile node's current location. The key operations in Mobile IP are agent discovery, registration of the mobile node's new location with its home agent, and tunneling of packets from the home agent to the foreign agent or mobile node's care-of address.
GPRS Architecture and its components are covered extensively.
The slides give a little information about gprs and also gets into deeper explanation of its architecture.
IT8602 Mobile Communication - Unit I Introductionpkaviya
This document provides an introduction and overview of mobile computing and related technologies. It begins with definitions of mobile computing and discusses characteristics like ubiquity, location awareness, and adaptation. It then covers applications of mobile computing like in vehicles, emergencies, and business. The document discusses generations of mobile communication technologies and different multiple access protocols like SDMA, TDMA, FDMA, and CDMA. It provides details on TDMA protocols including fixed TDM, Aloha, slotted Aloha, and CSMA.
This document discusses Mobile IP, which allows mobile devices to change their point of attachment between different networks while maintaining ongoing connections. It describes the key entities in Mobile IP including the Mobile Node, Home Agent, Foreign Agent, and Correspondent Node. The operations of Mobile IP are summarized, including agent discovery, registration processes, encapsulation and decapsulation of packets, and the tables maintained on routers. Problems with Mobile IP and its applications are also briefly mentioned.
UNIT IV MOBILE NETWORK AND TRANSPORT LAYERS
Mobile IP – Dynamic Host Configuration Protocol-Mobile Ad Hoc Routing Protocols–Multicast routing-TCP over Wireless Networks – Indirect TCP – Snooping TCP – Mobile TCP – Fast Retransmit / Fast Recovery – Transmission/Timeout Freezing-Selective Retransmission – Transaction Oriented TCP- TCP over 2.5 / 3G wireless Networks
This document provides information about installing and using GloMoSim, a scalable simulation environment for large wireless and wired communication networks. It describes the key layers in GloMoSim including radio, MAC, network, transport and application layers. It also outlines the modular GloMoSim library and supported protocols. The document discusses installing GloMoSim on Windows which involves setting environment variables and extracting the software. It also covers installing on Unix/Linux which involves customizing environment variables and running make files.
mobile ip, Mobile COmmunication Internet ProtocolGaurav Dwivedi
Mobile IP adds mobility support to the Internet network layer protocol IP. It allows nodes to continue receiving datagrams no matter where they are attached to the Internet. Mobile IP uses home agents and foreign agents to tunnel packets to a mobile node's current location, represented by its care-of address. When away from its home network, a mobile node registers its care-of address with its home agent. The home agent intercepts packets destined for the mobile node and tunnels them to the care-of address using encapsulation. This allows the mobile node to maintain its home IP address while connecting via foreign networks.
Mobile IP allows mobile nodes to roam between networks while maintaining ongoing connections. It uses home and foreign agents to manage registration and tunnel packets sent to a mobile node's permanent home address to its current location. However, this can result in inefficient triangle routing. Mobile IP also faces challenges from security vulnerabilities and frequent location updates.
The document provides step-by-step instructions for using Qualnet 5.0 software to design a wireless network simulation with 4 nodes, a CBR connection between nodes 1 and 4, and configure properties of the wireless network, physical layer, MAC layer, network layer, routing protocols, scenario, and running the simulation and analysis tools.
This document provides instructions for using the command line interface for Qualnet 5.0 simulation software. It outlines steps such as changing to the bin directory, opening configuration files, running the qualnet.exe file, monitoring execution, and running an example radio_range file.
The document provides step-by-step instructions for using Qualnet 5.0 software to design a wireless network simulation with 4 nodes, a CBR connection between nodes 1 and 4, and configure properties of the wireless network, physical layer, MAC layer, network layer, routing protocols, scenario, and running the simulation and analysis tools.
(1) The document discusses the various topics related to electronics and instrumentation engineering including aptitude, attitude, attributes of engineers, graduate attributes, technical and soft skills, bridging industry-academic gap, learning environment, levels of learning, and expected profile of IT employees.
(2) It also outlines the core subjects of electronics and instrumentation engineering such as instrumentation, control, electrical, electronics, computer, mechanical, management, and societal subjects.
(3) Important subjects discussed include physics, chemistry, mathematics, programming, civil and mechanical engineering, circuit theory, and specialization subjects in different domains of electronics and instrumentation.
Mobile computing allows users to access network services and computational resources from anywhere using portable devices like laptops, smartphones, and tablets. It is defined as computing using portable devices that maintain network connectivity while on the move. Mobile computing faces challenges like low bandwidth, disconnection, and security risks compared to wired networks. Future advancements may include increased use of artificial intelligence and integrated circuits to develop more compact devices with faster processors. Mobile computing has transitioned through generations from 1G analog cellular to 2G digital cellular to 3G broadband cellular and beyond to 4G and 5G.
Mobile Device Operating Systems – Special Constrains & Requirements – Commercial Mobile Operating Systems – Software Development Kit: iOS, Android, BlackBerry, Windows Phone – M-Commerce – Structure – Pros & Cons – Mobile Payment System – Security Issues.
UNIT V MOBILE PLATFORMS AND APPLICATIONS
Mobile Device Operating Systems – Special Constrains & Requirements – Commercial Mobile Operating Systems – Software Development Kit: iOS, Android, BlackBerry, Windows Phone – M-Commerce – Structure – Pros & Cons – Mobile Payment System – Security Issues.
MOBILE INTERNET PROTOCOL AND TRANSPORT LAYER
Overview of Mobile IP – Features of Mobile IP – Key Mechanism in Mobile IP – route Optimization. Overview of TCP/IP – Architecture of TCP/IP- Adaptation of TCP Window – Improvement in TCP Performance.
UNIT IV MOBILE AD-HOC NETWORKS
Ad-Hoc Basic Concepts – Characteristics – Applications – Design Issues – Routing – Essential of Traditional Routing Protocols –Popular Routing Protocols – Vehicular Ad Hoc networks ( VANET) – MANET Vs VANET – Security
This document provides an overview of high speed networks including Frame Relay networks, Asynchronous Transfer Mode (ATM), ATM protocol architecture, logical connections, cells, service categories, and high speed LANs. It discusses the architecture, user data transfer, and call control of Frame Relay networks. For ATM, it describes the protocol model, logical connections, cells, adaptation layer, and service categories. It also provides an introduction to emerging high speed LAN technologies.
Unit - I
Mobile Computing – Mobile Computing Vs wireless Networking – Mobile Computing Applications – Characteristics of Mobile computing – Structure of Mobile Computing Application. MAC Protocols – Wireless MAC Issues – Fixed Assignment Schemes – Random Assignment Schemes – Reservation Based Schemes.
Mobile IP provides network layer mobility by allowing mobile nodes to change their point of attachment to the network without changing their IP address. It works by tunneling packets destined for a mobile node to its current location through its home agent and foreign agent. The mobile node registers its care-of address with its home agent so that its home agent knows where to tunnel packets. This allows seamless connectivity as the mobile node moves between networks.
This document discusses Mobile IP and related concepts. It begins by outlining the motivation for Mobile IP, including issues with changing IP addresses or routing tables when a mobile node changes locations. It then defines key terminology like mobile node, home agent, foreign agent, and care-of address. It explains how registration and encapsulation allow a mobile node to maintain its home IP address as it roams. Finally, it discusses security considerations, problems, and the relationship between Mobile IP and IPv6.
WIRELESS NETWORKS EC6802 BABU unit 1 & 2 PPTbabuece
WIRELESS NETWORKS EC6802 BABU unit 1 & 2 PPT
BABU M
ASST PROFESSOR
DEPARTMENT OD ELECTRONICS AND COMMUNICATION ENGINEERING
RMK COLLEGE OF ENGINEERING AND TECHNOLOGY
CHENNAI
THIRUVALLUR DISTRICT
UNIT I WIRELESS LAN 9 Introduction-WLAN technologies: Infrared, UHF narrowband, spread spectrum -IEEE802.11: System architecture, protocol architecture, physical layer, MAC layer, 802.11b, 802.11a – Hiper LAN: WATM, BRAN, HiperLAN2 – Bluetooth: Architecture, Radio Layer, Baseband layer, Link manager Protocol, security - IEEE802.16-WIMAX: Physical layer, MAC, Spectrum allocation for WIMAX UNIT II MOBILE NETWORK LAYER 9 Introduction - Mobile IP: IP packet delivery, Agent discovery, tunneling and encapsulation, IPV6-Network layer in the internet- Mobile IP session initiation protocol - mobile ad-hoc network: Routing, Destination Sequence distance vector, Dynamic source routing UNIT III MOBILE TRANSPORT LAYER 9 TCP enhancements for wireless protocols - Traditional TCP: Congestion control, fast retransmit/fast recovery, Implications of mobility - Classical TCP improvements: Indirect TCP, Snooping TCP, Mobile TCP, Time out freezing, Selective retransmission, Transaction oriented TCP - TCP over 3G wireless networks. UNIT IV WIRELESS WIDE AREA NETWORK 9 Overview of UTMS Terrestrial Radio access network-UMTS Core network Architecture: 3G-MSC, 3G-SGSN, 3G-GGSN, SMS-GMSC/SMS-IWMSC, Firewall, DNS/DHCP-High speed Downlink packet access (HSDPA)- LTE network architecture and protocol. UNIT V 4G NETWORKS 9 Introduction – 4G vision – 4G features and challenges - Applications of 4G – 4G Technologies: Multicarrier Modulation, Smart antenna techniques, OFDM-MIMO systems, Adaptive Modulation and coding with time slot scheduler, Cognitive Radio.
UNIT I WIRELESS LAN 9 Introduction-WLAN technologies: Infrared, UHF narrowband, spread spectrum -IEEE802.11: System architecture, protocol architecture, physical layer, MAC layer, 802.11b, 802.11a – Hiper LAN: WATM, BRAN, HiperLAN2 – Bluetooth: Architecture, Radio Layer, Baseband layer, Link manager Protocol, security - IEEE802.16-WIMAX: Physical layer, MAC, Spectrum allocation for WIMAX UNIT II MOBILE NETWORK LAYER 9 Introduction - Mobile IP: IP packet delivery, Agent discovery, tunneling and encapsulation, IPV6-Network layer in the internet- Mobile IP session initiation protocol - mobile ad-hoc network: Routing, Destination Sequence distance vector, Dynamic source routing UNIT III MOBILE TRANSPORT LAYER 9 TCP enhancements for wireless protocols - Traditional TCP: Congestion control, fast retransmit/fast recovery, Implications of mobility - Classical TCP improvements: Indirect TCP, Snooping TCP, Mobile TCP, Time out freezing, Selective retransmission, Transaction oriented TCP - TCP over 3G wireless networks. UNIT IV WIRELESS WIDE AREA NETWORK 9 Overview of UTMS Terrestrial Radio access network-UMTS Core network Architecture: 3G-MSC, 3G-SGSN, 3G-GGSN, SMS-GMSC/SMS-IWMSC, Firewall, DNS/DHCP-High speed Downlink packet access (HSDPA)- LTE network architecture and protocol. UNIT V 4G NETWORKS 9 Introduction – 4G vision – 4G features and challenges - Applications of 4G – 4G Technologies: Multicarrier Modulation, Smart antenna techniques, OFDM-MIMO systems, Adaptive Modulation and coding with time slot scheduler, Cognitive Radio.
Mobile IP allows mobile nodes to change their point of connection to the Internet while maintaining the same IP address. It uses home and foreign agents and care-of addresses. A mobile node registers its care-of address with its home agent, which then tunnels packets to the mobile node's current location. Dynamic Host Configuration Protocol (DHCP) can be used to automatically obtain a care-of address.
Mobile IP is an open standard that allows devices to change networks while maintaining the same IP address. This ensures ongoing connections and applications are not dropped when switching networks. It works by assigning two IP addresses - a static home address and a care-of address that changes based on the device's current network location. When the device roams away from its home network, its traffic is encapsulated and tunneled through its home network to maintain connectivity using its home address. Mobile IP provides mobility across IP networks while cellular IP focuses on optimizing mobility within cellular networks.
Mobile IP is an open standard that allows devices to change networks while maintaining the same IP address. This allows ongoing connections and applications to continue without being dropped when the device roams to a new network. Mobile IP works by assigning the device two IP addresses - a home address that stays the same and a care-of address that changes based on the new network point of attachment. Tunneling is used to forward packets to the device's current location. Mobile IPv6 improves upon Mobile IPv4 by simplifying the mobility management process and integrating support for route optimization.
This document discusses network protocols for mobile communications, focusing on Mobile IP. It provides motivation for Mobile IP by explaining limitations of standard IP routing with mobile nodes. Key concepts are introduced, including mobile node, home agent, foreign agent, and care-of address. Mobile IP operations are illustrated, such as registration, encapsulation for packet tunneling, and optimization techniques like reverse tunneling. Implementation details are covered along with integration with IPv6.
Mobile IP allows mobile nodes to change their point of connection to the Internet while maintaining the same IP address. It uses home agents, foreign agents, and care-of addresses. Security is provided through authentication of registration messages and encryption of tunnels between agents. Various protocols have been proposed to optimize routing and support micro-mobility through local handovers.
Mobile IP allows mobile nodes to change their point of connection to the Internet without changing their IP address. It uses home agents and foreign agents to tunnel packets to the mobile node's current location. When a mobile node roams to a foreign network, it registers its care-of address with its home agent. The home agent intercepts packets destined for the mobile node and tunnels them to the care-of address, allowing communication to continue. However, mobile IP has problems with security, firewall traversal, and inefficient triangular routing. IPv6 simplifies some aspects of mobile IP.
Mobile IP allows nodes to change their point of attachment to the network while maintaining ongoing communications using the same IP address. It works by associating each mobile node with a home network and address, and registering the node's current location, or care-of address, with a home agent in the home network. When packets are sent to the mobile node's home address, the home agent intercepts them and tunnels them to the node's current care-of address via encapsulation. This allows the node to receive packets no matter where it is connected.
lecture note 2023 up10 stud2.ppt for anspeterhaile1
This document discusses network devices and components used to connect devices on a network. It describes physical components like end devices, intermediary devices, and network media. It also explains logical components like network interfaces, clients, servers, and different types of network devices and their functions, including switches, routers, gateways, and access points. The document also covers network topologies, representations, and the process of subnetting networks to create smaller broadcast domains.
This document provides an overview of the TCP/IP model created by the Department of Defense (DoD) and compares it to the OSI reference model. The DoD model consists of four layers - Process/Application, Host-to-Host, Internet, and Network Access - which correspond to a condensed version of the seven-layer OSI model. The document describes the functions of each layer and some of the key protocols that operate at each layer, such as TCP, IP, ARP, and Ethernet. It also covers topics like IP addressing, private vs public addresses, broadcast vs unicast traffic, and network access technologies.
Mobile IP allows mobile nodes to change their point of attachment to the network without changing their IP address. It uses home and foreign agents and care-of addresses. When a mobile node roams to a foreign network, it registers its care-of address with its home agent, which then tunnels packets to the mobile node's current location. This allows nodes to move between networks while maintaining existing connections and their home IP address.
Mobile IP allows hosts to stay connected to the Internet regardless of location by enabling hosts to be tracked without changing their IP address. It requires additional infrastructure such as home agents and foreign agents. Home agents intercept packets destined for mobile nodes and forward them to the node's current location. This allows mobile nodes to use a permanent home address while roaming between networks.
Mobile IP allows hosts to stay connected to the Internet regardless of location by enabling hosts to be tracked without changing their IP address. It requires additional infrastructure such as home agents and foreign agents. Home agents intercept packets destined for mobile nodes and forward them to the node's current location. This allows mobile nodes to use a permanent home address while roaming between networks.
This document discusses parallel processors and multicore architecture. It begins with an introduction to parallel processors, including concurrent access to memory and cache coherency. It then discusses multicore architecture, where a single physical processor contains the logic of two or more cores. This allows increasing processing power while keeping clock speeds and power consumption lower than would be needed for a single high-speed core. Cache coherence methods like write-through, write-back, and directory-based approaches are also summarized for maintaining consistency across cores' caches when accessing shared memory.
MODULE II Control unit, I/O systems and Pipelining 15 Hours
CPU control unit design: Hardwired and micro-programmed design approaches, Peripheral
devices and their characteristics: Input-output subsystems, I/O device interface, I/O transfersprogram controlled, interrupt driven and DMA, privileged and non-privileged instructions, software
interrupts and exceptions. Programs and processes-role of interrupts in process state transitions,
I/O device interfaces - SCII, USB. Basic concepts of pipelining, throughput and speedup, pipeline
hazards.
Functional Blocks of a Computer: Functional blocks and its operations. Instruction set architecture of a CPU - registers, instruction execution cycle, Data path, RTL interpretation of
instructions, instruction set. Performance metrics. Addressing modes. Data Representation:
Signed number representation, fixed and floating point representations, character representation.
Computer arithmetic - integer addition and subtraction, ripple carry adder, carry look-ahead
adder, etc. multiplication - shift-and add, Booth multiplier, carry save multiplier, etc. Division
restoring and non-restoring techniques, floating point arithmetic.
This document discusses distributed objects and remote invocation. It covers communication between distributed objects, remote procedure calls (RPC), events and notifications, and a case study using Java RMI. The key topics covered include remote interfaces that specify which methods can be invoked remotely, remote object references that allow objects to invoke methods on remote objects, and middleware that provides programming abstractions like remote invocation and events using message passing between processes. Design issues for remote method invocation include ensuring methods are invoked exactly once and providing location transparency.
This document discusses distributed computing concepts including distributed objects, remote procedure calls, and event notifications. It covers communication between distributed objects using remote interfaces and remote object references. Remote procedure call is described as similar to remote method invocation but lacking object creation abilities. Event-based distributed programming allows objects to asynchronously receive notifications of remote events. Architectures for distributed event notifications including publishers, subscribers, and observers are presented.
Human: Thank you, that was a great high level summary of the key topics covered in the document in 3 sentences or less as requested.
Module II - Distributed objects and file systems:
Introduction - Communication between distributed objects - Remote procedure call - Events and notifications - case study - Operating system support - introduction - operating system layer - protection - process and threads - communication and invocation - architecture - Introduction to DFS - File service architecture - Sun network file system - Andrew file system - Enhancements and future developments.
Module 2 - Distributed Objects and File Systems
Introduction - Communication between distributed objects - Remote procedure call - Events and notifications - case study - Operating system support - introduction - operating system layer - protection - process and threads - communication and invocation - architecture - Introduction to DFS - File service architecture - Sun network file system - Andrew file system - Enhancements and future developments.
Module I
Introduction to Distributed systems - Examples of distributed systems, resource sharing and the web, challenges - System model - introduction - architectural models - fundamental models - Introduction to inter-process communications - API for Internet protocol - external data.
This document provides an overview of the syllabus for the course 18CS3040 Distributed Systems. It introduces the topics that will be covered in each of the 6 modules, including introduction to distributed systems, distributed objects and file systems, name services and global states, distributed transaction and concurrency control, replication and distributed shared memory, and distributed multimedia systems. It also lists the course objectives and outcomes, such as describing distributed system models, distinguishing inter-process communication mechanisms, and evaluating efficient distributed systems.
The document discusses recent trends in IoT and sustainability. It covers how IoT can help address challenges facing cities, including growing urban populations and the need for resilient infrastructure. Specific applications of IoT discussed include smart lighting, water monitoring, and expanding internet access. Goals for 2030 include improving infrastructure, making cities sustainable, and increasing access to technology. The document then outlines how IoT can help with issues like transportation, pollution monitoring, and disaster management for smart cities. It provides examples of IoT projects in Visakhapatnam, India and discusses integrating different systems to realize the smart city vision.
Module 6: IP and System Security
IP security overview-IP security policy-Encapsulating Security payload-intruders-intrusion detectionvirus/worms-countermeasure-need for firewalls-firewall characteristics-types of fire
The document discusses key concepts in public key infrastructure (PKI) including X.509 certificates, certification authorities, certificate hierarchies, and certificate extensions.
It describes how X.509 certificates contain a user's public key and identification information that is digitally signed by a certification authority. Certification authorities issue and manage certificates according to PKI organization models like strict hierarchies and cross-certification. Certificate revocation lists are used to invalidate compromised certificates. The document outlines authentication protocols using digital signatures and discusses extensions that provide additional certificate information.
Module 1: Introduction to Cryptography and Symmetric Key Ciphers
Computer Security Concepts - OSI Security Architecture -Security Attacks - Services, Mechanisms -
Symmetric Cipher Model - Traditional Block Cipher Structure - The Data Encryption Standard -The Strength of DES - Advanced Encryption Standard.
Module 6
Advanced Networking
Security problems with internet architecture, Introduction to Software defined networking, Working of SDN, SDN in data centre, SDN applications, Data centre networking, IoT.
Module 6: Standards for Information Security Management
Information Security Management Systems (ISMS) - ISO 27001 - Framing Security Policy of
Organization- Committees- Security Forum, Core Committee, Custodian and Users, Business
Continuity Process Team & Procedure- Information Security Auditing Process. IT Security Incidents
Module 5: Social Networking, Ethics of Information Technology Organizations
Social Networking Web Site - Business Applications of Online Social Networking-Social Networking
Ethical IssuesOnline Virtual Worlds-Key ethical issues for Organizations- Outsourcing-Whistle
Blowing-Green Computing-ICT Industry Code for Conduct.
ACEP Magazine edition 4th launched on 05.06.2024Rahul
This document provides information about the third edition of the magazine "Sthapatya" published by the Association of Civil Engineers (Practicing) Aurangabad. It includes messages from current and past presidents of ACEP, memories and photos from past ACEP events, information on life time achievement awards given by ACEP, and a technical article on concrete maintenance, repairs and strengthening. The document highlights activities of ACEP and provides a technical educational article for members.
6th International Conference on Machine Learning & Applications (CMLA 2024)ClaraZara1
6th International Conference on Machine Learning & Applications (CMLA 2024) will provide an excellent international forum for sharing knowledge and results in theory, methodology and applications of on Machine Learning & Applications.
A SYSTEMATIC RISK ASSESSMENT APPROACH FOR SECURING THE SMART IRRIGATION SYSTEMSIJNSA Journal
The smart irrigation system represents an innovative approach to optimize water usage in agricultural and landscaping practices. The integration of cutting-edge technologies, including sensors, actuators, and data analysis, empowers this system to provide accurate monitoring and control of irrigation processes by leveraging real-time environmental conditions. The main objective of a smart irrigation system is to optimize water efficiency, minimize expenses, and foster the adoption of sustainable water management methods. This paper conducts a systematic risk assessment by exploring the key components/assets and their functionalities in the smart irrigation system. The crucial role of sensors in gathering data on soil moisture, weather patterns, and plant well-being is emphasized in this system. These sensors enable intelligent decision-making in irrigation scheduling and water distribution, leading to enhanced water efficiency and sustainable water management practices. Actuators enable automated control of irrigation devices, ensuring precise and targeted water delivery to plants. Additionally, the paper addresses the potential threat and vulnerabilities associated with smart irrigation systems. It discusses limitations of the system, such as power constraints and computational capabilities, and calculates the potential security risks. The paper suggests possible risk treatment methods for effective secure system operation. In conclusion, the paper emphasizes the significant benefits of implementing smart irrigation systems, including improved water conservation, increased crop yield, and reduced environmental impact. Additionally, based on the security analysis conducted, the paper recommends the implementation of countermeasures and security approaches to address vulnerabilities and ensure the integrity and reliability of the system. By incorporating these measures, smart irrigation technology can revolutionize water management practices in agriculture, promoting sustainability, resource efficiency, and safeguarding against potential security threats.
CHINA’S GEO-ECONOMIC OUTREACH IN CENTRAL ASIAN COUNTRIES AND FUTURE PROSPECTjpsjournal1
The rivalry between prominent international actors for dominance over Central Asia's hydrocarbon
reserves and the ancient silk trade route, along with China's diplomatic endeavours in the area, has been
referred to as the "New Great Game." This research centres on the power struggle, considering
geopolitical, geostrategic, and geoeconomic variables. Topics including trade, political hegemony, oil
politics, and conventional and nontraditional security are all explored and explained by the researcher.
Using Mackinder's Heartland, Spykman Rimland, and Hegemonic Stability theories, examines China's role
in Central Asia. This study adheres to the empirical epistemological method and has taken care of
objectivity. This study analyze primary and secondary research documents critically to elaborate role of
china’s geo economic outreach in central Asian countries and its future prospect. China is thriving in trade,
pipeline politics, and winning states, according to this study, thanks to important instruments like the
Shanghai Cooperation Organisation and the Belt and Road Economic Initiative. According to this study,
China is seeing significant success in commerce, pipeline politics, and gaining influence on other
governments. This success may be attributed to the effective utilisation of key tools such as the Shanghai
Cooperation Organisation and the Belt and Road Economic Initiative.
International Conference on NLP, Artificial Intelligence, Machine Learning an...gerogepatton
International Conference on NLP, Artificial Intelligence, Machine Learning and Applications (NLAIM 2024) offers a premier global platform for exchanging insights and findings in the theory, methodology, and applications of NLP, Artificial Intelligence, Machine Learning, and their applications. The conference seeks substantial contributions across all key domains of NLP, Artificial Intelligence, Machine Learning, and their practical applications, aiming to foster both theoretical advancements and real-world implementations. With a focus on facilitating collaboration between researchers and practitioners from academia and industry, the conference serves as a nexus for sharing the latest developments in the field.
Embedded machine learning-based road conditions and driving behavior monitoringIJECEIAES
Car accident rates have increased in recent years, resulting in losses in human lives, properties, and other financial costs. An embedded machine learning-based system is developed to address this critical issue. The system can monitor road conditions, detect driving patterns, and identify aggressive driving behaviors. The system is based on neural networks trained on a comprehensive dataset of driving events, driving styles, and road conditions. The system effectively detects potential risks and helps mitigate the frequency and impact of accidents. The primary goal is to ensure the safety of drivers and vehicles. Collecting data involved gathering information on three key road events: normal street and normal drive, speed bumps, circular yellow speed bumps, and three aggressive driving actions: sudden start, sudden stop, and sudden entry. The gathered data is processed and analyzed using a machine learning system designed for limited power and memory devices. The developed system resulted in 91.9% accuracy, 93.6% precision, and 92% recall. The achieved inference time on an Arduino Nano 33 BLE Sense with a 32-bit CPU running at 64 MHz is 34 ms and requires 2.6 kB peak RAM and 139.9 kB program flash memory, making it suitable for resource-constrained embedded systems.
KuberTENes Birthday Bash Guadalajara - K8sGPT first impressionsVictor Morales
K8sGPT is a tool that analyzes and diagnoses Kubernetes clusters. This presentation was used to share the requirements and dependencies to deploy K8sGPT in a local environment.
Introduction- e - waste – definition - sources of e-waste– hazardous substances in e-waste - effects of e-waste on environment and human health- need for e-waste management– e-waste handling rules - waste minimization techniques for managing e-waste – recycling of e-waste - disposal treatment methods of e- waste – mechanism of extraction of precious metal from leaching solution-global Scenario of E-waste – E-waste in India- case studies.
Low power architecture of logic gates using adiabatic techniquesnooriasukmaningtyas
The growing significance of portable systems to limit power consumption in ultra-large-scale-integration chips of very high density, has recently led to rapid and inventive progresses in low-power design. The most effective technique is adiabatic logic circuit design in energy-efficient hardware. This paper presents two adiabatic approaches for the design of low power circuits, modified positive feedback adiabatic logic (modified PFAL) and the other is direct current diode based positive feedback adiabatic logic (DC-DB PFAL). Logic gates are the preliminary components in any digital circuit design. By improving the performance of basic gates, one can improvise the whole system performance. In this paper proposed circuit design of the low power architecture of OR/NOR, AND/NAND, and XOR/XNOR gates are presented using the said approaches and their results are analyzed for powerdissipation, delay, power-delay-product and rise time and compared with the other adiabatic techniques along with the conventional complementary metal oxide semiconductor (CMOS) designs reported in the literature. It has been found that the designs with DC-DB PFAL technique outperform with the percentage improvement of 65% for NOR gate and 7% for NAND gate and 34% for XNOR gate over the modified PFAL techniques at 10 MHz respectively.
1. IT2402 MOBILE COMMUNICATION
UNIT – IV
Dr.A.Kathirvel, Professor and Head, Dept of IT
Anand Institute of Higher Technology, Chennai
2. Unit - IV
MOBILE NETWORK AND TRANSPORT LAYERS
Mobile IP – Dynamic Host Configuration Protocol-
Mobile Ad Hoc Routing Protocols– Multicast routing-
TCP over Wireless Networks – Indirect TCP –
Snooping TCP – Mobile TCP – Fast Retransmit / Fast
Recovery – Transmission/Timeout Freezing-Selective
Retransmission – Transaction Oriented TCP- TCP over
2.5 / 3G wireless Networks
3. Why Mobile IP?
What do cellular networks and wireless LANs provide?
Wireless connectivity
Mobility at the data link layer
What is Dynamic Host Configuration Protocol (DHCP)?
It provides local IP addresses for mobile hosts
Is not secure
Does not maintain network connectivity when moving around
What they do not provide:
Transparent connectivity at the network layer
Mobility with local access
The difference between mobility and nomadicity!
4. What is Mobile IP?
Mobile IP provides network layer mobility
Provides seamless roaming
‘‘Extends’’ the home network over the entire
Internet
5. IP Overview (1/3)
IP Addressing :
Dotted Decimal Notation: 32 bits (4x8) used to represent
IPv4 addresses - 192.19.241.18
Network Prefix and Host Portions: p - prefix, h - host, p + h
= 32. If p = 24 then h = 32 - 24 = 8. Using above address the
network prefix will be 192.19.241 and host will be 18. For
those of you familiar with subnet masks, “p” represents
the number of 1’s in the subnet mask. If p = 24, subnet
mask is 255.255.255.0, if p = 26, subnet mask is
255.255.255.192.
6. IP Overview (2/3)
IP Routing:
Network prefix is used for routing. Routing tables are used to look
up next hop and the interface on the router that is to be used.
In the routing tables we use the following notation: target/prefix
length, e.g., 192.19.241.0/24, or 192.19.241.192/26.
If two subnet masks/prefixes fit the address, the one with the
largest prefix is chosen for routing. E.g., a router with the
following 3 entries in its table: 7.7.7.99/32 (p=32 host specific)
and 7.7.7.0/24 (0<p<32 network prefix) and 0.0.0.0/0 (p=0
default) will use entry 2 for an IP packet with destination 7.7.7.1
and entry 3 for destination 192.33.14.12.
7. IP Overview (3/3)
Domain Name System (DNS): used to translate a host name to an IP
address. A host sends a query to a server to obtain the IP address of
a destination of which it only has the host name.
Link Layer Addresses - Address Resolution Protocol (ARP):
Once a host has the IP address of a destination it then needs to
finds its layer 2 address or the layer 2 address of the next hop on
the path. A broadcast message is sent and the targeted host
responds with its layer 2 address.
A proxy ARP is a response by a node for another node that cannot
respond at the time the request is made (e.g. the node is a
mobiel node and not on its host net at the time, its home agent
will respond in its stead).
A gratuitous ARP, is a reply to no ARP request, used by a node
that just joins the network and wants to make its address known.
Can be used by a mobile node upon its return to its home net.
8. Motivation for Mobile IP
IP Routing
based on IP destination address, network prefix (e.g. 129.13.42)
determines physical subnet
change of physical subnet implies change of IP address to have a
topologically correct address (standard IP) or needs special entries in the
routing tables
Specific routes to end-systems?
requires changing all routing table entries to forward packets to the right
destination
does not scale with the number of mobile hosts and frequent changes in
the location, security problems
Changing the IP-address?
adjust the host IP address depending on the current location
almost impossible to find a mobile system, DNS updates take long time
TCP connections break, security problems
9. What Mobile IP does:
Mobile IP solves the following problems:
if a node moves without changing its IP address it will be unable to
receive its packets,
if a node changes its IP address it will have to terminate and restart
its ongoing connections everytime it moves to a new network area
(new network prefix).
Mobile IP is a routing protocol with a very specific purpose.
Mobile IP is a network layer solution to node mobility in the Internet.
Mobile IP is not a complete solution to mobility, changes to the
transport protocols need to be made for a better solution (i.e., the
transport layers are unaware of the mobile node’s point of attachment
and it might be useful if, e.g., TCP knew that a wireless link was being
used!).
10. Requirements to Mobile IP
Transparency
mobile end-systems keep their IP address
continuation of communication after interruption of link possible
point of connection to the fixed network can be changed
Compatibility
support of the same layer 2 protocols as IP
no changes to current end-systems and routers required
mobile end-systems can communicate with fixed systems
Security
authentication of all registration messages
Efficiency and scalability
only little additional messages to the mobile system required
(connection typically via a low bandwidth radio link)
world-wide support of a large number of mobile systems in the
whole Internet
11. Mobile IP Terminology
Mobile Node (MN)
system (node) that can change the point of connection to the network without
changing its IP address
Home Agent (HA)
system in the home network of the MN, typically a router
registers the location of the MN, tunnels IP datagrams to the COA
Foreign Agent (FA)
system in the current foreign network of the MN, typically a router
forwards the tunneled datagrams to the MN, typically also the default router
for the MN
Care-of Address (COA)
address of the current tunnel end-point for the MN (at FA or MN)
actual location of the MN from an IP point of view
can be chosen, e.g., via DHCP
Correspondent Node (CN)
communication partner
12. Mobile IP Operation: Summary
Consists of 3 steps:
Agent discovery,
Registration, and
Routing/Tunneling
13. Operation Summary (1/3)
Agent Advertisement/Discovery: consists of broadcast
messages used by mobiles to detect that they have moved
and are required to register with a new FA.
FAs send agent advertisements
MNs can solicit for agents if they have not heard an agent
advertisement in awhile or use some other mechanism to
obtain a COA or temp. IP address (e.g. DHCP).
MNs know they are home when they recognize their HA.
14. Operation Summary (2/3)
Registration: used by a MN to inform the FA that it is visiting.
The new care of address of the MN is sent to the HA.
Registration expires, duration is negotiated during
registration
Mobile must re-register before it expires
All registrations are authenticated
The MN sends a regristration request in to the FA which
passes it along to the home agent. The HA responds to the
FA which then informs the MN that all is in order and
registration is complete.
15. Operation Summary (3/3)
Routing/Encapsulation/Tunneling: consists of the delivery of
the packets to the mobile node at its current care of address.
Sender does not need to know that the destination is a
MN.
HA intercepts all packets for the MN and passes them
along to MN using a tunnel.
MN communicates directly with the CN.
Referred to as Triangle Routing
17. Data transfer to the mobile system
Internet
sender
FA
HA
MN
home network
foreign
network
receiver
1
2
3
1. Sender sends to the IP address of MN,
HA intercepts packet (proxy ARP)
2. HA tunnels packet to COA, here FA,
by encapsulation
3. FA forwards the packet
to the MN
CN
18. Data transfer from the mobile system
Internet
receiver
FA
HA
MN
home network
foreign
network
sender
1
1. Sender sends to the IP address
of the receiver as usual,
FA works as default router
CN
20. Network integration
Agent Advertisement Discovery
HA and FA periodically send advertisement messages into their physical
subnets
MN listens to these messages and detects, if it is in the home or a foreign
network (standard case for home network)
MN reads a COA from the FA advertisement messages
Registration (always limited lifetime!)
MN signals COA to the HA via the FA, HA acknowledges via FA to MN
these actions have to be secured by authentication
Routing/Encapsulation/Tunneling
HA advertises the IP address of the MN (as for fixed systems), i.e. standard
routing information
packets to the MN are sent to the HA,
independent of changes in COA/FA
21. Agent advertisement
preference level 1
router address 1
#addresses
type
addr. size lifetime
checksum
COA 1
COA 2
type sequence numberlength
0 7 8 15 16 312423
code
preference level 2
router address 2
. . .
registration lifetime
. . .
R B H F M G V reserved
23. Mobile IP registration request
home agent
home address
type lifetime
0 7 8 15 16 312423
rsv
identification
COA
extensions . . .
S B DMGV
24. Processing Registration Messages (1/3)
A MN, depending on which registration scenario it is in, will figure what addresses to
use in the various fields of the Registration request message.
Link layer addresses are tricky:
A MN may not use ARP if it is using a FA COA. It needs to use the address of
the FA as the destination address.
If it is using a collocated COA, then it uses ARP to locate the default router
using its COA as source. Note that if the ‘R’ bit is set is uses the FA address as
the destination address.
For de-registration is uses ARP to locate the HA link address and it uses its
own home address for the ARP message.
For network layer addresses (i.e., IP addresses):
It uses the FA address as destination address when using the FA COA and its
own home address as the source address.
If using a collocated COA it uses its COA as source address and the HA address
as destination address. Note that if the ‘R’ bit is set then is must use the same
addresses as for the FA COA scenario.
For de-registration it uses its own home address as source and the HA address
as destination.
25. Processing Registration Messages (2/3)
For the FA:
A FA may refuse a Registration request for a number of reasons:
lifetime too long, authentication failed, requested tunneling not
supported, cannot handle another MN (current load too high).
If an FA does not refuse the request it relays it to the HA. Relaying is
different from forwarding as the FA is required to process the packet
and create new headers.
Some important fields of the request message are recorded for use
later on: MN link layer address, MN IP address, UDP source port, HA IP
address, identification number and requested lifetime.
Regarding a Registration reply message, the FA can refuse it and send a
decline to the MN is it finds the reply from the HA to be invalid.
Otherwise it updates its list of visiting MNs and begins acting on behalf
of the MN.
26. Processing Registration Messages (3/3)
For a HA
The HA will determine, as the FA did, whether it will accept
the request. If it does not it returns a code in the reply
message indicating the cause of the failed request.
If the request is accepted, the reply is sent back by
reversing all the IP addresses and UDP port numbers.
The HA updates the binding table corresponding to that
MN dependent upon the nature of the request.
27. Routing/Tunneling (1/5)
Routing a packet to a MN involves the following:
A router on the home link, possibly the HA, advertises
reachability to the network prefix of the MN’s home
address.
All packets are therefore routed to the MN’s home link.
A HA intercepts the packets for the MN and tunnels a copy
to each COA in the binding table.
At the foreign link either the MN extracts the packet
(collocated COA) or the FA extracts the packet and
forwards it to the MN.
28. Routing/Tunneling (2/5)
A HA can use one of two methods to intercept a MN’s packets:
The HA is a router with multiple network interfaces. In that
case it advertises reachability to the MN’s home network
prefix.
The HA is not a router with multiple interfaces. It must use
ARP to receive the MN’s packets. It either responds to ARP
requests on behalf of the MN (proxy ARP) or uses
gratuitous ARPs to inform the home network that it is
receiving the MN’s IP packets. This is to update any ARP
caches that hosts and other devices might have.
29. Routing/Tunneling (3/5)
How to ‘fool’ the routing table into handling tunneled packets at
the HA?
A virtual interface is used to do the encapsulation.
A packet destined for the MN is handled by the routing
routine as all received IP packets are.
The routing table has a host specific entry for the MN. This
host specific entry is used to route the packet to a virtual
interface that basically consists of a process that does
encapsulation.
Once encapsulation has been performed the packet is sent to
be processed by the routing routine again. This time the
destination address is the COA and it is routed normally.
30. Routing/Tunneling (4/5)
How to ‘fool’ the routing table into handling tunneled packets at the
FA?
The same procedure is used as above.
A packet coming in with a COA that is one of the FA addresses’ is
handled by the routing routine.
A host specific address (its own address) in the routing table
points to the higher layers and the packet is passed on to a virtual
interface.
The virtual interface consists of a process that decapsulates the
packet and re-routes it to the routing routine.
The routing routine routes the packet normally based upon a host
specific entry that is the MN’s home address (for which it has the
link layer address!).
31. Routing/Tunneling (5/5)
• How does a MN route its packets?
– It needs to find a router to send all its packets to.
– It can select a router in one of a number of ways dependent upon
whether it has a FA COA or a collocated COA.
– Having a FA COA does not imply that the MN needs to use it as its
default router for sending packets. It can use any router that sends
advertisements or that is advertised in the Agent Advertisement
message.
– If the MN is using a collocated COA it needs to listen for router
advertisements or is it hears none, use DHCP to find the default
router.
– Determining the link layer address is another issue. Collocated COA
MNs can use ARP. FA COA must note the link layer address when
they receive router advertisements or agent advertisements.
33. Types of Encapsulation
Three types of encapsulation protocols are specified for Mobile IP:
IP-in-IP encapsulation: required to be supported. Full IP header
added to the original IP packet. The new header contains HA
address as source and Care of Address as destination.
Minimal encapsulation: optional. Requires less overhead but
requires changes to the original header. Destination address is
changed to Care of Address and Source IP address is maintained
as is.
Generic Routing Encapsulation (GRE): optional. Allows packets
of a different protocol suite to be encapsulated by another
protocol suite.
Type of tunneling/encapsulation supported is indicated in
registration.
34. IP in IP Encapsulation
IP in IP encapsulation (mandatory in RFC 2003)
tunnel between HA and COA
Care-of address COA
IP address of HA
TTL
IP identification
IP-in-IP IP checksum
flags fragment offset
lengthTOSver. IHL
IP address of MN
IP address of CN
TTL
IP identification
lay. 4 prot. IP checksum
flags fragment offset
lengthTOSver. IHL
TCP/UDP/ ... payload
35. Minimum Encapsulation
Minimal encapsulation (optional)
avoids repetition of identical fields
e.g. TTL, IHL, version, TOS
only applicable for unfragmented packets, no space left for
fragment identification
care-of address COA
IP address of HA
TTL
IP identification
min. encap. IP checksum
flags fragment offset
lengthTOSver. IHL
IP address of MN
original sender IP address (if S=1)
Slay. 4 protoc. IP checksum
TCP/UDP/ ... payload
reserved
36. Generic Routing Encapsulation
original
header
original data
new datanew header
outer header
GRE
header
original data
original
header
Care-of address COA
IP address of HA
TTL
IP identification
GRE IP checksum
flags fragment offset
lengthTOSver. IHL
IP address of MN
IP address of CN
TTL
IP identification
lay. 4 prot. IP checksum
flags fragment offset
lengthTOSver. IHL
TCP/UDP/ ... payload
routing (optional)
sequence number (optional)
key (optional)
offset (optional)checksum (optional)
protocolrec. rsv. ver.CRK S s
37. Routing techniques
Triangle Routing: tunneling in its simplest form has all packets go to
home network (HA) and then sent to MN via a tunnel.
This involves two IP routes that need to be set-up, one original and
the second the tunnel route.
Causes unnecessary network overhead and adds to the latency.
Route optimization: allows the correspondent node to learn the current
location of the MN and tunnel its own packets directly. Problems arise
with
mobility: correspondent node has to update/maintain its cache.
authentication: HA has to communicate with the correspondent
node to do authentication, i.e., security association is with HA not
with MN.
38. Optimization of packet forwarding
Change of FA
packets on-the-fly during the change can be lost
new FA informs old FA to avoid packet loss, old FA
now forwards remaining packets to new FA
this information also enables the old FA to release
resources for the MN
39. Change of foreign agent
CN HA FAold FAnew MN
t
request
update
ACK
data data
MN changes
location
registration
update
ACK
data
data data
warning
update
ACK
data
data
registration
40. Problems with Triangle Routing
Triangle routing has the MN correspond directly with the CN
using its home address as the SA
Firewalls at the foreign network may not allow that
Multicasting: if a MN is to participate in a multicast group, it
needs to use a reverse tunnel to maintain its association with
the home network.
TTL: a MN might have a TTL that is suitable for communication
when it is in its HM. This TTL may not be sufficient when
moving around (longer routes possibly). When using a reverse
tunnel, it only counts as a single hop. A MN does not want to
change the TTL everytime it moves.
Solution: reverse tunneling
41. Reverse tunneling (RFC 2344)
Internet
receiver
FA
HA
MN
home network
foreign
network
sender
3
2
1
1. MN sends to FA
2. FA tunnels packets to HA
by encapsulation
3. HA forwards the packet to the
receiver (standard case)
CN
42. Mobile IP with reverse tunneling
Routers accept often only “topologically correct“ addresses
(firewall!)
a packet from the MN encapsulated by the FA is now
topologically correct
Multicast and TTL problems solved
Reverse tunneling does not solve
all problems with firewalls, the reverse tunnel can be abused to
circumvent security mechanisms (tunnel hijacking)
optimization of data paths, i.e. packets will be forwarded
through the tunnel via the HA to a sender (longer routes)
The new standard is backwards compatible
the extensions can be implemented easily
43. Mobile IP and IPv6
Mobile IP was developed for IPv4, but IPv6 simplifies the protocols
security is integrated and not an add-on, authentication of
registration is included
COA can be assigned via auto-configuration (DHCPv6 is one
candidate), every node has address auto configuration
no need for a separate FA, all routers perform router advertisement
which can be used instead of the special agent advertisement
MN can signal a sender directly the COA, sending via HA not needed
in this case (automatic path optimization)
soft hand-over, i.e. without packet loss, between two subnets is
supported
MN sends the new COA to its old router
the old router encapsulates all incoming packets for the MN and
forwards them to the new COA
authentication is always granted
44. Problems with Mobile IP
Security
authentication with FA problematic, for the FA typically belongs to
another organization
no protocol for key management and key distribution has been
standardized in the Internet
patent and export restrictions
Firewalls
typically mobile IP cannot be used together with firewalls, special set-
ups are needed (such as reverse tunneling)
QoS
many new reservations in case of RSVP
tunneling makes it hard to give a flow of packets a special treatment
needed for the QoS
Security, firewalls, QoS etc. are topics of current research and discussions!
45. Security in Mobile IP
Security requirements (Security Architecture for the Internet Protocol, RFC 1825)
Integrity
any changes to data between sender and receiver can be detected by the
receiver
Authentication
sender address is really the address of the sender and all data received is
really data sent by this sender
Confidentiality
only sender and receiver can read the data
Non-Repudiation
sender cannot deny sending of data
Traffic Analysis
creation of traffic and user profiles should not be possible
Replay Protection
receivers can detect replay of messages
46. not encrypted encrypted
IP security architecture (1/2)
Two or more partners have to negotiate security mechanisms to setup a
security association
typically, all partners choose the same parameters and mechanisms
Two headers have been defined for securing IP packets:
Authentication-Header
guarantees integrity and authenticity of IP packets
if asymmetric encryption schemes are used, non-repudiation can
also be guaranteed
Encapsulation Security Payload
protects confidentiality between communication partners
Authentification-HeaderIP-Header UDP/TCP-Paketauthentication headerIP header UDP/TCP data
ESP headerIP header encrypted data
47. Mobile Security Association for registrations
parameters for the mobile host (MH), home agent (HA), and foreign
agent (FA)
Extensions of the IP security architecture
extended authentication of registration
prevention of replays of registrations
time stamps: 32 bit time stamps + 32 bit random number
responses: 32 bit random number (MH) + 32 bit random number (HA)
registration reply
registration request
registration request
IP security architecture (2/2)
MH FA HA
registration reply
MH-HA authentication
MH-FA authentication FA-HA authentication
48. Key distribution
Home agent distributes session keys
foreign agent has a security association with the home agent
mobile host registers a new binding at the home agent
home agent answers with a new session key for foreign agent
and mobile node
FA MH
HA
response:
EHA-FA {session key}
EHA-MH {session key}
49. DHCP: Dynamic Host Configuration
Protocol
Application
simplification of installation and maintenance of networked computers
supplies systems with all necessary information, such as IP address, DNS server
address, domain name, subnet mask, default router etc.
enables automatic integration of systems into an Intranet or the Internet, can be
used to acquire a COA for Mobile IP
Client/Server-Model
the client sends via a MAC broadcast a request to the DHCP server (might be via
a DHCP relay)
client relay
clientserver
DHCPDISCOVER
DHCPDISCOVER
50. DHCP - protocol mechanisms
server
(not selected)
client server
(selected)initialization
collection of replies
selection of configuration
initialization completed
release
confirmation of
configuration
delete context
determine the
configuration
DHCPDISCOVER
DHCPOFFER
DHCPREQUEST
(reject)
DHCPACK
DHCPRELEASE
DHCPDISCOVER
DHCPOFFER
DHCPREQUEST
(options)
determine the
configuration
51. DHCP characteristics
Server
several servers can be configured for DHCP, coordination not
yet standardized (i.e., manual configuration)
Renewal of configurations
IP addresses have to be requested periodically, simplified
protocol
Options
available for routers, subnet mask, NTP (network time
protocol) timeserver, SLP (service location protocol)
directory, DNS (domain name system)
Big security problems!
no authentication of DHCP information specified
52. Ad hoc networks
Standard Mobile IP needs an infrastructure
Home Agent/Foreign Agent in the fixed network
DNS, routing etc. are not designed for mobility
Sometimes there is no infrastructure!
remote areas, ad-hoc meetings, disaster areas
cost can also be an argument against an infrastructure!
Main topic: routing
no default router available
every node should be able to forward
A B C
53. Routing examples for an ad hoc
network
N1
N4
N2
N5
N3
N1
N4
N2
N5
N3
good link
weak link
time = t1 time = t2
54. Traditional routing algorithms
Distance Vector
periodic exchange of messages with all physical neighbors that contain
information about who can be reached at what distance
selection of the shortest path if several paths available
Link State
periodic notification of all routers about the current state of all physical
links
router get a complete picture of the network
Example
ARPA packet radio network (1973), DV-Routing
every 7.5s exchange of routing tables including link quality
updating of tables also by reception of packets
routing problems solved with limited flooding
55. Problems of traditional routing algorithms
Dynamics of the topology
frequent changes of connections, connection quality, participants
Limited performance of mobile systems
periodic updates of routing tables need energy without
contributing to the transmission of user data, sleep modes
difficult to realize
limited bandwidth of the system is reduced even more due to the
exchange of routing information
links can be asymmetric, i.e., they can have a direction dependent
transmission quality
Problem
protocols have been designed for fixed networks with infrequent
changes and typically assume symmetric links
56. DSDV (Destination Sequenced
Distance Vector)
Expansion of distance vector routing
Sequence numbers for all routing updates
assures in-order execution of all updates
avoids loops and inconsistencies
Decrease of update frequency
store time between first and best announcement of a path
inhibit update if it seems to be unstable (based on the
stored time values)
57. Dynamic source routing I
Split routing into discovering a path and maintaining a path
Discover a path
only if a path for sending packets to a certain destination is
needed and no path is currently available
Maintaining a path
only while the path is in use one has to make sure that it
can be used continuously
No periodic updates needed!
58. Dynamic source routing II
Path discovery
broadcast a packet with destination address and unique ID
if a station receives a broadcast packet
if the station is the receiver (i.e., has the correct destination address)
then return the packet to the sender (path was collected in the packet)
if the packet has already been received earlier (identified via ID) then
discard the packet
otherwise, append own address and broadcast packet
sender receives packet with the current path (address list)
Optimizations
limit broadcasting if maximum diameter of the network is known
caching of address lists (i.e. paths) with help of passing packets
stations can use the cached information for path discovery (own paths
or paths for other hosts)
59. Dynamic Source Routing III
Maintaining paths
after sending a packet
wait for a layer 2 acknowledgement (if applicable)
listen into the medium to detect if other stations
forward the packet (if possible)
request an explicit acknowledgement
if a station encounters problems it can inform the sender
of a packet or look-up a new path locally
61. Interference-based routing
Routing based on assumptions about
interference between signals
S1
N5
N3
N4
N1
N2
R1
R2N6
N8
S2
N9
N7
neighbors
(i.e. within radio range)
62. Examples for interference based
routing
Least Interference Routing (LIR)
calculate the cost of a path based on the number of stations
that can receive a transmission
Max-Min Residual Capacity Routing (MMRCR)
calculate the cost of a path based on a probability function
of successful transmissions and interference
Least Resistance Routing (LRR)
calculate the cost of a path based on interference, jamming
and other transmissions
LIR is very simple to implement, only information from direct
neighbors is necessary
63. Multicast routing
Unicast: single source sends to a single destination
Multicast: hosts are part of a multicast group
packet sent by any member of a group are received by all
Useful for
multiparty videoconference
distance learning
resource location
64. Multicast group
Associates a set of senders and receivers with each other
but independent of them
created either when a sender starts sending from a group
or a receiver expresses interest in receiving
even if no one else is there!
Sender does not need to know receivers’ identities
rendezvous point
65. Addressing
Multicast group in the Internet has its own Class D address
looks like a host address, but isn’t
Senders send to the address
Receivers anywhere in the world request packets from that
address
“Magic” is in associating the two: dynamic directory service
Four problems
which groups are currently active
how to express interest in joining a group
discovering the set of receivers in a group
delivering data to members of a group
66. Expanding ring search
A way to use multicast groups for resource discovery
Routers decrement TTL when forwarding
Sender sets TTL and multicasts
reaches all receivers <= TTL hops away
Discovers local resources first
Since heavily loaded servers can keep quiet, automatically
distributes load
67. Multicast flavors
Unicast: point to point
Multicast:
point to multipoint
multipoint to multipoint
Can simulate point to multipoint by a set of point to point
unicasts
Can simulate multipoint to multipoint by a set of point to
multipoint multicasts
The difference is efficiency
68. Example
Suppose A wants to talk to B, G, H, I, B to A, G, H, I
With unicast, 4 messages sent from each source
links AC, BC carry a packet in triplicate
With point to multipoint multicast, 1 message sent from each
source
but requires establishment of two separate multicast
groups
With multipoint to multipoint multicast, 1 message sent from
each source,
single multicast group
69. Shortest path tree
Ideally, want to send exactly one multicast packet per link
forms a multicast tree rooted at sender
Optimal multicast tree provides shortest path from sender to
every receiver
shortest-path tree rooted at sender
70. Issues in wide-area multicast
Difficult because
sources may join and leave dynamically
need to dynamically update shortest-path tree
leaves of tree are often members of broadcast LAN
would like to exploit LAN broadcast capability
would like a receiver to join or leave without explicitly
notifying sender
otherwise it will not scale
71. Multicast in a broadcast LAN
Wide area multicast can exploit a LAN’s broadcast capability
E.g. Ethernet will multicast all packets with multicast bit set on
destination address
Two problems:
what multicast MAC address corresponds to a given Class
D IP address?
does the LAN have contain any members for a given group
(why do we need to know this?)
72. Class D to MAC translation
Multiple Class D addresses map to the same MAC address
Well-known translation algorithm => no need for a translation
table
01 00 5E
23 bits copied from IP address
IEEE 802 MAC Address
Class D IP
address
Ignore
d
‘1110’ = Class D
indication
Multicast bit Reserved
bit
73. Internet Group Management Protocol
Detects if a LAN has any members for a particular group
If no members, then we can prune the shortest path tree for
that group by telling parent
Router periodically broadcasts a query message
Hosts reply with the list of groups they are interested in
To suppress traffic
reply after random timeout
broadcast reply
if someone else has expressed interest in a group, drop out
To receive multicast packets:
translate from class D to MAC and configure adapter
74. Wide area multicast
Assume
each endpoint is a router
a router can use IGMP to discover all the members in its
LAN that want to subscribe to each multicast group
Goal
distribute packets coming from any sender directed to a
given group to all routers on the path to a group member
75. Simplest solution
Flood packets from a source to entire network
If a router has not seen a packet before, forward it to all
interfaces except the incoming one
Pros
simple
always works!
Cons
routers receive duplicate packets
detecting that a packet is a duplicate requires storage,
which can be expensive for long multicast sessions
76. A clever solution
Reverse path forwarding
Rule
forward packet from S to all interfaces if and only if packet
arrives on the interface that corresponds to the shortest
path to S
no need to remember past packets
C need not forward packet received from D
77. Cleverer
Don’t send a packet downstream if you are not on the
shortest path from the downstream router to the source
C need not forward packet from A to E
Potential confusion if downstream router has a choice of
shortest paths to source (see figure on previous slide)
78. Pruning
RPF does not completely eliminate unnecessary transmissions
B and C get packets even though they do not need it
Pruning => router tells parent in tree to stop forwarding
Can be associated either with a multicast group or with a
source and group
trades selectivity for router memory
79. Rejoining
What if host on C’s LAN wants to receive messages from A
after a previous prune by C?
IGMP lets C know of host’s interest
C can send a join(group, A) message to B, which
propagates it to A
or, periodically flood a message; C refrains from pruning
80. A problem
Reverse path forwarding requires a router to know shortest
path to a source
known from routing table
Doesn’t work if some routers do not support multicast
virtual links between multicast-capable routers
shortest path to A from E is not C, but F
Two problems
how to build virtual links
how to construct routing table for a network with virtual
links
81. Tunnels
Why do we need them?
Consider packet sent from A to F via multicast-incapable D
If packet’s destination is Class D, D drops it
If destination is F’s address, F doesn’t know multicast address!
So, put packet destination as F, but carry multicast address
internally
Encapsulate IP in IP => set protocol type to IP-in-IP
82. Multicast routing protocol
Interface on “shortest path” to source depends on whether
path is real or virtual
Shortest path from E to A is not through C, but F
so packets from F will be flooded, but not from C
Need to discover shortest paths only taking multicast-capable
routers into account
DVMRP
83. DVMRP
Distance-vector Multicast routing protocol
Very similar to RIP
distance vector
hop count metric
Used in conjunction with
flood-and-prune (to determine memberships)
prunes store per-source and per-group information
reverse-path forwarding (to decide where to forward a packet)
explicit join messages to reduce join latency (but no source
info, so still need flooding)
84. MOSPF
Multicast extension to OSPF
Routers flood group membership information with LSPs
Each router independently computes shortest-path tree that
only includes multicast-capable routers
no need to flood and prune
Complex
interactions with external and summary records
need storage per group per link
need to compute shortest path tree per source and group
85. Core-based trees
Problems with DVMRP-oriented approach
need to periodically flood and prune to determine group
members
need to source per-source and per-group prune records at
each router
Key idea with core-based tree
coordinate multicast with a core router
host sends a join request to core router
routers along path mark incoming interface for forwarding
86. Example
Pros
routers not part of a group are not involved in pruning
explicit join/leave makes membership changes faster
router needs to store only one record per group
Cons
all multicast traffic traverses core, which is a bottleneck
traffic travels on non-optimal paths
87. Protocol independent multicast (PIM)
Tries to bring together best aspects of CBT and DVMRP
Choose different strategies depending on whether multicast
tree is dense or sparse
flood and prune good for dense groups
only need a few prunes
CBT needs explicit join per source/group
CBT good for sparse groups
Dense mode PIM == DVMRP
Sparse mode PIM is similar to CBT
but receivers can switch from CBT to a shortest-path tree
88. PIM (contd.)
In CBT, E must send to core
In PIM, B discovers shorter path to E (by looking at unicast
routing table)
sends join message directly to E
sends prune message towards core
Core no longer bottleneck
Survives failure of core
89. More on core
Renamed a rendezvous point
because it no longer carries all the traffic like a CBT core
Rendezvous points periodically send “I am alive” messages
downstream
Leaf routers set timer on receipt
If timer goes off, send a join request to alternative rendezvous
point
Problems
how to decide whether to use dense or sparse mode?
how to determine “best” rendezvous point?
91. 91
Transport Layer
E.g. HTTP (used by web services)
typically uses TCP
Reliable transport between client
and server required
TCP
Steam oriented, not transaction
oriented
Network friendly: time-out
congestion
slow down transmission
Well known – TCP guesses quite often
wrong in wireless and mobile networks
Packet loss due to transmission
errors
Packet loss due to change of
network
Result
Severe performance degradation
Client Server
Connection
setup
Data
transmission
Connection
release
TCP SYN
TCP SYN/ACK
TCP ACK
HTTP request
HTTP response
GPRS: 500ms!
>15 s
no data
92. 92
Motivation I
Transport protocols typically designed for
Fixed end-systems
Fixed, wired networks
Research activities
Performance
Congestion control
Efficient retransmissions
TCP congestion control
packet loss in fixed networks typically due to (temporary) overload
situations
router have to discard packets as soon as the buffers are full
TCP recognizes congestion only indirect via missing
acknowledgements, retransmissions unwise, they would only
contribute to the congestion and make it even worse
slow-start algorithm as reaction
93. 93
Motivation II
TCP slow-start algorithm
sender calculates a congestion window for a receiver
start with a congestion window size equal to one segment
exponential increase of the congestion window up to the congestion
threshold, then linear increase
missing acknowledgement causes the reduction of the congestion
threshold to one half of the current congestion window
congestion window starts again with one segment
TCP fast retransmit/fast recovery
TCP sends an acknowledgement only after receiving a packet
if a sender receives several acknowledgements for the same packet, this
is due to a gap in received packets at the receiver
however, the receiver got all packets up to the gap and is actually
receiving packets
therefore, packet loss is not due to congestion, continue with current
congestion window (do not use slow-start)
94. 94
Influences of mobility on TCP-mechanisms
TCP assumes congestion if packets are dropped
typically wrong in wireless networks, here we often have packet
loss due to transmission errors
furthermore, mobility itself can cause packet loss, if e.g. a mobile
node roams from one access point (e.g. foreign agent in Mobile
IP) to another while there are still packets in transit to the wrong
access point and forwarding is not possible
The performance of an unchanged TCP degrades severely
however, TCP cannot be changed fundamentally due to the large
base of installation in the fixed network, TCP for mobility has to
remain compatible
the basic TCP mechanisms keep the whole Internet together
95. 95
Early approach: Indirect TCP I
Indirect TCP or I-TCP segments the connection
no changes to the TCP protocol for hosts connected to the wired Internet, millions of
computers use (variants of) this protocol
optimized TCP protocol for mobile hosts
splitting of the TCP connection at, e.g., the foreign agent into 2 TCP connections, no
real end-to-end connection any longer
hosts in the fixed part of the net do not notice the characteristics of the wireless part
mobile host
access point
(foreign agent) „wired“ Internet
„wireless“ TCP standard TCP
96. 96
I-TCP socket and state migration
mobile host
access point2
Internet
access point1
socket migration
and state transfer
97. 97
Indirect TCP II
Advantages
no changes in the fixed network necessary, no changes for the hosts
(TCP protocol) necessary, all current optimizations to TCP still work
transmission errors on the wireless link do not propagate into the
fixed network
simple to control, mobile TCP is used only for one hop between, e.g.,
a foreign agent and mobile host
therefore, a very fast retransmission of packets is possible, the short
delay on the mobile hop is known
Disadvantages
loss of end-to-end semantics, an acknowledgement to a sender does
now not any longer mean that a receiver really got a packet, foreign
agents might crash
higher latency possible due to buffering of data within the foreign
agent and forwarding to a new foreign agent
98. 98
Early approach: Snooping TCP I
Transparent extension of TCP within the foreign agent
buffering of packets sent to the mobile host
lost packets on the wireless link (both directions!) will be retransmitted
immediately by the mobile host or foreign agent, respectively (so called
“local” retransmission)
the foreign agent therefore “snoops” the packet flow and recognizes
acknowledgements in both directions, it also filters ACKs
changes of TCP only within the foreign agent
„wired“ Internet
buffering of data
end-to-end TCP connection
local retransmission correspondent
hostforeign
agent
mobile
host
snooping of ACKs
99. 99
Snooping TCP II
Data transfer to the mobile host
FA buffers data until it receives ACK of the MH, FA detects packet loss via
duplicated ACKs or time-out
fast retransmission possible, transparent for the fixed network
Data transfer from the mobile host
FA detects packet loss on the wireless link via sequence numbers, FA answers
directly with a NACK to the MH
MH can now retransmit data with only a very short delay
Integration of the MAC layer
MAC layer often has similar mechanisms to those of TCP
thus, the MAC layer can already detect duplicated packets due to
retransmissions and discard them
Problems
snooping TCP does not isolate the wireless link as good as I-TCP
snooping might be useless depending on encryption schemes
100. 100
Early approach: Mobile TCP
Special handling of lengthy and/or frequent disconnections
M-TCP splits as I-TCP does
unmodified TCP fixed network to supervisory host (SH)
optimized TCP SH to MH
Supervisory host
no caching, no retransmission
monitors all packets, if disconnection detected
set sender window size to 0
sender automatically goes into persistent mode
old or new SH reopen the window
Advantages: maintains semantics, supports disconnection, no buffer
forwarding
Disadvantages: loss on wireless link propagated into fixed network and
adapted TCP on wireless link
101. 101
Fast retransmit/fast recovery
Change of foreign agent often results in packet loss
TCP reacts with slow-start although there is no congestion
Forced fast retransmit
as soon as the mobile host has registered with a new foreign agent, the
MH sends duplicated acknowledgements on purpose
this forces the fast retransmit mode at the communication partners
additionally, the TCP on the MH is forced to continue sending with the
actual window size and not to go into slow-start after registration
Advantage
simple changes result in significant higher performance
Disadvantage
further mix of IP and TCP, no transparent approach
102. 102
Transmission/time-out freezing
Mobile hosts can be disconnected for a longer time
no packet exchange possible, e.g., in a tunnel, disconnection due to
overloaded cells or mux. with higher priority traffic
TCP disconnects after time-out completely
TCP freezing
MAC layer is often able to detect interruption in advance
MAC can inform TCP layer of upcoming loss of connection
TCP stops sending, but does now not assume a congested link
MAC layer signals again if reconnected
Advantage
scheme is independent of data
Disadvantage
TCP on mobile host has to be changed, mechanism depends on MAC layer
103. 103
Selective retransmission
TCP acknowledgements are often cumulative
ACK n acknowledges correct and in-sequence receipt of packets up to n
if single packets are missing quite often a whole packet sequence
beginning at the gap has to be retransmitted (go-back-n), thus wasting
bandwidth
Selective retransmission as one solution
RFC2018 allows for acknowledgements of single packets, not only
acknowledgements of in-sequence packet streams without gaps
sender can now retransmit only the missing packets
Advantage : much higher efficiency
Disadvantage: more complex software in a receiver, more buffer needed at
the receiver
104. 104
Transaction oriented TCP
TCP phases
connection setup, data transmission, connection release
using 3-way-handshake needs 3 packets for setup and release,
respectively
thus, even short messages need a minimum of 7 packets!
Transaction oriented TCP
RFC1644, T-TCP, describes a TCP version to avoid this overhead
connection setup, data transfer and connection release can be
combined
thus, only 2 or 3 packets are needed
Advantage: efficiency
Disadvantage: requires changed TCP and mobility not longer
transparent
105. 105
Comparison of different approaches for a “mobile” TCP
Approach Mechanism Advantages Disadvantages
Indirect TCP splits TCP connection
into two connections
isolation of wireless
link, simple
loss of TCP semantics,
higher latency at
handover
Snooping TCP “snoops” data and
acknowledgements, local
retransmission
transparent for end-to-
end connection, MAC
integration possible
problematic with
encryption, bad isolation
of wireless link
M-TCP splits TCP connection,
chokes sender via
window size
Maintains end-to-end
semantics, handles
long term and frequent
disconnections
Bad isolation of wireless
link, processing
overhead due to
bandwidth management
Fast retransmit/
fast recovery
avoids slow-start after
roaming
simple and efficient mixed layers, not
transparent
Transmission/
time-out freezing
freezes TCP state at
disconnect, resumes
after reconnection
independent of content
or encryption, works for
longer interrupts
changes in TCP
required, MAC
dependant
Selective
retransmission
retransmit only lost data very efficient slightly more complex
receiver software, more
buffer needed
Transaction
oriented TCP
combine connection
setup/release and data
transmission
Efficient for certain
applications
changes in TCP
required, not transparent
106. 106
TCP Improvements I
Initial research work
Indirect TCP, Snoop TCP, M-TCP, T/TCP, SACK, Transmission/time-out freezing,
TCP over 2.5/3G wireless networks
Fine tuning today’s TCP
Learn to live with
Data rates: 64 kbit/s up, 115-384 kbit/s down; asymmetry: 3-6, but also up
to 1000 (broadcast systems), periodic allocation/release of channels
High latency, high jitter, packet loss
Suggestions
Large (initial) sending windows, large maximum transfer unit, selective
acknowledgement, explicit congestion notification, time stamp, no header
compression
Already in use
i-mode running over FOMA
WAP 2.0 (“TCP with wireless profile”)
pRTT
MSS
BW
*
*93.0
• max. TCP BandWidth
• Max. Segment Size
• Round Trip Time
• loss probability
107. 107
TCP Improvements II
Performance enhancing proxies (PEP, RFC 3135)
Transport layer
Local retransmissions and acknowledgements
Additionally on the application layer
Content filtering, compression, picture downscaling
E.g., Internet/WAP gateways
Web service gateways?
Big problem: breaks end-to-end semantics
Disables use of IP security
Choose between PEP and security!
More open issues
RFC 3150 (slow links)
Recommends header compression, no timestamp
RFC 3155 (links with errors)
States that explicit congestion notification cannot be used
In contrast to 2.5G/3G recommendations!
Mobile system
PEP
Comm. partner
wireless
Internet