US011362940B2

United States Patent

(12) Peng ( 10) Patent No.: US 11,362,940 B2
et al. (45 ) Date of Patent : Jun . 14 , 2022
( 54 ) METHOD AND APPARATUS FOR ( 52 ) U.S. CI.
DETERMINING IDENTIFICATION CPC H04L 45/42 (2013.01 ) ; H04L 12/4633
INFORMATION ABOUT CROSS -DOMAIN (2013.01 ) ; H04L 41/12 ( 2013.01 ) ;
PATH , AND STORAGE MEDIUM (Continued)
( 58 ) Field of Classification Search
( 71 ) Applicant: XI'AN ZHONGXING NEW CPC HO4L 45/42 ; H04L 45/02 ; HO4L 45/507 ;
SOFTWARE CO . , LTD ., Shenzhen H04L 45/26 ; H04L 45/04 ; HO4L 45/24 ;
( CN ) (Continued )
( 72 ) Inventors: Shaofu Peng , Shenzhen (CN) ; Feicai ( 56 ) References Cited
Jin , Shenzhen ( CN) ; Shencai Zhu , U.S. PATENT DOCUMENTS
Shenzhen (CN )
2009/0245253 A1 * 10/2009 Chen HO4L 45/42
( 73 ) Assignee : XI'AN ZHONGXING NEW 370/390
SOFTWARE CO . , LTD ., Shaanxi 2010/0208733 Al 8/2010 Zhao
(CN ) ( Continued )
( * ) Notice: Subject to any disclaimer, the term of this FOREIGN PATENT DOCUMENTS
patent is extended or adjusted under 35 CN 101908998 A 12/2010
U.S.C. 154 ( b ) by 152 days . CN 101931583 A 12/2010
(21 ) Appl. No.: 16 /623,613 (Continued )
(22 ) PCT Filed : May 29 , 2018 OTHER PUBLICATIONS
( 86) PCT No .: PCT/CN2018/ 088880 International Search Report for corresponding application PCT /
CN2018 /088880 filed May 29 , 2018 dated Aug. 20 , 2018 .
$ 371 (c ) ( 1 ) , (Continued )
(2 ) Date : Dec. 17 , 2019
Primary Examiner — Joshua Kading
( 87 ) PCT Pub . No .: WO2019 /007166 (74 ) Attorney, Agent, or Firm Cantor Colburn LLP
PCT Pub . Date : Jan. 10 , 2019
( 57 ) ABSTRACT
( 65 ) Prior Publication Data Provided are a method and apparatus for determining iden
US 2020/0213223 A1 Jul . 2 , 2020 tification information about a cross -domain path , and a
storage medium . The method includes: receiving a path
( 30 ) Foreign Application Priority Data computation request from a first child path computation
element (PCE ) , wherein the path computation request car
Jul. 3 , 2017 ( CN) 201710532649.1 ries a compression identifier for identifying compression of
path segments and a path set -up type (PST ); after identifi
( 51 ) Int . Ci . cation information about a path from a source node to a
H04L 45/42 ( 2022.01 ) destination node is acquired, instructing, according to the
H04L 12/46 ( 2006.01 ) compression identifier and the PST, each of sub - PCEs
(Continued ) (Continued )
Send a path computation request to a parent path computation request (PCE ) , where
the path compulation request is used for making a request to acquire a path from a
source node to a destination node, the source node and the destination node are S202
located in different domains , the path includes one or more path segments , and the
path computation request carries a compression identilier lor identilying compression
of the one or more paih segments, and a path setup lype (PST )

Keceive a creation message from the parent PCE , where the creation message is sent S204
by the parent PCE according to the compression identifier and the PST

Compress identification information about a path segment according to the creation $ 206
message

Retum the compressed identification information about the one or more path segments S208
to the parent PCE
 US 11,362,940 B2
Page 2

corresponding to the one or more path segments to compress (56) References Cited
identification information about a respective of the one U.S. PATENT DOCUMENTS
or more path segments; and receiving the compressed iden
tification information about each path segment. 2012/0213224 A1 ** 8/2012 Chen H04L 45/44
370/390
2012/0246625 Al 9/2012 Puthuff
20 Claims , 4 Drawing Sheets 2012/0308225 A1 * 12/2012 Long H04J 14/0267
398/13
2014/0369356 A1 12/2014 Bryant
2015/0163125 A1 * 6/2015 Caviglia HO4L 45/26
370/254
2016/0105358 Al 4/2016 Kannan
( 51 ) Int . Ci . 2016/0105958 A1 4/2016 Kannan
H04L 47/70 ( 2022.01) 2016/0359735 A1 * 12/2016 Zhao HO4L 45/028
2017/0163443 A1 * 6/2017 Chen HO4L 45/124
H04L 45/50 ( 2022.01 ) 2019/0349286 A1 * 11/2019 Bruno HO4L 45/04
H04L 45/02 ( 2022.01 )
H04L 41/12 ( 2022.01 ) FOREIGN PATENT DOCUMENTS
H04L 45/00 ( 2022.01) CN 102742224 A 10/2012
H04L 45/24 ( 2022.01) CN 102970222 B 8/2015
H04L 47/72 ( 2022.01 ) WO 2011057154 A1 5/2011
(52) U.S. Ci . OTHER PUBLICATIONS
CPC H04L 45/02 ( 2013.01 ) ; H04L 45/04
(2013.01 ) ; H04L 45/24 ( 2013.01 ) ; H04L 45/26 European Search Report for corresponding application EP18 82
( 2013.01 ) ; H04L 45/507 ( 2013.01 ) ; H04L 7949 : Report dated Feb. 16 , 2021 .
47/72 ( 2013.01 ) ; H04L 47/825 (2013.01 ) Chinese Office Action for corresponding application 201710532649 .
1 ; Report dated Aug. 18 , 2021 .
( 58 ) Field of Classification Search Chinese Search Report for corresponding application 201710532649 .
CPC .... HO4L 45/50 ; H04L 41/12 ; H04L 12/4633 ; 1 ; Report dated Aug. 13 , 2021 .
HO4L 47/72 ; HO4L 47/825 ; HO4L 477821
See application file for complete search history . * cited by examiner
U.S. Patent Jun . 14 , 2022 Sheet 1 of 4 US 11,362,940 B2

Receive a path computation request from a first child path computation element
( PCE ) , where the path computation request is used for making a request to acquire a
path from a source node to a destination node , the source node and the destination
node are located in different domains , the path includes one or more path segments , S102
and the path computation request carries a compression identifier for identifying
compression of the one or more path segments , and a path setup type ( PST )

After identification information about the path from the source node to the destination
node is acquired , instruct, according to the compression identifier and the PST , each S104
of sub - PCEs corresponding to the one or more path segments to compress
identification information about a respective one of the one or more path segments

Receive the compressed identification information about the respective one of the one
or more path segmentsinformation about the one or more path segments returned by
the each of sub - PCEs corresponding to the one or more path segments , and according S106
to the identification information about the path , combine the compressed identification
information about the one or more path segments into compressed identification
information about the path

FIG . 1
Send a path computation request to a parent path computation request ( PCE ) , where
the path computation request is used for making a request to acquire a path from a
source node to aa destination node , the source node and the destination node are S202
located in different domains , the path includes one or more path segments , and the
path computation request carries a compression identifier for identifying compression
of the one or more path segments , and a path setup type ( PST )

Receive a creation message from the parent PCE , where the creation message is sent S204
by the parent PCE according to the compression identifier and the PST

Compress identification information about a path segment according to the creation S206
message

Return the compressed identification information about the one or more path segments S208
to the parent PCE

FIG . 2
U.S. Patent Jun . 14. 2022 Sheet 2 of 4 US 11.362,940 B2

1 3
? 1234567gg123456391.23456 ? ? 91
? ???? - + - + ?????? ?? ? + - + - + - + - + - + - + - + - +
Flags ICF MIDIPIET SELPT1
+ - + -+ - + - + - + - + - + - + 1 + 1 + - + -+ - + -+ -+ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + 1 + 1 *
Request - ID - nüiber
- +- +- + - + - +- +- +- +- +- + - +- +- + -+ - +- +- + - +- + - + - + -+ - + - ?? ?? +- + -+ -+- +i
1 |
Optional TLVS
1
? + - + - + - + - + - + -+ - + - + - + - + - + - + - + - + - + - + - + -+ - + -+ - + - + - + - + - + + - + - + - ? ??

FIG . 3
.0 1 2 3
0 1 2 3 4 5 6 78 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+ ?? ? ??? ?? ? ????
· ?, ? ++ ?? + - + - + - + - + - + - + - + ?? ?
Type Length
??? ...
+ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +- + - + - + - + .

?
+

.1 Reserved PST
? - + - + - + - + - + + - + - + - + - + - + - + - + - + - + - + - + - + - + + - + - + - + - + - + - + - + - + -- ***

FIG . 4
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 ?
+ - + ? ?? ? ???? ? :?? + - +- + - + ?? ? ?? ?
1 Type Length
+ - + - + - + - +Binding
- + - + - + - Type
+ - + - + - (+BT
- + -), + - + ??+ - + - + - + - + Binding
- + - + - + ? Value
? ????? E- +
1 I I
* +- +- + - + - + - +- + - + - + - + - + - + ++++++++ - - +
Binding Value ( continued ) (variable length )
+ - + - - +- + - + - + -+ - + - +- + - + ? ? ? ? ? ? + - + - + - + - + - + - + -+ - + - + - + - + - + - + F - ##

FIG . 5
U.S. Patent Jun . 14 , 2022 Sheet 3 of 4 US 11,362,940 B2

PCE4

PCE1 PCE2 PCE3

AS1 AS2 AS3

S P2 A2 P4 A4 P6
?1 A3 D
P1 P3 P5

FIG. 6
72
First receiving
module

74
Instruction module

Second receiving 76
module

FIG . 7
U.S. Patent Jun . 14 , 2022 Sheet 4 of 4 US 11,362,940 B2

82
Sending module

Third receiving 84
module

Compression 86
module

First returning 88
module

FIG . 8
 US 11,362,940 B2
1 2
METHOD AND APPARATUS FOR adjacency SID + Peer-Adj SID list is resulted in , label encap
DETERMINING IDENTIFICATION sulation capability of a device is easily exceeded, and
INFORMATION ABOUT CROSS -DOMAIN forwarding efficiency and maximum transmission unit
PATH , AND STORAGE MEDIUM (MTU) problems are introduced . Another problem is that the
5 each sub - PCE may not necessarily return the information
CROSS - REFERENCES TO RELATED about the path segment in the domain to the parent PCE
APPLICATIONS according to a local strategy. For example, a concept and a
mechanism of a path -key are defined by RFC 5520 , the
This is a National Stage Application, filed under 35 sub - PCE may reply to the parent PCE with the path -key
U.S.C. 371 , of International Patent Application No. PCT / 10 replacing the path segment information in an explicit rout
2

