Transcript MobileMAN kick-off

MobileMAN kick-off
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar
{Jose, Raimo.Kantola,Nicklas.Beijar}@hut.fi
Networking Laboratory
Helsinki University of Technology
P.O. Box 3000, FIN-02015, Finland
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 1
Outline
1.
2.
3.
4.
5.
6.
Assumptions
Design Requirements
Initial Architecture design
Ad Hoc framework modules
Service discovery extensions in AODV
Steps forward
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 2
Assumtions
• Initial assumptions to clarify before going forward
•
•
Several routing protocols for Ad Hoc networks
• Proactive
• Reactive
• Hybrid
• Which protocol to select?
Required Services for network and applications functioning
• DHCP servers, DNS servers(broadcast or unicast for IPv6 discovery),
Positioning systems, SIP registrars, Gateway Location (for
interoperability with fixed networks), etc.
– Service Discovery embedded with routing?-> Common mechanism
to be used by ANY upper layer to discover network and application
services.
– Horizontal approach?-> Simple and does not complicate the selected
routing protocol but it is left up to the application to implement the
appropriate Service discovery?Broadcast at application level versus
Service Discovery within routing?
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 3
Design requirements
1. Some nodes are highly mobile with small resources, some with more
resources are quite static
•
Nodes classification
•
Classification criteria
2. Support for several routing algorithms and several link technologies
•
Division of the problem into different modules
•
Standardized API allows replacing modules
3. Support for persistent data required when Ad Hoc network is part of
another infrastructure (3G, 4G)
4. What are the routing requirements for service discovery to support in
order to request additional service from other infrastructures
(Positioning Services for location information)
5. What are the routing requirements in order to identify the
requirements to the Physical Layer.
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 4
Design requirements
1. Some nodes are highly mobile with small resources, some quite
static with more resources
•
Nodes classification
•
Classification criteria
2. Support for several routing algorithms and several link technologies
•
Division of the problem into different modules
•
Standardized API allows replacing modules
3. Support for persistent data required when Ad Hoc network is part of
another infrastructure (3G, 4G)
4. What are the routing requirements for service discovery to support in
order to request additional service from other infrastructures
(Positioning Services for location information)
5. What are the routing requirements in order to identify the
requirements to the Physical Layer.
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 5
Initial architecture assumptions
•
•
•
•
•
A preliminary basic nodes classification could be:
•
Smart nodes
–
Nodes with more resources and less mobility, e.g. laptops, servers,
network access points. Only smart nodes are capable of
maintaining large data amounts nodes participate in replication
•
Dummy nodes
–
Nodes with less resources and higher mobility, e.g. phones, PDAs
Proactive routing between smart nodes.
Reactive routing between dummy nodes and between Dummy and smart
nodes.
Information accessible from different locations

