WO2017000250A1 - 一种业务恢复方法和控制器 - Google Patents

一种业务恢复方法和控制器 Download PDF

Info

Publication number
WO2017000250A1
WO2017000250A1 PCT/CN2015/082888 CN2015082888W WO2017000250A1 WO 2017000250 A1 WO2017000250 A1 WO 2017000250A1 CN 2015082888 W CN2015082888 W CN 2015082888W WO 2017000250 A1 WO2017000250 A1 WO 2017000250A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
path
bandwidth
compressed
services
Prior art date
Application number
PCT/CN2015/082888
Other languages
English (en)
French (fr)
Inventor
郑好棉
林毅
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2015/082888 priority Critical patent/WO2017000250A1/zh
Priority to CN201580081339.1A priority patent/CN107710698B/zh
Publication of WO2017000250A1 publication Critical patent/WO2017000250A1/zh

Links

Images

Definitions

  • the present invention relates to communication networks and, more particularly, to a service recovery method and controller.
  • PCE is a centralized path calculation unit mainly used to implement complex path calculation.
  • PCE usually has resource information of the network, including topology, nodes, and current resource usage. After receiving the request from the PCC (Path Computation Client), the PCE returns the path information to the PCC through a routing algorithm combined with the available resources of the current network.
  • the IETF The Internet Engineering Task Force
  • PCE label Switched Paths
  • LSPs Label Switched Paths
  • PCE is called stateful PCE (stateful PCE).
  • LSP Delegation function is also defined. After the PCC grants the modification right of an LSP to the PCE, the Stateful PCE can modify the LSP when necessary and notify the corresponding PCC to respond. LSP update.
  • VTS Virtual Transport Service
  • the physical resources are divided into virtualized network controllers by the transport network controller, and are divided into virtual network topologies according to user requirements, and then provided to different tenants.
  • the resources of different tenants are independent of each other and do not feel each other.
  • Each transport network customer has a CC (Client Controller) to manage its own virtual network.
  • the embodiment of the present invention provides a service recovery method, where the method includes: detecting that a first path carrying a first service fails, the first service is a degradable service; determining the first Whether the available bandwidth on the second path between the first node and the last node corresponding to the service is sufficient to recover the first service; when the available bandwidth on the second path is insufficient to recover the first service, compressing the The first service, the bandwidth of the compressed first service is smaller than the available bandwidth of the second path, and the compressed first service is switched to the second path.
  • an embodiment of the present invention provides a controller, including: a detecting unit, configured to detect whether a first path carrying a first service fails, the first service is a degradable service; And determining, after the detecting unit detects the first path fault, whether the available bandwidth on the second path between the first node and the last node corresponding to the first service is sufficient to recover the first service; and the compressing unit is configured to: When the available bandwidth on the second path is insufficient to recover the first service, the first service is compressed, and the bandwidth of the compressed first service is smaller than the available bandwidth of the second path; And configured to switch the compressed first service to the second path.
  • an embodiment of the present invention provides a controller, including a memory and a processor, where The memory is configured to store an instruction; the processor is configured to: run the memory stored instruction to: detect that the first path carrying the first service fails, the first service is a degradable service; Whether the available bandwidth on the second path between the first node and the last node corresponding to the first service is sufficient to recover the first service; when the available bandwidth on the second path is insufficient to recover the first service Compressing the first service, the bandwidth of the compressed first service is smaller than the available bandwidth of the second path, and switching the compressed first service to the second path.
  • the solution of the embodiment of the present invention can improve the resource recovery by reducing the degraded service when the remaining resources between the first and last nodes corresponding to the service affected by the fault are insufficient, but are insufficient to meet the recovery service. Utilization and optimize the user experience.
  • FIG. 1 is a schematic diagram of a network topology involved in a service recovery method according to an embodiment of the present invention
  • Embodiment 2 is an interaction diagram of a transport network controller and a client controller in the network topology of Embodiment 1;
  • FIG. 3 is a schematic diagram of a network topology involved in a service recovery method according to Embodiment 2 of the present invention.
  • FIG. 4 is a schematic diagram of a network topology involved in a service recovery method according to Embodiment 3 of the present invention.
  • FIG. 5 is an interaction diagram of a transport network controller and a client controller in the network topology of Embodiment 3;
  • FIG. 6 is an interaction diagram of a transport network controller and a client controller in the network topology of Embodiment 4;
  • FIG. 7 is a flowchart of an embodiment of a service recovery method according to Embodiment 5 of the present invention.
  • FIG. 8 is a structural diagram of a controller according to Embodiment 6 of the present invention.
  • FIG. 9 is a schematic diagram of an embodiment of a general purpose computer system.
  • the attributes of the data are not perceived and treated equally, which is closely related to the text format of the transmitted content.
  • the traditional transmission service it is usually the original data such as text and voice.
  • the compression ratio of this type of data is not high. Once the loss is lost, the impact on the transmission effect is very obvious, which will greatly affect the user experience.
  • This type of service is called non-degradable service.
  • the non-degradable service is a business that is sensitive to packet loss. For today's and even the future of the transport network services, the higher proportion of the pipeline is similar to media data such as pictures and videos.
  • This type of data can be compressed at a predetermined ratio according to needs.
  • the short interruption of the service does not directly affect User experience, this type of business is called degradable business. Since the degradable service is a service that can be compressed according to a predetermined ratio according to needs, the degradable service is a service that is not sensitive to packet loss, and the user can accept a short interruption of the degradable service.
  • the service type is identified at the transport network level, and some of the transport services mainly transmit media data or other degradable services, and may perform partial recovery when the bandwidth resources are insufficient.
  • FIG. 1 is a schematic diagram of a network topology involved in a service recovery method according to an embodiment of the present invention
  • FIG. 2 is an interaction diagram of a transport network controller and a client controller in an embodiment network topology.
  • the network of Figure 1 includes Node A, Node B, and Node C.
  • Figure 2 shows the transport network controller and the client controller.
  • the bandwidth on the link between Node A and Node B is 100 G. Between Node A and Node C. Bandwidth is 10G, Node B and Node C
  • the bandwidth between the nodes is 10G, the link between the node A and the node B carries the service one, and the composition data of the service one is the media data.
  • the link between node A and node B fails, the service is interrupted.
  • the link interruption between node A and node B is first perceived by the transport network controller, and the transport network controller reroutes the service one. Since the node A is the first node, and the remaining resources on the recovery path ACB with the node B as the last node are only 10G, it is not enough to restore all the services requiring 100G bandwidth.
  • the transport network controller notifies the client of the fault condition. And notify the client controller of the remaining resources on the path ACB that are insufficient to recover the traffic one and the remaining bandwidth between the ACBs.
  • the client controller checks the service attribute of the faulty service, that is, checks the service attribute of the service one, and the client controller checks that the attribute of the service one is degradable "media data", and the service one can Do a 10:1 ratio compression process.
  • the client controller 102 determines to recover the failed service using the 10G bandwidth resource of the A-C-B, that is, restores the service one, and transmits the recovery plan to the transport network controller 101.
  • the transport network controller 101 compresses the service according to a ratio of 10:1, and then switches the compressed service to the ACB path, and the service 1 is carried by the 10G bandwidth link of the ACB. .
  • step S20 the client controller can also determine that the compression ratio of 10:1 will seriously affect the quality and decide not to use the resources of A-C-B. At this time, the recovery scheme can be rejected, resulting in recovery failure.
  • FIG. 3 is a schematic diagram of a network topology involved in a service recovery method according to Embodiment 2 of the present invention.
  • the network of FIG. 1 includes a node A, a node B, and a node C.
  • four services are carried between the AB links.
  • the service attributes of the four services, the bearer link and the occupied bandwidth are as shown in Table 1.
  • the four services are degraded "media data services", in which the bandwidth occupied by the service 1 is 10G, and the bandwidth occupied by the service 2 is 20G.
  • the bandwidth occupied by service three is 30G, and the bandwidth occupied by service four is 40G.
  • the above four services are interrupted.
  • the fault is first perceived by the transport network controller and initiates rerouting of the four services that are interrupted within the network of the client controller (in this embodiment, the three nodes of the A-B-C in FIG. 1). If the solution of the embodiment of the present invention is not used, the service 1 can be recovered on the alternate path A-C-B, and the remaining three services all fail to recover.
  • the recovery resource since the first node is the node A and the last node is the node B, the recovery resource only has 10G resources on the ACB path, which is insufficient to recover all four interrupt services. Therefore, as shown in step S301, the transport network control is performed.
  • the client controller checks the service attributes of the four services after receiving the message. When it is determined that the attributes of the four services are all degradable "media data services" (meaning compressible), in step S303, the client controller decides to use the 10G resources of the ACB to recover all the above four services, each recovering 10% of the bandwidth.
  • the recovery scheme is as shown in Table 2. The client controller sends the recovery scheme to the transport network controller.
  • step S304 after receiving the recovery plan, the transport network controller accepts the recovery plan and resumes according to the plan. If the recovery is successful, all four services are carried by the A-C-B 10G link, and the transceiver end of the service will select the best transmission scheme according to the new bandwidth to ensure maximum QoS.
  • the foregoing embodiment complies with the following process: after the transport network controller senses the fault and determines that the resource is restored, the resource that can be used for recovery and the service that needs to be restored are reported to the client controller, and the recovery plan is formulated by the client controller.
  • the embodiment of the present invention may also formulate a recovery scheme by the transport network controller.
  • the transport network controller When the transport network controller senses the fault, it can also check the attributes of the damaged service, determine the damaged service as the original data service or the media data service, and allocate the available recovery bandwidth to different services. After the recovery is completed, the updated service distribution is reported to the client controller.
  • the attributes of the check service 1234 are media data services, and the transport network controller can complete the recovery of the four services by using the 10G bandwidth of the ACB. And generate a recovery plan as shown in Table 2. After the recovery is completed, Table 2 is reported to the client controller for subsequent maintenance of the service and network by the client controller.
  • FIG. 4 is a schematic diagram of a network topology involved in a service recovery method according to Embodiment 3 of the present invention
  • FIG. 5 is an interaction diagram of a transport network controller and a client controller in the network topology of Embodiment 3.
  • the network of FIG. 4 includes node A, node B, and node C.
  • FIG. 5 shows the transport network controller and the client controller.
  • the bandwidth on the link between node A and node B in FIG. 4 is 100 G, node A and node.
  • the bandwidth between C is 20G
  • the bandwidth between Node B and Node C is 20G
  • the link between Node A and Node B carries four services, of which
  • the service attribute of the service 1 is the non-degradable original data service
  • the service 2, the service 3, and the service 4 are degradable media data services.
  • the bandwidth occupied by the service 1 is 10 G
  • the bandwidth occupied by the service 2 is 20 G
  • the service 3 is occupied.
  • the bandwidth of the service is 30G
  • the bandwidth occupied by the service four is 40G.
  • the above four services are interrupted.
  • the fault is first perceived by the transport network controller, and all services that are interrupted are rerouted within the network of the client controller (in this embodiment, the network of the three nodes A-B-C in FIG. 3). Since the node A is the first node, the remaining resources on the recovery path ACB with the node B as the last node are only 20G, which is not enough to recover all the four interrupt services. Therefore, as shown in step S501, the transport network controller will fault, and It cannot be fully recovered, and all bandwidth resources are reported to the client controller in a total of 20G.
  • the client controller checks the service attributes of the four services after receiving the message.
  • the client controller checks that the service-attribute is a non-degradable "raw data service”, meaning that it is incompressible and must be fully restored, and the remaining service attributes are degradable "media data services”, meaning compressible.
  • the client controller preferentially allocates the recovery bandwidth to the service one, and decides to use the remaining 10G resources of the link ACB to recover the service 2, the service 3, and the service 4.
  • the recovery scheme is as shown in Table 4, and the client controller restores the service.
  • the solution is sent to the transport network controller.
  • step S504 after receiving the recovery plan, the transport network controller accepts the recovery plan and resumes according to the plan. If the recovery is successful, all four services are carried by the A-C-B 20G link, and the transceiver end of the service will select the best transmission scheme according to the new bandwidth to ensure maximum QoS.
  • the present invention does not limit which data is selected for transmission by the service transceiver.
  • FIG. 6 is an interaction diagram of a transport network controller and a client controller in the network topology of the fourth embodiment.
  • the network of FIG. 4 includes node A, node B, node C, and node A and node B in FIG.
  • the bandwidth on the link is 100G
  • the bandwidth between node A and node C is 20G
  • the bandwidth between node B and node C is 20G
  • the link AB between node A and node B carries four services.
  • Service 1 , Service 2, Service 3 and Service 4 are all degradable media data services.
  • the bandwidth occupied by the service 1 is 10 G
  • the bandwidth occupied by the service 2 is 20 G
  • the bandwidth occupied by the service 3 is 30 G. It is 40G.
  • the link A-C-B carries the service 5
  • the service 5 is also the degradable media data service
  • the bandwidth occupied by the service 5 is 20G.
  • the bearer services and attribute distributions in the current network are shown in Table 5:
  • the service When the A-B link fails, the service is interrupted by one, two, three, and four.
  • the fault is first perceived by the transport network controller, and all services that are interrupted are rerouted within the network of the client controller (in this embodiment, the network of the three nodes of A-B-C in FIG. 4).
  • the transport network controller After receiving the fault, the transport network controller will make the following judgment: since the available resources of the link ACB in the first node being the end node A are occupied by the service five and the service 5 is the degradable media data. Business means that business five can be compressed, so the business has a chance to recover in 1234.
  • the transport network returns the conclusion that the recovery cannot be fully recovered and the recovery opportunity is returned to the client controller in step S601.
  • the feedback form is not limited.
  • the transport network controller can inform the client that the controller can recover the service by 20G.
  • the client controller checks the service attributes of the five services. When it is determined that the attributes of the five services are both degradable "media data services" (meaning compressible), the client in step S603 The controller decides to use the 20G resource of the ACB to simultaneously carry the service 1234.
  • the recovery scheme is shown in Table 6. The client controller sends the recovery scheme to the transport network controller.
  • the transport network controller accepts the recovery plan and resumes according to the plan. If the recovery is successful, all five services are carried by the 20G link of A-C-B, and the transceiver end of the service will be rooted. Based on the new bandwidth, choose the best transmission solution to ensure maximum QoS.
  • the present invention does not limit which data is selected for transmission by the service transceiver.
  • FIG. 7 is a flowchart of an embodiment of a service recovery method according to Embodiment 5 of the present invention, where the service recovery method includes:
  • the transport network controller detects that the first path that carries the first service is faulty, and the first service is a degradable service.
  • the first path may be carried by multiple services including the first service, and the multiple services may be degradable services, and the service recovery method may further include: compressing the multiple services.
  • the other service except the first service; the compressed other service is switched to the second path, where the sum of the bandwidth of the compressed first service and the compressed other service is not greater than The available bandwidth of the second path.
  • the compression ratio of the first service and the other services is determined according to the service type and priority of the first service and the other services.
  • the multiple services are degradable services
  • the first path may include a second service that cannot be degraded in the multiple services that are included in the first service that are carried before the fault.
  • the service recovery method may further include: switching the second service to the second path, where the sum of the bandwidth of the compressed first service and the bandwidth of the second service is not greater than The available bandwidth of the second path.
  • the second service since the second service cannot be degraded, the second service is not compressed before the handover.
  • the transport network controller determines whether the available bandwidth on the second path between the first node and the last node corresponding to the first service is sufficient to recover the first service.
  • the available bandwidth of the transport network controller on the second path is insufficient to restore the first industry.
  • the first service is compressed, and the bandwidth of the compressed first service is smaller than the available bandwidth of the second path;
  • the service recovery method may further include: the transport network controller collecting a recovery plan from the client controller corresponding to the first service, where the recovery plan includes a compression ratio of the first service;
  • the first service includes: the transport network controller compresses the first service according to a compression ratio of the first service.
  • the transport network controller switches the compressed first service to the second path.
  • the second path may be originally carrying the degradable third service, and the second path is not sufficient to carry the third service, and the available bandwidth is insufficient to recover according to the compression ratio in the recovery scheme.
  • the first service in this case, before the compressed first service is switched to the second path, the service recovery method may further include: compressing the third service to increase the available of the second path Bandwidth until the available bandwidth of the second path is sufficient to recover the first service at a compression ratio in the recovery scheme.
  • the solution of the embodiment of the present invention can improve the resource recovery by reducing the degraded service when the remaining resources between the first and last nodes corresponding to the service affected by the fault are insufficient, but are insufficient to meet the recovery service. Utilization and optimize the user experience.
  • the controller may be a transport network controller corresponding to the service recovery method of the foregoing embodiment, and the controller includes:
  • the detecting unit 801 is configured to detect whether a first path carrying the first service is faulty, and the first service is a degradable service;
  • a determining unit 802 configured to determine, after the detecting unit detects the first path fault, the first service Whether the available bandwidth on the second path between the corresponding head node and the last node is sufficient to recover the first service;
  • a compression unit 803 configured to compress the first service when the available bandwidth on the second path is insufficient to recover the first service, where a bandwidth of the compressed first service is smaller than that of the second path Available bandwidth
  • the switching unit 804 is configured to switch the compressed first service to the second path.
  • the first path may carry multiple services including the first service before the fault, and other services other than the first service in the multiple services are also degradable services.
  • the compression unit is further configured to: compress another service except the first service of the multiple services; the switching unit is further configured to: switch the compressed other service to the second path, where The sum of the bandwidth occupied by the compressed first service and the compressed other service is not greater than the available bandwidth of the second path.
  • These components can be used with any common network component, such as a computer or network component with sufficient processing power, memory resources, and network throughput capabilities to collectively handle the amount of work it undertakes.
  • FIG. 9 shows a typical general network group 900 that is suitable for implementing one or more embodiments for the components disclosed herein.
  • Network component 900 can include a processor 902 (which can be referred to as a central processing unit or CPU) that can be in communication with any memory device, including auxiliary memory 903, read only memory (ROM) 904, random access memory (RAM) 905, input. /output (I/O) device 901, network connection device 906, or a combination of these devices.
  • the processor 902 can function as one or more CPU chips or as part of one or more application specific integrated circuits (ASICs).
  • ASICs application specific integrated circuits
  • Secondary storage 903 typically includes one or more disk drives or tape drives for numbering According to the non-volatile storage, if the RAM 905 is not large enough to process all working data, it can be used as an overflow data storage device. When the program loaded onto the RAM 905 is selected and executed, the auxiliary memory 903 can be used to store these programs.
  • ROM 904 is used to store the read instructions and possible data during program execution.
  • the ROM 904 is a non-volatile storage device having a small memory capacity with respect to the auxiliary memory 903 of a larger memory capacity.
  • RAM 905 is used to store volatile data and perhaps store instructions. Accessing ROM 904 and RAM 905 is typically faster than accessing auxiliary storage 903.
  • R R l + k * (R u - R l ), where k is a variable between 1% and 100% in increments of 1%, ie k is 1% 2%, 3%, 4%, 5%, up to 50%, 51%, 52%, up to 95%, 96%, 97%, 98%, 99% or 100%.
  • R R l + k * (R u - R l ), where k is a variable between 1% and 100% in increments of 1%, ie k is 1% 2%, 3%, 4%, 5%, up to 50%, 51%, 52%, up to 95%, 96%, 97%, 98%, 99% or 100%.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例提供了一种业务恢复方法和对应的控制器,该业务恢复方法包括:检测到承载第一业务的第一路径发生故障,所述第一业务为可降质的业务；确定所述第一业务对应的首节点和末节点之间的第二路径上的可用带宽是否足以恢复所述第一业务；在所述第二路径上的可用带宽不足以恢复所述第一业务时，压缩所述第一业务，所述压缩后的第一业务的带宽小于所述第二路径的可用带宽；将压缩后的所述第一业务切换到所述第二路径。本发明实施例的方案在发现故障影响的业务对应的首末节点间有剩余资源但不足以满足恢复中断业务时，压缩可降质的业务，达到节省带宽的同时实现业务的恢复，可以提高资源利用率和优化用户体验。

