Information interaction method and relay protection fault information system

Abstract

The information interaction method and the relay protection fault information system provided in the application, the method is applied to a client, when data in a relay protection substation system needs to be acquired, a configuration file and a callback interface are generated, the callback interface includes an interface, interface information and a timing time; the callback interface is registered to a container of the client, a route corresponding to the callback interface is injected into a service of the client; a valid time limit of the callback interface is determined, then an encryption method is determined, and a target key is generated according to the encryption method, finally a request with the configuration file, the valid time limit, the interface information and a public key in the target key as a request parameter is generated, and the request is sent to a relay protection master station system; encrypted data returned by the relay protection master station system is received; the encrypted data is decrypted according to a private key. The relay protection master station system does not need to generate a corresponding interface according to different request initiation ends, so that the development cost can be reduced, the resource utilization rate and the security of information interaction can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of power system communication, and in particular to an information interaction method and a relay protection fault information system. BACKGROUND

[0002] The relay protection fault information system refers to a system composed of a relay protection information substation system installed at a station end, a relay protection information master station system installed at a dispatching organization or a district control (centralized control) center, and a power system network and interface equipment for providing information transmission, which is referred to as a relay protection information system. The relay protection information substation system is mainly used to send various information in the station end to the relay protection information master station as required, and the relay protection information master station system is mainly used to receive the information of the relay protection information substation system and analyze and process the information.

[0003] With the popularization of mobile office, the daily operation and maintenance of the relay protection information system is changed from the traditional workstation mode to more flexible cloud office, and thus remote access to the data in the relay protection information system becomes one of the necessary functions of the relay protection information system. Considering that the data request involves cross-district communication, inter-station communication, and intra-station communication, and the system types of the terminals initiating the request to the relay protection information master station system are various, the relay protection information master station needs to generate an interface matched with the client to perform information interaction, which increases the development cost of the system and reduces the resource utilization rate of the relay protection information master station system. SUMMARY

[0004] The present application aims to at least solve one of the above technical defects, in particular, the technical defect that the relay protection information master station needs to generate an interface matched with the client to perform information interaction, which increases the development cost of the system and reduces the resource utilization rate of the relay protection information master station system in the prior art.

[0005] In a first aspect, the present application provides an information interaction method, which is applied to a client and includes:

[0006] When data in the relay protection information substation system needs to be obtained, a configuration file and a callback interface are generated; wherein the callback interface includes an interface, interface information, and a timing time; the timing time starts to be counted from when the callback interface is generated, and is continuously updated until the callback interface is cancelled;

[0007] The callback interface is registered in a container of the client, and a route corresponding to the callback interface is registered in a service of the client; wherein the container of the client is a storage container with a dependency injection function;

[0008] The effective time limit of the callback interface is determined according to the configuration file;

[0009] determining an encryption method, and generating a target key according to the encryption method; wherein the target key comprises a public key and a private key;

[0010] generating a target request with the configuration file, a valid time limit of the callback interface, the interface information, and the public key as request parameters, and sending the target request to a main station system of a trusted service;

[0011] receiving encrypted data returned by the main station system of the trusted service;

[0012] decrypting the encrypted data according to the private key to obtain decrypted data.

[0013] In one of the embodiments, the method further comprises:

[0014] monitoring the timing time of the callback interface in real time;

[0015] if the timing time of the callback interface is not within the valid time limit of the callback interface, removing the callback interface from the container of the client and removing the route corresponding to the callback interface from the service of the client to log out the callback interface.

[0016] In one of the embodiments, the method further comprises:

[0017] determining a proxy class;

[0018] instantiating the proxy class to obtain a dynamic proxy instance;

[0019] obtaining actual interface information according to the configuration file;

[0020] obtaining a callback interface and establishing a corresponding relationship between an actual interface corresponding to the actual interface information and the callback interface; wherein the callback interface is generated by the dynamic proxy instance.

[0021] In one of the embodiments, the method further comprises:

[0022] randomly selecting an encryption method from a preset encryption algorithm library.

[0023] In a second aspect, the application provides an information interaction method, which is applied to a main station system of a trusted service and comprises the following steps:

[0024] receiving a target request initiated by a client, and obtaining a configuration file, interface information, a valid time limit of a callback interface, and a public key contained in the target request;

[0025] determining a target trusted substation according to the configuration file, and forwarding the target request to the target trusted substation;

