Remote debugging system and method for abnormal electric meter based on remote meter reading system

Abstract

The invention belongs to the field of power equipment, and particularly relates to a remote debugging system and method for an abnormal electric meter based on a remote meter reading system. According to the scheme, the original concentrator and server module of the remote meter reading system are utilized, and the client module is additionally arranged, so that remote debugging of the abnormal electric meter connected with the concentrator is realized. According to the scheme, firstly, connection with a concentrator is established through a server module, and dynamic ports with the permission of accessing a debugging object are sequentially generated; the server module is connected with the client module through a dynamic port, and in the debugging process, the server module forwards a debugging instruction and response data between the client module and a debugging object and records a data interaction log at the same time. And finally, after the client module obtains a debugging ending instruction, the client module is disconnected with the server module, and the server module closes the dynamic port. According to the scheme, abnormal ammeter debugging can be realized through remote real-time interaction, the operation and maintenance cost is reduced, and the risk of hot-line operation can be avoided by adopting the remote debugging operation by technicians.

Description

Technical Field

[0001] The present invention belongs to the technical field of electric power equipment, and in particular relates to a remote debugging system for an abnormal electric meter based on a remote meter reading system, a remote debugging method for an abnormal electric meter, and a remote meter reading system. Background Art

[0002] Currently, the operation and maintenance of smart meters primarily relies on on-site technicians, who perform parameter configuration, functional testing, and fault diagnosis through local interfaces such as infrared and RS-485. However, this traditional operation and maintenance model faces multiple challenges: First, manual commissioning requires live operation, and meters are widely distributed and installed in complex environments. Some are located at high altitudes, in high-voltage areas, or in private courtyards, increasing the difficulty and safety risks of on-site operations. Second, manual commissioning is largely time-consuming, and even if the cause of a fault is the same, scattered meters in the same batch must be individually investigated. This is especially true for older meters, where the lack of location information makes locating them even more time-consuming, severely impacting fault response speed and power service quality, while also maintaining high operation and maintenance costs. Summary of the Invention

[0003] In order to solve the technical problems of high operating risks and high operation and maintenance costs for operation and maintenance personnel in high-risk environments, the present application provides a remote debugging system for abnormal electricity meters based on a remote meter reading system, a remote debugging method for abnormal electricity meters, and a remote meter reading system.

[0004] The technical solution provided by the present invention is:

[0005] A remote debugging system for abnormal electricity meters based on a remote meter reading system includes a client module and utilizes a server module and a concentrator from the remote meter reading system to remotely debug abnormal electricity meters in the remote meter reading system. The server module establishes a connection with the concentrator and sequentially generates dynamic ports with access permissions to the debugged object. The dynamic port generation method includes the following steps: 1) The server module establishes a connection with the concentrator, based on the meter address and meter number of one abnormal electricity meter in a list of abnormal electricity meters. 2) The server module sequentially reads the meter addresses and meter numbers of all electricity meters connected to the concentrator through the concentrator, performs a consistency check with the meter address and meter number of the abnormal electricity meter, and defines the electricity meter that passes the check as a debugged object. The server module then generates a dynamic port with access permissions to the debugged object. The server module also establishes a connection with the client module via the dynamic port. During the debugging process, debugging commands and response data are forwarded between the client module and the debugged object, while also recording a data exchange log. After receiving the debugging termination command, the client module disconnects from the server module, and the server module closes the dynamic port.

[0006] The present invention also provides another remote debugging system for abnormal electricity meters based on a remote meter reading system. The system includes a client module and utilizes a server module and a concentrator from the remote meter reading system to remotely debug abnormal electricity meters in the remote meter reading system. The server module establishes a connection with the concentrator and sequentially generates dynamic ports with access rights to the debugged object. The method for generating the dynamic ports includes the following steps: 1) The server module establishes a connection with one of the concentrators. 2) The server module sequentially reads the meter addresses and meter numbers of all electricity meters connected to the concentrator through the concentrator, performs a consistency check with the meter addresses and meter numbers of abnormal meters in a list of abnormal electricity meters, and defines the electricity meters that pass the check as debugged objects. The server module then generates a dynamic port with access rights to the debugged object. The server module also establishes a connection with the client module via the dynamic port. During the debugging process, debugging commands and response data are forwarded between the client module and the debugged object, while simultaneously recording a data exchange log. After receiving the debugging termination command, the client module disconnects from the server module, and the server module closes the dynamic port.

