WO2019007166A1 - 跨域的路径的标识信息的确定方法、装置及存储介质 - Google Patents

跨域的路径的标识信息的确定方法、装置及存储介质 Download PDF

Info

Publication number
WO2019007166A1
WO2019007166A1 PCT/CN2018/088880 CN2018088880W WO2019007166A1 WO 2019007166 A1 WO2019007166 A1 WO 2019007166A1 CN 2018088880 W CN2018088880 W CN 2018088880W WO 2019007166 A1 WO2019007166 A1 WO 2019007166A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
tunnel
pce
segment
identification information
Prior art date
Application number
PCT/CN2018/088880
Other languages
English (en)
French (fr)
Inventor
彭少富
金飞蔡
祝沈财
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to ES18827949T priority Critical patent/ES2942465T3/es
Priority to US16/623,613 priority patent/US11362940B2/en
Priority to EP18827949.1A priority patent/EP3651423B1/en
Publication of WO2019007166A1 publication Critical patent/WO2019007166A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/26—Route discovery packet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/42—Centralised routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H04L45/507—Label distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/821—Prioritising resource allocation or reservation requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/825—Involving tunnels, e.g. MPLS

Definitions

  • the present application relates to the field of communications, and in particular, to a method, an apparatus, and a storage medium for determining identification information of a cross-domain path.
  • RFC5623 discusses the use of the Path Computation Element (PCE) architecture to calculate the traffic engineering (Traffic Engineering, TE for short) path.
  • the parent PCE can obtain all domains from each sub-PCE. Maintain a domain-level topology by connecting relationships.
  • the parent PCE When the parent PCE is requested by a sub-PCE to calculate the TE path across the domain, the parent PCE first determines which domain sequence the TE path may pass according to the domain-level topology, and then requests each sub-PCE to calculate the corresponding domain for each domain sequence.
  • the path fragment after the parent PCE receives the calculation result of each sub-PCE, splicing all the path segments to obtain a complete TE path across the domain.
  • the parent PCE will pick an optimal path from the complete TE path corresponding to the domain sequence to the sub-PCE requesting the path of the calculation, and the latter will reply the path to the corresponding path calculation client (Path Computation Client, PCC for short). ).
  • the draft-ietf-pce-segment-routing-09 discusses how the PCE uses the segmented list segment list to represent the scenario in which the segmentation route is forwarded.
  • a strictly explicit next hop in a domain in a TE path may be represented by a neighboring adjacency SID (ie, a segment identifier segment-id) of the segmentation route, and a domain between the TE paths.
  • a strict explicit next hop can be represented by the Peer-Adj SID of the segmentation route.
  • the Path Setup Type can be specified as "establishing a path using the segmentation routing technology", and the parent PCE is directed to each domain sequence.
  • the PST is also specified as "establishing a path using the segmentation routing technology", and the path fragment information that each sub-PCE replies to the parent PCE can be represented by an adjacency SID list, and the parent PCE will eventually be optimal.
  • the adjacency SID+Peer-Adj SID list can also be used to represent the complete TE path when the path is replied to the sub-PCE that requested it to calculate the path.
  • each sub-PCE may not return the path fragment information in the domain to the parent PCE according to the local policy.
  • RFC 5520 defines the concept and mechanism of path-key, and the sub-PCE may replace the explicit route with path-key.
  • the path fragment information in the reply is returned to the parent PCE, and the head node PCC of the final TE path will not be able to obtain the complete adjacency SID+Peer-Adj SID list.
  • the binding-ietf-spring-segment-routing-11 defines a binding segment binding segment, which can be used to refer to the forwarding information of a tunnel tunnel, that is, if If a path fragment in the complete TE path itself creates an additional tunnel, the path fragment can be represented by the corresponding binding segment identifier Binding SID. Based on this idea, many protocols have been extended accordingly, such as:
  • draft-ietf-isis-segment-routing-extensions-12 extends the intermediate system to intermediate system (ISIS) and defines the SID/Label Binding TLV (where T is The tag Tag, L is the length Length, V is the value Value) and its usage.
  • this method only defines the Binding SID/Label for the SR-TE path (that is, the TE path established by using the segmentation routing technology), and does not define the RSVP-TE path of the resource reservation protocol establishment path based on the traffic engineering extension (ie, use The TE path established by RSVP-TE signaling is corresponding to the Binding SID/Label.
  • the Interior Gateway Protocol (IGP) adjacency SID may be allocated. Not Binding SID). In addition, this method is only applicable to the IGP area area, and the TE path across the domain is not applicable.
  • IGP Interior Gateway Protocol
  • BGP-LS Gateway Protocol-Link State
  • the information about the ERO (Explicit Route Object) corresponding to the path fragment is given along with the Binding SID, and as mentioned above, the sub-PCE does not necessarily expose the path fragment information in the domain to the parent PCE, so
  • the method is only applicable to the PCC reporting the Binding SID to the child PCE, and is not applicable to the child PCE reporting the Binding SID to the parent PCE.
  • the method is generally only used for the PCC to synchronize data to the PCE direction, and is not applicable to the tunnel actively created by the PCE.
  • the method only describes how the BGP-LS acts as a channel to carry the Binding SID, and does not pay attention to the solution for the TE path calculation and packet forwarding across the domain.
  • the method involves multiple channels, from the PCC to the PCE direction, a BGP-LS-like PCE-LS (see draft-dhodylee-pce-pcep-ls-07) is advertised, and from the PCE to the PCC direction is Similar to NETCONF's PCLabelUpd (see draft-zhao-pce-pcep-extension-for-pce-controller-04), although both are nominally PCEP extension protocols, the differences are large and complex to implement and deploy. Similarly, this method only describes how the PCEP advertises the tunnel segment as a channel, and does not pay attention to the solution for the TE path calculation and message forwarding across the domain.
  • the protocol-sivabalan-pce-binding-label-sid-02 also extends the PCEP protocol to advertise the Binding label for the RSVP-TE path, and the Binding SID for the SR-TE path, and the PCC reports the binding label/SID to the PCE.
  • This method is only used to synchronize data between the PCC and the PCE. It is not applicable to the tunnel that the PCE actively creates. Similarly, this method only describes how the PCEP advertises the binding label/SID as a channel, and does not care about the solution for TE path calculation and message forwarding across domains.
  • the embodiment of the present application provides a method, an apparatus, and a storage medium for determining identification information of a cross-domain path, so as to at least solve the problem that the path identification information existing in the related art is too long.
  • a method for determining identification information of a path of a domain domain comprising: receiving a path calculation request from a first sub-path computing unit PCE, wherein the path calculation request is used for a request Obtaining a path from the source node to the destination node, where the source node and the destination node are located in different domains, the path includes one or more path segments, and the path calculation request carries identifiers for identifying the path segments Compressing the compression identifier and the path establishment type PST; after acquiring the identification information of the path of the source node to the destination node, indicating the corresponding sub-PCE pairs corresponding to the path segments according to the compression identifier and the PST The identification information of the path segment is compressed; the identification information of the compressed path segment returned by the sub-PCE corresponding to each path segment is received, and the information of the compressed path segment is composed of the compressed information according to the identification information of the path.
  • the identification information of the path is received from a first sub-path computing unit PCE, wherein
  • the compressing by the sub-PCE corresponding to each path segment, the identification of the identification information of the corresponding path segment by the sub-PCEs, according to the compression identifier, sending a creation message to the sub-PCE corresponding to each path segment according to the compression identifier, where The creation message is used to request a sub-PCE corresponding to each path segment to create a tunnel tunnel, and a binding segment identifier Binding SID is assigned to the created tunnel, where the creation message carries the path information of the path segment.
  • the creating message is used to request the sub-PCE corresponding to each path segment to create a tunnel tunnel, including one of the following: the creating message is used to request a sub-PCE corresponding to each path segment to create a resource reservation protocol based on traffic engineering extension. Establishing a path of the RSVP-TE tunnel; the creation message is used to request the sub-PCE corresponding to each path segment to create an SR-TE tunnel based on the segmentation routing technology; the creation message is used to request the sub-PCE corresponding to each path segment Create an RSVP-TE tunnel or an SR-TE tunnel.
  • the identifier information of the compressed path segment returned by the sub-PCE corresponding to each path segment is received, and the identifier information of the compressed path segment is formed into the compressed identifier information of the path, including: receiving each path segment The corresponding sub-PCE returns the Binding SID assigned to the created tunnel; each received Binding SID is composed of the compressed identification information of the path.
  • the path information includes: a path name of the path, segment information of the path segment, start node information of the tunnel to be created, and destination node information, the PST.
  • the method includes: marking the compressed path Information is returned to the first sub-PCE.
  • a method for determining identification information of a path of a domain domain including: sending a path calculation request to a parent path calculation unit PCE, wherein the path calculation request is used to request acquisition a path from the source node to the destination node, where the source node and the destination node are located in different domains, the path includes one or more path segments, and the path calculation request carries identifiers for identifying the path segments.
  • a compressed compression identifier and a path establishment type PST receiving a creation message from the parent PCE, wherein the creation message is sent by the parent PCE according to the compression identifier and the PST;
  • the identification information of the segment is compressed; the identification information of the compressed path segment is returned to the parent PCE.
  • the compressing the identifier information of the path segment according to the creation message includes: determining path information of the path segment carried in the creation message; creating a tunnel tunnel according to the path information, and creating the tunnel The tunnel allocates a Binding SID.
  • the creating message is used to request to create at least one of the following tunnels: an RSVP-TE tunnel that establishes a path based on a resource engineering extension resource reservation protocol; and an SR-TE tunnel that establishes a path based on the segment routing technology.
  • the creating a tunnel according to the path information includes: instantiating the tunnel according to the path information, and forwarding the creation message to a path calculation client PCC as a starting node of the tunnel to be created, where The creation message is used to instruct the PCC to initiate a process of creating the tunnel according to the path information.
  • the method includes the following: when the creating message is used to request to create the RSVP-TE tunnel, the creating message is used to instruct the PCC to initiate an RSVP-TE signaling establishment path; When the request is made to create the SR-TE tunnel, the creation message is used to instruct the PCC to calculate forwarding information of the path according to the segment routing information.
  • the allocating the Binding SID for the created tunnel includes: after the segment identifier SID is uniformly allocated by the controller globally, after the tunnel is instantiated according to the path information, the Binding is allocated for the tunnel
  • the SID is reported to the parent PCE and the PCC; and/or, in the case that the SID is allocated by the forwarding device and the assigned SID is reported to the controller, the PCC is allocated for the tunnel after the tunnel is created.
  • the Binding SID is reported to the parent PCE.
  • the method further includes: receiving identification information of the compressed path from the parent PCE; when the path is calculated The request is returned by the predetermined path calculation client PCC, and the compressed identification information of the path is returned to the predetermined PCC; when the path calculation request is not initiated by the predetermined path calculation client PCC, the request is compressed.
  • the identification information of the subsequent path is sent to the PCC of the tunnel as a starting node.
  • a determining device for identifying information of a path of a domain domain comprising: a first receiving module configured to receive a path calculation request from the first sub-path computing unit PCE, wherein The path calculation request is used to request to obtain a path from the source node to the destination node, where the source node and the destination node are located in different domains, and the path includes one or more path segments, where the path calculation request is Carrying a compressed identifier for identifying the path segment and the path establishment type PST; the indication module is configured to: after acquiring the identification information of the path of the source node to the destination node, according to the compressed identifier and the The PST indicates that the sub-PCE corresponding to each path segment compresses the identification information of the corresponding path segment, and the second receiving module is configured to receive the identification information of the compressed path segment returned by the sub-PCE corresponding to each path segment, and according to The identification information of the path forms the compressed information of each compressed path segment into
  • the indication module includes: a sending unit, configured to send, according to the compressed identifier, a creation message to a sub-PCE corresponding to each path segment, where the creation message is used to request a sub-PCE corresponding to each path segment to create a tunnel
  • the tunnel is configured to allocate a Binding SID to the created tunnel, where the creation message carries path information of the path segment.
  • a device for determining identification information of a path of a domain domain including: a sending module, configured to send a path calculation request to a parent path calculation unit PCE, where the path calculation The request is used to request to obtain a path from the source node to the destination node, where the source node and the destination node are located in different domains, the path includes one or more path fragments, and the path calculation request carries a identifier pair
  • the path identifier is configured to receive the creation message from the parent PCE, where the creation message is the
  • the compression module is configured to compress the identification information of the path segment according to the creation message; the first returning module is configured to return the identification information of the compressed path segment to the parent PCE.
  • the compression module includes: a determining unit configured to determine path information of the path segment carried in the creation message; a creating unit configured to create a tunnel tunnel according to the path information, and create a tunnel Assign a Binding SID.
  • the device further includes: a fourth receiving module, configured to receive the identifier of the compressed path from the parent PCE after returning the identifier information of the compressed path segment to the parent PCE
  • the second returning module is configured to: when the path calculation request is initiated by the predetermined path calculation client PCC, return the compressed identification information of the path to the predetermined PCC; In the case that the path calculation request is not initiated by the predetermined path calculation client PCC, the compressed identification information of the path is sent to the PCC of the tunnel as the start node.
  • a storage medium comprising a stored program, wherein the program is executed while performing the method of any of the above.
  • a processor for running a program wherein the program is executed to perform the method of any of the above.
  • the length of the identification information of the path is effectively reduced, thereby solving the problem in the related art.
  • the problem that the path identification information is too long.
  • FIG. 1 is a flowchart of a method for determining identification information of a first cross-domain path according to an embodiment of the present application
  • FIG. 2 is a flowchart of a method for determining identification information of a second cross-domain path according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of an RP object according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a Path Setup Type TLV according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a TE-PATH-BINDING TLV according to an embodiment of the present application.
  • FIG. 6 is a structural diagram of a layered PCE network according to an embodiment of the present application.
  • FIG. 7 is a structural block diagram of an apparatus for determining identification information of a first cross-domain path according to an embodiment of the present application
  • FIG. 8 is a structural block diagram of an apparatus for determining identification information of a second cross-domain path according to an embodiment of the present application.
  • FIG. 1 is a flowchart of a method for determining identification information of a first cross-domain path according to an embodiment of the present application. As shown in FIG. 1, the process includes the following steps:
  • Step S102 Receive a path calculation request from the first sub-path computing unit PCE, where the path calculation request is used to request to obtain a path from the source node to the destination node, where the source node and the destination node are located in different domains, and the path includes One or more path segments, the path calculation request carries a compression identifier for identifying a path segment to be compressed, and a path establishment type PST;
  • Step S104 After acquiring the identifier information of the path from the source node to the destination node, the sub-PCE corresponding to each path segment is used to compress the identification information of the corresponding path segment according to the compressed identifier and the PST.
  • step S106 the identification information of the compressed path segment returned by the sub-PCE corresponding to each path segment is received, and the identification information of each compressed path segment is formed into the identification information of the compressed path according to the identification information of the path.
  • the above operation may be performed by the parent PCE.
  • the processing on the parent PCE side is described.
  • the identification information of the path from the source node to the destination node is acquired, the identification information of the path is compressed, thereby effectively reducing the length of the identification information of the path, thereby solving the problem in the related art.
  • the problem that the path identification information is too long.
  • the sub-PCE corresponding to each path segment is used to compress the identification information of the corresponding path segment according to the compressed identifier, and the sending information is sent to the sub-PCE corresponding to each path segment according to the compressed identifier.
  • the creation message is used to request the sub-PCE corresponding to each path segment to create a tunnel tunnel, and the binding segment identifier Binding SID is assigned to the created tunnel, where the creation message carries the path information of the path segment.
  • the foregoing creation message is used to request the sub-PCE corresponding to each path segment to create a tunnel tunnel, including one of the following: the creation message is used to request the sub-PCE corresponding to each path segment to create a resource engineering extension-based resource.
  • the RSVP-TE tunnel is set up by the reservation protocol.
  • the creation message is used to request the sub-PCE corresponding to each path segment to create an SR-TE tunnel based on the segmentation routing technology.
  • the creation message is used to request the sub-path corresponding to each path segment.
  • the PCE creates an RSVP-TE tunnel or an SR-TE tunnel.
  • the identifier information of the compressed path segment returned by the sub-PCE corresponding to each path segment is received, and the identifier information of the compressed path segment is formed into the compressed identifier information of the path. : receiving the Binding SID assigned to the created tunnel returned by the sub-PCE corresponding to each path segment; and forming the received Binding SID into the encrypted path identification information.
  • the path information includes the following: a path name of the path, segment information of the path segment, start node information of the tunnel to be created, and destination node information, and the PST.
  • the method further includes: marking the compressed path
  • the information is returned to the first child PCE. That is, as the response of the path calculation request sent by the first sub-PCE, the identification information of the compressed path is returned to the first sub-PCE, and the first sub-PCE can continue after obtaining the identification information of the compressed path.
  • the subsequent operations are performed. For example, the obtained information of the compressed path is sent to the corresponding PCC.
  • the PCC then encapsulates the packet according to the path identification information and forwards the packet.
  • FIG. 2 is a flowchart of a method for determining identification information of a second cross-domain path according to an embodiment of the present application. As shown in FIG. 2, the process includes the following steps:
  • Step S202 Send a path calculation request to the parent path calculation unit PCE, where the path calculation request is used to request to obtain a path from the source node to the destination node, where the source node and the destination node are located in different domains, and the path includes one or more paths.
  • a path segment the path calculation request carrying a compression identifier for identifying the path segment and a path establishment type PST;
  • Step S204 receiving a creation message from the parent PCE, where the creation message is sent by the parent PCE according to the compressed identifier and the PST;
  • Step S206 compressing the identification information of the path segment according to the foregoing creation message
  • Step S208 returning the identification information of the compressed path segment to the parent PCE.
  • the sub-PCE (for example, the first sub-PCE in the first embodiment) may be used to perform the above operation.
  • the processing on the sub-PCE side is described.
  • the identification information of the path from the source node to the destination node is acquired, the identification information of the path is compressed, thereby effectively reducing the length of the identification information of the path, thereby solving the problem in the related art.
  • the problem that the path identification information is too long.
  • the compressing the identifier information of the path segment according to the foregoing creation message includes: determining path information of the path segment carried in the created message; creating a tunnel tunnel according to the path information, and assigning the created tunnel Binding SID.
  • the foregoing creation message is used to request to create at least one of the following tunnels: an RSVP-TE tunnel based on a resource reservation protocol of a traffic engineering extension; and an SR-TE based on a segmentation routing technology Tunnel.
  • an RSVP-TE tunnel based on a resource reservation protocol of a traffic engineering extension
  • an SR-TE based on a segmentation routing technology Tunnel.
  • the RSVP-TE tunnel and the SR-TE tunnel are only two preferred embodiments, and other types of tunnels may be created according to actual conditions and technical developments, which are not limited herein.
  • the creating a tunnel according to the path information includes: instantiating a tunnel according to the path information, and forwarding the creation message to a path calculation client PCC as a starting node of the tunnel to be created, where The create message is used to instruct the PCC to initiate the process of creating a tunnel according to the path information.
  • the tunnel is created by the PCC.
  • the tunnel type to be created is different, the specific operation indicated by the PCC is different.
  • the creation message is used to request to create an RSVP-TE tunnel, the foregoing message is created. Instructing the PCC to initiate the RSVP-TE signaling establishment path.
  • the creation message is used to instruct the PCC to calculate the forwarding information of the path according to the segmentation routing information.
  • the method further includes: receiving identification information of the compressed path from the parent PCE; when the path calculation request is When the predetermined path calculation client PCC initiates, the identification information of the compressed path is returned to the predetermined PCC; when the path calculation request is not initiated by the predetermined path calculation client PCC, the identifier information of the compressed path is sent to the tunnel.
  • the PCC as the starting node.
  • the SR-TE tunnel initiated by the PCC side or the SR-TE tunnel actively created by the PCE can be explicitly configured to compress the possible path segments, and the capability flag (corresponding to The above compression flag will be included in the path calculation request initiated by the PCC to the PCE (and the child PCE to the parent PCE).
  • the parent PCE will trigger the sub-PCE of each domain to additionally create an RSVP-TE tunnel (or SR-TE tunnel) according to the corresponding path segment, and each sub-PCE actively creates an additional RSVP-TE tunnel (or SR-).
  • TE tunnel Assigns a Binding SID or acquires a Binding SID from the head node PCC of the RSVP-TE tunnel (or SR-TE tunnel).
  • Each sub-PCE synchronizes the Binding SID to the parent PCE, and the parent PCE applies the Binding SID to the sub-PCE that initiates the path calculation request to the segmented route SID list corresponding to the complete TE path of the domain, and the latter sends the sub-PCE to the sub-PCE. Its PCC.
  • the PCC uses the SID list to encapsulate the packet for forwarding.
  • the explicit configuration can compress the possible path segments.
  • the specific compression capability can be:
  • Option 2 Create an RSVP-TE tunnel only for the path segment.
  • Option 3 Create an SR-TE tunnel only for the path segment.
  • Option 4 Create an RSVP-TE tunnel or an SR-TE tunnel for the path segment.
  • Option 1 the method described in the embodiment of the present application is the same as the method described in RFC6805.
  • the description is mainly for Option 2 or Option 3 or Option 4.
  • Option 2, Option 3, and Option 4 are collectively referred to as "to be compressed.” It should be noted that in addition to the above four types of options, other options can be extended in the future.
  • the PCC will initiate a path calculation request to the sub-PCE (recorded as sub-PCE1) of the domain in which it is located, or for the sub-PCE1
  • the actively established SR-TE tunnel the sub-PCE1 will initiate a path calculation request to the parent PCE.
  • the path calculation request message will indicate that the PST is "establishing a path using the segmentation routing technology", and also includes the above path fragment compression capability flag.
  • the request message also contains the path name path-name-SD.
  • the parent PCE will first calculate which domain sequence the TE path across the domain may traverse according to the domain-level topology information it maintains, and then initiate a path within the domain to each sub-PCE of each domain for each domain sequence. Calculate the request. Note that the path calculation request message sent by the parent PCE to each sub-PCE is only used to obtain the potential path for optimization. Therefore, the path fragment compression flag included in the message must be uncompressed, and the PST can still be set to "use segmentation.” Routing technology establishes a path.” The parent PCE will eventually calculate an optimal cross-domain TE path from a number of domain sequences.
  • the TE path may include an IP address list or a SID list corresponding to a specific path segment in each domain, or a path-key corresponding to a specific path segment in each domain.
  • each sub-PCE may attempt to reply to the parent PCE with a SID list.
  • replying to the IP address list or the IP address+SID mixed list is also permitted by the protocol. This description also applies when the parent PCE replies to the full TE path to the child PCE1.
  • Each sub-PCE can collect the intra-domain information of the domain in which the domain is responsible for the BGP-LS and the link information between the domains of the domain.
  • the sub-PCEs need to report the link information between the domains to the BGP-LS.
  • Parent PCE Other than the BGP-LS, there are other channels, which are not limited in the embodiment of the present application.
  • the parent PCE does not immediately reply the above-mentioned optimal full TE path to the sub-PCE1, but checks the path segment compression included in the corresponding path calculation request message sent to the sub-PCE1.
  • the flag prompts "to be compressed”, so the parent PCE sends an "actively create tunnel" message to the sub-PCE corresponding to each domain for each path segment corresponding to each domain in each optimal full path, and at least provides: a path in the message. Name, path fragment information, the starting node of the tunnel to be created (ie, the head node of the path fragment) and the destination node (ie, the tail node of the path fragment) information, and the PST.
  • the path name can be added to the trail after the full path name (ie path-name-SD), such as the path-name-SD-path fragment first node-path fragment tail node, so as to be globally uniquely distinguished;
  • the path fragment information is the corresponding
  • the child PCE replies to the parent PCE, but now the parent PCE is in turn provided as the ERO to the child PCE to create the tunnel;
  • the starting node and the destination node of the tunnel to be created are the first node and the tail node of the corresponding path segment;
  • PST According to the above path fragment compression flag, if the path fragment compression flag is Option2, the PST should be set to "establish path using RSVP-TE signaling".
  • the PST should be set to "use point.” Segment routing technology establishes a path. If the path fragment compression flag is Option4, the PST should be set to "establish path using RSVP-TE signaling or segmentation routing technology.”
  • the sub-PCE corresponding to each domain receives the "actively create tunnel" message of the parent PCE, and then instantiates the corresponding tunnel locally, and forwards the message "actively creating a tunnel" to the starting node PCC of the tunnel to be created.
  • the PCC selects to initiate RSVP-TE signaling to establish a path or directly calculate a path according to the segment routing information according to its actual capabilities. Forward the message.
  • the sub-PCE corresponding to each domain can be configured to allocate the corresponding Binding SID to the corresponding tunnel and send it to the parent PCE and send it to the PCC. . If the SID is configured on the forwarding device and the device is deployed to the controller, the PCC of the corresponding tunnel is assigned to the tunnel and the sub-PCE is reported to the tunnel. Parent PCE.
  • the Binding SID assigned to the tunnel has local attributes, and generally does not need to be globally unique. If the requirement is globally unique, the scenario in which the controller globally allocates the SIDs should be deployed, and the SID resource pools controlled by the sub-PCEs should not overlap each other. This may be a management mode or other dynamic learning mode.
  • the SID list corresponding to the original complete TE path can be reduced and optimized.
  • the parent PCE does not care about the specific ERO content of the path fragment information.
  • the fragment only needs to be represented by its Binding SID in the SID list corresponding to the complete TE path.
  • the SID list of the optimized complete TE path is generally reduced: ⁇ Binding SID1, Peer-Adj SID1, Binding SID2, Peer-Adj SID2, ..., Binding SIDn ⁇ .
  • each Binding SID and Peer-Adj SID in the SID list can also be inserted into the node SID corresponding to the corresponding starting node, but this is not required.
  • Binding SID1 may not exist in special cases. For example, the starting node of the complete TE path happens to be the exit boundary node of the first domain in the domain sequence.
  • the parent PCE replies the above-reduced optimized SID list to the sub-PCE1 as a response to the inter-domain TE path calculation request message received from the sub-PCE1.
  • the sub-PCE1 continues to reply the SID list to the PCC that previously received the corresponding path calculation request from the PCC, or the sub-PCE1 sends the SID list to the tunnel head node PCC when the cross-domain tunnel is actively created.
  • the PCC will be able to use the SID list as forwarding information for the SR-TE tunnel across the domain.
  • the Binding SID actually refers to the forwarding information of the tunnel corresponding to the path segment of the domain where the PCC is located. Therefore, when the SR-TE tunnel finally generates forwarding information, Replace the first SID (Binding SID) with the forwarding information of the corresponding tunnel.
  • the first SID in the SID list is a Peer-Adj SID
  • the first SID (Peer-Adj SID) is replaced with the forwarding information of the link between the corresponding domains.
  • the method of the embodiment of the present invention can significantly shorten the segmentation route SID list of the TE path across the domain, reduce the packet stack depth for packet encapsulation, improve packet load efficiency, and avoid MTU. Fragmentation.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • FIG. 3 is a schematic diagram of an RP object according to an embodiment of the present application. Based on the RP object defined in RFC5440, RFC5520, RFC5541, and RFC5557, a CF (Compress Flag) that is intended to occupy three bits is added to the Flags flag field. The flag is used to identify whether the path needs to be compressed.
  • CF Compress Flag
  • FIG. 4 is a schematic diagram of a Path Setup Type TLV according to an embodiment of the present application.
  • the Path Setup Type TLV can be carried in the RP object (refer to RFC5440) and the SRP object (refer to draft-ietf-pce-stateful-pce-18).
  • FIG. 5 is a schematic diagram of a TE-PATH-BINDING TLV according to a specific embodiment of the present application, which is based on the TE-PATH-BINDING TLV defined by the draft-sivabalan-pce-binding-label-sid-02. .
  • the draft-sivabalan-pce-binding-label-sid-02 defines the TE-PATH-BINDING TLV, which is included in the LSP object in the PCRpt message, and is used to report the Binding SID of the corresponding TE path from the PCC to the PCE.
  • the method is used to report the Binding SID of the tunnel created by the path segment in the corresponding domain from the PCC to the child PCE and the child PCE to the parent PCE.
  • the method is applicable to the deployment scenario where the forwarding device directly configures the SID and reports the controller.
  • this embodiment will also extend the use of LSP objects in draft-ietf-pce-stateful-pce-18 and draft-ietf-pce-pce-initiated-lsp-09, respectively allowing for PCUpd messages and
  • the LSP object included in the PCInitiate message includes the TE-PATH-BINDING TLV, which is used to deliver the Binding SID of the tunnel created by the path fragment in the corresponding domain from the sub-PCE to the PCC. .
  • FIG. 6 is a schematic diagram of a hierarchical PCE network architecture according to an embodiment of the present application, including three domains, namely, AS1, AS2, and AS3, and corresponding sub-PCEs are PCE1, PCE2, and PCE3, respectively, and the parent PCE is PCE4.
  • AS1, AS2, and AS3 the deployment scenario is that the centralized controller uniformly allocates the SID and sends the SID to the forwarding device; the PCE1 wants to actively create an SR-TE tunnel from the source node S to the destination node D, and the PCE1 knows other ASs (AS2). AS3) Except that the border node has been upgraded to support the segmentation routing function, the internal nodes only support RSVP-TE but do not support the segmentation routing function. Now let's look at the specific steps of PCE1 to actively create an SR-TE tunnel from source node S to destination node D, as follows:
  • step 110 the PCE1 actively creates an SR-TE tunnel, where the source node is S and the destination node is D.
  • the PCE1 sends the PCReq message to the parent PCE (PCE4) to request the calculation of the TE path across the domain according to the TED (TE database) information of the MPLS (TE database).
  • the PCE1 sends a PCReq message to the domain.
  • RFC 5440 and draft-ietf-pce-stateful-pce-18 are combined with the solution in the embodiment of the present application. Only the main information related to the processing flow in the embodiment of the present application is given below:
  • ⁇ RP object> PST is set to 1, indicating that the path is established by using the segmentation routing technology; the CF flag is set to 1, so that an RSVP-TE tunnel is additionally created for the path segment in each AS for compression;
  • ⁇ END-POINTS object> the source node is S and the destination node is D;
  • path-name is set to path-name-SD-100;
  • Step 120 After receiving the request, the PCE4 determines, according to the method described in RFC6805, that the domain where the destination node is located is AS3, and then determines a possible domain sequence. In this embodiment, only one domain sequence exists, that is, S-(AS1)-A1. -A2-(AS2)-A3-A4-(AS3)-D.
  • PCE4 sends a PCReq message to each sub-PCE corresponding to each domain in the sequence, requesting to calculate a path segment in each domain.
  • PCE4 sends a PCReq message to PCE1 to request a path segment from source node S to destination node A1.
  • the main information in the message is as follows:
  • ⁇ RP object> PST is set to 1, indicating that the path is established using the segmentation routing technology; the CF flag must be set to 0, indicating that the path is not compressed;
  • ⁇ END-POINTS object> the source node is S and the destination node is A1;
  • PCE4 also sends a PCReq message to PCE2 to request a path segment from source node A2 to destination node A3, and a PCReq message to PCE3 to request a path segment from source node A4 to destination node D. No longer.
  • Step 130 After receiving the path calculation request sent by the PCE4, each sub-PCE calculates a corresponding path segment and sends a PCRep message to the PCE4.
  • PCE1 will calculate the path segment S-P1-P2-A1
  • PCE2 will calculate the path segment A2-P3-P4-A3
  • PCE3 will calculate the path segment A4-P5-P6-D.
  • the path fragment information will be given in the ERO object included in the PCERep message sent by each sub-PCE to PCE4, which may be a IP address list, a SID list, a mixed list of IP addresses and SIDs, or even a path for security reasons.
  • -key may be an IP address list or a path-key.
  • Step 140 For the domain sequence S-(AS1)-A1-A2-(AS2)-A3-A4-(AS3)-D, after the PCE4 receives the path fragments of all the domains from all the sub-PCEs, the complete end is obtained.
  • the TE path to the end In this embodiment, since there are no other domain sequences, the complete TE path will be the optimal path.
  • the PCE4 does not rush to reply the PCE1 to the PCE1, but checks that the CF flag is 1 in the corresponding path calculation request received from the PCE1, and the RSVP-TE tunnel is actively created for each path segment.
  • a PCInitiate message is sent to each child PCE.
  • PCE4 internally creates a corresponding RSVP-TE tunnel for the path segment S-P1-P2-A1 corresponding to AS1, and the main path included therein may be named path-name-SD-100-SA1 (Note: This naming method)
  • path-name-SD-100-SA1 Note: This naming method
  • the key information S and A1 of the sub-path are guaranteed to be globally unique.
  • the PCE4 sends the PCInitiate message to PCE1.
  • the main information is as follows:
  • ⁇ SRP object> PST is set to 0, indicating that the path is established using RSVP-TE.
  • path-name is set to 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 IP address list or path-key, that is, the path fragment information previously received from PCE1 is filled in as it is.
  • PCE4 also internally creates a corresponding RSVP-TE tunnel for the path segment A2-P3-P4-A3 corresponding to AS2, and the main path included therein may be named path-name-SD-100-A2A3, and correspondingly sent to PCE2.
  • PCE4 also internally creates a corresponding RSVP-TE tunnel for the path segment A4-P5-P6-D corresponding to AS3, and the main path included therein may be named path-name-SD-100-A4D, and corresponding Send a PCInitiate message to PCE3. No longer.
  • Step 150 After receiving the PCInitiate message of the PCE4, each sub-PCE will actively create a corresponding RSVP-TE tunnel internally and continue to send a PCInitiate message to the head node PCC of the tunnel.
  • the ERO object contains an explicit strict hop-by-hop explicit path, which can be an IP address list, but not a path-key.
  • Each tunnel head node will establish a path through the RSVP-TE signaling in the network to negotiate the label.
  • each sub-PCE will also actively allocate a Binding SID to the RSVP-TE tunnel.
  • Each sub-PCE can send the Binding SID to the tunnel head node PCC along with the PCInitiate message or the subsequent PCUpd message, or report the PCRpt message to the PCE4.
  • each tunnel head node will establish a label entry with the Binding SID as the key value to guide the packet forwarding to the tunnel.
  • the label operation is to exchange the Binding SID into the RSVP-TE tunnel. Label out.
  • each sub-PCE also allocates a Peer-Adj SID to the inter-domain link of the domain to other domains, and reports it to PCE4 through BGP-LS.
  • the original complete TE path is represented by the compressed SID list and is returned to the PCE1 through the PCRep message.
  • the compressed SID list in this embodiment may be: ⁇ 1000, Peer-Adj-SID-A1A2, 2000, Peer-Adj-SID-A3A4, 3000 ⁇ .
  • Step 170 After receiving the PCRep message of 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, including the compressed SID list.
  • the corresponding SR-TE tunnel is created on the S-node.
  • the forwarding entry is generated for the SR-TE tunnel
  • the first SID in the SID list that is, the 1000 search label entry
  • the corresponding RSVP-TE tunnel Forward the information, the other SIDs are unchanged.
  • Step 180 On the S node, the packet sent to the SR-TE tunnel will be pressed into the corresponding label stack: ⁇ RSVP-TE tunnel-SA1 label, Peer-Adj-SID-A1A2, 2000, Peer-Adj -SID-A3A4, 3000 ⁇ , that is, the top label is the outgoing label corresponding to the RSVP-TE tunnel created by the path segment in the foregoing AS1, and the lower label is the Peer-Adj SID corresponding to the link A1-A2 between the domains, and the lower label is The Binding SID corresponding to the RSVP-TE tunnel created by the path segment in AS2, and the lower label is the Peer-Adj SID corresponding to the link A3-A4 between the domains. The lower label is the RSVP-TE tunnel created by the path fragment in AS3. Binding SID. The message will be forwarded along the desired TE path across the domain.
  • the specific embodiment is similar to the specific embodiment.
  • the difference is that the SID in the embodiment is a deployment scenario that is allocated and sent by the forwarding device (for example, through BGP-LS) to the controller.
  • the process of the PCE1 actively establishing an SR-TE tunnel across the domain from the source node S to the destination node D is basically similar to the first embodiment except that the path segment of each domain involved is additionally created by the RSVP-TE tunnel.
  • the Binding SID is allocated by the tunnel head node itself and reported to the corresponding sub-PCE through the PCRpt message.
  • the sub-PCE continues to report the Binding SID to the PCE4 through the PCRpt message.
  • the other processes are the same as those in the embodiment.
  • the specific embodiment is basically similar to the specific embodiment 1. The difference is that in this embodiment, an S-node establishes a cross-domain SR-TE tunnel from the source node S to the destination node D, and the S-node PCC sends a PCReq to the PCE1.
  • the message is the same as the PCReq message sent by the sub-PCE1 to the PCE4 in the first embodiment.
  • the other remaining procedures are the same as in the first embodiment, and finally the PCE1 sends a PCRep message reply path calculation result to the S-node PCC, which includes the compressed SID list.
  • the specific embodiment is basically the same as the specific embodiment 1. The difference is that all domains have been upgraded to support the segment routing function, and RSVP-TE is no longer supported in the network. Now let's look at the specific steps of PCE1 to actively create an SR-TE tunnel from source node S to destination node D, as follows:
  • step 410 the PCE1 actively creates an SR-TE tunnel, where the source node is S and the destination node is D.
  • the PCE1 sends the PCReq message to the parent PCE (PCE4) to request the calculation of the TE path across the domain according to the TED (TE database) information of the MPLS (TE database).
  • the PCE1 sends a PCReq message to the domain.
  • RFC 5440 and draft-ietf-pce-stateful-pce-18 are combined with the solution in the embodiment of the present application. Only the main information related to the processing flow in the embodiment of the present application is given below:
  • ⁇ RP object> PST is set to 1, indicating that the path is established using the segmentation routing technology; the CF flag is set to 2, so that an SR-TE tunnel is additionally created for the path segment in each AS for compression;
  • ⁇ END-POINTS object> the source node is S and the destination node is D;
  • path-name is set to path-name-SD-100;
  • Step 420 After receiving the request, the PCE4 determines, according to the method described in RFC6805, that the domain where the destination node is located is AS3, and then determines a possible domain sequence. In this embodiment, only one domain sequence exists, that is, S-(AS1)-A1. -A2-(AS2)-A3-A4-(AS3)-D. For the domain sequence, PCE4 sends a PCReq message to each sub-PCE corresponding to each domain in the sequence, requesting to calculate a path segment in each domain. For example, PCE4 sends a PCReq message to PCE1 to request a path segment from source node S to destination node A1. The main information in the message is as follows:
  • ⁇ RP object> PST is set to 1, indicating that the path is established using the segmentation routing technology; the CF flag must be set to 0, indicating that the path is not compressed;
  • ⁇ END-POINTS object> the source node is S and the destination node is A1;
  • the PCE 4 also sends a PCReq message to the PCE 2 to request the calculation of the path segment of the source node A2 to the destination node A3, and sends a PCReq message to the PCE 3 to request the calculation of the path segment of the source node A4 to the destination node D. No longer.
  • Step 430 After receiving the path calculation request sent by the PCE4, each sub-PCE calculates a corresponding path segment and sends a PCRep message to the PCE4.
  • PCE1 will calculate the path segment S-P1-P2-A1
  • PCE2 will calculate the path segment A2-P3-P4-A3
  • PCE3 will calculate the path segment A4-P5-P6-D.
  • the path fragment information will be given in the ERO object included in the PCERep message sent by each sub-PCE to PCE4, which may be a IP address list, a SID list, a mixed list of IP addresses and SIDs, or even a path for security reasons.
  • -key may be SID list or path-key.
  • Step 440 for the domain sequence S-(AS1)-A1-A2-(AS2)-A3-A4-(AS3)-D, after the PCE4 receives the path fragments of all the domains from all the sub-PCEs, the complete end is obtained.
  • the TE path to the end In this embodiment, since there are no other domain sequences, the complete TE path will be the optimal path.
  • the PCE4 does not rush to reply the PCE1 to the PCE1, but checks that the CF flag is 2 in the corresponding path calculation request received from the PCE1, and the SR-TE tunnel is actively created for each path segment.
  • a PCInitiate message is sent to each child PCE.
  • PCE4 internally creates a corresponding SR-TE tunnel for the path segment S-P1-P2-A1 corresponding to AS1, and the main path it contains may be named path-name-SD-100-SA1 (Note: This naming method)
  • path-name-SD-100-SA1 Note: This naming method
  • the key information S and A1 of the sub-path are guaranteed to be globally unique.
  • the PCE4 sends the PCInitiate message to PCE1.
  • the main information is as follows:
  • ⁇ SRP object> PST is set to 1, indicating that the path is established using the segmentation routing technology
  • path-name is set to 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 SID list or path-key, that is, the path fragment information previously received from PCE1 is filled in as it is.
  • PCE4 also internally creates a corresponding SR-TE tunnel for the path segment A2-P3-P4-A3 corresponding to AS2, and the main path included therein may be named path-name-SD-100-A2A3, and correspondingly sent to PCE2.
  • PCE4 also internally creates a corresponding SR-TE tunnel for the path segment A4-P5-P6-D corresponding to AS3, and the main path included therein may be named path-name-SD-100-A4D, and corresponding Send a PCInitiate message to PCE3. No longer.
  • Step 450 After receiving the PCInitiate message of the PCE4, each sub-PCE will actively create a corresponding SR-TE tunnel internally and continue to send a PCInitiate message to the head node PCC of the tunnel. Note that in the PCInitiate message sent by the sub-PCE to the tunnel node PCC, the ERO object contains an explicit SID list, which cannot be path-key. Each tunnel header node will generate a corresponding SR-TE tunnel, and the forwarding information is generated using the corresponding SID list.
  • each tunnel head node After receiving the Binding SID, each tunnel head node will establish a label entry with the Binding SID as the key value to guide the packet forwarding to the tunnel.
  • the label operation is to exchange the incoming label Binding SID into the SR-TE tunnel. Out of the label stack.
  • each sub-PCE also allocates a Peer-Adj SID to the inter-domain link of the domain to other domains, and reports it to PCE4 through BGP-LS.
  • step 460 after the PCE4 receives the Binding SID of all the sub-PCEs, the original complete TE path is represented by the compressed SID list and is returned to the PCE1 through the PCRep message.
  • the compressed SID list in this embodiment may be: ⁇ 1000, Peer-Adj-SID-A1A2, 2000, Peer-Adj-SID-A3A4, 3000 ⁇ .
  • Step 470 After receiving the PCRep message of 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, including the compressed SID list.
  • the corresponding SR-TE tunnel is created on the S-node.
  • the forwarding entry is generated for the SR-TE tunnel
  • the first SID in the SID list that is, the 1000 search label entry
  • the corresponding SR-TE tunnel Forward the information (usually a label stack), the other SIDs are unchanged.
  • step 480 the packet sent to the SR-TE tunnel on the S node is pressed into the corresponding label stack: ⁇ SR-TE tunnel-SA1 SID list, Peer-Adj-SID-A1A2, 2000, Peer- Adj-SID-A3A4, 3000 ⁇ , that is, the top label is the outgoing label stack corresponding to the SR-TE tunnel created by the path segment in the foregoing AS1, and then the lower label is the Peer-Adj SID corresponding to the link A1-A2 between the domains, and then The lower label is the Binding SID corresponding to the SR-TE tunnel created by the path fragment in AS2, and the lower label is the Peer-Adj SID corresponding to the link A3-A4 between the domains, and the lower label is the SR-created by the path fragment in AS3. Binding SID corresponding to the TE tunnel.
  • the message will be forwarded along the desired TE path across the domain.
  • the specific embodiment is similar to the fourth embodiment.
  • the SID in the embodiment is a deployment scenario that is allocated and sent by the forwarding device (for example, through BGP-LS) to the controller.
  • the process of the PCE1 actively establishing an SR-TE tunnel across the domain from the source node S to the destination node D is basically similar to that in the fourth embodiment, except that the path segment of each domain involved is additionally created by the SR-TE tunnel.
  • the Binding SID is allocated by the tunnel head node itself and reported to the corresponding sub-PCE through the PCRpt message.
  • the sub-PCE continues to report the Binding SID to the PCE4 through the PCRpt message.
  • the other processes are the same as those in the fourth embodiment.
  • the specific embodiment is basically similar to the fourth embodiment.
  • an S-node establishes an SR-TE tunnel across the domain from the source node S to the destination node D, and the S node PCC sends a PCReq to the PCE1.
  • the message is the same as the PCReq message sent by the sub-PCE1 to the PCE4 in the first embodiment, and the other remaining processes are the same as in the first embodiment, and finally the PCE1 sends a PCRep message reply path calculation result to the S-node PCC, which includes The compressed SID list.
  • the specific embodiment is basically the same as the specific embodiment 1. The difference is that all AS1 and AS2 have been upgraded to support the segment routing function and no longer support RSVP-TE. However, only the border node upgrade of AS3 supports the segment routing function and the internal nodes are still only Support RSVP-TE. Now let's look at the specific steps of PCE1 to actively create an SR-TE tunnel from source node S to destination node D, as follows:
  • the PCE1 actively creates an SR-TE tunnel, where the source node is S and the destination node is D.
  • the PCE1 sends the PCReq message to the parent PCE (PCE4) to request the calculation of the TE path across the domain according to the TED (TE database) information of the MPLS (TE database).
  • the PCE1 sends a PCReq message to the domain.
  • RFC 5440 and draft-ietf-pce-stateful-pce-18 are combined with the solution in the embodiment of the present application. Only the main information related to the processing flow of the embodiment of the present application is given below:
  • ⁇ RP object> PST is set to 1, indicating that the path is established using the segmentation routing technology; the CF flag is set to 3, so that the RSVP-TE tunnel or SR-TE tunnel is additionally created for each path segment according to the actual capability. compression;
  • ⁇ END-POINTS object> the source node is S and the destination node is D;
  • path-name is set to path-name-SD-100;
  • Step 720 After receiving the request, the PCE4 determines, according to the method described in RFC6805, that the domain where the destination node is located is AS3, and then determines a possible domain sequence. In this embodiment, only one domain sequence exists, that is, S-(AS1)-A1. -A2-(AS2)-A3-A4-(AS3)-D. For the domain sequence, PCE4 sends a PCReq message to each sub-PCE corresponding to each domain in the sequence, requesting to calculate a path segment in each domain. For example, PCE4 sends a PCReq message to PCE1 to request a path segment from source node S to destination node A1. The main information in the message is as follows:
  • ⁇ RP object> PST is set to 1, indicating that the path is established using the segmentation routing technology; the CF flag must be set to 0, indicating that the path is not compressed;
  • ⁇ END-POINTS object> the source node is S and the destination node is A1;
  • the PCE 4 also sends a PCReq message to the PCE 2 to request the calculation of the path segment of the source node A2 to the destination node A3, and sends a PCReq message to the PCE 3 to request the calculation of the path segment of the source node A4 to the destination node D. No longer.
  • Step 730 After receiving the path calculation request sent by the PCE4, each sub-PCE calculates a corresponding path segment and sends a PCRep message to the PCE4.
  • PCE1 will calculate the path segment S-P1-P2-A1
  • PCE2 will calculate the path segment A2-P3-P4-A3
  • PCE3 will calculate the path segment A4-P5-P6-D.
  • the path fragment information will be given in the ERO object included in the PCERep message sent by each sub-PCE to PCE4, which may be a IP address list, a SID list, a mixed list of IP addresses and SIDs, or even a path for security reasons. -key.
  • the path fragment information that PCE1 and PCE2 reply to PCE4 may be SID list or path-key; since AS3 only border node supports SR, PCE3 replies to path segment of PCE4.
  • the information can be an IP address list or a path-key.
  • Step 740 for the domain sequence S-(AS1)-A1-A2-(AS2)-A3-A4-(AS3)-D, after the PCE4 receives the path fragments of all the domains from all the sub-PCEs, the complete end is obtained.
  • the TE path to the end In this embodiment, since there are no other domain sequences, the complete TE path will be the optimal path.
  • the PCE4 does not rush to reply the PCE1 to the PCE1, but checks that the CF flag is 3 in the corresponding path calculation request received from the PCE1, and the TE tunnel is actively created for each path segment.
  • the RSVP-TE tunnel is also an SR-TE tunnel) and sends a PCInitiate message to each sub-PCE.
  • PCE4 internally creates a corresponding TE tunnel for the path segment S-P1-P2-A1 corresponding to AS1, and the main path it contains may be named path-name-SD-100-SA1 (Note: This naming method is in The parent path name path-name-SD-100 is added to the end of the sub-path key information S, A1, which can guarantee global uniqueness.
  • PCE4 sends the PCInitiate message to PCE1.
  • the main information is as follows:
  • ⁇ SRP object> PST is set to 2, indicating that the path can be established using RSVP-TE signaling or segmentation routing technology;
  • path-name is set to 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 SID list or path-key, that is, the path fragment information previously received from PCE1 is filled in as it is.
  • PCE4 also internally creates a corresponding TE tunnel for the path segment A2-P3-P4-A3 corresponding to AS2, and the main path included therein may be named path-name-SD-100-A2A3, and correspondingly sends a PCInitiate message to PCE2.
  • PCE4 also internally creates a corresponding TE tunnel for the path segment A4-P5-P6-D corresponding to AS3, which contains the main path named path-name-SD-100-A4D, and sends PCInitiate to PCE3 accordingly. Message. No longer.
  • Step 750 After receiving the PCInitiate message of the PCE4, the PCE1 and the PCE2 will actively create a corresponding SR-TE tunnel according to their own capabilities, and continue to send a PCInitiate message to the head node PCC of the tunnel.
  • PCE3 After receiving the PCInitiate message from PCE4, PCE3 will actively create the corresponding RSVP-TE tunnel according to its own capabilities and continue to send the PCInitiate message to the head node PCC of the tunnel. Note that in the PCInitiate message sent by the sub-PCE1 and the sub-PCE2 to the tunnel head node PCC, the ERO object contains an explicit SID list, which cannot be a path-key.
  • the PCE3 continues to send the PCInitiate message to the tunnel node PCC.
  • the ERO object contains an explicit IP address list, which cannot be path-key.
  • the tunnel header node in AS1 and AS2 will generate the corresponding SR-TE tunnel, and the forwarding information will be generated using the corresponding SID list.
  • the tunnel head node in AS3 will generate the corresponding RSVP-TE tunnel, and establish a path through the RSVP-TE signaling in the network to negotiate the label. .
  • each sub-PCE will actively allocate a Binding SID to the TE tunnel after the corresponding SR-TE tunnel or the RSVP-TE tunnel is created.
  • the PCE1 allocates Binding to the SR-TE tunnel created above.
  • Each sub-PCE can send the Binding SID to the tunnel head node PCC along with the PCInitiate message or the subsequent PCUpd message, or report the PCRpt message to the PCE4.
  • each tunnel head node After receiving the Binding SID, each tunnel head node will establish a label entry with the Binding SID as the key value to guide the packet forwarding to the tunnel.
  • the label operation is to exchange the incoming label Binding SID into the corresponding SR-TE tunnel.
  • the outgoing label stack is either switched to the outgoing label contained in the corresponding RSVP-TE tunnel.
  • each sub-PCE also allocates a Peer-Adj SID to the inter-domain link of the domain to other domains, and reports it to PCE4 through BGP-LS.
  • step 760 after the PCE4 receives the Binding SID of all the sub-PCEs, the original complete TE path is represented by the compressed SID list and is returned to the PCE1 through the PCRep message.
  • the compressed SID list in this embodiment may be: ⁇ 1000, Peer-Adj-SID-A1A2, 2000, Peer-Adj-SID-A3A4, 3000 ⁇ .
  • Step 770 After receiving the PCRep message of 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, including the compressed SID list.
  • the corresponding SR-TE tunnel is created on the S-node.
  • the forwarding entry is generated for the SR-TE tunnel
  • the first SID in the SID list that is, the 1000 search label entry
  • the corresponding SR-TE tunnel Forward the information (usually a label stack), the other SIDs are unchanged.
  • Step 780 On the S node, the packet sent to the SR-TE tunnel will be pressed into the corresponding label stack: ⁇ SR-TE tunnel-SA1 SID list, Peer-Adj-SID-A1A2, 2000, Peer- Adj-SID-A3A4, 3000 ⁇ , that is, the top label is the outgoing label stack corresponding to the SR-TE tunnel created by the path segment in the foregoing AS1, and then the lower label is the Peer-Adj SID corresponding to the link A1-A2 between the domains, and then The lower label is the Binding SID corresponding to the SR-TE tunnel created by the path fragment in AS2, and the lower label is the Peer-Adj SID corresponding to the link A3-A4 between the domains, and the lower label is the RSVP created by the path fragment in AS3. Binding SID corresponding to the TE tunnel. The message will be forwarded along the desired TE path across the domain.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present application.
  • a device for determining identification information of a cross-domain path is further provided, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • FIG. 7 is a structural block diagram of an apparatus for determining identification information of a first cross-domain path according to an embodiment of the present application. As shown in FIG. 7, the apparatus includes a first receiving module 72, an indication module 74, and a second receiving module 76. The device is described below:
  • the first receiving module 72 is configured to receive a path calculation request from the first sub-path computing unit PCE, where the path calculation request is used to request to obtain a path from the source node to the destination node, where the source node and the destination node are located in different domains.
  • the path includes one or more path segments, and the path calculation request carries a compressed identifier for identifying a path segment and a path establishment type PST.
  • the indication module 74 is connected to the first receiving module 72, configured as After acquiring the identification information of the path from the source node to the destination node, the sub-PCE corresponding to each path segment is compressed according to the compressed identifier and the PST, and the second receiving module 76 is connected to the foregoing.
  • the indication module 74 is configured to receive the identification information of the compressed path segment returned by the sub-PCE corresponding to each path segment, and form the identification information of the compressed path segment by the identification information of each compressed path segment according to the identification information of the path. .
  • the indication module 74 includes: a sending unit, configured to send a creation message to the sub-PCE corresponding to each path segment according to the compression identifier, where the creation message is used to request the sub-PCE corresponding to each path segment.
  • a tunnel is created, and a Binding SID is assigned to the created tunnel, where the creation message carries the path information of the path segment.
  • the foregoing creation message is used to request the sub-PCE corresponding to each path segment to create a tunnel tunnel, including one of the following: the creation message is used to request the sub-PCE corresponding to each path segment to create a resource engineering extension-based resource.
  • the RSVP-TE tunnel is set up by the reservation protocol.
  • the creation message is used to request the sub-PCE corresponding to each path segment to create an SR-TE tunnel based on the segmentation routing technology.
  • the creation message is used to request the sub-path corresponding to each path segment.
  • the PCE creates an RSVP-TE tunnel or an SR-TE tunnel.
  • the second receiving module 76 is configured to: receive a Binding SID of the created tunnel that is returned by the sub-PCE corresponding to each path segment, and combine the received Binding SIDs with the identifier of the compressed path. information.
  • the path information includes the following: a path name of the path, segment information of the path segment, start node information of the tunnel to be created, and destination node information, and the PST.
  • the apparatus further includes a returning module configured to: after the identification information of each compressed path segment is formed into the information of the compressed path according to the identification information of the path, the compressed path is The identification information is returned to the first child PCE. That is, as the response of the path calculation request sent by the first sub-PCE, the identification information of the compressed path is returned to the first sub-PCE, and the first sub-PCE can continue after obtaining the identification information of the compressed path. The subsequent operations are performed. For example, the obtained information of the compressed path is sent to the corresponding PCC. The PCC then encapsulates the packet according to the path identification information and forwards the packet.
  • FIG. 8 is a structural block diagram of an apparatus for determining identification information of a second cross-domain path according to an embodiment of the present application.
  • the apparatus includes a sending module 82, a third receiving module 84, a compression module 86, and a A return module 88, the device is described below:
  • the sending module 82 is configured to send a path calculation request to the parent path calculation unit PCE, where the path calculation request is used to request to obtain a path from the source node to the destination node, where the source node and the destination node are located in different domains, and the path includes One or more path segments, the path calculation request carries a compression identifier for identifying the path segment compression and a path establishment type PST;
  • the third receiving module 84 is connected to the sending module 82, and configured to receive the parent PCE from the foregoing a creation message, wherein the creation message is sent by the parent PCE according to the compression identifier and the PST;
  • the compression module 86 is connected to the third receiving module 84, and configured to compress the identification information of the path segment according to the creation message;
  • the returning module 88 is connected to the compression module 86 and configured to return the identification information of the compressed path segment to the parent PCE.
  • the compression module 86 includes: a determining unit configured to determine path information of the path segment carried in the created message; and a creating unit configured to create a tunnel tunnel according to the path information, and create a tunnel Assign a Binding SID.
  • the foregoing creation message is used to request to create at least one of the following tunnels: an RSVP-TE tunnel based on a resource reservation protocol of a traffic engineering extension; and an SR-TE based on a segmentation routing technology Tunnel.
  • an RSVP-TE tunnel based on a resource reservation protocol of a traffic engineering extension
  • an SR-TE based on a segmentation routing technology Tunnel.
  • the RSVP-TE tunnel and the SR-TE tunnel are only two preferred embodiments, and other types of tunnels may be created according to actual conditions and technical developments, which are not limited herein.
  • the creating unit is configured to: instantiate the tunnel according to the path information, and forward the created message to the path computing client PCC as the starting node of the tunnel to be created, where the creation message is used
  • the process of creating a tunnel is initiated by instructing the PCC to follow the path information.
  • the tunnel is created by the PCC.
  • the tunnel type to be created is different, the specific operation indicated by the PCC is different.
  • the creation message is used to request to create an RSVP-TE tunnel, the foregoing message is created. Instructing the PCC to initiate the RSVP-TE signaling establishment path.
  • the creation message is used to instruct the PCC to calculate the forwarding information of the path according to the segmentation routing information.
  • the foregoing apparatus further includes: a fourth receiving module, connected to the first returning module 88, configured to receive the information from the parent PCE after returning the identification information of the compressed path segment to the parent PCE. Identification information of the compressed path; the second returning module is connected to the fourth receiving module, configured to return the identification information of the compressed path to the path when the path calculation request is initiated by the predetermined path calculation client PCC a third PC is configured to be connected to the second return module, configured to send the identifier information of the compressed path to the tunnel as the start when the path calculation request is not initiated by the predetermined path calculation client PCC.
  • the PCC of the node is configured to send the identifier information of the compressed path to the tunnel as the start when the path calculation request is not initiated by the predetermined path calculation client PCC.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • the embodiment of the present application further provides a storage medium including a stored program, wherein the program runs to perform the method described in any of the above.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • Embodiments of the present application also provide a processor for running a program, wherein the program executes the steps of any of the above methods when executed.
  • modules or steps of the present application can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the application is not limited to any particular combination of hardware and software.
  • the identification information of the path is compressed, thereby effectively reducing the length of the identification information of the path, thereby solving the related art.
  • the existing path identifies that the information is too long.

Landscapes

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

Abstract

本申请提供了一种跨域的路径的标识信息的确定方法、装置及存储介质，其中，该方法包括：接收来自第一子路径计算单元PCE的路径计算请求，该路径计算请求中携带有用于标识对路径片段进行压缩的压缩标识以及路径建立类型PST；在获取上述源节点至目的节点的路径的标识信息之后，根据上述压缩标识以及PST指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩；接收各路径片段对应的子PCE返回的压缩后的路径片段的标识信息，并根据该路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的路径的标识信息。

Description

跨域的路径的标识信息的确定方法、装置及存储介质
相关申请的交叉引用
本申请基于申请号为201710532649.1、申请日为2017年07月03日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及通信领域，具体而言，涉及一种跨域的路径的标识信息的确定方法、装置及存储介质。
背景技术
RFC5623中讨论了采用分层路径计算单元(Path Computation Element，简称为PCE)架构计算跨domain(域)的流量工程(Traffic Engineering，简称为TE)路径，父PCE能从各子PCE获取到所有domain之间的连接关系，维护domain级拓扑。当父PCE被某个子PCE请求计算跨domain的TE路径时，父PCE首先根据domain级拓扑得出TE路径可能会经过哪些domain序列，然后针对每个domain序列分别向各子PCE请求计算相应domain内的路径片段，父PCE收到各子PCE的计算结果后，将所有路径片段拼接起来得到一条完整的跨domain的TE路径。父PCE将从这些domain序列对应的完整TE路径中挑选出一条最优的路径回复给请求它计算路径的子PCE，后者再将路径回复给相应的路径计算客户(Path Computation Client，简称为PCC)。
draft-ietf-pce-segment-routing-09中讨论了PCE如何将计算得到的TE路径采用分段列表segment list表示以适用于分段路由转发的场景。一般的， 在分段路由场景中，TE路径中的domain内严格显式下一跳可以使用分段路由的邻接adjacency SID(即，段标识segment-id)来表示，而TE路径中的domain间严格显式下一跳则可以使用分段路由的Peer-Adj SID表示。如上，当某个子PCE向父PCE请求计算跨domain的路径时，可以指定路径建立类型(Path Setup Type，简称为PST)为“使用分段路由技术建立路径”，父PCE针对每个domain序列向各子PCE请求计算domain内的路径时也同样指定PST为“使用分段路由技术建立路径”，则各子PCE向父PCE回复的路径片段信息可以使用adjacency SID list表示，父PCE最终将最优路径回复给请求它计算路径的子PCE时也可以使用adjacency SID+Peer-Adj SID list来表示完整的TE路径。然而这里存在的一个主要问题是，完整的TE路径一般很长，导致adjacency SID+Peer-Adj SID list对应的标签栈将很深，很容易超出设备的标签封装能力以及引入转发效率与MTU问题。另外一个问题是，各子PCE可能会依据本地策略不一定向父PCE返回domain内的路径片段信息，如RFC5520定义了path-key的概念与机制，子PCE可能会使用path-key替代显式路由中的路径片段信息回复给父PCE，那么最终TE路径的头节点PCC将无法获得完整的adjacency SID+Peer-Adj SID list。
为了缩短完整TE路径对应的分段路由SID list，draft-ietf-spring-segment-routing-11中定义了绑定分段binding segment，它可以用来指代一条隧道tunnel的转发信息，即如果为完整TE路径中某个路径片段本身额外创建一条tunnel的话，那么该路径片段就可以使用相应的一个绑定段标识Binding SID来表示。基于这个思想，许多协议做了相应的扩展，比如：
1)draft-ietf-isis-segment-routing-extensions-12扩展中间系统到中间系统(Intermediate system to intermediate system，简称为ISIS)并定义了 SID/Label Binding TLV(标签绑定TLV，其中，T为标签Tag，L为长度Length，V为值Value)及其使用方法。不过该方法仅定义了针对SR-TE path(即使用分段路由技术建立的TE路径)的Binding SID/Label，没有定义基于流量工程扩展的资源预留协议建立路径的RSVP-TE path(即使用RSVP-TE信令建立的TE路径)相应的Binding SID/Label(注：RSVP-TE path作为转发邻接Forwarding-adjacency时，可能会分配内部网关协议(Interior Gateway Protocol，简称为IGP)adjacency SID，但不是Binding SID)。另外，该方法仅适用于IGP区域area内，不适用跨domain的TE路径。
2)draft-ietf-idr-bgp-ls-segment-routing-ext-01扩展边界网关协议-链路状态(Border Gateway Protocol-Link State，简称为BGP-LS)(见RFC7752)并定义了Binding SID TLV的通告方法。由于BGP-LS一般是从IGP实例导入链路状态数据，所以该方法与上述ISIS-SR类似，仅定义了针对SR-TE path的Binding SID/Label，没有定义RSVP-TE path相应的Binding SID/Label。另外该方法中随Binding SID要给出路径片段对应的ERO(Explicit Route Object显式路由对象)信息，而前面提到，子PCE不一定会向父PCE暴露其domain内的路径片段信息，所以在分层PCE架构中，该方法最多仅适用于PCC向子PCE上报Binding SID，不适用于子PCE向父PCE上报Binding SID。另外该方法一般仅用于PCC向PCE方向同步数据，不适用于PCE主动创建的tunnel。最后，该方法仅描述了BGP-LS作为一个通道如何携带Binding SID，并不关注针对跨domain的TE路径计算与报文转发给出解决方案。
3)draft-li-pce-tunnel-segment-02中扩展路径计算单元通信协议PCEP(见RFC5440)并定义了通告隧道分段tunnel segment的方法，tunnel segment与前面所述的Binding SID类似，支持RSVP-TE tunnel与SR-TE tunnel。该方法涉及到多种通道，从PCC至PCE方向采取的是类似BGP-LS 的PCE-LS(见draft-dhodylee-pce-pcep-ls-07)来通告，而从PCE向PCC方向采取的是类似NETCONF的PCLabelUpd(见draft-zhao-pce-pcep-extension-for-pce-controller-04)，虽然两者名义上都是PCEP的扩展协议，但差异较大，在实现以及部署时比较复杂。同样，该方法仅描述了PCEP作为一个通道如何通告tunnel segment，并不关注针对跨domain的TE路径计算与报文转发给出解决方案。
4)draft-sivabalan-pce-binding-label-sid-02中也扩展PCEP协议为RSVP-TE path通告Binding label，为SR-TE path通告Binding SID，由PCC将binding label/SID向PCE报告。该方法仅用于PCC向PCE方向同步数据，不适用于PCE主动创建的tunnel。同样，该方法仅描述了PCEP作为一个通道如何通告binding label/SID，并不关注针对跨domain的TE路径计算与报文转发给出解决方案。
针对相关技术中路径标识信息过长的问题，目前尚未提出有效的解决方案。
发明内容
本申请实施例提供了一种跨域的路径的标识信息的确定方法、装置及存储介质，以至少解决相关技术中存在的路径标识信息过长的问题。
根据本申请的一个实施例，提供了一种跨域domain的路径的标识信息的确定方法，包括：接收来自第一子路径计算单元PCE的路径计算请求，其中，所述路径计算请求用于请求获取源节点至目的节点的路径，所述源节点和所述目的节点位于不同的domain中，所述路径包括一个或多个路径片段，所述路径计算请求中携带有用于标识对所述路径片段进行压缩的压缩标识以及路径建立类型PST；在获取所述源节点至所述目的节点的路径的标识信息之后，根据所述压缩标识以及所述PST指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩；接收各路径片段对应 的子PCE返回的压缩后的路径片段的标识信息，并根据所述路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的所述路径的标识信息。
可选地，根据所述压缩标识指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩包括：根据所述压缩标识向各路径片段对应的子PCE发送创建消息，其中，所述创建消息用于请求各路径片段对应的子PCE创建隧道tunnel，并为创建的tunnel分配绑定段标识Binding SID，其中，所述创建消息中携带有所述路径片段的路径信息。
可选地，所述创建消息用于请求各路径片段对应的子PCE创建隧道tunnel包括以下之一：所述创建消息用于请求各路径片段对应的子PCE创建基于流量工程扩展的资源预留协议建立路径的RSVP-TE tunnel；所述创建消息用于请求各路径片段对应的子PCE创建基于分段路由技术建立路径的SR-TE tunnel；所述创建消息用于请求各路径片段对应的子PCE创建RSVP-TE tunnel或者SR-TE tunnel。
可选地，接收各路径片段对应的子PCE返回的压缩后的路径片段的标识信息，并将各压缩后的路径片段的标识信息组成压缩后的所述路径的标识信息包括：接收各路径片段对应的子PCE返回的为创建的tunnel分配的Binding SID；将接收的各Binding SID组成压缩后的所述路径的标识信息。
可选地，所述路径信息包括以下内容：所述路径的路径名，所述路径片段的片段信息，待创建tunnel的起始节点信息和目的节点信息，所述PST。
可选地，在根据所述路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的所述路径的标识信息之后，所述方法包括：将所述压缩后的所述路径的标识信息返回给所述第一子PCE。
根据本申请的另一个实施例，还提供了一种跨域domain的路径的标识信息的确定方法，包括：向父路径计算单元PCE发送路径计算请求，其中，所述路径计算请求用于请求获取源节点至目的节点的路径，所述源节点和 所述目的节点位于不同的domain中，所述路径包括一个或多个路径片段，所述路径计算请求中携带有用于标识对所述路径片段进行压缩的压缩标识以及路径建立类型PST；接收来自所述父PCE的创建消息，其中，所述创建消息为所述父PCE根据所述压缩标识以及所述PST发送的；根据所述创建消息对路径片段的标识信息进行压缩；将压缩后的路径片段的标识信息返回给所述父PCE。
可选地，根据所述创建消息对所述路径片段的标识信息进行压缩包括：确定所述创建消息中携带的所述路径片段的路径信息；根据所述路径信息创建隧道tunnel，并为创建的tunnel分配Binding SID。
可选地，所述创建消息用于请求创建以下tunnel至少之一：基于流量工程扩展的资源预留协议建立路径的RSVP-TE tunnel；基于分段路由技术建立路径的SR-TE tunnel。
可选地，根据所述路径信息创建隧道tunnel包括：根据所述路径信息实例化所述tunnel，并将所述创建消息转发给待创建所述tunnel的作为起始节点的路径计算客户PCC，其中，所述创建消息用于指示所述PCC按照所述路径信息发起创建所述tunnel的流程。
可选地，包括以下之一：当所述创建消息用于请求创建所述RSVP-TE tunnel时，所述创建消息用于指示所述PCC发起RSVP-TE信令建立路径；当所述创建消息用于请求创建所述SR-TE tunnel时，所述创建消息用于指示所述PCC根据分段路由信息计算路径的转发信息。
可选地，为创建的tunnel分配所述Binding SID包括：在由控制器全局统一分配段标识SID的情况下，在根据所述路径信息实例化所述tunnel之后，为所述tunnel分配所述Binding SID并上报给父PCE以及所述PCC；和/或，在由转发设备分配SID并将分配的SID上报给控制器的情况下，接收所述PCC在创建所述tunnel之后为所述tunnel分配的所述Binding SID， 并上报给所述父PCE。
可选地，在将压缩后的路径片段的标识信息返回给所述父PCE之后，所述方法还包括：接收来自所述父PCE的压缩后的所述路径的标识信息；当所述路径计算请求是由预定路径计算客户PCC发起的情况下，将压缩后的所述路径的标识信息返回给所述预定PCC；当所述路径计算请求不是由预定路径计算客户PCC发起的情况下，将压缩后的所述路径的标识信息发送给所述tunnel的作为起始节点的PCC。
根据本申请的另一个实施例，还提供了一种跨域domain的路径的标识信息的确定装置，包括：第一接收模块，配置为接收来自第一子路径计算单元PCE的路径计算请求，其中，所述路径计算请求用于请求获取源节点至目的节点的路径，所述源节点和所述目的节点位于不同的domain中，所述路径包括一个或多个路径片段，所述路径计算请求中携带有用于标识对所述路径片段进行压缩的压缩标识以及路径建立类型PST；指示模块，配置为在获取所述源节点至所述目的节点的路径的标识信息之后，根据所述压缩标识以及所述PST指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩；第二接收模块，配置为接收各路径片段对应的子PCE返回的压缩后的路径片段的标识信息，并根据所述路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的所述路径的标识信息。
可选地，所述指示模块包括：发送单元，配置为根据所述压缩标识向各路径片段对应的子PCE发送创建消息，其中，所述创建消息用于请求各路径片段对应的子PCE创建隧道tunnel，并为创建的tunnel分配Binding SID，其中，所述创建消息中携带有所述路径片段的路径信息。
根据本申请的另一个实施例，还提供了一种跨域domain的路径的标识信息的确定装置，包括：发送模块，配置为向父路径计算单元PCE发送路径计算请求，其中，所述路径计算请求用于请求获取源节点至目的节点的 路径，所述源节点和所述目的节点位于不同的domain中，所述路径包括一个或多个路径片段，所述路径计算请求中携带有用于标识对所述路径片段进行压缩的压缩标识以及路径建立类型PST；第三接收模块，配置为接收来自所述父PCE的创建消息，其中，所述创建消息为所述父PCE根据所述压缩标识以及所述PST发送的；压缩模块，配置为根据所述创建消息对路径片段的标识信息进行压缩；第一返回模块，配置为将压缩后的路径片段的标识信息返回给所述父PCE。
可选地，所述压缩模块包括：确定单元，配置为确定所述创建消息中携带的所述路径片段的路径信息；创建单元，配置为根据所述路径信息创建隧道tunnel，并为创建的tunnel分配Binding SID。
可选地，所述装置还包括：第四接收模块，配置为在将压缩后的路径片段的标识信息返回给所述父PCE之后，接收来自所述父PCE的压缩后的所述路径的标识信息；第二返回模块，配置为当所述路径计算请求是由预定路径计算客户PCC发起的情况下，将压缩后的所述路径的标识信息返回给所述预定PCC；第三返回模块，配置为当所述路径计算请求不是由预定路径计算客户PCC发起的情况下，将压缩后的所述路径的标识信息发送给所述tunnel的作为起始节点的PCC。
根据本申请的另一个实施例，还提供了一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行上述任一项所述的方法。
根据本申请的又一个实施例，还提供了一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行上述任一项所述的方法。
通过本申请，由于在获取了源节点至目的节点的路径的标识信息之后，对该路径的标识信息进行了压缩，从而有效的缩小了路径的标识信息的长度，从而解决了相关技术中存在的路径标识信息过长的问题。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是根据本申请实施例的第一种跨域的路径的标识信息的确定方法流程图；
图2是根据本申请实施例的第二种跨域的路径的标识信息的确定方法流程图；
图3所示是根据本申请具体实施方式的RP object示意图；
图4所示是根据本申请具体实施方式的Path Setup Type TLV示意图；
图5所示是根据本申请具体实施方式的TE-PATH-BINDING TLV示意图；
图6所示是根据本申请实施例的分层PCE网络架构图；
图7是根据本申请实施例的第一种跨域的路径的标识信息的确定装置的结构框图；
图8是根据本申请实施例的第二种跨域的路径的标识信息的确定装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例一
图1是根据本申请实施例的第一种跨域的路径的标识信息的确定方法 流程图，如图1所示，该流程包括如下步骤：
步骤S102，接收来自第一子路径计算单元PCE的路径计算请求，其中，该路径计算请求用于请求获取源节点至目的节点的路径，该源节点和目的节点位于不同的domain中，该路径包括一个或多个路径片段，该路径计算请求中携带有用于标识对路径片段进行压缩的压缩标识以及路径建立类型PST；
步骤S104，在获取上述源节点至目的节点的路径的标识信息之后，根据上述压缩标识以及PST指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩；
步骤S106，接收各路径片段对应的子PCE返回的压缩后的路径片段的标识信息，并根据该路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的路径的标识信息。
其中，执行上述操作的可以是父PCE，在本实施例一中，是对父PCE侧的处理进行的说明。
通过上述步骤，由于在获取了源节点至目的节点的路径的标识信息之后，对该路径的标识信息进行了压缩，从而有效的缩小了路径的标识信息的长度，从而解决了相关技术中存在的路径标识信息过长的问题。
在一个可选的实施例中，根据上述压缩标识指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩包括：根据上述压缩标识向各路径片段对应的子PCE发送创建消息，其中，该创建消息用于请求各路径片段对应的子PCE创建隧道tunnel，并为创建的tunnel分配绑定段标识Binding SID，其中，该创建消息中携带有上述路径片段的路径信息。
在一个可选的实施例中，上述创建消息用于请求各路径片段对应的子PCE创建隧道tunnel包括以下之一：上述创建消息用于请求各路径片段对应的子PCE创建基于流量工程扩展的资源预留协议建立路径的RSVP-TE  tunnel；上述创建消息用于请求各路径片段对应的子PCE创建基于分段路由技术建立路径的SR-TE tunnel；上述创建消息用于请求各路径片段对应的子PCE创建RSVP-TE tunnel或者SR-TE tunnel。
在一个可选的实施例中，接收各路径片段对应的子PCE返回的压缩后的路径片段的标识信息，并将各压缩后的路径片段的标识信息组成压缩后的所述路径的标识信息包括：接收各路径片段对应的子PCE返回的为创建的tunnel分配的Binding SID；将接收的各Binding SID组成压缩后的路径的标识信息。
在一个可选的实施例中，上述路径信息包括以下内容：路径的路径名，路径片段的片段信息，待创建tunnel的起始节点信息和目的节点信息，上述PST。
在一个可选的实施例中，在根据上述路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的路径的标识信息之后，上述方法还包括：将压缩后的所述路径的标识信息返回给第一子PCE。也就是说，作为第一子PCE发送的路径计算请求的响应，将压缩后的路径的标识信息返回给第一子PCE，第一子PCE在获取了压缩后的路径的标识信息之后，可以继续执行后续的操作，例如，可以将获取的压缩后的路径的标识信息发送给相应的PCC，PCC再依据路径的标识信息封装报文，并转发报文。
实施例二
图2是根据本申请实施例的第二种跨域的路径的标识信息的确定方法流程图，如图2所示，该流程包括如下步骤：
步骤S202，向父路径计算单元PCE发送路径计算请求，其中，该路径计算请求用于请求获取源节点至目的节点的路径，该源节点和目的节点位于不同的domain中，该路径包括一个或多个路径片段，该路径计算请求中携带有用于标识对所述路径片段进行压缩的压缩标识以及路径建立类型 PST；
步骤S204，接收来自父PCE的创建消息，其中，该创建消息为父PCE根据上述压缩标识以及PST发送的；
步骤S206，根据上述创建消息对路径片段的标识信息进行压缩；
步骤S208，将压缩后的路径片段的标识信息返回给父PCE。
其中，执行上述操作的可以是子PCE(例如，实施例一中的第一子PCE)，在本实施例二中，是对该子PCE侧的处理进行的说明。
通过上述步骤，由于在获取了源节点至目的节点的路径的标识信息之后，对该路径的标识信息进行了压缩，从而有效的缩小了路径的标识信息的长度，从而解决了相关技术中存在的路径标识信息过长的问题。
在一个可选的实施例中，根据上述创建消息对路径片段的标识信息进行压缩包括：确定上述创建消息中携带的路径片段的路径信息；根据上述路径信息创建隧道tunnel，并为创建的tunnel分配Binding SID。
在一个可选的实施例中，上述创建消息用于请求创建以下tunnel至少之一：基于流量工程扩展的资源预留协议建立路径的RSVP-TE tunnel；基于分段路由技术建立路径的SR-TE tunnel。需要说明的是，在本实施例中，RSVP-TE tunnel以及SR-TE tunnel仅是两种优选的实施例，还可以根据实际情况以及技术发展创建其他类型的tunnel，在此，不做限定。
在一个可选的实施例中，根据上述路径信息创建隧道tunnel包括：根据上述路径信息实例化tunnel，并将上述创建消息转发给待创建tunnel的作为起始节点的路径计算客户PCC，其中，该创建消息用于指示PCC按照上述路径信息发起创建tunnel的流程。在本实施例中，是由PCC进行隧道的创建。
在一个可选的实施例中，在待创建的tunnel类型不同时，指示PCC执行的具体操作也是不同的，可选的，当上述创建消息用于请求创建RSVP-TE  tunnel时，上述创建消息用于指示PCC发起RSVP-TE信令建立路径；可选的，当上述创建消息用于请求创建SR-TE tunnel时，上述创建消息用于指示PCC根据分段路由信息计算路径的转发信息。
在一个可选的实施例中，针对如何为创建的tunnel分配Binding SID分情况进行说明：在由控制器全局统一分配段标识SID的情况下，在根据上述路径信息实例化所述tunnel之后，为tunnel分配Binding SID并上报给父PCE以及上述PCC；和/或，在由转发设备分配SID并将分配的SID上报给控制器的情况下，接收上述PCC在创建tunnel之后为tunnel分配的所述Binding SID，并上报给父PCE。
在一个可选的实施例中，在将压缩后的路径片段的标识信息返回给父PCE之后，上述方法还包括：接收来自父PCE的压缩后的路径的标识信息；当上述路径计算请求是由预定路径计算客户PCC发起的情况下，将压缩后的路径的标识信息返回给预定PCC；当路径计算请求不是由预定路径计算客户PCC发起的情况下，将压缩后的路径的标识信息发送给tunnel的作为起始节点的PCC。
实施例三
上述的实施例是分别从父PCE和子PCE侧进行描述的，下面结合整体操作对本申请进行说明：
在本实施例中，可以在PCC侧发起建立的SR-TE tunnel或者PCE主动创建的SR-TE tunnel中，显式的配置可以针对其可能的路径片段进行压缩的能力，该能力标志(对应于上述的压缩标识)将包含在PCC向PCE(以及子PCE向父PCE)发起的路径计算请求中。根据该能力标志，父PCE将触发每个domain的子PCE根据相应的路径片段额外创建RSVP-TE tunnel(或SR-TE tunnel)，各子PCE主动为额外创建的RSVP-TE tunnel(或者SR-TE tunnel)分配Binding SID或者从RSVP-TE tunnel(或SR-TE tunnel) 的头节点PCC获取Binding SID。各子PCE将Binding SID同步给父PCE，父PCE将Binding SID应用在跨domain的完整TE路径对应的分段路由SID list中回复给向它发起路径计算请求的子PCE，后者再下发给其PCC。PCC使用SID list封装报文进行转发。
本实施例中所提供的跨域TE路径的计算与报文转发方法具体包括以下步骤：
第一步：
在PCC侧发起建立的SR-TE tunnel或者PCE主动创建的SR-TE tunnel中，显式的配置可以针对其可能的路径片段进行压缩的能力。具体压缩能力可以是：
Option1：不压缩；
Option2：仅针对路径片段额外建立RSVP-TE tunnel；
Option3：仅针对路径片段额外建立SR-TE tunnel；
Option4：针对路径片段额外建立RSVP-TE tunnel或者SR-TE tunnel，不做限制；
如果配置为Option1，则本申请实施例中描述的方法与RFC6805描述的方法无异。在本实施中主要针对Option2或Option3或Option4进行描述，为了描述方便，在本实施中统一将Option2、Option3、Option4称为“要压缩”。需要说明的是，除了上述四种Option以外，未来还可以类似扩展支持其它Option。
第二步：
对于跨domain的TE路径计算，按照RFC6805描述的方法，对于PCC侧发起建立的SR-TE tunnel，PCC将向其所处domain的子PCE(记为子PCE1)发起路径计算请求，或者对于子PCE1主动建立的SR-TE tunnel，子PCE1将向父PCE发起路径计算请求。路径计算请求消息中将指明PST 为“使用分段路由技术建立路径”，同时还包含上述路径片段压缩能力标志。假设请求消息中还包含有路径名为path-name-SD。
按照RFC6805描述的方法，父PCE将首先根据其维护的domain级拓扑信息，计算出跨domain的TE路径可能穿越哪些domain序列，然后针对每个domain序列，向各domain的子PCE发起domain内的路径计算请求，注意这里父PCE向各子PCE发送的路径计算请求消息只是用于获取潜在路径用于择优，所以消息中包含的路径片段压缩标志必须为不压缩，PST可以仍然设置为“使用分段路由技术建立路径”。父PCE最终会从众多domain序列中计算出一条最优的跨domain的TE路径。该TE路径可能包含有各domain内的具体路径片段对应的IP address list或SID list，或者包含有各domain内具体路径片段对应的path-key。
需要说明的是，由于PST为“使用分段路由技术建立路径”，所以各子PCE可以尝试向父PCE回复SID list，当然回复IP address list或者IP address+SID混合list也都是协议允许的。该说明同样适用于父PCE向子PCE1回复完整TE路径时。
各子PCE一般可以通过BGP-LS收集其所负责的domain的domain内拓扑信息以及该domain连接其它domain的domain间链路信息，各子PCE需要将domain间链路信息再通过BGP-LS上报给父PCE。除了BGP-LS以外，还可以通过其它通道，在本申请实施例中不做限制。
第三步
与RFC6805描述的方法不同的是，此时父PCE并不立即将上述最优的完整TE路径回复给子PCE1，而是检查发现子PCE1发给它的相应路径计算请求消息中包含的路径片段压缩标志提示“要压缩”，所以父PCE针对每个最优的完整路径中每个domain对应的路径片段，分别向各domain对应的子PCE发送“主动创建tunnel”消息，在消息中至少提供：路径名、路 径片段信息、待创建tunnel的起始节点(即路径片段的首节点)与目的节点(即路径片段的尾节点)信息、以及PST。其中：路径名可以在完整路径名(即path-name-SD)后再加尾巴，如path-name-SD-路径片段首节点-路径片段尾节点，以便全局唯一区分；路径片段信息就是之前相应的子PCE回复给父PCE的，只不过现在被父PCE反过来作为ERO提供给该子PCE创建tunnel而已；待创建tunnel的起始节点与目的节点就是相应路径片段的首节点与尾节点；PST要根据上述路径片段压缩标志来设置，如果路径片段压缩标志为Option2，则PST要设置为“使用RSVP-TE信令建立路径”，如果路径片段压缩标志为Option3，则PST要设置为“使用分段路由技术建立路径”，如果路径片段压缩标志为Option4，则PST要设置为“使用RSVP-TE信令或分段路由技术建立路径”。
第四步：
各domain对应的子PCE收到父PCE的“主动创建tunnel”消息后，在本地实例化相应的tunnel，并将该“主动创建tunnel”消息转发给待创建tunnel的起始节点PCC，该PCC将在网络中按照消息中给出的PST与ERO发起建立路径。比如PST为“使用RSVP-TE信令建立路径”，则该PCC发起RSVP-TE信令建立路径；比如PST为“使用分段路由技术建立路径”，则该PCC直接根据分段路由信息计算路径的转发信息；比如PST为“使用RSVP-TE信令或分段路由技术建立路径”，则该PCC根据自身实际能力，选择发起RSVP-TE信令建立路径或直接根据分段路由信息计算路径的转发信息。
如果是控制器全局统一分配SID的部署场景，则各domain对应的子PCE在实例化相应的tunnel后，就可以主动为相应的tunnel分配相应的Binding SID，并上报给父PCE以及下发给PCC。如果是由转发设备侧自行配置SID并上报控制器的部署场景，则相应tunnel的起始节点PCC在tunnel 建立好后，就可以为tunnel分配相应的Binding SID并上报子PCE，子PCE继续上报给父PCE。
需要说明的是：为tunnel分配的Binding SID具有本地属性，一般情况下不需要做到全局唯一。如果要求全局唯一，则应该部署控制器全局统一分配SID的场景，并且各子PCE掌控的SID资源池应相互不重叠，这可以是通过管理的方式或者其它动态学习的方式。
第五步：
父PCE从各子PCE收到相应domain内路径片段对应创建的tunnel的Binding SID后，就可以对原始的完整TE路径对应的SID list进行缩减优化了。实际上，不管之前各子PCE给父PCE回复的路径片段信息是IP address list或SID list或两种的混合，甚至是path-key，父PCE都不关心路径片段信息的具体ERO内容，该路径片段在完整TE路径对应的SID list中仅需使用其Binding SID来表示。另外，再结合domain间链路相应的Peer-Adj SID，最终缩减优化后的完整TE路径的SID list一般为：{Binding SID1,Peer-Adj SID1,Binding SID2,Peer-Adj SID2,…,Binding SIDn}。注意SID list中各Binding SID与Peer-Adj SID之前也可以插入相应起始节点对应的node SID，但这并非必须。另外，特殊情况下Binding SID1可能不存在，比如完整TE路径的起始节点恰好是domain序列中第一个domain的出口边界节点。
第六步：
父PCE将上述缩减优化后的SID list回复给子PCE1，作为之前从子PCE1收到的跨domain TE路径计算请求消息的响应。子PCE1继续将该SID list回复给之前从PCC收到对应路径计算请求的PCC，或者子PCE1主动创建跨domain的隧道时将该SID list下发给隧道头节点PCC。
PCC将可以使用该SID list作为跨domain的SR-TE tunnel的转发信息。 注意SID list中第一个SID如果是Binding SID的话，该Binding SID实际上指代的是该PCC所处domain的路径片段对应的tunnel的转发信息，所以SR-TE tunnel最终生成转发信息时，要将第一个SID(Binding SID)换成对应的tunnel的转发信息。类似的，SID list中第一个SID如果是Peer-Adj SID的话，要将第一个SID(Peer-Adj SID)换成对应的domain间链路的转发信息。
采用本申请实施例中的方法，与现有技术相比，能显著缩短跨domain的TE路径的分段路由SID list，减小为报文封装的标签栈深度，提高报文载荷效率以及避免MTU分片。
实施例四：
在本实施例中结合附图对技术方案的实施作进一步的详细描述：
图3所示是根据本申请具体实施方式的RP object示意图，是在RFC5440、RFC5520、RFC5541、RFC5557定义的RP object基础上，在Flags标志字段中新增一个拟占用三个比特的CF(Compress Flag)标志，用于标识是否需要对路径进行压缩，具体取值的含义如下：
0：表示不需要对路径进行压缩；
1：表示采取仅针对路径片段额外建立RSVP-TE tunnel的方式进行压缩；
2：表示采取仅针对路径片段额外建立SR-TE tunnel的方式进行压缩；
3：表示采取针对路径片段额外建立RSVP-TE tunnel或者SR-TE tunnel的方式进行压缩；
图4所示是根据本申请具体实施方式的Path Setup Type TLV示意图，是在draft-ietf-pce-lsp-setup-type-04的基础上，新增一种PST＝2，以表示路径建立技术可以是“RSVP-TE信令或者分段路由技术”。Path Setup Type TLV可以在RP object(参考RFC5440)和SRP object(参考 draft-ietf-pce-stateful-pce-18)中携带。当前draft-ietf-pce-lsp-setup-type-04定义了PST＝0，表示路径建立技术采取RSVP-TE信令，draft-ietf-pce-segment-routing-09定义了PST＝1，表示路径建立技术采取分段路由技术。
图5所示是根据本申请具体实施方式的TE-PATH-BINDING TLV示意图，是在draft-sivabalan-pce-binding-label-sid-02定义的TE-PATH-BINDING TLV基础上，扩展其使用方式。draft-sivabalan-pce-binding-label-sid-02定义了TE-PATH-BINDING TLV，包含在PCRpt消息中的LSP object中，用于从PCC向PCE报告相应TE路径的Binding SID，本实施方式沿用该方法用于从PCC向子PCE、以及子PCE向父PCE上报相应domain内路径片段额外创建的tunnel的Binding SID，适用于转发设备侧自行配置SID并上报控制器的部署场景。除此之外，本实施方式还将扩展draft-ietf-pce-stateful-pce-18与draft-ietf-pce-pce-initiated-lsp-09中关于LSP object的使用方法，分别允许在PCUpd消息和PCInitiate消息中包含的LSP object中包含上述TE-PATH-BINDING TLV，用于从子PCE向PCC下发相应domain内路径片段额外创建的tunnel的Binding SID，适用于控制器全局统一分配SID的部署场景。
具体实施例一
图6所示是根据本申请实施例的分层PCE网络架构图，包含三个domain，分别是AS1、AS2、AS3，对应的子PCE分别是PCE1、PCE2、PCE3，父PCE为PCE4。本实施例中，假设：部署场景为集中式控制器统一分配SID并下发至转发设备；PCE1希望主动创建一条源节点S至目的节点D的SR-TE tunnel，并且PCE1知道其它AS(AS2、AS3)除边界节点已经升级支持分段路由功能以外，内部节点均仅支持RSVP-TE但不支持分段路由功能。现在我们来看PCE1主动创建一条源节点S至目的节点D的SR-TE  tunnel的具体步骤，如下：
步骤110，PCE1主动创建SR-TE tunnel，源节点为S，目的节点为D。PCE1根据其自身维护的TED(TE database)信息，发现目的节点D不属于AS1，则PCE1向父PCE(PCE4)发送PCReq消息以请求计算跨domain的TE路径，消息中各字段的设置方法可参考RFC5440与draft-ietf-pce-stateful-pce-18并结合本申请实施例中的方案，以下仅给出与本申请实施例中处理流程强相关的主要信息：
<RP object>：PST设置为1，表明使用分段路由技术建立路径；将其中的CF标志设置为1，以便各AS内针对路径片段额外创建RSVP-TE tunnel进行压缩；
<END-POINTS object>：源节点为S，目的节点为D；
<LSP object>：path-name设置为path-name-SD-100；
其它object如约束条件等不再具体描述。
步骤120，PCE4收到请求后，按照RFC6805描述的方法，先确定目的节点所在的domain为AS3，然后确定可能的domain序列，本实施例中，仅存在一个domain序列即S-(AS1)-A1-A2-(AS2)-A3-A4-(AS3)-D。针对该domain序列，PCE4向序列中每个domain对应的子PCE分别发送PCReq消息，请求计算各domain内的路径片段。比如PCE4向PCE1发送PCReq消息以请求计算源节点S至目的节点A1的路径片段，消息中的主要信息如下：
<RP object>：PST设置为1，表明使用分段路由技术建立路径；CF标志必须设置为0，表示不对路径做压缩；
<END-POINTS object>：源节点为S，目的节点为A1；
PCE4亦向PCE2发送PCReq消息以请求计算源节点A2至目的节点A3的路径片段，以及向PCE3发送PCReq消息以请求计算源节点A4至目 的节点D的路径片段。不再赘述。
步骤130，各子PCE收到PCE4发来的路径计算请求后，计算出相应的路径片段并发送PCRep消息回复给PCE4。本实施例中，PCE1将计算出路径片段S-P1-P2-A1，PCE2将计算出路径片段A2-P3-P4-A3，PCE3将计算出路径片段A4-P5-P6-D。一般的，各子PCE回复给PCE4的PCERep消息中包含的ERO object中将给出路径片段信息，可以是IP address list、SID list、IP address与SID混合list，甚至出于安全考虑可以是一个path-key。不过本实施例中，由于各AS内不支持SR，所以各子PCE回复给PCE4的路径片段信息可以是IP address list或者path-key。
步骤140，针对domain序列S-(AS1)-A1-A2-(AS2)-A3-A4-(AS3)-D，PCE4从所有子PCE收到其中所有domain的路径片段后，将得到完整的端到端的TE路径。本实施例中，由于不再存在其它domain序列，所以上述完整的TE路径将作为最优路径。此时，PCE4不急于将该最优的完整TE路径回复给PCE1，而是检查发现之前从PCE1收到的相应路径计算请求中CF标志为1，则为各路径片段主动创建RSVP-TE tunnel并向各子PCE发送PCInitiate消息。比如PCE4在内部为AS1对应的路径片段S-P1-P2-A1额外创建相应的RSVP-TE tunnel，其包含的主路径可取名为path-name-SD-100-SA1(注：这种命名方式是在母路径名称path-name-SD-100的尾部加上子路径首尾关键信息S、A1，可保证全局唯一)，相应的，PCE4发给PCE1的PCInitiate消息中，主要信息如下：
<SRP object>：PST设置为0，表示使用RSVP-TE建立路径；
<LSP object>：path-name设置为path-name-SD-100-SA1；
<END-POINTS object>：源节点为S，目的节点为A1；
<ERO object>：S-P1-P2-A1，具体可以为IP address list或path-key，也即把之前从PCE1收到的路径片段信息原封不动的填入。
PCE4亦在内部为AS2对应的路径片段A2-P3-P4-A3额外创建相应的RSVP-TE tunnel，其包含的主路径可取名为path-name-SD-100-A2A3，并相应的向PCE2发送PCInitiate消息；PCE4亦在内部为AS3对应的路径片段A4-P5-P6-D额外创建相应的RSVP-TE tunnel，其包含的主路径可取名为path-name-SD-100-A4D，并相应的向PCE3发送PCInitiate消息。不再赘述。
步骤150，各子PCE收到PCE4的PCInitiate消息后，也将在内部主动创建相应的RSVP-TE tunnel并继续向该tunnel的头节点PCC发送PCInitiate消息。注意各子PCE继续向tunnel头节点PCC下发的PCInitiate消息中，ERO object中包含的是明确的严格逐跳显式路径，即可以是IP address list，但不能是path-key。各tunnel头节点将在网络内通过RSVP-TE信令建立路径，协商标签。
本实施例中，各子PCE在创建好相应RSVP-TE tunnel后，还将主动为该RSVP-TE tunnel分配Binding SID，比如，PCE1上为其上述创建的RSVP-TE tunnel分配Binding SID＝1000，PCE2上为其上述创建的RSVP-TE tunnel分配Binding SID＝2000，PCE3上为其上述创建的RSVP-TE tunnel分配Binding SID＝3000。各子PCE可将Binding SID随上述PCInitiate消息或者后续的PCUpd消息下发到tunnel头节点PCC，也可以随PCRpt消息上报给PCE4。各tunnel头节点收到Binding SID后，将会建立以Binding SID为键值的标签表项，用于指导报文向该tunnel转发，标签操作为将入标签Binding SID交换成RSVP-TE tunnel包含的出标签。
需要说明的是，各子PCE还为其所负责domain至其它domain的domain间链路分配Peer-Adj SID，并通过BGP-LS上报给PCE4。
步骤160，PCE4收到所有子PCE的Binding SID上报后，就可以将原始的完整TE路径采用压缩后的SID list表示并通过PCRep消息回复给PCE1，本实施例中压缩后的SID list可以为：{1000,Peer-Adj-SID-A1A2, 2000,Peer-Adj-SID-A3A4,3000}。
步骤170，PCE1收到PCE4的PCRep消息后，继续向S节点PCC发送PCInitiate消息触发S节点上实例化相应的SR-TE tunnel，包含上述压缩后的SID list。
S节点上将创建相应的SR-TE tunnel，在为该SR-TE tunnel生成转发表项时，要将上述SID list中第一个SID即1000查找标签表项换成相应的RSVP-TE tunnel的转发信息，其它SID不变。
步骤180，S节点上，向上述SR-TE tunnel发送的报文，将会被压上相应的标签栈：{RSVP-TE tunnel-SA1 label,Peer-Adj-SID-A1A2,2000,Peer-Adj-SID-A3A4,3000}，即顶层标签为前述AS1内路径片段额外创建的RSVP-TE tunnel对应的出标签，下层标签是domain间链路A1-A2对应的Peer-Adj SID，再下层标签是AS2内路径片段额外创建的RSVP-TE tunnel对应的Binding SID，再下层标签是domain间链路A3-A4对应的Peer-Adj SID，再下层标签是AS3内路径片段额外创建的RSVP-TE tunnel对应的Binding SID。报文将会沿期望的跨domain的TE路径转发。
具体实施例二
本具体实施例与具体实施例一基本类似，区别是本实施例中SID是由转发设备侧分配并上送(如通过BGP-LS)给控制器的部署场景。则PCE1主动建立一条从源节点S至目的节点D的跨domain的SR-TE tunnel的流程与实施例一是基本类似的，只不过其中涉及到的各domain的路径片段额外创建的RSVP-TE tunnel的Binding SID是由tunnel头节点自己分配并通过PCRpt消息上报给相应的子PCE，子PCE继续通过PCRpt消息将Binding SID上报给PCE4，其它流程与实施例一无异。
具体实施例三
本具体实施例与具体实施例一基本类似，区别是本实施例中是由S节点建立一条从源节点S至目的节点D的跨domain的SR-TE tunnel，则S节点PCC将向PCE1发送PCReq消息，该消息与实施例一中子PCE1发给PCE4的PCReq消息是一样的，其它剩余流程与实施例一相同，并且最终PCE1会向S节点PCC发送PCRep消息回复路径计算结果，其中包含压缩后的SID list。
具体实施例四
本具体实施例与具体实施例一基本相同，区别是所有domain都已经升级支持分段路由功能，网络中不再支持RSVP-TE。现在我们来看PCE1主动创建一条源节点S至目的节点D的SR-TE tunnel的具体步骤，如下：
步骤410，PCE1主动创建SR-TE tunnel，源节点为S，目的节点为D。PCE1根据其自身维护的TED(TE database)信息，发现目的节点D不属于AS1，则PCE1向父PCE(PCE4)发送PCReq消息以请求计算跨domain的TE路径，消息中各字段的设置方法可参考RFC5440与draft-ietf-pce-stateful-pce-18并结合本申请实施例中的方案，以下仅给出与本申请实施例中的处理流程强相关的主要信息：
<RP object>：PST设置为1，表明使用分段路由技术建立路径；将其中的CF标志设置为2，以便各AS内针对路径片段额外创建SR-TE tunnel进行压缩；
<END-POINTS object>：源节点为S，目的节点为D；
<LSP object>：path-name设置为path-name-SD-100；
其它object如约束条件等不再具体描述。
步骤420，PCE4收到请求后，按照RFC6805描述的方法，先确定目的节点所在的domain为AS3，然后确定可能的domain序列，本实施例中，仅存在一个domain序列即S-(AS1)-A1-A2-(AS2)-A3-A4-(AS3)-D。针对该 domain序列，PCE4向序列中每个domain对应的子PCE分别发送PCReq消息，请求计算各domain内的路径片段。比如PCE4向PCE1发送PCReq消息以请求计算源节点S至目的节点A1的路径片段，消息中的主要信息如下：
<RP object>：PST设置为1，表明使用分段路由技术建立路径；CF标志必须设置为0，表示不对路径做压缩；
<END-POINTS object>：源节点为S，目的节点为A1；
PCE4亦向PCE2发送PCReq消息以请求计算源节点A2至目的节点A3的路径片段，以及向PCE3发送PCReq消息以请求计算源节点A4至目的节点D的路径片段。不再赘述。
步骤430，各子PCE收到PCE4发来的路径计算请求后，计算出相应的路径片段并发送PCRep消息回复给PCE4。本实施例中，PCE1将计算出路径片段S-P1-P2-A1，PCE2将计算出路径片段A2-P3-P4-A3，PCE3将计算出路径片段A4-P5-P6-D。一般的，各子PCE回复给PCE4的PCERep消息中包含的ERO object中将给出路径片段信息，可以是IP address list、SID list、IP address与SID混合list，甚至出于安全考虑可以是一个path-key。不过本实施例中，由于各AS内均支持SR，所以各子PCE回复给PCE4的路径片段信息可以是SID list或者path-key。
步骤440，针对domain序列S-(AS1)-A1-A2-(AS2)-A3-A4-(AS3)-D，PCE4从所有子PCE收到其中所有domain的路径片段后，将得到完整的端到端的TE路径。本实施例中，由于不再存在其它domain序列，所以上述完整的TE路径将作为最优路径。此时，PCE4不急于将该最优的完整TE路径回复给PCE1，而是检查发现之前从PCE1收到的相应路径计算请求中CF标志为2，则为各路径片段主动创建SR-TE tunnel并向各子PCE发送PCInitiate消息。比如PCE4在内部为AS1对应的路径片段S-P1-P2-A1额外 创建相应的SR-TE tunnel，其包含的主路径可取名为path-name-SD-100-SA1(注：这种命名方式是在母路径名称path-name-SD-100的尾部加上子路径首尾关键信息S、A1，可保证全局唯一)，相应的，PCE4发给PCE1的PCInitiate消息中，主要信息如下：
<SRP object>：PST设置为1，表示使用分段路由技术建立路径；
<LSP object>：path-name设置为path-name-SD-100-SA1；
<END-POINTS object>：源节点为S，目的节点为A1；
<ERO object>：S-P1-P2-A1，具体可以为SID list或path-key，也即把之前从PCE1收到的路径片段信息原封不动的填入。
PCE4亦在内部为AS2对应的路径片段A2-P3-P4-A3额外创建相应的SR-TE tunnel，其包含的主路径可取名为path-name-SD-100-A2A3，并相应的向PCE2发送PCInitiate消息；PCE4亦在内部为AS3对应的路径片段A4-P5-P6-D额外创建相应的SR-TE tunnel，其包含的主路径可取名为path-name-SD-100-A4D，并相应的向PCE3发送PCInitiate消息。不再赘述。
步骤450，各子PCE收到PCE4的PCInitiate消息后，也将在内部主动创建相应的SR-TE tunnel并继续向该tunnel的头节点PCC发送PCInitiate消息。注意各子PCE继续向tunnel头节点PCC下发的PCInitiate消息中，ERO object中包含的是明确的SID list，不能是path-key。各tunnel头节点将生成相应的SR-TE tunnel，转发信息使用相应的SID list生成。
本实施例中，各子PCE在创建好相应SR-TE tunnel后，还将主动为该SR-TE tunnel分配Binding SID，比如，PCE1上为其上述创建的SR-TE tunnel分配Binding SID＝1000，PCE2上为其上述创建的SR-TE tunnel分配Binding SID＝2000，PCE3上为其上述创建的SR-TE tunnel分配Binding SID＝3000。各子PCE可将Binding SID随上述PCInitiate消息或者后续的PCUpd消息下发到tunnel头节点PCC，也可以随PCRpt消息上报给PCE4。各tunnel 头节点收到Binding SID后，将会建立以Binding SID为键值的标签表项，用于指导报文向该tunnel转发，标签操作为将入标签Binding SID交换成SR-TE tunnel包含的出标签栈。
需要说明的是，各子PCE还为其所负责domain至其它domain的domain间链路分配Peer-Adj SID，并通过BGP-LS上报给PCE4。
步骤460，PCE4收到所有子PCE的Binding SID上报后，就可以将原始的完整TE路径采用压缩后的SID list表示并通过PCRep消息回复给PCE1，本实施例中压缩后的SID list可以为：{1000,Peer-Adj-SID-A1A2,2000,Peer-Adj-SID-A3A4,3000}。
步骤470，PCE1收到PCE4的PCRep消息后，继续向S节点PCC发送PCInitiate消息触发S节点上实例化相应的SR-TE tunnel，包含上述压缩后的SID list。
S节点上将创建相应的SR-TE tunnel，在为该SR-TE tunnel生成转发表项时，要将上述SID list中第一个SID即1000查找标签表项换成相应的SR-TE tunnel的转发信息(一般是一个标签栈)，其它SID不变。
步骤480，S节点上，向上述SR-TE tunnel发送的报文，将会被压上相应的标签栈：{SR-TE tunnel-SA1 SID list,Peer-Adj-SID-A1A2,2000,Peer-Adj-SID-A3A4,3000}，即顶层标签为前述AS1内路径片段额外创建的SR-TE tunnel对应的出标签栈，然后下层标签是domain间链路A1-A2对应的Peer-Adj SID，再下层标签是AS2内路径片段额外创建的SR-TE tunnel对应的Binding SID，再下层标签是domain间链路A3-A4对应的Peer-Adj SID，再下层标签是AS3内路径片段额外创建的SR-TE tunnel对应的Binding SID。报文将会沿期望的跨domain的TE路径转发。
具体实施例五
本具体实施例与具体实施例四基本类似，区别是本实施例中SID是由 转发设备侧分配并上送(如通过BGP-LS)给控制器的部署场景。则PCE1主动建立一条从源节点S至目的节点D的跨domain的SR-TE tunnel的流程与实施例四是基本类似的，只不过其中涉及到的各domain的路径片段额外创建的SR-TE tunnel的Binding SID是由tunnel头节点自己分配并通过PCRpt消息上报给相应的子PCE，子PCE继续通过PCRpt消息将Binding SID上报给PCE4，其它流程与具体实施例四无异。
具体实施例六
本具体实施例与具体实施例四基本类似，区别是本实施例中是由S节点建立一条从源节点S至目的节点D的跨domain的SR-TE tunnel，则S节点PCC将向PCE1发送PCReq消息，该消息与具体实施例一中子PCE1发给PCE4的PCReq消息是一样的，其它剩余流程与具体实施例一相同，并且最终PCE1会向S节点PCC发送PCRep消息回复路径计算结果，其中包含压缩后的SID list。
具体实施例七
本具体实施例与具体实施例一基本相同，区别是所有AS1、AS2已经升级支持分段路由功能且不再支持RSVP-TE，而AS3仅边界节点升级支持了分段路由功能且内部节点仍只支持RSVP-TE。现在我们来看PCE1主动创建一条源节点S至目的节点D的SR-TE tunnel的具体步骤，如下：
步骤710，PCE1主动创建SR-TE tunnel，源节点为S，目的节点为D。PCE1根据其自身维护的TED(TE database)信息，发现目的节点D不属于AS1，则PCE1向父PCE(PCE4)发送PCReq消息以请求计算跨domain的TE路径，消息中各字段的设置方法可参考RFC5440与draft-ietf-pce-stateful-pce-18并结合本申请实施例中的方案，以下仅给出与本申请实施例处理流程强相关的主要信息：
<RP object>：PST设置为1，表明使用分段路由技术建立路径；将其中的CF标志设置为3，以便各AS内针对路径片段根据实际能力额外创建RSVP-TE tunnel或者SR-TE tunnel进行压缩；
<END-POINTS object>：源节点为S，目的节点为D；
<LSP object>：path-name设置为path-name-SD-100；
其它object如约束条件等不再具体描述。
步骤720，PCE4收到请求后，按照RFC6805描述的方法，先确定目的节点所在的domain为AS3，然后确定可能的domain序列，本实施例中，仅存在一个domain序列即S-(AS1)-A1-A2-(AS2)-A3-A4-(AS3)-D。针对该domain序列，PCE4向序列中每个domain对应的子PCE分别发送PCReq消息，请求计算各domain内的路径片段。比如PCE4向PCE1发送PCReq消息以请求计算源节点S至目的节点A1的路径片段，消息中的主要信息如下：
<RP object>：PST设置为1，表明使用分段路由技术建立路径；CF标志必须设置为0，表示不对路径做压缩；
<END-POINTS object>：源节点为S，目的节点为A1；
PCE4亦向PCE2发送PCReq消息以请求计算源节点A2至目的节点A3的路径片段，以及向PCE3发送PCReq消息以请求计算源节点A4至目的节点D的路径片段。不再赘述。
步骤730，各子PCE收到PCE4发来的路径计算请求后，计算出相应的路径片段并发送PCRep消息回复给PCE4。本实施例中，PCE1将计算出路径片段S-P1-P2-A1，PCE2将计算出路径片段A2-P3-P4-A3，PCE3将计算出路径片段A4-P5-P6-D。一般的，各子PCE回复给PCE4的PCERep消息中包含的ERO object中将给出路径片段信息，可以是IP address list、SID list、IP address与SID混合list，甚至出于安全考虑可以是一个path-key。 本实施例中，由于各AS1、AS2均支持SR，所以PCE1与PCE2回复给PCE4的路径片段信息可以是SID list或者path-key；由于AS3仅边界节点支持SR，所以PCE3回复给PCE4的路径片段信息可以是IP address list或者path-key。
步骤740，针对domain序列S-(AS1)-A1-A2-(AS2)-A3-A4-(AS3)-D，PCE4从所有子PCE收到其中所有domain的路径片段后，将得到完整的端到端的TE路径。本实施例中，由于不再存在其它domain序列，所以上述完整的TE路径将作为最优路径。此时，PCE4不急于将该最优的完整TE路径回复给PCE1，而是检查发现之前从PCE1收到的相应路径计算请求中CF标志为3，则为各路径片段主动创建TE tunnel(不区分RSVP-TE tunnel还是SR-TE tunnel)并向各子PCE发送PCInitiate消息。比如PCE4在内部为AS1对应的路径片段S-P1-P2-A1额外创建相应的TE tunnel，其包含的主路径可取名为path-name-SD-100-SA1(注：这种命名方式是在母路径名称path-name-SD-100的尾部加上子路径首尾关键信息S、A1，可保证全局唯一)，相应的，PCE4发给PCE1的PCInitiate消息中，主要信息如下：
<SRP object>：PST设置为2，表示可使用RSVP-TE信令或者分段路由技术建立路径；
<LSP object>：path-name设置为path-name-SD-100-SA1；
<END-POINTS object>：源节点为S，目的节点为A1；
<ERO object>：S-P1-P2-A1，具体可以为SID list或path-key，也即把之前从PCE1收到的路径片段信息原封不动的填入。
PCE4亦在内部为AS2对应的路径片段A2-P3-P4-A3额外创建相应的TE tunnel，其包含的主路径可取名为path-name-SD-100-A2A3，并相应的向PCE2发送PCInitiate消息；PCE4亦在内部为AS3对应的路径片段A4-P5-P6-D额外创建相应的TE tunnel，其包含的主路径可取名为 path-name-SD-100-A4D，并相应的向PCE3发送PCInitiate消息。不再赘述。
步骤750，PCE1与PCE2收到PCE4的PCInitiate消息后，根据自身能力将在内部主动创建相应的SR-TE tunnel，并继续向该tunnel的头节点PCC发送PCInitiate消息。PCE3收到PCE4的PCInitiate消息后，根据自身能力将在内部主动创建相应的RSVP-TE tunnel，并继续向该tunnel的头节点PCC发送PCInitiate消息。注意子PCE1和子PCE2继续向tunnel头节点PCC下发的PCInitiate消息中，ERO object中包含的是明确的SID list，不能是path-key。子PCE3继续向tunnel头节点PCC下发的PCInitiate消息中，ERO object中包含的是明确的IP address list，不能是path-key。AS1和AS2内的tunnel头节点将生成相应的SR-TE tunnel，转发信息使用相应的SID list生成。AS3内的tunnel头节点将生成相应的RSVP-TE tunnel，并在网络内通过RSVP-TE信令建立路径，协商标签。。
本具体实施例中，各子PCE在创建好相应SR-TE tunnel或RSVP-TE tunnel后，还将主动为该TE tunnel分配Binding SID，比如，PCE1上为其上述创建的SR-TE tunnel分配Binding SID＝1000，PCE2上为其上述创建的SR-TE tunnel分配Binding SID＝2000，PCE3上为其上述创建的RSVP-TE tunnel分配Binding SID＝3000。各子PCE可将Binding SID随上述PCInitiate消息或者后续的PCUpd消息下发到tunnel头节点PCC，也可以随PCRpt消息上报给PCE4。各tunnel头节点收到Binding SID后，将会建立以Binding SID为键值的标签表项，用于指导报文向该tunnel转发，标签操作为将入标签Binding SID交换成相应SR-TE tunnel包含的出标签栈，或者交换成相应RSVP-TE tunnel包含的出标签。
需要说明的是，各子PCE还为其所负责domain至其它domain的domain间链路分配Peer-Adj SID，并通过BGP-LS上报给PCE4。
步骤760，PCE4收到所有子PCE的Binding SID上报后，就可以将原 始的完整TE路径采用压缩后的SID list表示并通过PCRep消息回复给PCE1，本实施例中压缩后的SID list可以为：{1000,Peer-Adj-SID-A1A2,2000,Peer-Adj-SID-A3A4,3000}。
步骤770，PCE1收到PCE4的PCRep消息后，继续向S节点PCC发送PCInitiate消息触发S节点上实例化相应的SR-TE tunnel，包含上述压缩后的SID list。
S节点上将创建相应的SR-TE tunnel，在为该SR-TE tunnel生成转发表项时，要将上述SID list中第一个SID即1000查找标签表项换成相应的SR-TE tunnel的转发信息(一般是一个标签栈)，其它SID不变。
步骤780，S节点上，向上述SR-TE tunnel发送的报文，将会被压上相应的标签栈：{SR-TE tunnel-SA1 SID list,Peer-Adj-SID-A1A2,2000,Peer-Adj-SID-A3A4,3000}，即顶层标签为前述AS1内路径片段额外创建的SR-TE tunnel对应的出标签栈，然后下层标签是domain间链路A1-A2对应的Peer-Adj SID，再下层标签是AS2内路径片段额外创建的SR-TE tunnel对应的Binding SID，再下层标签是domain间链路A3-A4对应的Peer-Adj SID，再下层标签是AS3内路径片段额外创建的RSVP-TE tunnel对应的Binding SID。报文将会沿期望的跨domain的TE路径转发。
实施例五
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例所述 的方法。
在本实施例中还提供了一种跨域的路径的标识信息的确定装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图7是根据本申请实施例的第一种跨域的路径的标识信息的确定装置的结构框图，如图7所示，该装置包括第一接收模块72，指示模块74和第二接收模块76，下面对该装置进行说明：
第一接收模块72，配置为接收来自第一子路径计算单元PCE的路径计算请求，其中，该路径计算请求用于请求获取源节点至目的节点的路径，该源节点和目的节点位于不同的domain中，上述路径包括一个或多个路径片段，上述路径计算请求中携带有用于标识对路径片段进行压缩的压缩标识以及路径建立类型PST；指示模块74，连接至上述第一接收模块72，配置为在获取上述源节点至目的节点的路径的标识信息之后，根据上述压缩标识以及PST指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩；第二接收模块76，连接至上述指示模块74，配置为接收各路径片段对应的子PCE返回的压缩后的路径片段的标识信息，并根据上述路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的路径的标识信息。
在一个可选的实施例中，上述指示模块74包括：发送单元，配置为根据压缩标识向各路径片段对应的子PCE发送创建消息，其中，该创建消息用于请求各路径片段对应的子PCE创建隧道tunnel，并为创建的tunnel分配Binding SID，其中，该创建消息中携带有所述路径片段的路径信息。
在一个可选的实施例中，上述创建消息用于请求各路径片段对应的子 PCE创建隧道tunnel包括以下之一：上述创建消息用于请求各路径片段对应的子PCE创建基于流量工程扩展的资源预留协议建立路径的RSVP-TE tunnel；上述创建消息用于请求各路径片段对应的子PCE创建基于分段路由技术建立路径的SR-TE tunnel；上述创建消息用于请求各路径片段对应的子PCE创建RSVP-TE tunnel或者SR-TE tunnel。
在一个可选的实施例中，上述第二接收模块76配置为：接收各路径片段对应的子PCE返回的为创建的tunnel分配的Binding SID；将接收的各Binding SID组成压缩后的路径的标识信息。
在一个可选的实施例中，上述路径信息包括以下内容：路径的路径名，路径片段的片段信息，待创建tunnel的起始节点信息和目的节点信息，上述PST。
在一个可选的实施例中，上述装置还包括返回模块，配置为在根据上述路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的路径的标识信息之后，将压缩后的路径的标识信息返回给第一子PCE。也就是说，作为第一子PCE发送的路径计算请求的响应，将压缩后的路径的标识信息返回给第一子PCE，第一子PCE在获取了压缩后的路径的标识信息之后，可以继续执行后续的操作，例如，可以将获取的压缩后的路径的标识信息发送给相应的PCC，PCC再依据路径的标识信息封装报文，并转发报文。
图8是根据本申请实施例的第二种跨域的路径的标识信息的确定装置的结构框图，如图8所示，该装置包括发送模块82，第三接收模块84，压缩模块86和第一返回模块88，下面对该装置进行说明：
发送模块82，配置为向父路径计算单元PCE发送路径计算请求，其中，该路径计算请求用于请求获取源节点至目的节点的路径，该源节点和目的节点位于不同的domain中，该路径包括一个或多个路径片段，该路径计算请求中携带有用于标识对路径片段进行压缩的压缩标识以及路径建立类型 PST；第三接收模块84，连接至上述发送模块82，配置为接收来自上述父PCE的创建消息，其中，该创建消息为父PCE根据压缩标识以及PST发送的；压缩模块86，连接至上述第三接收模块84，配置为根据上述创建消息对路径片段的标识信息进行压缩；第一返回模块88，连接至上述压缩模块86，配置为将压缩后的路径片段的标识信息返回给父PCE。
在一个可选的实施例中，上述压缩模块86包括：确定单元，配置为确定上述创建消息中携带的路径片段的路径信息；创建单元，配置为根据路径信息创建隧道tunnel，并为创建的tunnel分配Binding SID。
在一个可选的实施例中，上述创建消息用于请求创建以下tunnel至少之一：基于流量工程扩展的资源预留协议建立路径的RSVP-TE tunnel；基于分段路由技术建立路径的SR-TE tunnel。需要说明的是，在本实施例中，RSVP-TE tunnel以及SR-TE tunnel仅是两种优选的实施例，还可以根据实际情况以及技术发展创建其他类型的tunnel，在此，不做限定。
在一个可选的实施例中，上述创建单元配置为：根据上述路径信息实例化tunnel，并将上述创建消息转发给待创建tunnel的作为起始节点的路径计算客户PCC，其中，该创建消息用于指示PCC按照上述路径信息发起创建tunnel的流程。在本实施例中，是由PCC进行隧道的创建。
在一个可选的实施例中，在待创建的tunnel类型不同时，指示PCC执行的具体操作也是不同的，可选的，当上述创建消息用于请求创建RSVP-TE tunnel时，上述创建消息用于指示PCC发起RSVP-TE信令建立路径；可选的，当上述创建消息用于请求创建SR-TE tunnel时，上述创建消息用于指示PCC根据分段路由信息计算路径的转发信息。
在一个可选的实施例中，针对创建单元如何为创建的tunnel分配Binding SID分情况进行说明：在由控制器全局统一分配段标识SID的情况下，创建单元在根据上述路径信息实例化所述tunnel之后，为tunnel分配 Binding SID并上报给父PCE以及上述PCC；和/或，在由转发设备分配SID并将分配的SID上报给控制器的情况下，创建单元接收上述PCC在创建tunnel之后为tunnel分配的所述Binding SID，并上报给父PCE。
在一个可选的实施例中，上述装置还包括：第四接收模块，连接至上述第一返回模块88，配置为在将压缩后的路径片段的标识信息返回给父PCE之后，接收来自父PCE的压缩后的路径的标识信息；第二返回模块，连接至上述第四接收模块，配置为当路径计算请求是由预定路径计算客户PCC发起的情况下，将压缩后的路径的标识信息返回给预定PCC；第三返回模块，连接至上述第二返回模块，配置为当上述路径计算请求不是由预定路径计算客户PCC发起的情况下，将压缩后的路径的标识信息发送给tunnel的作为起始节点的PCC。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本申请的实施例还提供了一种存储介质，该存储介质包括存储的程序，其中，上述程序运行时执行上述任一项所述的方法。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本申请的实施例还提供了一种处理器，该处理器用于运行程序，其中，该程序运行时执行上述任一项方法中的步骤。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执 行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
工业实用性
采用本申请实施例，由于在获取了源节点至目的节点的路径的标识信息之后，对该路径的标识信息进行了压缩，从而有效的缩小了路径的标识信息的长度，从而解决了相关技术中存在的路径标识信息过长的问题。

