DETECTION AND READING MANAGEMENT SYSTEM FOR MASS READING FAILURES RELATED TO THE COMMON COMMUNICATION COMPONENT IN SMART METERING SYSTEMS

Abstract

The invention relates to a system and method for detecting and efficiently managing data reading failures in smart meter systems via common communication components. The system analyzes failed meter readings performed via the Head End System (HES), identifies meters using the same modem, gateway / data collector, APN, communication channel, protocol, network connection, or HES service component, and groups the affected meters under a failure group. As long as the common communication problem persists, the rereading of the affected meters is stopped or delayed. Once the communication component is found to be functioning properly again, the rereading of the meters in the failure group is automatically and controllably initiated.This helps reduce unnecessary communication traffic and failed queries, ensures more efficient use of HES resources, and increases the continuity of data collection.

Description

-1- TARIFF SMART METERING SYSTEMS ARE CONNECTED TO A COMMON COMMUNICATION COMPONENT. IDENTIFYING FAILURES IN GROUP READING AND READING MANAGEMENT SYSTEM Technical Area 5 The invention relates to electrical energy distribution systems, smart meter infrastructure (AMI), and Head End. System (HES) technologies relate to the technical field, particularly smart meters. bulk communication occurring during data reading operations analyzing failures, identifying common communication components of failures 10 Linking, grouping the relevant meters and rereading the processes It includes systems and methods for managing it. State of the Art In today's electricity distribution systems, smart meter infrastructures (AMI) are used, Measurements from numerous meters and communication devices located on the site. 15 Head End System (HES) solutions for the centralized collection of data. These systems use meters that provide data at specific intervals or as needed. Data is being read; re-reading operations are being performed for devices from which data cannot be obtained. It can be accomplished. In current practices, failure to read is considered a failure if data cannot be obtained from the meters. The processes are mostly evaluated on a device-by-device basis and recalculated for the relevant meters. Reading tasks are being created. However, the same modem, gateway / data collector, APN, using common infrastructures such as communication channels, protocols or HES service components Simultaneous communication problems can occur in a large number of meters. In such cases, attempting to reread each meter independently; the same 25 As long as the malfunction persists, numerous failed queries will be repeated. increase in communication traffic and HES processing load and system resources This can lead to unnecessary use. In known technology, monitoring smart meter communications and troubleshooting are possible. 30 various processes for evaluation and rereading Although methods exist, collective reading failures are caused by the meters used. linking through common communication components, common fault group -2- the creation of, and the re-reading operations in the group in question during the malfunction period suppression or postponement and the restoration of the common component to a healthy state then the need to automatically start group-based rereading It is located. Explanation of the Purposes of the Invention The primary purpose of the invention is to address the issue of aggregated data readings occurring in smart metering systems. failures are analyzed through common communication components. more effective source identification and optimization of rereading processes The aim is to ensure that it is done. 10 Another purpose of the invention is to combine the same modem, gateway / data collector, APN, and communication system. common occurrences in meters using the channel, protocol or HES service component communication problems are identified and the relevant meters are grouped under a single fault category. The aim is to establish a connection. The invention also provides 15 for the relevant meters as long as the common communication problem continues. to prevent the creation of unnecessary rereading tasks or to avoid existing ones postponing tasks; thus reducing communication traffic, failed connection attempts, and It aims to reduce the workload on the HES (Health Information System). Another aim of the invention is to restore the common communication component to a healthy state. After it was determined that the problem had occurred, the affected meters were reread within 20 days. by initiating data collection automatically and in a controlled manner, the continuity of data collection and the system The goal is to ensure the efficient use of resources. Explaining the Figures Figure 1; Collective reading connected to the common communication component in smart meter systems 25 Schematic of the workflow for identifying failures and managing rereading. It is a representation. Reference Numbers -3- Detailed Description of the Invention The invention addresses the problem of cumulative data reading failures occurring in smart metering systems. Analyzing these failures through shared communication components Grouping affected meters and common communication for rereading processes. 5 with a system and method for managing the problem depending on its nature. It is related. Head End System (HES) infrastructures used in electricity distribution systems. Numerous smart meters and communication devices are managed centrally through this system. And measurement data is collected from these devices. Modems are also used within the scope of LENA-HES. and meter management, Pull / Push data collection, communication and network quality management 10 Functions such as these are available. The invention's operating principle is as shown in Figure 1, and consists of the following stages: It consists of. Reading smart meters: In the first stage, smart meters connected to the system via HES are read. Data reading operations are performed on the meters. The reading operations are carried out within the specified 15 days. Tasks created periodically or as needed according to a time schedule. This can be done accordingly. Each reading operation is either successful or unsuccessful. The status of being present is recorded by the system. Identifying failed readings: Results of the reading procedures performed. The system evaluates and identifies meters from which data cannot be obtained. A specific 20 By evaluating the failed reading operations that occurred during the time interval, in order to determine whether there is a collective communication problem Information regarding failed readings is included in the analysis process. Identifying the common communication component: Failed read. The communication characteristics of the meters are compared. Within this scope, the data of the meters is 25. modem, gateway or data collector, APN, which they use in common in their communication, communication channel, communication protocol, network connection or HES service component, etc. Communication infrastructure elements can be evaluated. A certain number or percentage of failed reads is associated with the same communication component. If it is determined that this is the case, then the failures in question are 30 years apart. It is related to a common communication problem rather than independent meter problems. -4- This identifies the culprits behind numerous failed meter readings. This ensures the identification of a common communication component. Meters are grouped into a fault category: because they are related to the same common communication problem. The identified meters are grouped by the system under a fault category. The fault category, 5. Linking the common communication component with the meters affected by this component. provides. For example, a specific APN, modem, gateway / data collector, or HES service component. Hundreds of meters affected by a problem reported separate malfunctions. Instead of being evaluated individually, they can be managed within the same fault group. Thus, a single meter The breakdowns and the cumulative breakdowns resulting from the shared communication infrastructure are 10 times more separate from each other. Separation is ensured. Stopping or postponing rereads: Identifying a common communication problem. After that, a re-reading of the meters in the relevant fault group is carried out. Operations are temporarily suspended or postponed by the system. This process allows the same meters to be connected again for 15 seconds while the shared communication problem persists. This prevents the need to send another data read request. Thus, it prevents failure. By reducing expected unnecessary communication attempts, traffic on the communication network, The processing load on the hydroelectric power plant and the unnecessary use of system resources are reduced. Not included in the fault group and not affected by the common communication problem. The meter readings for the designated meters can continue as normal. 20 Confirmation that the communication problem has been resolved: The system is functioning as a shared communication network. It monitors the status of the component where the problem has been identified. This monitoring takes place over a specific period of time. health checks, test communications or related activities carried out during these intervals This can be accomplished by evaluating the status information received from the component. Re-establishing successful communication via the shared communication component 25 If it is determined that this can be accomplished, the system will resolve the relevant communication problem. It detects that the problem has been resolved or that the component has been made reusable. At this stage, it is not mandatory to reread all meters simultaneously. First, Common communication is established by performing verification readings on a limited number of meters. It can be verified that the component is functioning properly. 30 -5- Initiating group-based rereading: Confirming that the communication problem has been resolved. Following the completion of the work, a delayed rereading was carried out for the meters in the fault group. The processes are automatically restarted. Rereading operations are necessary because a large number of meters need to be queried simultaneously. To prevent sudden load build-up on communication infrastructure or hydroelectric power plants. 5 This can be carried out in a controlled manner for this purpose. In this context, in the fault group The meters can be read sequentially by dividing them into subgroups or batches of a specific size. A sample application shows the process of reading data for 10,000 smart meters via the HES system. Let's assume that the process was carried out and data could not be obtained from 750 of them. The system, By comparing the communication information regarding the failed readings, the 750 10 in question... It can determine that 620 of the counters are using the same common communication component. In this case, the system will perform a separate rereading for each of the 620 meters. Instead, it groups the meters in question under a common fault group. Common communication. Re-reading of these meters will be suspended as long as the problem persists. or postponed. 15 It has been determined that the common communication component has been restored to a healthy state. Then the rereading process for the 620 meters in the fault group was done automatically. The system is started. The meters are divided into smaller groups as needed and operated in a controlled manner. The data is read and the data collection process continues. With the application of the invention, many 20 common communication problems arising from a shared communication issue can be solved. the number of failed meter readings being considered as independent malfunctions preventative measures are being taken; the common source of the malfunction is identified, and the affected meters are located. grouping prevents unnecessary rereadings and normalizes communication. Upon return, group-based rereading is ensured. This eliminates unnecessary 25, especially in hydroelectric power plant infrastructures where there are many smart meters. Reducing communication traffic and failed queries, centralized system more efficient use of resources and continuity of data collection processes The aim is to increase it. .

