Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Some comments on the notes from Mariana: It is not immediately clear how a network
deployment treatment of coexistence will make any analysis more complete. Outage
probability, in this case, is down to network planning and area coverage
requirements. This is a statistic in its own right. How can the outage from,
for example, coexistence time domain analysis and network deployment be
separated? Point 1: Why uniform .16 and variable
(random) .11 positions? What does that have to do with outage probability? How
is an “outage” detected? Admittance threshold based on some
criteria? Point 2: Again, how is an
“outage” detected? Where does 2% come from? What does it mean when
the 2% threshold is crossed? Network outage? Point 3: Why care about the statistics of
distance? It either works or it doesn’t? Point 4: What’s a “fixed
network?” Non-mobile access point/base station? Any comments? Please let me know. Paul. From: Mariana
Goldhamer [mailto:marianna.goldhammer@alvarion.com] Hi Steve, I've spoke with Alvarion's people doing
deployment simulations and we agreed that the following should be added:
Mariana From: Shellhammer, Steve
[mailto:sshellha@qualcomm.com] All,
Here is a first cut at a document on coexistence metrics for the 3650 MHz
band. We can discuss it on the call and I will take suggestions on any
additional coexistence metrics.
Ian, please post on the web. 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(43). ************************************************************************************ ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses(42). ************************************************************************************ |