1 / 9

802.19.1 Concept of Operation

802.19.1 Concept of Operation. Authors:. Date: 2010-07-12.

donnyt
Télécharger la présentation

802.19.1 Concept of Operation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 802.19.1 Concept of Operation Authors: Date: 2010-07-12 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)

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

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

  4. How an 802.19.1 System is Used • An 802.19.1 System provides an Optional Service Set (OSS) • Not everyone has to subscribe to any given OSS • 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 OSS 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, we do not need to maintain connection continuity – no handover Alex Reznik, et. al. (InterDigital)

  5. 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 • Mechanisms • Control points (knobs) which available in the underlying MAC/PHY for enabling coexistence. Some examples • Channel assignment • Time-slot / sub-carrier scheduling • Algorithms • 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 • Policies • 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 (B2 and B3) 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)

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

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

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

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

More Related