Claims

-6- REQUESTS 1. Detecting and re-reading failures in smart meter systems. It is a system for managing reading processes, and its feature is; • Smart meter reading performed via Head End System (HES) 5 Identifying those who failed the procedures, • Communication used by meters that have failed to take readings Comparison of its components, • Multiple failed reads are associated with a common communication component. the determination that it is, 10 • meters affected by the aforementioned shared communication component have a malfunction being associated under the group, • As long as the common communication problem continues, meters in the fault group will be affected. stopping or postponing the related rereading processes, • confirming that the common communication component has been restored to a healthy state and 15 • after the communication problem is resolved, to the meters in the fault group restarting the rereading process It is the performance of its operations.

2. According to claim 1, it is a system whose characteristic is; the aforementioned common communication. components include modem, gateway / data collector, APN, communication channel, 20 communication protocol, network connection or HES service components at least It is that there is one.

3. It is a system according to claim 1, and its characteristic is that it is related to the same common communication component. Multiple meters that were found to be faulty were grouped under a single fault category. As long as the problem of linking and communicating continues, the 25 in question... or stopping the rereading tasks for the meters in the group It is a postponement.

4. The system is defined in accordance with Claim 1, and its characteristic is the health of the common communication component. the status should be checked periodically or on an event basis and the said 30 successful communication was re-established through the component. If this is determined, it will automatically indicate that the communication problem has been resolved. It is the identification of. -7- 5. The system, according to claim 4, has the characteristic that the communication problem has been resolved. Following the detection, a reassessment will be conducted regarding the meters in the fault group. automatic initiation of reading processes and these processes in HES group or party based to reduce the load on the communication infrastructure This is how it is carried out. 5 15 25

Images