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

Re: [STDS-802-11-TGM] CID 195 and CID 196 - antenna ID range



--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---
I am not hard set on the 1-254 for any of the specific cases, but rather the initial proposal.
As we look at the specific variable, if it should allow for 0 and 255, then we should make it so.
Jon

-----------------------------------------------------------------------------
Jon Rosdahl                 Engineer, Senior Staff
office: 801-492-4023      Qualcomm Technologies, Inc.
cell:   801-376-6435      10871 North 5750 West
                                   Highland, UT 84003

A Job is only necessary to eat!

A Family is necessary to be happy!!

On Thu, Jan 18, 2018 at 9:22 AM, Graham Smith <gsmith@xxxxxxxxxxxxxxxxxxx> wrote:

If I look at Table 15-1, yes, it is wrong at 1-256, but I say it should be 0-255.  The TX_ANTENNA is further specified in this section as “Selects the antenna used by the PHY for transmission (when diversity is disabled),  So I would assert that 0 (unknown) and 255 (Multiple) are valid values. 

IMHO.

 

From: ***** 802.11 REVm - Revision Maintainance List ***** [mailto:STDS-802-11-TGM@ieee.org] On Behalf Of Jon Rosdahl
Sent: Thursday, January 18, 2018 11:08 AM
To: STDS-802-11-TGM@xxxxxxxxxxxxx.ORG
Subject: Re: [STDS-802-11-TGM] CID 195 and CID 196 - antenna ID range

 

--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Thanks for the feedback Graham,

I agree that for the 0 and 255 values are valid in certain instances, but in these specific cases, you should know which antenna you are sending/receiving on due to the context of the variable.

There are other variables that the 0 and 255 are usable and I would agree are used.

It definitely is the case that 256 is not a correct value, so that one needs change for sure.

The context of these specific variables should be evaluated to see if the 0 and 255 is valid, I am not suggesting changing in general, but rather looking at the noted locations.

FWIW,

Jon


-----------------------------------------------------------------------------
Jon Rosdahl                 Engineer, Senior Staff
office: 801-492-4023      Qualcomm Technologies, Inc.
cell:   801-376-6435      10871 North 5750 West
                                   Highland, UT 84003


A Job is only necessary to eat!
A Family is necessary to be happy!!

 

On Thu, Jan 18, 2018 at 9:02 AM, Graham Smith <gsmith@xxxxxxxxxxxxxxxxxxx> wrote:

Hi Jon,

I am still not sure about this.  To me the Antenna ID is very clear, it can be 0 to 255.  1 to 254 are specific antennas, 0 is unknown and 255 is multiple. 

Hence 0 and 255 are valid values.  Furthermore I would opine that 0 is the most used value.

Graham

 

From: ***** 802.11 REVm - Revision Maintainance List ***** [mailto:STDS-802-11-TGM@ieee.org] On Behalf Of Jon Rosdahl
Sent: Thursday, January 18, 2018 4:36 AM
To: STDS-802-11-TGM@xxxxxxxxxxxxx.ORG
Subject: [STDS-802-11-TGM] CID 195 and CID 196 - antenna ID range

 

--- This message came from the IEEE 802.11 Task Group M Technical Reflector ---

Greetings,

    CID 195 and 196 address a concern where a parameter to hold an antenna ID should have a valid range of 1-254.

   Antenna ID is defined in 9.4.2.40 (Antenna element).

   Variables that hold an specific valid Antenna ID include TX_ANTENNA (specific for transmit), RX_ANTENNA (specific ID for receiving antenna), dot11CurrentTXAntenna (specific ID for transmitting), dot11CurrentRxAntenna (specific ID for receiving antenna), dot11AntennaListIndex (specifies a valid antenna ID). These variables do not provide for the value of "0 = unknown" or for "255 = Multiple Antenna".

 

The CIDs and the proposed resolutions are noted below. 


CID 195

Comment: The antenna ID in the Antenna element is only allowed to be from 1 to 254 (0 and 255 have special meanings)

 

Proposed Change: Change 256 to 254 in Table 16-1, 15.2.2.7 and Table 16-2; change 255 to 254 in C.3 for dot11CurrentTxAntenna, dot11CurrentRxAntenna and dot11AntennaListIndex

 

Proposed Resolution:

REVISED (GEN: 2018-01-18 08:42:37Z)
at P2675.56 in Table 15-1 - Change 256 to 254 (range for TX_ANTENNA).
at P2676.20 in Table 15-2 - Change 256 to 254 (range for TXVECTOR TX_ANTENNA).
at P2676.49 in Table 15-2 - Change 256 to 254 (range for RX_ANTENNA).

at P3875.2   Change 255 to 254 (range for dot11CurrentTxAntenna).
at P3875.37 Change 255 to 254 (range for dot11CurrentRxAntenna).
at P3883.61 Change 255 to 254 (range for dot11AntennaListIndex)
This corrects the range for antenna ID.

 

CID 196

Comment:  The antenna ID in the Antenna element is only allowed to be from 1 to 254 (0 (unknown) and 255 (multiple) have special meanings, but maybe they're allowed on receive)

 

Proposed Change:  In Table 16-5 change 1-256 to 1-254.  In Table 17-2 change 0-255 for ANT_STATE to 1-254

 

Proposed Resolution:

REVISED (GEN: 2018-01-18 07:56:47Z)
In Table 16-5 Change at P2716.22 "ANT_STATE" to "RX_ANTENNA".
In Table 16-5 Change at P2716.22 "1-256" to "1-254"
In Table 16-5 Change at P2716.25 "1 to 256" to "1 to 254"

In Table 17-2 Change at P2732.59 "ANT_STATE" to "RX_ANTENNA"
In Table 17-2 Change at P2732.59 "0-255" to "1-254"

Change at P2710.60  "ANT_STATE (the antenna used for receive)," to "RX_ANTENNA"

This corrects the range for use of antenna ID.

There are only 3 instances of ANT_STATE which is referenced as the receive antenna information, so the change to RX_ANTENNA is consistent.

 

A Motion will be prepared to accept the proposed resolutions for CID 195 and CID 196 made on Thursday PM1 slot.

regards,

Jon

 

 

-----------------------------------------------------------------------------
Jon Rosdahl                 Engineer, Senior Staff
office: 801-492-4023      Qualcomm Technologies, Inc.
cell:   801-376-6435      10871 North 5750 West
                                   Highland, UT 84003


A Job is only necessary to eat!
A Family is necessary to be happy!!

_______________________________________________________________________________

IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.

SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.

Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________

 

_______________________________________________________________________________

IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.

SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.

Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________


_______________________________________________________________________________

IF YOU WISH to be Removed from this reflector, PLEASE DO NOT send your request to this CLOSED reflector. We use this valuable tool to communicate on the issues at hand.

SELF SERVICE OPTION: Point your Browser to - http://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGM and then amend your subscription on the form provided. If you require removal from the reflector press the LEAVE button.

Further information can be found at: http://www.ieee802.org/11/Email_Subscribe.html _______________________________________________________________________________