Ethernet device management method and apparatus, and storage medium

Abstract

The present disclosure provides an Ethernet device management method and device and storage medium, and relates to the technical field of communication, and solves the technical problem that an SDN management and control device cannot manage a box-type Ethernet device in the case that a local device and the box-type Ethernet device are not from the same device manufacturer in the related art. The method comprises the following steps: obtaining protocol data unit OAMPDU information in an EFM message sent by a box-type Ethernet device to be managed; converting information of the box-type Ethernet device to be managed 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 instruct the SDN controller to manage the box-type Ethernet device to be managed based on the SDN interface message. The present disclosure is used in the scenario of Ethernet device management.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to an Ethernet device management 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 through the protocol messages.

[0003] However, there are limitations to managing box-type Ethernet devices using the above method. Specifically, the central office equipment and the box-type Ethernet device need to be from the same manufacturer. If the central office equipment and the box-type Ethernet device are not from the same manufacturer, the Software Defined Network (SDN) management equipment cannot manage the box-type Ethernet device. Summary of the Invention

[0004] This disclosure provides an Ethernet device management method, apparatus, and storage medium, which solves the technical problem in the related art that software-defined networking (SDN) management cannot manage the box-type Ethernet device when the central office equipment and the box-type Ethernet device are not from the same equipment manufacturer.

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

[0006] Firstly, a method for managing Ethernet devices is provided. This method includes: obtaining Protocol Data Unit (OAMPDU) information from an EFM message sent by a managed Ethernet box; identifying the managed Ethernet box as such; determining the managed Ethernet box information based on the OAMPDU information; the managed Ethernet box information including: the fault type of the managed Ethernet box, the local area network address of the managed Ethernet box, the vendor name of the managed Ethernet box, and the device type of the managed Ethernet box; converting the managed Ethernet box information into SDN interface messages according to a preset model; the preset model being a data model constructed based on a data modeling language and the Ethernet box information; and sending SDN interface messages to an SDN controller; the SDN interface messages instructing the SDN controller to manage the managed Ethernet box based on the SDN interface messages.

[0007] In conjunction with the first aspect mentioned above, in one possible implementation, the OAMPDU information includes: an identification field, a source address field, and a vendor information field; the method specifically includes: determining the fault type of the managed box-type Ethernet device based on the identification field; determining the local area network address of the managed box-type Ethernet device based on the source address field; and determining the vendor name and device type of the managed box-type Ethernet device based on the vendor information field.

[0008] In conjunction with the first aspect mentioned above, in one possible implementation, the SDN interface message includes: a LAN address field, a vendor information field, and a device type field; the method specifically includes: according to a preset model, storing the LAN address of the managed box-type Ethernet device in the LAN address field of the SDN interface message; according to a preset model, storing the vendor name of the managed box-type Ethernet device in the vendor information field of the SDN interface message; and according to a preset model, storing the device type of the managed box-type Ethernet device in the device type field of the SDN interface message.

[0009] In conjunction with the first aspect mentioned above, in one possible implementation, the method specifically includes: when the identifier field is Bit0, determining that the fault type of the managed box-type Ethernet device is optical port missing; when the identifier field is Bit1, determining that the fault type of the managed box-type Ethernet device is remote power failure; and when the identifier field is Bit2, determining that the fault type of the managed box-type Ethernet device is electrical port disconnection.

[0010] In conjunction with the first aspect above, in one possible implementation, the method further includes: generating alarm information based on the fault type of the managed box-type Ethernet device when it is determined that there is a fault in the managed box-type Ethernet device; and sending the alarm information to the SDN controller.

[0011] Secondly, an Ethernet device management apparatus is provided, comprising: a communication unit and a processing unit; the communication unit is used to acquire Protocol Data Unit (OAMPDU) information from an EFM message sent by a managed box-type Ethernet device; the managed box-type Ethernet device is identified as such; the processing unit is used to determine information about the managed box-type Ethernet device based on the OAMPDU information; the information about the managed box-type Ethernet device includes: the fault type of the managed box-type Ethernet device, the local area network address of the managed box-type Ethernet device, the vendor name of the managed box-type Ethernet device, and the device type of the managed box-type Ethernet device; the processing unit is used to convert the information of the managed 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 information of the box-type Ethernet device; the communication unit is used to send SDN interface messages to an SDN controller; the SDN interface messages are used to instruct the SDN controller to manage the managed box-type Ethernet device based on the SDN interface messages.

