Professional Documents
Culture Documents
Power-based admission decision involves admission decision for RRC connection setup request
as well as RAB admission decision based on algorithms 1, 2, or 3.
Based on the current cell load (indicated by the uplink load factor and downlink TCP) and the
predicted load increment due to admission of the new service, the RNC determines whether the
cell load will exceed the threshold upon admitting the new service. If yes, the RNC rejects the
access request. If not, the RNC accepts the access request.
Depending on the current ENU and the access request, the RNC determines whether the ENU
will exceed the threshold upon admitting a new service. If yes, the RNC rejects the request. If
not, the RNC accepts the request.
This algorithm assumes that load increment upon admission of a new service is 0. Based on the
current cell load (indicated by the uplink load factor and downlink TCP), the RNC determines
whether the cell load will exceed the threshold upon admitting the new service. If yes, the RNC
rejects the access request. If not, the RNC accepts the access request.
If the Control RTWP Anti-interference function switch (RsvdBit1) is enabled, the system
checks whether the uplink equivalent user load proportion of the cell is lower than 40%. If it is
lower than 40%, the access request is accepted. Otherwise, the original procedure remains
unchanged.
If the Control RTWP Anti-interference function switch is disabled, the RNC rejects the access
request.
The following figure shows the basic procedure of power-based admission decision.
Four basic load thresholds are used for power-based admission decision. They are:
Admission control involves uplink admission control and downlink admission control. The
corresponding admission control switches NBMUlCacAlgoSelSwitch and
NBMDlCacAlgoSelSwitch are independent of each other.
For a non-intra-frequency handover request, both uplink and downlink decisions are needed if
both uplink CAC and downlink CAC are enabled.
For a rate upsizing request, the RNC makes the decision, as shown in 0.
For a rejected RRC connection setup request, the RNC performs DRD or redirection.
For a rejected service request, the RNC performs preemption or queuing according to the actual
situation.
To ensure that the RRC connection setup request is not denied by mistake, tolerance principles
are applied.
When power-based admission is based on power or interference (algorithm 1 and algorithm 3):
− For the RRC connection setup request for the reason of emergency call, detach or registration,
direct admission is used.
− For the RRC connection setup request for other reasons, the UL or DL OLC trigger threshold
(UlOlcTrigThd or DlOlcTrigThd) is used for admission.
For details about UL and DL OLC trigger thresholds, see Error! Reference source not
found."Error! Reference source not found.."
− For the RRC connection setup request for the reason of emergency call, detach or registration,
direct admission is used.
− For the RRC connection setup request for other reasons, the admission decision is made as
follows:
a. When UL_UU_OLC or DL_UU_OLC is set to 1, RRC connection setup request is rejected
when the cell is in the overload congestion state. If the cell is not in the overload state, the UL or
DL OLC trigger threshold is used for power-based admission.
The following figure shows the procedure of uplink power–based admission decision for R99
cells.
The procedure of uplink power–based admission decision for R99 cells is as follows:
1. The RNC obtains the uplink RTWP of the cell and uses the formula
to calculate the current uplink load factor ηUL, where PN is the received uplink background
noise.
2. The RNC calculates the uplink load increment ΔηUL based on the service request.
3. The RNC uses the following formula to predict the uplink load factor:
Eb/N0 of the new incoming call, which has a positive correlation with the uplink load
increment
UL neighbor interference factor, which has a positive correlation with the uplink load
increment
Active Factor (AF) of the new incoming call, which has a positive correlation with the uplink
load increment, and varies with the traffic class, user priority level, and carrier type (DCH or
HSPA)
4. By comparing the predicted uplink load factor ηUL,predicted with the corresponding threshold
(UlNonCtrlThdForHo, UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR, or
UlNonCtrlThdForOther), the RNC decides whether to accept the access request. If the access
request is accepted, the RNC processes the access request. If the access request is rejected, the
RNC performs the next step.
5. The RNC checks whether the Control RTWP Anti-interference function switch (RsvdBit1) is
enabled. If it is enabled, the RNC checks whether the uplink equivalent user load proportion of
the cell is lower than 40%. If it is lower than 40%, the RNC accepts the access request.
Otherwise, the RNC rejects the access request.
AF of the service
The formula is similar to that for R99. After the RSEPS measurement is introduced, the UL
RTWP is divided into two parts: controllable part and uncontrollable part. The controllable part
is generated by the E-DCH scheduling service, and others belong to the uncontrollable part. The
following figure shows the uncontrollable part of the UL RTWP.
Type B: UEs of this type are not in the serving E-DCH cell.
The methods of calculating the uplink load vary according to user type.
For type A, the uplink load generated by the E-DCH scheduling service is calculated as
follows:
For type B, the uplink load generated by the E-DCH scheduling service is calculated through
, which is set to 0.
Since the HSUPA scheduling algorithm consumes additional uplink power resources, the power
load of the HSUPA cell is always relatively high. Therefore, the CAC algorithm combines the
PBR-based decision with the load-based decision to reduce the number of potential erroneous
rejections.
PBR-based decision is used to check whether the QoS requirement of existing users is fulfilled.
The QoS is measured on the basis of the Provided Bit Rate (PBR) of the users. If the QoS
requirement is fulfilled, new users are allowed to access the network.
As shown in the previous figure, the Scheduling Priority Indicator (SPI) of a new HSUPA user is
SPINew user.
When the admission of HSUPA scheduling services is implemented, the following formulas
apply:
1.
2.
3.
4.
5.
Here:
− ηthd is the cell UL admission threshold of a specific type of service. The threshold may be
UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR, UlNonCtrlThdForOther, or
UlNonCtrlThdForHo.
The RNC admits the HSUPA scheduling services in either of the following cases:
− Formula 1, 2, or 3 is fulfilled.
− Formula 4 is fulfilled.
For HSUPA non-scheduling services, the RNC admits the HSUPA non-scheduling services in
either of the following cases:
− Formula 1, 2, or 3 is fulfilled.
If the HSUPA scheduling services or non-scheduling services are rejected according to the
previous conditions, the RNC checks whether the Control RTWP Anti-interference function
switch (RsvdBit1) is enabled. If it is enabled, the RNC checks whether the uplink equivalent
user load proportion of the cell is lower than 40%. If it is lower than 40%, the RNC accepts the
access request. Otherwise, the RNC rejects the access request.
For the first HSUPA service accessing the cell, the decision formulas that involve PBR are
regarded as unsatisfied.
If the PBR measurement is deactivated, the decision formulas that involve PBR are regarded as
unsatisfied.
If the RSEPS measurement is deactivated, the admission algorithm automatically changes into
algorithm 2.
For details about the scheduling mode of services on HSUPA, see the Radio Bearer Parameter
Description.
Uncontrollable interference must be kept within a certain range. The purpose is to ensure the
stability of the system and to prevent non-scheduling services and DCH services from seizing the
resources of HSUPA services. In this regard, the CAC algorithm combines the uncontrollable
part–based decision and the total load–based decision.
When the admission of DCH services is implemented, the following formulas apply:
Here:
− is the cell UL admission threshold for a specific type of service. The threshold may be
UlNonCtrlThdForAMR, UlNonCtrlThdForNonAMR, UlNonCtrlThdForOther, or
UlNonCtrlThdForHo.
If formulas 1 and 2 are fulfilled, the RNC admits DCH services. If they are not fulfilled, the
RNC checks whether the Control RTWP Anti-interference function switch (RsvdBit1) is
enabled. If it is enabled, the RNC checks whether the uplink equivalent user load proportion of
the cell is lower than 40%. If it is lower than 40%, the RNC accepts the access request.
Otherwise, the RNC rejects the access request.
The following figure shows the procedure of downlink power–based admission decision.
1. The RNC obtains the cell downlink TCP and calculates the downlink load factor ηDL by
dividing the maximum downlink transmit power Pmax by this TCP.
2. The RNC calculates the downlink load increment ΔηDL based on the service request and
the current load.
3. The RNC uses the following formula to predict the downlink load factor:
4. By comparing the downlink load factor ηDL,predicted with the corresponding threshold
(DlConvAMRThd, DlConvNonAMRThd, DlOtherThd, and DlHOThd), the RNC decides
whether to accept the access request.
Non-orthogonal factor, which has a positive correlation with the downlink load increment
Current TCP, which has a negative correlation with the downlink load increment
Active Factor (AF) of the incoming new call, which has a positive correlation with the
downlink load increment
The power increment estimation for the DCH RAB in the HSPA cell is similar to the DCH RAB
in the R99 cell.
The power increment estimation for HSDPA RAB ΔPDL is made on the basis of GBR, Ec/N0,
non-orthogonal factor, and so on.
When the admission of the DCH RAB is implemented, the following formulas apply:
1.
2.
3.
Here:
− is the maximum available power for HSPA. Its value is associated with the HSDPA
power allocation mode. For details, see the HSDPA Parameter Description.
The RNC admits the DCH RAB in either of the following situations:
If the GBP measurement is deactivated, the GBP involved in the decision formulas is set to 0.
When the admission of the HSDPA RAB is implemented, the following formulas apply:
1.
2.
3.
4.
5.
Here:
− is the maximum available power for HSPA. Its value is associated with the HSDPA
power allocation mode. For details, see the HSDPA Parameter Description.
The RNC admits the HSDPA streaming RAB in any of the following situations:
− Formula 1 is fulfilled.
The RNC admits the HSDPA BE RAB in any of the following situations:
− Formula 2 is fulfilled.
If the GBP measurement is deactivated, the GBP involved in the decision formulas is set to 0.
If the PBR measurement is deactivated, the decision formulas that involve PBR are regarded as
dissatisfied.
For the first HSDPA service accessing the cell, the decision formulas that involve PBR are
regarded as unsatisfied.
When the uplink CAC function or the downlink CAC function uses algorithm 2, the admission of
uplink/downlink power resources uses the algorithm depending on the ENU.
The 12.2 kbit/s AMR traffic is defined as one ENU, which stands for Equivalent Number of
Users. Thus, the 12.2 kbit/s AMR traffic can be used to calculate the ENU of all other services.
The calculation is related to the following factors:
Traffic domain, CS or PS
Service ENU
Uplink for DCH Downlink for DCH HSDPA HSUPA
Service ENU
Uplink for DCH Downlink for DCH HSDPA HSUPA
3.4 kbit/s SIG 0.44 0.42 0.28 1.76
13.6 kbit/s SIG 1.11 1.11 0.74 1.89
3.4+12.2 kbit/s 1.44 1.42 - -
3.4+8 kbit/s (PS) 1.35 1.04 0.78 2.26
3.4+16 kbit/s (PS) 1.62 1.25 1.11 2.37
3.4+32 kbit/s (PS) 2.15 2.19 1.70 2.60
3.4+64 kbit/s (PS) 3.45 3.25 2.79 3.14
3.4+128 kbit/s (PS) 5.78 5.93 4.92 4.67
3.4+144 kbit/s (PS) 6.41 6.61 5.46 4.87
3.4+256 kbit/s (PS) 10.18 10.49 9.36 6.61
3.4+384 kbit/s (PS) 14.27 15.52 14.17 9.36
1. The RNC obtains the total ENU of all existing users ENUtotal = ∑all_exist_userENUi.
2. The RNC gets the ENU of the new incoming user ENUnew.
3. The RNC uses the formula (ENUtotal + ENUnew)/ENUmax to forecast the ENU load, where
ENUmax is the configured maximum ENU (UlTotalEqUserNum or DlTotalEqUserNum).
4. By comparing the forecasted ENU load with the corresponding threshold, the RNC decides
whether to accept the access request. The threshold may be one of the following thresholds:
The admission thresholds for different types of service are different. The following table lists the
parameters used to set admission thresholds for different types of service:
For example, the admission of a new AMR service in the uplink based on algorithm 2 will be
successful if the following condition is fulfilled:
Before the admission of the uplink ENU resource, if the uplink OLC algorithm switch
(UL_UU_OLC) is enabled, and the cell is in the OLC state triggered by the RTWP.
-If the Control RTWP Anti-interference function switch (RsvdBit1) is enabled, the system
checks whether the uplink equivalent user load proportion of the cell is lower than 40%. If it is
lower than 40%, the RNC accepts the access request. Otherwise, the RNC performs an admission
decision on the uplink ENU resource.
-If the Control RTWP Anti-interference function switch is disabled, the RNC rejects the access
request.
If the cell is in the overload congestion state in the uplink, the RNC rejects any new RAB.
The ENU of MBMS downlink control channels (MICH and MCCH) is reserved. Therefore,
the power-based admission for these channels is not needed.
The ENU of HSUPA downlink control channels (E-AGCH, E-RGCH, and E-HICH) is
reserved by DlHSUPARsvdFactor. Therefore, the power-based admission for these channels is
not required.
Algorithm 3 is similar to algorithm 1. The difference is that the estimated load increment in
algorithm 3 is always set to 0.
In accordance with the current cell load (uplink load factor and downlink TCP), the RNC
determines whether the cell load will exceed the threshold, with the estimated load increment set
to 0. If yes, the RNC rejects the request. If not, the RNC accepts the request.
CE is used to measure the channel demodulation capability of the NodeBs. On the RNC side, it
is referred to the NodeB credit. On the NodeB side, it is the channel element.
The resource of one equivalent 12.2 kbit/s AMR voice service, including 3.4 kbit/s signaling on
the Dedicated Control Channel (DCCH), is defined as one CE. If there is only 3.4 kbit/s
signaling on the DCCH, one CE is consumed. Channel elements provide either uplink or
downlink capacity for services. There are two kinds of CE. One is uplink CE supporting uplink
services, and the other is downlink CE supporting downlink services. Therefore, one 12.2 kbit/s
AMR voice service consumes one uplink CE and one downlink CE.
For details about local cell, local cell group, and capacity consumption law, refer to the 3GPP TS
25.433.
According to the capacity consumption laws of common and dedicated channels, the Controlling
RNC (CRNC) debits the amount of the credit resource consumed from or credits the amount to
the Capacity Credit (CC) of the local cell (or local cell group, if any) based on the SF. The
specific scenarios are the addition, removal, and reconfiguration of the common and dedicated
channels.
If the UL CC and the DL CC are separate, they are maintained separately in the local cell or
local cell group.
If the UL CC and DL CC are not separate, only the global CC is maintained in the local cell or
local cell group.
The consumption laws of CEs and the relation between CE and credit are listed in 0 and 0.
For the DCH service, the RNC uses the MBR to calculate the SF and searches 0 for the number
of consumed CEs.
For the HSUPA service, if the NodeB reports through its private interface that the dynamic CE
function of the cell is enabled, the RNC uses the GBR to calculate the spreading factor. If the
NodeB reports that the dynamic CE function is disabled, the RNC uses the MBR to calculate the
spreading factor. If the NodeB does not report whether the dynamic CE function is enabled, the
RNC determines whether to use the GBR or MBR to calculate the spreading factor, based on the
value of HsupaCeConsumeSelection. Then, the RNC searches 0 for the number of consumed
CEs.
UL 3.4 256 1 2
13.6 64 1 2
8 64 1 2
16 64 1 2
32 32 1.5 3
64 16 3 6
128 8 5 10
144 8 5 10
256 4 10 20
384 4 10 20
DL 3.4 256 1 1
13.6 128 1 1
Direction Rate (kbit/s) SF Number of CEs Consumed Corresponding Credits Consumed
8 128 1 1
16 128 1 1
32 64 1 1
64 32 2 2
128 16 4 4
144 16 4 4
256 8 8 8
384 8 8 8
As listed in 0 and 0, for each data rate and service, the number of UL credits is equal to the
number of UL CEs multiplied by 2. This is because the RESOURCE STATUS INDICATION
message over the Iub interface supports only integers. For example, a UL 32 kbit/s PS service
consumes 1.5 CEs. Then, the number of corresponding UL credits consumed is 3, an integer,
which can be carried in the RESOURCE STATUS INDICATION message.
There is no capacity consumption law for HS-DSCH in 3GPP TS 25.433, so certain credits are
reserved for HSDPA RAB, and credit admission for HSDPA is not needed.
6.4.2 Procedure of Admission Decision Based on NodeB Credit
When a new service tries to access the network, the admission decision based on NodeB credit is
implemented as follows:
For an RRC connection setup request, the credit resource–based admission is successful if the
current remaining credit resources of the local cell, local cell group (if any), and NodeB are
sufficient for RRC connection setup.
For a handover service, the credit resource–based admission is successful if the current
remaining credit resources of the local cell, local cell group (if any), and NodeB are sufficient for
the service.
For other services, the RNC has to ensure that the remaining credit of the local cell, local cell
group (if any), and NodeB does not exceed the value of UlHoCeResvSf (for the uplink) or
DlHoCeCodeResvSf (for the downlink) after admission of the new services.
The CE capabilities at the levels of local cell, local cell group, and NodeB are reported to the
RNC through the NBAP_AUDIT_RSP message over the Iub interface.
- The CE capability of local cell level indicates the maximum capability in terms of hardware
that can be used in the local cell.
- The CE capability of local cell group level indicates the capability obtained after the license
and hardware are taken into consideration.
- The CE capability of NodeB level indicates the number of CEs allowed to use as specified in
the license.
If the UL CC and DL CC are not separate, the credit resource–based admission is implemented
based on the total CC.
For details about resource-based admission at the Iub transport layer, see the Transmission
Resource Management Parameter Description.
When a new HSDPA service attempts to access the network, the algorithm admits the service if
the following conditions are met:
The number of HSDPA users in the cell does not exceed the maximum value specified by
MaxHsdpaUserNum.
The number of HSDPA users in the NodeB does not exceed the maximum value specified by
NodeBHsdpaMaxUserNum.
When a new HSUPA service attempts to access the network, the algorithm admits the service if
the following conditions are met:
The number of the HSUPA users in the cell does not exceed the maximum value specified by
MaxHsupaUserNum.
The number of the HSUPA users in the NodeB does not exceed the maximum value specified
by NodeBHsupaMaxUserNum.