WO2021073367A1 - 一种数据处理方法、设备及系统 - Google Patents

一种数据处理方法、设备及系统 Download PDF

Info

Publication number
WO2021073367A1
WO2021073367A1 PCT/CN2020/116542 CN2020116542W WO2021073367A1 WO 2021073367 A1 WO2021073367 A1 WO 2021073367A1 CN 2020116542 W CN2020116542 W CN 2020116542W WO 2021073367 A1 WO2021073367 A1 WO 2021073367A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network device
eca
extended
network management
Prior art date
Application number
PCT/CN2020/116542
Other languages
English (en)
French (fr)
Inventor
陶冉
王子韬
吴钦
秦晓鹏
杨宇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20876189.0A priority Critical patent/EP4030691A4/en
Publication of WO2021073367A1 publication Critical patent/WO2021073367A1/zh
Priority to US17/720,493 priority patent/US20220239572A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/12—Arrangements for remote connection or disconnection of substations or of equipment thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring

Definitions

  • This application relates to the field of communication technology, and in particular to a data processing method, device and system.
  • the network configuration protocol is a network management protocol based on the extensible markup language (XML), which provides a programmable method for configuring and managing network devices. Users can set parameters, obtain parameter values, and obtain statistical information through this protocol.
  • NETCONF messages use XML format, with powerful filtering capabilities, and each data item has a fixed element name and location, which enables different devices of the same manufacturer to have the same access method and result presentation method.
  • the device can also get the same effect by mapping XML, which makes it very convenient in the development of third-party software, and it is easy to develop special customized network management software under the environment of mixing different manufacturers and different devices. With the assistance of such network management software, using the NETCONF function will make the configuration management of network equipment easier and more efficient.
  • YANG (Yet Another Next Generation) is a data modeling language for NETCONF access.
  • NETCONF uses YANG to model various operations, data, and notifications, which has good readability and scalability. Both devices and clients can use YANG for modeling. After the YANG model is provided on the device side, the client can automatically generate the corresponding access model code according to the tool to save development workload.
  • Restconf is a protocol based on Hypertext Transfer Protocol (HTTP), which configures data in YANG through the data storage concept defined in NETCONF.
  • HTTP Hypertext Transfer Protocol
  • Telemetry (telemetry) technology is a remote high-speed data collection technology from physical network equipment or virtual network equipment. Through the push mode, a more real-time and high-speed data collection function is provided. At the same time, the utilization of network equipment and network in the collection process is improved.
  • the event-condition-action (ECA) model can model general strategies and allow monitoring of a certain type of parameters in the device/controller. When the trigger condition is met, an event occurs. In actual network scenarios, the action part of the ECA model only supports the reconfiguration of the network devices running the ECA model or the trigger of recording the relevant time.
  • embodiments of the present application provide a data processing method, device, and system.
  • the network management device sends an extended ECA instance to the network device, and the action part included in the extended ECA instance can trigger the telemetry function of the network device. Therefore, the network device can trigger the telemetry function according to the event part included in the extended ECA instance, and send corresponding telemetry data to the network management device.
  • the extended ECA model automatic correlation between network events and telemetry is realized.
  • a data processing method includes that a network management device generates an extended ECA instance, the extended ECA instance includes a first event, a first condition, and a first action, and the first action includes A first object identifier and a first indicator type, the first object identifier indicates a first object to be detected, the first indicator type indicates a performance indicator of the first object to be detected, and the extended ECA instance is used to indicate
  • the network device managed by the network management device sends first detection data to the network management device according to the first event and the first condition, and the network device includes the first object to be detected. Then, the network management device sends a first message to the network device, where the first message includes the extended ECA instance. In addition, the network management device receives a second message sent by the network device, where the second message includes the first detection data.
  • the network device may trigger the telemetry function according to the event part included in the extended ECA instance, and send corresponding telemetry data to the network management device.
  • the extended ECA model automatic correlation between network events and telemetry is realized.
  • the method before the network management device receives the second message sent by the network device, the method further includes: the network management device sends a request message to the network device, so The request message is used to request the network device to send the second message.
  • the sending of the request message by the network management device to the network device includes: the network management device sending the request message to the network device according to a preset frequency.
  • the method before the network management device generates the extended ECA instance, the method further includes: the network management device obtains an extended ECA model, and the extended ECA model instructs the network manager The device generates the extended ECA instance according to the extended ECA model and the event that needs to be monitored.
  • the first action further includes a second object identifier and a second indicator type
  • the second object identifier indicates a second object to be detected
  • the second indicator type indicates the performance of the second object to be detected
  • the extended ECA instance is also used to instruct the network device to send the network management device corresponding to the second indicator type for the second standby according to the first event and the first condition.
  • the second detection data of the detection object the network device includes the second object to be detected; the second message also includes the second detection data.
  • the first action further includes a group identifier, the group identifier indicating a service type associated with the extended ECA instance.
  • the first action further includes an enable flag, and the enable flag is used to enable the first action.
  • the first action further includes a first operation type and/or a first index value type, the first operation type indicates an attribute of the first detection data, and the first index value type indicates the The data type of the first detection data.
  • the method before the network management device sends the first message to the network device, the method further includes: the network management device establishes the network management device and the network device The network configuration protocol between NETCONF sessions or RESTCONF sessions.
  • a data processing method includes: a network device receives a first message sent by a network management device, the first message includes an extended ECA instance, the extended ECA instance includes a first event, A first condition and a first action, the first action includes a first object identifier and a first indicator type, the first object identifier indicates a first object to be detected, and the first indicator type indicates the first object to be detected
  • the performance index of the object the network device includes the first object to be detected.
  • the network device determines that the first condition is established, the network device determines that the first event occurs.
  • the network device sends a second message to the network management device, where the second message includes the first detection data.
  • the network device may trigger the telemetry function according to the event part included in the extended ECA instance, and send corresponding telemetry data to the network management device.
  • the extended ECA model automatic correlation between network events and telemetry is realized.
  • the method before the network device sends the second message to the network management device, the method further includes: the network device receives the request message sent by the network management device, so The request message is used to request the network device to send the second message.
  • the first action further includes a second object identifier and a second indicator type
  • the second object identifier indicates a second object to be detected
  • the second indicator type indicates the performance of the second object to be detected
  • the network device includes the second object to be detected
  • the second message further includes the second detection data
  • the second detection data corresponds to the second indicator type and is directed to the first 2. The detection data of the object to be detected.
  • the first action further includes a group identifier, the group identifier indicating a service type associated with the extended ECA instance, and the first detection data is detection data associated with the service type.
  • the first action further includes an enable flag, where the enable flag is used to enable the first action, and the network device determines the first action.
  • the method further includes: the network device starts to run the sending function of the detection data associated with the first action according to the enable flag.
  • the second message further includes a group identifier, and the group identifier indicates a service type associated with the extended ECA instance.
  • the second message further includes an event identifier, and the event identifier indicates the first event.
  • the second message further includes the first object identifier and the first indicator type.
  • the first condition is a condition that the first object to be detected meets the performance index indicated by the first index type.
  • the first condition is that the first object to be detected meets the condition of the performance index indicated by the third index type, wherein the third index type is consistent with the performance index indicated by the third index type.
  • the types of the first indicators are different.
  • a network management device in a third aspect, has the function of realizing the behavior of the network management device in the foregoing method.
  • the functions can be implemented based on hardware, or implemented by corresponding software based on hardware.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the network management device includes a processor and an interface, and the processor is configured to support the network management device to perform corresponding functions in the foregoing method.
  • the interface is used to support communication between the network management device and the network device, and to receive the information or instructions involved in the above method from the network device.
  • the network management device may further include a memory, which is used for coupling with the processor and stores necessary program instructions and data of the network management device.
  • the network management device includes a processor, a transmitter, a receiver, a random access memory, a read-only memory, and a bus.
  • the processor is respectively coupled to the transmitter, the receiver, the random access memory, and the read-only memory through the bus.
  • the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to boot the system to start the network management device into a normal operating state. After the network management device enters the normal operating state, the application program and the operating system are run in the random access memory, so that the processor executes the first aspect or the method in any possible implementation manner of the first aspect.
  • a network management device in a fourth aspect, includes a main control board and an interface board, and may further include a switching network board.
  • the network management device is used to execute the first aspect or the method in any possible implementation manner of the first aspect.
  • the network management device includes a module for executing the first aspect or the method in any possible implementation manner of the first aspect.
  • a network management device in a fifth aspect, includes a controller and a first forwarding sub-device.
  • the first forwarding sub-device includes: an interface board, and further, may also include a switching network board.
  • the first forwarding sub-device is used to perform the function of the interface board in the fourth aspect, and further, may also perform the function of the switching network board in the fourth aspect.
  • the controller includes a receiver, a processor, a transmitter, a random access memory, a read-only memory, and a bus. Among them, the processor is respectively coupled to the receiver, the transmitter, the random access memory, and the read-only memory through the bus.
  • the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to guide the system to start, and the controller is guided to enter a normal operating state.
  • the application program and the operating system are run in the random access memory, so that the processor executes the function of the main control board in the fourth aspect.
  • a computer storage medium for storing programs, codes, or instructions used by the above-mentioned network management device.
  • the processor or hardware device executes these programs, codes or instructions, the network management device in the first aspect can be completed. Function or step.
  • a network device in a seventh aspect, has a function of realizing the behavior of the network device in the foregoing method.
  • the functions can be implemented based on hardware, or implemented by corresponding software based on hardware.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the network device includes a processor and an interface, and the processor is configured to support the network device to perform corresponding functions in the foregoing method.
  • the interface is used to support the communication between the network device and the network management device, and send the information or instructions involved in the above method to the network management device.
  • the network device may further include a memory, which is used for coupling with the processor and stores program instructions and data necessary for the network device.
  • the network device includes: a processor, a transmitter, a receiver, a random access memory, a read-only memory, and a bus.
  • the processor is respectively coupled to the transmitter, the receiver, the random access memory, and the read-only memory through the bus.
  • the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to boot the system to boot the network device into a normal operating state. After the network device enters the normal operating state, the application program and the operating system are run in the random access memory, so that the processor executes the second aspect or the method in any possible implementation manner of the second aspect.
  • a network device in an eighth aspect, includes a main control board and an interface board, and further, may also include a switching network board.
  • the network device is used to execute the second aspect or the method in any possible implementation manner of the second aspect.
  • the network device includes a module for executing the second aspect or the method in any possible implementation manner of the second aspect.
  • a network device in a ninth aspect, includes a controller and a second forwarding sub-device.
  • the second forwarding sub-device includes: an interface board, and further, may also include a switching network board.
  • the second forwarding sub-device is used to perform the function of the interface board in the eighth aspect, and further, may also perform the function of the switching network board in the eighth aspect.
  • the controller includes a receiver, a processor, a transmitter, a random access memory, a read-only memory, and a bus. Among them, the processor is respectively coupled to the receiver, the transmitter, the random access memory, and the read-only memory through the bus.
  • the basic input/output system solidified in the read-only memory or the bootloader in the embedded system is used to guide the system to start, and the controller is guided to enter a normal operating state.
  • the application program and the operating system are run in the random access memory, so that the processor executes the function of the main control board in the eighth aspect.
  • a computer storage medium for storing programs, codes, or instructions used by the above-mentioned network device.
  • the processor or hardware device executes these programs, codes or instructions, the network device in the second aspect can be completed. Function or step.
  • a network system in an eleventh aspect, includes a network management device and a network device.
  • the network management device is the network management device in the aforementioned third aspect or the fourth aspect or the fifth aspect, and the network device is the aforementioned network management device.
  • the network device in the seventh aspect or the eighth aspect or the ninth aspect.
  • the network management device generates and sends an extended ECA instance to the network device.
  • the network device determines that the first condition in the extended ECA instance is satisfied, the network device triggers the extended ECA instance.
  • the occurrence of the first event in the ECA instance triggers the first action (telemetry function) in the extended ECA instance, thereby sending corresponding telemetry data to the network management device.
  • the extended ECA model realizes the automatic association between network events in the network device and the telemetry function, so that the network device can automatically start the telemetry function and send telemetry data according to the network event that occurs.
  • FIG. 1 is a schematic diagram of a communication network structure according to an embodiment of the application
  • Fig. 2 is a flowchart of a data processing method according to an embodiment of the application
  • FIG. 3 is a schematic structural diagram of a network management device according to an embodiment of the application.
  • FIG. 4 is a schematic diagram of the hardware structure of a network management device according to an embodiment of the application.
  • FIG. 5 is a schematic diagram of the hardware structure of a network management device according to an embodiment of the application.
  • Fig. 6 is a schematic structural diagram of a network device according to an embodiment of the application.
  • FIG. 7 is a schematic diagram of the hardware structure of a network device according to an embodiment of the application.
  • FIG. 8 is a schematic diagram of the hardware structure of a network device according to an embodiment of the application.
  • Fig. 1 is a schematic diagram of a communication network structure according to an embodiment of the application.
  • the communication network includes network management equipment and network equipment.
  • the number of network devices is not limited.
  • the communication network shown in FIG. 1 includes network device A, network device B, and network device C.
  • the network management device communicates with the network device A, the network device B, and the network device C via communication links, respectively.
  • the network device may be any one of the network device A, the network device B, and the network device C.
  • the network management device may be regarded as a management device in the communication network, and the network device A, network device B, and network device C may be regarded as a managed device in the communication network.
  • the network management device may be an independent hardware device, such as a server or a controller; the network management device may also include multiple hardware devices, for example, the network management device includes a control device and a client device. Wherein, the control device communicates with the network device via a communication link, and the client device communicates with the control device via a wired link or a wireless link.
  • the network device may be an independent hardware device, such as a router or switch, and the network device may include multiple forwarding boards, each of which includes a physical port to communicate with other network devices, and each Each forwarding board may include a central processing unit (CPU).
  • the network device may also include multiple hardware devices.
  • the network device includes a router and multiple hosts, and the router communicates with the multiple hosts respectively.
  • the network management device sends the extended ECA instance to the network device (such as the network device A in FIG. 1).
  • the network management device may directly generate an extended ECA instance, and then send the extended ECA instance to the network device.
  • the network management device may first generate an extended ECA model, the network management device generates the corresponding extended ECA instance according to the extended ECA model, and then sends to the network device The extended ECA instance.
  • the extended ECA model can be implemented based on NETCONF, specifically, based on the YANG model.
  • the extended ECA model may include events, conditions, and actions.
  • the event represents a network event related to the network device.
  • the conditions indicate conditions that can trigger the occurrence of a network event.
  • the action means that the corresponding telemetry function is triggered when the event occurs. Therefore, the extended ECA model indicates that when the condition is met, the event is triggered, and the corresponding action (telemetry function) is triggered after the event occurs.
  • the extended ECA model is a universal model.
  • the network management device may generate the extended ECA instance according to the extended ECA model and specific telemetry indicators that need to be monitored. Therefore, the extended ECA instance is a specific monitoring instance generated according to the extended ECA model. For example, the network management device wants to monitor the CPU occupancy rate of the network device, and when the CPU occupancy rate is greater than a threshold value, the network device is required to send the network management device a CPU occupancy rate exceeding the threshold value.
  • the network management device may generate a first event according to the event part in the extended ECA model and specific events related to the CPU usage rate (for example, reporting the CPU usage rate to the network management device), and according to the conditions in the extended ECA model Part of the specific conditions related to the CPU occupancy rate (for example, the CPU occupancy rate is greater than the threshold) generates the first condition, and the specific actions related to the CPU occupancy rate (for example, sending CPU The telemetry data corresponding to the occupancy rate) generates the first action. Therefore, the extended ECA instance may include a first event, a first condition, and a first action. Wherein, the first event, first condition, and first action in the extended ECA instance are implementation forms of specific monitoring instances of events, conditions, and actions in the extended ECA model.
  • the network device receives the extended ECA instance sent by the network management device.
  • the extended ECA instance is implemented in an XML format.
  • the network device runs the extended ECA instance.
  • the network device determines that the first condition in the extended ECA instance is satisfied, the network device triggers the occurrence of the first event in the extended ECA instance.
  • the network device determines that the first event occurs, it triggers the corresponding first action in the extended ECA instance (that is, the telemetry function shown in FIG. 1).
  • the network device is triggering the telemetry function, and generates corresponding telemetry data according to the telemetry function.
  • the network device sends the telemetry data to the network management device.
  • the specific implementation manner please refer to the description in the subsequent method implementation manner.
  • the network management device generates and sends an extended ECA instance to the network device, and when the network device determines that the first condition in the extended ECA instance is satisfied, the network device triggers the extension
  • the occurrence of the first event in the ECA instance in the ECA instance triggers the first action (telemetry function) in the extended ECA instance, thereby sending corresponding telemetry data to the network management device.
  • the extended ECA model realizes the automatic association between network events in the network device and the telemetry function, so that the network device can automatically start the telemetry function and send telemetry data according to the network event that occurs.
  • Figure 1 shows the interaction process between the network management device and the network device A.
  • the interaction process between the network management device and the network device B and the interaction process between the network management device and the network device C can also be in accordance with the above Realization way to achieve.
  • the network device is used as the detected object for description. It should be understood that a part of the network device can also be used as the detected object in the foregoing implementation manner (for example, one or more forwarding boards included in the network device). Card, or router and/or host included in the network device).
  • Fig. 2 is a flowchart of a data processing method according to an embodiment of the application.
  • the method shown in FIG. 2 can be applied to the network structure shown in FIG. 1.
  • network management equipment and “network equipment” are used for description.
  • the "network equipment” can be network equipment A, network equipment B, and network equipment C in FIG. Any network device.
  • the first action refers to the telemetry function.
  • the method includes:
  • the network management device generates an extended ECA instance, where the extended ECA instance includes a first event, a first condition, and a first action, where the first action includes a first object identifier and a first indicator type, and the first object
  • the identifier indicates the first object to be detected
  • the first indicator type indicates the performance index of the first object to be detected
  • the extended ECA instance is used to instruct the network device managed by the network management device to follow the first event and
  • the first condition sends first detection data corresponding to the first indicator type and for the first object to be detected to the network management device, and the network device includes the first object to be detected.
  • the network management device may directly generate the extended ECA instance.
  • the extended ECA instance includes a first event, a first condition, and a first action.
  • the first event represents a network event related to the network device.
  • the first condition represents a condition that can trigger the occurrence of a network event.
  • the first action indicates that the corresponding telemetry function is triggered when the event occurs. Therefore, the extended ECA instance indicates that when the first condition is met, the first event is triggered to occur, and the corresponding first action (telemetry function) is triggered after the first event occurs.
  • Table 1 shows an example of a description of commonly used extended ECA instances.
  • Table 1 describes each extended ECA instance in the way of implementing functions.
  • multiple protocols or computer languages can be used to implement the extended ECA instance, for example, the XML mode is used to implement the above-mentioned each extended ECA instance.
  • the extended ECA instance 1 realizes the monitoring of the packet loss rate. Specifically, the network management device remotely detects that the network device executes the extended ECA instance 1. The network device monitors the packet loss rate of the first object to be detected, and when the packet loss rate is greater than a threshold value (first condition), triggers a report of the packet loss rate (first event) to the network management device. The network device determines that a first event occurs, and triggers a telemetry function that sends a packet loss rate exceeding a threshold (first action) to the network management device. Among them, the transmitted packet loss rate exceeding the threshold belongs to telemetry data.
  • the packet loss rate in the extended ECA instance 1 is the packet loss rate in the device, for example, the packet loss rate is the data of the egress port queue and the ingress port queue of the first object to be detected The difference in the number of packages.
  • the packet loss rate in the extended ECA instance 1 is the packet loss rate of the link between the devices.
  • the packet loss rate is the first object to be detected and the first object to be detected.
  • the packet loss rate of the link between the last-hop network devices of the object, where the first object to be detected serves as the receiving end of the traffic.
  • the network device includes the first object to be detected.
  • the first object to be detected may be the network device itself, or a component or device included in the network device.
  • the first object to be detected is a forwarding board in the network device, or the first object to be detected is a host included in the network device.
  • the extended ECA instance 2 realizes the monitoring of CPU usage.
  • the network management device remotely detects that the network device executes the extended ECA instance 2.
  • the network device monitors the CPU occupancy rate of the first object to be detected, and when the CPU occupancy rate is greater than the threshold value (first condition), it triggers to report the CPU occupancy rate to the network management device (first event).
  • the network device determines that a first event occurs, and triggers a telemetry function that sends a CPU occupancy rate exceeding a threshold (first action) to the network management device.
  • the CPU occupancy rate that is sent that exceeds the threshold belongs to telemetry data.
  • the network device may include multiple CPUs, for example, the network device includes multiple forwarding boards, and each forwarding board includes a CPU.
  • the CPU occupancy rate in the extended ECA instance 2 may be the occupancy rate of the central processing unit of the network device, or the occupancy rate of the CPU on the forwarding board included in the network device, or the occupancy rate of the CPU included in the network device.
  • the CPU occupancy rate in the host may be the occupancy rate of the central processing unit of the network device, or the occupancy rate of the CPU on the forwarding board included in the network device, or the occupancy rate of the CPU included in the network device.
  • the extended ECA instance 3 realizes the monitoring of the queue length.
  • the network management device remotely detects that the network device executes the extended ECA instance 3.
  • the network device monitors the queue length of the first object to be detected, and when the queue length is greater than the threshold value (first condition), triggers to report the queue length (first event) to the network management device.
  • the network device determines that the first event occurs, and triggers the telemetry function that sends the queue length exceeding the threshold (first action) to the network management device.
  • the queue length includes the length of the outgoing port queue or the length of the incoming port queue.
  • the extended ECA instance 4 realizes the monitoring of time delay. Specifically, the network management device remotely detects that the network device executes the extended ECA instance 4. The network device monitors the time delay of the first object to be detected, and the time delay is greater than the threshold value (first condition) to trigger the reporting of the time delay (first event) to the network management device. The network device determines that a first event occurs, and triggers a telemetry function that sends a time delay exceeding a threshold value (first action) to the network management device.
  • the delay in the extended ECA instance 4 is the link delay between devices, for example, the delay is the last one between the first object to be detected and the first object to be detected.
  • the delay in the extended ECA instance 4 is the processing delay in the device, for example, the delay is the delay from the ingress port queue of the first detection object to the egress port queue. .
  • the extended ECA instance 5 realizes the monitoring of jitter value. Specifically, the network management device remotely detects that the network device executes the extended ECA instance 5. The network device monitors the jitter value of the first object to be detected, and when the jitter value is greater than the threshold value (first condition), triggers to report the jitter value (first event) to the network management device. The network device determines that a first event occurs, and triggers a telemetry function that sends a jitter value exceeding a threshold (first action) to the network management device. Wherein, the jitter in the extended ECA instance 5 refers to the delay between the packets flowing through the first object to be detected. Jitter can be used to detect whether there is an interruption between multiple packets in the sequentially sent data stream.
  • the extended ECA instance 6 realizes the monitoring of bandwidth utilization. Specifically, the network management device remotely detects that the network device executes the extended ECA instance 6. The network device monitors the bandwidth utilization rate of the first object to be detected, and when the bandwidth utilization rate is less than the threshold value (the first condition), it is triggered to report the bandwidth utilization rate to the network management device (the first event). The network device determines that a first event occurs, and triggers a telemetry function that sends a bandwidth utilization rate (first action) below a threshold value to the network management device.
  • the bandwidth utilization rate in the extended ECA instance 5 refers to the ratio between the rate at which the outgoing port of the first object to be detected sends traffic and the rated physical bandwidth of the link connecting the outgoing port.
  • the network management device first obtains the extended ECA model before generating the extended ECA instance.
  • the extended ECA model may include events, conditions, and actions.
  • the network management device may automatically generate the extended ECA model, or may receive the extended ECA model from other devices.
  • the extended ECA instance may be generated according to the telemetry indicator that needs to be specifically monitored. For example, the network management device wishes to generate an extended ECA instance 2, so that the network management device can detect the CPU occupancy rate of the first object to be detected.
  • the network management device may add the relevant parameters of the first event in the extended ECA instance 2 to the event part of the extended ECA model according to the description for the extended ECA instance 2 in Table 1, and add the extended ECA instance 2
  • the relevant parameters of the first condition in the extended ECA model are added to the condition part of the extended ECA model, and the relevant parameters of the first action in the extended ECA instance 2 are added to the action part of the extended ECA model, thereby generating an extended ECA instance 2.
  • the first action in the extended ECA instance includes a first object identifier and a first indicator type.
  • the first object identifier indicates the first object to be detected.
  • the first object to be detected is the network device, and the first object identifier may specifically be the device identifier of the network device.
  • the first object to be detected is a forwarding board included in the network device, and the first object identifier may specifically be the device identifier of the network device and the forwarding board identifier, or the first Specifically, the object identifier may be the device identifier of the network device and the position identifier of the forwarding board in the network device. Multiple first object identifiers may be included in the same extended ECA instance.
  • the first action not only includes the first object identifier and the first indicator type mentioned above, the first action also includes a second object identifier and a second indicator type, and the second object identifier indicates the second
  • the second indicator type indicates a performance indicator of the second object to be detected.
  • the extended ECA instance 2 includes the device identification of the network device A and the device identification of the network device B, and the first indicator type and the second indicator type are both CPU occupancy rates. In this way, the network management device can monitor the CPU occupancy rates of the network device A and the network device B through the extended ECA instance 2.
  • the first index type indicates the performance index of the first object to be detected.
  • the network management device generates an extended ECA instance 1, the value of the first indicator type is 01, and 01 represents the packet loss rate.
  • the network management device generates an extended ECA instance 2, and the value of the first indicator type is 02, and 02 represents the CPU occupancy rate.
  • the extended ECA instance is used to instruct the network device managed by the network management device to send to the network management device according to the first event and the first condition, corresponding to the first indicator type, for the first The first detection data of the object to be detected.
  • the extended ECA instance may instruct the network device to execute the extended ECA instance, thereby triggering the telemetry function in the extended ECA instance to generate corresponding telemetry data. It should be understood that the implementation manner of the present application exemplarily uses telemetry data as the first detection data.
  • the first action further includes a group identifier, the group identifier indicating a service type associated with the extended ECA instance.
  • the group identification can be used to monitor the flow of the specific service.
  • the network device A includes a three-layer virtual private network (virtual private network, VPN) service and a multi-protocol label switch (multi-protocol label switch, MPLS) service.
  • the network management device hopes to monitor the packet loss rate of the data traffic of the related MPLS service in the network device A. Therefore, the extended ECA instance 1 may include a group identifier, and the value of the group identifier is 01, indicating that the extended ECA instance 1 is used to monitor the packet loss rate of the data traffic of the MPLS service.
  • the first action further includes an enable flag, and the enable flag is used to enable the first action.
  • the network device runs the telemetry function, it needs to run a protocol related to the telemetry function.
  • the monitoring of the network equipment by the network management equipment may be performed periodically. For example, the network management device monitors the network device every 1 hour, and the monitoring period is 5 minutes. In this way, if the network device keeps the telemetry function on all the time, it will inevitably increase the power consumption and CPU usage of the network device. Therefore, during the operation of the network device, the telemetry function can be maintained in the off state, and when the network device receives the extended ECA instance, it determines whether the first action includes an enable flag. When the network device determines that the first action includes an enable flag, the network device enables the function of sending telemetry data.
  • the first action further includes a first operation type
  • the first operation type indicates an attribute of the first detection data.
  • the attribute of the first detection data may include at least one of the following: an average value, a maximum value, a minimum value, and a variance value.
  • the network management device wants to monitor the average value of the CPU usage of the network device.
  • the network management device may add a first operation type field to the extended ECA instance 2, and set the value of the first operation type field to an average value. In the process of running the extended ECA instance 2, the network device will monitor all CPU occupancy rates greater than the threshold within a predetermined period, take the average value, and then send the average value to the network management device.
  • the first action further includes a first indicator value type, and the first indicator value type indicates a data type of the first detection data.
  • the first indicator value type indicates the value type of the telemetry data when the network device reports the telemetry data, for example, unit 32 represents a 32-bit unsigned integer.
  • the first action further includes a first object identification list.
  • the first object identification list includes a plurality of object identifications, for example, the first object identification list includes a first object identification and a second object identification.
  • the following takes a specific implementation as an example to illustrate the actions of the extended ECA model and the implementation of the first action of the extended ECA model.
  • the above command line shows the specific implementation of the actions of the extended ECA model in the implementation of this application.
  • rw telemetry means that the action is a telemetry function.
  • Rwenable indicates the enable flag in the foregoing embodiment. When the value is “enable”, it instructs the network device to start the function of sending telemetry data to the network management device.
  • Rw group-id represents the group identifier in the foregoing embodiment.
  • Rw telemtry-attributes means that the command line after this line is a description of the attribute function.
  • “Rw node-telemetry-attributes*[node-selector]" represents the first object identification list in the foregoing embodiment.
  • Rw node-selector represents the first object identifier or the second object identifier in the foregoing embodiment.
  • Rw metric-type indicates the first indicator type or the second indicator type in the foregoing embodiment.
  • Rw operation-type indicates the first operation type in the foregoing embodiment.
  • Ro metric-value indicates the first indicator value type in the foregoing embodiment.
  • the network management device can generate an extended ECA instance according to the extended ECA model. Specifically, the network management device adds specific related parameters to the extended ECA model to generate a corresponding extended ECA instance. For example, for the specific implementation of the action part of the aforementioned extended ECA model, the network management device wishes to generate an extended ECA instance 2 in order to monitor the CPU occupancy rate of the network device A. Then, the network management equipment adds the identity of network device A in "rw node-telemetry-attributes*[node-selector]", adds the identity of network device A in "rw node-selector", and adds the identity of network device A in "rw metric-type" Add a flag indicating the CPU usage.
  • the network management device also sets the specific values of the parameters of the above-mentioned action part according to the monitoring requirements, thereby forming the first action part in the extended ECA instance 2.
  • the network management device should also correspondingly generate the first event and the first condition part of the extended ECA instance 2 in a similar manner, which will not be repeated here.
  • the extended ECA instance 2 is applied to the monitoring of the CPU usage of the network device A and the network device B. Then, the network management device adds the identity of network device A and the identity of network device B in "rw node-telemetry-attributes*[node-selector]".
  • the generated extended ECA instance 2 includes two sets of parameters, for example, “rw node-selector-1 ", “rw metric-type-1”, “rw operation-type-1” and “ro metric-value-1” are the parameters of related network device A, “rw node-selector-2”, “rw metric-type -1”, “rw operation-type-2” and “ro metric-value-2” are the parameters of related network device B.
  • the first indicator type may indicate the performance indicators that can obtain corresponding data through measurement means, such as packet loss rate, CPU occupancy rate, queue length, delay, jitter value, and bandwidth utilization. Rate etc.
  • the first indicator type may also indicate a performance indicator that does not require corresponding data to be obtained through measurement means, for example, configuration information of the first object to be detected.
  • the network management device sends a first message to the network device, where the first message includes the extended ECA instance.
  • the network device receives the first message sent by the network management device.
  • the network management device is generating the extended ECA instance, and sends a first message to the network device, where the first message includes the extended ECA instance.
  • the message transferred between the network management device and the network device may be implemented based on NETCONF or RESTCONF, that is, the first message includes a NETCONF message or a RESTCONF message.
  • the network management device before the network management device sends the first message to the network device, the network management device establishes a NETCONF session or a RESTCONF session between the network management device and the network device.
  • the network management device establishes a NETCONF session between the network management device and the network device.
  • the network management device sends a NETCONF session request message to the network device.
  • the network device determines that it can establish a NETCONF session with the network management device.
  • the network device sends a NETCONF session confirmation message to the network management device.
  • the network management device After receiving the NETCONF session confirmation message, the network management device determines that the establishment of the NETCONF session is completed.
  • the process of establishing a RESTCONF session is similar to the process of establishing a NETCONF session, and will not be repeated here.
  • the network device receives the first message sent by the network management device. Then, the network device obtains the extended ECA instance in the first message.
  • the network device determines that the first event has occurred, the network device sends a second message to the network management device, where the second message includes the first detection data, and the first detection data is related to The detection data corresponding to the first indicator type for the first object to be detected.
  • S106 The network management device receives the second message sent by the network device.
  • the extended ECA instance sent by the network management device to the network device is extended ECA instance 2
  • the to-be-detected object to be monitored by the network management device is network device A.
  • Network device A runs extended ECA instance 2.
  • the network device A detects the CPU occupancy rate of the network device A according to the first condition part in the extended ECA instance 2.
  • the network device A compares the value of the detected CPU occupancy rate with the threshold value.
  • the network device A determines that the value of the detected CPU occupancy rate is greater than the threshold value, and the network device A determines that the first condition in the extended ECA instance 2 is satisfied.
  • the network device A triggers the occurrence of the first event (reporting the CPU occupancy rate to the network management device) in the extended ECA instance 2.
  • the network device A determines that the first event in the extended ECA instance 2 occurs, the network device A executes the first action in the extended ECA instance 2.
  • the network device A finds that the enable flag included in the first action in the extended ECA instance 2 is in the enable state, and enables the function of sending telemetry data to the network management device.
  • the network device A determines the final first detection data (the value of the CPU occupancy rate), that is, the telemetry data, according to the parameters in each field included in the first action in the ECA instance 2.
  • the network device After determining the first detection data, the network device generates the second message.
  • the second message includes a NETCONF message or a RESTCONF message.
  • the following takes a specific implementation manner as an example to illustrate the implementation manner of the second message.
  • telemetry-trigger indicates that the second message is triggered by the telemetry function.
  • Ro event-name represents the first event identifier associated with the second message, which corresponds to the first event identifier in the extended ECA instance executed by the network device.
  • Ro group-id represents the group ID corresponding to the sent telemetry data, which corresponds to the group ID in the extended ECA instance executed by the network device.
  • Ro node-telemetry-attributes*[node-selector] represents the first object identification list corresponding to the telemetry data sent, which is the same as the "re node-telemetry-attributes*[ node-selector]" corresponds to.
  • the "ro node-selector” represents the first object identifier or the second object identifier in the foregoing embodiment, which corresponds to the "re node-selector” in the extended ECA instance executed by the network device.
  • the "ro metric-type” indicates the first indicator type or the second indicator type in the foregoing embodiment, which corresponds to the "rw metric-type” in the extended ECA instance executed by the network device.
  • the "ro metric-value" includes the first detection data.
  • multiple second messages may be generated and sent to the network management device respectively; or, a second message may be generated to carry multiple The detection data of an object to be detected.
  • a second message may be generated to carry multiple The detection data of an object to be detected.
  • the network device After generating the second message, the network device sends the second message to the network management device. Correspondingly, the network management device receives the second message sent by the network device.
  • the network device sends the second message to the network management device according to a predetermined cycle. For example, the network device sends the second message to the network management device every 5 minutes.
  • the network device may send the second message according to the query request of the network management device.
  • the network management device sends a request message to the network device, and the request message is used to request the network device to send the second message.
  • the request message may include a NETCONF message or a RESTCONF message.
  • the network device sends the second message to the network management device according to the request message.
  • the network management device sends the request message to the network device according to a predetermined period (or a preset frequency). For example, the network management device sends a request message to the network device every 5 minutes.
  • the first condition is a condition that the first object to be detected meets the performance index indicated by the first index type.
  • extended ECA instance 2 in Table 1.
  • the value of the first indicator type is 02, which indicates that the performance indicator indicated by the first indicator type is the CPU occupancy rate.
  • the first condition in the extended ECA instance 2 is related to the CPU occupancy rate, that is, the set condition is the condition related to the CPU occupancy rate. It can be seen from the extended ECA instance 7 that the performance index (CPU occupancy rate) set in the first condition is the same as the performance index (CPU occupancy rate) set in the first action.
  • the first condition is that the first object to be detected satisfies a condition for a performance index indicated by a third index type, wherein the third index type is the same as the first index type Are not the same.
  • the first event of the extended ECA instance 7 (not shown in Table 1) is "reporting ARP statistics to the network management device" (where ARP refers to the address resolution protocol, Address Resolution Protocol), and the first condition is "monitoring CPU occupancy rate, and the CPU occupancy rate is greater than the threshold", the first action is "send the number of ARP packets received by the object to be detected in a predetermined period".
  • the specific implementation of "sending the number of ARP packets received by the object to be detected in a predetermined period” may be: when the first event occurs, the predetermined period starts to count, and the network device detects that the object to be detected receives within the predetermined period. The number of received ARP packets until the end of the predetermined period, and then the counted number of ARP packets are sent to the network management device.
  • the extended ECA instance 7 can be applied to ARP packet attack detection. It can be seen from the extended ECA instance 7 that the performance index (CPU occupancy rate) set in the first condition is different from the performance index (the number of ARP packets) set in the first action.
  • the network management device generates and sends an extended ECA instance to the network device, and when the network device determines that the first condition in the extended ECA instance is satisfied, the network device triggers the extension The occurrence of the first event in the ECA instance in the ECA instance triggers the first action (telemetry function) in the extended ECA instance, thereby sending corresponding telemetry data to the network management device.
  • the extended ECA model realizes the automatic association between network events in the network device and the telemetry function, so that the network device can automatically start the telemetry function and send telemetry data according to the network event that occurs.
  • FIG. 3 is a schematic structural diagram of a network management device 1000 according to an embodiment of the application.
  • the network management device 1000 shown in FIG. 3 can execute the corresponding steps performed by the network management device in the method of the foregoing embodiment.
  • the network management device is deployed in a communication network, and the communication network also includes a network device.
  • the network management device 1000 includes a receiving unit 1002, a processing unit 1004, and a sending unit 1006.
  • the processing unit 1004 is configured to generate an ECA instance, the extended ECA instance includes a first event, a first condition, and a first action, the first action includes a first object identifier and a first indicator type, and the first An object identifier indicates a first object to be detected, the first indicator type indicates a performance indicator of the first object to be detected, and the extended ECA instance is used to instruct the network device managed by the network management device according to the first The event and the first condition send first detection data corresponding to the first indicator type and corresponding to the first object to be detected to the network management device, where the network device includes the first object to be detected;
  • the sending unit 1006 is configured to send a first message to the network device, where the first message includes the extended ECA instance;
  • the receiving unit 1002 is configured to receive a second message sent by the network device, where the second message includes the first detection data.
  • the first condition is a condition that the first object to be detected meets the performance index indicated by the first index type.
  • the first condition is a condition that the first object to be detected meets a performance indicator indicated by a third indicator type, wherein the third indicator type is different from the first indicator type.
  • the sending unit 1006 is further configured to send a request message to the network device, where the request message is used to request the network device Send the second message.
  • the sending unit 1006 is specifically configured to send the request message to the network device according to a preset frequency.
  • the processing unit 1004 before the processing unit 1004 generates an ECA instance, the processing unit 1004 is further configured to obtain an extended ECA model, and the extended ECA model instructs the processing unit 1004 according to the extended ECA model and what needs to be monitored The event generates the extended ECA instance.
  • the first action further includes a second object identifier and a second indicator type
  • the second object identifier indicates a second object to be detected
  • the second indicator type indicates the performance of the second object to be detected
  • the extended ECA instance is also used to instruct the network device to send the network management device corresponding to the second indicator type for the second standby according to the first event and the first condition.
  • the second detection data of the detection object the network device includes the second object to be detected; the second message also includes the second detection data.
  • the first action further includes a group identifier, the group identifier indicating a service type associated with the extended ECA instance.
  • the first action further includes an enable flag, and the enable flag is used to enable the first action.
  • the first action further includes a first operation type and/or a first index value type, the first operation type indicates an attribute of the first detection data, and the first index value type indicates the The data type of the first detection data.
  • the processing unit 1004 is further configured to establish a network configuration protocol NETCONF session or a RESTCONF session between the network management device and the network device .
  • the network management device shown in FIG. 3 can execute the corresponding steps performed by the network management device in the method of the foregoing embodiment.
  • the network management device sends an extended ECA instance to the network device, and the action part included in the extended ECA instance can trigger the telemetry function of the network device. Therefore, the network device can trigger the telemetry function according to the event part included in the extended ECA instance, and send corresponding telemetry data to the network management device.
  • the extended ECA model automatic correlation between network events and telemetry is realized.
  • FIG. 4 is a schematic diagram of the hardware structure of a network management device 1100 according to an embodiment of the application.
  • the network management device device 1100 shown in FIG. 4 can execute the corresponding steps performed by the network management device device in the method of the foregoing embodiment.
  • the network management equipment 1100 includes a processor 1101, a memory 1102, an interface 1103, and a bus 1104.
  • the interface 1103 may be implemented in a wireless or wired manner, and specifically may be a network card.
  • the aforementioned processor 1101, memory 1102, and interface 1103 are connected through a bus 1104.
  • the interface 1103 may specifically include a transmitter and a receiver, which are used to send and receive information between the network management device device and the network device in the foregoing embodiment.
  • the interface 1103 is used to support receiving the second message sent by the network device, or used to support the first message sent.
  • the interface 1103 is used to support the processes S102 and S106 in FIG. 2.
  • the processor 1101 is configured to execute the processing performed by the network management device in the foregoing embodiment.
  • the processor 1101 is used to generate an extended ECA instance; and/or used in other processes of the technology described herein.
  • the processor 1101 is configured to support the process S101 in FIG. 2.
  • the memory 1102 includes an operating system 11021 and an application program 11022 for storing programs, codes or instructions.
  • the memory 1102 may include a read-only memory (English: Read-only Memory, abbreviation: ROM) and a random access memory (English: Random Access Memory, abbreviation: RAM).
  • ROM includes a basic input/output system (English: Basic Input/Output System, abbreviation: BIOS) or an embedded system;
  • BIOS Basic Input/Output System
  • the RAM includes an application program and an operating system.
  • FIG. 4 only shows a simplified design of the network management device 1100.
  • the network management equipment can contain any number of interfaces, processors or memories.
  • FIG. 5 is a schematic diagram of the hardware structure of another network management device 1200 according to an embodiment of the application.
  • the network management device 1200 shown in FIG. 5 can execute the corresponding steps performed by the network management device in the method of the foregoing embodiment.
  • the network management device 1200 includes: a main control board 1210, an interface board 1230, a switching network board 1220, and an interface board 1240.
  • the main control board 1210, the interface boards 1230 and 1240, and the switching network board 1220 are connected to the system backplane through the system bus to achieve intercommunication.
  • the main control board 1210 is used to complete functions such as system management, equipment maintenance, and protocol processing.
  • the switching network board 1220 is used to complete data exchange between various interface boards (interface boards are also called line cards or service boards).
  • the interface boards 1230 and 1240 are used to provide various service interfaces (for example, POS interface, GE interface, ATM interface, etc.), and implement data packet forwarding.
  • the interface board 1230 may include a central processing unit 1231, a forwarding entry memory 1234, a physical interface card 1233, and a network processor 1232.
  • the central processing unit 1231 is used to control and manage the interface board and communicate with the central processing unit on the main control board.
  • the forwarding entry storage 1234 is used to store forwarding entries.
  • the physical interface card 1233 is used to complete the reception and transmission of traffic.
  • the network storage 1232 is used to control the receiving and sending traffic of the physical interface card 1233 according to the forwarding entry.
  • the physical interface card 1233 is configured to receive the second message sent by the network device.
  • the physical interface card 1233 is also used to send a first message to the network device.
  • the physical interface card 1233 After receiving the second message, the physical interface card 1233 sends the second message to the central processing unit 1211 via the central processing unit 1231, and the central processing unit 1211 processes the second message.
  • the central processing unit 1211 is also used to generate extended ECA instances.
  • the central processing unit 1231 is also used to control the network storage 1232 to obtain forwarding entries in the forwarding entry storage 1234, and the central processing unit 1231 is also used to control the network storage 1232 to send a first message to the network device via the physical interface card 1233 .
  • the operations on the interface board 1240 in the embodiment of the present invention are consistent with the operations on the interface board 1230, and will not be repeated for the sake of brevity.
  • the network management device 1200 of this embodiment may correspond to the functions and/or various steps implemented in the foregoing method embodiments, and details are not described herein again.
  • main control boards there may be one or more main control boards, and when there are more than one, it may include a main main control board and a standby main control board.
  • the switching network board may not exist, or there may be one or more. When there are more than one, the load sharing and redundant backup can be realized together. Under the centralized forwarding architecture, the network management equipment does not need to switch the network board, and the interface board undertakes the processing function of the business data of the entire system.
  • the network management equipment can have at least one switching network board, and data exchange between multiple interface boards can be realized through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network management equipment with a distributed architecture are greater than those with a centralized architecture.
  • the specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.
  • an embodiment of the present application provides a computer storage medium for storing computer software instructions used for the above-mentioned network management device, which includes a program designed for executing the above-mentioned method embodiment.
  • FIG. 6 is a schematic structural diagram of a network device 2000 according to an embodiment of the application.
  • the network device 2000 shown in FIG. 6 can execute the corresponding steps performed by the network device in the method of the foregoing embodiment.
  • the network device is deployed in a communication network, and the communication network also includes a network management device.
  • the network device 2000 includes a receiving unit 2002, a processing unit 2004 and a sending unit 2006.
  • the receiving unit 2002 is configured to receive a first message sent by a network management device, where the first message includes an extended ECA instance, and the extended ECA instance includes a first event, a first condition, and a first action.
  • An action includes a first object identifier and a first indicator type, the first object identifier indicates a first object to be detected, the first indicator type indicates a performance indicator of the first object to be detected, and the network device includes all The first object to be detected;
  • the processing unit 2004 is configured to determine that the first event occurs when it is determined that the first condition is satisfied;
  • the sending unit 2006 is configured to send a second message to the network management device when the processing unit 2004 determines that the first event has occurred.
  • the second message includes first detection data, and the first detection data is The detection data corresponding to the first indicator type for the first object to be detected.
  • the first condition is a condition that the first object to be detected meets the performance index indicated by the first index type.
  • the first condition is a condition that the first object to be detected meets a performance indicator indicated by a third indicator type, wherein the third indicator type is different from the first indicator type.
  • the receiving unit 2002 is further configured to receive a request message sent by the network management device, and the request message is used to request the network device Send the second message.
  • the first action further includes a second object identifier and a second indicator type
  • the second object identifier indicates a second object to be detected
  • the second indicator type indicates the performance of the second object to be detected
  • the network device includes the second object to be detected
  • the second message further includes the second detection data
  • the second detection data corresponds to the second indicator type and is directed to the first 2. The detection data of the object to be detected.
  • the first action further includes a group identifier, the group identifier indicating a service type associated with the extended ECA instance, and the first detection data is detection data associated with the service type.
  • the first action further includes an enable flag, and the enable flag is used to enable the first action.
  • the processing unit 2004 determines that the first condition is satisfied, the processing unit 2004 It is also used to enable the sending function of running the detection data associated with the first action according to the enable flag.
  • the second message further includes a group identifier, and the group identifier indicates a service type associated with the extended ECA instance.
  • the second message further includes an event identifier, and the event identifier indicates the first event.
  • the second message further includes the first object identifier and the first indicator type.
  • the network device shown in FIG. 6 can execute the corresponding steps performed by the network device in the method of the foregoing embodiment.
  • the network management device sends an extended ECA instance to the network device, and the action part included in the extended ECA instance can trigger the telemetry function of the network device. Therefore, the network device can trigger the telemetry function according to the event part included in the extended ECA instance, and send corresponding telemetry data to the network management device.
  • the extended ECA model automatic correlation between network events and telemetry is realized.
  • FIG. 7 is a schematic diagram of the hardware structure of the network device 2100 according to an embodiment of the application.
  • the network device 2100 shown in FIG. 7 can execute the corresponding steps performed by the network device in the method of the foregoing embodiment.
  • the network device 2100 includes a processor 2101, a memory 2102, an interface 2103, and a bus 2104.
  • the interface 2103 may be implemented in a wireless or wired manner, and specifically may be a network card.
  • the aforementioned processor 2101, memory 2102, and interface 2103 are connected through a bus 2104.
  • the interface 2103 may specifically include a transmitter and a receiver, which are used to send and receive information or data between the network device and the network management device in the foregoing embodiment.
  • the interface 2103 is used to support sending a second message to the network management device; for another example, the interface 2103 is used to support receiving a first message sent by the network management device.
  • the interface 2103 is used to support the processes S103 and S105 in FIG. 2.
  • the processor 2101 is configured to execute the processing performed by the network device in the foregoing embodiment.
  • the processor 2101 is used to generate a second message, used to execute the extended ECA instance; and/or used in other processes of the technology described herein.
  • the processor 2101 is configured to support the process S104 in FIG. 2.
  • the memory 2102 includes an operating system 21021 and an application program 21022, which are used to store programs, codes, or instructions. When the processor or hardware device executes these programs, codes, or instructions, the processing process involving the network device in the method embodiment can be completed.
  • the memory 2102 may include a read-only memory (English: Read-only Memory, abbreviation: ROM) and a random access memory (English: Random Access Memory, abbreviation: RAM).
  • ROM includes a basic input/output system (English: Basic Input/Output System, abbreviation: BIOS) or an embedded system
  • the RAM includes an application program and an operating system.
  • the system is booted by the BIOS solidified in the ROM or the bootloader in the embedded system to guide the network device 2100 into a normal operating state.
  • the application program and the operating system run in the RAM, thereby completing the processing procedure involving the network device in the method embodiment.
  • FIG. 7 only shows a simplified design of the network device 2100.
  • a network device can include any number of interfaces, processors or memories.
  • FIG. 8 is a schematic diagram of the hardware structure of another network device 2200 according to an embodiment of the application.
  • the network device 2200 shown in FIG. 8 can execute the corresponding steps performed by the network device in the method of the foregoing embodiment.
  • the network device 2200 includes: a main control board 2210, an interface board 2230, a switching network board 2220, and an interface board 2240.
  • the main control board 2210, the interface boards 2230 and 2240, and the switching network board 2220 are connected to the system backplane through the system bus to achieve intercommunication.
  • the main control board 2210 is used to complete functions such as system management, equipment maintenance, and protocol processing.
  • the switching network board 2220 is used to complete data exchange between various interface boards (interface boards are also called line cards or service boards).
  • the interface boards 2230 and 2240 are used to provide various service interfaces (for example, POS interface, GE interface, ATM interface, etc.), and implement data packet forwarding.
  • the interface board 2230 may include a central processing unit 2231, a forwarding entry memory 2234, a physical interface card 2233, and a network processor 2232.
  • the central processing unit 2231 is used to control and manage the interface board and communicate with the central processing unit on the main control board.
  • the forwarding entry storage 2234 is used to store forwarding entries.
  • the physical interface card 2233 is used to complete the reception and transmission of traffic.
  • the network storage 2232 is used for controlling the receiving and sending traffic of the physical interface card 2233 according to the forwarding entry.
  • the physical interface card 2233 is used to send the second message to the network management device.
  • the physical interface card 2233 is also used to receive the first message sent by the network management network device.
  • the physical interface card 2233 After receiving the first message sent by the network management device, the physical interface card 2233 sends the first message to the central processing unit 2211 via the central processing unit 2231, and the central processing unit 2211 processes the first message.
  • the central processing unit 2211 is used to generate the second message and execute the extended ECA instance.
  • the central processing unit 2231 is also used to control the network storage 2232 to obtain forwarding entries in the forwarding entry storage 2234, and the central processing unit 2231 is also used to control the network storage 2232 to receive and send traffic via the physical interface card 2233.
  • main control boards there may be one or more main control boards, and when there are more than one, it may include a main main control board and a standby main control board.
  • the switching network board may not exist, or there may be one or more. When there are more than one, the load sharing and redundant backup can be realized together. Under the centralized forwarding architecture, the network equipment does not need to switch the network board, and the interface board undertakes the processing function of the business data of the entire system.
  • the network device can have at least one switching network board, and data exchange between multiple interface boards is realized through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network equipment with a distributed architecture are greater than those with a centralized architecture.
  • the specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.
  • an embodiment of the present application provides a computer storage medium for storing computer software instructions used for the above-mentioned network device, which includes a program designed for executing the above-mentioned method embodiment.
  • the embodiment of the present application also includes a network system, the network system includes a network management device and a network device, the network management device is the network management device in the foregoing FIG. 3 or FIG. 4 or FIG. 5, and the network device is the foregoing FIG. 6 or FIG.
  • the network device in Figure 7 or Figure 8.
  • the steps of the method or algorithm described in combination with the disclosure of this application can be implemented in a hardware manner, or can be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage known in the art Medium.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in the user equipment.
  • the processor and the storage medium may also exist as discrete components in the user equipment.
  • the functions described in this application may be implemented by hardware or a combination of hardware and software.
  • the software can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Abstract

