A method and system for flexibly configuring the functions of the acquisition and execution unit

By separating the system management layer and functional module layer of the acquisition and execution unit, and adopting the MAT table and time slice mechanism, flexible configuration and independent operation of modules are achieved, solving the maintenance inconvenience caused by module coupling in the prior art, and improving the reliability and maintainability of the device.

CN117725043BActive Publication Date: 2026-11-10BEIJING SIFANG JIBAO ENG TECH +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311586774.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-11-24
Publication Date
2026-11-10
Estimated Expiration
2043-11-24

AI Technical Summary

Technical Problem

In the existing technology, the functional configuration of the acquisition and execution unit requires the writing of multiple different programs, which leads to inconvenience in maintenance. Furthermore, the modules are coupled with each other, making it difficult to flexibly combine them in the field, thus affecting the reliability and maintainability of the device.

Method used

The system adopts a design that separates the system management layer and the functional module layer. The module structure and time slice are defined through the MAT table, which enables flexible configuration and independent operation of the modules. The modules interact with each other through a real-time database. The MMU and ECC are used to protect the MAT table to ensure system stability.

Benefits of technology

It improves the reliability and maintainability of modules, simplifies program development and verification, enhances the flexibility and security of the system, reduces maintenance workload, and ensures stable operation of the system under high load conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117725043B_ABST
    Figure CN117725043B_ABST
Patent Text Reader

Abstract

This invention discloses a method and system for flexibly configuring the functions of a data acquisition and execution unit. The method includes: summarizing the functions of the data acquisition and execution unit, constructing the data acquisition and execution unit structure, including a system management layer and a functional module layer. The system management layer is used for database maintenance and executes the tasks of each functional module according to a configured linked list. The functional module layer includes a sampling module, a logic module, and an output module. Based on the field requirements, the functional module structure required by the data acquisition and execution unit is defined according to the MAT table, obtaining the corresponding MAT table and backing it up and setting checksums. The required functional modules are configured according to the actual engineering situation, determining the time slice, priority, and configuration linked list required by the system management layer for each functional module. The configuration linked list is a unidirectional linked list based on the MAT table. This invention facilitates the development, verification, and maintenance of data acquisition and execution unit functions, improving the reliability and execution efficiency of the data acquisition and execution unit.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention belongs to the field of relay protection technology and relates to a method and system for flexibly configuring the functions of the data acquisition and execution unit. Background Technology

[0002] With the continuous development and advancement of smart grid technology, the data acquisition and execution unit (TAU), as a process-level device in a digital substation conforming to the IEC 61850 standard, collects AC voltage and current signals from the power grid and sends them to the protection device via the SV message of IEC 61850-9-2. The protection device receives the real-time voltage and current signals from the TAU to determine whether a fault has occurred in the system. If a fault occurs (such as a short circuit to ground), the protection device sends a GOOSE message to the TAU via IEC 61850-8-1. After parsing the GOOSE message, the TAU controls the opening and closing operations of the corresponding circuit breakers and disconnectors. As the information collector and result executor of the smart grid, the TAU plays a particularly important role.

[0003] For specific data acquisition and execution units on-site, users will propose various functional requirements based on the on-site environment. These requirements can be mainly categorized into three types of functional devices:

[0004] 1. Merging unit, comprising two types of devices: bus merging unit and bay merging unit, with the following functions:

[0005] The device acquires AC voltage and current signals of the current bay through internal AD acquisition; receives SV messages from the bus merging unit to obtain the bus voltage signal; receives FT3 messages from the electronic instrument transformer to obtain the voltage and current signals of the current bay; resamples the voltage and current signals to the same time segment and sends the sampled values ​​through SV messages; receives GOOSE messages from the intelligent terminal to obtain the positions of circuit breakers and disconnectors; performs voltage paralleling for bus merging units based on the positions of circuit breakers and disconnectors; performs voltage switching for bay merging units based on the positions of circuit breakers and disconnectors; performs time synchronization management; and sends its own operating status to other devices through GOOSE messages.

