Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Qualcomm Moderated Thread - please read rules before posting -- Ignore unavailable to you. Want to Upgrade?

To: rkral who wrote (23235)	5/31/2002 12:59:24 AM
From: Clarksterh	Read Replies (1) \| Respond to of 196650

rkral - Imho, the 200 kHz BW is probably not as limiting as you think. Back to this later. Something similar to this for EOTD is very plausible to me. It's probably as simple as reading an accurate clock at a certain point in the data frame, or super-frame. And how do you know the framing is right? It is inherently impossible to do synchronization without some form of 'on your mark' (the framing in your example)and the sharpness of this is a function of bandwidth and number of samples (the last is assuming the clocks in the handset and the basestation clocks are not drifting relative to one another and there is no bias in either system (although strictly speaking it is possible to calibrate any biases it takes a relatively long time and/or extra basestations)) For EOTD the accuracy of one timing sample and range is at best on the order of 1.5 km and for more samples and it goes down by approximately square root of n where n is the number of samples. Of course all of this assumes you have no biases, and the handset is not moving and there is no changing multipath. Clark