FDD Admission Control ZTE eReader-Browse

16/4/2020 FDD Admission Control (LR18+)
FDD Admission Control (LR18+)

Feature Guide
FDD Admission Control (LR18+)

Version Date Author Reviewer Notes
Update parameter.
V1.0 2018-09-30 Mou Jun Zhang Fan
Engineering Guide is reorganized.
V1.1 2019-03-30 Mou Jun Zhang Fan No technical change.
TABLE OF CONTENTS
1 Introduction
1.1 Related Feature List and License Control
1.2 Correlation with Other Features
2 Function Description
3 Technical Description
3.1 User Admission Control Procedure
3.1.1 Probability Rejection Based Admission Strategy
3.1.2 CPU utilization of CC board Based Admission Strategy
3.1.3 UE Number Based Admission Control Strategy
3.1.4 Privilege User Admission Control
3.2 Service Admission Control Procedure
3.2.1 Admission Queuing Strategy
3.2.2 Admission Control Based on the Number of Services
3.2.3 Admission Control Based on the Sufficiency of PRB Resources
3.2.4 Blind Redirection
4 Engineering Guide
4.1 Requirements
4.1.1 Hardware Requirements
4.1.2 EPC Requirements
4.1.3 Frequency Band, Frequency and Bandwidth Requirements
4.1.4 UE Requirement
4.1.5 Transmission Bandwidth Requirements
4.1.6 License Requirements
4.2 User Admission Control Configuration
4.2.2 CPU Utilization of CC board Based Admission Strategy Configuration
4.2.3 UE Number Based Admission Control Strategy Configuration
4.2.4 Privilege User Admission Control Configuration
4.3 Service Admission Control Configuration
4.3.1 Admission Queuing Strategy Configuration
4.3.4 Blind Redirection for Admission Failure Configuration
4.4 Data Synchronization
4.5 Deactivate feature
5 Related Counters, KPI and Alarms

5.1 Related Counters
5.2 Related KPIs
5.3 Related Alarms
6 Impact on Network
7 Abbreviations
8 References
127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 1/30
FIGURES
Figure 3‑1 User Admission Control Procedure

Figure 3‑2 Probability Rejection Based Admission Strategy
Figure 3‑3 CPU utilization Based Admission Strategy
Figure 3‑4 UE Number Based Admission Control Strategy
Figure 3‑5 Service Admission Control Procedure
Figure 3‑6 Admission Control Flow Based on the Number of Services
Figure 3‑7 PRB-Based Admission Control Procedure for GBR Services
Figure 3‑8 PRB-Based Admission Control Procedure for NGBR Services
Figure 4‑1 Admission for Probable Rejection Parameters
Figure 4‑2 CPU usage access control switch
Figure 4‑3 Threshold of RRC Connection user number and User reserved for handover
Figure 4‑4 Threshold of ENodeB User Number and Threshold of Board User Number
Figure 4‑5 The Cell Preset Allocations of Network RRC License
Figure 4‑6 Switch of Report RRC Connection Cause Value of Voice Service Parameter Configuration
Figure 4‑7 Deprioritisation Type and The Validity of Deprioritisation
Figure 4‑8 Switch of Admission Control and Preemption function
Figure 4‑9 ARP of emergency call configured by operator
Figure 4‑10 Admission queuing algorithm switch
Figure 4‑11 Threshold of active E-RAB number
Figure 4‑12 Admission based GBR parameters
Figure 4‑13 Admission based NGBR parameter
Figure 4‑14 Switch of Redirection for admit failure
Figure 4‑16 Admission Control Switch for Probable Rejection
Figure 4‑18 Admission control algorithm switch for GBR service
Figure 4‑19 Admission control algorithm switch for NGBR service
Figure 4‑20 Admission control switch for emergency call
Figure 4‑21 Switch of CSFB High Priority Admission
TABLES
Table 1‑1 Related Feature List and License Control

Table 1‑2 Correlation with Other Features
Table 4‑1 License Control for Admission
Table 4‑2 Admission for Probable Rejection Parameters Configuration Rule
Table 4‑3 CPU usage access control Parameters Configuration Rule
Table 4‑4 RRC Connection user number Admission Parameters Configuration Rule
Table 4‑5 Privileged Users Admission Parameters Configuration Rule
Table 4‑6 Admission queuing algorithm Parameters Configuration Rule
Table 4‑7 Active E-RAB number Admission Parameters Configuration Rule
Table 4‑8 PRB based GBR service Parameters Configuration Rule
Table 4‑9 PRB based NGBR service Parameters Configuration Rule
Table 4‑10 Redirection for admission failure Parameters Configuration Rule
Table 5‑1 Related Counters
1 Introduction
This document provides the introduction, technical descriptions, parameter configuration, counters, alarms, and validation procedure of the LTE FDD admission control
feature.
The parameters, alarms and counters in this document are the same as those of the latest software version when this document is released. To obtain the MO, parameters,
alarms, and KPIs of the existing software version, please refer to the product manuals of the existing software version.
This document is applicable to LTE FDD mode. "LTE" and "eNodeB" mentioned in this document respectively refer to "LTE FDD" and "LTE FDD-based eNodeB".
1.1 Related Feature List and License Control
Table 1‑1 Related Feature List and License Control
No Feature List Feature List Name License Technical part

No. Control or not
1 ZLF31-08-001 Radio Admission No 3.1
Control 3.2
2 ZLF31-08-014 Radio Admission N/A 3.1
Control
Enhancement
3 ZLF31-08-015 LTE Congestion N/A 3.1
Control
Enhancement
1.2 Correlation with Other Features
Table 1‑2 Correlation with Other Features

Feature ID Feature Name Required Mutually Impacted
Feature Exclusive Feature
Feature
ZLF31-08- Radio None None None
001 Admission
Control
ZLF31-08- Radio ZLF31-08-001 None None
014 Admission Radio
Control Admission
Enhancement Control
ZLF31-08- LTE Congestion ZLF31-08-001 None None
015 Control Radio
Enhancement Admission
Control
2 Function Description
Admission control is mainly to determine whether to admit new service requests in accordance with the requested resource requirements and current usage of cell
resources.
Admission control feature is applied in the following scenarios: RRC connection establishment, E-RAB setup, intra-eNodeB handover, X2 handover and S1 handover etc.
When receiving service setup requests, the admission control module will perform admission control in accordance with service’s QoS information and usage of cell
resources, for example, CPU usage of the CC board, and PRB usage of cell.
If the feature is enabled, the existing services will not be affected after new services access the system. Therefore, the system stability can be maintained and users' QoS
can be guaranteed. Additionally, the feature enables the system to admit services as many as possible if resources permit, which facilitates usage of system resources,
improves the system capacity and lowers operators' OPEX.
3 Technical Description
Admission control can be divided into user admission control and service admission control.
1. When a user requests to access the network, that is, the user requests to establish an RRC connection or be handed over to the network, the eNodeB performs the
user admission control procedure.
2. When the eNodeB needs to establish or modify services for users connected to the network, that is, to establish or modify an E-RAB for the UE, or process a handover
request, the eNodeB performs the service admission control procedure.
& Note:
When a user requests to be handed over to the eNodeB, the eNodeB allocates the resources required for the RRC connection and service bearer to the user, so the
eNodeB performs the user admission control procedure and service admission control procedure successively.
3.1 User Admission Control Procedure

