CN115102831B - Deployment method and system of distributed BGP service - Google Patents

Deployment method and system of distributed BGP service Download PDF

Info

Publication number
CN115102831B
CN115102831B CN202210895454.4A CN202210895454A CN115102831B CN 115102831 B CN115102831 B CN 115102831B CN 202210895454 A CN202210895454 A CN 202210895454A CN 115102831 B CN115102831 B CN 115102831B
Authority
CN
China
Prior art keywords
bgp
service
resource management
network
resource
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210895454.4A
Other languages
Chinese (zh)
Other versions
CN115102831A (en
Inventor
王巍
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fiberhome Telecommunication Technologies Co Ltd
Original Assignee
Fiberhome Telecommunication Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fiberhome Telecommunication Technologies Co Ltd filed Critical Fiberhome Telecommunication Technologies Co Ltd
Priority to CN202210895454.4A priority Critical patent/CN115102831B/en
Publication of CN115102831A publication Critical patent/CN115102831A/en
Application granted granted Critical
Publication of CN115102831B publication Critical patent/CN115102831B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04Network management architectures or arrangements
    • H04L41/042Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0893Assignment of logical groups to network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/50Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Landscapes

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

Abstract

The invention relates to the technical field of communication, and provides a deployment method and a deployment system of distributed BGP (Border gateway protocol) services. Wherein the method comprises: establishing a plurality of minimum resource management units according to the whole network resources and the network topology; according to the service affinity between the minimum resource management units, carrying out network resource aggregation on the minimum resource management units with high service affinity to obtain corresponding aggregated resource management units; and deploying the distributed BGP service according to the converged resource management unit. The invention deploys BGP services according to the service affinity, thereby belonging the devices or resources with more intimate service forwarding to the nanotubes of the same BGP service, and only affecting the BGP service of the network area where the corresponding devices or resources are located when the corresponding devices or resources are in failure, without affecting the normal forwarding of the services of other areas, thereby realizing the isolation of resources and the isolation of faults.

Description

Deployment method and system of distributed BGP service
Technical Field
The invention belongs to the technical field of communication, and in particular relates to a deployment method and system of distributed BGP (Border gateway protocol) service.
Background
As network scales become larger, network architecture has gradually changed from traditional integrated network architecture to distributed network architecture, where distributed BGP services (Border Gateway Protocal, border gateway protocol) are essential in distributed network architecture.
In the conventional distributed BGP service, the number of deployed services and service resources are fixedly set in the early stage of network construction, and the service resources are generally wasted when the number of services does not reach the expected maximum specification preset by the network. In such a case, once the network resources are adjusted, adjustment of a plurality of BGP services is needed, or once a single network resource fails, the adjustment of a plurality of BGP services may be affected, especially in a cloud data center, the BGP services are usually leased to tenants in a virtual terminal mode, a virtual private network is usually formed under a single tenant, service interaction inside the virtual private network is far more frequent than external interaction, at this time, it is generally expected that adjustment inside the virtual private network does not affect other virtual private networks, namely, resource isolation and fault isolation, and the conventional distributed BGP service deployment mode cannot meet the BGP service dynamic deployment requirement of the cloud data center.
In view of this, overcoming the drawbacks of the prior art is a problem to be solved in the art.
Disclosure of Invention
The technical problem to be solved by the invention is that the existing BGP service deployment method cannot realize resource isolation and fault isolation.
The invention adopts the following technical scheme:
in a first aspect, the present invention provides a deployment method of a distributed BGP service, including:
establishing a plurality of minimum resource management units according to the whole network resources and the network topology;
according to the service affinity between the minimum resource management units, carrying out network resource aggregation on the minimum resource management units with high service affinity to obtain corresponding aggregated resource management units;
according to the converged resource management unit, deploying distributed BGP service; wherein, one BGP service corresponds to one convergent resource management unit and manages network resources under the corresponding convergent resource management unit.
Preferably, the network resource aggregation is performed on the minimum resource management units with high affinity according to the affinity between the minimum resource management units to obtain corresponding aggregate resource management units, which specifically includes:
taking the first resource management units meeting the convergence condition as second resource management units, calculating the service affinity between any two second resource management units, and carrying out network resource convergence on the two second resource management units with the highest service affinity to obtain a third resource management unit;
The third resource management unit obtained by the previous network resource aggregation replaces the two first resource management units for network aggregation, and the next network resource aggregation is iterated until the number of the second resource management units is less than two or the total number of the first resource management units and the third resource management units is less than or equal to the preset number; the minimum resource management unit is used as a first resource management unit when the first network resource aggregation is carried out;
the first resource management unit and the third resource management unit obtained after the iteration is completed are corresponding convergence resource management units.
Preferably, the calculating the service affinity between any two second resource management units specifically includes:
calculating the business affinity between the network resources of the same type in the two second resource management units;
and taking the weighted summation of the service affinities between all types of network resources in the two second resource management units as the service affinities of the corresponding two second resource management units.
Preferably, when a new network resource is added in the network, the method further comprises:
dynamic capacity expansion is carried out on BGP service, in particular,
Judging whether the number of BGP services is required to be increased according to the load condition of each BGP service;
if the number of BGP services does not need to be increased, selecting a corresponding BGP service from deployed BGP services to perform nano-tube on the newly increased network resources;
if the number of BGP services needs to be increased, the distributed BGP services are redeployed according to the business affinity.
Preferably, the determining whether to increase the number of BGP services according to the load situation of each BGP service specifically includes:
if the number of BGP services whose corresponding load exceeds the first preset load threshold exceeds the preset duty ratio in all BGP services and/or the load variance calculated by the loads of all BGP services exceeds the preset variance threshold, the number of BGP services is increased.
Preferably, the selecting a corresponding BGP service from deployed BGP services to perform a nanotubes on the newly-added network resource specifically includes:
in the deployed first BGP service, taking the BGP service with the corresponding load lower than a second preset load threshold as a second BGP service;
and calculating the business affinity of the newly-added network resource and each second BGP service, and selecting the second BGP service with the highest business affinity to perform nano-tube on the newly-added network resource.
Preferably, the redeploying the distributed BGP service according to the service affinity specifically includes:
for the newly added network resource, when the distributed BGP service is redeployed, directly releasing the route corresponding to the newly added network resource;
for the existing network resources in the network, a route deletion message is issued by using the distributed BGP service which is not redeployed, a new route is issued by using the distributed BGP service which is redeployed, and route update and route decision are processed in a delayed manner.
Preferably, when a network resource pruning occurs in the network, the method further comprises:
dynamic capacity reduction is carried out on BGP services, and in particular,
and if the load of the corresponding BGP service is lower than a third preset load threshold, the network resources under the BGP service nanotubes are submitted to other BGP services for nanotubes, and the BGP service is deleted.
Preferably, the method further comprises:
judging whether BGP service is abnormal or not according to the connection state and health state of the BGP service;
and deleting the abnormal BGP service and releasing the corresponding network resources.
In a second aspect, the present invention further provides a distributed BGP service deployment system, which includes an acquisition module, a BGP service policy module, and a BGP service deployment module, where:
The acquisition module is used for acquiring the whole network resources and the network topology;
the BGP service strategy module is used for calculating the quantity of BGP services and corresponding network resources;
the BGP service deployment module is configured to deploy distributed BGP services according to the calculated BGP service number and the corresponding network resources.
In a third aspect, the present invention further provides a deployment device of a distributed BGP service, configured to implement the deployment method of the distributed BGP service in the first aspect, where the device includes:
at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor for performing the distributed BGP service deployment method of the first aspect.
In a fourth aspect, the present invention also provides a non-volatile computer storage medium storing computer executable instructions for execution by one or more processors to perform the method of deploying distributed BGP services according to the first aspect.
The invention deploys BGP services according to the service affinity, thereby belonging the devices or resources with more intimate service forwarding to the nanotubes of the same BGP service, and only affecting the BGP service of the network area where the corresponding devices or resources are located when the corresponding devices or resources are in failure, without affecting the normal forwarding of the services of other areas, thereby realizing the isolation of resources and the isolation of faults.
Drawings
Fig. 1 is a schematic flow chart of a deployment method of a distributed BGP service according to an embodiment of the present invention;
fig. 2 is a flow chart of a deployment method of a distributed BGP service according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a CLOS network according to an embodiment of the present invention;
fig. 4 is a flow chart of a deployment method of a distributed BGP service according to an embodiment of the present invention;
fig. 5 is a schematic flow chart of a deployment method of a distributed BGP service according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of attributes contained in elements in a resource management unit set according to an embodiment of the present invention;
fig. 7 is a schematic flow chart of a deployment method of a distributed BGP service according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a load indicator of BGP services provided by an embodiment of the present invention;
fig. 9 is a schematic architecture diagram of a distributed BGP service deployment system according to an embodiment of the present invention;
fig. 10 is a schematic architecture diagram of a distributed BGP service deployment system according to an embodiment of the present invention;
fig. 11 is a schematic architecture diagram of a distributed BGP service deployment device according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. In addition, the technical features of the embodiments of the present invention described below may be combined with each other as long as they do not collide with each other.
Example 1:
the embodiment of the invention provides a deployment method of distributed BGP services, as shown in figure 1, comprising the following steps:
in step 201, a plurality of minimum resource management units are established based on the total network resources and the network topology.
The minimum resource management unit corresponds to the minimum BGP service management unit and network resources of the corresponding minimum BGP service management unit.
The minimum resource management unit is not an entity that actually acts, but is an alternative conceptual expression, and the minimum resource management unit is used for representing the corresponding minimum BGP service management unit and network resources corresponding to the minimum BGP service management unit, and in a specific implementation process, since the minimum BGP service management unit is also one of the network resources, the minimum resource management unit can be regarded as a set of network resources. The network resources and minimum BGP service management elements may be represented using corresponding attributes, with the minimum resource management elements being represented using corresponding sets of attributes. Where the minimum BGP service management unit is the minimum unit that can be managed by a single BGP service when building a distributed BGP service in the network, and is typically set by those skilled in the art based on the network size and BGP service management requirements. As in the cloud data center, the minimum BGP service management element is at least one of a virtual private network, a virtual switch, or a virtual terminal.
In step 202, according to the service affinities of the minimum resource management units, network resource aggregation is performed on the minimum resource management units with high service affinities, so as to obtain corresponding aggregated resource management units.
The service affinity refers to the degree of closeness in the process of participating in service forwarding, for example, for a cloud data center, the service affinity is generally divided into a plurality of virtual private networks, and the service forwarding frequency of a virtual terminal located in the same virtual private network is generally higher than the service forwarding frequency of a virtual terminal in a different virtual private network, that is, the service forwarding frequency is relatively close in the process of service forwarding. And for large-scale networks, the service forwarding frequency between terminals under the same subnet or the same switch is generally higher than the service forwarding frequency between terminals under different subnets or different switches, i.e. the service forwarding process is relatively close. And the single service forwarding layer analysis has higher relative service affinity related to resource crossing in the service forwarding process. If the terminals under the same switch relate to the resource use of the same switch during service forwarding, that is, there is resource crossover in the service forwarding process, the service affinity is also considered to be higher. The traffic affinity may be used to represent a regional division of the network.
The service affinity is not specific to the minimum resource management unit and the minimum BGP service management unit, but may exist between entities including or representing network resources or network devices. For example, for the minimum resource management unit, the service affinity is calculated by the minimum BGP service management unit represented by the minimum resource management unit.
In step 203, according to the aggregate resource management unit, deploying a distributed BGP service; wherein, one BGP service corresponds to one convergent resource management unit and manages network resources under the corresponding convergent resource management unit.
The network resource aggregation specifically means that network resources in one or more minimum resource management units are combined, and the combined aggregate resource management unit is used for representing one or more minimum BGP service management units and all network resources of the corresponding one or more minimum BGP service management units.
The network resources under the corresponding convergent resource management units of the nanotubes specifically refer to the minimum BGP service management unit managed by the corresponding BGP service and the network resources corresponding to the minimum BGP service management unit.
According to the embodiment, the deployment of the BGP service is carried out according to the service affinity, so that the equipment or the resource with more intimate service forwarding belongs to the nano-tube of the same BGP service, when the corresponding equipment or the resource fails, the BGP service of the network area is only affected, and the normal forwarding of the service of other areas is not affected, thereby realizing the resource isolation and the fault isolation.
In the foregoing embodiment, according to the service affinities between the minimum resource management units, one most common implementation manner for performing network resource aggregation on the minimum resource management units with high service affinities between the minimum resource management units is: calculating the service affinity between any two minimum resource management units, carrying out network resource aggregation on the two minimum resource management units with the highest service affinity, calculating the service affinity for the minimum resource management units which do not carry out network resource aggregation, selecting two minimum resource management units to carry out network resource aggregation, and carrying out the network resource aggregation in sequence until all the minimum resource management units carry out network resource aggregation or only the rest minimum resource management units do not carry out network resource aggregation. In such an implementation, the number of BGP services must be the number of minimum resource management units divided by 2, or the number of minimum resource management units divided by 2 plus 1. This greatly limits the flexibility of deployment of BGP services and is also an excessive waste of BGP services in cases where the network resources corresponding to the minimum resource management units are minimal. In view of this problem, in combination with the foregoing embodiments, there is a preferred embodiment, that is to perform network resource aggregation on the minimum resource management units with high affinity according to the affinity between the minimum resource management units, to obtain corresponding aggregate resource management units, as shown in fig. 2, including:
In step 301, the first resource management unit satisfying the aggregation condition is used as the second resource management unit, the service affinity between any two second resource management units is calculated, and the network resource aggregation is performed on the two second resource management units with the highest service affinity therebetween, so as to obtain the third resource management unit.
In step 302, the third resource management unit obtained by performing network resource aggregation last time replaces the two first resource management units performing network aggregation, and iterates to perform next network resource aggregation until the number of the second resource management units is less than two, or the total number of the first resource management units and the third resource management units is less than or equal to the preset number; the minimum resource management unit is used as a first resource management unit when the first network resource aggregation is carried out.
In step 303, the first resource management unit and the third resource management unit obtained after the iteration is completed are corresponding aggregate resource management units.
The third resource management unit obtained by performing network resource aggregation at the previous time replaces the two first resource management units performing network aggregation, and specifically comprises the following steps: discarding two first resource management units for network convergence, and taking the obtained third resource management unit as the first resource management unit to participate in the subsequent iteration process of network resource convergence.
The convergence condition and the preset number are obtained by common analysis of BGP service management requirements and network resources by a person skilled in the art, and the resource quantity of a single BGP service is limited by formulating the convergence condition, so that the load of the BGP service is controlled. And controlling the distribution degree of BGP services by formulating a preset number.
The preset number can also be set by a user, and when the preset number is handed over to the user for setting, the preset number needs to be greater than or equal to a minimum preset number threshold set by a person skilled in the art so as to ensure the minimum distribution degree of BGP services.
The aggregation condition may be that the number of minimum BGP service management units represented in the first resource management unit does not exceed a corresponding number. The more accurate implementation is that the aggregation condition is that the number of network resources of the corresponding type in the first resource management unit is smaller than or equal to a preset resource number threshold; wherein the preset resource quantity threshold is obtained by a person skilled in the art according to BGP service management requirements and network resource analysis. The determination of the aggregation conditions for the network resources of which types may exist under a minimum resource management unit is also obtained by those skilled in the art according to BGP service management requirements. The convergence condition judgment can be performed for one type of network resource, and the convergence condition judgment can be performed for a plurality of types of network resources.
For better understanding, the set G will be built using the corresponding set and elements, each of which is given by G, as an example of the minimum resource management unit as an element, as part of the critical process illustrating the iteration i And (3) representing, wherein i is the sequence number of the corresponding element.
When the network convergence is carried out for the nth time, m elements exist in the set G, if G i1 And g i2 Meets the convergence condition, and the service affinity among the service affinities is calculated to be the highest, g is calculated to be i1 And g i2 Network resource aggregation is carried out to obtain g k Will g i1 And g i2 Delete from collection G, get G k When the element is inserted into the collection G, the number of the elements in the collection G is m-1 when the n+1th time of network collection, the network collection is carried out again by the collection G of m-1, and whether the elements meet the collection condition is required to be judged when the network collection is carried out each time. When the first aggregation is performed, the elements in the set G are the minimum resource management units,after the iteration is finished, each element in the set represents an aggregate resource management unit.
In the preferred embodiment, the third resource management unit obtained by aggregation also participates in subsequent aggregation in an iterative network resource aggregation manner, and two resource management units with highest service affinity are aggregated each time, so that the service affinity between the minimum BGP service management units under a single BGP service nano-tube is ensured to be higher than the service affinity between the minimum BGP service management units under different BGP service nano-tubes. And the load of BGP services and the quantity of BGP services are controlled by the convergence condition and the preset quantity, so that the high isolation of resources and faults in the network is ensured on the basis of adjustable distribution degree of BGP services.
In the above embodiment, one more conceivable implementation manner of calculating the service affinity between any two second resource management units is:
dividing a multi-stage network area set according to network topology, setting a corresponding affinity value for each network area, and determining the business affinity between two minimum BGP service management units according to the network areas where any two minimum BGP service management units are located, namely the business affinity between the corresponding minimum resource management units.
If the affinity value is set as a for the virtual private network, the affinity value is set as b for the virtual private network, and when two minimum BGP service management units belong to the same virtual private network but do not belong to the same virtual private network, the service affinity between the two minimum BGP service management units is a, that is, the service affinity between the minimum resource management units representing the two minimum BGP service management units is a.
The above implementation manner is simple and direct, but because it only depends on the relationship between network topologies, and does not involve the situation of resource intersection, in view of this problem, in combination with the above embodiment, there is also a preferred embodiment that calculates the service affinity between any two second resource management units, specifically including:
Calculating the business affinity between the network resources of the same type in the two second resource management units;
and taking the weighted summation of the service affinities between all types of network resources in the two second resource management units as the service affinities of the corresponding two second resource management units.
Each second resource management unit may include multiple types of network resources, for example, when the virtual switch is taken as the minimum BGP service management unit in the cloud data center network scenario, the type of the corresponding network resource may be at least one of a virtual switch, an L0 switch connected to the virtual switch, an L1 switch connected to the L0 switch, an L2 switch connected to the L1 switch, a server to which the virtual switch belongs, a virtual terminal under the virtual switch, a subnet to which the virtual terminal belongs, and a virtual private network described by the virtual switch.
One calculation of the service affinity between the network resources of the same type is specifically: and calculating the quantity ratio of the quantity of the resources which generate the intersection between the network resources of the same type in the two second resource management units in all the network resources of the same type in the two second resource management units. Since the service forwarding affinity is also related to resource crossing, the service affinity between the same type of network resources can be obtained through resource crossing calculation. And may use a weighted sum of the traffic affinities between all the same type of network resources in the second resource management units as the traffic affinities of the respective two second resource management units.
The weight corresponding to each type of network resource is analyzed by a person skilled in the art according to the corresponding network architecture or user requirements.
According to the preferred embodiment, the service affinity of the network resources of each type in the two second resource management units is calculated, so that the service affinity of the two second resource management units is obtained comprehensively, the resource cross relationship of the two second resource management units can be expressed more directly and accurately, and the service affinity is represented.
In practical situations, the network resources of the network are not unchanged, when the network resources are newly added in the network, how to enable the newly added network resources to be managed by the distributed BGP service, and for this problem, there is the following preferred embodiment, that is, when the network resources are newly added in the network, the method further includes: expanding BGP service, specifically:
judging whether the number of BGP services is required to be increased according to the load condition of each BGP service;
if the number of BGP services does not need to be increased, selecting a corresponding BGP service from deployed BGP services to perform nano-tube on the newly increased network resources;
if the number of BGP services needs to be increased, the distributed BGP services are redeployed according to the business affinity.
The load condition comprises at least one of memory use condition, CPU use condition, virtual terminal number of the nanotubes and subnet number of the nanotubes of the BGP service.
According to the preferred embodiment, through the loading condition of the BGP service, whether the newly added minimum BGP service causes the overload of the existing BGP service or not is judged under the current condition, so that whether the corresponding BGP service is newly added or not is judged, and the influence on service forwarding caused by the overload of the BGP service is avoided. And when BGP service is newly added, the distributed BGP service is still redeployed according to the business affinity, so that the resource isolation and the fault isolation are still realized after the minimum BGP service management unit is newly added.
In the foregoing embodiment, the most common implementation manner for determining whether to increase the number of BGP services according to the load situation of each BGP service is: and when the overall load of the distributed BGP service exceeds a preset ratio, adding the BGP service. However, in actual situations, not only the overall load of the distributed BGP service may affect the traffic forwarding efficiency, when the load of the very individual BGP service is very high, but also the traffic forwarding efficiency may be affected, and for this case, in combination with the foregoing embodiment, there is the following preferred embodiment, where the determining whether to increase the number of BGP services according to the load situation of each BGP service specifically includes:
If the number of BGP services whose corresponding load exceeds the first preset load threshold exceeds the preset duty ratio in all BGP services and/or the load variance calculated by the loads of all BGP services exceeds the preset variance threshold, the number of BGP services is increased.
Wherein the first preset load threshold, the preset duty cycle and the preset variance threshold are all obtained by a person skilled in the art according to BGP service management requirements and network resource analysis.
And the method can also judge whether the load of the BGP service exceeds a first preset load threshold value or not by formulating a plurality of load indexes for the BGP service and judging whether the load of the BGP service exceeds the first preset load threshold value or not by one or more load indexes, and at the moment, the first preset load threshold value is obtained by comprehensive analysis of a plurality of load indexes by a person skilled in the art.
The preferred embodiment not only calculates the load variance through the number of high-load BGP services, but also is used for representing the deviation degree between the load and the average load of the BGP services, so as to judge whether to add the BGP services newly, further maintain the load balance among the BGP services and ensure the efficiency of service forwarding.
In order to continuously ensure the resource isolation and the fault isolation under the condition that the BGP service is not newly added, in combination with the above embodiment, the following preferred embodiment is provided, that is, the newly added network resource is managed by selecting a corresponding BGP service from the deployed BGP services, which specifically includes:
And in the deployed first BGP service, taking the BGP service with the corresponding load lower than a second preset load threshold as a second BGP service.
And calculating the business affinity of the newly-added network resource and each second BGP service, and selecting the second BGP service with the highest business affinity to perform nano-tube on the newly-added network resource.
Wherein the second preset load threshold is obtained by a person skilled in the art according to BGP service management requirements and network resource analysis. The second preset load threshold is usually equal to or less than the first preset load threshold.
The preferred embodiment maintains the resource isolation and fault isolation of the network by selecting the minimum BGP service management unit newly added to the corresponding BGP service nano-tube through service affinity.
When the distributed BGP service is redeployed, the foregoing embodiments provide, in combination with the foregoing embodiments, a preferred implementation manner of redeploying the distributed BGP service according to service affinity, where the method specifically includes:
for the newly added network resource, when the distributed BGP service is redeployed, the route corresponding to the minimum BGP service management unit is directly released.
For the existing network resources in the network, a route deletion message is issued by using the distributed BGP service which is not redeployed, a new route is issued by using the distributed BGP service which is redeployed, and route update and route decision are processed in a delayed manner.
The delay processing route updating and route decision is specifically as follows: after receiving the deleted route message from BGP service, it does not execute route update and route decision immediately, if no new route message of the same route is received within the preset time period after receiving the deleted route message, then executes route update and route decision, otherwise, when receiving the new route message of the same route, it does not execute route update and route decision, but retains the route.
The preferred embodiment avoids that the same route of the local router is frequently deleted and newly added when BGP service is changed through route updating and route decision delay processing, reduces the time consumed when BGP service is changed, and avoids resource consumption caused by frequent route updating and route decision.
In the actual use case, there is also a situation that BGP services in the network are abnormal, and if abnormal BGP services are not processed, network resources may be continuously occupied by abnormal BGP services and cannot be effectively utilized, and in combination with the above embodiment, there is the following preferred implementation manner, that is, the method further includes:
and judging whether the BGP service is abnormal or not according to the connection state and the health state of the BGP service.
And deleting the abnormal BGP service and releasing the corresponding network resources.
The method further comprises the steps of: the BGP service of the user-specified shrinkage is processed, specifically: deleting the corresponding minimum resource management unit appointed to be deleted by the user and redeploying the BGP service.
The method further comprises the steps of: when network resource pruning occurs in the network, the BGP service is scaled, and in particular,
and if the load of the corresponding BGP service is lower than a third preset load threshold, the network resources under the BGP service nanotubes are submitted to other BGP services for nanotubes, and the BGP service is deleted.
The implementation of the network resource delivery to other BGP service nanotubes is consistent with the implementation thought when the network resource is newly added, and is specifically:
and in the deployed first BGP service, taking the BGP service with the corresponding load lower than the second preset load threshold value but not lower than the third preset load threshold value as a third BGP service.
And calculating the business affinity of the network resource and each third BGP service, and selecting the third BGP service with the highest business affinity to perform nano-tube on the network resource.
Or the third BGP service quantity is used as the contracted BGP service quantity, and the BGP service is redeployed.
In the present invention, the expression similar to "a and/or B" means that the implementation manner may be implemented in a manner of taking a as an object, or in a manner of taking B as an object, or in a manner of taking a combination of a and B as an object, and in which a and B may be replaced by specific subject name objects according to requirements of a specific description scenario.
The terms "first," "second," and "third" in this embodiment have no special limitation, and the description is merely for convenience of description of different individuals in a class of objects, and should not be construed as a sequential or otherwise specifically defined meaning.
Example 2:
the invention is based on the method described in embodiment 1, and combines specific application scenes, and the implementation process in the characteristic scene of the invention is described by means of technical expression in the relevant scene.
In this embodiment, a distributed BGP service is deployed in a cloud data center, where a bottom network of the cloud data center is configured by using a CLOS architecture, and a network hierarchy architecture of the cloud data center is shown in fig. 3.
The deployment process of the corresponding distributed BGP service is shown in fig. 4, and specifically includes:
in step 401, the ports and the port opposite ends of the switch are traversed, link connection between the switches is calculated, and a physical network topology composed of the switches is constructed. Estimating the number of tenants of the cloud data center according to the specification of a single virtual terminal in the cloud data center; each tenant represents a private virtual network of the networks. Step 202 is entered.
In step 402, a virtual switch is used as a minimum BGP management unit, and a resource management unit set G is constructed and initialized, where each element in the set G represents a minimum resource management unit, and manages a minimum BGP management unit; step 403 is entered.
In step 403, element aggregation is performed on the elements in the resource management unit set G, where each element in the set G represents an aggregate resource management unit; step 404 is entered.
In step 404, distributed BGP services are deployed according to the aggregated set G, where an element in the set G deploys a BGP service correspondingly.
The following will describe the above steps in detail in connection with a specific scenario, where the building and initializing the resource management unit set G specifically includes:
constructing a corresponding element g by taking each virtual switch in the cloud data center as a minimum BGP service management unit i And i is the serial number of the corresponding virtual switch, and is less than or equal to the number N of the virtual switches in the cloud data center.
Each element contains a corresponding type of attribute, and each type of attribute represents one type of network resource.
The element aggregation, as shown in fig. 5, specifically includes:
In step 501, each element G in the set of resource management units G is traversed i The method comprises the steps of carrying out a first treatment on the surface of the Judgment element g i If the number of the corresponding attributes is greater than the number of the preset attributes, g is determined i Move to the convergence set, otherwise still get g i Remain in set G, enter step 502.
In step 502, it is determined whether the number of elements in the set G is greater than or equal to 2, and if the number of elements is greater than 2, step 503 is entered; otherwise, go to step 507 and end the convergence.
In step 503, it is determined whether the total number of elements in the collection G and the convergence collection is less than or equal to the preset number of elements; if the total number of elements is less than or equal to the preset number of elements, step 507 is entered, otherwise step 504 is entered.
In step 504, calculating a business affinity between any two elements in the collection G; step 505 is entered.
In step 505, the elements in the set G with the highest service affinity are aggregated, and step 506 is entered.
In step 506, element aggregation is performed on two elements with highest service affinities in the set G, whether the number of corresponding attributes in new elements obtained by aggregation is greater than the preset attribute number is judged, if so, the new elements are moved to the aggregation set, otherwise, the new elements are still kept in the set G, and in step 502, whether iteration is continued is judged.
In step 507, all elements in the aggregate set are moved to the set G, where the set G is the aggregate management unit set. And (5) ending the aggregation.
Taking a CLOS architecture networking as an example, a calculation process of service affinity between two elements is shown, and the calculation process of the service affinity between the element A and the element B is set as follows: and calculating the service affinity between each type of attribute, namely the network resources of the same type, in the element A and the element B, wherein the weighted summation of the service affinities of the network resources is taken as the service affinities of the two elements.
The present embodiment represents the business affinities between network resources with the resource intersection degree of the network resources. The calculation process of the business affinities of the corresponding element a and the element B is expressed as a formula:
Figure BDA0003765772720000171
wherein J (A, B) represents the business affinity between element A and element B, K i Representing the weight corresponding to each type of network resource, i representing the network resource type number, NUM () representing the number of elements in the corresponding set, A i Representing a set of network resources of a type in element A, namely a type of attribute under element A, B i Representing a set of network resources of a type in element B, i.e. a type of attribute under element B. A is that i ∩B i Representative set A i And set B i Is the intersection of A i ∪B i Representative set A i And set B i Is a union of (a) and (b). From the intersection to obtain A i And B i Intersecting network resources, obtaining A from union i And B i The resource crossing degree of the network resources of the corresponding type is obtained through the ratio of the element quantity, namely the service affinity among the network resources, and then K is used for obtaining the network resources of the corresponding type i The weighted summation results in a business affinity between element a and element B.
Weight K i Are analyzed by those skilled in the art based on the corresponding network architecture or user requirements. In the CLOS architecture networking, the network architecture is shown in fig. 3, and includes a Tier3, tier2, and Tier1, and according to the network hierarchy, each element constructed includes attribute types shown in fig. 6, including: corresponding virtual switch, L0 switch connected with corresponding virtual switch, L1 switch connected with corresponding L0 switch, L2 switch connected with corresponding L1 switch, server of virtual switch, virtual terminal sub-network and virtual private network, wherein each type of attribute is stored in list formAnd storing corresponding IDs for representing attributes in the list so as to facilitate the convergence of subsequent elements, and defining a sub-element list in the elements so as to store sub-elements forming the elements in the convergence process of the subsequent elements, thereby facilitating the expansion and contraction of the later BGP service.
And establishing a corresponding weight value range for each type of network resources according to the CLOS architecture networking, and enabling the weight value to be selected according to the user requirement in the corresponding value range.
The element aggregation process of steps 501-507 described above will be described below by way of example, assuming that G is present in the constructed and initialized collection G 1 、g 2 、g 3 、g 4 And g 5 The 5 elements are set to be converged under the condition that the number of virtual terminals in the corresponding elements is not more than 10000, the number of virtual private networks is not more than 100, the preset number is set to be 3, namely, convergence is stopped when the 3 elements are converged.
Let g 2 In which there are 101 virtual private networks, g 2 Not participate in subsequent element aggregation, but calculate g 1 And g is equal to 3 The service affinity between the two is 49 g 1 And g is equal to 4 The service affinity between the two is 49 g 1 And g is equal to 5 The service affinity between the two is 55 g 3 And g is equal to 4 The service affinity between the two is 32 g 4 And g is equal to 5 The service affinity between the two is 27, g with the highest service affinity between the two is selected 1 And g is equal to 5 Element aggregation is carried out, and the aggregated element is g (1,5) If the convergence condition is satisfied, the element participating in the convergence of the subsequent element has g (1,5) 、g 3 And g 4 G is calculated (1,5) And g 3 The service affinity between the two is 40 g (1,5) And g 4 The service affinity between the two is 44, g is given (1,5) And g 4 Element aggregation is carried out to obtain g (1,4,5) The final element is g 2 、g 3 And g (1,4,5) The number of elements has reached 3, so the convergence is stopped.
The deploying a distributed BGP service according to the aggregated set G in step 404 specifically includes: updating a configuration template for deploying BGP service according to the elements in the set G, deploying distributed BGP service according to the configuration template of BGP service, and establishing BGP topology, wherein network resources and network parameters of the corresponding BGP service are set in the configuration template.
After the initial deployment of the distributed BGP service is finished, there is also a case where the number of minimum BGP service management units, i.e., virtual switches, in the network changes.
When a virtual switch is newly added, the present embodiment further includes the steps of:
in step 601, the load of each BGP service is collected, and whether BGP services need to be added is determined according to the load of BGP services, if BGP services need to be added, step 603 is entered, and if BGP services need to be added, step 602 is entered. The load of BGP service is shown in fig. 8, and includes a plurality of load indexes, that is, BGP service memory usage, BGP service CPU usage, the number of virtual terminals under BGP service, and the number of virtual private networks under BGP service, and sets a corresponding threshold for each load index, and when one or more indexes of BGP service exceeds the corresponding threshold, the load of BGP service is considered to exceed the first load threshold. If the corresponding load exceeds the BGP service quantity ratio of the first preset load threshold value by more than 20%, or calculating the variance of all BGP services, and if the variance exceeds the preset variance threshold value, the BGP service is considered to be needed to be added.
In step 602, the newly added virtual switch is used as a minimum BGP management unit, a corresponding minimum resource management unit is established, the service affinity between the minimum resource management unit and each convergence resource management unit in the set G is calculated, an element G with the highest service affinity is selected to perform element convergence, the newly added virtual switch and corresponding network resource of the BGP service nanotubes corresponding to G are selected, route update is performed, and deployment is ended.
In step 603, the newly added virtual switch is used as a minimum BGP management unit, a corresponding minimum resource management unit is established, and a BGP service with a load lower than 80% is selected as a second BGP service from all deployed BGP services, and aggregate resources in a set G corresponding to the second BGP service are selectedThe management unit is split into minimum resource management units, and the split minimum resource management units and the minimum resource management units corresponding to the newly added virtual switch form a set G 2 . Step 604 is entered.
In step 604, for G 2 Element aggregation is carried out until the quantity of BGP services obtained by aggregation is 1 plus the quantity of the original second BGP services. And redeploying the second BGP service according to the converged resource management unit, carrying out route updating and route decision, and ending the deployment.
When the virtual switch is reduced, there are two cases, one is to specify the capacity reduction for the user and reduce the virtual switch, that is, specify the capacity reduction, one is to dynamically reduce the capacity according to BGP load, and one is to provide abnormal service between BGP service and the virtual switch, that is, active capacity reduction.
Aiming at the designated capacity reduction, the minimum resource management unit of the corresponding virtual switch is deleted from the set G or the convergent resource management unit of the set G, and the corresponding network resource under the corresponding BGP service is released to carry out route update and route decision.
Aiming at dynamic capacity reduction, specifically, the load of each BGP service is collected, when the load of the BGP service is lower than a third preset load threshold, for example, 10%, network resources under the BGP service nanotubes are submitted to other BGP services for nanotubes, and the BGP service is deleted. Wherein, the network resource under the BGP service nanotubes is still managed by other BGP services according to the affinity, and the method is specifically: in all deployed BGP services, selecting a BGP service with a corresponding load lower than 80% and not lower than 10% as a third BGP service, splitting aggregate resource management units in a set G corresponding to all BGP services into minimum resource management units and forming a minimum resource management unit set G 3 . For G 3 Element aggregation is carried out according to the service affinity degree until the quantity of BGP services obtained by aggregation is the quantity of third BGP services. And redeploying the second BGP service according to the converged resource management unit, carrying out route updating and route decision, and ending the deployment.
Aiming at active capacity reduction, in particular to obtaining the connection state and the health state of BGP service, when the connection of the corresponding BGP service is interrupted or the health state of the BGP service is abnormal, deleting the corresponding BGP service, and carrying out route updating and route decision. The connection interruption of the BGP service specifically refers to interruption of heartbeat messages of the BGP service management module and the BGP service module, and the BGP service health state anomaly includes a neighbor failure state establishment, internal data anomaly, and the like.
The route updating and route decision comprises the following steps:
when receiving the route information, judging whether the route information is sent by a control plane of BGP service, if yes, comparing whether the publisher of the deleted route is the same as the publisher of the route stored in the local router, if not, immediately starting the route publishing and decision flow of the local router, deleting the corresponding table items in the local route table and the forwarding table, and completing route convergence.
If the publisher of the deleted route is the same as the publisher of the route stored in the local router, the route publishing and decision process of the local router is not started, whether a new route message consistent with the deleted route is received or not is judged in a preset time period, if the new route message consistent with the deleted route is received, the route publishing and decision process of the local router is not executed, and the existing route information is delayed, so that the repeated deletion of the same route in the expanding or shrinking process of BGP service is avoided. If the consistent newly added routing information is not received, starting a route release and decision process of the local router after the preset time period is finished, deleting corresponding table entries in the local routing table and the forwarding table, and completing route convergence.
The preset time period is obtained by analysis of response rate of the network and deployment requirement of BGP service by a person skilled in the art, and is realized by a timer in the embodiment, namely, when a deleting route message sent by a control plane of BGP service is received, the timer is started to delay, and in the delay process of the timer, the route release and decision process of the local router is not executed.
The implementation method for judging whether the routing message is sent by the control plane of the BGP service comprises the following steps: when the attribute value is defined as 0, the routing message is not sent by the control plane of the BGP service, and when the attribute value is 1, the routing message is sent by the control plane of the BGP service.
Example 3:
fig. 9 is a schematic architecture diagram of a distributed BGP service deployment system according to an embodiment of the present invention, where the system includes a resource acquisition module, a BGP service policy module, and a BGP service deployment module, where:
the acquisition module is used for acquiring the whole network resources and the network topology; the BGP service strategy module is used for calculating the quantity of BGP services and corresponding network resources; the BGP service deployment module is configured to deploy distributed BGP services according to the calculated BGP service number and the corresponding network resources. After deployment is completed, the system also comprises a BGP service management module, wherein the BGP service management module manages all BGP services and centrally manages device routes. Fig. 10 is a schematic diagram of the BGP service management module and BGP service architecture after deployment, where each BGP service nano-tube corresponds to a network resource and issues and receives a routing message.
The decision and deployment of the corresponding BGP service are based on the same concept as the deployment method of the distributed BGP service in embodiment 1, and specific content may be referred to the description in the embodiment of the method of the present invention, which is not repeated herein.
Example 4:
fig. 11 is a schematic architecture diagram of a distributed BGP service deployment device according to an embodiment of the present invention. The deployment apparatus of the distributed BGP service of the present embodiment includes one or more processors 21 and a memory 22. In fig. 11, a processor 21 is taken as an example.
The processor 21 and the memory 22 may be connected by a bus or otherwise, for example in fig. 8.
The memory 22 is used as a non-volatile computer readable storage medium for storing non-volatile software programs and non-volatile computer executable programs, such as the deployment method of distributed BGP services in example 1. The processor 21 executes a deployment method of the distributed BGP service by running nonvolatile software programs and instructions stored in the memory 22.
The memory 22 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 22 may optionally include memory located remotely from processor 21, which may be connected to processor 21 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The program instructions/modules are stored in the memory 22, and when executed by the one or more processors 21, perform the distributed BGP service deployment method in embodiment 1 described above, for example, perform the steps shown in fig. 1, 2, 4, 5, and 7 described above.
It should be noted that, because the content of information interaction and execution process between modules and units in the above-mentioned device and system is based on the same concept as the processing method embodiment of the present invention, specific content may be referred to the description in the method embodiment of the present invention, and will not be repeated here.
Those of ordinary skill in the art will appreciate that all or a portion of the steps in the various methods of the embodiments may be implemented by a program that instructs associated hardware, the program may be stored on a computer readable storage medium, the storage medium may include: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.
The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather is intended to cover all modifications, equivalents, and alternatives falling within the spirit and principles of the invention.

Claims (10)

1. A method for deploying a distributed BGP service, comprising:
establishing a plurality of minimum resource management units according to the whole network resources and the network topology;
according to the service affinity between the minimum resource management units, carrying out network resource aggregation on the minimum resource management units with high service affinity to obtain corresponding aggregated resource management units;
According to the converged resource management unit, deploying distributed BGP service; wherein, a BGP service corresponds to a convergent resource management unit and manages network resources under the corresponding convergent resource management unit; wherein, the BGP is Border Gateway Protocal, border gateway protocol;
representing the service affinity between minimum resource management units by the resource crossing degree of network resources, wherein the calculation formula of the service affinity is as follows
Figure QLYQS_2
The method comprises the steps of carrying out a first treatment on the surface of the Wherein (1)>
Figure QLYQS_7
Representing the traffic affinity between minimum resource management unit A and minimum resource management unit B,/for the minimum resource management unit A and minimum resource management unit B>
Figure QLYQS_10
Representing the weight corresponding to each type of network resource, i representing the network resource type serial number,/for each type of network resource>
Figure QLYQS_3
Representing the number of elements in the respective set, +.>
Figure QLYQS_6
Represents a set of a class of network resources in the minimum resource management unit a,/>
Figure QLYQS_8
Representing a set of one type of network resource in the minimum resource management unit B; />
Figure QLYQS_11
Representative set->
Figure QLYQS_1
And set->
Figure QLYQS_5
Is->
Figure QLYQS_9
Representative set->
Figure QLYQS_12
And set->
Figure QLYQS_4
Is a union of (a) and (b).
2. The deployment method of distributed BGP services according to claim 1, wherein the performing network resource aggregation on the minimum resource management units with high affinity according to the affinity between the minimum resource management units to obtain corresponding aggregated resource management units specifically includes:
Taking the first resource management units meeting the convergence condition as second resource management units, calculating the service affinity between any two second resource management units, and carrying out network resource convergence on the two second resource management units with the highest service affinity to obtain a third resource management unit;
the third resource management unit obtained by the previous network resource aggregation replaces the two first resource management units for network aggregation, and the next network resource aggregation is iterated until the number of the second resource management units is less than two or the total number of the first resource management units and the third resource management units is less than or equal to the preset number; the minimum resource management unit is used as a first resource management unit when the first network resource aggregation is carried out;
the first resource management unit and the third resource management unit obtained after the iteration is completed are corresponding convergence resource management units.
3. The method for deploying distributed BGP services according to claim 2, wherein the calculating the traffic affinity between any two second resource management units specifically comprises:
calculating the business affinity between the network resources of the same type in the two second resource management units;
And taking the weighted summation of the service affinities between all types of network resources in the two second resource management units as the service affinities of the corresponding two second resource management units.
4. The method for deploying distributed BGP services according to claim 1, wherein when a new network resource is present in the network, the method further comprises:
dynamic capacity expansion is carried out on BGP service, in particular,
judging whether the number of BGP services is required to be increased according to the load condition of each BGP service;
if the number of BGP services does not need to be increased, selecting a corresponding BGP service from deployed BGP services to perform nano-tube on the newly increased network resources;
if the number of BGP services needs to be increased, the distributed BGP services are redeployed according to the business affinity.
5. The method for deploying distributed BGP services according to claim 4, wherein the determining whether to increase the number of BGP services according to the loading situation of each BGP service specifically comprises:
if the number of BGP services whose corresponding load exceeds the first preset load threshold exceeds the preset duty ratio in all BGP services and/or the load variance calculated by the loads of all BGP services exceeds the preset variance threshold, the number of BGP services is increased.
6. The method for deploying distributed BGP services according to claim 4, wherein selecting a corresponding BGP service from deployed BGP services to nanotube the newly-added network resource specifically comprises:
in the deployed first BGP service, taking the BGP service with the corresponding load lower than a second preset load threshold as a second BGP service;
and calculating the business affinity of the newly-added network resource and each second BGP service, and selecting the second BGP service with the highest business affinity to perform nano-tube on the newly-added network resource.
7. The method for deploying distributed BGP services according to claim 4, wherein the redeploying the distributed BGP services according to the service affinity specifically comprises:
for the newly added network resource, when the distributed BGP service is redeployed, directly releasing the route corresponding to the newly added network resource;
for the existing network resources in the network, a route deletion message is issued by using the distributed BGP service which is not redeployed, a new route is issued by using the distributed BGP service which is redeployed, and route update and route decision are processed in a delayed manner.
8. The method for deploying a distributed BGP service according to claim 1, wherein when a network resource pruning occurs in the network, the method further comprises:
Dynamic capacity reduction is carried out on BGP services, and in particular,
and if the load of the corresponding BGP service is lower than a third preset load threshold, the network resources under the BGP service nanotubes are submitted to other BGP services for nanotubes, and the BGP service is deleted.
9. The method for deploying a distributed BGP service according to any one of claims 1-8, wherein the method further comprises:
judging whether BGP service is abnormal or not according to the connection state and health state of the BGP service;
and deleting the abnormal BGP service and releasing the corresponding network resources.
10. The distributed BGP service deployment system is characterized by comprising an acquisition module, a BGP service strategy module and a BGP service deployment module, wherein:
the acquisition module is used for acquiring the whole network resources and the network topology;
the BGP service strategy module is used for calculating the quantity of BGP services and corresponding network resources;
the BGP service deployment module is configured to deploy the distributed BGP service according to the deployment method of the distributed BGP service according to any one of claims 1-9.
CN202210895454.4A 2022-07-26 2022-07-26 Deployment method and system of distributed BGP service Active CN115102831B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210895454.4A CN115102831B (en) 2022-07-26 2022-07-26 Deployment method and system of distributed BGP service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210895454.4A CN115102831B (en) 2022-07-26 2022-07-26 Deployment method and system of distributed BGP service

Publications (2)

Publication Number Publication Date
CN115102831A CN115102831A (en) 2022-09-23
CN115102831B true CN115102831B (en) 2023-07-04

Family

ID=83300823

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210895454.4A Active CN115102831B (en) 2022-07-26 2022-07-26 Deployment method and system of distributed BGP service

Country Status (1)

Country Link
CN (1) CN115102831B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117714453B (en) * 2024-02-05 2024-04-26 济南千寻信息科技有限公司 Intelligent device management method and system based on Internet of things card

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB201421184D0 (en) * 2014-11-28 2015-01-14 Aria Networks Ltd Optimizing the topology of a network with variable traffic demands
CN108718244A (en) * 2017-12-20 2018-10-30 北京时代民芯科技有限公司 A kind of frame of reference and method for multi-service fusion
CN113381879A (en) * 2021-05-17 2021-09-10 浪潮思科网络科技有限公司 SDN-based network deployment method and device
CN113993214A (en) * 2021-09-29 2022-01-28 西安电子科技大学 Task-driven spatial information network resource management system and method

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101926153A (en) * 2008-01-23 2010-12-22 艾利森电话股份有限公司 Be used for Internet resources are carried out the method and apparatus that handle in the pond

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB201421184D0 (en) * 2014-11-28 2015-01-14 Aria Networks Ltd Optimizing the topology of a network with variable traffic demands
CN108718244A (en) * 2017-12-20 2018-10-30 北京时代民芯科技有限公司 A kind of frame of reference and method for multi-service fusion
CN113381879A (en) * 2021-05-17 2021-09-10 浪潮思科网络科技有限公司 SDN-based network deployment method and device
CN113993214A (en) * 2021-09-29 2022-01-28 西安电子科技大学 Task-driven spatial information network resource management system and method

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
云网一体使能网络即服务;朱海东;;中兴通讯技术(第02期);全文 *
基于云计算技术的一体化网络资源管理方法;季青;杨扬;孟坤;王强;张诗雅;;兵工自动化(第01期);全文 *

Also Published As

Publication number Publication date
CN115102831A (en) 2022-09-23

Similar Documents

Publication Publication Date Title
Orda et al. QoS routing: the precomputation perspective
Rath et al. Optimal controller placement in Software Defined Networks (SDN) using a non-zero-sum game
CN105103492B (en) Control network topology
CN108540204B (en) Satellite network topology generation method using fast convergence ant colony algorithm
CN114285758B (en) Communication network optimization simulation system, method and device based on OPNET
CN100488145C (en) Distributed type clustering method in use for constructing cluster type peer-to-peer network
CN106713468B (en) A kind of distributed type assemblies service system and its method for node synergy
CN108718246B (en) Resource scheduling method and system oriented to network function virtualization
CN115102831B (en) Deployment method and system of distributed BGP service
WO2017101230A1 (en) Routing selection method for data centre network and network manager
CN112600609B (en) Network capacity estimation method of satellite network system
CN109561033A (en) The method and device of multicast replication in Overlay network
CN105553855B (en) Method and system for dynamically adjusting topological structure of underlying network spanning tree
Perepelkin et al. Algorithm and software of virtual slices formation in software defined networks
Misra et al. A low-overhead fault-tolerant routing algorithm for mobile ad hoc networks: A scheme and its simulation analysis
CN106506368A (en) A kind of data communication implementation method based on internet
Li et al. Design of a service caching and task offloading mechanism in smart grid edge network
CN109286563B (en) Data transmission control method and device
CN110290069A (en) A kind of reliable multicast method for routing under SDN scene
CN104994019B (en) A kind of horizontal direction interface system for SDN controllers
Chekired et al. A hybrid SDN path computation for scaling data centers networks
Parzyjegla et al. Reconfiguring publish/subscribe overlay topologies
CN106101280A (en) A kind of network information synchronization update method between data center
Petrov et al. Minimization of multicast traffic and ensuring its fault tolerance in software-defined networks
Ju et al. On building a low latency network for future internet services

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20230329

Address after: 430000 No. 6, High-tech Fourth Road, Donghu High-tech Development Zone, Wuhan City, Hubei Province

Applicant after: FIBERHOME TELECOMMUNICATION TECHNOLOGIES Co.,Ltd.

Address before: No.4, Guanshan 2nd Road, Donghu Development Zone, Wuhan City, Hubei Province 430205

Applicant before: WUHAN FIBERHOME TECHNICAL SERVICES Co.,Ltd.

Applicant before: FIBERHOME TELECOMMUNICATION TECHNOLOGIES Co.,Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant