WO2019085809A1 - 获得目标传输路径的方法、相关设备及系统 - Google Patents

获得目标传输路径的方法、相关设备及系统 Download PDF

Info

Publication number
WO2019085809A1
WO2019085809A1 PCT/CN2018/111811 CN2018111811W WO2019085809A1 WO 2019085809 A1 WO2019085809 A1 WO 2019085809A1 CN 2018111811 W CN2018111811 W CN 2018111811W WO 2019085809 A1 WO2019085809 A1 WO 2019085809A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
node
information
flexe
path
Prior art date
Application number
PCT/CN2018/111811
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 EP18873491.7A priority Critical patent/EP3694153B1/en
Priority to JP2020523980A priority patent/JP7026788B2/ja
Publication of WO2019085809A1 publication Critical patent/WO2019085809A1/zh
Priority to US16/860,777 priority patent/US11171860B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/26—Route discovery packet
    • 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
    • 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/28—Routing or path finding of packets in data switching networks using route fault recovery
    • 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/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers

Definitions

  • the present application relates to the field of communications, and in particular, to a method, related device, and system for obtaining a target transmission path.
  • the Flexible Ethernet (FlexE) implementation protocol published by the Optical Internetworking Forun (OIF), defines a shim layer between the medium access control layer and the physical layer.
  • FlexE-based forwarding the transmitting FlexE device sends the FlexE client's packet to the receiving FlexE device using the time slot corresponding to the FlexE client.
  • the receiving end FlexE device obtains the data sent by the transmitting end FlexE device from the time slot corresponding to the FlexE client to recover the message of the FlexE client.
  • IP Internet Protocol
  • ICMP Internet Control Message Protocol
  • Text hop-by-hop tracking and sending IP routes along the way.
  • the IP routing forwarding table needs to be searched for the path detection packet, but the 1.5 layer involved in the FlexE (the data transmission layer involved in the FlexE protocol is located in the Open System Interconnect (OSI) 7-layer model. Between the medium access control layer and the physical layer, the data transmission layer using Time Division Multiplexing (TDM) mode does not use such a forwarding table, and cannot identify a specific message in the data stream.
  • OSI Open System Interconnect
  • the path tracking mechanism set for the Ethernet packet network working in the medium access control layer needs to use multicast forwarding when transmitting the path detection packet.
  • a specific type of Ethernet frame (using a specific multicast address and Ethernet type) is used as a path tracking probe message.
  • the 1.5-layer network involved in FlexE does not support multicast and cannot parse and identify Ethernet frames in the data stream.
  • the embodiment provides a method, a related device and a system for obtaining a target transmission path, and provides a path discovery mechanism under a 1.5-layer network using a FlexE interface.
  • the embodiment of the present application provides a method for obtaining a target transmission path, where the method is applied to a flexible Ethernet FlexE networking network, where the method includes: receiving, by a first node, a request query sent by a second node.
  • the information includes: the first node identity information, the first FlexE client information, the first physical interface identifier information, the second FlexE client information, and the second physical interface identifier information; wherein the first FlexE client
  • the information includes: first time slot information carrying the first FlexE client, first FlexE group information carrying the first FlexE client; the first physical interface identification information includes a physical interface that carries the first FlexE client Identification information; the second FlexE client information includes: second time slot information carrying the second FlexE client, and second Flex carrying the second FlexE client E-group information; the second physical interface identifier information includes physical interface identifier information that carries the second FlexE client; a first time slot that carries the first FlexE client and a second time that carries the second FlexE client There is a cross relationship between the gaps.
  • the transmission path and comparison of the FlexE network segment to the segment can be dynamically discovered in real time. Plan the deployed transmission path and the actually discovered path to evaluate the operation of the network. It can also detect connection connectivity on the transmission path and locate faulty nodes on the transmission path within the FlexE network.
  • the method further includes: querying the time slot exchange mapping according to the first message. Forming a third message according to the first message, and sending the third message to the third node if the query is performed by querying the time slot exchange mapping table; if the time slot exchange mapping table does not exist The result of the query generates a second message according to the first message.
  • the embodiment of the present application can query the cross-map of the time slot allocation table of the FlexE client on the path node and record the cross-mapping relationship as a one-hop transmission path.
  • the query result exists, record the query result and generate a third message. And sending the third message to the next hop node. If the query result does not exist, the path is terminated at the node, the second hop node returns a second message, the second message records the path information of each hop node, and the path information in the second message is extracted to obtain the target transmission path.
  • the first FlexE client includes the identifier information
  • the querying the time slot exchange mapping table according to the first message includes: determining, according to the identifier information included by the first FlexE client, the bearer First slot information of the first FlexE client; determining, according to the first slot information, first FlexE group information that carries the first FlexE client; according to the first slot information and the first FlexE group information Query the time slot exchange mapping table.
  • the embodiment of the present application may determine, by using the first FlexE client, the identifier information to determine the first time slot information of the first FlexE client, and determine the first FlexE group information that carries the first FlexE client.
  • the second FlexE client information after the time slot crossing is obtained by using the first time slot information and the first FlexE group information as a query condition.
  • the querying the time slot exchange mapping table according to the first message includes: querying the time slot exchange mapping table according to the first FlexE client information recorded by the first message.
  • the time slot exchange mapping table may be queried according to the first time slot information of the first FlexE client and the first FlexE group information of the first FlexE client, and the query result is obtained, thereby obtaining the FlexE client at the node.
  • the query result includes second time slot information carrying a second FlexE client, second FlexE group information that carries the second FlexE client, and the first message generation And the third message is sent to the third node, and the third message is generated according to the first message, and sent to the third node on the physical interface that carries the second FlexE client.
  • the third message includes second time slot information carrying a second FlexE client, second FlexE group information that carries the second FlexE client, and the first message generation
  • the third message is sent to the third node, and the third message is generated according to the first message, and sent to the third node on the physical interface that carries the second FlexE client.
  • the third message includes second time slot information carrying a second FlexE client, second FlexE group information that carries the second FlexE client, and the first message generation
  • the third message is sent to the third node, and the third message is generated according to the first message, and sent to the third node on the physical interface that carries the second FlexE client.
  • the third message is generated according to the first message, and the third message is sent to the third node on the physical interface that carries the second FlexE client according to the query result.
  • the third message includes a path information entry, where the path entry information includes a path information entry in the first message and path information of the first node;
  • the path information of the first node includes the first FlexE client information, identifier information of a physical interface that carries the first FlexE client, the second FlexE client information, and physical interface identifier information that carries the second FlexE client. .
  • the path information of the FlexE client on the node may be added on the basis of the path information entry of the first message, so that the third message is generated, that is, the path information of the node is recorded to the path information table entry. .
  • the method further includes: if the third message is not received within the specified time period Generating the second message according to the first message, where the second message is generated according to the first message, where the fourth message includes a path information entry; the path information entry includes at least the third message The path information of the node.
  • the second message is returned to the second node, and the second node can read the path information entry in the second message to obtain the transmission path.
  • the second message includes a path information entry, where the path information entry includes a path information entry in the first message and path information of the first node;
  • the path information of the first node includes the first FlexE client information, identifier information of a physical interface that carries the first FlexE client, the second FlexE client information, and physical interface identifier information that carries the second FlexE client. .
  • the path information of the node may be added when the second message is returned, that is, the path information of the first node is added on the basis of the path information entry of the first message, and the second message is generated.
  • the generating the second message according to the first message includes: generating, according to the path information entry in the first message, the second message;
  • the second message includes a path information entry;
  • the path information entry includes a path information entry in the first message.
  • the transmission path is terminated at the node, and the path information entry in the first message is directly used as the path information entry in the second message, and returns to the first After the two nodes, the second node can read the path information entry in the second message to obtain a transmission path.
  • the method after the first node receives the first message sent by the second node to query the first FlexE client transmission path, before the first node sends the second message to the second node, the method also includes:
  • the embodiment of the present application may generate a second message according to the fourth message returned by the third node. After the second message is returned to the second node, the second node may read the path information entry in the second message to obtain the transmission. path.
  • the second message includes a path information entry, where the path information entry includes a path information entry in the fourth message.
  • the path information of the node is added to the path information table in the process of the second node sending the first message to the first node, so in the process of returning the second message, the fourth message may be directly
  • the path information entry is used as the path information entry of the second message.
  • the second message includes a path information entry, where the path information entry includes a path information entry in the fourth message and path information of the first node;
  • the path information of the first node includes the first FlexE client information, identifier information of a physical interface that carries the first FlexE client, information of the second FlexE client, and a physical interface identifier that carries the second FlexE client. information.
  • the path information of the node is added to the path information table in the process of the first node returning the second message to the second node, so the path information of the node is added on the basis of the path information entry of the fourth message. , as the path information entry of the second message.
  • the first message, the second message, the third message, and the fourth message are all carried by at least one FlexE overhead frame.
  • each message can be carried by the FlexE overhead frame to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • the embodiment of the present application provides a method for obtaining a target transmission path, where the method is applied to a flexible Ethernet FlexE networking network, where the method includes: the second node sends a request query to the first node. a first message of the FlexE client transmission path; the second node receives the second message sent by the first node; wherein the second message includes a path information entry; the path information entry includes at least one path
  • the information includes: the first node identity information, the first FlexE client information, the first physical interface identifier information, the second FlexE client information, and the second physical interface identifier information; wherein the first FlexE client
  • the information includes: first time slot information carrying the first FlexE client, first FlexE group information carrying the first FlexE client; the first physical interface identification information includes a physical interface that carries the first FlexE client Identification information; the second FlexE client information includes: second time slot information carrying a second FlexE client, and a second FlexE group carrying the second FlexE client
  • the second physical interface identifier information includes physical interface
  • the entry information and the egress information of the FlexE client on the path node can be recorded as the transmission path of each hop, and the transmission path of the FlexE network segment to the segment can be dynamically discovered in real time, and the transmission path of the planned deployment is compared. With the actual discovered path to assess the operation of the network, it is also possible to detect connectivity connectivity on the transmission path and locate faulty nodes on the transmission path within the FlexE network.
  • the first message and the second message are all carried by at least one FlexE overhead frame.
  • each message in the transmission process can be carried by the FlexE overhead frame to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the bearer efficiency of the data path.
  • the embodiment of the present application provides a first node, where the first node is applied to a flexible Ethernet FlexE networking network, where the first node includes: a first receiving unit, configured to receive a second node. Sending a request to query a first message of a first FlexE client transmission path; a first sending unit, configured to send a second message to the second node; wherein the second message includes a path information entry; the path information
  • the entry includes at least one path information, where the path information includes: the first node identity information, the first FlexE client information, the first physical interface identifier information, the second FlexE client information, and the second physical interface identifier information;
  • the first FlexE client information includes: first slot information carrying the first FlexE client, first FlexE group information carrying the first FlexE client; the first physical interface identifier information includes carrying the Physical interface identification information of the first FlexE client; the second FlexE client information includes: second time slot information carrying the second FlexE client, and carrying the second FlexE client Two FlexE group information; the second physical physical
  • the first node further includes: a query unit, configured to: after the first receiving unit receives the first message sent by the second node and query the first FlexE client transmission path, according to the a first message query time slot exchange mapping table; a first generating unit, configured to generate a third message according to the first message if the query result is queried by the query unit to query the time slot exchange mapping table, and The third node sends the third message, and the second generating unit is configured to generate a second message according to the first message if the query unit does not query the time slot exchange mapping table to have a query result.
  • a query unit configured to: after the first receiving unit receives the first message sent by the second node and query the first FlexE client transmission path, according to the a first message query time slot exchange mapping table
  • a first generating unit configured to generate a third message according to the first message if the query result is queried by the query unit to query the time slot exchange mapping table, and The third node sends the third message
  • the second generating unit is configured
  • the first FlexE client includes the identifier information
  • the query unit includes: a first determining subunit, configured to determine, according to the identifier information included by the first FlexE client, the first a first time slot information of the FlexE client, a second determining subunit, configured to determine, according to the first time slot information, first FlexE group information that carries the first FlexE client, and a query subunit, according to the first The time slot information and the first FlexE group information query the time slot exchange mapping table.
  • the querying unit is configured to: query the time slot exchange mapping table according to the first FlexE client information recorded by the first message.
  • the query result includes second time slot information carrying a second FlexE client, second FlexE group information that carries the second FlexE client, and the first generating unit is configured to: The first message generates a third message, and the third message is sent to the third node on a physical interface that carries the second FlexE client.
  • the third message includes a path information entry, where the path entry information includes a path information entry in the first message and path information of the first node;
  • the path information of the first node includes the first FlexE client information, identifier information of a physical interface that carries the first FlexE client, the second FlexE client information, and a physical interface that carries the second FlexE client. Identification information.
  • the first node further includes: a third generating unit, configured to generate, by the first generating unit, a third message according to the first message, and send the After the third message, if the fourth message sent by the third node is not received within the specified duration, the second message is generated according to the first message, where the fourth message includes a path information table.
  • the path information table entry includes at least path information of the third node.
  • the second message includes a path information entry, where the path information entry includes a path information entry in the first message and path information of the first node;
  • the path information of the first node includes information of the first FlexE client, identifier information of a physical interface carrying the first FlexE client, information of the second FlexE client, and carrying the second FlexE client. Physical interface identification information.
  • the second generating unit is configured to: generate the second message according to the path information entry in the first message; where the second message includes a path information entry; The path information entry includes a path information entry in the first message.
  • the first node further includes: a second receiving unit, configured to: after receiving, by the first receiving unit, the first message sent by the second node to query the first FlexE client transmission path, Receiving, by the first sending unit, the fourth message sent by the third node, before the sending, by the first sending unit, the fourth message, where the fourth message includes a path information entry; the path information entry includes at least The path information of the third node, and the fourth generating unit, configured to generate the second message according to the fourth message.
  • a second receiving unit configured to: after receiving, by the first receiving unit, the first message sent by the second node to query the first FlexE client transmission path, Receiving, by the first sending unit, the fourth message sent by the third node, before the sending, by the first sending unit, the fourth message, where the fourth message includes a path information entry; the path information entry includes at least The path information of the third node, and the fourth generating unit, configured to generate the second message according to the fourth message.
  • the second message includes a path information entry, where the path information entry includes a path information entry in the fourth message.
  • the second message includes a path information entry, where the path information entry includes a path information entry in the fourth message and path information of the first node;
  • the path information of the first node includes information of the first FlexE client, identifier information of a physical interface carrying the first FlexE client, information of the second FlexE client, and carrying the second FlexE client. Physical interface identification information.
  • the first message, the second message, the third message, and the fourth message are all carried by at least one FlexE overhead frame.
  • the embodiment of the present application provides a second node, where the second node is applied to a flexible Ethernet FlexE networking network, and the second node includes: a second sending unit, configured to use the first node Sending a request to query a first message of the first FlexE client transmission path; a third receiving unit, configured to receive a second message sent by the first node; wherein the second message includes a path information entry; the path information The entry includes at least one path information, where the path information includes: the first node identity information, the first FlexE client information, the first physical interface identifier information, the second FlexE client information, and the second physical interface identifier information;
  • the first FlexE client information includes: first slot information carrying the first FlexE client, first FlexE group information carrying the first FlexE client; the first physical interface identifier information includes carrying the Physical interface identification information of the first FlexE client; the second FlexE client information includes: second time slot information carrying the second FlexE client, and carrying the second FlexE client Two FlexE group information; the second physical interface identification
  • the first message and the second message are all carried by at least one FlexE overhead frame.
  • the embodiment of the present application provides a first node, where the first node is applied to a flexible Ethernet FlexE networking network, where the first node includes: a processor, a memory, and a transceiver.
  • said processor, said memory and said transceiver are interconnected, said memory being for storing a computer program, said computer program comprising program instructions, said processor being configured to invoke said program instructions, Performing the steps of: receiving a first message sent by the second node to query the first FlexE client transmission path; sending a second message to the second node; wherein the second message includes a path information entry; the path The information entry includes at least one path information, where the path information includes: the first node identity information, the first FlexE client information, the first physical interface identifier information, the second FlexE client information, and the second physical interface identifier information;
  • the first FlexE client information includes: first slot information carrying the first FlexE client, and carrying the first FlexE client.
  • the first physical interface identifier information includes physical interface identifier information that carries the first FlexE client;
  • the second FlexE client information includes: a second time slot information that carries the second FlexE client, and a bearer
  • the second physical interface identifier information includes physical interface identifier information that carries the second FlexE client; the first time slot carrying the first FlexE client and the bearer
  • the second time slot of the second FlexE client has a cross relationship.
  • the processor is further configured to: query the time slot exchange mapping table according to the first message. And if the query results of the time slot exchange mapping table are queried, generating the third message according to the first message, and sending the third message to the third node; if the time slot exchange mapping table is queried If there is a query result, a second message is generated according to the first message.
  • the first FlexE client includes the identifier information
  • the processor, according to the first message, querying the time slot exchange mapping table includes: determining, according to the identifier information included by the first FlexE client, the bearer. First slot information of the first FlexE client; determining, according to the first slot information, first FlexE group information that carries the first FlexE client; according to the first slot information and the first FlexE The group information queries the time slot exchange mapping table.
  • the processor according to the first message, querying the time slot exchange mapping table, includes: querying the time slot exchange mapping table according to the first FlexE client information recorded by the first message.
  • the query result includes second time slot information carrying a second FlexE client, second FlexE group information carrying the second FlexE client, and the processor according to the first message.
  • Generating the third message, and sending the third message to the third node including: generating the third message according to the first message, on a physical interface that carries the second FlexE client, to a third The node sends the third message.
  • the third message includes a path information entry, where the path entry information includes a path information entry in the first message and path information of the first node;
  • the path information of the first node includes the first FlexE client information, identifier information of a physical interface that carries the first FlexE client, the second FlexE client information, and a physical interface that carries the second FlexE client. Identification information.
  • the processor is further configured to: if not received within a specified duration Generating the second message according to the first message to the fourth message sent by the third node, where the fourth message includes a path information entry; the path information entry includes at least the Path information of the third node.
  • the second message includes a path information entry, where the path information entry includes a path information entry in the first message and path information of the first node;
  • the path information of the first node includes the first FlexE client information, identifier information of a physical interface that carries the first FlexE client, the second FlexE client information, and a physical interface that carries the second FlexE client. Identification information.
  • the generating, by the processor, the second message according to the first message includes: generating, according to the path information entry in the first message, the second message;
  • the second message includes a path information entry;
  • the path information entry includes a path information entry in the first message.
  • the processor is further used to send the second message to the second node.
  • the second message includes a path information entry, where the path information entry includes a path information entry in the fourth message.
  • the second message includes a path information entry, where the path information entry includes a path information entry in the fourth message and path information of the first node;
  • the path information of the first node includes the first FlexE client information, identifier information of a physical interface that carries the first FlexE client, the second FlexE client information, and a physical interface that carries the second FlexE client. Identification information.
  • the first message, the second message, the third message, and the fourth message are all carried by at least one FlexE overhead frame.
  • the embodiment of the present application provides a second node, where the second node is applied to a flexible Ethernet FlexE networking network, where the second node includes: a processor, a memory, and a transceiver, where: The processor, the memory and the transceiver are interconnected, the memory for storing a computer program, the computer program comprising program instructions, the processor being configured to invoke the program instructions, performing the following steps: Sending, to the first node, a first message requesting to query the first FlexE client transmission path; receiving a second message sent by the first node; wherein the second message includes a path information entry; the path information entry includes At least one path information, the path information includes: the first node identity information, the first FlexE client information, the first physical interface identifier information, the second FlexE client information, and the second physical interface identifier information; The first FlexE client information includes: first time slot information carrying the first FlexE client, and a first FlexE group message carrying the first FlexE client The first physical interface identifier information
  • the first message and the second message are all carried by at least one FlexE overhead frame.
  • the embodiment of the present application provides a communication system, including a first node and a second node; the first node is a third aspect, or the foregoing description of any one of the optional implementations of the third aspect A node, the second node being the fourth aspect, or the second node described in any one of the alternative implementations of the fourth aspect.
  • an embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores a computer program, where the computer program includes program instructions, when the program instructions are processed by a processor of the first device When executed, the processor of the first device is caused to perform the method described in the above first aspect or any one of the optional implementations of the first aspect; or the program instruction, when executed by the processor of the second device, The processor of the second device is caused to perform the method described in the second aspect or any one of the alternative implementations of the second aspect.
  • the first FlexE client information and the second FlexE client information of the FlexE client on the path node can be recorded as the transmission path of each hop, and the transmission path and ratio of the FlexE network segment to the segment can be dynamically discovered in real time.
  • the planned deployment path and the actually discovered path are used to evaluate the operation of the network. It is also possible to detect connection connectivity on the transmission path and locate faulty nodes on the transmission path within the FlexE network.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • Figure 1 is a schematic diagram of the general structure of the FlexE
  • Figure 2 is a schematic diagram of the FlexE calendar
  • Figure 3 is a schematic diagram of the definition of the FlexE overhead frame format
  • FIG. 4 is a schematic diagram of a format of a data field according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a format of a Traced Route field according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a PE node according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a P node according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flowchart of a method for obtaining a target transmission path according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart diagram of another method for obtaining a target transmission path according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic flowchart diagram of another method for obtaining a target transmission path according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic flowchart diagram of another method for obtaining a target transmission path according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram of a specific scenario provided by an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a specific Traced Route field according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of another specific scenario provided by an embodiment of the present application.
  • FIG. 16 is a schematic diagram of another specific Traced Route field according to an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a first node according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram of another first node according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic structural diagram of a second node according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic structural diagram of another first node according to an embodiment of the present disclosure.
  • FIG. 21 is a schematic structural diagram of another second node according to an embodiment of the present disclosure.
  • FlexE's rate aggregation supports high-speed Ethernet traffic. Data flows are carried together using multiple physical interfaces at low rates. Sub-rate and channelization allow multiple low-rate data streams to be carried concurrently within an Ethernet physical interface.
  • FlexE divides time slots by TDM to implement time division-based hard partitioning of transmission pipeline bandwidth, realizing hard allocation of link bandwidth in several service times, and one service data stream can be allocated to one or more time slots, realizing Matching of various rate services.
  • a FlexE Group can contain one or more physical link interfaces (PHYs).
  • the time slot allocation table corresponding to the FlexE Group is called FlexE-calendar, and the time slot mapping table corresponding to each physical link is called a sub-slot allocation table sub-calendar.
  • Each sub-calendar indicates how 20 time slots are allocated to the corresponding FlexE client.
  • the FlexE client represents a client data stream that is transmitted over a specified time slot (1 to more time slots) on the FlexE Group.
  • a FlexE Group can host multiple FlexE Clients, as shown in Figure 1.
  • One FlexE Client can correspond to one or more user service data flows (MAC Client), and the FlexE Shim layer provides data adaptation and conversion from FlexE Client to MAC Client.
  • MAC Client user service data flows
  • Figure 2 shows the slot allocation of a FlexE Group across n physical interfaces (aggregating n PHYs), each with 20 sub-slots (Slot 0-Slot 19), so the FlexE Group has 20n sub- Sub-calendar.
  • a FlexE Group sends a FlexE overhead 66b block to the remote PHY every 13.1 ⁇ s on each PHY, and 8 successively transmitted FlexE overheads.
  • the 66b block constitutes a FlexE overhead frame.
  • FlexE defines some fields on the overhead frame to carry the slot allocation table, and synchronizes the slot table to the remote PHY through the FlexE overhead frame to ensure that the dual-end receives and transmits the FlexE client data stream using the same time slot allocation table.
  • the format of the eight 66b blocks of the FlexE Group overhead frame is shown in Figure 3. Among them, Block#1-3 is used to record various data, which is not described in detail here, and Block#4-8 is a reserved management channel, and no information is recorded.
  • the first message, the second message, the third message, and the fourth message, which are involved in the embodiment of the present application may be carried by the FlexE overhead frame.
  • the first message and the third message involved in the embodiment of the present application may be a path detection request message.
  • the second message and the fourth message involved in the embodiment of the present application may be a path detection response message.
  • a continuous FlexE overhead frame carries the above message.
  • the packet format of the path detection message provided by the embodiment of the present application is introduced.
  • the path probe message includes a path probe request message and a path probe response message. That is, the first message, the second message, the third message, the fourth message, and the like involved in the subsequent embodiments of the present application.
  • the embodiment of the present application may use, but is not limited to, use the data field to record the FlexE Client requested by the PE node and the path information along the line.
  • the specific format of the data field is as shown in FIG. 4 .
  • a Sequence Number field is used to identify the number of the path probe message. It is used to distinguish different path detection messages on the entire transmission path when the user inputs multiple instructions for querying a path detection message of a FlexE client on the PE node.
  • the message type represents a type of the path probe message, and may be a path probe request message or a path probe response message.
  • the value of the Op Code field is 1, it indicates that the message is a path probe request message, and when the value of the Op Code field is 0, it indicates that the message is a path probe response message.
  • the value of the Op Code field is 1, it indicates that the message is a path probe request message, and when the value of the Op Code field is 0, it indicates that the message is a path probe response message.
  • the value of the Op Code field is 1, it indicates that the message is a path probe request message, and when the value of the Op Code field is 0, it indicates that the message is a path probe response message.
  • the opposite is also possible.
  • the source FlexE client represents the FlexE Client requested by the PE node, and can be represented by an available number or a time slot allocation table used by the FlexE Client.
  • the Hop Count indicates the hop count of the path that the current message is going through.
  • the path probe request message increments the Hop Count every time a node passes; the path probe response message decrements the Hop Count every time a node passes.
  • the path information table item (Traced Route) records the path information detected by the path detection request message, which is referred to in the embodiment of the present application, and can be further divided into multiple entries, and each entry corresponds to one path. Jump the node. As shown in FIG. 5, each entry should include the identity information node ID of the current node, the ingress FlexE client information Ingress Client, and the egress FlexE client information Egress Client. It can be known that the ingress FlexE customer information can include first FlexE customer information and identification information of a physical interface carrying the first FlexE customer; the export FlexE customer information can include information of the second FlexE customer and a physical interface carrying the second FlexE client. Identification information. The existence of the Traced Route is not limited to a path information entry. In fact, it can exist in other forms. It can record the path information of each node detected by the path probe request message.
  • the Ingress Client includes a first time slot information that carries the first FlexE client, FlexE Client #c1, a first FlexE group information that carries the first FlexE client, FlexE Group#g1, and a physical interface identifier information that carries the first FlexE client. P1;
  • the Egress Client includes: second time slot information carrying the second FlexE client, FlexE Group#c2, second FlexE group information carrying the second FlexE client, FlexE Group#g2, physical interface identification information carrying the second FlexE client, PHY #p2.
  • the first FlexE client is the FlexE client requesting the query in the first message.
  • the second FlexE customer is the FlexE customer after the first FlexE customer crosses the time slot within the node.
  • the third message is that after the node passes, the new path probe request message generated based on the first message includes at least an increase of the hop value, and may further include an increase of the path information of the node in the path information entry.
  • the first node and the second node involved in the embodiment of the present application may be a network device (Provider Edge, PE) node connected to the user at the edge of the network, and the device is equipped with an interface between the network or devices in the network (Network to Network Interface The NNI and the User Network Interface (UNI); the first node and the second node involved in the embodiment of the present application may also be a network device (Provider, P) node in the network, and the device is only equipped with an NNI.
  • the NNI may be, for example, a FlexE interface
  • the UNI may be, for example, a standard Ethernet interface.
  • the embodiments of the present application are applicable to a multi-node network using a FlexE interface.
  • FIG. 6 is a schematic structural diagram of a communication system according to an embodiment of the present disclosure
  • FIG. 7 is a schematic structural diagram of a PE node according to an embodiment of the present disclosure
  • Schematic is a schematic structural diagram of a communication system according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a communication system according to an embodiment of the present disclosure.
  • the communication system may include at least one PE node and a plurality of P nodes, and the PE node may send a path detection to the P node through the FlexE interface.
  • the overhead frame of the request message after receiving the overhead frame of the path detection request message sent by the PE node, the P node sends the overhead frame of the repackaged path detection request message with the added path information to the next P node.
  • the P node may also send an overhead frame carrying a path probe response message to the next P node or the PE node.
  • the PE node may extract the field of the path information in the overhead frame to implement the path discovery function.
  • the PE node and the P node include, but are not limited to, an IP-based transport network supporting a FlexE interface, a Packet Transport Network (PTN) box or a box switch device, and the like.
  • a functional unit capable of path discovery can be added to the NNI side interface chip of the switch device (PE node, P node), that is, a logical processing unit (traceroute) for implementing path discovery is implemented under the FlexE interface architecture (ie, the NNI side) to implement FlexE. Encapsulation and extraction of overhead frames to implement path discovery. See Figures 7 and 8.
  • the PE node 10 can include at least a UNI side interface chip 110, a switching network chip 120, and an NNI side interface chip 130.
  • the NNI side interface chip 130 further includes a logical processing unit (traceroute) 131 and a FlexE pad. Slice (FlexE Shim) 132, PHY133.
  • the UNI side interface chip 110 is configured to receive various instructions input by the user, such as an instruction to query the FlexE client transmission path.
  • the switch fabric chip 120 is used to connect the UNI side interface chip 110 and the NNI side interface chip 130 for implementing time slot exchange of the FlexE client.
  • a logic processing unit (traceroute) 131 is used to encapsulate and extract FlexE overhead frames
  • a FlexE Shim 132 is used to convert standard Ethernet data streams into FlexE time slot data streams
  • a PHY 133 is used for the next node PHY. Send a FlexE overhead frame.
  • the P node 20 can include at least two NNI side interface chips 210 and a switching network chip 220.
  • Each of the NNI side interface chips 210 further includes a PHY 211, a FlexE Shim 212, and a traceroute 213.
  • the PHY 211 is used to receive or transmit FlexE overhead frames
  • the FlexE Shim 212 is used to convert the standard Ethernet data stream to the FlexE time slot data stream
  • the traceroute 213 is used to encapsulate and extract FlexE overhead frames.
  • FIG. 9 is a schematic flowchart of a method for obtaining a target transmission path according to an embodiment of the present disclosure, where the method includes but is not limited to the following steps:
  • S301 The request sent by the second node to the first node queries the first message of the first FlexE client transmission path.
  • the second node may be a PE node, and the first node is a P node.
  • the user can enter an instruction requesting to query the first FlexE client transmission path on the second node.
  • the second node may generate the first message according to the above instruction. And encapsulating the first message in the at least one FlexE overhead frame.
  • the first message may be a path probe request message.
  • the first time slot for transmitting the first FlexE client, the first FlexE group carrying the first time slot, and the physical interface included in the first FlexE group may be queried according to the foregoing instruction. And assigning, according to the time slot occupied by the first FlexE client, at least one physical interface that transmits the first FlexE client from a physical interface included in the first FlexE group.
  • the first FlexE client may occupy multiple time slots
  • the second node may select one physical interface from the physical interfaces included in the first FlexE group, or the second node may be from the physical interface included in the first FlexE group.
  • Multiple physical interfaces are selected to carry one or more of the above time slots respectively.
  • the first FlexE client may be assigned a physical interface, where the physical interface includes the two time slots; or the first FlexE client may be assigned two physical interfaces.
  • the above two physical interfaces respectively comprise one of the two time slots.
  • the label of the path probe message In the data field of the first message, the label of the path probe message, the message type (path probe request message), the number of the first FlexE client (or the time slot assignment table used by the FlexE Client), and the hop value may be recorded. And path information table entries. It can be known that since the second node is a PE node, the hop value is the initial value Z 0 , and Z 0 can be, for example but not limited to, 0, and no path information is recorded in the information table item.
  • the second node may be a P node, and the first node is a P node.
  • the first message sent by the second node to the first node is a path probe request message.
  • the label of the path probe message, the message type (path probe request message), the number of the first FlexE client (or the time slot assignment table used by the FlexE Client), and the hop value may be recorded. And path information table entries.
  • the second node may be a P node
  • the first node may be a PE node.
  • the transmission path is terminated.
  • the label of the path probe message, the message type (path probe request message), the number of the first FlexE client (or the time slot assignment table used by the FlexE Client), and the hop value may be recorded. And path information table entries.
  • S302 The first node sends a second message to the second node.
  • the second message includes a path information entry, where the path information entry includes at least one piece of path information, where the path information includes: the first node identity information, the first FlexE client information, the first physical interface identifier information,
  • the first FlexE client information and the second FlexE client information include: first time slot information carrying the first FlexE client, and first FlexE group information carrying the first FlexE client;
  • the second FlexE client information includes: second time slot information carrying the second FlexE client, and second FlexE group information carrying the second FlexE client;
  • the second physical interface identifier information includes a physical interface identifier that carries the second FlexE client.
  • the first time slot carrying the first FlexE client has a cross relationship with the second time slot carrying the second FlexE client, that is, the first time slot of the first FlexE client passes through the time slot in the first node. Can be crossed to the second time slot of the second FlexE client described above.
  • the physical interface identifier information of the second time slot carrying the second FlexE client may be all the physical interface identifier information of the second time slot carrying the second FlexE client, or may be the second FlexE client.
  • Identification information of one of the plurality of physical interfaces of the second time slot the first node may send a third message to the third node on the physical interface, where the third message may correspond to the first message, After the message is updated, a third message is obtained, and the third message may be a path probe request message.
  • the update of the first message may be: only increasing the hop value in the first message, or increasing the hop value in the first message to generate the third message; or the path information table in the first message.
  • the path information of the first node is added on the basis of the item, and then the third message is generated.
  • the physical interface identifier information of the second time slot carrying the second FlexE client mentioned in the following embodiments may be all physical interface identifier information that carries the second time slot of the second FlexE client. It may be identification information of one of a plurality of physical interfaces carrying the second time slot of the second FlexE client. This will not be repeated in the subsequent embodiments.
  • the second message may be a path probe response message. That is, after the path is terminated, the path detection response message returned from the downstream node.
  • the path detection response message may record path information of each node on the entire transmission path, or may record path information of all nodes downstream of the second node. It can be understood that the first node is a downstream node of the second node. Conversely, the second node is the upstream node of the first node.
  • the entry information and the egress information of the FlexE client on the path node can be recorded as the transmission path of each hop, and the transmission path of the FlexE network segment to the segment can be dynamically discovered in real time, and the transmission path of the planned deployment is compared. With the actual discovered path to assess the operation of the network, it is also possible to detect connectivity connectivity on the transmission path and locate faulty nodes on the transmission path within the FlexE network.
  • FIG. 10 is a schematic flowchart diagram of another method for obtaining a target transmission path according to an embodiment of the present disclosure, where the method includes but is not limited to the following steps:
  • S401 The second node receives an instruction input by the user to query the first FlexE client transmission path.
  • the second node is a PE node.
  • the user can input the above instruction for querying the first FlexE client transmission path through the UNI side interface of the first node.
  • the second node queries the first time slot information for transmitting the first FlexE client according to the foregoing instruction, and carries the first FlexE group information of the first FlexE client, and the physical interface included in the first FlexE group.
  • the first time slot of the first FlexE client is transmitted, the first FlexE group carrying the first FlexE client, and the physical interface included in the first FlexE group are parameters configured by the user in advance for the node.
  • the first FlexE group contains at least one physical interface.
  • the first FlexE client can include identification information.
  • the first node may determine, according to the identification information included by the first FlexE client, the first time slot information for transmitting the first FlexE client, and then determine the first FlexE group information that carries the first FlexE client.
  • the first FlexE client identification information has a mapping relationship with the first time slot information that carries the first FlexE client.
  • the mapping relationship is also a parameter preset by the user.
  • the first time slot information carrying the first FlexE client may be determined according to the foregoing mapping relationship.
  • the identification information of the FlexE client can also be determined according to the time slot information of the FlexE client.
  • the second node allocates, according to the time slot occupied by the first FlexE client, at least one physical interface that carries the first FlexE client from the physical interface included in the first FlexE group.
  • the first FlexE client may occupy multiple time slots
  • the second node may allocate one physical interface from the physical interfaces included in the first FlexE group, or the second node may be from the physical interface included in the first FlexE group. Multiple physical interfaces are allocated, one or more of the above slots are respectively carried.
  • the first FlexE client may be assigned a physical interface, where the physical interface includes the two time slots; or the first FlexE client may be assigned two physical interfaces. The above two physical interfaces respectively comprise one of the two time slots.
  • S404 The second node sends a first message requesting to query the first FlexE client transmission path to the first node, where the first node receives the first message sent by the second node.
  • the second node generates a first message on each of the allocated at least one physical interfaces.
  • the label of the path probe message In the data field of the first message, the label of the path probe message, the message type (path probe request message), the number of the first FlexE client (or the time slot assignment table used by the FlexE Client), and the hop value may be recorded. And path information table entries. It can be known that since the second node is a PE node, the hop value is the initial value Z 0 , and Z 0 can be, for example but not limited to, 0, and no path information is recorded in the information table item.
  • the second node can be sent to the same first node together, and the first node can generate a first message for each first message.
  • Three messages After the second node generates a first message on the at least one physical interface that is allocated, the second node may also be sent to different first nodes. Each first node generates a third message for each of the first messages it receives.
  • the timer is started after the second node sends the first message to the first node. If the timer does not receive the second message (path probe response message) returned by the first node after the timer expires, the path discovery fails, no path information is found, and the hop value of the current record and the Source Client field are cleared.
  • the timing of the timer may be, for example but not limited to, 50n*13.1 ⁇ s, where n represents the average hop count in the FlexE network.
  • S405 The first node queries the time slot exchange mapping table according to the first FlexE client information, and determines whether the query result exists. If there is a query result, S406 is performed; if there is no query result, S411 is executed.
  • the first FlexE client information includes first slot information carrying the first FlexE client and first FlexE group information carrying the first FlexE client.
  • the foregoing first FlexE client information may be obtained by extracting a Source Client field of the first message.
  • the first node may save the first FlexE client information to the local, and the first node may extract the locally saved first FlexE client information.
  • the first node may extract the second FlexE customer information recorded in the last item of the path information representation in the first message, and use the second FlexE client information as the query condition. , query the time slot exchange mapping table.
  • the second FlexE client information is time slot information of the FlexE client carried by the second node when the first message is sent to the first node, and the FlexE group information that carries the FlexE client.
  • the determining whether the second node is a PE node or a P node may determine whether the hop value in the first message is greater than an initial value Z 0 . If it is greater than Z 0 , the second node is a P node, and if Z 0 , the second node is a PE node.
  • S406 The first node generates a third message according to the first message.
  • the third message is generated according to the first message.
  • the first message is a path probe request message
  • the third message is also a path probe request message.
  • the query result includes second time slot information carrying the second FlexE client and second FlexE group information carrying the second FlexE client.
  • the first FlexE client exchanges time slots in the first node and is switched into a second FlexE client.
  • the FlexE client sent by the receiving upstream node is the first FlexE client
  • the FlexE client sent to the downstream node is the second FlexE client.
  • the first FlexE client of the current node is the second FlexE client of the upstream node
  • the second FlexE client of the current node is the first FlexE client of the downstream node.
  • the path information of the current node is added to the path information entry.
  • the third message includes a path information entry; the path entry information in the third message includes a path information entry in the first message and path information of the first node; where the path information of the first node includes the foregoing
  • the path information of the first node is used as the last item of the path information entry in the third message.
  • the third message may also include a hop value.
  • the hop value in the third message is incremented by one compared to the hop value in the first message. If the hop value recorded in the first message is Z 0 , then the hop value recorded in the third message is Z 0 +1.
  • the path information of the current node is not added to the path information entry, but when the path probe response message is returned to the upstream node. Add the path information of the current node to the path information table entry.
  • the third message includes a path information entry; the path information entry in the third message includes a path information entry in the first message. That is, the path information table entry in the first message does not record any path information, and the path information entry in the third message does not record any path information.
  • the hop value in the third message is incremented by one compared to the hop value in the first message. If the hop value recorded in the first message is Z 0 , then the hop value recorded in the third message is Z 0 +1.
  • S407 The first node sends the third message to the third node.
  • the first node sends a third message to the third node on the at least one physical interface included in the second FlexE group that carries the second time slot.
  • the specific physical interface used to send the third message may be pre-configured, and the physical interface may be determined according to the second time slot.
  • all the physical interfaces included in the second FlexE group may be used to send a third message on each physical interface, but only one physical interface is finally used.
  • a path probe response message returned by the downstream node is received. It can be known that the identification information of the physical interface for transmitting the third message recorded in each third message is different.
  • the timer is started. If the timer does not receive the fourth message (path probe response message) returned by the third node after the timer expires, the path is terminated at the third node. Then generating a second message according to the first message.
  • the timing of the timer may be, for example but not limited to, 50n*13.1 ⁇ s, where n represents the average hop count in the FlexE network.
  • the fourth message includes a path information entry; the path information entry included in the fourth message includes at least path information of the third node.
  • the content of the path information of the third node may be referred to the content included in the path information of the first node, and details are not described herein again.
  • the second message includes a path information entry; the path entry information in the second message includes a path information entry in the first message and path information of the first node; where the path information of the first node includes Information of a FlexE client, identification information of a physical interface carrying the first FlexE client, information of the second FlexE client, and physical interface identification information carrying the second FlexE client.
  • the path information of the first node is used as the last item of the path information entry in the second message.
  • the path information entry included in the second message includes the path information entry in the third message.
  • the hop value may also be included in the second message.
  • the hop value in the second message is incremented by one compared to the hop value in the first message. If the hop value recorded in the first message is Z 0 , then the hop value recorded in the third message is Z 0 +1.
  • the Op Code field in the second message changes. It can be known that the first message is a path probe request message, and the second message is a path probe response message.
  • S409 The third node sends a fourth message to the first node, where the first node receives the fourth message sent by the third node.
  • the first node receives the fourth message sent by the third node within a specified duration.
  • the fourth message includes a path information entry; the path information entry includes at least the path information of the third node.
  • the path information of the current node is added to the path information entry.
  • the fourth message includes a path information entry; the path entry information in the fourth message includes path information of all nodes on the transmission path.
  • the path information of the current node is not added to the path information entry, but when the path probe response message is returned to the upstream node.
  • the fourth message includes a path information entry; the path entry information in the fourth message includes path information of all downstream nodes of the first node on the transmission path, that is, all downstream nodes of the third node and the third node. Path information.
  • the third node may send a fourth message to the first node on the physical interface that receives the third message.
  • S410 The first node generates a second message according to the fourth message.
  • the path information of the current node is added to the path information entry.
  • the path entry information in the fourth message includes the path information of all the nodes on the transmission path, and only the path information entry in the fourth message is copied to the path information entry of the second message.
  • the hop value in the fourth message is then decremented by one as the hop value in the second message.
  • the path information of the current node is not added to the path information entry, but when the path probe response message is returned to the upstream node. Add the path information of the current node to the path information table entry. Then, the path entry information in the fourth message includes the path information of all the downstream nodes of the first node on the transmission path, and the path information of the first node is added to the path information entry in the fourth message to The path information entry in the second message. The hop value in the fourth message is then decremented by one as the hop value in the second message.
  • the path information of the first node is obtained in at least two ways:
  • the first type querying the time slot exchange mapping table according to the second FlexE client information recorded in the last item in the path information entry in the received fourth message, and obtaining the query result.
  • the second FlexE client information is the first FlexE client information of the current first node
  • the query result is the second FlexE client information of the current first node.
  • the path information of the first node includes information of the first FlexE client, identifier information of a physical interface that carries the first FlexE client, information of the second FlexE client, and physical interface identifier information that carries the second FlexE client.
  • the path information of the first node is used as the last item of the path information entry in the second message.
  • the path information of the first node includes information of the first FlexE client, identifier information of a physical interface that carries the first FlexE client, information of the second FlexE client, and physical interface identifier information that carries the second FlexE client.
  • S411 The first node generates a second message according to the first message.
  • the second message is generated according to the first message.
  • the first message is a path probe request message
  • the second message is a path probe response message.
  • the query result does not exist, indicating that the transmission path is terminated at the node, and the path discovery ends. Since the second node is a PE node, the query time slot exchange mapping table in the first node does not have a query result, indicating the second message.
  • the path information entry in the space is empty.
  • the second node when the second node is a P node, at least the path information of the second node may be included in the path information entry in the first message.
  • the path information entry in the first message may be directly copied to the path information entry in the second message, and the hop value is unchanged.
  • S412 The first node sends a second message to the second node.
  • the first node is second to the second message.
  • the node sends a second message.
  • the second node may extract the path information entry in the second message to obtain a transmission path.
  • the first node may send the second message to the second node on the physical interface that receives the first message.
  • the second node after receiving the request of the user input to query the first FlexE client transmission path, the second node separately performs on the multiple physical interfaces allocated according to the time slot occupied by the first FlexE client. After generating a first message, at this time, all the messages returned according to the first message are received at S412, so that a complete transmission path can be obtained. Specifically, it can be implemented by setting a timer at the second node as described above. Specifically, the sequence number in each second message may be used to distinguish whether each second message belongs to the same instruction requesting to query the first FlexE client transmission path.
  • the path information of the first node is added when the third message is sent to the downstream node, or the path information of the first node is added when the second message is returned to the upstream node, and the user can set the second information.
  • the extraction order when the transmission path information is extracted on the node, and finally the correct transmission path is obtained.
  • the path information of the first node is added, and finally the path information entry in the second message is directly extracted.
  • the path information of the first node is added, and if the node information recorded when the locally saved third message is sent is directly added, the path information entry in the second message is finally extracted in reverse order.
  • the path information of the first node is added, and if the time slot exchange mapping table is queried according to the query condition saved locally by the first node, the path information of the first node is added to the second message.
  • the path information table entry finally extracts the path information entry in the second message in reverse order.
  • the path information of the first node is added, and if the query result is obtained by querying the time slot exchange mapping table according to the first FlexE client information at the time of return, the path information of the first node is finally followed.
  • the flashback extracts the path information entry in the second message, and then reverses the first FlexE client information with the second FlexE client information.
  • the first FlexE client information and the second FlexE client information of the FlexE client on the path node can be recorded as the transmission path of each hop, and the transmission path and ratio of the FlexE network segment to the segment can be dynamically discovered in real time.
  • the planned deployment path and the actually discovered path are used to evaluate the operation of the network. It is also possible to detect connection connectivity on the transmission path and locate faulty nodes on the transmission path within the FlexE network.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • FIG. 11 is a diagram of adding a path information of a current node to a path information entry when transmitting a path probe request message to a downstream node on a transmission path.
  • FIG. 12 shows that on the transmission path, when the path probe response message is returned to the upstream node, the path information of the current node is added to the path information entry.
  • the method for obtaining a target transmission path may include at least the following steps:
  • S501 The second node receives an instruction input by the user to query the first FlexE client transmission path.
  • S502 The second node queries, according to the foregoing instruction, the first time slot information of the first FlexE client, the first FlexE group information of the first FlexE client, and the physical interface included in the first FlexE group.
  • the second node allocates, according to the time slot occupied by the first FlexE client, at least one physical interface that carries the first FlexE client from the physical interface included in the first FlexE group.
  • S504 The second node sends a first message requesting to query the first FlexE client transmission path to the first node, where the first node receives the first message sent by the second node.
  • S505 The first node queries the time slot exchange mapping table according to the first FlexE client information, and determines whether the query result exists. If there is a query result, execute S506; if there is no query result, execute S511.
  • S506 Add the path information of the first node to the path information entry in the first message to generate a third message.
  • the query result includes second time slot information carrying the second FlexE client, and second FlexE group information carrying the second FlexE client.
  • the third message includes a path information entry; the path entry information in the third message includes the path information entry in the first message and the path information of the first node; wherein the path information of the first node includes the first FlexE
  • the path information of the first node is used as the last item of the path information entry in the third message.
  • the third message may also include a hop value.
  • the hop value in the third message is incremented by one compared to the hop value in the first message. If the hop value recorded in the first message is Z 0 , then the hop value recorded in the third message is Z 0 +1.
  • S507 The first node sends the third message to the third node.
  • S508 The first node does not receive the fourth message sent by the third node within the specified duration, and generates a second message according to the foregoing first message.
  • S507 to S508 refer to S407 to S408 in FIG. 10, and details are not described herein.
  • S509 The third node sends a fourth message to the first node, where the first node receives the fourth message sent by the third node.
  • the first node receives the fourth message sent by the third node within a specified duration.
  • the fourth message includes a path information entry; the path entry information in the fourth message includes path information of all nodes on the transmission path.
  • the path information entry in the fourth message is used as the path information entry in the second message to generate a second message.
  • the path entry information in the fourth message includes path information of all nodes on the transmission path, and only the path information entry in the fourth message is copied to the path information entry of the second message.
  • the hop value in the fourth message is then decremented by one as the hop value in the second message.
  • S511 The first node generates a second message according to the first message.
  • S512 The first node sends a second message to the second node.
  • S511 to S512 refer to S411 to S412 in FIG. 10, and details are not described herein.
  • the path information of the current node is added to the path information entry.
  • the transmission path of the FlexE network segment to the segment can be dynamically discovered in real time, the planned transmission path and the actually discovered path can be compared to evaluate the operation of the network, and the connection connectivity on the transmission path can be detected and the transmission path in the FlexE network can be located. Faulty node.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • the method for obtaining a target transmission path may include at least the following steps:
  • S601 The second node receives an instruction input by the user to query the first FlexE client transmission path.
  • the second node queries the first time slot information for transmitting the first FlexE client according to the foregoing instruction, and carries the first FlexE group information of the first FlexE client, and the physical interface included in the first FlexE group.
  • the second node allocates at least one physical interface that carries the first FlexE client from the physical interfaces included in the first FlexE group according to the time slot occupied by the first FlexE client.
  • S604 The second node sends a first message requesting to query the first FlexE client transmission path to the first node, where the first node receives the first message sent by the second node.
  • S605 The first node queries the time slot exchange mapping table according to the first FlexE client information, and determines whether the query result exists. If there is a query result, S606 is performed; if there is no query result, S611 is performed.
  • S601 to S605 For the implementation of S601 to S605, refer to S401 to S405 in FIG. 10, and details are not described herein.
  • the path information entry in the first message is used as the path information entry in the third message to generate a third message.
  • the query result includes second time slot information carrying the second FlexE client, and second FlexE group information carrying the second FlexE client.
  • the third message includes a path information entry; the path information entry in the third message includes a path information entry in the first message. That is, the path information table entry in the first message does not record any path information, and the path information entry in the third message does not record any path information.
  • the hop value in the third message is incremented by one compared to the hop value in the first message. If the hop value recorded in the first message is Z 0 , then the hop value recorded in the third message is Z 0 +1.
  • S607 The first node sends the foregoing third message to the third node.
  • S607 to S608 refer to S407 to S408 in FIG. 10, and details are not described herein.
  • S609 The third node sends a fourth message to the first node, where the first node receives the fourth message sent by the third node.
  • the first node receives the fourth message sent by the third node within a specified duration.
  • the fourth message includes a path information entry.
  • the path entry information in the fourth message includes path information of all downstream nodes of the first node on the transmission path, that is, path information of all downstream nodes of the third node and the third node.
  • S610 Add path information of the first node to the path information entry in the fourth node to generate a second message.
  • the path entry information in the fourth message includes the path information of all the downstream nodes of the first node on the transmission path, and the path information of the first node is added to the path information entry in the fourth message to The path information entry in the second message.
  • the hop value in the fourth message is then decremented by one as the hop value in the second message.
  • S611 The first node generates a second message according to the first message.
  • S612 The first node sends a second message to the second node.
  • S611 to S612 For the implementation of S611 to S612, refer to S411 to S412 in FIG. 10, and details are not described herein.
  • the path information of the current node is added to the path information entry.
  • the transmission path of the FlexE network segment to the segment can be dynamically discovered in real time, the planned transmission path and the actually discovered path can be compared to evaluate the operation of the network, and the connection connectivity on the transmission path can be detected and the transmission path in the FlexE network can be located. Faulty node.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • the first type As shown in Figure 13, the network operation and maintenance personnel or users on the PE node FlexE node #1 (FlexE Node #1) request to query the transmission path of FlexE client #c1 (FlexE Client #c1) in the FlexE network,
  • the implementation process of this embodiment is as follows:
  • FlexE Node#1 receives the user's request and inputs FlexE Client#c1 (c1 represents the time slot allocation table, according to which the time slot allocation table can determine the time slot for transmitting the FlexE Client), query on FlexE Node#1
  • the FlexE Group (FlexE Group) carrying FlexE Client#c1 is FlexE Group#1 (FlexE Group#1)
  • the FlexE physical interface (PHY) included in FlexE Group#1 is PHY#6, which is the FlexE Client#c1.
  • the physical interface is PHY#6, and the FlexE overhead frame carrying the first message is sent on PHY#6; the hop count is 0, FlexE Group#1, FlexE Client#c1, and the timer is started.
  • STEP 2 The first message is delivered to the FlexE interface PHY#6 on the NNI side of the remote network device FlexE Node#2 (FlexE Node#2); the traceroute function unit parses the first message Op Code field, which is a path probe request message. Read the Traced Route field in the first message and find that it does not contain any path information entries; extract the source client field of the first message, and use the FlexE Group#1 and RTR to which the FlexE interface PHY#6 hosting FlexE Client#c1 belongs.
  • the FlexE client#c1 time slot allocation table of the source client field is used as the query condition (the query condition is also recorded), and the FlexE time slot exchange mapping table in the FlexE Node#2 node is queried, and the query obtains the cross-mapped exit as the FlexE group #3. (FlexE Group#3) and FlexE Client#c2 (FlexE Client#c2). Query the FlexE interface PHY list included in FlexE Group#3.
  • FlexE Group#3 only includes PHY#3, that is, the physical interface carrying FlexE Client#c2 is PHY#3, incrementing the hop count value in the first message, using Node#2 As Node ID; FlexE group #1+PHY#6+FlexE client#c1 (FlexE Group#1+PHY#6+FlexE Client#c1) as Ingress Client; FlexE group #3+PHY#3+FlexE client#c2( FlexE Group#3+PHY#3+FlexE Client#c2) is the Egress Client, attached to the Traced Route field as the last entry, generates a third message, and sends a FlexE overhead frame carrying the third message on PHY#3. . Record the hop count as 1, FlexE Group #3, FlexE Client #c2, and start the timer.
  • STEP 3 As shown in Figure 13, the third message sent cannot reach FlexE Node#3 due to a link failure of FlexE Node #2 (FlexE Node#2) to FlexE Node #3 (FlexE Node#3).
  • FlexE Node#2 receives the timeout event of the timer (the fourth message returned by FlexE Node#3 is not received after the timer expires), and uses the recorded hop count as 1 as the hop count value in the second message.
  • the path information in the three messages is characterized as a path information entry in the second message, and a FlexE overhead frame encapsulating the second message is sent for the physical interface PHY #6 carrying the FlexE Client #c1. Clear the current recorded hop count, FlexE Group#1, FlexE Client#c1, and stop the timer.
  • STEP 4 The second message is transmitted to the remote network device FlexE Node 1 on the NNI side of the FlexE interface PHY#1; the message Op Code field is read, the path detection response message is read, the Hop Count field of the second message is read, and it is found The Hop Count value is 0, ending the second message.
  • FlexE Group#1 carrying FlexE Client#c1 corresponds to only one physical port PHY#1, and the second message has been received from the port, and the path detection is terminated.
  • the transmission path of FlexE Client#c1 on Node 1 is shown in Figure 14.
  • the embodiment of the present application takes the scenario of adding the path information of the first node to the path information entry in the third message when the first node sends the third message to the downstream node as an example, and implements a path discovery process.
  • the transmission path of the FlexE network segment to the segment can be dynamically discovered in real time, and the transmission path and the actually discovered path of the planned deployment are compared.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • the second embodiment is as follows: As shown in Figure 13, the network operation and maintenance personnel or the user requests the FlexE Node #1 to query the transmission path of the FlexE Client #c1 in the FlexE network on the PE node.
  • the implementation process of this embodiment is as follows:
  • FlexE Node#1 receives the user's request and inputs FlexE Client#c1 (c1 represents the time slot allocation table, according to which the time slot allocation table can determine the time slot for transmitting the FlexE Client), query on FlexE Node#1
  • the FlexE Group hosting FlexE Client#c1 is FlexE Group#1
  • the FlexE physical interface (PHY) included in FlexE Group#1 is PHY#6, that is, the physical interface carrying FlexE Client#c1 is PHY#6, in PHY#
  • the FlexE overhead frame carrying the first message is sent on the 6th; the hop count is 0, FlexE Group#1, FlexE Client#c1, and the timer is started.
  • STEP 2 The first message is delivered to the FlexE interface PHY#6 on the NNI side of the remote network device FlexE Node#2; the traceroute function unit parses the first message Op Code field, which is a path probe request message; reads the first message In the Traced Route field, it is found that no path information entry is included; the source client field of the first message is extracted, and the source client field in the FlexE Group#1 and RTR messages belonging to the FlexE interface PHY#6 that carries FlexE Client#c1 is used.
  • the traceroute function unit parses the first message Op Code field, which is a path probe request message; reads the first message In the Traced Route field, it is found that no path information entry is included; the source client field of the first message is extracted, and the source client field in the FlexE Group#1 and RTR messages belonging to the FlexE interface PHY#6 that carries FlexE Client#c1 is used.
  • the FlexE client #c1 time slot allocation table is used as a query condition (simultaneously recording query conditions), and the FlexE time slot exchange mapping table in the FlexE Node #2 node is queried, and the exits of the cross-map are obtained as FlexE Group #3 and FlexE Client #c2.
  • FlexE Group#3 only includes PHY#3, that is, the physical interface carrying FlexE Client#c2 is PHY#3, incrementing the hop count value in the first message to generate a third message. And transmitting a FlexE overhead frame carrying the third message on PHY#3. Record the hop count as 1, FlexE Group #3, FlexE Client #c2, and start the timer.
  • STEP 3 As shown in Figure 13, due to the failure of the link of FlexE Node#2 to FlexE Node#3, the third message sent cannot reach the FlexE Node#3 node.
  • the FlexE Node#2 node receives the timer timeout event (the fourth message returned by FlexE Node#3 is not received after the timer expires), and the recorded hop count is 1 as the hop count value in the second message.
  • FlexE Group#1 and FlexE client#c1 query the FlexE slot exchange mapping table, and the query obtains the cross-mapped exits as FlexE Group#3 and FlexE Client#c2 (c2 stands for slot allocation table); queries the FlexE Group#1 PHY, that is, FlexE Group#1 only corresponds to PHY#6, that is, the physical interface carrying FlexE Client#c1 is PHY#6, then a second message is generated, using Node#2 as the Node ID; FlexE Group#1+PHY#6 +FlexE Client#c1 as the Ingress Client; FlexE Group#3+PHY#3+FlexE Client#c2 as the Egress Client, attached to the Traced Route field as the last entry, as the path information entry in the second message; The physical interface PHY#6 of the FlexE Client#c1 sends the FlexE overhead frame carrying the second message; clears the current recorded hop count, FlexE Group#1, FlexE Client#c1, and stops the RTR timer.
  • STEP 4 The second message is transmitted to the remote network device FlexE Node 1 on the NNI side of the FlexE interface PHY#1; the message Op Code field is read, the path detection response message is read, the Hop Count field of the second message is read, and it is found The Hop Count value is 0, ending the second message.
  • FlexE Group#1 carrying FlexE Client#c1 corresponds to only one physical port PHY#1, and the second message has been received from the port, and the path detection is terminated.
  • the transmission path of FlexE Client#c1 on Node 1 is shown in Figure 14.
  • the embodiment of the present application takes the scenario of adding the path information of the first node to the path information entry in the second message when the first node returns the second message to the upstream node as an example, and implements a path discovery process.
  • the transmission path of the FlexE network segment to the segment can be dynamically discovered in real time, and the transmission path and the actually discovered path of the planned deployment are compared.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • FlexE Node#1 receives the user's request and enters FlexE Client#c1.
  • FlexE Node#1 query the FlexE Group (FlexE Group) that carries FlexE Client#c1 to FlexE Group#1 (FlexE Group#1).
  • FlexE physical interface (PHY) included in FlexE Group#1 as PHY#1 and PHY#2, and transmit the FlexE overhead carrying the first message on the physical interfaces PHY#1 and PHY#2 carrying FlexE Client#c1.
  • Frame this message transmission needs to occupy several FlexE overhead transmission cycles
  • record hop count is 0, FlexE Group#1, FlexE Client#c1, and start 2 timers respectively.
  • STEP 2 The first message is delivered to the remote network device FlexE node #2 (FlexE Node #2) on the NNI side of the FlexE interface PHY #1; the traceroute function unit parses the first message Op Code field, which is a path probe request message; Read the traced route field in the first message, and find that no path information entry is included; extract the source client field of the first message, and use the FlexE Group#1 and the first of the FlexE interface PHY#1 that receives the first message.
  • FlexE node #2 Flexible Ethernet Node #2
  • the traceroute function unit parses the first message Op Code field, which is a path probe request message
  • Read the traced route field in the first message and find that no path information entry is included
  • extract the source client field of the first message and use the FlexE Group#1 and the first of the FlexE interface PHY#1 that receives the first message.
  • the FlexE client#c1 time slot allocation table of the source client field is used as the query condition (the query condition is also recorded), and the FlexE time slot exchange mapping table in the FlexE Node#2 node is queried, and the exit of the cross-map is obtained as the FlexE group #2.
  • the FlexE Group#2 FlexE Group#2
  • FlexE Client#c2 FlexE Client#c2
  • FlexE Group#2 only contains PHY#3, that is, the physical interface carrying FlexE Client#c2 is PHY#3, increment the hop count value in the first message, and generate the third message.
  • a FlexE overhead frame carrying the third message is sent on PHY #3. Record the hop count as 1, FlexE Group #2, FlexE Client #c2, and start the timer.
  • STEP 3 The first message is delivered to the FlexE interface PHY#2 on the NNI side of the remote network device FlexE node #3 (FlexE Node#3); the traceroute function unit parses the first message Op Code field, which is a path probe request message; Read the traced route field in the first message, and find that no path information entry is included; extract the source client field of the first message, and use the FlexE Group#1 and the first of the FlexE interface PHY#2 that receives the first message.
  • the traceroute function unit parses the first message Op Code field, which is a path probe request message
  • Read the traced route field in the first message, and find that no path information entry is included extract the source client field of the first message, and use the FlexE Group#1 and the first of the FlexE interface PHY#2 that receives the first message.
  • the FlexE client#c1 time slot allocation table of the source client field is used as the query condition (the query condition is also recorded), and the FlexE time slot exchange mapping table in the FlexE Node#2 node is queried, and the exit of the cross-map is obtained as FlexE Group#2. And FlexE Client#c2.
  • FlexE Group#2 only includes PHY#4, that is, the physical interface carrying FlexE Client#c2 is PHY#4, incrementing the hop count value in the first message to generate a third message.
  • a FlexE overhead frame carrying the third message is sent on PHY #4. Record the hop count as 1, FlexE Group #2, FlexE Client #c2, and start the timer.
  • FlexE Node #4 (FlexE Node#4) is a PE node and terminates the FlexE Client on FlexE Group#2. Therefore, constructing the fourth message, using the hop count (in this case, 1) in the third message as the hop count value in the fourth message, initializing the Traced Route table, but the entry is empty, generating a fourth message; for the FlexE Group #2 contains PHY#3 and PHY#4, that is, the physical interfaces carrying FlexE Client#c2 are PHY#3 and PHY#4, that is, the FlexE overhead carrying the fourth message is respectively sent on PHY#3 and PHY#4. frame.
  • the hop count in this case, 1
  • STEP 5 The FlexE Node#2 node receives the fourth message from FlexE Node#4 on PHY#3. Use FlexE Group#2 and FlexE client#c2 to query the FlexE slot exchange mapping table. The query obtains the cross-mapped exits as FlexE Group#1 and FlexE Client#c1.
  • the hop count value in the fourth message is decremented to generate a second message.
  • the FlexE overhead frame carrying the second message is sent on PHY#1; the currently recorded hop count, FlexE Group#2, FlexE Client#c2, and the RTR timer are stopped.
  • STEP 6 The FlexE Node #3 node receives the fourth message from FlexE Node #4 on PHY #4. Use FlexE Group#2 and FlexE client#c2 to query the FlexE slot exchange mapping table. The query obtains the cross-mapped exits as FlexE Group#1 and FlexE Client#c1.
  • the hop count value in the fourth message is decremented to generate a second message.
  • PHY#2 that carries FlexE Client#c1
  • the overhead frame encapsulating the RTRR message is sent on PHY#2; the current recorded hop count, FlexE Group#2, FlexE Client#c2, and the RTR timer are stopped.
  • STEP 7 The second message in STEP 5, STEP 6 is passed to the FlexE interface PHY#1 and PHY#2 on the NNI side of the remote network device FlexE Node#1; the message Op Code field is read as the path probe response message. The Hop Count field of the two second messages is read, and the Hop Count value is found to be 0, and the second message is terminated. FlexE Group#1 carrying FlexE Client#c1 only corresponds to 2 physical ports PHY#1 and PHY#2, and the second message has been received from both ports, and the path detection is terminated. The transmission path of FlexE Client#c1 on Node 1 is shown in Figure 16.
  • the embodiment of the present application takes a scenario in which a FlexE client is carried by multiple PHYs as an example to implement a path discovery process.
  • a FlexE client is carried by multiple PHYs as an example to implement a path discovery process.
  • the transmission path of the FlexE network segment to the segment can be dynamically discovered in real time, and the transmission path and the actually discovered path of the planned deployment are compared.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • FIG. 17 is a schematic structural diagram of a first node according to an embodiment of the present disclosure.
  • the first node 70 may include at least: a first receiving unit 710 and a first sending unit 720; wherein:
  • the first receiving unit 710 is configured to receive a first message sent by the second node requesting to query the first FlexE client transmission path.
  • the first sending unit 720 is configured to send a second message to the second node.
  • the second message includes a path information table entry.
  • the path information entry includes at least one path information.
  • the path information includes: first node identity information, first FlexE client information, first physical interface identifier information, and second FlexE client information.
  • the second FlexE client information includes: first time slot information carrying the first FlexE client, first FlexE group information carrying the first FlexE client;
  • the physical interface identification information includes physical interface identification information that carries the first FlexE client;
  • the second FlexE customer information includes: second time slot information carrying the second FlexE client, and second information carrying the second FlexE client.
  • the second physical interface identifier information includes physical interface identifier information that carries the second FlexE client; a first time slot carrying the first FlexE client and a second time when the second FlexE client is hosted There is a cross relationship between the gaps.
  • the first node 70 further includes: a query unit 730, a first generating unit 740, and a second generating unit 750; as shown in FIG.
  • the query unit 730 is configured to query the time slot exchange mapping table according to the first message after the first receiving unit 710 receives the first message sent by the second node that queries the first FlexE client transmission path.
  • the first generating unit 740 is configured to: if the query result is queried by the query unit 730, the third exchange message is generated according to the first message, and the third message is sent to the third node.
  • the second generating unit 750 is configured to generate a second message according to the first message if the query unit 730 queries the time slot exchange mapping table that the query result does not exist.
  • the query unit 730 is configured to query the slot exchange mapping table according to the first FlexE client information recorded by the first message.
  • the query result includes second FlexE group information carrying the second FlexE client second time slot information and carrying the second FlexE client.
  • the first generating unit 720 is configured to generate a third message according to the first message, and send a third message to the third node on the physical interface that carries the second time slot of the second FlexE client.
  • the third message includes a path information entry; the path entry information in the third message includes a path information entry in the first message and path information of the first node 70;
  • the path information of a node 70 includes first FlexE customer information, identification information of a physical interface carrying the first FlexE client, information of the second FlexE client, and physical interface identification information of the second FlexE client.
  • the first node 70 further includes: a third generating unit 760; as shown in FIG.
  • the third generating unit 760 is configured to: after the first generating unit 710 generates the third message according to the first message, and after sending the third message to the third node, if the fourth message sent by the third node is not received within the specified duration And generating a second message according to the first message, where the fourth message includes a path information entry; and the path information entry in the fourth message includes at least path information of the third node.
  • the second message includes a path information entry; the path information entry in the second message includes a path information entry in the first message and path information of the first node 70;
  • the path information of a node 70 includes information of the first FlexE client, identification information of the physical interface carrying the first FlexE client, information of the second FlexE client, and physical interface identification information of the second FlexE client.
  • the second generating unit 720 is specifically configured to generate a second message according to the path information entry in the first message, where the second message includes a path information entry; the path in the second message The information entry contains the path information entry in the first message.
  • the first node 70 further includes: a second receiving unit 770 and a fourth generating unit 780; as shown in FIG. 18, wherein:
  • the second receiving unit 770 is configured to: after the first receiving unit 710 receives the first message sent by the second node to query the first FlexE client transmission path, before the first sending unit 720 sends the second message to the second node, The fourth message sent by the three nodes; wherein the fourth message includes a path information entry; the path information entry in the fourth message includes at least path information of the third node.
  • the fourth generating unit 780 is configured to generate a second message according to the fourth message.
  • the second message includes a path information entry; the path information entry in the second message includes a path information entry in the fourth message.
  • the second message includes a path information entry; the path information entry in the second message includes a path information entry in the fourth message and path information of the first node 70;
  • the path information of a node 70 includes information of the first FlexE client, identification information of the physical interface carrying the first FlexE client, information of the second FlexE client, and physical interface identification information of the second FlexE client.
  • the first message, the second message, the third message, and the fourth message are all carried by at least one FlexE overhead frame.
  • the first FlexE client information and the second FlexE client information of the FlexE client on the path node can be recorded as the transmission path of each hop, and the transmission path and ratio of the FlexE network segment to the segment can be dynamically discovered in real time.
  • the planned deployment path and the actually discovered path are used to evaluate the operation of the network. It is also possible to detect connection connectivity on the transmission path and locate faulty nodes on the transmission path within the FlexE network.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • FIG. 19 is a schematic structural diagram of a second node according to an embodiment of the present disclosure.
  • the second node 80 may include at least: a second sending unit 810 and a third receiving unit 820; wherein:
  • the second sending unit 810 is configured to send, to the first node 70, a first message requesting to query the first FlexE client transmission path.
  • the third receiving unit 820 is configured to receive the second message sent by the first node 70.
  • the second message includes a path information entry; the path information entry in the second message includes at least one path information, where the path information includes: first node identity information, first FlexE client information, first physical interface identifier information, The second FlexE client information and the second FlexE client information, where the first FlexE client information includes: first time slot information carrying the first FlexE client, and a first FlexE group carrying the first FlexE client
  • the first physical interface identifier information includes physical interface identifier information that carries the first FlexE client
  • the second FlexE client information includes: second time slot information that carries the second FlexE client, and carries the second Second FlexE group information of the time slot
  • the second physical interface identification information includes physical interface identification information that carries the second FlexE client; carrying the first time slot of the first FlexE client and carrying the second FlexE
  • the customer's second time slot has a cross relationship.
  • the first message, the second message, and the third message are all carried by at least one FlexE overhead frame.
  • the first FlexE client information and the second FlexE client information of the FlexE client on the path node can be recorded as the transmission path of each hop, and the transmission path and ratio of the FlexE network segment to the segment can be dynamically discovered in real time.
  • the planned deployment path and the actually discovered path are used to evaluate the operation of the network. It is also possible to detect connection connectivity on the transmission path and locate faulty nodes on the transmission path within the FlexE network.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • FIG. 20 is a first node 90 according to an embodiment of the present application.
  • the first node 90 includes a processor 901, a memory 902, and a transceiver 903.
  • the processor 901, the memory 902, and the transceiver 903 pass.
  • the buses 904 are connected to each other.
  • the memory 902 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), or an erasable programmable read only memory (Erasable Programmable Read-Only Mmory, EPROM or fast). Flash memory), the memory 902 is used for related instructions and data.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable Programmable Read-Only Mmory
  • Flash memory Flash memory
  • the transceiver 903 can include a receiver and a transmitter, for example, a radio frequency module.
  • the processor 901 described below receives or transmits a message, which can be understood by the processor 901 to receive or transmit through the transceiver.
  • the processor 901 may be one or more central processing units (CPUs). In the case where the processor 901 is a CPU, the CPU may be a single core CPU or a multi-core CPU.
  • CPUs central processing units
  • the processor 901 in the first node 90 is configured to read the program code stored in the memory 902, and perform the following operations:
  • the processor 901 receives, by the transceiver 903, a first message sent by the second node to query the first FlexE client transmission path.
  • the processor 901 sends a second message to the second node through the transceiver 903.
  • the second message includes a path information entry; the path information entry in the second message includes at least one path information, where the path information includes: first node identity information, first FlexE client information, first physical interface identifier information, The second FlexE client information and the second FlexE client information, where the first FlexE client information includes: first time slot information carrying the first FlexE client, and a first FlexE group carrying the first FlexE client
  • the first physical interface identifier information includes physical interface identifier information that carries the first FlexE client
  • the second FlexE client information includes: second time slot information that carries the second FlexE client, and carries the second The second FlexE group information of the FlexE client;
  • the second physical interface identifier information includes physical interface identifier information that carries the second FlexE client; the first time slot carrying the first FlexE client and the second FlexE
  • the customer's second time slot has a cross relationship.
  • the processor 901 is further configured to:
  • the time slot exchange mapping table is queried according to the first message.
  • the third message is generated according to the first message, and the third message is sent to the third node.
  • the second message is generated according to the first message.
  • the processor 901 queries the time slot exchange mapping table according to the first message, including:
  • the query result includes second time slot information carrying the second FlexE client and second FlexE group information carrying the second FlexE client.
  • the processor 901 generates a third message according to the first message, and sends a third message to the third node, including:
  • the third message includes a path information entry; the path entry information in the third message includes a path information entry in the first message and path information of the first node 90;
  • the path information of a node 90 includes first FlexE customer information, identification information of a physical interface carrying the first FlexE client, second FlexE client information, and physical interface identification information carrying the second FlexE client.
  • the processor 901 after the processor 901 generates the third message according to the first message and sends the third message to the third node, the processor 901 is further configured to:
  • the second message is generated according to the first message, where the fourth message includes a path information entry; the path information entry in the fourth message includes at least Path information of the third node.
  • the second message includes a path information entry; the path information entry in the second message includes a path information entry in the first message and path information of the first node 90;
  • the path information of a node 90 includes information of the first FlexE client, identification information of the physical interface carrying the first FlexE client, information of the second FlexE client, and physical interface identification information of the second FlexE client.
  • the processor 901 generates a second message according to the first message, including:
  • the processor 901 after the processor 901 receives the first message sent by the second node to query the first FlexE client transmission path, before the processor 901 sends the second message to the second node, the processor 901 is further configured to:
  • the second message includes a path information entry; the path information entry in the second message includes a path information entry in the fourth message.
  • the second message includes a path information entry; the path information entry in the second message includes a path information entry in the fourth message and path information of the first node 90;
  • the path information of a node 90 includes information of the first FlexE client, identification information of the physical interface carrying the first FlexE client, information of the second FlexE client, and physical interface identification information of the second FlexE client.
  • the first message, the second message, the third message, and the fourth message are all carried by at least one FlexE overhead frame.
  • the first FlexE client information and the second FlexE client information of the FlexE client on the path node can be recorded as the transmission path of each hop, and the transmission path and ratio of the FlexE network segment to the segment can be dynamically discovered in real time.
  • the planned deployment path and the actually discovered path are used to evaluate the operation of the network. It is also possible to detect connection connectivity on the transmission path and locate faulty nodes on the transmission path within the FlexE network.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • FIG. 21 is a second node 100, which is applied to a flexible Ethernet FlexE networking network, where the second node 100 includes a processor 1001, a memory 1002, and The transceiver 1003, the processor 1001, the memory 1002, and the transceiver 1003 are connected to one another via a bus 1004.
  • the memory 1002 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), or an erasable programmable read only memory (Erasable Programmable Read-Only Mmory, EPROM or fast). Flash memory), the memory 1002 is used for related instructions and data.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable Programmable Read-Only Mmory
  • Flash memory Flash memory
  • the transceiver 1003 can include a receiver and a transmitter, for example, a radio frequency module.
  • the processor 1001 described below receives or transmits a message, which can be understood as the processor 1001 receiving or transmitting through the transceiver.
  • the processor 1001 may be one or more central processing units (CPUs). In the case that the processor 1001 is a CPU, the CPU may be a single core CPU or a multi-core CPU.
  • CPUs central processing units
  • the processor 1001 in the second node 100 is configured to read the program code stored in the memory 1002 and perform the following operations:
  • the processor 1001 sends a first message to the first node 90 requesting to query the first FlexE client transmission path.
  • the processor 1001 receives the second message sent by the first node 90.
  • the second message includes a path information entry; the path information entry in the second message includes at least one path information, where the path information includes: first node identity information, first FlexE client information, first physical interface identifier information, The second FlexE client information and the second FlexE client information, where the first FlexE client information includes: first time slot information carrying the first FlexE client, and a first FlexE group carrying the first FlexE client
  • the first physical interface identifier information includes physical interface identifier information that carries the first FlexE client
  • the second FlexE client information includes: second time slot information that carries the second FlexE client, and carries the second The second FlexE group information of the FlexE client;
  • the second physical interface identifier information includes physical interface identifier information that carries the second FlexE client; the first time slot carrying the first FlexE client and the second FlexE
  • the customer's second time slot has a cross relationship.
  • the first message, the second message, and the third message are all carried by at least one FlexE overhead frame.
  • the first FlexE client information and the second FlexE client port information of the FlexE client on the path node can be recorded as the transmission path of each hop, and the transmission path of the FlexE network segment to the segment can be dynamically discovered in real time.
  • the planned transmission path and the actually discovered path are compared to evaluate the operation of the network, and the connection connectivity on the transmission path and the faulty node on the transmission path in the FlexE network can be detected.
  • the FlexE overhead frame carries the messages in the transmission process to implement out-of-band communication, which does not occupy the bandwidth of the data path, and does not affect the carrying efficiency of the data path.
  • a computer readable storage medium stores a computer program, where the computer program includes program instructions, and when the program instructions are executed by a processor, the first node receives The first node sends a second message to the second node; the second message includes a path information entry; the path information entry in the second message Include at least one path information; the path information includes: first node identity information, first FlexE client information, first physical interface identifier information, second FlexE client information, and second physical interface identifier information; wherein the first FlexE The customer information includes: first slot information carrying the first FlexE client, first FlexE group information carrying the first FlexE client; the first physical interface identifier information includes a physics carrying the first FlexE client Interface identification information; the second FlexE client information includes: second time slot information carrying the second FlexE client, The second FlexE group information of the second FlexE client; the second physical interface identifier information includes physical interface identifier information that carries the second FlexE client; and the first time slot and
  • the above computer readable storage medium may be the internal storage unit of the first node or the second node described above in any of the foregoing embodiments, such as a hard disk or a memory of the first node or the second node.
  • the computer readable storage medium may also be an external storage device of the first node or the second node, for example, a plug-in hard disk (Smart), or a smart memory card (SMC) provided on the first node or the second node. Secure Digital (SD) card, Flash Card, etc.
  • the computer readable storage medium may further include an internal storage unit of the first node or the second node and an external storage device.
  • the computer readable storage medium described above is for storing the above computer program and other programs and data required by the first node or the second node.
  • the computer readable storage medium described above can also be used to temporarily store data that has been output or is about to be output.
  • the program can be stored in a computer readable storage medium, when the program is executed
  • the flow of the method embodiments as described above may be included.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请实施例提供了一种获得目标传输路径的方法、相关设备及系统。其中，该方法应用于灵活以太网FlexE组网网络中，包括：接收第二节点发送的请求查询第一FlexE客户传输路径的第一消息；向所述第二节点发送第二消息；其中，第二消息中的路径信息表项包括FlexE客户在各节点上的路径信息。通过记录FlexE客户在路径节点上的入口信息及出口信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。