Reduced load of route discovery
Flexible node classification in order to allow nodes to change roles (e.g.
smart node becomes a dummy node)
•
Attach – Detach procedure
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 6
Design requirements
1. Some nodes are highly mobile with small resources, some quite
static with more resources
•
Nodes classification
•
Classification criteria
2. Support for several routing algorithms and several link technologies
•
Division of the problem into different modules
•
Standardized API allows replacing modules
3. Support for persistent data required when Ad Hoc network is part of
another infrastructure (3G, 4G)
4. What are the routing requirements for service discovery to support in
order to request additional service from other infrastructures
(Positioning Services for location information)
5. What are the routing requirements in order to identify the
requirements to the Physical Layer.
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 7
Initial architecture design
•
•
•
In order to support Several routing schemes in a node and routing
independent of physical layer it is required a modular architecture with
differentiated modules.
Interoperability between modules through standardized API
•
Initiates the discovery procedure
•
Provides an Attach – Detach mechanism
•
Accommodates the rate of updates
Initial set of modules
•
Routing module
•
Replication and synchronization module
–
Requirements for replication
–
Independence of underlying technology
–
Different routing protocols above
•
Context Sensitive Roaming Layer
–
Support to and dependent of terminal applications
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 8
Design requirements
1. Some nodes are highly mobile with small resources, some quite
static with more resources
•
Nodes classification
•
Classification criteria
2. Support for several routing algorithms and several link technologies
•
Division of the problem into different modules
•
Standardized API allows replacing modules
3. Support for persistent data required when Ad Hoc network is part of
another infrastructure (3G, 4G)
4. What are the routing requirements for service discovery to support in
order to request additional service from other infrastructures
(Positioning Services for location information)
5. What are the routing requirements in order to identify the
requirements to the Physical Layer.
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 9
Routing module
Application and services
User
UserServices
Services Future
Directory (Messaging
Directory
Future
(
Messaging
Services
Services
Services
Services
Gaming)
Gaming)
Services and session
management
(SIP,HTTP)
Auto-Configuration
Module
Context-Sensitive
Roaming Layer
IP Layer
(IPv4/IPv6)
Routing
Module
Routing Module
Policy
Module
Routing
Routing Module
Algorithm
Information
Module
Routing
Routing
Information
API
Link Layer Protocol
Synchronization
Synchronization&
Replication
module (SCSP)
Module
Communication
Module
Physical Layer
Physical Layer
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 10
Initial architecture modules: Routing module
•
Terminal Applications
Context Roaming
Module
AdHoc_Framework
Main modules in the architecture design
• Context Roaming Module
– Provide the API to the applications to roam
depending on context information.
• Ad Hoc Framework
– Implement the different Ad Hoc routing
algorithms (proactive, reactive, or others)
– Interact with the Linux Kernel for
implementing Attach-detach procedures.
– Implement the necessary extensions to
perform service discovery.
Kernel
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Interface
Handler
Slide 11
Design requirements
1. Some nodes are highly mobile with small resources, some quite
static with more resources
•
Nodes classification
•
Classification criteria
2. Support for several routing algorithms and several link technologies
•
Division of the problem into different modules
•
Standardized API allows replacing modules
3. Support for persistent data required when Ad Hoc network is part of
another infrastructure (3G, 4G)
4. What are the routing requirements for service discovery to support in
order to request additional service from other infrastructures
(Positioning Services for location information)
5. What are the routing requirements in order to identify the
requirements to the Physical Layer.
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 12
Initial architecture: Routing Ad Hoc Framework
Context Roaming Module
•
Sub classes:
–
–
Specific Routing Module
+ Change_Context()
–
Specific Routing Module (implement the different Ad Hoc
routing algorithms; proactive, reactive, or others)
The Generic Ad Hoc module provides the functionality
common to any routing algorithm (packet processing, DB
management, replication modul,etc)
Kernel API, interacts with the Linux Kernel.
Network Servic Data
Ad Hoc
Framework API
+ change_Context_Req()
Gneric
DB Mngt
Routing Data
Generic Ad Hoc Module
ask_rt()
Kernel Ad
Hoc API
(f rom Kernel)
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 13
Initial architecture: Kernel Ad Hoc module
•
Sub classes:
– Kernel API, interacts with the Linux Kernel.
– Kernel Ad Hoc module, implements missing functions in order to
accomodate Ad Hoc framework module.
Kernel Ad
Hoc API
Kernel Ad Hoc module
(from Use Case View)
Kernel API
Kernel Routing Table
(f rom Use Case View)
(from Use Case View)
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Core Kernel
(f rom Use Case View)
Slide 14
Initial architecture design: Multiple interfaces
•
The Kernel Ad Hoc module will request information from the network
interfaes in order to get link state data.
• This information will be provided to the Ad Hoc Framework module to be
utilised by the appropiate AD Hoc algorithm.
WLAN Interface
Core Kernel
UMTS Interface
(f rom Use Case View)
Bluetooth Interface
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 15
Design requirements
1. Some nodes are highly mobile with small resources, some quite
static with more resources
•
Nodes classification
•
Classification criteria
2. Support for several routing algorithms and several link technologies
•
Division of the problem into different modules
•
Standardized API allows replacing modules
3. Support for persistent data required when Ad Hoc network is part of
another infrastructure (3G, 4G)
4. What are the routing requirements for service discovery to support in
order to request additional service from other infrastructures
(Positioning Services for location information)
5. What are the routing requirements in order to identify the
requirements to the Physical Layer.
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 16
Service discovery
Proposed extensions for network incentive and Service discovery
Routing Protocol specific fields
Message Type
Service Type
Network Service Announcement
Network Management (Charging)
Service Object
Service Data
Service Information
[Charging server Address,
Charging, info, Billing,
authentication info]
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 17
Service Discovery extensions in AODV
draft-koodli-manet-servicediscovery-00.txt, R. Koodli,C.
Perkins,Oct 2002, IETF work ongoing.
Message types:
Service discovery request: SREQ
Type Length
Service Type
Reserved
<Service-type> String
Service Request PRedicate
Service discovery response: SRESP
Type Length
Lifetime
URL length
URL (Variable length)
No URL auth
Auth blocks (if any)
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 18
Actual state: Framework
•
•
•
•
Initial division and classification of needed modules
Implementation of some components in those modules extracted from
existing implementations (UU, NIST, etc)
• Initial set of elements supporting AODV
• Tested among (4-5) fixed nodes for debugging purposes
Including new modules for IPV6 (HUT)
• Support for AODV over IPV6
• After tested would it would be provided as library
Next steps:
• Extend existing modules to support several routing protocols and
underlying transport layers
• Define the functionality of basic Context Sensitive Roaming Layer
• Implement the Attach-Detach procedure for separation between smart
and dummy nodes.
• Groups of collaborating smart nodes create ”Ad Hoc backbone”
• Extend the Ad Hoc Framework including service discovery extensions
• Test and provide scalability and performance results.
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 19
Additional info: Nokia
• Initial interest for contributing in MobileMAN project as partner proving
terminals for testing and participate in IAB.
• After few meetings the interest decreased because of different
company interests: BT-enabled terminals and WLAN access but the
Ad Hoc is seen as in-mature research area.
• They have some some relevant people working on the area towards
more mature technology but not ready to concentrate products on that.
• Result:
• They will participate in the IAB but do not provide terminals (The
available terminals that could be ready for adding Ad Hoc feature
as a new plug-in are Symbian)
• Latest findings: There is one project researching on alternatives OS to
Symbian and they finalised a prototype on Linux. This could be a
target for involving Nokia in MobileMAN but it is still too early for
getting a clear commitment.
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 20
This is where we are
right now!
Thank you for
your attention!
Questions,
suggestions for
continuing?
Jose Costa-Requena, Raimo Kantola, Nicklas Beijar / MobileMAN Kick-off/ CNR,Pisa 04-06.11.2002
Slide 21