ZGO-01-03-001 eMLPP FG 20101030 PDF

Operator Logo
ZGO-01-03-001
Feature Guide
eMLPP
ZGO-01-03-001
ZGO-01-03-001
Version
V1.00
Date
eMLPP
eMLPP
Author
2010-10-30
Approved By
Remarks
Not open to the Third Party
2010 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be
disclosed or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is
subjected to change without notice.
ZTE Confidential Proprietary
2010 ZTE CORPORATION. All rights reserved.
ZGO-01-03-001
eMLPP
TABLE OF CONTENTS
1
Feature Property ............................................................................................. 1
2
2.1
2.2
Overview ......................................................................................................... 1
Feature Introduction.......................................................................................... 1
Correlation with Other Features ........................................................................ 2
3
3.1
3.2
3.3
Technical Description .................................................................................... 2

A Interface Parameters Related to eMLPP ....................................................... 2
eMLPP Call Setup Flow .................................................................................... 4
eMLPP Handover Flow ..................................................................................... 7
4
4.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4
Parameter Configuration and Descriptions .................................................. 8

Parameter List .................................................................................................. 8
Parameter Configuration ................................................................................. 10
eMLPP Priority Configuration (ZTE CN).......................................................... 10
Reserved Channel Configuration .................................................................... 11
Queuing and Preemption Strategy Setting ...................................................... 15
Channel Allocation Strategy Setting................................................................ 24
5
5.1
5.2
5.3
Engineering Guide and Configuration Principle......................................... 25

Application Scenarios ..................................................................................... 25
Configuration Principle .................................................................................... 25
Recommendation ........................................................................................... 26
6
6.1
6.2
Related Counters and Alarms ...................................................................... 27

Related Counters ............................................................................................ 27
Related Alarms ............................................................................................... 33
Abbreviations................................................................................................ 33
Reference Document .................................................................................... 33
II
ZGO-01-03-001
eMLPP
FIGURES
Figure 3-1 Flow of Handling Channel Acquisition Failure in Local Cell ................................. 6
Figure 3-2 eMLPP Handover Flow ....................................................................................... 7
Figure 4-1 BSC Configuration ............................................................................................ 12
Figure 4-2 Cell Configuration ............................................................................................. 14
Figure 4-3 Module Parameters ........................................................................................... 16
Figure 4-4 Configuration at BSC Level ............................................................................... 17
Figure 4-5 Configuration at BSC Level ............................................................................... 17
Figure 4-6
Cell Switch ...................................................................................................... 18
Figure 4-7 ............................................................................................................................. 18

Figure 4-8 ............................................................................................................................. 19
Figure 4-9 ............................................................................................................................. 19
Figure 4-10 ........................................................................................................................... 20
Figure 4-11 ........................................................................................................................... 20
Figure 4-12 Switch of eMLPP Strategy............................................................................... 21
Figure 4-13 Selection of Preemption Target ....................................................................... 24
Figure 4-14 Channel Allocation Strategy ............................................................................ 25
TABLES
Table 3-1 PIE definition ........................................................................................................ 2
Table 3-2 Priority BIT Definition............................................................................................ 3
Table 3-3 Extra information definition ................................................................................... 3
Table 3-4 Octet 3 is coded ................................................................................................... 4
Table 4-1 Parameter List ...................................................................................................... 8
Table 6-1 Counter list ......................................................................................................... 27
III
Document Title
Feature Property
iBSC version: [iBSC V6.20]
BTS version: [applicable for all SDR BTS versions]
Attribute: [optional function]
NEs involved
NE Name
Involved or Not
MS
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Special Requirement
Dependency: [None]
Mutual exclusion: [None]
Remarks: None
Overview
2.1
Feature Introduction
In the 3GPP protocol, the enhanced Multi-Level Precedence and Preemption service
(eMLPP) is a supplementary service provided by the GSM system. The eMLPP service
involves multiple NEs, such as BSC, MSC, and HLR.
After the service is provisioned, mobile subscribers are differentiated by different priority
levels. The system allocates channel resources by following the principle of higher
priority, easier network access. Therefore, based on the priority configuration, the
high-priority MS has obvious advantages in call connection setup ability and call
interruption prevention ability. When the voice service channels are scarce, high-priority
call may preempt the resources of low-priority calls.
Generally, the eMLPP service contains the following three parts:
2010ZTE Corporation. All rights reserved.
Document Title
Queuing and preemption
When the network is lack of radio channel resource, calls are put in the queue based on
the priority level. Once idle resources are available, high-priority users can access first.
After preemption is enabled, the high-priority user may preempt resources originally
allocated to low-priority calls. The preemption involves forced handover and forced
release.
2
Reserve channels for high-priority users;
Reserve channels for users of specified priority level. The reserved channels will be used
by the high-priority users at the time of assignment and handover.
3
Configure different channel allocation policies based on the priorities of the users.
You can configure different channel allocation policies for users of different priorities.
2.2
Correlation with Other Features

ZGF05-09-006 Co-BCCH: If the handover from sub-cell 2 to sub-cell 1,is
handover, the eMLPP preemption flow is used.
emergency
ZGF05-02-005 Directed Retry: As another mode to obtain resources during channel

congestion, it is considered in enhanced eMLPP function.
ZGF05-09-009 Enhancement on Channel Allocation: The reserved channels involved in
the eMLPP and the policy of allocating channels according to priority are the factors that
must be considered in the enhancement on channel allocation. The channel allocation
methods are described in <Enhancement on Channel Allocation Feature Guide>.
Technical Description
3.1
A Interface Parameters Related to eMLPP

According to 3GPP 48.008, the MSC carries call priority parameters in A interface
messages ASSIGNMENT REQUEST and HANDOVER REQUEST. Different operators
may have different parameter setting modes.
Table 3-1 defines the priority (PIE (Priority Information Element.)) segment.
Table 3-1
8
PIE definition
Element identifier
1
octet 1
Document Title
Length
octet 2
Priority
octet 3
Table 3-2 lists the definition of priority bits.
Table 3-2
Priority BIT Definition
spare
pci
priority level
qa
pvi
octet 3
Priority Level (PL) occupies 4 bits and defines 15 user levels.

6 5 4 3 (bit)
0000
spare
0001
priority level 1 = highest priority
0010
priority level 2 = second highest priority
::::
1110
priority level 14 = lowest priority
1111
priority not used
Other parameters are defined as follows:

Preemption capability indicator (PCI) identifies whether the call can preempt resources of
other calls;
Preemption vulnerability indicator (PVI) identifies whether the resources of the call can be
preempted by other calls;
Queuing allowed indicator (QA) identifies whether this call allow queuing.
The value of these parameters includes 1 (allow) and 0 (prohibit).
According to 3GPP 48.008, for inter BSC handover, the Extra information part in Old BSS
to New BSS Information element of the HANDOVER REQUIRED message sent by
source BSC to MSC carries PREC parameter, which indicates whether recommend
preemption to the target BSC.
Table 3-3
Extra information definition
Document Title
Field Element identifier

Length
Table 3-4
octet 1
octet 2
octet 3
Octet 3 is coded
6
Spare
3
UEprob
2
lcs
1
prec
octet 3
PREC (Preemption Recommendation): identifies whether source BSC recommends the

handover to preempt other calls .1 means recommend, 0 means not recommend.
3.2
eMLPP Call Setup Flow

When a user initiates a call or serves as a callee, the MSC sends the ASSIGNMENT
REQUEST message with the PIE parameter to the BSC. The following describes the flow
of speech channel allocation by the BSC:
First try to allocate
an idle TCH channel in the local cell:
Check the PriorityLevel of MS. If PriorityLevelPriThreshold, it means that the service can
occupy the reserved channel. Check the parameter RsvChanFirst to judge whether the
service should occupy the reserved channel or non-reserved channel. When allocating
the reserved channels, check whether the local cell has reserved channels in reference
to parameter EMLPPThs.
When channel acquisition fails, the flow is as follows:
1
Judge whether allow forced handover:

i
If ForcedHoInd_0=1, forced handover is allowed. In this case, go to step 2.
ii
If ForcedHoInd_0=0, forced handover is allowed. In this case, go to step 4.
Judge whether allow forced queue:

i
If QueueInd_0=1, queue is allowed. In this case, go to step 3.
ii
If QueueInd_0=0, queue is not allowed. In this case, go to step 4. Forced

handover needs queue at the same time. Forced release does not need queue.
Search for forced handover object. The object must have a lower priority level than
the user implementing forced handover, its PVI flag, channel type, and frequency
band must meet the requirement, and have adjacent cells meeting lowest handover
level.
i
If the forced handover object is found, trigger handover and go to step 7.
ii
If the forced handover object is not found, go to step 4.
Document Title
Judge whether the cell parameter configuration allows forced release:

i
If PreemptionInd_0=1, forced release is allowed. In this case, go to step 5.
ii
If PreemptionInd_0=0, forced release is not allowed. In this case, go to step 6.
Search for forced release object. The object must have a lower priority level than the
user implementing forced release, its PVI flag, channel type, and frequency band
must meet the requirement.
i
If the forced release object is found, wait for the system to allocate forcibly
released channel. The flow ends.
ii
If the forced release object is not found, go to step 6.
Judge whether the cell parameter configuration allows queue:

i
If QueueInd_0=1, queue is allowed. In this case, go to step 7.
ii
If QueueInd_0=0, queue is not allowed. Channel acquisition fails and the flow
ends.
Enter the queue to wait for channel allocation.

i
If channel is acquired before the timer expires, MS successfully acquires the

channel. In the case, the flow ends.
ii
If no channel is acquired before the timer expires, go to step 8.
Judge whether the cell parameter configuration allows forced release:

i
If PreemptionInd_0=1, forced release is allowed. In this case, go to step 9.
ii
If PreemptionInd_0=0, forced release is not allowed. Channel allocation fails

and the flow ends.
Search for forced release object by using the policy in step 5.

i
If the forced release object is found, wait for the channel allocated after being
forcibly released. The flow ends.
ii
If the forced release object is not found, MS fails to acquire channel and the flow
ends.
The previous process is shown in figure 3-1.
Document Title
Figure 3-1
Flow of Handling Channel Acquisition Failure in Local Cell
Channel allocation
fails due to cell
congestion
Allow forced
handover?
Yes
No
No
Yes
No
Find forced
release
object?
Allow
queuing?
Yes
Allow forced
release?
No
No
Allow
queuing
Yes
Implement
forced release
to acquire
channel
Find forced
handover
object?
Yes
Forced
handover object
attempts
handover
Enter the
queue
Acquire
channel before
queue timer
expires
Yes
No
Allow forced
release?
Yes
Yes
Channel
acquisition
succeeds
Find forced
release
target
No
No
Channel
acquisition
fails
Yes
Implement
forced release
to acquire
channel
Document Title
3.3
eMLPP Handover Flow

The handover in the BSC includes intra-cell handover, inter-cell handover, inter-BSC
handover out, and inter-BSC handover in.
For the handover of users with high priority, besides system parameter , the handover
causes also decide whether to implement preemption. Classified by handover cause,
handover has two types. One is rescue handover (also called emergency handover),
such as quality handover and level handover. If such type of handover is not performed,
call drop may occur. The other is non-rescue handover, including PBGT handover,
handover from the first sub cell to the second sub cell (the handover from the second sub
cell to the first sub cell serves as a rescue handover). For details, please refer to
ZGF05-09-006 Co-BCCH. BSC performs different measures for handling these two types
of handover. For non-rescue handover, the system does not implement preemption if the
target cell does not have available channels. For rescue handover, if the target cell has
no idle channel, like the preemption in allocation process, the system attempts forced
handover and forced release on target cell based on parameter setting and PIE to
acquire channels.
Intra-cell emergency handover has only one target cell. The preemption process is the
same as that in allocation process. Inter-cell handover has multiple target cells and they
need to be applied for channel attempt one by one. When the system fails to allocate
channels for all internal candidate target cells and no other external candidate cells are
available, the system attempts the preemption to acquire channels.
The inter-cell handover flow has 2 stages:
1
BSC does not start the preemption process but applies for channels in the target
cells one by one. If the channel allocation fails in the target cells, the system does
not resort to forced handover, forced release and queuing. According to the
parameter PriorityLevel, the system decides whether to allocate reserved channels,
and selects the channel priority selection strategy by PriorityLevel when BSC
decides to allocate the unreserved channels.
If no channel is allocated after the system has tried the inner cells in the top of the
cell table and no outer cells are available, the system starts the preemption process
and tries the target cell once again. The system tries the preemption and queuing to
obtain a channel in the target cell according to the settings (QueueInd_1,
PreemptionInd_1, and ForcedHoInd_1) of the parameters of the target cells, as
shown in Figure 2. The processing in the target cell is similar to the preemption flow
of the call setup flow mentioned in Section 3.2.
Figure 3-2 shows the inter-cell handover flow.

Figure 3-2
eMLPP Handover Flow
Document Title
Inner
target cell
1
Call initiating
handover
Apply channel (preemption not

recommended)
Return channel not available
Apply channel (preemption recommended)
Return channel available or Proceeding
Inner
target cell
2
In case that outer candidate cells are available during handover, if all target cells before
the outer cells fail to apply for channels during the first resource application, that is,
preemption not recommended, BSC does not attempt to acquire channel through
preemption among inner cells but starts external handover. Based on whether the
handover is a rescue handover, BSC transmits the PREC flag, which indicates whether
preemption is recommended, to target BSC through the OLD BSC TO NEW BSC
parameter in HANDOVER REQUIRED message. The target BSC performs channel
preemption according to this parameter.
During inter-BSC handover, the target BSC decides whether to perform preemption
according to parameter configuration, PCI flag, and the PREC flag in OLD BSC TO NEW
BSC information element. The preemption process is the similar to that described
section 3.2. The difference is that different control parameters are used, including
QueueInd_1, PreemptionInd_1, and ForcedHoInd_1.
Parameter Configuration and

Descriptions
4.1
Parameter List
Table 4-1
Parameter List
No.
Parameter Name
Configured in
Document Title
PriThreshold
Figure 5
RsvChanFirst
Figure 5
EMLPPThs
Figure 5
EMLPPThs
Figure 6
UseCellEmlppThs
Figure 6
AssQueEnable
Figure 7
AssPreEmpt
Figure 7
HoQueEnable
Figure 7
HoPreEmpt
Figure 7
10
QueueIndAss
Figure 8
11
QueueIndHo
Figure 8
12
PreemptionIndAss
Figure 8
13
PreemptionIndHo
Figure 8
14
ForcedHoIndAss
Figure 8
15
ForcedHoIndHo
Figure 8
16
QueueInd_0
Figure 9
17
QueueInd_1
Figure 9
18
PreemptionInd_0
Figure 9
19
PreemptionInd_1
Figure 9
20
ForcedHoInd_0
Figure 9
21
ForcedHoInd_1
Figure 9
22
AssPreemptStrategy
Figure 10
23
HoPreemptStrategy
Figure 10
24
AssForcedHoTry
Figure 10
25
HoForcedHoTry
Figure 10
26
AssForcedRelTry
Figure 10
27
HoForcedRelTry
Figure 10
28
AssPreemTimer
Figure 10
29
HoPreemTimer
Figure 10
30
AssForceRelTimer
Figure 10
31
HoForceRelTimer
Figure 10
32
AssForceHoInterval
Figure 10
33
HoForceHoInterval
Figure 10
34
AssForceRelInterval
Figure 10
35
HoForceRelInterval
Figure 10
36
RmsT11
Figure 11
37
RmsTqHo
Figure 11
38
ForceHoWaitEmergServiceIPrio
Figure 11
39
ForceRelWaitEmergServiceIPrio
Figure 11
40
LowestPriority
Figure 11
Document Title
41
Longcallduration
Figure 11
42
ForceHoPenalty
Figure 11
4.2
Parameter Configuration
4.2.1
eMLPP Priority Configuration (ZTE CN)

Set priority for MS through MSC and HLR. Note that there are 15 RAM priority levels (1 ~
14 + None) at MSC side, which correspond to the previously mentioned 15 priority levels.
At HLR side, however, only 4 priority levels (L1~L4; LA and LB are internally used priority
levels and therefore are excluded here). In this case, the system should select four RAB
priority levels from the 15 options to set up corresponding relation with the service
priorities at HLR side, and then set priority levels on HLR for MS. That means, only four
priority levels can be set to users in ZTE system.
4.2.1.1
Configuration at MSC side

Choose Service Data Configuration> RAB Configuration>RAN Service Priority
on MSCSERVER and choose the RAM priority (eMLPP priority) corresponding to
services on HLR:
10
Document Title
Configure PVI, PCI, and QA parameters in PIE information element.

In addition, choose Service Data Configuration> VLR Configuration>Services
supported by VLR and select Support enhanced multi-level precedence and
pre-emption service to enable the function of priority access.
4.2.1.2
Configuration at HLR side

For mobile phone numbers required for priority access, this service needs to be enabled
through IMSI. The procedures for configuring the parameters in HLR are as follows:
Choose Supplementary Service ->eMLPP and set priorities from 1 to 4. The highest
level of eMLPP is the highest level of this the user. For example, if the highest level of the
user is 2, the default priority can be a level among 2, 3, and 4. Generally, the highest
priority is configured to be the same with the default priority.
4.2.2
Reserved Channel Configuration

