Network resource operation and maintenance method, equipment, medium and product

Abstract

The embodiment of the invention provides a network resource operation and maintenance method and device, a medium and a product. The method comprises the steps of obtaining equipment identification information corresponding to equipment to be operated and maintained based on a target data acquisition strategy, and performing standardization processing on the equipment identification information to obtain terminal connection information corresponding to the equipment to be operated and maintained; obtaining service information corresponding to the to-be-operated and to-be-maintained equipment, and fusing the service information and the terminal connection information to obtain fused resource data; if the fused resource data passes the data consistency detection, acquiring position information corresponding to the to-be-operated and to-be-maintained equipment; and constructing a network topological graph corresponding to the equipment to be operated and maintained based on the position information and the fused resource data, wherein nodes of the network topological graph comprise the position information, the equipment state and the service priority of the equipment to be operated and maintained. According to the method, accurate mapping of the network entity and the service function is realized, and the operation and maintenance efficiency, the reliability and the intelligent level of the data network are comprehensively improved.

Description

Technical Field

[0001] This application relates to the field of equipment operation and maintenance technology, and in particular to network resource operation and maintenance methods, equipment, media and products. Background Technology

[0002] In modern power grid data networks, with the deepening of smart grid construction, the network scale is expanding at an unprecedented rate, and the number of access terminals is surging, covering all aspects of power generation, transmission, substation, distribution, and consumption. Simultaneously, the business systems supporting stable power grid operation and intelligent services are becoming increasingly complex and sophisticated. Key services such as precise load control, distributed energy monitoring, and intelligent inspection place extremely high demands on the network's real-time performance, reliability, and security. Against this backdrop, IP addresses, as a core foundational resource for network connectivity and service delivery, are experiencing exponential growth in management requirements.

[0003] In related technologies, the manual static management method using spreadsheets involves recording IP address pools, subnetting, device port configurations, and service-related information in a scattered manner using tools such as Excel. Maintenance personnel need to manually update the spreadsheet content regularly, and network analysis requires cross-spreadsheet retrieval and logging into devices to query ARP entries for verification. This method has drawbacks such as poor data consistency, low timeliness, low operational efficiency, high error rate, and difficulty in auditing, and it cannot clearly define the relationship between IP address ranges and service information. Summary of the Invention

[0004] This application provides network resource operation and maintenance methods, devices, media, and products to achieve accurate mapping between network entities and business functions, and comprehensively improve the operation and maintenance efficiency, reliability, and intelligence level of data networks.

[0005] In a first aspect, embodiments of this application provide a network resource operation and maintenance method, comprising: acquiring device identification information corresponding to a device to be maintained based on a target data collection strategy, and standardizing the device identification information to obtain terminal connection information corresponding to the device to be maintained; acquiring service information corresponding to the device to be maintained, and fusing the service information with the terminal connection information to obtain fused resource data; if the fused resource data passes a data consistency detection, acquiring location information corresponding to the device to be maintained; constructing a network topology map corresponding to the device to be maintained based on the location information and the fused resource data, wherein the nodes of the network topology map include the location information, device status, and service priority of the device to be maintained.

[0006] In one possible implementation, before obtaining the device identification information corresponding to the device to be maintained based on the target data acquisition strategy, the method further includes: if the acquisition item corresponding to the device to be maintained can be acquired through a preset application layer protocol, then the first data acquisition strategy is used as the target data acquisition strategy; if the acquisition item corresponding to the device to be maintained cannot be acquired through the preset application layer protocol, then the second data acquisition strategy is used as the target data acquisition strategy.

[0007] In one possible implementation, obtaining the device identification information corresponding to the device to be maintained based on the target data acquisition strategy includes: determining the data to be maintained corresponding to the device to be maintained based on the preset application layer protocol; establishing a communication channel with the device to be maintained based on the first data acquisition strategy, and determining the access permissions corresponding to the data to be maintained; obtaining the identification information corresponding to the data to be maintained based on the access permissions, and using the identification information to determine the device identification information corresponding to the device to be maintained.

[0008] In one possible implementation, obtaining the device identification information corresponding to the device to be maintained based on the target data acquisition strategy includes: determining the acquisition item corresponding to the device to be maintained and the data acquisition instruction corresponding to the acquisition item; establishing a connection with a target switch based on the second data acquisition strategy, the target switch including a switch corresponding to the device to be maintained; and executing the data acquisition instruction on the target switch to obtain the device identification information corresponding to the device to be maintained.

[0009] In one possible implementation, the terminal connection information includes an IP address, and the process of fusing the service information with the terminal connection information includes: standardizing the service information to obtain a baseline service information table with IP addresses as keys; determining the data association between the baseline service information table and the terminal connection information based on the IP addresses; and fusing the service information with the terminal connection information based on the data association.

[0010] In one possible implementation, the method further includes: determining whether the MAC address in the terminal connection information is consistent with the MAC address in the service information based on the IP address; if they are consistent, determining that the merged resource data has passed the data consistency detection; if they are inconsistent, generating a prompt message corresponding to the data conflict, and generating an anomaly report based on the prompt message for push.

[0011] In one possible implementation, the method further includes: constructing a logical model of the IP address corresponding to the device to be maintained based on the fused resource data; determining the graphical elements corresponding to the logical model of the IP address, and constructing a network topology map corresponding to the device to be maintained based on the graphical elements; obtaining real-time device identification information of the device to be maintained, and updating the network topology map based on the real-time device identification information.

