A method, apparatus, and readable storage medium for automatically updating a dedicated line resource ledger.

Abstract

This application provides a method, apparatus, and readable storage medium for automatically updating a dedicated line resource ledger. The method includes: acquiring log records and configuration information of the equipment corresponding to the dedicated line resource; detecting whether there are up / down records of physical ports in the log records to obtain a first detection result; determining a port configuration verification strategy based on the first detection result, and performing port configuration verification according to the verification strategy to obtain a second detection result; and determining a ledger update strategy for the dedicated line resource based on the second detection result. This application provides a method for automatically updating a dedicated line resource ledger, which can realize automatic ledger updates without manual intervention, ensuring the real-time nature of resource ledger records and greatly improving accuracy, effectively supporting fault handling and automatic activation of Internet dedicated line services.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a method, apparatus and readable storage medium for automatically updating a dedicated line resource ledger. Background Technology

[0002] An internet leased line resource ledger is a detailed inventory that records and manages internet leased line resources. It is crucial for ensuring the effective management, optimization, and monitoring of network resources. By establishing and maintaining such a ledger, resource usage can be better tracked, improving the quality and efficiency of network services.

[0003] Currently, the basic network of operators is divided into transmission network, IP data network, voice switching network, etc. Each of these networks has a resource ledger to record the corresponding records of resources such as device name, port name, IP address, customer name, and resource ledger. The accuracy of this resource ledger is very important. Inaccurate resource ledger will lead to a series of serious problems such as the inability to handle faults and the inability to automatically activate services.

[0004] Therefore, ensuring the real-time nature and accuracy of resource ledgers has become a problem that needs to be solved. Summary of the Invention

[0005] The technical problem to be solved by this application is to provide a method, apparatus and readable storage medium for automatically updating a dedicated line resource ledger, in order to address the above-mentioned shortcomings of the prior art and solve the problems existing in the prior art.

[0006] Firstly, this application provides a method for automatically updating a dedicated line resource ledger.

[0007] The methods include:

[0008] S1. Obtain the log records and configuration information of the devices corresponding to the leased line resources;

[0009] S2. Check if there are any up / down records for physical ports in the log records to obtain the first detection result;

[0010] S3. Determine the port configuration verification strategy based on the first detection result, and perform port configuration verification according to the verification strategy to obtain the second detection result;

[0011] S4. Determine the ledger update strategy for dedicated line resources based on the second detection result.

[0012] In some embodiments, S3, determining the port configuration verification strategy based on the first detection result includes:

[0013] If the first detection result indicates the existence of up / down records, then the port configuration verification strategy is determined as follows: verify whether the current configuration information of the device's physical port is consistent with the historical configuration.

[0014] In some embodiments, S4 includes:

[0015] If the second detection result obtained by checking whether the current configuration information of the device's physical port is consistent with the historical configuration is inconsistent, then the ledger update strategy for leased line resources is determined to be: update the leased line resource ledger according to the current configuration information of the device's physical port.

[0016] In some embodiments, S4 includes:

[0017] If the second detection result obtained by verifying whether the current configuration information of the device's physical port is consistent with the historical configuration is consistent, then the ledger update strategy for leased line resources is determined to be: do not update the leased line resource ledger.

[0018] In some embodiments, S3, determining the port configuration verification strategy based on the first detection result includes:

[0019] If the first detection result indicates that there are no up / down records, then the port configuration verification strategy is determined to be: verify whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration.

[0020] In some embodiments, S4 includes:

[0021] If the second detection result obtained by checking whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration is inconsistent, then the ledger update strategy for leased line resources is determined to be: update the leased line resource ledger according to the current configuration information of the logical port VLAN interface.

[0022] In some embodiments, S4 includes:

[0023] If the second detection result obtained by verifying whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration is consistent, then the ledger update strategy for leased line resources is determined to be: do not update the leased line resource ledger.

[0024] Secondly, this application provides a device for automatically updating a dedicated line resource ledger.

[0025] The device includes:

[0026] The information acquisition module is configured to acquire log records and configuration information of the devices corresponding to the leased line resources.

[0027] The first detection module is configured to detect whether there are up / down records of physical ports in the log records and obtain the first detection result;