[0026] receiving response data returned by the target sub-signaling station in a preset time period;

[0027] when the preset time period ends, obtaining a timing time of a callback interface corresponding to the interface information as a second time, and determining whether the second time is within a valid time limit of the callback interface;

[0028] if the second time is within the valid time limit of the callback interface, encrypting target data based on the public key to obtain encrypted data; wherein the target data is all response data received in the preset time period;

[0029] determining a callback interface address corresponding to the interface information, and sending the encrypted data to the client according to the callback interface address;

[0030] obtaining a timing time of a callback interface corresponding to the interface information as a third time;

[0031] if the third time is within the valid time limit of the callback interface, receiving response data returned by the target sub-signaling station in a next preset time period until the timing time of the callback interface corresponding to the interface information is not within the valid time limit of the callback interface.

[0032] In one of the embodiments, the method further comprises:

[0033] if the second time is not within the valid time limit of the callback interface, the callback interface corresponding to the interface information has been invalidated, and alarm information indicating that the request data fails is returned to the client.

[0034] In a third aspect, the application provides an information interaction device, which is applied to a client and comprises:

[0035] a callback interface generation module, configured to generate a configuration file and a callback interface when data in a sub-signaling station system needs to be obtained; wherein the callback interface comprises an interface, interface information and a timing time; the timing time starts to be counted from when the callback interface is generated, and is continuously updated until the callback interface is cancelled;

[0036] a callback interface registration module, configured to register the callback interface to a container of the client, and register a route corresponding to the callback interface to a service of the client; wherein the container of the client is a storage container with a dependency injection function;

[0037] a valid time limit determination module, configured to determine a valid time limit of the callback interface according to the configuration file;

[0038] The encryption method determining module is configured to determine an encryption method and generate a target key according to the encryption method, wherein the target key comprises a public key and a private key;

[0039] The request sending module is configured to generate a target request with the configuration file, the valid time limit of the callback interface, the interface information and the public key as request parameters, and send the target request to the main station system;

[0040] The first data receiving module is configured to receive encrypted data returned by the main station system.

[0041] The data decryption module is configured to decrypt the encrypted data according to the private key to obtain decrypted data.

[0042] In a fourth aspect, the application provides an information interaction device, which is applied to a main station system and comprises:

[0043] The request receiving module is configured to receive a target request initiated by a client, and obtain a configuration file, interface information, a valid time limit of a callback interface and a public key contained in the target request.

[0044] The request forwarding module is configured to determine a target sub-station according to the configuration file, and forward the target request to the target sub-station.

[0045] The second data receiving module is configured to receive response data returned by the target sub-station within a preset time period.

[0046] The time limit judging module is configured to obtain a timing time of a callback interface corresponding to the interface information as a second time when the preset time period ends, and judge whether the second time is within the valid time limit of the callback interface.

[0047] The data encryption module is configured to encrypt target data based on the public key to obtain encrypted data if the second time is within the valid time limit of the callback interface, wherein the target data is all the response data received within the preset time period.

[0048] The data returning module is configured to determine a callback interface address corresponding to the interface information, and send the encrypted data to the client according to the callback interface address.

[0049] The time obtaining module is configured to obtain a timing time of a callback interface corresponding to the interface information as a third time.

[0050] The third data receiving module is used to receive response data returned by the target information protection substation in the next preset time period if the third time is within the valid time limit of the callback interface, until the time of the callback interface corresponding to the obtained interface information is not within the valid time limit of the callback interface.

[0051] Fifthly, this application provides a storage medium storing computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of the information interaction method as described in any of the above embodiments.

[0052] Sixthly, this application provides a relay protection fault information system, the system comprising: a relay protection master station system and a relay protection substation system;

[0053] The main station system for information security is installed at the dispatching agency or regional control center to receive information sent by the substations for information security, and to process and analyze it.

[0054] The Baoxin substation system is installed at the plant site and is used to complete protocol conversion and information collection. It is also used to send information related to various devices in the plant site to the Baoxin master station system.