[0012] In conjunction with the second aspect above, in one possible implementation, the OAMPDU information includes: an identification field, a source address field, and a vendor information field; and a processing unit specifically used for: determining the fault type of the managed box-type Ethernet device based on the identification field; determining the local area network address of the managed box-type Ethernet device based on the source address field; and determining the vendor name and device type of the managed box-type Ethernet device based on the vendor information field.

[0013] In conjunction with the second aspect above, in one possible implementation, the SDN interface message includes: a LAN address field, a vendor information field, and a device type field; the processing unit is specifically used to: save the LAN address of the managed box-type Ethernet device in the LAN address field of the SDN interface message according to a preset model; save the vendor name of the managed box-type Ethernet device in the vendor information field of the SDN interface message according to a preset model; and save the device type of the managed box-type Ethernet device in the device type field of the SDN interface message 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 managed box-type Ethernet device as optical port missing when the identifier field is Bit0; determine the fault type of the managed box-type Ethernet device as remote power failure when the identifier field is Bit1; and determine the fault type of the managed box-type Ethernet device as electrical port disconnection when the identifier field is Bit2.

[0015] In conjunction with the second aspect above, in one possible implementation, the processing unit is further configured to: generate alarm information based on the fault type of the managed box-type Ethernet device when it is determined that there is a fault in the managed box-type Ethernet device; and instruct the communication unit to send the alarm information to the SDN controller.

[0016] Thirdly, an Ethernet device management apparatus is provided, comprising: a processor and a memory; wherein the memory is used to store computer execution instructions, and when the Ethernet device management apparatus is running, the processor executes the computer execution instructions stored in the memory to cause the Ethernet device management apparatus to perform the Ethernet device management method as described in the first aspect 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 management device, cause the Ethernet device management device to perform the Ethernet device management 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 management method as described in the first aspect above and any possible implementation thereof.

[0019] In this disclosure, the name of the aforementioned Ethernet device management 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 management device in this disclosure first obtains the OAMPDU information from the EFM message sent by the managed box-type Ethernet device; the managed box-type Ethernet device is identified as such; the managed box-type Ethernet device information is determined based on the OAMPDU information; the managed box-type Ethernet device information includes: the fault type of the managed box-type Ethernet device, the local area network address of the managed box-type Ethernet device, the vendor name of the managed box-type Ethernet device, and the device type of the managed box-type Ethernet device; the managed box-type Ethernet device information is converted 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 box-type Ethernet device information; the SDN interface messages are sent to the SDN controller; so that the SDN controller manages the managed box-type Ethernet device based on the managed box-type Ethernet device information converted into SDN interface messages; thereby solving the technical problem that the SDN controller cannot manage the box-type Ethernet device when the central office equipment and the box-type Ethernet device are not from the same equipment manufacturer. 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 This is a schematic diagram of the structure of an information OAMPDU provided in an embodiment of the present 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 management system provided in an embodiment of the present disclosure;

[0026] Figure 5 A schematic diagram of the hardware structure of an Ethernet device management device provided in an embodiment of this disclosure;

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

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

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

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

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

[0032] Figure 11 This is a schematic diagram illustrating the process of an Ethernet device management device managing 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 management device provided in an embodiment of the present disclosure. Detailed Implementation

[0034] The following description, in conjunction with the accompanying drawings, details an Ethernet device management 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] The OAMPDU (Local Info Type Length and Value) is used for link connectivity detection and includes a Local info TLV field and a Remote info TLV field. During the handshake phase, the OAM entity periodically sends OAMPDUs at preset time intervals to detect link connectivity. The OAMPDU structure is as follows: Figure 2As shown; Event Notification OAMPDU is used for link monitoring, including: Sequence (seq) field and Link Event TLV field. 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, including: Loopback Command field. The remote loopback function is enabled or disabled 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 structures of data 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 of the managed box-type Ethernet devices in EFM messages into corresponding fields in SDN interface messages 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 3 As 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 equipment manufacturer's proprietary protocol. OTN equipment converts management signaling into protocol messages, which are then used to manage the box-type Ethernet devices. However, this method has limitations: the central office equipment and the box-type Ethernet device must be from the same manufacturer. If the central office equipment and the box-type Ethernet device are not from the same manufacturer, the SDN management equipment cannot manage the box-type Ethernet device.

[0049] To address the aforementioned technical issues, this disclosure provides an Ethernet device management method, apparatus, and storage medium to resolve the technical problem that SDN control equipment cannot manage the box-type Ethernet device when the central office equipment and the box-type Ethernet device are from different manufacturers. The method includes: obtaining OAMPDU information from the EFM message sent by the managed Ethernet box device; identifying the managed Ethernet box device as such; determining the managed Ethernet box device information based on the OAMPDU information; the managed Ethernet box device information including: the fault type of the managed Ethernet box device, the local area network address of the managed Ethernet box device, the vendor name of the managed Ethernet box device, and the device type of the managed Ethernet box device; converting the managed Ethernet box device information 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 Ethernet box device information; sending SDN interface messages to the SDN controller; so that the SDN controller can manage the managed Ethernet box device based on the managed Ethernet box device information converted into SDN interface messages; thereby solving the technical problem that the SDN controller cannot manage the Ethernet box device when the central office equipment and the Ethernet box device are not from the same equipment manufacturer.

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

[0051] The device 401 sends EFM messages to the Ethernet device management device 402, which in turn obtains OAMPDU information from the EFM messages sent by the managed device. The managed device is identified as the EFM device to be managed. Based on the OAMPDU information, the managed device information is determined. This information includes: the fault type, LAN address, vendor name, and device type of the managed device. The managed device information is then converted into SDN interface messages according to a preset model, which is a data model constructed based on a data modeling language and the managed device information. Finally, an SDN interface message is sent to the SDN controller 403, enabling the SDN controller 403 to manage the managed device based on the converted SDN interface message information. The SDN controller 403 is used to manage managed Ethernet box devices based on the information of the managed Ethernet box devices after they have been converted into SDN interface messages.

[0052] In one possible implementation, the hardware structure of the Ethernet device management device 402 in the aforementioned Ethernet device management system 400 includes: Figure 5 The components included in the Ethernet device management device 500 shown below are denoted as follows: Figure 5 The hardware structure of Ethernet device management device 402 is illustrated using Ethernet device management device 500 as an example. Figure 5 As shown, the Ethernet device management 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 are 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 management 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 management device 500 may include multiple processors, such as CPU0 and CPU1. Figure 5 The processors 501 and 507 are included. Alternatively, the Ethernet device management 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 management method provided in the embodiments of this disclosure.

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

[0061] S601, The Ethernet device management device obtains the Protocol Data Unit (OAMPDU) information from the EFM message sent by the managed box-type Ethernet device.

[0062] Among them, the managed box-type Ethernet device is the managed box-type Ethernet device.

[0063] In one possible implementation, the Ethernet device management 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 implements link layer communication based on 802.3ah protocol EFM messages.

[0064] S602. The Ethernet device management device determines the information of the box-type Ethernet device to be managed based on the OAMPDU information.

[0065] The information for the managed Ethernet box device includes: the fault type of the managed Ethernet box device, the local area network address of the managed Ethernet box device, the vendor name of the managed Ethernet box device, and the device type of the managed Ethernet box device.

[0066] In one possible implementation, the Ethernet device management device extracts the OAMPDU information from the EFM message and parses the fields in the OAMPDU information to obtain the fault type of the managed box-type Ethernet device, the local area network address of the managed box-type Ethernet device, the vendor name of the managed box-type Ethernet device, and the device type of the managed box-type Ethernet device.

[0067] S603. The Ethernet device management device converts the information of the managed box-type Ethernet device into SDN interface messages according to the preset model.

[0068] The preset model is a data model built based on a data modeling language and information about the box-type Ethernet device.

[0069] In one possible implementation, the Ethernet device management 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 information of the box-type Ethernet device to be managed in the EFM message into the corresponding fields of the SDN interface message.

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

[0071]

[0072] Where ptp is the port connecting the central office equipment and the box-type Ethernet device, name is the port name of the central office equipment, mac-address is the MAC address of the box-type Ethernet device, vendor-info is the abbreviation of the device manufacturer's name, and device-type is the device type identifier of the box-type Ethernet device.

[0073] S604. The Ethernet device management device sends an SDN interface message to the SDN controller.

[0074] Among them, the SDN interface message is used to instruct the SDN controller to manage the managed box-type Ethernet device based on the SDN interface message.

[0075] In one possible implementation, after receiving an SDN interface message from the target Ethernet device management device, the SDN controller manages the Ethernet device to be managed based on the port on which the central office device and the Ethernet box to be managed are connected, the port name of the central office device, the MAC address of the Ethernet box to be managed, the abbreviation of the manufacturer's name of the Ethernet box to be managed, and the device type identifier of the Ethernet box to be managed, as contained in the SDN interface message.

[0076] The technical solution provided by the above embodiments can bring at least the following beneficial effects: The Ethernet device management device first obtains the OAMPDU information in the EFM message sent by the managed box Ethernet device; the managed box Ethernet device is the managed box Ethernet device; the managed box Ethernet device information is determined based on the OAMPDU information; the managed box Ethernet device information includes: the fault type of the managed box Ethernet device, the local area network address of the managed box Ethernet device, the vendor name of the managed box Ethernet device, and the device type of the managed box Ethernet device; the managed box Ethernet device information is converted 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 box Ethernet device information; the SDN interface messages are sent to the SDN controller; so that the SDN controller can manage the managed box Ethernet device based on the managed box Ethernet device information after it has been converted into SDN interface messages; thereby solving the technical problem that the SDN controller cannot manage the box Ethernet device when the central office equipment and the box Ethernet device are not from the same equipment manufacturer.

[0077] In one possible implementation, the OAMPDU information includes: an identifier field, a source address field, and a supplier information field, combined with... Figure 6 ,like Figure 7 As shown, the process by which the Ethernet device management device determines the information of the managed box-type Ethernet device based on the OAMPDU information in S602 can be specifically implemented through the following S701-S703, which will be explained in detail below.

[0078] S701, The Ethernet device management device determines the fault type of the managed box-type Ethernet device based on the identification field.

[0079] In one possible implementation, the fault types of the managed box-type Ethernet device include: electrical port connection failure, remote power failure, and optical port loss; the Ethernet device management device determines the fault type of the managed box-type Ethernet device based on the Flags field in the EFM message.

[0080] S702, The Ethernet device management device determines the local area network address of the managed box-type Ethernet device based on the source address field.

[0081] In one possible implementation, the Ethernet device management device obtains the local area network information of the managed box-type Ethernet device based on the source address in the EFM message.

[0082] S703. The Ethernet device management device determines the supplier name and device type of the managed box-type Ethernet device based on the supplier information field.

[0083] In one possible implementation, the Vendor Specific Info field in the EFM message is 4 bytes of data. The first two bytes are the abbreviation of the manufacturer's name, and the last two bytes are the Ethernet device type identifier. Based on the Vendor Specific Info field in the EFM message, the Ethernet device management device determines the vendor name and device type of the managed box-type Ethernet device.

[0084] The technical solution provided by the above embodiments can bring at least the following beneficial effects: the Ethernet device management device obtains the OAMPDU information in the EFM message, and extracts the identification field, source address field, and vendor information field in the OAMPDU information. Based on the information in the fields, it determines the fault type of the managed box Ethernet device, the local area network address of the managed box Ethernet device, the vendor name of the managed box Ethernet device, and the device type of the managed box Ethernet device.

