Metering equipment management method, computer equipment, storage medium and program product

Abstract

The invention discloses a metering equipment management method, computer equipment, a storage medium and a program product, and relates to the technical field of equipment management, and the method comprises the steps: determining target user field information corresponding to user login information in a geographic information model; target area field information and target role field information are determined in the geographic information model according to the target user field information, a target area and a user area permission are determined according to the field information, and the to-be-managed device in the target area is managed according to the user area permission. The problems that the regional management mode of the metering equipment is too wide, the user authority is disordered, and cross-regional management of the metering equipment is difficult can be solved. According to the method, a regional management mode is refined, roles and regions are bound to users, and regional permissions are granted to the users, so that the users with the permissions can conveniently carry out cross-regional management on the metering equipment. And accurate authorization is carried out on the user based on the role and the region, so that the unauthorized operation is effectively prevented, and the data security is fundamentally guaranteed.

Description

Technical Field

[0001] The present invention relates to the technical field of equipment management, and in particular to a metering equipment management method, computer equipment, storage medium and program product. Background Art

[0002] Metering equipment primarily includes specialized instruments for geometry, temperature, mechanics, and electricity. Metering equipment is common in factories and workshops, numerous and widely installed. Traditionally, the regional management model for metering equipment has been overly broad, categorizing metering equipment by department or type. This has led to confusing user permissions and complicated cross-regional scheduling and status monitoring of metering equipment.

[0003] Therefore, the related technology has the problem that the regional management mode of metering equipment is too broad, user authority is confusing, and it is difficult to manage metering equipment across regions. Summary of the Invention

[0004] In view of this, the present invention provides a metering equipment management method, computer equipment, storage medium and program product to solve the problem that the regional management mode of metering equipment is too broad, user authority is confusing, and it is difficult to manage metering equipment across regions.

[0005] In a first aspect, the present application provides a method for managing a metering device, the method comprising: Determining target user field information corresponding to user login information in a geographic information model, and obtaining a region character and a role character from the target user field information, wherein the geographic information model is generated based on the user field information, the role field information, and the region field information; Determine target region field information in the geographic information model based on the region character, and determine target role field information in the geographic information model based on the role character; Determine the target region in the preset region hierarchy of the geographic information model based on the node character and the level character in the target region field information, and determine the user region authority based on the authority character in the target role field information; Manage the devices to be managed in the target area according to the user's area permissions.

[0006] In a second aspect, the present application provides a metering equipment management device, the device comprising: a character acquisition module, configured to determine target user field information corresponding to user login information in a geographic information model, and to acquire region characters and role characters from the target user field information, wherein the geographic information model is generated based on the user field information, the role field information, and the region field information; An information determination module, configured to determine target region field information in a geographic information model based on region characters, and to determine target role field information in a geographic information model based on role characters; The authority determination module is used to determine the target area in the preset area hierarchy of the geographic information model according to the node character and the level character in the target area field information, and determine the user area authority according to the authority character in the target role field information; The device management module is used to manage the devices to be managed in the target area according to the user's area authority.

[0007] In a third aspect, the present application provides a computer device comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, computer instructions being stored in the memory, and the processor executing the metering equipment management method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0008] In a fourth aspect, the present application provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the metering equipment management method of the first aspect or any corresponding embodiment thereof.

[0009] In a fifth aspect, the present application provides a computer program product, comprising computer instructions, which are used to enable a computer to execute the metering equipment management method of the above-mentioned first aspect or any corresponding embodiment thereof.

[0010] Through this application, since the method determines the target user field information corresponding to the user login information in the geographic information model; determines the target area field information and the target role field information in the geographic information model based on the target user field information; determines the target area based on the target area field information, determines the user area authority based on the target role field information, and manages the equipment to be managed in the target area based on the user area authority. It can solve the problem that the regional management mode of metering equipment is too broad, the user authority is confusing, and it is difficult to manage metering equipment across regions. The method manages regions at multiple levels, refines the regional management mode, and, by binding users to roles and regions, granting users corresponding user area authorities, it is convenient for users with authority to manage metering equipment across regions. Accurately authorize users based on roles and regions, effectively prevent unauthorized operations, and fundamentally ensure data security. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the specific implementation methods of this application or the technical solutions in related technologies, the following is a brief introduction to the drawings required for use in the specific implementation methods or related technical descriptions. Obviously, the drawings described below are some implementation methods of this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0012] Figure 1 is a flow chart of a method for managing metering equipment according to an embodiment of the present application; Figure 2 is a schematic diagram of a geographic information model according to an embodiment of the present application; Figure 3 is a flowchart of uploading a metering report according to an embodiment of the present application; Figure 4 This is a flow chart of providing an early warning based on a device status score according to an embodiment of the present application; Figure 5 is a flow chart of computing device status scoring according to an embodiment of the present application; Figure 6 is a flow chart of measurement report data verification according to an embodiment of the present application; Figure 7 is another flowchart of uploading a metering report according to an embodiment of the present application; Figure 8 is a structural block diagram of a metering equipment management device according to an embodiment of the present application; Figure 9 It is a schematic diagram of the hardware structure of the computer device of an embodiment of the present application. DETAILED DESCRIPTION

[0013] To make the purpose, technical solutions, and advantages of the embodiments of the present application more clear, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of this application.

[0014] Traditional metering equipment management methods have multiple problems, including: the regional management model is too broad, with equipment simply categorized by department or type, lacking a refined management system based on geographical levels. This complicates cross-regional equipment scheduling and status monitoring; metering cycle management relies on manual maintenance of ledgers, which are prone to omissions or misjudgments, making it difficult to achieve dynamic tracking of equipment throughout its lifecycle; equipment information entry relies primarily on manual operations, lacking a standardized verification mechanism for batch imports, making it difficult to ensure data accuracy; report management lacks systematic support, with paper documents easily lost and difficult to archive, and no real-time connection between electronic documents and the actual operating status of equipment, resulting in inefficient historical data tracing and analysis. These problems limit the intelligent and refined development of equipment management, making it difficult to adapt to the requirements of the Industrial Internet of Things era for precise control of equipment throughout its lifecycle.

[0015] Based on the above content, the embodiment of the present application provides a method for managing metering equipment, which isolates geographic information modeling from permissions, supports dynamic regional division and creates a three-level geographic information model, realizes refined management of equipment, implements data isolation in combination with a role-based access control model, and ensures the security of cross-regional data access. Automated task scheduling and intelligent early warning, dynamically generates a task list based on the metering cycle and automatically pushes it to the relevant person in charge, and adopts a multi-dimensional evaluation model to achieve hierarchical early warning. Data standardization and blockchain evidence storage, using Excel spreadsheet components to realize batch import of metering files, while automatically verifying the accuracy of table data; using regular expressions to verify the data format to ensure the standardization of data. Key operations use a decentralized storage method to ensure that the data cannot be tampered with. This method solves the four core problems of extensive regional division, inefficient cycle management, confusing data entry, and difficult operation tracing in traditional metering equipment management by constructing a geographic information model to achieve refined management and control, designing an intelligent task scheduling mechanism, adopting blockchain evidence storage technology, and adopting a multi-dimensional risk assessment model.

[0016] According to an embodiment of the present application, a metering device management embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, for example: a computer, a server, etc., and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0017] In this embodiment, a method for managing metering equipment is provided. Figure 1 is a flow chart of a method for managing a metering device according to an embodiment of the present application, such as Figure 1 As shown, the process includes the following steps: Step S101 : determining target user field information corresponding to user login information in a geographic information model, and obtaining region characters and role characters from the target user field information, wherein the geographic information model is generated based on user field information, role field information, and region field information.

[0018] Specifically, the metering equipment management method is implemented through a regional management and upload system for equipment metering, which includes an intelligent metering management platform. This embodiment divides regions into three levels: district, factory, and workshop. Furthermore, this embodiment employs a role-based access control (RBAC) model for permission management. Regional field information for each region is generated based on the regional hierarchy, such as the region's level, parent region, and region identifier. Multiple roles are generated based on the access control model, along with role field information for each role, such as the permissions specified for each role. User field information for each user is generated, such as the user identifier, the role bound to the user, and the region bound to the user. A geographic information model is generated based on the user field information, role field information, and region field information. If the region is divided into three levels: district, factory, and workshop, the geographic information model is a three-level model. If the region is divided into four levels: primary district, secondary district, factory, and workshop, the geographic information model is a four-level model. The geographic information model enables refined device management, and combined with the role-based access control model, data isolation is implemented to ensure secure cross-region data access. Realize geographic information modeling and permission isolation.

[0019] The regional management and upload system for device metering includes an intelligent metering management platform, which consists of multiple modules, including a regional management module. This module incorporates the aforementioned geographic information model and uses a tree-like structure to flexibly store multiple regional nodes. It also assigns regional permissions to different users in the system. Users can only see the regions and devices within their permissions, thus achieving data isolation.

[0020] Geographic information models such as: Figure 2 As shown, the geographic information model is generated based on user field information, role field information, and region field information. Based on the user login information, the corresponding target user field information is retrieved from all user field information contained in the geographic information model. The region character and role character are obtained from the target user field information. The region character is used to record the region bound to the user, and the role character is used to record the role bound to the user.

[0021] Step S102 : determining target region field information in the geographic information model according to the region character, and determining target role field information in the geographic information model according to the role character.

[0022] Specifically, the region bound to the user is determined based on the region character, and the target region field information corresponding to the region bound to the user is determined in the geographic information model. For example, the region identification character is recorded in the region field information, and the target region field information is determined by matching the region identification. The role bound to the user is determined based on the role character, and the target role field information corresponding to the role bound to the user is determined in the geographic information model. For example, the role identification character is recorded in the role field information, and the target role field information is determined by matching the role identification.

[0023] Step S103 , determining the target area in the preset area hierarchy of the geographic information model according to the node character and the level character in the target area field information, and determining the user area authority according to the authority character in the target role field information.

[0024] Specifically, the node characters in the area field information are used to record the parent node or child node of the corresponding area. The parent node represents the upper-level area of ​​the area, and the child node represents the lower-level area of ​​the area. The hierarchy characters in the area field information are used to record the area hierarchy of the corresponding area, such as: region, factory, workshop. The preset area hierarchy of the geographic information model is, for example, region, factory, workshop, equipment, etc. According to the node characters in the target area field information, the parent node or child node of the target area is determined, and the area hierarchy of the target area is determined according to the hierarchy characters, and the target area is determined. The permission characters in the role field information are used to record the permissions possessed by the corresponding role, and according to the permission characters in the target role field information, the permissions for the bound area, i.e., the user area permissions, are determined.

[0025] This embodiment utilizes a regional role-based access control mechanism, combined with an operation log tracing module, to ensure transparent oversight of the entire operational process. Regarding regional role-based access control, the system precisely assigns access rights based on different business areas and functional roles. Through detailed business scenario segmentation, the system determines the functional boundaries of each area and, based on the user's role attributes, grants operational permissions within that area.

[0026] Step S104: managing the devices to be managed in the target area according to the user's area authority.

[0027] Specifically, users manage the devices to be managed in the target area based on user area permissions. For example: user area permissions include viewing and entry permissions, and users can view the status of the devices to be managed or enter the data of the devices to be managed into the system; user area permissions include data query, review and modification permissions, and users can query the data corresponding to the devices to be managed, review the data, and modify the data according to the review results; user area permissions include permission allocation permissions, and users can allocate permissions corresponding to the devices to be managed to users, etc.

[0028] The metering equipment management method provided in this embodiment determines the target user field information corresponding to the user login information in the geographic information model; determines the target area field information and the target role field information in the geographic information model based on the target user field information; determines the target area based on the target area field information, determines the user area authority based on the target role field information, and manages the equipment to be managed in the target area based on the user area authority. This method manages the area at multiple levels, refines the area management model, and grants the user the corresponding user area authority by binding the user to the role and area, so that users with authority can manage the metering equipment across regions. Accurately authorize users based on roles and regions, effectively prevent unauthorized operations, and fundamentally ensure data security. It solves the problem that the regional management model of metering equipment is too broad, user authority is confusing, and it is difficult to manage metering equipment across regions.

[0029] As an optional embodiment, before determining the target user field information corresponding to the user login information in the geographic information model, the method further includes: Acquire regions under a first preset number of regional levels, and determine regional identifiers and associated regions of the regions according to the regional levels; Generate the corresponding regional field information of the region according to the regional level, regional identifier and associated regions; Generate a second preset number of regional management roles, and obtain management permissions corresponding to the regional management roles; Generate role field information based on regional management roles and management permissions; Obtain user information and determine the regional management role and region corresponding to the user information; Generate user field information based on user information, regional management role, and region; Generate a geographic information model based on user field information, role field information, and region field information.

[0030] Specifically, combined Figure 2 This embodiment is described. The first preset number represents a plurality of, for example, the first preset number of regional levels: regions, factories, workshops, equipment, etc. The specific regional levels can be divided manually according to the actual location of the equipment. Get the regions under the first preset number of regional levels, for example: region 1 and region 2 under the regional level, factory 1 and factory 2 under the factory level, workshop 1 and workshop 2 under the workshop level, etc. According to the regional level, determine the regional identification and associated areas of the region, and the associated areas include upper-level areas or lower-level areas, for example: the regional identification of region 1 is region 1, and the lower-level areas of region 1 include factory 2; the regional identification of factory 1 is factory 1, and the lower-level areas of factory 1 include workshop 1, and the upper-level areas of factory 1 include region 2.

[0031] Generate regional level characters based on the regional level, determine the regional identification characters, and generate node characters based on the associated regions. Integrate the regional identification characters, regional level characters, and node characters to generate regional field information corresponding to the region.