When a new user requires to access the network, that is, require to setup RRC connection or handover request, eNodeB performs user admission control procedure as
shown below.
Figure 3‑1 User Admission Control Procedure
The principle for the above procedure is described as follows:

1. When eNodeB receives RRC Connection Request, first identify the access user type:
l If RRCConnectionRequest:EstablishmentCause is ’emergency’, the user is regarded as emergency call user;
l If RRCConnectionRequest:EstablishmentCause is ’highPriorityAccess’, the user is regarded as high priority user;
l If RRCConnectionRequest: EstablishmentCause is ’mo-VoiceCall-v1280’, the user is regarded as VoLTE user.
The emergency call user and high priority user are hereinafter referred to as a privileged user, and non privileged user and non VoLTE user are referred to normal
user.
2. Probability rejection is a cell access restriction function. When probability rejection switch AC.swchProRejAC is configured to “Open”, the eNodeB rejects access
requests of new users on a random basis in accordance with the specified rejection probability threshold. For details, refer to 3.1.1.
3. If the CPU resource is limited, the system rejects users from accessing the network. For details, refer to 3.1.2.
4. If the number of users connected to the network has reached the threshold, and user are non- privileged user, the eNodeB rejects new users from accessing the
network. If the user resources of privilege user or VoLTE user are limited, eNodeB implements RRC resource preemption. For details, refer to 3.1.3
5. For initial RRC access user, when user admission failure occurs, eNodeB sends RRCConnectionReject to UE and configures deprioritisationReq-r11 according to
deprioritisation type LoadControlCell.deprioritisation, and set T325 timer (delay time of deprioritisation) based on LoadControlCell.deprioritisationTimer.
Probability rejection based admission strategy is that some UEs are rejected probably based on cell load (UL/DL PRB usage rate). When the service traffic is large and
many UEs are to be admitted, if the number of UEs is not limited at the admission stage, the system load will rise sharply in a short time. Therefore, the probable rejection
based admission strategy is used to reject some UEs so that the system load will not rise rapidly and the system stability and availability can be improved.
Note:
Probable rejection admission adopts the formula of PRB usage used for load balancing, where the PRB usage of a cell is calculated based on the PRB of each cell and cell
throughput.
The detailed procedure is illustrated below:
Figure 3‑2 Probability Rejection Based Admission Strategy
If the parameter AC.swchProRejAC value is 1 (open), the probable rejection is enabled, the eNodeB decides whether to admit the user based on the uplink and downlink
loads of the cell. If the uplink PRB usage is lower than the corresponding threshold set by AC.proRejThrdUl, and downlink PRB usage is lower than the corresponding
threshold set by AC.proRejThrdDl, the eNodeB admits the user. Otherwise, the eNodeB generates a random number ‘rand’ (accurate to two decimal places) for the UE
which uniformly distributed in the range: 0 ≤ rand < 1. The eNodeB admits the user only if rand is smaller than AC.factorProRej. Otherwise, the user is rejected.
3.1.2 CPU utilization of CC board Based Admission Strategy
The eNodeB real-time monitors the CPU utilization of the CC board to learn about the system load. If the CPU utilization is high (>=95%, un-configurable), the eNodeB
rejects user access to guarantee system stability.
The following figure shows the procedure.
Figure 3‑3 CPU utilization Based Admission Strategy
If the parameter GlobleSwitchInformation.swichForCpuAC value is 1 (open), the CPU admission is enabled, the eNodeB decides whether to admit the user based on
the current CPU utilization, which is evaluated based on the system load. If the CPU utilization is lower than the specified threshold (95%, un-configurable), the eNodeB
admits the user access. Otherwise, the eNodeB rejects the user.
3.1.3 UE Number Based Admission Control Strategy

The system supports the application of different admission policies based on access types. The following figure shows the admission control procedure.
Figure 3‑4 UE Number Based Admission Control Strategy
l RRC license
A network operator can obtain eNodeB services by purchasing an RRC license. For details about the license mechanism, refer to the FDD License Feature Guide.
ZTE provides four levels of RRC license authorization: whole network- level, eNodeB-level, baseband-board level, and cell-level. A network operator can purchase
any one of them as required. For example, if the operator purchases a cell-level RRC license, the eNodeB restricts the number of online UEs in a cell within the
licensed number specified by the RRC license.
If the operator purchases the whole network -level RRC license, the eNodeB flexibly allocates the number of online UEs in each cell through the parameter
AC.cellPresetNetRRCLic as long as the sum of the numbers of online UEs allocated to all cells is less than the licensed number specified by the RRC license that
the operator purchases.
l UEs of emergency calls and high priority
For emergency cell UE and high priority UE, the eNodeB can ignore the corresponding admission threshold of the number of RRC-connected UEs to ensure high-
priority access of the UE. After the privileged user admission control function and the RRC user number preemption function are enabled, and when RRC user
number reaches the value (AC.ueNumThrd * (1 - AC.reservedHO), preemption can be triggered to release the resources for emergency call user and high priority
user.
Depending on whether an operator purchases an RRC license, the admission rules for the number of RRC-connected UEs are as follows:
1. If the operator purchases an RRC license, the admission rules for the number of RRC-connected UEs are as follows
(1) Non-emergency scenario. In normal cases (without an emergent event), the eNodeB checks whether the number of online UEs is restricted by the
corresponding admission threshold of the number of RRC-connected UEs configured by the network administrator. If yes, the eNodeB rejects the UE from
accessing the network; otherwise, the eNodeB checks whether the number of online UEs is restricted by the licensed number specified by the RRC license that
the operator purchases. If yes, the eNodeB rejects the UE from accessing the network; otherwise, it accepts the UE. The admission thresholds of the number
of RRC-connected UEs are as follows: the threshold of the number of RRC-connected UEs in a cell, configured through the parameter AC.ueNumThrd; the
threshold of the number of RRC-connected UEs on a baseband board, configured through the parameter ENBFunctionFDD.boardPermitRRCNum; and the
threshold of the number of RRC-connected UEs in an eNodeB, configured through the parameter ENBFunctionFDD.permitRRCNum.
(2) Emergency scenario. In an emergency case, for example, an earthquake, an operator can request to enable emergency license mode. In emergency license
mode, the eNodeB ignores the restriction of the RRC license that the operator purchases and the admission threshold of the number of RRC-connected UEs.
2. If the operator does not purchase an RRC license, the admission rules for the number of RRC-connected UEs are as follows:
The eNodeB checks whether the number of online UEs is restricted by the corresponding admission threshold of the number of RRC-connected UEs configured by
the network administrator. If yes, the eNodeB rejects the UE from accessing the network; otherwise, it accepts the UE. For details about the admission thresholds of
the number of RRC-connected UEs, refer to the above description. The admission rules vary with the access type of the UEs.
Depending on the access type, the admission rules for the number of RRC-connected UEs are as follows:
1. For a non-VoLTE UE: A cell reserves a certain percentage of the number of RRC-connected UEs for handover UEs and VoLTE UEs, and the reserved percentage is
configured through the parameter AC.reservedHO. Therefore, the actual admission threshold of the number of RRC-connected UEs in the cell is the result of the
following formula:
AC.ueNumThrd × (1 - AC.reservedHO).
2. For an incoming handover UE: Compared with a non-VoLTE UE, an incoming handover UE can use all RRC resources of a cell, and therefore, the actual admission
threshold of the number of RRC-connected UEs in the cell is the value of AC.ueNumThrd.
3. For a VoLTE UE: The eNodeB can instruct the UE to set the establishmentCause IE in an RRC CONNECTION REQUEST message to mo-VoiceCall-v1280 during the
initiation of MMTEL Voice access by containing the voiceServiceCauseIndication-r12 IE in a SIB2 message. In this way, the eNodeB can identify a VoLTE UE.
Compared with a non-VoLTE UE, a VoLTE UE can use all RRC resources of a cell, and therefore, the actual admission threshold of the number of RRC-connected
UEs in the cell is the value of AC.ueNumThrd. The parameter EUtranReselection.voiceServiceCauseIndSwch determines whether the eNodeB contains the
voiceServiceCauseIndication-r12 IE in a SIB2 message. When the RRC user number preemption function is enabled, and when the RRC number admission fails, the
resource can be released for the VoLTE user by triggering the preemption, and the access of the VoLTE user is preferentially guaranteed.
4. For a CA UE
- If the operator purchases an RRC license, the access attempt of a CA UE is counted as that of an RRC-connected UE on the PCell and the RRC license
applies. If an SCell is configured, the access attempt of the CA UE is counted as that of an RRC-connected UE on the SCell but the RRC license does not apply.
If all UEs in a network are CA UEs and an SCell is configured, the actual number of UEs accessing the network is decreased by half and just equal to the
licensed number specified by the RRC license.
- If the operator does not purchase an RRC license, the network administrator can configure the number of UEs that are allowed to access a cell through the
parameter AC.cellPresetNetRRCLic, which can be called a user-defined RRC license. The access attempt of a CA UE is counted as that of an RRC-connected
UE on the PCell and the user-defined RRC license applies. If an SCell is configured, the access attempt of the CA UE is counted as that of an RRC-connected
UE on the SCell but the user-defined RRC license does not apply. In other words, if AC.cellPresetNetRRCLic UEs are connected to the PCell, the remaining
(AC.ueNumThrd - AC.cellPresetNetRRCLic) RRC-connected UEs can be connected to only the SCell. If there is no CA UE in the network, or if the user-
defined RRC license is not used, the value of the parameter AC.cellPresetNetRRCLic can be set to its upper limit.
3.1.4 Privilege User Admission Control

For high priority access user and emergency call user, eNodeB will not perform RRC user resource limitation for these users. The high priority users are terminals of
access level of AC11~AC15, and the terminals configure RRCConnectionRequest->establishmentCause to ”highPriorityAccess”. When eNodeB receives RRC Connection
Request, eNodeB identifies high priority access user according to -”highPriorityAccess”.
When the RRC user resources are not sufficient, privilege users can normally access and policies are listed below:
- When Switch of Admission Control and Preemption for Privileged User AC.priUserACSwch is set to “open”, and RRC user number is larger than the value
(AC.ueNumThrd * (1 - AC.reservedHO)), perform RRC user preemption. Whenever the RRC user number preemption success or failure, the system admit the
UE access.
- When the parameter AC.priUserACSwch is set to “close”, the system will ignore the judgment for RRC user number and the privileged user access.
- When RRC Resource Preemption Function Switch AC.userNumPreemptSwch is set to “Open”, the RRC user number resources preemption will be enabled.
When the number of RRC connected users in a cell reaches the admission control threshold, the privileged users who are newly accessed or handed over,
VoLTE users will perform resource preemption for online low priority users.
l Selection strategy for users being preempted

(1) The following users cannot be preempted: emergency call user; high priority user; VoLTE and users carrying emergency bearing service.
(2) After excluding the users who cannot be preempted in the cell, select the users with lower priority or cell edge users as the preemptive ones in the remaining
users.
l Processing Strategy for users being preempted
1. If AC.userNumPreemptRedSwch is set to “Close”, eNodeB releases the RRC connection for the users being preempted;
2. If AC.userNumPreemptRedSwch is set to “Open”, eNodeB performs blind redirection for the users being preempted, and sort according to User Migration Priority
in High Load Scenarios (EUtranCellMeasurement.hlMigrtRATPriority) and frequency priority. The sorting policy is described as below:
(1) Select the system which UE supports and has highest priority as the target system. Go to Next step;
(2) Select the frequency which UE supports and has highest redirection priority as the target frequency. If there is available frequency, jump to Step 4; if
there is no available frequency, go to Next step;
(3) If there is no available frequency in the selected system, select the system with secondary priority as the target system and return to Step 2;
(4) Send the selected frequency to UE.
Note: if one system priority is 0, the redirection will not be performed to this system; if the redirection priority of one frequency is 0, redirection will not be
performed to this frequency.
3.2 Service Admission Control Procedure

When UE establishes/modifies E-RAB, or requests for access, eNodeB performs service admission control procedure as shown below:
Figure 3‑5 Service Admission Control Procedure
1. Service queuing: When multiple services request to be admitted concurrently, the system needs to determine the admission order in accordance with particular rules.
The eNodeB assigns a priority level to each service based on the QoS of each service, and the services with higher priority levels are admitted preferentially. For
details, refer to 3.2.1.
2. CSFB user service admission: The eNodeB does not perform judgment on service number restriction for CSFB users. For details, refer to 3.2.2
3. Emergency call service and the high priority service
When AC.priUserACSwch is set to “Close”, eNodeB will not perform special processing for emergency call service and the high priority service, and the services are
accessed whenever the resources are sufficient or not; when AC.priUserACSwch is set to “Open”, if the services are congested due to PRB resources limited,
eNodeB directly perform congestion control. For details about congestion control for privilege users, refer to FDD Congestion Control Feature Guide.
4. CPU resource limitation: If the CPU utilization is high (>=95%, un-configurable) the eNodeB rejects services. The services of the emergency call and the high priority
user are not limited by the CPU resources.
5. Maximum number of services: If the number of existing services reaches the threshold, the eNodeB rejects other services. For details, refer to 3.2.2. The services of
the emergency call and the high priority user are not limited by the CPU resources.
6. PRB resource insufficiency: The eNodeB monitors the uplink or downlink PRB usage of each cell in real time. If the uplink or downlink PRB usage is limited, the
eNodeB rejects services. For details, refer to 3.2.3.
7. Congestion control: if service congestion occurs due to insufficiency of resources (for example, uplink or downlink PRB), the eNodeB performs the congestion control
procedure. For details, refer to FDD Congestion Control Feature Guide.
8. Blind redirection: when the eNodeB detects that the default bearer failed to admit the user, the eNodeB redirects the user to a cell of another carrier frequency
through blind redirection. For details, refer to 3.2.4.
3.2.1 Admission Queuing Strategy
A UE may originate multiple service requests simultaneously. To guarantee the QoS requirements of all services, the eNodeB puts the concurrent services of the UE into a
queue, and executes the admission queuing strategy. Whether the strategy is enabled or not is determined by the switch.
1. If the parameter AC.switchForQueuing value is 0 (close), the service admission queuing is disabled, the eNodeB performs the admission control procedure in the
original service queue.
2. If the parameter AC.switchForQueuing value is 1(open), the service admission queuing is enabled, the eNodeB determines the admission priority of each service by
querying the database based on the service QoS and user class (gold, silver, or bronze). The service with the highest admission priority is first admitted. If multiple
services have the same admission priority (the admission priorities of GBR and NGBR services are different), the eNodeB preferentially admits the service with a
larger downlink GBR value (for GBR services) or admits the services in a random order (for NGBR services).
Note:
Default ARP levels: 1–5 (gold)
6–10 (silver)
11–15 (bronze)

If the number of existing services reaches the threshold, the eNodeB rejects other services. The following types of services have different admission control thresholds:
Figure 3‑6 Admission Control Flow Based on the Number of Services
l E-RAB license
A network operator can obtain eNodeB services by purchasing an E-RAB license. For details about the license mechanism, refer to the ZTE LTE FDD License
Feature Guide. ZTE provides two levels of E-RAB license authorization: whole network level, and cell level. A network operator can purchase one of them as required.
For example, if the operator purchases a cell-level E-RAB license, the eNodeB restricts the number of online UEs in a cell within the licensed number specified by the
E-RAB license.
If the operator purchases the network-wide-level E-RAB license, the eNodeB flexibly allocates the number of online E-RABs in each cell through the AC.rabThrd
parameter as long as the sum of the numbers of online E-RABs allocated to all cells is less than the licensed number specified by the E-RAB license that the operator
purchases.
l Emergency call service
If the QCI of the current service is equal to the value of the GlobalQoS.arpCfgforEMC parameter, the eNodeB regards the service as an emergency call service. The
services of the emergency call and the high priority user are not limited by the CPU resources.
l CSFB service
If the INITIAL CONTEXT SETUP REQUEST message sent by the MME to the eNodeB contains the CS Fallback Indicator IE, the eNodeB identifies the UE as a
CSFB UE. The eNode directly accepts the access request of the CSFB UE without implementing admission control based on the number of services.
l E-RAB license for an emergency scenario
In an emergency case, for example, an earthquake, an operator can request to enable emergency license mode. In emergency license mode, the eNodeB ignores the
restriction of the E-RAB license that the operator purchases and the admission threshold of the number of E-RAB-connected UEs.The admission threshold of E-RAB
numbers in each cell can be configured by AC.rabThrd parameter.
The eNodeB real-time monitors the PRB resources of each cell. If radio resource–based admission control is disabled, the system does not decide service admission
based on resource sufficiency. If PRB-based admission control is enabled, the eNodeB determines whether PRB resources are sufficient in the downlink and uplink
directions in order for the services. If the PRB resources are insufficient in any direction, the eNodeB rejects the service.
3.2.3.1 GBR Service
Figure 3‑7 PRB-Based Admission Control Procedure for GBR Services
If the parameter AC.switchForGbr value is 1, the radio resource–based admission control is enabled for GBR services. Still further, the eNodeB determines the resource
sufficiency as follows:
1. If the parameter AC.switchForGbr is set to 1(open) and AC.switchForGbrUl value is 1 (open), the uplink radio resource–based admission control is enabled for GBR
services. If the uplink PRB resources required for services are more than the remaining PRB resources in the cell, the eNodeB determines that the uplink PRB
resources are insufficient, and rejects the services. Otherwise, the eNodeB admits the access.
2. If the parameter AC.switchForGbr is set to 1(open) and the parameter AC.switchForGbrDl value is 1(open), the downlink radio resource–based admission control is
enabled for GBR services. If the downlink PRB resources required for services are more than the remaining PRB resources in the cell, the eNodeB determines that
the downlink PRB resources are insufficient, and rejects the services. Otherwise, the eNodeB admits the access.
3.2.3.2 NGBR Service
Figure 3‑8 PRB-Based Admission Control Procedure for NGBR Services
If the parameter AC.switchForNGBR value is 1, the radio resource–based admission control is enabled for NGBR services. Still further, the eNodeB determines the
resource sufficiency as follows:
1. If the parameter AC.switchForNGBR value is 1 and the parameter AC.switchForNGBRUl value is 1, the uplink radio resource–based admission control is enabled
for NGBR services. If the uplink PRB resources required for services are more than the remaining PRB resources in the cell, the eNodeB determines that the uplink
PRB resources are insufficient, and rejects the services. Otherwise, the eNodeB admits the access.
2. If the parameter AC.switchForNGBR value is 1 and the parameter AC.switchForNGBRDl value is 1, the downlink radio resource–based admission control is
enabled for NGBR services. If the downlink PRB resources required for services are more than the remaining PRB resources in the cell, the eNodeB determines that
the downlink PRB resources are insufficient, and rejects the services. Otherwise, the eNodeB admits the access.
3.2.4 Blind Redirection

For the RRC access user, if the service admission fails, the system sends an RRC release command to release the user. Based on admission failure redirection switch,
eNodeB performs the following release policies:
1. If the AC.swchOfRedi4ACFail parameter is set to 0, the blind redirection is disabled. The eNodeB releases the RRC connection upon admission failure, but does not
send any redirection information to the user through the RRC release message. The user may (if cell reselection is not performed) continue to initiate another access
attempt in the original serving cell.
2. If the AC.swchOfRedi4ACFail parameter is set to 1, the blind redirection is enabled. The eNodeB releases the RRC connection, and sends redirection information to
the user through the RRC release message. The eNodeB selects a proper carrier frequency configuration for the user based on the RAT (E-UTRAN/UTRAN) priority
configured on the OMC and reselection priority of the carrier frequency in the RAT. Upon receiving the RRC release message, the user is redirected to another cell
based on the carrier frequency configured by the eNodeB. For more details about blind redirection, refer to FDD Intra-RAT Connected Mobility Feature Guide.
4 Engineering Guide
4.1 Requirements
4.1.1 Hardware Requirements

Preemption feature in Initial RRC connection is not supported by BPL0 board.
4.1.2 EPC Requirements

No special requirements
4.1.3 Frequency Band, Frequency and Bandwidth Requirements
4.1.4 UE Requirement
ZLF31-08-014 Radio Admission Control Enhancement
UE: support R11 deprioritisation function
ZLF31-08-015 LTE Congestion Control Enhancement
UE: support R12 mo-VoiceCall-V1280 cause in RRC Connection Request.
4.1.5 Transmission Bandwidth Requirements
4.1.6 License Requirements
Table 4‑1 License Control for Admission
No Feature ID Feature License License Control Control

Name Document Name Level
Number
1 ZLF31-08- Radio SDR_F001_L LTE FDD E-RAB Network
001 Admission Number
Control
2 ZLF31-08- Radio SDR_F003_L LTE FDD RRC Network
001 Admission Connection User
Control Number
3 ZLF31-08- Radio LTE- LTE FDD E-RAB Cell
001 Admission FDD_ENB_F001 Number
Control
4 ZLF31-08- Radio LTE- LTE FDD RRC Cell
001 Admission FDD_ENB_F011 Connected User
Control Number (Cell)
5 ZLF31-08- Radio LTE- LTE FDD RRC eNodeB
Control Number(Board)
6 ZLF31-08- Radio LTE- LTE FDD RRC eNodeB
Control Number(eNodeB)
4.2 User Admission Control Configuration
4.2.1.1 Related parameters
Table 4‑2 Admission for Probable Rejection Parameters Configuration Rule
Parameter Range Default

SN Parameter Parameter explanation
name value value
Admission Control
Switch for Probable
Rejection: If Admission
Control Switch is open
Admission in one cell, eNodeB
Control should perform 0:close
1 AC.swchProRejAC Switch for Probable Rejection 0:Close
1:open
Probable Admission for initial UE
Rejection accessing in the cell;
Otherwise eNodeB don’t
perform Probable
Rejection Admission in
the cell.
Parameter Range Default
SN Parameter Parameter explanation
name value value
Uplink Threshold of
Probable Rejection
Admission: When the
Admission Control
Switch for Probable
Rejection is open in one
cell, and the uplink total
Uplink ratio of used PRB is
Threshold of higher than Uplink
2 AC.proRejThrdUl Probable Threshold of Probable [0-100] 70
Rejection Rejection Admission,
Admission eNodeB should perform
probable rejection
admission for initial UE
accessing in cell;
perform Probable
Rejection Admission in
the cell.
Downlink Threshold of
Probable Rejection
Admission: When the
Admission Control
Switch for Probable
Rejection is open in one
cell, and the downlink
Downlink total ratio of used PRB
Threshold of is higher than downlink
3 AC.proRejThrdDl Probable threshold of probable [0-100] 70
Rejection rejection admission,
Admission eNodeB should perform
probable rejection
admission for initial UE
accessing in the cell;
perform probable
rejection admission in
the cell.
Threshold of Probable
Rejection Admission:
When the Admission
Control Switch for
Probable Rejection is
open, and the uplink
total ratio of used PRB
is higher than uplink
threshold of probable
rejection admission, or
the downlink total ratio
of used PRB is higher
Probable
than downlink threshold [0,1]
Rejection
4 AC.factorProRej of probable rejection step 0.95
Admission
admission, eNodeB 0.05
Factor
creates a random value
in [0,1) for initial UE
accessing in the cell. If
the value is higher than
or equals to the
Probable Rejection
Admission Factor,
eNodeB should reject
the UE; Otherwise the
UE isn’t rejected by
Probable Rejection
Admission.
4.2.1.2 Parameter Configuration
Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Admission Control Switch for Probable
Rejection, click and set Admission Control Switch for Probable Rejection to Open[1], configure Uplink Threshold of Probable Rejection Admission, Downlink Threshold
of Probable Rejection Admission and Probable Rejection Admission Factor, Click to save configuration.
Figure 4‑1 Admission for Probable Rejection Parameters
4.2.2 CPU Utilization of CC board Based Admission Strategy Configuration
4.2.2.1 Related Parameters
Table 4‑3 CPU usage access control Parameters Configuration Rule
Parameter Parameter Range Default

SN Parameter
name explanation value value
The
parameter
indicates
whether
open CPU
usage rate
based
admission
CPU
control or
Usage 0:close
not. close:
1 GlobleSwitchInformation.swichForCpuAC Access 0:close
The CPU 1:open
Control
usage rate
Switch
based
admission is
closed;
open: The
CPU usage
rate based
admission is
open
Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > E-UTRAN Service Configuration>Global Switch> CPU Usage Access
Control Switchh, click and set CPU Usage Access Control Switch to Open[1], Click to save configuration.
4.2.3 UE Number Based Admission Control Strategy Configuration
Table 4‑4 RRC Connection user number Admission Parameters Configuration Rule
Parameter Parameter Default

SN Parameter Range value
name explanation value
The parameter
is the threshold
of RRC
Connection
user number. It
can be
configured
Threshold of according to
RRC the numbers of
1 AC.ueNumThrd 0-65535 800
Connection client
User Number purchase. But
the max value
configured will
not larger than
memory
capacity of one
cell on BPL
board.
The parameter
is the
maximum of
admission
RRC
connection
user to eNB. It
can be
configured
Threshold of
according to
2 ENBFunctionFDD.permitRRCNum ENodeB User [0,43200] 10800
the numbers of
Number
client
purchase. But
the max value
configured will
not larger than
memory
capacity of
main control
board.
The parameter
is the
maximum of
admission
RRC
connection
user to Board.
It can be
Threshold of
configured
3 ENBFunctionFDD.boardPermitRRCNum Board User [0,5400] 3600
according to
Number
the numbers of
client
purchase. But
the max value
configured will
not larger than
capacity of
BPL board.
User Reserved User Reserved
4 AC.reservedHO [0,100] 5
for Handover for handover
Parameter Parameter Default
SN Parameter Range value
The parameter
represents the
cell preset
allocations of
network RRC
License. When
the user
purchased the
eNB level, or
baseband
board level, or
cell level RRC
License, the
eNB shall
ignore this
parameter, and
not used into
the cell
admission
control
process. When
the user
purchased the
network level
RRC License
or doesn't
need purchase
any level RRC
License, the
The Cell eNB shall treat
Preset this parameter
5 AC.cellPresetNetRRCLic Allocations of as the user [0,1200] 1200
Network RRC preset cell
License allocations of
network RRC
License and
use it into the
cell admission
control
process.
About the
CA(Carrier
Aggregation)
user, in the
admission
control process
of PCell shall
be counted as
an RRC
connection
user and
consume an
RRC License,
and in the
admission
control process
of SCell shall
be counted as
an RRC
connection
user but not
consume RRC
License.
Indicates
whether UE is
requested to
Switch of
use the
Report RRC
establishment 0:close
Connection
6 EUtranReselection.voiceServiceCauseIndSwch cause mo- Open[1]
Cause Value 1:open
Voice Call for
of Voice
mobile
Service
originating
MMTEL voice
calls.
This parameter
indicates
whether the 0:Close,
Deprioritisation
7 LoadControlCell.deprioritisation current 1: Frequency 0:Close
type
frequency or 2: e-UTRAN
RAT is to be
de-prioritized.
This parameter
The validity of is used to limit
8 LoadControlCell.deprioritisationTimer enum(5,10,15,30) 5
deprioritisation the validity of
deprioritisation.
1. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control, and click and configure Threshold of
RRC Connection User Number , User Reserved for Handover and The Cell Preset Allocations of Network RRC License, Click to save configuration.
Figure 4‑3 Threshold of RRC Connection user number and User reserved for handover
2. Select Modify Area > Managed Element > Radio Parameter > LTE FDD, and click and configure Threshold of ENodeB User Number and Threshold of Board
User Number, Click to save configuration.
Figure 4‑4 Threshold of ENodeB User Number and Threshold of Board User Number
3. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control, and click and configure The Cell Preset
Allocations of Network RRC License, Click to save configuration.
Figure 4‑5 The Cell Preset Allocations of Network RRC License
4. Select Modify Area > Managed Element > Radio Parameter > Cell Reselection Configuration > E-UTRAN Cell Reselection, click and configure Switch of
Report RRC Connection Cause Value of Voice Service, Click to save configuration.
Figure 4‑6 Switch of Report RRC Connection Cause Value of Voice Service Parameter Configuration
5. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Load Control for Cell, and click and configure
Deprioritisation Type and The Validity of Deprioritisation, Click to save configuration.
Figure 4‑7 Deprioritisation Type and The Validity of Deprioritisation
4.2.4 Privilege User Admission Control Configuration
Table 4‑5 Privileged Users Admission Parameters Configuration Rule
Parameter Parameter Range

SN Parameter Default value
This
parameter
enables or
disables the
admission
control and
preemption
strategy for
privileged
users. If it is
set to Open,
the privileged
users need to
execute
admission
control based
on the
number of
users and the
Switch of PRB
Admission resources. If
Control the admission
and fails, the 0:close
1 AC.priUserACSwch 1:open
Preemption corresponding 1:open
for preemption
Privileged procedure is
Users triggered and
the privileged
users and
their services
are admitted
no matter
whether the
preemption
succeeds or
not. If it is set
to Close, the
privileged
users and
their services
are admitted
immediately
without the
execution of
admission
control.
This
parameter
enables or
disables RRC
resource
preemption. If
it is set to
Open, some
high-priority
RRC
users (for
Resource 0: Close.
example,
2 AC.userNumPreemptSwch Preemption 0:Close
VoLTE users) 1: Open.
Function
can preempt
Switch
the RRC
resources of
low-priority
users in the
case of
admission
failure due to
RRC resource
restriction.
This
parameter
enables or
disables RRC
resource
preemption
redirection. If
it is set to
Open, the
RRC low-priority
Resource users whose
Preemption resources are 0: Close.
3 AC.userNumPreemptRedSwch 0: Close.
Function preempted 1: Open.
Redirection are
Switch redirected. If it
is set to
Close, the
low-priority
users whose
resources are
preempted
are released
without
redirection.
Configuration
ARP for
Emergency
Service
Bearer by the
enum(Not
ARP of Operator.
Support,
Emergency When the
1, 2, 3, 4,
Call ARP value of
4 GlobalQoS.arpCfgforEMC 5, 6, 7, 8, Not Support
Configured a service for
9, 10, 11,
By UE is equal to
12, 13,
Operator the
14, 15)
parameter, so
the service
belongs to the
emergency
service.
This
parameter
indicates the
priority of user
migration
between
systems in
high load
scenarios. It
defines an
array with
seven
elements that
correspond to
the priorities
of the
EUTRA-FDD,
EUTRA-TDD,
GERAN,
User UTRA-FDD,
Migration UTRA-TDD,
5 EUtranCellMeasurement.hlMigrtRATPriority Priority in CDMA2000- [0..255] 0;0;0;255;0;0;0
High Load HRPD, and
Scenarios CDMA2000-
1xRTT
systems
respectively.
The priority of
each system
ranges from 0
to 255. A
higher value
indicates a
higher priority.
The default
value 0
indicates that
the RAT is not
selected as
the target
system for
user
migration.
1. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Admission Control Switch for
Emergency Call, click and set Switch of Admission Control and Preemption for Privileged Users, RRC Resource Preemption Function Switch, RRC Resource
Preemption Function Redirection Switch, Click to save configuration.
Figure 4‑8 Switch of Admission Control and Preemption function
2. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > Qos Configuration>Global Qos Parameter> ARP of Emergency Call Configured By
Operator, click and configure ARP of Emergency Call Configured By Operator, Click to save configuration.
Figure 4‑9 ARP of emergency call configured by operator
4.3 Service Admission Control Configuration
4.3.1 Admission Queuing Strategy Configuration
Table 4‑6 Admission queuing algorithm Parameters Configuration Rule

SN Parameter
Switch for queuing
based admission
Admission
control algorithm, 0:close
Queuing
1 AC.switchForQueuing which can determine 1:open
Algorithm 1:open
whether the queuing
Switch
algorithm is valid or
not.
Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Admission Queuing Algorithm Switch, Click
and set Admission Queuing Algorithm Switch to Open[1], Click to save configuration.
Table 4‑7 Active E-RAB number Admission Parameters Configuration Rule
Parameter Range
SN Parameter Parameter explanation Default value
name value
Parameter Range
SN Parameter Parameter explanation Default value
name value
The maximum number of
Threshold of established E-RAB that
1 AC.rabThrd Active E-RAB the cell can hold and the 0-65535 1600
Number QoS of all the service
can be guaranteed.
1. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Threshold of active E-RAB number, click
and configure Threshold of Active E-RAB number, Click to save configuration.
Figure 4‑11 Threshold of active E-RAB number
Table 4‑8 PRB based GBR service Parameters Configuration Rule

SN Parameter
Admission Switch of PRB based
Control GBR service
Algorithm admission control,
Switch for which can determine 0:close
1 AC.switchForGbr 0:close
Hardware whether the GBR 1:open
Resource admission control
Based GBR algorithm is valid or
Service not.
Switch of PRB based
GBR service
Admission
admission control
Control
algorithm in downlink,
Algorithm
which can determine 0:close
2 AC.switchForGbrDl Switch for 0:close
whether downlink 1:open
Downlink
PRB based GBR
PRB Based
service admission
GBR Service
control algorithm is
valid or not.
Switch of PRB based
GBR service
Admission
admission control
Control
algorithm in uplink,
Algorithm
3 AC.switchForGbrUl Switch for 0:close
whether uplink PRB 1:open
Uplink PRB
based GBR service
Based GBR
admission control
Service
not.
Table 4‑9 PRB based NGBR service Parameters Configuration Rule

SN Parameter
SN Parameter
Admission Switch of PRB based
Control NGBR service
Algorithm admission control,
Switch for which can determine 0:close
1 AC.switchForNGBR 0:close
Hardware whether the NGBR 1:open
Resource admission control
Based NGBR algorithm is valid or
Service not.
Switch of PRB based
NGBR service
Admission
admission control
Control
algorithm in
Algorithm
downlink, which can 0:close
Switch for
2 AC.switchForNGBRDl determine whether 0:close
Downlink 1:open
downlink PRB based
PRB Based
NGBR service
NGBR
admission control
Service
not.
Switch of PRB based
NGBR service
Admission
admission control
Control
algorithm in uplink,
Algorithm
3 AC.switchForNGBRUl Switch for 0:close
whether uplink PRB 1:open
Uplink PRB
based NGBR service
Based NGBR
admission control
Service
not.
1. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control > Algorithm Control Switch for Hardware
Resource Based GBR Service, Admission Control Algorithm Switch for Downlink PRB Based GBR Service, Admission Control Algorithm Switch for Uplink
PRB Based GBR Service, click and set Admission Control Algorithm Switch for Hardware Resource Based GBR Service, Admission Control Algorithm
Switch for Downlink PRB Based GBR Service, Admission Control Algorithm Switch for Uplink PRB Based GBR Service to Open[1], Click to save
configuration.
Figure 4‑12 Admission based GBR parameters
2. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control > Admission Control Algorithm Switch for
Hardware Resource Based NGBR Service, Admission Control Algorithm Switch for Downlink PRB Based NGBR Service, Admission Control Algorithm
Switch for Uplink PRB Based NGBR Service ,click and set Algorithm Switch for Hardware Resource Based NGBR Service, Admission Control Algorithm
Switch for Downlink PRB Based NGBR Service, Admission Control Algorithm Switch for Uplink PRB Based NGBR Service to Open[1], Click to save
configuration.
Figure 4‑13 Admission based NGBR parameter
4.3.4 Blind Redirection for Admission Failure Configuration
Table 4‑10 Redirection for admission failure Parameters Configuration Rule

SN Parameter
Switch for
queuing based
admission control
Switch of
algorithm, which 0:close
Redirection
1 AC.swchOfRedi4ACFail can determine 0:close
for Admit 1:open
whether the
Failure
queuing
algorithm is valid
or not.
1. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Switch of Redirection for Admit Failure,
click and set Switch of Redirection for Admit Failure to ”Open[1]”. Click to save configuration.
4.4 Data Synchronization

Check the configuration and click Data Synchronization button.
4.5 Deactivate feature

To deactivate Admission Control function, set related switch to “Close[0]”, and synchronize configuration data.
1. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Admission Queuing Algorithm Switch,
Click and set Admission Queuing Algorithm Switch to “Close[0]”,. Click to save configuration.
2. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Admission Control Switch for Probable
Rejection, click and set Admission Control Switch for Probable Rejection to “Close[0]”, Click to save configuration.
Figure 4‑16 Admission Control Switch for Probable Rejection
3. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN Service Configuration>Global Switch> CPU Usage Access Control
Switch, click and set CPU Usage Access Control Switch to “Close[0]” , Click to save configuration.
4. Select [Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control>Algorithm Control Switch for Hardware
Resource Based GBR Service, Admission Control Algorithm Switch for Downlink PRB Based GBR Service, Admission Control Algorithm Switch for Uplink
PRB Based GBR Service] ,click and set Algorithm Control Switch for Hardware Resource Based GBR Service, Admission Control Algorithm Switch for
Downlink PRB Based GBR Service, Admission Control Algorithm Switch for Uplink PRB Based GBR Service to “Close[0]”,Click to save configuration.
Figure 4‑18 Admission control algorithm switch for GBR service
5. Select [Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control>Algorithm Switch for Hardware Resource
Based NGBR Service, Admission Control Algorithm Switch for Downlink PRB Based NGBR Service, Admission Control Algorithm Switch for Uplink PRB
Based NGBR Service],click and set Algorithm Switch for Hardware Resource Based NGBR Service, Admission Control Algorithm Switch for Downlink
PRB Based NGBR Service, Admission Control Algorithm Switch for Uplink PRB Based NGBR Service to “Close[0]”. Click to save configuration.
Figure 4‑19 Admission control algorithm switch for NGBR service
6. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Admission Control Switch for
Emergency Call click and set Admission Control Switch for Emergency Call to “Close[0]. Click to save configuration.
Figure 4‑20 Admission control switch for emergency call
7. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Switch of CSFB High Priority Admission
click and set Switch of CSFB High Priority Admission to “Close[0]”. Click to save configuration.
Figure 4‑21 Switch of CSFB High Priority Admission
8. Select Modify Area > Managed Element > Radio Parameter > LTE FDD > E-UTRAN FDD Cell > Admission Control> Switch of Redirection for Admit Failure]
click and set Switch of Redirection for Admit Failure to“Close[0]”. Click to save configuration.
5 Related Counters, KPI and Alarms
5.1 Related Counters
Table 5‑1 Related Counters
SN Counter Number Descriptions

