ZGO-01-03-001 eMLPP

Feature Guide

ZGO-01-03-001 eMLPP

ZGO-01-03-001 eMLPP
Version

V1.0

Date

2013/04/03

Author
Luo Chang
qing

Reviewer
GU

Notes

Commercial

System Supporting

Not open to the third party

Dept.

2013 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

ZGO-01-03-001 eMLPP

TABLE OF CONTENTS

Feature Attribute ............................................................................................... 6

2
2.1
2.2
2.3

Overview ............................................................................................................ 6
Feature Introduction ............................................................................................. 6
License Control .................................................................................................... 7
Correlation with Other Features ........................................................................... 7

3
3.1
3.2
3.3

Technical Description ....................................................................................... 8

A Interface Parameters Related to eMLPP........................................................... 8
eMLPP Call Setup Flow ..................................................................................... 10
eMLPP Handover Flow ...................................................................................... 14

4
4.1
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
4.2.10
4.2.11
4.2.12
4.2.13
4.2.14
4.2.15
4.2.16
4.2.17
4.2.18
4.2.19
4.2.20

Parameters and Configurations ..................................................................... 16

Parameter List ................................................................................................... 16
Parameter Configuration .................................................................................... 17
User Priority threshold for EMLPP ..................................................................... 17
Reserved channel first ....................................................................................... 17
EMLPP channel reserved rate (BSC) ................................................................. 18
EMLPP channel reserved rate (cell) ................................................................... 18
Use cell EMLPP Threshold ................................................................................ 19
Support EMLPP ................................................................................................. 19
Queue indicate when assign .............................................................................. 19
Queue allowed when handover .......................................................................... 20
Forced release indication when assign .............................................................. 20
Forced release allowed when handover ............................................................. 21
Forced handover indication for assign................................................................ 21
Forced handover indication for handover ........................................................... 22
Strategy for preemption when assign ................................................................. 22
Strategy for preemption when handover ............................................................ 23
Queue allowed when assign .............................................................................. 23
Queue allowed when handover .......................................................................... 23
Forced release indicate when assign ................................................................. 24
Forced handover indication for assign................................................................ 24
Forced release indicate when handover ............................................................. 25
Forced handover indication for handover ........................................................... 26

5
5.1
5.2

Related Counters and Alarms ........................................................................ 26

Related Counters ............................................................................................... 26
Related Alarms .................................................................................................. 33

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

6
6.1
6.2
6.3
6.3.1
6.3.2
6.4
6.5

Engineering Guide .......................................................................................... 34

Application Scenario .......................................................................................... 34
Configuration Description ................................................................................... 34
Feature Validation .............................................................................................. 37
Force release of CS service ............................................................................... 37
Force handover of CS services .......................................................................... 37
Feature Turn off ................................................................................................. 38
Network Impact .................................................................................................. 39

Abbreviation .................................................................................................... 41

Reference Document....................................................................................... 42

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

FIGURES
Figure 3-1 Flow of Handling Channel Acquisition Failure in Local Cell .................................13
Figure 3-2 eMLPP Handover Flow........................................................................................15
Figure 6-1 eMLPP Configuration window1 ............................................................................34
Figure 6-2 eMLPP Configuration window 2 ...........................................................................35
Figure 6-3 eMLPP User Priority Configuration window .........................................................35
Figure 6-4 GSM Cell Configuration window1 ........................................................................36
Figure 6-5 GSM Cell Configuration window2 ........................................................................36
Figure 6-6 eMLPP Configuration window..............................................................................39

TABLES
Table 3-1 PIE definition ......................................................................................................... 8
Table 3-2 Priority BIT............................................................................................................. 8
Table 3-3 Extra information definition .................................................................................... 9
Table 4-1 Parameter List ......................................................................................................16
Table 4-2 Configuration rule of User Priority threshold for EMLPP .......................................17
Table 4-3 Configuration rule of Reserved channel first .........................................................17
Table 4-4 Configuration rule of EMLPP channel reserved rate (BSC)...................................18
Table 4-5 Configuration rule of EMLPP channel reserved rate (cell).....................................18
Table 4-6 Configuration rule of Use cell EMLPP Threshold ..................................................19
Table 4-7 Configuration rule of Support EMLPP ...................................................................19
Table 4-8 Configuration rule of Queue indicate when assign ................................................19
Table 4-9 Configuration rule of Queue allowed when handover ............................................20
Table 4-10 Configuration rule of Forced release indication when assign ..............................20
Table 4-11 Configuration rule of Forced release allowed when handover .............................21
Table 4-12 Configuration rule of Forced handover indication for assign ...............................21

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

Table 4-13 Configuration rule of Forced handover indication for handover ...........................22
Table 4-14 Configuration rule of Strategy for preemption when assign .................................22
Table 4-15 Configuration rule of Strategy for preemption when handover ............................23
Table 4-16 Configuration rule of Queue allowed when assign ..............................................23
Table 4-17 Configuration rule of Queue allowed when handover ..........................................23
Table 4-18 Configuration rule of Forced release indicate when assign .................................24
Table 4-19 Configuration rule of Forced handover indication for assign ...............................24
Table 4-20 Configuration rule of Forced release indicate when handover.............................25
Table 4-21 Configuration rule of Forced handover indication for handover ...........................26
Table 5-1 Counter List ..........................................................................................................26

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

Feature Attribute
BSC Version: [ZXG10-iBSC GSM (V6.30.102)]
BTS Version: [Independent with the BTS hardware platform ]
Property: [Optional]
Related Network Element:
NE Name

Related or Not

MS

BTS

BSC

MSC

MGW

SGSN

GGSN

HLR

Special Requirements

Intra-MSC handover not involved, inter-MSC

handover involved

Dependent Function: [None]

Exclusive Function: [None]
Note: [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. ZTE BSC supports all
functions related with eMLPP.

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

After the service is provisioned, mobile subscribers are differentiated by different

priority levels. The system allocates channel resources by 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:

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.

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.

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

License Control
None license control for this feature in UR12 Release.

2.3

Correlation with Other Features

This feature is functionally related to the following features:

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

ZGO-04-02-005 Co-BCCH: If the handover from sub-cell 2 to sub-cell 1, as the

emergency handover, the eMLPP preemption flow is used.
ZGB-03-01-002 Directed Retry: As another mode to obtain resources during channel
congestion, it is considered in enhanced eMLPP function.
ZGO-03-02-002 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.
Priority (PIE) information element is defined as table below.

Table 3-1 PIE definition

8

Element identifier

octet 1

Length

octet 2

Priority

octet 3

Priority bits are shown below.

Table 3-2 Priority BIT

8

spare

pci

priority level

qa

pvi

octet 3

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

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

6543 (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

8

Field Element identifier

octet 1

Length

octet 2
octet 3

Octet 3 is coded as follows:

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

spare

UE-

lcs

prec

octet 3

prob

Pre-emption Recommendation (PREC) 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.

2.

Judge whether allow forced handover:

i.

ForcedHoInd_01, forced handover is allowed. In this case, go to step 2.

ii.

ForcedHoInd_00, 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.

10

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

3.

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.

4.

5.

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.

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.
6.

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.

7.

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.
8.

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

Judge whether the cell parameter configuration allows forced release:

ZTE Confidential Proprietary

11

ZGO-01-03-001 eMLPP

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.

9.

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 below.

12

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

Figure 3-1 Flow of Handling Channel Acquisition Failure in Local Cell

ZTE Confidential Proprietary

13

ZGO-01-03-001 eMLPP

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
ZGO-04-02-005 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.

2.

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

14

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

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 eMLPP Handover Flow

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

ZTE Confidential Proprietary

15

ZGO-01-03-001 eMLPP

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.

4
4.1

Parameters and Configurations

Parameter List
Table 4-1 Parameter List

16

SN

Name

Figure

User priority threshold for EMLPP

Figure 4-1

Reserved channel first

Figure 4-1

EMLPP channel reserved rate

Figure 4-1

EMLPP channel reserved rate

Figure 4-5

Use cell EMLPP Threshold

Figure 4-5

Support EMLPP(SupportEMLPP)

Figure 4-1

Queue indicate when assign

Figure 4-2

Queue allowed when handover

Figure 4-2

Forced release indicate when assign

Figure 4-2

10

Forced release allowed when handover

Figure 4-2

11

Forced handover indication for assign

Figure 4-2

12

Forced handover indication for handover

Figure 4-2

13

Strategy for preemption when assign

Figure 4-3

14

Strategy for preemption when handover

Figure 4-3

15

Queue allowed when assign

Figure 4-4

16

Queue allowed when handover

Figure 4-4

17

Forced release indicate when assign

Figure 4-4

18

Forced handover indication for assign

Figure 4-4

19

Forced release indicate when handover

Figure 4-4

20

Forced handover indication for handover

Figure 4-4

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

4.2
4.2.1

Parameter Configuration
User Priority threshold for EMLPP
Table 4-2 Configuration rule of User Priority threshold for EMLPP
Full name

User Priority threshold for EMLPP

Abbreviation

priThreshold
This parameter (PriThreshold) uses the service of preferred
access for high-priority subscriber, that is eMLPP service, the
system may set some reserved channels (currently, only full rate
TCH channels are supported to be the reserved channels). When
CS instance calls database to apply for channels, the subscriber's

Description

PriorityLevel information reaches to database, and is compared

with PriThreshold in the database and BSC table. When
PriorityLevelPriThreshold (the less the subscriber's priority level
value, the higher the priority level, that is the subscriber's priority
level is not lower than PriThreshold priority), the reserved channel
can be used.

4.2.2

Managed object

eMLPP Configuration (GBssEmlpp)

Value range

1~15

Unit

NA

Default value

Reserved channel first

Table 4-3 Configuration rule of Reserved channel first
Full name

Reserved channel first

Abbreviation

rsvChanFirst
This parameter indicates the selection order of reserved channel
and non-reserved channel. If this feature is enabled, the reserved

Description

channel has the higher priority.

1: reserved channel is preferred.

0: non-reserved channel is preferred.

Managed object

ZTE Confidential Proprietary

eMLPP Configuration (GBssEmlpp)

17

ZGO-01-03-001 eMLPP

4.2.3

Value range

0~1

Unit

NA

Default value

EMLPP channel reserved rate (BSC)

Table 4-4 Configuration rule of EMLPP channel reserved rate (BSC)
Full name

EMLPP channel reserved rate (BSC)

Abbreviation

emlppThs
This parameter decides the proportion of channels reserved for

Description

high-priority subscribers when you enable the eMLPP service

function, which allows high-priority users to access channels first.

4.2.4

Managed object

eMLPP Configuration (GBssEmlpp)

Value range

0~100

Unit

Default value

EMLPP channel reserved rate (cell)

Table 4-5 Configuration rule of EMLPP channel reserved rate (cell)
Full name

EMLPP channel reserved rate (cell)

Abbreviation

emlppThs
When using high priority user to access service, that is, EMLPP
service, the system may configure certain reserved channels for

Description

the users with high priority to access CS service. The reserved

channels equal to the reserved rate of EMLPP multiplying the
minimum value of available channels (including TCH and PD) and
idle TCHP channels.

18

Managed object

GSM Cell Configuration (GGsmCell)

Value range

0~100

Unit

Default value

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

4.2.5

Use cell EMLPP Threshold

Table 4-6 Configuration rule of Use cell EMLPP Threshold
Full name

Use cell EMLPP Threshold

Abbreviation

useCellEmlppThs

Description
Managed object
Value range

4.2.6

This parameter defines whether to use eMLPPThs. If yes, you

shall select cell property, otherwise to select BSC property.
GSM Cell Configuration (GGsmCell)
0: No

1: Yes

Unit

NA

Default value

Support EMLPP
Table 4-7 Configuration rule of Support EMLPP
Full name

Support EMLPP

Abbreviation

supportEmlpp
This parameter indicates whether the eMLPP function is enabled.

Description

0 (NO): Disabled.1 (YES): Enabled. The related functions include

queuing, forced handover and release, and reserved channels.

Managed object
Value range

4.2.7

eMLPP Configuration (GBssEmlpp)

0: No
1: Yes

Unit

NA

Default value

Queue indicate when assign

Table 4-8 Configuration rule of Queue indicate when assign
Full name

Queue indicate when assign

Abbreviation

queueIndAss

ZTE Confidential Proprietary

19

ZGO-01-03-001 eMLPP

During an assignment, this parameter decides whether to allow

Description

queuing or carry out the assignment according to the cell settings

when there are no available channels in the cell.

Managed object

eMLPP Configuration (GBssEmlpp)

0: Queue forbidden when assign

Value range

1: Queue allowed when assign

2: According to the cell

4.2.8

Unit

NA

Default value

Queue allowed when handover

Table 4-9 Configuration rule of Queue allowed when handover
Full name

Queue allowed when handover

Abbreviation

queueIndHo

Description

During a handover, this parameter decides whether to allow

queuing or carry out the assignment according to the cell
settings when there are no available channels in the cell.

Managed object

eMLPP Configuration (GBssEmlpp)

0: Queue forbidden when handover

Value range

1: Queue allowed when handover

2: According to the cell

4.2.9

Unit

NA

Default value

Forced release indication when assign

Table 4-10 Configuration rule of Forced release indication when assign
Full name

Forced release indication when assign

Abbreviation

preemptionIndAss
This parameter decides whether to allow forced releases during an

Description

assignment or carry out the assignment according to the cell

settings when there are no available channels in the cell.

20

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

Managed object

eMLPP Configuration (GBssEmlpp)

0: Forced release forbidden when assign

Value range

1: Forced release allowed when assign

2: According to the cell

4.2.10

Unit

NA

Default value

Forced release allowed when handover

Table 4-11 Configuration rule of Forced release allowed when handover
Full name

Forced release allowed when handover

Abbreviation

preemptionIndHo

Description

This parameter decides whether to allow forced releases during

a handover or carry out the handover according to the cell
settings when there are no available channels in the cell.

Managed object

eMLPP Configuration (GBssEmlpp)

0: Forced release forbidden when handover

Value range

1: Forced release allowed when handover

2: According to the cell

4.2.11

Unit

NA

Default value

Forced handover indication for assign

Table 4-12 Configuration rule of Forced handover indication for assign
Full name

Forced handover indication for assign

Abbreviation

forcedHoIndAss
This parameter decides whether to allow forced handovers during

Description

an assignment or carry out the assignment according to the cell

settings when there are no available channels in the cell.

Managed object

eMLPP Configuration (GBssEmlpp)

0: Forced handover forbidden when assign

Value range

1: Forced handover allowed when assign

2: According to the cell

ZTE Confidential Proprietary

21

ZGO-01-03-001 eMLPP

4.2.12

Unit

NA

Default value

Forced handover indication for handover

Table 4-13 Configuration rule of Forced handover indication for handover
Full name

Forced handover indication for handover

Abbreviation

forcedHoIndHo
This parameter decides whether to allow forced handovers during

Description

a handover or carry out the handover according to the cell settings

when there are no available channels in the cell.

Managed object

eMLPP Configuration (GBssEmlpp)

0: Forced handover forbidden when handover

Value range

1: Forced handover allowed when handover

2: According to the cell

4.2.13

Unit

NA

Default value

Strategy for preemption when assign

Table 4-14 Configuration rule of Strategy for preemption when assign
Full name

Strategy for preemption when assign

Abbreviation

assPreemptstrategy
This parameter specifies the preemption strategy in the
assignment process when there are no available channels. Its

Description

value corresponds to 15 levels of priority (1 to 15) which are

defined by the parameter "Priority" in the Assignment Command
message or Handover Request message from the CN.

Managed object

eMLPP User Priority Configuration (GEmlppUserPriority)

0: Only forced handover

Value range

1: First forced handover, if fail, forced release

2: First forced release

22

Unit

NA

Default value

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

4.2.14

Strategy for preemption when handover

Table 4-15 Configuration rule of Strategy for preemption when handover
Full name

Strategy for preemption when handover

Abbreviation

hoPreemptstrategy

Description

This parameter specifies the preemption strategy in handovers

when there are no available channels. Its value corresponds to
15 levels of priority (1 to 15) which are defined by the parameter
"Priority" in the Assignment Command message or Handover
Request message from the CN.

Managed object

eMLPP User Priority Configuration (GEmlppUserPriority)

Value range

0: Only forced handover

1: First forced handover, if fail, forced release
2: First forced release

4.2.15

Unit

NA

Default value

Queue allowed when assign

Table 4-16 Configuration rule of Queue allowed when assign
Full name

Queue allowed when assign

Abbreviation

queueAssInd

Description

This parameter determines whether to allow queuing during

assignments when no available channel exists in the cell.

Managed object

GSM Cell Configuration (GGsmCell)

0: not allowed

Value range

4.2.16

1: allowed

Unit

NA

Default value

Queue allowed when handover

Table 4-17 Configuration rule of Queue allowed when handover
Full name

ZTE Confidential Proprietary

Queue allowed when handover

23

ZGO-01-03-001 eMLPP

Abbreviation

queueHoInd

Description

This parameter determines whether to allow queuing during

handovers when no available channel exists in the cell.

Managed object

GSM Cell Configuration (GGsmCell)

0: not allowed

Value range

4.2.17

1: allowed

Unit

NA

Default value

Forced release indicate when assign

Table 4-18 Configuration rule of Forced release indicate when assign
Full name

Forced release indicate when assign

Abbreviation

preemptionAssInd

Description

This parameter indicates whether to allow forced release during

assignments. The MSC sends the priority parameters
(including priority level, PCI, and PVI) to the BSC through an
assignment command message. If this message contains a
high priority level and a valid PCI (indicating this user can
preempt the channel of another user), the BSC can forcibly
release the connection to a user whose PVI is reset (indicating
the channel of this user can be preempted by another user) and
then allocate the released channel on this assignment request
when no resource is immediately assigned to the higher-priority
user.

Managed object

GSM Cell Configuration (GGsmCell)

Value range

4.2.18

0: not allowed
1: allowed

Unit

NA

Default value

Forced handover indication for assign

Table 4-19 Configuration rule of Forced handover indication for assign
Full name

24

Forced handover indication for assign

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

Abbreviation

forcedAssInd

Description

This parameter indicates whether to allow forced handover

during assignments. The MSC sends the priority parameters
(including priority level, PCI, and PVI) to the BSC through an
assignment command message. If this message contains a
high priority level and a valid PCI (indicating this user can
preempt the channel of another user), the BSC can hand over a
user whose PVI is reset (indicating the channel of this user can
be preempted by another user) to another cell and then allocate
the released channel on this assignment request when no
resource is immediately assigned to the higher-priority user.

Managed object

GSM Cell Configuration (GGsmCell)

Value range

4.2.19

0: not allowed
1: allowed

Unit

NA

Default value

Forced release indicate when handover

Table 4-20 Configuration rule of Forced release indicate when handover
Full name

Forced release indicate when handover

Abbreviation

preemptionHoInd

Description

This parameter indicates whether to allow forced release during

handovers. The MSC sends the priority parameters (including
priority level, PCI, and PVI) to the BSC through an assignment
command or handover request message. If this message
contains a high priority level and a valid PCI (indicating this
user can preempt the channel of another user), the BSC can
forcibly release the connection to a user whose PVI is reset
(indicating the channel of this user can be preempted by
another user) and then allocate the released resource to this
handover request when no resource is immediately assigned in
this handover or the later handover.

Managed object

GSM Cell Configuration (GGsmCell)

Value range
Unit

ZTE Confidential Proprietary

0: not allowed
1: allowed
NA

25

ZGO-01-03-001 eMLPP

Default value

4.2.20

Forced handover indication for handover

Table 4-21 Configuration rule of Forced handover indication for handover
Full name

Forced handover indication for handover

Abbreviation

forcedHoInd

Description

This parameter determines whether to allow forced handover

during handovers. The MSC sends the priority parameters
(including priority level, PCI, and PVI) to the BSC through an
assignment command or handover request message. If this
message contains a high priority level and a valid PCI
(indicating this user can preempt the channel of another user),
the BSC can hand over a user whose PVI is reset (indicating
the channel of this user can be preempted by another user) to
another cell and then allocate the released resource to this
handover request when no resource is immediately assigned in
this handover or the later handover.

Managed object

GSM Cell Configuration (GGsmCell)

Value range

0: not allowed
1: allowed

Unit

NA

Default value

Related Counters and Alarms

5.1

Related Counters
Table 5-1 Counter List
Counter ID

Name

C901260002

Number of signaling TCH/F seizure success for

assignment

26

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

C901260003

Number of signaling TCH/F seizure failure for

assignment

C901260004

Number of signaling TCH/F seizure attempts for

handover

C901260005

Number of signaling TCH/F seizure success for

handover

C901260006

Number of signaling TCH/F seizure failure for handover

C901260007

Number of signaling TCH/F allocation attempts for

assignment

C901270130

Number of assigning TCH/H released by forced

handover to forced handover source

C901270131

Number of assigning TCH/H released by forced

handover to queuing user

C901270132

Number of restoring TCH/H released by forced handover

to DBS

C901270133

Number of assigning TCH/H released by forced release

to forced release source

C901270134

Number of assigning TCH/H released by forced release

to queuing user

C901270135

Number of restoring TCH/H released by forced release to

DBS

C901050001

Number of general assignment executions (voice)

C901050002

Number of assignment attempts due to forced release

(voice)

C901050003

Number of assignment executions due to forced release

(voice)

C901050004

Number of assignment attempts due to forced handover

(voice)

C901050005

Number of assignment executions due to forced

handover (voice)

C901050006

Number of assignment attempts due to queuing (voice)

C901050007

Number of assignment executions due to queuing (voice)

C901050008

Duration of successful assignment due to queuing

(voice)

C901050009

ZTE Confidential Proprietary

Number of assignment successes due to queuing (voice)

27

ZGO-01-03-001 eMLPP

C901050010

Number of attempts of assignment for directed retry

(voice)

C901050011

Number of assignment executions due to directed retry

(voice)

C901050012

Number of general assignment executions (data)

C901050013

Number of assignment attempts due to forced release

(data)

C901050014

Number of assignment executions due to forced release

(data)

C901050015

Number of assignment attempts due to forced handover

(data)

C901050016

Number of assignment executions due to forced

handover (data)

C901050017

Number of assignments attempts for data due to queuing

C901050018

Number of assignment executions for data due to

queuing

C901050019

Duration of successful assignments for data due to

queuing

C901050020

Number of assignments success for data due to queuing

C901050021

Number of assignments attempts for directed retry (data)

C901050022

Number of assignment executions for directed retry

(data)

C901050023

Number of assignment attempts for directed retry

towards FDD cell (voice)

C901050024

Number of assignment executions for directed retry

towards FDD cell (voice)

C901050025

Number of assignment attempts for directed retry

towards FDD cell (data)

C901050026

Number of assignment executions for directed retry

towards FDD cell (data)

C901050027

Number of assignments attempts for directed retry

towards TDD cell (voice)

C901050028

Number of assignments executions for directed retry

towards TDD cell (voice)

C901050029

Number of assignments attempts for directed retry

towards TDD cell (data)

28

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

C901050030

Number of assignments executions for directed retry

towards TDD cell (data)

C901050031

A-interface assignment failure due to circuit obstruction

C901050032

A-interface assignment failure due to circuit group

mismatched

C901050033

A-interface assignment failure due to no available radio

resource

C901050034

A-interface assignment failure due to other causes

C901050035

Number of assignments attempts due to forced

release(emergency service)

C901050036

Number of assignment executions due to forced release

(emergency service)

C901050037

Number of assignment attempts due to forced handover

(emergency service)

C901070064

Number of SDCCH drops due to eMLPP forced handover

C901070065

Number of signaling TCH/F drops due to eMLPP forced

handover

C901070066

Number of voice TCH/F drops due to eMLPP forced

handover

C901070067

Number of data TCH/F drops due to eMLPP forced

handover

C901070068

Number of signaling TCH/H drops due to eMLPP forced

handover

C901070069

Number of voice TCH/H drops due to eMLPP forced

handover

C901070070

Number of data TCH/H drops due to eMLPP forced

handover

C901060001

Number of handover attempts due to direct retry

C901060020

Number of attempts of forced handover during

assignment (on SDCCH)

C901060021

Number of attempts of forced handover during handover

(on SDCCH)

C901060043

Number of attempts of forced handover during

assignment (on TCH/F)

C901060044

Number of attempts of forced handover during handover

(on TCH/F)

ZTE Confidential Proprietary

29

ZGO-01-03-001 eMLPP

C901060066

Number of attempts of forced handover during

assignment (on TCH/H)

C901060067

Number of attempts of forced handover during handover

(on TCH/H)

C901090011

Number of BSC-controlled inter-cell incoming handover

attempts

C901090012

Number of BSC-controlled inter-cell incoming handover

C901090013

Number of BSC-controlled inter-cell incoming handover

attempts due to forced release

C901090014

Number of BSC-controlled inter-cell incoming handover

due to forced release

C901090015

Number of BSC-controlled inter-cell incoming handover

attempts due to queue

C901090016

Number of BSC-controlled inter-cell incoming handover

due to queue

C901090017

Number of BSC-controlled inter-cell incoming handover

attempts due to forced handover

C901090018

Number of BSC-controlled inter-cell incoming handover

due to forced handover

C901090019

Number of BSC-controlled inter-cell incoming handover

success

C901090020

Total time of queuing for BSC-controlled incoming

handover

C901090021

Number of BSC-controlled incoming handover due to

queue

C901090022

Total time of queuing for successful BSC-controlled

incoming handover

C901090023

Number of BSC-controlled incoming handover success

due to queue

C901090024

Number of MSC-controlled incoming handover attempts

C901090025

Number of A-interface incoming handover failures due to

circuit obstruction

C901090026

Number of A-interface incoming handover failures due to

circuit group mismatched

C901090027

Number of A-interface incoming handover failures due to

no available radio resource

30

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

C901090028

Number of A-interface incoming handover failures due to

other factors

C901090029

Number of MSC-controlled incoming handover

C901090030

Number of forced release attempts due to

MSC-controlled incoming handover

C901090031

Number of MSC-controlled incoming handover due to

forced release

C901090032

Number of MSC-controlled incoming handover attempts

due to queue

C901090033

Number of times a service queues due to MSC-controlled

incoming handover

C901090034

Number of forced handover attempts due to

MSC-controlled inter-cell incoming handover

C901090035

Number of MSC-controlled incoming handover due to

forced handover

C901090036

Number of MSC-controlled incoming handover success

C901090149

Number of BSC-controlled inter-cell incoming handover

attempts due to forced release(emergency service)

C901090150

Number of BSC-controlled inter-cell incoming

handover(forced release)(emergency service)

C901090151

Number of BSC-controlled inter-cell incoming handover

attempts due to forced handover(emergency service)

C901090152

Number of BSC-controlled inter-cell incoming

handover(forced handover)(emergency service)

C901090153

Number of BSC-controlled inter-cell incoming handover

attempts due to queue(emergency service)

C901090154

Number of BSC-controlled inter-cell incoming

handover(queue)(emergency service)

C901090155

Number of MSC-controlled incoming handover attempts

due to forced release(emergency service)

C901090156

Number of MSC-controlled incoming handover(forced

release)(emergency service)

C901090157

Number of MSC-controlled inter-cell incoming handover

attempts due to forced handover(emergency service)

C901090158

Number of MSC-controlled inter-cell incoming

handover(forced handover)(emergency service)

ZTE Confidential Proprietary

31

ZGO-01-03-001 eMLPP

C901090159

Number of MSC-controlled incoming handover attempts

due to queue(emergency service)

C901090160

Number of MSC-controlled incoming

handover(queue)(emergency service)

C901090161

Number of forced handover target not

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

C901090162

Number of sending forced handover request to lower PRI

user (BSC-controlled inter-cell handover due to forced
handover)

C901090163

Number of receiving failure in lower PRI user requesting

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

C901090164

Number of lower PRI user handover

failure(BSC-controlled inter-cell handover due to forced
handover)

C901090165

Number of higher PRI user's timeout for waiting for

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

C901090166

Number of forced release target not

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

C901090167

Number of higher PRI user's timeout for waiting for

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

C901090168

Number of forced handover target not found

(MSC-controlled incoming handover due to forced
handover)

C901090169

Number of sending forced handover request to lower PRI

user (MSC-controlled incoming handover due to forced
handover)

C901090170

Number of failure in lower PRI user requesting resource

for forced handover (MSC-controlled incoming handover
due to forced handover)

C901090171

Number of lower PRI user handover

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

32

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

C901090172

Number of higher PRI user's timeout for waiting for

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

C901090173

Number of forced release target not

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

C901090174

Number of higher PRI user's timeout for waiting for

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

C901090175

Number of getting previously preempted released

channel (handover forced handover)

C901090176

Number of getting previously preempted released

channel (handover forced release)

C901090177

Number of handover attempts due to eMLPP forced

handover

C901090178

Number of handover due to eMLPP forced handover

C901090179

Number of handover success due to eMLPP forced

handover

5.2

C901510001

Average length of queue

C901510002

Duration of queuing

C901510003

Number of queuing

C901510004

Duration of queuing success

C901510005

Number of queuing success

Related Alarms
This feature has no related alarms.

ZTE Confidential Proprietary

33

ZGO-01-03-001 eMLPP

6
6.1

Engineering Guide
Application Scenario
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.

6.2

Configuration Description
In the configuration resource tree window, double click Configuration Management
Modify Area GSM Logical Configuration Global Information Configuration eMLPP
Configuration, set related parameters, as shown below.

Figure 6-1 eMLPP Configuration window1

34

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

In the configuration resource tree window, double click Configuration Management

Modify Area GSM Logical Configuration Global Information Configuration eMLPP
Configuration, set related parameters, as shown below.

Figure 6-2 eMLPP Configuration window 2

In the configuration resource tree window, double click Configuration Management

Modify Area GSM Logical Configuration Global Information Configuration eMLPP
Configuration eMLPP User Priority Configuration, set related parameters, as shown
below.

Figure 6-3 eMLPP User Priority Configuration window

ZTE Confidential Proprietary

35

ZGO-01-03-001 eMLPP

In the configuration resource tree window, double click Configuration Management

Modify Area GSM Logical Configuration Cell Information Configuration GSM Cell
Configuration, set related parameters, as shown below.

Figure 6-4 GSM Cell Configuration window1

In the configuration resource tree window, double click Configuration Management

Modify Area GSM Logical Configuration Cell Information Configuration GSM Cell
Configuration, set related parameters, as shown below.

Figure 6-5 GSM Cell Configuration window2

36

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

6.3

Feature Validation

6.3.1

Force release of CS service

Test Item

Force release of CS service

Precondition

1.

check CN is healthy;

2.

check BSC is healthy;

3.

check SDR is healthy;

4.

check default cell configuration and parameters in BSC;

5.

ensure good radio environment;

6.

The test MS has been registered on HLR: MS1 with

higher priority (PCI=1)., MS2 with lower priority (PVI=1);

Test Steps

7.

MSC supports emlpp.

1.

Set cell property supporting preemption

(preemptionind_0= yes);

2.

MS2 make a call and block other channel which are not
used;

Anticipative Result

3.

MS1 make a call;

4.

Repeat Step 2 and 3 without blocking other channels

1.

At step3, the second call could be established by

preempting channel which MS2 occupied.

2.

At step3, Clear Request with Cause: Preemption can

be found in SCCP signalling.

3.

At step4, MS1 call established without preempting MS2

Test Result

1.

Force release of CS service performed successfully.

Parameters Setting

Default parameters

6.3.2

Force handover of CS services

Test Item

Force handover of CS services

Precondition

1.

check CN is healthy, see chapter Check Test

Environment;

2.

check BSC is healthy, see chapter Check Test

Environment;

3.

check SDR is healthy, see chapter Check Test

Environment;

ZTE Confidential Proprietary

4.

check default cell configuration and parameters in BSC;

5.

ensure good radio environment;

6.

The test MS has been registered on HLR: MS1 with

37

ZGO-01-03-001 eMLPP

higher priority (PCI=1 and QA=1)., MS2 with lower

priority (PVI=1);

Test Steps

7.

MSC supports emlpp;

8.

Configure cell with adjacent cell.

1.

Set cell property supporting queue, force handover

(Queueind_0= yes and ForceHoInd=0);

2.

MS2 make a call and block other channel which are not
used

Anticipative Result

3.

MS1 make a call.

1.

At step 3, Queuing Indication can be found in SCCP

signalling trace;

2.

At step 3, MS2 will be forcedly handovered to adjacent

cell; Handover Required with Cause: Preemption can
be found in SCCP signalling.

3.

At step 3, MS1 call successfully by occupied the

channel which MS2 occupied before. Assignment
Completed can be found in SCCP signalling.

4.

Test Result

1.

Parameters Setting

Default parameters

6.4

Force handover of CS service performed

successfully.

Feature Turn off

In the configuration resource tree window, double click Configuration Management
Modify Area GSM Logical Configuration Global Information Configuration eMLPP
Configuration, set Support EMLPP to No[0], as shown below.

38

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

Figure 6-6 eMLPP Configuration window

6.5

Network Impact
This feature, when applied, has the following impacts over the network:
1.

Impact on Successful Wireless Connection Rate

If the queuing function is enabled, then the opportunity for obtaining a wireless channel is
increased and the successful wireless connection rate can be increased;
If forced handover is enabled, the system can enable a high-priority user to successfully
access the system and the successful wireless connection rate is increased by handing
over the low-priority users out and release idle channel resources;
If forced release is enabled, the system enables a high-priority user to successfully
access the system and the successful wireless connection rate is increased by forcedly
releasing the low-priority users and idle channel resources.
2.

Impact on Call Drop Rate

The queuing function, if enabled, has no direct impact over the call drop rate.

ZTE Confidential Proprietary

39

ZGO-01-03-001 eMLPP

If forced handover is enabled, the system releases idle channel resources by handing
over the low-priority users out and during this process possibility that the call is dropped
due the failure in handing over the low-priority users out exists, but the probability that the
call is dropped due to the failure in successfully handing over the high-priority user to
another cell is decreased.
If forced release is enabled, the call drop rate increases because call drop is caused to
low-priority users when the system releases idle channel resources by forcedly releasing
low-priority users, but the probability that the call is dropped due to the failure in handing
over the high-priority user decreases.
3.

Impact on Handover

The handover success rate is defined as the ratio of completed handovers to

implemented handovers.
The queuing function, if enabled, has no direct impact over the handover success rate,
but the opportunity for obtaining the target channel to perform handover is increased.
If forced handover is enabled, the system handovers the low-priority user to the adjacent
cell and releases the channel for the high-priority user for assignment or handover, thus
increasing handovers. If the wireless environment is relatively excellent, the handover
success rate is increased, otherwise the handover success rate is decreased.
If forced release is enabled, the system releases the call by a low-priority user to
complete assignment or handover of high-priority user and this increases the opportunity
for performing handovers and has no direct impact over the handover success rate.
4.

Impact On Radio Resource Utilization Efficiency

If a reserved channel is configured, the wireless channel utilization efficiency is

decreased because the reserved channel cannot be occupied by a low-priority user.
If the queuing function is enabled, instant busy traffic is buffered to reduce call loss and
access more traffic, thus increasing the channel utilization efficiency.

40

ZTE Confidential Proprietary

ZGO-01-03-001 eMLPP

If forced handover is enabled, the system releases idle channel resources by handing
over low-priority users out to complete assignment or handover of high-priority user, thus
increasing the channel utilization efficiency.
If forced release is enabled, the system releases idle channel resources by forcedly
releasing the low-priority user to enable the high-priority user to successfully access the
system. Because the high-priority user occupies the channel instead of the low-priority
user, the overall wireless channel utilization efficiency is not influenced, but the
high-priority users preemption of the resources is manifested.
5.

Impact from Applying Different Channel Allocation Policies According to Priorities

Applying different channel allocation policies for users with different priorities can
ensure more appropriate channel utilization when channel resources are limited.

Abbreviation
Abbreviations

Full Characteristics
rd

3GPP

3 Generation Partnership Project

BSC

Base Station Controller

BTS

Base Transceiver Station

BSS

Base Station System

AMR

Adaptive Multi-Rate

FR

Full Rate

GERAN

GSM/EDGE Radio Access Network

HR

Half Rate

GSM

Global System for Mobile communications

MS

Mobile Station

SDCCH

Stand alone dedicated Control Channel

OMC

Operation and Maintenance Center

SACCH

Slow Associated Control Channel

TCH

Traffic Channel

TDMA

Time Division Multiplex Access

ZTE Confidential Proprietary

41

ZGO-01-03-001 eMLPP

Reference Document
ZXG10 iBSC (V6.30.10) Base Station Controller Radio Parameter Reference
ZXG10 iBSC (V6.30.10) Base Station Controller Perfomrance Counter Reference

42

ZTE Confidential Proprietary