A power cut alarm method and device for a user side and electronic equipment

Abstract

The application discloses a user-side power failure alarm method and device and electronic equipment. The method is applied to an alarm platform, and comprises the following steps: sending a polling request to a broadband access server according to a preset fixed period, and receiving an online user list returned by the broadband access server; screening offline users not appearing in the online user list of the current period; searching a pre-configured device mapping table according to account information of the offline users, and determining optical line terminal devices to which the offline users belong; sending a user state query request to the optical line terminal devices, and marking the offline users as suspected power failure users if a user terminal device offline reason code returned by the optical line terminal devices is a power-off reason; and continuously monitoring an offline duration of the suspected power failure users, and generating an alarm information when the offline duration exceeds a preset determination threshold. The method can realize active identification, accurate determination and early warning of user-side power failure.

Description

Technical Field

[0001] This invention relates to the field of network technology, and in particular to an alarm method, device, and electronic device for power outages on the user side. Background Technology

[0002] With the deep integration of broadband networks and power grids, the stability of user-side power supply directly affects the online status of broadband network equipment and the user experience. In daily operation, user-side network equipment (such as optical line terminal equipment) frequently experiences power outages or disconnections due to abnormal power supply, line faults, or partial power outages. However, existing monitoring and maintenance methods have the following significant shortcomings: 1) Inability to accurately determine user-side power outages, resulting in a fundamental monitoring blind spot: Traditional power monitoring systems physically cannot cover the "last 100 meters" of faults after the user's electricity meter, and logically lack reliable criteria to effectively distinguish between fault-based power outages and normal no-load conditions. When user-side equipment goes offline, the operation and maintenance system cannot accurately determine whether the offline is due to fiber optic cable faults, equipment malfunctions, or actual power outages on the user side, making it difficult to accurately pinpoint the root cause of the fault.

[0003] 2) Insufficient initiative and timeliness: Existing network operation and maintenance models generally rely on user reports of faults, and the system itself cannot proactively issue alarms before users discover and report faults. When a power outage on the user side causes a network interruption, there is a long time lag from the occurrence of the disconnection to the user noticing it, calling customer service to report the fault, and then to the intervention of operation and maintenance personnel, which seriously affects the timeliness of fault handling and user satisfaction. Summary of the Invention

[0004] The technical problem to be solved by this invention is to address the above-mentioned shortcomings of the prior art by proposing a user-side power outage alarm method, device, and electronic equipment. This method can achieve proactive identification, accurate judgment, and early warning of user-side power outage faults.

[0005] In a first aspect, the present invention provides an alarm method for a power outage on the user side, which is applied to an alarm platform and includes: The system sends polling requests to the broadband access server at a preset fixed period and receives the list of online users returned by the broadband access server. The online user list for the current period is compared with the online user list for the previous period, and offline users that do not appear in the online user list for the current period are filtered out. Based on the account information of offline users, search the pre-configured device mapping table to determine the optical line terminal device to which the offline user belongs; Send a user status query request carrying an offline user identifier to the optical line terminal equipment, and receive the user terminal equipment offline reason code returned by the optical line terminal equipment; If the offline reason code indicates a power outage, then the offline user will be marked as a suspected power outage user. The system monitors the continuous offline time of users suspected of power outages, and generates an alarm message when the continuous offline time exceeds a preset threshold.

[0006] Furthermore, it sends polling requests to the broadband access server at a preset fixed period and receives the online user list returned by the broadband access server, specifically including: According to the preset polling cycle, polling requests are periodically sent to the management interface of the broadband access server to query the user's online status; Receive raw online session data returned by the broadband access server based on polling requests; The raw online session data is parsed, cleaned, and structured to extract the account information of current online users and generate a list of online users.

[0007] Furthermore, a user status query request carrying an offline user identifier is sent to the optical line terminal equipment, and the user terminal equipment offline reason code returned by the optical line terminal equipment is received, specifically including: A user status query request is generated based on the offline user identifier. The user status query request carries the offline user identifier and the query instruction identifier. The user status query request is sent to the optical line terminal equipment. The optical line terminal equipment responds to the query command identifier and queries the offline reason code of the user terminal equipment corresponding to the offline user identifier. The system receives offline reason codes from the optical line terminal equipment. These offline reason codes include at least one of the following: power outage reason code, fiber optic link interruption reason code, equipment failure reason code, and user-initiated offline reason code.

[0008] Furthermore, before searching the pre-configured device mapping table based on the offline user's account information, the method also includes: Determine whether an offline user is a periodically offline user; If so, retrieve the offline user's historical offline records and calculate the offline user's periodic offline feature value based on the historical offline records; If the periodic offline characteristic value exceeds the preset periodic offline threshold, the offline user will be removed from the query queue, and the step of searching the pre-configured device mapping table will no longer be executed.

[0009] Furthermore, the system monitors the continuous offline time of suspected power outage users. When the continuous offline time exceeds a preset threshold, an alarm message is generated, specifically including: Establish offline monitoring tasks for users suspected of experiencing power outages, and update the duration of continuous offline activity for users suspected of experiencing power outages according to the preset monitoring update cycle; Determine whether the updated continuous offline duration exceeds a preset threshold. If so, obtain the user attribute information of the suspected power outage user, encapsulate the user attribute information and the continuous offline duration, and generate alarm information.

[0010] Furthermore, the method also includes: Get multiple target users marked as suspected power outage users within a preset time window, and extract the geographic coordinate information of each target user; Based on geographic coordinate information, spatial clustering analysis is performed on multiple target users to determine the spatial clustering region to which each target user belongs. The number of target users in each spatial cluster region is counted, and the offline density ratio of target users in each spatial cluster region to the total number of users in the corresponding spatial cluster region is calculated. The offline density ratio is compared with the preset regional fault density threshold. If the offline density ratio exceeds the regional fault density threshold, a regional fault alarm is generated and pushed to the operation and maintenance management platform.