[0028] The second detection module is configured to determine a port configuration verification strategy based on the first detection result, and perform port configuration verification according to the verification strategy to obtain a second detection result.

[0029] The ledger update module is configured to determine the ledger update strategy for dedicated line resources based on the second detection result.

[0030] Thirdly, this application provides an automatic update device for dedicated line resource ledgers, including a memory and a processor. The memory stores a computer program, and the processor is configured to run the computer program to implement the automatic update method for dedicated line resource ledgers described in the first aspect.

[0031] Fourthly, this application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the automatic update method for leased line resource ledgers described in the first aspect.

[0032] This application provides a method, apparatus, and readable storage medium for automatically updating a dedicated line resource ledger. The method includes: acquiring log records and configuration information of the device corresponding to the dedicated line resource; detecting whether there are up / down records of physical ports in the log records to obtain a first detection result; determining a port configuration verification strategy based on the first detection result, and performing port configuration verification according to the verification strategy to obtain a second detection result; and determining a ledger update strategy for the dedicated line resource based on the second detection result. This application provides a method for automatically updating a dedicated line resource ledger, which can realize automatic ledger updates without manual intervention, ensuring the real-time nature of resource ledger records and greatly improving accuracy, effectively supporting fault handling and automatic activation of Internet dedicated line services. Attached Figure Description

[0033] 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.

[0034] Figure 1 This is a typical diagram of a leased internet line access.

[0035] Figure 2 A flowchart illustrating an automatic update method for a dedicated line resource ledger provided in this application embodiment;

[0036] Figure 3 A flowchart illustrating yet another method for automatically updating a dedicated line resource ledger, as provided in an embodiment of this application.

[0037] Figure 4 This is a schematic diagram illustrating a specific scenario example of how to automatically update the ledger when resources change, provided in an embodiment of this application.

[0038] Figure 5 This is a schematic diagram illustrating a specific scenario example two regarding how to automatically update the ledger when resources change, as provided in the embodiments of this application.

[0039] Figure 6 A schematic diagram of the structure of an automatic update device for leased line resource ledger provided in this application embodiment;

[0040] Figure 7 A schematic diagram of another automatic update device for dedicated line resource ledgers provided in this application embodiment.

[0041] The accompanying drawings have illustrated 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 specific embodiments. Detailed Implementation

[0042] To enable those skilled in the art to better understand the technical solution of this application, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

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

[0044] It is understood that, without conflict, the various embodiments and features in the embodiments of this application can be combined with each other.

[0045] It is understood that, for ease of description, only the parts relevant to this application are shown in the accompanying drawings, while parts unrelated to this application are not shown in the drawings.

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

[0047] It is understood that the terms "first," "second," etc., used in the embodiments of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

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

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

[0050] It is understood that the units and modules involved in the embodiments of this application can be implemented by software or by hardware. For example, the units and modules can be located in the processor.

[0051] Internet leased line resource ledgers are widely used in many fields, such as:

[0052] (1) Construction of Telemedicine Networks: In accordance with the notices issued by the General Offices of the Ministry of Industry and Information Technology and the National Health Commission, in order to strengthen the construction of telemedicine network capabilities, it is required to establish broadband access ledgers for medical and health institutions at all levels. This includes list-based management of medical and health institutions that do not have broadband access, in order to improve network access rates and ensure that more than 98% of primary-level medical and health institutions have access to the Internet.

[0053] (2) Management of e-Government Extranet: The "Construction and Management Standards for Wuwei City's E-Government Extranet (2021 Edition)" issued by the Wuwei City Data Resources Administration Bureau states that the construction and management of the e-government extranet need to follow certain standards. These include network construction principles and network support services, to ensure the effective operation and management of the e-government extranet.

[0054] (3) IPv6 Deployment and Application: In deepening the deployment and application of IPv6, basic telecommunications enterprises are required to establish information ledgers to investigate the deployment and application of NAT44 devices and to formulate work plans and timelines for network deNAT. This helps to promote the popularization and application of IPv6 and improve the quality and efficiency of network services.

[0055] A typical internet leased line resource ledger might include the following:

[0056] a. Network equipment list: including the model, configuration, and deployment location of devices such as routers, switches, and servers.

[0057] b. Bandwidth and IP address allocation: Record the bandwidth and IP address range allocated to each user or department.

