WO2021063022A1 - 故障事件信息的上报方法及系统 - Google Patents

故障事件信息的上报方法及系统 Download PDF

Info

Publication number
WO2021063022A1
WO2021063022A1 PCT/CN2020/095195 CN2020095195W WO2021063022A1 WO 2021063022 A1 WO2021063022 A1 WO 2021063022A1 CN 2020095195 W CN2020095195 W CN 2020095195W WO 2021063022 A1 WO2021063022 A1 WO 2021063022A1
Authority
WO
WIPO (PCT)
Prior art keywords
event information
failure
point
fault
failure event
Prior art date
Application number
PCT/CN2020/095195
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 中兴通讯股份有限公司
Priority to EP20871094.7A priority Critical patent/EP4040726A4/en
Publication of WO2021063022A1 publication Critical patent/WO2021063022A1/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/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • 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

Definitions

  • the present disclosure relates to the field of communications, and in particular to a method and system for reporting fault event information.
  • MCC Management Control Continuum
  • SDN Software Defined Networking
  • EMS Element Management System
  • NMS Network Management System
  • the MCC system is used to realize unified management and control of transmission resources, and provide comprehensive management and control services for upper-level users.
  • functional modules provide functional services through interfaces.
  • faults In traditional network elements, faults generally need to be confirmed before being reported to the management plane or network management system.
  • the time required to confirm the occurrence of the fault is 2 ⁇ 0.5 seconds, and the time required to confirm the disappearance of the fault is 10 ⁇ 0.5 seconds.
  • Fault Reporting Management is an important function in the forwarding plane network element specified in ITU-T G.7710. It is mainly to register the faults generated in the network element and filter according to the fault event (Fault Event). Reporting) The information configuration will quickly report the faults that need to be reported to the specific MCC system, such as the SDN controller or the control plane.
  • Dynamic scheduling of connections is the basic function of the MCC system.
  • the MCC system needs to start the restoration of the connection.
  • it is not yet clear how to report fault event information in the MCC system.
  • the present disclosure provides a method and system for reporting failure event information, so as to at least solve the technical problem in the related art that how to report failure event information in the MCC system is not yet clear.
  • a method for reporting fault event information including:
  • the termination and adaptation executor TAP receives the first failure event information reported by the forwarding network element
  • the TAP converts the first failure event information into second failure event information according to the binding relationship between the subnet point and the forwarding point;
  • the TAP sends the second failure event information to the resource notification component RN;
  • the RN converts the second failure event information into third failure event information, and sends the third failure event information to the link resource manager LRM;
  • the LRM updates the operating state of the sub-network point according to the third failure event information.
  • a system for reporting fault event information including: a termination and adaptation executor TAP, a resource notification component RN, and a link resource manager LRM,
  • the TAP is configured to: receive the first failure event information reported by the forwarding network element; convert the first failure event information into the second failure event information according to the binding relationship between the subnet point and the forwarding point; and The second failure event information is sent to the resource notification component RN;
  • the RN is configured to convert the second failure event information into third failure event information, and send the third failure event information to the link resource manager LRM;
  • the LRM is configured to update the operating state of the sub-network point according to the third failure event information.
  • the termination and adaptation executor TAP receives the first fault event information reported by the forwarding network element; the TAP converts the first fault event information according to the binding relationship between the subnet point and the forwarding point Is the second failure event information; the TAP sends the second failure event information to the resource notification component RN; the RN converts the second failure event information into the third failure event information, and the third
  • the fault event information is sent to the link resource manager LRM; the LRM updates the operating state of the sub-network point according to the third fault event information. Therefore, it is possible to solve the technical problem of how to report the fault event information in the MCC system in the related technology, and realize the effect of clarifying the reporting process of the fault event information in the MCC system.
  • Fig. 1 is a structural block diagram of an MCC system according to an embodiment of the present disclosure
  • Fig. 2 is a flowchart of a method for reporting fault event information according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a network topology of an optional embodiment of the present disclosure.
  • Fig. 4 is a structural block diagram of a system for reporting fault event information according to an embodiment of the present disclosure.
  • ASON Automatically Switched Optical Network, Automatically Switched Optical Network, referred to as ASON;
  • LRM Link Resource Manager, Link Resources Manager, referred to as LRM for short;
  • Connection Controller Connection Controller, Connection Controller, referred to as CC for short;
  • Routing Controller Routing Controller, referred to as RC for short;
  • Termination and Adaptation Performer referred to as TAP for short;
  • Resource Notification component Resource Notification
  • RN Resource Notification
  • FEF Fault Event Filtering
  • FEF information Fault Event Filtering information
  • SDN Software Defined Networking
  • Subnetwork Point referred to as SNP for short;
  • FP Forwarding Point
  • FwEP Forwarding End Point
  • Fig. 1 is a structural block diagram of an MCC system according to an embodiment of the present disclosure.
  • the MCC system includes LRM, TAP, and RN.
  • Figure 1 shows the connection relationship between the MCC system and the forwarding plane network elements.
  • the forwarding resources of the forwarding plane need to be converted into resources that can be managed and controlled by the MCC system.
  • the forwarding resources of the forwarding plane can be represented by the forwarding point FP or the forwarding terminal point FwEP, where the forwarding terminal point is a forwarding point related to the path termination source or sink.
  • the resources used in the MCC system are represented by Subnetwork Point (SNP for short).
  • SNP Subnetwork Point
  • the relationship between FP/FwEP (ie FP or FwEP) and SNP is managed by TAP.
  • One SNP can be bound to one FP/FwEP; multiple SNPs can also be bound to one FP/FwEP to express multiple Two SNPs share the use of the FP/FwEP resource.
  • the connection maintained by the MCC system uses a series of SNPs from the perspective of management and control; from the perspective of the forwarding plane, it uses the FP/FwEP resources in the forwarding plane network elements.
  • Fig. 2 is a flowchart of a method for reporting fault event information according to an embodiment of the present disclosure. As shown in Fig. 2, the process includes the following steps:
  • Step S202 the termination and adaptation executor TAP receives the first fault event information reported by the forwarding network element
  • Step S204 The TAP converts the first failure event information into second failure event information according to the binding relationship between the subnet point and the forwarding point;
  • Step S206 the TAP sends the second failure event information to the resource notification component RN;
  • Step S208 The RN converts the second failure event information into third failure event information, and sends the third failure event information to the link resource manager LRM;
  • step S2010 the LRM updates the operating status of the sub-network point according to the third failure event information.
  • the termination and adaptation executor TAP receives the first failure event information reported by the forwarding network element; the TAP converts the first failure event information into the first failure event information according to the binding relationship between the subnet point and the forwarding point Two failure event information; the TAP sends the second failure event information to the resource notification component RN; the RN converts the second failure event information into third failure event information, and transfers the third failure event
  • the information is sent to the link resource manager LRM; the LRM updates the operating state of the sub-network point according to the third failure event information.
  • the first failure event information is used to indicate failure information on one or more forwarding points
  • the first failure event information includes one or more records, wherein each The record includes at least the following information: the identification, location, and operating status of the forwarding point, where the operating status includes: permission or prohibition.
  • a record in the first fault event information may include the identification, location, and operating status of a forwarding point, where the operating status includes: permitted or prohibited.
  • the operating status is allowed, which means that the forwarding point is allowed to be used; the operating status is prohibited, which means that the forwarding point is forbidden to use.
  • the first failure event information is used to indicate failure information on one or more forwarding points
  • the first failure event information includes one or more records, wherein each of the The record includes at least the following information: the identification, location, failure cause, and failure status of the forwarding point, where the failure status includes: occurrence of a failure or disappearance of the failure.
  • a record in the first failure event information may include the identification, location, failure cause, and failure status of a forwarding point.
  • the second failure event information is used to indicate failure information on one or more sub-network points
  • the second failure event information includes one or more records, wherein each The record includes at least the following information: the identification of the subnet point and the operating status, and the operating status includes: permission or prohibition.
  • a record in the second fault event information may include the identification of the subnet point and the operating status, where the operating status includes: permitted or prohibited.
  • the running status is allowed, it means that the subnet point is allowed to use; if the running status is prohibited, it means that the subnet point is forbidden to use.
  • the TAP converts the first failure event information into the second failure event information according to the binding relationship between the subnet point and the forwarding point, including:
  • the TAP determines the one or more sub-network points bound to the forwarding point in the first fault event information according to the binding relationship between the sub-network point and the forwarding point, and combines the one or more sub-network points As the sub-network point in the second fault event information; the TAP uses the operating state in the first fault information as the operating state in the second fault event information.
  • the TAP may determine one or more sub-network points bound to the forwarding point in the first failure event information according to the binding relationship between the forwarding point and the sub-network point, and Use the one or more sub-network points as the sub-network points in the second failure event information. And, the TAP uses the operating status of the forwarding point in the first failure event information as the operating status of one or more sub-network points bound to the forwarding point, and records the identification of each sub-network point and the operating status of the sub-network point in the first failure event information. 2. In a record in the fault event information.
  • the TAP converts the first failure event information into the second failure event information according to the binding relationship between the subnet point and the forwarding point, including:
  • the TAP determines the one or more sub-network points bound to the forwarding point in the first fault event information according to the binding relationship between the sub-network point and the forwarding point, and combines the one or more sub-network points Recorded in the second fault event information;
  • the TAP determines the operating state in the second failure event information according to the failure cause and the failure state in the first failure event information.
  • the TAP may determine the operating state in the second failure event information according to the failure cause and the failure state in the first failure event information. In an optional embodiment of the present disclosure, the TAP determines the operating status of one or more sub-network points bound to the forwarding point according to the failure cause and the failure state of the forwarding point in the first failure event information.
  • the TAP determining the operating state in the second failure event information according to the failure cause and the failure state in the first failure event information includes:
  • the fault status is that the fault disappears, it is determined that the operating status in the second fault event information is allowed.
  • the TAP in the case that the fault status of the forwarding point in the first fault event information is that the fault has occurred, the TAP will operate one or more subnet points bound to the forwarding point. The status is determined to be prohibited; when the failure status of the forwarding point in the first failure event information is that the failure disappears, the TAP determines the operating status of one or more subnet points bound to the forwarding point as permitted.
  • the third failure event information is used to indicate failure information on one or more sub-network points, and the third failure event information includes one or more records, wherein each record At least include the following information: the identification and operating status of the sub-network point, where the operating status includes: allow or prohibit;
  • the RN converting the second failure event information into third failure event information includes: using a sub-network point in the second failure event information as a sub-network point in the third failure event information, and converting The operating state in the second fault information is used as the operating state in the third fault information.
  • the RN uses the sub-network point in the second fault event information as the sub-network point in the third fault event information, and records the operating status of the sub-network point in the second fault event information in the third fault Event information.
  • the foregoing embodiment may also perform the following technical solutions:
  • the RN filters the second failure event information according to the failure suppression rule, and determines the second failure event information that needs to be reported in the second failure event information and the second failure event information that does not need to be reported;
  • the RN determines the sub-network point in the second fault event information that needs to be reported as the sub-network point in the third fault event information, and determines the operating state in the second fault event information that needs to be reported as The operating status in the third fault information.
  • a specific fault type can be filtered out by filtering the fault event information.
  • the fault messages belonging to the specific fault type are not confirmed by the fault, but Directly and quickly report, thereby speeding up the reporting process of fault messages within the MCC system, and saving the time it takes for the MCC system to restore the connection.
  • the RN filters the second fault event information according to the fault suppression rule, and determines the second fault event information that needs to be reported in the second fault event information, And after the second failure event information that does not need to be reported, only the second failure event information that needs to be reported is converted into the third failure event information.
  • the LRM updating the operating status of the sub-network point according to the third failure event information includes:
  • the LRM updates the operating status of the sub-network point managed by the LRM according to the operating status of the sub-network point in the third failure event information.
  • the LRM notifies a connection controller (Connection Controller, CC for short) that the link resource status corresponding to the subnet point has changed; the connection controller determines whether to initiate a connection recovery or reply.
  • a connection controller Connection Controller, CC for short
  • the LRM notifies a routing controller (Routing Controller, RC for short) that the link and topology state corresponding to the subnet point has changed; the routing controller determines whether to update the topology.
  • a routing controller Routing Controller, RC for short
  • LRM can notify the CC that the link resource status corresponding to the subnet point has changed, and the CC determines whether to start to restore or reply to the connection, for example, But it is not limited to determining whether to restore the connection or reuse the connection.
  • the forwarding point includes a forwarding terminal point.
  • Step 1 The TAP module receives the first failure event information reported by the forwarding network element
  • Fig. 3 is a schematic diagram of a network topology of an optional embodiment of the present disclosure.
  • four network elements A, B, C, and Z are interconnected through OTU2 links.
  • an ODU1 connection between port 8# (port 8) of point A (ie A network element) and port 8# of Z point can be established through an MCC system, such as an SDN controller or control plane, and the connection is established.
  • the binding relationship between the forwarding point and the resources used in the MCC system can be established in the SDN controller.
  • the binding relationship between the forwarding point and the resources used in the MCC system is pre-established. The following takes the pre-established binding relationship between FP and SNP as an example for description.
  • the forwarding point used by the ODU1 connection and the MCC system The binding relationship of the resources used in, that is, the binding relationship between FP and SNP is shown in Table 1.
  • SNP logo Bound FP resources SNP-A8 8#OTU2 port 1#ODU1 of A network element SNP-A1 1#ODU1 of port 1#OTU2 of network element A SNP-B1 1#ODU1 of port 1#OTU2 of network element B SNP-B2 2#OTU2 port 1#ODU1 of B network element SNP-Z1 Z network element 1#OTU2 port 1#ODU1 SNP-Z8 8#OUT2 port 1#ODU1 of Z network element
  • the MCC system (such as an SDN controller or control plane) can be configured with specific SNPs to report failures or prohibit reporting failures, for example, failures of all SNPs used by the connection
  • the quick report enable state is set to allow, that is, the forwarding point failure used by the connection is allowed to be quickly reported to the MCC system; other unused SNPs are not set to the failure quick report enable state, that is, the failure report enable state is forbidden.
  • the forwarding plane network element after detecting a failure (such as link interruption failure, ODUk channel failure, etc.), the forwarding plane network element reports the failure information (that is, the first failure event information in the above embodiment) to the TAP module of the MCC system .
  • a failure such as link interruption failure, ODUk channel failure, etc.
  • the faulty ODU-AIS ODU alarm indication signal
  • the MCC system can be reported to the MCC system.
  • the forwarding point bound to the subnet point SNP-Z1 is Z
  • the 1#ODU1 of the 1#OTU2 port of the network element that is, the No. 1 ODU1 in the OTU2 under the No. 1 port of the Z network element, which reflects the identification and location of the forwarding point
  • the first failure event information content is: 1#ODU1 (i.e. the identification and location of the forwarding point) of the 1#OTU2 port of the Z network element is prohibited (i.e. the operating state of the forwarding point).
  • each record in the first failure event information includes at least: forwarding point/forwarding terminal point identification and location, failure cause, and failure status, where the failure status includes: occurrence or disappearance, due to
  • the forwarding point bound to SNP-Z1 is 1#ODU1 of 1#OTU2 port of Z network element, so the content of the first failure event information is: 1#ODU1 of Z network element 1#OTU2 port 1#ODU1, ODU-AIS (i.e. failure Cause), the fault state is generated (that is, the fault occurred in the above-mentioned embodiment).
  • Step 2 The TAP module converts the first failure event information into second failure event information according to the binding relationship between the subnet point and the forwarding point/forwarding terminal point;
  • the binding relationship between the forwarding point/forwarding terminal point and the subnet point there may be only one SNP bound to one forwarding point, or multiple SNPs may be bound to one forwarding point, that is, these SNPs share the use of this forwarding point.
  • Resource obtain one or more subnet points bound to the forwarding point/forwarding terminal point in the first fault event information, and update it to the second fault event information.
  • Step 3 The TAP module transmits the second fault event information to the RN module;
  • Step 4 The RN module converts the second fault event information into the third fault event information and transmits it to the LRM module;
  • Step 5 The LRM module updates the operating status of the sub-network point according to the third fault event information.
  • the first failure event information indicates failure information on one or more forwarding points/forwarding terminal points, and may include one or more records, and each record includes at least: forwarding point/forwarding terminal point identification and location, Running status, where running status includes: allow or prohibit.
  • the first failure event information indicates the failure information on one or more forwarding points/forwarding terminal points, and may include one or more records, and each record includes at least: forwarding point/forwarding
  • the identification and location of the terminal point, the cause of the failure, the failure state, and the failure state include: occurrence or disappearance.
  • the second fault event information represents the fault information on one or more sub-network points, and may include one or more records, and each record includes at least: the sub-network point identifier and the operating status, where the operating status includes : Allow or prohibit.
  • the TAP module obtains the binding of the forwarding point/forwarding terminal point in the first fault event information according to the binding relationship between the forwarding point/forwarding terminal point and the subnet point.
  • Set one or more sub-network points and update the one or more sub-network points in the second failure event information (for example, but not limited to, record the one or more sub-network points in the record in the second failure event information);
  • the operating status in the second fault event information can be determined or updated according to the following steps:
  • the fault cause and fault status in the first fault event information to the operating status in the second fault event information, for example but not limited to, if the fault status is occurrence (that is, the fault occurrence in the above embodiment), the operating status is Prohibited; if the fault status is disappearing (that is, the fault message in the above embodiment), the running status is permitted.
  • the third failure event information indicates failure information on one or more sub-network points, and may include one or more records, and each record includes at least: sub-network point identification and operating status, where the operating status includes: allowed Or prohibit.
  • the RN module converts the sub-network point in the second fault event information to the sub-network point in the third fault event information (that is, the RN module converts the sub-network point in the second fault event information
  • the sub-network point is used as the sub-network point in the third fault event information), and accordingly, the operating state in the second fault information is equivalently converted to the operating state in the third fault information.
  • the RN module filters out the second failure event information that does not need to be reported according to the failure suppression rules; and removes the second failure event information that is not filtered out of the second failure event information.
  • the sub-network point in the fault event information is equivalently converted to the sub-network point in the third fault event information, and accordingly, the operating state in the second fault event information that is not filtered in the second fault information is equivalently converted into the third fault information The operating status of the.
  • the LRM module informs the CC module (that is, the connection controller in the above embodiment) that the link resource status corresponding to the subnet point has changed, and the CC module can determine whether to initiate recovery or reply; and, the LRM module informs the RC For the module (that is, the routing controller in the above-mentioned embodiment), the link and topology state corresponding to the subnet point changes, and the RC module can determine whether to start the topology update.
  • the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solutions of the embodiments of the present disclosure can be embodied in the form of a software product in essence or a part that contributes to the prior art.
  • the computer software product is stored in a storage medium (such as ROM/RAM, magnetic A disc or an optical disc) includes several instructions to make a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) execute the methods described in the various embodiments of the present disclosure.
  • a system for reporting fault event information is also provided.
  • the system is used to implement the above-mentioned embodiments and preferred implementations, and what has been explained will not be repeated.
  • the term "module" can implement a combination of software and/or hardware with predetermined functions.
  • the devices described in the following embodiments are preferably implemented by software, implementation by hardware or a combination of software and hardware is also possible and conceived.
  • Fig. 4 is a structural block diagram of a system for reporting fault event information according to an embodiment of the present disclosure. As shown in Fig. 4, the system includes:
  • Termination and adaptation executor TAP 402 resource notification component RN 404, link resource manager LRM 406,
  • the TAP 402 is configured to: receive the first failure event information reported by the forwarding network element; convert the first failure event information into the second failure event information according to the binding relationship between the subnet point and the forwarding point; and Sending the second failure event information to the resource notification component RN;
  • the RN 404 is configured to convert the second failure event information into third failure event information, and send the third failure event information to the link resource manager LRM;
  • the LRM 406 is set to update the operating status of the sub-network point according to the third failure event information.
  • the termination and adaptation executor TAP receives the first fault event information reported by the forwarding network element; the TAP converts the first fault event information into Second failure event information; the TAP sends the second failure event information to the resource notification component RN; the RN converts the second failure event information into third failure event information, and transfers the third failure event information
  • the event information is sent to the link resource manager LRM; the LRM updates the operating state of the sub-network point according to the third failure event information.
  • the first failure event information is used to indicate failure information on one or more forwarding points
  • the first failure event information includes one or more records, wherein each The record includes at least the following information: the identification, location, and operating status of the forwarding point, where the operating status includes: permission or prohibition.
  • the first failure event information is used to indicate failure information on one or more forwarding points
  • the first failure event information includes one or more records, wherein each of the The record includes at least the following information: the identification, location, failure cause, and failure status of the forwarding point, where the failure status includes: occurrence of a failure or disappearance of the failure.
  • each of the above modules can be implemented by software or hardware.
  • it can be implemented in the following manner, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination.
  • the forms are located in different processors.
  • modules or steps of the above-mentioned embodiments of the present disclosure can be implemented by a general computing device, and they can be concentrated on a single computing device, or distributed among multiple computing devices.
  • they can be implemented by the program code executable by the computing device, so that they can be stored in the storage device for execution by the computing device, and in some cases, they can be different from here
  • the steps shown or described are performed in the order of, or they are respectively fabricated into individual integrated circuit modules, or multiple modules or steps of them are fabricated into a single integrated circuit module to achieve. In this way, the embodiments of the present disclosure are not limited to any specific combination of hardware and software.
  • the termination and adaptation executor TAP receives the first fault event information reported by the forwarding network element; the TAP converts the first fault event information according to the binding relationship between the subnet point and the forwarding point Is the second failure event information; the TAP sends the second failure event information to the resource notification component RN; the RN converts the second failure event information into the third failure event information, and the third
  • the fault event information is sent to the link resource manager LRM; the LRM updates the operating state of the sub-network point according to the third fault event information. Therefore, it is possible to solve the technical problem of how to report the fault event information in the MCC system in the related technology, and realize the effect of clarifying the reporting process of the fault event information in the MCC system.

Landscapes

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

Abstract

本公开实施例提供了一种故障事件信息的上报方法及系统，上述方法包括：终结和适配执行器TAP接收转发网元上报的第一故障事件信息；所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；所述TAP将所述第二故障事件信息发送给资源通告组件RN；所述RN将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；所述LRM根据所述第三故障事件信息更新所述子网点的运行状态。通过本公开实施例，解决了相关技术中，尚未明确如何在MCC系统中进行故障事件信息的上报的技术问题，进而达到了在MCC系统中明确故障事件信息的上报流程的效果。

Description

故障事件信息的上报方法及系统 技术领域
本公开涉及通信领域，具体而言，涉及一种故障事件信息的上报方法及系统。
背景技术
管理控制融合(Management Control Continuum，简称为MCC)将管理功能与控制功能融合在一起，例如，软件定义网络(Software Defined Networking，简称为SDN)控制器、网元管理系统(Element Management System，简称为EMS)、网络管理系统(Network Management System，简称为NMS)以及控制平面都是MCC系统实例。MCC系统用于实现对传送资源的统一管理和控制，为上层用户提供管理控制综合服务。在MCC系统中，功能模块通过接口提供功能服务。
在传统网元中，故障(Fault)一般需要经过确认后才上报给管理平面或网络管理系统。确认故障产生所需要的时间是2±0.5秒，确认故障消失所需要的时间是10±0.5秒。通过这样的延时确认机制，能够在转发面故障频繁产生或消失时，减少上报给管理平面的故障消息。
故障上报管理(Fault Reporting Management，简称为FRM)是ITU-T G.7710中规范的转发面网元中的重要功能，主要是对网元内产生的故障进行注册，根据故障事件过滤(Fault Event Reporting)信息配置将需要上报的故障快速报给具体的MCC系统，如SDN控制器或控制平面。
连接的动态调度是MCC系统的基本功能，当转发面中的转发资源出现故障影响到连接时，需要MCC系统启动对连接的恢复。而相关技术中，尚未明确如何在MCC系统中进行故障事件信息的上报。
针对相关技术中，尚未明确如何在MCC系统中进行故障事件信息的上报的技术问题，尚未提出解决方案。
发明内容
本公开提供了一种故障事件信息的上报方法及系统，以至少解决相关技术中尚未明确如何在MCC系统中进行故障事件信息的上报的技术问题。
根据本公开的一个实施例，提供了一种故障事件信息的上报方法，包括：
终结和适配执行器TAP接收转发网元上报的第一故障事件信息；
所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；
所述TAP将所述第二故障事件信息发送给资源通告组件RN；
所述RN将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；
所述LRM根据所述第三故障事件信息更新所述子网点的运行状态。
根据本公开的另一个实施例，提供了一种故障事件信息的上报系统，包括：终结和适配执行器TAP，资源通告组件RN，链路资源管理器LRM，
所述TAP，设置为：接收转发网元上报的第一故障事件信息；根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；以及将所述第二故障事件信息发送给资源通告组件RN；
所述RN，设置为将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；
所述LRM，设置为根据所述第三故障事件信息更新所述子网点的运行状态。
通过本公开实施例，终结和适配执行器TAP接收转发网元上报的第一故障事件信息；所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；所述TAP将所述第二故障事件信息发送给资源通告组件RN；所述RN将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管 理器LRM；所述LRM根据所述第三故障事件信息更新所述子网点的运行状态。因此，可以解决相关技术中，尚未明确如何在MCC系统中进行故障事件信息的上报的技术问题，实现了在MCC系统中明确故障事件信息的上报流程的效果。
附图说明
此处所说明的附图用来提供对本公开实施例的进一步理解，构成本公开实施例的一部分，本公开的示意性实施例及其说明用于解释本公开实施例，并不构成对本公开实施例的不当限定。在附图中：
图1是根据本公开实施例的一种MCC系统的结构框图；
图2是根据本公开实施例的故障事件信息的上报方法的流程图；
图3为本公开一可选实施例的网络拓扑示意图；
图4是根据本公开实施例的故障事件信息的上报系统的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开实施例。需要说明的是，在不冲突的情况下，本公开中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开实施例的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本公开实施例中涉及到的技术术语和对应的英文全称以及缩写如下：
自动交换光网络，Automatically Switched Optical Network，简称为ASON；
链路资源管理器，Link Resources Manager，简称为LRM；
连接控制器，Connection Controller，简称为CC；
路由控制器，Routing Controller，简称为RC；
终结和适配执行器，Termination and Adaptation Performer，简称为TAP；
资源通告组件，Resource Notification，简称为RN；
故障事件过滤，Fault Event Filtering，简称为FEF；
故障事件过滤信息，Fault Event Filtering information，简称为FEF information；
软件定义网络，Software Defined Networking，简称为SDN；
子网点，Subnetwork Point，简称为SNP；
转发点，Forwarding Point，简称为FP；
转发终端点，Forwarding End Point，简称为FwEP；
实施例1
图1是根据本公开实施例的一种MCC系统的结构框图。如图1所示，MCC系统中包括了LRM、TAP、RN，图1中显示了MCC系统与转发面网元的连接关系。
转发面的转发资源(例如，时隙、带宽标签、端口均可以作为转发面的转发资源)需要转换为MCC系统能够管控的资源。转发面的转发资源可以用转发点FP或转发终端点FwEP来表示，其中，转发终端点是一种与路径终结源或宿相关的转发点。MCC系统中使用的资源用子网点(Subnetwork Point，简称为SNP)来表示。FP/FwEP(即FP或FwEP)与SNP之间的关系由TAP管理，可以将一个SNP绑定到一个FP/FwEP上；也可以将多个SNP绑定到一个FP/FwEP上，以表示多个SNP共享使用该FP/FwEP资源。也就是说，MCC系统维护的连接，从管控角度来看，是使用了一系列的SNP；而从转发面的角度来看，是使用了转发面网元中的FP/FwEP资源。
本公开实施例提供了一种故障事件信息的上报方法，可选地，作为一种可选的实施方式，上述故障事件信息的上报方法可以运行于图1所示的网络架构上。图2是根据本公开实施例的故障事件信息的上报方法的流程 图，如图2所示，该流程包括如下步骤：
步骤S202，终结和适配执行器TAP接收转发网元上报的第一故障事件信息；
步骤S204，所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；
步骤S206，所述TAP将所述第二故障事件信息发送给资源通告组件RN；
步骤S208，所述RN将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；
步骤S2010，所述LRM根据所述第三故障事件信息更新所述子网点的运行状态。
通过上述步骤，终结和适配执行器TAP接收转发网元上报的第一故障事件信息；所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；所述TAP将所述第二故障事件信息发送给资源通告组件RN；所述RN将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；所述LRM根据所述第三故障事件信息更新所述子网点的运行状态。解决了相关技术中，尚未明确如何在MCC系统中进行故障事件信息的上报的技术问题，实现了在MCC系统中明确故障事件信息的上报流程的效果。以及进一步地，增强了MCC系统对转发面故障的处理能力，进而提高了MCC系统的故障恢复效率。
在本公开的一可选实施例中，所述第一故障事件信息用于表示一个或多个转发点上的故障信息，所述第一故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：转发点的标识、位置以及运行状态，其中，所述运行状态包括：允许或禁止。
作为一种可选的实施方式，第一故障事件信息中的一条记录可以包括一个转发点的标识、位置以及运行状态，其中，运行状态包括：允许或禁 止。可选地，运行状态为允许，表示该转发点被允许使用；运行状态为禁止，表示该转发点被禁止使用。
作为一种可选的实施方式，所述第一故障事件信息用于表示一个或多个转发点上的故障信息，所述第一故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：转发点的标识、位置、故障原因以及故障状态，其中，所述故障状态包括：故障产生或故障消失。
可选地，在上述实施例中，第一故障事件信息中的一条记录可以包括一个转发点的标识、位置、故障原因以及故障状态。
在本公开的一可选实施例中，所述第二故障事件信息用于表示一个或多个子网点上的故障信息，所述第二故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：子网点的标识以及运行状态，所述运行状态包括：允许或禁止。
作为一种可选的实施方式，在上述实施例中，第二故障事件信息中的一条记录可以包括子网点的标识以及运行状态，其中，运行状态包括：允许或禁止。可选地，运行状态为允许，表示该子网点被允许使用；运行状态为禁止，表示该子网点被禁止使用。
在上述实施例中，所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息，包括：
所述TAP根据所述子网点与转发点之间的绑定关系，确定与所述第一故障事件信息中的转发点绑定的所述一个或多个子网点，将所述一个或多个子网点作为所述第二故障事件信息中的子网点；所述TAP将所述第一故障信息中的运行状态作为所述第二故障事件信息中的运行状态。
在上述实施例中，作为一种可选的实施方式，TAP可以根据转发点与子网点的绑定关系，确定出与第一故障事件信息中的转发点绑定的一个或多个子网点，并将该一个或多个子网点作为第二故障事件信息中的子网点。以及，TAP将第一故障事件信息中的转发点的运行状态作为与该转发点绑定的一个或多个子网点的运行状态，并将每个子网点的标识以及该子网点 的运行状态记录在第二故障事件信息中的一条记录中。
作为一种可选的实施方式，在上述实施例中，所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息，包括：
所述TAP根据所述子网点与转发点之间的绑定关系，确定与所述第一故障事件信息中的转发点绑定的所述一个或多个子网点，将所述一个或多个子网点记录到所述第二故障事件信息中；
所述TAP根据所述第一故障事件信息中的故障原因和故障状态确定所述第二故障事件信息中的运行状态。
其中，TAP可以根据第一故障事件信息中的故障原因和故障状态确定第二故障事件信息中运行状态。在本公开的一可选实施例中，TAP根据第一故障事件信息中的转发点的故障原因以及故障状态，确定出与该转发点绑定的一个或多个子网点的运行状态。
其中，在上述实施例中，所述TAP根据所述第一故障事件信息中的故障原因和故障状态确定所述第二故障事件信息中的运行状态，包括：
在所述故障状态为故障产生的情况下，确定所述第二故障事件信息中的运行状态为禁止；
在所述故障状态为故障消失的情况下，确定所述第二故障事件信息中的运行状态为允许。
需要说明的是，作为一种可选的实施方式，在第一故障事件信息中的转发点的故障状态为故障产生的情况下，TAP将与该转发点绑定的一个或多个子网点的运行状态确定为禁止；在第一故障事件信息中的转发点的故障状态为故障消失的情况下，TAP将与该转发点绑定的一个或多个子网点的运行状态确定为允许。
在本公开的上述实施例中，所述第三故障事件信息用于表示一个或多个子网点上的故障信息，所述第三故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：子网点的标识、运行状态，所述运 行状态包括：允许或禁止；
其中，所述RN将所述第二故障事件信息转换为第三故障事件信息，包括：将所述第二故障事件信息中的子网点作为所述第三故障事件信息中的子网点，以及将所述第二故障信息中的运行状态作为所述第三故障信息中的运行状态。
作为一种可选的实施方式，RN将第二故障事件信息中的子网点作为第三故障事件信息中的子网点，并将第二故障事件信息中的子网点的运行状态记录在第三故障事件信息中。
此外，在所述RN将所述第二故障事件信息转换为第三故障事件信息之前，上述实施例还可以执行以下技术方案：
所述RN根据故障抑制规则对所述第二故障事件信息进行过滤，确定所述第二故障事件信息中需要上报的第二故障事件信息，以及不需要上报的第二故障事件信息；
所述RN将所述需要上报的第二故障事件信息中的子网点确定为所述第三故障事件信息中的子网点，以及将所述需要上报的第二故障事件信息中的运行状态确定为所述第三故障信息中的运行状态。
若MCC系统基于经过确认后的故障来触发连接的恢复，则延长了故障恢复所花费的时间，影响了连接所承载业务的质量。为了加速基于MCC系统的连接恢复，在本公开一可选实施例中，可以通过对故障事件信息进行过滤筛选出特定的故障类型，属于该特定的故障类型的故障消息不经过故障确认，而是直接快速上报，从而加速了MCC系统内部对故障消息的上报流程，节省了MCC系统恢复连接所花费的时间。
需要说明的是，在本公开的上述实施例中，RN根据故障抑制规则对所述第二故障事件信息进行过滤，在确定出所述第二故障事件信息中需要上报的第二故障事件信息，以及不需要上报的第二故障事件信息之后，仅将需要上报的第二故障事件信息转换为第三故障事件信息。
上述实施例中，所述LRM根据所述第三故障事件信息更新所述子网 点的运行状态，包括：
所述LRM根据所述第三故障事件信息中的子网点的运行状态，更新由所述LRM管理的所述子网点的运行状态。
此外，上述实施例还可以执行以下技术方案：
所述LRM通知连接控制器(Connection Controller，简称为CC)所述子网点对应的链路资源状态发生改变；所述连接控制器判断是否启动对连接进行恢复或回复。
所述LRM通知路由控制器(Routing Controller，简称为RC)所述子网点对应的链路和拓扑状态发生改变；所述路由控制器判断是否对拓扑进行更新。
作为一种可选的实施方式，在子网点的运行状态发生改变的情况下，LRM可以通知CC该子网点对应的链路资源状态发生了改变，CC判断是否启动对连接进行恢复或回复，例如但不限于，判断是否对该连接进行恢复，或是重新使用该连接。
可选地，在上述实施例中，转发点包括转发终端点。
以下结合一示例对上述的故障事件信息的上报方法行解释说明，但不用于限定本公开实施例的技术方案，本公开示例的技术方案如下：
步骤1，TAP模块收到转发网元上报的第一故障事件信息；
图3为本公开一可选实施例的网络拓扑示意图。如图3所示，在该网络拓扑中，A、B、C、Z四个网元通过OTU2链路互联。在这个网络上，可以通过MCC系统，如SDN控制器或控制平面建立A点(即A网元)的8#端口(即8号端口)与Z点8#端口之间的ODU1连接，连接建立后，即可以在SDN控制器中建立转发点与MCC系统中使用的资源的绑定关系。在本公开实施例中，预先建立了转发点与MCC系统中使用的资源的绑定关系，以下以预先建立FP与SNP的绑定关系为例进行说明，上述ODU1连接使用的转发点与MCC系统中使用的资源的绑定关系，也即FP与SNP的绑定关系如表1所示。
表1
SNP标识 绑定的FP资源
SNP-A8 A网元的8#OTU2端口的1#ODU1
SNP-A1 A网元的1#OTU2端口的1#ODU1
SNP-B1 B网元的1#OTU2端口的1#ODU1
SNP-B2 B网元的2#OTU2端口的1#ODU1
SNP-Z1 Z网元的1#OTU2端口的1#ODU1
SNP-Z8 Z网元的8#OUT2端口的1#ODU1
为了加速该ODU1连接的故障恢复，在本公开实施例中，MCC系统(如SDN控制器或控制平面)可配置具体的SNP可以上报故障或禁止上报故障，例如，该连接使用的所有SNP的故障快报使能状态都置为允许，即该连接使用的转发点故障允许快速上报给MCC系统；其他未使用的SNP上没有设置故障快报使能状态，即故障快报使能状态为禁止。
在上述实施例中，转发面网元检测到故障(如链路中断故障、ODUk通道故障等)后，将故障信息(即上述实施例中的第一故障事件信息)上报给MCC系统的TAP模块。
例如，网元B与网元Z之间的链路中断，会导致链路层故障以及ODUk通道故障。在本公开实施例中，SN标识为子网点SNP-Z1的故障ODU-AIS(ODU告警指示信号)可上报给MCC系统。
作为一种可选的实施方式，当第一故障事件信息中的每条记录至少包含：转发点/转发终端点标识及位置、运行状态时，由于子网点SNP-Z1绑定的转发点为Z网元的1#OTU2端口的1#ODU1(即Z网元的1号端口下的OTU2中的1号ODU1，其中反映出了转发点的标识以及位置)，因此第一故障事件信息内容为：Z网元的1#OTU2端口的1#ODU1(即转发点的标识以及位置)，禁止(即转发点的运行状态)。
作为一种可选的实施方式，当第一故障事件信息中的每条记录至少包 含：转发点/转发终端点标识及位置，故障原因，故障状态，其中故障状态包括：产生或消失时，由于SNP-Z1绑定的转发点为Z网元的1#OTU2端口的1#ODU1，因此第一故障事件信息内容为：Z网元的1#OTU2端口的1#ODU1，ODU-AIS(即故障原因)，故障状态为产生(即上述实施例中的故障产生)。
步骤2，TAP模块根据子网点与转发点/转发终端点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；
其中，转发点/转发终端点与子网点的绑定关系中，可能只有一个SNP绑定到一个转发点，也可能有多个SNP绑定到一个转发点，即这些SNP共享使用了这个转发点资源，获得所述第一故障事件信息中转发点/转发终端点所绑定的一个或多个子网点，更新到第二故障事件信息中。
步骤3，TAP模块将所述第二故障事件信息传递给RN模块；
步骤4，RN模块将所述第二故障事件信息转换为第三故障事件信息并传递给LRM模块；
步骤5，LRM模块根据第三故障事件信息更新子网点的运行状态。
可选地，第一故障事件信息，表示一个或多个转发点/转发终端点上的故障信息，可包含一条或多条记录，每条记录至少包含：转发点/转发终端点标识及位置，运行状态，其中运行状态包括：允许或禁止。
作为另一种可选的实施方式，第一故障事件信息，表示一个或多个转发点/转发终端点上的故障信息，可包含一条或多条记录，每条记录至少包含：转发点/转发终端点标识及位置，故障原因，故障状态，故障状态包括：产生或消失。
在本公开的上述实施例中，第二故障事件信息表示一个或多个子网点上的故障信息，可包含一条或多条记录，每条记录至少包含：子网点标识，运行状态，其中运行状态包括：允许或禁止。
需要说明的是，在本公开的上述实施例中，所述TAP模块根据转发点/转发终端点与子网点的绑定关系，获得所述第一故障事件信息中转发点 /转发终端点所绑定的一个或多个子网点，并将该一个或多个子网点更新到第二故障事件信息中(例如但不限于，将该一个或多个子网点记录到第二故障事件信息中的记录中)；
其中，可以按照以下步骤确定或更新第二故障事件信息中的运行状态：
将第一故障信息中的运行状态等同转换为第二故障信息中的运行状态；或，
将第一故障事件信息中的故障原因和故障状态转换为第二故障事件信息中的运行状态，例如但不限于，若故障状态为产生(即上述实施例中的故障产生)，则运行状态为禁止；若故障状态为消失(即上述实施例中的故障消息)，则运行状态为允许。
可选地，所述第三故障事件信息，表示一个或多个子网点上的故障信息，可包含一条或多条记录，每条记录至少包含：子网点标识，运行状态，其中运行状态包括：允许或禁止。
作为一种可选的实施方式，RN模块将所述第二故障事件信息中的子网点等同转换到第三故障事件信息中的子网点(即，RN模块将所述第二故障事件信息中的子网点作为第三故障事件信息中的子网点)，相应的，将第二故障信息中的运行状态等同转换为第三故障信息中的运行状态。
此外，本公开的上述实施例还可以执行以下技术方案：RN模块根据故障抑制规则过滤掉不需要上报的第二故障事件信息；并将所述第二故障事件信息中未被过滤掉的第二故障事件信息中的子网点等同转换到第三故障事件信息中的子网点，相应的，将第二故障信息中未被过滤的第二故障事件信息中的运行状态等同转换为第三故障信息中的运行状态。
此外，可选地，LRM模块通知CC模块(即上述实施例中的连接控制器)，子网点对应的链路资源状态发生改变，CC模块可判断是否启动恢复或回复；以及，LRM模块通知RC模块(即上述实施例中的路由控制器)，子网点对应的链路和拓扑状态发生改变，RC模块可判断是否启动拓扑更新。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
实施例2
在本实施例中还提供了一种故障事件信息的上报系统，该系统用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图4是根据本公开实施例的故障事件信息的上报系统的结构框图，如图4所示，该系统包括：
终结和适配执行器TAP 402，资源通告组件RN 404，链路资源管理器LRM 406，
所述TAP 402，设置为：接收转发网元上报的第一故障事件信息；根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；以及将所述第二故障事件信息发送给资源通告组件RN；
所述RN 404，设置为将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；
所述LRM 406，设置为根据所述第三故障事件信息更新所述子网点的运行状态。
通过上述实施例，终结和适配执行器TAP接收转发网元上报的第一故障事件信息；所述TAP根据子网点与转发点之间的绑定关系，将所述 第一故障事件信息转换为第二故障事件信息；所述TAP将所述第二故障事件信息发送给资源通告组件RN；所述RN将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；所述LRM根据所述第三故障事件信息更新所述子网点的运行状态。解决了相关技术中，尚未明确如何在MCC系统中进行故障事件信息的上报的技术问题，实现了在MCC系统中明确故障事件信息的上报流程的效果。
在本公开的一可选实施例中，所述第一故障事件信息用于表示一个或多个转发点上的故障信息，所述第一故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：转发点的标识、位置以及运行状态，其中所述运行状态包括：允许或禁止。
作为一种可选的实施方式，所述第一故障事件信息用于表示一个或多个转发点上的故障信息，所述第一故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：转发点的标识、位置、故障原因以及故障状态，其中，所述故障状态包括：故障产生或故障消失。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开实施例的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开实施例不限 制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开实施例，对于本领域的技术人员来说，本公开实施例可以有各种更改和变化。凡在本公开实施例的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开实施例的保护范围之内。
工业实用性
通过本公开实施例，终结和适配执行器TAP接收转发网元上报的第一故障事件信息；所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；所述TAP将所述第二故障事件信息发送给资源通告组件RN；所述RN将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；所述LRM根据所述第三故障事件信息更新所述子网点的运行状态。因此，可以解决相关技术中，尚未明确如何在MCC系统中进行故障事件信息的上报的技术问题，实现了在MCC系统中明确故障事件信息的上报流程的效果。