[0011] Furthermore, after generating the alarm information, the method also includes: Obtain the geographic information of the area where the suspected power outage user is located, and query whether there are any reported power outage plans in the area based on the geographic information; If there are reported power outage plans, compare the power outage time of suspected power outage users with the time window of the reported power outage plans; If the power outage time falls within the time window of the reported power outage plan, the alarm information will be marked as a planned power outage alarm and pushed to the planned power outage management unit of the operation and maintenance management platform. If there is no reported power outage plan, the alarm information will be marked as a power outage alarm and pushed to the fault repair unit of the operation and maintenance management platform.

[0012] Furthermore, after generating the alarm information, the method also includes: Obtain the user identification information and geographical location information corresponding to the alarm information; The geographic location information is reversibly encrypted using a reversible encryption algorithm to generate encrypted geographic location information. The user identification information is de-identified using an irreversible hash algorithm to generate a de-identified user identifier. Encapsulate encrypted geographic location information, de-identified user identifiers, and power outage timestamps from alarm information to generate standardized alarm data packets; Alarm data packets are pushed to the power supply operation and maintenance management platform via a secure transmission protocol.

[0013] Secondly, the present invention provides an alarm device for user-side power outages, which is applied to an alarm platform and includes: The system includes a polling unit, a comparison unit, a first query unit, a second query unit, a processing unit, and an alarm generation unit. The polling unit is used to send polling requests to the broadband access server at a preset fixed period, receive the online user list returned by the broadband access server, and send the online user list to the comparison unit. The comparison unit, connected to the polling unit, is used to compare the online user list of the current period with the online user list of the previous period, filter out offline users that do not appear in the online user list of the current period, and send the information of the offline users to the first query unit. The first query unit, connected to the comparison unit, is used to search a pre-configured device mapping table based on the account information of the offline user, determine the optical line terminal device to which the offline user belongs, and send the information of the optical line terminal device to the second query unit. The second query unit, connected to the first query unit, is used to send a user status query request carrying an offline user identifier to the optical line terminal equipment, and receive the offline reason code of the user terminal equipment returned by the optical line terminal equipment, and send the offline reason code to the processing unit. The processing unit, connected to the second query unit, is used to mark the offline user as a suspected power outage user when the offline reason code indicates a power outage reason, and to send the information of the suspected power outage user to the alarm generation unit. The alarm generation unit, connected to the processing unit, is used to monitor the continuous offline time of suspected power outage users. When the continuous offline time exceeds the preset judgment threshold, alarm information is generated.

[0014] Thirdly, the present invention provides an electronic device including a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor executes the alarm method for user-side power outage according to the first aspect.

[0015] This invention uses an alarm platform to periodically poll the broadband access server to filter offline users and combines this with cross-device collaborative analysis of the offline cause codes returned by the optical line terminal equipment. This enables accurate determination of the actual power outage status on the user side and automatic generation of alarms after the fault has persisted for a certain period of time, achieving proactive maintenance to prevent problems before they occur. The specific beneficial effects are as follows: 1) Accurately Identifying User-Side Power Outages and Eliminating Monitoring Blind Spots: This invention obtains an online user list by polling the broadband access server at a preset fixed period, reducing the granularity of user online status monitoring from the traditional device level to the individual user account level. Offline users are accurately identified through periodic comparisons. Furthermore, a pre-configured device mapping table is used to establish the association between user accounts and OLT devices. A status query request carrying an offline user identifier is proactively sent to the OLT to obtain the user-end device offline reason code recorded in the OLT's underlying protocol. This offline reason code can accurately distinguish between power outage causes and non-power outage causes (such as fiber optic cable faults, equipment crashes, and normal user shutdowns), effectively compensating for the physical blind spots of traditional power monitoring systems that cannot cover the "last hundred meters" of faults behind the user's electricity meter. It provides a reliable logical criterion for distinguishing between fault-related power outages and normal no-load states, achieving accurate root cause localization of user-side power outage faults.

[0016] 2) Proactive Identification and Early Alarms for Improved Timeliness and User Satisfaction: This invention employs a fixed-period automatic polling mechanism, triggering the detection process the moment offline occurs without waiting for user reports. Suspected power outage users are quickly identified through real-time parsing of offline cause codes. Furthermore, continuous offline duration monitoring eliminates transient anomalies such as momentary power outages and equipment restarts. An alarm is generated when the continuous offline duration exceeds a preset threshold. This mechanism significantly advances fault detection to before users notice and report the fault, enabling maintenance personnel to intervene early, proactively care for users, or pre-schedule repair resources. This significantly shortens the time lag between fault occurrence and maintenance response, improving the timeliness of fault handling and effectively enhancing user satisfaction.

[0017] 3) Reduced Operation and Maintenance Costs and Improved Resource Scheduling Efficiency: This invention implements power outage alarms entirely based on the broadband network's own operation and maintenance data, eliminating reliance on external data interfaces from the power sector and avoiding the complexity and data latency issues associated with cross-system integration. Simultaneously, through a dual filtering mechanism of offline cause code parsing and continuous offline duration determination, invalid alarms caused by non-power outage factors such as normal user shutdowns, equipment restarts, and fiber optic cable failures are effectively eliminated, significantly reducing the workload of maintenance personnel in unnecessary troubleshooting. In large-scale power outage scenarios, the system can quickly pinpoint the affected user area, supporting precise scheduling and prioritization of operation and maintenance resources, significantly reducing operation and maintenance costs and improving overall operation and maintenance efficiency.

