ELTE2.3 Broadband Access Solution Feature Description

eLTE2.
3
Broadband Access Solution
Feature Description
Issue 02
Date 2014-05-28
HUAWEI TECHNOLOGIES CO., LTD.

eLTE2.3
Broadband Access Solution Feature Description Change History
Copyright © Huawei Technologies Co., Ltd. 2014. 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
eLTE2.3
Broadband Access Solution Feature Description Change History
Change History
Issue Date Author Description

Draft 2014-02-14 Shen Minjun (employee This issue is a draft.
A ID: 00119604)
V0.2 2014-05-28 Sun Xun(employee ID: Add VRF.
00269690)
eLTE2.3
Broadband Access Solution Feature Description Contents
Contents
1 Common Features ......................................................................................................................... 1

1.1 LTE Wireless Broadband Communication .................................................................................................................... 1
1.1.1 SBFD-001003 LTE TDD Mode ................................................................................................................................. 1
1.1.2 SBFD-001004 Scalable Bandwidths (TDD Mode).................................................................................................... 2
1.1.3 SBFD-001005 Uplink-Downlink Configuration Types 1 and 2 ................................................................................ 2
1.1.4 SBFD-001006 UL/DL QPSK, UL/DL 16QAM, and DL 64QAM............................................................................. 3
1.1.5 SBFD-001007 AMC .................................................................................................................................................. 4
1.1.6 SBFD-001008 DL Asynchronous HARQ .................................................................................................................. 5
1.1.7 SBFD-001009 Uplink Synchronous HARQ .............................................................................................................. 6
1.1.8 SBFD-001010 Cell combination................................................................................................................................ 7
1.2 Industry Spectrum Flexibility ....................................................................................................................................... 9
1.2.1 SBFD-002001 Frequency Band Customization ......................................................................................................... 9
1.3 Light-Weighted Industry Solutions ............................................................................................................................. 10
1.3.1 SBFD-003001 Single-Subrack Enterprise EPC ....................................................................................................... 10
1.3.2 SBFD-003002 Network Management Using a PC Server ....................................................................................... 12
1.3.3 SBFD-003003 Small EPC ....................................................................................................................................... 14
1.3.4 SBFD-003004 Unified Network Management (eSight) .......................................................................................... 15
1.3.5 SBFD-003005 Diversification terminals ................................................................................................................. 17
1.4 Trunking Voice ............................................................................................................................................................ 19
1.4.1 SBFD-004001 Group Calls ...................................................................................................................................... 19
1.4.2 SBFD-004002 Broadcast Calls ................................................................................................................................ 21
1.4.3 SBFD-004003 Single Calls ...................................................................................................................................... 22
1.4.4 SBFD-004004 Common Calls ................................................................................................................................. 23
1.4.5 SBFD-004005 Interworking with TETRA............................................................................................................... 23
1.4.6 SBFD-004006 Interworking with PSTN, PLMM, and PABX ................................................................................. 24
1.4.7 SBFD-004007 CDR Generation .............................................................................................................................. 24
1.4.8 SBFD-004008 Signaling Tracing ............................................................................................................................. 25
1.5 Trunking Dispatch ...................................................................................................................................................... 26
1.5.1 SBFD-005001 Break-in Service .............................................................................................................................. 26
1.5.2 SBFD-005002 Forced Release Service .................................................................................................................... 27
1.5.3 SBFD-005003 Call Forwarding ............................................................................................................................... 27
1.5.4 SBFD-005004 Call Divert ....................................................................................................................................... 28
eLTE2.3
1.5.5 SBFD-005005 Floor Preemption in a Group Call.................................................................................................... 28

1.5.6 SBFD-005006 Priority-based Call Preemption ........................................................................................................ 29
1.5.7 SBFD-005007 Recording ........................................................................................................................................ 30
1.5.8 SBFD-005008 Subscriber Management .................................................................................................................. 30
1.5.9 SBFD-005009 Group Management ......................................................................................................................... 31
1.6 Video Surveillance ...................................................................................................................................................... 32
1.6.1 SBFD-006001 Uplink-Downlink Configuration Type 0 .......................................................................................... 32
1.6.2 SBFD-006003 Multiple Carriers.............................................................................................................................. 33
1.6.3 SBFD-006004 UL 2x4 MU-MIMO ......................................................................................................................... 33
1.7 Reliability ................................................................................................................................................................... 35
1.7.1 SBFD-007001 eCNS Redundancy ........................................................................................................................... 35
1.7.2 SBFD-007002 1+1 Backup of eCNS Boards ........................................................................................................... 36
1.7.3 SBFD-007003 1+1 Backup of the eNodeB Main Control Board ............................................................................ 37
1.7.4 SBFD-007004 Baseband Board Backup (CPRI Backup) ........................................................................................ 37
1.8 QoS Management ....................................................................................................................................................... 38
1.8.1 SBFD-008001 Basic QoS Management .................................................................................................................. 38
1.9 Maintainability of Network Equipment ...................................................................................................................... 40
1.1.1 SBFD-009001 Fault Management of NEs ............................................................................................................... 41
1.9.2 SBFD-009002 Performance Management ............................................................................................................... 42
1.9.3 SBFD-009003 Configuration Management ............................................................................................................. 43
1.10 Terminal Management .............................................................................................................................................. 43
1.10.1 SBFD-010001 Remote CPE Upgrade .................................................................................................................... 43
1.10.2 SBFD-010002 Remote CPE Configuration ........................................................................................................... 44
1.10.3 SBFD-010003 Querying CPE Status ..................................................................................................................... 45
1.10.4 SBFD-010004 Monitoring CPE Performance ....................................................................................................... 45
1.10.5 SBFD-010005 Automatic CPE Deployment (PNP) ............................................................................................... 46
1.10.6 SBFD-010006 CPE Fault Management ................................................................................................................. 46
1.10.7 SBFD-010007 Remote CPE Maintenance ............................................................................................................. 47
1.11 Transmission Networking ......................................................................................................................................... 48
1.11.1 SBFD-011001 Star Topology ................................................................................................................................. 48
1.11.2 SBFD-011002 Chain Topology .............................................................................................................................. 49
1.11.3 SBFD-011003 Tree Topology ................................................................................................................................ 49
1.12 Broadband Data Service ........................................................................................................................................... 50
1.12.1 SBFD-012001 VLAN ............................................................................................................................................ 50
1.12.2 SBFD-012002 OSPFv2.......................................................................................................................................... 52
1.12.3 SBFD-012003 VRF ............................................................................................................................................... 53
1.12.4 SBFD-012004 Local Routing ................................................................................................................................ 54
1.12.5 SBFD-012005 SGi Interface Packet Redirection ................................................................................................... 55
1.12.6 SBFD-012006 Routing Behind MS ....................................................................................................................... 57
1.12.7 SBFD-012007 DHCP relay.................................................................................................................................... 59
1.13 Service Management................................................................................................................................................. 61
1.13.1 SBFD-013001 Offline Charging ............................................................................................................................ 61
eLTE2.3
1.13.2 SBFD-014001 Core Network Interoperability ....................................................................................................... 63
2 Features Applicable to Specific Industries ............................................................................ 66

2.1 Railway Communications ........................................................................................................................................... 66
2.1.1 SOFD-010001 Common Calls ................................................................................................................................. 66
2.1.2 SOFD-010002 Function Number Addressing .......................................................................................................... 66
2.1.3 SOFD-010003 Location-based Addressing ............................................................................................................. 67
2.1.4 SOFD-010004 Access Matrix .................................................................................................................................. 68
2.1.5 SOFD-010005 Railway Group Calls ....................................................................................................................... 68
2.1.6 SOFD-010006 Railway Broadcast Calls.................................................................................................................. 69
2.1.7 SOFD-010007 Late Entry ........................................................................................................................................ 70
2.1.8 SOFD-010008 Railway Emergency Calls ............................................................................................................... 70
2.1.9 SOFD-010009 Priority-based Call Preemption ....................................................................................................... 71
2.1.10 SOFD-010010 Supplementary Services for Common Calls .................................................................................. 72
2.1.11 SOFD-010011 Inter-Network Connections ............................................................................................................ 73
2.1.12 SOFD-010012 CDR Generation ............................................................................................................................ 73
2.1.13 SOFD-010013 SIP DPT Operator .......................................................................................................................... 75
2.1.14 SOFD-010014 Call Recording ............................................................................................................................... 76
2.1.15 SOFD-010015 Call Signaling Tracing ................................................................................................................... 76
2.1.16 SOFD-010016 Dual Network with Load-sharing .................................................................................................. 77
2.2 wISP Communications................................................................................................................................................ 78
2.2.1 SOFD-010019 Home Broadband Data Services ...................................................................................................... 78
2.2.2 SOFD-010020 Home VoIP Services ........................................................................................................................ 78
2.2.3 SOFD-010021 CPE-level Max-Rate Control .......................................................................................................... 79
2.3 Features of Radio Enhancement ................................................................................................................................. 80
2.3.1 SOFD-001001 Extended Cell Access Radius (TDD) .............................................................................................. 80
2.3.2 SOFD-001002 DL 2x2 MIMO (4-Antenna TDD) ................................................................................................... 82
2.3.3 SOFD-001003 UL 4-Antenna Receive Diversity (TDD)......................................................................................... 83
eLTE2.3
Broadband Access Solution Feature Description 1 Common Features
1 Common Features
1.1 LTE Wireless Broadband Communication

The eLTE solution inherits advanced wireless technologies from Long Term Evolution (LTE)
and meets the requirements for broadband communication. This section describes important
radio access features and functions of LTE. For details about E-UTRAN NodeB (eNodeB)
features related to eLTE2.1, see the feature list and feature description of the corresponding
eRAN version.
1.1.1 SBFD-001003 LTE TDD Mode

Availability
This feature was introduced in eLTE2.0.
Summary
Huawei eLTE supports the LTE time division duplex (TDD) mode.
Benefits
The LTE TDD mode allows for flexible ratios of uplink throughput to downlink throughput
by using the same uplink and downlink frequency band but different uplink-downlink
configurations.
Description
The LTE TDD mode is stipulated in 3GPP protocols. In the LTE TDD mode, the uplink and
downlink for a UE use the same frequency band for data transmission.
Dependencies
To receive services from a TDD eNodeB, the UE must support the LTE TDD mode.
Issue 01 (2014-02-14) Huawei Proprietary and Confidential 1

Copyright © Huawei Technologies Co., Ltd.
eLTE2.3
1.1.2 SBFD-001004 Scalable Bandwidths (TDD Mode)

Availability
Summary
Huawei eLTE supports scalable channel bandwidths of 5 MHz, 10 MHz, and 20 MHz in the
LTE TDD mode.
Benefits
This feature provides the following benefits:
 Enterprise customers can use different channel bandwidths for networking.
 Higher bandwidths allow for higher throughput and better user experience.
Description
Huawei eLTE supports scalable channel bandwidths of 5 MHz, 10 MHz, and 20 MHz in the
LTE TDD mode.
Enhancement
None
Dependencies
UEs must support the eNodeB-supported bandwidths.
1.1.3 SBFD-001005 Uplink-Downlink Configuration Types 1 and 2

Availability
Summary
eNodeBs support uplink-downlink configuration types 1 and 2.
Benefits
This feature allows operators to flexibly configure uplink-downlink configurations based on
specific service requirements.
Description
eNodeBs support the following uplink-downlink configurations defined in 3GPP TS 36.211:

eLTE2.3
 Type 1: The ratio of the number of uplink subframes to the number of downlink
subframes is 2:2. If this uplink-downlink configuration is used, resources are evenly
allocated to the uplink and downlink.
 Type 2: The ratio of the number of uplink subframes to the number of downlink
subframes is 1:3. If this uplink-downlink configuration is used, the downlink throughput
is greater than the uplink throughput.
Table 1-1 Subframe configurations for uplink-downlink configuration types 1 and 2.
Uplink-Downli Downlink-to- Subframe No.

nk Uplink
Configuration Switching 0 1 2 3 4 5 6 7 8 9
Period
1 5 ms D S U U D D S U U D
2 5 ms D S U D D D S U D D
In this table, D indicates subframes reserved for downlink transmission, U indicates

subframes reserved for uplink transmission, and S indicates special subframes. A special
subframe consists of three fields: DwPTS, GP, and UpPTS.
Dependencies
Huawei iManager M2000 and local maintenance terminal (LMT) must support man-machine
language (MML) commands for uplink-downlink configurations.
1.1.4 SBFD-001006 UL/DL QPSK, UL/DL 16QAM, and DL 64QAM

Availability
Summary
This feature provides various modulation mechanisms that are applicable to the
uplink/downlink.
Benefits
This feature allows the eNodeB and UE to select modulation mechanisms that suit uplink and
downlink radio channel qualities. For example, if the quality for downlink radio channel is
favorable, 64QAM can be used in the downlink to achieve higher data rates, higher
throughput, and higher spectral efficiency. QAM is short for quadrature amplitude
modulation.
Description
This feature provides the following modulation mechanisms:
 Quadrature phase shift keying (QPSK): applicable to the uplink and downlink.
 16QAM: applicable to the uplink and downlink.

eLTE2.3
 64QAM: applicable only to the downlink.

The characteristics of the preceding three modulation mechanisms are described as
follows:
 For QPSK, each symbol has 4 different constellation mappings and represents 2 bits.
 For 16QAM, each symbol has 16 different constellation mappings and represents 4 bits.
 For 64QAM, each symbol has 64 different constellation mappings and represents 6 bits.
This feature allows the eNodeB and UE to select the optimal modulation mechanisms based
on current radio channel qualities, helping achieve optimal tradeoff between user data rates
and frame error rates (FERs).
High-order modulation mechanisms require good-quality radio channels. For example, if the
UE is experiencing poor-quality radio channels, it may use a low-order modulation
mechanism (for example, QPSK) for uplink transmission to meet basic service requirements.
If the UE is experiencing good-quality radio channels, it may use a high-order modulation
mechanism (for example, 16QAM) for uplink transmission to achieve higher data rates.
Enhancement
None
Dependencies
Both the eNodeB and the UE must support this feature. For example, if the eNodeB supports
64QAM in the uplink but the UE does not, the eNodeB cannot apply 64QAM for uplink
transmission. In this case, the eNodeB can only apply the highest-order modulation
mechanism (such as 16QAM) that the UE supports for uplink transmission.
1.1.5 SBFD-001007 AMC

Availability
Summary
Adaptive modulation and coding (AMC) allows the eNodeB to adaptively select the optimal
modulation and coding scheme (MCS) based on radio channel qualities. Under fixed system
resources and transmit power, AMC increases spectral efficiency and satisfies quality of
service (QoS) requirements while maximizing throughput.
Benefits
AMC provides the following benefits:
 System throughput is maximized.
 QoS requirements (such as for packet loss rates) are satisfied, and the optimal tradeoff