Claims (17)

  1. 一种故障事件信息的上报方法，包括：
    终结和适配执行器TAP接收转发网元上报的第一故障事件信息；
    所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；
    所述TAP将所述第二故障事件信息发送给资源通告组件RN；
    所述RN将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；
    所述LRM根据所述第三故障事件信息更新所述子网点的运行状态。
  2. 根据权利要求1所述的方法，其中，所述第一故障事件信息用于表示一个或多个转发点上的故障信息，所述第一故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：转发点的标识、位置以及运行状态，其中，所述运行状态包括：允许或禁止。
  3. 根据权利要求1所述的方法，其中，所述第一故障事件信息用于表示一个或多个转发点上的故障信息，所述第一故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：转发点的标识、位置、故障原因以及故障状态，其中，所述故障状态包括：故障产生或故障消失。
  4. 根据权利要求2所述的方法，其中，所述第二故障事件信息用于表示一个或多个子网点上的故障信息，所述第二故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：子网点的标识以及运行状态，所述运行状态包括：允许或禁止。
  5. 根据权利要求4所述的方法，其中，所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息，包括：
    所述TAP根据所述子网点与转发点之间的绑定关系，确定与所述 第一故障事件信息中的转发点绑定的所述一个或多个子网点，将所述一个或多个子网点作为所述第二故障事件信息中的子网点；
    所述TAP将所述第一故障信息中的运行状态作为所述第二故障事件信息中的运行状态。
  6. 根据权利要求3所述的方法，其中，所述第二故障事件信息用于表示一个或多个子网点上的故障信息，所述第二故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：子网点的标识以及运行状态，所述运行状态包括：允许或禁止。
  7. 根据权利要求6所述的方法，其中，所述TAP根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息，包括：
    所述TAP根据所述子网点与转发点之间的绑定关系，确定与所述第一故障事件信息中的转发点绑定的所述一个或多个子网点，将所述一个或多个子网点记录到所述第二故障事件信息中；
    所述TAP根据所述第一故障事件信息中的故障原因和故障状态确定所述第二故障事件信息中的运行状态。
  8. 根据权利要求7所述的方法，其中，所述TAP根据所述第一故障事件信息中的故障原因和故障状态确定所述第二故障事件信息中的运行状态，包括：
    在所述故障状态为故障产生的情况下，确定所述第二故障事件信息中的运行状态为禁止；
    在所述故障状态为故障消失的情况下，确定所述第二故障事件信息中的运行状态为允许。
  9. 根据权利要求1所述的方法，其中：所述第三故障事件信息用于表示一个或多个子网点上的故障信息，所述第三故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：子网点的标识、运行状态，所述运行状态包括：允许或禁止；
    其中，所述RN将所述第二故障事件信息转换为第三故障事件信息，包括：
    将所述第二故障事件信息中的子网点作为所述第三故障事件信息中的子网点，以及将所述第二故障信息中的运行状态作为所述第三故障信息中的运行状态。
  10. 根据权利要求1所述的方法，其中，在所述RN将所述第二故障事件信息转换为第三故障事件信息之前，所述方法还包括：
    所述RN根据故障抑制规则对所述第二故障事件信息进行过滤，确定所述第二故障事件信息中需要上报的第二故障事件信息，以及不需要上报的第二故障事件信息；
    所述RN将所述需要上报的第二故障事件信息中的子网点确定为所述第三故障事件信息中的子网点，以及将所述需要上报的第二故障事件信息中的运行状态确定为所述第三故障信息中的运行状态。
  11. 根据权利要求1所述的方法，其中，所述LRM根据所述第三故障事件信息更新所述子网点的运行状态，包括：
    所述LRM根据所述第三故障事件信息中的子网点的运行状态，更新由所述LRM管理的所述子网点的运行状态。
  12. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述LRM通知连接控制器所述子网点对应的链路资源状态发生改变；
    所述连接控制器判断是否启动对连接进行恢复或回复。
  13. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述LRM通知路由控制器所述子网点对应的链路和拓扑状态发生改变；
    所述路由控制器判断是否对拓扑进行更新。
  14. 根据权利要求1-13中任一项所述的方法，其中，所述转发点 包括转发终端点。
  15. 一种故障事件信息的上报系统，包括：终结和适配执行器TAP，资源通告组件RN，链路资源管理器LRM，
    所述TAP，设置为：接收转发网元上报的第一故障事件信息；根据子网点与转发点之间的绑定关系，将所述第一故障事件信息转换为第二故障事件信息；以及将所述第二故障事件信息发送给资源通告组件RN；
    所述RN，设置为将所述第二故障事件信息转换为第三故障事件信息，并将所述第三故障事件信息发送给链路资源管理器LRM；
    所述LRM，设置为根据所述第三故障事件信息更新所述子网点的运行状态。
  16. 根据权利要求15所述的系统，其中，所述第一故障事件信息用于表示一个或多个转发点上的故障信息，所述第一故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：转发点的标识、位置以及运行状态，其中所述运行状态包括：允许或禁止。
  17. 根据权利要求15所述的系统，其中，所述第一故障事件信息用于表示一个或多个转发点上的故障信息，所述第一故障事件信息包括一条或多条记录，其中，每条所述记录至少包括以下信息：转发点的标识、位置、故障原因以及故障状态，其中，所述故障状态包括：故障产生或故障消失。
