WO2016062166A1 - 一种网络的操作管理维护oam方法、装置和系统 - Google Patents

一种网络的操作管理维护oam方法、装置和系统 Download PDF

Info

Publication number
WO2016062166A1
WO2016062166A1 PCT/CN2015/088793 CN2015088793W WO2016062166A1 WO 2016062166 A1 WO2016062166 A1 WO 2016062166A1 CN 2015088793 W CN2015088793 W CN 2015088793W WO 2016062166 A1 WO2016062166 A1 WO 2016062166A1
Authority
WO
WIPO (PCT)
Prior art keywords
oam
management
maintenance
fault
information
Prior art date
Application number
PCT/CN2015/088793
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 EP15852154.2A priority Critical patent/EP3203684B1/en
Publication of WO2016062166A1 publication Critical patent/WO2016062166A1/zh
Priority to US15/494,128 priority patent/US10237124B2/en

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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • 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/0686—Additional information in the notification, e.g. enhancement of specific meta-data
    • 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
    • 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/0677—Localisation of faults
    • 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
    • H04L41/0266—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
    • 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/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network

Definitions

  • the present invention relates to the field of network technologies, and in particular, to an OAM method, apparatus, and system for operation management and maintenance of a network.
  • OAM Operation Administration Maintenance
  • ⁇ may be deployed in different layers or in different domains.
  • Different network technologies may use different OAM technologies, such as Connectivity Fault Management (CFM) technology or two-way forwarding detection.
  • CFM Connectivity Fault Management
  • BFD Bidirectional Forwarding Detection
  • the existing fault alarm related technologies in these cross-layer cross-domain scenarios are bound to specific OAM technologies on the data plane network device, which requires complex mapping and conversion, which is difficult to implement. Therefore, how to better perform fault alarms for cross-layer and cross-domain scenarios using different OAM technologies needs to be solved.
  • an embodiment of the present invention provides a method, an apparatus, and a system for operation management and maintenance of a network.
  • the first aspect provides a network operation management and maintenance OAM method, including:
  • the OAM unified management center receives the fault alarm message sent by the management and maintenance node MP, where the fault alarm message includes fault information.
  • the OAM unified management center Determining, by the OAM unified management center, the first management maintenance set to which the MP belongs according to the fault alarm message, where the first management maintenance set includes an MP that uses the first OAM technology;
  • the OAM unified management center queries the OAM database to obtain a second management maintenance set that is associated with the first management maintenance set, where the second management maintenance set includes an MP that uses the second OAM technology, and the OAM
  • the database stores linkage information of different management and maintenance collections;
  • the OAM unified management center sends a failure notification message to all MPs in the second management maintenance set or the MP determined according to the policy, and the failure notification message includes the failure information.
  • the management maintenance set includes a management maintenance domain MD or a management maintenance entity group MEG.
  • the determining, by the OAM unified management center, the first management maintenance set according to the fault alarm message specifically includes:
  • the OAM unified management center determines the first management maintenance set according to the source address of the fault alarm message.
  • the fault alarm message further includes location information of the fault discovery device and/or location information of the fault reporting device, where the OAM is The determining, by the unified management center, the first management and maintenance set according to the content of the fault alarm message specifically includes:
  • the OAM unified management center determines the first management maintenance set according to at least one of the fault information, the location information of the fault discovery device, and the location information of the fault reporting device.
  • the OAM unified management center queries the OAM database to obtain the first management and maintenance
  • the step of establishing the OAM database is further included before the second management and maintenance set of the set linkage;
  • Establishing the OAM database by the OAM unified management center includes:
  • the OAM unified management center collects information about each MP in the network managed by the OAM unified management center, where the information of each MP includes network topology information of the respective MPs and OAM technical information used;
  • the OAM unified management center establishes the management and maintenance set according to the information of each MP;
  • the OAM unified management center establishes linkage information for the management and maintenance collections that need to be associated with the OAM.
  • the association information of the management and maintenance collections that need to be associated with the OAM linkage includes the linkage attribute of the connection MP to the other management and maintenance collections.
  • the multiple MPs are connected MPs when there are multiple MPs belonging to different management and maintenance collections on one network device.
  • the network corresponding to the management and maintenance set that needs to perform OAM linkage includes at least one same network device or covers the same path.
  • the OAM unified management center receives the fault alarm message sent by the management maintenance node MP.
  • the OAM unified management center receives data in the form of XML transmitted by the MP using a network configuration protocol NETCONF, and the data in the XML form is converted by an object of a general OAM management data model, and the universal OAM management data model uses IETF YANG Data Model format generation, the object of the generic OAM management data model carrying the fault information.
  • the OAM unified management center maintains all the The MP or the MP sending failure notification message determined according to the policy specifically includes:
  • the OAM unified management center sends data in the form of XML transmitted by the NETCONF to all the MPs in the second management maintenance set or the MP determined according to the policy, and the data in the XML form is converted by the object of the general OAM management data model.
  • the generic OAM management data model is generated using an IETF YANG Data Model format, and the object of the generic OAM management data model carries the fault information.
  • an embodiment of the present invention provides an OAM unified management center for operation management and maintenance, including:
  • a receiving unit configured to receive a fault alarm message sent by the management and maintenance node MP, where the fault alarm message includes fault information
  • a determining unit configured to determine, according to the fault alarm message, a first management maintenance set to which the MP belongs, where the first management maintenance set includes an MP that uses a first type of OAM technology;
  • a processing unit configured to query the OAM database to obtain a second management maintenance set that is associated with the first management maintenance set, where the second management maintenance set includes an MP that uses a second OAM technology, where the OAM database is saved with different management Maintain linkage information of the collection;
  • a sending unit configured to send a fault notification message to all MPs in the second management maintenance set or the MP determined according to the policy, where the fault notification message includes the fault information.
  • the management maintenance set includes a management maintenance domain MD or a management maintenance entity group MEG.
  • the determining unit is specifically configured to determine, according to the content of the fault alarm message, the first management and maintenance Collection; or
  • the fault alarm message further includes location information of the fault finding device and/or location information of the fault reporting device, and the determining unit is specifically configured to use the fault information, the location information of the fault finding device, and the fault report. At least one of the location information of the device determines the first administrative maintenance set.
  • the OAM unified management center further includes an establishing unit, where the establishing unit specifically includes :
  • a collection subunit configured to collect information about each MP in the network managed by the OAM unified management center, where the information of each MP includes network topology information of the respective MPs and OAM technical information used;
  • a first establishing subunit configured to establish the management and maintenance set according to the information of each MP
  • the second establishing sub-unit is configured to establish the linkage information for the management and maintenance collection that needs to perform the OAM linkage, and the establishing the linkage information for the management and maintenance collection that needs to perform the OAM linkage includes adding the linkage MP to the other management maintenance collection for the connection MP.
  • a linkage attribute where, when there are multiple MPs belonging to different management and maintenance collections on one network device, the multiple MPs are connected MPs.
  • the network corresponding to the management and maintenance set that needs to perform OAM linkage includes at least one same network device or covers the same path.
  • the receiving unit is configured to receive the MP by using a network configuration protocol NETCONF Passing data in XML form, the data in XML form is transformed from an object of a generic OAM management data model generated using an IETF YANG Data Model format, the object of the generic OAM management data model being carried The fault information.
  • NETCONF Passing data in XML form the data in XML form is transformed from an object of a generic OAM management data model generated using an IETF YANG Data Model format, the object of the generic OAM management data model being carried The fault information.
  • the sending unit is specifically configured to be used in the second management maintenance set All MPs or MPs determined according to the policy send data in the form of XML delivered using NETCONF, which is converted from objects of the general OAM management data model using the IETF YANG Data Model format. Generating, the object of the universal OAM management data model carries the fault information.
  • an embodiment of the present invention provides a network system, including:
  • the maintenance and maintenance node MP is configured to send a fault alarm message to the operation management and maintenance OAM unified management center as described above, where the fault alarm message includes fault information;
  • the OAM unified management center is configured to determine, according to the fault alarm message, that the MP belongs to a first management maintenance set, the first management maintenance set includes an MP that uses the first OAM technology, and is configured to query the OAM database to obtain a second management maintenance set that is associated with the first management maintenance set, where the second management
  • the maintenance set includes an MP that uses a second OAM technology, where the OAM database stores linkage information of different management and maintenance sets, and is used to send a failure notification message to all MPs in the second management maintenance set or MPs determined according to the policy.
  • the failure notification message includes the fault information;
  • All the MPs in the second management maintenance set or the MPs determined according to the policy are used to perform fault linkage according to the fault notification message.
  • the OAM method, device and system for operation management and maintenance of the network provided by the embodiment of the present invention can uniformly notify related fault alarms on the management plane and decouple with the specific OAM technology, thereby greatly reducing the implementation difficulty.
  • FIG. 1 is a schematic flowchart of a method for operation management and maintenance OAM of a network according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of an application scenario of an OAM method for operation management and maintenance of a network according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of an application scenario of an OAM method for operation management and maintenance of a network according to an embodiment of the present disclosure
  • FIG. 4 is a schematic structural diagram of an OAM unified management center for operation management and maintenance according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of a network system according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of an OAM unified management center for operation management and maintenance according to an embodiment of the present invention.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the letter “/” in this article generally indicates that the contextual object is an "or" relationship.
  • an embodiment of the present invention provides an OAM method for operation management and maintenance of a network, including:
  • the OAM unified management center receives a fault alarm message sent by a maintenance point (MP), where the fault alarm message includes fault information.
  • MP maintenance point
  • the OAM unified management center determines, according to the fault alarm message, a first management maintenance set to which the MP belongs, where the first management maintenance set includes an MP that uses a first type of OAM technology;
  • the OAM unified management center queries the OAM database to obtain a second management maintenance set that is associated with the first management maintenance set, where the second management maintenance set includes an MP that uses the second OAM technology, and the OAM database is saved. There are linkage information for different management and maintenance collections;
  • the OAM unified management center sends a fault notification message to all MPs in the second management maintenance set or the MP determined according to the policy, where the fault notification message includes the fault information.
  • the OAM method for operation management and maintenance of the network provided by the embodiment of the present invention can uniformly notify related fault alarms on the management plane and decouple with the specific OAM technology, thereby greatly reducing the implementation difficulty.
  • the management maintenance set includes a maintenance maintenance domain (MD) or a maintenance entity group (MEG).
  • MD maintenance maintenance domain
  • MEG maintenance entity group
  • the determining, by the OAM unified management center, that the first management and maintenance set according to the fault alarm message specifically includes:
  • the OAM unified management center determines the first management maintenance set according to the source address of the fault alarm message.
  • the fault alarm message further includes location information of the fault discovery device and/or location information of the fault reporting device, where the OAM unified management center determines the first management maintenance set according to the content of the fault alarm message. Specifically include:
  • the OAM unified management center determines the first management maintenance set according to at least one of the fault information, the location information of the fault discovery device, and the location information of the fault reporting device.
  • the fault discovery device and the fault reporting device may be a network device, that is, the network device finds a fault and sends a fault alarm message to the OAM unified management center; the fault discovery device and the fault reporting device may also be After the fault is discovered, the faulty device is notified to the fault reporting device, and the fault reporting device sends a fault alarm message to the OAM unified management center.
  • the OAM unified management center detects the fault according to the fault information.
  • At least one of the location information and the location information of the fault reporting device determines the first management maintenance set.
  • the determining, according to the fault information, the first management maintenance set may be determining the first management maintenance set according to location information of a network device or a link that fails in the fault information.
  • the faulty network device or link, the fault finding device, and the fault reporting device usually belong to a maintenance management set, the fault information, the location information of the fault finding device, and the location of the fault reporting device. At least one of the information includes information of the first management maintenance set, and then the first management maintenance set may be determined.
  • the fault alarm message may not include the location information of the fault finding device or the location information of the fault reporting device, and the OAM unified management center may send the fault by using a source address of the fault alert message, such as a source IP address.
  • the information of the MP of the alarm message such as the information of the first management maintenance set to which it belongs.
  • the step of the OAM unified management center querying the OAM database to obtain the OAM database before obtaining the second management maintenance set associated with the first management maintenance set;
  • Establishing the OAM database by the OAM unified management center includes:
  • each MP Collecting information about each MP in the network managed by the OAM unified management center, where the information of each MP includes network topology information of the respective MPs and OAM technical information used;
  • the OAM unified management center establishes the management and maintenance set according to the information of each MP;
  • the OAM unified management center establishes linkage information for the management and maintenance collections that need to be associated with the OAM.
  • the association information of the management and maintenance collections that need to be associated with the OAM linkage includes the linkage attribute of the connection MP to the other management and maintenance collections.
  • the multiple MPs are connected MPs when there are multiple MPs belonging to different management and maintenance collections on one network device.
  • the network corresponding to the management maintenance set that needs to perform OAM linkage includes at least one same network device or covers the same path.
  • the receiving, by the OAM unified management center, the fault alarm message sent by the management and maintenance node MP includes:
  • the OAM unified management center receives data in the form of XML transmitted by the MP using a network configuration protocol NETCONF, and the data in the XML form is converted by an object of a general OAM management data model, and the universal OAM management data model uses IETF YANG Data Model format generation, the object of the generic OAM management data model carrying the fault information.
  • the OAM unified management center maintains all MPs in the set to the second management or according to
  • the MP-disabled failure notification message determined by the policy specifically includes:
  • the OAM unified management center sends data in the form of XML transmitted by the NETCONF to all the MPs in the second management maintenance set or the MP determined according to the policy, and the data in the XML form is converted by the object of the general OAM management data model.
  • the generic OAM management data model is generated using an IETF YANG Data Model format, and the object of the generic OAM management data model carries the fault information.
  • CFM is deployed on the network between Switch A and Switch B.
  • BFD is deployed on the network between Switch B and Switch C. If the link between Switch B and Switch C fails, the remote switch A will not send the user traffic to the faulty link and cause user traffic. Interrupted.
  • the operation and maintenance OAM method of the network in the embodiment of the present invention is used, the related fault alarms can be advertised in the management plane and decoupled from the specific OAM technology, thereby greatly reducing the implementation difficulty, thereby making it easier to avoid this. The emergence of a situation.
  • the OAM unified management center establishes an OAM database
  • Establishing the OAM database by the OAM unified management center includes:
  • the OAM unified management center collects information about each MP in the network managed by the OAM unified management center, where the information of each MP includes network topology information of the respective MPs and OAM technical information used;
  • the embodiment of the present invention provides an OAM unified management center for unified management of the network.
  • the OAM unified management center is a logical concept, and may be an independent network device, such as a switch or a router, or may be built in a network device.
  • the OAM unified management center may be centralized, physically a separate network device, or built in a network device; or distributed, physically distributed in multiple independent network devices or built in On multiple network devices.
  • a plurality of MPs are provided in the network of the embodiment of the present invention, and the MP is used to perform OAM detection or OAM measurement.
  • the MP is also a logical concept and can be physically located on a network device, such as a switch or router.
  • One or more MPs can be set on one network device, and multiple MPs on one network device can also use different OAM technologies.
  • MP1 and MP2 there are two MPs on Switch B in Figure 2, namely, MP1 and MP2.
  • MP1 uses CFM technology and MP2 uses BFD technology.
  • Switch A has one MP, that is, MP3 and MP3 use CFM technology.
  • On Switch C one MP is set, that is, MP4, and MP4 uses BFD technology; the OAM unified tube
  • the information center may collect information about the MPs, that is, MP1, MP2, MP3, and MP4, and the information of the MPs includes network topology information of the respective MPs and OAM technology information used;
  • the OAM unified management center establishes the management and maintenance set according to the information of each MP, and the management and maintenance set may be an MD or an MEG;
  • the OAM unified management center establishes MD1.
  • the MD1 includes an MP that uses an OAM technology (CFM), that is, MP3 on Switch A and MP1 on Switch B.
  • CFM OAM technology
  • MD2 is established.
  • MD2 includes another type.
  • the MP of the OAM technology (BFD), that is, the MP4 on Switch C and the MP2 on Switch B establish MD2.
  • the OAM unified management center establishes linkage information for the management and maintenance collections that need to be linked to the OAM.
  • the association information is set up for the management and maintenance collections that need to be linked to the OAM, including adding the linkage to the other management and maintenance collections.
  • a linkage attribute where, when there are multiple MPs belonging to different management and maintenance collections on one network device, the multiple MPs are connected MPs.
  • a network device has an MP that belongs to a management and maintenance set. When there are multiple management and maintenance collections on one network device, multiple MPs belonging to each management maintenance set are connected MPs.
  • the establishing the linkage information for the management and maintenance set that needs to perform OAM linkage may also include establishing a linkage attribute for the management maintenance collection that needs to perform OAM linkage.
  • the network corresponding to the management and maintenance set that needs to perform OAM linkage includes at least one same network device or covers the same path.
  • the network corresponding to MD1 and MD2 includes the same network device Switch B.
  • the same user traffic flows through MD1 and MD2. If a fault occurs in MD1 or MD2, you need to notify another MD.
  • the other MD adjusts the flow of the user traffic accordingly, and determines that the MD and MAC2 need to perform OAM linkage;
  • the OAM unified management center is a management and maintenance set that needs to perform OAM linkage, that is, the association information is set up between the MD1 and the MD2, and the linkage information is set up between the MD1 and the MD2, and the linkage attribute of the connection MP to the other management maintenance set is added to the connection MP.
  • MP1 and MP2 on Switch B in Figure 2 MP1 belongs to MD1, MP2 belongs to MD2, MP1 and MP2 are located on Switch B, and MP1 and MP2 can be connected to MP.
  • the OAM unified management center is on MP1. Add the linkage attribute of "Link to MP2" and add the linkage attribute of "Link to MP1" on MP2.
  • the establishment of the linkage information for the MD1 and the MD2 may also include establishing a linkage attribute for the MD1 and the MD2, for example, adding the linkage attribute of "Linked to MD2" to MD1, and adding the linkage attribute of "Linked to MD1" by MD2.
  • the fault of the embodiment also includes other types of faults such as a network device or a node fault, or the fault of the embodiment of the present invention also includes that the link performance is degraded or the performance of the network device or the node is degraded.
  • the MP4 first detects the link failure, and the MP4 sends a fault alarm message to the unified OAM management center.
  • the OAM unified management center receives data in the form of XML transmitted by the MP4 using a Network Configuration Protocol (NETCONF), and the data in the XML form is converted by an object of a general OAM management data model, and the universal The OAM management data model is generated using an IETF YANG Data Model format, the object of the general OAM management data model carrying the fault information, wherein the universal OAM management data model in the IETF YANG Data Model format is converted into an XML form
  • the data may adopt rules of existing standards; the fault alarm message includes the fault information, the fault information includes a fault location, a fault state, and a fault content, where the fault location includes a location of the failed network device or link Information, etc.
  • the fault alarm message further includes location information of the fault finding device and/or location information of the fault reporting device, where the location information of the fault finding device and/or the location information of the fault reporting device includes the fault finding device.
  • the OAM unified management center may be the node identifier of the fault reporting device, the first management maintenance set to which the fault finding device and/or the fault reporting device belongs, such as the node identifier of the MP4, and the MD to which the MP4 belongs.
  • the general OAM management data model can be:
  • the object of the general OAM management data model is obtained by populating and/or expanding related parameters of the general OAM management data model according to a specific example.
  • the specific examples may or may not be related to a particular OAM technique.
  • the embodiment of the present invention fills and/or expands related parameters of the general OAM management data model according to the fault information that is not related to the specific OAM technology, and obtains the general OAM management data model. Object.
  • the OAM unified management center After receiving the fault alarm message, the OAM unified management center queries the OAM database to obtain the MD1 associated with the MD2;
  • the linkage attribute of the connection MP to the other management maintenance set is added to the connection MP, and the linkage attribute of the connection MP is found and described.
  • the connection MP is located in the other MPs of the same network device, and finds the linked MD according to the MD to which the MP is connected. For example, if the linkage information for the MD1 and the MD2 is included, the MP is added, that is, the linkage to the MP2 is added to the MP1.
  • the linkage attribute of the association, the linkage attribute of the linkage to the MP1 is added to the MP2, and the MP1 is found according to the linkage attribute of the MP2, and the MD1 to which the MP1 belongs is found according to the MP1;
  • the association between the OAM-based management and maintenance collections and the establishment of the linkage information also includes the linkage attribute of the management and maintenance collections that need to be linked to the OAM.
  • the linkage attribute of the linkage to the MD2 is added to the MD1, and the linkage attribute of the linkage to the MD1 is added to the MD2.
  • the MD1 associated with the MD2 can be directly found according to the linkage attribute of the management maintenance set.
  • the OAM unified management center sends a fault notification message to all MPs in the MD1 or the MP determined according to the policy, where the fault notification message includes the fault information.
  • the OAM unified management center sends a fault notification message to all the MPs in the MD1; or the OAM unified management center may send a fault notification message to the MP determined according to the policy in the MD1, and the specific policy is not used in the embodiment of the present invention.
  • the limitation is that the protection scope of the embodiment of the present invention is provided.
  • the OAM unified management center sends a failure notification message to all MPs in the MD1, that is, MP1 and MP3; the OAM unified management center sends the MP1 and the MP3 to the MP3 and the MP3.
  • the data in XML form is transformed from an object of a generic OAM management data model generated using an IETF YANG Data Model format, the generic OAM management data model
  • the object carries the fault information, wherein the data converted into the XML form using the universal OAM management data model in the IETF YANG Data Model format may adopt an existing standard rule; the fault notification message includes the fault information
  • the fault information includes a fault location, a fault state, and a fault content, where the fault location includes Location information of the failed network device or link.
  • the fault notification message further includes location information of the fault finding device and/or location of the fault reporting device.
  • the information, the location information of the fault discovery device and/or the location information of the fault reporting device includes a node identifier of the fault discovery device and/or the fault reporting device, and the fault discovery device and/or the fault reporting device belongs to the first Manage maintenance collections, such as the node ID of MP4, MP4 belongs to MD, etc.; MP1 and MP3 can be linked according to their own situation, such as enabling alternate channels.
  • the generic OAM management data model can be:
  • the object of the general OAM management data model is obtained by populating and/or expanding related parameters of the general OAM management data model according to a specific example.
  • the specific examples may or may not be related to a particular OAM technique.
  • the embodiment of the present invention fills and/or expands related parameters of the general OAM management data model according to the fault information that is not related to the specific OAM technology to obtain an object of the general OAM management data model.
  • the OAM unified management center may send the fault notification message to other MPs that are in the same MD as the MP4.
  • the OAM unified management center may send the fault notification message to the MP2.
  • the MP2 when the MP2 detects the link failure, if the MP2 has received the fault notification message sent by the OAM unified management center, it does not need to be uniformly managed to the OAM.
  • the center sends a fault alarm message. If the MP2 has not received the fault notification message sent by the OAM unified management center, the fault alarm message may be sent to the OAM unified management center.
  • the fault alarm message or the fault notification message in the embodiment of the present invention may also be delivered by using an extended Simple Network Management Protocol (SNMP).
  • SNMP extended Simple Network Management Protocol
  • the OAM unified management center in the embodiment of the present invention may also receive a fault alarm message sent by the MP of the first management and maintenance set by using a method of the prior art, where the fault alarm message includes fault information, and the existing The technical method is related to the OAM technology used by the MP; the OAM unified management center queries the OAM database to obtain a second management maintenance set associated with the first management maintenance set, and the second management maintenance set includes using the second An OAM technology MP, the OAM database stores linkage information of different management and maintenance sets; the OAM unified management center converts the fault information into an object of a general OAM management data model; the OAM unified management center The second management maintains all MPs in the set or the MP according to the policy, and sends a fault notification message, where the fault notification message includes the fault information, and the fault notification message adopts XML-form data transmitted by NETCONF, in the form of XML Data is managed by the generic OAM An object of the model is transformed, the generic OAM management data model being generated using
  • the OAM unified management center in the embodiment of the present invention may also receive a fault alarm message sent by the MP of the first management and maintenance set by using a method of the prior art, where the fault alarm message includes fault information, and the existing The technical method is related to the OAM technology used by the MP; the OAM unified management center queries the OAM database to obtain a second management maintenance set associated with the first management maintenance set, and the second management maintenance set includes using the second An MP of the OAM technology, the OAM database stores linkage information of different management and maintenance sets; the OAM unified management center sends a failure notification message to all MPs in the second management maintenance set or the MP determined according to the policy.
  • the failure notification message includes the failure information, and the failure notification message is transmitted by a prior art method related to the OAM technology used by the MP.
  • the embodiment of the present invention can be compatible with the method of supporting the prior art to send a fault alarm message or a fault notification message, and does not support the MP based on the method of the general OAM management data model.
  • Figure 3 shows a multi-layer OAM (Multi-layer OAM) scenario.
  • the bottom layer is the label switched path LSP layer, followed by the pseudowire PW layer and the multi-segment pseudowire MS-PW layer.
  • the cross layer may include In other layers, each layer uses the OAM technology corresponding to the layer network technology.
  • the fault of the embodiment of the present invention includes Other types of faults such as network device or node failure, or the fault of the embodiment of the present invention also includes link performance degradation or network device or node performance degradation, etc., and MPs located in different layers of the management and maintenance set may detect the chain.
  • a fault alarm may be sent, and an alarm storm may be generated.
  • the OAM method is used for the operation and maintenance of the network in the embodiment of the present invention, the related fault alarm may be uniformly notified and suppressed on the management plane. The decoupling of specific OAM technology greatly reduces the difficulty of implementation, and it is easier to avoid this situation.
  • each of the routers of each layer is configured with an MP
  • the OAM unified management center may collect information about each MP in the network managed by the OAM unified management center, where the information of each MP includes the network of each MP.
  • Different layers are distinguished by different MEGs, that is, each layer is assigned to one MEG, and the MEG-LEVEL attribute is used in the MEG to distinguish different OAM technologies of different layers.
  • the OAM unified management center establishes linkage information for the management and maintenance collections that need to be associated with the OAM.
  • the association information of the management and maintenance collections that need to be associated with the OAM linkage includes the linkage attribute of the connection MP to the other management and maintenance collections.
  • the multiple MPs are connected MPs when there are multiple MPs belonging to different management and maintenance collections on one network device.
  • a network device has an MP that belongs to a management and maintenance set. When there are multiple management and maintenance collections on one network device, multiple MPs belonging to each management maintenance set are connected MPs.
  • the establishing the linkage information for the management and maintenance set that needs to perform OAM linkage may also include establishing a linkage attribute for the management maintenance collection that needs to perform OAM linkage.
  • the network corresponding to the management and maintenance set that needs to perform OAM linkage includes at least one same network device or covers the same path.
  • the network topology corresponding to the management and maintenance set of each layer covers the same path.
  • the MP of the management and maintenance set of each layer may detect the link fault. And sending a fault alarm message to generate an alarm storm. Therefore, the MP of the management and maintenance set of the layer that first detects and sends the fault alarm message needs to notify the MP of the management maintenance set of another layer to make the management maintenance set of the other layer.
  • the MP performs alarm suppression and no longer sends a fault alarm message, and then determines that OAM linkage is required for the management and maintenance set of each layer.
  • the embodiment of the present invention may also determine that only OAM linkage between management and maintenance sets of certain layers is performed according to the policy. ;
  • the establishing the linkage information for the management and maintenance set that needs to be associated with the OAM includes adding the linkage attribute of the connection MP to the other management maintenance set for the connection MP.
  • the different management maintenance sets in FIG. 3 are cross layers, and each layer is physically Covering the same path, the OAM unified management center uses multiple MPs belonging to different management and maintenance collections on each network device as the connection MP, and adds the linkage attributes of the connection MP to other management and maintenance collections for the connection MP, such as the carrier.
  • the terminating edge router 1 has three MPs, the MP-LSP-T-PE1 belonging to the management and maintenance set of the LSP layer, the MP-PW-T-PE1 belonging to the management and maintenance set of the PW layer, and the management and maintenance set belonging to the multi-segment PW layer.
  • MP-MS-PW-T-PE1 the OAM unified management center uses these MPs as the connection MP, and adds linkage attributes to these connection MPs, and adds "linkage to MP-PW-T to MP-LSP-T-PE1.
  • the establishing the linkage information for the OAM-related management and maintenance set may also include establishing a linkage attribute for the OAM-linked management and maintenance set, for example, adding the management and maintenance set of the LSP layer to the management and maintenance set of the PW layer. And the linkage attribute of the management and maintenance collection of the linkage to the MS-PW layer, and the management and maintenance collection of the PW layer is added to the management and maintenance collection of the linkage to the LSP layer and the management and maintenance collection of the linkage to the MS-PW layer. The linkage attribute is added to the management and maintenance set of the MS-PW layer. The linkage attribute of the management and maintenance collection of the linkage to the LSP layer and the management and maintenance collection of the linkage to the PW layer are added.
  • the MP of the LSP layer management and maintenance set that is, MP-LSP-T-PE1
  • MP-LSP-T-PE1 the MP of the LSP layer management and maintenance set
  • the OAM unified management center receives the data in the form of XML transmitted by the MP-LSP-T-PE1 using NETCONF, and the data in the XML form is converted by the object of the general OAM management data model, and the general OAM management data is The model is generated using an IETF YANG Data Model format, the object of the general OAM management data model carrying the fault information, wherein the data converted into XML form using the universal OAM management data model in the IETF YANG Data Model format may be adopted
  • the existing standard rule includes: the fault alarm message includes the fault information, and the fault information includes a fault location, a fault state, and a fault content, where the fault location includes location information of the faulty network device or link.
  • the fault alarm message further includes location information of the fault finding device and/or location information of the fault reporting device, where the location information of the fault finding device and/or the location information of the fault reporting device includes the fault finding device.
  • the node identifier of the fault reporting device, the first management maintenance set to which the fault finding device and/or the fault reporting device belongs such as the node identifier including the MP-LSP-T-PE1, MP-LSP-T-PE1
  • the MMC to which the MP-LSP-T-PE1 belongs, and the OAM unified management center can obtain the information of the MP that sends the fault alarm message, such as the information of the first management and maintenance set, and the like.
  • the universal OAM management data model may for:
  • the object of the general OAM management data model is obtained by populating and/or expanding related parameters of the general OAM management data model according to a specific example.
  • the specific examples may or may not be related to a particular OAM technique.
  • the embodiment of the present invention fills and/or expands related parameters of the general OAM management data model according to the fault information that is not related to the specific OAM technology to obtain an object of the general OAM management data model.
  • the OAM unified management center After receiving the fault alarm message, the OAM unified management center queries the OAM database to obtain a management and maintenance set associated with the management and maintenance set of the LSP layer, that is, the management and maintenance set of the PW layer and the management and maintenance set of the MS-PW layer. ;
  • connection MP is located in the other MPs of the same network device, and finds the linkage management and maintenance set according to the management and maintenance set to which the connection MP belongs, for example, the linkage to the MP-PW according to the MP-LSP-T-PE1 of the LSP layer.
  • -T-PE1 and the linkage attribute of "Linked to MP-MS-PW-T-PE1", find other MPs that are on the same network device as MP-LSP-T-PE1, ie MP-PW-T-PE1 and MP-MS-PW-T-PE1, and finds the linkage management and maintenance set according to the management and maintenance set of MP-PW-T-PE1 and MP-MS-PW-T-PE1, that is, the management and maintenance set and MS of the PW layer. - management and maintenance collection of the PW layer;
  • association information is set up for the management and maintenance set that needs to be associated with the OAM
  • the association attribute is set to be associated with the OAM-linked management and maintenance set
  • the LSP layer may be directly found according to the linkage attribute of the management maintenance set.
  • the management and maintenance collection of the collection and management of the collection and maintenance that is, the management and maintenance collection of the PW layer and the management and maintenance collection of the MS-PW layer;
  • the OAM unified management center sends the management and maintenance set associated with the management and maintenance set of the LSP layer, that is, the management and maintenance set of the PW layer and all the MPs in the management and maintenance set of the MS-PW layer or the MP determined according to the policy.
  • a failure notification message, the failure notification message including the failure information is included in the management and maintenance set of the LSP layer.
  • the OAM unified management center sends a failure notification message to all the MPs in the management maintenance set of the PW layer and the management maintenance set of the MS-PW layer; or the OAM unified management center may also manage the collection and the MS to the PW layer.
  • the MP sends a fault notification message according to the policy.
  • the specific policy is not limited in the embodiment of the present invention, and belongs to the protection scope of the embodiment of the present invention.
  • the OAM is unified.
  • the management center sends a fault notification message to all the MPs in the management and maintenance set of the PW layer and the management and maintenance set of the MS-PW layer.
  • the OAM unified management center sends the MP to the MP that needs to perform fault linkage.
  • Data in XML form delivered by NETCONF the data in XML form is transformed from an object of a generic OAM management data model generated using an IETF YANG Data Model format, the generic OAM management data model
  • the object carries the fault information, wherein the data converted into the XML form by using the universal OAM management data model in the IETF YANG Data Model format may adopt an existing standard rule;
  • the fault notification message includes the fault information,
  • the fault information includes a fault location, a fault state, and a fault location, where the fault location includes location information of the faulty network device or link.
  • the fault notification message further includes location information of the fault finding device and/or location of the fault reporting device.
  • the information, the location information of the fault discovery device and/or the location information of the fault reporting device includes a node identifier of the fault discovery device and/or the fault reporting device, and the fault discovery device and/or the fault reporting device belongs to the first Management and maintenance collections, such as the node ID of the MP-LSP-T-PE1, the MD to which the MP-LSP-T-PE1 belongs, the MEG to which the MP-LSP-T-PE1 belongs, and the MP to which the fault linkage needs to be performed.
  • fault linkage for example, alarm suppression is performed, and when the link is detected, the fault alarm message is no longer sent.
  • the generic OAM management data model can be:
  • the object of the general OAM management data model is obtained by populating and/or expanding related parameters of the general OAM management data model according to a specific example.
  • the specific examples may or may not be related to a particular OAM technique.
  • the embodiment of the present invention fills and/or expands related parameters of the general OAM management data model according to the fault information that is not related to the specific OAM technology to obtain an object of the general OAM management data model.
  • the OAM unified management center may send a fault notification message to other MPs in the same management and maintenance set as the MP-LSP-T-PE1.
  • the OAM unified management center may send faults to other MPs of the LSP layer. Notification message.
  • the fault alarm message or the fault notification message in the embodiment of the present invention may also be delivered by using extended SNMP.
  • the OAM unified management center in the embodiment of the present invention may also receive a fault alarm message sent by the MP of the first management and maintenance set by using a method of the prior art, where the fault alarm message includes fault information, and the existing The technical method is related to the OAM technology used by the MP; the OAM unified management center queries the OAM database to obtain a second management maintenance set associated with the first management maintenance set, and the second management maintenance set includes using the second An OAM technology MP, the OAM database stores linkage information of different management and maintenance sets; the OAM unified management center converts the fault information into an object of a general OAM management data model; the OAM unified management center The second management maintains all MPs in the set or the MP according to the policy, and sends a fault notification message, where the fault notification message includes the fault information, and the fault notification message adopts XML-form data transmitted by NETCONF, in the form of XML Data is converted from objects of the generic OAM management data model using IETF YANG Data Model format generation, the
  • the OAM unified management center in the embodiment of the present invention may also receive a fault alarm message sent by the MP of the first management and maintenance set by using a method of the prior art, where the fault alarm message includes fault information, and the existing The technical method is related to the OAM technology used by the MP; the OAM unified management center queries the OAM database to obtain a second management maintenance set associated with the first management maintenance set, and the second management maintenance set includes using the second An MP of the OAM technology, the OAM database stores linkage information of different management and maintenance sets; the OAM unified management center sends a failure notification message to all MPs in the second management maintenance set or the MP determined according to the policy.
  • the failure notification message includes the failure information, and the failure notification message is transmitted by a prior art method related to the OAM technology used by the MP.
  • the embodiment of the present invention can be compatible with the method of supporting the prior art to send a fault alarm message or a fault notification message, and does not support the MP based on the method of the general OAM management data model.
  • an embodiment of the present invention further provides an OAM unified management center for operation management and maintenance, including:
  • the receiving unit 401 is configured to receive a fault alarm message that is sent by the management and maintenance node MP, where the fault alarm message includes fault information.
  • a determining unit 402 configured to determine, according to the fault alarm message, a first management maintenance set to which the MP belongs, where the first management maintenance set includes an MP that uses a first type of OAM technology;
  • the processing unit 403 is configured to query the OAM database to obtain a second management maintenance set that is associated with the first management maintenance set, where the second management maintenance set includes an MP that uses the second OAM technology, and the OAM number
  • the database stores linkage information of different management and maintenance collections
  • the sending unit 404 is configured to send a fault notification message to all MPs in the second management maintenance set or the MP determined according to the policy, where the fault notification message includes the fault information.
  • the management maintenance set includes an administrative maintenance domain MD or an administrative maintenance entity group MEG.
  • the determining unit 402 is specifically configured to determine, according to the content of the fault alarm message, the first management maintenance set; or
  • the fault alarm message further includes location information of the fault finding device and/or location information of the fault reporting device, where the determining unit is specifically configured to use the fault information, location information of the fault finding device, and At least one of the location information of the fault reporting device determines the first management maintenance set.
  • the OAM unified management center further includes an establishing unit, where the establishing unit specifically includes:
  • a collection subunit configured to collect information about each MP in the network managed by the OAM unified management center, where the information of each MP includes network topology information of the respective MPs and OAM technical information used;
  • a first establishing subunit configured to establish the management and maintenance set according to the information of each MP
  • the second establishing sub-unit is configured to establish the linkage information for the management and maintenance collection that needs to perform the OAM linkage, and the establishing the linkage information for the management and maintenance collection that needs to perform the OAM linkage includes adding the linkage MP to the other management maintenance collection for the connection MP.
  • a linkage attribute where, when there are multiple MPs belonging to different management and maintenance collections on one network device, the multiple MPs are connected MPs.
  • the network corresponding to the management maintenance set that needs to perform OAM linkage includes at least one same network device or covers the same path.
  • the receiving unit 401 is specifically configured to receive data in an XML format that is transmitted by the MP by using a network configuration protocol NETCONF, where the data in the XML form is converted by an object of a general OAM management data model, where the universal The OAM management data model is generated using the IETF YANG Data Model format, and the object of the generic OAM management data model carries the fault information.
  • NETCONF network configuration protocol
  • the sending unit 403 is specifically configured to send data in an XML form that is delivered by using NETCONF to all MPs in the second management maintenance set or MPs determined according to the policy, where the data in the XML form is used by the general OAM.
  • the object of the management data model is transformed, the generic OAM management data model is generated using an IETF YANG Data Model format, the object of the generic OAM management data model carrying the fault information.
  • an embodiment of the present invention further provides a network system, including:
  • the management and maintenance node MP 501 is configured to send a fault alarm message to the operation management and maintenance OAM unified management center 502 as described above, where the fault alarm message includes fault information;
  • the OAM unified management center 502 is configured to determine, according to the fault alarm message, a first management maintenance set to which the MP belongs, where the first management maintenance set includes an MP that uses a first type of OAM technology, and is used for querying Obtaining, by the OAM database, a second management maintenance set that is associated with the first management maintenance set, where the second management maintenance set includes an MP that uses a second OAM technology, where the OAM database stores linkage information of different management maintenance sets; And sending a failure notification message to all MPs in the second management maintenance set or the MP determined according to the policy, where the failure notification message includes the failure information;
  • All the MPs in the second management maintenance set or the MP 503 determined according to the policy are used to perform fault linkage according to the fault notification message.
  • the embodiment of the present invention further provides an OAM unified management center for operation management and maintenance, including:
  • the transceiver 601, the processor 602, the memory 603, and the bus 604, the transceiver 601, the processor 602, and the memory 603 are connected by a bus 604 and complete communication with each other, wherein:
  • the bus 604 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus 604 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one line is shown in the figure, but it does not mean that there is only one bus or one type of bus.
  • the memory 603 is for storing program code, and the program code includes an operation instruction.
  • the memory 603 may include a random access memory (RAM), and may also include a non-volatile memory such as a disk storage.
  • the processor 602 may be a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • the transceiver 601 can be an interface.
  • the transceiver 601 is configured to receive a fault alarm message sent by the management and maintenance node MP, where the fault alarm message includes fault information.
  • the processor 602 is configured to call the program code in the memory 603 to perform the following operations:
  • the first management maintenance set includes an MP that uses a first type of OAM technology
  • the query OAM database obtains the first management maintenance set.
  • a second management and maintenance set the second management and maintenance set includes an MP that uses a second OAM technology, where the OAM database stores linkage information of different management and maintenance sets;
  • the transceiver 601 is further configured to send a fault notification message to all MPs in the second management maintenance set or the MP determined according to the policy, where the fault notification message includes the fault information.
  • modules and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules is only a logical function division.
  • there may be another division manner for example, multiple modules or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or module, and may be electrical, mechanical or otherwise.
  • the modules described as separate components may or may not be physically separated.
  • the components displayed as modules may or may not be physical modules, that is, may be located in one place, or may be distributed to multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.
  • the functions, if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including A number of instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the methods of the various embodiments of the present invention Step by step.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

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