Number of Mt-Access RRC Establishment
1 C373200002
Failure due to ENODEB Admission Failure
Number of Mo-Signaling RRC Establishment
2 C373200006
Number of Mo-Data RRC Establishment
3 C373200010
Number of HighPriorityAccess RRC
4 C373200014 Establishment Failure due to ENODEB
Admission Failure
Number of Emergency RRC Establishment
5 C373200018
Number of Handover Failure Triggered RRC
6 C373200062 Re-establishment Failures due to ENODEB
Admission Failure
Number of Reconfig Failure Triggered RRC
7 C373200068 Re-establishment Failures due to ENODEB
Admission Failure
Number of Other Triggered RRC Re-
8 C373200074 establishment Failures due to ENODEB
Admission Failure
Number of inter-RAT Handover Failure
9 C373200099 Triggered RRC Re-establishment Failures due
to ENODEB Admission Failure
Number of delayTolerantAccess RRC
10 C373200122 Establishment Failure due to ENB Admission
Failure
Number of Initial QCI1 E-RAB Setup Failures
11 C373210201
due to ENODEB Admission Failure
12 C373210207
13 C373210213
14 C373210219
15 C373210225
16 C373210231
17 C373210237
18 C373210243
19 C373210249
Number of Additional QCI1 E-RAB Setup
20 C373210255
Failures due to ENB Admission Failure
21 C373210261
22 C373210267
23 C373210273
24 C373210279
25 C373210285
26 C373210291
27 C373210297
28 C373210303
Number of QCI1 E-RAB Modification Failure
29 C373210309
due to ENB Admission Failure
30 C373210315
31 C373210321
32 C373210327
33 C373210333
34 C373210339
35 C373210345
36 C373210351
37 C373210357
Number of E-RAB(QCI1) HO Incoming
38 C373210472
Admission Request
39 C373210473
Admission Request
40 C373210474
Admission Request
41 C373210475
Admission Request
42 C373210476
Admission Request
43 C373210477
Admission Request
44 C373210478
Admission Request
45 C373210479
Admission Request
46 C373210480
Admission Request
Number of E-RAB HO Incoming Admission
47 C373210481
Request
48 C373210482
Admission Fail
49 C373210483
Admission Fail
50 C373210484
Admission Fail
51 C373210485
Admission Fail
52 C373210486
Admission Fail
53 C373210487
Admission Fail
54 C373210488
Admission Fail
55 C373210489
Admission Fail
56 C373210490
Admission Fail
57 C373210491 Number of HO Incoming Admission Fail
Number of Initial E-RAB Setup Failures due to

