WO2021258823A1 - 路径创建方法、装置及系统 - Google Patents

路径创建方法、装置及系统 Download PDF

Info

Publication number
WO2021258823A1
WO2021258823A1 PCT/CN2021/087505 CN2021087505W WO2021258823A1 WO 2021258823 A1 WO2021258823 A1 WO 2021258823A1 CN 2021087505 W CN2021087505 W CN 2021087505W WO 2021258823 A1 WO2021258823 A1 WO 2021258823A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
message
network device
identifier
bandwidth
Prior art date
Application number
PCT/CN2021/087505
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 华为技术有限公司
Publication of WO2021258823A1 publication Critical patent/WO2021258823A1/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/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/12—Shortest path evaluation
    • H04L45/125—Shortest path evaluation based on throughput or bandwidth

Definitions

  • This application relates to the field of communication technology, and in particular to a method, device and system for creating a path.
  • the path calculation is performed by the controller. After that, the controller sends the calculated path to the repeater through configuration, so as to realize the creation of the path.
  • the embodiments of the present application provide a path creation method, device and system to overcome the problems existing in the related art.
  • a path creation method includes: the first network device obtains a destination address, a bandwidth and a path identifier corresponding to a path to the destination address, and the destination address Used to indicate the tail node of the path; the first network device sends a first message to the second network device.
  • the first message includes the bandwidth, path identifier, and destination address corresponding to the path to the destination address.
  • the first message uses When instructing the second network device to create path information and reserve corresponding resources according to the bandwidth and path identifier, the first message includes an interior gateway protocol (IGP) message or a border gateway protocol (border gateway protocol, BGP) Message, the second network device includes a network device or tail node that the path passes through.
  • IGP interior gateway protocol
  • BGP border gateway protocol
  • the path creation method is more flexible and more reliable than the method where the controller creates the path and statically configures it.
  • the path identifier includes: a flexible Ethernet FlexE identifier, a slice identifier, or a segment routing path identifier.
  • the type of the first message includes an IGP hello (Hello) message or a BGP keep alive (Keep alive) message.
  • the type of the first message includes an IGP Hello message
  • the variable VARIABLE field of the first message includes an extended TLV
  • the extended TLV is used to carry the destination address , The bandwidth and the path identifier.
  • the existing solution architecture can be maximized, and the usability of the technical solution can be improved.
  • the first message further includes a path list
  • the path list includes an identifier of at least one network device through which the path passes
  • the device identifier of the at least one network device includes an identifier of the second network device.
  • the path list is a target path calculated by the first network device according to the destination address.
  • the first message can be propagated according to the path indicated by the path list, and the devices in the path list can create corresponding path information and presets for the path according to the path identifier, bandwidth, etc. Leave the corresponding bandwidth and so on.
  • the method further includes: in response to the path failure, recalculating the path to obtain an updated path list, the updated path list including the identification of at least one network device through which the updated path passes, and the updated path
  • the device identification of at least one network device passed by the path includes the identification of the third network device; a second message is sent to the third network device, and the second message carries the destination address, bandwidth, path identification, and updated path list.
  • the type of the second message is consistent with the type of the first message.
  • the method further includes: receiving a third message sent by the second network device, the third message is a response message of the first message, and the third message is used to indicate that the path information is successfully created ;
  • the third message includes the path identifier.
  • the third message further includes a segment path identifier, and the segment path identifier includes a local identifier assigned to the path by the second network device.
  • the first network device can know that the path is successfully created.
  • the method further includes: receiving a fourth message sent by the second network device, the fourth message is used to indicate that the path information creation failed, the type of the fourth message is the same as the type of the first message Unanimous.
  • the first network device By receiving the fourth message in response to the first message for creating the path, the first network device knows that the path creation has failed, and can further recalculate the path to ensure that the corresponding path can be created, thereby improving the reliability and availability of the network.
  • the method further includes: the first network device reserves corresponding resources according to the bandwidth and path identifier, including: The first network device determines the first outbound interface according to the bandwidth, and the first outbound interface meets the bandwidth requirement; the first network device reserves bandwidth resources on the first outbound interface.
  • the first network device can determine the interface that meets the bandwidth requirement, and prescribe the path on the interface. Keep resources. Improve the availability of the network.
  • the first message is also used to instruct the second network device to send a fifth message corresponding to the first message to the destination address, and the fifth message includes the bandwidth, path identifier, and destination address,
  • the fifth message is used to instruct the fourth network device to create path information and reserve corresponding resources according to the bandwidth and the path identifier, and the fourth network device includes the network devices that the path passes through.
  • the first message further includes a source address
  • the source address is used to indicate the head node of the path
  • the source address is used to instruct the second network device to send a message indicating whether the path is successfully created to the head node.
  • the network device on the path can send a message to the head node whether the path is to create a function.
  • a method for creating a path includes: the second network device receives a first packet sent by the first network device, and the first packet includes a destination address , The bandwidth and path identifier corresponding to the path to the destination address, the destination address is used to indicate the tail node of the path; the second network device creates path information according to the bandwidth and path identifier and reserves corresponding resources, the first message includes an IGP message Or a BGP message, the second network device includes a network device or tail node that the path passes through.
  • the first message further includes a path list
  • the path list includes an identifier of at least one network device through which the path passes
  • the device identifier of the at least one network device includes an identifier of the second network device.
  • the first message sent by the first network device after receiving the first message sent by the first network device, it further includes: receiving a second message sent by the first network device, the second message carrying the destination address, bandwidth, and path identifier And update the path list, the updated path list includes the identification of at least one network device that the updated path passes through, the device identification of at least one network device that the updated path passes through includes the identification of the second network device, and the second report
  • the type of the message is consistent with the type of the first message; the path information is created according to the bandwidth and the path identifier and corresponding resources are reserved.
  • the method further includes: sending a third message to the first network device, the third message being a response message of the first message, and The third message is used to indicate that the path information is successfully created; the third message includes the path identifier.
  • the third message further includes a segment path identifier, and the segment path identifier includes a local identifier assigned to the path by the second network device.
  • the method further includes: sending a fourth message to the first network device, where the fourth message is used to indicate that the path information creation fails, and the fourth message is The type of the message is consistent with the type of the first message.
  • the first network device can know that the path creation has failed, and can further recalculate the path to ensure that the corresponding path can be created and improve the reliability of the network Sex and usability.
  • reserving the corresponding resources according to the bandwidth and the path identifier includes: the second network device determines the first outgoing interface according to the bandwidth, the first outgoing interface meets the bandwidth requirement; the second network device is in the first The outbound interface reserves bandwidth resources.
  • the second network device can determine the interface that meets the bandwidth requirement, and prescribe the path on the interface. Reserve resources to improve the availability of the network.
  • the method further includes: the second network device sends a fifth packet corresponding to the first packet to the destination address, and the fifth packet includes Bandwidth, path identifier and destination address, the fifth message is used to instruct the third network device to create path information and reserve corresponding resources according to the bandwidth and path identifier, and the third network device includes the network device through which the path passes.
  • a path creation device which includes:
  • the processing unit is used to obtain the destination address, the bandwidth and the path identifier corresponding to the path to the destination address, and the destination address is used to indicate the tail node of the path;
  • the sending unit is configured to send a first message to the second network device.
  • the first message includes the bandwidth, path identifier, and destination address.
  • the corresponding resources are reserved.
  • the first message includes an IGP message or a BGP message
  • the second network device includes a network device or tail node that the path passes through.
  • the first message further includes a path list
  • the path list includes an identifier of at least one network device through which the path passes
  • the device identifier of the at least one network device includes an identifier of the second network device.
  • the path list is a target path calculated by the first network device according to the destination address.
  • the processing unit is further configured to re-calculate the path in response to the path failure to obtain an updated path list, the updated path list includes the identification of at least one network device through which the updated path passes, and the update The device identifier of at least one network device passed by the following path includes the identifier of the third network device;
  • the sending unit is further configured to send a second message to the third network device.
  • the second message carries the destination address, bandwidth, path identifier, and updated path list, and the type of the second message is consistent with the type of the first message.
  • the device further includes:
  • the first receiving unit is configured to receive a third message sent by the second network device, the third message is a response message of the first message, the third message is used to indicate that the path information is successfully created, and the third message includes Path identification.
  • the third message further includes a segment path identifier, and the segment path identifier includes a local identifier assigned to the path by the second network device.
  • the device further includes:
  • the second receiving unit is configured to receive a fourth message sent by the second network device, where the fourth message is used to indicate that the path information creation fails, and the type of the fourth message is consistent with the type of the first message.
  • the processing unit is further configured for the first network device to reserve corresponding resources according to the bandwidth and the path identifier, including: determining the first outbound interface according to the bandwidth, and the first outbound interface meets the bandwidth requirement; The first outbound interface reserves bandwidth resources.
  • the first message is also used to instruct the second network device to send a fifth message corresponding to the first message to the destination address, and the fifth message includes the bandwidth, path identifier, and destination address,
  • the fifth message is used to instruct the fourth network device to create path information and reserve corresponding resources according to the bandwidth and the path identifier, and the fourth network device includes the network devices that the path passes through.
  • the first message further includes a source address
  • the source address is used to indicate the head node of the path
  • the source address is used to instruct the second network device to send a message indicating whether the path is successfully created to the head node.
  • a path creation device which includes:
  • a receiving unit configured to receive a first message sent by a first network device, the first message including a destination address, a bandwidth corresponding to a path to the destination address, and a path identifier, and the destination address is used to indicate the tail node of the path;
  • the processing unit is configured to create path information and reserve corresponding resources according to the bandwidth and the path identifier.
  • the first message includes an IGP message or a BGP message
  • the second network device includes a network device or tail node that the path passes through.
  • the first message further includes a path list
  • the path list includes the identification of at least one network device that the path passes through
  • the device identification of the at least one network device includes the identification of the second network device.
  • the receiving unit is further configured to receive a second message sent by the first network device.
  • the second message carries the destination address, bandwidth, path identifier, and update path list. Updating the path list includes updating
  • the identification of at least one network device passed by the subsequent path, the device identification of at least one network device passed by the updated path includes the identification of the second network device, the type of the second packet and the type of the first packet Consistent
  • the processing unit is also used to reserve corresponding resources according to the bandwidth and path identification.
  • the device further includes:
  • the first sending unit is configured to send a third message to the first network device, the third message is a response message to the first message, the third message is used to indicate that the path information is successfully created, and the third message includes the path logo
  • the third message includes a segment path identifier, and the segment path identifier includes a local identifier assigned to the path by the second network device.
  • the device further includes:
  • the second sending unit is configured to send a fourth message to the first network device, the fourth message is used to indicate that the path information creation fails, and the type of the fourth message is consistent with the type of the first message.
  • the processing unit is configured to determine the first outgoing interface according to the bandwidth, and the first outgoing interface meets the bandwidth requirement; and the bandwidth resource is reserved on the first outgoing interface.
  • the device further includes:
  • the third sending unit is configured to send a fifth message corresponding to the first message to the destination address.
  • the fifth message includes the bandwidth, path identifier, and destination address.
  • the fifth message is used to instruct the third network device according to the bandwidth and
  • the path identifier creates path information and reserves corresponding resources, and the third network device includes the network devices through which the path passes.
  • the path identifier includes: a FlexE identifier, a slice identifier, or a segment routing path identifier.
  • the type of the first message includes an IGP Hello message or a BGP keepalive message.
  • the type of the first message includes an IGP Hello message
  • the variable VARIABLE field of the first message includes an extended type length value ( type length value, TLV)
  • the extended TLV is used to carry the destination address, bandwidth, and path identifier.
  • a path creation device comprising: a memory and a processor, and at least one instruction is stored in the memory, and the at least one instruction is loaded and executed by the processor, so as to implement the path creation method of any one of the above-mentioned first aspects.
  • a path creation device comprising: a memory and a processor, and at least one instruction is stored in the memory, and the at least one instruction is loaded and executed by the processor, so as to implement any one of the above-mentioned second aspects.
  • a path creation system is also provided.
  • the system includes a first network device and a second network device.
  • the first network device is configured to execute the path creation method according to any one of the above-mentioned first aspects
  • the second network device is configured to execute The path creation method according to any one of the above-mentioned second aspects.
  • a path creation system is also provided.
  • the system includes a first network device and a second network device.
  • the first network device includes the device according to any one of the foregoing third aspect, and the second network device includes the foregoing fourth aspect. Any one of the devices.
  • a computer-readable storage medium is also provided, and at least one instruction is stored in the storage medium, and the instruction is loaded and executed by a processor to implement the path creation method according to any one of the first aspect or the second aspect.
  • Another communication device which includes a transceiver, a memory, and a processor.
  • the transceiver, the memory, and the processor communicate with each other through an internal connection path, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the transceiver to receive signals and control the transceiver to send signals , And when the processor executes the instructions stored in the memory, the processor is caused to execute the method in the first aspect or any one of the possible implementations of the first aspect, or the processor is caused to execute the second aspect or the first aspect. The method in any possible implementation of the two aspects.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor may be provided separately.
  • the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting mode of the memory and the processor.
  • ROM read only memory
  • a computer program (product) is provided, the computer program (product) includes: computer program code, when the computer program code is run by a computer, the computer executes the methods in the above aspects.
  • a chip including a processor, configured to call and execute instructions stored in the memory from a memory, so that a communication device installed with the chip executes the methods in the foregoing aspects.
  • Another chip including: an input interface, an output interface, a processor, and a memory.
  • the input interface, output interface, the processor, and the memory are connected through an internal connection path, and the processor is used to execute all When the code in the memory is executed, the processor is used to execute the methods in the foregoing aspects.
  • Figure 1 is a schematic diagram of an application scenario provided by an embodiment of the application
  • Figure 2 is a schematic diagram of creating a path in a FlexE scenario provided by an embodiment of the application
  • FIG. 3 is a flowchart of a path creation method provided by an embodiment of the application.
  • Figure 4 is a schematic diagram of the message format of the IGP Hello message provided by an embodiment of the application.
  • FIG. 5 is a schematic diagram of the format of a TLV provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of a process of dynamically creating a FlexE cross tunnel according to an embodiment of the application
  • FIG. 7 is a schematic diagram of a process of dynamically creating a FlexE cross tunnel according to an embodiment of the application.
  • FIG. 8 is a schematic diagram of a process of statically creating a FlexE cross tunnel according to an embodiment of the application.
  • FIG. 9 is a schematic diagram of a process of creating a path provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram of a process of creating a path provided by an embodiment of this application.
  • FIG. 11 is a schematic diagram of a process of dynamically creating a FlexE non-intersecting path according to an embodiment of the application.
  • FIG. 12 is a schematic diagram of a process of statically creating a FlexE non-intersecting path according to an embodiment of the application
  • FIG. 13 is a schematic structural diagram of a path creation device provided by an embodiment of the application.
  • FIG. 14 is a schematic structural diagram of a path creation device provided by an embodiment of the application.
  • FIG. 15 is a schematic structural diagram of a path creation device provided by an embodiment of the application.
  • FIG. 16 is a schematic structural diagram of a path creation device provided by an embodiment of the application.
  • the 100 Gigabit Ethernet (Gigabit Ethernet, GE) flexible Ethernet group (FlexE Group) flexible Ethernet mode physical interface to transmit messages can provide long-distance transmission performance.
  • the standard Ethernet physical interface can be switched to the flexible Ethernet mode physical interface through commands, and when the standard Ethernet physical interface is switched to the flexible Ethernet mode physical interface, the corresponding FlexE interface will be generated at the same time.
  • the bandwidth of the FlexE interface can be flexibly specified. FlexE technology divides the physical (PHY) layer of the standard Ethernet physical interface into multiple identical sub-slots. Each sub-slot corresponds to the same bandwidth. Multiple sub-slot bandwidths can be flexibly combined into logical port bandwidths of different sizes. It is the bandwidth of the FlexE interface.
  • the FlexE interface is equivalent to an independent physical interface.
  • the traffic, protocol, and operation and maintenance of any fragmented network do not affect other fragments, such as business operations, network upgrades, security isolation, attack isolation, etc. Therefore, FlexE technology can meet the requirements of network fragmentation, so that traffic is isolated at the physical layer, and services are network fragmented on the same physical network, so that a physical network supports a large number of different service level agreements (SLA).
  • SLA service level agreements
  • FlexE technology combines network fragmentation to achieve resource isolation and high-speed transmission
  • two paths created.
  • One is a connected FlexE cross path, which can be used as an end-to-end FlexE path.
  • the other is a non-connected FlexE non-cross path.
  • the FlexE non-cross path only establishes a FlexE interface, which can be used for single-hop resource isolation.
  • SR segment routing
  • SIDs segment identifiers
  • SR can directly use the multi-protocol label switching (MPLS) forwarding plane or the Internet protocol version 6 (Internet protocol version 6, IPv6) forwarding plane.
  • MPLS multi-protocol label switching
  • IPv6 Internet protocol version 6, IPv6
  • MPLS forwarding plane it is called SR-MPLS or MPLS-SR.
  • a segment is a label
  • a segment list is a label stack. The currently active segment is at the top of the stack, and the processed segment will be popped from the top of the stack.
  • the label stack is used as the path.
  • IPv6 forwarding plane When the IPv6 forwarding plane is used, it is called an SR based on IPv6 (SRv6), where segments can be expressed in the format of IPv6 addresses, and the packet forwarding path is represented by an IPv6 address sequence.
  • SRv6 based on IPv6 forwarding plane a new IPv6 extension header is added.
  • the IPv6 extension header is a segment routing header (segment routing header, SRH) defined based on the original routing extension header of the IPv6 message, and may also be called an SRH extension header.
  • the SRH extension header specifies an IPv6 path, and stores multiple IPv6 segment identifiers.
  • the head node that sends the message adds one or more SRH extension headers to the message, and the intermediate node can forward the IPv6 message according to the path information contained in the SRH extension header.
  • the related technology adopts the method of path calculation by the controller, and then the controller sends the calculated path information through static configuration to act as a repeater Of the various network devices.
  • the FlexE technology can be applied to the access layer (access), the aggregation layer (aggregation), and the core layer (core).
  • the FlexE scenario includes a controller, a router that undertakes the network forwarding function, and an access router.
  • the controller is a centralized control device in the network.
  • the access router is used to carry network service access and network forwarding functions. Compared with the controller, the router can be called a repeater.
  • the controller After the controller calculates the path, it delivers the corresponding configuration information to the corresponding network device.
  • the configuration information of each network device includes information such as FlexE entrance, FlexE exit, and bandwidth, so as to realize the creation of FlexE path information. Since the related technology performs path calculation through the controller and delivers it to each network device through a static configuration, the method for creating this type of path is relatively complicated and has low reliability.
  • the embodiment of the present application provides a method for creating a path.
  • the method uses the IGP or BGP protocol to create path information on a network device hop by hop, and reserve corresponding resources for the path, so as to simplify the way of path creation and improve the creation of the path. The reliability of the path.
  • the path creation method includes the following processes.
  • the first network device obtains a destination address, a bandwidth corresponding to a path to the destination address, and a path identifier, where the destination address is used to indicate the tail node of the path.
  • the destination address is used to indicate the end node of the path.
  • the bandwidth corresponding to the path to the destination address can be set based on scenario requirements.
  • Path identifiers include but are not limited to FlexE identifiers, slice identifiers, or segment routing path identifiers.
  • the first network device is the head node of the path to the destination address, or the first network device is the network device through which the path to the destination address passes. Among them, the network device through which the path to the destination address passes is also called an intermediate node.
  • the embodiments of this application do not limit the manner in which the first network device obtains the destination address and the bandwidth and path identifier corresponding to the path to the destination address. For the first network device, the following two situations include but are not limited to the following method of obtaining:
  • Case 1 The first network device is the head node of the path to the destination address.
  • information such as the destination address, the bandwidth corresponding to the path to the destination address, and the path identifier can be configured in advance on the side of the first network device. Or, configure the destination address, the bandwidth and path identification information corresponding to the path to the destination address in the controller in advance, and the first network device will control it from the control The device obtains information such as the destination address, the bandwidth corresponding to the path to the destination address, and the path identifier.
  • the first network device is a network device through which the path to the destination address passes.
  • the destination address and the path to the destination address can be obtained from the received message.
  • Information such as the bandwidth and path identification of the destination address, the bandwidth and path identification corresponding to the path to the destination address are transmitted to the next hop node, so that the first network device obtains the destination address and corresponds to the path to the destination address Information such as the bandwidth and path identification.
  • the last hop node of the first network device carries information such as the destination address, the bandwidth corresponding to the path to the destination address, and the path identifier in a message and sends it to the first network device.
  • the first network device can obtain the destination address and the bandwidth and path identification information corresponding to the path to the destination address by parsing the packet.
  • the first network device sends a first message to the second network device.
  • the first message includes a bandwidth, a path identifier, and a destination address.
  • the first message is used to instruct the second network device to create path information based on the bandwidth and path identifier. Reserving corresponding resources, the first message includes an IGP message or a BGP message, and the second network device includes a network device or tail node that the path passes through.
  • the first network device Regardless of whether the first network device is the head node of the path to the destination address or the network device through which the path to the destination address passes, since the first network device is not the tail node of the path to the destination address, in order to enable each
  • the network device creates a path and reserves corresponding resources, and the first network device transmits the obtained destination address, bandwidth, and path identifier to the next hop node on the path.
  • the first network device carries the destination address, bandwidth, and path identifier in the first packet, and sends the second network device to the second network device.
  • the method before the first network device sends the first message to the second network device, the method further includes: determining the second network device according to the destination address. For example, after the first network device obtains the destination address, the bandwidth and the path identifier corresponding to the path to the destination address, it sends the first packet to the next hop calculated by the first network device to reach the destination address, and the next hop The corresponding device is the second network device.
  • the first network device may calculate the path to the destination address according to the destination address, thereby obtaining the path list.
  • the path list includes the identification of each network device that the path passes through, and the first network device can determine which network device is the next hop of the first network device according to the path list, thereby determining the second network device.
  • constraint conditions may also be set.
  • the first network device is configured with path constraint conditions, or the path constraint conditions are acquired from the controller, the first network device calculates the path to the destination address according to the destination address and the path constraint conditions.
  • the path constraint condition is used to indicate the network equipment that the path to the destination address needs to pass through.
  • the destination address is the address of the tail node E. If there is no path constraint condition, when the first network device calculates the path to the tail node E according to the destination address, all paths that can reach the tail node E can meet the requirements.
  • the path constraint condition is set, take the path constraint condition as passing through node C as an example, when the first network device calculates the path to the tail node E according to the destination address, the path must not only reach the tail node E, but also need to pass through the node C .
  • the path list can also be implemented through pre-configuration.
  • the path list is pre-configured on the controller side, and the first network device obtains the path list from the controller through such methods as being issued by the controller or requesting from the controller by the first network device.
  • the path list may also be configured on the first network device side in advance.
  • the path list may be a loose path or a strict path, which is not limited in the embodiment of the present application.
  • the second network device can be determined according to the path list, and the second network device includes but is not limited to the network device that the path passes through, or the tail node of the path.
  • the path list includes the identifier of at least one network device that the path passes through, and the device identifier of the at least one network device includes the identifier of the second network device.
  • the embodiment of the present application does not limit the method for obtaining the path list included in the first message, and the second network device that receives the first message can determine the next hop node according to the path list.
  • the first message includes but is not limited to an IGP message or a BGP message.
  • the first message is an IGP message, and the first message includes but is not limited to an IGP Hello message.
  • the first message is a BGP message, and the first message includes but is not limited to a keepalive message.
  • variable (VARIABLE) field of the first message includes an extended TLV, and the extended TLV is used for carrying purpose Address, bandwidth and path identification.
  • the message format of the IGP Hello message is shown in Figure 4.
  • the path can be established by extending the TLV of the IGP Hello message, and this TLV can be carried in the VARIABLE field of the IGP Hello message.
  • the extended TLV is used for path establishment, that is, it carries the destination address, bandwidth, and path identifier.
  • the first message further includes a source address, the source address is used to indicate the head node of the path, and the source address is used to instruct the second network device to send a message indicating whether the path is successfully created to the head node.
  • the format of the extended TLV is shown in Figure 5.
  • the meaning of each field of the extended TLV is shown in Table 1.
  • a bandwidth (Bandwidth) field is used to carry bandwidth
  • a destination address (DestAddress) field is used to carry a destination address
  • a path identifier (PathIdentifier) field is used to carry a path identifier
  • a source address (SourceAddress) field is used to carry a source address.
  • the method further includes: the first network device creates corresponding path information according to the bandwidth and path identifier, and reserves corresponding resources.
  • creating the corresponding path information includes, but is not limited to, creating a FlexE interface, assigning a label or IPv6SID, and so on.
  • creating the corresponding path information includes creating a FlexE interface.
  • creating the corresponding path information includes creating a FlexE interface.
  • creating the corresponding path information includes assigning the label.
  • the path label is SRv6, creating the corresponding path information includes assigning an IPv6 SID.
  • the first network device reserving the corresponding resource includes: the first network device determines the first outgoing interface according to the bandwidth, and the first outgoing interface meets the bandwidth requirement; the first network device reserves the first outgoing interface Bandwidth resources.
  • determining the first outbound interface according to the bandwidth includes, but is not limited to, querying the next hop according to the destination address or the address in the path list, and the number of the next hop is one or more. Determine the outgoing interface that satisfies the bandwidth among the outgoing interfaces corresponding to one or more next hops, and use the determined outgoing interface that satisfies the bandwidth as the first outgoing interface.
  • resources are reserved on the first outbound interface and a FlexE interface is created.
  • the second network device receives the first packet sent by the first network device.
  • the second network device establishes a network connection with the first network device.
  • the second network device parses the first message to obtain the destination address and the bandwidth and path identification corresponding to the path to the destination address.
  • the first message further includes a source address, and the source address is used to indicate the head node of the path.
  • the source address is also obtained.
  • the embodiment of the application does not limit the manner in which the first message includes the source address.
  • the variable VARIABLE field of the first message includes an extended TLV to carry the source address.
  • the source address can also be carried in other ways.
  • the second network device after parsing the first message, the second network device also obtains the path list, and the path list includes the identification of at least one network device that the path passes through.
  • the device identification of the network device includes the identification of the second network device.
  • the second network device creates path information according to the bandwidth and the path identifier and reserves corresponding resources.
  • the second network device creates corresponding path information according to the bandwidth and the path identifier, including but not limited to creating a FlexE interface, assigning a label or IPv6 SID, and so on.
  • the manner in which the second network device creates corresponding path information according to the bandwidth and the path identifier may refer to the manner in which the first network device creates corresponding path information. For example, if the path identifier is FlexE ID, the creation of the corresponding path information by the second network device includes the creation of a FlexE interface. For another example, if the path label is SR MPLS, the creation of the corresponding path information by the second network device includes assigning the label. For another example, if the path label is SRv6, the creation of the corresponding path information by the second network device includes allocating an IPv6 SID.
  • the second network device reserves the corresponding resource according to the bandwidth and the path identifier, including: the second network device reserves the corresponding resource according to the bandwidth
  • the first outgoing interface is determined, and the first outgoing interface meets the bandwidth requirement; the second network device reserves bandwidth resources on the first outgoing interface.
  • determining the first outbound interface according to the bandwidth includes, but is not limited to, querying the next hop according to the destination address or the path list, and the number of the next hop is one or more.
  • the second network device is a network device through which the path passes, in addition to determining the outgoing interface, it also includes creating a FlexE interface on the interface that receives the first message. If it is necessary to create a FlexE cross path, the second network device further includes connecting the two FlexE interfaces to be created (the connection may also be referred to as a cross).
  • the first network device in the case of carrying the path list in the first message, if the first network device detects that the path fails, in response to the path failure, the first network device recalculates the path to obtain the updated path list ,
  • the updated path list includes the identification of at least one network device passed by the updated path, and the device identification of at least one network device passed by the updated path includes the identification of the third network device;
  • the network device sends a second message, the second message carries the destination address, the bandwidth, the path identifier, and the updated path list, and the type of the second message is consistent with the type of the first message.
  • the third network device is the next hop determined after the first network device recalculates the route.
  • the third network device may be the same as the second network device, or it may be different from the second network device. If the third network device is the same as the second network device, the second network device receives the second message sent by the first network device, creates corresponding path information according to the bandwidth and path identifier in the second message, and reserves the corresponding resource.
  • the method further includes: sending the second network device to the first network device.
  • the third message is the response message of the first message
  • the third message includes the path identifier
  • the third message is used to indicate that the path information is successfully created
  • the third message includes the segment path identifier
  • the segment The path identifier includes a local identifier assigned to the path by the second network device.
  • the third message further includes a path identifier. Through the path identifier, the corresponding interface between the first network device and the second network device can be associated.
  • the first network device receives the third message sent by the second network device.
  • the third message may not carry the segment path identifier.
  • the first network device and the second network device both associate the interface between the first network device and the second network device with a path identifier
  • the third packet may also not include the segment path identifier.
  • the method further includes: sending a third message to the first network device, the third message Used to respond to the second message.
  • the manner in which the second network device sends the third packet to the first network device includes but is not limited to the following two situations:
  • the second network device is the tail node of the path. After creating the corresponding path information and reserving the corresponding resources, the second network device generates a third message and sends the third message to the first network device.
  • the third message may carry a path identifier and a segment path identifier to associate the interface between the first network device and the second network device, and the third message may also carry the path identifier.
  • the third packet may not carry the segment path identifier, for example, the path identifier is used to associate the interface between the first network device and the second network device.
  • Case 2 The second network device is not the tail node of the path, but the network device that the path passes through.
  • the second network device After the second network device creates the corresponding path information and reserves the corresponding resources, it will also send a third message to the next hop of the second network device, and this third message can also be referred to as successful creation.
  • the next hop here refers to the next hop device for the second network device to send the third message to the first network device.
  • the third message may carry the address information of the head node of the path.
  • the next hop device adopts the processing method of the second network device, creates the corresponding path information and reserves the corresponding resources, and then sends the creation success message to the next hop of the next hop in turn, until the creation success message is sent To the head node of the path.
  • the manner in which the network device generates the creation success message, that is, the third message can include but is not limited to the following two:
  • Method 1 After the tail node on the path creates the corresponding path information and reserves related resources, it generates a third message, and sends the third message to the last hop of the tail node, which is the third message sent by the tail node Including the local identifier assigned by the tail node to the path, that is, the segment path identifier, or the third message includes the above path identifier, and the corresponding path between the tail node and the last hop of the tail node is associated with the segment path identifier or path identifier Interface. After that, the last hop of the tail node continues to send the third message to the upper hop according to the processing method of the tail node.
  • the third packet includes the local path allocated by the next hop of the second network device Identifier to associate the interface between the second network device and the next hop of the second network device, or the third message includes the above-mentioned path identifier, and the tail node is associated with the last hop of the tail node through the path identifier Corresponding interface between.
  • the second network device sends a third message to the first network device.
  • the third message includes the local identifier assigned to the path by the second network device to associate the corresponding interface between the second network device and the first network device.
  • Method 2 After each intermediate device or tail node on the path successfully creates path information or reserves related resources, respectively, send a path creation success message to the head node on the path, and the head node combines the messages sent by each device Make sure that the path is created successfully.
  • the second network device after the second network device receives the first packet sent by the first network device, it also includes: the second network device sends a destination address corresponding to the first packet
  • the fifth message includes the bandwidth, path identifier, and destination address.
  • the fifth message is used to instruct the third network device to create path information and reserve corresponding resources based on the bandwidth and path identifier.
  • the third network device Including the network equipment that the path passes through. For example, if the third network device is the next hop of the second network device on the path, the second network device will send the fifth packet to the next hop of the second network device.
  • the fifth message may not carry the path list.
  • the path list may not include the identifier of the second network device, but includes the identifier of the next hop of the second network device.
  • the next hop uses the processing method of the second network device to create the corresponding path information and reserve the corresponding resources, and then send the packets corresponding to the first packet to the next hop of the next hop, until it is sent to the destination address The corresponding tail node.
  • the second network device if the second network device fails to create the corresponding path information or fails to reserve the corresponding resource according to the bandwidth and the path identifier, the second network device sends a fourth packet to the first network device, and the fourth The message is used to indicate that the creation of the path information fails, and the type of the fourth message is consistent with the type of the first message.
  • the first network device receives the fourth packet sent by the second network device.
  • the first network device deletes the created path information.
  • the first message is the Hello message in the IGP message
  • the fourth message is also the Hello message in the IGP message
  • the Action type field of the Hello message is an error notification, indicating that the path creation failed.
  • the first network device receives the Hello message sent by the second network device, and deletes the created path information. If the first network device also creates a FlexE interface, delete the created FlexE interface.
  • the reason why the second network device fails to create the corresponding path information according to the bandwidth and the path identifier is not limited in the embodiment of the present application. For example, if the second network device does not have enough bandwidth to create the corresponding path information, or the second network device does not have a route to the destination address, the second network device may fail to create the path information. In this regard, the second network device sends a fourth message to the first network device to indicate that the creation of the path information fails.
  • the second network device fails to create the corresponding path information and sends the fourth message to the first network device as an example for description.
  • the second network device is the network device through which the path passes, and If the second network device successfully creates the corresponding path information, but the network device after the second network device fails to create the corresponding path information, the second network device will also receive the next hop sent by the second network device The fourth message. Then the second network device deletes the created path information according to the fourth message. If the second network device also creates a FlexE interface, delete the created FlexE interface.
  • the method provided in the embodiments of the present application uses the IGP protocol or the BGP protocol to dynamically create a path and reserve corresponding resources by the network device.
  • the path creation method is more flexible. , Higher reliability. And when a path fails, it can converge in time, which further improves the reliability of creating a path.
  • the path information can also be dynamically created by the network device according to the IGP protocol or the BGP protocol, without the need to reserve corresponding resources.
  • the path to the destination address can be calculated by the controller or the network device, and the way of calculating the path is more flexible.
  • the following takes the creation of a FlexE path through the IGP protocol as an example, and combines the following scenarios to illustrate the method of creating a path provided in the embodiments of the present application.
  • Scenario 1 Dynamically create a FlexE cross tunnel
  • the first network device in the method embodiment shown in FIG. 3 may be device A, device B, device C, or device D in FIG. 6.
  • the second network device may be device B, device C, device D, or device E in FIG. 6.
  • This method includes but is not limited to the following processes. 601. Configure at the head node A or the controller sends configuration information for creating a FlexE cross tunnel to the head node A, the configuration information includes the designated bandwidth, path identifier, and destination address.
  • the designated bandwidth is 2G
  • the path identifier is the unique FlexE-ID of the entire network
  • the FlexE-ID is 1000
  • the destination address is A2:1::1.
  • the destination address is the address of node E, that is, node E is the tail node of the path.
  • the head node A queries the route next hop according to the destination address, reserves resources on the outgoing interface corresponding to the next hop, creates a FlexE interface, and sends an IGP Hello message on the corresponding outgoing interface.
  • the node that initiates the IGP Hello message is node A, which is the head node of the path, and nodes B, C, and D are the network devices that the path passes through.
  • the node E is the node indicated by the destination address, that is, the node E is the tail node of the path.
  • the head node A queries the route next hop NHP as node B according to the destination address. After that, the head node A reserves resources on the outgoing interface corresponding to the node B and creates a FlexE interface.
  • the Hello message carries information such as bandwidth, FlexE ID, and destination address.
  • the Path Type of the extended TLV field of the Hello message is IPv6, the RES Type is FlexE Cross, and the Action is Create.
  • the Hello message instructs Node B to create a FlexE cross path, and the path type is IPv6.
  • Node B receives the Hello message, creates a FlexE interface on the inbound interface of the receiving end according to the content of the Hello message, and queries the next hop based on the destination address, creates a FlexE interface on the outbound interface corresponding to the next hop and reserves resources, The incoming and outgoing FlexE interfaces are crossed, and Hello packets are sent to the next hop.
  • the next hop of node B is queried for node C according to the destination address. Therefore, node B sends a Hello message to node C.
  • the Path Type of the extended TLV field of the Hello message is IPv6
  • the RES Type is FlexE Cross
  • the Action is Create.
  • the Hello message instructs node C to create a FlexE cross path, and the path type is IPv6.
  • Node C processes the Hello message according to the processing method of node B, and so on, sends a Hello message to node D
  • node D also processes the Hello message according to the processing method of node B, and continues to send the Hello message to node D.
  • the next hop node sends the Hello message until the end node E of the Hello message is sent, that is, the node corresponding to the destination address.
  • tail node E After the tail node E receives the Hello message and successfully creates the FlexE interface, it sends a third message in response to the Hello message to the node A.
  • the third message is sent to node A through a user networks interface (UNI).
  • the third message is a successful creation of the IGP protocol.
  • the third message is sent by node D to node C, and then sent by node C to node B, until it is sent by node B to node A.
  • the third message may carry a segment path identifier, and may also carry a path identifier.
  • the path identifier of the segment is a local identifier assigned to the path by the current node, and the corresponding interface between two nodes is associated with the local identifier or path identifier.
  • Node A receives the third message and confirms that the path is successfully established. At this point, the FlexE cross tunnel is established.
  • nodes B, C, and D receive the Hello message. After creating two FlexE interfaces, the two FlexE interfaces are cross-connected. It is explained as an example. In addition to this method, after receiving the Hello message, nodes B, C, and D can only create two FlexE interfaces in and out, and do not cross-connect the two FlexE interfaces. Instead, they will send it to the next hop after receiving the Hello message. After the third message, cross-connect the two FlexE interfaces.
  • the process of creating a path shown in Figure 6 is for the scenario of successfully creating a FlexE cross tunnel.
  • the target node to a certain link does not have enough bandwidth to create a FlexE interface, or the target If the node does not have a route to the destination address, the target node can reply to the previous hop of the target node with a new Hello message.
  • the Action type of the new Hello message is filled in as an error notification to indicate that the FlexE cross tunnel creation failed.
  • After the last hop of the target node receives the new Hello message it deletes the created FlexE interface, and continues to send the new Hello message to the upper hop until it is sent to the head node A. After receiving the new Hello message, the head node A deletes the created FlexE interface.
  • Configure at the head node A or the controller sends configuration information for creating a FlexE cross tunnel to the head node A.
  • the configuration information includes a designated bandwidth, a path identifier, and a destination address.
  • the designated bandwidth is 2G
  • the path identifier is the unique FlexE-ID of the entire network
  • the FlexE-ID is 1000
  • the destination address is A2:1::1.
  • the destination address is the address of node E, that is, node E is the tail node of the path.
  • the head node A queries the route next hop according to the destination address, reserves resources on the outgoing interface corresponding to the next hop, creates a FlexE interface, and sends an IGP Hello message on the corresponding outgoing interface.
  • the node that initiates the IGP Hello message is node A, which is the head node of the path, and nodes B, C, and D are the network devices that the path passes through.
  • the node E is the node indicated by the destination address, that is, the node E is the tail node of the path.
  • the head node A queries the route next hop NHP as node B according to the destination address. After that, the head node A reserves resources on the outgoing interface corresponding to the node B and creates a FlexE interface.
  • the Hello message carries information such as bandwidth, FlexE ID, and destination address.
  • the Path Type of the extended TLV field of the Hello message is IPv6, the RES Type is FlexE Cross, and the Action is Create.
  • the Hello message instructs Node B to create a FlexE cross path, and the path type is IPv6.
  • Node B receives the Hello message, creates a FlexE interface on the inbound interface of the receiving end according to the content of the Hello message, and queries the next hop based on the destination address, creates a FlexE interface on the outbound interface corresponding to the next hop, and reserves corresponding resources , Cross the incoming and outgoing FlexE interfaces, and continue to send Hello packets to the next hop.
  • the next hop of node B is queried for node C according to the destination address. Therefore, node B sends a Hello message to node C.
  • the Path Type of the extended TLV field of the Hello message is IPv6
  • the RES Type is FlexE Cross
  • the Action is Create.
  • the Hello message instructs node C to create a FlexE cross path, and the path type is IPv6.
  • Node C receives the Hello message, finds that the next hop is node D according to the destination address in the Hello message, determines the outgoing interface to node D, and finds a link failure, then node C converges to the next hop node F .
  • Node C creates a FlexE interface on the new outgoing interface and sends a Hello message to node F.
  • the node C may also send a fourth message to the head node, where the fourth message is used to indicate that the path information creation fails.
  • the type of the fourth message is consistent with the type of the first message.
  • node F After node F receives the Hello message, it creates a FlexE interface on the inbound interface of the receiving end according to the content of the Hello message, and queries the next hop based on the destination address, creates a FlexE interface on the outbound interface corresponding to the next hop, and reserves the corresponding Resources, cross the incoming and outgoing FlexE interfaces, and continue to send Hello packets to the next hop.
  • node E which is the tail node of the path.
  • the tail node E After receiving the Hello message, the tail node E successfully creates the FlexE interface, and sends a third message in response to the Hello message to node A.
  • the third message is a successful creation of the IGP protocol. As shown in FIG. 7, the third message is sent by node F to node C, and then sent by node C to node B, until it is sent by node B to node A.
  • the third message may carry a segment path identifier, and may also carry a path identifier.
  • the path identifier of the segment is a local identifier assigned to the path by the current node, and the corresponding interface between two nodes is associated with the local identifier or path identifier.
  • Node A receives the third message and confirms that the path is successfully established. At this point, the FlexE cross tunnel is established.
  • Configure the head node A or the controller sends configuration information for creating a FlexE cross tunnel to the head node A.
  • the configuration information includes the designated bandwidth, path identifier, destination address, and an explicit path list.
  • the designated bandwidth is 2G
  • the path identifier is the unique FlexE-ID of the entire network
  • the FlexE-ID is 1000
  • the destination address is A2:1::1.
  • the destination address is the address of node E, that is, node E is the tail node of the path.
  • the specified explicit path list includes the identifiers of the network devices on the path, as shown in Figure 8 Path: A, B, C, D, E. Among them, A, B, C, D, and E represent the identifiers of nodes A, B, C, D, and E respectively.
  • Node A is the first node in the explicit path list, that is, node A is the head node that initiates the IGP Hello message, and nodes B, C, and D are the network devices that the path passes through, and node E is the destination address. That is, the node E is the end node of the path.
  • the head node A searches for the outgoing interface corresponding to the next hop according to the explicit path list, reserves resources on the outgoing interface corresponding to the next hop, creates a FlexE interface, and sends an IGP Hello message on the outgoing interface corresponding to the next hop.
  • the head node A queries the next hop NHP as node B according to the explicit path list. After that, the head node A reserves resources on the outgoing interface corresponding to the node B and creates a FlexE interface.
  • the Hello message carries bandwidth, FlexE ID, destination address and display path list.
  • the display path list in the Hello message sent by the head node A to the node B does not include the identification of the head node A.
  • the Path Type of the extended TLV field of the Hello message is IPv6, the RES Type is FlexE Cross, and the Action is Create.
  • Node B receives the Hello message, creates a FlexE interface on the inbound interface of the receiving end according to the content of the Hello message, and queries the next hop based on the displayed path list, creates a FlexE interface on the outbound interface corresponding to the next hop, and reserves the corresponding Resources, cross the incoming and outgoing FlexE interfaces, and continue to send Hello packets to the next hop.
  • the next hop of node B is queried for node C according to the displayed path list. Therefore, node B sends a Hello message to node C.
  • the display path list in the Hello message sent by node B to node C does not include the identifier of node B.
  • the Path Type of the extended TLV field of the Hello message is IPv6
  • the RES Type is FlexE Cross
  • the Action is Create.
  • the Hello message instructs node C to create a FlexE cross path
  • the path type is IPv6.
  • Node C processes the Hello message according to the processing method of node B, and so on, sends a Hello message to node D
  • node D also processes the Hello message according to the processing method of node B, and continues to send the Hello message to node D.
  • the next hop node sends the Hello message until the end node E of the Hello message is sent, that is, the node corresponding to the destination address.
  • the tail node E receives the Hello message, and after successfully creating the FlexE interface, it sends a third message in response to the Hello message to the node A.
  • the third message is a successful creation of the IGP protocol.
  • the third message is sent by node D to node C, and then sent by node C to node B, until it is sent by node B to node A.
  • the third message can carry the segment path identifier and also the path identifier.
  • the path identifier of the segment is a local identifier assigned to the path by the current node, and the corresponding interface between two nodes is associated with the local identifier or path identifier.
  • Node A receives the third message and confirms that the path is successfully established. At this point, the FlexE cross tunnel is established.
  • the process of statically creating FlexE cross tunnels in this scenario three specifies an explicit path list.
  • FlexE cross paths are established hop by hop, the routing table is not checked, but based on the path list. Specify the route to establish a FlexE cross interface hop by hop.
  • Scenario 4 The network device calculates the path and establishes a FlexE path that satisfies the constraints
  • the CSPF algorithm is used for dynamic path calculation on the network device side, such as the head node, based on the bandwidth constraint, to find a path that satisfies the bandwidth constraint. Then the path is established hop by hop by the IGP protocol, resource reservation and interface creation are performed. Taking the process of creating a path shown in FIG. 9 as an example, the method of creating a path will be described, including but not limited to the following processes.
  • Configure at the head node A or the controller sends configuration information for creating a FlexE cross tunnel to the head node A.
  • the configuration information includes a designated bandwidth, a path identifier, and a destination address.
  • the designated bandwidth is 2G
  • the path identifier is the unique FlexE-ID of the entire network
  • the FlexE-ID is 1000
  • the destination address is A2:1::1.
  • the destination address is the address of node E, that is, node E is the tail node of the path.
  • the head node A calculates a path that satisfies the bandwidth constraint according to the configured destination address.
  • the head node A calculates a path that satisfies the bandwidth constraint according to the configured destination address A2:1::1, and obtains a path list.
  • the identifiers of the network devices included in the path list are B, C, D, and E.
  • the node that initiates the IGP Hello message is node A, which is the head node of the path, and nodes B, C, and D are the network devices that the path passes through, and node E is the destination address.
  • the indicated node, that is, the node E is the end node of the path.
  • the head node A searches for the outgoing interface corresponding to the next hop according to the calculated path, reserves resources on the outgoing interface corresponding to the next hop, creates a FlexE interface, and sends an IGP Hello message on the outgoing interface corresponding to the next hop.
  • the head node A queries the next hop NHP as node B according to the calculated path. After that, the head node A reserves resources on the outgoing interface corresponding to the node B and creates a FlexE interface.
  • the Hello message carries bandwidth, FlexE ID, destination address and display path list.
  • the display path list in the Hello message sent by the head node A to the node B does not include the identification of the head node A.
  • the Path Type of the extended TLV field of the Hello message is IPv6, the RES Type is FlexE Cross, and the Action is Create.
  • Node B receives the Hello message, creates a FlexE interface on the inbound interface of the receiving end according to the content of the Hello message, and queries the next hop according to the path list, creates a FlexE interface on the outbound interface corresponding to the next hop, and reserves corresponding resources , Cross the incoming and outgoing FlexE interfaces, and continue to send Hello packets to the next hop.
  • the next hop of node B is queried for node C according to the path list. Therefore, node B sends a Hello message to node C.
  • the path list in the Hello message sent by node B to node C does not include the identifier of node B.
  • the Path Type of the extended TLV field of the Hello message is IPv6
  • the RES Type is FlexE Cross
  • the Action is Create.
  • the Hello message instructs node C to create a FlexE cross path
  • the path type is IPv6.
  • Node C processes the Hello message according to the processing method of node B, and so on, sends a Hello message to node D, and node D also processes the Hello message according to the processing method of node B, and continues to send the Hello message to node D.
  • the next hop node sends the Hello message until the end node E of the Hello message is sent, that is, the node corresponding to the destination address.
  • tail node E After the tail node E receives the Hello message and successfully creates the FlexE interface, it sends a third message in response to the Hello message to the node A.
  • the third message is a successful creation of the IGP protocol.
  • the third message is sent by node D to node C, and then sent by node C to node B, until it is sent by node B to node A.
  • the third message may carry a segment path identifier, and may also carry a path identifier.
  • the path identifier of the segment is a local identifier assigned to the path by the current node, and the corresponding interface between two nodes is associated with the local identifier or path identifier.
  • Node A receives the third message and confirms that the path is successfully established. At this point, the FlexE cross tunnel is established.
  • the head node A can recalculate the constraint path after sensing the failure from the TEDB to obtain an updated path list. After that, continue to create paths according to the updated path list.
  • Scenario 5 The network device calculates the path and establishes a FlexE path that meets path constraints
  • users may wish to specify a FlexE path to pass through a certain link and node, and other paths are not restricted.
  • the IGP protocol establishes the constraint path. Taking the process of creating a path shown in FIG. 10 as an example, the method of creating a path will be described, including but not limited to the following processes.
  • Configure at head node A or the controller sends configuration information for creating a FlexE cross tunnel to head node A.
  • the configuration information includes designated bandwidth, path identifier, destination address, and path constraint conditions.
  • the designated bandwidth is 2G
  • the path identifier is the unique FlexE-ID of the entire network
  • the FlexE-ID is 1000
  • the destination address is A2:1::1.
  • the path constraint condition indicates that the path to the destination address needs to include node F.
  • the destination address is the address of node E, that is, node E is the tail node of the path.
  • the head node calculates a path that satisfies the bandwidth constraint according to the configured destination address. Since the path calculation constraint requires passing through node F, the path list obtained by calculating the path includes identifiers B, C, F, and E.
  • the node that initiates the IGP Hello message is node A, which is the head node of the path, and nodes B, C, and F are the network devices that the path passes through, and node E is the destination address.
  • the indicated node, that is, the node E is the end node of the path.
  • the head node searches for the outgoing interface corresponding to the next hop according to the calculated path, reserves resources on the outgoing interface corresponding to the next hop, creates a FlexE interface, and sends an IGP Hello message on the outgoing interface corresponding to the next hop.
  • the head node A queries the next hop NHP as node B according to the calculated path. After that, the head node A reserves resources on the outgoing interface corresponding to the node B and creates a FlexE interface.
  • the Hello message carries bandwidth, FlexE ID, destination address and display path list. Among them, the display path list in the Hello message sent by the head node A to the node B does not include the identification of the head node A, but includes the identifications B, C, F, and E.
  • the Path Type of the extended TLV field of the Hello message is IPv6, the RES Type is FlexE Cross, and the Action is Create.
  • Node B receives the Hello message, creates a FlexE interface on the inbound interface of the receiving end according to the content of the Hello message, and queries the next hop according to the path list, creates a FlexE interface on the outbound interface corresponding to the next hop, and reserves corresponding resources , Cross the incoming and outgoing FlexE interfaces, and continue to send Hello packets to the next hop.
  • the next hop of node B is queried for node C according to the path list. Therefore, node B sends a Hello message to node C.
  • the path list in the Hello message sent by node B to node C does not include the identifier of node B.
  • the Path Type of the extended TLV field of the Hello message is IPv6
  • the RES Type is FlexE Cross
  • the Action is Create.
  • the Hello message instructs node C to create a FlexE cross path
  • the path type is IPv6.
  • Node C processes the Hello message according to the processing method of node B, and so on, sends a Hello message to node F, and node F also processes the Hello message according to the processing method of node B, and continues to send the Hello message to node F.
  • the next hop node sends the Hello message until the end node E of the Hello message is sent, that is, the node corresponding to the destination address.
  • tail node E After the tail node E receives the Hello message and successfully creates the FlexE interface, it sends a third message in response to the Hello message to the node A.
  • the third message is a successful creation of the IGP protocol. As shown in FIG. 10, the third message is sent by node F to node C, and then sent by node C to node B, until it is sent by node B to node A.
  • the third message may carry a segment path identifier, and may also carry a path identifier.
  • the path identifier of the segment is a local identifier assigned to the path by the current node, and the corresponding interface between two nodes is associated with the local identifier or path identifier.
  • Node A receives the third message and confirms that the path is successfully established. At this point, the FlexE cross tunnel is established.
  • each node When creating a FlexE non-cross path, each node only creates a single-hop path, only creates a FlexE interface, reserves resources, and does not cross-connect.
  • the Res Type carried in the IGP hello message is FlexE.
  • Other processing is similar to that of creating a FlexE cross path, and you can refer to the process of creating a FlexE cross path as shown in Figure 6. Taking the process of dynamically creating a FlexE non-intersecting path shown in FIG. 11 as an example, the method of creating a path will be described, including but not limited to the following processes.
  • the configuration information includes the designated bandwidth, path identifier, and destination address.
  • Figure 11 shows the process of creating two FlexE non-intersecting paths in a fragment.
  • the specified bandwidth is 2G
  • the path ID is Slicing ID
  • the Slicing ID is 100
  • the destination address is H.
  • the destination address is the address of node H, that is, node H is the end node of the path.
  • the head node A queries the route next hop according to the destination address, reserves resources on the outgoing interface corresponding to the next hop, creates a FlexE interface, and sends an IGP Hello message on the corresponding outgoing interface.
  • the node that initiates the IGP Hello message is node A, which is the head node of the path, and nodes B, E, F, and G are the networks that the path passes through
  • node H is the node indicated by the destination address, that is, the node H is the end node of the path.
  • the head node A queries the route next hop NHP as node B according to the destination address. After that, the head node A reserves resources on the outgoing interface corresponding to the node B and creates a FlexE interface.
  • the Hello message carries information such as a bandwidth of 2G, a Slicing ID of 100, and a destination address of the address of node H.
  • Node B receives the Hello message, creates a FlexE interface on the inbound interface of the receiving end according to the content of the Hello message, and queries the next hop based on the destination address, creates a FlexE interface on the outbound interface corresponding to the next hop, and reserves corresponding resources , Continue to send Hello packets to the next hop.
  • next hop of node B is queried for node E according to the destination address, so node B sends a Hello message to node E.
  • Node E processes the Hello message according to the processing method of node B, and so on, sends a Hello message to node F, and node F also processes the Hello message according to the processing method of node B, and continues to send the Hello message to node F.
  • the next hop node G sends the Hello message until the end node H sent by the Hello message, that is, the node corresponding to the destination address.
  • the bandwidth on one interface of node F is only 3G, and the two paths are 2G and 3G respectively. Chips can share bandwidth on one interface, and the created FlexE information contains information about two paths. Therefore, the Hello message sent by node E received by node F in FIG. 11 includes two sets of information.
  • the Slicing ID in the two groups of information is 100, one group carries the bandwidth of 2G, the destination address is the address of node H, and the other group carries the bandwidth of 3G, and the destination address is the address of node J.
  • tail node H After the tail node H receives the Hello message and successfully creates the FlexE interface, it sends a third message in response to the Hello message to node A.
  • the third message is a successful creation of the IGP protocol. As shown in FIG. 11, the third message is sent by node G to node F, then sent by node F to node E, and then sent by node E to node B, until it is sent by node B to node A.
  • Node A receives the third message and confirms that the path is successfully established. At this time, the FlexE non-intersecting path is established.
  • statically creating a FlexE non-crossing path is a specified path
  • dynamically creating a FlexE non-crossing path is a path that is dynamically learned based on routing.
  • Configure a FlexE non-cross path configuration information on the head node A where the configuration information includes a designated bandwidth, a path identifier, a destination address, and an explicit path list.
  • Figure 12 shows the process of creating two FlexE non-intersecting paths in a fragment.
  • the specified bandwidth is 2G
  • the path identifier is Slicing ID
  • the Slicing ID is 100
  • the destination address is H.
  • the destination address is the address of node H, that is, node H is the end node of the path.
  • the specified explicit path list includes the identifiers of the network devices on the path, such as the Path shown in Figure 12: A, B, E, F, G, and H. Among them, A, B, E, F, G, and H represent the identifiers of nodes A, B, E, F, G, and H respectively.
  • node A is the head node that initiates the IGP Hello message
  • nodes B, E, F, and G are the network devices that the path passes through
  • node H is the node indicated by the destination address, that is, the Node H is the end node of the path.
  • the head node A searches for the outgoing interface corresponding to the next hop according to the explicit path list, reserves resources on the outgoing interface corresponding to the next hop, creates a FlexE interface, and sends an IGP Hello message on the outgoing interface corresponding to the next hop.
  • the head node A queries the next hop NHP as node B according to the explicit path list. After that, the head node A reserves resources on the outgoing interface corresponding to the node B and creates a FlexE interface.
  • the Hello message carries bandwidth, FlexE ID, destination address and display path list. Wherein, the display path list in the Hello message sent by the head node A to the node B does not include the identification of the head node A.
  • Node B receives the Hello message, creates a FlexE interface on the inbound interface of the receiving end according to the content of the Hello message, and queries the next hop according to the displayed path list, creates a FlexE interface on the outbound interface corresponding to the next hop, and reserves the corresponding Resources, continue to send Hello packets to the next hop.
  • node B sends a Hello message to node E.
  • the display path list in the Hello message sent by node B to node E does not include the identifier of node B.
  • Node E processes the Hello message according to the processing method of node B, and so on, sends a Hello message to node F, and node F also processes the Hello message according to the processing method of node B, and continues to send the Hello message to node F.
  • the next hop node G sends the Hello message until the end node H sent by the Hello message, that is, the node corresponding to the destination address.
  • the Hello message from node E received by node F in FIG. 12 includes two sets of information.
  • the Slicing ID in the two groups of information is 100, one group carries the bandwidth of 2G, the destination address is the address of node H, the path list includes the identifiers F, G, and H; the other group carries the bandwidth of 3G, and the destination address is the node.
  • the address of J, the identifiers included in the path list are F, I, and J.
  • the tail node H After receiving the Hello message, the tail node H successfully creates the FlexE interface, and sends a third message in response to the Hello message to node A.
  • the third message is a successful creation of the IGP protocol. As shown in FIG. 12, the third message is sent by node G to node F, then sent by node F to node E, and then sent by node E to node B, and then sent by node B to node A.
  • Node A receives the third message and confirms that the path is successfully established. At this time, the FlexE non-intersecting path is established.
  • An embodiment of the present application provides a path creation device, which is used to execute the method executed by the first network device in FIG. 3 through the units shown in FIG. 13.
  • the device includes:
  • the processing unit 1301 is configured to obtain the destination address, the bandwidth and the path identifier corresponding to the path to the destination address, and the destination address is used to indicate the tail node of the path.
  • the processing unit 1301 Exemplarily, for the functions performed by the processing unit 1301, reference may be made to the related description of 301 shown in FIG. 3, which will not be repeated here.
  • the sending unit 1302 is configured to send a first message to the second network device.
  • the first message includes a bandwidth, a path identifier, and a destination address.
  • the first message is used to instruct the second network device to create path information based on the bandwidth and path identifier. Reserving corresponding resources, the first message includes an IGP message or a BGP message, and the second network device includes a network device or tail node that the path passes through.
  • the sending unit 1302 reference may be made to the related description of 302 shown in FIG. 3, which will not be repeated here.
  • the first message further includes a path list
  • the path list includes an identifier of at least one network device through which the path passes
  • the device identifier of the at least one network device includes an identifier of the second network device.
  • the path list is a target path calculated by the first network device according to the destination address.
  • the processing unit 1301 is further configured to perform path calculation again in response to a path failure to obtain an updated path list, and the updated path list includes the identification of at least one network device through which the updated path passes.
  • the device identifier of at least one network device passed by the updated path includes the identifier of the third network device;
  • the sending unit 1302 is further configured to send a second message to the third network device, the second message carries the destination address, bandwidth, path identifier, and update path list, and the type of the second message is consistent with the type of the first message .
  • the device further includes: a first receiving unit, configured to receive a third message sent by the second network device, the third message being a response message of the first message, and the third message It is used to indicate that the path information is successfully created, and the third message includes the path identifier.
  • the third message may also include a segment path identifier, and the segment path identifier includes a local identifier assigned to the path by the second network device.
  • the apparatus further includes: a second receiving unit, configured to receive a fourth packet sent by the second network device, the fourth packet is used to indicate that the path information creation failed, and the type of the fourth packet Consistent with the type of the first message.
  • the processing unit 1301 is further configured for the first network device to reserve corresponding resources according to the bandwidth and the path identifier, including: determining the first outbound interface according to the bandwidth, and the first outbound interface meets the bandwidth requirement; Reserve bandwidth resources on the first outbound interface.
  • the first message is also used to instruct the second network device to send a fifth message corresponding to the first message to the destination address, and the fifth message includes the bandwidth, path identifier, and destination address,
  • the fifth message is used to instruct the fourth network device to create path information and reserve corresponding resources according to the bandwidth and the path identifier, and the fourth network device includes the network devices that the path passes through.
  • the first message further includes a source address
  • the source address is used to indicate the head node of the path
  • the source address is used to instruct the second network device to send a message indicating whether the path is successfully created to the head node.
  • the device provided by the embodiment of the present application uses the IGP protocol or the BGP protocol to dynamically create a path and reserve corresponding resources by the network device.
  • the path creation method is more flexible. , Higher reliability. And when a path fails, it can converge in time, which further improves the reliability of creating a path.
  • the path to the destination address can be calculated by the controller or the first network device, and the way of calculating the path is more flexible.
  • An embodiment of the present application provides a path creation device, which is used to execute the method executed by the second network device in FIG. 3 through each unit shown in FIG. 14.
  • the device includes:
  • the receiving unit 1401 is configured to receive a first message sent by a first network device, the first message includes a destination address, a bandwidth corresponding to a path to the destination address, and a path identifier, and the destination address is used to indicate the tail node of the path; exemplary For the functions performed by the receiving unit 1401, reference may be made to the related description of 303 shown in FIG. 3, which will not be repeated here.
  • the processing unit 1402 is configured to create path information and reserve corresponding resources according to the bandwidth and path identifiers.
  • the first message includes an interior gateway protocol IGP message or a border gateway protocol BGP message
  • the second network device includes a network device that the path passes through Or tail node.
  • the first message further includes a path list
  • the path list includes an identifier of at least one network device through which the path passes
  • the device identifier of the at least one network device includes an identifier of the second network device.
  • the receiving unit 1401 is further configured to receive a second message sent by the first network device.
  • the second message carries the destination address, bandwidth, path identifier, and update path list.
  • the update path list includes The identifier of at least one network device passed by the updated path, the device identifier of at least one network device passed by the updated path includes the identifier of the second network device, and the type of the second packet is the same as that of the first packet. The same type;
  • the processing unit 1402 is further configured to reserve corresponding resources according to the bandwidth and path identifier.
  • the device further includes: a first sending unit, configured to send a third message to the first network device, the third message is a response message of the first message, and the third message is used for To indicate that the path information is successfully created; the third message includes the segment path identifier, and the segment path identifier includes the local identifier assigned to the path by the second network device.
  • the apparatus further includes: a second sending unit, configured to send a fourth message to the first network device, the fourth message is used to indicate that the path information creation fails, and the type of the fourth message is the same as The type of the first message is the same.
  • the processing unit 1402 is configured to determine the first outgoing interface according to the bandwidth, and the first outgoing interface meets the bandwidth requirement; and to reserve bandwidth resources on the first outgoing interface.
  • the device further includes: a third sending unit, configured to send a fifth message corresponding to the first message to the destination address, the fifth message including the bandwidth, the path identifier, and the destination address.
  • the fifth message is used to instruct the third network device to create path information and reserve corresponding resources according to the bandwidth and the path identifier, and the third network device includes the network devices that the path passes through.
  • FIG. 15 is a schematic diagram of the hardware structure of a path creation device 1500 according to an embodiment of the application.
  • the path creation device 1500 shown in FIG. 15 can execute the corresponding steps in the path creation method provided in the above-mentioned embodiment shown in FIG. 3.
  • the path creation device 1500 includes a processor 1501, a memory 1502, an interface 1503, and a bus 1504.
  • the interface 1503 may be implemented in a wireless or wired manner.
  • the interface 1503 may be a network card.
  • the aforementioned processor 1501, memory 1502, and interface 1503 are connected through a bus 1504.
  • the interface 1503 may include a transmitter and a receiver for communicating with other communication devices.
  • the processor 1501 is configured to perform processing related steps 301 to 304 in the embodiment shown in FIG. 3.
  • the memory 1502 includes an operating system 15021 and application programs 15022 for storing programs, codes, or instructions. When the processor or hardware device executes these programs, codes, or instructions, the processing process involving the path creation device 1500 in the method embodiment can be completed.
  • the memory 1502 may include a read-only memory (English: Read-only Memory, abbreviation: ROM) and a random access memory (English: Random Access Memory, abbreviation: RAM).
  • ROM includes basic input/output system (English: Basic Input/Output System, abbreviation: BIOS) or embedded system; RAM includes application programs and operating system.
  • BIOS Basic Input/Output System
  • RAM includes application programs and operating system.
  • BIOS Basic Input/Output System
  • the running path creation device 1500 the system is booted by the BIOS solidified in the ROM or the bootloader in the embedded system, and the boot path creation device 1500 enters a normal operating state. After the path creation device 1500 enters the normal operating state, the application program and the operating system run in the RAM, thereby completing the processing procedure involving the path creation device 1500 in the method embodiment.
  • FIG. 15 only shows a simplified design of the path creation device 1500.
  • the path creation device 1500 may include any number of interfaces, processors or memories.
  • processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processing (DSP), and application specific integrated circuits. ASIC), field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or any conventional processor. It is worth noting that the processor can be a processor that supports an advanced RISC machine (advanced RISC machines, ARM) architecture.
  • the foregoing memory may include a read-only memory and a random access memory, and provide instructions and data to the processor.
  • the memory may also include non-volatile random access memory.
  • the memory can also store device type information.
  • the memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), a Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not limiting illustration, many forms of RAM are available.
  • static random access memory static random access memory
  • dynamic random access memory dynamic random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate synchronous dynamic random access Memory double data date SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • serial link DRAM SLDRAM
  • direct memory bus random access memory direct rambus RAM
  • FIG. 16 shows a schematic structural diagram of a network device 700 provided by an exemplary embodiment of the present application.
  • the network device 700 may be configured as the first network device or the second network device in the foregoing method embodiment.
  • the network device 700 includes: a main control board 710 and an interface board 730.
  • the main control board is also called the main processing unit (MPU) or the route processor card.
  • the main control board 710 is used to control and manage the various components of the network device 700, including route calculation and device management. , Equipment maintenance, protocol processing functions.
  • the main control board 710 includes a central processing unit 711 and a memory 712.
  • the interface board 730 is also called a line processing unit (LPU), a line card (line card), or a service board.
  • the interface board 730 is used to provide various service interfaces and implement data packet forwarding.
  • Service interfaces include, but are not limited to, Ethernet interfaces, POS (Packet over SONET/SDH) interfaces, etc.
  • the Ethernet interfaces are, for example, Flexible Ethernet Clients (Flexible Ethernet Clients, FlexE Clients).
  • the interface board 730 includes a central processor 731, a network processor 732, a forwarding entry memory 734, and a physical interface card (PIC) 733.
  • PIC physical interface card
  • the central processing unit 731 on the interface board 730 is used to control and manage the interface board 730 and communicate with the central processing unit 711 on the main control board 710.
  • the network processor 732 is used to implement message forwarding processing.
  • the form of the network processor 732 may be a forwarding chip.
  • the network processor 732 is configured to forward the received message based on the forwarding table stored in the forwarding table entry memory 734, and if the destination address of the message is the address of the network device 700, the message is sent to the CPU (such as the central processing unit 711) processing; if the destination address of the message is not the address of the network device 700, the next hop and outbound interface corresponding to the destination address are found from the forwarding table according to the destination address, and the message is forwarded to The outgoing interface corresponding to the destination address.
  • the processing of the upstream message includes: the processing of the inbound interface of the message, the lookup of the forwarding table; the processing of the downstream message: the lookup of the forwarding table, and so on.
  • the physical interface card 733 is used to implement the docking function of the physical layer, the original traffic enters the interface board 730 from this, and the processed packets are sent from the physical interface card 733.
  • the physical interface card 733 is also called a daughter card, which can be installed on the interface board 730, and is responsible for converting the photoelectric signal into a message, checking the validity of the message, and forwarding it to the network processor 732 for processing.
  • the central processing unit can also perform the functions of the network processor 732, such as implementing software forwarding based on a general-purpose CPU, so that the network processor 732 is not required in the physical interface card 733.
  • the network device 700 includes multiple interface boards.
  • the network device 700 further includes an interface board 740.
  • the interface board 740 includes a central processing unit 741, a network processor 742, a forwarding entry memory 744, and a physical interface card 743.
  • the network device 700 further includes a switching network board 720.
  • the switch fabric unit 720 may also be referred to as a switch fabric unit (SFU).
  • SFU switch fabric unit
  • the switching network board 720 is used to complete data exchange between the interface boards.
  • the interface board 730 and the interface board 740 may communicate with each other through the switching network board 720.
  • the main control board 710 and the interface board 730 are coupled.
  • the main control board 710, the interface board 730, the interface board 740, and the switching network board 720 are connected to the system backplane through the system bus to achieve intercommunication.
  • an inter-process communication protocol (IPC) channel is established between the main control board 710 and the interface board 730, and the main control board 710 and the interface board 730 communicate through the IPC channel.
  • IPC inter-process communication protocol
  • the network device 700 includes a control plane and a forwarding plane.
  • the control plane includes a main control board 710 and a central processing unit 731.
  • the forwarding plane includes various components that perform forwarding, such as a forwarding entry memory 734, a physical interface card 733, and network processing. ⁇ 732.
  • the control plane performs functions such as routers, generating forwarding tables, processing signaling and protocol messages, configuring and maintaining the status of the equipment, and the control plane sends the generated forwarding tables to the forwarding plane.
  • the network processor 732 is based on the control plane.
  • the issued forwarding table looks up and forwards the message received by the physical interface card 733.
  • the forwarding table issued by the control plane can be stored in the forwarding entry storage 734. In some embodiments, the control plane and the forwarding plane can be completely separated and not on the same device.
  • the network device 700 in this embodiment may correspond to the first network device or the second network device in each of the foregoing method embodiments, and the main control board 710, interface boards 730, and/or 740 in the network device 700 may implement
  • the functions of the first network device or the second network device and/or the various steps implemented in each of the foregoing method embodiments will not be repeated here.
  • main control boards there may be one or more main control boards, and when there are more than one, it may include the main main control board and the standby main control board.
  • the switching network board may not exist, or there may be one or more. When there are more than one, the load sharing and redundant backup can be realized together. Under the centralized forwarding architecture, the network equipment does not need to switch the network board, and the interface board undertakes the processing function of the business data of the entire system.
  • the network device can have at least one switching network board, and data exchange between multiple interface boards is realized through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network devices with a distributed architecture are greater than those with a centralized architecture.
  • the form of the network device may also have only one board, that is, there is no switching network board, and the functions of the interface board and the main control board are integrated on the one board.
  • the central processing unit and the main control board on the interface board The central processing unit on the board can be combined into a central processing unit on this board to perform the functions of the two superimposed.
  • This type of equipment has low data exchange and processing capabilities (for example, low-end switches or routers and other networks) equipment).
  • the specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.
  • An embodiment of the present application also provides a path creation system, the system includes a first network device and a second network device, the first network device is used to perform the functions performed by the first network device in the embodiment shown in FIG. 3, The second network device is used to perform the functions performed by the second network device in the embodiment shown in FIG. 3.
  • An embodiment of the present application also provides a computer-readable storage medium, in which at least one instruction is stored, and the instruction is loaded and executed by a processor to implement any one of the path creation methods described above.
  • the embodiment of the present application provides a computer program.
  • the processor or the computer can execute the corresponding steps and/or processes in the foregoing method embodiments.
  • the embodiment of the present application provides a chip, including a processor, configured to call and execute instructions stored in the memory from a memory, so that a communication device installed with the chip executes the methods in the foregoing aspects.
  • the embodiment of the present application provides another chip, including: an input interface, an output interface, a processor, and a memory.
  • the input interface, the output interface, the processor, and the memory are connected by an internal connection path, and the processing
  • the processor is used to execute the code in the memory, and when the code is executed, the processor is used to execute the methods in the foregoing aspects.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium, (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk).

Landscapes

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

Abstract

本申请公开了路径创建方法、装置及系统，方法包括：第一网络设备获取用于指示路径的尾节点的目的地址、到达目的地址的路径对应的带宽和路径标识；第一网络设备向第二网络设备发送第一报文，该第一报文包括到达目的地址的路径对应的带宽、路径标识和目的地址，该第一报文用于指示第二网络设备根据带宽和路径标识创建路径信息并预留对应的资源，该第一报文包括IGP报文或BGP报文，该第二网络设备包括路径经过的网络设备或者尾节点。通过采用IGP协议或BGP协议由网络设备来动态创建路径信息并预留资源，创建路径的方式更为灵活，可靠性更高。

Description

路径创建方法、装置及系统
本申请要求于2020年06月24日提交的申请号为202010589773.3、发明名称为“路径创建方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种路径创建方法、装置及系统。
背景技术
随着网络的发展，对移动承载带宽提出了更高的需求，对电信网络接口也提出了更高的要求。由于灵活以太(flexible ethernet，FlexE)技术通过FlexE接口之间完全隔离互不影响，能够实现流量在物理层隔离，业务在同一张物理网络上进行网络分片。因此，FlexE结合网路分片能够实现资源隔离和高速传输，而如何创建路径成了亟待解决的问题。
现有技术中，由控制器进行路径计算。之后，控制器将计算好的路径通过配置的方式下发到转发器，从而实现路径的创建。
然而，由于是通过控制器进行路径计算并以静态配置的方式进行下发，因而该种路径创建的方式较为复杂，且可靠性不高。
发明内容
本申请实施例提供了一种路径创建方法、装置及系统，以克服相关技术中存在的问题。
第一方面，提供了一种路径创建方法，以第一网络设备执行该方法为例，该方法包括：第一网络设备获取目的地址、到达目的地址的路径对应的带宽和路径标识，该目的地址用于指示路径的尾节点；第一网络设备向第二网络设备发送第一报文，该第一报文包括到达目的地址的路径对应的带宽、路径标识和目的地址，该第一报文用于指示第二网络设备根据带宽和路径标识创建路径信息并预留对应的资源，该第一报文包括内部网关协议(interior gateway protocol，IGP)报文或边界网关协议(border gateway protocol，BGP)报文，该第二网络设备包括路径经过的网络设备或者尾节点。
通过采用IGP协议或BGP协议由网络设备来动态创建路径，与控制器来创建路径并静态配置的方式相比，创建路径的方式更为灵活，可靠性更高。
在一种可能的实现方式中，该路径标识包括：灵活以太FlexE标识、切片标识或段路由路径标识。
通过对多种路径标识、多种路径的支持，可以进一步提高本技术方案可用性。
在一种可能的实现方式中，该第一报文的类型包括IGP问候(Hello)报文或BGP保活(Keep alive)报文。
在一种可能的实现方式中，该第一报文的类型包括IGP Hello报文，所述第一报文的可变VARIABLE域包括扩展的TLV，所述扩展的TLV用于携带所述目的地址、所述带宽和所述路径标识。
通过采用IGP hello报文或者BGP keep alive报文，可以最大可能已有方案架构，提高本技术方案的可用性。
在一种可能的实现方式中，第一报文还包括路径列表，路径列表包括路径经过的至少一台网络设备的标识，至少一台网络设备的设备标识包括第二网络设备的标识。
在一种可能的实现方式中，路径列表为第一网络设备根据目的地址计算的目标路径。
通过在第一报文中携带路径列表，可以使得第一报文按照路径列表指示的路径进行传播，并使得路径列表中的设备能够根据路径标识、带宽等为该路径创建对应的路径信息以及预留对应的带宽等。
在一种可能的实现方式中，方法还包括：响应于路径故障，重新进行路径计算，得到更新路径列表，更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，更新后的路径所经过的至少一台网络设备的设备标识包括第三网络设备的标识；向第三网络设备发送第二报文，第二报文中携带目的地址、带宽、路径标识和更新路径列表，第二报文的类型与第一报文的类型一致。
由于在路径故障时，可及时收敛，进一步提高了创建路径的可靠性。
在一种可能的实现方式中，方法还包括：接收第二网络设备发送的第三报文，第三报文为第一报文的响应报文，第三报文用于指示路径信息创建成功；第三报文包括路径标识。
在一种可能的实现方式中，第三报文还包括段路径标识，段路径标识包括第二网络设备为路径分配的本地标识。
通过接收响应于创建路径的第一报文的第三报文，则第一网络设备可知该路径创建成功。
在一种可能的实现方式中，方法还包括：接收第二网络设备发送的第四报文，第四报文用于指示路径信息创建失败，第四报文的类型与第一报文的类型一致。
通过接收响应于创建路径的第一报文的第四报文，则第一网络设备可知该路径创建失败，进一步可以重新计算路径从而确保能够创建对应的路径，提高网络的可靠性和可用性。
在一种可能的实现方式中，第一网络设备获取目的地址、到达目的地址的路径对应的带宽和路径标识之后，还包括：第一网络设备根据带宽和路径标识预留对应的资源，包括：第一网络设备根据带宽确定第一出接口，第一出接口满足带宽的要求；第一网络设备在第一出接口预留带宽资源。
当第一网络设备与第二网络设备之间存在多个接口，但是每个接口的带宽不一致的情况下，则第一网络设备可以确定满足带宽需求的接口，并在该接口上为该路径预留资源。提高该网络的可用性。
在一种可能的实现方式中，第一报文还用于指示第二网络设备向目的地址发送与第一报文对应的第五报文，第五报文包括带宽、路径标识和目的地址，第五报文用于指示第四网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第四网络设备包括路径经过的网络设备。
在一种可能的实现方式中，第一报文还包括源地址，源地址用于指示路径的头节点，该源地址用于指示第二网络设备向头节点发送路径是否创建成功的报文。
通过在第一报文中携带用于指示路径的头节点的源地址的方式，使得该路径上的网络设备可以向头节点发送路径是否创建功能的消息。
第二方面，提供了一种路径创建方法，以第二网络设备执行该方法为例，该方法包括：第二网络设备接收第一网络设备发送的第一报文，第一报文包括目的地址、到达目的地址的路径对应的带宽和路径标识，目的地址用于指示路径的尾节点；第二网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第一报文包括IGP报文或BGP报文，第二网络设备包括路径经过的网络设备或者尾节点。
接收到采用IGP协议或BGP协议的第一报文后，根据该第一报文中的带宽和路径标识创建路径信息并预留对应的资源，与控制器来创建路径并静态配置的方式相比，创建路径的方式更为灵活，可靠性更高。
在一种可能的实现方式中，第一报文还包括路径列表，路径列表包括路径经过的至少一台网络设备的标识，至少一台网络设备的设备标识包括第二网络设备的标识。通过在第一报文中携带路径列表，使得第一报文按照路径列表指示的路径进行传播，从而使得第二网络设备能够根据路径标识、带宽等为该路径创建对应的路径信息以及预留对应的带宽等。
在一种可能的实现方式中，接收第一网络设备发送的第一报文之后，还包括：接收第一网络设备发送的第二报文，第二报文中携带目的地址、带宽、路径标识和更新路径列表，更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，更新后的路径所经过的至少一台网络设备的设备标识包括第二网络设备的标识，第二报文的类型与第一报文的类型一致；根据带宽和路径标识创建路径信息并预留对应的资源。
在一种可能的实现方式中，根据带宽和路径标识预留对应的资源之后，还包括：向第一网络设备发送第三报文，第三报文为第一报文的响应报文，第三报文用于指示路径信息创建成功；第三报文包括路径标识。
在一种可能的实现方式中，第三报文还包括段路径标识，段路径标识包括第二网络设备为路径分配的本地标识。
通过在预留对应的资源之后向第一网络设备发送响应于创建路径的第一报文的第三报文，使得第一网络设备可知该路径创建成功。
在一种可能的实现方式中，接收第一网络设备发送的第一报文之后，还包括：向第一网络设备发送第四报文，第四报文用于指示路径信息创建失败，第四报文的类型与第一报文的类型一致。
通过向第一网络设备发送响应于创建路径的第一报文的第四报文，使得第一网络设备可知该路径创建失败，进一步可以重新计算路径从而确保能够创建对应的路径，提高网络的可靠性和可用性。
在一种可能的实现方式中，根据带宽和路径标识预留对应的资源，包括：第二网络设备根据带宽确定第一出接口，第一出接口满足带宽的要求；第二网络设备在第一出接口预留带宽资源。
当第一网络设备与第二网络设备之间存在多个接口，但是每个接口的带宽不一致的情况下，则第二网络设备可以确定满足带宽需求的接口，并在该接口上为该路径预留资源，提高该网络的可用性。
在一种可能的实现方式中，接收第一网络设备发送的第一报文之后，还包括：第二网络设备向目的地址发送与第一报文对应的第五报文，第五报文包括带宽、路径标识和目的地址，第五报文用于指示第三网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第三 网络设备包括路径经过的网络设备。
第三方面，提供了一种路径创建装置，该装置包括：
处理单元，用于获取目的地址、到达目的地址的路径对应的带宽和路径标识，目的地址用于指示路径的尾节点；
发送单元，用于向第二网络设备发送第一报文，第一报文包括带宽、路径标识和目的地址，第一报文用于指示第二网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第一报文包括IGP报文或BGP报文，第二网络设备包括路径经过的网络设备或者尾节点。
在一种可能的实现方式中，第一报文还包括路径列表，路径列表包括路径经过的至少一台网络设备的标识，至少一台网络设备的设备标识包括第二网络设备的标识。
在一种可能的实现方式中，路径列表为第一网络设备根据目的地址计算的目标路径。
在一种可能的实现方式中，处理单元，还用于响应于路径故障，重新进行路径计算，得到更新路径列表，更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，更新后的路径所经过的至少一台网络设备的设备标识包括第三网络设备的标识；
发送单元，还用于向第三网络设备发送第二报文，第二报文中携带目的地址、带宽、路径标识和更新路径列表，第二报文的类型与第一报文的类型一致。
在一种可能的实现方式中，装置还包括：
第一接收单元，用于接收第二网络设备发送的第三报文，第三报文为第一报文的响应报文，第三报文用于指示路径信息创建成功，第三报文包括路径标识。
第三报文还包括段路径标识，段路径标识包括第二网络设备为路径分配的本地标识。
在一种可能的实现方式中，装置还包括：
第二接收单元，用于接收第二网络设备发送的第四报文，第四报文用于指示路径信息创建失败，第四报文的类型与第一报文的类型一致。
在一种可能的实现方式中，处理单元，还用于第一网络设备根据带宽和路径标识预留对应的资源，包括：根据带宽确定第一出接口，第一出接口满足带宽的要求；在第一出接口预留带宽资源。
在一种可能的实现方式中，第一报文还用于指示第二网络设备向目的地址发送与第一报文对应的第五报文，第五报文包括带宽、路径标识和目的地址，第五报文用于指示第四网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第四网络设备包括路径经过的网络设备。
在一种可能的实现方式中，第一报文还包括源地址，源地址用于指示路径的头节点，该源地址用于指示第二网络设备向头节点发送路径是否创建成功的报文。
第四方面，提供了一种路径创建装置，该装置包括：
接收单元，用于接收第一网络设备发送的第一报文，第一报文包括目的地址、到达目的地址的路径对应的带宽和路径标识，目的地址用于指示路径的尾节点；
处理单元，用于根据带宽和路径标识创建路径信息并预留对应的资源，第一报文包括IGP报文或BGP报文，第二网络设备包括路径经过的网络设备或者尾节点。
在一种可能的实现方式中，第一报文还包括路径列表，路径列表包括路径经过的至少一 台网络设备的标识，至少一台网络设备的设备标识包括第二网络设备的标识。
在一种可能的实现方式中，接收单元，还用于接收第一网络设备发送的第二报文，第二报文中携带目的地址、带宽、路径标识和更新路径列表，更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，更新后的路径所经过的至少一台网络设备的设备标识包括第二网络设备的标识，第二报文的类型与第一报文的类型一致；
处理单元，还用于根据带宽和路径标识预留对应的资源。
在一种可能的实现方式中，装置还包括：
第一发送单元，用于向第一网络设备发送第三报文，第三报文为第一报文的响应报文，第三报文用于指示路径信息创建成功，第三报文包括路径标识；
第三报文包括段路径标识，段路径标识包括第二网络设备为路径分配的本地标识。
在一种可能的实现方式中，装置还包括：
第二发送单元，用于向第一网络设备发送第四报文，第四报文用于指示路径信息创建失败，第四报文的类型与第一报文的类型一致。
在一种可能的实现方式中，处理单元，用于根据带宽确定第一出接口，第一出接口满足带宽的要求；在第一出接口预留带宽资源。
在一种可能的实现方式中，装置还包括：
第三发送单元，用于向目的地址发送与第一报文对应的第五报文，第五报文包括带宽、路径标识和目的地址，第五报文用于指示第三网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第三网络设备包括路径经过的网络设备。
在第一方面至第四方面中的任一方面的一种可能的实现方式中，路径标识包括：FlexE标识、切片标识或段路由路径标识。
在第一方面至第四方面中的任一方面的一种可能的实现方式中，第一报文的类型包括IGP Hello报文或BGP保活(Keep alive)报文。
在第一方面至第四方面中的任一方面的一种可能的实现方式中，第一报文的类型包括IGP Hello报文，第一报文的可变VARIABLE域包括扩展的类型长度值(type length value，TLV)，扩展的TLV用于携带目的地址、带宽和路径标识。
还提供一种路径创建设备，该设备包括：存储器及处理器，存储器中存储有至少一条指令，至少一条指令由处理器加载并执行，以实现上述第一方面任一所述的路径创建方法。
还提供一种路径创建设备，该设备包括：存储器及处理器，所述存储器中存储有至少一条指令，所述至少一条指令由所述处理器加载并执行，以实现上述第二方面任一所述的路径创建方法。
还提供了一种路径创建系统，该系统包括第一网络设备和第二网络设备，第一网络设备用于执行上述第一方面任一项所述的路径创建方法，第二网络设备用于执行上述第二方面任一项所述的路径创建方法。
还提供了一种路径创建系统，该系统包括第一网络设备和第二网络设备，第一网络设备包括如上述第三方面任一项所述的装置，第二网络设备包括如上述第四方面任一项所述的装置。
还提供了一种计算机可读存储介质，所述存储介质中存储有至少一条指令，所述指令由 处理器加载并执行以实现如上第一方面或第二方面任一所述的路径创建方法。
提供了另一种通信装置，该装置包括：收发器、存储器和处理器。其中，该收发器、该存储器和该处理器通过内部连接通路互相通信，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制收发器接收信号，并控制收发器发送信号，并且当该处理器执行该存储器存储的指令时，使得该处理器执行第一方面或第一方面的任一种可能的实施方式中的方法，或者，使得该处理器执行第二方面或第二方面的任一种可能的实施方式中的方法。
作为一种示例性实施例，所述处理器为一个或多个，所述存储器为一个或多个。
作为一种示例性实施例，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
提供了一种计算机程序(产品)，所述计算机程序(产品)包括：计算机程序代码，当所述计算机程序代码被计算机运行时，使得所述计算机执行上述各方面中的方法。
提供了一种芯片，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得安装有所述芯片的通信设备执行上述各方面中的方法。
提供另一种芯片，包括：输入接口、输出接口、处理器和存储器，所述输入接口、输出接口、所述处理器以及所述存储器之间通过内部连接通路相连，所述处理器用于执行所述存储器中的代码，当所述代码被执行时，所述处理器用于执行上述各方面中的方法。
附图说明
图1为本申请实施例提供的应用场景示意图；
图2为本申请实施例提供的FlexE场景下创建路径的示意图；
图3为本申请实施例提供的路径创建方法流程图；
图4为本申请实施例提供的IGP Hello报文的报文格式示意图；
图5为本申请实施例提供的TLV的格式示意图；
图6为本申请实施例提供的动态创建FlexE交叉隧道的过程示意图；
图7为本申请实施例提供的动态创建FlexE交叉隧道的过程示意图；
图8为本申请实施例提供的静态创建FlexE交叉隧道的过程示意图；
图9为本申请实施例提供的创建路径的过程示意图；
图10为本申请实施例提供的创建路径的过程示意图；
图11为本申请实施例提供的动态创建FlexE不交叉路径的过程示意图；
图12为本申请实施例提供的静态创建FlexE不交叉路径的过程示意图；
图13为本申请实施例提供的路径创建装置的结构示意图；
图14为本申请实施例提供的路径创建装置的结构示意图；
图15为本申请实施例提供的路径创建设备的结构示意图；
图16为本申请实施例提供的路径创建设备的结构示意图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的实施例进行解释，而非旨在限定本申请。
随着第五代移动通信系统(fifth-generation，5G)的建设，网络的发展对移动承载带宽提出了更高的需求，同时运营商也希望通过统一的网络来承载包括家庭宽带业务、专线接入业务、移动承载等各种不同的业务，这些需求对电信网络接口也提出了更高的需求。为了满足这些需求，常常需要在网络中创建路径。
创建路径的场景有多种，在FlexE场景下创建路径便是其中的一种。由于FlexE技术能够通过接口带宽隔离来实现业务隔离，FlexE接口之间可以完全隔离互不影响。因此，在FlexE场景下创建路径的需求越来越多。以图1所示的应用场景为例，在对接的两端网络设备(如图1中的R所示的路由器)之间通过加入100吉比特以太网(gigabit ethernet，GE)灵活以太组(FlexE Group)的灵活以太模式的物理接口来传输报文，能够提供长距离的传输性能。此外，标准以太物理接口能够通过命令切换为灵活以太模式的物理接口，且由标准以太物理接口切换为灵活以太模式的物理接口时，会同时生成对应的FlexE接口。
一方面，FlexE接口的带宽可以灵活指定。FlexE技术将标准以太物理接口的物理(physical，PHY)层划分多个相同的子时隙，每个子时隙对应相同的带宽，多个子时隙带宽可灵活组合成不同大小的逻辑口带宽，也就是FlexE接口的带宽。
另一方面，FlexE接口相当于独立的物理接口。在分片网络中，任何分片网络的流量、协议以及运行维护都不影响其他分片，如业务运行、网络升级、安全隔离、攻击隔离等。因此，FlexE技术能够满足网络分片的要求，使得流量在物理层隔离，业务在同一张物理网络上进行网络分片，达到一张物理网络支撑海量的不同服务等级协议(service level agreement，SLA)的定制，实现一网多用，网络价值最大化。
针对FlexE技术结合网络分片实现资源隔离和高速传输的场景，创建的路径有两种，一种是有连接的FlexE交叉路径，该FlexE交叉路径可作为一个端到端的FlexE路径。另一种是无连接的FlexE不交叉路径，该FlexE不交叉路径只是建立FlexE接口，可用于做单跳的资源隔离。
除了上述在FlexE场景下创建路径之外，还可以在其他场景创建路径。例如，在段路由(segment routing，SR)场景下创建路径，SR是基于原路由理念设计的在网络上转发数据包的一种协议。SR将网络路径分成一个个段，并且为这些段和网络中的节点分配段标识(segment identifier，SID)，该多个SID可以组成段标识列表(segment list)，通过对段和网络节点进行有序排列，就可以得到一条转发路径。
此外，SR可直接使用多协议标签交换(multi-protocol label switching，MPLS)转发面或互联网协议第6版(internet protocol version 6，IPv6)转发面。使用MPLS转发面时，称为SR-MPLS或MPLS-SR，其中，一个段(segment)就是一个标签，segment list就是标签栈。当前活跃的segment位于栈顶，处理完的segment会从栈顶弹出。在MPLS转发平面中，利用标签栈作为路径。
使用IPv6转发面时，称为基于IPv6的SR(SRv6)，其中，segment可以通过IPv6地址的格式来表达，通过IPv6地址序列来表示报文转发路径。为了基于IPv6转发面实现SRv6，新增加一种IPv6扩展头。该IPv6扩展头即是基于IPv6报文的原有路由扩展头定义的段路由头(segment routing header，SRH)，也可以称作SRH扩展头。该SRH扩展头指定一个IPv6的路径，存储的是IPv6的多个段标识。发送报文的头节点在报文中增加一个或多个SRH扩展头，中间节点就 可以按照SRH扩展头里包含的路径信息转发该IPv6报文。
无论是上述哪种创建路径的场景，当需要创建路径时，相关技术均采用由控制器进行路径计算的方式，然后由控制器将计算好的路径信息通过静态配置的方式下发到作为转发器的各个网络设备。以在图2所示的FlexE场景下创建路径为例，FlexE技术可应用在接入层(access)、汇聚层(aggregation)、核心层(core)。该FlexE场景下包括控制器、承担网络转发功能的路由器及接入路由器。控制器是网络中的集中控制设备，接入路由器用于承载网络业务接入以及网络转发功能，路由器相对控制器而言，可称为转发器。控制器计算好路径之后，向对应的网络设备下发对应的配置信息。每个网络设备的配置信息包括FlexE入口、FlexE出口和带宽等信息，从而实现FlexE路径信息的创建。由于相关技术是通过控制器进行路径计算并通过静态配置的方式下发到各个网络设备，因此，该种路径创建的方式较为复杂，且可靠性不高。
对此，本申请实施例提供了一种创建路径的方法，该方法通过IGP或BGP协议在网络设备上逐跳创建路径信息，为路径预留相应的资源，以简化路径创建的方式，提高创建路径的可靠性。
接下来，以待创建的路径上的第一网络设备和第二网络设备的交互过程为例，对本申请实施例提供的路径创建方法进行说明。如图3所示，该方法包括如下几个过程。
301，第一网络设备获取目的地址、到达目的地址的路径对应的带宽和路径标识，目的地址用于指示路径的尾节点。
在示例性实施例中，目的地址用于指示路径的尾节点。到达目的地址的路径对应的带宽可基于场景需求设置。路径标识包括但不限于FlexE标识、切片标识或段路由路径标识。示例性地，第一网络设备是到达目的地址的路径的头节点，或者，第一网络设备是到达目的地址的路径经过的网络设备。其中，到达目的地址的路径经过的网络设备也称为中间节点。本申请实施例不对第一网络设备获取目的地址、到达目的地址的路径对应的带宽和路径标识的方式进行限定，针对第一网络设备的如下两种情况，包括但不限于如下所述的几种获取方式：
情况一：第一网络设备是到达目的地址的路径的头节点。
该情况一下，可提前在第一网络设备侧配置目的地址、到达目的地址的路径对应的带宽和路径标识等信息。或者，提前在控制器配置目的地址、到达目的地址的路径对应的带宽和路径标识等信息，通过由控制器下发，或者由第一网络设备向控制器请求等方式，第一网络设备从控制器获取目的地址、到达目的地址的路径对应的带宽和路径标识等信息。
情况二：第一网络设备是到达目的地址的路径经过的网络设备。
该情况二下，虽然第一网络设备不是到达目的地址的路径的头节点，但对于到达目的地址的路径的头节点，可以通过接收到的报文中获取到目的地址、到达目的地址的路径对应的带宽和路径标识等信息，之后向下一跳节点传输目的地址、到达目的地址的路径对应的带宽和路径标识等信息，从而使得该第一网络设备获取到目的地址、到达目的地址的路径对应的带宽和路径标识等信息。
例如，第一网络设备的上一跳节点将目的地址、到达目的地址的路径对应的带宽和路径标识等信息携带在报文中发送给第一网络设备。第一网络设备通过解析报文，从而能够获取到目的地址、到达目的地址的路径对应的带宽和路径标识等信息。
302，第一网络设备向第二网络设备发送第一报文，第一报文包括带宽、路径标识和目的地址，第一报文用于指示第二网络设备根据带宽和路径标识创建路径信息并预留对应的资源， 第一报文包括IGP报文或BGP报文，第二网络设备包括路径经过的网络设备或者尾节点。
无论第一网络设备是到达目的地址的路径的头节点，还是到达目的地址的路径经过的网络设备，由于该第一网络设备不是到达目的地址的路径的尾节点，因而为了能够使得路径上的各个网络设备创建路径并预留对应的资源，第一网络设备将获取到的目的地址、带宽和路径标识向路径上的下一跳节点进行传输。示例性地，以第一网络设备的下一跳节点为第二网络设备为例，第一网络设备将目的地址、带宽和路径标识携带在第一报文中，向第二网络设备发送该第一报文，以通过第一报文指示该第二网络设备根据带宽和路径创建对应的路径信息，预留对应的资源。
在示例性实施例中，第一网络设备向第二网络设备发送第一报文之前，还包括：根据目的地址确定第二网络设备。例如，第一网络设备获取到目的地址、到达目的地址的路径对应的带宽和路径标识后，向第一网络设备计算得到的到达该目的地址的下一跳发送第一报文，该下一跳对应的设备即为第二网络设备。
或者，第一网络设备可以根据目的地址计算到达目的地址的路径，由此得到路径列表。该路径列表包括路径经过的各个网络设备的标识，第一网络设备根据该路径列表能够确定第一网络设备的下一跳是哪个网络设备，从而确定出第二网络设备。
可选地，第一网络设备根据目的地址计算到达目的地址的路径时，还可设置约束条件。例如，第一网络设备被配置了路径约束条件，或者从控制器获取到路径约束条件，则第一网络设备根据目的地址以及路径约束条件来计算到达目的地址的路径。其中，路径约束条件用于指示到达目的地址的路径所需要经过的网络设备。例如，目的地址为尾节点E的地址，如果没有路径约束条件，则第一网络设备根据目的地址计算到达尾节点E的路径时，能够到达尾节点E的路径均可以满足要求。但如果设置了路径约束条件，以路径约束条件为经过节点C为例，则第一网络设备根据目的地址计算到达尾节点E的路径时，该路径不仅要到达尾节点E，还需要经过节点C。
需要说明的是，该路径列表除了由第一网络设备根据目的地址计算得到，还可以通过预先配置来实现。例如，预先在控制器侧配置路径列表，通过由控制器下发，或者由第一网络设备向控制器请求等方式，第一网络设备从控制器获取路径列表。此外，也可提前在第一网络设备侧配置路径列表。该路径列表可以是松散路径，也可以是严格路径，本申请实施例不做限定。无论是哪种获取路径列表的方式，根据该路径列表均可确定出第二网络设备，该第二网络设备包括但不限于是路径经过的网络设备，或者路径的尾节点。
示例性地，该路径列表包括路径经过的至少一台网络设备的标识，至少一台网络设备的设备标识包括该第二网络设备的标识。本申请实施例不对第一报文所包括的路径列表的获取方式进行限定，接收到第一报文的第二网络设备根据该路径列表即可确定下一跳节点。
示例性地，该第一报文包括但不限于IGP报文或BGP报文。例如，第一报文是IGP报文，该第一报文包括但不限于是IGP Hello报文。又例如，第一报文是BGP报文，该第一报文包括但不限于是keep alive报文。
关于第一报文携带目的地址、带宽和路径标识的方式，本申请实施例不进行限定，例如，第一报文的可变(VARIABLE)域包括扩展的TLV，该扩展的TLV用于携带目的地址、带宽和路径标识。
以IGP Hello报文为例，该IGP Hello报文的报文格式如图4所示。可以通过扩展IGP Hello 报文的TLV来进行路径建立，该TLV可以携带在IGP Hello报文的VARIABLE域。该扩展的TLV用来进行路径建立，也即携带目的地址、带宽和路径标识。示例性地，第一报文还包括源地址，该源地址用于指示路径的头节点，该源地址用于指示第二网络设备向头节点发送路径是否创建成功的报文。例如，该扩展的TLV的格式如图5所示。该扩展的TLV的各个字段的含义如表1所示。表1中，带宽(Bandwidth)字段用于携带带宽，目的地址(DestAddress)字段用于携带目的地址，路径标识(PathIdentifier)字段用于携带路径标识，源地址(SourceAddress)字段用于携带源地址。
表1
Figure PCTCN2021087505-appb-000001
在示例性实施例中，第一网络设备除了向第二网络设备发送第一报文，指示第二网络设备创建对应的路径信息并预留对应的资源之外，该第一网络设备获取目的地址、到达目的地址的路径对应的带宽和路径标识之后，还包括：第一网络设备根据带宽和路径标识创建对应的路径信息，预留对应的资源。其中，创建对应的路径信息包括但不限于创建FlexE接口、分配标签或IPv6SID等。例如，路径标识为FlexE ID，则创建对应的路径信息包括创建FlexE接口。又例如，路径标签为SR MPLS，则创建对应的路径信息包括分配标签。又例如，路径标签为SRv6，则创建对应的路径信息包括分配IPv6SID。
可选地，该第一网络设备预留对应的资源，包括：第一网络设备根据带宽确定第一出接口，该第一出接口满足带宽的要求；第一网络设备在第一出接口预留带宽资源。其中，根据带宽确定第一出接口，包括但不限于根据目的地址或路径列表中的地址查询下一跳，该下一跳的数量为一个或多个。在一个或多个下一跳对应的出接口中确定满足带宽的出接口，将确定出的满足带宽的出接口作为第一出接口。示例性地，针对FlexE场景，在第一出接口预留资 源并创建FlexE接口。
303，第二网络设备接收第一网络设备发送的第一报文。
第二网络设备与第一网络设备建立网络连接，第二网络设备接收到第一网络设备发送的第一报文后，由于第一报文包括目的地址、到达目的地址的路径对应的带宽和路径标识，因而第二网络设备通过对第一报文进行解析，得到目的地址、到达目的地址的路径对应的带宽和路径标识。相应的，该第一报文还包括源地址，该源地址用于指示路径的头节点，则第二网络设备对第一报文进行解析之后，还得到源地址。需要说明的是，本申请实施例不对该第一报文包括源地址的方式进行限定，例如，第一报文的可变VARIABLE域包括扩展的TLV用于携带该源地址，除此之外，也可采用其他方式携带源地址。
示例性地，如果第一报文还包括路径列表，则第二网络设备解析第一报文后，还获取到路径列表，该路径列表包括路径经过的至少一台网络设备的标识，至少一台网络设备的设备标识包括该第二网络设备的标识。
304，第二网络设备根据带宽和路径标识创建的路径信息并预留对应的资源。
第二网络设备根据带宽和路径标识创建对应的路径信息，包括但不限于创建FlexE接口、分配标签或IPv6SID等。该第二网络设备根据带宽和路径标识创建对应的路径信息的方式可参考第一网络设备创建对应的路径信息的方式。例如，路径标识为FlexE ID，则第二网络设备创建对应的路径信息包括创建FlexE接口。又例如，路径标签为SR MPLS，则第二网络设备创建对应的路径信息包括分配标签。又例如，路径标签为SRv6，则第二网络设备创建对应的路径信息包括分配IPv6SID。
在示例性实施例中，如果第二网络设备是路径经过的网络设备，而不是路径的尾节点，则第二网络设备根据带宽和路径标识预留对应的资源，包括：第二网络设备根据带宽确定第一出接口，该第一出接口满足带宽的要求；第二网络设备在第一出接口预留带宽资源。示例性地，根据带宽确定第一出接口，包括但不限于根据目的地址或路径列表查询下一跳，该下一跳的数量为一个或多个。在一个或多个下一跳对应的出接口中确定满足带宽的出接口，将确定出的满足带宽的出接口作为第一出接口。示例性地，针对FlexE场景，在第一出接口预留资源并创建FlexE接口。此外，由于第二网络设备是路径经过的网络设备，除了确定出接口，还包括在接收第一报文的接口创建FlexE接口。如果需要创建FlexE交叉路径，则第二网络设备还包括将创建的两个FlexE接口进行连接(连接也可以称为交叉)。
在示例性实施例中，针对将路径列表携带在第一报文的情况下，如果第一网络设备检测到路径发生故障，响应于路径故障，第一网络设备重新进行路径计算，得到更新路径列表，更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，更新后的路径所经过的至少一台网络设备的设备标识包括第三网络设备的标识；第一网络设备向第三网络设备发送第二报文，第二报文中携带目的地址、带宽、路径标识和更新路径列表，第二报文的类型与第一报文的类型一致。
需要说明的是，第三网络设备是第一网络设备重新算路之后确定出的下一跳，该第三网络设备可能与第二网络设备相同，也有可能与第二网络设备不同。如果第三网络设备与第二网络设备相同，则第二网络设备接收第一网络设备发送的第二报文，根据第二报文中的带宽和路径标识创建对应的路径信息并预留对应的资源。
在示例性实施例中，第二网络设备接收到第一报文，第二网络设备根据带宽和路径标识 创建对应的路径信息并预留对应的资源之后，还包括：向第一网络设备发送第三报文，该第三报文为第一报文的响应报文，第三报文包括路径标识，第三报文用于指示路径信息创建成功；第三报文包括段路径标识，该段路径标识包括第二网络设备为路径分配的本地标识。在示例性实施例中，该第三报文还包括路径标识。通过该段路径标识，可将第一网络设备与第二网络设备之间对应的接口进行关联。相应的，第一网络设备接收第二网络设备发送的第三报文。
需要说明的是，由于段路径标识用于关联第一网络设备与第二网络设备之间对应的接口，如果通过其他方式能够对第一网络设备与第二网络设备之间对应的接口进行关联，则第三报文可不携带段路径标识。例如，如果第一网络设备和第二网络设备均以路径标识来关联第一网络设备和第二网络设备之间的接口，则第三报文还可以不包括段路径标识。第一网络设备接收到第二网络设备发送的第三报文之后，根据第三报文确定到达目的地址的路径已经建立完成。此外，第二网络设备接收到第二报文，根据带宽和路径标识创建对应的路径信息并预留对应的资源之后，还包括：向第一网络设备发送第三报文，该第三报文用于响应第二报文。
示例性地，第二网络设备向第一网络设备发送第三报文的方式，包括但不限于如下两种情况：
情况一：第二网络设备是路径的尾节点，则第二网络设备创建对应的路径信息并预留对应的资源后，生成第三报文，向第一网络设备发送该第三报文。该第三报文可携带路径标识和段路径标识，以关联第一网络设备与第二网络设备之间的接口，该第三报文还可携带路径标识。可选地，如果采用其他的接口关联方式，该第三报文也可不携带段路径标识，例如通过路径标识来关联第一网络设备与第二网络设备之间的接口。
情况二：第二网络设备不是路径的尾节点，而是路径经过的网络设备。
该情况二下，第二网络设备创建对应的路径信息并预留对应的资源后，还将向第二网络设备的下一跳发送第三报文，该第三报文也可以称为创建成功报文，这里的下一跳是指第二网络设备向第一网络设备发送第三报文的下一跳设备。第三报文可以携带该路径的头节点的地址信息。下一跳设备采用第二网络设备的处理方式，创建对应的路径信息并预留对应的资源之后，再依次向下一跳的下一跳发送创建成功报文，直至将该创建成功报文发送至该路径的头节点。
网络设备生成创建成功报文即第三报文的方式可以包括但不限于以下两种：
方式一、路径上的尾节点在创建对应的路径信息，预留相关资源之后，生成第三报文，向尾节点的上一跳发送该第三报文，该尾节点发送的第三报文包括尾节点为路径分配的本地标识，也即段路径标识，或者该第三报文中包括上述路径标识，通过该段路径标识或路径标识来关联尾节点与尾节点的上一跳之间对应的接口。之后，尾节点的上一跳按照尾节点的处理方式，继续向上一跳发送第三报文。以此类推，直至第二网络设备接收到第二网络设备的下一跳发送给第二网络设备的第三报文，该第三报文包括第二网络设备的下一跳为路径分配的本地标识，以关联第二网络设备与第二网络设备的下一跳之间的接口，或者该第三报文中包括上述路径标识，通过该路径标识来关联尾节点与尾节点的上一跳之间对应的接口。则第二网络设备向第一网络设备发送第三报文，该第三报文包括第二网络设备为路径分配的本地标识，以关联第二网络设备与第一网络设备之间对应的接口。
方式二、该路径上的中间设备或尾节点各自在创建路径信息或预留相关资源成功之后， 分别向该路径上的头节点发送路径创建成功报文，该头节点结合各设备发送的报文确定该路径创建成功。
需要说明的是，针对第二网络设备不是尾节点的情况，第二网络设备接收第一网络设备发送的第一报文之后，还包括：第二网络设备向目的地址发送与第一报文对应的第五报文，该第五报文包括带宽、路径标识和目的地址，第五报文用于指示第三网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第三网络设备包括路径经过的网络设备。例如，第三网络设备是第二网络设备在路径上的下一跳，则第二网络设备将向第二网络设备的下一跳发送第五报文。该第五报文可不携带路径列表，如果携带路径列表，则该路径列表可以不包括第二网络设备的标识，但包括第二网络设备的下一跳的标识。下一跳采用第二网络设备的处理方式，创建对应的路径信息并预留对应的资源，再依次向下一跳的下一跳发送与第一报文对应的报文，直至发送至目的地址对应的尾节点。
在示例性实施例中，第二网络设备根据带宽和路径标识未成功创建对应的路径信息或未成功预留对应的资源，则第二网络设备向第一网络设备发送第四报文，第四报文用于指示路径信息创建失败，第四报文的类型与第一报文的类型一致。相应的，第一网络设备接收第二网络设备发送的第四报文。示例性地，该第一网络设备接收到第四报文后，将创建的路径信息进行删除。例如，第一报文是IGP报文中的Hello报文，该第四报文也是IGP报文中的Hello报文，该Hello报文的Action类型字段为错误通知，标识路径创建失败。第一网络设备接收到该第二网络设备发送的Hello报文，删除创建的路径信息。如果第一网络设备还创建了FlexE接口，则将创建的FlexE接口删除。
关于第二网络设备根据带宽和路径标识未成功创建对应的路径信息的原因，本申请实施例不进行限定。例如，第二网络设备没有足够的带宽创建对应的路径信息，或者第二网络设备没有到目的地址的路由等情况下，第二网络设备均有可能创建路径信息失败。对此，第二网络设备向第一网络设备发送第四报文，以指示路径信息创建失败。
需要说明的是，以上仅以第二网络设备未成功创建对应的路径信息而向第一网络设备发送第四报文的情况为例进行说明，针对第二网络设备为路径经过的网络设备，且第二网络设备成功创建了对应的路径信息，但第二网络设备之后的网络设备未成功创建对应的路径信息的情况，则第二网络设备也会接收到第二网络设备的下一跳发送的第四报文。则第二网络设备根据该第四报文，删除创建的路径信息。如果第二网络设备还创建了FlexE接口，则将创建的FlexE接口删除。
本申请实施例提供的方法，通过采用IGP协议或BGP协议由网络设备来动态创建路径并预留对应的资源，与控制器来创建路径并静态配置的方式相比，创建路径的方式更为灵活，可靠性更高。且在路径故障时，可及时收敛，进一步提高了创建路径的可靠性。
在一些情况下，也可以根据IGP协议或BGP协议由网络设备来动态创建路径信息，而不需要预留对应的资源。
另外，本申请实施例提供的方法中，到达目的地址的路径可由控制器计算，也可由网络设备计算，算路方式更灵活。
为了便于理解本申请实施例提供的方法，接下来以通过IGP协议创建FlexE路径为例，结合如下几个场景，对本申请实施例提供的创建路径的方法进行举例说明。
场景一：动态创建FlexE交叉隧道
以图6所示的动态创建FlexE交叉隧道的过程，并成功创建FlexE交叉隧道的情况为例，对创建路径的方法进行说明。其中，上述如图3所示的方法实施例中的第一网络设备可以为图6中的设备A、设备B、设备C或设备D。第二网络设备可以为图6中的设备B、设备C、设备D、或设备E。
该方法包括但不限于如下几个过程。601，在头节点A配置或由控制器向头节点A下发创建一条FlexE交叉隧道的配置信息，该配置信息包括指定带宽、路径标识及目的地址。
如图6所示，指定带宽为2G，路径标识为全网唯一的FlexE-ID，且FlexE-ID为1000，目的地址为A2:1::1。该目的地址为节点E的地址，也即节点E为路径的尾节点。
602，头节点A根据目的地址查询路由下一跳，在下一跳对应的出接口预留资源并创建FlexE接口，并在对应的出接口发送IGP Hello报文。
如图6所示，在本场景创建的路径中，始发IGP Hello报文的节点是节点A，该节点A是该路径的头节点，而节点B、C、D是路径经过的网络设备，节点E是目的地址所指示的节点，也即该节点E是路径的尾节点。头节点A根据目的地址查询路由下一跳NHP为节点B。之后，头节点A在与节点B对应的出接口预留资源并创建FlexE接口。该Hello报文携带带宽，FlexE ID，目的地址等信息。例如，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。通过该Hello报文指示节点B创建FlexE交叉路径，路径类型为IPv6。
603，节点B接收到Hello报文，根据Hello报文的内容在接收端入接口创建FlexE接口，并根据目的地址查询下一跳，在下一跳对应的出接口创建FlexE接口并预留资源，将入和出两个FlexE接口进行交叉，继续向下一跳发送Hello报文。
如图6所示，根据目的地址查询节点B的下一跳为节点C，因此，节点B向节点C发送Hello报文。同样，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。通过该Hello报文指示节点C创建FlexE交叉路径，路径类型为IPv6。
604，节点C按照节点B的处理方式对Hello报文进行处理，以此类推，向节点D发送Hello报文，节点D也按照节点B的处理方式对Hello报文进行处理，继续向节点D的下一跳节点发送Hello报文，直到Hello报文发送的尾节点E，也即目的地址对应的节点。
605，尾节点E接收到Hello报文，创建FlexE接口成功后，向节点A发送响应于Hello报文的第三报文。
例如，通过用户网络侧接口(user networks interface，UNI)向节点A发送第三报文。该第三报文为IGP协议的创建成功消息。如图6所示，该第三报文由节点D发送到节点C，再由节点C发送到节点B，直至由节点B发送到节点A。另外，每个节点向各自的上一跳发送第三报文时，该第三报文可携带段路径标识，还可携带路径标识。例如，该段路径标识是当前节点为路径分配的本地标识，通过该本地标识或路径标识来关联两个节点之间对应的接口。
606，节点A接收到第三报文，确认路径成功建立。此时，FlexE交叉隧道建立完成。
需要说明的是，图6所示的动态创建FlexE交叉隧道的过程中，仅以节点B、C和D接收到Hello报文，创建入和出两个FlexE接口后，将两个FlexE接口交叉连接为例进行了说明。除此方式外，节点B、C和D还可在接收到Hello报文后，仅创建入和出两个FlexE接口，并不将两个FlexE接口交叉连接，而是在接收到下一跳发送的第三报文后，再将两个FlexE接口交叉连接。
另外，图6中所示的创建路径的过程针对的是成功创建FlexE交叉隧道的场景，在示例性实施例中，如果到某条链路的目标节点没有足够的带宽创建FlexE接口，或者该目标节点没有到目的地址的路由，则该目标节点可向目标节点的上一跳回复新的Hello报文，该新的Hello报文的Action类型填写为错误通知，用于指示FlexE交叉隧道创建失败。目标节点的上一跳收到该新的Hello报文后，删除已创建的FlexE接口，继续向上一跳发送新的Hello报文，直至发送到头节点A。头节点A收到该新的Hello报文后，删除已创建的FlexE接口。
场景二：动态创建FlexE交叉隧道时发生链路故障
以图7所示的动态创建FlexE交叉隧道的过程，针对创建FlexE交叉隧道发生链路故障的情况为例，对创建路径的方法进行说明，包括但不限于如下几个过程。
701，在头节点A配置或由控制器向头节点A下发创建一条FlexE交叉隧道的配置信息，该配置信息包括指定带宽、路径标识及目的地址。
如图7所示，指定带宽为2G，路径标识为全网唯一的FlexE-ID，且FlexE-ID为1000，目的地址为A2:1::1。该目的地址为节点E的地址，也即节点E为路径的尾节点。
702，头节点A根据目的地址查询路由下一跳，在下一跳对应的出接口预留资源并创建FlexE接口，并在对应的出接口发送IGP Hello报文。
如图7所示，在本场景创建的路径中，始发IGP Hello报文的节点是节点A，该节点A是该路径的头节点，而节点B、C、D是路径经过的网络设备，节点E是目的地址所指示的节点，也即该节点E是路径的尾节点。头节点A根据目的地址查询路由下一跳NHP为节点B。之后，头节点A在与节点B对应的出接口预留资源并创建FlexE接口。该Hello报文携带带宽，FlexE ID，目的地址等信息。例如，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。通过该Hello报文指示节点B创建FlexE交叉路径，路径类型为IPv6。
703，节点B接收到Hello报文，根据Hello报文的内容在接收端入接口创建FlexE接口，并根据目的地址查询下一跳，在下一跳对应的出接口创建FlexE接口并预留对应的资源，将入和出两个FlexE接口进行交叉，继续向下一跳发送Hello报文。
如图7所示，根据目的地址查询节点B的下一跳为节点C，因此，节点B向节点C发送Hello报文。同样，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。通过该Hello报文指示节点C创建FlexE交叉路径，路径类型为IPv6。
704，节点C接收到Hello报文，根据Hello报文中的目的地址查询到下一跳为节点D，确定到节点D的出接口，发现链路故障，则节点C收敛到下一跳节点F。节点C在新的出接口创建FlexE接口，向节点F发送Hello报文。
需要说明的是，节点C除了收敛到下一跳节点F，也可向头节点发送第四报文，该第四报文用于指示路径信息创建失败。该第四报文的类型与第一报文的类型一致。
705，节点F收到Hello报文后，根据Hello报文的内容在接收端入接口创建FlexE接口，并根据目的地址查询下一跳，在下一跳对应的出接口创建FlexE接口并预留对应的资源，将入和出两个FlexE接口进行交叉，继续向下一跳发送Hello报文。
如图7所示，节点F的下一跳为节点E，也即路径的尾节点。
706，尾节点E接收到Hello报文，创建FlexE接口成功后，向节点A发送响应于Hello报文的第三报文。
例如，该第三报文为IGP协议的创建成功消息。如图7所示，该第三报文由节点F发送到节点C，再由节点C发送到节点B，直至由节点B发送到节点A。另外，每个节点向各自的上一跳发送第三报文时，该第三报文可携带段路径标识，还可携带路径标识。例如，该段路径标识是当前节点为路径分配的本地标识，通过该本地标识或路径标识来关联两个节点之间对应的接口。
706，节点A接收到第三报文，确认路径成功建立。此时，FlexE交叉隧道建立完成。
场景三：静态创建FlexE交叉隧道
以图8所示的静态创建FlexE交叉隧道的过程，并成功创建FlexE交叉隧道的情况为例，对创建路径的方法进行说明，包括但不限于如下几个过程。
801，在头节点A配置或由控制器向头节点A下发创建一条FlexE交叉隧道的配置信息，该配置信息包括指定带宽、路径标识、目的地址以及显式路径列表。
如图8所示，指定带宽为2G，路径标识为全网唯一的FlexE-ID，且FlexE-ID为1000，目的地址为A2:1::1。该目的地址为节点E的地址，也即节点E为路径的尾节点。指定显式路径列表包括路径上的网络设备的标识，如图8所示的Path：A、B、C、D、E。其中，A、B、C、D、E分别代表节点A、B、C、D、E的标识。节点A是显式路径列表中的第一个节点，也即节点A是始发IGP Hello报文的头节点，而节点B、C、D是路径经过的网络设备，节点E是目的地址所指示的节点，也即该节点E是路径的尾节点。
802，头节点A根据显式路径列表查找下一跳对应的出接口，在下一跳对应的出接口预留资源并创建FlexE接口，并在下一跳对应的出接口发送IGP Hello报文。
如图8所示，头节点A根据显式路径列表查询下一跳NHP为节点B。之后，头节点A在与节点B对应的出接口预留资源并创建FlexE接口。该Hello报文携带带宽，FlexE ID，目的地址和显示路径列表。其中，头节点A向节点B发送的Hello报文中的显示路径列表不包括头节点A的标识。例如，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。
803，节点B收到Hello报文，根据Hello报文的内容在接收端入接口创建FlexE接口，并根据显示路径列表查询下一跳，在下一跳对应的出接口创建FlexE接口并预留对应的资源，将入和出两个FlexE接口进行交叉，继续向下一跳发送Hello报文。
如图8所示，根据显示路径列表查询节点B的下一跳为节点C，因此，节点B向节点C发送Hello报文。其中，节点B向节点C发送的Hello报文中的显示路径列表不包括节点B的标识。例如，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。通过该Hello报文指示节点C创建FlexE交叉路径，路径类型为IPv6。
804，节点C按照节点B的处理方式对Hello报文进行处理，以此类推，向节点D发送Hello报文，节点D也按照节点B的处理方式对Hello报文进行处理，继续向节点D的下一跳节点发送Hello报文，直到Hello报文发送的尾节点E，也即目的地址对应的节点。
805，尾节点E接收到Hello报文，创建FlexE接口成功后，向节点A发送响应于Hello报文的第三报文。
例如，该第三报文为IGP协议的创建成功消息。如图8所示，该第三报文由节点D发送到节点C，再由节点C发送到节点B，直至由节点B发送到节点A。另外，每个节点向各自的上一 跳发送第三报文时，该第三报文可携带段路径标识，还可携带路径标识。例如，该段路径标识是当前节点为路径分配的本地标识，通过该本地标识或路径标识来关联两个节点之间对应的接口。
806，节点A接收到第三报文，确认路径成功建立。此时，FlexE交叉隧道建立完成。
该场景三静态创建FlexE交叉隧道的过程相比动态创建FlexE交叉隧道的过程多指定了一条显式路径列表，逐跳建立FlexE交叉路径的时候不查路由表，而是根据路径列表进行查询，根据指定路由逐跳建立FlexE交叉接口。
场景四：网络设备计算路径，建立满足约束的FlexE路径
该场景下，由于FlexE路径需要带宽，根据带宽约束在网络设备侧例如头节点使用CSPF算法进行动态路径计算，查找一条满足带宽约束的路径。然后再由IGP协议逐跳建立路径，进行资源预留和接口创建。以图9所示的创建路径的过程为例，对创建路径的方法进行说明，包括但不限于如下几个过程。
901，在头节点A配置或由控制器向头节点A下发创建一条FlexE交叉隧道的配置信息，该配置信息包括指定带宽、路径标识及目的地址。
如图9所示，指定带宽为2G，路径标识为全网唯一的FlexE-ID，且FlexE-ID为1000，目的地址为A2:1::1。该目的地址为节点E的地址，也即节点E为路径的尾节点。
902，头节点A根据配置的目的地址，计算一条满足带宽约束的路径。
例如，如图9所示，头节点A根据配置的到目的地址A2:1::1，计算满足带宽约束的路径，得到路径列表。该路径列表包括的网络设备的标识为B、C、D、E。在本场景创建的路径中，始发IGP Hello报文的节点是节点A，该节点A是该路径的头节点，而节点B、C、D是路径经过的网络设备，节点E是目的地址所指示的节点，也即该节点E是路径的尾节点。
903，头节点A根据算出的路径查找下一跳对应的出接口，在下一跳对应的出接口预留资源并创建FlexE接口，并在下一跳对应的出接口发送IGP Hello报文。
如图9所示，头节点A根据算出的路径查询下一跳NHP为节点B。之后，头节点A在与节点B对应的出接口预留资源并创建FlexE接口。该Hello报文携带带宽，FlexE ID，目的地址和显示路径列表。其中，头节点A向节点B发送的Hello报文中的显示路径列表不包括头节点A的标识。例如，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。
904，节点B收到Hello报文，根据Hello报文的内容在接收端入接口创建FlexE接口，并根据路径列表查询下一跳，在下一跳对应的出接口创建FlexE接口并预留对应的资源，将入和出两个FlexE接口进行交叉，继续向下一跳发送Hello报文。
如图9所示，根据路径列表查询节点B的下一跳为节点C，因此，节点B向节点C发送Hello报文。其中，节点B向节点C发送的Hello报文中的路径列表不包括节点B的标识。例如，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。通过该Hello报文指示节点C创建FlexE交叉路径，路径类型为IPv6。
905，节点C按照节点B的处理方式对Hello报文进行处理，以此类推，向节点D发送Hello报文，节点D也按照节点B的处理方式对Hello报文进行处理，继续向节点D的下一跳节点发送Hello报文，直到Hello报文发送的尾节点E，也即目的地址对应的节点。
906，尾节点E接收到Hello报文，创建FlexE接口成功后，向节点A发送响应于Hello报文的第三报文。
例如，该第三报文为IGP协议的创建成功消息。如图9所示，该第三报文由节点D发送到节点C，再由节点C发送到节点B，直至由节点B发送到节点A。另外，每个节点向各自的上一跳发送第三报文时，该第三报文可携带段路径标识，还可携带路径标识。例如，该段路径标识是当前节点为路径分配的本地标识，通过该本地标识或路径标识来关联两个节点之间对应的接口。
907，节点A接收到第三报文，确认路径成功建立。此时，FlexE交叉隧道建立完成。
在该场景四种，当中间节点出现故障时，头节点A从TEDB中感知故障后可重新进行约束路径计算，得到更新的路径列表。之后，按照更新的路径列表继续创建路径。
场景五：网络设备计算路径，建立满足路径约束条件的FlexE路径
在部分场景中，用户可能希望指定FlexE路径经过某个链路和节点，其他路径不做限制。这种情况下可以通过在头节点配置FlexE的约束路径条件，并由头节点计算满足路径约束条件的FlexE路径。之后，再由IGP协议进行约束路径的建立。以图10所示的创建路径的过程为例，对创建路径的方法进行说明，包括但不限于如下几个过程。
1001，在头节点A配置或由控制器向头节点A下发创建一条FlexE交叉隧道的配置信息，该配置信息包括指定带宽、路径标识、目的地址及路径约束条件。
如图10所示，指定带宽为2G，路径标识为全网唯一的FlexE-ID，且FlexE-ID为1000，目的地址为A2:1::1。路径约束条件指示到达目的地址的路径需要包括节点F。该目的地址为节点E的地址，也即节点E为路径的尾节点。
1002，头节点根据配置的目的地址，计算一条满足带宽约束的路径，由于算路约束要求经过节点F，因此计算路径得到的路径列表包括标识B、C、F、E。在本场景创建的路径中，始发IGP Hello报文的节点是节点A，该节点A是该路径的头节点，而节点B、C、F是路径经过的网络设备，节点E是目的地址所指示的节点，也即该节点E是路径的尾节点。
1003，头节点根据算出的路径查找下一跳对应的出接口，在下一跳对应的出接口预留资源并创建FlexE接口，并在下一跳对应的出接口发送IGP Hello报文。
如图10所示，头节点A根据算出的路径查询下一跳NHP为节点B。之后，头节点A在与节点B对应的出接口预留资源并创建FlexE接口。该Hello报文携带带宽，FlexE ID，目的地址和显示路径列表。其中，头节点A向节点B发送的Hello报文中的显示路径列表不包括头节点A的标识，而是包括标识B、C、F、E。例如，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。
1004，节点B收到Hello报文，根据Hello报文的内容在接收端入接口创建FlexE接口，并根据路径列表查询下一跳，在下一跳对应的出接口创建FlexE接口并预留对应的资源，将入和出两个FlexE接口进行交叉，继续向下一跳发送Hello报文。
如图10所示，根据路径列表查询节点B的下一跳为节点C，因此，节点B向节点C发送Hello报文。其中，节点B向节点C发送的Hello报文中的路径列表不包括节点B的标识。例如，该Hello报文的扩展TLV字段的Path Type为IPv6，RES Type为FlexE Cross，Action为Create。通过该Hello报文指示节点C创建FlexE交叉路径，路径类型为IPv6。
1005，节点C按照节点B的处理方式对Hello报文进行处理，以此类推，向节点F发送Hello报文，节点F也按照节点B的处理方式对Hello报文进行处理，继续向节点F的下一跳节点发送Hello报文，直到Hello报文发送的尾节点E，也即目的地址对应的节点。
1006，尾节点E接收到Hello报文，创建FlexE接口成功后，向节点A发送响应于Hello报文的第三报文。
例如，该第三报文为IGP协议的创建成功消息。如图10所示，该第三报文由节点F发送到节点C，再由节点C发送到节点B，直至由节点B发送到节点A。另外，每个节点向各自的上一跳发送第三报文时，该第三报文可携带段路径标识，还可携带路径标识。例如，该段路径标识是当前节点为路径分配的本地标识，通过该本地标识或路径标识来关联两个节点之间对应的接口。
1007，节点A接收到第三报文，确认路径成功建立。此时，FlexE交叉隧道建立完成。
场景六：动态创建FlexE不交叉路径
创建FlexE不交叉路径时，各个节点只创建单跳路径，仅创建FlexE接口，预留资源，不做交叉连接，在IGP hello报文中携带的Res Type为FlexE。其他处理与创建FlexE交叉路径类似，可参见图6所示的创建FlexE交叉路径的过程。以图11所示的动态创建FlexE不交叉路径的过程为例，对创建路径的方法进行说明，包括但不限于如下几个过程。
1101，在头节点A配置创建一条FlexE不交叉路径的配置信息，该配置信息包括指定带宽、路径标识及目的地址。
图11示出了在一个分片创建两条FlexE不交叉路径的过程，以创建头节点A所在的路径为例，指定带宽为2G，路径标识为Slicing ID，且Slicing ID为100，目的地址为H。该目的地址为节点H的地址，也即节点H为路径的尾节点。
1102，头节点A根据目的地址查询路由下一跳，在下一跳对应的出接口预留资源并创建FlexE接口，并在对应的出接口发送IGP Hello报文。
如图11所示，在本场景创建的路径中，始发IGP Hello报文的节点是节点A，该节点A是该路径的头节点，而节点B、E、F、G是路径经过的网络设备，节点H是目的地址所指示的节点，也即该节点H是路径的尾节点。头节点A根据目的地址查询路由下一跳NHP为节点B。之后，头节点A在与节点B对应的出接口预留资源并创建FlexE接口。该Hello报文携带带宽为2G，Slicing ID为100，目的地址为节点H的地址等信息。
1103，节点B接收到Hello报文，根据Hello报文的内容在接收端入接口创建FlexE接口，并根据目的地址查询下一跳，在下一跳对应的出接口创建FlexE接口并预留对应的资源，继续向下一跳发送Hello报文。
如图11所示，根据目的地址查询节点B的下一跳为节点E，因此，节点B向节点E发送Hello报文。
1104，节点E按照节点B的处理方式对Hello报文进行处理，以此类推，向节点F发送Hello报文，节点F也按照节点B的处理方式对Hello报文进行处理，继续向节点F的下一跳节点G发送Hello报文，直到Hello报文发送的尾节点H，也即目的地址对应的节点。
需要说明的是，如图11所示，由于节点E和节点F为两条路径均经过的网络设备，在节点F有一个接口上带宽只有3G，两条路径分别是2G和3G，相同的分片可以在一个接口上共享带 宽，创建的FlexE信息中包含两个路径的信息。因此，图11中节点F所接收到的节点E发来的Hello报文包括两组信息。两组信息中的Slicing ID均为100，一组携带带宽为2G，目的地址为节点H的地址，另一组携带带宽为3G，目的地址为节点J的地址等信息。
1105，尾节点H接收到Hello报文，创建FlexE接口成功后，向节点A发送响应于Hello报文的第三报文。
例如，该第三报文为IGP协议的创建成功消息。如图11所示，该第三报文由节点G发送到节点F，再由节点F发送到节点E，再由节点E发送到节点B，直至由节点B发送到节点A。
1106，节点A接收到第三报文，确认路径成功建立。此时，FlexE不交叉路径建立完成。
场景七：静态创建FlexE不交叉路径
创建静态FlexE不交叉路径的过程与动态创建FlexE不交叉路径的区别在于静态创建FlexE不交叉路径是指定的路径，而动态创建FlexE不交叉路径是根据路由动态学习的路径。以图12所示的静态创建FlexE不交叉路径的过程，并成功创建FlexE不交叉路径的情况为例，对创建路径的方法进行说明，包括但不限于如下几个过程。
1201，在头节点A配置一条FlexE不交叉路径的配置信息，该配置信息包括指定带宽、路径标识、目的地址以及显式路径列表。
图12示出了在一个分片创建两条FlexE不交叉路径的过程，以创建头节点A所在的路径为例，指定带宽为2G，路径标识为Slicing ID，且Slicing ID为100，目的地址为H。该目的地址为节点H的地址，也即节点H为路径的尾节点。指定显式路径列表包括路径上的网络设备的标识，如图12所示的Path：A、B、E、F、G、H。其中，A、B、E、F、G、H分别代表节点A、B、E、F、G、H的标识。在本场景创建的路径中，节点A是始发IGP Hello报文的头节点，而节点B、E、F、G是路径经过的网络设备，节点H是目的地址所指示的节点，也即该节点H是路径的尾节点。
1202，头节点A根据显式路径列表查找下一跳对应的出接口，在下一跳对应的出接口预留资源并创建FlexE接口，并在下一跳对应的出接口发送IGP Hello报文。
如图12所示，头节点A根据显式路径列表查询下一跳NHP为节点B。之后，头节点A在与节点B对应的出接口预留资源并创建FlexE接口。该Hello报文携带带宽，FlexE ID，目的地址和显示路径列表。其中，头节点A向节点B发送的Hello报文中的显示路径列表不包括头节点A的标识。
1203，节点B收到Hello报文，根据Hello报文的内容在接收端入接口创建FlexE接口，并根据显示路径列表查询下一跳，在下一跳对应的出接口创建FlexE接口并预留对应的资源，继续向下一跳发送Hello报文。
如图12所示，根据显示路径列表查询节点B的下一跳为节点E，因此，节点B向节点E发送Hello报文。其中，节点B向节点E发送的Hello报文中的显示路径列表不包括节点B的标识。
1204，节点E按照节点B的处理方式对Hello报文进行处理，以此类推，向节点F发送Hello报文，节点F也按照节点B的处理方式对Hello报文进行处理，继续向节点F的下一跳节点G发送Hello报文，直到Hello报文发送的尾节点H，也即目的地址对应的节点。
需要说明的是，如图12所示，由于节点E和节点F为两条路径均经过的网络设备，在节点F有一个接口上带宽只有3G，两条路径分别是2G和3G，相同的分片可以在一个接口上共享带 宽，创建的FlexE信息中包含两个路径的信息。因此，图12中节点F所接收到的节点E发来的Hello报文包括两组信息。两组信息中的Slicing ID均为100，一组携带带宽为2G，目的地址为节点H的地址，路径列表包括的标识为F、G、H；另一组携带带宽为3G，目的地址为节点J的地址，路径列表包括的标识为F、I、J。
1205，尾节点H接收到Hello报文，创建FlexE接口成功后，向节点A发送响应于Hello报文的第三报文。
例如，该第三报文为IGP协议的创建成功消息。如图12所示，该第三报文由节点G发送到节点F，再由节点F发送到节点E，再由节点E发送到节点B，直至由节点B发送到节点A。
1206，节点A接收到第三报文，确认路径成功建立。此时，FlexE不交叉路径建立完成。
以上，示例性介绍了本申请实施例的方法示例，以下介绍本申请实施例的装置。
本申请实施例提供了一种路径创建装置，该装置用于通过图13所示的各个单元执行上述图3中第一网络设备所执行的方法。参见图13，该装置包括：
处理单元1301，用于获取目的地址、到达目的地址的路径对应的带宽和路径标识，目的地址用于指示路径的尾节点。示例性地，该处理单元1301所执行的功能可参考图3所示的301的相关描述，此处不再赘述。
发送单元1302，用于向第二网络设备发送第一报文，第一报文包括带宽、路径标识和目的地址，第一报文用于指示第二网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第一报文包括IGP报文或BGP报文，第二网络设备包括路径经过的网络设备或者尾节点。示例性地，该发送单元1302所执行的功能可参考图3所示的302的相关描述，此处不再赘述。
在一种可能的实现方式中，第一报文还包括路径列表，路径列表包括路径经过的至少一台网络设备的标识，至少一台网络设备的设备标识包括第二网络设备的标识。
在一种可能的实现方式中，路径列表为第一网络设备根据目的地址计算的目标路径。
在一种可能的实现方式中，处理单元1301，还用于响应于路径故障，重新进行路径计算，得到更新路径列表，更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，更新后的路径所经过的至少一台网络设备的设备标识包括第三网络设备的标识；
发送单元1302，还用于向第三网络设备发送第二报文，第二报文中携带目的地址、带宽、路径标识和更新路径列表，第二报文的类型与第一报文的类型一致。
在一种可能的实现方式中，装置还包括：第一接收单元，用于接收第二网络设备发送的第三报文，第三报文为第一报文的响应报文，第三报文用于指示路径信息创建成功，第三报文包括路径标识。第三报文还可以包括段路径标识，段路径标识包括第二网络设备为路径分配的本地标识。
在一种可能的实现方式中，装置还包括：第二接收单元，用于接收第二网络设备发送的第四报文，第四报文用于指示路径信息创建失败，第四报文的类型与第一报文的类型一致。
在一种可能的实现方式中，处理单元1301，还用于第一网络设备根据带宽和路径标识预留对应的资源，包括：根据带宽确定第一出接口，第一出接口满足带宽的要求；在第一出接口预留带宽资源。
在一种可能的实现方式中，第一报文还用于指示第二网络设备向目的地址发送与第一报文对应的第五报文，第五报文包括带宽、路径标识和目的地址，第五报文用于指示第四网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第四网络设备包括路径经过的网 络设备。
在一种可能的实现方式中，第一报文还包括源地址，源地址用于指示路径的头节点，该源地址用于指示第二网络设备向头节点发送路径是否创建成功的报文。
本申请实施例提供的装置，通过采用IGP协议或BGP协议由网络设备来动态创建路径并预留对应的资源，与控制器来创建路径并静态配置的方式相比，创建路径的方式更为灵活，可靠性更高。且在路径故障时，可及时收敛，进一步提高了创建路径的可靠性。
另外，本申请实施例提供的装置中，到达目的地址的路径可由控制器计算，也可由第一网络设备计算，算路方式更灵活。
本申请实施例提供了一种路径创建装置，该装置用于通过图14所示的各个单元执行上述图3中第二网络设备所执行的方法。参见图14，该装置包括：
接收单元1401，用于接收第一网络设备发送的第一报文，第一报文包括目的地址、到达目的地址的路径对应的带宽和路径标识，目的地址用于指示路径的尾节点；示例性地，该接收单元1401所执行的功能可参考图3所示的303的相关描述，此处不再赘述。
处理单元1402，用于根据带宽和路径标识创建路径信息并预留对应的资源，第一报文包括内部网关协议IGP报文或边界网关协议BGP报文，第二网络设备包括路径经过的网络设备或者尾节点。示例性地，该处理单元1402所执行的功能可参考图3所示的304的相关描述，此处不再赘述。
在一种可能的实现方式中，第一报文还包括路径列表，路径列表包括路径经过的至少一台网络设备的标识，至少一台网络设备的设备标识包括第二网络设备的标识。
在一种可能的实现方式中，接收单元1401，还用于接收第一网络设备发送的第二报文，第二报文中携带目的地址、带宽、路径标识和更新路径列表，更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，更新后的路径所经过的至少一台网络设备的设备标识包括第二网络设备的标识，第二报文的类型与第一报文的类型一致；
处理单元1402，还用于根据带宽和路径标识预留对应的资源。
在一种可能的实现方式中，装置还包括：第一发送单元，用于向第一网络设备发送第三报文，第三报文为第一报文的响应报文，第三报文用于指示路径信息创建成功；第三报文包括段路径标识，段路径标识包括第二网络设备为路径分配的本地标识。
在一种可能的实现方式中，装置还包括：第二发送单元，用于向第一网络设备发送第四报文，第四报文用于指示路径信息创建失败，第四报文的类型与第一报文的类型一致。
在一种可能的实现方式中，处理单元1402，用于根据带宽确定第一出接口，第一出接口满足带宽的要求；在第一出接口预留带宽资源。
在一种可能的实现方式中，装置还包括：第三发送单元，用于向目的地址发送与第一报文对应的第五报文，第五报文包括带宽、路径标识和目的地址，第五报文用于指示第三网络设备根据带宽和路径标识创建路径信息并预留对应的资源，第三网络设备包括路径经过的网络设备。
应理解的是，上述图13或图14提供的装置在实现其功能时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即 将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置与方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
图15为本申请实施例的路径创建设备1500的硬件结构示意图。图15所示的路径创建设备1500可以执行上述图3所示实施例提供的路径创建方法中的相应步骤。
如图15所示，路径创建设备1500包括处理器1501、存储器1502、接口1503和总线1504。其中接口1503可以通过无线或有线的方式实现，示例性地，该接口1503可以是网卡。上述处理器1501、存储器1502和接口1503通过总线1504连接。
接口1503可以包括发送器和接收器，用于与其他通信设备通信。处理器1501用于执行上述图3所示实施例中301-304的处理相关步骤。处理器1501和/或用于本文所描述的技术的其他过程。存储器1502包括操作系统15021和应用程序15022，用于存储程序、代码或指令，当处理器或硬件设备执行这些程序、代码或指令时可以完成方法实施例中涉及路径创建设备1500的处理过程。可选的，存储器1502可以包括只读存储器(英文：Read-only Memory，缩写：ROM)和随机存取存储器(英文：Random Access Memory，缩写：RAM)。其中，ROM包括基本输入/输出系统(英文：Basic Input/Output System，缩写：BIOS)或嵌入式系统；RAM包括应用程序和操作系统。当需要运行路径创建设备1500时，通过固化在ROM中的BIOS或者嵌入式系统中的bootloader引导系统进行启动，引导路径创建设备1500进入正常运行状态。在路径创建设备1500进入正常运行状态后，运行在RAM中的应用程序和操作系统，从而，完成方法实施例中涉及路径创建设备1500的处理过程。
可以理解的是，图15仅仅示出了路径创建设备1500的简化设计。在实际应用中，路径创建设备1500可以包含任意数量的接口，处理器或者存储器。
应理解的是，上述处理器可以是中央处理器(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processing，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field－programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者是任何常规的处理器等。值得说明的是，处理器可以是支持进阶精简指令集机器(advanced RISC machines，ARM)架构的处理器。
进一步地，在一种可选的实施例中，上述存储器可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。
该存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用。例如，静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic random access memory，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data date  SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
参见附图16，附图16示出了本申请一个示例性实施例提供的网络设备700的结构示意图，该网络设备700可以配置为上述方法实施例中的第一网络设备或第二网络设备。网络设备700包括：主控板710和接口板730。
主控板也称为主处理单元(main processing unit，MPU)或路由处理卡(route processor card)，主控板710用于对网络设备700中各个组件的控制和管理，包括路由计算、设备管理、设备维护、协议处理功能。主控板710包括：中央处理器711和存储器712。
接口板730也称为线路接口单元卡(line processing unit，LPU)、线卡(line card)或业务板。接口板730用于提供各种业务接口并实现数据包的转发。业务接口包括而不限于以太网接口、POS(Packet over SONET/SDH)接口等，以太网接口例如是灵活以太网业务接口(Flexible Ethernet Clients，FlexE Clients)。接口板730包括：中央处理器731、网络处理器732、转发表项存储器734和物理接口卡(physical interface card，PIC)733。
接口板730上的中央处理器731用于对接口板730进行控制管理并与主控板710上的中央处理器711进行通信。
网络处理器732用于实现报文的转发处理。网络处理器732的形态可以是转发芯片。具体而言，网络处理器732用于基于转发表项存储器734保存的转发表转发接收到的报文，如果报文的目的地址为网络设备700的地址，则将该报文上送至CPU(如中央处理器711)处理；如果报文的目的地址不是网络设备700的地址，则根据该目的地址从转发表中查找到该目的地址对应的下一跳和出接口，将该报文转发到该目的地址对应的出接口。其中，上行报文的处理包括：报文入接口的处理，转发表查找；下行报文的处理：转发表查找等等。
物理接口卡733用于实现物理层的对接功能，原始的流量由此进入接口板730，以及处理后的报文从该物理接口卡733发出。物理接口卡733也称为子卡，可安装在接口板730上，负责将光电信号转换为报文并对报文进行合法性检查后转发给网络处理器732处理。在一些实施例中，中央处理器也可执行网络处理器732的功能，比如基于通用CPU实现软件转发，从而物理接口卡733中不需要网络处理器732。
可选地，网络设备700包括多个接口板，例如网络设备700还包括接口板740，接口板740包括：中央处理器741、网络处理器742、转发表项存储器744和物理接口卡743。
可选地，网络设备700还包括交换网板720。交换网板720也可以称为交换网板单元(switch fabric unit，SFU)。在网络设备有多个接口板730的情况下，交换网板720用于完成各接口板之间的数据交换。例如，接口板730和接口板740之间可以通过交换网板720通信。
主控板710和接口板730耦合。例如。主控板710、接口板730和接口板740，以及交换网板720之间通过系统总线与系统背板相连实现互通。在一种可能的实现方式中，主控板710和接口板730之间建立进程间通信协议(inter-process communication，IPC)通道，主控板710和接口板730之间通过IPC通道进行通信。
在逻辑上，网络设备700包括控制面和转发面，控制面包括主控板710和中央处理器731，转发面包括执行转发的各个组件，比如转发表项存储器734、物理接口卡733和网络处理器732。控制面执行路由器、生成转发表、处理信令和协议报文、配置与维护设备的状态等功能， 控制面将生成的转发表下发给转发面，在转发面，网络处理器732基于控制面下发的转发表对物理接口卡733收到的报文查表转发。控制面下发的转发表可以保存在转发表项存储器734中。在有些实施例中，控制面和转发面可以完全分离，不在同一设备上。
应理解，本实施例的网络设备700可对应于上述各个方法实施例中的第一网络设备或第二网络设备，该网络设备700中的主控板710、接口板730和/或740可以实现上述各个方法实施例中的第一网络设备或第二网络设备所具有的功能和/或所实施的各种步骤，为了简洁，在此不再赘述。
值得说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的网络设备的数据接入和处理能力要大于集中式架构的设备。可选地，网络设备的形态也可以是只有一块板卡，即没有交换网板，接口板和主控板的功能集成在该一块板卡上，此时接口板上的中央处理器和主控板上的中央处理器在该一块板卡上可以合并为一个中央处理器，执行两者叠加后的功能，这种形态设备的数据交换和处理能力较低(例如，低端交换机或路由器等网络设备)。具体采用哪种架构，取决于具体的组网部署场景，此处不做任何限定。
本申请实施例还提供了一种路径创建系统，该系统包括第一网络设备和第二网络设备，第一网络设备用于执行图3所示实施例中的第一网络设备所执行的功能，第二网络设备用于执行图3所示实施例中的第二网络设备所执行的功能。
本申请实施例还提供了一种计算机可读存储介质，存储介质中存储有至少一条指令，指令由处理器加载并执行以实现如上任一所述的路径创建方法。
本申请实施例提供了一种计算机程序，当计算机程序被计算机执行时，可以使得处理器或计算机执行上述方法实施例中对应的各个步骤和/或流程。
本申请实施例提供了一种芯片，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得安装有所述芯片的通信设备执行上述各方面中的方法。
本申请实施例提供另一种芯片，包括：输入接口、输出接口、处理器和存储器，所述输入接口、输出接口、所述处理器以及所述存储器之间通过内部连接通路相连，所述处理器用于执行所述存储器中的代码，当所述代码被执行时，所述处理器用于执行上述各方面中的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站 站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk)等。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。

