21-04-0257-00-0000 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN:21-04-0257-00-0000-draft_invariants Title: Invariants in Proposed Drafts Date Submitted:

Slides:



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

xx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: July,
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: Reference Model and Use-Cases for Information Service Date.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Analysis on Identifiers Date Submitted: January 9, 2006 Presented.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Subscription ID Scope Date Submitted: June, 14 th, 2007 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:
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Information Service Flow Update Date Submitted: October 22, 2006.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Instructions to get a Free IEEE Web Account Date Submitted: January.
21-05-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Support for query of the registered event at MIH Layer and Link.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Handover Initiation Strategy Consistency Date Submitted: November,
Doc.: IEEE /0310r0 Submission Sept 2007 Srinivas Sreemanthula Slide 1 IEEE MEDIA INDEPENDENT HANDOVER DCN: MIH-Security-Options.ppt.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Notify high layer when events change Date Submitted: Jan, 06,
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Handover Flow Diagrams Update Date Submitted: May 14, 2007 Presented.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Problem Scenario Date Submitted: September, 2007 Presented at.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Capability Discovery Amendment Date Submitted: April 20, 2006.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: FMCA MIH Work Item Date Submitted: March, 2009 Presented at IEEE.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Session Identifier Date Submitted: February 17, 2006 Presented.
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
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IEs related Issues Date Submitted: March 2007 Presented at IEEE session.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Optimize MIIS Get Information Message Date Submitted: February.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Reference Model and Use-Cases for Information Service Date.
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: Title: Amendment-for-Link_Handover_Complete.Indication- primitive Date.
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst Title: Overview of Draft P802.21b/D0.01 Date Submitted: May 11, 2010 Presented at IEEE
21-05-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Amendment for MIH_Handover_Initiate.request Date Submitted: April.
xx-00-XXXX IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Workflow for IEEE Specification work Date Submitted: July, 11, 2005 Presented.
IEEE MEDIA INDEPENDENT HANDOVER DCN: 100 Title: Cross Domain Trigger and Handover Talking Points Date Submitted: July 13, 2004.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Multiple MIH User Issues Date Submitted: November, 12-16, 2007.
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
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
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: xxx
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 DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE “ Requirements” Date: Authors:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcast
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Your Title Here
Presentation transcript:

IEEE MEDIA INDEPENDENT HANDOVER DCN: draft_invariants Title: Invariants in Proposed Drafts Date Submitted: March, 16, 2004 Presented at IEEE session #7 in Atlanta, GA Authors or Source(s): David Johnston Abstract: This document attempts to identify draft text elements that are invariant under the current proposals and so clarify text that meets the needs outlined in all the proposals.

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 outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3

Services Proposed Proposed services have evolved to a common position Information Service Request/Response Information orthogonal to, or typed by media Available locally or remotely Event Service Source initiated Consumed by MIH or upper interface of MIH Pass across locally up the stack or down and across the local link to pass up the remote stack Sourced within MIH, MIH Upper Interface, MAC or PHY

Information Definition Defined Services need information of the appropriate type Information service Information definition per media type Media independent information specific information Event Service Event types Event semantics Event scope (local/remote/both, bounds)

Supporting Elements Information and Event Service requires supporting elements LLC differentiated message definitions Ethertype Internal payload structure, message classes, bit level coding Addressing rules SAP Definitions Upwards to Layer 3 Internal SAPs –Only necessary for internal structuring. Not required Primitives for both

Models The proposed services demand a model to allow conceptualization of the usage. E.G. Feeding information to a policy engine Ethertype Internal payload structure, message classes, bit level coding Addressing rules Feeding information to upper layers Upwards to Layer 3 Internal SAPs –Only necessary for internal structuring. Not required

Implications Any given model is more restrictive than the service definitions and supporting material, since it imposes a mode of use that the specification should not enforce E.G. Policy engine in MIH Policy engine above MIH Policy engine distributed horizontally or vertically These are different models and use but do not affect (mostly) the service, SAP or information definitions

Draft Text I expect the draft will be structures something like this: Introduction – Informative material, model assumptions Overview – Stack layering, interface locations Support Features Information base representation Event structure Ethertype Payload format Event service Event service upper interface primitive definitions Event service internal interface primtive definitions Information service Request/Response protocol Request/Response message defintions Upper interface primitive definitions

The Models in Context The policy engine is a consumer of events and information that may use that information to select the port to use, or select the point of attachment of an individual port This is divisible into The bit that determines preference The bit that imposes, requests or otherwise effects a handover It is the separation of these entities that leads to the only significant interface difference between the models

The Models in Context A simple binary decomposition of internal/external PE and internal/external control Model A, Internal PE and control Model B, External PE and control Model C, External PE, Internal control Model D, Internal PE, External control Port selection Port Preference identification MIH events Info req/rsp events Info req/rsp (e.g) (e.g.) Single interface advertised upwards L3 No preference or control signaling on SAP

The Models in Context A simple binary decomposition of internal/external PE and internal/external control Model A, Internal PE and control Model B, External PE and control Model C, External PE, Internal control Model D, Internal PE, External control Port selection Port Preference identification MIH events Info req/rsp MIH selection L3 Control Signaling On SAP!

The Models in Context A simple binary decomposition of internal/external PE and internal/external control Model A, Internal PE and control Model B, External PE and control Model C, External PE, Internal control Model D, Internal PE, External control Port selection Port Preference identification MIH events Info req/rsp L3 Preference Signaling On SAP!

MIH The Models in Context A simple binary decomposition of internal/external PE and internal/external control Model A, Internal PE and control Model B, External PE and control Model C, External PE, Internal control Model D, Internal PE, External control Port selection Port Preference identification MIH events Info req/rsp L3 Control Signaling On SAP!

Therefore Differences in the proposals and associated models might be significant But the difference in the text comes down to the presence of two forms of upper layer SAP primitives Control Imperatives, EG: Dot21_Select_Port_X Dot21_Change_attachment_Point Preference_Indicationss, EG: Dot21_Port_x_Preferred Dot21_Port_Weight_Map It doesn’t effect the definition of the event service, information service, transport, information base or events The presence of control imperative or preference indication does not impose their use. Define them and all models are supported. No other text changes between the proposals -> 95% of text is common.