WO2020052641A1 - 报文的发送方法、绑定关系的通告方法、装置及存储介质 - Google Patents

报文的发送方法、绑定关系的通告方法、装置及存储介质 Download PDF

Info

Publication number
WO2020052641A1
WO2020052641A1 PCT/CN2019/105626 CN2019105626W WO2020052641A1 WO 2020052641 A1 WO2020052641 A1 WO 2020052641A1 CN 2019105626 W CN2019105626 W CN 2019105626W WO 2020052641 A1 WO2020052641 A1 WO 2020052641A1
Authority
WO
WIPO (PCT)
Prior art keywords
label
container
fec
node
message
Prior art date
Application number
PCT/CN2019/105626
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 US17/274,595 priority Critical patent/US11671352B2/en
Priority to EP19861174.1A priority patent/EP3852319B1/en
Publication of WO2020052641A1 publication Critical patent/WO2020052641A1/zh

Links

Images

Classifications

    • 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
    • H04L45/245—Link aggregation, e.g. trunking
    • 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/16—Multipoint 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/74—Address processing for 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/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering

Definitions

  • the present disclosure relates to the field of communications.
  • the FEC aggregation strategy can be a coarse-grained aggregation strategy. For example, multiple different FECs are combined into a union. At this time, the union itself is an FEC. Each member of the union is called a component FEC (or detailed FEC). ) To assign a single MPLS label to the complex.
  • the FEC aggregation strategy can also be a fine-grained aggregation strategy. For example, each detailed FEC is assigned an MPLS label.
  • the FEC aggregation strategy can also be an aggregation strategy between coarse-grained and fine-grained.
  • the FEC aggregation strategy can simply follow the route aggregation strategy.
  • the aggregated route itself is an FEC and assigned an MPLS label.
  • the FEC aggregation strategy can be BGP (Border Gateway Gateway Protocol) or MPLS IP VPN (Internet Protocol Virtual Private Networks, IP Virtual Private Networks, see RFC4364) per VPN label allocation mode.
  • PE Provide edge
  • the device assigns the same MPLS label to all local CE (Customer Edge) device-side private network routes in the same VPN instance. From these examples, we can see that the FEC aggregation strategy is essentially a label distribution strategy.
  • the corresponding label forwarding behavior is generally to continue to forward based on the IP load after POP (pop-up). There are no new requirements for the existing MPLS forwarding mechanism. After FEC aggregation occurs, end-to-end MPLS LSPs (Label Switched Paths) are generally no longer established for detailed FECs, but in many scenarios it is still necessary to configure complex policies to establish end-to-end MPLS LSPs for the specified detailed FECs.
  • label Switched Paths Label Switched Paths
  • IGP Interior, Gateway, and Interior Gateway Protocol
  • ISIS Intermediate System to Intermediate System Intermediate System to Intermediate System Protocol
  • OSPF Open Shortest Path First First Open Shortest Path First Protocol
  • Inter-domain leaks are very common.
  • the longest matching rule for IP forwarding naturally supports route aggregation, but the existing MPLS LSP forwarding mechanism is based on exact matching rules, so a certain amount of end-to-end detailed FEC is always required. notice.
  • the industry has proposed some solutions.
  • RFC5283 and RFC7032 are extensions of the LDP (Label Distribution Protocol Protocol, see RFC5036) protocol.
  • RFC5283 is mainly to modify the original RFC5036 restriction of establishing an LSP when the detailed FEC must have an exact matching detailed route to notify the neighbor that the detailed FEC can match a route for the longest and the next hop of the route is a detailed FEC.
  • LSPs are established at all times.
  • RFC7032 mainly solves the problem of how the detailed FEC is born and perishes by making services dynamically trigger the establishment and destruction of LSPs that invent the fine FEC, and provides a means for rapid convergence of LDPDOD (Downstream on Demand).
  • LDPDOD Downstream on Demand
  • An aspect of the present disclosure provides a method for sending a message.
  • the method for sending a message includes: receiving a first message on a first node on which route aggregation has been performed; When the first incoming label mapping (ILM) entry set on the first node matches, the label of the first packet is exchanged for an outgoing label corresponding to a detailed forwarding equivalence class (FEC) to obtain a second A message; and forwarding the second message to a downstream node according to a label forwarding path (LSP) corresponding to the detailed FEC.
  • ILM label mapping
  • LSP label forwarding path
  • the method for announcing a binding relationship includes: receiving a binding relationship announced by a first node on a second node, wherein the first node For a node performing route aggregation, the binding relationship is a binding relationship between a container label and a first container FEC, and the container label is pre-assigned in the first node for the first container FEC,
  • the first container FEC is an FEC carrying a container identifier obtained after configuring the route aggregated on the first node, and the container identifier is used to identify the first container FEC as a container FEC type.
  • the message sending device includes: a first receiving module configured to receive a first message on a first node where route aggregation is performed; an exchange module , If the first packet matches a first incoming label mapping (ILM) entry set on the first node in advance, the label of the first packet is exchanged for detailed forwarding, etc.
  • the second message is obtained through the label corresponding to the price class (FEC); the forwarding module is configured to forward the second message to a downstream node according to a label forwarding path (LSP) corresponding to the detailed FEC.
  • LSP label forwarding path
  • the binding relationship notification device includes a second receiving module configured to receive a binding relationship announced by a first node on a second node.
  • the first node is a node where route aggregation is performed
  • the binding relationship is a binding relationship between a container label and a first container FEC
  • the container label is the The first container FEC is allocated.
  • the first container FEC is an FEC carrying a container identifier obtained after configuring the route aggregated on the first node, and the container identifier is used to identify the first container FEC as a container. FEC type.
  • Another aspect of the present disclosure also provides a storage medium, where the computer program is stored, and when the computer program is executed by a processor, the processor is caused to execute the foregoing message sending method or binding. Method of notification of the relationship.
  • Another aspect of the present disclosure also provides an electronic device including a memory and a processor.
  • the memory stores a computer program executable by the processor.
  • the processor is executed by the processor, The processor is caused to execute the foregoing message sending method or the binding relationship notification method.
  • FIG. 1 is a flowchart of a message sending method according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of an extended MPLS label protocol and an SR routing protocol according to an embodiment of the present disclosure
  • FIG. 6 is a flowchart of a binding relationship notification method according to an embodiment of the present disclosure.
  • FIG. 7 is a network topology diagram according to an embodiment of the present disclosure.
  • FIG. 8 is a network topology diagram according to another embodiment of the present disclosure.
  • FIG. 9 is a structural block diagram of a message transmitting apparatus according to an embodiment of the present disclosure.
  • FIG. 10 is a structural block diagram of a binding relationship notification device according to an embodiment of the present disclosure.
  • the embodiment of the present disclosure proposes a concept of a Forwarding Equivalence Class (FEC) container to solve the problem of establishing an end-to-end LSP for a service after route aggregation.
  • FEC Forwarding Equivalence Class
  • the term "container FEC” is for distinguishing from the term “FEC aggregation (Aggregation)”. There is a difference between the two in terms of protocol notification and forwarding mechanism.
  • the received message corresponds to the first message
  • the ILM entry created corresponds to the first ILM entry
  • the configured container FEC corresponds to the first container.
  • the queried FTN entry corresponds to the first FTN entry.
  • FIG. 1 is a flowchart of a message transmission method according to an embodiment of the present disclosure.
  • step S102 a first packet is received on a first node that has undergone route aggregation.
  • step S104 when the first message matches a first incoming label mapping (ILM) entry created in advance on the first node, the label of the first message is exchanged with the details
  • the FEC corresponds to the label and obtains the second packet.
  • step S106 the second message is forwarded to a downstream node according to a label forwarding path (LSP) corresponding to the detailed FEC.
  • LSP label forwarding path
  • the aggregated route may be recorded as aggregation-prefix.
  • node A the first node where route aggregation occurs
  • aggregation-prefix-A an aggregation-prefix-A may be configured as a container FEC.
  • Container FEC is a common prefix FEC, except that it is marked with a container, and is not a new type of FEC.
  • the method before step S102, further includes: configuring the aggregated route as a first container FEC on the first node, wherein the first container FEC carries a container identifier, and the The container flag is used to identify that the first container FEC is a container FEC type; and the first ILM entry is created for the first container FEC, wherein the first ILM entry carries the container flag.
  • the route aggregated on the first node can be configured as a container FEC and assigned an MPLS label (the MPLS label can be referred to as a container label) to create a corresponding ILM (incoming label mapping) entry. The entry is marked with a container.
  • the packet that hits this ILM entry will query the outgoing label corresponding to the detailed FEC and perform the label exchange operation based on the encapsulation information after the label in the packet label stack, and the packet will continue to be forwarded along the LSP corresponding to the detailed FEC.
  • step S104 may include: when the first message matches the first ILM entry, querying and detailing the FEC according to the encapsulation information after the container label in the message label stack.
  • the corresponding outgoing label exchanges the container label in the packet label stack with the outgoing label corresponding to the detailed FEC queried out, wherein the packet label stack is upstream of the first node A label stack generated on the node, the container label is an MPLS label having a binding relationship with the first container FEC, and the encapsulation information is information about the detailed FEC encapsulated in the packet label stack after the container label .
  • the message received by node A (corresponding to the above-mentioned first node) is generated on a node upstream of node A.
  • the upstream node may be node S in the route shown below.
  • the detailed host routes (for example, D1, D2, D3, etc.) are aggregated into one aggregated route Dx and flooded toward the node S side.
  • the aggregated route Dx is configured as a container FEC to generate a container FEC Dx
  • a container label is assigned to the container FEC Dx and then sequentially announced to the node S side through the node P2 and the node P1
  • the node P2 is a container after receiving the container FEC Dx FEC Dx redistributes the container label and informs P1 of the container FEC Dx of reassigning the container label.
  • P1 After P1 receives the container FEC Dx of reassigning the container label, P1 redistributes the container label again for the container FEC DD of reassigning the container label. The node F is notified to the node S of the container FEC re-assignment of the container label, and finally the node F is generated on the node S for the container FEC of the re-assigned container label. ) FTN entry. That is, node S has an LSP with an FEC of Dx.
  • the node S will find the FTN entry corresponding to the above-mentioned container FEC re-assignment of the container FEC Dx according to the destination IP D1 . Because the FTN entry has a container flag, node S encapsulates the outgoing label given in the FTN entry for the message, and then continues to encapsulate the detailed FEC D1 information after the label is generated, thereby generating a report that encapsulates the container label and the detailed FEC D1. Text label stack.
  • the method before querying the outgoing label corresponding to the detailed FEC according to the encapsulation information after the container label in the message label stack, the method further includes: configuring the binding relationship.
  • the method further includes: notifying the binding relationship to other nodes except the first node.
  • querying the outgoing label corresponding to the detailed FEC according to the packaging information after the container label in the message label stack includes: querying the packaging information after the container label in the message label stack and A first FTN entry corresponding to the detailed FEC; and when the first FTN entry is queried, it is determined that the outgoing label in the first FTN entry is an outgoing label corresponding to the detailed FEC.
  • the method further includes at least one of the following: If the first FTN entry is not queried, and if it is determined that the bottom-of-stack flag of the container label in the message label stack is valid, the container label in the message label stack is removed And subsequent encapsulation information, query the routing table according to the Internet Protocol (IP) payload, and forward the first message according to the routing table; if the first FTN entry is not queried, and the report is determined When the stack bottom flag of the container label in the text label stack is invalid, the first message is discarded.
  • IP Internet Protocol
  • the method before querying the first FTN entry corresponding to the detailed FEC according to the encapsulation information after the container label in the message label stack, the method further includes: The first FTN entry corresponding to the first FEC generated by a previous node of the first node, wherein the previous node of the first node includes a node that originally generated the first FEC.
  • the first node may serve as an egress node of the container FEC.
  • the label operation of the ILM entry is POP.
  • the message corresponding to the ILM entry will query the FTN entry corresponding to the detailed FEC according to the detailed FEC information immediately following the container label in the message label stack (herein collectively referred to as query to FTN, And the queried FTN entry is recorded as the outgoing label of the FTN-detailed entry), and the container label in the packet label stack performs a label exchange operation with the outgoing label.
  • the detailed FEC information is expressed in multiple ways.
  • the detailed FEC may be an IP address, a prefix-sid, or an MPLS label.
  • the FTN entry actually queried may be, for example, a routing entry. , SID entry, label entry. It should be noted that when RFC8029 is applied, the FEC change actually occurs at the same time when the label exchange operation is performed on the message.
  • the packet continues to be forwarded along the LSP corresponding to the detailed FEC. It should be noted that if there is no container flag in the FTN-detailed entry that is queried, the detailed FEC information immediately following the original container label in the packet label stack is removed during forwarding.
  • the packet is forwarded along the IP based on whether the bottom-of-stack flag of the container label in the packet label stack is valid. For example, if the bottom-of-stack flag is valid, the message is removed. The container label in the text label stack and the detailed FEC information that follows it are forwarded according to the IP payload to check the routing table. If the flag at the bottom of the stack is invalid, the packet is discarded.
  • the first FTN entry when the type of the first FEC generated by a previous node of the first node is not a container FEC, the first FTN entry does not include the container flag.
  • the first FTN entry when the type of the first FEC generated by a previous node of the first node is a container FEC, the first FTN entry includes the container flag.
  • the method further includes at least one of the following: when the container flag is not included in the first FTN entry, exchanging a container label in the packet label stack for the first FTN The label in the entry, and the information about the detailed FEC encapsulated after removing the container tag in the packet stack of the message; when the container flag is included in the first FTN entry, the message is sent
  • the container label exchange in the label stack is the outgoing label in the first FTN entry, and the information about the detailed FEC encapsulated after the container label in the packet label stack is retained.
  • the encapsulation form of the encapsulation information includes at least one of the following: an encapsulation form of directly encapsulating the IP address information of the detailed FEC; an encapsulation form of encapsulating at least one of the following information using an encapsulation header: the detail The FEC's IP address information, MPLS label information, and segment identification SID information, where the IP address information includes one of the following: complete IP address information, and host segment information including only the IP address.
  • the encapsulation information immediately after the label in the packet label stack may have various forms, for example, type 1 (Style-1): directly encapsulate IP address information related to detailed FEC, type 2 ( Style-2): An encapsulation header (contained as container_header).
  • the encapsulation header continues to encapsulate IP address information, MPLS label information, or SID information related to detailed FEC.
  • IP address information can be divided into encapsulated complete IP Address information and host segment information that encapsulates only IP addresses.
  • the detailed FEC information may also include other types, such as using an MPLS reserved label, followed by the detailed FEC information.
  • the encapsulation form of the above detailed FEC information must be specified as a configuration option when the container FEC is configured on node A. After the encapsulation form of the detailed FEC is configured, the configuration is usually not changed to avoid packet parsing errors.
  • FIG. 2 is a detailed FEC packaging format according to an embodiment of the present disclosure.
  • Figure 2 shows the type 1 encapsulation form of detailed FEC.
  • the IP address information related to the encapsulated detailed FEC can be Is an IPv4 address (shown in (a) in Figure 2) or an IPv6 address (shown in (b) in Figure 2).
  • FIG. 3 is a detailed FEC packaging format according to another embodiment of the present disclosure.
  • FIG. 3 shows a detailed FEC type 2 package form.
  • the type 2 package header includes a first area, a Ver area, a Reserved area, a Length area, and a Type area.
  • the first area occupies 4 bits, and the value is all ones.
  • the Ver area occupies 4 bits, indicating the version number.
  • the current value is all 0s.
  • the Reserved area occupies 8 bits, indicating unused reserved fields.
  • the current value is all 0s.
  • the Length area occupies 8 bits, indicating how many bytes (for example, 4 bytes) the encapsulated detail FEC information occupies.
  • the length does not include the length of the package header itself. For example, the length of the detail FEC information can range from It is 1 to 4 bytes.
  • the host segment information of the IP address is mainly used for encapsulation of IPv6 address information (also can be used for IPv4) to save the encapsulation size. When node A receives the packet, it needs to use this information (as the host segment of the complete IP address) and aggregation- The prefix-A (the network segment that is the complete IP address) is combined to obtain the final complete IP address corresponding to the detailed FEC.
  • FIG. 4 is a message encapsulation format according to an embodiment of the present disclosure.
  • the detailed FEC is encapsulated by using a type 2 packaging form.
  • the encapsulated detailed FEC information may also be an MPLS label (as shown in (c) in FIG. 4).
  • the MPLS label is allocated by the node A for the detailed FEC.
  • the packaged detailed FEC information may also be a prefix-sid (as shown in (d) of FIG. 4).
  • the method further comprises: notifying an encapsulation form of the detailed FEC to the other nodes.
  • the way of the announcement includes at least one of the following: extending an MPLS label protocol for announcing a label binding message of a prefix type FEC, using the extended MPLS label protocol to advertise;
  • the segmented routing SR protocol used to advertise label-bound messages of the prefix type FEC is extended and advertised using the extended SR protocol.
  • the first node may notify the neighbor node of the label binding message of the container FEC through the MPLS label protocol, and accurately set the configured encapsulation type type in the notification message.
  • the container label is used as a normal MPLS label to encapsulate the message, so that the container label encapsulated in the packet label stack of the message does not immediately follow the detailed FEC information, so when such a message reaches node A, node A always It is considered that detailed FEC information immediately followed by the container label will inevitably lead to packet parsing errors.
  • extending the LDP protocol for advertising a label binding message of a prefix type FEC includes: based on a request for amendment RFC5036, Adding a container label type-length-value (Container Label TLV) to the LDP protocol; using the Container Label TLV in the extended LDP protocol for notification.
  • container label type-length-value Container Label TLV
  • FIG. 5 is a specific implementation of the label binding information announcement of the extended LDP support container FEC, which is based on RFC5036, and a new Container Label TLV is added to the existing Generic Label TLV is completely similar, except that the value of TYPE is 0x02ff, and the Style field can be set to 1 (see the aforementioned type 1) or 2 (see the aforementioned type 2). The interpretation of other fields is exactly the same as Generic Label TLV.
  • extending the ISIS protocol for advertising a label binding message of a prefix type FEC includes: draft-ietf-isis-segment- On the basis of routing-extensions-16, add a container-prefix-segment identifier-type-length-value Container-Prefix-SID Sub-TLV to the ISIS protocol; use the described in the extended ISIS protocol Container-Prefix-SID and Sub-TLV.
  • FIG. 5 is a specific implementation of the tag binding information announcement of the extended ISIS support container FEC, which is based on draft-ietf-isis-segment-routing-extensions-16, adding a new This kind of Container-Prefix-SID Sub-TLV is completely similar to the existing Prefix-SID Sub-TLV, except that the TYPE value is 15, and the S-Flag flag is added to the Flags field (the value can be 0 corresponding to the aforementioned Type 1 or a value of 1 corresponds to the foregoing type 2). Note that the values of the following flags in Flags are fixed at this time: N-Flag must be 0, P-Flag must be 1, and E-Flag must be 0.
  • Prefix-SID and Sub-TLV The interpretation of other fields is exactly the same as Prefix-SID and Sub-TLV.
  • a new Container-Prefix-SID Sub-TLV instead of adding a container flag in the existing Prefix-SID Sub-TLV or an existing prefix announcement (such as TLV-135 (Extended IPv4reachability) is defined in RFC5305 , Or TLV-235 (Multitopology IPv4Reachability) is defined in RFC5120, or TLV-236 (Multicastology IPv6Reachability) is defined in RFC5308, or TLV-237 (Multitopology IPv6IP Reachability) is defined in RFC5120) to extend the specific implementation of adding container flags, so that those The old equipment that does not recognize the Container-Prefix-SID Sub-TLV will directly discard the received label binding information notification message of the container FEC, and the new equipment that can recognize the Container-Prefix-SID Sub-TLV will be processed normally And install the entry.
  • TLV-135 Extended IP
  • extending BGP for advertising a label binding message of a prefix prefix type FEC includes: draft-ietf-idr-bgp-perfix-sid On the basis of -20, adding a Container-Label-Index, Type-Length-Value (Container-Label-Index-TLV) to the BGP, wherein the Container-Label-Index-TLV is carried with the BGP Prefix-SID attribute; Use the Container-Label-Index TLV in the extended BGP for notification.
  • c) in FIG. 5 is a specific implementation of the label binding information announcement of the extended SR-BGP support container FEC, which is based on draft-ietf-idr-bgp-prefix-sid-20.
  • Add a Container-Label-Index TLV which is carried with the BGP Prefix-SID attribute, and is completely similar to the existing Label-Index TLV, except that the value of TYPE is 2, and the S-Flag flag is added to the Flags field.
  • a value of 0 corresponds to the foregoing type 1 or a value of 1 corresponds to the foregoing type 2).
  • the interpretation of other fields is exactly the same as the Label-Index TLV.
  • the label operation in the first ILM entry is pop-up (POP).
  • the method includes: after receiving the second message, the second node may continue to redistribute the MPLS label for the first container FEC and create a corresponding ILM entry, and the entry is marked with a container flag
  • the label operation is SWAP (exchange).
  • the second node may also create a corresponding FTN entry for the container FEC, and the entry is marked with a container flag. Therefore, in the case that the message hits this FTN entry, in addition to encapsulating the container tag given by the FTN in the message label stack, the message label stack also encapsulates information about the detailed FEC immediately after the container label. .
  • the message received on the second node side corresponds to the second message
  • the ILM entry created corresponds to the second ILM entry
  • the FTN entry created corresponds to the second FTN entry.
  • FIG. 6 is a flowchart of a method for notifying a binding relationship according to an embodiment of the present disclosure. As shown in FIG. 6, the flow includes step S602.
  • a binding relationship announced by the first node is received on a second node, wherein the first node is a node having route aggregation, and the binding relationship is between a container label and a first container FEC.
  • the container label is assigned in advance to the first container FEC in the first node, and the first container FEC is a carrying container obtained by configuring a route aggregated on the first node.
  • a flag FEC the container flag is used to identify that the first container FEC is a container FEC type.
  • the binding relationship is notified to other nodes other than the first node.
  • the second node in the embodiment of the present disclosure may be other nodes in the foregoing embodiment.
  • the subsequent embodiment is a further description of the action after the second node receives the binding relationship.
  • the method further includes at least one of the following: when the second node is the first container FEC When transmitting a node, a new container label is assigned to the first container FEC, and then the upstream node is further notified of the binding relationship between the new container label and the first container FEC, and creates a connection with the first container FEC.
  • a second ILM entry corresponding to the container FEC wherein the second ILM entry carries the container identifier; when the second node is an entry node of the first container FEC, it is the first container
  • the FEC creates a corresponding second FTN entry, where the second FTN entry carries the container identifier.
  • the method further includes: in a case where the received packet matches the second ILM entry, Performing a label exchange operation according to a container label located on the top layer of the message, ignoring information about the detailed FEC after the container label of the message; or, when the received message matches the second ILM entry, And when the time-to-live value (TTL) of the top-level container label of the message times out, the message is sent to the control plane for processing, wherein the detailed FEC after the container label in the message Information is not a label.
  • TTL time-to-live value
  • the method further includes: when the received packet matches the second FTN entry, Encapsulating the container label in the second FTN entry for the data message, and encapsulating information about the detailed FEC after the container label, wherein the container label and the information about the detailed FEC form a whole .
  • the second node after the second node receives the label binding message of the container FEC, the second node can serve as a transmission node of the container FEC, and can continue to assign an MPLS label to the container FEC and create a corresponding ILM entry.
  • the entry is marked with a container flag, and the label operation is SWAP (exchange).
  • SWAP exchange
  • the MPLS packet that hits this ILM entry generally only performs label exchange based on the container label located on the top layer of the packet, and does not perceive and analyze the detailed FEC information immediately following the container label in the packet.
  • the second node may receive an MPLS packet and find that the TTL of the container label on the top layer has timed out.
  • the second node can also serve as the ingress node of the container FEC, and create a corresponding FTN entry (denoted as FTN-aggregation) for the container FEC. If the container flag is marked in the entry, the packet that hits the FTN entry In addition to packaging the container label, information about the detailed FEC is packaged immediately after the container label. Note that the detailed FEC information encapsulated immediately after the container label cannot itself be regarded as a label, but as a whole with the container label.
  • the second node may even further aggregate routes, for example, the further aggregated route is aggregation-prefix-B. Similar to the first node, aggregation-prefix-B is configured as a container FEC and a corresponding ILM is established. The entry is marked with a container flag, and the label operation is POP. Then, the packet that hits this ILM entry will query the FTN entry according to the detailed FEC information immediately following the container tag in the message label stack.
  • the label of the packet is exchanged with the outgoing label of the FTN-aggregation entry, and the packet continues to be forwarded along the LSP corresponding to the FTN-aggregation (note that the If the FTN-aggregation entry has a container flag, the detailed FEC information immediately following the original container tag in the packet label stack of the packet should be retained when forwarding. If the FTN entry cannot be queried, it is determined based on whether the bottom flag of the container tag is valid. The message continues to be forwarded along the IP (when the bottom of the stack is valid, the container label in the message label stack and the detailed FEC information immediately following it will be removed, and the path will be checked according to the IP payload. Table forward) or drop (bottom of the stack flag invalid).
  • the method further comprises: receiving, on a second node, an encapsulation form advertised by the first node, wherein the encapsulation form is in a packet label stack in the first node Encapsulation form of the information about the detailed FEC encapsulated after the container label.
  • the second node in the embodiment of the present disclosure may be one of the other nodes in the foregoing embodiment.
  • the encapsulation form includes at least one of the following: an encapsulation form that directly encapsulates the detailed FEC IP address information; an encapsulation header that encapsulates at least one of the following information: an IP of the detail FEC Address information, MPLS label information, and segment identification SID information.
  • the IP address information includes one of the following: complete IP address information, and host segment information including only IP addresses.
  • the network shown in FIG. 7 includes access, aggregation, and core domains. Each domain is deployed with a separate IGP (such as ISIS) process, and routes are redistributed between IGP processes.
  • IGP such as ISIS
  • AN indicates an access node (Access node)
  • AGN indicates an aggregation node (Aggregation Node)
  • LSR Label Switching Router
  • the loopback address of AN2 is 200.2.2.2, AGN2 will learn the detailed route 200.2.2.2/32 through the IGP5 process, and also redistribute the aggregated route 200.2.2.0/24 to the IGP4 process; LSR2 learns the route 200.2 through the IGP4 process.
  • a message sending method includes the following steps 701 to 706.
  • the redistributed aggregated route can be configured as a container FEC and the detailed FEC encapsulation style is configured as Style-1, and the container FEC is synchronized to the LDP protocol, and LDP will be
  • the corresponding container FEC allocates an MPLS label and notifies the neighbor of the binding relationship between the corresponding container FEC and the MPLS label allocated to it (using Container Label TLV) and generates an ILM entry.
  • a container FEC IPv4 prefix 200.2.2.0/2
  • a corresponding ILM entry (denoted as ILM-5) will be generated.
  • the label operation in the ILM entry is POP and contains a container flag, Style-1 flag, IPv4 flag.
  • AGN2 also maintains the corresponding FTN entry (denoted as FTN-5) for the detailed FEC (IPv4 prefix 200.2.2.2/32), and the FTN entry does not include the container flag.
  • LSR2 will generate a container FEC (IPv4 prefix 200.2.0.0/16) and a corresponding ILM entry (denoted as ILM-4).
  • the label operation in the ILM entry is POP and includes a container flag, Style-1 flag, and IPv4 flag.
  • LSR2 also maintains the corresponding FTN entries (denoted as FTN-4) for detailed FEC (IPv4 prefix 200.2.2.0/24), and the FTN entries include the container flag and the Style-1 flag.
  • LSR1 will generate a container FEC (IPv4 prefix 200.0.0.0/8) and a corresponding ILM entry (denoted as ILM-3).
  • the label operation in the ILM entry is POP and includes a container flag, Style-1 flag, and IPv4 flag.
  • LSR1 also maintains the corresponding FTN entries (denoted as FTN-3) for the detailed FEC (IPv4 prefix 200.2.0.0/16).
  • the FTN entries include the container flag and the Style-1 flag.
  • AGN1 will generate a container FEC (IPv4 prefix 0.0.0.0/0) and the corresponding ILM entry (denoted as ILM-2).
  • the label operation in the ILM entry is POP and contains the container flag, Style-1 flag, and IPv4 flag.
  • AGN1 also maintains the corresponding FTN entries (denoted as FTN-2) for the detailed FEC (IPv4 prefix 200.0.0.0/8).
  • the FTN entries include the container flag and the Style-1 flag.
  • FTN-1 The corresponding FTN entry (denoted as FTN-1) will be maintained for detailed FEC (IPv4 prefix 0.0.0.0/0) on AN1.
  • FTN entry contains the container flag and the Style-1 flag.
  • Step 702 assuming that an IPv4 packet (this may be a PING packet, a BGP protocol packet, and the like) with the destination IP of AN2 (200.2.2.2) needs to be sent on AN1, the packet will match the above FTN-1 table Entry, because the FTN-1 entry contains the container flag and the Style-1 flag, the tag given in the FTN-1 entry is encapsulated in the IPv4 packet (and the bottom tag of the tag is set to 1).
  • the detailed FEC information (200.2.2.2) is encapsulated immediately after the label, and the message is forwarded to AGN1.
  • step 703 after the AGN1 receives the message, the label of the received message will hit the above ILM-2 entry.
  • the label operation in the ILM-2 entry is POP and contains the container flag, Style-1 flag, and IPv4 flag.
  • the label located on the top layer of the message and the detailed FEC information (200.2.2.2) immediately following it are stripped, and then based on the detailed FEC information (200.2.2.2), it continues to find the corresponding FTN entry, and determines that the message will match the above FTN -2 entry. Since the FTN-2 entry contains the container flag and the Style-1 flag, the tag given in the FTN-2 entry is encapsulated in the IPv4 packet (and the bottom tag of the tag is set to 1). ), While encapsulating the detailed FEC information (200.2.2.2) immediately after the label, the message is forwarded to LSR1.
  • the label of the received message will hit the above-mentioned ILM-3 entry, and the label on the top layer of the message and its subsequent detailed FEC information (200.2. 2.2) Strip, then continue to find and match the above FTN-3 entries based on the detailed FEC information (200.2.2.2), and finally encapsulate the tag given in the FTN-3 entry in the IPv4 packet (and then The bottom mark of the stack is set to 1), and the detailed FEC information (200.2.2.2) is encapsulated immediately after the label, and the message is forwarded to LSR2.
  • the label of the received message will hit the above ILM-4 entry, and the label on the top layer of the message and its subsequent detailed FEC information (200.2. 2.2) Strip, then continue to find and match the above FTN-4 entry based on the detailed FEC information (200.2.2.2), and finally encapsulate the tag given in the FTN-4 entry in the IPv4 packet (and then The bottom of the stack is set to 1), and the detailed FEC information (200.2.2.2) is encapsulated immediately after the label, and the message is forwarded to AGN2.
  • step 706 similarly, after the AGN2 receives the message, the label of the received message will hit the above ILM-5 entry, and the label on the top layer of the message and its subsequent detailed FEC information (200.2. 2.2) Strip, and then continue to find and match the above FTN-5 entries based on the detailed FEC information (200.2.2.2), and determine that the message will match the above FTN-5 entries, because the FTN-5 entries do not contain containers Flag, after encapsulating the label given in the FTN-5 entry in the IPv4 packet (and setting the bottom label of the label to 1), the detailed FEC information is no longer encapsulated immediately after the label (200.2.2.2), The message is forwarded to AN2.
  • a path has been formed from AN1 to AN2 that uses label switching along the way.
  • the IPv4 payload is not exposed at all, and the detailed FEC for AN2 does not need to be announced with the LDP protocol.
  • the label switching path needs to carry other MPLS payloads, such as VPN labels, the process is similar to the above.
  • a VPN label (the bottom of the stack is labeled 1) can be encapsulated for the packet and then continue to be based on BGP next-hop (AN2 ) Iterates to the above FTN-1 entries, and continues to package the packet label (its bottom label is 0) and the detailed FEC information (200.2.2.2), which will not be described in detail.
  • SR-ISIS can also be used to send messages from AN1 to AN2.
  • the specific process includes the following steps 1 and 2.
  • the redistributed aggregated route can be configured as a container FEC, and the detailed FEC encapsulation style is configured as Style-1, so that the IGP will assign a prefix- sid and notify neighbors (using Container-Prefix-SID Sub-TLV) and generate ILM entries.
  • the FTN and ILM entries generated on each node are basically the same as the LDP message sending process described above.
  • step 2 assuming that an IPv4 packet with a destination IP of AN2 (200.2.2.2) needs to be sent on AN1, the packet will match the above FTN-1 entry.
  • the subsequent forwarding process of the packet is the same as described above.
  • the process of sending LDP packets is basically the same.
  • IPv4 payload is not exposed during the entire process, and the detailed route for AN2 does not need to be flooded throughout.
  • the network shown in FIG. 8 includes access, aggregation, and core domains. Each domain deploys a separate IGP (such as ISIS) process, but does not leak IGP routes to each other.
  • IGP such as ISIS
  • the explanation of the AN, AGN, and LSR nodes in FIG. 8 is basically the same as the network shown in FIG. 7.
  • ABR represents the border node (Area Border Router) of the aggregation domain and the core domain.
  • a BGP session is generally established between border nodes to advertise the BGP-LU detailed route. For example, ABR1 advertises the detailed route of LSR1 to AGN1 through BGP-LU, and AGN1 in turn also passes BGP- LU continues to announce to AN1.
  • ABR1 only needs to advertise the route that aggregates all LSRs to AGN1 through BGP-LU, and AGN1 only needs to advertise the default route (0.0.0.0/0) to AN1 through BGP-LU.
  • the loopback address of LSR1 is 100.1.1.1.
  • the detailed route 100.1.1.1/32 is learned through the IGP3 process.
  • the aggregate route 100.1.0.0/16 is redistributed to AGN1 through BGP-LU.
  • AGN1 continues to pass BGP.
  • -LU redistributes the default route (0.0.0.0/0) to AN1.
  • SR-BGP is enabled on the border nodes of the entire network, and SR-ISIS is enabled on the nodes in each IGP domain.
  • a message sending method according to an embodiment of the present disclosure includes the following steps 801 to 804.
  • Step 801 On the nodes that redistribute the aggregated routes, all the redistributed aggregated routes can be configured as container FEC and the detailed FEC encapsulation style is configured as Style-2, and BGP will assign a prefix-sid to the corresponding aggregated route and Notify neighbors (using Container-Label-Index TLV) and generate ILM entries.
  • ABR1 will generate the container FEC (IPv4 prefix 100.1.0.0/16) and the corresponding ILM entry (denoted as ILM-3).
  • the label operation in the ILM entry is POP and contains the container flag, Style-2 flag, and IPv4. Sign.
  • ABR1 also maintains the corresponding FTN entry (denoted as FTN-3) for the detailed FEC (IPv4 prefix 100.1.1.1/32), and the FTN entry does not include a container flag.
  • AGN1 will generate the container FEC (IPv4 prefix 0.0.0.0/0) and the corresponding ILM entry (denoted as ILM-2).
  • the label operation in the ILM entry is POP and contains the container flag, Style-2 flag, and IPv4 flag.
  • AGN1 also maintains the corresponding FTN entries (referred to as FTN-2) for FEC (IPv4 prefix 100.1.0.0/16).
  • the FTN entries include the container flag and the Style-2 flag.
  • AN1 will maintain the corresponding FTN entries (referred to as FTN-1) for FEC (IPv4 prefix 0.0.0.0/0).
  • FTN entries include the container flag and the Style-2 flag.
  • step 802 it is assumed that an IPv4 packet with a destination IP of LSR1 (100.1.1.1) needs to be sent on AN1, and the packet will match the above-mentioned FTN-1 entry. Since the FTN-1 entry contains a container flag, The Style-2 flag encapsulates the label given in the FTN-1 entry in the IPv4 packet (and sets the label's bottom flag to 1), and immediately encapsulates the container_header (where Type can be set to 1, The host segment information 100.1.1.1 of the detailed FEC information is re-encapsulated in the container_header. This is because the prefix length of the default route 0.0.0.0/0 matched by 100.1.1.1 is 0, so the entire 100.1.1.1 can be considered as the host segment. Note Type can also be set to 0, 2, 3 and other values, which is the local behavior of AN1). After continuing to encapsulate the outer SR-ISIS LSP label, it forwards the message to AGN1.
  • step 803 after AGN1 receives the packet, the label of the packet will hit the above ILM-2 entry.
  • the label operation in the ILM-2 entry is POP and contains the container flag, Style-2 flag, and IPv4 flag.
  • the top-level label of the text, its immediately following container_header, and its detailed FEC information are stripped, and then based on the detailed FEC information (100.1.1.1, this is the FEC 0.0.0.0/0 network segment of ILM-2 and 100.1 .1.1 phase or obtained) continue to find the corresponding FTN entry, determine that the message will match the above FTN-2 entry, because the FTN-2 entry contains the container flag and the Style-2 flag, FTN is encapsulated in the IPv4 message -2
  • the label given in the table entry (and set the label's bottom of the label to 1), and at the same time immediately after the label encapsulates the container_header (where Type can be set to 1, and the container_header encapsulates the detailed FEC information of the host segment information 0.0.
  • the label of the message will hit the above ILM-3 entry, and the label at the top of the message and its immediately following container_header and the detailed FEC information it encapsulates Strip, then based on the detailed FEC information (100.1.1.1, which is obtained by matching the network segment of ILC-3's FEC 100.1.0.0/16 with 0.0.1.1) and continue to find and match the above FTN-3 entries, Since the FTN-3 entry does not contain a container flag, the tag given in the FTN-3 entry is encapsulated in the IPv4 packet (and the bottom label of the tag is set to 1), and no longer immediately follows the tag. After encapsulating the container_header and continuing to encapsulate the outer SR-ISIS LSP label, the packet is forwarded to LSR1.
  • the software may be stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disc), and includes several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the embodiments of the present disclosure.
  • a terminal device which may be a mobile phone, a computer, a server, or a network device, etc.
  • An embodiment of the present disclosure also provides a device for sending a message and a device for receiving a message.
  • the device is used to implement the foregoing embodiment, and the description has not been repeated.
  • the term "module" may implement a combination of software and / or hardware for a predetermined function.
  • the devices described in the following embodiments may be implemented in software, hardware, or a combination of software and hardware.
  • FIG. 9 is a structural block diagram of a message transmitting apparatus according to an embodiment of the present disclosure. As shown in FIG. 9, the device includes a first receiving module 92, a switching module 94, and a forwarding module 96.
  • the first receiving module 92 is configured to receive a first packet on a first node that has undergone route aggregation.
  • the switching module 94 is configured to exchange a label of the first packet to a corresponding FEC in the case that the first packet matches a first ILM entry set on the first node in advance. Label out and get the second message.
  • the forwarding module 96 is configured to forward the second packet to a downstream node according to an LSP corresponding to the detailed FEC.
  • the device further includes at least one of the following: a configuration module configured to, before the first receiving module 92 receives the first packet on the first node on which route aggregation has been performed, The aggregated route is configured as a first container FEC on one node, wherein the first container FEC carries a container flag, and the container flag is used to identify the first container FEC as a container FEC type; a creating module is set to The first receiving module 92 creates the first ILM entry for the first container FEC before receiving the first packet on the first node where the route aggregation is performed, where the first ILM entry carries The container sign.
  • the exchange module 94 is specifically configured to: when the first packet matches the first ILM entry, query and exchange the packet according to the encapsulation information after the container label in the packet label stack.
  • the outgoing label corresponding to the detailed FEC is to exchange the container label in the packet label stack with the outgoing label corresponding to the detailed FEC.
  • the packet label stack is a label stack generated in advance on a node upstream of the first node
  • the container label is an MPLS label having a binding relationship with the first container FEC
  • the information is information about the detailed FEC encapsulated in the message label stack after the container label.
  • the device is further configured to configure the binding relationship before querying an out-label corresponding to the detailed FEC according to the encapsulation information after the container label in the message label stack.
  • the device is further configured to, after configuring the binding relationship: notify the binding relationship to other nodes except the first node.
  • the exchange module 94 may query the outgoing label corresponding to the detailed FEC in the following manner: according to the encapsulation information query and the detailed information after the container label in the message label stack A first FTN entry corresponding to the FEC; and when the first FTN entry is queried, it is determined that the outgoing label in the first FTN entry is an outgoing label corresponding to the detailed FEC.
  • the device is further configured to perform at least one of the following operations after querying the first FTN entry corresponding to the detailed FEC according to the encapsulation information after the container label in the message label stack.
  • 1 In the case where the first FTN entry is not queried, and if it is determined that the bottom-of-stack flag of the container label in the packet stack of the message is valid, all the packets in the packet stack are removed.
  • the container label and subsequent encapsulation information query a routing table according to an Internet Protocol (IP) payload, and forward the first message according to the routing table; if the first FTN entry is not queried, and When it is determined that the stack bottom flag of the container label in the packet label stack is invalid, the first packet is discarded.
  • IP Internet Protocol
  • the device is further configured to maintain the first FTN entry corresponding to the detailed FEC according to the encapsulation information after the container tag in the message label stack.
  • the first FTN entry corresponding to the first FEC generated by a previous node of the first node, wherein the previous node of the first node includes a node that originally generated the first FEC.
  • the first FTN entry when the type of the first FEC generated by a previous node of the first node is not a container FEC, the first FTN entry does not include the container flag; when the first When the type of the first FEC generated by the previous node of the node is a container FEC, the first FTN entry includes the container flag.
  • the container label in the packet label stack is exchanged for the outgoing label in the first FTN entry, and Information about detailed FEC encapsulated after the container label in the message label stack; when the container flag is included in the first FTN entry, the container label in the message label stack is exchanged for all Describe the outgoing label in the first FTN entry, and retain the information about the detailed FEC encapsulated after the container label in the message label stack.
  • the encapsulation form of the encapsulation information includes at least one of the following: an encapsulation form of directly encapsulating the IP address information of the detailed FEC; an encapsulation form of encapsulating at least one of the following information using an encapsulation header: the detail The FEC's IP address information, MPLS label information, and segment identification SID information, where the IP address information includes one of the following: complete IP address information, and host segment information including only the IP address.
  • the apparatus is further configured to notify the encapsulation form of the detailed FEC to the other nodes.
  • the device notification mode includes at least one of: extending an MPLS label protocol used to advertise a label binding message of a prefix type FEC, using the extended MPLS label protocol to advertise;
  • the SR protocol that advertises the label binding message of the prefix type FEC is extended, and the extended SR protocol is used for advertisement.
  • the device when the MPLS label protocol includes a label distribution protocol, the LDP protocol, the device extends the LDP protocol used to advertise a label binding message of a prefix type FEC by: On the basis of RFC5036, a container label type-length-value (Container Label TLV) is added to the LDP protocol; and the Container Label TLV in the extended LDP protocol is used for notification.
  • a container label type-length-value Container Label TLV
  • the device when the SR protocol includes an intermediate system to an intermediate system ISIS protocol, the device extends the ISIS protocol for advertising a label binding message of a prefix type FEC in the following manner: in draft-ietf -isis-segment-routing-extensions-16, adding a container-prefix-segment identifier-type-length-value Container-Prefix-SID Sub-TLV to the ISIS protocol; using the extended ISIS The Container-Prefix-SID and Sub-TLV in the protocol announce.
  • the device when the SR protocol includes a border gateway protocol BGP, the device is configured to extend BGP for advertising a label binding message of a prefix prefix type FEC in the following manner: in draft-ietf- On the basis of idr-bgp-perfix-sid-20, a Container-Label-Index TLV is added to the BGP, where the Container-Label-Index TLV follows The BGP Prefix-SID attribute is carried; and the Container-Label-Index TLV in the extended BGP is used for notification.
  • a Container-Label-Index TLV is added to the BGP, where the Container-Label-Index TLV follows The BGP Prefix-SID attribute is carried; and the Container-Label-Index TLV in the extended BGP is used for notification.
  • the label operation in the first ILM entry is pop-up (POP).
  • FIG. 10 is a structural block diagram of a binding relationship notification device according to an embodiment of the present disclosure. As shown in FIG. 10, the device includes a second receiving module 102.
  • the second receiving module 102 is configured to receive a binding relationship announced by the first node on a second node, where the first node is a node that has been aggregated by a route, and the binding relationship is a container label and the first Binding relationship between container FECs, the container label is pre-assigned in the first node for the first container FEC, and the first container FEC configures a route aggregated on the first node
  • the obtained FEC carrying a container logo, where the container logo is used to identify that the first container FEC is a container FEC type.
  • the apparatus further includes: an allocation module configured to, after receiving the binding relationship announced by the first node on the second node, perform at least one of the following operations: when the second node When a transmission node of the first container FEC is allocated, a new container label is allocated to the first container FEC, and then the binding relationship between the new container label and the first container FEC is further notified to an upstream node. And create a second ILM entry corresponding to the first container FEC, wherein the second ILM entry carries the container identifier; when the second node is an entry node of the first container FEC When a corresponding second FTN entry is created for the first container FEC, wherein the second FTN entry carries the container identifier.
  • the device further includes: a first processing module configured to perform one of the following operations after creating a second ILM entry corresponding to the first container FEC: a received message
  • a label exchange operation is performed according to the container label located on the top layer of the message, and the information about the detailed FEC after the container label of the message is ignored; or, If the packet matches the second ILM entry and the time-to-live (TTL) of the container label on the top of the packet times out, the packet is sent to the control plane for processing, where , The detailed FEC information after the container label in the message is not a label.
  • TTL time-to-live
  • the apparatus further includes: a second processing module configured to, after creating a corresponding second FTN entry for the first container FEC, receive the message and the second FTN If the entry matches, the data packet is used to encapsulate the container tag in the second FTN entry, and after the container tag, information about the detailed FEC is encapsulated, wherein the container tag and the about The detailed FEC information forms a whole.
  • a second processing module configured to, after creating a corresponding second FTN entry for the first container FEC, receive the message and the second FTN If the entry matches, the data packet is used to encapsulate the container tag in the second FTN entry, and after the container tag, information about the detailed FEC is encapsulated, wherein the container tag and the about The detailed FEC information forms a whole.
  • the label operation in the second ILM entry is exchange (SWAP).
  • the apparatus is further configured to receive, on a second node, an encapsulation form advertised by the first node, wherein the encapsulation form is in a packet label stack in the first node. Encapsulation form of the information about the detailed FEC encapsulated after the container label.
  • the encapsulation form includes at least one of the following: an encapsulation form that directly encapsulates the detailed FEC IP address information; an encapsulation header that encapsulates at least one of the following information: an IP of the detail FEC Address information, MPLS label information, and segment identification SID information, where the IP address information includes one of the following: complete IP address information, and host segment information including only IP addresses.
  • the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but not limited to the above: the above modules are located in the same processor; or the above modules are combined in any combination The forms are located in different processors.
  • An embodiment of the present disclosure further provides a storage medium having a computer program stored therein, wherein the computer program executes a method for transmitting a message according to an embodiment of the present disclosure when the computer program is executed by a processor.
  • the storage medium may include, but is not limited to, various media that can store a computer program, such as a U disk, a read only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk. .
  • a computer program such as a U disk, a read only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.
  • An embodiment of the present disclosure also provides an electronic device including a memory and a processor, wherein the computer program is stored in the memory, and the processor is configured to run the computer program to perform transmission of a message according to an embodiment of the present disclosure. method.
  • the electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the processor, and the input-output device is connected to the processor.
  • modules or steps of the present disclosure may be implemented by a general-purpose computing device, and they may be centralized on a single computing device or distributed on a network composed of multiple computing devices. Alternatively, they may be implemented with program code executable by a computing device, such that they may be stored in a storage device and executed by the computing device, and in some cases, all of the steps may be performed in a different order than here.
  • the steps shown or described are implemented by either making them into individual integrated circuit modules or making multiple modules or steps into a single integrated circuit module. As such, the present disclosure is not limited to any particular combination of hardware and software.

Landscapes

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

Abstract

提供了一种报文的发送方法、绑定关系的通告方法、报文的发送装置、绑定关系的通告装置、存储介质及电子装置。所述报文的发送方法包括：在进行了路由聚合的第一节点上接收第一报文；在所述第一报文与预先在所述第一节点上设置的第一入标签映射(ILM)表项匹配的情况下，将所述第一报文的标签交换为与明细转发等价类(FEC)对应的出标签，得到第二报文；按照与明细FEC对应的标签转发路径LSP将所述第二报文转发给下游节点。

Description

报文的发送方法、绑定关系的通告方法、装置及存储介质 技术领域
本公开涉及通信领域。
背景技术
MPLS(Multiprotocol Label Switching多协议标签交换，见RFC3031)架构中提到了FEC(Forwarding Equivalence Class转发等价类)聚合的概念和FEC聚合策略。FEC聚合策略可以是粗粒度的聚合策略，例如，将多个不同的FEC组成一个联合体，此时该联合体本身是一个FEC，将联合体内的各个成员称为component FEC(或称为明细FEC)，为该联合体分配单个MPLS标签。FEC聚合策略也可以是细粒度的聚合策略，例如，为每个明细FEC都分配一个MPLS标签。FEC聚合策略还可以是介于粗粒度与细粒度之间的聚合策略，例如，FEC聚合策略可以是简单的沿用路由聚合策略，此时，聚合后的路由本身是一个FEC并被分配MPLS标签，或者，FEC聚合策略可以是BGP(Border Gateway Protocol边界网关协议)或MPLS IP VPN(Internet Protocol Virtual Private Networks，IP虚拟专用网，见RFC4364)中的每VPN标签分配模式，此时PE(Provider Edge)设备为同一VPN实例内的所有本地CE(Customer Edge)设备侧私网路由分配相同的MPLS标签。从这些例子中，我们可以看到FEC聚合策略本质上是一种标签分配策略，相应的标签转发行为一般是POP(弹出)后基于IP载荷继续转发，对现有的MPLS转发机制并没有新要求，发生FEC聚合后一般不再为明细FEC建立端到端的MPLS LSP(Label Switched Path，标签交换路径)，但很多场景下仍需要配置复杂的策略为指定的明细FEC建立端到端的MPLS LSP。
在实际网络部署中，路由聚合后在IGP(Interior Gateway Protocol，内部网关协仪)(例如，ISIS(Intermediate System to Intermediate System中间系统至中间系统协议)、OSPF(Open  Shortest Path First开放式最短路径优先协议))域间泄露是很常见的，IP转发的最长匹配规则天然支持路由聚合，但是现有MPLS LSP的转发机制却是基于精确匹配规则，因此总是需要一定数量的端到端的明细FEC通告。针对这种FEC聚合策略和路由聚合策略不一致的状况，业界提出了一些解决思路，如RFC5283、RFC7032是对LDP(Label Distribution Protocol标签分发协议，见RFC5036)协议做了扩展。RFC5283主要是将原来RFC5036规定的在明细FEC必须有精确匹配的明细路由时才建立LSP的限制修改为在明细FEC能最长匹配到一条路由并且该路由的下一跳是明细FEC的标签通告邻居时建立LSP。RFC7032主要是通过使业务动态触发明细FEC的LSP建立和销毁来解决明细FEC如何诞生和消亡的问题，以及提供LDP DOD(Downstream on Demand下游按需)快速收敛的手段。这种解决思路有其局限性，无法作为一种通用的解决方案适用于其它MPLS标签分发协议，比如BGP、SR(Segment Routing分段路由，此处特指SR-MPLS，即SR应用MPLS转发平面)。
发明内容
本公开的一方面提供了一种报文的发送方法，所述报文的发送方法包括：在进行了路由聚合的第一节点上接收第一报文；在所述第一报文与预先在所述第一节点上设置的第一入标签映射(ILM)表项匹配的情况下，将所述第一报文的标签交换为明细转发等价类(FEC)对应的出标签，得到第二报文；按照与所述明细FEC对应的标签转发路径(LSP)将所述第二报文转发给下游节点。
本公开的另一方面提供了一种绑定关系的通告方法，所述绑定关系的通告方法包括：在第二节点上接收由第一节点通告的绑定关系，其中，所述第一节点为进行了路由聚合的节点，所述绑定关系为容器标签与第一容器FEC之间的绑定关系，所述容器标签是所述第一节点中预先为所述第一容器FEC分配的，所述第一容器FEC是对所述第一节点上聚合的路由进行配置后得到的携带 容器标志的FEC，所述容器标志用于标识所述第一容器FEC为容器FEC类型。
本公开的再一方面提供了一种报文的发送装置，所述报文的发送装置包括：第一接收模块，设置为在进行了路由聚合的第一节点上接收第一报文；交换模块，设置为在所述第一报文与预先在所述第一节点上设置的第一入标签映射(ILM)表项匹配的情况下，将所述第一报文的标签交换为明细转发等价类(FEC)对应的出标签，得到第二报文；转发模块，设置为按照与所述明细FEC对应的标签转发路径(LSP)将所述第二报文转发给下游节点。
本公开的再一方面提供了一种绑定关系的通告装置，所述绑定关系的通告装置包括：第二接收模块，设置为在第二节点上接收由第一节点通告的绑定关系，其中，所述第一节点为进行了路由聚合的节点，所述绑定关系为容器标签与第一容器FEC之间的绑定关系，所述容器标签是所述第一节点中预先为所述第一容器FEC分配的，所述第一容器FEC是对所述第一节点上聚合的路由进行配置后得到的携带容器标志的FEC，所述容器标志用于标识所述第一容器FEC为容器FEC类型。
本公开的再一方面还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时，使得所述处理器执行上述报文的发送方法或绑定关系的通告方法。
本公开的再一方面还提供了一种电子装置，其包括存储器和处理器，所述存储器中存储有能够由所述处理器执行的计算机程序，所述处理器被所述处理器执行时，使得所述处理器执行上述报文的发送方法或绑定关系的通告方法。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是根据本公开的实施例的报文的发送方法的流程图；
图2是根据本公开的实施例的明细FEC的封装格式；
图3是根据本公开的另一实施例的明细FEC的封装格式；
图4是根据本公开的实施例的报文封装格式；
图5是根据本公开的实施例的扩展MPLS标签协议以及SR路由协议的示意图；
图6是根据本公开的实施例的绑定关系的通告方法的流程图；
图7是根据本公开的实施例的网络拓扑图；
图8是根据本公开的另一实施例的网络拓扑图；
图9是根据本公开的实施例的报文的发送装置的结构框图；
图10是根据本公开的实施例的绑定关系的通告装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在一些情况下，本公开中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序。
在本公开的实施例中提出了一种转发等价类(FEC)容器(container)的概念，以解决路由聚合后为业务建立端到端LSP的问题。术语“容器FEC”是为了与术语“FEC聚合(Aggregation)”进行区分，两者在协议通告与转发机制上存在差异。
首先需要说明的是，在本公开中，在第一节点侧，接收的报文对应于第一报文，创建的ILM表项对应于第一ILM表项，配置的容器FEC对应于第一容器FEC，查询的FTN表项对应于第一FTN表项。
图1是根据本公开的实施例的报文的发送方法的流程图。
如图1所示，在步骤S102，在进行了路由聚合的第一节点上接收第一报文。
在步骤S104，在所述第一报文与预先在所述第一节点上创建的第一入标签映射(ILM)表项匹配的情况下，将所述第一报文的标签交换为与明细FEC对应的出标签，得到第二报文。
在步骤S106，按照与所述明细FEC对应的标签转发路径(LSP)将所述第二报文转发给下游节点。
执行上述步骤的可以是上述的第一节点。在上述实施例中，聚合后的路由可以记为aggregation-prefix。在发生路由聚合的第一节点(第一节点可称为节点A，发生路由聚合的第一节点可以记为aggregation-prefix-A)上，可以将某个aggregation-prefix-A配置为容器FEC。容器FEC就是普通的prefix FEC，只不过打上了容器标志，并不是一种新的FEC类型。比如，对于LDP、BGP协议来说，可以照常为该aggregation-prefix-A分配标签(例如，MPLS标签，下面以MPLS标签为例)，创建相应的ILM表项，在ILM表项中打上容器标志；对于SR-MPLS的协议(如ISIS、OSPF、BGP路由协议)来说，可以照常为aggregation-prefix-A分配prefix-sid(Segment ID)，创建相应的ILM表项，同样也在ILM表项中打上容器标志。
通过上述方法，通过对报文的标签进行交换，可以只需要简单地随路由聚合建立端到端的LSP，而不需要通过配置复杂的策略来控制明细FEC通告以建立端到端的LSP，从而有效解决了在路由聚合后无法为业务建立端到端LSP的问题。
根据本公开的实施例，在步骤S102之前，所述方法还包括：在所述第一节点上将聚合的路由配置为第一容器FEC，其中，所述第一容器FEC携带容器标志，所述容器标志用于标识所述第一容器FEC为容器FEC类型；为所述第一容器FEC创建所述第一ILM表项，其中，所述第一ILM表项中携带所述容器标志。通过上述实施例，可以通过配置将在第一节点上聚合的路由作为一个容器FEC并为其分配MPLS标签(MPLS标签可被称为容器标签)，创建相应的ILM(入标签映射)表项，表项中打上容器标志。因此，命中此ILM表项的报文将根据报文标签栈中的标签之后的封 装信息查询出与明细FEC对应的出标签并进行标签交换操作，报文继续沿与明细FEC对应的LSP转发。
根据本公开的实施例，步骤S104可以包括：在第一报文与所述第一ILM表项匹配的情况下，根据报文标签栈中的容器标签之后的封装信息来查询与所述明细FEC对应的出标签，将所述报文标签栈中的容器标签交换为与查询出的与所述明细FEC对应的出标签，其中，所述报文标签栈为在处于所述第一节点的上游的节点上生成的标签栈，所述容器标签为与所述第一容器FEC具有绑定关系的MPLS标签，所述封装信息为在报文标签栈中在容器标签之后封装的关于明细FEC的信息。
下面将详细描述根据本公开的实施例的报文标签栈的生成方法。
节点A(对应上述的第一节点)收到的报文是处于节点A的上游的节点上生成的，上游节点可以是如下所示路由中的节点S。
S----P1----P2----A----P3----P4------D1
\------D2
\------D3
首先，在进行了路由聚合的节点A，将明细的主机路由(例如，D1、D2、D3等)聚合成一个聚合路由Dx并向节点S侧方向泛洪。具体地，将聚合路由Dx配置为容器FEC以产生容器FEC Dx，为容器FEC Dx分配容器标签并依次通过节点P2和节点P1向节点S侧方向通告，节点P2在收到容器FEC Dx后为容器FEC Dx重新分配容器标签，并向向P1通告重新分配容器标签的容器FEC Dx，P1在收到重新分配容器标签的容器FEC Dx后，为重新分配容器标签的容器FEC Dx再次重新分配容器标签，并向节点S通告再次重新分配容器标签的容器FEC Dx，最终在节点S上针对接收到的再次重新分配容器标签的容器FEC Dx生成FEC至下一跳标签转发单元映射(FEC to NHLFE Map，FTN)FTN表项。即，节点S上有一条FEC为Dx的LSP。
其次，在节点S上，对于将要发往目的地为D1(或D2,D3 等)的报文，节点S将根据目的IP D1查找与上述再次重新分配容器标签的容器FEC Dx对应的FTN表项。由于FTN表项中有容器标志，所以节点S为报文封装FTN表项中给出的出标签，还在出标签之后继续封装明细FEC D1信息，从而生成封装有容器标签和明细FEC D1的报文标签栈。
根据本公开的实施例，在根据报文标签栈中的容器标签之后的封装信息查询出与所述明细FEC对应的出标签之前，所述方法还包括：配置所述绑定关系。
根据本公开的实施例，在配置所述绑定关系之后，所述方法还包括：将所述绑定关系通告给除所述第一节点之外的其他节点。
根据本公开的实施例，根据报文标签栈中的容器标签之后的封装信息查询与所述明细FEC对应的出标签包括：根据所述报文标签栈中的所述容器标签之后封装信息查询与所述明细FEC对应的第一FTN表项；在查询到所述第一FTN表项的情况下，确定所述第一FTN表项中的出标签为与所述明细FEC对应的出标签。
根据本公开的实施例，在根据所述报文标签栈中的所述容器标签之后封装信息查询与所述明细FEC对应的第一FTN表项之后，所述方法还包括以下至少之一：在未查询到所述第一FTN表项的情况下，且在确定报文标签栈中的所述容器标签的栈底标志有效的情况下，移除所述报文标签栈中的所述容器标签及之后的封装信息，根据互联网协议(IP)载荷查询路由表，并根据所述路由表转发所述第一报文；在未查询到所述第一FTN表项的情况下，且在确定报文标签栈中的所述容器标签的栈底标志无效时，丢弃所述第一报文。
根据本公开的实施例，在根据所述报文标签栈中的所述容器标签之后的封装信息查询到与所述明细FEC对应的第一FTN表项之前，所述方法还包括：维护与所述第一节点的前一节点生成的所述第一FEC对应的所述第一FTN表项，其中，所述第一节点的前一节点包括原始产生所述第一FEC的节点。
根据本公开的实施例，第一节点可以作为该容器FEC的出口 节点，在这种情况下，ILM表项的标签操作为POP(弹出)。例如，与该ILM表项的对应的报文将根据报文标签栈中的容器标签之后紧随的明细FEC的信息查询到与该明细FEC对应的FTN表项(这里统一称为查询到FTN，并且查询到的FTN表项记为FTN-detailed表项)的出标签，并将报文标签栈中的容器标签与该出标签进行标签交换操作。在本公开实施例中，明细FEC信息有多种表示方式，例如，明细FEC可以是IP地址、prefix-sid、MPLS标签，那么根据本地实现，实际查询到的FTN表项可以是例如路由表项、SID表项、标签表项。需要说明的是，在应用RFC8029时，在对报文进行标签交换操作时，实际上也同时发生了FEC改变。报文继续沿与明细FEC对应的LSP转发。需要说明的是，如果查询到的FTN-detailed表项中没有容器标志，则转发时要移除报文标签栈中原来容器标签之后紧随的明细FEC信息。如果查询不到与明细FEC对应的FTN表项，则根据报文标签栈中的容器标签的栈底标志是否有效决定报文是继续沿IP转发，例如，如果栈底标志有效，则移除报文标签栈中的容器标签及其后紧随的明细FEC信息，并根据IP载荷查路由表转发，如果栈底标志无效，则丢弃该报文。
根据本公开的实施例，当所述第一节点的前一节点生成的第一FEC的类型不为容器FEC时，所述第一FTN表项不包括所述容器标志。
根据本公开的实施例，当所述第一节点的前一节点生成的第一FEC的类型为容器FEC时，所述第一FTN表项包括所述容器标志。
根据本公开的实施例上述方法还包括以下至少之一：当所述第一FTN表项中不包括所述容器标志时，将所述报文标签栈中的容器标签交换为所述第一FTN表项中的出标签，且移除所述报文标签栈中的容器标签之后封装的关于明细FEC的信息；当所述第一FTN表项中包括所述容器标志时，将所述报文标签栈中的容器标签交换为所述第一FTN表项中的出标签，且保留所述报文标签 栈中的容器标签之后封装的关于明细FEC的信息。
根据本公开的实施例，所述封装信息的封装形式包括以下至少之一：直接封装所述明细FEC的IP地址信息的封装形式；利用封装头封装以下信息至少之一的封装形式：所述明细FEC的IP地址信息、MPLS标签信息、段标识SID信息，其中，所述IP地址信息包括以下之一：完整的IP地址信息、仅包括IP地址的主机段信息。
根据本公开的实施例，报文标签栈中的紧随标签之后的封装信息可以有多种形式，例如，类型1(Style-1)：直接封装与明细FEC相关的IP地址信息，类型2(Style-2)：一种封装头(记为container_header)，在封装头中继续封装与明细FEC相关的IP地址信息、MPLS标签信息、或SID信息，其中，IP地址信息又可分为封装完整IP地址信息和仅封装IP地址的主机段信息。此外，明细FEC的信息可能还包含其它类型，例如，使用某个MPLS保留标签，其后紧随明细FEC信息。
上述明细FEC信息的封装形式在节点A上配置容器FEC时就要作为配置选项予以指定，在配置明细FEC的封装形式后，通常不再变动配置以避免报文解析错误。
图2是根据本公开的实施例的明细FEC的封装格式。
图2示出了明细FEC的类型1的封装形式，如图2所示，在类型1的报文封装中，取决于容器FEC是IPv4prefix还是IPv6prefix，与所封装的明细FEC相关的IP地址信息可以是一个IPv4地址(如图2中的(a)所示)或者IPv6地址(如图2中的(b)所示)。
图3是根据本公开的另一实施例的明细FEC的封装格式。
图3示出了明细FEC的类型2的封装形式，如图3所示，类型2的封装头中包括第一区域、Ver区域、Reserved区域、Length区域和Type区域。第一区域占4比特，取值为全1。Ver区域占4比特，表示版本号，当前取值为全0。Reserved区域占8比特，表示未用的保留字段，当前取值为全0。Length区域占8比特，表 示所封装的明细FEC信息的长度占用多少个字节(例如，4字节)，该长度不包含封装头自身的长度，例如，明细FEC信息的长度的取值范围可以是1～4字节。Type区域占8比特，表示所封装的明细FEC信息的封装类型，当前定义了四种类型，其中，Type＝0表示与封装明细FEC对应的完整IP地址，Type＝1表示封装与明细FEC对应的IP地址的主机段信息，主要用于IPv6地址信息的封装(也可用于IPv4)，以节约封装大小，节点A收到报文时需要将该信息(作为完整IP地址的主机段)与aggregation-prefix-A(作为完整IP地址的网络段)合并得到最终的与明细FEC对应的完整IP地址，Type＝2表示封装与明细FEC对应的MPLS标签信息，主要用于与明细FEC对应的MPLS标签被用作业务通告(如VPN路由通告)的属性的场景，Type＝3表示封装与明细FEC对应的prefix-sid信息，主要用于与明细FEC对应的prefix-sid被用作业务通告(如VPN路由通告)的属性的场景。
图4是根据本公开的实施例的报文封装格式。
如图4所示，采用类型2的封装形式对明细FEC进行封装。在类型2的报文封装中，取决于容器FEC是IPv4prefix还是IPv6prefix，与所封装的明细FEC相关的IP地址信息可以是一个IPv4地址(如图4中的(a)所示)或者IPv6地址(如图4中的(b)所示)，当IP地址是IPv6地址时，封装头中的类型区域可以设置为type＝1，在这种情况下，如果aggregation-prefix-A的prefix-length为96比特时，仅需要封装32比特的与明细FEC对应IPv6地址的主机段。另外，所封装的明细FEC信息也可以是MPLS标签(如图4中的(c)所示)，在这种情况下，该MPLS标签是节点A为该明细FEC分配的。另外，所封装的明细FEC信息也可以是prefix-sid(如图4中的(d)所示)。
根据本公开的实施例，所述方法还包括：将所述明细FEC的封装形式通告给所述其他节点。
根据本公开的实施例，所述通告的通告方式包括以下至少之一：对用于通告前缀类型FEC的标签绑定消息的MPLS标签协议 进行扩展，利用扩展后的MPLS标签协议进行通告；对用于通告前缀类型FEC的标签绑定消息的分段路由SR协议进行扩展，利用扩展后的SR协议进行通告。在上述实施例中，第一节点可以通过MPLS标签协议向邻居节点通告容器FEC的标签绑定消息，在通告消息中准确的设置所配置的封装形式类型。现有的能支持通告前缀类型FEC的标签绑定消息的MPLS标签协议(如LDP、BGP)以及SR路由协议(如ISIS、OSPF、BGP)等，均可扩展以支持容器FEC的标签绑定信息的通告。为了兼容旧设备，容器FEC的标签绑定信息的通告不能简单的在现有的FEC通告消息中增加容器标志的方式来支持，否则那些无法识别容器标志的节点可能在忽略了容器标志的情况下将容器标签当成正常的MPLS标签来对报文进行封装，使得报文的报文标签栈中封装的容器标签之后没有紧跟明细FEC信息，那么这样的报文到达节点A时，节点A总是认为容器标签之后紧跟有明细FEC信息，必然会导致报文解析错误。
根据本公开的实施例，当所述MPLS标签协议包括标签分发协议LDP协议时，对用于通告前缀类型FEC的标签绑定消息的LDP协议进行扩展包括：在征求修正意见书RFC5036的基础上，在所述LDP协议中增加容器标签类型-长度-值(Container Label TLV)；利用所述扩展后的LDP协议中的所述Container Label TLV进行通告。
下面结合附图5对本公开实施例进行说明。根据前述的兼容原则，图5中的a)是扩展LDP支持容器FEC的标签绑定信息通告的一种具体实施方式，是在RFC5036的基础上，新增一种Container Label TLV，与已有的Generic Label TLV完全类似，只不过TYPE取值为0x02ff，另外其中的Style字段可取值为1(见前述类型1)或2(见前述类型2)，其它字段的解释与Generic Label TLV完全相同。通过这种引入新的Container Label TLV而不是在现有的Generic Label TLV中扩展添加容器标志或者在现有的FEC TLV中扩展添加容器标志的具体实施方式，使得那些不识别 Container Label TLV的旧设备，将直接丢弃所接收到的容器FEC的标签绑定信息通告消息，而对那些能识别Container Label TLV的新设备则正常处理并安装表项。
根据本公开的实施例，当所述SR协议包括中间系统到中间系统ISIS协议时，对用于通告前缀类型FEC的标签绑定消息的ISIS协议进行扩展包括：在draft-ietf-isis-segment-routing-extensions-16的基础上，在所述ISIS协议中增加容器-前缀-段标识子-类型-长度-值Container-Prefix-SID Sub-TLV；利用所述扩展后的ISIS协议中的所述Container-Prefix-SID Sub-TLV进行通告。
类似的，图5中的b)是扩展ISIS支持容器FEC的标签绑定信息通告的一种具体实施方式，是在draft-ietf-isis-segment-routing-extensions-16的基础上，新增一种Container-Prefix-SID Sub-TLV，与已有的Prefix-SID Sub-TLV完全类似，只不过TYPE取值为15，在Flags字段中新增S-Flag标志位(可取值为0对应前述类型1或取值为1对应前述类型2)，注意此时Flags中已有的如下标志位的取值是固定的：N-Flag必须为0，P-Flag必须为1，E-Flag必须为0，其它字段的解释与Prefix-SID Sub-TLV完全相同。通过这种引入新的Container-Prefix-SID Sub-TLV而不是在现有的Prefix-SID Sub-TLV中扩展添加容器标志或者在现有的prefix通告(如TLV-135(Extended IPv4reachability)定义于RFC5305，或TLV-235(Multitopology IPv4Reachability)定义于RFC5120，或TLV-236(IPv6IP Reachability)定义于RFC5308，或TLV-237(Multitopology IPv6IP Reachability)定义于RFC5120)中扩展添加容器标志的具体实施方式，使得那些不识别Container-Prefix-SID Sub-TLV的旧设备，将直接丢弃所接收到的容器FEC的标签绑定信息通告消息，而对那些能识别Container-Prefix-SID Sub-TLV的新设备则正常处理并安装表项。
根据本公开的实施例，当所述SR协议包括边界网关协议BGP时，对用于通告前缀prefix类型FEC的标签绑定消息的BGP进行 扩展包括：在draft-ietf-idr-bgp-perfix-sid-20的基础上，在所述BGP中增加容器-标签-索引、类型-长度-值(Container-Label-Index TLV)，其中，所述Container-Label-Index TLV随BGP Prefix-SID属性携带；利用所述扩展后的BGP中的所述Container-Label-Index TLV进行通告。
类似的，图5中的c)是扩展SR-BGP支持容器FEC的标签绑定信息通告的一种具体实施方式，是在draft-ietf-idr-bgp-prefix-sid-20的基础上，新增一种Container-Label-Index TLV，随BGP Prefix-SID属性携带，与已有的Label-Index TLV完全类似，只不过TYPE取值为2，在Flags字段中新增S-Flag标志位(可取值为0对应前述类型1或取值为1对应前述类型2)，其它字段的解释与Label-Index TLV完全相同。通过这种引入新的Container-Label-Index TLV而不是在现有的Label-Index TLV中扩展添加容器标志或者在现有的prefix通告(如Labeled IPv4/IPv6unicast prefixes定义于RFC8277，简称BGP-LU路由)中扩展添加容器标志的具体实施方式，使得那些不识别Container-Label-Index TLV的旧设备，将直接丢弃所接收到的容器FEC的标签绑定信息通告消息，而对那些能识别Container-Label-Index TLV的新设备则正常处理并安装表项。
其它MPLS标签协议(如BGP)以及SR路由协议(如OSPF)的扩展也按此兼容原则，不再赘述。
根据本公开的实施例，所述第一ILM表项中标签操作为弹出(POP)。
前述实施例是从报文发送侧描述的，下面从报文接收侧进行进一步描述。
在报文接收侧，所述方法包括：第二节点在收到第二报文后，可以继续为所述第一容器FEC重新分配MPLS标签并创建相应的ILM表项，表项中打上容器标志，标签操作为SWAP(交换)。第二节点还可以为该容器FEC创建相应的FTN表项，表项中打上容器标志。因此，在报文命中此FTN表项情况下，除了在报文标 签栈中封装该FTN给出的容器标签以外，还在报文标签栈中还紧随该容器标签之后封装关于明细FEC的信息。首先需要说明的是，在第二节点侧接收的报文对应于第二报文，创建的ILM表项对应于第二ILM表项，创建的FTN表项对应于第二FTN表项。
本公开的实施例中还提供了一种绑定关系的通告方法，图6是根据本公开的实施例的绑定关系的通告方法的流程图，如图6所示，该流程包括步骤S602。
步骤S602，在第二节点上接收由第一节点通告的绑定关系，其中，所述第一节点为进行了路由聚合的节点，所述绑定关系为容器标签与第一容器FEC之间的绑定关系，所述容器标签是所述第一节点中预先为所述第一容器FEC分配的，所述第一容器FEC是对所述第一节点上聚合的路由进行配置后得到的携带容器标志的FEC，所述容器标志用于标识所述第一容器FEC为容器FEC类型。
需要说明的是，在前述的实施例中，涉及到了将绑定关系通告给除第一节点之外的其他节点，本公开实施例中的第二节点可以是前述的实施例中的其他节点中的一个节点。后续的实施例是对第二节点接收到上述绑定关系之后的动作进行的进一步描述。
根据本公开的实施例，在第二节点上接收由所述第一节点通告的绑定关系之后，所述方法还包括以下至少之一：当所述第二节点为所述第一容器FEC的传输节点时，为所述第一容器FEC分配新的容器标签，然后继续向上游节点通告所述新的容器标签与所述第一容器FEC之间的绑定关系，并创建与所述第一容器FEC对应的第二ILM表项，其中，所述第二ILM表项中携带所述容器标志；当所述第二节点为所述第一容器FEC的入口节点时，为所述第一容器FEC创建对应的第二FTN表项，其中，所述第二FTN表项中携带所述容器标志。
根据本公开的实施例，在创建与所述第一容器FEC对应的第二ILM表项之后，所述方法还包括：在接收到的报文与所述第二ILM表项匹配的情况下，根据位于所述报文的顶层的容器标签执 行标签交换操作，忽略所述报文的容器标签之后的关于明细FEC的信息；或者，在接收到的报文与所述第二ILM表项匹配，且位于所述报文的顶层容器标签的生存时间值(TTL)超时的情况下，将所述报文上送到控制平面进行处理，其中，所述报文中的容器标签之后的关于明细FEC信息不为标签。
根据本公开的实施例，在为所述第一容器FEC创建对应的第二FTN表项之后，所述方法还包括：在接收到的报文与所述第二FTN表项匹配的情况下，为所述数据报文封装所述第二FTN表项中的容器标签，以及在所述容器标签之后封装关于明细FEC的信息，其中，所述容器标签和所述关于明细FEC的信息构成一个整体。
在上述实施例中，第二节点在收到容器FEC的标签绑定消息后，第二节点可作为该容器FEC的传输节点，可以继续为该容器FEC分配MPLS标签并创建相应的ILM表项，表项中打上容器标志，标签操作为SWAP(交换)。命中此ILM表项的MPLS报文，一般仅根据位于报文的顶层的容器标签做标签交换，对报文中紧随容器标签之后的关于明细FEC的信息不进行感知和解析。有些特殊的场景(如tracerout)，第二节点可能收到MPLS报文发现位于顶层的容器标签的TTL超时，在按照RFC8029做FEC校验和标签校验时，容器标签后紧随的关于明细FEC的信息应该要被忽略，不能误当成标签影响校验结果。第二节点还可以作为该容器FEC的入口(ingress)节点，为该容器FEC创建相应的FTN表项(记为FTN-aggregation)，表项中打上容器标志，则命中此FTN表项的报文除了封装容器标签以外，还紧随容器标签之后封装关于明细FEC的信息。注意紧随容器标签之后封装的明细FEC信息本身不能被当成标签，而是与容器标签作为一个整体，它不影响报文中的容器标签的EXP、TTL、S设置。在本公开实施例中，第二节点甚至可以进一步将路由聚合，比如进一步聚合后的路由为aggregation-prefix-B，类似第一节点一样将aggregation-prefix-B配置为容器FEC并建立相应的ILM表项，表项中打上容器标志， 标签操作为POP，那么命中此ILM表项的报文将根据报文标签栈中的容器标签之后紧随的明细FEC信息查询FTN表项，在查询到FTN表项时(即，上述FTN-aggregation表项)，将报文的标签与FTN-aggregation表项的出标签进行标签交换操作，报文继续沿FTN-aggregation对应的LSP转发(注意由于查询到的FTN-aggregation表项中有容器标志，则转发时报文标签栈中原来容器标签之后紧随的明细FEC信息要保留)，如果查询不到FTN表项，则根据容器标签的栈底标志是否有效决定报文是继续沿IP转发(栈底标志有效时，此时将移除报文标签栈中的容器标签及其后紧随的明细FEC信息，并根据IP载荷查路由表转发)还是丢弃(栈底标志无效时)。
根据本公开的实施例，所述方法还包括：在第二节点上接收由所述第一节点通告的封装形式，其中，所述封装形式为所述第一节点中的报文标签栈中的容器标签之后封装的所述关于明细FEC的信息的封装形式。同样地，在前述的实施例中，涉及到了将所述封装形式通告给除第一节点之外的其他节点，本公开实施例中的第二节点可以是前述的实施例中的其他节点中的一个节点。
根据本公开的实施例，所述封装形式包括以下至少之一：直接封装所述明细FEC的IP地址信息的封装形式；利用封装头封装以下信息至少之一的封装形式：所述明细FEC的IP地址信息、MPLS标签信息、段标识SID信息，其中所述IP地址信息包括以下之一：完整的IP地址信息、仅包括IP地址的主机段信息。
下面结合具体实施例对本公开进行说明。
如图7所示的网络，包括接入、汇聚、核心域，每个域均部署单独的IGP(如ISIS)进程，路由聚合后在IGP进程之间重分发。图7中AN表示接入节点(Access Node)，AGN表示汇聚节点(Aggregation Node)，LSR(Label Switching Router)表示核心节点。比如AN2的loopback地址为200.2.2.2，AGN2上会通过IGP5进程学习到明细的路由200.2.2.2/32，同时也向IGP4进程重分发聚合路由200.2.2.0/24；LSR2通过IGP4进程学习到路由 200.2.2.0/24，同时也向IGP3进程重分发聚合路由200.2.0.0/16；LSR1通过IGP3进程学习到路由200.2.0.0/16，同时也向IGP2进程重分发聚合路由200.0.0.0/8；AGN1通过IGP2进程学习到路由200.0.0.0/8，同时也向IGP1进程重分发聚合路由0.0.0.0/0(默认路由)。全网使能LDP。根据本公开的实施例报文发送方法包括以下步骤701到步骤706。
在步骤701，在重分发聚合路由的节点上，均可以将所重分发的聚合路由配置为容器FEC且将明细FEC封装样式配置为Style-1，并将容器FEC同步给LDP协议，LDP将为相应的容器FEC分配MPLS标签并向邻居通告相应的容器FEC和向其分配的MPLS标签的绑定关系(使用Container Label TLV)以及产生ILM表项。
例如，在AGN2上将生成容器FEC(IPv4 prefix 200.2.2.0/24)及相应的ILM表项(记为ILM-5)，ILM表项中标签操作为POP且包含容器标志、Style-1标志、IPv4标志。在AGN2上也为明细FEC(IPv4 prefix 200.2.2.2/32)维护相应的FTN表项(记为FTN-5)，FTN表项中不包含容器标志。
LSR2上将生成容器FEC(IPv4 prefix 200.2.0.0/16)及相应的ILM表项(记为ILM-4)，ILM表项中标签操作为POP且包含容器标志、Style-1标志、IPv4标志。LSR2上也为明细FEC(IPv4 prefix 200.2.2.0/24)维护相应的FTN表项(记为FTN-4)，FTN表项中包含容器标志、Style-1标志。
LSR1上将生成容器FEC(IPv4 prefix 200.0.0.0/8)及相应的ILM表项(记为ILM-3)，ILM表项中标签操作为POP且包含容器标志、Style-1标志、IPv4标志。LSR1上也为明细FEC(IPv4 prefix 200.2.0.0/16)维护相应的FTN表项(记为FTN-3)，FTN表项中包含容器标志、Style-1标志。
AGN1上将生成容器FEC(IPv4 prefix 0.0.0.0/0)及相应的ILM表项(记为ILM-2)，ILM表项中标签操作为POP且包含容器标志、Style-1标志、IPv4标志。AGN1上也为明细FEC(IPv4 prefix  200.0.0.0/8)维护相应的FTN表项(记为FTN-2)，FTN表项中包含container标志、Style-1标志。
AN1上将为明细FEC(IPv4 prefix 0.0.0.0/0)维护相应的FTN表项(记为FTN-1)，FTN表项中包含容器标志、Style-1标志。
步骤702，假设AN1上需要始发一份目的IP为AN2(200.2.2.2)的IPv4报文(这可能是PING报文、BGP协议报文等)，则报文将匹配到上述FTN-1表项，由于FTN-1表项中包含容器标志、Style-1标志，则在IPv4报文中封装FTN-1表项中给出的标签(并将该标签的栈底标记设置为1)，同时紧随标签之后封装明细FEC信息(200.2.2.2)，报文向AGN1转发。
在步骤703，AGN1收到报文后，接收到的报文的标签将命中上述ILM-2表项，ILM-2表项中标签操作为POP且包含容器标志、Style-1标志、IPv4标志，则将位于报文的顶层的标签及其紧随的明细FEC信息(200.2.2.2)剥除，然后基于明细FEC信息(200.2.2.2)继续查找相应FTN表项，确定报文将匹配到上述FTN-2表项，由于FTN-2表项中包含容器标志、Style-1标志，则在IPv4报文中封装FTN-2表项中给出的标签(并将该标签的栈底标记设置为1)，同时紧随标签之后封装明细FEC信息(200.2.2.2)，报文向LSR1转发。
在步骤704，类似的，LSR1收到报文后，接收到的报文的标签将命中上述ILM-3表项，同样将位于报文的顶层的标签及其紧随的明细FEC信息(200.2.2.2)剥除，然后基于明细FEC信息(200.2.2.2)继续查找并匹配到上述FTN-3表项，最终在IPv4报文中封装FTN-3表项中给出的标签(并将该标签的栈底标记设置为1)，同时紧随标签之后封装明细FEC信息(200.2.2.2)，报文向LSR2转发。
在步骤705，类似的，LSR2收到报文后，接收到的报文的标签将命中上述ILM-4表项，同样将位于报文的顶层的标签及其紧随的明细FEC信息(200.2.2.2)剥除，然后基于明细FEC信息(200.2.2.2)继续查找并匹配到上述FTN-4表项，最终在IPv4报 文中封装FTN-4表项中给出的标签(并将该标签的栈底标记设置为1)，同时紧随标签之后封装明细FEC信息(200.2.2.2)，报文向AGN2转发。
在步骤706，类似的，AGN2收到报文后，接收到的报文的标签将命中上述ILM-5表项，同样将位于报文的顶层的标签及其紧随的明细FEC信息(200.2.2.2)剥除，然后基于明细FEC信息(200.2.2.2)继续查找并匹配到上述FTN-5表项，确定报文将匹配到上述FTN-5表项，由于FTN-5表项中不包含容器标志，则在IPv4报文中封装FTN-5表项中给出的标签(并将该标签的栈底标记设置为1)后，不再紧随标签之后封装明细FEC信息(200.2.2.2)，报文向AN2转发。
至此，形成了一条从AN1至AN2沿途全程采用标签交换的路径，IPv4载荷全程未暴露，且针对AN2的明细FEC无须随LDP协议全程通告。如果该标签交换路径需要承载其它MPLS载荷，比如VPN标签，流程与上述是类似的，在AN1节点上可以为报文封装VPN标签(其栈底标记为1)后继续根据BGP next-hop(AN2)迭代到上述FTN-1表项，继续为报文封装容器标签(其栈底标记为0)及其紧随的明细FEC信息(200.2.2.2)，具体不再赘述。
除了LDP之外，也可以采用SR-ISIS实现从AN1到AN2的报文发送。具体过程包括以下步骤1和步骤2。
在步骤1，在重分发聚合路由的节点上，均可以将所重分发的聚合路由配置为容器FEC，且将明细FEC封装样式配置为Style-1，从而IGP将为相应的聚合路由分配prefix-sid并向邻居通告(使用Container-Prefix-SID Sub-TLV)以及产生ILM表项。各节点上生成的FTN、ILM表项与如上所述采用LDP的报文发送过程基本相同。
在步骤2，假设AN1上需要始发一份目的IP为AN2(200.2.2.2)的IPv4报文，则报文将匹配到上述FTN-1表项，报文的后续转发流程与如上所述采用LDP的报文发送过程基本相同。
至此，形成了一条从AN1至AN2沿途全程采用标签交换的 路径，IPv4载荷全程未暴露，且针对AN2的明细路由无须全程泛洪。
如图8所示的网络，包括接入、汇聚、核心域，每个域均部署单独的IGP(如ISIS)进程，但相互不泄露IGP路由。图8中AN、AGN、LSR节点的解释与图7所示的网络基本相同。另外，ABR表示汇聚域与核心域的边界节点(Area Border Router)。在现有的无痕(seamlesss)MPLS方案中，一般会在边界节点之间建立BGP会话通告BGP-LU明细路由，比如ABR1通过BGP-LU向AGN1通告LSR1的明细路由，AGN1进而也通过BGP-LU继续向AN1通告。而采用根据本公开的报文发送方法，ABR1只需通过BGP-LU向AGN1通告汇聚所有LSR的路由，AGN1也只需要通过BGP-LU向AN1通告默认路由(0.0.0.0/0)。比如LSR1的loopback地址为100.1.1.1，在ABR1上会通过IGP3进程学习到明细的路由100.1.1.1/32，同时也通过BGP-LU向AGN1重分发聚合路由100.1.0.0/16，AGN1继续通过BGP-LU向AN1重分发默认路由(0.0.0.0/0)。全网边界节点使能SR-BGP，各IGP域内节点使能SR-ISIS。根据本公开的实施例的报文发送方法包括以下步骤801到步骤804。
步骤801，在重分发聚合路由的节点上，均可以将所重分发的聚合路由配置为容器FEC且将明细FEC封装样式配置为Style-2，则BGP将为相应的聚合路由分配prefix-sid并向邻居通告(使用Container-Label-Index TLV)以及产生ILM表项。
例如，ABR1上将生成容器FEC(IPv4 prefix 100.1.0.0/16)及相应的ILM表项(记为ILM-3)，ILM表项中标签操作为POP且包含容器标志、Style-2标志、IPv4标志。ABR1上也为明细FEC(IPv4 prefix 100.1.1.1/32)维护相应的FTN表项(记为FTN-3)，FTN表项中不包含容器标志。
AGN1上将生成容器FEC(IPv4 prefix 0.0.0.0/0)及相应的ILM表项(记为ILM-2)，ILM表项中标签操作为POP且包含容器标志、Style-2标志、IPv4标志。AGN1上也为FEC(IPv4 prefix  100.1.0.0/16)维护相应的FTN表项(记为FTN-2)，FTN表项中包含容器标志、Style-2标志。
AN1上将为FEC(IPv4 prefix 0.0.0.0/0)维护相应的FTN表项(记为FTN-1)，FTN表项中包含容器标志、Style-2标志。
在步骤802，假设AN1上需要始发一份目的IP为LSR1(100.1.1.1)的IPv4报文，则报文将匹配到上述FTN-1表项，由于FTN-1表项中包含容器标志、Style-2标志，在IPv4报文中封装FTN-1表项中给出的标签(并将该标签的栈底标记设置为1)，同时紧随标签之后封装container_header(其中Type可设置为1，container_header内再封装明细FEC信息的主机段信息100.1.1.1，这是由于100.1.1.1匹配的默认路由0.0.0.0/0的前缀长度为0，所以整个100.1.1.1都可被认为是主机段。注意Type也可设置为0、2、3等其它值，这是AN1的本地行为)，在继续封装外层SR-ISIS LSP的标签后，将报文向AGN1转发。
在步骤803，AGN1收到报文后，报文的标签将命中上述ILM-2表项，ILM-2表项中标签操作为POP且包含容器标志、Style-2标志、IPv4标志，将位于报文的顶层的标签及其紧随的container_header及其所封装的明细FEC信息剥除，然后基于明细FEC信息(100.1.1.1，这是将ILM-2的FEC 0.0.0.0/0的网络段与100.1.1.1相或得到的)继续查找相应FTN表项，确定报文将匹配到上述FTN-2表项，由于FTN-2表项中包含容器标志、Style-2标志，在IPv4报文中封装FTN-2表项中给出的标签(并将该标签的栈底标记设置为1)，同时紧随标签之后封装container_header(其中Type可设置为1，container_header内再封装明细FEC信息的主机段信息0.0.1.1，这是由于100.1.1.1匹配的路由100.1.0.0/16的前缀长度为16，所以主机段为100.1.1.1的后16比特即0.0.1.1。注意Type也可设置为0、2、3等其它值，这是AGN1的本地行为)，在继续封装外层SR-ISIS LSP的标签后，将报文向ABR1转发。
在步骤804，类似的，ABR1收到报文后，报文的标签将命中上述ILM-3表项，同样将位于报文的顶层的标签及其紧随的 container_header及其所封装的明细FEC信息剥除，然后基于明细FEC信息(100.1.1.1，这是将ILM-3的FEC 100.1.0.0/16的网络段与0.0.1.1相或得到的)继续查找并匹配到上述FTN-3表项，由于FTN-3表项中不包含容器标志，则在IPv4报文中封装FTN-3表项中给出的标签(并将该标签的栈底标记设置为1)后，不再紧随标签之后封装contaner_header，并在继续封装外层SR-ISIS LSP的标签后，将报文向LSR1转发。
至此，形成了一条从AN1至LSR1沿途全程采用标签交换的路径，IPv4载荷全程未暴露，且针对LSR1的明细FEC无须随BGP协议全程通告。另外，从上可知Style-2的有益效果是能更灵活的封装明细FEC信息，特别是container_header中Type设置为1时只需要封装明细FEC完整IP地址的主机段信息，节约了报文封装开销。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件、硬件或它们的组合的方式来实现。软件可以存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
在本公开实施例中还提供了一种报文的发送装置和报文的接收装置，该装置用于实现上述实施例，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。以下实施例所描述的装置可以以软件、硬件或者软件和硬件的组合来实现。
图9是根据本公开的实施例的报文的发送装置的结构框图。如图9所示，该装置包括第一接收模块92、交换模块94和转发模块96。
第一接收模块92，设置为在进行了路由聚合的第一节点上接收第一报文。交换模块94，设置为在所述第一报文与预先在所述第一节点上设置的第一ILM表项匹配的情况下，将所述第一报文 的标签交换为与明细FEC对应的出标签，得到第二报文。转发模块96，设置为按照与所述明细FEC对应的LSP将所述第二报文转发给下游节点。
根据本公开的实施例，所述装置还包括以下至少之一：配置模块，设置为在由第一接收模块92在进行了路由聚合的第一节点上接收第一报文之前，在所述第一节点上将聚合的路由配置为第一容器FEC，其中，所述第一容器FEC携带容器标志，所述容器标志用于标识所述第一容器FEC为容器FEC类型；创建模块，设置为在由第一接收模块92在进行了路由聚合的第一节点上接收第一报文之前，为所述第一容器FEC创建所述第一ILM表项，其中，所述第一ILM表项中携带所述容器标志。
根据本公开的实施例，所述交换模块94具体用于：在第一报文与所述第一ILM表项匹配的情况下，根据报文标签栈中的容器标签之后的封装信息来查询与所述明细FEC对应的出标签，将所述报文标签栈中的容器标签交换为与查询出的与所述明细FEC对应的出标签。其中，所述报文标签栈为在处于所述第一节点的上游的节点上预先生成的标签栈，所述容器标签为与所述第一容器FEC具有绑定关系的MPLS标签，所述封装信息为在报文标签栈中在所述容器标签之后封装的关于明细FEC的信息。
根据本公开的实施例，所述装置还用于在根据报文标签栈中的容器标签之后的封装信息查询出与所述明细FEC对应的出标签之前，配置所述绑定关系。
根据本公开的实施例，所述装置还用于在配置所述绑定关系之后：将所述绑定关系通告给除所述第一节点之外的其他节点。
根据本公开的实施例，所述交换模块94可以通过如下方式查询出与所述明细FEC对应的出标签：根据所述报文标签栈中的所述容器标签之后的封装信息查询与所述明细FEC对应的第一FTN表项；在查询到所述第一FTN表项的情况下，确定所述第一FTN表项中的出标签为与所述明细FEC对应的出标签。
根据本公开的实施例，所述装置还用于在根据所述报文标签 栈中所述容器标签之后的封装信息查询与所述明细FEC对应的第一FTN表项之后，执行以下操作至少之一：在未查询到所述第一FTN表项的情况下，且在确定报文标签栈中的所述容器标签的栈底标志有效的情况下，移除所述报文标签栈中的所述容器标签及之后的封装信息，根据互联网协议(IP)载荷查询路由表，并根据所述路由表转发所述第一报文；在未查询到所述第一FTN表项的情况下，且在确定报文标签栈中的所述容器标签的栈底标志无效时，丢弃所述第一报文。
根据本公开的实施例，，所述装置还用于在根据所述报文标签栈中的所述容器标签之后的封装信息查询到与所述明细FEC对应的第一FTN表项之前，维护与所述第一节点的前一节点生成的第一FEC对应的所述第一FTN表项，其中，所述第一节点的前一节点包括原始产生所述第一FEC的节点。
根据本公开的实施例，，当所述第一节点的前一节点生成的第一FEC的类型不为容器FEC时，所述第一FTN表项不包括所述容器标志；当所述第一节点的前一节点生成的第一FEC的类型为容器FEC时，所述第一FTN表项包括所述容器标志。
根据本公开的实施例，所述第一FTN表项中不包括所述容器标志时，将所述报文标签栈中的容器标签交换为所述第一FTN表项中的出标签，且移除所述报文标签栈中的容器标签之后封装的关于明细FEC的信息；当所述第一FTN表项中包括所述容器标志时，将所述报文标签栈中的容器标签交换为所述第一FTN表项中的出标签，且保留所述报文标签栈中的容器标签之后封装的关于明细FEC的信息。
根据本公开的实施例，所述封装信息的封装形式包括以下至少之一：直接封装所述明细FEC的IP地址信息的封装形式；利用封装头封装以下信息至少之一的封装形式：所述明细FEC的IP地址信息、MPLS标签信息、段标识SID信息，其中，所述IP地址信息包括以下之一：完整的IP地址信息、仅包括IP地址的主机段信息。
根据本公开的实施例，所述装置还用于将所述明细FEC的封装形式通告给所述其他节点。
根据本公开的实施例，所述装置通告方式包括以下至少之一：对用于通告前缀类型FEC的标签绑定消息的MPLS标签协议进行扩展，利用扩展后的MPLS标签协议进行通告；对用于通告前缀类型FEC的标签绑定消息的分段路由SR协议进行扩展，利用扩展后的SR协议进行通告。
根据本公开的实施例，当所述MPLS标签协议包括标签分发协议LDP协议时，所述装置通过如下方式对用于通告前缀类型FEC的标签绑定消息的LDP协议进行扩展：在征求修正意见书RFC5036的基础上，在所述LDP协议中增加容器标签类型-长度-值(Container Label TLV)；利用所述扩展后的LDP协议中的所述Container Label TLV进行通告。
根据本公开的实施例，当所述SR协议包括中间系统到中间系统ISIS协议时，所述装置通过如下方式对用于通告前缀类型FEC的标签绑定消息的ISIS协议进行扩展：在draft-ietf-isis-segment-routing-extensions-16的基础上，在所述ISIS协议中增加容器-前缀-段标识子-类型-长度-值Container-Prefix-SID Sub-TLV；利用所述扩展后的ISIS协议中的所述Container-Prefix-SID Sub-TLV进行通告。
根据本公开的实施例，当所述SR协议包括边界网关协议BGP时，所述装置用于通过如下方式对用于通告前缀prefix类型FEC的标签绑定消息的BGP进行扩展：在draft-ietf-idr-bgp-perfix-sid-20的基础上，在所述BGP中增加容器-标签-索引、类型-长度-值(Container-Label-Index TLV)，其中，所述Container-Label-Index TLV随BGP Prefix-SID属性携带；利用所述扩展后的BGP中的所述Container-Label-Index TLV进行通告。
根据本公开的实施例，所述第一ILM表项中标签操作为弹出(POP)。
图10是根据本公开的实施例的绑定关系的通告装置的结构框图，如图10所示，该装置包括第二接收模块102。
第二接收模块102，设置为在第二节点上接收由第一节点通告的绑定关系，其中，所述第一节点为进行了路由聚合的节点，所述绑定关系为容器标签与第一容器FEC之间的绑定关系，所述容器标签是所述第一节点中预先为所述第一容器FEC分配的，所述第一容器FEC是对所述第一节点上聚合的路由进行配置后得到的携带容器标志的FEC，所述容器标志用于标识所述第一容器FEC为容器FEC类型。
根据本公开的实施例，所述装置还包括：分配模块，设置为在第二节点上接收由所述第一节点通告的绑定关系之后，执行以下操作至少之一：当所述第二节点为所述第一容器FEC的传输节点时，为所述第一容器FEC分配新的容器标签，然后继续向上游节点通告所述新的容器标签与所述第一容器FEC之间的绑定关系，并创建与所述第一容器FEC对应的第二ILM表项，其中，所述第二ILM表项中携带所述容器标志；当所述第二节点为所述第一容器FEC的入口节点时，为所述第一容器FEC创建对应的第二FTN表项，其中，所述第二FTN表项中携带所述容器标志。
根据本公开的实施例，所述装置还包括：第一处理模块，设置为在创建与所述第一容器FEC对应的第二ILM表项之后，执行以下操作之一：在接收到的报文与所述第二ILM表项匹配的情况下，根据位于所述报文的顶层的容器标签执行标签交换操作，忽略所述报文的容器标签之后的关于明细FEC的信息；或者，在接收到的报文与所述第二ILM表项匹配，且位于所述报文的顶层的容器标签的生存时间值(TTL)超时的情况下，将所述报文上送到控制平面进行处理，其中，所述报文中的容器标签之后的明细FEC信息不为标签。
根据本公开的实施例，所述装置还包括：第二处理模块，设置为在为所述第一容器FEC创建对应的第二FTN表项之后，在接收到的报文与所述第二FTN表项匹配的情况下，为所述数据报文 封装所述第二FTN表项中的容器标签，以及在所述容器标签之后封装关于明细FEC的信息，其中，所述容器标签和所述关于明细FEC的信息构成一个整体。
根据本公开的实施例，所述第二ILM表项中标签操作为交换(SWAP)。
根据本公开的实施例，所述装置还用于在第二节点上接收由所述第一节点通告的封装形式，其中，所述封装形式为所述第一节点中的报文标签栈中的容器标签之后封装的所述关于明细FEC的信息的封装形式。
根据本公开的实施例，所述封装形式包括以下至少之一：直接封装所述明细FEC的IP地址信息的封装形式；利用封装头封装以下信息至少之一的封装形式：所述明细FEC的IP地址信息、MPLS标签信息、段标识SID信息，其中，所述IP地址信息包括以下之一：完整的IP地址信息、仅包括IP地址的主机段信息。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本公开的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被处理器执行时执行根据本公开的实施例的报文的发送方法。
在本公开实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM)、随机存取存储器(RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，其包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行根据本公开的实施例的报文的发送方法。
上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
采用本公开所述方法，不需要配置复杂的策略控制明细FEC通告以建立端到端的MPLS LSP，只需简单的随路由聚合建立端到端的MPLS LSP。
本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上实施例不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (25)

  1. 一种报文的发送方法，包括：
    在进行了路由聚合的第一节点上接收第一报文；
    在所述第一报文与预先在所述第一节点上设置的第一入标签映射(ILM)表项匹配的情况下，将所述第一报文的标签交换为与明细转发等价类(FEC)对应的出标签，得到第二报文；以及
    按照与所述明细FEC对应的标签转发路径(LSP)将所述第二报文转发给下游节点。
  2. 根据权利要求1所述的方法，其中，在进行了路由聚合的第一节点上接收第一报文之前，所述方法还包括：
    在所述第一节点上将聚合的路由配置为第一容器FEC，其中，所述第一容器FEC携带容器标志，所述容器标志用于标识所述第一容器FEC为容器FEC类型；以及
    为所述第一容器FEC创建所述第一ILM表项，其中，所述第一ILM表项中携带所述容器标志。
  3. 根据权利要求2所述的方法，其中，将所述第一报文的标签交换为与明细FEC对应的出标签包括：
    根据报文标签栈中的容器标签之后的封装信息来查询与所述明细FEC对应的出标签，其中，所述报文标签栈为在处于所述第一节点的上游的节点上生成的标签栈，所述容器标签为与所述第一容器FEC具有绑定关系的多协议标签交换(MPLS)标签，所述封装信息为在所述报文标签栈中在所述容器标签之后封装的关于所述明细FEC的信息；以及
    将所述报文标签栈中的所述容器标签交换为与查询出的所述明细FEC对应的出标签。
  4. 根据权利要求3所述的方法，其中，在根据所述报文标签 栈中的所述容器标签之后的所述封装信息查询出与所述明细FEC对应的出标签之前，所述方法还包括：
    配置所述绑定关系。
  5. 根据权利要求4所述的方法，其中，在配置所述绑定关系之后，所述方法还包括：
    将所述绑定关系通告给除所述第一节点之外的其他节点。
  6. 根据权利要求3所述的方法，其中，根据所述报文标签栈中的所述容器标签之后的所述封装信息查询与所述明细FEC对应的出标签包括：
    根据所述报文标签栈中的所述容器标签之后的所述封装信息查询与所述明细FEC对应的第一FEC至下一跳标签转发单元映射(FTN)表项；以及
    在查询到所述第一FTN表项的情况下，确定所述第一FTN表项中的出标签为与所述明细FEC对应的出标签。
  7. 根据权利要求6所述的方法，其中，在根据所述报文标签栈中的所述容器标签之后的所述封装信息查询与所述明细FEC对应的第一FTN表项之后，所述方法还包括以下至少之一：
    在未查询到所述第一FTN表项的情况下，且在确定所述报文标签栈中的所述容器标签的栈底标志有效的情况下，移除所述报文标签栈中的所述容器标签及所述容器标签之后的所述封装信息，根据互联网协议(IP)载荷查询路由表，并根据所述路由表转发所述第一报文；以及
    在未查询到所述第一FTN表项的情况下，且在确定所述报文标签栈中的所述容器标签的栈底标志无效时，丢弃所述第一报文。
  8. 根据权利要求6所述的方法，其中，在根据所述报文标签栈中所述容器标签之后的所述封装信息查询到与所述明细FEC对 应的所述第一FTN表项之前，所述方法还包括：
    维护与所述第一节点的前一节点生成的所述第一FEC对应的所述第一FTN表项，其中，所述第一节点的前一节点包括原始产生所述第一FEC的节点。
  9. 根据权利要求8所述的方法，还包括以下至少之一：
    当所述第一节点的前一节点生成的所述第一FEC的类型不为容器FEC时，所述第一FTN表项不包括所述容器标志；以及
    当所述第一节点的前一节点生成的所述第一FEC的类型为容器FEC时，所述第一FTN表项包括所述容器标志。
  10. 根据权利要求9所述的方法，还包括以下至少之一：
    当所述第一FTN表项中不包括所述容器标志时，将所述报文标签栈中的容器标签交换为所述第一FTN表项中的出标签，且移除所述报文标签栈中的所述第一报文中的所述容器标签之后的所述封装信息；以及
    当所述第一FTN表项中包括所述容器标志时，将所述报文标签栈中的所述容器标签交换为所述第一FTN表项中的出标签，且保留所述报文标签栈中的所述容器标签之后的所述封装信息。
  11. 根据权利要求6所述的方法，其中，所述封装信息的封装形式包括以下至少之一：
    直接封装所述明细FEC的IP地址信息的封装形式；以及
    利用封装头封装以下信息至少之一的封装形式：所述明细FEC的IP地址信息、MPLS标签信息、段标识SID信息，
    其中，所述IP地址信息包括以下之一：完整的IP地址信息、仅包括IP地址的主机段信息。
  12. 根据权利要求11所述的方法，还包括：
    将所述封装信息的封装形式通告给除所述第一节点之外的其 他节点。
  13. 根据权利要求5或12所述的方法，其中，所述通告的通告方式包括以下至少之一：
    对用于通告前缀类型FEC的标签绑定消息的MPLS标签协议进行扩展，利用扩展后的MPLS标签协议进行通告；以及
    对用于通告前缀类型FEC的标签绑定消息的分段路由SR协议进行扩展，利用扩展后的SR协议进行通告。
  14. 根据权利要求1所述的方法，其中，所述第一ILM表项中标签操作为弹出(POP)。
  15. 一种绑定关系的通告方法，包括：
    在第二节点上接收由第一节点通告的绑定关系，其中，所述第一节点为进行了路由聚合的节点，所述绑定关系为容器标签与第一容器FEC之间的绑定关系，所述容器标签是所述第一节点中预先为所述第一容器FEC分配的，所述第一容器FEC是对所述第一节点上聚合的路由进行配置后得到的携带容器标志的FEC，所述容器标志用于标识所述第一容器FEC为容器FEC类型。
  16. 根据权利要求15所述的方法，其中，在第二节点上接收由所述第一节点通告的绑定关系之后，所述方法还包括以下至少之一：
    当所述第二节点为所述第一容器FEC的传输节点时，为所述第一容器FEC分配新的容器标签然后继续向上游节点通告所述新的容器标签与所述第一容器FEC之间的绑定关系，并创建与所述第一容器FEC对应的第二ILM表项，其中，所述第二ILM表项中携带所述容器标志；以及
    当所述第二节点为所述第一容器FEC的入口节点时，为所述第一容器FEC创建对应的第二FTN表项，其中，所述第二FTN 表项中携带所述容器标志。
  17. 根据权利要求16所述的方法，其中，在创建与所述第一容器FEC对应的第二ILM表项之后，所述方法还包括：
    在接收到的报文与所述第二ILM表项匹配的情况下，根据位于所述报文的顶层的容器标签执行标签交换操作，忽略所述报文的容器标签之后的关于明细FEC的信息；或者，
    在接收到的报文与所述第二ILM表项匹配，且位于所述报文的顶层的容器标签的生存时间值(TTL)超时的情况下，将所述报文上送到控制平面进行处理，其中，所述报文中的容器标签之后的关于明细FEC的信息不为标签。
  18. 根据权利要求16所述的方法，其中，在为所述第一容器FEC创建对应的第二FTN表项之后，所述方法还包括：
    在接收到的报文与所述第二FTN表项匹配的情况下，为所述报文封装所述第二FTN表项中的容器标签，以及在所述容器标签之后封装关于明细FEC的信息，其中，所述容器标签和所述关于明细FEC的信息构成一个整体。
  19. 根据权利要求16所述的方法，其中，所述第二ILM表项中的标签操作为交换SWAP。
  20. 根据权利要求15所述的方法，还包括：
    在所述第二节点上接收由所述第一节点通告的封装形式，其中，所述封装形式为所述第一节点中的报文标签栈中的容器标签之后封装的所述关于明细FEC的信息的封装形式。
  21. 根据权利要求20所述的方法，其中于，所述封装形式包括以下至少之一：
    直接封装所述明细FEC的IP地址信息的封装形式；以及
    利用封装头封装以下信息至少之一的封装形式：所述明细FEC的IP地址信息、MPLS标签信息、段标识SID信息，
    其中，所述IP地址信息包括以下之一：完整的IP地址信息、仅包括IP地址的主机段信息。
  22. 一种报文的发送装置，包括：
    第一接收模块，设置为在进行了路由聚合的第一节点上接收第一报文；
    交换模块，设置为在所述第一报文与预先在所述第一节点上设置的第一入标签映射(ILM)表项匹配的情况下，将所述第一报文的标签交换为明细转发等价类(FEC)对应的出标签，得到第二报文；以及
    转发模块，设置为按照与所述明细FEC对应的标签转发路径(LSP)将所述第二报文转发给下游节点。
  23. 一种绑定关系的通告装置，包括：
    第二接收模块，设置为在第二节点上接收由第一节点通告的绑定关系，其中，所述第一节点为进行了路由聚合的节点，所述绑定关系为容器标签与第一容器FEC之间的绑定关系，所述容器标签是所述第一节点中预先为所述第一容器FEC分配的，所述第一容器FEC是对所述第一节点上聚合的路由进行配置后得到的携带容器标志的FEC，所述容器标志用于标识所述第一容器FEC为容器FEC类型。
  24. 一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时，使得所述处理器执行根据权利要求1至14任一项中所述的方法，或者执行根据权利要求15至21任一项中所述的方法。
  25. 一种电子装置，其包括存储器和处理器，其中，所述存储 器中存储有能够由所述处理器执行的计算机程序，所述计算机程序被所述处理器执行时，使所述处理器执行根据权利要求1至14任一项中所述的方法，或者执行根据权利要求15至21任一项中所述的方法。
PCT/CN2019/105626 2018-09-13 2019-09-12 报文的发送方法、绑定关系的通告方法、装置及存储介质 WO2020052641A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/274,595 US11671352B2 (en) 2018-09-13 2019-09-12 Message sending method, binding relationship advertising method, apparatus, and storage medium
EP19861174.1A EP3852319B1 (en) 2018-09-13 2019-09-12 Message sending method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811070482.2 2018-09-13
CN201811070482.2A CN110896379B (zh) 2018-09-13 2018-09-13 报文的发送方法、绑定关系的通告方法、装置及存储介质

Publications (1)

Publication Number Publication Date
WO2020052641A1 true WO2020052641A1 (zh) 2020-03-19

Family

ID=69778198

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/105626 WO2020052641A1 (zh) 2018-09-13 2019-09-12 报文的发送方法、绑定关系的通告方法、装置及存储介质

Country Status (4)

Country Link
US (1) US11671352B2 (zh)
EP (1) EP3852319B1 (zh)
CN (1) CN110896379B (zh)
WO (1) WO2020052641A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022068436A1 (zh) * 2020-09-30 2022-04-07 华为技术有限公司 业务处理方法以及相关设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113872854B (zh) * 2020-06-30 2022-12-30 华为技术有限公司 一种丢包处理方法及网络设备
US11855885B2 (en) * 2020-10-20 2023-12-26 Nokia Solutions And Networks Oy Label switched path scalability
CN112291093A (zh) * 2020-10-29 2021-01-29 迈普通信技术股份有限公司 网络检测方法、装置、网络设备及网络系统
CN113765794B (zh) * 2021-09-30 2022-11-25 新华三信息安全技术有限公司 数据发送的方法、装置、电子设备及介质
CN114024725B (zh) * 2021-10-25 2023-06-20 全球能源互联网研究院有限公司南京分公司 一种容器间通信方法、系统、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040165601A1 (en) * 2003-02-24 2004-08-26 Hsin-Yuo Liu Method and system for label-based packet forwarding among multiple forwarding elements
CN101090355A (zh) * 2007-07-24 2007-12-19 杭州华三通信技术有限公司 虚拟专用网隧道的标签交换路径建立方法、系统和设备
CN101656663A (zh) * 2008-08-20 2010-02-24 华为技术有限公司 一种mpls多播报文的转发方法、装置及系统
CN102025632A (zh) * 2010-12-15 2011-04-20 迈普通信技术股份有限公司 Mpls网络中数据分组的标签分配方法及系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100596107C (zh) * 2007-02-09 2010-03-24 华为技术有限公司 报文转发方法以及自治系统边界路由器
US9344357B2 (en) * 2014-01-24 2016-05-17 Cisco Technology, Inc. Label-switched path aggregation
US10382333B2 (en) * 2017-05-31 2019-08-13 Juniper Networks, Inc. Fabric path context-based forwarding for virtual nodes
US10432523B2 (en) * 2017-05-31 2019-10-01 Juniper Networks, Inc. Routing protocol signaling of multiple next hops and their relationship
US10476817B2 (en) * 2017-05-31 2019-11-12 Juniper Networks, Inc. Transport LSP setup using selected fabric path between virtual nodes
US10659352B2 (en) * 2017-05-31 2020-05-19 Juniper Networks, Inc. Signaling private context forwarding tables for a private forwarding layer

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040165601A1 (en) * 2003-02-24 2004-08-26 Hsin-Yuo Liu Method and system for label-based packet forwarding among multiple forwarding elements
CN101090355A (zh) * 2007-07-24 2007-12-19 杭州华三通信技术有限公司 虚拟专用网隧道的标签交换路径建立方法、系统和设备
CN101656663A (zh) * 2008-08-20 2010-02-24 华为技术有限公司 一种mpls多播报文的转发方法、装置及系统
CN102025632A (zh) * 2010-12-15 2011-04-20 迈普通信技术股份有限公司 Mpls网络中数据分组的标签分配方法及系统

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022068436A1 (zh) * 2020-09-30 2022-04-07 华为技术有限公司 业务处理方法以及相关设备

Also Published As

Publication number Publication date
CN110896379A (zh) 2020-03-20
EP3852319B1 (en) 2024-05-01
CN110896379B (zh) 2022-11-08
US11671352B2 (en) 2023-06-06
EP3852319A1 (en) 2021-07-21
EP3852319A4 (en) 2021-11-10
US20210273881A1 (en) 2021-09-02

Similar Documents

Publication Publication Date Title
WO2020052641A1 (zh) 报文的发送方法、绑定关系的通告方法、装置及存储介质
CN110912795B (zh) 一种传输控制方法、节点、网络系统及存储介质
WO2016198015A1 (zh) 一种报文传输的方法、装置和系统
CN109863725B (zh) 基于最大分段标识符深度的分段路由方法及电子设备
WO2018188464A1 (zh) 一种实现ioam的方法、装置及存储介质
US7483387B2 (en) Hierarchical label distribution for inter-area summarization of edge-device addresses
US10880203B2 (en) Centralized segment routing dataplane based backup path validation
US8467411B1 (en) Service-specific forwarding in an LDP-RSVP hybrid network
US7936780B1 (en) Hierarchical label distribution protocol for computer networks
US10097446B2 (en) Dynamic area filtering for link-state routing protocols
US8363667B2 (en) Summarization and longest-prefix match within MPLS networks
US8259564B1 (en) Egress protection for label switched paths
CN104380673B (zh) 用于在IPv6网络中使用标签分发协议(LDP)实例的系统和方法
CN104243311B (zh) 报文处理的方法及路由器
WO2019165888A1 (zh) 一种利用统一sr标签栈进行报文处理的方法及装置
WO2015149598A1 (zh) 报文处理的方法及标签交换路由器
US9813332B2 (en) Method, device and system for establishing label switched path
CN108886494B (zh) 使用中间系统到中间系统(is-is)的伪线建立和保持的方法和装置
WO2021135624A1 (zh) 基于虚电路的数据报文处理方法、转发表项的构建方法
US11323371B1 (en) Micro SID packet processing with operations, administration, and management
US11240142B2 (en) Class-based traffic engineering in an IP network
WO2022184169A1 (zh) 报文转发方法、系统、存储介质及电子装置
US11563697B2 (en) Multiple label spaces in a label switched router
CN111865795B (zh) 控制方法及装置
WO2022188488A1 (zh) 路径建立方法及其装置、节点、计算机可读存储介质

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: 19861174

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: 2019861174

Country of ref document: EP

Effective date: 20210413