between data rates and block error rates (BLERs) is achieved.

eLTE2.3
Description
AMC allows the eNodeB to adaptively select the optimal MCS based on radio channel
qualities. Under fixed system resources and transmit power, AMC increases spectral
efficiency and satisfies QoS requirements while maximizing throughput.
For the uplink, the eNodeB selects the initial MCS based on the signal to interference plus
noise ratio (SINR) measurements of the uplink reference signals (RSs). Then, the eNodeB
adjusts the MCS based on the received sounding reference signals (SRSs), demodulation
reference signals (DMRSs), or whether control signals have been transmitted in the uplink. It
is worth noting that control signals may require MCSs with low MCS indexes for reliable
transmission.
For the downlink, the eNodeB first selects the MCS for a UE based on the UE-reported
channel quality indicators (CQIs) and power designated to the UE. Then, the eNodeB adjusts
the CQIs based on the BLERs to influence the selection of the MCS to use to maximize radio
resource usage.
Dependencies
None
1.1.6 SBFD-001008 DL Asynchronous HARQ

Availability
Summary
Hybrid automatic repeat request (HARQ) provides robustness against transmission errors and
enhances capacity. HARQ retransmissions are fast, and multiple services allow for one or
multiple HARQ retransmissions. As a result, HARQ can be considered as an implicit
closed-loop rate control mechanism. Downlink HARQ is based on the asynchronous protocol.
Therefore, downlink HARQ retransmissions may occur anytime after the initial transmission
starts. Each HARQ process is identified by an explicit HARQ process number.
Benefits
This feature helps increase user throughput and reduce downlink transmission delays.
Description
Downlink HARQ is a fast retransmission protocol that ensures successful downlink
transmission at the physical and Media Access Control (MAC) layers. After detecting
incorrectly decoded data, the UE sends a negative acknowledgment (NACK) message to
request a retransmission. After receiving the retransmitted data, the UE applies soft combining
to the retransmitted data and previously received data to increase decoding performance.
HARQ is a link enhancement technology, which combines the forwarding error correction
(FEC) and automatic repeat request (ARQ) functions. Compared with ARQ, HARQ provides
faster and more efficient retransmissions with lower transmission delays. The UE sends an
acknowledgment (ACK) message to the eNodeB if the received downlink data is correctly
decoded by FEC and passes the cyclic redundancy check (CRC). Otherwise, the UE sends an
NACK message to the eNodeB to request a retransmission.

eLTE2.3
Downlink HARQ is an asynchronous adaptive transmission process, which means the UE is

not preallocated any HARQ transmission schedulers. In addition, the positions of resource
blocks (RBs) and the modulation and coding scheme (MCS) allocated to the UE in a
retransmission may be different from those in previous transmissions.
According to LTE specifications, downlink HARQ is based on the incremental redundancy
(IR) algorithm. In a message, downlink HARQ specifies retransmitted data and the
redundancy version (RV) of the retransmission. After receiving retransmitted data and
obtaining its RV, the UE's HARQ process applies soft combining to the retransmission data
and previously received data and then forwards the combined data to FEC for decoding. Soft
combining helps increase FEC-based decoding success rates and therefore increases data
reception success rates.
To fully utilize system resources, LTE specifications require the use of multiple downlink
HARQ processes, which significantly increases system throughput and reduces delays but
requires more buffer space and signaling overhead.
Dependencies
None
1.1.7 SBFD-001009 Uplink Synchronous HARQ

Availability
Summary
Uplink HARQ is based on the synchronous protocol, which is different from downlink HARQ.
Uplink HARQ retransmissions occur at a predefined time after the initial transmission.
Therefore, the number of retransmissions can be implicitly obtained.
Benefits
This feature helps increase user throughput and reduce uplink transmission delays.
Description
Uplink HARQ is a fast retransmission protocol that ensures successful uplink transmission at
the physical and Media Access Control (MAC) layers. After detecting incorrectly decoded
data, the eNodeB sends a negative acknowledgment (NACK) message in response to the data
and requests a retransmission. Then, the eNodeB applies soft combining to the retransmitted
data and previously received data to increase decoding performance.
As a link enhancement technology, HARQ is a combination of the forwarding error correction
(FEC) and automatic repeat request (ARQ) functions. Compared with ARQ, HARQ provides
faster and more efficient retransmissions with lower transmission delays. The eNodeB sends
an acknowledgment (ACK) message to the UE through the physical HARQ indicator channel
(PHICH) if the received uplink data is correctly decoded by FEC and passes the cyclic
redundancy check (CRC). Otherwise, the eNodeB sends an NACK message to the UE,
requesting a retransmission.
Huawei supports uplink adaptive synchronous HARQ. The positions of resource blocks (RBs)
and modulation and coding scheme (MCS) allocated in a retransmission vary by the channel

eLTE2.3
quality. However, the transport block size for any retransmission is the same as that for the
initial transmission.
In Long Term Evolution (LTE) specifications, uplink HARQ is based on the incremental
redundancy (IR) algorithm. In a message, uplink HARQ specifies whether the data is a
retransmission; if so, uplink HARQ also specifies the redundancy version (RV) of the
retransmission. After receiving a retransmission and obtaining its RV, the eNodeB's HARQ
process applies soft combining to the retransmitted data and previously received data and then
forwards the combined data to FEC for decoding. Soft combining helps increase FEC-based
decoding success rates and therefore increases data reception success rates.
To fully utilize system resources, LTE specifications require the use of multiple uplink HARQ
processes, which significantly increases system throughput and reduces delays but requires
more buffer space and signaling overhead.
Dependencies
None
1.1.8 SBFD-001010 Cell combination

Availability
Summary
This feature allows multiple independent cells to form a single logical cell, which is served by
several RRUs that belonged to cells with the same physical cell ID (PCI). This is known as
cell combination.
Benefits
This feature has the following benefits:
 Reduced inter-cell intra-frequency interference and improved satisfaction of cell edge
users (CEUs)
 Increased downlink rate
 Reduced number of neighboring cells and handovers
This feature typically applies to areas along railways and highways, as well as areas with
coverage holes, hotspots, and indoor coverage.
Description
This feature reduces the number of neighboring cells and subsequently the number of
handovers. In the uplink, complete reception and selective reception modes are used.
Therefore, uplink interference that exists between the otherwise independent cells is reduced.
In the downlink, signals from the multiple RRUs adopt joint transmission so that the signals
can be strengthened through signaling adding on multiple paths. This increases the signal to
interference plus noise ratio (SINR) and downlink rate at cell edges. Cell combination is
recommended for broadband application scenarios where downlink services account for the
majority of all services. Figure 1-1 shows cell combination.

eLTE2.3
Figure 1-1 Cell combination
Figure 1-2 shows the comparison between railway/highway coverage scenarios with and
without cell combination. When this feature is applied, adjacent RRUs are combined to serve
a single cell.
Figure 1-2 Comparison between railway/highway coverage scenarios with and without cell
combination
Figure 1-3 shows the feature application to areas with coverage holes, hotspots, and indoor
coverage. Multiple RRUs are deployed to fill in the coverage holes or hotspots within the
coverage of the primary RRU. All RRUs belong to one cell.

eLTE2.3
Figure 1-3 Application of cell combination for areas with coverage holes and hotspots
This feature applies to LTE TDD 5 MHz (with a configuration ratio of 0/1) and 20 MHz (with
a configuration ratio of 1/2) bandwidths. A cell can contain a maximum of six 2T2R RRUs or
three 4T4R RRUs.
Dependencies
The eNodeB must be configured with the LBBPd4 board.
This feature cannot be used together with the following features:
 SEFD-033100 Adaptive Inter-Cell Interference Coordination
 TDLOFD-001031 Extended CP
 TDLOFD-001039 RF Channel Intelligent Shutdown
 TDLOFD-001077 Multi-User Beamforming (when the eNodeB is configured with the
LBBPc board)
 TDLOFD-001058 UL 2x4 MU-MIMO (when the eNodeB is configured with the LBBPc
board)
 TDLAOFD-001001 Carrier Aggregation Introduction Package (Two Component
Carriers)
1.2 Industry Spectrum Flexibility

Industry spectrums are characterized by uncertain frequencies, non-standard bandwidths, and
discontinuous spectrums. In light of these characteristics, eLTE2.1 provides pertinent and
flexible spectrum solutions.
1.2.1 SBFD-002001 Frequency Band Customization

Availability
Summary
Huawei eLTE supports multiple LTE time division duplex (TDD) frequency bands.

eLTE2.3
Benefits
Industry frequency bands are not unified. Frequency bands used by different industries and
regions vary, and large spectrum chunks are difficult to obtain. To deal with this situation, this
feature offers customers more flexible spectrum choices.
Description
The following table lists the LTE TDD frequency bands supported by the eLTE.
Table 1-2 eLTE-supported LTE TDD frequency bands
Frequency Band Frequency Range
1.8 GHz 1785 MHz to 1805 MHz

2.6 GHz (band 38) 2570 MHz to 2620 MHz

Dependencies
RRUs and UEs must support the preceding frequency bands. eLTE2.1 can provide other
customized frequency bands by using the corresponding RRU.
1.3 Light-Weighted Industry Solutions

Enterprise projects are generally small in network scales and limited in investments. To adapt
to characteristics of industry applications, eLTE2.1 simplifies the system so that the whole
system becomes more compact and more tailored to industry applications.
1.3.1 SBFD-003001 Single-Subrack Enterprise EPC

Availability
Summary
A 14U single-subrack device is provided as the evolved packet core (EPC) for enterprise
applications. It integrates the functions of the home subscriber server (HSS), mobility
management entity (MME), PDN gateway (P-GW), and serving gateway (S-GW) into a
single 14U device.

eLTE2.3
This feature applies to enterprise networks with a large or medium scale, comprehensive
O&M, and high reliability, such as networks for governments, high-speed railways, and urban
rail transportation.
Benefits
By integrating multiple network elements (NEs) in the EPC into one device, this feature
reduces the required hardware footprint, power requirements, maintenance costs, and network
delays.
Description
Compared with telecommunications wireless networks, enterprise wireless networks have
much smaller network coverage, much fewer subscribers, and much lower throughput.
Enterprise wireless devices are required to:
 Be smaller, lighter, and more energy-efficient. To meet this requirement, enterprise
wireless devices must be compact.
 Be few in number, low in cost, and easily managed.
Based on the preceding requirements, it is unnecessary to keep multiple NEs in the EPC
separate in enterprise applications.
This feature integrates multiple closely related NEs in the EPC into one device, which takes
the form of one major NE and incorporates the functions of other NEs.
The single-subrack device serving as the EPC takes the form of an MME and incorporates the
functions of the S-GW, P-GW, and policy and charging rules function (PCRF).
Figure 1-4 shows the integration policy for enterprise EPCs.

eLTE2.3
Figure 1-4 Integration policy for enterprise EPCs
Operator-specific EPC
MME HSS
S6a
eNodeB
S1-MME
UE
S11
S-GW P-GW
S1-U
SGi Internet/
S5 Intranet
Enterprise EPC
eNodeB
MME/HSS/S-GW/P-GW
UE
S1 SGi Internet/
Intranet
The number of NEs in the EPC continues to decrease along with the NE integration process,
leading to most external interfaces and unnecessary functions being removed. This
significantly reduces the investment and maintenance costs on the EPC.
Dependencies
The single-subrack device serving as the EPC can only be managed by a network
management element (NME) at the PC server level.
1.3.2 SBFD-003002 Network Management Using a PC Server

Availability
Summary
Network management software is installed on a common personal computer (PC) server.
Benefits
A lightweight network management system can be provided for enterprise customers. The
system features low cost and easy maintenance.

eLTE2.3
Description
To meet enterprise customer requirements, Huawei provides a low-cost M2000 solution. This
solution uses an IBM PC server running the network management software to manage
equipment on the enterprise wireless network.
The following table lists the general specifications for the network management server used in
eLTE2.1.
Item Specification
Dimensions 85.4 mm x 443.6 mm x 705 mm (H x W x D)
Adaptive voltage –48 V DC to –60 V DC
Weight 1. 22 kg to 29.3 kg (varying with the number of disks)
The following table lists the software and hardware specifications for the network
management server used in eLTE2.1.
Item Specification
CPU Intel Xeon 2*E5640 4-Core 2.66 GHz
Memory capacity 2. 4 x 8 GB
Hard disk capacity 3. 8 x 300 GB
Operating system Linux SUSE10 SP4
Database Oracle 11.1.0.7.3
The PC server–based network management system for the enterprise wireless network is
developed based on M2000 V200R012C01 developed for operator wireless networks. The
network management system for the enterprise wireless network supports the following
features:
 Management of eCNS600
The eCNS600 is a single-subrack core network equipment for the enterprise wireless network.
For detailed descriptions of the single-subrack core network equipment, see section 1.3.1
"SBFD-003001 Single-Subrack Enterprise EPC."
Based on the features provided by eCNS600, the network management system for the
enterprise wireless network manages eCNS600 in terms of common operation and
management (OM) functions such as topology management, alarm management, and
configuration management. For details about the OM functions for eCNS600, see the function
and feature list issued for network management system of eLTE2.1.
 Co-Cabinet Deployment of the Network Management System and Core Network
Equipment
The network management equipment and single-subrack core network equipment for the
enterprise wireless network can be deployed in one cabinet and can share their power supply
and switch equipment. This deployment method requires smaller space and reduces hardware
costs.

eLTE2.3
For details about features of the PC server–based network management system, see the related
feature list and feature description.
Dependencies
The versions of the NEs managed by the network management system for the enterprise
wireless network must comply with the eLTE2.1 version requirements.
1.3.3 SBFD-003003 Small EPC

Availability
This feature is introduced in eLTE2.3.
Summary
This feature allows enterprise wireless networks to use a 2U LTE PS core device (known as
eCNS610). The eCNS610 integrates functions of the system architecture evolution home
subscriber server (SAE-HSS), mobility management entity (MME), serving gateway
(S-GW)/PDN gateway (P-GW), and RCRF (except for charging). RCRF stands for policy and
charging rules function.
The eCNS610 is suitable for enterprise customers with a medium- or small-scale network
with easy O&M requirements, such as networks for the WISP, airports, rural areas, hi-tech
parks, hospitals, business organizations, and SOHO workers.
Benefits
Compared with the eCNS600, the eCNS610 is more compact with a height of only 2U. The
supported network scale has been expanded, and O&M of the eCNS610 have been improved.
The eCNS610 supports O&M of a single NE and allows access to the eSight-eWL.
Description
The eCNS610 adopts Huawei Tecal RH2288 V2-8S server and functions of the SAE-HSS,
MME, S-GWP-GW, and PCRF (except for charging), as shown in Figure 1-5.
Figure 1-5 Network position of the eCNS
SGW PGW PCRF

