Client Entry ID processing method and system

Abstract

The invention relates to a client Entry ID processing method and system, and belongs to the field of intelligent substation communication control. According to the invention, processing methods are respectively and correspondingly formulated according to two conditions of disconnection between the client and the server. The method comprises the following steps of: when the client is disconnected and reconnected with a server due to initialization of the client, reading a current corresponding Entry ID from the server and then writing the Entry ID into a corresponding datagram because the server runs normally all the time and a real-time Entry ID does not exist in a memory of the client when the client is initialized; when the client is passively disconnected and reconnected with the server due to the network or the server, the real-time Entry ID in the internal memory of the client is directly written into the corresponding datagram because the client runs normally all the time. According to the invention, the client writes the corresponding Entry ID into the datagram according to different conditions, so that the consistency of the Entry ID of the client and the Entry ID of the server is effectively ensured.

Description

Technical Field

[0001] The present invention relates to a client EntryID processing method and system, and belongs to the field of intelligent substation communication control. Background Art

[0002] 8.1.3.5 of the DL / T860.81 specification defines the entry identifier (EntryID), which is mapped to the MMS (Manufacturing Message Specification) as a fixed-length octet string consisting of 8 octets, and its reserved value is 0. However, there is no specific description of the usage of the entry identifier (EntryID).

[0003] In the current smart substation, EntryID is used to record the number of reports sent by the buffer report control block (BRCB) to the IEC61850 server (hereinafter referred to as the server), and it is accumulated in sequence as the number of reports received increases. Whether it is the IEC61850 client (hereinafter referred to as the client) or the server, the EntryID value of each buffer report control block must be recorded. The purpose is to enable the client and the server to restart sending reports from the last EntryID before the interruption of both parties when the communication between the two parties resumes normal after a network anomaly, client failure or server failure occurs, so that the communication between the two parties can continue in the state before the interruption. In this way, the repeated sending of previously sent reports is avoided, and the newly generated reports during the interruption process are not lost.

[0004] However, during the actual communication between the client and the server, after the communication between the two parties is disconnected due to various reasons, when the two parties re-establish the communication connection, the EntryID of the two parties may be inconsistent. For example, before the two parties disconnect, the server sends a datagram with EntryID 9 of a cache report control block to the client (at this time, the EntryID of the cache report control block on the client is 8). Under normal circumstances, the client modifies the EntryID to 9 after receiving this message, but due to communication quality reasons, the client cannot receive this message, and the two parties are disconnected. Therefore, after the two parties re-establish the connection, the EntryID of the server is 9 and the EntryID of the client is 8. At this time, when the client writes EntryID to the server again, the server is likely to report a data error, resulting in the sending of historical signals to the master station. When this happens, it causes certain interference to the safe operation of the smart substation and the monitoring panel (monitoring the operating status of related power equipment) on the dispatching side, and also leads to a waste of manpower and material resources. Summary of the invention

[0005] The purpose of the present invention is to provide a client EntryID processing method and system to solve the problem that the EntryIDs of both parties are inconsistent when the client writes the EntryID to the server after the client and the server establish a connection.

[0006] To achieve the above object, the solution of the present invention includes: A client EntryID processing method of the present invention includes a client initialization processing method and / or a disconnection processing method; The client initialization processing method includes: when the client is initialized, reading the current first server EntryID of the corresponding cache report control block from the server, and when it is necessary to send a datagram containing the EntryID to the server, writing the read first server EntryID into the datagram; The disconnection processing method includes: after the client passively disconnects from the server and re-establishes the connection, when it needs to send a datagram to the server, the real-time EntryID of the corresponding cache report control block stored in the client is written into the datagram; EntryID is an entry identifier in the IEC61850 protocol.

[0007] Furthermore, the client initialization processing method further includes: when the first server EntryID is not read from the server and a datagram needs to be sent to the server, writing the first persistent EntryID of the corresponding cache report control block persistently stored in the client into the datagram.

[0008] Furthermore, the disconnection processing method further includes: when writing the real-time EntryID fails, writing the second persistent EntryID of the corresponding cache report control block persistently stored in itself into the datagram.

[0009] Furthermore, the disconnection processing method also includes: when writing the second persistent EntryID fails, reading the current second server EntryID of the corresponding cache report control block from the server, and when it is necessary to send a datagram containing the EntryID to the server, writing the read second server EntryID into the datagram.

[0010] A client EntryID processing system includes a processor, the processor executing a computer program to implement the steps of a client initialization processing method and / or a disconnection processing method; The client initialization processing method includes: when the client is initialized, reading the current first server EntryID of the corresponding cache report control block from the server, and when it is necessary to send a datagram containing the EntryID to the server, writing the read first server EntryID into the datagram; The disconnection processing method includes: after the client passively disconnects from the server and re-establishes the connection, when it needs to send a datagram to the server, the real-time EntryID of the corresponding cache report control block stored in the client is written into the datagram; EntryID is an entry identifier in the IEC61850 protocol.

[0011] Furthermore, the client initialization processing method further includes: when the first server EntryID is not read from the server and a datagram needs to be sent to the server, writing the first persistent EntryID of the corresponding cache report control block persistently stored in the client into the datagram.

[0012] Furthermore, the disconnection processing method further includes: when writing the real-time EntryID fails, writing the second persistent EntryID of the corresponding cache report control block persistently stored in itself into the datagram.

[0013] Furthermore, the disconnection processing method also includes: when writing the second persistent EntryID fails, reading the current second server EntryID of the corresponding cache report control block from the server, and when it is necessary to send a datagram containing the EntryID to the server, writing the read second server EntryID into the datagram.

[0014] The beneficial effects of the present invention are as follows: the present invention is a pioneering invention, and the present invention has formulated corresponding processing methods according to the two situations in which the client is disconnected from the server. When the client is disconnected from the server due to initialization and then reconnected, because the server has been operating normally and the client does not have a real-time EntryID in its memory during initialization, the current corresponding EntryID is read from the server, and then this EntryID is written into the corresponding datagram; when the client is passively disconnected from the server due to network or server reasons and then reconnected, because the client has been operating normally, the real-time EntryID in its own memory is directly written into the corresponding datagram. The client of the present invention writes the corresponding EntryID into the datagram according to different situations, which effectively ensures the consistency of the client EntryID and the server EntryID. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a schematic diagram of the processing flow after the client is initialized in the present invention; Figure 2 It is a schematic diagram of the processing flow after the client of the present invention passively reconnects with the server. DETAILED DESCRIPTION

[0016] In order to make the purpose, technical solutions and advantages of the present invention more clear, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0017] The idea of ​​the present invention is that the client generally needs to re-establish a connection with the server in the following two situations. The first is that the client restarts and initializes, and the network and the server are in normal operation; the second is that the client is disconnected and reconnected due to various reasons of the network and / or the server, and the client is always in normal operation. The present invention proposes different processing methods according to these two situations, and the sources of the client's EntryID are divided into three types: one is read from the server; the second is the real-time EntryID stored in the client's memory during runtime; the third is the EntryID that the client itself stores periodically and persistently, and the periodically stored EntryID comes from the real-time EntryID.

[0018] When the first situation occurs, that is, when the client is initialized, there is no real-time EntryID in its memory, and since the server has been running normally, the EntryID of the server is used as the basis, so the EntryID of the server is read, and then the EntryID read from the server is written into the datagram and sent to the server.

[0019] When the second situation occurs, that is, the client is passively disconnected from the server, since the client has been running normally, after re-establishing the connection, it reads the real-time EntryID in its own memory, and then writes the read real-time EntryID into a datagram and sends it to the server.

[0020] Method Example: This embodiment provides a method for processing EntryID of a client. In view of the above two situations, the present invention proposes two processing methods. The first processing method (client initialization processing method) is as follows: Figure 1 As shown. Client restart mainly includes power-on restart, configuration change restart, fault restart, etc. It can be a hard restart or a soft restart. During the restart process, it will establish a connection with the server again and summon all the telemetry and telesignaling data of the server. Therefore, the client restart process is also its initialization process, which is the process of creating real-time data of the client from scratch. During the process of establishing its own basic data status, the client is not allowed to establish a connection with the master station and send data, so as to prevent the wrong data from being sent to the master station.

[0021] When the client is initialized, because there is no real-time EntryID of the cache report control block in its memory, it calls the read service (GetBRCBValues) to read the current EntryID (first server EntryID) corresponding to the corresponding cache report control block from the server. Then, in the subsequent initialization process, when it is necessary to send a datagram to the server (for example, to read the change value stored in a cache report control block), the EntryID corresponding to the cache report control block is filled into the datagram through the write service (SetBRCBValues) and sent to the server. The server will return the relevant data. When the first server EntryID is read and after the client initialization is completed, the EntryID is used as the real-time EntryID and is persisted after a period of time.

[0022] If reading the first server EntryID from the server fails (for example, read timeout) and a datagram needs to be sent to the server, the first persistent EntryID of the corresponding cache report control block in its own periodic persistent storage (for example, stored on disk) is written into the datagram and then sent to the server.

[0023] The second processing method (disconnection processing method) is as follows Figure 2 The client passively disconnects from the server due to network reasons or server-side reasons and then reconnects to the server: server interruption and reconnection are mainly caused by server configuration change, power-on restart, fault restart, etc.; network interruption and reconnection are mainly caused by network structure change, network equipment fault restart, etc. In addition, the client network switching caused by these changes also belongs to the client passively disconnecting from the server.

[0024] After the client re-establishes the connection with the server, since the client has been in normal operation, when writing the EntryID, the real-time EntryID of the corresponding cache report control block in its own memory is written into the datagram and then sent to the server.

[0025] When writing the real-time EntryID into the datagram, the writing of the EntryID may fail (for example, the memory is powered off). In this case, the second persistent EntryID of the corresponding cache report control block in its own persistent storage is written into the datagram and then sent to the server.

[0026] When writing the second persistent EntryID into the datagram, the writing of the EntryID may fail (for example, persistent storage has not been performed yet), in which case the current EntryID (the second server EntryID) corresponding to the corresponding cache report control block is read from the server, and then the second server EntryID is written into the datagram when necessary and sent to the server.

[0027] The reports sent by each cache report control block include a general call report and a change report, and the EntryIDs corresponding to the general call report and the change report are stored. Therefore, when sending the EntryID, you can choose the EntryID of the general call report or the EntryID of the change report. For the first case, it is recommended to select the general call report; for the second case, it is recommended to select the change report. Among them, the general call report contains all the current values ​​of the cache report control block. Since the client needs to obtain all values ​​after initialization after the first case occurs, a general call report is required; the change report contains the change value of the cache report control block that currently meets the change conditions. Since the client has been in normal operation in the second case, the client saves the previous value, so the client needs a change report.

[0028] System Example: This embodiment provides a client EntryID processing system, in which the computer program executed by the processor is designed using a client EntryID processing method as described in the method embodiment. Since the introduction of this method is clear enough, it will not be repeated here.

[0029] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A method for processing EntryID of a client, characterized in that: Including client initialization processing method and / or disconnection processing method; The client initialization processing method comprises: when the client is initialized, reading the current first server EntryID of the corresponding cache report control block from the server, and when a datagram containing the EntryID needs to be sent to the server, writing the read first server EntryID into the datagram; The disconnection processing method comprises: after the client is passively disconnected from the server and then reconnected, when it is necessary to send the datagram to the server, writing the real-time EntryID of the corresponding cache report control block stored in the client into the datagram; The EntryID is an entry identifier in the IEC61850 protocol.

2. The client EntryID processing method according to claim 1, characterized in that: The client initialization processing method further includes: when the first server EntryID is not read from the server and the datagram needs to be sent to the server, writing the first persistent EntryID of the corresponding cache report control block persistently stored in the client into the datagram.

3. The client EntryID processing method according to claim 2, characterized in that: The disconnection processing method further includes: when writing the real-time EntryID fails, writing the second persistent EntryID of the corresponding cache report control block persistently stored in the datagram.

4. The client EntryID processing method according to claim 3, characterized in that: The disconnection processing method also includes: when writing the second persistent EntryID fails, reading the current second server EntryID of the corresponding cache report control block from the server, and when it is necessary to send a datagram containing the EntryID to the server, writing the read second server EntryID into the datagram.

5. A client EntryID processing system, comprising a processor, characterized in that: The processor executes the computer program to implement the steps of the client initialization processing method and / or the disconnection processing method; The client initialization processing method comprises: when the client is initialized, reading the current first server EntryID of the corresponding cache report control block from the server, and when a datagram containing the EntryID needs to be sent to the server, writing the read first server EntryID into the datagram; The disconnection processing method comprises: after the client is passively disconnected from the server and then reconnected, when it is necessary to send the datagram to the server, writing the real-time EntryID of the corresponding cache report control block stored in the client into the datagram; The EntryID is an entry identifier in the IEC61850 protocol.

6. The client EntryID processing system according to claim 5, characterized in that: The client initialization processing method further includes: when the first server EntryID is not read from the server and the datagram needs to be sent to the server, writing the first persistent EntryID of the corresponding cache report control block persistently stored in the client into the datagram.

7. The client EntryID processing system according to claim 6, characterized in that: The disconnection processing method further includes: when writing the real-time EntryID fails, writing the second persistent EntryID of the corresponding cache report control block persistently stored in the datagram.

8. The client EntryID processing system according to claim 7, characterized in that: The disconnection processing method also includes: when writing the second persistent EntryID fails, reading the current second server EntryID of the corresponding cache report control block from the server, and when it is necessary to send a datagram containing the EntryID to the server, writing the read second server EntryID into the datagram.

Images