Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TR 28.829
Study on Network and Service operations for Energy Utilities

3GPP‑Page   fToC↓   Partial Content →
V18.0.1 (Wzip)  2023/06  56 p.
Rapporteur:
Mr. Guttman, Erik
Samsung R&D Institute UK

full Table of Contents for  TR 28.829  Word version:  18.0.1

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
0Introduction  p. 6
1Scope  p. 7
2References  p. 7
3Definitions of terms, symbols and abbreviations  p. 8
3.1Terms  p. 8
3.2Symbols  p. 9
3.3Abbreviations  p. 9
4Overview  p. 9
4.1General  p. 9
5Concepts  p. 10
5.1Energy Service is Critical for Telecommunications Service Availability  p. 10
6Business use cases and potential requirements  p. 10
6.1Business use case: MNO exposes network performance monitoring  p. 10
6.1.1Description  p. 10
6.1.2Details  p. 11
6.1.3Potential Requirements  p. 13
6.2Business use case: Energy utility and telecommunication coordinated recovery of energy service  p. 14
6.2.1Description  p. 14
6.2.2Details  p. 17
6.2.3Potential Requirements  p. 18
6.3Business use case: Rapid intervention for outages without redundant energy feeder topology  p. 19
6.3.1Description  p. 19
6.3.2Details  p. 20
6.3.3Potential requirements  p. 23
7Key Issues and potential solutions  p. 24
7.1Key Issue #1: MNO exposes network performance monitoring  p. 24
7.1.1Description  p. 24
7.1.2Potential solutions  p. 24
7.1.2.1Potential Solution #1: MNO exposes network performance monitoring  p. 24
7.1.2.1.1Introduction  p. 24
7.1.2.1.2Description  p. 25
7.1.2.2Potential Solution #2: MNO exposes network performance monitoring  p. 26
7.2Void  p. …
7.3Key Issue #3: Energy utility and telecommunication coordinated recovery of energy service  p. 26
7.3.1Description  p. 26
7.3.1.1General  p. 26
7.3.1.2Coordinated recovery of energy service with redundant topology  p. 26
7.3.1.3Coordinated recovery of energy service without redundant topology  p. 27
7.3.2Potential Solutions  p. 27
7.3.2.1Potential Solution # 1: Energy utility and telecommunication coordinated rapid recovery of energy service  p. 27
7.3.2.1.1Introduction  p. 27
7.3.2.1.2Description  p. 28
7.3.2.2Potential Solution # 2: Energy utility and telecommunication coordinated rapid recovery of energy service  p. 30
7.4Key Issue #4: Security aspects of exposure of energy service  p. 30
7.4.1Description  p. 30
7.4.2Potential solutions  p. 30
7.4.2.1Potential solution #1: CAPIF  p. 30
7.4.2.2Potential solution #2: MSAC  p. 30
8Conclusion and recommendation  p. 30
8.1Key Issue #1: MNO exposes network performance monitoring  p. 30
8.2Key Issue #3: Energy utility and telecommunication coordinated recovery of energy service  p. 31
8.3Key Issue #3: Security aspects of exposure of energy service  p. 32
AService model for energy utilities and communication service providers  p. 33
BNetwork services and operations for energy utilities applicability statement  p. 34
CUse cases not pursued  p. 36
C.1General  p. 36
C.2Business use case: DSO obtains network performance and outage information, current practice  p. 36
C.2.1Description  p. 36
C.2.2Details  p. 39
C.2.3Potential requirements  p. 40
C.3Business use case: DSO reporting to MNO to resolve problems and incidents, current practice  p. 40
C.3.1Description  p. 40
C.3.2Details  p. 41
C.3.3Potential requirements  p. 42
C.4Business use case Energy Outage Coordination current practice  p. 43
C.4.1Description  p. 43
C.4.2Details  p. 43
C.4.3Use case actors  p. 44
C.4.4Use case service flow  p. 44
C.4.5Potential requirements  p. 44
C.5Business use case: MNO exposes Network Alarm  p. 44
C.5.1Description  p. 44
C.5.2Details  p. 45
C.5.3Potential Requirements  p. 46
C.6Business use case: DSO Provides Performance Information indicating Relevant Changes to its Network  p. 47
C.6.1Description  p. 47
C.6.2Details  p. 47
C.6.3Potential Requirements  p. 49
C.7Business use case: DSO reports an incident to MNO  p. 49
C.7.1Description  p. 49
C.7.2Details  p. 50
C.7.3Potential Requirements  p. 51
DKey issues not pursued  p. 53
D.1Key Issue # 2: DSO reports an incident to the MNO  p. 53
D.1.1Description  p. 53
D.1.2Potential Solutions  p. 53
D.1.2.1Potential Solution # 1: TMF API 621 (Trouble Ticket)  p. 53
D.1.2.1.1Introduction  p. 53
D.1.2.2Potential Solution # 2: MnS-based standardized interface  p. 53
D.2.2.2.1Introduction  p. 53
$Change history  p. 54

Up   Top