[0058] c. Service Level and Performance Indicators: including performance parameters such as network speed, latency, and reliability.

[0059] d. Maintenance and upgrade records: Record the maintenance, upgrades and troubleshooting of the equipment.

[0060] Currently, operators' data internet access serves a large number of customers. These customers typically need to browse the internet, send and receive emails, and publish applications. To meet these customers' internet access needs, operators provide dedicated internet lines. These dedicated lines require providing transmission and data internet resources. Users access data centers (IDCs) through the operator's transmission network and data internet to achieve their internet access goals.

[0061] Figure 1 This is a typical diagram of a leased internet line access, such as... Figure 1 As shown, when a user accesses the internet, the operator records the user's transmission and data internet resources. This record is called the internet user access resource ledger. Currently, the most common solution for IP data network ledgers is to manually record the resources using Excel or WPS spreadsheets. When the service is activated, the resources used by the customer are manually recorded; when the equipment or transmission resources used by the customer change, the ledger is manually updated. The creation and updating of the ledger are both done manually on the spreadsheet. Below is a sample of a manually recorded IP data network ledger:

[0062]

[0063] For data internet devices, the device configuration is as follows:

[0064] r1-s-gdgz-xx#

[0065] interface GigabitEthernet5 / 0

[0066] description A company,DIA,100M,GDLT2405219

[0067] switchport

[0068] switchport trunk encapsulation dot1q

[0069] switchport trunk allowed vlan 1622

[0070] switchport mode trunk

[0071] load-interval 30

[0072] no SNMP trap link-status

[0073] end

[0074] interface Vlan1622

[0075] description A company,DIA,100M,GDLT2405219

[0076] IP address 210.21.128.0 255.255.255.248

[0077] no IP redirects

[0078] load-interval 30

[0079] no SNMP trap link-status

[0080] VRRP 330 IP 210.21.128.1

[0081] VRRP 330 Priority 200

[0082] vrrp 330preempt

[0083] end

[0084] In addition to the fields listed in the table above, there are also transmission routes, account managers, service activation time, and customer addresses. When a customer reports a fault, this ledger is used to query the device resources corresponding to that user in order to accurately handle the customer's network fault.

[0085] However, the existing manual ledger record forms have significant drawbacks, mainly in the following aspects:

[0086] 1. When a malfunction occurs, updating the ledger becomes difficult. Changes in the resources on the equipment require manual updating of the ledger forms. However, ledger managers can easily forget or fill in the information incorrectly, leading to inaccurate ledger entries.

[0087] For example, if a device port belonging to a business fails, in order to quickly resolve the fault, the on-site personnel will switch the faulty port to a normal port. The configuration under the faulty port must be copied to the normal port. For example, if Company A's original port GigabitEthernet5 / 0 fails and needs to be switched to GigabitEthernet6 / 0, the log record of Company A needs to be updated manually in the table. The person updating the log record and the person handling the fault are often not the same person, resulting in the log record not being updated.

[0088] 2. When the network is cut over, it is difficult to update the ledger. Due to potential equipment failures, it is necessary to replace the customer's business access equipment, which requires manual updating of the forms and ledgers. However, the ledger managers are prone to forgetting or making mistakes, resulting in inaccurate ledgers.

[0089] For example, Company A originally connected to the r1-s-gdgz-xsk and GigabitEtherne5 / 0 devices and ports. After the cutover, the connected devices and ports are r2-s-gdgz-xsk and GigabitEtherne6 / 0. This requires manual updating of Company A's records, but it is difficult for the network cutover personnel and the record-keeping personnel to update them synchronously.

[0090] Inaccurate records can lead to significant problems in handling user malfunctions and automatically activating services later on.

[0091] Examples of troubleshooting issues:

[0092] User A reported a fault, stating that they could not access the internet. After receiving the report, the network administrator checked the records and found that User A's access port was GigabitEthernet5 / 0. In fact, due to a previous port failure, it had been changed to GigabitEthernet6 / 0, which caused the fault to be delayed and prolonged the time.

[0093] Example of service activation issues:

[0094] User A's service access port was changed to GigabitEthernet6 / 0 due to a previous device port failure, but this was not updated in the ledger. Now, User B's service is activated, and the system synchronizes with the ledger. The system records GigabitEthernet6 / 0 as an idle port, so it allocates GigabitEthernet6 / 0 to User B. However, this port has actually been given to User A, causing the service to fail to activate automatically.

