1. Abstract: Relationship between 802.19.1 and 802.21
IEEE MEDIA INDEPENDENT HANDOVER
DCN: hwnm
Title: Thoughts on IEEE relation with IEEE
Date Submitted: May 13, 2010
Presented to Heterogeneous Wireless Networks Mgmt. SG at IEEE session #38 in Bangalore
Authors or Source(s):
Antonio de la Oliva (UC3M) Johannes Lessmann (NEC) Christian Niephaus (FhG)
Abstract: Relationship between and

2. IEEE 802.21 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

3. IEEE 802.19.1 Architecture Coexistence Enabler Coexistence Manager
Request and obtain information, required for coexistence, from TVBD network or device
Translate reconfiguration requests/commands to TVBD-specific
Coexistence Manager
Discovery of other CMs
Decision Making
Support exchange of information ..
Coexistence Discovery and Information Server
Support Discovery of CMs
Collect, aggregate information
CHECK NEXT SLIDE FOR MAPPING TO .21 ARCHITECTURE

4. IEEE 802.19.1 Architecture mapping to IEEE 802.21
Interface C and D=MIH_SAP+MIH_NET_SAP
Interface B3=MIH_SAP+MIH_NET_SAP
MIH Users
TVWS Database
Coexistence Manager
Coexistence Discovery and Information Server
Another Coexistence Manager
Operator Management Entity
Other TVBD device or network
(supporting the MIHF)
Interface B1=MIH_SAP
MIH_SAP
MIIS
MIHF (Extended)
Coexistence Enabler
MIH_NET_SAP
MIH_NET_SAP
Interface A=MIH_LINK_SAP
MIH_LINK_SAP
TVBD Network or Device

5. Set of System Requirements
Requirements in red are not in scope of .21 (IMHO), requirements in green are in scope while in blue I am in doubts.
R1: system shall enable discovery for compliant TVBD networks and devices
R2: system shall be able to obtain and update information required for TVWS coexistence
R3: system shall have means to exchange obtained information
R4: system shall be able to provide reconfiguration requests and/or commands as well as corresponding control information to compliant TVBD networks and devices to implement TVWS coexistence decisions
R5: system shall analyze obtained information
R6: system shall be capable of making TVWS coexistence decisions
R7: system shall support different topologies of decision making for TVWS coexistence (e.g. centralized, distributed and autonomous)
R8: system shall support appropriate security mechanisms. This shall include user/device authentication, integrity and confidentiality of open exchanges, and data privacy and policy correctness attestation and enforcement
R9: system shall utilize a set of mechanisms to achieve coexistence of TVBD networks and devices

6. R2: 802.19.1 system shall be able to obtain and update information required for TVWS coexistence
At least two sources of information:
TVWS database
Other TVBD network/devices
.21 MIIS can be used as foundation
Same concept, information in a geographical area
Transport protocol already defined
There are already some IEs with frequency information
Required changes
Push information into the MIIS
Information taken from other TVBDs? Events, local MIIS, MIIS proxy mode?
IEs for MIIS, specifically for TVWS and potentially some extra IEs for policies etc..

7. R3: 802.19.1 system shall have means to exchange obtained information
.21 already has remote communication mechanisms, over L2 and L3
MIH protocol can be used
RFC5677
No required change

8. Commands for radio configuration Changes
R4: system shall be able to provide reconfiguration requests and/or commands as well as corresponding control information to compliant TVBD networks and devices to implement TVWS coexistence decisions
Commands for radio configuration
Remote and local
Changes
Introduce Interface notion in the standard
Introduce commands for radio configuration
Nothing fancy, just freq and power at beginning
Make sure the .21 architecture/ref model allows the required communication paths

9. Blue Ones
R1: system shall enable discovery for compliant TVBD networks and devices:
Discovery of Coexistence Services using .21: Extensions to RFC 5678 (DHCP Options for .21) and RFC 5679 (Locating .21 services through DNS)
Discovery of other compliant devices: Thing to explore, maybe a Media Independent Beaconing system
R7: system shall support different topologies of decision making for TVWS coexistence (e.g. centralized, distributed and autonomous)
A .21 based approach is compatible with this requirement since we do not force any specific topology
R8: system shall support appropriate security mechanisms. This shall include:
user/device authentication: IMHO a covers this
integrity and confidentiality of open exchanges: IMHO a covers this
data privacy: IMHO a covers this
policy correctness attestation and enforcement: Not covered in IEEE

10. Strawpoll
Do people in the SG “HWNM” believe that offers a good framework for the requirements?
Yes: 9
No: 0
Abstain: 0