Description

一种业务恢复方法和控制器 技术领域
本发明涉及通信网络，更具体地，涉及业务恢复方法和控制器。
发明背景
PCE(Path Computation Element，路径计算单元)是一个集中式的路径计算单元，主要用于实现复杂的路径计算。PCE通常有网络的资源信息，包括拓扑，节点，当前资源使用情况。PCE在收到从PCC(Path Computation Client，路径计算客户端)的请求后，通过路由算法，结合当前网络可用资源，给PCC返回路径信息。
为了丰富PCE的动态能力，IETF(The Internet Engineering Task Force，国际互联网工程任务组)标准组织对PCE功能又进行了扩展，使其能够获取LSP(Label Switched Path，标签交换路径)，这种类型的PCE被称为stateful PCE(有状态PCE)。此外，还定义LSP Delegation(LSP代理)功能，也就是说在PCC将某一条LSP的修改权利授予给PCE后，Stateful PCE可以在必要的时候对这条LSP进行修改，并通知对应的PCC做对应的LSP更新。
VTS(Virtual Transport Service，虚拟传送服务)是为传送网用户提供虚拟服务的一种方式。在该传送网架构中，物理资源被传送网控制器进行虚拟化划分，根据用户需求划分成一个个虚拟的网络拓扑，然后提供给不同租户，不同租户之间资源互相独立，不会感受到彼此的存在。每个传送网的客户拥有CC(Client Controller，客户控制器)来管理自己的虚拟网络。
在现有的传送网恢复方案中，当一个节点至另一个节点之间的带宽为固定值的链路发生故障导致业务中断时，系统会重新计算一条相同带宽的链路并将中断业务加载在新计算的路径上。当两个节点之间没有相同带宽的恢复链路时，链路恢复失败。
发明内容
结合下列的具体实施方案以及相关附图和权利要求，能够更明确地了解上述特征和其他特征。
一方面，本发明实施例提供了一种业务恢复方法,所述方法包括:检测到承载第一业务的第一路径发生故障,所述第一业务为可降质的业务；确定所述第一业务对应的首节点和末节点之间的第二路径上的可用带宽是否足以恢复所述第一业务；在所述第二路径上的可用带宽不足以恢复所述第一业务时，压缩所述第一业务，所述压缩后的第一业务的带宽小于所述第二路径的可用带宽；将压缩后的所述第一业务切换到所述第二路径。
另一方面，本发明实施例提供了一种控制器，包括：检测单元，用于检测承载第一业务的第一路径是否发生故障,所述第一业务为可降质的业务；确定单元，用于在检测单元检测到第一路径故障后，确定所述第一业务对应的首节点和末节点之间的第二路径上的可用带宽是否足以恢复所述第一业务；压缩单元，用于在所述第二路径上的可用带宽不足以恢复所述第一业务时，压缩所述第一业务，所述压缩后的第一业务的带宽小于所述第二路径的可用带宽；切换单元，用于将压缩后的所述第一业务切换到所述第二路径。
另一方面，本发明实施例提供了一种控制器，包括存储器和处理器，所述 存储器用于存储指令；所述处理器用于，运行所述存储器存储的指令以进行下列操作：检测到承载第一业务的第一路径发生故障,所述第一业务为可降质的业务；确定所述第一业务对应的首节点和末节点之间的第二路径上的可用带宽是否足以恢复所述第一业务；在所述第二路径上的可用带宽不足以恢复所述第一业务时，压缩所述第一业务，所述压缩后的第一业务的带宽小于所述第二路径的可用带宽；将压缩后的所述第一业务切换到所述第二路径。
本发明实施例的方案在发现故障影响的业务对应的首末节点间有剩余资源但不足以满足恢复中断业务时，压缩可降质的业务，达到节省带宽的同时实现业务的恢复，可以提高资源利用率和优化用户体验。
附图简述
要更全面地了解本发明，请参考下列附图说明以及相关附图和具体实施方案，其中相似的附图标记表示相似的部件。
图1为本发明实施例一业务恢复方法所涉及的网络拓扑示意图；
图2为实施例一网络拓扑中传送网控制器和客户控制器的交互图；
图3为本发明实施例二业务恢复方法所涉及的网络拓扑示意图；
图4为本发明实施例三业务恢复方法所涉及的网络拓扑示意图；
图5为实施例三网络拓扑中传送网控制器和客户控制器的交互图；
图6为实施例四网络拓扑中传送网控制器和客户控制器的交互图；
图7为本发明实施例五的业务恢复方法实施例流程图；
图8是本发明实施例六提供的控制器的结构图；
图9是一种通用计算机系统实施例的原理图。
具体实施方式
尽管下面提供了一个或多个实施例的例证性实施，但是可以使用任何数量的技术，无论是当前已知的技术或现有的技术，来实施公开的系统和/或方法，从一开始时就应该明白这一点。本发明绝不仅限于下面例举的例证性实施、图纸和技术，它还包括本文中例举和说明的典型设计和实施，同时可以在不超出其权利要求范围及等同权利要求的全部范围内对其进行修改。
在传统通信的传送网中，对于数据的属性是不做感知并一视同仁的，这与传送内容的文本格式密切相关。对于传统的传送业务，通常是文本、语音等原始数据，该类数据压缩比不高，一旦损失后对传输效果的影响非常明显，会较大地影响用户的体验，这类业务叫做不可降质业务，不可降质业务是对丢包敏感的业务。而对于如今甚至是未来的传送网业务，管道中占比较高的是类似图片、视频之类的媒体数据，该类数据可以根据需要以预定的比例进行压缩，业务的短时中断并不直接影响用户体验，这类业务叫做可降质业务。由于可降质业务是可以根据需要按预定的比例压缩的业务，可降质业务是对丢包不敏感的业务，用户可以接受可降质业务的短时中断。
本发明实施例在传送网层面针对业务类型进行识别，有些传送业务主要传输媒体数据或其他可降质业务，在带宽资源不足的时候可以进行部分恢复。
图1为本发明实施例一业务恢复方法所涉及的网络拓扑示意图，图2为实施例网络拓扑中传送网控制器和客户控制器的交互图。图1的网络包括节点A，节点B，节点C，图2示出了传送网控制器和客户控制器，节点A和节点B之间的链路上带宽为100G，节点A和节点C之间的带宽为10G，节点B和节点C 之间的带宽为10G，在节点A和节点B之间的链路承载有业务一，业务一的构成数据为媒体数据。当节点A和节点B之间的链路发生故障时，业务一中断。节点A和节点B之间的链路中断先由传送网控制器所感知，传送网控制器对业务一进行重路由。由于以节点A为首节点，以节点B为末节点的恢复路径A-C-B上的剩余资源只有10G，不足以全部恢复需要100G带宽的业务一，在步骤201，传送网控制器将故障情况通知给客户控制器，并将路径A-C-B上的剩余资源不足以恢复业务一的情况以及A-C-B之间的剩余带宽通知给客户控制器。在步骤202，客户控制器收到通知后检查故障业务的业务属性，即检查业务一的业务属性，客户控制器检查后发现业务一的属性为可降质的“媒体数据”，并且业务一可以做10：1比例的压缩处理。在步骤203，客户控制器102确定使用A-C-B的10G带宽资源恢复故障业务，即恢复业务一，并将该恢复方案发送给传送网控制器101。在步骤204，传送网控制器101收到恢复方案后，对业务一按照10：1的比例进行压缩，之后将压缩后的业务一切换到A-C-B路径，业务一由A-C-B的10G带宽链路所承载。
值得注意的是，在步骤S20,4，客户控制器也可以确定10:1的压缩比例会严重影响质量而决定不使用A-C-B的资源，此时可以拒绝恢复方案，从而导致恢复失败。
图3为本发明实施例二业务恢复方法所涉及的网络拓扑示意图，同样参考图1，图1的网络包括节点A，节点B，节点C，在实施例二中A-B链路间共承载四条业务，四条业务的业务属性，承载链路和占用带宽如表1所示，四条业务都是可降质的“媒体数据业务”，其中业务一占用的带宽为10G，业务二占用的带宽为20G，业务三占用的带宽为30G，业务四占用的带宽为40G。
  业务一 业务二 业务三 业务四