Claims (19)

  1. 一种跨域domain的路径的标识信息的确定方法，包括：
    接收来自第一子路径计算单元PCE的路径计算请求，其中，所述路径计算请求用于请求获取源节点至目的节点的路径，所述源节点和所述目的节点位于不同的domain中，所述路径包括一个或多个路径片段，所述路径计算请求中携带有用于标识对所述路径片段进行压缩的压缩标识以及路径建立类型PST；
    在获取所述源节点至所述目的节点的路径的标识信息之后，根据所述压缩标识以及所述PST指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩；
    接收各路径片段对应的子PCE返回的压缩后的路径片段的标识信息，并根据所述路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的所述路径的标识信息。
  2. 根据权利要求1所述的方法，其中，根据所述压缩标识指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩包括：
    根据所述压缩标识向各路径片段对应的子PCE发送创建消息，其中，所述创建消息用于请求各路径片段对应的子PCE创建隧道tunnel，并为创建的tunnel分配绑定段标识Binding SID，其中，所述创建消息中携带有所述路径片段的路径信息。
  3. 根据权利要求2所述的方法，其中，所述创建消息用于请求各路径片段对应的子PCE创建隧道tunnel包括以下之一：
    所述创建消息用于请求各路径片段对应的子PCE创建基于流量工程扩展的资源预留协议建立路径的RSVP-TE tunnel；
    所述创建消息用于请求各路径片段对应的子PCE创建基于分段路由技术建立路径的SR-TE tunnel；
    所述创建消息用于请求各路径片段对应的子PCE创建RSVP-TE tunnel或者SR-TE tunnel。
  4. 根据权利要求2所述的方法，其中，接收各路径片段对应的子PCE返回的压缩后的路径片段的标识信息，并将各压缩后的路径片段的标识信息组成压缩后的所述路径的标识信息包括：
    接收各路径片段对应的子PCE返回的为创建的tunnel分配的Binding SID；
    将接收的各Binding SID组成压缩后的所述路径的标识信息。
  5. 根据权利要求2所述的方法，其中，所述路径信息包括以下内容：
    所述路径的路径名，所述路径片段的片段信息，待创建tunnel的起始节点信息和目的节点信息，所述PST。
  6. 根据权利要求1所述的方法，其中，在根据所述路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的所述路径的标识信息之后，所述方法包括：
    将所述压缩后的所述路径的标识信息返回给所述第一子PCE。
  7. 一种跨域domain的路径的标识信息的确定方法，包括：
    向父路径计算单元PCE发送路径计算请求，其中，所述路径计算请求用于请求获取源节点至目的节点的路径，所述源节点和所述目的节点位于不同的domain中，所述路径包括一个或多个路径片段，所述路径计算请求中携带有用于标识对所述路径片段进行压缩的压缩标识以及路径建立类型PST；
    接收来自所述父PCE的创建消息，其中，所述创建消息为所述父PCE根据所述压缩标识以及所述PST发送的；
    根据所述创建消息对路径片段的标识信息进行压缩；
    将压缩后的路径片段的标识信息返回给所述父PCE。
  8. 根据权利要求7所述的方法，其中，根据所述创建消息对所述路径片段的标识信息进行压缩包括：
    确定所述创建消息中携带的所述路径片段的路径信息；
    根据所述路径信息创建隧道tunnel，并为创建的tunnel分配Binding SID。
  9. 根据权利要求8所述的方法，其中，所述创建消息用于请求创建以下tunnel至少之一：
    基于流量工程扩展的资源预留协议建立路径的RSVP-TE tunnel；基于分段路由技术建立路径的SR-TE tunnel。
  10. 根据权利要求9所述的方法，其中，根据所述路径信息创建隧道tunnel包括：
    根据所述路径信息实例化所述tunnel，并将所述创建消息转发给待创建所述tunnel的作为起始节点的路径计算客户PCC，其中，所述创建消息用于指示所述PCC按照所述路径信息发起创建所述tunnel的流程。
  11. 根据权利要求10所述的方法，其中，包括以下之一：
    当所述创建消息用于请求创建所述RSVP-TE tunnel时，所述创建消息用于指示所述PCC发起RSVP-TE信令建立路径；
    当所述创建消息用于请求创建所述SR-TE tunnel时，所述创建消息用于指示所述PCC根据分段路由信息计算路径的转发信息。
  12. 根据权利要求10所述的方法，其中，为创建的tunnel分配所述Binding SID包括：
    在由控制器全局统一分配段标识SID的情况下，在根据所述路径信息实例化所述tunnel之后，为所述tunnel分配所述Binding SID并上报给父PCE以及所述PCC；和/或，
    在由转发设备分配SID并将分配的SID上报给控制器的情况下，接 收所述PCC在创建所述tunnel之后为所述tunnel分配的所述Binding SID，并上报给所述父PCE。
  13. 根据权利要求8所述的方法，其中，在将压缩后的路径片段的标识信息返回给所述父PCE之后，所述方法还包括：
    接收来自所述父PCE的压缩后的所述路径的标识信息；
    当所述路径计算请求是由预定路径计算客户PCC发起的情况下，将压缩后的所述路径的标识信息返回给所述预定PCC；
    当所述路径计算请求不是由预定路径计算客户PCC发起的情况下，将压缩后的所述路径的标识信息发送给所述tunnel的作为起始节点的PCC。
  14. 一种跨域domain的路径的标识信息的确定装置，包括：
    第一接收模块，配置为接收来自第一子路径计算单元PCE的路径计算请求，其中，所述路径计算请求用于请求获取源节点至目的节点的路径，所述源节点和所述目的节点位于不同的domain中，所述路径包括一个或多个路径片段，所述路径计算请求中携带有用于标识对所述路径片段进行压缩的压缩标识以及路径建立类型PST；
    指示模块，配置为在获取所述源节点至所述目的节点的路径的标识信息之后，根据所述压缩标识以及所述PST指示各路径片段对应的子PCE对各自对应的路径片段的标识信息进行压缩；
    第二接收模块，配置为接收各路径片段对应的子PCE返回的压缩后的路径片段的标识信息，并根据所述路径的标识信息将各压缩后的路径片段的标识信息组成压缩后的所述路径的标识信息。
  15. 根据权利要求14所述的装置，其中，所述指示模块包括：
    发送单元，配置为根据所述压缩标识向各路径片段对应的子PCE发送创建消息，其中，所述创建消息用于请求各路径片段对应的子PCE创 建隧道tunnel，并为创建的tunnel分配Binding SID，其中，所述创建消息中携带有所述路径片段的路径信息。
  16. 一种跨域domain的路径的标识信息的确定装置，包括：
    发送模块，配置为向父路径计算单元PCE发送路径计算请求，其中，所述路径计算请求用于请求获取源节点至目的节点的路径，所述源节点和所述目的节点位于不同的domain中，所述路径包括一个或多个路径片段，所述路径计算请求中携带有用于标识对所述路径片段进行压缩的压缩标识以及路径建立类型PST；
    第三接收模块，配置为接收来自所述父PCE的创建消息，其中，所述创建消息为所述父PCE根据所述压缩标识以及所述PST发送的；
    压缩模块，配置为根据所述创建消息对路径片段的标识信息进行压缩；
    第一返回模块，配置为将压缩后的路径片段的标识信息返回给所述父PCE。
  17. 根据权利要求16所述的装置，其中，所述压缩模块包括：
    确定单元，配置为确定所述创建消息中携带的所述路径片段的路径信息；
    创建单元，配置为根据所述路径信息创建隧道tunnel，并为创建的tunnel分配Binding SID。
  18. 根据权利要求17所述的装置，其中，所述装置还包括：
    第四接收模块，配置为在将压缩后的路径片段的标识信息返回给所述父PCE之后，接收来自所述父PCE的压缩后的所述路径的标识信息；
    第二返回模块，配置为当所述路径计算请求是由预定路径计算客户PCC发起的情况下，将压缩后的所述路径的标识信息返回给所述预定PCC；
    第三返回模块，配置为当所述路径计算请求不是由预定路径计算客户PCC发起的情况下，将压缩后的所述路径的标识信息发送给所述tunnel的作为起始节点的PCC。
  19. 一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求1至13中任一项所述的方法。
