WO2019000241A1 - 保护倒换方法、设备及系统 - Google Patents

保护倒换方法、设备及系统 Download PDF

Info

Publication number
WO2019000241A1
WO2019000241A1 PCT/CN2017/090402 CN2017090402W WO2019000241A1 WO 2019000241 A1 WO2019000241 A1 WO 2019000241A1 CN 2017090402 W CN2017090402 W CN 2017090402W WO 2019000241 A1 WO2019000241 A1 WO 2019000241A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
link
protection
links
flexe
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/090402
Other languages
English (en)
French (fr)
Inventor
孙亮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2017/090402 priority Critical patent/WO2019000241A1/zh
Priority to CN201780087993.2A priority patent/CN110383766B/zh
Priority to EP17915619.5A priority patent/EP3618350B1/en
Publication of WO2019000241A1 publication Critical patent/WO2019000241A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/40—Bus networks
    • H04L12/40006—Architecture of a communication node
    • H04L12/40013—Details regarding a bus controller
    • 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
    • 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/40—Bus networks
    • 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
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0836—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability to enhance reliability, e.g. reduce downtime
    • 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
    • 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/40—Bus networks
    • H04L2012/40208—Bus networks characterized by the use of a particular bus standard
    • H04L2012/40215—Controller Area Network CAN

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a protection switching method, device, and system.
  • Flexible Ethernet is an improved Ethernet-based network.
  • FIG. 1 exemplarily shows a network architecture of FlexE.
  • a plurality of links are established between the first network device 11 and the second network device 12, and the links form a FlexE link group, and the links are used to carry at least one client service. More flexibility is achieved because a customer's business can be transmitted over multiple links.
  • the embodiment of the present application provides a protection switching method, device, and system, which are used to solve the problem that the entire FlexE link group stops working when a link in the FlexE link group is unavailable in the prior art.
  • the embodiment of the present application provides a protection switching method, where the method includes: determining, by the first network device, that at least one link in the primary FlexE link group is unavailable, and selecting m spares from the pre-configured backup link.
  • the link acts as a protection link, wherein the primary FlexE link group includes multiple links that are logically bundled, m is a positive integer, and m is less than or equal to the number of unavailable links in the primary FlexE link group;
  • the first network device sends a protection switching notification to the second network device, and replaces m unavailable links in the at least one unavailable link by using m protection links; the second network device uses m lines according to the protection switching notification.
  • the protection link replaces m unavailable links, wherein the m protection links and the m unavailable links are in one-to-one correspondence; the second network device sends a protection switching response to the first network device.
  • redundant backup of the link is implemented by providing a backup link for the link in the FlexE link group.
  • the backup link is selected as the protection link, and the protection link is used to replace the unavailable link, thereby avoiding the entire FlexE link caused by one link failure.
  • the problem of the group stopping work satisfies the application requirements of FlexE for protection switching.
  • the protection link belongs to the alternate FlexE link group.
  • the first network device/second network device replaces m unavailable links in the at least one unavailable link by using m protection links, including: for the first protection link in the m protection links, if the first The protection link belongs to the standby FlexE link group, and the first protection link is used to replace the first unavailable link, and the first network device/second network device connects the first unavailable link from the primary FlexE link group. Deleted and added the first protection link to the primary FlexE link group.
  • the protection link belongs to the primary FlexE link group.
  • the first network device/second network device replaces m unavailable links in the at least one unavailable link by using m protection links, including: for the second protection link in the m protection links, if the second The protection link belongs to the primary FlexE link group, and the second protection link is used to replace the second unavailable link, and the first network device/second network device configures the time slot of the second unavailable link, and configures To the second protection link.
  • the protection switching notification is a FlexE information frame
  • the target field of the FlexE information frame carries protection switching information
  • the protection switching information is used to indicate that the second network device replaces m unavailable links by using m protection links. road.
  • the transmission of protection switching information is achieved by extending the function of the target field in the FlexE information frame.
  • the method further includes: if it is determined that n links in the m unavailable links are restored to be available, the first network device sends a link recovery notification to the second network device, and adopts n pieces are restored to the available links to replace n protection links; the second network device replaces n protection links with n links to available links according to the link recovery notification, n is a positive integer, and n is less than or Equal to m; the second network device sends a link recovery response to the first network device.
  • the protection link is replaced by the link restored to the available link, so as to restore the standby link resource in time.
  • the method further includes: determining, by the first network device, that at least one link in the primary FlexE link group is unavailable, including: the first network device detecting the inclusion in the primary FlexE link group Whether the FlexE information frame sent by the second network device is correctly received on each link; the first network device determines, according to the detection result, whether each link included in the primary FlexE link group is available; and/or, the first network device receives a receiving status information sent by the second network device, where the receiving status information is used to indicate whether the second network device correctly receives the FlexE information frame sent by the first network device on each link included in the primary FlexE link group; The network device determines, according to the reception status information, whether each link included in the primary FlexE link group is available.
  • the method further includes: the first network device sends the first master-slave configuration information to the second network device, where the first master-slave configuration information is used to indicate the master-slave configured in the first network device The relationship is such that the second network device determines whether the master-slave relationship between the first network device and the second network device is correctly configured according to the first master-slave configuration information and the master-slave relationship configured in the second network device.
  • the second network device sends the second master-slave configuration information to the first network device, where the second master-slave configuration information is used to indicate the master-slave relationship configured in the second network device, so that the first network device is configured according to the second master-slave configuration
  • the information and the master-slave relationship configured in the first network device determine whether the master-slave relationship between the first network device and the second network device is correctly configured.
  • the master-slave relationship can be clarified between the two ends of the FlexE.
  • the master device selects the protection link and initiates a protection switching notification to simplify the process.
  • the embodiment of the present application provides a network device, which has the function of implementing the behavior of the first network device side or the second network device side in the foregoing method example.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the structure of the network device includes a processor and a communication interface, the processor being configured to support the network device to perform corresponding functions in the above methods.
  • the communication interface is used to support communication between a network device and other network devices.
  • the network device can also include a memory for coupling with the processor that holds program instructions and data necessary for the network device.
  • the embodiment of the present application provides a protection switching system, where the system includes the first network device and the second network device.
  • an embodiment of the present application provides a computer storage medium for storing computer software instructions used by the first network device and/or the second network device, which includes a program designed to perform the above aspects.
  • an embodiment of the present application provides a computer program product for performing the method of the first network device and/or the second network device side described in the foregoing aspect when the computer program product is executed.
  • redundant backup of the link is implemented by providing a backup link for the link in the FlexE link group.
  • the backup link is selected as the protection link, and the protection link is used to replace the unavailable link, thereby avoiding the entire FlexE link caused by one link failure.
  • the problem of the group stopping work satisfies the application requirements of FlexE for protection switching.
  • FIG. 1 is a network architecture of a FlexE exemplarily shown
  • FIG. 2 is a schematic diagram showing a protection switching that is exemplarily shown
  • FIG. 3 is a flowchart of a protection switching method provided by an embodiment of the present application.
  • FIG. 5A is a schematic diagram showing protection switching when the link from the primary end to the secondary direction is exemplarily shown
  • 5B is a flow chart of protection switching when the link from the primary end to the secondary direction is exemplarily shown;
  • 6A is a schematic diagram showing protection switching when a link from the end to the primary direction is exemplarily shown
  • 6B is a flow chart of protection switching when the link from the end to the primary direction is exemplarily shown;
  • Figure 7 is a flow chart of an exemplary illustrated link recovery process
  • FIG. 8 is a flowchart of a protection switching method provided by another embodiment of the present application.
  • FIG. 9 is a schematic diagram of an application scenario exemplarily shown.
  • FIG. 10 is a schematic diagram of another application scenario exemplarily shown.
  • FIG. 11 is a schematic diagram of still another application scenario exemplarily shown.
  • FIG. 12A is a schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 12B is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • the technical solution provided by the embodiment of the present application can be applied to the network architecture of a FlexE shown in FIG. 1.
  • the network architecture includes a first network device 11 and a second network device 12.
  • the network device (eg, the first network device 11, the second network device 12, etc.) may be a device having a data transceiving function, such as a router, a switch, a data storage device, or the like.
  • each FlexE link group includes a plurality of links that are logically bundled.
  • the so-called logical bundling means that multiple links are grouped together to form a For a FlexE link group, there may be no physical connection between the multiple links. Therefore, multiple links in the FlexE link group can be physically independent.
  • the link involved in the embodiment of the present application may be an Ethernet physical link, such as an optical fiber.
  • the FlexE network device can identify the links in a FlexE link group by the number of the link to implement logical bundling of multiple links. For example, the number of each link can be identified by a number between 1 and 254, with 0 and 255 being reserved numbers. The number of a link can correspond to a port on a network device. Both ends of the first network device 11 and the second network device 12 need to use the same number to identify the same link. The number of each link included in a FlexE link group does not have to be contiguous. There are one or more FlexE link groups between the two network devices. One link can be used to carry at least one customer service, and one customer service can be transmitted on at least one link. In the FlexE standard, customer business can be called a Client.
  • the main FlexE link group 1 includes four links, which are respectively recorded as PG1: PHY1, PG1: PHY2, PG1: PHY3, and PG1: PHY4.
  • the main FlexE link group 2 includes two links, which are respectively recorded as PG2: PHY1 and PG2: PHY2.
  • the standby FlexE link group includes two links, which are denoted as Spare PHY1 and Spare PHY2, respectively.
  • FIG. 3 is a flowchart of a protection switching method provided by an embodiment of the present application.
  • the method can include the following steps.
  • Step 301 The first network device determines that at least one link in the primary FlexE link group is unavailable, and selects m standby links from the pre-configured backup link as the protection link, where m is a positive integer, and m is less than or equal to the number of unavailable links in the primary FlexE link group.
  • the primary FlexE link group includes multiple links that are logically bundled.
  • the primary FlexE link group 1 shown in FIG. 2 includes four links, and the primary FlexE link group 2 includes two links.
  • the alternate link refers to a redundant link used to replace the above unavailable link when the link in the primary FlexE link group is unavailable.
  • the total number of pre-configured alternate links can be determined based on actual needs. For example, when a strong protection switching function needs to be provided, a larger number of backup links are pre-configured.
  • the pre-configured alternate link does not belong to any of the primary FlexE link groups.
  • the pre-configured alternate link belongs to the alternate FlexE link group.
  • Any of the alternate FlexE link groups can be used to provide protection switching for any of the primary FlexE link groups.
  • the alternate FlexE link group shown in Figure 2 includes two links, denoted Spare PHY1 and Spare PHY2, respectively.
  • Spare PHY1 can be used to provide protection switching for any of the main FlexE link group 1 and the main FlexE link group 2.
  • Spare PHY2 can be used for the main FlexE link group 1 and the main FlexE chain. Any one of the links 2 provides protection switching.
  • the alternate link is pre-configured in the primary FlexE link group.
  • the alternate link pre-configured in a primary FlexE link group is used only to protect any link in the primary FlexE link group to which it belongs. It can not be used to provide protection switching for links in other active FlexE link groups. For example, as shown in FIG. 4, it is assumed that there are two active FlexE link groups between the first network device and the second network device.
  • the primary FlexE link group 1 includes six links, four of which are primary links and two are used.
  • the above four main links are respectively recorded as PG1: PHY1, PG1: PHY2, PG1: PHY3, and PG1: PHY4, and the above two alternate links are respectively recorded as PG1: Spare PHY1 and PG1: Spare PHY2.
  • the main FlexE link group 2 includes two links, which are respectively recorded as PG2: PHY1 and PG2: PHY2, and the above two links are all active links, and the primary FlexE link group 2 does not include the backup link. .
  • PG1: Spare PHY1 can be used to provide protection switching for any primary link in the main FlexE link group 1.
  • PG1: Spare PHY2 can be used for any primary link in the main FlexE link group 1.
  • the road provides protection switching.
  • neither PG1: Spare PHY1 nor PG1: Spare PHY2 can be used to provide protection switching for links in the main FlexE link group 2.
  • the protection link is selected from the available alternate links.
  • the alternate link to be selected refers to an alternate link that belongs to the standby FlexE link group and/or belongs to the same primary FlexE link group as the unavailable link and is not used.
  • the first network device determines that n links in the primary FlexE link group are unavailable, n is a positive integer, and the number of pre-configured alternative backup links is p, and p is a positive integer. If p is greater than or equal to n, the first network device may select at most n protection links, that is, the maximum value of m is n, thereby providing protection switching for all links in the n unavailable links; If p is less than n, the first network device may select at most p protection links, that is, the maximum value of m is p, thereby providing protection switching for some of the n unavailable links.
  • the unavailable link may be a link that has been allocated for use by the customer's service, or a link that is not allocated for use by the customer's service.
  • the situation in which the link is unavailable may be that the link is faulty.
  • the embodiment of the present application does not limit other possible situations that cause the link to be unavailable. For example, during the test or maintenance process, the link is configured to be switched from the available state to the unavailable state.
  • Step 302 The first network device sends a protection switching notification to the second network device.
  • the protection switching notification is used to instruct the second network device to replace the m unavailable links in the at least one unavailable link by using m protection links.
  • the m protection links and the m unavailable links are in one-to-one correspondence, that is, one protection link is used to replace one unavailable link.
  • the protection switching notification indicates a correspondence between the protection link and the unavailable link, that is, which protection link is used to replace which one is unavailable.
  • the first network device can send a protection switching notification to the second network device over any one or more of the available FlexE links.
  • the above-mentioned available FlexE link may be a link that is not faulty in the primary FlexE link group, or may be a backup link, such as a protection link.
  • the first network device and the second network device further have a communication channel other than the FlexE link, and the first network device may also send the protection to the second network device by using the other communication channel. Switching notice.
  • the foregoing other communication channels include, but are not limited to, an Ethernet channel, an optical transmission network channel, and the like, which are not limited in this embodiment of the present application.
  • the protection switching notification is a FlexE information frame.
  • the target field of the FlexE information frame carries protection switching information, and the protection switching information is used to indicate that the second network device replaces m unavailable links by using m protection links.
  • the packets transmitted by the two ends of the FlexE (such as the first network device and the second network device in the embodiment of the present application) on the FlexE link may be referred to as FlexE information frames, and the FlexE information frames may be FlexE overhead frames or FlexE management. frame. Called FlexE Overhead Frame and FlexE Multiframe in the FlexE standard.
  • the FlexE information frame includes FlexE Group Number, PHY Map, PHY Number, Client Calendar, Reserved, Management Channel-Section, Management Channel-Shim to Shim and other fields.
  • the FlexE Group Number field is used to indicate the number of the FlexE link group
  • the PHY Map field is used to indicate the link included in the FlexE link group
  • the PHY Number field is used to indicate the number of the link in the FlexE link group
  • Client The Calendar field may be referred to as a time slot allocation table for indicating the allocation relationship between the time slot and the client service.
  • the Reserved field is a reserved field
  • the Management Channel field is used to indicate management information related to the FlexE link group.
  • the target field may be a Management Channel-Section field or a Reserved field, which is not limited in this embodiment of the present application.
  • Step 303 The first network device replaces m unavailable links by using m protection links.
  • the first network device replaces one of the m protection links.
  • the first network device For the first protection link of the foregoing m protection links, if the first protection link belongs to the standby FlexE link group, and the first protection link is used to replace the first unavailable link, the first network device will The first unavailable link is removed from the primary FlexE link group and the first protection link is added to the primary FlexE link group. The first protection link is one of the m protection links, and the first unavailable link is one of the m unavailable links. The first network device deletes the first unavailable link from the primary FlexE link group, that is, releases the association between the first unavailable link and the primary FlexE link group. The first network device adds the first protection link to the active FlexE link group, that is, creates an association relationship between the first protection link and the primary FlexE link group.
  • the first network device replaces PG1: PHY2 with Spare PHY1, and the replacement process may include the following steps:
  • the first network device uses the configuration information of PG1: PHY2 to configure (1) configure the FlexE Group Number of Spare PHY1; (2) configure the PHY Map of Spare PHY1; (3) configure the PHY Number of Spare PHY1; (4) configure Spare PHY1's Client Calendar; (5) Create a relationship between Spare PHY1 and the primary FlexE link group 1.
  • the method further includes the following step 4:
  • the first network device uses the configuration information of Spare PHY1 to configure: (1) configure PG1: FlexE Group Number of PHY2; (2) configure PHY1 of PG1: PHY2; (3) configure PHY Number of PG1: PHY2; (4) ) Create an association between PG1: PHY2 and the alternate FlexE link group.
  • the time slot configuration of the second unavailable link is configured to the second protection link.
  • the second protection link is one of the m protection links
  • the second unavailable link is one of the m unavailable links.
  • the slot configuration includes but is not limited to: slot division, configuration of slot state, configuration of assignment relationship between client service and slot.
  • the slot states include an unavailable state, a used state, and an unused state.
  • the unavailable state indicates that the time slot cannot be allocated for use by the customer.
  • the used state indicates that the time slot has been assigned to customer service usage.
  • the unused state indicates that the time slot can be assigned to the customer service Used, and has not been assigned to customer business for the time being.
  • the first network device replaces PG1: PHY2 with PG1: Spare PHY1, and the first network device configures the time slot configuration of PG1: PHY2 to PG1: Spare PHY1. For example, if the status of a certain time slot on PG1: PHY2 is used, then PG1 is configured: the corresponding time slot on Spare PHY1 changes from the unavailable state to the used state.
  • PG1 For another example, if a time slot on PG1:PHY2 is allocated for use by client service 1, then PG1 is configured: the corresponding time slot on Spare PHY1 is allocated for use by client service 1. In addition, the first network device also configures all time slots on PG1: PHY2 to be unavailable.
  • Step 304 The second network device replaces m unavailable links by using m protection links according to the protection switching notification.
  • the second network device After receiving the protection switching notification sent by the first network device, the second network device replaces the m unavailable links by using m protection links according to the protection switching notification.
  • the second network device will be the first An unavailable link is removed from the primary FlexE link group and the first protection link is added to the primary FlexE link group.
  • the second network device For the second protection link in the m protection links, if the second protection link belongs to the primary FlexE link group, and the second protection link is used to replace the second unavailable link, the second network device will The time slot configuration of the second unavailable link is configured to the second protection link.
  • the specific operation procedure of the second network device adopting the protection link to replace the unavailable link is the same as the specific operation procedure of the first network device introduced in step 303.
  • Step 305 The second network device sends a protection switching response to the first network device.
  • the protection switching response is used to indicate that the second network device has completed the link replacement according to the protection switching notification.
  • the second network device can send a protection switching response to the first network device over any one or more of the available FlexE links.
  • the above-mentioned available FlexE link may be a link that is not faulty in the primary FlexE link group, or may be a backup link, such as a protection link.
  • the first network device and the second network device further have a communication channel other than the FlexE link, and the second network device may also send the protection to the first network device by using the other communication channel. Switch the response.
  • the foregoing other communication channels include, but are not limited to, an Ethernet channel, an optical transmission network channel, and the like, which are not limited in this embodiment of the present application.
  • the first network device will transmit the customer on the unavailable link after receiving the protection switching response.
  • the service is switched to a corresponding one of the protection links; if the unavailable link is not allocated for use by the client service, the switching of the above-mentioned client service is not required.
  • redundant backup of the link is implemented by providing a backup link for the link in the FlexE link group.
  • the backup link is selected as the protection link, and the protection link is used to replace the unavailable link, thereby avoiding the entire FlexE link caused by one link failure.
  • the problem of the group stopping work satisfies the application requirements of FlexE for protection switching.
  • the specific process for the first network device to select the protection link may be as follows:
  • the first network device determines that a link is unavailable in a certain primary FlexE link group, if the primary FlexE link group is not pre-configured with the standby link or the primary FlexE link group does not exist, Alternative alternate link, and spare If there is an alternate link to be selected in the FlexE link group, the first network device selects b alternate links from the standby FlexE link group as the protection link; where a and b are positive integers, and b is smaller than Or equal to a. Assume that the number of alternate links available in the alternate FlexE link group is c, and c is a positive integer.
  • the first network device may select a protection link at most, that is, provide protection switching for all links in the above a unavailable links; if c is smaller than a, the first network device A maximum of c protection links can be selected, that is, protection switching is provided for some links in the above a unavailable links.
  • the first network device determines that a link is unavailable in a certain primary FlexE link group, if there is an alternate link available in the primary FlexE link group, the spare FlexE link group does not exist. If the alternate link is available or the spare FlexE link group is not pre-configured, the first network device selects b alternate links from the primary FlexE link group as the protection link; wherein a and b are positive An integer, and b is less than or equal to a. Assume that the number of alternate links that can be selected in the above-mentioned primary FlexE link group is c, and c is a positive integer.
  • the first network device may select a protection link at most, that is, provide protection switching for all links in the above a unavailable links; if c is smaller than a, the first network device A maximum of c protection links can be selected, that is, protection switching is provided for some links in the above a unavailable links.
  • the first network device determines that a link is unavailable in a certain primary FlexE link group, if there is an alternate link available in the primary FlexE link group, and the spare FlexE link group also exists For the alternate link to be selected, the first network device selects b alternate links as the protection link from the primary FlexE link group and/or the standby FlexE link group; wherein a and b are positive integers And b is less than or equal to a. Assume that the total number of alternative backup links in the primary FlexE link group and the standby FlexE link group is c, and c is a positive integer.
  • the first network device may select a protection link at most, that is, provide protection switching for all links in the above a unavailable links; if c is smaller than a, the first network device A maximum of c protection links can be selected, that is, protection switching is provided for some links in the above a unavailable links.
  • the first network device preferentially selects a protection link from the primary FlexE link group.
  • the first network device selects a protection link and initiates a protection switching notification as an example.
  • the primary and secondary devices can negotiate the master-slave relationship between the two devices at the same time.
  • the master device selects the protection link and initiates protection switching notification.
  • the negotiation process of the master-slave relationship includes the following two parts:
  • the first network device sends the first master-slave configuration information to the second network device, where the first master-slave configuration information is used to indicate the master-slave relationship configured in the first network device.
  • the second network device determines a master-slave relationship between the first network device and the second network device according to the first master-slave configuration information and the master-slave relationship configured in the second network device. Is it configured correctly?
  • the second network device sends the second master-slave configuration information to the first network device, where the second master-slave configuration information is used to indicate the master-slave relationship configured in the second network device.
  • the first network device determines a master-slave relationship between the first network device and the second network device according to the second master-slave configuration information and the master-slave relationship configured in the first network device Is it configured correctly?
  • the master-slave relationship between the first network device and the second network device may be that the first network device is a master device, the second network device is a slave device, or the first network device is a slave device, The second network device is the master device.
  • the above-mentioned master-slave relationship can be configured by the user in the first network device and the second network device, and can be changed according to actual needs.
  • the foregoing master-slave configuration information may be sent when the master-slave relationship is initially configured or reconfigured, or may be sent once every preset time interval.
  • the preset time intervals of two adjacent times may be the same or different.
  • the foregoing master-slave configuration information is carried in a FlexE information frame.
  • the master-slave configuration information is carried in the target field of the FlexE information frame.
  • the target field may be the Management Channel-Section field, or the Reserved field, which is described above, which is not limited in this embodiment of the present application.
  • the foregoing master-slave configuration information may be carried in the first FlexE information frame sent after the initial configuration or reconfiguration of the master-slave relationship, or may be carried in each FlexE information frame.
  • the master-slave configuration information is carried in the Management Channel-Section field of each FlexE overhead frame.
  • the master-slave relationship can be clarified between the first network device and the second network device.
  • the primary device selects the protection link and initiates a protection switching notification to simplify the process.
  • an alarm information may be sent, where the alarm information is used to indicate that the master-slave relationship configuration is inaccurate.
  • the first network device determines whether a link is unavailable in the active FlexE link group in the following manner.
  • the first network device itself detects whether a link is unavailable.
  • the first network device detects whether the FlexE information frame sent by the second network device is correctly received on each link included in the primary FlexE link group, and determines whether each link included in the primary FlexE link group is available according to the detection result. .
  • the first network device If the first network device correctly receives the FlexE information frame sent by the second network device on a certain link, determining that the link is available; if the first network device does not correctly receive the second network device sent on a certain link
  • the FlexE info frame determines that the link is not available. For example, the FlexE overhead frame is usually sent once at 104.77 us. If the first network device fails to receive the FlexE overhead frame sent by the second network device on a certain timeout, the first network device determines that the link is unavailable. Alternatively, if the first network device receives the FlexE information frame sent by the second network device on a certain link, but the received signal strength is less than a preset threshold, the first network device may also determine that the link is unavailable. .
  • the first network device sends, to the second network device, the receiving state information, where the receiving state information is used to indicate that the first network device is on each link included in the active FlexE link group. Whether the FlexE information frame sent by the second network device is correctly received.
  • the first network device determines, according to the received status information fed back by the second network device, whether a link is unavailable.
  • the second network device detects by itself whether the link is unavailable (in the manner described above), and then sends the receiving status information to the first network device, where the receiving status information is used to indicate that the second network device is in the primary FlexE link. Whether the FlexE information frame sent by the first network device is correctly received on each link included in the group. Then, the first network device determines, according to the received reception status information, whether each link included in the primary FlexE link group is available.
  • the link between the first network device and the second network device is bidirectional.
  • the first network device can detect whether the link from the peer end to the local end is available.
  • the second network device can also detect the peer end to the local end. Whether the direction link is available.
  • the link states indicated in the receive status information include a Normal state, a signal failure (SF) state, and a signal degradation (SD) state.
  • the Normal state indicates that the link is available, and both the SF state and the SD state indicate that the link is unavailable.
  • the SF state means that the peer signal cannot be detected, such as the FlexE information frame that cannot be received by the peer end; the SD state refers to the ability to detect the peer signal, but the signal strength is relatively high. Low, such as the ability to receive the FlexE message frame sent by the peer, but there is a bit error.
  • the links in the SF state and the SD state are all unavailable links and need to be replaced by the protection link.
  • the link in the SF state is preferentially replaced.
  • the foregoing receiving status information is carried in a FlexE information frame.
  • the receiving status information is carried in the target field of the FlexE information frame.
  • the target field may be the Management Channel-Section field, or the Reserved field, which is described above, which is not limited in this embodiment of the present application.
  • the foregoing reception status information may be sent when the link status changes, or may be carried in each FlexE information frame.
  • the receiving status information is carried in the Management Channel-Section field of each FlexE overhead frame.
  • the target field (such as the Management Channel-Section field) in the FlexE information frame is extended to carry the reception status information, the master-slave indication information, or the switching action information.
  • the switching action information may be the protection switching information and the protection switching response described above, or may be the link recovery information and the link recovery response described below.
  • the transmission timings in Table-1 and Table-2 above are “always” indicating that they are carried in each FlexE information frame, and the delivery timing is “switching", which means that it is carried in a certain FlexE information frame that is sent when the switching needs to be performed. .
  • the direction from the master device to the slave device may not be available, or the direction from the end device to the master device may not be available.
  • the first network device is the primary device
  • the second network device is the secondary device.
  • the PG1 PHY2 link in the primary FlexE link group 1
  • the primary device is The direction of the slave device is not available.
  • the corresponding protection switching process is as follows:
  • Step 51 The second network device sends, to the first network device, the receiving state information, where the receiving state information indicates that PG1: PHY2 is an SF state.
  • Step 52 The first network device selects Spare PHY1 as a protection link from the pre-configured backup link.
  • Step 53 The first network device sends a protection switching notification to the second network device, where the protection switching notification is used to indicate that the second network device replaces PG1: PHY2 by using Spare PHY1;
  • Step 54 the first network device replaces PG1: PHY2 with Spare PHY1;
  • Step 55 the second network device replaces PG1: PHY2 with Spare PHY1 according to the protection switching notification;
  • Step 56 The second network device sends a protection switching response to the first network device.
  • the first network device is the master device, and the second network device is the slave device.
  • the PG1 PHY2 link in the primary FlexE link group 1
  • the slave device is The direction of the primary device is unavailable.
  • the corresponding protection switching process is as follows:
  • Step 61 The first network device detects that PG1: PHY2 is unavailable;
  • Step 62 The first network device sends, to the second network device, the receiving status information, where the receiving status information indicates that PG1: PHY2 is an SF status.
  • Step 63 The first network device selects Spare PHY1 as a protection link from the pre-configured backup link.
  • Step 64 The first network device sends a protection switching notification to the second network device, where the protection switching notification is used to indicate that the second network device replaces PG1: PHY2 by using Spare PHY1;
  • Step 65 the first network device replaces PG1: PHY2 with Spare PHY1;
  • Step 66 the second network device replaces PG1: PHY2 with Spare PHY1 according to the protection switching notification;
  • Step 67 The second network device sends a protection switching response to the first network device.
  • Step 306 If the first network device determines that n links in the m unavailable links are restored to be available, the first network device sends a link recovery notification to the second network device, where n is a positive integer, and n is less than or Equal to m.
  • the first network device may determine whether the unavailable link is available or not according to the self-detection manner described above or according to the received status information sent by the second network device.
  • the link recovery notification is used to instruct the second network device to replace n protection links with n links restored to available links.
  • the n links are restored to the available link and the n protection links are in one-to-one correspondence, that is, one link is restored to the available link for replacing one protection link.
  • the link recovery notification indicates that the relationship between the restored link and the protection link is restored, that is, which one of the protection links is replaced by the available link.
  • the first network device may send a protection switching notification to the second network device over any one or more of the available FlexE links.
  • the above-mentioned available FlexE link may be a link that is not faulty in the primary FlexE link group, such as a link that is restored to an available link, a protection link, or other backup link.
  • the first network device may also send a link recovery notification to the second network device through other communication channels.
  • the foregoing other communication channels include, but are not limited to, an Ethernet channel, an optical transmission network channel, and the like, which are not limited in this embodiment of the present application.
  • the link recovery notification is a FlexE information frame.
  • the target field of the FlexE information frame carries link recovery information, and the link recovery information is used to indicate that the second network device replaces n protection links by using n links to the available links.
  • the above target field can be Management Channel-Section
  • the field may also be a Reserved field, which is not limited in this embodiment of the present application.
  • Step 307 The first network device replaces n protection links with n links restored to available links.
  • the first network device For each of the n protection links, the first network device replaces one of the above-mentioned n links to the available links.
  • the first network device For the first protection link of the foregoing n protection links, if the first protection link belongs to the standby FlexE link group, and the first protection link is replaced by the first protection link, the first network device will be the first The protection link is removed from the primary FlexE link group and the first recovery link is added to the primary FlexE link group. The first recovery link is one of the above n links restored to the available link. The first network device deletes the first protection link from the primary FlexE link group, that is, releases the association between the first protection link and the active FlexE link group. The first network device adds the first recovery link to the active FlexE link group, that is, creates an association relationship between the first recovery link and the primary FlexE link group.
  • the first network device replaces Spare PHY1 with PG1: PHY2.
  • the replacement process is the same as the replacement process described above for replacing the unavailable link with the protection link, and details are not described herein again.
  • the first network device will be the first The time slot configuration of the second protection link is configured to the second recovery link.
  • the second recovery link is one of the above n links restored to the available link.
  • the first network device replaces PG1: Spare PHY1 with PG1: PHY2.
  • the replacement process is the same as the replacement process described above for replacing the unavailable link with the protection link, and details are not described herein again.
  • Step 308 The second network device replaces n protection links with n links to available links according to the link recovery notification.
  • the second network device After receiving the link recovery notification sent by the first network device, the second network device replaces n protection links with n links to available links according to the link recovery notification.
  • the specific operation procedure of the second network device to replace the protection link with the link that is available to be restored is the same as the specific operation procedure of the first network device introduced in step 307. For details, refer to the description in step 307, and details are not described herein again.
  • Step 309 The second network device sends a link recovery response to the first network device.
  • the link recovery response is used to indicate that the second network device has completed the link replacement according to the link recovery notification.
  • the second network device can send a link recovery response to the first network device over any one or more of the available FlexE links.
  • the above-mentioned available FlexE link may be a link that is not faulty in the primary FlexE link group, such as a link that is restored to an available link, a protection link, or other backup link.
  • the second network device may also send a link recovery response to the first network device through the other communication channel.
  • the foregoing other communication channels include, but are not limited to, an Ethernet channel, an optical transmission network channel, and the like, which are not limited in this embodiment of the present application.
  • the first network device may send a protection switching notification to the second network device over any one or more of the available FlexE links.
  • the above-mentioned available FlexE link may be a link that is not faulty in the primary FlexE link group, such as a link that is restored to an available link, a protection link, or other backup link.
  • the first network device may also send a link recovery notification to the second network device through other communication channels.
  • the foregoing other communication channels include, but are not limited to, an Ethernet channel, an optical transmission network channel, and the like, which are not limited in this embodiment of the present application.
  • the protection link is replaced by the link that is restored to the available link, so as to restore the standby link resource in time.
  • the non-recovery mode may also be used, that is, the unavailable link becomes the standby link after being replaced by the protected link, and does not need to be executed after the unavailable link is restored to be available.
  • any one of the primary FlexE link groups when the first network device determines that the link is unavailable (ie, the link is an unavailable link), Perform the following steps to protect the unavailable link.
  • Step 801 When determining, by the first network device, that any link in the active FlexE link group is unavailable, selecting a backup link from the pre-configured backup link as the protection link;
  • the protection switching scenario shown in FIG. 2 is taken as an example.
  • Spare PHY1 is selected as the protection link from the standby FlexE link group.
  • Step 802 The first network device sends a protection switching notification to the second network device by using the protection link.
  • the first network device sends a FlexE information frame to the second network device by using the Spare PHY1, where the Management Channel-Section field of the FlexE information frame carries protection switching information.
  • the protection switching information is used to instruct the second network device to replace the PG1: PHY2 with the Spare PHY1.
  • the protection switching information carries the number of the PG1: PHY2 and the indication information for protecting the switching action.
  • Step 803 The first network device replaces the unavailable link by using a protection link.
  • the first network device removes PG1:PHY2 from the primary FlexE link group 1, removes Spare PHY1 from the standby FlexE link group, and then adds Spare PHY1 to the primary FlexE link group 1.
  • the first network device also adds PG1: PHY2 to the alternate FlexE link group.
  • Step 804 The second network device replaces the unavailable link by using the protection link according to the protection switching notification.
  • the second network device After receiving the protection switching notification, the second network device deletes PG1:PHY2 from the primary FlexE link group 1 according to the protection switching notification, removes Spare PHY1 from the standby FlexE link group, and then adds Spare PHY1 to The main FlexE link is in group 1.
  • the second network device also adds PG1:PHY2 to the alternate FlexE link group.
  • Step 805 The second network device sends a protection switching response to the first network device by using the protection link.
  • the FlexE information frame is sent to the first network device by the Spare PHY1, and the protection channel-Section field of the FlexE information frame carries a protection switching response.
  • the embodiment further includes the following steps:
  • Step 806 After determining that the unavailable link is restored to be available, the first network device sends a link recovery notification to the second network device by using the protection link.
  • the first network device sends a FlexE information frame to the second network device by using the Spare PHY1 after determining that PG1: PHY2 is restored from being unavailable to available, and the link recovery information is carried in the Management Channel-Section field of the FlexE information frame.
  • the link recovery information is used to indicate that the second network device replaces the Spare PHY1 with PG1: PHY2, for example, the link recovery information carries the number of the PG1: PHY2 and the indication information of the link recovery action.
  • Step 807 the first network device replaces the protection link with a link that is restored to an available state
  • the first network device removes the Spare PHY1 from the primary FlexE link group 1 and then restores to the available PG1: PHY2 is added to the primary FlexE link group 1 and Spare PHY1 is added to the alternate FlexE link group .
  • Step 808 The second network device replaces the protection link by using a link that is restored to an available link according to the link recovery notification.
  • the second network device After receiving the link recovery notification, the second network device deletes the Spare PHY1 from the primary FlexE link group 1 according to the link recovery notification, and then restores to the available PG1: PHY2 is added to the active FlexE link group. In 1, add Spare PHY1 to the alternate FlexE link group.
  • Step 809 The second network device sends a link recovery response to the first network device by using the protection link.
  • the FlexE information frame is sent to the first network device by the Spare PHY1, and the Management Channel-Section field of the FlexE information frame carries a link recovery response.
  • the link recovery notification and the link recovery response are sent through the protection link as an example.
  • the link recovery notification and the link recovery response may also be sent by reverting to an available link.
  • the protection link can be selected in the manner provided in this embodiment, and the protection link is protected by the protection link.
  • two data devices are directly connected through a FlexE interface, wherein data device 1 serves as a master device and data device 2 functions as a slave device.
  • the main FlexE link group 1 is included, and the main FlexE link group 1 includes four links.
  • a spare FlexE link group is also included, and the standby FlexE link group includes two standby links.
  • PG1:PHY2 in the primary FlexE link group 1 is not available, Spare PHY1 in the standby FlexE link group is used as the protection link, replacing PG1:PHY2.
  • the transport network device restores the FlexE signal to the FlexE Client level for transmission.
  • Two protection groups (protection group 1 and protection group 2 as shown in the figure) are respectively configured on the two ends of the access transport network, and the FlexE interface between the data device and the transport device is protected by the protection group.
  • the configuration of the two protection groups is independent of each other.
  • the protection group 1 includes a data device 1 as a master device and a transmission device 1 as a slave device. Between the data device 1 and the transmitting device 1 includes a primary FlexE link group 1, which includes four links in the primary FlexE link group 1. Also included between the data device 1 and the transmitting device 1 is a spare FlexE link group 1, which includes 2 spare links in the standby FlexE link group 1. Illustratively, when PG1:PHY2 in the primary FlexE link group 1 is not available, the Spare PHY1 in the spare FlexE link group 1 is used as the protection link, replacing PG1: PHY2.
  • the protection group 2 includes a transmission device 2 and a data device 2, wherein the transmission device 2 and the data device 2 include an active FlexE link group 2, and the main FlexE link group 2 includes five links. Between the transmitting device 2 and the data device 2, a spare FlexE link group 2 is also included, and the standby FlexE link group 2 includes three standby links.
  • the transport network device (such as the transport device 1 and the transport device 2 in the figure) transmits the overhead and payload of the FlexE.
  • Two protection groups (protection group 1 and protection group 2 as shown in the figure) are respectively configured on the two ends of the access transport network, and the FlexE interface between the data device and the transport device is protected by the protection group.
  • the configuration of the two protection groups is independent of each other.
  • the protection group 1 includes a data device 1 and a transmission device 1, wherein the data device 1 serves as a primary end.
  • the device, the transmitting device 2 acts as a slave device.
  • Between the data device 1 and the transmitting device 1 includes a primary FlexE link group 1, which includes four links in the primary FlexE link group 1.
  • Also included between the data device 1 and the transmitting device 1 is a spare FlexE link group 1, which includes 2 spare links in the standby FlexE link group 1.
  • PG1:PHY2 in the primary FlexE link group 1 is not available, the Spare PHY1 in the spare FlexE link group 1 is used as the protection link, replacing PG1: PHY2.
  • the protection group 2 includes a transmission device 2 and a data device 2, wherein the transmission device 2 and the data device 2 include an active FlexE link group 2, and the main FlexE link group 2 includes four links. Between the transmitting device 2 and the data device 2, a spare FlexE link group 2 is also included, and the standby FlexE link group 2 includes three standby links.
  • the solution provided by the embodiment of the present application is introduced from the perspective of interaction between the first network device and the second network device.
  • the network device for example, the first network device, the second network device
  • the network device includes corresponding hardware structures and/or software modules for performing the respective functions in order to implement the above functions.
  • the embodiments of the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements of the examples and algorithm steps described in the embodiments disclosed in the application. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.
  • the embodiments of the present application may perform functional unit division on a network device (for example, a first network device and a second network device) according to the foregoing method example.
  • a network device for example, a first network device and a second network device
  • each functional unit may be divided according to each function, or two or more functions may be used.
  • the functions are integrated in one processing unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • FIG. 12A shows a possible structural diagram of the network device involved in the above embodiment.
  • the network device 1200 includes a processing unit 1202 and a communication unit 1203.
  • the processing unit 1202 is configured to control and manage the actions of the network device 1200.
  • the processing unit 1202 is configured to support the network device 1200 to perform steps 301-303 in FIG. 3, steps 306-307 in FIG. 7, steps 801-803 in FIG. 806-807, and/or other steps for performing the techniques described herein.
  • the processing unit is configured to support the network device 1200 to perform steps 304-305 in FIG. 3, steps 308-309 in FIG.
  • the communication unit 1203 is for supporting communication between the network device 1200 and other network devices.
  • the network device 1200 may further include a storage unit 1201 for storing program codes and data of the network device 1200.
  • the processing unit 1202 may be a processor or a controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 1203 may be a communication interface, a transceiver, a transceiver circuit, etc., wherein the communication interface is a collective name and may include one or more interfaces, such as an interface between the first network device and the second network device.
  • the storage unit 1201 may be a memory.
  • the processing unit 1202 is a processor
  • the communication unit 1203 is a communication interface
  • the storage unit 1201 is a memory
  • the network device involved in the embodiment of the present application may be the network device shown in FIG. 12B.
  • the network device 1210 includes a processor 1212, a communication interface 1213, and a memory 1211.
  • network device 1210 may also include a bus 1214.
  • the communication interface 1213, the processor 1212, and the memory 1211 may be connected to each other through a bus 1214.
  • the bus 1214 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • the bus 1214 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 12B, but it does not mean that there is only one bus or one type of bus.
  • the network device shown in FIG. 12A or 12B above may be the first network device or the second network device.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present application may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in a network device.
  • the processor and the storage medium can also exist as discrete components in the network device.
  • the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种保护倒换方法、设备及系统，属于通信技术领域。所述方法包括：第一网络设备确定主用FlexE链路组中存在至少一条链路不可用，从预配置的备用链路中选择m条备用链路作为保护链路，其中，m为正整数，且m小于或等于主用FlexE链路组中的不可用链路的数量；第一网络设备向第二网络设备发送保护倒换通知，并采用m条保护链路替换至少一条不可用链路中的m条不可用链路；第二网络设备根据保护倒换通知，采用m条保护链路替换m条不可用链路，其中，m条保护链路和m条不可用链路一一对应；第二网络设备向第一网络设备发送保护倒换响应。本申请实施例满足了FlexE对保护倒换的应用需求。