58 C373505474
ENB Admission Failure
Number of Additional E-RAB Setup Failures
59 C373505482
Number of E-RAB Modification Failure due to
60 C373505490
ENB Admission Failure
Number of Context Setup Failure due to
61 C373220602
Admission Control Failure
Number of Context Modify Failure due to ENB
62 C373220608
Admission Failure
Number of Cell Admission Failure due to Not
63 C373404455
Enough RRC Resource in ENB
64 C373404456
Enough E-RAB Resource
65 C373404457
Enough DL PRB Resource
66 C373404458
Enough UL PRB Resource
Number of Cell Admission Failure due to Shut
67 C373404460
Down or Reset Cell
Number of Cell Admission Failure due to PHY
68 C373404462
Resource Allocated Failure
Number of Cell Admission Failure due to Other
69 C373404463
Reason
Number of Cell Admission Failure due to
70 C373404464
Probability Refuse
71 C373404465 Enough PRB Resource in Load Balance inter
Manufacturer
Number of RRC Connection Release By RRC
72 C373200168
Resource Preemption
Number of E-RAB Release due to RRC
73 C373210567
Resource preemption
Number of QCI1 E-RAB Release by ENB
74 C373210568 Through E-RAB Release Procedure due to
RRC Resource preemption
Number of Context Release by eNB due to
83 C373220677
5.2 Related KPIs