[0018] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0019] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used together with the embodiments of the invention to explain the invention and do not constitute a limitation thereof. The above and other features and advantages will become more apparent to those skilled in the art from the detailed description of exemplary embodiments with reference to the accompanying drawings, in which: Figure 1 This is a schematic diagram of a user-side power outage alarm method provided in an embodiment of the present invention; Figure 2 A framework diagram of a user-side power outage alarm provided in an embodiment of the present invention; Figure 3 This invention provides a data collection intent for user-side power outage alarms in an embodiment of the invention. Figure 4 This is a schematic diagram illustrating the fault determination of a user-side power outage alarm provided in an embodiment of the present invention. Figure 5 This is a schematic diagram illustrating the alarm information push and processing for user-side power outage alarms provided in an embodiment of the present invention; Figure 6 A schematic diagram of a user-side power outage alarm device provided in an embodiment of the present invention; Figure 7 A framework diagram of an electronic device provided in an embodiment of the present invention.

[0020] Reference numerals: 10, polling unit; 20, comparison unit; 30, first query unit; 40, second query unit; 50, processing unit; 60, alarm generation unit; 100, processor; 200, memory. Detailed Implementation

[0021] It is understood that the specific embodiments and accompanying drawings described herein are merely for explaining the invention and are not intended to limit the invention.

[0022] It is understood that, without conflict, the various embodiments and features in the embodiments of the present invention can be combined with each other.

[0023] It is understood that, for ease of description, only the parts related to the present invention are shown in the accompanying drawings, while the parts unrelated to the present invention are not shown in the drawings.

[0024] It is understood that each unit or module involved in the embodiments of the present invention may correspond to only one entity structure, or may be composed of multiple entity structures, or multiple units or modules may be integrated into one entity structure.

[0025] It is understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of this invention may occur in a different order than that marked in the accompanying drawings.

[0026] It is understood that the flowcharts and block diagrams of this invention illustrate the possible architecture, functions, and operations of systems, apparatuses, devices, and methods according to various embodiments of this invention. Each block in the flowchart or block diagram may represent a unit, module, program segment, or code, containing executable instructions for implementing the specified function. Furthermore, each block or combination of blocks in the block diagram and flowchart can be implemented using a hardware-based system to achieve the specified function, or using a combination of hardware and computer instructions.

[0027] It is understood that the units and modules involved in the embodiments of the present invention can be implemented by software or by hardware. For example, the units and modules can be located in a processor.

[0028] Example 1: like Figure 1 As shown, this embodiment provides an alarm method for user-side power outages. This method can be applied to the daily operation and maintenance scenarios of broadband networks of telecommunications operators. When a power outage occurs on the user side, causing network equipment such as optical line terminal equipment to go offline, the alarm platform, through linkage with the broadband access server and optical line terminal equipment, periodically and proactively polls and compares to filter out offline users, queries across devices to obtain offline reason codes to accurately identify the actual power outage status, and automatically generates alarm information for users whose continuous offline time reaches a judgment threshold. Thus, it achieves early detection of power outage faults and proactive operation and maintenance dispatch before users notice the network interruption and report the fault. This method is applied to the alarm platform and includes steps S1 to S6.

[0029] Step S1: Send polling requests to the broadband access server at a preset fixed period and receive the list of online users returned by the broadband access server.

[0030] As a specific implementation method, this embodiment sends polling requests to the broadband access server at a preset fixed period and receives the online user list returned by the broadband access server. Specifically, it includes the following steps: According to a preset polling cycle, polling requests are periodically sent to the management interface of the broadband access server to query user online status. This embodiment receives raw online session data returned by the broadband access server based on the polling requests. This embodiment parses, cleans, and structures the raw online session data, extracts the account information of currently online users, and generates a list of online users.

[0031] Step S2: Compare the current period's online user list with the previous period's online user list, and filter out offline users who do not appear in the current period's online user list.

[0032] Step S3: Based on the offline user's account information, search the pre-configured device mapping table to determine the optical line terminal device to which the offline user belongs.

[0033] As a specific implementation, before searching the pre-configured device mapping table based on the offline user's account information, this embodiment further includes: determining whether the offline user is a periodically offline user. If so, the offline user's historical offline records are obtained, and the periodic offline characteristic value of the offline user is calculated based on the historical offline records. If the periodic offline characteristic value exceeds a preset periodic offline threshold, the offline user is removed from the query queue, and the step of searching the pre-configured device mapping table is no longer executed.

[0034] Step S4: Send a user status query request carrying the offline user identifier to the optical line terminal equipment, and receive the user terminal equipment offline reason code returned by the optical line terminal equipment.

[0035] As a specific implementation, this embodiment sends a user status query request carrying an offline user identifier to the optical line terminal equipment and receives the user terminal equipment offline reason code returned by the optical line terminal equipment, specifically including the following steps: First, a user status query request is generated based on the offline user identifier. This request carries the offline user identifier and a query instruction identifier, whereby the query instruction identifier instructs the optical line terminal equipment (OLT) to perform an offline cause query operation. Then, the user status query request is sent to the OLT. Upon receiving the request, the OLT responds to the query instruction identifier by querying its local database or cache for the offline cause code of the user terminal equipment corresponding to the offline user identifier. Finally, the OLT receives the offline cause code of the user terminal equipment returned by the OLT. The offline cause code includes at least one of the following: power outage cause code, fiber optic link interruption cause code, equipment failure cause code, and user-initiated offline cause code, thereby accurately pinpointing the root cause of the user terminal equipment's offline status.

[0036] Step S5: If the offline reason code indicates a power outage, then mark the offline user as a suspected power outage user.

[0037] Step S6: Monitor the continuous offline time of suspected power outage users. When the continuous offline time exceeds the preset judgment threshold, generate alarm information.

[0038] As a specific implementation method, continuous offline time monitoring is performed on users suspected of experiencing power outages. When the continuous offline time exceeds a preset threshold, an alarm message is generated. Specifically, this includes: first, establishing an offline monitoring task for the suspected power outage user and updating the continuous offline time of the suspected power outage user according to a preset monitoring update cycle; then, determining whether the updated continuous offline time exceeds the preset threshold; if so, obtaining the user attribute information of the suspected power outage user, encapsulating the user attribute information with the continuous offline time, and generating an alarm message. This embodiment, by establishing an offline monitoring task and periodically updating the continuous offline time, can monitor the changes in the offline status of suspected power outage users in real time and trigger an alarm promptly when the offline time exceeds the preset threshold. Simultaneously, encapsulating the user attribute information with the continuous offline time makes the generated alarm information more complete and accurate, facilitating rapid identification of the user and targeted handling, thereby effectively improving the response efficiency and processing accuracy of suspected power outage events.

[0039] As a specific implementation method, the method further includes: acquiring multiple target users marked as suspected power outage users within a preset time window, and extracting the geographic coordinate information of each target user. Based on the extracted geographic coordinate information, spatial clustering analysis is performed on the multiple target users to determine the spatial clustering area to which each target user belongs. Further, the number of target users in each spatial clustering area is counted, and the offline density ratio of target users in each spatial clustering area to the total number of users in the corresponding spatial clustering area is calculated. Subsequently, the calculated offline density ratio is compared with a preset regional fault density threshold. If the offline density ratio exceeds the regional fault density threshold, a regional fault alarm is generated, and the generated regional fault alarm is pushed to the operation and maintenance management platform.

[0040] As a specific implementation method, after generating alarm information, the method of this embodiment further includes the following steps: First, the geographical information of the area where the suspected power outage user is located is obtained, and based on this geographical information, a query is performed to see if there are any reported power outage plans within that area. If the query results show that there are reported power outage plans, the outage time of the suspected power outage user is further compared with the time window of the reported power outage plan. If the outage time of the suspected power outage user falls within the time window of the reported power outage plan, the alarm information is marked as a planned power outage alarm, and the planned power outage alarm is pushed to the planned power outage management unit of the operation and maintenance management platform. If the query results show that there are no reported power outage plans, the alarm information is marked as a fault power outage alarm, and the fault power outage alarm is pushed to the fault repair unit of the operation and maintenance management platform.

[0041] As a specific implementation method, this embodiment includes the following processing steps after generating the alarm information: First, obtain the user identity information and geographical location information corresponding to the alarm information. Second, reversibly encrypt the obtained geographical location information using a reversible encryption algorithm to generate encrypted geographical location information, ensuring the security of geographical location data during transmission while retaining the possibility of subsequent decryption and restoration under authorized conditions. Next, desensitize the user identity information using an irreversible hash algorithm to generate a desensitized user identifier, thereby effectively avoiding the direct leakage of the original user identity information while ensuring the user's identity is associated. Subsequently, the encrypted geographical location information, the desensitized user identifier, and the power outage timestamp contained in the alarm information are uniformly encapsulated to generate a standardized alarm data packet, achieving data format standardization and consistency in subsequent processing. Finally, the alarm data packet is pushed to the power supply operation and maintenance management platform through a secure transmission protocol, completing the reliable delivery of the alarm information.

[0042] This embodiment utilizes a bottom-up, hierarchical four-layer technical architecture to achieve closed-loop management of the entire chain, from bottom-level data acquisition to top-level business applications. The overall architecture covers four levels: data acquisition, core processing, alarm judgment, and data push services. Details of the functional modules, flow logic, and data exchange types for each level can be found in [link to documentation]. Figure 2 Architecture flowchart.

[0043] The first level is the data acquisition level: global awareness and persistent storage.

[0044] This layer relies on the BAS (Building Automation System) equipment of telecom operators to construct a real-time, full-domain sensing network. In implementation, customized automated data collection scripts are deployed, and a polling mechanism with a five-minute cycle is set to automatically traverse and capture raw data on the online status of all optical line terminal equipment (OLTP) devices across the network. All collected raw data is written to a dedicated time-series database for persistent storage in real time. This layer consists of three main units: operator BAS equipment, automated data collection scripts, and a time-series database. It outputs raw OLTP status data to provide a data source for downstream analysis.

[0045] Specifically, this embodiment employs high-frequency data acquisition. The acquisition target is the online status data of all broadband users in the broadband access server (BAS) of the telecommunications operator. The acquisition method involves an automated script that automatically logs into the BAS to crawl data at a high frequency of 5 minutes. Following the interface logic of this embodiment, regular expressions and JSON tools are used to match online user information and store it in a time-series database. The data acquisition process is as follows: Figure 3As shown, the specific process includes: after the initial stage, a scheduled task is started and executed every 5 minutes; then, the system logs into the operator's network management system; next, it crawls the online list of optical line terminal equipment across the entire network; then, it performs data cleaning and standardization processing; next, it stores the processed data in a time-series database; finally, it waits for the next cycle, and if the conditions are met, it returns to continue executing the scheduled task. In this process, this embodiment first integrates the operator's Broadband Access Server (BAS) interface to establish a stable data channel. Secondly, it sets a 5-minute collection cycle to monitor changes in the online status of broadband users across the entire network in real time. Finally, it performs preliminary cleaning and standardization processing on the acquired raw online user data and stores it in the basic database.