PCT/CN2018/088880 2017-07-03 2018-05-29 跨域的路径的标识信息的确定方法、装置及存储介质 WO2019007166A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
ES18827949T ES2942465T3 (es) 2017-07-03 2018-05-29 Determinación de información de identificación sobre trayectoria entre dominios
US16/623,613 US11362940B2 (en) 2017-07-03 2018-05-29 Method and apparatus for determining identification information about cross-domain path, and storage medium
EP18827949.1A EP3651423B1 (en) 2017-07-03 2018-05-29 Determining identification information about cross-domain path

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710532649.1A CN109218189B (zh) 2017-07-03 2017-07-03 跨域的路径的标识信息的确定方法、装置及存储介质
CN201710532649.1 2017-07-03

Publications (1)

Publication Number Publication Date
WO2019007166A1 true WO2019007166A1 (zh) 2019-01-10

Family

ID=64949686

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088880 WO2019007166A1 (zh) 2017-07-03 2018-05-29 跨域的路径的标识信息的确定方法、装置及存储介质

Country Status (5)

Country Link
US (1) US11362940B2 (zh)
EP (1) EP3651423B1 (zh)
CN (1) CN109218189B (zh)
ES (1) ES2942465T3 (zh)
WO (1) WO2019007166A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020168549A1 (en) * 2019-02-22 2020-08-27 Telefonaktiebolaget Lm Ericsson (Publ) Method and router for label switched path traceroute
US20230126801A1 (en) * 2020-03-10 2023-04-27 Zte Corporation Packet encapsulation method, packet forwarding method, announcement method, electronic device, and storage medium
EP4131870A4 (en) * 2020-03-30 2024-04-24 ZTE Corporation SERVICE PROCESSING METHOD AND APPARATUS, AND DEVICE AND STORAGE MEDIUM

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110417651B (zh) 2018-04-28 2021-07-16 华为技术有限公司 一种隧道建立方法、装置及系统
CN110708243B (zh) * 2018-07-09 2021-08-13 华为技术有限公司 段路由中获取数据包的转发路径的信息的方法和装置
JP7176428B2 (ja) * 2019-02-06 2022-11-22 日本電信電話株式会社 制御装置、制御方法及びプログラム
US11012350B2 (en) * 2019-07-16 2021-05-18 Cisco Technology, Inc. Network interworking with no cross-domain state
CN112583745A (zh) * 2019-09-27 2021-03-30 华为技术有限公司 一种在sr网络中转发报文的方法、设备和系统
CN113141338B (zh) 2020-01-20 2022-07-22 华为技术有限公司 一种消息生成方法、处理方法及装置
CN113259238B (zh) * 2020-02-07 2022-10-21 中国移动通信有限公司研究院 分段标识的处理方法及设备
CN113382452B (zh) * 2020-03-09 2023-04-07 中国移动通信有限公司研究院 路径建立方法、数据传输方法、装置、网络节点及存储介质
CN113438160B (zh) * 2020-03-23 2024-05-31 中兴通讯股份有限公司 路由方法、路由装置及计算机可读存储介质
CN112511429A (zh) * 2020-03-25 2021-03-16 中兴通讯股份有限公司 信息发送和处理的方法、节点、控制器、计算机可读介质
JP2023521022A (ja) * 2020-04-02 2023-05-23 華為技術有限公司 Ｓｒｖ６の信頼領域境界フィルタリングの方法および装置
CN113497760B (zh) * 2020-04-07 2024-05-07 中兴通讯股份有限公司 分段路由头压缩方法、业务处理方法及装置
CN113542118B (zh) * 2020-04-13 2024-01-23 中兴通讯股份有限公司 分段路由头压缩方法、业务处理方法及装置
CN115398869A (zh) * 2020-04-15 2022-11-25 华为技术有限公司 最小化用于分段路由的分段标识符中的差异
CN113556284B (zh) * 2020-04-24 2023-01-10 中国移动通信有限公司研究院 数据包处理的方法及设备
CN111628995B (zh) * 2020-05-26 2023-06-16 新华三信息安全技术有限公司 基于SRv6的SID压缩方法、装置、设备及存储介质
CN116582476A (zh) * 2020-05-28 2023-08-11 华为技术有限公司 绑定段标识的处理方法及设备
CN113824638A (zh) * 2020-06-18 2021-12-21 华为技术有限公司 一种转发报文的方法、设备和系统
CN112118179B (zh) * 2020-08-10 2022-01-14 中盈优创资讯科技有限公司 创建端到端分段路由sr路径的方法及装置
CN112532520B (zh) * 2020-10-28 2022-04-05 中盈优创资讯科技有限公司 基于pce的te-lsp的实现方法及装置
CN112422427B (zh) * 2020-10-28 2022-04-19 中盈优创资讯科技有限公司 基于分段路由的流量工程实现方法、装置及控制器
US11411876B2 (en) 2020-11-30 2022-08-09 Cisco Technology, Inc. Optimizing segment routing paths using segment identifiers
CN114205188B (zh) * 2021-12-08 2023-08-29 中盈优创资讯科技有限公司 一种基于srte时延优化的隧道调度方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101908998A (zh) * 2009-06-03 2010-12-08 华为技术有限公司 路径计算方法、路径计算单元及路径计算系统
WO2011057154A1 (en) * 2009-11-06 2011-05-12 Qualcomm Incorporated Header compression for relay nodes in a wireless network
US20160105358A1 (en) * 2014-10-13 2016-04-14 Dell Products L.P. Compression of routing information exchanges

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101155054A (zh) * 2006-09-28 2008-04-02 华为技术有限公司 自治系统域间pce路径自动探测和计算的方法和装置
US8064447B2 (en) * 2008-03-27 2011-11-22 Futurewei Technologies, Inc. Computing point-to-multipoint paths
CN102308519B (zh) * 2009-02-19 2015-07-08 华为技术有限公司 适用于点至多点域间多协议标签交换流量工程路径计算的系统和方法
CN101931583B (zh) * 2009-06-18 2012-09-26 中兴通讯股份有限公司 域路由信息生成方法、装置以及路径计算方法、装置
EP3337107B1 (en) * 2011-02-21 2021-06-16 Huawei Technologies Co., Ltd. System and method for finding point-to-multipoint label switched path crossing multiple domains
US8776029B2 (en) * 2011-03-23 2014-07-08 Zerodee, Inc. System and method of software execution path identification
CN102238443B (zh) * 2011-06-01 2013-11-20 电子科技大学 一种满足波长连续性约束条件的跨域路径建路方法
WO2013086653A1 (zh) * 2011-12-13 2013-06-20 华为技术有限公司 域间链路信息的发布方法、设备和系统
US10038621B2 (en) * 2012-04-05 2018-07-31 Telefonaktiebolaget Lm Ericsson (Publ) Apparatus and method for computing end-to-end paths through a network comprising a plurality of network domains
CN102970222B (zh) * 2012-11-20 2015-08-12 中兴通讯股份有限公司 一种跨域路由的管理方法、系统及装置
US9537769B2 (en) * 2013-03-15 2017-01-03 Cisco Technology, Inc. Opportunistic compression of routing segment identifier stacks
US20160105958A1 (en) 2013-04-26 2016-04-14 Denso Corporation Multi-layer substrate, electronic device using multi-layer substrate, manufacturing method for multilayer substrate, substrate, and electronic device using substrate
US9450864B2 (en) * 2013-10-11 2016-09-20 Futurewei Technologies, Inc. Using PCE as SDN controller
CN105871721B (zh) * 2015-01-19 2020-05-05 中兴通讯股份有限公司 一种段路由处理方法、处理装置及发送装置
US10050806B2 (en) * 2015-12-07 2018-08-14 Futurewei Technologies, Inc. End-to-end (E2E) tunnel based on shortest point-to-point (P2P) path computation
CN109565468B (zh) * 2016-06-06 2022-07-01 瑞典爱立信有限公司 确定通信网络中的路径

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101908998A (zh) * 2009-06-03 2010-12-08 华为技术有限公司 路径计算方法、路径计算单元及路径计算系统
WO2011057154A1 (en) * 2009-11-06 2011-05-12 Qualcomm Incorporated Header compression for relay nodes in a wireless network
US20160105358A1 (en) * 2014-10-13 2016-04-14 Dell Products L.P. Compression of routing information exchanges

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3651423A4

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020168549A1 (en) * 2019-02-22 2020-08-27 Telefonaktiebolaget Lm Ericsson (Publ) Method and router for label switched path traceroute
US11968108B2 (en) 2019-02-22 2024-04-23 Telefonaktiebolagget LM Ericsson (Publ) Method and router for label switched path traceroute
US20230126801A1 (en) * 2020-03-10 2023-04-27 Zte Corporation Packet encapsulation method, packet forwarding method, announcement method, electronic device, and storage medium
US12015551B2 (en) * 2020-03-10 2024-06-18 Zte Corporation Packet encapsulation method, packet forwarding method, announcement method, electronic device, and storage medium
EP4131870A4 (en) * 2020-03-30 2024-04-24 ZTE Corporation SERVICE PROCESSING METHOD AND APPARATUS, AND DEVICE AND STORAGE MEDIUM

Also Published As

Publication number Publication date
ES2942465T3 (es) 2023-06-01
EP3651423B1 (en) 2023-03-15
EP3651423A4 (en) 2021-03-17
CN109218189B (zh) 2022-04-29
EP3651423A1 (en) 2020-05-13
US20200213223A1 (en) 2020-07-02
CN109218189A (zh) 2019-01-15
US11362940B2 (en) 2022-06-14

Similar Documents

Publication Publication Date Title
WO2019007166A1 (zh) 跨域的路径的标识信息的确定方法、装置及存储介质
WO2020156105A1 (zh) 数据转发方法及相关装置
US8718062B2 (en) Method, device and system for establishing pseudo wire
US8442050B2 (en) Apparatus and method of controlling LSP of RSVP-TE protocol using label with availability of end-to-end range
WO2019141118A1 (zh) 创建双向分段路由隧道的方法、设备及存储介质
US11743204B2 (en) Tunnel establishment method, apparatus, and system
WO2020134946A1 (zh) 流量工程路径建立方法及装置和系统
CN107306222B (zh) 标签交换路径上的流量工程隧道建立的方法和设备
WO2015192501A1 (zh) 地址信息的发布方法及装置
CN110730478B (zh) 切片关联方法、装置、端到端切片编排器及存储介质
WO2019134639A1 (zh) 实现无缝最优跨域路径的方法、装置、设备及存储介质
WO2017124709A1 (zh) 流量工程隧道建立方法和装置
JP2015507404A (ja) 少なくとも２つのドメインを横切ってデータを搬送する方法及び装置
CN114363235B (zh) 在启用分段路由的网络中计算多路径的分段标识符列表
CN101494552B (zh) 一种建立业务连接的方法、系统和装置
US9553790B2 (en) Terminal apparatus and method of controlling terminal apparatus
WO2008154848A1 (fr) Procédé d&#39;acquisition des informations de capacité d&#39;un nœud de réseau entre des domaines, nœud de réseau et système de communication
US20210352012A1 (en) Method for creating inter-domain bidirectional tunnel, communication method and device, and storage medium
CN110784403B (zh) 路径标识传输方法、装置和计算机可读存储介质
CN117014357A (zh) 发送路由的方法、装置及存储介质
CN118118436A (zh) 一种通信方法及装置
CN115396360A (zh) 一种路径计算方法、装置、存储介质及电子装置
CN115695284A (zh) 算力网络中的回程流量引流方法、装置、设备及存储介质
CN115865823A (zh) 流量传输方法、装置、计算机设备及存储介质
KR20040045964A (ko) 조건 기반 레이블 분배 프로토콜（（ｃｒ）ｌｄｐ）기반ｍｐｌｓ 망과 자원 예약 프로토콜（ｒｓｖｐ）기반전광망의 자동 연결 설정 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18827949

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018827949

Country of ref document: EP

Effective date: 20200203