(19)
(11)EP 3 203 684 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
04.11.2020 Bulletin 2020/45

(21)Application number: 15852154.2

(22)Date of filing:  01.09.2015
(51)International Patent Classification (IPC): 
H04L 12/24(2006.01)
(86)International application number:
PCT/CN2015/088793
(87)International publication number:
WO 2016/062166 (28.04.2016 Gazette  2016/17)

(54)

METHOD, APPARATUS AND SYSTEM FOR NETWORK OPERATIONS, ADMINISTRATION AND MAINTENANCE

VERFAHREN, VORRICHTUNG UND SYSTEM FÜR NETZWERKOPERATIONEN, VERWALTUNG UND WARTUNG

PROCÉDÉ, APPAREIL ET SYSTÈME POUR LES OPÉRATIONS, L'ADMINISTRATION ET LA MAINTENANCE DE RÉSEAU


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 23.10.2014 CN 201410571235

(43)Date of publication of application:
09.08.2017 Bulletin 2017/32

(73)Proprietor: Huawei Technologies Co., Ltd.
Longgang District Shenzhen, Guangdong 518129 (CN)

(72)Inventors:
  • WANG, Zitao
    Shenzhen Guangdong 518129 (CN)
  • WU, Qin
    Shenzhen Guangdong 518129 (CN)
  • HUANG, Yihong
    Shenzhen Guangdong 518129 (CN)
  • XIA, Liang
    Shenzhen Guangdong 518129 (CN)

(74)Representative: Epping - Hermann - Fischer 
Patentanwaltsgesellschaft mbH Schloßschmidstraße 5
80639 München
80639 München (DE)


(56)References cited: : 
EP-A1- 2 528 272
CN-A- 101 826 983
CN-A- 102 857 362
US-A1- 2014 136 685
CN-A- 101 132 320
CN-A- 102 843 249
US-A1- 2008 016 311
  
  • MOORE R E: "UTILIZING THE SNA ALERT IN THE MANAGEMENT OF MULTIVENDOR NETWORKS", IBM SYSTEMS JOURNAL, IBM CORP. ARMONK, NEW YORK, US, vol. 27, no. 1, 1 January 1988 (1988-01-01), pages 15-30, XP000811961, ISSN: 0018-8670
  • KERN A TAKACS ERICSSON A: "GMPLS RSVP-TE Extensions for OTN and SONET/SDH OAM Configuration; draft-kern-ccamp-rsvp-te-sdh-otn-oam-ext-0 0.txt", GMPLS RSVP-TE EXTENSIONS FOR OTN AND SONET/SDH OAM CONFIGURATION; DRAFT-KERN-CCAMP-RSVP-TE-SDH-OTN-OAM-EXT-0 0.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, 6 July 2009 (2009-07-06), XP015063105, [retrieved on 2009-07-06]
  • Y-X LI ET AL: "Telecom Ethernet OAM Research in the Metropolitans Area Network Multi-Operation Platform", APPERCEIVING COMPUTING AND INTELLIGENCE ANALYSIS, 2008. ICACIA 2008. INTERNATIONAL CONFERENCE ON, IEEE, PISCATAWAY, NJ, USA, 13 December 2008 (2008-12-13), pages 343-346, XP031415341, ISBN: 978-1-4244-3427-5
  • TSURUSAWA M ET AL: "Feasibility validation of management capability for an Ethernet based access network using Ethernet OAM functionality", NETWORK OPERATIONS AND MANAGEMENT SYMPOSIUM, 2008. NOMS 2008. IEEE, IEEE, PISCATAWAY, NJ, USA, 7 April 2008 (2008-04-07), pages 660-673, XP031290569, ISBN: 978-1-4244-2065-0
  • TOCHIO FUJITSU H VAN HELVOORT HAI GAOMING BV L XIA HUAWEI Y: "Gap Analysis for Layer and Technology Independent OAM Management in the Multi-Layer Environment; draft-txh-opsawg-lime-gap-analysis-00.txt" , GAP ANALYSIS FOR LAYER AND TECHNOLOGY INDEPENDENT OAM MANAGEMENT IN THE MULTI-LAYER ENVIRONMENT; DRAFT-TXH-OPSAWG-LIME-GAP-ANALYSIS-00.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1, 26 September 2014 (2014-09-26), pages 1-11, XP015101845, [retrieved on 2014-09-26]
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

TECHNICAL FIELD



[0001] The present invention relates to the field of network technologies, and in particular, to a network operation, administration, and maintenance OAM method, an apparatus, and a system.

BACKGROUND



[0002] With a rapid increase of network service traffic and service types, networks become more complex, and a higher requirement is imposed on network operation, administration, and maintenance (Operation Administration Maintenance, OAM). More attention is paid to technologies related to fault alarms.

[0003] In cross-layer or cross-domain scenarios, different network technologies may be deployed for different layers or different domains. Different network technologies may use different OAM technologies, for example, a connectivity fault management (Connectivity Fault Management, CFM) technology or a bidirectional forwarding detection (Bidirectional Forwarding Detection, BFD) technology. In these cross-layer or cross-domain scenarios, an existing technology related to fault alarms is bound to a specific OAM technology on a data plane network device. Complex mapping and conversion need to be performed, and implementation is difficult. Therefore, how to better perform a fault alarm in the cross-layer or cross-domain scenarios in which different OAM technologies are used needs to be resolved urgently.

[0004] US 2008/016311 A1 relates to a computer, which manages a SAN/NAS system, and comprises a configuration information acquisition part, and a configuration association part. The configuration information acquisition part respectively acquires NAS host configuration information managed by a NAS host, and storage configuration information managed by a storage system. The configuration association part retrieves from storage configuration information a second information element, which conforms to a first information element in SAN host configuration information, and associates the retrieved second information element to the first information element.

[0005] CN 102857362 A provides a fault processing method, device and system. The method comprises the following steps of receiving a fault event reported by a first linkage module after the first linkage module detects that a main pseudo wire (PW) between local equipment and far-end equipment has a fault; according to a preset linkage mapping relation, announcing the fault event to a second linkage module in the far-end equipment, which is in linkage with the first linkage module, so that the second linkage module carries out fault processing according to the fault event. The invention also provides a fault linkage device, a fault processing device and a fault processing system. When a link at the local equipment side has a fault, the far-end equipment in the embodiment of the invention can senses the fault in time, millisecond scale switching of user flow is realized, and the phenomenon that transferring of the user flow is stopped can be avoided.

SUMMARY



[0006] An OAM method, an OAM management center and a network system according to the independent claims are provided. Dependent claims provide preferred embodiments. To better perform a fault alarm in cross-layer or cross-domain scenarios in which different OAM technologies are used, embodiments of the present invention provide a network operation, administration, and maintenance OAM method, an apparatus, and a system.

[0007] According to a first aspect, a network operation, administration, and maintenance OAM method is provided, including:

receiving, by a unified OAM management center, a fault alarm message sent by a maintenance point MP, where the fault alarm message includes fault information;

determining, by the unified OAM management center according to the fault alarm message, a first maintenance set to which the MP belongs, where the first maintenance set includes MPs using a first OAM technology;

querying, by the unified OAM management center, an OAM database, to obtain a second maintenance set interacting with the first maintenance set, where the second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets; and

sending, by the unified OAM management center, a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, where the fault notification message includes the fault information. With reference to the first aspect, in a first possible implementation manner, the maintenance set includes a maintenance domain MD or a maintenance entity group MEG.



[0008] With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the determining, by the unified OAM management center according to the fault alarm message, a first maintenance set specifically includes:

determining, by the unified OAM management center, the first maintenance set according to content of the fault alarm message; or

determining, by the unified OAM management center, the first maintenance set according to a source address of the fault alarm message.



[0009] With reference to the second possible implementation manner of the first aspect, in a third possible implementation manner, the fault alarm message further includes location information of a fault discovery device and/or location information of a fault reporting device, and the determining, by the unified OAM management center, the first maintenance set according to content of the fault alarm message specifically includes:
determining, by the unified OAM management center, the first maintenance set according to at least one of the fault information, the location information of the fault discovery device, or the location information of the fault reporting device.

[0010] With reference to any one of the first aspect or the first to the third possible implementation manners of the first aspect, in a fourth possible implementation manner, before the querying, by the unified OAM management center, an OAM database, to obtain a second maintenance set interacting with the first maintenance set, the method further includes a step of establishing the OAM database, where
the establishing, by the unified OAM management center, the OAM database includes:

collecting, by the unified OAM management center, information about MPs in a network managed by the unified OAM management center, where the information about the MPs includes network topology information and information about a used OAM technology that are of the MPs;

establishing, by the unified OAM management center, the maintenance sets according to the information about the MPs; and

establishing, by the unified OAM management center, interaction information for a maintenance set that needs to perform OAM interaction, where the establishing interaction information for a maintenance set that needs to perform OAM interaction includes adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, where when there are multiple MPs that belong to different maintenance sets on one network device, the multiple MPs are connective MPs.



[0011] With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, networks corresponding to the maintenance sets that need to perform OAM interaction include at least one same network device or cover a same path.

[0012] With reference to any one of the first aspect or the first to the fifth possible implementation manners of the first aspect, in a sixth possible implementation manner, the receiving, by a unified OAM management center, a fault alarm message sent by a maintenance point MP specifically includes:
receiving, by the unified OAM management center, XML-form data transferred by the MP by using the Network Configuration Protocol NETCONF, where the XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.

[0013] With reference to any one of the first aspect or the first to the sixth possible implementation manners of the first aspect, in a seventh possible implementation manner, the sending, by the unified OAM management center, a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set specifically includes:
sending, by the unified OAM management center to all the MPs in the second maintenance set or the MP that is determined according to the policy, the XML-form data transferred by using the NETCONF, where the XML-form data is obtained by transforming the object of the unified OAM management data model, the unified OAM management data model is generated by using the IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.

[0014] According to a second aspect, an embodiment of the present invention provides a unified operation, administration, and maintenance OAM management center, including:

a receiving unit, configured to receive a fault alarm message sent by a maintenance point MP, where the fault alarm message includes fault information;

a determining unit, configured to determine, according to the fault alarm message, a first maintenance set to which the MP belongs, where the first maintenance set includes MPs using a first OAM technology;

a processing unit, configured to query an OAM database, to obtain a second maintenance set interacting with the first maintenance set, where the second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets; and