[0012] Secondly, embodiments of this application provide a network resource operation and maintenance device, the device comprising: an acquisition module, configured to acquire device identification information corresponding to a device to be maintained based on a target data acquisition strategy, and to standardize the device identification information to obtain terminal connection information corresponding to the device to be maintained; a fusion module, configured to acquire service information corresponding to the device to be maintained, and to fuse the service information with the terminal connection information to obtain fused resource data; a judgment module, configured to acquire location information corresponding to the device to be maintained if the fused resource data passes a data consistency detection; and a construction module, configured to construct a network topology map corresponding to the device to be maintained based on the location information and the fused resource data, wherein the nodes of the network topology map include the location information, device status, and service priority of the device to be maintained.

[0013] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0014] The memory stores computer-executed instructions;

[0015] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0016] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0017] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0018] The network resource operation and maintenance method, equipment, media, and products provided in this application embodiment acquire and process device identification information based on standardized strategies, ensuring the accuracy and standardization of terminal connection data and avoiding the problems of field omissions or format errors that are prone to occur in manual collection. Next, by deeply integrating network connection information with upper-layer business information, resource data across physical and logical layers is generated, realizing the accurate mapping between network entities and business functions and breaking the dilemma of data silos in traditional operation and maintenance. Subsequently, by using data consistency detection as a key quality control link, conflicting and abnormal data are effectively screened out. Based on the dynamic network topology map constructed from high-quality data that has passed verification and device location information, the traditional static topology is upgraded into a multi-dimensional perception map that integrates geographical location, real-time status, and business priority. This enables operation and maintenance personnel to quickly identify weak links affecting critical businesses and accurately locate the root cause of faults, thereby achieving a fundamental transformation from passive response to proactive early warning and from extensive management to refined optimization, and comprehensively improving the operation and maintenance efficiency, reliability, and intelligence level of the data network. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0020] Figure 1 A schematic diagram illustrating the network resource operation and maintenance scenario provided in this application;

[0021] Figure 2 Flowchart of the network resource operation and maintenance method provided in this application Figure 1 ;

[0022] Figure 3 Flowchart of the network resource operation and maintenance method provided in this application Figure 2 ;

[0023] Figure 4 A schematic diagram of the network resource operation and maintenance device provided in this application;

[0024] Figure 5 A schematic diagram of the structure of the electronic device provided in this application.

[0025] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0026] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0027] First, let me explain the terms used in this application:

[0028] The Address Resolution Protocol (ARP) is a core protocol in network communication used to resolve the IP address of a target device to its corresponding MAC address. When a host needs to communicate with another device on the same local area network (LAN), it first looks up the MAC address corresponding to the target IP in its local ARP cache table. If it does not find the MAC address, it broadcasts an ARP request packet (containing its own IP-MAC mapping and the target IP). The device that receives the request and whose IP matches will unicast its MAC address in response. The sender then updates its cache and completes data link layer encapsulation, ultimately achieving frame transmission based on IP addresses. This protocol solves the problem of converting network layer IP addresses to link layer physical addresses through a dynamic mapping mechanism, but it is only applicable to LANs and has security risks such as ARP spoofing. It needs to be combined with static ARP or dynamic detection techniques for prevention.

[0029] A MAC address (Media Access Control address) is a hardware-level physical address used to uniquely identify network devices at the data link layer. It consists of 48 bits of binary data (usually represented as 6 groups of hexadecimal numbers, such as 00:1A:2B:3C:4D:5E). It is uniformly assigned by IEEE to manufacturers of network interface controllers (NICs) such as network cards, switches, and routers. Each address is unique globally. When devices communicate in a local area network, the header of the data frame encapsulates the source MAC address and the destination MAC address, enabling devices such as switches to accurately forward data to the target device based on the MAC address table. At the same time, as the core identifier of the second layer of the OSI model, the MAC address, together with the IP address of the third layer, constitutes a dual address system of "physical identity and logical identity" for network communication, ensuring that data can be accurately delivered from the source to the destination within the same subnet.

[0030] Figure 1 This application provides a schematic diagram of a network resource operation and maintenance scenario, such as... Figure 1As shown, the specific application scenario of this application includes a device 110 to be maintained and a server 120. The server 120 obtains the device identification information corresponding to the device 110 based on a target data acquisition strategy, and standardizes the device identification information to obtain the terminal connection information corresponding to the device. Simultaneously, the server 120 also obtains the service information of the device 110 and merges this service information with the terminal connection information to obtain merged resource data. If the server 120 determines that the merged resource data passes the data consistency check, it obtains the location information corresponding to the device 110, and then constructs a network topology map corresponding to the device 110 based on the location information and the merged resource data. The nodes of this network topology map include the location information, device status, and service priority of the device 110. This achieves automated operation and maintenance of the network resources of the device to be maintained.

[0031] Figure 1 The server 120 shown can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. No restrictions are placed on this. The device 110 to be maintained can communicate with the server 120 via wireless networks such as 3G (third-generation mobile information technology), 4G (fourth-generation mobile information technology), and 5G (fifth-generation mobile information technology). No restrictions are placed on this as well.

[0032] In related technologies, the main approach is manual static management using spreadsheets. This involves using tools like Excel to record IP address pools, subnetting, device port configurations, and business-related information in a scattered manner. Maintenance personnel need to manually update the spreadsheet content regularly, and network analysis requires cross-spreading and logging into devices to query ARP entries for verification. This method suffers from drawbacks such as poor data consistency, low timeliness, low operational efficiency, high error rate, and difficulty in auditing. Furthermore, it cannot clearly define the relationship between IP address ranges and business information.

[0033] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0034] Figure 2 Flowchart of the network resource operation and maintenance method provided in this application Figure 1 ,like Figure 2 As shown, the process of this network resource operation and maintenance method includes at least steps S201 to S204, which are described in detail below:

[0035] Step S201: Obtain the device identification information corresponding to the device to be maintained based on the target data acquisition strategy, and perform standardized processing on the device identification information to obtain the terminal connection information corresponding to the device to be maintained.

[0036] For example, a pre-defined target data collection strategy is executed. This strategy explicitly specifies the collection protocol, frequency, and parameters, such as periodically polling the device to be maintained via SNMP protocol or command-line interface. The collection process directly acquires the device's raw identification data, which typically includes, but is not limited to, key fields such as IP address, MAC address, device manufacturer, model, and system version. The core data standardization processing stage then begins. This stage first cleans and standardizes the collected multi-source heterogeneous raw data. For example, MAC addresses of different formats (such as aa-bb-cc-11-22-33 and aabb.cc11.2233) are converted to a standard format, and IP address ranges and device model descriptions are normalized to eliminate ambiguity and inconsistency in the raw data. Based on this, the processing logic further extracts and associates deeper network connection attributes. For example, by parsing the device's ARP table, MAC address table, or routing table, IP address, MAC address, VLAN, and physical port information are associated and integrated to form a complete, context-sensitive terminal connection record. Ultimately, the system outputs structured terminal connection information, which includes not only standardized device identification information, but also its real-time connection status and topology in the network.

[0037] Step S202: Obtain the business information corresponding to the device to be maintained, and merge the business information with the terminal connection information to obtain the merged resource data.

[0038] For example, business information corresponding to the equipment to be maintained is obtained from the business management system. These systems typically include a CMDB configuration management database, an ITSM work order system, or a business asset list. The information obtained covers key business attributes such as business system name, responsible person, department, business priority, and pre-assigned IP address. Then, the core data fusion processing stage begins. This stage first standardizes and cleans the business information, ensuring that the format of its key fields (such as IP address) is completely consistent with the processed terminal connection information, and constructs a business baseline information table with IP address as the unique primary key. Next, the business baseline information table and the terminal connection information table are precisely associated through database table join operations. Using IP address as the matching key, business attributes (such as business name and responsible person) and network connection attributes (such as MAC address, physical port, and online status) are horizontally concatenated to generate a complete data record that simultaneously contains business and network dimensions. During this fusion process, the system performs logical checks, such as checking whether the pre-recorded MAC address in the business information is consistent with the actual MAC address collected from the network side, and marking any discrepancies as pending conflicts. Finally, the system outputs a merged global resource data table, which realizes a precise mapping between physical network entities and logical business units, providing a unified and authoritative data view for subsequent resource monitoring, impact analysis and fault location.

[0039] Step S203: If the merged resource data passes the data consistency test, then obtain the location information corresponding to the device to be maintained.

[0040] For example, once the merged resource data successfully passes the data consistency check—that is, ensuring that key fields such as IP address, MAC address, and device model are completely consistent between the business records and the network-collected data without any logical conflicts—the system will automatically trigger the process of obtaining the location information of the device to be maintained. Taking a substation scenario as an example, this process first uses the uniquely identified device identifier (such as the device hostname or asset number) from the verified, highly reliable merged resource data as the key index for accurate querying.

[0041] Optionally, in some feasible embodiments, multiple heterogeneous data sources can be linked to obtain its location information: First, the asset management system or CMDB configuration database can be queried to obtain the predefined physical location description of the device in the asset ledger, such as "the third compartment of the second cabinet in the relay protection room of the 500kV Qinglong Substation in XX District, XX City, XX Province". Second, if the device is a network device, its connected physical port information can be obtained from adjacent uplink devices through link layer discovery protocols such as LLDP or CDP, thereby inferring its location in the distribution room or communication rack. Third, an interface call can be made with the geographic information system to convert the text-formatted station name into precise latitude and longitude coordinates, and associate it with the electrical main wiring diagram of the substation to determine the logical location range of the device in the primary wiring of the substation. Finally, the multi-dimensional location information, including physical location, rack space, geographic coordinates, and logical intervals, obtained from different sources, is integrated and standardized to form a complete and structured equipment location file. This file is then linked and bound to the previously integrated business and connection information, providing a solid data foundation for subsequent precise positioning of equipment in 3D reality, automatic generation of network topology within the site, and rapid on-site addressing of faulty equipment.

[0042] Step S204: Construct a network topology map corresponding to the device to be maintained based on the location information and the fused resource data. The nodes of the network topology map include the location information, device status and service priority of the device to be maintained.

[0043] For example, a topology skeleton can be constructed based on the physical hierarchy (such as substation name, equipment room, and cabinet) in the device location information, with the substation as the root node, the equipment room as the child node, and the cabinet as the leaf node, forming a container hierarchy of physical space. Next, each device to be maintained is injected as a topology node into its corresponding physical container, and the integrated resource data is mapped to the node's visual attributes. Specifically, the coordinate offset of the cabinet space is extracted from the location information to achieve precise layout, and data such as device online status and CPU load are obtained in real time from the terminal connection information and converted into node colors and animation effects (e.g., green represents normal operation, red flashing represents failure). Simultaneously, business priority is extracted from the business information and defined as the node's shape or icon style (e.g., core servers are identified by a star, and ordinary workstations by a circle). Subsequently, by parsing the MAC address table and ARP table of network devices, logical connection lines between devices are automatically drawn, and the line thickness and style are dynamically adjusted according to link aggregation or redundancy protocols. Finally, the above elements are combined into a dynamic and interactive topology map through a graphics rendering engine. Operation and maintenance personnel can drill down to obtain full information about the devices by clicking on nodes. When a device fails, the topology map can automatically trigger an alarm escalation process based on business priority, ensuring that high-priority business device failures are handled first, thereby realizing a multi-dimensional integrated operation and maintenance view from physical space to logical relationships, and from static configuration to dynamic perception.

[0044] In the embodiments provided in this application, terminal connection data is obtained by standardizing device identification information, resource data is formed by integrating business information, and location information is integrated after consistency detection. Finally, a network topology map containing device location, status and business priority is constructed, realizing a closed loop of the whole process from data collection to intelligent visual operation and maintenance, which significantly improves the accuracy and response efficiency of device status monitoring, fault location and business impact analysis.

[0045] Based on the above embodiments, in one exemplary embodiment provided in this application, the specific implementation process of obtaining the business information corresponding to the device to be maintained and merging the business information with the terminal connection information to obtain the merged resource data may further include steps S301 and S302, which are described in detail below:

[0046] Step S301: If the data collection items corresponding to the device to be maintained can be collected through the preset application layer protocol, then the first data collection strategy is used as the target data collection strategy.

[0047] For example, before collecting data from the device under maintenance, a protocol compatibility test is first initiated. This involves sending a trial communication request based on a standard application layer protocol (such as HTTP, SNMP, NETCONF, etc.) and analyzing the format and content characteristics of the response data returned by the device. If the device can correctly respond to the query command of a specific protocol (such as SNMPv2c), and the returned data items are complete in format, with clear field meanings, and conform to the data structure and semantic requirements of the preset protocol specification, then the device is determined to meet the collection conditions of the preset application layer protocol. At this point, the system triggers the policy matching logic, calling the first data collection policy that completely corresponds to the verified protocol from the policy library as the target data collection policy. This policy has predefined collection parameters optimized for this protocol, including but not limited to authentication credentials (such as community words or OID lists), collection frequency, timeout time, and data parsing rules. Subsequently, the system starts the formal data collection task based on this target policy, efficiently obtaining device status information through standard protocol interfaces (such as SNMP Get requests), and using a built-in parser to convert the raw response data (such as ASN.1 encoding) into structured information. Ultimately, the system records the matching relationship between this protocol and the device, providing a basis for the automatic selection of strategies for similar devices in the future. This enables precise adaptation and automated deployment of data collection strategies in heterogeneous network environments, effectively improving the reliability and efficiency of data collection.

[0048] Optionally, taking SNMP as an example, upon receiving a command for a specific data collection item (such as CPU utilization, port status, etc.), the system queries the built-in device knowledge base. This knowledge base pre-stores standardized management capabilities and protocol characteristics supported by different device manufacturers and models. The system matches the target device's manufacturer and model information with the data collection item. If the knowledge base explicitly records that the device model provides standardized and complete SNMP MIB library support for the target data collection item, SNMP will be prioritized as the data collection mode. This is because the SNMP protocol has advantages in efficiency, standardization, and overhead, and is particularly suitable for performance indicators requiring high-frequency, automated data collection. Conversely, if the device is an older model or a specific proprietary device with an incomplete SNMP implementation, or if the target data collection item is non-standard information (such as certain diagnostic logs or complex configuration fragments) and SNMP cannot provide corresponding OID support, the system will automatically determine to use the command-line data collection mode. In command-line mode, the system retrieves a set of instructions specific to the manufacturer and model of the device from the knowledge base, along with corresponding login authentication parameters. A connection is established via SSH or Telnet, and commands are sent. A targeted parser (e.g., using regular expressions or text templates) is then used to accurately extract the values ​​of the target data collection items from the returned unstructured text output. The entire decision-making and execution process is dynamic, continuously learning and updating the knowledge base. For example, it records cases where SNMP acquisition of certain information fails for a particular device model but succeeds via command line, thereby continuously optimizing subsequent data collection mode selection strategies. Ultimately, this achieves optimal adaptation of the data collection method in heterogeneous network environments, ensuring both accuracy and high efficiency in data acquisition.

[0049] Step S302: If the data collection items corresponding to the device to be maintained cannot be collected through the preset application layer protocol, then the second data collection strategy shall be used as the target data collection strategy.

[0050] For example, when it is detected that the device under maintenance cannot successfully obtain the target collection item through the preset application layer protocol (such as SNMP, NETCONF, etc.), the collection policy switching mechanism will be automatically triggered: First, the protocol adaptation layer will determine the protocol interaction failure based on the device response timeout, abnormal data format, or error code, and record the characteristics of the collection item being incompatible with the protocol; then, the policy engine will call the second data collection policy preset for this scenario from the policy library as the new target policy. This policy usually includes a command line interaction process based on SSH / Telnet. Its specific implementation process includes matching the corresponding login authentication template and command line sequence according to the device manufacturer and model, establishing an encrypted connection and sending a specific query command, and then cleaning the returned unstructured output through a multi-level text parser, such as using regular expressions to extract key indicators such as port traffic counters or the number of error packets; finally, this policy switching relationship will be updated to the device knowledge base to form a protocol avoidance scheme for specific collection items of this device model, so that the reliable collection of key data can still be guaranteed through the command line degradation scheme when the standardized protocol fails.

[0051] In the embodiments provided in this application, the optimal data acquisition strategy is automatically selected by dynamically adapting the collectability of the application layer protocol. This ensures standardized and efficient data acquisition for protocol-compatible devices and flexible data acquisition for non-protocol-compatible devices, significantly improving the integrity and reliability of data acquisition from multiple types of devices.

[0052] Based on the above embodiments, in one exemplary embodiment provided in this application, the specific implementation process of the above network resource operation and maintenance method may further include steps S401 to S403, which are described in detail below:

[0053] Step S401: Determine the maintenance data corresponding to the device to be maintained based on the preset application layer protocol.

[0054] Step S402: Establish a communication channel with the device to be maintained based on the first data acquisition strategy, and determine the access permissions corresponding to the data to be maintained.

[0055] Step S403: Obtain the identification information corresponding to the data to be maintained based on access permissions, and use the identification information to determine the device identification information corresponding to the device to be maintained.

[0056] For example, taking SNMP as the first data acquisition strategy, the scope of data to be maintained in the device can be determined first based on the preset SNMP application layer protocol characteristics. This range can be obtained from the standard MIB library. For example, standardized indicators such as system description, interface status, and CPU load. Then, based on the specific parameters configured in the SNMP policy (including device IP address, SNMP community word or user authentication information, port number, and timeout), the system establishes a management communication channel with the target device via the UDP protocol, and verifies the community word or user credentials to confirm the read-only or read-write access permissions the local end has for the target data. After the channel is established and the authorization is verified, an SNMP Get request for a specific object identifier (OID) is sent to the device. The data in the returned message is successfully obtained and parsed to extract key information that uniquely identifies the device (such as obtaining the device model and operating system version by querying the sysDescr object with OID 1.3.6.1.2.1.1.0, or obtaining the device hostname by the sysName object with OID 1.3.6.1.2.1.1.5.0). Finally, this parsed identification information is structured and stored as the formal device identification information of the device to be maintained, providing a data foundation for subsequent device identification, asset management and topology discovery.

[0057] In the embodiments provided in this application, the scope of data to be maintained is precisely defined by a preset application layer protocol, a secure communication channel is established in conjunction with a first data collection strategy and access permissions are verified, and finally the accurate and secure collection of device identification information is achieved, providing a reliable data foundation and access protection for subsequent maintenance operations.

[0058] Based on the above embodiments, in one exemplary embodiment provided in this application, the specific implementation process of the above network resource operation and maintenance method may further include steps S501 to S503, which are described in detail below:

[0059] Step S501: Determine the data collection items corresponding to the equipment to be maintained and the data collection instructions corresponding to the data collection items.

[0060] Step S502: Establish a connection with the target switch based on the second data acquisition strategy. The target switch includes the switch corresponding to the device to be maintained.

[0061] Step S503: Execute a data acquisition command on the target switch to obtain the device identification information corresponding to the device to be maintained.

[0062] For example, after determining through device identification and collection item analysis that CLI command-line method is required for data collection, the system matches the corresponding device login authentication parameters (such as SSH key, username / password) and the specific instructions required to obtain specific device identification information from a pre-set command library based on the manufacturer, model, and system version characteristics of the target switch (e.g., using the "display interface description" command to obtain port description information for Huawei switches, and the "show interface description" command for Cisco switches). Then, based on the SSH connection parameters (including IP address, port number, encryption algorithm, and timeout settings) defined in the second data collection strategy, an encrypted command-line session channel is established with the target switch. After successful session establishment, predefined collection commands are automatically sent to the switch one by one. The system then uses real-time parsing of the unstructured text output returned by the commands, employing parsing techniques such as regular expressions or text template matching to accurately extract key identification information directly associated with the device to be maintained, such as MAC address, IP address, connected port, and VID. Finally, this cleaned data is standardized into structured device identification records, completing the device information collection process based on command-line interaction.

[0063] In the embodiments provided in this application, the target switch is connected through a second data acquisition strategy and a data acquisition command is executed to indirectly obtain the identification information of the device to be maintained. This effectively solves the problem of acquiring data from non-protocol-compatible devices, improves the integrity and flexibility of data acquisition, and provides broader device coverage and reliable data support for operation and maintenance management. Based on the above embodiments, in one exemplary embodiment provided in this application, the terminal connection information includes an IP address. The specific implementation process of fusing service information and terminal connection information further includes steps S601 to S603, which are detailed below:

[0064] Step S601: Standardize the business information to obtain a baseline business information table with IP address as the key.

[0065] Step S602: Determine the data association between the baseline service information table and the terminal connection information based on the IP address.

[0066] Step S603: Based on the data association relationship, the business information and terminal connection information are fused and processed.