[0055] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0056] The information interaction method provided in this application is applied to a client. When data needs to be obtained from the Baoxin substation system, a configuration file and a callback interface are generated. The callback interface includes an interface, interface information, and a timeout period. The callback interface is registered in the client's container, and the route corresponding to the callback interface is injected into the client's service. Based on the configuration file, the validity period of the callback interface is determined, and then the encryption method is determined. Based on the encryption method, a target key is generated, which includes a public key and a private key. Finally, a target request is generated with the configuration file, the validity period of the callback interface, the interface information, and the public key as request parameters, and the target request is sent to the Baoxin mainstation system. The encrypted data returned by the Baoxin mainstation system is received. Based on the private key, the encrypted data is decrypted to obtain the decrypted data. The client generates the callback interface and uses it as a parameter to initiate a request to the Baoxin system. The Baoxin mainstation system does not need to generate corresponding interfaces for different request initiators to complete the information interaction, thus reducing the development cost of the Baoxin mainstation system and improving its resource utilization. Simultaneously, generating the target key enables the Baoxin mainstation system to encrypt the response data, improving the security of information interaction. Attached Figure Description

[0057] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the accompanying drawings in the following description only constitute some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0058] Figure 1 A flowchart of a method for information interaction applied to a client according to an embodiment of the present application is provided.

[0059] Figure 2 A flowchart of a method for information interaction applied to a client according to an embodiment of the present application is provided.

[0060] Figure 3 A flowchart of a method for information interaction applied to a client according to an embodiment of the present application is provided.

[0061] Figure 4 A flowchart of a method for information interaction applied to a client according to an embodiment of the present application is provided.

[0062] Figure 5 A flowchart of a method for information interaction applied to a client according to an embodiment of the present application is provided.

[0063] Figure 6 A flowchart of a method for information interaction applied to a client according to an embodiment of the present application is provided. DETAILED DESCRIPTION

[0064] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0065] In one of the embodiments, the present application provides a method for information interaction, and the following embodiments are described by taking the method applied to a client. It can be understood that the client performing the method for information interaction can be a client of a relay protection fault information system, or a client of other third party, which is not specifically limited by the present application.

[0066] As shown in Figure 1 The present application provides a method for information interaction, which is applied to a client, and includes:

[0067] Step S101: When data in a relay protection substation system needs to be acquired, a configuration file and a callback interface are generated.

[0068] The callback interface includes an interface, interface information, and a timing time; the timing time starts timing from when the callback interface is generated and continuously updates until the callback interface is unregistered; and the information in the configuration file includes, but is not limited to, at least one sub-station identifier and a data type to be acquired corresponding to each sub-station identifier.

[0069] The sub-station system is a component of the relay protection fault information system, is installed at the station end, has functions of collecting real-time operation conditions, configuration information, and fault information of devices such as relay protection devices and fault recording devices, and monitoring and analyzing the operation states of the devices, through the sub-station system, state quantity information, analog quantity information, fault recording data, and the like of each device can be acquired, and setting values and setting value area numbers of a certain device in the sub-station system can be queried or modified, wherein the setting value can be understood as a certain value in the power system, when a physical quantity reaches the corresponding setting value, a corresponding operation will be performed.

[0070] Step S102: register the callback interface to the container of the client, and register the route corresponding to the callback interface to the service of the client.

[0071] The container of the client is a storage container with a dependency injection function.

[0072] It can be understood that the callback interface is registered to the container of the client, so that when the sub-station system receives the interface information of the callback interface and determines the corresponding callback interface, the response data can be returned to the client through the callback interface. The purpose of registering the route corresponding to the callback interface to the service of the client is to realize the mapping between the callback interface and the controller of the client.

[0073] Step S103: determine the effective time limit of the callback interface according to the configuration file.

[0074] The effective time limit of the callback interface is the effective period of the callback interface, once the timing time of the callback interface exceeds the effective time limit corresponding thereto, the callback interface will be invalid, and data transmission cannot be performed through the callback interface.

[0075] Specifically, the effective time limit of the callback interface can be determined according to the data type to be acquired corresponding to each sub-station identifier included in the configuration file through a model or an algorithm, or can be input by a developer to generate a configuration file including the effective time limit of the callback interface, which is not limited in the present application.

[0076] Step S104: determine an encryption method, and generate a target key according to the encryption method.

[0077] The target key includes a public key and a private key, the target key is a key pair, the public key is a non-secret half in the key pair, and when the key pair is used, if one key is used to encrypt a piece of data, the other key must be used for decryption, that is, the ciphertext encrypted by the public key can only be decrypted by the corresponding private key.