Abstract

本申请公开了一种网络的操作管理维护OAM方法、装置和系统，OAM统一管理中心接收MP发送的故障告警消息，所述故障告警消息包括故障信息；所述OAM统一管理中心根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP；所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，从而可以统一在管理平面对相关故障告警进行通告，与具体OAM技术解耦合，极大的降低了实现难度。

Description

一种网络的操作管理维护OAM方法、装置和系统
本申请要求于2014年10月23日提交中国专利局、申请号为201410571235.6、发明名称为“一种网络的操作管理维护OAM方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及网络技术领域，特别涉及一种网络的操作管理维护OAM方法、装置和系统。
背景技术
随着网络业务量和业务种类的迅速增加，网络变的越来越复杂，对网络的操作管理维护(Operation Administration Maintenance,OAM)也提出了更高的要求。其中，故障告警相关技术越来越受到人们的重视。
在跨层跨域场景下，不同层或者不同域可能会部署不同的网络技术，不同的网络技术可能会使用不同的OAM技术，比如连通故障管理(Connectivity Fault Management,CFM)技术或者双向转发检测(Bidirectional Forwarding Detection,BFD)技术，而在这些跨层跨域场景下现有的故障告警相关技术是在数据面网络设备上与具体的OAM技术绑定，需要进行复杂的映射和转换，实现难度大，因此如何更好的对使用不同OAM技术的跨层跨域场景进行故障告警亟需解决。
发明内容
为了更好的对使用不同OAM技术的跨层跨域场景进行故障告警，本发明实施例提供一种网络的操作管理维护OAM方法、装置和系统。
第一方面，提供一种网络的操作管理维护OAM方法，包括：
OAM统一管理中心接收管理维护节点MP发送的故障告警消息，所述故障告警消息包括故障信息；
所述OAM统一管理中心根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；
所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM 数据库保存有不同管理维护集合的联动信息；
所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息。
结合第一方面，在第一种可能的实现方式中，所述管理维护集合包括管理维护域MD或管理维护实体组MEG。
结合第一方面或第一方面的第一种可能的实现方式，在第二种可能的实现方式中，所述OAM统一管理中心根据所述故障告警消息确定所述第一管理维护集合具体包括：
所述OAM统一管理中心根据所述故障告警消息的内容确定所述第一管理维护集合；或者
所述OAM统一管理中心根据所述故障告警消息的源地址确定所述第一管理维护集合。
结合第一方面的第二种可能的实现方式，在第三种可能的实现方式中，所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，则所述OAM统一管理中心根据所述故障告警消息的内容确定所述第一管理维护集合具体包括：
所述OAM统一管理中心根据所述故障信息、所述故障发现设备的位置信息和所述故障上报设备的位置信息中的至少一个确定所述第一管理维护集合。
结合第一方面或第一方面的第一种至第三种任一可能的实现方式，在第四种可能的实现方式中，所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合之前还包括建立所述OAM数据库的步骤；
所述OAM统一管理中心建立所述OAM数据库包括：
所述OAM统一管理中心收集所述OAM统一管理中心管理的网络中各个MP的信息，所述各个MP的信息包括所述各个MP的网络拓扑信息和使用的OAM技术信息；
所述OAM统一管理中心根据所述各个MP的信息建立所述管理维护集合；
所述OAM统一管理中心为需要进行OAM联动的管理维护集合建立联动信息，所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，其中，当一个网络设备上有属于不同管理维护集合的多个MP时，所述多个MP为衔接MP。
结合第一方面的第四种可能的实现方式，在第五种可能的实现方式中，所述需要进行OAM联动的管理维护集合对应的网络包括至少一个相同的网络设备或者覆盖相同的路径。
结合第一方面或第一方面的第一种至第五种任一可能的实现方式，在第六种可能的实现方式中，所述OAM统一管理中心接收管理维护节点MP发送的故障告警消息具体包括：
所述OAM统一管理中心接收所述MP采用网络配置协议NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
结合第一方面或第一方面的第一种至第六种任一可能的实现方式，在第七种可能的实现方式中，所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息具体包括：
所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送采用NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
第二方面，本发明实施例提供一种操作管理维护OAM统一管理中心，包括：
接收单元，用于接收管理维护节点MP采用发送的故障告警消息，所述故障告警消息包括故障信息；
确定单元，用于根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；
处理单元，用于查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；
发送单元，用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息。
结合第二方面，在第一种可能的实现方式中，所述管理维护集合包括管理维护域MD或管理维护实体组MEG。
结合第二方面或第二方面的第一种可能的实现方式，在第二种可能的实现方式中，所述确定单元，具体用于根据所述故障告警消息的内容确定所述第一管理维护集合；或者
根据所述故障告警消息的源地址确定所述第一管理维护集合。
结合第二方面的第二种可能的实现方式，在第三种可能的实现方式中，
所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，则所述确定单元具体用于根据所述故障信息、所述故障发现设备的位置信息和所述故障上报设备的位置信息中的至少一个确定所述第一管理维护集合。
结合第二方面或第二方面的第一种至第三种任一可能的实现方式，在第四种可能的实现方式中，所述OAM统一管理中心还包括建立单元，所述建立单元具体包括：
收集子单元，用于收集所述OAM统一管理中心管理的网络中各个MP的信息，所述各个MP的信息包括所述各个MP的网络拓扑信息和使用的OAM技术信息；
第一建立子单元，用于根据所述各个MP的信息建立所述管理维护集合；
第二建立子单元，用于为需要进行OAM联动的管理维护集合建立联动信息，所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，其中，当一个网络设备上有属于不同管理维护集合的多个MP时，所述多个MP为衔接MP。
结合第二方面的第四种可能的实现方式，在第五种可能的实现方式中，所述需要进行OAM联动的管理维护集合对应的网络包括至少一个相同的网络设备或者覆盖相同的路径。
结合第二方面或第二方面的第一种至第五种任一可能的实现方式，在第六种可能的实现方式中，所述接收单元，具体用于接收所述MP采用网络配置协议NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
结合第二方面或第二方面的第一种至第六种任一可能的实现方式，在第七种可能的实现方式中，所述发送单元，具体用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送采用NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
第三方面，本发明实施例提供一种网络系统，包括：
管理维护节点MP，用于向如上所述的操作管理维护OAM统一管理中心发送故障告警消息，所述故障告警消息包括故障信息；
如上所述的OAM统一管理中心，用于根据所述故障告警消息确定所述MP所属的 第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；并用于查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；并用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息；
所述第二管理维护集合中所有的MP或者根据策略确定的MP，用于根据所述故障通知消息进行故障联动。
本发明实施例提供的一种网络的操作管理维护OAM方法、装置和系统，从而可以统一在管理平面对相关故障告警进行通告，与具体OAM技术解耦合，极大的降低了实现难度。
附图说明
图1为本发明实施例提供的一种网络的操作管理维护OAM方法流程示意图；
图2为本发明实施例提供的一种网络的操作管理维护OAM方法的应用场景示意图；
图3为本发明实施例提供的一种网络的操作管理维护OAM方法的应用场景示意图；
图4为本发明实施例提供的一种操作管理维护OAM统一管理中心结构示意图；
图5为本发明实施例提供的一种网络系统结构示意图；
图6为本发明实施例提供的一种操作管理维护OAM统一管理中心结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获取的所有其他实施例，都属于本发明保护的范围。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字母“/”，一般表示前后关联对象是一种“或”的关系。
下面结合说明书附图对本发明优选的实施方式进行详细说明，应当理解，此处所描述的优选实施例仅用于说明和解释本发明，并不用于限定本发明，并且在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。。
如图1所示，本发明实施例提供了一种网络的操作管理维护OAM方法，包括：
S101，OAM统一管理中心接收管理维护节点(Maintenance Point,MP)发送的故障告警消息，所述故障告警消息包括故障信息；
S102，所述OAM统一管理中心根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；
S103，所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；
S104，所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息。
本发明实施例提供的一种网络的操作管理维护OAM方法，从而可以统一在管理平面对相关故障告警进行通告，与具体OAM技术解耦合，极大的降低了实现难度。
可选地，所述管理维护集合包括管理维护域(Maintenance Domain,MD)或管理维护实体组(Maintenance Entity Group,MEG)。
可选地，所述OAM统一管理中心根据所述故障告警消息确定所述第一管理维护集合具体包括：
所述OAM统一管理中心根据所述故障告警消息的内容确定所述第一管理维护集合；或者
所述OAM统一管理中心根据所述故障告警消息的源地址确定所述第一管理维护集合。
可选地，所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，则所述OAM统一管理中心根据所述故障告警消息的内容确定所述第一管理维护集合具体包括：
所述OAM统一管理中心根据所述故障信息、所述故障发现设备的位置信息和所述故障上报设备的位置信息中的至少一个确定所述第一管理维护集合。
可选地，故障发现设备和故障上报设备可以是一个网络设备，即该网络设备发现故障并向OAM统一管理中心发送故障告警消息；故障发现设备和故障上报设备也可以是 不同的网络设备，比如故障发现设备发现故障后，通知给故障上报设备，由故障上报设备向OAM统一管理中心发送故障告警消息；而OAM统一管理中心根据所述故障信息、所述故障发现设备的位置信息和所述故障上报设备的位置信息中的至少一个确定所述第一管理维护集合。其中，根据故障信息确定所述第一管理维护集合可以是根据故障信息中发生故障的网络设备或链路的位置信息来确定所述第一管理维护集合。所述发生故障的网络设备或链路、所述故障发现设备和所述故障上报设备通常属于一个维护管理集合，所述故障信息、所述故障发现设备的位置信息和所述故障上报设备的位置信息中的至少一个包括所述第一管理维护集合的信息，则可以确定所述第一管理维护集合。
可选地，所述故障告警消息也可以不包括故障发现设备的位置信息或故障上报设备的位置信息，而OAM统一管理中心可以由故障告警消息的源地址，比如源IP地址，得到发送该故障告警消息的MP的信息，比如所属的第一管理维护集合等信息。
可选地，所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合之前还包括建立所述OAM数据库的步骤；
所述OAM统一管理中心建立所述OAM数据库包括：
收集所述OAM统一管理中心管理的网络中各个MP的信息，所述各个MP的信息包括所述各个MP的网络拓扑信息和使用的OAM技术信息；
所述OAM统一管理中心根据所述各个MP的信息建立所述管理维护集合；
所述OAM统一管理中心为需要进行OAM联动的管理维护集合建立联动信息，所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，其中，当一个网络设备上有属于不同管理维护集合的多个MP时，所述多个MP为衔接MP。
可选地，所述需要进行OAM联动的管理维护集合对应的网络包括至少一个相同的网络设备或者覆盖相同的路径。
可选地，所述OAM统一管理中心接收管理维护节点MP发送的故障告警消息具体包括：
所述OAM统一管理中心接收所述MP采用网络配置协议NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
可选地，所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据 策略确定的MP发送故障通知消息具体包括：
所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送采用NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
下面结合图2的应用场景，对本发明又一实施例提供的一种网络的操作管理维护OAM方法进行说明：
如图2所示：在Switch A和Switch B之间的网络部署CFM，在Switch B和Switch C之间的网络部署BFD。这样，Switch B到Switch C之间链路发生故障时，远端Switch A感知不到Switch B到Switch C之间的链路故障，则仍会将用户流量发往故障链路从而造成用户流量的中断。采用本发明实施例的一种网络的操作管理维护OAM方法，则可以统一在管理平面对相关故障告警进行通告，与具体OAM技术解耦合，极大的降低了实现难度，从而更容易的避免这种情况的出现。
本发明实施例的一种网络的操作管理维护OAM方法，流程如下：
1、OAM统一管理中心建立OAM数据库；
所述OAM统一管理中心建立所述OAM数据库包括：
11、OAM统一管理中心收集所述OAM统一管理中心管理的网络中各个MP的信息，所述各个MP的信息包括所述各个MP的网络拓扑信息和使用的OAM技术信息；
本发明实施例设置OAM统一管理中心，对所述网络进行统一管理，所述的OAM统一管理中心是个逻辑的概念，物理上可以是独立的网络设备，如交换机或路由器，也可以内置在网络设备上，所述的OAM统一管理中心可以是集中式，物理上是一个独立的网络设备，或者内置在某个网络设备上；也可以是分布式，物理上分布在多个独立的网络设备或者内置在多个网络设备上。
本发明实施例的网络中设置有多个MP，所述MP用于执行OAM检测或OAM测量。所述MP也是个逻辑的概念，物理上可以设置在某个网络设备上，如交换机或路由器上。一台网络设备上可以设置一个或多个MP，一台网络设备上的多个MP也可以分别使用不同的OAM技术。
比如，图2中的Switch B上设置有两个MP，即，MP1和MP2，其中，MP1使用CFM技术，MP2使用BFD技术；Switch A上设置有1个MP，即，MP3，MP3使用CFM技术；Switch C上设置有1个MP，即MP4，MP4使用BFD技术；所述OAM统一管 理中心可以收集所述各个MP，即MP1，MP2，MP3和MP4的信息，所述各个MP的信息包括所述各个MP的网络拓扑信息和使用的OAM技术信息；
12、所述OAM统一管理中心根据所述各个MP的信息建立所述管理维护集合，所述的管理维护集合可以为MD或MEG；
如图2所示，所述OAM统一管理中心建立MD1，MD1包括使用一种OAM技术(CFM)的MP，即Switch A上的MP3和Switch B上的MP1；建立MD2，MD2包括使用另一种OAM技术(BFD)的MP，即所述Switch C上的MP4和Switch B上的MP2建立MD2；
13、所述OAM统一管理中心为需要进行OAM联动的管理维护集合建立联动信息，所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，其中，当一个网络设备上有属于不同管理维护集合的多个MP时，所述多个MP为衔接MP。一个网络设备上有属于一个管理维护集合的一个MP，一个网络设备上有多个管理维护集合时，属于各个管理维护集合的多个MP为衔接MP。
所述为需要进行OAM联动的管理维护集合建立联动信息也可以包括为所述需要进行OAM联动的管理维护集合建立联动属性。
其中，所述需要进行OAM联动的管理维护集合对应的网络包括至少一个相同的网络设备或者覆盖相同的路径。
如图2所示，MD1和MD2对应的网络包括一个相同的网络设备Switch B，则同一用户流量会流经MD1和MD2，而如果MD1或MD2中出现故障，需要通知到另一MD，以使另一MD相应调整用户流量的流向，则确定MD1和MD2需要进行OAM联动；
所述OAM统一管理中心为需要进行OAM联动的管理维护集合，即MD1和MD2建立联动信息，所述为MD1和MD2建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，比如图2中位于Switch B上的MP1和MP2，MP1属于MD1，MP2属于MD2，MP1和MP2同位于Switch B上，则MP1和MP2可以作为衔接MP，则所述OAM统一管理中心在MP1上添加“联动到MP2”的联动属性，在MP2上添加“联动到MP1”的联动属性；
所述为MD1和MD2建立联动信息也可以包括为MD1和MD2建立联动属性，比如将MD1添加“联动到MD2”的联动属性，将MD2添加“联动到MD1”的联动属性。
2、如图2所示，当Switch B和Switch C之间的链路故障时，这里只是示例，本发 明实施例的故障还包括网络设备或节点故障等其他类型的故障，或者，本发明实施例的故障也包括链路性能下降或者网络设备或节点性能下降等，假设使用BFD技术的Switch C上的MP4最先检测到该链路故障，MP4向统一OAM管理中心发送故障告警消息；
具体的，所述OAM统一管理中心接收MP4采用网络配置协议(Network Configuration Protocol,NETCONF)传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息，其中，使用所述IETF YANG Data Model格式的所述通用OAM管理数据模型转换成XML形式的数据可以采用现有标准的规则；所述故障告警消息包括所述故障信息，所述故障信息包括故障位置、故障状态，故障内容，所述的故障位置包括发生故障的网络设备或链路的位置信息等。可选地，所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，所述故障发现设备的位置信息和/或故障上报设备的位置信息包括所述故障发现设备和/或故障上报设备的节点标识，所述故障发现设备和/或故障上报设备所属的第一管理维护集合等，比如MP4的节点标识，MP4所属的MD等，则所述OAM统一管理中心可以根据这些信息得到发送该故障告警消息的MP的信息，比如所属的第一管理维护集合等信息，并查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，而且OAM统一管理中心也可以根据这些信息，可以不用向所述故障发现设备和/或故障上报设备发送故障通知消息；所述通用OAM管理数据模型可以为：
Figure PCTCN2015088793-appb-000001
所述通用OAM管理数据模型的对象是根据具体实例对所述通用OAM管理数据模型的相关参数进行填充和/或扩展得到。所述具体实例可能与具体OAM技术相关，也可能不相关。比如本发明实施例根据与具体OAM技术无关的所述故障信息，对所述通用OAM管理数据模型的相关参数进行填充和/或扩展得到所述通用OAM管理数据模型的 对象。
3、所述OAM统一管理中心接收所述故障告警消息后，查询OAM数据库获得与MD2联动的MD1；
具体的，如果所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，则根据所述衔接MP的联动属性，找到与所述衔接MP位于同一网络设备的其他所述衔接MP，并根据所述衔接MP所属的MD找到联动的MD，比如如果为MD1和MD2建立联动信息包括为衔接MP，即为MP1添加“联动到MP2”的联动属性，为MP2添加“联动到MP1”的联动属性，则根据所述MP2的联动属性找到所述MP1，并根据所述MP1找到所述MP1所属的所述MD1；如果所述为需要进行OAM联动的管理维护集合建立联动信息也包括为所述需要进行OAM联动的管理维护集合建立联动属性，比如将MD1添加“联动到MD2”的联动属性，将MD2添加“联动到MD1”的联动属性，则可以直接根据所述管理维护集合的联动属性找到与所述MD2联动的所述MD1。
4、所述OAM统一管理中心向MD1中的所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息。
所述OAM统一管理中心向MD1中的所有的MP发送故障通知消息；或者所述OAM统一管理中心也可以向MD1中的根据策略确定的MP发送故障通知消息，具体的策略本发明实施例不加以限定，都属于本发明实施例的保护范围；本发明实施例中，所述OAM统一管理中心向MD1中所有的MP，即MP1和MP3发送故障通知消息；所述OAM统一管理中心向MP1和MP3发送采用NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息，其中，使用所述IETF YANG Data Model格式的所述通用OAM管理数据模型转换成XML形式的数据可以采用现有标准的规则；所述故障通知消息包括所述故障信息，所述故障信息包括故障位置、故障状态，故障内容，所述的故障位置包括发生故障的网络设备或链路的位置信息等。可选地，如果所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，则所述故障通知消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，所述故障发现设备的位置信息和/或故障上报设备的位置信息包括所述故障发现设备和/或故障上报设备的节点标识，所述故障发现设备和/或故障上报设备所属的第一管理维护集合等，比如MP4的节点标识，MP4所属 的MD等；MP1和MP3则可以根据自己的情况进行故障联动，比如启用备用通道等。所述通用OAM管理数据模型可以为：
Figure PCTCN2015088793-appb-000002
所述通用OAM管理数据模型的对象为根据具体实例对所述通用OAM管理数据模型的相关参数进行填充和/或扩展得到。所述具体实例可能与具体OAM技术相关，也可能不相关。比如本发明实施例根据与具体OAM技术无关的所述故障信息，对所述通用OAM管理数据模型的相关参数进行填充和/或扩展得到所述通用OAM管理数据模型的对象。
可选地，所述OAM统一管理中心也可以向和MP4位于同一MD的其他MP发送所述故障通知消息，比如所述OAM统一管理中心可以向MP2发送所述故障通知消息；
至于MD2中使用BFD技术的其他MP，比如MP2后来检测到该链路故障的时候，如果该MP2已经接收到所述OAM统一管理中心发送的故障通知消息，则不需要再向所述OAM统一管理中心发送故障告警消息，如果该MP2还没有接收到所述OAM统一管理中心发送的故障通知消息，则可以再向所述OAM统一管理中心发送故障告警消息。
可选地，本发明实施例的故障告警消息或故障通知消息也可以采用扩展简单网络管理协议(Simple Network Management Protocol,SNMP)来传递。
可选地，本发明实施例中所述OAM统一管理中心也可以接收第一管理维护集合的MP采用现有技术的方法发送的故障告警消息，所述故障告警消息包括故障信息，所述现有技术的方法和所述MP使用的OAM技术相关；所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；所述OAM统一管理中心将所述故障信息转换为通用OAM管理数据模型的对象；所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息，所述故障通知消息采用NETCONF传递的XML形式的数据，所述XML形式的数据由所述通用OAM管理数据 模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息，其中，使用所述IETF YANG Data Model格式的所述通用OAM管理数据模型转换成XML形式的数据可以采用现有标准的规则。
可选地，本发明实施例中所述OAM统一管理中心也可以接收第一管理维护集合的MP采用现有技术的方法发送的故障告警消息，所述故障告警消息包括故障信息，所述现有技术的方法和所述MP使用的OAM技术相关；所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息，所述故障通知消息采用现有技术的方法发送，所述现有技术的方法与所述MP使用的OAM技术相关。
这样，本发明实施例可以兼容支持现有技术的方法发送故障告警消息或故障通知消息，而不支持基于通用OAM管理数据模型的方法的MP。
下面结合图3的应用场景，对本发明实施例提供的又一种网络的操作管理维护OAM方法进行介绍，
如图3所示为多层OAM(Multi-layer OAM)的场景，底层为标签交换路径LSP层，然后是伪线PW层和多段伪线MS-PW层，当然这里只是示例，跨层可以包括其它层，每一层使用对应该层网络技术的OAM技术，当运营商终结边缘路由器1和运营商交换边缘路由器1之间的链路故障时，这里只是示例，本发明实施例的故障还包括网络设备或节点故障等其他类型的故障，或者，本发明实施例的故障也包括链路性能下降或者网络设备或节点性能下降等，位于不同层的管理维护集合的MP都可能检测到所述链路故障，都可能会发送故障告警消息，则可能会产生告警风暴，采用本发明实施例的一种网络的操作管理维护OAM方法，则可以统一在管理平面对相关故障告警进行通告并抑制，与具体OAM技术解耦合，极大的降低了实现难度，从而更容易的避免这种情况的出现。
具体的，每一层的各个路由器上分别都设置有MP，OAM统一管理中心可以收集所述OAM统一管理中心管理的网络中各个MP的信息，所述各个MP的信息包括所述各个MP的网络拓扑信息和使用的OAM技术信息；OAM统一管理中心根据所述各个MP的信息建立管理维护集合，所述的管理维护集合可以为MD，比如可以将每一层划为一个MD；所述的管理维护集合也可以为MEG，比如将各层所有的MP都划归一个MD， 通过不同的MEG来区分各层，即每一层划归一个MEG，MEG中通过MEG-LEVEL这个属性来区分不同层的不同OAM技术。
所述OAM统一管理中心为需要进行OAM联动的管理维护集合建立联动信息，所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，其中，当一个网络设备上有属于不同管理维护集合的多个MP时，所述多个MP为衔接MP。一个网络设备上有属于一个管理维护集合的一个MP，一个网络设备上有多个管理维护集合时，属于各个管理维护集合的多个MP为衔接MP。
所述为需要进行OAM联动的管理维护集合建立联动信息也可以包括为所述需要进行OAM联动的管理维护集合建立联动属性。
其中，所述需要进行OAM联动的管理维护集合对应的网络包括至少一个相同的网络设备或者覆盖相同的路径。
如图3所示，各层的管理维护集合对应的网络拓扑覆盖相同的路径，则出现如图3所示的链路故障时，各层的管理维护集合的MP都可能检测到该链路故障并发送故障告警消息，产生告警风暴，因此最先检测并发送故障告警消息的某层的管理维护集合的MP需要通知到另外的层的管理维护集合的MP，以使另外的层的管理维护集合的MP进行告警抑制，不再发送故障告警消息，则确定各层的管理维护集合都需要进行OAM联动；本发明实施例也可以根据策略确定只让某些层的管理维护集合之间进行OAM联动；
所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，比如图3中不同管理维护集合是跨层，每一层在物理上覆盖相同的路径，OAM统一管理中心则将各个网络设备上有属于不同管理维护集合的多个MP作为衔接MP，并为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，比如运营商终结边缘路由器1上有三个MP，属于LSP层的管理维护集合的MP-LSP-T-PE1、属于PW层的管理维护集合的MP-PW-T-PE1和属于多段PW层的管理维护集合的MP-MS-PW-T-PE1，则所述OAM统一管理中心将这些MP作为衔接MP，并给这些衔接MP添加联动属性，给MP-LSP-T-PE1添加“联动到MP-PW-T-PE1”和“联动到MP-MS-PW-T-PE1”的联动属性，给MP-PW-T-PE1添加“联动到MP-LSP-T-PE1”和“联动到MP-MS-PW-T-PE1”的联动属性，给MP-MS-PW-T-PE1添加“联动到MP-LSP-T-PE1”和“联动到MP-PW-T-PE1”的联动属性。
所述为需要进行OAM联动的管理维护集合建立联动信息也可以包括为所述需要进行OAM联动的管理维护集合建立联动属性，比如将LSP层的管理维护集合添加“联动到PW层的管理维护集合”和“联动到MS-PW层的管理维护集合”的联动属性，将PW层的管理维护集合添加“联动到LSP层的管理维护集合”和“联动到MS-PW层的管理维护集合”的联动属性，将MS-PW层的管理维护集合添加“联动到LSP层的管理维护集合”和“联动到PW层的管理维护集合”的联动属性。
如图3所示，当运营商终结边缘路由器1和运营商交换边缘路由器1之间的链路故障时，假设LSP层的管理维护集合的MP，即，MP-LSP-T-PE1，最先检测到该链路故障，MP-LSP-T-PE1向统一OAM管理中心发送故障告警消息；
具体的，所述OAM统一管理中心接收MP-LSP-T-PE1采用NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息，其中，使用所述IETF YANG Data Model格式的所述通用OAM管理数据模型转换成XML形式的数据可以采用现有标准的规则；所述故障告警消息包括所述故障信息，所述故障信息包括故障位置、故障状态，故障内容，所述的故障位置包括发生故障的网络设备或链路的位置信息等。可选地，所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，所述故障发现设备的位置信息和/或故障上报设备的位置信息包括所述故障发现设备和/或故障上报设备的节点标识，所述故障发现设备和/或故障上报设备所属的第一管理维护集合等，比如包括MP-LSP-T-PE1的节点标识，MP-LSP-T-PE1所属的MD，MP-LSP-T-PE1所属的MEG等，则所述OAM统一管理中心可以根据这些信息得到发送该故障告警消息的MP的信息，比如所属的第一管理维护集合等信息，并查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，而且OAM统一管理中心也可以根据这些信息，可以不用向所述故障发现设备和/或故障上报设备发送故障通知消息；所述通用OAM管理数据模型可以为：
Figure PCTCN2015088793-appb-000003
Figure PCTCN2015088793-appb-000004
所述通用OAM管理数据模型的对象为根据具体实例对所述通用OAM管理数据模型的相关参数进行填充和/或扩展得到。所述具体实例可能与具体OAM技术相关，也可能不相关。比如本发明实施例根据与具体OAM技术无关的所述故障信息，对所述通用OAM管理数据模型的相关参数进行填充和/或扩展得到所述通用OAM管理数据模型的对象。
所述OAM统一管理中心接收所述故障告警消息后，查询OAM数据库获得与所述LSP层的管理维护集合联动的管理维护集合，也即PW层的管理维护集合和MS-PW层的管理维护集合；
具体的，如果所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，则根据所述衔接MP的联动属性，找到与所述衔接MP位于同一网络设备的其他所述衔接MP，并根据所述衔接MP所属的管理维护集合找到联动的管理维护集合，比如根据LSP层的MP-LSP-T-PE1的“联动到MP-PW-T-PE1”和“联动到MP-MS-PW-T-PE1”的联动属性，找到与MP-LSP-T-PE1位于同一网络设备的其他衔接MP，即MP-PW-T-PE1和MP-MS-PW-T-PE1，并根据MP-PW-T-PE1和MP-MS-PW-T-PE1所属的管理维护集合找到联动的管理维护集合，即PW层的管理维护集合和MS-PW层的管理维护集合；
如果所述为需要进行OAM联动的管理维护集合建立联动信息也包括为所述需要进行OAM联动的管理维护集合建立联动属性，则可以直接根据所述管理维护集合的联动属性找到与所述LSP层的管理维护集合联动的管理维护集合，也即PW层的管理维护集合和MS-PW层的管理维护集合；
所述OAM统一管理中心向与所述LSP层的管理维护集合联动的管理维护集合，即PW层的管理维护集合和MS-PW层的管理维护集合中的所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息。
所述OAM统一管理中心向PW层的管理维护集合和MS-PW层的管理维护集合中的所有的MP发送故障通知消息；或者所述OAM统一管理中心也可以向PW层的管理维护集合和MS-PW层的管理维护集合中的根据策略确定的MP发送故障通知消息，具体的策略本发明实施例不加以限定，都属于本发明实施例的保护范围；本发明实施例中，所述OAM统一管理中心向PW层的管理维护集合和MS-PW层的管理维护集合中所有的MP发送故障通知消息；所述OAM统一管理中心向需要进行故障联动的MP发送采 用NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息，其中，使用所述IETF YANG Data Model格式的所述通用OAM管理数据模型转换成XML形式的数据可以采用现有标准的规则；所述故障通知消息包括所述故障信息，所述故障信息包括故障位置、故障状态，故障内容，所述的故障位置包括发生故障的网络设备或链路的位置信息等。可选地，如果所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，则所述故障通知消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，所述故障发现设备的位置信息和/或故障上报设备的位置信息包括所述故障发现设备和/或故障上报设备的节点标识，所述故障发现设备和/或故障上报设备所属的第一管理维护集合等，比如MP-LSP-T-PE1的节点标识，MP-LSP-T-PE1所属的MD，MP-LSP-T-PE1所属的MEG等；需要进行故障联动的MP则可以根据自己的情况进行故障联动，比如进行告警抑制，检测到该链路故障的时候不再发送故障告警消息。所述通用OAM管理数据模型可以为：
Figure PCTCN2015088793-appb-000005
所述通用OAM管理数据模型的对象是根据具体实例对所述通用OAM管理数据模型的相关参数进行填充和/或扩展得到。所述具体实例可能与具体OAM技术相关，也可能不相关。比如本发明实施例根据与具体OAM技术无关的所述故障信息，对所述通用OAM管理数据模型的相关参数进行填充和/或扩展得到所述通用OAM管理数据模型的对象。
可选地，所述OAM统一管理中心也可以向和MP-LSP-T-PE1位于同一管理维护集合的其他MP发送故障通知消息，比如所述OAM统一管理中心可以向LSP层的其他MP发送故障通知消息。
可选地，本发明实施例的故障告警消息或故障通知消息也可以采用扩展SNMP来传递。
可选地，本发明实施例中所述OAM统一管理中心也可以接收第一管理维护集合的MP采用现有技术的方法发送的故障告警消息，所述故障告警消息包括故障信息，所述现有技术的方法和所述MP使用的OAM技术相关；所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；所述OAM统一管理中心将所述故障信息转换为通用OAM管理数据模型的对象；所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息，所述故障通知消息采用NETCONF传递的XML形式的数据，所述XML形式的数据由所述通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息，其中，使用所述IETF YANG Data Model格式的所述通用OAM管理数据模型转换成XML形式的数据可以采用现有标准的规则。
可选地，本发明实施例中所述OAM统一管理中心也可以接收第一管理维护集合的MP采用现有技术的方法发送的故障告警消息，所述故障告警消息包括故障信息，所述现有技术的方法和所述MP使用的OAM技术相关；所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息，所述故障通知消息采用现有技术的方法发送，所述现有技术的方法与所述MP使用的OAM技术相关。
这样，本发明实施例可以兼容支持现有技术的方法发送故障告警消息或故障通知消息，而不支持基于通用OAM管理数据模型的方法的MP。
如图4所示，本发明实施例还提供一种操作管理维护OAM统一管理中心，包括：
接收单元401，用于接收管理维护节点MP采用发送的故障告警消息，所述故障告警消息包括故障信息；
确定单元402，用于根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；
处理单元403，用于查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数 据库保存有不同管理维护集合的联动信息；
发送单元404，用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息。
可选地，所述管理维护集合包括管理维护域MD或管理维护实体组MEG。
可选地，所述确定单元402，具体用于根据所述故障告警消息的内容确定所述第一管理维护集合；或者
根据所述故障告警消息的源地址确定所述第一管理维护集合。
可选地，所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，则所述确定单元具体用于根据所述故障信息、所述故障发现设备的位置信息和所述故障上报设备的位置信息中的至少一个确定所述第一管理维护集合。
可选地，所述OAM统一管理中心还包括建立单元，所述建立单元具体包括：
收集子单元，用于收集所述OAM统一管理中心管理的网络中各个MP的信息，所述各个MP的信息包括所述各个MP的网络拓扑信息和使用的OAM技术信息；
第一建立子单元，用于根据所述各个MP的信息建立所述管理维护集合；
第二建立子单元，用于为需要进行OAM联动的管理维护集合建立联动信息，所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，其中，当一个网络设备上有属于不同管理维护集合的多个MP时，所述多个MP为衔接MP。
可选地，所述需要进行OAM联动的管理维护集合对应的网络包括至少一个相同的网络设备或者覆盖相同的路径。
可选地，所述接收单元401，具体用于接收所述MP采用网络配置协议NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
可选地，所述发送单元403，具体用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送采用NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
如图5所示，本发明实施例还提供一种网络系统，包括：
管理维护节点MP 501，用于向如上所述的操作管理维护OAM统一管理中心502发送故障告警消息，所述故障告警消息包括故障信息；
如上所述的OAM统一管理中心502，用于根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；并用于查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；并用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息；
所述第二管理维护集合中所有的MP或者根据策略确定的MP 503，用于根据所述故障通知消息进行故障联动。
如图6所示，本发明实施例还提供一种操作管理维护OAM统一管理中心，包括：
收发器601、处理器602、存储器603和总线604，该收发器601、处理器602和存储器603通过总线604连接并完成相互间的通信，其中：
该总线604可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、外部设备互连(Peripheral Component，PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，EISA)总线等。该总线604可以分为地址总线、数据总线、控制总线等。为便于表示，图中仅用一条线表示，但并不表示仅有一根总线或一种类型的总线。
存储器603用于存储程序代码，该程序代码包括操作指令。存储器603可能包括高速随机存储器(random access memory，RAM)，也可能包括非易失性存储器(non-volatile memory)，例如磁盘存储器。
处理器602可能是一个中央处理器(Central Processing Unit，CPU)，或者是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本发明实施例的一个或多个集成电路。
收发器601可以为接口。
收发器601，用于接收接收管理维护节点MP发送的故障告警消息，所述故障告警消息包括故障信息；
处理器602，用于调用存储器603中的程序代码，用以执行以下操作：
根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；查询OAM数据库获得与所述第一管理维护集 合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；
收发器601，还用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息。
本发明实施例的装置的功能实现和方法属于同一发明构思，可以参考方法，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的模块及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或模块的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能模块可以集成在一个处理模块中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个模块中。
所述功能如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部 分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。