[0032] Generate a second preset number of regional management roles, such as ordinary employees, managers, etc. Obtain the management permissions corresponding to each regional management role. For example, ordinary employees have viewing and input permissions, and ordinary employees can view the status of the devices to be managed or enter the data of the devices to be managed into the system; managers have data query, review, and modification permissions, and managers can query the data corresponding to the devices to be managed, review the data, and modify the data based on the review results.

[0033] Obtain user information and determine the corresponding regional management role and region. Assign different regional management roles and bound regions to different users, determine user permissions, and implement data isolation. For example, if you assign factory permissions, the user can see all equipment in that factory, but not equipment in other factories. If you assign a workshop, the user can only see equipment in that workshop, but not equipment in other regions. Multiple region selection is supported. User information includes: user name, user account ID.

[0034] Generate user identification characters based on user information, such as user1, abcdef, etc. Generate role characters based on regional management roles, such as role1, role2, etc. Generate region characters based on region. Integrate user identification characters, role characters, and region characters to generate user field information.

[0035] Integrate the above user field information, role field information and region field information to generate a geographic information model, such as Figure 2 shown.

[0036] In this embodiment, a geographic information model is generated based on user field information, role field information, and region field information. Geographic information modeling and permission isolation are implemented through the geographic information model, and devices are managed in a refined manner. Data isolation is implemented in combination with a role-based access control model to ensure the security of cross-regional data access.

[0037] As an optional embodiment, managing the devices to be managed in the target area according to the user area authority includes: Obtain the metering report of the device to be managed and the upload time of the metering report; Verify the metering report according to the preset rules. If the metering report passes the verification, obtain the device data of the device to be managed based on the metering report; Determine the task list based on the metering report and upload time, and generate push information based on the task list.

[0038] Specifically, obtain the measurement report uploaded by the user for the device to be managed. The measurement report may include: device details, device BOM (Bill of Materials), device technical documentation, and other information. Determine the upload time when the user uploads the measurement report.

[0039] Preset rules, for example, accurately verify the type, length, and value range of each field in the metering report. For example, for date fields, the system checks whether its format is correct; for numeric fields, it verifies whether it is within a reasonable range. The metering report is verified according to the preset rules. If the metering report passes the verification, the data in the metering report is parsed and read to obtain the device data of the device to be managed.

[0040] A task list is determined based on the metering report and upload time, and push notifications are generated based on the task list. For example, a task list is dynamically generated based on the upload time and metering cycle and automatically pushed to the relevant person in charge. A multi-dimensional assessment model is used to implement graded early warnings. A yellow alert is triggered if the remaining period is less than or equal to 30 days, while a red alert is triggered if the remaining period is zero, triggering the device to be deactivated. This enables automated task scheduling and intelligent early warning. Furthermore, since metering devices have different metering cycles, the current metering time and metering cycle must be entered when initializing and adding new metering devices. The system automatically calculates and stores the next metering deadline based on the metering cycle, and sends an email reminder one month before the next due date. Furthermore, the color of devices in the device list that are about to expire changes to orange, reminding engineers to complete metering tasks promptly. When engineers upload a device's metering report, the system automatically updates the next due date based on the current metering time and the device's metering cycle. The device inventory list in the metering management module clearly displays the metering time and number of metering report uploads for each device, and supports quick filtering of report statistics.

[0041] The aforementioned smart metering management platform also includes a device management module and a metering management module. The device management module utilizes a multi-table relational structure, recording detailed device information such as initial device information, device code, and device location. This information is entered into the system by equipment engineers. If the device has a built-in intelligent module, operating status can be automatically obtained via the network. If it is not, the device status can be updated based on employee reports of abnormalities. The metering management module focuses on metering devices and aggregates information for all metering devices. Some metering devices are independent, while others are associated with production equipment, effectively forming a subset of the data. A separate extraction module is used to independently summarize metering work reminders, facilitating user data query. The data displayed in the table has different focuses, allowing users to customize additional data such as periodic metering reports, calibration dates, and the next calibration deadline. The module also supports batch addition of metering devices via Excel spreadsheets and importing of metering devices into the device management module. Some metering devices support IoT technology and can periodically report device data to the system via TCP (Transmission Control Protocol). The metering management module is equivalent to a subset of the equipment module, except that the targeted content is different. The page list displays content with different focuses, focusing more on recording the historical records of the metering equipment and promptly reminding engineers to complete metering work. The equipment module focuses more on displaying equipment status, summarizing equipment alarm information, maintaining equipment technical documents, and related information such as inspection and maintenance. Batch addition through the table means adding metering equipment in batches, that is, entering metering equipment into the system in batches. The metering report has a separate button for metering equipment. Click it to display a pop-up window, where you can upload the current metering report and remarks. The system automatically calculates the deadline for uploading the report next time based on the metering time and cycle, and will remind you when the deadline is approaching.

[0042] The above process is as follows Figure 3 As shown, a user logs in to the app and sends their login information to the system. The system verifies regional permissions based on the user's login information; the device list is loaded; the user submits a metering report; the report format is verified; the next metering date is updated; and the system sends a confirmation email to the user. Loading the device list and submitting the device report are primarily intended to achieve data isolation, meaning each user only sees and fully accesses content within their authorized area. Because each area has different responsibilities, it is necessary for the person in charge to manage the metering equipment in that area.

[0043] In this embodiment, Excel is used to implement batch import of measurement reports, while automatically verifying the accuracy of table data; regular expressions are used to verify the data format to ensure the standardization of the data.

[0044] As an optional embodiment, obtaining device data of the device to be managed according to the measurement report includes: Obtain device data of the device to be managed in the metering report; Get the operation information corresponding to the measurement report; The device data and operation information are synchronized to a third preset number of storage nodes using a preset synchronization mechanism.

[0045] Specifically, obtain the device data of the device to be managed in the measurement report, such as device details, device material list, device technical documentation, etc. Obtain the operation information corresponding to the measurement report, such as the operation time, operator, imported data content, etc.

[0046] This embodiment uses blockchain evidence storage technology to design a preset synchronization mechanism. Blockchain evidence storage technology provides a solid traceability guarantee for operation records. Each data import operation will be recorded on the blockchain, forming an unalterable record. Whether it is data review, audit, or subsequent problem troubleshooting, accurate information can be obtained by querying the records on the blockchain, ensuring the transparency and traceability of data operations.

[0047] The third preset number represents multiple storage nodes, such as initiators, reviewers, storage providers, and querying parties. The preset synchronization mechanism, for example, follows a "transaction broadcast - consensus verification - block synchronization" process to ensure that all nodes maintain complete ledger consistency. Any modifications require network-wide consensus, ultimately achieving "full traceability and non-repudiation" of data import records. This preset synchronization mechanism synchronizes device data and operational information to each storage node, enabling multi-party oversight and preventing a single node from monopolizing data recording rights.

