WO2019029286A1 - 一种通信方法、设备及存储介质 - Google Patents

一种通信方法、设备及存储介质 Download PDF

Info

Publication number
WO2019029286A1
WO2019029286A1 PCT/CN2018/092947 CN2018092947W WO2019029286A1 WO 2019029286 A1 WO2019029286 A1 WO 2019029286A1 CN 2018092947 W CN2018092947 W CN 2018092947W WO 2019029286 A1 WO2019029286 A1 WO 2019029286A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault information
port
type
information
communication device
Prior art date
Application number
PCT/CN2018/092947
Other languages
English (en)
French (fr)
Inventor
张小俊
陈启昌
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18843735.4A priority Critical patent/EP3661125B1/en
Priority to KR1020207006748A priority patent/KR102364803B1/ko
Priority to JP2020507659A priority patent/JP7026776B2/ja
Publication of WO2019029286A1 publication Critical patent/WO2019029286A1/zh
Priority to US16/784,741 priority patent/US11296924B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/14—Monitoring arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0681—Configuration of triggering conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0057—Operations, administration and maintenance [OAM]
    • H04J2203/006—Fault tolerance and recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet

Definitions

  • the present application relates to the field of communications, and in particular, to a communication method, device, and storage medium.
  • Standard Ethernet The 802.3 standard Ethernet (StdE) standard defined by the 802.3 working group of the Institute of Electrical and Electronics Engineers (IEEE) is widely cited in the industry. Standard Ethernet is greatly welcomed by manufacturers because of its simple principle, easy implementation and low price. However, with the development of technology, the difference in bandwidth particles is getting larger and larger, and the deviation between the ports of standard Ethernet and the actual application requirements is also increasing. A situation that is likely to occur is that the mainstream application requires bandwidth that does not belong to any existing Ethernet standard rate. For example, if a 50Gb/s service uses 100GE ports to carry the waste of resources, the 200Gb/s service is currently available. There are no corresponding Ethernet standard granules that can be carried.
  • FlexE Flexible Ethernet
  • MAC medium access control
  • FlexE can support the following functions: Binding, multiple Ethernet ports Bind as a link group to support medium access control (MAC) services at a rate greater than a single Ethernet port; sub-rates, by assigning time slots to support traffic, the rate is less than the link group bandwidth or less than a single Ethernet port Bandwidth MAC service; channelization, which supports simultaneous transmission of multiple MAC services in a link group by allocating time slots for services, for example, supporting simultaneous transmission of one 150G and two 25G MAC services in a 2x100GE link group.
  • MAC medium access control
  • FIG. 1 is a schematic diagram of a possible communication system architecture in the prior art.
  • the first Ethernet device 1101 and the second Ethernet device 1201 are included, where the first Ethernet device 1101 includes media related.
  • Medium Dependent Interface (MDI) 1102 (the description is clearly written as MEDIUM1102), physical layer, Media Independent Interface (MII) 1107, Reconciliation Sublayer (RS) 1108, media access control ( Medium Access Control, MAC) layer 1109 and upper layer 1110.
  • MDI Medium Dependent Interface
  • MII Media Independent Interface
  • RS Reconciliation Sublayer
  • the physical layer of the first Ethernet device 1101 may include a Physical Medium Dependent (PMD) 1104, a Physical Medium Attachment (PMA) 1105, and a Physical Coding Sublayer (Physical Coding Sublayer). , PCS) 1106.
  • PMD Physical Medium Dependent
  • PMA Physical Medium Attachment
  • PCS Physical Coding Sublayer
  • the upper layer 1110 may include an Internet Protocol (IP) layer, a Transmission Control Protocol (TCP) layer, and the like.
  • the second Ethernet device 1201 includes a Medium Dependent Interface (MDI) 1202 (the description is clearly written as MEDIUM 1202), a physical layer, an MII 1207, an RS 1208, a MAC layer 1209, and an Upper layer 1210.
  • MDI Medium Dependent Interface
  • the physical layer of the second Ethernet device 1201 may include a PMD 1204, a PMA 1205, and a PCS 1206.
  • the upper layer 1210 may include an IP layer, a TCP layer, and the like.
  • Section 81.3.4 of the IEEE 802.3 standard document defines local fault information (LF) and remote fault information (40) in the 40GE/100GE standard Ethernet protocol.
  • the local fault information can refer to the remote RS and local.
  • the faults between the RSs may be Faults detected between the remote RS and the local RS.
  • the remote fault information may be RF signal originated at RS when RS detected LF.
  • the mechanism for the local RS to negotiate the link failure status with the remote RS sublayer and the transmission and processing mechanism of the 64b/66bit Block based on LF and RF are specified in the protocol.
  • the link from the second Ethernet device 1201 to the first Ethernet device 1101 fails, and the physical layer (such as the PMD 1104) in the first Ethernet device 1101 detects a link failure, PMD 1104,
  • the PMA1105 or PCS1106 will generate the LF and send it up to the upper functional unit until the RS1108 receives the LF. If the RS1108 detects the LF sent by the PCS 1106 through the MII1107 port, the upper MAC data stream is stopped from being inserted into the PCS 1106, and the RF is continuously inserted into the PCS 1106 and sent to the second Ethernet device 1201. If the transmission link of the first Ethernet device 1101 to the second Ethernet device 1201 is intact, the RF may arrive at the second Ethernet device 1201.
  • the RS1208 of the second Ethernet device 1201 detects the RF, stops the upper layer MAC data stream from being inserted into the PCS1206, and continuously inserts the Idle control block stream to the PCS1206 (refer to Section 81.3.4 of IEEE 802.3-2015 Section 6), Idle Control
  • the block stream is sent from the second Ethernet device 1201 to the first Ethernet device 1101. Since the transmission link from the second Ethernet device 1201 to the first Ethernet device 1101 fails, the Idle control block stream does not arrive.
  • fault negotiation can be implemented by transmitting LF and RF in an Ethernet device, and the RS in the Ethernet device can terminate the fault information and stop the transmission of the MAC layer data stream.
  • the flexible Ethernet protocol that has been proposed, it is imperative to combine the standard Ethernet protocol and the flexible Ethernet protocol.
  • the embodiment of the present invention provides a communication method, a device, and a storage medium, which are used to implement transmission of fault information in a joint network of a standard Ethernet protocol and a flexible Ethernet protocol.
  • the embodiment of the present application provides a communication method, where the method includes: obtaining, by using a first port, a first fault information; wherein, the first port is a first type of port, and the first type of port is configured to transmit information according to a standard Ethernet protocol;
  • the first fault information is a first type of fault information, and the first type of fault information includes at least one of local fault information and remote fault information.
  • the second fault information is sent through the second port.
  • the second port is a second type of port, the second type of port transmits information according to the flexible Ethernet protocol;
  • the second type of fault information is a second type of fault information, and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty.
  • the first fault information is obtained by using the first port, and the second fault information is sent by the second port according to the first fault information, where the first port is a first type port, and the first type port is according to a standard Ethernet.
  • the protocol transmits information
  • the first fault information is the first type of fault information
  • the second port is the second type of port
  • the second type of port transmits information according to the flexible Ethernet protocol
  • the first type of fault information includes the local fault information and the remote end.
  • At least one of the fault information, the second fault information is a second type of fault information, and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty, so the method for transmitting the second fault information may be
  • the fault is reported in the joint networking of the standard Ethernet protocol and the flexible Ethernet protocol. It can also lay the foundation for distinguishing between the link failure corresponding to the flexible Ethernet protocol and the link failure of the standard Ethernet protocol.
  • the sending, by the second port, the second fault information according to the first fault information including: if the obtained first type fault information meets the first preset condition, according to the first fault information,
  • the second port sends the second fault information, where the first preset condition includes that the number of the first type of fault information obtained in the first preset duration is greater than the first threshold; or the obtained number is not less than the first threshold.
  • the first preset code block, and the interval between any two adjacent first preset code blocks obtained does not exceed the first preset code block interval. In this way, erroneous operations caused by a small amount of fault information can be avoided, and the accuracy of the operation can be further improved.
  • the method further includes: obtaining, by the second port, the third fault information; wherein the third fault information is the second type of fault information; and transmitting, according to the third fault information, the fourth fault information by using the first port;
  • the fourth fault information is the first type of fault information.
  • the fourth fault information is sent through the first port according to the third fault information, including: if the obtained second type fault information meets the second preset condition, according to the third fault information, pass the first
  • the port sends the fourth fault information, where the second preset condition includes: the number of the third fault information obtained in the second preset duration is greater than the second threshold; or; obtaining the number that is not less than the second threshold Two preset code blocks, and the interval between any two adjacent second preset code blocks obtained does not exceed the second preset code block interval.
  • the method further includes obtaining, by the third port, the fifth fault information; wherein the third port is the second type of port, and the fifth fault information is the first type of fault information or the second type of fault information;
  • the fourth port sends a fifth fault information; wherein the fourth port is a second type of port.
  • the first type of fault information and the second type of fault information can be transparently transmitted inside the flexible Ethernet network, so that the second type of fault information can be transmitted inside the flexible Ethernet network, and the first type of fault is transmitted outside the flexible Ethernet network.
  • the information can be used to distinguish whether the link corresponding to the flexible Ethernet protocol is faulty or the link corresponding to the standard Ethernet protocol is faulty according to the type of the fault information.
  • the method further includes obtaining, by the fifth port, the sixth fault information; wherein the fifth port is the second type of port, the sixth fault information is the first type of fault information, and the fifth port is configured with the standby link. ; Enable the alternate link corresponding to the fifth port.
  • the second fault information is sent by the second port according to the first fault information, including: sending, according to the first fault information, at least two second fault information by using the second port; wherein, at least two Any two of the second fault information are separated by at least one code block.
  • the transmission frequency of the second fault information can be flexibly set. For example, if the transmission frequency of the second fault information is set to be smaller than the transmission frequency of the first fault information, the bandwidth of the transmission path of the link corresponding to the flexible Ethernet protocol can be saved.
  • the first fault information is the remote fault information
  • the second fault information is the customer service type remote fault information
  • the remote fault information is continuous transmission, occupying a large bandwidth, and setting a certain number of code blocks to send one. Customer service type remote fault information can save bandwidth.
  • the embodiment of the present application provides a communication method, where the method includes: obtaining, by using a second port, third fault information; and sending, according to the third fault information, the fourth fault information by using the first port; where, the first port is a type of port, the first type of port transmits information according to a standard Ethernet protocol; the fourth type of fault information is a first type of fault information; the first type of fault information includes at least one of local fault information and remote fault information; For the second type of port, the second type of port transmits information according to the flexible Ethernet protocol; the third type of fault information is the second type of fault information; and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty.
  • the third fault information is obtained by using the second port, and the fourth fault information is sent by using the first port according to the third fault information, where the first type fault information includes at least one of the local fault information and the remote fault information.
  • the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty. Therefore, by transmitting the second fault information, the fault can be reported in the standard Ethernet protocol and the flexible Ethernet protocol joint network. It can lay a foundation for distinguishing between the link failure corresponding to the flexible Ethernet protocol and the link failure of the standard Ethernet protocol; the third can also be compatible with the scheme of notifying the fault through the first type of fault information transmission in the standard Ethernet protocol network.
  • the communication method further includes any one of the foregoing first aspect or the first aspect, and details are not described herein again.
  • the embodiment of the present application provides a communication device, where the communication device includes a memory, a transceiver, and a processor, where: the memory is used to store an instruction; the processor is configured to control the transceiver to perform signal reception according to an instruction to execute the memory storage. And signaling, the communication device is configured to perform the method of any of the first aspect or the first aspect described above when the processor executes the instruction stored in the memory.
  • the embodiment of the present application provides a communication device, which is used to implement any one of the foregoing first aspect or the first aspect, and includes a corresponding functional module, which is used to implement the steps in the foregoing method.
  • the embodiment of the present application provides a computer storage medium, where the computer storage medium stores instructions, when the computer is running on the computer, causing the computer to perform the method in the first aspect or any possible implementation manner of the first aspect. .
  • an embodiment of the present application provides a computer program product comprising instructions, which when executed on a computer, cause the computer to perform the method of the first aspect or any possible implementation of the first aspect.
  • FIG. 1 is a schematic diagram of a possible communication system architecture in the prior art
  • FIG. 2 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic structural diagram of a system according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of a fault information transmission path based on the system architecture shown in FIG. 4;
  • FIG. 6 is a schematic diagram of another fault information transmission path based on the system architecture shown in FIG. 4;
  • FIG. 7 is a schematic flowchart of a communication method according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart diagram of a communication method according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of another fault information transmission path based on the system structure shown in FIG. 4 according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a 0x4B 66 bit block code block according to an embodiment of the present disclosure
  • FIG. 11 is a schematic diagram of fault clearing information based on the 0x4B code block shown in FIG. 10 according to an embodiment of the present application;
  • FIG. 12 is a schematic diagram of local fault information based on the 0x4B code block shown in FIG. 10 according to an embodiment of the present application;
  • FIG. 13 is a schematic diagram of remote fault information based on the 0x4B code block shown in FIG. 10 according to an embodiment of the present application;
  • FIG. 14 is a schematic diagram of a second type of fault information based on the 0x4B code block shown in FIG. 10 according to an embodiment of the present disclosure
  • FIG. 15 is a schematic diagram of local service information of a customer service type based on the 0x4B code block shown in FIG. 10 according to an embodiment of the present application;
  • FIG. 16 is a schematic diagram of remote fault information of a client service type based on the 0x4B code block shown in FIG. 10 according to an embodiment of the present disclosure
  • FIG. 17 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of another communication device according to an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of another communication device according to an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1301 includes two types of ports, a first type port and a second type port.
  • the first type port transmits information according to a standard Ethernet protocol
  • the second type port transmits according to a flexible Ethernet protocol. information.
  • the communication device 1301 may include one or more first type ports, and one or more second type ports, such as the first type port 1401, the first type port 1402, the first type port 1403, and the second type shown in FIG. 2.
  • the first type of port corresponds to an interface and a physical layer
  • the physical layer of the first type of port includes a PMD, a PMA, and a PCS.
  • the second type of port includes an interface, a physical layer, and a flexible Ethernet protocol layer (also referred to as FlexE shim in English), and the physical layer of the second type of port includes PMD, PMA, and PCS.
  • the interfaces in the first type of port and the second type of port specifically refer to the connection port of the cable.
  • the first type of port further includes other layers above the physical layer, such as a MAC layer and the like.
  • the RS of the first type of port in the embodiment of the present application is not included.
  • the second type of port further includes other layers above the flexible Ethernet protocol layer, such as a MAC layer and the like. In FIG. 2, only the physical layer of the first type of port and the physical layer and flexible Ethernet protocol layer of the second type of port are simply shown.
  • the first type of port may be a port that only supports the standard Ethernet protocol. In this case, the first type of port can only transmit information according to the standard Ethernet protocol.
  • the first type of port may also be a port supporting two standard types: standard Ethernet protocol and flexible Ethernet protocol. In this case, the first type of port means that the currently used protocol is a standard Ethernet protocol. port.
  • the second type of port may be a port that only supports the flexible Ethernet protocol. In this case, the second type of port can only transmit information according to the flexible Ethernet protocol.
  • the second type of port may also be a port supporting two standard types: standard Ethernet protocol and flexible Ethernet protocol. In this case, the second type of port means that the currently used protocol is a flexible Ethernet protocol.
  • the first port can support the standard Ethernet protocol and the flexible Ethernet protocol. If the first port transmits information according to the standard Ethernet protocol in a period of time, the information can be transmitted according to the standard Ethernet protocol.
  • the first port is referred to as the first type of port. If the first port transmits information according to the flexible Ethernet protocol within a period of time, the first port may be referred to as the first port during the period of transmitting information according to the flexible Ethernet protocol.
  • the second type of port is referred to as the first type of port.
  • the embodiment of the present application may further include a third type of port, where the third type of port transmits information according to a standard Ethernet protocol, and the third type of port includes an interface, a physical layer, and an RS, and other upper functional units.
  • the third type of port may be, for example, a port including the RS in the first Ethernet device 1101 and the second Ethernet device 1201 shown in FIG. 1.
  • the third type of port may be a port that only supports the standard Ethernet protocol, in which case the third type of port can only transmit information according to the standard Ethernet protocol.
  • the third type of port may also be a port supporting two standard types: standard Ethernet protocol and flexible Ethernet protocol. In this case, the third type of port means that the currently used protocol is a standard Ethernet protocol. port.
  • the communication device 1301 in the embodiment of the present application further includes a fault information processing module, and the fault information processing module may be one or multiple, such as the fault information module 1601 and the fault information module 1602 in FIG. And fault information module 1603.
  • the fault information processing module may be disposed on one side of the first type of port, such as in an upper layer of a physical layer of the first type of port, or may be disposed on one side of the second type of port. For example, it can be set on the upper layer of the physical layer of the second type of port.
  • the fault information module can be set on the link connecting the first type of port and the second type of port.
  • the fault information processing module in the embodiment of the present application may perform the solution provided by the embodiment of the present application.
  • the second type of fault information may be generated according to the first type of fault information, or the first type of fault information may be generated according to the second type of fault information. and many more.
  • the embodiment of the present application further includes a switching unit 1701, and each port may be connected through the switching unit 1701.
  • the switching unit 1701 may also be referred to as a 1.5 layer flexible Ethernet protocol switching unit in the communication device 2102, the communication device 2103, and the communication device 2104.
  • the 1.5 layer may be a data transmission layer involved in the flexible Ethernet protocol, and may be located in a data transmission layer between the physical layer and the MAC layer of the Open System Interconnection (OSI) 7-layer model.
  • OSI Open System Interconnection
  • the concepts above the physical layer, or above the physical layer, or the upper layer of the physical layer refer to the layer above the physical layer in the model, such as 1.5 layers in the flexible Ethernet protocol.
  • the flexible Ethernet protocol layer can be, for example, the MAC layer and the like.
  • the relationship between ports can be pre-configured.
  • the first type port 1401 may be associated with the second type port 1501, that is, the first type port 1401 is connected to the second type port 1501, and the first type port 1401 obtains information.
  • the information defaults to the information that needs to be sent; the obtained information may be the information sent by other devices received, or the information generated by the first type of port 1401) is sent through the second type port 1501, and the second type of port is sent.
  • the information obtained by 1501 (this information defaults to the information that needs to be sent; the obtained information may be the information sent by other devices received, or the information generated by the first type of port 1501)) is sent through the first type of port 1401. Go out.
  • one port may be connected to one or more ports, but some connection relationships may not be in a working state.
  • the first type port 1401 and the second type port 1501 are connected, and The first type of port 1401 and the second type of port 1502 are also connected, but the connections of the first type of port 1401 and the second type of port 1502 are not currently in operation, only the connections of the first type of port 1401 and the second type of port 1501 are currently In the working state, that is to say, the information obtained by the first type port 1401 is sent out through the second type port 1501, and the information obtained by the second type port 1501 is sent out from the first type port 1401.
  • the first type port 1401 and the second type port 1501 are associated with each other, and the connection of the first type port 1401 and the second type port 1502 is in an inactive state, which may be called an inactive state or an association is not activated.
  • the association relationship between the ports in the embodiment of the present application is an association relationship in a working state. If the connection between the first type port 1401 and the second type port 1502 is currently in the working state in the next time period, that is, the information obtained by the first type port 1401 is sent through the second type port 1502.
  • the information obtained by the second type port 1502 is sent from the first type port 1401, and the relationship between the first type port 1401 and the second type port 1502 may be referred to in the next time period.
  • An association relationship between the two ports in the following embodiments of the present application may mean that there is a connection between the two ports, and the connection is in an active state, as shown in the explanation of the example.
  • the communication device in the embodiment of the present application may include at least two first type ports, and may also include at least two second type ports, and may also include at least one first type port and at least one second type port.
  • a third type of port may also be included in the embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a communication device according to an embodiment of the present application. As shown in FIG. 3, the communication device in the embodiment of the present application includes two types (for the first type port and the second type port).
  • the port of the first type can be associated with the port of the second type, and the port of the same type (such as two ports of the first type or two ports of the second type) can be associated with each other.
  • the first type port 1401 and the second type port 1503 are associated with each other, and the second type port 1502 and the second type port 1503 are associated with each other.
  • FIG. 4 is a schematic diagram showing a system architecture provided by an embodiment of the present application.
  • the communication system includes a communication device 2101, a communication device 2102, a communication device 2103, a communication device 2104, and a communication device. 2105.
  • the third type port 2201 of the communication device 2101 is connected to the first type port 2202 of the communication device 2102, the internal first type port 2202 and the second type port 2203 of the communication device 2102 are associated; the second type of the communication device 2102
  • the port 2203 is connected to the second type port 2204 of the communication device 2103, the internal second type port 2204 of the communication device 2103 is associated with the second type port 2205; the second type port 2205 of the communication device 2103 is associated with the second type of the communication device 2104
  • Type port 2206 is connected, internal second type port 2206 of communication device 2104 is associated with first type port 2207; first type port 2207 of communication device 2104 is coupled to third type port 2208 of communication device 2105.
  • each communication device in the system architecture shown in FIG. 4 are merely schematic, and any one of the communication device 2101, the communication device 2102, the communication device 2103, the communication device 2104, and the communication device 2105 may include at least one first At least one of the type port, the at least one second type port, and the at least one third type port is not limited in the embodiment of the present application.
  • the communication device 2101 and the communication device 2105 may only include a third type of port.
  • the communication device 2101 and the communication device 2105 may also be referred to as an Ethernet device, and may also be referred to as a user-side device; optionally, a communication device.
  • the 2101 and communication device 2105 can also include at least one first type of port and/or at least one second type of port, and the like.
  • the communication device 2103 may only include a second type of port, and optionally the communication device 2103 may further include at least one first type of port and/or at least one third type of port or the like.
  • the communication device 2102 and the communication device 2104 include at least one first type of port and at least one second type of port so that information transmitted by the first type of port can be transmitted through the second type of port.
  • communication device 2102 can also include at least one third type of port.
  • the communication device 2102 and the communication device 2104 may be referred to as a PE node, and the English may be written as a provider edge, which refers to a network device connected to the user at the edge of the operator network, and the PE node
  • the network-to-network interface (NNI) and the user-side port can be configured on the network, and the user-side port is the port (User network interface, UNI) that the network connects to the user.
  • the user side port may be the first type of port, and the port between the networks or between the devices in the network may be the second type of port.
  • the communication device 2103 can be called a provider, and is a network device in the carrier network.
  • P node It can be called a P node, and only the network port of the NNI can be configured on the P node.
  • one or more communication devices 2103 may be included between the communication device 2102 and the communication device 2104, that is, each of the two PE nodes is connected to the P node and the Ethernet device, and between the two PE nodes. It can include at least one P node.
  • information corresponding to the standard Ethernet protocol can be transmitted through the flexible Ethernet protocol, so that data can be transmitted more quickly and efficiently, and reused under the standard Ethernet network architecture. The purpose of the flexible Ethernet protocol.
  • the third type port in the communication device 2101 and the communication device 2105 includes an RS.
  • the communication device 2102, the communication device 2103, and the communication may be optionally
  • the RS is not configured in the first type port and the second type port in the device 2104.
  • data can be transmitted between the ports.
  • the port and the port can include two types of links, and one type of link is used to send information from one port to another port. One type of link is used to cause the one port to receive information sent by the other port.
  • the third type of port 2201 and the first type of port 2202 may include two types of links, which may be referred to as a first type of link and a second type of link, respectively, and the first type of link is used for transmission from the first type.
  • the third type of port 2201 transmits information to the first type of port 2202, and the second type of link user transmits information transmitted from the first type of port 2202 to the third type of port 2201.
  • the first type of link and the second type of link may be a pair of optical fibers, which are respectively used for receiving and transmitting, that is, one of the pair of optical fibers may be referred to as a first type of link.
  • the other root can be called the second type of link.
  • FIG. 5 exemplarily shows a fault information transmission path diagram based on the system architecture shown in FIG. 4, as shown in FIG. 5, after the introduction of the FlexE network in the standard Ethernet protocol, if the slave communication device 2101 to the communication device 2102 A fault occurs on the link, for example, the link of the third type port 2201 transmitting information to the first type port 2202 fails.
  • the physical layer of the first type port 2202 After the first type port 2202 detects the link fault, the physical layer of the first type port 2202 generates a local link. Fault information (Local Fault, LF).
  • the first type of port 2202 detects multiple faults in the link. For example, the first type of port 2202 does not receive information within the preset duration.
  • the LF generated by the first type port 2202 is transmitted to the communication device.
  • the 1.5-layer switching unit of 2102 is switched to the second type of port 2203.
  • the LF information is transmitted through the flexible Ethernet protocol network and is transparently transmitted to the third type of port 2208 of the communication device 2105. RS. That is, the LF generated by the first type of port 2202 will be passed along the second type port 2203, the second type port 2204, the second type port 2205, the second type port 2206, the first type port 2207, and finally to the third type.
  • Type RS of port 2208 may stop the data transmission of the MAC layer of the third type of port 2208 when the LF information is detected, and generate RF information, which is continuously inserted into the PCS layer of the third type of port 2208.
  • the RF information is also transmitted along the first type port 2207, the second type port 2206, the second type port 2205, the second type port 2204, the second type port 2203, and the first type port 2202 to the third type port 2201.
  • the RS of the third type port 2201 detects the RF information, the data transmission of the MAC layer of the third type port 2201 is stopped, the Idle control block is generated, and the PCS layer of the third type port 2201 is continuously inserted.
  • the fault information (such as LF and/or RF) generated by the link between the ports of the first type in the embodiment of the present application is transmitted inside the network of the flexible Ethernet protocol. Because the frequency of the LF generated by the first type of port in the prior art is high, and the RF is continuously transmitted, the fault information generated by the link failure between the first type of ports occupies a large proportion of the bandwidth. .
  • the first fault information is obtained by using the first port, and the second fault information is sent by the second port according to the first fault information, where the first port is a first type port, and the first type port is According to the standard Ethernet protocol, the first fault information is the first type of fault information, the second port is the second type of port, the second type of port transmits information according to the flexible Ethernet protocol, and the first type of fault information includes the local fault.
  • At least one of the information and the remote fault information, and the transmission path of the local fault information and the remote fault information occupies a large bandwidth, so that the second fault information can be transmitted through the standard Ethernet protocol and
  • the flexible Ethernet protocol can notify the fault in the joint network, and it can also save the bandwidth of the transmission path of the link corresponding to the flexible Ethernet protocol.
  • the physical layer of the second type of port also generates local fault information (such as LF) after detecting the fault.
  • LF local fault information
  • the FlexE Implementation Agreement 1.0 specification specifies that information failure (link failure), flexible Ethernet protocol group overhead frame (English may be called FlexE Group Overhead Frame), synchronization lock failure, is detected on the FlexE port (ie, the second type of port).
  • the protection switching function can be configured on the communication device configured with the second type of port.
  • the protection switching function can be called protection switching, which is also called automatic protection switching (APS).
  • APS automatic protection switching
  • the transmission of traffic is switched from one working path to a protection path corresponding to the working path due to failure or manual intervention (for example, switching from the working link to the standby link).
  • the protection switching function is configured in the communication device, the protection switching function is enabled when the LF is detected.
  • the protection switching function is configured in the flexible Ethernet protocol to provide a self-healing mechanism under the flexible Ethernet protocol. If a fault occurs inside the flexible Ethernet protocol network, the protection switching function can be used to achieve self-healing.
  • FIG. 6 exemplarily shows another fault information transmission path diagram based on the system architecture shown in FIG. 4.
  • at least one link may be included between the communication devices, such as the communication device 2103.
  • the communication device 2103 and the communication device 2104 include two links between the second type port 2205 and the second type port 2206, and between the second type port 2205 and the second type port 2303. Link (not shown in this example figure).
  • only one link between the communication device 2103 and the communication device 2104 is in a working state, and the link that is currently in the working state is a working link, and the link that is not currently in the working state is called Alternate link.
  • the link between the second type port 2205 and the second type port 2206 is in a working state during a time period, that is, data required to be transmitted between the communication device 2103 and the communication device 2104 passes through the second type port 2205 and the The link between the two types of ports 2206 is transmitted, and the link between the second type port 2205 and the second type port 2206 is called a working link, and the second type port 2301 and the second type that are not currently in the working state.
  • the link between the ports 2302 is referred to as a backup link; the link between the second type port 2301 and the second type port 2302 is in an active state in the next time period, and the second type port 2301 and the second type port 2302
  • the link between the two is called a working link, and the link between the second type of port 2205 and the second type of port 2206 is called a standby link.
  • the protection switching function is turned on when the LF is detected.
  • the protection switching function is configured on the communication device 2104, for example, between the communication device 2103 and the communication device 2104.
  • the two links are a link between the second type port 2205 and the second type port 2206, and a link between the second type port 2301 and the second type port 2302.
  • the current working link is a link between the second type of port 2205 and the second type of port 2206.
  • the protection switching function can be configured on the physical layer of the second type of port.
  • the protection switching function can be configured at the flexible Ethernet protocol layer of each second type of port.
  • the link between the communication device 2103 and the communication device 2104 fails, for example, the link of the second type port 2205 transmitting information to the second type port 2206 fails. Then, the physical layer of the second type port 2206 generates LF, and the flexible Ethernet protocol layer of the second type port 2206 (identified as FlexE shim in the figure) receives the LF, and then activates the protection switching function, that is, enables the second type of port 2206. Alternate link. That is, the working link is switched from the link between the second type port 2205 and the second type port 2206 to the link between the second type port 2301 and the second type port 2302, that is, the second type port 2301 is enabled.
  • the link between the second type of port 2302 and the second type of port 2206 is changed to the standby link.
  • the second type of port 2204 is associated with the second type of port 2301, and the second type of port 2204 and the second type of port 2205 are in an inactive state. It can be seen that when there is a fault in the flexible Ethernet protocol, the flexible Ethernet protocol enables the standby link to continue to work. This capability can also be called the self-healing capability of the flexible Ethernet protocol.
  • the alternate link of the second type of port 2205 is enabled, the second type of port 2302 no longer receives the LF because the second type of port 2205 failed to send a message to the second type of port 2206.
  • the first type port 2202 detects the link fault, first.
  • the physical layer of the type port 2202 generates LF, and the LF is transmitted to the communication device 2104.
  • the communication device 2104 After detecting the LF, the communication device 2104 triggers a protection switching function, that is, the link corresponding to the second type port 2206 is switched to the standby link, that is, Said to switch the working link from the link between the second type of port 2205 and the second type of port 2206 to the link between the second type of port 2301 and the second type of port 2302, ie enable the second type of port 2301 and the first
  • the link between the two types of ports 2302 serves as a working link, and the link between the second type of port 2205 and the second type of port 2206 changes to a standby link.
  • the LF will be received even after the communication device 2104 initiates the protection switching function, in which case the communication device 2104 may continue to enable the protection switching.
  • the function is to switch the working link from the link between the second type port 2301 and the second type port 2302 to the link between the second type port 2205 and the second type port 2206. It can be seen that, since the LF information received by the communication device is generated when a fault occurs between the first type of ports, the LF sends the communication device 2104 even after the communication device 2104 starts the automatic protection switching function, resulting in repeated switching of the working link. There is a situation of switching shocks.
  • the protection switching function under the flexible Ethernet protocol originally implements the self-healing function for the fault information inside the flexible Ethernet protocol, but the fault information outside the flexible Ethernet protocol network may enter the flexible Ethernet protocol, which may cause communication.
  • the device mistakenly believes that the fault information is fault information in the flexible Ethernet protocol network, causing a return to the working link and a switching vibration.
  • the second fault information is the second type of fault information, and the link corresponding to the standard Ethernet protocol may be faulty indicated by the second fault information. The link between the link corresponding to the Ethernet protocol and the link corresponding to the standard Ethernet protocol is faulty.
  • FIG. 7 exemplarily shows a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 7, the method includes steps 3101 to 3102.
  • Step 3101 The communication device obtains the first fault information by using the first port.
  • the first port is a first type of port, and the first type of port transmits information according to a standard Ethernet protocol.
  • the first fault information is a first type of fault information.
  • One type of failure information includes at least one of local failure information and remote failure information.
  • the communication device includes a plurality of first type ports, and the first port is a first type port of the plurality of first type ports and associated with the at least one second type port.
  • the first type of port may be a port supporting only a standard Ethernet protocol, or a port supporting two standard types: a standard Ethernet protocol and a flexible Ethernet protocol.
  • the first type of port It means that the protocol currently in use is the port of the standard Ethernet protocol.
  • the second type of port may be a port that only supports the flexible Ethernet protocol, or a port that supports the standard Ethernet protocol and the flexible Ethernet protocol. In this case, the second type of port. It means that the currently used protocol is the port of the flexible Ethernet protocol.
  • the second type of port It means that the currently used protocol is the port of the flexible Ethernet protocol.
  • Step 3102 The communication device sends the second fault information by using the second port according to the first fault information.
  • the second port is a second type port, and the second type port is configured to transmit information according to a flexible Ethernet protocol.
  • the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty.
  • the communication device of this step may be the communication device including two types of ports in FIG. 2 to FIG. 6 above, such as the communication device 2102 and the communication device 2104 in FIG. 2 to FIG. 6 described above.
  • the first port and the second port are associated with each other, that is, the information obtained by the first port is transmitted through the second port, and the information obtained by the second port is transmitted from the first port.
  • the communication device includes a plurality of second type ports, and the second port is a second type port of the plurality of second type ports and associated with the at least one first type port.
  • the communication device when the communication device obtains the first type of fault information through the first type of port, if the second type of port is required to be sent out, the second type of fault information is sent through the second type of port.
  • the first fault information is obtained by using the first port, and the second fault information is sent by the second port according to the first fault information, where the first port is a first type port, and the first type port is according to a standard Ethernet.
  • the protocol transmits information
  • the first fault information is the first type of fault information
  • the second port is the second type of port
  • the second type of port transmits information according to the flexible Ethernet protocol
  • the first type of fault information includes the local fault information and the remote end.
  • At least one of the fault information, the second fault information is a second type of fault information, and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty, so the method for transmitting the second fault information may be
  • the fault is reported in the joint networking of the standard Ethernet protocol and the flexible Ethernet protocol. It can also lay the foundation for distinguishing between the link failure corresponding to the flexible Ethernet protocol and the link failure of the standard Ethernet protocol.
  • FIG. 8 is a schematic flowchart showing a communication method provided by an embodiment of the present application. As shown in FIG. 8 , the method includes steps 3401 to 3402. .
  • the communication device performing step 3401 to step 3402 and the communication device performing step 3101 and step 3102 may be two different communication devices.
  • the steps included in the communication device of step 3401 to step 3402 are performed.
  • a port is different from the first port in the communication device performing step 3101 and step 3102, and the second port included in the communication device of step 3401 to step 3402 is executed in the communication device performing step 3101 and step 3102.
  • the second port is a different two ports.
  • the communication device performing step 3101 to step 3102 may be the communication device 2102 in FIG. 8, and the communication device performing step 3401 to step 3402 may be the communication device 2104 in FIG. 8. In this case, step 3101 is performed.
  • the first port in the communication device to step 3102 may be the first type port 2202, and the second port in the communication device performing step 3101 to step 3102 may be the second type port 2203; the communication device performing step 3401 to step 3402
  • the first port in the communication may be the first type port 2207, and the second port in the communication device performing step 3401 to step 3402 may be the second type port 2206.
  • the communication device that performs step 3401 to step 3402 may also be the communication device that performs step 3101 and step 3102 described above.
  • the first port and the execution step included in the communication device of step 3401 to step 3402 are performed.
  • the first port in the communication device of the step 3101 and the step 3102 may be two different ports or the same two ports, and the second port included in the communication device of step 3401 to step 3402 is executed and steps 3101 and 3102 are performed.
  • the second port in the communication device can be two different ports or the same two ports.
  • step 3401 and step 3402 may be performed after step 3101 and step 3102 described above, or may be performed before step 3101 and step 3102.
  • Step 3401 the communication device obtains third fault information through the second port; according to the third fault information; the second port is a second type port, the second type port transmits information according to a flexible Ethernet protocol; and the third fault information is a second type
  • the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty; optionally, the communication device includes multiple second type ports, and the second port is among the plurality of second type ports, and A second type of port associated with at least one port of the first type.
  • the communication device obtains the second type of fault information through the second type of port, if the first type of port is required to be sent out, the first type of fault information is sent through the first type of port.
  • the first type of port may be a port supporting only a standard Ethernet protocol, or a port supporting two standard types: a standard Ethernet protocol and a flexible Ethernet protocol.
  • the first type of port It means that the protocol currently in use is the port of the standard Ethernet protocol.
  • the second type of port may be a port that only supports the flexible Ethernet protocol, or a port that supports the standard Ethernet protocol and the flexible Ethernet protocol. In this case, the second type of port. It means that the currently used protocol is the port of the flexible Ethernet protocol.
  • the second type of port It means that the currently used protocol is the port of the flexible Ethernet protocol.
  • Step 3402 The communication device sends the fourth fault information by using the first port, where the first port is a first type port, the first type port transmits information according to a standard Ethernet protocol, and the fourth fault information is a first type fault information.
  • One type of failure information includes at least one of local failure information and remote failure information.
  • the communication device of this step may be the communication device including two types of ports in FIG. 2 to FIG. 6 above, such as the communication device 2102 and the communication device 2104 in FIG. 2 to FIG. 6 described above.
  • the first port and the second port are associated with each other, that is, the information obtained by the first port is transmitted through the second port, and the information obtained by the second port is transmitted from the first port.
  • the communication device includes a plurality of first type ports, and the first port is a first type port of the plurality of first type ports and associated with the at least one second type port.
  • the third fault information is obtained by using the second port, and the fourth fault information is sent by using the first port according to the third fault information, where the first type fault information includes at least one of local fault information and remote fault information.
  • the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty. Therefore, by transmitting the second fault information, the fault can be reported in the standard Ethernet protocol and the flexible Ethernet protocol joint network. It can lay a foundation for distinguishing between the link failure corresponding to the flexible Ethernet protocol and the link failure of the standard Ethernet protocol; the third can also be compatible with the scheme of notifying the fault through the first type of fault information transmission in the standard Ethernet protocol network.
  • FIG. 7 and FIG. 8 Based on the communication methods described in FIG. 7 and FIG. 8, several possible designs in the above-mentioned FIG. 7 and FIG. 8 are further explained below, and the following method item embodiments are applicable to the solutions described in FIG. 7 and FIG. .
  • the bandwidth of the transmission path is occupied.
  • the solution of the embodiment of the present application can transmit the second type of fault information in the flexible Ethernet protocol, and can flexibly set the sending frequency of the second fault information, for example, setting the sending frequency of the second fault information to be smaller than the first fault information.
  • the transmission frequency can save the bandwidth of the transmission path of the link corresponding to the flexible Ethernet protocol.
  • the first fault information is the remote fault information
  • the second fault information is the customer service type remote fault information
  • the remote fault information is continuous transmission, occupying a large bandwidth, and setting a certain number of code blocks to send one.
  • Customer service type remote fault information can save bandwidth.
  • the saved network bandwidth can be used to carry other services, including statistical multiplexing, and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty, so that the standard Ethernet protocol can be avoided. If the corresponding link fails, the protection switching function is triggered by mistake.
  • the link in English may also be referred to as LINK
  • the link negotiation based on the local Ethernet 802.3 specification based on local fault information and/or remote fault information may be supported ( IEEE 802.3, Section 81.3.4), also ensures the correct implementation of the self-healing mechanism within the flexible Ethernet protocol network.
  • the communications device obtains the first fault information by using the first port, where the communications device may generate the local fault information by using the physical layer of the first port; or the communications device may pass the first Remote fault information received by the port. For example, if the first port is the first type port 2202, and the link of the third type port 2201 to the first type port 2202 fails in FIG. 6, the physical layer of the first type port 2202 generates a local fault. information.
  • the link of the first type of port 2202 to the third type of port 2201 fails, the physical layer of the third type of port 2201 generates local fault information, and after the RS of the third type of port 2201 detects the local fault information, The remote fault information is generated, and the remote fault information is transmitted to the first type port 2202.
  • Two types of second type fault information may be defined in the embodiment of the present application, and are distributed into customer service type local fault information and customer service type remote fault information.
  • the local fault information of the customer service type can be called Client Service Fault, which can be abbreviated as CSF.
  • CSF is used to represent the local fault information of the customer service type.
  • the customer service type remote fault information in English can be called Remote Client Service Fault, which can be abbreviated as RCSF.
  • the expression in Figure 9 is clearer.
  • the RCSF is used to represent the remote fault information of the customer service type.
  • Customer service type local fault information and customer service type The type of customer service in the remote fault information is a relatively high-level statement, specifically the relevant content of the service serving the customer; the customer service type local fault information and the customer service type are far
  • the type of the customer service in the terminal fault information is not limited to the second type of fault information in the embodiment of the present application, and is only used for the local fault information (English shorthand LF) and the remote fault information in the embodiment of the present application (English shorthand) RF) distinguishes between names.
  • the sending, by the second port, the second fault information according to the first fault information, the second fault information corresponding to the first fault information is generated according to the first fault information, and the second fault information is sent by using the second port.
  • the first fault information is the local fault information
  • the second fault information corresponding to the first fault information is the customer service type local fault information
  • the first fault information is the remote fault information
  • the second fault corresponding to the first fault information is the customer service type remote fault information.
  • the second type of fault information corresponding to the first type of fault information is the customer service type remote fault information; correspondingly, the second type of fault information is the customer service type local fault information, and the second type of fault information corresponds to the first type of fault.
  • the information of the second type is the fault information of the customer service type, and the fault information of the first type corresponding to the fault information of the second type is the remote fault information.
  • generating the second fault information corresponding to the first fault information according to the first fault information may be newly generating the second fault information, or adding the indication information to the first fault information, where the indication information is used to indicate The link corresponding to the standard Ethernet protocol has failed.
  • generating the second type of fault information corresponding to the first type of fault information according to the first type of fault information may be newly generating the second type of fault information, or adding the indication information to the first type of fault information.
  • the indication information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty.
  • the communications device sends the second fault information by using the second port according to the first fault information, including: if the obtained first type fault information meets the first preset condition, according to the first fault information.
  • the first preset code block that is not less than the first quantity threshold is obtained, and the interval between any two adjacent first preset code blocks obtained does not exceed the first preset code.
  • the second fault information is sent under the condition of the block interval, and the communication device may continuously detect the obtained number of the first preset code blocks, and if it detects that the first preset code block that is not less than the first quantity threshold is obtained, And the condition that the interval between any two adjacent first preset code blocks does not exceed the first preset code block interval is stopped, and then the second fault information is stopped. In this way, erroneous operations caused by a small amount of fault information can be avoided, and the accuracy of the operation can be further improved.
  • the first 66 bit block control block is the first preset code block, and the first preset code block interval is 128 code blocks, and the first quantity threshold is 4, when 4 first 66 are detected.
  • the counter is recorded as the first code block, and if one is detected in the next 128 blocks, the counter is recorded as the second one, if In the next 128 blocks, no first 66 bit block control block is detected, the event record is cleared (ie, the counter is cleared); when the first 66 bit block control block is detected again, the counter is restarted from 1 Counting; thus, if four valid first 66 bit block control blocks are continuously accumulated (ie, the counter reaches 4), it is considered that LF or RF information is obtained.
  • the communication device continuously detects that the communication device sends the second fault information when the value of the counter is not less than 4, and stops transmitting the second fault information if the value of the counter is less than 4, that is, correspondingly, if not If the condition is that the first preset code block is not less than the first quantity threshold, and the interval between any two adjacent first preset code blocks is not more than the first preset code block interval, If the fault is cleared, the second fault information is no longer sent. For example, if the communication device does not detect the first 66 bit block control block in consecutive 128 code blocks, the fault is considered to be cleared.
  • the communications device sends the second fault information by using the second port according to the first fault information, including: if the number of the first fault information obtained in the first preset duration is greater than the first threshold, A fault information is sent through the second port to send the second fault information.
  • the first fault information may also be a first preset code block. That is, if the obtained first type of fault information meets the first preset condition, the second fault information is sent through the second port according to the first fault information; wherein the first preset condition includes: at the first preset The number of first type of fault information obtained within the duration is greater than the first number of thresholds. The first type of failure information obtained in this case is the first failure information.
  • the second fault information is sent under the condition that “the number of the first fault information obtained in the first preset duration is greater than the first threshold”, and the number of the first fault information obtained by the communications device is continuously detected. If it is detected that the condition that the number of the first fault information obtained within the first preset duration is greater than the first number threshold is not satisfied, the sending of the second fault information is stopped.
  • the first 66 bit block control block is the first preset code block
  • the first quantity threshold is 4, and the duration used by the first preset code block for determining the first quantity threshold is not greater than the first.
  • the preset time length for example, when the duration of the four consecutive first 66 bit blocks is not greater than the first preset duration, the second fault information is sent.
  • the communication device continuously detects the obtained first preset code block, and if the duration of the four consecutive first 66 bit blocks is greater than the first preset duration, it is determined that “the first obtained in the first preset duration is satisfied” The condition that the number of fault information is greater than the first number threshold is stopped, and the second fault information is stopped.
  • the method further includes: the communication device obtains the sixth fault information by using the fifth port; wherein the fifth port is the second type of port, the sixth fault information is the first type of fault information; the fifth port is configured with the standby link; The alternate link corresponding to the fifth port.
  • the protection switching function is configured in the communication device, when the communication device receives the fault information in the flexible Ethernet protocol network, the protection switching function is enabled, and the flexible Ethernet protocol is received. The switching function is not enabled in the case of fault information outside the network.
  • the second type of fault information in the embodiment of the present application may indicate that the link corresponding to the standard Ethernet protocol is faulty.
  • the protection switching function is not enabled, and the first type of fault is received.
  • the protection switching function is turned on. It can be seen that, in the embodiment of the present application, the link corresponding to the standard Ethernet protocol is faulty and the link corresponding to the flexible Ethernet protocol is faulty is distinguished by using the first type of fault information and the second type of fault information, thereby avoiding The link corresponding to the standard Ethernet protocol triggers the protection switching function. For example, the process of enabling the backup link between the communication device 2103 and the communication device 2104 shown in FIG. 6 is not mentioned here.
  • the second type fault information when the fault information is transmitted from the standard Ethernet protocol network into the flexible Ethernet protocol network, the second type fault information may be generated according to the first type fault information, and the second type fault is transmitted in the flexible Ethernet protocol network. information.
  • the first type of fault information may be generated according to the second type of fault information, and the first type of fault information may be transmitted in the standard Ethernet protocol network.
  • the third fault information is obtained by using the second port, where the third fault information is the second type of fault information, and the fourth fault information is sent by the first port according to the third fault information.
  • the fourth fault information is the first type of fault information.
  • the second type of fault information can be transmitted inside the flexible Ethernet network, and the first type of fault information can be transmitted outside the Ethernet network flexibly, so that the link corresponding to the flexible Ethernet protocol can be distinguished according to the type of the fault information or the standard.
  • the link corresponding to the Ethernet protocol has failed.
  • the fault information in the embodiment of the present application is information for indicating that the link is faulty, and is a high-level name, and the fault information may include the first type of fault information and/or the second type of fault information.
  • the fourth fault information is sent by using the first port according to the third fault information, including: generating fourth fault information corresponding to the third fault information according to the third fault information, and sending the fourth fault information by using the first port.
  • the third fault information is a customer service type local fault information, and the fourth fault information corresponding to the third fault information is local fault information; the third fault information is a customer service type remote fault information, and the third fault information corresponds to the third fault information.
  • the four fault information is the remote fault information.
  • the generating the fourth fault information corresponding to the third fault information according to the third fault information may be newly generated fourth fault information, or may be obtained by removing the indication information in the third fault information, where the indication information is used.
  • the indication information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty.
  • the communications device sends the fourth fault information by using the first port according to the third fault information, including: if the obtained second type fault information meets the second preset condition, passing the first port according to the third fault information.
  • the second preset code block that is not less than the second quantity threshold is obtained, and the interval between any two adjacent second preset code blocks obtained does not exceed the first
  • the fourth fault information is sent under the condition of two preset code block intervals, and the communication device continuously detects the obtained number of second preset code blocks, and if it detects that the second pre-acquisition is not satisfied, the second pre-determination is not less than the second quantity threshold. If the code block is set and the interval between any two adjacent second preset code blocks does not exceed the second preset code block interval, the fourth fault information is stopped. In this way, erroneous operations caused by a small amount of fault information can be avoided, and the accuracy of the operation can be further improved.
  • the second 66 bit block control block is the second preset code block
  • the second preset code block interval is 128 code blocks
  • the second number threshold is 4, when 4 second 66 are detected.
  • a bit block (which may also be referred to as a second 66-bit block) control block, and the second 66 bit block control block may carry indication information indicating that a link corresponding to the standard Ethernet protocol is faulty.
  • any two adjacent second 66 bit block control blocks are separated by no more than 128 code blocks, and the fourth fault information is sent through the first port according to the third fault information.
  • the counter is recorded as the first code block, and if one is detected in the next 128 blocks, the counter is recorded as the second one.
  • the event record is cleared (ie, the counter is cleared), and the second 66 bit block control block is re-started from 1 when the second 66 bit block control block is detected next time; In this way, four valid second 66 bit block control blocks are continuously accumulated, that is, when the counter reaches 4, it is considered that LF or RF information is obtained.
  • the communication device continuously detects that the communication device sends the fourth fault information when the value of the counter is not less than 4, and stops transmitting the fourth fault information if the value of the counter is less than 4, that is, correspondingly, if not
  • the condition "acquiring a second preset code block having a quantity not less than the second quantity threshold, and the interval between any two adjacent second preset code blocks is not more than the second preset code block interval", If the fault is cleared, the fourth fault information is no longer sent. For example, if the communication device does not detect the second 66 bit block control block in consecutive 128 code blocks, the fault is considered to be cleared.
  • the communications device sends the fourth fault information by using the first port according to the third fault information, including: if the number of the third fault information obtained in the second preset duration is greater than the second threshold, The third fault information is sent through the first port.
  • the third fault information may also be a second preset code block. That is, if the obtained second type of fault information meets the second preset condition, the fourth fault information is sent through the first port according to the third fault information; wherein the second preset condition includes: at the second preset The number of third fault information obtained within the duration is greater than the second threshold.
  • the second type of failure information obtained in this case is the third failure information.
  • the fourth fault information is sent under the condition that “the number of the third fault information obtained in the second preset duration is greater than the second threshold”, and the communication device continuously detects the obtained third fault information. If it is detected that the condition that the number of the third fault information obtained within the second preset duration is greater than the second number threshold is not satisfied, the fourth fault information is stopped.
  • the second 66 bit block control block is the second preset code block
  • the second quantity threshold is 4, and the duration used by the second preset code block for determining the second quantity threshold is not greater than the second.
  • the preset time length for example, when the duration of the four consecutive 66 bit blocks is not greater than the second preset duration, the fourth fault information is sent.
  • the communication device continuously detects the obtained second preset code block, and if the duration of the four consecutive 66 bit blocks is greater than the first preset duration, it is determined that “the second preset duration is satisfied”. The condition that the number of two fault information is greater than the second number threshold is stopped, and the fourth fault information is stopped.
  • the method further includes: obtaining, by using the third port, the fifth fault information, where the third port is the second type of port, and the fifth fault information is the first type of fault information or the second type of fault.
  • the first type of fault information and the second type of fault information can be transparently transmitted inside the flexible Ethernet network, so that the second type of fault information can be transmitted inside the flexible Ethernet network, and the first type of fault is transmitted outside the flexible Ethernet network.
  • the information can be used to distinguish whether the link corresponding to the flexible Ethernet protocol is faulty or the link corresponding to the standard Ethernet protocol is faulty according to the type of the fault information.
  • the third port and the fourth port are associated with each other, that is, the information obtained by the third port is transmitted through the fourth port, and the fourth port is obtained.
  • the information is transmitted from the third port, and the third port is the second type port, and the fourth port is the second type port, and the third port and the fourth port can transparently obtain the first type of fault information or the second type.
  • Type fault information may be the third port may be the second type port 2204 in the communication device 2103 in FIG. 4 to FIG. 6 described above, and the fourth port may be the second type port 2205 in the communication device 2103 in FIG. 4 to FIG.
  • the second type of port 2204 and the second type of port 2205 can transparently transmit the obtained first type of fault information or the second type of fault information.
  • the third port and the fourth port may also be two second type ports in the communication device 2102 in FIGS. 4 to 6 described above.
  • the method further includes: obtaining, by using the sixth port, the seventh fault information, where the sixth port is the first type of port, the seventh fault information is the first type of fault information, and the seventh port is Sending a seventh fault information; wherein the seventh port is a first type of port. That is, if there is an association between the two types of ports, for example, there is an association between the sixth port and the seventh port, that is, the information obtained by the sixth port is transmitted through the seventh port, and the seventh port is obtained.
  • the information is transmitted from the sixth port, and the sixth port is the first type port, the seventh port is the first type port, and the sixth port and the seventh port can transparently obtain the first type of fault information or the second type.
  • Type fault information is, obtaining, by using the sixth port, the seventh fault information, where the sixth port is the first type of port, the seventh fault information is the first type of fault information, and the seventh port is Sending a seventh fault information; wherein the seventh port is a first type of port. That is, if there is
  • the sixth port may be the first type port 3201 in the communication device 2102 in FIG. 4, and the seventh port may be the first type port 3202 in the communication device 2102 in FIG. 4, the first type port 3201 and the first port.
  • a type 1 port 3202 can transparently obtain the first type of fault information or the second type of fault information.
  • the first type of port 3201 and the first type of port 3202 are associated with each other.
  • the first type of port 3201 can be connected to other communication devices.
  • the first type of port, the second type of port 3202 can also be connected to the first type of port of the other communication device.
  • FIG. 9 exemplarily shows the system structure based on FIG. 4 provided in the embodiment of the present application.
  • a fault information transmission path diagram is shown in FIG. 9.
  • a fault information processing module can be configured in the communication device, such as a first type port 2202, a first type port 3201, and a first type port 3202 in the communication device 2102.
  • the fault information processing module is configured above the physical layer, and the fault information processing module is configured on the upper layer of the physical layer of the first type port 2207 in the communication device 2104.
  • the physical layer of the first type port 2202 generates local fault information (belonging to the first type of fault information, Illustrated as LF), optionally, when the communication device 2102 obtains the first type of fault information through the first type of port 2202, for example, when the first preset condition is met, the customer service type local fault information is sent (belongs to The second type of fault information is schematically written as CSF in the figure.
  • the fault information processing module can be used. When the fault information processing module receives the first type of fault information, for example, when the first preset condition is met, the fault information processing module sends the customer service type local fault information.
  • the first preset condition is that “the number of the first type of fault information obtained in the first preset duration is greater than the first threshold” or “the first preset code block that is not less than the first threshold” is obtained. And the interval between any two adjacent first preset code blocks is not more than the first preset code block interval.
  • the first preset code block whose number is not less than the first quantity threshold is obtained, and the interval between any two adjacent first preset code blocks is not more than the first preset code block interval
  • the condition of the customer service type local fault information is sent, for example, a counter is set.
  • the counter is incremented by 1
  • the current counter value is 1
  • the second first preset code block is received. If the interval between the first preset code block and the previous adjacent first preset code block is not greater than 128 code blocks, the counter is incremented by one; if the first preset code block is before The interval between an adjacent first predetermined code block is greater than 128 code blocks, and the counter is cleared.
  • the preset first quantity threshold is 4, and when the counter is not less than 4, the customer service type local fault information is started to be sent.
  • a customer service type local fault information may be sent by a certain number of code blocks. When the counter is less than 4, the customer service type local fault information is no longer sent.
  • the customer service type local fault information generated by the first type port 2202 is transmitted along the second type port 2203, the second type port 2204, the second type port 2205, and the second type port 2206 (also referred to as transparent transmission) to Communication device 2104. Since the communication device needs to transmit the information transmitted by the second type port 2206 through the first type port 2207, the communication device 2104 can determine that the obtained customer service type local fault information satisfies the second according to the obtained customer service type local fault information. When the condition is preset, local fault information is generated and local fault information is transmitted through the first type of port 2207 to the third type of port 2208 of the communication device 2105.
  • the fault information processing module in the communication device 2104 may generate local fault information according to the obtained customer service type local fault information.
  • the communication device 2104 may no longer send the local fault information through the first type port 2207.
  • the second preset condition may be: “the number of the second type of fault information obtained in the second preset duration is greater than the second threshold” or “the second preset block having the number not less than the second threshold” And the interval between any two adjacent second preset code blocks obtained does not exceed the second preset code block interval.
  • the RS in the third type port 2208 may be sent a remote fault if it is determined that the obtained local fault information satisfies the condition first preset condition.
  • the information may be that the remote fault information is continuously sent.
  • the communication device 2105 determines that the obtained local fault information does not meet the first preset condition, the remote fault information is not sent.
  • the first type port 2207 of the communication device 2104 determines that the obtained remote fault information satisfies the first preset condition, and the communication device 2104 generates the client service type remote fault information and passes the The second type of port 2206 is sent.
  • the communication device 2105 determines that the obtained remote fault information does not satisfy the first preset condition, the communication device 2105 does not transmit the customer service type remote fault information.
  • the client service type remote fault information sent by the communication device 2104 through the second type port 2206 is transparently transmitted to the communication device 2102 along the second type port 2205, the second type port 2204, and the second type port 2203. . Since the communication device 2102 needs to transmit the information obtained by the second type port 2203 through the first type port 2202, the communication device 2104 determines the obtained client service type far-end according to the case where the client service type remote failure information is obtained. The fault information satisfies the second preset condition, and the remote fault information is sent through the first type port 2202. Correspondingly, if it is determined that the obtained client service type remote fault information does not satisfy the second preset condition, the remote fault information is not sent through the first type port 2202.
  • FIG. 9 another optional implementation manner is provided in the embodiment of the present application.
  • the third type port 2201 of the communication device 2101 sends information to the chain of the first type port 2202. If the fault occurs, the physical layer of the first type of port 2202 generates local fault information.
  • the communications device obtains the first type of fault information through the first port, and determines that the obtained first type fault information meets the first The preset condition sends a local fault information for the customer service type.
  • the communication device 2102 obtains the first type of fault information through the first type port 2202 and does not satisfy the first preset condition, the fault clearing information may be sent.
  • the customer service type local fault information sent by the first type port 2202 is transparently transmitted to the communication device 2104 along the second type port 2203, the second type port 2204, the second type port 2205, and the second type port 2206. Since the communication device 2104 needs to transmit the information transmitted by the second type port 2206 through the first type port 2207, the communication device 2104 determines that the obtained customer service type local fault information satisfies the second pre-acquisition according to the obtained customer service type local fault information. With the condition set, local fault information is generated and local fault information is transmitted through the first type of port 2207 to the third type of port 2208 of the communication device 2105.
  • the fault information processing module in the communication device 2104 may generate local fault information according to the obtained customer service type local fault information.
  • the fault clearing information may also be along the second type port 2203, the second type port 2204, the second type port 2205, and the second type port. 2206 is transparently transmitted to the communication device 2104, and the communication device 2104 stops transmitting the local failure information through the first type of port 2207 in the event that it is determined that the failure clearing information is received.
  • the remote fault information is sent by the RS in the third type port 2208, if the obtained local fault information meets the first preset condition, It can be that the remote fault information is continuously sent.
  • the communication device 2105 determines that the obtained local fault information does not meet the first preset condition, the remote fault information is not sent.
  • the first type port 2207 of the communication device 2104 determines that the received remote fault information meets the first preset condition, and the communication device 2104 generates the client service type remote fault information. And sent through the second type of port 2206.
  • the communication device 2105 determines that the received remote fault information does not satisfy the first preset condition, the remote fault information may not be sent or the fault clear information may be sent.
  • the client service type remote fault information sent by the communication device 2104 through the second type port 2206 is transparently transmitted to the communication device 2102 along the second type port 2205, the second type port 2204, and the second type port 2203. . Since the communication device 2102 needs to transmit the information obtained by the second type port 2203 through the first type port 2202, the communication device 2104 determines the received type of customer service according to the remote failure information of the customer service type. The remote fault information meets the second preset condition, and the remote fault information is sent through the first type port 2202.
  • the fault clearing information may also be transparently transmitted to the communication device 2102 along the second type port 2205, the second type port 2204, and the second type port 2203.
  • the communication device 2102 stops transmitting the remote failure information or transmits the failure clear information to the third type port 2201 of the communication device 2101 in the case where it is determined that the failure clear information is received.
  • the protection switching function is configured in the communication device 2104, if the link between the second type of ports fails, for example, the second type of port 2205 sends a link to the second type of port 2206.
  • the second type of port 2206 in the communication device 2104 generates local fault information, and the communication device 2104 initiates a backup link corresponding to the second type of port 2206, such as starting the second type of port 2301 and the second type of port 2302 of FIG.
  • a connection between the communication device 2103 and the communication device 2104 is implemented.
  • the fault of the standard Ethernet protocol link and the fault of the flexible Ethernet protocol link can be distinguished, so that the fault negotiation mechanism under the standard Ethernet protocol is retained, and the protection can also be based on the protection.
  • the switching function implements the self-healing function inside the flexible Ethernet protocol.
  • the backup link corresponding to the second type port in FIG. 4 may include a link between the second type port 2301 and the second type port 2303 between the communication device 2103 and the communication device 2104.
  • a link between the second type of port 3301 of the communication device 2102 and the second type of port 3302 of the communication device 2103 may be included, such as enabling association of the first type of port 2202 and the second type of port 3301 in the communication device 2102, enabling communication
  • the association relationship between the second type port 3302 and the second type port 2301 in the device 2103 enables the association relationship between the second type port 2302 and the first type port 2207 in the communication device 2104.
  • the alternate link included in the flexible Ethernet protocol can replace all the working links in the good Ethernet protocol, thereby ensuring the self-healing function inside the flexible Ethernet protocol.
  • the first type port 2202 can be used in FIG. a link between the second type of port 3301, the second type of port 3302, the second type of port 2301, the second type of port 2302, and the first type of port 2207 "replaces" the first type of port 2202, the second type of port 2203, A link between the second type of port 2204, the second type of port 2205, the second type of port 2206, and the first type of port 2207.
  • the sending the second type of fault information in the embodiment of the present application may be to send at least two second type fault information, where at least one of the at least two second type fault information is separated by at least one code block.
  • the sending, by the second port, the second fault information according to the first fault information including: sending, according to the first fault information, the at least two second fault information by using the second port; wherein, at least one second fault information is included Any two second fault information are separated by at least one code block. In this way, the bandwidth of the transmission path of the link corresponding to the flexible Ethernet protocol can be saved.
  • FIG. 10 exemplarily shows a schematic diagram of a 0x4B 66 bit block code block provided by an embodiment of the present application.
  • a control block format of an 0x4B code block (English may be called a control block). Format) is 0 0 D 1 D 2 D 3 Z 4 Z 5 Z 6 Z 7 ; the sync header (also known as the synchronization header) is "10"; the block type area (English can be called block type field) is 0x4B
  • the next three bytes are D1 byte, D2 byte and D3 byte, respectively.
  • the O code area is after the D3 byte; the last 28 bits are 0x0000000.
  • the 0x4B code block is the standard Ethernet IEEE 802.3-2015 standard.
  • a class of control code blocks as defined in Figure 82-5.
  • the fault clearing information in the above example may be an operation, maintenance, and maintenance (OAM) message block indicating the normal operation of the client.
  • the OAM message block may also include error detection, fault detection, and delay measurement in the network. Mechanisms such as path discovery.
  • the OAM message block of the fault clearing information can be carried on the 0x4B code block.
  • FIG. 11 is a schematic diagram showing the fault clearing information based on the 0x4B code block shown in FIG. 10 provided by the embodiment of the present application.
  • FIG. 12 is a schematic diagram showing local fault information based on the 0x4B code block shown in FIG. 10 according to an embodiment of the present application
  • FIG. 13 exemplarily shows an embodiment based on FIG. 10 according to FIG. Schematic diagram of the remote fault information of the 0x4B code block.
  • the sync header is "10”
  • the block type area is 0x4B
  • the D1 byte is 0x00
  • the D2 byte is 0x00
  • the D3 byte is 0x01
  • the D code is O code.
  • the area is 0x0; the last 28 bits are 0x0000000.
  • the sync header is "10"
  • the block type area is 0x4B
  • the D1 byte is 0x00
  • the D2 byte is 0x00
  • the D3 byte is 0x02
  • the D3 byte is O.
  • the code area is 0x0; the last 28 bits are 0x0000000.
  • the local fault information and the remote fault information are distinguished by the D3 byte.
  • the second type of fault information in this embodiment of the present application may be carried by a 0x4B code block.
  • the second type of fault information may be an OAM message block.
  • FIG. 14 is a schematic diagram showing a second type of fault information based on the 0x4B code block shown in FIG. 10 according to an embodiment of the present application.
  • the second type fault information carries a 0x4B control type “0x4B”.
  • "0x6" of the O code area using D1, D2 bytes to carry a specific message block.
  • the first six bits of the D1 byte are used as the OAM message type field, and the 0th to fifth bits in the D1 byte are "0b000001", which indicates that the 0x4B code block carries the second type of fault information.
  • the second type of fault information can be called customer service information (Client Service, CS); the last 2 bits of D1 byte (6th to 7th bits of D1 byte) and the first two bits of D2 byte (D2 word)
  • the 0th to the 1st bits of the section indicate the CSF, the RCSF, and the bearer service (such as an Ethernet service, which may be called an Ethernet service) under normal circumstances.
  • the 6th to 7th bits of the D1 byte and the 0th to the 1st bits of the D2 byte are "1110"
  • the 0th to 1st bits of the bit and the D2 byte are "1111”, indicating that the 0x4B code block carries the CSF; for example, the 6th to 7th bits of the D1 byte and the 0th to the 1st bit of the D2 byte are " 0100" indicates that the 0x4B code block carries normal service information (such as Ethernet service service information), and may also indicate fault clearing. That is, the 6th to 7th bits of the D1 byte and the 0th to 1st bits of the D2 byte are "0100", which may indicate that the 0x4B code block carries the fault clearing information.
  • FIG. 15 is a schematic diagram showing a customer service type local fault information based on the 0x4B code block shown in FIG. 10 according to an embodiment of the present application
  • FIG. 16 exemplarily shows a graph based on the embodiment of the present application.
  • 10 is a schematic diagram of the remote service fault information of the customer service type of the 0x4B code block.
  • the synchronization header is "10”
  • the block type area is 0x4B
  • the D1 byte is 0b00000111
  • the D2 byte is 0b11000000
  • the D3 byte is 0x06, after the D3 byte.
  • the O code area is 0x6; the last 28 bits are 0x0000000.
  • the sync header is "10"
  • the block type area is 0x4B
  • the D1 byte is 0b00000111
  • the D2 byte is 0b10000000
  • the D3 byte is 0x06, in the D3 byte.
  • the O code area is 0x6; the last 28 bits are 0x0000000.
  • the O-code area of the customer service type local failure information and the customer service type remote failure information is 0x6, and the local failure information and the remote failure information shown in FIG. 12 and FIG.
  • the code area is 0x0.
  • FIG. 17 is a schematic diagram of a communication device according to an embodiment of the present disclosure.
  • the communication device 4101 may be a network device, or may be a chip or a circuit, such as A chip or circuit of a network device.
  • the communication device can implement the steps performed by the communication device in any one or more of the corresponding methods as shown in Figures 7 and/or 8 above.
  • the communication device 4101 can include a fault information processing module 4201 and at least two ports.
  • the communication device 4101 can include a fault information processing module 4201 and at least one first type port and at least one second type port, such as a first port 4102 and a second port 4103.
  • the communication device 4101 can include a fault information processing module 4201 and at least two first type ports, such as a sixth port 4107 and a seventh port 4108.
  • the communication device 4101 can include a fault information processing module 4201 and at least two second type ports, such as a third port 4104 and a seventh port 4105.
  • the first port to the seventh port are schematically illustrated in FIG. 17 .
  • two ports of the same type may be the same port, for example, the fourth port 4105 and the fifth port 4106 may be the same port.
  • two ports are drawn in the figure.
  • the first port 4102 and the sixth port 4107 may be the same port, but in order to clearly describe the embodiment of the present application, two ports are drawn in the figure.
  • two ports of different types may also be the same port.
  • the sixth port 4107 and the third port 4104 may be the same port, and the port can support standard Ethernet protocol and flexible Ethernet protocol.
  • the port can be called the sixth port 4107.
  • the port currently uses the flexible Ethernet protocol to send and receive information
  • the port can be called the third port 4104, but for clarity
  • the embodiment of the present application is drawn as two ports in the figure.
  • the first port in FIG. 7 above It may be the first port 4102 in the communication device 4101, and the second port in FIG. 7 above may be the second port 4103 in the communication device 4101.
  • the first port in FIG. 8 above It may be the first port 4102 in the communication device 4101, and the second port in FIG. 8 above may be the second port 4103 in the communication device 4101.
  • the communication device 4101 implements the steps performed by the communication device in the method corresponding to any one or more of the foregoing steps shown in FIG. 7 and FIG. 8, the first in FIG. 7 and FIG. 8 described above.
  • the port may be the first port 4102 in the communication device 4101, and the second port in Figures 7 and 8 above may be the second port 4103 in the communication device 4101.
  • the communication device 4101 implements the steps performed by the communication device in the method corresponding to any one or more of the foregoing steps shown in FIG. 7 and FIG. 8, the foregoing FIG. 7
  • the first port of the communication device 4101 may be the first port 4102 of the communication device 4101, and the second port of FIG.
  • the first type of port other than the first port 4102, the second port in FIG. 7 above may be a second type of port other than the second port 4103 in the communication device 4101.
  • the first port 4102, the sixth port 4107, and the seventh port 4108 are first type ports, and the first type port is not configured with RS, the second port 4103, the third port 4104, the fourth port 4105, and the first port.
  • the five ports 4106 are the second type of ports, and the second type of ports are not configured with the RS.
  • the remaining related descriptions of the first type of port and the second type of port can participate in the foregoing, and are not described herein again.
  • the fault information processing module 4201 in the embodiment of the present application may be distributed, and each port is correspondingly disposed. As shown in FIG. 2 above, it is integrated on each port.
  • the fault information processing module 4201 includes the first type of port in FIG.
  • the fault information processing module 4201 in the embodiment of the present application may be centralized, and each port shares one, that is, the fault information processing module 4201 can be independent and connected to each port.
  • the fault information processing module may be disposed on one side of the first type of port or on one side of the second type of port, and only the illustration of one side of the first type of port is shown.
  • the fault information processing module 4201 may be disposed on the physical port of each port if it is disposed on the side of the first type port; if it is disposed on the side of the second type port, it may be set above the physical layer of each port, or may be set to be flexible in each port. Above the network protocol layer.
  • the communication device 4101 further includes a switching unit 4301.
  • the switching unit 4301 may be the switching unit 1701 in FIG. 2, where the association relationship between the ports is stored, and the ports may be updated. Relationships and so on. For related introductions, refer to the foregoing description about the switching unit 1701, and details are not described herein again.
  • the first port 4102 and the second port 4103 are associated with each other, and the sixth port 4107 and the seventh port 4108 are associated with each other, and the third port 4104 and the fourth port are connected to each other. There is an association between ports 4105.
  • association relationship between the ports may be pre-configured, and the association relationship may be updated, for example, according to a new association relationship input by the user, or updated according to internal self-healing mechanism policies (such as the foregoing content).
  • the update of the association relationship caused by enabling the alternate link) and so on.
  • the first port 4102 in the embodiment of the present application is configured to obtain the first fault information, for example, may receive the first fault information sent by another port or be generated by the physical layer of the first port 4102.
  • the type port transmits information according to a standard Ethernet protocol; the first fault information is a first type of fault information, the first type of fault information includes at least one of local fault information and remote fault information; and the second port 4103 is a second type of port.
  • the second type of port transmits information according to the flexible Ethernet protocol; the second type of fault information is the second type of fault information, and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty.
  • the first fault information is obtained by using the first port, and the second fault information is sent by the second port according to the first fault information, where the first port is a first type port, and the first type port is according to a standard Ethernet.
  • the protocol transmits information
  • the first fault information is the first type of fault information
  • the second port is the second type of port
  • the second type of port transmits information according to the flexible Ethernet protocol
  • the first type of fault information includes the local fault information and the remote end.
  • At least one of the fault information, the second fault information is a second type of fault information, and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty, so the method for transmitting the second fault information may be
  • the fault is reported in the joint networking of the standard Ethernet protocol and the flexible Ethernet protocol. It can also lay the foundation for distinguishing between the link failure corresponding to the flexible Ethernet protocol and the link failure of the standard Ethernet protocol.
  • the fault information processing module 4201 is configured to generate second fault information according to the first fault information, if the obtained first type fault information meets the first preset condition, where the first preset The condition includes: obtaining, by the first preset duration, a quantity of the first type of fault information that is greater than the first quantity threshold; or obtaining a first preset code block that is not less than the first quantity threshold, and obtaining any two The interval between adjacent first preset code blocks does not exceed the first preset code block interval. In this way, erroneous operations caused by a small amount of fault information can be avoided, and the accuracy of the operation can be further improved.
  • the embodiment of the present application further provides a communication device.
  • the second port 4103 in the communication device is configured to obtain third fault information.
  • the second type of fault information; the fault information processing module 4201 is further configured to generate fourth fault information according to the third fault information; wherein the fourth fault information is the first type of fault information; the first port 4102 is further configured to send The fourth fault information.
  • the first port is a first type port, the first type port transmits information according to a standard Ethernet protocol, the second port is a second type port, and the second type port transmits information according to a flexible Ethernet protocol.
  • the first type of fault information includes at least one of local fault information and remote fault information, and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty.
  • the third fault information is obtained by using the second port, and the fourth fault information is sent by using the first port according to the third fault information, where the first type fault information includes at least one of local fault information and remote fault information.
  • the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty. Therefore, by transmitting the second fault information, the fault can be reported in the standard Ethernet protocol and the flexible Ethernet protocol joint network. It can lay a foundation for distinguishing between the link failure corresponding to the flexible Ethernet protocol and the link failure of the standard Ethernet protocol; the third can also be compatible with the scheme of notifying the fault through the first type of fault information transmission in the standard Ethernet protocol network.
  • the fault information processing module 4201 is configured to generate fourth fault information according to the third fault information, if the obtained second type fault information meets the second preset condition, where the second preset The condition includes that the number of third fault information obtained within the second preset duration is greater than the second threshold; or; obtaining a second preset code block having a quantity not less than the second number threshold, and obtaining any two adjacent The interval between the second preset code blocks does not exceed the second preset code block interval. In this way, erroneous operations caused by a small amount of fault information can be avoided, and the accuracy of the operation can be further improved.
  • the communication device 4101 may further have other possible implementations in the embodiment in which the communication method shown in FIG. 7 and/or FIG. 8 described above is performed.
  • the following describes the communication device 4101 performing the above-described FIG. 7 and/or FIG. Other alternative embodiments of the communication method shown in FIG.
  • the communication device 4101 further includes a third port 4104, configured to obtain a fifth fault information, where the third port 4104 is a second type of port, and the fifth fault information is a first type of fault information or a
  • the second type of fault information includes a fourth port 4105 for transmitting the fifth fault information, wherein the fourth port 4105 is a second type of port.
  • the first type of fault information and the second type of fault information can be transparently transmitted inside the flexible Ethernet network, so that the second type of fault information can be transmitted inside the flexible Ethernet network, and the first type of fault is transmitted outside the flexible Ethernet network.
  • the information can be used to distinguish whether the link corresponding to the flexible Ethernet protocol is faulty or the link corresponding to the standard Ethernet protocol is faulty according to the type of the fault information.
  • the communication device 4101 further includes a fifth port 4106, configured to obtain a sixth fault information, wherein the fifth port 4106 is a second type of port, and the sixth fault information is a first type of fault information;
  • the five port 4106 configures the standby link; the alternate link corresponding to the fifth port 4106 is enabled.
  • the link corresponding to the standard Ethernet protocol is faulty and the link corresponding to the flexible Ethernet protocol is faulty is distinguished by using the first type of fault information and the second type of fault information, thereby avoiding
  • the link corresponding to the standard Ethernet protocol triggers the protection switching function.
  • the protection switching function can be triggered based on the fault information inside the flexible Ethernet protocol network.
  • the second port 4103 is configured to send at least two second fault information; wherein, at least one of the at least one second fault information is separated by at least one code block.
  • the transmission frequency of the second fault information can be flexibly set. For example, if the transmission frequency of the second fault information is set to be smaller than the transmission frequency of the first fault information, the bandwidth of the transmission path of the link corresponding to the flexible Ethernet protocol can be saved.
  • the first fault information is the remote fault information
  • the second fault information is the customer service type remote fault information
  • the remote fault information is continuous transmission, occupying a large bandwidth, and setting a certain number of code blocks to send one. Customer service type remote fault information can save bandwidth.
  • the division of the unit in the embodiment of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • FIG. 18 is a schematic diagram of a communication device according to an embodiment of the present disclosure.
  • the communication device 5300 may be a network device, or may be a chip or a circuit, such as A chip or circuit of a network device.
  • the communication device can implement the steps performed by the communication device in any one or more of the corresponding methods as shown in Figures 7 and/or 8 above.
  • the communication device 4101 can include a processor 5301, a transceiver 5302, a memory 5303, and a communication interface 5304; wherein the processor 5301, the transceiver 5302, the memory 5303, and the communication interface 5304 are connected to one another via a bus 5305.
  • the bus 5305 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 18, but it does not mean that there is only one bus or one type of bus.
  • the memory 5303 may include a volatile memory such as a random-access memory (RAM); the memory may also include a non-volatile memory such as a flash memory.
  • RAM random-access memory
  • non-volatile memory such as a flash memory.
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory 5303 may also include a combination of the above types of memories.
  • the communication interface 5304 can be a wired communication access port, a wireless communication interface, or a combination thereof, wherein the wired communication interface can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless communication interface can be a WLAN interface.
  • the communication interface 5304 may be each of the above ports, such as a first type of port and a second type of port, such as the first port 4102, the second port 4103, the third port 4104, the fourth port 4105, and the fifth port 4106 in FIG.
  • the processor 5301 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor 5301 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory 5303 can also be used to store program instructions
  • the processor 5301 calls the program instructions stored in the memory 5303, can control the transceiver 5302 to perform signal reception and signal transmission, and can execute the embodiment in the embodiment shown in the foregoing solution.
  • One or more steps, or alternative embodiments thereof, cause communication device 5300 to implement the functionality of the communication device in the above method.
  • the processor is configured to obtain the first fault information by using the first port, and control the transceiver to send the second fault information by using the second port according to the first fault information, where the transceiver is configured to send the second through the second port.
  • the first port is a first type of port, and the first type of port transmits information according to a standard Ethernet protocol; the first fault information is a first type of fault information, and the first type of fault information includes a local fault information and a remote fault.
  • the second port is a second type of port, the second type of port transmits information according to a flexible Ethernet protocol;
  • the second type of fault information is a second type of fault information, and the second type of fault information is used to indicate a standard type of Ethernet The link corresponding to the protocol has failed.
  • the first fault information is obtained by using the first port, and the second fault information is sent by the second port according to the first fault information, where the first port is a first type port, and the first type port is according to a standard Ethernet.
  • the protocol transmits information
  • the first fault information is the first type of fault information
  • the second port is the second type of port
  • the second type of port transmits information according to the flexible Ethernet protocol
  • the first type of fault information includes the local fault information and the remote end.
  • At least one of the fault information, the second fault information is a second type of fault information, and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty, so the method for transmitting the second fault information may be
  • the fault is reported in the joint networking of the standard Ethernet protocol and the flexible Ethernet protocol. It can also lay the foundation for distinguishing between the link failure corresponding to the flexible Ethernet protocol and the link failure of the standard Ethernet protocol.
  • the processor is configured to: when the first type of fault information obtained meets the first preset condition, send the second fault information by using the second port according to the first fault information;
  • the first preset condition includes: obtaining, by the first preset duration, a quantity of the first type of fault information that is greater than the first quantity threshold; or obtaining a first preset code block that is not less than the first quantity threshold, and obtaining The interval between any two adjacent first preset code blocks does not exceed the first preset code block interval.
  • the embodiment of the present application further provides a communications device.
  • the processor in the communications device is further configured to obtain third fault information by using the second port.
  • the fault information is the second type of fault information.
  • the third fault information is sent by the control transceiver according to the third fault information.
  • the fourth fault information is the first type of fault information.
  • the first port is a first type port, the first type port transmits information according to a standard Ethernet protocol, the second port is a second type port, and the second type port transmits information according to a flexible Ethernet protocol.
  • the first type of fault information includes at least one of local fault information and remote fault information, and the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty.
  • the third fault information is obtained by using the second port, and the fourth fault information is sent by using the first port according to the third fault information, where the first type fault information includes at least one of local fault information and remote fault information.
  • the second type of fault information is used to indicate that the link corresponding to the standard Ethernet protocol is faulty. Therefore, by transmitting the second fault information, the fault can be reported in the standard Ethernet protocol and the flexible Ethernet protocol joint network. It can lay a foundation for distinguishing between the link failure corresponding to the flexible Ethernet protocol and the link failure of the standard Ethernet protocol; the third can also be compatible with the scheme of notifying the fault through the first type of fault information transmission in the standard Ethernet protocol network.
  • the processor is configured to: when the second type of fault information obtained meets the second preset condition, send the fourth fault information by using the first port according to the third fault information;
  • the second preset condition includes: the number of the third fault information obtained in the second preset duration is greater than the second threshold; or; obtaining the second preset code that is not less than the second threshold, and obtained The interval between any two adjacent second preset code blocks does not exceed the second preset code block interval.
  • the communication device 5300 may further have other possible implementations in the embodiment in which the communication method shown in FIG. 7 and/or FIG. 8 described above is performed.
  • the following describes the communication device 5300 performing the above-described FIG. 7 and/or FIG. Other alternative embodiments of the communication method shown in FIG.
  • the processor is further configured to obtain the fifth fault information by using the third port, where the third port is the second type of port, and the fifth fault information is the first type of fault information or the second type of fault.
  • the transceiver is further configured to send the fifth fault information by using the fourth port; wherein the fourth port is the second type of port.
  • the processor is further configured to obtain the sixth fault information by using the fifth port, where the fifth port is the second type of port, the sixth fault information is the first type of fault information, and the fifth port is configured. Alternate link; enable the alternate link corresponding to the fifth port.
  • the processor is configured to: according to the first fault information, control the transceiver to send at least two second fault information through the second port; wherein any two of the at least one second fault information are second The fault information is separated by at least one code block.
  • FIG. 19 is a schematic diagram of a communication device according to an embodiment of the present disclosure.
  • the communication device 6101 may be a communication device in the foregoing content, and may be, for example, the one in FIG.
  • the communication device 5300 may be the communication device 4101 in FIG. 17 described above, or may be the children's shoe device 1301 in FIG. 2 and FIG. 3 described above, or may be the communication device in FIG. 2 to FIG. 6 and FIG.
  • Communication device 6101 may also be referred to as a packet bearer device.
  • the communication device 6101 provided by the embodiment of the present application can be landed on a network device supporting 1.5 layer switching, and the communication device (or network device) product form includes a network protocol-based radio connection supporting a port of a flexible Ethernet protocol.
  • IPRAN Internet Protocol Radio Access Network
  • PTN Packet Transport Network box or box switch equipment.
  • the solution for landing products in the embodiment of the present application may be implemented by adding an FPGA between an existing second type port (also referred to as a FlexE port) chip and a PHY chip of a standard Ethernet protocol port, such as adding the FPGA implementation.
  • the solution executed by the fault information processing module may be implemented in a chip of a second type (also referred to as a FlexE port), such as implementing the solution executed by the fault information processing module in the chip, thereby implementing the 66 bit.
  • a chip of a second type also referred to as a FlexE port
  • the communication device 6101 may include a main control switch board 6104, an interface board 6102, and an interface board 6103.
  • the main control switch board 6104 may be an exchange unit in the above content, such as the exchange unit 4301 in FIG. 17 and the exchange unit 1701 in FIG.
  • the switching unit or the main control switch board is not shown in other figures, but each port is connected through a main control switch board or a switching unit.
  • the main control switchboard 6104 includes a network processor (NP) or a switch fabric chip 6203.
  • the network processor (NP) or the switch fabric chip 6203 may be part of the processor 5301 in FIG. 18 described above.
  • the interface board 6102 can be a user side interface board, and can include a user side interface chip 6201.
  • the user-side interface chip 6201 may be the first type of port, for example, the first port 4102 in FIG. 17 or the first type port 2202 in FIG.
  • the user side interface chip 6201 is connected to the main control switch board 6104 through an interface.
  • the fault information processing module 6105 may be integrated in the user side interface chip 6201, and the fault information processing module 6105 may be distributed, for example, one integrated on each user side interface chip, or may be centralized, such as multiple One of the user side interface chips is shared.
  • the fault information processing module 6105 may be the fault information processing module 4201 in FIG. 17 described above, or may be at least one of the fault information processing module 1601, the fault information processing module 1602, and the fault information processing module 1603 in FIG.
  • the interface board 6103 can be a network side interface board, and can include a network side interface chip 6202.
  • the network side interface chip 6202 may be the second type port described above, and may be, for example, the second port 4103 in FIG. 17 or the first type port 2205 in FIG.
  • the network side interface chip 6202 is connected to the main control switch board 6104 through an interface.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the size of the serial numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of cells is only a logical function division.
  • multiple units or components may be combined or integrated. Go to another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • a computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, computer instructions can be wired from a website site, computer, server or data center (eg Coax, fiber, digital subscriber line (DSL) or wireless (eg, infrared, wireless, microwave, etc.) is transmitted to another website, computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • Useful media can be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Small-Scale Networks (AREA)
  • Communication Control (AREA)

Abstract

一种通信方法、设备及存储介质，用于实现标准以太网协议和灵活以太网协议联合组网中故障信息的传输。本申请实施例中通过第一端口获得第一故障信息，根据第一故障信息通过第二端口发送第二故障信息，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息，第一故障信息为第一类型故障信息，第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息，第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二故障信息为第二类型故障信息，第二类型故障信息用于指示标准以太网协议对应的链路发生故障，从而可以在标准以太网协议和灵活以太网协议联合组网中通报故障。

Description

一种通信方法、设备及存储介质
本申请要求在2017年08月09日提交中国专利局、申请号为201710677029.7、发明名称为“一种通信方法、设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法、设备及存储介质。
背景技术
电气和电子工程师协会(Institute of Electrical and Electronics Engineers,IEEE)下属的802.3工作组所定义的802.3标准以太网(Standard Ethernet，StdE)的相关标准在业界被广泛引用。标准以太网以其原理简单、便于实现同时又价格低廉的优势受到厂商的极大欢迎。但是随着技术的发展，带宽颗粒差异越来越大，标准以太网的端口与实际应用需求的偏差也越来越大。很可能出现的一种情况是：主流的应用需求带宽不属于任何一种现有以太网标准速率，比如：50Gb/s的业务如果用100GE端口来承载存在资源浪费，而200Gb/s的业务目前还没有对应的以太网标准颗粒可以承载。
为了应对这一挑战，光互联网论坛(Optical Internet Forum,OIF)发布了灵活以太网(Flexible Ethernet,FlexE)，FlexE是一种支持多种以太网MAC层速率的通用技术。通过将多个100GE(Physical，PHYs)端口绑定，并将每个100GE端口在时域上以5G为颗粒划分为20个时隙，FlexE可支持以下功能：绑定，将多个以太网端口绑定为一个链路组以支持速率大于单个以太网端口的媒体访问控制(Medium Access Control，MAC)业务；子速率，通过为业务分配时隙支持速率小于链路组带宽或者小于单个以太网端口带宽的MAC业务；通道化，通过为业务分配时隙支持在链路组中同时传输多个MAC业务，例如在2x100GE链路组中支持同时传输一个150G和两个25G的MAC业务。
图1示出了现有技术中一种可能的通信系统架构示意图，如图1所示，包括第一以太网设备1101和第二以太网设备1201，其中，第一以太网设备1101包括介质相关端口(Medium Dependent Interface，MDI)1102(图中为表述清楚写为MEDIUM1102)、物理层、媒介无关端口(Media Independent Interface，MII)1107、协调子层(Reconciliation Sublayer，RS)1108、媒体访问控制(Medium Access Control，MAC)层1109和上层(Upper layer)1110。其中，第一以太网设备1101的物理层可以包括物理媒介相关子层(Physical Medium Dependent，PMD)1104、物理媒介接入子层(Physical Medium Attachment，PMA)1105和物理编码子层(Physical Coding Sublayer，PCS)1106。上层(Upper layer)1110中可以包括网络协议(Internet Protocol，IP)层和传输控制协议(Transfer Control Protocol，TCP)层等。相应地，第二以太网设备1201包括介质相关端口(Medium Dependent Interface，MDI)1202(图中为表述清楚写为MEDIUM1202)、物理层、MII1207、RS1208、MAC层1209和上层(Upper layer)1210。其中，第二以太网设备1201的物理层可以包括PMD1204、PMA1205和PCS1206。上层(Upper layer)1210中可以包括IP层和TCP层等。
IEEE 802.3标准文档81.3.4章节定义40GE/100GE标准以太网协议中的本地故障信息(Local Fault，LF)和远端故障信息(Remote Fault)，其中，本地故障信息可以是指远端 RS和本地RS之间发生故障(英文可以为Faults detected between the remote RS and the local RS)，远端故障信息可以是当RS检测到LF时由RS生成RF(RF signal originated at RS when RS detects LF)。在协议中规定了本地RS与远端RS子层协商链路故障状态的机制，以及基于LF和RF的64b/66bit Block的发送和处理机制。
如图1所示，从第二以太网设备1201发送信息至第一以太网设备1101的链路发生故障，第一以太网设备1101中的物理层(比如PMD1104)检测到链路故障，PMD1104、PMA1105或PCS1106会生成LF并上送给上层功能单元，直至RS1108接收到LF。RS1108若检测到PCS1106通过MII1107端口上送的LF，则停止上层MAC数据流往PCS1106的下插，并向PCS1106持续下插RF，发往第二以太网设备1201。若第一以太网设备1101至第二以太网设备1201的发送链路完好，则RF可以抵达第二以太网设备1201。
第二以太网设备1201的RS1208检测到RF，停止上层MAC数据流往PCS1206的下插，并向PCS1206持续下插Idle控制块流(可以参见IEEE 802.3-2015Section 6中81.3.4章节)，Idle控制块流从第二以太网设备1201发往第一以太网设备1101，由于从第二以太网设备1201发往第一以太网设备1101的发送链路出现故障，因此Idle控制块流并不会抵达第一以太网设备1101。
通过上述示例可以看出，现有技术中可以在以太网设备中通过传输LF和RF实现故障协商，而以太网设备中的RS可以终结故障信息并停止MAC层数据流的发送。基于已经提出的灵活以太网协议，将标准以太网协议和灵活以太网协议联合组网势在必行，而目前针对标准以太网协议和灵活以太网协议联合组网还没有故障信息的传输方案。
综上所述，亟需一种通信方案用于实现标准以太网协议和灵活以太网协议联合组网中故障信息的传输。
发明内容
本申请实施例提供一种通信方法、设备及存储介质，用于实现标准以太网协议和灵活以太网协议联合组网中故障信息的传输。
第一方面，本申请实施例提供一种通信方法，该方法包括通过第一端口获得第一故障信息；其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息；第一故障信息为第一类型故障信息，第一类型故障信息包括本地故障信息和远端故障信息中的至少一项；根据第一故障信息，通过第二端口发送第二故障信息；其中，第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息；第二故障信息为第二类型故障信息，第二类型故障信息用于指示标准以太网协议对应的链路发生故障。
本申请实施例中通过第一端口获得第一故障信息，根据第一故障信息，通过第二端口发送第二故障信息，其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息，第一故障信息为第一类型故障信息，第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息，且由于第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二故障信息为第二类型故障信息，第二类型故障信息用于指示标准以太网协议对应的链路发生故障，因此通过传输第二故障信息的方式既可以在标准以太网协议和灵活以太网协议联合组网中通报故障，也可以为区分灵活以太网协议对应的链路发生故障和标准以太网协议对应的链路发生故障奠定基础。
在一种可能的设计中，根据第一故障信息，通过第二端口发送第二故障信息，包括： 若获得的第一类型故障信息满足第一预设条件，则根据第一故障信息，通过第二端口发送第二故障信息；其中，第一预设条件包括在第一预设时长内获得的第一类型故障信息的数量大于第一数量阈值；或者；获得数量不少于第一数量阈值的第一预设码块，且获得的任两个相邻的第一预设码块之间间隔不超过第一预设码块间隔。如此，可以避免因为数量较少的故障信息导致的误操作，进一步提高操作的准确性。
在一种可能的设计中，方法还包括通过第二端口获得第三故障信息；其中，第三故障信息为第二类型故障信息；根据第三故障信息，通过第一端口发送第四故障信息；其中，第四故障信息为第一类型故障信息。如此，可以在灵活以太网网络内部传输第二类型故障信息，在灵活以以太网网络外部传输第一类型故障信息，从而可以根据故障信息的类型区分灵活以太网协议对应的链路发生故障还是标准以太网协议对应的链路发生故障。
在一种可能的设计中，根据第三故障信息，通过第一端口发送第四故障信息，包括若获得的第二类型故障信息满足第二预设条件，则根据第三故障信息，通过第一端口发送第四故障信息；其中，第二预设条件包括：在第二预设时长内获得的第三故障信息的数量大于第二数量阈值；或者；获得数量不少于第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔。如此，可以避免因为数量较少的故障信息导致的误操作，进一步提高操作的准确性。
在一种可能的设计中，方法还包括通过第三端口获得第五故障信息；其中，第三端口为第二类型端口，第五故障信息为第一类型故障信息或者第二类型故障信息；通过第四端口发送第五故障信息；其中，第四端口为第二类型端口。如此，在灵活以太网网络内部可以透传第一类型故障信息和第二类型故障信息，进而可以在灵活以太网网络内部传输第二类型故障信息，在灵活以以太网网络外部传输第一类型故障信息，从而可以根据故障信息的类型区分灵活以太网协议对应的链路发生故障还是标准以太网协议对应的链路发生故障。
在一种可能的设计中，方法还包括通过第五端口获得第六故障信息；其中，第五端口为第二类型端口，第六故障信息为第一类型故障信息；第五端口配置备用链路；启用第五端口对应的备用链路。可见，本申请实施例中可以实现将标准以太网协议对应的链路发生故障和灵活以太网协议对应的链路发生故障的情况通过第一类型故障信息和第二类型故障信息进行区分，从而避免标准以太网协议对应的链路发生故障触发保护倒换功能的情况；而且可以更加准确的根据灵活以太网协议网络内部的故障信息触发保护倒换功能。
在一种可能的设计中，根据第一故障信息，通过第二端口发送第二故障信息，包括根据第一故障信息，通过第二端口发送至少两个第二故障信息；其中，至少两个第二故障信息中的任两个第二故障信息之间间隔至少一个码块。如此，可以灵活设置第二故障信息的发送频率，比如将第二故障信息的发送频率设置的小于第一故障信息的发送频率，则可以节省灵活以太网协议对应的链路的传输路径的带宽。举个例子，比如第一故障信息为远端故障信息，第二故障信息为客户服务类型远端故障信息，远端故障信息为持续发送，占用带宽较大，设置间隔一定数量的码块发送一个客户服务类型远端故障信息，则可以节省带宽。
第二方面，本申请实施例提供一种通信方法，该方法包括通过第二端口获得第三故障信息；根据第三故障信息，通过第一端口发送第四故障信息；其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息；第四故障信息为第一类型故障信息； 第一类型故障信息包括本地故障信息和远端故障信息中的至少一项；第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息；第三故障信息为第二类型故障信息；第二类型故障信息用于指示标准以太网协议对应的链路发生故障。
本申请实施例中通过第二端口获得第三故障信息，根据第三故障信息，通过第一端口发送第四故障信息，由于第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二类型故障信息用于指示标准以太网协议对应的链路发生故障，因此通过传输第二故障信息的方式既可以在标准以太网协议和灵活以太网协议联合组网中通报故障，也可以为区分灵活以太网协议对应的链路发生故障和标准以太网协议对应的链路发生故障奠定基础；第三也可以兼容标准以太网协议网络中通过第一类型故障信息传输通报故障的方案。
该通信方法中还包括上述第一方面或第一方面中任一种方法，在此不再赘述。
第三方面，本申请实施例提供一种通信设备，通信设备包括存储器、收发器和处理器，其中：存储器用于存储指令；处理器用于根据执行存储器存储的指令，并控制收发器进行信号接收和信号发送，当处理器执行存储器存储的指令时，通信设备用于执行上述第一方面或第一方面中任一种方法。
第四方面，本申请实施例提供一种通信设备，用于实现上述第一方面或第一方面中的任意一种方法，包括相应的功能模块，分别用于实现以上方法中的步骤。
第五方面，本申请实施例提供一种计算机存储介质，计算机存储介质中存储有指令，当其在计算机上运行时，使得计算机执行第一方面或第一方面的任意可能的实现方式中的方法。
第六方面，本申请实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行第一方面或第一方面的任意可能的实现方式中的方法。
附图说明
图1为现有技术中一种可能的通信系统架构示意图；
图2为本申请实施例提供的一种通信设备的结构示意图；
图3为本申请实施例提供的一种通信设备的结构示意图；
图4为本申请实施例提供的一种系统架构示意图；
图5为基于图4所示系统架构的一种故障信息传输路径示意图；
图6为基于图4所示系统架构的另一种故障信息传输路径示意图；
图7为本申请实施例提供的一种通信方法的流程示意图；
图8为本申请实施例提供的一种通信方法的流程示意图；
图9为本申请实施例中提供的基于图4所示系统结构的另一种故障信息传输路径示意图；
图10为本申请实施例提供的一种0x4B的66 bit block码块的示意图；
图11为本申请实施例提供的一种基于图10所示0x4B码块的故障清除信息的示意图；
图12为本申请实施例提供的一种基于图10所示0x4B码块的本地故障信息的示意图；
图13为本申请实施例提供的一种基于图10所示0x4B码块的远端故障信息的示意图；
图14为本申请实施例提供的一种基于图10所示0x4B码块的第二类型故障信息的示意图；
图15为本申请实施例提供的一种基于图10所示0x4B码块的客户服务类型本地故障信息的示意图；
图16为本申请实施例提供的一种基于图10所示0x4B码块的客户服务类型远端故障信息的示意图；
图17为本申请实施例提供的一种通信设备的结构示意图；
图18为本申请实施例提供的另一种通信设备的结构示意图；
图19为本申请实施例提供的另一种通信设备的结构示意图。
具体实施方式
图2示例性示出了本申请实施例提供的一种通信设备的结构示意图。如图2所示，通信设备1301包括两种类型的端口，分别为第一类型端口和第二类型端口，第一类型端口根据标准以太网协议传输信息，第二类型端口根据灵活以太网协议传输信息。通信设备1301可以包括一个或多个第一类型端口，以及一个或多个第二类型端口，比如图2所示第一类型端口1401、第一类型端口1402、第一类型端口1403、第二类型端口1501、第二类型端口1502和第二类型端口1503。第一类型端口对应包括接口和物理层，第一类型端口的物理层包括PMD、PMA和PCS。第二类型端口包括接口、物理层和灵活以太网协议层(英文也可以称为FlexE shim)，第二类型端口的物理层包括PMD、PMA和PCS。第一类型端口和第二类型端口中的接口具体是指电缆的连接口。可选地，第一类型端口物理层之上还包括其它层，比如MAC层等等。本申请实施例中的第一类型端口中不包括RS。可选地，第二类型端口灵活以太网协议层之上还包括其它层，比如MAC层等等。图2中仅仅示意性仅画出第一类型端口的物理层以及第二类型端口的物理层和灵活以太网协议层等。
本申请实施例中第一类型端口可以是仅支持标准以太网协议的端口，这种情况下第一类型端口仅能根据标准以太网协议传输信息。可选地，第一类型端口也可以是支持标准以太网协议和灵活以太网协议这两种协议类型的端口，这种情况下，第一类型端口是指当前使用的协议是标准以太网协议的端口。本申请实施例中第二类型端口可以是仅支持灵活以太网协议的端口，这种情况下第二类型端口仅能根据灵活以太网协议传输信息。可选地，第二类型端口也可以是支持标准以太网协议和灵活以太网协议这两种协议类型的端口，这种情况下，第二类型端口是指当前使用的协议是灵活以太网协议的端口。举个例子，比如第一端口可以支持标准以太网协议和灵活以太网协议，若第一端口在一个时间段内根据标准以太网协议传输信息，则可以在该根据标准以太网协议传输信息的时间段内称第一端口为第一类型的端口，若第一端口在一个时间段内根据灵活以太网协议传输信息，则可以在该根据灵活以太网协议传输信息的时间段内称第一端口为第二类型的端口。
可选地，本申请实施例中还可以包括第三类型端口，第三类型端口根据标准以太网协议传输信息，且第三类型端口中依次包括接口、物理层和RS，以及其它上层功能单元，比如MAC层等等。第三类型端口比如可以是图1中所示的第一以太网设备1101和第二以太网设备1201中的包括RS的端口。可选地，第三类型端口可以是仅支持标准以太网协议的端口，这种情况下第三类型端口仅能根据标准以太网协议传输信息。可选地，第三类型端口也可以是支持标准以太网协议和灵活以太网协议这两种协议类型的端口，这种情况下，第三类型端口是指当前使用的协议是标准以太网协议的端口。
如图2所示，本申请实施例中通信设备1301中还包括故障信息处理模块，故障信息 处理模块可以是一个，也可以是多个，比如图2中的故障信息模块1601、故障信息模块1602和故障信息模块1603。一种可选地实施方式中，故障信息处理模块可以设置在第一类型端口的一侧，比如设置在第一类型端口的物理层的上层中，或者也可以设置在第二类型端口的一侧，比如可以设置在第二类型端口的物理层的上层。一种可选地实施方式中，可以在第一类型端口和第二类型端口连接的链路上设置故障信息模块。本申请实施例中的故障信息处理模块可以执行本申请实施例所提供的方案，比如可以根据第一类型故障信息生成第二类型故障信息，也可以根据第二类型故障信息生成第一类型故障信息等等。
如图2所示，可选地，本申请实施例中还包括交换单元1701，各个端口可以通过交换单元1701连接。交换单元1701在通信设备2102、通信设备2103、通信设备2104中也可以称为1.5层灵活以太网协议交换单元。1.5层可以是灵活以太网协议涉及到的数据传输层，可位于开放式系统互联(Open System Interconnection，OSI)7层模型的物理层和MAC层之间的数据传输层。本申请实施例中涉及到的物理层之上，或者物理层以上，或者物理层的上层等等概念均是指在模型中位于物理层上面的层，比如可以是灵活以太网协议中的1.5层灵活以太网协议层，再比如可以是MAC层等等。端口之间有的关联关系，端口之间的关联关系可以是预先配置的。比如在图2中可以设置第一类型端口1401与第二类型端口1501有关联关系，也就是说，第一类型端口1401与第二类型端口1501连接，且第一类型端口1401获得的信息(该信息默认为需要发送出去的信息；获得的信息可以是收到的其它设备发送的信息，或者是第一类型端口1401生成的信息)都要通过第二类型端口1501发送出去，而第二类型端口1501获得的信息(该信息默认为需要发送出去的信息；获得的信息可以是收到的其它设备发送的信息，或者是第一类型端口1501生成的信息))都要通过第一类型端口1401发送出去。
可选地，一个端口可以与一个或多个端口连接，但是可能有某些连接关系未处于工作状态，举个例子，比如图2中，第一类型端口1401和第二类型端口1501连接，且第一类型端口1401和第二类型端口1502也连接，但是第一类型端口1401和第二类型端口1502的连接当前也未处于工作状态，仅第一类型端口1401和第二类型端口1501的连接当前处于工作状态，也就是说这种情况下第一类型端口1401获得的信息都要通过第二类型端口1501发送出去，而第二类型端口1501获得的信息都要从第一类型端口1401发送出去，这种情况下可以称第一类型端口1401与第二类型端口1501有关联关系，而第一类型端口1401和第二类型端口1502的连接处于未激活状态，可以称未激活状态或者称关联未激活等等，也就是说本申请实施例中端口之间的关联关系是处于工作状态的关联关系。若在下一个时间段内第一类型端口1401和第二类型端口1502的连接当前也处于工作状态，也就是说这种情况下第一类型端口1401获得的信息都要通过第二类型端口1502发送出去，而第二类型端口1502获得的信息都要从第一类型端口1401发送出去，则在该下一个时间段可以称第一类型端口1401和第二类型端口1502之间有关联关系。本申请实施例中下文的两个端口之间有关联关系可以是指这两个端口之间存在连接，且连接处于工作状态，如该示例所解释的内容所示。
本申请实施例中的通信设备可以包括至少两个第一类型端口，也可以包括至少两个第二类型端口，也可以包括至少一个第一类型端口和至少一个第二类型端口。本申请实施例中还可以包括第三类型端口。图3示例性示出了本申请实施例提供的一种通信设备的结构示意图，如图3所示，本申请实施例中通信设备若包括两种类型(为第一类型端口和第二 类型端口)的端口，则第一类型端口和第二类型端口之间可以有关联关系、同一种类型的端口(比如两个第一类型端口，或者两个第二类型端口)之间可以有关联关系，比如图3中第一类型端口1401和第二类型端口1501有关联关系，第一类型端口1402和第一类型端口1403有关联关系，第二类型端口1502和第二类型端口1503有关联关系。
图4示例性示出了本申请实施例提供的一种系统架构示意图，如图4所示，该通信系统包括依次连接的通信设备2101、通信设备2102、通信设备2103、通信设备2104和通信设备2105。其中，通信设备2101的第三类型端口2201与通信设备2102的第一类型端口2202连接，通信设备2102的内部第一类型端口2202和第二类型端口2203有关联关系；通信设备2102的第二类型端口2203与通信设备2103的第二类型端口2204连接，通信设备2103的内部第二类型端口2204和第二类型端口2205有关联关系；通信设备2103的第二类型端口2205与通信设备2104的第二类型端口2206连接，通信设备2104的内部第二类型端口2206和第一类型端口2207有关联关系；通信设备2104的第一类型端口2207与通信设备2105的第三类型端口2208连接。
图4所示的系统架构中各个通信设备中包括的端口仅仅是示意，通信设备2101、通信设备2102、通信设备2103、通信设备2104和通信设备2105中的任一个设备都可以包括至少一个第一类型端口、至少一个第二类型端口和至少一个第三类型端口中的至少一项，本申请实施例不做限制。比如，通信设备2101和通信设备2105可以只包括第三类型端口，这种情况下，通信设备2101和通信设备2105也可以称为以太网设备，也可以称为用户侧设备；可选地通信设备2101和通信设备2105还可以包括至少一个第一类型端口和/或至少一个第二类型端口等。通信设备2103中可以仅包括第二类型端口，可选地通信设备2103还可以包括至少一个第一类型端口和/或至少一个第三类型端口等。通信设备2102和通信设备2104中包括至少一个第一类型端口和至少一个第二类型端口，从而可以用于将第一类型端口传输的信息通过第二类型端口传输。可选地通信设备2102还可以包括至少一个第三类型端口。
可选地，图4中所示的系统架构中，通信设备2102和通信设备2104可以称为PE节点，英文可以写为provider edge，是指运营商网络边缘与用户连接的网络设备，该PE节点上可配置网络之间或网络内设备之间的端口(Network to Network interface，NNI)和用户侧端口，用户侧端口即网络与用户连接的部分的端口(User network interface，UNI)。可选地，用户侧端口可以是第一类型端口，网络之间或网络内设备之间的端口可以是第二类型端口。通信设备2103英文可以称为provider，为运营商网络内的网络设备，可以称为P节点，该P节点上可以仅配置NNI的网络端口。可选地，通信设备2102和通信设备2104之间可以包括一个或多个通信设备2103，也就是说两个PE节点中的每个PE节点连接P节点和以太网设备，两个PE节点之间可以包括至少一个P节点，在这种系统架构下，可以将标准以太网协议对应的信息通过灵活以太网协议进行传输，从而可以更加快速高效的传输数据，实现在标准以太网网络架构下复用灵活以太网协议的目的。
本申请实施例中，如图4所示，通信设备2101和通信设备2105中的第三类型端口中包括RS，为了提高信息传输效率，可选地，可以在通信设备2102、通信设备2103和通信设备2104中的第一类型端口和第二类型端口中不配置RS。本申请实施例中端口之间可互相传输数据，可选地，端口与端口之间可以包括两种类型的链路，一种类型的链路用于从一个端口发送信息至另一个端口，另一种类型的链路用于使该一个端口接收该另一个端口 发送的信息。比如，第三类型端口2201和第一类型端口2202之间可以包括两种类型的链路，可以分别称为第一类型链路和第二类型链路，第一类型链路用于传输从第三类型端口2201发送至第一类型端口2202的信息，第二类型链路用户传输从第一类型端口2202发送至第三类型端口2201的信息。具体实施中，可选地，第一类型链路和第二类型链路可以是一对光纤，分别用于接收和发送，也就是说一对光纤中的一根可以称为第一类型链路，另一根可以称为第二类型链路。
图5示例性示出了基于图4所示系统架构的一种故障信息传输路径示意图，如图5所示，在标准以太网协议中引入FlexE网络后，若在从通信设备2101至通信设备2102的链路上发生故障，比如第三类型端口2201向第一类型端口2202发送信息的链路发生故障，第一类型端口2202检测到链路故障后，第一类型端口2202的物理层会生成本地故障信息(Local Fault，LF)。第一类型端口2202检测到链路故障有多种实现方式，比如第一类型端口2202在预设时长内未收到信息。由于第一类型端口中没有RS，且通信设备2102、通信设备2103、通信设备2104中的第一类型端口和第二类型端口都没有RS，因此第一类型端口2202生成的LF会传输至通信设备2102的1.5层交换单元，交换到第二类型端口2203，由于第二类型端口也无RS，因此LF信息经过灵活以太网协议网络传输，会一直透传至通信设备2105的第三类型端口2208的RS。也就是说，第一类型端口2202生成的LF会沿着第二类型端口2203、第二类型端口2204、第二类型端口2205、第二类型端口2206、第一类型端口2207，最终传至第三类型端口2208的RS。第三类型端口2208的RS在检测到LF信息时，可以停止第三类型端口2208的MAC层的数据发送，并生成RF信息，持续下插到第三类型端口2208的PCS层。该RF信息也沿着第一类型端口2207、第二类型端口2206、第二类型端口2205、第二类型端口2204、第二类型端口2203、第一类型端口2202一直传输至第三类型端口2201的RS中，第三类型端口2201的RS在检测到RF信息时，则停止第三类型端口2201的MAC层的数据发送，生成Idle控制块，持续下插到第三类型端口2201的PCS层。
通过图5所示的示例可以看出，本申请实施例中第一类型端口之间的链路发生故障所生成的故障信息(比如LF和/或RF)会在灵活以太网协议的网络内部传输，由于现有技术中第一类型的端口所生成的LF的频率较高，且RF会持续传输，因此第一类型端口之间的链路发生故障所生成的故障信息占用了较大比例的带宽。基于这个问题，本申请实施例中通过第一端口获得第一故障信息，根据第一故障信息，通过第二端口发送第二故障信息，其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息，第一故障信息为第一类型故障信息，第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息，且由于第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，而本地故障信息和远端故障信息的传输方式占用的传输路径的带宽较大，因此通过传输第二故障信息的方式既可以在标准以太网协议和灵活以太网协议联合组网中通报故障，也可以节省灵活以太网协议对应的链路的传输路径的带宽。
进一步，在标准以太网协议中引入灵活以太网协议网络后，第二类型端口的物理层在检测到故障后也会生成本地故障信息(比如LF)。比如FlexE Implementation Agreement 1.0规范约定，在FlexE端口(即第二类型端口)上检测到信息失效(链路故障)、灵活以太网协议组开销帧(英文可以称为FlexE Group Overhead Frame)同步锁定失败、高误码率、属于同一个灵活以太网协议组(英文可以称为FlexE Group)的多个PHY的对齐失败、在属 于同一个FlexE Group但不同灵活以太网协议物理端口上接收到的灵活以太网协议组开销帧(英文可以称为FlexE Group Overhead Frame)中的PHY映射表、PHY编号、FlexE Group编号字段存在不一致的问题、或多个PHY之间的接收时钟偏差过大，该FlexE物理端口(第二类型端口)上的所有灵活以太网协议客户(英文可以称为FlexE Client)都持续下插以太网LF故障信息。
可选地，可以在配置有第二类型端口的通信设备上配置保护倒换功能，保护倒换功能英文可以称为protection switching，也称为自动保护倒换(Automatic Protection Switching，APS)，具体可以是指数据流量的传输因故障或人工干预的方式从一条工作路径切换到对应该工作路径的保护路径(比如从工作链路切换至备用链路)。通信设备中若配置有保护倒换功能，则在检测到LF时开启保护倒换功能。灵活以太网协议中配置保护倒换功能是为了提供灵活以太网协议下的自愈机制，即若灵活以太网协议网络内部出现故障，可以通过保护倒换功能实现自愈。
图6示例性示出了基于图4所示系统架构的另一种故障信息传输路径示意图，如图6所示，本申请实施例中通信设备之间可以包括至少一条链路，比如通信设备2103和通信设备2104之间包括两条链路，分别为第二类型端口2205和第二类型端口2206之间的链路，以及第二类型端口2301和第二类型端口2302之间的链路。再比如通信设备2103和通信设备2104之间包括两条链路，分别为第二类型端口2205和第二类型端口2206之间的链路，第二类型端口2205和第二类型端口2303之间的链路(此示例图中未示出)。
在一个时间段内可选地通信设备2103和通信设备2104之间只有一条链路处于工作状态，也可以称当前处于工作状态的链路为工作链路，当前未处于工作状态的链路称为备用链路。比如在一个时间段内第二类型端口2205和第二类型端口2206之间的链路处于工作状态，即通信设备2103和通信设备2104之间所需要传输的数据都通过第二类型端口2205和第二类型端口2206之间的链路进行传输，则第二类型端口2205和第二类型端口2206之间的链路称为工作链路，当前未处于工作状态的第二类型端口2301和第二类型端口2302之间的链路称为备用链路；在下一个时间段内第二类型端口2301和第二类型端口2302之间的链路处于工作状态，则第二类型端口2301和第二类型端口2302之间的链路称为工作链路，第二类型端口2205和第二类型端口2206之间的链路称为备用链路。
由于通信设备中若配置有保护倒换功能，则在检测到LF时开启保护倒换功能，如图6所示，在通信设备2104上配置保护倒换功能，比如在通信设备2103和通信设备2104之间设置两条链路，分别为第二类型端口2205和第二类型端口2206之间的链路，以及第二类型端口2301和第二类型端口2302之间的链路。当前工作链路为第二类型端口2205和第二类型端口2206之间的链路。可选地，保护倒换功能可以配置在第二类型端口的物理层之上。可选地，保护倒换功能可以在每个第二类型端口的灵活以太网协议层配置。
一种可能发生故障的情况下，在图6中，若通信设备2103和通信设备2104之间的链路发生故障，比如第二类型端口2205向第二类型端口2206发送信息的链路出现故障，则第二类型端口2206的物理层会生成LF，第二类型端口2206的灵活以太网协议层(图中标识为FlexE shim)接收到LF，则启动保护倒换功能，即启用第二类型端口2206对应的备用链路。也就是说将工作链路从第二类型端口2205和第二类型端口2206之间的链路切换至第二类型端口2301和第二类型端口2302之间的链路，即启用第二类型端口2301和第二类型端口2302之间的链路作为工作链路，第二类型端口2205和第二类型端口2206之 间的链路变更为备用链路。进一步的第二类型端口2204与第二类型端口2301之间有关联关系，而第二类型端口2204和第二类型端口2205的连接处于未激活状态。可见，当灵活以太网协议内部有故障时，灵活以太网协议启用备用链路可以继续进行工作，这个能力也可以称为灵活以太网协议的自愈能力。当启用第二类型端口2205的备用链路的情况下，第二类型端口2302不会再因为第二类型端口2205向第二类型端口2206发送信息的链路出现故障而收到LF。
另一种可能发生故障的情况下，如图6所示，若第三类型端口2201向第一类型端口2202发送信息的链路发生故障，第一类型端口2202检测到链路故障后，第一类型端口2202的物理层会生成LF，LF会传输至通信设备2104，通信设备2104检测到LF后，会触发保护倒换功能，即将第二类型端口2206对应的链路切换至备用链路，也就是说将工作链路从第二类型端口2205和第二类型端口2206之间的链路切换至第二类型端口2301和第二类型端口2302之间的链路，即启用第二类型端口2301和第二类型端口2302之间的链路作为工作链路，第二类型端口2205和第二类型端口2206之间的链路变更为备用链路。在这种情况下，由于第一类型端口2202的物理层在继续生产LF，因此即使在通信设备2104启动保护倒换功能后仍然会收到LF，这种情况下通信设备2104可能会继续启用保护倒换功能，即将工作链路再从第二类型端口2301和第二类型端口2302之间的链路切换至第二类型端口2205和第二类型端口2206之间的链路。可见，由于通信设备收到的LF信息是第一类型端口之间发生故障时生成的，因此该LF即使在通信设备2104启动自动保护倒换功能后仍旧发送通信设备2104，结果导致反复倒换工作链路，出现倒换震荡的情况。也就是说，灵活以太网协议下的保护倒换功能本来是针对灵活以太网协议内部的故障信息实现自愈功能，但是灵活以太网协议网络外的故障信息一旦进入灵活以太网协议，可能会使通信设备误以为该故障信息是灵活以太网协议网络内的故障信息，从而引起返回倒换工作链路，出现倒换振动的情况。针对这种情况，本申请实施例中，由于第二故障信息为第二类型故障信息，且还可以通过第二故障信息将标准以太网协议对应的链路发生故障指示出来，从而可以为区分灵活以太网协议对应的链路发生故障和标准以太网协议对应的链路发生故障奠定基础。
基于上述内容，本申请实施例提供一种通信方法，图7示例性示出了本申请实施例提供的一种通信方法的流程示意图，如图7所示，该方法包括步骤3101至步骤3102。
步骤3101，通信设备通过第一端口获得第一故障信息；其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息；第一故障信息为第一类型故障信息，第一类型故障信息包括本地故障信息和远端故障信息中的至少一项。可选地，通信设备包括多个第一类型端口，第一端口为多个第一类型端口中的、且与至少一个第二类型端口有关联关系的第一类型端口。
本申请实施例中第一类型端口可以是仅支持标准以太网协议的端口，也可以是支持标准以太网协议和灵活以太网协议这两种协议类型的端口，这种情况下，第一类型端口是指当前使用的协议是标准以太网协议的端口。本申请实施例中第二类型端口可以是仅支持灵活以太网协议的端口，也可以是支持标准以太网协议和灵活以太网协议这两种协议类型的端口，这种情况下，第二类型端口是指当前使用的协议是灵活以太网协议的端口。示例可参见上述图2所示相关内容，在此不再赘述。
步骤3102，通信设备根据第一故障信息，通过第二端口发送第二故障信息；其中，第 二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息；第二故障信息为第二类型故障信息，第二类型故障信息用于指示标准以太网协议对应的链路发生故障。可选地，该步骤的通信设备可以是上述图2至图6中包括两种类型端口的通信设备，比如可以是上述图2至图6中的通信设备2102和通信设备2104。在步骤3102中，第一端口和第二端口之间有关联关系，即第一端口获得的信息都通过第二端口传输出去，第二端口获得的信息都从第一端口传输出去。可选地，通信设备包括多个第二类型端口，第二端口为多个第二类型端口中的、且与至少一个第一类型端口有关联关系的第二类型端口。
本申请实施例中可选地，通信设备通过第一类型端口获得第一类型故障信息的情况下，若需要通过第二类型端口发送出去，则通过第二类型端口发送第二类型故障信息。
本申请实施例中通过第一端口获得第一故障信息，根据第一故障信息，通过第二端口发送第二故障信息，其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息，第一故障信息为第一类型故障信息，第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息，且由于第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二故障信息为第二类型故障信息，第二类型故障信息用于指示标准以太网协议对应的链路发生故障，因此通过传输第二故障信息的方式既可以在标准以太网协议和灵活以太网协议联合组网中通报故障，也可以为区分灵活以太网协议对应的链路发生故障和标准以太网协议对应的链路发生故障奠定基础。
基于上述内容，本申请实施例提供另一种通信方法，图8示例性示出了本申请实施例提供的一种通信方法的流程示意图，如图8所示，该方法包括步骤3401至步骤3402。
可选地，执行步骤3401至步骤3402的通信设备和执行步骤3101和步骤3102的通信设备可以是两个不同的通信设备，这种情况下，执行步骤3401至步骤3402的通信设备中包括的第一端口与执行步骤3101和步骤3102的通信设备中的第一端口为不同的两个端口，执行步骤3401至步骤3402的通信设备中包括的第二端口与执行步骤3101和步骤3102的通信设备中的第二端口为不同的两个端口。可选地，执行步骤3101至步骤3102的通信设备可以是图8中的通信设备2102，执行步骤3401至步骤3402的通信设备可以是图8中的通信设备2104，这种情况下，执行步骤3101至步骤3102的通信设备中的第一端口可以是第一类型端口2202，执行步骤3101至步骤3102的通信设备中的第二端口可以是第二类型端口2203；执行步骤3401至步骤3402的通信设备中的第一端口可以是第一类型端口2207，执行步骤3401至步骤3402的通信设备中的第二端口可以是第二类型端口2206。
可选地，执行步骤3401至步骤3402的通信设备也可以是上述执行步骤3101和步骤3102的通信设备，这种情况下，执行步骤3401至步骤3402的通信设备中包括的第一端口与执行步骤3101和步骤3102的通信设备中的第一端口可以为不同的两个端口也可以为相同的两个端口，执行步骤3401至步骤3402的通信设备中包括的第二端口与执行步骤3101和步骤3102的通信设备中的第二端口可以为不同的两个端口也可以为相同的两个端口。这种情况下，步骤3401和步骤3402可以在上述步骤3101和步骤3102之后执行，也可以在步骤3101和步骤3102之前执行。
步骤3401，通信设备通过第二端口获得第三故障信息；根据第三故障信息；第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息；第三故障信息为第二类型故障信息；第二类型故障信息用于指示标准以太网协议对应的链路发生故障；可选地，通信设备包括多个第二类型端口，第二端口为多个第二类型端口中的、且与至少一个第一类 型端口有关联关系的第二类型端口。
本申请实施例中可选地，通信设备通过第二类型端口获得第二类型故障信息的情况下，若需要通过第一类型端口发送出去，则通过第一类型端口发送第一类型故障信息。
本申请实施例中第一类型端口可以是仅支持标准以太网协议的端口，也可以是支持标准以太网协议和灵活以太网协议这两种协议类型的端口，这种情况下，第一类型端口是指当前使用的协议是标准以太网协议的端口。本申请实施例中第二类型端口可以是仅支持灵活以太网协议的端口，也可以是支持标准以太网协议和灵活以太网协议这两种协议类型的端口，这种情况下，第二类型端口是指当前使用的协议是灵活以太网协议的端口。示例可参见上述图2所示相关内容，在此不再赘述。
步骤3402，通信设备通过第一端口发送第四故障信息；其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息；第四故障信息为第一类型故障信息；第一类型故障信息包括本地故障信息和远端故障信息中的至少一项。可选地，该步骤的通信设备可以是上述图2至图6中包括两种类型端口的通信设备，比如可以是上述图2至图6中的通信设备2102和通信设备2104。在步骤3102中，第一端口和第二端口之间有关联关系，即第一端口获得的信息都通过第二端口传输出去，第二端口获得的信息都从第一端口传输出去。可选地，通信设备包括多个第一类型端口，第一端口为多个第一类型端口中的、且与至少一个第二类型端口有关联关系的第一类型端口。
本申请实施例中通过第二端口获得第三故障信息，根据第三故障信息，通过第一端口发送第四故障信息，由于第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二类型故障信息用于指示标准以太网协议对应的链路发生故障，因此通过传输第二故障信息的方式既可以在标准以太网协议和灵活以太网协议联合组网中通报故障，也可以为区分灵活以太网协议对应的链路发生故障和标准以太网协议对应的链路发生故障奠定基础；第三也可以兼容标准以太网协议网络中通过第一类型故障信息传输通报故障的方案。
基于图7和图8所描述的通信方法，下面进一步对上述图7和图8中的几种可能的设计进行阐述，下面的方法项实施例均适用于上述图7和图8所描述的方案。
本申请实施例中，由于本地故障信息和远端故障信息是持续传递的66b block，因此会占用了传输路径的带宽。而应用本申请实施例的方案可以在灵活以太网协议内传输第二类型故障信息，可以灵活设置第二故障信息的发送频率，比如将第二故障信息的发送频率设置的小于第一故障信息的发送频率，则可以节省灵活以太网协议对应的链路的传输路径的带宽。举个例子，比如第一故障信息为远端故障信息，第二故障信息为客户服务类型远端故障信息，远端故障信息为持续发送，占用带宽较大，设置间隔一定数量的码块发送一个客户服务类型远端故障信息，则可以节省带宽。进一步，可将节省的网络带宽用于承载其他业务，包括统计复用等)，还由于第二类型故障信息用于指示标准以太网协议对应的链路发生故障，因此可以避免由于标准以太网协议对应的链路发生故障的情况下误触发保护倒换功能。进一步，本申请实施例中，在采用FlexE组网的情况下，既可以支持标准以太网802.3规范的基于本地故障信息和/或远端故障信息进行链路(英文也可以称为LINK)协商(IEEE 802.3章节81.3.4)，也可以保证灵活以太网协议网络内自愈机制的正确实施。
一种可选地实施方式中，上述步骤3101中，通信设备通过第一端口获得第一故障信息，可以是通信设备通过第一端口的物理层生成本地故障信息；或者可以是通信设备通过 第一端口接收的远端故障信息。举个例子，比如第一端口为第一类型端口2202，图6中，第三类型端口2201发送信息至第一类型端口2202的链路出现故障，则第一类型端口2202的物理层生成本地故障信息。再比如，第一类型端口2202发送信息至第三类型端口2201的链路出现故障，则第三类型端口2201的物理层生成本地故障信息，第三类型端口2201的RS检测到本地故障信息后，生成远端故障信息，该远端故障信息传输至第一类型端口2202。
本申请实施例中可以定义两种类型的第二类型故障信息，分布为客户服务类型本地故障信息和客户服务类型远端故障信息。客户服务类型本地故障信息英文可以称为Client Service Fault，可以简写为CSF，下图9中为表达更加清晰，采用CSF来表示客户服务类型本地故障信息。客户服务类型远端故障信息英文可以称为Remote Client Service Fault，可以简写为RCSF，下图9中为表达更加清晰，采用RCSF来表示客户服务类型远端故障信息。客户服务类型本地故障信息和客户服务类型远端故障信息中的客户服务类型是一种比较上位的说法，具体可以是为客户服务的业务的相关内容；客户服务类型本地故障信息和客户服务类型远端故障信息中的客户服务类型对本申请实施例中的第二类型故障信息不具有限定意义，仅仅用于与本申请实施例中的本地故障信息(英文简写LF)和远端故障信息(英文简写RF)从名字上进行区分。
可选地，根据第一故障信息，通过第二端口发送第二故障信息，包括：根据第一故障信息生成第一故障信息对应的第二故障信息，并通过第二端口发送第二故障信息。其中，第一故障信息为本地故障信息，则第一故障信息对应的第二故障信息为客户服务类型本地故障信息，第一故障信息为远端故障信息，则第一故障信息对应的第二故障信息为客户服务类型远端故障信息。也就是说，可选地，第一类型故障信息为本地故障信息，则第一类型故障信息对应的第二类型故障信息为客户服务类型本地故障信息，第一类型故障信息为远端故障信息，则第一类型故障信息对应的第二类型故障信息为客户服务类型远端故障信息；相应地，第二类型故障信息为客户服务类型本地故障信息，则第二类型故障信息对应的第一类型故障信息为本地故障信息，第二类型故障信息为客户服务类型远端故障信息，则第二类型故障信息对应的第一类型故障信息为远端故障信息。
可选地，根据第一故障信息生成第一故障信息对应的第二故障信息可以是新生成第二故障信息，也可以是在第一故障信息中增加指示信息生成的，该指示信息用于指示标准以太网协议对应的链路发生故障。也就是说，根据第一类型故障信息生成第一类型故障信息对应的第二类型故障信息可以是新生成第二类型故障信息，也可以是在第一类型故障信息中增加指示信息生成的，该指示信息用于指示标准以太网协议对应的链路发生故障。
可选地，上述步骤3102中，通信设备根据第一故障信息，通过第二端口发送第二故障信息，包括：若获得的第一类型故障信息满足第一预设条件，则根据第一故障信息，通过第二端口发送第二故障信息；其中，第一预设条件包括：获得数量不少于第一数量阈值的第一预设码块，且获得的任两个相邻的第一预设码块之间间隔不超过第一预设码块间隔。本申请实施例中在满足“获得数量不少于第一数量阈值的第一预设码块，且获得的任两个相邻的第一预设码块之间间隔不超过第一预设码块间隔”的条件下发送第二故障信息，通信设备可以持续检测获得的第一预设码块的数量，若检测到不满足“获得数量不少于第一数量阈值的第一预设码块，且获得的任两个相邻的第一预设码块之间间隔不超过第一预设码块间隔”的条件，则停止发送第二故障信息。如此，可以避免因为数量较少的故 障信息导致的误操作，进一步提高操作的准确性。
举个例子，第一66 bit block控制块为上述第一预设码块，第一预设码块间隔为128个码块，第一数量阈值为4个，当在检测到4个第一66 bit block(也可以称为第一66比特块)控制块，且任意相邻两个第一66 bit block控制块之间间隔不超过128个码块，则根据第一故障信息，通过第二端口发送第二故障信息。具体检测过程中，可以在检测到第1个第一66 bit block控制块后，计数器记为第1个码块，后面128个block里面如果再检测到1个，计数器记为第2个，如果在后面128个block里面没有再检测到1个第一66 bit block控制块，事件记录清零(即计数器清零)；当下次再检测到第一66 bit block控制块时重新将计数器从1开始计数；如此下来，连续累计检测到4个有效第一66 bit block控制块(即计数器达到4)，则认为获得了LF或RF信息。通信设备持续检测，在计数器的值不小于4的情况下通信设备发送第二故障信息，在计数器的值小于4的情况下停止发送第二故障信息，也就是说，相对应的，如果没有达到条件“获得数量不少于第一数量阈值的第一预设码块，且获得的任两个相邻的第一预设码块之间间隔不超过第一预设码块间隔”，则可以认为故障清除，则不再发送第二故障信息。举个例子，比如通信设备在连续128个码块内没有检测到第一66 bit block控制块，则认为故障清除。
可选地，通信设备根据第一故障信息，通过第二端口发送第二故障信息，包括：若在第一预设时长内获得的第一故障信息的数量大于第一数量阈值，则：根据第一故障信息，通过第二端口发送第二故障信息。可选地，第一故障信息也可以是第一预设码块。也就是说，若获得的第一类型故障信息满足第一预设条件，则根据第一故障信息，通过第二端口发送第二故障信息；其中，第一预设条件包括：在第一预设时长内获得的第一类型故障信息的数量大于第一数量阈值。在这种情况下获得的第一类型故障信息是第一故障信息。本申请实施例中在满足“在第一预设时长内获得的第一故障信息的数量大于第一数量阈值”的条件下发送第二故障信息，通信设备持续检测获得的第一故障信息的数量，若检测到不满足“在第一预设时长内获得的第一故障信息的数量大于第一数量阈值”的条件，则停止发送第二故障信息。
举个例子，第一66 bit block控制块为上述第一预设码块，第一数量阈值为4个，在确定获得第一数量阈值的第一预设码块所使用的时长不大于第一预设时长，比如获得连续4个第一66 bit block的时长不大于第一预设时长，则发送第二故障信息。可选地，通信设备持续检测获得的第一预设码块，若获得连续4个第一66 bit block的时长大于第一预设时长，则确定满足“在第一预设时长内获得的第一故障信息的数量大于第一数量阈值”的条件，停止发送第二故障信息。
可选地，方法还包括通信设备通过第五端口获得第六故障信息；其中，第五端口为第二类型端口，第六故障信息为第一类型故障信息；第五端口配置备用链路；启用第五端口对应的备用链路。可选地，本申请实施例中若在通信设备中配置了保护倒换功能，在通信设备在接收到灵活以太网协议网络内的故障信息的情况下开启保护倒换功能，在接收到灵活以太网协议网络外的故障信息的情况下不开启倒换功能。本申请实施例中第二类型故障信息可以指示标准以太网协议对应的链路发生故障，因此当通信设备接收到第二类型故障信息时，则不开启保护倒换功能，当接收到第一类型故障信息时，则开启保护倒换功能。可见，本申请实施例中可以实现将标准以太网协议对应的链路发生故障和灵活以太网协议对应的链路发生故障的情况通过第一类型故障信息和第二类型故障信息进行区分，从而避 免标准以太网协议对应的链路发生故障触发保护倒换功能的情况。可选地，启用第五端口对应的备用链路，可以是参照上述图6所示的通信设备2103和通信设备2104之间的启用备用链路的过程，在此不再赘述。
本申请实施例中当将故障信息从标准以太网协议网络传输进灵活以太网协议网络，则可以根据第一类型故障信息生成第二类型故障信息，并在灵活以太网协议网络传输第二类型故障信息。相应地，若将故障信息从灵活以太网协议网络传输进标准以太网协议网络，则可以根据第二类型故障信息生成第一类型故障信息，并在标准以太网协议网络传输第一类型故障信息。可选地，本申请实施例中通过第二端口获得第三故障信息；其中，第三故障信息为第二类型故障信息；根据第三故障信息，通过第一端口发送第四故障信息；其中，第四故障信息为第一类型故障信息。如此，可以在灵活以太网网络内部传输第二类型故障信息，在灵活以以太网网络外部传输第一类型故障信息，从而可以根据故障信息的类型区分灵活以太网协议对应的链路发生故障还是标准以太网协议对应的链路发生故障。本申请实施例中故障信息是用于指示链路出现故障的信息，是一种上位的称呼，故障信息可以包括第一类型故障信息和/或第二类型故障信息。
可选地，根据第三故障信息，通过第一端口发送第四故障信息，包括：根据第三故障信息生成第三故障信息对应的第四故障信息，并通过第一端口发送第四故障信息。其中，则第三故障信息为客户服务类型本地故障信息，第三故障信息对应的第四故障信息为本地故障信息；第三故障信息为客户服务类型远端故障信息，第三故障信息对应的第四故障信息为远端故障信息。
可选地，根据第三故障信息生成第三故障信息对应的第四故障信息可以是新生成第四故障信息，也可以是将第三故障信息中的指示信息去除后得到的，该指示信息用于指示标准以太网协议对应的链路发生故障。也就是说，根据第二类型故障信息生成第二类型故障信息对应的第一类型故障信息可以是新生成第一类型故障信息，也可以是将第二类型故障信息中的指示信息去除之后得到的，该指示信息用于指示标准以太网协议对应的链路发生故障。
可选地，通信设备根据第三故障信息，通过第一端口发送第四故障信息，包括：若获得的第二类型故障信息满足第二预设条件，则根据第三故障信息，通过第一端口发送第四故障信息；其中，第二预设条件包括：获得数量不少于第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔。也就是说，本申请实施例中在满足“获得数量不少于第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔”的条件下发送第四故障信息，通信设备持续检测获得的第二预设码块的数量，若检测到不满足“获得数量不少于第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔”的条件，则停止发送第四故障信息。如此，可以避免因为数量较少的故障信息导致的误操作，进一步提高操作的准确性。
举个例子，第二66 bit block控制块为上述第二预设码块，第二预设码块间隔为128个码块，第二数量阈值为4个，当在检测到4个第二66 bit block(也可以称为第二66比特块)控制块，该第二66 bit block控制块中可以承载用于指示标准以太网协议对应的链路出现故障的指示信息。且任意相邻两个第二66 bit block控制块之间间隔不超过128个码块，则根据第三故障信息，通过第一端口发送第四故障信息。具体检测过程中，可以在检测到 第1个第二66 bit block控制块后，计数器记为第1个码块，后面128个block里面如果再检测到1个，计数器记为第2个，如果在后面128个block里面没有再检测到1个第二66 bit block控制块，事件记录清零(即计数器清零)，当下次再检测到第二66 bit block控制块时重新从1开始计数；如此下来，连续累计检测到4个有效第二66 bit block控制块，即计数器达到4，则认为获得了LF或RF信息。通信设备持续检测，在计数器的值不小于4的情况下通信设备发送第四故障信息，在计数器的值小于4的情况下停止发送第四故障信息，也就是说，相对应的，如果没有达到条件“获得数量不少于第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔”，则可以认为故障清除，则不再发送第四故障信息。举个例子，比如通信设备在连续128个码块内没有检测到第二66 bit block控制块，则认为故障清除。
可选地，通信设备根据第三故障信息，通过第一端口发送第四故障信息，包括：若在第二预设时长内获得的第三故障信息的数量大于第二数量阈值，则：根据第三故障信息，通过第一端口发送第四故障信息。可选地，第三故障信息也可以是第二预设码块。也就是说，若获得的第二类型故障信息满足第二预设条件，则根据第三故障信息，通过第一端口发送第四故障信息；其中，第二预设条件包括：在第二预设时长内获得的第三故障信息的数量大于第二数量阈值。在这种情况下获得的第二类型故障信息是第三故障信息。本申请实施例中在满足“在第二预设时长内获得的第三故障信息的数量大于第二数量阈值”的条件下发送第四故障信息，通信设备持续检测获得的第三故障信息的数量，若检测到不满足“在第二预设时长内获得的第三故障信息的数量大于第二数量阈值”的条件，则停止发送第四故障信息。
举个例子，第二66 bit block控制块为上述第二预设码块，第二数量阈值为4个，在确定获得第二数量阈值的第二预设码块所使用的时长不大于第二预设时长，比如获得连续4个第二66 bit block的时长不大于第二预设时长，则发送第四故障信息。可选地，通信设备持续检测获得的第二预设码块，若获得连续4个第二66 bit block的时长大于第一预设时长，则确定满足“在第二预设时长内获得的第二故障信息的数量大于第二数量阈值”的条件，停止发送第四故障信息。
本申请实施例中，可选地，方法还包括：通过第三端口获得第五故障信息；其中，第三端口为第二类型端口，第五故障信息为第一类型故障信息或者第二类型故障信息；通过第四端口发送第五故障信息；其中，第四端口为第二类型端口。如此，在灵活以太网网络内部可以透传第一类型故障信息和第二类型故障信息，进而可以在灵活以太网网络内部传输第二类型故障信息，在灵活以以太网网络外部传输第一类型故障信息，从而可以根据故障信息的类型区分灵活以太网协议对应的链路发生故障还是标准以太网协议对应的链路发生故障。也就是说，若两个第二类型端口之间有关联关系，比如第三端口和第四端口之间有关联关系，即第三端口获得的信息都通过第四端口传输出去，第四端口获得的信息都从第三端口传输出去，且第三端口为第二类型端口，第四端口为第二类型端口，则第三端口和第四端口可以透传获得的第一类型故障信息或第二类型故障信息。比如第三端口可以是上述图4至图6中的通信设备2103中的第二类型端口2204，第四端口可以是上述图4至图6中的通信设备2103中的第二类型端口2205，第二类型端口2204和第二类型端口2205可以透传获得的第一类型故障信息或第二类型故障信息。再比如第三端口和第四端口还可以是上述图4至图6中通信设备2102中的两个第二类型端口。
本申请实施例中，可选地，方法还包括：通过第六端口获得第七故障信息；其中，第六端口为第一类型端口，第七故障信息为第一类型故障信息；通过第七端口发送第七故障信息；其中，第七端口为第一类型端口。也就是说，若两个第一类型端口之间有关联关系，比如第六端口和第七端口之间有关联关系，即第六端口获得的信息都通过第七端口传输出去，第七端口获得的信息都从第六端口传输出去，且第六端口为第一类型端口，第七端口为第一类型端口，则第六端口和第七端口可以透传获得的第一类型故障信息或第二类型故障信息。比如第六端口可以是上述图4中的通信设备2102中的第一类型端口3201，第七端口可以是上述图4中的通信设备2102中的第一类型端口3202，第一类型端口3201和第一类型端口3202可以透传获得的第一类型故障信息或第二类型故障信息，图4中第一类型端口3201和第一类型端口3202有关联关系，第一类型端口3201可以连接其它通信设备的第一类型端口，第二类型端口3202也可以连接其它通信设备的第一类型端口。
基于上述内容，为了进一步描述本申请实施例所提供的方案，本申请实施例中提供一种通信方法流程示意图，图9示例性示出了本申请实施例中提供的基于图4所示系统结构的一种故障信息传输路径示意图，如图9所示，可以在通信设备中配置故障信息处理模块，比如在通信设备2102中的第一类型端口2202、第一类型端口3201和第一类型端口3202中的物理层上方配置故障信息处理模块，在通信设备2104中的第一类型端口2207的物理层上层配置故障信息处理模块。
若通信设备2101的第三类型端口2201发送信息至通信设备2102的第一类型端口2202的链路出现故障，则第一类型端口2202的物理层生成本地故障信息(属于第一类型故障信息，图中示意性写为LF)，可选地，通信设备2102通过第一类型端口2202获得第一类型故障信息的情况下，比如在满足第一预设条件时，发送客户服务类型本地故障信息(属于第二类型故障信息，图中示意性写为CSF)。比如可以通过故障信息处理模块来做，当故障信息处理模块接收到第一类型故障信息的情况下，比如在满足第一预设条件时，故障信息处理模块发送客户服务类型本地故障信息。其中，第一预设条件为“在第一预设时长内获得的第一类型故障信息的数量大于第一数量阈值”或“获得数量不少于第一数量阈值的第一预设码块，且获得的任两个相邻的第一预设码块之间间隔不超过第一预设码块间隔”。
举个例子说明“获得数量不少于第一数量阈值的第一预设码块，且获得的任两个相邻的第一预设码块之间间隔不超过第一预设码块间隔”的条件时，发送客户服务类型本地故障信息，比如，设置计数器，当检测到第一预设码块时，将计数器加1，当前计数器值为1，收到第二个第一预设码块时，若该第一预设码块与前一个相邻的第一预设码块之间的间隔不大于128个码块在，则将计数器加1；若该第一预设码块与前一个相邻的第一预设码块之间的间隔大于128个码块，则将计数器清零。预设第一数量阈值为4，则当计数器为不小于4的情况下，开始发送客户服务类型本地故障信息，可选地，可以是间隔一定数量的码块发送一个客户服务类型本地故障信息。当计数器为小于4的情况下，则不再发送客户服务类型本地故障信息。
进一步，第一类型端口2202生成的客户服务类型本地故障信息沿着第二类型端口2203、第二类型端口2204、第二类型端口2205、第二类型端口2206传输(也可以称为透传)至通信设备2104。由于通信设备需要将第二类型端口2206传输的信息通过第一类型端口2207传输出去，因此通信设备2104根据获得的客户服务类型本地故障信息，可以在 确定获得的客户服务类型本地故障信息满足第二预设条件时，生成本地故障信息，并将本地故障信息通过第一类型端口2207传输至通信设备2105的第三类型端口2208。可选地，可以是通信设备2104中的故障信息处理模块根据获得的客户服务类型本地故障信息，生成本地故障信息。相对应地，通信设备2104在获得的客户服务类型本地故障信息不满足第二预设条件时，可以不再通过第一类型端口2207发送本地故障信息。其中，第二预设条件可以是“在第二预设时长内获得的第二类型故障信息的数量大于第二数量阈值”或者“获得数量不少于第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔”。
进一步，通信设备2105的通过第三类型端口2208获得本地故障信息后，可以在确定获得的本地故障信息满足条件第一预设条件的情况下，第三类型端口2208中的RS下发远端故障信息，可以是持续下发远端故障信息。相对应的，若通信设备2105确定获得的本地故障信息不满足第一预设条件，则不再下发远端故障信息。
进一步，可选地，通信设备2104的第一类型端口2207在获得远端故障信息之后，确定获得的远端故障信息满足第一预设条件，通信设备2104生成客户服务类型远端故障信息并通过第二类型端口2206发送。相应地，若通信设备2105确定获得的远端故障信息不满足第一预设条件，则通信设备2105不发送客户服务类型远端故障信息。
进一步，可选地，通信设备2104通过第二类型端口2206发送的客户服务类型远端故障信息沿着第二类型端口2205、第二类型端口2204、第二类型端口2203一直透传至通信设备2102。由于通信设备2102需要将第二类型端口2203获得的信息通过第一类型端口2202传输出去，因此通信设备2104根据在获得客户服务类型远端故障信息的情况下，且确定获得的客户服务类型远端故障信息满足第二预设条件，通过第一类型端口2202发送远端故障信息。相应地，若确定获得的客户服务类型远端故障信息不满足第二预设条件，则不通过第一类型端口2202发送远端故障信息。
基于图9所示的实施例，本申请实施例中提供另外一种可选地实施方式，如图9所示，若通信设备2101的第三类型端口2201发送信息至第一类型端口2202的链路出现故障，则第一类型端口2202的物理层生成本地故障信息，可选地，通信设备通过第一端口获得第一类型故障信息的情况下，且确定获得的第一类型故障信息满足第一预设条件，则发送客户服务类型本地故障信息。相对应的，若通信设备2102通过第一类型端口2202获得第一类型故障信息不满足第一预设条件，则可以发送故障清除信息。
进一步，第一类型端口2202发出的客户服务类型本地故障信息沿着第二类型端口2203、第二类型端口2204、第二类型端口2205、第二类型端口2206透传至通信设备2104。由于通信设备2104需要将第二类型端口2206传输的信息通过第一类型端口2207传输出去，因此通信设备2104根据获得的客户服务类型本地故障信息，确定获得的客户服务类型本地故障信息满足第二预设条件，则生成本地故障信息，并将本地故障信息通过第一类型端口2207传输至通信设备2105的第三类型端口2208。可选地，可以是通信设备2104中的故障信息处理模块根据获得的客户服务类型本地故障信息，生成本地故障信息。相对应的，若通信设备2102生成第一类型端口2202对应的故障清除信息，则故障清除信息也可以沿着第二类型端口2203、第二类型端口2204、第二类型端口2205、第二类型端口2206透传至通信设备2104，通信设备2104在确定收到故障清除信息的情况下停止通过第一类型端口2207发送本地故障信息。
进一步，通信设备2105通过第三类型端口2208获得本地故障信息后，可以在确定获得的本地故障信息满足第一预设条件的情况下，第三类型端口2208中的RS下发远端故障信息，可以是持续下发远端故障信息。相对应的，若通信设备2105确定获得的本地故障信息不满足第一预设条件，则不再下发远端故障信息。
进一步，可选地，通信设备2104的第一类型端口2207在收到远端故障信息之后，确定收到的远端故障信息满足第一预设条件，通信设备2104生成客户服务类型远端故障信息并通过第二类型端口2206发送。相应地，若通信设备2105确定收到的远端故障信息不满足第一预设条件，则可以不发送远端故障信息或者发送故障清除信息。
进一步，可选地，通信设备2104通过第二类型端口2206发送的客户服务类型远端故障信息沿着第二类型端口2205、第二类型端口2204、第二类型端口2203一直透传至通信设备2102。由于通信设备2102需要将第二类型端口2203获得的信息通过第一类型端口2202传输出去，因此通信设备2104根据在收到客户服务类型远端故障信息的情况下，且确定收到的客户服务类型远端故障信息满足第二预设条件，通过第一类型端口2202发送远端故障信息。相对应的，若生成第一类型端口2207对应的故障清除信息，则故障清除信息也可以沿着第二类型端口2205、第二类型端口2204、第二类型端口2203一直透传至通信设备2102，通信设备2102在确定收到故障清除信息的情况下停止发送远端故障信息或者发送故障清除信息给通信设备2101的第三类型端口2201。
基于图9所示的系统架构，若通信设备2104中配置有保护倒换功能，若第二类型端口之间的链路出现故障，比如第二类型端口2205向第二类型端口2206发送信息的链路出现故障，则通信设备2104中的第二类型端口2206生成本地故障信息，通信设备2104启动第二类型端口2206对应的备用链路，比如启动图9中第二类型端口2301和第二类型端口2302实现通信设备2103和通信设备2104之间的连接。可见，如此，由于本申请实施例中可以将标准以太网协议链路的故障和灵活以太网协议的链路的故障区分，因此即保留了标准以太网协议下的故障协商机制，也可基于保护倒换功能实现灵活以太网协议内部的自愈功能。
本申请实施例中，上述图4中的第二类型端口对应的备用链路可以包括通信设备2103与通信设备2104之间的第二类型端口2301和第二类型端口2303之间的链路，还可以包括通信设备2102的第二类型端口3301和通信设备2103的第二类型端口3302之间的链路，比如启用通信设备2102中第一类型端口2202和第二类型端口3301的关联关系，启用通信设备2103中第二类型端口3302和第二类型端口2301的关联关系，启用通信设备2104中第二类型端口2302和第一类型端口2207的关联关系。也就是说灵活以太网协议内部包括的备用链路可以替换良好以太网协议内部所有的工作链路，从而保证灵活以太网协议内部的自愈功能，比如图4中可以用“第一类型端口2202、第二类型端口3301、第二类型端口3302、第二类型端口2301、第二类型端口2302、第一类型端口2207之间的链路”替换“第一类型端口2202、第二类型端口2203、第二类型端口2204、第二类型端口2205、第二类型端口2206、第一类型端口2207之间的链路”。
本申请实施例中发送第二类型故障信息可以是发送至少两个第二类型故障信息，其中至少两个第二类型故障信息中的任两个第二类型故障信息之间间隔至少一个码块。可选地，根据第一故障信息，通过第二端口发送第二故障信息，包括：根据第一故障信息，通过第二端口发送至少两个第二故障信息；其中，至少一个第二故障信息中的任两个第二故 障信息之间间隔至少一个码块。如此，可以节省灵活以太网协议对应的链路的传输路径的带宽。
本申请实施例中图10示例性示出了本申请实施例提供的一种0x4B的66 bit block码块的示意图，如图10所示，0x4B码块的控制块格式(英文可以称为control block format)为O 0D 1D 2D 3Z 4Z 5Z 6Z 7；同步头(英文也可称为synchronization header)为“10”；块类型区域(英文可以称为block type field)为0x4B；之后的三个字节分别为D1字节、D2字节和D3字节，在D3字节后为O码区域；最后28个比特为0x0000000。0x4B码块是标准以太网IEEE 802.3-2015标准文档图Figure 82-5中定义的一类控制码块。
上述示例中故障清除信息可以是指示客户侧正常的操作管理维护功能(Operation,Administration and Maintenance，OAM)消息块，OAM消息块还可以包括网络中的误码检测、故障侦测、时延测量、路径发现等机制。故障清除信息的OAM消息块可以承载在0x4B码块上。图11示例性示出了本申请实施例提供的一种基于图10所示0x4B码块的故障清除信息的示意图，当通信设备检测到如图10所示的消息块的情况下，具体来说，当通信设备检测到“10”同步头+第一个字节“0x4B”+第四个字节的前4个比特“0x06”+第二个字节和第三个字节的内容“0b00000101”“0b00000000”，则认为收到了故障清除信息。
图12示例性示出了本申请实施例提供的一种基于图10所示0x4B码块的本地故障信息的示意图，图13示例性示出了本申请实施例提供的一种基于图10所示0x4B码块的远端故障信息的示意图。如图12所示，本地故障信息中，同步头为“10”，块类型区域为0x4B；D1字节为0x00、D2字节为0x00；D3字节为0x01，在D3字节后为O码区域为0x0；最后28个比特为0x0000000。如图13所示，远端故障信息中，同步头为“10”，块类型区域为0x4B；D1字节为0x00、D2字节为0x00；D3字节为0x02，在D3字节后为O码区域为0x0；最后28个比特为0x0000000。通过图12和图13可以看出，本地故障信息和远端故障信息通过D3字节进行区分。
本申请实施例中的第二类型故障信息可以用0x4B码块来承载。可选地，第二类型故障信息可以是OAM消息块。图14示例性示出了本申请实施例提供的一种基于图10所示0x4B码块的第二类型故障信息的示意图，如图14所示，第二类型故障信息携带0x4B控制类型“0x4B”和O码区域的“0x6”，使用D1、D2字节承载特定消息块。如图14所示，使用D1字节的前六位作为OAM消息类型字段，当D1字节中的第0至第5比特为“0b000001”可以表示该0x4B码块承载第二类型故障信息，也可以称第二类型故障信息为客户服务信息(Client Service，CS)；使用D1字节的后2位(D1字节的第6至第7比特)和D2字节的前两位比特(D2字节的第0至第1比特)表示CSF、RCSF以及正常情况下承载业务(比如以太网服务，应为可以称为Ethernet service)的信息。举个例子，比如D1字节的第6至第7比特和D2字节的第0至第1比特为“1110”，则表示该0x4B码块承载RCSF；比如D1字节的第6至第7比特和D2字节的第0至第1比特为“1111”，则表示该0x4B码块承载CSF；比如D1字节的第6至第7比特和D2字节的第0至第1比特为“0100”，则表示该0x4B码块承载正常的业务信息(比如以太网服务业务信息)，也可以指示故障清除。也就是说，D1字节的第6至第7比特和D2字节的第0至第1比特为“0100”，可以表示该0x4B码块承载故障清除信息。
图15示例性示出了本申请实施例提供的一种基于图10所示0x4B码块的客户服务类 型本地故障信息的示意图，图16示例性示出了本申请实施例提供的一种基于图10所示0x4B码块的客户服务类型远端故障信息的示意图。如图15所示，客户服务类型本地故障信息中，同步头为“10”，块类型区域为0x4B；D1字节为0b00000111、D2字节为0b11000000；D3字节为0x06，在D3字节后为O码区域为0x6；最后28个比特为0x0000000。如图16所示，客户服务类型远端故障信息中，同步头为“10”，块类型区域为0x4B；D1字节为0b00000111、D2字节为0b10000000；D3字节为0x06，在D3字节后为O码区域为0x6；；最后28个比特为0x0000000。通过图14和图15可以看出，客户服务类型本地故障信息和客户服务类型远端故障信息的O码区域为0x6，而图12和图13所示的本地故障信息和远端故障信息的O码区域为0x0。
基于以上实施例以及相同构思，图17为本申请实施例提供的一种通信设备的示意图，如图17所示，该通信设备4101可以为网络设备，也可以为芯片或电路，比如可设置于网络设备的芯片或电路。该通信设备可以实现如上图7和/或图8中所示的任一项或任多项对应的方法中通信设备所执行的步骤。该通信设备4101可以包括故障信息处理模块4201和至少两个端口。比如该通信设备4101可以包括故障信息处理模块4201和至少一个第一类型端口和至少一个第二类型端口，比如可以是包括第一端口4102和第二端口4103。再比如，该通信设备4101可以包括故障信息处理模块4201和至少两个第一类型端口，比如可以是包括第六端口4107和第七端口4108。再比如，该通信设备4101可以包括故障信息处理模块4201和至少两个第二类型端口，比如可以是包括第三端口4104和第七端口4105。
在图17中示意性将第一端口至第七端口都示意出，可选地，同一个类型的两个端口可能是同一个端口，比如第四端口4105和第五端口4106可能是同一个端口，但为了清楚介绍本申请实施例，在图中画为两个端口。再比如，第一端口4102和第六端口4107可能是同一个端口，但为了清楚介绍本申请实施例，在图中画为两个端口。再比如，不同类型的两个端口有可能也是同一个端口，举个例子，比如第六端口4107和第三端口4104可能是同一个端口，该端口可以支持标准以太网协议和灵活以太网协议，当该端口当前使用标准以太网协议收发信息时，可以称该端口为第六端口4107，当该端口当前使用灵活以太网协议收发信息时，可以称该端口为第三端口4104，但为了清楚介绍本申请实施例，在图中画为两个端口。
可选地，在图17中，通信设备4101在实现上述图7中所示的任一项或任多项对应的方法中通信设备所执行的步骤的情况下，上述图7中的第一端口可以是通信设备4101中的第一端口4102，上述图7中的第二端口可以是通信设备4101中的第二端口4103。可选地，在图17中，通信设备4101在实现上述图8中所示的任一项或任多项对应的方法中通信设备所执行的步骤的情况下，上述图8中的第一端口可以是通信设备4101中的第一端口4102，上述图8中的第二端口可以是通信设备4101中的第二端口4103。可选地，通信设备4101在实现上述图7和图8中所示的任一项或任多项对应的方法中通信设备所执行的步骤的情况下，上述图7和图8中的第一端口可以是通信设备4101中的第一端口4102，上述图7和图8中的第二端口可以是通信设备4101中的第二端口4103。另一种可选地实施例中，通信设备4101在实现上述图7和图8中所示的任一项或任多项对应的方法中通信设备所执行的步骤的情况下，上述图7中的第一端口可以是通信设备4101中的第一端口4102，上述图7中的第二端口可以是通信设备4101中的第二端口4103；上述图8中的第一端口可以是通信设备4101中的除第一端口4102之外的第一类型端口，上述图7中的 第二端口可以是通信设备4101中的除第二端口4103之外的第二类型端口。
本申请实施例中第一端口4102、第六端口4107和第七端口4108为第一类型端口，第一类型端口中不配置RS，第二端口4103、第三端口4104、第四端口4105、第五端口4106为第二类型端口，第二类型端口中不配置RS。其余关于第一类型端口和第二类型端口的相关介绍可参加前述内容，在此不再赘述。
本申请实施例中故障信息处理模块4201可以是分布式的，各个端口对应设置一个，如上述图2所示，集成在各个端口上，比如故障信息处理模块4201包括图2中的第一类型端口1401中的故障信息处理模块1601、第一类型端口1402中的故障信息处理模块1602和第一类型端口1403中的故障信息处理模块1603。或者本申请实施例中故障信息处理模块4201可以是集中式的，各个端口共用一个，也就是说故障信息处理模块4201可以独立出来，并与各个端口相连接。故障信息处理模块可以设置在第一类型端口的一侧，或者设置在第二类型端口的一侧，图中仅示出了设置在第一类型端口的一侧的示意。故障信息处理模块4201若设置在第一类型端口一侧，可以设置在各个端口物理层以上；若设置在第二类型端口一侧，可以设置在各个端口物理层以上，或者设置在各个端口灵活以太网协议层以上。
本申请实施例中通信设备4101还包括交换单元4301，可选地该交换单元4301可以是上述图2中的交换单元1701，用于存储各个端口之间的关联关系，并可以更新各个端口之间的关联关系等等。相关介绍可以参见前述关于交换单元1701的介绍，在此不再赘述。可选地，图17所示的实施例中，第一端口4102和第二端口4103之间有关联关系，第六端口4107和第七端口4108之间有关联关系，第三端口4104和第四端口4105之间有关联关系。可选地，各个端口之间的关联关系可以是预配置的，该关联关系可以更新，比如根据用户输入的新的关联关系更新，或者根据内部的一些自愈机制的策略进行更新(比如上述内容中启用备用链路所带来的关联关系的更新)等等。
在一种可能的设计中，本申请实施例中第一端口4102，用于获得第一故障信息，比如可以是接收到其它端口发送的第一故障信息或者是第一端口4102的物理层生成的第一故障信息；故障信息处理模块4201，根据第一故障信息，生成第二故障信息；第二端口4103，用于发送第二故障信息；其中，第一端口4102为第一类型端口，第一类型端口根据标准以太网协议传输信息；第一故障信息为第一类型故障信息，第一类型故障信息包括本地故障信息和远端故障信息中的至少一项；第二端口4103为第二类型端口，第二类型端口根据灵活以太网协议传输信息；第二故障信息为第二类型故障信息，第二类型故障信息用于指示标准以太网协议对应的链路发生故障。
本申请实施例中通过第一端口获得第一故障信息，根据第一故障信息，通过第二端口发送第二故障信息，其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息，第一故障信息为第一类型故障信息，第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息，且由于第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二故障信息为第二类型故障信息，第二类型故障信息用于指示标准以太网协议对应的链路发生故障，因此通过传输第二故障信息的方式既可以在标准以太网协议和灵活以太网协议联合组网中通报故障，也可以为区分灵活以太网协议对应的链路发生故障和标准以太网协议对应的链路发生故障奠定基础。
在一种可能的设计中，故障信息处理模块4201，用于若获得的第一类型故障信息满足 第一预设条件，则根据第一故障信息，生成第二故障信息；其中，第一预设条件包括：在第一预设时长内获得的第一类型故障信息的数量大于第一数量阈值；或者；获得数量不少于第一数量阈值的第一预设码块，且获得的任两个相邻的第一预设码块之间间隔不超过第一预设码块间隔。如此，可以避免因为数量较少的故障信息导致的误操作，进一步提高操作的准确性。
基于上述内容以及相同构思，本申请实施例还提供一种通信设备，在一种可能的设计中，该通信设备中的第二端口4103，用于获得第三故障信息；其中，第三故障信息为第二类型故障信息；故障信息处理模块4201，还用于根据第三故障信息，生成第四故障信息；其中，第四故障信息为第一类型故障信息；第一端口4102，还用于发送第四故障信息。其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息，第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息。第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二类型故障信息用于指示标准以太网协议对应的链路发生故障。
本申请实施例中通过第二端口获得第三故障信息，根据第三故障信息，通过第一端口发送第四故障信息，由于第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二类型故障信息用于指示标准以太网协议对应的链路发生故障，因此通过传输第二故障信息的方式既可以在标准以太网协议和灵活以太网协议联合组网中通报故障，也可以为区分灵活以太网协议对应的链路发生故障和标准以太网协议对应的链路发生故障奠定基础；第三也可以兼容标准以太网协议网络中通过第一类型故障信息传输通报故障的方案。
在一种可能的设计中，故障信息处理模块4201，用于若获得的第二类型故障信息满足第二预设条件，则根据第三故障信息，生成第四故障信息；其中，第二预设条件包括在第二预设时长内获得的第三故障信息的数量大于第二数量阈值；或者；获得数量不少于第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔。如此，可以避免因为数量较少的故障信息导致的误操作，进一步提高操作的准确性。
基于上述所描述，通信设备4101在执行上述图7和/或图8所示的通信方法的实施例中还可能存在其它可能的实施方式，下面介绍通信设备4101在执行上述图7和/或图8所示的通信方法中的其它的可选地实施方式。
在一种可能的设计中，通信设备4101还包括第三端口4104，用于获得第五故障信息；其中，第三端口4104为第二类型端口，第五故障信息为第一类型故障信息或者第二类型故障信息；还包括第四端口4105，用于发送第五故障信息；其中，第四端口4105为第二类型端口。如此，在灵活以太网网络内部可以透传第一类型故障信息和第二类型故障信息，进而可以在灵活以太网网络内部传输第二类型故障信息，在灵活以以太网网络外部传输第一类型故障信息，从而可以根据故障信息的类型区分灵活以太网协议对应的链路发生故障还是标准以太网协议对应的链路发生故障。
在一种可能的设计中，通信设备4101还包括第五端口4106，用于获得第六故障信息；其中，第五端口4106为第二类型端口，第六故障信息为第一类型故障信息；第五端口4106配置备用链路；启用第五端口4106对应的备用链路。可见，本申请实施例中可以实现将标准以太网协议对应的链路发生故障和灵活以太网协议对应的链路发生故障的情况通过 第一类型故障信息和第二类型故障信息进行区分，从而避免标准以太网协议对应的链路发生故障触发保护倒换功能的情况；而且可以更加准确的根据灵活以太网协议网络内部的故障信息触发保护倒换功能。
在一种可能的设计中，第二端口4103，用于发送至少两个第二故障信息；其中，至少一个第二故障信息中的任两个第二故障信息之间间隔至少一个码块。如此，可以灵活设置第二故障信息的发送频率，比如将第二故障信息的发送频率设置的小于第一故障信息的发送频率，则可以节省灵活以太网协议对应的链路的传输路径的带宽。举个例子，比如第一故障信息为远端故障信息，第二故障信息为客户服务类型远端故障信息，远端故障信息为持续发送，占用带宽较大，设置间隔一定数量的码块发送一个客户服务类型远端故障信息，则可以节省带宽。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
基于以上实施例以及相同构思，图18为本申请实施例提供的一种通信设备的示意图，如图18所示，该通信设备5300可以为网络设备，也可以为芯片或电路，比如可设置于网络设备的芯片或电路。该通信设备可以实现如上图7和/或图8中所示的任一项或任多项对应的方法中通信设备所执行的步骤。该通信设备4101可以包括处理器5301、收发器5302、存储器5303和通信接口5304；其中，处理器5301、收发器5302、存储器5303和通信接口5304通过总线5305相互连接。
总线5305可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器5303可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器5303还可以包括上述种类的存储器的组合。
通信接口5304可以为有线通信接入口，无线通信接口或其组合，其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为WLAN接口。通信接口5304可以是上述各个端口，比如第一类型端口和第二类型端口，再比如图17中第一端口4102、第二端口4103、第三端口4104、第四端口4105、第五端口4106、第六端口4107和第七端口4108。
处理器5301可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器5301还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。
可选地，存储器5303还可以用于存储程序指令，处理器5301调用该存储器5303中 存储的程序指令，可以控制收发器5302进行信号接收和信号发送，可以执行上述方案中所示实施例中的一个或多个步骤，或其中可选的实施方式，使得通信设备5300实现上述方法中通信设备的功能。
本申请实施例中处理器用于通过第一端口获得第一故障信息，并根据第一故障信息，控制收发器通过第二端口发送第二故障信息；收发器，用于通过第二端口发送第二故障信息；其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息；第一故障信息为第一类型故障信息，第一类型故障信息包括本地故障信息和远端故障信息中的至少一项；第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息；第二故障信息为第二类型故障信息，第二类型故障信息用于指示标准以太网协议对应的链路发生故障。
本申请实施例中通过第一端口获得第一故障信息，根据第一故障信息，通过第二端口发送第二故障信息，其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息，第一故障信息为第一类型故障信息，第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息，且由于第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二故障信息为第二类型故障信息，第二类型故障信息用于指示标准以太网协议对应的链路发生故障，因此通过传输第二故障信息的方式既可以在标准以太网协议和灵活以太网协议联合组网中通报故障，也可以为区分灵活以太网协议对应的链路发生故障和标准以太网协议对应的链路发生故障奠定基础。
在一种可能的设计中，处理器，用于若获得的第一类型故障信息满足第一预设条件，则根据第一故障信息，控制收发器通过第二端口发送第二故障信息；其中，第一预设条件包括：在第一预设时长内获得的第一类型故障信息的数量大于第一数量阈值；或者；获得数量不少于第一数量阈值的第一预设码块，且获得的任两个相邻的第一预设码块之间间隔不超过第一预设码块间隔。
基于上述内容以及相同构思，本申请实施例还提供一种通信设备，在一种可能的设计中，该通信设备中处理器，还用于通过第二端口获得第三故障信息；其中，第三故障信息为第二类型故障信息；根据第三故障信息，控制收发器通过第一端口发送第四故障信息；其中，第四故障信息为第一类型故障信息。其中，第一端口为第一类型端口，第一类型端口根据标准以太网协议传输信息，第二端口为第二类型端口，第二类型端口根据灵活以太网协议传输信息。第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二类型故障信息用于指示标准以太网协议对应的链路发生故障。
本申请实施例中通过第二端口获得第三故障信息，根据第三故障信息，通过第一端口发送第四故障信息，由于第一类型故障信息包括本地故障信息和远端故障信息中的至少一项，第二类型故障信息用于指示标准以太网协议对应的链路发生故障，因此通过传输第二故障信息的方式既可以在标准以太网协议和灵活以太网协议联合组网中通报故障，也可以为区分灵活以太网协议对应的链路发生故障和标准以太网协议对应的链路发生故障奠定基础；第三也可以兼容标准以太网协议网络中通过第一类型故障信息传输通报故障的方案。
在一种可能的设计中，处理器，用于若获得的第二类型故障信息满足第二预设条件，则根据第三故障信息，控制收发器通过第一端口发送第四故障信息；其中，第二预设条件包括：在第二预设时长内获得的第三故障信息的数量大于第二数量阈值；或者；获得数量 不少于第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔。
基于上述所描述，通信设备5300在执行上述图7和/或图8所示的通信方法的实施例中还可能存在其它可能的实施方式，下面介绍通信设备5300在执行上述图7和/或图8所示的通信方法中的其它的可选地实施方式。
在一种可能的设计中，处理器，还用于通过第三端口获得第五故障信息；其中，第三端口为第二类型端口，第五故障信息为第一类型故障信息或者第二类型故障信息；收发器，还用于通过第四端口发送第五故障信息；其中，第四端口为第二类型端口。
在一种可能的设计中，处理器，还用于通过第五端口获得第六故障信息；其中，第五端口为第二类型端口，第六故障信息为第一类型故障信息；第五端口配置备用链路；启用第五端口对应的备用链路。
在一种可能的设计中，处理器，用于根据第一故障信息，控制收发器通过第二端口发送至少两个第二故障信息；其中，至少一个第二故障信息中的任两个第二故障信息之间间隔至少一个码块。
基于以上实施例以及相同构思，图19为本申请实施例提供的一种通信设备的示意图，如图19所示，该通信设备6101可以是上述内容中的通信设备，比如可以是图18中的通信设备5300、也可以是上述图17中的通信设备4101，也可以是上述图2和图3中的儿童鞋设备1301，也可以是上述图2至图6、以及图9中的通信设备，比如通信设备2102、通信设备2104。通信设备6101也可以称为分组承载设备。具体实施中，本申请实施例提供的通信设备6101可以在支持1.5层交换的网络设备上落地，通信设备(或者称网络设备)产品形态包括支持灵活以太网协议的端口的基于网络协议的无线电接入网(Internet Protocol Radio Access Network，IPRAN)、分组传送网(Packet Transport Network，PTN)盒式或框式交换机设备。本申请实施例落地产品的方案可以采用在已有的第二类型端口(也可以称为FlexE端口)芯片和标准以太网协议端口的PHY芯片之间增加一块FPGA来实现，比如增加的该FPGA实现上述故障信息处理模块所执行的方案，或者可以在第二类型端口(也可以称为FlexE端口)芯片内实现，比如在该芯片内实现上述故障信息处理模块所执行的方案，从而实现在66 bit block数据流中插入和提取CSF和/或RCSF消息块以及插入和提取LF和/或RF消息块的目的。
如图19所示，通信设备6101中可以包括主控交换板6104、接口板6102和接口板6103。其中，主控交换板6104可以是上述内容中的交换单元，比如图17中的交换单元4301、图2中的交换单元1701。其它图中未示出交换单元或主控交换板，但各个端口通过主控交换板或交换单元连接。主控交换板6104中包括网络处理器(Network Processor，NP)或交换网芯片6203，网络处理器(Network Processor，NP)或交换网芯片6203可以是上述图18中的处理器5301中的一部分。
如图19所示，接口板6102可以是用户侧接口板，可以包括用户侧接口芯片6201。用户侧接口芯片6201可以是上述第一类型端口，比如可以是图17中的第一端口4102，也可以是图9中的第一类型端口2202。用户侧接口芯片6201通过接口与主控交换板6104连接。
本申请实施例中用户侧接口芯片6201中可以集成故障信息处理模块6105，故障信息处理模块6105可以是分布式的，比如每个用户侧接口芯片上集成一个，也可以是集中式的，比如多个用户侧接口芯片中共用一个。故障信息处理模块6105可以是上述图17中的 故障信息处理模块4201，也可以是上述图2中的故障信息处理模块1601、故障信息处理模块1602和故障信息处理模块1603中的至少一个。
如图19所示，接口板6103可以是网络侧接口板，可以包括网络侧接口芯片6202。网络侧接口芯片6202可以是上述第二类型端口，比如可以是图17中的第二端口4103，也可以是图9中的第一类型端口2205。网络侧接口芯片6202通过接口与主控交换板6104连接。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
还应理解，本文中涉及的第一、第二、第三、第四以及各种数字编号仅为描述方便进行的区分，并不用来限制本发明实施例的范围。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地生成 按照本发明实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以权利要求的保护范围为准。