CN2018 /088880 , filed on May 29 , 2018 , which claims ing , and then a head node PCC of a final TE path cannot
priority to Chinese patent application No. 201710532649.1 obtain a complete adjacency SID + Peer -Adj SID list .
filed on Jul . 3 , 17 , contents of both of which are incor- In order to shorten the segment routing SID list corre
porated herein by reference in their entireties . sponding to the complete TE path , a binding segment is
15 defined in draft- ietf- spring-segment-routing -11, and may be
TECHNICAL FIELD used for referring to forwarding information about one
tunnel. That is , if one tunnel is additionally created for a
The present application relates to the field of communi- certain path segment in the complete TE path , and then the
cations and specifically, relates to a method and apparatus path segment may be represented by using one correspond
for determining identification information about a cross- 20 ing binding segment-identification (Binding SID) . Based on
domain path , and a storage medium . the idea , many protocols have been extended accordingly ,
and examples are descried below.
BACKGROUND 1 ) An Intermediate system to intermediate system (ISIS )
is extended and a SID /Label Binding TLV (where T repre
In the RFC 5623 , the computing cross - domain Traffic 25 sents Tag , L represents Length and V represents Value ) and
Engineering ( TE ) paths by adopting a hierarchical Path the usage method thereof are defined in draft-ietf-isis
Computation Element (PCE ) architecture has been dis- segment -routing -extensions - 12. However, only a Binding
cussed . A parent PCE is able to acquire connections between SID/ Label for a SR - TE path ( that is , the TE path established
all domains from each sub - PCE and maintain a domain - level by using the segment routing technique) is defined and a
topology . When the parent PCE is requested by a certain 30 Binding SID/Label corresponding to the Resource Reserva
sub - PCE to compute the cross - domain TE path , the parent tion Protocol- Traffic Engineering ( RSVP - TE) path ( that is ,
PCE firstly obtains according to the domain- level topology, the TE path established by using the RSVP - TE signaling) is
which domain sequences may be passed through by the TE not defined (note: when the RSVP - TE path is served as a
path , and then for each domain sequence , requests each Forwarding- adjacency, and an Interior Gateway Protocol
sub - PCE to compute a path segment in a corresponding 35 (IGP ) adjacency SID but not the Binding SID may be
domain . After the parent PCE receives the computation allocated ). In addition, the method is only applicable in the
result of the each sub - PCE , all the path segments are spliced IGP area , and not applicable in the cross - domain TE path .
to obtain a complete cross - domain TE path. The parent PCE 2 ) A Border Gateway Protocol - Link State (BGP - LS ) ( see
selects one optimal path from the complete TE paths cor- RFC7752 ) is extended and a notification method of the
responding to these domain sequences, and replies to the 40 Binding SID TLV is defined in the draft- ietf-idr-bgp - ls
sub -PCE requesting the computation path , which replies to segment - routing -ext- 01. Since the BGP - LS generally
the corresponding Path Computation Client ( PCC ) with the imports link state data from IGP instances , the method is
computation path . similar to the above -mentioned ISIS - SR , and only defines
The draft- ietf -pce - segment- routing -09 discusses how the the Binding SID /Label for the SR - TE path , and does not
PCE uses a segment list to represent the computed TE path 45 define the Binding SID /Label corresponding to the RSVP
for applying to a scenario of segment route forwarding. In TE path . In addition, Explicit Route Object (ERO ) informa
general, in the segment routing scenario , a strict explicit next tion corresponding to the path segment is to be provided
hop within ?a domain in the TE path may be represented by with the Binding SID in the method , while as mentioned
using an adjacency segment - identification ( SID ) of a seg- above , the sub - PCE does not necessarily expose the path
ment routing, while a strict explicit next hop between 50 segment information in its domain to the parent PCE , so in
domains in the TE path may be represented by using a the hierarchical PCE architecture , the method is only appli
Peer -Adj SID of the segment routing. As described above, cable to the PCC reporting a Binding SID to the sub - PCE at
when the parent PCE is requested by a certain sub - PCE to most , but not to the sub - PCE reporting the Binding SID to
compute a cross - domain TE path, the sub - PCE may specify the parent PCE . In addition, the method is generally only
a Path Setup Type ( PST) as “ path setup using a segment 55 used for synchronizing data in the direction from the PCC to
routing technique ". When the parent PCE requests the the PCE , and not for the tunnel initiatively created by the
sub - PCE to compute the path in the domain for each domain PCE . Finally, the method only describes how the BGP - LS
sequence, the parent PCE also specifies that the PST as “ path carries the Binding SID as a channel, and does not focus on
setup using the segment routing technique ”. Then , path providing solutions for the cross - domain TE path computa
segment information with which the each sub - PCE replies to 60 tion and packet forwarding.
the parent PCE may be represented by an adjacency SID list , 3 ) A Path Computation Element Protocol (PCEP) ( see
and the parent PCE may also use an adjacency SID + Peer- RFC 5440 ) is extended and aa method for notifying a tunnel
Adj SID list to represent a complete TE path when the parent segment is defined in the draft- li-pce - tunnel -segment-02.
PCE finally replies, with an optimal path , to the sub -PCE The tunnel segment is similar to the above -mentioned Bind
that requests the parent PCE to compute the path . However, 65 ing SID , and the RSVP - TE tunnel and the SR - TE tunnel are
a major problem here is that the complete TE path is supported. The method relates to a plurality of channels, a
generally long , a deep label stack corresponding to the PCE - LS similar to the BGP - LS ( seen draft-dhodylee -pce
 US 11,362,940 B2
3 4
pcep - ls - 07 ) is used to perform notification in a direction segment - identification (Binding SID ) to the created tunnel,
from the PCC to the PCE , and a PCLabelUpd ( see draft- where the creation message carries path information about
zhao -pce -pce -pcep -extension - for -pce - controller-04 ) similar the one or more path segments.
to a NETCONF is used in a direction from the PCE to the Optionally, the creation message being used for request
PCC . Both the PCE -LS and the PCLabelUpd are nominally 5 ing the each of sub -PCEs corresponding to the one or more
extension protocols of the PCEP, but differ greatly, and are path segments to create the tunnel includes one of the
complex when implemented and deployed. Similarly, the following: the creation message is used for requesting the
method only describes how the PCEP notifies the tunnel each of sub - PCEs corresponding to the one or more path
segment as a channel, and does not focus on providing segments to create a Resource Reservation Protocol - Traffic
solutions for the cross -domain TE path computation and 10 Extension (RSVP - TE) tunnel ; the creation message is used
packet forwarding. for requesting the each of sub - PCEs corresponding to the
4 ) The PCEP is also extended in the draft -sivabalan -pce- one or more path segments to create a Segment Routing
binding - label - sid - 02 so as to notify the Binding label to the Traffic Engineering ( SR - TE) tunnel; or the creation message
RSVP - TE path , and notify the Binding SID to the SR - TE is used for requesting the each of sub -PCEs corresponding
path , and the binding label/SID is reported by the PCC to the 15 to the one or more path segments to create the RSVP -TE
PCE . The method is only used for synchronizing data in the tunnel or the SR - TE tunnel.
direction from the PCC to the PCE , and not for the tunnel Optionally, the step in which the compressed identifica
initiatively created by the PCE . Similarly , the method only tion information about the one or more path segments
describes how the PCEP notifies the binding label / SID as a returned by the each of sub -PCEs corresponding to the one
channel, and does not focus on providing solutions for the 20 or more path segments is received, and in which the com
cross -domain TE path computation and packet forwarding. pressed identification information about the one or more
In view of the problem that the path identification infor- path segments is combined into the compressed identifica
mation is too long in the related art, no effective solution has tion information about the path includes steps described
yet been proposed . below . The Binding SID assigned to the created tunnel and
25 returned by the each of sub - PCEs corresponding to the one
SUMMARY or more path segments is received ; and received Binding
SIDs returned by the sub - PCEs corresponding to the one or
Embodiments of the present application provide a method more path segments are combined into compressed identi
and apparatus for determining identification information fication information about the path .
about a cross -domain path , and a storage medium , to solve 30 Optionally, the path information includes : a path name of
at least the problem of excessive length of the path identi- the path, segment information about the one or more path
fication information in the related art. segments, starting node information and destination node
According to one embodiment of the present application , information about to be created tunnel, and the PST.
a method for determining identification information about a Optionally, after the compressed identification informa
cross - domain path is provided . The method includes steps 35 tion about the one or more path segments are combined into
described below. A path computation request from a first the compressed identification information about the path
child path computation element (PCE ) is received , where the according to the identification information about the path ,
path computation request is used for making a request to the method includes that: the compressed identification
acquire a path from a source node to a destination node, the information about the path is returned to the first sub - PCE .
source node and the destination node are located in different 40 According to another embodiment of the present appli
domains , the path includes one or more path segments, and cation, a method for determining identification information
.

the path computation request carries a compression identifier
for identifying compression of the one or more path seg-
ments and a path setup type (PST ) . After identification
information about the path from the source node to the
destination node is acquired, each of sub - PCEs correspond-
ing to the one or more path segments is instructed according
to the compression identifier and the PST to compress
identification information about the respective each corre-
sponding path segment. The compressed identification infor-
mation about the one or more path segments returned by the
each of sub - PCEs corresponding to the one or more path
segments is received , and , the compressed identification
information about the one or more path segments is com-
bined into the compressed identification information about
the path according to the identification information about the
path .
Optionally, the step in which the each of sub - PCEs
corresponding to the one or more path segments is instructed
according to the compression identifier to compress the
identification information about a respective one of the one
or more path segments includes steps described below .
According to the compression identifier, a creation message
is sent to the each of sub - PCEs corresponding to the one or
more path segments, where the creation message is used for
requesting the each of sub - PCEs corresponding to the one or
more path segments to create a tunnel, and assign a binding
about aa cross - domain path is further provided . The method
includes steps described below . A path computation request
is sent to a parent path computation element (PCE ) , where
45 the path computation request is used for making a request to
acquire a path from a source node to a destination node , the
source node and the destination node are located in different
domains , the path includes one or more path segments, and
the path computation request carries a compression identifier
50 for identifying compression of the one or more path seg
ments and a path setup type ( PST ) . A creation message from
the parent PCE is received , where the creation message is
sent by the parent PCE according to the compression iden
tifier and the PST. The identification information about a
55 path segment is compressed according to the creation mes
sage . The compressed identification information about the
one or more path segments is returned to the parent PCE .
Optionally, the step in which the identification informa
tion about the one or more path segments is compressed
60 according to the creation message includes steps described
below . Path information about the one or more path seg
ments carried in the creation message is determined . A
tunnel is created according to the path information , and a
binding segment - identification ( Binding SID ) is assigned to
65 the created tunnel.
Optionally, the creation message is used for making a
request to create at least one of following tunnels : a
 US 11,362,940 B2
5 6
Resource Reservation Protocol - Traffic Engineering (RSVP- ing to the identification information about the path , the
TE ) tunnel; or a Segment Routing - Traffic Engineering ( ST- compressed identification information about the one or more
TE) tunnel. path segments into the compressed identification informa
Optionally, the step in which the tunnel is created accord- tion about the path .
ing to the path information includes that: the tunnel is 5 Optionally, the instruction module includes a sending
instantiated according to the path information, and that the element. The sending element is configured to send a
creation message is forwarded to a path computation client creation message to the each of sub - PCEs corresponding to
( PCC ) as a starting node of the tunnel to be created, where the one or more path segments according to the compression
the creation message is used for instructing the PCC to identifier, where the creation message is used for requesting
creating, the
initiate according
tunnel. to the path information , a process of 10 the each of sub -PCEs corresponding to the one or more path
segments to create a tunnel, and assign a binding segment
Optionally, the method includes one of the following: identification ( Binding SID ) to the created tunnel, where the
when the creation message is used for making a request to creation message carries path information about the one or
create the RSVP - TE tunnel, the creation message is used for more path segments.
instructing the PCC to initiate an RSVP -TE signaling setup 15 According to another embodiment of the present appli
path ; or when the creation message is used for making a
request to create the SR - TE tunnel, the creation message is cation, an apparatus for determining identification informa
used for instructing the PCC to compute forwarding infor- tion about a cross - domain path is further provided . The
mation about the path according to segment routing infor- apparatus includes : a sending module, a third receiving
mation . 20 module, a compression module and a first returning module .
Optionally, the step in which the Binding SID is assigned The sending module is configured to send a path computa
to the created tunnel includes: in condition that the segment- tion request to a parent path computation element ( PCE ) ,
identification ( SID ) is assigned by a controller globally and where the path computation request is used for making a
uniformly , after the tunnel is instantiated according to the request to acquire a path from a source node to a destination
path information , the Binding SID is assigned to the tunnel 25 node , the source node and the destination node are located
and reported to the parent PCE and the PCC ; and / or that in in different domains, the path includes one or more path
condition that the SID is assigned by a forwarding device segments, and the path computation request carries a com
and where the assigned SID is reported to the controller, the pression identifier for identifying compression of the one or
Binding SID assigned by the PCC to the tunnel after the more path segments and a path setup type (PST ) . The third
PCC creates the tunnel is received and the Binding SID is 30 receiving module is configured to receive a creation message
reported to the parent PCE . from the parent PCE , where the creation message is sent by
Optionally, after the compressed identification informa- the parent PCE according to the compression identifier and
tion about the one or more path segments is returned to the the PST. The compression module is configured to compress
parent PCE , the method further includes steps described identification information about a path segment according to
below. Compressed identification information about the path 35 the creation message . The first returning module is config
from the parent PCE is received . In condition that the path ured to return the compressed identification information
computation request is initiated by a predetermined path about the one or more path segments to the parent PCE .
computation client (PCC ) , the compressed identification Optionally, the compression module includes: a determi
information about the path is returned to the predetermined nation element and a creation element. The determination
PCC . In condition that the path computation request is not 40 element is configured to determine path information about
initiated by the predetermined path computation client the one or more path segments carried in the creation
( PCC ) , the compressed identification information about the message . The creation element is configured to create a
path is sent to a PCC as a starting node of the tunnel. tunnel according to the path information, and assign a
According to another embodiment of the present appli- binding segment- identification ( Binding SID ) to the created
cation, an apparatus for determining identification informa- 45 tunnel.
tion about a cross -domain path is further provided . The Optionally, the apparatus further includes : a fourth receiv
apparatus includes : a first receiving module, an instruction ing module, a second returning module and aa third returning
module and a second receiving module. The first receiving module. The fourth receiving module is configured to
module is configured to receive a path computation request receive compressed identification information about the path
from a first child path computation element ( PCE ) , where 50 from the parent PCE after the compressed identification
the path computation request is used for making a request to information about the one or more path segments is returned
acquire a path from a source node to a destination node, the to the parent PCE . The second returning module is config
source node and the destination node are located in different ured to return the compressed identification information
domains , the path includes one or more path segments, and about the path to a predetermined path computation client
the path computation request carries a compression identifier 55 (PCC ) in condition that the path computation request is
for identifying compression of the one or more path seg- initiated by the predetermined PCC . The third returning
ments and a path setup type (PST ) . The instruction module module is configured to send the compressed identification
is configured to instruct, according to the compression information about the path to a path computation client
identifier and the PST, each of sub -PCEs corresponding to (PCC ) as a starting node of the tunnel in condition that the
the one or more path segments to compress the identification 60 path computation request is not initiated by the predeter
information about a respective one of the one or more path mined PCC .
segments after identification information about the path According to another embodiment of the present appli
from the source node to the destination node is acquired. The cation, a storage medium is further provided . The storage
second receiving module is configured to receive the com- medium includes stored programs which, when run , execute
pressed identification information about the one or more 65 the method of any one of the embodiments described above .
path segments returned by the each of sub - PCEs correspond- According to another embodiment of the present appli
ing to the one or more path segments, and combine , accord- cation, a processor is further provided . The processor is
 US 11,362,940 B2