[0007] As a further improvement of the present invention, the server module is further configured to send a stop monitoring instruction to the concentrator after closing the dynamic port, thereby triggering the concentrator to end the monitoring operation on the debugged object.

[0008] As a further improvement of the present invention, the server module further includes a monitoring unit. The monitoring unit is configured to monitor the duration of the disconnection between the server module and the client module. If the disconnection duration exceeds a preset threshold, the server module closes the dynamic port. If the disconnection duration does not exceed the preset threshold and the server module receives a reconnection request from the client module, the server module reconnects to the client module via the dynamic port.

[0009] The present invention also provides a remote debugging method for an abnormal electric meter, which is applied to any of the aforementioned remote debugging systems for abnormal electric meters based on a remote meter reading system, and comprises:

[0010] S1: The server module establishes a connection with the concentrator and generates dynamic ports with access rights to the debugged object. The process includes:

[0011] S11: The server module establishes a connection with the concentrator communicating with the abnormal electricity meter according to the meter address and meter number of one of the abnormal electricity meters in the abnormal electricity meter list.

[0012] S12: The server module reads the meter addresses and meter numbers of all the meters connected to the concentrator in sequence through the concentrator, and performs consistency verification with the meter addresses and meter numbers of the abnormal meters, and defines the meters that pass the verification as the debugging object.

[0013] This generates a dynamic port with access rights to the debuggee.

[0014] S2: The server module establishes a connection with the client module through a dynamic port. During the debugging process, the server module forwards debugging instructions and response data between the client module and the debugged object, and records the data interaction log.

[0015] S3: After the client module obtains the end debugging instruction, it disconnects from the server module.

[0016] S4: After the server module disconnects from the client module, it closes the dynamic port.

[0017] Repeat steps S1 to S4 until the list of abnormal meters is traversed.

[0018] The present invention also provides another remote debugging method for an abnormal electric meter, which is applied to any of the aforementioned remote debugging systems for abnormal electric meters based on a remote meter reading system, and includes:

[0019] S1: The server module establishes a connection with the concentrator and generates dynamic ports with access rights to the debugged object. The process includes:

[0020] S11: The server module establishes a connection with one of the concentrators.

[0021] S12: The server module reads the meter addresses and meter numbers of all the electricity meters connected to the concentrator in sequence through the concentrator, and performs consistency verification with the meter addresses and meter numbers of the abnormal meters in the abnormal meter list, defines the electricity meters that pass the verification as debugging objects, and generates a dynamic port with access permission to the debugging object.

[0022] S2: The server module establishes a connection with the client module through a dynamic port. During the debugging process, the server module forwards debugging instructions and response data between the client module and the debugged object, and records the data interaction log.

[0023] S3: After the client module obtains the end debugging instruction, it disconnects from the server module.

[0024] S4: After the server module disconnects from the client module, it closes the dynamic port.

[0025] Repeat steps S1 to S4 until all concentrators are traversed or the list of abnormal meters is traversed.

[0026] As a further improvement of the present invention, step S2 includes:

[0027] S21: The server module establishes an encrypted communication channel with the client module through the dynamic port.

[0028] S22: The server module sends a monitoring debugging object instruction to the concentrator, triggering the concentrator to enter a debugging monitoring mode.

[0029] S23: The server module receives the debugging instruction sent by the client module, and records the content and timestamp of the debugging instruction to the log database.

[0030] S24: The server module transmits the debugging instruction to the debugging target through the concentrator.

[0031] S25: The concentrator monitors the response data of the debugged object and sends it to the server module.

[0032] S26: After receiving the response data of the debugging object sent back by the concentrator, the server module records the content and timestamp of the response data in the log database, and encrypts and sends it back to the client module.

[0033] As a further improvement of the present invention, in step S4, after closing the dynamic port, the server module sends a stop-monitoring instruction to the concentrator. After receiving the stop-monitoring instruction, the concentrator ends the monitoring operation on the debugged object.

[0034] As a further improvement of the present invention, in step S4, after the server module disconnects from the client module, the server module monitors the duration of the disconnection with the client module. If the disconnection duration exceeds a preset threshold, the server module closes the dynamic port; if the disconnection duration does not exceed the preset threshold and the server module receives a reconnection request from the client module, the server module re-establishes a connection with the client module through the dynamic port.

