1. IEEE P1900.4 vs IEEE 802.21 Date: 2009-01-22 Authors:
November 2005
doc.: IEEE /1051r0
IEEE P vs IEEE
Date:
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 < 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 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
Slide 1
Mujtaba (Agere), Petranovich (Conexant), Fischer (Broadcom), Stephens (Intel) et. al.

2. Standards detailed overview
For overview of P1900.4, see tutorial at:
Overview pdf
For overview of , see tutorial at:
021-IEEE-Tutorial.ppt

3. 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 P specifies architecture and information model
to enable policy-based management
for optimized radio resource usage
in heterogeneous wireless networks

4. IEEE 802.21 scope Handover Initiation Handover Decision
Handover Preparation
Handover Execution
Scope of IEEE
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 is an enabler/toolbox for having seamless handovers
IEEE is an abstraction layer
between access technologies & mobility management solution

5. 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

6. 1900.4 System Architecture (1)

7. 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

8. (3) MIH Information Service
IEEE : 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.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

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

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

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

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