[0095] In response to the difficulties in updating ledgers in existing technologies, which affect fault handling and service activation, this application aims to solve the problem of difficult ledger updates. The ledger system matches with the equipment daily and automatically updates the ledgers without manual intervention, realizing automated updates of data network resource ledgers.

[0096] 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 be described below with reference to the accompanying drawings.

[0097] This application provides a method for automatically updating a dedicated line resource ledger. The workflow of this method can be implemented by electronic devices, such as computers and handheld smart terminals. For ease of explanation, the embodiments of this application are described with the computer as the subject of the method execution.

[0098] It is understood that the technical solution of this application can be implemented by a software system in a computer, such as an IT system for ledgers.

[0099] Figure 2 This is a schematic diagram illustrating the automatic update method for leased line resource ledgers provided in an embodiment of this application. Figure 3 Another schematic diagram of the automatic update method for the dedicated line resource ledger provided in the embodiments of this application is shown below. Figure 2 as well as Figure 3 As shown, this application provides a method for automatically updating a dedicated line resource ledger, the method comprising S1-S4, as follows:

[0100] S1. Obtain the log records and configuration information of the devices corresponding to the leased line resources;

[0101] In this context, "leased line resource corresponding equipment" refers to the data internet equipment on the user side, and the data internet resources occupied by this equipment are its leased line resources. Log recording for leased line resource corresponding equipment is an important function in computer network and system management. It involves recording events, status changes, error messages, and other relevant information that occur during the operation of the leased line resource corresponding equipment. Configuration information can include both hardware and software configurations.

[0102] In this step, the log records and configuration information of the device corresponding to the dedicated line resource can be obtained at preset intervals. For example, log in to the device at midnight every day to obtain the log records and configuration information.

[0103] S2. Check if there are any up / down records for physical ports in the log records to obtain the first detection result;

[0104] The port up / down logging function refers to the system's ability to automatically record changes in the state of a port within a network device. Specifically, when a port changes from "down" to "up," or vice versa, the system generates corresponding log entries. These logs help network administrators quickly understand the port's operational status changes and take timely action. This function is particularly useful in scenarios where many specific interfaces repeatedly go up / down, especially when APs connected in a network cause normal up / down cycles. By disabling the logging of these interface up / down status changes, unnecessary log output can be reduced, simplifying the management process.

[0105] In this step, the first step is to check whether there are up / down records for physical ports in the log records. The first detection result is divided into two types: there are up / down records for physical ports and there are no up / down records for physical ports.

[0106] S3. Determine the port configuration verification strategy based on the first detection result, and perform port configuration verification according to the verification strategy to obtain the second detection result;

[0107] In this step, based on the first detection result obtained in step S2, a verification strategy of the corresponding type is selected, and then the configuration verification is performed based on the strategy.

[0108] In some embodiments, S3, determining the port configuration verification strategy based on the first detection result includes:

[0109] If the first detection result indicates the existence of up / down records, then the port configuration verification strategy is determined as follows: verify whether the current configuration information of the device's physical port is consistent with the historical configuration.

[0110] The historical configuration can be configuration information from a previously preset time period.

[0111] For example, if the device log records port up / down records, query the configuration under each physical port and check whether the port configuration is consistent with the configuration of the previous day.

[0112] In some embodiments, S3, determining the port configuration verification strategy based on the first detection result includes:

[0113] If the first detection result indicates that there are no up / down records, then the port configuration verification strategy is determined to be: verify whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration.

[0114] The historical configuration can be configuration information from a previously preset time period.

[0115] For example, if the device log records no physical port up / down records, check whether the configuration under the logical port VLAN interface is consistent with the previous day.

[0116] S4. Determine the ledger update strategy for dedicated line resources based on the second detection result.

[0117] In some embodiments, if the first detection result indicates the presence of an up / down record, S4 includes:

[0118] If the second detection result obtained by checking whether the current configuration information of the device's physical port is consistent with the historical configuration is inconsistent, then the ledger update strategy for leased line resources is determined to be: update the leased line resource ledger according to the current configuration information of the device's physical port.

[0119] Specifically, if the verification and inspection finds inconsistencies in port configurations, the resource ledger will be updated according to the configuration of the port.

