IO virtualization and GOOSE / SV engine collaboration method in protection measurement and control

Abstract

The invention provides an IO virtualization and GOOSE / SV engine collaboration method in protection measurement and control, and relates to the technical field of protection measurement and control, and the method comprises the steps: traversing a physical IO of a protection measurement and control device, abstracting the physical IO into a virtual IO resource unit, and constructing an IO virtual resource pool; a GOOSE / SV engine is embedded in an exchange chip layer between the IO virtual resource pool and the physical IO, and parameters are configured; building an IO resource scheduling module, establishing a communication link with an IO virtual resource pool and a GOOSE / SV engine, and formulating a virtual resource allocation rule and a signal transmission priority strategy; a device access request or a physical IO upgrading instruction is received, a virtual IO resource unit and a physical IO are mapped through an IO resource scheduling module, and a GOOSE / SV engine processes protocol analysis, encoding and decoding and timing receiving and sending of signals, so that IO virtualization adaptation is achieved, the processing time delay of the GOOSE / SV engine is shortened, and the maintenance cost is reduced.

Description

Technical Field

[0001] This invention relates to the field of protection and control technology, and in particular to a method for coordinating IO virtualization and GOOSE / SV engine in protection and control. Background Technology

[0002] Traditional protection and control devices suffer from significant drawbacks in their I / O modules and GOOSE / SV signal processing. Physical I / O interfaces are tightly bound to the device, resulting in rigid functionality and extremely poor adaptability. Replacing or upgrading hardware requires simultaneous modifications to the underlying software drivers and even refactoring of functional modules, extending hardware upgrade cycles and significantly increasing adaptation costs. The protocol parsing of GOOSE / SV signals relies on the main control CPU, consuming substantial CPU resources and introducing additional transmission delays due to bus interaction, making it difficult to meet the speed requirements of protection signals. Furthermore, traditional solutions have complex maintenance processes and insufficient adaptability to scenarios involving multiple sensor types and frequent operating condition changes, further increasing on-site maintenance costs and hindering the intelligent upgrade of protection and control systems.

[0003] Therefore, it is necessary to provide a method for coordinating IO virtualization and the GOOSE / SV engine in protection and control to solve the above-mentioned technical problems. Summary of the Invention

[0004] To address the aforementioned technical problems, this invention provides a method for coordinating IO virtualization and the GOOSE / SV engine in protection and control, which solves the problems of traditional IO being strongly bound to devices and GOOSE / SV processing relying on the CPU, resulting in difficulties in adaptation, high latency, resource waste, and high maintenance costs.

[0005] The present invention provides a method for coordinating IO virtualization and GOOSE / SV engine in protection measurement and control, the method comprising: Based on SR-IOV technology, the physical I / O of the protection and control device is traversed, the parameters of the physical I / O are extracted, the physical I / O is abstracted into a dynamically allocable virtual I / O resource unit, and a programmable virtual I / O resource pool is constructed. A hardware-level GOOSE / SV engine is embedded in the switching chip layer between the IO virtual resource pool and the physical IO, and the communication interface, clock frequency and cache capacity of the GOOSE / SV engine are configured to complete the connection and initialization of the GOOSE / SV engine with the hardware layer. Build an IO resource scheduling module, establish communication links between the IO resource scheduling module and the IO virtual resource pool and the GOOSE / SV engine, formulate virtual resource allocation rules and GOOSE / SV signal transmission priority strategies, and form a collaborative control of the IO resource scheduling module, the IO virtual resource pool and the GOOSE / SV engine; Upon receiving a device access request or physical IO upgrade instruction, the virtual IO resource unit is matched and mapped to the physical IO through the IO resource scheduling module. The GOOSE / SV engine directly processes the protocol parsing, encoding, decoding, and timed transmission and reception of GOOSE / SV signals, completing low-latency transmission and hardware adaptation of GOOSE / SV signals without modifying the underlying driver software.

[0006] Preferably, the construction process of the IO virtual resource pool is as follows: The device parameter acquisition tool is used to scan all the physical I / Os of the protection and control device, and the unique port identifier, supported communication protocol, maximum data transmission bandwidth and signal type of each physical I / O are recorded to form a physical I / O parameter list; According to the communication protocol, the physical I / O in the physical I / O parameter list are classified, and physical I / O with the same or compatible communication protocol are grouped together to ensure that the signal processing logic of the physical I / O within the same group is consistent. Based on SR-IOV technology, each group of physical I / O is abstracted, and several virtual I / O resource units with uniform specifications are generated for each group of physical I / O. A unique virtual identifier and independent memory address space are assigned to each virtual I / O resource unit, and the parameter mapping relationship between the virtual I / O resource unit and the corresponding physical I / O is clarified. Integrate all the virtual IO resource units, construct a resource pool management ledger and record the identifier, associated physical IO information, current occupancy status and available bandwidth of all the virtual IO resource units, and output a programmable IO virtual resource pool.

[0007] Preferably, the parameter configuration process for the virtual I / O resource unit is as follows: Analyze the signal transmission requirements of typical devices, namely the minimum data transmission bandwidth, signal response time, and protocol compatibility requirements of the typical devices; Based on the maximum transmission bandwidth of the physical I / O and the device requirements, the standard bandwidth and signal processing capability of a single virtual I / O resource unit are set so that a single virtual I / O resource unit meets the signal transmission requirements of at least one type of typical device. Based on the signal type of the physical I / O, configure signal conversion logic for the corresponding virtual I / O resource unit, configure level conversion adaptation module for the virtual I / O resource unit corresponding to digital physical I / O, and configure AD / DA conversion adaptation module for the virtual I / O resource unit corresponding to analog physical I / O. Perform functional tests on the configured virtual I / O resource unit to verify whether the virtual I / O resource unit can normally receive, process and forward the corresponding physical I / O signals.

[0008] Preferably, the embedding process of the GOOSE / SV engine is as follows: Collect key characteristics of GOOSE / SV signals in protection and control scenarios, including signal frame structure, transmission period, priority level and fault tolerance requirements; Select a switching chip that supports hardware-level protocol processing in the switching chip layer between the IO virtual resource pool and the physical IO, integrate the GOOSE / SV engine into the switching chip, and configure the communication interface, clock frequency and buffer capacity of the GOOSE / SV engine according to the key characteristics of the GOOSE / SV signal. A virtual IO channel connecting the GOOSE / SV engine to the IO virtual resource pool, and a hardware interface connecting the GOOSE / SV engine to the physical IO.