[0048] In this embodiment, a decentralized storage method is used to store device data and operational information to ensure data immutability. Whether conducting data review, audit, or subsequent troubleshooting, accurate information can be obtained by querying records on the blockchain, ensuring transparency and traceability of data operations.

[0049] As an optional embodiment, synchronizing device data and operation information to a third preset number of storage nodes using a preset synchronization mechanism includes: Store device data and operation information to the target storage node; When the block height of the target storage node is greater than the block height of other storage nodes, a synchronization request containing device data and operation information is generated; Send the synchronization request to other storage nodes, where other storage nodes are used to filter the data in the synchronization request according to the defined storage rules and only store data that meets the storage rules. The storage rules are generated when the storage node is created. Other storage nodes are also used to store the storage rules of this storage node and the storage rules of the target storage node.

[0050] Specifically, a third preset number of storage nodes, such as an initiator, an auditor, a storage party, a query party, etc., selects one storage node from the above storage nodes as a target storage node, such as a storage party, and stores the above device data and operation information in the target storage node.

[0051] The block height is an increasing integer representing the number of "blocks" stored on a node. It's like the page numbers in a book: larger page numbers indicate newer and more complete content. In blockchain, block height equals the total number of blocks on the chain. In distributed storage, it can also refer to a "data version" or "log sequence number."

[0052] When the block height of the target storage node is smaller than that of other storage nodes, it means that the data of the target storage node is outdated and the data version it has is newer than that of other nodes. Therefore, it is necessary to synchronize data with other storage nodes and generate a synchronization request containing device data and operation information.

[0053] The synchronization request is sent to other storage nodes, and the data in the synchronization request is filtered according to the defined storage rules, storing only data that meets the storage rules. Through the human-computer interaction interface, the blockchain administrator can configure the corresponding storage rules for the blockchain node through the storage rule definition module 11. The storage rule can be a piece of code that can express complex meanings. The input is the transaction content of the blockchain, and the output is True or False, indicating whether the storage rule is met.

[0054] Storage rules such as: bool filter(transaction) / / Verify the input data to determine whether it meets the storage rules.

[0055] wrid = transaction.wrid; / / Get the warehouse receipt ID in the synchronization request.

[0056] type = transaction.type; / / Get the warehouse receipt operation in the synchronous request.

[0057] if(type==PLEDGE&&node==ICBC): / / If the warehouse receipt indicates that the most recent operation was a pledge to this storage node.

[0058] return True; / / Output True, indicating that the data complies with the storage rules.

[0059] else: / / Other situations.

[0060] return False; / / Output False, indicating that the data does not comply with the storage rules.

[0061] As an optional embodiment, after obtaining the device data of the device to be managed according to the measurement report, the method further includes: Obtaining a fourth preset number of device status data from the device data; Determine, based on the device status data, a device status score of the metering device, wherein the metering device includes the device to be managed; Determine equipment control strategies based on equipment status scores and equipment status data; A first push message is generated according to the score range corresponding to the device status score and the device control strategy.

[0062] Specifically, a fourth preset number of device status data items are obtained from the device data. The fourth preset number represents a plurality of items. Examples of the fourth preset number of device status data items include: cumulative device operation time, mode operation time, device fault type, fault frequency, and the temperature, humidity, pressure, and vibration of the metering device. Furthermore, this embodiment deploys various environmental sensors around the metering device, including temperature, humidity, pressure, and vibration sensors, to monitor the temperature, humidity, pressure, and vibration of the device's environment in real time. This device status data is crucial for assessing the device's operating status and potential risks, as adverse environmental conditions can accelerate device aging and damage.

[0063] The aforementioned device status data is input into a multidimensional assessment model, which outputs a device status score for the metering equipment. This model breaks down device data into three core dimensions: usage intensity, failure risk, and environmental adaptability. Each dimension includes specific, quantifiable indicators and is weighted (W1 / W2 / W3 can be dynamically configured based on device characteristics). A weighted summation is used to determine the overall score. The warning level is determined based on the score range, ultimately outputting warning information and recommendations. The device status score calculation converts device data into a quantified risk value, essentially a multi-dimensional data weighting / rule mapping.

[0064] The equipment control strategy is determined based on the equipment status score and equipment status data. For example, if the equipment status score is 59 and the metering equipment is in a high-risk state, the equipment control strategy is to replace the metering equipment with a device with the same equipment status data. In addition, the system will measure the time of occurrence of the fault, the type of fault, the location of the fault, the environmental parameters when the fault occurred, the fault handling process and results, and the equipment status before the fault occurred. The failure mode refers to the regular failure characteristics exhibited by the equipment during long-term operation, and is a summary of "how and why the failure occurred." Historical failure data is a "case library," and comparative analysis is a process of "inductive reasoning." By finding patterns through a large number of cases, we can eventually upgrade from "passive response to failures" to "active prediction and control of failures."

[0065] The first push notification is generated based on the score range corresponding to the device status score and the device control strategy. For example, if the device status score is 81, which is in the 80-100 range, the metering device is in a low-risk state, triggering a yellow alert and generating the first push notification. Furthermore, the device status score can be compared with the corresponding threshold to determine the risk of metering device failure. The threshold is inferred through statistical methods, using the risk-failure correlation of historical failure data to find the critical value at which an increase in the risk score causes a failure.

[0066] The regional equipment metering and upload system also includes an intelligent early warning subsystem. By integrating an assessment model based on equipment usage time, failure frequency, and environmental parameters, this system provides risk-based early warning and precise management of equipment status. This system is integrated with the equipment's control system to track equipment start-up and stop times, as well as cumulative operating time, in real time. For equipment with complex operating modes, the system also records the operating time in each mode in detail, providing accurate data support for subsequent evaluation. Leveraging the equipment's built-in fault diagnosis module and sensors installed in key locations, the system monitors equipment failures in real time. Upon detection of a fault, the system automatically records the time, type, and location of the fault and performs statistical analysis of the fault frequency. Using a multi-dimensional assessment model, the system automatically determines the early warning level based on weighting of parameters such as equipment startup time. Furthermore, the system compares fault information with the equipment's historical failure data to provide a more comprehensive understanding of the equipment's failure patterns.

[0067] The above process is as follows Figure 4 As shown, device data is collected; risk score is calculated; and it is determined whether the risk score exceeds the threshold. If so, a red warning is issued; if not, a yellow warning is issued.

[0068] In this embodiment, a device status score for the metering device is determined based on the device status data. When the metering device is determined to be abnormal based on the device status score, a first push message is promptly generated based on the score range corresponding to the device status score and the device control strategy. This ensures the normal operation of the metering device and prevents business operations from being affected by metering device failures.

[0069] As an optional embodiment, determining the device status score of the metering device according to the device status data includes: Obtain equipment operation data, fault information data, and environmental parameter data from equipment status data; Preprocessing the equipment operation data, the fault information data, and the environmental parameter data to obtain a fifth preset number of initial indicator data and indicator types of the initial indicator data; If the indicator type is the first type, the initial indicator data is used as the indicator data; if the indicator type is the second type, the difference between the preset parameter and the initial indicator data is used as the indicator data; Generating a sixth preset number of indicator scores based on the preset indicator weights and indicator data; The device status score is obtained based on the indicator score and score weight.

