Anda di halaman 1dari 5

Analysis of NGMN Requirements

REQ 9: LTE Parameter Optimization

1
Specifications
Related 3GPP SA5 specifications
TS 32.521/522/523/525 “SON Policy NRM IRP”
TS 32.541/542 “SON Self-healing”

Current Status of the specifications


• TS 32.521: Requirements for Load Balancing and Handover parameters Optimization
have been completed in Release 9.
• TS 32.522: In Release 9, the targets of Load Balancing and Handover parameters
Optimization have been defined, and the definitions of common IOCs for Self-
Optimization management also have been completed.
• TS 32.523/32.525: CORBA SS & XML for SON Policy NRM IRP, to be completed by
June 2010 (Release 9 exception).
• TS 32.541: The use case and some requirements of Cell Outage Compensation have
been completed and will be finished in Release 10.
• TS 32.542: Some stage 2 description of Cell Outage Compensation has been agreed
and the related NRM IRP definitions will be completed in Release 10.

2
LTE Parameter Optimization

Requirements Existing 3GPP Standards Status

Automatic optimization of coverage and Some requirements have been defined in 3GPP TS
capacity related parameters in dependency 32.521 Release9.
of related KPIs and thresholds.

Automatic optimization of QoS and GoS Some requirements of RACH optimization have
related parameters (i.e. adaption of been defined in 3GPP TS 32.521 Release 9.
scheduling and / or RACH parameters) in
dependency of related KPIs and thresholds.

Automatic optimization of mobility and The Load balancing and HO parameters


handover related parameters (i.e. cell optimization related requirements, NRM and targets
individual offsets, down tilts, Event A have been completed in TS 32.521/522 in Release 9.
related parameters) in dependency of
related KPIs.
Automatic optimization of cells or services Some requirements and some stage 2 description
in outage based on an unambiguous of Cell Outage Compensation have been defined in
detection of this outage. draft TS 32.541/542.

3
LTE Parameter Optimization

Requirements Existing 3GPP Standards Status

Optimization for identified parameters shall The targets of Load balancing and HO parameters
be done within a value range, defined by the optimization have been defined in TS 32.522, which
operator can be set by the operator within a value range.
Optimization shall be done with respect to There is a related requirement (REQ-SO_MM-CON-
KPIs and parameters not directly related to 11 ) in TS 32.521, but the related IS and solution
the use case KPI (i.e. other KPIs shall not sets have not been completed.
become worse than defined thresholds (e.g.
handover optimization shall be done with
respect to capacity related parameters resp.
KPIs).
Dependency between KPIs resp. definition There is no related definition in existing standard.
which KPIs shall be considered in addition to
use case KPI(s) shall be configurable by the
operator.
Thresholds for start and end point of There is a related requirement(REQ-SO_MM-FUN-
parameter optimization shall be configurable 1 ) in TS 32.521, the targets of Load balancing and
by the operator. HO parameters optimization and the IOC of
SONTargets have been defined in TS 32.522.

4
LTE Parameter Optimization

Requirements Existing 3GPP Standards Status

Optimization cycle should be configurable There is a related requirement (REQ-SO_MM-CON-


(periodically, event-based) 6 ) in TS 32.521, but the related IS and solution
sets have not been completed.
Support of centralized / decentralized Based on the definitions of SONTargets and
solution SONControl in TS 32.522, this requirement has
been supported.
Degree of automation configurable by the The concept of “Open loop” , which is related with
operator. the configuration of the optimization cycle, has
o Optimization cycle completely automated: been discussed is SA5 and more discussion is
yes / no needed.
o Automated import of optimized settings: There is no related information about the
yes / no automated import of optimized settings in existing
standard.

Import / export function of network status There is no related information in existing


with history and fallback solution. standard.

OSS should provide standardized interfaces There is no related information in existing


to planning tools / processes. standard.