[0046] The second level, the core processing level: offline identification and cause verification.

[0047] This layer, as the core of the algorithm, integrates two major processing units: status comparison and OLT query, implementing offline identification and cause verification logic. First, it compares the online user list collected in the current period with the data from the previous period item by item, accurately filtering out users who were "online in the previous period but offline in the current period." Then, it automatically sends a query command to the OLT device for this group to verify the offline labeling information on the device side. If the device returns an identifier of "power outage," the user is determined to be a suspected power outage user, and a suspected power outage list is generated and passed to the next stage. This layer receives the raw optical line terminal equipment status data from upstream and outputs a structured suspected power outage list.

[0048] The third level is the alarm determination level: event determination and security encapsulation.

[0049] This layer is configured with a rule engine and data encryption unit, responsible for accurate determination of power outage events and data security. The processing logic is as follows: Based on preset alarm rules, it continuously monitors users suspected of experiencing power outages. When a user's continuous offline time exceeds a preset threshold (e.g., ten minutes), an alarm mechanism is formally triggered. Simultaneously, this layer standardizes and encapsulates the alarm information and performs full data encryption, generating encrypted alarm data packets for transmission downstream. This layer receives a list of suspected power outages from upstream and outputs encrypted alarm data packets.

[0050] Specifically, the fault alarm and judgment process in this embodiment is as follows: (1) Establish a multi-dimensional fault identification and judgment mechanism to analyze and judge offline events of optical line terminal equipment. The specific process is as follows: Figure 4 As shown.

[0051] 1) In this embodiment, the data acquisition engine performs the task of collecting and storing the online user list according to a fixed cycle. At cycle T-1, the collected online user list snapshot is stored in the time-series database. At cycle T, the current online user list snapshot is stored in the time-series database again. Subsequently, the status comparison engine retrieves the two lists from the time-series database for cycles T-1 and T, and compares them using a "previous list present, subsequent list absent" rule to quickly filter out users who have gone offline within the last 5 minutes.

[0052] 2) Based on this, this embodiment associates the OLT resource information (OLT, PON port and ONUID) of the offline user, thereby providing accurate positioning basis for subsequent optical line terminal equipment status collection.

[0053] 3) Next, the status comparison engine automatically logs into the OLT network management system of each offline user and collects the status of their optical line terminal equipment.

[0054] 4) Subsequently, the status comparison engine determines the cause of offline status one by one. For each offline user, it queries the OLT network management system for the cause of offline status of the user's optical line terminal equipment. The OLT network management system returns the cause of offline status (e.g., Power Off or LOS). If the cause of offline status is "Power Off", the user is marked as a "suspected power outage user". If the cause of offline status is other (e.g., LOS), it is excluded and determined to be a communication failure.

[0055] 5) After the initial marking is completed, continuous monitoring is started for users suspected of power outage. When the continuous offline time exceeds the preset judgment threshold (such as 10 minutes), this embodiment automatically updates their status to "confirmed power outage" and triggers an alarm push.

[0056] (2) Secure push and closed-loop processing of alarm information. The process is as follows: Figure 5 As shown, the sequence from beginning to end is: Start, Data Retrieval, API Push, Receive Decryption, User Matching, Work Order Generation, Work Order Dispatch and Processing, Result Feedback, End.

[0057] 1) After confirming the power outage, this embodiment encrypts the data packets of the "confirmed power outage" user in real time using the AES algorithm.

[0058] 2) Subsequently, the encrypted data packet is pushed to the API interface designated by the power company via the HTTPS protocol.

[0059] 3) The power company receives and decrypts the data, uses the MD5 hash value of the mobile phone number to perform a collision match with its own user profile, and associates it with the specific electricity meter account in order to conduct further comparison and association of user electricity meter data.

[0060] 4) If the power supply company makes a comprehensive judgment and rules out the problem of regional power outage, and the user's electricity meter has indeed recently experienced a "sudden drop in current to 0", then it will generate an emergency repair work order and dispatch it to the on-site maintenance personnel.

[0061] 5) After completing the emergency repair, the maintenance personnel will report the results. This embodiment can record the validity of alarms for algorithm optimization.

[0062] (3) Data security and privacy protection: Encrypted transmission, information anonymization, and digital signature verification ensure the compliance and security of the entire process. This embodiment generates standardized data packets, which include the following main contents: a) User's real-name registration installation address (for precise location).

[0063] b) The cell / grid in which it is located (for regional fault analysis).

[0064] c) The MD5 hash of the user's mobile phone number (used as a "keyword" for the power company to associate with the user in this embodiment, while protecting privacy).

[0065] d) The precise timestamp of the "power off" status of the optical line terminal equipment.

