Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TS 28.318
Word version: 18.1.0
0…
5…
5
Requirements
6
Informational model definitions
7
Stage 3 definitions
A
Procedures
B
Coordinated energy service recovery business relationship model
C
Coordinated energy recovery use cases supported
D
Unspecified needed configuration and functionality
E
UML source code
$
Change history
5
Requirements
p. 11
5.1
General
p. 11
5.2
Exposing performance and prediction information for high availability
p. 11
5.2.1
Description
p. 11
5.2.2
Requirements
p. 12
5.3
Exposed coordinated recovery requirements
p. 12
5.3.1
Description
p. 12
5.3.2
Requirements
p. 13
6
Informational model definitions
p. 15
6.1
Imported and associated information
p. 15
6.1.1
Imported information entities and local labels
p. 15
6.1.2
Associated information entities and local labels
p. 15
6.2
Class diagrams
p. 15
6.2.1
Relationships
p. 15
6.2.2
Inheritance
p. 16
6.3
Class definitions
p. 16
6.3.1
OutageAndRecoveryInfo
p. 16
6.3.2
EnergyServiceLocation <<datatype>>
p. 17
6.3.3
DsoThresholdMonitor
p. 18
6.4
Attribute definitions
p. 18
6.4.1
Attribute properties
p. 18
6.5
Performance Measurements and KPIs for NSOEU
p. 20
6.6
Common notifications
p. 20
7
Stage 3 definitions
p. 20
7.1
OpenAPI document for DSO NRM
p. 20
A
Procedures
p. 21
A.1
Exposing performance and prediction information for high availability
p. 21
A.1.1
DSO is trusted and supported by network operator, non-split gNB
p. 21
A.1.2
DSO is trusted and supported by network operator, split gNB
p. 32
A.2
Energy utility and telecommunication coordinated rapid recovery of energy service procedure
p. 43
A.2.1
General
p. 43
A.2.2
Signal flow
p. 43
B
Coordinated energy service recovery business relationship model
p. 44
C
Coordinated energy recovery use cases supported
p. 45
C.1
General
p. 45
C.2
Scenario #1: Energy service recovery with redundant energy distribution topology
p. 45
C.3
Scenario #2: Energy service recovery without redundant energy distribution topology
p. 49
D
Unspecified needed configuration and functionality
p. 53
D.1
General
p. 53
D.2
Service reachability configuration
p. 53
D.3
Service security management
p. 54
D.4
Service configuration
p. 54
E
(Normative) UML source code
p. 54
$
Change history
p. 63