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

通信方法和装置

Info

Publication number
WO2020103530A1
WO2020103530A1 PCT/CN2019/104811 CN2019104811W WO2020103530A1 WO 2020103530 A1 WO2020103530 A1 WO 2020103530A1 CN 2019104811 W CN2019104811 W CN 2019104811W WO 2020103530 A1 WO2020103530 A1 WO 2020103530A1
Authority
WO
WIPO (PCT)
Prior art keywords
flexe
customer
network device
node
link group
Prior art date
Application number
PCT/CN2019/104811
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 JP2021527214A priority Critical patent/JP7168286B2/ja
Priority to EP19888000.7A priority patent/EP3873037A4/en
Publication of WO2020103530A1 publication Critical patent/WO2020103530A1/zh
Priority to US17/325,033 priority patent/US20210273826A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • 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
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • 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
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/41—Flow control; Congestion control by acting on aggregated flows or links

Definitions

  • This 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 processing method and 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.
  • a communication processing method is provided, which is applied to a ring network.
  • the ring network is a FlexE cross-ring.
  • the FlexE cross-ring includes a first network device, a second network device, and a third network device.
  • the second network device is adjacent, and the first network device is adjacent to the third network device; there is a first FlexE link group and a second FlexE link group between the first network device and the second network device, the first FlexE The link group is used to carry the first customer, and the second FlexE link group is used to carry the second customer; there is a third FlexE link group between the first network device and the third network device, and the third FlexE link group is used to Carrying a third customer;
  • the method includes: the first network device determines that the third FlexE link group has failed; the first network device deletes the FlexE cross between the first customer and the third customer; establishing the first customer and the second customer FlexE cross between; the service data transmission path is switched from the working path to the protection path, the working path includes the
  • the first FlexE link group and the second FlexE link group may be the same link group or different link groups.
  • the solution provided by this application establishes a protection path between network devices and network devices in the FlexE cross-ring, so that when the transmission path between the first network device and the third network device (for example, the third FlexE link group ) A failure occurs, the first network device can establish a FlexE cross between the working client (eg, the first client) and the protection client (eg, the second client), providing a backup transmission channel for business data, thereby improving the FlexE cross Ring reliability.
  • the method further includes: the first network device receives the first FlexE data sent by the second network device through the first client; the first The network device uses the second FlexE link group to forward the first FlexE data through the second client.
  • FlexE data is a code block that conforms to the FlexE protocol.
  • the first network device transmits service data (for example, the first FlexE data) back to the second network device by protecting the customer, and the second network device completes the forwarding of the service data through the protection path, thereby Improves the reliability of the FlexE cross-ring.
  • the method further includes: the first network device deletes the FlexE cross between the first client and the second client; the first network device establishes the first FlexE cross between a customer and a third customer; the first network device switches the transmission path of service data from the protection path to 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, which can provide optimization for the service data Transmission resources.
  • the method further includes: the first network device receives second FlexE data sent by the second network device through the first client; the first The network device forwards the second FlexE data to the third network device through the third 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 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 the third customer and the customer, and the third customer deploys OAM detection ,
  • the fourth customer has not deployed OAM detection; the first network device determining that the third FlexE link group fails includes: based on the OAM detection deployed by the third customer, the first network device determines that the third FlexE link group fails.
  • 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 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, the memory including computer-readable instructions; the device further includes a processor connected to the memory, the processor is configured to execute the computer-readable instructions, Performing the operations in the method of the first aspect or any possible design of the first aspect.
  • the present application also provides a computer-readable storage medium in which computer program code is stored.
  • the communication device executes the first aspect And the method described in any possible design of the first aspect.
  • a chip in which instructions are stored, which when executed on a communication device or a network device, causes the chip to perform the above-mentioned first aspect and any possible design method of the first aspect.
  • a computer program product includes: computer program code, which when executed by a processor of a communication device, causes the communication device to execute the first aspect and any one of the first aspect A possible design method.
  • a network device for performing the method in the first aspect and any possible design of the first aspect.
  • a network device including the communication device according to the second aspect.
  • FIG. 3 shows a schematic diagram of FlexE cross transmission technology applicable to the present application
  • FIG. 5 shows a schematic diagram of a method for providing upper and lower rings of service data provided by this application
  • FIG. 6 is a schematic diagram of a communication processing method provided by this application.
  • FIG. 7 is a schematic diagram of a data forwarding method after a FlexE cross-ring failure provided by this application.
  • FIG. 9 is a schematic diagram of another data forwarding method after a FlexE cross-ring failure provided by this application.
  • FIG. 10 is a schematic diagram of a node configured with a customer group provided by this application.
  • FIG. 11 is a schematic diagram of another node provided with a client group provided by this application.
  • FIG. 12 is a schematic diagram of yet another node configured with a customer group provided by this application.
  • FIG. 13 is a schematic diagram of a FlexE cross-ring including nodes configured with customer groups provided by this application;
  • FIG. 14 is a schematic diagram of a data forwarding method after a FlexE cross-ring including a node configured with a customer group fails according to this application;
  • 16 is a schematic diagram of a communication device provided by the present application.
  • node 1 and node 2 represent two different nodes, and there is no other limitation; the first FlexE data and the second FlexE data represent two different FlexE data, and there are no other limitations.
  • 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 ”).
  • FlexE shim flexible Ethernet time division multiplexing layer
  • 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 number of each PHY included in a FlexE link group need not be consecutive.
  • 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 further divided into a physical coding sublayer (PCS), a physical medium access (PMA) sublayer, and a physical medium dependent (PMD) sublayer.
  • PCS physical coding sublayer
  • PMA physical medium access
  • PMD physical medium dependent 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). In the process of receiving signals, PCS The reverse process of the above steps will be performed. 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) .
  • 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 cross ring (that is, a ring Ethernet that uses FlexE cross technology) provided by this application.
  • the FlexE link group between node 1 and node 2 can be called link group 1
  • the FlexE link group between node 2 and node 3 can be called link group 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 cross-ring shown in FIG. 4 includes three nodes.
  • 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 (eg, optical fibers), and both the working path and the protection path are bidirectional paths.
  • data can be transmitted from node 1 to node 2 through the working path, and data can also The working path is transmitted from node 2 to node 1.
  • Different paths correspond to different customers, so you can use the customer's logo to describe the working path or protection path.
  • the PE node After the PE node (for example, node 2) receives the data through the UNI, it can determine the corresponding FlexE interface (ie, client) for forwarding by looking up the virtual local area network (VLAN) identifier corresponding to the data.
  • the static path can be configured in advance through the network management device, and FlexE crossover between various customers can be configured. It should be noted that node 2 is now a PE device and receives data through UNI.
  • 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 customer 1 in the PHY corresponding to customer 1; m time slots allocated to customer 4 in the PHY corresponding to customer 4. 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 3, node 1 uses the FlexE cross-connection established between customer 1 and customer 4, through the m occupied by customer 4. The time slots and the PHY corresponding to client 4 forward the data to node 3.
  • both the working path and the protection path are in a closed loop state.
  • there is a FlexE intersection between customer 1 and customer 4 as shown by the solid line in node 1 in FIG. 4, data can be transmitted from the working path of customer 1 to the working path of customer 4, or from the working path of customer 4 The working path transmitted to customer 1.
  • the node When the service data (ie, the information to be sent) is looped, the node deletes the FlexE cross between the two working clients. For example, when service data is looped on node 2, node 2 deletes the FlexE cross between customer 1 and customer 6.
  • FIG. 5 shows a schematic diagram of a method for providing service data in a ring and a ring.
  • node 2 After node 2 obtains the business data through the UNI, it performs the loop processing, that is, deletes the FlexE cross between customer 1 and customer 6, and selects a transmission path to send the business data according to the destination address of the business data. For example, if the destination address of the business data is node 3, then node 2 can select the transmission path of "node 2 ⁇ node 1 ⁇ node 3" and send the business data to node 1 through client 1.
  • node 1 After receiving the business data through the working path corresponding to customer 1, node 1 sends the business data through customer 4 based on the FlexE intersection between customer 1 and customer 4.
  • the node 3 After receiving the service data through the working path corresponding to the client 4, the node 3 performs the next loop processing, that is, deletes the FlexE cross between the client 4 and the client 6, and sends the service data through the UNI of the node 3.
  • node 2 After node 2 obtains the business data through UNI and determines the transmission path, node 2 can select customer 1 to send business data from multiple customers using the VLAN identifier corresponding to the business data, that is, when node 2 is the sending end, customer 1 is a ring customer; if Node 2 as the receiving end receives service data from other nodes through client 1, then node 2 can perform down-loop processing on the service data and send the service data through UNI, that is, when node 2 is the receiving end, client 1 is down Ring customers.
  • the node 3 receives the service data through the client 4, the node 3 processes the service data according to the pre-configured upper and lower ring clients.
  • the upper ring customer and the lower ring customer of each of the above nodes are the customer configuration when node 2 is the PE node. If node 2 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.
  • Node 2 is configured as two PE nodes with two working paths: "Node 2 ⁇ Node 1 ⁇ Node 3" and "Node 2 ⁇ Node 3"; Node 2 is also configured with a protection path, as shown in Figure 5 Closed loop shown by the dotted line in the middle.
  • 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 the link group 3 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 4, and does not receive a response message for the OAM message within N cycles, node 1 determines that link group 3 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 3 fails.
  • the method for node 1 to determine the failure of the working path and the protection path between node 1 and node 3 is only an example, and the specific method for node 1 to determine the failure of link group 3 in this application is not limited.
  • node 1 establishes a FlexE cross between customer 1 and customer 3.
  • node 2 After receiving the business data through customer 3, node 2 sends the business data through customer 5 according to the FlexE cross between customer 3 and customer 5. After node 3 receives the business data through customer 5, since customer 5 is a pre-configured lower-loop customer of node 3, node 3 performs the lower-loop processing, deletes the FlexE cross between customer 5 and customer 2, and passes the UNI of node 3 Send business data.
  • the nodes in the FlexE cross-ring can follow the Method 600 completes the forwarding of business data. For example, after a link group between any intermediate node and a receiving node between the sending node and the receiving node fails, the intermediate node can return the service data to the sending node through the protection path between two adjacent nodes , And transmitted to the receiving node via the sending node to complete the forwarding of business data.
  • a FlexE cross-ring configured with an E2E protection path, there is only a protection path between the sending node and the receiving node.
  • 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 FlexE cross-ring.
  • FIG. 8 is a schematic diagram of another FlexE cross ring provided by this application.
  • Network elements (NE) 1, NE2, NE3, NE4, NE5 and NE6 form a FlexE cross-ring, where NE1 is connected as a PE to customer equipment (CE) 1, and NE4 is connected as another PE to CE2 .
  • the aforementioned NE may also be called a node or a network device.
  • the service data sent by the base station can be transmitted to the lower ring of NE4 according to the transmission path of "NE1 ⁇ NE2 ⁇ NE3 ⁇ NE4" after passing through the ring of NE1.
  • NE3 determines that the FlexE link group between NE3 and NE4 is faulty, NE3 can delete the FlexE cross between the two working customers of NE3, and at the same time, establish a FlexE cross between NE3's working customer and protection customer to connect the Data is transmitted to NE2 through the protection path between NE3 and NE2.
  • NE2 transmits service data to NE1 through the protection path between NE2 and NE1 based on the FlexE cross between the two protection customers.
  • the service data is finally transmitted to the lower ring of NE4 according to the transmission path of "NE1 ⁇ NE2 ⁇ NE3 ⁇ NE2 ⁇ NE1 ⁇ NE6 ⁇ NE5 ⁇ NE4", as shown in FIG. 9.
  • FlexE cross ring 8 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. Shown in FIG. FlexE cross ring 8 may also be applied in the 5th generation (5 th generation, 5G) mobile communication system, which, may be directly connected to CEl 5G mobile communication system, a base station (GNB) or indirectly.
  • 4G 4 th generation, 4G mobile communication system
  • eNB base station
  • GNB base station
  • the FlexE cross-ring shown in FIG. 8 may also be in a cross-layer network architecture, where NE1 may be connected to an access layer device, and NE4 may be connected to an aggregation layer device or a core layer device.
  • 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.
  • the node 1 includes two physical ports (ie, PHY), which are an east physical port and a west physical port, respectively.
  • PHY physical ports
  • the node 1 shown in FIG. 10 is only an example, and the node 1 may also include more physical ports.
  • the eastbound physical port corresponds to 6 customers, namely customer 1, customer 3, customer 7, customer 8, customer 9 and customer 10, of which customer 1, customer 7 and customer 8 are working customers (ie, corresponding to the working path Customer), customer 3, customer 8 and customer 10 are protected customers (ie, customers corresponding to the protection path).
  • the westward physical port corresponds to 6 customers, namely customer 2, customer 4, customer 11, customer 12, customer 13 and customer 14, of which customer 4, customer 11 and customer 12 are working customers, customer 2, customer 13 and customer 14 To protect customers.
  • the three working clients on the east physical port are configured as a client group (client group); the three working clients on the west physical port are configured as another client group, namely, work client group 2.
  • client group the customer group may also be referred to as a customer binding group.
  • the three protection clients on the east physical port are configured as one client group, that is, protection client group 1, and the three protection clients on the west physical port are configured as another client group, that is, protection client group 2.
  • 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, 2 customers as a customer group, or more customers as a customer group.
  • node 2 and node 3 can also be configured with working client groups and protection client groups.
  • the configuration results are shown in Figure 11 and Figure 12.
  • the FlexE cross-ring including the node 1 shown in FIG. 10, the node 2 shown in FIG. 11 and the node 3 shown in FIG. 12 is shown in FIG. If the FlexE link group corresponding to the west physical port of node 1 fails, node 1 can delete the FlexE cross between the west physical port and the east physical port, and establish a working customer group and a protection customer group FlexE between them will send business data from the east to the physical port protection client group.
  • the present application also provides a method for detecting the failure of the FlexE cross-ring, which is applied to the FlexE cross-ring including the customer group as shown in FIG. 13.
  • the method includes:
  • Node 1 sends an OAM message to node 3 through working client 4.
  • 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 11 or The client 12 sends an OAM message, thereby reducing the 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 FIG. 15.
  • 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 ones
  • 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 FlexE cross between working customers and protecting customers in the same direction.
  • the APS code block is the first 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. 15 is only an example, and the application does not limit the coding format of the OAM message.
  • a 64B coding format can also be used to encode the OAM message.
  • 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 the units in this application is schematic, and is only a division of logical functions. In actual implementation, there may be another division manner.
  • FIG. 16 shows a schematic diagram of a communication device provided by this application.
  • the communication device 1600 can be applied to the network architecture shown in FIG. 4 or FIG. 8, for example, can be applied to the node 1 in the network architecture shown in FIG. 4 or NE1 of the network architecture shown in FIG.
  • the communication device 1600 may include a processor 1610, a memory 1620 coupled to the processor 1610, and a communication interface 1630.
  • the processor 1610 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 logic gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL), or a combination thereof.
  • the processor 1610 may refer to one processor, or may include multiple processors.
  • the memory 1620 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory 1620 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 1620 may also include a combination of the above-mentioned different types of memory.
  • the memory 1620 may refer to one memory, or may include multiple memories.
  • the memory 1620 stores computer readable instructions, and the computer readable instructions may include multiple software modules, such as a sending module 1621, a processing module 1622, and a receiving module 1623.
  • the processor 1610 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 1610 according to the instruction of the software module.
  • the processor 1610 executes the processing module 1622 and executes:
  • the processor 1610 may be, for example, the processor in the node 1 shown in FIG. 4, the third FlexE link group is, for example, the link group 3 shown in FIG. 4, the first customer is, for example, the customer 1, and the third customer is, for example, the customer 4.
  • the second customer is customer 3, for example.
  • the processor 1610 may also be executed after running the receiving module 1623: receiving the first FlexE data sent by the second network device through the first client; and, after running the sending module 1623, executing: through the second client The second network device forwards the first FlexE data.
  • the processor 1610 may also execute after running the processing module 1622: delete the FlexE cross between the first customer and the second customer; establish the first customer and the third customer FlexE cross between.
  • the processor 1610 may also execute after running the receiving module 1623: receive the second FlexE data sent by the second network device through the first client; and forward the second FlexE data to the third network device through the third client.
  • the second network device may be, for example, the node 2 shown in FIG. 4, and the third network device may be, for example, the node 3 shown in FIG.
  • 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 third customer and a fourth customer, and the third customer deploys OAM detection
  • the fourth customer has not deployed OAM detection; the processor 1610 can also execute after running the processing module 1622: based on the OAM detection deployed by the third customer, it is determined that the third FlexE link group is faulty.
  • 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.
  • 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)
  • Environmental & Geological Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请提供了一种在FlexE交叉环中传输数据的方法，组成FlexE交叉环的至少3个节点包括第一节点、第二节点和第三节点，任意两个相邻节点之间存在保护路径和工作路径，保护路径是工作路径的备份路径。本申请所提供的方案在FlexE交叉环中建立了节点到节点之间的保护路径，这样，当FlexE交叉环中任意两个相邻节点间的FlexE链路组出现故障，FlexE交叉环中的节点仍然可以完成数据转发，例如，第一节点与第三节点之间的FlexE链路组出现故障，第一节点可以通过第一节点与第二节点之间的保护路径将数据回传给第二节点，以便于第二节点通过其它路径传输至第三节点，从而提高了FlexE交叉环的可靠性。

