1. doc.: IEEE 802.22-12-0088r0 Submission October 2012 Sunghyun Hwang, ETRISlide 1 [Resource Allocation for IEEE 802.22b Systems] IEEE P802.22 Wireless RANs Date: 2012-10-28 Authors: 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 http://standards.ieee.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 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 Chairhttp://standards.ieee.org/guides/bylaws/sb-bylaws.pdf Apurva Mody Apurva Mody 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 patcom@iee.org.patcom@iee.org

2. doc.: IEEE 802.22-12-0088r0 Submission Summary Classification Statement It is a partial proposal regarding the resource allocation for 802.22b systems. –Address the issues of resource allocation –Propose the resource allocation and backup channel management on a group basis –Compare the MAP overhead according to network model –Mainly consider the Smart Metering Model and Real-time/near real-time video Monitoring Model as described in the 802.22b Functional Requirements Document October 2012 Sunghyun Hwang, ETRISlide 2

3. doc.: IEEE 802.22-12-0088r0 Submission Technology Overview Very large number of devices, small burst transmissions –It is a burden of overhead to allocate the resources to each devices individually. It is also inefficient to use random-access fully. –The solution is Group Resource Allocation (GRA) Allocate the resources to the Group and contend the resources within each Group Select the appropriate resource allocation method (i.e., contention scheme or reservation scheme) within Group considering the Group characteristics Manage the backup channel on a Group basis October 2012 Sunghyun Hwang, ETRISlide 3

4. doc.: IEEE 802.22-12-0088r0 Submission MAP Overhead as Percentage of Frame Individual RA vs. group RA Assumptions –Smart Metering Model (Upstream) 1 BS, 25 H-CPEs, 2500 L-CPEs (100 L-CPEs per H-CPE) Max. simultaneous communication L-CPEs: 2500 (H-CPEs: 25) –Real-time/near real-time video Monitoring Model (Upstream) 1 BS, 250 H-CPEs, 2500 L-CPEs (10 L-CPEs per H-CPE) Max. simultaneous communication H-CPEs: 100 –Bits per US-MAP IE: 16 –Total bits per frame: 24*1440=34,560 Assuming 6 MHz BW, ¼ CP, and QPSK-1/2 October 2012 Slide 4Sunghyun Hwang, ETRI

5. doc.: IEEE 802.22-12-0088r0 Submission MAP Overhead as Percentage of Frame October 2012 Slide 5Sunghyun Hwang, ETRI 4.7% 2150 1.2%

6. doc.: IEEE 802.22-12-0088r0 Submission How to make a group? (Hub-device vs. Nano-device) Hub-device is a controller of a group consisting of many Nano-devices Hub-device (only one): access to DB, network entry with BS, identify the Group ID(GID) Nano-device (multiple): Sync. to Hub-device and/or BS Hub-device is mode II or mode I device, but Nano- device is mode I device only Nano-devices has same GID, but different Device ID(DID) Grouping the Nano-devices which connect to the same Hub-device October 2012 Sunghyun Hwang, ETRISlide 6

7. doc.: IEEE 802.22-12-0088r0 Submission Type of Group Fixed Group –Hub-device is fixed (e.g., on the building, house, tower) –Fixed group with fixed devices (e.g., village, wind turbines) –Fixed group with nomadic devices (e.g., live stocks) Mobile Group –Hub-device is mobile (e.g., on the vehicles) –Mobile group with mobile devices (e.g., vehicles, boats) –Mobile group with nomadic devices (e.g., rescue crew, firefighter) October 2012 Sunghyun Hwang, ETRISlide 7

8. doc.: IEEE 802.22-12-0088r0 Submission How to Manage the Backup Channel? All devices within group share the same backup channel information. –Control all devices with one message simultaneously Type of group is determined according to the mobility of Hub-device. Using the location information from the Hub-device, the BS can identify if the group could overlap with other group or not. October 2012 Sunghyun Hwang, ETRISlide 8

9. doc.: IEEE 802.22-12-0088r0 Submission How to Manage the Backup Channel? October 2012 Sunghyun Hwang, ETRISlide 9 Fixed vs. Fixed –In principle, allocate same backup channel to each group (e.g., farmhouse vs. wind turbine) –But, if they could overlap, the allocated backup channel should be different to avoid interference among groups (e.g., farmhouse vs. village). Fixed vs. Mobile or Mobile vs. Mobile –In principle, allocate different backup channel to each group (e.g., wind turbines vs. vehicles) –But, if they could not overlap, the allocated backup channel could be same for frequency reuse (village vs. vehicles) Periodic monitoring to check if groups could overlap each other –The backup channel of each group should be updated according to the monitoring result

10. doc.: IEEE 802.22-12-0088r0 Submission Example of Backup Channel Management October 2012 Sunghyun Hwang, ETRISlide 10

11. doc.: IEEE 802.22-12-0088r0 Submission Messages to Support CR-based GRA October 2012 Sunghyun Hwang, ETRISlide 11 ParameterSizeNote Type of Group (TOG) or Type of Hub-device (TOH) 1 bit Fixed group: 0 Mobile group: 1 Location of Group (LOG) Location of Hub-device (LOH) 6 bytes Latitude: 3 bytes Longitude: 3 bytes Device Identifier (DID)< 3 bytes Depending on the number of devices under the control of a BS. Same as Station ID(SID) in 802.22-2011 DS/US MAP IE Group Identifier (GID)< 2 bytes Depending on the number of groups under the control of a BS

12. doc.: IEEE 802.22-12-0088r0 Submission Conclusions Reduce the MAP overhead using group resource allocation As new group or new incumbent user appears, or mobile group moves into other group, we can avoid frequent channel switching –Reduce the signaling overhead –Prevent QoS degradation due to frequent channel switching October 2012 Sunghyun Hwang, ETRISlide 12