一种数据处理方法、设备及系统，所述方法包括，网管设备生成扩展的ECA实例，扩展的ECA实例包括第一事件、第一条件和第一动作，第一动作包括第一对象标识和第一指标类型，第一对象标识指示第一待检测对象，第一指标类型指示第一待检测对象的性能指标，扩展的ECA实例用于指示网管设备管理的网络设备根据第一事件和第一条件向网管设备发送第一检测数据，所述网络设备包括所述第一待检测对象。然后，网管设备向网络设备发送第一消息，所述第一消息包括扩展的ECA实例。并且，网管设备接收网络设备发送的第二消息，第二消息包括第一检测数据。从而，基于扩展的ECA模型，实现了网络事件和telemetry的自动关联。

Description

一种数据处理方法、设备及系统
本申请要求于2019年10月16日提交的申请号为201910984111.3、发明名称为“一种数据处理方法、设备及系统”的中国专利申请的优先权和于2019年11月1日提交的申请号为201911061787.1、发明名称为“一种数据处理方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种数据处理方法、设备及系统。
背景技术
网络配置协议(network configuration protocol，NETCONF)是一种基于可扩展标记语言extensible markup language，XML)的网络管理协议，它提供了一种可编程的、对网络设备进行配置和管理的方法。用户可以通过该协议设置参数、获取参数值、获取统计信息等。NETCONF报文使用XML格式，具有强大的过滤能力，而且每一个数据项都有一个固定的元素名称和位置，这使得同一厂商的不同设备具有相同的访问方式和结果呈现方式，不同厂商之间的设备也可以经过映射XML得到相同的效果，这使得它在第三方软件的开发上非常便利，很容易开发出在混合不同厂商、不同设备的环境下的特殊定制的网管软件。在这样的网管软件的协助下，使用NETCONF功能会使网络设备的配置管理工作，变得更简单更高效。
YANG(Yet Another Next Generation)是针对NETCONF访问的数据建模语言，NETCONF用YANG对各种操作、数据、以及通知进行建模，具有良好的可读性和可扩展性。设备和客户端都可以使用YANG进行建模。设备侧提供了YANG模型后，客户端可依据工具自动生成对应的访问模型代码，以节省开发工作量。
Restconf是一种基于超文本传输协议(hypertext transfer protocol，HTTP)的协议，该协议通过NETCONF中定义的数据存储概念来配置YANG中的数据。
遥测(telemetry)技术是一项远程的从物理网络设备或虚拟网络设备上高速采集数据的技术。通过push模式，提供了更实时更高速的数据采集功能。同时提高了采集过程中的网络设备和网络的利用率。
事件-条件-动作(event-condition-action，ECA)模型可以对通用策略进行建模，允许对设备/控制器中某一类参数进行监控，当触发条件满足时，事件发生。在实际网络场景中，ECA模型中的动作部分只支持对运行ECA模型的网络设备进行重新配置或者记录相关时间的触发。
发明内容
有鉴于此，本申请实施例提供了一种数据处理方法、设备及系统，网管设备向网络设备发送扩展的ECA实例，所述扩展的ECA实例中包括的动作部分可以触发网络设备的telemetry功能。从而，所述网络设备可以根据所述扩展的ECA实例中包括的事件部分触发telemetry功能，向所述网管设备发送相对应的telemetry数据。从而，基于扩展的ECA模型，实现了网络事件和telemetry的自动关联。
本申请实施例提供的技术方案如下。
第一方面，提供了一种数据处理方法，所述方法包括，网管设备生成扩展的ECA实例，所述扩展的ECA实例包括第一事件、第一条件和第一动作，所述第一动作包括第一对象标识和第一指标类型，所述第一对象标识指示第一待检测对象，所述第一指 标类型指示所述第一待检测对象的性能指标，所述扩展的ECA实例用于指示所述网管设备管理的网络设备根据所述第一事件和所述第一条件向所述网管设备发送第一检测数据，所述网络设备包括所述第一待检测对象。然后，所述网管设备向所述网络设备发送第一消息，所述第一消息包括所述扩展的ECA实例。并且，所述网管设备接收所述网络设备发送的第二消息，所述第二消息包括所述第一检测数据。
基于实施例提供的方案，所述网络设备可以根据所述扩展的ECA实例中包括的事件部分触发telemetry功能，向所述网管设备发送相对应的telemetry数据。从而，基于扩展的ECA模型，实现了网络事件和telemetry的自动关联。
在第一方面的一种可能的实现方式中，在所述网管设备接收所述网络设备发送的第二消息之前，所述方法还包括：所述网管设备向所述网络设备发送请求消息，所述请求消息用于请求所述网络设备发送所述第二消息。
在第一方面的又一种可能的实现方式中，所述网管设备向所述网络设备发送请求消息，包括：所述网管设备按照预设频率向所述网络设备发送所述请求消息。
在第一方面的再一种可能的实现方式中，在网管设备生成扩展的ECA实例之前，所述方法还包括：所述网管设备获取扩展的ECA模型，所述扩展的ECA模型指示所述网管设备根据所述扩展的ECA模型和需要监控的事件生成所述扩展的ECA实例。
可选的，所述第一动作还包括第二对象标识和第二指标类型，所述第二对象标识指示第二待检测对象，所述第二指标类型指示所述第二待检测对象的性能指标，所述扩展的ECA实例还用于指示所述网络设备根据所述第一事件和所述第一条件向所述网管设备发送与所述第二指标类型对应的、针对所述第二待检测对象的第二检测数据，所述网络设备包括所述第二待检测对象；所述第二消息还包括所述第二检测数据。
可选的，所述第一动作还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型。
可选的，所述第一动作还包括使能标志，所述使能标志用于使能所述第一动作。
可选的，所述第一动作还包括第一操作类型和/或第一指标值类型，所述第一操作类型指示所述第一检测数据的属性，所述第一指标值类型指示所述第一检测数据的数据类型。
在第一方面的再一种可能的实现方式中，在所述网管设备向所述网络设备发送第一消息之前，所述方法还包括：所述网管设备建立所述网管设备与所述网络设备之间的网络配置协议NETCONF会话或RESTCONF会话。
第二方面，提供了一种数据处理方法，所述方法包括，网络设备接收网管设备发送的第一消息，所述第一消息包括扩展的ECA实例，所述扩展的ECA实例包括第一事件、第一条件和第一动作，所述第一动作包括第一对象标识和第一指标类型，所述第一对象标识指示第一待检测对象，所述第一指标类型指示所述第一待检测对象的性能指标，所述网络设备包括所述第一待检测对象。当所述网络设备确定所述第一条件成立，所述网络设备确定所述第一事件发生。当所述网络设备确定所述第一事件发生，所述网络设备向所述网管设备发送第二消息，所述第二消息包括第一检测数据。
基于实施例提供的方案，所述网络设备可以根据所述扩展的ECA实例中包括的事件部分触发telemetry功能，向所述网管设备发送相对应的telemetry数据。从而，基于扩展的ECA模型，实现了网络事件和telemetry的自动关联。
在第二方面的一种可能的实现方式中，在所述网络设备向所述网管设备发送第二消息之前，所述方法还包括：所述网络设备接收所述网管设备发送的请求消息，所述请求消息用于请求所述网络设备发送所述第二消息。
可选的，所述第一动作还包括第二对象标识和第二指标类型，所述第二对象标识指示第二待检测对象，所述第二指标类型指示所述第二待检测对象的性能指标，所述网络设备包括所述第二待检测对象，所述第二消息还包括所述第二检测数据，所述第二检测数据是与所述第二指标类型对应的、针对所述第二待检测对象的检测数据。
可选的，所述第一动作还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型，所述第一检测数据是与所述业务类型相关联的检测数据。
在第二方面的又一种可能的实现方式中，所述第一动作还包括使能标志，所述使能标志用于使能所述第一动作，在所述网络设备确定所述第一条件成立之前，所述方法还包括：所述网络设备根据所述使能标志开启运行所述第一动作关联的所述检测数据的发送功能。
可选的，所述第二消息还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型。
可选的，所述第二消息还包括事件标识，所述事件标识指示所述第一事件。
可选的，所述第二消息还包括所述第一对象标识和所述第一指标类型。
在上述第一方面或第二方面中，可选的，所述第一条件是所述第一待检测对象满足所述第一指标类型指示的性能指标的条件。
在上述第一方面或第二方面中，可选的，所述第一条件是所述第一待检测对象满足第三指标类型指示的性能指标的条件，其中，所述第三指标类型与所述第一指标类型不相同。
第三方面，提供了一种网管设备，所述网管设备具有实现上述方法中网管设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，网管设备的结构中包括处理器和接口，所述处理器被配置为支持网管设备执行上述方法中相应的功能。所述接口用于支持网管设备与网络设备之间的通信，从所述网络设备接收上述方法中所涉及的信息或者指令。所述网管设备还可以包括存储器，所述存储器用于与处理器耦合，其保存网管设备必要的程序指令和数据。
在另一个可能的设计中，所述网管设备包括：处理器、发送器、接收器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接发送器、接收器、随机存取存储器以及只读存储器。其中，当需要运行网管设备时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导网管设备进入正常运行状态。在网管设备进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第四方面，提供一种网管设备，所述网管设备包括：主控板和接口板，进一步，还可以包括交换网板。所述网管设备用于执行第一方面或第一方面的任意可能的实现方式中的方法。具体地，所述网管设备包括用于执行第一方面或第一方面的任意可能 的实现方式中的方法的模块。
第五方面，提供一种网管设备，所述网管设备包括控制器和第一转发子设备。所述第一转发子设备包括：接口板，进一步，还可以包括交换网板。所述第一转发子设备用于执行第四方面中的接口板的功能，进一步，还可以执行第四方面中交换网板的功能。所述控制器包括接收器、处理器、发送器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接接收器、发送器、随机存取存储器以及只读存储器。其中，当需要运行控制器时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导控制器进入正常运行状态。在控制器进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第四方面中主控板的功能。
第六方面，提供了一种计算机存储介质，用于储存为上述网管设备所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述第一方面中网管设备的功能或步骤。
第七方面，提供了一种网络设备，所述网络设备具有实现上述方法中网络设备行为的功能。所述功能可以基于硬件实现，也可以基于硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，网络设备的结构中包括处理器和接口，所述处理器被配置为支持网络设备执行上述方法中相应的功能。所述接口用于支持网络设备与网管设备之间的通信，向网管设备发送上述方法中所涉及的信息或者指令。所述网络设备还可以包括存储器，所述存储器用于与处理器耦合，其保存网络设备必要的程序指令和数据。
在另一个可能的设计中，所述网络设备包括：处理器、发送器、接收器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接发送器、接收器、随机存取存储器以及只读存储器。其中，当需要运行网络设备时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导网络设备进入正常运行状态。在网络设备进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第八方面，提供一种网络设备，所述网络设备包括：主控板和接口板，进一步，还可以包括交换网板。所述网络设备用于执行第二方面或第二方面的任意可能的实现方式中的方法。具体地，所述网络设备包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的模块。
第九方面，提供一种网络设备，所述网络设备包括控制器和第二转发子设备。所述第二转发子设备包括：接口板，进一步，还可以包括交换网板。所述第二转发子设备用于执行第八方面中的接口板的功能，进一步，还可以执行第八方面中交换网板的功能。所述控制器包括接收器、处理器、发送器、随机存取存储器、只读存储器以及总线。其中，处理器通过总线分别耦接接收器、发送器、随机存取存储器以及只读存储器。其中，当需要运行控制器时，通过固化在只读存储器中的基本输入/输出系统或者嵌入式系统中的bootloader引导系统进行启动，引导控制器进入正常运行状态。在控制器进入正常运行状态后，在随机存取存储器中运行应用程序和操作系统，使得该 处理器执行第八方面中主控板的功能。
第十方面，提供了一种计算机存储介质，用于储存为上述网络设备所用的程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成上述第二方面中网络设备的功能或步骤。
第十一方面，提供一种网络系统，所述网络系统包括网管设备和网络设备，所述网管设备为前述第三方面或第四方面或第五方面中的网管设备，所述网络设备为前述第七方面或第八方面或第九方面中的网络设备。
通过上述方案，所述网管设备生成并向所述网络设备发送扩展的ECA实例，当所述网络设备判断所述扩展的ECA实例中的第一条件满足时，所述网络设备触发所述扩展的ECA实例中的第一事件发生，进而触发所述扩展的ECA实例中的第一动作(telemetry功能)，从而，向所述网管设备发送相对应的telemetry数据。如此这样，所述扩展的ECA模型实现了所述网络设备中的网络事件与telemetry功能自动关联，从而使得所述网络设备能够根据发生的网络事件自动启动telemetry功能和发送telemetry数据。
附图说明
图1为本申请实施例的一种通信网络结构示意图；
图2为本申请实施例的一种数据处理方法流程图；
图3为本申请实施例的网管设备的结构示意图；
图4为本申请实施例的网管设备的硬件结构示意图；
图5为本申请实施例的网管设备的硬件结构示意图；
图6为本申请实施例的网络设备的结构示意图；
图7为本申请实施例的网络设备的硬件结构示意图；
图8为本申请实施例的网络设备的硬件结构示意图。
具体实施方式
下面通过具体实施例，分别进行详细的说明。
图1为本申请实施例的一种通信网络结构示意图。如图1所述，所述通信网络包括网管设备和网络设备。其中，本申请实施方式中，对网络设备的数量不进行限定，例如图1所示的通信网络包括网络设备A、网络设备B和网络设备C。所述网管设备分别经由通信链路与所述网络设备A、网络设备B和网络设备C进行通信。在本申请实施方式中，在不增加附加说明的情况下，所述网络设备可以是所述网络设备A、网络设备B和网络设备C中的任一台网络设备。所述网管设备可以被看作所述通信网络中的管理设备，所述网络设备A、网络设备B和网络设备C可以被看作所述通信网络中的被管理设备。所述网管设备可以是一台独立的硬件设备，例如一台服务器或者一个控制器；所述网管设备也可以包括多台硬件设备，例如所述网管设备包括控制设备和客户端设备。其中，所述控制设备经由通信链路与所述网络设备通信，所述客户端设备经由有线链路或无线链路与所述控制设备通信。所述网络设备可以是一台独立的硬件设备，例如一台路由器或交换机，并且，所述网络设备可以包括多个转发板卡，每个转发板卡包括物理端口与其他网络设备通信，而且每个转发板卡可以包括中央处理器(Central Processing Unit，CPU)。所述网络设备也可以包括多台硬件设备，例如所述网络设备包括路由器和多台主机，路由器分别与多台主机通信。
所述网管设备向所述网络设备(如图1中的网络设备A)发送扩展的ECA实例。在一种可能的实现方式中，所述网管设备可以直接生成扩展的ECA实例，然后向所述网络设备发送所述扩展的ECA实例。在另一种可能的实现方式中，所述网管设备可以首先生成扩展的ECA模型，所述网管设备根据所述扩展的ECA模型生成相应的所述扩展的ECA实例，然后向所述网络设备发送所述扩展的ECA实例。
其中，所述扩展的ECA模型可以基于NETCONF实现，具体的，基于YANG模型实现。所述扩展的ECA模型可以包括事件、条件和动作。所述事件表示与网络设备相关的网络事件。所述条件表示能够触发网络事件发生的条件。所述动作表示当所述事件发生了触发相应的telemetry功能。因此，所述扩展的ECA模型表示当满足所述条件，所述事件被触发，所述事件发生后触发相应的所述动作(telemetry功能)。
所述扩展的ECA模型是一种通用性的模型。所述网管设备可以根据所述扩展的ECA模型和具体需要监测的telemetry指标生成所述扩展的ECA实例。因此，所述扩展的ECA实例是根据所述扩展的ECA模型生成的具体化的监测实例。例如，所述网管设备想要监控所述网络设备的CPU占用率，并且当CPU占用率大于门限值时，要求所述网络设备向所述网管设备发送超过门限值的CPU占用率。所述网管设备可以根据所述扩展的ECA模型中的事件部分和CPU占用率相关的具体事件(例如，向网管设备报告CPU占用率)生成第一事件，根据所述扩展的ECA模型中的条件部分和CPU占用率相关的具体条件(例如，CPU占用率大于门限值)生成第一条件，和根据所述扩展的ECA模型中的动作部分和CPU占用率相关的具体动作(例如，发送CPU占用率相对应的telemetry数据)生成第一动作。因此，所述扩展的ECA实例可以包括第一事件、第一条件和第一动作。其中，所述扩展的ECA实例中的所述第一事件、第一条件和第一动作是所述扩展的ECA模型中的事件、条件和动作的具体监测实例的实现形式。
所述网络设备接收所述网管设备发送的所述扩展的ECA实例。在一种可能的实现方式中，所述扩展的ECA实例以XML的格式实现。所述网路设备接收到所述扩展的ECA实例后，运行所述扩展的ECA实例。所述网络设备在确定所述扩展的ECA实例中的第一条件满足的情况下，所述网络设备触发所述扩展的ECA实例中的第一事件的发生。然后，所述网络设备确定所述第一事件发生的情况下，触发相应的所述扩展的ECA实例中的第一动作(也就是图1中所示的telemetry功能)。所述网络设备在触发telemetry功能，根据telemetry功能生成相应的telemetry数据。然后，所述网络设备将所述telemetry数据发送到所述网管设备。具体的实现方式可以参见后续方法实现方式中的说明。
通过上述实现方式，所述网管设备生成并向所述网络设备发送扩展的ECA实例，当所述网络设备判断所述扩展的ECA实例中的第一条件满足时，所述网络设备触发所述扩展的ECA实例中的第一事件发生，进而触发所述扩展的ECA实例中的第一动作(telemetry功能)，从而，向所述网管设备发送相对应的telemetry数据。如此这样，所述扩展的ECA模型实现了所述网络设备中的网络事件与telemetry功能自动关联，从而使得所述网络设备能够根据发生的网络事件自动启动telemetry功能和发送telemetry数据。应当理解，图1示出了网管设备与网络设备A之间的交互过程，应当理解，网管设备与网络设备B之间的交互过程和网管设备与网络设备C之间的交互过 程也可以按照上述实现方式实现。在上述实现方式中，以网络设备作为被检测对象进行说明，应当理解，所述网络设备中的一部分同样可以作为上述实现方式中的被检测对象(例如，网络设备包括的一个或多个转发板卡，或者网络设备包括的路由器和/或主机)。
图2为本申请实施例的一种数据处理方法流程图。图2所示的方法可以应用在图1所示的网络结构中。在本申请实施方式中，为了方便说明，使用“网管设备”和“网络设备”进行说明，应当理解，“网络设备”可以是图1中的网络设备A、网络设备B和网络设备C中的任一台网络设备。在本申请实施方式中，在不加特殊说明的情况下，第一动作是指telemetry功能。具体的，所述方法包括：
S101、网管设备生成扩展的ECA实例，所述扩展的ECA实例包括第一事件、第一条件和第一动作，所述第一动作包括第一对象标识和第一指标类型，所述第一对象标识指示第一待检测对象，所述第一指标类型指示所述第一待检测对象的性能指标，所述扩展的ECA实例用于指示所述网管设备管理的网络设备根据所述第一事件和所述第一条件向所述网管设备发送与所述第一指标类型对应的、针对所述第一待检测对象的第一检测数据，所述网络设备包括所述第一待检测对象。
根据前述实施方式，在一种可能的实现方式中，所述网管设备可以直接生成所述扩展的ECA实例。所述扩展的ECA实例包括第一事件、第一条件和第一动作。所述第一事件表示与网络设备相关的网络事件。所述第一条件表示能够触发网络事件发生的条件。所述第一动作表示当所述事件发生了触发相应的telemetry功能。因此，所述扩展的ECA实例表示当满足所述第一条件，触发所述第一事件发生，所述第一事件发生后触发相应的所述第一动作(telemetry功能)。
Figure PCTCN2020116542-appb-000001
表1
表1示例的展示了常用的扩展的ECA实例的描述。也就是说，表1使用了实现功 能的方式描述了各个扩展的ECA实例。在实际的应用场景中，可以采用多种协议或计算机语言实现扩展的ECA实例，例如采用XML方式实现上述各个扩展的ECA实例。下面分别介绍表1中的扩展的ECA实例。
扩展的ECA实例1实现了对丢包率的监测。具体的，所述网管设备遥测所述网络设备执行所述扩展的ECA实例1。所述网络设备监测第一待检测对象的丢包率，并且当丢包率大于门限值(第一条件)触发向所述网管设备报告丢包率(第一事件)。所述网络设备确定第一事件发生，触发向所述网管设备发送超过门限值的丢包率(第一动作)的telemetry功能。其中，被发送的超过门限值的丢包率属于telemetry数据。在一种可能的实现方式中，扩展的ECA实例1中的丢包率是设备内的丢包率，例如，丢包率是所述第一待检测对象的出端口队列和入端口队列的数据包数量的差值。在另一种可能的实现方式中，扩展的ECA实例1中的丢包率是设备间链路的丢包率，例如，丢包率是所述第一待检测对象与所述第一待检测对象的上一跳网络设备之间的链路的丢包率，其中所述第一待检测对象作为流量的接收端。在本申请实施方式中，所述网络设备包括所述第一待检测对象。也就是说，所述第一待检测对象可以是所述网络设备本身，也可以是所述网络设备包括的部件或设备。例如，所述第一待检测对象是所述网络设备中的转发板卡，或者所述第一待检测对象是所述网络设备包括的主机。
扩展的ECA实例2实现了对CPU占用率的监测。具体的，所述网管设备遥测所述网络设备执行所述扩展的ECA实例2。所述网络设备监测第一待检测对象的CPU占用率，并且当CPU占用率大于门限值(第一条件)触发向所述网管设备报告CPU占用率(第一事件)。所述网络设备确定第一事件发生，触发向所述网管设备发送超过门限值的CPU占用率(第一动作)的telemetry功能。其中，被发送的超过门限值的CPU占用率属于telemetry数据。其中，所述网络设备可以包括多个CPU，例如所述网络设备包括多个转发板卡，每个转发板卡包括CPU。因此，扩展的ECA实例2中的CPU占用率可以是所述网络设备的中央处理器的占用率、或者所述网络设备包括的转发板卡上的CPU的占用率、或者所述网络设备包括的主机中的CPU的占用率。
扩展的ECA实例3实现了对队列长度的监测。具体的，所述网管设备遥测所述网络设备执行所述扩展的ECA实例3。所述网络设备监测第一待检测对象的队列长度，并且当队列长度大于门限值(第一条件)触发向所述网管设备报告队列长度(第一事件)。所述网络设备确定第一事件发生，触发向所述网管设备发送超过门限值的队列长度(第一动作)的telemetry功能。其中，队列长度包括出端口队列长度或者入端口队列长度。
扩展的ECA实例4实现了对时延的监测。具体的，所述网管设备遥测所述网络设备执行所述扩展的ECA实例4。所述网络设备监测第一待检测对象的时延，并且当时延大于门限值(第一条件)触发向所述网管设备报告时延(第一事件)。所述网络设备确定第一事件发生，触发向所述网管设备发送超过门限值的时延(第一动作)的telemetry功能。在一种可能的实现方式中，扩展的ECA实例4中的时延是设备间的链路时延，例如，时延是所述第一待检测对象与所述第一待检测对象的上一跳网络设备之间的链路的时延，其中所述第一待检测对象作为流量的接收端。在另一种可能的实现方式中，扩展的ECA实例4中的时延是设备内的处理时延，例如，时延是从所述第一检测对象的入端口队列到出端口队列的时延。
扩展的ECA实例5实现了对抖动值的监测。具体的，所述网管设备遥测所述网络设备执行所述扩展的ECA实例5。所述网络设备监测第一待检测对象的抖动值，并且当抖动值大于门限值(第一条件)触发向所述网管设备报告抖动值(第一事件)。所述网络设备确定第一事件发生，触发向所述网管设备发送超过门限值的抖动值(第一动作)的telemetry功能。其中，扩展的ECA实例5中的抖动是指流经所述第一待检测对象的报文之间的时延。通过抖动可以检测顺序发送的数据流中的多个报文之间是否发生中断。
扩展的ECA实例6实现了对带宽利用率的监测。具体的，所述网管设备遥测所述网络设备执行所述扩展的ECA实例6。所述网络设备监测第一待检测对象的带宽利用率，并且当带宽利用率小于门限值(第一条件)触发向所述网管设备报告带宽利用率(第一事件)。所述网络设备确定第一事件发生，触发向所述网管设备发送低于门限值的带宽利用率(第一动作)的telemetry功能。其中，扩展的ECA实例5中的带宽利用率是指所述第一待检测对象的出端口发送流量的速率与连接所述出端口的链路的额定物理带宽之间的比值。
另外，表1中的最后一行表示表1中所例举的扩展的ECA实例并不是穷举。所述网管设备可以生成其他的扩展的ECA实例。
根据前述实施方式，在另一种可能的实现方式中，所述网管设备在生成所述扩展的ECA实例之前，首先获取扩展的ECA模型。所述扩展的ECA模型可以包括事件、条件和动作。所述网管设备可以自动的生成所述扩展的ECA模型，也可以从其他设备接收所述扩展的ECA模型。所述网管设备生成所述网管设备后，可以根据具体需要监测的telemetry指标生成所述扩展的ECA实例。举例说明，所述网管设备希望生成扩展的ECA实例2，从而，所述网管设备能够对所述第一待检测对象的CPU占用率进行检测。所述网管设备可以根据表1中针对扩展的ECA实例2的描述，将扩展的ECA实例2中的第一事件的相关参数添加到所述扩展的ECA模型的事件部分，将扩展的ECA实例2中的第一条件的相关参数添加到所述扩展的ECA模型的条件部分，和将扩展的ECA实例2中的第一动作的相关参数添加到所述扩展的ECA模型的动作部分，从而生成扩展的ECA实例2。
所述扩展的ECA实例中的第一动作包括第一对象标识和第一指标类型。所述第一对象标识指示所述第一待检测对象。例如，所述第一待检测对象是所述网络设备，所述第一对象标识具体的可以是所述网络设备的设备标识。又例如，所述第一待检测对象是所述网络设备包括的转发板卡，所述第一对象标识具体的可以是所述网络设备的设备标识和该转发板卡标识，或者所述第一对象标识具体的可以是所述网络设备的设备标识和该转发板卡在所述网络设备中的位置标识。在同一个扩展的ECA实例中可以包括多个第一对象标识。具体的，所述第一动作不仅包括上述提及的第一对象标识和第一指标类型，所述第一动作还包括第二对象标识和第二指标类型，所述第二对象标识指示第二待检测对象，所述第二指标类型指示所述第二待检测对象的性能指标。例如，扩展的ECA实例2中包括网络设备A的设备标识和网络设备B的设备标识，并且，第一指标类型和第二指标类型均为CPU占用率。这样，所述网管设备可以通过扩展的ECA实例2对网络设备A和网络设备B的CPU占用率进行监测。所述第一指标类型指示所述第一待检测对象的性能指标。举例说明，所述网管设备生成扩展的ECA 实例1，所述第一指标类型的值为01，01表示丢包率。所述网管设备生成扩展的ECA实例2，所述第一指标类型的值为02，02表示CPU占用率。
所述扩展的ECA实例用于指示所述网管设备管理的网络设备根据所述第一事件和所述第一条件向所述网管设备发送与所述第一指标类型对应的、针对所述第一待检测对象的第一检测数据。所述扩展的ECA实例可以指示所述网络设备执行所述扩展的ECA实例，从而触发所述扩展的ECA实例中的telemetry功能，生成相应的telemetry数据。应当理解，本申请实现方式示例性的将telemetry数据作为第一检测数据。
可选的，所述第一动作还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型。当网络设备中包括多种业务的流量时，通过组标识可以针对具体的业务的流量进行监测。举例说明，网络设备A中包括有三层虚拟专用网(virtual private network，VPN)业务和多协议标签交换(multi-protocol label switch，MPLS)业务。所述网管设备希望对网络设备A中相关MPLS业务的数据流量的丢包率进行监测。因此，扩展的ECA实例1可以包括组标识，组标识的取值为01，表示扩展的ECA实例1用于对MPLS业务的数据流量的丢包率进行监测。
可选的，所述第一动作还包括使能标志，所述使能标志用于使能所述第一动作。所述网络设备运行telemetry功能时，需要运行与telemetry功能相关的协议。所述网管设备对所述网络设备的监测可能是周期进行的。例如，所述网管设备每间隔1小时监测一次所述网络设备，监测时长为5分钟。如此这样，如果网络设备始终保持telemetry功能的开启，势必增加了所述网络设备的功耗和CPU占用率。因此，所述网络设备在运行过程中，可以将telemetry功能维持在关闭状态，当所述网络设备接收到所述扩展的ECA实例，确定所述第一动作中是否包括使能标志。当所述网络设备确定所述第一动作中包括使能标志，所述网络设备开启发送telemetry数据的功能。
可选的，所述第一动作还包括第一操作类型，所述第一操作类型指示所述第一检测数据的属性。所述第一检测数据的属性可以包括以下中的至少一种：平均值、最大值、最小值和方差值。例如，所述网管设备想要监测所述网络设备的CPU占用率的平均值。所述网管设备在扩展的ECA实例2中可以添加第一操作类型字段，并将第一操作类型字段的值设置为平均值。所述网络设备在运行扩展的ECA实例2过程中，将在预定周期内监测出所有大于门限值的CPU占用率，并且取平均值，然后向所述网管设备发送该平均值。
可选的，所述第一动作还包括第一指标值类型，所述第一指标值类型指示所述第一检测数据的数据类型。具体的，所述第一指标值类型指示了所述网络设备上报telemetry数据时，所述telemetry数据的数值类型，例如，unit 32表示32位无符号整数。
结合前述，当同一个扩展的ECA实例中包括多个待检测对象时，可选的，所述第一动作还包括第一对象标识列表。所述第一对象标识列表包括多个对象标识，例如，所述第一对象标识列表包括第一对象标识和第二对象标识。
下面以一个具体的实现方式为例，说明扩展的ECA模型的动作和扩展的ECA模型的第一动作的实现。
Figure PCTCN2020116542-appb-000002
Figure PCTCN2020116542-appb-000003
上述命令行显示了本申请实施方式中扩展的ECA模型的动作的具体实现。其中，“rw telemetry”表示所述动作是telemetry功能。“rw enable”表示了前述实施方式中的使能标志，当取值为“enable”时，指示网络设备启动向网管设备发送telemetry数据的功能。“rw group-id”表示了前述实施方式中的组标识。“rw telemtry-attributes”表示该行之后的命令行是对属性功能的描述。“rw node-telemetry-attributes*[node-selector]”表示了前述实施方式中的第一对象标识列表。“rw node-selector”表示了前述实施方式中的第一对象标识或第二对象标识。“rw metric-type”表示了前述实施方式中的第一指标类型或第二指标类型。“rw operation-type”表示了前述实施方式中的第一操作类型。“ro metric-value”表示了前述实施方式中的第一指标值类型。
根据前述，所述网管设备可以根据扩展的ECA模型生成扩展的ECA实例。具体的，所述网管设备在扩展的ECA模型添加具体的相关参数，生成相应的扩展的ECA实例。例如针对上述扩展的ECA模型的动作部分的具体实现，网管设备希望生成扩展的ECA实例2，以便监测网络设备A的CPU占用率。那么，网管设备在“rw node-telemetry-attributes*[node-selector]”中添加网络设备A的标识，在“rw node-selector”中添加网络设备A的标识，在“rw metric-type”中添加表示CPU占用率的标识。相应的，所述网管设备还根据监测要求设置上述动作部分的其参数的具体取值，从而形成扩展的ECA实例2中的第一动作部分。当然，网管设备也要按照类似的方式相应的生成扩展的ECA实例2的第一事件和第一条件部分，此处不进行赘述。
根据前述，当同一个扩展的ECA实例中包括多个待检测对象时，例如，将扩展的ECA实例2应用到网络设备A和网络设备B的CPU占用率的监测。那么，网管设备在“rw node-telemetry-attributes*[node-selector]”中添加网络设备A的标识和网络设备B的标识。对于“rw node-selector”、“rw metric-type”、“rw operation-type”和“ro metric-value”，生成的扩展的ECA实例2包括两组参数，例如，“rw node-selector-1”、“rw metric-type-1”、“rw operation-type-1”和“ro metric-value-1”是相关网络设备A的参数，“rw node-selector-2”、“rw metric-type-1”、“rw operation-type-2”和“ro metric-value-2”是相关网络设备B的参数。
结合前述，在本申请实施方式中，所述第一指标类型可以指示能够通过测量手段获得相应数据的性能指标，例如，丢包率、CPU占用率、队列长度、时延、抖动值和带宽利用率等。所述第一指标类型也可以指示不需要通过测量手段获得相应数据的性能指标，例如，第一待检测对象的配置信息等。
S102、所述网管设备向所述网络设备发送第一消息，所述第一消息包括所述扩展 的ECA实例。
S103、所述网络设备接收所述网管设备发送的所述第一消息。
所述网管设备在生成所述扩展的ECA实例，向所述网络设备发送第一消息，所述第一消息包括所述扩展的ECA实例。其中，可选的，所述网管设备与所述网络设备之间传递的消息可以基于NETCONF或RESTCONF实现，也就是说，所述第一消息包括NETCONF消息或RESTCONF消息。
可选的，在所述网管设备向所述网络设备发送所述第一消息之前，所述网管设备建立所述网管设备与所述网络设备之间的NETCONF会话或RESTCONF会话。例如，所述网管设备建立所述网管设备与所述网络设备之间的NETCONF会话。所述网管设备向所述网络设备发送NETCONF会话请求消息。所述网络设备接收到所述NETCONF会话请求消息后，确定能够和所述网管设备建立NETCONF会话。所述网络设备向所述网管设备发送NETCONF会话确认消息。所述网管设备接收到所述NETCONF会话确认消息后，确定NETCONF会话建立完成。RESTCONF会话的建立过程与NETCONF会话建立过程类似，此处不进行赘述。
所述网络设备接收所述网管设备发送的所述第一消息。然后，所述网络设备获取所述第一消息中的所述扩展的ECA实例。
S104、当所述网络设备确定所述第一条件成立，所述网络设备确定所述第一事件发生。
S105、当所述网络设备确定所述第一事件发生，所述网络设备向所述网管设备发送第二消息，所述第二消息包括所述第一检测数据，所述第一检测数据是与所述第一指标类型对应的、针对所述第一待检测对象的检测数据。
S106、所述网管设备接收所述网络设备发送的所述第二消息。
举例说明，所述网管设备向所述网络设备发送的扩展的ECA实例是扩展的ECA实例2，并且所述网管设备要监测的待检测对象是网络设备A。网络设备A运行扩展的ECA实例2。网络设备A根据扩展的ECA实例2中的第一条件部分检测网络设备A的CPU占用率。然后，网络设备A将检测到的CPU占用率的值与门限值进行比较。网络设备A确定检测到的CPU占用率的值大于门限值，网络设备A确定满足扩展的ECA实例2中的第一条件。然后，网络设备A触发扩展的ECA实例2中的第一事件(向网管设备报告CPU占用率)发生。当网络设备A确定扩展的ECA实例2中的第一事件发生，网络设备A执行扩展的ECA实例2中的第一动作。可选的，网络设备A发现扩展的ECA实例2中的第一动作包括的使能标志为enable状态，使能向网管设备发送telemetry数据的功能。网络设备A根据ECA实例2中的第一动作包括的各个字段中的参数，确定最终的第一检测数据(CPU占用率的值)，也就是telemetry数据。
所述网络设备确定所述第一检测数据后，生成所述第二消息。根据前述的说明，所述第二消息包括NETCONF消息或RESTCONF消息。下面以一个具体的实现方式为例，说明所述第二消息的实现方式。
Figure PCTCN2020116542-appb-000004
Figure PCTCN2020116542-appb-000005
其中，“telemetry-trigger”表示所述第二消息是telemetry功能触发的。“ro event-name”表示所述第二消息相关联的第一事件标识，其与所述网络设备执行的扩展的ECA实例中的第一事件标识对应。“ro group-id”表示发送的telemetry数据对应的组标识，其与所述网络设备执行的扩展的ECA实例中的组标识对应。“ro node-telemetry-attributes*[node-selector]”表示发送的telemetry数据对应的第一对象标识列表，其与所述网络设备执行的扩展的ECA实例中的“re node-telemetry-attributes*[node-selector]”对应。“ro node-selector”表示了前述实施方式中的第一对象标识或第二对象标识，其与所述网络设备执行的扩展的ECA实例中的“re node-selector”对应。“ro metric-type”表示了前述实施方式中的第一指标类型或第二指标类型，其与所述网络设备执行的扩展的ECA实例中的““rw metric-type””对应。“ro metric-value”中包括所述第一检测数据。
当所述网络设备需要向所述网管设备发送多个待检测对象的检测数据时，可以生成多个第二消息，分别发送给所述网管设备；或者，生成一个第二消息，用于携带多个待检测对象的检测数据。使用一个第二消息携带多个待检测对象的检测数据的实现方式可以参照前述实施方式的描述。
所述网络设备生成所述第二消息后，向所述网管设备发送所述第二消息。相应的，所述网管设备接收所述网络设备发送的所述第二消息。
在一种可能的实现方式中，所述网络设备按照预定的周期，向所述网管设备发送所述第二消息。例如所述网络设备每间隔5分钟向所述网管设备发送一次第二消息。
在另一种可能的实现方式中，所述网络设备可以根据所述网管设备的查询请求发送所述第二消息。例如，所述网管设备向所述网络设备发送请求消息，所述请求消息用于请求所述网络设备发送所述第二消息。所述请求消息可以包括NETCONF消息或RESTCONF消息。所述网络设备根据所述请求消息向所述网管设备发送所述第二消息。可选的，所述网管设备按照预定的周期(或者预设频率)，向所述网络设备发送所述请求消息。例如所述网管设备每间隔5分钟向所述网络设备发送一次请求消息。
结合前述实施方式，所述第一条件是所述第一待检测对象满足所述第一指标类型指示的性能指标的条件。例如，参见表1中的扩展的ECA实例2。在扩展的ECA实例2的第一动作中，所述第一指标类型的取值是02，表明所述第一指标类型指示的性能指标是CPU占用率。扩展的ECA实例2中的第一条件是和CPU占用率相关联的，也就是说，设定的条件是与CPU占用率相关的条件。从扩展的ECA实例7可以看出，在第一条件中设定的性能指标(CPU占用率)与在第一动作中设定的性能指标(CPU占用率)相同。
在另一种可能的实现方式中，所述第一条件是所述第一待检测对象满足第三指标类型指示的性能指标的条件，其中，所述第三指标类型与所述第一指标类型不相同。例如，扩展的ECA实例7(表1中未示出)的第一事件是“向网管设备报告ARP统计 量”(其中，ARP是指地址解析协议，Address Resolution Protocol)，第一条件是“监测CPU占用率，且CPU占用率大于门限值”，第一动作是“发送预定周期内待检测对象接收到的ARP报文的数量”。其中，关于“发送预定周期内待检测对象接收到的ARP报文的数量”的具体的实现可以是：当第一事件发生后，预定周期开始计时，网络设备在预定周期内检测待检测对象接收到的ARP报文的数量，直到预定周期计时结束，然后向网管设备发送统计的ARP报文的数量。扩展的ECA实例7可以被应用在ARP报文攻击检测中。从扩展的ECA实例7可以看出，在第一条件中设定的性能指标(CPU占用率)与在第一动作中设定的性能指标(ARP报文的数量)不相同。
通过上述实现方式，所述网管设备生成并向所述网络设备发送扩展的ECA实例，当所述网络设备判断所述扩展的ECA实例中的第一条件满足时，所述网络设备触发所述扩展的ECA实例中的第一事件发生，进而触发所述扩展的ECA实例中的第一动作(telemetry功能)，从而，向所述网管设备发送相对应的telemetry数据。如此这样，所述扩展的ECA模型实现了所述网络设备中的网络事件与telemetry功能自动关联，从而使得所述网络设备能够根据发生的网络事件自动启动telemetry功能和发送telemetry数据。
图3为本申请实施例的网管设备1000的结构示意图。图3所示的网管设备1000可以执行上述实施例的方法中网管设备执行的相应步骤。所述网管设备被部署在通信网络中，所述通信网络还包括网络设备。如图3所示，所述网管设备1000包括接收单元1002、处理单元1004和发送单元1006。
所述处理单元1004，用于生成ECA实例，所述扩展的ECA实例包括第一事件、第一条件和第一动作，所述第一动作包括第一对象标识和第一指标类型，所述第一对象标识指示第一待检测对象，所述第一指标类型指示所述第一待检测对象的性能指标，所述扩展的ECA实例用于指示所述网管设备管理的网络设备根据所述第一事件和所述第一条件向所述网管设备发送与所述第一指标类型对应的、针对所述第一待检测对象的第一检测数据，所述网络设备包括所述第一待检测对象；
所述发送单元1006，用于向所述网络设备发送第一消息，所述第一消息包括所述扩展的ECA实例；
所述接收单元1002，用于接收所述网络设备发送的第二消息，所述第二消息包括所述第一检测数据。
可选的，所述第一条件是所述第一待检测对象满足所述第一指标类型指示的性能指标的条件。
可选的，所述第一条件是所述第一待检测对象满足第三指标类型指示的性能指标的条件，其中，所述第三指标类型与所述第一指标类型不相同。
可选的，在所述接收单元1002接收所述网络设备发送的第二消息之前，所述发送单元1006还用于向所述网络设备发送请求消息，所述请求消息用于请求所述网络设备发送所述第二消息。
可选的，在所述发送单元1006向所述网络设备发送请求消息中，所述发送单元1006具体用于按照预设频率向所述网络设备发送所述请求消息。
可选的，在处理单元1004生成ECA实例之前，所述处理单元1004还用于获取扩展的ECA模型，所述扩展的ECA模型指示所述处理单元1004根据所述扩展的ECA 模型和需要监控的事件生成所述扩展的ECA实例。
可选的，所述第一动作还包括第二对象标识和第二指标类型，所述第二对象标识指示第二待检测对象，所述第二指标类型指示所述第二待检测对象的性能指标，所述扩展的ECA实例还用于指示所述网络设备根据所述第一事件和所述第一条件向所述网管设备发送与所述第二指标类型对应的、针对所述第二待检测对象的第二检测数据，所述网络设备包括所述第二待检测对象；所述第二消息还包括所述第二检测数据。
可选的，所述第一动作还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型。
可选的，所述第一动作还包括使能标志，所述使能标志用于使能所述第一动作。
可选的，所述第一动作还包括第一操作类型和/或第一指标值类型，所述第一操作类型指示所述第一检测数据的属性，所述第一指标值类型指示所述第一检测数据的数据类型。
可选的，在所述发送单元1006向所述网络设备发送第一消息之前，所述处理单元1004还用于建立所述网管设备与所述网络设备之间的网络配置协议NETCONF会话或RESTCONF会话。
图3所示的网管设备可以执行上述实施例的方法中网管设备执行的相应步骤。网管设备向网络设备发送扩展的ECA实例，所述扩展的ECA实例中包括的动作部分可以触发网络设备的telemetry功能。从而，所述网络设备可以根据所述扩展的ECA实例中包括的事件部分触发telemetry功能，向所述网管设备发送相对应的telemetry数据。从而，基于扩展的ECA模型，实现了网络事件和telemetry的自动关联。
图4为本申请实施例的网管设备设备1100的硬件结构示意图。图4所示的网管设备设备1100可以执行上述实施例的方法中网管设备设备执行的相应步骤。
如图4所示，所述网管设备设备1100包括处理器1101、存储器1102、接口1103和总线1104。其中接口1103可以通过无线或有线的方式实现，具体来讲可以是网卡。上述处理器1101、存储器1102和接口1103通过总线1104连接。
所述接口1103具体可以包括发送器和接收器，用于网管设备设备与上述实施例中的网络设备之间收发信息。例如，所述接口1103用于支持接收所述网络设备发送的第二消息，或者用于支持发送的第一消息。作为举例，所述接口1103用于支持图2中的过程S102和S106。所述处理器1101用于执行上述实施例中由网管设备进行的处理。例如，所述处理器1101用于生成扩展的ECA实例；和/或用于本文所描述的技术的其他过程。作为举例，所述处理器1101用于支持图2中的过程S101。存储器1102包括操作系统11021和应用程序11022，用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及网管设备的处理过程。可选的，所述存储器1102可以包括只读存储器(英文：Read-only Memory，缩写：ROM)和随机存取存储器(英文：Random Access Memory，缩写：RAM)。其中，所述ROM包括基本输入/输出系统(英文：Basic Input/Output System，缩写：BIOS)或嵌入式系统；所述RAM包括应用程序和操作系统。当需要运行网管设备1100时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导网管设备1100进入正常运行状态。在网管设备1100进入正常运行状态后，运行在RAM中的应用程序和操作系统，从而，完成方法实施例中涉及网管设备的处理过程。
可以理解的是，图4仅仅示出了网管设备1100的简化设计。在实际应用中，网管设备可以包含任意数量的接口，处理器或者存储器。
图5为本申请实施例的另一种网管设备1200的硬件结构示意图。图5所示的网管设备1200可以执行上述实施例的方法中网管设备执行的相应步骤。
如图5所述，网管设备1200包括：主控板1210、接口板1230、交换网板1220和接口板1240。主控板1210、接口板1230和1240，以及交换网板1220之间通过系统总线与系统背板相连实现互通。其中，主控板1210用于完成系统管理、设备维护、协议处理等功能。交换网板1220用于完成各接口板(接口板也称为线卡或业务板)之间的数据交换。接口板1230和1240用于提供各种业务接口(例如，POS接口、GE接口、ATM接口等)，并实现数据包的转发。
接口板1230可以包括中央处理器1231、转发表项存储器1234、物理接口卡1233和网络处理器1232。其中，中央处理器1231用于对接口板进行控制管理并与主控板上的中央处理器进行通信。转发表项存储器1234用于保存转发表项。物理接口卡1233用于完成流量的接收和发送。网络存储器1232用于根据所述转发表项控制物理接口卡1233收发流量。
具体的，物理接口卡1233用于接收所述网络设备发送的第二消息。物理接口卡1233还用于向所述网络设备发送第一消息。
物理接口卡1233接收到所述第二消息后，将所述第二消息经由中央处理器1231发送到中央处理器1211，中央处理器1211处理所述第二消息。
中央处理器1211还用于生成扩展的ECA实例。
中央处理器1231还用于控制网络存储器1232获取转发表项存储器1234中的转发表项，并且，中央处理器1231还用于控制网络存储器1232经由物理接口卡1233向所述网络设备发送第一消息。
应理解，本发明实施例中接口板1240上的操作与所述接口板1230的操作一致，为了简洁，不再赘述。应理解，本实施例的网管设备1200可对应于上述方法实施例所具有的功能和/或所实施的各种步骤，在此不再赘述。
此外，需要说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，网管设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，网管设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，网管设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的网管设备的数据接入和处理能力要大于集中式架构的设备。具体采用哪种架构，取决于具体的组网部署场景，此处不做任何限定。
另外，本申请实施例提供了一种计算机存储介质，用于储存为上述网管设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
图6为本申请实施例的网络设备2000的结构示意图。图6所示的网络设备2000可以执行上述实施例的方法中网络设备执行的相应步骤。所述网络设备被部署在通信网络中，所述通信网络还包括网管设备。如图6所示，所述网络设备2000包括接收单 元2002，处理单元2004和发送单元2006。
所述接收单元2002，用于接收网管设备发送的第一消息，所述第一消息包括扩展的ECA实例，所述扩展的ECA实例包括第一事件、第一条件和第一动作，所述第一动作包括第一对象标识和第一指标类型，所述第一对象标识指示第一待检测对象，所述第一指标类型指示所述第一待检测对象的性能指标，所述网络设备包括所述第一待检测对象；
所述处理单元2004，用于当确定所述第一条件成立，确定所述第一事件发生；
所述发送单元2006，用于当所述处理单元2004确定所述第一事件发生，向所述网管设备发送第二消息，所述第二消息包括第一检测数据，所述第一检测数据是与所述第一指标类型对应的、针对所述第一待检测对象的检测数据。
可选的，所述第一条件是所述第一待检测对象满足所述第一指标类型指示的性能指标的条件。
可选的，所述第一条件是所述第一待检测对象满足第三指标类型指示的性能指标的条件，其中，所述第三指标类型与所述第一指标类型不相同。
可选的，在所述发送单元2006向所述网管设备发送第二消息之前，所述接收单元2002还用于接收所述网管设备发送的请求消息，所述请求消息用于请求所述网络设备发送所述第二消息。
可选的，所述第一动作还包括第二对象标识和第二指标类型，所述第二对象标识指示第二待检测对象，所述第二指标类型指示所述第二待检测对象的性能指标，所述网络设备包括所述第二待检测对象，所述第二消息还包括所述第二检测数据，所述第二检测数据是与所述第二指标类型对应的、针对所述第二待检测对象的检测数据。
可选的，所述第一动作还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型，所述第一检测数据是与所述业务类型相关联的检测数据。
可选的，所述第一动作还包括使能标志，所述使能标志用于使能所述第一动作，在所述处理单元2004确定所述第一条件成立之前，所述处理单元2004还用于根据所述使能标志开启运行所述第一动作关联的所述检测数据的发送功能。
可选的，所述第二消息还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型。
可选的，所述第二消息还包括事件标识，所述事件标识指示所述第一事件。
可选的，所述第二消息还包括所述第一对象标识和所述第一指标类型。
图6所示的网络设备可以执行上述实施例的方法中网络设备执行的相应步骤。网管设备向网络设备发送扩展的ECA实例，所述扩展的ECA实例中包括的动作部分可以触发网络设备的telemetry功能。从而，所述网络设备可以根据所述扩展的ECA实例中包括的事件部分触发telemetry功能，向所述网管设备发送相对应的telemetry数据。从而，基于扩展的ECA模型，实现了网络事件和telemetry的自动关联。
图7为本申请实施例的网络设备2100的硬件结构示意图。图7所示的网络设备2100可以执行上述实施例的方法中网络设备执行的相应步骤。
如图7所示，所述网络设备2100包括处理器2101、存储器2102、接口2103和总线2104。其中接口2103可以通过无线或有线的方式实现，具体来讲可以是网卡。上述处理器2101、存储器2102和接口2103通过总线2104连接。
所述接口2103具体可以包括发送器和接收器，用于网络设备与上述实施例中的网管设备之间收发信息或数据。例如，所述接口2103用于支持向所述网管设备发送第二消息；又例如，所述接口2103用于支持接收网管设备发送的第一消息。作为举例，所述接口2103用于支持图2中的过程S103和S105。所述处理器2101用于执行上述实施例中由网络设备进行的处理。例如，所述处理器2101用于生成第二消息，用于执行扩展的ECA实例；和/或用于本文所描述的技术的其他过程。作为举例，所述处理器2101用于支持图2中的过程S104。存储器2102包括操作系统21021和应用程序21022，用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及网络设备的处理过程。可选的，所述存储器2102可以包括只读存储器(英文：Read-only Memory，缩写：ROM)和随机存取存储器(英文：Random Access Memory，缩写：RAM)。其中，所述ROM包括基本输入/输出系统(英文：Basic Input/Output System，缩写：BIOS)或嵌入式系统；所述RAM包括应用程序和操作系统。当需要运行网络设备2100时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导网络设备2100进入正常运行状态。在网络设备2100进入正常运行状态后，运行在RAM中的应用程序和操作系统，从而，完成方法实施例中涉及网络设备的处理过程。
可以理解的是，图7仅仅示出了网络设备2100的简化设计。在实际应用中，网络设备可以包含任意数量的接口，处理器或者存储器。
图8为本申请实施例的另一种网络设备2200的硬件结构示意图。图8所示的网络设备2200可以执行上述实施例的方法中网络设备执行的相应步骤。
如图8所述，网络设备2200包括：主控板2210、接口板2230、交换网板2220和接口板2240。主控板2210、接口板2230和2240，以及交换网板2220之间通过系统总线与系统背板相连实现互通。其中，主控板2210用于完成系统管理、设备维护、协议处理等功能。交换网板2220用于完成各接口板(接口板也称为线卡或业务板)之间的数据交换。接口板2230和2240用于提供各种业务接口(例如，POS接口、GE接口、ATM接口等)，并实现数据包的转发。
接口板2230可以包括中央处理器2231、转发表项存储器2234、物理接口卡2233和网络处理器2232。其中，中央处理器2231用于对接口板进行控制管理并与主控板上的中央处理器进行通信。转发表项存储器2234用于保存转发表项。物理接口卡2233用于完成流量的接收和发送。网络存储器2232用于根据所述转发表项控制物理接口卡2233收发流量。
具体的，物理接口卡2233用于向所述网管设备发送第二消息。物理接口卡2233还用于接收网管网络设备发送的第一消息。
物理接口卡2233接收到所述网管设备发送的第一消息后，将第一消息经由中央处理器2231发送到中央处理器2211，中央处理器2211处理第一消息。
中央处理器2211用于生成第二消息和执行扩展的ECA实例。
中央处理器2231还用于控制网络存储器2232获取转发表项存储器2234中的转发表项，并且，中央处理器2231还用于控制网络存储器2232经由物理接口卡2233完成流量的接收和发送。
应理解，本发明实施例中接口板2240上的操作与所述接口板2230的操作一致， 为了简洁，不再赘述。应理解，本实施例的网络设备2200可对应于上述方法实施例所具有的功能和/或所实施的各种步骤，在此不再赘述。
此外，需要说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的网络设备的数据接入和处理能力要大于集中式架构的设备。具体采用哪种架构，取决于具体的组网部署场景，此处不做任何限定。
另外，本申请实施例提供了一种计算机存储介质，用于储存为上述网络设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。
本申请实施例还包括一种网络系统，所述网络系统包括网管设备和网络设备，所述网管设备为前述图3或图4或图5中的网管设备，所述网络设备为前述图6或图7或图8中的网络设备。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于用户设备中。当然，处理器和存储介质也可以作为分立组件存在于用户设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件或者用硬件和软件的组合来实现。当使用硬件和软件的组合实现时，可以将这些软件存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明。所应理解的是，以上所述仅为本申请的具体实施方式而已。

