| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Comments added below. From: Mariana
Goldhamer [mailto:marianna.goldhammer@alvarion.com] Hi Steve, I had time for looking at the Parameter
document only. Here are some of my observations, based on
the rows in the database; some of them start with the group decision. We can
discuss them in the teleconf tomorrow. Line 4: the UCP was revised, however were added
details (like the Profile number), which were not mentioned in the comment. The
Editor did not add the same level of explanations to the CX-CBP. [Paul
Piggin] Provide
text for incorporation in the revised document. Line 13: “Accept in
principle. Delete the words "Portable and" in Scenario
C.” There still
are 15 places within the document which contain the word
“portable”, even if it was deleted from scenario C and does not
appear in other scenarios. [Paul
Piggin] It’s
ok for portable to be mentioned in the document; it’s which Scenarios are
mandatory that is important. Line 14: the path-loss model is not well
implemented; Section 5.1.2.2 refers to the LHSU in 5.1.2.1, however the equation
appears only in 5.1.1. Also the differential approach for 5.1.2.2 is not
correct and not needed. [Paul
Piggin] It is
necessary to read the section as a whole. 5.1.2.2 refers to 5.1.2.1 which in
turn refers to 5.1.1 which provides the expression for LHSU(d). The reason for this is that: 5.1.1 provides the general
expression; 5.1.2.1 provides the specific parameters for the BS-SS case, and
5.1.2.2 provides additional information for the outdoor-to-indoor case. Line 16: “Paul to rewrite explaining what
parameters apply to which scenario”; this was not done. The parameters
are not mandatory or optional. Only the scenarios are. This is why should be
clear the relation between parameters and scenarios. The existing way in which
they appear is a mess, because give redundant ands in some cases unclear
definitions of what is mandatory and what is optional. You can find a
re-definition of scenarios from Optional to Mandatory (see line 33 on page 6,
for B). [Paul
Piggin] I’m
not following this argument. Read the second paragraph in clause 3. Suffice it
to say parameters are used to narrow scenarios. Also note that parameters may
be mandatory for scenarios we have deemed to be optional. Line 30: “For now include both 4 and 10
clients per base station.” Not implemented. Hope that the omission was
not intentional. [Paul
Piggin] The comment
at line 30 is as yet unresolved. Regards, Mariana From: Shellhammer,
Steve [mailto:sshellha@qualcomm.com] All
Attached are the minutes from the 3650 MHz coexistence call this morning. https://mentor.ieee.org/802.19/file/08/19-08-0002-07-0000-conference-call-minutes.doc ------------------------------------------------------------------------------------------------------------- Marianna,
There were two items for you this morning.
Regards, Steve ************************************************************************************ 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). ************************************************************************************ |