1 / 6

Enhancing IETF MIF API for Effective Application Connectivity Management and Notifications

This document outlines future work for the IETF MIF Team, focusing on enhancing the existing MIF API. Key objectives include extending the API to support additional message notifications, drafting requirements for an abstract notifications API, and providing recommendations for managing interface changes using the MIF API. The synergy between IETF MIF and IEEE 802.21 is emphasized, promoting collaboration to avoid redundancy and ensure effective application hints, predictive signaling, and access network control, ultimately improving user experience and connectivity management.

janet
Télécharger la présentation

Enhancing IETF MIF API for Effective Application Connectivity Management and Notifications

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. IETF MIF &IEEE 802.21 Subir Das Juan Carlos Zuniga

  2. Future IETF MIF work(from OMA-MIF Workshop at IETF83) 1) Extend current MIF API to add additional messages for notifications. 2) Write a draft to define requirements for an abstract notifications API. 3) Write an informational draft that provides recommendations about using the MIF API in order to handle interface changes.

  3. IETF MIF API Application Connectivity Management • Application hints that it wants to connect • Application hints that connection is idle • Application hints that connection can be broken • API hints that Interface/PD is going away • API indicates that interface is going away • API indicates that interface is expensive • Etc?

  4. IEEE 802.21 MIHS (Control Plane) • Provides predictive signaling that can proactively trigger handovers or flow mobility and hence enhance QoE (ES) • Allows a better control of lower layers to enforce Operator and User’s policies (CS) • Provides information about available access networks (IS) MIH User (MIP, Policy Control, Conn Mngr) MIH_SAP (API) MIHF MIH_Link_SAP(API) L2(IF#1) L2(IF#2) L2(IF#n) … L1 L1 L1

  5. IEEE 802.21 MIH_SAP Media Independent Services (partial list) • MIH_Capability_Discover • MIH_Register • MIH_Event_Subscribe • MIH_Link_Parameters_Report/Get • MIH_Link_Detected/Up/Down/Going_Down • MIH_Link_Handover_Imminent/Complete • MIH_Link_Configure_Thresholds • MIH_Link_Actions • MIH_MN_HO_Commit/Complete/Query • MIH_Get_Information

  6. Recommendations • IETF MIF should not re-do the work that 802.21 has already done • 802.21 defines a Media Independent Services SAP (API) that provides most of the functionalities that MIF is looking for • 802.21 also defines low level Media Specific SAPs for the underlying access technologies • IETF MIF should identify requirements and make references to 802.21 SAPs where appropriate • If non-existing functionalities are identified both MIF and 802.21 should work together

More Related