Network management and control

Abstract

Embodiments of the present disclosure provide a network management and control method and system, a computer program product, and a storage medium. A state data management layer may be arranged in a network management and control system, and a cache space is introduced into the state data management layer, to cache state data of each communication device in a communication network; the state data management layer can monitor a state change event in the communication network, and for the state change event, determine a communication device impacted in the communication network as a target communication device; and in this way, a state change of a single node in the communication network can be sensed in time, an impact scope is assessed, and state changes of other nodes in the impact scope are also brought into a focus field of view.

Description

[0001] Network control technology field

[0002]

[0001] The present disclosure relates to the field of cloud computing technology, and in particular to network management and control.

[0003] With the rapid increase in network bandwidth of cloud computing data centers, the scale of communication networks, as the physical foundation for data center interconnection, is also growing rapidly, and the operation and maintenance of communication networks is becoming increasingly complex. In the field of cloud computing, network management and control services for intelligent operation and maintenance of communication networks have been proposed. Network management and control services can comprehensively judge the network operating status based on the status data corresponding to each communication device in the communication network through various analysis methods, thereby achieving intelligent operation and maintenance. Therefore, the ability to provide accurate and fast real-time data is key to the operation and maintenance performance of network management and control services.

[0004]

[0003] Currently, in order to ensure speed, the accuracy of the status data obtained by the network management and control service is not sufficient, which leads to poor operation and maintenance performance of the network management and control service.

[0005]

[0004] Various aspects of the present disclosure provide a network management and control method, system, computer program product, and storage medium for improving the operation and maintenance performance of network management and control services.

[0006]

[0005] An embodiment of the present disclosure provides a network management and control method, which is suitable for a status data management layer set up in a network management and control system, wherein the status data management layer includes a cache space for caching status data for each communication device in the communication network. The method includes: in response to monitoring a status change event occurring in the communication network, determining the communication device affected by the status change event in the communication network as a target communication device; tracking the status data corresponding to each target communication device respectively; and updating the cache space according to the tracked status data.

[0007]

[0006] Further, determining the communication device affected by the state change event in the communication network includes: detecting a first communication device to which the state change event points; and determining the first communication device and each second communication device on the transmission path where the first communication device is located and located after the first communication device as the communication device affected by the state change event in the communication network.

[0008]

[0007] Furthermore, the state change event includes the occurrence of a configuration operation affecting the transmission state of any communication device, and / or the detection of a fluctuation in the state value of any state item in the state data of any communication device exceeding a preset standard.

[0008] Furthermore, tracking the state data corresponding to each target communication device includes: initiating a transmission state acquisition instruction to each target communication device to obtain the state data corresponding to each target communication device.

[0009]

[0009] Furthermore, the method also includes: if there is a communication device supporting network telemetry in the communication network, then after receiving the telemetry data pushed by the communication device supporting network telemetry, the cache space is updated according to the telemetry data; and / or, if a transmission status acquisition instruction is initiated to some communication devices in the communication network in response to a periodic task or manual trigger, then the cache space is updated according to the status data acquired by the transmission status acquisition instruction.

[0010]

[0010] Furthermore, the method further includes: constructing the status items contained in the tracked status data into data segments; and storing the data segments in a preset time series storage space; wherein the time series storage space stores data segments respectively constructed for the monitored state change events, and each data segment carries time information.

[0011]

[0011] Furthermore, the method further includes: if there is a communication device supporting network telemetry in the communication network, after receiving the telemetry data pushed by the communication device supporting network telemetry, the telemetry data is used as a data segment to be stored in the time series storage space.

[0012]

[0012] Furthermore, the method further includes: receiving a historical state backtracking instruction for the communication network, wherein the historical state backtracking instruction specifies a historical time node to be queried; searching for a target data segment for the historical state backtracking instruction from the time series storage space for restoring the transmission state for the historical time node; and fusing the found target data segments to restore the transmission state corresponding to the historical time node.

[0013]

[0013] Further, searching for a target data segment for restoring the transmission status for the historical status backtracking instruction includes: determining a time range including the historical time node; based on the time information carried by each data segment in the time series storage space, searching for a data segment within the time range as the target data segment; wherein the data segment within the time range can cover the status item required by the historical status backtracking instruction.

[0014]

[0014] Further, determining the time range including the historical time node includes: extending the time forward and backward with the time node as the starting point, and when a data segment is reached during the extension process, detecting the state items contained in the touched data segment, until the state items contained in the touched data segment can cover the data items required by the historical state backtracking instruction, ending the time extension to determine the time range; or, taking the historical event node as the origin, determining time boundary points forward and backward according to a preset time width; and using the two determined time boundary points as boundaries to determine the time range.

[0015]

[0015] Furthermore, the target data segments found are merged to restore the transmission status corresponding to the historical time node, including: deleting the status items in the target data segments that are not required by the transmission status query instruction; and deduplicating the remaining status items in the target data segments to obtain the status items required by the historical status backtracking instruction as the transmission status corresponding to the historical time node.

[0016]

[0016] Further, deduplication of the remaining status items in the target data segment includes: when the credibility of the data segment stored in the time series database does not meet the preset standard, if there are two target data segments located at two instances of the historical time node and both contain the target status item, then retaining the target status item in the target data segment closer to the historical time node; when the credibility of the data segment stored in the time series database exceeds the preset standard, if there are two target data segments located at two instances of the historical time node and both contain the target status item, then retaining the target status item in the target data segment located before the historical time node.

[0017]

[0017] Furthermore, the method further includes: if there are two target data segments located at the same historical time node and both contain the target state item, retaining the target state item in the target data segment closer to the historical time node.

[0018]

[0018] Furthermore, storing the data fragments in a preset time series storage space includes: storing the generated data fragments in the time series storage space in a data stream manner; monitoring the fluctuation of the state value under each state item during the storage according to the data stream; if it is monitored that the state value under any state item is in a stable state within a local time period, the state value under the state item can be semantically deduplicated within the local time period before being stored in the time series storage space.

[0019]

[0019] Furthermore, the method further includes: if alarm data pushed by a communication device in the communication network is received, the alarm data is stored as a data segment in the time series storage space; an alarm query instruction for the communication network is received, wherein the alarm query instruction specifies a historical time node to be queried; from the time series storage space, a target data segment for the alarm query instruction to restore the alarm data for the historical time node; and the target data segments found are merged to restore the alarm data corresponding to the historical time node.

[0020]

[0020] The embodiment of the present disclosure further provides a network management and control system, including a state data management layer, wherein the state data management layer includes a cache space for caching state data for each communication device in the communication network, and the state data manager is used to execute the aforementioned network management and control method.

[0021]

[0021] The embodiment of the present disclosure also provides a computer-readable storage medium storing a computer program, which, when executed by one or more processors, causes the one or more processors to execute the aforementioned network management and control method.

[0022]

[0022] The embodiment of the present disclosure also provides a computer program product, including a computer program, which, when executed by one or more processors, causes the one or more processors to execute the aforementioned network management and control method.

[0023]

[0023] In an embodiment of the present disclosure, it is proposed that a state data management layer can be set up in a network control system, and a cache space can be introduced in the state data management layer to cache the state data of each communication device in the communication network. On this basis, it is proposed that the state data management layer can monitor state change events in the communication network and determine the communication devices affected by the monitored state change events in the communication network as target communication devices. In this way, the state changes of a single point in the communication network can be perceived in a timely manner, and the impact surface can be evaluated, and the state changes of other points in the impact surface can also be included in the field of view of attention. Based on this, the state data management layer can actively track the state data corresponding to each target communication device based on the triggering of the state change event and trigger the update of the cache space. This enables the state data management layer to achieve accurate and fast real-time data provision capabilities, thereby improving the operation and maintenance performance of the network control service.

[0024] The accompanying drawings described herein are intended to provide a further understanding of the present disclosure and constitute a part of the present disclosure. The exemplary embodiments of the present disclosure and their descriptions are intended to explain the present disclosure and do not constitute an improper limitation of the present disclosure. In the accompanying drawings:

[0025]

[0025] FIG1 is a schematic diagram of the structure of a network management and control system provided by an exemplary embodiment of the present disclosure;

[0026]

[0026] FIG2 is a schematic diagram of other components of a network management and control system provided in an exemplary embodiment of the present disclosure;

[0027] FIG3 is a schematic diagram illustrating an exemplary principle for determining a target communication device according to an exemplary embodiment of the present disclosure;

[0028]

[0028] FIG4 is a schematic diagram showing a principle of a historical state backtracking capability in a network management and control system provided by an exemplary embodiment of the present disclosure;

[0029] FIG5 is a logic diagram of a historical state generator provided by an exemplary embodiment of the present disclosure;

[0030]

[0030] FIG6 is a flow chart of a network management and control method provided by an exemplary embodiment of the present disclosure.

[0031] To make the objectives, technical solutions, and advantages of the present disclosure more clearly apparent, the technical solutions of the present disclosure will be described clearly and completely below in conjunction with specific embodiments of the present disclosure and the corresponding drawings. Obviously, the described embodiments are only some of the embodiments of the present disclosure, and are not all of the embodiments. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present disclosure without inventive effort are within the scope of protection of the present disclosure.

[0032]

[0032] Before describing in detail the technical solutions provided by the various embodiments of the present disclosure, the technical background and current status of the present disclosure are explained as follows.

[0033] With the continuous development of cloud computing technology, the network bandwidth of cloud computing data centers has increased rapidly. As the physical foundation for data center interconnection, the scale of communication networks is also growing rapidly. Faced with increasingly complex network operations and maintenance, intelligent network management and control can significantly reduce operations and maintenance costs, improve efficiency, and minimize operational errors. Compared to traditional operations and maintenance methods, intelligent operations and maintenance require frequent acquisition of real-time topology, device status, and other data, using various analytical methods to comprehensively assess network operational status.

[0033]

[0034] As described in the background, the ability to provide accurate and fast real-time data is crucial for the operational performance of network control services. Accuracy allows network control services to focus on implementing their own logic without worrying about data defects or anomalies. Without guaranteed accuracy, complex data issues inherent in the data will be directly exposed to the network control service. This can lead to entanglement between data processing and various services, multiplying the implementation complexity of network control services and overwhelming developers with vulnerabilities caused by data issues. Speed ​​ensures that network control services can obtain required data with low latency, significantly accelerating execution.

[0034]

[0035] During their research, the inventors discovered that, to ensure the aforementioned "speed," network control services can currently relax their real-time requirements for status data and simply store the status data obtained through interactions with communication devices. In this case, the network control service can directly access the status data as long as it falls within a relatively broad timeframe, without being able to assess whether the data has expired (i.e., is no longer up-to-date). This results in inaccurate status data obtained by the network control service, leading to poor operational performance. The network control service is unable to handle tasks triggered by short cycles or tasks requiring high real-time performance, and can only handle tasks that are less time-sensitive.

[0035]

[0036] To this end, this embodiment proposes a network management and control method to improve the operation and maintenance performance of the network management and control service by improving the accuracy and efficiency of status data provided for the network management and control service.

[0036]

[0037] The following describes in detail the technical solutions provided by various embodiments of the present disclosure in conjunction with the accompanying drawings.

[0037]

[0038] FIG1 is a schematic diagram of the structure of a network management and control system provided by an exemplary embodiment of the present disclosure. Referring to FIG1 , the network management and control system may be provided with a state data management layer, and a cache space may be introduced into the state data management layer.

[0038]

[0039] In this embodiment, it is proposed that the status data of each communication device in the communication network can be cached in the cache space.

[0039]

[0040] This embodiment does not limit the type of communication network or the type of communication equipment within the communication network. For example, the communication network in this embodiment may be an optical transmission network or a laser communication network, and further examples are not provided here. Accordingly, the communication equipment in this embodiment may be optical transmission equipment, and further examples are not provided here. The aforementioned optical transmission network, also known as an Optical Transport Network (OTN), is a type of network, a communication network based on optical fiber technology. It uses optical fiber as a transmission medium, transmitting information in the form of light. The aforementioned optical transmission equipment can be understood as equipment that converts various signals into optical signals for transmission over optical fibers. Common optical transmission equipment includes optical terminals, optical transceivers, optical switches, Plesiochronous Digital Hierarchy (PDH) equipment, Synchronous Digital Hierarchy (SDH) equipment, Packet Transport Network (PTN), and optical amplifiers, and further examples are not provided here. Further explanation of other types of communication networks and equipment applicable to this embodiment is not provided here.

[0040]

[0041] The status data in this embodiment may be various descriptive data used to reflect the transmission status of a communication device. In this embodiment, the status items included in the status data can be set based on the analysis requirements of the network management and control system during operation and maintenance. Specifically, in actual applications, the network management and control system can use the status items required for operation and maintenance as cache objects supported by the cache space in this embodiment. This allows the cache space to adapt to the analysis requirements of the network management and control service.