Claims (31)

  1. 一种路径创建方法，其特征在于，所述方法包括：
    第一网络设备获取目的地址、到达所述目的地址的路径对应的带宽和路径标识，所述目的地址用于指示所述路径的尾节点；
    所述第一网络设备向第二网络设备发送第一报文，所述第一报文包括所述带宽、所述路径标识和所述目的地址，所述第一报文用于指示所述第二网络设备根据所述带宽和所述路径标识创建路径信息并预留对应的资源，所述第一报文包括内部网关协议IGP报文或边界网关协议BGP报文，所述第二网络设备包括所述路径经过的网络设备或者尾节点。
  2. 根据权利要求1所述的方法，其特征在于，所述路径标识包括：灵活以太FlexE标识、切片标识或段路由路径标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一报文的类型包括IGP问候Hello报文或BGP保活Keep alive报文。
  4. 根据权利要求3所述的方法，其特征在于，所述第一报文的类型包括IGP Hello报文，所述第一报文的可变VARIABLE域包括扩展的TLV，所述扩展的TLV用于携带所述目的地址、所述带宽和所述路径标识。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述第一报文还包括路径列表，所述路径列表包括所述路径经过的至少一台网络设备的标识，所述至少一台网络设备的设备标识包括所述第二网络设备的标识。
  6. 根据权利要求5所述的方法，其特征在于，所述路径列表为所述第一网络设备根据所述目的地址计算的目标路径。
  7. 根据权利要求5或6所述的方法，其特征在于，所述方法还包括：
    响应于所述路径故障，重新进行路径计算，得到更新路径列表，所述更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，所述更新后的路径所经过的至少一台网络设备的设备标识包括第三网络设备的标识；
    向所述第三网络设备发送第二报文，所述第二报文中携带所述目的地址、所述带宽、所述路径标识和所述更新路径列表，所述第二报文的类型与所述第一报文的类型一致。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述方法还包括：
    接收所述第二网络设备发送的第三报文，所述第三报文为所述第一报文的响应报文，所述第三报文包括所述路径标识，所述第三报文用于指示所述路径信息创建成功。
  9. 根据权利要求8所述的方法，其特征在于，所述第三报文还包括段路径标识，所述段路径标识包括所述第二网络设备为所述路径分配的本地标识。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述第一网络设备获取目的地址、到达所述目的地址的路径对应的带宽和路径标识之后，还包括：
    所述第一网络设备根据所述带宽和所述路径标识预留对应的资源，包括：
    所述第一网络设备根据所述带宽确定第一出接口，所述第一出接口满足所述带宽的要求；
    所述第一网络设备在所述第一出接口预留所述带宽资源。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述第一报文还用于指示所述第二网络设备向所述目的地址发送与所述第一报文对应的第五报文，所述第五报文包括所述带宽、所述路径标识和所述目的地址，所述第五报文用于指示第四网络设备根据所述带宽和所述路径标识创建路径信息并预留对应的资源，所述第四网络设备包括所述路径经过的网络设备。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述第一报文还包括源地址，所述源地址用于指示所述路径的头节点，所述源地址用于指示所述第二网络设备向所述头节点发送路径是否创建成功的报文。
  13. 一种路径创建方法，其特征在于，所述方法包括：
    第二网络设备接收第一网络设备发送的第一报文，所述第一报文包括目的地址、到达所述目的地址的路径对应的带宽和路径标识，所述目的地址用于指示所述路径的尾节点；
    所述第二网络设备根据所述带宽和所述路径标识创建路径信息并预留对应的资源，所述第一报文包括内部网关协议IGP报文或边界网关协议BGP报文，所述第二网络设备包括所述路径经过的网络设备或者尾节点。
  14. 根据权利要求13所述的方法，其特征在于，所述第一报文还包括路径列表，所述路径列表包括所述路径经过的至少一台网络设备的标识，所述至少一台网络设备的设备标识包括所述第二网络设备的标识。
  15. 根据权利要求14所述的方法，其特征在于，所述接收第一网络设备发送的第一报文之后，还包括：
    接收所述第一网络设备发送的第二报文，所述第二报文中携带所述目的地址、所述带宽、所述路径标识和更新路径列表，所述更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，所述更新后的路径所经过的至少一台网络设备的设备标识包括所述第二网络设备的标识，所述第二报文的类型与所述第一报文的类型一致；
    根据所述带宽和所述路径标识创建路径信息并预留对应的资源。
  16. 根据权利要求13-15任一项所述的方法，其特征在于，所述根据所述带宽和所述路径标 识预留对应的资源之后，还包括：
    向所述第一网络设备发送第三报文，所述第三报文为所述第一报文的响应报文，所述第三报文包括所述路径标识，所述第三报文用于指示所述路径信息创建成功。
  17. 根据权利要求16所述的方法，其特征在于，所述第三报文还包括段路径标识，所述段路径标识包括所述第二网络设备为所述路径分配的本地标识。
  18. 根据权利要求13-17任一项所述的方法，其特征在于，所述根据所述带宽和所述路径标识预留对应的资源，包括：
    所述第二网络设备根据所述带宽确定第一出接口，所述第一出接口满足所述带宽的要求；
    所述第二网络设备在所述第一出接口预留所述带宽资源。
  19. 根据权利要求13-18任一项所述的方法，其特征在于，所述接收第一网络设备发送的第一报文之后，还包括：
    所述第二网络设备向所述目的地址发送与所述第一报文对应的第五报文，所述第五报文包括所述带宽、所述路径标识和所述目的地址，所述第五报文用于指示第三网络设备根据所述带宽和所述路径标识创建路径信息并预留对应的资源，所述第三网络设备包括所述路径经过的网络设备。
  20. 一种路径创建装置，其特征在于，所述装置包括：
    处理单元，用于获取目的地址、到达所述目的地址的路径对应的带宽和路径标识，所述目的地址用于指示所述路径的尾节点；
    发送单元，用于向第二网络设备发送第一报文，所述第一报文包括所述带宽、所述路径标识和所述目的地址，所述第一报文用于指示所述第二网络设备根据所述带宽和所述路径标识创建路径信息并预留对应的资源，所述第一报文包括内部网关协议IGP报文或边界网关协议BGP报文，所述第二网络设备包括所述路径经过的网络设备或者尾节点。
  21. 根据权利要求20所述的装置，其特征在于，所述处理单元，还用于响应于所述路径故障，重新进行路径计算，得到更新路径列表，所述更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，所述更新后的路径所经过的至少一台网络设备的设备标识包括第三网络设备的标识；
    所述发送单元，还用于向所述第三网络设备发送第二报文，所述第二报文中携带所述目的地址、所述带宽、所述路径标识和所述更新路径列表，所述第二报文的类型与所述第一报文的类型一致。
  22. 根据权利要求20或21所述的装置，其特征在于，所述装置还包括：
    第一接收单元，用于接收第二网络设备发送的第三报文，所述第三报文为所述第一报文的响应报文，所述第三报文包括所述路径标识，所述第三报文用于指示所述路径信息创建成功。
  23. 根据权利要求20或21所述的装置，其特征在于，所述装置还包括：
    第二接收单元，用于接收第二网络设备发送的第四报文，所述第四报文用于指示所述路径信息创建失败，所述第四报文的类型与所述第一报文的类型一致。
  24. 根据权利要求20-23任一项所述的装置，其特征在于，所述处理单元，还用于所述第一网络设备根据所述带宽和所述路径标识预留对应的资源，包括：根据所述带宽确定第一出接口，所述第一出接口满足所述带宽的要求；在所述第一出接口预留所述带宽资源。
  25. 一种路径创建装置，其特征在于，所述装置包括：
    接收单元，用于接收第一网络设备发送的第一报文，所述第一报文包括目的地址、到达所述目的地址的路径对应的带宽和路径标识，所述目的地址用于指示所述路径的尾节点；
    处理单元，用于根据所述带宽和所述路径标识创建路径信息并预留对应的资源，所述第一报文包括内部网关协议IGP报文或边界网关协议BGP报文，所述第二网络设备包括所述路径经过的网络设备或者尾节点。
  26. 根据权利要求25所述的装置，其特征在于，所述接收单元，还用于接收所述第一网络设备发送的第二报文，所述第二报文中携带所述目的地址、所述带宽、所述路径标识和更新路径列表，所述更新路径列表包括更新后的路径所经过的至少一台网络设备的标识，所述更新后的路径所经过的至少一台网络设备的设备标识包括所述第二网络设备的标识，所述第二报文的类型与所述第一报文的类型一致；
    所述处理单元，还用于根据所述带宽和所述路径标识预留对应的资源。
  27. 根据权利要求25或26所述的装置，其特征在于，所述装置还包括：
    第一发送单元，用于向所述第一网络设备发送第三报文，所述第三报文为所述第一报文的响应报文，所述第三报文用于指示所述路径信息创建成功；
    所述第三报文包括段路径标识，所述段路径标识包括所述第二网络设备为所述路径分配的本地标识。
  28. 根据权利要求25或26所述的装置，其特征在于，所述装置还包括：
    第二发送单元，用于向所述第一网络设备发送第四报文，所述第四报文用于指示所述路径信息创建失败，所述第四报文的类型与所述第一报文的类型一致。
  29. 根据权利要求25-28任一项所述的装置，其特征在于，所述处理单元，用于根据所述带宽确定第一出接口，所述第一出接口满足所述带宽的要求；在所述第一出接口预留所述带宽资源。
  30. 根据权利要求25-29任一项所述的装置，其特征在于，所述装置还包括：
    第三发送单元，用于向所述目的地址发送与所述第一报文对应的第五报文，所述第五报 文包括所述带宽、所述路径标识和所述目的地址，所述第五报文用于指示第三网络设备根据所述带宽和所述路径标识创建路径信息并预留对应的资源，所述第三网络设备包括所述路径经过的网络设备。
  31. 一种路径创建系统，其特征在于，所述系统包括第一网络设备和第二网络设备，所述第一网络设备包括如上述权利要求20-24任一项所述的装置，所述第二网络设备包括如上述权利要求25-30任一项所述的装置。
PCT/CN2021/087505 2020-06-24 2021-04-15 路径创建方法、装置及系统 WO2021258823A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010589773.3 2020-06-24
CN202010589773.3A CN113839870B (zh) 2020-06-24 2020-06-24 路径创建方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2021258823A1 true WO2021258823A1 (zh) 2021-12-30

Family

ID=78964599

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/087505 WO2021258823A1 (zh) 2020-06-24 2021-04-15 路径创建方法、装置及系统

Country Status (2)

Country Link
CN (1) CN113839870B (zh)
WO (1) WO2021258823A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116094821A (zh) * 2023-01-29 2023-05-09 中国联合网络通信集团有限公司 一种路由配置方法及装置
CN116319549A (zh) * 2023-05-18 2023-06-23 新华三技术有限公司 分布式流量调度方法及装置
WO2023174288A1 (zh) * 2022-03-18 2023-09-21 华为技术有限公司 通信方法、装置、系统及存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114615136B (zh) * 2022-03-04 2023-10-27 浙江国盾量子电力科技有限公司 一种5G智能电网切片的FlexE接口管理方法
CN115174414A (zh) * 2022-07-22 2022-10-11 科来网络技术股份有限公司 自动识别会话中设备、设备路径的方法、系统及电子设备
CN117527680A (zh) * 2022-07-29 2024-02-06 华为技术有限公司 一种资源预留路径建立、通信方法及装置
CN118055455A (zh) * 2022-11-17 2024-05-17 华为技术有限公司 一种资源配置方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107612825A (zh) * 2017-08-04 2018-01-19 华为技术有限公司 建立灵活以太网路径的方法和网络设备
US10382167B2 (en) * 2016-12-13 2019-08-13 Ciena Corporation Flexible ethernet enhanced forward error correction
CN110247787A (zh) * 2018-03-08 2019-09-17 中兴通讯股份有限公司 一种灵活以太网路径建立的方法、网元和控制设备
WO2020024906A1 (zh) * 2018-07-30 2020-02-06 中兴通讯股份有限公司 路径标识传输方法和装置、计算机可读存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101588296B (zh) * 2009-06-16 2011-09-07 杭州华三通信技术有限公司 一种转发组播报文的方法、头节点和尾节点
CN106803814B (zh) * 2015-11-26 2021-01-22 中兴通讯股份有限公司 一种灵活以太网路径的建立方法、装置及系统
CN107204941A (zh) * 2016-03-18 2017-09-26 中兴通讯股份有限公司 一种灵活以太网路径建立的方法和装置
CN110417651B (zh) * 2018-04-28 2021-07-16 华为技术有限公司 一种隧道建立方法、装置及系统
CN110677918B (zh) * 2018-07-03 2021-07-23 中国电信股份有限公司 链路状态信息转发方法、系统及装置
CN110944357B (zh) * 2018-09-25 2023-08-29 中兴通讯股份有限公司 一种网络切片的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10382167B2 (en) * 2016-12-13 2019-08-13 Ciena Corporation Flexible ethernet enhanced forward error correction
CN107612825A (zh) * 2017-08-04 2018-01-19 华为技术有限公司 建立灵活以太网路径的方法和网络设备
CN110247787A (zh) * 2018-03-08 2019-09-17 中兴通讯股份有限公司 一种灵活以太网路径建立的方法、网元和控制设备
WO2020024906A1 (zh) * 2018-07-30 2020-02-06 中兴通讯股份有限公司 路径标识传输方法和装置、计算机可读存储介质

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023174288A1 (zh) * 2022-03-18 2023-09-21 华为技术有限公司 通信方法、装置、系统及存储介质
CN116094821A (zh) * 2023-01-29 2023-05-09 中国联合网络通信集团有限公司 一种路由配置方法及装置
CN116094821B (zh) * 2023-01-29 2024-05-14 中国联合网络通信集团有限公司 一种路由配置方法及装置
CN116319549A (zh) * 2023-05-18 2023-06-23 新华三技术有限公司 分布式流量调度方法及装置
CN116319549B (zh) * 2023-05-18 2023-08-18 新华三技术有限公司 分布式流量调度方法及装置

Also Published As

Publication number Publication date
CN113839870A (zh) 2021-12-24
CN113839870B (zh) 2023-01-13

Similar Documents

Publication Publication Date Title
WO2021258823A1 (zh) 路径创建方法、装置及系统
US11677587B2 (en) EVPN packet processing method, device, and system for mac learning via MAC/IP advertisement route
US11606292B2 (en) Route processing method, device, and system
US11799773B2 (en) EVPN packet processing method, device, and system
US20220407802A1 (en) Packet processing method and apparatus, network device, and storage medium
US10554542B2 (en) Label distribution method and device
US11349687B2 (en) Packet processing method, device, and system
US20220124023A1 (en) Path Switching Method, Device, and System
US20220124033A1 (en) Method for Controlling Traffic Forwarding, Device, and System
WO2023045871A1 (zh) 报文处理方法、网络设备及系统
WO2022194023A1 (zh) 报文处理的方法、网络设备及控制器
WO2022048418A1 (zh) 一种转发报文的方法、设备和系统
US20230412508A1 (en) Packet processing method and related apparatus
WO2020114083A1 (zh) 一种ioam信息的处理方法和装置
CN117097818A (zh) 一种报文处理的方法及相关设备
CN114258109A (zh) 一种路由信息传输方法及装置
WO2022048381A1 (zh) 一种报文传输方法及装置
CN114629834B (zh) 通信方法及装置
CN112104539B (zh) 分段ngmvpn中的信息交互方法、装置和系统
WO2022143572A1 (zh) 一种报文处理方法及相关设备
WO2024104171A1 (zh) 一种资源配置方法和装置
WO2022166464A1 (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: 21829338

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21829338

Country of ref document: EP

Kind code of ref document: A1