PCT/CN2020/095195 2019-09-30 2020-06-09 故障事件信息的上报方法及系统 WO2021063022A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20871094.7A EP4040726A4 (en) 2019-09-30 2020-06-09 PROCEDURE AND SYSTEM FOR REPORTING FAULT EVENT INFORMATION

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910944260.7A CN112583622B (zh) 2019-09-30 2019-09-30 故障事件信息的上报方法及系统
CN201910944260.7 2019-09-30

Publications (1)

Publication Number Publication Date
WO2021063022A1 true WO2021063022A1 (zh) 2021-04-08

Family

ID=75116675

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/095195 WO2021063022A1 (zh) 2019-09-30 2020-06-09 故障事件信息的上报方法及系统

Country Status (3)

Country Link
EP (1) EP4040726A4 (zh)
CN (1) CN112583622B (zh)
WO (1) WO2021063022A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115550131A (zh) * 2021-06-30 2022-12-30 中兴通讯股份有限公司 故障处理方法、装置、存储介质及电子装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100239249A1 (en) * 2007-11-16 2010-09-23 Zte Corporation Tap, lrm, resource state control system and method
CN108712207A (zh) * 2018-04-17 2018-10-26 烽火通信科技股份有限公司 一种链路和业务的管理方法及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101360349B (zh) * 2008-09-12 2011-01-19 中兴通讯股份有限公司 一种有阻边界节点及有阻边界节点间建立连接的方法
JP5829183B2 (ja) * 2012-07-02 2015-12-09 Kddi株式会社 経路制御プロトコルに基づいて障害ノード装置又は障害リンクをリアルタイムに検出する方法、ノード装置及びプログラム
CN108632086B (zh) * 2018-04-19 2020-12-11 山东省计算中心（国家超级计算济南中心） 一种并行作业运行故障定位方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100239249A1 (en) * 2007-11-16 2010-09-23 Zte Corporation Tap, lrm, resource state control system and method
CN108712207A (zh) * 2018-04-17 2018-10-26 烽火通信科技股份有限公司 一种链路和业务的管理方法及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CENG GUO-BIN: "Research on Relation Between LRM and Other Modules in ASON", WIRELESS COMMUNICATION TECHNOLOGY, no. 3, 1 January 2011 (2011-01-01), pages 42 - 45, XP055797275 *
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 *
PAPADIMITRIOU, D. ET AL.: "Requirements for Generalized MPLS (GMPLS) Signaling Usage and Extensions for Automatically Switched Optical Network (ASON)", NETWORK WORKING GROUP REQUEST FOR COMMENTS: 4139, 31 July 2005 (2005-07-31), XP015041863 *