[0070] Specifically, this embodiment is mainly aimed at smart devices. The system will store relevant data of the device, such as usage time, number of failures, etc., and then the engineer will configure the corresponding weight and other parameters for the device. The system will perform a calculation based on this parameter and historical data to obtain the final result.

[0071] Combine Figure 5 This embodiment is described. Device operation data, fault information data, and environmental parameter data are obtained from the device status data. Device operation data includes, for example, accumulated duration and mode operation duration; fault information data includes, for example, fault type and fault frequency; and environmental parameter data includes, for example, temperature, humidity, pressure, and vibration.

[0072] Preprocessing is to perform preliminary processing on the collected data and filter the data for standards and abnormal values. Preprocess the equipment operation data, fault information data and environmental parameter data to obtain the fifth preset number of initial indicator data and the indicator type of the initial indicator data, such as positive indicators and reverse indicators. The initial indicator data is shown in Table 1. Figure 5 As shown in the figure, the equipment operation data, fault information data and environmental parameter data are cleaned and standardized to obtain 6 indicators, namely: indicator 1 cumulative operation time exceedance rate, indicator 2 high load mode operation ratio, indicator 3 number of failures per unit time, indicator 4 recurrence probability of similar failures, indicator 5 key environmental parameter deviation, indicator 6 abnormal environment duration.

[0073] Table 1 Indicator data, preset indicator weights and scoring weights

[0074] The first type is a positive indicator, and the second type is a negative indicator. If the indicator type is the first type, the initial indicator data is used as the indicator data. For example, if the initial indicator data of the first type includes the cumulative run time percentage and the high-load mode operation percentage, the initial indicator data is directly used as the indicator data. For example, if the cumulative run time percentage and the high-load mode operation percentage are of the first type, and the cumulative run time percentage is 0.85, the corresponding indicator data is 0.85; if the high-load mode operation percentage is 0.3, the corresponding indicator data is 0.3. If the indicator type is the second type, the difference between the preset parameter and the initial indicator data is used as the indicator data. For example, the preset parameter is 1, and the initial indicator data of the second type include the number of failures per unit time, the probability of recurrence of similar failures, the deviation of key environmental parameters, and the duration of the abnormal environment. The indicator data is 1 minus the above initial indicator data. For example, the probability of recurrence of similar failures, the number of failures per unit time, the deviation of key environmental parameters, and the duration of the abnormal environment are of the second type. The probability of recurrence of similar failures is 0.15, and the corresponding indicator data is 1-0.15=0.85; the number of failures per unit time is 0.2, and the corresponding indicator data is 1-0.2=0.8; the deviation of key environmental parameters is 0.25, and the corresponding indicator data is 0.75; the duration of the abnormal environment is 0.1, and the corresponding indicator data is 0.9.

[0075] According to the preset indicator weights and indicator data, a sixth preset number of indicator scores are generated. For example, the indicator score obtained by the device usage intensity assessment is equal to (0.85×W 11 )+(0.3×W 12 ) = 0.52, the index score obtained by fault risk assessment is equal to (0.8×W 21 )+(0.85×W 22 ) = 0.825, the index score obtained by environmental adaptability assessment is equal to (0.75×W 31 )+(0.9×W 32 ) = 0.855. The above process is as follows Figure 5 As shown in the figure, the indicator score of dimension 1 equipment usage intensity assessment is calculated using indicator 1, the cumulative operating time exceeding the standard rate, and indicator 2, the proportion of high-load mode operation; the indicator score of dimension 2 fault risk assessment is calculated using indicator 3, the number of failures per unit time, and indicator 4, the probability of recurrence of similar failures; the indicator score of dimension 3 environmental adaptability assessment is calculated using indicator 5, the deviation of key environmental parameters, and indicator 6, the duration of abnormal environment.

[0076] According to the indicator score and score weight, the device status score is obtained. For example, the device status score is equal to ∑ (indicator score × score weight) = (0.52 × W1) + (0.825 × W2) + (0.855 × W3) = 0.712. Figure 5 As shown in Figure 2, the weighted sum of all indicator scores is calculated as the device status score.

[0077] In addition, if Figure 5 As shown, the method further includes: determining the warning level according to the device status score and outputting the result.

[0078] As an optional embodiment, determining the area corresponding to the user information includes: Obtaining a region map containing the area to be managed, and identifying the area to be managed in the region map; Generate a feature vector of the area to be managed based on the number of metering devices and the amount of metering device data in the area to be managed; Determine the distance between the areas to be managed based on the feature vector; Determine whether the distance between two to-be-managed areas is greater than or equal to a distance threshold; If the distance between two areas to be managed is greater than or equal to the distance threshold, the two areas to be managed are merged into a new area to be managed; If the distance between the two to-be-managed areas is not greater than or equal to the distance threshold, an area corresponding to the user information is determined in the to-be-managed area, wherein the area corresponding to the user information is included in the to-be-managed area.

[0079] Specifically, a region map including all the regions to be managed is obtained, boundary lines of the regions to be managed are identified in the region map, and the regions to be managed are determined according to the boundary lines.

[0080] According to the number of metering devices and the amount of metering device data in the area to be managed, a feature vector of the area to be managed is generated, and the feature vector is composed of the number of metering devices and the amount of metering device data.

[0081] The feature vector is regarded as an independent cluster. The distance between the areas to be managed is determined by calculating the distance between each cluster. For example, the centroid distance or Euclidean distance between the clusters corresponding to adjacent areas to be managed is calculated, and the calculation result is used as the distance between the areas to be managed.

[0082] The maximum service radius of the monitoring area, i.e. the distance threshold, is set. The maximum service radius is set by the expert group based on the management capabilities of the management personnel.

[0083] If the distance between two areas to be managed is greater than or equal to the distance threshold, the two areas to be managed are merged into a new area to be managed.

[0084] If the distance between the two to-be-managed areas is not greater than or equal to the distance threshold, the area corresponding to the user information is determined in the to-be-managed area, and the area field information of the to-be-managed area is bound to the user field information of the user.

[0085] In this embodiment, dynamic optimization and automatic merging of the areas to be managed are achieved, the adaptability and scalability of the system are enhanced, and a basis for precise service is provided. The area corresponding to the user information is determined in the area to be managed, and the user's area management authority is clarified.

[0086] As an optional embodiment, the measurement report is verified according to a preset rule, including: Get the document template of the measurement report; Compare the file template with the preset template, and generate a prompt message if the file template is inconsistent with the preset template; If the file template is consistent with the preset template, obtain the field information in the measurement report; Verify field information according to the preset field format.

[0087] Specifically, the above system includes a data standardization module, which integrates template recognition, field verification and blockchain evidence storage technology to ensure the standardization of batch data import and the traceability of operation records.

