You are on page 1of 49

eRAN

Emergency Call Feature Parameter


Description

Issue 01
Date 2016-03-07

HUAWEI TECHNOLOGIES CO., LTD.


Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.


Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com
Email: support@huawei.com

Issue 01 (2016-03-07) Huawei Proprietary and Confidential i


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description Contents

Contents

1 About This Document.................................................................................................................. 1


1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between eNodeB Types.............................................................................................................................. 2

2 Overview of Emergency Call.......................................................................................................3


2.1 Background.....................................................................................................................................................................3
2.2 Introduction.................................................................................................................................................................... 3
2.3 Benefits........................................................................................................................................................................... 4
2.4 Architecture.................................................................................................................................................................... 4

3 CSFB-based Emergency Call....................................................................................................... 7


3.1 Procedure for CSFB-based Emergency Calls.................................................................................................................8
3.2 Emergency Call-related eNodeB Functions................................................................................................................. 10
3.2.1 Identification of Emergency UEs.............................................................................................................................. 10
3.2.2 Admission Control on Emergency UEs.....................................................................................................................10

4 IMS-based Emergency Call....................................................................................................... 12


4.1 Procedure for IMS-based Emergency Calls................................................................................................................. 13
4.1.1 Indicators................................................................................................................................................................... 13
4.1.2 Attach Procedures......................................................................................................................................................13
4.1.3 RRC Connection Setup..............................................................................................................................................14
4.1.4 Bearer Setup.............................................................................................................................................................. 15
4.1.5 Mobility-related Procedures...................................................................................................................................... 16
4.1.5.1 Reselection..............................................................................................................................................................16
4.1.5.2 TAU........................................................................................................................................................................ 16
4.1.5.3 Handover................................................................................................................................................................ 16
4.2 Emergency Call-related eNodeB Functions................................................................................................................. 19
4.2.1 Identification of Emergency UEs.............................................................................................................................. 19
4.2.2 Admission Control on Emergency UEs.....................................................................................................................19
4.2.3 Congestion Control....................................................................................................................................................20
4.2.4 Emergency Call in RAN Sharing Scenarios..............................................................................................................20

5 Related Features...........................................................................................................................22

Issue 01 (2016-03-07) Huawei Proprietary and Confidential ii


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description Contents

6 Network Impact........................................................................................................................... 23
7 Engineering Guidelines............................................................................................................. 24
7.1 When to Use Emergency Call.......................................................................................................................................24
7.2 Required Information................................................................................................................................................... 24
7.3 Network Planning......................................................................................................................................................... 24
7.4 Deployment (CSFB-based Emergency Call)................................................................................................................24
7.4.1 Requirements............................................................................................................................................................. 24
7.4.2 Data Preparation and Feature Activation...................................................................................................................24
7.4.2.1 Data Preparation..................................................................................................................................................... 24
7.4.2.2 Using the CME....................................................................................................................................................... 25
7.4.2.3 Using MML Commands......................................................................................................................................... 25
7.4.3 Precautions.................................................................................................................................................................26
7.4.4 Activation Observation..............................................................................................................................................26
7.4.5 Deactivation...............................................................................................................................................................26
7.4.5.1 Using the CME....................................................................................................................................................... 26
7.4.5.2 Using MML Commands......................................................................................................................................... 26
7.5 Deployment (IMS-based Emergency Call).................................................................................................................. 26
7.5.1 Requirements............................................................................................................................................................. 27
7.5.2 Data Preparation and Feature Activation...................................................................................................................27
7.5.2.1 Data Preparation..................................................................................................................................................... 27
7.5.2.2 Using the CME....................................................................................................................................................... 30
7.5.2.3 Using MML Commands......................................................................................................................................... 30
7.5.3 Precautions.................................................................................................................................................................30
7.5.4 Activation Observation..............................................................................................................................................31
7.5.5 Deactivation...............................................................................................................................................................32
7.5.5.1 Using the CME....................................................................................................................................................... 33
7.5.5.2 Using MML Commands......................................................................................................................................... 33
7.6 Performance Monitoring...............................................................................................................................................33
7.6.1 CSFB-based Emergency Calls...................................................................................................................................33
7.6.2 IMS-based Emergency Calls..................................................................................................................................... 34
7.7 Parameter Optimization................................................................................................................................................ 35
7.8 Troubleshooting............................................................................................................................................................ 35

8 Parameters..................................................................................................................................... 36
9 Counters........................................................................................................................................ 39
10 Glossary....................................................................................................................................... 44
11 Reference Documents............................................................................................................... 45

Issue 01 (2016-03-07) Huawei Proprietary and Confidential iii


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 1 About This Document

1 About This Document

1.1 Scope
This document describes LBFD-002028 Emergency Call, including its technical principles,
related features, network impact, and engineering guidelines.
This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Micro BTS3202E
BTS3911E
BTS3203E

LampSite DBS3900 LampSite

Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.

1.2 Intended Audience


This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 1


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 1 About This Document

1.3 Change History


This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.

eRAN11.1 01 (2016-03-07)
This issue does not include any changes.

eRAN11.1 Draft A (2015-12-30)


Compared with Issue 01 (2015-03-23) of eRAN8.1, Draft A (2015-12-30) of eRAN11.1
includes the following changes.

Change Change Description Parameter Affected


Type Change Entity

Feature None None None


change

Editorial Revised Using the CME in None N/A


change Engineering Guidelines.

1.4 Differences Between eNodeB Types


The features described in this document are implemented in the same way on macro, micro,
and LampSite eNodeBs.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 2


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 2 Overview of Emergency Call

2 Overview of Emergency Call

2.1 Background
An emergency call is a voice service initiated by user equipment (UE) in emergencies. The
emergency telephone number may differ from country to country. It is typically a nationwide
fixed number, for example, 911 in the United States. An emergency telephone number can be
a default number saved in a UE or a number sent by the serving network.
In scenarios of terrorism, medical urgency, fire and other natural disasters, people can dial
emergency telephone numbers for help. A UE can initiate an emergency call without a
Subscriber Identity Module (SIM), Universal SIM (USIM), or IM SIM (ISIM).
In some areas or countries, the operators are ruled to support the emergency call service.

2.2 Introduction
Emergency calls refer to voice services between UEs and the emergency center in emergency
scenarios.
Compared with other services, emergency calls have the following characters:
l High requirement of access success rate. That is, the emergency call service takes
priority over other types of services.
l High requirement of service continuity. That is, emergency UEs enjoy privileges in
terms of mobility management.
l High requirement of positioning precision. That is, the precise position of the UE can
be obtained by the network. The standard precision stipulated by Federal
Communications Commission (FCC) is 50 m to 300 m.
According to section 4.3.12.1 of 3GPP TS 23.401 V10.6.0, an emergency call is generally
made by the following types of users:
l Common user: a normal user who has a valid subscription and can get access to services
normally.
l Common limited user: a normal user who has a valid subscription but cannot get access
to services normally for reasons like the user is not in service areas or the telephone bill
is overdue.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 3


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 2 Overview of Emergency Call

l Limited user with a SIM card: a user whose SIM card fails the authentication. This
type of user makes an emergency call by using the international mobile equipment
identity (IMEI).
l Limited user without a SIM card: a user who does not have a SIM card. This type of
user makes an emergency call by using the IMEI.

2.3 Benefits
This feature enables UEs even without SIMs preferentially to contact with related emergency
centers.

2.4 Architecture
In the LTE system, a call can be an IMS-based VoIP call or a CSFB-based call. IMS, VoIP,
and CSFB are short forms of IP multimedia subsystem, voice over IP, and Circuit Switched
Fallback, respectively. Similarly, an emergency call can be a CSFB-based emergency call or
an IMS-based VoIP emergency call (referred to as IMS-based emergency call in this
document).