[0041]

[0042] Figure 2 is a schematic diagram of other components of a network management and control system provided in an exemplary embodiment of the present disclosure. Referring to Figure 2, the network management and control system in this embodiment may include a service interface for implementing service-oriented services. Based on this service interface, the network management and control system provided in this embodiment can be implemented as the aforementioned network management and control service. By invoking this service interface, the network management and control system provided in this embodiment can be triggered to execute various processing tasks.

[0042]

[0043] Referring to Figure 2 , the network management and control system in this embodiment may also include an automated service layer consisting of a series of automated network operations. This layer encapsulates predefined standard operating procedures for daily operations and maintenance, such as product launch, performance tuning, health checks, fault handling, and alarm resolution. The intelligent service layer shown in Figure 2 is a further upgrade of the automated service layer, further replacing manual operations and maintenance. By introducing artificial intelligence algorithms and other means, this layer can perform advanced operations at the level of operations and maintenance experts. For example, during health checks, the intelligent service layer can detect previously undefined abnormal device states through abnormal pattern recognition algorithms. Of course, the two service layers and their functions described here are exemplary and this embodiment is not limited to these.

[0043]

[0044] Here, based on Figure 2 , we would like to further illustrate that the cache space introduced in this embodiment can be used to provide status data to the various service layers shown in Figure 2 , supporting data analysis by these service layers. During research, the inventors discovered that the data return latency of the cache space can be reduced to milliseconds. Therefore, the cache space introduced in this embodiment can effectively ensure the rapid real-time data provision capability required by the aforementioned network management and control services.

[0044]

[0045] 1 , on this basis, this embodiment further introduces a state data management layer to improve the accuracy of the state data cached in the cache space through the state data management layer.

[0045]

[0046] This embodiment proposes that the state data management layer can be used to monitor state change events occurring in a communication network. A state change event can be understood as an event that directly or indirectly indicates a change in the transmission state of the communication network. This embodiment does not limit the type of state change event. State change events in this embodiment may include, but are not limited to, the occurrence of a configuration operation affecting the transmission state of any communication device, the detection of a fluctuation in the state value of any status item in the status data of any communication device exceeding a preset standard, and the like. Configuration operations performed on communication devices typically rely on a network management and control system to be implemented on the corresponding communication devices. Therefore, the state data management layer in this embodiment can seamlessly detect these configuration operations. The configuration operations that affect the transmission state can be preset based on experience. The state data management layer in this embodiment can monitor these preset configuration operations and thus promptly detect them. As mentioned above, the cache space introduced in this embodiment caches state data for communication devices. Therefore, the state data management layer in this embodiment can seamlessly detect whether any state item of a communication device fluctuates beyond a preset standard. In actual applications, after actively or passively acquiring the status data of a communication device, the status data management layer may compare the new status data with the status data cached for the communication device. If there is a significant difference, it may be determined that a status change event has been detected.

[0046]

[0047] Here, further examples of state change events are not provided. It should be understood that various events that can directly or indirectly indicate that a transmission state change has occurred in the communication network can be used as state change events supported by this embodiment. More comprehensive state change events can better ensure that the state data management layer can timely and comprehensively detect transmission state changes occurring in the communication network.

[0047]

[0048] During their research, the inventors discovered that state change events are typically single-point, specifically directed to a communication device in a communication network. This embodiment proposes assessing the impact surface based on monitored state change events at a single point, and also taking other points within the impact surface into account. The impact surface can be understood as the network range potentially affected by a single point experiencing a transmission state change in the communication network. During their research, the inventors discovered that the transmission states of communication devices in a communication network may be linked or dependent on each other. Therefore, a change in the transmission state at one point may cause simultaneous changes in the transmission states at other points, or the configurations at multiple points may often change simultaneously, leading to simultaneous changes in the transmission states of those points.

[0048]

[0049] Based on this, in this embodiment, the state data management layer can, in response to detecting a state change event in the communication network, identify the communication devices affected by the state change event in the communication network as target communication devices. It can be seen that in this embodiment, based on the mutual influence patterns between communication devices regarding transmission status, the impact surface corresponding to the state change event can be seamlessly determined. As a result, the single point targeted by the state change event, as well as other points determined by evaluating the impact surface, are all included in the scope of attention of this embodiment. These points included in the scope of attention of this embodiment can all serve as the aforementioned target communication devices.

[0049]

[0050] In one optional implementation, the state data management layer may detect the first communication device targeted by the state change event and identify the first communication device, as well as each second communication device located after the first communication device on the transmission path of the first communication device, as the communication devices affected by the state change event in the communication network. Specifically, in this optional implementation, the entire transmission path, from the communication device where the transmission state change occurred to the communication device at the end of the transmission path, is included in the scope of attention of this embodiment.

[0050]

[0051] Figure 3 is a schematic diagram illustrating an exemplary principle for determining a target communication device, according to an exemplary embodiment of the present disclosure. Referring to Figure 3 , A1-A8 represent different amplifiers. The optical line protector in the figure includes a light receiving element and a light emitting element. The light receiving element is connected to two optical paths, each of which has multiple amplifiers. It should be understood that when network transmission is required, optical signals are injected into both optical paths (the primary path and the backup path) connected to the light receiving element of the optical line protector in Figure 3 . However, the optical line protector selects one of the optical paths to communicate with the light emitting element. Referring to Figure 3 , the optical line protector selects the primary path to communicate with the light emitting element. Therefore, two transmission paths will appear in this network transmission: the first path is A1-A2-A3 - optical line protector - A4-A5; the second path is A6-A7-A8. Based on the state data manager provided in this embodiment, upon detecting a state change event directed to amplifier A2, the manager not only adds A2 to the scope of attention in this embodiment but also determines that A3 - optical line protector - A4 - A5 in the transmission path in which A2 resides (i.e., the first transmission path mentioned above in FIG. 3 ) may have also experienced a transmission state change synchronously with A2. Therefore, A3 - optical line protector - A4 - A5 in this transmission path are also included in the scope of attention in this embodiment. Similarly, based on the state data manager provided in this embodiment, upon detecting a state change event directed to amplifier A6, the manager not only adds A6 to the scope of attention in this embodiment but also adds A7 - A8 in the transmission path in which A6 resides.

[0051]

[0052] In this way, in this embodiment, after a state change event is detected, communication devices in the communication network that may have a transmission state change can be estimated, and these communication devices can be included in the field of view of attention in this embodiment. This allows the state data management layer in this embodiment to obtain a more comprehensive field of view of attention, rather than being limited to communication devices that have clearly changed.