[0078] Step S105: generating a target request taking the configuration file, the valid time limit of the callback interface, the interface information, and the public key as request parameters, and sending the target request to the protection main station system.

[0079] The protection main station system is a component of a relay protection fault information system, is installed in a dispatching mechanism or a district control (centralized control) center, interacts with the protection substation system, and processes, analyzes, publishes, and the like the obtained information.

[0080] Step S106: receiving encrypted data returned by the protection main station system.

[0081] Step S107: decrypting the encrypted data according to the private key to obtain decrypted data.

[0082] The information interaction method provided in the application is applied to a client, when data in a protection substation system needs to be obtained, a configuration file and a callback interface are generated, the callback interface includes an interface, interface information, and a timing time; the callback interface is registered to a container of the client, and a route corresponding to the callback interface is injected into a service of the client; the valid time limit of the callback interface is determined according to the configuration file, and then an encryption method is determined, and a target key is generated according to the encryption method, and the target key includes a public key and a private key; finally, a target request taking the configuration file, the valid time limit of the callback interface, the interface information, and the public key as request parameters is generated, and the target request is sent to the protection main station system; encrypted data returned by the protection main station system is received; and the encrypted data is decrypted according to the private key to obtain decrypted data. The callback interface is generated by the client, the callback interface is used as a parameter to initiate a request to the protection system, the protection main station system does not need to generate a corresponding interface according to different request initiation ends to complete information interaction, so that the development cost of the protection main station system can be reduced, the resource utilization rate of the protection main station system is improved, meanwhile, the target key is generated to enable the protection main station system to encrypt response data, and the security of information interaction can be improved.

[0083] As shown in FIG. 1, Figure 2 the information interaction method further includes:

[0084] Step S201: monitoring the timing time of the callback interface in real time.

[0085] Since the callback interface will be unregistered when the timing time of the callback interface exceeds the valid time limit of the callback interface, the timing time of the callback interface needs to be monitored in real time.

[0086] Step S202: If the timing time of the callback interface is not within the valid time limit of the callback interface, the callback interface is removed from the container of the client, and the route corresponding to the callback interface is removed from the service of the client, so as to unregister the callback interface.

[0087] It can be understood that by monitoring the timing time of the callback interface, the callback interface is unregistered after exceeding the valid time limit of the callback interface, that is, the callback interface will not be valid for a long time, and therefore the security of information interaction between the client and the trust system can be further improved.

[0088] As shown in FIG. 1, Figure 3 In one embodiment, the callback interface is generated, including:

[0089] Step S301: Determine the proxy class.

[0090] Step S302: The proxy class is instantiated to obtain a dynamic proxy instance.

[0091] Step S303: According to the configuration file, the actual interface information is obtained.

[0092] Step S304: The callback interface is obtained, and the corresponding relationship between the actual interface corresponding to the actual interface information and the callback interface is established.

[0093] The callback interface is generated by the dynamic proxy instance, and the dynamic proxy instance generates the interface domain name disclosed by the trust master station system when generating the callback interface.

[0094] The corresponding relationship between the callback interface and the actual interface corresponding to the actual interface information is established, so that when the callback interface is called, the data obtained finally can be returned to the actual interface.

[0095] For example, assuming that one of the interfaces disclosed by the trust master station system is http: / / master / requestSetting, at this time, the third-party client A wants to obtain the data of the trust substation system, and the callback interface generated by the third-party client A can be http: / / A / requestSettingCallback1234.

[0096] It can be understood that the client generates a callback interface according to the interface domain name disclosed by the main station system of the trust station, and returns the interface information of the callback interface to the main station system of the trust station. Therefore, when the main station system of the trust station interacts with the client, it is not necessary to generate an interface matching the client according to the differences between the clients every time, thereby saving the development cost of the trust system and improving the resource utilization rate.

[0097] In one of the embodiments, the encryption method is determined, including:

[0098] Randomly selecting an encryption method from a preset encryption algorithm library.

[0099] The encryption methods in the encryption algorithm library are all asymmetric encryption methods, including but not limited to RAS, Elgamal, knapsack encryption algorithm, Rabin algorithm, D-H algorithm, and ECC (Elliptic Curve Cryptography).

[0100] It can be understood that the encryption method is randomly selected from the encryption algorithm library, in other words, the encryption method used by the client and the main station system of the trust station when they interact with each other every time may not be consistent, thereby increasing the difficulty of cracking and further improving the security of information interaction between the trust system and the client.

[0101] In one of the embodiments, the application provides an information interaction method, and the following embodiments are described with the method applied to the main station system of the trust station.

[0102] As shown in Figure 4 The application provides an information interaction method, which is applied to the main station system of the trust station, including:

[0103] Step S401: receiving a target request initiated by a client, and obtaining a configuration file, interface information, a valid time limit of a callback interface, and a public key contained in the target request.

[0104] Step S402: determining a target trust substation according to the configuration file, and forwarding the target request to the target trust substation.

[0105] The configuration file includes at least one trust substation identifier, and the target trust substation can be determined according to the trust substation identifier. The target request is forwarded to the target trust substation to trigger the target trust substation to collect data conforming to the target request, and then returned to the main station system of the trust station.

[0106] Specifically, the target request is forwarded to the target trust substation, and the target trust substation will first perform a reduction conversion on the target request. The reduction conversion follows the Southern Power Grid Relay Protection 103 protocol or the 61850 communication protocol.

[0107] Step S403: receiving the response data returned by the target trusted sub-station within a preset time period.

[0108] The response data is data returned by the target trusted sub-station in response to the target request.

[0109] Step S404: when the preset time period ends, obtaining the timing time of the callback interface corresponding to the interface information as a second time, and determining whether the second time is within the valid time limit of the callback interface.

[0110] Step S405: if the second time is within the valid time limit of the callback interface, encrypting the target data based on the public key to obtain encrypted data.

[0111] The target data is all response data received within the preset time period.

[0112] Step S406: determining the callback interface address corresponding to the interface information, and sending the encrypted data to the client according to the callback interface address.

[0113] Specifically, since the target trusted sub-station returns the response data may be delayed, the response data received within a preset time period can be sent to the client first, and the response data of the target trusted sub-station within the next preset time period is continuously received until the callback interface is invalid, under the condition that the callback interface is not invalid.

[0114] Step S407: obtaining the timing time of the callback interface corresponding to the interface information as a third time.

[0115] Step S408: if the third time is within the valid time limit of the callback interface, receiving the response data returned by the target trusted sub-station within the next preset time period until the timing time of the callback interface corresponding to the interface information is not within the valid time limit of the callback interface.

[0116] It can be understood that if the third time is not within the valid time limit of the callback interface, the reception of the response data returned by the target trusted sub-station within the next preset time period is stopped. At this time, there are two cases, one is that the trusted main station system has received all the data matched with the configuration file, and the other is that there is a delay in the return data of some target trusted sub-station, resulting in that the trusted main station system only obtains part of the data. In this case, alarm information indicating that the data acquisition is incomplete can be returned to the client to remind the R&D personnel to adjust the valid time limit of the callback interface generated next time to reacquire the required data.

[0117] Exemplarily, it is assumed that both the trusted sub-station A and the trusted sub-station B are target trusted sub-stations, the data a and the data b need to be acquired in the trusted sub-station A, and the data c and the data d need to be acquired in the trusted sub-station B, when the target request is forwarded to the trusted sub-station A and the trusted sub-station B, because there is a delay in the process of collecting the data b, therefore, the trusted sub-station A only collects the data a as the response data and returns to the trusted master station system, and the trusted sub-station B collects the data c and the data d as the response data and returns to the trusted master station system, at this time, a preset time period ends, the acquired target data (the data a, the data c and the data d) is sent to the client, it is assumed that the callback interface is not invalid at this time, after the trusted sub-station A collects the data b, the data b is returned to the trusted master station system as the response data, and the trusted master station system sends the acquired target data (the data b) to the client.

[0118] Step S409: If the second time is not within the valid time limit of the callback interface, the callback interface corresponding to the interface information has been invalid, and the alarm information indicating that the request data fails is returned to the client.

