Tech-
invite
3GPP
space
IETF
RFCs
SIP
Quick
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 32.816
Word version: 8.0.0
0…
2…
2
References
3
Definitions and abbreviations
4
Concepts and background
5
Requirements
6
E-UTRAN/EPC Management Architecture
7
Conclusions and recommendations
A
Reuse of 3GPP TSs for E-UTRAN and EPC management
B
Use case comparison to NGMN SON
$
Change history
2
References
3
Definitions and abbreviations
Word‑p. 8
3.1
Definitions
3.2
Abbreviations
4
Concepts and background
5
Requirements
5.1
Business level requirements
5.1.1
Void
5.1.2
Void
5.1.3
High Level Use Cases
Word‑p. 9
5.1.3.1
Self organising network
5.1.3.1.1
Establishment of new eNodeB in network
5.1.3.1.2
Optimisation of the neighbourhood list
Word‑p. 11
5.1.3.1.3
Coverage and capacity optimisation
Word‑p. 12
5.1.3.1.4
Optimisation of parameter due to trouble shooting
Word‑p. 13
5.1.3.1.5
Continuous optimisation due to dynamic changes in the network (like traffic variation)
5.1.3.1.6
Void
5.1.3.1.7
Handover Optimisation:
5.1.3.1.8
QoS related radio parameters optimization
Word‑p. 14
5.1.3.1.9
MBMS network Optimization
Word‑p. 15
5.1.4
Evolution of existing SA5 specifications
5.1.5
Establishment of new eNodeB in network
5.1.5.1
Automatic Radio Network configuration data preparation
5.1.5.2
Self-Configuration of a new eNodeB
Word‑p. 16
5.1.6
Trace in E-UTRAN/EPC
5.1.7
KPIs in E-UTRAN/EPC
5.1.8
Site Management
5.1.9
Void
5.1.10
Configuration Management of E-UTRAN/EPC
Word‑p. 17
5.1.10.1
General
5.1.10.2
Pool Management
5.1.11
Void
5.1.12
Neighbourhood list handling
Word‑p. 18
5.2
Specification level requirements
5.2.1
Void
5.2.2
Void
5.2.3
Void
5.2.4
Use cases
5.2.4.1
SON Use cases
5.2.4.1.1
Void
5.2.4.1.2
Establishment of new eNodeB in network
5.2.4.1.2.1
Void
5.2.4.1.2.2
Self-Configuration of a new eNodeB
Word‑p. 19
5.2.4.1.3
Void
5.2.4.1.4
Void
5.2.4.1.5
Void
5.2.4.1.6
Void
5.2.4.1.7
Void
5.2.4.1.8
Void
5.2.4.1.9
Void
5.2.5
Requirements
Word‑p. 21
5.2.5.1
Evolution of existing SA5 specifications
5.2.5.2
Automatic installation of NEs
5.2.5.3
Trace in E-UTRAN/EPC
5.2.5.4
KPIs in E-UTRAN/EPC
Word‑p. 23
5.2.5.5
Void
5.2.5.6
Fault Management of E-UTRAN/EPC
5.2.5.7
Configuration Management of E-UTRAN/EPC
5.2.5.8
Performance Management of E-UTRAN/EPC
Word‑p. 24
5.2.5.9
Establishment of new eNodeB in network
5.2.5.10
Optimisation of neighbourhood list
6
E-UTRAN/EPC Management Architecture
Word‑p. 25
6.1
Generic requirements for the management architecture
6.2
Management Reference Models
Word‑p. 26
6.2.1
Existing Management Reference Model
6.2.2
Use Case Specific Management Reference Models
6.2.3
E-UTRAN / EPC Management Reference Model
6.3
Procedure for the specification of the E-UTRAN/EPC Function Specific Management Reference Models
Word‑p. 27
6.4
Specification of the E-UTRAN/EPC Use Case Specific Management Reference Model
Word‑p. 28
6.4.1
Requirements
6.4.2
Use Case Specific Logical Architecture
6.4.2.1
Use case self-configuration of eNodeBs
6.4.2.x
Use case X
Word‑p. 29
6.4.3
Void
6.4.3.1
Use case self-configuration of eNodeBs
Word‑p. 30
6.4.3.x
Void
6.5
Void
7
Conclusions and recommendations
Word‑p. 31
7.1
Establishment of new eNodeB in network
7.1.1
Automatic Radio Network configuration data preparation
7.1.2
Self-configuration of a new eNodeB
7.2
Optimisation of the neighbourhood list
7.3
Coverage and capacity optimisation
7.4
Optimisation of parameter due to trouble shooting
7.5
Continuous optimisation of due to dynamic changes in the network
7.6
Handover optimisation
7.7
QoS related radio parameters optimisation
7.8
MBMS network optimisation
Word‑p. 32
7.9
Evolution of existing SA5 specifications
7.10
Trace in E-UTRAN/EPC
7.11
KPIs in E-UTRAN/EPC
7.12
Site management
7.13
Fault management of E-UTRAN/EPC
7.14
Configuration of E-UTRAN/EPC
7.14.1
Pool management
7.15
Performance management of E-UTRAN/EPC
A
Reuse of 3GPP TSs for E-UTRAN and EPC management
Word‑p. 33
A.1
TSs to be reused
B
Use case comparison to NGMN SON
Word‑p. 37
$
Change history
Word‑p. 38