CSFB-based Emergency Call


With the CSFB solution, when a UE initiates a CS service, the mobility management entity
(MME) instructs the UE to fall back to the legacy CS network before the UE performs the
service. If operators deploy the evolved packet system (EPS) network without deploying the
IMS network, UEs attempting to initiate emergency calls must fall back to the legacy CS
network first and then initiate emergency calls in the CS network.
This document describes only the differences between the CSFB-based emergency call
procedure and the normal call procedure. For details, see 3.1 Procedure for CSFB-based
Emergency Calls. For details about CSFB, see CS Fallback Feature Parameter Description.

IMS-based Emergency Call


IMS-based emergency calls are emergency calls supported by the IP transmission network
between UEs and the IMS. If an operator has deployed the IMS, UEs in the LTE network can
directly initiate emergency calls.
Figure 2-1 shows the network architecture of the IMS-based emergency call service, which is
the same as that for the normal call service.

Figure 2-1 Network architecture of the IMS-based emergency call service

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 4


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 2 Overview of Emergency Call

E-UTRAN: evolved universal terrestrial GERAN: GSM/EDGE radio access network


radio access network
HSS: home subscriber server PCRF: policy and charging rule function
PSS: packet-switched streaming service SGSN: serving GPRS support node
UTRAN: universal terrestrial radio access
network

In an emergency call, the network elements (NEs) shown in Figure 2-1 provide the following
functions:
l UE
Supports attach, tracking area update (TAU), and detach of emergency calls.
l E-UTRAN
Supports the identification of emergency UEs.
Performs special processing on the admission and mobility management of
emergency UEs.
Participates in the positioning of emergency UEs.
l MME
Supports attach, TAU, and detach of emergency calls.
Supports IMEI-based attach and detach.
Supports the selection of the emergency PDN gateway (P-GW) based on the P-GW
identity, for example, select the local P-GW rather than the home P-GW of the UE.
Assigns a high priority to emergency call bearer setups. For example, the number of
access point name (APN) connections is not limited and no restriction is applied on
the bearer setup.
l P-GW
Sends requests to the PCRF for policy control and transfers the APN provided by the
MME to the PCRF.
l PCRF
Identifies an IP-connectivity access network (IP-CAN) session as the IMS-based
emergency call service based on the APN and then delivers the policy and charging
control (PCC) rules and authentication of emergency calls, ensuring that the
resources are not occupied by other services. For emergency-call APN-related IP
addresses, no subscription data check is performed and the authentication and rules
are delivered according to the operator's local policies.
Controls emergency call bearers, and supports the setup, modification, and deletion
of IP-CAN sessions for the emergency call service by adopting special quality of
service (QoS) policies.
l IMS
Identifies an emergency call based on the destination IP address contained in a
session request and lifts restrictions on the emergency call service.
Controls Session Initiation Protocol (SIP) sessions, and emergency calls, and routes
emergency calls to the correct emergency call center.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 5


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 2 Overview of Emergency Call

Ensures service continuity of emergency calls and provides such functions as


session anchor and session switching from the PS domain to the CS domain.
Provides the location of emergency UEs.

NOTE

If an emergency call is successfully made, a positioning procedure may be initiated by the evolved packet
core (EPC) to acquire the location of the UE. The location of emergency UEs is not provided in this
document.

This document describes only the differences between the IMS-based emergency call
procedure and the normal call procedure, the emergency call-related eNodeB functions, and
related parameters. For details, see 4 IMS-based Emergency Call.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 6


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 3 CSFB-based Emergency Call

3 CSFB-based Emergency Call

This chapter describes the CSFB-based emergency call procedure and the differences on the
eNodeB for implementing emergency calls and normal calls.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 7


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 3 CSFB-based Emergency Call

3.1 Procedure for CSFB-based Emergency Calls


The CSFB procedure defined in sections 7.3 and 7.4 of 3GPP TS 23.272 V10.7.0 is divided
to:
l PS HO Supported procedure, as shown in Figure 3-1.
l Without PS HO procedure, as shown in Figure 3-2.

Figure 3-1 CS call request in E-UTRAN and call in GERAN or UTRAN

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 8


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 3 CSFB-based Emergency Call

Figure 3-2 CS call request in E-UTRAN and call in GERAN or UTRAN without PS HO

The special processing of emergency calls in the CSFB procedure is as follows:


l Step 1a: The NAS Extended Service Request message is sent.
If a UE initiates an emergency call, "mobile originating CS fallback emergency call or
1xCS fallback emergency call" is contained in the IE Service type in the Extended
Service Request message. For details, see section 9.9.3.27 of 3GPP TS 24.301 V10.6.0.
l Step 1b: The messages over S1 interface are sent.
The MME sets the value of the IE CS Fallback Indicator to CS Fallback High Priority.
The IE CS Fallback Indicator is contained in the INITIAL CONTEXT SETUP
REQUEST or UE CONTEXT MODIFICATION REQUEST message over the S1
interface. For details, see section 8.3.1 of 3GPP TS 36.413 V10.5.0.
l Step 3a: The PS HO procedure that is the handover-based CSFB is performed.
Based on the indication of CS Fallback High Priority sent in step 1b, the eNodeB
preferentially processes the emergency call and selects an emergency call-supported CS
network for the UE.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 9


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 3 CSFB-based Emergency Call

3.2 Emergency Call-related eNodeB Functions


In CSFB-based emergency call procedures, after identifying emergency UEs, the eNodeB
preferentially admits the UEs initiating CSFB-based emergency calls, ensuring that the UEs
can successfully fall back to a UTRAN, GERAN, or CDMA2000 1xRTT network.

This document describes only CSFB to GERAN or UTRAN. For details about CSFB to
CDMA2000 1xRTT, see LTE-CDMA2000 CS Service Interworking Feature Parameter
Description

3.2.1 Identification of Emergency UEs


The eNodeB determines whether a CSFB procedure is initiated by an emergency UE or a
common UE based on the value of the IE CS Fallback Indicator in INITIAL CONTEXT
SETUP REQUEST and UE CONTEXT MODIFICATION REQUEST messages delivered by
the MME over the S1 interface. If the value of the IE is CS Fallback High Priority, the
eNodeB considers the CSFB procedure as an emergency-call-triggered CSFB procedure;
otherwise, the eNodeB considers the CSFB procedure as a common-call-triggered CSFB
procedure.

NOTE

If PS handovers are used for CSFB to UTRAN, the eNodeB sends the radio network controller (RNC) a
handover request with CS Fallback High Priority. This request informs the RNC that this CSFB
procedure is triggered by an emergency call so that the RNC preferentially processes this call.

3.2.2 Admission Control on Emergency UEs

Licensed User Number-based Admission Control


Generally, the ARP value of a radio bearer of a UE is allocated by the EPC. If a UE initiates a
CSFB procedure, the EPC allocates a lower ARP value for the bearer of the UE. When the
licensed number of UEs is limited, such a UE will experience an admission failure due to low
ARP value.

To increase the admission success rate of emergency UEs initiating CSFB procedures, the
ARP value for bearers of such UEs can increase. The
CsFallbackPolicyCfg.CsfbUserArpCfgSwitch parameter determines whether to set the ARP
value for emergency UEs initiating CSFB procedures. When this parameter is set to ON(On),
the IEs contained in the ARP values of default bearers for emergency UEs initiating CSFB
procedures are configured as follows:

l Priority Level
The value of this IE is 1.
l Pre-emption Capability
The value of this IE is may trigger pre-emption, indicating that the UEs can preempt
resources of other low-priority UEs.
l Pre-emption Vulnerability
The value of this IE is not pre-emptable, indicating that resources of the UEs cannot be
preempted by other UEs.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 10


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 3 CSFB-based Emergency Call

Licensed eNodeB Traffic-based Admission Control


If the admission is based on the licensed traffic volume of the eNodeB, emergency UEs
initiating CSFB procedures are directly admitted.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 11


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

4 IMS-based Emergency Call

Compared with common UEs, emergency UEs have higher priorities. This chapter describes
special processes of emergency calls on the eNodeB. The special processes ensure preferential
admission of emergency UEs and service continuity of emergency calls.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 12


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

4.1 Procedure for IMS-based Emergency Calls


Compared with the procedure for the normal voice service, the procedure for the IMS-based
emergency call service incorporates more special processing. This section describes the
special processing of IMS-based emergency calls based on the normal call procedure.

Emergency call services require the support from the EPC. eNodeBs identify emergency call
services and perform special processing such as assigning higher priorities to emergency call
services. If an emergency call is initiated, a default bearer and a dedicated bearer are set up for
special use of this emergency call. The bearers for emergency calls are associated with
emergency APNs.

4.1.1 Indicators
A UE must be notified of whether a network supports IMS-based emergency calls so that the
UE can determine whether to initiate an IMS-based emergency call or initiate a CSFB-based
emergency call in emergencies. During the attach procedure, if the UE detects that the
accessed network does not support emergency calls, the UE select another network supporting
emergency calls to access.

Whether a network supports emergency calls is determined by the local regulations and
operating policies of the operator.

UEs in the Normal Service State


UEs in the normal service state refer to UEs that are in a suitable cell and available for public
use. The UEs determine whether the network supports emergency calls based on the value of
the IE Emergency Number List in the Attach/TAU Accept message delivered by the MME.

UEs in the Limited Service State


UEs in the limited service state refer to UEs that are in an acceptable cell and only available
for emergency calls and earthquake and tsunami warning system (ETWS). The UEs determine
whether the network supports emergency calls based on the value of the IE ims-
EmergencySupport contained in system information block type 1 (SIB1).

The Emc.EmcEnableInLimitedMode parameter specifies whether the network supports


emergency calls for UEs in the limited service state. If the parameter is set to ON(On), the
value of the IE ims-EmergencySupport contained in SIB1 is true, indicating that the UEs in
the limited service state are allowed to initiate emergency calls in the network. If the
parameter is set to OFF(Off), the UEs select or reselect a cell that supports the emergency
call service in any RAT to camp on.

4.1.2 Attach Procedures

Normal Attach
A UE in the normal service state attaches to the network normally after initiating an
emergency call. For details about procedures for normal attach, see Idle Mode Management
Feature Parameter Description.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 13


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

Emergency Attach
A UE enters the limited service state if the UE encounters a failure of normal attach or TAU,
or the UE does not initiate attach attempts (for example, the UE is universal integrated circuit
card-less [UICC-less]). A UE in the limited service state performs emergency attach when it
initiates an emergency call. The emergency attach allows the UE to skip the authentication
procedure with the EPC, ensuring successful attach.
According to section 5.3.2 of 3GPP TS 23.401 V10.6.0, the emergency attach procedure is
based on a normal attach procedure but includes the following special processing.
l An emergency attach indicator is contained in the Attach Request message. Based on this
indicator, the MME performs such special processing as authentication cancellation.
l If the IMSI is unavailable or invalid, as in the case of a UICC-less UE or subscription-
expired UE, the IMEI of the emergency UE is contained in the Attach Request message
for the network to identify the UE.
l The authentication procedure can be skipped for UEs in the limited service state if local
regulations permit.

Emergency PDN Connection


According to the description of non-access stratum (NAS) in section 5.5 of 3GPP TS 24.301
V10.6.1 and 3GPP TS 24.008 V10.6.1, the MME delivers a local emergency call number list
to the UE when the UE attaches to the network, which is then saved by the UE. In this way,
the UE can obtain local emergency call numbers when roaming to a different area. This helps
the UE identify emergency calls. The preceding function depends on the capabilities of UEs
and MMEs.
For a UE in the normal service state, an emergency PDN connection procedure is initiated
when the UE attaches to the network normally and then initiates an emergency call. When a
UE detects that an emergency call is initiated, it sets up a PDN connection using the
emergency APN. For details about the PDN connection procedure, see section 5.10.2 of 3GPP
TS 23.401 V10.6.0. The following special processing is performed for an emergency PDN
connection procedure:
l The request type indicated in the PDN Connectivity Request message is emergency.
l The emergency configuration data configured on the MME is used for setting up default
bearers.
NOTE

For details on emergency configuration data, see section 5.7.2 of 3GPP TS 23.401 V10.7.0.

4.1.3 RRC Connection Setup


Figure 4-1 shows a successful RRC connection setup procedure. For details, see section 5.3.3
of 3GPP TS 36.331 V10.5.0.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 14


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

Figure 4-1 Successful RRC connection setup procedure

If the value of the IE establishmentCause contained in the RRCConnectionRequest message is


emergency, the UE is an emergency UE.
Emergency calls have a high priority. In the RRC connection setup procedure, the eNodeB
preferentially processes the RRCConnectionRequest messages sent by emergency UEs. The
eNodeB still sets up RRC connections for emergency calls even in MME overload scenarios.
If an MME is overloaded, it initiates the OVERLOAD START procedure, as shown in Figure
4-2. For details about the procedure, see section 8.7.6 of 3GPP TS 36.413 V10.5.0.

Figure 4-2 MME overload indication

The MME indicates the allowed and rejected services to eNodeBs. In the S1-
AP:OVERLOAD START message, the MME specifies the requests that the eNodeB should
accept or reject. For example, the eNodeB may be required to:
l Reject RRC connection setup requests for non-emergency mobile-originated data
transfer.
l Reject RRC connection setup requests for signaling services.
l Allow RRC connection setup requests for only emergency calls (mobile-originated or
mobile-terminated).
l Allow RRC connection setup requests for high-priority calls (with the RRC
establishment cause value "highPriorityAccess") and mobile-terminated calls (with the
RRC establishment cause value "mt-Access").
l Reject RRC connection setup requests for delay-tolerant services (with the RRC
establishment cause value "delayTolerantAcess")

4.1.4 Bearer Setup


The EPS bearer setup procedure is described in section 5.4 of 3GPP TS 23.401 V10.6.0. If an
E-UTRAN radio access bearer (E-RAB) is used for carrying an emergency call, some special

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 15


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

mechanisms are applied on this E-RAB. For example, this bearer can set up in scenarios of
limited resources, and high ARP is set for this bearer.

The eNodeB can perform admission control on an EPS bearer for an emergency call based on
QoS parameters and the EPC allocates the reserved ARP for the bearer. If the eNodeB has
insufficient resources, the ARP ensures that an emergency UE can preempt the resources of
low-priority UEs.

After an emergency call is initiated, a default E-RAB and a dedicated E-RAB are set up for
specific use of this emergency call.

l The default E-RAB, different from the one set up during the normal attach procedure, is
exclusively used by the emergency call.
l The dedicated E-RAB is used to carry the VoIP session for the emergency call.

Currently, one Huawei eNodeB can be shared by multiple operators. This function is known
as RAN sharing. In RAN sharing scenarios, to enable operators sharing one eNodeB to adopt
different emergency call strategies, parameters Emc.EmcDefaultBearerARP and
Emc.EmcDedicatedBearerARP specify ARP values for the default E-RABs and dedicated E-
RABs for emergency calls, respectively.

4.1.5 Mobility-related Procedures

4.1.5.1 Reselection
For a UE in the limited service state, the mobility of the UE in RRC_IDLE mode is
determined by the emergency call indicators described in 4.1.1 Indicators. If information in
SIB1 indicates that the cell does not support IMS-based emergency calls, the UE selects or
reselects to a cell supporting IMS-based emergency calls in any RAT to camp on.

4.1.5.2 TAU
The EPC uses an explicit context that is a special ARP to indicate an ongoing emergency call.
The TAU procedure defined in section 5.3.3 of 3GPP TS 23.401 V10.6.0 uses special
mechanisms for emergency UEs. If the network supports emergency UEs in the limited
service state, the TAU must succeed in case of emergency calls.

According to the description of NAS in section 8.2.26.1 of 3GPP TS 24.301 V10.6.1 and
3GPP TS 24.008 V10.6.1, the MME delivers a local emergency call number list to the UE
that is performing TAU, and then the list is saved by the UE. In this way, the UE can obtain
local emergency call numbers when roaming to a different area. This helps the UE identify
emergency calls. The preceding function depends on the capabilities of UEs and MMEs.

4.1.5.3 Handover
A mobility restriction function is introduced to the E-UTRAN. If a UE is in
RRC_CONNECTED mode, the EPC provides a handover restriction list (HRL) to the E-
UTRAN. In addition, the E-UTRAN and the EPC enable the mobility restriction function to
prevent the UE being handed over to an area listed in the HRL. To prevent the interruption of
emergency calls and to ensure the successful handover to an area listed in the HRL, special
mechanisms are applied, with which only emergency calls are allowed to be handed over to
the areas listed in the HRL.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 16


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

Coverage-based Handovers
Coverage-based handovers are fundamental to ensuring service continuity of moving UEs. As
a basic function, coverage-based handovers are classified as intra-frequency, inter-frequency,
and inter-RAT handovers.
Emergency UEs have the highest priority. Therefore, to ensure the stability and continuity of
emergency calls, emergency UEs can be handed over to any cells without restrictions. For
example, they can be handed over to the neighboring cells such as cells with NoHoFlag set to
FORBID_HO_ENUM(Forbid Ho), blacklisted neighboring cells and neighboring cells in an
area listed in the HRL. For details, see Overview of Mobility Management in Connected Mode
Feature Parameter Description.

Load-based Handovers
Load-based handovers are effective in ensuring service continuity when the local cell is
heavily loaded (or even congested) but the neighboring cells are lightly loaded. By requesting
lightly loaded neighboring cells to take away a proportion of UEs through negotiation, the
local cell transfers part of its load to its neighboring cells. Thereby, the inter-cell loads are
balanced and the resource utilization is maximized.
However, load-based handovers often induce a high probability of service drops. To ensure
the stability and continuity of emergency calls, the eNodeB will not apply load-based
handovers to emergency UEs.

SRVCC-based Handovers
The single radio voice call continuity (SRVCC) procedure ensures the continuity between
IMS-based VoIP calls and CS voice calls. For details, see 3GPP TS 23.216 V10.3.0.
According to 3GPP specifications, eNodeBs process the SRVCC procedure for emergency
calls in the same way as that for normal calls. Therefore, this document does not describe the
implementation of the SRVCC procedure for emergence calls.
Figure 4-3 shows the SRVCC procedure.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 17


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

Figure 4-3 SRVCC from E-UTRAN to UTRAN or GERAN with DTM HO support

During the E-UTRAN-initiated SRVCC procedure for emergency calls, the MME identifies
bearers for emergency calls based on the ARP value and then sends an indicator to the MSC.
The MSC initiates an IMS service continuity procedure using an emergency session transfer
number for SRVCC (E-STN-SR) to the served IMS. For details about the E-STN-SR, see
section 6c.2 of 3GPP TS 23.237 V10.9.0. When the emergency UE is handed over, the MME
initiates a positioning continuity procedure that is defined in 3GPP TS 23.271 V10.2.0.

Compared with the normal SRVCC procedure, the special processing of emergency calls in
the SRVCC procedure for emergency is as follows:

l Step 5a: The PS to CS Req message is sent.


The source MME sends the PS to CS Req message containing the emergency call
indicator to the MSC. If the UE is in the limited service state, the MME includes the user
identifiers in the message. If the UE has the IMSI or the mobile subscriber ISDN number
(MSSIDN), the IMSI and the MSSIDN are included. Otherwise, the IMEI is included.
l Step 9: The session transfer procedure is initiated.
The MSC initiates the session transfer procedure using the E-STN-SR. For details, see
section 6c.2 of 3GPP TS 23.237 V10.9.0.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 18


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

l Step 19: The subscriber location report is sent.


When the UE is handed over, the source MME or the corresponding MSC sends the
Subscriber Location Report message to the gateway mobile location center (GMLC) to
support the positioning continuity. For details, see 3GPP TS 23.271 V10.2.0.
In the SRVCC procedure for emergency calls, only UEs and MMEs perform special
processing on emergency calls, whereas eNodeBs do not.

4.2 Emergency Call-related eNodeB Functions

4.2.1 Identification of Emergency UEs


The eNodeB identifies a UE as an emergency UE if one of the following conditions is met:
l The value of the IE EstablishmentCause in the RRC Connection Request message is
emergency.
l The ARP value of a default E-RAB is the same as the Emc.EmcDefaultBearerARP
parameter value. This ARP is sent by the EPC to the eNodeB.
l The ARP value of a dedicated E-RAB is the same as the Emc.EmcDedicatedBearerARP
parameter value. This ARP is also sent by the EPC to the eNodeB.

4.2.2 Admission Control on Emergency UEs

Radio-Resource-based Admission Control and Transport-Resource-based


Admission Control
There are two types of admission control: admission control over radio resources and
admission control over transport resources.
Emergency UEs have the highest priority during admission control when accessing or being
handed over to a cell. This is achieved by assigning the highest priority to the default and
dedicated E-RABs for emergency calls. Besides, the following special mechanisms apply to
emergency UEs:
l Radio-resource-based admission control
Emergency UEs are directly admitted without considering UE capabilities and resource
sufficiency.
l Transport-resource-based admission control
Whether emergency UEs are preferentially admitted is set by the
TACALG.EMCTACPSW parameter:
When this parameter is set to ON(On), emergency UEs are directly admitted. In
this case, a certain bandwidth must be reserved for emergency UEs to ensure the
success of direct admission.
Larger bandwidth can be reserved by lowering the admission thresholds for uplink
and downlink gold, silver, and bronze subscribers and handed-over UEs to make
these subscribers and UEs harder to access the network. For details about the
thresholds, see Transport Resource Management Feature Parameter Description.
When this parameter is set to OFF(Off), emergency UEs are admitted based on
admission thresholds for incoming handover services. If an emergency UE fails to

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 19


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

be admitted, it preempts the resources of other admitted non-emergency UEs


regardless of whether transport resource preemption switches are turned on.
For details about preemption priorities, see Admission and Congestion Control Feature
Parameter Description and Transport Resource Management Feature Parameter Description.

UE-Number-Reservation-based Access Control


