Resource ledger management control method and system based on IP

By creating a virtual IP pool and building a master-redundant device pair for large-scale enterprise network devices, the resource ledger management problem caused by the complexity of IP address management is solved, and efficient management of resource ledgers and stable operation of network systems are achieved.

CN120675972APending Publication Date: 2025-09-19SHANXI ELECTRIC POWER CO POWER COMM CENT
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510818419.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-06-18
Publication Date
2025-09-19

AI Technical Summary

Technical Problem

In large-scale enterprise environments, the allocation, management, and maintenance of IP addresses are complex, making resource tracking difficult and increasing the difficulty of resource ledger management.

Method used

By creating a virtual IP pool corresponding to the network device category, configuring a virtual IP for each network device using preset distribution rules, building a primary and redundant device pair, and monitoring and updating the resource ledger through management devices.

Benefits of technology

It reduces the difficulty of resource ledger management and maintenance, improves the timeliness and accuracy of resource ledgers, and ensures the stability of the network system and the task reconstruction capability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120675972A_ABST
    Figure CN120675972A_ABST
Patent Text Reader

Abstract

The invention is applicable to the technical field of resource ledger management, and particularly relates to an IP-based resource ledger management control method and system, and the method comprises the steps: obtaining the types of network equipment in a region, creating virtual IP pools in one-to-one correspondence with the types, accessing the network equipment into the virtual IP pools, and distributing the network equipment to the virtual IP pools through a preset distribution rule. Configuring a virtual IP for each network device; and in the network device, defining a management device, traversing all the virtual IP pools, selecting an IP group, issuing the IP group to the management device, and creating a resource ledger. By constructing the virtual IP pool, the virtual IP resource allocation and scheduling process is simplified, the management efficiency is improved, and meanwhile, by allocating the same virtual IP to the main equipment and the redundant equipment, when the main equipment breaks down, tasks can be taken over through the redundant equipment, efficient and continuous operation of a network system is ensured, and the service life of the network system is prolonged. And the stability and the task reconstruction capability of the network system are greatly improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of resource ledger management, and in particular to an IP-based resource ledger management control method and system. Background Art

[0002] Resource ledger management is a systematic management method that aims to comprehensively and systematically record, track and manage all types of resources within an enterprise or organization. Resources can include materials, equipment, personnel and funds. Through Internet Protocol (IP) technology, by reading the IP identifier of each network device, network resources can be managed in a ledger, and the status, usage and flow of resources can be monitored in real time throughout the entire network to ensure efficient resource allocation.

[0003] As the number of resources increases, the allocation, management and maintenance of IP addresses will become more complicated, especially in large-scale enterprise environments. Problems such as IP address conflicts and duplicate allocations may make resource tracking difficult and increase the difficulty of ledger management. Therefore, "how to use virtual IP technology to update resource ledgers" is the technical problem that the present invention needs to solve. Summary of the Invention

[0004] The purpose of the present invention is to provide an IP-based resource ledger management and control method and system to solve the problems raised in the above background technology.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] A resource ledger management and control method and system based on IP, the method comprising:

[0007] Obtain the categories of network devices in the area, create a virtual IP pool corresponding to each category, connect the network devices to the virtual IP pool, and configure a virtual IP for each network device based on the preset distribution rules;

[0008] In the network device, a management device is defined, all virtual IP pools are traversed, an IP group is selected, and the IP group is sent to the management device to create a resource ledger;

[0009] Traversing the resource ledger, determining the risk level of network devices in each category, where the risk level includes high and low, and selecting a primary device and a redundant device respectively, constructing a primary and redundant device pair, unifying the virtual IP addresses of the primary and redundant device pairs, and obtaining a target IP address;

[0010] Collect the activity data of the master and redundant device pairs, send a notification message to the management device via the target IP, integrate the notification information and the preset fault definition principle, determine whether the master device has failed, and if so, use the redundant device to take over the master device, push broadcast information to the management device, and update the resource ledger.

[0011] Furthermore, the step of "creating a virtual IP pool corresponding to each category" includes:

[0012] Configuring multi-level thresholds of the virtual IP pool, calculating the total amount of the network devices, and monitoring changes in the total amount and categories;

[0013] The multi-level thresholds and changes are integrated to dynamically adjust the virtual IP pool.

[0014] Furthermore, the distribution rules include:

[0015] Divide the virtual IP pool into several sub-pools and determine the access rights of each sub-pool;

[0016] The priorities of the network devices are defined, and mappings between the sub-pools and the network devices are constructed based on the priorities.

[0017] Furthermore, the step of “defining a management device in the network device, traversing all virtual IP pools, selecting an IP group, and sending the IP group to the management device to create a resource ledger” includes:

[0018] In each virtual IP pool, a master IP is selected, integrated to obtain an IP group, and a monitoring strategy is integrated into the management device to determine the newly added device;

[0019] Build a configuration template library, use preset template matching rules to select the target template, and configure the newly added devices.

[0020] Furthermore, the step of “determining the risk level of network devices in each category” includes:

[0021] Determining the risk level classification criteria, wherein the classification criteria at least include: responsibilities, physical environment, and historical failure records;

[0022] Selecting a primary device from a high-risk level and a redundant device from a low-risk level, integrating the primary device and the redundant device to form a primary-redundant device pair;

[0023] A bidirectional redundancy strategy is embedded into the primary-residual device pair.

[0024] Furthermore, the step of "collecting activity data of the primary and secondary device pairs, sending a notification message to a management device via the target IP, and integrating the notification information with a preset fault definition principle" includes:

[0025] Taking a snapshot of the activity data and inserting a timestamp into the snapshot;

[0026] The snapshots are sorted according to the timestamps, adjacent snapshots are compared, incremental data is determined, and the incremental data is sent to the management device.

[0027] Furthermore, the step of “using a redundant device to take over the primary device, pushing broadcast information to the management device, and updating the resource ledger” includes:

[0028] Build a load balancer to distribute the load on the primary device after the redundant device takes over;

[0029] Add a time window to the load balancer, record the takeover time, shift the time window, and generate a recovery strategy.

[0030] Furthermore, the system includes:

[0031] The configuration module is used to obtain the categories of network devices in the area, create a virtual IP pool corresponding to the category, connect the network devices to the virtual IP pool, and configure a virtual IP for each network device according to the preset distribution rules;

[0032] A creation module is used to define a management device in the network device, traverse all virtual IP pools, select IP groups, and send the IP groups to the management device to create a resource ledger;

[0033] A module is provided for traversing the resource ledger, determining the risk level of network devices in each category, wherein the risk level includes high and low, selecting a primary device and a redundant device respectively, constructing a primary and redundant device pair, unifying the virtual IP addresses of the primary and redundant device pairs, and obtaining a target IP address;

[0034] An update module is used to collect activity data of the master and redundant device pairs, send notification messages to the management device via the target IP, integrate the notification information and the preset fault definition principle, and determine whether the master device has failed. If so, the redundant device is used to take over the master device, and push broadcast information to the management device to update the resource ledger.

[0035] Furthermore, the configuration module includes:

[0036] A monitoring unit, configured to configure multi-level thresholds of the virtual IP pool, calculate the total amount of the network devices, and monitor changes in the total amount and categories;

[0037] The dynamic adjustment unit is used to integrate the multi-level thresholds and changes and dynamically adjust the virtual IP pool.

[0038] Furthermore, the creation module includes:

[0039] A determination unit is used to select a master IP in each virtual IP pool, integrate it to obtain an IP group, integrate a monitoring strategy into the management device, and determine the newly added device;

[0040] The selection unit is used to build a configuration template library, use preset template matching rules to select the target template, and configure the newly added device.

[0041] Compared with the prior art, the present invention has the following beneficial effects:

