21-07-0009-02-0000-MIH User generated events

8/14/2019 21-07-0009-02-0000-MIH User generated events

1/15

21-07-0009-02-0000

IEEE 802.21 MEDIA INDEPENDENT HANDOVER

DCN: 21-07-0009-02-0000

Title: Events generated by MIH Users

Date Submitted: March, 13th, 2007

Presented at IEEE 802.21 session #19 in Orlando, FLAuthors or Source(s):

IEEE 802.21 WG

Abstract: Discussion on the communication between MIH_Users


2/15

21-07-0009-02-0000

IEEE 802.21 presentation release statements

This document has been prepared to assist the IEEE 802.21 Working Group. It isoffered as a basis for discussion and is not binding on the contributingindividual(s) or organization(s). The material in this document is subject tochange in form and content after further study. The contributor(s) reserve(s)the right to add, amend or withdraw material contained herein.

The contributor grants a free, irrevocable license to the IEEE to incorporate

material contained in this contribution, and any modifications thereof, in thecreation of an IEEE Standards publication; to copyright in the IEEEs nameany IEEE Standards publication even though it may include portions of thiscontribution; and at the IEEEs sole discretion to permit others to reproduce inwhole or in part the resulting IEEE Standards publication. The contributoralso acknowledges and accepts that this contribution may be made public byIEEE 802.21.

The contributor is familiar with IEEE patent policy, as outlined inSection 6.3 of the IEEE-SA Standards Board Operations Manual and in UnderstandingPatent Issues During IEEE Standards Developmenthttp://standards.ieee.org/board/pat/guide.html>
http://standards.ieee.org/guides/opman/sect6.htmlhttp://www.ist-daidalos.org/http://standards.ieee.org/board/pat/guide.htmlhttp://standards.ieee.org/board/pat/guide.htmlhttp://standards.ieee.org/board/pat/guide.htmlhttp://standards.ieee.org/board/pat/guide.htmlhttp://www.ist-daidalos.org/http://standards.ieee.org/guides/opman/sect6.html


3/15

21-07-0009-02-0000

Assigned Comment #16:

MIH User Events

Comment 3041 from LB #1b


4/15

21-07-0009-02-0000

Introduction

Current draft (Section 1.2, page 2, line 5):

"The standard addresses the support of handovers for both mobileand stationary users. For mobile users, handovers may occurdue to changes in wireless link conditions. [...].Another

possibility is that the user may choose an application which

requires a handover to a higher data rate channel, forexample during download of a large file.

How is the draft actually addressing this issue?


5/15

21-07-0009-02-0000

Introduction

Current communication model allows only upward events: FROMLower layers TOMIHF(Lower Layer Events) FROMMIHFTOMIH_Users (MIH Events)

PROBLEM: How to notify to MIH_Users about things (orevents) happening asynchronously in other MIH_Users?


6/15

21-07-0009-02-0000

Example

User is streaming video at low resolution.

User is currently connected to 3G, but is also within WLAN coverage.

User decides to change the application settings tohigh resolution

The action of the user may cause a handover to WLAN, seeking for a higherthroughput to support the resolution demanded by the user.

Notification FROM theApplication (an MIH_User) TO theHO_decision_module(another MIH_User) which may decide to initiate a handover or not. How? 4 possible solutions (so far)

MIH Function

WLAN 3G

Application HO decision module

?


7/15

21-07-0009-02-0000

Other examples

MME is the MIH User generating this event:

MME completes a handover which implies a "cost change event shouldbe notified to another MIH_User (application prompting on screen, forinstance)

prompted notification of the networks discovered in order to allow theuser choose which network to connect to.

Being a mobility protocol (e.g. MIP) the originator MIH User: BU (Binding Update) has just been successfully sent, which may cause

the MME to start preparing buffers for receiving bicasted packets, orperform any other transition in the internal state machine.

Being a video application the originator MIH User: User has changed preferences to a high resolution codec, which may

cause the MME to handover to a different link with more capacity.


8/15

21-07-0009-02-0000

Solution A

Communication between MIH_Usersnot specified by 802.21.

It can be achieved throughproprietary mechanisms, locallyand remotely.

Local

Remote

MIH Function

WLAN 3G

App HO module

MIH Function

WLAN 3G

App

MIH Function

WLAN 3G

HO module


9/15

21-07-0009-02-0000

Solution A

PROs:

No need to change current draft D04.00 Applications (or MIH Users in general) do not have to beMIH aware

CONs: No standard interface between MIH_Users Every application (and MIH User in general) will have to

build proprietary interfaces with other MIH_Users (e.g. HOmodules)


10/15

21-07-0009-02-0000

Solution B

Enabledownwards direction for MIES in addition to upward

events. Local

Remote

MIH Function

WLAN 3G

App HO module

MIH Function

WLAN 3G

App

MIH Function

WLAN 3G

HO module

User Event MIH Event

User Event MIH EventMIH Event

Added/Modified to MIH

No modification to MIH


11/15

21-07-0009-02-0000

Solution B

PROs:

Semantically, MIES better suits the kind of information wewant to transmit: things happening asynchronously(events). MICS implies to request an action and MIIS is fornon time critical information.

MIH_Users will subscribe to this type of events via the

MIHF. Same behavior as Link_Events. When a newMIH_User is started will inform the MIHF of the eventsoffered.

CONs: The direction of MIES has to be modified: also downward

events instead of only upward events New event(s) need to be specified in the draft.


12/15

21-07-0009-02-0000

Solution C

Addnew commandto send notification to other MIH_Users

(eg: MIH_Notify) Local

Remote

MIH Function

WLAN 3G

App HO module

MIH Function

WLAN 3G

App

MIH Function

WLAN 3G

HO module

1.Request Added/Modified to MIH


4.Conf

1.Request 3.Indication6.Confirm 2.Request

5.Response

4.Response

2.Indication3.Resp


13/15

21-07-0009-02-0000

Solution C

PROs:

Only one modification: add a new command to the MICS(eg: MIH_Notify)

CONs: Needs to be a primitive able to carry different types of

notifications Closed or open list?


14/15

21-07-0009-02-0000

Solution D

Addnew command(eg: MIH_Notify)combined with regular

MIH Event Local

Remote

MIH Function

WLAN 3G

App HO module

MIH Function

WLAN 3G

App

MIH Function

WLAN 3G

HO module

1.Request 3.MIH Event Added/Modified to MIH


2. Confirm

1.Request 4.MIH Event2.Confirm3.Remote MIH Event


15/15

21-07-0009-02-0000

Solution D

PROs:

Only modification: add a new command to the MICS (eg:MIH_Notify) Subscription mechanism problem (solution C) solved. When

MIHF receives the MIH_Notify, MIHF will send an eventonly to MIH_Users subscribed to that particular event.

CONs: Semantically, the kind of information is more an event than

a command. New event(s) need to be specified in the draft.

Documents

21-07-0009-02-0000-MIH User generated events