The reserved channel is used for users with certain high priorities during allocation and
handover. Currently, only TCH/F channel can be set as reserved channel.
4.2.2.1
Configuration at BSC Level

To configure channel reservation at BSC level, in configuration resource tree, choose
OMCGERAN SubnetworkBSC Managed ElementConfig Set and double-click
BSC Function. The BSC Function window is displayed at right. Select the Channel
Allocation Control Params tab, as shown in the following figure:
11
Document Title
Figure 4-1
BSC Configuration
Configure the following parameters:

User Priority for EMLPP: indicates the priority threshold for users to occupy reserved
channel. A user can occupy the reserved channel only when its priority level is lower than
the threshold.
Reserved channel first: indicates whether the system allocates reserved channel or
non-reserved channel for users meeting priority requirement.
EMLPP channel reserved threshold: indicates the proportion of reserved channels in a
cell. If the result of calculation according to the rate is greater than 0 and smaller than 1,
then one channel is reserved.
Full name
Reserved Channel First
Abbreviation
RsvChanFirst
3GPP name
3GPP reference
Description
The selection order of reserved channel and non-reserved

channel
Managed object
BSC
Value Range
Yes/No
Unit
None
Default value
Yes
Related functions
ZGF05-25-017
eMLPP
12
Document Title
Related parameters
Related interfaces
Full name
EMLPP channel reserved threshold
Abbreviation
EMLPPThs
3GPP name
3GPP reference
Description
When eMLPP service is used, the system may set certain

reserved channels. If the result of calculation according to
the rate is greater than 0 and smaller than 1, then one
channel is reserved.
Managed object
BSC
Value Range
0 ~ 100
Unit
Default value
Related functions
ZGF05-25-017
Related parameters
Related interfaces
Full name
4.2.2.2
eMLPP
User Priority for EMLPP
Abbreviation
PriThreshold
3GPP name
3GPP reference
Description
When eMLPP service is used, the system may set certain

reserved FR channels. This parameter specifies the lowest
priority level to use reserved channel.
Managed object
BSC
Value Range
1 ~ 15
Unit
None
Default value
Related functions
ZGF05-25-017
Related parameters
Related interfaces
eMLPP
Configuration at Cell Level

The rate of reserved channel can also be configured at cell level.
13
Document Title
In configuration resource tree, choose OMCGERAN SubnetworkBSC Managed

ElementConfig SetBSC FunctionSite ConfigSite and double-click Cell. The
Cell window is displayed at right. Select the Other Params, as shown in the following
figure:
Figure 4-2
Cell Configuration
Full name
Use cell EMLPP Threshold
Abbreviation
UseCellEmlppThs
3GPP name
3GPP reference
Description
This parameter defines whether to use eMLPPThs. If yes,

you shall select cell property, otherwise to select BSC
property.
Managed object
Cell
Value Range
Yes/No
Unit
None
Default value
No
Related functions
ZGF05-25-017
Related parameters
Related interfaces
Full name
eMLPP
Reserved rate of EMLPP
14
Document Title
4.2.3
Abbreviation
EmlppThs
3GPP name
3GPP reference
Description
This parameter defines eMLPP channel reserved time, that

is, the proportion of eMLPP channel in all available channels
in the cell. If the calculation result is greater than 0 and
smaller than 1, then one channel is reserved.
Managed object
Cell
Value Range
Yes/No
Unit
None
Default value
No
Related functions
ZGF05-25-017
Related parameters
Related interfaces
eMLPP
Queuing and Preemption Strategy Setting

Preemption has two modes: forced handover and forced release. Forced handover
means that channel is acquired through the handover of users with low priority to other
cells. Force release means that channel is acquired through the release of the calls from
users with low priority.
4.2.3.1
Switch of Queuing and Preemption

1. Configuration at Module Level
In the Configuration Resource Tree, right-click OMCGERAN SubnetworkBSC
Managed ElementConfig SetBSC Function and choose Set System Control
Parameteroperation control parameters, as shown in the following figure
15
Document Title
Figure 4-3
Module Parameters
As shown in the following figure, you can set whether to support assign/handover queue
and assign/handover preemption. If they are set as No, the eMLPP configurations at BSC
level and cell level are invalid.
2. Configuration at BSC Level
In the version R8.2, the eMLPP switch at BSC level is added. Double-click OMC
GERAN SubnetworkBSC Managed ElementConfig Set and select BSC Function.
In the displayed BSC Function window at right, select the EMLPP Set tab.
There are three values for queue, forced handover, and forced release. They are:
allowed, not allowed, and According to the Cell, as shown in the following figure:
16
Document Title
Figure 4-4
Pay attention to the following points:

1. The value of the functional switch is contained in R_EMLPP table. 0 means disable, 1
means enable, and 2 means refer to cell configuration.
2. The settings of BSC-level switch are also shown in the printed result:
Figure 4-5
3. Configuration at Cell Level

In configuration resource tree, double-click OMC GERAN Subnetwork BSC
Managed ElementConfig SetBSC FunctionSite ConfigSite and select Cell.
In the displayed Cell window at right, select the Service Process Additional Params
tab.
17
Document Title
Figure 4-6
Cell Switch
Full name
Queue allowed when assign
Abbreviation
QueueInd_0
3GPP name
3GPP reference
Description
The parameter decides whether queuing is allowed in the

process of assignment when there is no channel available in
the cell.
Managed object
Cell
Value Range
Yes/No
Unit
None
Default value
No
Related functions
ZGF05-25-017
Related parameters
Related interfaces
eMLPP
Figure 4-7
Full name
Queue allowed when handover
Abbreviation
QueueInd_1
3GPP name
3GPP reference
Description
The parameter decides whether queuing is allowed in the

process of handover when there is no channel available in
the cell.
Managed object
Cell
Value Range
Yes/No
18
Document Title
Unit
None
Default value
No
Related functions
ZGF05-25-017
Related parameters
Related interfaces
eMLPP
Figure 4-8
Full name
Preemption allowed when assign
Abbreviation
PreemptionInd_0
3GPP name
3GPP reference
Description
It decides whether forced disconnection is allowed during

the assignment. The priority in the assignment request is
valid and the preemption is valid. Those connections with
low priority can be forcefully disconnected (handover) to
allocate their resources to other assignments or handover
request with higher priority. Assignment request indicate the
call status.
Managed object
Cell
Value Range
Yes/No
Unit
None
Default value
No
Related functions
ZGF05-25-017
Related parameters
Related interfaces
eMLPP
Figure 4-9
Full name
Preemption allowed when handover
Abbreviation
PreemptionInd_1
3GPP name
3GPP reference
Description
It decides whether forced disconnection is allowed during

the handover. The priority in the handover request is valid
and the preemption is valid. Those connections with low
priority can be forcefully disconnected (handover) to allocate
their resources to other assignments or handover request
with higher priority. Assignment request indicate the call
status.
Managed object
Cell
Value Range
Yes/No
Unit
None
Default value
No
19
Document Title
Related functions
ZGF05-25-017
Related parameters
Related interfaces
eMLPP
Figure 4-10
Full name
When assigned forced handover
Abbreviation
ForcedHoInd_0
3GPP name
3GPP reference
Description
This parameter indicates whether the low priority

subscribers can be forcefully handover to other cell, so that
high priority subscribers can obtain channels. This
parameter represents whether forced handover is allowed
during assignment.
Managed object
Cell
Value Range
Yes/No
Unit
None
Default value
No
Related functions
ZGF05-25-017
Related parameters
The Queue allowed when assign (QueueInd_0) parameter

must be configured at the same time.
Related interfaces
eMLPP
Figure 4-11
Full name
When handover forced handover
Abbreviation
ForcedHoInd_1
3GPP name
3GPP reference
Description
This parameter indicates whether the low priority

subscribers can be forcefully handover to other cell, so that
high priority subscribers can obtain channels. This
parameter represents whether forced handover is allowed
during handover.
Managed object
Cell
Value Range
Yes/No
Unit
None
Default value
No
Related functions
ZGF05-25-017
Related parameters
The Queue allowed when handover (QueueInd_1)

parameter must be configured at the same time.
Related interfaces
eMLPP
20
Document Title
4.2.3.2
4.2.3.3
Control Switch of eMLPP Strategy

In R8.2, in BSC FunctioneMLPP Params, you can respectively configure preemption
polices of assignment and handover for users with different priority levels. They are
represented by the AssPreemptstrategy and HoPreemptstrategy parameters in
R_EMLPP table.
1.
For assignment, there are three strategies: 0 indicates forced handover only; 1
indicates try forced handover first, and if fails, try forced release; 2 indicates forced
release first.
2.
For handover, there are three strategies: 0 indicates forced handover only; 1
indicates try forced handover first, and if fails, try forced release; 2 indicates release
only.
Figure 4-12
Switch of eMLPP Strategy
In the channel allocation in versions earlier than R8.2, users are classified into high
priority and low priority. They use different channel allocation strategies. In versions later
21
Document Title
than R8.2, to flexibly configure the channel allocation for more user types, you can set the
priority allocation strategy for users based on the priority.
4.2.3.4
Flow Control Parameters

To flexibly control eMLPP process, R8.2 adds some configuration parameters for each
user priority. The parameters are grouped based on assignment or handover, and stored
in the R_EMLPP table. The flow control parameters are important for the whole eMLPP
process. Any incorrect understanding of the parameters may result in completely different
results. The following gives a detailed description of the parameters:
Max forced handover/release times: indicates the maximum times of force handovers
or forced releases, excluding those fails to find forced handover or release objects.
Preemption duration: indicates the period when forced handover or release can be
attempted. If the period elapses, only queue is allowed, and new forced handover or
forced release is not allowed.
Timer for start forced release: If both forced handover and forced release are allowed,
do forced handover first. If no channel is acquired, attempt forced release after the timer
for start forced release elapse.
Interval for search forced handover/release target: It determines the waiting time of
next search when no forced handover/release target instance is found. The new attempts
after receiving forced handover instance fails to apply for channel or returns to the
original channel, or timeout of timer for waiting for resources after forced handover,
timeout of timer for waiting for resources after forced release, are not restricted by the
condition and can be initiated immediately.
Queue timer: It determines the time of waiting for channel after forced handover or
forced release. If no channel is acquired after waiting for such a period and the maximum
number of allowed attempts is not reached, the system can initiate a new attempt.
Note that O&M personnel shall ensure the correctness of the whole configuration. The
foreground shall ensure that the software run normally. The related restriction relations
are as follows:
1.
For the same priority level, queuing period > preemption time. In actual configuration,
the difference of the two is about 2 seconds, so that enough time is reserved for
channel release.
2.
For the same priority level, start time of forced release < preemption time. In this way,
forced release can be performed within the preemption time.
22
Document Title
4.2.3.5
Selection of Preemption Targets

In R8.2, in addition to the PVI parameter of the target cell, the priority level and
conversation time also need to be considered during the selection of forced
handover/release targets.
Therefore, two parameters for target selection, LowestPriority and LongCallDuration, are
added at BSC side. The following content details the effect of these two parameters on
target selection:
1. LowestPriority is used to decide whether a comparatively low priority user is found.
Its value range is 1 ~ 15. That is, if the priority level of the found target is not smaller
than LowestPriority, the system assumes that the target level is low enough and
stops the search. Otherwise, the system keeps searching for the lowest priority. The
purpose is to reduce the number of times of search.
a)
If the parameter is set to 15, infer that the lowest priority user must be found.
b)
If the parameter is set to 1, infer that even if a user with priority level 1 is found,
the system assumes that the priority level is low enough and stops searching.
2. LongCallDuration is used to measure conversation duration. Here it refers to the

total number of measurement reports of TCHs within the local BSC. During forced
handover and forced release, users with comparatively long conversation duration
are tended to be serve as the target. When the number reported by the measurement
is larger than LongCallDuration, it is assumed that the conversation time is long
enough to serve as the target of preemption.
a)
If the value is set to the maximum number 65535 (period of measurement

report is about 480 ms), it indicates that the user with the longest conversation
time needs to be found.
b)
Note that the priority level is more important than call duration.
Additionally, the ForceHoPenalty parameter is also used for forced handover target. It
indicates the penalty time for the handover failure of forced handover object. During
penalty period, the instance cannot serve as the forced handover target, but it can serve
as forced release target.
23
Document Title
Figure 4-13
4.2.4
Selection of Preemption Target
Channel Allocation Strategy Setting

In R8.2, the system sets channel allocation strategies for users at each priority level. The
strategies are stored in the ChanSelectstrategy field of R_BTS. Totally nine values are
available:
0: According to channel select order of MSC, when prefer TCHF and cell congest change
to prefer TCHH
1: Prefer TCHF, when cell congest change to prefer TCHH
2: Prefer TCHH
3: Only TCHF
4: Only TCHH
5: According to channel select order of MSC, not consider whether cell congest
6: According to channel select order of MSC, when prefer TCHF and cell congest,
change to prefer TCHH if AMR-HR supported
7: Prefer TCHF, not consider whether cell congest
8: Prefer TCHF, when cell congest, change to prefer TCHH if AMR-HR supported
In configuration resource tree, choose OMCGERAN SubnetworkBSC Managed
ElementConfig SetBSC FunctionSite ConfigSite and double-click Cell. In the
displayed Cell window at right, select the Other Params tab and set the related
parameters, as shown in the following figure:
24
Document Title
Figure 4-14
Channel Allocation Strategy
Engineering Guide and Configuration

Principle
5.1
Application Scenarios
When there are a small number of VIP users, configure reserved channels of a certain
quantity to ensure that the calls of important users can be established and maintained.
Queuing is an extensively-applied function and can relieve radio resources congestion.
When there are a wide variety of users, the eMLPP function can be used to realize
priority based radio resource allocation. Forced handover has little impact on users of
lower priority; forced release has major impact on users of lower priority and therefore
should be applied with care.
5.2
Configuration Principle
This feature does not involve the adjustment of iBSC and BTS hardware configuration.
25
Document Title
5.3
Recommendation
This feature involves many parameters and switches. Also, many parameters have
corresponding switches in BSC and cell. Therefore, DO CAREFULLY read the chapters
about parameter configuration before enabling this feature. Ensure that you have
grasped the meanings of the parameters and their relations.
Pay attention to the following issues when enabling this feature:
3.
Only if the switch is set to cell level, the eMLPP setting at cell level can take effect.
4.
Either forced handover or forced release is set to be allowed, the queue function must
be set to enabled. Similarly, if the setting is according to the cell, the queue function
must be set to enabled or according to the cell. The reason is that queue provides
time for forced handover and forced release.
5.
The setting of allowing forced handover and forced release does not mean that users
with high priority can surely initiate them. The implementation of forced handover,
forced release, and queue are determined with the combination of PIE parameter sent
by MSC.
Additionally, various factors affect the selection of preemption target in this feature. The
feature may not be smoothly enabled due to any misunderstanding. It is recommended to
carefully read the following process for selecting preemption target instance before
configuring flow control parameters.
The preemption target instance found by iBSC must meet the following requirement:
The channel type, band, and subcell meet the requirement.
For forced handover target, the system determines whether the target cell has
available channels in advanced.
The target is not in penalty period, and not selected as preemption target by other
users. The PVI bit (meaning preemption allowed) is reset and the priority level is
lower than the preemption initiator.
After the instance meeting the requirement is found, it is compared with LowestPriority
and LongCallDuration. If both parameters meet the requirement, the system stops
searching and use the instance as the preemption target even if subscribers with lower
priority exists. If either of the two parameters does not meet the requirement, the system
precedes searching. If the found instance has a lower priority level, replace the previous
one with this one. If the found instance has the same priority level with the previous one
but longer conversation time, it is also used to replace the previous one. Similarly, the
system determines whether to continue the search based on LowestPriority and
LongCallDuration. This process goes cyclically till both the parameter requirements are
met. If no instance meeting the requirements is found, the finally got instance serves as
the preemption target after all instances are searched. After the preemption target is
found, the data area is marked to avoid being selected as the forced handover/release
target again.
26
Document Title
R8.2 involves directed retry. It is recommended to comprehensively consider directed

retry when enabling this feature. When directed retry takes effect, it can be initiated
earlier than the end of queuing (that is, queue timer expires). Therefore, in case directed
retry permits, quits the queue after directed retry start time (rmsT10) and attempts
directed retry.
Related Counters and Alarms
6.1
Related Counters
Table 6-1
Counter list
Counter No.
What It Counts
NE
Granularity
C100430130
Number of assign TCH/F release by forced

handover to forced handover source
cell
C100430131
Number of assign TCH/F release by forced

handover to queuing user
cell
C100430132
Number of restore TCH/F release by forced

handover to DBS
cell
C100430133
Number of assign TCH/F release by forced release

to forced release source
cell
C100430134
Number of assign TCH/F release by forced release

to queuing user
cell
C100430135
Number of restore TCH/F release by forced release

to DBS
cell
C100440130
Number of assign TCH/H release by forced

handover to forced handover source
cell
C100440131
Number of assign TCH/H release by forced

handover to queuing user
cell
C100440132
Number of restore TCH/H release by forced

handover to DBS
cell
C100440133
Number of assign TCH/H release by forced release

to forced release source
cell
C100440134
Number of assign TCH/H release by forced release

to queuing user
cell
C100440135
Number of restore TCH/H release by forced

release to DBS
cell
C100460001
Number of general assignment executions for voice

channel
cell
C100460002
Number of assignments attempts for voice due to

forced release
cell
C100460003
Number of assignment executions for voice

channel due to forced release
cell
27
Document Title
C100460004
Number of handover
forced release
C100460005
Number of handover executions for voice channel

due to forced release
cell
C100460006
Number of assignments for voice channel due to

queuing
cell
C100460007
Number of assignments for execution for voice

channel due to queuing
cell
C100460008
Duration of assignment success voice channel due

to queuing
cell
C100460009
Number of assignments success for voice channel

due to queuing
cell
C100460010
Number of assignments for directed retry attempts

for voice channel
cell
C100460011
Number of assignments for execution for voice

channel due to directed retry
cell
C100460012
Number of general assignments for execution for

data
cell
C100460013
Number of assignments attempts for data due to

forced release
cell
C100460014
Number of assignment executions for data due to

forced release
cell
C100460015
Number of handover attempts for data due to

forced release
cell
C100460016
Number of handover executions for data due to

forced release.
cell
C100460017

queuing
cell
C100460018
Number of assignments for execution for data due

to queuing
cell
C100460019
Total duration of successful assignments for data

due to queuing
cell
C100460020
Number of assignments success for data due to

queuing
cell
C100460021

directed retry
cell
C100460022
Number of assignment executions for data due to

directed retry.
cell
C100460035
Number of assignments attempts due to forced

release(emergency service)
cell
C100460036
Number of assignment executions channel due to

forced release(emergency service)
cell
C100460037
Number of handover attempts due to forced

cell
C100460038
Number of handover executions channel due to

forced release(emergency service)
cell
attempts for voice due to
cell
28
Document Title
C100460039
Number of assignments channel due to

queuing(emergency service)
cell
C100460040
Number of assignments for execution channel due

to queuing(emergency service)
cell
C100460041
Number of forced handover target not

found(assignment forced handover)
cell
C100460042
Number of send forced handover request to lower

PRI user(assignment forced handover)
cell
C100460043
Number of recv failure from lower PRI user request

resource for forced handover(assignment forced
handover)
cell
C100460044
Number of lower PRI user handover

failure(assignment forced handover)
cell
C100460045
Number of time out for wait resource(assignment

forced handover)
cell
C100460046
Number of forced release target not

found(assignment forced release
cell
C100460047
Number of time out for wait resource(assignment

forced release)
cell
C100460048
Number of get before grab released

channel(assignment forced handover)
cell
C100460049

channel(assignment forced release)
cell
C100470064
Number of SDCCH drops due to eMLPP forced

handover
cell
C100470065
Number of signaling TCH/F drops due to eMLPP

forced handover
cell
C100470066
Number of voice TCH/F drops due to eMLPP

forced handover
cell
C100470067
Number of data TCH/F drops due to eMLPP forced

handover
cell
C100470068
Number of signaling TCH/H drops due to eMLPP

forced handover
cell
C100470069
Number of voice TCH/H drops due to eMLPP

forced handover
cell
C100470070
Number of data TCH/H drops due to eMLPP forced

handover
cell
C100490001
Number of handover attempts due to direct retry
cell
C100490020
Number of SDCCH handover during assignment

due to forced transfer
cell
C100490021
Number of SDCCH handover during handover due

to forced transfer
cell
C100490043
Number of TCH/F handover during assignment due

to forced transfer
cell
C100490044
Number of TCH/F handover attempts during

handover due to forced transfer
cell
29
Document Title
C100490066
Number of TCH/H handover attempts during

assignment due to forced transfer
cell
C100490067
Number of TCH/H handover attempts during

handover due to forced transfer
cell
C100500011
Number of BSC-controlled inter-cell incoming

handover attempts
cell
C100500012

handover
cell
C100500013
Number of BSC-controlled incoming handover

attempts due to forced release
cell
C100500014
Number of BSC-controlled incoming handover due

to forced release
cell
C100500015

attempts due to queue
cell
C100500016

to queue
cell
C100500017

attempts due to forced handover
cell
C100500018

to forced handover
cell
C100500019

handover success
cell
C100500020
BSC-controlled incoming handover time due to

queue
cell
C100500021

to queue
cell
C100500022
BSC-controlled incoming handover success time

due to queue
cell
C100500023

success due to queue
cell
C100500024
Number of MSC-controlled incoming handover

attempts
cell
C100500029
cell
C100500030

cell
C100500031
Number of MSC-controlled incoming handover due

to forced release
cell
C100500032

attempts due to queue
cell
C100500033

to queue
cell
C100500034

cell
C100500035

to forced handover
cell
C100500036

success
cell
30
Document Title
C100500037
MSC-controlled incoming handover time due to

queue
cell
C100500038

to queue
cell
C100500039
MSC-controlled incoming handover success time

due to queue
cell
C100500040

success due to queue
cell
C100500149
B Number of BSC-controlled inter-cell incoming

handover attempts due to forced
cell
C100500150

handover(forced release)(emergency service)
cell
C100500151

handover(emergency service)
cell
C100500152

handover(forced handover)(emergency service)
cell
C100500153

handover attempts due to queue(emergency
service)
cell
C100500154

handover(queue)(emergency service)
cell
C100500155

attempts due to forced release(emergency service)
cell
C100500156
Number of MSC-controlled incoming

handover(forced release)(emergency service)
cell
C100500157
Number of MSC-controlled inter-cell incoming

handover(emergency service)
cell
C100500158
Number of MSC-controlled inter-cell incoming

handover(forced handover)(emergency service)
cell
C100500159

attempts due to queue(emergency service)
cell
C100500160
Number of MSC-controlled incoming

handover(queue)(emergency service)
cell
C100500161
Number of forced handover target not

found(BSC-controlled inter-cell handover due to
forced handover)
cell
C100500162

PRI user(BSC-controlled inter-cell handover due to
forced handover)
cell
C100500163
Number of recv failure from lower PRI user request

resource for forced handover(BSC-controlled
inter-cell handover due to forced handover)
cell
C100500164

failure(BSC-controlled inter-cell handover due to
forced handover)
cell
31
Document Title
C100500165
Number of high PRI user time out for wait

resource(BSC-controlled inter-cell handover due to
forced handover)
cell
C100500166

found(BSC-controlled inter-cell handover due to
forced release)
cell
C100500167

resource(BSC-controlled inter-cell handover due to
forced release)
cell
C100500168
Number of HO Target not found(MSC-controlled

incoming handover due to forced handover)
cell
C100500169

PRI user(MSC-controlled incoming handover due
to forced handover)
cell
C100500170
Number of failure to lower PRI user request

resource for forced handover(MSC-controlled
incoming handover due to forced handover)
cell
C100500171

failure(MSC-controlled incoming handover due to
forced handover)
cell
C100500172

resource(MSC-controlled incoming handover due
to forced handover)
cell
C100500173

found(MSC-controlled incoming handover due to
forced release)
cell
C100500174

resource(MSC-controlled incoming handover due
to forced release)
cell
C100500175

channel(handover forced handover)
cell
C100500176

channel(handover forced release)
cell
C100500177
Number of handover attempts due to eMLPP

forced handover
cell
C100500178
Number of handover due to eMLPP forced

handover
cell
C100500179
Number of handover success due to eMLPP forced

handover
cell
C100510001
Average length of queue
cell
C100510002
Duration of queuing
cell
C100510003
Number of queuing
cell
C100510004
Duration of queuing success
cell
C100510005
Number of queuing success
cell
32
Document Title
6.2
Related Alarms
None
Abbreviations
Abbreviation
Full Name
eMLPP
enhanced Multi-Level Precedence and Preemption service
PCI
Preemption capability indicator
PIE
Priority Information Element
PL
Priority Level
PREC
Preemption Recommendation
PVI
Preemption
QA
Queuing allowed indicator
TCH
Traffic channel
vulnerability indicator
Reference Document
[1] 3GPP TS 22.067
3rd Generation Partnership Project;Technical Specification Group Services and System
Aspects;enhanced Multi-Level Precedence and Preemption service (eMLPP) - Stage 1
[2] 3GPP TS 23.067
3rd
Generation
Partnership
Project;Technical
Specification
Group
Core
Network;enhanced Multi-Level Precedence and Preemption service (eMLPP) - Stage 2
[3] 3GPP TS 24.067
3rd
Generation
Partnership
Project;Technical
Specification
Group
Core
Network;enhanced Multi-Level Precedence and Preemption service (eMLPP) - Stage 3
[4] ZXG10 BSS (V6.20) Radio Parameters Reference (Volume I)
[5] ZXG10 BSS (V6.20) Radio Parameters Referce (Volume II)
33

ZGO-01-03-001 eMLPP FG 20101030 PDF

Загружено:

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

Исходное описание:

Оригинальное название

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

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

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

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

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

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

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

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

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

ZGO-01-03-001 eMLPP FG 20101030 PDF

Загружено:

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

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

Operator Logo

2010 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

2010 ZTE CORPORATION. All rights reserved.

Feature Property ............................................................................................. 1

Technical Description .................................................................................... 2

Parameter Configuration and Descriptions .................................................. 8

Engineering Guide and Configuration Principle......................................... 25

Related Counters and Alarms ...................................................................... 27

Reference Document .................................................................................... 33

ZTE Confidential Proprietary

2010 ZTE CORPORATION. All rights reserved.

Cell Switch ...................................................................................................... 18

Figure 4-7 ............................................................................................................................. 18

ZTE Confidential Proprietary

2010 ZTE CORPORATION. All rights reserved.

ZTE Confidential Proprietary

2010ZTE Corporation. All rights reserved.

Queuing and preemption

Reserve channels for high-priority users;

Correlation with Other Features

ZGF05-02-005 Directed Retry: As another mode to obtain resources during channel

A Interface Parameters Related to eMLPP

ZTE Confidential Proprietary

2010ZTE Corporation. All rights reserved.

Table 3-2 lists the definition of priority bits.

Priority BIT Definition

Priority Level (PL) occupies 4 bits and defines 15 user levels.

priority level 1 = highest priority

priority level 2 = second highest priority

priority level 14 = lowest priority

priority not used

Other parameters are defined as follows:

Extra information definition

ZTE Confidential Proprietary

2010ZTE Corporation. All rights reserved.

Field Element identifier

PREC (Preemption Recommendation): identifies whether source BSC recommends the

eMLPP Call Setup Flow

an idle TCH channel in the local cell:

Judge whether allow forced handover:

If ForcedHoInd_0=1, forced handover is allowed. In this case, go to step 2.

If ForcedHoInd_0=0, forced handover is allowed. In this case, go to step 4.

Judge whether allow forced queue:

If QueueInd_0=1, queue is allowed. In this case, go to step 3.

If QueueInd_0=0, queue is not allowed. In this case, go to step 4. Forced

If the forced handover object is found, trigger handover and go to step 7.

If the forced handover object is not found, go to step 4.

ZTE Confidential Proprietary

2010ZTE Corporation. All rights reserved.

Judge whether the cell parameter configuration allows forced release:

If PreemptionInd_0=1, forced release is allowed. In this case, go to step 5.

If PreemptionInd_0=0, forced release is not allowed. In this case, go to step 6.

If the forced release object is not found, go to step 6.

Judge whether the cell parameter configuration allows queue:

If QueueInd_0=1, queue is allowed. In this case, go to step 7.

Enter the queue to wait for channel allocation.

If channel is acquired before the timer expires, MS successfully acquires the

If no channel is acquired before the timer expires, go to step 8.

Judge whether the cell parameter configuration allows forced release:

If PreemptionInd_0=1, forced release is allowed. In this case, go to step 9.

If PreemptionInd_0=0, forced release is not allowed. Channel allocation fails