Data forwarding method applied to power system, electronic device and storage medium

Abstract

The application provides a data forwarding method applied to a power system, an electronic device and a storage medium. The method comprises the following steps: acquiring power data of the power system, and determining a mapping mark of the power data; mapping the power data to a data mapping queue corresponding to the mapping mark, so as to upload the power data to a specified master station of the power system through a forwarding protocol corresponding to the data mapping queue, wherein the mapping mark is used for indicating a mapping relationship between the power data and the data mapping queue, and each data mapping queue corresponds to one forwarding protocol. The application can improve the working reliability of the power system.

Description

Technical Field

[0001] This application relates to the field of power data transmission technology, and in particular to a data forwarding method, electronic device and storage medium applied to power systems. Background Technology

[0002] As electricity consumption continues to increase and power systems grow larger, the amount of data that needs to be transmitted also increases. Data from different locations within the power system can be of various types, requiring the use of corresponding data protocols for forwarding.

[0003] Currently, traditional data forwarding processing in power systems periodically checks for changes in data types and whether the forwarding protocol needs updating. If the data type changes, the forwarding protocol is updated first, and then the data is forwarded to the corresponding master station. However, this method requires periodic protocol updates, leading to lower data forwarding efficiency in power systems. Summary of the Invention

[0004] This application provides a data forwarding method, electronic device, and storage medium for use in power systems, in order to solve the problem that traditional data forwarding processing requires periodic updates to the forwarding protocol, which leads to low data forwarding efficiency in power systems.

[0005] Firstly, this application provides a data forwarding method for power systems, including:

[0006] Acquire power data from the power system and determine the mapping markers for the power data;

[0007] Power data is mapped to data mapping queues corresponding to mapping flags, so that the power data can be uploaded to the designated master station of the power system through the forwarding protocol corresponding to the data mapping queue. The mapping flag is used to indicate the mapping relationship between power data and data mapping queues, and each data mapping queue corresponds to a forwarding protocol.

[0008] In one possible implementation, the power data includes device data, and the mapping flags of the device data are used to indicate the location information of the device data and the mapping relationship of the corresponding data mapping queue.

[0009] In one possible implementation, power data includes non-device data, which includes background data and application data; the mapping flags of the non-device data are used to indicate the mapping relationship between the point name labels of the non-device data and the corresponding data mapping queues.

[0010] In one possible implementation, the name tag includes station name tags, device tags, and name tags (non-device data).

[0011] In one possible implementation, the method further includes, before acquiring the power system's power data:

[0012] Obtain the mapping flags for all power data in the power system;

[0013] Based on the mapping flags of all power data, establish the mapping relationship between each power data and the data mapping queue.

[0014] In one possible implementation, determining the mapping markers for the power data includes:

[0015] Determine if the power data has changed;

[0016] If changes occur, the mapping flag for the power data is determined.

[0017] Secondly, this application provides a data forwarding device for use in a power system, comprising:

[0018] The first acquisition module is used to acquire power data from the power system and determine the mapping flags of the power data;

[0019] The forwarding module is used to map power data to data mapping queues corresponding to mapping flags, so that the power data can be uploaded to the designated master station of the power system through the forwarding protocol corresponding to the data mapping queue. The mapping flag is used to indicate the mapping relationship between power data and data mapping queues, and each data mapping queue corresponds to a forwarding protocol.

[0020] Thirdly, this application provides an electronic device including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the computer program, it implements the steps of the data forwarding method applied to a power system as described in the first aspect or any possible implementation of the first aspect.

[0021] Fourthly, this application provides an electrical system including the electronic equipment described in the fourth aspect above.

[0022] Fifthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the data forwarding method applied to a power system as described in the first aspect or any possible implementation of the first aspect.

[0023] This application provides a data forwarding method, electronic device, and storage medium for power systems. By acquiring power data from the power system and determining the mapping flag of the power data, the power data is then mapped to at least one data mapping queue based on the mapping flag. The power data is then uploaded to the designated master station of the power system through the forwarding protocol corresponding to each data mapping queue. This eliminates the need to update the forwarding protocol, thereby shortening the data transmission time of the power system, improving the forwarding efficiency of the power system, and ultimately improving the operational reliability of the power system. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 This is a flowchart illustrating the implementation of a data forwarding method for power systems provided in this application embodiment;