Description

获得目标传输路径的方法、相关设备及系统 技术领域
本申请涉及通信领域，尤其涉及一种获得目标传输路径的方法、相关设备及系统。
背景技术
光互联论坛(Optical Internetworking Forun，OIF)发布的灵活以太网(Flexible Ethernet，FlexE)实施协议中在介质访问控制层和物理层之间定义了一个垫片(shim)层。基于FlexE的转发中，发送端FlexE设备使用FlexE客户(FlexE client)对应的时隙向接收端FlexE设备发送该FlexE客户的报文。接收端FlexE设备从FlexE客户对应的时隙中获取发送端FlexE设备发送的数据来恢复该FlexE客户的报文。
在发送该FlexE客户的报文的过程中，若能获取该传输过程中的路径跟踪报文，则可以明确知道该FlexE客户的传输路径。
现有技术一中，存在针对网络之间互连的协议(Internet Protocol，IP)分组网络设置的路径跟踪机制，使用基于IP报文封装的互联网控制消息协议(Internet Control Message Protocol，ICMP)格式报文，逐跳的跟踪并发送沿路的IP路由。在传递路径探测报文时需要查找IP路由转发表，但是FlexE中涉及到的1.5层(FlexE协议涉及到的数据传输层，位于开放系统互连参考模型(Open System Interconnect，OSI)7层模型的介质访问控制层和物理层之间，使用时分复用(Time Division Multiplexing，TDM)方式的数据传输层)网络不使用这类转发表，且无法识别数据流中的特定的报文。
现有技术二中，针对工作在介质访问控制层的以太网分组网络设置的路径跟踪机制，在传递路径探测报文时需要使用到组播转发。且使用特定类型的以太网帧(使用特定组播地址和以太网类型)作为路径跟踪探测报文。但是FlexE中涉及到的1.5层网络并不支持组播，且无法解析和识别数据流中的以太网帧。
发明内容
实施例提供了一种获得目标传输路径的方法、相关设备及系统，提供了一种在使用FlexE接口的1.5层网络下的路径发现机制。
第一方面，本申请实施例提供了一种获得目标传输路径的方法，所述方法应用于灵活以太网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客户的第一时隙信息；根据所述第一时隙信息确定承载所述第一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客户的物理接口的标识信息、所述第二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客户在路径节点上的入口信息及出口信息，作为每一跳的传输路径，可以实时动态发现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组信息；查询子单元，用于根据所述第一时隙信息及所述第一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客户的第一时隙信息、承载所述第一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客户的第一时隙与承载所述第二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客户的物理接口标识信息。
在一个可选的实现方式中，所述第一消息、所述第二消息、所述第三消息及所述第四消息均由至少一个FlexE开销帧承载。
第六方面，本申请实施例提供了一种第二节点，所述第二节点应用于灵活以太网FlexE组网网络中，所述第二节点包括：处理器、存储器和收发器，其中：所述处理器、所述存 储器和所述收发器相互连接，所述存储器用于存储计算机程序，所述计算机程序包括程序指令，所述处理器被配置用于调用所述程序指令，执行以下步骤：向第一节点发送请求查询第一FlexE客户传输路径的第一消息；接收所述第一节点发送的第二消息；其中，所述第二消息包括路径信息表项；所述路径信息表项包括至少一项路径信息；所述路径信息包括：所述第一节点身份信息、第一FlexE客户信息、第一物理接口标识信息、第二FlexE客户信息及第二物理接口标识信息；其中，所述第一FlexE客户信息包括：承载所述第一FlexE客户的第一时隙信息、承载所述第一FlexE客户的第一FlexE组信息；所述第一物理接口标识信息包括承载所述第一FlexE客户的物理接口标识信息；所述第二FlexE客户信息包括：承载第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；所述第二物理接口标识信息包括承载所述第二FlexE客户的物理接口标识信息；承载所述第一FlexE客户的第一时隙与承载所述第二FlexE客户的第二时隙存在交叉关系。
在一个可选的实现方式中，所述第一消息及所述第二消息均由至少一个FlexE开销帧承载。
第七方面，本申请实施例提供了一种通信系统，包括第一节点及第二节点；所述第一节点为第三方面，或者第三方面的任意一个可选的实现方式所描述的第一节点，所述第二节点为第四方面，或者第四方面的任意一个可选的实现方式所描述的第二节点。
第八方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被第一设备的处理器执行时，使所述第一设备的处理器执行上述第一方面或者第一方面的任意一个可选的实现方式所描述的方法；或者所述程序指令当被第二设备的处理器执行时，使所述第二设备的处理器执行上述第二方面或者第二方面的任意一个可选的实现方式所描述的方法。
实施本申请实施例，可以通过记录FlexE客户在路径节点上的第一FlexE客户信息及第二FlexE客户信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
图1为FlexE通用结构示意图；
图2为FlexE日历示意图；
图3为FlexE开销帧格式定义示意图；
图4为本申请实施例提供的一种data字段格式示意图；
图5为本申请实施例提供的一种Traced Route字段格式示意图；
图6为本申请实施例提供的一种通信系统的结构示意图；
图7为本申请实施例提供的一种PE节点结构示意图；
图8为本申请实施例提供的一种P节点结构示意图；
图9为本申请实施例提供的一种获得目标传输路径的方法的流程示意图；
图10为本申请实施例提供的另一种获得目标传输路径的方法的流程示意图；
图11为本申请实施例提供的另一种获得目标传输路径的方法的流程示意图；
图12为本申请实施例提供的另一种获得目标传输路径的方法的流程示意图；
图13为本申请实施例提供的一种具体场景示意图；
图14为本申请实施例提供的一种具体的Traced Route字段示意图；
图15为本申请实施例提供的另一种具体场景示意图；
图16为本申请实施例提供的另一种具体的Traced Route字段示意图；
图17为本申请实施例提供的一种第一节点的结构示意图；
图18为本申请实施例提供的另一种第一节点的结构示意图；
图19为本申请实施例提供的一种第二节点的结构示意图；
图20为本申请实施例提供的另一种第一节点的结构示意图；
图21为本申请实施例提供的另一种第二节点的结构示意图。
具体实施方式
下面将结合附图对本申请实施例中的技术方案进行清楚、详尽地描述。
FlexE的速率聚合支持高速以太网业务数据流使用低速率的多个物理接口一同承载，子速率和通道化则允许一个以太网物理接口内并发的承载多个低速率的数据流。
FlexE通过TDM划分时隙，实现传输管道带宽的基于时分的硬分割，实现了链路带宽在几个业务时间的硬分配，一个业务数据流可以分配到1到多个时隙中，实现了对各种速率业务的匹配。
一个FlexE组(FlexE Group)可以包含一个或多个物理链路接口(PHY)。FlexE Group对应的时隙分配表叫FlexE-calendar，每个物理链路对应的时隙映射表叫子时隙分配表sub-calendar。每个sub-calendar指示了20个时隙如何分配给相应的FlexE client。FlexE client代表在FlexE Group上指定时隙(1到多个时隙)传输的客户数据流，一个FlexE Group上可承载多个FlexE Client，如图1所示。
一个FlexE Client可对应一个到多个用户业务数据流(MAC Client)，FlexE Shim层提供FlexE Client到MAC Client的数据适配和转换。
图2显示了一个跨n个物理接口(聚合n个PHY)的FlexE Group的时隙分配情况，每个物理接口均拥有20个子时隙(Slot 0-Slot 19)，因此该FlexE Group拥有20n个子时隙(sub-calendar)。
根据FlexE实施协议1.0(Implementation Agreement 1.0)协议，一个FlexE Group在每个PHY上每隔13.1μs上就会发出一个开销块(FlexE overhead 66b block)至远端的PHY，8个依次发送的FlexE overhead 66b block构成了一个FlexE开销帧(FlexE overhead frame)。FlexE定义开销帧上的一些字段承载时隙分配表，并通过FlexE开销帧把时隙表同步至远端的PHY，以保证双端使用相同的时隙分配表接收和发送FlexE client数据流。FlexE Group开销帧的8个66b block的格式定义如图3所示。其中，Block#1-3用于记载各种数据，在 此不详细介绍，而Block#4-8为预留的管理通道(Management Channel)，未记录任何信息。因此，本申请实施例中涉及到的第一消息、第二消息、第三消息以及第四消息等均可由FlexE开销帧来承载。本申请实施例中涉及到的第一消息以及第三消息可以是路径探测请求消息；本申请实施例中涉及到的第二消息以及第四消息可以是路径探测应答消息。由于考虑到一个开销帧仅提供Block#4-8的5个blocks(一共只能提供5*64bits＝320bits，即为40个字节的空间供承载消息)，存储空间有限，故可使用多个连续的FlexE开销帧来承载上述消息。
接下来介绍本申请实施例提供的路径探测消息的报文格式。其中，路径探测消息包括路径探测请求消息以及路径探测应答消息。即为本申请后续实施例中涉及到的第一消息、第二消息、第三消息以及第四消息等。
具体地，本申请实施例可使用但不限于使用data字段记录PE节点请求的FlexE Client和沿线的路径信息，data字段具体格式如图4所示。
具体地，序列号(Sequence Number)字段用于标识路径探测消息的编号。用于当用户在PE节点上输入多个请求查询某个FlexE客户的路径探测消息的指令时，对整个传输路径上的不同的路径探测消息进行区分。
具体地，消息类型(Op Code)代表路径探测消息的类型，可为路径探测请求消息或者路径探测应答消息。例如，可以设定当Op Code字段的值为1时，表示该消息为路径探测请求消息，当Op Code字段的值为0时，表示该消息为路径探测应答消息。反之亦可。
具体地，源FlexE客户(Source Client)代表PE节点请求的FlexE Client，可用编号或传输该FlexE Client所使用的时隙分配表表示。
具体地，跳数值(Hop Count)表示当前消息所经历路径的跳数，路径探测请求消息每经过一个节点，就递增Hop Count；路径探测应答消息每经过一个节点，就递减Hop Count。
具体地，路径信息表项(Traced Route)记录路径探测请求消息探测到的路径信息，本申请实施例中称为，可进一步拆分为多个表项表示，每个表项对应路径上的一跳节点。如图5所示，每个表项应包含有当前节点的身份信息node ID、入口FlexE客户信息Ingress Client和出口FlexE客户信息Egress Client。可以知道的是，入口FlexE客户信息可以包括第一FlexE客户信息及承载第一FlexE客户的物理接口的标识信息；出口FlexE客户信息可以包括第二FlexE客户的信息及承载第二FlexE客户的物理接口标识信息。Traced Route的存在形式不限定于是一个路径信息表项，实际上还可以以其他形式存在，能够记录路径探测请求消息探测到的各个节点的路径信息即可。
其中，Ingress Client包括承载第一FlexE客户的第一时隙信息FlexE Client#c1、承载该第一FlexE客户的第一FlexE组信息FlexE Group#g1、承载第一FlexE客户的物理接口标识信息PHY#p1；Egress Client包括：承载第二FlexE客户的第二时隙信息FlexE Group#c2、承载上述第二FlexE客户的第二FlexE组信息FlexE Group#g2、承载第二FlexE客户的物理接口标识信息PHY#p2。其中，第一FlexE客户为第一消息中请求查询的FlexE客户。第二FlexE客户为第一FlexE客户在该节点内通过时隙交叉后的FlexE客户。第三消息为经过该节点后，基于第一消息生成的新的路径探测请求消息，至少包括跳数值的增加，还可以包括路径信息表项中该节点路径信息的增加。
本申请实施例涉及的第一节点、第二节点可以是网络边缘与用户连接的网络设备 (Provider Edge，PE)节点，设备上配备有网络之间或网络内设备之间的接口(Network to Network Interface，NNI)和用户侧接口(User Network Interface，UNI)；本申请实施例涉及的第一节点、第二节点还可以是即网络内的网络设备(Provider，P)节点，设备上仅配备NNI。具体地，NNI例如可以是FlexE接口，UNI例如可以是标准以太网接口。
本申请实施例适用于使用FlexE接口的多节点网络。
接下来结合图6-图8介绍本申请实施例涉及的通信系统以及相关设备。其中，图6为本申请实施例提供的一种通信系统的结构示意图；图7为本申请实施例提供的一种PE节点的结构示意图；图8为本申请实施例提供的一种P节点的结构示意图。
图6为本申请实施例提供的一种通信系统的结构示意图，如图6所述，通信系统可以包括至少一个PE节点和若干个P节点，PE节点可以通过FlexE接口向P节点发送携带路径探测请求消息的开销帧，P节点在接收到PE节点发送的携带路径探测请求消息的开销帧之后，向下一个P节点发送添加了路径信息的重新封装后的携带路径探测请求消息的开销帧。P节点也可以向上一个P节点或者PE节点发送携带路径探测应答消息的开销帧。PE节点在接收到P节点发送的携带路径探测应答消息的开销帧后，可以提取该开销帧内记录路径信息的字段，从而实现路径发现的功能。
PE节点和P节点包括但不限于是支持FlexE接口的基于IP的传送网、分组传送网(Packet Transport Network，PTN)盒式或框式交换机设备等。可以在交换机设备(PE节点、P节点)的NNI侧接口芯片增加能够实现路径发现的功能单元，即在FlexE接口架构(即NNI侧)下增加实施路径发现的逻辑处理单元(traceroute)，实现FlexE开销帧的封装和提取，以实现路径发现的功能。如图7和8所示。
具体地，如图7所示的PE节点结构示意图。从图中可以看出，PE节点10至少可以包括：UNI侧接口芯片110、交换网芯片120及NNI侧接口芯片130；其中，NNI侧接口芯片130又包括逻辑处理单元(traceroute)131、FlexE垫片(FlexE Shim)132、PHY133。
UNI侧接口芯片110用于接收用户输入的各种指令，例如请求查询FlexE客户传输路径的指令。交换网芯片120用于连接UNI侧接口芯片110以及NNI侧接口芯片130，用于实现FlexE客户的时隙交换。逻辑处理单元(traceroute)131用于封装以及提取FlexE开销帧，FlexE垫片(FlexE Shim)132用于实现将标准以太网数据流转换到FlexE时隙数据流，PHY133用于向下一个节点的PHY发送FlexE开销帧。
具体地，如图8所示的P节点结构示意图。从图中可以看出，P节点20至少可以包括：两个NNI侧接口芯片210以及交换网芯片220、其中，每个NNI侧接口芯片210又包括PHY211、FlexE Shim212、traceroute213。
PHY211用于接收或者发送FlexE开销帧，FlexE Shim212用于实现将标准以太网数据流与FlexE时隙数据流的相互转换，traceroute213用于封装以及提取FlexE开销帧。
接下来将结合图1-图8的描述，介绍本申请实施例提供的获得目标传输路径的方法。
请参见图9。图9为本申请实施例提供的一种获得目标传输路径的方法的流程示意图，该方法包括但不限于以下步骤：
S301：第二节点向第一节点发送的请求查询第一FlexE客户传输路径的第一消息。
在第一种可能的实现方式中，第二节点可以是PE节点，第一节点为P节点。用户可 以在第二节点上输入请求查询第一FlexE客户传输路径的指令。第二节点可以根据上述指令生成第一消息。并将上述第一消息封装在至少一个FlexE开销帧内。其中，第一消息可以为路径探测请求消息。
具体地，可以根据上述指令查询传输上述第一FlexE客户的第一时隙，承载该第一时隙的第一FlexE组，以及该第一FlexE组包含的物理接口。根据该第一FlexE客户占用的时隙，从上述第一FlexE组包含的物理接口中分配传输该第一FlexE客户的至少一个物理接口。
具体地，第一FlexE客户可以占用多个时隙，第二节点可以从上述第一FlexE组包含的物理接口中选取一个物理接口，或者，第二节点可以从上述第一FlexE组包含的物理接口中选取多个物理接口，分别承载一个或多个上述时隙。例如，当该第一FlexE客户占用两个时隙，可以为该第一FlexE客户分配一个物理接口，该物理接口包括上述两个时隙；或者可以为该第一FlexE客户分配两个物理接口，上述两个物理接口分别包括上述两个时隙中的一个时隙。
第一消息的data字段中，可以记录该路径探测消息的标号、消息类型(路径探测请求消息)、上述第一FlexE客户的编号(或者传输该FlexE Client所使用的时隙分配表)、跳数值以及路径信息表项。可以知道的是，由于第二节点为PE节点，因此跳数值为初始值Z 0，Z 0例如可以但不限于为0，且信息表项内未记录任何路径信息。
在第二种可能的实现方式中，第二节点可以是P节点，第一节点为P节点。第二节点向第一节点发送的第一消息为路径探测请求消息。第一消息的data字段中，可以记录该路径探测消息的标号、消息类型(路径探测请求消息)、上述第一FlexE客户的编号(或者传输该FlexE Client所使用的时隙分配表)、跳数值以及路径信息表项。
在第三种可能的实现方式中，第二节点可以是P节点，第一节点可以是PE节点。此时，第一节点接收到第二节点发送的第一消息后，传输路径终结。第一消息的data字段中，可以记录该路径探测消息的标号、消息类型(路径探测请求消息)、上述第一FlexE客户的编号(或者传输该FlexE Client所使用的时隙分配表)、跳数值以及路径信息表项。
S302：上述第一节点向上述第二节点发送第二消息。
具体地，第二消息中包括路径信息表项；上述路径信息表项包括至少一项路径信息；上述路径信息包括：上述第一节点身份信息、第一FlexE客户信息、第一物理接口标识信息、第二FlexE客户信息及第二物理接口标识信息；其中，上述第一FlexE客户信息包括：承载上述第一FlexE客户的第一时隙信息、承载上述第一FlexE客户的第一FlexE组信息；上述第二FlexE客户信息包括：承载第二FlexE客户的第二时隙信息、承载上述第二FlexE客户的第二FlexE组信息；上述第二物理接口标识信息包括承载上述第二FlexE客户的物理接口标识信息；承载上述第一FlexE客户的第一时隙与承载上述第二FlexE客户的第二时隙存在交叉关系，即上述第一FlexE客户的第一时隙在上述第一节点内经过时隙交叉，可以交叉到上述第二FlexE客户的第二时隙。
可以知道的是，承载上述第二FlexE客户的第二时隙的物理接口标识信息可以是承载上述第二FlexE客户的第二时隙的所有物理接口标识信息，也可以是承载上述第二FlexE客户的第二时隙的多个物理接口中的其中一个物理接口的标识信息，第一节点可以在该物 理接口上向第三节点发送第三消息，第三消息可以与第一消息对应，在第一消息的基础上更新后得到第三消息，第三消息可以为路径探测请求消息。此处对于第一消息的更新可以是只增加第一消息中的跳数值，也可以是既增加第一消息中的跳数值，进而生成第三消息；又可以是在第一消息的路径信息表项的基础上增加第一节点的路径信息，进而生成第三消息。
需要说明的是，后续实施例中提到的承载上述第二FlexE客户的第二时隙的物理接口标识信息均可以是承载上述第二FlexE客户的第二时隙的所有物理接口标识信息，也可以是承载上述第二FlexE客户的第二时隙的多个物理接口中的其中一个物理接口的标识信息。在后续实施例中不再赘述。
其中，上述第二消息可以为路径探测应答消息。即路径终结后，从下游节点返回的路径探测应答消息。该路径探测应答消息可以记录整个传输路径上各个节点的路径信息，或者可以记录上述第二节点下游的所有节点的路径信息。可以理解的是，第一节点为第二节点的下游节点。相反的，第二节点为第一节点的上游节点。
实施本申请实施例，可以通过记录FlexE客户在路径节点上的入口信息及出口信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。
接下来请参见图10。图10为本申请实施例提供的另一种获得目标传输路径的方法的流程示意图，该方法包括但不限于以下步骤：
S401：第二节点接收用户输入的请求查询第一FlexE客户传输路径的指令。
具体地，第二节点为PE节点。用户可以通过第一节点的UNI侧接口输入上述请求查询第一FlexE客户传输路径的指令。
S402：第二节点根据上述指令查询传输第一FlexE客户的第一时隙信息，承载该第一FlexE客户的第一FlexE组信息，以及该第一FlexE组包含的物理接口。
具体地，传输第一FlexE客户的第一时隙，承载该第一FlexE客户的第一FlexE组，以及该第一FlexE组包含的物理接口均为用户预先为该节点配置好的参数。该第一FlexE组包含的物理接口的数量为至少一个。
在一种可能的实现方式中，第一FlexE客户可以包含标识信息。
第一节点可以根据第一FlexE客户包含的标识信息确定传输传输第一FlexE客户的第一时隙信息，进而确定承载该第一FlexE客户的第一FlexE组信息。
具体地，第一FlexE客户标识信息与承载该第一FlexE客户的第一时隙信息存在映射关系。该映射关系也为用户预先设置好的参数。在知道该第一FlexE客户标识信息的情况下，根据上述映射关系即可确定承载该第一FlexE客户的第一时隙信息。反之，根据承载FlexE客户的时隙信息也可以确定该FlexE客户的标识信息。
S403：第二节点根据该第一FlexE客户占用的时隙，从上述第一FlexE组包含的物理接口中分配承载该第一FlexE客户的至少一个物理接口。
具体地，第一FlexE客户可以占用多个时隙，第二节点可以从上述第一FlexE组包含的物理接口中分配一个物理接口，或者，第二节点可以从上述第一FlexE组包含的物理接 口中分配多个物理接口，分别承载一个或多个上述时隙。例如，当该第一FlexE客户占用两个时隙，可以为该第一FlexE客户分配一个物理接口，该物理接口包括上述两个时隙；或者可以为该第一FlexE客户分配两个物理接口，上述两个物理接口分别包括上述两个时隙中的一个时隙。
S404：第二节点向第一节点发送请求查询第一FlexE客户传输路径的第一消息，第一节点接收第二节点发送的第一消息。
具体地，第二节点在上述分配的至少一个物理接口上分别产生一条第一消息。
第一消息的data字段中，可以记录该路径探测消息的标号、消息类型(路径探测请求消息)、上述第一FlexE客户的编号(或者传输该FlexE Client所使用的时隙分配表)、跳数值以及路径信息表项。可以知道的是，由于第二节点为PE节点，因此跳数值为初始值Z 0，Z 0例如可以但不限于为0，且信息表项内未记录任何路径信息。
可以知道的是，第二节点在上述分配的至少一个物理接口上分别产生一条第一消息之后，可以一起发送至同一个第一节点，该第一节点可以分别针对每一条第一消息生成一条第三消息。第二节点在上述分配的至少一个物理接口上分别产生一条第一消息之后，也可以分别发送至不同的第一节点。每个第一节点针对其收到的每一条第一消息分别生成一条第三消息。
此外，当第二节点向第一节点发送第一消息后，启动计时器。若计时器在计时结束后，未收到第一节点返回的第二消息(路径探测应答消息)，说明路径发现失败，未发现任何路径信息，清除当前记录的跳数值、Source Client字段。其中，计时器的计时时长例如可以但不限于是50n*13.1μs，其中，n表示FlexE网络中的平均跳数。
S405：第一节点根据第一FlexE客户信息查询时隙交换映射表，判断是否存在查询结果。若存在查询结果，执行S406；若不存在查询结果，执行S411。
具体地，第一FlexE客户信息包括承载上述第一FlexE客户的第一时隙信息及承载上述第一FlexE客户的第一FlexE组信息。
具体地，可以通过提取第一消息的Source Client字段获取上述第一FlexE客户信息。另外，第一节点在接收到第二节点发送的第一消息时，可以将第一FlexE客户信息保存至本地，第一节点可以提取本地保存的第一FlexE客户信息。
可以知道的是，当第二节点为P节点时，第一节点可以提取第一消息中的路径信息表征的最后一项中记录的第二FlexE客户信息，将上述第二FlexE客户信息作为查询条件，查询时隙交换映射表。其中，第二FlexE客户信息为第二节点向第一节点发出第一消息时承载的FlexE客户的时隙信息以及承载该FlexE客户的FlexE组信息。
其中，判断第二节点是PE节点还是P节点，可以通过判断第一消息中的跳数值是否大于初始值Z 0。若大于Z 0则说明第二节点为P节点，若为Z 0则说明第二节点为PE节点。
S406：第一节点根据第一消息生成第三消息。
具体地，当第一节点根据第一FlexE客户信息查询时隙交换映射表存在查询结果时，根据第一消息生成第三消息。其中，第一消息为路径探测请求消息，第三消息也为路径探测请求消息。
具体地，查询结果包括承载第二FlexE客户的第二时隙信息、承载上述第二FlexE客 户的第二FlexE组信息。可以知道的是，第一FlexE客户在第一节点内经过时隙交换，交换成了第二FlexE客户。对于每一个第一节点来说，接收上游节点发送的FlexE客户为第一FlexE客户，向下游节点发送的FlexE客户为第二FlexE客户。换言之，当前节点的第一FlexE客户即为上游节点的第二FlexE客户；当前节点的第二FlexE客户即为下游节点的第一FlexE客户。
在一种可能的实现方式中，在传输路径上，向下游节点发送路径探测请求消息时，添加当前节点的路径信息至路径信息表项。
具体地，第三消息中包含路径信息表项；第三消息中的路径表项信息包含第一消息中的路径信息表项以及第一节点的路径信息；其中，第一节点的路径信息包括上述第一FlexE客户信息、承载上述第一FlexE客户的物理接口的标识信息、上述第二FlexE客户信息及承载上述第二FlexE客户的物理接口标识信息。第一节点的路径信息作为第三消息中的路径信息表项的最后一项。
此外，第三消息中还可以包括跳数值。第三消息中的跳数值与第一消息中的跳数值相比加1。若第一消息中记录的跳数值为Z 0，那么第三消息中记录的跳数值则为Z 0+1。
在另外一种可能的实现方式中，在传输路径上，向下游节点发送路径探测请求消息时，不添加当前节点的路径信息至路径信息表项，而是在向上游节点返回路径探测应答消息时，添加当前节点的路径信息至路径信息表项。
具体地，第三消息中包含路径信息表项；第三消息中的路径信息表项包含第一消息中的路径信息表项。即第一消息中的路径信息表项未记录任何路径信息，第三消息中的路径信息表项也未记录任何路径信息。但是，第三消息中的跳数值与第一消息中的跳数值相比加1。若第一消息中记录的跳数值为Z 0，那么第三消息中记录的跳数值则为Z 0+1。
S407：第一节点向第三节点发送上述第三消息。
具体地，第一节点在承载上述第二时隙的第二FlexE组包含的至少一个物理接口上向第三节点发送第三消息。可以知道的是，具体使用哪一个物理接口发送第三消息可以是预先配置好的，根据第二时隙即可确定该物理接口。或者，第一节点无法根据第二时隙确定物理接口，则可以使用第二FlexE组包含的所有物理接口，分别在每一个物理接口上发送一条第三消息，但是最终只会在某一个物理接口上收到下游节点返回的路径探测应答消息。可以知道的是，每一条第三消息中记录的发送第三消息的物理接口的标识信息不同。
S408：第一节点若在指定时长内没有接收到第三节点发送的第四消息，则根据上述第一消息生成第二消息。
同样的，当第一节点向第三节点发送第三消息后，启动计时器。若计时器在计时结束后，未收到第三节点返回的第四消息(路径探测应答消息)，说明路径在第三节点终结。则根据第一消息生成第二消息。其中，计时器的计时时长例如可以但不限于是50n*13.1μs，其中，n表示FlexE网络中的平均跳数。
具体地，上述第四消息中包含路径信息表项；第四消息中包含的路径信息表项至少包括第三节点的路径信息。第三节点的路径信息包含的具体内容可参考第一节点的路径信息包含的内容，在此不再赘述。
具体地，第二消息中包含路径信息表项；第二消息中的路径表项信息包含第一消息中 的路径信息表项以及第一节点的路径信息；其中，第一节点的路径信息包括第一FlexE客户的信息、承载第一FlexE客户的物理接口的标识信息、第二FlexE客户的信息及承载所述第二FlexE客户的物理接口标识信息。第一节点的路径信息作为第二消息中的路径信息表项的最后一项。
可以知道的是，第二消息中包含的路径信息表项；第二消息中的路径信息表项包含第三消息中的路径信息表项。
此外，第二消息中还可以包括跳数值。第二消息中的跳数值与第一消息中的跳数值相比加1。若第一消息中记录的跳数值为Z 0，那么第三消息中记录的跳数值则为Z 0+1。
此外，第二消息中的Op Code字段发生变化。可以知道的是，第一消息为路径探测请求消息，第二消息为路径探测应答消息。
S409：第三节点向第一节点发送第四消息，第一节点接收第三节点发送的第四消息。
具体地，第一节点在指定时长内接收到第三节点发送的第四消息。其中，第四消息中包含路径信息表项；上述路径信息表项至少包括上述第三节点的路径信息。
在一种可能的实现方式中，在传输路径上，向下游节点发送路径探测请求消息时，添加当前节点的路径信息至路径信息表项。具体地，第四消息中包含路径信息表项；第四消息中的路径表项信息包含传输路径上所有节点的路径信息。
在另外一种可能的实现方式中，在传输路径上，向下游节点发送路径探测请求消息时，不添加当前节点的路径信息至路径信息表项，而是在向上游节点返回路径探测应答消息时，添加当前节点的路径信息至路径信息表项。具体地，第四消息中包含路径信息表项；第四消息中的路径表项信息包含传输路径上第一节点的所有下游节点的路径信息，即第三节点及第三节点的所有下游节点的路径信息。
具体地，第三节点可以在接收到第三消息的物理接口向第一节点发送第四消息。
S410：第一节点根据第四消息生成第二消息。
在一种可能的实现方式中，在传输路径上，向下游节点发送路径探测请求消息时，添加当前节点的路径信息至路径信息表项。则此时第四消息中的路径表项信息包含传输路径上所有节点的路径信息，则只需将第四消息中的路径信息表项复制至第二消息的路径信息表项。然后将第四消息中的跳数值减一，作为第二消息中的跳数值。
在另外一种可能的实现方式中，在传输路径上，向下游节点发送路径探测请求消息时，不添加当前节点的路径信息至路径信息表项，而是在向上游节点返回路径探测应答消息时，添加当前节点的路径信息至路径信息表项。则此时第四消息中的路径表项信息包含传输路径上第一节点的所有下游节点的路径信息，则需在第四消息中的路径信息表项的基础上添加第一节点的路径信息至第二消息中的路径信息表项。然后将第四消息中的跳数值减一，作为第二消息中的跳数值。
此时，第一节点的路径信息的获取方式至少包括以下两种：
第一种：根据接收到的第四消息中的路径信息表项中最后一项记录的第二FlexE客户信息作为查询条件，查询时隙交换映射表，获取查询结果。可以知道的是，上述第二FlexE客户信息即为当前第一节点的第一FlexE客户信息，上述查询结果即为当前第一节点的第二FlexE客户信息。
其中，第一节点的路径信息包括第一FlexE客户的信息、承载第一FlexE客户的物理接口的标识信息、第二FlexE客户的信息及承载所述第二FlexE客户的物理接口标识信息。第一节点的路径信息作为第二消息中的路径信息表项的最后一项。
第二种：在根据第一消息生成第二消息的过程中，记录第一节点的路径信息。其中，第一节点的路径信息包括第一FlexE客户的信息、承载第一FlexE客户的物理接口的标识信息、第二FlexE客户的信息及承载所述第二FlexE客户的物理接口标识信息。
S411：第一节点根据第一消息生成第二消息。
具体地，在S405中，当第一节点根据第一FlexE客户信息查询时隙交换映射表不存在查询结果时，根据第一消息生成第二消息。其中，第一消息为路径探测请求消息，第二消息为路径探测应答消息。
具体地，查询结果不存在，表明传输路径在该节点终结，路径发现结束，由于第二节点为PE节点，因此，在第一节点内查询时隙交换映射表不存在查询结果，表示第二消息中的路径信息表项为空。
可以知道的是，当第二节点为P节点时，第一消息中的路径信息表项中至少可以包含第二节点的路径信息。可以直接将第一消息中的路径信息表项复制至第二消息中的路径信息表项，且跳数值不变。
S412：第一节点向第二节点发送第二消息。
具体地，在S408中根据第一消息生成第二消息之后，或者在S410中根据第四消息生成第二消息之后，或者在S411中根据第一消息生成第二消息之后，第一节点向第二节点发送第二消息。第二节点可以提取第二消息中的路径信息表项以获得传输路径。
具体地，第一节点可以在接收到第一消息的物理接口上向第二节点发送第二消息。
可以知道的是，若在S404中，第二节点在接收到用户输入的请求查询第一FlexE客户传输路径的指令之后，在根据该第一FlexE客户占用的时隙分配的多个物理接口上分别产生一条第一消息之后，此时在S412需接收所有根据该第一消息返回的第二消息，方可获得完整的传输路径。具体可以通过前述的在第二节点设置计时器来实现。具体地，可以通过各第二消息中的Sequence Number辨别各个第二消息是否属于同一个请求查询第一FlexE客户传输路径的指令。
可以知道的是，无论是在向下游节点发送第三消息时添加第一节点的路径信息，或者是在向上游节点返回第二消息时添加第一节点的路径信息，用户均可设置在第二节点上提取传输路径信息时的提取顺序，最终获得正确的传输路径。
例如，在向下游节点发送第三消息时添加第一节点的路径信息，最终直接提取第二消息中的路径信息表项即可。
又例如，在向上游节点返回第二消息时添加第一节点的路径信息，若是直接添加本地保存的发送第三消息时记录的节点信息，最终按照倒序提取第二消息中的路径信息表项即可。
又例如，在向上游节点返回第二消息时添加第一节点的路径信息，若是根据第一节点本地保存的查询条件查询时隙交换映射表，再添加第一节点的路径信息至第二消息中的路径信息表项，最终按照倒序提取第二消息中的路径信息表项即可。
又例如，在向上游节点返回第二消息时添加第一节点的路径信息，若是根据返回时的第一FlexE客户信息查询时隙交换映射表获取查询结果，作为第一节点的路径信息，最终按照倒叙提取第二消息中的路径信息表项，然后将第一FlexE客户信息与第二FlexE客户信息对调即可。
实施本申请实施例，可以通过记录FlexE客户在路径节点上的第一FlexE客户信息及第二FlexE客户信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
接下来将结合图11-图12分别介绍本申请实施例提供的两种不同的获取目标传输路径的方法。其中，两种方法的区别在于添加当前节点的路径信息至路径信息表项的方式不同。图11介绍了在传输路径上，向下游节点发送路径探测请求消息时，添加当前节点的路径信息至路径信息表项。图12介绍了在传输路径上，在向上游节点返回路径探测应答消息时，添加当前节点的路径信息至路径信息表项。
请参见图11。如图11所示，获取目标传输路径的方法至少可以包括以下几个步骤：
S501：第二节点接收用户输入的请求查询第一FlexE客户传输路径的指令。
S502：第二节点根据上述指令查询传输第一FlexE客户的第一时隙信息，承载该第一FlexE客户的第一FlexE组信息，以及该第一FlexE组包含的物理接口。
S503：第二节点根据该第一FlexE客户占用的时隙，从上述第一FlexE组包含的物理接口中分配承载该第一FlexE客户的至少一个物理接口。
S504：第二节点向第一节点发送请求查询第一FlexE客户传输路径的第一消息，第一节点接收第二节点发送的第一消息。
S505：第一节点根据第一FlexE客户信息查询时隙交换映射表，判断是否存在查询结果。若存在查询结果，执行S506；若不存在查询结果，执行S511。
其中，S501～S505的实现方式可以参考图10中的S401～S405，这里不作赘述。
S506：添加第一节点的路径信息至第一消息中的路径信息表项，生成第三消息。
具体地，查询结果包括承载第二FlexE客户的第二时隙信息、承载上述第二FlexE客户的第二FlexE组信息。第三消息中包含路径信息表项；第三消息中的路径表项信息包含第一消息中的路径信息表项以及第一节点的路径信息；其中，第一节点的路径信息包括上述第一FlexE客户信息、承载上述第一FlexE客户的物理接口的标识信息、上述第二FlexE客户信息及承载上述第二FlexE客户的物理接口标识信息。第一节点的路径信息作为第三消息中的路径信息表项的最后一项。
此外，第三消息中还可以包括跳数值。第三消息中的跳数值与第一消息中的跳数值相比加1。若第一消息中记录的跳数值为Z 0，那么第三消息中记录的跳数值则为Z 0+1。
S507：第一节点向第三节点发送上述第三消息。
S508：第一节点若在指定时长内没有接收到第三节点发送的第四消息，则根据上述第一消息生成第二消息。
其中，S507～S508的实现方式可以参考图10中的S407～S408，这里不作赘述。
S509：第三节点向第一节点发送第四消息，第一节点接收第三节点发送的第四消息。
具体地，第一节点在指定时长内接收到第三节点发送的第四消息。其中，第四消息中包含路径信息表项；第四消息中的路径表项信息包含传输路径上所有节点的路径信息。
S510：将第四消息中的路径信息表项作为第二消息中的路径信息表项，生成第二消息。
具体地，第四消息中的路径表项信息包含传输路径上所有节点的路径信息，只需将第四消息中的路径信息表项复制至第二消息的路径信息表项。然后将第四消息中的跳数值减一，作为第二消息中的跳数值。
S511：第一节点根据第一消息生成第二消息。
S512：第一节点向第二节点发送第二消息。
其中，S511～S512的实现方式可以参考图10中的S411～S412，这里不作赘述。
实施本申请实施例，可以通过在传输路径上，向下游节点发送路径探测请求消息时，添加当前节点的路径信息至路径信息表项。可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
请参见图12。如图12所示，获取目标传输路径的方法至少可以包括以下几个步骤：
S601：第二节点接收用户输入的请求查询第一FlexE客户传输路径的指令。
S602：第二节点根据上述指令查询传输第一FlexE客户的第一时隙信息，承载该第一FlexE客户的第一FlexE组信息，以及该第一FlexE组包含的物理接口。
S603：第二节点根据该第一FlexE客户占用的时隙，从上述第一FlexE组包含的物理接口中分配承载该第一FlexE客户的至少一个物理接口。
S604：第二节点向第一节点发送请求查询第一FlexE客户传输路径的第一消息，第一节点接收第二节点发送的第一消息。
S605：第一节点根据第一FlexE客户信息查询时隙交换映射表，判断是否存在查询结果。若存在查询结果，执行S606；若不存在查询结果，执行S611。
其中，S601～S605的实现方式可以参考图10中的S401～S405，这里不作赘述。
S606：将第一消息中的路径信息表项作为第三消息中的路径信息表项，生成第三消息。
具体地，查询结果包括承载第二FlexE客户的第二时隙信息、承载上述第二FlexE客户的第二FlexE组信息。第三消息中包含路径信息表项；第三消息中的路径信息表项包含第一消息中的路径信息表项。即第一消息中的路径信息表项未记录任何路径信息，第三消息中的路径信息表项也未记录任何路径信息。但是，第三消息中的跳数值与第一消息中的跳数值相比加1。若第一消息中记录的跳数值为Z 0，那么第三消息中记录的跳数值则为Z 0+1。
S607：第一节点向第三节点发送上述第三消息。
S608：第一节点若在指定时长内没有接收到第三节点发送的第四消息，则根据上述第一消息生成第二消息。
其中，S607～S608的实现方式可以参考图10中的S407～S408，这里不作赘述。
S609：第三节点向第一节点发送第四消息，第一节点接收第三节点发送的第四消息。
具体地，第一节点在指定时长内接收到第三节点发送的第四消息。其中，第四消息中包含路径信息表项。第四消息中的路径表项信息包含传输路径上第一节点的所有下游节点的路径信息，即第三节点及第三节点的所有下游节点的路径信息。
S610：添加第一节点的路径信息至第四节点中的路径信息表项，生成第二消息。
具体地，第四消息中的路径表项信息包含传输路径上第一节点的所有下游节点的路径信息，则需在第四消息中的路径信息表项的基础上添加第一节点的路径信息至第二消息中的路径信息表项。然后将第四消息中的跳数值减一，作为第二消息中的跳数值。
S611：第一节点根据第一消息生成第二消息。
S612：第一节点向第二节点发送第二消息。
其中，S611～S612的实现方式可以参考图10中的S411～S412，这里不作赘述。
实施本申请实施例，可以通过在传输路径上，向上游节点返回路径探测应答消息时，添加当前节点的路径信息至路径信息表项。可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
接下来将结合图13-图16介绍本申请实施例提供的另外三种获取目标传输路径的方法。
第一种：如图13所示，网络运维人员或用户在PE节点上FlexE节点#1(FlexE Node#1)请求查询FlexE客户#c1(FlexE Client#c1)在FlexE网络中的传输路径，本实施例的实施流程如下：
STEP 1：FlexE Node#1接收到用户的请求和输入FlexE Client#c1(c1代表时隙分配表，根据该时隙分配表可以确定传输该FlexE Client的时隙)，在FlexE Node#1上查询承载FlexE Client#c1的FlexE组(FlexE Group)为FlexE组#1(FlexE Group#1)，查询FlexE Group#1所包括的FlexE物理接口(PHY)为PHY#6，即承载FlexE Client#c1的物理接口为PHY#6，在PHY#6上发送携带有第一消息的FlexE开销帧；记录hop count为0、FlexE Group#1、FlexE Client#c1，启动计时器。
STEP 2：上述第一消息传递至远端的网络设备FlexE节点#2(FlexE Node#2)的NNI侧的FlexE接口PHY#6；traceroute功能单元解析第一消息Op Code字段，为路径探测请求消息；读取第一消息中的Traced Route字段，发现未包含任何路径信息表项；提取第一消息的source client字段，使用承载FlexE Client#c1的FlexE接口PHY#6所属的FlexE Group#1和RTR消息中source client字段的FlexE client#c1时隙分配表作为查询条件(同时记录查询条件)，查询FlexE Node#2节点内的FlexE时隙交换映射表，查询得到交叉映射的出口为FlexE组#3(FlexE Group#3)和FlexE客户#c2(FlexE Client#c2)。查询FlexE Group#3包含的FlexE接口PHY列表，FlexE Group#3仅包含PHY#3，即承载FlexE Client#c2的物理接口为PHY#3，递增第一消息中的hop count值，使用Node#2作为Node ID；FlexE组#1+PHY#6+FlexE客户#c1(FlexE Group#1+PHY#6+FlexE Client#c1)作为Ingress Client；FlexE组#3+PHY#3+FlexE客户#c2(FlexE Group#3+PHY#3+FlexE Client#c2)作为 Egress Client，附至Traced Route字段作为最后一个表项，生成第三消息，并在PHY#3上发送携带该第三消息的FlexE开销帧。记录hop count为1、FlexE Group#3、FlexE Client#c2，启动计时器。
STEP 3：如图13所示，由于FlexE节点#2(FlexE Node#2)至FlexE节点#3(FlexE Node#3)的链路出现故障，发出的第三消息无法抵达FlexE Node#3。FlexE Node#2收到计时器的超时事件(计时器计时结束后未收到FlexE Node#3返回的第四消息)，使用记录的hop count为1作为第二消息中的hop count值，将第三消息中的路径信息表征作为第二消息中的路径信息表项，针对承载FlexE Client#c1的物理接口PHY#6，发送封装该第二消息的FlexE开销帧。清除当前记录的hop count、FlexE Group#1、FlexE Client#c1，停止计时器。
STEP 4：第二消息传递至远端的网络设备FlexE Node 1的NNI侧的FlexE接口PHY#1；读取消息Op Code字段，为路径探测应答消息，读取第二消息的Hop Count字段，发现Hop Count值为0，终结第二消息。承载FlexE Client#c1的FlexE Group#1只对应1个物理端口PHY#1，已从该端口收到第二消息，路径探测终结。Node 1上的FlexE Client#c1的传输路径如图14所示。
本申请实施例以在第一节点向下游节点发送第三消息时添加第一节点的路径信息至第三消息中的路径信息表项的场景为例，实施路径发现的流程。可以通过记录FlexE客户在路径节点上的入口信息及出口信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
第二种：如图13所示，网络运维人员或用户在PE节点上FlexE Node#1请求查询FlexE Client#c1在FlexE网络中的传输路径，本实施例的实施流程如下：
STEP 1：FlexE Node#1接收到用户的请求和输入FlexE Client#c1(c1代表时隙分配表，根据该时隙分配表可以确定传输该FlexE Client的时隙)，在FlexE Node#1上查询承载FlexE Client#c1的FlexE Group为FlexE Group#1，查询FlexE Group#1所包括的FlexE物理接口(PHY)为PHY#6，即承载FlexE Client#c1的物理接口为PHY#6，在PHY#6上发送携带有第一消息的FlexE开销帧；记录hop count为0、FlexE Group#1、FlexE Client#c1，启动计时器。
STEP 2：上述第一消息传递至远端的网络设备FlexE Node#2的NNI侧的FlexE接口PHY#6；traceroute功能单元解析第一消息Op Code字段，为路径探测请求消息；读取第一消息中的Traced Route字段，发现未包含任何路径信息表项；提取第一消息的source client字段，使用承载FlexE Client#c1的FlexE接口PHY#6所属的FlexE Group#1和RTR消息中source client字段的FlexE client#c1时隙分配表作为查询条件(同时记录查询条件)，查询FlexE Node#2节点内的FlexE时隙交换映射表，查询得到交叉映射的出口为FlexE Group#3和FlexE Client#c2。查询FlexE Group#3包含的FlexE接口PHY列表，FlexE Group#3仅包含PHY#3，即承载FlexE Client#c2的物理接口为PHY#3，递增第一消息中的hop count值，生成第三消息，并在PHY#3上发送携带该第三消息的FlexE开销帧。记录hop count为1、 FlexE Group#3、FlexE Client#c2，启动计时器。
STEP 3：如图13所示，由于FlexE Node#2至FlexE Node#3的链路出现故障，发出的第三消息无法抵达FlexE Node#3节点。FlexE Node#2节点收到计时器的超时事件(计时器计时结束后未收到FlexE Node#3返回的第四消息)，使用记录的hop count为1作为第二消息中的hop count值，使用FlexE Group#1和FlexE client#c1查询FlexE时隙交换映射表，查询得到交叉映射的出口为FlexE Group#3和FlexE Client#c2(c2代表时隙分配表)；查询FlexE Group#1所包含的PHY，即FlexE Group#1仅对应PHY#6，即承载FlexE Client#c1的物理接口为PHY#6，则产生一条第二消息，使用Node#2作为Node ID；FlexE Group#1+PHY#6+FlexE Client#c1作为Ingress Client；FlexE Group#3+PHY#3+FlexE Client#c2作为Egress Client，附至Traced Route字段作为最后一个表项，作为第二消息中的路径信息表项；针对承载FlexE Client#c1的物理接口PHY#6，发送携带该第二消息的FlexE开销帧；清除当前记录的hop count、FlexE Group#1、FlexE Client#c1，停止RTR计时器。
STEP 4：第二消息传递至远端的网络设备FlexE Node 1的NNI侧的FlexE接口PHY#1；读取消息Op Code字段，为路径探测应答消息，读取第二消息的Hop Count字段，发现Hop Count值为0，终结第二消息。承载FlexE Client#c1的FlexE Group#1只对应1个物理端口PHY#1，已从该端口收到第二消息，路径探测终结。Node 1上的FlexE Client#c1的传输路径如图14所示。
本申请实施例以在第一节点向上游节点返回第二消息时添加第一节点的路径信息至第二消息中的路径信息表项的场景为例，实施路径发现的流程。可以通过记录FlexE客户在路径节点上的入口信息及出口信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
第三种：如图15所示，网络运维人员或用户在PE节点上FlexE节点#1(FlexE Node#1)请求查询FlexE客户#c1(FlexE Client#c1)在FlexE网络中的传输路径，本实施例的实施流程如下：
STEP 1:FlexE Node#1接收到用户的请求和输入FlexE Client#c1，在FlexE Node#1上查询承载FlexE Client#c1的FlexE组(FlexE Group)为FlexE组#1(FlexE Group#1)，查询FlexE Group#1所包括的FlexE物理接口(PHY)为PHY#1和PHY#2，在承载FlexE Client#c1的物理接口PHY#1和PHY#2上分别发送携带有第一消息的FlexE开销帧(该消息发送需要占用若干个FlexE开销发送周期)；记录hop count为0、FlexE Group#1、FlexE Client#c1，分别启动2个计时器。
STEP 2:第一消息传递至远端的网络设备FlexE节点#2(FlexE Node#2)的NNI侧的FlexE接口PHY#1；traceroute功能单元解析第一消息Op Code字段，为路径探测请求消息；读取第一消息中的traced route字段，发现未包含任何路径信息表项；提取第一消息的source client字段，使用接收到第一消息的FlexE接口PHY#1所属的FlexE Group#1和第一消息中source client字段的FlexE client#c1时隙分配表作为查询条件(同时记录查询条件)，查询 FlexE Node#2节点内的FlexE时隙交换映射表，查询得到交叉映射的出口为FlexE组#2(FlexE Group#2)和FlexE客户#c2(FlexE Client#c2)。查询FlexE Group#2包含的FlexE接口PHY列表，FlexE Group#2仅包含PHY#3，即承载FlexE Client#c2的物理接口为PHY#3，递增第一消息中的hop count值，生成第三消息，在PHY#3上发送携带有第三消息的FlexE开销帧。记录hop count为1、FlexE Group#2、FlexE Client#c2，启动计时器。
STEP 3:第一消息传递至远端的网络设备FlexE节点#3(FlexE Node#3)的NNI侧的FlexE接口PHY#2；traceroute功能单元解析第一消息Op Code字段，为路径探测请求消息；读取第一消息中的traced route字段，发现未包含任何路径信息表项；提取第一消息的source client字段，使用接收到第一消息的FlexE接口PHY#2所属的FlexE Group#1和第一消息中source client字段的FlexE client#c1时隙分配表作为查询条件(同时记录查询条件)，查询FlexE Node#2节点内的FlexE时隙交换映射表，查询得到交叉映射的出口为FlexE Group#2和FlexE Client#c2。查询FlexE Group#2包含的FlexE接口PHY列表，FlexE Group#2仅包含PHY#4，即承载FlexE Client#c2的物理接口为PHY#4，递增第一消息中的hop count值，生成第三消息，在PHY#4上发送携带有第三消息的FlexE开销帧。记录hop count为1、FlexE Group#2、FlexE Client#c2，启动计时器。
STEP 4：FlexE节点#4(FlexE Node#4)为PE节点，终结FlexE Group#2上的FlexE Client。因此，构造第四消息，使用第三消息中的hop count(此时为1)作为第四消息中的hop count值，初始化Traced Route表，但表项为空，生成第四消息；针对FlexE Group#2包含的PHY#3和PHY#4，即承载FlexE Client#c2的物理接口为PHY#3和PHY#4，即在PHY#3和PHY#4上分别发送携带该第四消息的FlexE开销帧。
STEP 5：FlexE Node#2节点在PHY#3上收到来自FlexE Node#4的第四消息。使用FlexE Group#2和FlexE client#c2查询FlexE时隙交换映射表，查询得到交叉映射的出口为FlexE Group#1和FlexE Client#c1；查询FlexE Group#1所包含的PHY，即FlexE Group#1仅对应PHY#1，即承载FlexE Client#c1的物理接口为PHY#1，则产生一条第二消息，使用Node#2、FlexE组#1+PHY#1+FlexE客户#c1(FlexE Group#1+PHY#1+FlexE Client#c1)和FlexE组#2+PHY#3+FlexE客户#c2(FlexE Group#2+PHY#3+FlexE Client#c2)作为Traced Route表项的3个字段Node ID、Ingress Client、Egress Client的值，并附至Traced Route字段作为最后一个表项，递减第四消息中的hop count值，生成第二消息；针对承载FlexE Client#c1的物理接口PHY#1，即在PHY#1上发送该携带该第二消息的FlexE开销帧；清除当前记录的hop count、FlexE Group#2、FlexE Client#c2，停止RTR计时器。
STEP 6：FlexE Node#3节点在PHY#4上收到来自FlexE Node#4的第四消息。使用FlexE Group#2和FlexE client#c2查询FlexE时隙交换映射表，查询得到交叉映射的出口为FlexE Group#1和FlexE Client#c1；查询FlexE Group#1所包含的PHY，即FlexE Group#1仅对应PHY#2，即承载FlexE Client#c1的物理接口为PHY#2，则产生一条第二消息，使用Node#3、FlexE组#1+PHY#2+FlexE客户#c1(FlexE Group#1+PHY#2+FlexE Client#c1)和FlexE组#2+PHY#4+FlexE客户#c2(FlexE Group#2+PHY#4+FlexE Client#c2)作为Traced Route表项的3个字段Node ID、Ingress Client、Egress Client的值，并附至Traced Route字段作为最后一个表项，递减第四消息中的hop count值，生成第二消息；针对承载FlexE  Client#c1的物理接口PHY#2，即在PHY#2上发送封装该条RTRR消息的开销帧；清除当前记录的hop count、FlexE Group#2、FlexE Client#c2，停止RTR计时器。
STEP 7：STEP 5、STEP 6中的第二消息传递至远端的网络设备FlexE Node#1的NNI侧的FlexE接口PHY#1和PHY#2；读取消息Op Code字段，为路径探测应答消息，读取2条第二消息的Hop Count字段，发现Hop Count值均为0，终结第二消息。承载FlexE Client#c1的FlexE Group#1只对应2个物理端口PHY#1和PHY#2，已从2个端口都收到第二消息，路径探测终结。Node 1上的FlexE Client#c1的传输路径如图16所示。
本申请实施例以一个FlexE客户由多个PHY承载的场景为例，实施路径发现的流程。可以通过记录FlexE客户在路径节点上的入口信息及出口信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
上述详细阐述了本申请实施例的方法，下面为了便于更好地实施本申请实施例的上述方案，相应地，下面还提供用于配合实施上述方案的相关装置。
请参见图17。图17为本申请实施例提供的一种第一节点的结构示意图。如图17所示，第一节点70至少可以包括：第一接收单元710、第一发送单元720；其中：
第一接收单元710，用于接收第二节点发送的请求查询第一FlexE客户传输路径的第一消息。
第一发送单元720，用于向第二节点发送第二消息。
其中，第二消息包括路径信息表项；路径信息表项包括至少一项路径信息；路径信息包括：第一节点身份信息、第一FlexE客户信息、第一物理接口标识信息、第二FlexE客户信息及第二物理接口标识信息；其中，所述第一FlexE客户信息包括：承载所述第一FlexE客户的第一时隙信息、承载所述第一FlexE客户的第一FlexE组信息；所述第一物理接口标识信息包括承载所述第一FlexE客户的物理接口标识信息；所述第二FlexE客户信息包括：承载第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；所述第二物理接口标识信息包括承载所述第二FlexE客户的物理接口标识信息；承载所述第一FlexE客户的第一时隙与承载所述第二FlexE客户的第二时隙存在交叉关系。
在一个可选的实施例中，第一节点70还包括：查询单元730、第一生成单元740、第二生成单元750；如图18所示，其中：
查询单元730，用于在第一接收单元710接收第二节点发送的查询第一FlexE客户传输路径的第一消息之后，根据第一消息查询时隙交换映射表。
第一生成单元740，用于若通过查询单元730查询时隙交换映射表存在查询结果，则根据第一消息生成第三消息，并向第三节点第三消息。
第二生成单元750，用于若通过查询单元730查询时隙交换映射表不存在查询结果，则根据第一消息生成第二消息。
在一个可选的实施例中，查询单元730用于根据第一消息记录的第一FlexE客户信息查询时隙交换映射表。
在一个可选的实施例中，查询结果包括承载第二FlexE客户第二时隙信息、承载第二FlexE客户的第二FlexE组信息。
第一生成单元720，具体用于根据第一消息生成第三消息，承载所述第二FlexE客户的第二时隙的物理接口上，向第三节点发送第三消息。
在一个可选的实施例中，第三消息中包含路径信息表项；第三消息中的路径表项信息包含第一消息中的路径信息表项以及第一节点70的路径信息；其中，第一节点70的路径信息包括第一FlexE客户信息、承载第一FlexE客户的物理接口的标识信息、第二FlexE客户的信息及承载第二FlexE客户的物理接口标识信息。
在一个可选的实施例中，第一节点70还包括：第三生成单元760；如图18所示：
第三生成单元760，用于在第一生成单元710根据第一消息生成第三消息，并向第三节点发送第三消息之后，若在指定时长内没有接收到第三节点发送的第四消息，则根据第一消息生成第二消息；其中，第四消息中包含路径信息表项；第四消息中的路径信息表项至少包括第三节点的路径信息。
在一个可选的实施例中，第二消息中包含路径信息表项；第二消息中的路径信息表项包含第一消息中的路径信息表项以及第一节点70的路径信息；其中，第一节点70的路径信息包括第一FlexE客户的信息、承载第一FlexE客户的物理接口的标识信息、第二FlexE客户的信息及承载第二FlexE客户的物理接口标识信息。
在一个可选的实施例中，第二生成单元720，具体用于根据第一消息中的路径信息表项生成第二消息；其中，第二消息包含路径信息表项；第二消息中的路径信息表项包含第一消息中的路径信息表项。
在一个可选的实施例中，第一节点70还包括：第二接收单元770、第四生成单元780；如图18所示，其中：
第二接收单元770，用于在第一接收单元710接收第二节点发送的查询第一FlexE客户传输路径第一消息之后，在第一发送单元720向第二节点发送第二消息之前，接收第三节点发送的第四消息；其中，第四消息中包含路径信息表项；第四消息中的路径信息表项至少包括第三节点的路径信息。
第四生成单元780，用于根据第四消息生成第二消息。
在一个可选的实施例中，第二消息包含路径信息表项；第二消息中的路径信息表项包含第四消息中的路径信息表项。
在一个可选的实施例中，第二消息中包含路径信息表项；第二消息中的路径信息表项包含第四消息中的路径信息表项以及第一节点70的路径信息；其中，第一节点70的路径信息包括第一FlexE客户的信息、承载第一FlexE客户的物理接口的标识信息、第二FlexE客户的信息及承载第二FlexE客户的物理接口标识信息。
在一个可选的实施例中，上述第一消息、上述第二消息、上述第三消息及上述第四消息均由至少一个FlexE开销帧承载。
可理解的是，本实施例的第一节点70的各功能模块的功能可根据上述方法实施例中的方法具体实现，此处不再赘述。
实施本申请实施例，可以通过记录FlexE客户在路径节点上的第一FlexE客户信息及 第二FlexE客户信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
请参见图19。图19为本申请实施例提供的一种第二节点的结构示意图。如图19所示，第二节点80至少可以包括：第二发送单元810、第三接收单元820；其中：
第二发送单元810，用于向第一节点70发送请求查询第一FlexE客户传输路径的第一消息。
第三接收单元820，用于接收第一节点70发送的第二消息。
其中，第二消息包括路径信息表项；第二消息中的路径信息表项包括至少一项路径信息；路径信息包括：第一节点身份信息、第一FlexE客户信息、第一物理接口标识信息、第二FlexE客户信息及第二物理接口标识信息；其中，所述第一FlexE客户信息包括：承载所述第一FlexE客户的第一时隙信息、承载所述第一FlexE客户的第一FlexE组信息；所述第一物理接口标识信息包括承载所述第一FlexE客户的物理接口标识信息；所述第二FlexE客户信息包括：承载第二FlexE客户的第二时隙信息、承载所述第二时隙的第二FlexE组信息；所述第二物理接口标识信息包括承载所述第二FlexE客户的物理接口标识信息；承载所述第一FlexE客户的第一时隙与承载所述第二FlexE客户的第二时隙存在交叉关系。
在一个可选的实施例中，上述第一消息、上述第二消息及上述第三消息均由至少一个FlexE开销帧承载。
可理解的是，本实施例的第二节点80的各功能模块的功能可根据上述方法实施例中的方法具体实现，此处不再赘述。
实施本申请实施例，可以通过记录FlexE客户在路径节点上的第一FlexE客户信息及第二FlexE客户信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
请参见图20，图20是本申请实施例提供的一种第一节点90，该第一节点90包括处理器901、存储器902和收发器903，该处理器901、存储器902和收发器903通过总线904相互连接。
存储器902包括但不限于是随机存取存储器(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)或可擦除可编程只读存储器(Erasable Programmable Read-Only Mmory，EPROM或者快闪存储器)，该存储器902用于相关指令及数据。
该收发器903可以包括一个接收器和一个发送器，例如，无线射频模块，以下描述的处理器901接收或者发送某个消息，具体可以理解为该处理器901通过该收发器来接收或者发送。
处理器901可以是一个或多个中央处理器(Central Processing Unit，CPU)，在处理 器901是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
该第一节点90中的处理器901用于读取该存储器902中存储的程序代码，执行以下操作：
处理器901通过收发器903接收第二节点发送的请求查询第一FlexE客户传输路径的第一消息。
处理器901通过收发器903向第二节点发送第二消息。
其中，第二消息包括路径信息表项；第二消息中的路径信息表项包括至少一项路径信息；路径信息包括：第一节点身份信息、第一FlexE客户信息、第一物理接口标识信息、第二FlexE客户信息及第二物理接口标识信息；其中，所述第一FlexE客户信息包括：承载所述第一FlexE客户的第一时隙信息、承载所述第一FlexE客户的第一FlexE组信息；所述第一物理接口标识信息包括承载所述第一FlexE客户的物理接口标识信息；所述第二FlexE客户信息包括：承载第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；所述第二物理接口标识信息包括承载所述第二FlexE客户的物理接口标识信息；承载所述第一FlexE客户的第一时隙与承载所述第二FlexE客户的第二时隙存在交叉关系。
在一个可选的实施例中，第一节点90接收第二节点发送的查询第一FlexE客户传输路径的第一消息之后，处理器901还用于：
根据第一消息查询时隙交换映射表。
若查询时隙交换映射表存在查询结果，则根据第一消息生成第三消息，并向第三节点发送第三消息。
若查询时隙交换映射表不存在查询结果，则根据第一消息生成第二消息。
在一个可选的实施例中，处理器901根据第一消息查询时隙交换映射表包括：
根据第一消息记录的第一FlexE客户的信息查询时隙交换映射表；其中，第一FlexE客户的信息包括传输第一FlexE客户信息的第一时隙及承载第一FlexE客户的第一FlexE组信息。
在一个可选的实施例中，查询结果包括承载第二FlexE客户的第二时隙信息、承载第二FlexE客户的第二FlexE组信息。
处理器901根据第一消息生成第三消息，并向第三节点发送第三消息，包括：
根据第一消息生成第三消息，在承载所述第二FlexE客户的物理接口上，向第三节点发送第三消息。
在一个可选的实施例中，第三消息中包含路径信息表项；第三消息中的路径表项信息包含第一消息中的路径信息表项以及第一节点90的路径信息；其中，第一节点90的路径信息包括第一FlexE客户信息、承载第一FlexE客户的物理接口的标识信息、第二FlexE客户信息及承载第二FlexE客户的物理接口标识信息。
在一个可选的实施例中，处理器901根据第一消息生成第三消息，并向第三节点发送第三消息之后，处理器901还用于：
若在指定时长内没有接收到第三节点发送的第四消息，则根据第一消息生成第二消息；其中，第四消息中包含路径信息表项；第四消息中的路径信息表项至少包括第三节点的路 径信息。
在一个可选的实施例中，第二消息中包含路径信息表项；第二消息中的路径信息表项包含第一消息中的路径信息表项以及第一节点90的路径信息；其中，第一节点90的路径信息包括第一FlexE客户的信息、承载第一FlexE客户的物理接口的标识信息、第二FlexE客户的信息及承载第二FlexE客户的物理接口标识信息。
在一个可选的实施例中，处理器901根据第一消息生成第二消息，包括：
根据第一消息中的路径信息表项生成第二消息；其中，第二消息包含路径信息表项；第二消息中的路径信息表项包含第一消息中的路径信息表项。
在一个可选的实施例中，处理器901接收第二节点发送的查询第一FlexE客户传输路径第一消息之后，处理器901向第二节点发送第二消息之前，处理器901还用于：
接收第三节点发送的第四消息；其中，第四消息中包含路径信息表项；第四消息中的路径信息表项至少包括第三节点的路径信息。
根据第四消息生成第二消息。
在一个可选的实施例中，第二消息中包含路径信息表项；第二消息中的路径信息表项包含第四消息中的路径信息表项。
在一个可选的实施例中，第二消息中包含路径信息表项；第二消息中的路径信息表项包含第四消息中的路径信息表项以及第一节点90的路径信息；其中，第一节点90的路径信息包括第一FlexE客户的信息、承载第一FlexE客户的物理接口的标识信息、第二FlexE客户的信息及承载第二FlexE客户的物理接口标识信息。
在一个可选的实施例中，上述第一消息、上述第二消息、上述第三消息及上述第四消息均由至少一个FlexE开销帧承载。
需要说明的是，各个操作的具体实现还可根据上述方法实施例中的方法具体实现，此处不再赘述。
实施本申请实施例，可以通过记录FlexE客户在路径节点上的第一FlexE客户信息及第二FlexE客户信息，作为每一跳的传输路径，可以实时动态发现FlexE网络段到段的传输路径、比对规划部署的传输路径与实际发现的路径以评估网络的运行情况，还可以检测传输路径上的连接连通性和定位FlexE网络内传输路径上的故障节点。此外，通过FlexE开销帧承载该传输过程中的各个消息，实现带外通信，不占用数据通路的带宽，不影响数据通路的承载效率。
请参见图21，图21是本申请实施例提供的一种第二节点100，该第二节点100应用于灵活以太网FlexE组网网络中，该第二节点100包括处理器1001、存储器1002和收发器1003，该处理器1001、存储器1002和收发器1003通过总线1004相互连接。
存储器1002包括但不限于是随机存取存储器(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)或可擦除可编程只读存储器(Erasable Programmable Read-Only Mmory，EPROM或者快闪存储器)，该存储器1002用于相关指令及数据。
该收发器1003可以包括一个接收器和一个发送器，例如，无线射频模块，以下描述的处理器1001接收或者发送某个消息，具体可以理解为该处理器1001通过该收发器来接收或者发送。
处理器1001可以是一个或多个中央处理器(Central Processing Unit，CPU)，在处理器1001是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
该第二节点100中的处理器1001用于读取该存储器1002中存储的程序代码，执行以下操作：
处理器1001向第一节点90发送请求查询第一FlexE客户传输路径的第一消息。
处理器1001接收第一节点90发送的第二消息。
其中，第二消息包括路径信息表项；第二消息中的路径信息表项包括至少一项路径信息；路径信息包括：第一节点身份信息、第一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客户的第一时隙信息、承载所述第一FlexE客户的第一FlexE组信息；所述第一物理接口标识信息包括承载所述第一FlexE客户的物理接口标识信息；所述第二FlexE客户信息包括：承载第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；所述第二物理接口标识信息包括承载所述第二FlexE客户的物理接口标识信息；承载所述第一FlexE客户的第一时隙与承载所述第二FlexE客户的第二时隙存在交叉关系。
上述计算机可读存储介质可以是前述任一实施例上述的第一节点或第二节点的内部存 储单元，例如第一节点或第二节点的硬盘或内存。上述计算机可读存储介质也可以是上述第一节点或第二节点的外部存储设备，例如上述第一节点或第二节点上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。进一步地，上述计算机可读存储介质还可以既包括上述第一节点或第二节点的内部存储单元也包括外部存储设备。上述计算机可读存储介质用于存储上述计算机程序以及上述第一节点或第二节点所需的其他程序和数据。上述计算机可读存储介质还可以用于暂时地存储已经输出或者将要输出的数据。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。
尽管在此结合各实施例对本申请进行了描述，然而不能以此来限定本申请之权利范围，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现上述实施例的全部或部分流程，并依本申请权利要求所作的等同变化，仍属于申请所涵盖的范围。在权利要求中，“包括”一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个控制器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求所记载了某些措辞，但这并不表示这些措辞不能组合起来产生良好的效果。

Claims (32)

  1. 一种获得目标传输路径的方法，其特征在于，所述方法应用于灵活以太网FlexE组网网络中，所述方法包括：
    第一节点接收第二节点发送的请求查询第一FlexE客户传输路径的第一消息；
    所述第一节点向所述第二节点发送第二消息；
    其中，所述第二消息包括路径信息表项；所述路径信息表项包括至少一项路径信息；所述路径信息包括：所述第一节点身份信息、第一FlexE客户信息、第一物理接口标识信息、第二FlexE客户信息及第二物理接口标识信息；其中，所述第一FlexE客户信息包括：承载所述第一FlexE客户的第一时隙信息、承载所述第一FlexE客户的第一FlexE组信息；所述第一物理接口标识信息包括承载所述第一FlexE客户的物理接口标识信息；所述第二FlexE客户信息包括：承载所述第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；所述第二物理接口标识信息包括承载所述第二FlexE客户的物理接口标识信息；承载所述第一FlexE客户的第一时隙与承载所述第二FlexE客户的第二时隙存在交叉关系。
  2. 如权利要求1所述的方法，其特征在于，所述第一节点接收第二节点发送的查询第一FlexE客户传输路径的第一消息之后，所述方法还包括：
    根据所述第一消息查询时隙交换映射表；
    若查询所述时隙交换映射表存在查询结果，则根据所述第一消息生成第三消息，并向第三节点发送所述第三消息；
    若查询所述时隙交换映射表不存在查询结果，则根据所述第一消息生成第二消息。
  3. 如权利要求2所述的方法，其特征在于，所述根据所述第一消息查询时隙交换映射表包括：
    根据所述第一消息记录的所述第一FlexE客户信息查询时隙交换映射表。
  4. 如权利要求3所述的方法，其特征在于，所述查询结果包括承载所述第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；
    所述根据所述第一消息生成第三消息，并向第三节点发送所述第三消息，包括：
    根据所述第一消息生成第三消息，在承载所述第二FlexE客户的物理接口上，向第三节点发送所述第三消息。
  5. 如权利要求4所述的方法，其特征在于，所述第三消息中包含路径信息表项；所述路径表项信息包含所述第一消息中的路径信息表项以及所述第一节点的路径信息；其中，所述第一节点的路径信息包括所述第一FlexE客户信息、承载所述第一FlexE客户的物理接口的标识信息、所述第二FlexE客户信息及承载所述第二FlexE客户的物理接口标识信息。
  6. 如权利要求4所述的方法，其特征在于，所述根据所述第一消息生成第三消息，并向第三节点发送所述第三消息之后，所述方法还包括：
    若在指定时长内没有接收到所述第三节点发送的第四消息，则根据所述第一消息生成所述第二消息；其中，所述第四消息中包含路径信息表项；所述路径信息表项至少包括所述第三节点的路径信息。
  7. 如权利要求6所述的方法，其特征在于，所述第二消息中包含路径信息表项；所述路径信息表项包含所述第一消息中的路径信息表项以及所述第一节点的路径信息；其中，所述第一节点的路径信息包括所述第一FlexE客户的信息、承载所述第一FlexE客户的物理接口的标识信息、所述第二FlexE客户的信息及承载所述第二FlexE客户的物理接口标识信息。
  8. 如权利要求2所述的方法，其特征在于，所述根据所述第一消息生成所述第二消息，包括：
    根据所述第一消息中的路径信息表项生成所述第二消息；其中，所述第二消息包含路径信息表项；所述路径信息表项包含所述第一消息中的路径信息表项。
  9. 如权利要求1所述的方法，其特征在于，所述第一节点接收第二节点发送的查询第一FlexE客户传输路径第一消息之后，所述第一节点向所述第二节点发送第二消息之前，所述方法还包括：
    接收第三节点发送的第四消息；其中，所述第四消息中包含路径信息表项；所述路径信息表项至少包括所述第三节点的路径信息；
    根据所述第四消息生成所述第二消息。
  10. 如权利要求9所述的方法，其特征在于，所述第二消息包含路径信息表项；所述路径信息表项包含所述第四消息中的路径信息表项。
  11. 如权利要求9所述的方法，其特征在于，所述第二消息中包含路径信息表项；所述路径信息表项包含所述第四消息中的路径信息表项以及所述第一节点的路径信息；其中，所述第一节点的路径信息包括所述第一FlexE客户的信息、承载所述第一FlexE客户的物理接口的标识信息、所述第二FlexE客户的信息及承载所述第二FlexE客户的物理接口标识信息。
  12. 如权利要求1-11所述的方法，其特征在于，所述第一消息、所述第二消息、所述第三消息及所述第四消息均由至少一个FlexE开销帧承载。
  13. 一种获得目标传输路径的方法，其特征在于，所述方法应用于灵活以太网FlexE 组网网络中，所述方法包括：
    第二节点向第一节点发送请求查询第一FlexE客户传输路径的第一消息；
    所述第二节点接收所述第一节点发送的第二消息；
    其中，所述第二消息包括路径信息表项；所述路径信息表项包括至少一项路径信息；所述路径信息包括：所述第一节点身份信息、第一FlexE客户信息、第一物理接口标识信息、第二FlexE客户信息及第二物理接口标识信息；其中，所述第一FlexE客户信息包括：承载所述第一FlexE客户的第一时隙信息、承载所述第一FlexE客户的第一FlexE组信息；所述第一物理接口标识信息包括承载所述第一FlexE客户的物理接口标识信息；所述第二FlexE客户信息包括：承载所述第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；所述第二物理接口标识信息包括承载所述第二FlexE客户的物理接口标识信息；承载所述第一FlexE客户的第一时隙与承载所述第二FlexE客户的第二时隙存在交叉关系。
  14. 如权利要求13所述的方法，其特征在于，所述第一消息及所述第二消息均由至少一个FlexE开销帧承载。
  15. 一种第一节点，其特征在于，所述第一节点应用于灵活以太网FlexE组网网络中，所述第一节点包括：
    第一接收单元，用于接收第二节点发送的请求查询第一FlexE客户传输路径的第一消息；
    第一发送单元，用于向所述第二节点发送第二消息；
    其中，所述第二消息包括路径信息表项；所述路径信息表项包括至少一项路径信息；所述路径信息包括：所述第一节点身份信息、第一FlexE客户信息、第一物理接口标识信息、第二FlexE客户信息及第二物理接口标识信息；其中，所述第一FlexE客户信息包括：承载所述第一FlexE客户的第一时隙信息、承载所述第一FlexE客户的第一FlexE组信息；所述第一物理接口标识信息包括承载所述第一FlexE客户的物理接口标识信息；所述第二FlexE客户信息包括：承载所述第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；所述第二物理接口标识信息包括承载所述第二FlexE客户的物理接口标识信息；承载所述第一FlexE客户的第一时隙与承载所述第二FlexE客户的第二时隙存在交叉关系。
  16. 如权利要求15所述的第一节点，其特征在于，所述第一节点还包括：
    查询单元，用于在所述第一接收单元接收第二节点发送的查询第一FlexE客户传输路径的第一消息之后，根据所述第一消息查询时隙交换映射表；
    第一生成单元，用于若通过所述查询单元查询所述时隙交换映射表存在查询结果，则根据所述第一消息生成第三消息，并向第三节点发送所述第三消息；
    第二生成单元，用于若通过所述查询单元查询所述时隙交换映射表不存在查询结果，则根据所述第一消息生成第二消息。
  17. 如权利要求16所述的第一节点，其特征在于，所述查询单元用于：根据所述第一消息记录的所述第一FlexE客户信息查询时隙交换映射表。
  18. 如权利要求17所述的第一节点，其特征在于，所述查询结果包括承载所述第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；
    所述第一生成单元用于：根据所述第一消息生成第三消息，在承载所述第二FlexE客户的物理接口上，向第三节点发送所述第三消息。
  19. 如权利要求18所述的第一节点，其特征在于，所述第三消息中包含路径信息表项；所述路径表项信息包含所述第一消息中的路径信息表项以及所述第一节点的路径信息；其中，所述第一节点的路径信息包括所述第一FlexE客户信息、承载所述第一FlexE客户的物理接口的标识信息、所述第二FlexE客户信息及承载所述第二FlexE客户的物理接口标识信息。
  20. 如权利要求18所述的第一节点，其特征在于，所述第一节点还包括:
    第三生成单元，用于在所述第一生成单元根据所述第一消息生成第三消息，并向第三节点发送所述第三消息之后，若在指定时长内没有接收到所述第三节点发送的第四消息，则根据所述第一消息生成所述第二消息；其中，所述第四消息中包含路径信息表项；所述路径信息表项至少包括所述第三节点的路径信息。
  21. 如权利要求20所述的第一节点，其特征在于，所述第二消息中包含路径信息表项；所述路径信息表项包含所述第一消息中的路径信息表项以及所述第一节点的路径信息；其中，所述第一节点的路径信息包括所述第一FlexE客户的信息、承载所述第一FlexE客户的物理接口的标识信息、所述第二FlexE客户的信息及承载所述第二FlexE客户的物理接口标识信息。
  22. 如权利要求16所述的第一节点，其特征在于，所述第二生成单元用于：根据所述第一消息中的路径信息表项生成所述第二消息；其中，所述第二消息包含路径信息表项；所述路径信息表项包含所述第一消息中的路径信息表项。
  23. 如权利要求15所述的第一节点，其特征在于，所述第一节点还包括：
    第二接收单元，用于在所述第一接收单元接收第二节点发送的查询第一FlexE客户传输路径第一消息之后，在所述第一发送单元向所述第二节点发送第二消息之前，接收第三节点发送的第四消息；其中，所述第四消息中包含路径信息表项；所述路径信息表项至少包括所述第三节点的路径信息；
    第四生成单元，用于根据所述第四消息生成所述第二消息。
  24. 如权利要求23所述的第一节点，其特征在于，所述第二消息包含路径信息表项；所述路径信息表项包含所述第四消息中的路径信息表项。
  25. 如权利要求23所述的第一节点，其特征在于，所述第二消息中包含路径信息表项；所述路径信息表项包含所述第四消息中的路径信息表项以及所述第一节点的路径信息；其中，所述第一节点的路径信息包括所述第一FlexE客户的信息、承载所述第一FlexE客户的物理接口的标识信息、所述第二FlexE客户的信息及承载所述第二FlexE客户的物理接口标识信息。
  26. 如权利要求15-25所述的第一节点，其特征在于，所述第一消息、所述第二消息、所述第三消息及所述第四消息均由至少一个FlexE开销帧承载。
  27. 一种第二节点，其特征在于，所述第二节点应用于灵活以太网FlexE组网网络中，所述第二节点包括：
    第二发送单元，用于向第一节点发送请求查询第一FlexE客户传输路径的第一消息；
    第三接收单元，用于接收所述第一节点发送的第二消息；
    其中，所述第二消息包括路径信息表项；所述路径信息表项包括至少一项路径信息；所述路径信息包括：所述第一节点身份信息、第一FlexE客户信息、第一物理接口标识信息、第二FlexE客户信息及第二物理接口标识信息；其中，所述第一FlexE客户信息包括：承载所述第一FlexE客户的第一时隙信息、承载所述第一FlexE客户的第一FlexE组信息；所述第一物理接口标识信息包括承载所述第一FlexE客户的物理接口标识信息；所述第二FlexE客户信息包括：承载所述第二FlexE客户的第二时隙信息、承载所述第二FlexE客户的第二FlexE组信息；所述第二物理接口标识信息包括承载所述第二FlexE客户的物理接口标识信息；承载所述第一FlexE客户的第一时隙与承载所述第二FlexE客户的第二时隙存在交叉关系。
  28. 如权利要求27所述的第二节点，其特征在于，所述第一消息及所述第二消息均由至少一个FlexE开销帧承载。
  29. 一种第一节点，其特征在于，所述第一节点应用于灵活以太网FlexE组网网络中，所述第一节点包括：处理器、存储器和收发器，其中：
    所述处理器、所述存储器和所述收发器相互连接，所述存储器用于存储计算机程序，所述计算机程序包括程序指令，所述处理器被配置用于调用所述程序指令，执行如权利要求1至12任意一项所述的方法。
  30. 一种第二节点，其特征在于，所述第二节点应用于灵活以太网FlexE组网网络中，所述第二节点包括：处理器、存储器和收发器，其中：
    所述处理器、所述存储器和所述收发器相互连接，所述存储器用于存储计算机程序， 所述计算机程序包括程序指令，所述处理器被配置用于调用所述程序指令，执行如权利要求13或14所述的方法。
  31. 一种通信系统，其特征在于，包括第一节点及第二节点；所述第一节点为权利要求15至26任意一项所述的第一节点，所述第二节点为权利要求27或28所述的第二节点。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时，使所述处理器执行如权利要求1至14任意一项所述的方法。
