WO2020119474A1 - 通信方法和装置 - Google Patents

通信方法和装置 Download PDF

Info

Publication number
WO2020119474A1
WO2020119474A1 PCT/CN2019/121841 CN2019121841W WO2020119474A1 WO 2020119474 A1 WO2020119474 A1 WO 2020119474A1 CN 2019121841 W CN2019121841 W CN 2019121841W WO 2020119474 A1 WO2020119474 A1 WO 2020119474A1
Authority
WO
WIPO (PCT)
Prior art keywords
customer
flexe
network device
ring
cross
Prior art date
Application number
PCT/CN2019/121841
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 EP19896142.7A priority Critical patent/EP3886363B1/en
Priority to JP2021532928A priority patent/JP7191228B2/ja
Publication of WO2020119474A1 publication Critical patent/WO2020119474A1/zh
Priority to US17/343,192 priority patent/US11804982B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/08—Intermediate station arrangements, e.g. for branching, for tapping-off
    • H04J3/085—Intermediate station arrangements, e.g. for branching, for tapping-off for ring networks, e.g. SDH/SONET rings, self-healing rings, meashed SDH/SONET networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/42—Loop networks
    • H04L12/437—Ring fault isolation or reconfiguration
    • 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/0654—Management of faults, events, alarms or notifications using network fault recovery
    • 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/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/351—Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/356—Switches specially adapted for specific applications for storage area networks
    • H04L49/357—Fibre channel switches
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking

Definitions

  • the present application relates to the field of communications, and in particular to a ring network protection method and device applied to a flexible Ethernet cross-ring.
  • Flexible Ethernet (FlexibleEthernet, FlexE) is a new type of Ethernet developed on the basis of traditional Ethernet.
  • FlexE data is transmitted through the FlexE tunnel.
  • E2E end-to-end
  • one available method is to establish an end-to-end (E2E) protection path, that is, to establish a backup FlexE tunnel, when the working path (ie, the FlexE tunnel in use) appears
  • E2E end-to-end
  • one end of the E2E transmission path can transmit data through the protection path.
  • one end of the E2E transmission path is a service provider edge device (PE).
  • PE service provider edge device
  • FlexE will not be able to transmit data, resulting in decreased reliability of FlexE.
  • the present application provides a communication method and a communication device applied to a flexible Ethernet cross-ring. By configuring a protection path between two adjacent network devices, the reliability of FlexE can be enhanced.
  • the present application provides a communication method, which is applied to a ring network.
  • the ring network includes a first FlexE cross-ring and a second FlexE cross-ring.
  • the first FlexE cross-ring includes a first network device, a second network device, and A third network device
  • the second FlexE cross-ring includes a fourth network device, a first network device, and a second network device, the first network device is adjacent to the second network device, and the first network device is adjacent to the third network device,
  • the first network device is adjacent to the fourth network device;
  • the first network device and the second network device are intersecting nodes of the first FlexE cross-ring and the second FlexE cross-ring;
  • the first network device and the third network device have A FlexE link group, a second FlexE link group between the first network device and the fourth network device, a third FlexE link group between the first network device and the second network device, the first FlexE link group Used to carry the first customer and the fifth customer, the second FlexE link group is used to carry the
  • the first FlexE link group may be one link group or multiple link groups.
  • the first FlexE link group is a link group
  • the first customer and the fifth customer are carried on the same link group;
  • the first FlexE link group is a plurality of link groups
  • the first customer and the first Five clients can be carried on the same or different link groups.
  • the second FlexE link group and the third FlexE link group also have the same characteristics as the first FlexE link group.
  • the common node (eg, the first network device) carrying the working path can use the protection of the two FlexE cross-rings Path forwards business data.
  • the FlexE cross-ring in the prior art, there is only a working path and an E2E protection path between the sending node and the receiving node. Generally, the node carrying the working path does not carry the E2E protection path. If the working path is carried by a common node When a fault occurs, the working node cannot forward the business data through the protection path. Therefore, the FlexE cross-ring provided by this application and the automatic protection switching method based on the FlexE cross-ring improve the reliability of the ring network.
  • the method further includes: the first network device receives the third network device transmission from the third customer The first FlexE data; the first network device forwards the first FlexE data through the second customer or the fourth customer.
  • FlexE data is a code block that conforms to the FlexE protocol.
  • the first network device transmits the service data (for example, the first FlexE data) to the third network device by protecting the customer, and the third network device completes the forwarding of the service data through the protection path. Improve the reliability of the ring network.
  • the method further includes: the first network device deletes the FlexE cross between the third customer and the second customer or the fourth customer; the first The network equipment establishes a FlexE cross between the first customer and the second customer or the fourth customer.
  • the working path is usually the preferred transmission path between network devices. After the link fault of the first FlexE link group is eliminated, the first network device can choose to switch the transmission path of the service data to the working path, which can provide optimization for the service data Transmission resources.
  • the method further includes: the first network device receives the third network device's transmission through the first client The second FlexE data; the first network device forwards the second FlexE data through the second client or the fourth client.
  • the first network device After the first network device completes the path switching, it forwards the second FlexE data through the working path, so that it can provide preferred transmission resources for the second FlexE data.
  • the first FlexE link group is used to carry at least two customers, and the at least two customers form a customer binding group, and the customer binding group includes the first customer, and the customer binding group At least one customer has deployed OAM detection for operation, management and maintenance, and at least one customer in the customer binding group has not deployed OAM detection; the first network device determining that the first FlexE link group has failed includes: the first network device is based on the customer An OAM deployed by at least one customer in the bonding group detects that the first FlexE link group is faulty.
  • a plurality of work clients between the first network device and the third network device may be configured as a work client group, and a plurality of protection clients between the first network device and the third network device may be configured as a protection client group, if the first After a network device sends an OAM message to a third network device through a client in the client group and does not receive a response message, the first network device may determine the FlexE link group corresponding to the client group (for example, the first FlexE Link group) failure, no need to send OAM messages through each working customer or protection customer, thereby reducing the consumption of transmission resources.
  • the client group for example, the first FlexE Link group
  • the first link group is also used to carry seventh and eighth customers, and the third link group is also used to carry ninth customers.
  • the method further includes: the first network device determines the third The FlexE link group fails; the first network device deletes the FlexE cross between the seventh customer and the ninth client; the first network device establishes the FlexE cross between the seventh customer and the eighth customer.
  • the solution provided in this embodiment establishes a protection path between the network device and the network device in the first FlexE cross-ring, so that when the transmission path between the first network device and the second network device (for example, the third FlexE Link group) failure, the first network device can establish a FlexE cross between the working client (for example, the seventh client) and the protection client (for example, the eighth client), and pass the service data back to the third network through the protection client
  • the equipment provides a backup transmission channel for service data, thereby improving the reliability of the first FlexE cross-ring.
  • a similar guarantee mechanism can also be established in the second FlexE cross-ring.
  • the method further includes: the first network device deletes the FlexE cross between the seventh customer and the eighth customer; the first network device establishes the first FlexE cross between the seven customers and the ninth customer.
  • the path corresponding to the ninth customer is the working path.
  • the working path is usually the preferred transmission path between network devices.
  • the first network device can choose to switch the transmission path of the service data to The working path can provide optimal transmission resources for business data.
  • the third FlexE link group is used to carry at least two customers, and the at least two customers form a customer binding group, and the customer binding group includes a ninth customer, and at least A customer has deployed OAM detection, and at least one customer in the customer bonding group has not deployed OAM detection; the first network device determining that the third FlexE link group has failed includes: the first network device is based on at least one of the customer bonding group The OAM test deployed by the customer determines that the third FlexE link group has failed.
  • a plurality of work clients between the first network device and the second network device can be configured with a work client group, and a plurality of protection clients between the first network device and the second network device can be configured with a protection client group, if the first If a network device does not receive a response message after sending an OAM message to a second network device through a client in the client group, the first network device may determine the FlexE link group corresponding to the client group (for example, the third FlexE Link group) failure, no need to send OAM messages through each working customer or protection customer, thereby reducing the consumption of transmission resources.
  • the FlexE link group for example, the third FlexE Link group
  • the present application provides another communication method, which is applied to a ring network.
  • the ring network includes a first FlexE cross-ring and a second FlexE cross-ring.
  • the first FlexE cross-ring includes a first network device and a second network device
  • the third network device the second FlexE cross-ring includes a fourth network device, a first network device, and a second network device, the first network device is adjacent to the second network device, and the first network device is adjacent to the third network device ,
  • the first network device is adjacent to the fourth network device;
  • the first network device and the second network device are intersecting nodes of the first FlexE cross ring and the second FlexE cross ring;
  • the first network device and the third network device have A first FlexE link group, a second FlexE link group between the first network device and the second network device, a third FlexE link group, the first FlexE link between the first network device and the second network device
  • the group is used to carry the first customer and the fifth customer
  • the second FlexE link group is
  • the fifth customer, the third customer, and the seventh customer are customers in the ring protection path of the first FlexE cross-ring
  • the fourth customer, the sixth customer, and the eighth customer are customers in the ring protection path of the second FlexE cross-ring
  • the first network device carries the working path between the first FlexE cross-ring and the second FlexE cross-ring.
  • the first FlexE cross-ring and the second FlexE cross-ring need to determine another common node (for example, the second network Equipment), and establish an association between the protection paths of two FlexE cross-rings through the other common node, so as to facilitate the forwarding of data through the protection paths of the two FlexE cross-rings.
  • another common node for example, the second network Equipment
  • the FlexE cross-ring provided by the present application and an automatic protection switching method based on the FlexE cross-ring Improve the reliability of the ring network.
  • the method further includes: the first network device receives the first FlexE data through the seventh customer; The first network device forwards the first FlexE data through the eighth client.
  • FlexE data is a code block that conforms to the FlexE protocol.
  • the first network device implements data forwarding between the two FlexE cross-rings through the protection of two FlexE cross-rings, thereby improving the reliability of the ring network.
  • the method further includes: the second network device deletes the FlexE cross between the seventh customer and the eighth customer; the second network device establishes the seventh customer and the first FlexE cross between three customers; the second network equipment establishes FlexE cross between the eighth customer and the fourth customer.
  • the first network device can forward the data between the two FlexE cross-rings through the working path, and the second network device restores the ring protection paths of the two FlexE cross-rings, and continues to be the ring network. Provide reliability.
  • the present application also provides a communication method, which is applied to a ring network.
  • the ring network includes a first FlexE cross-ring and a second FlexE cross-ring.
  • the first FlexE cross-ring includes a first network device and a second network device
  • the third network device, the second FlexE cross-ring includes a fourth network device, a fifth network device, and a first network device, the first network device is adjacent to the second network device, and the first network device is adjacent to the third network device ,
  • the first network device is adjacent to the fourth network device, and the first network device is adjacent to the fifth network device;
  • the first network device is an intersecting node of the first FlexE cross-ring and the second FlexE cross-ring;
  • the first network device is There is a first FlexE link group between the third network device, a second FlexE link group between the first network device and the fourth network device, and a first FlexE link group between the first network device and the second network device and the fifth network device
  • the first FlexE link group may be one link group or multiple link groups.
  • first FlexE link group when the first FlexE link group is a link group, the first client and the fifth client are carried on the same link group; when the first FlexE link group is a plurality of link groups, the first client It can be carried on the same or different link group with the fifth client.
  • the second FlexE link group may be one link group or multiple link groups.
  • the third FlexE link group may be one link group or multiple link groups.
  • the common node (eg, the first network device) carrying the working path can use the protection of the two FlexE cross-rings Path forwards business data.
  • the FlexE cross-ring in the prior art, there is only a working path and an E2E protection path between the sending node and the receiving node. Generally, the node carrying the working path does not carry the E2E protection path. If the working path is carried by a common node When a fault occurs, the working node cannot forward the business data through the protection path. Therefore, the FlexE cross-ring provided by this application and the automatic protection switching method based on the FlexE cross-ring improve the reliability of the ring network.
  • the method further includes: the first network device receives the third network device transmission from the third customer The first FlexE data; the first network device forwards the first FlexE data through the second customer or the fourth customer.
  • FlexE data is a code block that conforms to the FlexE protocol.
  • the first network device transmits the service data (for example, the first FlexE data) to the third network device by protecting the customer, and the third network device completes the forwarding of the service data through the protection path. Improve the reliability of the ring network.
  • the method further includes: the first network device deletes the FlexE cross between the third customer and the second customer or the fourth customer; the first The network equipment establishes a FlexE cross between the first customer and the second customer or the fourth customer.
  • the working path is usually the preferred transmission path between network devices. After the link fault of the first FlexE link group is eliminated, the first network device can choose to switch the transmission path of the service data to the working path, which can provide optimization for the service data Transmission resources.
  • the method further includes: the first network device receives the third network device's transmission through the first client The second FlexE data; the first network device forwards the second FlexE data through the second client or the fourth client.
  • the first network device After the first network device completes the path switching, it forwards the second FlexE data through the working path, so that it can provide preferred transmission resources for the second FlexE data.
  • the first FlexE link group is used to carry at least two customers, and the at least two customers form a customer binding group, and the customer binding group includes the first customer, and the customer binding group At least one customer has deployed OAM detection for operation, management and maintenance, and at least one customer in the customer binding group has not deployed OAM detection; the first network device determining that the first FlexE link group has failed includes: the first network device is based on the customer An OAM deployed by at least one customer in the bonding group detects that the first FlexE link group is faulty.
  • a plurality of work clients between the first network device and the third network device may be configured as a work client group, and a plurality of protection clients between the first network device and the third network device may be configured as a protection client group, if the first After a network device sends an OAM message to a third network device through a client in the client group and does not receive a response message, the first network device may determine the FlexE link group corresponding to the client group (for example, the first FlexE Link group) failure, no need to send OAM messages through each working customer or protection customer, thereby reducing the consumption of transmission resources.
  • the client group for example, the first FlexE Link group
  • the first link group is also used to carry seventh and eighth customers, and the third link group is also used to carry ninth customers.
  • the method further includes: the first network device determines the third The FlexE link group fails; the first network device deletes the FlexE cross between the seventh customer and the ninth client; the first network device establishes the FlexE cross between the seventh customer and the eighth customer.
  • the solution provided in this embodiment establishes a protection path between the network device and the network device in the first FlexE cross-ring, so that when the transmission path between the first network device and the second network device (for example, the third FlexE Link group) failure, the first network device can establish a FlexE cross between the working client (for example, the seventh client) and the protection client (for example, the eighth client), and pass the service data back to the third network through the protection client
  • the equipment provides a backup transmission channel for service data, thereby improving the reliability of the first FlexE cross-ring.
  • a similar guarantee mechanism can also be established in the second FlexE cross-ring.
  • the method further includes: the first network device deletes the FlexE cross between the seventh customer and the eighth customer; the first network device establishes the first FlexE cross between the seven customers and the ninth customer.
  • the path corresponding to the ninth customer is the working path.
  • the working path is usually the preferred transmission path between network devices.
  • the first network device can choose to switch the transmission path of the service data to The working path can provide optimal transmission resources for business data.
  • the third FlexE link group is used to carry at least two customers, and the at least two customers form a customer binding group, and the customer binding group includes a ninth customer, and at least A customer has deployed OAM detection, and at least one customer in the customer bonding group has not deployed OAM detection; the first network device determining that the third FlexE link group has failed includes: the first network device is based on at least one of the customer bonding group The OAM test deployed by the customer determines that the third FlexE link group has failed.
  • a plurality of work clients between the first network device and the second network device can be configured with a work client group, and a plurality of protection clients between the first network device and the second network device can be configured with a protection client group, if the first If a network device does not receive a response message after sending an OAM message to a second network device through a client in the client group, the first network device may determine the FlexE link group corresponding to the client group (for example, the third FlexE Link group) failure, no need to send OAM messages through each working customer or protection customer, thereby reducing the consumption of transmission resources.
  • the FlexE link group for example, the third FlexE Link group
  • the present application provides a communication device including a memory including computer-readable instructions; the device further includes a processor connected to the memory, and the processor is configured to execute the computer-readable instructions to Perform the operation in the first aspect or any possible design of the first aspect, or to perform the operation in the second aspect or any possible design of the second aspect, or to perform the third aspect or the third aspect Operation in any possible design.
  • the present application also provides a computer-readable storage medium that stores computer program code in the computer-readable storage medium, and when the computer program code is executed by a processing unit or processor, causes the communication device to execute the first aspect And the operation in any one of the possible designs of the first aspect, or the communication device performs the operation in the second aspect and any possible design of the second aspect, or the communication device performs the third aspect and the third aspect Operation in any possible design.
  • the present application also provides a chip in which instructions are stored, which when executed on a communication device or a network device, causes the chip to perform the first aspect and any of the possible designs in the first aspect
  • the operation or, causes the chip to perform the operation in the second aspect and any possible design of the second aspect, or causes the chip to perform the operation in the third aspect and any possible design of the third aspect.
  • the present application also provides a computer program product, the computer program product comprising: computer program code, when the computer program code is executed by a processor of a communication device, causing the communication device to perform the first aspect and the first Aspects of any one of the possible designs of the design, or, to cause the communication device to perform the operations of the above second aspect and any of the possible designs of the second aspect, or to cause the communication device to perform the above third aspect and any of the third aspect Operation in a possible design.
  • the present application also provides a network device for performing the operations in the first aspect and any possible design of the first aspect, or for performing the second aspect and the second aspect The operation in any one of the possible designs, or for performing the operation in the third aspect and any one of the possible designs in the third aspect.
  • the present application also provides a network device, including the communication device in the fourth aspect.
  • FIG. 3 shows a schematic diagram of FlexE cross transmission technology applicable to the present application
  • FIG. 5 is a schematic diagram of a first data forwarding method of a FlexE cross-ring in a normal state provided by this application;
  • FIG. 6 is a schematic diagram of a communication method provided by this application.
  • FIG. 7 is a schematic diagram of a data forwarding method of a first FlexE cross-ring in the first failure state provided by this application;
  • FIG. 8 is a schematic diagram of a data forwarding method of a first FlexE cross-ring under a second failure state provided by this application;
  • FIG. 9 is a schematic diagram of a data forwarding method of a first FlexE cross-ring in a third fault state provided by this application.
  • FIG. 10 is a schematic diagram of a second data forwarding method of a FlexE cross-ring in a normal state provided by this application;
  • FIG. 11 is a schematic diagram of a data forwarding method of a second FlexE cross-ring in the first failure state provided by this application;
  • FIG. 12 is a schematic diagram of a data forwarding method of a second FlexE cross-ring in a second failure state provided by this application;
  • FIG. 13 is a schematic diagram of a data forwarding method of a second FlexE cross-ring in a third fault state provided by this application;
  • 16 is a schematic diagram of a data forwarding method of a second FlexE cross-ring under a fourth fault state provided by this application;
  • FIG. 18 is a schematic diagram of a third data forwarding method of a FlexE cross-ring in the first failure state provided by this application;
  • FIG. 19 is a schematic diagram of a third FlexE cross-ring data forwarding method provided in this application under a second failure state
  • FIG. 20 is a schematic diagram of a third method for forwarding data of a FlexE cross-ring in a third fault state provided by this application;
  • 21 is a schematic diagram of a node configured with a client group provided by this application.
  • 22 is a schematic diagram of another node provided with a client group provided by this application.
  • FIG. 23 is a schematic diagram of yet another node configured with a customer group provided by this application.
  • 24 is a schematic diagram of yet another node configured with a customer group provided by this application.
  • 26 is a schematic diagram of a fourth data forwarding method of a FlexE cross-ring in the first failure state provided by this application;
  • FIG. 27 is a schematic diagram of a fourth FlexE cross-ring data forwarding method provided in this application under a second fault state
  • FIG. 28 is a schematic diagram of the data forwarding method of the fourth FlexE cross-ring in the third failure state provided by this application;
  • FIG. 29 is a schematic diagram of a fourth data forwarding method of a FlexE cross-ring under a fourth fault state provided by this application;
  • FIG. 30 is a schematic diagram of an OAM message format provided by this application.
  • FIG. 31 is a schematic diagram of a fifth FlexE cross-ring provided by this application.
  • 34 is a schematic diagram of yet another communication device provided by this application.
  • nodes involved in this application may also be referred to as network equipment and network elements.
  • Nodes can be routers, packet transport network equipment, switches, firewalls, etc.
  • the above-mentioned devices are collectively referred to as nodes.
  • FIG. 1 is a schematic diagram of a FlexE transmission method suitable for this application.
  • FlexE introduces FlexE link group (FlexE Group), client (client), flexible Ethernet time division multiplexing layer (FlexE shim, hereinafter referred to as "time division multiplexing layer ”) and other concepts, in order to facilitate the understanding of the technical solutions of this application, we first briefly introduce the concepts involved in this application.
  • the FlexE link group can also be called a bundle group.
  • the FlexE link group can be interpreted as a functional module composed of multiple physical layers (physical, PHY).
  • the FlexE link group described in this application includes at least one link. For example, it may be composed of 1 to 254 PHYs supporting 100 Gigabit Ethernet (GE) rate.
  • GE Gigabit Ethernet
  • the PHY can be defined as: to provide physical, electronic, functional, and standardized characteristics for the establishment, maintenance, and removal of physical links required for data transmission.
  • the PHY may also be defined as a module having the above characteristics.
  • the PHY may be a physical layer working device at both ends of the transceiver and an optical fiber located between the receiving and sending ends.
  • the physical layer working device is, for example, a physical layer interface device.
  • Each PHY (ie, link) included in each FlexE link group has a logical bundling relationship.
  • the so-called logical bundling relationship refers to that there may be no physical connection relationship between different PHYs. Therefore, multiple PHYs in the FlexE link group may be physically independent.
  • the network equipment in FlexE can identify which links are included in a FlexE link group by the PHY number, so as to implement logical binding of multiple PHYs.
  • the number of each PHY can be identified by a number between 1 and 254, and 0 and 255 are reserved numbers.
  • a PHY number can correspond to a port on a network device. Two adjacent network devices need to use the same number to identify the same PHY.
  • the numbers of the various PHYs included in a FlexE link group need not be consecutive. Generally, there is one FlexE link group between two network devices, but this application does not limit that there is only one FlexE link group between two network devices, that is, there can be multiple FlexE between two network devices. Link group.
  • One PHY can be used to carry at least one client, and one client can transmit on at least one PHY.
  • Customer It can also be called a customer service.
  • a customer can be interpreted as an Ethernet stream based on a physical address.
  • Clients sent through the same bundling group need to share the same clock, and these clients need to be adapted according to the allocated time slot rate.
  • the bandwidth overhead of each client can be adapted by inserting/deleting idle blocks.
  • the client's identification is called Client ID, which can also be called the client identification.
  • Time-division multiplexing layer The main function of the time-division multiplexing layer is to slice data according to the same clock, and encapsulate the sliced data into pre-divided time slots (slot), and then according to the pre-configured time slot configuration table, Each divided time slot is mapped to the PHY in the bundle group for transmission, wherein each time slot is mapped to a PHY in the bundle group.
  • FlexE transmits data based on time division multiplexing (TDM) technology, and Ethernet packets are encoded into 64B/66B ("B" is short for "bit”) code blocks at the physical sub-coding layer, and based on time slots Map these code blocks to multiple different PHYs.
  • TDM time division multiplexing
  • the FlexE data described in this application may also be called a code block.
  • the Ethernet message is encoded into 64B/66B ("B" is short for "bit") code blocks at the physical sub-coding layer, and these code blocks are mapped to multiple different PHYs based on time slots .
  • FIG. 2 shows a partial architecture diagram of a FlexE applicable to the present application.
  • part of the architecture of FlexE includes a medium access control (MAC) sublayer, a time division multiplexing layer, and a physical layer, where the MAC sublayer belongs to a sublayer of the data link layer and is connected to Logical link control sublayer.
  • the physical layer can be divided into a physical coding sublayer (PCS), a physical medium access (PMA) sublayer, and a physical medium dependent (PMD) sublayer.
  • the MAC sublayer and the time division multiplexing layer and the time division multiplexing layer and the physical layer are respectively connected through a medium independent interface (MII), the physical layer is connected to the transmission medium, and the physical layer and the transmission medium pass through the medium Related interface (medium dependent interface, MDI) connection.
  • MII medium independent interface
  • MDI medium dependent interface
  • PCS In the process of sending signals, PCS is used to encode data, scramble (scrambled), insert overhead (OH), and insert alignment markers (AM).
  • PCS In the process of receiving signals, PCS The reverse process of the above steps will be carried out. Sending and receiving signals can be realized by different functional modules of PCS.
  • the main functions of the PMA sublayer are link monitoring, carrier monitoring, coding and decoding, transmission clock synthesis, and reception clock recovery.
  • the main functions of the PMD sublayer are scrambling/descrambling of data streams, coding and decoding, and DC restoration and adaptive equalization of received signals.
  • RS reconciliation sublayer
  • FEC forward error correction
  • FIG. 3 shows a schematic diagram of the FlexE cross transmission technology applicable to the present application.
  • the service provider edge (PE) device PE1 receives the Ethernet message sent by the user through the user network interface (UNI) and performs processing on the Ethernet message. For example, the Ethernet is sent at the physical coding sublayer
  • the message is encoded into 64B/66B data blocks, and these data blocks are mapped to the PHY based on the time slot.
  • an overhead frame or overhead multiframe is generated, and the overhead frame or overhead multiframe is transmitted to a service provider (P) device through a transmission medium (for example, optical fiber) .
  • a transmission medium for example, optical fiber
  • the time division multiplexing layer of the P device sends out from the unique output path based on the FlexE cross configuration. Therefore, FlexE crossover can also be interpreted as establishing the connection between the input path and the output path.
  • PE2 After receiving the above-mentioned overhead frame or overhead multiframe, PE2 decodes the overhead frame or overhead multiframe, obtains the Ethernet packet sent by PE1, and sends the Ethernet packet through the UNI of PE2.
  • the reason why the names of the P device and the PE device are different is that they are in different positions.
  • the P device obtains the Ethernet message to be transmitted through the UNI, the P device is converted into a PE device.
  • the PE device acts as a node that performs FlexE cross processing, the PE device is converted to a P device.
  • this application provides a communication method, which is applied to a FlexE cross-ring composed of at least three nodes.
  • FIG. 4 shows a schematic diagram of a FlexE ring network (that is, a ring Ethernet using FlexE crossover technology) provided by this application.
  • the FlexE link group between node 1 and node 3 can be called link group 1
  • the FlexE link group between node 1 and node 4 can be called link group 2
  • the link between node 1 and node 2 The FlexE link group may be referred to as link group 3.
  • Each link group carries at least one working path and/or at least one protection path.
  • the working path described in this application may also be referred to as a working channel, which refers to a path configured for system service data transmission.
  • a working FlexE link group When a FlexE link group only carries a working path, the FlexE link group may be referred to as a working FlexE link group.
  • the protection path described in this application may also be referred to as a protection channel, which refers to a backup path of the working path configured by the system, that is, a path for performing business data transmission instead of the working path when the working path cannot transmit business data.
  • the FlexE link group may be referred to as a protected FlexE link group.
  • the FlexE ring network shown in FIG. 4 is composed of two FlexE cross-rings, and each FlexE cross-ring includes 3 nodes, where node 1 and node 2 are nodes shared by the two FlexE cross-rings, and the FlexE where node 3 is located crosses The ring is ring 1, and the FlexE cross-ring where node 4 is located is ring 2.
  • each node is, for example, the P device shown in FIG. 3.
  • the working path and the protection path are data channels based on physical links (for example, optical fibers), and the working path and the protection path are both bidirectional paths.
  • data can be transmitted from node 3 to node 1 through the working path, and data can also pass through
  • the working path is transferred from node 1 to node 3.
  • Different paths correspond to different customers, so you can use the customer's logo to describe the working path or protection path.
  • Customers corresponding to the working path may be called working customers, for example, customer 1 and customer 2; customers corresponding to the protection path may be called protecting customers, for example, customer 3, customer 4, customer 5, customer 6, customer 7, and customer 8.
  • the above working path and protection path are pre-configured paths.
  • the sending end for example, node 3
  • the receiving end for example, node 4
  • the E2E working path between the sending end and the receiving end needs to be configured , That is, the working path corresponding to customer 1 and customer 2, you also need to configure the protection path in each FlexE cross-ring, that is, the protection path corresponding to customer 3, customer 5 and customer 7, and customer 4, customer 6 and customer 8 corresponding protection path.
  • Nodes need some time slots when transmitting data through clients. These time slots are allocated to at least one PHY in the FlexE link group. FlexE crossover means time slot crossover. For example, there are n time slots allocated to client 1 in the PHY corresponding to client 1; m time slots allocated to client 2 in the PHY corresponding to client 2. Node 1 receives data from the PHY corresponding to customer 1 through the n time slots occupied by customer 1. When forwarding the data to node 4, node 1 uses the FlexE crossover established between customer 1 and customer 2 and passes the m occupied by customer 2 The time slots and the PHY corresponding to client 2 forward the data to node 4.
  • the protection path In the default state, the protection path is in a closed loop state, and there is a FlexE cross between customers corresponding to the two protection paths. For example, there is a FlexE cross between customer 5 and customer 3, and there is a FlexE cross between customer 5 and customer 7. There is a FlexE cross between 7 and customer 3, as shown by the dotted lines in node 1, node 3, and node 2 in Figure 4.
  • the working path is in an open loop state, and there is also a FlexE intersection between customers corresponding to two adjacent working paths. For example, there is a FlexE intersection between customer 1 and customer 2, as shown by the solid line in node 1 in FIG. 4.
  • the PE node (for example, node 3) can determine the corresponding FlexE interface (that is, customer 1) to forward by looking up the virtual local area network (VLAN) identifier corresponding to the service data .
  • VLAN virtual local area network
  • FIG. 5 shows a schematic diagram of a method for providing service data in a ring and a ring.
  • node 3 After node 3 obtains the business data through the UNI, it performs the ring processing, that is, finds the customer corresponding to the business data. For example, if the destination address of the business data is node 4, then node 3 can select the transmission path of “node 3 ⁇ node 1 ⁇ node 4” and send the business data to node 1 through client 1, where node 1 acts as two FlexEs. The intersecting nodes of the ring.
  • node 1 After receiving the business data through customer 1, node 1 sends the business data through customer 4 based on the FlexE cross between customer 1 and customer 2.
  • the node 4 After receiving the service data through the client 2, the node 4 performs the lower loop processing, that is, sends the service data through the UNI of the node 3.
  • node 3 after node 3 obtains business data through UNI and determines the transmission path, it can select customer 1 to send business data from multiple customers according to the VLAN ID corresponding to the business data, that is, when node 2 is the sending end, customer 1 is A ring client; if node 3 as the receiving end receives service data from other nodes through client 1, node 3 can perform ring processing on the service data and send the service data through UNI, that is, node 3 as the receiving end Customer 1 is a lower ring customer.
  • the upper ring customer and the lower ring customer of each node are the customer configuration when node 3 is used as the PE node. If node 3 is no longer a PE node, the upper ring customer and the lower ring customer of each node Reconfiguration is required, that is, the configuration of the upper ring customer and the lower ring customer of each node in the FlexE cross-ring corresponds to the PE node.
  • the forwarding process described above is a data forwarding process when each path of the FlexE cross-ring is working normally. If the FlexE link group between node 1 and node 3 fails, node 1 can perform the method shown in FIG. 6 to complete data forwarding.
  • the method 600 includes:
  • Node 1 can determine that link group 1 fails according to the operation management and maintenance (OAM) function of FlexE.
  • OAM operation management and maintenance
  • node 1 After node 1 sends an OAM message to node 3 through client 1, and does not receive a response message of the OAM message within N cycles, node 1 determines that link group 1 is faulty. Among them, the OAM message is used to detect the connectivity of the path between the nodes.
  • node 1 determines that link group 1 fails.
  • Node 1 deletes the FlexE cross between customer 3 and customer 5.
  • node 1 establishes a FlexE cross between customer 3 and customer 2 or customer 4.
  • the common node (for example, node 1) carrying the working path can use the protection paths of the two FlexE cross-rings to forward Business data.
  • the FlexE cross-ring in the prior art there is only an E2E working path and an E2E protection path between the sending node and the receiving node.
  • the working path and the protection path both fail.
  • the node carrying the E2E working path does not carry the E2E protection path. If the working path carried by the public node fails, the node carrying the working path cannot forward service data through the protection path. Therefore, the FlexE cross-ring provided in this application and the FlexE cross-over The automatic protection switching method of the ring improves the reliability of the FlexE cross-ring.
  • FIG. 7 shows an embodiment of the method 600.
  • the node 1 may perform the following steps to forward data:
  • node 1 Since link group 2 also fails, node 1 needs to forward the service data through the protection path of ring 2. After the service data is looped from node 3, the service data is transmitted to node 2 through customer 7 and node 2 is based on customer 7 and customer 3. The FlexE crossover between customers transfers business data to node 1 through node 3. Node 1 transfers business data to node 2 based on the FlexE crossover between customers 3 and 4 and node 2 based on the FlexE crossover between customers 4 and 8 The business data is transmitted to node 4, and customer 8 is the lower ring customer of node 4 under the abnormal condition of ring 2. After receiving the business data through customer 8, node 4 forwards the business data through the UNI interface, thus completing the forwarding of the business data .
  • FIG. 7 is only an example, and business data can also be transmitted from node 4 to the ring, and then transmitted to the lower ring of node 3 through the transmission path “customer 8 ⁇ customer 4 ⁇ customer 3 ⁇ customer 7”.
  • node 1 can perform the following steps to send service data:
  • the service data is transmitted to the lower ring of node 4 via the transmission path "Customer 1 ⁇ Customer 4 ⁇ Customer 8", as shown in Figure 8.
  • Fig. 8 is only an example, and the service data can also be transmitted from the node 4 to the ring, and then transmitted to the node 3 to the ring via the transmission path "customer 8 ⁇ customer 4 ⁇ customer 1".
  • node 1 can perform the following steps to send service data:
  • the service data is transmitted to the lower ring of node 4 through the transmission path "Customer 1 ⁇ Customer 2", which is the transmission path shown in FIG.
  • the working path is usually the preferred transmission path between the nodes.
  • the nodes in the FlexE cross-ring can choose to preferentially transmit service data through the working path, so as to provide optimal transmission resources for the service data.
  • FIG. 9 shows another embodiment of the method 600.
  • the node 1 may perform the following steps to forward data:
  • the lower ring client is a client configured in advance (for example, client 2), and the lower ring client will not be affected by the FlexE cross ring where the sending end node is located (for example, ring 1) ) A failure occurs and changes. Therefore, in the case where the ring 2 is working normally, the node 1 needs to establish a FlexE cross between the client 3 and the client 2, so that the node 4 can process the business data through the client 2 to the ring.
  • the service data can also be transmitted from the node 4 to the ring, and then transmitted to the node 3 to the ring via the transmission path "customer 2 ⁇ customer 3 ⁇ customer 7".
  • node 1 can perform the following steps to send service data:
  • the service data is transmitted to the lower ring of node 4 through the transmission path "Customer 1 ⁇ Customer 2", which is the transmission path shown in FIG.
  • the working path is usually the preferred transmission path between nodes. After the link fault of link group 1 is eliminated, the nodes in the FlexE cross-ring can choose to preferentially transmit service data through the working path, which can provide optimal transmission resources for service data.
  • FIG. 10 is a schematic diagram of another FlexE cross-ring provided in this application.
  • NE5, NE6, NE7, NE9, NE10, NE11, NE12, and NE13 constitute another FlexE cross-ring (ie, Ring 2), where NE10 is connected to CE2 as a PE device.
  • the aforementioned NE may also be called a node or a network device.
  • the service data sent by CE1 passes NE1 to the ring, and then can be transmitted to the ring of NE4 according to the transmission path of "NE1 ⁇ NE8 ⁇ NE7 ⁇ NE9 ⁇ NE10".
  • the related nodes of Ring 1 and Ring 2 can forward the service data according to the following method.
  • NE8 After NE8 determines that the FlexE link group between NE7 and NE8 is faulty, it can delete the FlexE cross between two working customers of NE8, and at the same time, establish a FlexE cross between NE8's working customers and protection customers to pass business data through The protection path between NE8 and NE1 is transmitted to NE1, and then, the service data is transmitted counterclockwise to NE7 through the protection path of ring 1.
  • NE7 After NE7 determines that the FlexE link group between NE7 and NE8 is faulty, it can delete the FlexE crossover between NE7's protection customers and NE8's protection customers, and at the same time, establish a connection between ring 1's protection customers and ring 2's working customers. FlexE crosses and transmits service data to NE9 through the working path of ring 2. NE9 transmits the service data to the lower ring of NE10 based on the working path of ring 2.
  • the service data is finally transmitted to the lower ring of NE10 according to the transmission path of “NE1 ⁇ NE2 ⁇ NE3 ⁇ NE4 ⁇ NE5 ⁇ NE6 ⁇ NE7 ⁇ NE9 ⁇ NE10”, as shown in FIG. 11.
  • NE1 can also directly send service data to NE2 through the protection path, and no longer send service data to NE8.
  • Ring 1 and Ring 2 can forward service data according to the transmission path shown in FIG. 10.
  • the related nodes of Ring 1 and Ring 2 can forward the service data according to the following method.
  • NE8 After NE8 determines that the FlexE link group between NE7 and NE8 is faulty, it can delete the FlexE cross between two working customers of NE8, and at the same time, establish a FlexE cross between NE8's working customers and protection customers to pass business data through The protection path between NE8 and NE1 is transmitted to NE1, and then, the service data is transmitted counterclockwise to NE7 through the protection path changed to 1.
  • the service data is finally transmitted to the lower ring of NE10 according to the transmission path of “NE1 ⁇ NE2 ⁇ NE3 ⁇ NE4 ⁇ NE5 ⁇ NE6 ⁇ NE7 ⁇ NE6 ⁇ NE5 ⁇ NE13 ⁇ NE12 ⁇ NE11 ⁇ NE10”, as shown in FIG. 12.
  • NE1 can also directly send service data to NE2 through the protection path, and no longer send service data to NE8.
  • Ring 1 and Ring 2 can forward the service data according to the transmission path shown in FIG. 13.
  • Ring 1 and Ring 2 can forward services according to the transmission path shown in FIG. 10 data.
  • FlexE ring 10 shown in FIG crossing may also be applied in the 4th generation (4 th generation, 4G) mobile communication system, wherein, CEl direct connection to the 4G mobile communication system, a base station (eNB), or an indirect connection.
  • FlexE cross ring 10 shown in FIG. 5 may also be applied at the generation of (5 th generation, 5G) mobile communication system, which, may be directly connected to CEl 5G mobile communication system, a base station (GNB) or indirectly.
  • the FlexE cross-ring shown in FIG. 10 may also be in a cross-layer network architecture, where NE1 may be connected to an access layer device, and NE10 may be connected to an aggregation layer device or a core layer device.
  • the above solutions are all data forwarding solutions when the public node carrying the working path (for example, node 1 in FIG. 4) works normally. If the public node carrying the working path fails, you need to carry only the public node of the protection path (for example, Node 2 in Figure 4) establishes a FlexE cross between the two rings.
  • FIG. 14 shows another communication method applied to the FlexE cross-ring provided by this application.
  • the method 1400 may be performed by the node 2 in FIG. 4.
  • Method 1400 includes:
  • node 2 determines that node 1 has failed.
  • node 2 deletes the FlexE cross between customer 3 and customer 7.
  • node 2 deletes the FlexE cross between customer 4 and customer 8.
  • node 2 establishes a FlexE cross between customer 7 and customer 8.
  • Nodes adjacent to node 1 can determine that node 1 fails based on the OAM function. After node 3 determines that node 1 is faulty, customer 7 is determined to be a ring customer, deletes the FlexE cross between customer 7 and customer 5, and forwards the business data of the ring through customer 7; node 2 determines that node 1 fails, and establishes a customer 3 FlexE cross between customer 4 and forward the business data received through customer 7 through customer 8; after node 4 determines that node 1 fails, customer 8 is determined to be the lower ring customer and deletes customer 8 and customer 6 FlexE cross-connects and processes the business data received through the customer 8 in the next loop.
  • the above forwarding process is shown in Figure 15.
  • node 2 Since node 2 carries the protection paths of the two FlexE cross-rings, when the node carrying the working path (ie, node 1) fails, node 2 can establish a FlexE cross between the two protection customers, thus completing the cross-FlexE
  • the service data forwarding of the cross-ring enhances the reliability of the ring network composed of multiple FlexE cross-rings.
  • node 3 After node 3 determines that the fault of node 1 is eliminated, it continues to send service data through the working path carried by node 1, that is, the sending path shown in FIG. 5.
  • NE7 fails, NE8 and NE6 can determine that NE7 fails based on the OAM function, and perform corresponding processing on the forwarding path, as shown in FIG. 16.
  • NE8 deletes the FlexE cross between two work customers (work customers between NE1 and NE8, and work customers between NE8 and NE7), and establishes protection work customers (work customers between NE1 and NE8) and protection customers ( The FlexE between the protection client between NE1 and NE8 crosses and forwards the message sent by NE1 to NE6 through the protection path of ring 1.
  • NE6 deletes the FlexE cross between two protection clients (the protection client between NE5 and NE6, and the protection client between NE6 and NE7), and establishes the FlexE cross between the protection client of Ring 1 and the protection client of Ring 2 , Forward the service data to NE10 through the protection path of change 2.
  • NE10 processes the service data in the lower ring, thereby completing the forwarding of service data across FlexE cross-rings in the case of NE7 failure, enhancing the reliability of the ring network composed of multiple FlexE cross-rings.
  • the present application also provides a FlexE cross-ring.
  • Each node in the FlexE cross-ring has multiple working paths and multiple protection paths, and the multiple working paths correspond to the multiple protection paths in one-to-one correspondence.
  • node 1 includes three physical ports (ie, PHY), which are an east physical port, a west physical port, and a south physical port.
  • PHY physical ports
  • the node 1 shown in FIG. 21 is only an example, and the node 1 may also include more physical ports.
  • the eastbound physical port corresponds to 4 customers, namely customer 2, customer 10, customer 6 and customer 16, of which customer 2 and customer 10 are working customers (ie, customers corresponding to the working path), customer 6 and customer 16 are Protect customers (ie, customers corresponding to the protection path).
  • the west-facing physical port corresponds to four customers, namely customer 1, customer 9, customer 5 and customer 11, of which customer 1 and customer 9 are working customers, and customer 5 and customer 11 are protection customers.
  • the west-facing physical port corresponds to four customers, namely customer 12, customer 3, customer 4 and customer 14, which are all protected customers.
  • the two working clients of the east physical port are configured as a client group (client group); that is, the working client group 1; the two working clients of the west physical port are configured as another client group, that is, working client group 2.
  • client group the customer group may also be referred to as a customer binding group.
  • the two protection clients on the east physical port are configured as one client group, that is, protection client group 1, and the two protection clients on the west physical port are configured as another client group, that is, protection client group 2.
  • the four protection customers of the southbound physical port are configured as two customer groups, namely, protection customer group 3 and protection customer group 4.
  • the above example of the customer group is only for illustration.
  • the number of customers in the customer group provided in this application may also be other numbers, for example, 3 customers as a customer group, or more customers as a customer group.
  • node 2, node 3 and node 4 can also be configured with working client groups and protection client groups.
  • the configuration results are shown in Figure 22 to Figure 24.
  • the FlexE cross-ring including the four nodes shown in FIGS. 21 to 24 is shown in FIG. 25.
  • node 1 can delete the FlexE cross between the working client group of the west physical port and the east physical port, and establish two protection client groups of the south physical port The FlexE between them will send the service data from the protection client group of the south to the physical port.
  • the above transmission path is shown in FIG. 26.
  • node 1 can delete the FlexE cross between the working client group of the west physical port and the east physical port, and establish a working client group of the west physical port and a protection client group of the south physical port FlexE crosses between them to send business data from the protection client group to the physical port on the south.
  • the above transmission path is shown in Fig. 27.
  • link group 1 If link group 1 fails, node 1 can delete the FlexE cross between the working client group of the west physical port and the east physical port, and establish a protection client group of the south physical port and the working client of the east physical port FlexE crosses between groups to send business data from the working customer group to the physical port on the east.
  • the above transmission path is shown in FIG. 28.
  • node 2 can delete the FlexE cross between the two protected client groups that delete the west physical port and the north physical port, and delete the two protected client groups that delete the east physical port and the north physical port FlexE crossover, and establish a FlexE crossover between the protection client group of the west physical port and the protection client group of the east physical port to send business data from the protection client group of the east physical port.
  • the above transmission path is shown in FIG. 29.
  • the FlexE cross based on the customer group can Reduce the cost of path switching.
  • This application also provides a method for detecting the fault of the FlexE cross-ring, which is applied to the FlexE cross-ring including the customer group as shown in FIG. 25.
  • the method includes:
  • Node 1 sends an OAM message to node 3 through working client 1.
  • the OAM message is used to detect the connectivity of the FlexE link group between node 1 and node 3.
  • node 1 determines that the FlexE link group between node 1 and node 3 fails, and does not need to pass client 9 or Client 5 sends an OAM message, thereby reducing OAM message overhead.
  • using the FlexE cross-ring of the customer group can reduce the workload of configuring OAM.
  • Node 1 can also determine that the FlexE link group of the west-facing physical port has failed according to the failure to receive the OAM message sent by node 3 within N cycles.
  • the OAM message can use the message format shown in Figure 30.
  • the OAM message adopts the coding format of 66B code block.
  • the numbers 0 to 65 in the first line are the sequence number of 66 bits.
  • the first two bits are overhead bits, starting from bit 2, 8 adjacent
  • the bits are divided into one byte, and the following 64 bits are divided into 8 bytes in total.
  • the first byte (2-9) uses 0x4B to indicate the control type of the 66B code block, which is used to identify the O code, that is, the sorting control character defined by IEEE802.3.
  • the first two bits are the reserved field (Resv), and the last six bits are the type field (Type), indicating the OAM message type.
  • the 66B code block is a BAS code block, and one function of the BAS code block is to detect the connectivity of the path.
  • the BAS code block is the second OAM message described above.
  • the 66B code block is an APS code block.
  • One function of the APS code block is to detect and instruct the node to perform automatic protection switching, for example, to delete the FlexE cross between working clients in two directions and establish FlexE cross between working customers and protecting customers in the same direction.
  • the APS code block is the OAM message described above.
  • the third byte (18-25), the fourth byte (26-33), the sixth byte (42-49) and the seventh byte (50-57) are the Value fields. Used to carry OAM values.
  • the first 4 bits use 0xC as the identifier of the OAM information block.
  • the first 4 bits represent the sequence (Seq) field, and its value can indicate different meanings represented by different code block sequences in the multi-code block message.
  • the sequence field can be filled with an invalid value, for example 0000.
  • the last 4 bits of the eighth byte are the cyclic redundancy check (CRC) field, which is used to check the integrity of the above eight bytes (except the CRC field).
  • CRC cyclic redundancy check
  • the coding format shown in FIG. 30 is only an example, and the application does not limit the coding format of the OAM message.
  • the 64B coding format can also be used to encode the OAM message.
  • a ring network with a multi-ring architecture that is, a ring network including at least two FlexE cross-rings
  • a data forwarding method in the ring network It should be noted that for any ring described above It can also contain a single ring architecture.
  • FIG. 31 shows a ring network including a single ring architecture and a multi-ring architecture.
  • node 1 can delete the FlexE cross between customer 1 ⁇ and customer 3 ⁇ , and establish the FlexE cross between customer 1 ⁇ and customer 5, so that it can pass the customer 1 ⁇
  • the received data is transmitted back to the node 3 through the client 5, and the node 3 can send the data to the node 2 through the client 7, thereby completing the data forwarding in the single ring architecture.
  • the solution provided in this embodiment establishes a protection path between nodes in ring 1, so that when the transmission path between node 1 and node 2 (eg, link group 3) fails, node 1 can
  • the FlexE cross between the working client (for example, client 1) and the protection client (for example, client 5) is established.
  • the business data is transmitted back to node 3, which provides a backup transmission channel for the business data, thereby improving Reliability of FlexE cross-rings.
  • a similar guarantee mechanism can also be established in Ring 2.
  • FIG. 31 shows an example where the single-ring architecture and the multi-ring architecture share the same protection path (the protection path formed by customers 1, customers 7, and customers 3). It can be understood that the single-ring architecture and the multi-ring architecture may not be shared.
  • the same protection path that is, a new ring protection path is created to provide transmission protection for the working path composed of customer 1 ⁇ , customer 7 ⁇ and customer 3 ⁇ .
  • the communication device includes a hardware structure and/or a software module corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed by hardware or computer software driven hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
  • the present application may divide the functional unit of the data transmission device according to the above method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above integrated unit may be implemented in the form of hardware or software functional unit. It should be noted that the division of units in this application is schematic, and is only a division of logical functions. In actual implementation, there may be other division methods.
  • FIG. 32 shows a schematic diagram of a communication device provided by this application.
  • the communication device 3200 can be applied to the network architecture shown in FIG. 4, FIG. 10 or FIG. 25, for example, can be applied to the node 1 in the network architecture shown in FIG. 4, or NE7 of the network architecture shown in FIG. Node 1 in the network architecture shown in 25.
  • the communication device 3200 may include a processor 3210, a memory 3220 coupled to the processor 3210, and a communication interface 3230.
  • the processor 3210 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.
  • the processor may further include other hardware chips.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or a combination thereof.
  • the processor 3210 may refer to one processor, or may include multiple processors.
  • the memory 3220 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory 3220 may also include non-volatile memory (non-volatile memory), such as read-only memory (read -only memory (ROM), flash memory (flash), hard disk drive (HDD) or solid state disk (SSD); the memory 3220 may also include a combination of the aforementioned different types of memory.
  • the memory 3220 may refer to one memory, or may include multiple memories.
  • the memory 3220 stores computer readable instructions.
  • the computer readable instructions may include multiple software modules, such as a sending module 3221, a processing module 3222, and a receiving module 3223.
  • the processor 3210 runs each of the above software modules, it can perform corresponding operations according to the instructions of each software module.
  • the operation performed by one software module actually refers to the operation performed by the processor 3210 according to the instruction of the software module.
  • the processor 3210 runs the processing module 3222 and executes:
  • the processor 3210 may be, for example, the processor in the node 1 shown in FIG. 4, the first FlexE link group is, for example, the link group 1 shown in FIG. 4, the third customer is, for example, the customer 3, and the fifth customer is, for example, the customer 5.
  • the second customer is, for example, customer 2, and the fourth customer is, for example, customer 4.
  • the common node (for example, node 1) carrying the working path can use the protection paths of the two FlexE cross-rings to forward Business data.
  • the common node for example, node 1
  • the node carrying the working path does not carry the E2E protection path. If the working path is carried by a common node When a fault occurs, the working node cannot forward the business data through the protection path. Therefore, the FlexE cross-ring provided by this application and the automatic protection switching method based on the FlexE cross-ring improve the reliability of the ring network.
  • the processor 3210 may also execute after running the receiving module 3223:
  • the third network device is, for example, node 3 in FIG. 4, FlexE data is a code block that conforms to the FlexE protocol, and the first network device (for example, node 1 in FIG. 4) protects the customer’s business data (for example, the first FlexE data ) Back to the third network device, the third network device completes the forwarding of the service data through the protection path, thereby improving the reliability of the ring network.
  • the processor 3210 runs the processing module 3222 and executes:
  • the first customer is, for example, customer 1 in FIG. 4.
  • the working path is usually the preferred transmission path between network devices. After the link fault of the first FlexE link group is eliminated, the first network device can choose to switch the transmission path of the service data to the working path, which can provide optimization for the service data Transmission resources.
  • the processor 3210 may also execute after running the receiving module 3223:
  • the first network device After the first network device completes the path switching, it forwards the second FlexE data through the working path, so that it can provide preferred transmission resources for the second FlexE data.
  • the first FlexE link group may be used to carry at least two customers, and the at least two customers form a customer binding group, and the customer binding group includes the first customer, and at least one customer in the customer binding group deploys OAM It is detected that at least one customer in the customer binding group has not deployed OAM detection; the processor 3210 may execute after running the processing module 3222:
  • a plurality of work clients between the first network device and the third network device may be configured as a work client group, and a plurality of protection clients between the first network device and the third network device may be configured as a protection client group, if the first After a network device sends an OAM message to a third network device through a client in the client group and does not receive a response message, the first network device may determine the FlexE link group corresponding to the client group (for example, the first FlexE Link group) failure, no need to send OAM messages through each working customer or protection customer, thereby reducing the consumption of transmission resources.
  • the client group for example, the first FlexE Link group
  • the first link group is also used to carry seventh and eighth customers
  • the third link group is also used to carry ninth customers
  • the processor 3210 may also execute after running the processing module 3222:
  • the seventh customer is, for example, customer 1 ⁇ shown in FIG. 31
  • the eighth customer is, for example, customer 5 shown in FIG. 31
  • the ninth customer is, for example, customer 3 ⁇ shown in FIG. 31.
  • the solution provided in this embodiment establishes a protection path between the network device and the network device in the first FlexE cross-ring, so that when the transmission path between the first network device and the second network device (for example, the third FlexE Link group) failure, the first network device can establish a FlexE cross between the working client (for example, the seventh client) and the protection client (for example, the eighth client), and pass the service data back to the third network through the protection client
  • the equipment provides a backup transmission channel for service data, thereby improving the reliability of the first FlexE cross-ring.
  • a similar guarantee mechanism can also be established in the second FlexE cross-ring.
  • the processor 3210 may also execute after running the processing module 3222:
  • the path corresponding to the ninth customer is the working path.
  • the working path is usually the preferred transmission path between network devices.
  • the first network device can choose to switch the transmission path of the service data to The working path can provide optimal transmission resources for business data.
  • the third FlexE link group is used to carry at least two customers.
  • the at least two customers form a customer binding group.
  • the customer binding group includes a ninth customer.
  • At least one customer in the customer binding group has deployed OAM detection.
  • the road group is faulty.
  • a plurality of work clients between the first network device and the second network device can be configured with a work client group, and a plurality of protection clients between the first network device and the second network device can be configured with a protection client group, if the first If a network device does not receive a response message after sending an OAM message to a second network device through a client in the client group, the first network device may determine the FlexE link group corresponding to the client group (for example, the third FlexE Link group) failure, no need to send OAM messages through each working customer or protection customer, thereby reducing the consumption of transmission resources.
  • the FlexE link group for example, the third FlexE Link group
  • FIG. 33 shows a schematic diagram of another communication device provided by this application.
  • the communication device 3300 can be applied to the network architecture shown in FIG. 4, FIG. 10, or FIG. 25, for example, can be applied to the node 2 in the network architecture shown in FIG. 4, or NE6 of the network architecture shown in FIG. Node 2 in the network architecture shown in 25.
  • the communication device 3300 may include a processor 3310, a memory 3320 coupled to the processor 3310, and a communication interface 3330.
  • the processor 3310 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.
  • the processor may further include other hardware chips.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or a combination thereof.
  • the processor 3310 may refer to one processor, or may include multiple processors.
  • the memory 3320 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory 3320 may also include non-volatile memory (non-volatile memory), such as read-only memory (read -only memory (ROM), flash memory (flash), hard disk drive (HDD) or solid state disk (SSD); the memory 3320 may also include a combination of the above-mentioned different types of memory.
  • the memory 3320 may refer to one memory, or may include multiple memories.
  • the memory 3320 stores computer readable instructions.
  • the computer readable instructions may include multiple software modules, such as a sending module 3321, a processing module 3322, and a receiving module 3323.
  • the processor 3310 runs each of the above software modules, it can perform corresponding operations according to the instructions of each software module.
  • the operation performed by one software module actually refers to the operation performed by the processor 3310 according to the instruction of the software module.
  • the processor 3310 executes the processing module 3322 and executes:
  • the first network device is, for example, node 1 in FIG. 4, the third customer is, for example, customer 3 in FIG. 4, the seventh customer is, for example, customer 7 in FIG. 4, the fourth customer is, for example, customer 4 in FIG. 4, The eight customers are, for example, customers 8 in FIG. 4.
  • the fifth customer, the third customer, and the seventh customer are customers in the ring protection path of the first FlexE cross-ring
  • the fourth customer, the sixth customer, and the eighth customer are customers in the ring protection path of the second FlexE cross-ring
  • the first network device carries the working path between the first FlexE cross-ring and the second FlexE cross-ring.
  • the common node for example, the first network device
  • the first FlexE cross-ring and the second FlexE cross-ring need to pass through another common node (for example, the second network Equipment) establishes the association between the protection paths of the two FlexE cross-rings to facilitate data forwarding.
  • the FlexE cross-ring provided by the present application and an automatic protection switching method based on the FlexE cross-ring Improve the reliability of the ring network.
  • the processor 3310 may also execute after running the receiving module 3323:
  • the processor 3310 may also execute after running the sending module 3321:
  • FlexE data is a code block that conforms to the FlexE protocol.
  • the first network device implements data forwarding between the two FlexE cross-rings through the protection of two FlexE cross-rings, thereby improving the reliability of the ring network.
  • the processor 3310 may also execute after running the processing module 3322:
  • the first network device can forward the data between the two FlexE cross-rings through the working path.
  • the processor 3310 restores the ring protection paths of the two FlexE cross-rings and continues to be the ring network. Reliability is guaranteed.
  • FIG. 34 shows a schematic diagram of yet another communication device provided by this application.
  • the communication device 3400 can be applied to the network architecture shown in FIG. 17, for example, it can be applied to the node 1 in the network architecture shown in FIG. 17.
  • the communication device 3400 may include a processor 3410, a memory 3420 coupled to the processor 3410, and a communication interface 3430.
  • the processor 3410 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.
  • the processor may further include other hardware chips.
  • 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 (complex programmable logic device (CPLD), field programmable gate array (FPGA), general array logic (GAL) or a combination thereof.
  • the processor 3410 may refer to one processor, or may include multiple processors.
  • the memory 3420 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory 3420 may also include non-volatile memory (non-volatile memory), such as read-only memory (read -only memory (ROM), flash memory (flash), hard disk drive (HDD) or solid state disk (SSD); the memory 3420 may also include a combination of the above-mentioned different types of memory.
  • the memory 3420 may refer to one memory, or may include multiple memories.
  • the memory 3420 stores computer-readable instructions.
  • the computer-readable instructions may include multiple software modules, such as a sending module 3421, a processing module 3422, and a receiving module 3423.
  • the processor 3410 runs each of the above software modules, it can perform corresponding operations according to the instructions of each software module.
  • the operation performed by one software module actually refers to the operation performed by the processor 3410 according to the instruction of the software module.
  • the processor 3410 runs the processing module 3422 and executes:
  • the processor 3410 may be, for example, the processor in the node 1 shown in FIG. 17, the first FlexE link group is, for example, the link group 1 shown in FIG. 4, the third customer is, for example, the customer 3, and the fifth customer is, for example, the customer 5.
  • the second customer is, for example, customer 2, and the fourth customer is, for example, customer 4.
  • the common node (for example, node 1) carrying the working path can use the protection paths of the two FlexE cross-rings to forward Business data.
  • the common node for example, node 1
  • the node carrying the working path does not carry the E2E protection path. If the working path is carried by a common node When a fault occurs, the working node cannot forward the business data through the protection path. Therefore, the FlexE cross-ring provided by this application and the automatic protection switching method based on the FlexE cross-ring improve the reliability of the ring network.
  • the processor 3410 may also execute after running the receiving module 3423:
  • the third network device is, for example, node 3 in FIG. 17, and the FlexE data is a code block that conforms to the FlexE protocol.
  • the first network device (for example, node 1 in FIG. 17) transfers the service data (for example, the first FlexE data) by protecting customers ) Back to the third network device, the third network device completes the forwarding of service data through the protection path, thereby improving the reliability of the ring network.
  • the processor 3410 runs the processing module 3422 and executes:
  • the first customer is, for example, customer 1 in FIG. 17.
  • the working path is usually the preferred transmission path between network devices. After the link fault of the first FlexE link group is eliminated, the first network device can choose to switch the transmission path of the service data to the working path, which can provide optimization for the service data Transmission resources.
  • the processor 3410 may also execute after running the receiving module 3423:
  • the first network device After the first network device completes the path switching, it forwards the second FlexE data through the working path, so that it can provide preferred transmission resources for the second FlexE data.
  • the first FlexE link group may be used to carry at least two customers, and the at least two customers form a customer binding group, and the customer binding group includes the first customer, and at least one customer in the customer binding group deploys OAM It is detected that at least one customer in the customer binding group has not deployed OAM detection; the processor 3410 may execute after running the processing module 3422:
  • a plurality of work clients between the first network device and the third network device may be configured as a work client group, and a plurality of protection clients between the first network device and the third network device may be configured as a protection client group, if the first After a network device sends an OAM message to a third network device through a client in the client group and does not receive a response message, the first network device may determine the FlexE link group corresponding to the client group (for example, the first FlexE Link group) failure, no need to send OAM messages through each working customer or protection customer, thereby reducing the consumption of transmission resources.
  • the client group for example, the first FlexE Link group
  • the first link group is also used to carry seventh and eighth customers
  • the third link group is also used to carry ninth customers
  • the processor 3410 may also execute after running the processing module 3422:
  • the seventh customer is, for example, customer 1 ⁇ shown in FIG. 31
  • the eighth customer is, for example, customer 5 shown in FIG. 31
  • the ninth customer is, for example, customer 3 ⁇ shown in FIG. 31.
  • the solution provided in this embodiment establishes a protection path between the network device and the network device in the first FlexE cross-ring, so that when the transmission path between the first network device and the second network device (for example, the third FlexE Link group) failure, the first network device can establish a FlexE cross between the working client (for example, the seventh client) and the protection client (for example, the eighth client), and pass the service data back to the third network through the protection client
  • the equipment provides a backup transmission channel for service data, thereby improving the reliability of the first FlexE cross-ring.
  • a similar guarantee mechanism can also be established in the second FlexE cross-ring.
  • the processor 3410 may also execute after running the processing module 3422:
  • the path corresponding to the ninth customer is the working path.
  • the working path is usually the preferred transmission path between network devices.
  • the first network device can choose to switch the transmission path of the service data to The working path can provide optimal transmission resources for business data.
  • the third FlexE link group is used to carry at least two customers.
  • the at least two customers form a customer binding group.
  • the customer binding group includes a ninth customer.
  • At least one customer in the customer binding group has deployed OAM detection.
  • a plurality of work clients between the first network device and the second network device can be configured with a work client group, and a plurality of protection clients between the first network device and the second network device can be configured with a protection client group, if the first If a network device does not receive a response message after sending an OAM message to a second network device through a client in the client group, the first network device may determine the FlexE link group corresponding to the client group (for example, the third FlexE Link group) failure, no need to send OAM messages through each working customer or protection customer, thereby reducing the consumption of transmission resources.
  • the FlexE link group for example, the third FlexE Link group
  • the device embodiment and the method embodiment correspond exactly.
  • the steps in the method embodiment are performed by the corresponding modules in the device embodiment.
  • the communication interface performs the receiving step and the sending step in the method embodiment.
  • Other steps than sending and receiving can be performed by The processor executes.
  • the processor executes.
  • the function of the specific module please refer to the corresponding method embodiment, which will not be described in detail.
  • the size of the sequence number of each process does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application.

Landscapes

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

Abstract

本申请提供了一种在环网中传输数据的方法，该环网包括两个相邻的FlexE交叉环，每个FlexE交叉环包括至少3个节点，该两个FlexE交叉环具有至少一个公共节点，并且，该公共节点承载跨环的端到端工作路径，该两个FlexE交叉环各自包括一个环状保护路径。由于两个FlexE交叉环中任意两个相邻的节点之间都具有保护路径，因此，若公共节点的链路出现故障，则与公共节点相邻的节点可以利用环状保护路径将数据从一个FlexE交叉环传输至另一个FlexE交叉环，从而提高了包括至少两个FlexE交叉环的环网的可靠性。

Description

通信方法和装置
本申请要求于2018年12月10日提交中国国家知识产权局、申请号为201811505586.1、申请名称为“通信方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种应用于灵活以太交叉环的环网保护方法和装置。
背景技术
灵活以太网(flexible ethernet，FlexE)是在传统以太网基础上发展出来的一种新型以太网。在FlexE中，数据通过FlexE隧道进行传输。为了提高FlexE的可靠性，一种可用的方法是建立端到端(end to end，E2E)的保护路径，即，建立一条备用的FlexE隧道，当工作路径(即，正在使用的FlexE隧道)出现故障时，E2E传输路径的一端可以通过保护路径传输数据，上述E2E传输路径的一端例如是服务提供商边缘设备(provider edge，PE)。然而，若上述保护路径也出现故障，则FlexE将无法传输数据，从而导致FlexE的可靠性下降。
对于应用FlexE技术的环网，如何提供一种更有可靠有效的环网保护方法，成为目前需要解决的技术问题。
发明内容
本申请提供了一种应用于灵活以太交叉环的通信方法和通信装置，通过配置相邻两个网络设备之间的保护路径，能够增强FlexE的可靠性。
第一方面，本申请提供了一种通信方法，应用于环网，该环网包括第一FlexE交叉环和第二FlexE交叉环，第一FlexE交叉环包括第一网络设备、第二网络设备和第三网络设备，第二FlexE交叉环包括第四网络设备、第一网络设备和第二网络设备，第一网络设备与第二网络设备相邻，第一网络设备与第三网络设备相邻，第一网络设备与第四网络设备相邻；第一网络设备和第二网络设备为第一FlexE交叉环和第二FlexE交叉环的相交节点；第一网络设备与第三网络设备之间具有第一FlexE链路组，第一网络设备与第四网络设备之间具有第二FlexE链路组，第一网络设备与第二网络设备之间具有第三FlexE链路组，第一FlexE链路组用于承载第一客户和第五客户，第二FlexE链路组用于承载第二客户和第六客户，第三FlexE链路组用于承载第三客户和第四客户，第三客户用于在第一FlexE交叉环传输数据，第四客户用于在第二FlexE交叉环传输数据；所述方法包括：第一网络设备确定第一FlexE链路组发生故障；第一网络设备删除第三客户与第五客户之间的FlexE交叉；第一网络设备建立第三客户与第二客户或第四客户之间的FlexE交叉。
第一FlexE链路组可以是一个链路组，也可以是多个链路组。当第一FlexE链路组是一个链路组时，第一客户与第五客户承载于同一个链路组上；当第一FlexE链路组是多个 链路组时，第一客户与第五客户可以承载于相同或者不同的链路组上。第二FlexE链路组和第三FlexE链路组也具有与第一FlexE链路组相同的特征。
由于两个相邻的FlexE交叉环中各自存在一条环状保护路径，因此，当工作路径出现故障后，承载工作路径的公共节点(例如，第一网络设备)可以利用两个FlexE交叉环的保护路径转发业务数据。对于现有技术中的FlexE交叉环来说，发送节点和接收节点之间仅存在工作路径和E2E保护路径，通常情况下，承载工作路径的节点不承载E2E保护路径，若公共节点承载的工作路径出现故障，工作节点无法通过保护路径转发业务数据，因此，本申请提供的FlexE交叉环和基于该FlexE交叉环的自动保护倒换方法提高了环网的可靠性。
一种可能的设计中，第一网络设备建立第三客户与第二客户或第四客户之间的FlexE交叉之后，所述方法还包括：第一网络设备通过第三客户接收第三网络设备发送的第一FlexE数据；第一网络设备通过第二客户或第四客户转发第一FlexE数据。
FlexE数据即符合FlexE协议的码块，第一网络设备通过保护客户将业务数据(例如，第一FlexE数据)回传给第三网络设备，第三网络设备通过保护路径完成业务数据的转发，从而提高了环网的可靠性。
一种可能的设计中，第一FlexE链路组的链路故障排除后，所述方法还包括：第一网络设备删除第三客户与第二客户或第四客户之间的FlexE交叉；第一网络设备建立第一客户与第二客户或第四客户之间的FlexE交叉。
工作路径通常是网络设备之间优选的传输路径，第一FlexE链路组的链路故障排除后，第一网络设备可以选择将业务数据的传输路径切换至工作路径，从而能够为业务数据提供优选的传输资源。
一种可能的设计中，第一网络设备建立第一客户与第二客户或第四客户之间的FlexE交叉之后，所述方法还包括：第一网络设备通过第一客户接收第三网络设备发送的第二FlexE数据；第一网络设备通过第二客户或第四客户转发第二FlexE数据。
第一网络设备完成路径切换后，通过工作路径转发第二FlexE数据，从而能够为第二FlexE数据提供优选的传输资源。
一种可能的设计中，第一FlexE链路组用于承载至少两个客户，该至少两个客户构成一个客户绑定组，该客户绑定组包括第一客户，该客户绑定组中的至少一个客户部署了操作、管理和维护OAM检测，该客户绑定组中的至少一个客户没有部署OAM检测；第一网络设备确定第一FlexE链路组发生故障包括：第一网络设备基于该客户绑定组中的至少一个客户部署的OAM检测，确定第一FlexE链路组发生故障。
第一网络设备与第三网络设备之间的多个工作客户可以被配置一个工作客户组，第一网络设备与第三网络设备之间的多个保护客户可以被配置一个保护客户组，若第一网络设备通过上述客户组中的一个客户向第三网络设备发送OAM报文后未收到响应报文，则第一网络设备可以确定上述客户组对应的FlexE链路组(例如，第一FlexE链路组)出现故障，无需通过每个工作客户或保护客户发送OAM报文，从而减少了传输资源的消耗。
一种可能的设计中，第一链路组还用于承载第七客户和第八客户，第三链路组还用于承载第九客户，所述方法还包括：第一网络设备确定第三FlexE链路组发生故障；第一网络设备删除第七客户与第九客户之间的FlexE交叉；第一网络设备建立第七客户与第八客 户之间的FlexE交叉。
本实施例所提供的方案在第一FlexE交叉环中建立了网络设备到网络设备之间的保护路径，这样，当第一网络设备与第二网络设备之间的传输路径(例如，第三FlexE链路组)出现故障，第一网络设备可以建立工作客户(例如，第七客户)与保护客户(例如，第八客户)之间的FlexE交叉，通过保护客户将业务数据回传至第三网络设备，为业务数据提供了备用的传输通道，从而提高了第一FlexE交叉环的可靠性。第二FlexE交叉环中也可以建立类似的保障机制。
一种可能的设计中，第三FlexE链路组的链路故障排除后，所述方法还包括：第一网络设备删除第七客户与第八客户之间的FlexE交叉；第一网络设备建立第七客户与第九客户之间的FlexE交叉。
第九客户对应的路径为工作路径，工作路径通常是网络设备之间优选的传输路径，第三FlexE链路组的链路故障排除后，第一网络设备可以选择将业务数据的传输路径切换至工作路径，从而能够为业务数据提供优选的传输资源。
一种可能的设计中，第三FlexE链路组用于承载至少两个客户，该至少两个客户构成一个客户绑定组，该客户绑定组包括第九客户，该客户绑定组中至少一个客户部署了OAM检测，该客户绑定组中至少一个客户没有部署OAM检测；第一网络设备确定第三FlexE链路组发生故障包括：第一网络设备基于所述客户绑定组中至少一个客户部署的OAM检测，确定第三FlexE链路组发生故障。
第一网络设备与第二网络设备之间的多个工作客户可以被配置一个工作客户组，第一网络设备与第二网络设备之间的多个保护客户可以被配置一个保护客户组，若第一网络设备通过上述客户组中的一个客户向第二网络设备发送OAM报文后未收到响应报文，则第一网络设备可以确定上述客户组对应的FlexE链路组(例如，第三FlexE链路组)出现故障，无需通过每个工作客户或保护客户发送OAM报文，从而减少了传输资源的消耗。
第二方面，本申请提供了另一种通信方法，应用于环网，该环网包括第一FlexE交叉环和第二FlexE交叉环，第一FlexE交叉环包括第一网络设备、第二网络设备和第三网络设备，第二FlexE交叉环包括第四网络设备、第一网络设备和第二网络设备，第一网络设备与第二网络设备相邻，第一网络设备与第三网络设备相邻，第一网络设备与第四网络设备相邻；第一网络设备和第二网络设备为第一FlexE交叉环和第二FlexE交叉环的相交节点；第一网络设备与第三网络设备之间具有第一FlexE链路组，第一网络设备与第二网络设备之间具有第二FlexE链路组，第一网络设备与第二网络设备之间具有第三FlexE链路组，第一FlexE链路组用于承载第一客户和第五客户，第二FlexE链路组用于承载第二客户和第六客户，第三FlexE链路组用于承载第三客户和第四客户，第三客户用于在第一FlexE交叉环内传输数据，第四客户用于在第二FlexE交叉环内传输数据，第二网络设备还承载第七客户和第八客户，第七客户用于在第一FlexE交叉环内传输数据，第八客户用于在第二FlexE交叉环传输数据；所述方法包括：第二网络设备确定第一网络设备发生故障；第二网络设备删除第三客户与第七客户之间的FlexE交叉；第二网络设备删除第四客户与第八客户之间的FlexE交叉；第二网络设备建立第七客户与第八客户之间的FlexE交叉。
上述第五客户、第三客户以及第七客户为第一FlexE交叉环的环状保护路径中的客户， 上述第四客户、第六客户以及第八客户为第二FlexE交叉环的环状保护路径中的客户，第一网络设备承载了第一FlexE交叉环与第二FlexE交叉环之间的工作路径。当第一FlexE交叉环与第二FlexE交叉环的公共节点(例如，第一网络设备)出现故障时，第一FlexE交叉环与第二FlexE交叉环需要确定另外一个公共节点(例如，第二网络设备)，并通过该另外一个公共节点建立两个FlexE交叉环的保护路径之间的关联，以便于通过两个FlexE交叉环的保护路径转发数据。
由于两个相邻的FlexE交叉环中各自存在一条环状保护路径，因此，当第一网络设备出现故障后，第一FlexE交叉环中与第一网络设备相邻的承载工作路径的网络设备可以利用环状保护路径转发业务数据。对于现有技术中的FlexE交叉环来说，发送节点和接收节点之间仅存在工作路径和E2E保护路径，通常情况下，承载工作路径的网络设备不承载E2E保护路径，若第一网络设备出现故障，第一FlexE交叉环中与第一网络设备相邻的承载工作路径的网络设备无法通过保护路径转发业务数据，因此，本申请提供的FlexE交叉环和基于该FlexE交叉环的自动保护倒换方法提高了环网的可靠性。
一种可能的设计中，第一网络设备建立第三客户与第二客户或第四客户之间的FlexE交叉之后，所述方法还包括：第一网络设备通过第七客户接收第一FlexE数据；第一网络设备通过第八客户转发第一FlexE数据。
FlexE数据即符合FlexE协议的码块，第一网络设备通过两个FlexE交叉环的保护客户实现两个FlexE交叉环之间的数据转发，从而提高了环网的可靠性。
一种可能的设计中，第一网络设备的故障排除后，所述方法还包括：第二网络设备删除第七客户与第八客户之间的FlexE交叉；第二网络设备建立第七客户与第三客户之间的FlexE交叉；第二网络设备建立第八客户与第四客户之间的FlexE交叉。
第一网络设备的故障排除后，第一网络设备即可通过工作路径转发两个FlexE交叉环之间的数据，第二网络设备恢复两个FlexE交叉环各自的环状保护路径，继续为环网的可靠性提供保障。
第三方面，本申请还提供了一种通信方法，应用于环网，该环网包括第一FlexE交叉环和第二FlexE交叉环，第一FlexE交叉环包括第一网络设备、第二网络设备和第三网络设备，第二FlexE交叉环包括第四网络设备、第五网络设备和第一网络设备，第一网络设备与第二网络设备相邻，第一网络设备与第三网络设备相邻，第一网络设备与第四网络设备相邻，第一网络设备与第五网络设备相邻；第一网络设备为第一FlexE交叉环和第二FlexE交叉环的相交节点；第一网络设备与第三网络设备之间具有第一FlexE链路组，第一网络设备与第四网络设备之间具有第二FlexE链路组，第一网络设备与第二网络设备和第五网络设备之间具有第三FlexE链路组，第一FlexE链路组用于承载第一客户和第五客户，第二FlexE链路组用于承载第二客户和第六客户，第三FlexE链路组用于承载第三客户和第四客户，第三客户用于在第一FlexE交叉环传输数据，第四客户用于在第二FlexE交叉环传输数据；所述方法包括：第一网络设备确定第一FlexE链路组发生故障；第一网络设备删除第三客户与第五客户之间的FlexE交叉；第一网络设备建立第三客户与第二客户或第四客户之间的FlexE交叉。
第一FlexE链路组可以是一个链路组，也可以是多个链路组。例如，当第一FlexE链路组是一个链路组时，第一客户与第五客户承载于同一个链路组上；当第一FlexE链路组 是多个链路组时，第一客户与第五客户可以承载于相同或者不同的链路组上。同理，第二FlexE链路组可以是一个链路组，也可以是多个链路组。第三FlexE链路组可以是一个链路组，也可以是多个链路组。
由于两个相邻的FlexE交叉环中各自存在一条环状保护路径，因此，当工作路径出现故障后，承载工作路径的公共节点(例如，第一网络设备)可以利用两个FlexE交叉环的保护路径转发业务数据。对于现有技术中的FlexE交叉环来说，发送节点和接收节点之间仅存在工作路径和E2E保护路径，通常情况下，承载工作路径的节点不承载E2E保护路径，若公共节点承载的工作路径出现故障，工作节点无法通过保护路径转发业务数据，因此，本申请提供的FlexE交叉环和基于该FlexE交叉环的自动保护倒换方法提高了环网的可靠性。
一种可能的设计中，第一网络设备建立第三客户与第二客户或第四客户之间的FlexE交叉之后，所述方法还包括：第一网络设备通过第三客户接收第三网络设备发送的第一FlexE数据；第一网络设备通过第二客户或第四客户转发第一FlexE数据。
FlexE数据即符合FlexE协议的码块，第一网络设备通过保护客户将业务数据(例如，第一FlexE数据)回传给第三网络设备，第三网络设备通过保护路径完成业务数据的转发，从而提高了环网的可靠性。
一种可能的设计中，第一FlexE链路组的链路故障排除后，所述方法还包括：第一网络设备删除第三客户与第二客户或第四客户之间的FlexE交叉；第一网络设备建立第一客户与第二客户或第四客户之间的FlexE交叉。
工作路径通常是网络设备之间优选的传输路径，第一FlexE链路组的链路故障排除后，第一网络设备可以选择将业务数据的传输路径切换至工作路径，从而能够为业务数据提供优选的传输资源。
一种可能的设计中，第一网络设备建立第一客户与第二客户或第四客户之间的FlexE交叉之后，所述方法还包括：第一网络设备通过第一客户接收第三网络设备发送的第二FlexE数据；第一网络设备通过第二客户或第四客户转发第二FlexE数据。
第一网络设备完成路径切换后，通过工作路径转发第二FlexE数据，从而能够为第二FlexE数据提供优选的传输资源。
一种可能的设计中，第一FlexE链路组用于承载至少两个客户，该至少两个客户构成一个客户绑定组，该客户绑定组包括第一客户，该客户绑定组中的至少一个客户部署了操作、管理和维护OAM检测，该客户绑定组中的至少一个客户没有部署OAM检测；第一网络设备确定第一FlexE链路组发生故障包括：第一网络设备基于该客户绑定组中的至少一个客户部署的OAM检测，确定第一FlexE链路组发生故障。
第一网络设备与第三网络设备之间的多个工作客户可以被配置一个工作客户组，第一网络设备与第三网络设备之间的多个保护客户可以被配置一个保护客户组，若第一网络设备通过上述客户组中的一个客户向第三网络设备发送OAM报文后未收到响应报文，则第一网络设备可以确定上述客户组对应的FlexE链路组(例如，第一FlexE链路组)出现故障，无需通过每个工作客户或保护客户发送OAM报文，从而减少了传输资源的消耗。
一种可能的设计中，第一链路组还用于承载第七客户和第八客户，第三链路组还用于承载第九客户，所述方法还包括：第一网络设备确定第三FlexE链路组发生故障；第一网 络设备删除第七客户与第九客户之间的FlexE交叉；第一网络设备建立第七客户与第八客户之间的FlexE交叉。
本实施例所提供的方案在第一FlexE交叉环中建立了网络设备到网络设备之间的保护路径，这样，当第一网络设备与第二网络设备之间的传输路径(例如，第三FlexE链路组)出现故障，第一网络设备可以建立工作客户(例如，第七客户)与保护客户(例如，第八客户)之间的FlexE交叉，通过保护客户将业务数据回传至第三网络设备，为业务数据提供了备用的传输通道，从而提高了第一FlexE交叉环的可靠性。第二FlexE交叉环中也可以建立类似的保障机制。
一种可能的设计中，第三FlexE链路组的链路故障排除后，所述方法还包括：第一网络设备删除第七客户与第八客户之间的FlexE交叉；第一网络设备建立第七客户与第九客户之间的FlexE交叉。
第九客户对应的路径为工作路径，工作路径通常是网络设备之间优选的传输路径，第三FlexE链路组的链路故障排除后，第一网络设备可以选择将业务数据的传输路径切换至工作路径，从而能够为业务数据提供优选的传输资源。
一种可能的设计中，第三FlexE链路组用于承载至少两个客户，该至少两个客户构成一个客户绑定组，该客户绑定组包括第九客户，该客户绑定组中至少一个客户部署了OAM检测，该客户绑定组中至少一个客户没有部署OAM检测；第一网络设备确定第三FlexE链路组发生故障包括：第一网络设备基于所述客户绑定组中至少一个客户部署的OAM检测，确定第三FlexE链路组发生故障。
第一网络设备与第二网络设备之间的多个工作客户可以被配置一个工作客户组，第一网络设备与第二网络设备之间的多个保护客户可以被配置一个保护客户组，若第一网络设备通过上述客户组中的一个客户向第二网络设备发送OAM报文后未收到响应报文，则第一网络设备可以确定上述客户组对应的FlexE链路组(例如，第三FlexE链路组)出现故障，无需通过每个工作客户或保护客户发送OAM报文，从而减少了传输资源的消耗。
第四方面，本申请提供了一种通信装置，包括存储器，该存储器包括计算机可读指令；该装置还包括与该存储器相连的处理器，所述处理器用于执行所述计算机可读指令，以执行第一方面或第一方面任意一种可能的设计中的操作，或者，以执行第二方面或第二方面任意一种可能的设计中的操作，或者，以执行第三方面或第三方面任意一种可能的设计中的操作。
第五方面，本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储了计算机程序代码，该计算机程序代码被处理单元或处理器执行时，使得通信装置执行第一方面以及第一方面任意一种可能的设计中的操作，或者，使得通信装置执行第二方面以及第二方面任意一种可能的设计中的操作，或者，使得通信装置执行第三方面以及第三方面任意一种可能的设计中的操作。
第六方面，本申请还提供了一种芯片，其中存储有指令，当其在通信装置或网络设备上运行时，使得该芯片执行上述第一方面以及第一方面任意一种可能的设计中的操作，或者，使得该芯片执行上述第二方面以及第二方面任意一种可能的设计中的操作，或者，使得该芯片执行上述第三方面以及第三方面任意一种可能的设计中的操作。
第七方面，本申请还提供了一种计算机程序产品，该计算机程序产品包括：计算机程 序代码，当该计算机程序代码被通信装置的处理器运行时，使得通信装置执行上述第一方面以及第一方面任意一种可能的设计中的操作，或者，使得通信装置执行上述第二方面以及第二方面任意一种可能的设计中的操作，或者，使得通信装置执行上述第三方面以及第三方面任意一种可能的设计中的操作。
第八方面，本申请还提供了一种网络设备，用于执行上述第一方面以及第一方面的任意一种可能的设计中的操作，或者，用于执行上述第二方面以及第二方面的任意一种可能的设计中的操作，或者，用于执行上述第三方面以及第三方面的任意一种可能的设计中的操作。
第九方面，本申请还提供了一种网络设备，包括第四方面所述的通信装置。
附图说明
图1是一种适用于本申请的FlexE传输方式的示意图；
图2是一种适用于本申请FlexE的部分架构示意图；
图3示出了适用于本申请的FlexE交叉传输技术的示意图；
图4是本申请提供的第一种FlexE交叉环的示意图；
图5是本申请提供的第一种FlexE交叉环的在正常状态下的数据转发方法的示意图；
图6是本申请提供的一种通信方法的示意图；
图7是本申请提供的第一种FlexE交叉环在第一种故障状态下的数据转发方法的示意图；
图8是本申请提供的第一种FlexE交叉环在第二种故障状态下的数据转发方法的示意图；
图9是本申请提供的第一种FlexE交叉环在第三种故障状态下的数据转发方法的示意图；
图10是本申请提供的第二种FlexE交叉环在正常状态下的数据转发方法的示意图；
图11是本申请提供的第二种FlexE交叉环在第一种故障状态下的数据转发方法的示意图；
图12是本申请提供的第二种FlexE交叉环在第二种故障状态下的数据转发方法的示意图；
图13是本申请提供的第二种FlexE交叉环在第三种故障状态下的数据转发方法的示意图；
图14是本申请提供的另一种通信方法的示意图；
图15是本申请提供的第一种FlexE交叉环在第四种故障状态下的数据转发方法的示意图；
图16是本申请提供的第二种FlexE交叉环在第四种故障状态下的数据转发方法的示意图；
图17示出了本申请提供的第三种FlexE交叉环的示意图；
图18是本申请提供的第三种FlexE交叉环在第一种故障状态下的数据转发方法的示意图；
图19是本申请提供的第三种FlexE交叉环在第二种故障状态下的数据转发方法的示意 图；
图20是本申请提供的第三种FlexE交叉环在第三种故障状态下的数据转发方法的示意图；
图21是本申请提供的一种配置了客户组的节点的示意图；
图22是本申请提供的另一种配置了客户组的节点的示意图；
图23是本申请提供的再一种配置了客户组的节点的示意图；
图24是本申请提供的再一种配置了客户组的节点的示意图；
图25是本申请提供的第四种FlexE交叉环的示意图；
图26是本申请提供的第四种FlexE交叉环在第一种故障状态下的数据转发方法的示意图；
图27是本申请提供的第四种FlexE交叉环在第二种故障状态下的数据转发方法的示意图；
图28是本申请提供的第四种FlexE交叉环在第三种故障状态下的数据转发方法的示意图；
图29是本申请提供的第四种FlexE交叉环在第四种故障状态下的数据转发方法的示意图；
图30是本申请提供的一种OAM报文格式的示意图；
图31是本申请提供的第五种FlexE交叉环的示意图；
图32是本申请提供的一种通信装置的示意图；
图33是本申请提供的另一种通信装置的示意图；
图34是本申请提供的再一种通信装置的示意图。
具体实施方式
在没有特别说明的情况下，本申请中提及“1”、“2”、“3”、“4”、“5”、“6”、“7”、“8”、“第一”、“第二”等序数词用于对多个对象进行区分，不用于限定多个对象的顺序。例如，客户1、客户2、客户3、客户4、客户5、客户6、客户7和客户8表示八个不同的客户，除此之外并无其它限定；节点1、节点2、节点3和节点4表示四个不同的节点，除此之外并无其它限定；链路组1、链路组2和链路组3表示三个不同的链路组，除此之外并无其它限定；第一FlexE交叉环与第二FlexE交叉环表示两个不同的FlexE交叉环，除此之外并无其它限定。
本申请中涉及到的节点，也可以称之为网络设备，网元。节点可以是路由器、分组传送网设备、交换机、防火墙等等。为方便描述，本申请中，上面提到的设备统称为节点。
下面将结合附图，对本申请中的技术方案进行描述。
图1是一种适用于本申请的FlexE传输方式的示意图。
如图1所示，FlexE在传统以太网的基础上，引入了FlexE链路组(FlexE Group)、客户(client)、灵活以太网时分复用层(FlexE shim，下文简称为“时分复用层”)等概念，为了便于理解本申请的技术方案，首先对本申请涉及的概念做简要介绍。
FlexE链路组：也可称为捆绑组，FlexE链路组可以被解释为由多个物理层(physical，PHY)组成功能模块。本申请所述的FlexE链路组包括至少一条链路。例如，可以由1～254 个支持100吉比特以太网(gigabit ethernet，GE)速率的PHY组成。其中，PHY可以定义为：为传输数据所需要的物理链路建立、维持、拆除而提供具有机械的、电子的、功能的和规范的特性。PHY也可以定义为具有上述特性的模块，例如，PHY可以是收发两端的物理层工作器件以及位于收发两端之间的光纤，物理层工作器件例如是物理层接口设备。
每个FlexE链路组包括的多个PHY(即，链路)具有逻辑上的捆绑关系。所谓的逻辑上捆绑关系，指的是不同的PHY之间可以不存在物理连接关系，因此，FlexE链路组中的多个PHY在物理上可以是独立的。FlexE中的网络设备可以通过PHY的编号来标识一个FlexE链路组中包含哪些链路，来实现多个PHY的逻辑捆绑。例如，每个PHY的编号可用1～254之间的一个数字来标识，0和255为保留数字。一个PHY的编号可对应网络设备上的一个端口。相邻的两个网络设备之间需采用相同的编号来标识同一个PHY。一个FlexE链路组中包括的各个PHY的编号不必是连续的。通常情况下，两个网络设备之间具有一个FlexE链路组，但本申请并不限定两个网络设备之间仅存在一个FlexE链路组，即两个网络设备之间也可以具有多个FlexE链路组。一个PHY可用于承载至少一个客户，一个客户可在至少一个PHY上传输。
客户：也可以称之为客户业务，客户可以被解释为基于一个物理地址的以太网流。通过同一捆绑组发送的客户需要共用同一时钟，且这些客户需要按照分配的时隙速率进行适配，每个客户的带宽开销可以通过插入/删除空闲块(idle)进行适配。客户的标识称为Client ID，也可称之为客户标识。
时分复用层：时分复用层的主要作用是根据相同的时钟对数据进行切片，并将切片后的数据封装至预先划分的时隙(slot)中，然后根据预先配置的时隙配置表，将划分好的各时隙映射至捆绑组中的PHY上进行传输，其中，每个时隙映射于捆绑组中的一个PHY。
FlexE基于时分复用(time division multiplexing，TDM)技术传输数据，以太报文在物理子编码层被编码成为64B/66B(“B”是“比特”的简称)大小的码块，并基于时隙将这些码块映射到多个不同的PHY上。
本申请所述的FlexE数据，也可以称之为码块。如上所述，以太报文在物理子编码层被编码成为64B/66B(“B”是“比特”的简称)大小的码块，并基于时隙将这些码块映射到多个不同的PHY上。
图2示出了适用于本申请的一种FlexE的部分架构示意图。
如图2所示，FlexE的部分架构包括介质接入控制(medium access control，MAC)子层、时分复用层和物理层，其中，MAC子层属于数据链路层的一个子层，上接逻辑链路控制子层。物理层又可分为物理编码子层(physical coding sublayer，PCS)、物理介质接入(physical medium attachment，PMA)子层和物理介质关联(physical medium dependent，PMD)子层。MAC子层与时分复用层之间以及时分复用层与物理层之间分别通过介质无关接口(medium independent interface，MII)连接，物理层下接传输介质，物理层与传输介质之间通过介质相关接口(medium dependent interface，MDI)连接。上述各个层和接口的功能均由相应的芯片或模块实现，例如，PCS、PMA子层和PMD子层对应的功能可以分别由不同的PHY实现。
在发送信号的过程中，PCS用于对数据进行编码、扰码(scrambled)、插入开销头(overhead，OH)以及插入对齐标签(alignment marker，AM)等操作；在接收信号的过 程中，PCS则会进行上述步骤的逆处理过程。发送和接收信号可以由PCS的不同功能模块实现。
PMA子层的主要功能是链路监测、载波监测、编译码、发送时钟合成以及接收时钟恢复。PMD子层的主要功能是数据流的加扰/解扰、编译码以及对接收信号进行直流恢复和自适应均衡。
应理解，上述架构仅是举例说明，适用于本申请的FlexE的架构不限于此，例如，在MAC子层和时分复用层之间还可以存在一个适配子层(reconciliation sublayer，RS)，用于提供MII与MAC子层之间的信号映射机制；PCS与PMA子层之间还可以存在一个前向纠错(forward error correction，FEC)子层，用于增强发送的数据的可靠性。
基于上述架构，图3示出了适用于本申请的FlexE交叉(cross)传输技术的示意图。
服务提供商边缘(provider edge，PE)设备PE1通过用户网络接口(user network interface，UNI)接收用户发送的以太报文，对该以太报文进行发送处理，例如，在物理编码子层将该以太报文编码成为64B/66B大小的数据块，并基于时隙将这些数据块映射到PHY上。映射处理后的数据块经过物理层的处理后，生成开销帧(overhead frame)或者开销复帧，开销帧或者开销复帧通过传输介质(例如，光纤)传输至服务提供商(provider，P)设备。
P设备获取包含上述数据块的开销帧或者开销复帧后，在P设备的时分复用层基于FlexE交叉配置从唯一的输出路径发出。因此，FlexE交叉也可以被解释为建立输入路径和输出路径之间的连接关系。
PE2接收到上述开销帧或者开销复帧后，对开销帧或者开销复帧进行解码处理，获取PE1发送的以太报文，并通过PE2的UNI将该以太报文发送出去。
由于FlexE中的数据传输是在物理层进行转发处理，无需在MAC子层对数据进行解封装处理，因此，相比于多协议标签交换转发(multi-protocol label switching，MPLS)方式提高了转发效率。
需要说明的是，P设备和PE设备的名称不同的原因是其所处的位置不同，当P设备获取通过UNI获取待传输的以太报文时，P设备即转变为PE设备。相应地，当PE设备作为执行FlexE交叉处理的节点时，PE设备即转变为P设备。
为了提高FlexE的传输可靠性，本申请提供了一种通信方法，该方法应用于至少3个节点组成的FlexE交叉环。
图4示出了本申请提供的一种FlexE环网(即，应用FlexE交叉技术的环形以太网)的示意图。其中，节点1与节点3之间的FlexE链路组可以称为链路组1，节点1与节点4之间的FlexE链路组可以称为链路组2，节点1与节点2之间的FlexE链路组可以称为链路组3。每个链路组承载有至少一个工作路径和/或至少一个保护路径。
本申请中所述的工作路径，也可被称为工作通道，是指系统配置的用于业务数据传输的路径。当FlexE链路组仅承载工作路径时，该FlexE链路组可被称为工作FlexE链路组。本申请所述的保护路径，也可被称为保护通道，是指系统配置的工作路径的备份路径，即，当工作路径无法进行业务数据的传输时，代替工作路径进行业务数据传输的路径。当FlexE链路组仅承载保护路径时，该FlexE链路组可被称为保护FlexE链路组。
图4所示的FlexE环网由两个FlexE交叉环组成，每个FlexE交叉环包括3个节点，其中，节点1和节点2为该两个FlexE交叉环共用的节点，节点3所在的FlexE交叉环为 环1，节点4所在的FlexE交叉环为环2。在没有业务数据上环的情况下，各个节点例如是图3所示的P设备。各个节点之间存在用于传输数据的工作路径和/或保护路径。工作路径和保护路径是基于物理链路(例如，光纤)的数据通道，并且，工作路径和保护路径均为双向路径，例如，数据可以通过工作路径从节点3传输至节点1，数据也可以通过该工作路径从节点1传输至节点3。不同的路径对应不同的客户，因此，可以使用客户的标识来描述工作路径或者保护路径。工作路径对应的客户可以称为工作客户，例如，客户1和客户2；保护路径对应的客户可以称为保护客户，例如，客户3、客户4、客户5、客户6、客户7和客户8。
上述工作路径和保护路径为预先配置的路径，当发送端(例如，节点3)和接收端(例如节点4)位于不同的FlexE交叉环时，需要配置发送端到接收端之间的E2E工作路径，即，客户1和客户2对应的工作路径，还需要配置每个FlexE交叉环内的保护路径，即，客户3、客户5和客户7对应的保护路径，以及，客户4、客户6和客户8对应的保护路径。
节点通过客户传输数据时需要一些时隙，这些时隙被分配在FlexE链路组中至少一个PHY上。FlexE交叉即时隙交叉，例如，在客户1对应的PHY中存在分配给客户1的n个时隙；在客户2对应的PHY中存在分配给客户2的m个时隙。节点1通过客户1占用的n个时隙从客户1对应的PHY接收数据，在向节点4转发该数据时，节点1根据客户1与客户2之间建立的FlexE交叉，通过客户2占用的m个时隙以及客户2对应的PHY向节点4转发该数据。
在缺省状态下，保护路径处于闭环状态，两个保护路径对应的客户之间存在FlexE交叉，例如，客户5与客户3之间存在FlexE交叉，客户5与客户7之间存在FlexE交叉，客户7与客户3之间存在FlexE交叉，如图4中节点1，节点3以及节点2内的虚线所示。工作路径处于开环状态，相邻的两个工作路径对应的客户之间也存在FlexE交叉，例如，客户1与客户2之间存在FlexE交叉，如图4中节点1内的实线所示。
当业务数据通过UNI上环后，PE节点(例如，节点3)可以通过查找该业务数据对应的虚拟局域网(virtual local area network，VLAN)标识，确定相应的FlexE接口(即，客户1)进行转发。
图5示出了本申请提供的一种业务数据上环和下环方法的示意图。
节点3通过UNI获取业务数据后，进行上环处理，即，查找该业务数据对应的客户。例如，业务数据的目的地址是节点4，则节点3可以选择“节点3→节点1→节点4”的传输路径，并通过客户1将业务数据发送至节点1，其中节点1作为两个FlexE交叉环的相交节点。
节点1通过客户1接收到该业务数据后，基于客户1与客户2之间的FlexE交叉，通过客户4将该业务数据发送出去。
节点4通过客户2接收到该业务数据后，进行下环处理，即，通过节点3的UNI将该业务数据发送出去。
可以预先配置各个节点的上环客户和下环客户，例如，在上述示例中，可以配置节点3的上环客户和下环客户为：客户1；可以配置节点4的上环客户和下环客户为：客户2。
以节点3为例，节点3通过UNI获取业务数据并且确定传输路径后，可以根据业务数 据对应的VLAN标识从多个客户中选择客户1发送业务数据，即，节点2作为发送端时客户1是上环客户；若节点3作为接收端通过客户1从其它节点接收到业务数据，则节点3可以对该业务数据进行下环处理，通过UNI将该业务数据发送出去，即，节点3作为接收端时客户1是下环客户。
需要说明的是，上述各个节点的上环客户和下环客户均是在节点3作为PE节点时的客户配置情况，若节点3不再作为PE节点，则各个节点的上环客户和下环客户需要重新配置，即，FlexE交叉环中各个节点的上环客户和下环客户的配置情况与PE节点是一一对应的。
上文所描述的转发流程为FlexE交叉环的各条路径均正常工作时的数据转发流程。若节点1与节点3之间的FlexE链路组出现故障，节点1可以执行图6所示的方法完成数据转发。
如图6所示，该方法600包括：
S610，节点1确定链路组1发生故障。
节点1可以根据FlexE的操作管理维护(operation administration and maintenance，OAM)功能确定链路组1出现故障。
例如，节点1通过客户1向节点3发送OAM报文后，在N个周期内未收到该OAM报文的响应消息，则节点1确定链路组1出现故障。其中，该OAM报文用于检测节点之间的路径的连通性。
又例如，节点1在N个周期内未收到节点3发送的OAM报文，则节点1确定链路组1出现故障。
上述节点1确定链路组1出现故障的方法仅是举例说明，本申请对节点1确定链路组1发生故障的具体方式不作限定。
S620，节点1删除客户3与客户5之间的FlexE交叉。
S630，节点1建立客户3与客户2或客户4之间的FlexE交叉。
由于两个相邻的FlexE交叉环中各自存在一条环状保护路径，因此，当工作路径出现故障后，承载工作路径的公共节点(例如，节点1)可以利用两个FlexE交叉环的保护路径转发业务数据。对于现有技术中的FlexE交叉环来说，发送节点和接收节点之间仅存在E2E的工作路径和E2E保护路径，通常情况下，为了防止一条链路组故障导致工作路径和保护路径均出现故障，承载E2E工作路径的节点不承载E2E保护路径，若公共节点承载的工作路径出现故障，承载工作路径的节点无法通过保护路径转发业务数据，因此，本申请提供的FlexE交叉环和基于该FlexE交叉环的自动保护倒换方法提高了FlexE交叉环的可靠性。
图7示出了方法600的一种实施方式，当链路组2发生故障时，节点1可以执行以下步骤以转发数据：
删除客户4与客户6之间的FlexE交叉；
删除客户3与客户5之间的FlexE交叉；
建立客户3与客户4之间的FlexE交叉。
由于链路组2也出现故障，因此，节点1需要通过环2的保护路径转发业务数据，业务数据从节点3上环后，通过客户7传输至节点2，节点2基于客户7与客户3之间的FlexE 交叉通过客户3将业务数据传输至节点1，节点1基于客户3与客户4之间的FlexE交叉将业务数据传输至节点2，节点2基于客户4与客户8之间的FlexE交叉将业务数据传输至节点4，客户8为环2异常情况下的节点4的下环客户，节点4通过客户8接收到业务数据后，通过UNI接口将业务数据转发出去，从而完成了业务数据的转发。
图7仅是举例说明，业务数据也可从节点4上环，经过传输路径“客户8→客户4→客户3→客户7”传输至节点3下环。
若链路组1的故障被排除，链路组2依然存在故障，节点1可以执行下述步骤以发送业务数据：
删除客户3与客户4之间的FlexE交叉；
删除客户1与客户2之间的FlexE交叉；
建立客户1与客户4之间的FlexE交叉。
业务数据经过传输路径“客户1→客户4→客户8”传输至节点4下环，该传输路径如图8所示。
图8仅是举例说明，业务数据也可从节点4上环，经过传输路径“客户8→客户4→客户1”传输至节点3下环。
若链路组1和链路组2的故障均被排除，则节点1可以执行下述步骤以发送业务数据：
建立客户1与客户2之间的FlexE交叉。
业务数据经过传输路径“客户1→客户2”传输至节点4下环，该传输路径即图5所示的传输路径。
工作路径通常是节点之间优选的传输路径，链路组1的链路故障排除后，FlexE交叉环中的节点可以选择优先通过工作路径传输业务数据，从而能够为业务数据提供优选的传输资源。
图9示出了方法600的另一种实施方式，当链路组2未发生故障时，节点1可以执行以下步骤以转发数据：
删除客户1与客户2之间的FlexE交叉；
建立客户3与客户2之间的FlexE交叉。
对于接收端节点(例如，节点4)来说，下环客户为提前配置的客户(例如，客户2)，并且，该下环客户不会因发送端节点所在的FlexE交叉环(例如，环1)出现故障而改变，因此，在环2正常工作的情况下，节点1需要建立客户3与客户2之间的FlexE交叉，以便于节点4通过客户2对业务数据进行下环处理。
业务数据也可以从节点4上环，经过传输路径“客户2→客户3→客户7”传输至节点3下环。
若链路组1的故障均被排除，则节点1可以执行下述步骤以发送业务数据：
删除客户3与客户2之间的FlexE交叉；
建立客户1与客户2之间的FlexE交叉。
业务数据经过传输路径“客户1→客户2”传输至节点4下环，该传输路径即图5所示的传输路径。
工作路径通常是节点之间优选的传输路径，链路组1的链路故障排除后，FlexE交叉环中的节点可以选择优先通过工作路径传输业务数据，从而能够为业务数据提供优选的传 输资源。
图4至图9所描述的方案仅是举例说明，适用于本申请的FlexE交叉环还可以包括更多的节点。
图10是本申请提供的另一种FlexE交叉环的示意图。
网元(network element，NE)1、NE2、NE3、NE4、NE5、NE6、NE7和NE8构成一个FlexE交叉环(即，环1)，其中，NE1作为PE设备与客户设备(customer equipment，CE)1连接。NE5、NE6、NE7、NE9、NE10、NE11、NE12和NE13构成另一个FlexE交叉环(即，环2)，其中，NE10作为PE设备与CE2连接。上述NE也可以被称为节点或网络设备。
在环1和环2的各条路径均处于正常状态时，CE1发出的业务数据通过NE1上环后，可以按照“NE1→NE8→NE7→NE9→NE10”的传输路径传输至NE4下环。
若NE7与NE8之间的FlexE链路组出现故障，则环1和环2的相关节点可以按照下述方法转发业务数据。
NE8确定NE7与NE8之间的FlexE链路组出现故障后，可以删除NE8的两个工作客户之间的FlexE交叉，同时，建立NE8的工作客户与保护客户之间的FlexE交叉，将业务数据通过NE8与NE1之间的保护路径传输至NE1，随后，该业务数据通过环1的保护路径逆时针传输至NE7。
NE7确定NE7与NE8之间的FlexE链路组出现故障后，可以删除NE7的保护客户与NE8的保护客户之间的FlexE交叉，同时，建立环1的保护客户与环2的工作客户之间的FlexE交叉，将业务数据通过环2的工作路径传输至NE9，NE9基于环2的工作路径将该业务数据传输至NE10下环。
业务数据最终按照“NE1→NE2→NE3→NE4→NE5→NE6→NE7→NE9→NE10”的传输路径传输至NE10下环，该传输路径如图11所示。
上述方案仅是举例说明，NE7与NE8之间的FlexE链路组出现故障后，NE1也可以直接通过保护路径向NE2发送业务数据，不再向NE8发送业务数据。
NE7与NE8之间的FlexE链路组的故障被排除后，环1和环2可以按照图10所示的传输路径转发业务数据。
若NE7与NE8之间的FlexE链路组以及NE7与NE9之间的FlexE链路组均出现故障，则环1和环2的相关节点可以按照下述方法转发业务数据。
NE8确定NE7与NE8之间的FlexE链路组出现故障后，可以删除NE8的两个工作客户之间的FlexE交叉，同时，建立NE8的工作客户与保护客户之间的FlexE交叉，将业务数据通过NE8与NE1之间的保护路径传输至NE1，随后，该业务数据通过换1的保护路径逆时针传输至NE7。
NE7确定NE7与NE8之间的FlexE链路组以及NE7与NE9之间的FlexE链路组均出现故障后，可以删除NE7的保护客户与NE8的保护客户之间的FlexE交叉，并且，删除NE7的保护客户与NE9的保护客户之间的FlexE交叉，同时，建立环1的保护客户与环2的保护客户之间的FlexE交叉，将业务数据通过环2的保护路径传输至NE6，NE6基于环2的保护路径将该业务数据逆时针传输至NE10下环。
业务数据最终按照“NE1→NE2→NE3→NE4→NE5→NE6→NE7→NE6→NE5→NE13 →NE12→NE11→NE10”的传输路径传输至NE10下环，该传输路径如图12所示。
上述方案仅是举例说明，NE7与NE8之间的FlexE链路组出现故障后，NE1也可以直接通过保护路径向NE2发送业务数据，不再向NE8发送业务数据。
NE7与NE8之间的FlexE链路组的故障被排除后，环1和环2可以按照图13所示的传输路径转发业务数据。
NE7与NE8之间的FlexE链路组的故障被排除后，并且，NE7与NE9之间的FlexE链路组的故障被排除后，环1和环2可以按照图10所示的传输路径转发业务数据。
应理解，图10至图13所示的FlexE交叉环仅是举例说明，本申请提供的FlexE交叉环的应用场景不限于图10至图13所示的场景。
例如，图10所示的FlexE交叉环还可以应用在第4代(4 th generation，4G)移动通信系统中，其中，CE1可以与4G移动通信系统中的基站(eNB)直接连接或者间接连接。图10所示的FlexE交叉环还可以应用在第5代(5 th generation，5G)移动通信系统中，其中，CE1可以与5G移动通信系统中的基站(gNB)直接连接或间接连接。
再例如，图10所示的FlexE交叉环还可以跨层网络架构中，其中，NE1可以与接入层设备连接，NE10可以与汇聚层设备或者核心层设备连接。
以上示例仅是举例说明，未来的通信系统同样适用于本申请所提供的FlexE交叉环。
上述方案均为承载工作路径的公共节点(例如，图4中的节点1)正常工作时的数据转发方案，如果承载工作路径的公共节点出现故障，则需要仅承载保护路径的公共节点(例如，图4中的节点2)建立两个环之间的FlexE交叉。
图14示出了本申请提供的另一种应用于FlexE交叉环的通信方法。该方法1400可以由图4中的节点2执行。方法1400包括：
S1410，节点2确定节点1发生故障。
S1420，节点2删除客户3与客户7之间的FlexE交叉。
S1430，节点2删除客户4与客户8之间的FlexE交叉。
S1440，节点2建立客户7与客户8之间的FlexE交叉。
与节点1相邻的节点均可以基于OAM功能确定节点1出现故障。节点3确定节点1出现故障后，确定客户7为上环客户，删除客户7与客户5之间的FlexE交叉，通过客户7转发上环的业务数据；节点2确定节点1出现故障后，建立客户3与客户4之间的FlexE交叉，将通过客户7接收的业务数据通过客户8转发出去；节点4确定节点1出现故障后，确定客户8为下环客户，删除客户8与客户6之间的FlexE交叉，对通过客户8接收的业务数据进行下环处理。上述转发流程如图15所示。
由于节点2承载了两个FlexE交叉环的保护路径，因此，当承载工作路径的节点(即，节点1)出现故障时，节点2可以建立两个保护客户之间的FlexE交叉，从而完成跨FlexE交叉环的业务数据转发，增强了多个FlexE交叉环组成的环网的可靠性。
节点3确定节点1的故障排除后，继续通过节点1承载的工作路径发送业务数据，即图5所示的发送路径。
对于图10所示的FlexE交叉环，若NE7出现故障，则NE8和NE6可以基于OAM功能确定NE7出现故障，并对转发路径做相应的处理，如图16所示。
NE8删除两个工作客户(NE1与NE8之间的工作客户，和NE8与NE7之间的工作客 户)之间FlexE交叉，并建立保护工作客户(NE1与NE8之间的工作客户)与保护客户(NE1与NE8之间的保护客户)之间的FlexE交叉，通过环1的保护路径将NE1发送的报文转发至NE6。
NE6删除两个保护客户(NE5与NE6之间的保护客户，和NE6与NE7之间的保护客户)之间的FlexE交叉，并建立环1的保护客户和环2的保护客户之间的FlexE交叉，将业务数据通过换2的保护路径转发至NE10。NE10对业务数据做下环处理，从而在NE7出现故障的情况下完成了跨FlexE交叉环的业务数据转发，增强了多个FlexE交叉环组成的环网的可靠性。
上文描述了两个相邻的FlexE交叉环具有至少两个公共节点的方案。对于图17所示的环网，即两个相邻的FlexE交叉环仅存在一个公共节点的情况，图6所示的方法依然适用。图18至图20示出了链路组1和/或链路组2出现故障后的处理方法，对比图7至图9可知，环1和环2的保护路径是否承载于同一个节点上对于节点1来说处理方法都是一样的。
本申请还提供了一种FlexE交叉环，该FlexE交叉环中每个节点具有多个工作路径和多个保护路径，该多个工作路径与该多个保护路径一一对应。
如图21所示，节点1包括三个物理端口(即，PHY)，分别为东向物理端口、西向物理端口和南向物理端口。图21所示的节点1仅是举例说明，节点1还可以包含更多的物理端口。
东向物理端口对应4个客户，分别为客户2、客户10、客户6和客户16，其中，客户2和客户10为工作客户(即，与工作路径对应的客户)，客户6和客户16为保护客户(即，与保护路径对应的客户)。
西向物理端口对应4个客户，分别为客户1、客户9、客户5和客户11，其中，客户1和客户9为工作客户，客户5和客户11为保护客户。
西向物理端口对应4个客户，分别为客户12、客户3、客户4和客户14，该4个客户均为保护客户。
东向物理端口的2个工作客户被配置为一个客户组(client group)，即，工作客户组1；西向物理端口的2个工作客户被配置为另一个客户组，即，工作客户组2。本申请中，客户组也可以称之为客户绑定组。东向物理端口的2个保护客户被配置为一个客户组，即，保护客户组1，西向物理端口的2个保护客户被配置为另一个客户组，即，保护客户组2。南向物理端口的4个保护客户被配置为两个客户组，即，保护客户组3和保护客户组4。
上述客户组的示例仅是举例说明，本申请提供的客户组中客户的数量还可以是其它数量，例如，3个客户作为一个客户组，或者，更多个客户作为一个客户组。
类似地，也可以对节点2、节点3和节点4配置工作客户组和保护客户组。配置结果如图22至图24所示。
包含图21至图24所示的4个节点的FlexE交叉环如图25所示。
若链路组1和链路组2出现故障，则节点1可以将删除西向物理端口与东向物理端口的工作客户组之间的FlexE交叉，并建立南向物理端口的两个保护客户组之间的FlexE交叉，将业务数据从南向物理端口的保护客户组发送出去。上述传输路径如图26所示。
若链路组2出现故障，则节点1可以将删除西向物理端口与东向物理端口的工作客户组之间的FlexE交叉，并建立西向物理端口的工作客户组与南向物理端口的保护客户组之 间的FlexE交叉，将业务数据从南向物理端口的保护客户组发送出去。上述传输路径如图27所示。
若链路组1出现故障，则节点1可以将删除西向物理端口与东向物理端口的工作客户组之间的FlexE交叉，并建立南向物理端口的保护客户组与东向物理端口的工作客户组之间的FlexE交叉，将业务数据从东向物理端口的工作客户组发送出去。上述传输路径如图28所示。
若节点1出现故障，则节点2可以将删除西向物理端口与北向物理端口的两个保护客户组之间的FlexE交叉，并且，删除东向物理端口与北向物理端口的两个保护客户组之间的FlexE交叉，并且，建立西向物理端口的保护客户组与东向物理端口的保护客户组之间的FlexE交叉，将业务数据从东向物理端口的保护客户组发送出去。上述传输路径如图29所示。
由于节点基于客户组对多个工作客户和多个保护客户进行一次FlexE交叉处理即可完成路径倒换，无需对各个工作客户和保护客户进行多次FlexE交叉处理，因此，基于客户组的FlexE交叉可以减少路径倒换的开销。
本领域技术人员可以清楚地认识到：图25至图29所示的FlexE交叉环和相应的故障处理方法能够应用于图4，图10或者本申请所描述的其它场景是显而易见的。
本申请还提供了一种检测FlexE交叉环的故障的方法，应用于如图25所示的包括客户组的FlexE交叉环中。该方法包括：
节点1通过工作客户1向节点3发送OAM报文，OAM报文用于检测节点1与节点3之间的FlexE链路组的连通性。
若节点1在N(N为正整数)个周期内未接收到上述OAM报文的响应消息，则节点1确定节点1与节点3之间的FlexE链路组出现故障，无需再通过客户9或者客户5发送OAM报文，从而减小了OAM报文开销。此外，由于无需在一个客户组中每个客户均配置OAM检测，因此，使用客户组的FlexE交叉环能够减小配置OAM的工作量。
上述方案仅是举例说明，节点1也可以根据N个周期内未接收到节点3发送的OAM报文确定西向物理端口的FlexE链路组出现故障。
OAM报文可以采用图30所示的报文格式。
图30中，OAM报文采用66B码块的编码格式，第一行的数字0～65为66个比特的序号，其中，前两个比特为开销比特，从比特2开始，相邻的8个比特划分为一个字节，后面的64个比特共划分为8个字节。
第一个字节(2～9)采用0x4B表示66B码块的控制类型，用于识别O码，即IEEE802.3定义的排序控制符。
第二个字节(10～17)中，前两个比特为预留域(Resv)，后6个比特为类型域(Type)，表示OAM报文类型。
其中，当类型域的值为0x1时，表示该66B码块为BAS码块，BAS码块的一个作用是检测路径的连通性。BAS码块即上文所述的第二OAM报文。
当类型域的值为0x2时，表示该66B码块为APS码块，APS码块的一个作用是检测指示节点进行自动保护倒换，例如，删除两个方向的工作客户之间的FlexE交叉，建立相同方向的工作客户与保护客户之间的FlexE交叉。APS码块即上文所述的OAM报文。
第三个字节(18～25)、第四个字节(26～33)、第六个字节(42～49)和第七个字节(50～57)为值(Value)域，用于承载OAM取值。
第五个字节(34～41)中，前4个比特采用0xC作为OAM信息块的标识。
第八个字节(58～65)中，前4个比特表示序列(Seq)域，其取值可以指示多码块报文中不同的码块顺序所代表的不同含义。在单码块报文中，序列域可以填充为无效值，例如0000。第八个字节的后4个比特为循环冗余校验(cyclic redundancy check，CRC)域，用于校验上述八个字节(除CRC域)的完整性。
图30所示的编码格式仅是举例说明，本申请对OAM报文的编码格式不作限定，例如，还可以采用64B的编码格式对OAM报文进行编码。
上文描述了多环架构的环网(即，包括至少两个FlexE交叉环的环网)以及在该环网中的数据转发方法，需要说明的是，对于上文所述的任意一种环网，其还可以包含单环架构。
图31示出了一种包含单环架构和多环架构的环网。
客户1`、客户7`和客户3`构成了一个闭合的工作路径，客户1、客户7和客户3构成了一个闭合的保护路径，由于节点1、节点2和节点3中任意两个节点之间都具有工作路径和保护路径，因此，无论其中哪两个节点之间的链路出现故障，与故障点相邻的节点均可以通过建立工作客户与保护客户之间的FlexE交叉转发数据，即，通过保护路径转发数据。
例如，若节点1确定链路组3发生故障，则节点1可以删除客户1`与客户3`之间的FlexE交叉，并建立客户1`与客户5之间的FlexE交叉，从而可以将通过客户1`接收到的数据通过客户5回传至节点3，节点3可以通过客户7将该数据发送至节点2，从而完成了单环架构中的数据转发。
本实施例所提供的方案在环1中建立了节点与节点之间的保护路径，这样，当节点1与节点2之间的传输路径(例如，链路组3)出现故障时，节点1可以建立工作客户(例如，客户1`)与保护客户(例如，客户5)之间的FlexE交叉，通过保护客户将业务数据回传至节点3，为业务数据提供了备用的传输通道，从而提高了FlexE交叉环的可靠性。环2中也可以建立类似的保障机制。
图31示出了单环架构与多环架构共用相同的保护路径(客户1、客户7和客户3构成的保护路径)的示例，可以理解的是，单环架构与多环架构也可以不共用相同的保护路径，即，新建一个环状保护路径，为客户1`、客户7`和客户3`构成的工作路径提供传输保护。
上文详细介绍了本申请提供的通信方法的示例。可以理解的是，通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请可以根据上述方法示例对传输数据的装置进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要 说明的是，本申请中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图32示出了本申请提供的一种通信装置的示意图。
该通信装置3200可以应用于图4、图10或图25所示的网络架构中，例如可以应用于图4所示的网络架构中的节点1，或图10所示网络架构的NE7，或图25所示的网络架构中的节点1。通信装置3200可以包括处理器3210，与处理器3210耦合连接的存储器3220，通信接口3230。处理器3210可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)，或者CPU和NP的组合。处理器还可以进一步包括其它硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其组合。处理器3210可以是指一个处理器，也可以包括多个处理器。存储器3220可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器3220也可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，闪存(flash)，硬盘驱动器(hard disk drive，HDD)或固态硬盘(solid state disk，SSD)；存储器3220还可以包括上述不同种类的存储器的组合。存储器3220可以是指一个存储器，也可以包括多个存储器。存储器3220中存储有计算机可读指令，所述计算机可读指令可以包括多个软件模块，例如发送模块3221，处理模块3222和接收模块3223。处理器3210运行上述各个软件模块后，可以按照各个软件模块的指示进行相应的操作。在本实施例中，一个软件模块所执行的操作实际上是指处理器3210根据所述软件模块的指示而执行的操作。例如，处理器3210运行处理模块3222后执行：
确定第一FlexE链路组发生故障；
删除第三客户与第五客户之间的FlexE交叉；
建立第三客户与第二客户或第四客户之间的FlexE交叉。
处理器3210例如可以是图4所示的节点1中的处理器，第一FlexE链路组例如是图4所示的链路组1，第三客户例如是客户3，第五客户例如是客户5，第二客户例如是客户2，第四客户例如是客户4。
由于两个相邻的FlexE交叉环中各自存在一条环状保护路径，因此，当工作路径出现故障后，承载工作路径的公共节点(例如，节点1)可以利用两个FlexE交叉环的保护路径转发业务数据。对于现有技术中的FlexE交叉环来说，发送节点和接收节点之间仅存在工作路径和E2E保护路径，通常情况下，承载工作路径的节点不承载E2E保护路径，若公共节点承载的工作路径出现故障，工作节点无法通过保护路径转发业务数据，因此，本申请提供的FlexE交叉环和基于该FlexE交叉环的自动保护倒换方法提高了环网的可靠性。
处理器3210还可以在运行接收模块3223后执行：
通过第一客户接收第三网络设备发送的第一FlexE数据；以及，
在运行发送模块3223后执行：
通过第二客户或第四客户转发第一FlexE数据。
第三网络设备例如是图4中的节点3，FlexE数据即符合FlexE协议的码块，第一网络 设备(例如，图4中的节点1)通过保护客户将业务数据(例如，第一FlexE数据)回传给第三网络设备，第三网络设备通过保护路径完成业务数据的转发，从而提高了环网的可靠性。
第一FlexE链路组的链路故障排除后，处理器3210运行处理模块3222后执行：
删除第三客户与第二客户或第四客户之间的FlexE交叉；
建立第一客户与第二客户或第四客户之间的FlexE交叉。
第一客户例如是图4中的客户1。
工作路径通常是网络设备之间优选的传输路径，第一FlexE链路组的链路故障排除后，第一网络设备可以选择将业务数据的传输路径切换至工作路径，从而能够为业务数据提供优选的传输资源。
第一网络设备建立第一客户与第二客户或第四客户之间的FlexE交叉之后，处理器3210还可以在运行接收模块3223后执行：
通过第一客户接收第三网络设备发送的第二FlexE数据；
通过第二客户或第四客户转发第二FlexE数据。
第一网络设备完成路径切换后，通过工作路径转发第二FlexE数据，从而能够为第二FlexE数据提供优选的传输资源。
第一FlexE链路组可以用于承载至少两个客户，该至少两个客户构成一个客户绑定组，该客户绑定组包括第一客户，该客户绑定组中的至少一个客户部署了OAM检测，该客户绑定组中的至少一个客户没有部署OAM检测；处理器3210可以在运行处理模块3222后执行：
基于该客户绑定组中的至少一个客户部署的OAM检测，确定第一FlexE链路组发生故障。
第一网络设备与第三网络设备之间的多个工作客户可以被配置一个工作客户组，第一网络设备与第三网络设备之间的多个保护客户可以被配置一个保护客户组，若第一网络设备通过上述客户组中的一个客户向第三网络设备发送OAM报文后未收到响应报文，则第一网络设备可以确定上述客户组对应的FlexE链路组(例如，第一FlexE链路组)出现故障，无需通过每个工作客户或保护客户发送OAM报文，从而减少了传输资源的消耗。
第一链路组还用于承载第七客户和第八客户，第三链路组还用于承载第九客户，处理器3210还可以在运行处理模块3222后执行：
确定第三FlexE链路组发生故障；
删除第七客户与第九客户之间的FlexE交叉；
建立第七客户与第八客户之间的FlexE交叉。
第七客户例如是图31所示的客户1`，第八客户例如是图31所示的客户5，第九客户例如是图31所示的客户3`。
本实施例所提供的方案在第一FlexE交叉环中建立了网络设备到网络设备之间的保护路径，这样，当第一网络设备与第二网络设备之间的传输路径(例如，第三FlexE链路组)出现故障，第一网络设备可以建立工作客户(例如，第七客户)与保护客户(例如，第八客户)之间的FlexE交叉，通过保护客户将业务数据回传至第三网络设备，为业务数据提供了备用的传输通道，从而提高了第一FlexE交叉环的可靠性。第二FlexE交叉环中也可 以建立类似的保障机制。
第三FlexE链路组的链路故障排除后，处理器3210还可以在运行处理模块3222后执行：
删除第七客户与第八客户之间的FlexE交叉；
建立第七客户与第九客户之间的FlexE交叉。
第九客户对应的路径为工作路径，工作路径通常是网络设备之间优选的传输路径，第三FlexE链路组的链路故障排除后，第一网络设备可以选择将业务数据的传输路径切换至工作路径，从而能够为业务数据提供优选的传输资源。
第三FlexE链路组用于承载至少两个客户，该至少两个客户构成一个客户绑定组，该客户绑定组包括第九客户，该客户绑定组中的至少一个客户部署了OAM检测，该客户绑定组中的至少一个客户没有部署OAM检测；处理器3210还可以在运行处理模块3222后执行：基于所述客户绑定组中至少一个客户部署的OAM检测，确定第三FlexE链路组发生故障。
第一网络设备与第二网络设备之间的多个工作客户可以被配置一个工作客户组，第一网络设备与第二网络设备之间的多个保护客户可以被配置一个保护客户组，若第一网络设备通过上述客户组中的一个客户向第二网络设备发送OAM报文后未收到响应报文，则第一网络设备可以确定上述客户组对应的FlexE链路组(例如，第三FlexE链路组)出现故障，无需通过每个工作客户或保护客户发送OAM报文，从而减少了传输资源的消耗。
图33示出了本申请提供的另一种通信装置的示意图。
该通信装置3300可以应用于图4、图10或图25所示的网络架构中，例如可以应用于图4所示的网络架构中的节点2，或图10所示网络架构的NE6，或图25所示的网络架构中的节点2。通信装置3300可以包括处理器3310，与处理器3310耦合连接的存储器3320，通信接口3330。处理器3310可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)，或者CPU和NP的组合。处理器还可以进一步包括其它硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其组合。处理器3310可以是指一个处理器，也可以包括多个处理器。存储器3320可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器3320也可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，闪存(flash)，硬盘驱动器(hard disk drive，HDD)或固态硬盘(solid state disk，SSD)；存储器3320还可以包括上述不同种类的存储器的组合。存储器3320可以是指一个存储器，也可以包括多个存储器。存储器3320中存储有计算机可读指令，所述计算机可读指令可以包括多个软件模块，例如发送模块3321，处理模块3322和接收模块3323。处理器3310运行上述各个软件模块后，可以按照各个软件模块的指示进行相应的操作。在本实施例中，一个软件模块所执行的操作实际上是指处理器3310根据所述软件模块的指示而执行的操作。例如，处理器3310运行处理模块3322后执行：
确定第一网络设备发生故障；
删除第三客户与第七客户之间的FlexE交叉；
删除第四客户与第八客户之间的FlexE交叉；
建立第七客户与第八客户之间的FlexE交叉。
第一网络设备例如是图4中的节点1，第三客户例如是图4中的客户3，第七客户例如是图4中的客户7，第四客户例如是图4中的客户4，第八客户例如是图4中的客户8。
上述第五客户、第三客户以及第七客户为第一FlexE交叉环的环状保护路径中的客户，上述第四客户、第六客户以及第八客户为第二FlexE交叉环的环状保护路径中的客户，第一网络设备承载了第一FlexE交叉环与第二FlexE交叉环之间的工作路径。当第一FlexE交叉环与第二FlexE交叉环的公共节点(例如，第一网络设备)出现故障时，第一FlexE交叉环与第二FlexE交叉环需要通过另外一个公共节点(例如，第二网络设备)建立两个FlexE交叉环的保护路径之间的关联，以便于转发数据。
由于两个相邻的FlexE交叉环中各自存在一条环状保护路径，因此，当第一网络设备出现故障后，第一FlexE交叉环中与第一网络设备相邻的承载工作路径的网络设备可以利用环状保护路径转发业务数据。对于现有技术中的FlexE交叉环来说，发送节点和接收节点之间仅存在工作路径和E2E保护路径，通常情况下，承载工作路径的网络设备不承载E2E保护路径，若第一网络设备出现故障，第一FlexE交叉环中与第一网络设备相邻的承载工作路径的网络设备无法通过保护路径转发业务数据，因此，本申请提供的FlexE交叉环和基于该FlexE交叉环的自动保护倒换方法提高了环网的可靠性。
第一网络设备建立第七客户与第八客户之间的FlexE交叉之后，处理器3310还可以在运行接收模块3323后执行：
通过第七客户接收第一FlexE数据；
处理器3310还可以在运行发送模块3321后执行：
通过第八客户转发第一FlexE数据。
FlexE数据即符合FlexE协议的码块，第一网络设备通过两个FlexE交叉环的保护客户实现两个FlexE交叉环之间的数据转发，从而提高了环网的可靠性。
第一网络设备的故障排除后，处理器3310还可以在运行处理模块3322后执行：
删除第七客户与第八客户之间的FlexE交叉；
建立第七客户与第三客户之间的FlexE交叉；
建立第八客户与第四客户之间的FlexE交叉。
第一网络设备的故障排除后，第一网络设备即可通过工作路径转发两个FlexE交叉环之间的数据，处理器3310恢复两个FlexE交叉环各自的环状保护路径，继续为环网的可靠性提供保障。
图34示出了本申请提供的再一种通信装置的示意图。
该通信装置3400可以应用于图17所示的网络架构中，例如可以应用于图17所示的网络架构中的节点1。通信装置3400可以包括处理器3410，与处理器3410耦合连接的存储器3420，通信接口3430。处理器3410可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)，或者CPU和NP的组合。处理器还可以进一步包括其它硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以 是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其组合。处理器3410可以是指一个处理器，也可以包括多个处理器。存储器3420可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器3420也可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，闪存(flash)，硬盘驱动器(hard disk drive，HDD)或固态硬盘(solid state disk，SSD)；存储器3420还可以包括上述不同种类的存储器的组合。存储器3420可以是指一个存储器，也可以包括多个存储器。存储器3420中存储有计算机可读指令，所述计算机可读指令可以包括多个软件模块，例如发送模块3421，处理模块3422和接收模块3423。处理器3410运行上述各个软件模块后，可以按照各个软件模块的指示进行相应的操作。在本实施例中，一个软件模块所执行的操作实际上是指处理器3410根据所述软件模块的指示而执行的操作。例如，处理器3410运行处理模块3422后执行：
确定第一FlexE链路组发生故障；
删除第三客户与第五客户之间的FlexE交叉；
建立第三客户与第二客户或第四客户之间的FlexE交叉。
处理器3410例如可以是图17所示的节点1中的处理器，第一FlexE链路组例如是图4所示的链路组1，第三客户例如是客户3，第五客户例如是客户5，第二客户例如是客户2，第四客户例如是客户4。
由于两个相邻的FlexE交叉环中各自存在一条环状保护路径，因此，当工作路径出现故障后，承载工作路径的公共节点(例如，节点1)可以利用两个FlexE交叉环的保护路径转发业务数据。对于现有技术中的FlexE交叉环来说，发送节点和接收节点之间仅存在工作路径和E2E保护路径，通常情况下，承载工作路径的节点不承载E2E保护路径，若公共节点承载的工作路径出现故障，工作节点无法通过保护路径转发业务数据，因此，本申请提供的FlexE交叉环和基于该FlexE交叉环的自动保护倒换方法提高了环网的可靠性。
处理器3410还可以在运行接收模块3423后执行：
通过第一客户接收第三网络设备发送的第一FlexE数据；以及，
在运行发送模块3423后执行：
通过第二客户或第四客户转发第一FlexE数据。
第三网络设备例如是图17中的节点3，FlexE数据即符合FlexE协议的码块，第一网络设备(例如，图17中的节点1)通过保护客户将业务数据(例如，第一FlexE数据)回传给第三网络设备，第三网络设备通过保护路径完成业务数据的转发，从而提高了环网的可靠性。
第一FlexE链路组的链路故障排除后，处理器3410运行处理模块3422后执行：
删除第三客户与第二客户或第四客户之间的FlexE交叉；
建立第一客户与第二客户或第四客户之间的FlexE交叉。
第一客户例如是图17中的客户1。
工作路径通常是网络设备之间优选的传输路径，第一FlexE链路组的链路故障排除后，第一网络设备可以选择将业务数据的传输路径切换至工作路径，从而能够为业务数据提供优选的传输资源。
第一网络设备建立第一客户与第二客户或第四客户之间的FlexE交叉之后，处理器3410还可以在运行接收模块3423后执行：
通过第一客户接收第三网络设备发送的第二FlexE数据；
通过第二客户或第四客户转发第二FlexE数据。
第一网络设备完成路径切换后，通过工作路径转发第二FlexE数据，从而能够为第二FlexE数据提供优选的传输资源。
第一FlexE链路组可以用于承载至少两个客户，该至少两个客户构成一个客户绑定组，该客户绑定组包括第一客户，该客户绑定组中的至少一个客户部署了OAM检测，该客户绑定组中的至少一个客户没有部署OAM检测；处理器3410可以在运行处理模块3422后执行：
基于该客户绑定组中的至少一个客户部署的OAM检测，确定第一FlexE链路组发生故障。
第一网络设备与第三网络设备之间的多个工作客户可以被配置一个工作客户组，第一网络设备与第三网络设备之间的多个保护客户可以被配置一个保护客户组，若第一网络设备通过上述客户组中的一个客户向第三网络设备发送OAM报文后未收到响应报文，则第一网络设备可以确定上述客户组对应的FlexE链路组(例如，第一FlexE链路组)出现故障，无需通过每个工作客户或保护客户发送OAM报文，从而减少了传输资源的消耗。
第一链路组还用于承载第七客户和第八客户，第三链路组还用于承载第九客户，处理器3410还可以在运行处理模块3422后执行：
确定第三FlexE链路组发生故障；
删除第七客户与第九客户之间的FlexE交叉；
建立第七客户与第八客户之间的FlexE交叉。
第七客户例如是图31所示的客户1`，第八客户例如是图31所示的客户5，第九客户例如是图31所示的客户3`。
本实施例所提供的方案在第一FlexE交叉环中建立了网络设备到网络设备之间的保护路径，这样，当第一网络设备与第二网络设备之间的传输路径(例如，第三FlexE链路组)出现故障，第一网络设备可以建立工作客户(例如，第七客户)与保护客户(例如，第八客户)之间的FlexE交叉，通过保护客户将业务数据回传至第三网络设备，为业务数据提供了备用的传输通道，从而提高了第一FlexE交叉环的可靠性。第二FlexE交叉环中也可以建立类似的保障机制。
第三FlexE链路组的链路故障排除后，处理器3410还可以在运行处理模块3422后执行：
删除第七客户与第八客户之间的FlexE交叉；
建立第七客户与第九客户之间的FlexE交叉。
第九客户对应的路径为工作路径，工作路径通常是网络设备之间优选的传输路径，第三FlexE链路组的链路故障排除后，第一网络设备可以选择将业务数据的传输路径切换至工作路径，从而能够为业务数据提供优选的传输资源。
第三FlexE链路组用于承载至少两个客户，该至少两个客户构成一个客户绑定组，该客户绑定组包括第九客户，该客户绑定组中的至少一个客户部署了OAM检测，该客户绑 定组中的至少一个客户没有部署OAM检测；处理器3410还可以在运行处理模块3422后执行：基于所述客户绑定组中至少一个客户部署的OAM检测，确定第三FlexE链路组发生故障。
第一网络设备与第二网络设备之间的多个工作客户可以被配置一个工作客户组，第一网络设备与第二网络设备之间的多个保护客户可以被配置一个保护客户组，若第一网络设备通过上述客户组中的一个客户向第二网络设备发送OAM报文后未收到响应报文，则第一网络设备可以确定上述客户组对应的FlexE链路组(例如，第三FlexE链路组)出现故障，无需通过每个工作客户或保护客户发送OAM报文，从而减少了传输资源的消耗。
装置实施例和方法实施例中完全对应，方法实施例中的步骤由装置实施例中相应的模块执行，例如通信接口执行方法实施例中接收步骤和发送步骤，除发送接收外的其它步骤可以由处理器执行。具体模块的功能可以参考相应的方法实施例，不再详述。
在本申请各个实施例中，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请的实施过程构成任何限定。
另外，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (17)

  1. 一种通信方法，其特征在于，应用于环网，所述环网包括第一灵活以太FlexE交叉环和第二FlexE交叉环，所述第一FlexE交叉环包括第一网络设备、第二网络设备和第三网络设备，所述第二FlexE交叉环包括第四网络设备、所述第一网络设备和所述第二网络设备，所述第一网络设备与所述第二网络设备相邻，所述第一网络设备与所述第三网络设备相邻，所述第一网络设备与所述第四网络设备相邻；所述第一网络设备和所述第二网络设备为所述第一FlexE交叉环和所述第二FlexE交叉环的相交节点；所述第一网络设备与所述第三网络设备之间具有第一FlexE链路组，所述第一网络设备与所述第四网络设备之间具有第二FlexE链路组，所述第一网络设备与所述第二网络设备之间具有第三FlexE链路组，所述第一FlexE链路组用于承载第一客户和第五客户，所述第二FlexE链路组用于承载第二客户和第六客户，所述第三FlexE链路组用于承载第三客户和第四客户，所述第三客户用于在所述第一FlexE交叉环内传输数据，所述第四客户用于在所述第二FlexE交叉环内传输数据，
    所述方法包括：
    所述第一网络设备确定所述第一FlexE链路组发生故障；
    所述第一网络设备删除所述第三客户与所述第五客户之间的FlexE交叉；
    所述第一网络设备建立所述第三客户与所述第二客户或所述第四客户之间的FlexE交叉。
  2. 根据权利要求1所述的方法，其特征在于，所述第一FlexE链路组的链路故障排除后，所述方法还包括：
    所述第一网络设备删除所述第三客户与所述第二客户或所述第四客户之间的FlexE交叉；
    所述第一网络设备建立所述第一客户与所述第二客户或所述第四客户之间的FlexE交叉。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一FlexE链路组用于承载至少两个客户，所述至少两个客户构成一个客户绑定组，所述客户绑定组包括所述第一客户，所述客户绑定组中至少一个客户部署操作、管理和维护OAM检测，所述客户绑定组中至少一个客户没有部署OAM检测；
    所述第一网络设备确定所述第一FlexE链路组发生故障包括：
    所述第一网络设备基于所述OAM检测，确定所述第一FlexE链路组发生故障。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一链路组还用于承载第七客户和第八客户，所述第三链路组还用于承载第九客户，所述方法还包括：
    所述第一网络设备确定所述第三FlexE链路组发生故障；
    所述第一网络设备删除所述第七客户与所述第九客户之间的FlexE交叉；
    所述第一网络设备建立所述第七客户与所述第八客户之间的FlexE交叉。
  5. 根据权利要求4所述的方法，其特征在于，所述第三FlexE链路组的链路故障排除后，所述方法还包括：
    所述第一网络设备删除所述第七客户与所述第八客户之间的FlexE交叉；
    所述第一网络设备建立所述第七客户与所述第九客户之间的FlexE交叉。
  6. 根据权利要求4或5所述的方法，其特征在于，所述第三FlexE链路组用于承载至少两个客户，所述至少两个客户构成一个客户绑定组，所述客户绑定组包括所述第九客户，所述客户绑定组中至少一个客户部署OAM检测，所述客户绑定组中至少一个客户没有部署OAM检测；
    所述第一网络设备确定所述第三FlexE链路组发生故障包括：
    所述第一网络设备基于所述OAM检测，确定所述第三FlexE链路组发生故障。
  7. 一种通信装置，其特征在于，应用于环网，所述环网包括第一灵活以太FlexE交叉环和第二FlexE交叉环，所述第一FlexE交叉环包括第一网络设备、第二网络设备和第三网络设备，所述第二FlexE交叉环包括第四网络设备、所述第一网络设备和所述第二网络设备，所述第一网络设备与所述第二网络设备相邻，所述第一网络设备与所述第三网络设备相邻，所述第一网络设备与所述第四网络设备相邻；所述第一网络设备和所述第二网络设备为所述第一FlexE交叉环和所述第二FlexE交叉环的相交节点；所述第一网络设备与所述第三网络设备之间具有第一FlexE链路组，所述第一网络设备与所述第四网络设备之间具有第二FlexE链路组，所述第一网络设备与所述第二网络设备之间具有第三FlexE链路组，所述第一FlexE链路组用于承载第一客户和第五客户，所述第二FlexE链路组用于承载第二客户和第六客户，所述第三FlexE链路组用于承载第三客户和第四客户，所述第三客户用于在所述第一FlexE交叉环内传输数据，所述第四客户用于在所述第二FlexE交叉环内传输数据，
    所述通信装置配置于所述第一网络设备中，所述通信装置包括：
    存储器，该存储器包括计算机可读指令；
    与所述存储器相连的处理器，所述处理器用于执行所述计算机可读指令，从而执行以下操作：
    确定所述第一FlexE链路组发生故障；
    删除所述第三客户与所述第五客户之间的FlexE交叉；
    建立所述第三客户与所述第二客户或所述第四客户之间的FlexE交叉。
  8. 根据权利要求7所述的通信装置，其特征在于，所述第一FlexE链路组的链路故障排除后，所述处理器还用于：
    删除所述第三客户与所述第二客户或所述第四客户之间的FlexE交叉；
    建立所述第一客户与所述第二客户或所述第四客户之间的FlexE交叉。
  9. 根据权利要求7或8所述的通信装置，其特征在于，所述第一FlexE链路组用于承载至少两个客户，所述至少两个客户构成一个客户绑定组，所述客户绑定组包括所述第一客户，所述客户绑定组中至少一个客户部署操作、管理和维护OAM检测，所述客户绑定组中至少一个客户没有部署OAM检测；
    所述处理器具体用于：
    基于所述OAM检测，确定所述第一FlexE链路组发生故障。
  10. 根据权利要求7至9中任一项所述的通信装置，其特征在于，所述第一链路组还用于承载第七客户和第八客户，所述第三链路组还用于承载第九客户，所述处理器还用于：
    确定所述第三FlexE链路组发生故障；
    删除所述第七客户与所述第九客户之间的FlexE交叉；
    建立所述第七客户与所述第八客户之间的FlexE交叉。
  11. 根据权利要求10所述的通信装置，其特征在于，所述第三FlexE链路组的链路故障排除后，所述处理器还用于：
    删除所述第七客户与所述第八客户之间的FlexE交叉；
    建立所述第七客户与所述第九客户之间的FlexE交叉。
  12. 根据权利要求10或11所述的通信装置，其特征在于，所述第三FlexE链路组用于承载至少两个客户，所述至少两个客户构成一个客户绑定组，所述客户绑定组包括所述第九客户，所述客户绑定组中至少一个客户部署OAM检测，所述客户绑定组中至少一个客户没有部署OAM检测；
    所述处理器具体用于：
    基于所述OAM检测，确定所述第三FlexE链路组发生故障。
  13. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得所述计算机执行权利要求1-6中任一项所述的方法。
  14. 一种网络设备，其特征在于，包括权利要求7-12中任一项所述的通信装置。
  15. 一种网络设备，其特征在于，用于执行权利要求1-6中任一项所述的方法。，
  16. 一种计算机程序产品，包括计算机程序，其特征在于，当所述计算机程序在计算机上运行时，使得所述计算机执行权利要求1-6任一项所述的方法。
  17. 一种通信系统，其特征在于，包括权利要求14或15所述的网络设备。
PCT/CN2019/121841 2018-12-10 2019-11-29 通信方法和装置 WO2020119474A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP19896142.7A EP3886363B1 (en) 2018-12-10 2019-11-29 Communication method and apparatus
JP2021532928A JP7191228B2 (ja) 2018-12-10 2019-11-29 通信方法および装置
US17/343,192 US11804982B2 (en) 2018-12-10 2021-06-09 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811505586.1A CN111294226B (zh) 2018-12-10 2018-12-10 通信方法和装置
CN201811505586.1 2018-12-10

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/343,192 Continuation US11804982B2 (en) 2018-12-10 2021-06-09 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2020119474A1 true WO2020119474A1 (zh) 2020-06-18

Family

ID=71030575

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/121841 WO2020119474A1 (zh) 2018-12-10 2019-11-29 通信方法和装置

Country Status (5)

Country Link
US (1) US11804982B2 (zh)
EP (1) EP3886363B1 (zh)
JP (1) JP7191228B2 (zh)
CN (1) CN111294226B (zh)
WO (1) WO2020119474A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111211957B (zh) * 2018-11-21 2021-10-01 华为技术有限公司 通信方法和装置
CN112911420A (zh) * 2019-12-03 2021-06-04 中兴通讯股份有限公司 基于FlexE网络的重路由方法、电子设备和可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3013017A1 (en) * 2014-10-24 2016-04-27 Ciena Corporation Channelized oduflex systems and methods for flexible ethernet and otn multiplexing
CN107395425A (zh) * 2017-07-31 2017-11-24 烽火通信科技股份有限公司 一种灵活以太网1+1保护倒换实现方法
CN108347317A (zh) * 2017-01-22 2018-07-31 华为技术有限公司 一种业务的传输方法、网络设备及网络系统

Family Cites Families (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4214153B2 (ja) 1999-10-25 2009-01-28 富士通株式会社 リング伝送システム用光伝送装置及びリング伝送システム用光伝送方法
JP5061748B2 (ja) * 2007-06-21 2012-10-31 日本電気株式会社 パケットリングネットワークシステム、パケット転送方法
EP2216943A4 (en) 2007-11-30 2017-01-11 Fujitsu Limited Sonet/sdh transmission device
US20120207017A1 (en) * 2009-07-16 2012-08-16 Daniele Ceccarelli Recovery mechanism for point-to-multipoint traffic
GB2488729B (en) 2009-12-28 2015-11-04 Fujitsu Ltd Method of switching optical transport network and node device
JP5664645B2 (ja) * 2010-02-18 2015-02-04 日本電気株式会社 品質劣化箇所分析システム、品質劣化箇所分析装置、品質劣化箇所分析方法およびプログラム
US8976680B2 (en) * 2010-03-15 2015-03-10 Juniper Networks, Inc. Operations, administration, and management fields for packet transport
JP5621668B2 (ja) 2011-03-15 2014-11-12 富士通株式会社 伝送システム、冗長区間設定方法および接続ノード
US20140301185A1 (en) * 2011-04-15 2014-10-09 Hangzhou H3C Technologies Co., Ltd Handling a fault in an ethernet ring network
JP5580793B2 (ja) * 2011-08-30 2014-08-27 アラクサラネットワークス株式会社 ネットワーク装置、ネットワークシステム、およびコンピュータプログラム
JP5730737B2 (ja) * 2011-10-04 2015-06-10 日本電信電話株式会社 マルチリング網におけるパス設定方法及びパス切替方法
CN102437957B (zh) * 2011-12-16 2015-07-08 华为技术有限公司 一种多协议标签交换的相交环处理方法及装置
CN102546425B (zh) 2012-01-31 2014-11-05 华为技术有限公司 相交环保护方法、设备和系统
CN103731357B (zh) * 2012-10-15 2018-02-27 中兴通讯股份有限公司 网络拓扑结构的确定方法及装置
CN103841017B (zh) * 2012-11-22 2017-07-14 华为技术有限公司 环网保护中标签自动分配的方法及设备
CN103490921B (zh) 2013-09-09 2017-06-20 华为技术有限公司 网络保护方法、装置、下环节点及系统
WO2015097318A1 (es) * 2013-12-26 2015-07-02 Telefonica, S.A Procedimiento y sistema para restaurar degradaciones de la qos en redes de mpls
CN105099904B (zh) * 2014-04-30 2018-06-05 华为技术有限公司 一种确定中间路由节点的方法、装置及系统
JP2016122896A (ja) * 2014-12-24 2016-07-07 日立金属株式会社 中継システムおよびスイッチ装置
US20160204976A1 (en) * 2015-01-14 2016-07-14 Rajnath Singh Identifying the absence and presence of a ring protection link owner node in an ethernet network
US9838290B2 (en) * 2015-06-30 2017-12-05 Ciena Corporation Flexible ethernet operations, administration, and maintenance systems and methods
US9800361B2 (en) * 2015-06-30 2017-10-24 Ciena Corporation Flexible ethernet switching systems and methods
US10135760B2 (en) * 2015-06-30 2018-11-20 Ciena Corporation Flexible Ethernet chip-to-chip inteface systems and methods
EP3713158B1 (en) * 2015-06-30 2022-02-09 Ciena Corporation Time transfer systems and methods over a stream of ethernet blocks
WO2017008862A1 (en) * 2015-07-16 2017-01-19 Telefonaktiebolaget Lm Ericsson (Publ) Restoration method for an mpls ring network
US10341020B2 (en) * 2016-03-17 2019-07-02 Avago Technologies International Sales Pte. Limited Flexible ethernet logical lane aggregation
US10505655B2 (en) * 2016-07-07 2019-12-10 Infinera Corp. FlexE GMPLS signaling extensions
CN108075903B (zh) * 2016-11-15 2020-04-21 华为技术有限公司 用于建立灵活以太网群组的方法和设备
CN108156074B (zh) * 2016-12-02 2020-10-23 华为技术有限公司 保护倒换方法、网络设备及系统
US10382167B2 (en) * 2016-12-13 2019-08-13 Ciena Corporation Flexible ethernet enhanced forward error correction
CN113300876B (zh) 2016-12-26 2022-09-02 华为技术有限公司 Dcn报文处理方法、网络设备和网络系统
JP6950215B2 (ja) 2017-03-21 2021-10-13 富士通株式会社 通信装置及び信号中継方法
CN111106964A (zh) * 2017-04-28 2020-05-05 华为技术有限公司 配置链路组的方法和设备
CN111585778B (zh) * 2019-02-19 2022-02-25 华为技术有限公司 一种灵活以太网通信方法及网络设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3013017A1 (en) * 2014-10-24 2016-04-27 Ciena Corporation Channelized oduflex systems and methods for flexible ethernet and otn multiplexing
CN108347317A (zh) * 2017-01-22 2018-07-31 华为技术有限公司 一种业务的传输方法、网络设备及网络系统
CN107395425A (zh) * 2017-07-31 2017-11-24 烽火通信科技股份有限公司 一种灵活以太网1+1保护倒换实现方法

Also Published As

Publication number Publication date
JP7191228B2 (ja) 2022-12-16
EP3886363B1 (en) 2023-05-31
CN111294226A (zh) 2020-06-16
CN111294226B (zh) 2023-05-09
EP3886363A1 (en) 2021-09-29
EP3886363A4 (en) 2022-01-19
JP2022512470A (ja) 2022-02-04
US11804982B2 (en) 2023-10-31
US20210297285A1 (en) 2021-09-23

Similar Documents

Publication Publication Date Title
WO2020103530A1 (zh) 通信方法和装置
US7394758B2 (en) Method for supporting SDH/SONET APS on Ethernet
US8730822B2 (en) Method for supporting SDH/SONET OAMP on ethernet
WO2020168898A1 (zh) 一种灵活以太网通信方法及网络设备
WO2007129699A1 (ja) 通信システム、ノード、端末、通信方法、およびプログラム
US11804982B2 (en) Communication method and apparatus
CN101170711A (zh) 自动交换光网络scn和mcn信息传递装置及方法
US20210385127A1 (en) Flexible ethernet communication method and network device
WO2018149294A1 (zh) 一种分组网络中处理业务流的方法及装置
CN106850256A (zh) 一种分组传送网及其保护方法、网元设备
Delgado et al. A novel approach to automatic protection switching for Ethernet optical networks

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: 19896142

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021532928

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: 2019896142

Country of ref document: EP

Effective date: 20210622