a sending unit, configured to send a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, where the fault notification message includes the fault information.



[0015] With reference to the second aspect, in a first possible implementation manner, the maintenance set includes a maintenance domain MD or a maintenance entity group MEG.

[0016] With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner, the determining unit is specifically configured to: determine the first maintenance set according to content of the fault alarm message; or
determine the first maintenance set according to a source address of the fault alarm message.

[0017] With reference to the second possible implementation manner of the second aspect, in a third possible implementation manner,
the fault alarm message further includes location information of a fault discovery device and/or location information of a fault reporting device, and the determining unit is specifically configured to determine the first maintenance set according to at least one of the fault information, the location information of the fault discovery device, or the location information of the fault reporting device.

[0018] With reference to any one of the second aspect or the first to the third possible implementation manners of the second aspect, in a fourth possible implementation manner, the unified OAM management center further includes an establishment unit, where the establishment unit specifically includes:

a collection subunit, configured to collect information about MPs in a network managed by the unified OAM management center, where the information about the MPs includes network topology information and information about a used OAM technology that are of the MPs;

a first establishment subunit, configured to establish the maintenance sets according to the information about the MPs; and

a second establishment subunit, configured to establish interaction information for a maintenance set that needs to perform OAM interaction, where the establishing interaction information for a maintenance set that needs to perform OAM interaction includes adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, where when there are multiple MPs that belong to different maintenance sets on one network device, the multiple MPs are connective MPs.



[0019] With reference to the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner, networks corresponding to the maintenance sets that need to perform OAM interaction include at least one same network device or cover a same path.

[0020] With reference to any one of the second aspect or the first to the fifth possible implementation manners of the second aspect, in a sixth possible implementation manner, the receiving unit is specifically configured to receive XML-form data transferred by the MP by using the Network Configuration Protocol NETCONF, where the XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.

[0021] With reference to any one of the second aspect or the first to the sixth possible implementation manners of the second aspect, in a seventh possible implementation manner, the sending unit is specifically configured to send, to all the MPs in the second maintenance set or the MP that is determined according to the policy, the XML-form data transferred by using the NETCONF, where the XML-form data is obtained by transforming the object of the unified OAM management data model, the unified OAM management data model is generated by using the IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.

[0022] According to a third aspect, an embodiment of the present invention provides a network system, including:

a maintenance point MP, configured to send a fault alarm message to the operation, administration, and maintenance unified OAM management center described above, where the fault alarm message includes fault information;

the unified OAM management center described above, configured to determine, according to the fault alarm message, a first maintenance set to which the MP belongs, where the first maintenance set includes MPs using a first OAM technology; configured to query an OAM database, to obtain a second maintenance set interacting with the first maintenance set, where the second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets; and configured to send a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, where the fault notification message includes the fault information; and

all the MPs in the second maintenance set or the MP that is determined according to the policy, configured to perform fault interaction according to the fault notification message.



[0023] According to the network operation, administration, and maintenance OAM method, the apparatus, and the system that are provided in the embodiments of the present invention, a related fault alarm may be centrally notified on a management plane, and is decoupled from a specific OAM technology, thereby greatly reducing an implementation difficulty.

BRIEF DESCRIPTION OF DRAWINGS



[0024] 

FIG. 1 is a schematic flowchart of a network operation, administration, and maintenance OAM method according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of an application scenario of a network operation, administration, and maintenance OAM method according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of an application scenario of a network operation, administration, and maintenance OAM method according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a unified operation, administration, and maintenance OAM management center 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 invention; and

FIG. 6 is a schematic structural diagram of a unified operation, administration, and maintenance OAM management center according to an embodiment of the present invention.


DESCRIPTION OF EMBODIMENTS



[0025] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0026] In addition, the terms "system" and "network" may be used interchangeably in this specification. The term "and/or" in this specification describes only an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. In addition, the character "/" in this specification generally indicates an "or" relationship between the associated objects.

[0027] In the following, preferred implementation manners of the present invention are described in detail with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are merely used to illustrate and explain the present invention, but are not intended to limit the present invention. In addition, the embodiments of the present application and features in the embodiments may be mutually combined in a case in which they do not conflict with each other.

[0028] As shown in FIG. 1, an embodiment of the present invention provides a network operation, administration, and maintenance OAM method, including:

S101: A unified OAM management center receives a fault alarm message sent by a maintenance point (Maintenance Point, MP), where the fault alarm message includes fault information.

S102: The unified OAM management center determines, according to the fault alarm message, a first maintenance set to which the MP belongs, where the first maintenance set includes MPs using a first OAM technology.

S103: The unified OAM management center queries an OAM database, to obtain a second maintenance set interacting with the first maintenance set, where the second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets.

S104: The unified OAM management center sends a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, where the fault notification message includes the fault information.



[0029] According to the network operation, administration, and maintenance OAM method provided in this embodiment of the present invention, a related fault alarm may be centrally notified on a management plane, and is decoupled from a specific OAM technology, thereby greatly reducing an implementation difficulty.

[0030] Optionally, the maintenance set includes a maintenance domain (Maintenance Domain, MD) or a maintenance entity group (Maintenance Entity Group, MEG).

[0031] Optionally, the determining, by the unified OAM management center according to the fault alarm message, a first maintenance set specifically includes:

determining, by the unified OAM management center, the first maintenance set according to content of the fault alarm message; or

determining, by the unified OAM management center, the first maintenance set according to a source address of the fault alarm message.



[0032] Optionally, the fault alarm message further includes location information of a fault discovery device and/or location information of a fault reporting device, and the determining, by the unified OAM management center, the first maintenance set according to content of the fault alarm message specifically includes:
determining, by the unified OAM management center, the first maintenance set according to at least one of the fault information, the location information of the fault discovery device, or the location information of the fault reporting device.

[0033] Optionally, the fault discovery device and the fault reporting device may be a same network device, that is, the network device discovers a fault and sends the fault alarm message to the unified OAM management center; or the fault discovery device and the fault reporting device may be different network devices. For example, after discovering a fault, the fault discovery device notifies the fault reporting device, and the fault reporting device sends the fault alarm message to the unified OAM management center. The unified OAM management center determines the first maintenance set according to at least one of the fault information, the location information of the fault discovery device, or the location information of the fault reporting device. The determining the first maintenance set according to the fault information may be determining the first maintenance set according to location information of a faulty network device or link in the fault information. The faulty network device or link, the fault discovery device, and the fault reporting device usually belong to one maintenance set. If at least one of the fault information, the location information of the fault discovery device, or the location information of the fault reporting device includes information about the first maintenance set, the first maintenance set may be determined.

[0034] Optionally, the fault alarm message may not include the location information of the fault discovery device or the location information of the fault reporting device. The unified OAM management center may obtain, according to the source address of the fault alarm message, for example, a source IP address, information about an MP sending the fault alarm message, for example, information about the first maintenance set to which the MP belongs.

[0035] Optionally, before the querying, by the unified OAM management center, an OAM database, to obtain a second maintenance set interacting with the first maintenance set, the method further includes a step of establishing the OAM database.

[0036] The establishing, by the unified OAM management center, the OAM database includes:

collecting information about MPs in a network managed by the unified OAM management center, where the information about the MPs includes network topology information and information about a used OAM technology that are of the MPs;

establishing, by the unified OAM management center, the maintenance sets according to the information about the MPs; and

establishing, by the unified OAM management center, interaction information for a maintenance set that needs to perform OAM interaction, where the establishing interaction information for a maintenance set that needs to perform OAM interaction includes adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, where when there are multiple MPs that belong to different maintenance sets on one network device, the multiple MPs are connective MPs.



[0037] Optionally, networks corresponding to the maintenance sets that need to perform OAM interaction include at least one same network device or cover a same path.

[0038] Optionally, the receiving, by a unified OAM management center, a fault alarm message sent by a maintenance point MP specifically includes:
receiving, by the unified OAM management center, XML-form data transferred by the MP by using the Network Configuration Protocol NETCONF, where the XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.

[0039] Optionally, the sending, by the unified OAM management center, a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set specifically includes:
sending, by the unified OAM management center to all the MPs in the second maintenance set or the MP that is determined according to the policy, the XML-form data transferred by using the NETCONF, where the XML-form data is obtained by transforming the object of the unified OAM management data model, the unified OAM management data model is generated by using the IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.

[0040] A network operation, administration, and maintenance OAM method provided in another embodiment of the present invention is described below with reference to an application scenario of FIG. 2.

[0041] As shown in FIG. 2, CFM is deployed in a network between a Switch A and a Switch B, and BFD is deployed in a network between the Switch B and a Switch C. In this way, when a link from the Switch B to the Switch C is faulty, the remote Switch A cannot sense the link fault between the Switch B and the Switch C, and therefore, still sends user traffic to the faulty link, thereby causing an interruption of the user traffic. According to the network operation, administration, and maintenance OAM method provided in this embodiment of the present invention, a related fault alarm may be centrally notified on a management plane, and is decoupled from a specific OAM technology, thereby greatly reducing an implementation difficulty. Therefore, it is easier to avoid this case.

[0042] A procedure of a network operation, administration, and maintenance OAM method in this embodiment of the present invention is as follows:
  1. 1. A unified OAM management center establishes an OAM database.


[0043] The establishing, by the unified OAM management center, the OAM database includes:
11. The unified OAM management center collects information about MPs in a network managed by the unified OAM management center, where the information about the MPs includes network topology information and information about a used OAM technology that are of the MPs.

[0044] In this embodiment of the present invention, the unified OAM management center is set to centrally manage the network. The unified OAM management center is a logical concept, may be physically an independent network device, for example, a switch or a router, or may be disposed in a network device. The unified OAM management center may be centralized, which is physically an independent network device or is disposed in a network device; or may be distributed, which is physically distributed in multiple independent network devices or is disposed in multiple network devices.

[0045] Multiple MPs are disposed in the network in this embodiment of the present invention, where the MP is configured to perform OAM detection or OAM measurement. The MP is also a logical concept, and may be physically disposed in a network device, for example, in a switch or a router. One or more MPs may be disposed in a network device, and multiple MPs in a network device may use different OAM technologies.

[0046] For example, two MPs are disposed on the Switch B in FIG. 2, namely, an MP1 and an MP2, where the MP1 uses a CFM technology, and the MP2 uses a BFD technology. One MP is disposed on the Switch A, namely, an MP3, where the MP3 uses the CFM technology. One MP is disposed on the Switch C, namely, an MP4, where the MP4 uses the BFD technology. The unified OAM management center may collect information about the MPs, namely, information about the MP1, the MP2, the MP3, and the MP4. The information about the MPs includes network topology information and information about the used OAM technologies that are of the MPs.
12. The unified OAM management center establishes the maintenance sets according to the information about the MPs, where the maintenance set may be an MD or an MEG.

[0047] As shown in FIG. 2, the unified OAM management center establishes an MD1, where the MD1 includes MPs using one OAM technology (CFM), namely, the MP3 on the Switch A and the MP1 on the Switch B; establishes an MD2, where the MD2 includes MPs using another OAM technology (BFD), namely, the MP4 on the Switch C and the MP2 on the Switch B. 13. The unified OAM management center establishes interaction information for a maintenance set that needs to perform OAM interaction, where the establishing interaction information for a maintenance set that needs to perform OAM interaction includes adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, where when there are multiple MPs that belong to different maintenance sets on one network device, the multiple MPs are connective MPs. When there is one MP that belongs to one maintenance set on a network device and there are multiple maintenance sets on a network device, multiple MPs that belong to maintenance sets are connective MPs.

[0048] The establishing interaction information for a maintenance set that needs to perform OAM interaction may also include establishing an interaction attribute for the maintenance set that needs to perform OAM interaction.

[0049] Networks corresponding to the maintenance sets that need to perform OAM interaction include at least one same network device or cover a same path.

[0050] As shown in FIG. 2, networks corresponding to the MD1 and the MD2 include a same network device, that is, the Switch B, and same user traffic flows through the MD1 and the MD2. If the MD1 or the MD2 is faulty, the other MD needs to be notified, so that the other MD correspondingly adjusts a flow direction of the user traffic. That is, it is determined that the MD1 and the MD2 need to perform OAM interaction.

[0051] The unified OAM management center establishes interaction information for a maintenance set that needs to perform OAM interaction, that is, the MD1 and the MD2. The establishing interaction information for the MD1 and the MD2 includes adding, to a connective MP, an interaction attribute of a connective MP interacting with another maintenance set. For example, in FIG. 2, for the MP1 and the MP2 that are located on the Switch B, the MP1 belongs to the MD1, and the MP2 belongs to the MD2. Because both the MP1 and the MP2 are located on the Switch B, the MP1 and the MP2 may be used as connective MPs. Therefore, the unified OAM management center adds an interaction attribute of "interacting with the MP2" to the MP1, and adds an interaction attribute of "interacting with the MP1" to the MP2.

[0052] The establishing interaction information for the MD1 and the MD2 may also include establishing interaction attributes for the MD1 and the MD2, for example, adding an interaction attribute of "interacting with the MD2" to the MD1, and adding an interaction attribute of "interacting with the MD1" to the MD2.
2. As shown in FIG. 2, when the link between the Switch B and the Switch C is faulty, merely as an example herein, the fault in this embodiment of the present invention further includes another type of fault such as a network device fault or a node fault, or the fault in this embodiment of the present invention includes link performance degradation, network device performance degradation, node performance degradation, or the like. Assuming that the MP4 using the BFD technology on the Switch C first detects the link fault, the MP4 sends a fault alarm message to the unified OAM management center.

[0053] Specifically, the unified OAM management center receives XML-form data transferred by the MP4 by using the Network Configuration Protocol (Network Configuration Protocol, NETCONF). The XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information. That the unified OAM management data model is transformed to the XML-form data by using the IETF YANG Data Model format may be implemented by using an existing standard rule. The fault alarm message includes the fault information. The fault information includes a fault location, a fault status, and fault content. The fault location includes location information of a faulty network device or link, and the like. Optionally, the fault alarm message further includes location information of a fault discovery device and/or location information of a fault reporting device. 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 a node identifier of the fault reporting device, a first maintenance set to which the fault discovery device and/or the fault reporting device belongs, and the like, for example, a node identifier of the MP4, and an MD to which the MP4 belongs. The unified OAM management center may obtain, according to these pieces of information, information about an MP sending the fault alarm message, for example, information about the first maintenance set to which the fault discovery device and/or the fault reporting device belongs; query an OAM database, to obtain a second maintenance set interacting with the first maintenance set; and send a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set. Moreover, the unified OAM management center may not send a fault notification message to the fault discovery device and/or the fault reporting device according to these pieces of information. The unified OAM management data model may be:
+---n defect-condition-notification  
+--ro md-index uint32
+--ro meg-index uint32
+--ro me-index uint32
+--ro mp-index uint32
+--ro meg-oper-status uint32
+--ro meg-sub-oper-status uint32


[0054] The object of the unified OAM management data model is obtained by filling and/or extending a related parameter of the unified OAM management data model according to a specific example. The specific example may be or may be not related to a specific OAM technology. For example, in this embodiment of the present invention, the related parameter of the unified OAM management data model is filled and/or extended according to the fault information unrelated to a specific OAM technology, to obtain the object of the unified OAM management data model.
3. After receiving the fault alarm message, the unified OAM management center queries the OAM database, to obtain the MD1 interacting with the MD2.

[0055] Specifically, if the establishing interaction information for a maintenance set that needs to perform OAM interaction includes adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, another connective MP located in a same network device as the connective MP is found according to the interaction attribute of the connective MP, and an interacting MD is found according to an MD to which the connective MP belongs. For example, if the establishing interaction information for the MD1 and the MD2 includes: adding, to the connective MP, that is, the MP1, an interaction attribute of "interacting with the MP2", and adding, to the MP2, an interaction attribute of "interacting with the MP1", the MP1 is found according to an interaction attribute of the MP2, and the MD1 to which the MP1 belongs is found according to the MP1. If the establishing interaction information for a maintenance set that needs to perform OAM interaction also includes establishing an interaction attribute for the maintenance set that needs to perform OAM interaction, for example, adding an interaction attribute of "interacting with the MD2" to the MD1, and adding an interaction attribute of "interacting with the MD1" to the MD2, the MD1 interacting with the MD2 may be directly found according to the interaction attribute of the maintenance set.
4. The unified OAM management center sends a fault notification message to all MPs in the MD1 or an MP that is determined according to a policy, where the fault notification message includes the fault information.

[0056] The unified OAM management center sends the fault notification message to all the MPs in the MD1; or the unified OAM management center may send the fault notification message to the MP that is determined according to the policy in the MD1. A specific policy is not limited in this embodiment of the present invention, and belongs to the protection scope of this embodiment of the present invention. In this embodiment of the present invention, the unified OAM management center sends the fault notification message to all the MPs in the MD1, namely, the MP1 and the MP3. The unified OAM management center sends, to the MP1 and the MP3, XML-form data transferred by using the NETCONF. The XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information. That the unified OAM management data model is transformed to the XML-form data by using the IETF YANG Data Model format may be implemented by using an existing standard rule. The fault notification message includes the fault information. The fault information includes a fault location, a fault status, and fault content. The fault location includes location information of a faulty network device or link, and the like. Optionally, if the fault alarm message further includes location information of a fault discovery device and/or location information of a fault reporting device, the fault notification message further includes the location information of the fault discovery device and/or the location information of the fault reporting device. 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 a node identifier of the fault reporting device, and a first maintenance set to which the fault discovery device and/or the fault reporting device belongs, for example, a node identifier of the MP4, and an MD to which the MP4 belongs. The MP1 and the MP3 may perform fault interaction according to respective statuses, for example, starting a spare channel. The unified OAM management data model may be:
+---n defect-condition-spreading  
+--ro md-index uint32
+--ro meg-index uint32
+--ro me-index uint32
+--ro mp-index uint32
+--ro meg-oper-status uint32
+--ro meg-sub-oper-status uint32


[0057] The object of the unified OAM management data model is obtained by filling and/or extending a related parameter of the unified OAM management data model according to a specific example. The specific example may be or may be not related to a specific OAM technology. For example, in this embodiment of the present invention, the related parameter of the unified OAM management data model is filled and/or extended according to the fault information unrelated to a specific OAM technology, to obtain the object of the unified OAM management data model.

[0058] Optionally, the unified OAM management center may send the fault notification message to another MP located in a same MD as the MP4. For example, the unified OAM management center may send the fault notification message to the MP2.

[0059] As for another MP using the BFD technology in the MD2, for example, when the MP2 detects the link fault later, if the MP2 has received the fault notification message sent by the unified OAM management center, the MP2 does not need to send the fault alarm message to the unified OAM management center again. If the MP2 has not received the fault notification message sent by the unified OAM management center, the MP2 may then send the fault alarm message to the unified OAM management center.

[0060] Optionally, in this embodiment of the present invention, the fault alarm message or the fault notification message may be transferred by using an extended Simple Network Management Protocol (Simple Network Management Protocol, SNMP).

[0061] Optionally, in this embodiment of the present invention, the unified OAM management center may receive fault alarm messages sent by MPs in the first maintenance set by using a method in the prior art. The fault alarm messages include fault information. The method in the prior art is related to an OAM technology used by the MP. The unified OAM management center queries an OAM database, to obtain a second maintenance set interacting with the first maintenance set, where the second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets. The unified OAM management center transforms the fault information into an object of a unified OAM management data model. The unified OAM management center sends a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set. The fault notification message includes the fault information, the fault notification message is XML-form data transferred by using the NETCONF, the XML-form data is obtained by transforming the object of the unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information. That the unified OAM management data model is transformed to the XML-form data by using the IETF YANG Data Model format may be implemented by using an existing standard rule.

[0062] Optionally, in this embodiment of the present invention, the unified OAM management center may receive fault alarm messages sent by MPs in the first maintenance set by using a method in the prior art. The fault alarm messages include fault information. The method in the prior art is related to an OAM technology used by the MP. The unified OAM management center queries an OAM database, to obtain a second maintenance set interacting with the first maintenance set, where the second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets. The unified OAM management center sends a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, where the fault notification message includes the fault information. The fault notification message is sent by using the method in the prior art. The method in the prior art is related to an OAM technology used by the MP.

[0063] In this way, this embodiment of the present invention may compatibly support sending the fault alarm message or the fault notification message by using the method in the prior art, but does not support an MP of a method based on the unified OAM management data model.

[0064] Another network operation, administration, and maintenance OAM method provided in an embodiment of the present invention is described below with reference to an application scenario of FIG. 3.

