WO2023273919A1 - 故障处理方法、装置、存储介质及电子装置 - Google Patents

故障处理方法、装置、存储介质及电子装置 Download PDF

Info

Publication number
WO2023273919A1
WO2023273919A1 PCT/CN2022/099485 CN2022099485W WO2023273919A1 WO 2023273919 A1 WO2023273919 A1 WO 2023273919A1 CN 2022099485 W CN2022099485 W CN 2022099485W WO 2023273919 A1 WO2023273919 A1 WO 2023273919A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
control system
resource
component
fault
Prior art date
Application number
PCT/CN2022/099485
Other languages
English (en)
French (fr)
Inventor
周瑾
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2023273919A1 publication Critical patent/WO2023273919A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]

Definitions

  • Embodiments of the present disclosure relate to the communication field, and in particular, to a fault handling method, device, storage medium, and electronic device.
  • a service deployment may span multiple management domains, and a management domain corresponds to a management and control system.
  • a management domain corresponds to a management and control system.
  • it is usually required to be able to perform fault detection and automatic repair based on end-to-end services.
  • a fault/threshold warning occurs in a management and control system domain, if it only involves business within the domain, the management and control domain can be automatically repaired without the participation of other management and control domains or super management systems.
  • the self-healing cannot be completed in the control domain, the control domain needs to upgrade the problem to the super control system, start the self-repair operation of the service within the super control range, and drive the lower layer control domain to perform reconfiguration/rerouting and other functions. This series of processes requires interaction between multiple control systems.
  • a centralized control system such as a software-defined network control system (SDN controller) is based on a logically centralized control architecture, and completes centralized connection scheduling through control components such as call control, connection control, and routing control. Because it has global network resource information and can coordinately process all connection requests, resource allocation can be optimized through organization.
  • the management and control system is a layered architecture organized in a tree hierarchy, so as to control a large-scale network.
  • the domain management and control system directly manages the network elements; the super management and control system manages the domain management and control system.
  • the super management and control system does not directly manage network elements, but manages the actual network through the virtual network provided by the domain management and control system.
  • a border network element or some network resources managed by a certain domain management and control system may have an early warning or encounter a fault, especially an early warning or fault that the domain control system.
  • the super management and control system coordinates the management and control systems of multiple domains to recover and handle faults.
  • Embodiments of the present disclosure provide a fault handling method, device, storage medium, and electronic device to at least solve the problem in the related art that a super management and control system needs to coordinate management and control systems in multiple domains to handle faults, resulting in slow fault processing speed. .
  • a fault handling method including: receiving resource fault information; processing the resource fault information; and transmitting the resource fault information.
  • a fault processing device including: a receiving module configured to receive resource fault information; a processing module configured to process the resource fault information; a transfer module configured to transfer the resource accident details.
  • a computer-readable storage medium wherein a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to perform any one of the above-mentioned methods when running Steps in the examples.
  • an electronic device including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to perform any of the above Steps in the method examples.
  • FIG. 1 is a block diagram of a hardware structure of a wired device in a fault handling method according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a fault handling method according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of component interaction in an SDN management and control system according to an exemplary embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of interaction between SDN management and control systems according to an exemplary embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of component interaction between SDN management and control systems according to an exemplary embodiment of the present disclosure
  • connection-related SDN management and control systems according to an exemplary embodiment of the present disclosure
  • Fig. 7 is a structural block diagram of a fault handling device according to an embodiment of the present disclosure.
  • FIG. 1 is a block diagram of a hardware structure of a wired device according to a fault handling method according to an embodiment of the present disclosure.
  • the wired device may include one or more (only one is shown in FIG. 1) processor 102 (the processor 102 may include but not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 configured to store data, wherein the above-mentioned wired device may also include a transmission device 106 and an input/output device 108 configured to communicate.
  • FIG. 1 is only a schematic diagram, and does not limit the structure of the wired device.
  • a wired device may also include more or fewer components than shown in FIG. 1 , or have a different configuration than that shown in FIG. 1 .
  • the memory 104 can be set to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the fault handling method in the embodiment of the present disclosure, and the processor 102 runs the computer program stored in the memory 104 to execute Various functional applications and data processing are to realize the above-mentioned method.
  • the memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include memory located remotely from the processor 102, and such remote memory may be connected to a wired device through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission device 106 is configured to receive or transmit data via a network.
  • the specific example of the above-mentioned network may include a wired network provided by a communication provider.
  • Fig. 2 is a flow chart of the fault handling method according to an embodiment of the present disclosure. As shown in Fig. 2, the process includes the following steps:
  • Step S202 receiving resource failure information
  • Step S204 processing the resource failure information
  • Step S206 transmitting the resource failure information.
  • the resource failure information may be received by the management and control system, where the management and control system may be a centralized management and control system, such as a software-defined network management and control system (SDN controller).
  • SDN controller software-defined network management and control system
  • the management and control system can manage and control multiple subnetwork points (SNP).
  • SNP subnetwork points
  • the management and control system when the management and control system cannot handle the failure, it can also notify the super management and control system, and the super management and control system will notify the management and control systems in the management and control systems within its jurisdiction to make timely decisions, that is, other management and control systems can be equal to the management and control system.
  • the management and control system may also be a superior management and control system of the management and control system, that is, a super management and control system.
  • the resource fault information is received, it can also be processed in the management and control system, and at the same time, the resource fault information is transmitted to other management and control systems, and the management and control system and other management and control systems cooperate to process the fault corresponding to the resource fault information.
  • the fault information may be alarm information related to resources within the scope of the management and control system, including but not limited to: fault alarm, performance monitoring threshold exceeding, object creation or deletion, state change, and the like.
  • Handling operations may include restarting, reconfiguring, releasing connections, rerouting, handling calls, and the like.
  • the execution subject of the above steps may be a management and control system, for example, an LRM (Link Resource Manager) included in the management and control system.
  • LRM Link Resource Manager
  • the fault corresponding to the resource fault information after receiving the resource fault information, the fault corresponding to the resource fault information can be processed, and the resource fault information can be transmitted.
  • the resource fault information is received, the fault corresponding to the resource fault information can be directly processed, and the resource fault information can be transmitted directly, without deployment of the super management and control system. Therefore, it can solve the problem in the related art that the super management and control system needs to coordinate the management and control systems of multiple domains to handle the fault, resulting in a slow fault processing speed, and improves the fault processing speed.
  • the resource fault information is directly sent by the source component to the target component; within the range of multiple management and control systems in the untrusted domain, the resource fault information is sent by the Notification component delivered.
  • the resource fault information may be directly sent from the source component to the target component within the scope of multiple management and control systems in the trusted domain.
  • the resource failure information can be delivered by the notification component. That is, within the scope of multiple management and control systems in the same trusted domain, the resource fault information can be directly sent from the source component to the target component, where the target component can include a connection control component, a routing control component, a network call control component, and so on. Which component to send the resource fault information to can be determined according to the type of the resource fault information.
  • the resource failure information can be sent to the notification components of other management and control systems through the notification component of the management system, and the other management and control systems
  • the notification component sends resource failure information to target components in other management and control systems.
  • the resource failure information includes: resource-related alarm information within the management and control system, wherein the resource-related alarm information within the management and control system includes at least one of the following: failure alarm, performance Monitor threshold crossings, object creation or deletion, state changes.
  • resource failure information can be processed and/or resource failure information can be transmitted . For example, communicating resource failure information to other management systems, or communicating resource failure information to other components included in the management system.
  • processing the resource fault information includes abstractly aggregating the resource fault information.
  • fault notification information for notifying a fault can be determined by abstracting and aggregating resource fault information.
  • the source component directly sending the resource fault information to the target component includes: sending the resource fault information to a connection control component through the source component when the fault is a connection fault; When the failure is a routing failure, send the resource failure letter to the routing control component through the source component; when the failure is a network call failure, send the resource failure letter through the source component The letter is sent to the network call control component.
  • TAP terminal and adaptation executive
  • LRM Link Resource Manager
  • the LRM can determine the fault type according to the fault information, and when it is determined that the fault is a connection fault, it can send the resource fault information to the CC component (Connection Controller, connection management component).
  • the resource fault information can be sent to the RC component (Route Controller, routing control component).
  • the resource fault information can be sent to the NCC component (Network Call Controller, network call control component).
  • receiving resource failure information includes: receiving resource failure information reported from a forwarding plane within the management and control system; and/or receiving resource failure information sent from components in other management and control systems.
  • the resource fault information may be the resource fault information reported by the TAP component included in the management and control system, the resource fault information may be received by the source component in the management and control system, and the fault corresponding to the resource fault information may be processed in the source component, The resource fault information can also be sent to the target component included in the management and control system through the source component.
  • the TAP Long Adaptation and Adaptation Actuator
  • the LRM LRM
  • the resource failure information can also be information sent by other management and control systems, that is, when other management and control systems cannot handle the failure, or need the management and control system to assist in handling the failure, the resource failure information can be sent to the management and control system.
  • the method before receiving the resource failure information, the method further includes: pre-configuring policies among the plurality of management and control systems; determining all the resource failure information associated with the management and control systems based on the policies Describe resource failure information in other management and control systems.
  • policies can be pre-deployed in the management and control system, and resource failure information in other management and control systems can be determined according to the policies.
  • other management and control systems may be management and control systems associated with resource failure information between management and control systems. That is, the management and control system can receive resource failure information sent by other management and control systems, and before receiving resource failure information sent by other management and control systems, it needs to determine other management and control systems associated with it.
  • the method before determining the resource failure information in the other management and control system associated with the resource failure information between the management and control systems based on the policy, the method further includes at least one of the following: The management and control system of the notification component of the management and control system is determined to be the other management and control system; the management and control system associated with the management and control system is determined to be the other management and control system; The management and control system that pulls the message in the component is determined as the other management and control system.
  • the other management and control system may be a management and control system that subscribes to the messages of the notification component in the management and control system, it may also be a system pre-associated with the management and control system, or it may be a management and control system that periodically pulls connection messages from the management and control system system. That is, the fault information push mode can be a subscription mode, that is, the notification component of the management and control system 2 (corresponding to the notification components of the above-mentioned other management and control systems) subscribes to the connection-related messages of the notification component of the management and control system 1 (corresponding to the notification components of the above-mentioned management and control systems) .
  • the notification of management and control system 1 When the CC of management and control system 1 sends a connection-related notification message to the notification component, the notification of management and control system 1 will send a connection-related notification message to the notification component of management and control system 2. At this time, the notification of the management and control system 2 is notified to the local CC/RC component according to the local policy.
  • the notification of the first management and control system will send a connection-related notification message Go to the notification component of the control system 2.
  • the notification of the management and control system 2 is notified to the local CC/RC component according to the local policy.
  • the notification component of the second management and control system When the other management and control system is a management and control system that pulls connection messages from the notification component in the management and control system according to a predetermined period, the notification component of the second management and control system periodically obtains connection-related notifications from the notification component of the first management and control system. After obtaining the notification component of the control system 2, it notifies the local CC/RC component.
  • the LRM component included in the management and control system transmits the resource fault information to the notification component in the management and control system, and instructs the management and control system according to the pre-configured policies in the management and control system
  • the notification component in the system transmits the resource fault information to notification components in other untrusted management and control systems.
  • the connection resource management component may transmit the fault information to the notification component in the management and control system.
  • the notification component in the management and control system can transmit resource failure information to other untrusted management and control systems.
  • the LRM in the management and control system can obtain the resource failure of the target subnetwork through the TAP under the jurisdiction of the management and control system; the LRM in the management and control system can update the fault status of a certain connection/routing/call to CC/RC/NCC; the management and control system
  • the internal CC/RC/NCC component sends a notification message to the notification component of the management and control system; optionally, the LRM in the management and control system directly sends a notification message to the notification component of the management and control system; the decision of the notification component of the management and control system is based on the pre-deployed strategy Decide whether to notify other management and control systems, and decide which management and control system to notify specifically.
  • the method after instructing the notification component in the management and control system to transmit the resource fault information to notification components in other untrusted management and control systems according to the pre-configured policies in the management and control system, the method It also includes: after receiving the resource failure information, the notification component of the other untrusted management and control system processes the failure, and transmits the resource failure information to the target component of the other untrusted management and control system; wherein , passing to the target component of the other untrusted management and control system includes: in the case that the fault affects a connection fault, sending the resource fault information to the connection control component; in the case that the fault affects a routing fault In this case, the resource fault information is sent to the routing control component; when the fault affects the network call fault, the resource fault information is sent to the network call control component.
  • the notification component in the management and control system transmits the resource failure information to the notification components in other untrusted management and control systems, and the notification components of other untrusted management and control systems receive the resource failure information and can handle resource failures
  • the information corresponds to the failure
  • the resource failure information is passed to other target components of the non-trusted management and control system. That is, when the notification component in the management and control system locates other untrusted management and control systems, the notification component in the management and control system corresponds to the notification component of other untrusted management and control systems; the notification component of the management and control system sends notification messages to other untrusted management and control systems.
  • the notification component of the management and control system; the notification component of other untrusted management and control systems analyzes and processes the received notification messages through the previously pre-deployed strategy, and decides to notify the specific components in other untrusted management and control systems.
  • the CC/RC/NCC in the second management and control system; the CC/RC/NCC in the second management and control system decides to process the connection/routing/call after receiving the notification message. That is, according to the type of the fault, the resource fault information is sent to the component corresponding to the type.
  • the schematic diagram of component interaction between SDN management and control systems can be found in Figure 5, and the schematic diagram of component interface interaction between related SDN management and control systems can be seen in Figure 6.
  • the method After instructing the notification component in the management and control system to transmit the resource fault information to notification components in other untrusted management and control systems according to the pre-configured policies in the management and control system, the method It also includes: in the case that the other untrusted management and control system is the superior management and control system of the management and control system, performing one of the following operations: the first component included in the other untrusted management and control system is based on the resource failure information to process the resource failure information; the first component adjusts resources in the management and control system based on the failure information, so as to instruct a second component included in the management and control system to process the resource failure information.
  • the first component can Troubleshooting.
  • Other untrusted management and control systems can also directly adjust resources in the management and control system according to resource failure information. That is, if other untrusted management and control systems can see the resource status of the management and control system through transparent transmission, the notification component of other untrusted management and control systems can directly notify the LRM component of the management and control system to update the resource status of the management and control system.
  • the LRM After the LRM receives the fault alarm event information reported by the forwarding network element through the TAP module, the LRM updates and sends the latest connection status to the CC through the local connection status out interface, and carries specific connection information.
  • the interface of LRM involves (existing interface), in which the content of the performance notification is carried in the performance, and the fault alarm information is carried in the operationalnal state.
  • Local connection status out This interface is used to convey the information on the local connection status to CC, it also reports the state of SNPx.
  • connection status input interface local connection status After the CC receives the local connection status message through the connection status input interface local connection status in, it performs local processing.
  • connection state input interface parameters Refer to Table 2 for connection state input interface parameters.
  • the notification component handles it locally, and decides whether there is a message to be notified to other management and control systems. It can be notified by broadcasting or pre-subscribing. If not, terminate the process. If there is an association, it will be sent to the notification component of the management and control system 2 through the notification out interface.
  • the notification notification component of the management and control system 2 receives notification messages through the notifications in interface.
  • the receiving component When the receiving component is a CC, it involves the extension of the CC interface.
  • the receiving component When the receiving component is RC, it involves the extension of RC interface.
  • the CC determines the connection restart/reconfiguration/release according to the local connection state; after receiving the message, the RC determines the rerouting/restart/reconfiguration/release according to the local topology state.
  • the resource warning notification process between the upper and lower management and control systems is as follows:
  • the first control system is the domain control system
  • the second control system is the super control system above the first domain control system.
  • a client context in control system 1 corresponds to control system 2.
  • Resource mapping query This interface is used to query to the RDB to get the relationship between the network resources in the seryer context and the cotresponding virtual network resources in the client contexts.
  • Resource mapping query This interface is used to query the RDB to obtain the relationship between the network resources in the server context and the corresponding virtual network resources in the client context) to obtain whether the current resource has a corresponding virtual network resource in the client context. If so, you need Report to the management and control system 2.
  • the notification component of control system 1 notifies the notification component of control system 2 through the notifications out interface.
  • the notification component of management and control system 2 After the notification component of management and control system 2 receives the notification from management and control system 1 through the notification in component, it queries the corresponding connection through the interface Connection correlation query (connection correlation query), and notifies the corresponding CC through the notificationout interface. CC makes timely adjustments to the current connection through the notificationin interface.
  • the notification component of the management and control system 2 can also directly notify the corresponding LRM component to update the resource status.
  • the receiving interface corresponding to LRM is described in the following table:
  • the fault processing system may include a notification module (corresponding to the running module of the above-mentioned notification component), a CC module (corresponding to the running module of the above-mentioned CC component), an RC module (corresponding to the running module of the above-mentioned RC component), an NCC module (corresponding to the running module of the above-mentioned RC component), an NCC module (corresponding to the above-mentioned The running module of the NCC component), the LRM module (corresponding to the running module of the above-mentioned LRM component), etc.
  • a notification module corresponding to the running module of the above-mentioned notification component
  • a CC module corresponding to the running module of the above-mentioned CC component
  • an RC module corresponding to the running module of the above-mentioned RC component
  • an NCC module corresponding to the running module of the above-mentioned RC component
  • NCC module corresponding to the running module of the above-mentioned LRM
  • Notification modules can be set to:
  • the notification module receives the notification or fault information sent by the CC/RC/NCC in the management and control system;
  • the notification module receives the notification or fault information sent by the LRM in the management and control system
  • the notification module determines whether the received notification message is notified to the relevant management and control system
  • the notification module decides which relevant management and control systems to send the received notification messages to;
  • the notification module sends a notification message to the notification module of the relevant management and control system
  • the notification module interacts with the data service module to convert the namespace
  • the notification module receives and processes the notification messages sent by the notification modules of other control systems
  • the notification module decides which components in the management and control system to send the locally received notification messages to;
  • the notification module sends resource/connection/routing/call related notification messages to the LRM/CC/RC/NCC in the management and control system.
  • the notification module receives subscription messages sent by other management and control systems
  • the CC module can be set to:
  • the RC module can be set to:
  • the NCC module can be set to:
  • the LRM module can be set to:
  • the method according to the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation.
  • the technical solution of the present disclosure can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to enable a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present disclosure.
  • a fault processing device is also provided, which is configured to implement the above embodiments and preferred implementation modes, and what has been explained will not be repeated here.
  • the term "module” may be a combination of software and/or hardware that realizes a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
  • Fig. 7 is a structural block diagram of a fault processing device according to an embodiment of the present disclosure. As shown in Fig. 7, the device includes:
  • the receiving module 72 is configured to receive resource failure information
  • a processing module 74 configured to process the resource failure information
  • the transmitting module 76 is configured to transmit the resource failure information.
  • the resource fault information is directly sent by the source component to the target component; within the range of multiple management and control systems in the untrusted domain, the resource fault information is sent by the Notification component delivered.
  • the resource failure information includes: resource-related alarm information within the management and control system, wherein the resource-related alarm information within the management and control system includes at least one of the following: failure alarm, performance Monitor threshold crossings, object creation or deletion, state changes.
  • the processing module 74 realizes processing the resource failure information in the following manner: abstracting and aggregating the resource failure information.
  • the delivery module 76 realizes that the source component directly sends the resource failure information to the target component in the following manner: when the failure is a connection failure, the resource failure information is transmitted by the source component Send to the connection control component; in the case of the fault is a routing fault, send the resource fault letter to the routing control component through the source component; in the case of the fault is a network call fault, through the source The component sends the resource failure letter to the network call control component.
  • the receiving module 72 realizes receiving resource failure information in the following manner: receiving resource failure information reported from the forwarding plane within the scope of the management and control system; and/or receiving information sent by components in other management and control systems resource fault information.
  • the device is further configured to pre-configure policies among multiple management and control systems before receiving the resource failure information; Describe resource failure information in other management and control systems.
  • the device is further configured to subscribe to the management and control system before determining the resource failure information in the other management and control system associated with the resource failure information between the management and control systems based on the policy.
  • the management and control system of the message of the notification component of the notification component is determined to be other management and control systems; the management and control system associated with the management and control system is determined to be the other management and control system; The management and control system is determined as the other management and control system.
  • the LRM component included in the management and control system transmits the resource fault information to the notification component in the management and control system, and instructs the management and control system according to the pre-configured policies in the management and control system
  • the notification component in the system transmits the resource fault information to notification components in other untrusted management and control systems.
  • the notification component in the management and control system instructing the notification component in the management and control system to transmit the resource failure information to the notification components in other untrusted management and control systems, the other untrusted
  • the notification component of the information management and control system is used to process the failure after receiving the resource failure information, and deliver the resource failure information to the target components of the other untrusted management and control systems;
  • the target components of other untrusted management and control systems include: in the case that the fault affects the connection fault, sending the resource fault information to the connection control component; in the case that the fault affects the routing fault, sending the The resource fault information is sent to the routing control component; and in the case that the fault affects the network call fault, the resource fault information is sent to the network call control component.
  • the other non-trusted management and control systems is configured to perform one of the following operations if it is a superior management and control system of the management and control system: the first component included in the other untrusted management and control system checks the resources based on the resource failure information The fault information is processed; the first component adjusts resources in the management and control system based on the fault information, so as to instruct a second component included in the management and control system to process the resource fault information.
  • each of the above-mentioned modules can be implemented by software or hardware.
  • it can be implemented in the following manner, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned modules can be combined in any combination The forms of are located in different processors.
  • Embodiments of the present disclosure also provide a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the above method embodiments when running.
  • the above-mentioned computer-readable storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM) , mobile hard disk, magnetic disk or optical disk and other media that can store computer programs.
  • ROM read-only memory
  • RAM random access memory
  • mobile hard disk magnetic disk or optical disk and other media that can store computer programs.
  • Embodiments of the present disclosure also provide an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • each module or each step of the above-mentioned disclosure can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices
  • they can be implemented in program code executable by a computing device, and thus, they can be stored in a storage device to be executed by a computing device, and in some cases, can be executed in an order different from that shown here.
  • steps, or they are made into individual integrated circuit modules, or multiple modules or steps among them are made into a single integrated circuit module to realize.
  • the present disclosure is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开实施例提供了一种故障处理方法、装置、存储介质及电子装置，其中，该方法包括：接收资源故障信息；处理资源故障信息；传递资源故障信息。

Description

故障处理方法、装置、存储介质及电子装置
相关申请的交叉引用
本公开基于2021年6月30日提交的发明名称为“故障处理方法、装置、存储介质及电子装置”的中国专利申请CN202110742587.3，并且要求该专利申请的优先权，通过引用将其所公开的内容全部并入本公开。
技术领域
本公开实施例涉及通信领域，具体而言，涉及一种故障处理方法、装置、存储介质及电子装置。
背景技术
一个服务部署可能横跨多个管理域，一个管理域对应一个管控系统。对于一个跨域业务，通常要求能够进行基于端到端服务的故障检测和自动修复。如果一个管控系统域内发生故障/阈值预警，如果只是涉及域内业务，则本管控域可自动修复，无需其他管控域或者超级管理系统的参与。如果本管控域内无法完成进行自我修复，则本管控域需要将问题升级到超级管控系统，在超级管控范围内启动服务的自我修复操作，并驱动下层管控域内执行重配置/重路由等功能。这一系列流程需要多个管控系统之间交互。
集中式管控系统，如软件定义网络管控系统(SDN controller)，基于逻辑集中的控制架构，通过呼叫控制，连接控制，路由控制等控制组件完成集中式的连接调度。因具有全局网络资源信息并能协同处理全部连接请求，能够从整理来优化资源配置。在相关技术中，管控系统是按照树形层次化组织的分层架构，以便控制大规模网络。直接管理网元的是域管控系统；管理域管控系统的是超级管控系统，超级管控系统不直接管理网元，通过域管控系统提供的虚拟网络对实际网络进行管理。网络实际运行过程中，某一个域管控系统所管理的边界网元或者一部分网络资源可能出现预警或者遇到故障，尤其是域管控系统无法完成处理的预警或者故障，则需要将本告警衍生到超级管控系统。由超级管控系统协调多个域的管控系统进行故障的恢复和处理。
由此可知，相关技术中存在需要超级管控系统协调多个域的管控系统进行故障处理故障导致故障处理速度慢的问题。
针对相关技术中存在的上述问题，目前尚未提出有效的解决方案。
发明内容
本公开实施例提供了一种故障处理方法、装置、存储介质及电子装置，以至少解决相关技术中存在的需要超级管控系统协调多个域的管控系统进行故障处理故障导致故障处理速度慢的问题。
根据本公开的一个实施例，提供了一种故障处理方法，包括：接收资源故障信息；处理所述资源故障信息；传递所述资源故障信息。
根据本公开的另一个实施例，提供了一种故障处理装置，包括：接收模块，设置为接收资源故障信息；处理模块，设置为处理所述资源故障信息；传递模块，设置为传递所述资源 故障信息。
根据本公开的又一个实施例，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
附图说明
图1是本公开实施例的一种故障处理方法的有线设备的硬件结构框图；
图2是根据本公开实施例的故障处理方法的流程图；
图3是根据本公开示例性实施例的SDN管控系统内组件交互示意图；
图4是根据本公开示例性实施例的SDN管控系统间交互示意图；
图5是根据本公开示例性实施例的SDN管控系统间组件交互示意图；
图6是根据本公开示例性实施例的连接相关SDN管控系统间组件接口交互示意图；
图7是根据本公开实施例的故障处理装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开的实施例。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例中所提供的方法实施例可以在有线设备、计算机终端或者类似的运算装置中执行。以运行在有线设备上为例，图1是本公开实施例的一种故障处理方法的有线设备的硬件结构框图。如图1所示，有线设备可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和设置为存储数据的存储器104，其中，上述有线设备还可以包括设置为通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述有线设备的结构造成限定。例如，有线设备还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可设置为存储计算机程序，例如，应用软件的软件程序以及模块，如本公开实施例中的故障处理方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至有线设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106设置为经由一个网络接收或者发送数据。上述的网络具体实例可包括通信供应商提供的有线网络。
在本实施例中提供了一种故障处理方法，图2是根据本公开实施例的故障处理方法的流 程图，如图2所示，该流程包括如下步骤：
步骤S202，接收资源故障信息；
步骤S204，处理所述资源故障信息；
步骤S206，传递所述资源故障信息。
在上述实施例中，可以由管控系统接收资源故障信息，其中，管控系统可以为集中式管控系统，如软件定义网络管控系统(SDN controller)。管控系统可以管控多个子网点(Subnetwork Point，SNP)。在域管控系统获取到预警或者故障信息后，如果本地能够处理，则可以发送故障/预警信息到本地系统中的对应组件。如果本地无法处理故障，则可以通过通知组件通知到其他管控系统，以便其他管控系统及时作出决策。当然，当管控系统无法处理故障时，还可以通知到超级管控系统，由超级管控系统通知其管辖范围内的管控系统中的管控系统及时作出决策，即其他管控系统可以为与管控系统平级的管控系统，还可以为管控系统的上级管控系统，即超级管控系统。当然，当接收到资源故障信息时，还可以在管控系统中进行处理，同时将资源故障信息传递给其他管控系统，由管控系统和其他管控系统协同处理资源故障信息对应的故障。其中，故障信息可以是管控系统范围内的资源相关的告警信息，包括但不限于：故障告警、性能监控阈值过限、对象创建或删除、状态变更等。
在上述实施例中，不同的故障信息对应不同的处理操作。处理操作可以包括重启、重配、释放连接、重路由、处理呼叫等。
可选地，上述步骤的执行主体可以为管控系统，例如，管控系统中包括的LRM(链路资源管理器)。
通过本公开，在接收到资源故障信息后，可以处理资源故障信息对应的故障，以及传递资源故障信息。由于在接收到资源故障信息时，可以直接处理资源故障信息对应的故障，并直接传递资源故障信息，无需超级管控系统的调配。因此，可以解决相关技术中存在的需要超级管控系统协调多个域的管控系统进行故障处理故障导致故障处理速度慢的问题，提高了故障处理的速度。
在一个示例性实施例中，在可信域内多个管控系统范围内，所述资源故障信息由源组件直接发送目标组件；在非可信域内多个管控系统范围内，所述资源故障信息由通知组件传递。在本实施例中，在接收到资源故障信息后，在可信域内多个管控系统范围内，资源故障信息可以由源组件直接发送给目标组件。在非可信域内可以由通知组件传递资源故障信息。即在同一个可信域内的多个管控系统范围内，可以直接由源组件将资源故障信息发送给目标组件，其中，目标组件可以包括连接控制组件、路由控制组件、网络呼叫控制组件等。可以根据资源故障信息的类型确定将资源故障信息发送给哪一个组件。
在上述实施例中，在非可信域内多个管控系统范围内，当接收到资源故障信息后，可以通过管理系统的通知组件将资源故障信息发送给其他管控系统的通知组件，由其他管控系统的通知组件将资源故障信息发送给其他管控系统中的目标组件。
在一个示例性实施例中，所述资源故障信息包括：管控系统范围内的资源相关的告警信息，其中，所述管控系统范围内的资源相关的告警信息包括以下至少之一：故障告警、性能监控阈值过限、对象创建或删除、状态变更。在本实施例中，在接收到故障告警、性能监控阈值过限、对象创建或删除、状态变更等信息中包括的一个或多个信息后，可以处理资源故障信息，和/或传递资源故障信息。例如，将资源故障信息传递给其他管控系统，或者将资源 故障信息传递给管控系统中包括的其他组件。
在一个示例性实施例中，处理所述资源故障信息包括抽象聚合所述资源故障信息。在本实施例中，可以通过抽象和聚合资源故障信息以确定出用于通知发生故障的故障通知信息。
在一个示例性实施例中，所述资源故障信息由源组件直接发送目标组件包括：在所述故障为连接故障的情况下，通过所述源组件将所述资源故障信息发送给连接控制组件；在所述故障为路由故障的情况下，通过所述源组件将所述资源故障信发送给路由控制组件；在所述故障为网络呼叫故障的情况下，通过所述源组件将所述资源故障信发送给网络呼叫控制组件。在本实施例中，由TAP(终结和适配执行器)获取到资源状态后，上报LRM(链路资源管理器)，LRM跟CC/RC/NCC直接交互跟连接/路由/呼叫相关的故障通知。即，LRM可以根据故障信息确定故障类型，当确定故障为连接故障的情况下，可以将资源故障信息发送给CC组件(Connection Controller，连接管控组件)。当故障为路由故障的情况下，可以将资源故障信息发送给RC组件(Route Controller，路由管控组件)。当故障为网络呼叫故障的情况下，可以将资源故障信息发送给NCC组件(Network Call Controller，网络呼叫管控组件)。
在一个示例性实施例中，接收资源故障信息包括：接收来自于管控系统范围内的转发面上报的资源故障信息；和/或接收来自于其他管控系统内的组件发送过来的资源故障信息。在本实施例中，资源故障信息可以为本管控系统中包括的TAP组件上报的资源故障信息，可以通过管控系统内的源组件接收资源故障信息，在源组件中处理资源故障信息对应的故障，还可以通过源组件将资源故障信息发送给管控系统中包括的目标组件。例如，在管控系统所管辖的目标子网点发生故障时，管控系统中的TAP(终结和适配执行器)可以获取到管控系统中的子网点的资源故障信息，并将资源故障信息传递给LRM(对应于上述源组件)，LRM接收到TAP发送的资源故障信息。资源故障信息还可以为其他管控系统发送的信息，即在其他管控系统无法处理故障，或者需要管控系统协助处理故障时，可以将资源故障信息发送给管控系统。
在一个示例性实施例中，在接收资源故障信息之前，所述方法还包括：在多个所述管控系统间预先配置策略；基于所述策略确定关联所述管控系统间的资源故障信息的所述其他管控系统内的资源故障信息。在本实施例中，可以在管控系统内预先部署策略，根据策略确定其他管控系统中的资源故障信息。其中，其他管控系统可以为关联了管控系统间的资源故障信息的管控系统。即管控系统可以接收其他管控系统发送的资源故障信息，在接收其他管控系统发送的资源故障信息之前，需要确定出与之关联的其他管控系统。
在一个示例性实施例中，在基于所述策略确定关联所述管控系统间的资源故障信息的所述其他管控系统内的资源故障信息之前，所述方法还包括以下至少之一：将订阅了所述管控系统的通知组件的消息的管控系统确定为所述其他管控系统；将与所述管控系统关联的管控系统确定为所述其他管控系统；将按照预定周期从所述管控系统中的通知组件中拉取消息的管控系统确定为所述其他管控系统。在本实施例中，其他管控系统可以为订阅了管控系统中的通知组件的消息的管控系统，还可以为与管控系统预先关联的系统，也可以为从管控系统中定期拉取连接消息的管控系统。即故障信息推送模式可以为订阅模式，即管控系统二的notification组件(对应于上述其他管控系统的通知组件)订阅管控系统一的notification组件(对应于上述管控系统的通知组件)的连接相关的消息。当管控系统一的CC发送连接相关的通知消息给notification组件时，管控系统一的notification会发送连接相关的通知 消息到管控系统二的notification组件。此时，管控系统二的notification根据本地的策略，通知到本地CC/RC组件。
当其他管控系统为预先配置的与所述管控系统关联的管控系统的情况下，当管控系统一的CC发送连接相关的通知消息给notification组件时，管控系统一的notification会发送连接相关的通知消息到管控系统二的notification组件。此时，管控系统二的notification根据本地的策略，通知到本地CC/RC组件。
当其他管控系统为按照预定周期从所述管控系统中的通知组件中拉取连接消息的管控系统的情况下，管控系统二notification组件循环定时从管控系统一的notification组件获取跟连接相关的通知。获取到后管控系统二的notification组件，通知到本地的CC/RC组件。
在一个示例性实施例中，在非可信域内，管控系统中包括的LRM组件将所述资源故障信息传递给所述管控系统中的通知组件，根据管控系统中预先配置的策略指示所述管控系统中的通知组件将所述资源故障信息传递给其他非可信管控系统中的通知组件。在本实施例中，连接资源管理组件可以将故障信息传递给本管控系统中的通知组件。管控系统中的通知组件可以将资源故障信息传递给其他非可信管控系统。例如，管控系统内的LRM可以通过管控系统管辖内的TAP获取到目标子网点的资源的故障；管控系统内LRM可以更新某个连接/路由/呼叫的故障状态到CC/RC/NCC；管控系统内的CC/RC/NCC组件发送通知消息到管控系统的通知组件；可选地，管控系统内的LRM直接发送通知消息到管控系统内的通知组件；管控系统的通知组件决策根据预先部署的策略决策是否要通知到其他管控系统，并决策要具体通知的管控系统。当管控系统内可以完成对故障的通知和处理，则可以由管控域内的管控组件直接交互完成处理。其中，SDN管控系统内组件交互示意图可参见附图3。当组件内无法完成对故障的通知和处理时，可以通知其他管控系统处理故障。其中，SDN管控系统间交互示意图可参见附图4。其中，附图3和附图4中所涉及到的各个控制器即为管控系统。
在一个示例性实施例中，在在根据管控系统中预先配置的策略指示所述管控系统中的通知组件将所述资源故障信息传递给其他非可信管控系统中的通知组件之后，所述方法还包括：所述其他非可信管控系统的通知组件接收到所述资源故障信息后，处理所述故障，并将所述资源故障信息传递给所述其他非可信管控系统的目标组件；其中，传递给所述其他非可信管控系统的目标组件包括：在所述故障影响到连接故障的情况下，将所述资源故障信息发送给连接控制组件；在所述故障影响到路由故障的情况下，将所述资源故障信息发送给路由控制组件；在所述故障影响到网络呼叫故障的情况下，将所述资源故障信息发送给网络呼叫控制组件。在本实施例中，在管控系统中的通知组件将资源故障信息传递给其他非可信管控系统中的通知组件，由其他非可信管控系统的通知组件接到资源故障信息，可以处理资源故障信息对应的故障，并将资源故障信息传递给其他非可信管控系统的目标组件。即在管控系统中的通知组件定位到其他非可信管控系统的情况下，管控系统中的通知组件对应其他非可信管控系统的通知组件；管控系统的通知组件发送通知消息到其他非可信管控系统的通知组件；其他非可信管控系统的通知组件通过之前预部署的策略对接收到的通知消息进行分析和处理，决策将消息通知到其他非可信管控系统内的具体组件。例如，第二管控系统内的CC/RC/NCC；第二管控系统内的CC/RC/NCC接收到通知消息决策对连接/路由/呼叫进行处理。即，根据故障的类型将资源故障信息发送给与该类型对应的组件中。其中，SDN管控系统间组件交互示意图可参见附图5，连接相关SDN管控系统间组件接口交互示意图可参见附图6。
在一个示例性实施例中，在在根据管控系统中预先配置的策略指示所述管控系统中的通知组件将所述资源故障信息传递给其他非可信管控系统中的通知组件之后，所述方法还包括：在所述其他非可信管控系统为所述管控系统的上级管控系统的情况下，执行以下操作之一：所述其他非可信管控系统中包括的第一组件基于所述资源故障信息对所述资源故障信息进行处理；所述第一组件基于所述故障信息调整所述管控系统中的资源，以指示所述管控系统中包括的第二组件对所述资源故障信息进行处理。在本实施例中，当其他非可信管控系统为第一管控系统的上级管控系统时，即当其他非可信管控系统可以为超级管控系统的情况下，第一组件可以根据资源故障信息对故障进行处理。其他非可信管控系统也可以直接可以根据资源故障信息调整管控系统中的资源。即其他非可信管控系统如果可以透传看到管控系统的资源情况，也可以直接由其他非可信管控系统的notification组件，直接通知到管控系统的LRM组件，更新管控系统的资源状态。
下面结合具体实施方式对故障处理方法进行说明：
管控系统之间的连接故障通知过程如下：
LRM通过TAP模块收到转发网元上报的故障告警事件信息后，LRM则通过local connection status out接口更新和发送最新的连接状态到CC，并携带具体的连接信息。
LRM的接口涉及(已有接口)，其中性能通知的内容在performance中携带，故障告警信息在operaticnal state中携带。Local connection status out：This interface is used to convey the information on the local connection status to CC，it also reports the state of SNPx.(本地连接状态断开接口：该接口用于向CC传送关于本地连接状态的信息，其还报告SNPx的状态)。LRM的接口参数可参见表1。
表1
Figure PCTCN2022099485-appb-000001
CC通过连接状态输入接口local connection status in接收到本地连接状态local connection status消息后，进行本地处理。连接状态输入接口参数可参见表2。
表2
Figure PCTCN2022099485-appb-000002
CC通知到notification组件。
Output interface Basic output parameters Basic return parameters
Notification out Notification  
通知Notification组件通过notification in接口接收到从CC发送过来的通知消息。
Input interface Basic input parameters Basic return parameters
Notifications jn Notifications -
notification组件本地处理，决策是否有消息要通知到其他管控系统。可通过广播或者提前订阅的方式通知。如果没有，则终止流程。如果有关联，则通过notification out接口发送给管控系统二的notification组件。
Output interface Basic output parameters Basic return parameters
Notifications out Notifications -
管控系统二的通知notification组件通过notifications in接口接收到通知消息。
Input interface Basic input parameters Basic return parameters
Notifications in Connection Notifications -
先通过访问DS进行本地命名空间转换，再本地处理。决策是否发给本地组件，并通过notifications out接口通知到对应组件。
Output interface Basic output parameters Basic return parameters
Notifications out Notifications -
接收组件为CC时，涉及CC接口的扩展。
Input interface Basic input parameters Basic return parameters
Connection Notification in link connection id -
接收组件为RC时，涉及RC接口的扩展。
Input interface Basic input parameters Basic return parameters
Route Notification in Route  
CC收到消息后，根据本地的连接状态，确定是连接重启/重配/释放；RC收到消息后，根据本地的拓扑状态，确定是重路由/重启/重配/释放。
当第二管控系统为第一管控系统的上级系统的情况下，上下级管控系统之间的资源预警通知过程如下：
管控系统一为域管控系统，管控系统二为域管控系统一之上的超级管控系统。管控系统一中的某个client context对应管控系统二。
管控系统一的LRM通过TAP模块收到本地网元上报的故障告警事件信息后，LRM上报notification组件。Notification组件，通过接口Resource mapping query(Resource mapping query：This interface is used to query to the RDB to get the relationship between the network resources in the seryer context and the cotresponding virtual network resources in the client contexts。(资源映射查询：该接口用于查询RDB，得到服务器上下文中的网络资源与客户端上下文中对应的虚拟网络资源之间的关系)获取到当前资源是否在client context中有对应的虚拟网络资源。如果有，则需要上报到管控系统二。
此时管控系统一的notifiction组件通过notifications out接口通知管控系统二的notification组件。
管控系统二的notification组件通过notification in组件接收到管控系统一的通知后， 通过接口Connection correlation query(连接关联查询)查询到对应的连接，并通过notificationout接口通知到对应的CC。CC通过notificationin接口对当前的连接及时作出调整。
管控系统二如果可以透传看到管控系统一的资源情况，也可以直接由管控系统二的notification组件，直接通知到对应的LRM组件，更新资源状态。LRM对应的接收接口如下表所述：
Figure PCTCN2022099485-appb-000003
故障处理系统可以包括通知模块(对应于上述通知组件的运行模块)，CC模块(对应于上述CC组件的运行模块)，RC模块(对应于上述RC组件的运行模块)，NCC模块(对应于上述NCC组件的运行模块)，LRM模块(对应于上述LRM组件的运行模块)等。
通知模块可以设置为：
通知模块接收到本管控系统内的CC/RC/NCC上发送的通知或者故障信息；
通知模块接收到本管控系统内的LRM发送的通知或者故障信息；
通知模块决策接收到的通知消息是否通知到相关管控系统；
通知模块决策接收到的通知消息发送给哪些相关管控系统；
通知模块发送通知消息到相关管控系统的通知模块；
通知模块跟数据服务模块交互进行命名空间的转换；
通知模块接收并处理其他管控系统的通知模块发送过来的通知消息；
通知模块决策将本地接收到的通知消息发送给本管控系统内哪些组件；
通知模块发送资源/连接/路由/呼叫相关通知消息到本管控系统内的LRM/CC/RC/NCC。
通知模块接收其他管控系统发送的订阅消息；
CC模块可以设置为：
发送跟连接相关的通知消息到通知模块；
接收通知模块发送的跟某个连接相关的通知消息，本地决策重启/重配/释放连接。
RC模块可以设置为：
发送跟路由相关的通知消息到通知模块；
接收通知模块发送的跟某个路由相关的通知消息，本地决策重路由。
NCC模块可以设置为：
发送跟呼叫相关的通知消息到通知模块；
接收通知模块发送的跟某个呼叫相关的通知消息，本地决策处理呼叫。
LRM模块可以设置为：
发送跟资源相关的通知消息到通知模块；
接收通知模块发送的跟某个资源相关的通知消息，本地决策重启/重配/释放资源。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前 者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
在本实施例中还提供了一种故障处理装置，该装置设置为实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图7是根据本公开实施例的故障处理装置的结构框图，如图7所示，该装置包括：
接收模块72，设置为接收资源故障信息；
处理模块74，设置为处理所述资源故障信息；
传递模块76，设置为传递所述资源故障信息。
在一个示例性实施例中，在可信域内多个管控系统范围内，所述资源故障信息由源组件直接发送目标组件；在非可信域内多个管控系统范围内，所述资源故障信息由通知组件传递。
在一个示例性实施例中，所述资源故障信息包括：管控系统范围内的资源相关的告警信息，其中，所述管控系统范围内的资源相关的告警信息包括以下至少之一：故障告警、性能监控阈值过限、对象创建或删除、状态变更。
在一个示例性实施例中，处理模块74通过如下方式实现处理所述资源故障信息：抽象聚合所述资源故障信息。
在一个示例性实施例中，传递模块76通过如下方式实现所述资源故障信息由源组件直接发送目标组件：在所述故障为连接故障的情况下，通过所述源组件将所述资源故障信息发送给连接控制组件；在所述故障为路由故障的情况下，通过所述源组件将所述资源故障信发送给路由控制组件；在所述故障为网络呼叫故障的情况下，通过所述源组件将所述资源故障信发送给网络呼叫控制组件。
在一个示例性实施例中，接收模块72通过如下方式实现接收资源故障信息：接收来自于管控系统范围内的转发面上报的资源故障信息；和/或接收来自于其他管控系统内的组件发送过来的资源故障信息。
在一个示例性实施例中，所述装置还设置为在接收资源故障信息之前，在多个所述管控系统间预先配置策略；基于所述策略确定关联所述管控系统间的资源故障信息的所述其他管控系统内的资源故障信息。
在一个示例性实施例中，所述装置还设置为在基于所述策略确定关联所述管控系统间的资源故障信息的所述其他管控系统内的资源故障信息之前，将订阅了所述管控系统的通知组件的消息的管控系统确定为其他管控系统；将与所述管控系统关联的管控系统确定为所述其他管控系统；将按照预定周期从所述管控系统中的通知组件中拉取消息的管控系统确定为所述其他管控系统。
在一个示例性实施例中，在非可信域内，管控系统中包括的LRM组件将所述资源故障信息传递给所述管控系统中的通知组件，根据管控系统中预先配置的策略指示所述管控系统中的通知组件将所述资源故障信息传递给其他非可信管控系统中的通知组件。
在一个示例性实施例中，在根据管控系统中预先配置的策略指示所述管控系统中的通知组件将所述资源故障信息传递给其他非可信管控系统中的通知组件，所述其他非可信管控系统的通知组件用于在接收到所述资源故障信息后，处理所述故障，并将所述资源故障信息传递给所述其他非可信管控系统的目标组件；其中，传递给所述其他非可信管控系统的目标组件包括：在所述故障影响到连接故障的情况下，将所述资源故障信息发送给连接控制组件；在所述故障影响到路由故障的情况下，将所述资源故障信息发送给路由控制组件；在所述故障影响到网络呼叫故障的情况下，将所述资源故障信息发送给网络呼叫控制组件。
在一个示例性实施例中，在根据管控系统中预先配置的策略指示所述管控系统中的通知组件将所述资源故障信息传递给其他非可信管控系统中的通知组件之后，所述其他非可信管控系统用于在为所述管控系统的上级管控系统的情况下，执行以下操作之一：所述其他非可信管控系统中包括的第一组件基于所述资源故障信息对所述资源故障信息进行处理；所述第一组件基于所述故障信息调整所述管控系统中的资源，以指示所述管控系统中包括的第二组件对所述资源故障信息进行处理。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本公开的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、 改进等，均应包含在本公开的保护范围之内。

Claims (14)

  1. 一种故障处理方法，包括：
    接收资源故障信息；处理所述资源故障信息；传递所述资源故障信息。
  2. 根据权利要求1所述的方法，其中，
    在可信域内多个管控系统范围内，所述资源故障信息由源组件直接发送目标组件；
    在非可信域内多个管控系统范围内，所述资源故障信息由通知组件传递。
  3. 根据权利要求1所述的方法，其中，所述资源故障信息包括：
    管控系统范围内的资源相关的告警信息，其中，所述管控系统范围内的资源相关的告警信息包括以下至少之一：故障告警、性能监控阈值过限、对象创建或删除、状态变更。
  4. 根据权利要求1所述的方法，其中，
    处理所述资源故障信息包括抽象聚合所述资源故障信息。
  5. 根据权利要求2所述的方法，其中，所述资源故障信息由源组件直接发送目标组件包括：
    在所述故障为连接故障的情况下，通过所述源组件将所述资源故障信息发送给连接控制组件；
    在所述故障为路由故障的情况下，通过所述源组件将所述资源故障信发送给路由控制组件；
    在所述故障为网络呼叫故障的情况下，通过所述源组件将所述资源故障信发送给网络呼叫控制组件。
  6. 根据权利要求1所述的方法，接收资源故障信息包括：
    接收来自于管控系统范围内的转发面上报的资源故障信息；和/或接收来自于其他管控系统内的组件发送过来的资源故障信息。
  7. 根据权利要求6所述的方法，其中，在接收资源故障信息之前，所述方法还包括：
    在多个所述管控系统间预先配置策略；
    基于所述策略确定关联所述管控系统间的资源故障信息的所述其他管控系统内的资源故障信息。
  8. 根据权利要求7所述的方法，其中，在基于所述策略确定关联所述管控系统间的资源故障信息的所述其他管控系统内的资源故障信息之前，所述方法还包括以下至少之一：
    将订阅了所述管控系统的通知组件的消息的管控系统确定为其他管控系统；
    将与所述管控系统关联的管控系统确定为所述其他管控系统；
    将按照预定周期从所述管控系统中的通知组件中拉取消息的管控系统确定为所述其他管 控系统。
  9. 根据权利要求1所述的方法，其中，在非可信域内，管控系统中包括的LRM组件将所述资源故障信息传递给所述管控系统中的通知组件，根据管控系统中预先配置的策略指示所述管控系统中的通知组件将所述资源故障信息传递给其他非可信管控系统中的通知组件。
  10. 根据权利要求9所述的方法，其中，在根据管控系统中预先配置的策略指示所述管控系统中的通知组件将所述资源故障信息传递给其他非可信管控系统中的通知组件之后，所述方法还包括：
    所述其他非可信管控系统的通知组件接收到所述资源故障信息后，处理所述故障，并将所述资源故障信息传递给所述其他非可信管控系统的目标组件；
    其中，传递给所述其他非可信管控系统的目标组件包括：在所述故障影响到连接故障的情况下，将所述资源故障信息发送给连接控制组件；
    在所述故障影响到路由故障的情况下，将所述资源故障信息发送给路由控制组件；
    在所述故障影响到网络呼叫故障的情况下，将所述资源故障信息发送给网络呼叫控制组件。
  11. 根据权利要求9所述的方法，其中，在根据管控系统中预先配置的策略指示所述管控系统中的通知组件将所述资源故障信息传递给其他非可信管控系统中的通知组件之后，所述方法还包括：
    在所述其他非可信管控系统为所述管控系统的上级管控系统的情况下，执行以下操作之一：
    所述其他非可信管控系统中包括的第一组件基于所述资源故障信息对所述资源故障信息进行处理；
    所述第一组件基于所述故障信息调整所述管控系统中的资源，以指示所述管控系统中包括的第二组件对所述资源故障信息进行处理。
  12. 一种故障处理装置，包括：
    接收模块，设置为接收资源故障信息；
    处理模块，设置为处理所述资源故障信息；
    传递模块，设置为传递所述资源故障信息。
  13. 一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时实现所述权利要求1至11任一项中所述的方法的步骤。
  14. 一种电子装置，包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现所述权利要求1至11任一项中所述的方法的步骤。
PCT/CN2022/099485 2021-06-30 2022-06-17 故障处理方法、装置、存储介质及电子装置 WO2023273919A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110742587.3 2021-06-30
CN202110742587.3A CN115550131A (zh) 2021-06-30 2021-06-30 故障处理方法、装置、存储介质及电子装置

Publications (1)

Publication Number Publication Date
WO2023273919A1 true WO2023273919A1 (zh) 2023-01-05

Family

ID=84690721

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/099485 WO2023273919A1 (zh) 2021-06-30 2022-06-17 故障处理方法、装置、存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN115550131A (zh)
WO (1) WO2023273919A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006116896A1 (fr) * 2005-04-30 2006-11-09 Zte Corporation Méthode de restauration rapide pour ason
WO2010048772A1 (zh) * 2008-10-30 2010-05-06 中兴通讯股份有限公司 自动交换光网络连接修复方法及路由域
CN111757390A (zh) * 2019-03-29 2020-10-09 中兴通讯股份有限公司 一种支持网络切片的方法及网络管控系统
CN112583622A (zh) * 2019-09-30 2021-03-30 中兴通讯股份有限公司 故障事件信息的上报方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006116896A1 (fr) * 2005-04-30 2006-11-09 Zte Corporation Méthode de restauration rapide pour ason
WO2010048772A1 (zh) * 2008-10-30 2010-05-06 中兴通讯股份有限公司 自动交换光网络连接修复方法及路由域
CN111757390A (zh) * 2019-03-29 2020-10-09 中兴通讯股份有限公司 一种支持网络切片的方法及网络管控系统
CN112583622A (zh) * 2019-09-30 2021-03-30 中兴通讯股份有限公司 故障事件信息的上报方法及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NIU XIAO-BING: "Simulating transport plane resource alarms in ASON", OPTICAL COMMUNICATION TECHNOLOGY, no. 11, 1 January 2008 (2008-01-01), pages 5 - 7, XP055797278, DOI: 10.13921/j.cnki.issn1002-5561.2008.11.003 *
WAN ZHAOHUI, AO FALIANG, ZHANG PINCHUN: "Research on The Relationship Between LRM and Other Components in ASON", PHOTON TECHNOLOGY, no. 9, 30 September 2005 (2005-09-30), pages 177 - 180, XP093018402 *

Also Published As

Publication number Publication date
CN115550131A (zh) 2022-12-30

Similar Documents

Publication Publication Date Title
CN115460074B (zh) 用于分布式计算部署的网络控制器子集群
US11212181B2 (en) Cloud zone network analytics platform
US10601656B2 (en) Network element upgrade method and device
US10182105B2 (en) Policy based framework for application management in a network device having multiple packet-processing nodes
WO2020063876A1 (zh) Ue迁移方法、装置、系统及存储介质
US20080025227A1 (en) Method and system for handling fault messages in a network
US10819659B2 (en) Direct replying actions in SDN switches
US10530669B2 (en) Network service aware routers, and applications thereof
CN105162704A (zh) Overlay网络中组播复制的方法及装置
CN106059793A (zh) 一种基于平滑重启的路由信息处理方法及装置
WO2020057445A1 (zh) 一种通信系统、方法及装置
CN112653569B (zh) 一种设备管理的方法、装置及系统
CN109743250B (zh) 组播报文的传输方法、第一网络设备和第二网络设备
US10931529B2 (en) Terminal device management method, server, and terminal device for managing terminal devices in local area network
WO2023273919A1 (zh) 故障处理方法、装置、存储介质及电子装置
CN117061357A (zh) 一种基于虚拟专用网络的网络拓扑管理方法和系统
US8964596B1 (en) Network service aware routers, and applications thereof
CN113824595B (zh) 链路切换控制方法、装置和网关设备
US20050182763A1 (en) Apparatus and method for on-line upgrade using proxy objects in server nodes
CN114070784A (zh) 一种报文处理方法、装置、电子设备及存储介质
CN105049481A (zh) 一种支持多异构系统智能交互的方法
US20210320852A1 (en) Software-definable network service configuration method
EP2979395B1 (en) Methods and nodes for distribution of content to consumers
WO2017012315A1 (zh) 业务监听控制方法及装置
WO2024022209A1 (zh) 信息传输方法、装置、接入网设备及无线接入网控制器

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22831737

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE