Ethernet device link monitoring method and apparatus, and storage medium

Abstract

The present disclosure provides an Ethernet device link monitoring method, device and storage medium, relates to the technical field of communication, and solves the technical problem that an SDN management and control device is difficult to discover in time when an Ethernet device link error code event occurs in the case that a local device and a box-type Ethernet device are not from the same device manufacturer. The method comprises the following steps: obtaining an event notification operation, administration and maintenance protocol data unit (OAMPDU) message; determining error code information of the box-type Ethernet device based on the event notification OAMPDU message; converting the error code information of the box-type Ethernet device into an SDN interface message according to a preset model; and sending the SDN interface message to an SDN controller; and the SDN interface message is used to represent the error code event of the box-type Ethernet device. The present disclosure is used in the scenario of Ethernet device link monitoring.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to an Ethernet device link monitoring method, apparatus and storage medium. Background Technology

[0002] Currently, the management of box-type Ethernet devices is based on the proprietary protocols of the equipment manufacturers. Management signaling is converted into protocol messages through the optical transport network (OTN) equipment at the central office, and the management of box-type Ethernet devices is achieved by sending protocol messages to the software defined network (SDN) management equipment.

[0003] However, managing the box-type Ethernet device using the above method requires that the central office equipment and the box-type Ethernet device be from the same equipment manufacturer. When the central office equipment and the box-type Ethernet device are not from the same equipment manufacturer, the SDN management device can only monitor the port status of the central office equipment connected to it, and cannot monitor the status of the Ethernet device link. When an error event occurs in the Ethernet device link, the SDN management device will have difficulty detecting it in time. Summary of the Invention

[0004] This disclosure provides an Ethernet device link monitoring method, apparatus, and storage medium, which solves the technical problem in related technologies where, when the central office equipment and the box-type Ethernet equipment are not from the same manufacturer, the SDN management device can only monitor the port status of the central office equipment connected to it, but cannot monitor the status of the Ethernet device link, and the SDN management device has difficulty in timely detecting when an error event occurs in the Ethernet device link.

[0005] To achieve the above objectives, the present disclosure adopts the following technical solution:

[0006] Firstly, a method for monitoring Ethernet device links is provided. This method includes: acquiring Event Notification Operation Maintenance Management Protocol Data Unit (OAMPDU) messages; the Event Notification OAMPDU message is an Event Notification OAMPDU message in an EFM message sent by a box-type Ethernet device; determining bit error information of the box-type Ethernet device based on the Event Notification OAMPDU message; the bit error information of the box-type Ethernet device is used to characterize bit error events of the box-type Ethernet device; converting the bit error information of the box-type Ethernet device into SDN interface messages according to a preset model; the preset model is a data model constructed based on a data modeling language and the bit error information; and sending SDN interface messages to an SDN controller; the SDN interface messages are used to characterize bit error events of the box-type Ethernet device.

[0007] In conjunction with the first aspect mentioned above, in one possible implementation, the event notification OAMPDU message includes: a source address field, an event type field, and an error information field; the method specifically includes: determining the local area network address of the Ethernet box based on the source address field; determining the bit error event type of the Ethernet box based on the event type field; and determining the number of error frames of the Ethernet box based on the error information field.

[0008] In conjunction with the first aspect mentioned above, in one possible implementation, the SDN interface packet includes: a LAN address field, an event type field, and an error count field; the method specifically includes: according to a preset model, storing the LAN address of the Ethernet box device in the LAN address field of the SDN interface packet; according to a preset model, storing the bit error event type of the Ethernet box device in the event type field of the SDN interface packet; and according to a preset model, storing the number of error frames of the Ethernet box device in the error count field of the SDN interface packet.

[0009] In conjunction with the first aspect mentioned above, in one possible implementation, the method specifically includes: when the event type field is 0x01, determining the fault type of the Ethernet box device as a bit error exceeding the limit event; when the event type field is 0x02, determining the fault type of the Ethernet box device as a frame error exceeding the limit event; and when the event type field is 0x04, determining the fault type of the Ethernet box device as a frame error second exceeding the limit event.

[0010] In conjunction with the first aspect mentioned above, in one possible implementation, the method further includes: generating bit error event notification information based on the bit error event type of the box-type Ethernet device; and sending the bit error event notification information to the SDN controller.

[0011] Secondly, an Ethernet device link monitoring device is provided, comprising: a communication unit and a processing unit; the communication unit is used to acquire Event Notification Operation Maintenance Management Protocol Data Unit (OAMPDU) messages; the Event Notification OAMPDU message is the Event Notification OAMPDU message in the EFM message sent by the Ethernet box device; the processing unit is used to determine the bit error information of the Ethernet box device based on the Event Notification OAMPDU message; the bit error information of the Ethernet box device is used to characterize the bit error event of the Ethernet box device; the processing unit is used to convert the bit error information of the Ethernet box device into SDN interface messages according to a preset model; the preset model is a data model constructed based on a data modeling language and bit error information; the communication unit is used to send SDN interface messages to the SDN controller; the SDN interface messages are used to characterize the bit error event of the Ethernet box device.

[0012] In conjunction with the second aspect above, in one possible implementation, the event notification OAMPDU message includes: a source address field, an event type field, and an error information field; and a processing unit specifically used for: determining the local area network address of the Ethernet box based on the source address field; determining the bit error event type of the Ethernet box based on the event type field; and determining the number of error frames of the Ethernet box based on the error information field.

[0013] In conjunction with the second aspect above, in one possible implementation, the SDN interface packet includes: a LAN address field, an event type field, and an error count field; the processing unit is specifically used to: store the LAN address of the Ethernet box device in the LAN address field of the SDN interface packet according to a preset model; store the bit error event type of the Ethernet box device in the event type field of the SDN interface packet according to a preset model; and store the number of error frames of the Ethernet box device in the error count field of the SDN interface packet according to a preset model.

[0014] In conjunction with the second aspect above, in one possible implementation, the processing unit is specifically used to: determine the fault type of the Ethernet box device as a bit error exceeding the limit event when the event type field is 0x01; determine the fault type of the Ethernet box device as a frame error exceeding the limit event when the event type field is 0x02; and determine the fault type of the Ethernet box device as a frame error second exceeding the limit event when the event type field is 0x04.

[0015] In conjunction with the second aspect above, in one possible implementation, the processing unit is further configured to: generate bit error event notification information based on the bit error event type of the box-type Ethernet device; and send the bit error event notification information to the SDN controller.

[0016] Thirdly, an Ethernet device link monitoring device is provided, comprising: a processor and a memory; wherein the memory is used to store computer execution instructions, and when the Ethernet device link monitoring device is running, the processor executes the computer execution instructions stored in the memory to cause the Ethernet device link monitoring device to perform the Ethernet device link monitoring method as described in the first aspect above and any possible implementation thereof.

[0017] Fourthly, a computer-readable storage medium is provided, which stores instructions that, when executed by a processor of an Ethernet device link monitoring device, cause the Ethernet device link monitoring device to perform the Ethernet device link monitoring method as described in the first aspect and any possible implementation thereof.

[0018] Fifthly, a chip is provided, the chip including a processor and a communication interface, the communication interface and the processor being coupled, the processor being used to run computer programs or instructions to implement the Ethernet device link monitoring method as described in the first aspect above and any possible implementation thereof.

[0019] In this disclosure, the name of the aforementioned Ethernet device link monitoring device does not limit the device or functional module itself. In actual implementation, these devices or functional modules may appear under other names. As long as the function of each device or functional module is similar to that of this disclosure, it falls within the scope of this disclosure and its equivalents.

[0020] The technical solution provided in this disclosure brings at least the following beneficial effects: The Ethernet device link monitoring device in this disclosure first acquires the Event Notification OAMPDU message; the Event Notification OAMPDU message is the Event Notification OAMPDU message in the EFM message sent by the box-type Ethernet device; based on the Event Notification OAMPDU message, the bit error information of the box-type Ethernet device is determined; the bit error information of the box-type Ethernet device is used to characterize the bit error event of the box-type Ethernet device; the bit error information of the box-type Ethernet device is converted into SDN interface packets according to a preset model; the preset model is a data model constructed based on a data modeling language and bit error information; the SDN interface packets are sent to the SDN controller; so that when a bit error event occurs in the Ethernet device link, the SDN controller can promptly detect the bit error event based on the bit error information of the box-type Ethernet device after it has been converted into SDN interface packets. This solves the technical problem that when the central office equipment and the box-type Ethernet device are not from the same manufacturer, the SDN management device can only monitor the port status of the central office equipment connected to it, and cannot monitor the status of the Ethernet device link, making it difficult for the SDN management device to detect bit error events in a timely manner. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0022] Figure 1 This is a schematic diagram of an EFM message structure provided in an embodiment of the present disclosure;

[0023] Figure 2 A schematic diagram of the structure of an event notification OAMPDU provided in an embodiment of this disclosure;

[0024] Figure 3 This is a schematic diagram of an Ethernet device networking structure provided in an embodiment of the present disclosure;

[0025] Figure 4 This is a schematic diagram of the structure of an Ethernet device link monitoring system provided in an embodiment of this disclosure;

[0026] Figure 5 This is a schematic diagram of the hardware structure of an Ethernet device link monitoring device provided in an embodiment of the present disclosure;

[0027] Figure 6 A flowchart illustrating an Ethernet device link monitoring method provided in this embodiment of the disclosure;

[0028] Figure 7 A flowchart illustrating yet another Ethernet device link monitoring method provided in this disclosure embodiment;

[0029] Figure 8 A flowchart illustrating yet another Ethernet device link monitoring method provided in this disclosure embodiment;

[0030] Figure 9 A flowchart illustrating yet another Ethernet device link monitoring method provided in this disclosure embodiment;

[0031] Figure 10 A flowchart illustrating yet another Ethernet device link monitoring method provided in this disclosure embodiment;

[0032] Figure 11 This is a schematic diagram illustrating the process of an Ethernet device link monitoring device monitoring a box-type Ethernet device, as provided in an embodiment of this disclosure.

[0033] Figure 12 This is a schematic diagram of the structure of an Ethernet device link monitoring device provided in an embodiment of this disclosure. Detailed Implementation

[0034] The following describes in detail, with reference to the accompanying drawings, an Ethernet device link monitoring method, apparatus, and storage medium provided in the embodiments of this disclosure.

[0035] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0036] The terms “first” and “second” in this disclosure and its accompanying drawings are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a particular order of objects.

[0037] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this disclosure are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus. It should be noted that in the embodiments of this disclosure, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this disclosure should not be construed as preferred or advantageous over other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0038] In the description of this disclosure, unless otherwise stated, "multiple" means two or more.

[0039] The following explanations of the terms used in the embodiments of this disclosure are provided to facilitate the reader's understanding.

[0040] 1. Ethernet in the First Mile (EFM)

[0041] EFM (Ethernet First Mile) is a process of extending the reach of Ethernet technology through collaboration between end users and carriers. The "first mile" refers to the link between a subscriber or user and the public network. Ethernet in the first mile allows the subscriber to connect using a home Ethernet interface, meaning the faster the speed, the faster the network access. Ethernet in the first mile provides ultimate connectivity and bandwidth for multimedia applications. Ethernet in the first mile also aims to make optical Ethernet a low-cost alternative to DSL and cable modems. IEEE 802.3ah is the standard for the "Ethernet first mile." Figure 1 As shown, Figure 1 This illustration shows an EFM message structure provided in an embodiment of the present disclosure. In a standard IEEE 802.3ah (EFM) message, the main fields include destination address, source address, type, subtype, flags, code, data / pad, and CRC. This disclosure primarily utilizes the Flags and Code messages within the EFM message to transmit information about the cassette Ethernet device.

[0042] Common EFM messages mainly include the following three types: Operation Administration and Maintenance Protocol Data Unit (OAMPDU), Event Notification OAMPDU, and Remote Loopback OAMPDU.

[0043] Among them, the OAMPDU information is used for link connectivity detection. During the handshake phase, the OAM entity periodically sends OAMPDU information at preset time intervals to detect link connectivity; the event notification OAMPDU structure is as follows: Figure 2 As shown; Event Notification OAMPDU is used for link monitoring. When the interface detects an error bit limit exceeding event, frame error limit exceeding event, or frame error second limit exceeding event, the interface notifies the fault by sending an event notification OAMPDU to the peer device; Remote Loopback OAMPDU is used for remote loopback control, controlling the OAM loopback status of the remote device, and enabling or disabling the remote loopback function according to the enable and disable loopback function information in the OAMPDU.

[0044] 2. YANG Model

[0045] YANG is a data modeling language. YANG models define hierarchical data structures that can be used for operations based on network configuration management protocols (such as Netconf), including configuration, status data, remote procedure calls, and notifications. This disclosure uses the YANG language to model information about box-type Ethernet devices within the Netconf protocol, transforming the information from EFM packets into corresponding fields in SDN interface packets using the YANG model.

[0046] 3. Optical transport network (OTN) equipment

[0047] OTN is a transport network based on wavelength division multiplexing (WDM) technology and organized at the optical layer. It serves as the next-generation backbone transport network's 2.5G service quality identifier. OTN is a new generation of "digital transport system" and "optical transport system" standardized by a series of ITU-T recommendations such as G.872, G.709, and G.798. It addresses the problems of traditional WDM networks, such as poor wavelength / sub-wavelength service scheduling capabilities, weak networking capabilities, and weak protection capabilities. OTN equipment is a key component of this optically layered transport network. Access-type OTN equipment mainly includes two types: the first is access equipment deployed in customer rooms (OTN-A), including access equipment supporting OTN encapsulation and Ethernet access equipment that does not support OTN encapsulation; the second is OTN equipment deployed at the central office with integrated service access functions (OTN-U). The network structure of Ethernet equipment is as follows... Figure 3As shown, the box-type Ethernet device connects to the OTN-U deployed at the central office via an Ethernet optical port, and the OTN-U device connects to the SDN controller via a data communication network (DCN) network, thereby enabling the SDN controller to manage the box-type Ethernet device.

[0048] Currently, the management of box-type Ethernet devices is based on the proprietary protocols of the equipment manufacturers. Management signaling is converted into protocol messages by OTN equipment and then sent to SDN management equipment to achieve management of the box-type Ethernet devices. However, this method requires that the central office equipment and the box-type Ethernet device be from the same manufacturer. When the central office equipment and the box-type Ethernet device are not from the same manufacturer, the SDN management equipment can only monitor the port status of the connected central office equipment and cannot monitor the status of the Ethernet device link. Therefore, when bit error events occur on the Ethernet device link, the SDN management equipment struggles to detect them in a timely manner.