Claims (43)

  1. 一种数据处理方法，其特征在于，所述方法包括：
    网管设备生成扩展的事件-条件-动作ECA实例，所述扩展的ECA实例包括第一事件、第一条件和第一动作，所述第一动作包括第一对象标识和第一指标类型，所述第一对象标识指示第一待检测对象，所述第一指标类型指示所述第一待检测对象的性能指标，所述扩展的ECA实例用于指示所述网管设备管理的网络设备根据所述第一事件和所述第一条件向所述网管设备发送与所述第一指标类型对应的、针对所述第一待检测对象的第一检测数据，所述网络设备包括所述第一待检测对象；
    所述网管设备向所述网络设备发送第一消息，所述第一消息包括所述扩展的ECA实例；
    所述网管设备接收所述网络设备发送的第二消息，所述第二消息包括所述第一检测数据。
  2. 如权利要求1所述的方法，其特征在于，所述第一条件是所述第一待检测对象满足所述第一指标类型指示的性能指标的条件。
  3. 如权利要求1所述的方法，其特征在于，所述第一条件是所述第一待检测对象满足第三指标类型指示的性能指标的条件，其中，所述第三指标类型与所述第一指标类型不相同。
  4. 如权利要求1-3中任一项所述的方法，其特征在于，在所述网管设备接收所述网络设备发送的第二消息之前，所述方法还包括：
    所述网管设备向所述网络设备发送请求消息，所述请求消息用于请求所述网络设备发送所述第二消息。
  5. 如权利要求4所述的方法，其特征在于，所述网管设备向所述网络设备发送请求消息，包括：
    所述网管设备按照预设频率向所述网络设备发送所述请求消息。
  6. 如权利要求1-5中任一项所述的方法，其特征在于，在网管设备生成扩展的事件-条件-动作ECA实例之前，所述方法还包括：
    所述网管设备获取扩展的ECA模型，所述扩展的ECA模型指示所述网管设备根据所述扩展的ECA模型和需要监控的事件生成所述扩展的ECA实例。
  7. 如权利要求1-6中任一项所述的方法，其特征在于，所述第一动作还包括第二对象标识和第二指标类型，所述第二对象标识指示第二待检测对象，所述第二指标类型指示所述第二待检测对象的性能指标，所述扩展的ECA实例还用于指示所述网络设 备根据所述第一事件和所述第一条件向所述网管设备发送与所述第二指标类型对应的、针对所述第二待检测对象的第二检测数据，所述网络设备包括所述第二待检测对象；
    所述第二消息还包括所述第二检测数据。
  8. 如权利要求1-7中任一项所述的方法，其特征在于，所述第一动作还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型。
  9. 如权利要求1-8中任一项所述的方法，其特征在于，所述第一动作还包括使能标志，所述使能标志用于使能所述第一动作。
  10. 如权利要求1-9中任一项所述的方法，其特征在于，所述第一动作还包括第一操作类型和/或第一指标值类型，所述第一操作类型指示所述第一检测数据的属性，所述第一指标值类型指示所述第一检测数据的数据类型。
  11. 如权利要求1-10中任一项所述的方法，其特征在于，在所述网管设备向所述网络设备发送第一消息之前，所述方法还包括：
    所述网管设备建立所述网管设备与所述网络设备之间的网络配置协议NETCONF会话或RESTCONF会话。
  12. 一种数据处理方法，其特征在于，所述方法包括：
    网络设备接收网管设备发送的第一消息，所述第一消息包括扩展的事件-条件-动作ECA实例，所述扩展的ECA实例包括第一事件、第一条件和第一动作，所述第一动作包括第一对象标识和第一指标类型，所述第一对象标识指示第一待检测对象，所述第一指标类型指示所述第一待检测对象的性能指标，所述网络设备包括所述第一待检测对象；
    当所述网络设备确定所述第一条件成立，所述网络设备确定所述第一事件发生；
    当所述网络设备确定所述第一事件发生，所述网络设备向所述网管设备发送第二消息，所述第二消息包括第一检测数据，所述第一检测数据是与所述第一指标类型对应的、针对所述第一待检测对象的检测数据。
  13. 如权利要求12所述的方法，其特征在于，所述第一条件是所述第一待检测对象满足所述第一指标类型指示的性能指标的条件。
  14. 如权利要求12所述的方法，其特征在于，所述第一条件是所述第一待检测对象满足第三指标类型指示的性能指标的条件，其中，所述第三指标类型与所述第一指标类型不相同。
  15. 如权利要求12-14中任一项所述的方法，其特征在于，在所述网络设备向所述网管设备发送第二消息之前，所述方法还包括：
    所述网络设备接收所述网管设备发送的请求消息，所述请求消息用于请求所述网络设备发送所述第二消息。
  16. 如权利要求12-15中任一项所述的方法，其特征在于，所述第一动作还包括第二对象标识和第二指标类型，所述第二对象标识指示第二待检测对象，所述第二指标类型指示所述第二待检测对象的性能指标，所述网络设备包括所述第二待检测对象，所述第二消息还包括所述第二检测数据，所述第二检测数据是与所述第二指标类型对应的、针对所述第二待检测对象的检测数据。
  17. 如权利要求12-16中任一项所述的方法，其特征在于，所述第一动作还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型，所述第一检测数据是与所述业务类型相关联的检测数据。
  18. 如权利要求12-17中任一项所述的方法，其特征在于，所述第一动作还包括使能标志，所述使能标志用于使能所述第一动作，在所述网络设备确定所述第一条件成立之前，所述方法还包括：
    所述网络设备根据所述使能标志开启运行所述第一动作关联的所述检测数据的发送功能。
  19. 如权利要求12-18中任一项所述的方法，其特征在于，所述第二消息还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型。
  20. 如权利要求12-19中任一项所述的方法，其特征在于，所述第二消息还包括事件标识，所述事件标识指示所述第一事件。
  21. 如权利要求12-20中任一项所述的方法，其特征在于，所述第二消息还包括所述第一对象标识和所述第一指标类型。
  22. 一种网管设备，其特征在于，所述网管设备包括：
    处理单元，用于生成扩展的事件-条件-动作ECA实例，所述扩展的ECA实例包括第一事件、第一条件和第一动作，所述第一动作包括第一对象标识和第一指标类型，所述第一对象标识指示第一待检测对象，所述第一指标类型指示所述第一待检测对象的性能指标，所述扩展的ECA实例用于指示所述网管设备管理的网络设备根据所述第一事件和所述第一条件向所述网管设备发送与所述第一指标类型对应的、针对所述第一待检测对象的第一检测数据，所述网络设备包括所述第一待检测对象；
    发送单元，用于向所述网络设备发送第一消息，所述第一消息包括所述扩展的ECA实例；
    接收单元，用于接收所述网络设备发送的第二消息，所述第二消息包括所述第一检测数据。
  23. 如权利要求22所述的网管设备，其特征在于，所述第一条件是所述第一待检测对象满足所述第一指标类型指示的性能指标的条件。
  24. 如权利要求22所述的网管设备，其特征在于，所述第一条件是所述第一待检测对象满足第三指标类型指示的性能指标的条件，其中，所述第三指标类型与所述第一指标类型不相同。
  25. 如权利要求22-24中任一项所述的网管设备，其特征在于，
    在所述接收单元接收所述网络设备发送的第二消息之前，所述发送单元还用于向所述网络设备发送请求消息，所述请求消息用于请求所述网络设备发送所述第二消息。
  26. 如权利要求25所述的网管设备，其特征在于，
    在所述发送单元向所述网络设备发送请求消息中，所述发送单元具体用于按照预设频率向所述网络设备发送所述请求消息。
  27. 如权利要求22-25中任一项所述的网管设备，其特征在于，
    在处理单元生成扩展的事件-条件-动作ECA实例之前，所述处理单元还用于获取扩展的ECA模型，所述扩展的ECA模型指示所述处理单元根据所述扩展的ECA模型和需要监控的事件生成所述扩展的ECA实例。
  28. 如权利要求22-27中任一项所述的网管设备，其特征在于，所述第一动作还包括第二对象标识和第二指标类型，所述第二对象标识指示第二待检测对象，所述第二指标类型指示所述第二待检测对象的性能指标，所述扩展的ECA实例还用于指示所述网络设备根据所述第一事件和所述第一条件向所述网管设备发送与所述第二指标类型对应的、针对所述第二待检测对象的第二检测数据，所述网络设备包括所述第二待检测对象；
    所述第二消息还包括所述第二检测数据。
  29. 如权利要求22-28中任一项所述的网管设备，其特征在于，所述第一动作还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型。
  30. 如权利要求22-29中任一项所述的网管设备，其特征在于，所述第一动作还包括使能标志，所述使能标志用于使能所述第一动作。
  31. 如权利要求22-30中任一项所述的网管设备，其特征在于，所述第一动作还包括第一操作类型和/或第一指标值类型，所述第一操作类型指示所述第一检测数据的属性，所述第一指标值类型指示所述第一检测数据的数据类型。
  32. 如权利要求22-31中任一项所述的网管设备，其特征在于，
    在所述发送单元向所述网络设备发送第一消息之前，所述处理单元还用于建立所述网管设备与所述网络设备之间的网络配置协议NETCONF会话或RESTCONF会话。
  33. 一种网络设备，其特征在于，所述网络设备包括：
    接收单元，用于接收网管设备发送的第一消息，所述第一消息包括扩展的事件-条件-动作ECA实例，所述扩展的ECA实例包括第一事件、第一条件和第一动作，所述第一动作包括第一对象标识和第一指标类型，所述第一对象标识指示第一待检测对象，所述第一指标类型指示所述第一待检测对象的性能指标，所述网络设备包括所述第一待检测对象；
    处理单元，用于当确定所述第一条件成立，确定所述第一事件发生；
    发送单元，用于当所述处理单元确定所述第一事件发生，向所述网管设备发送第二消息，所述第二消息包括第一检测数据，所述第一检测数据是与所述第一指标类型对应的、针对所述第一待检测对象的检测数据。
  34. 如权利要求33所述的网络设备，其特征在于，所述第一条件是所述第一待检测对象满足所述第一指标类型指示的性能指标的条件。
  35. 如权利要求33所述的网络设备，其特征在于，所述第一条件是所述第一待检测对象满足第三指标类型指示的性能指标的条件，其中，所述第三指标类型与所述第一指标类型不相同。
  36. 如权利要求33-35中任一项所述的网络设备，其特征在于，
    在所述发送单元向所述网管设备发送第二消息之前，所述接收单元还用于接收所述网管设备发送的请求消息，所述请求消息用于请求所述网络设备发送所述第二消息。
  37. 如权利要求33-36中任一项所述的网络设备，其特征在于，所述第一动作还包括第二对象标识和第二指标类型，所述第二对象标识指示第二待检测对象，所述第二指标类型指示所述第二待检测对象的性能指标，所述网络设备包括所述第二待检测对象，所述第二消息还包括所述第二检测数据，所述第二检测数据是与所述第二指标类型对应的、针对所述第二待检测对象的检测数据。
  38. 如权利要求33-37中任一项所述的网络设备，其特征在于，所述第一动作还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型，所述第一检测数据是与所述业务类型相关联的检测数据。
  39. 如权利要求33-38中任一项所述的网络设备，其特征在于，所述第一动作还包括使能标志，所述使能标志用于使能所述第一动作，在所述处理单元确定所述第一条件成立之前，所述处理单元还用于根据所述使能标志开启运行所述第一动作关联的所述检测数据的发送功能。
  40. 如权利要求33-39中任一项所述的网络设备，其特征在于，所述第二消息还包括组标识，所述组标识指示与所述扩展的ECA实例相关联的业务类型。
  41. 如权利要求33-40中任一项所述的网络设备，其特征在于，所述第二消息还包括事件标识，所述事件标识指示所述第一事件。
  42. 如权利要求33-41中任一项所述的网络设备，其特征在于，所述第二消息还包括所述第一对象标识和所述第一指标类型。
  43. 一种网络系统，所述网络系统包括网管设备和网络设备，所述网管设备为权利要求22-32中任一项所述的网管设备，所述网络设备为权利要求33-42中任一项所述的网络设备。
PCT/CN2020/116542 2019-10-16 2020-09-21 一种数据处理方法、设备及系统 WO2021073367A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20876189.0A EP4030691A4 (en) 2019-10-16 2020-09-21 DATA PROCESSING METHOD, DEVICE AND SYSTEM
US17/720,493 US20220239572A1 (en) 2019-10-16 2022-04-14 Data Processing Method, Device, and System

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201910984111 2019-10-16
CN201910984111.3 2019-10-16
CN201911061787.1A CN112671549A (zh) 2019-10-16 2019-11-01 一种数据处理方法、设备及系统
CN201911061787.1 2019-11-01

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/720,493 Continuation US20220239572A1 (en) 2019-10-16 2022-04-14 Data Processing Method, Device, and System

Publications (1)

Publication Number Publication Date
WO2021073367A1 true WO2021073367A1 (zh) 2021-04-22

Family

ID=75400713

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/116542 WO2021073367A1 (zh) 2019-10-16 2020-09-21 一种数据处理方法、设备及系统

Country Status (4)

Country Link
US (1) US20220239572A1 (zh)
EP (1) EP4030691A4 (zh)
CN (1) CN112671549A (zh)
WO (1) WO2021073367A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11171853B2 (en) * 2020-01-30 2021-11-09 Ciena Corporation Constraint-based event-driven telemetry

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040117407A1 (en) * 2002-12-16 2004-06-17 Manoj Kumar Resource and data administration technologies for IT non-experts
CN1938703A (zh) * 2004-03-30 2007-03-28 甲骨文国际公司 管理数据库系统中的事件－条件－操作规则
US20070162423A1 (en) * 2005-12-30 2007-07-12 Shai Alfandary Aware location system and method
CN103792932A (zh) * 2012-11-01 2014-05-14 中国科学院软件研究所 一种基于eca规则的故障检测方法

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6732168B1 (en) * 2000-07-05 2004-05-04 Lucent Technologies Inc. Method and apparatus for use in specifying and insuring policies for management of computer networks
US6968374B2 (en) * 2002-07-03 2005-11-22 Telefonaktiebolaget Lm Ericsson (Publ) Quality of service (QOS) mechanism in an internet protocol (IP) network
US7313533B2 (en) * 2003-07-11 2007-12-25 International Business Machines Corporation Systems and methods for monitoring and controlling business level service level agreements
US8854980B2 (en) * 2005-05-06 2014-10-07 Lockheed Martin Corporation Switching module
US8612572B2 (en) * 2008-05-30 2013-12-17 Microsoft Corporation Rule-based system for client-side quality-of-service tracking and reporting
US20110072442A1 (en) * 2009-09-22 2011-03-24 International Business Machines Corporation Event-handler for selecting responsive actions
US20110153519A1 (en) * 2009-12-22 2011-06-23 Sap Ag Systems and methods for generating trigger networks corresponding to event-condition-action rules
US10225158B1 (en) * 2014-12-22 2019-03-05 EMC IP Holding Company LLC Policy based system management
US10042732B2 (en) * 2015-08-17 2018-08-07 Microsoft Technology Licensing, Llc Dynamic data collection pattern for target device
WO2017147772A1 (zh) * 2016-03-01 2017-09-08 华为技术有限公司 一种消息传输方法及核心网接口设备
CN108024255A (zh) * 2016-11-03 2018-05-11 华为技术有限公司 扩展网络切片实例的方法和网络设备
US20180124183A1 (en) * 2016-11-03 2018-05-03 Futurewei Technologies, Inc. Method and Apparatus for Stateful Control of Forwarding Elements
US10911308B2 (en) * 2017-09-18 2021-02-02 Rapyuta Robotics Co., Ltd. Auto-determining and installing missing components to a to-be-managed device by a single execution of unique device setup command
CN115987773A (zh) * 2019-10-12 2023-04-18 华为技术有限公司 一种设备管理的方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040117407A1 (en) * 2002-12-16 2004-06-17 Manoj Kumar Resource and data administration technologies for IT non-experts
CN1938703A (zh) * 2004-03-30 2007-03-28 甲骨文国际公司 管理数据库系统中的事件－条件－操作规则
US20070162423A1 (en) * 2005-12-30 2007-07-12 Shai Alfandary Aware location system and method
CN103792932A (zh) * 2012-11-01 2014-05-14 中国科学院软件研究所 一种基于eca规则的故障检测方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US20220239572A1 (en) 2022-07-28
CN112671549A (zh) 2021-04-16
EP4030691A4 (en) 2022-11-09
EP4030691A1 (en) 2022-07-20

