WO2017156675A1 - Système de maintenance d'administration d'opération - Google Patents

Système de maintenance d'administration d'opération Download PDF

Info

Publication number
WO2017156675A1
WO2017156675A1 PCT/CN2016/076248 CN2016076248W WO2017156675A1 WO 2017156675 A1 WO2017156675 A1 WO 2017156675A1 CN 2016076248 W CN2016076248 W CN 2016076248W WO 2017156675 A1 WO2017156675 A1 WO 2017156675A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
network
network element
maintenance
operation management
Prior art date
Application number
PCT/CN2016/076248
Other languages
English (en)
Chinese (zh)
Inventor
王昊
易粟
范小菁
王乐菲
薛文倩
松仓隆一
Original Assignee
富士通株式会社
王昊
易粟
范小菁
王乐菲
薛文倩
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 王昊, 易粟, 范小菁, 王乐菲, 薛文倩 filed Critical 富士通株式会社
Priority to PCT/CN2016/076248 priority Critical patent/WO2017156675A1/fr
Priority to CN201680076734.5A priority patent/CN108476149B/zh
Publication of WO2017156675A1 publication Critical patent/WO2017156675A1/fr

Links

Images

Definitions

  • the present invention relates to the field of communications, and in particular, to an Operation Administration Maintenance (OAM) system.
  • OAM Operation Administration Maintenance
  • Ethernet has evolved from a local area network to a metropolitan area network or a wide area network. Enterprises, schools, government departments, etc. use Ethernet to connect their respective local area networks to establish a virtual office environment, campus or community. As the network scale continues to expand, network devices become more diverse, and the number of network nodes grows geometrically. The network OAM system has become the key to the growth of operators or service providers.
  • the network OAM system includes two plane functions: a management plane performs network management and configuration functions and provides interfaces to network administrators; a network plane performs data transmission and reception and routing functions, and is monitored by the management plane. And management.
  • Ethernet OAM such as IEEE 802.3 (for example, called 802.3ah) and IEEE 802.1 (for example, 802.1ag) defined by the International Telecommunication Union (ITU); Corresponding to the Media Access Control (MAC) layer of the Open System Interconnection (OSI) Layer 7 protocol and the Logical Link Control (LLC) layer.
  • IEEE 802.3ah for example, called 802.3ah
  • IEEE 802.1ag for example, 802.1ag
  • the 802.1ag control information may be carried by an Ethernet bearer or by a wireless local area network (802.11).
  • the above two protocols can also be used in combination to discover, verify, test, isolate, and recover various faults in large-scale networks.
  • FIG 1 is a schematic diagram of a typical multi-layer network OAM deployment. As shown in Figure 1, different OAM protocols are used at different layers of the network. Each layer uses its own OAM protocol, such as customers, service providers, and operators deploy OAM tools on their respective layers to listen to the network.
  • OAM protocols are used at different layers of the network.
  • Each layer uses its own OAM protocol, such as customers, service providers, and operators deploy OAM tools on their respective layers to listen to the network.
  • the Multi-Protocol Label Switch is used to listen to the MPLS network of the carrier (such as the carrier 1 shown in Figure 1).
  • the IEEE 802.1ag OAM is used for monitoring operations. Ethernet (for example, operator 2 shown in Figure 1).
  • IEEE 802.1ag OAM is also deployed at the service provider layer and the client layer, while IEEE 802.3ah is used to listen to the customer equipment (CE, Customer Equipment) and the provider side (UPE, User-facing Provider Edge). Between devices Link.
  • Ethernet link layer OAM such as defined by IEEE 802.3ah
  • OAM Ethernet link layer
  • the main contents defined by IEEE 802.3ah include: Discovery, Link Monitoring, Remote Failure Indication, and Remote Loopback.
  • the main contents defined by IEEE 802.1ag include: Continuity Check, Link Trace and loopback testing.
  • Metro Ethernet Forum proposes the OAM architecture of Carrier Ethernet.
  • FIG. 2 is a schematic diagram of an OAM architecture of a carrier-grade Ethernet.
  • a function of a carrier-grade Ethernet network in a management plane may be divided into multiple sub-networks, for example, a network management system (NMS).
  • NMS network management system
  • EMS element management system
  • NE Network Element
  • Fault management on the EMS includes: alert notification, association and filtering; fault acknowledgment, elimination and recovery; forwarding of alerts/events to the NMS.
  • Fault management on the NMS includes: when the device automatically detects a fault, repairs the fault or provides a temporary solution and notifies the user; provides backup management, protection policies, routine maintenance, fault notification, and fault tracking.
  • IEEE 802.3ah and the like currently only involve a single network element, and there is no definition of the upper layer interface, and cannot be fully integrated with the management system; and the EMS function cannot be separated, and the support for the NMS function is also limited.
  • the carrier-class or carrier-class OAM architecture only gives a scheme of dividing into multiple subnets, but for network equipment, it is difficult to standardize functional modules and interfaces.
  • An embodiment of the present invention provides an operation management and maintenance system, including:
  • a network element management system that manages one or more network elements of a particular type, including one or more management function execution units;
  • each of the network elements includes an operation management maintenance client and one or more network element function execution units, and the operation management maintenance client communicates with the network element through one or more interfaces
  • the management system performs interaction; the operation management maintenance client controls the one or more network element function execution units to interact with other network elements.
  • the embodiment of the invention further provides an operation management and maintenance system, comprising:
  • each of the network elements includes a network element management system, an operation management maintenance client, and one or more network element function execution units;
  • the network element management system includes one or more management function execution units; the operation management maintenance client interacts with the network element management system through one or more interfaces, and the operation management maintenance client controls the One or more network element function execution units interact with other network elements.
  • the beneficial effects of the embodiments of the present invention are: dividing the OAM system into at least two parts of the EMS and the NE and redefining each interface, where each NE includes at least one OAM client and one or more network element function execution units. Therefore, the EMS function can be separated, the NE can be fully integrated with the management system, the standardization of the function modules and interfaces can be easily realized, the reliability and scalability of the OAM system can be improved, and the OAM can be satisfied in the case where the network system becomes larger and larger. Actual requirements.
  • FIG. 1 is a schematic diagram of a typical multi-layer network OAM deployment
  • FIG. 2 is a schematic diagram of an OAM architecture of a carrier Ethernet
  • FIG. 3 is a schematic diagram of an OAM system according to an embodiment of the present invention.
  • FIG. 4 is another schematic diagram of an OAM system according to an embodiment of the present invention.
  • FIG. 5 is another schematic diagram of an OAM system according to an embodiment of the present invention.
  • FIG. 6 is another schematic diagram of an OAM system according to an embodiment of the present invention.
  • FIG. 7 is another schematic diagram of an OAM system according to an embodiment of the present invention.
  • a network element can be understood as the smallest unit that can be monitored and managed in OAM. For example, it may be a client connected to a network (such as a mobile terminal, a personal computer, a printer, etc.), or may be a router, a switch, a server, or the like.
  • a network element can be understood as one or more hardware devices, and can also be understood as one or more logical units installed on a hardware device.
  • Ethernet is taken as an example for description, that is, the present application redefines the architecture of OAM in 802.3ah.
  • the present invention is not limited to Ethernet, and can be applied to other networks.
  • FIG. 3 is a schematic diagram of an OAM system according to an embodiment of the present invention. As shown in FIG. 3, the OAM system 300 may include:
  • EMS 301 which manages one or more network elements 302 of a particular type, including one or more management function execution units 3011;
  • each network element 302 includes an OAM client 3021 and one or more network element function execution units 3022; the OAM client 3021 interacts with the EMS 301 through one or more interfaces, OAM Client 3021 controls one or more network element function execution units 3022 to interact with other network elements (not shown in FIG. 3).
  • each functional module of the EMS 301 does not directly interact with each functional module of the network element 302.
  • Each network element 302 interacts with the EMS 301 through the OAM client 3021.
  • the OAM client 3021 can interact with one or more network element function execution units 3022 (also referred to as other sub-layers, such as OAM sub-layers) of the network element 302 through primitives; the OAM sub-layer can be located in an open system interconnection ( OSI, Open System Interconnection) The data link layer of the reference model, between the Media Access Control (MAC) layer and the Logical Link Control (LLC) sublayer.
  • OSI Open System Interconnection
  • the EMS function can be separated, the NE can be fully integrated with the management system, and the standardization of the function modules and interfaces can be easily realized, and the reliability and scalability of the OAM can be improved.
  • the OAM system 400 may include an EMS 301 and a network element 302, as described above.
  • the OAM system 400 may further include:
  • An NMS 401 that manages one or more EMSs 301; interacts with the EMS 301 through one or more interfaces.
  • the architecture shown in FIG. 3 may be used, that is, the NMS may not be configured; for example, if the network scale is particularly large, the architecture shown in FIG. 4 may be used. , you can configure NMS. This not only makes it easy to standardize functional modules and interfaces, but also maintains the flexibility and scalability of the architecture.
  • FIG. 3 and FIG. 4 show the case of centralized control of the EMS function, but the present invention is not limited thereto, and for example, the EMS function may be distributed to each NE.
  • FIG. 5 is another schematic diagram of an OAM system according to an embodiment of the present invention.
  • the OAM system 500 may include: an NMS 501, an EMS 502, and an NE 503.
  • the EMS 502 is distributed on each NE 503, and the EMS 502 may include one or more management function execution units (not shown in FIG. 5); that is, each NE 503 may include an EMS 502, and each NE 503 further includes a The OAM client 5031 and one or more network element function execution units 5032.
  • the OAM system may not include the NMS, for example, if the network size is not particularly large.
  • FIG. 6 is another schematic diagram of an OAM system according to an embodiment of the present invention.
  • the OAM system 600 may include: one or more NEs 503; wherein the EMS 502 is distributed on each NE 503. That is, each NE 503 can include an EMS 502, an OAM client 5031, and one or more network element function execution units 5032;
  • the EMS 502 can include one or more management function execution units (not shown in Figure 6); the OAM guest The client 5031 interacts with the EMS 502 through one or more interfaces, and the OAM client 5031 controls one or more network element function execution units 5032 to interact with other network elements (not shown in FIG. 6).
  • the OAM system includes two layers: an EMS and a network element.
  • the OAM system includes three layers: an NMS, an EMS, and a network element.
  • the present invention will be described in detail below by taking only the three-layer architecture shown in FIG. 4 as an example, but the present invention is not limited thereto.
  • FIG. 7 is another schematic diagram of an OAM system according to an embodiment of the present invention.
  • the OAM system 700 may include an NMS 601, an EMS 602, and an NE 603.
  • the EMS 602 may be one or more, and each EMS 602.
  • One or more NE 603s can be managed.
  • FIG. 7 shows only one EMS 602 and one NE 603, but the invention is not limited thereto.
  • EMS 602 can include:
  • a configuration unit 6021 (also referred to as a configurator) that manages configuration information of one or more network elements 603;
  • Aggregation unit 6022 (also referred to as aggregation), which manages alarm information of one or more network elements 603 based on preset rules;
  • Fault isolation unit 6023 (also referred to as failure isolation), which isolates and analyzes faults of one or more network elements 603;
  • a failure recovery unit 6024 (also referred to as failure recovery) that performs recovery operations on one or more network elements 603 to eliminate network failures;
  • a remote test management unit 6025 (also referred to as a remote test manager) that manages tests performed by one or more network elements 603.
  • management function execution units such as a configuration unit, an aggregation unit, a fault isolation unit, and the like
  • the unit may include one or more of the above units, and may also include other functional units, for example, one or more management function execution units may also be customized.
  • the network element 603 can include:
  • OAM client 6031 OAM client
  • each network element 603 interacts with the EMS 602 through the OAM client 6031.
  • the remote fault indication unit 6032 (also referred to as RFI, remote failure indication), which indicates that the network element 603 or other network element is faulty;
  • Link monitoring unit 6033 (also referred to as LM, link monitor), which links to the link between network elements 603 Line listening operation;
  • a remote test unit 6034 (also referred to as a remote test agent), which performs a test operation on the network element 603 or other network elements;
  • a capability discovery unit 6035 (also referred to as capability discovery) performs OAM capability discovery operations on the network element 603 or other network elements.
  • each network element interacts with the EMS through the OAM client, and in addition, each module in the EMS and the network element is redefined; thus, the logical relationship between each module in the architecture is The definition is clearer and can improve the reliability and scalability of OAM.
  • the network element function execution unit in 603 may include one or more of the above units, and may also include other functional units, for example, one or more network element function execution units may also be customized.
  • interfaces between the NMS 601 and the EMS 602 such as interface a, interface b, interface c, interface d and interface e as shown in FIG. 7; between EMS 602 and NE 603
  • FIG. 7 there may be an interface h between the aggregation unit 6022 of the EMS 602 and the fault isolation unit 6023, and an interface j between the fault isolation unit 6023 and the fault recovery unit 6024 of the EMS 602.
  • an interface m is provided between the OAM client 6031 of the NE 603 and the remote fault indication unit 6032, and an interface n is provided between the OAM client 6031 of the NE 603 and the link listening unit 6033.
  • An O interface between the OAM client 6031 and the remote test unit 6034 of the 603 has an interface p between the OAM client 6031 of the NE 603 and the capability discovery unit 6035.
  • interface q there may be multiple interfaces between the NE 603 and other NEs 603, such as interface q, interface r, interface s, and interface t as shown in FIG.
  • the configuration unit 6021 can receive the current configuration sent by the NMS 601 for requesting a certain network element. Set the information or configure the information of the adjustment information, and send the current configuration information or configuration adjustment information of the network element to the NMS 601;
  • NMS 601 makes configuration parameter adjustments to NE 603 via EMS 602, or NMS 601 requests EMS 602 for current configuration information for NE 603; EMS 602 can send an acknowledgment message to NMS 601 to indicate a successful configuration parameter adjustment, or EMS 602 The current configuration information of the NE 603 can be sent to the NMS 601.
  • the aggregating unit 6022 can receive the message sent by the NMS 601 for requesting the alarm information of a certain network element, and send the alarm information that meets the preset rule to the NMS 601; in addition, the aggregating unit 6022 can also receive the NMS 601. Request to clear the list of alerts related to a single fault that has been resolved.
  • NMS 601 requests EMS 602 to send an active alert list for a particular NE or a set of NEs, the request may include filtering rules such as type, severity, time, and NE ID; EMS 602 may request NMS based on the request 601 returns a list of active alarms that match the rules.
  • the fault isolation unit 6023 can send the analysis result of the fault cause to the NMS 601;
  • the EMS 602 returns to the NMS 601 the result of the current failure (which may be referred to as a root cause) analysis, which may include some information for further study by the NMS 601, or an unconfirmable analysis result.
  • a root cause the result of the current failure (which may be referred to as a root cause) analysis, which may include some information for further study by the NMS 601, or an unconfirmable analysis result.
  • failure recovery unit 6024 receives a message sent by NMS 601 requesting failure recovery without a mitigation of the failure, and transmits a recovery result to NMS 601.
  • the NMS 601 can request to initiate or initiate a recovery operation, and the EMS 602 can return the result of the recovery operation to the NMS 601.
  • the remote test management unit 6025 can receive the message sent by the NMS 601 for testing, and send the test result to the NMS 601;
  • the NMS 601 can request to initiate a test operation, the EMS 602 can perform the test, and return the results of the test operation to the NMS 601.
  • the configuration unit 6021 can interact with the OAM client 6031 based on a request from the NMS 601 to perform configuration management on the network element 503, for example, the interaction information can include parameters, thresholds, and the like.
  • the EMS 602 can configure the parameters and conditions of the NE 603 based on the request of the NMS 601.
  • the aggregating unit 6022 can receive the alarm information sent by the OAM client 6031 and the feature information related to the single fault;
  • the OAM client 6031 can send a set of active alarms for the current NE and feature information about a single network failure event; the alert can be related to a certain rule, such as an alert propagation path, a particular geographic region, a particular device, or from the same source. Repeat the alert.
  • Alarms can be divided into multiple sets, where the alarms in the same set have a high probability of being caused by the same network failure, and the related set can also contain communication characteristic information, which is considered to have a high probability Caused by the same network failure.
  • aggregation unit 6022 can forward the alert information and feature information associated with a single fault to fault isolation unit 6023.
  • the alert information and feature information can be forwarded to the fault isolation unit 6023 to look up the faulty root cause; wherein the set of such information may come from multiple network elements 603, thereby allowing network faults to be viewed from a broader perspective.
  • the fault isolation unit 6023 receives the alarm information sent by the OAM client 6031 and characteristic information related to a single fault, and analyzes the cause of the fault;
  • the OAM client 6031 can send an active alert set and feature information about a single network failure event; the alert can be related to a certain rule, such as an alert propagation path, a particular geographic region, a particular device, or a duplicate alert from the same source.
  • Alarms can be divided into multiple sets, where the alarms in the same set have a high probability of being caused by the same network failure, and the related set can also contain communication characteristic information, which is considered to have a high probability Caused by the same network failure.
  • the fault isolation unit 6023 may send a message to the fault recovery unit 6024 to initiate a recovery operation if the cause of the failure is obtained.
  • fault isolation is the process of being able to identify and identify the cause of a network failure. Once a root cause of a network failure is found, fault isolation initiates a recovery operation.
  • the fault recovery unit 6024 can interact with the OAM client 6031 to perform a recovery operation according to the result of the fault isolation and the preset rule.
  • the EMS 602 sends a request to the NE 603 to repair the fault based on the results of the fault isolation and the predefined rules. Once the fault is successfully recovered, the EMS 602 can send a request to the NMS 601 requesting that the active alert for the NE 603 be emptied.
  • the remote test management unit 6025 can also interact with the OAM client 6031 to perform a test operation;
  • EMS 602 requests from remote test unit 6034 in NE 603 via OAM client 6031
  • the remote test unit 6034 in the NE 603 will return the test results to the EMS 602 via the OAM client 6031.
  • the remote fault indication unit 6032 can interact with the OAM client 6031 to perform a remote fault indication operation if the local fault is detected;
  • the remote fault indication unit 6032 will initiate an RFI operation through the OAM client 6031; in addition, fault information about other NEs may also be notified to the OAM client 6031 of the NE 603 via the remote fault indication unit 6032.
  • the link listening unit 6033 can interact with the OAM client 6031 to perform a link listening operation
  • the link monitoring unit 6033 can initiate a link listening operation through the OAM client 6031, and the OAM client 6031 can collect the communication characteristic information and the result of receiving the link monitoring for acquiring statistical data about the communication status.
  • remote test unit 6034 can interact with OAM client 6031 to perform a test operation
  • the OAM client 6031 can initiate a test operation (eg, a loopback test) based on a request from the EMS 602, or can automatically initiate a test operation based on the configuration information.
  • a test operation eg, a loopback test
  • the capability discovery unit 6035 can interact with the OAM client 6031 to perform a capability discovery operation
  • capability discovery is the first phase of identifying remote NE OAM capabilities, and this information is provided to the OAM client 6031 to ensure that OAM operations are supported.
  • the remote fault indication unit 6032 is further configured to exchange remote fault indication information between other network elements and the OAM client 6031 of the network element 603.
  • information about local failures can be exchanged between OAM clients 6032 of multiple network elements.
  • the link monitoring unit 6033 is further configured to exchange link monitoring information between the other network element and the OAM client 6031 of the network element 603.
  • information about the communication link can be exchanged between OAM clients 6031 of a plurality of network elements.
  • variables from the Management Information Base (MIB) can also be exchanged between the OAM clients 6031.
  • the remote testing unit 6034 is further configured to exchange test information between other network elements and the OAM client 6031 of the network element 603.
  • information about the test can be exchanged between OAM clients 6032 of multiple network elements.
  • the capability discovery unit 6035 is further configured to exchange capability information between other network elements and the OAM client 6031 of the network element 603.
  • information about capabilities can be exchanged between OAM clients 6032 of multiple network elements.
  • FIG. 7 is a schematic diagram showing a specific embodiment of the embodiment of the present invention, but the invention is not limited thereto, for example, a part of the function execution unit or part of the interface may be used, or Define other functional execution units or interfaces.
  • the OAM system is at least divided into two parts, EMS and NE, and redefines each interface.
  • the NE includes an OAM client and one or more network element function execution units. Therefore, the EMS function can be separated, the NE can be fully integrated with the management system, the standardization of the function modules and interfaces can be easily realized, the reliability and scalability of the OAM system can be improved, and the OAM can be satisfied in the case where the network system becomes larger and larger. Actual requirements.
  • the above apparatus and method of the present invention may be implemented by hardware or by hardware in combination with software.
  • the present invention relates to a computer readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to cause the logic component to implement the various methods described above Or steps.
  • the present invention also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, or the like.
  • One or more of the functional blocks described in the figures and/or one or more combinations of functional blocks may be implemented as a general purpose processor, digital signal processor (DSP) for performing the functions described herein.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks described with respect to the figures and/or one or more combinations of functional blocks may also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors One or more microprocessors in conjunction with DSP communication or any other such configuration.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un système de maintenance d'administration d'opération comprenant : un système de gestion d'éléments de réseau pour gérer un ou plusieurs éléments de réseau d'un type spécifique ; et un ou plusieurs éléments de réseau, chacun des éléments de réseau comprenant un client de maintenance d'administration d'opération et une ou plusieurs unités d'exécution de fonction d'élément de réseau, le client de maintenance d'administration d'opération interagissant avec le système de gestion d'éléments de réseau au moyen d'une ou plusieurs interfaces et le client de maintenance d'administration d'opération commandant l'interaction d'une ou plusieurs unités d'exécution de fonction d'élément de réseau avec les autres éléments de réseau. Ainsi, une fonction EMS peut être séparée et un NE peut être entièrement intégré à un système de gestion, ce qui facilite la réalisation de la standardisation d'un module fonctionnel et d'une interface, permet d'améliorer la fiabilité et l'extensibilité de l'OAM et satisfait les exigences réelles de l'OAM lorsque le système de réseau s'agrandit.
