WO2021057350A1 - 一种灵活以太网响应链路故障的方法、装置、设备及介质 - Google Patents

一种灵活以太网响应链路故障的方法、装置、设备及介质 Download PDF

Info

Publication number
WO2021057350A1
WO2021057350A1 PCT/CN2020/110491 CN2020110491W WO2021057350A1 WO 2021057350 A1 WO2021057350 A1 WO 2021057350A1 CN 2020110491 W CN2020110491 W CN 2020110491W WO 2021057350 A1 WO2021057350 A1 WO 2021057350A1
Authority
WO
WIPO (PCT)
Prior art keywords
time slot
physical interface
slot configuration
management module
flexible ethernet
Prior art date
Application number
PCT/CN2020/110491
Other languages
English (en)
French (fr)
Inventor
钟秀琼
李爱民
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021057350A1 publication Critical patent/WO2021057350A1/zh

Links

Images

Classifications

    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/14—Monitoring arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0057—Operations, administration and maintenance [OAM]
    • H04J2203/006—Fault tolerance and recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • 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/0089—Multiplexing, e.g. coding, scrambling, SONET
    • H04J2203/0091—Time slot assignment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals

Definitions

  • the embodiments of the present application relate to, but are not limited to, the field of flexible Ethernet. Specifically, they relate to, but are not limited to, a method, device, device, and medium for flexible Ethernet to respond to link failures.
  • Ethernet service rate and the physical interface (PHYSICAL) rate have always been matched and consistent, and the rates of the two have developed simultaneously.
  • PHYSICAL physical interface
  • the speed development of the physical interface encounters a bottleneck, and the speed increase gradually slows down.
  • the price of the physical interface also drops slowly, and the cost-effectiveness of the high-speed physical interface decreases.
  • the price of a 400GE rate optical module exceeds the price of four 100GE rate optical modules, resulting in a reduction in the commercial cost performance of a 400GE rate optical module.
  • FLEXIBLE ETHERNET technology realizes the decoupling of service rate and physical channel rate.
  • the rate of the physical interface can no longer be equal to the rate of the customer's business, and the rate of the physical interface is flexible.
  • Customer services can be delivered on one or more physical channels. When customer services are delivered on multiple physical channels, multiple physical channels are bundled to form a virtual logical channel to deliver services. After decoupling the service rate and the physical channel rate, the speed of customer services can be diverse, and the rate of physical channels can also be multiple. Large-bandwidth customer services can be transmitted by logical channels that are bundled by multiple low-speed physical channels. .
  • the embodiment of the present application provides a flexible Ethernet method for responding to a link failure, which includes: when a failure of a first physical interface is detected, obtaining time slot configuration information of a client port bound to the first physical interface; Among the time slots currently used by the client port bound to the first physical interface, the remaining time slots are obtained after removing the time slots corresponding to the first physical interface; and updating the time slot configuration information according to the remaining time slots is The first time slot configuration, and according to the first time slot configuration, the service packet is sent and/or received from a physical interface that has never failed.
  • the embodiment of the present invention also provides a flexible Ethernet control device, including
  • Fault detection module drive management module, bottom management module
  • the fault detection module is used to detect whether a physical interface is faulty
  • the drive management module is used to obtain the time slot configuration information of the client port bound to the first physical interface when the first physical interface fails to transmit, and to obtain the current time slot configuration information from the client port bound to the first physical interface Among the used time slots, the remaining time slots are obtained after removing the time slots corresponding to the first physical interface; the bottom layer management module is configured to update the time slot configuration information to the first time slot configuration according to the remaining time slots .
  • An embodiment of the present application also provides a network device, including a processor, a memory, and a communication bus; the communication bus is used to implement connection and communication between the processor and the memory; the processor is used to execute one or more stored in the memory A computer program to implement the steps of the flexible Ethernet method for responding to link failures as described above.
  • the embodiments of the present application also provide a computer storage medium, the computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to realize the above The steps of the flexible Ethernet method for responding to link failures.
  • FIG. 2 is a flowchart of a method for a flexible Ethernet to respond to a link failure according to Embodiment 1 of the application;
  • FIG. 3 is a specific flowchart of a method for a flexible Ethernet to respond to a link failure according to the second embodiment of the application;
  • FIG. 5 is a schematic structural diagram of a flexible Ethernet control device provided in Embodiment 3 of the application.
  • FIG. 6 is a schematic structural diagram of a network device provided in Embodiment 4 of this application.
  • Figure 1 is a schematic diagram of a flexible Ethernet networking provided by Embodiment 1 of this application; wherein, the first device 11 has a physical interface 1 and a physical interface 3, and the second device 12 has a physical interface 2 and a physical interface. 4; Physical interface 1 and physical interface 2 are connected, and physical interface 3 and physical interface 4 are connected.
  • Flexible Ethernet 5 can bundle the first physical channel formed by physical interface 1 and physical interface 2 and the second physical channel formed by physical interface 3 and physical interface 4 into a virtual logical channel for service transfer.
  • FIG. 2 is a flowchart of a flexible Ethernet method for responding to a link failure according to Embodiment 1 of the application;
  • the first physical interface does not indicate a specific physical interface.
  • any physical interface that has failed is called the first physical interface; of course, it is also It is not excluded that there are other physical interfaces that have failed in the flexible Ethernet system in this embodiment.
  • This embodiment describes the technical solution provided in this application from the perspective of one of the physical interfaces. When multiple physical interfaces fail, the steps provided in this embodiment can all respond to the link failure through the steps provided in this embodiment. Regardless of the number of faulty physical interfaces, as long as they do not deviate from the concept of this application, they fall within the protection scope of this application.
  • the time slot of the first physical interface that has failed is removed from the time slots used by each client port corresponding to the first physical interface to obtain the remaining time slots; similarly, in other implementation processes, Multiple physical interfaces may fail, and the time slots of the failed physical interfaces are eliminated on the corresponding client ports, and the remaining available time slots will eventually be obtained.
  • S203 Update the time slot configuration information according to the remaining time slots, and send and/or receive service packets according to the updated time slot configuration on a physical interface that has never failed.
  • the remaining time slots can be used to continue to transmit service messages.
  • the time slots configured by each client port can be used, according to the updated time slot Configure the physical interface that never sends a fault to realize the transmission of service packets.
  • the updated time slot configuration is used to send and/or receive from the physical interface without failure. Before the service message, the resources allocated on the first physical interface are recovered.
  • the process of sending and/or receiving service messages from the unfaulted physical interface may be: the first device sends service messages to the unfaulted physical interface according to the updated time slot configuration.
  • the second device also only receives the service packet from the unfailed physical interface.
  • the second device extracts the transmission time slot from the overhead packet, and then according to the new transmission time slot The business message is assembled to obtain the correct business message.
  • the state of the first physical interface is also recorded and the state of the first physical interface is updated in the client to ensure that it can be unified in the flexible Ethernet system. Know the status of the physical interface, so as to realize the unification of status information among all levels in the system.
  • the time slot configuration information is checked according to the updated status information, and the time slot configuration information is adjusted to ensure that the time slot configuration information is consistent with the status information of the physical interface. It should be understood that when the time slot configuration information has been adjusted or does not need to be updated, it is no longer adjusted.
  • the status information of the first physical interface is updated.
  • the time slot corresponding to the first physical interface is added to the time slot currently used by the client port bound to the first physical interface to obtain the restored time slot. It should be understood that although the first physical interface at this time has recovered from the failure and has not yet transmitted data to the client port, according to the original configuration of the system, the client bound to the first physical interface can be obtained. port.
  • the time slot configuration information is updated according to the restored time slot to obtain the second time slot configuration. According to the second time slot configuration, the service message can be transmitted from the link where the restored first physical interface is located.
  • the second time slot configuration is not necessarily the default time slot configuration of the system, because in the actual process, there may be other physical interfaces that have failed and have not recovered.
  • the second time slot configuration in this embodiment is only It is the time slot configuration obtained after the time slot corresponding to the first physical interface is restored on the basis of the current time slot configuration; however, in some specific implementation processes, if only one physical interface fails and recovers, it will be obtained after restoration.
  • the second time slot configuration of is the initial default time slot configuration.
  • the first device sends a service packet from the non-failed interface including the first physical interface, and the second device receives the service packet on the second physical interface connected to the first physical interface,
  • the multi-frame is extracted from the overhead message, and after the multi-frame is locked, a new transmission time slot is extracted from the overhead message, and the service message is assembled according to the new transmission time slot, so as to obtain the correct service message.
  • the time slot is automatically added back to the time slot configuration, and the bandwidth is restored.
  • the transmission direction of the first device and the second device are bidirectional.
  • the above expressions only stand when the first device sends to the second device, and the second device sends service packets to the second device.
  • the steps performed are similar, so I won’t repeat them here.
  • the flexible Ethernet method for responding to link failures removes the first physical interface from the time slot currently used by the client port bound to the first physical interface when a failure of the first physical interface is detected.
  • Corresponding time slot update the time slot configuration information according to the remaining time slots, use the updated time slot configuration to transmit service messages on the physical interface that has never failed; quickly adjust the bandwidth when the link fails to ensure service transmission, and There is no need to configure additional time slots, which improves the speed of flexible Ethernet responding to link failures and reduces resource consumption.
  • FIG. 3 is a specific process of a flexible Ethernet method for responding to link failures according to Embodiment 2 of the application. Figure;
  • S302 Query the time slot configuration information of the client port bound to the failed physical interface, and record and update the state of the physical interface.
  • the time slot configuration information of the client port is obtained, and the time slot corresponding to physical interface 1 is removed from the time slot used by the client port to obtain the remaining time slot.
  • the remaining time slots at this time are all normally available time slots, that is, the time slots corresponding to physical interface 3.
  • the time slots corresponding to each faulty physical interface existing in the time slots used by the client port are respectively removed to obtain the remaining available time slots.
  • the adjusted transmission time slot is updated into the time slot configuration information.
  • the first device sends the service packet according to the new time slot configuration.
  • the first device 11 sends service packets according to the time slot configuration information. Since the time slot configuration information has been updated to use the remaining time slots to send service packets, in this embodiment, the remaining time slots are the time slots corresponding to physical interface 3. Therefore The service packet sent by the first device 11 is only sent through the physical interface 3.
  • the second device obtains a correct service message.
  • the second device 12 only receives service packets from the physical interface 4 connected to the physical interface 3. After receiving the service message, the second device 12 extracts a new transmission time slot from the overhead message, and according to the new transmission time slot, the second device 12 can assemble the correct service message.
  • Figure 4 is a specific flow chart of a method for flexible Ethernet responding to link failures according to the second embodiment of the application; the following is a comparison of this embodiment with the flexible Ethernet network structure shown in Figure 1 and Figure 4 The steps when the middle link is restored are explained:
  • the time slot currently used by the client port is the time slot corresponding to physical interface 3.
  • the status of the bound physical interface 1 is updated to UP, and the time slot corresponding to physical interface 3 is added to the time slot corresponding to physical interface 1 to obtain The recovery time slot.
  • the sending time slot of the client port is adjusted according to the recovery time slot.
  • the adjusted transmission time slot is updated into the time slot configuration information.
  • S406 The first device sends the service packet according to the new time slot configuration.
  • the first device 11 sends service packets according to the time slot configuration information. Since the time slot configuration information has been restored to use the time slots of physical interface 1 and physical interface 3 to send service packets, the service packets sent by the first device 11 pass Physical interface 1 and physical interface 3 send.
  • the second device obtains a correct service message.
  • the second device 12 receives service packets from the physical interface 2 and the physical interface 4. After receiving the service message, the second device 12 extracts the multiframe from the overhead message. After the multiframe is locked, it extracts the latest transmission time slot from the overhead message. According to the latest transmission time slot, the second device 12 Assemble the correct business message.
  • the embodiment of the application obtains the time slot configuration information and updates the state of the physical interface when a failure of the physical interface is detected, obtains the remaining time slots and adjusts the time slot configuration according to the remaining time slots; and updates the physical interface after the physical interface is restored Status and obtain the recovery time slot, and adjust the time slot configuration according to the recovery time slot. And when the link fails, the bandwidth can be adjusted quickly to ensure the transmission of the service. There is no need to configure additional time slots. After the failure is restored, the time slot is automatically adjusted to restore the bandwidth, which improves the speed of flexible Ethernet responding to link failures and reduces Resource consumption.
  • FIG. 5 is a schematic structural diagram of a flexible Ethernet control device provided in the third embodiment of the application. Please refer to FIG. 5.
  • the flexible Ethernet control device shown includes: a fault monitoring module 51 and a drive management module 52 , The bottom management module 53, the upper management module 54; the communication bus 55 connects each module;
  • the fault monitoring module 51 is used to detect whether the physical interface is faulty
  • the drive management module 52 is used to obtain the time slot configuration information of the client port bound to the first physical interface when the first physical interface fails, and to obtain the time slot currently used by the client port bound to the first physical interface , Remove the time slot corresponding to the first physical interface to obtain the remaining time slot;
  • the bottom layer control module is used to update the time slot configuration information for the first time slot configuration according to the remaining time slots;
  • the upper management module 54 is configured to record the state of the first physical interface when the first physical interface fails, update the state of the physical interface in the client, and notify the drive management module 52 after the update. After receiving the updated state information, the drive management module 52 adjusts the time slot, and notifies the bottom layer management module 53 to update the time slot configuration information according to the adjusted time slot.
  • the drive management module 52 responds quickly when the first physical interface sends a fault, adjusts the remaining time slots according to the time slot corresponding to the first physical interface and the time slot configuration information of the bound client port, and notifies the underlying control
  • the module updates the time slot configuration information; at the same time, when the first physical interface fails, the upper management module 54 also updates the status information of the physical interface in the client, and informs the drive management module 52 after the update, and the drive management module 52 according to the upper layer
  • the status information updated by the management module 54 adjusts the time slot to ensure that the relevant information at all levels in the system is consistent.
  • the drive management module 52 no longer adjusts according to the state information updated by the upper management module 54.
  • the drive management module 52 only makes adjustments to the time slot such as re-planning or scheduling.
  • the drive management module 52 does not apply its adjusted time slot configuration, but completes the time slot in the bottom management module 53. Changes in configuration information apply the adjusted time slots to the system.
  • the fault monitoring module 51 is also used to detect whether the physical interface is completely restored to normal
  • the upper management module 54 is also configured to update the state of the first physical interface after the first physical interface is completely restored to normal, and notify the drive management module 52;
  • the drive management module 52 is also configured to add the time slot corresponding to the first physical interface to the time slot currently used by the client port bound to the first physical interface after receiving the notification from the upload management module to obtain the recovery time slot , And notify the bottom layer management module 53 to update the time slot configuration to the second time slot configuration according to the restored time slot.
  • the flexible Ethernet control device provided by the embodiment of the present application can update the state of the physical interface through the upper management module when detecting a physical interface failure, and use the drive management module to adjust the time slot, and finally use the bottom management module according to the adjusted
  • the time slot update time slot configuration information and after the physical interface is restored, the time slot configuration information will be updated according to the restored time slot, and the bandwidth will be restored.
  • the flexible Ethernet can quickly respond to link failures by adjusting the bandwidth and can quickly respond to link failures. After the road is restored, the time slot and bandwidth effects are automatically restored.
  • This embodiment also provides a network device, as shown in FIG. 6, which includes a processor 61, a memory 62, and a communication bus 63, where:
  • the communication bus 63 is used to implement connection and communication between the processor 61 and the memory 62;
  • the processor 61 is configured to execute one or more computer programs stored in the memory 62 to implement at least one step in the flexible Ethernet method for responding to a link failure in the first embodiment and the second embodiment.
  • This embodiment also provides a computer-readable storage medium, which is included in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Volatile or non-volatile, removable or non-removable media.
  • Computer readable storage media include but are not limited to RAM (Random Access Memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory, charged Erasable Programmable Read-Only Memory) ), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, Or any other medium that can be used to store desired information and that can be accessed by a computer.
  • the computer-readable storage medium in this embodiment can be used to store one or more computer programs, and the stored one or more computer programs can be executed by a processor to implement the flexible Ethernet in the first and second embodiments above. At least one step of the method of responding to a link failure.
  • the time slot of a non-faulty physical interface other than the failed physical interface is used to troubleshoot the failure.
  • the time slot configuration of the client port bound to the physical interface is updated, and the service message is transmitted through the updated time slot configuration and the unfaulted physical interface.
  • fast response including but not limited to For link failure, the technical effect of service transmission is ensured by adjusting the time slot and bandwidth, and no additional time slot resources need to be configured to reduce resource consumption.
  • the functional modules/units in the system, and the device can be implemented as software (which can be implemented by computer program code executable by a computing device. ), firmware, hardware and their appropriate combination.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may consist of several physical components. The components are executed cooperatively.
  • Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit .
  • communication media usually contain computer-readable instructions, data structures, computer program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery medium. Therefore, this application is not limited to any specific combination of hardware and software.