PCT/CN2018/111811 2017-10-31 2018-10-25 获得目标传输路径的方法、相关设备及系统 WO2019085809A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18873491.7A EP3694153B1 (en) 2017-10-31 2018-10-25 Method, relevant device and system for acquiring a target transmission path
JP2020523980A JP7026788B2 (ja) 2017-10-31 2018-10-25 ターゲット伝送ルートを取得するための方法、関連デバイス、およびシステム
US16/860,777 US11171860B2 (en) 2017-10-31 2020-04-28 Method for obtaining target transmission route, related device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711051321.4 2017-10-31
CN201711051321.4A CN109728968B (zh) 2017-10-31 2017-10-31 获得目标传输路径的方法、相关设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/860,777 Continuation US11171860B2 (en) 2017-10-31 2020-04-28 Method for obtaining target transmission route, related device, and system

Publications (1)

Publication Number Publication Date
WO2019085809A1 true WO2019085809A1 (zh) 2019-05-09

Family

ID=66293258

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/111811 WO2019085809A1 (zh) 2017-10-31 2018-10-25 获得目标传输路径的方法、相关设备及系统

Country Status (5)

Country Link
US (1) US11171860B2 (zh)
EP (1) EP3694153B1 (zh)
JP (1) JP7026788B2 (zh)
CN (1) CN109728968B (zh)
WO (1) WO2019085809A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109818704B (zh) * 2017-11-21 2020-05-19 华为技术有限公司 数据传输方法和设备
CN110502426A (zh) * 2019-07-08 2019-11-26 中国工商银行股份有限公司 分布式数据处理系统的测试方法和装置
CN113111029B (zh) * 2021-04-14 2024-03-26 广州希姆半导体科技有限公司 一种确定数据传输路径的方法、芯片和存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106803814A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种灵活以太网路径的建立方法、装置及系统
CN106803811A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种路由信息的获取方法及装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4954947B2 (ja) 2008-06-23 2012-06-20 富士通株式会社 経路情報変換機能を有するノード装置
CN101702637B (zh) * 2009-10-30 2015-01-28 中兴通讯股份有限公司 时隙交叉方法和系统
US9510347B2 (en) * 2014-05-08 2016-11-29 Cisco Technology, Inc. Timeslot distribution in a distributed routing protocol for deterministic wireless networks
US10193688B2 (en) * 2015-12-11 2019-01-29 Ciena Corporation Flexible Ethernet encryption systems and methods
US9800361B2 (en) * 2015-06-30 2017-10-24 Ciena Corporation Flexible ethernet switching systems and methods
US10135760B2 (en) * 2015-06-30 2018-11-20 Ciena Corporation Flexible Ethernet chip-to-chip inteface systems and methods
US10218823B2 (en) * 2015-06-30 2019-02-26 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
US10097480B2 (en) * 2015-09-29 2018-10-09 Ciena Corporation Time transfer systems and methods over flexible ethernet
CN106330630B (zh) * 2015-07-03 2019-09-03 华为技术有限公司 传输灵活以太网的数据流的方法、发射机和接收机
WO2017070851A1 (en) * 2015-10-27 2017-05-04 Zte Corporation Channelization for flexible ethernet
CN107204941A (zh) * 2016-03-18 2017-09-26 中兴通讯股份有限公司 一种灵活以太网路径建立的方法和装置
US10505655B2 (en) * 2016-07-07 2019-12-10 Infinera Corp. FlexE GMPLS signaling extensions
US10333614B2 (en) * 2016-10-11 2019-06-25 Ciena Corporation Partial survivability for multi-carrier and multi-module optical interfaces
US10382167B2 (en) * 2016-12-13 2019-08-13 Ciena Corporation Flexible ethernet enhanced forward error correction
CN108965157B (zh) * 2017-05-19 2020-08-07 华为技术有限公司 数据传输方法、装置、设备及系统
CN109391461B (zh) * 2017-08-11 2021-08-13 华为技术有限公司 透传业务频率的方法和设备
EP3729734B1 (en) * 2017-12-22 2022-05-18 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for configuring a flex ethernet node

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106803814A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种灵活以太网路径的建立方法、装置及系统
CN106803811A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种路由信息的获取方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
See also references of EP3694153A4 *
VILALTA, R. ET AL.: "Network Slicing Using Dynamic Flex Ethernet; over Transport Networks", 2017 EUROPEAN CONFERENCE ON OPTICAL COMMUNICATION, 21 September 2017 (2017-09-21), XP033336438 *
WANG, Q. ET AL.: "RSVP-TE Signaling Extensions in Support Of Flexible Ethernet Networks", INTERNET ENGINEERING TASK FORCE, 8 July 2016 (2016-07-08), pages 1 - 13, XP015114107 *