None
5.3 Related Alarms

None
6 Impact on Network
Impact on Equipment Performance
None
Impact on Network KPIs
1) RRC Establishment Success Rate (310500): when the RRC Number in the network is limited, the admission control function can reduce the RRC-connection success
rate. The lower the threshold of probable rejection admission is configured, the lower the RRC setup success rate will be.
2) E-RAB Setup Success Rate (310501): When the network resource is limited, the admission control function can reduce the E-RAB setup success rate.
7 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.
8 References
1. 3GPP TS 23.203, "Policy and charging control architecture"
2. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"
3. 3GPP TS 36.306, "User Equipment (UE) radio access capabilities"
4. 3GPP TS 36.321, "Medium Access Control(MAC) protocol specification"
5. 3GPP TS 36.331, "Radio Resource Control (RRC)"
6. 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
7. FDD Intra-RAT Connected Mobility Feature Guide.
8. FDD Inter-RAT Connected Mobility Feature Guide
9. FDD License Feature Guide
10. FDD Congestion Control Feature Guide.

FDD Admission Control ZTE eReader-Browse

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

FDD Admission Control ZTE eReader-Browse

Загружено:

Авторское право:

Доступные форматы

16/4/2020 FDD Admission Control (LR18+)

FDD Admission Control (LR18+)