If the admission is based on the number of UEs, UE numbers can be reserved for privileged
UEs to improve the admission success rate of these UEs. Privileged UEs include emergency
UEs and high-priority UEs whose cause value of RRC connection establishment request is
"highPriorityAccess". Other UEs are common UEs.
Privileged UEs are defined because resource preemption is not allowed for operators in some
countries and areas by local regulations but high-priority UEs of these operators need to be
preferentially admitted. Admission for privileged UEs based on the reservation of UE
numbers is enabled for these operators in compliance with local regulations.
UE numbers within the maximum number of UEs supported by the cell are reserved for
privileged UEs. The number of emergency UEs that can be admitted is restricted only by the
maximum number of UEs supported by the cell rather than by the licensed number of UEs so
that emergency UEs can preferentially be admitted.
Admission for privileged UEs based on the reservation of UE numbers is set by the
CellRacThd.AcReservedUserNumber parameter:
l When this parameter is set to 0, the admission for privileged UEs is disabled. The
eNodeB admits both privileged UEs and common UEs based on the maximum number
of UEs supported by the cell.
l When this parameter is set to a non-zero value, the admission for privileged UEs based
on the reservation of UE numbers is enabled. The eNodeB admits privileged UEs and
common UEs based on different UE number requirements.
The number of privileged UEs that are allowed to be admitted is based on the
maximum number of UEs supported by the cell.
The number of common UEs that are allowed to be admitted is the difference
between the maximum number of UEs supported by the cell and the
CellRacThd.AcReservedUserNumber parameter value. The
CellRacThd.AcReservedUserNumber parameter value indicates the reserved UE
numbers for privileged UEs.

4.2.3 Congestion Control


By releasing some bearer resources, congestion control reduces the load on an eNodeB and
therefore ensures the QoS of the other services.
However, as the stability and continuity of emergency calls are the top concern, the eNodeB
will not release the default and dedicated bearers for emergency calls as a congestion relief
action.

4.2.4 Emergency Call in RAN Sharing Scenarios


Different parameter settings related to emergency calls can be configured for different
operators.
The IE ims-EmergencySupport in SIB1 does not distinguish operators. If one operator
supports IMS-based emergency calls (that is, the Emc.EmcEnableInLimitedMode parameter

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 20


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 4 IMS-based Emergency Call

is set to ON(On)), the eNodeB sets the IE ims-EmergencySupport value to true. To prevent
UEs in the limited service state from accessing PLMNs that do not support emergency calls,
the Emc.EmcEnableInLimitedMode parameter value for all operators must be the same.
eNodeBs process emergency calls based on the PLMNs selected by UEs.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 21


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 5 Related Features

5 Related Features

Prerequisite Features
Feature ID Feature or Function Description
Name

N/A Support for IMS-based The IMS-based emergency call service


VoIP by the UE and requires the UE and EPC to support
EPC IMS-based VoIP.

LOFD-001033 CS Fallback to UTRAN The CSFB-based emergency call


service requires the CSFB features.
LOFD-001034 CS Fallback to GERAN

LOFD-001022 SRVCC to UTRAN The SRVCC-based emergency call


service requires the SRVCC features.
LOFD-001023 SRVCC to GERAN

LOFD-001047 LoCation Services If the EPC requires the location


(LCS) information of emergency UEs, the
optional feature LOFD-001047
LoCation Services (LCS) is required.

Mutually Exclusive Features


None

Impacted Features
Feature ID Feature or Function Description
Name

N/A TM2 transmission mode To improve the access success rate and
and semi-persistent ensure service stability for emergency
scheduling UEs, the eNodeB uses the TM2
transmission mode and does not
configure semi-persistent scheduling.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 22


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 6 Network Impact

6 Network Impact

System Capacity
No impact.

Network Performance
No impact.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 23


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

7 Engineering Guidelines

7.1 When to Use Emergency Call


If an operator does not deploy the IMS network, the CSFB-based emergency call is
recommended.

If an operator has the IMS network deployed, the IMS-based emergency call is recommended.

7.2 Required Information


The ARP values of the default and dedicated bearers for emergency calls must be acquired.

7.3 Network Planning


Not involved.

7.4 Deployment (CSFB-based Emergency Call)

7.4.1 Requirements
If CSFB-based emergency call is enabled, UEs must support CSFB and related CSFB features
must be enabled on the eNodeB. For details about how to enable CSFB features, see CS
Fallback Feature Parameter Description.

7.4.2 Data Preparation and Feature Activation

7.4.2.1 Data Preparation


There are three types of data sources:

l Network plan (negotiation not required): parameter values planned and set by the
operator

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 24


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
(Optional) The following table describes the parameter that must be set in the
CsFallbackPolicyCfg MO to configure the ARP values of bearers for emergency UEs
initiating CSFB procedures.
When the number of UEs requesting to access the eNodeB reaches the licensed number of
UEs, the following parameter can be set to ensure a high priority for emergency UEs initiating
CSFB procedures.

Paramete Parameter ID Source Setting Notes


r Name

Csfb User CsFallbackPolicy Engineering This parameter specifies whether the


Arp Cfg.CsfbUserArpC design ARP value is allowed to be configured
Configurat fgSwitch for bearers of common UEs initiating
ion Switch CSFB procedures.
l If this parameter is set to ON(On),
you can configure ARP values of
bearers for common UEs initiating
CSFB procedures. The ARP value of
bearers for emergency UEs initiating
CSFB procedures is always 1,
indicating that these UEs can
preempt resources of other UEs with
lower priorities and the resources of
these UEs cannot be preempted.
l If this parameter is set to OFF(Off),
the ARP values of bearers for
common UEs and emergency UEs
and the preemption policies take
effect based on the configuration on
the EPC.
Recommended value: OFF(Off)

7.4.2.2 Using the CME


For detailed operations, see CME-based Feature Configuration.

7.4.2.3 Using MML Commands

Using MML Commands


(Optional) Run the MOD CSFALLBACKPOLICYCFG command with the Csfb User Arp
Configuration Switch parameter set.

MML Command Examples


MOD CSFALLBACKPOLICYCFG:CsfbUserArpCfgSwitch=1;

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 25


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

7.4.3 Precautions
None

7.4.4 Activation Observation


On the U2000 client, start the measurement of the counters listed in Table 7-1. If a UE has
initiated an emergency call during the measurement period and the values of the counters are
not zero, the CSFB-based emergency call feature has been activated.

Table 7-1 Counters related to CSFB-based emergency calls


Counter ID Counter Name Description

1526728709 L.CSFB.E2W.Emergency Number of EUTRAN-to-WCDMA CSFB


executions for emergency calls

1526728710 L.CSFB.E2G.Emergency Number of EUTRAN-to-GERAN CSFB


executions for emergency calls

7.4.5 Deactivation
The following table provides the parameter used to deactivate this feature.

Table 7-2 Emergency call parameter


MO Parameter ID Setting Notes

CsFallbackPolicyCfg CsfbUserArpCfgSwitch Set this parameter to OFF(Off).

This feature can be deactivated using the CME or MML commands.

7.4.5.1 Using the CME


For detailed operations, see CME-based Feature Configuration.

7.4.5.2 Using MML Commands

Using MML Commands


(Optional) Run the MOD CSFALLBACKPOLICYCFG command with the Csfb User Arp
Configuration Switch parameter set.

MML Command Examples


MOD CSFALLBACKPOLICYCFG:CsfbUserArpCfgSwitch=0;

7.5 Deployment (IMS-based Emergency Call)

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 26


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

7.5.1 Requirements
Before deploying IMS-based emergency call, ensure that UEs, the EPC, and IMS support
IMS-based emergency call.

7.5.2 Data Preparation and Feature Activation

7.5.2.1 Data Preparation


There are three types of data sources:

l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users

The following table describes the parameters that must be set in an Emc MO to configure the
IMS-based emergency call strategy for an operator of the eNodeB.

Parameter Parameter Source Setting Notes


Name ID

CN Emc.CnOpera Radio Set this parameter based on the network


Operator torId planning plan.
ID (internal
planning)

Emergency Emc.EmcEna Engineering This parameter specifies whether the


call ble design eNodeB can identify emergency UEs and
enabled apply special mechanisms to emergency
switch UEs. The setting of this parameter must be
consistent with the configuration of the
EPC.
l If this parameter is set to ON(On) but
the EPC does not support emergency
calls, the network does not support
emergency calls.
l If this parameter is set to OFF(Off) but
the EPC supports emergency calls, the
network supports emergency calls.
However, in this case, the eNodeB
cannot identify emergency UEs and
therefore cannot apply special
mechanisms to emergency UEs.
Settings of Emc.EmcEnableInLimited-
Mode, Emc.EmcDedicatedBearerARP, and
Emc.EmcDefaultBearerARP take effect
only when the Emc.EmcEnable parameter
is set to ON(On).

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 27


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

Parameter Parameter Source Setting Notes


Name ID

The ARP Emc.EmcDedi Engineering This parameter specifies the ARP value of
of EMC catedBearerA design the dedicated bearers for emergency calls.
dedicated RP The setting of this parameter must be
bearer consistent with the configuration of the
EPC.
This ARP value is reserved by the operator.
The ARP value of the dedicated bearers for
emergency calls can be the same as that of
the default bearers for emergency calls.
It is recommended that the ARP value of
the default bearer assigned during
subscription not be the same as that of the
default or dedicated bearer for emergency
calls; otherwise, all services of the user will
be considered and processed as emergency
calls.

The ARP Emc.EmcDef Engineering This parameter specifies the ARP value of
of EMC aultBearerAR design the default bearers for emergency calls. The
default P setting of this parameter must be consistent
bearer with the configuration of the EPC.
This ARP value is reserved by the operator.
The ARP value of the default bearers for
emergency calls can be the same as that of
the dedicated bearers for emergency calls.
It is recommended that the ARP value of
the default bearer assigned during
subscription not be the same as that of the
default or dedicated bearer for emergency
calls; otherwise, all services of the user will
be considered and processed as emergency
calls.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 28


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

Parameter Parameter Source Setting Notes


Name ID

Emergency Emc.EmcEna Engineering This parameter specifies whether the


call bleInLimited design eNodeB supports emergency calls initiated
enabled Mode by UEs in the limited service mode. If the
switch in eNodeB supports such emergency calls, the
limited eNodeB will notify UEs of this fact using
mode the IE ims-EmergencySupport-r9 in SIB1.
The setting of this parameter must be
consistent with the configuration of the
EPC.
l If this parameter is set to ON(On) but
the EPC does not support emergency
calls initiated by UEs in the limited
service state, the eNodeB does not
support such emergency calls and the
emergency calls initiated by UEs in the
limited service state fail.
l If this parameter is set to OFF(Off) but
the EPC supports emergency calls
initiated by UEs in the limited service
state, the eNodeB does not support such
emergency calls and UEs in the limited
service state cannot camp on the cells
provided by the eNodeB.

(Optional) The following table describes the parameter that must be set in the TACALG MO
to configure the preferential admission switch for emergency UEs under transport-resource-
based admission control.
If the TACALG.EMCTACPSW parameter is set to ON(On) and uplink and downlink
transmission admission control algorithms are enabled in scenarios where transmission
bandwidth is limited, the admission success rate of emergency UEs increases.

Paramete Parameter Source Setting Notes


r Name ID

Emergenc TACALG.E Network plan This parameter specifies whether the


y Call MCTACPSW (negotiation emergency UEs are preferentially admitted.
Preferenti not required) If this parameter is set to ON(On),
al transport-resource-based admission control
Admission is not performed for emergency calls and
Switch emergency calls will be directly successfully
admitted. If this parameter is set to
OFF(Off) and the transmission admission
algorithms are enabled, transport-resource-
based admission control is performed for
emergency calls. Recommended value:
OFF(Off)

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 29


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

(Optional) The following table describes the parameter that must be set in the CellRacThd
MO to configure the preferential admission switch for privileged UEs under UE-number-
reservation-based admission control. When the maximum number of UEs supported by the
cell is limited, UE numbers are reserved for emergency UEs. This ensures that emergency
calls are successfully connected and resources of admitted UEs performing voice services are
not preempted by emergency UEs.

Paramete Parameter Source Setting Notes


r Name ID

Admission CellRacTh Engineering design This parameter specifies the UE


Control d.AcReserv numbers in a cell reserved for
Reserved edUserNu privileged UEs (including
User mber emergency UEs and high-
Number priority UEs). If this parameter
is set to 0, no resource is
reserved for privileged UEs. If
this parameter is set to a non-
zero value, the value represents
the specifications of UE
numbers reserved for privileged
UEs. Recommended value: 0

7.5.2.2 Using the CME


For detailed operations, see CME-based Feature Configuration.

7.5.2.3 Using MML Commands

Using MML Commands


l Run the MOD EMC command with emergency call parameters set.
l (Optional) Run the SET TACALG command to turn on the preferential admission
switch for emergency UEs under transport-resource-based access control.
l (Optional) Run the MOD CELLRACTHD command to modify parameters related to
preferential admission for privileged UEs under UE-number-reservation-based access
control.

MML Command Examples


MOD
EMC:CNOPERATORID=0,EMCENABLE=ON,EMCENABLEINLIMITEDMODE=ON,EMCDEDICATEDBEARERARP=2,
EMCDEFAULTBEARERARP=1;
SET TACALG:EMCTACPSW=ON;
MOD CELLRACTHD:LOCALCELLID=0,AcReservedUserNumber=2;

7.5.3 Precautions
The settings of emergency call-related parameters must be consistent with the configurations
on the EPC; otherwise, emergency call services are affected. Table 7-3 describes the impacts
on emergency call services due to inconsistent parameter settings on the eNodeB and EPC.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 30


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

Table 7-3 Impacts on emergency call services

EPC eNodeB eNodeB Supports Impacts on Emergency Call


Supports Supports Emergency Calls Services
Emergency Emergency Initiated by UEs in
Calls or Not Calls or Not the Limited
Service State or
Not

No Yes No UEs cannot initiate emergency


calls.

Yes Yes l UEs in the normal service


state cannot initiate
emergency calls.
l UEs in the limited service
state can initiate IMS-based
emergency calls, but the
calls fail.

Yes No Yes or No UEs in the normal service state


can initiate emergency calls.
However, the eNodeB cannot
identify emergency UEs and
therefore will not apply special
processing to emergency UEs.

Yes No l UEs in the limited service


state cannot initiate IMS-
based emergency calls.
l UEs in the normal service
state can initiate IMS-based
emergency calls.

Yes Yes Both UEs in the normal service


state and UEs in the limited
service state can initiate
emergency calls.

7.5.4 Activation Observation

Using MML Commands


On the U2000, run the LST EMC command. If the Emergency call enabled switch
parameter value is On, the emergency call feature has been activated.

Using Signaling Tracing


To use Uu signaling tracing to verify whether the emergency call feature has been activated,
perform the following steps:

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 31


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

Step 1 On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.

Step 2 In the navigation tree on the left of the Signaling Trace Management tab page, double-click
Uu Interface Trace under LTE > Application Layer.
Step 3 Create and start a Uu interface tracing task.

Step 4 View the tracing result. If the value of the IE ims-EmergencySupport-r9 is true(0) in SIB1,
the emergency call feature has been activated.

Figure 7-1 Uu interface tracing result

----End

Checking the Counter Values


On the U2000 client, start the measurement of the counters listed in Table 7-4. If a UE has
initiated an emergency call during the measurement period and the values of the counters are
not zero, the IMS-based emergency call feature has been activated.

Table 7-4 Counters related to IMS-based emergency calls


Counter ID Counter Name Description

1526728217 L.RRC.ConnReq.Att.Emc Number of RRC connection setup