[0042] By configuring virtual IPs, the present invention greatly reduces the difficulty of managing and maintaining resource ledgers and improves the timeliness of resource ledgers. By building IP groups, different types of network devices can be uniformly monitored, which helps to eliminate departmental data barriers and ensure the authenticity and reliability of resource ledgers. By building a virtual IP pool, the virtual IP resource allocation and scheduling process is simplified, and management efficiency is improved. At the same time, by allocating the same virtual IP to the main and redundant devices, when the main device fails, the redundant device can be used to take over the task, ensuring the efficient and continuous operation of the network system, and greatly improving the stability of the network system and the task reconstruction capability. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention.

[0044] Figure 1 A flowchart of an IP-based resource ledger management and control method provided in an embodiment of the present invention.

[0045] Figure 2 This is a block diagram of the first sub-process of the IP-based resource ledger management and control method provided in an embodiment of the present invention.

[0046] Figure 3 This is a block diagram of the second sub-process of the IP-based resource ledger management and control method provided in an embodiment of the present invention.

[0047] Figure 4 This is a block diagram of the third sub-process of the IP-based resource ledger management and control method provided in an embodiment of the present invention.

[0048] Figure 5 This is a block diagram of the fourth sub-process of the IP-based resource ledger management and control method provided in an embodiment of the present invention.

[0049] Figure 6 A block diagram of the IP-based resource ledger management and control system provided in an embodiment of the present invention.

[0050] Figure 7 This is a block diagram of the configuration module in the IP-based resource ledger management and control system provided by an embodiment of the present invention.

[0051] Figure 8 A block diagram of the composition of the creation module in the IP-based resource ledger management and control system provided by an embodiment of the present invention.

[0052] Figure 9 This is a block diagram of the components of the IP-based resource ledger management and control system provided by an embodiment of the present invention.

[0053] Figure 10 A block diagram of the composition of the update module in the IP-based resource ledger management and control system provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0054] In order to make the technical problems, technical solutions and beneficial effects to be solved by the present invention more clearly understood, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0055] Figure 1 The following is a general flow chart of an IP-based resource ledger management and control method and system. In an embodiment of the present invention, an IP-based resource ledger management and control method includes:

[0056] S100: Obtain categories of network devices in the area, create a virtual IP pool corresponding to the categories, connect the network devices to the virtual IP pool, and configure a virtual IP for each network device according to a preset distribution rule.

[0057] According to the functions and characteristics of network devices, network devices are divided into several categories, a separate virtual IP pool is created for each category, and network devices are connected to the corresponding virtual IP pool. A virtual IP is allocated to each network device according to the preset distribution rules.

[0058] S200: In the network device, a management device is defined, all virtual IP pools are traversed, an IP group is selected, and the IP group is sent to the management device to create a resource ledger.

[0059] From the network devices, a management device is selected, where the management device is mainly used to coordinate and manage the network devices, and is also responsible for tasks such as network device monitoring and updating resource ledgers; from each virtual IP pool, a virtual IP is selected and integrated to obtain an IP group, and the management device is configured using the IP group; in addition, the IP group is continued to be used to establish a link between the management device and all network devices, and a resource ledger is created, where the management device has multiple virtual IPs at the same time, and each virtual IP represents a different category of connection points; by configuring the IP group, the access capability of the management device is greatly improved, ensuring that the management device can operate normally in a variety of network environments and monitor all network devices.

[0060] S300: Traverse the resource ledger to determine the risk level of network devices in each category, where the risk levels include: high and low, and select the main device and redundant device respectively, build a main and redundant device pair, unify the virtual IPs of the main and redundant device pairs, and obtain the target IP.

[0061] Network devices are classified into high-risk or low-risk levels based on their responsibilities, physical environment, and historical fault records. A primary device is selected from the high-risk level, and a redundant device is selected from the low-risk level, with one primary device and one or more redundant devices. The primary and redundant devices are integrated to generate a primary-and-redundant device pair, and the virtual IP addresses of the primary-and-redundant device pairs are unified, with this virtual IP address serving as the sole access point to the primary-and-redundant device pair. In other words, when a problem occurs with the primary device, the network system can switch tasks to the backup device through the virtual IP address, ensuring seamless access and smooth operation of the task.

