2 Overview of Call Admission Control

Call Admission Control (CAC) is used to determine whether the system resources in a cell are sufficient to
accept a resource request. If the system resources are sufficient, the resource request is accepted;
otherwise, the resource request is rejected.
A radio link sends a resource request to the CAC functional module when additional resources are
required, in cases such as radio resource control (RRC) connection setup, new service setup, change of
existing services, soft handover, and cell change. Upon receiving a resource request, the CAC functional
module determines whether the request can be accepted by measuring the cell load and the requested
resources. For details about measuring the cell load, see the Load Control Feature Parameter
Description.
The admission decision performed using CAC is based on the following resources: code resources,
power resources, NodeB credit resources, and Iub resources. In the case of an HSPA resource request,
the admission decision is also based on the number of HSPA users. The admission succeeds only when
the resources on which CAC is based are available.
With CAC, an overloaded cell can accept resource requests for an RRC connection setup only in the case
of emergency calls, detachments, or registrations. This is because the priority of such requests is high.
This helps maintain system stability when cells are overloaded. In addition, admitting or rejecting users
over FACH or enhanced FACH channels (HS-DSCH) in an overloaded cell can be specified by setting
FACH_UU_ADCTRL of the NBMCacAlgoSwitch parameter.

8)SYS_HO_OUT_CIPHER_SWITCH. When it is checked, the RNC will add ciphering

byte at GSM HANDOVER COMMAND if the GSM system do not add any cipher
information at that message.
9)SYS_HO_CIPHER_CONFIG. When it is checked, the cipher configuration in the
added cipher byte in GSM will be A5/1.When it is no checked ,the cipher
configuration is A5/0.
10)ARRED_CELL_FOR_CSDOMAIN_RST. When it is checked, cell will be bared when
CS domain is invalid, otherwise the CS domain will be bared when CS domain is
invalid. It is invalid If SYS_INFO_UPDATE_FOR_IU_RST is not checked.
11)CR2284R1_SWITCH.in section 8.6.6.28 of TS25.331 of R5 Before2006, it
describes that the HFN should add one when UE is ciphering in the situation of
Timing re-initialized hard handover, while not specified in RB SETUP process in the
section of 8.6.4.3. so it is not clear whether to add or not in RB SETUP in DRD
scenarios. CR2284R1 clarify that HFN should add one in RB SETUP process with
Timing re-initialized hard handover. when it is checked ,RNC accepts this CR2284R1;
when it is not checked ,RNC does not accept this CR2284R1.
12)CDT_MSG_FULL_TRACE: When it is checked, CDT trace function which starts
tracing from message RRC CONNECT REQUEST.
13)CR2284R1_COMPATIBLE_SWITCH.CR2284R1 causes the compatible problem. if
UE is not consistent with RNC regarding whether accept the CR2284R1 or not, it will
cause the problem of streaming when UEs are communicating with each other. So
RNC creates this switch. when it is checked, RNC is auto-adaptive to accept the
CR2284R1 according to UE version information. The principles that RNC judges UE
whether to accept the CR2284R1 are as follows: R5 and above UE accepts the CR;
R99/R4 UE, if it receives the START LIST value from RB SETUP COMPLETE,RNC

figures that UE accepts the CR; R99/R4 UE, if it only receives the START value from
RB SETUP COMPLETE,RNC figures that UE does not accept the CR; when it is not
checked, whether RNC accept the CR or not is according to CR2284R1_SWITCH. The
relations between these two switches CR2284R1_SWITCH and
CR2284R1_COMPATIBLE_SWITCH are as follows:
(1)CR2284R1_COMPATIBLE_SWITCH is checked, RNC is self-compatible, so the
CR2284R1_SWITCH is invalid;

GSM will be A5/1.When it is no checked ,the cipher configuration is A5/0.

10)ARRED_CELL_FOR_CSDOMAIN_RST. When it is checked, cell will be bared when
CS domain is invalid, otherwise the CS domain will be bared when CS domain is
invalid. It is invalid If SYS_INFO_UPDATE_FOR_IU_RST is not checked.
11)CR2284R1_SWITCH.in section 8.6.6.28 of TS25.331 of R5 Before2006, it
describes that the HFN should add one when UE is ciphering in the situation of
Timing re-initialized hard handover, while not specified in RB SETUP process in the
section of 8.6.4.3. so it is not clear whether to add or not in RB SETUP in DRD
scenarios. CR2284R1 clarify that HFN should add one in RB SETUP process with
Timing re-initialized hard handover. when it is checked ,RNC accepts this CR2284R1;
when it is not checked ,RNC does not accept this CR2284R1.
12)CDT_MSG_FULL_TRACE: When it is checked, CDT trace function which starts
tracing from message RRC CONNECT REQUEST.