Description

保护倒换方法、设备及系统 技术领域
本申请实施例涉及通信技术领域，特别涉及一种保护倒换方法、设备及系统。
背景技术
灵活以太网(Flexible Ethernet，FlexE)是一种基于以太网的改进型网络。
请参考图1，其示例性示出了一种FlexE的网络架构。第一网络设备11和第二网络设备12之间建立有多条链路，这些链路组成一个FlexE链路组，这些链路用于承载至少一个客户业务。由于一个客户业务可通过多条链路传输，因此具备更高的灵活性。
在目前的FlexE标准中，并没有定义相关的保护倒换机制。一个FlexE链路组中如果有一条链路出现故障，则整个FlexE链路组停止工作，这会造成大面积的业务中断。
发明内容
本申请实施例提供了一种保护倒换方法、设备及系统，用以解决现有技术所存在的因FlexE链路组中存在链路不可用时，导致整个FlexE链路组停止工作的问题。
一方面，本申请实施例提供一种保护倒换方法，该方法包括：第一网络设备确定主用FlexE链路组中存在至少一条链路不可用，从预配置的备用链路中选择m条备用链路作为保护链路，其中，主用FlexE链路组包括逻辑上捆绑的多条链路，m为正整数，且m小于或等于主用FlexE链路组中的不可用链路的数量；第一网络设备向第二网络设备发送保护倒换通知，并采用m条保护链路替换上述至少一条不可用链路中的m条不可用链路；第二网络设备根据保护倒换通知，采用m条保护链路替换m条不可用链路，其中，m条保护链路和m条不可用链路一一对应；第二网络设备向第一网络设备发送保护倒换响应。
本申请实施例提供的方案中，通过为FlexE链路组中的链路提供备用链路，实现了链路的冗余备份。这样，当FlexE链路组中存在不可用链路时，选择备用链路作为保护链路，采用该保护链路替换掉不可用链路，从而避免因一条链路出现故障而导致整个FlexE链路组停止工作的问题，满足了FlexE对保护倒换的应用需求。
在一个可能的设计中，保护链路属于备用FlexE链路组。第一网络设备/第二网络设备采用m条保护链路替换至少一条不可用链路中的m条不可用链路，包括：对于m条保护链路中的第一保护链路，若第一保护链路属于备用FlexE链路组，且第一保护链路用于替换第一不可用链路，则第一网络设备/第二网络设备将第一不可用链路从主用FlexE链路组中删除，并将第一保护链路添加至主用FlexE链路组中。
通过上述方式，实现了在保护链路属于备用FlexE链路组的情况下链路的替换。
在另一个可能的设计中，保护链路属于主用FlexE链路组。第一网络设备/第二网络设备采用m条保护链路替换至少一条不可用链路中的m条不可用链路，包括：对于m条保护链路中的第二保护链路，若第二保护链路属于主用FlexE链路组，且第二保护链路用于替换第二不可用链路，则第一网络设备/第二网络设备将第二不可用链路的时隙配置，配置到第二保护链路。
通过上述方式，实现了在保护链路属于主用FlexE链路组的情况下链路的替换。
在又一个可能的设计中，保护倒换通知为FlexE信息帧，FlexE信息帧的目标字段中携带保护倒换信息，保护倒换信息用于指示第二网络设备采用m条保护链路替换m条不可用链路。
通过扩展FlexE信息帧中的目标字段的功能，实现了保护倒换信息的发送。
在又一个可能的设计中，所述方法还包括：若确定m条不可用链路中存在n条链路恢复至可用，则第一网络设备向第二网络设备发送链路恢复通知，并采用n条恢复至可用的链路替换n条保护链路；第二网络设备根据链路恢复通知，采用n条恢复至可用的链路替换n条保护链路，n为正整数，且n小于或等于m；第二网络设备向第一网络设备发送链路恢复响应。
通过上述方式，在确定链路由不可用恢复至可用时，采用恢复至可用的链路替换保护链路，以实现及时恢复备用链路资源。
在又一个可能的设计中，所述方法还包括：第一网络设备确定主用FlexE链路组中存在至少一条链路不可用，包括：第一网络设备检测在主用FlexE链路组包括的各条链路上是否正确接收第二网络设备发送的FlexE信息帧；第一网络设备根据检测结果确定主用FlexE链路组包括的各条链路是否可用；和/或，第一网络设备接收第二网络设备发送的接收状态信息，该接收状态信息用于指示第二网络设备在主用FlexE链路组包括的各条链路上是否正确接收第一网络设备发送的FlexE信息帧；第一网络设备根据接收状态信息确定主用FlexE链路组包括的各条链路是否可用。
通过上述方式，提供了两种确定链路是否可用的方式，以实现对链路的双向可用情况分别进行检测。
在又一个可能的设计中，所述方法还包括：第一网络设备向第二网络设备发送第一主从配置信息，第一主从配置信息用于指示在第一网络设备中配置的主从关系，以使得第二网络设备根据第一主从配置信息以及在第二网络设备中配置的主从关系，确定第一网络设备与第二网络设备之间的主从关系是否配置正确。第二网络设备向第一网络设备发送第二主从配置信息，第二主从配置信息用于指示在第二网络设备中配置的主从关系，以使得第一网络设备根据第二主从配置信息以及在第一网络设备中配置的主从关系，确定第一网络设备与第二网络设备之间的主从关系是否配置正确。
通过上述方式，FlexE的两端设备之间即可明确主从关系，在出现不可用链路时，由主端设备选择保护链路，并发起保护倒换通知，简化流程。
另一方面，本申请实施例提供一种网络设备，该网络设备具有实现上述方法示例中第一网络设备侧或第二网络设备侧行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
在一个可能的设计中，网络设备的结构中包括处理器和通信接口，所述处理器被配置为支持网络设备执行上述方法中相应的功能。所述通信接口用于支持网络设备与其它网络设备之间的通信。进一步的，网络设备还可以包括存储器，所述存储器用于与处理器耦合，其保存网络设备必要的程序指令和数据。
再一方面，本申请实施例提供一种保护倒换系统，该系统包括上述方面所述的第一网络设备和第二网络设备。
又一方面，本申请实施例提供一种计算机存储介质，用于储存为上述第一网络设备和/或第二网络设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
又一方面，本申请实施例提供一种计算机程序产品，当该计算机程序产品被执行时，其用于执行上述方面所述的第一网络设备和/或第二网络设备侧的方法。
相较于现有技术，本申请实施例提供的方案中，通过为FlexE链路组中的链路提供备用链路，实现了链路的冗余备份。这样，当FlexE链路组中存在不可用链路时，选择备用链路作为保护链路，采用该保护链路替换掉不可用链路，从而避免因一条链路出现故障而导致整个FlexE链路组停止工作的问题，满足了FlexE对保护倒换的应用需求。
附图说明
图1是示例性示出的一种FlexE的网络架构；
图2是示例性示出的一种保护倒换的示意图；
图3是本申请一个实施例提供的保护倒换方法的流程图；
图4是示例性示出的另一种保护倒换的示意图；
图5A是示例性示出的主端至从端方向的链路不可用时，保护倒换的示意图；
图5B是示例性示出的主端至从端方向的链路不可用时，保护倒换的流程图；
图6A是示例性示出的从端至主端方向的链路不可用时，保护倒换的示意图；
图6B是示例性示出的从端至主端方向的链路不可用时，保护倒换的流程图；
图7是示例性示出的链路恢复过程的流程图；
图8是本申请另一个实施例提供的保护倒换方法的流程图；
图9是示例性示出的一种应用场景的示意图；
图10是示例性示出的另一种应用场景的示意图；
图11是示例性示出的又一种应用场景的示意图；
图12A是本申请一个实施例提供的网络设备的示意性框图；
图12B是本申请一个实施例提供的网络设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
本申请实施例描述的网络架构以及业务场景是为了更加清楚地说明本申请实施例的技术方案，并不构成对本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例提供的技术方案可适用于图1所示的一种FlexE的网络架构中。该网络架构包括：第一网络设备11和第二网络设备12。
网络设备(例如第一网络设备11、第二网络设备12等)可以是具备数据收发功能的设备，例如路由器、交换机、数据存储设备等。
第一网络设备11和第二网络设备12之间具有至少一个FlexE链路组，每一个FlexE链路组包括逻辑上捆绑的多条链路。所谓的逻辑上捆绑，是指多条链路被划分在一起形成一 个FlexE链路组，这多条链路可以不存在物理连接关系，因此，FlexE链路组中的多条链路在物理上可以是独立的。本申请实施例中涉及的链路可以是以太网物理链路，例如光纤。在本申请实施例中，对每一条链路提供的带宽不作限定，示例性地，每一条链路提供的带宽为100G，也即100G比特，1G＝1024M。FlexE的网络设备可以通过链路的编号来标识一个FlexE链路组中包含哪些链路，来实现多条链路的逻辑捆绑。例如，每一条链路的编号可用1-254之间的一个数字来标识，0和255为保留数字。一个链路的编号可对应网络设备上的一个端口。第一网络设备11和第二网络设备12两端需采用相同的编号来标识同一条链路。一个FlexE链路组中包括的各条链路的编号不必是连续的。两个网络设备之间具有一个或多个FlexE链路组。一条链路可用于承载至少一个客户业务，一个客户业务可在至少一条链路上传输。在FlexE标准中，客户业务可以称为Client。
在一个示例中，如图2所示，假设第一网络设备和第二网络设备之间具有2个主用FlexE链路组和1个备用FlexE链路组。主用FlexE链路组1中包括4条链路，分别记为PG1:PHY1、PG1:PHY2、PG1:PHY3和PG1:PHY4。主用FlexE链路组2中包括2条链路，分别记为PG2:PHY1和PG2:PHY2。备用FlexE链路组中包括2条链路，分别记为Spare PHY1和Spare PHY2。采用本申请实施例提供的技术方案，假设当主用FlexE链路组1中的链路PG1:PHY2因出现故障而不可用时，从备用FlexE链路组中选择一条备用链路(如Spare PHY1)作为保护链路，采用Spare PHY1替换PG1:PHY2，从而实现保护倒换。如果主用FlexE链路组中存在多条链路不可用，则需为该多条链路中的每一条链路提供上述保护倒换。
下面将基于上面所述的本申请实施例涉及的共性方面，对本申请实施例进一步详细说明。
请参考图3，其示出了本申请一个实施例提供的保护倒换方法的流程图。该方法可以包括如下几个步骤。
步骤301，第一网络设备确定主用FlexE链路组中存在至少一条链路不可用，从预配置的备用链路中选择m条备用链路作为保护链路，其中，m为正整数，且m小于或等于主用FlexE链路组中的不可用链路的数量。
主用FlexE链路组包括逻辑上捆绑的多条链路。例如，图2示出的主用FlexE链路组1中包括4条链路，主用FlexE链路组2中包括2条链路。
备用链路是指当主用FlexE链路组中的链路不可用时，用于替换上述不可用链路的冗余链路。预配置的备用链路的总数量可根据实际需求进行确定。例如，当需要提供较强的保护倒换功能时，预配置较多数量的备用链路。
在第一种可能的实施方式中，预配置的备用链路不属于任一主用FlexE链路组。可选地，预配置的备用链路属于备用FlexE链路组。备用FlexE链路组中的任意一条备用链路，可用于为任一主用FlexE链路组中的任意一条链路提供保护倒换。例如，图2示出的备用FlexE链路组中包括2条链路，分别记为Spare PHY1和Spare PHY2。Spare PHY1可用于为主用FlexE链路组1和主用FlexE链路组2中的任意一条链路提供保护倒换，同样的，Spare PHY2可用于为主用FlexE链路组1和主用FlexE链路组2中的任意一条链路提供保护倒换。
在第二种可能的实施方式中，在主用FlexE链路组中预配置备用链路。在某一主用FlexE链路组中预配置的备用链路，仅用于为其所属的主用FlexE链路组中的任意一条链路提供保 护倒换，而无法用于为其它主用FlexE链路组中的链路提供保护倒换。例如，如图4所示，假设第一网络设备和第二网络设备之间具有2个主用FlexE链路组。主用FlexE链路组1中包括6条链路，其中4条主用链路和2条备用链路。上述4条主用链路分别记为PG1:PHY1、PG1:PHY2、PG1:PHY3和PG1:PHY4，上述2条备用链路分别记为PG1:Spare PHY1和PG1:Spare PHY2。主用FlexE链路组2中包括2条链路，分别记为PG2:PHY1和PG2:PHY2，上述2条链路均为主用链路，主用FlexE链路组2中不包括备用链路。PG1:Spare PHY1可用于为主用FlexE链路组1中的任意一条主用链路提供保护倒换，同样的，PG1:Spare PHY2可用于为主用FlexE链路组1中的任意一条主用链路提供保护倒换。但是，PG1:Spare PHY1和PG1:Spare PHY2均无法用于为主用FlexE链路组2中的链路提供保护倒换。
第一网络设备在从预配置的备用链路中选取保护链路时，从可供选择的备用链路中选取保护链路。可供选择的备用链路是指：属于备用FlexE链路组和/或与不可用链路属于同一主用FlexE链路组，且未被使用的备用链路。
假设第一网络设备确定主用FlexE链路组中存在n条链路不可用，n为正整数，预配置的可供选择的备用链路的数量为p，p为正整数。如果p大于或等于n，则第一网络设备最多可选取n条保护链路，也即上述m的最大取值为n，从而为上述n条不可用链路中的全部链路提供保护倒换；如果p小于n，则第一网络设备最多可选取p条保护链路，也即上述m的最大取值为p，从而为上述n条不可用链路中的部分链路提供保护倒换。
针对上文提及的两种实施方式，选择保护链路的具体过程可参见下文介绍说明。
不可用链路可以是已被分配给客户业务使用的链路，也可以是未被分配给客户业务使用的链路。另外，导致链路不可用的情况可以是该链路出现故障。当然，本申请实施例并不限定其它可能情况导致链路不可用，例如在测试或维护过程中，链路被配置为由可用状态切换至不可用状态。
步骤302，第一网络设备向第二网络设备发送保护倒换通知。
保护倒换通知用于指示第二网络设备采用m条保护链路替换上述至少一条不可用链路中的m条不可用链路。其中，m条保护链路和m条不可用链路一一对应，也即1条保护链路用于替换1条不可用链路。可选地，保护倒换通知中指示有保护链路与不可用链路之间的对应关系，也即指示采用哪一条保护链路替换哪一条不可用链路。
第一网络设备可通过任意一条或多条可用的FlexE链路向第二网络设备发送保护倒换通知。上述可用的FlexE链路可以是主用FlexE链路组中未故障的链路，也可以是备用链路，如保护链路。在其它可能的实现方式中，第一网络设备与第二网络设备之间还具有除FlexE链路之外的其它通信通道，第一网络设备还可以通过上述其它通信通道向第二网络设备发送保护倒换通知。上述其它通信通道包括但不限于以太网通道、光传输网络通道等等，本申请实施例对此不作限定。
可选地，当保护倒换通知采用FlexE链路发送时，保护倒换通知为FlexE信息帧。FlexE信息帧的目标字段中携带保护倒换信息，保护倒换信息用于指示第二网络设备采用m条保护链路替换m条不可用链路。FlexE的两端设备(如本申请实施例中的第一网络设备和第二网络设备)在FlexE链路上传输的报文可称为FlexE信息帧，FlexE信息帧可以是FlexE开销帧或FlexE管理帧。在FlexE标准中称为FlexE Overhead Frame和FlexE Multiframe。FlexE信息帧中包括FlexE Group Number、PHY Map、PHY Number、Client Calendar、Reserved、 Management Channel-Section、Management Channel-Shim to Shim等字段。例如，FlexE Group Number字段用于指示FlexE链路组的编号，PHY Map字段用于指示FlexE链路组所包括的链路，PHY Number字段用于指示FlexE链路组中的链路的编号，Client Calendar字段可称为时隙分配表，用于指示时隙与客户业务之间的分配关系，Reserved字段为保留字段，Management Channel字段用于指示与FlexE链路组相关的管理信息。上述目标字段可以是Management Channel-Section字段，也可以是Reserved字段，本申请实施例对此不作限定。
步骤303，第一网络设备采用m条保护链路替换m条不可用链路。
对于上述m条不可用链路中的每一条不可用链路，第一网络设备采用上述m条保护链路中的一条保护链路进行替换。
对于上述m条保护链路中的第一保护链路，若第一保护链路属于备用FlexE链路组，且第一保护链路用于替换第一不可用链路，则第一网络设备将第一不可用链路从主用FlexE链路组中删除，并将第一保护链路添加至主用FlexE链路组中。其中，第一保护链路是上述m条保护链路中的一条，第一不可用链路是上述m条不可用链路中的一条。第一网络设备将第一不可用链路从主用FlexE链路组中删除，也即解除第一不可用链路与主用FlexE链路组之间的关联关系。第一网络设备将第一保护链路添加至主用FlexE链路组中，也即创建第一保护链路与主用FlexE链路组之间的关联关系。
在一个示例中，结合参考图2，第一网络设备采用Spare PHY1替换PG1:PHY2，该替换过程可以包括如下几个步骤：
1、将PG1:PHY2从主用FlexE链路组1中删除，也即解除PG1:PHY2与主用FlexE链路组1之间的关联关系；
2、将Spare PHY1从备用FlexE链路组中删除，也即解除Spare PHY1与备用FlexE链路组之间的关联关系；
3、将Spare PHY1添加至主用FlexE链路组1中；
第一网络设备使用PG1:PHY2的配置信息进行如下配置：(1)配置Spare PHY1的FlexE Group Number；(2)配置Spare PHY1的PHY Map；(3)配置Spare PHY1的PHY Number；(4)配置Spare PHY1的Client Calendar；(5)创建Spare PHY1与主用FlexE链路组1之间的关联关系。
可选地，还包括如下步骤4：
4、将PG1:PHY2添加至备用FlexE链路组中；
第一网络设备使用Spare PHY1的配置信息进行如下配置：(1)配置PG1:PHY2的FlexE Group Number；(2)配置PG1:PHY2的PHY Map；(3)配置PG1:PHY2的PHY Number；(4)创建PG1:PHY2与备用FlexE链路组之间的关联关系。
对于上述m条保护链路中的第二保护链路，若第二保护链路属于主用FlexE链路组，且第二保护链路用于替换第二不可用链路，则第一网络设备将第二不可用链路的时隙配置，配置到第二保护链路。其中，第二保护链路是上述m条保护链路中的一条，第二不可用链路是上述m条不可用链路中的一条。时隙配置包括但不限于：时隙划分，时隙状态的配置，客户业务与时隙的分配关系的配置。时隙状态包括不可用(unavailable)状态、已使用(used)状态和未使用(unused)状态。不可用状态表示该时隙不可被分配给客户业务使用。已使用状态表示该时隙已被分配给客户业务使用。未使用状态表示该时隙可被分配给客户业务使 用，且暂未被分配给客户业务使用。
属于主用FlexE链路组中的备用链路，在未被使用时，其所有时隙均被配置为unavailable状态。在一个示例中，结合参考图4，第一网络设备采用PG1:Spare PHY1替换PG1:PHY2，第一网络设备将PG1:PHY2的时隙配置，配置到PG1:Spare PHY1。例如，PG1:PHY2上某一时隙的状态为used，则配置PG1:Spare PHY1上该对应时隙由unavailable状态变为used状态。又例如，PG1:PHY2上某一时隙被分配给客户业务1使用，则配置PG1:Spare PHY1上该对应时隙被分配给客户业务1使用。另外，第一网络设备还将PG1:PHY2上所有时隙均配置为unavailable状态。
步骤304，第二网络设备根据保护倒换通知，采用m条保护链路替换m条不可用链路。
第二网络设备接收到第一网络设备发送的保护倒换通知之后，根据该保护倒换通知，采用m条保护链路替换m条不可用链路。
对于m条保护链路中的第一保护链路，若第一保护链路属于备用FlexE链路组，且第一保护链路用于替换第一不可用链路，则第二网络设备将第一不可用链路从主用FlexE链路组中删除，并将第一保护链路添加至主用FlexE链路组中。
对于m条保护链路中的第二保护链路，若第二保护链路属于主用FlexE链路组，且第二保护链路用于替换第二不可用链路，则第二网络设备将第二不可用链路的时隙配置，配置到第二保护链路。
第二网络设备采用保护链路替换不可用链路的具体操作过程，与步骤303中介绍的第一网络设备的具体操作过程相同，参见步骤303中的介绍说明，此处不再赘述。
步骤305，第二网络设备向第一网络设备发送保护倒换响应。
保护倒换响应用于指示第二网络设备已根据保护倒换通知，完成链路替换。
第二网络设备可通过任意一条或多条可用的FlexE链路向第一网络设备发送保护倒换响应。上述可用的FlexE链路可以是主用FlexE链路组中未故障的链路，也可以是备用链路，如保护链路。在其它可能的实现方式中，第一网络设备与第二网络设备之间还具有除FlexE链路之外的其它通信通道，第二网络设备还可以通过上述其它通信通道向第一网络设备发送保护倒换响应。上述其它通信通道包括但不限于以太网通道、光传输网络通道等等，本申请实施例对此不作限定。
另外，对于任意一条不可用链路来说，如果该不可用链路已被分配给客户业务使用，则第一网络设备在接收到保护倒换响应之后，将在上述不可用链路上传输的客户业务切换到相应的一条保护链路上传输；如果该不可用链路未被分配给客户业务使用，则不需要进行上述客户业务的切换。
本申请实施例提供的方案中，通过为FlexE链路组中的链路提供备用链路，实现了链路的冗余备份。这样，当FlexE链路组中存在不可用链路时，选择备用链路作为保护链路，采用该保护链路替换掉不可用链路，从而避免因一条链路出现故障而导致整个FlexE链路组停止工作的问题，满足了FlexE对保护倒换的应用需求。
可选地，第一网络设备选择保护链路的具体过程可以如下：
第一网络设备在确定某一主用FlexE链路组中存在a条链路不可用时，如果该主用FlexE链路组中未预配置备用链路或者该主用FlexE链路组中不存在可供选择的备用链路，而备用 FlexE链路组中存在可供选择的备用链路，则第一网络设备从备用FlexE链路组中选择b条备用链路作为保护链路；其中，a、b均为正整数，且b小于或等于a。假设备用FlexE链路组中可供选择的备用链路的数量为c，c为正整数。如果c大于或等于a，则第一网络设备最多可选取a条保护链路，也即为上述a条不可用链路中的全部链路提供保护倒换；如果c小于a，则第一网络设备最多可选取c条保护链路，也即为上述a条不可用链路中的部分链路提供保护倒换。
第一网络设备在确定某一主用FlexE链路组中存在a条链路不可用时，如果该主用FlexE链路组中存在可供选择的备用链路，而备用FlexE链路组中不存在可供选择的备用链路或者未预配置备用FlexE链路组，则第一网络设备从上述主用FlexE链路组中选择b条备用链路作为保护链路；其中，a、b均为正整数，且b小于或等于a。假设上述主用FlexE链路组中可供选择的备用链路的数量为c，c为正整数。如果c大于或等于a，则第一网络设备最多可选取a条保护链路，也即为上述a条不可用链路中的全部链路提供保护倒换；如果c小于a，则第一网络设备最多可选取c条保护链路，也即为上述a条不可用链路中的部分链路提供保护倒换。
第一网络设备在确定某一主用FlexE链路组中存在a条链路不可用时，如果该主用FlexE链路组中存在可供选择的备用链路，且备用FlexE链路组中也存在可供选择的备用链路，则第一网络设备从上述主用FlexE链路组和/或备用FlexE链路组中选择b条备用链路作为保护链路；其中，a、b均为正整数，且b小于或等于a。假设上述主用FlexE链路组和备用FlexE链路组中可供选择的备用链路的总数量为c，c为正整数。如果c大于或等于a，则第一网络设备最多可选取a条保护链路，也即为上述a条不可用链路中的全部链路提供保护倒换；如果c小于a，则第一网络设备最多可选取c条保护链路，也即为上述a条不可用链路中的部分链路提供保护倒换。可选地，第一网络设备优先从主用FlexE链路组中选取保护链路。
在上述图3实施例中，以第一网络设备选择保护链路，并发起保护倒换通知为例。为了避免因FlexE的两端设备同时发起保护倒换通知而导致选择的保护链路不同，两端设备之间可以协商主从关系，由主端设备选择保护链路并发起保护倒换通知。
可选地，主从关系的协商过程包括如下两部分：
第一部分，第一网络设备向第二网络设备发送第一主从配置信息，第一主从配置信息用于指示在第一网络设备中配置的主从关系。第二网络设备接收到第一主从配置信息之后，根据第一主从配置信息以及在第二网络设备中配置的主从关系，确定第一网络设备与第二网络设备之间的主从关系是否配置正确；
第二部分，第二网络设备向第一网络设备发送第二主从配置信息，第二主从配置信息用于指示在第二网络设备中配置的主从关系。第一网络设备接收到第二主从配置信息之后，根据第二主从配置信息以及在第一网络设备中配置的主从关系，确定第一网络设备与第二网络设备之间的主从关系是否配置正确。
其中，第一网络设备与第二网络设备之间的主从关系可以是第一网络设备为主端设备，第二网络设备为从端设备；也可以是第一网络设备为从端设备，第二网络设备为主端设备。上述主从关系可以由用户在第一网络设备与第二网络设备中配置，且可根据实际需求更改。
另外，上述主从配置信息(包括第一主从配置信息和第二主从配置信息)可以在主从关系初始配置或者重新配置时发送，也可以每隔预设时间间隔发送一次。其中，相邻两次的预设时间间隔可以相同，也可以不同。
可选地，上述主从配置信息被携带于FlexE信息帧中发送。例如，在FlexE信息帧的目标字段中携带主从配置信息。目标字段可以是上文介绍的Management Channel-Section字段，或Reserved字段，本申请实施例对此不作限定。另外，上述主从配置信息可以在主从关系初始配置或者重新配置后发送的第一个FlexE信息帧中携带，也可以在每一个FlexE信息帧中携带。例如，在每一个FlexE开销帧的Management Channel-Section字段中携带主从配置信息。
通过上述协商，第一网络设备与第二网络设备之间即可明确主从关系，在出现不可用链路时，由主端设备选择保护链路，并发起保护倒换通知，简化流程。
另外，当第一网络设备或第二网络设备确定主从关系配置不正确的情况下，可以发出告警信息，该告警信息用于指示主从关系配置不准确。通过上述方式，实现了对主从关系是否配置准确进行检测，确保主从配置的准确性。
可选地，第一网络设备采用如下方式，确定主用FlexE链路组中是否存在链路不可用。
在第一种方式中，第一网络设备自行检测是否存在链路不可用。第一网络设备检测在主用FlexE链路组包括的各条链路上是否正确接收第二网络设备发送的FlexE信息帧，根据检测结果确定主用FlexE链路组包括的各条链路是否可用。
若第一网络设备在某一链路上正确接收第二网络设备发送的FlexE信息帧，则确定该链路可用；若第一网络设备在某一链路上未正确接收第二网络设备发送的FlexE信息帧，则确定该链路不可用。例如，FlexE开销帧通常以104.77us发送一次，若第一网络设备在某一链路上超时未接收到第二网络设备发来的FlexE开销帧，则第一网络设备确定该链路不可用。或者，若第一网络设备在某一链路上接收到第二网络设备发来的FlexE信息帧，但接收信号强度小于预设门限值，则第一网络设备也可确定该链路不可用。
可选地，第一网络设备在获取上述检测结果之后，向第二网络设备发送接收状态信息，该接收状态信息用于指示第一网络设备在主用FlexE链路组包括的各条链路上是否正确接收第二网络设备发送的FlexE信息帧。
在第二种方式中，第一网络设备根据第二网络设备反馈的接收状态信息，确定是否存在链路不可用。第二网络设备自行检测是否存在链路不可用(其方式可参见上文介绍)，而后向第一网络设备发送接收状态信息，该接收状态信息用于指示第二网络设备在主用FlexE链路组包括的各条链路上是否正确接收第一网络设备发送的FlexE信息帧。而后，第一网络设备根据接收到的接收状态信息，确定主用FlexE链路组包括的各条链路是否可用。
第一网络设备与第二网络设备之间的链路是双向的，第一网络设备可自行检测对端至本端方向的链路是否可用，第二网络设备也可自行检测对端至本端方向的链路是否可用。
在一个示例中，接收状态信息中指示的链路状态包括：正常(Normal)状态、信号失效(signal failure，SF)状态和信号劣化(signal degradation，SD)状态。Normal状态表示链路可用，SF状态和SD状态均表示链路不可用。其中，SF状态是指无法检测到对端信号，如无法接收到对端发送的FlexE信息帧；SD状态是指能够检测到对端信号，但信号强度较 低，如能够接收到对端发送的FlexE信息帧，但存在误码。处于SF状态和SD状态的链路均为不可用链路，均需要通过保护链路来替换。可选地，优先替换处于SF状态的链路。
可选地，上述接收状态信息被携带于FlexE信息帧中发送。例如，在FlexE信息帧的目标字段中携带接收状态信息。目标字段可以是上文介绍的Management Channel-Section字段，或Reserved字段，本申请实施例对此不作限定。另外，上述接收状态信息可以在链路状态发生变化时发送，也可以在每一个FlexE信息帧中携带。例如，在每一个FlexE开销帧的Management Channel-Section字段中携带接收状态信息。
在一个示例中，通过对FlexE信息帧中的目标字段(如Management Channel-Section字段)进行扩展，使之携带接收状态信息、主从指示信息或倒换动作信息。其中，倒换动作信息可以是上文介绍的保护倒换信息和保护倒换响应，也可以是下文介绍的链路恢复信息和链路恢复响应。
在主用FlexE链路组中的链路上传输的FlexE信息帧的目标字段中携带的信息如下表-1所示：
Figure PCTCN2017090402-appb-000001
表-1
在备用链路上传输的FlexE信息帧的目标字段中携带的信息如下表-2所示：
Figure PCTCN2017090402-appb-000002
表-2
另外，上述表-1和表-2中的传递时机为“始终”表示在每一个FlexE信息帧中携带，传递时机为“倒换时”表示在需要进行倒换时发送的某一个FlexE信息帧中携带。
在上文已经介绍，发生链路不可用的情况，可能是主端设备至从端设备的方向不可用，也可能是从端设备至主端设备的方向不可用。
结合参考图5A和图5B，以第一网络设备为主端设备，第二网络设备为从端设备为例，对于主用FlexE链路组1中的PG1:PHY2链路，如果主端设备至从端设备的方向不可用，相应的保护倒换过程如下：
步骤51，第二网络设备向第一网络设备发送接收状态信息，该接收状态信息中指示PG1:PHY2为SF状态；
步骤52，第一网络设备从预配置的备用链路中选择Spare PHY1作为保护链路；
步骤53，第一网络设备向第二网络设备发送保护倒换通知，该保护倒换通知用于指示第二网络设备采用Spare PHY1替换PG1:PHY2；
步骤54，第一网络设备采用Spare PHY1替换PG1:PHY2；
步骤55，第二网络设备根据保护倒换通知，采用Spare PHY1替换PG1:PHY2；
步骤56，第二网络设备向第一网络设备发送保护倒换响应。
结合参考图6A和图6B，以第一网络设备为主端设备，第二网络设备为从端设备为例，对于主用FlexE链路组1中的PG1:PHY2链路，如果从端设备至主端设备的方向不可用，相应的保护倒换过程如下：
步骤61，第一网络设备检测到PG1:PHY2不可用；
步骤62，第一网络设备向第二网络设备发送接收状态信息，该接收状态信息中指示PG1:PHY2为SF状态；
步骤63，第一网络设备从预配置的备用链路中选择Spare PHY1作为保护链路；
步骤64，第一网络设备向第二网络设备发送保护倒换通知，该保护倒换通知用于指示第二网络设备采用Spare PHY1替换PG1:PHY2；
步骤65，第一网络设备采用Spare PHY1替换PG1:PHY2；
步骤66，第二网络设备根据保护倒换通知，采用Spare PHY1替换PG1:PHY2；
步骤67，第二网络设备向第一网络设备发送保护倒换响应。
可选地，如图7所示，第一网络设备和第二网络设备在采用m条保护链路替换m条不可用链路之后，还执行如下步骤：
步骤306，若第一网络设备确定m条不可用链路中存在n条链路恢复至可用，则第一网络设备向第二网络设备发送链路恢复通知，n为正整数，且n小于或等于m。
第一网络设备可以采用上文介绍的自行检测的方式，或者根据第二网络设备发来的接收状态信息，确定不可用链路是否恢复至可用。
链路恢复通知用于指示第二网络设备采用n条恢复至可用的链路替换n条保护链路。其中，n条恢复至可用的链路和n条保护链路一一对应，也即1条恢复至可用的链路用于替换1条保护链路。可选地，链路恢复通知中指示有恢复至可用的链路与保护链路之间的对应关系，也即指示采用哪一条恢复至可用的链路替换哪一条保护链路。
第一网络设备可以通过任意一条或多条可用的FlexE链路向第二网络设备发送保护倒换通知。上述可用的FlexE链路可以是主用FlexE链路组中未故障的链路，如恢复至可用的链路，也可以是保护链路，或者其它备用链路。或者，第一网络设备还可以通过其它通信通道向第二网络设备发送链路恢复通知。上述其它通信通道包括但不限于以太网通道、光传输网络通道等等，本申请实施例对此不作限定。
可选地，当链路恢复通知采用FlexE链路发送时，链路恢复通知为FlexE信息帧。FlexE信息帧的目标字段中携带链路恢复信息，链路恢复信息用于指示第二网络设备采用n条恢复至可用的链路替换n条保护链路。例如，上述目标字段可以是Management Channel-Section 字段，也可以是Reserved字段，本申请实施例对此不作限定。
步骤307，第一网络设备采用n条恢复至可用的链路替换n条保护链路。
对于上述n条保护链路中的每一条保护链路，第一网络设备采用上述n条恢复至可用的链路中的一条链路进行替换。
对于上述n条保护链路中的第一保护链路，若第一保护链路属于备用FlexE链路组，且采用第一恢复链路替换第一保护链路，则第一网络设备将第一保护链路从主用FlexE链路组中删除，并将第一恢复链路添加至主用FlexE链路组中。其中，第一恢复链路是上述n条恢复至可用的链路中的一条链路。第一网络设备将第一保护链路从主用FlexE链路组中删除，也即解除第一保护链路与主用FlexE链路组之间的关联关系。第一网络设备将第一恢复链路添加至主用FlexE链路组中，也即创建第一恢复链路与主用FlexE链路组之间的关联关系。
在一个示例中，结合参考图2，假设PG1:PHY2由不可用恢复至可用，第一网络设备采用PG1:PHY2替换Spare PHY1。该替换过程与上文介绍的采用保护链路替换不可用链路的替换过程相同，此处不再赘述。
对于上述n条保护链路中的第二保护链路，若第二保护链路属于主用FlexE链路组，且采用第二恢复链路替换第二保护链路，则第一网络设备将第二保护链路的时隙配置，配置到第二恢复链路。其中，第二恢复链路是上述n条恢复至可用的链路中的一条链路。
在一个示例中，结合参考图4，假设PG1:PHY2由不可用恢复至可用，第一网络设备采用PG1:PHY2替换PG1:Spare PHY1。该替换过程与上文介绍的采用保护链路替换不可用链路的替换过程相同，此处不再赘述。
步骤308，第二网络设备根据链路恢复通知，采用n条恢复至可用的链路替换n条保护链路。
第二网络设备接收到第一网络设备发送的链路恢复通知之后，根据该链路恢复通知，采用n条恢复至可用的链路替换n条保护链路。
第二网络设备采用恢复至可用的链路替换保护链路的具体操作过程，与步骤307中介绍的第一网络设备的具体操作过程相同，参见步骤307中的介绍说明，此处不再赘述。
步骤309，第二网络设备向第一网络设备发送链路恢复响应。
链路恢复响应用于指示第二网络设备已根据链路恢复通知，完成链路替换。
第二网络设备可通过任意一条或多条可用的FlexE链路向第一网络设备发送链路恢复响应。上述可用的FlexE链路可以是主用FlexE链路组中未故障的链路，如恢复至可用的链路，也可以是保护链路，或者其它备用链路。或者，第二网络设备还可以通过其它通信通道向第一网络设备发送链路恢复响应。上述其它通信通道包括但不限于以太网通道、光传输网络通道等等，本申请实施例对此不作限定。
第一网络设备可以通过任意一条或多条可用的FlexE链路向第二网络设备发送保护倒换通知。上述可用的FlexE链路可以是主用FlexE链路组中未故障的链路，如恢复至可用的链路，也可以是保护链路，或者其它备用链路。或者，第一网络设备还可以通过其它通信通道向第二网络设备发送链路恢复通知。上述其它通信通道包括但不限于以太网通道、光传输网络通道等等，本申请实施例对此不作限定。
本申请实施例提供的方案中，通过在确定链路由不可用恢复至可用时，采用恢复至可用的链路替换保护链路，以实现及时恢复备用链路资源。
此外，在其它可能的实现方式中，也可以使用非恢复模式，也即不可用链路在被保护链路替换之后，即变成备用链路，在不可用链路恢复至可用后，无需执行上述实施例介绍的链路恢复的操作。
在一个示例中，如图8所示，对于主用FlexE链路组中的任意一条链路，当第一网络设备确定该链路不可用(也即该链路为不可用链路)时，执行如下步骤流程，对该不可用链路进行保护倒换。
步骤801，第一网络设备在确定主用FlexE链路组中存在任意一条链路不可用时，从预配置的备用链路中选择一条备用链路作为保护链路；
在本实施例中，以图2所示的保护倒换场景为例。第一网络设备在确定主用FlexE链路组1中的PG1:PHY2不可用时，从备用FlexE链路组中选择Spare PHY1作为保护链路。
步骤802，第一网络设备通过保护链路向第二网络设备发送保护倒换通知；
可选地，第一网络设备通过Spare PHY1向第二网络设备发送FlexE信息帧，该FlexE信息帧的Management Channel-Section字段中携带保护倒换信息。该保护倒换信息用于指示第二网络设备采用Spare PHY1替换PG1:PHY2，例如，该保护倒换信息中携带PG1:PHY2的编号以及保护倒换动作的指示信息。
步骤803，第一网络设备采用保护链路替换不可用链路；
第一网络设备将PG1:PHY2从主用FlexE链路组1中删除，将Spare PHY1从备用FlexE链路组中删除，而后将Spare PHY1添加至主用FlexE链路组1中。可选地，第一网络设备还将PG1:PHY2添加至备用FlexE链路组中。
步骤804，第二网络设备根据保护倒换通知，采用保护链路替换不可用链路；
第二网络设备在接收到保护倒换通知之后，根据保护倒换通知，将PG1:PHY2从主用FlexE链路组1中删除，将Spare PHY1从备用FlexE链路组中删除，而后将Spare PHY1添加至主用FlexE链路组1中。可选地，第二网络设备还将PG1:PHY2添加至备用FlexE链路组中。
步骤805，第二网络设备通过保护链路向第一网络设备发送保护倒换响应；
第二网络设备完成上述保护倒换动作之后，通过Spare PHY1向第一网络设备发送FlexE信息帧，该FlexE信息帧的Management Channel-Section字段中携带保护倒换响应。
可选地，如果采用恢复模式，如图8所示，本实施例还包括如下步骤：
步骤806，第一网络设备在确定不可用链路恢复至可用后，通过保护链路向第二网络设备发送链路恢复通知；
可选地，第一网络设备在确定PG1:PHY2由不可用恢复至可用后，通过Spare PHY1向第二网络设备发送FlexE信息帧，该FlexE信息帧的Management Channel-Section字段中携带链路恢复信息。该链路恢复信息用于指示第二网络设备采用PG1:PHY2替换Spare PHY1，例如，该链路恢复信息中携带PG1:PHY2的编号以及链路恢复动作的指示信息。
步骤807，第一网络设备采用恢复至可用的链路替换保护链路；
第一网络设备将Spare PHY1从主用FlexE链路组1中删除，而后将恢复至可用的PG1：PHY2添加至主用FlexE链路组1中，并将Spare PHY1添加至备用FlexE链路组中。
步骤808，第二网络设备根据链路恢复通知，采用恢复至可用的链路替换保护链路；
第二网络设备在接收到链路恢复通知之后，根据链路恢复通知，将Spare PHY1从主用FlexE链路组1中删除，而后将恢复至可用的PG1:PHY2添加至主用FlexE链路组1中，并将Spare PHY1添加至备用FlexE链路组中。
步骤809，第二网络设备通过保护链路向第一网络设备发送链路恢复响应。
第二网络设备完成上述链路恢复动作之后，通过Spare PHY1向第一网络设备发送FlexE信息帧，该FlexE信息帧的Management Channel-Section字段中携带链路恢复响应。
需要说明的一点是，在本实施例中，仅以通过保护链路发送链路恢复通知和链路恢复响应为例。在其它可能的实现方式中，也可以通过恢复至可用的链路发送链路恢复通知和链路恢复响应。
对于主用FlexE链路组中的任意一条链路，当该链路不可用时，均可采用本实施例提供的方式选择保护链路，通过该保护链路对该不可用链路进行保护倒换。
下面，对本申请实施例提供的技术方案的应用场景做示例性介绍。
1、数据设备FlexE接口直连场景
如图9所示，两台数据设备(包括数据设备1和数据设备2)之间通过FlexE接口直连，其中，数据设备1作为主端设备，数据设备2作为从端设备。数据设备1和数据设备2之间包括主用FlexE链路组1，该主用FlexE链路组1中包括4条链路。数据设备1和数据设备2之间还包括备用FlexE链路组，该备用FlexE链路组中包括2条备用链路。示例性地，当主用FlexE链路组1中的PG1:PHY2不可用时，采用备用FlexE链路组中的Spare PHY1作为保护链路，替换PG1:PHY2。
2、传送网FlexE Termination应用场景
在此种应用场景下，如图10所示，传送网设备(如图中的传送设备1和传送设备2)将FlexE信号还原到FlexE Client级别进行传送。接入传送网的两端分别配置了两个保护组(如图中示出的保护组1和保护组2)，通过保护组对数据设备与传送设备之间的FlexE接口进行保护。两个保护组的配置互相独立。
如图10所示，保护组1中包括数据设备1和传送设备1，其中，数据设备1作为主端设备，传送设备2作为从端设备。数据设备1和传送设备1之间包括主用FlexE链路组1，该主用FlexE链路组1中包括4条链路。数据设备1和传送设备1之间还包括备用FlexE链路组1，该备用FlexE链路组1中包括2条备用链路。示例性地，当主用FlexE链路组1中的PG1:PHY2不可用时，采用备用FlexE链路组1中的Spare PHY1作为保护链路，替换PG1:PHY2。保护组2中包括传送设备2和数据设备2，其中，传送设备2和数据设备2之间包括主用FlexE链路组2，该主用FlexE链路组2中包括5条链路。传送设备2和数据设备2之间还包括备用FlexE链路组2，该备用FlexE链路组2中包括3条备用链路。
3、传送网FlexE Aware应用场景
在此种应用场景下，如图11所示，传送网设备(如图中的传送设备1和传送设备2)对FlexE的开销和净荷进行传送。接入传送网的两端分别配置了两个保护组(如图中示出的保护组1和保护组2)，通过保护组对数据设备与传送设备之间的FlexE接口进行保护。两个保护组的配置互相独立。
如图11所示，保护组1中包括数据设备1和传送设备1，其中，数据设备1作为主端 设备，传送设备2作为从端设备。数据设备1和传送设备1之间包括主用FlexE链路组1，该主用FlexE链路组1中包括4条链路。数据设备1和传送设备1之间还包括备用FlexE链路组1，该备用FlexE链路组1中包括2条备用链路。示例性地，当主用FlexE链路组1中的PG1:PHY2不可用时，采用备用FlexE链路组1中的Spare PHY1作为保护链路，替换PG1:PHY2。保护组2中包括传送设备2和数据设备2，其中，传送设备2和数据设备2之间包括主用FlexE链路组2，该主用FlexE链路组2中包括4条链路。传送设备2和数据设备2之间还包括备用FlexE链路组2，该备用FlexE链路组2中包括3条备用链路。
上述主要从第一网络设备和第二网络设备交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，网络设备(例如第一网络设备、第二网络设备)为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请中所公开的实施例描述的各示例的单元及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的技术方案的范围。
本申请实施例可以根据上述方法示例对网络设备(例如第一网络设备、第二网络设备)进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，图12A示出了上述实施例中所涉及的网络设备的一种可能的结构示意图。网络设备1200包括：处理单元1202和通信单元1203。处理单元1202用于对网络设备1200的动作进行控制管理。例如，当网络设备1200为第一网络设备时，处理单元1202用于支持网络设备1200执行图3中的步骤301-303，图7中的步骤306-307，图8中的步骤801-803和806-807，和/或用于执行本文所描述的技术的其它步骤。当网络设备1200为第二网络设备时，处理单元用于支持网络设备1200执行图3中的步骤304-305，图7中的步骤308-309，图8中的步骤804-805和808-809，和/或用于执行本文所描述的技术的其它步骤。通信单元1203用于支持网络设备1200与其它网络设备的通信。网络设备1200还可以包括存储单元1201，用于存储网络设备1200的程序代码和数据。
其中，处理单元1202可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元1203可以是通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口，例如第一网络设备与第二网络设备之间的接口。存储单元1201可以是存储器。
当处理单元1202为处理器，通信单元1203为通信接口，存储单元1201为存储器时， 本申请实施例所涉及的网络设备可以为图12B所示的网络设备。
参阅图12B所示，该网络设备1210包括：处理器1212、通信接口1213、存储器1211。可选地，网络设备1210还可以包括总线1214。其中，通信接口1213、处理器1212以及存储器1211可以通过总线1214相互连接；总线1214可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线1214可以分为地址总线、数据总线、控制总线等。为便于表示，图12B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图12A或图12B所示的网络设备可以是第一网络设备或第二网络设备。
结合本申请实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络设备中。当然，处理器和存储介质也可以作为分立组件存在于网络设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本申请实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请实施例的具体实施方式而已，并不用于限定本申请实施例的保护范围，凡在本申请实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请实施例的保护范围之内。

Claims (29)

  1. 一种保护倒换方法，其特征在于，所述方法包括：
    第一网络设备确定主用灵活以太网FlexE链路组中存在至少一条链路不可用，从预配置的备用链路中选择m条备用链路作为保护链路，其中，所述主用FlexE链路组包括逻辑上捆绑的多条链路，m为正整数，且m小于或等于所述主用FlexE链路组中的不可用链路的数量；
    所述第一网络设备向第二网络设备发送保护倒换通知，并采用所述m条保护链路替换所述至少一条不可用链路中的m条不可用链路，所述保护倒换通知用于指示所述第二网络设备采用所述m条保护链路替换所述m条不可用链路，其中，m条保护链路和m条不可用链路一一对应；
    所述第一网络设备接收所述第二网络设备发送的保护倒换响应。
  2. 根据权利要求1所述的方法，其特征在于，所述第一网络设备采用所述m条保护链路替换所述至少一条不可用链路中的m条不可用链路，包括：
    对于所述m条保护链路中的第一保护链路，若所述第一保护链路属于备用FlexE链路组，且所述第一保护链路用于替换第一不可用链路，则所述第一网络设备将所述第一不可用链路从所述主用FlexE链路组中删除，并将所述第一保护链路添加至所述主用FlexE链路组中。
  3. 根据权利要求1所述的方法，其特征在于，所述第一网络设备采用所述m条保护链路替换所述至少一条不可用链路中的m条不可用链路，包括：
    对于所述m条保护链路中的第二保护链路，若所述第二保护链路属于所述主用FlexE链路组，且所述第二保护链路用于替换第二不可用链路，则所述第一网络设备将所述第二不可用链路的时隙配置，配置到所述第二保护链路。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述保护倒换通知为FlexE信息帧，所述FlexE信息帧的目标字段中携带保护倒换信息，所述保护倒换信息用于指示所述第二网络设备采用所述m条保护链路替换所述m条不可用链路。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述方法还包括：
    若确定所述m条不可用链路中存在n条链路恢复至可用，则所述第一网络设备向所述第二网络设备发送链路恢复通知，并采用所述n条恢复至可用的链路替换n条保护链路，所述链路恢复通知用于指示所述第二网络设备采用所述n条恢复至可用的链路替换所述n条保护链路，n为正整数，且n小于或等于m；
    所述第一网络设备接收所述第二网络设备发送的链路恢复响应。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，所述第一网络设备确定主用FlexE链路组中存在至少一条链路不可用，包括：
    所述第一网络设备检测在所述主用FlexE链路组包括的各条链路上是否正确接收所述第二网络设备发送的FlexE信息帧；所述第一网络设备根据检测结果确定所述主用FlexE链路组包括的各条链路是否可用；
    和/或，
    所述第一网络设备接收所述第二网络设备发送的接收状态信息，所述接收状态信息用于指示所述第二网络设备在所述主用FlexE链路组包括的各条链路上是否正确接收所述第一网络设备发送的FlexE信息帧；所述第一网络设备根据所述接收状态信息确定所述主用FlexE链路组包括的各条链路是否可用。
  7. 根据权利要求1至6任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备向所述第二网络设备发送第一主从配置信息，所述第一主从配置信息用于指示在所述第一网络设备中配置的主从关系，以使得所述第二网络设备根据所述第一主从配置信息以及在所述第二网络设备中配置的主从关系，确定所述第一网络设备与所述第二网络设备之间的主从关系是否配置正确；
    和/或，
    所述第一网络设备接收所述第二网络设备发送的第二主从配置信息，所述第二主从配置信息用于指示在所述第二网络设备中配置的主从关系；所述第一网络设备根据所述第二主从配置信息以及在所述第一网络设备中配置的主从关系，确定所述第一网络设备与所述第二网络设备之间的主从关系是否配置正确。
  8. 一种保护倒换方法，其特征在于，所述方法包括：
    第二网络设备接收第一网络设备发送的保护倒换通知，所述保护倒换通知由所述第一网络设备在确定主用灵活以太网FlexE链路组中存在至少一条链路不可用时，从预配置的备用链路中选择m条备用链路作为保护链路后发送，所述主用FlexE链路组包括逻辑上捆绑的多条链路，所述保护倒换通知用于指示所述第二网络设备采用所述m条保护链路替换所述至少一条不可用链路中的m条不可用链路，其中，m条保护链路和m条不可用链路一一对应，m为正整数，且m小于或等于所述主用FlexE链路组中的不可用链路的数量；
    所述第二网络设备根据所述保护倒换通知，采用所述m条保护链路替换所述m条不可用链路；
    所述第二网络设备向所述第一网络设备发送保护倒换响应。
  9. 根据权利要求8所述的方法，其特征在于，所述第二网络设备采用所述m条保护链路替换所述m条不可用链路，包括：
    对于所述m条保护链路中的第一保护链路，若所述第一保护链路属于备用FlexE链路组，且所述第一保护链路用于替换第一不可用链路，则所述第二网络设备将所述第一不可用链路从所述主用FlexE链路组中删除，并将所述第一保护链路添加至所述主用FlexE链路组中。
  10. 根据权利要求8所述的方法，其特征在于，所述第二网络设备采用所述m条保护 链路替换所述m条不可用链路，包括：
    对于所述m条保护链路中的第二保护链路，若所述第二保护链路属于所述主用FlexE链路组，且所述第二保护链路用于替换第二不可用链路，则所述第二网络设备将所述第二不可用链路的时隙配置，配置到所述第二保护链路。
  11. 根据权利要求8至10任一项所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收所述第一网络设备发送的链路恢复通知，所述链路恢复通知由所述第一网络设备在确定所述m条不可用链路中存在n条链路恢复至可用后发送，所述链路恢复通知用于指示所述第二网络设备采用所述n条恢复至可用的链路替换n条保护链路，n为正整数，且n小于或等于m；
    所述第二网络设备根据所述链路恢复通知，采用所述n条恢复至可用的链路替换所述n条保护链路；
    所述第二网络设备向所述第一网络设备发送链路恢复响应。
  12. 根据权利要求8至11任一项所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备向所述第一网络设备发送接收状态信息，所述接收状态信息用于指示所述第二网络设备在所述主用FlexE链路组包括的各条链路上是否正确接收所述第一网络设备发送的FlexE信息帧。
  13. 根据权利要求8至12任一项所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收所述第一网络设备发送的第一主从配置信息，所述第一主从配置信息用于指示在所述第一网络设备中配置的主从关系；所述第二网络设备根据所述第一主从配置信息以及在所述第二网络设备中配置的主从关系，确定所述第一网络设备与所述第二网络设备之间的主从关系是否配置正确；
    和/或，
    所述第二网络设备向所述第一网络设备发送第二主从配置信息，所述第二主从配置信息用于指示在所述第二网络设备中配置的主从关系，以使得所述第一网络设备根据所述第二主从配置信息以及在所述第一网络设备中配置的主从关系，确定所述第一网络设备与所述第二网络设备之间的主从关系是否配置正确。
  14. 一种网络设备，其特征在于，所述网络设备为第一网络设备，所述网络设备包括：处理单元和通信单元；
    所述处理单元，用于确定主用灵活以太网FlexE链路组中存在至少一条链路不可用，从预配置的备用链路中选择m条备用链路作为保护链路，其中，所述主用FlexE链路组包括逻辑上捆绑的多条链路，m为正整数，且m小于或等于所述主用FlexE链路组中的不可用链路的数量；
    所述通信单元，用于向第二网络设备发送保护倒换通知，所述保护倒换通知用于指示所述第二网络设备采用所述m条保护链路替换所述至少一条不可用链路中的m条不可用链路，其中，m条保护链路和m条不可用链路一一对应；
    所述处理单元，还用于采用所述m条保护链路替换所述m条不可用链路；
    所述通信单元，还用于接收所述第二网络设备发送的保护倒换响应。
  15. 根据权利要求14所述的网络设备，其特征在于，所述处理单元，用于：
    对于所述m条保护链路中的第一保护链路，若所述第一保护链路属于备用FlexE链路组，且所述第一保护链路用于替换第一不可用链路，则将所述第一不可用链路从所述主用FlexE链路组中删除，并将所述第一保护链路添加至所述主用FlexE链路组中。
  16. 根据权利要求14所述的网络设备，其特征在于，所述处理单元，用于：
    对于所述m条保护链路中的第二保护链路，若所述第二保护链路属于所述主用FlexE链路组，且所述第二保护链路用于替换第二不可用链路，则将所述第二不可用链路的时隙配置，配置到所述第二保护链路。
  17. 根据权利要求14至16任一项所述的网络设备，其特征在于，所述保护倒换通知为FlexE信息帧，所述FlexE信息帧的目标字段中携带保护倒换信息，所述保护倒换信息用于指示所述第二网络设备采用所述m条保护链路替换所述m条不可用链路。
  18. 根据权利要求14至17任一项所述的网络设备，其特征在于，
    所述通信单元，还用于若所述处理单元确定所述m条不可用链路中存在n条链路恢复至可用，则向所述第二网络设备发送链路恢复通知，所述链路恢复通知用于指示所述第二网络设备采用所述n条恢复至可用的链路替换n条保护链路，n为正整数，且n小于或等于m；
    所述处理单元，还用于采用所述n条恢复至可用的链路替换所述n条保护链路，
    所述通信单元，还用于接收所述第二网络设备发送的链路恢复响应。
  19. 根据权利要求14至18任一项所述的网络设备，其特征在于，所述处理单元，用于：
    检测在所述主用FlexE链路组包括的各条链路上是否正确接收所述第二网络设备发送的FlexE信息帧；根据检测结果确定所述主用FlexE链路组包括的各条链路是否可用；
    和/或，
    根据所述通信单元从所述第二网络设备接收到的接收状态信息，确定所述主用FlexE链路组包括的各条链路是否可用，所述接收状态信息用于指示所述第二网络设备在所述主用FlexE链路组包括的各条链路上是否正确接收所述第一网络设备发送的FlexE信息帧。
  20. 根据权利要求14至19任一项所述的网络设备，其特征在于，
    所述通信单元，还用于向所述第二网络设备发送第一主从配置信息，所述第一主从配置信息用于指示在所述第一网络设备中配置的主从关系，以使得所述第二网络设备根据所述第一主从配置信息以及在所述第二网络设备中配置的主从关系，确定所述第一网络设备与所述第二网络设备之间的主从关系是否配置正确；
    和/或，
    所述通信单元，还用于接收所述第二网络设备发送的第二主从配置信息，所述第二主从配置信息用于指示在所述第二网络设备中配置的主从关系；所述处理单元，还用于根据所述第二主从配置信息以及在所述第一网络设备中配置的主从关系，确定所述第一网络设备与所述第二网络设备之间的主从关系是否配置正确。
  21. 一种网络设备，其特征在于，所述网络设备为第二网络设备，所述网络设备包括：处理单元和通信单元；
    所述通信单元，用于接收第一网络设备发送的保护倒换通知，所述保护倒换通知由所述第一网络设备在确定主用灵活以太网FlexE链路组中存在至少一条链路不可用时，从预配置的备用链路中选择m条备用链路作为保护链路后发送，所述主用FlexE链路组包括逻辑上捆绑的多条链路，所述保护倒换通知用于指示所述第二网络设备采用所述m条保护链路替换所述至少一条不可用链路中的m条不可用链路，其中，m条保护链路和m条不可用链路一一对应，m为正整数，且m小于或等于所述主用FlexE链路组中的不可用链路的数量；
    所述处理单元，用于根据所述保护倒换通知，采用所述m条保护链路替换所述m条不可用链路；
    所述通信单元，还用于向所述第一网络设备发送保护倒换响应。
  22. 根据权利要求21所述的网络设备，其特征在于，所述处理单元，用于：
    对于所述m条保护链路中的第一保护链路，若所述第一保护链路属于备用FlexE链路组，且所述第一保护链路用于替换第一不可用链路，则将所述第一不可用链路从所述主用FlexE链路组中删除，并将所述第一保护链路添加至所述主用FlexE链路组中。
  23. 根据权利要求21所述的网络设备，其特征在于，所述处理单元，用于：
    对于所述m条保护链路中的第二保护链路，若所述第二保护链路属于所述主用FlexE链路组，且所述第二保护链路用于替换第二不可用链路，则将所述第二不可用链路的时隙配置，配置到所述第二保护链路。
  24. 根据权利要求21至23任一项所述的网络设备，其特征在于，
    所述通信单元，还用于接收所述第一网络设备发送的链路恢复通知，所述链路恢复通知由所述第一网络设备在确定所述m条不可用链路中存在n条链路恢复至可用后发送，所述链路恢复通知用于指示所述第二网络设备采用所述n条恢复至可用的链路替换n条保护链路，n为正整数，且n小于或等于m；
    所述处理单元，还用于根据所述链路恢复通知，采用所述n条恢复至可用的链路替换所述n条保护链路；
    所述通信单元，还用于向所述第一网络设备发送链路恢复响应。
  25. 根据权利要求21至24任一项所述的网络设备，其特征在于，
    所述通信单元，还用于向所述第一网络设备发送接收状态信息，所述接收状态信息用 于指示所述第二网络设备在所述主用FlexE链路组包括的各条链路上是否正确接收所述第一网络设备发送的FlexE信息帧。
  26. 根据权利要求21至25任一项所述的网络设备，其特征在于，
    所述通信单元，还用于接收所述第一网络设备发送的第一主从配置信息，所述第一主从配置信息用于指示在所述第一网络设备中配置的主从关系；所述处理单元，还用于根据所述第一主从配置信息以及在所述第二网络设备中配置的主从关系，确定所述第一网络设备与所述第二网络设备之间的主从关系是否配置正确；
    和/或，
    所述通信单元，还用于向所述第一网络设备发送第二主从配置信息，所述第二主从配置信息用于指示在所述第二网络设备中配置的主从关系，以使得所述第一网络设备根据所述第二主从配置信息以及在所述第一网络设备中配置的主从关系，确定所述第一网络设备与所述第二网络设备之间的主从关系是否配置正确。
  27. 一种保护倒换系统，其特征在于，所述系统包括：第一网络设备和第二网络设备；
    所述第一网络设备是如权利要求14至20任一项所述的网络设备；
    所述第二网络设备是如权利要求21至26任一项所述的网络设备。
  28. 一种计算机存储介质，其特征在于，所述计算机存储介质中存储有可执行指令，所述可执行指令用于执行如权利要求1至7任一项所述的方法。
  29. 一种计算机存储介质，其特征在于，所述计算机存储介质中存储有可执行指令，所述可执行指令用于执行如权利要求8至13任一项所述的方法。
PCT/CN2017/090402 2017-06-27 2017-06-27 保护倒换方法、设备及系统 Ceased WO2019000241A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2017/090402 WO2019000241A1 (zh) 2017-06-27 2017-06-27 保护倒换方法、设备及系统
CN201780087993.2A CN110383766B (zh) 2017-06-27 2017-06-27 保护倒换方法、设备及系统
EP17915619.5A EP3618350B1 (en) 2017-06-27 2017-06-27 Protection switching method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/090402 WO2019000241A1 (zh) 2017-06-27 2017-06-27 保护倒换方法、设备及系统

Publications (1)

Publication Number Publication Date
WO2019000241A1 true WO2019000241A1 (zh) 2019-01-03

Family

ID=64740881

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/090402 Ceased WO2019000241A1 (zh) 2017-06-27 2017-06-27 保护倒换方法、设备及系统

Country Status (3)

Country Link
EP (1) EP3618350B1 (zh)
CN (1) CN110383766B (zh)
WO (1) WO2019000241A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019233403A1 (zh) * 2018-06-06 2019-12-12 中国移动通信有限公司研究院 同步信息传输方法、发送端设备、接收端设备及存储介质
US20210273826A1 (en) * 2018-11-21 2021-09-02 Huawei Technologies Co., Ltd. Communication method and communications apparatus
CN116418463A (zh) * 2021-12-30 2023-07-11 苏州盛科通信股份有限公司 灵活以太网中的自动保护切换方法和装置、存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113382430B (zh) * 2020-02-25 2022-11-01 中国电信股份有限公司 网络切片的数据传输方法、装置以及存储介质
CN114513454A (zh) 2020-11-16 2022-05-17 华为技术有限公司 一种应用在城域传送网络mtn或分片分组网络spn中的通信方法及系统
CN113794632B (zh) * 2021-08-31 2023-04-07 新华三信息安全技术有限公司 一种网络保护方法及装置
CN119814650A (zh) * 2024-12-12 2025-04-11 新华三技术有限公司 一种故障处理方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997751A (zh) * 2009-08-13 2011-03-30 中兴通讯股份有限公司 一种以太网中保护倒换的实现方法及装置
CN102833089A (zh) * 2011-06-17 2012-12-19 中兴通讯股份有限公司 一种链路保护方法及装置
EP3013017A1 (en) * 2014-10-24 2016-04-27 Ciena Corporation Channelized oduflex systems and methods for flexible ethernet and otn multiplexing
CN106803785A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种链路管理方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101399737A (zh) * 2008-10-21 2009-04-01 中兴通讯股份有限公司 用于以太环网的链路聚合组的保护方法及装置
CN102685007B (zh) * 2012-05-04 2016-11-23 华为技术有限公司 一种多链路捆绑链路组中成员链路的处理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997751A (zh) * 2009-08-13 2011-03-30 中兴通讯股份有限公司 一种以太网中保护倒换的实现方法及装置
CN102833089A (zh) * 2011-06-17 2012-12-19 中兴通讯股份有限公司 一种链路保护方法及装置
EP3013017A1 (en) * 2014-10-24 2016-04-27 Ciena Corporation Channelized oduflex systems and methods for flexible ethernet and otn multiplexing
CN106803785A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种链路管理方法及装置

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019233403A1 (zh) * 2018-06-06 2019-12-12 中国移动通信有限公司研究院 同步信息传输方法、发送端设备、接收端设备及存储介质
US20210273826A1 (en) * 2018-11-21 2021-09-02 Huawei Technologies Co., Ltd. Communication method and communications apparatus
CN116418463A (zh) * 2021-12-30 2023-07-11 苏州盛科通信股份有限公司 灵活以太网中的自动保护切换方法和装置、存储介质

