1. Media Independent Handover
January 2006
11-06-xxx
March 2006
Media Independent Handover
Date:
Authors:
Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Eleanor Hepworth, Siemens Roke Manor

2. Abstract Proposal for Media Independent Handover Cluster, R9H1.
January 2006
11-06-xxx
March 2006
Abstract
Proposal for Media Independent Handover Cluster, R9H1.
Eleanor Hepworth, Siemens Roke Manor

3. Similarities & Differences between 291r0 and 289r0
March 2006
Similarities & Differences between 291r0 and 289r0
Similarities
Protocol Architecture for MIH
Link layer events (primitives)
MIH Capability Indication
MIH Protocol Action Frame
Differences
Interface between AP and MIHF entity
MAC address Advertisement over Beacon (Optional)
Primitives to covey MIHF frame to/from MAC
2 primitives
Service Type information in action field

4. MIHF Deployment Scenario
March 2006
MIHF Deployment Scenario
MIHF-AP : AP with MIHF
Interface with MIHF-AP:
Using over the DS communication
Reuse 11r relaying mechanism
MIHF-AP MAC address shall be delivered to STA
Implementation Specific

5. MIH Capability Indication
March 2006
MIH Capability Indication
A new information element is defined for MIH capabilities
Order
Size (octets)
Description 1
TBD Element ID (to be assigned by the IEEE Assigned Numbers Authority): defines the Extended Capability IE 2
Length 3
MIH Capabilities 4 6
MIHF-AP MAC Address (optional)
Extended Capability Information Element
MIH Capabilities

6. MIH Transport Proposal
March 2006
MIH Transport Proposal
MIH Protocol Message Action frame
Define one MIH Protocol Message Action frame and use in all states.
MIHF frame is encapsulated into MIH Protocol Message Action frame
MAC does not need to know how to generate MIHF frame
Different Action field value is applied to different MIH services in order to prevent ES/CS delivery in state 1.
MIH Protocol Message Action Frame

7. March 2006
MIH Transport
Information Service and System Management Service are the target in Un-Authenticated and Un-associated State
Use of MIH Protocol Message Action frame implies
MIH function in STA uses MLME_SAP to transmit and receive MIHF frame
creates action frame and transports the MIHF frame
AP forwards action frame
Using over the DS communication
AP relays action frame using r relaying mechanism (Remote Request/response)
Implementation Specific Interface
in AP may have to reconstruct the message to forward to appropriate entity
For the response, the opposite process takes place

8. MIH Remote Message Delivery Primitives
March 2006
MIH Remote Message Delivery Primitives
New primitives are defined to deliver MIH frame from MIHF to MAC

9. 1) MLME-MIHProtocol.request
March 2006
1) MLME-MIHProtocol.request
Function
- This primitive is used for MAC to generate MIH protocol action frame. ‘MIHF Frame’ within this primitive is carried to AP through the MIH Protocol Action Frame.
Semantics
- STA Address
- Destination Address
- Service ID (1: System Management, 2: ES/CS services, 3: IS service)
- MIHF Frame
When generated
- This primitive is generated by MIH Function of the STA or MIHF-AP when the MIH Function needs to deliver MIHF Frame to MAC layer .
Effect on receipt
- MAC layer of the STA or MIHF-AP generates MIH Protocol Action frame in order to transmit MIH Frame remotely.

10. 2) MLME-MIHProtocol.indication
March 2006
2) MLME-MIHProtocol.indication
Function
- This primitive is used for MAC layer to notify MIH function of MIH Protocol Action frame delivery.
Semantics
- STA Address
- Destination Address
- Service ID (1: System Management, 2: ES/CS services, 3: IS service)
- MIHF Frame
When generated
- This primitive is generated by MAC layer of the STA or MIHF-AP when MIH Protocol Action Frame is received.
Effect on receipt
- MIH Function of the STA or MIHF-AP receives MIHF Frame transmitted remotely.

11. MIH Protocol Action Frame
March 2006
MIH Protocol Action Frame
Action Frames are defined to deliver MIH Protocol messages to AP
Action field value
Description
Reserved 1
MIH Protocol Message
2-255
Name
Value
MIH Protocol - I xx
MIH Protocol - II
MIH Protocol - III
Reserved
xx-27
Category field
Action Field
Mapping with Service ID
MIH Protocol Message Action Frame

12. 802.11 MAC Transparency March 2006 STA AP MIHF-AP
Optional [X]
STA AP
MIHF-AP
MIH
MAC
RRB
MIH
Beacon ([MIHF-AP]
MLME-Scan.confirmation
If MIHF-AP is not known to STA, this procedure would be implementation specific
MLME-MIHProtocol.request
(MIHF Frame->IS)
MIH Protocol Action Frame
(“Action” =Protocol- III)
AP checks STA’s state and “Action” field value.
AP discards if ES/CS is transmitted in state 1
Remote Request (MIH Action Frame)
MLME-MIHProtocol.indication
(MIHF Frame->IS)
MLME-MIHProtocol.request
(MIHF Frame->IS)
Remote Response (MIH Action Frame)
MIH Protocol Action Frame
(“Action” =Protocol-III)
MLME-MIHProtocol.indication
(MIHF Frame->IS)