业务属性 媒体数据业务 媒体数据业务 媒体数据业务 媒体数据业务
承载链路 A-B A-B A-B A-B
占用带宽 10G 20G 30G 40G
表1：实施例二中A-B链路上承载的业务
当A-B链路发生故障时，以上四条业务均中断。故障先由传送网控制器所感知，并启动对中断的四条业务在客户控制器的网络范围内(本实施例中为图1中的A-B-C三个节点的网络)进行重路由。如果不使用本发明实施例的方案，业务一可以在备用路径A-C-B上得到恢复，而其余三条业务均恢复失败。在本发明实施例中，由于首节点为节点A和末节点为节点B的恢复资源只有A-C-B路径上的10G资源，不足以全部恢复所有的四条中断业务，因此如步骤S301所示，传送网控制器将故障情况，以及不能全部恢复，所有带宽资源总共10G的情况上报给客户控制器。在步骤S302中，客户控制器收到消息后检查四条业务的业务属性。当确定四条业务的属性都为可降质的“媒体数据业务”时(意味着可压缩)，在步骤S303，客户控制器决定使用A-C-B的10G资源恢复以上全部四条业务，各自恢复10％的带宽，恢复方案如表2所示，客户控制器将该恢复方案发送给传送网控制器。
  业务一 业务二 业务三 业务四
承载链路 A-C-B A-C-B A-C-B A-C-B
占用带宽 1G 2G 3G 4G
表2：实施例二中的业务恢复方案
在步骤S304，传送网控制器收到该恢复方案后接受恢复方案，按照方案进行恢复。若恢复成功，四条业务均由A-C-B的10G链路所承载，业务的收发端将根据新的带宽，选择最佳的传输方案，以确保QoS最大化。
前面的实施例遵从如下流程：传送网控制器感知到故障并判断有资源恢复后，将可用于恢复的资源和需要恢复的业务上报给客户控制器，由客户控制器制定恢复方案。在一些网络配置下，本发明实施例也可以由传送网控制器制定恢复方案。
当传送网控制器感知到故障时，也可以自行检查受损业务的属性，确定受损业务为原始数据业务或媒体数据业务，并将可用的恢复带宽分配给不同业务。完成恢复后，将更新过的业务分布上报给客户控制器。
以实施例二中的业务分布为例，传送网控制器感知到故障后，检查业务一二三四的属性均为媒体数据业务，传送网控制器可以使用A-C-B的10G带宽完成对四条业务的恢复，并生成恢复方案如表2所示。恢复完成后将表二上报给客户控制器，用于后续客户控制器对业务和网络的维护。
图4为本发明实施例三业务恢复方法所涉及的网络拓扑示意图，图5为实施例三网络拓扑中传送网控制器和客户控制器的交互图。图4的网络包括节点A，节点B，节点C，图5示出了传送网控制器和客户控制器，图4中节点A和节点B之间的链路上带宽为100G，节点A和节点C之间的带宽为20G，节点B和节点C之间的带宽为20G，在节点A和节点B之间的链路承载有四条业务，其中 业务一的业务属性为不可降质的原始数据业务，业务二，业务三和业务四为可降质的媒体数据业务，业务一占用的带宽为10G，业务二占用的带宽为20G，业务三占用的带宽为30G，业务四占用的带宽为40G。具体细节如表3所示：
  业务一 业务二 业务三 业务四
