@Martin Keding wrote:
The co-location tool is great and gives the numbers for downlink, etc
But what is confusing is the LTE Frame configuration options (0,1,2)
The co-loc tool doesn't address this and the documentation is unclear, at least to me.
Hi Martin,
The frame configuration options (0, 1, 2) are literally refering to the LTE standard TDD frame configurations as mentioned here, for example: http://niviuk.free.fr/lte_tdd.php
For colocation with LTE, we can only support frame configurations 0, 1, and 2. LTE frames are 10ms long, but if their periodicity is 5ms (i.e. the DL to UL switch point is every 5ms, like LTE frame configurations 0, 1, and 2) and both halves of the 10ms frame are identical (which leaves out LTE frame configuration 6, which swaps a DL symbol for an UL symbol in the second 5ms interval), they can be temporally shifted to match a 5ms Canopy frame configuration.
For example, taking LTE frame config 1 (and ignoring the special subframe symbols for the sake of simplicity), the LTE symbol pattern is:
|-5ms-|-5ms-|
DUUD DUUD
By shifting the Canopy frame start time to align with the second D symbol, and using a 50% duty cycle with 5ms frame, Canopy neatly aligns with LTE like so:
|-5ms-|-5ms-|
LTE: DUUD DUUD
Canopy: D DUU
|-5ms-|
The same kind of temporal shift can be done with frame 2 along with a 75% duty cycle, and frame 0 is naturally aligned when using a 25% duty cycle in Canopy.
Hope that clears things up!
-Al