Requirements Date: Authors: March 2010 Month Year

Slides:



Advertisements
Similar presentations
Submission doc.: IEEE /0032r0 April 2015 Sho Furuichi, SonySlide 1 The new coexistence use cases for IEEE Date: Authors: Notice:
Advertisements

Doc.: IEEE /0104r0 Submission July 2010 Alex Reznik, et. al. (InterDigital)Slide 1 Channel Selection Support in TVWS Date: Authors:
Doc.: IEEE /0287r0 Submission March 2011 Slide 1Hyunduk Kang, et al, ETRI Overview and Issues Notice: This document has been prepared.
Doc.: IEEE /0074r2 Submission May 2010 Tuncer Baykas, NICTSlide TG1 Introduction and Status Notice: This document has been prepared to.
Submission doc.: IEEE /0097r0 November 2015 Sho Furuichi, SonySlide 1 Information exchange between independent IEEE systems Date: xx.
Submission doc.: IEEE /0011r2 January 2016 Sho Furuichi, SonySlide 1 System architecture for information exchange between independent IEEE
Doc.: IEEE /41r0 SubmissionSlide 1 P System Architecture Notice: This document has been prepared to assist IEEE It is offered.
Doc.: IEEE /20rev0 SubmissionSlide 1 P Assumptions and Architecture Notice: This document has been prepared to assist IEEE It.
Submission doc.: IEEE /0015r0 January 2016 Sho Furuichi, SonySlide 1 Proposal for CM discovery/selection/ association as CE operation Date:
Doc.: IEEE /0098r0 Submission July 2010 Alex Reznik, et. al. (InterDigital)Slide Security Procedures Notice: This document has been.
Doc.: IEEE /0019r0 Submission February 2010 Mika Kasslin, NokiaSlide 1 High Level Architecture View Notice: This document has been prepared to.
Doc.: IEEE /0013r0 Submission January 2010 Mika Kasslin, NokiaSlide 1 Coexistence architecture of Notice: This document has been prepared.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IEEE as a Media Independence Service Layer Date Submitted: July 13, 2010.
Doc.: IEEE /0085r1 Submission June 2010 Tuncer Baykas, NICTSlide TG1 and System Design Document Notice: This document has been prepared.
IEEE MEDIA INDEPENDENT HANDOVER DCN: hwnm Title: Thoughts on IEEE relation with IEEE Date Submitted: May 13, 2010.
Doc.: IEEE /0162r0 Submission November 2010 Jihyun Lee, LG ElectronicsSlide 1 TVWS Coexistence Procedures and Protocols Notice: This document.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Load balancing in heterogeneous network use case Date Submitted:
Requirements and Amendments Regarding TVWS Database Access
November 2005 doc.: IEEE /1051r0 09/06/2018
Teleconference Agenda
TG1 Introduction and Status
July 2009 doc.: IEEE /xxxxr0 July 2009
Proposal on system description, reference model and draft outline
On the Objectives and Scope of the WS Coexistence PAR
TG1 Tutorial Review Date: Authors: May 2010 May 2010
Reference Model Proposal
Channel Classification for Logical Entities
P System Architecture Date: Authors: March 2010
<May,2009> doc.: IEEE <doc .....> <July 2009>
Channel Classification for Logical Entities
Resource allocation principles for coexistence system
Submission Title: [802.11n Liaison Report May 2009]
July Tutorial – Possible Solutions
FCC Regulations and Multi-band Operation
Possible Effects of FCC rules to design
Design Principles for Entity Responsibilities
TG1 Introduction and Status
FCC rules and design Date: Authors: October 2010
January 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Technical Requirement sub-group report]
Coexistence of CMs with different decision making algorithms
Enabling Procedure of Communication in TVWS under FCC rules
Abstract: Relationship between and
P System Architecture Date: Authors: March 2010
Radio Resource Measurement for TVWS application under FCC rules
TG1 Tutorial Review Date: Authors: May 2010 May 2010
Neighbors and Neighbor Discovery
Coexistence Media Service Access Point (COEX_MEDIA_SAP)
Updates to the Draft Authors:
Updates to the Draft Authors:
Concept of Operation Date: Authors: July 2010
TG1 and System Design Document
Examples of deployment scenarios
July Tutorial – Possible Solutions
Logical Entities Date: Authors: September 2010
Data types definition directions
Neighbor Setting Procedures
March Liaison Report Date: Authors: March 2010
Possible Action Items Date: Author:
Possible Action Items Date: Author:
P System Architecture Date: Authors: March 2010
Coexistence Decision Making Topologies
P System Architecture Date: Authors: March 2010
List of Remaining Proposals for Downselection
doc.: IEEE <doc#>
Comments to IEEE /68 Date: Authors: September 2009
Enabling Procedure of Communication in TVWS under FCC rules
Month Year doc.: IEEE yy/xxxxr0 August 2019
Month Year doc.: IEEE yy/xxxxr0 January 2016
TG1 September Closing Report
Presentation transcript:

802.19.1 Requirements Date: 2010-03-15 Authors: March 2010 Month Year doc.: IEEE 802.11-yy/xxxxr0 March 2010 802.19.1 Requirements Date: 2010-03-15 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. S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 March 2010 Abstract This contribution summarizes 802.19.1 requirements as output of Requirements ad hoc at the end of PM2 slot on March 15. S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al John Doe, Some Company