[0009] Preferably, the process of building the IO resource scheduling module is as follows: The core functional modules of the IO resource scheduling module are designed, including a resource status monitoring module, a request parsing module, and an instruction generation module; Establish a communication link between the IO resource scheduling module and the IO virtual resource pool. The module obtains the occupancy status, available bandwidth, and associated physical IO information of the virtual IO resource unit in real time through the communication link, and sends resource allocation or release instructions to the IO virtual resource pool at the same time. Establish a communication link between the IO resource scheduling module and the GOOSE / SV engine. Obtain the signal processing status, buffer utilization rate and current signal type of the GOOSE / SV engine through the communication link. At the same time, send signal priority adjustment instructions and transmit / receive cycle modification instructions to the GOOSE / SV engine. The virtual resource allocation rules and the GOOSE / SV signal transmission priority strategy are formulated and embedded into the instruction generation module of the IO resource scheduling module.

[0010] Preferably, the collaborative control process of the IO resource scheduling module, the IO virtual resource pool, and the GOOSE / SV engine is as follows: Define the triggering conditions for the collaborative control process. When the collaborative control process is triggered, the IO resource scheduling module first collects the real-time status of the IO virtual resource pool and the GOOSE / SV engine, and then generates resource allocation instructions and engine adjustment instructions, which are sent to the IO virtual resource pool and the GOOSE / SV engine respectively and wait for feedback. A feedback verification mechanism is configured. The IO resource scheduling module receives the resource allocation result feedback from the IO virtual resource pool and the instruction execution result feedback from the GOOSE / SV engine. If the feedback result shows that the instruction execution failed, a new instruction is generated and the above feedback process is repeated.

[0011] Preferably, the dynamic adaptation process for the device access request is as follows: Receive the device access request, which includes device type, communication protocol, data transmission requirements, and target physical I / O identifier; The scheduling module parses the device access request and, based on the communication protocol and the target physical IO identifier, selects idle virtual IO resource units in the IO virtual resource pool that are associated with the target physical IO and support the communication protocol. The IO resource scheduling module sends resource allocation instructions to the IO virtual resource pool, establishes a mapping relationship between the selected virtual IO resource units and the target physical IO, and sends signal processing instructions to the GOOSE / SV engine. The device sends a test signal through the mapping channel between the virtual IO resource unit and the target physical IO. The GOOSE / SV engine receives and processes the test signal and then feeds back the processing result. If the processing result is normal, the device access adaptation is completed. If the processing result is abnormal, the virtual IO resource unit is re-selected and the adaptation process is repeated.

[0012] Preferably, the dynamic adaptation process of the physical I / O upgrade instruction is as follows: Collect the parameters of the upgraded physical I / O and compare them with the parameters of the physical I / O to determine the parameter differences; The IO resource scheduling module selects virtual IO resource units that support the parameters of the new physical IO from the IO virtual resource pool according to the parameters of the new physical IO. If there is no virtual IO resource unit that supports the parameters of the new physical IO, the new physical IO is abstracted based on SR-IOV technology to generate a new virtual IO resource unit. The IO resource scheduling module updates the mapping table between the virtual IO resource unit and the physical IO, deletes the association between the physical IO and the virtual IO resource unit, and establishes a mapping relationship between the new physical IO and the selected virtual IO resource unit or the new virtual IO resource unit. Send a test GOOSE / SV signal to the new physical IO to verify the validity of the mapping between the selected virtual IO resource unit or the new virtual IO resource unit and the new physical IO, as well as the correctness of the signal processing of the GOOSE / SV engine, so that the upgraded new physical IO works normally without modifying the underlying driver software.

[0013] A protection and control measurement and control IO virtualization and GOOSE / SV engine collaborative system, the system comprising: The resource pool construction module is used to traverse the physical I / O of the protection and control device based on SR-IOV technology, extract the parameters of the physical I / O, abstract the physical I / O into dynamically allocable virtual I / O resource units, and construct a programmable virtual I / O resource pool. An engine embedding module is used to embed a hardware-level GOOSE / SV engine into the switching chip layer between the IO virtual resource pool and the physical IO, and to configure the communication interface, clock frequency and cache capacity of the GOOSE / SV engine, and complete the connection and initialization of the GOOSE / SV engine with the hardware layer. The collaborative control module is used to build the IO resource scheduling module, establish communication links between the IO resource scheduling module and the IO virtual resource pool and the GOOSE / SV engine, formulate virtual resource allocation rules and GOOSE / SV signal transmission priority strategies, and form collaborative control of the IO resource scheduling module, the IO virtual resource pool and the GOOSE / SV engine. The signal processing module is used to receive device access requests or physical IO upgrade instructions. It matches and maps the virtual IO resource units with the physical IO through the IO resource scheduling module. The GOOSE / SV engine directly processes the protocol parsing, encoding, decoding and timed transmission and reception of GOOSE / SV signals to complete the low-latency transmission and hardware adaptation of GOOSE / SV signals without modifying the underlying driver software.

[0014] Compared with related technologies, the method for coordinating IO virtualization and GOOSE / SV engine in protection measurement and control provided by this invention has the following beneficial effects: This invention, based on SR-IOV technology, traverses the physical I / O of protection and control devices, extracts the parameters of the physical I / O, and abstracts the physical I / O into dynamically allocable virtual I / O resource units, constructing a programmable virtual I / O resource pool. A hardware-level GOOSE / SV engine is embedded in the switching chip layer between the virtual I / O resource pool and the physical I / O, and the communication interface, clock frequency, and cache capacity of the GOOSE / SV engine are configured to complete the connection and initialization between the GOOSE / SV engine and the hardware layer. An I / O resource scheduling module is built, establishing a communication link between the I / O resource scheduling module and the virtual I / O resource pool and the GOOSE / SV engine, and defining virtual resource allocation rules and GOOSE / SV... The V signal transmission priority strategy forms a collaborative control mechanism among the IO resource scheduling module, the IO virtual resource pool, and the GOOSE / SV engine. Upon receiving device access requests or physical IO upgrade commands, the IO resource scheduling module matches and maps virtual IO resource units to physical IO. The GOOSE / SV engine directly handles the protocol parsing, encoding, decoding, and timed transmission and reception of GOOSE / SV signals, achieving low-latency transmission and hardware adaptation of GOOSE / SV signals without modifying the underlying driver software. This enables dynamic adaptation of IO virtualization, reduces the processing latency of the GOOSE / SV engine, lowers maintenance costs, and meets the low-latency, high-reliability requirements of protection and control systems.

[0015] This invention utilizes a programmable I / O virtual resource pool built on SR-IOV technology, breaking the dependency of "software modification for hardware upgrades." Hardware upgrades do not require modification of the underlying driver, significantly improving I / O function configuration efficiency and adapting to various device types and operating condition switching requirements. The hardware-level GOOSE / SV engine of this invention is embedded in the switching chip layer, directly carrying out protocol parsing, encoding, decoding, and timed transmission and reception functions, shortening the processing latency of the GOOSE / SV engine and fully meeting the low latency and high reliability requirements of protection and control systems. The GOOSE / SV engine of this invention offloads the CPU's protocol processing load, freeing up main control CPU resources to focus on core tasks such as power quality analysis and arc flash protection logic operations. This invention simplifies on-site maintenance processes through a dynamic adaptation mechanism, significantly reducing operation and maintenance costs. Simultaneously, the collaborative control system ensures high reliability of signal transmission, contributing to the intelligent and efficient operation of protection and control systems. Attached Figure Description

[0016] Figure 1 This is a flowchart of the method for coordinating IO virtualization and GOOSE / SV engine in protection and control according to the present invention; Figure 2 This is a system block diagram of the collaborative system of IO virtualization and GOOSE / SV engine in the protection and control of this invention; Figure 3 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] like Figure 1 The diagram shown is a flowchart of the method for coordinating IO virtualization and the GOOSE / SV engine in protection and control according to an embodiment of the present invention. Figure 1 The execution entity of the method shown can be a software and / or hardware device. The execution entity of this application can include, but is not limited to, at least one of the following: user equipment, network equipment, etc. User equipment can include, but is not limited to, computers, smartphones, personal digital assistants (PDAs), and the aforementioned electronic devices. Network equipment can include, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing consisting of a large number of computers or network servers. Cloud computing is a type of distributed computing, consisting of a super virtual computer composed of a group of loosely coupled computers. This embodiment does not limit this. Steps S1 to S4 are detailed as follows: S1. Based on SR-IOV technology, traverse the physical I / O of the protection and control device, extract the parameters of the physical I / O, abstract the physical I / O into dynamically allocable virtual I / O resource units, and construct a programmable virtual I / O resource pool. S2, embed a hardware-level GOOSE / SV engine in the switching chip layer between the IO virtual resource pool and the physical IO, and configure the communication interface, clock frequency and cache capacity of the GOOSE / SV engine to complete the connection and initialization of the GOOSE / SV engine with the hardware layer; S3, build an IO resource scheduling module, establish a communication link between the IO resource scheduling module and the IO virtual resource pool and the GOOSE / SV engine, formulate virtual resource allocation rules and GOOSE / SV signal transmission priority strategy, and form a collaborative control of the IO resource scheduling module, the IO virtual resource pool and the GOOSE / SV engine; S4, receive device access requests or physical IO upgrade instructions, match and map the virtual IO resource units and the physical IO through the IO resource scheduling module, and have the GOOSE / SV engine directly handle the protocol parsing, encoding, decoding and timed transmission and reception of GOOSE / SV signals to complete low-latency transmission and hardware adaptation of GOOSE / SV signals without modifying the underlying driver software.

[0019] Specifically, based on SR-IOV (Single Root I / O Virtualization) technology, a full traversal of the physical I / O interfaces of the protection and control device is performed. During the traversal, the core parameters of the physical I / O are precisely extracted, covering unique port identifiers, supported communication protocols, maximum data transmission bandwidth, and signal types. Based on these parameters, the physical I / O is abstracted into virtual I / O resource units with independent resource attributes. These virtual I / O resource units can be dynamically allocated without being constrained by physical hardware, breaking the strong binding relationship between traditional physical I / O and software drivers. Finally, all virtual I / O resource units are integrated to construct a programmable virtual I / O resource pool.

[0020] A hardware-level GOOSE / SV engine is embedded in the switching chip layer between the IO virtual resource pool and physical IO devices. Compared to the software processing mode that relies on the main control CPU, the hardware-level engine can avoid CPU resource consumption and bus transmission latency issues. Then, based on the interface specifications of the IO virtual resource pool and physical IO, key engine parameters are configured: the communication interface must match the upstream and downstream link protocols to ensure data transmission compatibility; the clock frequency must match the real-time transmission cycle of protection signals such as trip commands and fault sampling signals; and the buffer capacity must be partitioned according to signal priority, reserving independent space for high-urgency signals. After completing the electrical connection between the engine and the hardware layer, standard test signals are injected to verify link connectivity and basic processing functions, completing the initialization.

[0021] Furthermore, a bidirectional communication link is first established between the IO resource scheduling module and the IO virtual resource pool and the GOOSE / SV engine. On the one hand, the unit occupancy status, available bandwidth, and associated physical IO information of the IO virtual resource pool, as well as the signal processing status and buffer utilization of the GOOSE / SV engine, are collected in real time. On the other hand, control commands such as resource allocation and parameter adjustment can be issued to both. Secondly, virtual resource allocation rules and GOOSE / SV signal transmission priority strategies are formulated. The virtual resource allocation rules prioritize the resource needs of high real-time devices; the GOOSE / SV signal transmission priority strategy clarifies the priority processing rights of key signals such as trip commands and fault current sampling signals. After embedding the IO virtual resource pool and the GOOSE / SV engine into the IO resource scheduling module, a collaborative control system is formed, enabling dynamic adaptation of resource allocation and signal processing.

[0022] Finally, upon receiving device access requests, such as sensor or actuator access or physical I / O upgrade commands, the I / O resource scheduling module matches suitable virtual I / O resource units in the I / O virtual resource pool based on device parameters or upgraded physical I / O parameters, establishing a mapping relationship between them and the target physical I / O. Simultaneously, the GOOSE / SV engine directly performs protocol parsing, encoding, decoding, and timed transmission and reception of GOOSE / SV signals, bypassing the main control CPU bus interaction throughout, ensuring low-latency signal transmission. The entire process requires no modification to the underlying driver software, achieving dynamic hardware adaptation and reliable signal transmission, meeting the flexibility and real-time requirements of protection and control scenarios.

[0023] In practice, the construction process of the IO virtual resource pool is as follows: The device parameter acquisition tool is used to scan all the physical I / Os of the protection and control device, and the unique port identifier, supported communication protocol, maximum data transmission bandwidth and signal type of each physical I / O are recorded to form a physical I / O parameter list; According to the communication protocol, the physical I / O in the physical I / O parameter list are classified, and physical I / O with the same or compatible communication protocol are grouped together to ensure that the signal processing logic of the physical I / O within the same group is consistent. Based on SR-IOV technology, each group of physical I / O is abstracted, and several virtual I / O resource units with uniform specifications are generated for each group of physical I / O. A unique virtual identifier and independent memory address space are assigned to each virtual I / O resource unit, and the parameter mapping relationship between the virtual I / O resource unit and the corresponding physical I / O is clarified. Integrate all the virtual IO resource units, construct a resource pool management ledger and record the identifier, associated physical IO information, current occupancy status and available bandwidth of all the virtual IO resource units, and output a programmable IO virtual resource pool.

[0024] Understandably, a device parameter acquisition tool is used to perform a full-domain scan of all physical I / O interfaces of the protection and control device. This process requires accurately capturing the core attributes of each physical I / O, including unique port identifier, supported communication protocols, maximum data transmission bandwidth, and signal type. The signal type is divided into digital and analog quantities. These parameters are then systematically organized to form a structured list of physical I / O parameters.

[0025] Based on communication protocols as the core classification criterion, all physical I / Os in the physical I / O parameter list are categorized. Physical I / Os with completely consistent or compatible communication protocols are grouped together to ensure that the signal encoding rules, transmission timing, and processing logic of physical I / Os within the same group remain consistent, avoiding conflicts in subsequent virtual abstraction and signal interaction due to protocol differences.

[0026] Based on SR-IOV technology, hardware-level abstraction is implemented for each group of physical I / O. For each group of physical I / O, several standardized virtual I / O resource units are generated. Each virtual I / O resource unit is assigned a unique virtual identifier and an independent memory address space. At the same time, a parameter mapping relationship between virtual I / O resource units and corresponding physical I / O is established, and the inheritance rules of virtual I / O resource units for physical I / O attributes are clarified, thereby realizing the virtualization mapping of physical I / O functions.

[0027] Integrate all generated virtual I / O resource units to build a resource pool management ledger. The ledger must fully record the virtual identifier of each virtual I / O resource unit, key information of the associated physical I / O, current occupancy status, and available bandwidth, forming a resource management system that can be dynamically queried and scheduled. The final output is a programmable virtual I / O resource pool to support subsequent dynamic resource allocation and hardware adaptation.

[0028] The parameter configuration process for the virtual I / O resource unit is as follows: Analyze the signal transmission requirements of typical devices, namely the minimum data transmission bandwidth, signal response time, and protocol compatibility requirements of the typical devices; Based on the maximum transmission bandwidth of the physical I / O and the device requirements, the standard bandwidth and signal processing capability of a single virtual I / O resource unit are set so that a single virtual I / O resource unit meets the signal transmission requirements of at least one type of typical device. Based on the signal type of the physical I / O, configure signal conversion logic for the corresponding virtual I / O resource unit, configure level conversion adaptation module for the virtual I / O resource unit corresponding to digital physical I / O, and configure AD / DA conversion adaptation module for the virtual I / O resource unit corresponding to analog physical I / O. Perform functional tests on the configured virtual I / O resource unit to verify whether the virtual I / O resource unit can normally receive, process and forward the corresponding physical I / O signals.

[0029] For typical equipment, such as various sensors, actuators, and protection and control devices, we break down the signal transmission requirements to clarify the minimum data transmission bandwidth, signal response time, and protocol compatibility range required for the normal operation of various equipment, thus forming a benchmark for equipment requirements as the basis for configuring virtual unit parameters.

[0030] By combining the maximum transmission bandwidth limit of physical I / O with the device requirement benchmark, the standard bandwidth parameters of a single virtual I / O resource unit are determined; at the same time, the signal processing capabilities of the virtual I / O resource unit are defined, including indicators such as data frame parsing rate and signal forwarding latency, so that a single virtual I / O resource unit can at least meet the full-scenario signal transmission needs of a typical type of device and improve resource utilization.

[0031] Based on the signal type of the physical I / O, signal conversion logic is configured for the corresponding virtual I / O resource unit. For virtual I / O resource units mapped to digital physical I / O, a level conversion adapter module is integrated to achieve signal adaptation for different level standards; for virtual I / O resource units mapped to analog physical I / O, an AD / DA conversion adapter module is embedded to complete the accurate conversion between analog and digital signals, ensuring that the signal types of the virtual I / O resource unit and the physical I / O match.

[0032] Full-function testing is performed on the virtual IO resource units with complete parameter configuration. By injecting simulated physical IO signals into the virtual IO resource units, it is verified whether they can receive signals normally, process signals according to the configured logic, and accurately forward them to the target node. At the same time, the stability of the units is tested in multi-signal concurrent scenarios to ensure that there are no signal loss or out-of-order issues. Only after the verification is passed can they be included in the IO virtual resource pool.

[0033] The embedding process of the GOOSE / SV engine is as follows: Collect key characteristics of GOOSE / SV signals in protection and control scenarios, including signal frame structure, transmission period, priority level and fault tolerance requirements; Select a switching chip that supports hardware-level protocol processing in the switching chip layer between the IO virtual resource pool and the physical IO, integrate the GOOSE / SV engine into the switching chip, and configure the communication interface, clock frequency and buffer capacity of the GOOSE / SV engine according to the key characteristics of the GOOSE / SV signal. A virtual IO channel connecting the GOOSE / SV engine to the IO virtual resource pool, and a hardware interface connecting the GOOSE / SV engine to the physical IO.

[0034] In practical applications, based on the real-time and reliability requirements of protection and control scenarios, the key characteristics of GOOSE / SV signals are collected: the signal frame structure must clearly define the frame header identifier, data payload partition, and check field format; the transmission cycle must match the protection task type; the priority level is divided according to the degree of impact of the signal on system security, with emergency control signals having higher priority than ordinary monitoring signals; and the fault tolerance requirements must define the allowable packet loss rate and data error correction mechanism to ensure the integrity of signal transmission.

[0035] At the switching chip layer between the IO virtual resource pool and physical IO, switching chips with hardware-level protocol acceleration capabilities are selected. These chips must support parallel data processing to avoid resource consumption and latency issues caused by reliance on the main control CPU. The GOOSE / SV engine is integrated into the internal hardware logic unit of the switching chip, and engine parameters are configured based on the characteristics of the previously acquired signals: the communication interface must be compatible with the protocol type of the virtual IO channel and the hardware interface specifications of the physical IO to ensure data link compatibility; the clock frequency must meet the time accuracy requirements of the signal transmission cycle to ensure real-time processing; and the buffer capacity is partitioned and allocated according to signal priority, reserving independent buffer blocks for high-priority signals to avoid buffer contention when multiple signals are concurrent.

[0036] Establish a virtual I / O channel connection between the GOOSE / SV engine and the I / O virtual resource pool, employing a high-speed data interaction method based on memory mapping to reduce intermediate data transmission steps. Simultaneously, connect the engine to the physical I / O hardware interface, using differential signal transmission technology to suppress electromagnetic interference and ensure the link's signal-to-noise ratio. After connection, verify link connectivity to ensure the GOOSE / SV engine can bidirectionally receive and forward signal data between the virtual I / O channel and the physical I / O.

[0037] The process of building the IO resource scheduling module is as follows: The core functional modules of the IO resource scheduling module are designed, including a resource status monitoring module, a request parsing module, and an instruction generation module; Establish a communication link between the IO resource scheduling module and the IO virtual resource pool. The module obtains the occupancy status, available bandwidth, and associated physical IO information of the virtual IO resource unit in real time through the communication link, and sends resource allocation or release instructions to the IO virtual resource pool at the same time. Establish a communication link between the IO resource scheduling module and the GOOSE / SV engine. Obtain the signal processing status, buffer utilization rate and current signal type of the GOOSE / SV engine through the communication link. At the same time, send signal priority adjustment instructions and transmit / receive cycle modification instructions to the GOOSE / SV engine. The virtual resource allocation rules and the GOOSE / SV signal transmission priority strategy are formulated and embedded into the instruction generation module of the IO resource scheduling module.

[0038] First, based on the dynamic adaptation requirements of the protection and control system, the IO resource scheduling module is designed with three core functional modules: a resource status monitoring module, responsible for collecting the operation data of the IO virtual resource pool and the GOOSE / SV engine across the entire domain to form a real-time status view; a request parsing module, which performs protocol parsing and parameter extraction on device access requests and physical IO upgrade instructions, and outputs standardized requirement information; and an instruction generation module, as the core decision-making unit, which generates resource scheduling and engine control instructions based on status data and requirement information. The three modules work together through an internal data bus.

[0039] Then, a communication link is established between the IO resource scheduling module and the IO virtual resource pool. The IO resource scheduling module retrieves key status parameters of virtual IO resource units in real time through the communication link, including unit occupancy status, remaining available bandwidth, port identifier and protocol type of associated physical IO, forming a resource status ledger. Based on the demand analysis results, the IO resource scheduling module issues resource allocation instructions or resource release instructions to the IO virtual resource pool through the communication link to realize dynamic scheduling of virtual resources.

[0040] The IO resource scheduling module obtains real-time operating data of the GOOSE / SV engine through the communication link, covering signal processing load, cache partition utilization, and the type and priority of currently processed signals. At the same time, the IO resource scheduling module can issue dynamic control commands to the GOOSE / SV engine, including signal priority adjustment commands and transmit / receive cycle modification commands, to ensure that the engine's processing capacity is adapted to the signal requirements.

[0041] Furthermore, based on the requirements of the protection scenario, two core strategies were formulated: a virtual resource allocation rule that prioritizes allocating low-load virtual units to high real-time devices to ensure rapid response times for critical equipment access; and a GOOSE / SV signal transmission priority strategy that clearly defines the priority order of tripping commands over fault sampling signals, which in turn are prioritized over ordinary monitoring signals. These two strategies are embedded into the logic unit of the command generation module, ensuring that every command generated by the module conforms to the strategy requirements and guarantees the consistency and rationality of scheduling decisions.

[0042] The collaborative control process of the IO resource scheduling module, the IO virtual resource pool, and the GOOSE / SV engine is as follows: Define the triggering conditions for the collaborative control process. When the collaborative control process is triggered, the IO resource scheduling module first collects the real-time status of the IO virtual resource pool and the GOOSE / SV engine, and then generates resource allocation instructions and engine adjustment instructions, which are sent to the IO virtual resource pool and the GOOSE / SV engine respectively and wait for feedback. A feedback verification mechanism is configured. The IO resource scheduling module receives the resource allocation result feedback from the IO virtual resource pool and the instruction execution result feedback from the GOOSE / SV engine. If the feedback result shows that the instruction execution failed, a new instruction is generated and the above feedback process is repeated.

[0043] First, define the triggering conditions for the collaborative control process, which cover business demand triggering and system status triggering. Business demand triggering includes device access requests and physical IO hardware upgrade instructions. System status triggering includes IO virtual resource pool occupancy rate greater than or equal to 80%, GOOSE / SV engine cache utilization rate greater than or equal to 90%, or signal processing latency exceeding the threshold. The collaborative process is started when any of the conditions are met.

[0044] After the collaborative control process is triggered, the IO resource scheduling module synchronously collects the real-time operating status of the IO virtual resource pool and the GOOSE / SV engine through a preset communication link: for the IO virtual resource pool, it obtains the occupancy status of virtual IO resource units, remaining available bandwidth, and associated physical IO parameters; for the GOOSE / SV engine, it collects the signal processing load, the utilization rate of each priority buffer, and the current signal type being processed. Based on the status data and trigger requirements, the instruction generation module of the IO resource scheduling module generates resource allocation instructions and engine adjustment instructions respectively, and sends them to the IO virtual resource pool and the GOOSE / SV engine through the corresponding communication links.

[0045] A two-way feedback verification mechanism is established, where the IO resource scheduling module receives two types of feedback data in real time: resource allocation results returned by the IO virtual resource pool and instruction execution results returned by the GOOSE / SV engine. If the feedback result indicates successful execution, the collaborative process terminates; if the feedback fails, the IO resource scheduling module re-analyzes the discrepancies between the status data and the requirements. For example, if resource allocation fails, it re-selects low-load virtual IO resource units within the IO virtual resource pool or temporarily generates new virtual IO resource units; if engine adjustment fails, it adjusts the cache partition or clock frequency parameters, then generates new resource allocation and engine adjustment instructions, repeating the issuance and feedback verification process until the instructions are successfully executed, forming a dynamic closed loop of collaborative control to ensure the reliability of system adaptation and signal processing.

[0046] The dynamic adaptation process for the device access request is as follows: Receive the device access request, which includes device type, communication protocol, data transmission requirements, and target physical I / O identifier; The scheduling module parses the device access request and, based on the communication protocol and the target physical IO identifier, selects idle virtual IO resource units in the IO virtual resource pool that are associated with the target physical IO and support the communication protocol. The IO resource scheduling module sends resource allocation instructions to the IO virtual resource pool, establishes a mapping relationship between the selected virtual IO resource units and the target physical IO, and sends signal processing instructions to the GOOSE / SV engine. The device sends a test signal through the mapping channel between the virtual IO resource unit and the target physical IO. The GOOSE / SV engine receives and processes the test signal and then feeds back the processing result. If the processing result is normal, the device access adaptation is completed. If the processing result is abnormal, the virtual IO resource unit is re-selected and the adaptation process is repeated.

[0047] First, the system receives access request frames from receiving devices. These frames carry device metadata, including device type, supported communication protocols, data transmission requirements, and target physical I / O identifiers, providing a requirement benchmark for adaptation.

[0048] The IO resource scheduling module performs protocol parsing on the request frame, extracts the core requirement parameters, and then searches for matching units in the IO virtual resource pool. Specifically, it selects virtual IO resource units that have a preset mapping relationship with the target physical IO, support the request protocol, and are currently in an idle state, ensuring that the capabilities of the virtual IO resource units match the device requirements.

[0049] The IO resource scheduling module issues resource allocation instructions to the IO virtual resource pool. The instructions specify the binding relationship between the selected virtual IO resource units and the target physical IO, thus completing the construction of the mapping channel between the two. At the same time, it issues signal processing instructions to the GOOSE / SV engine. The instructions include the signal frame structure, transmission priority and transmission and reception period of the device, and configure the engine processing logic.

[0050] The device sends a test signal through the mapping channel between the virtual I / O resource unit and the target physical I / O. After receiving the signal, the GOOSE / SV engine performs protocol parsing, encoding, and decoding, and then returns the processing result. If the result is normal, the adaptation process terminates; if an error occurs, the virtual unit is re-selected and the above steps are repeated until the adaptation is successful.

[0051] The dynamic adaptation process of the physical I / O upgrade command is as follows: Collect the parameters of the upgraded physical I / O and compare them with the parameters of the physical I / O to determine the parameter differences; The IO resource scheduling module selects virtual IO resource units that support the parameters of the new physical IO from the IO virtual resource pool according to the parameters of the new physical IO. If there is no virtual IO resource unit that supports the parameters of the new physical IO, the new physical IO is abstracted based on SR-IOV technology to generate a new virtual IO resource unit. The IO resource scheduling module updates the mapping table between the virtual IO resource unit and the physical IO, deletes the association between the physical IO and the virtual IO resource unit, and establishes a mapping relationship between the new physical IO and the selected virtual IO resource unit or the new virtual IO resource unit. Send a test GOOSE / SV signal to the new physical IO to verify the validity of the mapping between the selected virtual IO resource unit or the new virtual IO resource unit and the new physical IO, as well as the correctness of the signal processing of the GOOSE / SV engine, so that the upgraded new physical IO works normally without modifying the underlying driver software.

[0052] Collect the core parameters of the new physical I / O after the upgrade, including port identifier, supported protocols, maximum bandwidth, and signal type. Compare these parameters with those of the old physical I / O before the upgrade to identify the differences, such as the protocol being upgraded from RS485 to Ethernet and the bandwidth being increased from 100Mbps to 1Gbps, to provide a basis for adaptation adjustments.

[0053] The IO resource scheduling module selects virtual IO resource units that support the new physical IO parameters from the IO virtual resource pool. If there are no suitable virtual IO resource units, the module performs hardware abstraction on the new physical IO based on SR-IOV technology to generate new virtual IO resource units with matching specifications and allocates a unique identifier and independent memory space.

[0054] The virtual I / O resource unit updates the mapping table between virtual I / O resource units and physical I / O, deletes the association records between old physical I / O and the original virtual I / O resource units, and establishes the mapping relationship between new physical I / O and the selected virtual I / O resource units or new virtual I / O resource units to ensure that the data link is updated.

[0055] Inject standard GOOSE / SV test signals into the new physical I / O to verify the mapping connectivity between the selected virtual I / O resource units or new virtual I / O resource units and the new physical I / O. Simultaneously, check the correctness of the GOOSE / SV engine's signal parsing and processing. Once verification is successful, the new physical I / O can function normally without requiring any modifications to the underlying driver software, achieving seamless hardware upgrade adaptation.

[0056] like Figure 2 The diagram shown is a system block diagram of the IO virtualization and GOOSE / SV engine collaborative system in protection and control provided by an embodiment of the present invention. The system includes: The resource pool construction module is used to traverse the physical I / O of the protection and control device based on SR-IOV technology, extract the parameters of the physical I / O, abstract the physical I / O into dynamically allocable virtual I / O resource units, and construct a programmable virtual I / O resource pool. An engine embedding module is used to embed a hardware-level GOOSE / SV engine into the switching chip layer between the IO virtual resource pool and the physical IO, and to configure the communication interface, clock frequency and cache capacity of the GOOSE / SV engine, and complete the connection and initialization of the GOOSE / SV engine with the hardware layer. The collaborative control module is used to build the IO resource scheduling module, establish communication links between the IO resource scheduling module and the IO virtual resource pool and the GOOSE / SV engine, formulate virtual resource allocation rules and GOOSE / SV signal transmission priority strategies, and form collaborative control of the IO resource scheduling module, the IO virtual resource pool and the GOOSE / SV engine. The signal processing module is used to receive device access requests or physical IO upgrade instructions. It matches and maps the virtual IO resource units with the physical IO through the IO resource scheduling module. The GOOSE / SV engine directly processes the protocol parsing, encoding, decoding and timed transmission and reception of GOOSE / SV signals to complete the low-latency transmission and hardware adaptation of GOOSE / SV signals without modifying the underlying driver software.

[0057] Figure 2 The apparatus of the illustrated embodiment can be used to perform corresponding actions. Figure 1 The steps in the method embodiments shown are implemented in a similar manner and have similar technical effects, and will not be repeated here.

[0058] An electronic device includes a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor performs the steps of the protection and control IO virtualization and GOOSE / SV engine collaborative method as described in any of the above claims.

[0059] like Figure 3 The diagram shown is a hardware structure schematic of an electronic device according to an embodiment of the present invention. The electronic device 30 includes: a processor 31, a memory 32, and a computer program; wherein... The memory 32 is used to store the computer program, and the memory may also be flash memory. The computer program is, for example, an application program or functional module that implements the above method.

[0060] Processor 31 is configured to execute the computer program stored in the memory to implement the various steps performed by the device in the above method. For details, please refer to the relevant descriptions in the preceding method embodiments.

[0061] Alternatively, the memory 32 can be either standalone or integrated with the processor 31.

