MIF API extension for combining IEEE 802.21
draft-zhang-mif-api-extension-802-21-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-05-29
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MIF                                                       Hongke Zhang
Internet Draft                                               Fei Song
Intended status: Informational                               Boxin Du
Expires: November 29,2016                                    Mi Zhang
                                           Beijing Jiaotong University
                                                          May 29, 2016

                MIF API extension for combining IEEE 802.21
                draft-zhang-mif-api-extension-802-21-04.txt

Abstract

   The Application Program Interface (API) of MIF, specified in the MIF
   API consideration, must rely on lower layer functionalities when
   handover between homogeneous or heterogeneous networks is necessary.
   To improve the connectivity performance, the existing MIF API needs
   to be extended. IEEE is also aimed at the similar issue from
   different way. A kind of logical entities over the link layer
   protocol for handling the seamless handover has been defined in IEEE
   802.21. This document proposes a mechanism via integrating MIF API
   and IEEE 802.21 to support application service better.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other documents
   at any time.  It is inappropriate to use Internet-Drafts as
   reference material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 28, 2016.

Zhang, et al.         Expires November 29,2016                [Page 1]
Internet-Draft            MIF API extension                   May 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with
   respect to this document. Code Components extracted from this
   document must include Simplified BSD License text as described in
   Section 4.e of the Trust Legal Provisions and are provided without
   warranty as described in the Simplified BSD License.

Zhang, et al.         Expires November 29, 2016               [Page 2]
Internet-Draft            MIF API extension                   May 2016

Table of Contents

   1. Introduction ................................................ 4
   2. Terminology ................................................. 4
   3. The Relationship between IEEE MIHF and MIF API .............. 4
   4. The Extension of MIF API for Handover: A Case Study ......... 8
      4.1. The MN-initiated Handover .............................. 8
         4.1.1. Get Information ................................... 8
         4.1.2. Information Post .................................. 9
         4.1.3. Parameter Report .................................. 9
         4.1.4. Check Resources MN ................................ 9
         4.1.5. Resource Availability ............................. 9
         4.1.6. Connect to Interface .............................. 9
         4.1.7. Resource Preparation Messages .................... 10
         4.1.8. Establish Link Messages .......................... 10
         4.1.9. Link Up .......................................... 10
         4.1.10. Handover Completed .............................. 10
         4.1.11. Handover Completion Confirmation ................ 10
      4.2. The Network-initiated Handover ........................ 10
         4.2.1. Candidate Query Notification ..................... 11
         4.2.2. Candidate Query Result ........................... 11
         4.2.3. Check Resources Net .............................. 12
         4.2.4. Confirm Chosen Target ............................ 12
         4.2.5. Establish Link Messages .......................... 12
         4.2.6. Link Up .......................................... 12
         4.2.7. Handover Completed ............................... 12
         4.2.8. Handover Completion Confirmation ................. 12
   5. Discussions for New Messages from MIF Perspective .......... 12
      5.1. Get Information........................................ 13
      5.2. Release the Ongoing Connection ........................ 13
      5.3. Establish New L2 Connection ........................... 13
   6. Discussions for New Messages from IEEE Perspective ......... 13
Show full document text