ECE 750 – T2

Protocols, Software and Issues in

Mobile Systems

http: //www.uwaterloo.ca

About the Instructor

• Instructor: Pin-Han Ho
• Research interest
– Wireless multimedia networking
– Cognitive radios
– Optical communications and networking
• Book
• Software Testing and Quality Assurance: Theory and
Practice, John Wiley, August 2008.

1
 Mobile Computing Systems
• Mobile computing systems
= computing + mobile communication
• Wireless connectivity  functionality++
• Mobile computing faces several challenges
• Unpredictable bandwidth between mobile
handset (MH)  Base Station (BS)
• Changes in network topology
• Limited
Li it d power
• Scalability: centralized vs distributed
• Security and Privacy: open media in the air

Scope of ECE 750

• Communications
• Telecommunication systems
• Ad hoc networks
• Radio resource management
• Support for mobility, mobile IP, mobile TCP
• Broadcast
• Network architecture, protocols, applications,
and performance evaluation
– Functional architectures, protocol stacks, design
parameters, performance metrics

2
 Course material

• Lecture notes
• Textbook

Grading Scheme

• Final Exam [50%]

• Project [35%]
• In-class Presentation [10%]
• In-class take home exercise [5%]

3
 Project Topics
• Cellular networks • Mobility management
- resource allocation, - handover , rooming architecture
- scheduling, - Power control and management
- femtocell networking,
g • Multimedia transmissions
- spectrum sensing in - cross-layer design
cognitive radios, - content delivery and multicast
- interference management • Security in wireless
• Ad hoc networks networks
– routing - message authentication
– broadcasting & - conditional privacy
multicasting
– geocasting
– vehicular communication
networks
• Delay tolerant networks
- routing

Project Details
• In groups of two
• Submit a proposal
– Choose a problem / Importance of the work
– Studyy the proposed
p p solutions
– What you want to do
• Milestones: For tracking and quality control
– Proposal: June 7 (1 page)
– 3-minute presentation June 10
– Progress Report: July 5 (3-4 pages)
– Final Report: July 28 (~15 pages)
• Consulting hours: in the afternoons
– Short duration: Knock on my door
– Longer: Send me email

4
 Course Outline
• Evolution of Internet and standards (3 hours)
• Wireless telecommunication systems: how to reach the end-
users
– GSM (3 hours)
– WiMAX, LTE, Relay and femtocell (3 hours)
• Ad hoc networks and delay tolerant networks (DTN) (3 hours)
• Communication protocols adapted to mobile environment
– Mobile TCP, Mobile IPv4 (3 hours)
• Wireless security (3 hours)
• Supporting applications (WAP), network aware computing (3
hours)
• Cognitive radio network design and topics (3 hours)
• Low power protocols, applications, system software (3 hours)

Evolution of Internet and Standard

• Control and Management on the Internet

• Evolution of the Internet Technology
• Industry Standardization Process
• Routing Protocols

5
Control and Management for the
Internet
• Elementary y Control Elements for the Internet
- Addressing
- Neighbor/topology Discovery
- Path Selection (route computation)
- Protection/Restoration
- Signaling
Si li

Elementary Control Elements

• Addressing
- IP-centric,
IP centric IPv4 or IPv6
- Identifiable entities in the Internet: routers, links, a port of a
router, a group of entities subject to a single failure (or called
Shared Risk Link Group),…etc.
- Granularity vs. scalability
- in mobile communication, each user is assigned with a
single IP address (but not always true in the wired Internet)
- Mobile IP: an IETF standard that allows a mobile handset
(MH) to roam from one network to another without changing
its home IP address.

6
Elementary Control Elements
• Neighbor Discovery
- Distributed control is desirable
- Discover the local status of links and ports of a node
- IETF defined Link Management Protocol (LMP) for
the Internet
- A prerequisite for network-wide link-state
dissemination and topology discovery
- In multi-hop wireless communications, hello
messages are exchanged between two neighbor nodes
to maintain the connectivity

Elementary Control Elements

• Topology Discovery
- Topology
p gy and resource state of the whole network can be
determined by disseminating link-state update messages
- Reactive versus Proactive
- Proactive link state dissemination in the Internet:
- Bundling of links
- Periodic encoding and dissemination of link state update
messages: OSPF,
OSPF IS-IS
IS IS
- Reactive dissemination mostly used in wireless environments
- dynamic source routing (DSR) floods RouteRequest
messages when demand arrives, and the destination
responds with RouteReply

7
Elementary Control Elements
• Path Selection (Routing)
- Least-cost path search under constraints (or QoS routing)
- Delay, delay jitters, administrative requirements
- Through an optimization process to plan/schedule paths for
multiple connection requests
- Hop-by-hop (e.g., AODV) vs. explicit routing (e.g., DSR)
- Adaptive, semi-adaptive and non-adaptive

Elementary Control Elements

• Protection, Monitoring, and Restoration
- Protection: pre-planned multiple working paths for a single
session to improve robustness and QoS
- 1+N => > pre-planned
l d N+1 pathsth (either
( ith logical
l i l or
physical) between the nodes, and 1+N copies of data are
launched to improve QoS
- 1:N => pre-planned N backup paths between the nodes,
and a single copy of data is launched along the working path.
- Monitoring: real-time obtaining the network link status =>
mostlyl by
b link
li k management protocols l
- Restoration: after failure occurs
- dynamically searching for an alternate route after a link
fails (e.g., DSR and AODV)
- best to “locally” restore the connectivity

8
Elementary Control Elements
• Signaling
- Essential to support all the control and management
mechanisms in a wireless network, and should be subject to
very careful design
- Specific to the protocols in the network system

Packet-Switched Networks
• Packet-switching with 32-bit address in the header
• Connectionless mode communication
- Sequence of the packets received may not be in order
- Traffic bottleneck due to the use of routing table
• X.25 was standardized in 1976 for virtual circuit services
=> in-band signaling
• IP routers with software-based routing core
- IP packets have a high error rate => large overhead on the
error detection/correction in each intermediate node
- Multiplexing of virtual circuits takes place at layer 3
- Both layer 2 and layer 3 have error control mechanisms
- 64 KB/sec
• Use routing metrics and routing table in each node

9
Frame Relay
• Relay => forward
• For improving X.25
- Released efforts in intermediate nodes
- Communication media is getting more reliable => the
overheads by X.25 are unnecessary
- Multiplexing and switching of logic connections take place at
layer 2
- Around 2 MB/sec
• Bandwidth bottleneck:
- Variable length of frames => hardware cannot reach

Asynchronous Transfer Mode (ATM)

• Evolution of frame relay
• Design objective:
- High performance in switching data packets
- Better mechanisms in traffic engineering
- Class of service
• High performance => part of the layer 2 functionality
with hardware design due to fixed sized cells
• Around
ou d 10Mbps
0 bps to Gbps
• Can provision constant data rate using packet switching
technique

10
 Label Swapping
label ATM switch
Cell A 5 1 1 Cell B 2
2 2
Cell C 4 3 3 Cell A 4
4 4
Cell B 4 5 5 Cell C 2
Input Input Output Swapped
port label port label
VC 1 5 3 4
VC 3 4 1 2
VC 1 4 5 2

Forwarding Table

Label Binding and Distribution

Label has only local significance to a node
Label is assigned
g to a cell according
g to its
- Destination address
- Quality of service requirement
- Traffic engineering consideration
Traffic aggregation at edge routers => Forwarding
Equivalence Class (FEC)

11
Traffic Engineering

ATM Networks
Use a new protocol (PNNI) to handle control and
management
Problem 1:1 IP addressing
dd i is i ubiquitous
bi i A ’
=> ATM’s
PNNI can never replace the Internet Protocol
- IP packets are what to be delivered
Problem 2: Very time- and effort-consuming to
newly construct a carrier network (with ATM)
- Existing software artifacts of no use

12
Emergence of IP Over ATM (IPOA)
• Used to connect IP and ATM networks
• ISPs
ISP migrated
i d to IP
IP-over-ATM
ATM (IPOA) ffor greater
bandwidth, deterministic performance, and traffic
engineering
• IP routing/signaling was limited to edges of the
networks

IP-Over-ATM (IP/ATM) Model

Edge Core Core
standard IP
I
Ingress edge
d router
t routing protocol
IP control

IP forwarding ATM Forum ATM Forum

signaling/routing ATM switch signaling/routing ATM switch
ATM ATM control ATM control
Layer 2 Control
transport ATM label ATM label
C ll
Cells swapping C ll
Cells swapping

Packets Assign initial Packets

ATM label

13
Disadvantages of IP/ATM Networks
• Still bandwidth limitation - 10% cell tax
• Physical topology cannot be seen in the ATM layer
- Hardd to
t do
d traffic
t ffi engineering
i i
- Scalability issues (e.g., N-square problem due to virtual
circuits and the SAR overhead)
• Inability to operate over non-ATM infrastructures
• Complexity gained by operating two disparate networks
- Connectionless vs. connection-oriented
- Different addressing, protocols, resource reservation schemes

Multi-layer Switching
• Alternatives to IPOA
- Internet market is large
g enough
g to build equipment
specifically designed for Internet backbone applications
- need high performance without complex mapping in IPOA
- IP switching by Ipsilon/Nokia
- Tag switching by Cisco
- Aggregate Route-Based IP Switching (ARIS) by IBM
- Cell
ll Switching
i hi Router by b Toshiba
hib
• Keep control software in the IP routers and integrate with the
forwarding performance of label-swapping ATM-switch

14
Multi-layer Switch as a Fast IP
Router

IP router Multi-layer switch ATM switch

Control: Control: Control:
IP router IP router ATM Forum
software software software
Forwarding: Forwarding: Forwarding:
Longest-match ATM label ATM label
lookup Swapping Swapping

Multi-layer Switching
Ingress
multilayer
switch

Edge Core
Standard IP
routing protocol
IP control IP control
Proprietary IP-based
IP forwarding signaling and
label-distribution
protocols
Layer 2
transport label
Labeled swapping Labeled
Packets Assign initial
packets packets
label

Label binding & distribution

15
Multi-Protocol Label Switching (MPLS)
• Problems with Multi-layer switching
- Vendor-specific
Vendor specific and not interoperable
- Need a multi-vendor standard
• Early~mid 1998, standardized by IETF
• Latest step in the evolution of multilayer switching in
the Internet – originally Cisco’s Tag switching
• Ultimate goal: IP
IP-routed
routed MPLS (or IP/MPLS)
- Operational expense reduction
- Enrich of class of services
- Enhance performance

Multi-Protocol Label Switching (MPLS)

Edge LSR

Edge Core
LSR (Label Switched Router)

IP control IP control

IP forwarding Standard IP
routing protocol
MPLS label
swapping
Layer 2
transport Any
Any data link
data link Labeled Labeled
Packets packets packets
Assign initial
MPLS label

16
MPLS

IP Domain MPLS Domain IP Domain

A: Label Switching B: Label Switching C: Label Switching
IP router Routing (LSR) Routing (LSR) Routing (LSR) IP router

MPLS MPLS MPLS

IP Control Plane Control Plane Control Plane IP
Forwarding Forwarding Forwarding
Plane
l Plane
l Plane
l

IP/MPLS Packet Header

Class of Time-to
Time to
Label service (CoS) S -live (TTL)
20 bits 3 bits 1 bit 8 bits

Layer 2 MPLS Payload

IP header
header header (user data)

An IP packet
MPLS: a shim layer between layer 2 and IP

17
Summary on MPLS Protocols
• MPLS control plane: defined in RFC-2702 & conventional IP
protocol constructs
• TE
TE-extension
extension was developed
• Independent and interoperable modules, including:
- Topology/neighbor discovery : LMP
- Link-state dissemination : extended conventional IP link
state IGP’s, such as OSPF-te and ISIS-te
- Path selection : constraint-based routing
- Path management :
-- path setup
-- path maintenance
-- path revocation RSVP-te
-- failure/configuration notification

IP/MPLS control plane

LSP Constrain-based Shortest LSP

setup Path First (CSPF) Module Signaling p
setup
TE-database & component
(1) link-state database
Information Information
Dissemination (2) Dissemination
IS-IS/OSPF routing

Flows in Forwarding Component Flows out

(1) : Configure forwarding (2) : Configure forwarding
table based on the routing table corresponding to LSP
decision of CSPF Module setup requests of the other LSRs

18
Functions of the MPLS
• Enhance routing functionality
- Strong tool for traffic engineering
- Support explicit route setup over physical infrastructures
- ISPs can fully control their networks

Functions of the MPLS

• Deliver new services with ease
- Modify the control component
- ISPs provision LSPs to satisfy specific FEC requirements
=> traffic classification needed at ingress nodes for DiffServ
- An LSP has its FEC providing different performance and
bandwidth guarantee
- Support Virtual Private Networks (VPNs)

19
Virtual Private Networks (VPNs)
• Private wide area networks
• Design issues: data privacy, use of non
non-unique
unique and
private IP addresses
• More than firewalls, authentication and encryption,
MPLS solutions:
- Use locally significant number as labels in each intermediate
node
ode ass forwarding
ow d g
- Tunneling encapsulation

Virtual Private Networks (VPNs)

• Provision a set of LSPs for connectivity among
different sites
• Define prefixes for each VPN in edge LSRs
- ingress LSRs place traffic into LSPs also based on VPN
membership information

20
VPN Design Issues
• Security
• Address translation
• Performance: Throughput, Load balancing,
fragmentation
• Bandwidth Management: RSVP
• Availability: Good performance at all times
• Scalability: Number of locations/Users
• Interoperability: Among vendors, ISPs, customers (for
extranets)

VPN Design Issues

• Compression: Reduces bandwidth requirements
• Manageability: SNMP,
SNMP Browser based
based, Java based
based,
centralized/distributed
• Accounting, Auditing, and Alarming
• Protocol Support: IP, non-IP (IPX)
• Platform and O/S support: Windows, UNIX, MacOS,
HP/Sun/Intel
• Installation: Changes to desktop or backbone only
• Need key recovery

21