1 / 11

802 Handoff ECSG Overview for Joint 16e/Handoff

802 Handoff ECSG Overview for Joint 16e/Handoff. David Johnston david.johnston@ieee.org dj.johnston@intel.com. Purpose. Explain what has been done in 802 Handoff Understand areas of possible intersection with 802.16e Make sure we aren’t heading for a train wreck!.

eunice
Download Presentation

802 Handoff ECSG Overview for Joint 16e/Handoff

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 802 Handoff ECSGOverview for Joint 16e/Handoff David Johnston david.johnston@ieee.org dj.johnston@intel.com David Johnston, Intel

  2. Purpose • Explain what has been done in 802 Handoff • Understand areas of possible intersection with 802.16e • Make sure we aren’t heading for a train wreck! David Johnston, Intel

  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. David Johnston, Intel

  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 David Johnston, Intel

  5. 802.1x David Johnston, Intel

  6. CUPE* Model*Controlled/Uncontrolled Port Model David Johnston, Intel

  7. What about 802.1X in 802.16? • 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 802.16 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. David Johnston, Intel

  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 David Johnston, Intel

  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. David Johnston, Intel

  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 David Johnston, Intel

  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 802.16 • Longish attachment time • Other methods can substitute • Backhaul communication • Preemtive triggers • Pre authentication • Neighbour lists. David Johnston, Intel

More Related