Claims (23)

  1. 一种通信方法，其特征在于，包括：
    通过第一端口获得第一故障信息；其中，所述第一端口为第一类型端口，所述第一类型端口根据标准以太网协议传输信息；所述第一故障信息为第一类型故障信息，所述第一类型故障信息包括本地故障信息和远端故障信息中的至少一项；
    根据所述第一故障信息，通过第二端口发送第二故障信息；其中，所述第二端口为第二类型端口，所述第二类型端口根据灵活以太网协议传输信息；所述第二故障信息为第二类型故障信息，所述第二类型故障信息用于指示标准以太网协议对应的链路发生故障。
  2. 如权利要求1所述的方法，其特征在于，所述根据所述第一故障信息，通过第二端口发送第二故障信息，包括：
    若获得的所述第一类型故障信息满足第一预设条件，则根据所述第一故障信息，通过所述第二端口发送第二故障信息；
    其中，所述第一预设条件包括：
    在第一预设时长内获得的所述第一类型故障信息的数量大于第一数量阈值；或者；
    获得数量不少于所述第一数量阈值的第一预设码块，且获得的任两个相邻的所述第一预设码块之间间隔不超过第一预设码块间隔。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    通过所述第二端口获得第三故障信息；其中，所述第三故障信息为所述第二类型故障信息；
    根据所述第三故障信息，通过所述第一端口发送第四故障信息；其中，所述第四故障信息为所述第一类型故障信息。
  4. 如权利要求3所述的方法，其特征在于，所述根据所述第三故障信息，通过所述第一端口发送第四故障信息，包括：
    若获得的所述第二类型故障信息满足第二预设条件，则根据所述第三故障信息，通过所述第一端口发送第四故障信息；
    其中，所述第二预设条件包括：
    在第二预设时长内获得的所述第三故障信息的数量大于第二数量阈值；或者；
    获得数量不少于所述第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔。
  5. 如权利要求3或4所述的方法，其特征在于，所述方法还包括：
    通过第三端口获得第五故障信息；其中，所述第三端口为所述第二类型端口，所述第五故障信息为所述第一类型故障信息或者所述第二类型故障信息；
    通过第四端口发送所述第五故障信息；其中，所述第四端口为所述第二类型端口。
  6. 如权利要求1至4任一权利要求所述的方法，其特征在于，所述方法还包括：
    通过第五端口获得第六故障信息；其中，所述第五端口为所述第二类型端口，所述第六故障信息为所述第一类型故障信息；所述第五端口配置备用链路；
    启用所述第五端口对应的所述备用链路。
  7. 如权利要求1至6任一权利要求所述的方法，其特征在于，所述根据所述第一故障信息，通过第二端口发送第二故障信息，包括：
    根据所述第一故障信息，通过第二端口发送至少两个第二故障信息；
    其中，所述至少两个第二故障信息中的任两个第二故障信息之间间隔至少一个码块。
  8. 一种通信设备，其特征在于，包括处理器和收发器；其中：
    所述处理器用于通过第一端口获得第一故障信息，并根据所述第一故障信息，控制所述收发器通过第二端口发送第二故障信息；
    所述收发器，用于通过第二端口发送第二故障信息；
    其中，所述第一端口为第一类型端口，所述第一类型端口根据标准以太网协议传输信息；所述第一故障信息为第一类型故障信息，所述第一类型故障信息包括本地故障信息和远端故障信息中的至少一项；所述第二端口为第二类型端口，所述第二类型端口根据灵活以太网协议传输信息；所述第二故障信息为第二类型故障信息，所述第二类型故障信息用于指示标准以太网协议对应的链路发生故障。
  9. 如权利要求8所述的通信设备，其特征在于，所述处理器，用于：
    若获得的所述第一类型故障信息满足第一预设条件，则根据所述第一故障信息，控制所述收发器通过所述第二端口发送第二故障信息；
    其中，所述第一预设条件包括：
    在第一预设时长内获得的所述第一类型故障信息的数量大于第一数量阈值；或者；
    获得数量不少于所述第一数量阈值的第一预设码块，且获得的任两个相邻的所述第一预设码块之间间隔不超过第一预设码块间隔。
  10. 如权利要求8或9所述的通信设备，其特征在于，所述处理器，还用于：
    通过所述第二端口获得第三故障信息；其中，所述第三故障信息为所述第二类型故障信息；
    根据所述第三故障信息，控制所述收发器通过所述第一端口发送第四故障信息；其中，所述第四故障信息为所述第一类型故障信息。
  11. 如权利要求10所述的通信设备，其特征在于，所述处理器，用于：
    若获得的所述第二类型故障信息满足第二预设条件，则根据所述第三故障信息，控制所述收发器通过所述第一端口发送第四故障信息；
    其中，所述第二预设条件包括：
    在第二预设时长内获得的所述第三故障信息的数量大于第二数量阈值；或者；
    获得数量不少于所述第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔。
  12. 如权利要求10或11所述的通信设备，其特征在于，所述处理器，还用于：
    通过第三端口获得第五故障信息；其中，所述第三端口为所述第二类型端口，所述第五故障信息为所述第一类型故障信息或者所述第二类型故障信息；
    所述收发器，还用于：
    通过第四端口发送所述第五故障信息；其中，所述第四端口为所述第二类型端口。
  13. 如权利要求8至11任一权利要求所述的通信设备，其特征在于，所述处理器，还用于：
    通过第五端口获得第六故障信息；其中，所述第五端口为所述第二类型端口，所述第六故障信息为所述第一类型故障信息；所述第五端口配置备用链路；
    启用所述第五端口对应的所述备用链路。
  14. 如权利要求8至13任一权利要求所述的通信设备，其特征在于，所述处理器，用于：
    根据所述第一故障信息，控制所述收发器通过第二端口发送至少两个第二故障信息；
    其中，所述至少两个第二故障信息中的任两个第二故障信息之间间隔至少一个码块。
  15. 一种通信设备，其特征在于，包括：
    第一端口，用于获得第一故障信息；
    故障信息处理模块，根据所述第一故障信息，生成第二故障信息；
    第二端口，用于发送第二故障信息；
    其中，所述第一端口为第一类型端口，所述第一类型端口根据标准以太网协议传输信息；所述第一故障信息为第一类型故障信息，所述第一类型故障信息包括本地故障信息和远端故障信息中的至少一项；所述第二端口为第二类型端口，所述第二类型端口根据灵活以太网协议传输信息；所述第二故障信息为第二类型故障信息，所述第二类型故障信息用于指示标准以太网协议对应的链路发生故障。
  16. 如权利要求15所述的通信设备，其特征在于，所述故障信息处理模块，用于：
    若获得的所述第一类型故障信息满足第一预设条件，则根据所述第一故障信息，生成第二故障信息；
    其中，所述第一预设条件包括：
    在第一预设时长内获得的所述第一类型故障信息的数量大于第一数量阈值；或者；
    获得数量不少于所述第一数量阈值的第一预设码块，且获得的任两个相邻的所述第一预设码块之间间隔不超过第一预设码块间隔。
  17. 如权利要求15或16所述的通信设备，其特征在于，所述第二端口，还用于：
    获得第三故障信息；其中，所述第三故障信息为所述第二类型故障信息；
    所述故障信息处理模块，还用于：
    根据所述第三故障信息，生成第四故障信息；其中，所述第四故障信息为所述第一类型故障信息；
    所述第一端口，还用于：
    发送第四故障信息。
  18. 如权利要求17所述的通信设备，其特征在于，所述故障信息处理模块，用于：
    若获得的所述第二类型故障信息满足第二预设条件，则根据所述第三故障信息，生成第四故障信息；
    其中，所述第二预设条件包括：
    在第二预设时长内获得的所述第三故障信息的数量大于第二数量阈值；或者；
    获得数量不少于所述第二数量阈值的第二预设码块，且获得的任两个相邻的第二预设码块之间间隔不超过第二预设码块间隔。
  19. 如权利要求17或18所述的通信设备，其特征在于，还包括第三端口，用于：
    获得第五故障信息；其中，所述第三端口为所述第二类型端口，所述第五故障信息为所述第一类型故障信息或者所述第二类型故障信息；
    还包括第四端口，用于：
    发送所述第五故障信息；其中，所述第四端口为所述第二类型端口。
  20. 如权利要求15至18任一权利要求所述的通信设备，其特征在于，还包括第五端 口，用于：
    获得第六故障信息；其中，所述第五端口为所述第二类型端口，所述第六故障信息为所述第一类型故障信息；所述第五端口配置备用链路；
    启用所述第五端口对应的所述备用链路。
  21. 如权利要求15至20任一权利要求所述的通信设备，其特征在于，所述第二端口，用于：
    发送至少两个第二故障信息；
    其中，所述至少两个第二故障信息中的任两个第二故障信息之间间隔至少一个码块。
  22. 一种计算机存储介质，其特征在于，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令在被计算机调用时，使所述计算机执行如权利要求1至7任一权利要求所述的方法。
  23. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得所述计算机执行权利要求1至7任一权利要求所述的方法。