Landscapes

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

Abstract

本申请实施例提供一种灵活以太网响应链路故障的方法、装置、设备和介质，通过检测到第一物理接口发生故障时，获取第一物理接口对应的客户端端口的时隙配置信息，从上述客户端端口所使用的时隙中，去除所述第一物理接口对应的时隙得到剩余时隙，根据剩余时隙更新时隙配置信息并按照新的时隙配置信息发送和/或接收业务报文。

Description

一种灵活以太网响应链路故障的方法、装置、设备及介质
相关申请的交叉引用
本申请基于申请号为201910902710.6、申请日为2019年9月23日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请实施例涉及但不限于灵活以太网领域，具体而言，涉及但不限于一种灵活以太网响应链路故障的方法、装置、设备及介质。
背景技术
过去的以太网技术标准中，以太网业务速率和物理接口(PHYSICAL)的速率始终保持配合和一致，两者的速率同步发展。然而当以太网业务速率提升到100GE以上时，物理接口的速度发展遇到瓶颈，速度的提升逐渐放缓，同时物理接口的价格也下降缓慢，高速物理接口的性价比降低。例如，400GE速率的光模块价格超过了4个100GE速率的光模块价格，导致400GE速率的光模块商用性价比降低。
灵活以太网(FLEXIBLE ETHERNET)技术实现了业务速率和物理通道速率的解耦，物理接口的速率可以不再等于客户业务的速率，物理接口的速率是灵活的。客户业务可以在一个或者多个物理通道上进行传递，当客户业务在多个物理通道传递时，将多个物理通道捆绑起来形成一个虚拟的逻辑通道来传递业务。业务速率和物理通道速率解耦后，客户业务的速度可以是多样的，物理通道的速率也可以是多种的，大带宽的客户业务可以由多个低速物理通道捆绑而成的逻辑通道进行传递。
然而，在将多个物理通道捆绑为逻辑通道后，若其中某个物理通道产生故 障，则可能会导致整个逻辑通道故障。通常需要通过开销进行协商调整到备用时隙，增加资源的消耗且效率低下。
发明内容
本申请实施例提供的一种灵活以太网响应链路故障的方法、装置、设备及介质。
本申请实施例提供一种灵活以太网响应链路故障的方法，包括：检测到第一物理接口发生故障时，获取所述第一物理接口绑定的客户端端口的时隙配置信息；从所述第一物理接口绑定的客户端端口当前所使用的时隙中，去除所述第一物理接口对应的时隙后得到剩余时隙；根据所述剩余时隙更新所述时隙配置信息为第一时隙配置，并按照所述第一时隙配置从未故障的物理接口发送和/或接收业务报文。
本发明实施例还提供一种灵活以太网控制装置，包括
故障检测模块、驱动管理模块、底层管理模块；
所述故障检测模块用于检测物理接口是否发生故障；
所述驱动管理模块用于在第一物理接口发送故障时，获取所述第一物理接口绑定的客户端端口的时隙配置信息，并从所述第一物理接口绑定的客户端端口当前所使用的时隙中，去除所述第一物理接口对应的时隙后得到剩余时隙；所述底层管理模块用于根据所述剩余时隙更新所述时隙配置信息为第一时隙配置。
本申请实施例还提供一种网络设备，包括处理器、存储器及通信总线；所述通信总线用于实现处理器和存储器之间的连接通信；所述处理器用于执行存储器中存储的一个或者多个计算机程序，以实现如上述灵活以太网响应链路故障的方法的步骤。
本申请实施例还提供一种计算机存储介质，所述计算机可读存储介质存储 有一个或者多个计算机程序，所述一个或者多个计算机程序可被一个或者多个处理器执行，以实现如上所述的灵活以太网响应链路故障的方法的步骤。
本发明本申请其他特征和相应的有益效果在说明书的后面部分进行阐述说明，且应当理解，至少部分有益效果从本申请说明书中的记载变的显而易见。
附图说明
图1为本申请实施例一的一种灵活以太网组网示意图；
图2为本申请实施例一提供的一种灵活以太网响应链路故障的方法的流程图；
图3为本申请实施例二提供的一种灵活以太网响应链路故障的方法的具体流程图；
图4为本申请实施例二提供的一种灵活以太网响应链路故障的方法的具体流程图；
图5为本申请实施例三提供的一种灵活以太网控制装置的结构示意图；
图6为本申请实施例四提供的一种网络设备的结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，下面通过具体实施方式结合附图对本申请实施例作进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
实施例一：
请参见图1，图1为本申请实施例一提供的一种灵活以太网组网示意图；其中，第一设备11有物理接口1和物理接口3，第二设备12有物理接口2和物理接口4；物理接口1和物理接口2连接，物理接口3和物理接口4连接。灵活以太网5可以将物理接口1和物理接口2形成的第一物理通道与物理接口3和物理接口4形成的第二物理通道捆绑为一个虚拟的逻辑通道进行业务的传递。
请参见图2，图2为本申请实施例一提供的一种灵活以太网响应链路故障的方法的流程图；
S201、检测到第一物理接口发生故障时，获取第一物理接口绑定的客户端端口的时隙配置信息。
应当说明的是，在本申请实施例中，第一物理接口并不表示一个特定的物理接口，在本申请实施例中，将任意的发生故障的物理接口称作第一物理接口；当然，也并不排除在本实施例中的灵活以太网系统中还有其他发生故障的物理接口。本实施例站在其中一个物理接口的角度，对本申请提供的技术方案进行说明，在有多个物理接口发生故障时，均可通过本实施例提供的步骤响应链路故障。无论故障物理接口的数量如何，只要在不脱离本申请构思的前提下，都属于本申请的保护范围。在灵活以太网系统中，一个客户端端口的业务可能通过一个或者多个物理接口进行传递，一个物理接口也可能传递一个或者多个客户端端口的业务；物理接口与客户端端口的绑定关系可以被配置。应当说明的是，在本申请实施例中，物理接口绑定的客户端端口仅仅是在配置中与物理接口可能具有传输关系的客户端端口，相绑定的物理接口和客户端端口并不一定正在进行消息传输，在实际应用时，客户端端口可能仅通过其绑定的一部分物理端口对业务进行传递。
通过时隙配置信息，能够反映出客户端端口在每一个物理接口处所占用的时隙。
S202、从第一物理接口绑定的客户端端口当前使用的时隙中，去除第一物理接口对应的时隙，得到剩余时隙。
由于第一物理接口出现故障，若依然通过第一物理接口的时隙对业务报文进行传递，会导致通过第一物理接口对应的时隙承载的数据无法成功通信，最终在接收端会缺少相应的数据而无法组装出完整的业务报文。
本实施中，将发生了故障的第一物理接口的时隙从第一物理接口对应的各客户端端口使用的时隙中剔除，从而得到剩余的时隙；类似的，在其他实施过程中，可能出现多个物理接口发生故障，在相应的客户端端口将故障物理接口 的时隙分别剔除，最终也会获得可用的剩余时隙。
S203、根据剩余时隙更新时隙配置信息，按照更新后的时隙配置从未故障的物理接口发送和/或接收业务报文。
由于故障物理接口的时隙被去除，剩余时隙中，都是未发生故障的物理接口的时隙，因而，可以利用剩余时隙继续对业务报文进行传输。
在得到剩余时隙后，根据剩余时隙对时隙的配置进行重新的规划，更新时隙配置信息，此时，各客户端端口配置的时隙均是能够使用的，按照更新后的时隙配置从未发送故障的物理接口实现业务报文的传输。
在一实施例中，由于第一物理接口已经发生故障，且在时隙配置中已将故障物理接口的时隙排除，在按照更新后的时隙配置从未故障的物理接口发送和/或接收业务报文之前，对分配在第一物理接口上的资源进行回收。
应当说明的是，按照更新后的时隙配置从未故障的物理接口发送和/或接收业务报文的过程可以是：第一设备按照更新后的时隙配置从未故障的物理接口发送业务报文，此时，第二设备也仅从未故障的物理接口接收到业务报文，第二设备接收到业务报文后，从开销报文中提取出发送时隙，并根据新的发送时隙对业务报文进行组装，从而获得了正确的业务报文。
在一实施例中，在检测到第一物理接口发生故障之后，还对第一物理接口的状态进行记录并在客户端中更新第一物理接口的状态，保证在灵活以太网的系统中能够统一的得知物理接口的状态，从而在系统中各层次间实现状态信息的统一。对物理接口的状态进行更新后，再根据更新后的状态信息检查时隙配置信息，对时隙配置信息进行调整，保证时隙配置信息与物理接口的状态信息一致。应当理解的是，当时隙配置信息已经被调整或不需要更新，则不再对其进行调整。
在一实施例中，当检测到第一物理接口恢复正常后，对第一物理接口的状态信息进行更新。相应的，向第一物理接口绑定的客户端端口当前使用的时隙中，再加入第一物理接口对应的时隙，得到恢复时隙。应当理解的是，此时的第一物理接口虽然从故障中恢复，还没有与进行客户端端口存在数据的传输， 但是根据系统原本的配置，能够获得到第一物理接口所绑定的客户端端口。根据恢复时隙对时隙配置信息进行更新，得到第二时隙配置，按照第二时隙配置，可以从恢复后的第一物理接口所在的链路传递业务报文。应当理解的是，第二时隙配置不一定为系统默认的时隙配置，因为在实际过程中，可能还存在其他发生故障且未恢复的物理接口，本实施例中的第二时隙配置仅仅是在当前的时隙配置基础上，将第一物理接口对应的时隙恢复后所得的时隙配置；但在某些具体实施过程中，若仅有一个物理接口产生故障并恢复，恢复后得到的第二时隙配置就是最初默认的时隙配置。
类似的，第一物理接口恢复后，第一设备从包括有第一物理接口的未故障接口发送业务报文，第二设备在与第一物理接口连接的第二物理接口接收到业务报文，从开销报文中提取复帧，复帧锁定后从开销报文中提取到新的发送时隙，根据新的发送时隙对业务报文进行组装，从而获得正确的业务报文。在此种实施方式的某些实施过程中，检测到故障的物理接口恢复后，自动将时隙添加回时隙配置，恢复了带宽。
应当说明的是，本实施例中，第一设备和第二设备的传输方向是双向的，上述表述仅仅站在第一设备发送给第二设备的情况下，第二设备发送业务报文给第一设备时，执行的步骤是类似的，在此不赘述。
本申请实施例提供的灵活以太网响应链路故障的方法，通过检测到第一物理接口发生故障时，从第一物理接口绑定的客户端端口当前使用的时隙中，去除第一物理接口对应的时隙，根据剩余的时隙更新时隙配置信息，使用更新后的时隙配置从未故障的物理接口传递业务报文；在链路发生故障时迅速调整带宽，保证业务的传输，且不需要配置额外的时隙，提高了灵活以太网响应链路故障的速度，降低了资源消耗。
实施例二：
下面结合图1所示的灵活以太网组网结构对本申请实施例作进一步说明，请参见图3，图3为本申请实施例二提供的一种灵活以太网响应链路故障的方法 的具体流程图；
S301、检测到物理接口发生故障。
在本实施例中，第一设备11和第二设备12的传输方向是双向的，本实施例站在第一设备11发送业务报文时的角度进行表述，第二设备12作为发送端发送业务报文时执行的步骤类似，在此不赘述。
若物理接口1发生故障，相应的，物理接口1所处的链路发生了故障，物理接口2也无法正常的传输业务报文。
S302、查询故障物理接口绑定的客户端端口的时隙配置信息并记录和更新物理接口的状态。
获取到物理接口1的故障信息后，查询通过物理接口1传输数据的客户端端口信息，获取到客户端端口的时隙配置信息，并且，对物理接口1的状态信息进行记录，并在客户端中更新物理接口1的状态，此时物理接口1发生故障，状态更新为DOWN(即，不可用状态)。
在查询时隙配置信息时，也可以获取其他配置信息，以辅助对链路故障的响应。
S303、从客户端端口所使用的时隙中，去除故障物理接口对应的时隙，获得剩余时隙。
获取到客户端端口的时隙配置信息，从客户端端口所使用的时隙中，去除物理接口1对应的时隙，得到剩余时隙，在如本实施例仅有一条链路发生故障的情况下，此时的剩余时隙均为正常可用的时隙，即物理接口3对应的时隙。在有多条链路发生故障时，将客户端端口所使用的时隙中存在的各故障物理接口对应的时隙分别去除，得到可用的剩余时隙。
S304、对客户端端口的发送时隙进行调整。
针对物理接口1绑定的客户端端口，根据其剩余时隙调整客户端端口的发送时隙。
S305、将调整后的时隙应用于时隙配置中。
将调整后得到的发送时隙更新入时隙配置信息中。
S306、第一设备按照新的时隙配置发送业务报文。
第一设备11根据时隙配置信息发送业务报文，由于时隙配置信息已经被更新为采用剩余时隙发送业务报文，本实施例中，剩余时隙为物理接口3对应的时隙，因此第一设备11发送的业务报文仅通过物理接口3发送。
S307、第二设备获取正确的业务报文。
相应的，第二设备12仅从与物理接口3连接的物理接口4接收到业务报文。第二设备12接收到业务报文后，从开销报文中提取出新的发送时隙，根据新的发送时隙，第二设备12能够组装出正确的业务报文。
请参见图4，图4为本申请实施例二提供的一种灵活以太网响应链路故障的方法的具体流程图；以下结合图1所示的灵活以太网组网结构和图4对本实施例中链路恢复时的步骤进行说明：
S401、检测到链路恢复。
优选的，在检测到链路恢复后，为保证链路更加稳定，不做快速响应，保证链路完全恢复正常后再执行下面的步骤。
S402、更新客户端中物理接口的状态。
在客户端中，将物理接口1的状态更新为UP，即物理接口1正常工作。
S403、向绑定的客户端端口使用的时隙中加入恢复的物理接口对应的时隙，得到恢复时隙。
客户端端口当前使用的时隙为物理接口3对应的时隙，此时其绑定的物理接口1的状态更新为UP，将物理接口3对应的时隙加上物理接口1对应的时隙获得了恢复时隙。
S404、对时隙进行调整。
针对物理接口1绑定的客户端端口，根据恢复时隙调整客户端端口的发送时隙。
S405、将调整后的时隙应用于时隙配置中。
将调整后得到的发送时隙更新入时隙配置信息中。
S406、第一设备按照新的时隙配置发送业务报文。
第一设备11根据时隙配置信息发送业务报文，由于时隙配置信息已经恢复为采用物理接口1和物理接口3的时隙发送业务报文，因此，第一设备11发送的业务报文通过物理接口1和物理接口3发送。
S407、第二设备获取正确的业务报文。
相应的，第二设备12从物理接口2和物理接口4接收到业务报文。第二设备12接收到业务报文后，从开销报文中提取到复帧，复帧锁定后，从开销报文中提取出最新的发送时隙，根据最新的发送时隙，第二设备12组装出正确的业务报文。
本申请实施例通过检测到物理接口发生故障时，获取时隙配置信息并更新物理接口的状态，获得剩余时隙根据剩余的时隙调整时隙配置；并在物理接口恢复后，更新物理接口的状态，并获得恢复时隙，根据恢复时隙调整时隙配置。并在链路发生故障时迅速调整带宽，保证业务的传输，不需要配置额外的时隙，且在故障恢复后自动调整时隙，恢复带宽，提高了灵活以太网响应链路故障的速度，降低了资源消耗。
实施例三
如图5所示，图5为本申请实施例三提供的一种灵活以太网控制装置的结构示意图，请参见图5，所示灵活以太网控制装置包括：故障监测模块51、驱动管理模块52、底层管理模块53、上层管理模块54；通信总线55连接各模块；
故障监测模块51用于检测物理接口是否发生故障；
驱动管理模块52用于在第一物理接口发生故障时，获取第一物理接口绑定的客户端端口的时隙配置信息，并从第一物理接口绑定的客户端端口当前所使用的时隙中，去除第一物理接口对应的时隙得到剩余时隙；
底层控制模块用于根据剩余时隙更新时隙配置信息为第一时隙配置；
上层管理模块54用于在第一物理接口发生故障时，记录第一物理接口的状态，并更新客户端中的物理接口的状态，并在更新后通知驱动管理模块52。驱动管理模块52接收到更新后的状态信息后，对时隙进行调整，通知底层管理模块53根据调整后的时隙对时隙配置信息进行更新。
本实施例中，驱动管理模块52在第一物理接口发送故障时快速响应，根据第一物理接口对应的时隙和绑定的客户端端口的时隙配置信息调整出剩余时隙并通知底层控制模块对时隙配置信息进行更新；同时，第一物理接口发生故障时，上层管理模块54也更新客户端中物理接口的状态信息，并在更新后通知驱动管理模块52，驱动管理模块52根据上层管理模块54更新的状态信息调整时隙，保证系统中各层次的相关信息一致。可以理解的是，若时隙配置信息已经更新或时隙配置信息与状态信息是对应一致的，则驱动管理模块52不再根据上层管理模块54更新的状态信息进行调整。本实施例中，驱动管理模块52中仅仅对时隙做出了重新规划或者编排等调整，驱动管理模块52并未应用其调整的时隙配置，而是在底层管理模块53中完成了时隙配置信息的变动，将调整的时隙应用于系统。
在一实施例中，故障监测模块51还用于检测物理接口是否完全恢复正常；
上层管理模块54还用于在第一物理接口完全恢复正常后，对第一物理接口的状态进行更新，并通知驱动管理模块52；
驱动管理模块52还用于在接收到上传管理模块的通知后，向第一物理接口绑定的客户端端口当前所使用的时隙中，加入第一物理接口对应的时隙，得到恢复时隙，并通知底层管理模块53根据恢复时隙更新时隙配置为第二时隙配置。
本申请实施例提供的灵活以太网控制装置，能够在检测到物理接口发生故障时，通过上层管理模块对物理接口状态进行更新，并利用驱动管理模块调整时隙，最终采用底层管理模块根据调整后的时隙更新时隙配置信息，并在物理接口恢复后，将根据恢复后的时隙更新时隙配置信息，恢复带宽，实现了灵活以太网通过调整带宽，快速响应链路故障并能在链路恢复后自动恢复时隙和带宽的效果。
实施例四：
本实施例还提供了一种网络设备，参见图6所示，其包括处理器61、存储器62及通信总线63，其中：
通信总线63用于实现处理器61和存储器62之间的连接通信；
处理器61用于执行存储器62中存储的一个或者多个计算机程序，以实现上述实施例一和实施例二中的灵活以太网响应链路故障的方法中的至少一个步骤。
本实施例还提供了一种计算机可读存储介质，该计算机可读存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、计算机程序模块或其他数据)的任何方法或技术中实施的易失性或非易失性、可移除或不可移除的介质。计算机可读存储介质包括但不限于RAM(Random Access Memory，随机存取存储器),ROM(Read-Only Memory，只读存储器),EEPROM(Electrically Erasable Programmable read only memory，带电可擦可编程只读存储器)、闪存或其他存储器技术、CD-ROM(Compact Disc Read-Only Memory，光盘只读存储器)，数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。
本实施例中的计算机可读存储介质可用于存储一个或者多个计算机程序，其存储的一个或者多个计算机程序可被处理器执行，以实现上述实施例一和实施例二中的灵活以太网响应链路故障的方法的至少一个步骤。
根据本申请实施例提供的一种灵活以太网响应链路故障的方法、装置、设备及介质，通过在检测到物理接口发生故障时，使用故障物理接口以外的未故障物理接口的时隙对故障物理接口绑定的客户端端口的时隙配置进行更新，通过更新后的时隙配置以及未故障的物理接口进行业务报文的传递，在某些实施过程中可实现包括但不限于的快速响应链路故障，通过调整时隙和带宽保证业务传输的技术效果，且不需要配置额外的时隙资源，减少资源消耗。
可见，本领域的技术人员应该明白，上文中所公开方法中的全部或某些步 骤、系统、装置中的功能模块/单元可以被实施为软件(可以用计算装置可执行的计算机程序代码来实现)、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。
此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、计算机程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。所以，本申请不限制于任何特定的硬件和软件结合。
以上内容是结合具体的实施方式对本申请实施例所作的进一步详细说明，不能认定本申请的具体实施只局限于这些说明。对于本申请所属技术领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本申请的保护范围。