[0067] For example, the raw business information imported from the business system can be standardized and cleaned, including unifying the IP address format (e.g., standardizing "192.168.001.001" to "192.168.1.1"), filling in missing fields, and normalizing text information such as business names and responsible persons. This results in a standardized baseline business information table with IP addresses as the primary key. Subsequently, using the IP address as the unique association key, the baseline business information table is matched and associated with a terminal connection information table collected from the network side through database connection operations, establishing a precise IP address mapping relationship between the two tables. If an IP address in the business table has no corresponding record in the connection information table, the association is marked as an "IP offline" anomaly. Finally, based on this association, the successfully matched records undergo data fusion processing. Attributes such as the business system name and responsible person in the business information are horizontally concatenated with network attributes such as the MAC address and switch port in the terminal connection information, generating a fused data record that simultaneously contains both business and network dimensions. A difference report is generated for anomaly records where association fails, thus completing the deep integration of business information and network connection information.

[0068] Optionally, the business information is standardized to construct a baseline business information table with IP address as the key. The specific process includes: performing format validation and normalization on the original business data using regular expressions; verifying the MAC address format while filtering invalid characters (such as non-numeric alphanumeric symbols); uniformly converting fields such as VLAN number and interface description (e.g., unifying VLAN 100 and VLAN-100 to 100); and completing missing information (e.g., supplementing firmware version numbers by mapping device model to the manufacturer's default configuration). The final result is a baseline business information table with IP address as the unique key, containing standardized fields such as device type (e.g., 220kV line protection device), service priority (P0-level core equipment), assigned bay (e.g., the second bay in the 220kV GIS equipment area), and responsible person. Subsequently, a relationship is established between the baseline service information table and the terminal connection information based on the IP address: connection data such as ARP entries and MAC address tables are collected from the substation network switch to extract the device IP, MAC, physical port (such as GigabitEthernet0 / 1), VLAN (such as VLAN 100 corresponding to the 220kV equipment area) and online status; at the same time, the service information table is imported from the CMDB or configuration management platform, and the two are automatically matched through IP address to form an association mapping of "IP, service and connection".

[0069] Optionally, taking a substation as an example, the dynamic connection data (such as port traffic and link status) collected by the switch can be deeply integrated with static business information (such as device type and priority) to generate a fused resource view. For example, a device with IP address 192.168.1.10 can be labeled as a "220kV line protection device of P0 level," and associated with its physical location (5th cabinet on the 2nd floor of the main control building), electrical topology location (220kV bay 2), real-time status (CPU utilization 85%, temperature 72℃), and connection attributes (port GigabitEthernet0 / 1, VLAN 100). This fused data not only allows maintenance personnel to quickly locate the physical and logical location of the device via IP address, but also automatically analyzes the impact range during faults (e.g., the offline status of a P0 level protection device will trigger a 220kV line circuit breaker blocking alarm). Simultaneously, it provides four-dimensional decision support ("business, connection, status, and location") for substation 3D visualization monitoring, intelligent inspection route planning, and emergency response plan formulation, significantly improving the accuracy, safety, and response efficiency of substation maintenance.

[0070] In the embodiments provided in this application, a precise association between business information and terminal connection data is established through standardized processing using IP addresses as keys, realizing the structured fusion of multi-source heterogeneous data. This provides a unified and reliable data foundation for subsequent topology construction, status monitoring, and fault analysis, significantly improving the availability and analysis efficiency of operation and maintenance data.

[0071] Based on the above embodiments, in one exemplary embodiment provided in this application, the specific implementation process of the above network resource operation and maintenance method may further include steps S701 to S703, which are described in detail below:

[0072] Step S701: Determine whether the MAC address in the terminal connection information is consistent with the MAC address in the service information based on the IP address.

[0073] Step S702: If consistent, then the merged resource data has passed the data consistency check.

[0074] In step S703, if there is a discrepancy, a prompt message corresponding to the data conflict is generated, and an anomaly report is generated and pushed based on the prompt message.

[0075] For example, using the device IP address as the anchor point, the MAC address corresponding to the device is extracted from the terminal connection information (such as the physical address obtained through switch ARP entries or device self-reported data). Simultaneously, the expected MAC address associated with the same IP address is extracted from the standardized service information table (such as the device's factory MAC address recorded in the CMDB or the service MAC address labeled by the configuration management platform). Consistency verification is achieved through direct comparison of the two source MAC addresses. If the two are completely consistent (e.g., 00:1A:2B:3C:4D:5E in the terminal connection information completely matches 00:1A:2B:3C:4D:5E in the service information table), then the device MAC address data corresponding to that IP address is determined to be conflict-free, serving as one of the key criteria for passing the data consistency check. If discrepancies exist (e.g., terminal connection information displays 00:1A:2B:3C:4D:5E while the business information table records 00:1A:2B:3C:4D:6F), a data conflict identification mechanism is triggered. This mechanism automatically generates a prompt message containing the conflicting IP, actual MAC address, expected MAC address, timestamp, and possible causes (e.g., device replacement without updated configuration, data entry error, network hijacking, etc.). This prompt message will serve as the core content of the anomaly report and will be pushed to the responsible operations and maintenance personnel or management team through preset push channels (e.g., alarm module of the operations and maintenance management platform, email notification, SMS reminder). Simultaneously, the anomaly report will be associated with the device's business, priority, and historical change records to help quickly locate the root cause of the problem (e.g., whether there have been recent device replacements or configuration modifications). In other words, precise association of IP addresses can achieve MAC address consistency verification across data sources.

[0076] In the embodiments provided in this application, the consistency between the terminal connection information and the MAC address in the business information is verified by associating the IP address, thereby realizing the automated detection of data conflicts and the push of anomaly reports, which effectively improves the quality of operation and maintenance data and provides a reliable data verification mechanism for fault diagnosis and system optimization.

[0077] Based on the above embodiments, in one exemplary embodiment provided in this application, the specific implementation process of the above network resource operation and maintenance method may further include steps S801 to S803, which are described in detail below:

[0078] Step S801: Construct a logical model of the IP address of the device to be maintained based on the merged resource data.

[0079] Step S802: Determine the graphical elements corresponding to the IP address logical model, and construct the network topology diagram corresponding to the device to be maintained based on the graphical elements.

[0080] Step S803: Obtain the real-time device identification information of the device to be maintained, and update the network topology map based on the real-time device identification information.

[0081] In some feasible implementations, constructing an IP address logical model requires using IP addresses from integrated resource data as the core, integrating related information such as subnet masks, VLAN divisions, service priorities, and device status to form a structured logical framework. For example, IP addresses within the same subnet can be grouped according to service priority, associated with device types (such as servers, switches, and protection devices) and real-time status (such as online / offline, CPU utilization, and temperature values), and the connection relationships between IPs can be defined based on network topology rules (such as IP links mapped through switch ports). This model not only clarifies the logical affiliation and service attributes of IP addresses but also provides a structured foundation for subsequent visual mapping. Next, the graphical elements must be determined in accordance with business requirements and visualization specifications. For example, circular nodes represent server devices, square nodes represent network devices, red highlights P0-level core devices, green indicates online status, and yellow indicates alarm status. Connection styles (solid lines for physical connections, dashed lines for logical connections) and label formats (IP address, device type, and status) are also defined. These elements use unified visual coding rules to map data to graphics, ensuring the topology diagram intuitively reflects the business attributes and connection relationships of devices. Finally, the network topology diagram is constructed based on the logical model and graphical elements. A visualization engine renders IP addresses, connection relationships, and status information into a dynamic topology diagram. Node positions are arranged according to physical location or logical hierarchy, and connections display bandwidth utilization or link status. A real-time data interface is integrated; when real-time device identification information (such as changes in device online status or performance index updates) is obtained from the devices under maintenance, the system automatically triggers a topology diagram update mechanism. For example, the node color of an offline device is changed from green to gray, the link bandwidth utilization value is updated, and a status change alarm is pushed to the maintenance platform.

[0082] In the embodiments provided in this application, the transformation from static data to dynamic visualization view is realized through precise modeling of logical models, intelligent mapping of graphical elements and dynamic synchronization of real-time data. This not only supports maintenance personnel to monitor equipment status and business impact in real time, but also provides intuitive, accurate and timely decision support for rapid fault location, optimized resource allocation and automated maintenance strategy execution, significantly improving the intelligence level and response efficiency of maintenance management.

[0083] Please see Figure 3 , Figure 3 This is a flowchart illustrating the network resource operation and maintenance method provided in this application. Figure 2 ,like Figure 3As shown, it determines whether the data collection items corresponding to the device to be maintained can be collected through a preset application protocol. If the data collection items corresponding to the device to be maintained can be collected through the preset application layer protocol, then the first data collection strategy is used as the target data collection strategy; if the data collection items corresponding to the device to be maintained cannot be collected through the preset application layer protocol, then the second data collection strategy is used as the target data collection strategy. Based on the target data collection strategy, the device identification information corresponding to the device to be maintained is obtained, and the device identification information is standardized to obtain the terminal connection information corresponding to the device to be maintained; the service information corresponding to the device to be maintained is obtained, and the service information and terminal connection information are fused to obtain the fused resource data; based on the IP address, it is determined whether the MAC address in the terminal connection information is consistent with the MAC address in the service information; if they are inconsistent, a prompt message corresponding to the data conflict is generated, and an anomaly report is generated and pushed based on the prompt message. If they are consistent, it is determined that the fused resource data passes the data consistency check, and the location information corresponding to the device to be maintained is obtained; based on the location information and the fused resource data, a network topology map corresponding to the device to be maintained is constructed. The nodes of the network topology map include the location information, device status, and service priority of the device to be maintained. For detailed implementation process, please refer to the descriptions in the aforementioned embodiments; they will not be repeated here.

[0084] Figure 4 This is a schematic diagram of the network resource operation and maintenance device provided in this application, as shown below. Figure 4 As shown, the network resource operation and maintenance device 40 provided in this embodiment includes: an acquisition module 410, used to acquire device identification information corresponding to the device to be maintained based on a target data acquisition strategy, and to standardize the device identification information to obtain terminal connection information corresponding to the device to be maintained; a fusion module 420, used to acquire service information corresponding to the device to be maintained, and to fuse the service information with the terminal connection information to obtain fused resource data; a judgment module 430, used to acquire the location information corresponding to the device to be maintained if the fused resource data passes the data consistency detection; and a construction module 440, used to construct a network topology map corresponding to the device to be maintained based on the location information and the fused resource data, wherein the nodes of the network topology map include the location information, device status, and service priority of the device to be maintained.

[0085] In one possible implementation, the acquisition module 410 is further configured to: if the data collection items corresponding to the device to be maintained can be collected through a preset application layer protocol, then use the first data collection strategy as the target data collection strategy; if the data collection items corresponding to the device to be maintained cannot be collected through the preset application layer protocol, then use the second data collection strategy as the target data collection strategy.

[0086] In one possible implementation, the acquisition module 410 is further configured to: determine the maintenance data corresponding to the device to be maintained based on a preset application layer protocol; establish a communication channel with the device to be maintained based on a first data acquisition strategy, and determine the access permissions corresponding to the maintenance data; acquire the identification information corresponding to the maintenance data based on the access permissions, and use the identification information to determine the device identification information corresponding to the device to be maintained.

[0087] In one possible implementation, the acquisition module 410 is further configured to: determine the collection item corresponding to the device to be maintained and the data acquisition instruction corresponding to the collection item; establish a connection with the target switch based on the second data acquisition strategy, the target switch including the switch corresponding to the device to be maintained; and execute the data acquisition instruction on the target switch to obtain the device identification information corresponding to the device to be maintained.

[0088] In one possible implementation, the fusion module 420 is further configured to: standardize the service information to obtain a baseline service information table with IP address as the key; determine the data association between the baseline service information table and the terminal connection information based on the IP address; and fuse the service information and the terminal connection information based on the data association.

[0089] In one possible implementation, the judgment module 430 is further configured to determine whether the MAC address in the terminal connection information is consistent with the MAC address in the service information based on the IP address; if they are consistent, it is determined that the merged resource data has passed the data consistency detection; if they are inconsistent, a prompt message corresponding to the data conflict is generated, and an anomaly report is generated and pushed based on the prompt message.

[0090] In one possible implementation, the above-mentioned construction module 440 is further configured to: construct a logical model of the IP address corresponding to the device to be maintained based on the fused resource data; determine the graphical elements corresponding to the logical model of the IP address, and construct a network topology map corresponding to the device to be maintained based on the graphical elements; and obtain the real-time device identification information of the device to be maintained, so as to update the network topology map based on the real-time device identification information.

[0091] The network resource operation and maintenance device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0092] Figure 5 A schematic diagram of the structure of the electronic device provided in this application. Figure 5 As shown, the electronic device 50 provided in this embodiment includes at least one processor 510 and a memory 520. Optionally, the device 50 further includes a communication component 530. The processor 510, memory 520, and communication component 530 are connected via a bus 540.

[0093] In a specific implementation, at least one processor 510 executes computer execution instructions stored in memory 520, causing at least one processor 510 to perform the above-described method.

[0094] The specific implementation process of processor 510 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0095] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0096] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0097] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0098] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0099] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0100] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0101] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0102] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0103] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0104] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0105] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0106] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0107] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for network resource operation and maintenance, characterized in that, include: Based on the target data acquisition strategy, the device identification information corresponding to the device to be maintained is obtained, and the device identification information is standardized to obtain the terminal connection information corresponding to the device to be maintained. Obtain the business information corresponding to the device to be maintained, and fuse the business information with the terminal connection information to obtain the fused resource data; If the merged resource data passes the data consistency test, then the location information corresponding to the device to be maintained is obtained; Based on the location information and the fused resource data, a network topology map corresponding to the device to be maintained is constructed. The nodes of the network topology map include the location information, device status, and service priority of the device to be maintained.