7 8
configured to run programs which, when run , execute the the path computation request carries a compression identifier
method of any one of the embodiments described above . for identifying compression of the path segments and a path
According to the present application , after identification setup type ( PST ) .
information about the path from the source node to the In step S104 , after identification information about the
destination node is acquired, the identification information 5 path from the source node to the destination node is
about the path is compressed, and thereby the length of the acquired, each of sub - PCEs corresponding to the one or
identification information about the path is effectively more path segments is instructed according to the compres
sion identifier and the PST to compress identification infor
reduced, and the problem of excessive length of the path mation about a respective one of the one or more path
identification information in the related art is solved .
10 segments.
BRIEF DESCRIPTION OF DRAWINGS In step 106 , the compressed identification information
about the one or more path segments returned by the each of
The drawings described herein are used provide a sub -PCEs corresponding to the one or more path segments
further understanding of the present application and form a is received , and the compressed identification information
part of the present application. The exemplary embodiments 15 about the one or more path segments is combined into the
and description thereof in the present application are used to compressed identification information about the path
explain the present application and not to limit the present according to the identification information about the path.
application in any improper way . In the drawings: The above operations may be performed by a parent PCE .
FIG . 1 is a flowchart of a first method for determining The processing on the parent PCE side is described in the
identification information about a cross -domain path accord- 20
ing to an embodiment of the present application ;
embodiment
According one . above steps, after identification infor
to the
FIG . 2 is aa flowchart of a second method for determining mation about the path from the source node to the destina
identification information about a cross - domain path accord tion node is acquired, the identification information about
ing to an embodiment of the present application; the path is compressed, and thereby the length of the
FIG . 3 is a schematic diagram of a Request Parameters 25 identification information about the path is effectively
( RP) object according to an embodiment of the present reduced, and the problem of excessive length of the path
application; identification information in the related art is solved .
FIG . 4 is a schematic diagram of a Path Setup Type TLV In an optional embodiment, the step in which the each of
according to an embodiment of the present application; sub -PCEs corresponding to the one or more path segments
FIG . 5 is a schematic diagram of a TE - PATH - BINDING 30 is instructed according to the compression identifier to
TLV according to an embodiment of the present application; compress the identification information about the corre
FIG . 6 is a diagram of a hierarchical PCE network sponding path segment includes: a creation message sent
architecture according to an embodiment of the present path to the each of sub - PCEs corresponding to the one or more
application ; segments according to the compression identifier. The
FIG . 7 is a structure diagram of a first apparatus for 35 creation message is used for requesting the each of sub
determining identification information about aa cross - domain PCEs corresponding to the one or more path segments to
path according to an embodiment of the present application ; create a tunnel, and a binding segment- identification (Bind
and ing SID ) is assigned to the created tunnel. The creation
FIG . 8 is a structure diagram of a second apparatus for message carries path information about the one or more path
determining identification information about a cross -domain 40 segments.
path according to an embodiment of the present application. In an optional embodiment , the above-mentioned creation
message being used for requesting the each of sub - PCEs
DETAILED DESCRIPTION corresponding to the one or more path segments to create the
tunnel includes one of the following: the above -mentioned
The present application will be described hereinafter in 45 creation message is used for requesting the each of sub
detail through embodiments with reference to the drawings. PCEs corresponding to the one or more path segments to
It is to be noted that if not in collision , the embodiments and create a Resource Reservation Protocol- Traffic Engineering
features therein in the present application may be combined (RSVP - TE ) tunnel; the above -mentioned creation message
with each other. is used for requesting the each of sub -PCEs corresponding
It is to be noted that the terms “ first ” , “ second” and the 50 to the one or more path segments to create a Segment
like in the description, claims and drawings of the present Routing - Traffic Engineering ( SR - TE) tunnel; or the above
application are used to distinguish between similar objects mentioned creation message is used for requesting the each
and are not necessarily used to describe a particular order or of sub - PCEs corresponding to the one or more path seg
sequence. ments to create the RSVP - TE tunnel or the SR - TE tunnel.
55 In an optional embodiment, the step in which the com
Embodiment One pressed identification information about the one or more
path segments returned by the each of sub - PCEs correspond
FIG . 1 is a flowchart of a first method for determining ing to the one or more path segments is received , and in
oss -domain path accord- which the compressed identification information about the
identification information about a cros
ing to an embodiment of the present application . As shown 60 one or more path segments is combined into the compressed
in FIG . 1 , a process includes the steps described below. identification information about the path includes : the Bind
In step S102 , a path computation request from a first child ing SID assigned to the created tunnel and returned by the
path computation element ( PCE ) is received, where the path each of sub - PCEs corresponding to the one or more path
computation request is used for making a request to acquire segments is received ; and that the received Binding SIDs
a path from a source node to a destination node, the source 65 returned by the sub - PCEs corresponding to the one or more
node and the destination node are located in different path segments are combined into the compressed identifi
domains , the path includes one or more path segments , and cation information about the path .
 US 11,362,940 B2
9 10
In an optional embodiment, the above -mentioned path Traffic Engineering (RSVP - TE ) tunnel; or a Segment Rout
information includes : a path name of the path, segment ing - Traffic Engineering ( SR - TE ) tunnel. It is to be noted that
information about the one or more path segments, starting the embodiment about the RSVP - TE tunnel and the embodi
node information and destination node information about the ment about the SR - TE tunnel are merely two preferred
tunnel to be created , and the above -mentioned PST. 5 embodiments, and other types of tunnels may be created
In an optional embodiment, after the compressed identi- according to actual conditions and technological develop
fication information about the one or more path segments are ments , and are not limited herein .
combined into the compressed identification information In an optional embodiment, the step in which the tunnel
about the path according to the above -mentioned identifi- is created according to the path information includes: the
cation information about the path , the method further 10 tunnel is instantiated according to the path information , and
includes : the compressed identification information about that the creation message is forwarded to a path computation
the path is returned to the first sub - PCE . In other words, in client ( PCC) as a starting node of the tunnel to be created .
response to the path computation req sent by the first The creation message is used for instructing the PCC to
sub -PCE, the compressed identification information about initiate , according to the path information, a process of
the path is returned to the first sub - PCE , and the first 15 creating the tunnel. In the embodiment, the tunnel is created
sub -PCE may continue to perform subsequent operations by the PCC .
after acquiring the compressed identification information In an optional embodiment, when the types of tunnels to
about the path . For example, the first sub -PCE may send the be created are different, specific operations the PCC is
acquired compressed identification information about the instructed to perform are also different. Optionally, when the
path to the corresponding PCC , and the PCC encapsulates a 20 above -mentioned creation message is used for making a
packet according to the identification information about the request to create the RSVP - TE tunnel, the creation message
path , and forwards the packet. is used for instructing the PCC to initiate an RSVP - TE
signaling setup path ; and optionally, when the above-men
Embodiment Two tioned creation message is used for making a request to
25 create the SR - TE tunnel, the creation message is used for
FIG . 2 is a flowchart of a second method for determining instructing the PCC to compute forwarding information
oss -domain path accord-
identification information about a cros about the path according to segment routing information .
ing to an embodiment of the present application . As shown In an optional embodiment, how to assign the Binding
in FIG . 2 , a process includes the steps described below. SID to the created tunnel is described as follows: in condi
In step S202, a path computation request is sent to a parent 30 tion that a segment- identification ( SID) is assigned by a
path computation element ( PCE) , where the path computa- controller globally and uniformly, after the tunnel is instan
tion request is used for making a request to acquire a path tiated according to the above -mentioned path information ,
from a source node a destination node , the source node the Binding SID is assigned to the tunnel and reported to the
and the destination node are located in different domains, the parent PCE and the PCC ; and /or in condition that the SID is
path includes one or more path segments, and the path 35 assigned
computation request carries a compression identifier for
by a forwarding device and where the assigned SID
is reported to the controller, the Binding SID assigned by the
identifying compression of the path segments and a path PCC to the tunnel after the above -mentioned PCC creates
setup type ( PST) . the tunnel is received and reported to the parent PCE .
In step S204 , a creation message from the parent PCE is In an optional embodiment, after the compressed identi
2
received , where the creation message is sent by the parent 40 fication information about the one or more path segments is
PCE according to the compression identifier and the PST. returned to the parent PCE , the method further includes :
In step S206 , the identification information about a path compressed identification information about the path from
segment is compressed according to the creation message . the parent PCE is received . In condition that the above
In step S208 , the compressed identification information mentioned path computation request is initiated by a prede
about the path is returned to the parent PCE . 45 termined path computation client ( PCC ) , the compressed
The above -mentioned operations may be performed by a identification information about the path is returned to the
sub - PCE ( such as , the first sub - PEC in embodiment one) . predetermined PCC ; and in condition that the path compu
The processing on the sub - PCE side is described in the tation request is not initiated by the predetermined path
embodiment two . computation client ( PCC ) , the compressed identification
According to the above-mentioned steps, after identifica- 50 information about the path is sent to a PCC as a starting node
tion information about the path from the source node to the of the tunnel.
destination node is acquired, the identification information
about the path is compressed, and thereby the length of the Embodiment Three
identification information about the path is effectively
reduced, and the problem of excessive length of the path 55 The present application is described from the parent PCE
identification information in the related art is solved . side and the sub - PCE side in the above -mentioned embodi
In an optional embodiment, the step in which the identi- ments, and will be described below as a whole .
>

fication information about the one or more path segments is In the embodiment, in an SR - TE tunnel that is initiated
compressed according to the creation message includes : path and established by the PCC side or an SR - TE tunnel that is
information about the one or more path segments carried in 60 initiatively created by the PCE the ability to compress
the above -mentioned creation message is determined ; and possible path segments is explicitly configured . An ability
that a tunnel is created according to the path information , flag ( corresponding to the compression identifier described
and a binding segment- identification ( Binding SID ) is above) will be included in a path computation request
assigned to the created tunnel. initiated by the PCC to the PCE ( and the sub - PCE to the
In an optional embodiment, the above -mentioned creation 65 parent PCE ) . According to the ability flag, a parent PCE
message is used for making a request to create at least one triggers a sub - PCE of each domain to additionally create an
of the following tunnels: a Resource Reservation Protocol- RSVP - TE tunnel ( or SR - TE tunnel) according to a corre
 US 11,362,940 B2
11 12
sponding path segment. Each sub - PCE initiatively assigns a each domain , or a path -key corresponding to the specific
Binding SID to the additionally created RSVP - TE tunnel (or path segment within each domain.
SR - TE tunnel) or acquires the Binding SID from a head It is to be noted that since the PST is “ path setup using the
node PCC of the RSVP - TE tunnel (or SR - TE tunnel). Each segment routing technique ” , each sub - PCE may attempt to
sub - PCE synchronizes the Binding SID to the parent PCE , 5 reply to the parent PCE with the SID list , and certainly it is
the parent PCE applies the Binding SID in a segment routing also allowed by the protocol to reply to the parent PCE with
SID list corresponding to a complete cross - domain TE path either an IP address list or an IP address + SID combination
and replies to the sub - PCE initiating the path computation replies to description
list . The
the sub -
equally applies when the parent PCE
PCE1 with the complete TE path .
request to the parent PCE , and the PCE delivers the Binding 10 Each sub - PCE may generally
SID to its PCC . The PCC encapsulates a packet by using the LS , topology information within collect , through the BGP
9

SID list and forwards the encapsulated packet. the domain the each sub
A method of cross -domain TE path computation and about PCE is responsible for and inter -domain link information
packet forwarding provided in the embodiment specifically sub -PCE connection of the domain to other domains , and each
includes the steps below . needs to report the inter - domain link information
15 to the parent PCE through the BGP - LS . In addition to the
A first step is described below . BGP - LS , other channels may also be used , which is not
In an SR - TE tunnel that is initiated and established by the limited in the embodiment of the present application.
PCC side or an SR - TE tunnel that is initiatively created by A third step is described below .
the PCE , the ability to compress possible path segments is Unlike the method described in RFC 6805 , now the parent
explicitly configured . The specific compression capability 20 PCE does not immediately reply to the sub -PCE1 with the
may be as follows. above -mentioned optimal complete TE path , but finds after
Option1 : No compression is performed . checking that the path segment compression identifier
Option2: Only the RSVP - TE tunnel is additionally cre- included in the path computation request message sent to the
ated for path segments. parent PCE by the sub - PCE1 indicates “ to be compressed ”,
Option3: Only the SR - TE tunnel is additionally created 25 so the parent PCE sends an “ initiatively creating tunnel ”
for path segments . message to the sub - PCE corresponding to each domain for
Option4: The RSVP - TE tunnel or the SR - TE tunnel is each path segment in each domain in each optimal complete
additionally created for path segments, which is not limited . path . The message at least includes : a pathname, the path
If the ability is configured as Option1 , the method segment information , the starting node (that is , the first node
described in the embodiment of the present application is the 30 of the path segment) and the destination node ( that is , the last
same as a method described in RFC 6805. In the embodi- node of the path segment) information about the tunnel to be
ment, the description is mainly for Option2 or Option3 or created and the PST. For the pathname, the complete path
Option4 , and Option2 , Option3 , and Option4 are uniformly name (i.e. , path -name -SD ) may be followed by something,
referred to as “ to be compressed ” for ease of description. It such as path -name -SD -head node of the path segment - last
should be noted that in addition to the above -mentioned four 35 node of the path segment, so as to be globally unique. The
Options , other options may be extended and supported path segment information is returned to the parent PCE by
similarly in the future . the corresponding sub - PCE before, but now is in turn
A second step is described below. provided as an ERO by the parent PCE to the sub - PCE to
For computation of a cross - domain TE path , according to create a tunnel. The starting node and the destination node
the method described in RFC 6805 , for the SR - TE tunnel 40 of the tunnel to be created are the head node and the end
initiated and established by the PCC side , the PCC initiates
9 node of the corresponding path segment respectively. The
a path computation request to a sub - PCE ( referred to as PST is to be set accord to the path segment compression
sub - PCE1) in a domain where the SR - TE tunnel is located , identifier described above . If the path segment compression
or for the SR - TE tunnel initiatively established by the identifier is Option2 , the PST is set to be “ path setup using
sub -PCE1, the sub -PCElinitiates the path computation 45 the RSVP - TE signaling ”, if the path segment compression
request to the parent PCE . The path computation request identifier is Option3 , the PST is set to be “ path setup using
message indicates that the PST is “ path setup using the the segment routing technique", and if the path segment
segment routing technique” and also includes a compression compression identifier is Option4 , the PST is set to be “ path
ability flag of the path segment described above . It is setup using the RSVP - TE signaling or the segment routing
assumed that the request message further includes a path 50 technique ”.
name, i.e. , path -name-SD . A fourth step is described below .
According to the method described in RFC 6805 , the After the sub - PCE corresponding to each domain receives
parent PCE firstly computes, according to the domain - level a “ initiatively creating tunnel” message from the parent
topology information the parent PCE maintains, which PCE , the corresponding tunnel is instantiated locally, the
domain sequences the cross -domain TE path may traverse , 55 “ initiatively creating tunnel” message is forwarded to the
and then for each domain sequence , initiates a path compu- starting node PCC of the tunnel to be created , and the PCC
tation request within each domain to a sub - PCE in the each initiates the path setup in the network according to the PST
domain . It is to be noted that the path computation request and the ERO given in the message . For example, the PST is
message sent by the parent PCE to each sub - PCE is only “ path setup using the RSVP - TE signaling ", and then the
used to acquire potential paths for selecting an optimal path . 60 PCC initiates an RSVP - TE signaling path setup. For
Therefore the path segment compression identifier included example , the PST is “ path setup using the segment routing
in the message has to be “ No compression is performed ”, technique” , and then the PCC directly computes the for
and the PST may still be “ path setup using the segment warding information about the path according to the seg
routing technique ” . The parent PCE eventually computes an ment routing information . For example, the PST is " path
optimal cross - domain TE path from a number of domain 65 setup using the RSVP - TE signaling or path setup using the
sequences. The TE path may include an IP address list or a segment routing technique ", and then the PCC chooses,
.

SID list corresponding to a specific path segment within according to its own actual ability, to initiate the RSVP - TE
 US 11,362,940 B2
13 14
signaling path setup or directly compute the forwarding ( Peer -Adj SID ) is replaced with the forwarding information
information about the path according to the segment routing about the corresponding inter - domain link .
information . Compared with the existing art, the method in the embodi
In a deployment scenario in which a SID is assigned by ment of the present application can significantly shorten the
a controller globally and uniformly, after the corresponding 5 segment routing SID list of the cross - domain TE path ,
tunnel is instantiated , the sub - PCE corresponding to each reduce a depth of a label stack for encapsulating the packet,
domain may initiatively assign a Binding SID to the corre- improve the packet load efficiency and avoid MTU frag
sponding tunnel, report the Binding SID to the parent PCE mentation .
and delivers the Binding SID to the PCC . In a deployment 10
Embodiment Four
scenario in which the SID is configured by a forwarding
device side and reported to the controller, the starting node
PCC of the corresponding tunnel may assign the correspond- The implementation of the technical solution will be
ing Binding SID to the tunnel and report the Binding SID to further described in detail with reference to the drawings.
the sub - PCE after the tunnel is established , and the sub - PCE 15 FIG . 3 is a schematic diagram of an RP object according
continues to report the Binding SID to the parent PCE . to an embodiment of the present application. On the basis of
It is to be noted that the Binding SID assigned to the RP objects defined in RFC 5440 , RFC 5520 , RFC 5541 and
tunnel has local attributes and generally does not need to be
RFC 5557 , a Compress Flag (CF ) intending to occupy three
globally unique. If global uniqueness is required , a scenario
bits is added into a field of Flags to identify whether a path
should be deployed in which the controller assigns the SID 20
needs to be compressed , and the meanings of specific values
globally and uniformly, and SID resource pools controlled are as follows.
by sub - PCEs should not overlap each other, either by O denotes that the path does not need to be compressed.
management or in other dynamic learning manners. 1 denotes that compression is performed in a manner of
A fifth step is described below . additionally establishing only an RSVP -TE tunnel for path
After the parent PCE receives the Binding SID of the 25 segments.
created tunnel corresponding to the path segment in the 2 denotes that compression is performed in a manner of
corresponding domain from each sub - PCE , the SID list additionally establishing only an SR - TE tunnel for path
corresponding to an original complete TE path may be segments .
shortened and optimized . Actually, regardless of the path 3 denotes that compression is performed in a manner of
segment information with which each sub -PCE replies to the 30 additionally establishing the RSVP - TE tunnel or the SR-TE
parent PCE before being the IP address list or the SID list or tunnel for path segments.
a combination of the IP address list and the SID list , or even FIG . 4 is a schematic diagram of a Path Setup Type TLV
a path -key, the parent PCE does not care about the specific according to an embodiment of the present application. On
ERO content of the path segment information, and the path the basis of draftthat
- ietfa-pce -lspsetup
- setuptechnique
-type - 04 , amayPSTbe= 2“ anis
segment needs only to be represented by its Binding SID
the SID list corresponding to the complete TE path . In in 35 added to denote path
addition , in combination with the corresponding Peer-Adj RSVP - TE signaling or a segment routing technique ” . The
SID of the inter - domain link , the shortened and optimized Path Setup Type TLV may be carried in the RP object
SID list of the complete TE path is generally { Binding SID1 , ( reference to RFC 5440) and aa Stateful PCE Request Param
Peer- Adj SID1 , Binding SID2,Peer-Adj SID2, ... , Binding 40 eters (SRP) object (reference to draft -ietf -pce- stateful-pce
18 ) . At present , draft- ietf -pce - Isp -setup - type - 04 defines
SIDn } . It is to be noted that the node SID of the correspond PST = 0 , which denotes that the path setup technique adopts
ing starting node may, but may not necessarily, also be
inserted before each Binding SID and Peer- Adj SID in the the RSVP - TE signaling, and draft-ietf -pce -segment- routing
SID list . In addition , in aa special case , the Binding SID1 may 09 defines PST= 1 , which denotes that the path setup tech
not exist, for example, the starting node of the complete TE 45 nique adopts the segment routing technique.
path happens to be the exit boundary node of the first domain FIG . 5 is a schematic diagram of aa TE - PATH - BINDING
in the domain sequence. TLV according to an embodiment of the present application .
A sixth step is described below. A TE -PATH - BINDING TLV defined by draft - sivabalan -pce
The parent PCE replies to the sub - PCE1 with the above- binding - label- sid -02 is taken as a basis , and is extended in
mentioned shortened and optimized SID list in response to 50 the usage manner. The draft -sivabalan -pce -binding- label
a cross -domain TE path computation request message pre sid - 02 defines the TE -PATH -BINDING TLV included in a
viously received from the sub - PCE1. The sub - PCE1 con- Label Switched Path ( LSP ) object in a PCRpt message and
tinues to reply, with the SID list , to the PCC from which the used for reporting the Binding SID of a corresponding TE
corresponding path computation request is received , or path from the PCC to the PCE . The embodiment follows the
delivers the SID list to the head node PCC of the tunnel 55 method to report the Binding SID of an additionally created
when the sub - PCE1 initiatively creates a cross - domain tun- tunnel for a path segment in a corresponding domain from
nel . a PCC to a sub - PCE and from the sub -PCE to a parent PCE ,
The PCC may use the SID list as the forwarding infor- which is applicable to a deployment scenario in which a
mation about the cross - domain SR - TE tunnel. It is to be forwarding device side itself configures a SIDand reports the
noted that if the first SID in the SID list is the Binding SID , 60 SID to a controller. In addition, the embodiment also extends
the Binding SID actually refers to the forwarding informa- the usage of the LSP object described in draft -ietf-pce
tion about the tunnel corresponding to the path segment of stateful -pce - 18 and draft -ietf -pce -pce - initiated - Isp -09, and
the domain where the PCC is located , so when the SR - TE respectively allows inclusion of the above -mentioned TE
tunnel finally generates the forwarding information , the first PATH - BINDING TLV in the LSP object included in a
SID (Binding SID ) is replaced with the forwarding infor- 65 PCUpd message and a PCInitiate message , for delivering the
mation about the corresponding tunnel. Similarly, if the first Binding SID of an additionally created tunnel for a path
SID in the SID list is the Peer-Adj SID , the first SID segment in a corresponding domain from the sub - PCE to the
 US 11,362,940 B2
15
PCC , which is applicable to a deployment scenario in which
the controller assigns the SID globally and uniformly .
Specific Embodiment One
5
FIG . 6 is a diagram of a hierarchical PCE network
architecture according to an embodiment of the present
application. Three domains are included , and respectively
are AS1 , AS2 and AS3 . The corresponding sub - PCEs of
16
node A2 to the destination node A3 and sends the PCReq
message to the PCE3 for requesting computation of the path
segment from the source node A4 to the destination node D.
Details are not described here again .
In step 130 , after each sub - PCE receives the path com
putation request from the PCE4 , the respective path segment
is computed and the PCRep message is sent to the PCE4 . In
the embodiment, the PCE1 will compute a path segment
S - P1 - P2 -A1 , the PCE2 will compute a path segment A2-P3
2

AS1 , AS2 ,andandAS3

respectively are aPCEPCE1is ,a aPCE4
a parent PCE2. Inand
the aembodi
PCE3
10 P4-A3 , and the PCE3 will compute a path segment A4 -P5
ment, it is assumed that the deployment scenario is provided P6 - D . In general, the path segment information is provided
in which a centralized controller uniformly assigns the SID in an ERO object included in a PCERep message with which
and delivers the SID to a forwarding device ; and that the each sub - PCE replies to the PCE4 , and may be an IP address
PCE1 wants to initiatively create an SR - TE tunnel from a 15 even
list, a SID list, an IP address and SID combination list, or
source node S to a destination node D , and that the PCE1 may be a path -key for security reasons . However, in the
knows that border nodes of other ASs have been upgraded embodiment , since the SR is not supported in each AS , the
to be able to support the segment routing function and that path segment information returned by each sub - PCE to the
internal nodes of other ASs (AS2, AS3 ) only support an PCE4 may be the IP address list or the path -key.
RSVP - TE but do not support the segment routing function . 20 In step 140 , For domain sequence S-( AS1 )-A1- A2-(AS2 )
Now , the specific steps in which the PCE1 initiatively A3 -A4 - AS3 )-D , the PCE4 will obtain a complete end - to
creates one SR - TE tunnel from the source node S to the end TE path after receiving the path segments of all domains
destination node D are described below. from all sub - PCEs . In the embodiment, since no other
In step 110 , the PCE1 initiatively creates the SR - TE domain sequence exist , the complete TE path described
tunnel, the source node is S , and the destination node is D. 25 above will serve as an optimal path. At the moment, the
The PCE1 finds, according to its own maintained Textease PCE4 does not immediately reply to the PCE1 with the
( TE ) database ( TED ) information , that the destination node optimal complete TE path , but finds after checking that the
D does not belong to AS1 , and then the PCE1 sends a PCReq CF flag in the corresponding path computation request
message to the parent PCE (PCE4 ) for requesting compu- received from the PCE1 is 1 , and then initiatively creates the
tation of a cross - domain TE path . For aa setting method of 30 RSVP - TE tunnel for each path segment and sends a PCIni
each field in the message , reference may be made to the RFC tiate message to each sub - PCE . For example, the PCE4
5440 and draft- ietf-pce - stateful - pce - 18 in combination with additionally creates a corresponding RSVP - TE tunnel inter
the solution in the embodiment of the present application . nally for a path segment S - P1 - P2 - A1 in AS1 . An included
Only the main information strongly related to the processing main path may be named path -name -SD - 100 - SA1 (note : the
flow in the embodiment of the present application is given 35 naming method is to add head and tail key information, i.e. ,
below. respectively S and A1 , of a child path to the tail of a parent
<RP object > : The PST is set to be 1 indicating the path path name, i.e. , path -name - SD - 100, to ensure global unique
setup using segment routing technique; and a CF flag is set ness ) . Accordingly, in the PCInitiate message sent from the
to be 1 , so as to perform compression by additionally PCE4 to the PCE1 , the main information is as follows.
creating an RSVP - TE tunnel for the path segment within 40 < SRP object >: The PST is set to be 0 indicating path setup
each AS . using the RSVP - TE .
< END - POINTS object >: The source node is S , and the < LSP object >: The path -name is set to be path -name-SD
destination node is D. 100 - SA1 .
< LSP object > : The path - name is set to be path -name-SD- <END - POINTS object> : The source node is S , and the9

100 . 45 destination node is A1 .

Other objects such as constraints will not be described in < ERO object > : The S - P1 - P2 - A1 specifically may be the
detail. IP address list or the path -key, that is , the path segment
In step 120 , after the PCE4 receives a request, the PCE4 information previously received from the PCE1 is filled in
firstly determines, according to the method described in intact.
RFC 6805 , that the domain where the destination node is 50 The PCE4 also additionally creates a corresponding
located AS3 , and then determines a possible domain
2 RSVP - TE tunnel internally for a path segment A2 - P3 - P4 -A3
sequence. In the embodiment, only one domain sequence in AS2 . An included main path may be named path -name
exists , that is S -CAS1 )-A1-A2-(AS2 )-A3 - A4-(AS3 )-D . For SD - 100 - A2A3 , and accordingly, the PCInitiate message is
the domain sequence, the PCE4 sends a PCReq message to sent to the PCE2 . The PCE4 also additionally creates a
the sub - PCE corresponding to each domain in the sequence, 55 corresponding RSVP - TE tunnel internally for a path seg
requesting computation of the path segment within each ment A4 - P5 - P6 - D in AS3 . An included main path may be
domain . For example, the PCE4 sends the PCReq message named path -name- SD - 100 - A4D , and accordingly, the
to the PCE1 , requesting computation of the path segment PCInitiate message is sent to the PCE3 . Details are not
from the source node S to the destination node A1 . The main described here again .
information in the message is described below . 60 In step 150 , after each sub - PCE receives the PCInitiate
<RP object > : The PST is set to be 1 indicating the path message from the PCE4 , each sub - PCE will also initiatively
setup using segment routing technique; and aa CF flag has to create a corresponding RSVP - TE tunnel internally and con
be set as 0 , denoting that the path is not compressed. tinue to send the PCInitiate message to a head node PCC of
< END -POINTS object >: The source node is S , and the the tunnel. It is to be noted that in the PCInitiate message
destination node is A1 . 65 that each sub - PCE continues to send to the head node PCC
The PCE4 also sends the PCReq message to the PCE2 for of the tunnel, the ERO object includes a clear strict hop
requesting computation of the path segment from the source by - hop explicit path , which may be the IP address list but not
 US 11,362,940 B2
17 18
the path -key. Each head node of the tunnel will establish a establishes one cross - domain SR - TE tunnel from the source
path within the network through the RSVP - TE signaling and node S to the destination node D , and the processes are
negotiate labels . basically similar to those in the specific embodiment one ,
In the embodiment, after each sub - PCE has created a except that the Binding SID of the RSVP - TE tunnel addi
corresponding RSVP-TE tunnel, each sub -PCE will also 5 tionally created for the path segment of each domain
initiatively assign a Binding SID to the RSVP - TE tunnel. involved is assigned by the head node itself of the tunnel and
For example , the PCE1 assigns the Binding SID = 1000 to the reported to the corresponding sub - PCE through the PCRpt
above -mentioned created RSVP - TE tunnel, the PCE2 message , and that the sub - PCE continues to report the
assigns the Binding SID =2000 to the above -mentioned Binding SID to the PCE4 through the PCRpt message , and
created RSVP -TE tunnel, and the PCE3 assigns the Binding 10 the other processes are the sameas those in the embodiment
SID =3000 to the above -mentioned created RSVP - TE tun one .
nel . Each sub - PCE may deliver the Binding SID to the head
node PCC of the tunnel along with the above -mentioned Specific Embodiment Three
PCInitiate message or a subsequent PCUpd message , and
may also report the Binding SID to the PCE4 along with the 15 The specific embodiment is basically similar to the spe
PCRpt message . After receiving the Binding SID , each head cific embodiment one, except that the S node establishes one
node of the tunnel will establish a label table entry with the cross - domain SR - TE tunnel from the source node S to the
Binding SID as a key value to guide the packet to be destination node D in the embodiment, and that the S node
forwarded to the tunnel. The label operation is to exchange PCC sends the PCReq message to the PCE1 , where the
the incoming label Binding SID into the outgoing label 20 message is same as the PCReq message sent by the PCE1 to
included in the RSVP - TE tunnel. the PCE4 in the embodiment one , and the other processes
It is to be noted that each sub - PCE also assigns a are the same as those in the embodiment one , and finally the
Peer - to -Adj SID to an inter - domain link between the domain PCE1 sends the PCRep message to reply to the S node PCC
the sub - PCE is responsible for and another domain , and with the path computation result, where the compressed SID
reports the Peer-to -Adj SID to the PCE4 through a BGP - LS . 25 list is included .
In step 160 , after the PCE4 receives the reported Binding
SIDs of all the sub - PCEs , the original complete TE path may Specific Embodiment Four
be represented by the compressed SID list and replied to the
PCE1 through the PCRep message , and the compressed SID The specific embodiment is basically the same as the
list in the embodiment may be : { 1000, Peer - Adj -SID - A1 A2 , 30 specific embodiment one , except that all domains have been
2000 , Peer -Adj - SID -A3A4, 3000 ). upgraded to support the segment routing function and that
In step 170 , after the PCE1 receives the PCRep message the RSVP - TE is no longer supported on the network . Now,
from the PCE4 , the PCE1 continues to send the PCInitiate the step in which the PCE1 initiatively creates one SR - TE
message to the S node PCC to trigger the instantiation of the tunnel from the source node S to destination node D includes
corresponding SR - TE tunnel on the S node, where the 35 the specific steps described below .
above -mentioned compressed SID list is included . In step 410 , the PCE1 initiatively creates the SR - TE
The corresponding SR - TE tunnel will be created on the S tunnel, the source nose is S , and the destination node is D.
node. When a forwarding table entry is generated for the The PCE1 finds, according to its own maintained TE data
SR - TE tunnel, the first SID , that is , 1000 , in the SID list
2 base (TED ) information , that the destination node D does
described above, will be replaced with the forwarding infor- 40 not belong to AS1 , and then the PCE1 sends the PCReq
mation about the corresponding RSVP - TE tunnel by search- message to the parent PCE ( PCE4 ) for requesting compu
ing the label table entry , and the other SIDs will remain tation of the cross - domain TE path . For a setting method of
unchanged . each field in the message , reference may be made to the RFC
In step 180 , on the S node , the packet sent to the 5440 and draft - ietf -pce - stateful-pce - 18 in combination with
above -mentioned SR - TE tunnel will be pressed onto the 45 the solution in the embodiment of the present application,
corresponding label stack : (RSVP - TE tunnel -SA1 label , and only the main information strongly related to the pro
Peer - Adj - SID - A1A2, 2000 , Peer-Adj- SID - A3A4, 3000 }, cessing flow in the embodiment of the present application is
that is , the top layer label is the outgoing label corresponding given below.
to the additionally created RSVP - TE tunnel for the path <RP object >: The PST is set to be 1 indicating path setup
segment in above -mentioned AS1 , the lower layer label is 50 using the segment routing technique; a CF flag is set to be
the Peer - Adj SID corresponding to the inter - domain link 2 , so as to perform compression by additionally creating an
A1 -A2 , the further lower layer label is the Binding SID RSVP - TE tunnel for the path segment within each AS .
corresponding to the additionally created RSVP - TE tunnel <END - POINTS object > : The source node is S , and the
for the path segment in AS2 , the further lower layer label is destination node is D.
the Peer -Adj SID corresponding to the inter - domain link 55 <LSP object >: The path - name is set to be path -name-SD
A3 -A4 , and the further lower layer label is the Binding SID 100 .
corresponding to the additionally created RSVP - TE tunnel Other objects such as constraints will not be described in
for the path segment in AS3 . The packet will be forwarded detail.
along a desired cross -domain TE path . In step 420 , after the PCE4 receives the request, the PCE4
60 firstly determines, according to the method described in
Specific Embodiment Two RFC 6805 , the domain where the destination node is located
is AS3 , and then determines a possible domain sequence . In
The specific embodiment is basically similar to the spe- the embodiment, only one domain sequence exists, that is
cific embodiment one , except that a deployment scenario in S-( AS1 ) -A1 -A2-( AS2 ) -A3- A4- ( AS3 ) -D . For the domain
which the SID is assigned by a forwarding device side and 65 sequence , the PCE4sends the PCReq message to the sub
is reported ( such as through the BGP - LS ) to the controller is PCE corresponding to each domain in the sequence, request
provided in the embodiment. Then, the PCE1 initiatively ing computation of the path segment within each domain .
 US 11,362,940 B2
19 20
For example, the PCE4 sends the PCReq message to the path -name -SD - 100- A4D , and accordingly, the PCInitiate
PCE1 for requesting computation of the path segment from message is sent to the PCE3 . Details are not described here
the source node S to the destination node A1 , and the main again .
information in the message is described below. In step 450 , after each sub - PCE receives the PCInitiate
< RP object> : The PST is set to be 1 indicating path setup 5 message from the PCE4, each sub - PCE will also initiatively
using the segment routing technique; a CF flag has to be set create the corresponding SR - TE tunnel internally and con
as 0 , denoting that the path is not compressed. tinue to send the PCInitiate message to the head node PCC
< END -POINTS object > : The source node is S , and the that of the tunnel. It is to be noted that in the PCInitiate message
destination node is A1 . each sub - PCE continues to deliver to the head node PCC
The PCE4 also sends the PCReq message to the PCE2 for 10 of thepathtunnel
-key., Each
the ERO
headobject
node includes a clearwillSIDgenerate
a
list, nota
requesting computation of the path segment from the source the
corresponding
of the tunnel
SR - TE tunnel, and the forwarding informa
node A2 to the destination node A3 and sends the PCReq tion is generated by using the corresponding SID list .
message to the PCE3 for requesting computation of the path In the embodiment, after each sub - PCE has created a
segment fromnotthedescribed
Details are source node
hereA4 to the
again . destination node D. 15 tiatively
corresponding SR-TE tunnel, each sub-PCE will also ini
assign the Binding SID to the SR - TE tunnel. For
In step 430 , after each sub - PCE receives the path com- example , the PCE1 assigns the Binding SID = 1000 to the
putation request from the PCE4 , the respective path segment above -mentioned created SR - TE tunnel, the PCE2 assigns
is computed and the PCRep message is sent to the PCE4 . In the Binding SID =2000 to the above -mentioned created
the embodiment, the PCE1 will compute the path segment 20 SR-TE tunnel, and the PCE3 assigns the Binding SID=3000
S - P1 - P2 -A1 , the PCE2 will compute the path segment to the above -mentioned created SR - TE tunnel. Each sub
A2 - P3 - P4 -A3 , and the PCE3 will compute the path segment PCE may deliver the Binding SID to the head node PCC of
A4 - P5 - P6 - D . In general, the path segment information is the tunnel along with the above -mentioned PCInitiate mes
provided in an ERO object included in a PCERep message sage or the subsequent PCUpd message , and may also report
with which each sub - PCE replies to the PCE4 , and may be 25 the Binding SID to the PCE4 along with the PCRpt message .
the IP address list , the SID list , the IP address and SID After receiving the Binding SID , each head node of the
combination list , or even may be a path -key for security tunnel will establish the label table entry with the Binding
reasons . However, in the embodiment, since the SR is SID as the key value to guide the packet to be forwarded to
supported by each AS , the path segment information the tunnel. The label operation is to exchange the incoming
returned by each sub - PCE to the PCE4 may be the SID list 30 label Binding SID into the outgoing label stack included in
or the path -key. the SR - TE tunnel.
In step 440 , for domain sequence S-(AS1 )-A1-A2-(AS2 )- It is to be noted that each sub - PCE also assigns the
A3 -A4- (AS3 ) -D , the PCE4 will obtain the complete end- Peer-Adj SID to an inter -domain link between the domain
to - end TE path after receiving the path segments of all the sub - PCE is responsible for and another domain, and
domains from all sub - PCEs . In the embodiment, since no 35 reports the Peer-Adj SID to the PCE4 through the BGP - LS .
other domain sequence exists, the above -mentioned com- In step 460 , after the PCE4 receives the reported Binding
plete TE path will serve as the optimal path . At the moment, SIDs of all the sub - PCEs , the original complete TE path may
the PCE4 does not immediately reply to the PCE1 with the be represented by the compressed SID list and replied to the
optimal complete TE path , but finds after checking that the PCE1 through the PCRep message , and the compressed SID
CF flag in the corresponding path computation request 40 list in the embodiment may be : { 1000 , Peer - Adj -SID - A1 A2 ,
received from the PCE1 is 2 , and then initiatively creates the 2000 , Peer - Adj -SID - A3A4, 3000 } .
SR - TE tunnel for each path segment and sends the PCIni- In step 470 , after the PCE1 receives the PCRep message
tiate message to each sub - PCE . For example, the PCE4 from the PCE4 , the PCE1 continues to send the PCInitiate
additionally creates a corresponding SR - TE tunnel inter- message to the S node PCC to trigger the instantiation of the
nally for a path segment S - P1 - P2 - A1 in AS1 . An included 45 corresponding SR - TE tunnel on the S node , where the
main path may be named path -name - SD - 100 - SA1 ( note: the above -mentioned compressed SID list is included.
naming method is to add head and tail key information , i.e. , The corresponding SR - TE tunnel will be created on the S
respectively S and A1 , of a child path to the tail of a parent node . When a forwarding table entry is generated for the
path name, i.e. , path -name - SD - 100, to ensure global unique- SR - TE tunnel, the first SID , i.e. , 1000 , in the above-men
ness ) . Accordingly, in the PCInitiate message sent from the 50 tioned SID list will be replaced with the forwarding infor
PCE4 to the PCE1 , the main information is as follows. mation ( generally a label stack ) about the corresponding
< SRP object > : The PST is set to be 1 indicating path setup SR - TE tunnel by searching the label table entry, and the
using the segment routing technique. other SIDs will remain unchanged .
<LSP object >: The path - name is set to be path -name-SD- In step 480 , on the S node, the packet sent to the
100 - SA1 . 55 above -mentioned SR - TE tunnel will be pressed onto the
< END - POINTS object >: The source node is S , and the corresponding label stack : { SR - TE tunnel -SA1 SID list ,
destination node is A1 . Peer - Adj-SID -A1A2, 2000, Peer- Adj-SID - A3A4, 3000 },
2

<ERO object > : S - P1 - P2 -A1 specifically may be the SID that is , the top layer label is the outgoing label stack
list or the path -key, that is , the path segment information corresponding to the additionally created SR - TE tunnel for
previously received from the PCE1 is filled in intact. 60 the path segment in above -mentioned AS1 , the lower layer
The PCE4 also additionally creates a corresponding SR- label is the Peer-Adj SID corresponding to the inter -domain
TE tunnel internally for a path segment A2 - P3 - P4 -A3 in link A1 -A2 , the further lower layer label is the Binding SID
2

AS2 . An included main path may be named path -name-SD- corresponding to the additionally created SR - TE tunnel for
100 - A2A3 , and accordingly, the PCInitiate message is sent the path segment in AS2 , the further lower layer label is the
to the PCE2 . The PCE4 also additionally creates the corre- 65 Peer -Adj SID corresponding to the inter -domain link A3 -A4 ,
sponding SR - TE tunnel internally for the path segment and the further lower layer label is the Binding SID corre
A4 -P5 -P6 - D in AS3 . An included main path may be named sponding to the additionally created SR - TE tunnel for the
 US 11,362,940 B2
21 22
path segment in AS3 . The packet will be forwarded along the <LSP object >: The path - name is set to be path -name-SD
desired cross - domain TE path . 100 .
Other objects such as constraints will not be described in
Specific Embodiment Five detail.
5 In step 720 , after the PCE4 receives the request, the PCE4
The specific embodiment is basically similar to the spe- first determines, according to the method described in RFC
cific embodiment four, except that the deployment scenario 6805 , that the domain where the destination node is located
in which the SID is assigned by a forwarding device side and is AS3 , and then determines the possible domain sequence .
is reported ( such as through the BGP - LS ) to the controller is
In the embodiment, only one domain sequence exists, that is
provided in the embodiment. Then, the PCE1 initiatively 10 Ssequence
- AS1)-A1 -A2-(AS2) -A3-A4-(AS3)-D . For the domain
, the PCE4 sends the PCReq message to the sub
establishes one cross - domain SR - TE tunnel from the source
node S to the destination node D , and the processes are ing PCE corresponding to each domain in the sequence, request
basically similar to those in the embodiment four, nothing computation of the path segment within each domain .
except that the Binding SID of the SR - TE tunnel addition 15 For example, the PCE4 sends the PCReq message to the
ally created for the path segment of each domain involved is source, requesting
PCE1 computation of the path segment from the
node S to the destination node A1 , and the main
assigned by the head node itself of the tunnel and reported information in the message is described below.
to the corresponding sub - PCE through the PCRpt message , <RP object >: The PST is set to be 1 indicating path setup
and that the sub - PCE continues to report the Binding SID to using the segment routing technique; the CF flag has to be
the PCE4 through the PCRpt message , and the other pro- 20 set as 0 indicating that the path is not compressed.
cesses are the same as those in the embodiment four. <END - POINTS object > : The source node is S , and the
destination node is A1 .
Specific Embodiment Six The PCE4 also sends the PCReq message to the PCE2 for
requesting computation of the path segment from the source
The specific embodiment is basically similar to the spe- 25 node A2 to the destination node A3 and sends the PCReq
cific embodiment four, except that the S node establishes one message to a PCE3 for requesting computation of the path
cross - domain SR - TE tunnel from the source node S to the segment from the source node A4 to the destination node D.
destination node D in the embodiment, and that the S node Details are not described here again .
PCC sends the PCReq message to the PCE1 , where the In step 730 , after each sub - PCE receives the path com
message is same as the PCReq message sent by the sub- 30 putation request from the PCE4 , the respective path segment
PCE1 to the PCE4 in the specific embodiment one , and the is computed and the PCRep message is sent to the PCE4 . In
other processes are the same as those in the embodiment the embodiment, the PCE1 will compute the path segment
one , and finally the PCE1 sends the PCRep message to reply S - P1 - P2 -A1 , the PCE2 will compute the path segment
to the S node PCC with the path computation result , where A2 - P3 - P4 -A3 , and the PCE3 will compute the path segment
the compressed SID list is included . 35 A4 - P5 - P6 - D . In general, the path segment information is
provided in the ERO object included in the PCERep mes
Specific Embodiment Seven sage with which each sub - PCE replies to the PCE4 , and may
be the IP address list , the SID list , and the IP address and SID
The specific embodiment is basically the same as the combination list , or even may be a path -key for security
specific embodiment one, except that all AS1s and AS2s 40 reasons . In the embodiment, since the SR is supported by
have been upgraded to support the segment routing function each AS1 and each AS2 , the path segment information
and no longer support the RSVP - TE , and that for the AS3 , returned by the PCE1 and the PCE2 to the PCE4 may be the
only boundary nodes are upgraded to support the segment SID list or the path -key. Since the SR is only supported by
routing function and that internal nodes still support the the boundary nodes of AS3 , the path segment information
RSVP - TE only. Now, the step in which the PCE1 initiatively
2 45 with which the PCE3 replies to the PCE4 may be the IP
creates one SR - TE tunnel from the source node S to desti- address list or the path -key.
nation node D includes the specific steps described below . In step 740 , for domain sequence S-(AS1)-A1-A2-(AS2 )
In step 710 , the PCE1 initiatively creates the SR - TE A3 -A4 - AS3 ) -D , the PCE4 will obtain the complete end
tunnel, the source node is S , and the destination node is D. to - end TE path after receiving the path segments of all
The PCE1 finds, according to its own maintained TE data- 50 domains from all sub - PCEs . In the embodiment, since no
base (TED ) information, that the destination node D does other domain sequence exists, the above -mentioned com
not belong to AS1 , and then the PCE1 sends a PCReq plete TE path will serve as the optimal path . At the moment,
message to the parent PCE (PCE4 ) for requesting compu- the PCE4 does not immediately reply to the PCE1 with the
tation of the cross - domain TE path . For disposing setting optimal complete TE path , but finds after checking that the
method of each field in the message, reference may be made 55 CF flag in the corresponding path computation request
to the RFC 5440 and draft - ietf -pce - stateful- pce - 18 in com- received from the PCE1 is 3 , and then initiatively creates the
bination with the solution in the embodiment of the present TE tunnel ( the RSVP - TE tunnel or the SR - TE tunnel) for
application, and only the main information strongly related each path segment and sends the PCInitiate message to each
to the processing flow in the embodiment of the present sub - PCE . For example, the PCE4 additionally creates the
application is given below . 60 corresponding TE tunnel internally for the path segment
< RP object > : The PST is set to be 1 indicating path setup S - P1 - P2 -A1 in AS1 . An included main path may be named
using the segment routing technique; the CF flag is set to be path -name -SD -100 - SA1 ( note : the naming method is to add
3 , so as to perform compression by additionally creating the head and tail key information , i.e. , respectively S and A1 of
RSVP - TE tunnel or the SR - TE tunnel for the path segment the child path to the tail of a parent path name, i.e. ,
within each AS according to actual abilities. 65 path -name -SD - 100 to ensure global uniqueness ). Accord
< END -POINTS object > : The source node is S , and the ingly , in the PCInitiate message sent from the PCE4 to the
destination node is D. PCE1 , the main information is as follows.
 US 11,362,940 B2
23 24
< SRP object >: The PST is set to be 2 indicating path setup In step 760 , after the PCE4 receives the reported Binding
2

