Parallel threads operate the same technologies in the same plane but with some interesting (probably private difference), eg two data threads both bound to a control thread, one default and one devoted to realtime. We describe them as "kin" of one another, and they are distinguished by their "kindex" ie kin index, which is simply a whole number zero upwards, zero being the default and generally only value. It's up to a control provider to know about the parallel threads and specify the kindex when requesting a FC to talk to (eg a SCPR when creating a flow)

At present there are no parallel threads for CPRs as they have 1:1 with MCPR. It may be that in the future we have to worry about the same TierMgr in two threads, eg an authentication protocol being used by both BT & IP, and they're running separate control thread. This will require further thought once the use is clearer.