14
November 2005 Stephen Berger, TEM Consulting Slide 1 doc.: IEEE 802.19-05/0048r0 Submission November 2005 Liaison Report from P1900.2 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. 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 802.19. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < http:// 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 TAG 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 <[email protected]> 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 the IEEE 802.19 TAG. If you have questions, Date: 2005-11-14 N am e C om pany A ddress Phone em ail Stephen Berger TEM C onsulting 140 RiverRd. G eorgetow n, TX 78628 512-864-3365 stephen.berger@ ieee.org Authors:

Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

Embed Size (px)

Citation preview

Page 1: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 1

doc.: IEEE 802.19-05/0048r0

Submission

November 2005 Liaison Report from P1900.2

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.

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

Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// 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 TAG 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 <[email protected]> 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 the IEEE 802.19 TAG. If you have questions, contact the IEEE Patent Committee Administrator at <[email protected]>.

Date: 2005-11-14

Name Company Address Phone email Stephen Berger TEM Consulting 140 River Rd.

Georgetown, TX 78628

512-864-3365 [email protected]

Authors:

Page 2: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 2

doc.: IEEE 802.19-05/0048r0

Submission

IEEE P1900.2 Recommended Practice for

Interference and Coexistence Analysis

Page 3: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 3

doc.: IEEE 802.19-05/0048r0

Submission

Document Structure

Roadmap for 1900 Effort

Future Meetings

Overview

Page 4: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 4

doc.: IEEE 802.19-05/0048r0

Submission

Title & Sponsor

Title of Document to be Developed: Recommended Practice for Interference and Coexistence Analysis

Sponsorship: IEEE Electromagnetic Compatibility Society (EMC-S)and IEEE Communications Society (ComSoc);

EMC-S has the lead on this project.

Page 5: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 5

doc.: IEEE 802.19-05/0048r0

Submission

Scope & Purpose

Project Scope: This standard will provide technical guidelines for analyzing the potential for coexistence or in contrast interference between radio systems operating in the same frequency band or between different frequency bands.

Purpose of the Project: New concepts and technologies are rapidly emerging in the fields of spectrum management, policy defined radio, adaptive radio and software defined radio. A primary goal of these initiatives is to improve spectral efficiency. This standard will provide guidance for the analysis of coexistence and interference between various radio services.

Page 6: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 6

doc.: IEEE 802.19-05/0048r0

Submission

Context

PurposeUsage ModelContext/Comparison

Variables

Contrasting & Relevant VariablesFrequency & System RelationshipsReduce matrix of possible interference to a sparse matrix of controlling & bounding cases for analysisAnalyze Effects with Probability

Overview

Page 7: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 7

doc.: IEEE 802.19-05/0048r0

Submission

Benefits of Proposal

Full matrix of scenarios and conditions

Reduced sparse matrix for analysis

Summation

Overview

Page 8: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 8

doc.: IEEE 802.19-05/0048r0

Submission

Regulatory Agency

Technical Requirements

Regulatory Agency

Technical RequirementsCandidate System

Accredited

Test Laboratory

Accredited

Test Laboratory ExaminerExaminer

Certified System System

Description

System

DescriptionNIST

Software Ref. Lib.

NIST

Software Ref. Lib.

Vendor

Quality & ConfigurationControl Processes

Vendor

Quality & ConfigurationControl Processes

Field Deploymentand Use

Field Deploymentand Use

Receiving InspectionReceiving Inspection

System ManagerSystem Manager Field Surveillance

Performance Monitoring

Network Management

Field Surveillance

Performance Monitoring

Network Management

DASM System

System Modification

Page 9: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 9

doc.: IEEE 802.19-05/0048r0

Submission

Current IEEE 1900.x Projects• IEEE P1900.1

Standard Dictionary of Terms, Definitions and Concepts for Spectrum Management, Policy Defined Radio, Cognitive Radio and Software Defined Radio

Chair: Jim Hoffmeyer, Western Telecom Consultants

• IEEE P1900.2Recommended Practice for Interference and Coexistence Analysis

Chair: Stephen Berger, TEM Consulting

• IEEE P1900.3Recommended Practice for Conformance Evaluation of Software Defined Radio (SDR) Software Modules using Formal Concepts and Methods Analysis

Chair: Andre Kruetzfeldt, Sun Microsystems

Page 10: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 10

doc.: IEEE 802.19-05/0048r0

Submission

DASM Qualification Regiment – An evaluation process by which compliant implementations may be separated from non-compliant implementations. An abstracted and refined regiment producing the same information as field trials and proof-of-concept testing.

DASM Conformity Assessment System – Beyond the initial design verification, type acceptance qualification regiment there is a need to provide a full conformity assessment system to assure that fielded systems operated within specified bounds.

Policy definition - What are the restrictions in freq, power, bandwidth, time, etc for communication; how do we express them

Electronic Data Interchange (EDI) of Policy sets – Standard format for policy loads.

DASM Etiquette – An etiquette that allows cognitive radios to communicate between themselves, agree on operating modes, and exchange sensing information.

Possible Future Projects

Page 11: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 11

doc.: IEEE 802.19-05/0048r0

Submission

A generic radio interface – A standard that allows radio software to discover the hardware radio transmission, reception, and sensing capabilities and to control these capabilities. This allows SDR software to port across platforms more easily, and hardware to leverage new software developments.

Channel usage database – A standard that stores known transmitter information in a useful format for cognitive radios. It would define secure mechanisms for querying or broadcasting this information; and secure and distributed methods for the db to be updated by transmitter owners.

A beacon radio standard – A standard for disseminating channel usage info in an area; a transmitter beacon that is an easy to detect signal so cognitive radios could discover transmitters more easily; and a receiver beacon standard so dumb receivers (e.g. a TV) could have a simple beacon to warn off potential secondary users.

Possible Future Projects

Page 12: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 12

doc.: IEEE 802.19-05/0048r0

Submission

Definition of field management techniques – These standards would define field management techniques to manage and coordinate DASM systems. An example might be a standard query that a system receiving interference could issue to receive the identity, including software load and version level, of devices operating in the area..

Guide for ISO 17025 for DASM evaluation laboratories – A guide on the qualification of laboratories intending to test DASM systems.

Infrastructure Support – Coordination is needed to other bodies so that the environment is prepared for the introduction of DASM systems:

Update of ANSI C63.19 so that hearing aids are adequately tested for immunity to DASM transmissions and DASM systems can be tested for HAC.

Update of ANSI C63.9 so that office equipment can be adequately tested for RF immunity to DASM transmissions.

Update of AAMI PC69 so that implanted medical devices can be adequately tested for RF immunity to DASM transmissions.

Possible Future Projects

Page 13: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 13

doc.: IEEE 802.19-05/0048r0

Submission

Management Data Reporting & Facilities – This document would specify the data to be reported from lower layers and the controls to be made available in the device to allow various network management techniques.

Others?? – Other standards required to develop, qualify and support DASM systems.

Possible Future Projects

Page 14: Doc.: IEEE 802.19-05/0048r0 Submission November 2005 Stephen Berger, TEM ConsultingSlide 1 November 2005 Liaison Report from P1900.2 Notice: This document

November 2005

Stephen Berger, TEM ConsultingSlide 14

doc.: IEEE 802.19-05/0048r0

Submission

Future Meetings• January 24-26 – Boulder, CO

University of Colorado

• March 7-10 – Boulder, CO ISART Conference