[0052]

[0053] Afterwards, the status data management layer can track the status data corresponding to each target communication device. It's worth noting that the status data cached for the communication devices in the cache space is obtained based on the interaction between the status data management layer and the communication devices in this embodiment. Tracking here can be understood as the status data management layer proactively requesting the latest status data from each target communication device. To this end, the status data management layer can initiate a transmission status acquisition instruction to each target communication device to obtain the status data corresponding to each target communication device. Referring to Figure 2, in actual applications, the status data management layer can agree on a communication protocol with each communication device in the communication network. The device driver layer includes several communication protocols to support interaction between the two parties. The status data management layer can trigger the corresponding communication device to return status data by initiating a transmission status acquisition instruction according to the agreed communication protocol. The communication protocols agreed upon between the two parties may include, but are not limited to, NETCONF, RESTCONF, SNMP, gNMI, and other protocols, which are not limited here. Furthermore, the status data tracked here can be the full status data of each target communication device. Alternatively, required status items can be indicated, and only the latest status values ​​corresponding to these indicated status items can be tracked from the target communication device as the status data. Furthermore, the status items tracked for different target communication devices can also be different. In actual applications, this can be set as needed, and the status items in the status data tracked here are not limited.

[0053]

[0054] Referring to Figure 1 , after tracking state data, the state data cached for each target communication device in the cache space can be updated. Thus, in this embodiment, detecting a state change event triggers the state data management layer to promptly identify communication devices in the communication network whose transmission states may have changed, proactively track the state data of these communication devices, and update the cache. This proactive tracking mechanism, which extends from a single point to a larger area, enables more timely and comprehensive cache updates, effectively improving the accuracy of the state data cached for communication devices in the cache space.

[0054]

[0055] In practical applications, referring to Figure 2 , in this embodiment, a state tracker can be deployed in the state data management layer to perform the aforementioned operations in the data management layer, such as, in response to monitoring a state change event in the communication network, identifying the communication devices affected by the state change event as target communication devices; tracking the state data corresponding to each target communication device; and updating the cached state data for each target communication device based on the tracked state data. This enables the state data management layer to provide accurate and rapid real-time data based on cache space, thereby ensuring the operational performance of the network management and control system.

[0055]

[0056] In summary, this embodiment proposes setting up a state data management layer within the network management and control system and introducing cache space within the state data management layer to cache state data for each communication device in the communication network. Furthermore, it proposes that the state data management layer monitor state change events in the communication network and identify the communication devices affected by the detected state change events as target communication devices. This allows for timely detection of state changes at a single point in the communication network, assessment of the impact area, and consideration of state changes at other points within the impact area. Based on this, the state data management layer can proactively track the state data corresponding to each target communication device and trigger updates to the cache space. This enables the state data management layer to provide accurate and rapid real-time data, thereby improving the operational performance of network management and control services.

[0056]

[0057] In the above or below embodiments, in addition to performing cache updates on cache space based on the point-to-surface active tracking mechanism provided by the aforementioned state data management layer, the state data management layer can also support more trigger dimensions to execute cache updates. Several exemplary trigger dimensions are provided below.

[0057]

[0058] 2 , an exemplary trigger dimension may be: if there is a communication device supporting network telemetry in the communication network, then after receiving telemetry data pushed by the communication device supporting network telemetry, the status data cached for the communication device is updated according to the telemetry data.

[0058]

[0059] Network telemetry is a new generation of network monitoring technology that remotely and quickly collects data from communication devices. Using this technology, communication devices can periodically push their collected information to a collector. The status data management layer in this embodiment can serve as a collector in network telemetry technology. Therefore, if there are communication devices in the communication network that support network telemetry, these devices can proactively push status data to the status data management layer in this embodiment.

[0059]

[0060] For such communication devices, the state data management layer in this embodiment can maintain a cache update frequency of seconds. Therefore, the accuracy of the state data of such communication devices within the cache space can be effectively guaranteed. Based on this, in practical applications, state items on such communication devices that support network telemetry generally do not need to be included in the aforementioned point-to-surface active tracking mechanism. In other words, the state data management layer does not need to actively track such communication devices. Of course, this embodiment does not limit this; including such communication devices in the aforementioned point-to-surface active tracking mechanism does not affect the implementation of this embodiment's point-to-surface active tracking mechanism.

[0060]

[0061] Referring to Figure 2, another exemplary triggering dimension may be: if a transmission status acquisition instruction is initiated to some communication devices in the communication network in response to a periodic task or manual trigger, the status data cached for the corresponding communication device is updated according to the status data obtained by the transmission status acquisition instruction.

[0061]

[0062] In this exemplary triggering dimension, the state data manager may actively track the state data of the specified communication device and perform cache updates under periodic tasks or manual triggering.

[0062]

[0063] Echoing the aforementioned type of state change event—detection of a fluctuation in the state value of any status item in the state data of any communication device exceeding a preset standard—the active tracking operation performed under this exemplary trigger dimension may result in the occurrence of this type of state change event. For example, under this exemplary trigger dimension, the state data management layer initiates active tracking of the state data of communication device A. After tracking the latest state data of communication device A, the state data management layer discovers that the latest state value corresponding to state item a differs significantly from the state value in the cache space. Therefore, the state change event is detected on communication device A, thereby triggering the aforementioned point-to-surface active tracking mechanism.

[0063]

[0064] It is worth noting that the state data management layer in this embodiment can also support more trigger dimensions, and is not limited to the aforementioned exemplary trigger dimensions. Furthermore, the various exemplary trigger dimensions do not conflict with the point-to-surface active tracking mechanism proposed in this embodiment. Cache update operations caused by different trigger dimensions typically have a sequential order. In practical applications, the most recent update operation in the cache space is sufficient, regardless of the trigger dimension that triggered the update operation.

[0065] In summary, in this embodiment, the state data management layer can effectively improve the accuracy of the state data cached in the cache space through the mutual cooperation and mutual complementation between multiple trigger dimensions.

[0064]

[0066] In the above and following embodiments, in addition to ensuring the network control system's "accurate and rapid real-time data provision capability" based on the aforementioned cache space and state data management layer, a new data provision capability is introduced for the network control system: historical state backtracking capability. The aforementioned "accurate and rapid real-time data provision capability" can be understood as supporting the aforementioned service layers to query the real-time transmission status of the communication network. The historical state backtracking capability can be understood as supporting the aforementioned service layers to query the transmission status of the communication network at a specific historical time point.

[0065]

[0067] Figure 4 is a schematic diagram illustrating the principles of historical state traceability in a network management and control system, according to an exemplary embodiment of the present disclosure. Referring to Figure 4 , this embodiment proposes that, after tracking the state data of each target communication device, the state data management layer constructs the state items contained in the tracked state data into data segments and stores the data segments in a preset time-series storage space.

[0066]

[0068] The time series storage space can employ a time series database or a storage medium with the same capabilities as a time series database, which is not limited in this embodiment. Furthermore, each constructed data segment carries time information, and the time series storage space ensures that this time information is not lost and supports using this time information as a retrieval basis. The time information carried by the data segment can be the time node of a state change event, the time node when tracking of the corresponding state data is initiated, or the time node when the data segment is completed. During research, the inventors discovered that the errors between these time nodes are very small and do not affect the historical state backtracking capability of this embodiment. Therefore, in practical applications, the time information carried by the data segment can be any of the above time nodes.

[0067]

[0069] In addition to the time information carried by the data segments, in this embodiment, each status item contained in the data segments also carries time information. The time information carried by the status item can use the collection time node of the carried status value to indicate when the status item was collected.

[0068]

[0070] Thus, in this embodiment, as state change events continuously occur in the communication network, the state data manager can construct data segments for each monitored state change event and store them in the time series storage space. This ensures that the time series storage space stores data segments corresponding to different state change events.

[0069]

[0071] Following the aforementioned embodiment, the state data manager may support cache updates based on multiple trigger dimensions, particularly communication devices supporting network telemetry in a communication network. Here, for such communication devices, the received telemetry data can also be constructed into data segments. In practical applications, telemetry data pushed once by a single communication device supporting network telemetry can be constructed into a single data segment. The time information in such a data segment can be the time node of data collection, for example. The data segments constructed through this channel will also be stored in the time series storage space, further enriching the data segments in the time series storage space.

[0070]

[0072] Furthermore, referring to FIG4 , in this embodiment, the state data management layer (specifically, the state tracker within the state data management layer) can use a data stream to store the constructed data segments into the time series storage space. Referring to FIG4 , the state data management layer can also include a codec. The codec can compress the data segments during data stream storage, significantly saving time series storage space. In this embodiment, the compression method used by the codec is not limited. For example, the data segments can be compressed into binary data according to preset rules. This will not be discussed in detail here. Any compression method that can save storage space and accurately restore the data segments without losing information is applicable to this embodiment.

[0071]

[0073] A further optimization proposal proposes that during data stream storage, the state data management layer can utilize a codec to monitor fluctuations in the state values ​​of each state item. If it is detected that the state value of any state item is stable within a local time period, semantic deduplication can be performed on the state values ​​within that local time period before storage in the time series storage space. This optimization proposal does not limit the specific implementation of semantic deduplication. In one exemplary implementation, data segments may not store actual state values, but instead record references to the state values. For example, if 100 data segments all contain the same state item, and the state value of the state item in two data segments is the same, the later data segment can simply inherit the reference recorded for the state item in the earlier data segment. The reference can point to a previous data segment containing the state value of the state item. Based on this, in this exemplary implementation, if the codec detects that the fluctuation level of the status item within a period of time (i.e., the aforementioned local time period) is below a threshold, the codec can determine that the status item is stable within that local time period. Taking an amplifier as an example, the threshold corresponding to the input power status item can be set to ±0.2dBm. Based on this, if the amplifier's input power fluctuates within this range, the amplifier can be determined to be stable. In this case, the content used to record the status item's status value in the 100 data segments can be replaced with a single piece of time data [start time, end time]. Obviously, the storage space required for this time data will be much smaller than the storage space required for the original reference relationship, thus effectively saving time series storage space.

[0072]

[0074] In this embodiment, the state data management layer can also utilize the aforementioned codec to perform multi-dimensional processing on the data segments constructed by the state tracker. This embodiment is not limited to this, and further examples are not provided here. Furthermore, the codec can perform processing on the data segments in different dimensions in sequence, thus preventing any conflicts. This effectively reduces the amount of time series storage space occupied.

[0073]

[0075] It is understandable that the individual data fragments constructed in this embodiment carry incomplete state data of the communication network. However, this incomplete state data possesses a temporal attribute. Therefore, the large number of data fragments stored in the time series storage space can serve as the data foundation for historical state backtracking. In other words, this embodiment proposes that the state data management layer supports historical state backtracking based on the large number of data fragments stored in the time series storage space. This is because, although the individual data fragments carry incomplete state data of the communication network, the temporal attribute of the data fragments allows the complete state data required for query to be seamlessly restored by merging the data fragments.

[0074]

[76] To this end, referring to FIG4 , this embodiment proposes that a historical state generator can be provided in the state data management layer. Based on this, in this embodiment, the state data management layer can utilize the historical state generator to receive a historical state backtracking instruction for the communication network, wherein the historical state backtracking instruction specifies a historical time node to be queried; search the target data segment for the historical state backtracking instruction from the time series storage space for restoring the transmission state for the historical time node; and merge the found target data segments to restore the transmission state corresponding to the historical time node.

[0075]

[77] It is worth noting that, in actual applications, if the data segments are processed by the aforementioned codec and then stored in the time series storage space, then here, the codec needs to restore the target data segments provided by the time series storage space to their original appearance so that the historical state generator can perform the fusion operation.

[0076]

[78] In this embodiment, various implementations may be used to determine the target data segments required for the historical state backtracking instruction. FIG5 is a logic diagram of a historical state generator provided in an exemplary embodiment of the present disclosure. Referring to FIG5 , an exemplary implementation is provided below.

[0077]

[79] Determine a time range that includes historical time nodes; based on the time information carried by each data fragment in the time series storage space, search for a data fragment within the time range as the target data fragment; wherein the data fragment within the time range can cover the state items required by the historical state backtracking instruction. In practical applications, the historical state backtracking instruction may include range description information for indicating the required state items. For example, the range description information may be an identifier of a communication device, so that each state item in the indicated communication device is the state item required by the historical state backtracking instruction. For another example, the range description information may be an identifier of one or more state items, so that the state item in each communication device in the communication network is the state item required by the historical state backtracking instruction, and the same state item in different communication devices should be understood as different state items required by the historical state backtracking instruction. No further examples are given here.

[0078]