业务属性 原始数据业务 媒体数据业务 媒体数据业务 媒体数据业务
承载链路 A-B A-B A-B A-B
占用带宽 10G 20G 30G 40G
表3：实施例三中A-B链路上承载的业务
当A-B链路发生故障时，以上四条业务均中断。故障先由传送网控制器所感知，并对中断的所有业务在客户控制器的网络范围内(本实施例中为图3中的A-B-C三个节点的网络)进行重路由。由于以节点A为首节点，以节点B为末节点的恢复路径A-C-B上的剩余资源只有20G，不足以全部恢复所有的四条中断业务，因此如步骤S501所示，传送网控制器将故障情况，以及不能全部恢复，所有带宽资源总共20G的情况上报给客户控制器。在步骤S502中，客户控制器收到消息后检查四条业务的业务属性。客户控制器经检查发现业务一属性为不可降质的“原始数据业务”，意味着不可压缩，必须全部恢复，而剩余的业务属性为可降质的“媒体数据业务”，意味着可压缩，在步骤S503，客户控制器将恢复带宽优先分配给业务一，并决定使用链路A-C-B余下的10G资源恢复业务二、业务三和业务四，恢复方案如表4所示，客户控制器将该恢复方案发送给传送网控制器。
  业务一 业务二 业务三 业务四
承载链路 A-C-B A-C-B A-C-B A-C-B
占用带宽 10G 2G 3G 5G
表4：实施例三中的业务恢复方案
在步骤S504，传送网控制器收到该恢复方案后接受恢复方案，按照方案进行恢复。若恢复成功，四条业务均由A-C-B的20G链路所承载，业务的收发端将根据新的带宽，选择最佳的传输方案，以确保QoS最大化。本发明对业务收发端选择哪些数据进行发送不做限定。
图6为实施例四网络拓扑中传送网控制器和客户控制器的交互图，同样参考图4，图4的网络包括节点A，节点B，节点C，图4中节点A和节点B之间的链路上带宽为100G，节点A和节点C之间的带宽为20G，节点B和节点C之间的带宽为20G，在节点A和节点B之间的链路A-B承载有四条业务，其中业务一，业务二，业务三和业务四皆为可降质的媒体数据业务，业务一占用的带宽为10G，业务二占用的带宽为20G，业务三占用的带宽为30G，业务四占用的带宽为40G。与之前的实施例不同的是，本实施例中链路A-C-B承载有业务五，业务五同样为可降质的媒体数据业务，业务五占用的带宽为20G。当前网络中的承载业务及属性分布如表5所示：
  业务一 业务二 业务三 业务四 业务五
业务属性 媒体数据业务 媒体数据业务 媒体数据业务 媒体数据业务 媒体数据业务
承载链路 A-B A-B A-B A-B A-C-B
占用带宽 10G 20G 30G 40G 20G
表5：实施例三中A-B链路上承载的业务
当A-B链路发生故障时，业务一二三四均中断。故障先由传送网控制器所感知，并对中断的所有业务在客户控制器的网络范围内(本实施例中为图4中的A-B-C三个节点的网络)进行重路由。现有技术下，由于A-B链路间没有空闲资源，业务一二三四均返回恢复失败。在本发明技术中，传送网控制器接到故障后将进行如下判断：由于在首节点为A末节点为B的链路A-C-B可用资源被业务五占满且业务五为可降质的媒体数据业务，意味着业务五可压缩，因此业务一二三四有机会可以恢复。因此传送网在步骤S601将无法全部恢复以及有恢复机会的结论反馈给客户控制器，反馈形式不做限定，例如，传送网控制器可以告知客户控制器可以用20G恢复业务一二三四五。在步骤602，客户控制器收到该消息之后，检查五条业务的业务属性，当确定五条业务的属性都为可降质的“媒体数据业务”时(意味着可压缩)，在步骤S603，客户控制器决定使用A-C-B的20G资源同时承载业务一二三四五，恢复方案如表6所示，客户控制器将该恢复方案发送给传送网控制器。
  业务一 业务二 业务三 业务四 业务五
承载链路 A-C-B A-C-B A-C-B A-C-B A-C-B
占用带宽 1G 2G 3G 4G 10G
表6：实施例四中的业务恢复方案
在步骤604，传送网控制器收到该恢复方案后接受恢复方案，按照方案进行恢复。若恢复成功，五条业务均由A-C-B的20G链路所承载，业务的收发端将根 据新的带宽，选择最佳的传输方案，以确保QoS最大化。本发明对业务收发端选择哪些数据进行发送不做限定。
图7为本发明实施例五的业务恢复方法实施例流程图，该业务恢复方法包括：
S701、传送网控制器检测到承载第一业务的第一路径发生故障,所述第一业务为可降质的业务。
第一路径在故障前可以承载有包括所述第一业务的多条业务，所述多条业务可以都为可降质的业务，所述业务恢复方法还可以包括：压缩所述多条业务中第一业务之外的其他业务；将压缩后的所述其他业务切换到所述第二路径，其中所述压缩后的第一业务和所述压缩后的其他业务所占的带宽总和不大于所述第二路径的可用带宽。在这里，第一业务和所述其他业务的压缩比例根据所述第一业务和所述其他业务的业务类型和优先级确定。
与前面所提到的多条业务都为可降质的业务不同，所述第一路径在故障前承载的包括第一业务的多条业务中，还可以包括不可降质的第二业务，在这种情况下，所述业务恢复方法还可以包括：将第二业务切换到所述第二路径，其中所述压缩后的第一业务的带宽和所述第二业务的带宽总和不大于所述第二路径的可用带宽。在这里，由于第二业务不可降质，第二业务在切换前不会被压缩。
S702、传送网控制器确定所述第一业务对应的首节点和末节点之间的第二路径上的可用带宽是否足以恢复所述第一业务；
S703、传送网控制器在所述第二路径上的可用带宽不足以恢复所述第一业 务时，压缩所述第一业务，所述压缩后的第一业务的带宽小于所述第二路径的可用带宽；
压缩第一业务之前，该业务恢复方法还可以包括：传送网控制器从所述第一业务对应的客户控制器收集恢复方案，所述恢复方案包括所述第一业务的压缩比例；所述压缩第一业务包括：传送网控制器按所述第一业务的压缩比例压缩所述第一业务。
S704、传送网控制器将压缩后的所述第一业务切换到所述第二路径。
在这里，第二路径中可以原先就承载有可降质的第三业务，所述第二路径中在承载第三业务之外，可用带宽不足以按所述恢复方案中的压缩比例恢复所述第一业务，这种情况下，在将压缩后的所述第一业务切换到第二路径之前，该业务恢复方法还可以包括：压缩所述第三业务以增大所述第二路径的可用带宽，直到所述第二路径的可用带宽足以按所述恢复方案中的压缩比例恢复所述第一业务。
本发明实施例的方案在发现故障影响的业务对应的首末节点间有剩余资源但不足以满足恢复中断业务时，压缩可降质的业务，达到节省带宽的同时实现业务的恢复，可以提高资源利用率和优化用户体验。
图8是本发明实施例六提供的控制器的结构图，该控制器可以是对应于前面实施例的业务恢复方法的传送网控制器，该控制器包括：
检测单元801，用于检测承载第一业务的第一路径是否发生故障,所述第一业务为可降质的业务；
确定单元802，用于在检测单元检测到第一路径故障后，确定所述第一业务 对应的首节点和末节点之间的第二路径上的可用带宽是否足以恢复所述第一业务；
压缩单元803，用于在所述第二路径上的可用带宽不足以恢复所述第一业务时，压缩所述第一业务，所述压缩后的第一业务的带宽小于所述第二路径的可用带宽；
切换单元804，用于将压缩后的所述第一业务切换到所述第二路径。
在本发明实施例中，第一路径在故障前可以承载有包括所述第一业务的多条业务，所述多条业务中第一业务之外的其他业务也为可降质的业务，所述压缩单元还用于：压缩所述多条业务中第一业务之外的其他业务；所示切换单元还用于：将压缩后的所述其他业务切换到所述第二路径，其中所述压缩后的第一业务和所述压缩后的其他业务所占的带宽总和不大于所述第二路径的可用带宽。
上述组件可以配合任何通用的网络组件一起使用，例如有足够的处理能力、内存资源和网络吞吐量能力的计算机或网络组件，以共同处理其承担的工作量。
图9显示了一个典型的通用网络组900，其适用于为本文中公开的组件实施一个或多个实施例。网络组件900可以包括处理器902(可被称为中央处理单元或CPU)，其可与任何内存设备保持通信，包括辅助存储器903、只读存储器(ROM)904、随机存储器(RAM)905、输入/输出(I/O)设备901、网络连接设备906或者这些设备的组合。处理器902可以作为一个或多个CPU芯片，也可作为一个或多个专用集成电路(ASIC)的一部分。
辅助存储器903通常包括由一个或多个磁盘驱动器或磁带机组成，用于数 据的非易失性存储，如果RAM 905没有大到足以处理所有工作数据，可以作为溢出数据存储设备。在选择并执行加载到RAM 905上的程序时，可使用辅助存储器903存储这些程序。ROM 904用于在程序执行期间存储读取的指令和可能数据。ROM 904是非易失性存储设备，相对于更大内存容量的辅助存储器903而言，其内存容量较小。RAM 905用于存储易失性数据，也许可存储指令。访问ROM904和RAM 905的速度通常比访问辅助存储器903的速度要快。
至少公开了一个实施例，所属领域的技术人员可以在本发明的范围内对实施例和/或实施例的功能进行变动、组合和/或修改。通过组合、整合和/或删除实施例的功能而得出的替代实施例也将包括在本发明的范围之内。如果明确规定了数值范围或限制，应了解明确的范围或限制，使得包括的类似等级的迭代范围或限制在明确规定的范围或限制之内(例如，从1到10的范围包括2、3、4等；大于0.10的范围包括0.11、0.12、0.13等)。例如，如果公开了数字范围的下限值Rl和上限值Ru，则需要具体公开此范围内的任何数字。尤其是，具体公开范围内的以下数字：R＝Rl+k*(Ru-Rl)，其中k是1％到100％之间以1％以增量的变量，即k是1％、2％、3％、4％、5％、直到50％、51％、52％、直到95％、96％、97％、98％、99％或100％。而且，也需要具体公开上述定义的两个R定义的任何数字范围。针对权利要求中的任何元件使用“选择性地”词语时，意味着需要此元件，或者不需要此元件，这两种替代都在权利要求的范围内。使用“包括”、“包含”、“含有”等广义词应理解提供对“由…组成”、“基本上由…组成”、“大体上由…组成”等狭义词支持。相应地，保护范围不受上述说明的限制，但由下文的权利要求定义，该范围包括权利要求的主题的等同主题。每个权利要求作为进一步发明纳入本说明书中，这些权利要求是本 发明的实施例。不得对本发明中的属于现有技术的参考资料，尤其是出版日期在本申请的优先权日期之后的参考资料，进行讨论。本发明中引用的所有专利、专利申请和出版物的公开在本文中作为参考资料引入，为本发明提供示范性、程序性或其他方面的细节补充。
虽然本发明中提供了多个实施例，但是应这样理解为：公开的系统和方法可以在不脱离本发明的基本精神或范围内以很多其他特定的方式体现。本发明中的范例被视为解释本发明，而不是用于限制本发明，而且本发明不限于本文中提供的详情。例如，在其他系统中，可以组合或整合各个元件或组件，也可以删除或不实施某些特征。
对于各个实施例中以离散形式或者单独地解释说明的技术、系统、子系统和方法，在不脱离本发明的范围内，可以将其与其他系统、模块、技术或方法组合或整合起来。本文中显示或讨论的其他有关相互之间直接或间接相连或者连通的项目可以通过某些接口、设备或中间组件以电气方式、机械方式或其他方式进行间接相连或连通。对其他范例的更改、替换和变动需要由所属领域的技术人员进行确定，而且不得脱离本说明中的基本精神和范围。

Claims (10)

  1. 一种业务恢复方法,其特征在于，所述方法包括:
    检测到承载第一业务的第一路径发生故障,所述第一业务为可降质的业务；
    确定所述第一业务对应的首节点和末节点之间的第二路径上的可用带宽是否足以恢复所述第一业务；
    在所述第二路径上的可用带宽不足以恢复所述第一业务时，压缩所述第一业务，所述压缩后的第一业务的带宽小于所述第二路径的可用带宽；
    将压缩后的所述第一业务切换到所述第二路径。
  2. 如权利要求1所述的业务恢复方法，其特征在于，所述第一路径在故障前承载有包括所述第一业务的多条业务，所述多条业务为可降质的业务，所述方法还包括：
    压缩所述多条业务中第一业务之外的其他业务；
    将压缩后的所述其他业务切换到所述第二路径，其中所述压缩后的第一业务和所述压缩后的其他业务所占的带宽总和不大于所述第二路径的可用带宽。
  3. 如权利要求2所述的方法，其特征在于，所述第一业务和所述其他业务的压缩比例根据所述第一业务和所述其他业务的业务类型和优先级确定。
  4. 如权利要求1所述的业务恢复方法，其特征在于，所述第一路径在故障前承载有包括所述第一业务的多条业务，所述多条业务中包括不可降质的第二业务，所述方法还包括：
    将第二业务切换到所述第二路径，其中所述压缩后的第一业务的带宽和所述第二业务的带宽总和不大于所述第二路径的可用带宽。
  5. 如权利要求1所述的业务恢复方法，其特征在于，所述压缩第一业务之前，所述方法包括：
    从所述第一业务对应的客户控制器收集恢复方案，所述恢复方案包括所述第一业务的压缩比例；
    所述压缩第一业务包括：
    按所述第一业务的压缩比例压缩所述第一业务。
  6. 如权利要求5所述的业务恢复方法，其特征在于，在将压缩后的所述第一业务切换到所述第二路径之前，所述第二路径中承载有可降质的第三业务，所述第二路径中的可用带宽不足以按所述恢复方案中的压缩比例恢复所述第一业务；所述方法包括：
    压缩所述第三业务以增大所述第二路径的可用带宽，直到所述第二路径的可用带宽足以按所述恢复方案中的压缩比例恢复所述第一业务。
  7. 如权利要求1-4中任一权利要求所述的业务恢复方法，其特征在于，所述压缩第一业务之前，所述方法包括：
    确定第一业务的恢复方案，所述恢复方案包括所述第一业务的压缩比例；
    所述压缩第一业务包括：
    按所述第一业务的压缩比例压缩所述第一业务。
  8. 一种控制器，其特征在于，包括：
    检测单元，用于检测承载第一业务的第一路径是否发生故障,所述第一业务为可降质的业务；
    确定单元，用于在检测单元检测到第一路径故障后，确定所述第一业务对应的首节点和末节点之间的第二路径上的可用带宽是否足以恢复所述第一业务；
    压缩单元，用于在所述第二路径上的可用带宽不足以恢复所述第一业务时，压缩所述第一业务，所述压缩后的第一业务的带宽小于所述第二路径的可用带宽；
    切换单元，用于将压缩后的所述第一业务切换到所述第二路径。
  9. 如权利要求8所述的控制器，其特征在于，所述第一路径在故障前承载有包括所述第一业务的多条业务，所述多条业务中第一业务之外的其他业务为可降质的业务，所述压缩单元还用于：
    压缩所述第一业务之外的其他业务；
    所示切换单元还用于：
    将压缩后的所述第一业务之外的其他业务切换到所述第二路径，其中所述压缩后的第一业务和所述压缩后的第一业务之外的其他业务所占的带宽总和不大于所述第二路径的可用带宽。
  10. 一种控制器，其特征在于，包括存储器和处理器，
    所述存储器用于存储指令；
    所述处理器用于，运行所述存储器存储的指令以进行下列操作：
    检测到承载第一业务的第一路径发生故障,所述第一业务为可降质的业务；
    确定所述第一业务对应的首节点和末节点之间的第二路径上的可用带宽是否足以恢复所述第一业务；
    在所述第二路径上的可用带宽不足以恢复所述第一业务时，压缩所述第一业务，所述压缩后的第一业务的带宽小于所述第二路径的可用带宽；
    将压缩后的所述第一业务切换到所述第二路径。
