You are on page 1of 7

1.1.

1 LOFD-001027 Active Queue Management (AQM)


Availability
This feature is
 applicable to Macro from eRAN2.0
 applicable to Micro form eRAN3.0
 applicable to Lampsite from eRAN6.0

Summary
This feature provides an approach for buffer optimization to interact with the TCP
protocol in a favorable manner and shorten the buffering delay.

Benefits
The Active Queue Management feature improves the end user service in different
ways. With AQM, where the buffer fill level is balanced to the UE data rate, the delay
is significantly reduced.

Description
In an interactive connection, the packet data to be transferred is typically characterized
by large variations, so the buffer is introduced to even out the variations. However, if
the buffer is filled up or an overflow situation takes place, it will result in loss of data
packets.
Currently, TCP as the main transport layer protocol is used on Internet. Packet loss is
regarded as link congestion by TCP, and TCP will correspondingly reduce the data
transmission rate. TCP protocol is also sensitive to round trip delay and it will take
actions differently in case just one packet is lost or if a burst of packets is lost. In case
of uncontrolled packet losses, it may take a considerable time for the data rate to
increase again, leading to poor radio link utilization and causing long delays for the
end user.
In addition, in case a user is performing parallel activities, e.g. FTP downloading and
web browsing, if the file downloading as a dominant stream would fill the buffers and
thereby cause a long delay for web browsing, before anything would happen when
clicking on a link.
The functionality of AQM is provided as an optimized buffer handling method, in
order to interact with the TCP protocol in a favorable manner and reduce the buffering
delay.
Operators can switch on/off the Active Queue Management function.

Enhancement
None

Dependency
None
1.1.2 LOFD-001029 Enhanced Admission Control
1.1.2.1 LOFD-00102901 Radio/transport resource pre-emption

Availability
This feature is
 applicable to Macro from eRAN2.0
 applicable to Micro form eRAN3.0
 applicable to Lampsite from eRAN6.0

Summary
This feature enables service differentiation when the network is congested to provide
better services for high-priority users.

Benefits
This feature provides operators with a method to differentiate users according to their
priority. High priority users can obtain the system resources in case of resource
limitation. In this way, operators can provide better service to those high priority users.

Description
Pre-emption is the function related to admission control and is the method for
differentiating services. It enables operators to provide different services by setting
different priorities, which will affect the user call setup success rate during the call
setup procedure. If there are not enough resources and a new call is not admitted to
access to the network, high priority user will have more chances to access to the
network than low priority users by pre-empting other low priority users.
The priority information is obtained from the E-RAB Level QoS Parameters including
ARP (Allocation / Retention Priority), in the message of ERAB SETUP REQUEST.
The eNodeB will assign the user priority based on ARP.
Pre-emption will take action if admitting a call fails due to lack of resource, including
S1 transmission resource and radio resource (for example, QoS satisfaction ratio based
admission check is failure). The service with the attribution of Pre-emption Capability
and Pre-emption Vulnerability indicates the service ability of pre-empt and pre-
emption vulnerability. The pre-emption capability indicates the pre-emption capability
of the request on other E-RABs, and pre-emption vulnerability indicates the
vulnerability of the E-RAB to preemption of other E-RABs.
In case of Signaling Radio Bearer (SRB), the pre-emption will not be triggered if
resource allocation for SRB fails. For the emergency call (e.g., E911) service, on
account of their very high priority, it always has the preemption capability. For the
SRB, emergency call and IMS signaling, they cannot be preempted.

Enhancement
 In eRAN6.0
This feature enables preemption when the number of UEs that have accessed cells
reaches the maximum number of UEs supported by an eNodeB. With this
enhancement, high-priority services and services that must be guaranteed to
comply with laws can preempt resources of common services and therefore get
better access.
An eNodeB admits all initially accessing UEs, allowing setup of Radio Resource
Control (RRC) connections for the UEs. Then during E-UTRAN radio access
bearer (E-RAB) setup, the eNodeB triggers preemption for high-priority services
and emergency calls, which are selected based on allocation/retention priority
(ARP) values. The eNodeB selects services to be preempted in the following
sequence: non-GBR services on unsynchronized UEs, non-GBR services on
synchronized UEs, and low-priority GBR services.

Dependency
 CN
This feature needs the core network to bring the ARP IE to eNodeB during E-
RAB assignment procedure so that eNodeB can get the service priority with those
E-RAB parameters.

1.1.3 LOFD-001054 Flexible User Steering


1.1.3.1 LOFD-00105401 Camp & Handover Based on SPID

Availability
This feature is
 applicable to Macro from eRAN2.2
 applicable to Micro form eRAN3.0
 applicable to Lampsite from eRAN6.0

Summary
This feature is used in the scenarios under which the operator wants to control the
mobility of an UE to make it camp on, redirect or handover to a suitable cell. The
priorities for the cell selection is predefined and configured to eNodeB through SPID
(Subscriber Profile ID for RAT/Frequency Priority).

Benefits
Operators can make its subscribers to camp in, redirect or handover to a suitable RAT
(a cell of LTE/UMTS/GSM) or frequency (a cell of LTE) based on the service
characteristics. For example, for a data centric subscriber, a LTE cell will be the more
suitable selection than an UMTS cell or a GSM cell; for a voice centric subscriber, a
GSM cell or an UMTS cell will be the more suitable selection than a LTE cell.

