22-10-0051-00-0000-proposed-resolutions-to-comments-related-to-sections-9-6-and-9-7

IEEE P802.22 Wireless RANs

Proposed Resolutions to Comments Related to Sections 9.6 and 9.7 Date: 2010-03-16 Author(s): Name Ranga Reddy Apurva Mody Company US Army - CERDEC BAE Systems Address Ft. Monmouth, NJ P.O. Box 868, MER 15-2350, Nashua, NH 03061-0868 Phone 404-819-0314 email Ranga.reddy@us.army.mil apurva.mody@baesystems.com, apurva_mody@yahoo.com Abstract This document provides the proposed resolutions to the comments related to Section 9.6 and Section 9.7. These comments are 1130, 1167, 1168, 1169, 1170, 1178, 1179, 1180, 1181, 1182, 1185 and 1191. Notice: This document has been prepared to assist IEEE 802.22. 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.22. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures , 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 Working Group 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 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.22 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at . Submission

page 1 Apurva Mody, BAE Systems

March 2010 doc.: IEEE 802.22-10/0051r0000

1.0 Proposed Resolutions to Comments Related to Sections 9.6 and 9.7

Comment 1167 – Tom Kiernan - Database Service section is currently empty.

Proposed Resolution – Counter - Editor to include Sections A, C, D and E from Document 22-09-0123 Rev 15 into Section 9.6

Comments 1169, 1178, 1179 – Superceded by the proposed resolution to Comment 1167

Comment 1168, – Tom Kiernan - Although primitives in this Section are specific to the Cognitive Radio Capabilities, they really deserve to be in their own new section which is combined with the MIB and Management Plane Procedures

Proposed Resolution – Counter – The 802.22 ad-hoc group developed the Database Service Interface Document – 22-09-0123 Rev 15

In developing the database related document, these messages changed significantly. Cognitive radio capability ad-hoc recommends that the Contents of Section 9.7.1 be entirely replaced with the contents of Section B in Document 22-09-0123 Rev 15.

Comments 1170, 1180, 1182 – Superceded by the proposed resolution for Comment 1168

Comment 1185 – Steve Shellhammer – Sub-clause 9.7.4 and 9.4 are somewhat redundant. As a results there are tables in 9.7.4 that repeat some tables from 9.4. This will lead to lots of errors.

Proposed Resolution – Reject - Section 9.4 defines the Spectrum Sensing Function related terminology, and Section 9.7.4 defines the SSF interfaces, messaging and provides a SAP definition. Ultimately, contents of Section 9.7.4 will be included into a new Section on Managemen Plane Procedures and so it is necessary to keep. So, both these sections are necessary at this time.

Comment 1191 – Charles Einolf – Table 293 Valid Range Values are Missing.

Proposed Resolution - COUNTER – Modifications to the Tables 291, 292 and 293 are provided. Modifications to these tables resulted in a need to make appropriate modifications in Tables 257 and Tables 260 also. Those are also specified in this document.

All the proposed changes are highlighted in Red.

1. Editor – Please note proposed chjanges to Table 291

Table 291 — SM-SSF-SAP-CHANNEL-SENSING.request parameters

Name IETF Country Code Channel Number Type ASCII Integer Length (Bits) Value / Description 16 bits See Annex A 8 bits The channel number which is to be Submission

page 2 Apurva Mody, BAE Systems

March 2010 doc.: IEEE 802.22-10/0051r0000

Channel Bandwidth Sensing Mode Signal Type Array Sensing Window Specification Array Integer Integer Array Array Maximum Probability Array of False Alarm Array sensed by the SSF. Range as specified in Table 257. 4 bits The bandwidth of the channel to be sensed by the SSF. Values as specified in Table 257. 2 bits The sensing mode specifies which SSF outputs are valid as specified in Table 260. 32 bits An array indicating which signal types the SSF is to sense for as specified in Table 258. N X 32 N is the number of signal types enumerated (that are equal to ‘1’) in the Signal Type Array. Sensing window specifications as specified in Tables 257 and 260. Each element in the Sensing Window Specification consists of: NumSensingPeriods SensingPeriodDuration SensingPeriodInterval N X 8 N is the number of signal types enumerated (that are equal to ‘1’) in the Signal Type Array. This value is valid only for sensing modes 0 and 1. Each element specifies the maximum probability of false alarm for the corresponding signal type decision in the sensing present Array. Range of PFA as specified in Table 257.

Corresponding Changes that are Needed in Table 257, 259 and Table 260

2. Editor, please implement Comment 1130 – Table 257 – Proposed Resolution Expand STA to 32 bits.

3. Editor NumSensingPeriods needs to be changed in Tables 257 and 260 to 8 bits – 0-127 to align it with BLM-REQ. Values from 128 to 255 are reserved.

4. Editor, Table 259 – Num Sensing Periods – 8 bits – 0 to 127 to align it with the BLM-REQ message. Values from 128 to 255 are reserved.

5. Sensing Period Interval size needs to be changed in Tables 257 and 260 from current 8 bits to 16 bits,

This makes the total size of the Sensing Window Specification Array to 32 bits.

6. Editor - Also add Sensing Mode Size – 2 bits in Table 257

Submission

page 3 Apurva Mody, BAE Systems

March 2010 doc.: IEEE 802.22-10/0051r0000

7. Editor - Also add Maximum Probability of False Alarm – 8 bits in Table 257. Range goes from 0.001 – 0.255

8. Editor, please note changes to the Table 292

Table 292 — SM-SSF-SAP-CHANNEL-SENSING.confirm parameters

Name IETF Country Code Channel Number Sensing Mode Status Type ASCII Integer Length (Bits) 16 bits 8 bits Value / Description See Annex A The channel number which is to be sensed by the SSF. Range as specified in Table 257. The sensing mode specifies which SSF outputs are valid as specified in Table 260. 00 - INVALID_REQUEST, 01 - INVALID_SIGNAL_TYPES 10 - RESERVED 11 - SUCCESS, The value indicates whether the sensing request was successfully generated. An array indicating which signal types the SSF will not be able to sense for as specified in Table 258. This attribute is valid only if the Status = INVALID_SIGNAL_TYPEs Integer Enumeration 2 bits 2 bits Invalid Signal Type Array Array 32 bits

9. Editor – Please note changes to Table 293

Table 293 — SM-SSF-SAP-SENSING-RESULTS.indication parameters

Name IETF Country Code Channel Number Sensing Mode Signal Type Array Type ASCII Integer Integer Array Length (Bits) 16 bits 8 bits 2 bits 32 bits Value / Description See Annex A The channel number which is to be sensed by the SSF. Range as specified in Table 257. The sensing mode specifies which SSF outputs are valid as specified in Table 260. An array indicating which signal types the SSF is to sense for as specified in Table Submission

page 4 Apurva Mody, BAE Systems

March 2010

Signal Present Array doc.: IEEE 802.22-10/0051r0000

Confidence Array RSSI Measurements RSSI Standard Deviation 258. Array N X 2 Each element in the Array is a signal present decision. Each decision can take on three possible values, as given in Table 261. Array 8 bits Confidence Array is only valid for Sensing Mode 2 Each element in the confidence Array is a confidence metric for the sensing result for the corresponding signal type as defined in Table 261. The Confidence Array is only valid for Sensing Mode 1. 0x00 – No confidence 0x01 – 0xFE - Reserved 0xFF – Full confidence Array RSSI Measurement is only valid for Sensing NumSensingPeriods Mode 3 X 32 BS can ask the CPE for up to 127 last measurements of the RSSI estimate in the sensing chain, where each measurement is a floating point number (32 bits) which represents the RSSI in dBm. Length of the array is equal to the NumSensingPeriods, where each measurement is taken in a sensing period. Floating 32 RSSI Standard Deviation is only valid for Point Sensing Mode 3. It is a floating point number that represents the RSSI standard deviation over NumSenisngPeriods measurements.

Submission

page 5 Apurva Mody, BAE Systems