Claims (17)

  1. 一种网络的操作管理维护OAM方法，其特征在于，包括：
    OAM统一管理中心接收管理维护节点MP发送的故障告警消息，所述故障告警消息包括故障信息；
    所述OAM统一管理中心根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；
    所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；
    所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息。
  2. 根据权利要求1所述的方法，其特征在于，
    所述管理维护集合包括管理维护域MD或管理维护实体组MEG。
  3. 根据权利要求1或2所述的方法，其特征在于，所述OAM统一管理中心根据所述故障告警消息确定所述第一管理维护集合具体包括：
    所述OAM统一管理中心根据所述故障告警消息的内容确定所述第一管理维护集合；或者
    所述OAM统一管理中心根据所述故障告警消息的源地址确定所述第一管理维护集合。
  4. 根据权利要求3所述的方法，其特征在于，
    所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，则所述OAM统一管理中心根据所述故障告警消息的内容确定所述第一管理维护集合具体包括：
    所述OAM统一管理中心根据所述故障信息、所述故障发现设备的位置信息和所述故障上报设备的位置信息中的至少一个确定所述第一管理维护集合。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述OAM统一管理中心查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合之前还包括建立所述OAM数据库的步骤；
    所述OAM统一管理中心建立所述OAM数据库包括：
    所述OAM统一管理中心收集所述OAM统一管理中心管理的网络中各个MP的信 息，所述各个MP的信息包括所述各个MP的网络拓扑信息和使用的OAM技术信息；
    所述OAM统一管理中心根据所述各个MP的信息建立所述管理维护集合；
    所述OAM统一管理中心为需要进行OAM联动的管理维护集合建立联动信息，所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，其中，当一个网络设备上有属于不同管理维护集合的多个MP时，所述多个MP为衔接MP。
  6. 根据权利要求5所述的方法，其特征在于，
    所述需要进行OAM联动的管理维护集合对应的网络包括至少一个相同的网络设备或者覆盖相同的路径。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述OAM统一管理中心接收管理维护节点MP发送的故障告警消息具体包括：
    所述OAM统一管理中心接收所述MP采用网络配置协议NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
  8. 根据权利要求1至7任一所述的方法，其特征在于，所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息具体包括：
    所述OAM统一管理中心向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送采用NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
  9. 一种操作管理维护OAM统一管理中心，其特征在于，包括：
    接收单元，用于接收管理维护节点MP采用发送的故障告警消息，所述故障告警消息包括故障信息；
    确定单元，用于根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；
    处理单元，用于查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；
    发送单元，用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息。
  10. 根据权利要求9所述的OAM统一管理中心，其特征在于，
    所述管理维护集合包括管理维护域MD或管理维护实体组MEG。
  11. 根据权利要求9或10所述的OAM统一管理中心，其特征在于，
    所述确定单元，具体用于根据所述故障告警消息的内容确定所述第一管理维护集合；或者
    根据所述故障告警消息的源地址确定所述第一管理维护集合。
  12. 根据权利要求11所述的OAM统一管理中心，其特征在于，
    所述故障告警消息还包括故障发现设备的位置信息和/或故障上报设备的位置信息，则所述确定单元具体用于根据所述故障信息、所述故障发现设备的位置信息和所述故障上报设备的位置信息中的至少一个确定所述第一管理维护集合。
  13. 根据权利要求9至12任一所述的OAM统一管理中心，其特征在于，所述OAM统一管理中心还包括建立单元，所述建立单元具体包括：
    收集子单元，用于收集所述OAM统一管理中心管理的网络中各个MP的信息，所述各个MP的信息包括所述各个MP的网络拓扑信息和使用的OAM技术信息；
    第一建立子单元，用于根据所述各个MP的信息建立所述管理维护集合；
    第二建立子单元，用于为需要进行OAM联动的管理维护集合建立联动信息，所述为需要进行OAM联动的管理维护集合建立联动信息包括为衔接MP添加联动到其他管理维护集合的衔接MP的联动属性，其中，当一个网络设备上有属于不同管理维护集合的多个MP时，所述多个MP为衔接MP。
  14. 根据权利要求13所述的OAM统一管理中心，其特征在于，
    所述需要进行OAM联动的管理维护集合对应的网络包括至少一个相同的网络设备或者覆盖相同的路径。
  15. 根据权利要求9至14任一所述的OAM统一管理中心，其特征在于，
    所述接收单元，具体用于接收所述MP采用网络配置协议NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
  16. 根据权利要求9至15任一所述的OAM统一管理中心，其特征在于，
    所述发送单元，具体用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送采用NETCONF传递的XML形式的数据，所述XML形式的数据由通用OAM管理数据模型的对象转换而来，所述通用OAM管理数据模型使用IETF YANG Data Model格式生成，所述通用OAM管理数据模型的对象携带所述故障信息。
  17. 一种网络系统，其特征在于，包括：
    管理维护节点MP，用于向如权利要求9至16任一所述的操作管理维护OAM统一管理中心发送故障告警消息，所述故障告警消息包括故障信息；
    如权利要求9至16任一所述的OAM统一管理中心，用于根据所述故障告警消息确定所述MP所属的第一管理维护集合，所述第一管理维护集合包括使用第一种OAM技术的MP；并用于查询OAM数据库获得与所述第一管理维护集合联动的第二管理维护集合，所述第二管理维护集合包括使用第二种OAM技术的MP，所述OAM数据库保存有不同管理维护集合的联动信息；并用于向所述第二管理维护集合中所有的MP或者根据策略确定的MP发送故障通知消息，所述故障通知消息包括所述故障信息；
    所述第二管理维护集合中所有的MP或者根据策略确定的MP，用于根据所述故障通知消息进行故障联动。