[0062] When the memory 32 is a device independent of the processor 31, the device may further include: Bus 33 is used to connect the memory 32 and the processor 31.

[0063] A readable storage medium storing a computer program, which, when executed by a processor, is used to implement the steps of the protection and control IO virtualization and GOOSE / SV engine collaborative method as described in any of the above claims.

[0064] The readable storage medium can be a computer storage medium or a communication medium. A communication medium includes any medium that facilitates the transfer of computer programs from one location to another. A computer storage medium can be any available medium accessible to a general-purpose or special-purpose computer. For example, a readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application-Specific Integrated Circuit (ASIC). Alternatively, the ASIC can be located in a user equipment. Of course, the processor and the readable storage medium can also exist as discrete components in a communication device. The readable storage medium can be a read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0065] The present invention also provides a program product including executable instructions stored in a readable storage medium. At least one processor of the device can read the executable instructions from the readable storage medium, and the at least one processor executes the executable instructions to cause the device to implement the methods provided in the various embodiments described above.

[0066] In the embodiments of the above-described device, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.

[0067] Through the above embodiments, this invention, through a collaborative method of IO virtualization and GOOSE / SV engine in protection and control, traverses the physical IO of the protection and control device based on SR-IOV technology, extracts the parameters of the physical IO, abstracts the physical IO into dynamically allocable virtual IO resource units, and constructs a programmable IO virtual resource pool; embeds a hardware-level GOOSE / SV engine at the switching chip layer between the IO virtual resource pool and the physical IO, and configures the communication interface, clock frequency, and cache capacity of the GOOSE / SV engine to complete the connection and initialization between the GOOSE / SV engine and the hardware layer; builds an IO resource scheduling module and establishes communication between the IO resource scheduling module and the IO virtual resource pool and the GOOSE / SV engine. The link establishes virtual resource allocation rules and GOOSE / SV signal transmission priority strategies, forming a collaborative control mechanism among the IO resource scheduling module, IO virtual resource pool, and GOOSE / SV engine. It receives device access requests or physical IO upgrade instructions, matches and maps virtual IO resource units to physical IO through the IO resource scheduling module, and the GOOSE / SV engine directly handles protocol parsing, encoding, decoding, and timed transmission and reception of GOOSE / SV signals. This achieves low-latency transmission and hardware adaptation of GOOSE / SV signals without modifying the underlying driver software, enabling dynamic adaptation of IO virtualization, reducing the processing latency of the GOOSE / SV engine, lowering maintenance costs, and meeting the low-latency and high-reliability requirements of protection and control.

[0068] This invention utilizes a programmable I / O virtual resource pool built on SR-IOV technology, breaking the dependency of "software modification for hardware upgrades." Hardware upgrades do not require modification of the underlying driver, significantly improving I / O function configuration efficiency and adapting to various device types and operating condition switching requirements. The hardware-level GOOSE / SV engine of this invention is embedded in the switching chip layer, directly carrying out protocol parsing, encoding, decoding, and timed transmission and reception functions, shortening the processing latency of the GOOSE / SV engine and fully meeting the low latency and high reliability requirements of protection and control systems. The GOOSE / SV engine of this invention offloads the CPU's protocol processing load, freeing up main control CPU resources to focus on core tasks such as power quality analysis and arc flash protection logic operations. This invention simplifies on-site maintenance processes through a dynamic adaptation mechanism, significantly reducing operation and maintenance costs. Simultaneously, the collaborative control system ensures high reliability of signal transmission, contributing to the intelligent and efficient operation of protection and control systems.

[0069] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for coordinating IO virtualization and GOOSE / SV engine in protection measurement and control, characterized in that, The method includes: Based on SR-IOV technology, the physical I / O of the protection and control device is traversed, the parameters of the physical I / O are extracted, the physical I / O is abstracted into a dynamically allocable virtual I / O resource unit, and a programmable virtual I / O resource pool is constructed. A hardware-level GOOSE / SV engine is embedded in the switching chip layer between the IO virtual resource pool and the physical IO, and the communication interface, clock frequency and cache capacity of the GOOSE / SV engine are configured to complete the connection and initialization of the GOOSE / SV engine with the hardware layer. Build an IO resource scheduling module, establish communication links between the IO resource scheduling module and the IO virtual resource pool and the GOOSE / SV engine, formulate virtual resource allocation rules and GOOSE / SV signal transmission priority strategies, and form a collaborative control of the IO resource scheduling module, the IO virtual resource pool and the GOOSE / SV engine; Upon receiving a device access request or physical IO upgrade instruction, the virtual IO resource unit is matched and mapped to the physical IO through the IO resource scheduling module. The GOOSE / SV engine directly processes the protocol parsing, encoding, decoding, and timed transmission and reception of GOOSE / SV signals, completing low-latency transmission and hardware adaptation of GOOSE / SV signals without modifying the underlying driver software.

2. The method for coordinating IO virtualization and GOOSE / SV engine in protection and control according to claim 1, characterized in that, The construction process of the IO virtual resource pool is as follows: The device parameter acquisition tool is used to scan all the physical I / Os of the protection and control device, and the unique port identifier, supported communication protocol, maximum data transmission bandwidth and signal type of each physical I / O are recorded to form a physical I / O parameter list; According to the communication protocol, the physical I / O in the physical I / O parameter list are classified, and physical I / O with the same or compatible communication protocol are grouped together to ensure that the signal processing logic of the physical I / O within the same group is consistent. Based on SR-IOV technology, each group of physical I / O is abstracted, and several virtual I / O resource units with uniform specifications are generated for each group of physical I / O. A unique virtual identifier and independent memory address space are assigned to each virtual I / O resource unit, and the parameter mapping relationship between the virtual I / O resource unit and the corresponding physical I / O is clarified. Integrate all the virtual IO resource units, construct a resource pool management ledger and record the identifier, associated physical IO information, current occupancy status and available bandwidth of all the virtual IO resource units, and output a programmable IO virtual resource pool.

3. The method for coordinating IO virtualization and GOOSE / SV engine in protection and control according to claim 1, characterized in that, The parameter configuration process for the virtual I / O resource unit is as follows: Analyze the signal transmission requirements of typical devices, namely the minimum data transmission bandwidth, signal response time, and protocol compatibility requirements of the typical devices; Based on the maximum transmission bandwidth of the physical I / O and the device requirements, the standard bandwidth and signal processing capability of a single virtual I / O resource unit are set so that a single virtual I / O resource unit meets the signal transmission requirements of at least one type of typical device. Based on the signal type of the physical I / O, configure signal conversion logic for the corresponding virtual I / O resource unit, configure level conversion adaptation module for the virtual I / O resource unit corresponding to digital physical I / O, and configure AD / DA conversion adaptation module for the virtual I / O resource unit corresponding to analog physical I / O. Perform functional tests on the configured virtual I / O resource unit to verify whether the virtual I / O resource unit can normally receive, process and forward the corresponding physical I / O signals.

