WO2016184268A1 - 基于隧道共享的带宽控制方法及装置 - Google Patents

基于隧道共享的带宽控制方法及装置 Download PDF

Info

Publication number
WO2016184268A1
WO2016184268A1 PCT/CN2016/078694 CN2016078694W WO2016184268A1 WO 2016184268 A1 WO2016184268 A1 WO 2016184268A1 CN 2016078694 W CN2016078694 W CN 2016078694W WO 2016184268 A1 WO2016184268 A1 WO 2016184268A1
Authority
WO
WIPO (PCT)
Prior art keywords
tunnel
sharing
bandwidth
protection
service
Prior art date
Application number
PCT/CN2016/078694
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 WO2016184268A1 publication Critical patent/WO2016184268A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/20—Negotiating bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/825—Involving tunnels, e.g. MPLS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a bandwidth sharing method and apparatus based on tunnel sharing.
  • the bandwidth processing method commonly used on the current network is the management of the entire port level.
  • the bandwidth is amplified by configuring the convergence ratio.
  • accurate bandwidth control cannot be achieved, and for a network with an unbalanced bandwidth configuration, the port-level amplifying bandwidth cannot solve the problem of traffic congestion when the network is faulty. This problem can only be ensured by sharing between tunnels.
  • the services in the communication network are often configured with protection.
  • the same service works and the protection tunnels are routed through the same physical link, such as the LTE double-homed 4 tunnel and the ring-chain chain network.
  • the working and protection tunnels of the same physical link are called the same routing tunnel.
  • traffic will only flow through one of the tunnels regardless of whether switching occurs. In this way, if the working and protection tunnels calculate the bandwidth, the bandwidth resources in the network are redundantly allocated, thereby making it impossible to fully utilize the link bandwidth resources and causing waste of bandwidth resources.
  • the tunnel bandwidth sharing can be automatically configured for the scenario of the same routing service.
  • the services in the existing network there is no shared relationship between the routing work and the protection tunnel.
  • the embodiment of the invention provides a bandwidth control method and device based on tunnel sharing, which aims to solve the bandwidth problem of redundant routing of the same routing work and protection tunnel bandwidth in the inventory service, and release the redundantly allocated link bandwidth to achieve accurate Bandwidth control to avoid wasting bandwidth resources.
  • the shared relationship of the filtered tunnel is sent to the device to release redundant link bandwidth resources.
  • the step of sending the shared relationship of the filtered tunnel to the device to release the redundant link bandwidth resource further includes:
  • the step is: sending the shared relationship of the filtered tunnel to the device to release the redundant link bandwidth resource.
  • the step of filtering the tunnel that meets the bandwidth sharing condition from the resource object selected by the user includes:
  • the resource object comprises: a link set, a network element set or a tunnel set.
  • the sharing relationship of the tunnel includes: sharing within the tunnel protection group, sharing between the tunnel protection groups, and sharing between the tunnel protection group and the protection group.
  • the embodiment of the invention further provides a bandwidth sharing device based on tunnel sharing, including:
  • Obtaining a module configured to obtain a resource object selected by a user
  • a filtering module configured to filter out a tunnel that satisfies a bandwidth sharing condition from a resource object selected by the user
  • the service module is configured to query the client layer service carried on the filtered tunnel, and record the protection type of the tunnel service and the client layer service.
  • the verification sharing rule module is configured to determine the sharing relationship of the filtered tunnel according to the recorded tunnel service and the protection type of the client layer service, and the preset sharing relationship matching rule;
  • the sending module is configured to send the shared relationship of the filtered tunnel to the device to release redundant link bandwidth resources.
  • the device further comprises:
  • the pre-calculation module is configured to pre-calculate the shared relationship of the filtered tunnels, and obtains a pre-computed result for the user to view the bandwidth release situation after the tunnel sharing; if the user confirms the command, the filtering is performed by the sending module The shared relationship of the outgoing tunnel is sent to the device to release redundant link bandwidth resources.
  • the filtering module is further configured to determine whether the resource object selected by the user meets the CAC switch and the tunnel consistency state is consistent, and if so, filters the tunnel that meets the CAC switch ON and the tunnel consistency status; otherwise, discards The tunnel with the CAC switch open and the tunnel consistency status is not met.
  • the resource object comprises: a link set, a network element set or a tunnel set.
  • the sharing relationship of the tunnel includes: sharing within the tunnel protection group, sharing between the tunnel protection groups, and sharing between the tunnel protection group and the protection group.
  • the method and device for controlling bandwidth based on tunnel sharing according to the embodiment of the present invention, by analyzing the inventory service in the existing network, if redundant bandwidth allocation is found, the bandwidth allocation operation and the protection tunnel configuration are performed.
  • Bandwidth sharing can release the redundantly configured bandwidth resources without affecting the quality of the service, and the other services of the network can be used. This solves the problem of bandwidth allocation of the entire network link resources and makes the network bandwidth allocation accurate. Control; in addition, it also solves the problem of traffic congestion when the network fails in the network with unbalanced bandwidth configuration.
  • FIG. 1 is a schematic flowchart of a first embodiment of a bandwidth sharing control method based on tunnel sharing according to the present invention
  • FIG. 2 is a schematic flowchart of a second embodiment of a bandwidth sharing method based on tunnel sharing according to the present invention
  • 3a, 3b, 3c, and 3d are diagrams of some of the same route scenes in the embodiment of the present invention.
  • FIG. 4 is a schematic diagram of functional modules of a first embodiment of a bandwidth sharing device based on tunnel sharing according to the present invention
  • FIG. 5 is a schematic diagram of functional modules of a second embodiment of a tunnel sharing based bandwidth control apparatus according to the present invention.
  • the main solution of the embodiment of the present invention is: by analyzing the existing service in the existing network, the work of the same route and the protection tunnel can be effectively shared, thereby solving the problem of bandwidth allocation of the entire network link resource, which can not affect the service. In the case of quality, the redundant bandwidth resources of the network are effectively released, so that the network bandwidth allocation is precisely controlled.
  • the embodiment of the present invention considers that the services stored in the existing network are not configured to share the same relationship with the routing work and the protection tunnel. Currently, there is no effective means for solving the problem of the same routing work and the redundant allocation of the protection tunnel bandwidth.
  • the embodiment of the present invention provides a solution for solving the bandwidth problem of the redundant operation of the routing work and the protection tunnel bandwidth by using the tunnel-level bandwidth compression, releasing the redundantly allocated link bandwidth, and achieving accurate bandwidth control. To And solve the problem of traffic congestion when the network fails in the network with unbalanced bandwidth configuration.
  • a first embodiment of the present invention provides a bandwidth control method based on tunnel sharing, including:
  • Step S101 acquiring a resource object selected by a user
  • the resource object may be a set of links, some sets of network elements, or a collection of some tunnels. Regardless of the resource object selected by the user, the object that the network management needs to analyze is the tunnel resource on the link.
  • Step S102 Filtering, from the resource object selected by the user, a tunnel that satisfies the bandwidth sharing condition
  • the NMS first filters out the tunnel suitable for bandwidth sharing.
  • the tunnel needs to meet the requirements of the CAC switch and the consistency of the tunnel.
  • the bandwidth sharing is necessary. Therefore, you need to filter out the tunnels with the same CAC switch and consistency. If the two conditions are not met. Any of these will discard this type of tunnel.
  • Step S103 querying the client layer service carried on the filtered tunnel, and recording the protection type of the tunnel service and the client layer service;
  • the network management system searches for the client layer service carried on the tunnel according to the filtered tunnel, and records the protection type of the tunnel service and the client layer service, so as to be based on the recorded tunnel service and the protection type of the client layer service, and according to certain rules. To determine the sharing relationship of the tunnel.
  • the tunnel carries different types of client layer services, and different protection types of the tunnel service and the client layer service configuration, it directly determines whether there is a sharing relationship between the tunnels and what type of sharing relationship exists.
  • Step S104 Determine, according to the recorded tunnel service and the protection type of the client layer service, and the preset sharing relationship matching rule, the sharing relationship of the filtered tunnel.
  • the sharing relationship of tunnels is divided into four types: no sharing relationship between tunnels, sharing relationships among tunnel protection groups, sharing relationships between tunnel protection groups, and sharing relationships between tunnel protection groups and protection groups.
  • tunnel sharing the principle of sharing relationship matching rules, namely tunnel sharing, is:
  • the bandwidth of the protection tunnel shares the bandwidth of the working tunnel.
  • the tunnel bandwidth of the protection pseudowires shares the tunnel bandwidth of the working pseudowires, and the working tunnels and protection tunnel bandwidths that protect the pseudowires can share the working tunnels and the bandwidth of the protection tunnels.
  • a tunnel protection group is shared.
  • a typical type refers to a relationship between a pair of tunnels.
  • the tunnel has a protection relationship.
  • the service carried on the tunnel has no protection relationship.
  • the work and protection tunnels have the same route, and the protection type is 1:1.
  • the protection tunnel bandwidth can share the bandwidth of the working tunnel, which is the protection within the protection group.
  • Shared between tunnel protection groups typically refers to the relationship between two pairs of tunnels.
  • the first two pairs of tunnels have protection relationships.
  • the working and protection tunnels have the same route, and the protection type is 1+.
  • Type 1; the service carried on the service also has a protection relationship, but the protection type of the service is 1:1.
  • the working tunnel of the protection service can share the working tunnel of the work service, but the protection tunnel on the work service cannot be shared.
  • the working tunnel of the work business this is the sharing between the protection groups.
  • the sharing between the tunnel protection group and the protection group is typically the relationship between two pairs of tunnels.
  • the two tunnels have protection relationships.
  • the work and protection tunnels have the same route, and the protection type is 1:1.
  • the type of the service is also protected by the service, but the protection type of the service is also 1:1.
  • the working tunnel of the protection service can share the working tunnel of the work service, and the protection tunnel of the work service can also share the work service.
  • the working tunnel which is the sharing relationship between the protection group and the protection group.
  • Step S105 The shared relationship of the filtered tunnel is sent to the device to release the redundant link bandwidth resource.
  • the process is directly ended. If there is a sharing, the bandwidth resources are released.
  • the network management system sends the filtered relationship of the filtered tunnel to the device to release the redundancy. Link bandwidth resources. Only the tunnel sharing relationship is actually delivered to the device, and the redundant link bandwidth is effectively released.
  • the following steps may be included before the shared relationship of the filtered tunnel is sent to the device to release the redundant link bandwidth resource:
  • Step S106 pre-calculating the shared relationship of the filtered tunnel, and obtaining a pre-computed result for the user to view the bandwidth release situation after the tunnel sharing; if receiving the confirmation instruction of the user, proceeding to step S105: sharing the filtered tunnel
  • the relationship is sent to the device to release redundant link bandwidth resources.
  • the network management system pre-calculates the tunnel sharing relationship according to the tunnel sharing rule, and checks how much effective bandwidth the link can release after the tunnel sharing.
  • the precomputation here is just for the user to check how much bandwidth the link can release after the tunnel sharing relationship is set. Generally, as long as there is a sharing relationship in the tunnel, the link will release the bandwidth after pre-computation. If there is no sharing relationship, the link bandwidth does not change before and after.
  • the sharing relationship of the tunnel is sent to the device.
  • the device can be delivered, so that the tunnel sharing relationship is formally established and the effective bandwidth of the link is actually expanded. Only the tunnel sharing relationship is actually delivered to the device, and the redundant link bandwidth is effectively released.
  • the beneficial effects of the embodiments of the present invention are: through the analysis of the inventory service in the existing network, the work of the same route and the protection tunnel can be effectively shared, thereby solving the problem of bandwidth allocation of the entire network link resource bandwidth. ,allowable Without affecting the quality of the service, the redundant bandwidth resources of the network are effectively released, so that the network bandwidth allocation is precisely controlled.
  • the client layer service is not carried on the tunnel, and there is no sharing relationship between the tunnels.
  • the main reason is that the no-load service tunnel does not occupy the actual bandwidth resources. Only the bandwidth tunnel that carries the service allocates bandwidth resources.
  • Case 3 The tunnel that the service passes through is the same as the route, and the tunnel and the service are configured without protection. At this time, there is no sharing relationship between the tunnels. The main reason is that the services are not protected, so there is no protection tunnel sharing work tunnel.
  • Case 4 The tunnel that the service passes through is the same as the route.
  • the tunnel has a protection relationship.
  • the protection mode is 1+1.
  • the bearer services are configured without protection. In this case, there is no sharing relationship between the tunnels. The main reason is the 1+1 protection mode tunnel.
  • the protection tunnel needs to carry additional services. It needs to allocate bandwidth separately. It does not allow the tunnel bandwidth to share the working tunnel bandwidth.
  • Case 5 The tunnel that the service passes through is the same as the route.
  • the tunnel has no protection relationship.
  • the bearer service has a protection relationship, but the protection mode is 1+1. There is no sharing relationship between the tunnels. The main reason is the service in the 1+1 protection mode.
  • the protection pseudowire also needs to carry additional services. It needs to allocate bandwidth separately. It does not allow the tunnel bandwidth of the protection pseudowire to share the tunnel bandwidth of the working pseudowire.
  • Case 6 The tunnel through which the service passes is configured with the protection relationship between the tunnel and the service, but the protection mode is 1+1. There is no sharing relationship between the tunnels. The main reason is that the tunnels and services of the 1+1 protection mode need to protect the tunnels and the tunnels that protect the pseudowires to carry additional services. Therefore, the bandwidth needs to be occupied separately, and the bandwidth of other tunnels is not allowed to be shared.
  • Case 1 Sharing in the tunnel protection group: The tunnel carries the customer layer service. The tunnel that the service passes through has the same route. The tunnel has a protection relationship. The protection mode is 1:1. The service is not protected. There is a sharing relationship. The main reason is that the protection tunnel of the 1:1 protection mode cannot carry additional services and does not need to occupy bandwidth. Therefore, the protection tunnel can share the bandwidth of the working tunnel.
  • Case 4 Sharing between the tunnel protection group and the protection group:
  • the tunnel carries the customer layer service, the tunnel that the service passes through is the same as the route, and the tunnel and the service are protected.
  • the tunnel protection mode is 1:1, and the service protection mode is 1. :1, at this time there is a sharing relationship between the tunnels.
  • the main reason is that the 1:1 protection mode protection tunnel and the protection pseudowire tunnel cannot carry additional services and do not need to occupy bandwidth. Therefore, the protection tunnel bandwidth in the protection group can share the working tunnel bandwidth and protect the inter-group protection pseudowire tunnel bandwidth. Work pseudowire tunnel bandwidth can be shared.
  • Case 5 Sharing between the tunnel protection group and the protection group:
  • the tunnel carries the customer layer service, and the tunnel that the service passes through is the same as the route.
  • the tunnel and the service are protected.
  • the tunnel protection mode is 1:1 and the service protection mode is 1. +1, then there is a sharing relationship between the tunnels.
  • the main reason is that the protection tunnel of the 1:1 protection mode cannot carry additional services and does not need to occupy bandwidth.
  • the working pseudowire bandwidth of the 1+1 protection mode cannot carry additional services and does not need to occupy bandwidth. Therefore, the protection tunnel bandwidth in the protection group can be
  • the working tunnel bandwidth is shared, and the protection pseudowire tunnel bandwidth between the groups can share the working pseudowire tunnel bandwidth.
  • FIG. 3a, FIG. 3b, FIG. 3c, and FIG. 3d respectively show some common route scenes in the embodiment of the present invention.
  • Scenario 1 As shown in Figure 3a, the AZ endpoints are co-located and the AZ works in the same way as the protection tunnel. The tunnel has a protection relationship and the bearer service has no protection relationship. This scenario is the most basic same routing scenario in engineering use.
  • Scenario 2 As shown in Figure 3b, the AZ endpoints have the same origin and different routes. The working tunnel and the protection tunnel between the two protection groups have the same route. The tunnel and the service have protection relationships. This scenario is very common in engineering use.
  • Scenario 3 As shown in Figure 3c, the AZ endpoints have the same origin and different routes.
  • the working tunnel and the protection tunnel in the same protection group have the same route.
  • the working tunnel and the protection tunnel between the two protection groups also have the same route.
  • the tunnel and the service have the same route. Protect the relationship.
  • This scenario is a typical ring-chain scenario in engineering use and is widely used.
  • Scenario 4 As shown in Figure 3d, the AZ endpoints have the same origin, and the working tunnel and the protection tunnel between the two protection groups have the same route. The tunnel of the DNI pseudowire and the tunnel in the two protection groups also have the same route, tunnel and Business has a protective relationship. This scenario is a new type of protection scenario in engineering use and will be widely used more and more.
  • the solution of the embodiment of the present invention is very close to the engineering application.
  • the analysis of the inventory service in the existing network can effectively share the work of the route and the protection tunnel, thereby solving the redundancy allocation of the link resource bandwidth of the entire network.
  • the problem can effectively release the redundant bandwidth resources of the network without affecting the quality of the service, so that the network bandwidth allocation is accurately controlled.
  • the first embodiment of the present invention provides a tunneling-based bandwidth control apparatus, including: an obtaining module 201, a filtering module 202, a querying service module 203, a verification sharing rule module 204, and a sending module 205. among them:
  • the obtaining module 201 is configured to acquire a resource object selected by the user
  • the filtering module 202 is configured to filter, from the resource object selected by the user, a tunnel that satisfies the bandwidth sharing condition;
  • the query service module 203 is configured to query the client layer service carried on the filtered tunnel, and record the protection type of the tunnel service and the client layer service;
  • the verification sharing rule module 204 is configured to determine, according to the recorded tunnel service and the protection type of the client layer service, and the preset sharing relationship matching rule, the sharing relationship of the filtered tunnel;
  • the sending module 205 is configured to send the shared relationship of the filtered tunnel to the device to release the redundant link bandwidth resource.
  • the resource object may be some link set, some network element set or some set of tunnels. Regardless of the resource object selected by the user, the object that the network management needs to analyze is the tunnel resource on the link.
  • the NMS first filters out the tunnel suitable for bandwidth sharing.
  • the tunnel needs to meet the requirements of the CAC switch and the consistency of the tunnel.
  • the bandwidth sharing is necessary. Therefore, you need to filter out the tunnels with the same CAC switch and consistency. If the two conditions are not met. Any of these will discard this type of tunnel.
  • the network management system searches for the client layer service carried on the tunnel according to the filtered tunnel, and records the protection type of the tunnel service and the client layer service, so as to be based on the recorded tunnel service and the protection type of the client layer service, and according to certain rules. To determine the sharing relationship of the tunnel.
  • the tunnel carries different types of client layer services, and different protection types of the tunnel service and the client layer service configuration, it directly determines whether there is a sharing relationship between the tunnels and what type of sharing relationship exists.
  • the sharing relationship of the tunnel is divided into four types: no sharing relationship between the tunnels, a sharing relationship in the tunnel protection group, a sharing relationship between the tunnel protection groups, and a sharing relationship between the protection groups and the protection groups. .
  • tunnel sharing the principle of sharing relationship matching rules, namely tunnel sharing, is:
  • the bandwidth of the protection tunnel shares the bandwidth of the working tunnel.
  • the tunnel bandwidth of the protection pseudowires shares the tunnel bandwidth of the working pseudowires, and the working tunnels and protection tunnel bandwidths that protect the pseudowires can share the working tunnels and the bandwidth of the protection tunnels.
  • Shared within the tunnel protection group typically refers to the relationship between a pair of tunnels.
  • the tunnel has a protection relationship.
  • the service is unprotected, the working and protection tunnels are the same route, and the protection type is 1:1.
  • the protection tunnel bandwidth can share the bandwidth of the working tunnel. This is the protection group sharing.
  • Shared between tunnel protection groups typically refers to the relationship between two pairs of tunnels.
  • the first two pairs of tunnels have protection relationships.
  • the working and protection tunnels have the same route, and the protection type is 1+.
  • Type 1; the service carried on the service also has a protection relationship, but the protection type of the service is 1:1.
  • the working tunnel of the protection service can share the working tunnel of the work service, but the protection tunnel on the work service cannot be shared.
  • the working tunnel of the work business this is the sharing between the protection groups.
  • the sharing between the tunnel protection group and the protection group is typically the relationship between two pairs of tunnels.
  • the two tunnels have protection relationships.
  • the work and protection tunnels have the same route, and the protection type is 1:1.
  • the type of the service is also protected by the service, but the protection type of the service is also 1:1.
  • the working tunnel of the protection service can share the working tunnel of the work service, and the protection tunnel of the work service can also share the work service.
  • the working tunnel which is the sharing relationship between the protection group and the protection group.
  • the process is directly ended. If there is a sharing, the bandwidth resources are released.
  • the network management system sends the filtered relationship of the filtered tunnel to the device to release the redundancy. Link bandwidth resources. Only the tunnel sharing relationship is actually delivered to the device, and the redundant link bandwidth is effectively released.
  • the second embodiment of the present invention provides a tunnel-based bandwidth control apparatus.
  • the apparatus further includes:
  • the pre-calculation module 206 is configured to pre-calculate the shared relationship of the filtered tunnels, and obtain a pre-computed result for the user to view the bandwidth release situation after the tunnel sharing; if the user confirms the command, the sending module performs the The shared relationship of the filtered tunnel is sent to the device to release redundant link bandwidth resources.
  • the network management system pre-calculates the tunnel sharing relationship according to the tunnel sharing rule, and checks how much effective bandwidth the link can release after the tunnel sharing.
  • the precomputation here is just for the user to check how much bandwidth the link can release after the tunnel sharing relationship is set. Generally, as long as there is a sharing relationship in the tunnel, the link will release the bandwidth after pre-computation. If there is no sharing relationship, the link bandwidth does not change before and after.
  • the sharing relationship of the tunnel is sent to the device.
  • the device can be delivered, so that the tunnel sharing relationship is formally established and the effective bandwidth of the link is actually expanded. Only the tunnel sharing relationship is actually delivered to the device, and the redundant link bandwidth is effectively released.
  • the beneficial effects of the embodiments of the present invention are: through the analysis of the inventory service in the existing network, the same
  • the work of the route and the protection tunnel can be effectively shared, so as to solve the problem of redundant allocation of bandwidth of the entire network link resources, and effectively release the redundant bandwidth resources of the network without affecting the quality of the service, so that the network bandwidth allocation is accurately controlled. .
  • the client layer service is not carried on the tunnel, and there is no sharing relationship between the tunnels.
  • the main reason is that the no-load service tunnel does not occupy the actual bandwidth resources. Only the bandwidth tunnel that carries the service allocates bandwidth resources.
  • Case 3 The tunnel that the service passes through is the same as the route, and the tunnel and the service are configured without protection. At this time, there is no sharing relationship between the tunnels. The main reason is that the services are not protected, so there is no protection tunnel sharing work tunnel.
  • Case 4 The tunnel that the service passes through is the same as the route.
  • the tunnel has a protection relationship.
  • the protection mode is 1+1.
  • the bearer services are configured without protection. In this case, there is no sharing relationship between the tunnels. The main reason is the 1+1 protection mode tunnel.
  • the protection tunnel needs to carry additional services. It needs to allocate bandwidth separately. It does not allow the tunnel bandwidth to share the working tunnel bandwidth.
  • Case 5 The tunnel that the service passes through is the same as the route.
  • the tunnel has no protection relationship.
  • the bearer service has a protection relationship, but the protection mode is 1+1. There is no sharing relationship between the tunnels. The main reason is the service in the 1+1 protection mode.
  • the protection pseudowire also needs to carry additional services. It needs to allocate bandwidth separately. It does not allow the tunnel bandwidth of the protection pseudowire to share the tunnel bandwidth of the working pseudowire.
  • Case 6 The tunnel through which the service passes is configured with the protection relationship between the tunnel and the service, but the protection mode is 1+1. There is no sharing relationship between the tunnels. The main reason is that the tunnels and services of the 1+1 protection mode need to protect the tunnels and the tunnels that protect the pseudowires to carry additional services. Therefore, the bandwidth needs to be occupied separately, and the bandwidth of other tunnels is not allowed to be shared.
  • Case 1 Sharing in the tunnel protection group: The tunnel carries the customer layer service. The tunnel that the service passes through has the same route. The tunnel has a protection relationship. The protection mode is 1:1. The service is not protected. There is a sharing relationship. The main reason is that the protection tunnel of the 1:1 protection mode cannot carry additional services and does not need to occupy bandwidth. Therefore, the protection tunnel can share the bandwidth of the working tunnel.
  • Case 3 Sharing between tunnel protection groups: The tunnel carries the customer layer service. The tunnel that the service passes through is the same as the route. The tunnel and the service are protected. The tunnel protection mode is 1+1 and the service protection mode is 1:1. There is a shared relationship between the tunnels. The main reason is that the 1:1 protection mode protects the pseudowire tunnel. It cannot carry additional services and does not need to occupy bandwidth. Therefore, the protection pseudowire tunnel bandwidth can share the working pseudowire tunnel bandwidth.
  • Case 4 Sharing between the tunnel protection group and the protection group:
  • the tunnel carries the customer layer service, the tunnel that the service passes through is the same as the route, and the tunnel and the service are protected.
  • the tunnel protection mode is 1:1, and the service protection mode is 1. :1, at this time there is a sharing relationship between the tunnels.
  • the main reason is that the 1:1 protection mode protection tunnel and the protection pseudowire tunnel cannot carry additional services and do not need to occupy bandwidth. Therefore, the protection tunnel bandwidth in the protection group can share the working tunnel bandwidth and protect the inter-group protection pseudowire tunnel bandwidth. Work pseudowire tunnel bandwidth can be shared.
  • Case 5 Sharing between the tunnel protection group and the protection group:
  • the tunnel carries the customer layer service, and the tunnel that the service passes through is the same as the route.
  • the tunnel and the service are protected.
  • the tunnel protection mode is 1:1 and the service protection mode is 1. +1, then there is a sharing relationship between the tunnels.
  • the main reason is that the protection tunnel of the 1:1 protection mode cannot carry additional services and does not need to occupy bandwidth.
  • the working pseudowire bandwidth of the 1+1 protection mode cannot carry additional services and does not need to occupy bandwidth. Therefore, the protection tunnel bandwidth in the protection group can be
  • the working tunnel bandwidth is shared, and the protection pseudowire tunnel bandwidth between the groups can share the working pseudowire tunnel bandwidth.
  • FIG. 3a, FIG. 3b, FIG. 3c, and FIG. 3d respectively show some common route scenes in the embodiment of the present invention.
  • Scenario 1 As shown in Figure 3a, the AZ endpoints are co-located and the AZ works in the same way as the protection tunnel. The tunnel has a protection relationship and the bearer service has no protection relationship. This scenario is the most basic same routing scenario in engineering use.
  • Scenario 2 As shown in Figure 3b, the AZ endpoints have the same origin and different routes. The working tunnel and the protection tunnel between the two protection groups have the same route. The tunnel and the service have protection relationships. This scenario is very common in engineering use.
  • Scenario 3 As shown in Figure 3c, the AZ endpoints have the same origin and different routes.
  • the working tunnel and the protection tunnel in the same protection group have the same route.
  • the working tunnel and the protection tunnel between the two protection groups also have the same route.
  • the tunnel and the service have the same route. Protect the relationship.
  • This scenario is a typical ring-chain scenario in engineering use and is widely used.
  • Scenario 4 As shown in Figure 3d, the AZ endpoints have the same origin, and the working tunnel and the protection tunnel between the two protection groups have the same route. The tunnel of the DNI pseudowire and the tunnel in the two protection groups also have the same route, tunnel and Business has a protective relationship. This scenario is a new type of protection scenario in engineering use and will be widely used more and more.
  • the solution of the embodiment of the present invention is very close to the engineering application.
  • the analysis of the inventory service in the existing network can effectively share the work of the route and the protection tunnel, thereby solving the redundancy allocation of the link resource bandwidth of the entire network.
  • the problem can effectively release the redundant bandwidth resources of the network without affecting the quality of the service, so that the network bandwidth allocation is accurately controlled.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the foregoing embodiments of the present invention can be applied to the field of communication technologies, and solve the problem of redundant allocation of bandwidth resources of the entire network link, so that the network bandwidth allocation is accurately controlled; in addition, the network with unbalanced bandwidth configuration is also solved.
  • the problem of traffic congestion in the event of a fault the bandwidth problem of redundant routing of the routing work and the protection tunnel bandwidth, releasing redundantly allocated link bandwidth, achieving accurate bandwidth control, and avoiding waste of bandwidth resources.