[0062] S400: Collect the activity data of the master and redundant device pairs, send a notification message to the management device via the target IP, integrate the notification information and the preset fault definition principle, and determine whether the master device fails. If so, use the redundant device to take over the master device, push broadcast information to the management device, and update the resource ledger.

[0063] A management device is used to collect activity data of the primary and redundant device pairs, where the activity data includes: device performance indicators, load conditions, and network connection status; the activity data is sent to the management device in the form of a notification, which is a form of feedback reporting, and includes the operating status, performance indicators, and possible signs of failure of the primary and redundant devices; by utilizing the notification and fault definition principles, it is determined whether the primary device has a fault, where the fault definition rule is a specific way to determine the fault, and the faults include too long a device response time, abnormal data transmission, and device offline, etc.

[0064] If the primary device fails, the redundant device will take over the ongoing tasks in the primary device; after takeover, the redundant device will continue to provide network services through the target IP; at the same time, the management device will push broadcast information to all network devices, notifying all relevant network devices that the redundancy switch is successful and the primary device is in a faulty state; the management device will update the resource ledger to record the takeover status and device operation status of the redundant device to ensure the accuracy and timeliness of the resource ledger.

[0065] In Example 2, Figure 2 The implementation process of the IP-based resource ledger management control method provided by an embodiment of the present invention is shown. The steps of "creating a virtual IP pool corresponding to each category" are described in detail as follows:

[0066] S101: Configure multi-level thresholds of the virtual IP pool, calculate the total amount of the network devices, and monitor changes in the total amount and categories.

[0067] S102: Integrate the multi-level thresholds and changes and dynamically adjust the virtual IP pool.

[0068] Set multi-level thresholds for the number of virtual IPs in the virtual IP pool, count the changes in the total number of network devices, and dynamically adjust the number of virtual IPs.

[0069] For example, a three-level threshold is configured, where the first threshold is 14, the second threshold is 21, and the third threshold is 30. If the number of network devices is 15 at the current moment, the number of virtual IPs should be adjusted to the second threshold. Through the above adjustment method, resource overload can be avoided, management difficulty can be reduced, and performance bottlenecks or resource waste can be prevented.

[0070] In embodiment 3, different from embodiment 1, in this embodiment of the present invention, the distribution rule includes:

[0071] Divide the virtual IP pool into several sub-pools and determine the access rights of each sub-pool;

[0072] The priorities of the network devices are defined, and mappings between the sub-pools and the network devices are constructed based on the priorities.

[0073] The virtual IP pool is divided into several sub-pools, each of which contains several virtual IPs. The access rights of each sub-pool are determined according to the department and attributes of the network device, thereby defining the access scope of the network device to reduce unnecessary device access, prevent unauthorized devices from accessing specific sub-pools, and ensure the security and reliability of data in the sub-pools.

[0074] In Example 4, Figure 3The implementation process of the IP-based resource ledger management control method provided by an embodiment of the present invention is shown. The following details the steps of "defining a management device in the network device, traversing all virtual IP pools, selecting an IP group, and sending the IP group to the management device to create a resource ledger".

[0075] S201: In each virtual IP pool, a master IP is selected, and an IP group is obtained by integration. A monitoring strategy is integrated into the management device to determine a newly added device.

[0076] A virtual IP is selected from each virtual IP pool and defined as the master IP. All master IPs are integrated to generate an IP group. The monitoring strategy refers to the specific method of monitoring the network system composed of network devices. The monitoring strategy is used to identify the IP requests or device registration information of newly added devices.

[0077] S202: Build a configuration template library, use preset template matching rules to select a target template, and configure the newly added device.

[0078] When the management device recognizes the IP request of a newly added device, it uses the preset template matching rules to select the target template from the configuration template library and configure the newly added device; the template matching rules include: specific configuration parameters, network policies and function settings, etc.