[0006] 2. Smart terminals, with the following functions:

[0007] It collects the position signals of circuit breakers and disconnectors; receives GOOSE messages to control the opening and closing of circuit breakers and disconnectors; and sends its own operating status to other devices via GOOSE messages.

[0008] 3. Smart Integration Device, namely, a combination unit + smart terminal:

[0009] It combines the functions of a merging unit and a smart terminal. Users can combine them according to the actual use of the device. The time intervals required for each functional module are also different: AD acquisition and SV message transmission require 250us, with jitter not exceeding 10us; GOOSE message heartbeat is generally sent once every 5 seconds, and if there is a change in GOOSE status, it is required to be sent within 1ms; the acquisition resolution for circuit breakers and disconnectors requires 1ms.

[0010] Because the data acquisition and execution unit has very strict requirements for time stamp accuracy, such as for SV messages, the time synchronization accuracy requirement is 1µs, SV transmission jitter is less than 10µs, and the timekeeping accuracy is less than 4µs / 10 minutes. Since the operating system's time slice is at the millisecond level, the data acquisition and execution unit generally adopts an operating system-less approach. Current technology generally categorizes these devices into three types based on their field functions: merging units, intelligent terminals, and intelligent merging devices. This requires writing three different programs, each with many common modules, some of which need to work together, making maintenance quite inconvenient. Even when programmed modularly, each module executes at a fixed location, preventing flexible combination in the field. Summary of the Invention

[0011] To address the shortcomings of existing technologies, this invention provides a method and system for flexibly configuring the functions of the acquisition and execution unit.

[0012] The present invention adopts the following technical solution.

[0013] A method for flexibly configuring the functions of a data acquisition execution unit includes the following steps:

[0014] Step 1: Summarize the functions of the data acquisition and execution unit and construct the structure of the data acquisition and execution unit, including the system management layer and the functional module layer. The system management layer is used to maintain the database and execute the tasks of each functional module in the functional module layer according to the configured linked list. The functional modules in the functional module layer include the sampling module, the logic module, and the output module.

[0015] Step 2: Based on the on-site requirements, according to the functional module structure actually required by the data acquisition and execution unit as defined in the MAT table, obtain the corresponding MAT table and back it up and set the checksum.

[0016] Step 3: Configure the required functional modules according to the actual project situation, determine the time slice, priority, and configuration list required by the system management layer for the functional modules, wherein the configuration list is a singly linked list based on the MAT table.

[0017] Preferably, the system management layer includes a system configuration database and a real-time database;

[0018] The system configuration database is generated based on the hardware configuration file CFG of the acquisition and execution unit and the CCD exported from the field SCD file. The system configuration database contains the following information: the plug-in models and quantities that the device should have, the slot number of each plug-in inside the device; the correspondence between each input signal in the field and the input terminals of each plug-in; the correspondence between each output signal in the field and the output terminals of the device; the correspondence between the device input terminals and the GOOSE publish or SV publish virtual terminals; the correspondence between the GOOSE subscription virtual terminals and the device output terminals; and the logical relationship between the device input terminals and the device output terminals.

[0019] The real-time database includes data collected on-site and processed into mature data by the sampling module.

[0020] Preferably, the sampling module is used to collect on-site information and process it into mature data that can be directly used by other modules before filling it into the real-time database;

[0021] The logic module is used to retrieve real-time data from the real-time database, perform logical operations, and then fill the result of the logical operations into the real-time database.

[0022] The output module is used to obtain output information from the real-time database and to control circuit breakers, disconnectors, and interlocking nodes, or to publish SV messages for AC voltage and current.

[0023] Preferably, each functional module in the functional module layer operates independently and interacts with the real-time database. Each functional module uses standard interface functions to read or write to the real-time database of the system management layer.

