View Full Version : Question question about TCell
Pierron
2010-12-11, 11:31 AM
Hi all
in the network CDMA we have 2 frequency and I has a doubt, If I have a site with 4 sectors (4 for each frequency), what must be the parameter Tcell for each cell??
is this config OK?
Freq1 Freq 2
Sector 1 Chip 0 Chip0
Sector 2 Chip 256 Chip256
Sector 3 Chip 512 Chip512
Sector 4 Chip 0 Chip256
If somebody can explain how is used the Tcell It will be very apreciated, thanks a lot
Hi all
in the network CDMA we have 2 frequency and I has a doubt, If I have a site with 4 sectors (4 for each frequency), what must be the parameter Tcell for each cell??
is this config OK?
Freq1 Freq 2
Sector 1 Chip 0 Chip0
Sector 2 Chip 256 Chip256
Sector 3 Chip 512 Chip512
Sector 4 Chip 0 Chip256
If somebody can explain how is used the Tcell It will be very apreciated, thanks a lot
Hi!
I do it in steps of 512, starting with 0, Separate for every frequency. (Not Huawey).
Anyhow, in some other discussion on scrambling code planning, I got impression it simply
does not matter, but I have not tried it yet. It is on "to do list" to put it on 0 for every cell.
I recall FNOFFSET on 2g... And then, 10 years ago, we all put it to 0 and nobody reported
any noticeable impact.
BR
s52d
Hi
We use steps of 256. if you have two frequencies overlay there will be no problem to use to same spacing, i.e., 0-256-512. recall that TCELL is used for sync puprose to separate between cells.
giegala
2010-12-14, 06:15 AM
Unless you are using old NSN version, where HSDPA scheduler is controlled by TCELL, so all TCELL values in one site should be different
Pierron
2011-06-09, 06:09 AM
Hi
We use steps of 256. if you have two frequencies overlay there will be no problem to use to same spacing, i.e., 0-256-512. recall that TCELL is used for sync puprose to separate between cells.
yep, the purpose is sinconize the cells, be carefull with to put the same value in two cells (same frecuency) in the same nodeB, last year we had a lot of Call Fails access, this was the problem for the cell, just change and everything work fine
vBulletin® v4.2.5, Copyright ©2000-2024, Jelsoft Enterprises Ltd.