Also Published As

Publication number Publication date
EP3694153A1 (en) 2020-08-12
US11171860B2 (en) 2021-11-09
US20200259734A1 (en) 2020-08-13
CN109728968A (zh) 2019-05-07
EP3694153A4 (en) 2020-10-28
JP2021501519A (ja) 2021-01-14
EP3694153B1 (en) 2023-07-26
CN109728968B (zh) 2022-01-14
JP7026788B2 (ja) 2022-02-28

Similar Documents

Publication Publication Date Title
US10341748B2 (en) Packet-optical in-band telemetry (POINT) framework
TWI455501B (zh) 用以延伸乙太網路被動光學網路（ｅｐｏｎ）中之媒體存取控制（ｍａｃ）控制訊息的設備
EP2884697B1 (en) Measuring method, device and system for network packet loss
US9450846B1 (en) System and method for tracking packets in a network environment
US7830809B2 (en) Methods and apparatus for characterizing a route in a fibre channel fabric
US6772267B2 (en) Multi-portal bridge for providing network connectivity
KR102342286B1 (ko) Dcn 메시지 처리 방법, 네트워크 디바이스, 및 네트워크 시스템
CN106850466A (zh) 一种时间触发网络中数据包的转发方法及装置
US11271668B2 (en) Data transmission methods, apparatuses, devices, and system
US10063335B2 (en) Method, apparatus and system for remotely configuring PTP service of optical network unit
US20190222442A1 (en) In-band Telemetry with Limited Extra Bytes
US11171860B2 (en) Method for obtaining target transmission route, related device, and system
CN114465946B (zh) 获取转发表项的方法、装置以及系统
CN109391494B (zh) 一种通信方法、设备及可读存储介质
WO2019029419A1 (zh) 透传业务频率的方法和设备
CN106385344A (zh) 一种报文监控方法和装置
WO2015161736A1 (zh) 一种指示组播转发表项的方法及设备
CN113055293A (zh) 软件定义广域网中的选路方法及装置、通信系统
US20090109966A1 (en) Method and apparatus for performing synchronous time division switch, and ethernet switch
US9112772B2 (en) OLT and frame transfer control method
WO2022121638A1 (zh) 一种报文处理方法及装置
CN107835109B (zh) 一种测试软件定义的分组传送网网络的方法及系统
CN116938775A (zh) 网络性能的测量方法、通信装置及计算机可读存储介质
JP2000032058A (ja) 高効率パケットデ―タ伝送ネットワ―クおよびそれに用いられるインタフェ―ス
CN102098219A (zh) 承载点到多点伪线业务的方法和装置

Legal Events

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

Ref document number: 18873491

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020523980

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018873491

Country of ref document: EP

Effective date: 20200505