CN103581017B - The transmission method and device of path segment information - Google Patents
The transmission method and device of path segment information Download PDFInfo
- Publication number
- CN103581017B CN103581017B CN201210256058.3A CN201210256058A CN103581017B CN 103581017 B CN103581017 B CN 103581017B CN 201210256058 A CN201210256058 A CN 201210256058A CN 103581017 B CN103581017 B CN 103581017B
- Authority
- CN
- China
- Prior art keywords
- ofc
- message
- path
- information
- segment information
- 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.)
- Expired - Fee Related
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 21
- 229940067916 PCE Drugs 0.000 claims description 92
- 230000000875 corresponding Effects 0.000 claims description 36
- 238000011144 upstream manufacturing Methods 0.000 claims description 9
- 238000004891 communication Methods 0.000 claims description 5
- 201000006284 orofacial cleft 1 Diseases 0.000 description 30
- 238000000034 method Methods 0.000 description 11
- 241001576000 Ero Species 0.000 description 6
- 230000011664 signaling Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 239000010410 layer Substances 0.000 description 4
- 201000005625 neuroleptic malignant syndrome Diseases 0.000 description 4
- 230000003287 optical Effects 0.000 description 4
- 238000004422 calculation algorithm Methods 0.000 description 2
- 239000000969 carrier Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006011 modification reaction Methods 0.000 description 1
- 239000002356 single layer Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised Effects 0.000 description 1
Abstract
The invention discloses a kind of transmission method and device of path segment information, wherein, this method includes：First OFC obtains first path segment information, wherein, first path segment information includes the path segment information in the LSP domains where the first OFC being currently configured；The route segment in domain where first OFC configures the first OFC according to first path segment information；First OFC sends the first message for carrying the second path segment information to the 2nd OFC, wherein, 2nd OFC is the first OFC downstream OFC, second routing information includes the path segment information in LSP domains where the 2nd OFC, or the path segment information in LSP domains where domain and the 2nd OFC downstream OFC where the 2nd OFC.Pass through the present invention so that the OFC for belonging to different AS domains on LSP knows the path segment information that needs configure.
Description
Technical field
The present invention relates to the communications field, in particular to a kind of transmission method and device of path segment information.
Background technology
Path computing member（Path Computation Element, referred to as PCE）It is ability to domain where calculating it（Example
Such as, autonomous system（Autonomous System are referred to as AS）, or region（area）, or domain etc.）In know
The entity in the path between any node, it can be integrated in router interior, and a single entity can also be used as to exist
In network, it can also be integrated with network management system.
Why particularly useful PCE is, be because they become more apparent upon the network traffics in domain where them, therefore can quilt
For more preferable path computing.Head end LSR is also possible to as path calculating client（Path Computation Client, letter
Referred to as PCC）Work.PCC is arranged to PCE path computation requests, and receives the sound for carrying the path calculated
Should, the response may consider other requests from other PCC.It is further noted that when PCE to another
When PCE sends request, it serves as PCC.PCC can be realized with the information of interaction between PCE by internal interface, can also be passed through
Communication protocol interaction between PCC, PCE.Communication protocol example between PCC, PCE can be in the entitled " Path in March, 2009
Computation Element（PCE）Communication Protocol（PCEP）" RFC5440 in find, accordingly by
Quote by the full content of this document combine on the whole and this.
PCC can be had found by the pre-configured of keeper or using PCE（PCED）Message（" notice "）And learn PCE's
In the presence of PCED message is sent from PCE in its region or through whole AS, for noticing its service.PCED message
Address that can be including PCE and the instruction etc. of PCE abilities, PCE, which possesses, calculates path between local path, inter-area path, AS, more
The abilities such as domain path, di-verse paths.Entitled " OPSF Protocol of the example of PCED message in January, 2008
Extensions for Path Computation Element（PCE）Discovery " RFC5088 and the topic issued simultaneously
For " IS-IS Protocol Extensions for Path Computation Element（PCE）Discovery's "
Be described in RFC5089, accordingly by quote by the full content of this document combine on the whole and this.
Path computing member is a centralized computational entity, after PCC is given in its path calculated, if PCC is one
The first node in path（Label Edge Router, referred to as LER）, as shown in figure 1, then by distributed signaling technology such as
RSVP-TE（Resource ReSer Vation Protocol-Traffic Engineering）To reserve resource；Or such as
Fruit PCC is a webmaster（Network Management System, referred to as NMS）, as shown in Fig. 2 then configuration information is sent out
To first node, first node disposes path by distributed signaling technology again.
It is centralized in theory to issue configuration information to each node to get through one however, if PCC is a webmaster
Path is entirely equipment feasible, that simply the webmaster of each manufacturer manages each manufacturer itself, connecing between webmaster and equipment
Mouth operation proprietary protocol, thus the deployment of path end to end of the multiple vendor equipments of leap, can only use distributed letter
The solution of order.In view of the rise of data center's technology, standards organization open network organization（Open Network Forum,
Referred to as ONF）Openflow agreements are developed, operate in Openflow controllers（Openflow Controller）With
Openflow interchangers（Openflow Switch）Between, to configure flow table；In Openflow agreements, Openflow
Switch is a simple switching equipment, can be homogeneous, and all intelligence has all shifted to Openflow Controller
On.NMS can as Openflow controllers application layer or itself be used as controller, in controller and network element（Network
Element, referred to as NE）Between operation standard Openflow agreements, based on this, NMS is as Openflow Controller
Or the equipment of its application layer can configuration different manufacturers.
Speed is opened using what the deployment route scheme of centralization can accelerate business.For example, in wavelength switched optical network
（WSON）In, Italian research CNIT is in paper " OpenFlow and PCE Architectures in
By emulating actual physical network, contrast distribution formula signaling in Wavelength Switched Optical Networks "
With centralized configuration two schemes, find centralized configuration than distributed signaling scheme path blocks rate, control plane load,
Index will get well in terms of path settling time, OpenFlow controller loads.The WSON networks considered in this paper are also
An only single layer network, it is contemplated that the multi-layer multi-domain that packet switch, time gas exchange and wavelength exchange is integrated with one
In network, centralized deployment scheme is more superior than distributed signaling scheme.
Fig. 3 is the cooperation deployment TE-LSP signal between PCE and Openflow Controller according to correlation technique
Figure, in the system as shown in fig. 3, gives three Autonomous Domain AS, respectively AS1, AS2 and AS3；Wherein, each AS has one
The individual PCE for being responsible for specially calculating TE-LSP and special concentration issue the OFC of flow table（Openflow Controller）, it is respectively
PCE1 and OFC1, PCE2 and OFC2, PCE3 and OFC3.As shown in figure 3, the Openflow given in each Autonomous Domain is exchanged
Machine, these interchangers can be multiprotocol label switching（Multi-Protocol Label Switch, referred to as MPLS）Exchange
Machine or Ethernet switch, or the SDH based on time gas exchange（Synchronous Digital
Hierarchical）And OTN（Optical Transport Network）Interchanger, it can even is that what is exchanged based on wavelength
ROADM（Reconfigurable Optical Add Drop Multiplexer）Equipment.It is further or a variety of
The mixing apparatus of exchange, for example MPLS exchanges and OTN time gas exchanges are supported simultaneously, or support that OTN is exchanged and wavelength is handed over simultaneously
Change.
The interchanger that Fig. 3 is provided is respectively S1, S2, S3, S4, S5, S6, S7, S8, S9, S10, S11, S12 and S13, its
In, S1 and the edge switch that S2 is AS1, the edge switch S4 with AS2 are connected with S5, AS2 edge switch S6 and S7
It is connected by domain-to-domain link with S9 with S10.Between interchanger and OFC by band outside link connection, as shown in phantom in Figure 3.
It can be that a jump or multi-hop are connected between interchanger and controller, not be limited here, as long as up to.
It is heavier that the load in path is calculated in view of PCE, such as calculating the path of multi-layer multi-domain or using IA-
RWA（Impairment Awareness Routing Wavelength Algorithm）When calculating wavelength path, with OFC points
Open position in two it is different physically, entity can be physical server.As long as the PCE IP in each domain are up in Fig. 3
Dotted line shown in.
For example, to establish a label switched path from S1 to S13（Label Switch Path, referred to as LSP）,
According to Openflow framework, the configuration in path can be based on first packet and trigger, i.e. S1 receives message up sending OFC1, OFC1 a work
PCE1 is asked to calculate path for PCC；Or the request of user is sent directly to OFC1, OFC1 goes to ask PCE1 modules to calculate one again
Bar LSP.No matter which kind of mode used, after PCE1 receives PCRep message, PCE2 downstream can be asked to calculate, PCE2 is again
Go to ask PCE3 downstream to calculate；Here upstream or downstream relationship is later based on the elder generation for receiving path computing request
Distinguish.PCE3 returns to the route segment in the AS3 of calculating the PCE2 of its upstream, PCE2 again the AS2 of calculating route segment and
Route segment in AS3 splices the PCE1 for being sent to its upstream, and then PCE1 calculates the route segment in AS1 again, then from calculating
All paths in select optimal path and return to OFC1.Above-mentioned calculating process can be followed defined in RFCRFC5441
BRPC（Backward-Recursive PCE-Based Computation）With the Pathkey schemes defined in RFC5520, this
In be cited in full text in this.
Flow table is issued to the interchanger in AS1 by Openflow agreements after OFC1 receives complete path, however,
Interchanger in AS2 and AS3 is not belonging to AS1, thus flow table item can only by OFC2 and OFC3 come be respectively configured, it is necessary to OFC2 and
OFC3 knows the flow table item oneself to be issued, and this is the part of current PCE frameworks and agreement missing.
For how between OFC the problem of bang path segment information, not yet proposing effective solution at present in correlation technique
Certainly scheme.
The content of the invention
For how between OFC the problem of bang path segment information, the invention provides a kind of path in correlation technique
The transmission method and device of segment information, at least to solve the above problems.
A kind of according to an aspect of the invention, there is provided transmission method of path segment information, it is characterised in that including：
First Openflow controllers OFC obtains first path segment information, wherein, the first path segment information includes what is be currently configured
The path segment information in label switching path LSP domain where the first OFC；First OFC is according to the first path section
The route segment in domain where first OFC described in information configuration；First OFC is sent to the 2nd OFC carries the second route segment letter
The first message of breath, wherein, the 2nd OFC is the downstream OFC of the first OFC, and second routing information includes described
The path segment information in LSP domains where the 2nd OFC, or LSP domains and described second where the 2nd OFC
The path segment information in domain where OFC downstream OFC.
Preferably, the first OFC obtains first path segment information, including：First OFC is from first path computing unit
The OFC of PCE or described first upstream OFC obtains the first path segment information, wherein, the first PCE is the first OFC
Corresponding PCE.
The first path segment information preferably is obtained from the first PCE in, the first OFC, including：Described first
OFC receives the second message that the first PCE is sent, wherein, the information that second message carries includes the first path
Segment information；First OFC obtains the first path segment information from second message.
Preferably, the information that second message carries also includes：Route segment configuration instruction, wherein, the route segment is matched somebody with somebody
Put instruction and be used for the route segment for indicating that the first OFC configures the first OFC places domain.
Preferably, the first path segment information record has the complete path segment informations of the LSP, or the LSP is in institute
The information of the route segment in domain where stating the first OFC, or the LSP is under domain where the first OFC and the first OFC
The path segment information in domain where swimming OFC.
Preferably, the first OFC sends first message to the 2nd OFC, including：Pass through corresponding to the first OFC
2nd PCE corresponding to one PCE to the 2nd OFC sends the first message；By the 2nd PCE to the 2nd OFC
Send the first message.
Preferably, the second route segment information includes：The path segment information in LSP domains where the 2nd OFC,
Or the path segment information in LSP domains where domain and the 2nd OFC downstream OFC where the 2nd OFC.
Preferably, the first OFC sends first message to the 2nd OFC, including：First OFC is directly to described
Two OFC send the first message.
Preferably, the first OFC directly sends the first message to the 2nd OFC, including：First OFC
Passage path computing unit communication protocol PCEP sends the first message to the 2nd OFC.
Preferably, the second route segment information includes：LSP domains and described second where the 2nd OFC
The path segment information in domain where OFC downstream OFC.
Preferably, the first message or second message also carry route segment configuration instruction, wherein, the path
Section configuration instruction is used for the route segment in domain where indicating the first OFC configurations the first OFC, or instruction the 2nd OFC
The route segment in domain where configuring the 2nd OFC.
Preferably, after the first OFC sends first message to the 2nd OFC, in addition to：2nd OFC is according to institute
The route segment in domain where stating the 2nd OFC described in the second route segment information configuration；Do not include not in the segment information of second path
During the information of the route segment of configuration, in addition to：2nd OFC sends the 3rd message to the first OFC, wherein, described the
Three message carry the information completed for indicating the LSP configurations.
According to another aspect of the present invention, there is provided a kind of transfer device of path segment information, positioned at first
In Openflow controllers OFC, it is characterised in that including：Acquisition module, for obtaining first path segment information, wherein, it is described
First path segment information includes the path segment information in the label switching path LSP domain where the first OFC being currently configured；Match somebody with somebody
Module is put, the route segment for domain where configuring the first OFC according to the first path segment information；Sending module, it is used for
The first message for carrying the second path segment information is sent to the 2nd OFC, wherein, the 2nd OFC is under the first OFC
OFC is swum, second routing information includes the path segment information and described second in LSP domains where the 2nd OFC
The path segment information in domain where OFC downstream OFC.
Preferably, the acquisition module obtains the first path segment information in such a way：The acquisition module from
The OFC of first path computing unit PCE or described first upstream OFC obtains the first path segment information, wherein, described first
PCE is PCE corresponding to the first OFC.
Preferably, the acquisition module includes：Receiving unit, the second message sent for receiving the first PCE, its
In, the information that second message carries includes the first path segment information；Acquiring unit, for from second message
Obtain the first path segment information.
Preferably, the sending module sends the first message to the 2nd OFC in such a way：By described
The 2nd PCE corresponding to the first PCE to the 2nd OFC sends the first message corresponding to first OFC；Pass through described second
PCE sends the first message to the 2nd OFC.
Preferably, the sending module sends the first message to the 2nd OFC in such a way：The transmission
Module directly sends the first message to the 2nd OFC.
By the present invention, the first OFC obtains LSP first path segment information, according to first path segment information configuration first
The route segment in AS domains where OFC, and first message is sent to the first OFC downstream OFC, the of LSP is carried in first message
Two path segment informations, realize the path segment information that LSP is transmitted on OFC so that the OFC for belonging to not same area on LSP knows need
The information for the route segment to be configured, complete the configuration of each route segments of LSP.
Brief description of the drawings
Accompanying drawing described herein is used for providing a further understanding of the present invention, forms the part of the application, this hair
Bright schematic description and description is used to explain the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings：
Fig. 1 is the schematic diagram to be cooperated according to the LER of correlation technique as PCC with PCE；
Fig. 2 is the schematic diagram to be cooperated according to the NMS of correlation technique as PCC with PCE；
Fig. 3 is the cooperation deployment TE-LSP signal between PCE and Openflow Controller according to correlation technique
Figure one；
Fig. 4 is the flow chart according to the transmission method of the path segment information of embodiment of the present invention；
Fig. 5 is the cooperation deployment TE-LSP signal between PCE and Openflow Controller according to correlation technique
Figure two；
Fig. 6 is the cooperation deployment TE-LSP signal between PCE and Openflow Controller according to correlation technique
Figure three；
Fig. 7 is the schematic diagram according to the RP subject forms of embodiment of the present invention；
Fig. 8 is the schematic diagram according to the Notification subjects of embodiment of the present invention；
Fig. 9 is the structured flowchart of the transfer device of path segment information according to embodiments of the present invention；
Figure 10 is the structured flowchart of preferable acquisition module according to embodiments of the present invention.
Embodiment
Describe the present invention in detail below with reference to accompanying drawing and in conjunction with the embodiments.It should be noted that do not conflicting
In the case of, the feature in embodiment and embodiment in the application can be mutually combined.
For how between OFC the problem of bang path segment information, embodiment of the present invention is based on PCE in correlation technique
With Openflow controller interworking architectures, there is provided a kind of method that the route segment for needing to configure is transmitted between OFC, rapid deployment
LSP。
According to embodiments of the present invention, there is provided a kind of transmission method of path segment information, bang path section is believed between OFC
Breath, is configured, rapid deployment LSP to the route segment in different AS domains.
Fig. 4 is according to the flow chart of the transmission method of the path segment information of embodiment of the present invention, as shown in figure 4, the party
Method can include step S402 to step S406.
Step S402, the first OFC obtain first path segment information, wherein, first path segment information includes what is be currently configured
The path segment information in LSP domains where the first OFC.
The route segment in domain where step S404, the first OFC configure the first OFC according to first path segment information.
Step S406, the first OFC send the first message for carrying the second path segment information to the 2nd OFC, wherein, second
OFC is the first OFC downstream OFC, and the second routing information includes the path segment information in LSP domains where the 2nd OFC, or LSP exists
The path segment information in domain where domain and the 2nd OFC downstream OFC where 2nd OFC.
By the embodiment of the present invention, the first OFC obtains LSP first path segment information, matches somebody with somebody according to first path segment information
The route segment in AS domains where putting the first OFC, and first message is sent to the first OFC downstream OFC, carried in first message
LSP the second path segment information, realize the path segment information that LSP is transmitted on OFC so that belong to the OFC of not same area on LSP
Know the information for the route segment that needs configure, complete the configuration of each route segments of LSP.
In embodiments of the present invention, following three kinds of modes bang path segment information can be passed through between OFC：Mode one, OFC
Between pass through PCE transfers path segment information（As shown in Figure 3）；Mode two, pass through PCEP protocol forwards path segment information between OFC
（As shown in Figure 5）；Mode three, OFC and PCE transmit route segment information on same physical entity（As shown in Figure 6）.Divide below
The other preferred embodiment to above-mentioned three kinds of modes is described.
In a preferred embodiment of the embodiment of the present invention, when the first OFC obtains LSP first path segment information,
First path information can be obtained from PCE corresponding to the first OFC, or if the route segment in domain is not LSP where the first OFC
First route segment, the first OFC can also obtain first path segment information from the first OFC upstream OFC.In mode one, the
What one OFC was got is the domain where the first OFC（For example, AS domains）Route segment information, for example, OFC1 as shown in Figure 3
The path segment information got from PCE1 can be AS1 path segment information（For example, [S1, S3]）.In mode two, if the
One OFC is OFC corresponding to first route segment of LSP, and the first OFC believes from the first path sections got of PCE corresponding to the first OFC
Breath record has the complete path segment informations of LSP, or the information of LSP route segments in domain where the first OFC, or LSP is in the first OFC
The path segment information in domain where place domain and the first OFC downstream OFC.
Further, the first OFC from the first PCE obtain first path segment information when, the first OFC can receive the first PCE
The second message sent, wherein, the information that the second message carries includes first path segment information, and obtains from the second message the
One path segment information.For example, the first PCE be LSP each route segment first route segment corresponding to PCE when, the first PCE
It is determined that after LSP optimal path the second message can be sent to the first OFC（For example, PCRep message）, the first OFC receives the
The second message that one PCE is sent, first path segment information is obtained from the second message.Preferably, first message or the second message
The information of carrying can also include：Route segment configuration instruction, wherein, route segment configuration instruction is used to indicate the first OFC configurations the
The route segment in domain where one OFC, or the 2nd OFC of instruction configure the route segment in the 2nd OFC places domain.
For mode one, when the first OFC is to the 2nd OFC transmission first messages, the first OFC can be corresponding by the first OFC
The first PCE to corresponding to the 2nd OFC the 2nd PCE send first message, by the 2nd PCE to the 2nd OFC send first message.
Above-mentioned second path segment information is carried in first message, it is preferable that the second path segment information can include：LSP is in the 2nd OFC
The path segment information in place domain, or the route segment letter in LSP domains where domain and the 2nd OFC downstream OFC where the 2nd OFC
Breath.For example, [S5-S7-S9-S11-S13] as shown in Figure 3.2nd PCE issues path segment information, instruction second to the 2nd OFC
The route segment in AS domains where OFC configures the 2nd OFC.
For mode two, when the first OFC is to the 2nd OFC transmission first messages, the first OFC directly can be sent out to the 2nd OFC
Send first message.Preferably, the first OFC can send above-mentioned first message by PCEP agreements to the 2nd OFC, in first message
Carry above-mentioned second routing information, it is preferable that the second path segment information can include：The complete path segment informations of LSP, or
The path segment information in LSP domains where domain and the 2nd OFC downstream OFC where the 2nd OFC.Message occupancy is sent in order to reduce
Internet resources, can only carry the road in LSP domains where domain and the 2nd OFC downstream OFC where the 2nd OFC in the message
Footpath segment information.
In embodiments of the present invention, above-mentioned first message also carries route segment configuration instruction, wherein, route segment configuration refers to
Show for indicating that the 2nd OFC configures the route segment in the 2nd OFC places domain.In actual applications, as shown in figure 8, can be in RP
（Request Parameters）Object, in it is new define a flag bit such as S (Segment), to illustrate only to configure this domain
Interior path.If RP objects carry within the message, flag bit S can be carried；If RP objects do not carry, can pass through
Other modes, such as Notification objects, to illustrate that the message is used to indicate that OFC2 issues configuration path in its domain
Interchanger.The form of Notification objects defined in Flag as shown in figure 8, can indicate it is requirement by a S flag bit
OFC2 configures corresponding route segment, or the information is reflected by NT and NV combination.
After first OFC sends first message to the 2nd OFC, the 2nd OFC can be according to the second route segment information configuration the
When the route segment in domain does not include the information for the route segment not configured in the second path segment information where two OFC, i.e. the 2nd OFC
The 3rd message can also be sent to the first OFC for OFC corresponding to last route segment in LSP, the 2nd OFC, wherein, the 3rd disappears
Cease for indicating that LSP configurations are completed.For example, as shown in figure 3, when PCE3 receives the message of OFC3 configuration completions（Can be PCNtf
Either PCRpt or other message）Afterwards, PCRep message can be sent to PCE2.Similarly, match somebody with somebody when PCE2 receives from OFC2
PCE1 transmission PCRep message is given after putting the message of completion.Notify that OFC1 is other after PCE1 receives the PCRep message from PCE2
The route segment configuration successful in domain, OFC1 are combined and successful state are locally configured, and can import data flow.
The transmission method of the path segment information of embodiment of the present invention is described below by preferred embodiment.
Preferred embodiment one
Exemplified by this preferred embodiment needs the route segment that configures between OFC by PCE transfers, to embodiment of the present invention
The transmission method of path segment information be described.
As shown in figure 3, the BRPC flows defined according to RFC5441, after PCE1 gets complete route segment, example
Such as, the TE-LSP shown in Fig. 4 [S1-S3-S5-S7-S9-S11-S13], PCE1 issue route segment [S1-S3] in this domain to
OFC1, OFC1 are handed down to S1 and S3 nodes after being converted into Openflow agreements, configure the route segment in this domain.
In order to illustrate that route segment that PCE1 is handed down to OFC1 is only the route segment in this domain, as shown in figure 8, can be in RP
（Request Parameters）Object, in newly define a flag bit such as S（Segment）, to illustrate only to configure this domain
Interior path.Preferably, in view of be OFC1 send PCRep message to PCE1, PCE1 issues the message of the route segment in this domain
For PCRep message.
Further, PCE1 sends PCRep message to PCE2, carries the route segment to be configured within the message, such as such as
[S5-S7-S9-S11-S13] shown in Fig. 3.In the PCRep message, the END POINTS objects of head and the tail node are identified（It is fixed
Justice may be referred to RFC5440 and manuscript http://tools.ietf.org/html/draft-ietf-pce-gmpls-pcep-
extensions-05）, keep constant；In RP objects with reference to one request of END POINTS objects unique mark
Request-ID-number becomes constant.Preferably, a flag bit, such as C can be newly defined in its flag bit
（Configuration）, it is to indicate that it issues route segment to the configuration network element in its domain to indicate the request, such as OFC etc., configuration
Route segment in the domain.In addition, the route segment mark can also based on the ERO sequences used in RFC5441, wherein it is possible to
Path Key defined in embedded RFC5520.
Preferably, in a preferred embodiment of the invention, it is that PCE1 sends PCRep message to PCE2, in actual applications, on
The content stated can also be based on PCNtf（Notification）Message, or the message of other new definition（For example, manuscript
http:PCRpt message defined in //tools.ietf.org/html/draft-ietf-pce-stateful-pce-00
Deng）.
After PCE2 receives the path computing request message, the flag bit C in RP objects judges to need to issue this domain
Interior route segment（For example, [S5-S7]）To OFC2, PCE2 can issue route segment [S5-S7] to the configuration network element in its domain（Example
Such as OFC2）.If the carrier for carrying the agreement is PCEP agreements, in view of OFC2 does not send PCRep message to PCE2, issue
The message of route segment can be PCNtf message, naturally it is also possible to be the message of other new definition, such as PCRep or other disappear
Breath.
If RP objects carry within the message, flag bit S can be carried；If RP objects do not carry, can pass through
Other modes, such as Notification objects, to illustrate that the message is used to indicate that OFC2 issues configuration path in its domain
Interchanger.The form of Notification objects defined in Flag as shown in figure 8, can indicate it is requirement by a S flag bit
OFC2 configures corresponding route segment, or the information is reflected by NT and NV combination.
Further, PCE2 can send a request message to PCE3, indicate the route segment to be configured within the message, such as
[S9-S11-S13].In the message（Such as PCReq）In, identify END POINTS objects and the combination of head and the tail node
The RP objects of one request of ENDPOINTS objects unique mark are sent to being consistent for PCE2 with PCE1；The mark of the route segment
Knowledge can be based on the ERO sequences used in RFC5441, wherein the Path Key defined in RFC5520 can be embedded in.
Preferably, in a preferred embodiment of the invention, it is that PCE2 sends PCRep message to PCE3, certainly above-mentioned content
PCNtf can also be based on（Notification）Message, or the message of other new definition（For example, manuscript http://
PCRpt message defined in tools.ietf.org/html/draft-ietf-pce-stateful-pce-00 etc.）.
After PCE3 receives the request message, the C flag bits in RP objects, its responsible route segment [S9- is issued
S11-S13] give OFC3.Similarly, if the protocol bearer between PCE3 and OFC3 is PCEP agreements, in view of OFC3 is not sent
PCRep message is to PCE3, thus message here is preferably PCNtf message either PCRep message or other message.If
RP objects carry within the message, can carry flag bit S；If RP objects do not carry, can by other means, such as
Notification objects, to illustrate that the message is used to indicate that OFC2 issues configuration path to the interchanger in its domain.
In view of PCE3 is last PCE in PCE computational fields sequences, thus when PCE3 receives disappearing for OFC3 configuration completions
Breath（Can be PCNtf either PCRpt or other message）Afterwards, PCRep message can be sent to PCE2.Similarly, PCE2 is worked as
PCE1 transmission PCRep message is given after receiving the message completed from OFC2 configurations.When PCE1 receives the PCRep message from PCE2
The route segment configuration successful in the other domains of OFC1 is notified afterwards, and OFC1 is combined and successful state is locally configured, and can import data flow.
Preferred embodiment two
Exemplified by this preferred embodiment needs the route segment that configures between OFC by PCEP protocol forwards, to of the invention real
The transmission method for applying the path segment information of example is described.
As shown in figure 5, the BRPC flows defined according to RFC5441, after PCE1 gets complete route segment, example
Such as, TE-LSP as shown in Figure 5 [S1-S3-S5-S7-S9-S11-S13].PCE1 can issue complete route segment [S1-S3-
S5-S7-S9-S11-S13] give OFC1, OFC1 to be handed down to after the route segment [S1-S3] in this domain is converted into Openflow agreements
S1 and S3 nodes, configure the route segment in this domain.In view of be OFC1 send PCRep message to PCE1, it is thus preferable to which this disappears
Breath can be PCRep message.
Further, OFC1 can be sent PCNtf message to OFC2 either PCRpt message or it is other newly define disappear
Breath, carries remaining route segment, such as [S5-S7-S9-S11-S13] in the message, and instruction OFC2 configures corresponding route segment.
If RP objects are carried within the message, it is necessary to carry flag bit C；If RP objects are not carried, it is necessary to by otherwise
Illustrate that the message is indicating that OFC2 issues configuration path to the interchanger in its domain such as Notification objects.
The form of Notificaion objects is as shown in figure 8, it is requirement OFC2 configurations that a C flag bit defined in Flag, which indicates,
Corresponding route segment, or the information such as reflect in addition, the mark of the route segment still can be with base by NT and NV combination
The ERO sequences used in RFC5441, wherein the Path Key defined in RFC5520 can be embedded in.
After OFC2 receives above-mentioned PCNtf message, the flag bit C in RP objects or Notification objects sentences
It is disconnected to need to configure the route segment in this domain, and remaining route segment is forwarded to OFC3.Similarly, OFC2 is the route segment in this domain
[S5-S7] is handed down to S5 and S7 nodes after being converted into Openflow agreements, configures the route segment in this domain.
Further, OFC2 can be sent PCNtf message to OFC3 either PCRpt message or it is other newly define disappear
Breath, carries remaining route segment, such as [S9-S11-S13] in the message, and instruction OFC3 configures corresponding route segment.If RP
Object carries within the message, can carry flag bit C；, can be by otherwise such as if RP objects do not carry
Notification objects illustrate that the message is to indicate that OFC2 issues configuration path to the interchanger in its domain.
The form of Notificaion objects is as shown in figure 8, it is requirement OFC3 configurations that a C flag bit defined in Flag, which indicates,
Corresponding route segment, or the information are reflected by NT and NV combination.In addition, the mark of the route segment still can be with base
The ERO sequences used in RFC5441, wherein the Path Key defined in RFC5520 can be embedded in.
After OFC3 receives the PCNtf message, the flag bit C in RP objects or Notification objects judges
Need to configure the route segment in this domain.Similarly, OFC3 can be converted into the route segment [S9-S11-S13] in this domain
Node S9, S11 and S13 are handed down to after Openflow agreements, configures the route segment in this domain.In embodiments of the present invention, reflect
It is that after the completion of its configuration, OFC3 can send message in last AS domain in OFC3（Can be PCNtf or PCRpt or
Person's others message）To OFC2, instruction OFC3 configurations are completed.OFC2 receives the message that OFC3 configurations are completed and locally also configured
OFC1 is sent messages to after success.OFC1 receives the message and judged after being locally also arranged to work(, and data flow can is on LSP
Transmission.
Preferred embodiment three
This preferred embodiment is so that OFC and PCE are on same physical entity as an example, to the route segment of embodiment of the present invention
The transmission method of information is described.
In the preferred embodiment, when the computational algorithm in path and uncomplicated, or the traffic engineering data needed are calculated
When storehouse is little, OFC and PCE can be on a physical entity, to be interacted between the two modules by internal interface.
As shown in fig. 6, the BRPC flows defined according to RFC5441, when PCE1/OFC1 get complete route segment it
Afterwards, for example, TE-LSP [S1-S3-S5-S7-S9-S11-S13] shown in Fig. 6.PCE1/OFC1 passes through Openflow protocol configurations
Route segment [S1-S3] in this domain.
Further, PCE1/OFC1 sends PCNtf message to PCE2/OFC2（Preferably, message carrier here also may be used
To be PCRep message, or the message that PCRpt message either newly defines, in embodiments of the present invention, only with PCNtf message
Exemplified by illustrate, the content for carrying him is identical）, the route segment to be configured, such as [S5-S7- are indicated within the message
S9-S11-S13], instruction OFC2/PCE2 configures corresponding route segment.
If RP objects carry within the message, flag bit C can be carried；If RP objects do not carry, can pass through
Other modes, such as Notification objects, configuration path is issued to it to illustrate that the message is indicated for OFC2/PCE2
Interchanger in domain.The form of Notification objects defined in Flag as shown in figure 8, a C flag bit can indicate
It is that requirement OFC2/PCE2 configures corresponding route segment, or the information can also be reflected by NT and NV combination.Separately
Outside, the mark of the route segment is also based on the ERO sequences used in RFC5441, wherein it is possible to defined in embedded RFC5520
Path Key.
After OFC2/PCE2 receives above-mentioned PCNtf message, according to the mark in RP objects or Notification objects
Position C judges to need to configure the route segment in this domain, and forwards remaining route segment to OFC3/PCE3.Further, OFC2/
PCE2 can send PCNtf message to OFC3/PCE3, and remaining route segment is carried in PCNtf message（Such as [S9-S11-
S13]）, the corresponding route segment of instruction OFC3/PCE3 configurations.If RP objects carry within the message, flag bit C can be carried；
, can by other means if RP objects do not carry, such as Notification objects, to illustrate that the message is to be used to refer to
Show that OFC3/PCE3 issues configuration path to the interchanger in its domain.The forms of Notification objects is as shown in figure 8, can be with
It is that requirement OFC3/PCE3 configures corresponding route segment that a C flag bit defined in Flag, which indicates, or the information by NT and
NV combination the such as reflects in addition, the mark of the route segment is also based on the ERO sequences used in RFC5441, wherein, can
To be embedded in the Path Key defined in RFC5520.
After OFC3/PCE3 receives above-mentioned PCNtf message, according to the mark in RP objects or Notification objects
Position C judges to need to configure the route segment in this domain.OFC3/PCE3 is converted into the route segment [S9-S11-S13] in this domain
Node S9, S11 and S13 are handed down to after Openflow agreements, configures the route segment in this domain.In view of OFC3/PCE3 is most
The latter domain, after the completion of its configuration, send message（Can be PCNtf either PCRpt or other message）To OFC2/
PCE2；After OFC2/PCE2 receives the message that OFC3/PCE3 configurations are completed and is locally also arranged to work(, OFC1/ is sent messages to
PCE1.OFC1/PCE1 receives the message and judged after being locally also arranged to work(, and data flow can is transmitted on LSP.
According to embodiments of the present invention, a kind of transfer device of path segment information is additionally provided, in the first OFC, to
Realize the above method of the embodiment of the present invention.
Fig. 9 is the structured flowchart of the transfer device of path segment information according to embodiments of the present invention, as shown in figure 9, the dress
Putting mainly includes：Acquisition module 10, configuration module 20 and sending module 30.Wherein, acquisition module 10, for obtaining first path
Segment information, wherein, first path segment information includes the path segment information in the LSP domains where the first OFC being currently configured；Configure mould
Block 20, it is coupled with acquisition module 10, the route segment for domain where configuring the first OFC according to first path segment information；Send
Module 30, it is coupled with configuration module 20, the first message of the second path segment information is carried for being sent to the 2nd OFC, its
In, the 2nd OFC is the first OFC downstream OFC, the path segment information in LSP domains where the 2nd OFC described in the second routing information,
Or the path segment information in LSP domains where domain and the 2nd OFC downstream OFC where the 2nd OFC.
By the embodiment of the present invention, the first OFC acquisition module 10 obtains LSP first path segment information, by configuration mould
The route segment in AS domains where block 20 configures the first OFC according to first path segment information, and from sending module 30 to the first OFC under
The OFC of trip sends first message, and LSP the second path segment information is carried in first message, realizes and LSP is transmitted on OFC
Path segment information so that the OFC for belonging to not same area on LSP knows the information for the route segment that needs configure, and completes each roads of LSP
The configuration of footpath section.
In embodiments of the present invention, following three kinds of modes bang path segment information can be passed through between OFC：Mode one, OFC
Between pass through PCE transfers path segment information（As shown in Figure 3）；Mode two, pass through PCEP protocol forwards path segment information between OFC
（As shown in Figure 5）；Mode three, OFC and PCE transmit route segment information on same physical entity（As shown in Figure 6）.Divide below
The other preferred embodiment to above-mentioned three kinds of modes is described.
In a preferred embodiment of the embodiment of the present invention, acquisition module 10 obtains LSP first path segment information
When, first path information can be obtained from PCE or the first OFC upstream OFC corresponding to the first OFC.In mode one, mould is obtained
What block 10 was got is the information of the route segment of the AS where the first OFC, for example, OFC1 as shown in Figure 3 is got from PCE1
Path segment information can be AS1 path segment information（For example, [S1, S3]）.In mode two, if the first OFC is LSP
OFC corresponding to one route segment, the first path segment information record that PCE corresponding to acquisition module 10 from the first OFC is got have
The complete path segment informations of LSP, or the information of LSP route segments in domain where the first OFC, or LSP where the first OFC domain with
And the first OFC downstream OFC where domain path segment information.
Further, acquisition module 10 from the first PCE obtain first path segment information when, the first OFC can receive first
The second message that PCE is sent, wherein, the information that the second message carries includes first path segment information, and is obtained from the second message
Take first path segment information.Therefore, in a preferred embodiment of the embodiment of the present invention, as shown in Figure 10, acquisition module
10 can include：Receiving unit 102, the second message sent for receiving the first PCE, wherein, the information that the second message carries
Including first path segment information；Acquiring unit 104, it is coupled with receiving unit 102, for obtaining the first via from the second message
Footpath segment information.Preferably, the information that first message or the second message carry can also include：Route segment configuration instruction, wherein, road
Footpath section configuration instruction is used for the route segment in domain where indicating the first OFC of the first OFC configurations, or the 2nd OFC of instruction configures the 2nd OFC
The route segment in place domain.
For example, corresponding to first route segment in each route segment that the first PCE is LSP during PCE, the first PCE can be with
It is determined that after LSP optimal path, the second message is sent to the first OFC（For example, PCRep message）, the first OFC receiving unit
102 receive the second message that the first PCE is sent, and first path segment information is obtained from the second message by acquiring unit 104.
For mode one, the first OFC to the 2nd OFC send first message when, acquisition module 10 can be by the first OFC pairs
The first PCE answered sends first message to the 2nd PCE corresponding to the 2nd OFC, and sending first to the 2nd OFC by the 2nd PCE disappears
Breath.Above-mentioned second path segment information is carried in first message, it is preferable that the second routing information can include first path information
The information of the route segment not configured of middle record, or the complete path segment informations of LSP.For example, [S5-S7-S9- as shown in Figure 3
S11-S13].2nd PCE issues path segment information to the 2nd OFC, the path in AS domains where the 2nd OFC of instruction configures the 2nd OFC
Section.
For mode two, sending module 30 to the 2nd OFC send first message when, directly can send the to the 2nd OFC
One message.Preferably, sending module 30 can send above-mentioned first message by PCEP to the 2nd OFC, be carried in first message
There is above-mentioned second routing information, it is preferable that the second path segment information can also include：The route segment in LSP domains where the 2nd OFC
Information, or the path segment information in LSP domains where domain and the 2nd OFC downstream OFC where the 2nd OFC.Sent to reduce
The Internet resources that message takes, the current route segment not configured recorded in the second path segment information can be only carried in the message
Information.
In embodiments of the present invention, above-mentioned first message also carries route segment configuration instruction, wherein, route segment configuration refers to
Show for indicating that OFC configures the route segment in OFC places domain.In actual applications, can in RP objects, in new define a mark
Will position such as S, to illustrate only to configure the path in this domain.If RP objects carry within the message, flag bit can be carried
S；, can by other means if RP objects do not carry, such as Notification objects, to illustrate that the message is used to refer to
Show that OFC2 issues configuration path to the interchanger in its domain.The form of Notification objects is as shown in figure 8, can be in Flag
Defined in a S flag bit indicate it is that requirement OFC2 configures corresponding route segment, or the information by NT and NV combination come
Reflection etc..
After first OFC sends first message to the 2nd OFC, the 2nd OFC can be according to the second route segment information configuration the
When the route segment in AS domains does not include the information for the route segment not configured in the second path segment information where two OFC, i.e., second
OFC is OFC corresponding to last route segment in LSP, and the 2nd OFC can also send the 3rd message to the first OFC, wherein, the
Three message are used to indicate that LSP configurations are completed.For example, as shown in figure 3, when PCE3 receives the message of OFC3 configuration completions（Can be
PCNtf either PCRpt or other message）Afterwards, PCRep message can be sent to PCE2.Similarly, come from when PCE2 is received
After the message that OFC2 configurations are completed PCRep message is sent to PCE1.Notified after PCE1 receives the PCRep message from PCE2
The route segment configuration successful in the other domains of OFC1, OFC1 are combined and successful state are locally configured, and can import data flow.
As can be seen from the above description, the present invention realizes following technique effect：First OFC obtains the first of LSP
Path segment information, the route segment in AS domains where configuring the first OFC according to first path segment information, and to the first OFC downstream OFC
First message is sent, LSP the second path segment information is carried in first message, realizes the route segment that LSP is transmitted on OFC
Information so that the OFC for belonging to not same area on LSP knows the information for the route segment that needs configure, so as to complete to LSP differences path
The configuration of section, rapid deployment LSP.
Obviously, those skilled in the art should be understood that above-mentioned each module of the invention or each step can be with general
Computing device realize that they can be concentrated on single computing device, or be distributed in multiple computing devices and formed
Network on, alternatively, they can be realized with the program code that computing device can perform, it is thus possible to they are stored
Performed in the storage device by computing device, and in some cases, can be with different from shown in order execution herein
The step of going out or describing, they are either fabricated to each integrated circuit modules respectively or by multiple modules in them or
Step is fabricated to single integrated circuit module to realize.So, the present invention is not restricted to any specific hardware and software combination.
The preferred embodiments of the present invention are the foregoing is only, are not intended to limit the invention, for the skill of this area
For art personnel, the present invention can have various modifications and variations.Within the spirit and principles of the invention, that is made any repaiies
Change, equivalent substitution, improvement etc., should be included in the scope of the protection.
Claims (17)
- A kind of 1. transmission method of path segment information, it is characterised in that including：First Openflow controllers OFC obtains first path segment information, wherein, the first path segment information includes currently matching somebody with somebody The path segment information in the label switching path LSP put domain where the first OFC；The route segment in domain where first OFC configures the first OFC according to the first path segment information；First OFC sends the first message for carrying the second path segment information to the 2nd OFC, wherein, the 2nd OFC is The downstream OFC of first OFC, the route segment that second routing information includes LSP domains where the 2nd OFC are believed Breath, or the path segment information in LSP domains where domain and the 2nd OFC downstream OFC where the 2nd OFC.
- 2. according to the method for claim 1, it is characterised in that the first OFC obtains first path segment information, including：First OFC obtains the first path section from the OFC of first path computing unit PCE or described first upstream OFC Information, wherein, the first PCE is PCE corresponding to the first OFC.
- 3. according to the method for claim 2, it is characterised in that the first OFC obtains described first from the first PCE Path segment information, including：First OFC receives the second message that the first PCE is sent, wherein, the information that second message carries includes The first path segment information；First OFC obtains the first path segment information from second message.
- 4. according to the method for claim 3, it is characterised in that the information that second message carries also includes：Route segment Instruction is configured, wherein, the route segment configuration instruction is used for the road in domain where indicating the first OFC configurations the first OFC Footpath section.
- 5. according to the method for claim 2, it is characterised in that the first path segment information record has the LSP complete Path segment information, or the information of LSP route segments in domain where the first OFC, or the LSP is described first The path segment information in domain where domain and the first OFC downstream OFC where OFC.
- 6. according to the method for claim 1, it is characterised in that the first OFC sends first message, bag to the 2nd OFC Include：The first message is sent by the 2nd PCE corresponding to the first PCE to the 2nd OFC corresponding to the first OFC；The first message is sent to the 2nd OFC by the 2nd PCE.
- 7. according to the method for claim 6, it is characterised in that the second route segment information includes：The LSP is described The path segment information in domain where 2nd OFC, or the LSP domain and downstream of the 2nd OFC where the 2nd OFC The path segment information in domain where OFC.
- 8. according to the method for claim 1, it is characterised in that the first OFC sends first message, bag to the 2nd OFC Include：First OFC directly sends the first message to the 2nd OFC.
- 9. according to the method for claim 8, it is characterised in that the first OFC is directly to described in the 2nd OFC transmissions First message, including：The first OFC passage paths computing unit communication protocol PCEP sends the first message to the 2nd OFC.
- 10. according to the method for claim 8, it is characterised in that the second route segment information includes：The LSP is in institute The path segment information in domain where domain and the 2nd OFC downstream OFC where stating the 2nd OFC.
- 11. method according to any one of claim 1 to 10, it is characterised in that the first message or the second message Route segment configuration instruction is also carried, wherein, the route segment that is carried in first message configuration instruction, for indicating described the The route segment in domain where two OFC configure the 2nd OFC, the route segment configuration instruction that second message carries, for indicating The route segment in domain where first OFC configures the first OFC.
- 12. according to the method for claim 1, it is characterised in thatAfter first OFC sends first message to the 2nd OFC, in addition to：2nd OFC is according to second route segment The route segment in domain where 2nd OFC described in information configuration；When not including the information for the route segment not configured in the segment information of second path, in addition to：2nd OFC is to institute State the first OFC and send the 3rd message, wherein, the 3rd message carries the information completed for indicating the LSP configurations.
- A kind of 13. transfer device of path segment information, in the first Openflow controllers OFC, it is characterised in that including：Acquisition module, for obtaining first path segment information, wherein, the first path segment information includes the label being currently configured The path segment information in switching path LSP domains where the first OFC；Configuration module, the route segment for domain where configuring the first OFC according to the first path segment information；Sending module, the first message of the second path segment information is carried for being sent to the 2nd OFC, wherein, the 2nd OFC For the downstream OFC of the first OFC, second routing information includes the route segment in LSP domains where the 2nd OFC The path segment information in domain where information and the 2nd OFC downstream OFC.
- 14. device according to claim 13, it is characterised in that the acquisition module obtains described in such a way One path segment information：The acquisition module obtains the first path section from the OFC of first path computing unit PCE or described first upstream OFC Information, wherein, the first PCE is PCE corresponding to the first OFC.
- 15. device according to claim 14, it is characterised in that the acquisition module includes：Receiving unit, the second message sent for receiving the first PCE, wherein, the packet that second message carries Include the first path segment information；Acquiring unit, for obtaining the first path segment information from second message.
- 16. the device according to any one of claim 13 to 15, it is characterised in that the sending module is according to lower section Formula sends the first message to the 2nd OFC：The first message is sent by the 2nd PCE corresponding to the first PCE to the 2nd OFC corresponding to the first OFC；The first message is sent to the 2nd OFC by the 2nd PCE.
- 17. the device according to any one of claim 13 to 15, it is characterised in that the sending module is according to lower section Formula sends the first message to the 2nd OFC：The sending module directly sends the first message to the 2nd OFC.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210256058.3A CN103581017B (en) | 2012-07-23 | The transmission method and device of path segment information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210256058.3A CN103581017B (en) | 2012-07-23 | The transmission method and device of path segment information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103581017A CN103581017A (en) | 2014-02-12 |
| CN103581017B true CN103581017B (en) | 2018-02-09 |
Family
ID=
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101335692A (en) * | 2007-06-27 | 2008-12-31 | 华为技术有限公司 | Method for negotiating security capability between PCC and PCE and network system thereof |
| CN101552717A (en) * | 2008-04-03 | 2009-10-07 | 华为技术有限公司 | Method and device for requesting computing path in multiple-domain networks |
| CN101931583A (en) * | 2009-06-18 | 2010-12-29 | 中兴通讯股份有限公司 | Domain routing information generation method and device, path computation method and device |
| CN101945033A (en) * | 2009-07-08 | 2011-01-12 | 中兴通讯股份有限公司 | Method, device and system for merging/dividing traffic engineering domain |
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101335692A (en) * | 2007-06-27 | 2008-12-31 | 华为技术有限公司 | Method for negotiating security capability between PCC and PCE and network system thereof |
| CN101552717A (en) * | 2008-04-03 | 2009-10-07 | 华为技术有限公司 | Method and device for requesting computing path in multiple-domain networks |
| CN101931583A (en) * | 2009-06-18 | 2010-12-29 | 中兴通讯股份有限公司 | Domain routing information generation method and device, path computation method and device |
| CN101945033A (en) * | 2009-07-08 | 2011-01-12 | 中兴通讯股份有限公司 | Method, device and system for merging/dividing traffic engineering domain |
Non-Patent Citations (2)
| Title |
|---|
| A Path Computation Element (PCE)-Based Architecture;J. Ash等;《IETF-rfc4655》;20060830;全文 * |
| ath Computation Element (PCE) Communication Protocol (PCEP);JP. Vasseur等;《IETF-RFC5440》;20090331;全文 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3643022B1 (en) | A method for establishing segment routing for ipv6 tunnel | |
| RU2541940C2 (en) | Method of applying service instance to mpls network (versions) and mpls network | |
| US7684420B2 (en) | Method for implementing cross-domain constraint routing | |
| CN101228739B (en) | Method, equipment and system of dynamic enforcement of MPLS-TE inter-domain policy and QoS | |
| CN101133408B (en) | Computation of a shortest inter-domain te-lsp across a set of autonomous systems | |
| EP1863235B1 (en) | Method and system for multi-domain route computation | |
| EP3503478B1 (en) | Method of establishing relationships between sets of label switched paths and virtual networks | |
| CN101606341B (en) | Technique for efficiently routing ip traffic on CE-CE paths across a provider network | |
| CN101288266B (en) | Dynamic retrieval method and system of engineering label switching routing information among autonomous systems | |
| CN107637031A (en) | Path-calculating element central controller (PCECC) for Network | |
| US9571381B2 (en) | System and method for inter-domain RSVP-TE LSP load balancing | |
| EP3131239B1 (en) | Method and apparatus for path establishment | |
| WO2014081766A1 (en) | Bandwidth on-demand services in multiple layer networks | |
| CN105871722A (en) | Tag structure and tag message forwarding method and device | |
| WO2009092246A1 (en) | Path selection method and network system, path computation element | |
| JP2009538027A5 (en) | ||
| CN108574628B (en) | Method, device and system for establishing domain-level topology | |
| US20060203747A1 (en) | Network topology systems and methods | |
| CN101878623A (en) | Enhancing routing optimality in IP networks requiring path establishment | |
| CN110099002B (en) | Path calculation method and device | |
| CN103117925A (en) | Processing method and processing device for data message forward | |
| WO2015035616A1 (en) | Method and device for cross-network communications | |
| JP2008252439A (en) | Communication network system | |
| JP2008193395A (en) | Two-way path setting method, and communication system and node device for achieving it | |
| WO2015024440A1 (en) | Method and system of obtaining link overhead value of ip link |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20180209 Termination date: 20200723 |