2. The method as described in claim 1, characterized in that, Before obtaining the device identification information corresponding to the device to be maintained based on the target data acquisition strategy, the method further includes: If the data collection items corresponding to the device to be maintained can be collected through a preset application layer protocol, then the first data collection strategy will be used as the target data collection strategy. If the data collection items corresponding to the device to be maintained cannot be collected through the preset application layer protocol, then the second data collection strategy will be used as the target data collection strategy.

3. The method as described in claim 2, characterized in that, The process of obtaining the device identification information corresponding to the device to be maintained based on the target data acquisition strategy includes: The maintenance data corresponding to the device to be maintained is determined based on the preset application layer protocol. A communication channel is established between the device to be maintained and the data to be maintained based on the first data acquisition strategy, and the access permissions corresponding to the data to be maintained are determined. Based on the access permissions, obtain the identification information corresponding to the data to be maintained, and use the identification information to determine the device identification information corresponding to the device to be maintained.

4. The method as described in claim 2, characterized in that, The process of obtaining the device identification information corresponding to the device to be maintained based on the target data acquisition strategy includes: Determine the data collection items corresponding to the equipment to be maintained and the data collection instructions corresponding to the data collection items; A connection with the target switch is established based on the second data acquisition strategy, wherein the target switch includes a switch corresponding to the device to be maintained; The data acquisition command is executed on the target switch to obtain the device identification information corresponding to the device to be maintained.

5. The method according to any one of claims 1 to 4, characterized in that, The terminal connection information includes an IP address, and the process of fusing the service information with the terminal connection information includes: The business information is standardized to obtain a baseline business information table with IP address as the key; The data association between the baseline service information table and the terminal connection information is determined based on the IP address; The business information and the terminal connection information are fused together based on the data association relationship.

6. The method as described in claim 5, characterized in that, The method further includes: Based on the IP address, determine whether the MAC address in the terminal connection information is consistent with the MAC address in the service information; If they are consistent, then the merged resource data is determined to have passed the data consistency check. If there is a discrepancy, a prompt message corresponding to the data conflict will be generated, and an anomaly report will be generated and pushed based on the prompt message.

7. The method as described in claim 5, characterized in that, The method further includes: Based on the fused resource data, construct a logical model of the IP address corresponding to the device to be maintained; Determine the graphical elements corresponding to the IP address logical model, and construct the network topology diagram corresponding to the device to be maintained based on the graphical elements; Obtain the real-time device identification information of the device to be maintained, and update the network topology map based on the real-time device identification information.

8. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1 to 7.

Images