[0049] To address the aforementioned technical issues, this disclosure provides an Ethernet device link monitoring method, apparatus, and storage medium. This addresses the problem that, when the central office equipment and the box-type Ethernet device are from different manufacturers, the SDN management device can only monitor the port status of the central office equipment it is connected to, and cannot monitor the Ethernet device link status. Furthermore, when an error event occurs on the Ethernet device link, the SDN management device struggles to detect it in a timely manner. The method includes: an Ethernet device link monitoring device first acquires an event notification OAMPDU message; the event notification OAMPDU message is the event notification OAMPDU message in the EFM message sent by the box-type Ethernet device; the error information of the box-type Ethernet device is determined based on the event notification OAMPDU message; the error information of the box-type Ethernet device is used to characterize the error event of the box-type Ethernet device; the error information of the box-type Ethernet device is converted into an SDN interface message according to a preset model; the preset model is a data model constructed based on a data modeling language and error information; and the SDN interface message is sent to the SDN controller; so that when an error event occurs in the Ethernet device link, the SDN controller can promptly detect the error event based on the error information of the box-type Ethernet device after it has been converted into an SDN interface message. This solves the technical problem that when the central office equipment and the box-type Ethernet device are not from the same manufacturer, the SDN management device can only monitor the port status of the central office equipment connected to it, and cannot monitor the status of the Ethernet device link, making it difficult for the SDN management device to detect error events in a timely manner.

[0050] In one possible implementation, the above-described Ethernet device link monitoring method can be applied to an Ethernet device link monitoring system 400. The following, in conjunction with... Figure 4 This application provides a detailed description of an Ethernet device link monitoring system 400 according to an embodiment. For example... Figure 4 As shown, Figure 4 An Ethernet device link monitoring system 400 is provided for embodiments of this disclosure. The system includes: a box-type Ethernet device 401, an Ethernet device link monitoring device 402, and an SDN controller 403.

[0051] The device 401 is used to send EFM messages to the Ethernet link monitoring device 402. The Ethernet link monitoring device 402 is used to obtain the Event Notification OAMPDU message in the EFM message sent by the device 401. The Event Notification OAMPDU message is the Event Notification OAMPDU message in the EFM message sent by the device 402. The device 402 determines the bit error information of the device 401 based on the Event Notification OAMPDU message. The bit error information of the device 401 is used to characterize the bit error event of the device 401. The device 402 converts the bit error information of the device 401 into SDN interface messages according to a preset model. The preset model is a data modeling language and a data model constructed from the bit error information. The device 402 sends SDN interface messages to the SDN controller 403. The SDN controller 403 determines the bit error event of the device 401 based on the bit error information of the device 401 after it has been converted into SDN interface messages. The SDN controller 403 determines the bit error event of the device 401 based on the bit error information of the device 401 after it has been converted into SDN interface messages.

[0052] In one possible implementation, the hardware structure of the Ethernet device link monitoring device 402 in the aforementioned Ethernet device link monitoring system 400 includes: Figure 5 The components included in the Ethernet device link monitoring device 500 shown below are described in detail below. Figure 5 The hardware structure of the Ethernet device link monitoring device 402 is described using the Ethernet device link monitoring device 500 as an example. Figure 5 As shown, the Ethernet device link monitoring device 500 includes at least one processor 501, a communication line 502, and at least one communication interface 504, and may also include a memory 503. The processor 501, memory 503, and communication interface 504 can be connected via the communication line 502.

[0053] The processor 501 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present disclosure, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0054] Communication line 502 may include a path for transmitting information between the aforementioned components.

[0055] The communication interface 504 is used to communicate with other devices or communication networks. It can use any transceiver-like device, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc.

[0056] The memory 503 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of including or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0057] In one possible design, the memory 503 can exist independently of the processor 501, meaning the memory 503 can be an external memory of the processor 501. In this case, the memory 503 can be connected to the processor 501 via a communication line 502 to store execution instructions or application code, and its execution is controlled by the processor 501 to implement the Ethernet device link monitoring method provided in the following embodiments of this disclosure. In another possible design, the memory 503 can also be integrated with the processor 501, meaning the memory 503 can be an internal memory of the processor 501. For example, the memory 503 can be a cache, used to temporarily store some data and instruction information.

[0058] As one possible implementation, processor 501 may include one or more CPUs, for example Figure 5 CPU0 and CPU1 in the example. Alternatively, the Ethernet device link monitoring device 500 may include multiple processors, such as CPU0 and CPU1. Figure 5 The processors 501 and 507 are included. Alternatively, the Ethernet device link monitoring device 500 may also include an output device 505 and an input device 506.

[0059] The following provides a detailed description of the Ethernet device link monitoring method provided in the embodiments of this disclosure.

[0060] like Figure 6 As shown, Figure 6 The Ethernet device link monitoring method provided in this disclosure can be applied to, for example... Figure 5 The method in the Ethernet device link monitoring device shown includes the following steps S601-S604, which will be described in detail below.

[0061] S601, Ethernet device link monitoring device obtains event notification OAMPDU message.

[0062] Among them, the event notification OAMPDU message is the event notification OAMPDU message in the EFM message sent by the box-type Ethernet device.

[0063] In one possible implementation, the Ethernet device link monitoring device is a central office device that connects to the SDN controller via the DCN network and to the box-type Ethernet device via an Ethernet optical port, and realizes link layer communication based on the 802.3ah protocol EFM messages.

[0064] S602. The Ethernet device link monitoring device determines the bit error information of the box-type Ethernet device based on the event notification OAMPDU message.

[0065] Among them, the bit error information of the box-type Ethernet device is used to characterize the bit error events of the box-type Ethernet device.

[0066] In one possible implementation, the Ethernet device link monitoring device extracts the Event Notification OAMPDU message from the EFM packet and parses the fields in the Event Notification OAMPDU information to obtain the bit error information of the box-type Ethernet device.

[0067] S603, the Ethernet device link monitoring device converts the bit error information of the box-type Ethernet device into SDN interface packets according to the preset model.

[0068] The preset model is a data model built based on a data modeling language and error information.

[0069] In one possible implementation, the Ethernet device link monitoring device uses the YANG language in the Netconf protocol to model the information of the box-type Ethernet device, and uses the YANG model to convert the bit error information of the box-type Ethernet device in the EFM message into the corresponding field of the SDN interface message.

[0070] For example, the key tree structure of the preset model is as follows:

[0071] +---n oam-notification

[0072] |+--ro event

[0073] | +--ro event-serial-no? uint64

[0074] | +--ro event-type? event-type

[0075] | +--ro object-name? string

[0076] | +--ro mac-address? string

[0077] | +--ro errors-counter? counter64

[0078] | +--ro errors-running-total? counter64

[0079] | +--ro event-running-total counter64

[0080] …

[0081] Among them, oam-notification is the notification module reported by the Ethernet box device, event-serial-no is the serial number of the event notification, which is an unsigned 64-bit integer, event-type is the type of event notification, which is an enumeration type that includes the three event types defined in the event notification OAMPDU message, object-name is the port of the central office OTN device connected to the Ethernet box device, mac-address is the local area network address of the Ethernet box device, errors-counter is the number of error frames within a preset time period, which is a 64-bit integer, errors-running-total is the number of times errors occurred in SDN packets within a preset time period, and event-running-total is the number of bit error events that occurred within a preset time period.

[0082] S604. The Ethernet device link monitoring device sends SDN interface messages to the SDN controller.

[0083] Among them, SDN interface messages are used to characterize bit error events of box-type Ethernet devices.

[0084] In one possible implementation, after receiving an SDN interface message from the target Ethernet device link monitoring device, the SDN controller determines the bit error event of the Ethernet device based on the bit error information of the Ethernet device in the SDN interface message.

[0085] The technical solution provided by the above embodiments can bring at least the following beneficial effects: In this disclosure, the Ethernet device link monitoring device first obtains the event notification OAMPDU message; the event notification OAMPDU message is the event notification OAMPDU message in the EFM message sent by the box-type Ethernet device; the bit error information of the box-type Ethernet device is determined based on the event notification OAMPDU message; the bit error information of the box-type Ethernet device is used to characterize the bit error event of the box-type Ethernet device; the bit error information of the box-type Ethernet device is converted into SDN interface packets according to a preset model; the preset model is a data model constructed based on data modeling language and bit error information; the SDN interface packets are sent to the SDN controller; so that when a bit error event occurs in the Ethernet device link, the SDN controller can promptly detect the bit error event based on the bit error information of the box-type Ethernet device after it has been converted into SDN interface packets. This solves the technical problem that when the central office equipment and the box-type Ethernet device are not from the same manufacturer, the SDN management device can only monitor the port status of the central office equipment connected to it, and cannot monitor the status of the Ethernet device link, making it difficult for the SDN management device to detect bit error events in a timely manner.

[0086] In one possible implementation, the event notification OAMPDU message includes: a source address field, an event type field, and an error information field; combined with Figure 6 ,like Figure 7 As shown, the process by which the Ethernet device link monitoring device determines the bit error information of the box-type Ethernet device based on the event notification OAMPDU message in S602 can be specifically implemented through the following S701-S703, which will be explained in detail below.

[0087] S701, the Ethernet device link monitoring device determines the local area network address of the box-type Ethernet device based on the source address field.

[0088] In one possible implementation, the Ethernet device link monitoring device obtains the local area network information of the box-type Ethernet device based on the source address field of the event notification OAMPDU information in the EFM message.

[0089] S702. The Ethernet device link monitoring device determines the bit error event type of the box-type Ethernet device based on the event type field.

[0090] In one possible implementation, the error event types of the box-type Ethernet device include: bit error exceeding the limit event, frame error exceeding the limit event, and frame error second exceeding the limit event; the Ethernet device link monitoring device determines the fault type of the box-type Ethernet device based on the event type field of the event notification OAMPDU information in the EFM message.

[0091] S703, the Ethernet device link monitoring device determines the number of error frames of the box-type Ethernet device based on the error information field.

[0092] In one possible implementation, the Ethernet device link monitoring device determines the number of erroneous frames of the box-type Ethernet device based on the errors field of the event notification OAMPDU information in the EFM message; determines the number of times SDN packets have errors within a preset time period based on the Error running total field of the event notification OAMPDU information in the EFM message; and determines the number of bit error events that occur within the preset time period based on the event running total field of the event notification OAMPDU information in the EFM message.

[0093] The technical solution provided by the above embodiments can bring at least the following beneficial effects: the Ethernet device link monitoring device obtains the event notification OAMPDU message in the EFM message, and extracts the source address field, event type field, and error information field in the event notification OAMPDU message. Based on the information in the fields, the local area network address of the box Ethernet device, the bit error event type of the box Ethernet device, and the number of error frames of the box Ethernet device are determined.

[0094] In one possible implementation, the SDN interface message includes: a LAN address field, an event type field, and an error count field; combined with... Figure 7 ,like Figure 8 As shown in the figure, the process by which the Ethernet device link monitoring device converts the information of the box-type Ethernet device into SDN interface packets according to the preset model can be specifically implemented through the following S801-S803, which will be explained in detail below.

[0095] S801, the Ethernet device link monitoring device stores the local area network address of the box-type Ethernet device in the local area network address field of the SDN interface message according to the preset model.

[0096] For example, the Ethernet device link monitoring device, based on the data model of the box-type Ethernet device information, saves the local area network address information of the box-type Ethernet device in the Source address field of the event notification OAMPDU message into the mac-address field of the SDN interface message.

[0097] S802. The Ethernet device link monitoring device stores the bit error event type of the box-type Ethernet device in the event type field of the SDN interface message according to the preset model.

[0098] For example, the Ethernet device link monitoring device, based on the data model of the box-type Ethernet device information, stores the bit error event type of the box-type Ethernet device in the event type field of the event notification OAMPDU message in the event-type field of the SDN interface message.

[0099] S803, the Ethernet device link monitoring device, according to a preset model, saves the number of error frames of the box-type Ethernet device in the error count field of the SDN interface message.

[0100] For example, the Ethernet device link monitoring device, based on the data model of the box-type Ethernet device information, saves the number of error frames of the box-type Ethernet device within a preset time period in the error running total field of the event notification OAMPDU message in the errors-counter field of the SDN interface message.

[0101] In one possible implementation, the Ethernet device link monitoring device, based on the data model of the box-type Ethernet device information, saves the number of times SDN packets of the box-type Ethernet device have errors within a preset time period in the errors field of the event notification OAMPDU message into the errors-running-total field of the SDN interface message.

[0102] In one possible implementation, the Ethernet device link monitoring device, based on the data model of the box-type Ethernet device information, saves the number of bit error events occurring within a preset time period of the box-type Ethernet device in the event running total field of the event notification OAMPDU message into the errors-running-total field of the SDN interface message.

[0103] For example, the correspondence between EFM messages and SDN management interface fields is shown in Table 1 below.

[0104] Table 1. Correspondence between EFM messages and SDN management interface fields

[0105] EFM message SDN Management Interface source addr field mac-address event type field event-type errors field errors-counter Error running total errors-running-total event running total event-running-total

[0106] The technical solution provided by the above embodiments can bring at least the following beneficial effects: the Ethernet device link monitoring device saves the box-type Ethernet device information in the EFM message in the corresponding field of the SDN interface message, so that the SDN controller can obtain the box-type Ethernet device information through the received SDN interface message and manage the box-type Ethernet device based on the box-type Ethernet device information.

[0107] One possible implementation is, such as Figure 9 As shown, the process by which the Ethernet device link monitoring device determines the bit error event type of the box-type Ethernet device based on the event type field in S702 can be specifically implemented through the following S901-S903, which will be described in detail below.

[0108] S901. When the event type field is 0x01, the Ethernet device link monitoring device determines the fault type of the box-type Ethernet device as an error rate exceeding the limit event.

[0109] For example, the Ethernet device link monitoring device obtains the event notification OAMPDU message in the EFM message, and determines that the fault type of the box-type Ethernet device is an error rate violation event when the event type field is 0x01.

[0110] S902. When the event type field is 0x02, the Ethernet device link monitoring device determines that the fault type of the box-type Ethernet device is a frame error exceeding the limit event.

[0111] For example, the Ethernet device link monitoring device obtains the event notification OAMPDU message in the EFM message, and determines that the fault type of the box-type Ethernet device is a frame error limit violation event when the event type field is 0x02.

[0112] S903. When the event type field is 0x04, the Ethernet device link monitoring device determines that the fault type of the box-type Ethernet device is a frame error second limit violation event.

[0113] For example, the Ethernet device link monitoring device obtains the event notification OAMPDU message in the EFM message, and determines that the fault type of the box-type Ethernet device is a frame error second limit violation event when the event type field is 0x04.

[0114] In one possible implementation, the event type definition represented by the event type field in this disclosure is shown in Table 2 below.

[0115] The Flags field in Table 2 represents the fault definitions.

[0116]

[0117] The technical solution provided by the above embodiments can bring at least the following beneficial effects: the Ethernet device link monitoring device obtains the event notification OAMPDU message in the EFM message, and determines the event type of the box-type Ethernet device based on the event type field in the event notification OAMPDU message.

[0118] One possible implementation is, such as Figure 10 As shown, after the Ethernet device link monitoring device determines the bit error event type of the box-type Ethernet device based on the event type field in S702, it generates bit error event notification information and sends it to the SDN controller. This process can be implemented in detail in the following S1001-S1002.

[0119] S1001, The Ethernet device link monitoring device generates error event notification information based on the error event type of the box-type Ethernet device.

[0120] In one possible implementation, after determining that the box-type Ethernet device has events such as bit error exceeding the limit, frame error exceeding the limit, and frame error second exceeding the limit, the Ethernet device link monitoring device generates bit error event notification information based on the event type.

[0121] S1002. The Ethernet device link monitoring device sends error event notification information to the SDN controller.

[0122] The technical solution provided by the above embodiments can bring at least the following beneficial effects: the Ethernet device link monitoring device obtains the event notification OAMPDU message in the EFM message, and after determining the event type of the box-type Ethernet device based on the event type field in the event notification OAMPDU message, generates error event notification information according to the event type of the box-type Ethernet device, and sends it to the SDN controller so that the SDN controller can monitor the status of the Ethernet device link.

[0123] In one possible implementation, the process by which the Ethernet device link monitoring device monitors the box-type Ethernet device is as follows: Figure 11 As shown. The process specifically includes steps 1-5, which are described in detail below.

[0124] Step 1: Connect the box-type Ethernet device to the Ethernet device link monitoring device and power it on. After power-on, the box-type Ethernet device sends an EFM message to the Ethernet device link monitoring device.

[0125] Step 2: The Ethernet device link monitoring device receives the EFM message and parses the event notification OAMPDU message in the EFM message.

[0126] Step 3: The Ethernet device link monitoring device determines whether the event type field value is 0x01. If the event type field value is 0x01, it sends a box-type Ethernet device bit error rate exceeding event notification to the SDN controller. Otherwise, proceed to step 4.

[0127] Step 4: The Ethernet device link monitoring device determines whether the event type field value is 0x02. If the event type field value is 0x02, it sends a box-type Ethernet device frame error exceeding the limit event notification to the SDN controller. Otherwise, proceed to step 5.

[0128] Step 5: The Ethernet device link monitoring device determines whether the event type field value is 0x04. If the event type field value is 0x04, it sends a box-type Ethernet device frame error second limit exceeding event notification to the SDN controller. Otherwise, proceed to step 6.

[0129] Step 6: The Ethernet device link monitoring device does not translate and send the event notification OAMPDU message, and directly ends the process.

[0130] As can be seen, the above mainly describes the technical solutions provided by the embodiments of this disclosure from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0131] This disclosure embodiment can divide the Ethernet device link monitoring device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this disclosure embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0132] One possible implementation is, such as Figure 12 , Figure 12 This is a schematic diagram of the structure of an Ethernet device link monitoring device 1200 provided in this disclosure.

[0133] Ethernet device link monitoring device 1200 includes: a communication unit 1201 and a processing unit 1202; the communication unit 1201 is used to acquire Event Notification Operation Maintenance Management Protocol Data Unit (OAMPDU) messages; the Event Notification OAMPDU message is the Event Notification OAMPDU message in the EFM message sent by the box-type Ethernet device; the processing unit 1202 is used to determine the bit error information of the box-type Ethernet device based on the Event Notification OAMPDU message; the bit error information of the box-type Ethernet device is used to characterize the bit error event of the box-type Ethernet device; the processing unit 1202 is used to convert the bit error information of the box-type Ethernet device into SDN interface messages according to a preset model; the preset model is a data model constructed based on a data modeling language and bit error information; the communication unit 1201 is used to send SDN interface messages to the SDN controller; the SDN interface messages are used to characterize the bit error event of the box-type Ethernet device.

[0134] In one possible implementation, the event notification OAMPDU message includes: a source address field, an event type field, and an error information field; the processing unit 1202 is specifically used to: determine the local area network address of the box-type Ethernet device based on the source address field; determine the bit error event type of the box-type Ethernet device based on the event type field; and determine the number of error frames of the box-type Ethernet device based on the error information field.

[0135] In one possible implementation, the SDN interface message includes: a local area network address field, an event type field, and an error count field; the processing unit 1202 is specifically used to: store the local area network address of the box-type Ethernet device in the local area network address field of the SDN interface message according to a preset model; store the bit error event type of the box-type Ethernet device in the event type field of the SDN interface message according to a preset model; and store the number of error frames of the box-type Ethernet device in the error count field of the SDN interface message according to a preset model.

[0136] In one possible implementation, the processing unit 1202 is specifically used to: determine the fault type of the box Ethernet device as a bit error exceeding the limit event when the event type field is 0x01; determine the fault type of the box Ethernet device as a frame error exceeding the limit event when the event type field is 0x02; and determine the fault type of the box Ethernet device as a frame error second exceeding the limit event when the event type field is 0x04.

[0137] In one possible implementation, the processing unit 1202 is further configured to: generate bit error event notification information based on the bit error event type of the box-type Ethernet device; and send the bit error event notification information to the SDN controller.

[0138] This disclosure also provides an Ethernet device link monitoring device, which includes a processor and a memory; wherein the memory is used to store computer execution instructions, and when the Ethernet device link monitoring device is running, the processor executes the computer execution instructions stored in the memory to cause the Ethernet device link monitoring device to perform the Ethernet device link monitoring method described in this disclosure.

[0139] Embodiments of this disclosure provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the Ethernet device link monitoring method described in the above method embodiments.

[0140] Embodiments of this disclosure provide a chip including a processor and a communication interface, the communication interface and the processor being coupled together, the processor being used to run computer programs or instructions to implement the Ethernet device link monitoring method as described in the above method embodiments.

[0141] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disks, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing, or any other form of computer-readable storage medium in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In this embodiment of the disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0142] Since the apparatus, devices, computer-readable storage media, and computer program products in the embodiments of this disclosure can be applied to the above methods, the technical effects they can achieve can also be referred to the above method embodiments. The embodiments of this disclosure will not be repeated here.

[0143] The above descriptions are merely specific embodiments of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions within the technical scope disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A method for monitoring Ethernet device links, characterized in that, include: Obtain event notification operation and maintenance management protocol data unit (OAMPDU) messages; The event notification OAMPDU message is the event notification OAMPDU message in the EFM message sent by the box-type Ethernet device; The error information of the box-type Ethernet device is determined based on the event notification OAMPDU message; the error information of the box-type Ethernet device is used to characterize the error event of the box-type Ethernet device; The error information of the box-type Ethernet device is converted into SDN interface packets according to the preset model; The preset model is a data model built based on a data modeling language and error information; The SDN interface message is sent to the SDN controller; the SDN interface message is used to characterize the bit error event of the box-type Ethernet device.

2. The method according to claim 1, characterized in that, The event notification OAMPDU message includes: a source address field, an event type field, and an error information field; determining the bit error information of the box-type Ethernet device based on the event notification OAMPDU message includes: The local area network address of the box-type Ethernet device is determined based on the source address field. The error event type of the box-type Ethernet device is determined based on the event type field. The number of error frames of the cassette Ethernet device is determined based on the error information field.

3. The method according to claim 2, characterized in that, The SDN interface packet includes: a LAN address field, an event type field, and an error count field; the step of converting the bit error information of the box-type Ethernet device into an SDN interface packet according to a preset model includes: According to the preset model, the local area network address of the box-type Ethernet device is stored in the local area network address field of the SDN interface packet; According to the preset model, the bit error event type of the box-type Ethernet device is stored in the event type field of the SDN interface message; According to the preset model, the number of error frames of the box-type Ethernet device is stored in the error count field of the SDN interface message.

4. The method according to claim 2, characterized in that, Determining the error event type of the box-type Ethernet device based on the event type field includes: When the event type field is 0x01, the fault type of the box-type Ethernet device is determined to be an error rate violation event; When the event type field is 0x02, the fault type of the box-type Ethernet device is determined to be a frame error exceeding the limit event; When the event type field is 0x04, the fault type of the box-type Ethernet device is determined to be a frame error second exceeding the limit event.

5. The method according to claim 4, characterized in that, The method further includes: Generate bit error event notification information based on the bit error event types of the box-type Ethernet device; Send the bit error event notification information to the SDN controller.

6. An Ethernet device link monitoring device, characterized in that, include: Communication unit and processing unit; The communication unit is used to acquire Event Notification Operation Maintenance Management Protocol Data Unit (OAMPDU) messages; The event notification OAMPDU message is the event notification OAMPDU message in the EFM message sent by the box-type Ethernet device; The processing unit is used to determine the bit error information of the box-type Ethernet device based on the event notification OAMPDU message; The bit error information of the box-type Ethernet device is used to characterize the bit error events of the box-type Ethernet device; The processing unit is used to convert the bit error information of the box-type Ethernet device into SDN interface packets according to a preset model. The preset model is a data model built based on a data modeling language and error information; The communication unit is used to send the SDN interface message to the SDN controller; The SDN interface message is used to characterize the bit error events of the box-type Ethernet device.

7. The apparatus according to claim 6, characterized in that, The event notification OAMPDU message includes: a source address field, an event type field, and an error information field; the processing unit is specifically used for: The local area network address of the box-type Ethernet device is determined based on the source address field. The error event type of the box-type Ethernet device is determined based on the event type field. The number of error frames of the cassette Ethernet device is determined based on the error information field.

8. The apparatus according to claim 7, characterized in that, The SDN interface message includes: a local area network address field, an event type field, and an error count field; the processing unit is specifically used for: According to the preset model, the local area network address of the box-type Ethernet device is stored in the local area network address field of the SDN interface packet; According to the preset model, the bit error event type of the box-type Ethernet device is stored in the event type field of the SDN interface message; According to the preset model, the number of error frames of the box-type Ethernet device is stored in the error count field of the SDN interface message.

9. An Ethernet device link monitoring device, characterized in that, include: A processor and a memory; wherein the memory is used to store computer execution instructions, and when the Ethernet device link monitoring device is running, the processor executes the computer execution instructions stored in the memory to cause the Ethernet device link monitoring device to perform the Ethernet device link monitoring method according to any one of claims 1-5.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed by the processor of the Ethernet device link monitoring device, cause the Ethernet device link monitoring device to perform the Ethernet device link monitoring method according to any one of claims 1-5.

Images