Landscapes

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

Abstract

本发明涉及一种基于隧道共享的带宽控制方法及装置，其方法包括：获取用户选择的资源对象；从用户选择的资源对象中过滤出满足带宽共享条件的隧道；查询过滤出的隧道上承载的客户层业务，并记录隧道业务和客户层业务的保护类型；根据记录的隧道业务和客户层业务的保护类型，以及预设的共享关系匹配规则，确定所述过滤出的隧道的共享关系；将过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。本发明解决了全网链路资源带宽冗余分配的问题，使得网络带宽分配受到精确控制；此外，还解决了对于带宽配置不均衡的网络，网络出现故障时的流量挤占问题。

Description

基于隧道共享的带宽控制方法及装置 技术领域
本发明涉及通信技术领域，尤其涉及一种基于隧道共享的带宽控制方法及装置。
背景技术
随着数据通信与多媒体业务需求的发展，第四代移动通信开始兴起，这就对网络资源提出了更高的要求，特别是连接接纳控制(Connection Admission Control，简称为CAC)引入后，网络带宽分配受到精确控制。
目前，现网常用的带宽处理方式是整个端口级别的管理，通过配置收敛比对整个端口进行带宽放大处理。但是，这样不能实现精确的带宽控制，且对于带宽配置不均衡的网络，端口级放大带宽，不能解决网络故障时的流量挤占问题，这个问题只有隧道间的共享才能得到保证。
而且，通信网络中的业务往往配置有保护，在一些工程场景，同一条业务的工作、保护隧道，会途径同一个物理链路，如LTE双归4隧道、环带链组网的链跨段，这些途径同一条物理链路的工作、保护隧道称为同路由隧道，在实际业务工作时，不管是否发生倒换，业务流量只会流经其中的一条隧道。这样，如果工作、保护隧道都计算带宽，就会造成网络中的带宽资源被冗余分配，从而造成不能充分利用链路带宽资源，造成带宽资源的浪费。
在这种背景下，产生了同路由工作、保护隧道带宽共享的需求。
当然，在新配置业务时，对于同路由业务的场景，可以自动配置隧道带宽共享。但对于现网中存量的业务，同路由工作、保护隧道都没有配置共享关系，目前也没有有效的手段解决同路由工作、保护隧道带宽冗余分配的问题。
发明内容
本发明实施例提供一种基于隧道共享的带宽控制方法及装置，旨在解决存量业务中，同路由工作、保护隧道带宽冗余分配的带宽问题，释放出冗余分配的链路带宽，实现精确的带宽控制，避免带宽资源的浪费。
本发明实施例提出的一种基于隧道共享的带宽控制方法，包括：
获取用户选择的资源对象；
从用户选择的资源对象中过滤出满足带宽共享条件的隧道；
查询过滤出的隧道上承载的客户层业务，并记录隧道业务和客户层业务的保护类型；
根据记录的隧道业务和客户层业务的保护类型，以及预设的共享关系匹配规则，确定所述过滤出的隧道的共享关系；
将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
优选地，所述将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源的步骤之前还包括：
预计算过滤出的隧道的共享关系，得到预计算结果，供用户查看隧道共享后带宽释放情况；
若接收到用户的确认指令，则执行步骤：将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
优选地，所述从用户选择的资源对象中过滤出满足带宽共享条件的隧道的步骤包括：
判断用户选择的资源对象是否满足CAC开关开启和隧道一致性状态一致，若是，则过滤出满足CAC开关开启和隧道一致性状态一致的隧道；否则，丢弃不满足CAC开关开启和隧道一致性状态一致的隧道。
优选地，所述资源对象包括：链路集合、网元集合或者隧道集合。
优选地，所述隧道的共享关系包括：隧道保护组内共享、隧道保护组间共享，以及隧道保护组内和保护组间共享。
本发明实施例还提出一种基于隧道共享的带宽控制装置，包括：
获取模块，设置为获取用户选择的资源对象；
过滤模块，设置为从用户选择的资源对象中过滤出满足带宽共享条件的隧道；
查询业务模块，设置为查询过滤出的隧道上承载的客户层业务，并记录隧道业务和客户层业务的保护类型；
校验共享规则模块，设置为根据记录的隧道业务和客户层业务的保护类型，以及预设的共享关系匹配规则，确定所述过滤出的隧道的共享关系；
下发模块，设置为将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
优选地，所述装置还包括：
预计算模块，设置为预计算过滤出的隧道的共享关系，得到预计算结果，供用户查看隧道共享后带宽释放情况；若接收到用户的确认指令，则由所述下发模块将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
优选地，所述过滤模块，还设置为判断用户选择的资源对象是否满足CAC开关开启和隧道一致性状态一致，若是，则过滤出满足CAC开关开启和隧道一致性状态一致的隧道；否则，丢弃不满足CAC开关开启和隧道一致性状态一致的隧道。
优选地，所述资源对象包括：链路集合、网元集合或者隧道集合。
优选地，所述隧道的共享关系包括：隧道保护组内共享、隧道保护组间共享，以及隧道保护组内和保护组间共享。
本发明实施例提出的一种基于隧道共享的带宽控制方法及装置，通过对现网中存量业务的分析，如果发现有冗余分配带宽的情况，就对冗余分配带宽的工作、保护隧道配置带宽共享，可以在不影响业务质量的情况下，释放出冗余配置的带宽资源，供网络其他业务开通使用，从而解决了全网链路资源带宽冗余分配的问题，使得网络带宽分配受到精确控制；此外，还解决了对于带宽配置不均衡的网络，网络出现故障时的流量挤占问题。
附图说明
图1是本发明基于隧道共享的带宽控制方法第一实施例的流程示意图；
图2是本发明基于隧道共享的带宽控制方法第二实施例的流程示意图；
图3a、图3b、图3c、图3d分别是本发明实施例中一些同路由场景图；
图4是本发明基于隧道共享的带宽控制装置第一实施例的功能模块示意图；
图5是本发明基于隧道共享的带宽控制装置第二实施例的功能模块示意图。
为了使本发明的技术方案更加清楚、明了，下面将结合附图作进一步详述。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
本发明实施例的主要解决方案是：通过对现网中存量业务的分析，同路由的工作、保护隧道能够有效共享，从而解决全网链路资源带宽冗余分配的问题，可以在不影响业务质量的情况下，有效释放网络的冗余带宽资源，使得网络带宽分配受到精确控制。
本发明实施例考虑到，现网中存量的业务，同路由工作、保护隧道都没有配置共享关系，目前也没有有效的手段解决同路由工作、保护隧道带宽冗余分配的问题。
本发明实施例提出一种解决方案，通过隧道级带宽压缩，解决存量业务中，同路由工作、保护隧道带宽冗余分配的带宽问题，释放出冗余分配的链路带宽，实现精确的带宽控制，以 及解决对于带宽配置不均衡的网络，网络出现故障时的流量挤占问题。
具体地，如图1所示，本发明第一实施例提出一种基于隧道共享的带宽控制方法，包括：
步骤S101，获取用户选择的资源对象；
其中，资源对象可以是一些链路集合、一些网元集合或者一些隧道的集合。无论用户选择什么资源对象，最后网管需要分析的对象都是链路上的隧道资源。
步骤S102，从用户选择的资源对象中过滤出满足带宽共享条件的隧道；
网管根据选择的对象，首先过滤出适合带宽共享的隧道。
隧道需要满足CAC开关开启，以及隧道一致性状态一致这两个条件后，才享有带宽共享的必要性，因此需要全量过滤出CAC开关开启和一致性状态一致的隧道，如果不满足两个必要条件中的任何一个，则丢弃该类型的隧道。
步骤S103，查询过滤出的隧道上承载的客户层业务，并记录隧道业务和客户层业务的保护类型；
之后，网管根据过滤出的隧道，查询其上承载的客户层业务，并记录隧道业务和客户层业务的保护类型，以便根据记录的隧道业务和客户层业务的保护类型，并根据一定的规则，来确定隧道的共享关系。
因为隧道承载不同类型的客户层业务，以及隧道业务和客户层业务配置的不同保护类型，直接决定隧道间是否存在共享关系以及存在何种类型的共享关系。
步骤S104，根据记录的隧道业务和客户层业务的保护类型，以及预设的共享关系匹配规则，确定所述过滤出的隧道的共享关系；
隧道的共享关系一共分为四种：隧道间无共享关系、隧道保护组内有共享关系、隧道保护组间有共享关系、隧道保护组内和保护组间都有共享关系。
其中，共享关系匹配规则即隧道共享的原则是：
隧道保护组内，保护隧道的带宽共享工作隧道的带宽。
隧道保护子网间，保护伪线的隧道带宽共享工作伪线的隧道带宽，包括保护伪线的工作隧道和保护隧道带宽都可以共享工作伪线的工作隧道和保护隧道的带宽。
不能设置循环共享,不能A共享B，B共享C，应该直接设置A共享C，B共享C。
隧道保护组内共享，典型的指的是1对隧道间的关系，首先隧道有保护关系，隧道上承载的业务无保护关系，工作和保护隧道同路由，且保护类型又是1：1的类型，此时，保护隧道带宽可以共享工作隧道的带宽，这就是保护组内共享。
隧道保护组间共享，典型的指的是2对及其以上隧道间的关系，首先2对及其以上隧道都有保护关系，其工作和保护隧道都有同路由，且其保护类型是1+1的类型；其上承载的业务也有保护关系，但业务的保护类型是1：1的类型，此时，保护业务的工作隧道可以共享工作业务的工作隧道，但是工作业务上的保护隧道不能共享工作业务的工作隧道，这就是保护组间的共享。
隧道保护组内和保护组间的共享，典型的指的也是2对隧道间的关系，首先2对隧道都有保护关系，其工作和保护隧道都有同路由，且其保护类型是1：1的类型；其上承载的业务也有保护关系，但业务的保护类型也是1：1的类型，此时，保护业务的工作隧道可以共享工作业务的工作隧道，工作业务的保护隧道也能共享工作业务的工作隧道，这就是保护组间和保护组间都存在共享关系。
后续将结合共享关系匹配规则，对于各种类型的业务是否存在共享，以及存在何种类型的共享进行详细阐述。
步骤S105，将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
通过判断隧道之间是否有共享，如果无共享关系，则直接结束该流程；如果存在共享，则必然会有带宽资源释放，网管将过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。只有隧道共享关系实际下发到设备上，冗余的链路带宽才真正有效释放。
可选地，如图2所示，在另一实施例中，在将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源之前还可以包括以下步骤：
步骤S106，预计算过滤出的隧道的共享关系，得到预计算结果，供用户查看隧道共享后带宽释放情况；若接收到用户的确认指令，则进入步骤S105：将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
具体地，网管根据隧道共享规则预计算隧道共享关系，查看隧道共享后，链路可以释放多少有效带宽。
这里的预计算只是让用户查看一下，隧道共享关系设置后，链路可以释放多少带宽。一般来说，隧道只要存在共享关系，预计算后，链路一定会释放带宽，如果不存在共享关系，则链路带宽前后无变化。
在用户确认后，向设备下发隧道的共享关系。
对于预计算的结果，用户查看确认后，可以下发设备，这样隧道共享关系就正式确立，链路的有效带宽也实际扩展。只有隧道共享关系实际下发到设备上，冗余的链路带宽才真正有效释放。
与现有技术相比较，本发明实施例的有益效果在于：通过对现网中存量业务的分析，同路由的工作、保护隧道能够有效共享，从而解决全网链路资源带宽冗余分配的问题，可以在 不影响业务质量的情况下，有效释放网络的冗余带宽资源，使得网络带宽分配受到精确控制。
以下详细阐述本发明实施例中业务类型和隧道共享关系的匹配规则。
首先介绍无共享关系的业务类型，即各种隧道无共享关系的情况：
情况一，隧道上未承载客户层业务，这时隧道之间无共享关系。主要原因是，空载的业务隧道不占用实际带宽资源，只有承载了业务的带宽隧道，才为其分配带宽资源。
情况二：隧道上承载有客户层业务，但业务经过的隧道无同路由，这时隧道之间无共享关系。主要原因在于：只有同路由的隧道才有带宽共享的必要性，非同路由的隧道没有必要分析带宽共享。
情况三：业务经过的隧道同路由，隧道和业务都无保护关系配置，这时隧道之间无共享关系。主要原因是业务都无保护，所以不存在保护隧道共享工作隧道的情况。
情况四：业务经过的隧道同路由，隧道有保护关系配置，但保护模式是1+1，承载的业务都无保护关系配置，这时隧道之间无共享关系。主要原因是1+1保护模式的隧道，保护隧道需要承载额外业务，需要为其单独分配带宽，不允许保护隧道带宽共享工作隧道带宽。
情况五：业务经过的隧道同路由，隧道间无保护关系配置，承载的业务有保护关系配置，但保护模式是1+1，这时隧道之间无共享关系。主要原因是1+1保护模式的业务，保护伪线也需要承载额外业务，需要为其单独分配带宽，不允许保护伪线的隧道带宽共享工作伪线的隧道带宽。
情况六：业务经过的隧道同路由，隧道和业务都有保护关系配置，但保护模式都是1+1，这时隧道之间无共享关系。主要原因是1+1保护模式的隧道和业务，都需要保护隧道和保护伪线的隧道承载额外业务，因此需要单独占有带宽，不允许共享其他隧道的带宽。
其次，介绍存在共享关系的业务类型，即各种隧道存在共享关系的情况：
情况一：隧道保护组内共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道间有保护关系配置，且保护模式是1：1，业务无保护关系配置，这时隧道之间有共享关系。主要原因是1：1保护模式的保护隧道，不能承载额外业务，无需占有带宽，因此保护隧道可以共享工作隧道的带宽。
情况二：隧道保护组间共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道无保护关系配置，业务有保护关系配置，且保护模式是1：1，这时隧道之间有共享关系。主要原因是1：1保护模式的保护伪线的隧道，不能承载额外业务，无需占有带宽，因此保护伪线隧道带宽可以共享工作伪线隧道带宽。
情况三：隧道保护组间共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道 和业务都有保护关系配置，隧道保护模式是1+1，业务保护模式是1：1，这时隧道之间有共享关系。主要原因是1：1保护模式的保护伪线的隧道，不能承载额外业务，无需占有带宽，因此保护伪线隧道带宽可以共享工作伪线隧道带宽。
情况四：隧道保护组内和保护组间共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道和业务都有保护关系配置，隧道保护模式是1：1，业务保护模式是1：1，这时隧道之间有共享关系。主要原因是1：1保护模式的保护隧道和保护伪线的隧道，都不能承载额外业务，无需占有带宽，因此，保护组内保护隧道带宽可以共享工作隧道带宽，保护组间保护伪线隧道带宽可以共享工作伪线隧道带宽。
情况五：隧道保护组内和保护组间共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道和业务都有保护关系配置，隧道保护模式是1：1，业务保护模式是1+1，这时隧道之间有共享关系。主要原因是1：1保护模式的保护隧道，不能承载额外业务，无需占有带宽；1+1保护模式的工作伪线带宽，不能承载额外业务，无需占有带宽，因此，保护组内保护隧道带宽可以共享工作隧道带宽，保护组间保护伪线隧道带宽可以共享工作伪线隧道带宽。
如图3a、图3b、图3c、图3d所示，图3a、图3b、图3c、图3d分别示出了本发明实施例中常见的一些同路由场景图。
场景一：如图3a所示，AZ端点同源同宿，AZ工作和保护隧道同路由，隧道有保护关系，承载的业务无保护关系。该场景是工程使用中最基本的同路由场景。
场景二：如图3b所示，AZ端点同源不同宿，两个保护组间的工作隧道和保护隧道有同路由，隧道和业务都有保护关系。该场景在工程使用中非常常见。
场景三：如图3c所示，AZ端点同源不同宿，同一个保护组内工作隧道和保护隧道有同路由，两个保护组间的工作隧道和保护隧道也有同路由，隧道和业务都有保护关系。该场景在工程使用中是典型的环带链场景，应用广泛。
场景四：如图3d所示，AZ端点同源不同宿，两个保护组间的工作隧道和保护隧道有同路由，DNI伪线的隧道和两个保护组中的隧道也有同路由，隧道和业务都有保护关系。该场景在工程使用中是一种新型的保护场景，将会越来越多的被广泛应用。
当然，还有其他一些同路由的场景图，大多是这些场景的拆分或者组合，在此不再一一说明。
通过上述各个场景可知，本发明实施例方案非常贴近于工程应用，通过对现网中存量业务的分析，同路由的工作、保护隧道能够有效共享，从而解决全网链路资源带宽冗余分配的问题，可以在不影响业务质量的情况下，有效释放网络的冗余带宽资源，使得网络带宽分配受到精确控制。
对应地，提出本发明基于隧道共享的带宽控制装置实施例。
如图4所示，本发明第一实施例提出一种基于隧道共享的带宽控制装置，包括：获取模块201、过滤模块202、查询业务模块203、校验共享规则模块204以及下发模块205，其中：
获取模块201，设置为获取用户选择的资源对象；
过滤模块202，设置为从用户选择的资源对象中过滤出满足带宽共享条件的隧道；
查询业务模块203，设置为查询过滤出的隧道上承载的客户层业务，并记录隧道业务和客户层业务的保护类型；
校验共享规则模块204，设置为根据记录的隧道业务和客户层业务的保护类型，以及预设的共享关系匹配规则，确定所述过滤出的隧道的共享关系；
下发模块205，设置为将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
具体地，其中，资源对象可以是一些链路集合、一些网元集合或者一些隧道的集合。无论用户选择什么资源对象，最后网管需要分析的对象都是链路上的隧道资源。
网管根据选择的对象，首先过滤出适合带宽共享的隧道。
隧道需要满足CAC开关开启，以及隧道一致性状态一致这两个条件后，才享有带宽共享的必要性，因此需要全量过滤出CAC开关开启和一致性状态一致的隧道，如果不满足两个必要条件中的任何一个，则丢弃该类型的隧道。
之后，网管根据过滤出的隧道，查询其上承载的客户层业务，并记录隧道业务和客户层业务的保护类型，以便根据记录的隧道业务和客户层业务的保护类型，并根据一定的规则，来确定隧道的共享关系。
因为隧道承载不同类型的客户层业务，以及隧道业务和客户层业务配置的不同保护类型，直接决定隧道间是否存在共享关系以及存在何种类型的共享关系。
在本实施例中，隧道的共享关系一共分为四种：隧道间无共享关系、隧道保护组内有共享关系、隧道保护组间有共享关系、隧道保护组内和保护组间都有共享关系。
其中，共享关系匹配规则即隧道共享的原则是：
隧道保护组内，保护隧道的带宽共享工作隧道的带宽。
隧道保护子网间，保护伪线的隧道带宽共享工作伪线的隧道带宽，包括保护伪线的工作隧道和保护隧道带宽都可以共享工作伪线的工作隧道和保护隧道的带宽。
不能设置循环共享,不能A共享B，B共享C，应该直接设置A共享C，B共享C。
隧道保护组内共享，典型的指的是1对隧道间的关系，首先隧道有保护关系，隧道上承 载的业务无保护关系，工作和保护隧道同路由，且保护类型又是1：1的类型，此时，保护隧道带宽可以共享工作隧道的带宽，这就是保护组内共享。
隧道保护组间共享，典型的指的是2对及其以上隧道间的关系，首先2对及其以上隧道都有保护关系，其工作和保护隧道都有同路由，且其保护类型是1+1的类型；其上承载的业务也有保护关系，但业务的保护类型是1：1的类型，此时，保护业务的工作隧道可以共享工作业务的工作隧道，但是工作业务上的保护隧道不能共享工作业务的工作隧道，这就是保护组间的共享。
隧道保护组内和保护组间的共享，典型的指的也是2对隧道间的关系，首先2对隧道都有保护关系，其工作和保护隧道都有同路由，且其保护类型是1：1的类型；其上承载的业务也有保护关系，但业务的保护类型也是1：1的类型，此时，保护业务的工作隧道可以共享工作业务的工作隧道，工作业务的保护隧道也能共享工作业务的工作隧道，这就是保护组间和保护组间都存在共享关系。
后续将结合共享关系匹配规则，对于各种类型的业务是否存在共享，以及存在何种类型的共享进行详细阐述。
通过判断隧道之间是否有共享，如果无共享关系，则直接结束该流程；如果存在共享，则必然会有带宽资源释放，网管将过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。只有隧道共享关系实际下发到设备上，冗余的链路带宽才真正有效释放。
如图5所示，本发明第二实施例提出一种基于隧道共享的带宽控制装置，基于上述图4所述的实施例，该装置还包括：
预计算模块206，设置为预计算过滤出的隧道的共享关系，得到预计算结果，供用户查看隧道共享后带宽释放情况；若接收到用户的确认指令，则由所述下发模块将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
具体地，网管根据隧道共享规则预计算隧道共享关系，查看隧道共享后，链路可以释放多少有效带宽。
这里的预计算只是让用户查看一下，隧道共享关系设置后，链路可以释放多少带宽。一般来说，隧道只要存在共享关系，预计算后，链路一定会释放带宽，如果不存在共享关系，则链路带宽前后无变化。
在用户确认后，向设备下发隧道的共享关系。
对于预计算的结果，用户查看确认后，可以下发设备，这样隧道共享关系就正式确立，链路的有效带宽也实际扩展。只有隧道共享关系实际下发到设备上，冗余的链路带宽才真正有效释放。
与现有技术相比较，本发明实施例的有益效果在于：通过对现网中存量业务的分析，同 路由的工作、保护隧道能够有效共享，从而解决全网链路资源带宽冗余分配的问题，可以在不影响业务质量的情况下，有效释放网络的冗余带宽资源，使得网络带宽分配受到精确控制。
以下详细阐述本发明实施例中业务类型和隧道共享关系的匹配规则。
首先介绍无共享关系的业务类型，即各种隧道无共享关系的情况：
情况一，隧道上未承载客户层业务，这时隧道之间无共享关系。主要原因是，空载的业务隧道不占用实际带宽资源，只有承载了业务的带宽隧道，才为其分配带宽资源。
情况二：隧道上承载有客户层业务，但业务经过的隧道无同路由，这时隧道之间无共享关系。主要原因在于：只有同路由的隧道才有带宽共享的必要性，非同路由的隧道没有必要分析带宽共享。
情况三：业务经过的隧道同路由，隧道和业务都无保护关系配置，这时隧道之间无共享关系。主要原因是业务都无保护，所以不存在保护隧道共享工作隧道的情况。
情况四：业务经过的隧道同路由，隧道有保护关系配置，但保护模式是1+1，承载的业务都无保护关系配置，这时隧道之间无共享关系。主要原因是1+1保护模式的隧道，保护隧道需要承载额外业务，需要为其单独分配带宽，不允许保护隧道带宽共享工作隧道带宽。
情况五：业务经过的隧道同路由，隧道间无保护关系配置，承载的业务有保护关系配置，但保护模式是1+1，这时隧道之间无共享关系。主要原因是1+1保护模式的业务，保护伪线也需要承载额外业务，需要为其单独分配带宽，不允许保护伪线的隧道带宽共享工作伪线的隧道带宽。
情况六：业务经过的隧道同路由，隧道和业务都有保护关系配置，但保护模式都是1+1，这时隧道之间无共享关系。主要原因是1+1保护模式的隧道和业务，都需要保护隧道和保护伪线的隧道承载额外业务，因此需要单独占有带宽，不允许共享其他隧道的带宽。
其次，介绍存在共享关系的业务类型，即各种隧道存在共享关系的情况：
情况一：隧道保护组内共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道间有保护关系配置，且保护模式是1：1，业务无保护关系配置，这时隧道之间有共享关系。主要原因是1：1保护模式的保护隧道，不能承载额外业务，无需占有带宽，因此保护隧道可以共享工作隧道的带宽。
情况二：隧道保护组间共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道无保护关系配置，业务有保护关系配置，且保护模式是1：1，这时隧道之间有共享关系。主要原因是1：1保护模式的保护伪线的隧道，不能承载额外业务，无需占有带宽，因此保护伪线隧道带宽可以共享工作伪线隧道带宽。
情况三：隧道保护组间共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道和业务都有保护关系配置，隧道保护模式是1+1，业务保护模式是1：1，这时隧道之间有共享关系。主要原因是1：1保护模式的保护伪线的隧道，不能承载额外业务，无需占有带宽，因此保护伪线隧道带宽可以共享工作伪线隧道带宽。
情况四：隧道保护组内和保护组间共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道和业务都有保护关系配置，隧道保护模式是1：1，业务保护模式是1：1，这时隧道之间有共享关系。主要原因是1：1保护模式的保护隧道和保护伪线的隧道，都不能承载额外业务，无需占有带宽，因此，保护组内保护隧道带宽可以共享工作隧道带宽，保护组间保护伪线隧道带宽可以共享工作伪线隧道带宽。
情况五：隧道保护组内和保护组间共享：隧道上承载有客户层业务，业务经过的隧道同路由，隧道和业务都有保护关系配置，隧道保护模式是1：1，业务保护模式是1+1，这时隧道之间有共享关系。主要原因是1：1保护模式的保护隧道，不能承载额外业务，无需占有带宽；1+1保护模式的工作伪线带宽，不能承载额外业务，无需占有带宽，因此，保护组内保护隧道带宽可以共享工作隧道带宽，保护组间保护伪线隧道带宽可以共享工作伪线隧道带宽。
如图3a、图3b、图3c、图3d所示，图3a、图3b、图3c、图3d分别示出了本发明实施例中常见的一些同路由场景图。
场景一：如图3a所示，AZ端点同源同宿，AZ工作和保护隧道同路由，隧道有保护关系，承载的业务无保护关系。该场景是工程使用中最基本的同路由场景。
场景二：如图3b所示，AZ端点同源不同宿，两个保护组间的工作隧道和保护隧道有同路由，隧道和业务都有保护关系。该场景在工程使用中非常常见。
场景三：如图3c所示，AZ端点同源不同宿，同一个保护组内工作隧道和保护隧道有同路由，两个保护组间的工作隧道和保护隧道也有同路由，隧道和业务都有保护关系。该场景在工程使用中是典型的环带链场景，应用广泛。
场景四：如图3d所示，AZ端点同源不同宿，两个保护组间的工作隧道和保护隧道有同路由，DNI伪线的隧道和两个保护组中的隧道也有同路由，隧道和业务都有保护关系。该场景在工程使用中是一种新型的保护场景，将会越来越多的被广泛应用。
当然，还有其他一些同路由的场景图，大多是这些场景的拆分或者组合，在此不再一一说明。
通过上述各个场景可知，本发明实施例方案非常贴近于工程应用，通过对现网中存量业务的分析，同路由的工作、保护隧道能够有效共享，从而解决全网链路资源带宽冗余分配的问题，可以在不影响业务质量的情况下，有效释放网络的冗余带宽资源，使得网络带宽分配受到精确控制。
还需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
上述的本发明实施例，可以应用于通信技术领域，解决了全网链路资源带宽冗余分配的问题，使得网络带宽分配受到精确控制；此外，还解决了对于带宽配置不均衡的网络，网络出现故障时的流量挤占问题，同路由工作、保护隧道带宽冗余分配的带宽问题，释放出冗余分配的链路带宽，实现精确的带宽控制，避免带宽资源的浪费。

Claims (10)

  1. 一种基于隧道共享的带宽控制方法，包括：
    获取用户选择的资源对象；
    从用户选择的资源对象中过滤出满足带宽共享条件的隧道；
    查询过滤出的隧道上承载的客户层业务，并记录隧道业务和客户层业务的保护类型；
    根据记录的隧道业务和客户层业务的保护类型，以及预设的共享关系匹配规则，确定所述过滤出的隧道的共享关系；
    将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
  2. 根据权利要求1所述的方法，其中，所述将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源的步骤之前还包括：
    预计算过滤出的隧道的共享关系，得到预计算结果，供用户查看隧道共享后带宽释放情况；
    若接收到用户的确认指令，则执行步骤：将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
  3. 根据权利要求1所述的方法，其中，所述从用户选择的资源对象中过滤出满足带宽共享条件的隧道的步骤包括：
    判断用户选择的资源对象是否满足CAC开关开启和隧道一致性状态一致，若是，则过滤出满足CAC开关开启和隧道一致性状态一致的隧道；否则，丢弃不满足CAC开关开启和隧道一致性状态一致的隧道。
  4. 根据权利要求1所述的方法，其中，所述资源对象包括：链路集合、网元集合或者隧道集合。
  5. 根据权利要求1-4中任一项所述的方法，其中，所述隧道的共享关系包括：隧道保护组内共享、隧道保护组间共享，以及隧道保护组内和保护组间共享。
  6. 一种基于隧道共享的带宽控制装置，包括：
    获取模块，设置为获取用户选择的资源对象；
    过滤模块，设置为从用户选择的资源对象中过滤出满足带宽共享条件的隧道；
    查询业务模块，设置为查询过滤出的隧道上承载的客户层业务，并记录隧道业务和客户层业务的保护类型；
    校验共享规则模块，设置为根据记录的隧道业务和客户层业务的保护类型，以及预设的共享关系匹配规则，确定所述过滤出的隧道的共享关系；
    下发模块，设置为将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
  7. 根据权利要求6所述的装置，其中，所述装置还包括：
    预计算模块，设置为预计算过滤出的隧道的共享关系，得到预计算结果，供用户查看隧道共享后带宽释放情况；若接收到用户的确认指令，则由所述下发模块将所述过滤出的隧道的共享关系下发到设备，以释放冗余链路带宽资源。
  8. 根据权利要求6所述的装置，其中，
    所述过滤模块，还设置为判断用户选择的资源对象是否满足CAC开关开启和隧道一致性状态一致，若是，则过滤出满足CAC开关开启和隧道一致性状态一致的隧道；否则，丢弃不满足CAC开关开启和隧道一致性状态一致的隧道。
  9. 根据权利要求6所述的装置，其中，所述资源对象包括：链路集合、网元集合或者隧道集合。
  10. 根据权利要求6-9中任一项所述的装置，其中，所述隧道的共享关系包括：隧道保护组内共享、隧道保护组间共享，以及隧道保护组内和保护组间共享。
