1 / 9

Layer 2.5 Functionality

Layer 2.5 Functionality. Peretz Feder Ajay Rajkumar Lucent Technologies May 13, 2004. Objectives. To crystallize the concept and boundary of layer 2.5 To describe the scope of the triggers with relation to Layers 3 and 2.5 Define interfaces to mobility management at layer 3

eudora
Download Presentation

Layer 2.5 Functionality

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. Layer 2.5 Functionality Peretz Feder Ajay Rajkumar Lucent Technologies May 13, 2004 21-04-00xx-00-0021-Layer2.5functionality

  2. Objectives • To crystallize the concept and boundary of layer 2.5 • To describe the scope of the triggers with relation to Layers 3 and 2.5 • Define interfaces to mobility management at layer 3 • Identify the decision entity and its relation to the executive entity 21-04-00xx-00-0021-Layer2.5functionality

  3. IETF based Layer 3 • Mobility mechanism is Mobile IP Handover capable • Layer 3 mobility is not optimized for real time applications • Objective is to improve or assist layer 3 handover performance • Do we have the mandate to change it in 802.21? • Lets explore layer 3- 21-04-00xx-00-0021-Layer2.5functionality

  4. Layer 2.5 Boundary Definition Mobile Node Network 21-04-00xx-00-0021-Layer2.5functionality

  5. Mobility Model • Multi radio interface at the MT • Network may not control (or own) all the interfaces available to the MT • Propose to include a layer 2.5 entity at the MT that selects one of the available interfaces. However, the selection mechanism is vendor specific!! • Network has peer-to-peer relation with the state machine entity • Network assisted through handover recommendation • Network assisted through SLA directory update • Upon decision, L2.5 invokes the layer 3 (IP) handover mechanism providing it a single access choice 21-04-00xx-00-0021-Layer2.5functionality

  6. Layer 2.5 Selection Entity • Selects a preferred access and let layer 3 execute without delay • How? Process all the triggers and apply a vendor specific algorithm • Triggers include locally measured attributes, loading conditions, available QoS, normalized signal quality • Hints include cost of link, roaming agreements, network provided neighboring list 21-04-00xx-00-0021-Layer2.5functionality

  7. Air-interface 3GHigh 3GMedium 3GLow 3GUnavailable 802.11High 802.11 802.11 802.11 802.11 802.11Med 802.11 802.11 802.11 802.11 802.11Low 3G 802.11 802.11 802.11 802.11NA 3G 3G 3G Work offline or sleep Example: Preference Rules Translated into Decision Matrix 802.11medium_threshold is preferred over 3Ghigh_threshold 802.11low_threshold is preferred over 3Gmedium_threshold 21-04-00xx-00-0021-Layer2.5functionality

  8. Interface 802.3 802.3 802.3 802.3NA 802.11High 802.3 802.3 802.3 802.11 802.11Med 802.3 802.3 802.3 802.11 802.11Low 802.3 802.3 802.3 802.11 802.11NA 802.3 802.3 802.3 Work offline or sleep Example: Preference Rules Translated into Decision Matrix 802.3is preferred over 802.11any_threshold 21-04-00xx-00-0021-Layer2.5functionality

  9. Recommendation • Don’t attempt to fix layer 3 deficiencies • Develop layer 2+ entity that assists layer 3 mobility • Don’t waste time defining the selection algorithm • Make layer 3 execute the handover decision • Define the interface to L3. Bidirectional SAP or Ethertype_21? • 3G can’t talk the Ethertype language • MIB is too slow 21-04-00xx-00-0021-Layer2.5functionality

More Related