[0065] FIG. 3 shows a multi-layer OAM (Multi-layer OAM) scenario. The bottom layer is a label switched path LSP layer, and then a pseudo wire PW layer and a multi-segment pseudo wire MS-PW layer follow. Certainly, this is merely an example herein. The cross layer may include another layer. Each layer uses an OAM technology corresponding to a network technology of this layer. When a link between a provider termination edge router 1 and a provider switching edge router 1 is faulty, merely as an example herein, a fault in this embodiment of the present invention further includes another type of fault such as a network device fault or a node fault, or a fault in this embodiment of the present invention includes link performance degradation, network device performance degradation, node performance degradation, or the like. MPs of maintenance sets located on different layers may each detect the link fault, and may each send a fault alarm message. This may cause an alarm storm. According to a network operation, administration, and maintenance OAM method in this embodiment of the present invention, a related fault alarm may be centrally notified and suppressed on a management plane, and is decoupled from a specific OAM technology, thereby greatly reducing an implementation difficulty. Therefore, it is easier to avoid this case.

[0066] Specifically, each router on each layer is provided with an MP. The unified OAM management center may collect information about MPs in a network managed by the unified OAM management center. The information about the MPs includes network topology information and information about a used OAM technology that are of the MPs. The unified OAM management center establishes a maintenance set according to the information about the MPs, where the maintenance set may be an MD, for example, each layer may be allocated to one MD; or the maintenance set may be an MEG, for example, all MPs on layers are allocated to one MD. The layers are distinguished from each other by using different MEGs, that is, each layer is allocated to one MEG. In an MEG, different OAM technologies of different layers are distinguished from each other by using the attribute of MEG-LEVEL.

[0067] The unified OAM management center establishes interaction information for a maintenance set that needs to perform OAM interaction, where the establishing interaction information for a maintenance set that needs to perform OAM interaction includes adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, where when there are multiple MPs that belong to different maintenance sets on one network device, the multiple MPs are connective MPs. When there is one MP that belongs to one maintenance set on a network device and there are multiple maintenance sets on a network device, multiple MPs that belong to maintenance sets are connective MPs.

[0068] The establishing interaction information for a maintenance set that needs to perform OAM interaction may also include establishing an interaction attribute for the maintenance set that needs to perform OAM interaction.

[0069] Networks corresponding to the maintenance sets that need to perform OAM interaction include at least one same network device or cover a same path.

[0070] As shown in FIG. 3, network topologies corresponding to maintenance sets on layers cover a same path. When the link fault shown in FIG. 3 occurs, MPs of the maintenance sets on the layers may detect the link fault and send a fault alarm message, thereby causing an alarm storm. Therefore, an MP, which first detects and sends the fault alarm message, of a maintenance set on a layer needs to notify an MP of a maintenance set on another layer, so that the MP of the maintenance set on the another layer performs alarm suppression, and does not send the fault alarm message again. It is determined that maintenance sets on the layers need to perform OAM interaction. In this embodiment of the present invention, it may be determined according to a policy that OAM interaction is performed only between maintenance sets on some layers.

[0071] The establishing interaction information for a maintenance set that needs to perform OAM interaction includes adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set. For example, in FIG. 3, different maintenance sets are cross layers. Each layer physically cover a same path. A unified OAM management center uses multiple MPs that are on network devices and that belong to different maintenance sets as connective MPs, and adds, to the connective MPs, an interaction attribute of a connective MP interacting with another maintenance set. For example, there are three MPs on a provider termination edge router 1, namely, MP-LSP-T-PE1 that belongs to a maintenance set on an LSP layer, MP-PW-T-PE1 that belongs to a maintenance set on a PW layer, and MP-MS-PW-T-PE1 that belongs to a maintenance set on a multi-segment PW layer. The unified OAM management center uses these MPs as connective MPs, and adds interaction attributes to these connective MPs, that is, adds interaction attributes of "interacting with the MP-PW-T-PE1" and "interacting with MP-MS-PW-T-PE1" to the MP-LSP-T-PE1, adds interaction attributes of "interacting with the MP-LSP-T-PE1" and "interacting with MP-MS-PW-T-PE1" to the MP-PW-T-PE1, and adds interaction attributes of "interacting with the MP-LSP-T-PE1" and "interacting with the MP-PW-T-PE1" to the MP-MS-PW-T-PE1.

[0072] The establishing interaction information for a maintenance set that needs to perform OAM interaction may also include establishing an interaction attribute for the maintenance set that needs to perform OAM interaction, for example, adding interaction attributes of "interacting with a maintenance set on the PW layer" and "interacting with a maintenance set on the MS-PW layer" to a maintenance set on the LSP layer, adding interaction attributes of "interacting with the maintenance set on the LSP layer" and "interacting with the maintenance set on the MS-PW layer" to the maintenance set on the PW layer, and adding interaction attributes of "interacting with the maintenance set on the LSP layer" and "interacting with the maintenance set on the PW layer" to the maintenance set on the MS-PW layer.

[0073] As shown in FIG. 3, when a link between the provider termination edge router 1 and a provider switching edge router 1 is faulty, assuming that an MP of the maintenance set on the LSP layer, that is, the MP-LSP-T-PE1, first detects the link fault, the MP-LSP-T-PE1 sends a fault alarm message to the unified OAM management center.

[0074] Specifically, the unified OAM management center receives XML-form data transferred by the MP-LSP-T-PE1 by using the NETCONF. The XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information. That the unified OAM management data model is transformed to the XML-form data by using the IETF YANG Data Model format may be implemented by using an existing standard rule. The fault alarm message includes the fault information. The fault information includes a fault location, a fault status, and fault content. The fault location includes location information of a faulty network device or link, and the like. Optionally, the fault alarm message further includes location information of a fault discovery device and/or location information of a fault reporting device. 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 a node identifier of the fault reporting device, a first maintenance set to which the fault discovery device and/or the fault reporting device belongs, and the like, for example, a node identifier of the MP-LSP-T-PE1, an MD to which the MP-LSP-T-PE1 belongs, and an MEG to which the MP-LSP-T-PE1 belongs. The unified OAM management center may obtain, according to these pieces of information, information about an MP sending the fault alarm message, for example, information about the first maintenance set to which the fault discovery device and/or the fault reporting device belongs; query an OAM database, to obtain a second maintenance set interacting with the first maintenance set; and send a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set. Moreover, the unified OAM management center may not send a fault notification message to the fault discovery device and/or the fault reporting device according to these pieces of information. The unified OAM management data model may be:
+---n defect-condition-notification  
+--ro md-index uint32
+--ro meg-index uint32
+--ro me-index uint32
+--ro mp-index uint32
+--ro meg-oper-status uint32
+--ro meg-sub-oper-status uint32


[0075] The object of the unified OAM management data model is obtained by filling and/or extending a related parameter of the unified OAM management data model according to a specific example. The specific example may be or may be not related to a specific OAM technology. For example, in this embodiment of the present invention, the related parameter of the unified OAM management data model is filled and/or extended according to the fault information unrelated to a specific OAM technology, to obtain the object of the unified OAM management data model.

[0076] After receiving the fault alarm message, the unified OAM management center queries the OAM database, to obtain a maintenance set interacting with the maintenance set on the LSP layer, that is, the maintenance set on the PW layer and the maintenance set on the MS-PW layer.

[0077] Specifically, if the establishing interaction information for a maintenance set that needs to perform OAM interaction includes adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, another connective MP located in a same network device as the connective MP is found according to the interaction attribute of the connective MP, and an interacting maintenance set is found according to a maintenance set to which the connective MP belongs. For example, other connective MPs located in a same network device as the MP-LSP-T-PE1 are found according to interaction attributes of "interacting with the MP-PW-T-PE1" and "interacting with the MP-MS-PW-T-PE1" of the MP-LSP-T-PE1 on the LSP layer, namely, the MP-PW-T-PE1 and the MP-MS-PW-T-PE1. Interacting maintenance sets are found according to maintenance sets to which the MP-PW-T-PE1 and the MP-MS-PW-T-PE1 belong, namely, the maintenance set on the PW layer and the maintenance set on the MS-PW layer.

[0078] If the establishing interaction information for a maintenance set that needs to perform OAM interaction also includes establishing an interaction attribute for the maintenance set that needs to perform OAM interaction, maintenance sets interacting with the maintenance set on the LSP layer may be directly found according to the interaction attribute of the maintenance set, namely, the maintenance set on the PW layer and the maintenance set on the MS-PW layer.

[0079] The unified OAM management center sends a fault notification message to the maintenance sets interacting with the maintenance set on the LSP layer, namely, all MPs in the maintenance set on the PW layer and the maintenance set on the MS-PW layer or an MP that is determined according to a policy. The fault notification message includes the fault information.

[0080] The unified OAM management center sends the fault notification message to all the MPs in the maintenance set on the PW layer and the maintenance set on the MS-PW layer; or the unified OAM management center may send the fault notification message to the MP that is determined according to the policy in the maintenance set on the PW layer and the maintenance set on the MS-PW layer. A specific policy is not limited in this embodiment of the present invention, and belongs to the protection scope of this embodiment of the present invention. In this embodiment of the present invention, the unified OAM management center sends the fault notification message to all the MPs in the maintenance set on the PW layer and the maintenance set on the MS-PW layer. The unified OAM management center sends, to an MP that needs to perform fault interaction, XML-form data transferred by using the NETCONF. The XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information. That the unified OAM management data model is transformed to the XML-form data by using the IETF YANG Data Model format may be implemented by using an existing standard rule. The fault notification message includes the fault information. The fault information includes a fault location, a fault status, and fault content. The fault location includes location information of a faulty network device or link, and the like. Optionally, if the fault alarm message further includes location information of a fault discovery device and/or location information of a fault reporting device, the fault notification message further includes the location information of the fault discovery device and/or the location information of the fault reporting device. 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 a node identifier of the fault reporting device, and a first maintenance set to which the fault discovery device and/or the fault reporting device belongs, for example, a node identifier of the MP-LSP-T-PE1, an MD to which the MP-LSP-T-PE1 belongs, and an MEG to which the MP-LSP-T-PE1 belongs. An MP that needs to perform fault interaction may perform fault interaction according to a status of the MP, for example, performs alarm suppression, and does not send the fault alarm message again when detecting the link fault. The unified OAM management data model may be:
+---n defect-condition-spreading  
+--ro md-index uint32
+--ro meg-index uint32
+--ro me-index uint32
+--ro mp-index uint32
+--ro meg-oper-status uint32
+--ro meg-sub-oper-status uint32