[0079] In Example 5, Figure 4 The implementation process of the IP-based resource ledger management control method provided by an embodiment of the present invention is shown. The steps of "determining the risk level of network devices in each category" are described in detail below:

[0080] S301: Determine the risk level classification criteria, wherein the classification criteria at least include: responsibilities, physical environment, and historical failure records.

[0081] According to the risk level classification standards, network equipment is divided into several risk levels.

[0082] S302: Select a primary device from a high-risk level and a redundant device from a low-risk level, integrate the primary device and the redundant device, and construct a primary-redundant device pair.

[0083] S303: Embed a bidirectional redundancy strategy into the primary and redundant device pairs.

[0084] The bidirectional redundancy strategy can start the redundant device and take over the running tasks when the main device fails. At the same time, when the redundant device fails, the main device can also take over the running tasks. The core of the bidirectional redundancy strategy is automatic switching.

[0085] In Example 6, Figure 5 The implementation process of the IP-based resource ledger management control method provided by an embodiment of the present invention is shown. The steps of "collecting activity data of the primary and secondary device pairs, sending a notification message to the management device via the target IP, and integrating the notification information with the preset fault definition principle" are described in detail below:

[0086] S401: Taking a snapshot of the activity data and inserting a timestamp into the snapshot.

[0087] A snapshot is an instant capture of real-time data from a primary and secondary device pair. It can save the status information of the primary and secondary device pairs at a certain moment, such as network traffic, device performance, and load conditions. A timestamp is generated based on the snapshot generation time and inserted into the corresponding snapshot.

[0088] S402: Sort the snapshots according to the timestamps, compare adjacent snapshots, determine incremental data, and send the incremental data to the management device.

[0089] Perform incremental identification on adjacent snapshots to find out what changes have occurred between adjacent snapshots, extract incremental data, and send the incremental data to the management device. Changes include addition, modification, or deletion.

[0090] In Example 7, Figure 5 The implementation process of the IP-based resource ledger management control method provided by an embodiment of the present invention is shown. The steps of "using a redundant device to take over the master device, pushing broadcast information to the management device, and updating the resource ledger" are described in detail below:

[0091] S403: Build a load balancer to distribute the load on the primary device after the redundant device takes over.

[0092] After a redundant device takes over the primary device, the load balancer can evenly distribute the workload in progress on the primary device to avoid overloading of any redundant device.

[0093] S404: Add a time window to the load balancer, record the takeover time, shift the time window, and generate a recovery strategy.

[0094] Record the takeover time of the load balancer and generate a time window, where the time window is composed of the takeover start time and the takeover end time. Expand or reduce the time window based on the fault recovery of the primary device, and after the fault is recovered, use the recovery strategy to reply to the tasks in the primary device. The recovery strategy is the specific recovery process of the task, which usually includes: fault detection, resource allocation, data recovery, and service recovery.

[0095] Figure 6 The following is a structural block diagram of the IP-based resource ledger management and control system provided by an embodiment of the present invention. The IP-based resource ledger management and control system 1 includes:

[0096] Configuration module 11, used to obtain the category of network devices in the area, create a virtual IP pool corresponding to the category, connect the network devices to the virtual IP pool, and configure a virtual IP for each network device according to the preset distribution rules;

[0097] A creation module 12 is used to define a management device in the network device, traverse all virtual IP pools, select IP groups, and send the IP groups to the management device to create a resource ledger;

[0098] Obtaining module 13, for traversing the resource ledger, determining the risk level of network devices in each category, wherein the risk level includes: high and low, and selecting a primary device and a redundant device respectively, constructing a primary and redundant device pair, unifying the virtual IP addresses of the primary and redundant device pairs, and obtaining a target IP address;

[0099] The update module 14 is used to collect the activity data of the master and redundant device pairs, send a notification message to the management device via the target IP, integrate the notification information and the preset fault definition principle, and determine whether the master device fails. If so, the redundant device is used to take over the master device, and push broadcast information to the management device to update the resource ledger.