Gx SGi
S5
eNodeB S1
APP Server
S11
S1 SGi
S6a
Uu MME HSS eCNS

UE eNodeB

eLTE2.3
Dependencies
The eCNS610 supports OMS locally and eSight-eWL remotely for network management.
1.3.4 SBFD-003004 Unified Network Management (eSight)

Availability
Summary
The eSight is a unified network management tool for the eNodeB, eCNS610, and special
terminal equipment.
Enhancement
In eLTE2.2, the eSight can manage eA660/661 series of special terminal equipment.
In eLTE2.3, the eSight can manage the eNodeB, eCNS610, and eA360 terminals.
Benefits
The eSight enables users to manage end-to-end enterprise wireless network devices (including
the DBS3900 LTE, eCNS610, and special terminals) with the unified O&M GUI and
experience. The eSight provides NE configuration, performance, alarm, and other network
management capabilities.
Description
The eSight is a unified and low-cost network management solution tool (based on the PC
Server platform) that meets the enterprise customers' requirements for low-cost network
management and unified O&M.
The eSight supports two hardware specifications listed in Table 1-3. Users can choose a
specification according to the network scale.
Table 1-3 eSight hardware specifications

No. Item Specification
1 CPU 2*6Core 2.5 GHz

Memory 32G
Local storage 300G*4
2 CPU 4*8Core 2.0 GHz
Memory 64G
Local storage 300G*8
Table 1-4 lists the hardware specifications of the eSight.

eLTE2.3
Table 1-4 eSight software specifications
No. Operating System Database

1 Windows Server 2008 R2 Standard (64 MySQL 5.5
bits)
2 Novell SuSE LINUX Enterprise Oracle Database Standard Edition 11g
Server-Enterprise-11.0 SP1 R2
3 Windows Server 2008 R2 Standard (64 Microsoft SQL Server 2008
bits) R2-standard
The eSight provides the following functions:

 Security management
Security policies are applied to the eSight to implement security control. The security
policies include user management, role management (rights- and domain-specific
authorization), and login management. In addition, the eSight manages logs that record
user logins and operations and eSight running. The eSight also supports database backup.
 Log management
The eSight logs record major operations performed by users. Users can check the log list
and view detailed log information. Users can also export operation, security, and system
logs. Logs on the eSight have three severities: suggestion, minor, and major.
 Resource management
With the resource management function, users can add and manage devices and
sub-networks.
 Topology management
Topology management constructs and manages the topology of the entire network. Users
can learn the device networking and running status from the topology view in real time.
The device status is also indicated by different colors.
 Alarm management
If the network is running abnormally, alarms will be reported to inform users to take
measures to clear the alarms.
 Performance management
Performance management enables users to ensure the performance of a network that
operates at low costs and prepare for meeting the future needs for network performance.
With this function, users can plan, monitor, and measure network efficiencies, such as
connectivity rate and usage rate. Network performance may decrease due to internal or
external causes when a network is running. Performance management allows users to be
aware of the performance deterioration trend so that they can take necessary measures
before any performance issues occur. This reduces network failure risks.
The eSight also provides the following terminal management functions based on the TR069
specifications:
 Basic terminal information
Users can view the basic information about the CPEs, which can be updated and
refreshed.
 Generalized configurations for terminals

eLTE2.3
Users can change parameters by using the TR069-based generalized configuration model
tree.
 Web page redirecting
This function enables users to redirect to the web page for CPE management.
 Configuration file exporting
Users can export and download configuration files for the CPE for backup purposes.
 Configuration file loading
This function allows users to load configuration files to the CPE.
 Remote maintenance
Users can remotely reset the CPE to restore the CPE default settings. Ping tests can be
used to check the connectivity.
 Terminal PnP
Users can set the legal information list of terminals on the eSight in advance. After a
terminal is powered on and started, it can be automatically registered on the eSight.
Online version upgrade and delivery of the initial configuration file can be performed
with one click based on the configuration policies of users.
Dependencies
None
1.3.5 SBFD-003005 Diversification terminals

Availability
Summary
This feature supports a diversity of terminals so that customers can implement flexible access
and service deployment.
 TDD frequency bands of 1.8, 2.3G, 2.6G, 3.5G, 3.6G, and 3.7 GHz are supported.
 Multiple service access and deployment methods are supported, including data, voice,
and hybrid services.
Benefits
This feature allows users to use a diversity of terminals working on a number of frequency
bands. Therefore, the requirements for multiple service access and deployment methods can
be met.
Description
This feature supports terminals, including A660-118, eA660-135, eA660-160, and B2268.
This feature supports TDD frequency bands of 1.8, 2.3G, 2.6G, 3.5G, 3.6G (band 42), and 3.7
GHz.
Deployment for data, voice, and hybrid services is supported.

eLTE2.3
 Data service deployment
Figure 1-6 Data service deployment
 Voice service deployment
Figure 1-7 Voice service deployment
LTE Outdoor
Internet
Firewall
PoE
Core Network
RJ-45
RJ-11
LTE eNodeB VoIP Softswitch
WiFi 11 b/g/n
AC/DC
Adaptor
 Hybrid service deployment

eLTE2.3
Figure 1-8 Hybrid service deployment
Enhancement
None
Dependencies
Switches are required for a CPE to access multiple service terminals.
Standards
None
1.4 Trunking Voice

1.4.1 SBFD-004001 Group Calls
Availability

eLTE2.3
Summary
This feature provides voice services to a predefined group of subscribers within a mobile
network. Group members, except the DPT operator, work in half-duplex communication
mode.
Benefits
This feature provides group-oriented half-duplex voice communication services, which bring
the following benefits:
 Improves the communication efficiency within a group of subscribers when compared
with point-to-point communication services. Therefore, group calls are well tailored to
tasks that require cooperation of multiple people.
 Uses digital transmission to enhance voice quality when compared with traditional
analog communication systems.
Description
After data configurations about a group (calling restrictions, group definition, and
management over mobile group members) are complete on the trunking server, authorized
group members can initiate group calls by dialing the group call number.
After receiving the notifications of a group call, group members (including the DPT operator)
within the mobile network join in the group call. Then, any member that has joined in the
group call can initiate a push-to-talk (PTT) call by holding down the PTT key on the mobile
terminal.
During a PTT call initiated by a member (for example, subscriber A), other members in the
group can only listen to subscriber A (even if holding down the PTT key). Other members in
the group can only initiate a new PTT call after subscriber A finishes the PTT call and releases
the PTT key.
To terminate a group call, the subscriber that has initiated the group call presses the end key
on the mobile terminal. All members in the group then leave the group call.
A group generally includes a DPT operator. A DPT operator is a special subscriber defined in
the trunking server and can initiate PTT calls at anytime without floor application. In addition,
depending on the capability defined on the trunking server, a DPT operator can initiate or
terminate group calls.
A group call service involves the following functions:
1. Initiating a group call
An authorized member can initiate a group call by dialing the group call number. After a
group call is initiated, the trunking server allocates channel resources for the group call
and notifies the members within the mobile network to join in the group call. For those
members that have not joined in at the beginning of the group call (because they were
not within the mobile network or were not registered with the network), the trunking
server will notify them to join in the group call when they move back to the mobile
network or register with the network. For details, see 5 "Late entry" in the following
descriptions.
Group calls can also be initiated by authorized DPT operators.
2. Terminating a group call

eLTE2.3
The member that initiated a group call can terminate the group call. After the group call
is terminated, the trunking server releases all resources occupied by the group call and all
members that have joined in the group call return to the idle state.
Group calls can also be terminated by authorized DPT operators.
3. Applying for the floor
Any member that has joined in a group call can apply for the floor by pressing the PTT
key. If no PTT call is ongoing, the trunking server assigns the floor to the member that
presses the PTT key (the member must hold down the PTT key during the entire PTT
call). If there is an ongoing PTT call, the trunking server rejects the floor application.
4. Releasing the floor
When a PTT call is finished, the member that initiated the PTT call can release the floor
by releasing the PTT key. Other members in the group can then apply for the floor.
5. Late entry
Members that have not joined in a group call in the beginning, due to reasons such as
their mobile terminal is powered off, can receive notifications later to join in the group
call.
Dependencies
This feature depends on the group management function.
1.4.2 SBFD-004002 Broadcast Calls

Availability
Summary
This feature provides broadcast voice services to a predefined group of subscribers within a
mobile network. Group members work in simplex communication mode.
Benefits
This feature provides group-oriented simplex broadcast voice services, which meet the
requirements for dedicated dispatch communication.
Description
After group members and the broadcast call number are defined on the trunking server,
authorized group members can initiate broadcast calls by dialing the broadcast call number.
After receiving the notifications of a broadcast call, members of the group within the
broadcast area join in the broadcast call. Only the member (for example, subscriber A) that
initiated the broadcast call can speak. Subscriber A does not need to hold down the
push-to-talk (PTT) key on the mobile terminal and other members can only listen to
subscriber A. To terminate the broadcast call, subscriber A presses the end key. All members
then leave the broadcast call.
A broadcast group generally includes a DPT operator. A DPT operator is a special subscriber
defined on the trunking server. Depending on the capability defined on the trunking server, a
DPT operator can initiate or terminate broadcast calls. Note that DPT operators cannot speak
during a broadcast call initiated by another member.

eLTE2.3
A broadcast service involves the following functions:

1. Initiating a broadcast call
An authorized member can initiate a broadcast call by dialing the broadcast call number.
After a broadcast call is initiated, the trunking server allocates channel resources for the
broadcast call and notifies members within the broadcast area to join in the broadcast call.
For those members that have not joined at the beginning of the broadcast call (because
they were not within the broadcast area or were not registered with the network), the
trunking server will notify them to join in the broadcast call when they move back to the
broadcast area or register with the network. For details, see 3 "Late entry" in the
following descriptions. After initiating a broadcast call, the initiator can speak.
Broadcast calls can also be initiated by authorized DPT operators. After initiating a
broadcast call, the DPT operator can speak.
2. Terminating a broadcast call
The member that initiated a broadcast call can terminate the broadcast call. After the
broadcast call is terminated, the trunking server releases all resources occupied by the
broadcast call and all members that have joined in the broadcast call return to the idle
state.
3. Late entry
Members that have not joined in a broadcast call in the beginning, due to reasons such as
their mobile terminal is powered off, can receive notifications later to join in the
broadcast call.
Dependencies
This feature depends on the group management function.
1.4.3 SBFD-004003 Single Calls

Availability
Summary
This feature provides single calls. A single call is a half-duplex voice call between two
subscribers.
Benefits
Single calls are easy for group members to become accustomed with because single calls are a
conventional point-to-point voice communication service that usually last for a short time and
work in the same communication mode (half-duplex mode) as group calls.
Description
This feature provides single calls. A single call is a half-duplex voice call between two
subscribers. A subscriber initiates a single call to the other subscriber by dialing the other
subscriber's number and holding down the push-to-talk (PTT) key on the mobile terminal, and
terminates the single call by releasing the PTT key. During the single call, the other subscriber
cannot initiate another single call (even if holding down the PTT key).

eLTE2.3
Dependencies
Subscribers must be authorized to make single calls.
1.4.4 SBFD-004004 Common Calls

Availability
Summary
This feature provides common calls. A common call is a full-duplex point-to-point voice call
between two subscribers or between one subscriber and the DPT operator.
Benefits
Common calls are easy for subscribers to become accustomed with because common calls are
made in the same as that to make mobile calls.
Description
between two subscribers or between one subscriber and the DPT operator. A subscriber
initiates a common call by dialing the other subscriber's number and pressing the dial key.
Upon receiving the common call request, the trunking server notifies the other subscriber.
After the other subscriber picks up the call, a full-duplex connection is set up.
Dependencies
Subscribers must be authorized to make full-duplex common calls.
1.4.5 SBFD-004005 Interworking with TETRA

Availability
Summary
This feature allows eLTE subscribers and terrestrial trunking radio (TETRA) subscribers to
form a group for group call communication.
Benefits
With this feature, eLTE subscribers can form a group with TETRA subscribers for group call
communication.
Description
This feature enables the eLTE network to interwork with the TETRA network by deploying
radio gateways and TETRA vehicle-mounted stations. In this way, eLTE subscribers can form
a group with TETRA subscribers for group call communication over the radio interface.

eLTE2.3
Dependencies
None
1.4.6 SBFD-004006 Interworking with PSTN, PLMM, and PABX

Availability
Summary
This feature allows the eLTE network to interwork with the public switched telephone
network (PSTN), public land mobile network (PLMN), and private automatic branch
exchange (PABX) network.
Benefits
This feature allows eLTE subscribers to have voice communications with subscribers of other
external networks.
Description
The eLTE network, where trunk gateways (TGs) supporting the No.7, PRI, Q.SIG, or SIP2.0
protocol are deployed, can interwork with external PSTN, PLMN, and PABX networks.
Dependencies
This feature applies only to common calls.
1.4.7 SBFD-004007 CDR Generation

Availability
Summary
This feature allows the generation of call detail records (CDRs).
Benefits
With this feature, detailed information about calls made by a subscriber is recorded for future
query.
Description
CDRs about the following calls are generated:
 Common calls
A CDR is generated for a common call and includes the following fields: calling service
number, calling function number, called service number, called function number, LTE

eLTE2.3
cell ID of the calling party, LTE cell ID of the called party, start time for the common call,
stop time for the common call, and CDR type.
 Single calls
A CDR is generated for a single call and includes the following fields: calling number,
called number, cell ID of the calling party, cell ID of the called party, start time for the
single call, stop time for the single call, and CDR type.
 Group calls
− A CDR is generated for an entire group call and includes the following fields: group
call number, number of the group call initiator, cell ID of the group call initiator, start
time for the group call, stop time for the group call, and CDR type.
− A CDR is generated for a PTT call and includes the following fields: group call
number, number of the member starting the PTT call, cell ID of the member starting
the PTT call, start time for the PTT call, stop time for the PTT call, and CDR type.
− A CDR is generated for each DPT operator in a group call and includes the following
fields: group call number, number of the DPT operator, start time for the group call,
stop time for the group call, and CDR type.
 Broadcast calls
− A CDR is generated for an entire broadcast call and includes the following fields:
broadcast call number, number of the broadcast call initiator, cell ID of the broadcast
call initiator, start time for the broadcast call, stop time for the broadcast call, and
CDR type.
− A CDR is generated for each dispatcher in a broadcast call and includes the following
fields: broadcast call number, number of the dispatcher, start time for the broadcast
call, stop time for the broadcast call, and CDR type.
 Forwarded calls
A CDR is generated for a forwarded call and includes the following fields: calling
service number, number from which the call is forwarded, number to which the call is
forwarded, start time for the forwarded call, stop time for the forwarded call, and CDR
type.
 Transferred calls
