IEEE P vs IEEE Date: Authors:

Slides:



Advertisements
Similar presentations
November 2005 doc.: IEEE /1051r0 09/06/2018
Advertisements

IEEE White Space Radio Status Report
IEEE P Wireless RANs Date:
[ Interim Meetings 2006] Date: Authors: July 2005
TGn Sync Atlanta Presentation on Confirmation
Media Independent Coexistence
IEEE White Space Radio Contribution Title
IEEE White Space Radio Status Report
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
March 2014 Election Results
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
3GPP Extended Date: Authors: July 2005 July 2005
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
3GPP liaison report July 2006
[place presentation subject title text here]
Descriptive Language Usage in TGv
IEEE White Space Radio Cognitive Plane
WRAN Protocol Reference Model(PRM)
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
TGu Motions Date: Authors: September 2006 September 2006
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
TGu Closing Report Date: Authors: September 2005
IEEE White Space Radio Opening Report
IEEE White Space Radio Status Report
IEEE White Space Radio Draft Development Procedure
TGu Timeline Date: Authors: July 2005 July 2005
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
IEEE “ Requirements” Date: Authors:
IEEE White Space Radio Intended timeline
Addressing White Spaces Across all of IEEE 802
TGy draft 2.0 with changebars from draft 1.0
IEEE White Space Radio Draft Development Process
TGv Redline D0.10 Insert and Deletion
IEEE White Space Radio Draft ToC
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
3GPP2 Liaison Report Date: Authors: May 2006 May 2006
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
IEEE White Space Radio Liaisons
IEEE WG: P Status Review
TGu-changes-from-d0-04-to-d0-05
IEEE White Space Radio Status Report
IEEE White Space Radio Opening Report
TGu-changes-from-d0-03-to-d0-04
TGu Timeline Date: Authors: January 2005 January 2005
TGu Motions Date: Authors: May 2006 May 2006
IEEE White Space Radio Status Report
TGu Timeline Date: Authors: May 2005 May 2005
IEEE White Space Radio Status Report
TGu Timeline Date: Authors: July 2005 July 2005
IEEE White Space Radio Closing Report
IEEE White Space Radio Status Report
Media Independent Coexistence
IEEE White Space Radio First Call for Contributions
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGu Motions Date: Authors: September 2006 September 2006
IEEE White Space Radio Status Report
TGu Timeline Date: Authors: July 2005 July 2005
Presentation transcript:

IEEE P1900.4 vs IEEE 802.21 Date: 2009-01-22 Authors: November 2005 doc.: IEEE 802.11-05/1051r0 IEEE P1900.4 vs IEEE 802.21 Date: 2009-01-22 Authors: Notice: This document has been prepared to assist IEEE P1900. 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. Release: 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 P1900. Patent Policy and Procedures: The contributor is familiar with the IEEE P1900 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <stephen.berger@ieee.org> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within IEEE P1900. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Slide 1 Mujtaba (Agere), Petranovich (Conexant), Fischer (Broadcom), Stephens (Intel) et. al.

Standards detailed overview For overview of P1900.4, see tutorial at: http://grouper.ieee.org/groups/scc41/4/IEEE -1900.4-Overview-2009-01-07.pdf For overview of 802.21, see tutorial at: http://www.ieee802.org/21/Tutorials/802%2 021-IEEE-Tutorial.ppt

P1900.4 scope Reconfiguration Initiation Reconfiguration decision Entities in charge of reconfiguration decisions are in scope. (Not algorithms: implementation dependent!) Reconfiguration Initiation Reconfiguration decision Reconfiguration Execution Scope of IEEE P1900.4 Reconfiguration NOT for Connection Transfer Context information collection Distributed policy based management - RAN capabilities RAN measurements Terminal capabilities Required QoS level - Reconfiguration commands for terminals and base stations Spectrum assignment Spectrum access - Handover IEEE P1900.4 specifies architecture and information model to enable policy-based management for optimized radio resource usage in heterogeneous wireless networks

IEEE 802.21 scope Handover Initiation Handover Decision Handover Preparation Handover Execution Scope of IEEE 802.21 NOT a Decision Algorithm Setup New Link and Initiate HO Execution NOT for Connection Transfer Search New Link - Network Discovery - Network Capabilities Discovery - Handover Decision Making - Layer 2 Connectivity - Generic Handover Commands - L2 and IP Handover Signaling (not MIP) - Context Transfer IEEE 802.21 is an enabler/toolbox for having seamless handovers IEEE 802.21 is an abstraction layer between access technologies & mobility management solution

1900.4 Context CWN – Composite Wireless Network OSM – Operator Spectrum Manager NRM – Network Reconfiguration Manager RAN – Radio Access Network TRM – Terminal Reconfiguration Manager F1, 2, 3, 2 – Frequency bands

1900.4 System Architecture (1)

1900.4 System Architecture (2) Network side entities Operator Spectrum Manager (OSM) is the entity that enables operator to control dynamic spectrum assignment decisions of NRM RAN Measurement Collector (RMC) is the entity that collects RAN context information and provides it to NRM Network Reconfiguration Manager (NRM) is the entity that manages CWN and terminals for network-terminal distributed optimization of radio resource usage and improvement of QoS RAN Reconfiguration Controller (RRC) is the entity that controls reconfiguration of RANs based on requests from NRM Terminal side entities Terminal Measurement Collector (TMC) is the entity that collects terminal context information and provides it to TRM Terminal Reconfiguration Manager (TRM) is the entity that manages the terminal for network-terminal distributed optimization of radio resource usage and improvement of QoS within the framework defined by the NRM and in a manner consistent with user preferences and available context information Terminal Reconfiguration Controller (TRC) is the entity that controls reconfiguration of terminal based on requests from TRM

(3) MIH Information Service IEEE 802.21: reference model One Media Independent Handover Function (MIHF) with 3 SAPs: MIH SAP (media independent) MIH Link SAP (media dependent) MIH Net SAP (for remote transport) MIHF provides three services MIH SAP Link Layer (e.g., 802.3, 802.11, 802.16, 3GPP) Link SAP MIH Users (Handover Policy, L3 or higher mobility protocol, etc.) MIH LINK SAP MIH NET SAP L3 transport L2 transport Remote MIHF Media Independent Handover Function (MIHF) (1) MIH Event Service (2) MIH Command Service (3) MIH Information Service

IEEE 1900.4 principles Decision making in this standard is based on policy-based management framework. 1900.4 specifies architecture and information model to enable policy- based management. 1900.4 enables to describe policies of type Event-Condition-Action Radio resource selection policies create the framework within which TRMs will make terminal reconfiguration decisions =>1900.4 may reuse handover initiation and handover preparation Services defined by 802.21.

P1900.4-802.21 differences 802.21 deals with handover of mobile terminal. Can be network initiated or mobile initiated. P1900.4 scope is broader: reconfiguration of terminals but also of base stations P1900.4 defined a policy-based management and describes policies of type Event-Condition-Action

P1900.4-802.21 complementarities P1900.4 can use a subset of 802.21 (by defining a specific 1900.4 profile) P1900.4 NRM and TRM can be seen as 802.21 MIH users P1900.4 can reuse the service concepts of 802.21 but needs the extended information model specified in 1900.4.

Conclusion 802.21 for handover initiation, decision making and target network preparation 1900.4 defines policy-based framework for reconfiguration decisions The policies defined in 1900.4 framework may be policies that trigger Handover decisions. Complementary standards