[80] The upper part of FIG5 shows the temporal relationship between some data segments in the temporal storage space. In addition, the status items contained in different data segments may be different. Therefore, the upper part of FIG5 also shows the distribution status of the status items in different data segments through the upper and lower distribution positions. Referring to FIG5, t2 is the historical time node indicated by the historical state backtracking instruction. And [t1, t2] is the determined time range including t2.

[0081] Here, the essence carried by the data segments in this embodiment can be understood as: the incomplete transmission status in the communication network that can be queried at a certain time node. The data segments that just fall on the aforementioned historical time node may be one or more, or may not exist at all. Moreover, the data segments that just fall on the aforementioned historical time node usually cannot contain all the status items required for the query. Referring to FIG5, there is only one data segment P5 that falls on t2, and the status items contained in P5 are obviously not comprehensive. Therefore, in order to restore the complete transmission status that should be queried at the historical time node, a time range is proposed in this exemplary implementation, so that the status data tracked before and after the historical time node can be used to restore the transmission status.

[0079]

[0082] Here, several exemplary time range determination schemes are provided.

[0080]

[0083] One determination scheme may be: starting from a time node, time is extended forward and backward. When a data segment is reached during the extension process, the state items contained in the data segment reached are detected until the state items contained in the data segment reached can cover the data items required by the historical state backtracking instruction. The time extension is ended to determine the time range.

[0081]

[0084] Another determination scheme may be: taking the historical event node as the origin, determining time boundary points forward and backward according to a preset time width; and using the two determined time boundary points as boundaries to determine the time range.

[0082]

[0085] It should be understood that the above-mentioned determination schemes are merely exemplary and this embodiment is not limited thereto. It is sufficient to ensure that the data segments determined within the time range are sufficient to cover the state items required by the historical state backtracking instruction. No further examples are given here.

[0083]

[0086] In addition, in this embodiment, in addition to the aforementioned time range-based implementation method, other implementation methods can also be used to filter out target data segments for the historical state backtracking instruction, as long as the filtered target data segments are sufficient to cover the state items required by the historical state backtracking instruction. No further examples are given here.

[0084] During research, the inventors discovered that the target data segments selected for the historical state backtracking instruction may contain status items not required by the historical state backtracking instruction, and may also contain duplicate status items. In response to this, the present embodiment proposes that the state data management layer utilize a historical state generator to delete status items in the target data segments that are not required by the transmission state query instruction, and further deduplicate the remaining status items in the target data segments to obtain the status items required by the historical state backtracking instruction as the transmission state corresponding to the historical time node.

[0085]

[0088] The inventors also discovered during the research process that, in the above-mentioned deduplication process, correctly determining which state item in the target data segment to retain can effectively improve the accuracy of the restored transmission state.

[0086]

[0089] To this end, in this embodiment, with respect to the aforementioned deduplication link, it is proposed that: when the credibility of the data segments stored in the time series database does not reach the preset standard, if there are two target data segments located at two instances of the historical time nodes and both contain the target state item, then the target state item in the target data segment closer to the historical time node is retained; when the credibility of the data segments stored in the time series database exceeds the preset standard, if there are two target data segments located at two instances of the historical time nodes and both contain the target state item, then the target state item in the target data segment located before the historical time node is retained.

[0087]

[0090] The credibility of the data segments stored in the time series database can be used to measure the accuracy of the data segments in describing the transmission state of the communication network. The credibility here is affected by multiple factors, such as the aforementioned state tracker's ability to monitor state change events and its ability to assess the impact of state change events. In this embodiment, an independent evaluation mechanism can be used to evaluate the credibility of the data segments stored in the time series database. The evaluation mechanism is neither limited nor exemplified herein.

[0088]

[0091] The lower half of FIG. 5 illustrates the data segment fusion process, which includes the aforementioned deduplication step. Referring to FIG. 5 , target data segments P6 and P3 have duplicate target state items. However, the credibility of the data segments stored in the time series database does not meet the preset standard. Therefore, in FIG. 5 , since P6 is closer to the indicated historical time node t2, the target state item in P6 is retained, while the target state item in P3 is deleted. Referring to FIG. 5 , target data segments P5 and P6 also have duplicate target state items. Similarly, since P5 is closer to the historical time node t2, the target state item in P5 is retained, while the target state item in P6 is deleted.

[0089] Regardless of whether the credibility of the data segments stored in the time series database meets the preset standard, this embodiment further proposes, with respect to the aforementioned deduplication process, that if two target data segments are located at the same historical time node and both contain a target state item, the target state item in the target data segment closer to the historical time node is retained. This is because the target state item in the target data segment closer to the historical time node is generally closer to the actual transmission state at the historical time node.

[0090]

[0093] In this way, the correctness of the state items retained in the aforementioned deduplication link can be effectively improved, thereby improving the accuracy of the transmission state fused for the historical time node.

[0091]

[0094] In summary, in this embodiment, based on the time series storage space introduced for the state data management layer, the state data management layer can store state data that is actively sent or received through network telemetry as data segments in the time series storage space, while preserving the time attributes of the data segments. On this basis, the state data management layer can provide historical state backtracking capabilities based on the large number of data segments with time attributes stored in the time series storage space, thereby supporting various service layers in the network management and control system to initiate historical state backtracking instructions. The state data management layer can use the historical state generator it contains to reasonably filter target data segments from the time series storage space, and by fusing these target data segments, it can restore the transmission state corresponding to the indicated historical time point for the communication network.

[0095] In the above or following embodiments, the inventors also discovered that communication devices in the communication network typically push alarm data to the network management and control system, and this alarm data can also be an important basis for the network management and control system to perform intelligent operation and maintenance. In this regard, this embodiment proposes: if alarm data pushed by a transmission device in a communication network is received, the alarm data is stored as a data segment in a time series storage space; an alarm query instruction for the communication network may also be received, where the alarm query instruction specifies a historical time node to be queried; a target data segment for restoring the alarm data for the historical time node is searched from the time series storage space for the alarm query instruction; and the found target data segments are merged to restore the alarm data corresponding to the historical time node.

[0092]

[0096] Referring to FIG. 4 , in actual applications, the state data management layer (specifically, the state tracker) in the network control system may be responsible for storing the alarm data in the time series storage space. Of course, a system unit originally used for alarm data management in the network control system may also be responsible for this, and this is not limited here. In addition, the state data management layer (specifically, the historical state generator) in the network control system may be responsible for responding to the alarm query instruction, and of course, this embodiment does not limit this.

[0093]