A CDR is generated for a transferred call and includes the following fields: calling
service number, number from which the call is transferred, number to which the call is
transferred, start time for the transferred call, the time when the transfer occurs, stop time
for the transferred call, and CDR type.
Dependencies
None
1.4.8 SBFD-004008 Signaling Tracing

Availability
Summary
With this feature, signaling messages transmitted during calls are traced in real time, stored,
and reviewed.

eLTE2.3
Benefits
This feature traces signaling messages for all types of calls, which significantly improves the
operation and maintenance capability of the system.
Description
Signaling messages for the following calls are stored on the server for future review:
 Common calls
 Single calls
 Group calls
 Broadcast calls
Dependencies
None
1.5 Trunking Dispatch

1.5.1 SBFD-005001 Break-in Service
Availability
Summary
A high-priority subscriber can make a break-in call to a busy subscriber and the other party in
the original call is placed on hold.
Benefits
This feature enables subscribers with high priority to take precedence over normal subscribers
when making a call.
Description
It is assumed that A is having a call with B while C, who has the right to make break-in calls,
attempts to call A. If B is not enabled with the break-in service or the priority of B is lower
than that of C, the call from C to A is set up and B hears the music on hold. After the call
between C and A completes, the call between B and A resumes.
Dependencies
To use the break-in service, subscribers must subscribe to this service.

eLTE2.3
1.5.2 SBFD-005002 Forced Release Service

Availability
Summary
A high-priority subscriber can make a break-in call to a busy subscriber and the original call is
released.
Benefits
This feature enables subscribers with high priority to take precedence over normal subscribers
when making a call.
Description
It is assumed that A is having a call with B while C, who has been enabled with the forced
release service, attempts to call A. If B is not enabled with the forced release service or the
priority of B is lower than that of C, the call from C to A is set up and the call between A and
B is released.
Dependencies
To use the forced release service, subscribers must subscribe to this service.
1.5.3 SBFD-005003 Call Forwarding

Availability
Summary
This feature redirects incoming calls to another number before the call is set up.
Benefits
This feature improves the call completion rate and meets certain dispatch requirements.
Description
Call forwarding is classified into four types:
 Call forwarding - unconditional
All common incoming calls are unconditionally redirected to another specified number.
 Call forwarding - busy
A common incoming call is redirected to another specified number when the called party
is busy.

eLTE2.3
 Call forwarding - no reply

does not answer the call.
 Call forwarding - not reachable
is not reachable.
Dependencies
To use the call forwarding service, subscribers must subscribe to this service.
1.5.4 SBFD-005004 Call Divert

Availability
Summary
This feature enables a called party to divert a call to another subscriber after the call is set up.
Benefits
This feature improves communication efficiency.
Description
After answering a call, the called party can press the call transfer key, enter the number of the
third party, and then press the send key to end the original conversation and transfer the call to
the third party. The calling party then hears the alert tone "The subscriber you dialed is busy
now. Please hold on." The phone of the third party rings and the calling party hears the
ringback tone. After the third party answers the call, the calling party can talk to the third
party.
Dependencies
To use the call divert service, subscribers must subscribe to this service.
1.5.5 SBFD-005005 Floor Preemption in a Group Call

Availability
Summary
This feature allows subscribers to preempt the floor in a group call based on the priorities.

eLTE2.3
Benefits
The floor preemption in a group call provides flexible voice dispatch.
Description
With this feature, a listener can press the PTT key to apply for the floor at any time as long as
the listener has a priority higher than that of the talking party. The original talking party then
becomes a listener. Without the floor preemption feature, listeners can apply for the floor only
after the talking party releases the PTT key.
Dependencies
This feature applies only to group calls.
1.5.6 SBFD-005006 Priority-based Call Preemption

Availability
Summary
This feature forces users in a low-priority call to leave the call so that they can join in a
high-priority call.
Benefits
The called party can immediately join in a high-priority call in dispatch communication.
Description
If priority-based call preemption is not used, a called party cannot be connected to a new call
when the called party is busy. If priority-based call preemption is used, a called party can be
connected to a new call even if the called party is busy. The trunking server compares the
priorities of the ongoing call and the new call. If the new call has a higher priority than the
ongoing call, the called party will be forced to leave the ongoing call and join in the new call.
There are seven priorities that are defined on the trunking server. Each user or group has a
priority.
The priorities of various call modes are as follows:
 The priority of a common call is the same as the default priority of the calling party.
 The priority of a single call is the same as the default priority of the calling party.
 The priority of a half-duplex group call is the same as the default priority of the group.
 The priority of a simplex broadcast call is the same as the default priority of the group.
The consequence of preemption in each call mode is as follows:
 In a common call, if a party is preempted, the call will be released.
 In a single call, if a party is preempted, the call will be released.
 In a half-duplex group call, if the talking is preempted, the floor will be released.
 In a simplex broadcast call, if the talking party is preempted, the call will be released.

eLTE2.3
Dependencies
None
1.5.7 SBFD-005007 Recording

Availability
Summary
This feature allows subscribers to record and save voice calls.
Benefits
Important speeches can be recorded and reviewed.
Description
The following calls can be recorded: common, single, group, and broadcast calls.
Call recordings are saved as .wav files and can be queried by subscriber numbers or group
IDs.
Playback of call recordings is supported.
Dependencies
None
1.5.8 SBFD-005008 Subscriber Management

Availability
Summary
This feature helps manage subscribers by adding, deleting subscribers in the system, or
modifying subscriber attributes.
Benefits
Subscribers can be managed.
Description
The subscriber attributes are described as follows:
 Priority: specifies the priority of a subscriber. The priority value ranges from 0 to 4 (0
indicates the highest priority). The default value is 3.

eLTE2.3
 Single call authority: specifies the authority of a subscriber to make single calls, that is,
half-duplex calls.
 Whether to record single calls: specifies whether to enable the recording function during
single calls.
 Common call authority: specifies the authority of a subscriber to make common calls,
that is, full-duplex calls.
 Whether to record common calls: specifies whether to enable the recording function
during common calls.
Dependencies
None
1.5.9 SBFD-005009 Group Management

Availability
Summary
This feature helps manage groups in services such as group calls, broadcast calls, call pickup,
and ring group.
Benefits
Groups in services such as group calls, broadcast calls, call pickup, and ring group can be
managed.
Description
 Group management in group calls and broadcast calls: The administrator can divide
subscribers into groups by defining the group call number and specifying group members.
The administrator can also query or modify an existing group. Instructions are
transmitted to mobile terminals over the air interface.
 Ring group management: The administrator can divide subscribers into groups by
defining the group number and specifying policies (round-robin or parallel ring) and
group members. The administrator can also query or modify an existing group.
 Group management in call pickup: The administrator can divide subscribers into groups
by defining the group number and specifying group members. The administrator can also
query or modify an existing group.
Dependencies
None

eLTE2.3
1.6 Video Surveillance

In eLTE2.1 and later versions, the LTE network supports video surveillance services, which
can be used for various purposes, such as transportation, city security, and the monitoring of
unattended areas.
A video surveillance system consists of IP cameras and a management center. The LTE
network consists of the customer premises equipment (CPE), eNodeB, and eCNS. The CPE is
connected to the IP camera using 10 or 100 Mbit/s fast Ethernet (FE) ports and transmits
video surveillance services to the LTE network. The eCNS is connected to the management
center using 100 or 1000 Mbit/s gigabit Ethernet (GE) ports.
Video surveillance services require a large uplink bandwidth, which is much larger than the
required downlink bandwidth. Therefore, a single cell under the eNodeB can support a limited
number of IP cameras. One IP camera requires an uplink bandwidth of 1 or 2 Mbit/s and a
downlink bandwidth of less than 256 kbit/s.
1.6.1 SBFD-006001 Uplink-Downlink Configuration Type 0

Availability
Summary
Time division duplex (TDD) DBS3900 eNodeBs of eLTE2.1 support uplink-downlink
configuration type 0.
Benefits
Uplink-downlink configuration type can increase the uplink throughput of UEs and cells in
networks that have high uplink capacity requirements.
Description
The LTE TDD mode supports flexible uplink-downlink configurations. If uplink-downlink
configuration type 0 is used (that is, the ratio of the number of uplink subframes to the
number of downlink subframes is 3:1), the uplink cell throughput reaches the maximum
configured throughput.

eLTE2.3
Table 1-5 Uplink-downlink configuration type 0 in the LTE TDD mode
Uplink-Downlin Downlink-to-Uplin Subframe No.

k Configuration k Switching Period
0 1 2 3 4 5 6 7 8 9
0 5 ms D S U U U D S U U U
In this table, D indicates subframes reserved for downlink transmission, U indicates

subframes reserved for uplink transmission, and S indicates special subframes. A special
subframe consists of three fields: DwPTS, GP, and UpPTS.
Dependencies
UEs must support this feature.
In eLTE2.2, only the UEs working at the 1.8 GHz or 2.3 GHz band support this feature.
1.6.2 SBFD-006003 Multiple Carriers

Availability
Summary
Multiple carriers can be used in one sector.
Benefits
In contrast to a single 20 MHz carrier that cannot provide sufficient bandwidth, this feature
satisfies the bandwidth requirements in areas where a large number of IP cameras are used
and consequently the traffic of video surveillance services is heavy.
Description
One sector corresponds to one coverage area. If multiple 20 MHz carriers are used in one
sector, loads can be balanced among the carriers.
Dependencies
None
1.6.3 SBFD-006004 UL 2x4 MU-MIMO

Availability

eLTE2.3
Summary
MU-MIMO enables multiple UEs to use the same time-frequency resource for uplink data
transmission. Compared with uplink receive diversity that brings diversity and array gains,
MU-MIMO also brings multiplexing gains.
Benefits
For some cameras in a dense area, traffic is relatively large, MU-MIMO effectively increases
cell capacity, improve spectral efficiency of the network.
Description
In MU-MIMO mode, the number of UEs that use the same time-frequency resource cannot
exceed the number of receive antennas employed on the eNodeB.
the principles of 2x4 MU-MIMO.
As shown in the previous figure, UE1 and UE2 use the same time-frequency resource to
transmit signals x1 and x2, respectively, on their channels to the eNodeB. After applying
weights to the signals received from antennas, the MIMO decoder in the eNodeB combines
two groups of receive signals into y1 and y2, which are the estimated values of x1 and x2,
respectively. The eNodeB calculates the weight w and detects the UEs that use the same
time-frequency resource for pairing.
The process of calculating the estimated values of signals x1 and x2 can be regarded as two
independent processes of receive diversity, and signals x1 and x2 can be regarded as
interference with each other. Therefore, MU-MIMO, similar to receive diversity, also brings
diversity and array gains.
2x2 MU-MIMO has the same principles as 2x4 MU-MIMO. Compared with 2x2 MU-MIMO,
2x4 MU-MIMO brings larger diversity and array gains, because it uses more receive antennas.
Therefore, 2x4 MU-MIMO more effectively increases cell throughput and spectral efficiency,
reduces the average service delay per cell, and ultimately improves user experience.

eLTE2.3
Dependencies
TDLOFD-001058 UL 2x4 MU-MIMO requires TDLOFD-00101502 Dynamic Scheduling
when the eNodeB schedules two UEs on the same time-frequency resource in the uplink.
When TDLOFD-001058 UL 2x4 MU-MIMO is used with TDLOFD-001016 VoIP
Semi-persistent Scheduling, the system gains are low. When four or fewer RBs are scheduled
in semi-persistent scheduling mode, UEs cannot be paired for MU-MIMO.
1.7 Reliability
1.7.1 SBFD-007001 eCNS Redundancy
Availability
Summary
In N+1 eCNS redundancy, one eNodeB can be connected to multiple eCNSs. Based on a
preset load sharing policy, the eNodeB assigns UE services to the eCNSs. If the eNodeB
detects that one eCNS is faulty, the eNodeB adjusts the load sharing policy based on the
configuration and transfers services of UEs connected to the faulty eCNS to another eCNS.
The call handled by the failure eCNS will be dropped, new call can be established in 10
seconds.
Benefits
This feature achieves core network redundancy and enhances the network availability. At the
same time, this feature increases the maximum data throughput when the network forwarding
capability is insufficient.
Description
An eCNS redundancy area is served by multiple eCNSs. The load sharing policy of an
eNodeB determines which eCNS a UE accesses. Therefore, the eNodeB needs to detect the
load status of the eCNSs. If the eNodeB detects that an eCNS is unavailable, the eNodeB
adjusts the load sharing policy and sends new UE service requests to other available eCNSs.
In addition, the eNodeB needs to obtain the eCNS load weights over the S1 interface and
select eCNSs for the UEs accordingly.
Table 1-6 Specifications of the eCNS redundancy feature
Item Specification Description
Network availability 4. 1 – (1 – System When one eCNS is used, the

availability)N network availability is equal to
the system availability.
Maximum data throughput of N x 4 Gbit/s N times the maximum data
the network throughput of a single eCNS.

eLTE2.3
NOTE
The value of N is less than or equal to 5.
Dependencies
Data is synchronized between the M2000 and each eCNS, and S1-Flex is enabled for the
eNodeB.
1.7.2 SBFD-007002 1+1 Backup of eCNS Boards

Availability
Summary
1+1 backup is applied to major eCNS boards to improve the reliability of the eCNS.
Benefits
The reliability of the eCNS is improved.
Description
The major boards of eCNS600 including work in 1+1 active/standby mode to ensure the
equipment reliability. Major eCNS600 boards include the OMU, ISU, SWU, USI, QXI, and
SWI. The board backup design helps increase the availability of eCNS600 to 99.999%.
Figure 1-9 1+1 backup configuration
Dependencies
None

eLTE2.3
1.7.3 SBFD-007003 1+1 Backup of the eNodeB Main Control Board

Availability
Summary
Huawei eNodeBs provide cold backup of the UMPT.
Benefits
The UMPT backup design helps increase the availability of the eNodeB to 99.999%.
Description
Two UMPTs are configured in the eNodeB. When the eNodeB starts up, it uses one of the
UMPTs as the active UMPT. The active UMPT performs control and operation functions and
provides ports to connect to the transmission network. If the active UMPT detects a hardware
or software fault, it switches over to the standby state. Meanwhile, the originally standby
UMPT switches over to the active state. Services can be recovered within 3 minutes. Users
can also manually switch over the UMPT using the element management system (EMS).
Dependencies
None
1.7.4 SBFD-007004 Baseband Board Backup (CPRI Backup)

Availability
Summary
In a Huawei eNodeB, multiple LTE Baseband Processing (LBBP) boards can be configured to
serve multiple cells. If an LBBP fails, the cell/cells served by the LBBP can be reestablished
on another operating LBBP with spare resources or on a backup LBBP if one is available.
Benefits
The system reliability can be ensured even when the LBBP or common public radio interface
(CPRI) is faulty.
Description
Generally, an eNodeB is equipped with multiple LBBP boards to serve multiple cells. Figure
1-10 shows a configuration example of 3 x 10 MHz 2T2R with CPRI backup.