Claims (10)

  1. 一种灵活以太网响应链路故障的方法，包括：
    检测到第一物理接口发生故障时，获取所述第一物理接口绑定的客户端端口的时隙配置信息；
    从所述第一物理接口绑定的客户端端口当前所使用的时隙中，去除所述第一物理接口对应的时隙后得到剩余时隙；
    根据所述剩余时隙更新所述时隙配置信息为第一时隙配置，并按照所述第一时隙配置从未故障的物理接口发送和/或接收业务报文。
  2. 如权利要求1所述的灵活以太网响应链路故障的方法，其中，所述检测到第一物理接口发生故障后还包括：
    记录所述第一物理接口的状态信息，对客户端中记录的所述第一物理接口的状态信息进行更新；
    并根据更新后的状态信息调整所述时隙配置信息。
  3. 如权利要求2所述的灵活以太网响应链路故障的方法，其中，还包括:
    检测到所述第一物理接口恢复正常后，对客户端中记录的所述第一物理接口的状态信息进行更新；
    向所述第一物理接口绑定的客户端端口当前所使用的时隙中，加入所述第一物理接口对应的时隙后得到恢复时隙；
    根据所述恢复时隙更新所述时隙配置信息为第二时隙配置，并按照所述第二时隙配置从未故障的物理接口发送和/或接收业务报文。
  4. 如权利要求1所述的灵活以太网响应链路故障的方法，其中，所述按照所述第一时隙配置从未故障的物理接口发送和/或接收业务报文之前，还包括：回收所述第一物理接口上分配的资源。
  5. 如权利要求1或2任一项所述的灵活以太网响应链路故障的方法，其中，所述从未故障的物理接口发送和/或接收业务报文包括：
    第一设备按照时隙配置信息中配置的时隙从未故障的物理接口发送业务报 文；
    第二设备接收到所述业务报文后，从开销报文中提取出发送时隙，根据所述发送时隙获取正确的业务报文信息。
  6. 一种灵活以太网控制装置，包括：故障检测模块、驱动管理模块、底层管理模块；
    所述故障检测模块用于检测物理接口是否发生故障；
    所述驱动管理模块用于在第一物理接口发生故障时，获取所述第一物理接口绑定的客户端端口的时隙配置信息，并从所述第一物理接口绑定的客户端端口当前所使用的时隙中，去除所述第一物理接口对应的时隙后得到剩余时隙；
    所述底层管理模块用于根据所述剩余时隙更新所述时隙配置信息为第一时隙配置。
  7. 如权利要求6所述的灵活以太网控制装置，其中，还包括：上层管理模块；
    所述上层管理模块用于记录所述第一物理接口的状态信息，对客户端中记录的所述第一物理接口的状态信息进行更新；
    所述驱动管理模块还用于根据更新后的状态信息调整时隙，并通知所述底层管理模块根据调整后的时隙更新时隙配置信息。
  8. 如权利要求7所述的灵活以太网控制装置，其中，所述故障检测模块还用于检测物理接口是否完全恢复正常；
    所述上层管理模块还用于在所述第一物理接口完全恢复正常后，对客户端中记录的所述第一物理接口的状态信息进行更新，并通知所述驱动管理模块；
    所述驱动管理模块还用于在接收到所述上层管理模块的通知后，向所述第一物理接口绑定的客户端端口当前所使用的时隙中，加入所述第一物理接口对应的时隙后得到恢复时隙，并通知所述底层管理模块根据所述恢复时隙更新所述时隙配置信息为第二时隙配置。
  9. 一种网络设备，所述网络设备包括处理器、存储器及通信总线；
    所述通信总线用于实现处理器和存储器之间的连接通信；
    所述处理器用于执行存储器中存储的一个或者多个计算机程序，以实现如 权利要求1-5中任一项所述的灵活以太网响应链路故障的方法的步骤。
  10. 一种计算机可读存储介质，其中，所述计算机可读存储介质存储有一个或者多个计算机程序，所述一个或者多个计算机程序可被一个或者多个处理器执行，以实现如权利要求1-5所述的灵活以太网响应链路故障的方法的步骤。
PCT/CN2020/110491 2019-09-23 2020-08-21 一种灵活以太网响应链路故障的方法、装置、设备及介质 WO2021057350A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910902710.6A CN112543113A (zh) 2019-09-23 2019-09-23 一种灵活以太网响应链路故障的方法、装置、设备及介质
CN201910902710.6 2019-09-23

Publications (1)

Publication Number Publication Date
WO2021057350A1 true WO2021057350A1 (zh) 2021-04-01

Family

ID=75013154

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/110491 WO2021057350A1 (zh) 2019-09-23 2020-08-21 一种灵活以太网响应链路故障的方法、装置、设备及介质

Country Status (2)

Country Link
CN (1) CN112543113A (zh)
WO (1) WO2021057350A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024082668A1 (zh) * 2022-10-21 2024-04-25 华为技术有限公司 一种故障信息通知方法及其相关设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115695190A (zh) * 2021-07-26 2023-02-03 中兴通讯股份有限公司 灵活以太网时隙协商方法、接收端、发送端及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109218061A (zh) * 2017-07-07 2019-01-15 中兴通讯股份有限公司 灵活以太网之故障通知及获取方法、装置、通信设备
CN109309530A (zh) * 2017-07-28 2019-02-05 中兴通讯股份有限公司 一种数据传输方法和装置
CN109688016A (zh) * 2019-01-25 2019-04-26 中兴通讯股份有限公司 灵活以太网协议中切换时隙配置的方法及相关设备
WO2019128887A1 (zh) * 2017-12-26 2019-07-04 华为技术有限公司 一种灵活以太网中故障指示方法以及装置
WO2019165991A1 (zh) * 2018-03-01 2019-09-06 中兴通讯股份有限公司 基于灵活以太网的业务保护方法、服务器及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109218061A (zh) * 2017-07-07 2019-01-15 中兴通讯股份有限公司 灵活以太网之故障通知及获取方法、装置、通信设备
CN109309530A (zh) * 2017-07-28 2019-02-05 中兴通讯股份有限公司 一种数据传输方法和装置
WO2019128887A1 (zh) * 2017-12-26 2019-07-04 华为技术有限公司 一种灵活以太网中故障指示方法以及装置
WO2019165991A1 (zh) * 2018-03-01 2019-09-06 中兴通讯股份有限公司 基于灵活以太网的业务保护方法、服务器及存储介质
CN109688016A (zh) * 2019-01-25 2019-04-26 中兴通讯股份有限公司 灵活以太网协议中切换时隙配置的方法及相关设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024082668A1 (zh) * 2022-10-21 2024-04-25 华为技术有限公司 一种故障信息通知方法及其相关设备