using the RSVP - TE signaling or the segment routing tech-
nique .
<LSP object >: The path -name is set to be path -name-SD-
100 - SA1 .
< END - POINTS object >: The source node is S , and the
destination node is A1 .
<ERO object > : S - P1 - P2 -A1 specifically may be the SID
list or the path -key, that is , the path segment information
previously received from the PCE1 is filled in intact. 10
The PCE4 also additionally creates the corresponding TE
tunnel internally for the path segment A2 - P3 - P4 -A3 in AS2 .
An included main path may be named path -name-SD - 100
A2A3 , and accordingly, the PCInitiate message is sent to the 15
PCE2 . The PCE4 also additionally creates the corresponding
TE tunnel internally for the path segment A4 - P5 - P6 - D in
AS3 . An included main path may be named path -name-SD
100 - A4D , and accordingly, the PCInitiate message is sent to
SIDs of all the sub - PCEs, the original complete TE path may
be represented by the compressed SID list and replied to the
PCE1 through the PCRep message , and the compressed SID
5 list in the embodiment may be : { 1000 , Peer - Adj -SID - A1 A2 ,
2000 , Peer - Adj -SID -A3A4 , 3000 } .
In step 770 , after the PCE1 receives the PCRep message
from the PCE4 , the PCE1 continues to send the PCInitiate
message to the S node PCC to trigger the instantiation of the
corresponding SR - TE tunnel on the S node , where the
compressed SID list is included .
The corresponding SR - TE tunnel will be created on the S
node . When the forwarding table entry is generated for the
SR - TE tunnel, the first SID , that is , 1000 , in the SID list
described above will be replaced with the forwarding infor
mation ( generally one label stack) about the corresponding
SR - TE tunnel by searching the label table entry, and the
other SIDs will remain unchanged .
In step 780 , on the S node, the packet sent to the
2

the PCE3 . Details are not described here again . 20 above -mentioned SR - TE tunnel will be pressed onto the
In step 750 , after the PCE1 and the PCE2 respectively corresponding label stack : { SR - TE tunnel -SA1 SID list ,
receive the PCInitiate messages from the PCE4 , the PCE1 Peer- Adj - SID - A1A2, 2000 , Peer -Adj -SID -A3A4 , 3000 },
and the PCE2 will respectively and initiatively create the that the top layer label is the outgoing label stack
SR - TE tunnel internally according to their respective self- corresponding to the additionally created SR - TE tunnel for
ability and respectively continue to send the PCInitiate 25
message to the head node PCC of the tunnel. After the PCE3
the path segment in above -mentioned AS1 , the lower layer
label is the Peer - Adj SID corresponding to the inter - domain
receives the PCInitiate message from the PCE4 , the PCE3 link A1 -A2 , the further lower layer label is the Binding SID
initiatively creates the corresponding RSVP - TE tunnel inter- corresponding to the additionally created SR - TE tunnel for
nally according to the self -ability and continues to send the the path segment in AS2 , the further lower layer label is the
PCInitiate message to the head node PCC of the tunnel. It is 30 Peer - Adj SID corresponding to the inter - domain link A3 -A4 ,
to be noted that in the PCInitiate message that aa sub - PCE1 and the further lower layer label is the Binding SID corre
and a sub -PCE2 continue to send to the head node PCC of sponding to the additionally created RSVP - TE tunnel for the
the tunnel, the ERO object includes the clear SID list not the path segment in AS3 . The packet will be forwarded along the
path -key. In the PCInitiate message that a sub - PCE3 con- desired cross - domain TE path .
tinues to send to the head node PCC of the tunnel, the ERO 35
object includes a clear SID list , not the path -key. The head Embodiment Five
nodes of the tunnels in AS1 and AS2 will respectively
generate the corresponding SR - TE tunnel, and the forward- From the description of the above -mentioned embodi
ing information is generated using the respective SID list . ments , it will be apparent to those skilled in the art that the
The head node of the tunnel in AS3 will generate the 40 method in the embodiments described above may be imple
corresponding RSVP - TE tunnel, and establish the path mented by software plus a necessary general-purpose hard
within the network through the RSVP - TE signaling and ware platform , or may of course be implemented by hard
negotiate labels . ware . However, in many cases , the former is a preferred
In the specific embodiment, after each sub - PCE has implementation mode . Based on this understanding, the
created the corresponding SR - TE tunnel or RSVP - TE tun- 45 solution provided by the present application substantially, or
nel , each sub -PCE will also initiatively assign the Binding the part contributing to the existing art, may be embodied in
SID to the TE tunnel. For example , the PCE1 assigns the the form of a software product. The computer software
Binding SID = 1000 to the above -mentioned created SR - TE product is stored on a storage medium ( such as a read -only
tunnel, the PCE2 assigns the Binding SID =2000 to the memory (ROM )/ random access memory (RAM ), a magnetic
above-mentioned created SR - TE tunnel, and the PCE3 50 disk or an optical disk ) and includes several instructions for
assigns the Binding SID =3000 to the above -mentioned enabling a terminal device (which may be aa mobile phone ,
created RSVP - TE tunnel. Each sub - PCE may deliver the a computer, a server or a network device) to execute the
Binding SID to the head node PCC of the tunnel along with method according to each embodiment of the present appli
the above -mentioned PCInitiate message or the subsequent cation .
PCUpd message , and may also be reported to the PCE4 55 The present embodiment further provides an apparatus for
along with the PCRpt message . After receiving the Binding determining identification information about a cross -domain
SID , each head node of the tunnel will establish the label path . The apparatus is used for implementing the above
table entry with the Binding SID as the key value to guide mentioned embodiments and preferred embodiments . What
the packet to be forwarded to the tunnel. The label operation has been described will not be repeated. As used below, the
is to exchange the incoming label Binding SID into the 60 term “ module ” may be software, hardware or a combination
corresponding outgoing label stack included in the SR - TE thereof capable of implementing predetermined functions .
tunnel or into the outgoing label included in the RSVP - TE The apparatus in the embodiments described below is pref
tunnel . erably implemented by software, but implementation by
It is to be noted that each sub -PCE also assigns the hardware or by a combination of software and hardware is
Peer -Adj SID to the inter - domain link between the domain 65 also possible and conceived .
the sub - PCE is responsible for and another domain , and FIG . 7 is a structure diagram of a first apparatus for
reports the Peer -Adj SID to the PCE4 through the BGP - LS . determining identification information about a cross - domain
 US 11,362,940 B2
25 26
path according to an embodiment of the present application. In an optional embodiment, the above -mentioned appa
As shown in FIG . 7 , the apparatus includes aa first receiving ratus further includes a returning module, which is config
module 72 , an instruction module 74 and a second receiving ured to return the compressed identification information
module 76. The apparatus is described below . about the path to the first sub - PCE after the compressed
The first receiving module 72 is configured to receive a 5 identification information about the one or more path seg
path computation request from a first path computation ments are combined into the compressed identification infor
element PCE . The path computation request is used for mation about the path according to the above -mentioned
making a request to acquire a path from a source node to a identification information about the path . In other words, in
destination node , and the source node and the destination response to the path computation request sent by the first
node are located in different domains . The above -mentioned 10 sub - PCE, the compressed identification information about
path includes one or more path segments, and the above- the path is returned to the first sub - PCE , and the first
mentioned path computation request carries a compression sub - PCE may continue to perform subsequent operations
identifier for identifying compression of the one or more after acquiring the compressed identification information
path segments and a path setup type (PST ) . The instruction about the path . For example, the first sub - PCE may send the
module 74 is connected to the first receiving module 72 and 15 acquired compressed identification information about the
configured to instruct, according to the compression identi- path to the corresponding PCC , and the PCC encapsulates a
fier and the PST, each of sub - PCEs corresponding to the one packet according to the identification information about the
or more path segments to compress identification informa- path , and forwards the packet .
tion about a respective one of the one or more path segments FIG . 8 is a structure diagram of a second apparatus for
after identification information about the path from the
source node to the destination node is acquired. The second
20 determining identification information about a cross - domain
path according to an embodiment of the present application .
receiving module 76 is connected to the instruction module As shown in FIG . 8 , the apparatus includes a sending
74 and configured to receive the compressed identification module 82 , a third receiving module 84 , a compression
information about the one or more path segments returned module 86 and a first returning module 88. The apparatus is
by the each of sub - PCEs corresponding to the one or more 25 described below .
path segments, and combine , according to the identification The sending module 82 is configured to send a path
information about the path , the compressed identification computation request to a parent path computation element
information about the one or more path segments into the (PCE ) , where the path computation request is used for
identification information about the path. making a request to acquire a path from the source node to
In an optional embodiment, the instruction module 74 30 the destination node , the source node and the destination
includes a sending element configured to send a creation node are located in different domains, the path includes one
message to the each of sub - PCEs corresponding to the one or more path segments, and the path computation request
or more path segments according to the compression iden- carries the compression identifier for identifying compres
tifier, where the creation message is used for requesting the sion of the one or more path segments and the path setup
each of sub - PCEs corresponding to the one or more path 35 type (PST ) . The third receiving module 84 is connected to
segments to create a tunnel and assign a binding segment- the sending module 82 and configured to receive a creation
identification ( Binding SID ) to the created tunnel. The message from the parent PCE , where the creation message
creation message carries path information about the one or is sent by the parent PCE according to the compression
more path segments. identifier and the PST. The compression module 86 is
In an optional embodiment, the above -mentioned creation 40 connected to the third receiving module 84 and configured
message being used for requesting the each of sub - PCEs to compress identification information about a path segment
corresponding to the one or more path segments to create the according to the above -mentioned creation message . The
tunnel includes one of the following: the above -mentioned first returning module 88 is connected to the compression
creation message is used for requesting the each of sub- module 86 and configured to return the compressed identi
PCEs corresponding to the one or more path segments to 45 fication information about the one or more path segments to
create a Resource Reservation Protocol- Traffic Engineering the parent PCE .
( RSVP - TE ) tunnel; the above -mentioned creation message In an optional embodiment, the compression module 86
is used for requesting the each of sub - PCEs corresponding includes : a determination element, which is configured to
to the one or more path segments to create a Segment determine path information about the one or more path
Routing technology - Traffic Engineering (ST- TE ) tunnel; or 50 segments carried in the above -mentioned creation message ;
the above -mentioned creation message is used for requesting and a creation element, which is configured to create a
the each of sub - PCEs corresponding to the one or more path tunnel according to the path information , and assign a
segments to create the RSVP - TE tunnel or the SR - TE binding segment - identification (Binding SID ) to the created
tunnel. tunnel.
In an optional embodiment, the second receiving module 55 In an optional embodiment, the above -mentioned creation
76 is configured to receive a Binding SID assigned to the message is used for making a request to create at least one
created tunnel and returned by the each of sub - PCEs corre- of following tunnel: the Resource Reservation Protocol
sponding to the one or more path segments; and combine the Traffic Engineering (RSVP - TE ) tunnel; or the Segment
received Binding SIDs returned by the sub - PCEs corre- Routing - Traffic Engineering ( ST - TE ) tunnel. It is to be noted
sponding to the one or more path segments into the com- 60 that the embodiment about the RSVP -TE tunnel and the
pressed identification information about the path . embodiment about the SR - TE tunnel are merely two pre
In an optional embodiment, the above -mentioned path ferred embodiments, and other types of tunnels may be
2

information includes the following contents : a path name of created according to actual conditions and technological
the path, segment information about the one or more path developments , and are not limited herein .
segments , starting node information and destination node 65 In an optional embodiment, the above -mentioned creation
information about the tunnel to be created , and the above- element is configured to instantiate the tunnel according to
mentioned PST. the path information and forward the creation message to a
 US 11,362,940 B2