[0085] In one possible implementation, the SDN interface message includes: a LAN address field, a vendor information field, and a device type field; combined with... Figure 7 ,like Figure 8 As shown in the figure, the process by which the Ethernet device management device converts the information of the managed 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 described in detail below.

[0086] S801, the Ethernet device management device stores the LAN address of the managed box-type Ethernet device in the LAN address field of the SDN interface message according to the preset model.

[0087] For example, the Ethernet device management device, based on a preset model, saves the LAN address information of the managed box-type Ethernet device in the Source addr field of the EFM message into the mac-address field of the SDN interface message.

[0088] S802. The Ethernet device management device stores the vendor name of the managed box-type Ethernet device in the vendor information field of the SDN interface message according to the preset model.

[0089] For example, the Ethernet device management device, according to a preset model, stores the vendor name of the managed box-type Ethernet device in the first two bytes of the Vendor Specific Info field in the EFM message in the vendor-info field of the SDN interface message.

[0090] S803. The Ethernet device management device stores the device type of the managed box-type Ethernet device in the device type field of the SDN interface message according to the preset model.

[0091] For example, the Ethernet device management device, based on a preset model, stores the device type of the managed box-type Ethernet device in the last two bytes of the Vendor Specific Info field in the EFM message in the device-type field of the SDN interface message.

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

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

[0094]

[0095]

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

[0097] One possible implementation is, such as Figure 9As shown, the process by which the Ethernet device management device determines the fault type of the managed box-type Ethernet device based on the identification field in S701 can be specifically implemented through the following S901-S903, which will be explained in detail below.

[0098] S901. When the identification field is Bit0, the Ethernet device management device determines that the fault type of the managed box-type Ethernet device is optical port missing.

[0099] For example, the Ethernet device management device obtains the OAMPDU information in the EFM message and determines that the fault type of the managed box-type Ethernet device is optical port missing when the Flags field is Bit 0.

[0100] S902. When the identification field is Bit1, the Ethernet device management device determines that the fault type of the managed box-type Ethernet device is remote power failure.

[0101] For example, the Ethernet device management device obtains the OAMPDU information in the EFM message and determines that the fault type of the managed box-type Ethernet device is remote power failure when the Flags field is Bit1.

[0102] S903. When the identification field is Bit2, the Ethernet device management device determines that the fault type of the managed box-type Ethernet device is electrical port disconnection.

[0103] For example, the Ethernet device management device obtains the OAMPDU information in the EFM message and determines that the fault type of the managed box-type Ethernet device is electrical port disconnection when the Flags field is Bit2.

[0104] In one possible implementation, the fault definition represented by the Flags field in this disclosure is shown in Table 2 below.

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

[0106]

[0107] The technical solution provided by the above embodiments can bring at least the following beneficial effects: the Ethernet device management device obtains the OAMPDU information in the EFM message and determines the fault type of the managed box-type Ethernet device based on the identification field in the OAMPDU information.

[0108] One possible implementation is, such as Figure 10 As shown, after the Ethernet device management device determines the fault type of the managed box-type Ethernet device based on the identification field in the above S701 process, it generates alarm information and sends it to the SDN controller. This process can be implemented in detail in the following S1001-S1002.

[0109] S1001. When the Ethernet device management device determines that there is a fault in the managed box-type Ethernet device, it generates alarm information based on the fault type of the managed box-type Ethernet device.

[0110] In one possible implementation, after determining that the managed box-type Ethernet device has faults such as disconnected electrical port, remote power failure, or missing optical port, the Ethernet device management device generates alarm information based on the fault type.

[0111] S1002, The Ethernet device management device sends alarm information to the SDN controller.

[0112] The technical solution provided by the above embodiments can bring at least the following beneficial effects: the Ethernet device management device obtains the OAMPDU information in the EFM message, and after determining the fault type of the managed box-type Ethernet device based on the identification field in the OAMPDU information, generates alarm information according to the fault type of the box-type Ethernet device and sends it to the SDN controller, so that the SDN controller can manage the managed box-type Ethernet device based on the alarm information.

[0113] In one possible implementation, the process by which the Ethernet device management device manages 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.

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

[0115] Step 2: The Ethernet device management device receives the EFM message and determines whether there is a fault report based on the Flags field. If there is no fault, proceed to step 3; if there is a fault, proceed to step 4.

[0116] Step 3: The Ethernet device management device parses the box-type Ethernet device information in the Source addr field and vendor specific info field, and converts the box-type Ethernet device information into SDN interface packets through a preset model, sends the SDN interface packets to the SDN controller, and ends the process.

[0117] Step 4: The Ethernet device management device determines whether the fault type is a device power failure. If the fault type is a remote power failure, proceed to step 5; otherwise, proceed to step 6.

[0118] Step 5: The Ethernet device management device generates a remote device power failure alarm message and sends it to the SDN controller, ending the process;

[0119] Step 6: The Ethernet device management device generates corresponding alarm information based on the fault type in the Flags field and sends it to the SDN controller, thus ending the process.

[0120] 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.

[0121] This disclosure embodiment can divide the Ethernet device management 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.

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

[0123] Ethernet device management device 1200 includes: a communication unit 1201 and a processing unit 1202; the communication unit 1201 is used to acquire Protocol Data Unit (OAMPDU) information from the EFM message sent by the managed box-type Ethernet device; the managed box-type Ethernet device is the managed box-type Ethernet device; the processing unit 1202 is used to determine the managed box-type Ethernet device information based on the OAMPDU information; the managed box-type Ethernet device information includes: the fault type of the managed box-type Ethernet device, the local area network address of the managed box-type Ethernet device, the vendor name of the managed box-type Ethernet device, and the device type of the managed box-type Ethernet device; the processing unit 1202 is used to convert the information of the managed 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 box-type Ethernet device information; the communication unit 1201 is used to send SDN interface messages to the SDN controller; the SDN interface messages are used to instruct the SDN controller to manage the managed box-type Ethernet device based on the SDN interface messages.

[0124] In one possible implementation, the OAMPDU information includes: an identification field, a source address field, and a vendor information field; the processing unit 1202 is specifically used to: determine the fault type of the managed box-type Ethernet device based on the identification field; determine the local area network address of the managed box-type Ethernet device based on the source address field; and determine the vendor name and device type of the managed box-type Ethernet device based on the vendor information field.

[0125] In one possible implementation, the SDN interface message includes: a LAN address field, a vendor information field, and a device type field; the processing unit 1202 is specifically used to: save the LAN address of the managed box-type Ethernet device in the LAN address field of the SDN interface message according to a preset model; save the vendor name of the managed box-type Ethernet device in the vendor information field of the SDN interface message according to a preset model; and save the device type of the managed box-type Ethernet device in the device type field of the SDN interface message according to a preset model.

[0126] In one possible implementation, the processing unit 1202 is specifically configured to: determine the fault type of the managed box-type Ethernet device as optical port missing when the identifier field is Bit0; determine the fault type of the managed box-type Ethernet device as remote power failure when the identifier field is Bit1; and determine the fault type of the managed box-type Ethernet device as electrical port disconnection when the identifier field is Bit2.

[0127] In one possible implementation, the processing unit 1202 is further configured to: generate alarm information based on the fault type of the managed box-type Ethernet device when it is determined that there is a fault in the managed box-type Ethernet device; and instruct the communication unit 1201 to send the alarm information to the SDN controller.

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

[0129] 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 management method described in the above method embodiments.

[0130] 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 management method as described in the above method embodiments.

[0131] 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.

[0132] 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.

