in GSM system we have the SD channels that transport signalling traffic.

If we have blocks we can take a TS (time slot) dedicated for TCH and define it as
new SD.
In this way we can improve accessibility

In UMTS we have RRC connection , but i don't understand when we will have blocks.
If we have only a carrier f1, how many simultaneous attempts are neccessary to
have blocks ? how is it possible whe we need to expande the rrc connection capacity
?

thanks

--------------------------------------------------------------------------------
in RRC it's not count by number the below cause can cause rejection:
- CAC because of UL/DL power
- NO CE availble
- No Iub resource.
- No Code available.
--------------------------------------------------------------------------------
the Capacity in UMTS is related to : Codes , CEs , Downlink Power , RTWP (which is
uplink interference = Load of the cell) and Iub Resources .
you can have blocked RRC (Rejected) when you don't have enough resources of at
least one of the above mentioned .
first UE sends RRC Connection Request . then if the system has enough resources ,
it will send RRC Connection Setup (RRC Accepted).
--------------------------------------------------------------------------------
for RRC 4 parameter : Code, Power, CE and Iub that's all
--------------------------------------------------------------------------------
in RRC it's not count by number the below cause can cause rejection:
- CAC because of UL/DL power
- NO CE availble
- No Iub resource.
- No Code available.
--------------------------------------------------------------------------------
power cong is always in the downlink .
because one cell has a max power (20 watt , 40 , 60) according to nodeB hardware &
license .

when the cell had already used all the power it has , it cannot connect to a new
user since there is no enough power to dedicate it to this new user .

for uplink power : each UE has it's own power which is enough to overcome the path
loss in all the cells . but when the cell is loaded the noise floor increases (50%
load ==> rtwp = -103 dBm theoretically ; RTWP = Uplink Interference) ==> the UE has
to use higher power to achieve the required BLER for a given QOS service (there is
different BLER requirement for each service ; BLER = Block Error Rate) .

let's say that for a given service and a given cell load the UE cannot achieve the
required BLER even when using the max power ==> the connection cannot be
established . but if the UE moved closer toward the site ==> it maybe get the
service because in this case the path loss became smaller and we have extra power
to achieve the required BLER .

This is what is called cell breath = cell shrink which is only on the uplink (not
on the downlink) because all the UEs under this cell can decode the PCPICH (33dBm
default) but some of them are out of the uplink coverage , so to speak , because no
enough power to achieve the required BLER .

so finally when we have DL power problem ==> it can be counted . but when we have
UL power problem ==> it cannot be counted because the UE cannot connect to the
network (no message can be sent and received correctly from the UE to NodeB) .
--------------------------------------------------------------------------------
1. Congest due to CE --> add more CE
2. Congest due to Code ---> add more Code or Carrier
3. Congest due to Power ---> decrease PCPICH Power or add more carrier
--------------------------------------------------------------------------------
My network, some cell have UL load very high always over 80%, 90% or 100%. At this
time RTWP is also very high (-65 : -90 dBm). But i dont how to improve RTWP or
decrease UL Load?

your RTWP is very high and i think -90 ==> -65 dBm are not caused by the traffic
generated in the network . it's interference , maybe external .
you should plot the traffic & RTWP on charts (on hourly basis) to make sure that
you have a high RTWP even when you have very low traffic ==> this means you have
interference .

the first preventive action is to change your noise floor where you have a
parameter (used by the admission control) by which you set the value of the noise
floor . huawie have this parameter but i doun't know if other vendors have it.
after changing that parameter you will find that you have lower # of rejected
RRCs .
but finally you should determine the source of the interference & conduct the
problem to the related authorities .
--------------------------------------------------------------------------------
in RRC it's not count by number the below cause can cause rejection:
- CAC because of UL/DL power
- NO CE availble
- No Iub resource.
- No Code available.

When there is no code available which code are we talking about?

Scrambling code / Channelization code? I understand the code is to be assigned to
the UE. So is this the channelization code or scrambling code?