CN103841022A - Method and device for building tunnel - Google Patents
Method and device for building tunnel Download PDFInfo
- Publication number
- CN103841022A CN103841022A CN201410090021.7A CN201410090021A CN103841022A CN 103841022 A CN103841022 A CN 103841022A CN 201410090021 A CN201410090021 A CN 201410090021A CN 103841022 A CN103841022 A CN 103841022A
- Authority
- CN
- China
- Prior art keywords
- node
- tunnel
- mark
- address
- path
- 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.)
- Granted
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Provided are a method and device for building a tunnel. The method and device is beneficial to avoiding label distribution of the tunnel through an expanded PCEP. The method comprises the steps that a controller generates an identifier of the tunnel, and the identifier of the tunnel is the IP address of an exit joint; all the joints on the path of the tunnel and the connecting relation of all the joints are acquired, all the joints comprise the exit joint and first joints, the first joints are all the joints except the exit joint on the path, and the number of the first joints is m; the identifier of the tunnel is sent to the exit joint; first routes are distributed to all the joints in the first joints, the destination address of the first route distributed to the joint Ni in the first joints is the identifier of the tunnel, the next hop of the first route distributed to the joint Ni is the address of the joint Ni+1, the joint Ni+1 is the next joint of the joint Ni on the path, and i is an integer which is larger than or equal to 1 and smaller than or equal to m.
Description
Technical field
The embodiment of the present invention relates to the communication technology, relates in particular to a kind of for setting up method, controller, Ingress node and the Egress node in tunnel.
Background technology
Multiprotocol label switching (English full name is Multi-Protocol Label Switching, and english abbreviation is MPLS) network is a kind of system for rapid data packet switch and route.MPLS provides the abilities such as route, forwarding and exchange for network traffic data.In MPLS network, transfer of data occurs on label switched path (English full name is Label Switch Path, and english abbreviation is LSP).
In order to ensure the reliability of network and to carry out flow control, MPLS network can disposing flux engineering (English full name is Traffic Engineering, and english abbreviation is TE) tunnel.In the network of existing disposing flux engineering tunnel, (English full name is Path Computation Element to path-calculating element, english abbreviation is PCE) and multiple path calculating client (English full name is Path Computation Client, english abbreviation is PCC) all need support expansion after path computation element protocol (Path Computing Element Protocol, PCEP).Described PCC is for being synchronized to PCE by LSP data; LSP data comprise the label relevant to described PCC.Described PCE utilizes described LSP data and the path for traffic engineering tunnel calculating, is described path allocation label.The label of distribution is handed down to described PCC by described PCE, so that described PCC sets up LSP according to the label receiving.
To sum up, described PCE and described PCC need to support the PCEP after expansion, just can complete the foundation in tunnel, in other words, described PCE need to support the PCEP after expansion, could issue for distribution and label that label is carried out in path, the PCEP after described PCC need to support to expand, could carry out according to the label receiving the foundation of LSP, the difficulty of carrying out above-mentioned deployment in existing network is larger.
Summary of the invention
In view of this, it is a kind of for setting up the method in tunnel that the embodiment of the present invention provides, and helps avoid the PCEP adopting after expansion and complete the label distribution in tunnel.
The embodiment of the present invention also provides a kind of controller, Egress node and Ingress node.
The technical scheme that the embodiment of the present invention provides is as follows.
First aspect, provides a kind of for setting up the method in tunnel, comprising:
Controller generates the mark in tunnel, described tunnel is the tunnel definite according to business, described tunnel comprises Ingress node and Egress node, and the mark in described tunnel is the Internet protocol of described Egress node (English full name is Internet Protocol, and english abbreviation is IP) address;
Described controller obtains all nodes and the described all internodal annexations on the path in described tunnel, described all nodes comprise described Egress node and first node, described first node is all nodes except described Egress node on described path, and the quantity of all nodes that described first node comprises is m;
Described controller sends the mark in described tunnel to described Egress node;
Described controller is according to all internodal annexation on all nodes and described path on described path, for the each node in described first node distribute the first via by, wherein, be node N in described first node
idistribute the first via by destination address be the mark in described tunnel, be described node N
idistribute the first via by down hop be node N
i+1address, described node N
i+1described node N
inext-hop node on described path, described i is more than or equal to 1 and be less than or equal to the integer of m.
In the possible implementation of the first of above-mentioned first aspect, also comprise:
Described controller generates secondary route, and the route prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel;
Described controller sends described secondary route to described Ingress node.
In conjunction with the possible implementation of the first of first aspect or first aspect, the possible implementation of the second of first aspect is also provided, described controller is software defined network SDN controller, described Ingress node and described Egress node are all Provider Edge PE equipment, described business is the business of Virtual Private Network (English full name is Virtual Private Network, and english abbreviation is VPN).
Second aspect, provides a kind of for setting up the method in tunnel, comprising:
The Egress node in the path in tunnel receives the mark in the tunnel of self-controller, and described tunnel is the tunnel definite according to business, and the mark in described tunnel is the IP address of described Egress node;
The IP address of the interface of described Egress node using the mark in described tunnel as described Egress node;
Described Egress node is the node N in first node
mdistribute outlet label, described first node is all nodes except described Egress node on the path in described tunnel, and the quantity of all nodes that described first node comprises is m, described node N
mthe upper hop node of described Egress node on described path;
Described Egress node generating labels mapping relations, the mark that described label mapping relation is described tunnel and described node N
mthe mapping relations of outlet label;
Described Egress node is to described node N
msend described label mapping relation.
In the possible implementation of the first of above-mentioned second aspect, also comprise:
Described Egress node does not enable Interior Gateway Protocol (English full name is Internal Gateway Protocol, and english abbreviation is IGP) on described interface.
The third aspect, provides a kind of for setting up the method in tunnel, comprising:
The first via that the Ingress node in the path in tunnel receives self-controller by, described tunnel is the tunnel definite according to business, the described first via by destination address be the mark in tunnel, the mark in described tunnel is the IP address of the Egress node in described tunnel, the described first via by down hop be the address of the next-hop node of described Ingress node on described path;
Described Ingress node according to the described first via by, receive the label mapping relation that the next-hop node of described Ingress node on described path sends, the mapping relations of the mark that described label mapping relation is described tunnel and the outlet label of described Ingress node;
Described Ingress node generates tunnel list item, and described tunnel list item comprises the mapping relations of the mark in described tunnel and the outlet label of described Ingress node.
In the possible implementation of the first of the above-mentioned third aspect, after described generation tunnel list item, described method also comprises:
Described Ingress node receives the secondary route from described controller, and the route prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel;
Described Ingress node is according to described tunnel list item and described secondary route, calculated address mapping item, the mapping relations of the network segment corresponding to the outlet label that described address mapping table item is described Ingress node and described business;
Described Ingress node is in the time of the destination address of the message receiving and network segment coupling corresponding to described business, according to message described in the outlet label forwarding of Ingress node described in described address mapping table item.
Fourth aspect, provides a kind of controller, comprising:
Mark generation unit, for generating the mark in tunnel, described tunnel is the tunnel definite according to business, and described tunnel comprises Ingress node and Egress node, and the mark in described tunnel is the IP address of described Egress node;
Node acquiring unit, for obtaining all nodes and the described all internodal annexations on the path in described tunnel, described all nodes comprise described Egress node and first node, described first node is all nodes except described Egress node on described path, and the quantity of all nodes that described first node comprises is m;
Transmitting element, for the mark that sends the described tunnel that described mark generation unit generates to described Egress node;
The first via is by allocation units, for all nodes on the described path obtaining according to described node acquiring unit and all internodal annexation on described path, for the each node in described first node distribute the first via by, wherein, be node N in described first node
idistribute the first via by destination address be the mark in described tunnel, be described node N
idistribute the first via by down hop be node N
i+1address, described node N
i+1described node N
inext-hop node on described path, described i is more than or equal to 1 and be less than or equal to the integer of m.
In the possible implementation of the first of above-mentioned fourth aspect, also comprise: secondary route allocation units;
Described secondary route allocation units are used for generating secondary route, and the route prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel;
The extremely described Ingress node of described secondary route that described transmitting element generates specifically for sending described secondary route allocation units.
The 5th aspect, provides a kind of Egress node, comprising:
Receiving element, for receiving the mark in tunnel of self-controller, described tunnel is the tunnel definite according to business, the mark in described tunnel is the IP address of described Egress node;
Interface configuration unit, for the IP address using the mark in the described tunnel of described receiving element reception as the interface of described Egress node;
Label distribution unit, is used to the node N in first node
mdistribute outlet label, described first node is all nodes except described Egress node on the path in described tunnel, and the quantity of all nodes that described first node comprises is m, described node N
mthe upper hop node of described Egress node on described path;
Mapping generation unit is described node N for mark and the described label distribution unit in the described tunnel that receives according to described receiving element
mthe outlet label distributing, generating labels mapping relations, the mark that described label mapping relation is described tunnel and described node N
mthe mapping relations of outlet label;
Transmitting element, for to described node N
msend the described label mapping relation that described mapping generation unit generates.
In the possible implementation of the first aspect the above-mentioned the 5th, also comprise:
Protocol enabled unit, for not enabling IGP on described interface.
The 6th aspect, provides a kind of Ingress node, comprising:
The first receiving element, for the first via that receives self-controller by, the described first via by destination address be the mark in tunnel, described tunnel is the tunnel definite according to business, the mark in described tunnel is the IP address of the Egress node in described tunnel, the described first via by down hop be the address of the next-hop node of described Ingress node on the path in described tunnel;
The second receiving element, for according to described first receiving element receive the described first via by, receive the label mapping relation that the next-hop node of described Ingress node on described path sends, the mapping relations of the mark that described label mapping relation is described tunnel and the outlet label of described Ingress node;
Tunnel list item generation unit, for the described label mapping relation receiving according to described the second receiving element, generates tunnel list item, and described tunnel list item comprises the mapping relations of the mark in described tunnel and the outlet label of described Ingress node.
In the possible implementation of the first aspect the above-mentioned the 6th, also comprise:
The 3rd receiving element, for receiving the secondary route from described controller, the route prefix of described secondary route is the network segment corresponding to described business, the down hop of described secondary route is the mark in described tunnel;
Address mapping generation unit, be used for according to the described secondary route of the described tunnel list item of described tunnel list item generation unit generation and described the 3rd receiving element reception, calculated address mapping item, the mapping relations of the network segment corresponding to the outlet label that described address mapping table item is described Ingress node and described business;
Packet sending unit, during for the destination address at the message receiving and the network segment corresponding to described business coupling, message described in the outlet label forwarding of Ingress node described in the described address mapping table item generating according to described address mapping generation unit.
By such scheme, the each node on the path that controller is tunnel except Egress node distribute the first via relevant with the mark in tunnel by, thereby the each node except Egress node on the path in tunnel can be according to the described first via by carrying out label distribution; Controller issues identifying to Egress node of tunnel, and the mark in tunnel is the IP address of Egress node, thereby the Egress node in triggering tunnel carries out the label distribution in described tunnel.Technical scheme provided by the invention, the node on controller and tunnel is without the label distribution of PCEP being carried out to protocol extension can complete tunnel.
Brief description of the drawings
In order to be illustrated more clearly in the technical scheme in the embodiment of the present invention, below the accompanying drawing of required use during embodiment is described is briefly described, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skill in the art, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
The schematic diagram of the scene that Fig. 1 is the deployment tunnel that provides in the embodiment of the present invention.
Fig. 2 in the embodiment of the present invention, provide for setting up the flow chart of method in tunnel.
Fig. 3 in the embodiment of the present invention, provide for setting up the flow chart of method in tunnel.
Fig. 4 in the embodiment of the present invention, provide for setting up the flow chart of method in tunnel.
Fig. 5 in the embodiment of the present invention, provide for setting up the flow chart of method in tunnel.
The structural representation that Fig. 6 is the controller that provides in the embodiment of the present invention.
The structural representation that Fig. 7 is the Egress node that provides in the embodiment of the present invention.
The structural representation that Fig. 8 is the Ingress node that provides in the embodiment of the present invention.
The structural representation that Fig. 9 is the intermediate node that provides in the embodiment of the present invention.
The structural representation of the network equipment that Figure 10 provides for the embodiment of the present invention.
The structural representation of the network equipment that Figure 11 provides for the embodiment of the present invention.
The structural representation of the network equipment that Figure 12 provides for the embodiment of the present invention.
Embodiment
For making object, technical scheme and the advantage of the embodiment of the present invention clearer, below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly described.Obviously, described embodiment is the present invention's part embodiment, instead of whole embodiment.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
What in embodiments of the invention, provide is that a class business is set up tunnel corresponding to described business for setting up that the method in tunnel can be used to, for example: the business of VPN, also can be other business.In following embodiment of the present invention, only, taking the business of VPN as example, the method and apparatus of setting up tunnel is described.
In scene as shown in Figure 1, (English full name is Customer Edge to belong to two customer edges of same VPN, english abbreviation is CE) equipment is respectively CE1 and CE2, CE1 and CE2 are connected respectively LSR in MPLS network, and (English full name is label switching router, english abbreviation is LSR), for example: CE1 connects LSR0, CE2 connects LSR2, described LSR0 and described LSR2 are Provider Edge (English full name is Provider Edge, and english abbreviation is PE) equipment.In MPLS network, also comprise LSR1, described LSR1 can be operator's (English full name is Provider, and english abbreviation the is P) equipment in MPLS network.Between CE1 and CE2, need to set up the tunnel corresponding with the business of described VPN, described tunnel and path thereof can be planned according to the required bandwidth of the business of described VPN, i.e. described path process described LSR0, described LSR1 and described LSR2.Wherein, described LSR0 is as the entrance in described tunnel, and described LSR1 is positioned between the described LSR1 and described LSR2 on described path, and described LSR2 is as the outlet in described tunnel.
The method that the embodiment corresponding with Fig. 2 provides can be applicable to the scene shown in Fig. 1.As shown in Figure 2, the embodiment of the present invention provide for setting up the method in tunnel, comprising:
S20, controller generates the mark in tunnel, and described tunnel is the tunnel definite according to business, and described tunnel comprises Ingress node and Egress node, and the mark in described tunnel is the IP address of described Egress node.
Alternatively, described controller can be according to tunnel described in described plan of operation, or mutual by with the network equipment, obtains tunnel corresponding to described business from the described network equipment.Wherein, described business can be the business of described VPN, and described tunnel can be traffic engineering tunnel.
Alternatively, controller can according to the required bandwidth of the business of described VPN and service quality, (English full name be Quality Of Service, english abbreviation is QoS) tunnel described in parametric programming in parameter except bandwidth, for example: the parameter in qos parameter except bandwidth is at least one parameter in time delay and packet loss.
For instance, the IP address of described Egress node can be the IP address of a physical interface of described Egress node, can also be the loop-back address of described Egress node.
S21, described controller obtains all nodes on the path in described tunnel and all internodal annexation on described path, described all nodes comprise described Egress node and first node, described first node is all nodes except described Egress node on described path, and the quantity of all nodes that described first node comprises is m.
Alternatively, controller can be by with the network equipment mutual, obtain all internodal annexation on all nodes and the described path on described path, or controller is described tunnel calculating path, to obtain all internodal annexation on all nodes and the described path on described path.Wherein, all internodal annexation on described path can be with two annexations that internodal link represents on described path.
Alternatively, controller can adopt restricted shortest path footpath (English full name is Constrained Shortest Path First, and english abbreviation is CSPF) algorithm or linear programming algorithm to calculate described path.For example: controller in the time being described tunnel calculating path, all nodes that can comprise according to path described in bandwidth selection, all nodes that also can select described path to comprise according to the parameter except bandwidth in bandwidth and QoS.
For instance, node N in described first node
inext-hop node on described path is the node N in described first node
i+1, described node N
ion described path, there is and only has a next-hop node.Wherein, described i is more than or equal to 1 and be less than or equal to the integer of m, and the Ingress node in described tunnel is the node N in described first node
1, the upper hop node of the Egress node in described tunnel on described path is the node N in described first node
m, described Egress node is node N
m+1.
As shown in Figure 1, all internodal annexation on all nodes and described path on the described path that controller obtains is LSR0->LSR1->LSR2, and the quantity of all nodes that described first node comprises is 2.Described LSR0 is as the entrance in described tunnel, and described LSR1 is the down hop of described LSR0 on described path, and described LSR2 is as the outlet in described tunnel.
S22, described controller sends the mark in described tunnel to described Egress node.
Alternatively, by Simple Network Management Protocol, (English full name is Simple network management protocol to described controller, english abbreviation is SNMP) or network configuration protocol (English name is netconf), the mark in described tunnel sent to described Egress node.
S23, described controller is according to all internodal annexation on all nodes and described path on described path, for the each node in described first node distribute the first via by, wherein, be node N in described first node
idistribute the first via by destination address be the mark in described tunnel, be described node N
idistribute the first via by down hop be node N
i+1address, described node N
i+1described node N
inext-hop node on described path, described i is more than or equal to 1 and be less than or equal to the integer of m.
For instance, described node N
i+1address can be described node N
i+1the IP address of interface, can also be described node N
i+1loop-back address.
For instance, controller can adopt Border Gateway Protocol, and (English full name is Border Gateway Protocol, english abbreviation is BGP) issue the first via by, also can adopt other agreement issue the first via by, such as open flows (English name is OpenFlow) agreement.
As shown in Figure 1, described LSR0 is the node N in first node
1, described LSR1 is the node N in first node
2, described LSR2 is Egress node N
3.Described controller be the described LSR0 first via of distributing by destination address be the mark in described tunnel, described controller be the described LSR0 first via of distributing by down hop be the address of described LSR1.Described controller be the described LSR1 first via of distributing by destination address be the mark in described tunnel, described controller be the described LSR1 first via of distributing by down hop be the address of described LSR2.
Alternatively, after S23, describedly also can comprise in order to the method for setting up tunnel: described controller generates secondary route, and the route prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel; Described controller sends described secondary route to described Ingress node.
For instance, described controller can obtain the network segment corresponding to described business from the Egress node in described tunnel, also can obtain the network segment corresponding to described business by static configuration.Wherein, the network segment corresponding to described business can be the network segment of described VPN, can also be the IP address of the target device in described VPN, and described target device is the equipment that receives the message corresponding with described business.
S20 in this embodiment and the execution sequence of S21 are not unique, for example: S20 can carry out after S21, also can carry out with S21 simultaneously.
For instance, described controller can be software defined network (English full name is Software Defined Network, and english abbreviation is SDN) controller.
Alternatively, if controller has obtained two paths, one paths is corresponding to a tunnel, all nodes that described two paths comprise form tree, the Egress node that described two paths comprise is the root node of described tree, the mark in two tunnels that described controller generates can be identical IP address, to reduce the use amount of mark in tunnel.For example: the path in the first tunnel is the first path, the path in the second tunnel is the second path, controller has obtained all nodes on all nodes and the second path on the first path, all nodes on all nodes on the first path and the second path form tree, the Egress node on the first path is identical with the Egress node on the second path, described Egress node is the root node of tree, controller can be the first tunnel identical with the second tunnel distributing mark, distribute the mark of identical IP address as tunnel.
Alternatively, if controller has obtained two tunnels, a tunnel is the tunnel corresponding to a class business, and the Ingress node in two tunnels is identical, and the Egress node in two tunnels is identical.For example: the first tunnel is corresponding to the first business, and the second tunnel is corresponding to the second business, and the Ingress node in the first tunnel is identical with the Ingress node in the second tunnel, and the Egress node in the first tunnel is identical with the Egress node in the second tunnel.Controller is in the time of path corresponding to planning tunnel, determine that the qos parameter of a paths is except meeting the demand of the first business, also can meet the demand of the second business, using described path as the common paths using in the first tunnel and the second tunnel, be that the first tunnel and the second tunnel generate identical mark, to reduce the use amount of mark in tunnel.
In the method that this embodiment provides, controller carries out the distribution of label and issuing of label without the PCEP that adopts expansion, controller generates Tunnel Identifier and is the each node distribution route in first node, by issuing described Tunnel Identifier and route, can contribute to the node on described path to carry out the distribution of label, when having alleviated the burden of controller, simplify the control function of controller.Therefore, controller, without the label distribution of PCEP being carried out to protocol extension can complete tunnel, contributes to the foundation in tunnel.
The method that the embodiment corresponding with Fig. 3 provides can be applicable to the scene shown in Fig. 1.As shown in Figure 3, the embodiment of the present invention provide for setting up the method in tunnel, comprising:
S30, the Egress node in the path in tunnel receives the mark in the tunnel of self-controller, and described tunnel is the tunnel definite according to business, and the mark in described tunnel is the IP address of described Egress node.
S31, the IP address of the interface of described Egress node using the mark in described tunnel as described Egress node.
The mark in described tunnel is the IP address of described Egress node, if the IP address of described Egress node is the IP address of a physical interface of described Egress node, described Egress node is that described physical interface configures described IP address, if the IP address of described Egress node is loop-back address, described Egress node generates a loopback interface, and described loop-back address is configured to the IP address of described loopback interface.
For instance, described Egress node can be disposed at the mark in described tunnel described Egress node connected node N
minterface on, described node N
mthe upper hop node of described Egress node on described path.For example: described Egress node can obtain node N from described controller
mthe interface of down hop described Egress node pointed, and the mark in described tunnel is disposed to the interface of the down hop of described node Nm described Egress node pointed.Certainly, described Egress node also can be disposed at the mark in described tunnel on other interface of described Egress node.
For instance, the IP address of described Egress node using the mark in tunnel as described interface, triggers the operation of label distribution.
As shown in Figure 1, described LSR1 and described LSR2 are on described path, and described LSR1 is the upper hop of described LSR2 on described path.I
0be an interface of LSR2, LSR2 is using the mark in the described tunnel receiving as I
0iP address.
S32, described Egress node is node N
mdistribute outlet label, described node N
mthe upper hop node of described Egress node on described path, described node N
mbe the node in first node, described first node is all nodes except described Egress node on described path, and the quantity of all nodes that described first node comprises is m.
Described Egress node can adopt existing tag distribution protocol, and (English full name is Label Distribution Protocal, english abbreviation is LDP), for from the upper hop node distributing labels on described path, without the PECP adopting after expansion, contribute to reduce the difficulty of disposing.
S33, described Egress node generating labels mapping relations, the mark that described label mapping relation is described tunnel and node N
mthe mapping relations of outlet label.
S34, described Egress node is to described node N
msend described label mapping relation.
Alternatively, described Egress node sends described label mapping relation to the upstream node of MPLS network middle outlet node, determines whether to receive described label mapping relation by described upstream node.
As shown in Figure 1, LSR2 passes through I
0send the upstream node of described label mapping relation to MPLS network middle outlet node, the upstream node of described MPLS network middle outlet node comprises LSR1.
Alternatively, after S31, describedly also comprise for the method for setting up tunnel: described Egress node does not enable IGP on described interface.Wherein, described interface can be the physical interface of described Egress node, can also be the loopback interface that described Egress node generates.
For instance, the instruction of carrying in the instruction that Egress node can issue according to controller or message does not enable IGP on described interface, contributes to generate a LSP consistent with the path of planning.Because do not enable IGP, make the neighbor node of described Egress node to learn the IGP route that is designated destination address with tunnel by IGP, and described IGP route is in order to indicate the neighbor node of described Egress node to receive the label of described Egress node distribution, like this, the neighbor node of described Egress node, in the situation that cannot learning IGP route, can not receive the label of described Egress node distribution.
As shown in Figure 1, described LSR1 belongs to the neighbor device of described LSR2.Described LSR2 is not at I
0on enable IGP, I
0iP address be the mark in described tunnel, contribute to the neighbor device (comprising LSR1) of described LSR2 to get the route that is designated destination address with tunnel by IGP, thus cannot be according to LSR2 described in IGP route acquisition from I
0the label sending, but the first via that described LSR1 can distribute according to controller by, obtain the label of described LSR2 distribution.
In the method for this embodiment, Egress node, without the PCEP adopting after expansion, adopts existing LDP just can realize the distribution of label, contributes to, in the situation that not upgrading conventional network equipment, to complete the distribution of label.
The method that the embodiment corresponding with Fig. 4 provides can be applicable to the scene shown in Fig. 1.As shown in Figure 4, the embodiment of the present invention provide for setting up the method in tunnel, comprising:
S40, the first via that the Ingress node in the path in tunnel receives self-controller by, described tunnel is the tunnel definite according to business, the described first via by destination address be the mark in tunnel, the mark in described tunnel is the IP address of the Egress node in described tunnel, the described first via by down hop be the address of the next-hop node of described Ingress node on described path.
As shown in Figure 1, described LSR0 is as the entrance in described tunnel, and described LSR2 is as the outlet in described tunnel, and described LSR1 is positioned between described LSR0 and described LSR2 on described path.The first via that described LSR0 receives by down hop be the address of described LSR1, the address of described LSR1 can be the IP address of the interface on described LSR1 or the loop-back address of described LSR1.
S41, described Ingress node according to the described first via by, receive the label mapping relation that the next-hop node of described Ingress node on described path sends, the mapping relations of the mark that described label mapping relation is described tunnel and the outlet label of described Ingress node.
Described Ingress node is the N in first node
1, the next-hop node of described Ingress node on described path is the node N in described first node
2.Wherein, described first node is all nodes except Egress node on described path, and the quantity of all nodes that described first node comprises is m.
For instance, when described Ingress node receives label mapping and is related to, first determine the sender of label mapping relation be the first via by down hop, then according to the described first via by destination address and described label mapping relation described in the mark in tunnel, determine the outlet label using the outlet label in described label mapping relation as described Ingress node.
As shown in Figure 1, if the first via that described LSR0 receives by the IP address of the down hop interface that is described LSR1, LSR0 determines that according to the IP address of the interface of described LSR1 the sender of this label mapping relation is LSR1.If the first via that described LSR0 receives by the down hop loop-back address that is described LSR1, first described LSR0 need to carry out an address iteration, obtain the IP address of the interface of described LSR1, then determine that according to the IP address of the interface of described LSR1 the sender of this label mapping relation is LSR1.
For instance, the method that described LSR0 carries out address iteration comprises: described LSR0 learns or static configuration by IGP, obtains the route that arrives neighbor node (comprising LSR1), the neighbor node that described neighbor node is described LSR0; The destination address of the route of described neighbor node is the loop-back address of described neighbor node, and the down hop of the route of described neighbor node is the IP address of the interface of described neighbor node.Described LSR0 according to the described first via by down hop and the destination address of the route of described neighbor node, from the IP address of the interface of LSR1 described in the route acquisition of described neighbor node.
S42, described Ingress node generates tunnel list item, and described tunnel list item comprises the mapping relations of the mark in described tunnel and the outlet label of described Ingress node.
Alternatively, after S42, describedly also comprise for the method for setting up tunnel: described Ingress node receives the secondary route from described controller, and the prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel; Described Ingress node, in the time of the destination address of message receiving and the prefix matching of described secondary route, obtains the mark in described tunnel from described secondary route; Described Ingress node is inquired about described tunnel list item according to the mark in described tunnel, obtains the outlet label of described Ingress node, to utilize message described in the outlet label forwarding of described Ingress node.
Alternatively, after S42, describedly also comprise for the method for setting up tunnel: described Ingress node receives the secondary route from described controller, and the prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel; Described Ingress node is according to described tunnel list item and described secondary route, calculated address mapping item, the mapping relations of the network segment corresponding to the outlet label that described address mapping table item is described Ingress node and described business; Described Ingress node is in the time of the destination address of the message receiving and network segment coupling corresponding to described business, according to message described in the outlet label forwarding of Ingress node described in described address mapping table item.
After described Ingress node calculated address mapping item, without the outlet label that carries out twice search operation and obtain Ingress node, without the mark of searching described tunnel according to the destination address of described message, search again the outlet label of described Ingress node according to the mark in described tunnel, can obtain the outlet label of Ingress node by once searching the operation of address mapping table item, alleviate work load, improved search efficiency.
Ingress node in this embodiment completes the generation of tunnel table, to represent the end of label distribution flow process in tunnel.Described Ingress node, without the PCEP adopting after expansion, contributes to reduce the difficulty of disposing.
The method that the embodiment corresponding with Fig. 5 provides can be applicable to the scene shown in Fig. 1.As shown in Figure 5, the embodiment of the present invention provide for setting up the method in tunnel, comprising:
S50, the node N on the path in tunnel in first node
jreceive controller distribute the first via by, described tunnel is the tunnel definite for business, described first node is all nodes except the Egress node in described tunnel on described path, the quantity of all nodes that described first node comprises is m, described node N
jit is the node except the Ingress node in described tunnel in described first node, described j is greater than 1 and be less than or equal to the integer of m, the described first via by destination address be the mark in described tunnel, the IP address that is designated Egress node in described tunnel, the described first via by down hop be node N
j+1address, described node N
j+1for described node N
jnext-hop node on described path.
As shown in Figure 1, the quantity of all nodes that described first node comprises is 2, and described LSR0 is node N
1, described LSR1 is node N
2, described LSR2 is node N
3, described LSR2 is the down hop of described LSR1 on described path.Described LSR1 receive the first via by destination address be the mark in described tunnel, the first via that described LSR1 receives by down hop be the address of described LSR2.
S51, described node N
jaccording to the described first via by, receive from described node N
j+1the first label mapping relation, described first label mapping close be mark and the node N in tunnel
jthe mapping relations of outlet label.
As shown in Figure 1, described LSR1 receives the first label mapping relation from described LSR2 node, the concrete method that receives the first label mapping relation, in the embodiment corresponding with Fig. 4, LSR0 receives from the method for the label mapping relation of LSR1 node identically, does not repeat them here.
S52, described node N
jfor the node N in described first node
j-1distribute outlet label, generate the second label mapping relation, described node N
j-1for described node N
jupper hop node on described path, it is mark and the described node N in described tunnel that described the second label mapping closes
j-1the mapping relations of outlet label.
For instance, described node N
j-1can be the Ingress node in described tunnel, can also be on described path, to be positioned at described Ingress node and described node N
jbetween node.
For instance, described node N
jcan come for described node N by triggering LDP
j-1distribute outlet label.
As shown in Figure 1, LSR1 is that LSR0 distributes outlet label, according to the outlet label of the mark in tunnel and LSR0, generates the second label mapping relation.
S53, described node N
jaccording to the first label mapping relation and the second label mapping relation, generate the first label forwarding list item, described the first label forwarding list item comprises described node N
j-1outlet label and described node N
joutlet label.
For instance, as the node N of intermediate node
jreceive the message of described business, can, according to label forwarding list item, from described message, eject the node N in first node
j-1outlet label, by described node N
joutlet label be pressed into described message and send, described message is forwarded along the LSP consistent with described path.
In this embodiment, as the node N of intermediate node
jwithout the PCEP adopting after expansion, the first via of distributing according to controller by, adopt existing LDP can carry out label distribution, contribute to set up the LSP corresponding with tunnel, contribute to reduce the difficulty of deployment.
As shown in Figure 6, the controller providing in the embodiment of the present invention, comprising: mark generation unit 101, node acquiring unit 102, transmitting element 103 and the first via are by allocation units 103.
For instance, described node acquiring unit 102 can adopt CSPF algorithm or linear programming algorithm to calculate the path in described tunnel, and then obtains all nodes and all internodal annexations on described path.
Transmitting element 103 for the mark in the described tunnel that sends described mark generation unit 101 and generate to described Egress node.
The first via by allocation units 104 for all internodal annexation on all nodes and described path on the described path obtaining according to described node acquiring unit 102, for the each node in described first node distribute the first via by, wherein, be node N in described first node
idistribute the first via by destination address be the mark in described tunnel, be described node N
idistribute the first via by down hop be node N
i+1address, described node N
i+1described node N
inext-hop node on described path, described i is more than or equal to 1 and be less than or equal to the integer of m.
The controller that this embodiment provides can be realized all functions of the embodiment middle controller corresponding with Fig. 2.
Alternatively, described controller can further comprise: secondary route allocation units.
Described secondary route allocation units are used for generating secondary route, and the route prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel; The extremely described Ingress node of described secondary route that described transmitting element generates specifically for sending described secondary route allocation units.
The controller that this embodiment provides carries out the distribution of label and issuing of label without the PCEP that adopts expansion, controller generates Tunnel Identifier and is the each node distribution route in first node, by issuing described Tunnel Identifier and route, can contribute to the node on described path to carry out the distribution of label, when having alleviated the burden of controller, simplify the control function of controller.Therefore, controller, without the label distribution of PCEP being carried out to protocol extension can complete tunnel, contributes to the foundation in tunnel.
As shown in Figure 7, the Egress node that the embodiment of the present invention provides comprises: receiving element 201, interface configuration unit 202, label distribution unit 203, mapping generation unit 204 and transmitting element 205.
Receiving element 201 is for receiving the mark in tunnel of self-controller, and described tunnel is the tunnel definite according to business, and the mark in described tunnel is the IP address of described Egress node.
Transmitting element 205 is for to described node N
msend the described label mapping relation that described mapping generation unit 204 generates.
Alternatively, described transmitting element 205 is also for sending the network segment corresponding to described business to described controller with the form of route.For instance, when business that described business is VPN, the form of described route can be the form of VPN route, the prefix by the network segment corresponding to described business as VPN route.
Alternatively, described Egress node also comprises: protocol enabled unit.Described protocol enabled unit for not enabling IGP on described interface.For instance, the instruction that described protocol enabled unit can issue according to controller or message do not enable IGP on described interface.Described interface is the interface using the mark in described tunnel as IP address.
The Egress node that this embodiment provides can be realized all functions of the embodiment middle outlet node corresponding with Fig. 3.
The Egress node that this embodiment provides, without the PCEP adopting after expansion, adopts existing LDP just can realize the distribution of label, contributes to complete the distribution of label in the situation that not upgrading conventional network equipment.
As shown in Figure 8, the Ingress node that the embodiment of the present invention provides comprises: the first receiving element 301, the second receiving element 302 and tunnel list item generation unit 303.Wherein, Ingress node belongs to the first node on the path in described tunnel.
The first receiving element 301 for the first via that receives self-controller by, the described first via by destination address be the mark in tunnel, described tunnel is the tunnel definite according to business, the mark in described tunnel is the IP address of the Egress node in described tunnel, the described first via by down hop be the address of the next-hop node of described Ingress node on the path in described tunnel.
The second receiving element 302 for the described first via that receives according to described the first receiving element 301 by, receive the label mapping relation that the next-hop node of described Ingress node on described path sends, the mapping relations of the mark that described label mapping relation is described tunnel and the outlet label of described Ingress node.
The described label mapping relation of tunnel list item generation unit 303 for receiving according to described the second receiving element 302, generates tunnel list item, and described tunnel list item comprises the mapping relations of the mark in described tunnel and the outlet label of described Ingress node.
The Ingress node that this embodiment provides can be realized all functions of Ingress node in the embodiment corresponding with Fig. 4.
Alternatively, the Ingress node that the embodiment corresponding with Fig. 8 provides also comprises: the 3rd receiving element, address mapping generation unit and packet sending unit.Described the 3rd receiving element is for receiving the secondary route from described controller, and the route prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel.Described address mapping generation unit is used for according to the described secondary route of the described tunnel list item of described tunnel list item generation unit generation and described the 3rd receiving element reception, calculated address mapping item, the mapping relations of the network segment corresponding to the outlet label that described address mapping table item is described Ingress node and described business.Described packet sending unit is for when the destination address of the message receiving and network segment coupling corresponding to described business, message described in the outlet label forwarding of Ingress node described in the described address mapping table item generating according to described address mapping generation unit.
Alternatively, the Ingress node that the embodiment corresponding with Fig. 8 provides also comprises the 4th receiving element, the second mark determining unit, label acquiring unit and the second transmitting element.Described the 4th receiving element is for receiving the secondary route from described controller, and the prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel.Described the second mark determining unit is used for, in the time of the destination address of message receiving and the prefix matching of described secondary route, obtaining the mark in described tunnel from described secondary route.Described label acquiring unit, for inquiring about described tunnel list item according to the mark in described tunnel, obtains the outlet label of described Ingress node; Described the second transmitting element is for utilizing message described in the outlet label forwarding of described Ingress node.
The Ingress node that this embodiment provides completes the generation of tunnel table, to represent the end of label distribution flow process in tunnel.Described Ingress node, without the PCEP adopting after expansion, contributes to reduce the difficulty of disposing.
As shown in Figure 9, the node N as intermediate node that the embodiment of the present invention provides
jcomprise: the first receiving element 401, the second receiving element 402, label distribution unit 403, mapping generation unit 404 and label list item generation unit 405.
The first receiving element 401 for receive controller distribute the first via by, the described first via by destination address be the mark in tunnel, described tunnel is the tunnel definite for business, the IP address that is designated Egress node in described tunnel, the described first via by down hop be node N in first node
j+1address, described first node is all nodes except the Egress node in described tunnel on described path, the quantity of all nodes that described first node comprises is m, described j is greater than 1 and be less than or equal to the integer of m, described node N
j+1for described node N
jnext-hop node on described path, described node N
jit is the node except the Ingress node in described tunnel in described first node.
The second receiving element 402 for the described first via that receives according to described the first receiving element 401 by, receive from described node N
j+1the first label mapping relation, described first label mapping close be mark and the node N in tunnel
jthe mapping relations of outlet label.
Described the second label mapping relation that label list item generation unit 405 generates for described the first label mapping relation of receiving according to described the second receiving element 402 and described mapping generation unit 404, generate the first label forwarding list item, described the first label forwarding list item comprises described node N
j-1outlet label and described node N
joutlet label.
The node N as intermediate node of this embodiment
jwithout the PCEP adopting after expansion, the first via of distributing according to controller by, adopt existing LDP can carry out label distribution, contribute to set up the LSP corresponding with tunnel, contribute to reduce the difficulty of deployment.
The node N mentioning in the above embodiment of the present invention
ifor the network equipment, Egress node is the network equipment.
The embodiment of the present invention further provides the device embodiment that realizes each step and method in said method embodiment.
Figure 10 shows a kind of embodiment of the network equipment, and in this embodiment, the described network equipment comprises transtation mission circuit 501, receiving circuit 502, processor 503, memory 504 and bus 505.The equipment of this embodiment can be applied to the network equipment such as switch or router of communication system.The equipment that generates route for tunnel to be set up of this embodiment can be the controller in the embodiment corresponding with Fig. 2 and/or Fig. 6.In memory 504, store computer-readable instruction.
Processor 503 reads described computer-readable instruction, and carries out following operation according to read described computer-readable instruction:
Obtain all nodes on the path in tunnel and all internodal annexation on described path by receiving circuit 502, described tunnel is the tunnel definite according to business, described tunnel comprises Ingress node and Egress node, all nodes on described path comprise described Egress node and first node, and described first node is all nodes except described Egress node on described path;
The mark that sends the tunnel generating by transtation mission circuit 501 to described Egress node, the mark in described tunnel is the IP address of described Egress node;
According to all internodal annexation on all nodes and described path on described path, for the each node in described first node distribute the first via by, wherein, be node N in described first node
idistribute the first via by destination address be the mark in described tunnel, be described node N
idistribute the first via by down hop be node N
i+1address, described node N
i+1described node N
inext-hop node on described path, described i is more than or equal to 1 and be less than or equal to the integer of m.
Each nextport hardware component NextPort that bus 505 can comprise this equipment is coupled.Bus 505, except comprising data/address bus, also comprises power bus and control bus.In order to clearly demonstrate, the various buses in Figure 10 are all designated as bus 505.The all functions of the controller in can realization corresponding with Fig. 2 and/or Fig. 6 embodiment of the described network equipment.
Figure 11 shows a kind of embodiment of the network equipment, and in this embodiment, the described network equipment comprises transtation mission circuit 601, receiving circuit 602, processor 603, memory 604 and bus 605.The equipment of this embodiment can be applied to the network equipment such as switch or router of communication system.The network equipment of this embodiment is the Egress node in the embodiment corresponding with Fig. 3 and/or Fig. 7.In memory 604, store computer-readable instruction.
Receive the mark in tunnel by receiving circuit 602, described tunnel is the tunnel definite according to business, and the mark in described tunnel is the Internet protocol IP address of described Egress node;
The IP address of the interface using the mark in described tunnel as described Egress node;
For the node N in first node
mdistribute outlet label, described first node is all nodes except described Egress node on the path in described tunnel, and the quantity of all nodes that described first node comprises is m, described node N
mthe upper hop node of described Egress node on described path;
Generating labels mapping relations, the mark that described label mapping relation is described tunnel and described node N
mthe mapping relations of outlet label;
By transtation mission circuit 601 to described node N
msend described label mapping relation.
Each nextport hardware component NextPort that bus 605 can comprise this equipment is coupled.Bus 605, except comprising data/address bus, also comprises power bus and control bus.In order to clearly demonstrate, the various buses in Figure 11 are all designated as bus 605.The all functions of the Egress node in can realization corresponding with Fig. 3 and/or Fig. 7 embodiment of the described network equipment.
Figure 12 shows a kind of embodiment of the network equipment, and in this embodiment, the described network equipment comprises transtation mission circuit 701, receiving circuit 702, processor 703, memory 704 and bus 705.The equipment of this embodiment can be applied to the network equipment such as switch or router of communication system.The described network equipment of this embodiment is the Ingress node in the embodiment corresponding with Fig. 4 and/or Fig. 8.In memory 704, store computer-readable instruction.
By receiving circuit 702 receive the first via by, described tunnel is the tunnel definite according to business, the described first via by destination address be the mark in tunnel, the mark in described tunnel is the IP address of the Egress node in described tunnel, the described first via by down hop be the address of the next-hop node of described Ingress node on described path;
According to the described first via by, receive label mapping relation, the mapping relations of the mark that described label mapping relation is described tunnel and the outlet label of described Ingress node;
According to the first via, by generating tunnel list item with label mapping relation, described tunnel list item comprises the mapping relations of the mark in described tunnel and the outlet label of described Ingress node.
Each nextport hardware component NextPort that bus 705 can comprise this equipment is coupled.Bus 705, except comprising data/address bus, also comprises power bus and control bus.In order to clearly demonstrate, the various buses in Figure 12 are all designated as bus 705.The all functions of the Ingress node in can realization corresponding with Fig. 4 and/or Fig. 8 embodiment of the described network equipment.
Above-mentioned general processor can be that microprocessor or this processor can be also the processors of any routine.In conjunction with the step of the disclosed method of the embodiment of the present invention, can directly be presented as that hardware processor is complete, or complete with the hardware in processor and software module combination.In the time using software to realize, can be by the code storage that realizes above-mentioned functions in computer-readable medium.Computer-readable medium comprises computer-readable storage medium.Storage medium can be any usable medium that computer can access.As example but be not limited to: computer-readable medium can be that (English full name is random access memory to random access memory, english abbreviation is RAM), (English full name is read only memory to read-only memory, english abbreviation is ROM), (English full name is electrically erasable programmable read-only memory to EEPROM (Electrically Erasable Programmable Read Only Memo), english abbreviation is EEPROM), (English full name is compact disc-read only memory to read-only optical disc, english abbreviation is CD-ROM) or other optical disc storage, magnetic disk storage medium or other magnetic storage apparatus, or can be used in carry or store the expectation with instruction or data structure form program code and can be by any other medium of computer access.Computer-readable medium can be that (English full name is compact disk to compression laser disc, english abbreviation is CD), laser dish, laser disc, digital video disc (English full name is digital video disc, and english abbreviation is DVD), floppy disk or Blu-ray Disc.
In a word, the foregoing is only the preferred embodiment of technical solution of the present invention, be not intended to limit protection scope of the present invention.All within principle of the present invention, any amendment of doing, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.
Claims (13)
1. for setting up the method in tunnel, it is characterized in that, described method comprises:
Controller generates the mark in tunnel, and described tunnel is the tunnel definite according to business, and described tunnel comprises Ingress node and Egress node, and the mark in described tunnel is the Internet protocol IP address of described Egress node;
Described controller obtains all nodes and the described all internodal annexations on the path in described tunnel, described all nodes comprise described Egress node and first node, described first node is all nodes except described Egress node on described path, and the quantity of all nodes that described first node comprises is m;
Described controller sends the mark in described tunnel to described Egress node;
Described controller is according to all internodal annexation on all nodes and described path on described path, for the each node in described first node distribute the first via by, wherein, be node N in described first node
idistribute the first via by destination address be the mark in described tunnel, be described node N
idistribute the first via by down hop be node N
i+1address, described node N
i+1described node N
inext-hop node on described path, described i is more than or equal to 1 and be less than or equal to the integer of m.
2. the method for claim 1, is characterized in that, described method also comprises:
Described controller generates secondary route, and the route prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel;
Described controller sends described secondary route to described Ingress node.
3. method as claimed in claim 1 or 2, is characterized in that, described controller is software defined network SDN controller, and described Ingress node and described Egress node are all Provider Edge PE equipment, the business that described business is virtual private network.
4. for setting up the method in tunnel, it is characterized in that, described method comprises:
The Egress node in the path in tunnel receives the mark in the tunnel of self-controller, and described tunnel is the tunnel definite according to business, and the mark in described tunnel is the Internet protocol IP address of described Egress node;
The IP address of the interface of described Egress node using the mark in described tunnel as described Egress node;
Described Egress node is the node N in first node
mdistribute outlet label, described first node is all nodes except described Egress node on the path in described tunnel, and the quantity of all nodes that described first node comprises is m, described node N
mthe upper hop node of described Egress node on described path;
Described Egress node generating labels mapping relations, the mark that described label mapping relation is described tunnel and described node N
mthe mapping relations of outlet label;
Described Egress node is to described node N
msend described label mapping relation.
5. method as claimed in claim 4, is characterized in that, described method also comprises:
Described Egress node does not enable Interior Gateway Protocol IGP on described interface.
6. for setting up the method in tunnel, it is characterized in that, described method comprises:
The first via that the Ingress node in the path in tunnel receives self-controller by, described tunnel is the tunnel definite according to business, the described first via by destination address be the mark in described tunnel, the mark in described tunnel is the Internet protocol IP address of the Egress node in described tunnel, the described first via by down hop be the address of the next-hop node of described Ingress node on described path;
Described Ingress node according to the described first via by, receive the label mapping relation that the next-hop node of described Ingress node on described path sends, the mapping relations of the mark that described label mapping relation is described tunnel and the outlet label of described Ingress node;
Described Ingress node generates tunnel list item, and described tunnel list item comprises the mapping relations of the mark in described tunnel and the outlet label of described Ingress node.
7. method as claimed in claim 6, is characterized in that, after described generation tunnel list item, described method also comprises:
Described Ingress node receives the secondary route from described controller, and the route prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel;
Described Ingress node is according to described tunnel list item and described secondary route, calculated address mapping item, the mapping relations of the network segment corresponding to the outlet label that described address mapping table item is described Ingress node and described business;
Described Ingress node is in the time of the destination address of the message receiving and network segment coupling corresponding to described business, according to message described in the outlet label forwarding of Ingress node described in described address mapping table item.
8. a controller, is characterized in that, described controller comprises:
Mark generation unit, for generating the mark in tunnel, described tunnel is the tunnel definite according to business, and described tunnel comprises Ingress node and Egress node, and the mark in described tunnel is the Internet protocol IP address of described Egress node;
Node acquiring unit, for obtaining all nodes and the described all internodal annexations on the path in described tunnel, described all nodes comprise described Egress node and first node, described first node is all nodes except described Egress node on described path, and the quantity of all nodes that described first node comprises is m;
Transmitting element, for the mark that sends the described tunnel that described mark generation unit generates to described Egress node;
The first via is by allocation units, for all nodes on the described path obtaining according to described node acquiring unit and all internodal annexation on described path, for the each node in described first node distribute the first via by, wherein, be node N in described first node
idistribute the first via by destination address be the mark in described tunnel, be described node N
idistribute the first via by down hop be node N
i+1address, described node N
i+1described node N
inext-hop node on described path, described i is more than or equal to 1 and be less than or equal to the integer of m.
9. controller as claimed in claim 8, is characterized in that, described controller also comprises: secondary route allocation units;
Described secondary route allocation units are used for generating secondary route, and the route prefix of described secondary route is the network segment corresponding to described business, and the down hop of described secondary route is the mark in described tunnel;
The extremely described Ingress node of described secondary route that described transmitting element generates specifically for sending described secondary route allocation units.
10. an Egress node, is characterized in that, described Egress node comprises:
Receiving element, for receiving the mark in tunnel of self-controller, described tunnel is the tunnel definite according to business, the mark in described tunnel is the Internet protocol IP address of described Egress node;
Interface configuration unit, for the IP address using the mark in the described tunnel of described receiving element reception as the interface of described Egress node;
Label distribution unit, is used to the node N in first node
mdistribute outlet label, described first node is all nodes except described Egress node on the path in described tunnel, and the quantity of all nodes that described first node comprises is m, described node N
mthe upper hop node of described Egress node on described path;
Mapping generation unit is node N for mark and the described label distribution unit in the described tunnel that receives according to described receiving element
mthe outlet label distributing, generating labels mapping relations, the mark that described label mapping relation is described tunnel and described node N
mthe mapping relations of outlet label;
Transmitting element, for to described node N
msend the described label mapping relation that described mapping generation unit generates.
11. Egress nodes as claimed in claim 10, is characterized in that, described Egress node also comprises:
Protocol enabled unit, for not enabling Interior Gateway Protocol IGP on described interface.
12. 1 kinds of Ingress nodes, is characterized in that, described Ingress node comprises:
The first receiving element, for the first via that receives self-controller by, the described first via by destination address be the mark in tunnel, described tunnel is the tunnel definite according to business, the mark in described tunnel is the Internet protocol IP address of the Egress node in described tunnel, the described first via by down hop be the address of the next-hop node of described Ingress node on the path in described tunnel;
The second receiving element, for according to described first receiving element receive the described first via by, receive the label mapping relation that the next-hop node of described Ingress node on described path sends, the mapping relations of the mark that described label mapping relation is described tunnel and the outlet label of described Ingress node;
Tunnel list item generation unit, for the described label mapping relation receiving according to described the second receiving element, generates tunnel list item, and described tunnel list item comprises the mapping relations of the mark in described tunnel and the outlet label of described Ingress node.
13. want the Ingress node as described in 12 as right, it is characterized in that, described Ingress node also comprises:
The 3rd receiving element, for receiving the secondary route from described controller, the route prefix of described secondary route is the network segment corresponding to described business, the down hop of described secondary route is the mark in described tunnel;
Address mapping generation unit, be used for according to the described secondary route of the described tunnel list item of described tunnel list item generation unit generation and described the 3rd receiving element reception, calculated address mapping item, the mapping relations of the network segment corresponding to the outlet label that described address mapping table item is described Ingress node and described business;
Packet sending unit, during for the destination address at the message receiving and the network segment corresponding to described business coupling, message described in the outlet label forwarding of Ingress node described in the described address mapping table item generating according to described address mapping generation unit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410090021.7A CN103841022B (en) | 2014-03-12 | 2014-03-12 | For setting up the method and device in tunnel |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410090021.7A CN103841022B (en) | 2014-03-12 | 2014-03-12 | For setting up the method and device in tunnel |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103841022A true CN103841022A (en) | 2014-06-04 |
| CN103841022B CN103841022B (en) | 2017-04-05 |
Family
ID=50804174
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410090021.7A Active CN103841022B (en) | 2014-03-12 | 2014-03-12 | For setting up the method and device in tunnel |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103841022B (en) |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016058329A1 (en) * | 2014-10-17 | 2016-04-21 | 中兴通讯股份有限公司 | Service transfer method and device |
| CN105610717A (en) * | 2015-12-30 | 2016-05-25 | 杭州华三通信技术有限公司 | Cross-SDN routing release method and device |
| WO2016115850A1 (en) * | 2015-01-19 | 2016-07-28 | 中兴通讯股份有限公司 | Segment routing processing method, processing apparatus and sending apparatus |
| WO2016198015A1 (en) * | 2015-11-02 | 2016-12-15 | 中兴通讯股份有限公司 | Packet transmission method, apparatus, and system |
| CN106576074A (en) * | 2015-07-31 | 2017-04-19 | 华为技术有限公司 | Routing rule acquisition method, device and system |
| CN106656802A (en) * | 2016-12-21 | 2017-05-10 | 北京格林伟迪科技股份有限公司 | End-to-end tunnel generation method |
| CN107370675A (en) * | 2016-05-13 | 2017-11-21 | 华为技术有限公司 | It route the method disseminated and node |
| CN108092909A (en) * | 2016-11-21 | 2018-05-29 | 中国移动通信有限公司研究院 | Data flow control method, apparatus and system |
| CN108429646A (en) * | 2018-03-07 | 2018-08-21 | 广州西麦科技股份有限公司 | A kind of method and device of optimization Ipsec VPN |
| CN108471629A (en) * | 2017-02-23 | 2018-08-31 | 华为技术有限公司 | The control method of business service quality, equipment and system in transmission network |
| CN108494684A (en) * | 2018-03-30 | 2018-09-04 | 新华三技术有限公司 | Create the method and device in tunnel |
| WO2018214731A1 (en) * | 2017-05-26 | 2018-11-29 | 新华三技术有限公司 | State detection of netconf session |
| CN109639600A (en) * | 2019-01-25 | 2019-04-16 | 新华三技术有限公司 | A kind of method and device of tunnel speed limit |
| CN109923838A (en) * | 2017-05-22 | 2019-06-21 | 华为技术有限公司 | Bridge the elastic VPN of long-range isolated island |
| CN110535782A (en) * | 2019-06-15 | 2019-12-03 | 华为技术有限公司 | A kind of message processing method, equipment and system realizing QoS and ensureing |
| CN110838965A (en) * | 2019-09-25 | 2020-02-25 | 北京华为数字技术有限公司 | Tunnel establishment method and receiving node |
| CN111416762A (en) * | 2020-02-28 | 2020-07-14 | 联想(北京)有限公司 | Method, device, system and storage medium for establishing network tunnel |
| CN115037681A (en) * | 2021-03-04 | 2022-09-09 | 国家电网有限公司信息通信分公司 | Label forwarding method and system with IP address as explicit path |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040037296A1 (en) * | 2002-08-21 | 2004-02-26 | Kim Mi Hui | Method for setting up QoS supported bi-directional tunnel and distributing L2VPN membership information for L2VPN using extended LDP |
| CN101083611A (en) * | 2006-05-30 | 2007-12-05 | 中兴通讯股份有限公司 | Apparatus for using color identification L-LSP tunnel packet forwarding priority |
| CN101090355A (en) * | 2007-07-24 | 2007-12-19 | 杭州华三通信技术有限公司 | Label exchange route setting method, system and equipment of virtual special network channel |
| EP2061189A1 (en) * | 2006-09-15 | 2009-05-20 | Huawei Technologies Co., Ltd. | Ethernet frame transmitting method and ethernet infrastructure |
| CN101656663A (en) * | 2008-08-20 | 2010-02-24 | 华为技术有限公司 | Method, device and system for forwarding MPLS multicast message |
| US20110032828A1 (en) * | 2009-08-04 | 2011-02-10 | Thomas Scholl | Methods and apparatus to respond to signaling protocol failures in traffic engineering tunnels |
| CN102025608A (en) * | 2009-09-17 | 2011-04-20 | 中兴通讯股份有限公司 | Communication method, data message forwarding method in communication process as well as communication nodes |
| CN102088390A (en) * | 2009-12-08 | 2011-06-08 | 中兴通讯股份有限公司 | Implementation method of user mobility |
| CN102136991A (en) * | 2010-07-02 | 2011-07-27 | 华为技术有限公司 | Method and node for configuring tunnel on label switching path |
| CN102439919A (en) * | 2011-09-28 | 2012-05-02 | 华为技术有限公司 | Method, device and system for building lable switching path |
| CN102882787A (en) * | 2012-10-11 | 2013-01-16 | 华为技术有限公司 | Method and device for determining retransmission routes of traffic engineering tunnels |
| CN103152267A (en) * | 2013-02-04 | 2013-06-12 | 华为技术有限公司 | Route managing method and route method and network controller and router |
-
2014
- 2014-03-12 CN CN201410090021.7A patent/CN103841022B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040037296A1 (en) * | 2002-08-21 | 2004-02-26 | Kim Mi Hui | Method for setting up QoS supported bi-directional tunnel and distributing L2VPN membership information for L2VPN using extended LDP |
| CN101083611A (en) * | 2006-05-30 | 2007-12-05 | 中兴通讯股份有限公司 | Apparatus for using color identification L-LSP tunnel packet forwarding priority |
| EP2061189A1 (en) * | 2006-09-15 | 2009-05-20 | Huawei Technologies Co., Ltd. | Ethernet frame transmitting method and ethernet infrastructure |
| CN101090355A (en) * | 2007-07-24 | 2007-12-19 | 杭州华三通信技术有限公司 | Label exchange route setting method, system and equipment of virtual special network channel |
| CN101656663A (en) * | 2008-08-20 | 2010-02-24 | 华为技术有限公司 | Method, device and system for forwarding MPLS multicast message |
| US20110032828A1 (en) * | 2009-08-04 | 2011-02-10 | Thomas Scholl | Methods and apparatus to respond to signaling protocol failures in traffic engineering tunnels |
| CN102025608A (en) * | 2009-09-17 | 2011-04-20 | 中兴通讯股份有限公司 | Communication method, data message forwarding method in communication process as well as communication nodes |
| CN102088390A (en) * | 2009-12-08 | 2011-06-08 | 中兴通讯股份有限公司 | Implementation method of user mobility |
| CN102136991A (en) * | 2010-07-02 | 2011-07-27 | 华为技术有限公司 | Method and node for configuring tunnel on label switching path |
| CN102439919A (en) * | 2011-09-28 | 2012-05-02 | 华为技术有限公司 | Method, device and system for building lable switching path |
| CN102882787A (en) * | 2012-10-11 | 2013-01-16 | 华为技术有限公司 | Method and device for determining retransmission routes of traffic engineering tunnels |
| CN103152267A (en) * | 2013-02-04 | 2013-06-12 | 华为技术有限公司 | Route managing method and route method and network controller and router |
Cited By (33)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016058329A1 (en) * | 2014-10-17 | 2016-04-21 | 中兴通讯股份有限公司 | Service transfer method and device |
| WO2016115850A1 (en) * | 2015-01-19 | 2016-07-28 | 中兴通讯股份有限公司 | Segment routing processing method, processing apparatus and sending apparatus |
| CN105871721A (en) * | 2015-01-19 | 2016-08-17 | 中兴通讯股份有限公司 | Segment routing processing method, processing device and sending device |
| CN105871721B (en) * | 2015-01-19 | 2020-05-05 | 中兴通讯股份有限公司 | Segment routing processing method, processing device and sending device |
| CN106576074A (en) * | 2015-07-31 | 2017-04-19 | 华为技术有限公司 | Routing rule acquisition method, device and system |
| CN106576074B (en) * | 2015-07-31 | 2020-04-21 | 华为技术有限公司 | Method, equipment and system for acquiring routing rule |
| WO2016198015A1 (en) * | 2015-11-02 | 2016-12-15 | 中兴通讯股份有限公司 | Packet transmission method, apparatus, and system |
| CN106656781A (en) * | 2015-11-02 | 2017-05-10 | 中兴通讯股份有限公司 | Message transmission method, apparatus and system |
| CN106656781B (en) * | 2015-11-02 | 2020-12-11 | 中兴通讯股份有限公司 | Method, device and system for transmitting message |
| CN105610717B (en) * | 2015-12-30 | 2018-11-27 | 新华三技术有限公司 | A kind of route issuing method and device across SDN network |
| CN105610717A (en) * | 2015-12-30 | 2016-05-25 | 杭州华三通信技术有限公司 | Cross-SDN routing release method and device |
| CN107370675B (en) * | 2016-05-13 | 2021-02-23 | 华为技术有限公司 | Method and node for route dissemination |
| CN107370675A (en) * | 2016-05-13 | 2017-11-21 | 华为技术有限公司 | It route the method disseminated and node |
| CN108092909A (en) * | 2016-11-21 | 2018-05-29 | 中国移动通信有限公司研究院 | Data flow control method, apparatus and system |
| CN106656802A (en) * | 2016-12-21 | 2017-05-10 | 北京格林伟迪科技股份有限公司 | End-to-end tunnel generation method |
| CN108471629A (en) * | 2017-02-23 | 2018-08-31 | 华为技术有限公司 | The control method of business service quality, equipment and system in transmission network |
| US10938599B2 (en) | 2017-05-22 | 2021-03-02 | Futurewei Technologies, Inc. | Elastic VPN that bridges remote islands |
| CN109923838A (en) * | 2017-05-22 | 2019-06-21 | 华为技术有限公司 | Bridge the elastic VPN of long-range isolated island |
| US11792045B2 (en) | 2017-05-22 | 2023-10-17 | Futurewei Technologies, Inc. | Elastic VPN that bridges remote islands |
| WO2018214731A1 (en) * | 2017-05-26 | 2018-11-29 | 新华三技术有限公司 | State detection of netconf session |
| US11843534B2 (en) | 2017-05-26 | 2023-12-12 | New H3C Technologies Co., Ltd. | State detection of NETCONF session |
| CN108429646B (en) * | 2018-03-07 | 2021-05-11 | 广州西麦科技股份有限公司 | Method and device for optimizing Ipsec VPN |
| CN108429646A (en) * | 2018-03-07 | 2018-08-21 | 广州西麦科技股份有限公司 | A kind of method and device of optimization Ipsec VPN |
| CN108494684B (en) * | 2018-03-30 | 2021-01-26 | 新华三技术有限公司 | Method and device for establishing tunnel |
| CN108494684A (en) * | 2018-03-30 | 2018-09-04 | 新华三技术有限公司 | Create the method and device in tunnel |
| CN109639600B (en) * | 2019-01-25 | 2022-07-01 | 新华三技术有限公司 | Tunnel speed limiting method and device |
| CN109639600A (en) * | 2019-01-25 | 2019-04-16 | 新华三技术有限公司 | A kind of method and device of tunnel speed limit |
| CN110535782B (en) * | 2019-06-15 | 2023-06-20 | 华为技术有限公司 | Message processing method, device and system for realizing QoS guarantee |
| CN110535782A (en) * | 2019-06-15 | 2019-12-03 | 华为技术有限公司 | A kind of message processing method, equipment and system realizing QoS and ensureing |
| US12107764B2 (en) | 2019-06-15 | 2024-10-01 | Huawei Technologies Co., Ltd. | Packet processing method for implementing QoS guarantee, device, and system |
| CN110838965A (en) * | 2019-09-25 | 2020-02-25 | 北京华为数字技术有限公司 | Tunnel establishment method and receiving node |
| CN111416762A (en) * | 2020-02-28 | 2020-07-14 | 联想(北京)有限公司 | Method, device, system and storage medium for establishing network tunnel |
| CN115037681A (en) * | 2021-03-04 | 2022-09-09 | 国家电网有限公司信息通信分公司 | Label forwarding method and system with IP address as explicit path |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103841022B (en) | 2017-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103841022A (en) | Method and device for building tunnel | |
| CN105049350B (en) | Utilize the method, apparatus and system of the Segment routing of the reciprocity engineering in outlet | |
| US10021023B2 (en) | Packet forwarding method, controller, forwarding device, and network system | |
| US9749214B2 (en) | Software defined networking (SDN) specific topology information discovery | |
| EP2540041B1 (en) | System and method for computing a backup ingress of a point-to-multipoint label switched path | |
| CN101606341B (en) | Technique for efficiently routing ip traffic on CE-CE paths across a provider network | |
| CN103155499B (en) | For calculating the system and method for the backup outlet of point-to-multipoint label switch paths | |
| CN101133408B (en) | Computation of a shortest inter-domain te-lsp across a set of autonomous systems | |
| CN101243648B (en) | Method and apparatus for enabling routing of label switched data packets | |
| CN101243654B (en) | Method and apparatus for enabling routing of label switched data packets | |
| CN107637031A (en) | Path-calculating element central controller (PCECC) for Network | |
| CN103891220B (en) | The MPLS using LDP quickly re-routes method and the NE of (LDP-FRR) | |
| WO2019134639A1 (en) | Method and apparatus for implementing optimal seamless cross-domain path, device and storage medium | |
| KR20150036206A (en) | System and method for switching traffic from sub-optimal primary p2mp to standby p2mp | |
| CN103354988A (en) | System and method for computing point-to-point label switched path crossing multiple domains | |
| CN104753713A (en) | SDN (Self-Defending Network) service deployment method and SDN controller | |
| CN107888497A (en) | Communication means, the network equipment and computer-readable recording medium | |
| CN104396197A (en) | Selecting between equal cost shortest paths in a 802.1aq network using split tiebreakers | |
| Kalmykov et al. | Segment routing as a basis for software defined network | |
| CN107483338A (en) | A kind of method, apparatus and system for determining cross-domain label switched path tunnel | |
| CN103117925A (en) | Processing method and processing device for data message forward | |
| CN110140331A (en) | Path calculation method and device | |
| CN113709033A (en) | Segment traceroute for segment routing traffic engineering | |
| CN104092611A (en) | Method and device for determining label switching route with restrained cross region | |
| CN105391633A (en) | Transponder, controller and route distribution method of controller |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |