802.19.1 Concept of Operation Date: 2010-07-12 Authors: July 2010 May 2010 doc.: IEEE 802.11-yy/xxxxr0 July 2010 802.19.1 Concept of Operation Date: 2010-07-12 Authors: Notice: This document has been prepared to assist IEEE 802.19. 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. Alex Reznik, et. al. (InterDigital) Tuncer Baykas, NICT

Abstract Present our view of how 802.19.1 devices and networks operate July 2010 Abstract Present our view of how 802.19.1 devices and networks operate Outline some main operational concepts Highlight some challenges Open up the topic for further discussion Alex Reznik, et. al. (InterDigital)

Basic Functions What does an 802.19.1 capable network/device do? July 2010 Basic Functions What does an 802.19.1 capable network/device do? Join an 802.19.1 System which consists of other 802.19.1 capable network devices that have decided to cooperate for coexistence Discovery Procedures Access and Admission Procedures Tell others what one can do Negotiate coexistence policies Not all networks devices can – or are willing – to do all things Operate in the system Request “coexistence help” Receive and execute coexistence requests Leave the system Say, bye-bye Alex Reznik, et. al. (InterDigital)

How an 802.19.1 System is Used July 2010 An 802.19.1 System provides an Coexistence Service Set (CSS) Not everyone has to subscribe to any given CSS Not everyone is allowed to subscribe (although most everyone will likely be invited) OSS include several optional services There are always entities around who are not subscribed to any of these services To Subscribe to the CSS you need to Include 802.19.1 CE in the design of the device or network Enable the 802.19.1 CE and connect to the 802.19.1 system Provide info about your 802.19.1 TVBD device(s). Select from the menu of services offered If you subscribe to a command service, you have to follow the command You have the freedom of choice in subscribing to services Presumably this will determines how you are treated – i.e. presumably the more flexible you are willing to be, the more others will work with you Once you’ve made a service commitment – you have to remain honest OSS Service rules may change The set of policies that are being employed may depend on what networks/devices are active Thus, entry/exit of networks/devices affects the policy set Networks/devices can be nomadic Moving from club-to-club must be fairly easy However, may not need continual connectivity (i.e. handover may not be needed) Alex Reznik, et. al. (InterDigital)

Basic Operational Constructs July 2010 Basic Operational Constructs An 802.19.1 System Deals with 4 Basic Types of Entities Coexistence information (simply Information when its not confusing) Mechanisms Algorithms Policies Information Information available to 802.19 system to make coexistence decisions May be provided by databases (CDIS, Regulatory, Operator) or measurements by networks and devices which comprise the system Control points (knobs) which available in the underlying MAC/PHY for enabling coexistence. Some examples Channel assignment Time-slot / sub-carrier scheduling 802.19.1 standard-defined procedures for exercising available mechanisms to facilitate coexistence. Which algorithms are used as well as what parameters they use depends on policies and available information Rules specific to each 802.19.1 system which define how algorithms are to be used to facilitate coexistence Policies are NOT defined by the standard Policy exchange protocol over the internal interfaces (CM-to-CM and CM-to-CDIS) is defined by the standard Acceptable policy languages should be listed, however do not necessarily need to be defined (i.e. defined by reference to existing work) Alex Reznik, et. al. (InterDigital)

What Might This Look Like: An Example July 2010 What Might This Look Like: An Example Mechanisms Information Algorithms Policies From M. Sherman, “Policy Engine Architecture and Certification,” IEEE SCC41 Document 2010-037 Alex Reznik, et. al. (InterDigital)

High-Level Example of Operation: System Entry and Policy Exchange July 2010 High-Level Example of Operation: System Entry and Policy Exchange Necessary Procedures Discovery Access Control Policy Negotiation Policy Enforcement Normal Operations May also include policy updates and changes Includes all other coexistence mechanisms Alex Reznik, et. al. (InterDigital)

July 2010 High-Level Example of Operation: Policy Exchange under Normal Operation Note on Policy Commitment As we noted, each network/device free to choose which policies is can/willing to follow But once it declares, it must commit to following them A de-commitment also has to be declared Alex Reznik, et. al. (InterDigital)

Conclusions Presented some initial thoughts on concept of operation July 2010 Conclusions Presented some initial thoughts on concept of operation Need further discussion Does the rest of the group agree with this concept How much of this needs to be captured in normative text How does this translate into requirements on different architectural components Alex Reznik, et. al. (InterDigital)