[0119] The information interaction method provided in the application is applied to the trusted master station system, receives the target request initiated by the client, acquires the configuration file, the interface information, the valid time limit of the callback interface and the public key contained in the target request, determines the target trusted sub-station according to the configuration file, forwards the target request to the target trusted sub-station, receives the response data returned by the target trusted sub-station within a preset time period, when the preset time period ends, acquires the timing time of the callback interface corresponding to the interface information as the second time, judges whether the second time is within the valid time limit of the callback interface, if the second time is within the valid time limit of the callback interface, encrypts the target data based on the public key to obtain the encrypted data, wherein the target data is all the response data received within the preset time period, determines the callback interface address corresponding to the interface information, and sends the encrypted data to the client according to the callback interface address, acquires the timing time of the callback interface corresponding to the interface information as the third time, if the third time is within the valid time limit of the callback interface, receives the response data returned by the target trusted sub-station within the next preset time period, until the timing time of the callback interface corresponding to the interface information is not within the valid time limit of the callback interface. The trusted master station system only needs to forward the request to the target trusted sub-station, receive the data of the target trusted sub-station, encrypt the obtained response data using the public key transmitted by the client, and finally send the encrypted data to the client according to the interface information. The trusted master station system does not need to generate different interfaces according to different request initiation ends, and send the data to the initiation end through the interface, thereby saving the development cost of the trusted master station system, and using the asymmetric encryption method to encrypt the interaction information between the request initiation end and the trusted system can improve the security of information interaction.

[0120] It should be understood that, although each step in the flowchart involved in each embodiment as described above is shown in sequence according to the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless explicitly stated herein, there is no strict order limitation for the execution of these steps, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart involved in each embodiment as described above can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be alternately executed with at least part of other steps or steps or stages in other steps.

[0121] The information interaction device provided by the embodiments of the present application is described below. The information interaction device described below can be correspondingly referred to the information interaction method described above.

[0122] As shown in Figure 5 The present application provides an information interaction device 500, which is applied to a client and includes:

[0123] The callback interface generation module 501 is configured to generate a configuration file and a callback interface when data in the trusted substation system needs to be acquired. The callback interface includes an interface, interface information, and a timing time. The timing time starts timing from when the callback interface is generated and is continuously updated until the callback interface is cancelled.

[0124] The callback interface registration module 502 is configured to register the callback interface to a container of the client and register a route corresponding to the callback interface to a service of the client. The container of the client is a storage container with a dependency injection function.

[0125] The effective time limit determination module 503 is configured to determine an effective time limit of the callback interface according to the configuration file.

[0126] The encryption method determination module 504 is configured to determine an encryption method and generate a target key according to the encryption method. The target key includes a public key and a private key.

[0127] The request sending module 505 is configured to generate a target request with the configuration file, the effective time limit of the callback interface, the interface information, and the public key as request parameters and send the target request to the trusted master station system.

[0128] The first data receiving module 506 is configured to receive encrypted data returned by the trusted master station system.

[0129] The data decryption module 507 is configured to decrypt the encrypted data according to the private key to obtain decrypted data.

[0130] In one of the embodiments, the information interaction device further comprises:

[0131] The monitoring module is configured to monitor the timing time of the callback interface in real time.

[0132] The callback interface unregistration module is configured to remove the callback interface from the container of the client and remove the corresponding route of the callback interface from the service of the client to unregister the callback interface if the timing time of the callback interface is not within the valid time limit of the callback interface.

[0133] In one of the embodiments, the callback interface generation module comprises:

[0134] The determination submodule is configured to determine the proxy class.

[0135] The instantiation submodule is configured to instantiate the proxy class to obtain the dynamic proxy instance.

[0136] The first acquisition submodule is configured to acquire the actual interface information according to the configuration file.

[0137] The second acquisition submodule is configured to acquire the callback interface and establish a corresponding relationship between the actual interface corresponding to the actual interface information and the callback interface, wherein the callback interface is generated by the dynamic proxy instance.

[0138] In one of the embodiments, the encryption method determination module comprises:

[0139] The encryption method selection submodule is configured to randomly select an encryption method from a preset encryption algorithm library.

[0140] As shown in Figure 6 The present application provides an information interaction device 600, which is applied to a main station system of a trust center and comprises:

[0141] The request receiving module 601 is configured to receive a target request initiated by a client, acquire a configuration file, interface information, a valid time limit of a callback interface and a public key contained in the target request.

[0142] The request forwarding module 602 is configured to determine a target trust center substation according to the configuration file and forward the target request to the target trust center substation.

[0143] The second data receiving module 603 is configured to receive response data returned by the target trust center substation within a preset time period.

[0144] The time limit determining module 604 is configured to acquire a timing time of the callback interface corresponding to the interface information as a second time when the preset time period ends and determine whether the second time is within the valid time limit of the callback interface.