attempts with a cause value of emergency
(retransmissions excluded)

1526728167 L.EMC.E-RAB.AttEst Number of E-RAB setup attempts for


emergency calls in a cell

7.5.5 Deactivation
The following table provides the parameters used to deactivate this feature.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 32


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

Table 7-5 Emergency call parameters


MO Parameter ID Setting Notes

Emc EmcEnable Set this parameter to OFF(Off).

TACALG EMCTACPSW Set this parameter to OFF(Off).

CellRacThd AcReservedUserNumber Set this parameter to 0.

This feature can be deactivated using the CME or MML commands.

7.5.5.1 Using the CME


For detailed operations, see CME-based Feature Configuration.

7.5.5.2 Using MML Commands

Using MML Commands


l Run the MOD EMC command with the Emergency call enabled switch parameter set
to OFF(Off).
l (Optional) Run the SET TACALG command with the Emergency Call Preferential
Admission Switch parameter set to OFF(Off).
l (Optional) Run the MOD CELLRACTHD command with the Admission Control
Reserved User Number parameter set.

MML Command Examples


MOD EMC:CNOPERATORID=0,EMCENABLE=OFF;
SET TACALG:EMCTACPSW=OFF;
MOD CELLRACTHD:LOCALCELLID=0,AcReservedUserNumber=0;

7.6 Performance Monitoring

7.6.1 CSFB-based Emergency Calls


Monitor the counters listed in Table 7-6 on the U2000 to evaluate the performance of CSFB-
based emergency calls.

Table 7-6 Counters related to CSFB-based emergency calls


Counter Name Description

L.CSFB.PrepAtt.Emergency Number of CSFB triggering attempts for


emergency calls received by the eNodeB

L.CSFB.PrepSucc.Emergency Number of CSFB procedures for emergency


calls that the eNodeB has responded to

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 33


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

The response success rate to CSFB-based emergency calls is calculated as follows:

7.6.2 IMS-based Emergency Calls


Monitor the counters listed in Table 7-7 on the U2000 to evaluate the performance of IMS-
based emergency calls. The counters can be used to calculate emergency call-related key
performance indicators (KPIs), which can be further used to evaluate network performance of
IMS-based emergency calls.

Table 7-7 Counters related to IMS-based emergency calls

Counter ID Counter Name Description

1526728217 L.RRC.ConnReq.Att.Emc Number of RRC connection setup


attempts with a cause value of
emergency (retransmissions
excluded)

1526728222 L.RRC.ConnReq.Succ.Emc Number of RRC Connection Setup


Complete messages with a cause
value of emergency received from
UEs in a cell

1526728164 L.EMC.HHO.ExecSuccOut Number of successful intra-duplex-


mode outgoing handovers for
emergency calls in a cell

1526728162 L.EMC.HHO.PrepAttOut Number of intra-duplex-mode


outgoing handover attempts for
emergency calls in a cell

1526729601 L.EMC.HHO.InterFddTdd.E Number of successful inter-duplex-


xecSuccOut mode outgoing handovers for
emergency calls in a cell

1526729599 L.EMC.HHO.InterFddTdd.P Number of inter-duplex-mode


repAttOut outgoing handover attempts for
emergency calls in a cell

1526728168 L.EMC.E-RAB.SuccEst Number of successful E-RAB setups


for emergency calls in a cell

1526728167 L.EMC.E-RAB.AttEst Number of E-RAB setup attempts


for emergency calls in a cell

Emergency call-related KPIs are calculated as follows:

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 34


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 7 Engineering Guidelines

l
If KPIs in a cell do not meet requirements, check the cell status and perform network
optimization.

7.7 Parameter Optimization


None

7.8 Troubleshooting
None

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 35


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 8 Parameters

8 Parameters

Table 8-1 Parameters


MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd

CSFallB CsfbUse MOD LBFD-0 Admissi Meaning: Indicates whether allocation/retention


ackPolic rArpCfg CSFAL 02023 / on priorities (ARPs) can be configured for CSFB services
yCfg Switch LBACK TDLBF Control triggered by common calls. For details about ARPs,
POLIC D-00202 see 3GPP TS 23.401.
YCFG 3 GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CSFAL
LBACK Actual Value Range: OFF, ON
POLIC Default Value: OFF(Off)
YCFG

Emc EmcEna MOD LBFD-0 Emerge Meaning: Indicates whether the operator supports
bleInLi EMC 02028 / ncy Call emergency calls initiated by UEs in the limited service
mitedM LST TDLBF state.
ode EMC D-00202 GUI Value Range: OFF(Off), ON(On)
8
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)

Emc EmcDef MOD LBFD-0 Emerge Meaning: Indicates the Allocation and Retention
aultBear EMC 02028 / ncy Call Priority (ARP) value of the default emergency call
erARP LST TDLBF bearer.
EMC D-00202 GUI Value Range: 1~15
8
Unit: None
Actual Value Range: 1~15
Default Value: 1

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 36


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 8 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

Emc EmcDed MOD LBFD-0 Emerge Meaning: Indicates the Allocation and Retention
icatedBe EMC 02028 / ncy Call Priority (ARP) value of the dedicated emergency call
arerARP LST TDLBF bearer.
EMC D-00202 GUI Value Range: 1~15
8
Unit: None
Actual Value Range: 1~15
Default Value: 1

TACAL EMCTA SET LOFD-0 Transpo Meaning: Indicates the switch that is used to
G CPSW TACAL 0301101 rt preferentially admit emergency calls. When this
G / Overboo parameter is set to ON, transmission admission
LST TDLOF king control is not performed for emergency calls and
TACAL D-00301 Emerge emergency calls will be successfully admitted. When
G 101 ncy Call this parameter is set to OFF and the transmission
LBFD-0 admission algorithm switch is turned on, transmission
02028 / admission control is performed for emergency calls.
TDLBF When this parameter is set to OFF and the
D-00202 transmission admission algorithm switch is turned off,
8 transmission admission control is not performed for
emergency calls.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)

CellRac AcReser MOD LBFD-0 Admissi Meaning: Indicates the UE numbers reserved for UEs
Thd vedUser CELLR 02023 / on initiating emergency calls and high-priority UEs. If
Number ACTHD TDLBF Control this parameter is set to 0, no UE number is reserved
LST D-00202 for UEs initiating emergency calls and high-priority
CELLR 3 UEs. A non-zero value of this parameter represents
ACTHD the maximum UE number reserved for UEs initiating
emergency calls and high-priority UEs.
GUI Value Range: 0~30
Unit: None
Actual Value Range: 0~30
Default Value: 0

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 37


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 8 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

Emc CnOper LST LOFD-0 RAN Meaning: Indicates the id of the operator.
atorId EMC 01036 / Sharing GUI Value Range: 0~5
MOD TDLOF with
D-00103 Commo Unit: None
EMC
6 n Actual Value Range: 0~5
LOFD-0 Carrier Default Value: None
01037 / RAN
TDLOF Sharing
D-00103 with
7 Dedicate
d
Carrier

Emc EmcEna MOD LBFD-0 Emerge Meaning: Indicates whether to enable or disable
ble EMC 02028 / ncy Call emergency calls. It is recommended that this
LST TDLBF parameter be set to a value in accordance with the
EMC D-00202 actual emergency call capability of the operator.
8 GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 38


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 9 Counters

9 Counters

Table 9-1 Counters


Counter ID Counter Name Counter Feature ID Feature Name
Description

1526728162 L.EMC.HHO.Prep Number of intra- Multi-mode: None Emergency Call


AttOut duplex-mode GSM: None Emergency call
outgoing handover
attempts for UMTS: None
emergency calls in LTE:
a cell LBFD-002028
TDLBFD-002028