PCT/CN2015/082888 2015-06-30 2015-06-30 一种业务恢复方法和控制器 WO2017000250A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2015/082888 WO2017000250A1 (zh) 2015-06-30 2015-06-30 一种业务恢复方法和控制器
CN201580081339.1A CN107710698B (zh) 2015-06-30 2015-06-30 一种业务恢复方法和控制器

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/082888 WO2017000250A1 (zh) 2015-06-30 2015-06-30 一种业务恢复方法和控制器

Publications (1)

Publication Number Publication Date
WO2017000250A1 true WO2017000250A1 (zh) 2017-01-05

Family

ID=57607478

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/082888 WO2017000250A1 (zh) 2015-06-30 2015-06-30 一种业务恢复方法和控制器

Country Status (2)

Country Link
CN (1) CN107710698B (zh)
WO (1) WO2017000250A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019183911A1 (en) * 2018-03-30 2019-10-03 Zte Corporation Secondary communication node change

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111314145A (zh) * 2020-02-25 2020-06-19 邦彦技术股份有限公司 一种流量控制方法、终端、交换机

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004080434A (ja) * 2002-08-19 2004-03-11 Anritsu Corp ネットワーク中継装置
CN102347862A (zh) * 2011-10-24 2012-02-08 北京邮电大学 基于带宽压缩的全光网业务恢复方法
US20130283118A1 (en) * 2012-04-18 2013-10-24 Nevion Usa, Inc. Launch delay offset data flow protection
CN103636168A (zh) * 2013-09-26 2014-03-12 华为技术有限公司 一种故障恢复的方法、节点和路径计算单元

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5819019A (en) * 1995-12-01 1998-10-06 Silicon Graphics, Inc. System/method for recovering network resources in a distributed environment, via registered callbacks
US7398321B2 (en) * 2002-05-14 2008-07-08 The Research Foundation Of Suny Segment protection scheme for a network
US8705345B2 (en) * 2007-11-26 2014-04-22 Iowa State University Research Foundation, Inc. Network protection using network coding
CN101800941B (zh) * 2009-05-20 2012-12-12 中国科学院声学研究所 一种多级降级呼叫接入控制方法
CN103929360A (zh) * 2014-04-29 2014-07-16 苏州大学 一种弹性光网络保护方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004080434A (ja) * 2002-08-19 2004-03-11 Anritsu Corp ネットワーク中継装置
CN102347862A (zh) * 2011-10-24 2012-02-08 北京邮电大学 基于带宽压缩的全光网业务恢复方法
US20130283118A1 (en) * 2012-04-18 2013-10-24 Nevion Usa, Inc. Launch delay offset data flow protection
CN103636168A (zh) * 2013-09-26 2014-03-12 华为技术有限公司 一种故障恢复的方法、节点和路径计算单元

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SONE ET AL.: "Bandwidth Squeezed Restoration in Spectrum-Sliced Elastic Optical Path Networks (SLICE", JOURNAL OF OPTICAL COMMUNICATIONS AND NETWORKING, vol. 3, no. 3, 30 March 2011 (2011-03-30), pages 223 - 233, XP011350766, ISSN: 1943-0620 *
ZHANG, YIN.: "Research on the Protection and Recovery Technique in the Elastic Optical Network", CHINA MASTER'S THESES FULL-TEXT DATABASE, 15 April 2015 (2015-04-15), ISSN: 1674-0246 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019183911A1 (en) * 2018-03-30 2019-10-03 Zte Corporation Secondary communication node change
US11310704B2 (en) 2018-03-30 2022-04-19 Zte Corporation Secondary communication node change

Also Published As

Publication number Publication date
CN107710698A (zh) 2018-02-16
CN107710698B (zh) 2021-02-09

Similar Documents

Publication Publication Date Title
US8644156B2 (en) Load-balancing traffic with virtual port channels
US9148364B2 (en) System, method and apparatus for efficient management of S-PMSI resource in RSVP P2MP multicast networks
CN102347867B (zh) 一种堆叠分裂检测的处理方法和设备
US20140219289A1 (en) Handling stacking link failures in mdc device
US9467380B2 (en) Data center network flow migration method and system thereof
US9143398B2 (en) System and method for spare capacity allocation for shared backup path protection for dual link failures using successive survivable routing
US8780701B2 (en) Communication apparatus and packet distribution method
US9838245B2 (en) Systems and methods for improved fault tolerance in solicited information handling systems
WO2016165422A1 (zh) 业务动态恢复的方法、装置及软件定义网络sdn控制器
CN106059791A (zh) 一种存储系统中业务的链路切换方法和存储设备
CN113254205B (zh) 负载均衡系统、方法、装置、电子设备及存储介质
JP5846308B2 (ja) 通信装置、通信システム、経路決定方法、及びプログラム
Wang et al. CFR: A cooperative link failure recovery scheme in software‐defined networks
WO2017000250A1 (zh) 一种业务恢复方法和控制器
CN104901882A (zh) 一种设备切换方法、装置和服务器
US20130308459A1 (en) Highly scalable modular system with high reliability and low latency
JP5952779B2 (ja) ネットワーク制御装置、および、ネットワーク制御プログラム
CN105247823A (zh) 调整链路开销的方法和装置
CN109218179A (zh) 负载分担方法及装置、交换机及计算机可读存储介质
WO2020261393A1 (ja) 通信装置及び通信方法
EP2923464B1 (en) Method and apparatus for allocating shared spare bandwidth for a flow on two disjoint routes between end nodes
CN112910781B (zh) 网络故障切换方法、装置、系统和存储介质
JP2013179483A (ja) トラヒック制御装置及びトラヒック制御方法
CN103780431B (zh) 一种te隧道的管理方法和设备
US10257120B2 (en) Converting an aggregated flow to a real flow for core nodes

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

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

Country of ref document: EP

Kind code of ref document: A1