[0035] The present invention also provides a remote meter reading system, which includes a server module, at least one concentrator communicating with the server module, and at least one electricity meter communicating with each concentrator. It also includes a client module. The client module, server module, concentrator, and electricity meter constitute the main components of any of the aforementioned remote debugging systems for abnormal electricity meters based on the remote meter reading system.

[0036] The technical solution provided by the present invention has the following beneficial effects:

[0037] The technical solution provided by the present invention utilizes the existing concentrator and server module of the remote meter reading system and adds a client module to achieve remote debugging of abnormal meters connected to the concentrator. Compared with the traditional solution of on-site debugging of abnormal meters by technicians, the present invention uses the client module to remotely exchange data with abnormal meters, reducing on-site manpower and transportation time, shortening fault location time, and thus reducing operation and maintenance costs. Technicians can complete debugging operations without entering dangerous areas such as high-voltage and high-altitude areas, avoiding the risks of live operations. The server module records the data interaction log during the interaction between the client module and the abnormal meter, which can fully record operation traces, prevent data tampering, and ensure data security.

[0038] On the other hand, the present invention performs a consistency check on the device information in the abnormal meter list and the device information returned by the meter, and identifies the meter that passes the check as the debugging target, which not only ensures the reliability of the communication link but also verifies the authenticity of the device identity of the debugging target. The server module generates a dynamic port with access rights to the debugging target and closes the dynamic port after debugging is completed, ensuring that technicians can only perform debugging operations on the designated debugging target (i.e., the actual abnormal meter), further improving the security of the remote debugging system. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 This is a structural block diagram of a remote debugging system for abnormal electric meters based on a remote meter reading system provided in Example 1 of the present invention.

[0040] Figure 2 This is a flow chart of a remote debugging method for an abnormal electric meter provided in Example 2 of the present invention. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0042] Example 1

[0043] like Figure 1As shown, the remote debugging system for abnormal meters based on a remote meter reading system includes a server module 101, a concentrator 102, and an additional client module 103 from the remote meter reading system to remotely debug abnormal meters 1041 in the remote meter reading system. By utilizing the existing concentrator and server modules of the remote meter reading system and adding a client module, remote debugging of abnormal meters connected to the concentrator can be achieved at low cost and with high stability. Compared to traditional solutions where technicians debug abnormal meters on-site, the present invention uses the client module to remotely exchange data with abnormal meters, shortening fault location time, reducing on-site manpower and travel time, and thus lowering operation and maintenance costs. Technicians can complete debugging operations without entering dangerous areas such as high-voltage and high-altitude areas, thus avoiding the risks of working with live power.

[0044] The server module 101 establishes a connection with the concentrator 102 and sequentially generates a dynamic port with access rights to the debugged object (i.e., the abnormal electricity meter 1041). The server module 101 also establishes a connection with the client module 103 via the dynamic port. During the debugging process, the client module 103 forwards debugging instructions and response data between the client module 103 and the debugged object, while also recording a data interaction log. After receiving the command to end debugging, the client module 103 disconnects from the server module 101. The server module 101 closes the dynamic port and sends a stop-listening command to the concentrator 102, triggering the concentrator 102 to stop monitoring the debugged object.

[0045] Specifically, the steps of the above dynamic port generation method are as follows:

[0046] 1) Server module 101 includes a backend management system 1011 and a server 1012. Backend management system 1011 is used to obtain a list of abnormal meters containing information about at least one abnormal meter. This abnormal meter information may be the meter address and meter number of an abnormal meter 1041. Based on the meter address and meter number of an abnormal meter 1041 in the list of abnormal meters, backend management system 1011 drives server 1012 to establish a connection with concentrator 102, which is communicating with abnormal meter 1041.

[0047] 2) The server 1012 sends device information reading instructions to all electricity meters connected to the concentrator 102 in sequence through the concentrator 102 , and thereby receives meter addresses and meter numbers returned by all electricity meters 104 through the concentrator 102 in sequence.