[0120] In some embodiments, if the first detection result indicates the presence of an up / down record, S4 further includes:

[0121] If the second detection result obtained by verifying whether the current configuration information of the device's physical port is consistent with the historical configuration is consistent, then the ledger update strategy for leased line resources is determined to be: do not update the leased line resource ledger.

[0122] Specifically, if the port configuration is verified to be consistent, the ledger will not be updated and will remain unchanged.

[0123] In some embodiments, if the first detection result is that there are no up / down records, S4 includes:

[0124] If the second detection result obtained by checking whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration is inconsistent, then the ledger update strategy for leased line resources is determined to be: update the leased line resource ledger according to the current configuration information of the logical port VLAN interface.

[0125] Specifically, if the verification finds that there are modification records under the VLAN interface configuration, the ledger will be updated according to the modification records.

[0126] In some embodiments, if the first detection result is that there are no up / down records, S4 further includes:

[0127] If the second detection result obtained by verifying whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration is consistent, then the ledger update strategy for leased line resources is determined to be: do not update the leased line resource ledger.

[0128] To facilitate understanding of this solution, the following is a specific scenario example of how the ledger is automatically updated when resources change:

[0129] Scene 1:

[0130] Figure 4 This is a schematic diagram illustrating a specific scenario example of how to automatically update the ledger when resources change, as provided in the embodiments of this application. Figure 4 As shown:

[0131] Company A's internet service access is via the carrier's equipment r1-s-gdgz-xsk, port GigabitEtherne5 / 0. The resource change log is as follows:

[0132] ① Log in to the ledger system at midnight to access the device (you can use the telnet command to log in and save the device configuration to the system);

[0133] ② The system checked the log records of device r1-s-gdgz-xsk and found that there were down records on port GigabitEtherne5 / 0, and a few minutes later there were up records on GigabitEtherne6 / 0;

[0134] ③ Upon checking the configuration under the GigabitEtherne6 / 0 port, it was found to be different from the configuration of the previous day;

[0135] ④ Modify Company A's access operator ledger record, automatically changing the original port GigabitEtherne5 / 0 to GigabitEtherne6 / 0.

[0136] Scene 2:

[0137] Figure 5 This is a schematic diagram illustrating a specific scenario example two regarding how to automatically update the ledger when resources change, as provided in the embodiments of this application. Figure 5 As shown:

[0138] Company A discovered that it lacked sufficient IP addresses during operation, so it applied to its ISP for an expansion of IP address capacity, increasing the number from 8 to 16. Specifically, the IP address range was expanded from 210.21.128.0 / 29 (29-bit subnet mask) to 210.21.128.0 / 28 (28-bit subnet mask). Equipment configuration:

[0139] interface Vlan1622

[0140] description A company,DIA,100M,GDLT2405219

[0141] IP address 210.21.128.0 255.255.255.240

[0142] At this time, the network resources used by the user have changed. Traditionally, the ledger is updated manually. This patent adopts an automated resource ledger update system, which is divided into logical resource changes and physical resource changes.

[0143] I. Logical Resource Changes:

[0144] ① The IT system logs into the devices at midnight every day (using the telnet command) and saves the device configuration to the system.

[0145] ② Check the device log records; there are no records of the port being down.

[0146] ③ The system matched the saved configuration with the configuration from the previous day and found that the configuration under the vlan1622 interface had changed.

[0147] ④ The system updates the ledger, and the IP address resource used by Company A is automatically changed from 210.21.128.0 / 29 to 210.21.128.0 / 28.

[0148] This application provides a method for automatically updating a dedicated line resource ledger, which can realize automatic updating of the ledger without manual intervention, ensuring the real-time nature of the resource ledger records and greatly improving the accuracy, effectively supporting fault handling and automatic activation of Internet dedicated line services.

[0149] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0150] Figure 6 This is a schematic diagram of the automatic update device for leased line resource ledgers provided in the embodiments of this application, as shown below. Figure 6 As shown, this application provides an automatic update device for leased line resource ledgers, the device comprising:

[0151] Information acquisition module 11 is configured to acquire log records and configuration information of the devices corresponding to the leased line resources;

[0152] The first detection module 12 is configured to detect whether there are up / down records of physical ports in the log records and obtain the first detection result;