PCT/CN2018/092947 2017-08-09 2018-06-26 一种通信方法、设备及存储介质 WO2019029286A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP18843735.4A EP3661125B1 (en) 2017-08-09 2018-06-26 Communication method and device and storage medium
KR1020207006748A KR102364803B1 (ko) 2017-08-09 2018-06-26 통신 방법, 통신 장치 및 저장 매체
JP2020507659A JP7026776B2 (ja) 2017-08-09 2018-06-26 通信方法、通信デバイス、および記憶媒体
US16/784,741 US11296924B2 (en) 2017-08-09 2020-02-07 Communication method, communications device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710677029.7A CN109391494B (zh) 2017-08-09 2017-08-09 一种通信方法、设备及可读存储介质
CN201710677029.7 2017-08-09

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/784,741 Continuation US11296924B2 (en) 2017-08-09 2020-02-07 Communication method, communications device, and storage medium

Publications (1)

Publication Number Publication Date
WO2019029286A1 true WO2019029286A1 (zh) 2019-02-14

Family

ID=65272876

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/092947 WO2019029286A1 (zh) 2017-08-09 2018-06-26 一种通信方法、设备及存储介质

Country Status (6)

Country Link
US (1) US11296924B2 (zh)
EP (1) EP3661125B1 (zh)
JP (1) JP7026776B2 (zh)
KR (1) KR102364803B1 (zh)
CN (2) CN109391494B (zh)
WO (1) WO2019029286A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022520281A (ja) * 2019-02-19 2022-03-29 華為技術有限公司 フレキシブルイーサネット通信方法及びネットワーク装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109962807B (zh) * 2017-12-26 2022-04-26 华为技术有限公司 一种灵活以太网中故障指示方法以及装置
CN112448755A (zh) * 2019-08-30 2021-03-05 中兴通讯股份有限公司 一种光通道1+1保护的实现方法、装置和设备
CN112532522B (zh) * 2019-09-19 2023-09-05 中兴通讯股份有限公司 一种业务路径的建立方法、装置、电子设备
CN113037578B (zh) * 2019-12-09 2022-10-04 中盈优创资讯科技有限公司 设备捆绑口故障告警方法及装置
US11258752B2 (en) * 2020-04-13 2022-02-22 Texas Instruments Incorporated Address resolution information acquisition (ARIA) for a computing device
CN114384878B (zh) * 2021-12-31 2024-09-10 江苏核电有限公司 一种dcs系统网络故障后果的缓解方法
US20240333552A1 (en) * 2022-09-16 2024-10-03 Siliconally Gmbh Ethernet device with safety features at the physical layer and method for a bi-directional data transfer between two ethernet devices

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101351056A (zh) * 2008-09-05 2009-01-21 华为技术有限公司 一种故障信息传输的方法和装置
US20170005949A1 (en) * 2015-06-30 2017-01-05 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
CN106612220A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 灵活以太网的通道管理方法和装置
CN106911426A (zh) * 2017-02-16 2017-06-30 华为技术有限公司 一种灵活以太网中传输数据的方法及设备

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4096183B2 (ja) 2003-02-27 2008-06-04 日本電気株式会社 警報転送方法及び広域イーサネット網
US7213178B1 (en) * 2003-05-30 2007-05-01 Cisco Technology, Inc. Method and system for transporting faults across a network
JP4786571B2 (ja) 2007-03-02 2011-10-05 富士通テレコムネットワークス株式会社 データ伝送システム
US8804534B2 (en) * 2007-05-19 2014-08-12 Cisco Technology, Inc. Interworking between MPLS/IP and Ethernet OAM mechanisms
CN101998191A (zh) * 2009-08-27 2011-03-30 华为技术有限公司 汇聚节点联动切换方法及汇聚节点和系统
JP5553029B2 (ja) 2011-01-11 2014-07-16 富士通株式会社 伝送装置及び障害の通知方法
JP5743809B2 (ja) * 2011-08-26 2015-07-01 株式会社日立製作所 網管理システムおよび網管理方法
US9313093B2 (en) * 2012-11-14 2016-04-12 Ciena Corporation Ethernet fault management systems and methods
CA2925818A1 (en) * 2013-09-26 2015-04-02 Five3 Genomics, Llc Systems, methods, and compositions for viral-associated tumors
US9838290B2 (en) * 2015-06-30 2017-12-05 Ciena Corporation Flexible ethernet operations, administration, and maintenance systems and methods
CN106982105B (zh) * 2016-01-15 2020-03-31 华为技术有限公司 处理弹性以太网信号的方法和装置
US9832548B2 (en) * 2016-01-29 2017-11-28 Ciena Corporation Flexible behavior modification during restoration in optical networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101351056A (zh) * 2008-09-05 2009-01-21 华为技术有限公司 一种故障信息传输的方法和装置
US20170005949A1 (en) * 2015-06-30 2017-01-05 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
CN106612220A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 灵活以太网的通道管理方法和装置
CN106911426A (zh) * 2017-02-16 2017-06-30 华为技术有限公司 一种灵活以太网中传输数据的方法及设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
IEEE: "IEEE Standard for Ethernet", IEEE STD 802.3-2015, 31 December 2015 (2015-12-31), XP055672908 *
See also references of EP3661125A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022520281A (ja) * 2019-02-19 2022-03-29 華為技術有限公司 フレキシブルイーサネット通信方法及びネットワーク装置
JP7282187B2 (ja) 2019-02-19 2023-05-26 華為技術有限公司 フレキシブルイーサネット通信方法及びネットワーク装置
US11792067B2 (en) 2019-02-19 2023-10-17 Huawei Technologies Co., Ltd. Flexible ethernet communication method and network device