[0088] The data standardization module can accurately identify data templates of various formats. For example, the data standardization module determines whether the content of the template complies with the standard template content. If it does not comply, a corresponding error prompt will be given. The preset template uses the Excel parsing module to convert the corresponding field data and store the corresponding data in the database through dictionaries and other methods.

[0089] Use the data standardization module to compare the file template with the preset template. If the file template is inconsistent with the preset template, there may be some abnormal data. The system cannot automatically correct these abnormal data and needs to withdraw the operation. A prompt message is generated to guide the user to modify the content and re-import it. For example, there are system abnormal data, incorrect date data, and numerical data in the imported content.

[0090] The Data Standardization module's field validation function performs rigorous checks on every field in the imported data. If the file template matches the preset template, the module retrieves the field information from the metering report and verifies it against the preset field format. For example, for date fields, the module checks whether the format is correct; for numeric fields, the module verifies whether they fall within a reasonable range. If any data violates the rules, the module clearly identifies the problem, allowing users to make timely corrections.

[0091] In this embodiment, the file template of the metering report is first verified, and then the field information in the metering report is verified. If the verification fails, the problem is clearly pointed out, so that the user can make corrections in time to ensure that the metering report format is correct.

[0092] As an optional embodiment, verifying the field information according to a preset field format includes: Get the regular expression corresponding to the preset field format; Verify the data type and data length of the field information according to the regular expression to obtain a first verification result; According to the regular expression, determine whether the value of the field information is within a preset range, and obtain a second verification result; If an abnormal field is determined according to the first verification result, or if an abnormal field is determined according to the second verification result, a prompt message is generated according to the abnormal field; If no abnormal field is determined according to the first verification result, and no abnormal field is determined according to the second verification result, it is determined that the measurement report verification has passed.

[0093] Specifically, accurate verification of the field type, length, value range, encoding format, etc. is achieved through regular expressions. Preset field formats include: field type, length, value range, encoding format, etc. The corresponding regular expressions are generated based on the requirements for type, length, value range, encoding format, etc.

[0094] The data type and data length of the field information are verified according to the regular expression to obtain a first verification result. For example, the date field is checked according to the regular expression to see whether its format is correct and whether the data length meets the length requirement.

[0095] According to the regular expression, it is determined whether the value of the field information is within a preset range to obtain a second verification result, for example: according to the regular expression, it is verified whether the value field is within a reasonable range.

[0096] If an abnormal field is determined based on the first check result or the second check result, the abnormal field is a field whose data does not conform to the rules. Once an abnormal field is found, a prompt message is generated based on the abnormal field, clearly indicating the problem through the prompt message, so that the user can correct it in a timely manner.

[0097] If no abnormal field is determined according to the first verification result, and no abnormal field is determined according to the second verification result, it is determined that the measurement report verification has passed.

[0098] The above process is as follows Figure 6As shown, data is imported; template matching, if the matching fails, a template prompt is given; if the matching is successful, field verification is performed, and if the field verification fails, an error feedback is given; if the field verification passes, blockchain evidence is stored.

[0099] As an optional embodiment, determining a task list based on the metering report and the upload time, and generating push information based on the task list include: Generate pending measurement tasks based on measurement reports; Get the metering period of the pending metering task; Determine the deadline for pending metering tasks based on the upload time and metering cycle; Generate a task list based on pending measurement tasks and task deadlines; A second push message including a task list is generated according to the difference between the current system time and the task deadline.

[0100] Specifically, since metering devices have different metering cycles, the metering time and metering cycle of the current metering device must be filled in when initializing or adding a new metering device. Based on the metering report, pending metering tasks are generated. Pending metering tasks include: re-uploading metering reports, repairing metering devices, and testing metering devices.

[0101] Get the metering period of pending metering tasks, for example, uploading a metering report every 30 days, testing metering equipment every 3 months, etc.

[0102] Determine the deadline for pending metering tasks based on the upload time and metering cycle. For example, if the upload time is X month Y day and the metering cycle is 1 month, the deadline for the task is X+1 month Y day.

[0103] Generate a task list based on pending metering tasks and task deadlines. Based on the difference between the current system time and the task deadline, generate a second push message containing the task list. For example, the second push message is an email that automatically calculates and stores the next metering deadline based on the metering cycle. An email reminder is sent one month before the next due date. The system also supports changing the color of devices in the device list that are about to expire to orange, reminding engineers to complete metering work in a timely manner. When engineers upload metering reports for devices, the system automatically updates the next due date based on the current metering time and the device's metering cycle.

[0104] The system also includes an automated task scheduling module. A scheduled task engine triggers a metering reminder task at 9:00 AM daily (configurable), integrating with an email notification system to automate task assignment. This module utilizes the Spring Framework's TaskScheduler to periodically trigger metering reminders. Through a correlation query, the module retrieves a list of all metering devices with a due date within a month. It then groups these devices by their responsible individuals and aggregates the list of devices by their responsible individuals. It then iterates through the device metering deadlines in the list, checking for any devices with a due date exactly one month from the current date, 15 days from the current date, or on the current date, or with a metering deadline that has expired. If so, the module aggregates the device list into emails with expired, due today, within 15 days, or within a month, based on the metering deadline. The module then invokes the email module to send an email reminder to the responsible individuals. Devices with different metering deadlines are marked with different colors, prompting engineers to complete metering work and upload metering reports to the system.

[0105] In the device inventory list in the metering management module, you can clearly see the metering time and number of metering report uploads for different devices, and support quick filtering of report statistics. The inventory list is a list of information in the metering management module, mainly displaying: device ID, device name, device model, manufacturer, serial number, metering cycle, calibration date, next calibration deadline, responsible person, number of reports, using unit, associated devices, associated regions, and other list data.

[0106] The above process is as follows Figure 7 As shown, the metering equipment is archived; the current metering time and cycle are entered; the system automatically calculates the next deadline; the equipment transmits data through the IoT terminal, and the "equipment transmits data through the IoT terminal" is run periodically; it is determined whether the deadline is approaching. If so, an email reminder is sent and the ledger is marked orange; the engineer uploads the metering report; the system automatically updates the next deadline; if the deadline is not approaching, the "equipment transmits data through the IoT terminal" is re-executed.

[0107] In this embodiment, by automatically generating tasks, intelligently calculating deadlines, and dynamically pushing reminders, the automation level, execution efficiency, and time controllability of metering management are significantly improved, effectively preventing tasks from being missed or overdue, and ensuring system compliance and stable operation.

[0108] As an optional embodiment, after obtaining the device data of the device to be managed according to the measurement report, the method further includes: Obtain the upload process data of the measurement report and generate an operation log based on the upload process data, measurement report, user login information and upload time; In the event of an abnormality in the device to be managed, determine whether the user area permissions include permissions corresponding to the operation log; In the case where the user area authority includes the authority corresponding to the operation log, the abnormal information and the responsible person information of the device to be managed are determined according to the operation log.