Description
The SPID is an index referring to user information (e.g. mobility profile, service usage
profile). The information is UE specific and applies to all its Radio Bearers.
This index is mapped by the eNodeB to locally defined configuration in order to apply
specific RRM strategies (e.g. to define RRC_IDLE mode priorities and control Inter-
RAT/inter frequency redirection/ handover in RRC_CONNECTED mode).
In RRC_IDLE mode, UE can camp in a cell with its suitable RAT or frequency.
In RRC_CONNECTED mode, when load balance or overload control triggers an
inter-frequency or Inter-RAT handover or redirection, eNodeB will choose a suitable
target from the cells according to the priorities indexed by its SPID. In addition, when
UE finish its service, eNodeB can release it into a suitable cell according to its SPID
priority. For UE without SPID, when overload happens, the UE could also be redirect
to a suitable cell according to common priority and overload information.
Thus, Operator can configure and push subscribers into the suitable cell according its
subscription. For example: a dongle user usually stays in a LTE high frequency band
for a high service rate; a VoIP user is prior to stay in a LTE low frequency band to
guarantee the continuous coverage.

Enhancement
 In eRAN3.0
When UE triggers an inter-frequency or inter-RAT handover, eNodeB can not
only choose a suitable target from the cells but also choose a HPLMN cell for
national roaming subscribers according to the priorities indexed by its SPID. For
national roaming subscribers, HPLMN cell will be more suitable to be selected
than roaming cell when entering HPLMN LTE or 3G coverage area through
connected mode handover.

Dependency
 CN
It depends on SAE to support the SPID configuration.
 Other features
The SPID-specific load-based handover policies function in this feature depends
on LOFD-001032 Intra-LTE Load Balancing or LOFD-001044 Inter-RAT Load
Sharing to UTRAN or LOFD-001045 Inter-RAT Load Sharing to GERAN.
The SPID-specific handover back to the HPLMN policies function in this feature
depends on LBFD-00201802 Coverage Based Inter-frequency or LOFD-001019
PS Inter-RAT Mobility between E-UTRAN and UTRAN.
 Others
GSM/UMTS network should support this functionality to avoid ping-pong
handover.

1.1.4 LOFD-001059 UL Pre-allocation Based on SPID


Availability
This feature is
 applicable to Macro from eRAN2.2
 applicable to Micro form eRAN3.0
 applicable to Lampsite from eRAN6.0

Summary
Operator can configure a suitable SPID (Subscriber Profile ID for RAT/Frequency
Priority) in core network for each UE. When an UE accesses to the network, its SPID
will be transmitted to the eNodeB, by which the eNodeB can enable or disable the UL
pre-allocation for the corresponding UE.
Benefits
With this feature, Operator can assign different UL pre-allocation capability for
different UE. UL pre-allocation is used when the cell is in a light load situation to
achieve the small latency for a certain UE.

Description
The SPID is an index referring to user information (e.g. mobility profile, service usage
profile). The information is UE specific and applies to all its Radio Bearers.
This index is mapped by the eNodeB to locally defined configuration in order to apply
specific RRM strategies.
Operator can configure a suitable SPID in core network for each UE. When an UE
accesses to the network, its SPID will be transmitted to the eNodeB, by which the
eNodeB can enable or disable the UL pre-allocation for the corresponding UE.
UL pre-allocation functionality allocates PUSCH RBs to the UE while the cell is in
light load situation; even the UE's sending buffer is empty. It gives the UE the
possibility to hit the sending chance quickly. For instance, this functionality can
accelerate the ACK of a DL RRC signaling message.
With UL pre-allocation, the sending delay of UE will be shortened, but the power
consumption of UE will increase. Operators can adjust the related parameters to get
compromise on the latency and power consumption.

Enhancement
None

Dependency
 CN
This feature depends on SAE to support the SPID configuration.

1.1.5 LOFD-001109 DL Non-GBR Packet Bundling


Availability
This feature is
 applicable to Macro from eRAN6.0
 applicable to Micro form eRAN6.0
 applicable to Lampsite from eRAN6.0

Summary
Delay-based downlink (DL) packet bundling introduces delay control and bundles DL
packets before transmission.

Benefits
Delay-based DL packet bundling offers the following benefits:
 This feature reduces PDCCH overheads and increases the PDCCH capacity.
 Compared with non-delay-based functions, this feature better meets the delay
requirements of best effort (BE) services and increases the eNodeB throughput in
hybrid service scenarios when both guaranteed bit rate (GBR) and non-GBR
services exist.

Description
Delay-based DL packet bundling primarily introduces delay control for BE services.
If the network load is light and the resources for control and traffic channels are
sufficient, delay-based DL packet bundling is not necessary. When the network load
increase, PDCCH packet delay will also increase and PDCCH transmission might be
congested. By bundling the PDCCH packets, eNodeB reduced the overhead on the
PDCCH transmission. This feature improves BE user experience , and increases the
eNodeB throughput in hybrid service scenarios at high load.
When the feature is used, average PDCCH packet delay of GBR services might
increase when it is mixed with non-GBR services. For non-GBR services, when
Proportional Fair (PF) scheduling is used small PDCCH packet delay might increase.

Enhancement
None

Dependency
None

1.2 Signaling Storm & Terminal Battery Life Saving


1.2.1 LOFD-070207 Intelligent Access Class Control
Availability
This feature is
 applicable to Macro from eRAN7.0
 applicable to Micro form eRAN7.0
 applicable to Lampsite from eRAN7.0

Summary
This feature enables access control in scenarios where a large number of users access
the network simultaneously, such as New Year party, concert, or gathering. Access
control is performed based on the cell congestion status to ensure smooth access of
UEs and prevent a sharp increase in signaling load.
This feature may affect user experience in network access. Therefore, it is
recommended that this feature be enabled only when a large number of users access
the network simultaneously.

Benefits
This feature offers the following benefits:
 Controls UE access to prevent a sharp increase in signaling load.
Relieves

You might also like