[0145] The data encryption module 605 is configured to encrypt the target data based on the public key to obtain encrypted data if the second time is within the valid time limit of the callback interface.

[0146] The data return module 606 is configured to determine the callback interface address corresponding to the interface information, and send the encrypted data to the client according to the callback interface address.

[0147] The time acquisition module 607 is configured to acquire the timing time of the callback interface corresponding to the interface information as the third time.

[0148] The third data receiving module 608 is configured to receive the response data returned by the target repeater station in the next preset time period if the third time is within the valid time limit of the callback interface, until the timing time of the callback interface corresponding to the interface information is not within the valid time limit of the callback interface.

[0149] In one of the embodiments, the information interaction apparatus further comprises:

[0150] The alarm information return module is configured to return alarm information indicating that the request data fails to the client if the second time is not within the valid time limit of the callback interface.

[0151] It can be understood that the client and the repeater master station system both belong to a kind of computer equipment, in addition, the computer equipment can include server, repeater substation system, repeater system, third party system and the like, the division of each module in the above information interaction apparatus is only used for example, in other embodiments, the information interaction apparatus can be divided into different modules as needed to complete all or part of the functions of the above information interaction apparatus. Each module in the above information interaction apparatus can be realized by software, hardware and their combinations in whole or in part. The above each module can be embedded in or independent of the processor in the computer equipment in hardware form, or can be stored in the memory in the computer equipment in software form, so as to call and execute the operations corresponding to each module by the processor.

[0152] In one embodiment, the present application further provides a storage medium, wherein the storage medium stores computer readable instructions, and the computer readable instructions are executed by one or more processors to enable the one or more processors to perform the steps of the information interaction method in any of the above embodiments.

[0153] In one embodiment, the application further provides a relay protection fault information system, which comprises a relay protection master station system and a relay protection substation system; the relay protection master station system is installed in a dispatching mechanism or a district control center, and is used for receiving information sent by the relay protection substation and processing and analyzing the information; the relay protection substation system is installed in a station end, and is used for completing protocol conversion and information collection, and further used for sending information related to each device in the station end to the relay protection master station system.

[0154] Finally, it should be noted that the terminology used herein, such as first and second, merely for the purpose of distinguishing one entity or action from another, and is not necessarily intended to denote any such actual relationship or order between such entities or actions. Moreover, the terms "comprises" and / or "comprising," or "includes" and / or "including" when used in this specification, specify the presence of stated features, integers, steps, operations, elements, or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof. The terms "a" or "an", as used herein, mean "one or more" unless the context clearly dictates otherwise. As used herein, the term "includes" and / or "including," as well as "containing" and / or "containing," means the inclusion of at least the recited item or list of items, but does not exclude the inclusion of other items or lists of items. The term "or" as used herein means any one member of a logical disjunction received with respect to another member.

[0155] The various embodiments described in the specification are presented for the purpose of illustration and description. Each of the embodiments highlights a different aspect of the application, and the embodiments can be combined according to the needs of the application. The same reference numerals in different embodiments designate the same or similar elements.

[0156] The above description of disclosed embodiments provides those skilled in the art with enough information to implement or use the application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the application. Therefore, the application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An information exchange method, characterized in that, The method is applied to the client and includes: When data needs to be retrieved from the Baoxin substation system, a configuration file and a callback interface are generated; wherein, the callback interface includes an interface, interface information and a timer; the timer starts counting from the time the callback interface is generated and is continuously updated until the callback interface is deregistered; The callback interface is registered in the client's container, and the route corresponding to the callback interface is registered in the client's service; wherein, the client's container is a storage container with dependency injection functionality; The validity period of the callback interface is determined according to the configuration file. Determine an encryption method, and generate a target key based on the encryption method; wherein the target key includes a public key and a private key; Generate a target request with the configuration file, the validity period of the callback interface, the interface information, and the public key as request parameters, and send the target request to the Baoxin main station system; Receive encrypted data returned by the security master station system; The encrypted data is decrypted using the private key to obtain the decrypted data.

2. The information interaction method according to claim 1, characterized in that, The method further includes: The timing of the callback interface is monitored in real time; If the timing of the callback interface is not within the valid time limit of the callback interface, the callback interface is removed from the container of the client, and the route corresponding to the callback interface is removed from the service of the client to cancel the callback interface.

3. The information interaction method according to claim 1, characterized in that, The callback generation interface includes: Determine the proxy class; The proxy class is instantiated to obtain a dynamic proxy instance; According to the configuration file, obtain the actual interface information; Obtain the callback interface and establish the correspondence between the actual interface corresponding to the actual interface information and the callback interface; wherein the callback interface is generated by the dynamic proxy instance.

4. The information interaction method according to claim 1, characterized in that, The method for determining encryption includes: Randomly select an encryption method from a pre-set encryption algorithm library.

5. An information exchange method, characterized in that, The method is applied to the Baoxin master station system, including: Receive the target request initiated by the client, and obtain the configuration file, interface information, validity period of the callback interface and public key contained in the target request; Based on the configuration file, the target information protection substation is determined, and the target request is forwarded to the target information protection substation; Receive response data returned by the target information security substation within a preset time period; When the preset time period ends, the timing time of the callback interface corresponding to the interface information is obtained as the second time, and it is determined whether the second time is within the valid time limit of the callback interface. If the second time is within the valid time limit of the callback interface, the target data is encrypted based on the public key to obtain encrypted data; wherein, the target data is all response data received within the preset time period; Determine the callback interface address corresponding to the interface information, and send the encrypted data to the client according to the callback interface address; Obtain the timing of the callback interface corresponding to the interface information as the third time; If the third time is within the valid time limit of the callback interface, the response data returned by the target information protection substation in the next preset time period is received until the time of the callback interface corresponding to the obtained interface information is not within the valid time limit of the callback interface.

6. The information interaction method according to claim 5, characterized in that, The method further includes: If the second time is not within the valid time limit of the callback interface, the callback interface corresponding to the interface information has expired, and an alarm message indicating that the data request failed is returned to the client.

7. An information interaction device, characterized in that, The device is applied to a client and includes: The callback interface generation module is used to generate configuration files and callback interfaces when data needs to be obtained from the Baoxin substation system. The callback interface includes an interface, interface information, and a timing period. The timing period starts when the callback interface is generated and is continuously updated until the callback interface is deregistered. A callback interface registration module is used to register the callback interface to the container of the client and register the route corresponding to the callback interface to the service of the client; wherein, the container of the client is a storage container with dependency injection function; The effective time limit determination module is used to determine the effective time limit of the callback interface based on the configuration file. An encryption method determination module is used to determine an encryption method and generate a target key based on the encryption method; wherein the target key includes a public key and a private key; The request sending module is used to generate a target request with the configuration file, the validity period of the callback interface, the interface information and the public key as request parameters, and send the target request to the security master station system; The data receiving module is used to receive encrypted data returned by the security master station system; The data decryption module is used to decrypt the encrypted data based on the private key to obtain the decrypted data.

8. An information interaction device, characterized in that, The device is applied to the information security master station system and includes: The request receiving module is used to receive the target request initiated by the client and obtain the configuration file, interface information, validity period of the callback interface and public key contained in the target request; The request forwarding module is used to determine the target information protection substation according to the configuration file and forward the target request to the target information protection substation; The first data receiving module is used to receive response data returned by the target information security substation within a preset time period; The time limit determination module is used to obtain the timing time of the callback interface corresponding to the interface information as the second time when the preset time period ends, and determine whether the second time is within the valid time limit of the callback interface. The data encryption module is used to encrypt the target data based on the public key to obtain encrypted data if the second time is within the valid time limit of the callback interface; wherein the target data is all response data received within the preset time period; The data return module is used to determine the callback interface address corresponding to the interface information, and send the encrypted data to the client according to the callback interface address; The time acquisition module is used to acquire the timing time of the callback interface corresponding to the interface information as the third time; The second data receiving module is used to receive response data returned by the target information protection substation in the next preset time period if the third time is within the valid time limit of the callback interface, until the time of the callback interface corresponding to the obtained interface information is not within the valid time limit of the callback interface.

9. A storage medium, characterized in that: The storage medium stores computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of the information interaction method as described in any one of claims 1 to 6.

10. A relay protection fault information system, characterized in that, The system includes: the Baoxin main station system and the Baoxin substation system; The information security master station system is installed in the dispatching agency or the regional control center and is used to execute the steps of the information interaction method as described in claim 5 or 6. The Baoxin substation system is installed at the plant site and is used to complete protocol conversion and information collection. It is also used to send information related to various devices in the plant site to the Baoxin master station system.

Images