[0109] Specifically, an operation log is generated based on uploaded process data, metering reports, user login information, and upload time. This log records every operation within the system in detail, including data queries, modifications, and system configuration changes. It also records key information such as the time, operator, content, and results of the operation. These operation logs are securely stored for easy subsequent query and audit. Operation logs are also managed based on role and region permissions.

[0110] In the event of an abnormality in the device to be managed, first determine whether the user has the corresponding permissions for the operation log, such as the permission to read the operation log, the permission to download the operation log, the permission to modify the operation log, etc. The abnormality of the device to be managed may be: abnormal operation or data security incident.

[0111] When the user area permissions include permissions corresponding to the operation log, for example: the user is a manager, the manager can use the operation log to quickly locate the time, location and responsible person of the problem, determine the abnormal information and responsible person information of the managed equipment, and achieve transparent supervision of the entire process.

[0112] In this embodiment, when abnormal operations or data security incidents occur, managers can use operation logs to quickly locate the time, location, and responsible person of the problem, thereby achieving transparent supervision of the entire process.

[0113] As an optional embodiment, the above step of "managing the devices to be managed in the target area according to the user's area authority" may further include steps A1 to A3.

[0114] Step A1: Check the total device reading error of the devices to be managed in the target area, and mark the target area with measurement error as an abnormal area.

[0115] Specifically, a regional input metering unit is set in each target area, and the regional input metering unit is used to calculate the input device reading in the corresponding target area, obtain the metering data of the equipment to be managed in each target area, calculate the total metering data of the equipment to be managed in the target area based on the obtained metering data of the equipment to be managed in the target area, and mark it as the regional equipment to be managed data, set the allowable metering error of the equipment to be managed in the corresponding target area, and the allowable metering error of the equipment to be managed is set according to the characteristics of the equipment to be managed and the number of equipment to be managed, calculate the difference between the reading of the equipment to be managed of the regional input metering unit and the regional equipment to be managed data, and mark it as the regional difference, and obtain the target area whose absolute value of the regional difference is greater than the allowable metering error of the equipment to be managed, because the regional difference may be a negative value.

[0116] Step A2: Obtain the analysis model corresponding to the abnormal area, collect the metering data of each device to be managed in the abnormal area in the current time period, analyze the collected metering data of the device to be managed through the analysis model, obtain the metering device corresponding to the metering data of the abnormal device, and mark it as an abnormal device; the time span of the current time period is set by the expert group according to the metering equipment usage specifications.

[0117] Specifically, obtain the historical metering data of the devices to be managed corresponding to the users in each target area, screen out the metering data of the devices to be managed with accurate metering from the historical metering data, mark it as regional training data, obtain the metering equipment analysis model, the metering equipment analysis model is the currently existing neural network model for analyzing metering anomalies of metering equipment, train and verify the metering equipment analysis model through the regional training data, mark the successfully verified metering equipment analysis model as the analysis model, and label the analysis model with the corresponding target area label; match according to the abnormal area to obtain the analysis model with the corresponding target area label.

[0118] Step A3: Establish a metering equipment analysis library, obtain metering data of the abnormal equipment N days before, where N is a positive integer, input the obtained metering data into the metering equipment analysis library for analysis, and obtain the inaccuracy judgment result of the abnormal equipment.

[0119] Specifically, a large amount of historical measurement data of metering equipment is obtained, and the measurement data of inaccurate metering equipment in the historical measurement data of metering equipment is screened out and marked as inaccurate data. The inaccurate data includes the measurement date and the measurement data of the corresponding date. The fault cause corresponding to the inaccurate data is obtained, and a data strip is set. The data strip has N data filling bits, and one data filling bit corresponds to the measurement data of one measurement date. A group of inaccurate data is integrated into one data strip, and the data strips are numbered. A fault cause matching table is set according to the data strip number and the corresponding fault cause; a database is established, and the data strips are input into the database for storage. A clustering unit is set in the database, and the data strips are clustered by the clustering unit to obtain k inaccurate clusters; a matching unit is set in the database; the matching unit is used to match according to the input data strip vector, and the database is marked as a metering equipment analysis library.

[0120] The metering equipment analysis library obtains the input metering data, inputs the obtained metering data into the data strip, marks it as an analysis data strip, vectorizes the analysis data strip, marks it as an analysis data strip vector, maps the analysis data strip vector into the vector space, clusters the analysis data strip vector through the clustering unit, obtains the cluster to which the analysis data strip vector belongs, and marks it as an analysis cluster, matches the analysis data strip vector with the data strip vector in the analysis cluster one by one through the matching unit, and obtains the matching degree between the analysis data strip vector and the data strip vector, which refers to the proportion of the corresponding position data of the two vectors that are the same; marks the data strip vector with a matching degree greater than the first threshold as matching data, calculates the proportion of the number of matching data in the analysis cluster, and marks it as the inaccuracy probability. When the inaccuracy probability is greater than the second threshold, the corresponding input metering data is marked as inaccurate data, and the fault cause corresponding to the matching data is obtained, and the obtained fault cause is sorted and sent to the corresponding management personnel.

[0121] In this embodiment, by setting up a regional input metering unit, the problem investigation area can be further narrowed down. Combined with the target area, when a metering difference occurs, the investigation area can be quickly narrowed down, the investigation workload can be reduced, and the investigation efficiency can be improved.

[0122] This embodiment also provides a metering equipment management device for implementing the above-described embodiments and preferred implementations. Details already described will not be repeated. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0123] This embodiment provides a metering equipment management device, such as Figure 8 Shown, including: The character acquisition module 801 is used to determine the target user field information corresponding to the user login information in the geographic information model, and obtain the region character and role character from the target user field information, wherein the geographic information model is generated based on the user field information, role field information, and region field information; An information determination module 802 is configured to determine target region field information in the geographic information model based on the region character, and to determine target role field information in the geographic information model based on the role character; The authority determination module 803 is used to determine the target area in the preset area hierarchy of the geographic information model according to the node character and the level character in the target area field information, and determine the user area authority according to the authority character in the target role field information; The device management module 804 is used to manage the devices to be managed in the target area according to the user's area authority.

[0124] The further functional description of each of the above modules is the same as that of the above corresponding embodiments and will not be repeated here.

[0125] The metering equipment management device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0126] The present application also provides a computer device having the above Figure 8 The metering equipment management device shown.

[0127] See also Figure 9 , Figure 9 This is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present application. Figure 9 As shown, the computer device includes: one or more processors 10, memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components utilize different buses to communicate with each other and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in the memory or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Equally, multiple computer devices can be connected, and each device provides part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 9 A processor 10 is taken as an example.

[0128] The processor 10 may be a central processing unit, a network processor, or a combination thereof. The processor 10 may further include an integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic, or any combination thereof.

[0129] The memory 20 stores instructions that can be executed by at least one processor 10, so as to enable at least one processor 10 to execute the method shown in the above embodiment.

