Transcript REQ 9 - 3GPP

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 SelfOptimization 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
capacity related parameters in dependency
of related KPIs and thresholds.
Some requirements have been defined in 3GPP TS
32.521 Release9.
Automatic optimization of QoS and GoS
related parameters (i.e. adaption of
scheduling and / or RACH parameters) in
dependency of related KPIs and thresholds.
Some requirements of RACH optimization have
been defined in 3GPP TS 32.521 Release 9.
Automatic optimization of mobility and
handover related parameters (i.e. cell
individual offsets, down tilts, Event A
related parameters) in dependency of
related KPIs.
The Load balancing and HO parameters
optimization related requirements, NRM and targets
have been completed in TS 32.521/522 in Release 9.
Automatic optimization of cells or services
in outage based on an unambiguous
detection of this outage.
Some requirements and some stage 2 description
of Cell Outage Compensation have been defined in
draft TS 32.541/542.
3
LTE Parameter Optimization
Requirements
Existing 3GPP Standards Status
Optimization for identified parameters shall
be done within a value range, defined by the
operator
The targets of Load balancing and HO parameters
optimization have been defined in TS 32.522, which
can be set by the operator within a value range.
Optimization shall be done with respect to
KPIs and parameters not directly related to
the use case KPI (i.e. other KPIs shall not
become worse than defined thresholds (e.g.
handover optimization shall be done with
respect to capacity related parameters resp.
KPIs).
There is a related requirement (REQ-SO_MM-CON11 ) in TS 32.521, but the related IS and solution
sets have not been completed.
Dependency between KPIs resp. definition
which KPIs shall be considered in addition to
use case KPI(s) shall be configurable by the
operator.
There is no related definition in existing standard.
Thresholds for start and end point of
parameter optimization shall be configurable
by the operator.
There is a related requirement(REQ-SO_MM-FUN1 ) in TS 32.521, the targets of Load balancing and
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
(periodically, event-based)
There is a related requirement (REQ-SO_MM-CON6 ) in TS 32.521, but the related IS and solution
sets have not been completed.
Support of centralized / decentralized
solution
Based on the definitions of SONTargets and
SONControl in TS 32.522, this requirement has
been supported.
Degree of automation configurable by the
operator.
o Optimization cycle completely automated:
yes / no
o Automated import of optimized settings:
yes / no
The concept of “Open loop” , which is related with
the configuration of the optimization cycle, has
been discussed is SA5 and more discussion is
needed.
There is no related information about the
automated import of optimized settings in existing
standard.
Import / export function of network status
with history and fallback solution.
There is no related information in existing
standard.
OSS should provide standardized interfaces
to planning tools / processes.
There is no related information in existing
standard.
5