1 / 8

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks ( WPANs)

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks ( WPANs) Submission Title: Proposed resolutions for CIDs 128, 129, 130, 131, 132, 133, and 134 Date Submitted: March, 2013 Source : Youngae Jeon , Sangjae Lee, and Sangsung Choi (ETRI), Soo-Young Chang (SYCA)

fleta
Download Presentation

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks ( WPANs)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Proposed resolutions for CIDs 128, 129, 130, 131, 132, 133, and 134 Date Submitted: March, 2013 Source: Youngae Jeon, Sangjae Lee, and Sangsung Choi (ETRI), Soo-Young Chang (SYCA) Contact: yajeon@etri.re.kr Voice:+82 42 860 6497, E-Mail: yajeon@etri.re.kr Re: [802.15 TG4m] Abstract: This document provides proposed resolutions for CIDs 128, 129, 130, 131, 132, 133, and 134ofLB#87. Purpose: To provides proposed resolutions for CIDs 128, 129, 130, 131, 132, 133, and 134of LB#87 Notice: This document has been prepared to assist the IEEE P802.15. 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 acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

  2. Comments for Sub-clause 5.1.14.1 • CID 128 (Editorial) • CID 129 (Technical) • CID 130 (Editorial) • CID 131 (Editorial) • CID 132 (Editorial) • CID 133 (Editorial) • CID 134 (Editorial)

  3. CS: A CID 128 (Editorial) • Comment • 1st instance and def. of acronym GDB occur above in 4.3.2. • Proposed Change • Remove acronym definition. • Proposed Resolution • (from) In step A, the SPC obtains the list of available TVWS channels from the geo-location database (GDB) through the Internet. • (to) In step A, the SPC obtains the list of available TVWS channels from the GDBthrough the Internet.

  4. CS: A CID 129 (Technical) • Comment • It is not clear here what "Fixed, Mode II, or Mode I Device" are • Proposed Change • Either use a footnote to refer to the FCC definitions or cross reference Table 4ig Device category where these are defined • Proposed Resolution • (from) Alternately, the SPC may obtain the list of available TVWS channels from another device (Fixed, Mode II or Mode I Device). • (to) Alternately, the SPC may obtain the list of available TVWS channels from another devicewhich can be a fixed, mode II or mode I device listed in Table 4ig.

  5. CS: A CID 130 (Editorial) • Comment • Missing "described"? • Proposed Change • eg "…as described in... • Proposed Resolution • (from) In Step B, the SPC transmits an enhanced beacon containing a TMCTP Extended Superframe Specification IE as in 5.2.4.35. • (to) In Step B, the SPC transmits an enhanced beacon containing a TMCTP Extended Superframe Specification IE as described in 5.2.4.35.

  6. CS: A CID 131 (Editorial) • Comment • Missing "by" & "described" • Proposed Change • Change to "…request a DBS allocation by sending a DBS request, as described in 5.3.14," • Proposed Resolution • (from) Upon successful reception of the beacon from the SPC, the TMCTP-child PAN coordinator may request a DBS allocation sending a DBS request, as in 5.3.14, to the SPC. • (to) Upon successful reception of the beacon from the SPC, the TMCTP-child PAN coordinator may request a DBS allocation by sending a DBS request, as describedin 5.3.14, to the SPC.

  7. CS: A CID 132 (Editorial) • Comment • Remove comma after "Step C" • Proposed Change • ie "In Step C of the example," • Proposed Resolution • (from) In Step C, of the example, the SPC indicates pending data for the TMCTP-child PAN coordinator in its beacon. • (to) In Step C of the example, the SPC indicates pending data for the TMCTP-child PAN coordinator in its beacon.

  8. CS: A CIDs 133 and 134 (Editorial) • Comment • CID 133: Superfluous "a"? • CID 134: Superfluous "or" in the text "and a channel allocated, or it or sends the DBS request" • Proposed Change • CID 133: eg "...reporting the slot and channel allocated, " • CID 134: "and a channel allocated, or it sends the DBS request" • Proposed Resolution • (from) Upon receiving the DBS request, the TMCTP-parent PAN coordinator directly generates the DBS response frame reporting the slot and a channel allocated, or it or sends the DBS request command frame to the SPC and then receives the DBS response command frame from the SPC. • (to) Upon receiving the DBS request, the TMCTP-parent PAN coordinator directly generates the DBS response frame reporting the slot and the channel allocated, or it sends the DBS request command frame to the SPC and then receives the DBS response command frame from the SPC

More Related