[0130] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store data created based on the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0131] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0132] The computer device further includes a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0133] The embodiments of the present application also provide a computer-readable storage medium. The above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as a computer code that can be recorded in a storage medium, or implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and downloaded through a network and will be stored in a local storage medium, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor or hardware, the method shown in the above embodiment is implemented.

[0134] Part of the present application may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present application through the operation of the computer. Those skilled in the art should understand that the form in which the computer program instruction exists in a computer-readable medium includes but is not limited to a source file, an executable file, an installation package file, etc. Accordingly, the way in which the computer program instruction is executed by the computer includes but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium that can be accessed by the computer.

[0135] Although the embodiments of the present application are described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present application, and such modifications and variations shall fall within the scope defined by the present application.

Claims

1. A method for managing measuring equipment, characterized in that: The method comprises: Determining target user field information corresponding to user login information in a geographic information model, and obtaining a region character and a role character from the target user field information, wherein the geographic information model is generated based on the user field information, the role field information, and the region field information; Determining target region field information in the geographic information model according to the region character, and determining target role field information in the geographic information model according to the role character; Determine the target area in the preset area hierarchy of the geographic information model according to the node character and the level character in the target area field information, and determine the user area authority according to the authority character in the target role field information; The devices to be managed in the target area are managed according to the user area authority.

2. The method according to claim 1, characterized in that Before determining the target user field information corresponding to the user login information in the geographic information model, the method further includes: Acquire regions under a first preset number of regional levels, and determine regional identifiers and associated regions of the regions according to the regional levels; Generate region field information corresponding to the region according to the region level, the region identifier, and the associated region; Generate a second preset number of regional management roles, and obtain management permissions corresponding to the regional management roles; Generate the role field information according to the regional management role and the management authority; Obtain user information and determine the regional management role and region corresponding to the user information; generating the user field information according to the user information, the regional management role, and the region; The geographic information model is generated according to the user field information, the role field information, and the region field information.

3. The method according to claim 1, characterized in that Managing the to-be-managed devices in the target area according to the user area authority includes: Obtaining a measurement report of the device to be managed and the upload time of the measurement report; Verifying the measurement report according to a preset rule, and if the measurement report passes the verification, obtaining device data of the device to be managed according to the measurement report; A task list is determined according to the measurement report and the upload time, and push information is generated according to the task list.

4. The method according to claim 3, characterized in that The obtaining the device data of the device to be managed according to the measurement report includes: Obtaining device data of the device to be managed in the measurement report; Obtaining operation information corresponding to the measurement report; The device data and the operation information are synchronized to a third preset number of storage nodes using a preset synchronization mechanism.

5. The method according to claim 4, characterized in that The step of synchronizing the device data and the operation information to a third preset number of storage nodes by using a preset synchronization mechanism includes: Storing the device data and the operation information in a target storage node; In a case where the block height of the target storage node is greater than the block heights of other storage nodes, generating a synchronization request including the device data and the operation information; The synchronization request is sent to the other storage node, wherein the other storage node is used to filter the data in the synchronization request according to the defined storage rules and only stores the data that complies with the storage rules. The storage rules are generated when the storage node is created. The other storage node is also used to store the storage rules of this storage node and the storage rules of the target storage node.

6. The method according to claim 3, characterized in that After obtaining the device data of the device to be managed according to the measurement report, the method further includes: Acquire a fourth preset number of device status data from the device data; Determining a device status score of a metering device according to the device status data, wherein the metering device includes the device to be managed; Determining a device control strategy based on the device status score and the device status data; Generate first push information according to the score range corresponding to the device status score and the device control strategy.

7. The method according to claim 6, characterized in that Determining the device status score of the measuring device according to the device status data includes: Obtaining equipment operation data, fault information data, and environmental parameter data from the equipment status data; Preprocessing the equipment operation data, the fault information data, and the environmental parameter data to obtain a fifth preset number of initial indicator data and indicator types of the initial indicator data; If the indicator type is the first type, the initial indicator data is used as the indicator data; if the indicator type is the second type, the difference between the preset parameter and the initial indicator data is used as the indicator data; Generating a sixth preset number of indicator scores based on the preset indicator weights and the indicator data; The device status score is obtained according to the indicator score and the score weight.

8. The method according to claim 2, characterized in that Determining the region corresponding to the user information includes: Acquire a region map containing an area to be managed, and identify the area to be managed in the region map; generating a feature vector of the area to be managed according to the number of metering devices and the amount of metering device data in the area to be managed; determining the distance between the areas to be managed according to the feature vector; Determine whether the distance between two to-be-managed areas is greater than or equal to a distance threshold; If the distance between two areas to be managed is greater than or equal to the distance threshold, the two areas to be managed are merged into a new area to be managed; If the distance between two to-be-managed areas is not greater than or equal to the distance threshold, an area corresponding to the user information is determined in the to-be-managed area, wherein the area corresponding to the user information is included in the to-be-managed area.

9. The method according to claim 3, characterized in that The verifying the measurement report according to a preset rule includes: Obtaining a document template for the measurement report; Comparing the file template with a preset template, and generating a prompt message if the file template is inconsistent with the preset template; If the file template is consistent with the preset template, obtaining field information in the measurement report; The field information is verified according to a preset field format.

10. The method according to claim 9, characterized in that The verifying the field information according to the preset field format includes: Obtaining a regular expression corresponding to the preset field format; Verify the data type and data length of the field information according to the regular expression to obtain a first verification result; Determine, based on the regular expression, whether the value of the field information is within a preset range, and obtain a second verification result; If an abnormal field is determined according to the first verification result, or if the abnormal field is determined according to the second verification result, generating prompt information according to the abnormal field; If no abnormal field is determined according to the first verification result, and if no abnormal field is determined according to the second verification result, it is determined that the measurement report verification has passed.

11. The method according to claim 3, characterized in that Determining a task list according to the measurement report and the upload time, and generating push information according to the task list, includes: Generate a pending measurement task based on the measurement report; Obtaining the metering period of the metering task to be processed; Determine a task deadline for the pending metering task based on the upload time and the metering period; Generating the task list according to the pending measurement tasks and the task deadlines; A second push message including the task list is generated according to the difference between the current system time and the task deadline.

12. The method according to claim 3, characterized in that After obtaining the device data of the device to be managed according to the measurement report, the method further includes: Obtaining upload process data of the metering report, and generating an operation log according to the upload process data, the metering report, the user login information, and the upload time; In the case that an abnormality occurs in the device to be managed, determining whether the user area authority includes the authority corresponding to the operation log; In a case where the user area authority includes the authority corresponding to the operation log, the abnormal information and the responsible person information of the device to be managed are determined according to the operation log.

13. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the metering equipment management method according to any one of claims 1 to 12 by executing the computer instructions.

14. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the metering equipment management method according to any one of claims 1 to 12.

15. A computer program product, characterized in that The method comprises computer instructions for causing a computer to execute the measuring equipment management method according to any one of claims 1 to 12.

Images