Month Year doc.: IEEE 802.11-yy/xxxxr0 March 2010 Introductory notes Slides 3 – 8 are providing introductory notes that assist in understanding of system requirements They are not part of 802.19.1 system requirements Introductory notes include Guidelines to create system requirements Explanation of terms Overview of system requirements S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al John Doe, Some Company

Guidelines to Create System Requirements March 2010 Guidelines to Create System Requirements SDD Components: System Architecture Outline Terminology System Requirements Assumptions Requirements Guidelines Agreed in January Meeting: Provide wording for system requirements for the coexistence system as a single entity. Provide general functional requirements, which should be categorized according to the following categories: Discovery Communications Etiquette Algorithms General Should the paragraph above be used as guidelines for functional requirements section of the SDD? No objections S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

Explanation of Terms 802.19.1 system March 2010 Explanation of Terms 802.19.1 system For the purpose of this contribution we understand the term “802.19.1 system” as follows: 802.19.1 system is a system that provides or enhances the coexistence of dissimilar or independently operated TVWS networks and devices. 802.19.1 system is a set of entities and interfaces defined in 802.19.1 standard This means that 802.19.1 system is distinguished from TVBD network or device Some entities and interfaces of the 802.19.1 system can be implemented inside TVBD network or device, while some entities and interfaces of the 802.19.1 system can be implemented outside TVBD network or device S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

Explanation of Terms 802.19.1 system March 2010 S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

Explanation of Terms 802.19.1 compliant TVBD network or device March 2010 Explanation of Terms 802.19.1 compliant TVBD network or device For the purpose of this contribution we understand the term “802.19.1 compliant TVBD network or device” as follows: 802.19.1 compliant TVBD network or device is network or device that contains the mandatory elements which 802.19.1 draft standard defines for TVBD network or device This term is used to distinguish from non-compliant TVBD network or device which does not contain mandatory elements of 802.19.1 draft standard and thus cannot use 802.19.1 coexistence methods Mandatory parts of 802.19.1 draft standard should be clarified at a later stage during draft development S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

Overview of system requirements March 2010 Overview of system requirements S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 1 802.19.1 system shall enable discovery for 802.19.1 compliant TVBD networks and devices Discovery Explanatory notes 802.19.1 system is required to identify potential 802.19.1 compliant TVBD networks or devices that need to coexist as one crucial step in order to achieve coexistence The term discovery should be understood as determining the presence of 802.19.1 compliant TVBD network or device and identifying its attribute such as ID S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 2 802.19.1 system shall be able to obtain information required for TVWS coexistence Communication Explanatory notes 802.19.1 system obtains this information from outside world, for example, from TVWS database, from 802.19.1 compliant TVBD networks/devices and etc S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 3 802.19.1 system shall have means to exchange obtained information Communication Explanatory notes Without constraining the mechanism of communication, this requirement puts a high level requirement to provide a means of exchanging information necessary for TVWS coexistence S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 4 802.19.1 system shall be able to provide reconfiguration requests and/or commands and corresponding control information to 802.19.1 compliant TVBD networks and devices to implement TVWS coexistence decisions Communication Explanatory notes Examples of reconfiguration commands are: to change center frequency, to adjust transmit power, possibly affect time scheduling, etc Reconfiguration requests and/or commands and corresponding control information are provided from 802.19.1 system to TVBD networks or devices, for example From a part of 802.19.1 system deployed in TVBD device to device management system via a SAP internal for the TVBD device From a part of 802.19.1 system deployed in TVBD network (e.g. in network management system) to radio nodes of the TVBD network, e.g., base stations, access points, etc S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 5 802.19.1 system shall be able to update information required for TVWS coexistence Communication Explanatory notes This requirement highlights the capability to update/refresh coexistence related information, such as location information of TVBD networks and devices, spectrum utilization by TVBD networks and devices S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 6 802.19.1 system should be able to analyze obtained information Algorithm Explanatory notes An example of analysis is the processing of raw data to generate a set of new data for assisting decision making S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 7 802.19.1 system shall enable TVWS coexistence decision making Algorithm Explanatory notes As an example of decision making, deciding on which actions should be taken by TVBD networks/devices to solve coexistence problem S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 8 802.19.1 system shall be able to support different topologies of decision making for TVWS coexistence (e.g. centralized, distributed and autonomous) Algorithm Explanatory notes This requirement underlines the possibility of having various approaches to implement decision making in coexistence scenarios It also underlines P802.19.1 system must be capable to support these different approaches of decision making for coexistence S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 9 802.19.1 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. General Explanatory notes 802.19.1 system shall be able to authenticate, provide integrity and/or confidentiality to all entities involved in 802.19.1 data exchange 802.19.1 system shall support privacy of sensitive data, and secure means to store and process such data while it resides in 802.19.1 entities Sensitive data may be geolocation, user and device credentials, and time alignment 802.19.1 system shall enable enforcement of coexistence policies for the 802.19.1 compliant TVWS networks or devices This includes secure means to detect and/or to remediate compromised behavior S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al

March 2010 Requirement 10 802.19.1 system shall utilize a set of mechanisms to achieve coexistence of TVBD networks and devices S. Filin (NICT), P. Ruuska (Nokia Research Center), A. Reznik (InterDigital), I. Reede (AmeriSys) et al