Also Published As

Publication number Publication date
CN110383766B (zh) 2021-02-12
CN110383766A (zh) 2019-10-25
EP3618350B1 (en) 2024-07-31
EP3618350A4 (en) 2020-04-08
EP3618350A1 (en) 2020-03-04

Similar Documents

Publication Publication Date Title
WO2019000241A1 (zh) 保护倒换方法、设备及系统
CN108156074B (zh) 保护倒换方法、网络设备及系统
US8830825B2 (en) Method and system for priority based (1:1)n ethernet protection
KR20090050933A (ko) 이더넷 링 네트워크의 비환원 모드에서의 장애 복구 방법
CN103081406B (zh) 用于应请求通过提供商网络来恢复连接的方法和设备
CN106533736A (zh) 一种网络设备重启方法和装置
CN111884923A (zh) 冗余化装置、冗余化系统以及冗余化方法
CN113742173A (zh) 多设备集群的控制方法、设备主控装置及可读存储介质
US12289196B2 (en) Smart online link repair and job scheduling in machine learning supercomputers
WO2017000096A1 (zh) 一种链路恢复方法和网络设备
US20200244516A1 (en) Rapid Owner Selection
US20200220773A1 (en) Control device, communication system, and communication method
KR102018225B1 (ko) 연결 방법
EP2953299B1 (en) Protection switching method, system and node
CN111263250B (zh) 业务数据处理方法及设备
WO2020166425A1 (ja) ネットワーク装置、ネットワークシステム、ネットワーク接続方法、およびプログラム
CN109981374B (zh) 可自动调整信号传送路径的网络装置
CN106464524A (zh) Ason的路由计算方法和装置
EP2953294B1 (en) Protection switching method, system, and node
CN106921568A (zh) 一种网络保护方法和装置
US12425431B2 (en) Fault tolerance methodology to detect and recover network uplink fault automatically
EP4475510A1 (en) Fault tolerance methodology to detect and recover network uplink fault automatically
US12621185B2 (en) Transmission method and transmission apparatus in ring network
CN116266807B (zh) 一种业务传输的方法以及相关装置
US20090323521A1 (en) Transmission method and transmission apparatus in ring network

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017915619

Country of ref document: EP

Effective date: 20191126

NENP Non-entry into the national phase

Ref country code: DE