[0081] The object of the unified OAM management data model is obtained by filling and/or extending a related parameter of the unified OAM management data model according to a specific example. The specific example may be or may be not related to a specific OAM technology. For example, in this embodiment of the present invention, the related parameter of the unified OAM management data model is filled and/or extended according to the fault information unrelated to a specific OAM technology, to obtain the object of the unified OAM management data model.

[0082] Optionally, the unified OAM management center may send a fault notification message to another MP located in a same maintenance set as the MP-LSP-T-PE1. For example, the unified OAM management center may send the fault notification message to another MP on the LSP layer.

[0083] Optionally, in this embodiment of the present invention, the fault alarm message or the fault notification message may be transferred by using an extended SNMP.

[0084] Optionally, in this embodiment of the present invention, the unified OAM management center may receive fault alarm messages sent by MPs in the first maintenance set by using a method in the prior art. The fault alarm messages include fault information. The method in the prior art is related to an OAM technology used by the MP. The unified OAM management center queries an OAM database, to obtain a second maintenance set interacting with the first maintenance set. The second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets. The unified OAM management center transforms the fault information into an object of a unified OAM management data model. The unified OAM management center sends a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set. The fault notification message includes the fault information, the fault notification message is XML-form data transferred by using the NETCONF, the XML-form data is obtained by transforming the object of the unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information. That the unified OAM management data model is transformed to the XML-form data by using the IETF YANG Data Model format may be implemented by using an existing standard rule.

[0085] Optionally, in this embodiment of the present invention, the unified OAM management center may receive fault alarm messages sent by MPs in the first maintenance set by using a method in the prior art. The fault alarm messages include fault information. The method in the prior art is related to an OAM technology used by the MP. The unified OAM management center queries an OAM database, to obtain a second maintenance set interacting with the first maintenance set. The second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets. The unified OAM management center sends a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set. The fault notification message includes the fault information. The fault notification message is sent by using the method in the prior art. The method in the prior art is related to an OAM technology used by the MP.

[0086] In this way, this embodiment of the present invention may compatibly support sending the fault alarm message or the fault notification message by using the method in the prior art, but does not support an MP of a method based on the unified OAM management data model.

[0087] As shown in FIG. 4, an embodiment of the present invention further provides a unified operation, administration, and maintenance (OAM) management center, including:

a receiving unit 401, configured to receive a fault alarm message sent by a maintenance point MP, where the fault alarm message includes fault information;

a determining unit 402, configured to determine, according to the fault alarm message, a first maintenance set to which the MP belongs, where the first maintenance set includes MPs using a first OAM technology;

a processing unit 403, configured to query an OAM database, to obtain a second maintenance set interacting with the first maintenance set, where the second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets; and

a sending unit 404, configured to send a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, where the fault notification message includes the fault information.



[0088] Optionally, the maintenance set includes a maintenance domain MD or a maintenance entity group MEG.

[0089] Optionally, the determining unit 402 is specifically configured to: determine the first maintenance set according to content of the fault alarm message; or
determine the first maintenance set according to a source address of the fault alarm message.

[0090] Optionally, the fault alarm message further includes location information of a fault discovery device and/or location information of a fault reporting device, and the determining unit is specifically configured to determine the first maintenance set according to at least one of the fault information, the location information of the fault discovery device, or the location information of the fault reporting device.

[0091] Optionally, the unified OAM management center further includes an establishment unit, where the establishment unit specifically includes:

a collection subunit, configured to collect information about MPs in a network managed by the unified OAM management center, where the information about the MPs includes network topology information and information about a used OAM technology that are of the MPs;

a first establishment subunit, configured to establish the maintenance sets according to the information about the MPs; and

a second establishment subunit, configured to establish interaction information for a maintenance set that needs to perform OAM interaction, where the establishing interaction information for a maintenance set that needs to perform OAM interaction includes adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, where when there are multiple MPs that belong to different maintenance sets on one network device, the multiple MPs are connective MPs.



[0092] Optionally, networks corresponding to the maintenance sets that need to perform OAM interaction include at least one same network device or cover a same path.

[0093] Optionally, the receiving unit 401 is specifically configured to receive XML-form data transferred by the MP by using the Network Configuration Protocol NETCONF. The XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information. Optionally, the sending unit 403 is specifically configured to send, to all the MPs in the second maintenance set or the MP that is determined according to the policy, the XML-form data transferred by using the NETCONF. The XML-form data is obtained by transforming the object of the unified OAM management data model, the unified OAM management data model is generated by using the IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.

[0094] As shown in FIG. 5, an embodiment of the present invention further provides a network system, including:

a maintenance point MP 501, configured to send a fault alarm message to the operation, administration, and maintenance unified OAM management center 502 described above, where the fault alarm message includes fault information;

the unified OAM management center 502 described above, configured to determine, according to the fault alarm message, a first maintenance set to which the MP belongs, where the first maintenance set includes MPs using a first OAM technology; configured to query an OAM database, to obtain a second maintenance set interacting with the first maintenance set, where the second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets; and configured to send a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, where the fault notification message includes the fault information; and

all the MPs 503 in the second maintenance set or the MP 503 determined according to the policy, configured to perform fault interaction according to the fault notification message.



[0095] As shown in FIG. 6, an embodiment of the present invention further provides a unified operation, administration, and maintenance OAM management center, including:
a transceiver 601, a processor 602, a memory 603, and a bus 604, where the transceiver 601, the processor 602, and the memory 603 are connected and implement communication with each other by using the bus 604.

[0096] The bus 604 may be an industry standard architecture (Industry Standard Architecture, ISA) bus, a peripheral component interconnect (Peripheral Component, PCI) bus, an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The bus 604 may be classified into an address bus, a data bus, a control bus, and the like. For convenience of representation, only one line is used for representation in the figure, but it does not indicate that there is only one bus or one type of bus.

[0097] The memory 603 is configured to store program code, and the program code includes an operation instruction. The memory 603 may include a high-speed random access memory (random access memory, RAM), or may include a non-volatile memory (non-volatile memory), for example, a magnetic disk storage.

[0098] The processor 602 may be a central processing unit (Central Processing Unit, CPU) or an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be one or more integrated circuits configured to implement the embodiments of the present invention.

[0099] The transceiver 601 may be an interface.

[0100] The transceiver 601 is configured to receive a fault alarm message sent by a maintenance point MP, where the fault alarm message includes fault information.

[0101] The processor 602 is configured to invoke the program code in the memory 603, to perform the following operations:
determining, according to the fault alarm message, a first maintenance set to which the MP belongs, where the first maintenance set includes MPs using a first OAM technology; and querying an OAM database, to obtain a second maintenance set interacting with the first maintenance set, where the second maintenance set includes MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets.

[0102] The transceiver 601 is further configured to send a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, where the fault notification message includes the fault information.

[0103] Because function implementation of the apparatus according to this embodiment of the present invention and that of the method both belong to a same inventive concept, reference may be made to the method, and details are not described herein again.

[0104] A person of ordinary skill in the art may be aware that, in combination with the examples described in the embodiments disclosed in this specification, modules and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraint conditions of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present invention.

[0105] It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and module, reference may be made to a corresponding process in the foregoing method embodiments, and details are not described herein again.

[0106] In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the described apparatus embodiment is merely an example. For example, the module division is merely logical function division and may be other division in actual implementation. For example, a plurality of modules or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the apparatuses or modules may be implemented in electronic, mechanical, or other forms.

[0107] The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one position, or may be distributed on a plurality of network modules. Some or all the modules may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

[0108] In addition, functional modules in the embodiments of the present invention may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module.

[0109] When the functions are implemented in the form of a software functional module and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of the present invention essentially, or the part contributing to the prior art, or some of the technical solutions may be implemented in a form of a software product. The software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or some of the steps of the methods described in the embodiments of the present invention. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc.

[0110] The foregoing descriptions are merely specific implementation manners of the present invention, but are not intended to limit the protection scope of the present invention. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in the present invention shall fall within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.


Claims

1. A network operation, administration, and maintenance, OAM, method, comprising:

receiving (101), by a unified OAM management center, a fault alarm message sent by a maintenance point, MP, wherein the fault alarm message comprises fault information;

determining (102), by the unified OAM management center according to the fault alarm message, a first maintenance set to which the MP belongs, wherein the first maintenance set comprises MPs using a first OAM technology;

querying (103), by the unified OAM management center, an OAM database, to obtain a second maintenance set interacting with the first maintenance set, wherein the second maintenance set comprises MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets; and

sending (104), by the unified OAM management center, a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, wherein the fault notification message comprises the fault information;

wherein the first OAM technology and the second OAM technology are selected from a Connectivity Fault Management, CFM, technology and a Bidirectional Forwarding Detection, BFD, technology.


 
2. The method according to claim 1, wherein
the maintenance set comprises a maintenance domain, MD, or a maintenance entity group, MEG.
 
3. The method according to claim 1 or 2, wherein the determining, by the unified OAM management center according to the fault alarm message, a first maintenance set specifically comprises:

determining, by the unified OAM management center, the first maintenance set according to content of the fault alarm message; or

determining, by the unified OAM management center, the first maintenance set according to a source address of the fault alarm message.


 
4. The method according to claim 3, wherein
the fault alarm message further comprises location information of a fault discovery device and/or location information of a fault reporting device, and the determining, by the unified OAM management center, the first maintenance set according to content of the fault alarm message specifically comprises:
determining, by the unified OAM management center, the first maintenance set according to at least one of the fault information, the location information of the fault discovery device, or the location information of the fault reporting device.
 
5. The method according to any one of claims 1 to 4, before the querying, by the unified OAM management center, an OAM database, to obtain a second maintenance set interacting with the first maintenance set, further comprising a step of establishing the OAM database, wherein
the establishing, by the unified OAM management center, the OAM database comprises:

collecting, by the unified OAM management center, information about MPs in a network managed by the unified OAM management center, wherein the information about the MPs comprises network topology information and information about a used OAM technology that are of the MPs;

establishing, by the unified OAM management center, the maintenance sets according to the information about the MPs; and

establishing, by the unified OAM management center, interaction information for a maintenance set that needs to perform OAM interaction, wherein the establishing interaction information for a maintenance set that needs to perform OAM interaction comprises adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, wherein when there are multiple MPs that belong to different maintenance sets on one network device, the multiple MPs are connective MPs.


 
6. The method according to claim 5, wherein
networks corresponding to the maintenance sets that need to perform OAM interaction comprise at least one same network device or covers a same path.
 
7. The method according to any one of claims 1 to 6, wherein the receiving, by a unified OAM management center, a fault alarm message sent by a maintenance point, MP, specifically comprises:
receiving, by the unified OAM management center, XML-form data transferred by the MP by using the Network Configuration Protocol NETCONF, wherein the XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.
 
8. The method according to any one of claims 1 to 7, wherein the sending, by the unified OAM management center, a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set specifically comprises:
sending, by the unified OAM management center to all the MPs in the second maintenance set or the MP that is determined according to the policy, the XML-form data transferred by using the NETCONF, wherein the XML-form data is obtained by transforming the object of the unified OAM management data model, the unified OAM management data model is generated by using the IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.
 
9. A unified operation, administration, and maintenance, OAM, management center, comprising:

a receiving unit (401), configured to receive a fault alarm message sent by a maintenance point, MP, wherein the fault alarm message comprises fault information;

a determining unit (402), configured to determine, according to the fault alarm message, a first maintenance set to which the MP belongs, wherein the first maintenance set comprises MPs using a first OAM technology;

a processing unit (403), configured to query an OAM database, to obtain a second maintenance set interacting with the first maintenance set, wherein the second maintenance set comprises MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets; and

a sending unit (404), configured to send a fault notification message to all MPs in the second maintenance set or an MP that is determined according to a policy in the second maintenance set, wherein the fault notification message comprises the fault information;

wherein the first OAM technology and the second OAM technology are selected from a Connectivity Fault Management, CFM, technology and a Bidirectional Forwarding Detection, BFD, technology.


 
10. The unified OAM management center according to claim 9, wherein
the determining unit is specifically configured to: determine the first maintenance set according to content of the fault alarm message; or
determine the first maintenance set according to a source address of the fault alarm message.
 
11. The unified OAM management center according to claim 10, wherein
the fault alarm message further comprises location information of a fault discovery device and/or location information of a fault reporting device, and the determining unit is specifically configured to determine the first maintenance set according to at least one of the fault information, the location information of the fault discovery device, or the location information of the fault reporting device.
 
12. The unified OAM management center according to any one of claims 9 to 11, wherein the unified OAM management center further comprises an establishment unit, wherein the establishment unit specifically comprises:

a collection subunit, configured to collect information about MPs in a network managed by the unified OAM management center, wherein the information about the MPs comprises network topology information and information about a used OAM technology that are of the MPs;

a first establishment subunit, configured to establish the maintenance sets according to the information about the MPs; and

a second establishment subunit, configured to establish interaction information for a maintenance set that needs to perform OAM interaction, wherein the establishing interaction information for a maintenance set that needs to perform OAM interaction comprises: adding, to connective MPs, an interaction attribute of a connective MP interacting with another maintenance set, wherein when there are multiple MPs that belong to different maintenance sets on one network device, the multiple MPs are connective MPs.


 
13. The unified OAM management center according to any one of claims 9 to 12, wherein
the receiving unit is specifically configured to receive XML-form data transferred by the MP by using the Network Configuration Protocol NETCONF, wherein the XML-form data is obtained by transforming an object of a unified OAM management data model, the unified OAM management data model is generated by using an IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.
 
14. The unified OAM management center according to any one of claims 9 to 13, wherein
the sending unit is specifically configured to send, to all the MPs in the second maintenance set or the MP that is determined according to the policy, the XML-form data transferred by using the NETCONF, wherein the XML-form data is obtained by transforming the object of the unified OAM management data model, the unified OAM management data model is generated by using the IETF YANG Data Model format, and the object of the unified OAM management data model carries the fault information.
 
15. A network system, comprising:

a maintenance point, MP (501), configured to send a fault alarm message to the unified operation, administration, and maintenance, OAM, management center (502) according to any one of claims 9 to 14, wherein the fault alarm message comprises fault information;

the unified OAM management center (502) according to any one of claims 9 to 14, configured to determine, according to the fault alarm message, a first maintenance set to which the MP (501) belongs, wherein the first maintenance set comprises MPs using a first OAM technology; configured to query an OAM database, to obtain a second maintenance set interacting with the first maintenance set, wherein the second maintenance set comprises MPs using a second OAM technology, and the OAM database saves interaction information of different maintenance sets; and configured to send a fault notification message to all MPs (503) in the second maintenance set or an MP (503) that is determined according to a policy in the second maintenance set, wherein the fault notification message comprises the fault information; and

all the MPs (503) in the second maintenance set or the MP (503) that is determined according to the policy, configured to perform fault interaction according to the fault notification message;

wherein the first OAM technology and the second OAM technology are selected from a Connectivity Fault Management, CFM, technology and a Bidirectional Forwarding Detection, BFD, technology.


 


Ansprüche

1. Netzbetriebs-, -administrations- und -wartungs-Verfahren bzw. OAM-Verfahren, Folgendes umfassend:

Empfangen (101) einer Fehleralarmnachricht durch ein vereinigtes OAM-Verwaltungszentrum, die von einem Wartungspunkt, MP, gesendet wird, wobei die Fehleralarmnachricht Fehlerinformationen umfasst,

Bestimmen (102) einer ersten Wartungsreihe, zu der der MP gehört, durch das vereinigte OAM-Verwaltungszentrum gemäß der Fehleralarmnachricht, wobei die erste Wartungsreihe MPs umfasst, die eine erste OAM-Technologie verwenden,

Abfragen (103) einer OAM-Datenbank durch das vereinigte OAM-Verwaltungszentrum, um eine zweite Wartungsreihe zu beziehen, die mit der ersten Wartungsreihe interagiert, wobei die zweite Wartungsreihe MPs umfasst, die eine zweite OAM-Technologie verwenden, und die OAM-Datenbank Interaktionsinformationen von verschiedenen Wartungsreihen speichert, und

Senden (104) einer Fehlermitteilungsnachricht an alle MPs in der zweiten Wartungsreihe oder an einen MP, der gemäß einer Strategie in der zweiten Wartungsreihe bestimmt wird, durch das vereinigte OAM-Verwaltungszentrum, wobei die Fehlermitteilungsnachricht die Fehlerinformationen umfasst,

wobei die erste OAM-Technologie und die zweite OAM-Technologie aus einer "Connectivity-Fault-Management"-Technologie bzw. CFM-Technologie und einer "Bidirectional-Forwarding-Detection"-Technologie bzw. BFD-Technologie ausgewählt werden.


 
2. Verfahren nach Anspruch 1, wobei
die Wartungsreihe eine Wartungsdomäne, MD, oder eine Wartungsentitätengruppe, MEG, umfasst.
 
3. Verfahren nach Anspruch 1 oder 2, wobei das Bestimmen einer ersten Wartungsreihe durch das vereinigte OAM-Verwaltungszentrum gemäß der Fehleralarmnachricht spezifisch Folgendes umfasst:

Bestimmen der ersten Wartungsreihe durch das vereinigte OAM-Verwaltungszentrum gemäß einem Inhalt der Fehleralarmnachricht oder

Bestimmen der ersten Wartungsreihe durch das vereinigte OAM-Verwaltungszentrum gemäß einer Quelladresse der Fehleralarmnachricht.


 
4. Verfahren nach Anspruch 3, wobei
die Fehleralarmnachricht ferner Standortinformationen eines Fehlerentdeckungsgeräts und/oder Standortinformationen eines Fehlermeldegeräts umfasst und wobei das Bestimmen der ersten Wartungsreihe durch das vereinigte OAM-Verwaltungszentrum gemäß dem Inhalt der Fehleralarmnachricht spezifisch Folgendes umfasst:
Bestimmen der ersten Wartungsreihe durch das vereinigte OAM-Verwaltungszentrum gemäß den Fehlerinformationen und/oder den Standortinformationen des Fehlerentdeckungsgeräts und/oder den Standortinformationen des Fehlermeldegeräts.
 
5. Verfahren nach einem der Ansprüche 1 bis 4, ferner vor dem Abfragen einer OAM-Datenbank durch das vereinigte OAM-Verwaltungszentrum, um eine zweite Wartungsreihe zu beziehen, die mit der ersten Wartungsreihe interagiert, einen Schritt des Erstellens der OAM-Datenbank umfassend, wobei
das Erstellen der OAM-Datenbank durch das vereinigte OAM-Verwaltungszentrum Folgendes umfasst:

Sammeln von Informationen über MPs in einem Netz, das von dem vereinigten OAM-Verwaltungszentrum verwaltet wird, durch das vereinigte OAM-Verwaltungszentrum, wobei die Informationen über die MPs Netztopologieinformationen und Informationen über eine von den MPs verwendete OAM-Technologie umfassen,

Erstellen der Wartungsreihen gemäß den Informationen über die MPs durch das vereinigte OAM-Verwaltungszentrum und

Erstellen von Interaktionsinformationen für eine Wartungsreihe, die eine OAM-Interaktion ausführen muss, durch das vereinigte OAM-Verwaltungszentrum, wobei das Erstellen der Interaktionsinformationen für eine Wartungsreihe, die eine OAM-Interaktion ausführen muss, das Hinzufügen eines Interaktionsattributs eines verbindungsfähigen MP, der mit einer anderen Wartungsreihe interagiert, zu verbindungsfähigen MPs umfasst, wobei, wenn mehrere MPs vorhanden sind, die zu unterschiedlichen Wartungsreihen auf einem Netzgerät gehören, die mehreren MPs verbindungsfähige MPs sind.


 
6. Verfahren nach Anspruch 5, wobei
Netze, die den Wartungsreihen entsprechen, die eine OAM-Interaktion ausführen müssen, mindestens ein gleiches Netzgerät umfassen oder einen gleichen Pfad abdecken.
 
7. Verfahren nach einem der Ansprüche 1 bis 6, wobei das Empfangen einer Fehleralarmnachricht, die von einem Wartungspunkt, MP, gesendet wird, durch ein vereinigtes OAM-Verwaltungszentrum spezifisch Folgendes umfasst:
Empfangen von XML-Formulardaten, die von dem MP mit Hilfe des Netzkonfigurationsprotokolls NETCONF, übertragen werden, durch das vereinigte OAM-Verwaltungszentrum, wobei die XML-Formulardaten durch Umwandeln eines Objekts eines vereinigten OAM-Verwaltungsdatenmodells bezogen werden, wobei das vereinigte OAM-Verwaltungsdatenmodell mit Hilfe eines IETF-YANG-Datenmodellformats erzeugt wird und das Objekt des vereinigten OAM-Verwaltungsdatenmodells die Fehlerinformationen mitführt.
 
8. Verfahren nach einem der Ansprüche 1 bis 7, wobei das Senden einer Fehlermittelungsnachricht an alle MPs in der zweiten Wartungsreihe oder an einen MP, der gemäß einer Strategie in der zweiten Wartungsreihe bestimmt wird, durch das vereinigte OAM-Verwaltungszentrum spezifisch Folgendes umfasst:
Senden der XML-Formulardaten, die mit Hilfe des NETCONF übertragen werden, an alle MPs in der zweiten Wartungsreihe oder an den MP, der gemäß der Strategie bestimmt wird, durch das vereinigte OAM-Verwaltungszentrum, wobei die XML-Formulardaten durch Umwandeln des Objekts des vereinigten OAM-Verwaltungsdatenmodells bezogen werden, wobei das vereinigte OAM-Verwaltungsdatenmodell mit Hilfe des IETF-YANG-Datenmodellformats erzeugt wird und das Objekt des vereinigten OAM-Verwaltungsdatenmodells die Fehlerinformationen mitführt.
 
9. Vereinigtes Netzbetriebs-, -administrations- und -wartungs-Verwaltungszentrum bzw. OAM-Verwaltungszentrum, Folgendes umfassend:

eine Empfangseinheit (401), die dafür konfiguriert ist, eine Fehleralarmnachricht zu empfangen, die von einem Wartungspunkt, MP, gesendet wird, wobei die Fehleralarmnachricht Fehlerinformationen umfasst,

eine Bestimmungseinheit (402), die dafür konfiguriert ist, gemäß der Fehleralarmnachricht eine erste Wartungsreihe zu bestimmen, zu der der MP gehört, wobei die erste Wartungsreihe MPs umfasst, die eine erste OAM-Technologie verwenden,

eine Verarbeitungseinheit (403), die dafür konfiguriert ist, eine OAM-Datenbank abzufragen, um eine zweite Wartungsreihe zu beziehen, die mit der ersten Wartungsreihe interagiert, wobei die zweite Wartungsreihe MPs umfasst, die eine zweite OAM-Technologie verwenden, und die OAM-Datenbank Interaktionsinformationen von verschiedenen Wartungsreihen speichert, und

eine Sendeeinheit (404), die dafür konfiguriert ist, eine Fehlermitteilungsnachricht an alle MPs in der zweiten Wartungsreihe oder an einen MP, der gemäß einer Strategie in der zweiten Wartungsreihe bestimmt wird, zu senden, wobei die Fehlermitteilungsnachricht die Fehlerinformationen umfasst,

wobei die erste OAM-Technologie und die zweite OAM-Technologie aus einer "Connectivity-Fault-Management"-Technologie bzw. CFM-Technologie und einer "Bidirectional-Forwarding-Detection"-Technologie bzw. BFD-Technologie ausgewählt sind.


 
10. Vereinigtes OAM-Verwaltungszentrum nach Anspruch 9, wobei die Bestimmungseinheit spezifisch für Folgendes konfiguriert ist: Bestimmen der ersten Wartungsreihe gemäß dem Inhalt der Fehleralarmnachricht oder
Bestimmen der ersten Wartungsreihe gemäß einer Quelladresse der Fehleralarmnachricht.
 
11. Vereinigtes OAM-Verwaltungszentrum nach Anspruch 10, wobei die Fehleralarmnachricht ferner Standortinformationen eines Fehlerentdeckungsgeräts und/oder Standortinformationen eines Fehlermeldegeräts umfasst und die Bestimmungseinheit spezifisch dafür konfiguriert ist, die erste Wartungsreihe gemäß den Fehlerinformationen und/oder den Standortinformationen des Fehlerentdeckungsgeräts und/oder den Standortinformationen des Fehlermeldegeräts zu bestimmen.
 
12. Vereinigtes OAM-Verwaltungszentrum nach einem der Ansprüche 9 bis 11, wobei das vereinigte OAM-Verwaltungszentrum ferner eine Erstellungseinheit umfasst, wobei die Erstellungseinheit spezifisch Folgendes umfasst:

eine Sammelteileinheit, die dafür konfiguriert ist, Informationen über MPs in einem Netz zu sammeln, das von dem vereinigten OAM-Verwaltungszentrum verwaltet wird, wobei die Informationen über die MPs Netztopologieinformationen und Informationen über eine von den MPs verwendete OAM-Technologie umfassen,

eine erste Erstellungsteileinheit, die dafür konfiguriert ist, die Wartungsreihen gemäß den Informationen über die MPs zu erstellen, und

eine zweite Erstellungsteileinheit, die dafür konfiguriert ist, Interaktionsinformationen für eine Wartungsreihe zu erstellen, die eine OAM-Interaktion ausführen muss, wobei das Erstellen von Interaktionsinformationen für eine Wartungsreihe, die eine OAM-Interaktion ausführen muss, Folgendes umfasst: Hinzufügen eines Interaktionsattributs eines verbindungsfähigen MP, der mit einer anderen Wartungsreihe interagiert, zu verbindungsfähigen MPs, wobei, wenn mehrere MPs vorhanden sind, die zu unterschiedlichen Wartungsreihen auf einem Netzgerät gehören, die mehreren MPs verbindungsfähige MPs sind.


 
13. Vereinigtes OAM-Verwaltungszentrum nach einem der Ansprüche 9 bis 12, wobei die Empfangseinheit spezifisch dafür konfiguriert ist, XML-Formulardaten zu empfangen, die von dem MP mit Hilfe des Netzkonfigurationsprotokolls NETCONF, übertragen werden, wobei die XML Formulardaten durch Umwandeln eines Objekts eines vereinigten OAM-Verwaltungsdatenmodells bezogen werden, wobei das vereinigte OAM-Verwaltungsdatenmodell mit Hilfe eines IETF-YANG-Datenmodellformats erzeugt wird und das Objekt des vereinigten OAM-Verwaltungsdatenmodells die Fehlerinformationen mitführt.
 
14. Vereinigtes OAM-Verwaltungszentrum nach einem der Ansprüche 9 bis 13, wobei die Sendeeinheit spezifisch dafür konfiguriert ist, die XML-Formulardaten, die mit Hilfe des NETCONF übertragen werden, an alle MPs in der zweiten Wartungsreihe oder an den MP, der gemäß der Strategie bestimmt wird, zu senden, wobei die XML-Formulardaten durch Umwandeln des Objekts des vereinigten OAM-Verwaltungsdatenmodells bezogen werden, wobei das vereinigte OAM-Verwaltungsdatenmodell mit Hilfe des IETF-YANG-Datenmodellformats erzeugt wird und das Objekt des vereinigten OAM-Verwaltungsdatenmodells die Fehlerinformationen mitführt.
 
15. Netzsystem, Folgendes umfassend:

einen Wartungspunkt, MP (501), der dafür konfiguriert ist, eine Fehleralarmnachricht an das vereinigte Netzbetriebs-, -administrations- und -wartungs-Verwaltungszentrum bzw. OAM-Verwaltungszentrum (502) nach einem der Ansprüche 9 bis 14 zu senden, wobei die Fehleralarmnachricht Fehlerinformationen umfasst,

das vereinigte OAM-Verwaltungszentrum (502) nach einem der Ansprüche 9 bis 14, das dafür konfiguriert ist, gemäß der Fehleralarmnachricht eine erste Wartungsreihe zu bestimmen, zu der der MP (501) gehört, wobei die erste Wartungsreihe MPs umfasst, die eine erste OAM-Technologie verwenden, dafür konfiguriert ist, eine OAM-Datenbank abzufragen, um eine zweite Wartungsreihe zu beziehen, die mit der ersten Wartungsreihe interagiert, wobei die zweite Wartungsreihe MPs umfasst, die eine zweite OAM-Technologie verwenden, und die OAM-Datenbank Interaktionsinformationen von verschiedenen Wartungsreihen speichert, und dafür konfiguriert ist, eine Fehlermitteilungsnachricht an alle MPs (503) in der zweiten Wartungsreihe oder an einen MP (503), der gemäß einer Strategie in der zweiten Wartungsreihe bestimmt wird, zu senden, wobei die Fehlermitteilungsnachricht die Fehlerinformationen umfasst, und

alle MPs (503) in der zweiten Wartungsreihe oder der MP (503), der gemäß der Strategie bestimmt wird, dafür konfiguriert sind/ist, gemäß der Fehlermitteilungsnachricht eine Fehlerinteraktion durchzuführen,

wobei die erste OAM-Technologie und die zweite OAM-Technologie aus einer "Connectivity-Fault-Management"-Technologie bzw. CFM-Technologie und einer "Bidirectional-Forwarding-Detection"-Technologie bzw. BFD-Technologie ausgewählt sind.


 


Revendications

1. Procédé d'exploitation, d'administration et de maintenance, OAM, de réseau, comprenant les étapes consistant à :

recevoir (101), par un centre de gestion OAM unifié, un message d'alarme de défaut envoyé par un point de maintenance, MP, le message d'alarme de défaut contenant des informations de défaut ;

déterminer (102), par le centre de gestion OAM unifié d'après le message d'alarme de défaut, un premier ensemble de maintenance auquel le MP appartient, le premier ensemble de maintenance comprenant des MP utilisant une première technologie OAM;

interroger (103), par le centre de gestion OAM unifié, une base de données OAM, pour obtenir un deuxième ensemble de maintenance interagissant avec le premier ensemble de maintenance, le deuxième ensemble de maintenance comprenant des MP utilisant une deuxième technologie OAM, et la base de données OAM sauvegardant des informations d'interaction de différents ensembles de maintenance ; et

envoyer (104), par le centre de gestion OAM unifié, un message de notification de défaut à tous les MP du deuxième ensemble de maintenance ou à un MP qui est déterminé selon une politique figurant dans le deuxième ensemble de maintenance, le message de notification de défaut contenant les informations de défaut ;

la première technologie OAM et la deuxième technologie OAM étant sélectionnées parmi une technologie de gestion de défaut de connectivité, CFM, et une technologie de détection d'expédition bidirectionnelle, BFD.


 
2. Procédé selon la revendication 1, dans lequel
l'ensemble de maintenance comprend un domaine de maintenance, MD, ou un groupe d'entités de maintenance, MEG.
 
3. Procédé selon la revendication 1 ou 2, dans lequel la détermination, par le centre de gestion OAM unifié d'après le message d'alarme de défaut, d'un premier ensemble de maintenance comprend spécifiquement l'étape consistant à :

déterminer, par le centre de gestion OAM unifié, le premier ensemble de maintenance d'après le contenu du message d'alarme de défaut ; ou

déterminer, par le centre de gestion OAM unifié, le premier ensemble de maintenance d'après une adresse source du message d'alarme de défaut.


 
4. Procédé selon la revendication 3, dans lequel
le message d'alarme de défaut contient également des informations d'emplacement d'un dispositif de découverte de défaut et/ou des informations d'emplacement d'un dispositif de signalisation de défaut, et la détermination, par le centre de gestion OAM unifié, du premier ensemble de maintenance d'après le contenu du message d'alarme de défaut comprend spécifiquement l'étape consistant à :
déterminer, par le centre de gestion OAM unifié, le premier ensemble de maintenance d'après les informations de défaut et/ou les informations d'emplacement du dispositif de découverte de défaut et/ou les informations d'emplacement du dispositif de signalisation de défaut.
 
5. Procédé selon l'une quelconque des revendications 1 à 4, le procédé, avant l'interrogation, par le centre de gestion OAM unifié, d'une base de données OAM, pour obtenir un deuxième ensemble de maintenance interagissant avec le premier ensemble de maintenance, comprenant également une étape consistant à établir la base de données OAM,
l'établissement, par le centre de gestion OAM unifié, de la base de données OAM comprenant les étapes consistant à :

collecter, par le centre de gestion OAM unifié, des informations concernant des MP d'un réseau géré par le centre de gestion OAM unifié, les informations concernant les MP contenant des informations de topologie de réseau et des informations concernant une technologie OAM utilisée, qui sont celles des MP ;

établir, par le centre de gestion OAM unifié, les ensembles de maintenance d'après les informations concernant les MP ; et

établir, par le centre de gestion OAM unifié, les informations d'interaction pour un ensemble de maintenance qui doit effectuer une interaction OAM, l'établissement d'informations d'interaction pour un ensemble de maintenance qui doit effectuer une interaction OAM comprenant l'ajout, à des MP connectifs, d'un attribut d'interaction d'un MP connectif interagissant avec un autre ensemble de maintenance, de sorte que lorsqu'il existe de multiples MP qui appartiennent à des ensembles de maintenance différents sur un même dispositif de réseau, les multiples MP sont des MP connectifs.


 
6. Procédé selon la revendication 5, dans lequel
les réseaux correspondant aux ensembles de maintenance qui doivent effectuer une interaction OAM comprennent au moins un même dispositif de réseau ou couvrent un même chemin.
 
7. Procédé selon l'une quelconque des revendications 1 à 6, dans lequel la réception, par un centre de gestion OAM unifié, d'un message d'alarme de défaut envoyé par un point de maintenance, MP, comprend spécifiquement l'étape consistant à :
recevoir, par le centre de gestion OAM unifié, des données de formulaire XML transférées par le MP au moyen du protocole de configuration réseau NETCONF, les données de formulaire XML étant obtenues par transformation d'un objet d'un modèle de données de gestion OAM unifié, le modèle de données de gestion OAM unifié étant généré au moyen d'un format de modèle de données IETF YANG, et l'objet du modèle de données de gestion OAM unifié transportant les informations de défaut.
 
8. Procédé selon l'une quelconque des revendications 1 à 7, dans lequel l'envoi, par le centre de gestion OAM unifié, d'un message de notification de défaut à tous les MP du deuxième ensemble de maintenance ou à un MP qui est déterminé selon une politique figurant dans le deuxième ensemble de maintenance comprend spécifiquement l'étape consistant à :
envoyer, par le centre de gestion OAM unifié à tous les MP du deuxième ensemble de maintenance ou au MP qui est déterminé selon la politique, les données de formulaire XML transférées au moyen du NETCONF, les données de formulaire XML étant obtenues par transformation de l'objet du modèle de données de gestion OAM unifié, le modèle de données de gestion OAM unifié étant généré au moyen du format de modèle de données IETF YANG, et l'objet du modèle de données de gestion OAM unifié transportant les informations de défaut.
 
9. Centre de gestion d'exploitation, d'administration et de maintenance, OAM, unifié, comprenant :

une unité de réception (401), configurée pour recevoir un message d'alarme de défaut envoyé par un point de maintenance, MP, le message d'alarme de défaut contenant des informations de défaut ;

une unité de détermination (402), configurée pour déterminer, d'après le message d'alarme de défaut, un premier ensemble de maintenance auquel le MP appartient, le premier ensemble de maintenance comprenant des MP utilisant une première technologie OAM ;

une unité de traitement (403), configurée pour interroger une base de données OAM, pour obtenir un deuxième ensemble de maintenance interagissant avec le premier ensemble de maintenance, le deuxième ensemble de maintenance comprenant des MP utilisant une deuxième technologie OAM, et la base de données OAM sauvegardant des informations d'interaction de différents ensembles de maintenance ; et

une unité d'envoi (404), configurée pour envoyer un message de notification de défaut à tous les MP du deuxième ensemble de maintenance ou à un MP qui est déterminé selon une politique figurant dans le deuxième ensemble de maintenance, le message de notification de défaut contenant les informations de défaut ;

la première technologie OAM et la deuxième technologie OAM étant sélectionnées parmi une technologie de gestion de défaut de connectivité, CFM, et une technologie de détection d'expédition bidirectionnelle, BFD.


 
10. Centre de gestion OAM unifié selon la revendication 9, dans lequel l'unité de détermination est spécifiquement configurée pour : déterminer le premier ensemble de maintenance d'après le contenu du message d'alarme de défaut ; ou déterminer le premier ensemble de maintenance d'après une adresse source du message d'alarme de défaut.
 
11. Centre de gestion OAM unifié selon la revendication 10, dans lequel le message d'alarme de défaut contient également des informations d'emplacement d'un dispositif de découverte de défaut et/ou des informations d'emplacement d'un dispositif de signalisation de défaut, et l'unité de détermination est spécifiquement configurée pour déterminer le premier ensemble de maintenance d'après les informations de défaut et/ou les informations d'emplacement du dispositif de découverte de défaut et/ou les informations d'emplacement du dispositif de signalisation de défaut.
 
12. Centre de gestion OAM unifié selon l'une quelconque des revendications 9 à 11, le centre de gestion OAM unifié comprenant également une unité d'établissement, l'unité d'établissement comprenant spécifiquement :

une sous-unité de collecte, configurée pour collecter des informations concernant des MP d'un réseau géré par le centre de gestion OAM unifié, les informations concernant les MP contenant des informations de topologie de réseau et des informations concernant une technologie OAM utilisée, qui sont celles des MP ;

une première sous-unité d'établissement, configurée pour établir les ensembles de maintenance d'après les informations concernant les MP ; et

une deuxième sous-unité d'établissement, configurée pour établir les informations d'interaction pour un ensemble de maintenance qui doit effectuer une interaction OAM, l'établissement d'informations d'interaction pour un ensemble de maintenance qui doit effectuer une interaction OAM comprenant : l'ajout, à des MP connectifs, d'un attribut d'interaction d'un MP connectif interagissant avec un autre ensemble de maintenance, de sorte que lorsqu'il existe de multiples MP qui appartiennent à des ensembles de maintenance différents sur un même dispositif de réseau, les multiples MP sont des MP connectifs.


 
13. Centre de gestion OAM unifié selon l'une quelconque des revendications 9 à 12, dans lequel
l'unité de réception est spécifiquement configurée pour recevoir des données de formulaire XML transférées par le MP au moyen du protocole de configuration réseau NETCONF, les données de formulaire XML étant obtenues par transformation d'un objet d'un modèle de données de gestion OAM unifié, le modèle de données de gestion OAM unifié étant généré au moyen d'un format de modèle de données IETF YANG, et l'objet du modèle de données de gestion OAM unifié transportant les informations de défaut.
 
14. Centre de gestion OAM unifié selon l'une quelconque des revendications 9 à 13, dans lequel
l'unité d'envoi est spécifiquement configurée pour envoyer, à tous les MP du deuxième ensemble de maintenance ou au MP qui est déterminé selon la politique, les données de formulaire XML transférées au moyen du NETCONF, les données de formulaire XML étant obtenues par transformation de l'objet du modèle de données de gestion OAM unifié, le modèle de données de gestion OAM unifié étant généré au moyen du format de modèle de données IETF YANG, et l'objet du modèle de données de gestion OAM unifié transportant les informations de défaut.
 
15. Système de réseau, comprenant :

un point de maintenance, MP (501), configuré pour envoyer un message d'alarme de défaut au centre de gestion d'exploitation, d'administration et de maintenance, OAM (502), unifié selon l'une quelconque des revendications 9 à 14, le message d'alarme de défaut contenant des informations de défaut ;

le centre de gestion OAM (502), unifié selon l'une quelconque des revendications 9 à 14, configuré pour déterminer, d'après le message d'alarme de défaut, un premier ensemble de maintenance auquel le MP (501) appartient, le premier ensemble de maintenance comprenant des MP utilisant une première technologie OAM ;

configuré pour interroger une base de données OAM, pour obtenir un deuxième ensemble de maintenance interagissant avec le premier ensemble de maintenance, le deuxième ensemble de maintenance comprenant des MP utilisant une deuxième technologie OAM, et la base de données OAM sauvegardant des informations d'interaction de différents ensembles de maintenance ; et configuré pour envoyer un message de notification de défaut à tous les MP (503) du deuxième ensemble de maintenance ou à un MP (503) qui est déterminé selon une politique figurant dans le deuxième ensemble de maintenance, le message de notification de défaut contenant les informations de défaut ; et

tous les MP (503) du deuxième ensemble de maintenance ou le MP (503) qui est déterminé selon la politique étant configurés pour effectuer une interaction de défaut selon le message de notification de défaut ;

la première technologie OAM et la deuxième technologie OAM étant sélectionnées parmi une technologie de gestion de défaut de connectivité, CFM, et une technologie de détection d'expédition bidirectionnelle, BFD.


 




Drawing

















Cited references

REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Patent documents cited in the description