Академический Документы
Профессиональный Документы
Культура Документы
V100R015C10
Issue Draft A
Date 2018-12-31
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.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
Draft A (2018-12-31)
This is the draft of this document.
Compared with Issue 01 (2018-06-30) of V100R013C10, this issue does not include any
changes.
The following figure shows the key services and supporting documents at each network stage.
Broadband (eMBB) network featured by large bandwidth, including basic capacity planning,
xMbps planning, and service KPI planning.
1.3.1.1 Overview
To meet subscribers' traffic demands and satisfy user experience on the network, the network
capacity needs to be planned based on operators' original requirements (especially traffic
requirements and user experience) and Huawei's recommended solutions.
The following figure shows inputs and outputs at the capacity planning stage.
The following figure shows the procedure for basic capacity planning.
l Perform the following steps to plan basic capacity at the network construction stage:
a. Understand operators' network construction requirements, including traffic demands
and user experience assurance solutions.
1.3.1.3 xMbps
xMbps planning aims to meet the data rate required by end users. It evaluates the data rates
supported by the air interface on a grid level to decide the difference between the current and
target data rates, and then provides advice on carrier capacity expansion and site planning by
means of simulation. The access data rates can be configured for WTTx users as required by
operators to serve as the planning target.
Mobile networks have entered the eMBB era from the voice era. In the eMBB era, media
streaming services are the leading services, and the next-stage high definition (HD) and ultra
high definition video services are taking the place of the currently leading low definition (LD)
and standard definition (SD) video services. eMBB service user experience greatly depends
on the bearer rate over the air interface, and a high bearer rate can ensure better user
experience.
xMbps Meaning
The xMbps bearer rate determines upper-layer user experience. Therefore, xMbps should be
customized during eMBB network construction based on user experience of the target service.
The customized xMbps is the minimum bearer capability for the target service on the eMBB
network and the minimum rate guaranteed for UEs.
xMbps for different types of services
The bearer rate varies according to the service type. eMBB services can be classified into
web, video, Voice over Internet Protocol (VoIP), social networking, instant message, cloud
services, email, file transfer, gaming, and machine-to-machine (M2M) services. xMbps for
different types of services to ensure good user experience is shown in the following figure.
Interrupt 0.8
ion-free
Share >
95%
Interrupt 2.3
ion-free
Share >
95%
Interrupt 3.8
ion-free
Share >
95%
Interrupt 7.7
ion-free
Share >
95%
NOTE
The bit rates of video services with different resolutions vary. Although the resolutions are the same, actual
bit rates vary obviously because of different dynamic aspect ratios and video coding levels. The statistical
results listed in the preceding table are measured based on the data from leading video websites.
A specific xMbps anywhere and anytime is not an absolute requirement. It can be defined as
follows from the perspective of engineering planning: The xMbps is reached in a specified
percentage (typical value: 95%) of places within a specified percentage (typical value: 90%)
of time to ensure user experience of a good level or above.
1. Deciding the target rate: A proper target rate is calculated based on the typical rate
required by services by analyzing service types and the ratio of each type of service. 10 Mbit/s
can meet 90% of service requirements on networks with non-video services. Therefore, 10
Mbit/s is used as the target rate during xMbps planning.
2. Evaluating grid-level rate capability: To evaluate the grid-level rate capability, calculate
the theoretical rate of each grid based on the channel quality indicator (CQI), number of users,
and available power in this grid, and then geographically display the rates in the grids.
3. Providing advice on planning: You can provide reasonable advice on carrier capacity
expansion and site planning through simulation and positioning based on the difference
between the current grid-level rate capability and the target rate. This method is also
applicable to multi-sector planning.
vMOS is designed to evaluate user experience of video services based on source video
quality, initial buffer duration, and video stalling rate. It is similar to MOS evaluation. The
following table lists details about the vMOS standard.
5 Excellent Imperceptible
2 Poor Annoying
The value of vMOS is based on sQuality (source video quality), sLoading (initial buffer
duration), and sStalling (video stalling ratio). sQuality determines the upper limit of the
vMOS value. The scores of sLoading and sStalling depend on video watching time. The
longer the watching time is, the smaller the impact of sLoading on the vMOS value is.
1.3.2 Dimensioning
At the dimensioning stage, the iterative service demands of capacity planning are used to
predict the demands of critical resources (such as air interface resources) for network
construction. These resources required at the dimensioning stage are abstract and irrelevant to
the network topology and hardware type.
The resources to be monitored can be classified into device and air interface resources:
l If device resources are found to be insufficient, add devices.
l If air interface resources are found to be insufficient, check whether capacity
optimization can relieve the congestion. Then, perform capacity expansion if the
congestion persists.
For details on resources and methods for capacity monitoring, see 5G RAN Capacity
Monitoring Guide.
For details about capacity optimization, see LTE Uplink Capacity Solution User Guide and
LTE Downlink Capacity Solution User Guide. To obtain this document, contact Huawei
technical support engineers.
On existing networks, traffic demands are affected by network capacity. That is, the traffic
demands may be not fully reflected due to network capacity restriction. Therefore, it is
required to decide whether the traffic demands are restrained before conducting network
capacity expansion.
Figure 1-12 Relationships between the system capacity and the number of users
a: point at which the actual system capacity begins to b: minimum system capacity demand designed by
decrease the operator
The following figure shows the relationships between the number of users and required
throughput, perceived throughput, as well as xMbps in typical eMBB traffic scenarios.
l In statistical sense, the required throughput is basically steady in specified traffic
scenarios (relevant to user types, service types, and charging policies). The capacity
demand is not affected by the number of users.
l The perceived throughput is first steady and then begins to decrease after the number of
users reaches the maximum limit allowed by the system capacity.
Figure 1-13 Relationships between the throughput and the number of users
c: target xMbps for the area where the network is constructed according to the xMbps standard
Capacity expansion focuses on system capacity and user throughput. The following table
describes the air interface capacity expansion standards.
Dimension Standard
NOTE
l After carriers are added, new cells and their neighboring cells (existing cells) are working in different
frequencies. Therefore, inter-frequency handover parameters must be properly configured to ensure
successful inter-frequency handovers. In this way, adding carriers will not decrease the handover
performance.
l For example, you can enable inter-frequency load balancing to ensure even load distribution on multiple
carriers.
l The inter-frequency handover policies and related parameter settings are complicated. For details, see
Mobility Management.
Adding gNodeBs
You can add intra-frequency and inter-frequency gNodeBs for small-scale capacity expansion.
Adding intra-frequency gNodeBs is more common due to carrier and networking restrictions.
l Adding intra-frequency gNodeBs
In some hotspot areas, adding intra-frequency gNodeBs improves the capacity in these areas,
but it also causes interference, which affects the coverage of existing cells. Therefore, you
need to optimize RF and network parameters after adding intra-frequency gNodeBs so that the
addition has less negative impact on the live networks.
This capacity expansion method is applicable when coverage holes exist, the number of users
reaches the maximum limit, or the throughput is limited due to capacity saturation. Add intra-
frequency gNodeBs when the following conditions are met:
l A second carrier is unavailable but a new site can be acquired.
l The interference from newly added intra-frequency gNodeBs is controllable and has
little impact on live networks.
l Emergency communications are required at places where the traffic volume surges, for
example, railway stations during holidays and stadiums with major events.
There is a rare scenario where an intra-frequency gNodeB is added at the same site to share
load on cells served by the existing gNodeB. This solution can only be used when the high
load on the existing gNodeB cannot be relieved after a main control board of higher
specifications is installed. For example, assume that the existing gNodeB serves three cells 0,
1, and 2, among which cell 0 has the largest number of users and the other two cells have
smaller number of users. You can use the main control board of the existing gNodeB to serve
cell 0 and use the main control board of the added gNodeB to serve cells 1 and 2. This
solution does not require cell addition or RF parameter optimization.
l Adding inter-frequency gNodeBs
Adding inter-frequency gNodeBs is preferred for capacity expansion if carriers are sufficient.
Unlike capacity expansion through adding intra-frequency gNodeBs, adding inter-frequency
gNodeBs does not cause intra-frequency interference. Theoretically, adding inter-frequency
gNodeBs doubles cell capacity.
This capacity expansion method is applicable when the number of users reaches the maximum
limit or the throughput is limited due to capacity insufficiency. Add inter-frequency gNodeBs
when the following conditions are met:
l A second carrier is available.
l A new site can be acquired. In this case, inter-frequency gNodeBs can be added in a
scattered way.
l The signaling load and user number reach the respective thresholds and capacity cannot
be expanded by adding inter-frequency cells.
Device capacity expansion must match the demands for air interface capacity.
Theoretically, if the system resource usage is measured on an extremely small percentage
(such as 1%) basis, capacity expansion can be performed based on network tolerance levels
for the resource insufficiency ratio. For example, capacity expansion is recommended for
networks requiring a low device resource insufficiency ratio when the probability of resource
usage higher than 90% exceeds a certain percentage (such as 5%). Capacity expansion is
recommended for networks tolerant of a high device resource insufficiency ratio when the
probability of resource usage higher than 99% exceeds a certain percentage (such as 5%).
The actual granularity for measuring resource usage cannot be as small as the theoretical
granularity. Only the average resource usage and maximum resource usage on the live
network are available for determining whether to expand the system capacity. Considering the
fluctuation in actual service demands, the measurement granularity is selected based on the
statistical data obtained during peak hours. The peak-to-average ratio should also be
considered to decrease the probability that device resources are insufficient.
For the capacity expansion thresholds for device resources, see 5G RAN Capacity Monitoring
Guide. The thresholds are the recommended values provided by Huawei based on empirical
network data and may be adjusted according to related experience and information.