This section presents the approach of SE service virtualization proposed in this paper. The work elaborated in this section is an exemplary case study that will be used later in the proof of concept. The CPES infrastructure is first presented followed by a description of SE service, with a focus of its execution modes and operational states. Next, the management of virtualized SE service with the aid of GFV is elaborated.
Infrastructure
In this paper, the exemplary PS model considered is the CIGRE MV benchmark grid (Alam et al. 2020). The grid consists of 15 busbars, with bus 0 considered to be the slack bus connected to the external grid. Operational technology (OT) devices (e.g., IEDs, RTUs) are located at the busbars (or sub-stations) as shown in the left side of Fig.1. Measurement data from OT devices is transmitted through the communication network to SE servers for processing.
Simulated model cyber-physical energy system
The communication network topology for the aforementioned power grid model is designed based on the methodology elaborated in Moussa et al. (2017), as shown in the right side of Fig.1. Each substation is associated with an edge router. Since there is no power lines between bus 0, bus 1 and bus 12, these three buses are located in the same substation, and are thus associated with one edge router. Local area network (LAN) is used for local communication between the devices in the substation (e.g., sensors) and the edge router. For wide area network (WAN), two communication architectures are elaborated taking into consideration the centralized and distributed SE implementations. A central architecture is considered for centralized execution of SE, where all OT devices send their data via the core routers to the central SE server located in the control room (CR). While for distributed execution of SE, a distributed architecture is considered, where the edge routers communicate with each other via communication links if the substations are neighbors (i.e., substations that are connected by power lines). Servers for distributed SE service are assumed to be located at bus 0, bus 5, bus 8 and bus 14, respectively.
Execution modes of SE service
The SE service estimates the PS state variables, i.e., bus voltage magnitudes and angles, based on field measurements. Typical measurements are line currents, active (P) and reactive (Q) power flows in the lines, and P and Q injections at buses. In centralized execution of SE service, measurements are transmitted from the sensors to the SE server via the communication network. The processing of the received measurements using a SE algorithm is done in the control room. Failures in the control room server cause the SE service to fail in case there is no backup or redundant server. A weighted least squares (WLS) algorithm, which is presented in Thurner et al. (2018), is used in this paper for centralized execution of SE service.
For the distributed execution of the SE service, the PS model addressed in this paper is assumed to be partitioned into four areas, having (n_{1}) = 4 buses (bus 1, 2, 3, 4), (n_{2}) = 3 buses (bus 5, 6, 7), (n_{3}) = 4 buses (bus 8, 9, 10, 11 ), and (n_{4}) = 3 buses (bus 12, 13, 14), respectively, as shown in Fig. 1. Note that this partition can be changed depending on the use case. Field measurements are transmitted locally to the appropriate SE servers via the inter-substation communication. Measurements are grouped as internal or local and boundary measurements. The SE servers perform the distributed SE algorithm by processing the internal measurements and exchanging the boundary measurements with the neighbor servers. For the distributed SE service, a WLS algorithm is considered as elaborated in Korres (2010).
Operational states of SE service
The performance of SE service can be assessed using three criteria—availability, latency, and correctness (Klaes et al. 2020). These criteria are used to qualitatively assess the impact of disturbances on the operation of SE service. Availability assesses the existence of required field measurements at a given time, which is the input for the SE service. Latency is a QoS requirement of the communication network and refers to the time between transmission and reception of data. Correctness captures the quality of input measurements, which directly impacts the quality of SE service output. It can be impacted by disturbances such as noise interference or cyber-attacks. The states of SE service can be defined as follows (Klaes et al. 2020; Hassan 2021):
Normal state All requirements of SE service are satisfied. Thus, SE service is fully functional and can be used by the operator to get real-time situational awareness of the PS. If no disturbances have impacted the SE service, or if the occurred disturbances have been absorbed, then the SE service is considered to be in normal state.
Limited state In this state, SE performance is partially degraded due to certain disturbances, which have impacted the availability, latency, and/or correctness. The operator is aware that the SE service needs to be used with caution as there is an increased risk of further degradation. This state characterizes the resiliency of the SE service.
Failed state This state indicates that the SE service is no longer functional, i.e., availability, latency, and/or correctness are violated. Therefore, it affects other grid services and can lead to inaccurate control actions. The operator should take suitable actions to restore the functionality of the SE service.
The operation of SE service depends on the availability of sensors, i.e., gathering field measurements, and on the SE servers, i.e., processing the field measurements and performing the SE algorithm. The solvability of a SE service requires the availability of sufficient field measurements. According to Korres (2010) and Salau et al. (2014), the typical condition for the solvability of SE service is(rho (H) = n) for centralized mode, where (rho (H)) is the rank of the measurement Jacobian matrix H and n the number of state variables. Similarly for distributed mode, the condition is (rho (H_{i}) = n_{i}), for each area (S_{i}). Field measurements in distributed mode include local measurements gathered via sensors and boundary measurements exchanged with the neighbor servers. Due to ICT disturbances, the available field measurements may not be sufficient to fulfill the solvability condition. Note that some disturbances such as link failures can be prevented with the distributed communication network architecture due to the local processing and the availability of alternative paths. In such cases, solvability can be satisfied by substituting the missing measurements with suitable pseudo measurements (m_{p}), which are derived based on historical data and have a higher standard deviation than field measurements (Dehghanpour et al. 2018). Therefore, using(m_{p}) increases the uncertainty in SE results. Based on this, states for centralized and distributed modes of SE which provide the operator with information about its performance can be outlined as shown in Fig. 2. Note that, latency and correctness are out of the scope of this paper, and will be considered in future work.
States of centralized and distributed SE service
Management
Virtualization of SE service requires management and orchestration of virtualization tasks examined throughout the life-cycle of a SE service. The GFV approach examined in Krüger (2020) is used for the management of the virtualized SE service. Service controller, local manager, and service description catalog are the main modules considered in this work. The local manager monitors the availability of virtualized SE service and the computational resources of hardware; and provides it to the service controller via the communication network. The communication network provides as well the service controller with information regarding its resources (e.g., latency). The service controller then aggregates the received information, and assesses the state of the virtualized SE service. This state provide the operator with additional information about the performance of SE. In the case of disturbances affecting the SE service (e.g., software failures), the service controller detects the performance degradation of SE service to failed state. The service description catalog (cf. descriptor files in Attarha et al. 2020) provides the service controller with information about the SE service in terms of its execution mode specifications (e.g., servers location, slack buses). Using these information, it reallocates the execution mode of SE service and sends the reconfiguration actions to the local managers. The local manager executes the received actions and starts running the new execution mode of the virtualized SE service (switching from central to distributed or vice versa).
Rights and permissions
Open Access This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons licence, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons licence, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons licence and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this licence, visit http://creativecommons.org/licenses/by/4.0/.
Disclaimer:
This article is autogenerated using RSS feeds and has not been created or edited by OA JF.
Click here for Source link (https://www.springeropen.com/)