Description

通信方法和装置
本申请要求于2018年11月21日提交中国国家知识产权局、申请号为201811394199.5、申请名称为“通信方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种应用于灵活以太交叉环的环网保护方法和装置。
背景技术
灵活以太网(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交叉环的可靠性。
一种可能的设计中，第三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示出了本申请提供的一种业务数据的上环和下环方法的示意图；
图6是本申请提供的一种通信处理方法的示意图；
图7是本申请提供的一种FlexE交叉环出现故障后的数据转发方法的示意图；
图8是本申请提供的另一种FlexE交叉环的示意图；
图9是本申请提供的另一种FlexE交叉环出现故障后的数据转发方法的示意图；
图10是本申请提供的一种配置了客户组的节点的示意图；
图11是本申请提供的另一种配置了客户组的节点的示意图；
图12是本申请提供的再一种配置了客户组的节点的示意图；
图13是本申请提供的一种包含配置了客户组的节点的FlexE交叉环的示意图；
图14是本申请提供的一种包含配置了客户组的节点的FlexE交叉环出现故障后的数据转发方法的示意图；
图15是本申请提供的一种OAM报文格式的示意图；
图16是本申请提供的一种通信装置的示意图。
具体实施方式
在没有特别说明的情况下，本申请中提及“1”、“2”、“第一”以及“第二”等序数词用于对多个对象进行区分，不用于限定多个对象的顺序。例如，节点1和节点2表示两个不同的节点，除此之外并无其它限定；第一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与节点2之间的FlexE链路组可以称为链路组1，节点2与节点3之间的FlexE链路组可以称为链路组2，节点3与节点1之间的FlexE链路组可以称为链路组3。每个链路组承载有至少一个工作路径和/或至少一个保护路径。
本申请中所述的工作路径，也可被称为工作通道，是指系统配置的用于业务数据传输的路径。当FlexE链路组仅承载工作路径时，该FlexE链路组可被称为工作FlexE链路组。本申请所述的保护路径，也可被称为保护通道，是指系统配置的工作路径的备份路径，即，当工作路径无法进行业务数据的传输时，代替工作路径进行业务数据传输的路径。当FlexE链路组仅承载保护路径时，该FlexE链路组可被称为保护FlexE链路组。
图4所示的FlexE交叉环包括3个节点，在没有业务数据上环的情况下，各个节点例如是图3所示的P设备。各个节点之间存在用于传输数据的工作路径和保护路径。工作路径和保护路径是基于物理链路(例如，光纤)的数据通道，并且，工作路径和保护路径均为双向路径，例如，数据可以通过工作路径从节点1传输至节点2，数据也可以通过该工作路径从节点2传输至节点1。不同的路径对应不同的客户，因此，可以使用客户的标识来描述工作路径或者保护路径。
PE节点(例如，节点2)通过UNI接收到数据后，可以通过查找该数据对应的虚拟局域网(virtual local area network，VLAN)标识，确定相应的FlexE接口(即，客户)进行 转发。可以通过网络管理设备提前配置静态路径，并配置各个客户之间的FlexE交叉。需要说明的是，节点2此时作为PE设备，通过UNI接收到数据。
节点通过客户传输数据时需要一些时隙，这些时隙被分配在FlexE链路组中至少一个PHY上。FlexE交叉即时隙交叉，例如，在客户1对应的PHY中存在分配给客户1的n个时隙；在客户4对应的PHY中存在分配给客户4的m个时隙。节点1通过客户1占用的n个时隙从客户1对应的PHY接收数据，在向节点3转发该数据时，节点1根据客户1与客户4之间建立的FlexE交叉，通过客户4占用的m个时隙以及客户4对应的PHY向节点3转发该数据。
在缺省状态下，工作路径和保护路径均处于闭环状态，两个工作路径对应的客户之间存在FlexE交叉，两个保护路径对应的客户之间也存在FlexE交叉。例如，客户1与客户4之间存在FlexE交叉，如图4中节点1内的实线所示，数据可以从客户1的工作路径传输至客户4的工作路径，也可以从客户4的工作路径传输至客户1的工作路径。
当业务数据(即，待发送的信息)上环时，节点删除两个工作客户之间的FlexE交叉。例如，当业务数据在节点2上环后，节点2删除客户1与客户6之间的FlexE交叉。
图5示出了本申请提供的一种业务数据上环和下环方法的示意图。
节点2通过UNI获取业务数据后，进行上环处理，即，删除客户1与客户6之间的FlexE交叉，根据业务数据的目的地址选择一个传输路径发送业务数据。例如，业务数据的目的地址是节点3，则节点2可以选择“节点2→节点1→节点3”的传输路径，并通过客户1将业务数据发送至节点1。
节点1通过客户1对应的工作路径接收到该业务数据后，基于客户1与客户4之间的FlexE交叉，通过客户4将该业务数据发送出去。
节点3通过客户4对应的工作路径接收到该业务数据后，进行下环处理，即，删除客户4与客户6之间的FlexE交叉，通过节点3的UNI将该业务数据发送出去。
可以预先配置各个节点的上环客户和下环客户，例如，在上述示例中，可以配置节点2的上环客户和下环客户为：客户1；可以配置节点3的上环客户和下环客户为：客户4。
节点2通过UNI获取业务数据并且确定传输路径后，节点2可以业务数据对应的VLAN标识从多个客户中选择客户1发送业务数据，即，节点2作为发送端时客户1是上环客户；若节点2作为接收端通过客户1从其它节点接收到业务数据，则节点2可以对该业务数据进行下环处理，通过UNI将该业务数据发送出去，即，节点2作为接收端时客户1是下环客户。相应地，节点3通过客户4接收到业务数据后，根据预配置的上下环客户对业务数据进行下环处理。
需要说明的是，上述各个节点的上环客户和下环客户均是在节点2作为PE节点时的客户配置情况，若节点2不再作为PE节点，则各个节点的上环客户和下环客户需要重新配置，即，FlexE交叉环中各个节点的上环客户和下环客户的配置情况与PE节点是一一对应的。
此外，对于PE节点来说，可能存在多条开环的工作路径，但通常仅存在一条闭环的保护路径。例如，图5中，节点2作为PE节点被配置了两条工作路径：“节点2→节点1→节点3”以及“节点2→节点3”；节点2还配置了一个保护路径，即图5中虚线所示的闭环。
上文所描述的转发流程为FlexE交叉环的各条路径均正常工作时的数据转发流程。若节点1与节点3之间的FlexE链路组出现故障，节点1可以执行图6所示的方法完成数据转发。
如图6所示，该方法600包括：
S610，节点1确定链路组3发生故障。
节点1可以根据FlexE的操作管理维护(operation administration and maintenance，OAM)功能确定链路组3出现故障。
例如，节点1通过客户4向节点3发送OAM报文后，在N个周期内未收到该OAM报文的响应消息，则节点1确定链路组3出现故障。其中，该OAM报文用于检测节点之间的路径的连通性。
又例如，节点1在N个周期内未收到节点3发送的OAM报文，则节点1确定链路组3出现故障。
上述节点1确定节点1与节点3之间的工作路径和保护路径出现故障的方法仅是举例说明，本申请对节点1确定链路组3发生故障的具体方式不作限定。
S620，节点1删除客户1与客户4之间的FlexE交叉。
S630，节点1建立客户1与客户3之间的FlexE交叉。
上述转发流程如图7所示，节点2通过客户3的收到业务数据后，根据客户3与客户5之间的FlexE交叉，通过客户5将业务数据发送出去。节点3通过客户5接收到业务数据后，由于客户5是节点3预配置的下环客户，因此，节点3执行下环处理，删除客户5与客户2之间的FlexE交叉，通过节点3的UNI将业务数据发送出去。
由于FlexE交叉环中任意两个节点之间均存在两条路径(即，工作路径和保护路径)，因此，无论FlexE交叉环中哪一个链路组出现故障，FlexE交叉环中的节点都可以按照方法600完成业务数据的转发。例如，发送节点与接收节点之间的任意一个中间节点与接收节点之间的链路组出现故障后，该中间节点可以通过相邻两个节点之间的保护路径将业务数据回传至发送节点，并经由发送节点传输至接收节点，完成业务数据的转发。对于配置E2E保护路径的FlexE交叉环来说，其仅存在发送节点与接收节点之间的保护路径，若中间节点与接收节点之间的链路组出现故障，由于中间节点与发送节点之间没有保护路径，则中间节点无法将业务数据回传至发送节点，也就无法完成业务数据的转发。因此，本申请提供的FlexE交叉环和基于该FlexE交叉环的自动保护倒换方法提高了FlexE交叉环的可靠性。
图4至图7所描述的方案仅是举例说明，适用于本申请的FlexE交叉环还可以包括更多的节点。
图8是本申请提供的另一种FlexE交叉环的示意图。
网元(network element，NE)1、NE2、NE3、NE4、NE5和NE6构成一个FlexE交叉环，其中，NE1作为PE与客户设备(customer equipment，CE)1连接，NE4作为另一个PE与CE2连接。上述NE也可以被称为节点或网络设备。
在上述FlexE交叉环的各条路径均处于正常状态时，基站发出的业务数据通过NE1上环后，可以按照“NE1→NE2→NE3→NE4”的传输路径传输至NE4下环。
若NE3确定NE3与NE4之间的FlexE链路组出现故障，则NE3可以删除NE3的两 个工作客户之间的FlexE交叉，同时，建立NE3的工作客户与保护客户之间的FlexE交叉，将业务数据通过NE3与NE2之间的保护路径传输至NE2，NE2基于两个保护客户之间的FlexE交叉将业务数据通过NE2与NE1之间的保护路径传输至NE1。业务数据最终按照“NE1→NE2→NE3→NE2→NE1→NE6→NE5→NE4”的传输路径传输至NE4下环，该传输路径如图9所示。
应理解，图8所示的FlexE交叉环仅是举例说明，本申请提供的FlexE交叉环的应用场景不限于图8所示的场景。
例如，图8所示的FlexE交叉环还可以应用在第4代(4 th generation，4G)移动通信系统中，其中，CE1可以与4G移动通信系统中的基站(eNB)直接连接或者间接连接。图8所示的FlexE交叉环还可以应用在第5代(5 th generation，5G)移动通信系统中，其中，CE1可以与5G移动通信系统中的基站(gNB)直接连接或间接连接。
再例如，图8所示的FlexE交叉环还可以跨层网络架构中，其中，NE1可以与接入层设备连接，NE4可以与汇聚层设备或者核心层设备连接。
以上示例仅是举例说明，未来的通信系统同样适用于本申请所提供的FlexE交叉环。
本申请还提供了一种FlexE交叉环，该FlexE交叉环中每个节点具有多个工作路径和多个保护路径，该多个工作路径与该多个保护路径一一对应。
如图10所示，节点1包括两个物理端口(即，PHY)，分别为东向物理端口和西向物理端口。图10所示的节点1仅是举例说明，节点1还可以包含更多的物理端口。
东向物理端口对应6个客户，分别为客户1、客户3、客户7、客户8、客户9和客户10，其中，客户1、客户7和客户8为工作客户(即，与工作路径对应的客户)，客户3、客户8和客户10为保护客户(即，与保护路径对应的客户)。
西向物理端口对应6个客户，分别为客户2、客户4、客户11、客户12、客户13和客户14，其中，客户4、客户11和客户12为工作客户，客户2、客户13和客户14为保护客户。
东向物理端口的3个工作客户被配置为一个客户组(client group)，即，工作客户组1；西向物理端口的3个工作客户被配置为另一个客户组，即，工作客户组2。本申请中，客户组也可以称之为客户绑定组。东向物理端口的3个保护客户被配置为一个客户组，即，保护客户组1，西向物理端口的3个保护客户被配置为另一个客户组，即，保护客户组2。
上述客户组的示例仅是举例说明，本申请提供的客户组中客户的数量还可以是其它数量，例如，2个客户作为一个客户组，或者，更多个客户作为一个客户组。
类似地，也可以对节点2和节点3配置工作客户组和保护客户组。配置结果如图11和图12所示。
包含图10所示的节点1、图11所示的节点2以及图12所示的节点3的FlexE交叉环如图13所示。若节点1的西向物理端口对应的FlexE链路组出现故障，则节点1可以将删除西向物理端口与东向物理端口之间的FlexE交叉，并建立东向物理端口的工作客户组和保护客户组之间的FlexE交叉，将业务数据从东向物理端口的保护客户组发送出去。
由于节点1基于客户组对多个工作客户和多个保护客户进行一次FlexE交叉处理即可完成路径倒换，无需对各个工作客户和保护客户进行多次FlexE交叉处理，因此，基于客户组的FlexE交叉可以减少路径倒换的开销。
FlexE交叉环的故障处理结果如图14所示，节点3也相应地删除出现故障的客户组与正常客户组之间的FlexE交叉。
本领域技术人员可以清楚地认识到：图13和图14所示的FlexE交叉环和相应地故障处理方法能够应用于图8，图4或者本申请所描述的其它场景是显而易见的。
本申请还提供了一种检测FlexE交叉环的故障的方法，应用于如图13所示的包括客户组的FlexE交叉环中。该方法包括：
节点1通过工作客户4向节点3发送OAM报文，OAM报文用于检测节点1与节点3之间的FlexE链路组的连通性。
若节点1在N(N为正整数)个周期内未接收到上述OAM报文的响应消息，则节点1确定节点1与节点3之间的FlexE链路组出现故障，无需再通过客户11或者客户12发送OAM报文，从而减小了OAM报文开销。此外，由于无需在一个客户组中每个客户均配置OAM检测，因此，使用客户组的FlexE交叉环能够减小配置OAM的工作量。
上述方案仅是举例说明，节点1也可以根据N个周期内未接收到节点3发送的OAM报文确定西向物理端口的FlexE链路组出现故障。
OAM报文可以采用图15所示的报文格式。
图15中，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域)的完整性。
图15所示的编码格式仅是举例说明，本申请对OAM报文的编码格式不作限定，例如，还可以采用64B的编码格式对OAM报文进行编码。
上文详细介绍了本申请提供的通信方法的示例。可以理解的是，通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或 硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请可以根据上述方法示例对传输数据的装置进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图16示出了本申请提供的一种通信装置的示意图。
该通信装置1600可以应用于图4或图8所示的网络架构中，例如可以应用于图4所示的网络架构中的节点1或图8所示网络架构的NE1。通信装置1600可以包括处理器1610，与处理器1610耦合连接的存储器1620，通信接口1630。处理器1610可以是中央处理器(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)或其组合。处理器1610可以是指一个处理器，也可以包括多个处理器。存储器1620可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器1620也可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，闪存(flash)，硬盘驱动器(hard disk drive，HDD)或固态硬盘(solid state disk，SSD)；存储器1620还可以包括上述不同种类的存储器的组合。存储器1620可以是指一个存储器，也可以包括多个存储器。存储器1620中存储有计算机可读指令，所述计算机可读指令可以包括多个软件模块，例如发送模块1621，处理模块1622和接收模块1623。处理器1610运行上述各个软件模块后，可以按照各个软件模块的指示进行相应的操作。在本实施例中，一个软件模块所执行的操作实际上是指处理器1610根据所述软件模块的指示而执行的操作。例如，处理器1610运行处理模块1622后执行：
确定第三FlexE链路组发生故障；
删除第一客户与第三客户之间的FlexE交叉；
建立第一客户与第二客户之间的FlexE交叉。
处理器1610例如可以是图4所示的节点1中的处理器，第三FlexE链路组例如是图4所示的链路组3，第一客户例如是客户1，第三客户例如是客户4，第二客户例如是客户3。
处理器1610还可以在运行接收模块1623后执行：通过所述第一客户接收所述第二网络设备发送的第一FlexE数据；以及，在运行发送模块1623后执行：通过所述第二客户向所述第二网络设备转发所述第一FlexE数据。
所述第三FlexE链路组的链路故障排除后，处理器1610还可以在运行处理模块1622后执行：删除第一客户与第二客户之间的FlexE交叉；建立第一客户与第三客户之间的FlexE交叉。
处理器1610还可以在运行接收模块1623后执行：通过第一客户接收第二网络设备发送的第二FlexE数据；通过第三客户向第三网络设备转发第二FlexE数据。
第二网络设备例如可以是图4所示的节点2，第三网络设备例如可以是图4所示的节点3。
所述第三FlexE链路组用于承载至少两个客户，所述至少两个客户构成一个客户绑定组，该客户绑定组包括第三客户和第四客户，第三客户部署了OAM检测，第四客户没有部署OAM检测；处理器1610还可以在运行处理模块1622后执行：基于第三客户部署的OAM检测，确定第三FlexE链路组发生故障。
装置实施例和方法实施例中完全对应，方法实施例中的步骤由装置实施例中相应的模块执行，例如通信接口执行方法实施例中接收步骤和发送步骤，除发送接收外的其它步骤可以由处理器执行。具体模块的功能可以参考相应的方法实施例，不再详述。
在本申请各个实施例中，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请的实施过程构成任何限定。
另外，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (13)

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

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2021527214A JP7168286B2 (ja) 2018-11-21 2019-09-07 通信方法および通信装置
EP19888000.7A EP3873037A4 (en) 2018-11-21 2019-09-07 COMMUNICATION METHOD AND DEVICE
US17/325,033 US20210273826A1 (en) 2018-11-21 2021-05-19 Communication method and communications apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811394199.5 2018-11-21
CN201811394199.5A CN111211957B (zh) 2018-11-21 2018-11-21 通信方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/325,033 Continuation US20210273826A1 (en) 2018-11-21 2021-05-19 Communication method and communications apparatus

Publications (1)

Publication Number Publication Date
WO2020103530A1 true WO2020103530A1 (zh) 2020-05-28

Family

ID=70774587

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/104811 WO2020103530A1 (zh) 2018-11-21 2019-09-07 通信方法和装置

Country Status (5)

Country Link
US (1) US20210273826A1 (zh)
EP (1) EP3873037A4 (zh)
JP (1) JP7168286B2 (zh)
CN (1) CN111211957B (zh)
WO (1) WO2020103530A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3942750A1 (en) * 2019-03-20 2022-01-26 Telefonaktiebolaget LM Ericsson (publ) Routing flexe data in a network
CN112911420A (zh) * 2019-12-03 2021-06-04 中兴通讯股份有限公司 基于FlexE网络的重路由方法、电子设备和可读存储介质
CN114513454A (zh) * 2020-11-16 2022-05-17 华为技术有限公司 一种应用在城域传送网络mtn或分片分组网络spn中的通信方法及系统
CN112511382B (zh) * 2020-11-24 2022-03-29 中盈优创资讯科技有限公司 灵活以太网FlexE通道的创建方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106788921A (zh) * 2016-11-24 2017-05-31 上海华为技术有限公司 多cpe冗余链路系统及方法
CN107453905A (zh) * 2017-07-31 2017-12-08 烽火通信科技股份有限公司 一种灵活以太网1：1保护倒换实现方法
WO2018099161A1 (zh) * 2016-12-02 2018-06-07 华为技术有限公司 保护倒换方法、网络设备及系统
CN108243120A (zh) * 2016-12-26 2018-07-03 北京华为数字技术有限公司 基于灵活以太网的业务流传输方法、装置和通信系统

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030214962A1 (en) * 2002-05-15 2003-11-20 Mark Allaye-Chan Method and apparatus for bandwidth optimization in network ring topology
WO2006030435A2 (en) * 2004-09-16 2006-03-23 Alcatel Optical Networks Israel Ltd. Efficient protection mechanisms for protecting multicast traffic in a ring topology network utilizing label switching protocols
US7936680B2 (en) * 2005-12-08 2011-05-03 Nortel Networks Limited Method and apparatus for increasing the scalability of Ethernet OAM
US8085676B2 (en) * 2006-06-29 2011-12-27 Nortel Networks Limited Method and system for looping back traffic in QIQ ethernet rings and 1:1 protected PBT trunks
US20100238813A1 (en) 2006-06-29 2010-09-23 Nortel Networks Limited Q-in-Q Ethernet rings
US7768928B2 (en) * 2006-07-11 2010-08-03 Corrigent Systems Ltd. Connectivity fault management (CFM) in networks with link aggregation group connections
CN101710877B (zh) 2009-12-04 2012-02-15 华为技术有限公司 基于伪线的业务流量处理方法、设备和系统
JP5319787B2 (ja) 2009-12-28 2013-10-16 富士通株式会社 光転送リングネットワークの切替え方法及びノード装置
EP3113502B1 (en) * 2015-06-30 2018-08-15 Ciena Corporation Flexible ethernet systems and methods for switching, oam, multi-service, chip-to-chip interface, time transfer, and encryption
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
CN113300876B (zh) 2016-12-26 2022-09-02 华为技术有限公司 Dcn报文处理方法、网络设备和网络系统
CN108418753A (zh) * 2017-02-10 2018-08-17 中兴通讯股份有限公司 路径的建立方法及装置
CN111106964A (zh) * 2017-04-28 2020-05-05 华为技术有限公司 配置链路组的方法和设备
CN110383766B (zh) * 2017-06-27 2021-02-12 华为技术有限公司 保护倒换方法、设备及系统
CN109586864B (zh) * 2017-09-28 2021-01-15 华为技术有限公司 数据传输方法、装置及系统
JP7035877B2 (ja) * 2018-07-20 2022-03-15 富士通株式会社 伝送装置
CN111294226B (zh) * 2018-12-10 2023-05-09 华为技术有限公司 通信方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106788921A (zh) * 2016-11-24 2017-05-31 上海华为技术有限公司 多cpe冗余链路系统及方法
WO2018099161A1 (zh) * 2016-12-02 2018-06-07 华为技术有限公司 保护倒换方法、网络设备及系统
CN108243120A (zh) * 2016-12-26 2018-07-03 北京华为数字技术有限公司 基于灵活以太网的业务流传输方法、装置和通信系统
CN107453905A (zh) * 2017-07-31 2017-12-08 烽火通信科技股份有限公司 一种灵活以太网1：1保护倒换实现方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP3873037A4 (en) 2022-01-19
EP3873037A1 (en) 2021-09-01
CN111211957B (zh) 2021-10-01
US20210273826A1 (en) 2021-09-02
JP7168286B2 (ja) 2022-11-09
CN111211957A (zh) 2020-05-29
JP2022507745A (ja) 2022-01-18

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) 一种灵活以太网通信方法及网络设备
US20210385127A1 (en) Flexible ethernet communication method and network device
US11804982B2 (en) Communication method and apparatus
CN101170711A (zh) 自动交换光网络scn和mcn信息传递装置及方法
WO2006131019A1 (fr) Procede et site pour realiser l'agregation de liaison entre anneaux de paquet redondants interconnectes

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021527214

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

Country of ref document: EP

Effective date: 20210621