FDD Admission Control (LR18+)

5 Related Counters, KPI and Alarms

Figure 3‑1 User Admission Control Procedure

Table 1‑1 Related Feature List and License Control

1.1 Related Feature List and License Control

Table 1‑1 Related Feature List and License Control

No Feature List Feature List Name License Technical part

1.2 Correlation with Other Features

Table 1‑2 Correlation with Other Features

3.1 User Admission Control Procedure

Figure 3‑1 User Admission Control Procedure

The principle for the above procedure is described as follows:

3.1.1 Probability Rejection Based Admission Strategy

The detailed procedure is illustrated below:

Figure 3‑2 Probability Rejection Based Admission Strategy

The principle for the above procedure is described as follows:

3.1.2 CPU utilization of CC board Based Admission Strategy

The following figure shows the procedure.

Figure 3‑3 CPU utilization Based Admission Strategy

3.1.3 UE Number Based Admission Control Strategy

Figure 3‑4 UE Number Based Admission Control Strategy

l UEs of emergency calls and high priority

3.1.4 Privilege User Admission Control

l Selection strategy for users being preempted

l Processing Strategy for users being preempted

3.2 Service Admission Control Procedure

Figure 3‑5 Service Admission Control Procedure

The principle for the above procedure is described as follows:

3. Emergency call service and the high priority service

