|
Sep 23rd, 2008 at 10:08am
both of the above are valid answers, but I think the question refers to Frequency Hopping as it is implemented in the iDirect platform.
iDirect allow you to use multiple inbound, or return carriers in any single network, these carriers all have their own frequency. the inbound carriers on the iDirect platform are not FDMA, but MF-TDMA (Multi Frequency - Time division Multiple Access). when a system is configured with multiple inroute carriers the hub operator can define whether a remote will be allowed to use all the carriers or locked to a single carrier. If a single remote is allowed to utilise all the carriers, this is frequency hopping. the PP blade running the bandwidth allocation process tells the remotes which carrier to use - i.e. which frequency. and for how long - number of slots etc.
Carrier Grooming mode - when the system in configured in this way a remote will come on line and will remain on the same return carrier.
so Frequency Hopping is the recommended way forward from my point of view, if a carrier becomes heavily utilised the system will move remotes to a less ustilised carrier = better customer experience. Carrier grooming is very useful for fault finding though, if you have a remote causing Traffic CRC errors and this remote is in FH mode, he will cause errors across all your return channels, to identify and isolate this remote you can (in later versions) lock a remote to a single carrier individually, basically placing an individual remote in carrier grooming. Very helpful when trying to isolate and solve issues.
hope that helps.
|