[0066] Example of pushed user information content (JOSN format): [{'tdbh': '20251009171839', #serial number] 'xqmc': 'GCGtzTmQ0R4mjDg3oilO / uDMZPZMtLMhDYOYue9g6KNYWFvjeuFtQ==', #AES encrypted cell name 'yhdz': 'GCGtzTmQ0Rg3ofRBs3pGxrjBwV8gkgsYSq / Jp9HGVtZOa9JFT1fmxScIkP2UNeRgF0pZ2A8=', #AES encrypted user address 'tdkssj': '2025-10-09 17:06:19', #User power outage time 'yhhm': '1C076230D62EC33C3B91450369D0E895' #user's mobile phone number after MD5 hash} ...... The fourth level is the data push and service level: interface interaction and delivery.

[0067] As the external data exchange outlet, this layer connects with the power supply company's service management platform via a dedicated API interface. The specific process is as follows: it receives encrypted alarm data packets from upstream, performs secure parsing via a standardized API interface, and pushes the processed data to the power supply company's service management platform in real time, ultimately achieving a closed-loop delivery of power outage alarm information from the communication network to the power business system. This layer is responsible for the final data distribution and implementation across the entire chain.

[0068] The overall business process in this embodiment proceeds sequentially step by step: it begins at the data acquisition layer, where BAS devices, in conjunction with scripts, complete data acquisition, storage, and archiving; it flows through the core processing layer, generating a suspected data list through cross-cycle comparison and OLT verification; it then moves to the alarm judgment layer, determining events based on duration thresholds and completing encrypted encapsulation; finally, it concludes at the data push layer, delivering data to the power company in real time via API interfaces. The entire chain fully realizes automated operations from data capture, anomaly identification, intelligent analysis to real-time information push.

[0069] Furthermore, existing fault monitoring methods for optical line terminal equipment (OLT) mostly focus on the offline characteristics of individual user devices for judgment and alarm. They can only push alarms after the offline time of a single OLT reaches a preset threshold, resulting in shortcomings such as delayed fault perception and difficulty in early detection of potential regional common faults. To address this, this embodiment proposes an early regional fault identification method based on the offline spatiotemporal patterns of group OLTs. In addition to achieving accurate anomaly alarms for individual user devices, it deeply mines the group linkage effect contained in the massive offline time-series and spatial correlation data of OLTs. This enables proactive and macroscopic judgment of small regional faults such as community power outages, building main circuit breaker tripping, and building main line interruptions. It can generate regional-level fault alarm signals in advance, before users initiate fault reporting and before the single device offline judgment cycle is completed, significantly shortening the fault detection and response delay. The specific implementation logic of this method is as follows: User groups are divided into spatial units such as communities, buildings, and vertical units. The online / offline timing data of all users' optical line terminal devices within the same spatial range are aggregated in real time. The concurrent events of multiple optical line terminal devices going offline simultaneously within the area are continuously monitored and statistically analyzed. Spatiotemporal joint discrimination rules are constructed by combining time windows and geographical range. If the scale and concurrency density of synchronous offline events of optical line terminal devices reach the preset judgment criteria within the defined spatiotemporal interval, even if the offline time of a single optical line terminal device does not reach the single user alarm threshold, the system will automatically determine that there is a suspected common power supply / line fault in the area and immediately trigger a regional early alarm. At the same time, alarm information such as the area location, the scale of offline users, and the suspected fault type are pushed to the power operation and maintenance platform to remind front-line operation and maintenance personnel to prioritize checking the status of power supply lines, distribution switches, and other facilities in the area. Relying on the proactive perception capability, the fault handling is transformed from passive reporting and emergency repair to proactive prediction and early intervention, effectively reducing the scope of fault impact and reducing the duration of user network outages.

[0070] This embodiment integrates visualization capabilities with actual power operation and maintenance (O&M) business applications. It relies on two core models: standardized API data push and integration with power supply company platforms. This enables comprehensive visualization capabilities, empowering power O&M management in all aspects. Core business functions cover three dimensions: situation visualization, refined alarms, and intelligent data analysis. Specifically, the regional power outage overview view uses massive amounts of data collected offline by optical line terminal equipment for intelligent automatic calculation, accurately generating regional power outage heat maps. Simultaneously, the visualized data is pushed to the power supply company's O&M management screen, providing real-time, full-area presentation of the overall power outage situation within the jurisdiction. This allows O&M managers to intuitively and clearly grasp the scale of power outage coverage and fault location distribution in each area, achieving global visibility and controllable situational awareness of power outages. The power outage alarm information list can receive user-level power outage alarm data pushed from upstream platforms in real time, uniformly collecting, organizing, and centrally displaying various alarm information. The list completely retains key business fields such as detailed user addresses, predicted outage time periods, and core fault causes, effectively... It helps frontline maintenance personnel quickly identify the affected users during power outages, enabling them to proactively conduct fault diagnosis and handling, and inform and reassure users, significantly improving the initiative and efficiency of power outage emergency response. The multi-dimensional statistical analysis reports have the capability to automatically generate periodic reports, covering a wide range of detailed data statistics, including total alarm statistics, fault frequency rankings for different regions, and alarm prediction accuracy verification analysis. This allows for precise quantification of the effectiveness of daily fault handling and alarm management, providing comprehensive, objective, and accurate data support for various management decisions such as power maintenance dispatch coordination, team performance evaluation, and maintenance strategy optimization, thus fully supporting the digital, refined, and intelligent upgrading of power maintenance work.

[0071] This embodiment constructs a cross-domain collaborative alarm scheme, aiming to effectively solve the three core problems commonly found in user-side power fault monitoring: perception blind spots, high false alarm rates, and passive response. Specifically, at the data acquisition level, this embodiment adopts an offline list collection technology based on active polling of the broadband access server (BAS). Addressing the data latency, data loss, and unstructured format issues inherent in traditional passive syslog monitoring methods, an active collection system is constructed. Through a programmatic interface, queries are initiated directly to the BAS at fixed intervals to obtain a structured offline user list, ensuring the timeliness and accuracy of the data from the source. This achieves the step of directly obtaining a structured offline user list through active, periodic polling of the BAS.

[0072] At the fault diagnosis level, this embodiment introduces a precise diagnostic method based on OLT reason codes, aiming to solve the problem of misjudgment often caused by non-power outage factors such as communication line faults and user-initiated shutdown. When device offline is detected, this embodiment can penetrate and query the underlying offline reason codes recorded by the operator's OLT equipment, and establish judgment rules, using the event with the reason code "poweroff" as direct evidence of a power outage on the user side. Thus, it includes the necessary steps of determining whether a power outage has occurred on the user side by querying the user-end device offline reason codes recorded in the operator's OLT equipment.

[0073] To construct a progressively converging, multi-dimensionally verified decision-making process to eliminate transient fluctuation interference and ensure the high reliability and accuracy of the final alarm, this embodiment designs a decision-making model, namely a three-level progressive collaborative filtering model. This model implements a three-level progressive decision-making process of "discovery-confirmation-determination": first, offline anomalies are discovered through inventory comparison; second, the power outage is confirmed through OLT reason codes; and finally, the duration of monitoring is used to determine whether it is a stable fault requiring action. The protection point of this embodiment lies in a power fault decision-making model, the decision-making process of which sequentially includes an offline discovery step for optical line terminal equipment based on state comparison, a power outage event confirmation step based on OLT reason codes, and a final alarm triggering step based on duration.

[0074] Regarding data security, this embodiment effectively balances operational and privacy protection through dual encapsulation, resolving the conflict between the operational needs for "precise positioning" and the legal boundaries of "user privacy" in cross-industry data collaboration. This embodiment employs a hierarchical security encapsulation strategy, reversibly encrypting the address information necessary for emergency repairs to ensure repair efficiency, while irreversibly hashing and desensitizing user identification information to anonymize privacy data. This results in reversibly encrypting the geographical location information in alarm messages and irreversibly hashing and desensitizing the user's personal identification information.

[0075] Furthermore, this embodiment also includes a closed-loop architecture design for alarms, integrating discrete technical points into a highly automated, end-to-end business solution, realizing unmanned closed-loop management from fault detection to emergency repair dispatch. This architecture constructs a system integrating data acquisition, analysis and judgment, security encapsulation, and work order push functions, and is driven by business flow to automatically complete the conversion and transmission of emergency repair instructions from the communication side to the power side.

[0076] Finally, this embodiment expands the application scope to include an early identification method for regional faults based on the spatiotemporal patterns of offline optical line terminal equipment (OLTP) devices. Building upon accurate alarms for individual households, this embodiment further enables early, macroscopic perception of faults in small-scale areas such as power distribution units and buildings, improving the comprehensiveness and predictability of alarms. This embodiment can perform density and scale analysis on group OLTP device offline events identified as "power outages" within a specific spatiotemporal range. When the preset group fault characteristics are met, a regional fault alarm is immediately triggered even if the individual household duration threshold is not reached. Specifically, this embodiment performs spatiotemporal statistical analysis on multiple OLTP device offline events due to power outages. When the results meet the preset group fault characteristics, a regional fault alarm is generated. Group fault characteristics include: within a preset time period, within a specific geographical area, the occurrence of OLTP device offline events exceeding a threshold and possessing a power outage cause code.

[0077] Example 2: like Figure 6 As shown, this embodiment provides a user-side power outage alarm device. The device is applied to an alarm platform and includes: a polling unit 10, a comparison unit 20, a first query unit 30, a second query unit 40, a processing unit 50, and an alarm generation unit 60.

[0078] The polling unit 10 is used to send polling requests to the broadband access server according to a preset fixed period, and to receive the online user list returned by the broadband access server and send the online user list to the comparison unit.

[0079] The comparison unit 20 is connected to the polling unit 10 and is used to compare the online user list of the current period with the online user list of the previous period, filter out offline users that do not appear in the online user list of the current period, and send the information of the offline users to the first query unit 30.

[0080] The first query unit 30 is connected to the comparison unit 20 and is used to search the pre-configured device mapping table based on the account information of the offline user, determine the optical line terminal device to which the offline user belongs, and send the information of the optical line terminal device to the second query unit 40.

[0081] The second query unit 40 is connected to the first query unit 30 and is used to send a user status query request carrying an offline user identifier to the optical line terminal equipment, receive the offline reason code of the user terminal equipment returned by the optical line terminal equipment, and send the offline reason code to the processing unit 50.

[0082] The processing unit 50 is connected to the second query unit 40 and is used to mark the offline user as a suspected power outage user when the offline reason code indicates a power outage reason, and send the information of the suspected power outage user to the alarm generation unit 60.

[0083] The alarm generation unit 60 is connected to the processing unit 50 and is used to monitor the continuous offline time of suspected power outage users. When the continuous offline time exceeds the preset judgment threshold, an alarm message is generated.

[0084] The apparatus in this embodiment is capable of performing the method in Embodiment 1.

[0085] Example 3: like Figure 7 As shown, this embodiment provides an electronic device, which includes a memory 200 and a processor 100. The memory 200 stores a computer program. When the processor 100 runs the computer program stored in the memory 200, the processor 100 executes the alarm method for user-side power outage according to Embodiment 1.

[0086] It is understood that the above embodiments are merely exemplary implementations used to illustrate the principles of the present invention, and the present invention is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and essence of the present invention, and these modifications and improvements are also considered to be within the scope of protection of the present invention.

Claims

1. A method of alerting of a user side power failure, characterized by, The method is applied to an alarm platform and includes: The system sends polling requests to the broadband access server at a preset fixed period and receives the list of online users returned by the broadband access server. The online user list for the current period is compared with the online user list for the previous period to filter out offline users who do not appear in the online user list for the current period. Based on the account information of the offline user, the pre-configured device mapping table is searched to determine the optical line terminal device to which the offline user belongs; Send a user status query request carrying the offline user identifier to the optical line terminal equipment, and receive the user terminal equipment offline reason code returned by the optical line terminal equipment; If the offline reason code indicates a power outage, then the offline user is marked as a suspected power outage user; The system monitors the continuous offline time of suspected power outage users, and generates an alarm message when the continuous offline time exceeds a preset threshold.

2. The alarm method for user-side power outage according to claim 1, characterized in that, The step of sending polling requests to the broadband access server at a preset fixed period and receiving the online user list returned by the broadband access server specifically includes: According to the preset polling cycle, polling requests are periodically sent to the management interface of the broadband access server to query the user's online status; Receive the raw online session data returned by the broadband access server based on the polling request; The original online session data is parsed, cleaned, and structured to extract the account information of the current online users and generate the online user list.

3. The alarm method for user-side power outage according to claim 1, characterized in that, The step of sending a user status query request carrying the offline user identifier to the optical line terminal equipment and receiving the user terminal equipment offline reason code returned by the optical line terminal equipment specifically includes: A user status query request is generated based on the offline user identifier, and the user status query request carries the offline user identifier and the query instruction identifier. The user status query request is sent to the optical line terminal device. The optical line terminal device responds to the query instruction identifier and queries the offline reason code of the user terminal device corresponding to the offline user identifier. The system receives an offline reason code for the user terminal equipment returned by the optical line terminal equipment. The offline reason code includes at least one of the following: power failure reason code, optical fiber link interruption reason code, equipment failure reason code, and user-initiated offline reason code.

4. The alarm method for user-side power outage according to claim 1, characterized in that, Before searching the pre-configured device mapping table based on the offline user's account information, the method further includes: Determine whether the offline user is a periodically offline user; If so, then obtain the historical offline records of the offline user, and calculate the periodic offline feature value of the offline user based on the historical offline records; If the periodic offline characteristic value exceeds the preset periodic offline threshold, the offline user will be removed from the query queue, and the step of searching the pre-configured device mapping table will no longer be executed.

5. The alarm method for user-side power outage according to claim 1, characterized in that, The step of monitoring the continuous offline time of the suspected power outage users, and generating alarm information when the continuous offline time exceeds a preset judgment threshold, specifically includes: An offline monitoring task is established for the suspected power outage users, and the continuous offline duration of the suspected power outage users is updated according to a preset monitoring update cycle; Determine whether the updated continuous offline duration exceeds the preset judgment threshold; If so, the user attribute information of the suspected power outage user is obtained, and the user attribute information and the continuous offline duration are encapsulated to generate the alarm information.

6. The user side power interruption warning method of claim 1, wherein, The method further includes: Get multiple target users marked as suspected power outage users within a preset time window, and extract the geographic coordinate information of each target user; Based on the geographic coordinate information, spatial clustering analysis is performed on multiple target users to determine the spatial clustering region to which each target user belongs; The number of target users in each spatial cluster region is counted, and the offline density ratio of target users in each spatial cluster region to the total number of users in the corresponding spatial cluster region is calculated. The offline density ratio is compared with a preset regional fault density threshold. If the offline density ratio exceeds the regional fault density threshold, a regional fault alarm is generated and pushed to the operation and maintenance management platform.

7. The alarm method for user-side power outage according to claim 1, characterized in that, After generating the alarm information, the method further includes: Obtain the geographic information of the area where the suspected power outage user is located, and query whether there are any reported power outage plans in the area based on the geographic information; If there are reported power outage plans, compare the power outage time of suspected power outage users with the time window of the reported power outage plans; If the power outage time falls within the time window of the reported power outage plan, the alarm information will be marked as a planned power outage alarm, and the planned power outage alarm will be pushed to the planned power outage management unit of the operation and maintenance management platform. If there is no reported power outage plan, the alarm information will be marked as a power outage alarm and the power outage alarm will be pushed to the fault repair unit of the operation and maintenance management platform.

8. The alarm method for user-side power outage according to any one of claims 1 to 7, characterized in that, After generating the alarm information, the method further includes: Obtain the user identification information and geographical location information corresponding to the alarm information; The geographic location information is reversibly encrypted using a reversible encryption algorithm to generate encrypted geographic location information; The user identification information is de-identified using an irreversible hash algorithm to generate a de-identified user identifier; The encrypted geographic location information, the de-identified user identifier, and the power outage timestamp in the alarm information are encapsulated to generate a standardized alarm data packet; The alarm data packet is pushed to the power supply operation and maintenance management platform through a secure transmission protocol.

9. A user-side power outage alarm device, characterized in that, The device is used in an alarm platform and includes: The system includes a polling unit, a comparison unit, a first query unit, a second query unit, a processing unit, and an alarm generation unit. The polling unit is used to send polling requests to the broadband access server according to a preset fixed period, receive the online user list returned by the broadband access server, and send the online user list to the comparison unit. The comparison unit, connected to the polling unit, is used to compare the online user list of the current period with the online user list of the previous period, filter out offline users that do not appear in the online user list of the current period, and send the information of the offline users to the first query unit. The first query unit, connected to the comparison unit, is used to search a pre-configured device mapping table based on the account information of the offline user, determine the optical line terminal device to which the offline user belongs, and send the information of the optical line terminal device to the second query unit; The second query unit, connected to the first query unit, is used to send a user status query request carrying the offline user identifier to the optical line terminal equipment, and receive the offline reason code of the user terminal equipment returned by the optical line terminal equipment, and send the offline reason code to the processing unit. The processing unit, connected to the second query unit, is used to mark the offline user as a suspected power outage user when the offline reason code indicates a power outage reason, and to send the information of the suspected power outage user to the alarm generation unit. The alarm generation unit is connected to the processing unit and is used to monitor the continuous offline time of the suspected power outage user. When the continuous offline time exceeds a preset judgment threshold, an alarm message is generated.

10. An electronic device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor executes the alarm method for user-side power outage according to any one of claims 1 to 8.

Images