Also Published As

Publication number Publication date
KR20200037368A (ko) 2020-04-08
JP2020530964A (ja) 2020-10-29
CN109391494B (zh) 2021-02-09
CN113037540A (zh) 2021-06-25
JP7026776B2 (ja) 2022-02-28
EP3661125A4 (en) 2020-07-29
EP3661125B1 (en) 2022-04-06
CN109391494A (zh) 2019-02-26
KR102364803B1 (ko) 2022-02-17
EP3661125A1 (en) 2020-06-03
US20200177442A1 (en) 2020-06-04
US11296924B2 (en) 2022-04-05

Similar Documents

Publication Publication Date Title
WO2019029286A1 (zh) 一种通信方法、设备及存储介质
US10623293B2 (en) Systems and methods for dynamic operations, administration, and management
KR102342286B1 (ko) Dcn 메시지 처리 방법, 네트워크 디바이스, 및 네트워크 시스템
US11134029B2 (en) Communication method, communications device, and storage medium
US7394758B2 (en) Method for supporting SDH/SONET APS on Ethernet
WO2020168898A1 (zh) 一种灵活以太网通信方法及网络设备
US20210273826A1 (en) Communication method and communications apparatus
US20150172173A1 (en) Communication system, communication apparatus and path switching method
US20210385127A1 (en) Flexible ethernet communication method and network device
WO2022121638A1 (zh) 一种报文处理方法及装置
US11804982B2 (en) Communication method and apparatus
WO2023071249A1 (zh) 一种时隙协商方法及装置
US11290578B2 (en) Encapsulating and exchanging bytes in a telecommunication system

Legal Events

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

Ref document number: 18843735

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020507659

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018843735

Country of ref document: EP

Effective date: 20200228

Ref document number: 20207006748

Country of ref document: KR

Kind code of ref document: A