[0026] Figure 2 This application illustrates a data mapping relationship diagram according to an embodiment of the present application;

[0027] Figure 3 Another data mapping relationship diagram according to an embodiment of this application is shown;

[0028] Figure 4 This illustration shows a data mapping relationship provided in an embodiment of this application;

[0029] Figure 5 This is a schematic diagram of the structure of a data forwarding device applied to a power system according to an embodiment of this application;

[0030] Figure 6 This is a schematic diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0031] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0032] To make the objectives, technical solutions, and advantages of this application clearer, the following description will be provided in conjunction with the accompanying drawings and specific embodiments.

[0033] With the increasing number of power devices, power data from each device is uploaded to a corresponding master station for aggregation. Staff can then remotely access this data from the master station for intuitive monitoring and troubleshooting based on real-time data. However, power data needs to be converted using a specific forwarding protocol before being uploaded to the master station to ensure data consistency. Currently, when the data type changes, the power device needs to check if the forwarding protocol has been updated. After a data change, the forwarding protocol is updated before the data is forwarded to the corresponding master station. This method requires periodic protocol updates, leading to reduced data forwarding efficiency in the power system.

[0034] To address the aforementioned problems, this application provides a data forwarding method applicable to power systems. See also... Figure 1 This illustrates a flowchart of the implementation of a data forwarding method for power systems provided in an embodiment of this application. Figure 1 As shown, a data forwarding method applied to a power system may include S101 and S102.

[0035] S101, acquire power data from the power system and determine the mapping flag for the power data.

[0036] The executing entity in this application embodiment can be a data controller or data control terminal of power equipment in a power system. The data controller or data control terminal pre-stores a first number of data mapping queues, each data mapping queue corresponding to a forwarding protocol. For example, it can include N data mapping queues and N forwarding protocols. The specific number can be set according to actual conditions. The following embodiment of this application uses a data controller as the executing entity.

[0037] The data controller acquires power data from the power system, which includes various data types. Each type of power data corresponds to a mapping flag, which determines the data mapping queue information and the master station information to be uploaded to for that power data.

[0038] Generally, when power data remains unchanged, it is uploaded to the corresponding master station through a pre-defined data mapping queue. When power data changes, a new data mapping queue is determined based on the current mapping flag, and the changed power data is uploaded to the corresponding master station.

[0039] Therefore, in some embodiments of this application, determining the mapping flag for power data may include S1011 and S1012.

[0040] S1011, determine whether the power data has changed;

[0041] S1012, if a change occurs, determine the mapping flag for the power data.

[0042] S102, map the power data to the data mapping queue corresponding to the mapping flag, so as to upload the power data to the designated master station of the power system through the forwarding protocol corresponding to the data mapping queue. The mapping flag is used to indicate the mapping relationship between the power data and the data mapping queue, and each data mapping queue corresponds to a forwarding protocol.

[0043] The data controller maps the power data to the corresponding data mapping queue, and then sends the power data to the forwarding protocol corresponding to the data mapping queue. After the conversion is completed, it is uploaded to the corresponding master station.

[0044] Optionally, power data may include equipment data and non-equipment data. Equipment data indicates the electrical parameters of the power equipment, such as current or voltage. Non-equipment data indicates the non-electrical parameters of the equipment, such as temperature, pressure, etc.

[0045] The data controller may include a first processing module and a second processing module. The first processing module collects device data, maps the device data to corresponding data mapping queues using mapping flags, converts the device data using corresponding forwarding protocols, and finally uploads it to the corresponding master station. The second processing module collects non-device data, maps non-device data to corresponding data mapping queues using mapping flags, converts the non-device data using corresponding forwarding protocols, and finally uploads it to the corresponding master station.

