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: [ Resolution of CID 139 ] Date Submitted: [ 11 Nov 2008 ] Source: [John R. Barr] Company [ Motorola, Inc. ] Address [ 1303 E. Algonquin Road, Schaumburg, IL, 60010, USA ]

nash
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: [Resolution of CID 139] Date Submitted: [11 Nov 2008] Source: [John R. Barr] Company [Motorola, Inc.] Address [1303 E. Algonquin Road, Schaumburg, IL, 60010, USA] Voice:[847-962-5407], FAX: [847-576-6758], E-Mail:[John.Barr@Motorola.com] Re: [] Abstract: [Rationale and editorial changes addressing CID 139 from LB47] Purpose: [Instruct technical editor on necessary changes to accept comment.] 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. John R. Barr, Motorola, Inc.

  2. CID 139 Comment • I see no reason for requiring both CMS and MLR for SC devices. Since the CMS is the base rate for the SC PHY, it can be used for all coexistence and interoperability messages. This should allow devices to be built that guarantee coexistence while being cost effective for certain use cases. If necessary, require that al least one mode with data rate > 1 Gbps is also included. If the text in 12.2.2.5 indicating that only CMS is mandatory does not also include MLR, then the specification will be consistent with necessary use cases. John R. Barr, Motorola, Inc.

  3. CID 139 Proposed Resolution • On Page 67,Line 6 in clause 12.2 change: • "There are two mandatory MCSs for all SC devices, The common mode signaling (CMS) and the mandatory low rate (MLR)." • to • "The common mode signaling (CMS) MSC shall be mandatory for all SC devices." • On line 28 change: • "The RS(255,239) and the shortened RS(33,17) block codes are mandatory, ..." • to • "The RS(255,239) block code is mandatory, ...". • Also, change any other place where both CMS and MLR are mandatory to just indicate CMS as mandatory. John R. Barr, Motorola, Inc.

  4. Rationale for Accepting CID 139 • There are accepted requirements for low cost devices. • Reducing number of required modes reduces implementation cost • Clause 12.1.10 indicates that only CMS is required to enable interoperability: • “The role of CMS is to enable interoperability among different PHY modes. CMS may be used for both interference mitigation and data transmission purposes.” John R. Barr, Motorola, Inc.

  5. CID 139 Accept in Principle (First) • On Page 67, Line 6 in clause 12.2 change: • "There are two mandatory MCSs for all SC devices, The common mode signaling (CMS) and the mandatory low rate (MLR)." • to • "The common mode signaling (CMS) MSC shall be mandatory for all SC devices.” • On line 28 change: • "The RS(255,239) and the shortened RS(33,17) block codes are mandatory, ..." • to • "The RS(255,239) block code is mandatory, ...” • Add the following at the end of the first paragraph of clause 12.2: • The mandatory low rate (MLR) or a low complexity mode employing OOK/DAMI shall be included in any PNC-capable SC DEV. John R. Barr, Motorola, Inc.

  6. CID 139 Accept in Principle (Option 1) • On Page 67, Line 6 in clause 12.2 change: • "There are two mandatory MCSs for all SC devices, The common mode signaling (CMS) and the mandatory low rate (MLR)." • to • “The mandatory MSCs for an SC device shall be either a combination of common mode signaling (CMS) and the mandatory low rate (MLR), or, alternatively, a low complexity mode employing OOK/DAMI.” • Add the following at the end of the paragraph in clause 12.1.10: • All PNC-capable DEVs shall implement the CMS MSC. John R. Barr, Motorola, Inc.

  7. CID 139 Accept in Principle (Option 2) • On Page 67, Line 6 in clause 12.2 change: • "There are two mandatory MCSs for all SC devices, The common mode signaling (CMS) and the mandatory low rate (MLR)." • to • “There are two mandatory MCSs for all SC devices except for low complexity mode devices, the common mode signaling (CMS) and the mandatory low rate (MLR). OOK/DAMI modes are allowed for low complexity SC devices.” • Add the following rules to clause 12.1.8: • An OOK/DAMI PNC-capable DEV, when operating as a PNC, shall transmit an OOK/DAMI beacon and a CMS sync frame in every superframe. • An OOK/DAMI PNC-capable DEV shall be able to receive the CMS sync frame and command frames. • Note: It is still possible to implement OOK/DAMI PNC-capable device that uses CMS and MLR modes. John R. Barr, Motorola, Inc.

  8. CID 139 Accept in Principle (Final) • On Page 67, Line 6 in clause 12.2 change: • "There are two mandatory MCSs for all SC devices, The common mode signaling (CMS) and the mandatory low rate (MLR)." • to • “There are two mandatory MCSs for all SC devices except for low complexity mode devices, the common mode signaling (CMS) and the mandatory low rate (MLR). OOK/DAMI modes are allowed for low complexity SC devices.” • Note: It is still possible to implement OOK/DAMI PNC-capable device that uses CMS and MLR modes. John R. Barr, Motorola, Inc.

More Related