WO2019024930A1 - 建立灵活以太网路径的方法和网络设备 - Google Patents

建立灵活以太网路径的方法和网络设备 Download PDF

Info

Publication number
WO2019024930A1
WO2019024930A1 PCT/CN2018/098610 CN2018098610W WO2019024930A1 WO 2019024930 A1 WO2019024930 A1 WO 2019024930A1 CN 2018098610 W CN2018098610 W CN 2018098610W WO 2019024930 A1 WO2019024930 A1 WO 2019024930A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
node
flexe
time slot
forwarding node
Prior art date
Application number
PCT/CN2018/098610
Other languages
English (en)
French (fr)
Inventor
杜宗鹏
陈国义
董杰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18841043.5A priority Critical patent/EP3641242B1/en
Publication of WO2019024930A1 publication Critical patent/WO2019024930A1/zh
Priority to US16/749,506 priority patent/US11228526B2/en

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/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • 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/34—Source routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246—Connectivity information discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0051—Network Node Interface, e.g. tandem connections, transit switching
    • H04J2203/0053—Routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0057—Operations, administration and maintenance [OAM]
    • H04J2203/0058—Network management, e.g. Intelligent nets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Definitions

  • the present application relates to the field of flexible Ethernet and, more particularly, to a method and network device for establishing a flexible Ethernet (FlexE) path.
  • Flexible Ethernet Flexible Ethernet
  • Flexible Ethernet is an Ethernet technology developed on the basis of traditional Ethernet. FlexE technology enables bandwidth isolation of different flexible Ethernet client (FlexE Client) services on the port. Therefore, this technology can also be applied to Internet Protocol (IP) Ethernet networks to guarantee specific Quality of Service (QoS) of the service.
  • IP Internet Protocol
  • QoS Quality of Service
  • Node 11, Node 13, Node 14, Node 16, and Node 17 are connected by FlexE, and can be established by establishing an end-to-end FlexE path (or Channel) between Node 13 and Node 16 of Node 14.
  • the source node is the node 11 and the destination node is the service stream 2 of the node 17, which can provide exclusive bandwidth guarantee and service isolation for the service flow 1 and the service flow 2, and guarantee the QoS of the service flow 1 and the service flow 2.
  • the present application provides a method and network device for establishing a FlexE path, which can reduce the management complexity of the control plane of the node and the signaling overhead required to maintain the FlexE path.
  • a method for establishing a FlexE path including: a first forwarding node receives a first path setup request message sent by a first source node, where the first path setup request message is used to establish a first source node to the first a first FlexE path between the destination nodes, where the first FlexE path is used to transmit the first service flow, the first path setup request message includes first routing information, where the first routing information is used to indicate node information on the first FlexE path, The first forwarding node on the first FlexE path is an upstream node of the second forwarding node on the first FlexE path; the first forwarding node establishes the first forwarding node to the second forwarding node according to the first path establishment request message.
  • the second FlexE path can satisfy the bandwidth requirement of the first service flow and the bandwidth requirement of the second service flow; the first forwarding node establishes and saves the first FlexE path and the first The correspondence between the two FlexE paths is such that the first traffic flow and the second traffic flow are mapped to time slots of the second FlexE path.
  • the method for establishing a flexible Ethernet path in the embodiment of the present application on the basis that the third FlexE path for transmitting the second service flow has been established, if the first service flow needs to be transmitted, the first forwarding node may be re-established to the second Forwarding the second FlexE path between the nodes, and merging the first service flow and the second service flow to the second FlexE path for forwarding, and deleting the third FlexE path, so that the first forwarding node and the second forwarding node can be reduced.
  • the first path establishment request message may further include path type information, where the path type information is used to indicate that the established path type is a FlexE path.
  • the path type that each node needs to establish by default may be a FlexE path.
  • the path establishment request message such as the first path establishment request message and the second path establishment request message, may be a Path message in a Resource Reservation Protocol-Traffic Engineering (RSVP).
  • RSVP Resource Reservation Protocol-Traffic Engineering
  • the embodiment of the present application is not limited to the Path message.
  • the method of the present application can be implemented using an existing protocol, and system compatibility can be improved.
  • the second FlexE path multiplexes a session established when the third FlexE path is established.
  • a session is established (for example, as a second session).
  • the second FlexE path can be established based on the second session, that is, the second FlexE path and The second session corresponds.
  • the time slot resource for transmitting the second service flow on the second FlexE path is the same as the time slot resource for transmitting the second service flow on the third FlexE path.
  • the time slot resource used for transmitting the second service flow in the slot resource reserved by the second FlexE path is the same as the reserved time slot resource of the third FlexE path.
  • the first forwarding node establishes and saves a correspondence between the first FlexE path and the second FlexE path, where the first forwarding node sends the next forwarding node to the next node of the first forwarding node on the second FlexE path.
  • a second path establishment request message where the second path establishment request message includes second routing information, where the second routing information is used to indicate node information on the second FlexE path, so that the next node of the first forwarding node is configured according to the second routing information.
  • the first forwarding node receives a second resource reservation message sent by the next node of the first forwarding node according to the second path establishment request message; the first forwarding node determines the first according to the second resource reservation message a first time slot resource on the second FlexE path, and establishing and storing a correspondence between the first time slot resource, the first FlexE path, and the second FlexE path, so that the first service carried on the first FlexE path
  • the flow is mapped to a time slot corresponding to the first time slot resource.
  • the resource reservation message such as the first resource reservation message and the second resource reservation message, may be a Resv message in the RSVP, but the embodiment of the present application is not limited to the Resv message.
  • the first time slot resource may be determined by a next node of the first forwarding node, and the next node of the first forwarding node may carry the indication information of the first time slot resource in the second resource reservation message.
  • the first forwarding node may determine the first time slot resource according to the indication information.
  • the indication information may be a Generalized Multiprotocol Label Switching (GMPLS) label, and the GMPLS label is used to indicate the first time slot resource. It should be understood that the GMPLS label can simultaneously indicate the time slot resources used to transmit the second traffic flow on the previous third FlexE path. It should be understood that the application is not limited to the indication information being a GMPLS label.
  • GMPLS Generalized Multiprotocol Label Switching
  • the first forwarding node may change the next forwarding node by using an inband control channel with the next node of the first forwarding node.
  • the FlexE configuration on the ingress interface of the node achieves the purpose of changing the slot configuration of the second FlexE path.
  • the method may further include: the first forwarding node receives a third path setup request message, where the third path setup request message is used to establish a fourth between the second source node and the second destination node.
  • a FlexE path the fourth FlexE path is used to transmit the third service flow
  • the third path establishment request message includes third routing information
  • the third routing information is used to indicate node information on the fourth FlexE path, where the fourth FlexE path is The next node of the first forwarding node is the second destination node; the first forwarding node sends a third path establishment request message to the second destination node; the first forwarding node receives the second destination node according to the third path establishment request message.
  • the first forwarding node determines a third time slot resource according to the third resource reservation message; the first forwarding node establishes and saves the third time slot resource and the fourth time slot resource on the fifth FlexE path Corresponding relationship, so that the first forwarding node maps the third service flow mapped to the time slot corresponding to the fourth time slot resource to the third time slot resource a time slot, wherein the fifth FlexE path is a FlexE path between the second forwarding node and the first forwarding node, and the time slot corresponding to the third time slot resource is used for transmitting the third service flow on the fifth FlexE path. Time slot.
  • the first forwarding node may perform the previous one of the first source node on the fourth FlexE path according to the correspondence between the third time slot resource and the fourth time slot resource on the fifth FlexE path.
  • the third service flow that is mapped by the node to the time slot corresponding to the fourth time slot resource is mapped to the time slot corresponding to the third time slot resource for transmission.
  • the second source node and the second destination node may be the first destination node and the first source node, respectively, and then the fourth FlexE path is the FlexE between the first destination node and the first source node.
  • the path, the fifth FlexE path is a path between the second forwarding node to the first forwarding node, and the fifth FlexE path path can be considered as part of the fourth FlexE path.
  • a network device comprising means for performing the method of the first aspect or various possible implementations of the first aspect.
  • a network device comprising a memory, a processor, and a communication interface, the memory for storing program code, the processor for executing program code stored in the memory to perform the first aspect or The operations corresponding to the methods in the various possible implementations of the first aspect.
  • a computer readable medium storing program code, the program code comprising instructions for performing the method of the first aspect or various possible implementations of the first aspect.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect or the various possible implementations of the first aspect.
  • Figure 1 is an architectural diagram of an existing flexible Ethernet.
  • FIG. 2 is an exemplary diagram of a conventional traffic flow process of a flexible Ethernet.
  • FIG. 3 is a schematic diagram of a system architecture applied to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of establishing a flexible Ethernet path according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of establishing a flexible Ethernet path according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of establishing a flexible Ethernet path according to another embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a network device according to another embodiment of the present application.
  • a network device such as a first source node, a first destination node, and a first forwarding node, may be a router or a switch.
  • next node of node A refers to a node that is directly connected to the node A and is a downstream node of the node A along the direction of the FlexE path.
  • next node of the first forwarding node refers to a node that is directly connected to the first forwarding node through the FlexE and is the downstream node of the first forwarding node. It should be understood that there is no intermediate node between node A and the next node of node A along the direction of the FlexE path.
  • the "previous node of node A" in the present application refers to a node that is directly connected to the node A through the FlexE along the direction of the FlexE path and is the upstream node of the node A.
  • the previous node of the first forwarding node refers to a node that is directly connected to the first forwarding node through the FlexE and is the upstream node of the first forwarding node. It should be understood that there is no intermediate node between node A and the previous node of node A along the direction of the FlexE path.
  • the source node in the present application for example, the first source node, the second source node, etc., refers to the sender of the data.
  • the destination node in the present application for example, the first destination node, the second destination node, etc., refers to the receiving end of the data.
  • FlexE introduces a bundled group (FlexE Group, hereinafter referred to as a bundle group), a flexible Ethernet client (FlexE Client, hereinafter referred to as a client), and a time slot (Calendar).
  • New concepts such as flexible Ethernet time division multiplexing layer (FlexE Shim, hereinafter referred to as time division multiplexing layer) and FlexE interface.
  • Bundle group It can be bundled by multiple PHYs. For example, it can consist of 1 to 254 PHYs supporting 100GE rates.
  • the bandwidth resource corresponding to a bundle group is the sum of bandwidth resources corresponding to the PHYs in the bundle group.
  • the FlexE can transmit multiple service flows in parallel through the bundle group.
  • the service data of the same service flow can be carried in one PHY in the bundle group, or can be carried in different PHYs in the bundle group. In other words, the service data of the same service flow can be transmitted to the peer through one PHY in the bundle group, or can be transmitted to the peer end through multiple PHYs in the bundle group.
  • a PHY can be defined as providing mechanical, electrical, functional, and specification characteristics for the physical link establishment, maintenance, and teardown required to transmit data.
  • the PHY may include a physical layer working device at both ends of the transmitting and receiving, and an optical fiber between the transmitting and receiving ends, and the physical layer working device may include, for example, an Ethernet physical layer interface device or the like.
  • FlexE interface A FlexE interface can be thought of as a bundle. The data reception or transmission of the FlexE interface needs to be transmitted through an external PHY.
  • One FlexE interface can be connected to one or more PHYs, and the total bandwidth of the PHY determines the bandwidth of the entire FlexE interface.
  • a bundle group or a FlexE interface may be represented by an index or an identifier (ID) of a bundle group, or a bundle group or a FlexE interface may be represented by an index or an ID of the bundle group.
  • ID an identifier
  • a bundle group or interface with an ID of 1 is represented as bundle group 1 or interface 1
  • bundle group 1 or interface 1 represents a bundle group or interface with ID 1.
  • the ingress interface represents the FlexE interface used by the node to receive data, that is, the FlexE interface used by the previous node of the node to transmit data.
  • the outbound interface represents the FlexE interface used by the node to send data, that is, the FlexE interface used by the next node of the node to receive data.
  • the client can be understood as: a channel with independent bandwidth, each client bandwidth size is user configurable (by scheduling time slot configuration).
  • Time slot The bandwidth resource of a PHY is usually divided into multiple time slots (such as 20 time slots).
  • the service data is first encapsulated into time slots, and then the time slots are mapped to the PHY in the bundle group.
  • the mapping relationship between the time slot and the PHY is recorded in the time slot configuration table of the FlexE.
  • the FlexE generally supports two sets of time slot configuration tables, where one set of time slot configuration table is the time slot configuration table currently in use, and the other set.
  • the time slot configuration table can be used as a backup, and the two sets of time slot configuration tables can be switched to each other.
  • the specific switching timing can be negotiated by the upstream and downstream, and switched synchronously. In this way, when the service configuration of a certain client changes, the services of other clients are not affected.
  • Time division multiplexing layer The main function of the time division multiplexing layer is to arrange the 64b/66b block of service data according to the pre-configured time slot configuration table (specifically, can be configured by the user), that is, the 64b/66b block package corresponding to the service data. To the pre-divided time slots, the planned time slots are then mapped to the PHYs in the bundling group for transmission, wherein each time slot is mapped to one PHY in the bundling group.
  • the pre-configured time slot configuration table specifically, can be configured by the user
  • a certain time slot in a certain bundle group may be represented by an index or an ID of a time slot, or a certain time slot in a certain bundle group may be represented by an index or an ID of the time slot.
  • a time slot with ID 1 indicates time slot 1 in a bundle, or slot 1 indicates an ID or a time slot with index 1.
  • the in-slot represents the time slot to which the data transmitted to the node is mapped, that is, the time slot to which the previous node of the node maps the data, that is, the previous node of the node can map the data.
  • the time slot indicates the time slot to which the node maps data, that is, the node can map the data to the outgoing time slot for transmission, and the outgoing time slot is the next node of the node for the next node of the node.
  • the time slot of the node is the time slot to which the data transmitted to the node is mapped.
  • Figure 2 depicts the general processing of a FlexE traffic flow.
  • the bundle group includes PHYs 1-4, and the bundle group can be used to transmit service stream 1, service stream 2, and service stream 3.
  • the service flow 1 of the client may encapsulate the MAC layer information through a Media Access Control (MAC) layer module, and then convert the MAC frame into 64b/66b. The format.
  • the client sends the processed service data to the time division multiplexing layer.
  • MAC Media Access Control
  • the time division multiplexing layer may perform time slot scheduling on the received service data based on the pre-configured time slot configuration table (that is, the 64b/66b block corresponding to the service data is arranged into the pre-divided time slots). Further, the time slot in which the service data of the service flow 1 is encapsulated is mapped to the PHY in the bundle group. As shown in FIG. 2, the time slot in which the service data of the service flow 1 is encapsulated is mapped to the PHY1 and the PHY2. Then, the PHY in the bundle group can transmit data to the receiving end through the optical module. The receiving end reassembles the data transmitted on the PHY in the bundle group into a service flow according to the reverse process of the processing process of the sender.
  • service flow 2 and service flow 3 are similar to service flow 1, and will not be described in detail herein.
  • the FlexE path can be understood as follows: Each node on the FlexE path is connected through the FlexE interface.
  • the FlexE path forwarding table is established by the other nodes on the FlexE path except the source node and the destination node of the FlexE path. These FlexE connections and the FlexE path forwarding table are combined.
  • a FlexE path forwarding table of a node is used to indicate a correspondence between one or more time slots on one bundle group and one or more time slots on another bundle group. According to the correspondence, the forwarding plane of the node may be Mapping data carried on one or more time slots on the one bundle group to one or more time slots on the other bundle group.
  • node 13 and node 14 are connected through a FlexE interface, and node 14 is connected to node 16 through a FlexE interface.
  • the node 14 can be based on FlexE.
  • the path forwarding table performs the transmission of the data service flow 1.
  • the FlexE path forwarding table of node 14 can be as shown in Table 1, for example.
  • the interface 1A is the FlexE interface corresponding to the bundle group 1A between the node 13 and the node 14, and the interface 3A is the FlexE interface corresponding to the bundle group 3A between the node 14 and the node 16.
  • node 13 maps traffic flow 1 to time slots 6 and 9 on bundle 1A for transmission, and node 14 transmits traffic flows through time slots 6 and 9 on bundle group 1A according to Table 1.
  • 1 is mapped to time slots 7 and 12 of bundle group 3A between node 14 and node 16 without the need to reassemble the data on time slots 6 and 9 on bundle group 1A.
  • the node 16 After receiving the service flow 1 on the slots 7 and 12 of the bundle group 3A, the node 16 reassembles and restores the service flow 1.
  • FIG. 3 is a schematic diagram of an application scenario according to the present application.
  • node 11, node 12, and node 17 belonging to domain 1 are interconnected by domain 2
  • node 13 and node 16 are edge nodes (for example, Provider Edge (PE) devices)
  • nodes. 14 and node 15 are intermediate nodes (e.g., a provider (Provide, P) device).
  • PE Provider Edge
  • P Provider Edge
  • Each node in domain 2 is connected by FlexE
  • node 11 and node 13 are connected by FlexE
  • node 12 and node 13 are also connected by FlexE
  • node 16 and node 17 are connected by FlexE.
  • the service flow in which the source node in the domain 2 is the node 13 and the destination node is the node 16 can be carried over by establishing the end-to-end FlexE path 21 of the node 13 to the node 16. If the traffic transmitted between the node 11 and the node 17 also needs to guarantee QoS, the service flow can be carried by establishing the end-to-end FlexE path 22 where the source node is the node 11 and the destination node is the node 17.
  • the nodes on the established FlexE path 22 may be node 11, node 13, node 14, node 16, and node 17, or node 11, node 13, node 15, node 16, and node 17, in order.
  • the nodes on the re-established FlexE path may be node 13, node 14, and node 16, or It can be node 13, node 15, and node 16.
  • the established source node is the node 13
  • the intermediate node is the node 14 and the destination node is the FlexE path of the node 16
  • the established source node is the node 13
  • the intermediate node is the node 15 and The destination node is the FlexE path of node 16 to carry the traffic flow.
  • control planes of node 13, node 14, and node 16, or the control planes of node 13, node 15, and node 16, need to maintain two FlexE paths (ie, FlexE path 21 and FlexE path 22), resulting in node 13
  • FlexE path 21 and FlexE path 22 Two FlexE paths
  • the present application provides a method for establishing a FlexE path.
  • the method embodiment of the present application is described in detail below with reference to FIG. 4 .
  • FIG. 4 is a schematic flowchart of a method for establishing a FlexE path according to an embodiment of the present application.
  • the first forwarding node receives the first path setup request message sent by the first source node.
  • the first path setup request message is used to establish a first FlexE path between the first source node and the first destination node, where the first FlexE path is used to transmit the first service flow.
  • the first path establishment request message includes first routing information, where the first routing information is used to indicate node information on the first FlexE path.
  • the first forwarding node on the first FlexE path is an upstream node of the second forwarding node on the first FlexE path.
  • the first source node when the first source node needs to establish a FlexE path (ie, the first FlexE path) to transmit the first service flow, the first source node calculates routing information of the first FlexE path, that is, which first FlexE path needs to pass. The node then encapsulates the routing information (ie, the first routing information) into a first path setup request message, which is sent along the FlexE path to the next node. For example, when the first forwarding node is the next node of the first source node, the first path establishment request message is sent by the first source node to the first forwarding node.
  • a FlexE path ie, the first FlexE path
  • the first path setup request message carries the bandwidth requirement information of the first service flow
  • the first forwarding node can know the bandwidth required by the first service flow according to the bandwidth requirement information of the first service flow, so that the first service can be determined.
  • the number of time slots required for the stream For example, suppose a PHY has a bandwidth of 100G and is divided into 20 slots. If the bandwidth required for the first service flow is 10G, the number of slots required for the first service flow is two, that is, Said that the first traffic flow needs to be mapped to 2 time slots.
  • the routing information sent by the source node may carry the full routing information of the FlexE path, that is, each of the FlexE paths. Node information.
  • the first FlexE path is a FlexE path in the domain, that is, a non-cross-domain FlexE path
  • the first forwarding node is the next node of the first source node, and the first forwarding node is known according to the first routing information
  • the second The forwarding node is the next node of the first forwarding node, and the next node of the second forwarding node is the first destination node.
  • the routing information sent by the source node may carry part of the routing information of the FlexE path, and the part of the routing information may be used to indicate the Source node, destination node, and edge node on the FlexE path.
  • the source node of the first FlexE path is the first source node
  • the destination node is the first destination node
  • the two edge nodes are the first forwarding node and the second forwarding node respectively.
  • the first forwarding node is an upstream node of the second forwarding node.
  • the first forwarding node may autonomously determine the routing information between the first forwarding node and the second forwarding node according to the first routing information and the bandwidth requirement of the first service flow, that is, determine the path from the first forwarding node to the second forwarding node. Each node.
  • the first forwarding node may determine the routing information between the first forwarding node and the second forwarding node by using a plurality of methods. For example, the shortest path method may be used, and the specific technology may be referred to. Narration.
  • the first path establishment request message may further include path type information, where the path type information is used to indicate that the established path type is a FlexE path.
  • the path type that each node needs to establish by default may be a FlexE path.
  • the path establishment request message such as the first path establishment request message and the second path establishment request message (to be referred to hereinafter), may be a resource reservation protocol (Resource Reservation Protocol-Traffic Engineering, RSVP).
  • RSVP Resource Reservation Protocol-Traffic Engineering
  • the first forwarding node establishes a second FlexE path between the first forwarding node and the second forwarding node according to the first path establishment request message, and deletes the established first after establishing the second FlexE path.
  • a third FlexE path between the forwarding node and the second forwarding node.
  • the first forwarding node may establish the first forwarding node to the first The FlexE path between the two forwarding nodes (for example, recorded as the third FlexE path) transmits the second service flow through the third FlexE path.
  • the first forwarding node may re-establish a FlexE path between the first forwarding node and the second forwarding node according to the bandwidth requirements of the first service flow and the second service flow (for example, Recorded as the second FlexE path), after establishing the second FlexE path, the traffic on the third FlexE path (ie, the second traffic flow) is switched to the second FlexE path, and the third FlexE path is deleted. In this way, the forwarding of the first service flow and the second service flow can be performed through the second FlexE path.
  • the bandwidth requirements of the first service flow and the second service flow for example, Recorded as the second FlexE path
  • the second FlexE path multiplexes a session established when the third FlexE path is established, that is, the second FlexE path and the third FlexE path correspond to the second session.
  • a session is established (for example, as a second session).
  • the second FlexE path can be established based on the second session, that is, the second FlexE path and The second session corresponds.
  • a session can be defined as a data stream at a particular destination address and transport protocol.
  • a session can be represented by a triple (destination address, protocol number, protocol port).
  • destination address the protocol number
  • protocol port the protocol port
  • a session may be re-established when the second FlexE path is established, which is not limited in this embodiment of the present application.
  • the time slot resource for transmitting the second service flow on the second FlexE path is the same as the time slot resource for transmitting the second service flow on the third FlexE path.
  • the time slot resource used for transmitting the second service flow in the slot resource reserved by the second FlexE path is the same as the reserved time slot resource of the third FlexE path.
  • the first forwarding node establishes and saves a correspondence between the first FlexE path and the second FlexE path, so that the first service flow and the second service flow are mapped to time slots of the second FlexE path.
  • the first forwarding node may establish a correspondence between the first FlexE path and the second FlexE path by establishing a form.
  • the first forwarding node may forward the first service flow through the second FlexE path according to the correspondence shown in the table when receiving the first service flow that is forwarded through the first FlexE path.
  • the present application does not specifically define the form of the correspondence between the first FlexE path and the second FlexE path.
  • the method for establishing a flexible Ethernet path in the embodiment of the present application on the basis that the third FlexE path for transmitting the second service flow has been established, if the first service flow needs to be transmitted, the first forwarding node may be re-established to the second Forwarding the second FlexE path between the nodes, and merging the first service flow and the second service flow to the second FlexE path for forwarding, and deleting the third FlexE path, so that the first forwarding node and the second forwarding node can be reduced.
  • the first forwarding node establishes and saves a correspondence between the first FlexE path and the second FlexE path, including:
  • the first forwarding node sends a second path establishment request message to the next node of the first forwarding node on the second FlexE path, where the second path establishment request message includes second routing information, where the second routing information is used to indicate the second FlexE path.
  • Node information so that the next node of the first forwarding node sends a second path establishment request according to the second routing information; the first forwarding node receives the second node sent by the next node of the first forwarding node according to the second path establishment request message.
  • a resource reservation message the first forwarding node determines, according to the second resource reservation message, the first time slot resource on the second FlexE path, and establishes and saves the first time slot resource, the first FlexE path, and the second FlexE path. Corresponding relationship between the first service flows carried on the first FlexE path is mapped to the time slot corresponding to the first time slot resource.
  • the first forwarding node suspends the sending of the first path setup request message, and sends the second node to the next node of the first forwarding node (for example, as an intermediate forwarding node).
  • a path setup request message requests to establish a second FlexE path.
  • the intermediate forwarding node sends a second path establishment request to the next node along the direction of the second FlexE path according to the second routing information until the second path establishment request message reaches the second forwarding node.
  • the second forwarding node After receiving the second path setup request message, the second forwarding node sends a second resource reservation message in response to the second path setup request message in the reverse direction of the second FlexE path, along each of the opposite directions of the second FlexE path.
  • the node performs resource reservation according to the second resource reservation message.
  • the first forwarding node may determine the first time slot resource after the first forwarding node receives the second resource reservation message sent by the intermediate forwarding node.
  • the first time slot resource includes a time slot resource used by the first forwarding node to forward the first service flow.
  • the first time slot resource includes time slots 15 and 16 on interface 1A.
  • the first forwarding node may map the first traffic flow to time slots 15 and 16 on interface 1A for transmission.
  • the first forwarding node establishes and saves a correspondence between the first time slot resource, the first FlexE path, and the second FlexE path.
  • the first forwarding node may map the first service flow carried on the first FlexE path to the time slot corresponding to the first time slot resource for transmission.
  • the first forwarding node may establish a correspondence between the first slot resource, the first FlexE path, and the second FlexE path by establishing a mapping table as shown in Table 2.
  • the first time slot resource includes time slots 15 and 16 on interface 1A.
  • the first forwarding node may map the first service flow to the time slots 15 and 16 on the interface 1A for transmission.
  • Table 2 is only one embodiment of the correspondence between the first slot resource, the first FlexE path, and the second FlexE path.
  • the first forwarding node may also save the correspondence between the first time slot resource, the first FlexE path, and the second FlexE path in other manners, for example, the first forwarding node may also save by establishing two tables.
  • the first time slot resource, the first FlexE path, and the first FlexE path are saved in the form of the first time slot resource, the first FlexE path, and the second FlexE path.
  • the correspondence between the two FlexE paths is not specifically limited.
  • the resource reservation message such as the first resource reservation message and the second resource reservation message (hereinafter referred to as the following), may be a Resv message in the RSVP, but the embodiment of the present application does not Limited to Resv messages.
  • the time slot resource used for transmitting the second service flow on the second FlexE path is the same as the time slot resource used for transmitting the second service flow on the third FlexE path, and therefore Each node only needs to determine a time slot resource for transmitting the first service flow.
  • the first forwarding node sends a second path establishment request message to the intermediate forwarding node.
  • the first forwarding node suspends sending of the first path establishment request message, and requests to establish a second FlexE path by sending a second path establishment request message to the intermediate forwarding node.
  • the second path setup request message may carry bandwidth requirement information and second routing information.
  • the bandwidth requirement information is used to indicate bandwidth requirements of the first service flow and the second service flow, and the second routing information indicates node information on the second FlexE path.
  • the intermediate forwarding node After receiving the second path setup request message, the intermediate forwarding node sends a second path setup request to the second forwarding node along the direction of the second FlexE path.
  • the second forwarding node After receiving the second path setup request message, the second forwarding node sends a second resource reservation message in response to the second path setup request message to the intermediate forwarding node in the reverse direction of the second FlexE path.
  • the intermediate forwarding node determines the slot resource #1 according to the second resource reservation message, and instructs the second forwarding node to change the FlexE configuration of the inbound interface of the second forwarding node according to the slot resource #1, so that the first service flow can be mapped. Transfer to time slot resource #1.
  • time slot resource #1 is the time slot resource used by the intermediate forwarding node to forward the first service flow, that is, the FlexE configuration of the outbound interface of the intermediate forwarding node.
  • time slot resource #1 may be time slots 8 and 10 on interface 3A.
  • the intermediate forwarding node maps the first traffic to slots 8 and 10 on interface 3A for transmission.
  • the second resource reservation message sent by the second forwarding node to the intermediate forwarding node may carry the indication information of the slot resource #1, where the indication information of the slot resource #1 is used to indicate the intermediate forwarding.
  • the time slot resource #1 determined by the node. Specifically, after receiving the second path establishment request message, the second forwarding node searches for the idle time slot, determines the time slot resource #1 from the idle time slot, and then passes the indication information of the time slot resource #1. The time slot resource #1 informs the intermediate forwarding node.
  • the indication information may be a Generalized Multiprotocol Label Switching (GMPLS) label, and the GMPLS label is used to indicate the slot resource #1. It should be understood that the GMPLS label can simultaneously indicate the time slot resources used to transmit the second traffic flow on the previous third FlexE path. It should be understood that the application is not limited to the indication information being a GMPLS label.
  • GMPLS Generalized Multiprotocol Label Switching
  • the time slot resource #1 may be determined by the intermediate forwarding node. Specifically, the second forwarding node requests the intermediate forwarding node to determine the time slot resource #1 by using the second resource reservation message, and the intermediate forwarding node searches for the idle time slot after receiving the second resource reservation message, from the idle time slot. The time slot resource #1 is determined.
  • the first forwarding node may change the FlexE configuration on the inbound interface of the intermediate forwarding node by using an in-band control channel with the intermediate forwarding node, thereby The purpose of changing the slot configuration of the second FlexE path is reached.
  • the intermediate forwarding node sends a second resource reservation message to the first forwarding node.
  • the first forwarding node determines the slot resource #2 according to the second resource reservation message (that is, an example of the first slot resource), and instructs the intermediate forwarding node to change the inbound interface of the intermediate forwarding node according to the slot resource #2.
  • the FlexE configuration allows the first traffic flow to be mapped to time slot resource #2 for transmission.
  • time slot resource #2 is the time slot resource used by the first forwarding node to forward the first service flow.
  • time slot resource #2 may be time slots 15 and 16 on interface 1A.
  • the intermediate forwarding node maps the first traffic to slots 15 and 16 on interface 1A for transmission.
  • step S606 can refer to the description of step S604 above, and for brevity, details are not described herein again.
  • the intermediate forwarding node can establish a time slot forwarding table as shown in Table 3 according to the FlexE configuration of the inbound interface and the outbound interface.
  • the intermediate forwarding node may map the first service flow received from time slots 15 and 16 on interface 1A to time slots 8 and 10 on interface 3A for transmission of the service flow.
  • the first forwarding node establishes and saves the mapping table shown in Table 2.
  • the first forwarding node may map the first service flow to the time slot corresponding to the time slot resource #2 for transmission.
  • the intermediate forwarding node maps the first service flow to the time slot corresponding to the time slot resource #1 for transmission.
  • the first forwarding node after the first forwarding node establishes the second FlexE path, the first forwarding node continues to send the first path establishment request message along the direction of the first FlexE path.
  • the operation performed by the second forwarding node may refer to an operation performed by the first forwarding node in the embodiment to be described below.
  • the method may further include: the first forwarding node receives a third path establishment request message, where the third path establishment request message is used to establish a relationship between the second source node and the second destination node.
  • a fourth FlexE path the fourth FlexE path is used to transmit the third service flow
  • the third path establishment request message includes third routing information
  • the third routing information is used to indicate node information on the fourth FlexE path, where the fourth FlexE
  • the next node of the first forwarding node on the path is the second destination node; the first forwarding node sends a third path establishment request message to the second destination node; the first forwarding node receives the second destination node according to the third path establishment request message.
  • the first forwarding node determines a third time slot resource according to the third resource reservation message; the first forwarding node establishes and saves the third time slot resource and the fourth time slot on the fifth FlexE path
  • the corresponding relationship of the resources so that the first forwarding node maps the third service flow mapped to the time slot corresponding to the fourth time slot resource to the third time slot resource
  • Corresponding time slot wherein the fifth FlexE path is a FlexE path between the second forwarding node and the first forwarding node, and the time slot corresponding to the third time slot resource is used for transmitting the third service on the fifth FlexE path.
  • the time slot of the stream is a FlexE path between the second forwarding node and the first forwarding node.
  • the fifth FlexE path between the second forwarding node and the first forwarding node is established.
  • the second forwarding node sends a third path setup request message along the direction of the fourth FlexE path.
  • the first forwarding node goes to the next node (ie, the first The source node sends a third path setup request message.
  • the first source node After receiving the third path setup request message, the first source node sends a third resource reservation message to the first forwarding node, requesting the first forwarding node to perform resource reservation.
  • the first forwarding node reserves the third time slot resource as the time slot resource for transmitting the third service flow according to the third resource reservation message.
  • the correspondence between the third time slot resource and the fourth time slot resource on the fifth FlexE path is established and saved.
  • the first forwarding node may map the previous node of the first source node on the fourth FlexE path to the third time slot corresponding to the fourth time slot resource according to the correspondence.
  • the service flow is mapped to the time slot corresponding to the third time slot resource for transmission.
  • the second destination node may be the first source node herein, and the second source node may be the first destination node herein.
  • the second forwarding node continues to send the first path establishment request to the next node along the first FlexE path. Message. If the next node of the second forwarding node is the first destination node, after the first destination node receives the first path establishment request message, the first destination node sends a response to the first path establishment request message to the second forwarding node. The first resource reservation message.
  • the second forwarding node determines, according to the first resource reservation message, an available time slot resource (for example, as a fifth time slot resource), and instructs the first destination node to change the inbound interface of the first destination node according to the fifth time slot resource. FlexE configuration.
  • the second forwarding node saves the fifth time slot resource and the sixth time slot resource (ie, the time slot used by the previous node of the second forwarding node on the second FlexE path to send the first service flow, for example, the time slot resource# 1) Correspondence.
  • the second forwarding node may map the first service flow transmitted on the time slot corresponding to the sixth time slot resource to the fifth time slot resource for transmission.
  • the sixth time slot resource is the time slot resource #1
  • the fifth time slot resource is the time slots 17 and 27 on the interface 2C between the second forwarding node and the first destination node.
  • the second forwarding node may be used as an example.
  • the correspondence between the fifth slot resource and the sixth slot resource is saved by establishing a mapping table shown in Table 4.
  • the second forwarding node may map the first service flows of time slots 8 and 10 carried on the inbound interface 3A to the time slots 17 and 27 on the outbound interface 2C for transmission.
  • Table 5 is only an embodiment showing the correspondence between the fifth slot resource and the sixth slot resource.
  • the second forwarding node may also save the correspondence between the fifth slot resource and the sixth slot resource in other manners or forms.
  • the second forwarding node may also save the fifth slot resource and the sixth by establishing two tables.
  • Correspondence of time slot resources The embodiment of the present application does not specifically limit the correspondence between the fifth time slot resource and the sixth time slot resource in the form of the second forwarding node.
  • the second forwarding node After the second forwarding node establishes and saves the correspondence between the fifth slot resource and the sixth slot resource, the second forwarding node sends the first resource reservation message along the reverse direction of the first FlexE path.
  • the first forwarding node sends a first resource reservation message to the first source node.
  • the first source node determines the second time slot resource, and instructs the first forwarding node to configure the FlexE configuration on the inbound interface of the first forwarding node according to the second time slot resource to establish the first A FlexE path.
  • the first forwarding node saves the correspondence between the second slot resource and the first slot resource.
  • the first forwarding node may map the first service flow to the time slot corresponding to the second time slot resource according to the correspondence between the first time slot resource and the second time slot resource It is mapped to the time slot corresponding to the first time slot resource.
  • the second time slot resource may be time slots 3 and 7 on interface 1B between the first source node and the first forwarding node.
  • the first forwarding node may save the correspondence between the second slot resource and the first slot resource by establishing a forwarding table as shown in Table 5.
  • the forwarding plane of the first source node may map the first traffic flow to slots 3 and 7 in interface 1B, and the first forwarding node will be carried on timeslots 3 and 7 in interface 1B.
  • the first traffic flow is mapped to time slots 15 and 16 on interface 1A for transmission.
  • Table 5 is only one embodiment of the correspondence between the first slot resource and the second slot resource.
  • the first forwarding node may also save the correspondence between the first slot resource and the second slot resource in other manners or forms.
  • the first forwarding node may also save the correspondence between the first time slot resource and the second time slot resource by establishing two or more tables, and the first embodiment of the present application saves the first form in the first forwarding node.
  • the correspondence between the slot resource and the second slot resource is not specifically limited.
  • the first forwarding node may combine Table 2 and Table 5 and save it as a table.
  • the table may be a simple splicing of two tables, or may be a table obtained by combining the same contents of Tables 2 and 3. This embodiment of the present application does not limit this.
  • first source node, the first forwarding node, the intermediate forwarding node, the second forwarding node, and the first destination node in the method shown in FIG. 6 may respectively correspond to the node 11 in the scenario shown in FIG. 3, 13, 14, 16 and 17.
  • FIG. 6 is a schematic interaction diagram of a method of establishing a FlexE path in accordance with an embodiment of the present application.
  • the first source node sends a first path setup request message to the first forwarding node, where the first path setup request message includes bandwidth requirement information of the first service flow and first routing information.
  • the first forwarding node is configured to establish a FlexE path that passes through the first forwarding node to the second forwarding node, and determines whether a FlexE path is established between the first forwarding node and the second forwarding node. If the FlexE path, that is, the third FlexE path, has been established, it is determined whether there are enough time slot resources to satisfy the bandwidth requirement of the first service flow. If there is sufficient time slot resource to meet the bandwidth requirement of the first service flow, the first forwarding node suspends the sending of the first path establishment request message, and establishes a second FlexE path between the first forwarding node and the second forwarding node.
  • the second FlexE path can be established with reference to the method illustrated in FIG. For the sake of brevity, it will not be repeated here.
  • the third FlexE path is deleted, so that each node no longer needs to maintain the third FlexE path.
  • the first forwarding node After the second FlexE path is established, the first forwarding node sends a first path establishment request message along a direction of the path of the first FlexE.
  • the intermediate forwarding node After receiving the first path setup request message, the intermediate forwarding node sends a first path setup request message to the second forwarding node.
  • the second forwarding node After receiving the first path setup request message, the second forwarding node sends a first path setup request message to the first destination node.
  • the first destination node sends a first resource reservation message to the second forwarding node after determining that the available time slot meets the bandwidth requirement of the first service flow.
  • the second forwarding node performs resource reservation according to the first resource reservation message.
  • the second forwarding node determines, according to the first resource reservation message, a fifth time slot resource used for transmitting the first service flow with the first destination node, for example, time slots 17 and 27 on the outbound interface 2C, and indicates A destination node changes the FlexE configuration on the inbound interface of the first destination node.
  • the second forwarding node may also save the correspondence between the fifth slot resource and the sixth slot resource by establishing a forwarding table as shown in Table 4.
  • the first destination node changes the FlexE configuration on the inbound interface according to the indication of the second forwarding node.
  • the second forwarding node sends the first resource reservation message in a reverse direction of the first FlexE path.
  • the intermediate forwarding node After receiving the first resource reservation message, the intermediate forwarding node continues to send the first resource reservation message to the first forwarding node.
  • the first forwarding node sends a first resource reservation message to the first source node.
  • the first source node determines a second slot resource that transmits the first service flow with the first forwarding node, for example, timeslots 3 and 7 on interface 1B, and instructs the first forwarding node to change the first forwarding node.
  • the FlexE configuration on the inbound interface is a second slot resource that transmits the first service flow with the first forwarding node, for example, timeslots 3 and 7 on interface 1B, and instructs the first forwarding node to change the first forwarding node.
  • the first forwarding node changes the FlexE configuration on the inbound interface according to the indication of the first source node. And establishing a mapping relationship between the second slot resource and the first slot resource.
  • the establishment of the first FlexE path is completed. Thereafter, when forwarding the service flow, the first service flow can be forwarded according to the mapping table/transfer table shown in Tables 2 to 5.
  • the second service flow may be forwarded according to the time slot mapping table established and saved when the third FlexE path was previously established, and the application is not limited thereto.
  • the method for establishing a flexible Ethernet path in the embodiment of the present application on the basis that the third FlexE path for transmitting the second service flow has been established, if the first service flow needs to be transmitted, the first forwarding node may be re-established to the second Forwarding the second FlexE path between the nodes, and merging the first service flow and the second service flow to the second FlexE path for forwarding, and deleting the third FlexE path, so that the first forwarding node and the second forwarding node can be reduced.
  • FIG. 7 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • the network device 800 shown in FIG. 7 includes a transceiver unit 810 and a processing unit 820.
  • the transceiver unit 810 is configured to receive a first path setup request message sent by the first source node, where the first path setup request message is used to establish a first FlexE path between the first source node and the first destination node, and the first FlexE path
  • the first path setup request message includes the first route information, where the first route information is used to indicate the node information on the first FlexE path, where the first forwarding node on the first FlexE path is the first An upstream node of a second forwarding node on a FlexE path.
  • the processing unit 820 is configured to establish a second FlexE path between the first forwarding node and the second forwarding node according to the first path establishment request message, and delete the established first forwarding node after the second FlexE path is established. And a third FlexE path between the second forwarding node, where the third FlexE path is used to transmit the second service flow, and the second FlexE path can satisfy the bandwidth requirement of the first service flow and the bandwidth requirement of the second service flow.
  • the processing unit 820 is further configured to establish and save a correspondence between the first FlexE path and the second FlexE path, so that the first service flow and the second service flow are mapped to time slots of the second FlexE path.
  • each unit in the network device 800 is used to perform various actions or processes performed by the first forwarding node (e.g., PE device) in each of the above methods.
  • PE device e.g., PE device
  • network device 800 can also be the second forwarding node in the embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a network device according to another embodiment of the present application.
  • the network device 900 of FIG. 8 establishing a flexible Ethernet path includes a memory 910, a processor 920, and a communication interface 930.
  • Memory 910, processor 920, and communication interface 930 communicate with one another via internal connection paths to communicate control and/or data signals.
  • Processor 920 corresponds to processing unit 820 in FIG. 7, in other words, processor 920 is capable of performing the operations performed by processing unit 820 in FIG.
  • the communication interface 930 corresponds to the transceiving unit 810 in FIG. 7, in other words, the communication interface 930 is capable of performing the operations performed by the transceiving unit 810 in FIG.
  • the memory 910, the processor 920, and the communication interface 930 are described in detail below.
  • the memory 910 is configured to store program code
  • the processor 920 is configured to execute program code stored in the memory 910.
  • the communication interface 930 is configured to receive a first path establishment request message sent by the first source node, where the first The path establishment request message is used to establish a first FlexE path between the first source node and the first destination node, where the first FlexE path is used to transmit a first service flow, where the first path establishment request message includes a routing information, the first routing information is used to indicate node information on the first FlexE path, where the first forwarding node on the first FlexE path is the first on the first FlexE path Two upstream nodes of the forwarding node;
  • the processor 920 is configured to establish, according to the first path setup request message, a second FlexE path between the first forwarding node and the second forwarding node, and after establishing the second FlexE path Deleting a third FlexE path between the first forwarding node and the second forwarding node that is established, where the third FlexE path is used to transmit a second service flow, where the second FlexE path can satisfy The bandwidth requirement of the first service flow and the bandwidth requirement of the second service flow.
  • the processor 920 is further configured to establish and save a correspondence between the first FlexE path and the second FlexE path, so that the first service flow and the second service flow are mapped to the second On the time slot of the FlexE path.
  • each unit in the network device 900 is used to perform each action or process performed by the first forwarding node in each of the above methods.
  • a detailed description thereof will be omitted.
  • the network device 900 in the above may be a network device in a flexible Ethernet, for example, may be a routing device in a flexible Ethernet, or may be a single board in the routing device.
  • the embodiments of the present application may be applied to a processor or implemented by a processor.
  • the processor can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the processor may be a central processing unit (CPU), the processor may be another general-purpose processor, a digital signal processor (DSP), or an application specific integrated circuit (ASIC). ), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software in the decoding processor.
  • the software can be located in a random storage medium, such as a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (ROMM), an erasable programmable read only memory (erasable PROM, EPROM), or an electrical Erase programmable EPROM (EEPROM) or flash memory.
  • the volatile memory can be a random access memory (RAM) that acts as an external cache.
  • RAM random access memory
  • RAM random access memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM double data rate synchronous DRAM
  • DDR SDRAM double data rate synchronous DRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronously connected dynamic random access memory
  • DRRAM direct memory bus random access memory
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .

Landscapes

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

Abstract

本申请提供了一种建立FlexE路径的方法和网络设备，能够降低节点的控制面的管理复杂度和信令开销。该方法包括：第一转发节点接收第一源节点发送的第一路径建立请求消息，第一路径建立请求消息用于建立第一源节点到第一目的节点之间的第一FlexE路径，第一FlexE路径用于传输第一业务流；第一转发节点根据第一路径建立请求消息，建立第一转发节点至第二转发节点之间的第二FlexE路径，并在建立第二FlexE路径后，删除已建立的第一转发节点到第二转发节点之间的第三FlexE路径；第一转发节点建立并保存第一FlexE路径和第二FlexE路径的对应关系，使得将第一业务流和第二业务流映射至第二FlexE路径的时隙上。

Description

建立灵活以太网路径的方法和网络设备
本申请要求于2017年8月4日提交中国专利局、申请号为201710662235.0、申请名称为“建立灵活以太网路径的方法和网络设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及灵活以太网领域，并且更具体地，涉及一种建立灵活以太网(Flexible Ethernet，FlexE)路径的方法和网络设备。
背景技术
灵活以太网是在传统以太网基础上发展出来的一种以太网技术。FlexE技术在端口上能够实现不同的灵活以太网客户端(FlexE Client)的业务的带宽的隔离，因此，这种技术也可以应用在因特网协议(Internet Protocol，IP)以太网络，用来保障特定的业务的服务质量(Quality of Service，QoS)。比如，节点11、节点13、节点14、节点16以及节点17之间通过FlexE连接，可以通过建立经过节点14的节点13到节点16之间的端到端的FlexE路径(或通道(Channel))1来承载源节点为节点13且目的节点为节点16的业务流1，以及通过建立转发节点依次为节点13、节点14、节点16的节点11到节点17之间的端到端的FlexE路径2来承载源节点为节点11且目的节点为节点17的业务流2，可以为业务流1和业务流2提供独享的带宽保障和业务隔离，保障业务流1和业务流2的QoS。
现有技术中，在建立FlexE路径2时，需要重新建立一条节点13到边缘节点16之间的端到端的FlexE路径，该重新建立的FlexE路径作为FlexE路径2的一部分，在业务流2到达节点13时，通过该重新建立的FlexE路径承载该业务流。这样，至少节点13和16需要维护两个FlexE路径(即，FlexE路径1和FlexE路径2)，从而造成边缘转发节点B1和B2的管理复杂度的增大以及维护FlexE路径带来的信令开销的增大。
发明内容
本申请提供一种建立FlexE路径的方法和网络设备，能够降低节点的控制面的管理复杂度以及维护FlexE路径所需的信令开销。
第一方面，提供了一种建立FlexE路径的方法，包括：第一转发节点接收第一源节点发送的第一路径建立请求消息，第一路径建立请求消息用于建立第一源节点到第一目的节点之间的第一FlexE路径，第一FlexE路径用于传输第一业务流，第一路径建立请求消息包括第一路由信息，第一路由信息用于指示第一FlexE路径上的节点信息，其中，第一FlexE路径上的第一转发节点为第一FlexE路径上的第二转发节点的上游节点；第一转发节点根据第一路径建立请求消息，建立第一转发节点至第二转发 节点之间的第二FlexE路径，并在建立第二FlexE路径后，删除已建立的第一转发节点到第二转发节点之间的第三FlexE路径，其中，第三FlexE路径用于传输第二业务流，第二FlexE路径能够满足第一业务流的带宽需求和第二业务流的带宽需求；第一转发节点建立并保存第一FlexE路径和第二FlexE路径的对应关系，使得将第一业务流和第二业务流映射至第二FlexE路径的时隙上。
本申请实施例的建立灵活以太网路径的方法，在已经建立传输第二业务流的第三FlexE路径的基础上，若还需要传输第一业务流，可以通过重新建立第一转发节点到第二转发节点之间的第二FlexE路径，将第一业务流和第二业务流汇聚到第二FlexE路径上进行转发，同时删除第三FlexE路径，这样能够减少第一转发节点和第二转发节点之间建立的FlexE路径的数量，从而能够降低第一转发节点和第二转发节点的控制面需要维护的FlexE路径的数量，进而能够降低第一转发节点和第二转发节点的控制面的管理复杂度以及维护FlexE路径所需的信令开销。
可选地，第一路径建立请求消息还可以包括路径类型信息，该路径类型信息用于指示建立的路径类型为FlexE路径。此外，本申请实施例中，也可以规定各节点默认需要建立的路径类型为FlexE路径。
可选地，本申请所涉及的诸如第一路径建立请求消息、第二路径建立请求消息等路径建立请求消息，可以是资源预留协议(Resource Reservation Protocol-Traffic Engineering，RSVP)中的Path消息，但本申请实施例并不限定于Path消息。
通过采用Path消息，可以使用现有协议实现本申请的方法，能够提高系统兼容性。
在一种可能的实现方式中，所述第二FlexE路径复用建立所述第三FlexE路径时所建立的会话。
在建立第三FlexE路径的同时，会建立一个会话(session)(例如，记作第二会话)在建立第二FlexE路径时，可以基于第二会话建立第二FlexE路径，即第二FlexE路径与第二会话对应。通过这样的方法，能够与现有技术更大程度地互通。
在一种可能的实现方式中，第二FlexE路径上用于传输第二业务流的时隙资源与第三FlexE路径上用于传输第二业务流的时隙资源相同。
也就是说，第二FlexE路径所预留的时隙资源中用于传输第二业务流的时隙资源与第三FlexE路径所预留时隙资源相同。通过这样的方法，能够与现有技术更大程度地互通。
在一种可能的实现方式中，第一转发节点建立并保存第一FlexE路径和第二FlexE路径的对应关系，包括：第一转发节点向第二FlexE路径上第一转发节点的下一节点发送第二路径建立请求消息，第二路径建立请求消息包括第二路由信息，第二路由信息用于指示第二FlexE路径上的节点信息，以便于第一转发节点的下一节点根据第二路由信息发送第二路径建立请求；第一转发节点接收第一转发节点的下一节点根据第二路径建立请求消息发送的第二资源预留消息；第一转发节点根据第二资源预留消息，确定第二FlexE路径上的第一时隙资源，并建立和保存第一时隙资源、第一FlexE路径和第二FlexE路径三者之间的对应关系，使得承载于第一FlexE路径上的第一业务流映射至第一时隙资源所对应的时隙上。
应理解，本申请所涉及的诸如第一资源预留消息、第二资源预留消息等资源预留 消息，可以是RSVP中的Resv消息，但本申请实施例并不限定于Resv消息。
可选地，所述第一时隙资源可以是第一转发节点的下一节点确定的，第一转发节点的下一节点可以在第二资源预留消息可以携带第一时隙资源的指示信息，第一转发节点根据该指示信息可以确定第一时隙资源。
进一步地，该指示信息可以是通用多协议标志交换协议(Generalized Multiprotocol Label Switching，GMPLS)标签，该GMPLS标签用于指示第一时隙资源。应理解，该GMPLS标签可以同时指示之前第三FlexE路径上用于传输第二业务流的时隙资源。应理解，本申请并不限于所述指示信息为GMPLS标签。
在通过例如上述两种可能的实现方式确定出第一时隙资源后，第一转发节点可以通过与第一转发节点的下一节点之间的带内控制通道来更改第一转发节点的下一节点的入接口上的FlexE配置，从而达到更改第二FlexE路径的时隙配置的目的。
在一种可能的实现方式中，该方法还可以包括：第一转发节点接收第三路径建立请求消息，第三路径建立请求消息用于建立第二源节点到第二目的节点之间的第四FlexE路径，第四FlexE路径用于传输第三业务流，第三路径建立请求消息包括第三路由信息，第三路由信息用于指示第四FlexE路径上的节点信息，其中，第四FlexE路径上的第一转发节点的下一节点为第二目的节点；第一转发节点向第二目的节点发送第三路径建立请求消息；第一转发节点接收第二目的节点根据第三路径建立请求消息发送的第三资源预留消息；第一转发节点根据第三资源预留消息确定第三时隙资源；第一转发节点建立并保存第三时隙资源和第五FlexE路径上的第四时隙资源的对应关系，使得第一转发节点将映射至第四时隙资源所对应的时隙上的第三业务流映射至第三时隙资源所对应的时隙上，其中，第五FlexE路径为第二转发节点到第一转发节点之间的FlexE路径，第三时隙资源所对应的时隙为第五FlexE路径上用于传输第三业务流的时隙。
这样，在进行业务流的转发时，第一转发节点可以根据第三时隙资源和第五FlexE路径上的第四时隙资源的对应关系，将由第四FlexE路径上第一源节点的上一节点映射至第四时隙资源所对应的时隙上的第三业务流映射至第三时隙资源所对应的时隙上进行传输。
应理解，在本实施例中，第二源节点和第二目的节点可以分别是第一目的节点和第一源节点，那么第四FlexE路径为第一目的节点到第一源节点之间的FlexE路径，第五FlexE路径为第二转发节点到第一转发节点之间的路径，并且第五FlexE路径路径可以看作是第四FlexE路径的一部分。
第二方面，提供了一种网络设备，包括用于执行第一方面或第一方面各种可能的实现方式中的方法的单元。
第三方面，提供了一种网络设备，包括存储器、处理器和通信接口，所述存储器用于存储程序代码，所述处理器用于执行所述存储器中存储的程序代码，以执行第一方面或第一方面各种可能的实现方式中的方法所对应的操作。
第四方面，提供一种计算机可读介质，所述计算机可读介质存储程序代码，所述程序代码包括用于执行第一方面或第一方面的各种可能实现方式中的方法的指令。
第五方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使 得计算机执行第一方面或第一方面的各种可能实现方式中的方法。
附图说明
图1是现有的灵活以太网的架构图。
图2是灵活以太网的常规业务流处理流程的示例图。
图3是应用于本申请实施例的一个系统架构的示意图。
图4是本申请实施例的建立灵活以太网路径的示意性流程图。
图5是本申请一个实施例的建立灵活以太网路径的示意性流程图。
图6是本申请另一实施例的建立灵活以太网路径的示意性流程图。
图7是本申请一个实施例的网络设备的示意性结构图。
图8是本申请另一实施例的网络设备的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请所涉及的节点，例如第一源节点、第一目的节点、第一转发节点等网络设备，可以是路由器或交换机。
本申请中的“节点A的下一节点”是指沿着FlexE路径的方向，与节点A直接通过FlexE连接且为节点A的下游节点的节点。比如，第一转发节点的下一节点，是指与第一转发节点直接通过FlexE连接且为第一转发节点的下游节点的节点。应理解，沿着FlexE路径的方向，节点A和节点A的下一节点之间不存在中间节点。
本申请中的“节点A的上一节点”是指沿着FlexE路径的方向，与节点A直接通过FlexE连接且为节点A的上游节点的节点。比如，第一转发节点的上一节点，是指与第一转发节点直接通过FlexE连接且为第一转发节点的上游节点的节点。应理解，沿着FlexE路径的方向，节点A和节点A的上一节点之间不存在中间节点。
本申请中的源节点，例如第一源节点、第二源节点等，是指数据的发送端。
本申请中的目的节点，例如第一目的节点、第二目的节点等，是指数据的接收端。
在介绍本申请的方案之前，首先，对FlexE技术和FlexE路径进行简要介绍。
如图1所示，FlexE在传统以太网的基础上，引入了捆绑组(FlexE Group，下文简称捆绑组)，灵活以太网客户端(FlexE Client，下文简称客户端)，时隙(Calendar)，灵活以太网时分复用层(FlexE Shim，下文简称时分复用层)、FlexE接口等新概念。
捆绑组：可以由多个PHY捆绑而成，例如，可以由1～254个支持100GE速率的PHY组成。一个捆绑组对应的带宽资源为该捆绑组中的PHY对应的带宽资源之和。FlexE通过捆绑组可以并行地传输多个业务流，同一业务流的业务数据可以承载于捆绑组中的一个PHY，也可以承载于捆绑组中的不同PHY。换句话说，同一业务流的业务数据可以通过捆绑组中的一个PHY传输至对端，也可以通过捆绑组中的多个PHY传输至对端。
PHY可以定义为：为传输数据所需要的物理链路建立、维持、拆除而提供具有机械的、电子的、功能的和规范的特性。例如，PHY可以包括收发两端的物理层工作器件，以及位于收发两端之间的光纤，物理层工作器件例如可以包括以太网的物理层接 口设备(Physical Layer Interface Devices)等。
FlexE接口：可以认为一个FlexE接口就是一个捆绑组。FlexE接口的数据接收或发送，需通过外接PHY来传输。1个FlexE接口可以外接1个或多个PHY，PHY的带宽总和决定整个FlexE接口的带宽。
本申请中，可以通过捆绑组的索引或标识(Identity，ID)表示一个捆绑组或一个FlexE接口，或者说，一个捆绑组或一个FlexE接口可以通过该捆绑组的索引或ID表示。例如，ID为1的捆绑组或接口表示为捆绑组1或接口1，或者说，捆绑组1或接口1表示ID为1的捆绑组或接口。
此外，本申请中，入接口表示节点接收数据所使用的FlexE接口，也即，该节点的上一节点发送数据所使用的FlexE接口。出接口表示该节点发送数据所使用的FlexE接口，也即，该节点的下一节点接收数据所使用的FlexE接口。
客户端可以理解为：具有独立带宽的通道，每个客户端带宽大小用户可配置(通过调度时隙配置的方式)。
时隙：一个PHY的带宽资源通常会被划分成多个时隙(如20个时隙)，实际使用时，会先将业务数据封装至时隙，然后将时隙映射至捆绑组中的PHY，时隙与PHY之间的映射关系记录在FlexE的时隙配置表中，FlexE一般支持2套时隙配置表，其中一套时隙配置表为当前正在使用的时隙配置表，另一套时隙配置表可以作为备用，且两套时隙配置表之间可以相互切换。具体的切换时机可以由上下游相互协商，并同步切换，这样一来，当某个客户端的业务配置变化时，其他客户端的业务不会受到影响。
时分复用层：时分复用层的主要作用是根据预先配置的时隙配置表(具体可以由用户配置)，对业务数据的64b/66b block进行编排，即将业务数据对应的64b/66b block封装至预先划分的时隙中，然后将规划好的各时隙映射至捆绑组中的PHY上进行传输，其中每个时隙映射于捆绑组中的一个PHY。
本申请中，可以通过时隙的索引或ID表示某一捆绑组中的某一时隙，或者说，某一捆绑组中的某一时隙可以通过该时隙的索引或ID表示。例如，ID为1的时隙表示某一捆绑组中的时隙1，或者说，时隙1表示ID或索引为1的时隙。
此外，本申请中，入时隙表示发送至节点的数据被映射至的时隙，即该节点的上一节点将数据映射至的时隙，也即，该节点的上一个节点可以将数据映射至入时隙上传输至该节点。出时隙表示该节点将数据映射至的时隙，即该节点可以将数据映射至出时隙上进行传输，该出时隙对于该节点的下一节点来讲，即为该节点的下一节点的入时隙。
下面结合图2对灵活以太网中的业务流的常规处理过程进行举例说明。
图2描述的是FlexE业务流的常规处理过程。
如图2所示，捆绑组包括PHY1-4，且捆绑组可用于传输业务流1、业务流2和业务流3。以业务流1的传输过程为例，在发送侧，客户端的业务流1可以通过媒体接入控制(Media Access Control，MAC)层模块进行MAC层信息的封装，之后将MAC帧转换成64b/66b的格式。客户端将处理后得到的业务数据发送至时分复用层。
然后，时分复用层可以基于预先配置的时隙配置表，对接收到的业务数据进行时隙编排(即将业务数据对应的64b/66b block编排至预先划分的时隙中)。进一步地， 将封装有业务流1的业务数据的时隙映射至捆绑组中PHY上，如图2所示，封装有业务流1的业务数据的时隙被映射至PHY1和PHY2上。然后，捆绑组中PHY可以通过光模块将数据传输至接收端。接收端会按照发送端处理过程的逆过程，将捆绑组中PHY上传输的数据重新拼装成业务流。
业务流2和业务流3的处理过程与业务流1类似，此处不再详述。
若上述的业务流1和业务流2需要经过转发节点，那么转发节点还需要进行如上述发送侧和接收侧的相应操作，可以看出，这种单跳解析的技术需要业务流的转发节点进行数据的重新拼装，导致处理时延增大。由此，提出了FlexE时隙转发路径(以下，简称为“FlexE路径”)的概念。
FlexE路径可以理解为：FlexE路径上的各节点通过FlexE接口连接，除FlexE路径的源节点和目的节点外的FlexE路径上的其他节点建立FlexE路径转发表，这些FlexE连接和FlexE路径转发表共同构成一个FlexE路径。某一节点的FlexE路径转发表用于表示一个捆绑组上的一个或多个时隙和另一捆绑组上的一个或多个时隙的对应关系，根据该对应关系，该节点的转发面可以将所述一个捆绑组上的一个或多个时隙上承载的数据映射至所述另一捆绑组上的一个或多个时隙上。
以节点13到节点16之间的FlexE路径为例，节点13与节点14通过FlexE接口连接，节点14与节点16通过FlexE接口连接，通过建立节点14的FlexE路径转发表，使得节点14可以根据FlexE路径转发表，进行数据业务流1的发送。节点14的FlexE路径转发表例如可以如表1所示。
表1
入接口 入时隙 出接口 出时隙
接口1A 6，9 接口3A 7，12
表1中，接口1A为节点13和节点14之间的捆绑组1A所对应的FlexE接口，接口3A为节点14和节点16之间的捆绑组3A所对应的FlexE接口。在进行数据转发时，节点13将业务流1映射至捆绑组1A上的时隙6和9上进行传输，节点14根据表1，将通过捆绑组1A上的时隙6和9传输的业务流1映射至节点14和节点16之间的捆绑组3A的时隙7和12上进行传输，而不需要对捆绑组1A上的时隙6和9上的数据进行重新拼装。节点16接收到捆绑组3A的时隙7和12上的业务流1后，再进行重新拼装，恢复出业务流1。
图3是根据本申请一个应用场景的示意图。如图3所示，属于域(domain)1的节点11、节点12和节点17通过域2互联，节点13和节点16为边缘节点(例如，运营商边缘(Provider Edge，PE)设备)，节点14和节点15为中间节点(例如，运营商(Provide，P)设备)。域2中各节点通过FlexE连接，节点11和节点13通过FlexE连接，节点12和节点13也通过FlexE连接，节点16和节点17通过FlexE连接。可 以通过建立节点13到节点16的端到端的FlexE路径21来承载在域2中的源节点为节点13且目的节点为节点16的业务流。如果节点11到节点17之间传输的业务也需要保障QoS，那么可以通过建立源节点为节点11且目的节点为节点17的端到端的FlexE路径22，来承载该业务流。所建立的FlexE路径22上的节点可以依次是节点11、节点13、节点14、节点16和节点17，也可以是节点11、节点13、节点15、节点16和节点17。由于在建立FlexE路径22时，需要重新建立一条节点13到节点16之间的端到端的FlexE路径，该重新建立的FlexE路径上的各节点依次可以是节点13、节点14和节点16，或者也可以是节点13、节点15和节点16。在业务流到达节点13时，通过所建立的源节点为节点13，中间节点为节点14且目的节点为节点16的FlexE路径，或者通过所建立的源节点为节点13，中间节点为节点15且目的节点为节点16的FlexE路径，来承载该业务流。这样，节点13、节点14和节点16的控制面、或者节点13、节点15和节点16的控制面，均需要维护两条FlexE路径(即，FlexE路径21和FlexE路径22)，从而造成节点13、节点14和节点16的控制面的管理复杂度以及维护FlexE路径所需的信令开销的增大。
为了降低节点的控制面的管理复杂度以及维护FlexE路径所需的信令开销，本申请提供了一种建立FlexE路径的方法，下面结合图4，对本申请的方法实施例进行详细描述。
图4是本申请实施例的建立FlexE路径的方法的示意性流程图。
S510，第一转发节点接收第一源节点发送的第一路径建立请求消息。第一路径建立请求消息用于建立第一源节点到第一目的节点之间的第一FlexE路径，第一FlexE路径用于传输第一业务流。所述第一路径建立请求消息包括第一路由信息，第一路由信息用于指示第一FlexE路径上的节点信息。其中，第一FlexE路径上的第一转发节点为第一FlexE路径上的第二转发节点的上游节点。
具体地，在第一源节点需要建立FlexE路径(即，第一FlexE路径)传输第一业务流时，第一源节点计算第一FlexE路径的路由信息，即该第一FlexE路径均需要经过哪些节点，然后将路由信息(即，第一路由信息)封装至第一路径建立请求消息，第一路径建立请求消息沿着FlexE路径被发送至下一节点。例如，当第一转发节点为所述第一源节点的下一节点时，第一路径建立请求消息被第一源节点发送至第一转发节点。
应理解，第一路径建立请求消息携带第一业务流的带宽需求信息，第一转发节点根据第一业务流的带宽需求信息，可知第一业务流所需的带宽大小，从而能够确定第一业务流所需的时隙数量。比如，假设一个PHY的带宽大小为100G，且被分为20个时隙，若第一业务流所需的带宽大小为10G，则第一业务流所需的时隙数量为2个，也就是说，第一业务流需要被映射至2个时隙上。
还应理解，若FlexE路径为域内的FlexE路径，即FlexE路径上的各节点在同一域内，则源节点所发送的路由信息可以携带该FlexE路径的全路由信息，即该FlexE路径上的每个节点的信息。比如，第一FlexE路径为域内的FlexE路径，即非跨域的FlexE路径时，第一转发节点为第一源节点的下一节点，并且第一转发节点根据该第一路由信息可知，第二转发节点为第一转发节点的下一节点，且第二转发节点的下一 节点为第一目的节点。
若FlexE路径为跨域的FlexE路径，即FlexE路径上的各节点不全都在同一域内，则源节点所发送的路由信息可以携带该FlexE路径的部分路由信息，该部分路由信息可以用于指示该FlexE路径上源节点、目的节点、以及边缘节点。比如，第一FlexE路径为跨域的FlexE路径时，第一FlexE路径的源节点为第一源节点，目的节点为第一目的节点，两个边缘节点分别为第一转发节点和第二转发节点，且第一转发节点为第二转发节点的上游节点。第一转发节点根据第一路由信息和第一业务流的带宽需求，可以自主确定第一转发节点至第二转发节点之间的路由信息，即确定第一转发节点至第二转发节点的路径上的各节点。其中，第一转发节点可以采用多种方法自主确定第一转发节点至第二转发节点之间的路由信息，例如可以采用最短路径方法等，具体地可以参照现有技术，为了简洁，此处不作赘述。
可选地，第一路径建立请求消息还可以包括路径类型信息，该路径类型信息用于指示建立的路径类型为FlexE路径。此外，本申请实施例中，也可以规定各节点默认需要建立的路径类型为FlexE路径。
可选地，本申请所涉及的诸如第一路径建立请求消息、第二路径建立请求消息(下文中将涉及)等路径建立请求消息，可以是资源预留协议(Resource Reservation Protocol-Traffic Engineering，RSVP)中的Path消息，但本申请实施例并不限定于Path消息。
S520，第一转发节点根据第一路径建立请求消息，建立第一转发节点至所述第二转发节点之间的第二FlexE路径，并在建立所述第二FlexE路径后，删除已建立的第一转发节点到第二转发节点之间的第三FlexE路径。
具体来讲，在接收到第一路径建立请求消息之前，若第一转发节点有传输业务流(例如，记作第二业务流)的需求，则第一转发节点可以建立第一转发节点到第二转发节点之间的FlexE路径(例如，记作第三FlexE路径)，通过第三FlexE路径传输第二业务流。在接收到第一路径建立请求消息后，第一转发节点可以根据第一业务流和第二业务流的带宽需求，重新建立一条第一转发节点到第二转发节点之间的FlexE路径(例如，记作第二FlexE路径)，在建立第二FlexE路径后，将第三FlexE路径上的流量(即，第二业务流)切换到第二FlexE路径上，并删除第三FlexE路径。这样，通过第二FlexE路径，可以进行第一业务流和第二业务流的转发。
可选地，所述第二FlexE路径复用建立所述第三FlexE路径时所建立的会话，即第二FlexE路径和第三FlexE路径与第二会话对应。
在建立第三FlexE路径的同时，会建立一个会话(session)(例如，记作第二会话)在建立第二FlexE路径时，可以基于第二会话建立第二FlexE路径，即第二FlexE路径与第二会话对应。通过这样的方法，能够与现有技术更大程度地互通。
应理解，会话可以定义为在特定的目标地址和传送协议上的数据流。例如，一次会话可以由一个三元组(目的地址，协议号，协议端口)来表示。关于目的地址，协议号，协议端口具体可以参照现有技术，为了简洁，此处不再赘述。
此外，在建立第二FlexE路径时，也可以重新建立一个会话，本申请实施例对此不作限定。
可选地，第二FlexE路径上用于传输第二业务流的时隙资源与第三FlexE路径上用于传输第二业务流的时隙资源相同。
也就是说，第二FlexE路径所预留的时隙资源中用于传输第二业务流的时隙资源与第三FlexE路径所预留时隙资源相同。通过这样的方法，能够与现有技术更大程度地互通。
S530，第一转发节点建立并保存第一FlexE路径和第二FlexE路径的对应关系，使得将第一业务流和第二业务流映射至第二FlexE路径的时隙上。
比如，第一转发节点可以通过建立表格的形式建立第一FlexE路径和第二FlexE路径的对应关系。在数据转发时，在接收到通过第一FlexE路径上转发的第一业务流时，第一转发节点可以根据该表格所示的对应关系，通过第二FlexE路径转发第一业务流。但应理解，本申请并不对体现第一FlexE路径和第二FlexE路径的对应关系的形式作具体限定。
本申请实施例的建立灵活以太网路径的方法，在已经建立传输第二业务流的第三FlexE路径的基础上，若还需要传输第一业务流，可以通过重新建立第一转发节点到第二转发节点之间的第二FlexE路径，将第一业务流和第二业务流汇聚到第二FlexE路径上进行转发，同时删除第三FlexE路径，这样能够减少第一转发节点和第二转发节点之间建立的FlexE路径的数量，从而能够降低第一转发节点和第二转发节点的控制面需要维护的FlexE路径的数量，进而能够降低第一转发节点和第二转发节点的控制面的管理复杂度以及维护FlexE路径所需的信令开销。
可选地，在S530步骤中，第一转发节点建立并保存第一FlexE路径和所述第二FlexE路径的对应关系，包括：
第一转发节点向第二FlexE路径上第一转发节点的下一节点发送第二路径建立请求消息，第二路径建立请求消息包括第二路由信息，第二路由信息用于指示第二FlexE路径上的节点信息，以便于第一转发节点的下一节点根据第二路由信息发送第二路径建立请求；第一转发节点接收第一转发节点的下一节点根据第二路径建立请求消息发送的第二资源预留消息；第一转发节点根据第二资源预留消息，确定第二FlexE路径上的第一时隙资源，并建立和保存第一时隙资源、第一FlexE路径和第二FlexE路径三者之间的对应关系，使得承载于第一FlexE路径上的第一业务流映射至第一时隙资源所对应的时隙上。
具体而言，第一转发节点接收到第一路径建立请求消息后，暂停第一路径建立请求消息的发送，并向第一转发节点的下一节点(例如，记作中间转发节点)发送第二路径建立请求消息，请求建立第二FlexE路径。中间转发节点根据第二路由信息，沿着第二FlexE路径的方向，向下一节点发送第二路径建立请求，直至第二路径建立请求消息到达第二转发节点。
第二转发节点接收到第二路径建立请求消息后，沿着第二FlexE路径的反方向发送响应第二路径建立请求消息的第二资源预留消息，沿着第二FlexE路径的反方向的各节点根据第二资源预留消息进行资源预留。其中，在第一转发节点接收到中间转发节点发送的第二资源预留消息后，第一转发节点可以确定第一时隙资源。这里，第一时隙资源包括第一转发节点转发第一业务流所使用的时隙资源。例如，第一时隙资源 包括接口1A上的时隙15和16。在进行业务流的转发时，第一转发节点可以将第一业务流映射至接口1A上的时隙15和16进行传输。
接着或同时，第一转发节点建立并保存第一时隙资源、第一FlexE路径和第二FlexE路径三者之间的对应关系。这样，在进行业务流的转发时，第一转发节点可以将承载于第一FlexE路径上的第一业务流映射至第一时隙资源所对应的时隙上进行传输。
举例来说，第一转发节点可以通过建立如表2所示的映射表，保存的第一时隙资源、第一FlexE路径和第二FlexE路径三者之间的对应关系。
表2
入FlexE路径 出FlexE路径 出接口 出时隙
第一FlexE路径 第二FlexE路径 接口1A 15，16
参见表2，第一时隙资源包括接口1A上的时隙15和16。在进行业务流转发时，第一转发节点接收到承载于第一FlexE路径上的第一业务流后，可以将第一业务流映射至接口1A上的时隙15和16上进行传输。
应理解，表2仅是表示第一时隙资源、第一FlexE路径和第二FlexE路径三者之间的对应关系的一种体现形式。第一转发节点还可以通过其他方式或形式保存第一时隙资源、第一FlexE路径和第二FlexE路径三者之间的对应关系，例如，第一转发节点还可以通过建立两个表格来保存第一时隙资源、第一FlexE路径和第二FlexE路径三者之间的对应关系，本申请实施例对于第一转发节点具体以怎样的形式保存第一时隙资源、第一FlexE路径和第二FlexE路径三者之间的对应关系不作具体限定。
可选地，本申请所涉及的诸如第一资源预留消息、第二资源预留消息(下文中将涉及)等资源预留消息，可以是RSVP中的Resv消息，但本申请实施例并不限定于Resv消息。
下面，结合图5，详细描述建立第二FlexE路径的一个具体实施例。
需要说明的是，图5所示的实施例中，第二FlexE路径上用于传输第二业务流的时隙资源与第三FlexE路径上用于传输第二业务流的时隙资源相同，因此，各节点仅需确定用于传输第一业务流的时隙资源。
S601，第一转发节点向中间转发节点发送第二路径建立请求消息。
具体地，第一转发节点在接收到第一路径建立请求消息后，暂停第一路径建立请求消息的发送，并通过向中间转发节点发送第二路径建立请求消息，请求建立第二FlexE路径。其中，第二路径建立请求消息可以携带带宽需求信息以及第二路由信息。其中，该带宽需求信息用于指示第一业务流和第二业务流的带宽需求，第二路由信息指示第二FlexE路径上的节点信息。
S602，中间转发节点在接收到第二路径建立请求消息后，沿着第二FlexE路径的方向，向第二转发节点发送第二路径建立请求。
S603，第二转发节点接收到第二路径建立请求消息后，沿着第二FlexE路径的反 方向向中间转发节点发送响应第二路径建立请求消息的第二资源预留消息。
S604，中间转发节点根据第二资源预留消息确定时隙资源#1，并且指示第二转发节点根据时隙资源#1更改第二转发节点的入接口的FlexE配置，使得第一业务流可以映射至时隙资源#1上进行传输。
应理解，时隙资源#1为中间转发节点转发第一业务流所使用的时隙资源，即中间转发节点的出接口的FlexE配置。例如，时隙资源#1可以是接口3A上的时隙8和10。在进行业务流的转发时，中间转发节点将第一业务流映射至接口3A上的时隙8和10进行传输。
在步骤S604中，可选地，第二转发节点向中间转发节点发送的第二资源预留消息可以携带时隙资源#1的指示信息，该时隙资源#1的指示信息用于指示中间转发节点所确定的时隙资源#1。具体来讲，第二转发节点在接收到第二路径建立请求消息后，查找空闲时隙，从空闲时隙中确定出时隙资源#1，然后再通过时隙资源#1的指示信息，将时隙资源#1告知中间转发节点。
进一步地，该指示信息可以是通用多协议标志交换协议(Generalized Multiprotocol Label Switching，GMPLS)标签，该GMPLS标签用于指示时隙资源#1。应理解，该GMPLS标签可以同时指示之前第三FlexE路径上用于传输第二业务流的时隙资源。应理解，本申请并不限于所述指示信息为GMPLS标签。
在步骤S604中，可选地，可以由中间转发节点确定时隙资源#1。具体来讲，第二转发节点通过第二资源预留消息请求中间转发节点确定时隙资源#1，中间转发节点在接收到第二资源预留消息后，查找空闲时隙，从空闲时隙中确定出时隙资源#1。
在通过例如上述两种可能的实现方式确定出时隙资源#1后，第一转发节点可以通过与中间转发节点之间的带内控制通道来更改中间转发节点的入接口上的FlexE配置，从而达到更改第二FlexE路径的时隙配置的目的。
S605，中间转发节点向第一转发节点发送第二资源预留消息。
S606，第一转发节点根据第二资源预留消息确定时隙资源#2(即，第一时隙资源的一例)，并指示中间转发节点根据时隙资源#2更改中间转发节点的入接口的FlexE配置，使得第一业务流可以映射至时隙资源#2上进行传输。
应理解，时隙资源#2为第一转发节点转发第一业务流所使用的时隙资源。例如，时隙资源#2可以是接口1A上的时隙15和16。在进行业务流的转发时，中间转发节点将第一业务流映射至接口1A上的时隙15和16进行传输。
还应理解，步骤S606的具体实现方式可以参照上文对步骤S604的描述，为了简洁，此处不再赘述。
另外，中间转发节点根据入接口和出接口的FlexE配置，可以建立如表3所示的时隙转发表。
表3
入接口 入时隙 出接口 出时隙
接口1A 15，16 接口3A 8，10
根据表3，中间转发节点在进行业务流的转发时，可以将从接口1A上的时隙15和16接收的第一业务流映射至接口3A上的时隙8和10进行传输。
S607，第一转发节点建立并保存表2所示的映射表。
这样，在进行业务流的转发时，第一转发节点可以将第一业务流映射至时隙资源#2所对应的时隙上进行传输。中间转发节点从时隙资源#2接收到第一业务流后，将第一业务流映射至时隙资源#1所对应的时隙上进行传输。
在本申请实施例中，第一转发节点建立第二FlexE路径后，继续沿着第一FlexE路径的方向发送第一路径建立请求消息。
可选地，在第一路径建立请求消息到达第二转发节点后，第二转发节点所执行的操作可以参照下文即将描述的实施例中的第一转发节点所执行的操作。
可选地，作为本申请一个实施例，该方法还可以包括：第一转发节点接收第三路径建立请求消息，第三路径建立请求消息用于建立第二源节点到第二目的节点之间的第四FlexE路径，第四FlexE路径用于传输第三业务流，第三路径建立请求消息包括第三路由信息，第三路由信息用于指示第四FlexE路径上的节点信息，其中，第四FlexE路径上的第一转发节点的下一节点为第二目的节点；第一转发节点向第二目的节点发送第三路径建立请求消息；第一转发节点接收第二目的节点根据第三路径建立请求消息发送的第三资源预留消息；第一转发节点根据第三资源预留消息确定第三时隙资源；第一转发节点建立并保存第三时隙资源和第五FlexE路径上的第四时隙资源的对应关系，使得第一转发节点将映射至第四时隙资源所对应的时隙上的第三业务流映射至第三时隙资源所对应的时隙上，其中，第五FlexE路径为第二转发节点到第一转发节点之间的FlexE路径，第三时隙资源所对应的时隙为第五FlexE路径上用于传输第三业务流的时隙。
具体来讲，在建立第二目的节点至第二源节点之间的FlexE路径(即，第四FlexE路径)时，在已建立第二转发节点至第一转发节点之间的第五FlexE路径的基础上，第二转发节点沿着第四FlexE路径的方向发送第三路径建立请求消息，在第三路径建立请求消息到达第一转发节点后，第一转发节点向下一节点(即，第一源节点)发送第三路径建立请求消息。第一源节点接收到第三路径建立请求消息后，向第一转发节点发送第三资源预留消息，请求第一转发节点进行资源预留。第一转发节点根据第三资源预留消息，预留第三时隙资源作为传输第三业务流的时隙资源。同时，建立并保存第三时隙资源和第五FlexE路径上的第四时隙资源的对应关系。这样，在进行业务流的转发时，第一转发节点可以根据该对应关系，将由第四FlexE路径上第一源节点的上一节点映射至第四时隙资源所对应的时隙上的第三业务流映射至第三时隙资源所对应的时隙上进行传输。
这里，第二目的节点可以是本文中的第一源节点，第二源节点可以是本文中的第一目的节点。
参照上述实施例，在建立第一FlexE路径的过程中，在第一路径建立请求消息到达第二转发节点后，第二转发节点沿着第一FlexE路径继续向下一节点发送第一路径建立请求消息。若第二转发节点的下一节点为第一目的节点，则在第一目的节点接收到第一路径建立请求消息后，第一目的节点向第二转发节点发送响应于第一路径建立 请求消息的第一资源预留消息。第二转发节点根据该第一资源预留消息，确定可用时隙资源(例如，记作第五时隙资源)，并指示第一目的节点根据第五时隙资源更改第一目的节点的入接口的FlexE配置。同时，第二转发节点保存第五时隙资源和第六时隙资源(即，第二FlexE路径上第二转发节点的上一节点发送第一业务流所使用的时隙，例如时隙资源#1)的对应关系。这样，在进行第一业务流的转发时，第二转发节点可以将通过第六时隙资源所对应的时隙上传输的第一业务流映射至第五时隙资源进行发送。
例如，以第六时隙资源为时隙资源#1，第五时隙资源为第二转发节点与第一目的节点之间的接口2C上的时隙17和27为例，第二转发节点可以通过建立表4所示的映射表保存第五时隙资源和第六时隙资源的对应关系。
表4
Figure PCTCN2018098610-appb-000001
参见表5，在进行数据转发时，第二转发节点可以将承载于入接口3A上的时隙8和10的第一业务流映射至出接口2C上的时隙17和27进行传输。
应理解，表5仅是表示第五时隙资源和第六时隙资源的对应关系的一种体现形式。第二转发节点还可以通过其他方式或形式保存第五时隙资源和第六时隙资源的对应关系，例如，第二转发节点还可以通过建立两个表格来保存第五时隙资源和第六时隙资源的对应关系。本申请实施例对于第二转发节点具体以怎样的形式保存第五时隙资源和第六时隙资源的对应关系不作具体限定。
在第二转发节点建立并保存第五时隙资源和第六时隙资源的对应关系后，第二转发节点沿着第一FlexE路径的反方向发送继续发送第一资源预留消息。
若第一转发节点的上一节点为第一源节点，第一资源预留消息到达第一转发节点后，第一转发节点向第一源节点发送第一资源预留消息。第一源节点接收到第一资源预留消息后，确定出第二时隙资源，并指示第一转发节点根据第二时隙资源配置第一转发节点的入接口上的FlexE配置，来建立第一FlexE路径。在配置第一转发节点的入接口上的FlexE配置的同时或者在配置完第一转发节点的入接口上的FlexE配置后，第一转发节点保存第二时隙资源和第一时隙资源的对应关系，这样，在进行数据转发时，第一转发节点可以根据第一时隙资源和第二时隙资源的对应关系，将映射至第二时隙资源所对应的时隙上的第一业务流映射至第一时隙资源所对应的时隙上。
举例来说，第二时隙资源可以是第一源节点和第一转发节点之间的接口1B上的时隙3和7。第一转发节点可以通过建立如表5所示的转发表保存第二时隙资源和第一时隙资源的对应关系。
表5
入接口 入时隙 出接口 出时隙
接口1B 3，7 接口1A 15，16
参见表1，第一源节点的转发面可以将第一业务流映射至在接口1B中的时隙3和7进行传输，第一转发节点将承载在接口1B中的时隙3和7上的第一业务流映射至接口1A上的时隙15和16进行传输。
应理解，表5仅是第一时隙资源和第二时隙资源的对应关系的一种体现形式。第一转发节点还可以通过其他方式或形式保存第一时隙资源和第二时隙资源的对应关系。例如，第一转发节点还可以通过建立两个或多个表格来保存第一时隙资源和第二时隙资源的对应关系，本申请实施例对于第一转发节点具体以怎样的形式保存第一时隙资源和第二时隙资源的对应关系不作具体限定。
还应理解，第一转发节点可以将表2和表5合并起来作为一个表格进行保存，这个表格可以是两个表格简单的拼接，也可以是合并表格2和3相同的内容后得到的表格，本申请实施例对此不作限定。
以下，结合图6，对本申请的建立FlexE路径的一个方法实施例进行详细描述。应理解，图6所示的方法中的第一源节点、第一转发节点、中间转发节点、第二转发节点和第一目的节点，可以分别对应于图3所示的场景中的节点11、13、14、16和17。
图6是根据本申请一个具体实施例的建立FlexE路径的方法的示意性交互图。
S701，第一源节点向第一转发节点发送第一路径建立请求消息，该第一路径建立请求消息包括第一业务流的带宽需求信息和第一路由信息。
S702，第一转发节点根据第一路由信息，可知需要建立经过第一转发节点到第二转发节点的FlexE路径，并判断第一转发节点到第二转发节点之间是否已建立FlexE路径。如果已建立FlexE路径，即第三FlexE路径，则判断是否有足够的时隙资源满足第一业务流的带宽需要。如果有足够的时隙资源满足第一业务流的带宽需要，则第一转发节点暂停第一路径建立请求消息的发送，建立第一转发节点到第二转发节点之间的第二FlexE路径。
在具体实施例时，可以参照图5所示的方法建立第二FlexE路径。为了简洁，此处不再赘述。
在建立好第二FlexE路径后，删除第三FlexE路径，这样，各节点不再需要维护第三FlexE路径。
S703，第二FlexE路径建立完成后，第一转发节点沿着第一FlexE的路径的方向，发送第一路径建立请求消息。
S704，中间转发节点接收到第一路径建立请求消息后，向第二转发节点发送第一路径建立请求消息。
S705，在第二转发节点接收到第一路径建立请求消息后，向第一目的节点发送第 一路径建立请求消息。
S706，第一目的节点在确定其可用时隙满足第一业务流的带宽需求后，向第二转发节点发送第一资源预留消息。
S707，第二转发节点根据第一资源预留消息进行资源预留。
具体地，第二转发节点根据第一资源预留消息确定与第一目的节点之间传输第一业务流所用的第五时隙资源，例如出接口2C上的时隙17和27，并指示第一目的节点更改第一目的节点的入接口上的FlexE配置。第二转发节点还可以通过建立如表4所示的转发表，保存第五时隙资源和第六时隙资源的对应关系。
相应地，第一目的节点根据第二转发节点的指示，更改入接口上的FlexE配置。
S708，第二转发节点沿着第一FlexE路径的反方向，发送第一资源预留消息。
S709，中间转发节点接收到第一资源预留消息后，继续向第一转发节点发送第一资源预留消息。
S710，第一转发节点向第一源节点发送第一资源预留消息。
S711，在第一源节点接收到第一转发节点发送的第一资源预留消息后，进行资源预留。
具体地，第一源节点确定出与第一转发节点之间传输第一业务流的第二时隙资源，例如接口1B上的时隙3和7，并指示第一转发节点更改第一转发节点的入接口上的FlexE配置。
相应地，第一转发节点根据第一源节点的指示，更改入接口上的FlexE配置。并且，建立第二时隙资源和第一时隙资源的映射关系。
至此，完成第一FlexE路径的建立。之后，在进行业务流的转发时，第一业务流可以按照表2～表5所示的映射表/转发表进行转发。
应理解，第二业务流可以按照之前建立第三FlexE路径时所建立并保存的时隙映射表进行转发，并本申请并不限于此。
本申请实施例的建立灵活以太网路径的方法，在已经建立传输第二业务流的第三FlexE路径的基础上，若还需要传输第一业务流，可以通过重新建立第一转发节点到第二转发节点之间的第二FlexE路径，将第一业务流和第二业务流汇聚到第二FlexE路径上进行转发，同时删除第三FlexE路径，这样能够减少第一转发节点和第二转发节点之间建立的FlexE路径的数量，从而能够降低第一转发节点和第二转发节点的控制面需要维护的FlexE路径的数量，进而能够降低第一转发节点和第二转发节点的控制面的管理复杂度以及维护FlexE路径所需的信令开销。
下面对本申请的装置实施例进行描述，由于装置实施例可以执行上述方法，因此未详细描述的部分可以参见前面各方法实施例。
图7是本申请一个实施例的网络设备的示意性结构图。图7所示的网络设备800包括：收发单元810和处理单元820。
收发单元810，用于接收第一源节点发送的第一路径建立请求消息，第一路径建立请求消息用于建立第一源节点到第一目的节点之间的第一FlexE路径，第一FlexE路径用于传输第一业务流，第一路径建立请求消息包括第一路由信息，第一路由信息用于指示第一FlexE路径上的节点信息，其中，第一FlexE路径上的第一转发节点为 第一FlexE路径上的第二转发节点的上游节点。
处理单元820，用于根据第一路径建立请求消息，建立第一转发节点至第二转发节点之间的第二FlexE路径，并在建立第二FlexE路径后，删除已建立的第一转发节点到第二转发节点之间的第三FlexE路径，其中，第三FlexE路径用于传输第二业务流，第二FlexE路径能够满足第一业务流的带宽需求和第二业务流的带宽需求。
处理单元820还用于，建立并保存第一FlexE路径和第二FlexE路径的对应关系，使得将第一业务流和第二业务流映射至第二FlexE路径的时隙上。
应理解，该网络设备800中各单元分别用于执行上述各方法中由第一转发节点(例如，PE设备)执行的各动作或处理过程。这里，为了避免赘述，省略其详细说明。
还应理解，网络设备800也可以是本申请实施例中的第二转发节点。
图8是本申请另一实施例提供的网络设备的示意性结构图。图8的建立灵活以太网路径的网络设备900包括存储器910、处理器920和通信接口930。存储器910、处理器920和通信接口930之间通过内部连接通路互相通信，传递控制和/或数据信号。处理器920对应于图7中的处理单元820，换句话说，处理器920能够执行图7中的处理单元820执行的操作。通信接口930对应于图7中的收发单元810，换句话说，通信接口930能够执行图7中的收发单元810执行的操作。下面对存储器910、处理器920和通信接口930进行详细描述。
所述存储器910用于存储程序代码；
所述处理器920用于执行所述存储器910中存储的程序代码，当所述程序代码被执行时，通信接口930用于接收第一源节点发送的第一路径建立请求消息，所述第一路径建立请求消息用于建立所述第一源节点到第一目的节点之间的第一FlexE路径，所述第一FlexE路径用于传输第一业务流，所述第一路径建立请求消息包括第一路由信息，所述第一路由信息用于指示所述第一FlexE路径上的节点信息，其中，所述第一FlexE路径上的所述第一转发节点为所述第一FlexE路径上的第二转发节点的上游节点；
所述处理器920，用于根据所述第一路径建立请求消息，建立所述第一转发节点至所述第二转发节点之间的第二FlexE路径，并在建立所述第二FlexE路径后，删除已建立的所述第一转发节点到所述第二转发节点之间的第三FlexE路径，其中，所述第三FlexE路径用于传输第二业务流，所述第二FlexE路径能够满足所述第一业务流的带宽需求和所述第二业务流的带宽需求。
所述处理器920还用于，建立并保存所述第一FlexE路径和所述第二FlexE路径的对应关系，使得将所述第一业务流和所述第二业务流映射至所述第二FlexE路径的时隙上。
应理解，该网络设备900中各单元分别用于执行上述各方法中由第一转发节点执行的各动作或处理过程。这里，为了避免赘述，省略其详细说明。
应理解，上文中的网络设备900可以是灵活以太网中的网络设备，例如可以是灵活以太网中的路由设备，或者，也可以是该路由设备中的单板。
本申请实施例可以应用于处理器中，或者由处理器实现。处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过 处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是中央处理单元(central processing unit，CPU)、该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件器组合执行完成。软件器可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DRRAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可 以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (12)

  1. 一种建立灵活以太网FlexE路径的方法，其特征在于，包括：
    第一转发节点接收第一源节点发送的第一路径建立请求消息，所述第一路径建立请求消息用于建立所述第一源节点到第一目的节点之间的第一FlexE路径，所述第一FlexE路径用于传输第一业务流，所述第一路径建立请求消息包括第一路由信息，所述第一路由信息用于指示所述第一FlexE路径上的节点信息，其中，所述第一FlexE路径上的所述第一转发节点为所述第一FlexE路径上的第二转发节点的上游节点；
    所述第一转发节点根据所述第一路径建立请求消息，建立所述第一转发节点至所述第二转发节点之间的第二FlexE路径，并在建立所述第二FlexE路径后，删除已建立的所述第一转发节点到所述第二转发节点之间的第三FlexE路径，其中，所述第三FlexE路径用于传输第二业务流，所述第二FlexE路径能够满足所述第一业务流的带宽需求和所述第二业务流的带宽需求；
    所述第一转发节点建立并保存所述第一FlexE路径和所述第二FlexE路径的对应关系，使得将所述第一业务流和所述第二业务流映射至所述第二FlexE路径的时隙上。
  2. 如权利要求1所述的方法，其特征在于，所述第二FlexE路径复用建立所述第三FlexE路径时所建立的会话。
  3. 如权利要求1或2所述的方法，其特征在于，所述第二FlexE路径上用于传输所述第二业务流的时隙资源与所述第三FlexE路径上用于传输所述第二业务流的时隙资源相同。
  4. 如权利要求1至3中任一项所述的方法，所述第一转发节点建立并保存所述第一FlexE路径和所述第二FlexE路径的对应关系，包括：
    所述第一转发节点向所述第二FlexE路径上所述第一转发节点的下一节点发送第二路径建立请求消息，所述第二路径建立请求消息包括第二路由信息，所述第二路由信息用于指示所述第二FlexE路径上的节点信息，以便于所述第一转发节点的下一节点根据所述第二路由信息发送所述第二路径建立请求；
    所述第一转发节点接收所述第一转发节点的下一节点根据所述第二路径建立请求消息发送的第二资源预留消息；
    所述第一转发节点根据所述第二资源预留消息，确定所述第二FlexE路径上的第一时隙资源，并建立和保存所述第一时隙资源、所述第一FlexE路径和所述第二FlexE路径三者之间的对应关系，使得承载于所述第一FlexE路径上的所述第一业务流映射至所述第一时隙资源所对应的时隙上。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一转发节点接收第三路径建立请求消息，所述第三路径建立请求消息用于建立第二源节点到第二目的节点之间的第四FlexE路径，所述第四FlexE路径用于传输第三业务流，所述第三路径建立请求消息包括第三路由信息，所述第三路由信息用于指示所述第四FlexE路径上的节点信息，其中，所述第四FlexE路径上的所述第一转发节点的下一节点为所述第二目的节点；
    所述第一转发节点向所述第二目的节点发送所述第三路径建立请求消息；
    所述第一转发节点接收所述第二目的节点根据所述第三路径建立请求消息发送的 第三资源预留消息；
    所述第一转发节点根据所述第三资源预留消息确定第三时隙资源；
    所述第一转发节点建立并保存所述第三时隙资源和第五FlexE路径上的第四时隙资源的对应关系，使得所述第一转发节点将映射至所述第四时隙资源所对应的时隙上的所述第三业务流映射至所述第三时隙资源所对应的时隙上，其中，所述第五FlexE路径为所述第二转发节点到所述第一转发节点之间的FlexE路径，所述第三时隙资源所对应的时隙为所述第五FlexE路径上用于传输所述第三业务流的时隙。
  6. 一种网络设备，其特征在于，包括：
    收发单元，用于接收第一源节点发送的第一路径建立请求消息，所述第一路径建立请求消息用于建立所述第一源节点到第一目的节点之间的第一FlexE路径，所述第一FlexE路径用于传输第一业务流，所述第一路径建立请求消息包括第一路由信息，所述第一路由信息用于指示所述第一FlexE路径上的节点信息，其中，所述第一FlexE路径上的所述第一转发节点为所述第一FlexE路径上的第二转发节点的上游节点；
    处理单元，用于根据所述第一路径建立请求消息，建立所述第一转发节点至所述第二转发节点之间的第二FlexE路径，并在建立所述第二FlexE路径后，删除已建立的所述第一转发节点到所述第二转发节点之间的第三FlexE路径，其中，所述第三FlexE路径用于传输第二业务流，所述第二FlexE路径能够满足所述第一业务流的带宽需求和所述第二业务流的带宽需求；
    所述处理单元还用于，建立并保存所述第一FlexE路径和所述第二FlexE路径的对应关系，使得将所述第一业务流和所述第二业务流映射至所述第二FlexE路径的时隙上。
  7. 如权利要求6所述的网络设备，其特征在于，所述第二FlexE路径复用建立所述第三FlexE路径时所建立的会话。
  8. 如权利要求6或7所述的网络设备，其特征在于，所述第二FlexE路径上用于传输所述第二业务流的时隙资源与所述第三FlexE路径上用于传输所述第二业务流的时隙资源相同。
  9. 如权利要求6至8中任一项所述的网络设备，所述收发单元具体用于：
    向所述第二FlexE路径上所述第一转发节点的下一节点发送第二路径建立请求消息，所述第二路径建立请求消息包括第二路由信息，所述第二路由信息用于指示所述第二FlexE路径上的节点信息，以便于所述第一转发节点的下一节点根据所述第二路由信息发送所述第二路径建立请求；
    所述第一转发节点接收所述第一转发节点的下一节点根据所述第二路径建立请求消息发送的第二资源预留消息；
    所述处理单元具体用于，根据所述第二资源预留消息，确定所述第二FlexE路径上的第一时隙资源，并建立和保存所述第一时隙资源、所述第一FlexE路径和所述第二FlexE路径三者之间的对应关系，使得承载于所述第一FlexE路径上的所述第一业务流映射至所述第一时隙资源所对应的时隙上。
  10. 如权利要求6至9中任一项所述的网络设备，其特征在于，所述收发单元还用于：
    接收第三路径建立请求消息，所述第三路径建立请求消息用于建立第二源节点到第二目的节点之间的第四FlexE路径，所述第四FlexE路径用于传输第三业务流，所述第三路径建立请求消息包括第三路由信息，所述第三路由信息用于指示所述第四FlexE路径上的节点信息，其中，所述第四FlexE路径上的所述第一转发节点的下一节点为所述第二目的节点；
    向所述第二目的节点发送所述第三路径建立请求消息；
    接收所述第二目的节点根据所述第三路径建立请求消息发送的第三资源预留消息；
    所述处理单元还用于，根据所述第三资源预留消息确定第三时隙资源；
    所述处理单元还用于，建立并保存所述第三时隙资源和第五FlexE路径上的第四时隙资源的对应关系，使得所述第一转发节点将映射至所述第四时隙资源所对应的时隙上的所述第三业务流映射至所述第三时隙资源所对应的时隙上，其中，所述第五FlexE路径为所述第二转发节点到所述第一转发节点之间的FlexE路径，所述第三时隙资源所对应的时隙为所述第五FlexE路径上用于传输所述第三业务流的时隙。
  11. 一种网络设备，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于执行所述存储器中存储的计算机程序，以使得所述装置执行如权利要求1至5中任一项所述的方法。
  12. 一种计算机可读存储介质，包括计算机程序，当其在计算机上运行时，使得所述计算机执行如权利要求1至5中任意一项所述的方法。
PCT/CN2018/098610 2017-08-04 2018-08-03 建立灵活以太网路径的方法和网络设备 WO2019024930A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18841043.5A EP3641242B1 (en) 2017-08-04 2018-08-03 Method and network device for establishing flexible ethernet path
US16/749,506 US11228526B2 (en) 2017-08-04 2020-01-22 Flexible ethernet path establishment method and network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710662235.0A CN107612825B (zh) 2017-08-04 2017-08-04 建立灵活以太网路径的方法和网络设备
CN201710662235.0 2017-08-04

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/749,506 Continuation US11228526B2 (en) 2017-08-04 2020-01-22 Flexible ethernet path establishment method and network device

Publications (1)

Publication Number Publication Date
WO2019024930A1 true WO2019024930A1 (zh) 2019-02-07

Family

ID=61064673

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/098610 WO2019024930A1 (zh) 2017-08-04 2018-08-03 建立灵活以太网路径的方法和网络设备

Country Status (4)

Country Link
US (1) US11228526B2 (zh)
EP (1) EP3641242B1 (zh)
CN (1) CN107612825B (zh)
WO (1) WO2019024930A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022001285A1 (zh) * 2020-07-03 2022-01-06 华为技术有限公司 一种自动配置灵活以太FlexE的方法及装置

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107612825B (zh) 2017-08-04 2020-10-27 华为技术有限公司 建立灵活以太网路径的方法和网络设备
CN110138498B (zh) * 2018-02-02 2021-10-22 中兴通讯股份有限公司 数据交织方法与数据解交织方法、存储介质、处理器
CN110247787B (zh) * 2018-03-08 2022-02-18 中兴通讯股份有限公司 一种灵活以太网路径建立的方法、网元和控制设备
CN110266612B (zh) * 2018-03-12 2022-01-25 中兴通讯股份有限公司 数据传输方法及装置、网络设备及存储介质
CN112491687B (zh) * 2018-03-29 2022-04-12 华为技术有限公司 一种处理报文的方法及装置
CN114363184A (zh) * 2018-05-31 2022-04-15 华为技术有限公司 灵活以太网中调整传输通道的带宽方法和装置
CN111278059B (zh) * 2018-12-04 2023-09-01 中兴通讯股份有限公司 一种报文转发方法和装置
CN111510311B (zh) * 2019-01-30 2022-10-28 中兴通讯股份有限公司 配置策略的确定方法及装置、存储介质
CN112532522B (zh) * 2019-09-19 2023-09-05 中兴通讯股份有限公司 一种业务路径的建立方法、装置、电子设备
CN116192726A (zh) * 2020-03-20 2023-05-30 华为技术有限公司 转发路径建立方法、装置以及计算机可读存储介质
CN113839870B (zh) * 2020-06-24 2023-01-13 华为技术有限公司 路径创建方法、装置及系统
US11363115B2 (en) * 2020-11-05 2022-06-14 Servicenow, Inc. Integrated operational communications between computational instances of a remote network management platform
CN115087106A (zh) * 2021-03-15 2022-09-20 中兴通讯股份有限公司 时隙配置方法、业务路径创建方法、装置、设备及介质
CN113890827B (zh) * 2021-12-03 2022-04-15 国网江苏省电力有限公司信息通信分公司 电力通信资源分配方法、装置、存储介质以及电子设备
WO2023165412A1 (zh) * 2022-03-02 2023-09-07 华为技术有限公司 数据处理方法、装置、设备、系统及计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170005949A1 (en) * 2015-06-30 2017-01-05 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
CN106803814A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种灵活以太网路径的建立方法、装置及系统
CN106803811A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种路由信息的获取方法及装置
CN107612825A (zh) * 2017-08-04 2018-01-19 华为技术有限公司 建立灵活以太网路径的方法和网络设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7127056B2 (en) * 2000-12-26 2006-10-24 Nortel Networks Limited Dynamic adaptation to congestion in connection-oriented networks
US8218445B2 (en) * 2006-06-02 2012-07-10 Ciena Corporation Smart ethernet edge networking system
CN107204941A (zh) * 2016-03-18 2017-09-26 中兴通讯股份有限公司 一种灵活以太网路径建立的方法和装置
US10505655B2 (en) * 2016-07-07 2019-12-10 Infinera Corp. FlexE GMPLS signaling extensions

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170005949A1 (en) * 2015-06-30 2017-01-05 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
CN106803814A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种灵活以太网路径的建立方法、装置及系统
CN106803811A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种路由信息的获取方法及装置
CN107612825A (zh) * 2017-08-04 2018-01-19 华为技术有限公司 建立灵活以太网路径的方法和网络设备

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022001285A1 (zh) * 2020-07-03 2022-01-06 华为技术有限公司 一种自动配置灵活以太FlexE的方法及装置

Also Published As

Publication number Publication date
CN107612825B (zh) 2020-10-27
EP3641242A4 (en) 2020-05-13
US20200162376A1 (en) 2020-05-21
EP3641242B1 (en) 2021-10-06
US11228526B2 (en) 2022-01-18
EP3641242A1 (en) 2020-04-22
CN107612825A (zh) 2018-01-19

Similar Documents

Publication Publication Date Title
WO2019024930A1 (zh) 建立灵活以太网路径的方法和网络设备
JP7079866B2 (ja) パケット処理方法、及びデバイス
KR102240140B1 (ko) 전송 레이트 조정 방법 및 네트워크 장치
US10554542B2 (en) Label distribution method and device
WO2018120917A1 (zh) 基于灵活以太网的业务流传输方法、装置和通信系统
CA2382271C (en) Circuit emulation service over an internet protocol network
WO2017157052A1 (zh) 基于隧道绑定的通信方法和网络设备
KR102342286B1 (ko) Dcn 메시지 처리 방법, 네트워크 디바이스, 및 네트워크 시스템
US8913623B2 (en) Method and apparatus for processing labeled flows in a communications access network
EP1585260B1 (en) Apparatus and method for terminating service emulation instances
US6895008B2 (en) Label switching router
US10992385B2 (en) Apparatus and method for joint profile-based slicing of mobile access and optical backhaul
JP5413452B2 (ja) ネットワーク通信システム、通信装置、ネットワーク連携方法及びプログラム
US10601602B2 (en) Hybrid data transport solution, in particular for satellite links
CN112585910B (zh) 在广域网中建立安全、低延迟、优化路径的方法和装置
WO2020114083A1 (zh) 一种ioam信息的处理方法和装置
KR100388066B1 (ko) 다수의 인터넷 프로토콜 패킷 포워딩 엔진을 탑재한 멀티프로토콜 레이블 스위칭 시스템에서의 확장 레이블스위치드 경로 설정방법
US11082255B1 (en) Method and an apparatus for establishing secure, low latency, optimized paths in a wide area network
EP1170904A1 (en) Communications network and method for routing data packets
KR20050029483A (ko) 엠피엘에스(ｍｐｌｓ) 망에서 확장성을 고려한티디엠(ｔｄｍ) 가상회선 제어방법

Legal Events

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

Ref document number: 18841043

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018841043

Country of ref document: EP

Effective date: 20200116

NENP Non-entry into the national phase

Ref country code: DE