PCT/CN2016/078694 2015-05-18 2016-04-07 基于隧道共享的带宽控制方法及装置 WO2016184268A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510252663.7A CN106304202B (zh) 2015-05-18 2015-05-18 基于隧道共享的带宽控制方法及装置
CN201510252663.7 2015-05-18

Publications (1)

Publication Number Publication Date
WO2016184268A1 true WO2016184268A1 (zh) 2016-11-24

Family

ID=57319434

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/078694 WO2016184268A1 (zh) 2015-05-18 2016-04-07 基于隧道共享的带宽控制方法及装置

Country Status (2)

Country Link
CN (1) CN106304202B (zh)
WO (1) WO2016184268A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111325403A (zh) * 2020-02-26 2020-06-23 长安大学 一种公路隧道机电设备剩余寿命预测方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022052009A1 (en) * 2020-09-10 2022-03-17 Huawei Technologies Co., Ltd. Device and method for load balancing

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101072161A (zh) * 2007-07-12 2007-11-14 华为技术有限公司 一种保证虚拟专用网带宽和服务质量的方法和设备
US20100246603A1 (en) * 2004-04-20 2010-09-30 Nortel Networks Limited Method and system for quality of service support for ethernet multiservice interworking over multiprotocol label switching
CN102136991A (zh) * 2010-07-02 2011-07-27 华为技术有限公司 在标签交换路径上配置隧道的方法和节点
CN102223299A (zh) * 2011-06-08 2011-10-19 中兴通讯股份有限公司 隧道间带宽资源的管理方法和系统
US20130259067A1 (en) * 2012-03-27 2013-10-03 Eci Telecom Ltd. Method for Providing an MPLS Tunnel with Shared Bandwidth

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080089285A (ko) * 2007-03-30 2008-10-06 한국전자통신연구원 이더넷 링 네트워크에서의 보호 절체 방법
CN101471693B (zh) * 2007-12-27 2013-04-17 华为技术有限公司 一种实现共享网格保护的方法和装置
CN101197633B (zh) * 2008-01-04 2011-04-20 中兴通讯股份有限公司 一种共享保护和提高带宽利用率的方法及装置
CN101969382B (zh) * 2010-09-25 2014-07-02 中兴通讯股份有限公司 网状网中实现业务保护共享的方法及装置
CN102891787B (zh) * 2011-07-20 2017-10-10 中兴通讯股份有限公司 基于共享路径的环网隧道配置方法、业务切换方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100246603A1 (en) * 2004-04-20 2010-09-30 Nortel Networks Limited Method and system for quality of service support for ethernet multiservice interworking over multiprotocol label switching
CN101072161A (zh) * 2007-07-12 2007-11-14 华为技术有限公司 一种保证虚拟专用网带宽和服务质量的方法和设备
CN102136991A (zh) * 2010-07-02 2011-07-27 华为技术有限公司 在标签交换路径上配置隧道的方法和节点
CN102223299A (zh) * 2011-06-08 2011-10-19 中兴通讯股份有限公司 隧道间带宽资源的管理方法和系统
US20130259067A1 (en) * 2012-03-27 2013-10-03 Eci Telecom Ltd. Method for Providing an MPLS Tunnel with Shared Bandwidth

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
BRADEN, R. ET AL.: "Resource ReSerVation Protocol (RSVP", RFC2205, 30 September 1997 (1997-09-30), pages 19 - 30, XP055330382 *
KOMPELLA, K. ET AL.: "Procedures for Modifying the Resource reSerVation Protocol (RSVP", RFC3936, 31 October 2004 (2004-10-31), pages 2 - 7, XP055330383 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111325403A (zh) * 2020-02-26 2020-06-23 长安大学 一种公路隧道机电设备剩余寿命预测方法
CN111325403B (zh) * 2020-02-26 2023-07-11 长安大学 一种公路隧道机电设备剩余寿命预测方法