[0024] Preferably, in step 2, the contents of the MAT table include: usage flag, functional module name, version, creation time, task type, task number, module priority number, and program allocation start address.

[0025] Preferably, in step 2, three copies of the MAT table corresponding to each functional module structure are backed up, and each copy of the MAT table is equipped with a CRC check code to verify whether the MAT table is correct.

[0026] The MAT table uses both MMU and ECC for write protection and performs CRC checks periodically. When a CRC check error is found in the MAT table in use, a two-out-of-three principle is adopted to select the correct MAT table from the three MAT tables, and the MAT table with the CRC error is automatically repaired.

[0027] Preferably, in step 3, time slices are divided according to the actual engineering situation, and the specific time slices to which the functional modules should be defined are determined, so as to realize scheduling in the time slice manner during bare-metal operation; the priority of the functional modules in their corresponding time slices is set, and the tasks to be executed in each time slice and the functional module programs are combined with the MAT table to form a singly linked list according to their addresses.

[0028] Preferably, the tasks are divided into two categories: interrupt tasks and polling tasks. Interrupt tasks can preempt polling tasks, while polling tasks cannot preempt each other. They can only be scheduled to run in the current task segment after the currently executing task has finished.

[0029] Preferably, the task scheduling process is as follows:

[0030] If the execution conditions of this task segment are met, the starting address of the first task module program is retrieved from the linked list of this task segment, and the program of the first module is executed. After the program of the first module is executed, the program returns to the task scheduler, retrieves the address of the next module from the linked list, and executes the program of the next module, until the last priority module is executed. Then the task segment is completed and returns to the system management program to execute the next task segment.

[0031] A system for flexibly configuring the functions of the acquisition and execution unit includes:

[0032] The system management layer and functional module layer are building units used to summarize the functions of the acquisition and execution unit and construct the structure of the acquisition and execution unit. The system management layer is used for allocating program addresses for each module, maintaining the database, and executing the tasks of each functional module according to the configured linked list. The functional module layer includes sampling modules, logic modules, and output modules.

[0033] The functional module structure definition unit is used to define the actual functional module structure required by the acquisition and execution unit according to the field requirements and the MAT table definition, to obtain the corresponding MAT table and to back up and set the check code of the MAT table.

[0034] The functional module configuration unit is used to configure the required functional modules according to the actual engineering situation, determine the time slice, priority, and configuration list required by the system management layer of the functional modules, wherein the configuration list is a singly linked list based on the MAT table.

[0035] Preferably, the system management layer is also used to monitor the operating status of each functional module, specifically monitoring whether each functional module occupies CPU load for a long time; whether it has not been running for a long time; and whether the memory used exceeds the predetermined range. It is also used to monitor the operating status of the entire system, including: whether the system is in a high-load operating state; once the maximum load rate is found to be greater than the load warning value, an alarm is issued and the CPU load occupancy rate of each functional module is provided; and to monitor read and write operations to the real-time database, issuing an alarm and writing the functional module number, time, and alarm information of the operation to a log file in case of out-of-bounds access, illegal operation address, illegal permissions, or illegal operation method, for analysis of the cause of the anomaly.

[0036] The beneficial effects of this invention are compared with those of the prior art:

[0037] 1. This invention separates the system management layer and the functional module layer, which facilitates device development, verification, and maintenance. Because the data acquisition and execution units have very strict time requirements and run on a bare system using a single program, three different programs are used for the merging unit, intelligent terminal, and intelligent device. Existing technologies contain both system scheduling and functional modules within the same program, lacking a distinction between the system management layer and the functional module layer. This invention separates the system management layer from the functional module layer, which facilitates program maintenance. Modifying a single functional module does not require upgrading and verifying the entire program; only the modified module needs to be upgraded and verified, significantly reducing the verification workload. Simultaneously, the modules are completely decoupled, with no inter-module communication. Their interaction is achieved through data exchange via a real-time database. This allows configuration software to determine whether a module needs to run based on actual application requirements. Each module can be written according to specific needs, improving module security. Modules have single functions, simplifying functionality, making them easy to write and test, and allowing them to be used as common modules. This allows for continuous enrichment of the configured functional modules, improving their reliability, maintainability, and readability, thus enhancing the reliability and maintainability of the device.

