IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-14-0060-00-MISU-OpenFlow_PoA Title: OpenFlow PoA proposal for SDN use case Date Submitted: March 20, 2014.

Slides:



Advertisements
Similar presentations
_link_parameter_report IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Definition and enhancements to MIH Link Parameter.
Advertisements

IEEE MEDIA INDEPENDENT SERVICES DCN: SAUC Title: Considerations for MIS framework to cooperate with SDN Date Submitted: July 11th,
xx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: July,
IEEE MEDIA INDEPENDENT SERVICES DCN: SAUC Title: Use cases of MIS framework to cooperate with SDN wireless access networks Date.
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: Discussion on “MGW vs. MIH-PoS” in IEEE c Date Submitted: Sept. 14 th, 2012.
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP-Session#57-Agenda Title: m Session #57 Agenda Date Submitted: July 18 th 2013 To be.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: PoA Capabilities of IE with IPv6 Prefix Availability Date Submitted: May 2006 Authors.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Utilizing terminal identifier to recognize the reserved resources.
MuGM IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Group management mechanisms Date Submitted: November, 2012 Authors or Source(s): Daniel.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Analysis on Identifiers Date Submitted: January 9, 2006 Presented.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Amendments for Event Register Date Submitted: July, 10, 2006 Presented.
MuGM IEEE MEDIA INDEPENDENT HANDOVER DCN: MuGM Title: Definition of IEEE d multicast identifiers Date Submitted:
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: sec Title: Message Flow Date Submitted: March 1, 2011 Authors or Source(s): Fernando Bernal-Hidalgo,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Handover Initiation Strategy Consistency Date Submitted: November,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Notify high layer when events change Date Submitted: Jan, 06,
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Problem Scenario Date Submitted: September, 2007 Presented at.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: FMCA MIH Work Item Date Submitted: March, 2009 Presented at IEEE.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Handover Initiation Strategy Consistency Date Submitted: November,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Comments Date Submitted: Jan, 06, 2006 Presented at IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: SAUC-Handover-Use-Case Title: Handover Use Case Date Submitted: January 22, 2014 To.
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: IEEE c TG November 2012 Report and Agenda Date Submitted: November.
21-06-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: The amendment for the MIH_Scan primitive Date Submitted: April,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: September,
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst Title: Overview of Draft P802.21b/D0.01 Date Submitted: May 11, 2010 Presented at IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: 100 Title: Cross Domain Trigger and Handover Talking Points Date Submitted: July 13, 2004.
IEEE MEDIA INDEPENDENT SERVICES DCN: SAUC Title: Use cases of MIS framework to cooperate with SDN wireless access networks Date.
IEEE DCN: SAUC Title: TG Closing Note Date Submitted: November 14, 2013 Presented at IEEE session #59 in Dallas, Texas,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: New scenarios for Date Submitted: May 16, 2013 To be presented at… Authors or Source(s): Daniel.
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 DCN: Title: Load balancing in heterogeneous network use case Date Submitted:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: MISU
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
REVP Session#64 Opening Note
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
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 DCN: SAUC Title: TG Closing Note Date Submitted: Nov 06, 2014
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE DCN: Title: TG Opening Note Date Submitted: Mar 09, 2015
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
Date Submitted: June 2nd, 2008 Radio States
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Your Title Here
Presentation transcript:

IEEE MEDIA INDEPENDENT HANDOVER DCN: MISU-OpenFlow_PoA Title: OpenFlow PoA proposal for SDN use case Date Submitted: March 20, 2014 To be presented at IEEE TG, Beijing Wireless Plenary meeting Authors or Source(s): Charlie Perkins Abstract: This contribution to IEEE Wireless Plenary in Beijing during March, 2014 proposes that design an OpenFlow interface from PoS to PoA MISU OpenFlow_PoA

2 IEEE presentation release statements This document has been prepared to assist the IEEE 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 The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws and in Understanding Patent Issues During IEEE Standards Development Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6http://standards.ieee.org/board/pat/faq.pdf MISU OpenFlow_PoA

Use Case Proposal for the Wireless & Mobility Working Group Daniel Corujo, Carlos Guimarães, Rui Aguiar Charles Perkins Subir Das MISU OpenFlow_PoA

Outline Introduction Base Scenario Proposed System Plan MISU OpenFlow_PoA

Introduction IEEE targets the facilitation and optimization of handover scenarios  In multi-technology environments It provides technology-agnostic…  … Link layer events (i.e., link up, link down, link parameter changes  RSSI)  … Link layer commands (i.e., device link actions, network point of attachment query and commit) MISU OpenFlow_PoA

Introduction (cont’d) These are quite useful for  Detecting and acting regards the dynamics of wireless environments  Convey this information/actions in a remote way Different scenarios become enabled  Handover optimization  Monitoring  Load balancing  … MISU OpenFlow_PoA

Base Scenario Empower networking control/management/configuration mechanisms with the ability to  Perceive the Mobile Terminal’s perspective on its wireless link to the network, and leverage it to …  Determine an action to re-optimize/re-configure/re- control/re-manage that wireless link  And others involved/impacted MISU OpenFlow_PoA

Base Scenario (cont’d) Specific SDN impact of the scenario  The controller gets “fed” with link status information from wireless network entities  Either through query or triggered events –Thresholds can be pre-configured and events registered  The controller can re-organize SDN flows affected by wireless link conditions  Either wireless backhaul, or links terminating in wireless Points of Attachment  It also enables preemptive actions, through the preparation of links before the mobile nodes move there MISU OpenFlow_PoA

Examples – Load Balancing OpenFlow PoA #1 OpenFlow PoA #2 MN OpenFlow Switch OpenFlow Controller MN MISU OpenFlow_PoA

Examples – Handover Optimization PoA sends monitoring data to Controller (i.e., Load Values) OpenFlow PoA #1 OpenFlow PoA #2 OpenFlow Switch OpenFlow Controller MN MISU OpenFlow_PoA

Examples - Monitoring OpenFlow PoA #1 OpenFlow PoA #2 MN OpenFlow Switch OpenFlow Controller CN MN MISU OpenFlow_PoA

Proposed System Wireless Interfaces (at Network Equipment and mobile terminals)  Able to provide wireless link related information to an “OpenFlow Controller”  New counters, parameters… OpenFlow PoA #1 OpenFlow Switch OpenFlow Controller MN MN wireless interface information PoA wireless interface information Ctrl combines MN and PoA Wireless info w/ Ethernet Switch Info, for optimization MISU OpenFlow_PoA

Proposed System (cont’d) Controller is able to send commands to wireless entities  Controlling wireless link aspects operation Controller makes use of previously collected/received wireless information  Reconfigures both wired/wireless affected equipment OpenFlow PoA #1 OpenFlow Switch OpenFlow Controller MN MISU OpenFlow_PoA

Plan Dual evolution process  Some aspects discussed here can also motivate evolutions in IEEE  IEEE – Services and Use Cases  For example, PoA-based events Leverage from existing work, showcasing OpenFlow and Wireless integration scenarios  I.e., previous demo Next step: Assess architectural and protocol impact to OpenFlow  Identify parameters, structures and procedures MISU OpenFlow_PoA

THANK YOU! MISU OpenFlow_PoA