27 28
path computation client (PCC ) as a starting node of the Apparently, it should be understood by those skilled in the
tunnel to be created . The creation message is used for art that each of the above -mentioned modules or steps of the
instructing the PCC to initiate , according to the path infor- present application may be implemented by a general
mation , a process of creating the tunnel. In the embodiment, purpose computing apparatus, the modules or steps may be
the tunnel is created by the PCC . 5 concentrated on a single computing apparatus or distributed
In an optional embodiment, when the types of tunnels to on a network composed of multiple computing apparatuses,
be created are different, specific operations the PCC is and alternatively, the modules or steps may be implemented
instructed to perform are also different. Optionally, when the by program codes executable by the computing apparatus,
above -mentioned creation message is used for making a so that the modules or steps may be stored in a storage
request to create the RSVP - TE tunnel, the creation message 10 apparatus and executed by the computing apparatus. In some
is used for instructing the PCC to initiate an RSVP - TE circumstances, the illustrated or described steps may be
signaling setup path ; and optionally, when the creation executed in sequences different from those described herein ,
message is used for making a request to create the SR - TE or the modules or steps may be made into various integrated
tunnel, the creation message is used for instructing the PCC circuit modules separately, or multiple modules or steps
to compute forwarding information about the path according 15 therein may be made into a single integrated circuit module
to segment routing information . for implementation . In this way, the present application is
In an optional embodiment, how to assign the Binding not limited to any specific combination of hardware and
SID to the created tunnel is described as follows: in condi- software.
tion that a segment - identification ( SID ) is assigned by a The above are only preferred embodiments of the present
controller globally and uniformly, after the tunnel is instan- 20 application and are not intended to limit the present appli
tiated according to the path information , the Binding SID is cation, and for those skilled in the art, the present application
assigned to the tunnel and reported to the parent PCE and the may have various modifications and variations. Any modi
above-mentioned PCC ; and /or in condition that the SID is fications, equivalent substitutions, improvements and the
assigned by a forwarding device and where the assigned SID like made within the principle of the present application
is reported to the controller, the creation element receives the 25 should fall within the scope of the present application .
Binding SID assigned by the PCC to the tunnel after the What is claimed is :
tunnel is created , and reports the Binding SID to the parent 1. A method for determining identification information
PCE . about a cross - domain path , comprising:
In an optional embodiment, the above -mentioned appa- receiving a path computation request from a first child
ratus further includes : a fourth receiving module, a second 30 path computation element ( PCE ) , wherein the path
returning module and a third returning module . The fourth computation request is used for making a request to
receiving module is connected to the first returning module acquire a path from a source node to a destination node ,
88 and configured to receive compression identification wherein the source node and the destination node are
information about the path from the parent PCE after the located in different domains , wherein the path com
compressed identification information about the one or more 35 prises one or more path segments, and the path com
path segments is returned to the parent PCE . The second putation request carries a compression identifier for
returning module is connected to the fourth receiving mod- identifying compression of the one or more path seg
ule and configured to return the compressed identification ments and a path setup type ( PST ) ;
information about the path to a predetermined path compu- after identification information about the path from the
tation client (PCC ) , in condition that the path computation 40 source node to the destination node is acquired ,
request is initiated by a predetermined PCC . The third instructing, according to the compression identifier and
returning module is connected to the second returning the PST, each of sub - PCEs corresponding to the one or
module and configured to send the compressed identification more path segments to compress identification infor
information about the path to aa PCC as a starting node of the mation about a respective one of the one or more path
tunnel, in condition that the path computation request is not 45 segments ; and
initiated by the predetermined PCC . receiving the compressed identification information about
It is to be noted that the various modules described above the respective one of the one or more path segments
may be implemented by software or hardware . Implemen- returned by each of the sub - PCEs corresponding to the
tation by hardware may, but may not necessarily, be per- one or more path segments, and combining, according
formed in the following manners : the various modules 50 to the identification information about the path , the
described above are located in the same processor, or the compressed identification information about the one or
various modules described above are located in their respec more path segments into compressed identification
tive processors in any combination form . information about the path ;
An embodiment of the present application further pro- wherein the PST comprises path setup using Resource
vides a storage medium . The storage medium includes 55 Reservation Protocol - Traffic Engineering (RSVP - TE )
stored programs which , when run , execute the method signaling and path setup using a segment routing tech
according to any embodiment described above . nique, the compressed identification information about
Optionally, in the embodiment, the storage medium the path comprises a segment - identification ( SID ) list ,
described above may include, but is not limited to , a USB the SID list comprises Binding SIDs .
flash disk , a Read - Only Memory (ROM) , a Random Access 60 2. The method of claim 1 , wherein the instructing, accord
Memory (RAM ), a mobile hard disk, a magnetic disk , an ing to the compression identifier, each of the sub - PCEs
optical disk or various other media capable of storing corresponding to the one or more path segments to compress
program codes. the identification information about the respective one of the
The embodiment of the present application further pro- one or more path segments comprises:
vides a processor. The processor is configured to run pro- 65 sending, according to the compression identifier, a cre
grams which, when run , perform the steps of any above- ation message to each of the sub -PCEs corresponding
mentioned method . to the one or more path segments, wherein the creation
 US 11,362,940 B2
29
message is used for requesting each of the sub - PCEs
corresponding to the one or more path segments to
create a tunnel and assign a Binding SID to the created
tunnel, wherein the creation message carries path infor-
mation about the one or more path segments .
3. The method of claim 2 , wherein the creation message
being used for requesting each of the sub - PCEs correspond
ing to the one or more path segments to create the tunnel
comprises one of the following :
30
wherein the PST comprises path setup using Resource
Reservation Protocol - Traffic Engineering (RSVP - TE )
signaling and path setup using a segment routing tech
nique, compressed identification information about the
5 path formed by combining the compressed identifica
tion information about the one or more path segments
comprises a segment- identification ( SID ) list , the SID
list comprises Binding SIDs.
8. The method of claim 7 , wherein the compressing,
.

the creation message is used for requesting each of the 10 according to the creation message , the identification infor
sub - PCEs corresponding to the one or more path seg mation about the one or more path segments comprises :
ments to create a RSVP - TE tunnel; determining path information about the one or more path
the creation message is used for requesting each of the segments carried in the creation message ; and
sub - PCEs corresponding to the one or more path seg- creating a tunnel according to the path information and
ments to create a Segment Routing - Traffic Engineering 15 assigning a Binding SID to the created tunnel .
( SR - TE ) tunnel; or 9. The method of claim 8 , wherein the creation message
the creation message is used for requesting each of the is used for making a request to create at least one of
sub - PCEs corresponding to the one or more path seg- following tunnels:
ments to create the RSVP - TE tunnel or the SR - TE a RSVP - TE tunnel, or a Segment Routing - Traffic Engi
tunnel. 20 neering ( SR -TE ) tunnel.
4. The method of claim 2 , wherein receiving the com- 10. The method of claim 9 , wherein the creating the tunnel
pressed identification information about the one or more according to the path information comprises:
path segments returned by each of the sub - PCEs correspond- instantiating the tunnel according to the path information,
ing to the one or more path segments, and combining the and forwarding the creation message to a path compu
compressed identification information about the one or more 25 tation client (PCC ) as a starting node of the tunnel to be
path segments into the compressed identification informa- created , wherein the creation message is used for
tion about the path comprises: instructing the PCC to initiate a process of creating the
receiving the Binding SID assigned to the created tunnel tunnel according to the path information .
and returned by each of the sub - PCEs corresponding to 11. The method of claim 10 , comprising one of the
the one or more path segments ; and 30 following:
combining received Binding SIDs returned by the sub- when the creation message is used for making a request to
PCEs corresponding to the one or more path segments create the RSVP - TE tunnel, the creation message is
into the compressed identification information about used for instructing the PCC to initiate an RSVP - TE
the path . signaling setup path ; or
5. The method of claim 2 , wherein the path information 35 when the creation message is used for making a request to
comprises following contents : create the SR - TE tunnel, the creation message is used
a path name of the path , segment information about the for instructing the PCC to compute forwarding infor
one or more path segments, starting node information mation about the path according to segment routing
and destination node information about the tunnel to be information.
created , and the PST. 40 12. The method of claim 10 , wherein assigning the
6. The method of claim 1 , wherein after the combining, Binding SID to the created tunnel comprises:
according to the identification information about the path , in condition that the SID is assigned by a controller
the compressed identification information about the one or globally and uniformly , assigning the Binding SID to
more path segments into the compressed identification infor- the tunnel and reporting the Binding SID to the parent
mation about the path , the method comprises : 45 PCE and the PCC after the tunnel is instantiated
returning the compressed identification information about according to the path information; and /or
the path to the first sub - PCE . in condition that the SID is assigned by a forwarding
7. A method for determining identification information device and the assigned SID is reported to the control
about a cross - domain path , comprising: ler, receiving the Binding SID assigned by the PCC to
sending a path computation request to a parent path 50 the tunnel after the PCC creates the tunnel, and report
computation element (PCE ) , wherein the path compu- ing the Binding SID to the parent PCE .
tation request is used for making a request to acquire a 13. The method of claim 8 , wherein after the returning the
path from a source node to a destination node , wherein compressed identification information about the one or more
the source node and the destination node are located in path segments to the parent PCE , the method further com
different domains, wherein the path comprises one or 55 prises:
more path segments , and the path computation request receiving compressed identification information about the
carries a compression identifier for identifying com path from the parent PCE ;
pression of the one or more path segments and a path in condition that the path computation request is initiated
setup type (PST) ; by a predetermined path computation client ( PCC ) ,
receiving a creation message from the parent PCE , 60 returning the compressed identification information
wherein the creation message is sent by the parent PCE about the path to the predetermined PCC ; and
according to the compression identifier and the PST ; in condition that the path computation request is not
compressing, according to the creation message , identi- initiated by the predetermined PCC , sending the com
fication information about the one or more path seg pressed identification information about the path to a
ments; and 65 PCC as a starting node of the tunnel.
returning the compressed identification information about 14. An apparatus for determining identification informa
the one or more path segments to the parent PCE ; tion about a cross - domain path , comprising:
 US 11,362,940 B2
31 32
at least one processor ; and a memory for storing instruc- 16. The apparatus of claim 15 , wherein the creation
tions executable by the at least one processor, wherein message being used for requesting each of the sub - PCEs
the at least one processor is configured to perform : corresponding to the one or more path segments to create the
receiving a path computation request from a first child tunnel comprises one of the following:
path computation element (PCE ) , wherein the path 5 the creation message is used for requesting each of the
computation request is used for making a request to sub - PCEs corresponding to the one or more path seg
acquire a path from a source node to aa destination node, ments to create a RSVP - TE tunnel;
wherein the source node and the destination node are the creation message is used for requesting each of the
located in different domains , wherein the path com sub - PCEs corresponding to the one or more path seg
prises one or more path segments , and the path com- 10 ments to create a Segment Routing - Traffic Engineering
putation request carries a compression identifier for ( SR - TE ) tunnel ; or
identifying compression of the one or more path seg the creation message is used for requesting each of the
ments and a path setup type (PST) ; sub - PCEs corresponding to the one or more path seg
after identification information about the path from the ments to create the RSVP - TE tunnel or the SR - TE
source node to the destination node is acquired, 15 tunnel.
instructing , according to the compression identifier and 17. The apparatus of claim 15 , wherein the receiving the
the PST , each of sub - PCEs corresponding to the one or compressed identification information about the one or more
more path segments to compress identification infor path segments returned by the each of the sub - PCEs corre
mation about a respective one of the one or more path
segments; and 20 sponding to the one or more path segments, and combining
receiving the compressed identification information about the compressed identification information about the one or
the respective one of the one or more path segments more path segments into the compressed identification infor
returned by each of the sub - PCEs corresponding to the mation about the path comprises:
one or more path segments , and combining, according receiving the Binding SID assigned to the created tunnel
to the identification information about the path , the 25 and returned by each of the sub - PCEs corresponding to
compressed identification information about the one or the one or more path segments ; and
more path segments into compressed identification combining received Binding SIDs returned by the sub
information about the path ; PCEs corresponding to the one or more path segments
wherein the PST comprises path setup using Resource into the compressed identification information about
Reservation Protocol- Traffic Engineering (RSVP - TE ) 30 18.theThepathapparatus
.
of claim 15 , wherein the path informa
signaling and path setup using a segment routing tech
nique , the compressed identification information about tiona path comprises following contents:
name of the path, segment information about the
the path comprises a segment- identification ( SID ) list , one or more path segments, starting node information
the SID list comprises Binding SIDs . and destination node information about the tunnel to be
15. The apparatus of claim 14 , wherein the instructing, 35
according to the compression identifier, each of the sub- created , and the PST.
PCEs corresponding to the one or more path segments to combining 19. The apparatus of the claim 14 , wherein after the
compress the identification information about the respective , according to the identification information about
one of the one or more path segments comprises: the path , the compressed identification information about the
sending, according to the compression identifier, a cre- 40 one or more path segments into the compressed identifica
ation message to each of the sub - PCEs corresponding tionreturning
information about the path , further comprising:
the compressed identification information about
to the one or more path segments, wherein the creation the path to the first sub - PCE .
message is used for requesting each of the sub - PCEs 20. A non - transitory storage medium , comprising stored
corresponding to the one or more path segments to
create a tunnel and assign a Binding SID to the created 45 programs which, when executed , execute the method of any
tunnel, wherein the creation message carries path infor one of claims 1 to 13 .
mation about the one or more path segments .