[0038] 2. The functional modules of this invention are highly independent and completely decoupled from each other. Each module has a single function, which is conducive to the writing, verification and maintenance of the modules and improves the reliability of the device.

[0039] 3. This invention can calculate the load rate for each task type. When the maximum load rate exceeds the load warning value, the system management layer will issue an alarm message. This function can help ensure the stable operation of the system.

[0040] 4. This invention defines a functional module structure based on the MAT table, and has the following characteristics:

[0041] Each module has its own version and creation time, which can be managed and upgraded individually.

[0042] Each module's MAT table contains the task type and execution order, as well as the address where the module is stored. Based on these three pieces of information, the system management layer can generate an execution linked list for each task type.

[0043] Upgrading and maintenance are convenient. To replace a module, simply modify the MAT table, delete the "use flag" of the old version, and add the module to the MAT table.

[0044] 5. MAT Table Protection Measures for Functional Modules: Since the MAT table is crucial to this invention, three identical backups of the MAT table are stored. Write protection is implemented using the CPU's built-in MMU and ECC functions, and CRC checks are performed periodically. If a CRC error is detected in any MAT table, a two-out-of-three principle is adopted to select one MAT table as the running MAT table, while automatically repairing erroneous MAT tables. This significantly improves system reliability.

[0045] 6. Program execution order: In general program scheduling, the program is traversed and executed according to the pre-programmed pattern and the function enable / disable flags. The system management program MAT table of this invention generates an execution linked list. Each task type is executed in order according to its own linked list, which greatly improves the flexibility and efficiency of execution. Attached Figure Description

[0046] Figure 1 This is a structural diagram of the acquisition and execution unit in this invention;

[0047] Figure 2 This is a tree structure diagram of module scheduling and operation in this invention;

[0048] Figure 3 This is a flowchart of the system management layer program scheduling in this invention. Detailed Implementation

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

[0050] Embodiment 1 of the present invention provides a method for flexibly configuring the functions of a data acquisition and execution unit, applicable to secondary equipment in the field of relay protection. In a preferred but non-limiting embodiment of the present invention, the method includes the following steps:

[0051] Step 1: Summarize the functions of the data acquisition and execution unit and construct its structure, which includes a system management layer and a functional module layer. The system management layer is used for database maintenance and executes the tasks of each functional module in the functional module layer according to the configured linked list. The functional modules in the functional module layer include sampling modules, logic modules, and output modules.

[0052] More preferably, the device program is divided into two layers:

[0053] System management layer program: allocates and manages addresses for each functional module program, maintains the database, and executes each functional module according to the configured linked list;

[0054] Functional module layer program: consists of subroutines of each module;

[0055] The connection diagram of each module is as follows: Figure 1 As shown.

[0056] The system management program contains two types of databases:

[0057] (1) System Configuration Database: This database is generated based on the hardware configuration file CFG of the acquisition and execution unit device and the CCD exported from the field SCD file. Each functional module serves as the input of hardware-related information. The system configuration database contains the following information: the plug-in model and number that the device should have, the slot number of each plug-in inside the device; the correspondence between each input signal in the field and the input terminal of each plug-in; the correspondence between each output signal in the field and the output terminal of the device; the correspondence between the device input terminal and the GOOSE publishing or SV publishing virtual terminal; the correspondence between the GOOSE subscription virtual terminal and the device output terminal; and the logical relationship between the device input terminal and the device output terminal.

[0058] (2) Real-time database: Data collected on-site is processed into mature data by the sampling module or mature data obtained by the logic module after logical operations;

[0059] The functional modules in the functional module layer are divided into three categories:

[0060] (1) Sampling module type: collect field information (this information is not limited to AC voltage, current, remote signaling, DC signal, etc.), process it and convert it into mature data that can be directly used by other modules and fill it into the real-time database, that is, collect various signals, convert them into actual signal values ​​and fill them into the real-time database;

[0061] Among them, "processed data" refers to data that has been processed and can represent on-site dimensional measurements, while "raw data" refers to raw data that has not been processed.

[0062] (2) Output module class: retrieves the output with changes from the real-time database, controls the circuit breaker and disconnector, that is, retrieves the data from the real-time database, controls the circuit breaker, disconnector or publishes SV messages, such as control circuit breaker output, disconnector output, SV message output, GOOSE message output;

[0063] Among them, SV messages are sampled data messages that conform to the "IEC 61850-9-2 Specific communication service mapping (SCSM) - Sampled value over ISO / IEC 8802-3" specification.

[0064] GOOSE message: Substation events oriented towards common objects, conforming to the IEC 61850-8-1 Specific communication service mapping (SCSM) Mappings to MMS and to ISO / IEC 8802-3 standard;

[0065] (3) Logic module class: retrieves real-time data from the real-time database, performs logical operations, and then fills the results of the logical operations into the real-time database;

[0066] More preferably, the modules are not interconnected or coupled, and can operate independently. All modules interact with each other via a real-time database, and deleting any module will not affect the normal operation of other modules.

[0067] The functional modules use standard interface functions to read or write to the real-time database of the system management layer. The module scheduling and execution tree structure is as follows: Figure 2 As shown.

[0068] Step 2: Based on the on-site requirements, according to the functional module structure actually required by the data acquisition and execution unit as defined in the MAT table, obtain the corresponding MAT table and back it up and set the checksum.

[0069] The MAT table (Model Allocation Table) records the location of functional modules. It is crucial for program operation; without it, the application will not function.

[0070] The structural definition (MAT table) of the functional modules is shown in Table 1;

[0071] Table 1

[0072]

[0073] For example, based on the needs of the site, the voltage merging unit device has the following functional modules: AD sampling module; SV subscription module; data alignment module; voltage paralleling module; SV publishing module; alarm management module; human-machine interface module; GOOSE subscription module; GOOSE publishing module; among which, the MAT table for the AD sampling module is Table 2.

[0074] Table 2

[0075]

[0076]

[0077] The MAT tables for other modules are similar.

[0078] More preferably, the MAT table is backed up with three identical copies, each with a CRC checksum to verify the correctness of the MAT table.

[0079] The MAT table uses the CPU's built-in MMU and ECC functions for write protection, and performs CRC checks periodically. When a CRC check error is found in the MAT table in use, a two-out-of-three principle is adopted to select the correct MAT table from the three MAT tables, and the MAT table with the CRC error is automatically repaired.

[0080] MMU (Memory Management Unit) is a type of computer hardware responsible for handling memory access requests from the central processing unit (CPU).

[0081] ECC: (Error Correcting Code) ECC is a technology that enables "error checking and correction".

[0082] Step 3: Configure the required functional modules according to the actual project situation, determine the time slice, priority, and configuration list required by the system management layer for the functional modules, wherein the configuration list is a singly linked list based on the MAT table.

[0083] For example, based on the actual engineering situation, the linked lists for merged units are shown in Tables 3 and 4.

[0084] Table 3. Disruption Link List

[0085]

[0086] Table 4 Polling Linked List

[0087] Voltage paralleling and switching module Alarm Management Module Human-machine interface module

[0088] This step involves developing a configuration software program to implement the required functional modules, and configuring it according to the actual project requirements.

[0089] 1) On which time slice should the required functional modules be defined?

[0090] 2) The priority of this functional module in this time slice

[0091] 3) Based on the above information, organize the functional modules to be executed in each time slice into a linked list.

[0092] More preferably, the time slice is divided as follows: when running on bare metal, scheduling is performed in a time slice manner. This is simple and reliable. Compared with the operating system, it greatly simplifies the system architecture and increases the real-time performance of each module. As a result, the real-time jitter of SV message transmission can be guaranteed to be within 10us.

[0093] Linked list generation: Singly linked lists based on MAT tables are shown in Table 5:

[0094] Table 5

[0095]

[0096] After the system management program finishes executing one module, it retrieves the address of the next module for execution.

[0097] The system management layer program scheduling process is as follows: Figure 3 As shown, the system management layer of the acquisition and execution unit is divided into two categories: interrupt tasks and polling tasks. They run independently according to their respective MAT table configuration information. Interrupt tasks can preempt polling tasks, but polling tasks cannot preempt each other. They can only be scheduled to execute in their current task segment after the currently executing task has finished. Each scheduling block diagram is the same, as shown below:

[0098] If the execution conditions for this task segment are met, the starting address of the first task module is retrieved from the execution list of this task segment, and the program of the first module is executed. After the program of the first module is completed, the task scheduler returns to the task scheduler, retrieves the address of the next module from the list, and executes the program of the next module, until the last module is completed. At this point, the task segment is completed, and the system management layer is returned to execute the next task segment.

[0099] Embodiment 2 of the present invention provides a system for flexibly configuring the functions of the acquisition and execution unit, comprising:

[0100] The system management layer and functional module layer are building units used to summarize the functions of the acquisition and execution unit and construct the structure of the acquisition and execution unit. The system management layer is used for allocating program addresses for each module, maintaining the database, and executing the tasks of each functional module according to the configured linked list. The functional module layer includes sampling modules, logic modules, and output modules.

[0101] The functional module structure definition unit is used to define the actual functional module structure required by the acquisition and execution unit according to the field requirements and the MAT table definition, to obtain the corresponding MAT table and to back up and set the check code of the MAT table.

[0102] The functional module configuration unit is used to configure the required functional modules according to the actual engineering situation, determine the time slice, priority, and configuration list required by the system management layer of the functional modules, wherein the configuration list is a singly linked list based on the MAT table.

[0103] The system management layer is also used to monitor the operating status of each functional module, specifically monitoring whether each functional module occupies CPU load for extended periods; whether it remains inactive for extended periods; and whether its memory usage exceeds a predetermined range. It is also used to monitor the overall system operating status, including:

[0104] Is the system operating under high load? When the load is too high, the system will be unstable, increasing the error of each time slice and making it easy for modules to operate abnormally. Once the maximum load is found to be greater than the load warning value, an alarm will be issued and the CPU load occupancy of each functional module will be provided. Operation and maintenance personnel can optimize the corresponding configuration files and functional programs based on the CPU load occupancy of each module to reduce the load.

[0105] The system monitors read and write operations to the real-time database. If any out-of-bounds situations, illegal addresses, illegal permissions, or illegal operation methods occur, an alarm is issued and the function module number, time, and alarm information of the operation are written to the log file for analysis of the cause of the anomaly.

[0106] A terminal includes a processor and a storage medium; the storage medium is used to store instructions; the processor is used to perform operations according to the instructions to execute the steps of the method.

[0107] A computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps of the method.

[0108] The beneficial effects of this invention are compared with those of the prior art:

[0109] 1. This invention separates the system management layer and the functional module layer, which is beneficial for device development, verification, and maintenance:

[0110] Because the data acquisition and execution units have very strict time requirements, they all run under a bare system and use a single program. However, for the merging unit, smart terminal, and smart device, three different programs are used. Existing technology has both system scheduling and functional modules in the same program, without distinguishing between the system management layer and the functional module layer.

[0111] This invention separates the system management layer from the functional module layer, which facilitates program maintenance. Modifying a single functional module does not require upgrading and verifying the entire program; only the modified module needs to be upgraded and verified, greatly reducing the workload of verification. Simultaneously, the modules are completely decoupled, with no inter-module communication. Their interactions are all conducted through a real-time database. This allows configuration software to determine whether a module needs to run in the actual application. Each module can be written according to its specific needs, improving the security of each module. The modules have single functions, simplifying their functionality, making them easy to write and test, and allowing them to be used as common modules. This allows for the continuous enrichment of the configured functional modules, improving their reliability, maintainability, and readability, thus enhancing the reliability and maintainability of the device.

[0112] 2. The functional modules are highly independent and completely decoupled from each other. Each module has a single function, which is conducive to the writing, verification and maintenance of the modules and improves the reliability of the device.

[0113] 3. This invention can calculate the load rate for each task type. When the maximum load rate exceeds the load warning value, the system management layer will issue an alarm message. This function can help ensure the stable operation of the system.

[0114] 4. The functional module structure is defined based on the MAT table and has the following characteristics:

[0115] Each module has its own version and creation time, which can be managed and upgraded individually.

[0116] Each module's MAT table contains the task type and execution order, as well as the address where the module is stored. Based on these three pieces of information, the system management layer can generate an execution linked list for each task type.

[0117] Upgrading and maintenance are convenient. To replace a module, simply modify the MAT table, delete the "use flag" of the old version, and add the module to the MAT table.

[0118] 5. MAT Table Protection Measures for Functional Modules: Since the MAT table is crucial to this invention, three identical backups of the MAT table are stored. Write protection is implemented using the CPU's built-in MMU and ECC functions, and CRC checks are performed periodically. If a CRC error is detected in any MAT table, a two-out-of-three principle is adopted to select one MAT table as the running MAT table, while automatically repairing erroneous MAT tables. This significantly improves system reliability.

[0119] 6. Program execution order: In general program scheduling, the program is traversed and executed according to the pre-programmed pattern and the function enable / disable flags. The system management program MAT table of this invention generates an execution linked list. Each task type is executed in order according to its own linked list, which greatly improves the flexibility and efficiency of execution.

[0120] This disclosure can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of this disclosure.

[0121] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination of the foregoing. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0122] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0123] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.

[0124] 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 it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the protection scope of the claims of the present invention.

Claims

1. A method for flexibly configuring the functions of a data acquisition and execution unit, characterized in that: The method includes the following steps: Step 1: Summarize the functions of the data acquisition and execution unit and construct its structure, including a system management layer and a functional module layer. The system management layer is used for database maintenance and executes the tasks of each functional module in the functional module layer according to the configured linked list. The functional modules in the functional module layer include sampling modules, logic modules, and output modules. The system management layer includes a system configuration database and a real-time database. The system configuration database is generated based on the hardware configuration file CFG of the data acquisition and execution unit device and the CCD exported from the field SCD file. This system configuration database contains the following information: the plug-in models and quantities that the device should have, the slot number of each plug-in inside the device; the correspondence between each input signal in the field and the input terminals of each plug-in; the correspondence between each output signal in the field and the output terminals of the device; the correspondence between the device input terminals and the GOOSE or SV publish virtual terminals; the correspondence between the GOOSE subscription virtual terminals and the device output terminals; and the logical relationship between the device input terminals and the device output terminals. The real-time database includes the data acquired in the field after being processed into mature data by the sampling module. The sampling module is used to collect field information and process it into mature data that can be directly used by other modules before filling it into the real-time database; the logic module is used to retrieve real-time data from the real-time database, perform logical operations, and then fill the result of the logical operations into the real-time database; the output module is used to obtain output information from the real-time database and perform circuit breaker, disconnector, and interlocking node control or AC voltage and current SV message publication. Each functional module in the functional module layer operates independently and interacts with the real-time database. Each functional module uses standard interface functions to read or write to the real-time database of the system management layer. Step 2: Based on the on-site requirements, according to the MAT table definition, obtain the corresponding MAT table by defining the actual functional module structure required by the acquisition and execution unit, and back up and set the checksum of the MAT table; the MAT table is a module allocation table used to record the location of the functional modules. The contents of the MAT table include: usage flag, functional module name, version, creation time, task type, task number, module priority number and program allocation start address; Step 3: Configure the required functional modules according to the actual project situation, determine the time slice, priority, and configuration list required by the system management layer for the functional modules, wherein the configuration list is a singly linked list based on the MAT table.