4. The method for coordinating IO virtualization and GOOSE / SV engine in protection and control according to claim 1, characterized in that, The embedding process of the GOOSE / SV engine is as follows: Collect key characteristics of GOOSE / SV signals in protection and control scenarios, including signal frame structure, transmission period, priority level and fault tolerance requirements; Select a switching chip that supports hardware-level protocol processing in the switching chip layer between the IO virtual resource pool and the physical IO, integrate the GOOSE / SV engine into the switching chip, and configure the communication interface, clock frequency and buffer capacity of the GOOSE / SV engine according to the key characteristics of the GOOSE / SV signal. A virtual IO channel connecting the GOOSE / SV engine to the IO virtual resource pool, and a hardware interface connecting the GOOSE / SV engine to the physical IO.

5. The method for coordinating IO virtualization and GOOSE / SV engine in protection and control according to claim 1, characterized in that, The process of building the IO resource scheduling module is as follows: The core functional modules of the IO resource scheduling module are designed, including a resource status monitoring module, a request parsing module, and an instruction generation module; Establish a communication link between the IO resource scheduling module and the IO virtual resource pool. The module obtains the occupancy status, available bandwidth, and associated physical IO information of the virtual IO resource unit in real time through the communication link, and sends resource allocation or release instructions to the IO virtual resource pool at the same time. Establish a communication link between the IO resource scheduling module and the GOOSE / SV engine. Obtain the signal processing status, buffer utilization rate and current signal type of the GOOSE / SV engine through the communication link. At the same time, send signal priority adjustment instructions and transmit / receive cycle modification instructions to the GOOSE / SV engine. The virtual resource allocation rules and the GOOSE / SV signal transmission priority strategy are formulated and embedded into the instruction generation module of the IO resource scheduling module.

6. The method for coordinating IO virtualization and GOOSE / SV engine in protection and control according to claim 1, characterized in that, The collaborative control process of the IO resource scheduling module, the IO virtual resource pool, and the GOOSE / SV engine is as follows: Define the triggering conditions for the collaborative control process. When the collaborative control process is triggered, the IO resource scheduling module first collects the real-time status of the IO virtual resource pool and the GOOSE / SV engine, and then generates resource allocation instructions and engine adjustment instructions, which are sent to the IO virtual resource pool and the GOOSE / SV engine respectively and wait for feedback. A feedback verification mechanism is configured. The IO resource scheduling module receives the resource allocation result feedback from the IO virtual resource pool and the instruction execution result feedback from the GOOSE / SV engine. If the feedback result shows that the instruction execution failed, a new instruction is generated and the above feedback process is repeated.

7. The method for coordinating IO virtualization and GOOSE / SV engine in protection and control according to claim 1, characterized in that, The dynamic adaptation process for the device access request is as follows: Receive the device access request, which includes device type, communication protocol, data transmission requirements, and target physical I / O identifier; The scheduling module parses the device access request and, based on the communication protocol and the target physical IO identifier, selects idle virtual IO resource units in the IO virtual resource pool that are associated with the target physical IO and support the communication protocol. The IO resource scheduling module sends resource allocation instructions to the IO virtual resource pool, establishes a mapping relationship between the selected virtual IO resource units and the target physical IO, and sends signal processing instructions to the GOOSE / SV engine. The device sends a test signal through the mapping channel between the virtual IO resource unit and the target physical IO. The GOOSE / SV engine receives and processes the test signal and then feeds back the processing result. If the processing result is normal, the device access adaptation is completed. If the processing result is abnormal, the virtual IO resource unit is re-selected and the adaptation process is repeated.

8. The method for coordinating IO virtualization and GOOSE / SV engine in protection and control according to claim 1, characterized in that, The dynamic adaptation process of the physical I / O upgrade command is as follows: Collect the parameters of the upgraded physical I / O and compare them with the parameters of the physical I / O to determine the parameter differences; The IO resource scheduling module selects virtual IO resource units that support the parameters of the new physical IO from the IO virtual resource pool according to the parameters of the new physical IO. If there is no virtual IO resource unit that supports the parameters of the new physical IO, the new physical IO is abstracted based on SR-IOV technology to generate a new virtual IO resource unit. The IO resource scheduling module updates the mapping table between the virtual IO resource unit and the physical IO, deletes the association between the physical IO and the virtual IO resource unit, and establishes a mapping relationship between the new physical IO and the selected virtual IO resource unit or the new virtual IO resource unit. Send a test GOOSE / SV signal to the new physical IO to verify the validity of the mapping between the selected virtual IO resource unit or the new virtual IO resource unit and the new physical IO, as well as the correctness of the signal processing of the GOOSE / SV engine, so that the upgraded new physical IO works normally without modifying the underlying driver software.

9. A collaborative system for IO virtualization and GOOSE / SV engine in protection and control, applied to the collaborative method for IO virtualization and GOOSE / SV engine in protection and control as described in any one of claims 1-8, characterized in that, The system includes: The resource pool construction module is used to traverse the physical I / O of the protection and control device based on SR-IOV technology, extract the parameters of the physical I / O, abstract the physical I / O into dynamically allocable virtual I / O resource units, and construct a programmable virtual I / O resource pool. An engine embedding module is used to embed a hardware-level GOOSE / SV engine into the switching chip layer between the IO virtual resource pool and the physical IO, and to configure the communication interface, clock frequency and cache capacity of the GOOSE / SV engine, and complete the connection and initialization of the GOOSE / SV engine with the hardware layer. The collaborative control module is used to build the IO resource scheduling module, establish communication links between the IO resource scheduling module and the IO virtual resource pool and the GOOSE / SV engine, formulate virtual resource allocation rules and GOOSE / SV signal transmission priority strategies, and form collaborative control of the IO resource scheduling module, the IO virtual resource pool and the GOOSE / SV engine. The signal processing module is used to receive device access requests or physical IO upgrade instructions. It matches and maps the virtual IO resource units with the physical IO through the IO resource scheduling module. The GOOSE / SV engine directly processes the protocol parsing, encoding, decoding and timed transmission and reception of GOOSE / SV signals to complete the low-latency transmission and hardware adaptation of GOOSE / SV signals without modifying the underlying driver software.

Images