IPv6 RealTime Usage of IEEE 802'16: Problem Statement

1
16ng, 65th IETF Meeting Dallas, March 22, 2006

• IPv6 Real-Time Usage of IEEE 802.16 Problem
  Statement
• draft-neves-rt-usage-80216-problem-statement-00

Pedro Neves Susana Sargento Rui L. Aguiar IT
Aveiro
2
Motivation

• Next generation challenges
• Real-time services support
• Ubiquitous internet access
• Users access to the internet all the time and
  everywhere
• Demand for high bandwidth services and
  applications
• Always Best Connected (ABC) concept
• IEEE 802.16(e) is an attractive solution to fill
  this gap
• PMP technology, high throughputs, oriented for
  WMAN
• Built-in QoS functionalities through the usage of
  connections and service flows

3
MAC Overview

• Connection-oriented technology
• Explicit service flow reservation is mandatory
• Real-time environments usage can be compromised
• Convergence Sublayer (CS)
• Set of classifiers to identify and differentiate
  the packets
• Each classifier maps the incoming packet to a
  specific CID
• CID has a service flow associated with a set of
  QoS parameters
• 802.3/Ethernet, IPv4, IPv6
• 802.3/Ethernet adopted as CS
• More Flexible
• Independent of the upper layer protocol being
  used (IPv4 or IPv6)

4
Multicast

• No native multicast support
• Dedicated CID for broadcast data
• Butno dedicated CID is defined for multicast
• Establishment of multicast connections
• Create a CID with each SS that belongs to the
  multicast group
• The CID must be equal for all the SSs
• Any available transport CID can be used for this
  matter

5
IPv6 Neighbor Discovery

• Neighbor Discovery Process is multicast based
• Router Discovery process
• RS destination MAC address is 333300000002
  (all-routers multicast MAC address)
• RA destination MAC address is 333300000001
  (all-nodes multicast MAC address)
• Address Resolution process
• NS destination MAC address is 3333FFxxxxxx
  (solicited node multicast MAC address)

6
MN Network Access

• Dynamic and fast process
• 802.3/Ethernet CS is a constraint for this
  requirement
• A service flow must be allocated for the MN
  (connection oriented feature)
• The BS (entity responsible to establish the
  service flow) must be aware of the MN MAC address
• This is not an instantaneous process
• The MN MAC address must be conveyed to the BS and
  then the service allocation can be triggered

7
Dynamic Service Differentiation

• MN granularity
• All services for a specific MN are aggregated in
  a single service flow (CID)
• Single Service/Application granularity
• Each service has a specific service flow
  allocated in the air link
• 802.3/Ethernet CS is a major constraint for this
  requirement
• It is not possible to allocate two service flows
  with the same classification parameter (MN MAC
  address)
• Even if only one service is being used by the MN,
  signaling packets and data packets must be sent
  in different service flows

8
Fast Mobility

• Inter-BS and intra-BS mobility
• Mobility with other access technologies
• UMTS
• MNs may handoff between APs attached to different
  SSs (intra-BS)
• Service Flow reservations in old SS must be
  teardown to release the allocated resources
• New service flow must be allocated in the new SS
• Traffic disruption must be avoided during this
  process

9
Thank You !