Also Published As

Publication number Publication date
EP4040726A1 (en) 2022-08-10
CN112583622A (zh) 2021-03-30
CN112583622B (zh) 2023-09-26
EP4040726A4 (en) 2022-11-16

Similar Documents

Publication Publication Date Title
CN112868206B (zh) 一种用于提供服务代理功能的方法、系统和计算机可读介质
US8203931B2 (en) Communication network protection systems
US10623293B2 (en) Systems and methods for dynamic operations, administration, and management
US8509061B2 (en) Systems and methods for scaling performance of Ethernet ring protection protocol
US8477769B2 (en) Flexible shared mesh protection services for intelligent TDM-based optical transport networks
US9344323B2 (en) G.8032 ethernet multiple fault recovery mechanisms
US10091023B2 (en) Systems and methods to detect and recover from a loop in an Ethernet ring protected network
US10158500B2 (en) G.8032 prioritized ring switching systems and methods
US9813286B2 (en) Method for virtual local area network fail-over management, system therefor and apparatus therewith
US7991872B2 (en) Vertical integration of network management for ethernet and the optical transport
WO2018010555A1 (zh) 一种北向接口lte业务自动配置方法、北向接口装置及存储介质
US20160204976A1 (en) Identifying the absence and presence of a ring protection link owner node in an ethernet network
JP2009516463A (ja) Ｖｐｌｓリモート故障表示
EP2555469B1 (en) Fault protection method and device
US8248913B1 (en) System and method to support full-time protection services in a network
WO2021063022A1 (zh) 故障事件信息的上报方法及系统
EP2526652B1 (en) Method, apparatus and communication network for providing restoration survivability
US9065756B2 (en) System and method for providing fast and efficient flushing of a forwarding database in a network processor
US8965199B2 (en) Method and apparatus for automatically restoring node resource state in WSON system
WO2021063069A1 (zh) 过滤信息配置方法及系统
WO2016184268A1 (zh) 基于隧道共享的带宽控制方法及装置
US20100239249A1 (en) Tap, lrm, resource state control system and method
US7756009B1 (en) Method and apparatus for priority call setup and restoration in an optical communications system
CN111614558B (zh) 一种主备路径计算单元工作优化方法及系统
WO2020118505A1 (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: 20871094

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020871094

Country of ref document: EP

Effective date: 20220502