1526728163 L.EMC.HHO.Exec Number of intra- Multi-mode: None Emergency Call


AttOut duplex-mode GSM: None Emergency call
outgoing handover
executions for UMTS: None
emergency calls in LTE:
a cell LBFD-002028
TDLBFD-002028

1526728164 L.EMC.HHO.Exec Number of Multi-mode: None Emergency Call


SuccOut successful intra- GSM: None Emergency call
duplex-mode
outgoing handovers UMTS: None
for emergency calls LTE:
in a cell LBFD-002028
TDLBFD-002028

1526728167 L.EMC.E- Number of E-RAB Multi-mode: None Emergency Call


RAB.AttEst setup attempts for GSM: None Emergency call
emergency calls in
a cell UMTS: None
LTE:
LBFD-002028
TDLBFD-002028

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 39


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 9 Counters

Counter ID Counter Name Counter Feature ID Feature Name


Description

1526728168 L.EMC.E- Number of Multi-mode: None Emergency Call


RAB.SuccEst successful E-RAB GSM: None Emergency call
setups for
emergency calls in UMTS: None
a cell LTE:
LBFD-002028
TDLBFD-002028

1526728169 L.EMC.E- Number of normal Multi-mode: None Emergency Call


RAB.NormRel.Ho E-RAB releases due GSM: None Emergency call
Out to outgoing
handovers for UMTS: None
emergency calls in LTE:
a cell LBFD-002028
TDLBFD-002028

1526728170 L.EMC.E- Number of Multi-mode: None Emergency Call


RAB.AbnormRel.H abnormal E-RAB GSM: None Emergency call
oOut releases due to
outgoing handovers UMTS: None
for emergency calls LTE:
in a cell LBFD-002028
TDLBFD-002028

1526728171 L.EMC.E- Number of Multi-mode: None Emergency Call


RAB.Abnormrel abnormal E-RAB GSM: None Emergency call
releases for
emergency calls in UMTS: None
a cell LTE:
LBFD-002028
TDLBFD-002028

1526728172 L.EMC.E- Number of normal Multi-mode: None Emergency Call


RAB.NormRel E-RAB releases for GSM: None Emergency call
emergency calls in
a cell UMTS: None
LTE:
LBFD-002028
TDLBFD-002028

1526728217 L.RRC.ConnReq.At Number of RRC Multi-mode: None RRC Connection


t.Emc connection setup GSM: None Management
attempts with a RRC Connection
cause value of UMTS: None
Management
emergency LTE:
LBFD-002007 Dynamic DRX
TDLBFD-002007
LOFD-00110501

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 40


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 9 Counters

Counter ID Counter Name Counter Feature ID Feature Name


Description

1526728222 L.RRC.ConnReq.S Number of RRC Multi-mode: None RRC Connection


ucc.Emc Connection Setup GSM: None Management
Complete messages RRC Connection
with a cause value UMTS: None
Management
of emergency LTE:
received from UEs LBFD-002007
in a cell TDLBFD-002007

1526728707 L.CSFB.PrepAtt.E Number of CSFB Multi-mode: None CS Fallback to


mergency indicators received GSM: None UTRAN
by the eNodeB for CS Fallback to
emergency calls UMTS: None
UTRAN
LTE:
CS Fallback to
LOFD-001033
GERAN
TDLOFD-001033 CS Fallback to
LOFD-001034 GERAN
TDLOFD-001034 CS Fallback to
CDMA2000 1xRTT
LOFD-001035
CS Fallback to
TDLOFD-001035 CDMA2000 1xRTT

1526728708 L.CSFB.PrepSucc. Number of Multi-mode: None CS Fallback to


Emergency responses sent from GSM: None UTRAN
the eNodeB for CS Fallback to
CSFB triggered for UMTS: None
UTRAN
emergency calls LTE:
CS Fallback to
LOFD-001033
GERAN
TDLOFD-001033 CS Fallback to
LOFD-001034 GERAN
TDLOFD-001034 CS Fallback to
CDMA2000 1xRTT
LOFD-001035
CS Fallback to
TDLOFD-001035 CDMA2000 1xRTT

1526728709 L.CSFB.E2W.Emer Number of Multi-mode: None CS Fallback to


gency procedures for GSM: None UTRAN
CSFB to WCDMA CS Fallback to
network triggered UMTS: None
UTRAN
for emergency calls LTE:
LOFD-001033
TDLOFD-001033

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 41


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 9 Counters

Counter ID Counter Name Counter Feature ID Feature Name


Description

1526728710 L.CSFB.E2G.Emer Number of Multi-mode: None CS Fallback to


gency procedures for GSM: None GERAN
CSFB to GERAN CS Fallback to
triggered for UMTS: None
GERAN
emergency calls LTE:
LOFD-001034 Ultra-Flash CSFB
to GERAN
TDLOFD-001034
Ultra-Flash CSFB
LOFD-081283 to GERAN
TDLOFD-081203

1526729599 L.EMC.HHO.InterF Number of inter- Multi-mode: None Emergency Call


ddTdd.PrepAttOut duplex-mode GSM: None Emergency call
outgoing handover
attempts for UMTS: None
emergency calls in LTE:
a cell LBFD-002028
TDLBFD-002028

1526729600 L.EMC.HHO.InterF Number of inter- Multi-mode: None Emergency Call


ddTdd.ExecAttOut duplex-mode GSM: None Emergency call
outgoing handover
executions for UMTS: None
emergency calls in LTE:
a cell LBFD-002028
TDLBFD-002028

1526729601 L.EMC.HHO.InterF Number of Multi-mode: None Emergency Call


ddTdd.ExecSuccOu successful inter- GSM: None Emergency call
t duplex-mode
outgoing handovers UMTS: None
for emergency calls LTE:
in a cell LBFD-002028
TDLBFD-002028

1526730100 L.Traffic.Privilege. Average number of Multi-mode: None Admission Control


User.avg privileged UEs in a GSM: None Admission Control
cell
UMTS: None Emergency Call
LTE: Emergency call
LBFD-002023
TDLBFD-002023
LBFD-002028
TDLBFD-002028

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 42


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 9 Counters

Counter ID Counter Name Counter Feature ID Feature Name


Description

1526730101 L.Traffic.Privilege. Maximum number Multi-mode: None Admission Control


User.max of privileged UEs in GSM: None Admission Control
a cell
UMTS: None Emergency Call
LTE: Emergency call
LBFD-002023
TDLBFD-002023
LBFD-002028
TDLBFD-002028

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 43


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 10 Glossary

10 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 44


Copyright Huawei Technologies Co., Ltd.
eRAN
Emergency Call Feature Parameter Description 11 Reference Documents

11 Reference Documents

1. 3GPP TS 36.331, "Radio Resource Control (RRC); Protocol specification"


2. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access"
3. 3GPP TS 24.008, "Mobile radio interface Layer 3 specification; Core network protocols;
Stage 3"
4. 3GPP TS 36.413, "Evolved Universal Terrestrial Radio Access Network (E-UTRAN);
S1 Application Protocol (S1AP)"
5. 3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System (EPS);
Stage 2"
6. 3GPP TS 23.237, "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2"
7. 3GPP TS 23.271, "Functional stage 2 description of Location Services (LCS)"
8. CS Fallback Feature Parameter Description
9. Admission and Congestion Control Feature Parameter Description
10. Transport Resource Management Feature Parameter Description
11. LTE-CDMA2000 CS Service Interworking Feature Parameter Description

Issue 01 (2016-03-07) Huawei Proprietary and Confidential 45


Copyright Huawei Technologies Co., Ltd.