Also Published As

Publication number Publication date
CN112543113A (zh) 2021-03-23

Similar Documents

Publication Publication Date Title
US10114713B1 (en) Systems and methods for preventing split-brain scenarios in high-availability clusters
US8892936B2 (en) Cluster wide consistent detection of interconnect failures
US8874974B2 (en) Synchronizing a distributed communication system using diagnostic heartbeating
US6658595B1 (en) Method and system for asymmetrically maintaining system operability
EP3107251B1 (en) Packet transmission method and device
EP3518500B1 (en) Arbitration method, apparatus, and system used in active-active data centers
WO2021057350A1 (zh) 一种灵活以太网响应链路故障的方法、装置、设备及介质
WO2017050254A1 (zh) 热备方法、装置及系统
US20120281525A1 (en) METHOD AND SYSTEM FOR PRIORITY BASED (1:1)n ETHERNET PROTECTION
CN109391691A (zh) 一种单节点故障下nas服务的恢复方法及相关装置
US10931531B2 (en) Bandwidth-based virtual router redundancy protocol node designation
CN108512753B (zh) 一种集群文件系统中消息传输的方法及装置
US11611816B2 (en) Service data processing method and device
US20140298076A1 (en) Processing apparatus, recording medium storing processing program, and processing method
CN109445984B (zh) 一种业务恢复方法、装置、仲裁服务器以及存储系统
JP6134720B2 (ja) 接続方法
CN111224803B (zh) 一种堆叠系统中多主检测方法及堆叠系统
CN106020975A (zh) 数据操作方法、装置和系统
CN110601972A (zh) 一种报文传输方法、装置及智能弹性架构系统
US11947431B1 (en) Replication data facility failure detection and failover automation
WO2024067051A1 (zh) 一种多az仲裁系统及方法
US11949597B2 (en) Platform independent on demand network management and monitoring
CN112214466B (zh) 分布式集群系统及数据写入方法、电子设备、存储装置
CN117555493B (zh) 数据处理方法、系统、装置、存储介质及电子设备
WO2021000647A1 (zh) 一种业务保护方法、网络设备、分布式业务处理系统及存储介质

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20869704

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 22.02.23)

122 Ep: pct application non-entry in european phase

Ref document number: 20869704

Country of ref document: EP

Kind code of ref document: A1