Similar Documents

Publication Publication Date Title
WO2019233179A1 (zh) 一种数据报文的检测方法、设备及系统
US8098682B2 (en) System and method for interfacing with a management system
US8458305B2 (en) Method and system for matching and repairing network configuration
US9385944B2 (en) Communication system, path switching method and communication device
US11398976B2 (en) Method, device, and system for implementing MUX machine
CN106537840B (zh) 用于网络设备管理的系统和方法
US9288075B2 (en) Method and system for auto-configuration, and network node
US9077625B2 (en) Apparatus and method for controlling a transmission interval of maintenance packets in a communication network
JP2003186765A (ja) ネットワーク接続デバイス、ネットワーク接続デバイス管理システム、ネットワーク接続デバイス管理方法
WO2010022635A1 (zh) 多线程通讯程序中防止线程吊死的方法
CN102263651A (zh) Snmp网络管理系统中局端设备连接状态的检测方法
CN108600100B (zh) 成员端口选取方法和装置
US11258666B2 (en) Method, device, and system for implementing MUX machine
WO2021073367A1 (zh) 一种数据处理方法、设备及系统
US20210377125A1 (en) Network Topology Discovery Method, Device, and System
WO2016082436A1 (zh) 一种业务混合集中处理方法和装置、存储介质
US9374274B2 (en) System and method for automated DCB configuration of access switches
WO2014113957A1 (zh) 一种链路管理方法、设备和通信系统
JP6118464B2 (ja) ポートステータス同期化方法、関連のデバイス、及びシステム
CN115514719A (zh) 报文发送方法、装置、交换机及可读存储介质
KR101589385B1 (ko) 컨트롤러와 네트워크 장치 간 이벤트를 처리하는 방법
CN116055565B (zh) 一种数据传输方法、系统、装置、电子设备及存储介质
CN115150453B (zh) 一种避免lacp协议超时的方法、系统、设备和存储介质
CN115701051A (zh) 分布式设备的检测方法、客户端、服务端、设备和介质
CN117793015A (zh) 专线网络的限速处理方法及装置、存储介质、电子设备

Legal Events

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

Ref document number: 20876189

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020876189

Country of ref document: EP

Effective date: 20220411

NENP Non-entry into the national phase

Ref country code: DE