PCT/CN2016/076248 2016-03-14 2016-03-14 Système de maintenance d'administration d'opération WO2017156675A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2016/076248 WO2017156675A1 (fr) 2016-03-14 2016-03-14 Système de maintenance d'administration d'opération
CN201680076734.5A CN108476149B (zh) 2016-03-14 2016-03-14 操作管理维护系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/076248 WO2017156675A1 (fr) 2016-03-14 2016-03-14 Système de maintenance d'administration d'opération

Publications (1)

Publication Number Publication Date
WO2017156675A1 true WO2017156675A1 (fr) 2017-09-21

Family

ID=59851451

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/076248 WO2017156675A1 (fr) 2016-03-14 2016-03-14 Système de maintenance d'administration d'opération

Country Status (2)

Country Link
CN (1) CN108476149B (fr)
WO (1) WO2017156675A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050097216A1 (en) * 2003-10-10 2005-05-05 Nortel Networks Limited Method and network for delivering management software for a network element
CN101924649A (zh) * 2010-08-03 2010-12-22 中兴通讯股份有限公司 一种无源光网络系统中光网络单元的远程管理方法和系统
US20140342721A1 (en) * 2008-04-16 2014-11-20 Nokia Solutions And Networks Oy Managing a network element
CN105049245A (zh) * 2015-07-02 2015-11-11 深圳市西迪特科技有限公司 Epon的网元管理系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100456711C (zh) * 2007-02-09 2009-01-28 华为技术有限公司 网元状态监测方法和网络管理设备
CN101350735A (zh) * 2007-07-20 2009-01-21 中兴通讯股份有限公司 一种告警同步方法
CN101729282A (zh) * 2008-10-30 2010-06-09 中兴通讯股份有限公司 单板告警的处理方法和装置
JP2013165448A (ja) * 2012-02-13 2013-08-22 Sony Corp 機器管理装置及び機器管理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050097216A1 (en) * 2003-10-10 2005-05-05 Nortel Networks Limited Method and network for delivering management software for a network element
US20140342721A1 (en) * 2008-04-16 2014-11-20 Nokia Solutions And Networks Oy Managing a network element
CN101924649A (zh) * 2010-08-03 2010-12-22 中兴通讯股份有限公司 一种无源光网络系统中光网络单元的远程管理方法和系统
CN105049245A (zh) * 2015-07-02 2015-11-11 深圳市西迪特科技有限公司 Epon的网元管理系统