[0048] 3) The background management system 1011 retrieves the table address and table number received by the server 1012, and performs a consistency check with the table address and table number of the abnormal meter 1041 in the abnormal meter list, and defines the meter 104 that passes the check as the debugging object (i.e., the abnormal meter 1041), and drives the server 1012 to generate a dynamic port with access to the debugging object. Through the consistency check, it is confirmed that the currently established communication link is normal and the debugging environment is normal, preventing subsequent debugging operations from being mistakenly connected to other meters or the communication link from failing. Only when it is ensured that the device identity information is correct and the communication link is normal, will the server 1012 generate a dynamic port for this debugging task. This method of dynamically generating temporary ports can avoid the risk of fixed ports being attacked by long-term scanning. Generating a unique port for each debugging is equivalent to building a one-time communication channel. The technician can only interact with the specified debugging object through this port to prevent other normal meters from being maliciously attacked.

[0049] Server 1012 establishes a connection with client module 103 via a dynamic port and then sends a command to monitor the debugged object to concentrator 102. Upon receiving the command, concentrator 102 monitors the state of the debugged object and forwards the debugged object's received command to the debugged object. Server 1012 acts as a relay point for data exchange between client module 103 and the debugged object during the debugging process. It receives debugged commands from client module 103 and forwards them to concentrator 102, receives response data from concentrator 102 and forwards it to client module 103, and records a data exchange log.

[0050] The server module 101 may also include a log database 1013. Throughout the debugging process, all data generated during data interaction between the client module 103 and the debugged object, such as every debug command and timestamp issued by the client module 103 and every response data and timestamp issued by the debugged object, is stored in the log database 1013. The entire data interaction process is recorded in the log database, enabling accurate tracing of operation records during audits and significantly improving security.

[0051] Specifically, the backend management system 1011 can obtain abnormal meter device information from the master station. The master station is the core management platform in the power system, responsible for centralized monitoring, data collection, and abnormality diagnosis of smart meters. The master station applies threshold judgments to metering parameters reported by the meters (such as voltage surges and current imbalances), and flags abnormalities if they exceed preset ranges. Meters also periodically send heartbeat messages. If the master station does not receive a response or receives a fault code, an alarm is triggered. The master station can also locate abnormal meters by comparing theoretical power usage with actual power usage. The master station's database stores device information for all meters. When an abnormality alarm is received, it automatically associates the corresponding information and sends the abnormal meter device information to the backend management system 1011. The master station's database also stores the topological relationship between meter 104 and concentrator 102. The abnormal meter device information can be used to query the corresponding concentrator identification code, which can then be used to quickly locate the corresponding concentrator 102.

[0052] The server 1012 may also include a monitoring unit, which is used to monitor the connection status between the server 1012 and the client module 103 in real time. When a connection interruption is detected and the duration exceeds a preset threshold (such as 30 seconds), the server 1012 will close the current dynamic port to release resources and send a stop listening instruction to the concentrator 102 to terminate the concentrator 102's monitoring operation on the debugged object; when the disconnection lasts for less than 30 seconds and the server module receives a reconnection request from the client module, it will reconnect to the client module. This mechanism, while ensuring security, reserves a reasonable fault tolerance space for legitimate users - when a technician causes a non-malicious disconnection due to operational errors or network fluctuations, the original connection can be quickly restored within the threshold time, avoiding efficiency loss and waste of network resources caused by repeated application for new dynamic ports.

[0053] It should be noted that the server 1012 closes the dynamic port, which only means that the current debugging object is debugged. If there are other abnormal meters in the abnormal meter list that have not been debugged, the server 1012 will repeat the above steps to generate dynamic ports again until all abnormal meters in the abnormal meter list are debugged.

[0054] The above-described dynamic port generation method is suitable for scenarios where abnormal meters 1041 are sparsely distributed during power system operation and maintenance, and is particularly well-suited for systems where a complete topology of meters 104 and concentrators 102 has been established. By precisely locating the target concentrators 102 and meters 104, this strategy significantly reduces network communication burdens and improves troubleshooting efficiency. It is particularly well-suited for newly built residential communities or areas with low equipment failure rates. Its core advantage lies in its highly targeted response to specific anomalies, while also complying with mainstream "address-based" communication protocol specifications to ensure stable system operation.

[0055] However, in the scenario of upgrading an old power grid, the pre-stored topological relationship between meter 104 and concentrator 102 at the master station may no longer be accurate. For example, abnormal meter 1041 recorded in the abnormal meter list has long been replaced by concentrator 102. At this time, the topological relationship between meter 104 and concentrator 102 will locate the wrong concentrator 102, and abnormal meter 1041 will not be found. Therefore, another implementation method can be used to generate dynamic ports. The specific steps are as follows:

[0056] 1) Backend management system 1011 obtains a list of abnormal meters containing information about at least one abnormal meter. This information can be the meter address and meter number of abnormal meter 1041. The existing remote meter reading system includes at least one concentrator, each of which is connected to at least one meter. Backend management system 1011 drives server 1012 to establish a connection with one of the concentrators 102.

[0057] 2) The server 1012 sends device information reading instructions to all the electricity meters 104 connected to the concentrator 102 in sequence through the concentrator 102 , and thereby receives meter addresses and meter numbers returned by all the electricity meters 104 through the concentrator 102 in sequence.

[0058] 3) The background management system 1011 retrieves the table address and table number received by the server 1012, and performs a consistency check with the table address and table number of the abnormal meter 1041 in the abnormal meter list, and defines the meter 104 that passes the check as the debugging object (i.e., the abnormal meter 1041), and drives the server 1012 to generate a dynamic port with access to the debugging object. Through the consistency check, it is confirmed that the currently established communication link is normal and the debugging environment is normal, preventing subsequent debugging operations from being mistakenly connected to other meters or the communication link from failing. Only when it is ensured that the device identity information is correct and the communication link is normal, will the server 1012 generate a dynamic port for this debugging task. This method of dynamically generating temporary ports can avoid the risk of fixed ports being attacked by long-term scanning. Generating a unique port for each debugging is equivalent to building a one-time communication channel. The technician can only interact with the specified debugging object through this port to prevent other normal meters from being maliciously attacked.

[0059] It should be noted that closing the dynamic port by the server 1012 only indicates that the debugging of the current debugged object has been completed. If there are other abnormal meters in the abnormal meter list that have not been debugged, the server 1012 will repeat the above steps to generate dynamic ports again until all concentrators 102 are traversed or all abnormal meters in the abnormal meter list have been debugged.

[0060] The dynamic port generation method described above uses a concentrator 102 traversal mode, which is more suitable for scenarios involving the renovation of older power grids. This method does not rely on pre-existing topological relationships and ensures comprehensiveness and reliability by comprehensively scanning all concentrators 102 and their subordinate meters 104. Furthermore, this concentrator 102 traversal method can effectively detect batches of abnormal meters 1041 under a particular concentrator 102, eliminating the need to frequently establish connections with different concentrators 102 based on abnormal meter entries in the abnormal meter list. This makes it suitable for large-scale exception handling (such as when a group of meters are damaged due to natural disasters) and improves the efficiency of remote debugging.

[0061] Example 2

[0062] like Figure 2 As shown, this embodiment provides a remote debugging method for an abnormal electric meter, which is applied to a remote debugging system for an abnormal electric meter based on a remote meter reading system provided in the above embodiment 1, and includes the following steps:

[0063] S1: The server module establishes a connection with the concentrator and generates dynamic ports with access rights to the debugged object. Step S1 can be broken down into the following steps:

[0064] S11: The server module pre-acquires a list of abnormal meters containing at least one abnormal meter device information, and the abnormal meter device information may be the table address and table number of the abnormal meter. The server module establishes a connection with the concentrator communicating with the abnormal meter through the 4G wireless communication network based on the table address and table number of one of the abnormal meters in the abnormal meter list. Specifically, the server module obtains the abnormal meter list through the electricity consumption information collection system of the power grid master station. The abnormal meter list contains multiple abnormal meter device information, and each abnormal meter device information includes a 12-bit BCD-coded table address and a 6-bit table number. The database of the master station stores the topological relationship between the meter and the concentrator. The corresponding concentrator identification code can be queried through the abnormal meter device information, and then the corresponding concentrator can be quickly located through the concentrator identification code.

[0065] S12: The server module sends a device information reading instruction to the concentrator, which forwards the device information reading instruction to all meters connected to the concentrator via the power line carrier, and then receives the meter addresses and meter numbers returned by all meters through the concentrator in turn.

[0066] S13: The server module performs consistency check on the returned meter address and meter number with the meter address and meter number of the abnormal meter, and defines the meter that passes the check as the debugging object. The server module then generates a dynamic port with access rights to the debugging object. During the consistency check, not only the device identity of the meter can be confirmed, but also the validity of the communication link can be confirmed. Eliminate packet loss or signal interference issues with the 4G communication module.

[0067] S2: The server module establishes a connection with the client module through a dynamic port. During the debugging process, the server module forwards debugging instructions and response data between the client module and the debugged object, and records the data interaction log. The specific steps can be broken down into the following:

[0068] S21: The server module establishes an encrypted communication channel with the client module through the dynamic port. When establishing the connection, the server needs to verify the legitimacy of the client through the TCP three-way handshake.

[0069] S22: The server module sends a monitoring debugging object instruction to the concentrator, triggering the concentrator to enter a debugging monitoring mode.

[0070] Specifically, the server module sends a specially formatted sniffing command message (containing a 0xA0 start character, the meter address, and a 2-byte opcode) to the concentrator. Upon receipt, the concentrator immediately switches to debug mode: 1) raises the meter's communication priority to the highest level; 2) enables full message capture; and 3) establishes a dedicated uplink channel. In this mode, all meter communication messages (including proactive reports) are uploaded to the server in real time via the 4G network.

[0071] S23: The server module receives the debugging instruction sent by the client module, and records the content and timestamp of the debugging instruction to the log database.

[0072] Specifically, upon receiving a debug command, the server module performs the following: 1) timestamps the debug command using the Beidou timing system; 2) stores the timestamp and debug command content in a specific format in a log database. The stored fields include session ID, operation type, key parameters, and digital signature.

[0073] S24: The server module transmits the debugging instructions to the debugged object via the concentrator. In some typical cases, after the server completes storage, it verifies the legality of the instructions (parameter range, business logic), and then sends the legal debugging instructions to the concentrator via the 4G network. The concentrator then transmits the debugging instructions to the debugged object via power line carrier communication.

[0074] S25: The concentrator monitors the response data of the debugged object and sends it to the server module.

[0075] S26: After receiving the debugged object's response data from the concentrator, the server module records the response data's content and timestamp in the log database and encrypts it before sending it back to the client module. The entire data interaction is recorded in the log database, enabling accurate tracing of operation records during audits and significantly improving security.

[0076] S3: After receiving the command to end debugging, the client module disconnects from the server module. Once the technician confirms the debugging task is complete, they issue the command to end debugging to the client module, which then sends a disconnect request to the server module. This prevents unauthorized access or malicious attackers from exploiting unused ports, effectively reducing security risks.

[0077] S4: After the server module is disconnected from the client module, it closes the dynamic port. In some other embodiments, the server module also sends a stop listening instruction to the concentrator, triggering the concentrator to stop monitoring the debug object. Specifically, the server reclaims the dynamic port, notifies the concentrator to stop monitoring the debug object, updates the debugging status to "completed", and generates an audit summary (including total traffic, number of operations, etc.) in the log database. In some typical cases, the server module also has a "disconnect and reconnect" function. After disconnecting from the client module, it will also monitor the disconnection duration. If the disconnection duration exceeds the preset threshold, the dynamic port will be closed. If the disconnection duration does not exceed the preset threshold and a reconnection request from the client module is received, the connection with the client module will be established again. This mechanism, while ensuring security, reserves a reasonable fault tolerance space for legitimate users - when a technician causes a non-malicious disconnection due to operational error or network fluctuations, the original connection can be quickly restored within the threshold time, avoiding efficiency loss and waste of network resources caused by repeated application for new dynamic ports.

[0078] This dynamic port generation method is suitable for power system operations and maintenance scenarios where abnormal meters are sparsely distributed, and is particularly well-suited for systems with a complete meter-concentrator topology. By precisely locating the target concentrator and meter, this strategy significantly reduces network communication overhead and improves troubleshooting efficiency. It is particularly well-suited for newly built residential communities or areas with low equipment failure rates. Its core advantage lies in its highly targeted response to specific anomalies, while also complying with mainstream "address-based" communication protocols to ensure stable system operation.

[0079] However, in the scenario of upgrading an old power grid, the pre-stored topological relationship between the meter 104 and the concentrator 102 at the master station may no longer be accurate. For example, if the abnormal meter 1041 recorded in the abnormal meter list has already been replaced by the concentrator 102, then the topological relationship between the meter 104 and the concentrator 102 will locate the wrong concentrator 102, and the abnormal meter 1041 will not be found. Therefore, another method can be used to generate dynamic ports in the above step S1. The specific steps are as follows:

[0080] S11: The server module establishes a connection with one of the concentrators.

[0081] S12: The server module sends device information reading instructions to all electricity meters connected to the concentrator in sequence through the concentrator, and thereby receives meter addresses and meter numbers returned by all electricity meters through the concentrator in sequence.

[0082] S13: The server module pre-acquires an abnormal meter list containing information about at least one abnormal meter. The abnormal meter information may be the meter address and meter number of the abnormal meter. The server module performs a consistency check on the returned meter address and meter number with the meter addresses and meter numbers of the abnormal meters in the abnormal meter list. The meter that passes the check is defined as a debug target, and the server module generates a dynamic port with access rights to the debug target.

[0083] The dynamic port generation method described above uses a concentrator traversal model, which is more suitable for retrofitting legacy power grids. This method does not rely on pre-existing topological relationships and ensures comprehensive and reliable troubleshooting by comprehensively scanning all concentrators and their subordinate meters. Furthermore, this concentrator traversal method effectively detects batches of abnormal meters under a specific concentrator, eliminating the need to frequently establish connections with different concentrators based on abnormal meter entries in the abnormal meter list. This makes it suitable for large-scale anomaly handling (such as when a group of meters are damaged due to natural disasters) and improves the efficiency of remote debugging.

[0084] Example 3

[0085] Based on the remote debugging system for abnormal electricity meters based on a remote meter reading system provided in Example 1, this embodiment further provides a remote meter reading system comprising a server module, at least one concentrator communicating with the server module, and at least one electricity meter communicating with each concentrator. The system also comprises a client module. The client module, server module, concentrator, and electricity meter constitute the main components of the remote debugging system for abnormal electricity meters based on a remote meter reading system as described in Example 1.

[0086] In other words, the present invention upgrades the traditional remote meter reading system, further expanding its functionality while retaining its original features. By using the client module as a standard component of the remote meter reading system, it enables remote debugging of abnormal meters connected to the concentrator, achieving low cost and high stability.

[0087] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in the present invention can be achieved. This is not limited herein.

[0088] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of such features. In the description of the present invention, "plurality" means two or more, unless otherwise specifically defined.

[0089] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A remote debugging system for abnormal electric meters based on a remote meter reading system, characterized by: It includes a client module and utilizes a server module and a concentrator from a remote meter reading system to remotely debug abnormal meters in the remote meter reading system; The server module establishes a connection with the concentrator and sequentially generates dynamic ports with access rights to the debug object: the server module establishes a connection with the concentrator that communicates with the abnormal meter based on the meter address and meter number of one of the abnormal meters in the abnormal meter list; the server module sequentially reads the meter addresses and meter numbers of all meters connected to the concentrator through the concentrator, and performs a consistency check with the meter address and meter number of the abnormal meter, defining the meter that passes the check as a debug object, and the server module thereby generates a dynamic port with access rights to the debug object; The server module also establishes a connection with the client module through a dynamic port. During the debugging process, it forwards debugging instructions and response data between the client module and the debugging object, and records the data interaction log. After the client module obtains the end debugging instruction, it disconnects from the server module, and the server module closes the dynamic port.

2. A remote debugging system for abnormal electric meters based on a remote meter reading system, characterized by: It includes a client module and utilizes a server module and a concentrator from a remote meter reading system to remotely debug abnormal meters in the remote meter reading system; The server module establishes a connection with the concentrator and sequentially generates dynamic ports with access rights to the debug object: the server module establishes a connection with one of the concentrators; the server module sequentially reads the meter addresses and meter numbers of all the meters connected to the concentrator through the concentrator, and performs consistency verification with the meter addresses and meter numbers of the abnormal meters in the abnormal meter list. The meter that passes the verification is defined as the debug object, and the server module generates a dynamic port with access rights to the debug object. The server module also establishes a connection with the client module through a dynamic port. During the debugging process, it forwards debugging instructions and response data between the client module and the debugging object, and records the data interaction log. After the client module obtains the end debugging instruction, it disconnects from the server module, and the server module closes the dynamic port.

3. The remote debugging system for abnormal electric meters based on the remote meter reading system according to claim 1 or 2, characterized in that: The server module is further configured to send a stop monitoring instruction to the concentrator after closing the dynamic port, thereby triggering the concentrator to end the monitoring operation on the debugged object.

4. The remote debugging system for abnormal electric meters based on the remote meter reading system according to claim 1 or 2, characterized in that: The server module further includes a monitoring unit configured to monitor a disconnection duration between the server module and the client module. If the disconnection duration exceeds a preset threshold, the server module closes the dynamic port. If the disconnection duration does not exceed the preset threshold and the server module receives a reconnection request from the client module, the server module reestablishes a connection with the client module through the dynamic port.

5. A remote debugging method for an abnormal electric meter, characterized in that: The invention is applied to the remote debugging system for abnormal electric meters based on the remote meter reading system described in claim 1, 3 or 4, and comprises: S1: The server module establishes a connection with the concentrator and sequentially generates dynamic ports with access rights to the debugged object. The process includes: S11: The server module establishes a connection with the concentrator communicating with the abnormal meter according to the meter address and meter number of one of the abnormal meters in the abnormal meter list; S12: The server module reads the meter addresses and meter numbers of all the electricity meters connected to the concentrator in sequence through the concentrator. A consistency check is performed with the meter address and meter number of the abnormal meter, and the meter that passes the check is defined as the debugging object, thereby generating a dynamic port with access permission to the debugging object; S2: The server module establishes a connection with the client module through a dynamic port. During the debugging process, the server module forwards debugging instructions and response data between the client module and the debugged object, and records data interaction logs. S3: After the client module obtains the end debugging instruction, it disconnects from the server module; S4: After the server module is disconnected from the client module, the dynamic port is closed; steps S1 to S4 are repeated until the abnormal meter list is traversed.

6. A remote debugging method for an abnormal electric meter, characterized in that: The remote debugging system for abnormal electric meters based on a remote meter reading system is applied to any one of claims 2 to 4, and comprises: S1: The server module establishes a connection with the concentrator and sequentially generates dynamic ports with access rights to the debug object. The process includes: S11: The server module establishes a connection with one of the concentrators; S12: The server module sequentially reads the meter addresses and meter numbers of all the electricity meters connected to the concentrator through the concentrator, performs consistency check with the meter addresses and meter numbers of the abnormal electricity meters in the abnormal electricity meter list, defines the electricity meters that pass the check as debugging objects, and generates a dynamic port with access rights to the debugging objects; S2: The server module establishes a connection with the client module through a dynamic port. During the debugging process, the server module forwards debugging instructions and response data between the client module and the debugged object, and records data interaction logs. S3: After the client module obtains the end debugging instruction, it disconnects from the server module; S4: After the server module is disconnected from the client module, the dynamic port is closed; steps S1 to S4 are repeated until all concentrators are traversed or the abnormal meter list is traversed.

7. The remote debugging method for an abnormal electric meter according to claim 5 or 6, characterized in that: Step S2 includes: S21: The server module establishes an encrypted communication channel with the client module through the dynamic port; S22: The server module sends a monitoring and debugging object instruction to the concentrator, triggering the concentrator to enter the debugging and monitoring mode; S23: The server module receives the debugging instruction sent by the client module and records the content and timestamp of the debugging instruction to the log database; S24: The server module transmits the debugging instruction to the debugging target through the concentrator; S25: The concentrator monitors the response data of the debugged object and sends it to the server module; S26: After receiving the response data of the debugging object sent back by the concentrator, the server module records the content and timestamp of the response data in the log database, and encrypts and sends it back to the client module.

8. The remote debugging method for an abnormal electric meter according to claim 7, characterized in that: In step S4, after closing the dynamic port, the server module sends a stop listening instruction to the concentrator; After receiving the stop monitoring instruction, the concentrator ends the monitoring operation on the debugged object.

9. The remote debugging method for an abnormal electric meter according to claim 7, characterized in that: In step S4, after the server module is disconnected from the client module, the server module monitors the duration of the disconnection with the client module. If the disconnection duration exceeds a preset threshold, the server module closes the dynamic port. If the disconnection duration does not exceed the preset threshold and the server module receives a reconnection request from the client module, the server module reestablishes a connection with the client module through the dynamic port.

10. A remote meter reading system comprising a server module, at least one concentrator communicating with the server module, and at least one electric meter communicating with each concentrator, characterized in that: It also includes a client module. The client module, the server module, the concentrator, and the electric meter constitute the main components of the remote debugging system for abnormal electric meters based on the remote meter reading system as claimed in any one of claims 1 to 4.

Images