eLTE2.3
Figure 1-10 3 x 10 MHz 2T2R
When an LBBP board fails due to a hardware or CPRI failure, the eNodeB can detect and
locate the failure and attempts to select a target LBBP board on which the cell/cells are to be
reestablished. The target LBBP should have a CPRI connection with the RRU serving the
cell/cells involved, as shown in Figure 1-10. The selection of a target LBBP board mainly
depends on the spare resources of the potential target LBBP board. If the target LBBP has
inadequate spare resources, the bandwidth of the reestablished cell/cells, or even that of the
existing cells, will decrease.
Dependencies
The eNodeB is equipped with at least two LBBP boards.
1.8 QoS Management

1.8.1 SBFD-008001 Basic QoS Management
Availability
Summary
In an LTE network, QoS policies vary with services.

eLTE2.3
Benefits
If different types of services are running on the network at the same time and these services
compete for bandwidth resources, operators can use QoS management to ensure that
high-priority services can be preferentially performed.
Description
The network maps user data onto various EPS bearers based on user data information such as
the source and destination IP addresses, source and destination IP port numbers, and protocol
type (for example, FTP and HTTP). A QoS policy applies to all the traffic carried on one type
of bearers. A different QoS policy applies to traffic carried on another type of bearers.
During initial attach, a default bearer is set up based on the QoS class that the user has
subscribed to. Therefore, at least one bearer is activated for each UE to ensure a short service
delay at the start of the service.
Each bearer has a QoS class identifier (QCI) and an allocation and retention priority (ARP).
The QCI and ARP determine QoS policies.
Table 1-7 Mapping between QCIs, services, and service requirements
QCI Resource Priority Data Packet Service Example

Type Delay Loss
Rate
1 GBR 2 100 ms 10-2 Conversational call

2 4 150 ms 10-3 Conversational video (live
streaming media)
3 5 300 ms 10-6 Non-conversational video
(buffered streaming media)
4 3 50 ms 10-3 Real-time game
5 Non-GBR 1 100 ms 10-6 IP multimedia subsystem (IMS)
signaling
6 6 100 ms 10-3 Voice, video (live streaming
media), or interactive game
7 7 300 ms 10-6 Video (buffered streaming
media), and TCP-based services
such as Internet surfing, email,
chatting, file transfer,
point-to-point (PTP) file sharing,
and progressive video scan
Detailed descriptions about the GBR, MBR, ARP, and AMBR are provided as follows:
The system reserves resources for guaranteed bit rate (GBR) services to ensure that data flows
with bit rates less than or equal to the GBR can be admitted. If the bit rates of some data flows
are greater than the GBR but lower than the maximum bit rate (MBR), the system rejects the
data flows in case of network congestion or admits the data flows when there is no network

eLTE2.3
congestion. Bearers that use GBR resources are GBR bearers, and other bearers are non-GBR
bearers.
The system prevents the bit rates of data flows from exceeding the MBR by limiting the
traffic volume. The MBR must be greater than or equal to the GBR. Currently, the MBR is
equal to the GBR due to the limitations in UE capability.
The ARP applies to both GBR and non-GBR bearers and is used for admission control. If
resources are insufficient, the system determines whether a bearer setup request can be
accepted based on the ARP of the bearer. The eNodeB can also use the ARP to determine the
preemption priority of existing bearers when a new bearer is set up. Different from the QCI
that is used after a bearer is set up, the ARP is used before a bearer is set up.
The system limits the traffic volume to prevent the total bit rate of a group of data flows from
exceeding the aggregate maximum bit rate (AMBR). Multiple EPS bearers can share an
AMBR. The AMBR applies to any individual EPS bearer when other EPS bearers do not
carry traffic. The total bit rate of all EPS bearers that share an AMBR cannot exceed the
AMBR. Extra traffic will be discarded. The AMBR applies only to non-GBR services.
Dependencies
None
1.9 Maintainability of Network Equipment

An eLTE network consists of radio access network (RAN) and core network elements,
network management system (NMS) server, and NMS client. The RAN and core network
elements process services and the NMS manages the RAN and core network elements.
Figure 1-11 shows the basic eLTE network topology.
Figure 1-11 Basic eLTE network topology
In eLTE2.1, the NMS is developed based on the M2000 and provides comprehensive
end-to-end (E2E) network management and maintenance functions. The major functions are
as follows:

eLTE2.3
 Equipment fault management: With real-time alarm lists and alarm logs, maintenance
personnel can have a comprehensive view of the actual status of the network at any time.
 Performance management: This function effectively monitors the network performance
for network troubleshooting and optimization.
 Configuration management: This function provides online and offline configurations,
which support quick installation, expansion, and configuration of the network.
1.1.1 SBFD-009001 Fault Management of NEs

Availability
Summary
This feature provides automatic fault monitoring and handling of NEs.
Benefits
Using real-time alarm lists and alarm logs, maintenance personnel can have a comprehensive
view of the actual status of the network at any time.
Description
Fault management includes fault detection, fault handling, fault correlation, and fault
reporting. With this feature, operators can be informed of faults in the network and take
appropriate actions to minimize or prevent service disruptions.
 Fault detection
Fault detection includes environment monitoring of the physical layer and data link layer,
key performance indicator (KPI) alarm monitoring, and other fault detection. A small
portion of faults may have a negative impact on services if self-testing, such as random
access memory (RAM) self-testing and transmission link loopback, is performed. Some
of those faults are automatically detected during the board startup, and some are
manually triggered by executing fault testing commands.
Fault detection methods are carefully designed to avoid false and intermittent alarms.
 Fault handling
The NEs perform fault isolation and automatic fault recovery to minimize the impacts on
services.
 Fault correlation
Fault management supports the fault correlation mechanism. This mechanism allows
operators to learn about the most important alarms (alarms whose root causes are severe
or impacts are major) instead of all alarms when faults occur. This greatly reduces the
number of alarms and facilitates network problem locating and troubleshooting. This
mechanism can be predefined and embedded in NEs. Operators can customize more
alarm correlation handling rules on the M2000.
 Fault reporting
Faults are reported to users in the form of alarms. With the fault correlation function, the
correlation information between alarms is contained in alarms. If any service-affecting
faults occur, operators can learn about the root faults simply by right-clicking the
service-affecting faults.

eLTE2.3
The operators can browse real-time alarm information, query historical alarm
information, and store alarm information. The online help provides detailed
troubleshooting methods for each type of alarm.
Dependencies
Fault management is implemented on the M2000.
1.9.2 SBFD-009002 Performance Management

Availability
Summary
This feature provides various performance measurement (PM) counters to monitor the
performance of NEs.
Benefits
Performance management effectively monitors the network performance so that network
troubleshooting and optimization can be implemented.
Description
Performance measurement provides detailed information about the network. Such information
facilitates troubleshooting and network optimization.
 Performance measurement management
The performance measurement management helps operators manage available
measurements.
A man-machine interface is available. The M2000 collects necessary statistics. Related
parameters can be set. These parameters include counters and measurement periods.
The statistics are obtained by the M2000 in binary format in each measurement period.
 Performance measurement counters
The performance measurement counters include key counters and other counters. Key
counters are used to generate KPIs. The KPIs, related original counters, and formulas can
be added, modified, and deleted on the M2000. Other counters reflecting other aspects of
network performance can be started when needed.
 Real-time KPI monitoring
This feature provides KPI monitoring and graphical reports for network performance,
which makes troubleshooting, drive tests, and network optimization more convenient.
The minimum sampling period is 10 seconds.
Dependencies
Performance management is implemented on the M2000.

eLTE2.3
1.9.3 SBFD-009003 Configuration Management

Availability
Summary
This feature provides online and offline configurations, which support quick installation,
expansion, and configuration of the network.
Benefits
This feature provides an overview of the current status of the network and supports quick
installation, expansion, and configuration of the network.
Description
Configuration management allows operators to collect and manage NE data. The NE data
covers the physical aspect (equipment) and logical/functional aspect (such as cells and links).
The graphical user interface makes the management implementation easier.
To minimize the impact of reconfiguration on the system, the Huawei configuration
management feature has the following characteristics:
 Physical modifications are independent of the related logical modifications.
 All the modifications required by a specified task are thoroughly checked to ensure their
validity before being applied to the system.
 The consistency of the configuration data between the NE and the M2000 is always
ensured.
You can use MML commands to modify and query all configuration data online.
Dependencies
Configuration management is implemented on the M2000 or the LMT.
1.10 Terminal Management

1.10.1 SBFD-010001 Remote CPE Upgrade
Availability
Summary
The terminal management system enables the remote upgrade of the CPE firmware.

eLTE2.3
Benefits
 Operating expense (OPEX) is reduced because onsite upgrade is not required.
 Rapid service provisioning improves user experience.
Enhancement
In eLTE2.3, users can configure whether a forced upgrade is performed if the device version
and target version are inconsistent.
Description
Upgrade can be performed on the firmware of a single device or a batch of devices. The
firmware file server can be either an external file server or a file server embedded in the
terminal management system. If a large number of CPEs are to be upgraded, the CPEs can be
divided into small batches to avoid potential network congestion. You can configure the
number of CPEs to be upgraded at the same time. The firmware upgrade task can be started
immediately or later.
Dependencies
None
1.10.2 SBFD-010002 Remote CPE Configuration

Availability
Summary
The terminal management system enables remote configuration for CPEs.
Enhancement
In eLTE2.3, batch configuration for multiple terminals and multiple configuration parameters
is supported.
Benefits
 OPEX is reduced because onsite configuration is not required.
 Rapid service provisioning improves user experience.
Description
Remote configuration is performed on CPEs based on the object model defined by the
TR-069 protocol suite.
The backup and restore of device configurations are supported.

eLTE2.3
Dependencies
None
1.10.3 SBFD-010003 Querying CPE Status

Availability
Summary
The terminal management system supports query of the CPE status.
Benefits
The terminal management system supports remote diagnosis to improve user experience.
OPEX is reduced.
Description
A device can be searched and recognized based on its attributes, such as device ID and MAC
address.
Data is displayed in tree structure.
Terminal logs can be obtained after the terminal uploads the log files.
Alarms are generated when faults occur. Alarms generated for a specific device can be viewed
on the interface of the terminal management system.
Dependencies
None
1.10.4 SBFD-010004 Monitoring CPE Performance

Availability
Summary
The terminal management system monitors the CPE performance counters.
Benefits
 The terminal management system supports remote diagnosis to improve user experience.
 OPEX is reduced.

eLTE2.3
Description
The terminal management system can select a terminal, add it to the monitoring list, and
configure the monitoring parameters.
Dependencies
None
1.10.5 SBFD-010005 Automatic CPE Deployment (PNP)

Availability
Summary
When a CPE is powered on for the first time, it automatically connects to the eSight and
triggers registration, firmware upgrade, and configuration file delivery.
Benefits
This feature improves user experience and reduces OPEX.
Description
A CPE can be automatically deployed only when both of the following conditions are met:
 The list of authorized CPEs has been imported into the eSight.
 The enterprise has purchased the license for this feature.
The automatic CPE deployment process consists of the registration, upgrade, and
configuration procedures. Due to the limited bandwidth in a wireless network, the upgrade
and configuration procedures can be skipped. The eSight user can omit the upgrade and
configuration procedures from the CPE deployment process on the plug and play (PNP)
interface. After a CPE has registered with the network, the PNP process is complete. The user
then manually upgrades the CPE firmware and delivers the configuration file to the CPE.
Dependencies
None
1.10.6 SBFD-010006 CPE Fault Management

Availability
Summary
The eSight can manage CPE alarms.

eLTE2.3
Benefits
Description
A CPE reports an alarm to the eSight upon detecting a fault. The eSight determines whether to
report an alarm to itself according to the customized rules.
Alarms must be reported in a specific format so that the eSight can parse them. After the
eSight parses the alarms, it acknowledges, unacknowledges, masks, and filters them according
to certain rules.
Dependencies
None
1.10.7 SBFD-010007 Remote CPE Maintenance

Availability
Summary
The eSight can remotely ping CPE IP addresses, restart CPEs, and restore CPE factory
defaults.
Enhancement
In eLTE2.3, a terminal configured with IP Ping parameters can initiate an IP ping test for
another destination address.
Benefits
Description
The eSight can remotely perform the following functions for CPEs
 Ping the CPE WAN IP addresses.
 A terminal configured with IP Ping parameters can initiate an IP ping test for another
destination address.
 Reboot the CPEs by remote CPE maintenance.
 Restore the CPE factory defaults.
 Display the operation results.
Dependencies
None

eLTE2.3
1.11 Transmission Networking

1.11.1 SBFD-011001 Star Topology
Availability
Summary
eNodeBs can be connected in star topology. This is a simple topology of eNodeB interfaces
(consisting of X2 and S1 interfaces).
Benefits
 Simple topology
 Simple management and high reliability
Description
Figure 1-12 Star topology
The eNodeBs support star topology. eNodeBs connect to the EPC through the layer 2 or layer
3 data network. The interface between the eNodeB and the core network is the S1 interface.
eNodeBs connect to and exchange information with each other over the X2 interface.
Dependencies
None

eLTE2.3
1.11.2 SBFD-011002 Chain Topology

Availability
Summary
eNodeBs can be connected in chain topology. This topology is applicable to narrow and
sparsely-populated areas.
Benefits
The chain topology reduces the costs of transmission equipment, engineering, construction,
and transmission link leases.
Description
eNodeBs can be connected in chain topology. This topology is applicable to narrow and
sparsely-populated areas, such as expressways and railways. In these areas, the chain topology
requires less transmission equipment. However, the chain topology reduces reliability because
signals travel through many intermediate systems.
Figure 1-13 shows the chain topology.
Figure 1-13 Chain topology
Dependencies
None
1.11.3 SBFD-011003 Tree Topology

Availability
Summary
eNodeBs can be connected in tree topology. This topology applies to microwave transmission
networks.

eLTE2.3
Benefits
The tree topology is applicable to microwave transmission networks. The tree topology
requires fewer transmission links than the star topology does.
Description
eNodeBs can be connected in tree topology. Most microwave transmission networks adopt the
tree topology.
The tree topology requires fewer transmission links than the star topology does. However, the
tree topology reduces reliability because signals are transferred through many intermediate
systems. If an upper-level eNodeB is faulty, the operation of the lower-level eNodeBs is
affected. The tree topology applies to large areas with sparse population. The capacity
expansion may result in network reconstruction.
Figure 1-14 shows the tree topology.
Figure 1-14 Tree topology
Dependencies
This feature is based on E1/T1 and Ethernet interfaces.
1.12 Broadband Data Service

1.12.1 SBFD-012001 VLAN
Availability