[0133] 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 managing Ethernet devices, characterized in that, include: Obtain the Protocol Data Unit (OAMPDU) information from the first-mile Ethernet EFM message sent by the managed box-type Ethernet device; The OAMPDU information includes: an identifier field, a source address field, and a supplier information field; The information of the managed box-type Ethernet device is determined based on the OAMPDU information. The information of the managed box-type Ethernet device includes: the fault type of the managed box-type Ethernet device, the local area network address of the managed box-type Ethernet device, the vendor name of the managed box-type Ethernet device, and the device type of the managed box-type Ethernet device. The step of determining the information of the managed box-type Ethernet device based on the OAMPDU information includes: The fault type of the managed box-type Ethernet device is determined based on the identification field; The local area network address of the managed box-type Ethernet device is determined based on the source address field. The supplier name and device type of the managed box-type Ethernet device are determined based on the supplier information field. The step of determining the fault type of the managed box-type Ethernet device based on the identification field includes: When the identifier field is Bit0, the fault type of the managed box-type Ethernet device is determined to be optical port missing; When the identifier field is Bit1, the fault type of the managed box-type Ethernet device is determined to be remote power failure; When the identifier field is Bit2, the fault type of the managed box-type Ethernet device is determined to be a disconnected electrical port connection; The information of the managed Ethernet box device is converted into a Software Defined Networking (SDN) interface packet according to a preset model; the preset model is a data model built based on a data modeling language and the Ethernet box device information; the SDN interface packet includes: the local area network address field, the vendor information field, and the device type field; The step of converting the information of the managed box-type Ethernet device into SDN interface packets according to a preset model includes: According to the preset model, the local area network address of the managed box-type Ethernet device is stored in the local area network address field of the software-defined networking (SDN) interface packet; According to the preset model, the vendor name of the managed box-type Ethernet device is stored in the vendor information field of the SDN interface message; According to the preset model, the device type of the managed box-type Ethernet device is stored in the device type field of the SDN interface message; The SDN interface message is sent to the SDN controller; the SDN interface message is used to instruct the SDN controller to manage the managed box-type Ethernet device based on the SDN interface message.

2. The method according to claim 1, characterized in that, The method further includes: If it is determined that the managed box-type Ethernet device is faulty, an alarm message is generated based on the fault type of the managed box-type Ethernet device; The alarm information is sent to the SDN controller.

3. An Ethernet device management device, characterized in that, include: Communication unit and processing unit; The communication unit is used to obtain the Protocol Data Unit (OAMPDU) information in the EFM message sent by the managed box-type Ethernet device. The OAMPDU information includes: an identifier field, a source address field, and a supplier information field; The processing unit is used to determine the information of the managed box-type Ethernet device based on the OAMPDU information; the information of the managed box-type Ethernet device includes: the fault type of the managed box-type Ethernet device, the local area network address of the managed box-type Ethernet device, the vendor name of the managed box-type Ethernet device, and the device type of the managed box-type Ethernet device. Specifically, the processing unit is used for: The fault type of the managed box-type Ethernet device is determined based on the identification field; The local area network address of the managed box-type Ethernet device is determined based on the source address field. The supplier name and device type of the managed box-type Ethernet device are determined based on the supplier information field. The processing unit is further specifically used for: When the identifier field is Bit0, the fault type of the managed box-type Ethernet device is determined to be optical port missing; When the identifier field is Bit1, the fault type of the managed box-type Ethernet device is determined to be remote power failure; When the identifier field is Bit2, the fault type of the managed box-type Ethernet device is determined to be a disconnected electrical port connection; The processing unit is further configured to convert the information of the managed box-type Ethernet device into SDN interface packets according to a preset model; the preset model is a data model constructed based on a data modeling language and the box-type Ethernet device information; the SDN interface packet includes: a local area network address field, a vendor information field, and a device type field; The processing unit is further specifically used for: According to the preset model, the local area network address of the managed box-type Ethernet device is stored in the local area network address field of the SDN interface packet; According to the preset model, the vendor name of the managed box-type Ethernet device is stored in the vendor information field of the SDN interface message; According to the preset model, the device type of the managed box-type Ethernet device is stored in the device type field of the SDN interface message; The communication unit is used to send the SDN interface message to the SDN controller; the SDN interface message is used to instruct the SDN controller to manage the managed box-type Ethernet device based on the SDN interface message.

4. An Ethernet device management 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 management device is running, the processor executes the computer execution instructions stored in the memory to cause the Ethernet device management device to perform the Ethernet device management method according to any one of claims 1-2.

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

Images