doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide Handoff ECSG Overview for Joint 16e/Handoff David Johnston

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide 2 Purpose Explain what has been done in 802 Handoff Understand areas of possible intersection with e Make sure we aren’t heading for a train wreck!

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide 3 Problems We Are Addressing You don’t know what you attached to when you associated/registered/plugged into a L2 network Upper layers don’t know what is going on at L2 and so can’t make good handover decisions There is no media independent way of asking for handover related information over a link. A conduit is needed.

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide 4 The Link Interface A media independent protocol operating over 802 links –Get handover or network detection and selection information –Maybe act as conduit for event into –Maybe act as conduit for backhaul signalling CUPE model being promoted –Controlled and Uncontrolled Port Entity

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide x

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide 6 CUPE* Model *Controlled/Uncontrolled Port Model

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide 7 What about 802.1X in ? We build on the 802.1X to give us a conduit Backhaul AAA schemes may mandate it –So be aware that it may infiltrate products regardless of the specification Its only a conduit –So can put in its own substitute conduit –We could do it in handoff as a recommended practice –Probably only a container frame for Handover IEs.

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide 8 Handover Information Define a set of structured information that can be used to make handover decisions –Try to align with structured information from non 802 groups to allow effective interworking with them IETF, 3GPP, 3GPP2 –Achieve levels of mapping Structure equivalence – easy Semantic equivalence – requires hard work Encoding equivalence – next to impossible

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide 9 Triggers An API or management interface or MIB or MAC service interface to: –L2 Triggers An enabler for fast mobile IP Advanced handover decision making –Trajectory –Location based –Preemptive handover preparation Triggers not yet defined –Strong will to align triggers between the groups/IETF etc.

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide 10 Network Detection and Selection Early discovery of access point properties –What’s going on at L3 – IP, DHCP, subnets etc –What’s going on at L2 – VLAN, 1X –What auth services are required/supported –Neighbor, channel, location information –QoS capabilities/capacities Improve scanning efficiency –Neighbor lists

doc.: 802_Handoff_Joint_Handoff_16e_Session Submission July David Johnston, IntelSlide 11 Network Detection and Selection We are proposing means by which very early, non secured information can be accessed by mobile stations –Not so relevant for Longish attachment time Other methods can substitute –Backhaul communication –Preemtive triggers –Pre authentication –Neighbour lists.