[0153] The second detection module 13 is configured to determine a port configuration verification strategy based on the first detection result, and perform port configuration verification according to the verification strategy to obtain a second detection result;

[0154] The ledger update module 14 is configured to determine the ledger update strategy for dedicated line resources based on the second detection result.

[0155] Regarding the limitations on the automatic update device for dedicated line resource ledgers, please refer to the limitations on the automatic update method for dedicated line resource ledgers in the above embodiments of this application, which will not be repeated here.

[0156] Figure 7 Another schematic diagram of the automatic update device for leased line resource ledger provided in the embodiments of this application is shown below. Figure 7 As shown, in some embodiments, this application provides an automatic update device for leased line resource ledgers, including a memory 22 and a processor 21. The memory stores a computer program, and the processor is configured to run the computer program to execute the automatic update method for leased line resource ledgers in the above embodiments of this application.

[0157] The memory is connected to the processor. The memory can be flash memory, read-only memory or other types of memory. The processor can be a central processing unit or a microcontroller.

[0158] In some embodiments, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the automatic update method for leased line resource ledgers in the above embodiments of this application.

[0159] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), DVD or other optical disc storage, cartridges, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer.

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

Claims

1. A method for automatically updating a dedicated line resource ledger, characterized in that, The method includes: S1. Obtain the log records and configuration information of the devices corresponding to the leased line resources; S2. Check if there are any up / down records for physical ports in the log records to obtain the first detection result; S3. Determine the port configuration verification strategy based on the first detection result, and perform port configuration verification according to the verification strategy to obtain the second detection result; S4. Determine the ledger update strategy for dedicated line resources based on the second detection result; In S3, the verification strategy for determining the port configuration based on the first detection result includes: If the first detection result indicates the existence of up / down records, then the port configuration verification strategy is determined to be: verify whether the current configuration information of the device's physical port is consistent with the historical configuration; If the first detection result indicates that there are no up / down records, then the port configuration verification strategy is determined to be: verify whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration.

2. The method for automatically updating the dedicated line resource ledger according to claim 1, characterized in that, S4 includes: If the second detection result obtained by checking whether the current configuration information of the device's physical port is consistent with the historical configuration is inconsistent, then the ledger update strategy for leased line resources is determined to be: update the leased line resource ledger according to the current configuration information of the device's physical port.

3. The method for automatically updating the dedicated line resource ledger according to claim 1, characterized in that, S4 includes: If the second detection result obtained by verifying whether the current configuration information of the device's physical port is consistent with the historical configuration is consistent, then the ledger update strategy for leased line resources is determined to be: do not update the leased line resource ledger.

4. The method for automatically updating the dedicated line resource ledger according to claim 1, characterized in that, S4 includes: If the second detection result obtained by checking whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration is inconsistent, then the ledger update strategy for leased line resources is determined to be: update the leased line resource ledger according to the current configuration information of the logical port VLAN interface.

5. The method for automatically updating the dedicated line resource ledger according to claim 1, characterized in that, S4 includes: If the second detection result obtained by verifying whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration is consistent, then the ledger update strategy for leased line resources is determined to be: do not update the leased line resource ledger.

6. A device for automatically updating a dedicated line resource ledger, characterized in that, The device includes: The information acquisition module is configured to acquire log records and configuration information of the devices corresponding to the leased line resources. The first detection module is configured to detect whether there are up / down records of physical ports in the log records and obtain the first detection result; The second detection module is configured to determine a port configuration verification strategy based on the first detection result, and perform port configuration verification according to the verification strategy to obtain a second detection result. The ledger update module is configured to determine the ledger update strategy for dedicated line resources based on the second detection result; The verification strategy for determining the port configuration based on the first detection result includes: If the first detection result indicates the existence of up / down records, then the port configuration verification strategy is determined to be: verify whether the current configuration information of the device's physical port is consistent with the historical configuration; If the first detection result indicates that there are no up / down records, then the port configuration verification strategy is determined to be: verify whether the current configuration information of the logical port VLAN interface is consistent with the historical configuration.

7. A device for automatically updating a dedicated line resource ledger, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to implement the automatic update method for leased line resource ledgers as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the automatic update method for the leased line resource ledger as described in any one of claims 1-5.

Images