MIH implementation: Difference between revisions
| Line 10: | Line 10: | ||
*SAP -- interfaces between them. | *SAP -- interfaces between them. | ||
In ns-3, the MIH framework is being implemented by taking profit of the native "Object Aggregation" mechanism. | In ns-3, the MIH framework is being implemented by taking profit of the native "Object Aggregation" mechanism. You have to consider the following generic class if you want to make any interaction with the MIH framework: | ||
*MihLinkSap -- exposes the MIH_LINK_SAP interface to NetDevice | *MihLinkSap -- exposes the MIH_LINK_SAP interface to NetDevice | ||
*MihSap -- exposes the media independent MIH_SAP to MIH_USER | *MihSap -- exposes the media independent MIH_SAP to MIH_USER | ||
The MIH FUNCTION block is implemented as final class MihFunction, so there is no need to extend its functionalities. | |||
For each technology type, you have to subclass the generic class MihLinkSap and "Add" it to you | |||
=== API description === | === API description === | ||
Revision as of 11:52, 1 November 2008
The goal of this article is to describe the ongoing implementation framework of the emerging 802.21 standard in ns-3. If you arrived here following your high curiosity line, that's great but assure that you have first read a few documents regarding that draft standard.
Main Page - Roadmap - Summer Projects - Project Ideas - Developer FAQ - Tools - Related Projects
HOWTOs - Installation - Troubleshooting - User FAQ - Samples - Models - Education - Contributed Code - Papers
Overview
MIH framework in NS-3
In MIH, the main blocks are:
- MIH Function
- MIH User
- Link -- called NetDevice in ns-3
- SAP -- interfaces between them.
In ns-3, the MIH framework is being implemented by taking profit of the native "Object Aggregation" mechanism. You have to consider the following generic class if you want to make any interaction with the MIH framework:
- MihLinkSap -- exposes the MIH_LINK_SAP interface to NetDevice
- MihSap -- exposes the media independent MIH_SAP to MIH_USER
The MIH FUNCTION block is implemented as final class MihFunction, so there is no need to extend its functionalities. For each technology type, you have to subclass the generic class MihLinkSap and "Add" it to you
API description
Where is what?
Use of smart pointers
Designing choice structures
Tasks completed so far
By now, the following MIH blocks are defined:
- An abstract MIH_LINK_SAP class and its primitives
- An abstract MIH_SAP class and its primitives (except those related to remote communication)
Ongoing development
The following tasks are being held currently:
- Implementation of the MIH_FUNCTION for local MIH events and commands exchanges:
- Link events delivery from MIH_LINK_SAPs to MIH_USERs (through MIH_SAPs)
- Command delivery from MIH_USERs to MIH_LINK_SAPs
Foresights
In this section, you will find various components that are still needed to have start some MIH framework tests.
They are presented in their order of priority:
Local MIH exchanges
- Integration with WifiNetDevice and WimaxNetDevice
- WifiMihLinkSap -- ready to be done
- WimaxMihLinkSap -- until Wimax is validated
- Examples of MIH Users entities:
- A simple application is to be defined later.
Remote MIH exchanges
- The MIH Protocol including:
- Packet TLV formats
- MIH message header format
- Transport of MIH messages over L3+ plane
- MIIS
- RDF schemas