3.2.1 Admission Queuing Strategy

Default ARP levels: 1–5 (gold)

3.2.2 Admission Control Based on the Number of Services

Figure 3‑6 Admission Control Flow Based on the Number of Services

l Emergency call service

l E-RAB license for an emergency scenario

3.2.3.1 GBR Service

Figure 3‑7 PRB-Based Admission Control Procedure for GBR Services

3.2.3.2 NGBR Service

Figure 3‑8 PRB-Based Admission Control Procedure for NGBR Services

3.2.4 Blind Redirection

4.1.1 Hardware Requirements

4.1.2 EPC Requirements

UE: support R11 deprioritisation function

ZLF31-08-015 LTE Congestion Control Enhancement

UE: support R12 mo-VoiceCall-V1280 cause in RRC Connection Request.

4.1.5 Transmission Bandwidth Requirements

4.1.6 License Requirements

Table 4‑1 License Control for Admission

No Feature ID Feature License License Control Control

4.2 User Admission Control Configuration

4.2.1 Probability Rejection Based Admission Strategy

4.2.1.1 Related parameters

Table 4‑2 Admission for Probable Rejection Parameters Configuration Rule

Parameter Range Default

4.2.1.2 Parameter Configuration

Figure 4‑1 Admission for Probable Rejection Parameters

4.2.2 CPU Utilization of CC board Based Admission Strategy Configuration

4.2.2.1 Related Parameters

Table 4‑3 CPU usage access control Parameters Configuration Rule

Parameter Parameter Range Default

4.2.2.2 Parameter Configuration

Figure 4‑2 CPU usage access control switch