[0097] In addition, it should be understood that alarm data and transmission status have similar data attributes. For example, alarm data also includes multiple alarm items. Alarm data corresponding to a certain historical time node should also include multiple alarm items. Different data segments may also contain duplicate alarm items. Therefore, regarding the process of storing data segments, the process of searching for target data segments, and the process of merging target data segments, the technical details described in the "Historical Status Backtracking Capability" section of the aforementioned embodiment can all be referred to, and will not be repeated here.

[0094]

[0098] In order to avoid confusion between the data segments corresponding to the alarm data and the data segments corresponding to the status data, in this embodiment, different type tags may be added to the two types of data segments to distinguish the two types of data segments, thereby avoiding screening of unnecessary target data segments during the instruction response process.

[0095]

[0099] In summary, in this embodiment, the network management and control system also supports the storage of historical alarm data, thereby supporting on-demand query of historical alarm data, and furthermore can more accurately restore the alarm data corresponding to the historical time node.

[0096] FIG6 is a flow chart illustrating a network management and control method provided by an exemplary embodiment of the present disclosure. This method may be executed by a status data management layer provided in a network management and control system. The status data management layer may be implemented as an independent server or a server cluster. A cache space is also introduced in the status data management layer, which can be used to cache status data of each communication device in the communication network. Based on this, with reference to FIG1 , the method may include the following steps.

[0097]

[0101] Step 600: In response to monitoring a state change event in a communication network, a communication device affected by the state change event in the communication network is determined as a target communication device.

[0098]

[0102] Step 601: Track the status data corresponding to each target communication device.

[0103] Step 602: Update the cache space according to the tracked status data.

[0099]

[0104] In an optional embodiment, step 600 may include: detecting a first communication device to which the state change event points; and determining the first communication device and each second communication device located on the transmission path where the first communication device is located and after the first communication device as the communication devices affected by the state change event in the communication network.

[0100]

[0105] In an optional embodiment, the state change event includes a configuration operation affecting the transmission state of any communication device, and / or detecting that the fluctuation degree of the state value of any state item in the state data of any communication device exceeds a preset standard.

[0101]

[0106] In an optional embodiment, step 601 may include: initiating a transmission status acquisition instruction to each target communication device respectively to acquire status data corresponding to each target communication device.

[0102]

[0107] In an optional embodiment, the method may further include: if there is a communication device supporting network telemetry in the communication network, then after receiving the telemetry data pushed by the communication device supporting network telemetry, updating the cache space according to the telemetry data; and / or, if a transmission status acquisition instruction is initiated to some communication devices in the communication network in response to a periodic task or manual trigger, then updating the cache space according to the status data acquired by the transmission status acquisition instruction.

[0103]

[0108] In an optional embodiment, the method may further include: constructing the status items contained in the tracked status data into data segments; storing the data segments in a preset time series storage space; wherein the time series storage space stores data segments constructed respectively for the monitored status change events, and each data segment carries time information.

[0104]

[0109] In an optional embodiment, the method may further include: if there is a communication device supporting network telemetry in the communication network, after receiving the telemetry data pushed by the communication device supporting network telemetry, storing the telemetry data as a data segment in the time series storage space.

[0105]

[0110] In an optional embodiment, the method may also include: receiving a historical state backtracking instruction for the communication network, wherein the historical state backtracking instruction specifies a historical time node to be queried; searching for a target data segment for the historical state backtracking instruction from the time series storage space to restore the transmission state for the historical time node; and fusing the found target data segments to restore the transmission state corresponding to the historical time node.

[0106]

[0111] In an optional embodiment, the step of searching for a target data segment for restoring the transmission status for the historical time node by the historical state backtracking instruction may include: determining a time range including the historical time node; searching for a data segment located in the time range as the target data segment based on the time information carried by each data segment in the time series storage space; wherein the data segment within the time range can cover the status item required by the historical state backtracking instruction.

[0107]

[0112] In an optional embodiment, the step of determining the time range including the historical time node may include: extending the time forward and backward with the time node as the starting point, and when a data segment is reached during the extension process, detecting the state items contained in the reached data segment until the state items contained in the reached data segment can cover the data items required by the historical state backtracking instruction, and ending the time extension to determine the time range; or, taking the historical event node as the origin, determining time boundary points forward and backward according to a preset time width; and using the two determined time boundary points as boundaries to determine the time range.

[0108]

[0113] In an optional embodiment, the step of merging the target data segments found to restore the transmission status corresponding to the historical time node may include: deleting the status items in the target data segments that do not belong to the status items required by the transmission status query instruction; and deduplicating the remaining status items in the target data segments to obtain the status items required by the historical status backtracking instruction as the transmission status corresponding to the historical time node.

[0109]

[0114] In an optional embodiment, the step of deduplicating the remaining status items in the target data segment may include: when the credibility of the data segment stored in the time series database does not meet the preset standard, if there are two target data segments located at two instances of the historical time node and both contain the target status item, then retain the target status item in the target data segment closer to the historical time node; when the credibility of the data segment stored in the time series database exceeds the preset standard, if there are two target data segments located at two instances of the historical time node and both contain the target status item, then retain the target status item in the target data segment located before the historical time node.

[0110]

[0115] In an optional embodiment, the method may further include: if there are two target data segments located at the same instance of the historical time node and both contain target status items, then retaining the target status item in the target data segment closer to the historical time node.

[0111]

[0116] In an optional embodiment, the step of storing the data fragments into a preset time series storage space may include: storing the generated data fragments into the time series storage space in a data stream manner; monitoring the fluctuation of the state value under each state item during the storage according to the data stream; if it is detected that the state value under any state item is in a stable state within a local time period, the state value under the state item can be semantically deduplicated within the local time period before being stored in the time series storage space.

[0112]

[0117] In an optional embodiment, the method may further include: if alarm data pushed by a communication device in the communication network is received, storing the alarm data as a data segment in the time series storage space; receiving an alarm query instruction for the communication network, wherein the alarm query instruction specifies a historical time node to be queried; searching for a target data segment for the alarm query instruction in the time series storage space for restoring the alarm data for the historical time node; and fusing the found target data segments to restore the alarm data corresponding to the historical time node.

[0113]

[0118] It should be noted that some of the processes described in the above embodiments and the accompanying drawings include multiple operations that appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order in which they appear herein or may be executed in parallel. Operation sequence numbers, such as 601 and 602, are merely used to distinguish between different operations and do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the terms "first" and "second" herein are used to distinguish between different communication devices, etc., and do not represent a sequential order, nor do they limit the "first" and "second" to different types.