[0046] Figure 2 A data mapping diagram according to an embodiment of this application is shown. For example... Figure 2 As shown, the system can include N data mapping queues, and correspondingly, N forwarding protocols. The first processing module maps device data to all N data mapping queues, enabling the device data to be converted into N formats. When the master station needs the data, it can retrieve the corresponding format for uploading. The second processing module maps non-device data, also mapping it to all N data mapping queues and converting it into N formats. When the master station needs the data, it can retrieve the corresponding format for uploading.

[0047] For example, such as Figure 2As shown, the mapping flags in the device data indicate that the device data needs to be uploaded to main station 1 via forwarding protocol 1 and forwarding protocol 2, and also needs to be uploaded to main station 2 via forwarding protocol 5. Therefore, the first processing module will map the device data to data mapping queue 1, data mapping queue 2, and data mapping queue 5, so that the device data can be converted into three data formats simultaneously for corresponding uploads.

[0048] For example, such as Figure 2 As shown, the mapping flags in the non-device data indicate that this non-device data needs to be uploaded to main station 1 via forwarding protocol 3 and forwarding protocol 6, and also needs to be uploaded to main station 2 via forwarding protocol 9. Therefore, the first processing module will map the device data to data mapping queue 3, data mapping queue 6, and data mapping queue 9, so that the non-device data can be converted into three data formats simultaneously for corresponding upload.

[0049] This application embodiment maps and uploads power data through a data mapping queue, eliminating the need to update the forwarding protocol. This can shorten the data transmission time of the power system, improve the forwarding efficiency of the power system, and thus enhance the operational reliability of the power system.

[0050] In some embodiments of this application, the power data includes device data, and the mapping flag of the device data is used to indicate the location information of the device data and the mapping relationship of the corresponding data mapping queue.

[0051] Different power equipment is located in different places. In order to distinguish the equipment data of each power equipment, the location information of the equipment data can be used as a mapping mark to determine the data source. The location information of each equipment data can correspond to a different data mapping queue.

[0052] In some embodiments of this application, power data includes non-device data, which includes background data and application data; the mapping flag of non-device data is used to indicate the mapping relationship between the point name label of non-device data and the corresponding data mapping queue.

[0053] Non-equipment data from different power devices may be of the same type. By using the name tags of the non-equipment data as mapping markers, the data source can be identified, and then the non-equipment information can be mapped to the corresponding data mapping queue.

[0054] Non-equipment data can include backend data and application data. Point-of-origin labels include the station name label, equipment label, and point name for the non-equipment data. The station name label is the name of the main power station corresponding to the non-equipment data; the equipment label is the name of the power equipment corresponding to the non-equipment data; and the point name is the name of the location where the non-equipment data is located. For example, the point-of-origin label can be represented as "occ.HVPM01_HVOC_01YB_zydlq.Pos".

[0055] In some embodiments of this application, a mapping relationship is established before acquiring power data from the power system. The establishment process may include:

[0056] Obtain the mapping flags for all power data in the power system;

[0057] Based on the mapping flags of all power data, establish the mapping relationship between each power data and the data mapping queue.

[0058] Figure 3 Another data mapping relationship diagram according to an embodiment of this application is shown. For example... Figure 3 As shown, the data controller may include a device data processing module, a background data processing module, and an application data processing module. The device data processing module can map device data to N data mapping queues. The background data processing module can map background data to N data mapping queues. The application data processing module can map application data to N data mapping queues.

[0059] Figure 4 This diagram illustrates a data mapping relationship provided in an embodiment of this application. Location information from device data, point-of-sale (POS) tags from background data, and POS tags from application data are all used as mapping keys. By establishing data mapping flags, N forwarding protocols are associated with these flags.

[0060] This application embodiment unifies data from different data sources (device data, application data, and backend data) into a single mapping relationship, which facilitates unified processing by forwarding protocols.

[0061] Specifically, the mapping relationship is implemented through the structure SFesFwMapping, and each data point supports a maximum of 32 forwarding protocols.

[0062] typedef struct{

[0063] int MappingIndex;

[0064] int RemoteNo;

[0065] }SFesFwMapping;

[0066] MappingIndex: / / Forwarding protocol mapping index, each forwarding protocol corresponds to a unique MappingIndex;

[0067] RemoteNo: / / Dot number for the forwarding protocol;

[0068] When configuring the forwarding protocol point, the data controller will specify the data source and data source point label of the forwarding point, so that a mapping relationship can be established according to the configuration.

[0069] Data sources are divided into three types: device data, application data, and backend data. The specific methods are as follows:

[0070] (1) For device data, the data source can be the power equipment acquisition protocol. The forwarding point table of the acquisition protocol includes the SFesFwMapping structure. During initialization, the forwarding point table is searched one by one. If the data source in the forwarding point table is found in the forwarding point table, the SFesFwMapping structure is added. Each time a data source is found, an SFesFwMapping structure is added. That is, the number of SFesFwMapping structures is equal to the number of times the data source point is forwarded.

[0071] For example,

[0072]

[0073]

[0074] (2) For application data, the m_mapFwPubFesXX queue includes the SFesFwMapping structure. During initialization, the forwarding point table is searched one by one. When the point name label of the data source in the forwarding point table cannot be found in the m_mapFwPubFesXX queue, the point name of the data source is added to the m_mapFwPubFesXX queue, and the SFesFwMapping structure is set. If it already exists, an SFesFwMapping structure is added to the found point name.

[0075] typedef struct{

[0076] int SrcLocationID;

[0077] int SrcSubSystem;

[0078] char DPTagName[CN_FesMaxTagSize];

[0079] int FesRtuNo;

[0080] int SrcPointNo;

[0081] float Value;

[0082] uint32 Status;

[0083] uint64 time;

[0084] int FwMapNum;

[0085] SFesFwMapping FwMapping[CN_Fes_Fw_MaxMapping];

[0086] }SFesFwPubAi;

[0087] std::map<std::string,SFesFwPubAi> m_mapFwPubFesAi;

[0088] std::map<std::string,SFesFwPubDi> m_mapFwPubFesDi;

[0089] std::map<std::string,SFesFwPubAcc> m_mapFwPubFesAcc;

[0090] std::map<std::string,SFesFwPubMi> m_mapFwPubFesMi;

[0091] (3) For backend data, the mapFwPubDpXX queue includes the SFesFwMapping structure. During initialization, the forwarding point table is searched one by one. When the data source point name label in the forwarding point table cannot be found in the m_mapFwPubDpXX queue, the point name of the data source is added to the m_mapFwPubDpXX queue, and the SFesFwMapping structure is set. If it already exists, an SFesFwMapping structure is added to the found point.

[0092] typedef struct{

[0093] int SrcLocationID;

[0094] int SrcSubSystem;

[0095] char DPTagName[CN_FesMaxTagSize];

[0096] int FesRtuNo;

[0097] int SrcPointNo;

[0098] float Value;

[0099] uint32 Status;

[0100] uint64 time;

[0101] int FwMapNum;

[0102] SFesFwMapping FwMapping[CN_Fes_Fw_MaxMapping];

[0103] }SFesFwPubAi;

[0104] std::map<std::string,SFesFwPubAi> m_mapFwPubDpAi;

[0105] std::map<std::string,SFesFwPubDi> m_mapFwPubDpDi;

[0106] std::map<std::string,SFesFwPubAcc> m_mapFwPubDpAcc;

[0107] std::map<std::string,SFesFwPubMi> m_mapFwPubDpMi;

[0108] In this embodiment, the device data processing module uses the device information at the collection point as a key identifier for mapping, while the background data and application data use point labels as key identifiers for mapping. Since the devices in the system are diverse, and some devices collect the same data, each point needs a unique point label for differentiation. Therefore, the point name label can consist of a station name label, a device label, and the point name, connected by a ".". For example: occ.HVPM01_HVOC_01YB_zydlq.Pos.

[0109] In this embodiment, after receiving data from the communication interface, the device data processing module performs judgment and other processing on the data. If it finds that the data has changed, it directly sends the data to the data mapping queue corresponding to the forwarding protocol based on the data mapping flag. After receiving data from the message bus, the background data processing module and the application data processing module perform judgment and other processing on the data. If they find that the data has changed, they directly send the data to the forwarding protocol data queue based on the data mapping flag. The system sends the data to the data mapping queue of the forwarding protocol through unified forwarding data interfaces such as WriteFwDiBuf(), WriteFwAiBuf(), WriteFwAccBuf(), and WriteFwMiBuf().

[0110] For example, void WriteFwDiBuf(SFesFwChgDi buffer);

[0111] void WriteFwAiBuf(SFesFwChgAi buffer);

[0112] void WriteFwAccBuf(SFesFwChgAcc buffer);

[0113] void WriteFwMiBuf(SFesFwChgMi buffer;

[0114] In this embodiment, the data mapping queue and the forwarding protocol synchronize messages using semaphores. When the system calls the unified forwarding data interface, it activates the semaphore. Upon receiving the semaphore, the forwarding protocol reads the data from the data mapping queue and forwards the data according to the protocol format. Simultaneously, to prevent semaphore reception failures, the forwarding protocol periodically checks the data mapping queue. If data is found in the queue, it also forwards the data according to the protocol format, increasing the reliability of data forwarding.

[0115] This application primarily addresses the diversity of data sources in power systems by providing a unified mapped data interface to facilitate data processing for forwarding protocols. Data transmission based on data mapping significantly improves the speed and efficiency of data forwarding, and the forwarding speed does not slow down as the number of forwarding points increases. Furthermore, because data is transmitted using data mapping, data is simultaneously transmitted to the data mapping queues of each forwarding protocol, ensuring the accuracy of data from each protocol.

[0116] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0117] The following are device embodiments of this application. For details not described in detail, please refer to the corresponding method embodiments described above.

[0118] Figure 5 A schematic diagram of a data forwarding device applied to a power system according to an embodiment of this application is shown. For ease of explanation, only the parts related to the embodiment of this application are shown, and are described in detail below:

[0119] like Figure 5 As shown, the data forwarding device 20 applied to the power system may include:

[0120] The first acquisition module 201 is used to acquire power data of the power system and determine the mapping flag of the power data;

[0121] The forwarding module 202 is used to map power data to a data mapping queue corresponding to a mapping flag, so as to upload the power data to the designated master station of the power system through the forwarding protocol corresponding to the data mapping queue. The mapping flag is used to indicate the mapping relationship between power data and data mapping queues, and each data mapping queue corresponds to a forwarding protocol.

[0122] In some embodiments of this application, the power data includes device data, and the mapping flag of the device data is used to indicate the location information of the device data and the mapping relationship of the corresponding data mapping queue.

[0123] In some embodiments of this application, power data includes non-device data, which includes background data and application data; the mapping flag of non-device data is used to indicate the mapping relationship between the point name label of non-device data and the corresponding data mapping queue.

[0124] In some embodiments of this application, the name tag includes station name tags, device tags, and names that are not part of the device data.

[0125] In some embodiments of this application, the device 20 may further include:

[0126] The second acquisition module is used to acquire the mapping flags of all power data in the power system before acquiring the power data of the power system;

[0127] A module is established to create a mapping relationship between each power data point and a data mapping queue, based on the mapping flags of all power data.

[0128] In some embodiments of this application, the first acquisition module 201 may further include:

[0129] The judgment unit is used to determine whether the power data has changed;

[0130] A determination unit is used to determine the mapping flag of the power data if a change occurs.

[0131] Figure 6 This is a schematic diagram of the electronic device provided in an embodiment of this application. For example... Figure 6 As shown, the electronic device 30 of this embodiment includes a processor 300 and a memory 301, wherein the memory 301 stores a computer program 302 that can run on the processor 300. When the processor 300 executes the computer program 302, it implements the steps in the various data forwarding method embodiments applied to the power system described above, for example... Figure 1 S101 to S102 are shown. Alternatively, when the processor 300 executes the computer program 302, it implements the functions of each module / unit in the above-described device embodiments, for example... Figure 5The functions of modules 201 to 202 are shown.

[0132] For example, computer program 302 can be divided into one or more modules / units, one or more of which are stored in memory 301 and executed by processor 300 to complete this application. One or more modules / units can be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of computer program 302 in electronic device 30. For example, computer program 302 can be divided into... Figure 5 Modules 201 to 202 are shown.

[0133] Electronic device 30 may be a data device, server, etc. Electronic device 30 may include, but is not limited to, processor 300 and memory 301. Those skilled in the art will understand that... Figure 6 This is merely an example of electronic device 30 and does not constitute a limitation on electronic device 30. It may include more or fewer components than shown, or combine certain components, or different components. For example, electronic device may also include input / output devices, network access devices, buses, etc.

[0134] The processor 300 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0135] The memory 301 can be an internal storage unit of the electronic device 30, such as a hard disk or RAM of the electronic device 30. The memory 301 can also be an external storage device of the electronic device 30, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the electronic device 30. Furthermore, the memory 301 can include both internal and external storage units of the electronic device 30. The memory 301 is used to store computer programs and other programs and data required by the electronic device. The memory 301 can also be used to temporarily store data that has been output or will be output.

[0136] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0137] This application also provides a power system including the aforementioned electronic device 30.

[0138] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0139] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0140] In the embodiments provided in this application, it should be understood that the disclosed devices / electronic devices and methods can be implemented in other ways. For example, the device / electronic device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0141] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0142] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0143] If an integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various data forwarding method embodiments applied to power systems described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.

[0144] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application 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 of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A data forwarding method applied to a power system, characterized in that, include: Acquire the power data of the power system and determine the mapping flag of the power data; The power data is mapped to the data mapping queue corresponding to the mapping flag, so that the power data is uploaded to the designated master station of the power system through the forwarding protocol corresponding to the data mapping queue. The mapping flag is used to indicate the mapping relationship between the power data and the data mapping queue, and each data mapping queue corresponds to a forwarding protocol. The power data includes equipment data and non-equipment data. The equipment data is used to indicate the electrical parameters of the power equipment, and the non-equipment data is used to indicate the non-electrical parameters of the equipment. The mapping flag for the device data is the location information of the device data, and the mapping flag for the non-device data is the name tag of the non-device data.

2. The data forwarding method applied to a power system according to claim 1, characterized in that, The mapping flag for the device data is used to indicate the mapping relationship between the location information of the device data and the corresponding data mapping queue.

3. The data forwarding method applied to a power system according to claim 1, characterized in that, The non-device data includes background data and application data; the mapping flag of the non-device data is used to indicate the mapping relationship between the point name label of the non-device data and the corresponding data mapping queue.

4. The data forwarding method applied to a power system according to claim 3, characterized in that, The point name label includes the station name label, device label, and point name of the non-device data.

5. The data forwarding method applied to a power system according to claim 1, characterized in that, Prior to acquiring the power data of the power system, the method further includes: Obtain the mapping flags for all power data in the power system; Based on the mapping flags of all power data, establish the mapping relationship between each power data and the data mapping queue.

6. The data forwarding method applied to a power system according to any one of claims 1 to 5, characterized in that, The step of determining the mapping flag for the power data includes: Determine whether the power data has changed; If a change occurs, the mapping flag for the power data is determined.

7. A data forwarding device for use in a power system, characterized in that, include: The first acquisition module is used to acquire the power data of the power system and determine the mapping flag of the power data; A forwarding module is used to map the power data to a data mapping queue corresponding to the mapping flag, so as to upload the power data to a designated master station of the power system through the forwarding protocol corresponding to the data mapping queue. The mapping flag is used to indicate the mapping relationship between the power data and the data mapping queue, and each data mapping queue corresponds to a forwarding protocol. The power data includes equipment data and non-equipment data. The equipment data is used to indicate the electrical parameters of the power equipment, and the non-equipment data is used to indicate the non-electrical parameters of the equipment. The mapping flag for the device data is the location information of the device data, and the mapping flag for the non-device data is the name tag of the non-device data.

8. An electronic device comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the data forwarding method for a power system as described in any one of claims 1 to 6.

9. An electric power system, characterized in that, Including the electronic device as described in claim 8.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the data forwarding method for a power system as described in any one of claims 1 to 6.

Images