Monitoring method, device and system for data transmission between power systems and electronic equipment
By using object storage databases and message queues on the cloud processing platform, monitoring and verification of data files between power systems is solved, and the integrity and security issues in data file transmission are ensured, ensuring the reliability and security of data transmission between power systems.
Patent Information
- Application Number
- CN202311339268.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-10-16
- Publication Date
- 2025-04-18
AI Technical Summary
When data file interaction between different power systems, the storage of data files occupies a large amount of server space, and the execution of file movement commands of the system in the prior art may lead to data file truncation, and the integrity of data file transmission cannot be guaranteed.
By using object storage databases and message queues on the cloud processing platform, monitoring and verification of data files is achieved. The client receives the message body sent by the cloud platform, parses and obtains the storage path and identification information of the data file, and generates transmission monitoring results. The server parses the data file, generates a message body and uploads it to the message queue, ensuring the integrity of the data file during transmission.
It effectively solves the problems of integrity and security in data file transmission process, and ensures the reliability and security of data transmission between power systems.
Smart Images

Figure CN119848950A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer software, and in particular to a method, device, system and electronic equipment for monitoring data transmission between power systems. Background Art
[0002] In recent years, as the scale of power dispatching systems continues to expand, the safe and stable operation of the system requires access to massive amounts of data. At the same time, the development of the power spot market has led to a surge in the demand for data interaction between power dispatching systems, and a large number of data files will be generated in this process.
[0003] The inventor of this application found that when data files are interacted between different power systems, the storage of data files needs to occupy a large amount of server storage space; at the same time, when executing the file move command of the system in the prior art, the data file may be truncated, and the integrity of the data file transmission cannot be guaranteed. With the rapid development of cloud storage technology, object storage and message queues have provided solutions for data transmission in power dispatching systems. Summary of the invention
[0004] According to the first aspect of the present application, a method for monitoring data transmission between power systems is proposed, which is applied to a client. The method may include: receiving a message body corresponding to a data file sent by a cloud processing platform; parsing the message body to obtain a storage path of the data file in an object storage database of the cloud processing platform and first identification information of the data file; obtaining the data file from the object storage database according to the storage path; generating second identification information based on the data file; and generating a transmission monitoring result based on the first identification information and the second identification information.
[0005] According to the second aspect of the present application, a method for monitoring data transmission between power systems is proposed, which is applied to a server, and the method may include: parsing a data file to be verified to obtain path information of data transmission and first identification information of the data file; determining a transmission scenario of data transmission based on the path information; when the transmission scenario is data transmission across security zones, or when the transmission scenario is data reception, uploading the data file to an object storage database of a cloud processing platform; adding the storage path of the data file in the object storage database to the path information; generating a message body based on the path information and the first identification information; and sending the message body to a message queue of the cloud processing platform.
[0006] According to the third aspect of the present application, a monitoring device for data transmission between power systems is proposed, and the device may include: a message receiving module, used to receive a message body corresponding to a data file sent by a cloud processing platform; a message parsing module, used to parse the message body to obtain a storage path of the data file in an object storage database of the cloud processing platform and first identification information of the data file; a file acquisition module, used to obtain the data file from the object storage database according to the storage path; an identification generation module, used to generate second identification information based on the data file; and a result generation module, used to generate a transmission monitoring result based on the first identification information and the second identification information.
[0007] According to the fourth aspect of the present application, a monitoring system for data transmission between power systems is proposed, which system may include a server, a client and a cloud processing platform, and the cloud processing platform may include an object storage database and a message queue, wherein: the client can be used to execute the method described in the first aspect of the present application; the server can be used to execute the method described in the second aspect of the present application; the cloud processing platform can be used to receive data files sent by the server, store the data files in the object storage database, and send the data files to the client; the cloud processing platform can also be used to receive a message body sent by the server, add the message body to the message queue, and send the message body to the client.
[0008] According to the fifth aspect of the present application, an electronic device is proposed, which may include: a processor; and a memory storing a computer program, wherein when the computer program is executed by the processor, the processor executes the method described in the first and second aspects of the present application.
[0009] According to the sixth aspect of the present application, a non-transitory computer-readable storage medium is proposed, on which computer-readable instructions are stored. When the instructions are executed by a processor, the processor executes the method described in the first and second aspects of the present application.
[0010] The monitoring method for data transmission between power systems proposed in the present application parses the data file to be transmitted on the server side, generates a message body based on the data file and uploads it to the message queue of the cloud processing platform, and uploads the data file to the object storage database of the cloud processing platform; obtains the data file from the object storage database on the client side, generates second identification information based on the data file, obtains the first identification information corresponding to the data file from the message queue, and generates the transmission monitoring result by verifying the first identification information and the second identification information. The method proposed in the present application utilizes the object storage database and message queue in the cloud processing platform to realize the verification of data files in data transmission, and ensures the data integrity and the security and effectiveness of data transmission in the process of data transmission between power systems. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without exceeding the scope of protection required by the present application.
[0012] Figure 1 A schematic diagram of an application environment of the method for monitoring data transmission between power systems of the present application;
[0013] Figure 2 A flowchart of a method 1000 for monitoring data transmission between power systems applied to a client of the present application;
[0014] Figure 3 for Figure 2 A schematic flow chart of step S105 in method 1000;
[0015] Figure 4 A flowchart of a monitoring method 2000 for data transmission between power systems applied to a client of the present application;
[0016] Figure 5 for Figure 4 A flow chart of step S207 in method 2000;
[0017] Figure 6 A flowchart of a monitoring method 3000 for data transmission between power systems applied to a client of the present application;
[0018] Figure 7 A flowchart of a method 4000 for monitoring data transmission between power systems applied to a client of the present application;
[0019] Figure 8 A flowchart of a monitoring method 5000 for data transmission between power systems applied to a server of the present application;
[0020] Fig. 9 for Figure 8 A schematic flow chart of step S502 in method 5000;
[0021] Fig.10 A flowchart of a monitoring method 6000 for data transmission between power systems applied to a server of the present application;
[0022] Fig.11 A schematic diagram of the structure of a monitoring device 100 for data transmission between power systems of the present application;
[0023] Fig.12A schematic diagram of the structure of a monitoring system 200 for data transmission between power systems of the present application;
[0024] Fig.13 A schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION
[0025] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.
[0026] Figure 1 Schematic diagram of the application environment of the monitoring method for data transmission between power systems of the present application. The method of the present application can be applied to Figure 1 In the application environment shown. According to the characteristics of the power secondary system, the existing power system is divided into a production control area and a management information area. The production control area is divided into a control area (safety area I) and a non-control area (safety area II). The information management area is divided into a production management area (safety area III) and a management information area (safety area IV). Different safety zones have different safety protection requirements, among which safety area I has the highest safety level, followed by safety area II, and the rest are deduced in the same way. Figure 1 As shown, the application environment includes power system 1, power system 2 and power system 3 in security zone II and power system 4 in security zone III, wherein power system 3 includes a server 31, a cloud platform 32 and a client 33, and power system 4 includes a server 41, a cloud platform 42 and a client 43.
[0027] exist Figure 1 In the application environment shown, in the same security zone II, the power system 1 sends a data file to the power system 3. For the power system 3, the data file to be verified at this time is the data file 1 sent by the power system 1. The server 31 determines that the transmission scenario corresponding to the data file 1 is data reception according to the data file 1. When the transmission scenario is data reception, the server 31 generates a message body 1 and uploads the data file 1 and the message body 1 to the cloud platform 32. The client 33 obtains the message body 1 and the data file 1 from the cloud platform 32, and obtains the first identification information 1 according to the parsing of the message body 1, generates the second identification information 1 according to the data file 1, and generates the transmission monitoring result 1 according to the first identification information 1 and the second identification information 1. When the transmission scenario is data reception and the transmission monitoring result 1 is a successful transmission, the client 33 consumes the data of the data file 1.
[0028] exist Figure 1In the application environment shown, in the same security zone II, the power system 3 sends data file 2 to the power system 2. For the power system 3, the data file to be verified at this time is the data file 2 to be sent in the power system 3. The server 31 parses the data file 2, obtains the path information, and determines that the transmission scenario is data transmission according to the path information, the security zone where the power system 2 to be sent is the security zone II, and the data transmission corresponding to the data file 2 is data transmission that does not cross the security zone. When the transmission scenario is data transmission and the data transmission is not across the security zone, the server 31 sends the data file 2 to the target system, that is, the power system 2.
[0029] exist Figure 1 In the application environment shown, the power system 3 belonging to the safety zone II sends the data file 3 to the power system 4 belonging to the safety zone III. For the power system 3, the data file to be verified at this time is the data file 3 to be sent in the power system 3. The server 31 parses the data file 3, obtains the path information, and determines that the transmission scenario is data transmission according to the path information, the safety zone where the power system 4 to be sent is located is the safety zone III, and the data corresponding to the data file 3 is transmitted across the safety zone. When the transmission scenario is data transmission and the data transmission crosses the safety zone, the server 31 generates a message body 2 and uploads the data file 3 and the message body 2 to the cloud platform 32. The client 33 obtains the message body 2 and the data file 3 from the cloud platform 32, and obtains the first identification information 2 according to the parsing of the message body 2, generates the second identification information 2 according to the data file 3, and generates the transmission monitoring result 2 according to the first identification information 2 and the second identification information 2.
[0030] In the case where the transmission scenario is data transmission across security zones, the client 33 sends the transmission monitoring result 2 to the isolation device 1 for cross-security zone transmission between security zones II and III. In the case where the transmission monitoring result 2 is a successful transmission, the power system 3 sends the data file 3 to the isolation device 1. In the case where the transmission monitoring result 2 is a successful transmission, the power system 4 obtains the data file 3 through the isolation device 1, and the server 41, the cloud platform 42, and the client 43 execute the monitoring method for data transmission between power systems in the case where the transmission scenario is data reception.
[0031] The monitoring method for data transmission between power systems proposed in this application utilizes the server, cloud processing platform and client to monitor the data files to be transmitted and generate transmission monitoring results in the case of receiving data files during data transmission between power systems and sending data files during data transmission across security zones. The method proposed in this application utilizes the object storage database and message queue in the cloud processing platform to implement the verification of data files during data transmission, ensuring data integrity and safe and effective data transmission during data transmission between power systems.
[0032] Figure 2 FIG. 1 is a flow chart of a monitoring method 1000 for data transmission between power systems of a client according to the present application. Figure 2 As shown, method 1000 includes steps S101 to S105.
[0033] In step S101, the client receives a message body corresponding to a data file sent by a cloud processing platform. In some specific embodiments, in step S101, the client is a data integration server. The client includes identification information of a data file related to itself. Optionally, the identification information is a tag. In some specific embodiments, the client receives a message body corresponding to a data file in a message queue of the cloud processing platform according to the tag of the data file.
[0034] In step S102, the client parses the message body to obtain the storage path of the data file in the object storage database of the cloud processing platform and the first identification information of the data file. In some specific embodiments, the message body includes the path information of the data file and the first identification information, and the path information includes the storage path of the data file in the object storage database of the cloud processing platform. Optionally, the first identification information is the MD5 code of the data file.
[0035] In some specific embodiments, in step S103, the client obtains the data file from the object storage database according to the storage path. In some specific embodiments, the path information includes a verification path, and the verification path includes a first node and a second node in the current system, wherein the first node is a file server (i.e., a server) that verifies the data file in the current system, and the second node is a data integration server (i.e., a client) that verifies the data file in the current system, and the verification path also includes a first directory stored in the first node and a second directory stored in the second node. In step S103, the client stores the obtained data file in the second directory.
[0036] In step S104, the client generates second identification information according to the data file. In step S105, the client generates a transmission monitoring result according to the first identification information and the second identification information. Optionally, the second identification information is an MD5 code generated according to the data file. The client compares the first identification information and the second identification information to generate a transmission monitoring result.
[0037] According to Figure 2 In the embodiment shown, the method for monitoring data transmission between power systems proposed in the present application obtains the identification information of the data file to be transmitted and the data file corresponding to the current data transmission at the client of the power system, and compares the identification information generated according to the obtained data file with the received identification information, and generates a transmission monitoring result. Figure 2The method shown, the solution proposed in this application uses identification information to monitor the data files received by the client to ensure the reliability of the transmission process.
[0038] Figure 3 for Figure 2 The flowchart of step S105 in method 1000 is shown in FIG. Figure 3 As shown, step S105 includes step S1051-step S1052.
[0039] In step S1051, if the first identification information and the second identification information are the same, the client determines that the transmission monitoring result is a successful transmission. In step S1052, if the first identification information and the second identification information are different, the client determines that the transmission monitoring result is a failed transmission.
[0040] According to Figure 3 In the illustrated implementation manner, the method for monitoring data transmission between power systems proposed in the present application determines the transmission monitoring result as successful transmission or failed transmission based on the consistency of identification information at the client side of the power system, thereby providing a basis for continuing to operate on the data file based on the transmission monitoring result.
[0041] Figure 4 FIG. 2 is a flow chart of a monitoring method 2000 for data transmission between power systems of a client according to the present application. Figure 4 As shown, method 2000 includes steps S201 to S207, wherein steps S201 to S205 and Figure 2 Steps S101 to S105 are the same as in the above, and will not be repeated here.
[0042] In some specific embodiments, in step S206, the client parses the message body to obtain the path information of the data file. In some specific embodiments, the message body includes the path information of the data file, and the path information includes the transmission path, and the transmission path includes the starting node and the destination node of the data file, as well as the starting directory stored at the starting node and the destination directory stored at the destination node. In some specific embodiments, the starting node is the file server (i.e., the server) that generates the data file, and the starting directory is the directory where the data file is stored on the server. In some specific embodiments, the destination node is the data integration server (i.e., the client) where the data file is to be consumed, and the destination directory is the directory where the data file is stored in the client where the data is to be consumed.
[0043] In some specific embodiments, the message body includes path information of the data file, the path information includes a verification path, the verification path includes a first node and a second node in the current system, wherein the first node is a file server (i.e., a server) that verifies the data file in the current system, and the second node is a data integration server (i.e., a client) that verifies the data file in the current system, and the verification path also includes a first directory stored at the first node and a second directory stored at the second node.
[0044] In some specific embodiments, in step S207, the client determines the transmission scenario of the data file based on the path information. In some specific embodiments, the transmission scenarios include data reception, data transmission across security zones, and data transmission that does not cross security zones. In step S207, the client determines whether the data transmission crosses security zones by whether the security zones where the starting node and the destination node in the transmission path are located are the same. In some specific embodiments, in step S207, the client determines whether the data transmission is data transmission or data reception by verifying whether the first node in the path and the starting node in the transmission path are the same. Optionally, the transmission scenario of the starting node is data reception, and the transmitted data file is a file sent from other power systems to the power system to which the current client belongs. Optionally, the transmission scenario is data transmission, and the transmitted data file is a file sent from the power system to which the current client belongs to other power systems.
[0045] According to Figure 4 In the implementation manner shown, the monitoring method for data transmission between power systems proposed in the present application obtains the transmission scenario of the data file by parsing the message body. In both data reception and data sending scenarios, it can further ensure the security and stability of data transmission based on the transmission monitoring results.
[0046] Figure 5 for Figure 4 Schematic diagram of the process of step S207 in method 2000. Figure 5 As shown, step S207 includes steps S2071 to S2073.
[0047] In some specific embodiments, in step S207, the path information includes a transmission path and a verification path, the verification path includes a first node, and the transmission path includes a start node and a destination node.
[0048] In some specific embodiments, in step S2071, when the starting node is the first node and the security zone where the starting node is located is different from the security zone where the destination node is located, the client determines that the transmission scenario is data transmission across security zones. In some specific embodiments, in step S2072, when the starting node is the first node and the security zone where the starting node is located is the same as the security zone where the destination node is located, the client determines that the transmission scenario is data transmission that does not cross security zones. In some specific embodiments, in step S2073, when the starting node is not the first node, the client determines that the transmission scenario is data reception.
[0049] According to Figure 5 In the embodiment shown, the method proposed in the present application determines whether the data transmission is data sending or data receiving by verifying whether the first node in the path and the starting node in the transmission path are the same, and determines whether the data transmission crosses the security zone by verifying whether the security zone where the starting node and the destination node in the transmission path are located are the same. Figure 5 The method can accurately determine the transmission scenario of data transmission on the client side.
[0050] Figure 6 FIG. 3 is a flow chart of a monitoring method 3000 for data transmission between power systems of a client according to the present application. Figure 6 As shown, method 3000 includes steps S301 to S308, wherein steps S301 to S307 and Figure 4 Steps S201 to S207 are the same as in the above, and will not be repeated here.
[0051] In step S308, when the transmission scenario is data transmission across security zones, the client sends the transmission monitoring result to the isolation device for transmission across security zones. In some specific embodiments, the transmission scenario is data transmission, and the transmitted data file is a file sent from the power system to which the client belongs to other power systems. In this case, the destination system for data transmission and the system to which the client belongs must not belong to the same security zone (see Figure 8 The method 5000 applied to the server is shown in FIG. 5 ). After the client generates the transmission monitoring result, the transmission monitoring result is sent to the isolation device for cross-safety zone transmission. Optionally, the next-door device is a forward isolation device or a reverse isolation device. The forward isolation device is used when the power system in the safety zone with a high safety level transmits a data file to the power system in the safety zone with a low safety level, and the reverse isolation device is used when the power system in the safety zone with a low safety level transmits a data file to the power system in the safety zone with a high safety level.
[0052] According to Figure 6In the implementation manner shown, the monitoring method for data transmission between power systems proposed in the present application monitors the data file transmission process when data is sent across safety zones, and sends the transmission monitoring results to the isolation device, so that the destination system can be aware of the current status of data transmission, thereby ensuring the reliability of data transmission across safety zones.
[0053] Figure 7 FIG. 4 is a flow chart of a monitoring method 4000 for data transmission between power systems of a client according to the present application. Figure 7 As shown, method 4000 includes steps S401 to S409, wherein steps S401 to S407 and Figure 4 Steps S201 to S207 are the same as in the above, and will not be repeated here.
[0054] In some specific embodiments, in step S408, when the transmission scenario is data reception, the client determines whether to consume the data file according to the transmission monitoring result. In some specific embodiments, the transmission scenario is data reception, and the transmitted data file is a file sent by other power systems to the power system to which the client belongs, that is, a file that the client needs to consume.
[0055] In step S409, when the transmission monitoring result is that the transmission is successful, the client consumes the data file. In some specific embodiments, when the transmission monitoring result is that the transmission is successful, the client consumes the received data file, and the consumption process includes editing the data of the current client according to the received data file, controlling the operating status of each device in the current power system, etc.
[0056] According to Figure 7 In the illustrated implementation manner, the monitoring method for data transmission between power systems proposed in the present application consumes data files on the client side when the transmission scenario is data reception and the transmission monitoring result is a successful transmission, thereby ensuring the normal operation of the power system based on the data files transmitted between the power systems.
[0057] Figure 8 FIG. 5 is a flow chart of a monitoring method 5000 for data transmission between power systems applied to a server of the present application. Figure 8 As shown, method 5000 includes steps S501 to S506.
[0058] In some specific embodiments, in step S501, the server parses the data file to be verified to obtain the path information of the data transmission and the first identification information of the data file. Optionally, the server is a file server. In step S501, the server includes one or more data files. Optionally, in step S501, the first identification information is an MD5 code.
[0059] In some specific embodiments, the path information includes a verification path, and the verification path includes a first node and a second node in the current system, wherein the first node is a file server (i.e., a server) that verifies data files in the current system, and the second node is a data integration server (i.e., a client) that verifies data files in the current system, and the verification path also includes a first directory stored at the first node and a second directory stored at the second node.
[0060] In some specific embodiments, the path information includes a transmission path, and the transmission path includes a starting node and a destination node of the data file, as well as a starting directory stored at the starting node and a destination directory stored at the destination node. In some specific embodiments, the starting node is a file server (i.e., a server) that generates data files, and the starting directory is a directory where the data files are stored at the server. In some specific embodiments, the destination node is a data integration server (i.e., a client) where the data files are to be consumed, and the destination directory is a directory where the data files are stored in the client where the data files are to be consumed.
[0061] In step S502, the server determines the transmission scenario of the data transmission based on the path information. In some specific embodiments, in step S502, the server determines whether the data transmission crosses the security zone by whether the security zones where the starting node and the destination node in the transmission path are located are the same. In some specific embodiments, in step S502, the server determines whether the data transmission is data sending or data receiving by verifying whether the first node in the path and the starting node in the transmission path are the same. In some specific embodiments, the transmission scenarios corresponding to the data files include data sending across security zones, data sending that does not cross security zones, and data receiving.
[0062] In some specific embodiments, in step S503, when the transmission scenario is data transmission across security zones, or when the transmission scenario is data reception, the server uploads the data file to the object storage database of the cloud processing platform. In some specific embodiments, the cloud processing platform includes an object storage database, wherein the object storage database is used to store data files. In some specific embodiments, the transmission scenario is data transmission and the data is transmitted across security zones, for example, the power system to which the server belongs is in security zone II, and the power system to be transmitted is in security zone III, and the server uploads the data file to the object storage database.
[0063] In some specific embodiments, in step S504, the server adds the storage path of the data file in the object storage database to the path information. In some specific embodiments, after the server uploads the data file to the object storage database, the cloud processing platform uses object storage technology to store the data file and returns the storage path to the server, and the server adds the storage path to the existing path information.
[0064] In step S505, the server generates a message body according to the path information and the first identification information. In some specific embodiments, in step S506, the server sends the message body to a message queue of the cloud processing platform. In some specific embodiments, the cloud processing platform includes a message queue, wherein the message queue is used to receive a message body corresponding to the data file. The message body includes the path information and the first identification information of the data file.
[0065] According to Figure 8 In the embodiment shown, the monitoring method for data transmission between power systems proposed in the present application utilizes the server to upload the data file to the object storage database of the cloud processing platform when the transmission scenario is data transmission and the data transmission crosses the security zone, or when the transmission scenario is data reception, and upload the message body to the message queue of the cloud processing platform. Figure 8 In the method shown, the server uses the cloud processing platform to store data files and their corresponding identification information when receiving data and sending data across security zones, providing conditions for the client to verify the security of the data files.
[0066] Fig. 9 for Figure 8 Schematic diagram of the process of step S502 in method 5000. Fig. 9 As shown, step S502 includes steps S5021 to S5023.
[0067] In some specific embodiments, in step S502, the path information includes a transmission path and a verification path, the verification path includes a first node, and the transmission path includes a start node and a destination node.
[0068] In some specific embodiments, in step S5021, when the starting node is the first node and the security zone where the starting node is located is different from the security zone where the destination node is located, the server determines that the transmission scenario is data transmission across security zones. In some specific embodiments, in step S5022, when the starting node is the first node and the security zone where the starting node is located is the same as the security zone where the destination node is located, the server determines that the transmission scenario is data transmission that does not cross security zones. In some specific embodiments, in step S5023, when the starting node is not the first node, the server determines that the transmission scenario is data reception.
[0069] According to Fig. 9 In the embodiment shown, the method proposed in the present application determines whether the data transmission is data sending or data receiving by verifying whether the first node in the path and the starting node in the transmission path are the same, and determines whether the data transmission crosses the security zone by verifying whether the security zone where the starting node and the destination node in the transmission path are located are the same. Fig. 9 The method can accurately determine the transmission scenario of data transmission on the server side.
[0070] Fig.10 FIG. 6 is a flow chart of a monitoring method 6000 for data transmission between power systems applied to a server of the present application. Fig.10 As shown, method 6000 includes steps S601 to S603, wherein steps S601 to S602 are Figure 8 Steps S501 and S502 are the same and will not be repeated here.
[0071] In some specific embodiments, in step S603, when the transmission scenario is data transmission that does not cross the security zone, the server sends the data file to the power system where the destination node is located. For example, the starting node corresponding to the data file is the first node, and the starting node and the destination node are both in security zone II, and the transmission scenario is data transmission that does not cross the security zone, in step S603, the server sends the data file to the power system where the destination node is located.
[0072] According to Fig.10 In the illustrated implementation mode, the method proposed in the present application directly sends data files when the transmission scenario is data transmission that does not cross security zones, thereby ensuring efficient data transmission that does not cross security zones.
[0073] Fig.11 FIG. 1 is a schematic diagram of the structure of the monitoring device 100 for data transmission between power systems of the present application. Fig.11 As shown, the device 100 includes a message receiving module 11, a message parsing module 12, a file acquiring module 13, an identification generating module 14 and a result generating module 15.
[0074] In some specific embodiments, the device 100 is a client of the power system. In some specific embodiments, the client is a data integration server. In some specific embodiments, the message receiving module 11 receives a message body corresponding to a data file sent by a cloud processing platform. In some specific embodiments, the message receiving module 11 is a data integration server. The message receiving module 11 includes identification information of a data file related to itself. Optionally, the identification information is a tag. In some specific embodiments, the message receiving module 11 receives a message body corresponding to a data file in a message queue of the cloud processing platform according to the tag of the data file.
[0075] In some specific embodiments, the message parsing module 12 parses the message body to obtain the storage path of the data file in the object storage database of the cloud processing platform and the first identification information of the data file. In some specific embodiments, the message body includes the path information of the data file and the first identification information, and the path information includes the storage path of the data file in the object storage database of the cloud processing platform. Optionally, the first identification information is the MD5 code of the data file.
[0076] In some specific embodiments, the file acquisition module 13 acquires data files from the object storage database according to the storage path. In some specific embodiments, the path information includes a verification path, and the verification path includes a first node and a second node in the current system, wherein the first node is a file server (i.e., a server) that verifies data files in the current system, and the second node is a data integration server (i.e., a client) that verifies data files in the current system, and the verification path also includes a first directory stored in the first node and a second directory stored in the second node. The file acquisition module 13 stores the acquired data files in the second directory.
[0077] In some specific embodiments, the identification generation module 14 generates the second identification information according to the data file. The result generation module 15 generates the transmission monitoring result according to the first identification information and the second identification information. Optionally, the second identification information is an MD5 code generated according to the data file. The result generation module 15 compares the first identification information and the second identification information to generate the transmission monitoring result.
[0078] Fig.12 FIG. 2 is a schematic diagram of the structure of a monitoring system 200 for data transmission between power systems of the present application. Fig.12 As shown, the system 200 includes a server 21 , a cloud platform 22 and a client 23 .
[0079] In some specific embodiments, in the system 200, the server 21 parses the data file to be transmitted, generates a message body according to the data file, uploads it to the message queue 222 of the cloud processing platform, and uploads the data file to the object storage database 221 of the cloud processing platform. In some specific embodiments, in the system 200, the client 23 obtains the data file from the object storage database 221, generates the second identification information according to the data file, obtains the first identification information corresponding to the data file from the message queue 222, and generates the transmission monitoring result by verifying the first identification information and the second identification information.
[0080] According to Fig.12In the implementation manner shown, the method proposed in the present application utilizes the object storage database and message queue in the cloud processing platform to implement verification of data files during data transmission, thereby ensuring data integrity and secure and effective data transmission during data transmission between power systems.
[0081] Fig.13 A schematic diagram of the structure of an electronic device provided in this application.
[0082] See also Fig.13 , Fig.13 An electronic device is provided, comprising a processor and a memory. The memory stores computer instructions, and when the computer instructions are executed by the processor, the processor executes the computer instructions to achieve the following Figure 2-10 The method and refinement scheme shown.
[0083] It should be understood that the above device embodiments are only illustrative, and the device disclosed in the present invention can also be implemented in other ways. For example, the division of units / modules described in the above embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.
[0084] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present invention may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.
[0085] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. If not otherwise specified, the processor or chip may be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. If not otherwise specified, the on-chip cache, the off-chip memory, and the memory may be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory RRAM (Resistive Random Access Memory), a dynamic random access memory DRAM (Dynamic Random Access Memory), a static random access memory SRAM (Static Random-Access Memory), an enhanced dynamic random access memory EDRAM (Enhanced Dynamic Random Access Memory), a high-bandwidth memory HBM (High-Bandwidth Memory), a hybrid memory cube HMC (Hybrid Memory Cube), etc.
[0086] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.
[0087] The present application also provides a non-transitory computer storage medium storing a computer program. When the computer program is executed by a plurality of processors, the processors execute the following Figure 2-10 The method and refinement scheme shown.
[0088] The embodiments of the present application are described in detail above. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application. At the same time, changes or deformations made by those skilled in the art based on the ideas of the present application, the specific implementation methods and the scope of application of the present application, all belong to the scope of protection of the present application. In summary, the content of this specification should not be construed as a limitation on the present application.
Claims
1. A method for monitoring data transmission between power systems, applied to a client, characterized in that: include: receiving a message body corresponding to the data file sent by the cloud processing platform; Parsing the message body to obtain a storage path of the data file in an object storage database of the cloud processing platform and first identification information of the data file; Acquire the data file from the object storage database according to the storage path; generating second identification information according to the data file; A transmission monitoring result is generated according to the first identification information and the second identification information.
2. The method according to claim 1, characterized in that Generating the transmission monitoring result according to the first identification information and the second identification information includes: In a case where the first identification information and the second identification information are the same, determining that the transmission monitoring result is a successful transmission; or, When the first identification information and the second identification information are different, it is determined that the transmission monitoring result is a transmission failure.
3. The method according to claim 2, characterized in that The first identification information and the second identification information are MD5 codes of the data file.
4. The method according to any one of claims 1 to 3, characterized in that: Also includes: Parsing the message body to obtain path information of the data file; A transmission scenario of the data file is determined according to the path information.
5. The method according to claim 4, characterized in that The path information includes a transmission path and a verification path, the verification path includes a first node, the transmission path includes a starting node and a destination node, and determining the transmission scenario of the data transmission according to the path information includes: When the starting node is the first node and the security zone where the starting node is located is different from the security zone where the destination node is located, determining that the transmission scenario is data transmission across security zones; or, When the starting node is the first node and the security zone where the starting node is located is the same as the security zone where the destination node is located, determining that the transmission scenario is data transmission that does not cross security zones; or, When the starting node is not the first node, the transmission scenario is determined to be data reception.
6. The method according to claim 5, characterized in that Also includes: In the case where the transmission scenario is data transmission across security zones, after a transmission monitoring result is generated according to the first identification information and the second identification information, the transmission monitoring result is sent to an isolation device for transmission across security zones.
7. The method according to claim 5, characterized in that Also includes: In the case where the transmission scenario is data reception, after generating a transmission monitoring result according to the first identification information and the second identification information, determining whether to consume the data file according to the transmission monitoring result; or, When the transmission monitoring result is that the transmission is successful, the data file is consumed.
8. A method for monitoring data transmission between power systems, applied to a server, characterized in that: include: Parsing the data file to be verified to obtain the path information of the data transmission and the first identification information of the data file; determining a transmission scenario for the data transmission according to the path information; In the case where the transmission scenario is data transmission across security zones, or in the case where the transmission scenario is data reception, uploading the data file to an object storage database of a cloud processing platform; Adding the storage path of the data file in the object storage database to the path information; Generate a message body according to the path information and the first identification information; The message body is sent to the message queue of the cloud processing platform.
9. The method according to claim 8, characterized in that The path information includes a transmission path and a verification path, the verification path includes a first node, the transmission path includes a starting node and a destination node, and determining the transmission scenario of the data transmission according to the path information includes: When the starting node is the first node and the security zone where the starting node is located is different from the security zone where the destination node is located, determining that the transmission scenario is data transmission across security zones; or, When the starting node is the first node and the security zone where the starting node is located is the same as the security zone where the destination node is located, determining that the transmission scenario is data transmission that does not cross security zones; or, When the starting node is not the first node, the transmission scenario is determined to be data reception.
10. The method according to claim 9, characterized in that After determining a transmission scenario of the data transmission according to the path information, the method further includes: When the transmission scenario is data transmission that does not cross a security zone, the data file is sent to the power system where the destination node is located.
11. A monitoring device for data transmission between power systems, characterized in that: include: A message receiving module, used to receive a message body corresponding to a data file sent by a cloud processing platform; A message parsing module, used to parse the message body to obtain a storage path of the data file in an object storage database of a cloud processing platform and first identification information of the data file; A file acquisition module, used to acquire the data file from the object storage database according to the storage path; An identification generating module, used to generate second identification information according to the data file; A result generating module is used to generate a transmission monitoring result according to the first identification information and the second identification information.
12. A monitoring system for data transmission between power systems, characterized in that: It includes a server, a client and a cloud processing platform, wherein the cloud processing platform includes object storage and a message queue, wherein: The client is used to execute the method according to any one of claims 1 to 7; The server is used to execute the method according to any one of claims 8 to 10; The cloud processing platform is used to receive the data file sent by the server, store the data file in the object storage, and send the data file to the client; The cloud processing platform is also used to receive a message body sent by the server, add the message body to the message queue, and send the message body to the client.
13. An electronic device comprising: processor; A memory storing a computer program, which, when executed by the processor, causes the processor to perform the method according to any one of claims 1 to 10.
14. A non-transitory computer-readable storage medium having computer-readable instructions stored thereon, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 10.