[0114]

[0119] Accordingly, an embodiment of the present disclosure further provides a computer-readable storage medium storing a computer program, which can implement the steps in the above method embodiment when the computer program is executed.

[0115]

[0120] Accordingly, the embodiment of the present disclosure also provides a computer program product, which can implement the steps in the above method embodiment when the computer program contained therein is executed.

[0116]

[0121] Those skilled in the art will appreciate that embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0117] The present disclosure is described with reference to the flow chart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one or more flow processes of the flow chart and / or one or more boxes of the block diagram.

[0118]

[0123] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0119]

[0124] These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operating steps are performed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0120]

[0125] It should also be noted that the terms "comprise," "include," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a..." does not preclude the presence of other identical elements in the process, method, commodity, or apparatus comprising the element.

[0121]

[0126] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0122] The above description is merely an embodiment of the present disclosure and is not intended to limit the present disclosure. It will be apparent to those skilled in the art that various modifications and variations may be made to the present disclosure. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present disclosure shall be included within the scope of protection of the present disclosure.

Claims

Claims 1. A network management and control method, adapted for a status data management layer provided in a network management and control system, wherein the status data management layer includes a cache space for caching status data for each communication device in the communication network, the method comprising: In response to monitoring a state change event occurring in the communication network, determining a communication device affected by the state change event in the communication network as a target communication device; Tracking status data corresponding to each target communication device respectively; and updating the cache space according to the tracked status data.

2. The method according to claim 1, wherein: Determining the communication devices affected by the state change event in the communication network includes: detecting a first communication device to which the state change event points; and determining the first communication device and each second communication device that is on the transmission path where the first communication device is located and is located after the first communication device as the communication devices affected by the state change event in the communication network.

3. The method according to claim 1, wherein: The state change event includes a configuration operation affecting the transmission state of any communication device, and / or detection that a state value fluctuation degree of any state item in the state data of any communication device exceeds a preset standard.

4. The method according to claim 1, wherein: Tracking status data corresponding to each target communication device separately includes: initiating a transmission status acquisition instruction to each target communication device separately to acquire status data corresponding to each target communication device.

5. The method according to any one of claims 1 or 4, further comprising: If there is a communication device supporting network telemetry in the communication network, then after receiving the telemetry data pushed by the communication device supporting network telemetry, the cache space is updated according to the telemetry data; and / or, if a transmission status acquisition instruction is initiated to some communication devices in the communication network in response to a periodic task or manual trigger, the cache space is updated according to the status data acquired by the transmission status acquisition instruction.

6. The method according to claim 1, further comprising: constructing the state items contained in the tracked state data into data segments; and storing the data segments in a preset time series storage space; The time series storage space stores data segments respectively constructed for monitored state change events, and each data segment carries time information.

7. The method according to claim 6, further comprising: If there is a communication device supporting network telemetry in the communication network, after receiving the telemetry data pushed by the communication device supporting network telemetry, the telemetry data is used as a data segment to be stored in the time series storage space.

8. The method according to any one of claims 6 or 7, further comprising: A historical state backtracking instruction for the communication network is received, wherein the historical state backtracking instruction specifies a historical time node to be queried; target data segments for restoring the transmission state for the historical time node are searched from the time series storage space for the historical state backtracking instruction; and the found target data segments are merged to restore the transmission state corresponding to the historical time node.

9. The method according to claim 8, wherein: Searching for a target data segment for restoring a transmission state for the historical state backtracking instruction includes: determining a time range including the historical time node; and searching, based on time information carried by each data segment in the time series storage space, for a data segment within the time range as the target data segment; wherein the data segment within the time range can cover the state item required by the historical state backtracking instruction.

10. The method according to claim 9, wherein: Determining a time range including the historical time node includes: extending time forward and backward with the time node as the starting point, and when a data segment is reached during the extension process, detecting state items contained in the reached data segment until the state items contained in the reached data segment can cover the data items required by the historical state backtracking instruction, ending the time extension to determine the time range; or, determining time boundary points forward and backward according to a preset time width with the historical event node as the origin; and using the two determined time boundary points as boundaries to determine the time range.

11. The method according to claim 8, wherein: The target data segments found are merged to restore the transmission status corresponding to the historical time node, including: deleting the status items in the target data segments that are not required by the transmission status query instruction; deduplicating the remaining status items in the target data segments to obtain the status items required by the historical status backtracking instruction. The status item is used as the transmission status corresponding to the historical time node.

12. The method according to claim 11, wherein: Deduplication of the remaining status items in the target data segment includes: when the credibility of the data segment stored in the time series database does not meet the preset standard, if there are two target data segments located at two instances of the historical time node and both contain the target status item, then retain the target status item in the target data segment closer to the historical time node; when the credibility of the data segment stored in the time series database exceeds the preset standard, if there are two target data segments located at two instances of the historical time node and both contain the target status item, then retain the target status item in the target data segment located before the historical time node.

13. The method according to claim 12, further comprising: If there are two target data segments that are located at the same instance of the historical time node and both contain a target state item, the target state item in the target data segment closer to the historical time node is retained.

14. The method according to claim 6, wherein: Storing the data segments in a preset time series storage space includes: storing the generated data segments in the time series storage space in a data stream manner; monitoring fluctuations of state values ​​under various state items during storage according to the data stream; and if it is detected that the state value under any state item is in a stable state within a local time period, performing semantic deduplication on the state value under the state item within the local time period before storing the data segments in the time series storage space.

15. The method according to claim 6, further comprising: If alarm data pushed by a communication device in the communication network is received, the alarm data is stored as a data fragment in the time series storage space; Receiving an alarm query instruction for the communication network, wherein the alarm query instruction specifies a historical time node to be queried; Searching the time series storage space for the alarm query instruction for target data segments used to restore alarm data for the historical time node; and fusing the found target data segments to restore the alarm data corresponding to the historical time node.

16. A network management and control system includes a state data management layer, wherein: The state data management layer includes a cache space for caching state data for each communication device in the communication network, and the state data manager is used to execute the network management and control method according to any one of claims 1 to 15.

17. A computer-readable storage medium storing a computer program, wherein: When the computer program is When executed by one or more processors, the one or more processors are caused to execute the network management and control method according to any one of claims 1 to 15.

18. A computer program product, comprising a computer program, wherein: When the computer program is executed by one or more processors, the one or more processors are caused to execute the network management and control method according to any one of claims 1 to 15.

Images