Also Published As

Publication number Publication date
CN108476149B (zh) 2020-12-15
CN108476149A (zh) 2018-08-31

Similar Documents

Publication Publication Date Title
US10623293B2 (en) Systems and methods for dynamic operations, administration, and management
US10142203B2 (en) Ethernet fault management systems and methods
US20090161569A1 (en) System and method for facilitating carrier ethernet performance and quality measurements
EP3203684B1 (fr) Procédé, appareil et système pour les opérations, l'administration et la maintenance de réseau
EP4142239A1 (fr) Surveillance de performance de réseau et gestion de défauts basée sur des évaluations de l'état d'un lien de réseau étendu
US11805011B2 (en) Bulk discovery of devices behind a network address translation device
US20100161769A1 (en) Method and System for Virtual LAN Media Access Control Trouble Diagnostics
EP3069474B1 (fr) Corrélation de comptes rendus d'événements
WO2008090110A1 (fr) Entités de réseau fonctionnelles dans un système de communications
CN108353027B (zh) 一种用于检测端口故障的软件定义网络系统及方法
US8467301B2 (en) Router misconfiguration diagnosis
EP4080850A1 (fr) Intégration de dispositifs réseau virtualisés à un système d'assurance réseau en nuage
US11765059B2 (en) Leveraging operation, administration and maintenance protocols (OAM) to add ethernet level intelligence to software-defined wide area network (SD-WAN) functionality
WO2017156675A1 (fr) Système de maintenance d'administration d'opération
CN111343033B (zh) 一种面向多层差异的网络管理系统
Vieira et al. THANOS: Teleprotection holistic application for ONOS controller
US20080140825A1 (en) Determining availability of a network service
Yu et al. A practical scheme for MPLS fault monitoring and alarm correlation in backbone networks
US20240223434A1 (en) Detecting wired client stuck
EP4395265A1 (fr) Détection de blocage de client filaire
Ballani et al. Fault management using the CONMan abstraction
CN118282886A (zh) 检测有线客户端卡住
US20230231776A1 (en) Conversational assistant dialog design
Riggio et al. Up in the clouds: a taxonomical analysis of network management functionalities from a network as a service perspective
CN114244468A (zh) Otn链路快速定位故障点的方法、存储介质及设备

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16893840

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16893840

Country of ref document: EP

Kind code of ref document: A1