eLTE2.3
Summary
A virtual local area network (VLAN) is a logical subnet that is established on a physical
network. A VLAN covers a broadcast area and consists of multiple devices. VLANs
communicate with each other through routes.
The eCNS binds subinterfaces with a VLAN ID to implement VLAN functions.
If the layer 3 VLAN has been established, it is recommended that subinterfaces be configured
and bound with the VLAN to separate different users and services.
Benefits
 Increases the number of subinterfaces to support more VLANs.
 Controls traffic in networks, reduces costs in equipment, simplifies network management,
and improves network security and reliability.
Description
In a PS network, the eCNS performs the following VLAN functions:
 Separates traffic between VLANs
The eCNS binds the interfaces of different NEs with different VLAN IDs to identify
different types of services.
In addition, the eCNS can bind the interfaces of different PDNs with different VLAN
IDs to identify users.
 Adapts to peer devices
When VLANs have been configured for the router, switch, or firewall connected to the
eCNS, the eCNS must set up subinterfaces and bind these subinterfaces with associated
VLAN IDs.
 Increases the number of subinterfaces
When the physical ports on the eCNS, router, switch, or firewall are insufficient, the
eCNS sets up subinterfaces and binds these subinterfaces with VLAN IDs.
NOTE
If the eCNS binds a subinterface with a VLAN ID, the layer 2 or layer 3 devices connected to this
subinterface must be bound with the same VLAN ID to ensure proper commutation between the eCNS
and devices.
Enhancement
Table 1-8 eCNS versions that support VLAN
eCNS Version Description

eCNS600 V100R002C00 Second release.
One or more subinterfaces can be bound with a VLAN
ID.
eCNS600 V100R001C00 First release.
Only physical ports can be bound with VLAN IDs.

eLTE2.3
Dependencies
The router, switch, and firewall connected to the eCNS must support VLAN.
VLAN packet forwarding requires the route configuration on the eCNS.
1.12.2 SBFD-012002 OSPFv2

Availability
Summary
Open Shortest Path First (OSPF) is a link-state-based hierarchical Interior Gateway Protocol
(IGP) that the Internet Engineering Task Force (IETF) develops for large-scale and complex
networks.
The eCNS uses the OSPFv2 protocol to communicate with peer devices over the SGi
interface. It uses OSPF packets to exchange routing information with the peer devices. In this
way, network topology information is shared between the eCNS and peer devices.
Benefits
This feature enables flexible networking, easy maintenance, and dynamic adjustment.
Description
This feature implements the following functions:
 Adaptation to large-scale networks
OSPF supports networks on different scales, such as a network with hundreds of routers.
 Rapid convergences
Upon detecting network topology changes, OSPF sends update packets to synchronize
the change in an autonomous system (AS).
 Loop free
OSPF uses the shortest path tree (SPT) algorithm to calculate routes based on the
collected link status information. Therefore, no self-loop routes are generated.
A router uses OSPF to process the information in the routing table of an AS. In the AS,
each router running OSPF collects its link status information and broadcasts it to the
whole system through a flooding algorithm so that the system can maintain a
synchronized database of link status. Based on the database, the router can work out the
SPT with the router as the root and other network nodes as the leaves, and calculate the
optimal route to the system.
 Area partition
OSPF allows networks where ASs are located to be partitioned into different areas for
easy management. Routes that are transferred between these areas are further abstracted
to reduce the occupied network bandwidth.
 Equivalent routes

eLTE2.3
OSPF supports multiple equivalent routes to the same destination address.

 Hierarchical route
OSPF uses four types of routes: intra-area route, inter-area route, external type 1 route,
and external type 2 route. They are prioritized in descending order.
 Packet validation
OSPF supports interface-based packet validation to guarantee security for route
calculation.
 Multicast
OSPF supports multicast addresses.
Enhancement
None
Dependencies
OSPFv2 is an IGP that must be used within an AS. To support communication between ASs,
an Exterior Gateway Protocol (EGP), such as BGP-4, must be used.
OSPFv2 applies only to the SGi interface on the eCNS.
Standards
 RFC 791, Internet Protocol
 RFC 1155, Structure and Identification of Management Information for TCP/IP-based
Internets
 RFC 1131, OSPF specification
 RFC 1247, OSPF Version 2
1.12.3 SBFD-012003 VRF

Availability
Summary
Virtual routing and forwarding (VRF) is a means of implementing the virtual private network
(VPN) function. It enables the functions of multiple virtual routing devices to be implemented
on a single routing device. It is also used to logically define a physical device. Each VRF has
a separate routing table and address space.
eCNS supports VRF, and the functions of multiple logically separated virtual eCNS can be
implemented on one eCNS device. VPN instances can be created on the eCNS to implement
VRF.
Benefits
 This feature facilitates connections between the eCNS and intranets because the address
spaces of APNs of carriers' private networks can be reused.

eLTE2.3
 APN traffic can be separated to ensure network security.

 Interfaces of different VPN instances can use the same IP address, which conserves
public IP addresses.

Description
A VPN keeps the transferred data private from other VPNs. By taking advantage of this
feature on the eCNS, you can bind each APN to a separate VPN to divide the traffic of
different APNs. Through traffic separation and network division, the APN resources of a VPN
will not be used by other VPNs or subscribers of other VPNs on the network. Therefore, the
information in the VPN is secure.
A eCNS can be logically divided into multiple virtual eCNS through VRF. Each virtual eCNS
works independently as a eCNS and has its own routing table and interface for data
forwarding. In addition, traffic of different services can be separated.
Networking application: The problem of insufficient IP addresses can be solved by binding
physical interfaces (or Eth-trunk interfaces or sub-interfaces), logical interfaces, and routes to
VRF, and the traffic of the signaling plane, user plane, and operation and maintenance (OM)
data can be separated.
Service application: By binding APNs to VRF, multiple virtual routing areas are available on
one eCNS to realize the separation of addresses and routes among APNs.
Resource application: By binding address pools to VRF, address resources can be reused
Enhancement
None
Dependencies
Table 1-1 Interaction with other features
Feature Interaction
SBFD-012002 OSPFv2 One VRF support more than OSPF process, while
one OSPF process belongs to only one VRF.
SBFD-012006 Routing Behind MS Different UEs which support “Routing Behind MS”
can be separated by different VRFs。
Standards
RFC 2764, IP Based Virtual Private Networks
1.12.4 SBFD-012004 Local Routing

Availability

eLTE2.3
Summary
This feature enables an eCNS to forward service packets between two UEs connected to this
eCNS.
Benefits
No additional devices need to be deployed over the SGi interface for point-to-point (P2P)
packet transmission between two UEs.
Packet transmission delay decreases.
Description
Assume that two UEs (UE 1 and UE 2) are connected to an eCNS. After receiving a packet
from UE 1, the eCNS checks the destination IP address of the packet. If the destination
address is the IP address of UE 2, the eCNS directly forwards the packet to UE 2.
Figure 1-15 Local routing
UE1
UE2 eCNS
Enhancement
None
Dependencies
This feature does not take effect when the SGi interface packet redirection feature is enabled.
Standards
None
1.12.5 SBFD-012005 SGi Interface Packet Redirection

Availability

eLTE2.3
Summary
The SGi interface packet redirection feature prevents the eCNS from directly forwarding
service data between UEs and redirects UL service data to a specific PDN device, such as a
firewall, over the SGi interface.
Benefits
This feature ensures security of enterprise networks and communication between enterprise
users.
Description
The blue dashed lines in Figure 1-16 and Figure 1-17 indicate the data transmission paths when
this feature is enabled and disabled, respectively.
Most of firewalls do not use the same port to receive and transmit packets.
When this feature is enabled, a packet is transmitted between the eCNS and firewall as
follows:
1. The eCNS sends a packet to port A on the firewall, as shown in Figure 1-16.
2. After receiving the packet, the firewall checks it, and then transmits it to the eCNS
through port B if no error is detected.
Figure 1-16 Data transmission with the SGi interface packet redirection feature enabled
LPU interface A
UE1
SGi interface B
UE2 eCNS Firewall
When this feature is disabled, the eCNS directly forwards UL packets between UEs without
sending the packets to the firewall. As a result, user data security cannot be ensured.
Figure 1-17 Data transmission with the SGi interface packet redirection disabled
UE1
SGi interface
UE2 eCNS Firewall

eLTE2.3
Enhancement
None
Dependencies
When this feature is enabled, the local routing feature cannot take effect.
Standards
None
1.12.6 SBFD-012006 Routing Behind MS

Availability
Summary
When the routing behind MS feature is enabled in a mobile VPN, multiple terminals can
access the EPC and initiate bidirectional services to communicate with the application server
through a UE. After being activated in the EPC, the UE obtains a network segment and the
terminals can use IP addresses in this network segment to communicate with the EPC. This is
different from the NAT technology.
Huawei eCNS supports the routing behind MS feature controlled by the APN.
Benefits
 Supports mobile VPN services to improve working efficiency and reduce OPEX for
enterprises.
 Implements mobile offices for enterprise users to ensure flexible, quick, and secure
communication between enterprise branches and headquarters.
Users at the enterprise branches and headquarters can initiate bidirectional services to
communicate with each other.
Description
This feature mainly applies to mobile VPN users.
Both common users and mobile VPN users can access a network through a UE. However, the
network access procedure for mobile VPN users differs from that for common users.
 Multiple family users can use one household wireless router (it functions as a UE) to
access the network. Although the UE is configured with only one host IP address, it can
perform NAT to simultaneously meet data service requirements of multiple family users
because services requested in this scenario are unidirectional services.
 Mobile VPN users at the enterprise branches and users at the enterprise headquarters
initiate bidirectional services to communicate with each other. In this scenario, NAT
cannot be used. To address this issue, the routing behind MS feature is introduced.

eLTE2.3
Figure 1-18 shows the network structure for the routing behind MS feature.
Figure 1-18 Network structure for the routing behind MS feature
Local Access Network Backbone Network
IP Terminal
Subnet:A.B.C.x/24 Subnet:A.B.C.x/24
CPE eCNS Server
WiFi or Cable
LTE Network PDN
This feature involves the following NEs:

 UE
When requesting the establishment of the default bearer, a UE activates the EPS bearer
context to obtain one or more network segments, which are used to assign IP addresses
for terminals.
 eCNS
After receiving UL packets from a UE, the eCNS sets up a route to the PDN and
forwards the packets on this route. After receiving DL packets from the public network,
the eCNS sets up a route in the LTE network based on the destination IP address
contained in the packets and forwards the packets to the related UE.
 IP terminal
A UE connects to multiple terminals complying with the IP protocol, such as IP phones,
Wi-Fi terminals, and computers.
Enhancement
None
Dependencies
This feature requires the CPE to support the Routing Behind MS feature.
Standards
None

eLTE2.3
1.12.7 SBFD-012007 DHCP relay

Availability
Summary
DHCP relay allows the DHCP requests of the CPE lower devices to be forwarded to the core
network for address allocation. DHCP relay can only be used when Routing Behind MS is
enabled. When the CPE is activated on the EPC network, a gateway address can be
configured on the interface connecting the lower device. Terminals under the device can
obtain addresses from the core network by sending DHCP requests.
Whether to enable DHCP relay can be configured on the WebUI and TR069 management
software.
Benefits
DHCP relay allows the core network to manage CPE lower device address allocation and
maintenance.
Description
DHCP relay is used together with Routing Behind MS so that the core network can manage
CPE lower device address allocation.
Figure 1-19 shows the network structure for the DHCP relay feature.

eLTE2.3
Figure 1-19 Network structure for the DHCP relay feature
Remote Web-
based
eSight
managemet
The CPE supports DHCP relay. The
address for the PC relay under the CPE is
obtained from the core network, instead of Maintenance
from the CPE LAN side. management
OM
Switch DNS Server1
OM CPE EPC
VLAN1 Department a
DHCP Server
VPN1 EPS bears of APN1 VPN1
LAN_IPs WAN_IPs
公网 DNS Server2
VPN2 EPS bears of APN2
VPN2 (optional)
Department b
VLAN2 OM
Data Maintenance
stream stream
The main functional units are as follows:

 CPE
The CPE is a fixed terminal on the EPC network. When the CPE initiates a default
bearer setup request, a gateway address is obtained through the EPS bearer context
activation procedure. This address is reported to the DHCP server as the CPE lower
device gateway address during DHCP relay.
 DHCP server
The DHCP server receives DHCP relay messages forwarded by the CPE and returns a
DHCP request response message for allocating the PE lower device gateway address.
 VLANx
The VLAN connected to the CPE supports the IP protocol. The related devices include
IP phones and PCs.
Enhancement
None
Dependencies
The terminal must support DHCP relay.

eLTE2.3
Standards
None
1.13 Service Management

1.13.1 SBFD-013001 Offline Charging
Availability
Summary
The offline charging feature allows the eCNS to generate call detail records (CDRs) and send
them in GTPv2 packets to the charging gateway (CGW). After saving, combining, and
performing standardized preprocessing on these CDRs, the CGW generates a standard bill and
sends it to the billing system. In offline charging mode, the eCNS does not monitor user
account in real time, which is different from that in online charging mode.
Benefits
 Enterprise users are charged by service traffic or duration, which provides references for
service settlement between enterprises or between enterprises and operators.
 Enterprises can analyze user behaviors and habits based on the service usage in CDRs,
which helps enterprises to design their network operating strategies.
 Enterprise users can check service fees based on the service usage.
Description
This feature supports traffic- and service-duration-based charging modes and does not support
content-based charging mode.
Figure 1-20 shows the network structure for this feature.

eLTE2.3
Figure 1-20 Network structure for the offline charging feature
The eCNS and CGW cooperate with each other as follows:

1 The eCNS records the service usage and generates CDRs.
Based on a certain charging granularity preconfigured on the APN, an enterprise can
control whether the eCNS generates CDRs. If yes, the eCNS sends the generated CDRs
to the CGW.
A CDR contains multiple fields, such as the user identifier, time of starting a service, and
service duration, based on which the billing system charges the user.
CDR generation involves the following three procedures:
− Creating a CDR
When a user is performing a service, the service procedure triggers the eCNS to
create a CDR at a charging point. Then, the eCNS records the charging-related
actions of the user in the CDR.
− Creating an intermediate CDR
When specific conditions are met during service running, the eCNS creates an
intermediate CDR for the user. The conditions include the service duration threshold,
traffic threshold, tariff, and threshold for QoS change times.
− Closing a CDR
When a user stops using a service, the eCNS stops recording the charging-related
actions and generates the CDR.
In summary, when a user is performing a service, the eCNS generates one or more CDRs.
The CGW combines these CDRs for charging.
2. The eCNS uses Abstract Syntax Notation One (ASN.1) to encode the CDRs,
encapsulates them in GTPv2 packets, and then sends the packets to the CGW.

eLTE2.3
3. The CGW saves, combines, and performs standardized preprocessing on these CDRs,
and then sends them to the billing system. The billing system then generates a bill for the
user.
In addition, the eCNS provides the following functions:
 CGW load sharing