2. The method for flexibly configuring the functions of the acquisition and execution unit according to claim 1, characterized in that: In step 2, three copies of the MAT table corresponding to each functional module structure are backed up. Each copy of the MAT table is equipped with a CRC checksum to verify whether the MAT table is correct. The MAT table uses both MMU and ECC for write protection and performs CRC checks periodically. When a CRC check error is found in the MAT table in use, a two-out-of-three principle is adopted to select the correct MAT table from the three MAT tables, and the MAT table with the CRC error is automatically repaired.

3. The method for flexibly configuring the functions of the acquisition and execution unit according to claim 1, characterized in that: In step 3, time slices are divided according to the actual engineering situation, and the specific time slices to which the functional modules should be defined are determined to realize scheduling in a time slice manner during bare-metal operation; the priority of the functional modules in their corresponding time slices is set, and the tasks to be executed in each time slice and the functional module programs are combined with the MAT table to form a singly linked list according to their addresses.

4. The method for flexibly configuring the functions of the acquisition and execution unit according to claim 3, characterized in that: The tasks are divided into two categories: interrupt tasks and polling tasks. Interrupt tasks can preempt polling tasks, while polling tasks cannot preempt each other. They can only be scheduled to run in the current task segment after the currently executing task has finished.

5. The method for flexibly configuring the functions of the acquisition and execution unit according to claim 4, characterized in that: The scheduling process for the task is as follows: If the execution conditions of this task segment are met, the starting address of the first task module program is retrieved from the linked list of this task segment, and the program of the first module is executed. After the program of the first module is executed, the program returns to the task scheduler, retrieves the address of the next module from the linked list, and executes the program of the next module, until the last priority module is executed. Then the task segment is completed and returns to the system management program to execute the next task segment.

6. A system for flexibly configuring the functions of the acquisition and execution unit, used to implement the method described in any one of claims 1-5, characterized in that: The system includes: The system management layer and functional module layer are building units used to summarize the functions of the acquisition and execution unit and construct the structure of the acquisition and execution unit. The system management layer is used for allocating program addresses for each module, maintaining the database, and executing the tasks of each functional module according to the configured linked list. The functional module layer includes sampling modules, logic modules, and output modules. The functional module structure definition unit is used to define the actual functional module structure required by the acquisition and execution unit according to the field requirements and the MAT table definition, to obtain the corresponding MAT table and to back up and set the check code of the MAT table. The functional module configuration unit is used to configure the required functional modules according to the actual engineering situation, determine the time slice, priority, and configuration list required by the system management layer of the functional modules, wherein the configuration list is a singly linked list based on the MAT table.

7. The system for flexibly configuring the acquisition and execution unit function according to claim 6, characterized in that: The system management layer is also used to monitor the operating status of each functional module, specifically monitoring whether each functional module occupies CPU load for an extended period; whether it has been idle for a long time; and whether the memory usage exceeds the predetermined range. It is also used to monitor the overall system operating status, including: whether the system is operating at a high load rate; if the maximum load rate exceeds the load warning value, an alarm is issued and the CPU load occupancy rate of each functional module is provided; and it monitors read and write operations to the real-time database, issuing alarms and writing the functional module number, time, and alarm information to a log file if any out-of-bounds, illegal operation addresses, illegal permissions, or illegal operation methods occur, for analysis of the cause of the anomaly.

Citation Information

Patent Citations

  • Intelligent substation process layer intelligent component implementation method and device

    CN109542450A

  • Relay protection system and method capable of being flexibly defined

    CN115833065A