Also Published As

Publication number Publication date
CN106304202A (zh) 2017-01-04
CN106304202B (zh) 2019-04-30

Similar Documents

Publication Publication Date Title
CN105580317B (zh) 用于diameter负载和过载信息及虚拟化的方法、系统和计算机可读介质
US10484285B2 (en) System, method and article of manufacture for using control plane for critical data communications in software-defined networks
US9106769B2 (en) Methods, systems, and computer readable media for congestion management in a diameter signaling network
JP5537462B2 (ja) 通信ネットワークシステム及び通信ネットワーク構成方法
US9397933B2 (en) Method and system of providing micro-facilities for network recovery
EP2985961B1 (en) Packet traffic control method and device based on multi-path transmission
US9173244B2 (en) Methods for establishing and using public path, M2M communication method, and systems thereof
JP2015518336A (ja) Ｄｉａｍｅｔｅｒ過負荷制御を実行するための方法、システムおよびコンピュータ読取可能媒体
US7924705B2 (en) Method and system for span-based connection aggregation
EP3656089B1 (en) Methods, systems, and computer readable media for operating a telecommunications network using an on-premises computing system and an off-premises cloud computing system
US9948506B2 (en) High availability internet services provisioning
CN112054969A (zh) 一种实现报文镜像的方法及装置
EP2750337B1 (en) Service cross-layer separated path calculation method, device and communication system
WO2016184268A1 (zh) 基于隧道共享的带宽控制方法及装置
US20140047534A1 (en) Filtering Network Packets in Multiple Forwarding Information Base Systems
WO2017118422A1 (zh) 隧道出端口预留带宽的分配方法及系统
US11153214B2 (en) In service flow capability update in guaranteed bandwidth multicast network
US11812378B2 (en) User management device, BNG, and BNG user internet access method and system
WO2016095605A1 (zh) 业务处理方法及装置
CA2939509A1 (en) Differentiated routing system and method
WO2021063022A1 (zh) 故障事件信息的上报方法及系统
WO2017059733A1 (zh) 一种避免网络共享环保护导致的流量风暴的方法及装置
WO2019165991A1 (zh) 基于灵活以太网的业务保护方法、服务器及存储介质
KR101932656B1 (ko) 소프트웨어 정의 네트워크를 방어하는 방법, 장치 및 컴퓨터 프로그램
WO2011057518A1 (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: 16795755

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

Country of ref document: EP

Kind code of ref document: A1