IEEE MEDIA INDEPENDENT HANDOVER DCN:

Slides:



Advertisements
Similar presentations
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Your Title Here Date Submitted: Month, NN, 200x Presented at IEEE.
Advertisements

xx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: July,
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Handover Procedure – Redraw of Annex Figure Date Submitted: January.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx Title: Template for Handover Flow Diagram Date Submitted: Nov 6, 2006 Presented at IEEE.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Problem Scenario Date Submitted: September, 2007 Presented at.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Comments Date Submitted: Jan, 06, 2006 Presented at IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Registration Amendments Date Submitted: Nov.13, 2006 Submitted for discussion.
IEEE MEDIA INDEPENDENT HANDOVER DCN: 100 Title: Cross Domain Trigger and Handover Talking Points Date Submitted: July 13, 2004.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposal for power consumption information related to different.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: August,
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER SERVICES
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
Date Submitted: July 9, 2008 Radio States
IEEE MEDIA INDEPENDENT HANDOVER SERVICES
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
Date Submitted: June 2nd, 2008 Radio States
IEEE MEDIA INDEPENDENT HANDOVER DCN: mrpm
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Your Title Here
Presentation transcript:

IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-04-0098-00-0000. Title: Handover Scenarios and Use Cases between 802.16 and 802.11 Date Submitted: July, 13, 2004 Presented at IEEE 802.21 session 3 in City Authors or Source(s):   Xiaoyu Liu, Youn-Hee Han Abstract: This is the abstract text. Replace this text with a short statement of the contents and purpose of the presentation. Communicate well, you only have a few lines or so to convey the essence of the slides. 21-04-0098-00-0000

IEEE 802.21 presentation release statements This document has been prepared to assist the IEEE 802.21 Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change 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 the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.21. The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual <http://standards.ieee.org/guides/opman/sect6.html#6.3> and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html>  21-04-0098-00-0000

Handover Scenarios and Use Cases between 802.16 and 802.11 Xiaoyu Liu xiaoyu.liu@samsung.com Youn-Hee Han yh21.han@samsung.com 2004-07-07 21-04-0098-00-0000

Contents Background Handover Scenarios and Use Cases Suggestions and Open Issues 21-04-0098-00-0000

Background (1) 802.16 WMAN 802.11 WLAN Infrastructure Technology Large Coverage Low Population Density 802.11 WLAN Hot Spot Technology Moderate Coverage Dense Aggregations of People and Users 21-04-0098-00-0000

Background (2) Integration of 802.16/802.11 Standards Seamless Handover based on the User Location and Movement Optimization of Cost, Resources and Performance Standards WMAN: 802.16 WLAN: 802.11 a/b/g AP AP AP AP 21-04-0098-00-0000

Handover Scenarios (1) Enforced Service Continuity When one interface is (or will be) disabled, another connection is established to keep session continuity VHO Events initiated from lower layers: e.g. link down / link going down H/O Use Cases: 1 & 2 1 1 2 21-04-0098-00-0000

Handover Scenarios (2) Policy Driven Selection The current interface is qualified while other interfaces are available, active session is switched from one interface to another driven by policies or smart decision makers VHO Events initiated from upper layers: e.g. link switch H/O Use Cases: 3 & 4 1 3 4 21-04-0098-00-0000

Use Cases: Enforced Service Continuity A user who is using 802.11 service goes out of the hot spot coverage. The STA detects the degradation of WLAN signal and seamlessly handover the active session from .11 to .16 WMAN without user intervention A user who is using 802.16 service goes into blind areas of WMAN coverage where 802.11 WLAN is deployed. The STA detects the degradation of WMAN signal and seamlessly handover the active session from .16 to 11 without user intervention Use Case: Fast Mode A user who is using 802.11 service drives through or out of the hot spot coverage. Because of the high speed movement and short overlapping distance, a new 802.16 connection is established with very short latency. Tight coupling (with L2/L2.5 handover) might be a candidate solution for the fast mode handover between WMAN and WLAN. 21-04-0098-00-0000

Use Cases: Policy Driven Selection A user who is using 802.16 WMAN service goes into an area covered with several 802.11 AP and another 802.16 BS. Some WLAN APs are owned by public WLAN operator, some by company for intranet. When the STA detects the availability of multiple neighbors, the smart decision maker selects the optimal one based on user preferences and a set of policies, then handover the active session from .11 to the optimal interface without user intervention. (Note that link up event might not trigger a VHO immediately) 21-04-0098-00-0000

Proposals Technical Requirements (4.1) Sub-headings below the bullet for handover scenarios between 802.11/802.16 Enforced Service Continuity in handover between 802.11/802.16 Policy Driven Selection in handover between 802.11/802.16 21-04-0098-00-0000

Open Issues Open Issues regarding internetworking Models Loose Coupling 802.11 AP and 802.16 BS Connected via External IP Networks L3 Handover between 802.11 and 802.16 L3 protocols, e.g. Mobile IP, seems to be a natural solution Tight Coupling AP and BS Connected via L2(or L2.5) devices (in the same subnet) L2 Handover between 802.11 and 802.16 (shorter connection re-establishment latency) for Fast Mode cases Are the .16 and .11 MACs are compatible to be bridged? Are we going to develop a L2/L2.5 internetworking protocol for 802.11/802.16 in .21 WG? 21-04-0098-00-0000