1 / 6

Application Programming Interface to a Trigger Database for MOBIKE

Application Programming Interface to a Trigger Database for MOBIKE. < draft-schilcher-mobike-trigger-api-02.txt > Udo Schilcher Hannes Tschofenig Franz Muenz. Motivation. MOBIKE has to maintain an address list for all available interfaces

Download Presentation

Application Programming Interface to a Trigger Database for MOBIKE

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. Application Programming Interface to a Trigger Database for MOBIKE <draft-schilcher-mobike-trigger-api-02.txt > Udo Schilcher Hannes Tschofenig Franz Muenz

  2. Motivation • MOBIKE has to maintain an address list for all available interfaces • Many events for changing the address set are out of scope of MOBIKE,e.g., IEEE 802.21 Media Independent Handover (MIH) • These information have to be combined with higher layer information

  3. GPRSphone AP2 AP1 R2 GGSN BSS SGSN R1 Scope of the MOBIKE work A Making Information available to various protocols MOBIKE IKEv2 Mobility control Policy 802.21 B SEND 802.11 NUD DNA 802.3 IPv4 ESP PPP TCP BT IrDA IPv6 MOBIKE playground

  4. Features • Define an API to insert these information (so called triggers) into a DB • Triggers can be provided to MOBIKE and other higher layer protocols • Offered services are quite similar to MIH,but can be extended for other protocols • PF_TRIGGER IF is analogue to PF_KEY (based on BSD routing socket API) Note: Please do not misunderstand the term „database“. We solicit input for better terminology here.

  5. High-Level Interaction Optional; integration with IEEE 802.21 could be useful.

  6. Conclusion • This is an attempt to define an API to make mobility related information available. • Please let us know if you think that this work is useful. • Code might be available in the near future.

More Related