When the eCNS is connected to multiple CGWs, the eCNS can configure different
priorities or the same priority for these CGWs. If all available CGWs are of the same
type, the eCNS selects the CGW with the highest priority. If all available CGWs are
configured with the same priority, the eCNS selects the CGW that was earliest
configured with the priority.
When a CGW needs to process a large number of CDRs, the eCNS supports load sharing
between CGWs to reduce the load of this CGW and ensure the CDR transmission
reliability.
 CGW link detection
If the eCNS does not receive any responses after sending CDRs to the CGW, the eCNS
resends these CDRs to the CGW. If the eCNS still does not receive any responses from
the CGW within a specific period, the eCNS considers that the CGW is faulty.
When there is no CDR to transmit, the eCNS sends an echo message to the CGW every 2
minutes. If the eCNS does not receive any responses after sending three consecutive
echo messages, the eCNS considers that the CGW is faulty.
 CDR buffering
When the eCNS is disconnected from the CGW, the eCNS buffers CDRs. After the
communication between the eCNS and CGW recovers, the eCNS sends them to the
CGW.
Enhancement
None
Dependencies
None
Standards
 TS 32.240, Charging management; Charging architecture and principles
 TS 32.298, Charging management; Charging Data Record (CDR) parameter description
 TS 32.251, Charging management; Packet Switched (PS) domain charging
 TS 32.295, Charging management; Charging Data Record (CDR) transfer; Ga
1.13.2 SBFD-014001 Core Network Interoperability

Availability

eLTE2.3
Summary
In eLTE2.1, the eCNS600 is integrated with four logical modules: the HSS, MME, S-GW, and
P-GW.
In eLTE2.2, the eCNS600 is integrated with the logical modules based on required functions:
 HSS+MME+S-GW+P-GW
 HSS+MME+S-GW
 MME+S-GW+P-GW
 P-GW
In addition, the eCNS600 supports the S6a, S10, S5/S8, and Ga interfaces and therefore can
implement the functions of the preceding logical modules and communicate with other EPCs.
Benefits
This feature allows an enterprise network to communicate with the EPCs deployed by other
vendors.
Description
This feature complies with 3GPP Release 9 specifications.
Figure 1-21 shows the logical modules of three eCNS600s. They can communicate with
logical modules in the EPCs deployed by other vendors through the S6a, S10, and S5/S8
interfaces. In addition, these eCNS600s can communicate with Huawei CG9812 through the
Ga interface.
Figure 1-21 Network structure for communication with EPCs
NOTE
The interfaces supported by the eCNS600 depend on the logical modules with which the eCNS600 is
integrated. For example:

eLTE2.3
 If the eCNS is integrated with the MME, the eCNS supports the S6a interface between the MME and
HSS and the S10 interface between MMEs.
 If the eCNS is integrated with the P-GW, the eCNS supports the S5/S8 interface between the S-GW
and P-GW and the Ga interface between the P-GW and CGW.
In an small- or medium-scale enterprise network, the configuration

HSS+MME+S-GW+P-GW is recommended for the eCNS600. If an enterprise requires the
centralized management of wireless terminals, it is recommended that all subscription
information about enterprise users is saved on the HSS of one eCNS600 and other eCNS600s
obtain subscription information through the S6a interface.
If the application servers of an enterprise are densely deployed and far away from other
branches of this enterprise, it is recommended that an eCNS600 integrated with the P-GW be
deployed for the application server and function as the gateway to the internet and the
configuration HSS+MME+S-GW is recommended for the eCNSs at the branches. In this
networking mode, the enterprise service data is transmitted in the GTP-U tunnel over the
S5/S8 interface. This deployment ensures enterprise service security and simplifies the
network.
Dependencies
This feature requires the following features:
 eCNSFD-070300 S10 Interface
 eCNSFD-070700 S6a Interface
 eCNSFD-070600 Ga Interface
Standards
None

eLTE2.3
Broadband Access Solution Feature Description 2 Features Applicable to Specific Industries
2 Features Applicable to Specific Industries
2.1 Railway Communications

2.1.1 SOFD-010001 Common Calls
Availability
Summary
between two subscribers.
Benefits
Common calls are easy for subscribers to become accustomed with because common calls are
made in the same as that to make mobile calls.
Description
between two subscribers or between one subscriber and the DPT operator. A subscriber
initiates a common call by dialing the other subscriber's number and pressing the dial key.
Upon receiving the common call request, the trunking server notifies the other subscriber.
After the other subscriber picks up the call, a full-duplex connection is set up.
Dependencies
None
2.1.2 SOFD-010002 Function Number Addressing

Availability

eLTE2.3
Summary
This feature is tailored for Global System for Mobile Communications - Railway (GSM-R) to
meet requirements for communication and dispatch.
Benefits
Function numbers are specified based on positions, which simplifies the operation and
maintenance of numbers.
Description
A function number indicates a position (for example a train driver) instead of a subscriber.
The person on duty registers his or her subscriber number and sets up the mapping
relationship between the function number and the subscriber number. The dispatcher
dispatches the person on duty by dialing the function number. When the person on duty
changes, the subscriber number also changes but the function number remains unchanged as
long as the new person on duty has registered his or her subscriber number. The dispatcher
can still connect to the new person on duty by dialing the function number.
Dependencies
2.1.3 SOFD-010003 Location-based Addressing

Availability
Summary
This feature is tailored for GSM-R. With this feature, the called party can be connected to the
calling party based on the location of the calling party.
Benefits
This feature meets requirements for communication and dispatch for GSM-R.
Description
A short number can indicate multiple DPT operators that have the same duties but different
locations. When a subscriber dials a short number, the system routes the call to the DPT
operator in the same area with the calling party by using the location-based addressing.
Dependencies
None

eLTE2.3
2.1.4 SOFD-010004 Access Matrix

Availability
Summary
This feature is tailored for GSM-R to meet requirements for communication and dispatch by
designing connection strategies for common calls.
Benefits
Connection strategies can be designed for common calls to filter unnecessary calls.
Description
Subscribers on different positions have different function numbers in GSM-R. This feature
helps the system to determine whether the called or calling party is allowed to access the
GSM-R network based on the predefined access matrix.
Dependencies
None
2.1.5 SOFD-010005 Railway Group Calls

Availability
Summary
This feature provides voice services for a predefined group of subscribers within a predefined
area. Group members work in half-duplex communication mode.
Benefits
This feature provides group-oriented half-duplex voice communication services in area-based
dispatches. In these services, the traditional analog communication system is used, which can
meet requirements for dedicated dispatch communication.
Description
After data configurations about a group (group call number, mobile group members, and
group call coverage area) are complete on the trunking server, authorized group members can
initiate group calls by dialing the group call number.
After receiving the notifications of a group call, group members within the coverage area join
in the group call. Then, any member that has joined in the group call can initiate a
push-to-talk (PTT) call by holding down the PTT key on the mobile terminal.

eLTE2.3
During a PTT call initiated by a member (for example, subscriber A), other members in the
group can only listen to subscriber A (even if holding down the PTT key). Other members in
the group can only initiate a new PTT call after subscriber A finishes the PTT call and releases
the PTT key.
To terminate a group call, the subscriber that has initiated the group call presses the end key
on the mobile terminal. All members in the group then leave the group call.
A group generally includes a DPT operator. A DPT operator is a special subscriber defined in
the trunking server and can initiate PTT calls at anytime. In addition, depending on the
capability defined on the trunking server, a DPT operator can initiate or terminate group calls.
Dependencies
None
2.1.6 SOFD-010006 Railway Broadcast Calls

Availability
Summary
This feature provides broadcast voice services to a predefined group of subscribers within a
predefined area. Group members work in simplex communication mode.
Benefits
This feature provides group-oriented simplex broadcast voice services in area-based
dispatches, which meet the requirements for dedicated dispatch communication.
Description
After group members, the broadcast call number, and broadcast call coverage area are defined
on the trunking server, authorized group members can initiate broadcast calls by dialing the
broadcast call number. After receiving the notifications of a broadcast call, members of the
group within the broadcast area join in the broadcast call. Only the member (for example,
subscriber A) that initiated the broadcast call can speak. Subscriber A does not need to hold
down the push-to-talk (PTT) key on the mobile terminal and other members can only listen to
subscriber A. To terminate the broadcast call, subscriber A presses the end key. All members
then leave the broadcast call.
A broadcast group generally includes a DPT operator. A DPT operator is a special subscriber
defined on the trunking server. Depending on the capability defined on the trunking server, a
DPT operator can initiate or terminate broadcast calls. Note that DPT operators cannot speak
during a broadcast call initiated by another member.
Dependencies
None

eLTE2.3
2.1.7 SOFD-010007 Late Entry

Availability
Summary
A member can join in an ongoing group call or broadcast call.
Benefits
This feature allows late entry into an ongoing group call or broadcast call to accommodate
members who join late.
Description
Late entry into a group call or broadcast call usually occurs because:
 The mobile terminal was powered off when the group call or broadcast call was initiated.
 The group member was in an area with poor radio signal coverage.
In the preceding two situations, the member can join in the group call or broadcast call after
the mobile terminal is powered on or the member moves to an area with good wireless signal
coverage on the condition that the group call or broadcast call has not been ended.
Dependencies
None
2.1.8 SOFD-010008 Railway Emergency Calls

Availability
Summary
In emergencies, a group call can be quickly initiated in a restricted area. Members who join in
the group call will be recorded and they cannot leave the call before the call completes.
Benefits
Loss can be minimized in emergencies.
Description
Emergency calls in railway scenarios are special group calls with area restrictions. Different
from common half-duplex group calls with area restrictions, emergency calls in railway
scenarios have the following characteristics:
 One-key initiation: In emergencies, the user can press a dedicated key on the mobile
terminal to quickly initiate a call.

eLTE2.3
 Leaving not allowed: Users who have joined in an emergency call cannot use the
man-machine interface (MMI) to leave the call before the call is ended.
 Call confirmation: After the emergency call completes, all users who joined in the call
will be recorded.
Dependencies
None
2.1.9 SOFD-010009 Priority-based Call Preemption

Availability
Summary
This feature forces users in a low-priority call to leave the call so that they can join in a
high-priority call.
Benefits
The called party can immediately join in a high-priority call in dispatch communication.
Description
If priority-based call preemption is not used, a called party cannot be connected to a new call
when the called party is busy. If priority-based call preemption is used, a called party can be
connected to a new call even if the called party is busy. The trunking server compares the
priorities of the ongoing call and the new call. If the new call has a higher priority than the
ongoing call, the called party will be forced to leave the ongoing call and join in the new call.
There are seven priorities that are defined on the trunking server. Each user or group has a
priority.
The priorities of various call modes are as follows:
 The priority of a common call is the same as the default priority of the calling party.
 The priority of a half-duplex group call is the same as the default priority of the group.
 The priority of a simplex broadcast call is the same as the default priority of the group.
The consequence of preemption in each call mode is as follows:
 In a common call, if a party is preempted, the call will be released.
 In a half-duplex group call, if the talking is preempted, the floor will be released.
 In a simplex broadcast call, if the talking party is preempted, the call will be released.
Dependencies
None

eLTE2.3
2.1.10 SOFD-010010 Supplementary Services for Common Calls

Availability
Summary
Supplementary services for common calls are used together with common calls.
Benefits
User experience in common calls is improved.
Description
Supplementary services for common calls include the following services:
 Call forwarding - unconditional
This service allows an incoming common call to be forwarded to a preset phone number
irrespective of the status of the mobile subscriber.
 Call forwarding - busy
when the mobile subscriber is busy.
 Call forwarding - no reply
when the mobile subscriber does not answer the call within a specified time.
 Call forwarding - not reachable
when the mobile subscriber is unreachable.
 Call transfer
This service allows a mobile subscriber to relocate an existing call to another telephone.
 Barring of all outgoing calls
This service prevents a mobile subscriber from initiating a common call.
 Barring of all incoming calls
This service prevents a mobile subscriber from answering a common call.
 Call waiting
This service notifies a busy mobile subscriber of an incoming call and the mobile
subscriber can either accept or reject the incoming call.
 Call hold
This service allows a mobile subscriber to hold an ongoing call. When the call is on hold,
a recorded announcement is played for the other party. The call can be resumed when
required.
 Calling line identification presentation
This service allows the number of the calling party to be presented to the called party.
 Connected line identification presentation
This service allows the number of the called party to be presented to the calling party.

eLTE2.3
Dependencies
None
2.1.11 SOFD-010011 Inter-Network Connections

Availability
Summary
This feature allows the eLTE network to interwork with the public switched telephone
network (PSTN), public land mobile network (PLMN), and private automatic branch
exchange (PABX) network.
Benefits
With this feature, eLTE users can have voice communication with users of other external
networks.
Description
The eLTE network is connected to PSTN and PLMN switches using the integrated services
digital network user part (ISUP) and to PABX switches using the primary rate interface (PRI).
The connections allow eLTE users to initiate inter-network common calls.
Dependencies
None
2.1.12 SOFD-010012 CDR Generation

Availability
Summary
This feature allows the generation of call detail records (CDRs).
Benefits
With this feature, detailed information about calls made by a subscriber is recorded for future
query.
Description
CDRs about the following calls are generated:
 Common calls
A CDR is generated for a common call and includes the following fields: calling service
number, calling function number, called service number, called function number, LTE

eLTE2.3
cell ID of the calling party, LTE cell ID of the called party, start time for the common call,
stop time for the common call, and CDR type.
 Railway group calls
− A CDR is generated for an entire railway group call and includes the following fields:
railway group call number, number of the railway group call initiator, cell ID of the
railway group call initiator, start time for the railway group call, stop time for the
railway group call, and CDR type.
− A CDR is generated for a PTT call and includes the following fields: railway group
call number, number of the member starting the PTT call, cell ID of the member
starting the PTT call, start time for the PTT call, stop time for the PTT call, and CDR
type.
− A CDR is generated for each DPT operator in a railway group call and includes the
following fields: railway group call number, number of the DPT operator, start time
for the railway group call, stop time for the railway group call, and CDR type.
 Railway broadcast calls
− A CDR is generated for an entire railway broadcast call and includes the following
fields: railway broadcast call number, number of the railway broadcast call initiator,
cell ID of the railway broadcast call initiator, start time for the railway broadcast call,
stop time for the railway broadcast call, and CDR type.
− A CDR is generated for each dispatcher in a railway broadcast call and includes the
following fields: railway broadcast call number, number of the dispatcher, start time
for the railway broadcast call, stop time for the railway broadcast call, and CDR type.
 Railway emergency calls
− A CDR is generated for an entire railway emergency call and includes the following
fields: railway emergency call number, number of the railway emergency call initiator,
cell ID of the railway emergency call initiator, start time for the railway emergency
call, stop time for the railway emergency call, and CDR type.
− A CDR is generated for a PTT call and includes the following fields: railway
emergency call number, number of the member starting the PTT call, cell ID of the
member starting the PTT call, start time for the PTT call, stop time for the PTT call,
and CDR type.
− A CDR is generated for each participant in a railway emergency call and includes the
following fields: railway emergency call number, number of the participant, time that
the participant joins in the railway emergency call, time that the participant leaves the
railway emergency call, and CDR type.
 Forwarded calls
A CDR is generated for a forwarded call and includes the following fields:
− Calling service number
− Calling function number
− Service number from which the call is forwarded
− Function number from which the call is forwarded
− Service number to which the call is forwarded
− Function number to which the call is forwarded
− LTE cell ID of the calling party
− LTE cell ID of the party to which the call is forwarded
− Start time for the forwarded call
− Stop time for the forwarded call

eLTE2.3
− CDR type
 Transferred calls
A CDR is generated for a transferred call and includes the following fields:
− Calling service number
− Calling function number
− Service number from which the call is transferred
− Function number from which the call is transferred
− Service number to which the call is transferred
− Function number to which the call is transferred
− LTE cell ID of the calling party
− LTE cell ID of the party from which the call is transferred
− LTE cell ID of the party to which the call is transferred
− Start time for the transferred call
− Time when the transfer occurs
− Stop time for the transferred call
− CDR type
CDRs can be exported in .xls format.
Dependencies
None
2.1.13 SOFD-010013 SIP DPT Operator

Availability
Summary
With this feature, the Session Initiation Protocol (SIP) DPT operator accesses the trunking
server in a fixed manner. The SIP DPT operator can participate in and manage calls.
Benefits
The SIP DPT operator achieves scheduling of calls.
Description
The SIP DPT operator is the core of the dispatch system and provides the following functions:
 Makes common calls with mobile terminals
 Participates in group calls among mobile terminals
 Participates in broadcast calls among mobile terminals
 Multiple incoming calls
 Automatic answer
 Call hold

eLTE2.3
 Call break-in and forced subscriber release

 Remote activation and deactivation of mobile terminals
Dependencies
None
2.1.14 SOFD-010014 Call Recording

Availability
Summary
This feature allows the recoding and storing of subscribers' calls.
Benefits
With this feature, calls to and from an important subscriber can be recorded for future review.
Description
The following types of calls can be recorded: common calls, group calls, and broadcast calls.
Calls can be recorded and saved as .wav files.
Recorded calls can be queried using the subscriber number and group ID.
Playback of recorded calls is supported.
Dependencies
None
2.1.15 SOFD-010015 Call Signaling Tracing

Availability
Summary
With this feature, Session Initiation Protocol (SIP) signaling messages transmitted during calls
are traced in real time, stored, and reviewed.
Benefits
This feature traces signaling messages for all types of calls, which significantly improves the
operation and maintenance capability of the system.

eLTE2.3
Description
Signaling messages for the following calls are stored on the server for future review:
 Common calls
 Group calls with area restrictions
 Broadcast calls with area restrictions
 Railway emergency calls
Dependencies
None
2.1.16 SOFD-010016 Dual Network with Load-sharing

Availability
Summary
This feature applies to dual-layer networks where multiple types of terminals exist. With
user-based network management and load balancing functions, key services of terminals will
not be interrupted if a single point of failure occurs on the network. Both of the network
layers carry services, which maximize network resource utilization.
Benefits
Key services of terminals will not be interrupted if a single point of failure occurs on the
network. Air-interface, transmission, and other resources can be fully utilized.
Description
 Key services of terminals will not be interrupted if a single point of failure occurs on the
network. For example, a single point of failure will occur if a single-network cell is
faulty, the core network is faulty (can be caused by power-off of the service board or
core network), or S1 transmission is abnormal (can be caused by link disconnection).
 Both of the network layers carry services, which maximize network resource utilization.
Enhancement
None
Dependencies
None

eLTE2.3
2.2 wISP Communications

2.2.1 SOFD-010019 Home Broadband Data Services
Availability
Summary
This feature provides broadband data services for home users using the LTE network.
Benefits
This feature provides broadband data services to home users in areas where wired broadband
cannot be deployed.
Description
After a customer premises equipment (CPE) and antenna are installed, an RJ45 network port
is provided for each home user. After connecting a PC to the network port, the home user can
access data services such as Internet access.
A single CPE supports the access of multiple home users.
Enhancement
None
2.2.2 SOFD-010020 Home VoIP Services

Availability
Summary
This feature provides voice over Internet Protocol (VoIP) services for home users using the
LTE network.
Benefits
This feature provides fixed-line voice services to home users in areas where fixed-line phones
cannot be deployed.
Description
After a CPE and antenna are installed, an RJ11 network port is provided for each home user.
After connecting a fixed-line phone to the network port, the home user can access voice
services.
Other devices providing voice services can also be connected to the CPE.

eLTE2.3
The home user can access basic voice services on the PSTN, PLMN, and NGN networks.
A single CPE supports the access of multiple home users.
Enhancement
None
2.2.3 SOFD-010021 CPE-level Max-Rate Control

Availability
Summary
Different CPEs can be configured with different thresholds for the maximum uplink and
downlink rates.
Benefits
Service packages provided by telecom operators have different requirements for restricting
the maximum uplink and downlink rates. Home users who subscribe to different service
packages can access different CPEs configured with different thresholds for the maximum
uplink and downlink rates.
Description
Home users who subscribe to different service packages can access different CPEs configured
with different thresholds for the maximum uplink and downlink rates. This helps meet
different requirements for restricting the maximum uplink and downlink rates.
Different CPEs can be configured with different thresholds for the maximum uplink and
downlink rates.
Enhancement
None

eLTE2.3
2.3 Features of Radio Enhancement

2.3.1 SOFD-001001 Extended Cell Access Radius (TDD)
Availability
 This feature was introduced in eLTE2.3 and applies only to macro base stations.
 This feature does not apply to small cells.
 This feature cannot be used in the LampSite solution.
Summary
Appropriate preamble formats and special subframes are configured to expand RAN coverage.
In this way, cells whose radii are greater than 15 km are supported.
Benefits
This feature provides services in scenarios where cell radii are relatively large, such as seas,
deserts, and grasslands. This feature not only satisfies subscribers' communication demands
but also reduces network construction costs.
Description
This feature provides extended cell access radii to telecom operators. Appropriate preamble
formats and special subframes are configured so that cells whose radii are greater than 15 km
are supported.
When a UE initiates the random access procedure, an eNodeB allocates a random access
preamble to the UE. A preamble is a burst that contains cyclic prefix (TCP), time sequence
(TSEQ), and guide period (GP) in the time domain. There are five formats of random access
preambles, which are used for cells with different radii.
Table 2-1 Formats of random access preambles
Preamble Burst TCP TSEQ

Format
0 1000µs 103.1µs 800µs
1 2000µs 684.4µs 800µs
2 2000µs 203.1µs 1600µs
3 3000µs 684.4µs 1600µs
4 167.9µs 14.58µs 133.33µs
Periodic switching between uplink and downlink subframes is required in TDD networks, and
the GP is contained in special subframes. A TDD special subframe consists of three fields:

eLTE2.3
downlink pilot timeslot (DwPTS), GP, and uplink pilot timeslot (UpPTS), as shown in Figure
2-1. The total length of DwPTS, GP, and UpPTS is 1 ms (30720 Ts).
Figure 2-1 Special subframe structure
The DwPTS transmits downlink signals and carries data of the upper layer, which has the
same function as the downlink subframes. A DwPTS consists of 3 to 12 orthogonal frequency
division multiplexing (OFDM) signals, depending on the special subframe configurations.
The UpPTS transmits uplink signals but cannot carry data of the upper layer. It can be used as
a random access channel or transmit sounding reference signals (SRSs). An UpPTS consists
of one or two OFDM signals, depending on the special subframe configurations.
The length of GP depends on the transmitter transient period (TTP) and the round-trip delay
(RTD).
Special Common CP
Subframe
Time domain DwPTS GP UpPTS
SSP4 12 1 1
SSP5 3 9 2
SSP6 9 3 2
SSP7 10 2 2
Table 2-2 Different configurations of downlink-uplink subframes
TDD PRACH Preamble Special Maximum Cell

Downlink-Uplin Format Subframe Radius (km)
k Subframe Configuration
Configuration
SA2 0 SS6 20
SA1 1 SS5 77
SA1 2 SS6 29
SA0 1 SS5 77
SA0 2 SS6 29
SA0 3 SS5 93

eLTE2.3
Enhancement
None
Dependencies
The uplink and downlink links are imbalanced because their fading characteristics (including
uplink and downlink transmit power, antenna gain, and demodulation performance of
receivers) are different. Uplink coverage is limited in extended cell coverage scenarios.
Therefore, uplink coverage enhancement is required.
2.3.2 SOFD-001002 DL 2x2 MIMO (4-Antenna TDD)

Availability
Summary
Huawei LTE TDD eRAN1.0 supports DL 2x2 multiple-input multiple-output (MIMO),
2-antenna transmit diversity, and adaptive MIMO schemes between UEs and eNodeBs,
improving system downlink performance.
Benefits
This feature significantly improves downlink system throughput and coverage performance
and also provides good user experience by offering higher data rates.
Description
The downlink 2x2 MIMO is critical to the LTE outperforming the legacy system. Both space
diversity and spatial multiplexing are supported as defined in LTE specifications. Huawei
eNodeBs support two DL 2x2 MIMO modes:
 Transmit diversity
 Open-loop spatial multiplexing
 Closed-loop spatial multiplexing
 Closed-loop rank-1 precoding
If two transmit antennas are configured for the eNodeB, the eNodeB adaptively selects one of
the two modes based on the UE rate and downlink channel quality.
Transmit diversity and closed-loop rank-1 precoding are solutions to mitigate signal fading
and interference. By providing several signal branches that present independently varying
signal levels, the robustness of the radio link creates a low probability that all signal copies
are simultaneously in deep fading.
Spatial multiplexing can be classified into open-loop spatial multiplexing and closed-loop
spatial multiplexing. It is a technique to transmit independent and separately encoded data
signals, known as streams, from each of the transmit antennas that results in the space
dimension being reused, or multiplexed. If the transmitter is equipped with Ntx antennas and
the receiver has Nrx antennas, the maximum spatial multiplexing order is Ns = min (Ntx, Nrx).

eLTE2.3
If the spatial channels are independent of each other (that is, Ns different data streams are
transmitted over several independent spatial channels), it leads to an Ns increase of the
spectrum efficiency or capacity.
Enhancement
None
Dependencies
The eNodeB must be configured with two transmit channels and two antennas per sector, and
the UE must be configured with a minimum of two antennas for receiving.
2.3.3 SOFD-001003 UL 4-Antenna Receive Diversity (TDD)

Availability
Summary
Receive diversity is a common type of multiple-antenna technology to improve signal
reception and to mitigate signal fading and interference. It improves network capacity and
data rates. In addition to UL 2-antenna receive diversity, Huawei eNodeBs also support
4-antenna receive diversity.
Benefits
This feature improves uplink coverage and throughput.
Description
Receive diversity is a technique to mitigate signal fading and interference. Multiple
frequencies may be monitored from the same signal source or the same frequency may be
monitored from multiple antennas.
Receive diversity is a way to enhance uplink channel reception, including the PUSCH,
physical uplink control channel (PUCCH), physical random access channel (PRACH), and
sounding reference signal (SRS).
Huawei eNodeBs can work with or without RX diversity. In RX diversity mode, Huawei
eNodeBs in LTE TDD eRAN2.1 can be configured with 4 antennas (4-way) by setting the
antenna magnitude in addition to UL 2-antenna receive diversity.
Enhancement
None
Dependencies
This feature requires eNodeBs to provide enough RF channels and demodulation resources to
match the number of diversity antennas.

eLTE2.3
This feature cannot work when the bandwidth of the eNodeB equipped with the LBBPc is 5
MHz.
This feature cannot be used in the LampSite solution.
This feature is not applicable to micro eNodeBs.


ELTE2.3 Broadband Access Solution Feature Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ELTE2.3 Broadband Access Solution Feature Description

Uploaded by

Copyright:

Available Formats

eLTE2.

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Date Author Description

1 Common Features ......................................................................................................................... 1

1.5.5 SBFD-005005 Floor Preemption in a Group Call.................................................................................................... 28

1.13.2 SBFD-014001 Core Network Interoperability ....................................................................................................... 63

2 Features Applicable to Specific Industries ............................................................................ 66

1.1 LTE Wireless Broadband Communication

1.1.1 SBFD-001003 LTE TDD Mode

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 1

1.1.2 SBFD-001004 Scalable Bandwidths (TDD Mode)

1.1.3 SBFD-001005 Uplink-Downlink Configuration Types 1 and 2

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 2

Table 1-1 Subframe configurations for uplink-downlink configuration types 1 and 2.

Uplink-Downli Downlink-to- Subframe No.

In this table, D indicates subframes reserved for downlink transmission, U indicates

1.1.4 SBFD-001006 UL/DL QPSK, UL/DL 16QAM, and DL 64QAM

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 3

 64QAM: applicable only to the downlink.

1.1.5 SBFD-001007 AMC

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 4

1.1.6 SBFD-001008 DL Asynchronous HARQ

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 5

Downlink HARQ is an asynchronous adaptive transmission process, which means the UE is

1.1.7 SBFD-001009 Uplink Synchronous HARQ

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 6

1.1.8 SBFD-001010 Cell combination

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 7

Figure 1-1 Cell combination

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 8

1.2 Industry Spectrum Flexibility

1.2.1 SBFD-002001 Frequency Band Customization

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 9

Table 1-2 eLTE-supported LTE TDD frequency bands

Frequency Band Frequency Range

1.8 GHz 1785 MHz to 1805 MHz

2.3 GHz (band 40) 2300 MHz to 2400 MHz

3.5 GHz (band 42) 3400 MHz to 3600 MHz

3.7 GHz (band 43) 3600 MHz to 3800 MHz

1.3 Light-Weighted Industry Solutions

1.3.1 SBFD-003001 Single-Subrack Enterprise EPC

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 10

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 11

Figure 1-4 Integration policy for enterprise EPCs

1.3.2 SBFD-003002 Network Management Using a PC Server

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 12

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 13

1.3.3 SBFD-003003 Small EPC

Figure 1-5 Network position of the eCNS

SGW PGW PCRF

Uu MME HSS eCNS

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 14

1.3.4 SBFD-003004 Unified Network Management (eSight)

Table 1-3 eSight hardware specifications

1 CPU 2*6Core 2.5 GHz

Table 1-4 lists the hardware specifications of the eSight.

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 15

Table 1-4 eSight software specifications

No. Operating System Database

The eSight provides the following functions:

Issue 01 (2014-02-14) Huawei Proprietary and Confidential 16