PCT/CN2015/088793 2014-10-23 2015-09-01 一种网络的操作管理维护oam方法、装置和系统 WO2016062166A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15852154.2A EP3203684B1 (en) 2014-10-23 2015-09-01 Method, apparatus and system for network operations, administration and maintenance
US15/494,128 US10237124B2 (en) 2014-10-23 2017-04-21 Network operation, administration, and maintenance (OAM) method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410571235.6 2014-10-23
CN201410571235.6A CN105591775B (zh) 2014-10-23 2014-10-23 一种网络的操作管理维护oam方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/494,128 Continuation US10237124B2 (en) 2014-10-23 2017-04-21 Network operation, administration, and maintenance (OAM) method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2016062166A1 true WO2016062166A1 (zh) 2016-04-28

Family

ID=55760266

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/088793 WO2016062166A1 (zh) 2014-10-23 2015-09-01 一种网络的操作管理维护oam方法、装置和系统

Country Status (4)

Country Link
US (1) US10237124B2 (zh)
EP (1) EP3203684B1 (zh)
CN (1) CN105591775B (zh)
WO (1) WO2016062166A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108023782A (zh) * 2017-12-29 2018-05-11 华东师范大学 一种基于维修记录的设备故障预警方法
WO2018190292A1 (ja) 2017-04-10 2018-10-18 三菱瓦斯化学株式会社 樹脂組成物、プリプレグ、金属箔張積層板、樹脂シート及びプリント配線板

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107809336B (zh) * 2017-11-16 2019-10-25 中国联合网络通信集团有限公司 一种ip ran网络的故障检测方法、装置
CN112714006B (zh) * 2019-10-24 2024-05-17 中兴通讯股份有限公司 链路故障状态通告方法、装置、设备及介质
US11108689B1 (en) * 2020-02-07 2021-08-31 Ciena Corporation Incorporating a generic associated channel (G-ACh) header and channel-type for connectivity fault management (CFM) packets over multi-protocol label switching (MPLS)
CN116112344B (zh) * 2023-04-11 2023-06-20 山东金宇信息科技集团有限公司 一种机房故障网络设备检测方法、设备及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132320A (zh) * 2007-09-18 2008-02-27 华为技术有限公司 检测接口故障的方法及网络节点设备
CN101826983A (zh) * 2010-04-02 2010-09-08 中兴通讯股份有限公司 双归保护倒换方法、装置和系统
EP2528272A1 (en) * 2010-01-22 2012-11-28 ZTE Corporation Dual-attached protection switching method based on vpls and system thereof
CN102843249A (zh) * 2011-06-21 2012-12-26 中兴通讯股份有限公司 一种分组传送网络中维护管理状态传递的方法和设备
CN102857362A (zh) * 2012-04-20 2013-01-02 福建星网锐捷网络有限公司 故障处理方法、装置和系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1313950C (zh) * 2001-11-29 2007-05-02 上海复旦光华信息科技股份有限公司 域用户集中授权管理系统及其方法
US7855968B2 (en) * 2004-05-10 2010-12-21 Alcatel Lucent Alarm indication and suppression (AIS) mechanism in an ethernet OAM network
US20110174307A1 (en) * 2006-01-04 2011-07-21 Lessi Stephane Device for Supplying Oxygen to the Occupants of an Aircraft and Pressure Regulator for Such a Device
JP2008021116A (ja) * 2006-07-12 2008-01-31 Hitachi Ltd Ｓａｎ／ｎａｓ統合管理計算機及び方法
CN101174975B (zh) * 2006-11-03 2010-05-12 华为技术有限公司 一种以太网中的链路故障定位方法及系统
CN102185711B (zh) * 2011-04-26 2014-12-10 中兴通讯股份有限公司 一种检测混合网络中链路故障的方法及设备
CN102231674A (zh) * 2011-06-17 2011-11-02 中兴通讯股份有限公司 以太网远端故障的处理方法及装置
US9246747B2 (en) * 2012-11-15 2016-01-26 Hong Kong Applied Science and Technology Research Co., Ltd. Adaptive unified performance management (AUPM) with root cause and/or severity analysis for broadband wireless access networks

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132320A (zh) * 2007-09-18 2008-02-27 华为技术有限公司 检测接口故障的方法及网络节点设备
EP2528272A1 (en) * 2010-01-22 2012-11-28 ZTE Corporation Dual-attached protection switching method based on vpls and system thereof
CN101826983A (zh) * 2010-04-02 2010-09-08 中兴通讯股份有限公司 双归保护倒换方法、装置和系统
CN102843249A (zh) * 2011-06-21 2012-12-26 中兴通讯股份有限公司 一种分组传送网络中维护管理状态传递的方法和设备
CN102857362A (zh) * 2012-04-20 2013-01-02 福建星网锐捷网络有限公司 故障处理方法、装置和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3203684A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018190292A1 (ja) 2017-04-10 2018-10-18 三菱瓦斯化学株式会社 樹脂組成物、プリプレグ、金属箔張積層板、樹脂シート及びプリント配線板
KR20190130130A (ko) 2017-04-10 2019-11-21 미츠비시 가스 가가쿠 가부시키가이샤 수지 조성물, 프리프레그, 금속박 피복 적층판, 수지 시트 및 프린트 배선판
CN108023782A (zh) * 2017-12-29 2018-05-11 华东师范大学 一种基于维修记录的设备故障预警方法
CN108023782B (zh) * 2017-12-29 2020-11-27 华东师范大学 一种基于维修记录的设备故障预警方法

Also Published As

Publication number Publication date
EP3203684B1 (en) 2020-11-04
US10237124B2 (en) 2019-03-19
CN105591775A (zh) 2016-05-18
US20170230234A1 (en) 2017-08-10
CN105591775B (zh) 2019-10-25
EP3203684A4 (en) 2017-10-25
EP3203684A1 (en) 2017-08-09

Similar Documents

Publication Publication Date Title
WO2016062166A1 (zh) 一种网络的操作管理维护oam方法、装置和系统
EP3188409B1 (en) Oam mechanisms for evpn active-active services
US10142203B2 (en) Ethernet fault management systems and methods
CN102833108B (zh) 故障点位置信息处理方法及设备
US7912055B1 (en) Method and apparatus for configuration and analysis of network multicast routing protocols
WO2016062165A1 (zh) 一种实现操作管理维护功能的方法及装置
CN104518967A (zh) 路由方法、设备和系统
WO2011060651A1 (zh) 故障链路定位方法、告警根因分析方法及设备、系统
CN102647312B (zh) 一种整网组播拓扑的探测方法及装置
WO2015143810A1 (zh) 节点故障检测方法及装置
WO2020088683A1 (zh) 处理路由事件记录表项的方法、网络设备和控制设备
JP5949035B2 (ja) ネットワーク機器設定装置、設定システム、設定方法及び設定プログラム
WO2009009992A1 (fr) Procédé, système, extrémité de source et extrémité de destination pour indexer le trajet de commutation d'étiquettes au moyen d'une étiquette
US8051202B2 (en) Method and apparatus for providing alarm correlation for a gateway router
CN102315987B (zh) 环网保护组链路回切方法及装置
US8670299B1 (en) Enhanced service status detection and fault isolation within layer two networks
WO2011124178A2 (zh) 故障检测方法、路由节点及系统
CN102571464B (zh) 链路的跟踪处理方法及系统
WO2014048126A1 (zh) 业务流量保护方法和装置
CN112751701B (zh) 用于管理网络装置的系统、方法及计算机可读介质
WO2013075476A1 (zh) 以太网链路检测方法及装置
CN103780420A (zh) Vpls环境下以太网连通性检测的自动配置方法和系统
JP2004086522A (ja) 通信ネットワーク監視システム
CN106657355B (zh) 一种集群管理方法及设备
CN115604168A (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: 15852154

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015852154

Country of ref document: EP