Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-16] PAR Scope for M2M

Hi,

 

I support Dan’s text, because it is simply addressing the M2M market.

 

I was confused by the limitations introduced in the PAR Scope in the last time: the scope of this PAR is to cover the M2M market or to make sure that no changes are done to the existing products?

 

Regards,

 

Mariana

From: Gal, Dan (Dan) [mailto:dan.gal@ALCATEL-LUCENT.COM]
Sent: 28 April, 2010 9:45 PM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] PAR Scope for M2M

 

Gentlemen,

 

After reading all the preceding comments and text proposals, I had quite a few comments of my own and thought I would rather make a “comprehensive proposal” and suggest the following PAR wording (building upon portions of the GRIDMAN PAR):

 

2.1 Title: Standard for Local and Metropolitan Area Networks Part 16: Air Interface for Broadband Wireless Access Systems- Amendment: Support for Machine-to-Machine (M2M) Communication.

 

5.2 Scope: This amendment specifies protocol enhancements to the IEEE 802.16 standard for enabling efficient Machine-to-Machine (M2M) communication. Limited OFDMA extensions are included for enabling concurrent operation of M2M devices and mobile stations. Mobile base stations and mobile relay stations are also supported.

 

5.3 Is the completion of this standard dependent upon the completion of another standard: Yes, amendment 16m.

 

5.4 Purpose: This amendment is intended to add support for efficient M2M communication as well as to address other M2M operation requirements that the current IEEE 802.16 standard does not support.


5.5 Need for the Project: Compelling M2M applications that would enhance the market appeal and competitiveness of the IEEE 802.16 OFDMA based radio access technology.

 

 

Best regards

Dan Gal

Alcatel-Lucent

 

From: Shawn Taylor [mailto:shawn@TAYLOR.CX]
Sent: Wednesday, April 28, 2010 12:51 PM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] PAR Scope for M2M

 

 

Here are couple more slight edits. In purple this time.  

 

Shawn

 

 

This standard amends This amendment proposes enhancements to the IEEE 802.16 Advanced Air Interface specification to provide for enabling Machine to Machine (M2M) Communications between an M2M capable IEEE 802.16 subscriber station M2M device and IEEE 802.16 base station. It proposes limited The amendment will include extensions to the OFDMA PHY and MAC layers to support the unique requirements of M2M communications. PHY modifications, that are required for implementing the unique requirements of M2M communications, will also be included so long as they, but do not impact the frame structure, DL/UL physical structure and DL/UL control structure, can be considered.

This amendment provides support for IEEE 802.16 Advanced Air Interface equipment.  Backward compatibility with IEEE 802.16m specification legacy OFDMA equipment is maintained. 

 

 

 

 

 

 

 

 

 

 

 

On Apr 28, 2010, at 09h48 , Phillip Barber wrote:

 

I know this is an early draft of proposed PAR language, but…

 

A Scope statement is intended to say what a Standard includes, not what may be considered in the development process. It is not appropriate to say, ‘It proposes…’ and ‘PHY modifications…can be considered.’ A Standard does not ‘propose’ anything’ A Standard ‘is’. It defines a specification of features and functions. You either include, or you do not include. Consideration is irrelevant. So you have to be a bit more critical in the PAR language prep phase to determine EXACTLY what is in, what is within Scope AND WILL BE INCLUDED IN THE COMPLETED STANDARD (though I would agree that it is up to the Sponsor Ballot Members to determine if the necessary material is included, and when the Standard is complete). If you are not sure, don’t include it. If you feel confident you need the changes/enhancements, then include appropriate definitive language in the Scope:  If you are unsure, you can argue the point during the Standard development process and if you cannot do without such changes/enhancements then you process a PAR change to bring the required material into Scope.

 

Thanks,

Chief Scientist

Wireless Advanced Research and Standards

Huawei Technologies Co., LTD.

 

From: Ron Murias [mailto:ron@MURIAS.CA] 
Sent: Wednesday, April 28, 2010 8:58 AM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] PAR Scope for M2M

 

Re-sending with my own clean-up  (I missed cleaning up a couple more points in the previous email)...

 

Again, my recommendations in green:

 

 

On 2010-04-28, at 7:01 AM, Ron Murias wrote:



Hi Rakesh (and all),

 

I think the Scope needs more clean-up, with some recommendations included below in green.  While I won't comment on your PHY sentence, the wording is not consistent with what should be written in the Scope, especially wording like "can be considered", so I think that if the group agrees with the concept you are promoting, the sentence should be re-written (in line with my recommended text in green).

 

Thanks,

Ron

 

 

On 2010-04-28, at 3:31 AM, Rakesh Taori wrote:



Jose and all,

Thank you Jose, Hangyo and Shilpa for preparing the documents and organizing the discussions.

We would like to share some remarks on the 
(a) PAR language in the PAR & 5C document (0003r1) 
(b) the "MAC/PHY impact" sections of the SG report (0002r4) 
We will try and upload documents with comments on both of these. In this e-mail, I would just like to focus on the PAR language and would be grateful if you could review and consider our changes during the discussion in CC #5.

=== Suggested Changes to the PAR language === 
This standard amends This amendment proposes enhancements to the IEEE 802.16 Advanced Air Interface specification to provide for enabling Machine to Machine (M2M) Communications between an M2M capable IEEE 802.16 subscriber station M2M device and IEEE 802.16 base station. It proposes limited extensions to the OFDMA PHY and MAC layers to support the unique requirements of M2M communications. PHY modifications that are required for implementing the unique requirements of M2M communications, but do not impact the frame structure, DL/UL physical structure and DL/UL control structure, can be considered.

This amendment provides support for IEEE 802.16 Advanced Air Interface equipment.  Backward compatibility with IEEE 802.16m specification legacy OFDMA equipment is maintained. 
========

As you can see, the key change that we are proposing is further refinement of the PHY scope. 
Our main concern is HW impact. Any alternative language that explicitly addresses the HW change concern would be welcome also.

I am guessing that our changes, other than the PHY sentence, are likely to be acceptable to most people.

Thanks and Kind Regards, 
Rakesh
  _____  

From: Puthenkulam, Jose P [mailto:jose.p.puthenkulam@INTEL.COM]
Sent: Wednesday, April 28, 2010 4:23 PM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] 802.16 Project Planning Committee: M2M CC#4 Update - PAR Scope Discussion Summary + CC#5 bridge details again


Dear 802.16 M2M Fans, 
  
I’ve uploaded the M2M Study Report 802.16ppc-10/0002r4 that is a result of the discussions from CC#4. Thanks to HanGyu Cho and all the contributors to make this possible.

  
http://dot16.org/ul//upload/ppc_db/80216ppc-10_0002r4.doc 
  
I’ve also uploaded a M2M PAR and 5C initial working draft revised from the one we had earlier as place holder. It is 802.16ppc-10/0003r1. This also includes the text proposed by Shilpa Talwar based on some offline discussions we asked her to carry out after CC#4 to generate some initial text.  I’ve also filled out the rest of the PAR form and 5C as first cut for review on the call tomorrow. This document is just an input for discussion at this point. Hope is to get a consensus version after the call tomorrow.

  
http://dot16.org/ul//upload/ppc_db/80216ppc-10_0003r1.doc 
  
The final version of the PAR & 5C and also the Study report will only be finalized during the May meeting. These are draft documents we are preparing for discussion in the May meeting.

  
Thanks & BR, 
jose 
 

 

 

 

 



************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(190).
************************************************************************************


************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(42).
************************************************************************************



************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(42).
************************************************************************************