6 Specification level requirements
28.3043GPPControl and monitoring of Power, Energy and Environmental (PEE) parameters Integration Reference Point (IRP)Release 17RequirementsTS
6.1 Requirements
6.1.1 Requirements for solution 1
REQ-PEECMON-OPT1-FUN-001: for configuration management purposes, requirements from either 3GPP TS 32.601 [5] clause 4, or from 3GPP TS 32.611 [8] clause 4.3, shall apply.
REQ-PEECMON-OPT1-FUN-002: for performance management purposes, requirements from 3GPP TS 32.411 [6] – clauses 4 and 5 – shall apply.
REQ-PEECMON-OPT1-FUN-003: for fault management purposes, requirements from 3GPP TS 32.111-1 [7] – clauses 4 and 5 – shall apply.
6.1.2 Requirements for solution 2
REQ-PEECMON-OPT2-FUN-001: The IRPAgent shall support a capability allowing the IRPManager to initiate / stop the retrieval of power, energy and environmental parameters of selected base stations.
REQ-PEECMON-OPT2-FUN-002: The IRPAgent shall support a capability allowing the IRPManager to periodically receive measured power, energy and environmental parameters values, for selected base stations.
REQ-PEECMON-OPT2-FUN-003: The IRPAgent shall support a capability allowing the IRPManager to be notified in case of power, energy and environmental parameters related alarms, for selected base stations.
REQ-PEECMON-OPT2-FUN-004: The IRPAgent shall support a capability allowing the IRPManager to be notified in case of power, energy and environmental parameters related configuration changes being detected by the IRPAgent, for selected base stations.
6.2 Actor roles
6.2.1 Actor roles for solution 1
IRPManager at the NM-RMS, controlling and monitoring PEE parameters of base stations in the radio access network.
IRPAgent at the DM, enabling to control and monitor PEE parameters of base stations with built-in sensors managed by the subject DM.
6.2.2 Actor roles for solution 2
IRPManager at the NM-RMS, controlling and monitoring PEE parameters of base stations in the radio access network.
IRPAgent at the DM, enabling to control and monitor PEE parameters of base stations with built-in sensors managed by the subject DM.
IRPAgent at the XCU/DGU, enabling to control and monitor PEE parameters of base stations with external sensors managed by the subject XCU/DGU.
IRPAgent at the VS- RMS, enabling to control and monitor PEE parameters of base stations with external sensors managed by the subject VS- RMS, via XCU/DGU.
6.3 Telecommunication resources
6.3.1 Telecommunication resources for solution 1
NM-RMS: The Network Management layer Remote Management Server controlling and monitoring PEE parameters of one or more base stations.
6.3.2 Telecommunication resources for solution 2
All telecommunication resources, as defined in clause 5.3.
6.4 Use cases
6.4.1 Use cases for solution 1
6.4.1.1 Use case: Initiating PEE performance management job
IRPManager initiates a PM job by sending appropriate request to IRPAgent, in compliance with PM IRP – cf. 3GPP TS 32.411 [6]. This use case corresponds to the high-level use case "Managing the monitoring of PEE parameters" (cf. clause 5.4.1 of the present document).
6.4.1.2 Use case: Controlling PEE related threshold
IRPManager sends appropriate request to IRPAgent, in compliance with PM IRP – cf. 3GPP TS 32.411 [6]. This use case corresponds to the high-level use case "Controlling PEE related parameters" (cf. clause 5.4.2 of the present document).
6.4.1.3 Use case: Supervising PEE related alarms
In case of PEE related alarms, IRPAgent emits alarm notifications to inform IRPManager, in compliance with Alarm IRP – cf. 3GPP TS 32.111-1 [7]. This use case corresponds to the high-level use case "Supervising PEE related alarms" (cf. clause 5.4.3 of the present document).
6.4.1.4 Use case: Monitoring PEE related configuration changes
In case of PEE related configuration changes, IRPAgent emits configuration change notifications to inform IRPManager, in compliance with Notification IRP – cf. 3GPP TS 32.301 [2]. This use case corresponds to the high-level use case "Monitoring PEE related configuration changes" (cf. clause 5.4.4 of the present document).
6.4.2 Use cases for solution 2
See use cases in clause 5.4.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2018-03 |
SA#79 |
SP-180071 |
Presented for approval |
2.0.0 |
|||
|
2018-03 |
SA#79 |
Upgrade to change control version |
15.0.0 |
||||
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |