1. IEEE P802.22 Wireless RANs Date: 2007-03-07
Month Year
doc.: IEEE yy/xxxxr0
March 2007
Comment 126 Resolution
IEEE P Wireless RANs Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
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
Carl R. Stevenson 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
>
Liwen Chu STMicroelectronics
John Doe, Some Company

2. March 2007
Background
CID #126 refers to sub-clause , page 164 of r0_v0.2_with_line_numbers, entitled “Channel Management”. This sub-clause is “green” in priority.
Two distinct modes of Channel Management are described:
Embedded: where the Channel Management information elements are carried in Downstream Channel Descriptor (DCD) packets. (See ).
Explicit: where the Channel Management information is carried in the downlink subframe. (See )
Liwen Chu STMicroelectronics

3. Explicit Channel Management Modes in 802.22 version 0.2
Month Year
doc.: IEEE yy/xxxxr0
March 2007
Explicit Channel Management Modes in version 0.2
Explicit mode is able to transmit unicast, multicast, and broadcast channel management packets.
In this way, it is flexible for the BS to schedule.
Explicit mode is robust.
Each request message has an associated response message.
Explicit mode allows the BS to send out channel management packets only when needed.
It is bandwidth efficient, because its overhead is not periodic.
For these reasons: Explicit mode is desirable.
Liwen Chu STMicroelectronics
John Doe, Some Company

4. Embedded Channel Management Modes in 802.22 version 0.2
Month Year
doc.: IEEE yy/xxxxr0
March 2007
Embedded Channel Management Modes in version 0.2
DCD broadcast messages (6.8.1 – Table 25) are used to carry the DCD “Channel IEs” ( – Table 26).
It is not clear in Table 25 whether all the Channel IEs or part of the channel IEs in Table 26 are or are not carried in each DCD message
the implementations have to include all the IEs.
If the “Channel Action related IEs” must be carried in each DCD message then the fixed overhead of Embedded channel management is undesirable (loss of bandwidth).
Embedded channel management mode loses a lot of necessary information
channel remove mode
channel switch mode
number of quiet period purpose, quiet period purpose
It is not clear why the reserved field in Table 26 is required. If the reserved is really required, the length of the reserved field should be defined.
Liwen Chu STMicroelectronics
John Doe, Some Company

5. Option #1: Delete Embedded mode feature
March 2007
Option #1: Delete Embedded mode feature
Instructions to the editor in green:
Update the paragraph on line 23 on page 165 as follows:
A robust and efficient channel management component is a critical feature. In fact, the channel management component incorporated in CMAC allows systems to efficiently and dynamically use the available channels as the radio environment utilization changes. In CMAC, explicit channel management mode is provided.
Delete the paragraph on line 2 on page 166:
The embedded mode of channel management has the advantage that individual channel management commands need not be sent (as it is the case in the explicit mode), and hence better spectrum utilization can be achieved. Another advantage of the embedded mode is that it addresses all CPEs in a cell, and hence is an effective way to take corrective actions in case an incumbent user starts operating in a channel occupied by all CPEs in an cell.
Liwen Chu STMicroelectronics

6. March 2007
Option #2: Fix Embedded mode to only include the Channel Action information in DCD when needed
Instructions to the editor in green:
Add a new Scope column to indicate the scope that each IE should be used in Table 26.
This scope column indicate that “channel action related IEs” shall be included in DCD message when needed.
Add the following information in Table 26
channel remove mode
channel switch mode
number of quiet period purpose, quiet period purpose
Liwen Chu STMicroelectronics