[0100] Figure 7 The following is a structural block diagram of the IP-based resource ledger management and control system provided by an embodiment of the present invention. The configuration module 11 includes:

[0101] A monitoring unit 111 is configured to configure multi-level thresholds of the virtual IP pool, calculate the total number of network devices, and monitor changes in the total number and categories;

[0102] The dynamic adjustment unit 112 is used to integrate the multi-level thresholds and changes and dynamically adjust the virtual IP pool.

[0103] Figure 8The following is a structural block diagram of the IP-based resource ledger management and control system provided by an embodiment of the present invention. The creation module 12 includes:

[0104] The determining unit 121 is used to select a master IP in each virtual IP pool, integrate it to obtain an IP group, integrate the monitoring strategy into the management device, and determine the newly added device;

[0105] The selection unit 122 is used to build a configuration template library, select a target template using a preset template matching rule, and configure the newly added device.

[0106] Figure 9 The following is a structural block diagram of the IP-based resource ledger management and control system provided by an embodiment of the present invention. The obtaining module 13 includes:

[0107] A classification unit 131 is configured to determine a classification standard for the risk level, wherein the classification standard includes at least: responsibility, physical environment, and historical fault records;

[0108] A construction unit 132 is configured to select a primary device in a high-risk level and a redundant device in a low-risk level, and integrate the primary and redundant devices to construct a primary-redundant device pair;

[0109] The embedding unit 133 is configured to embed a bidirectional redundancy policy into the primary and redundant device pairs.

[0110] Figure 10 The following is a structural block diagram of the IP-based resource ledger management and control system provided by an embodiment of the present invention. The update module 14 includes:

[0111] The inserting unit 141 is configured to extract a snapshot of the activity data and insert a timestamp into the snapshot;

[0112] a comparison unit 142 for sorting the snapshots according to the timestamps, comparing adjacent snapshots, determining increments, and sending the increments to the management device;

[0113] The distribution unit 143 is used to build a load balancer to distribute the load in the primary device after the redundant device takes over;

[0114] The recording unit 144 is configured to add a time window to the load balancer, record the takeover time, shift the time window, and generate a recovery strategy.

[0115] The configuration module 11 is mainly used to complete step S100, the creation module 12 is mainly used to complete step S200, the acquisition module 13 is mainly used to complete step S300, and the update module 14 is mainly used to complete step S400;

[0116] The monitoring unit 111 is mainly used to complete step S101, and the dynamic adjustment unit 112 is mainly used to complete step S102;

[0117] The determining unit 121 is mainly used to complete step S201, and the selecting unit 122 is mainly used to complete step S202;

[0118] The dividing unit 131 is mainly used to complete step S301, the constructing unit 132 is mainly used to complete step S302, and the embedding unit 133 is mainly used to complete step S303;

[0119] The inserting unit 141 is mainly used to complete step S401 , the comparing unit 142 is mainly used to complete step S402 , the allocating unit 143 is mainly used to complete step S403 , and the recording unit 144 is mainly used to complete step S404 .

[0120] The above are only preferred embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention description and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A resource ledger management and control method based on IP, characterized in that: The method comprises: Obtain the categories of network devices in the area, create a virtual IP pool corresponding to each category, connect the network devices to the virtual IP pool, and configure a virtual IP for each network device based on the preset distribution rules; In the network device, a management device is defined, all virtual IP pools are traversed, an IP group is selected, and the IP group is sent to the management device to create a resource ledger; Traversing the resource ledger, determining the risk level of network devices in each category, where the risk level includes high and low, and selecting a primary device and a redundant device respectively, constructing a primary and redundant device pair, unifying the virtual IP addresses of the primary and redundant device pairs, and obtaining a target IP address; Collect the activity data of the master and redundant device pairs, send a notification message to the management device via the target IP, integrate the notification information and the preset fault definition principle, determine whether the master device has failed, and if so, use the redundant device to take over the master device, push broadcast information to the management device, and update the resource ledger.

2. The IP-based resource ledger management and control method according to claim 1, characterized in that: The step of "creating a virtual IP pool corresponding to each category" includes: Configuring multi-level thresholds of the virtual IP pool, calculating the total amount of the network devices, and monitoring changes in the total amount and categories; The multi-level thresholds and changes are integrated to dynamically adjust the virtual IP pool.

3. The IP-based resource ledger management and control method according to claim 2, characterized in that: The distribution rules include: Divide the virtual IP pool into several sub-pools and determine the access rights of each sub-pool; The priorities of the network devices are defined, and mappings between the sub-pools and the network devices are constructed based on the priorities.

4. The IP-based resource ledger management and control method according to claim 3, characterized in that: The step of "defining a management device in the network device, traversing all virtual IP pools, selecting an IP group, and sending the IP group to the management device to create a resource ledger" includes: In each virtual IP pool, a master IP is selected, all obtained IP groups are integrated, and a monitoring strategy is integrated into the management device to determine the newly added devices; Build a configuration template library, use preset template matching rules to select the target template, and configure the newly added devices.

5. The IP-based resource ledger management and control method according to claim 1, characterized in that: The step of "determining the risk level of network devices in each category" includes: Determining the risk level classification criteria, wherein the classification criteria at least include: responsibilities, physical environment, and historical failure records; Selecting a primary device from a high-risk level and a redundant device from a low-risk level, integrating the primary device and the redundant device to form a primary-redundant device pair; A bidirectional redundancy strategy is embedded into the primary-residual device pair.

6. The IP-based resource ledger management and control method according to claim 1, characterized in that: The step of "collecting activity data of the primary and secondary device pairs, sending a notification message to a management device via the target IP, and integrating the notification information with a preset fault definition principle" includes: Taking a snapshot of the activity data and inserting a timestamp into the snapshot; The snapshots are sorted according to the timestamps, adjacent snapshots are compared, incremental data is determined, and the incremental data is sent to the management device.

7. The IP-based resource ledger management and control method according to claim 1, characterized in that: The step of "using a redundant device to take over the master device, pushing broadcast information to the management device, and updating the resource ledger" includes: Build a load balancer to distribute the load on the primary device after the redundant device takes over; Add a time window to the load balancer, record the takeover time, shift the time window, and generate a recovery strategy.

8. An IP-based resource ledger management and control system, characterized in that: The system comprises: The configuration module is used to obtain the categories of network devices in the area, create a virtual IP pool corresponding to the category, connect the network devices to the virtual IP pool, and configure a virtual IP for each network device according to the preset distribution rules; A creation module is used to define a management device in the network device, traverse all virtual IP pools, select IP groups, and send the IP groups to the management device to create a resource ledger; A module is provided for traversing the resource ledger, determining the risk level of network devices in each category, wherein the risk level includes high and low, selecting a primary device and a redundant device respectively, constructing a primary and redundant device pair, unifying the virtual IP addresses of the primary and redundant device pairs, and obtaining a target IP address; An update module is used to collect activity data of the master and redundant device pairs, send notification messages to the management device via the target IP, integrate the notification information and the preset fault definition principle, and determine whether the master device has failed. If so, the redundant device is used to take over the master device, and push broadcast information to the management device to update the resource ledger.

9. The IP-based resource ledger management and control system according to claim 8, characterized in that: The configuration module includes: A monitoring unit, configured to configure multi-level thresholds of the virtual IP pool, calculate the total amount of the network devices, and monitor changes in the total amount and categories; The dynamic adjustment unit is used to integrate the multi-level thresholds and changes and dynamically adjust the virtual IP pool.

10. The IP-based resource ledger management and control system according to claim 9, characterized in that: The creation module includes: A determination unit is used to select a master IP in each virtual IP pool, integrate it to obtain an IP group, integrate a monitoring strategy into the management device, and determine the newly added device; The selection unit is used to build a configuration template library, use preset template matching rules to select the target template, and configure the newly added device.