WO2019076046A1 - Procédé, appareil et dispositif de configuration de voie de transmission - Google Patents

Procédé, appareil et dispositif de configuration de voie de transmission Download PDF

Info

Publication number
WO2019076046A1
WO2019076046A1 PCT/CN2018/087947 CN2018087947W WO2019076046A1 WO 2019076046 A1 WO2019076046 A1 WO 2019076046A1 CN 2018087947 W CN2018087947 W CN 2018087947W WO 2019076046 A1 WO2019076046 A1 WO 2019076046A1
Authority
WO
WIPO (PCT)
Prior art keywords
node device
label
phy
packet
group
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/087947
Other languages
English (en)
Chinese (zh)
Inventor
杜宗鹏
陈国义
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2019076046A1 publication Critical patent/WO2019076046A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a transmission path configuration method, apparatus, and device.
  • Flex Ethernet (FlexE) technology is an interface technology that adds an intermediation layer between the Media Access Control (MAC) layer and the physical layer (PHY).
  • This interposer can be referred to as the FlexE shim layer.
  • the FlexE shim layer is used to divide each PHY link into X scheduling granularities, the X being an integer greater than one, where the size of each scheduling granularity is 1/X of the total bandwidth of the PHY link.
  • the FlexE shim layer also divides the data to be transmitted of the MAC layer into a plurality of data blocks, and allocates and transmits the divided data blocks in order of scheduling granularity, so that the transmission bandwidth of each data block can be strictly guaranteed.
  • 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 message of the FlexE client is a MAC layer rate based Ethernet stream, and the MAC layer rate may be equal to or less than the PHY rate.
  • the receiving end FlexE device obtains data sent by the transmitting end FlexE device from the time slot corresponding to the FlexE client to recover the packet.
  • FlexE technology can strictly control the characteristics of data transmission bandwidth.
  • IP Internet Protocol
  • Ethernet networks in order to ensure the quality of service (QoS) of service data, it can be used.
  • the FlexE transmission path carries the transmission of service data.
  • the FlexE transmission path is a transmission path formed by a multi-hop FlexE interface connection, that is, the transmission port and the receiving port of each node in the transmission path are configured as a FlexE interface.
  • the FlexE interface and the receiving end FlexE interface of the same FlexE transmission path need to meet certain rules, and the FlexE transmission path can normally transmit data.
  • the currently used FlexE interface configuration method is manually configured, so that not only the configuration efficiency is low, but also the error rate is high.
  • the embodiment of the invention provides a method, a device and a device for configuring a transmission path, so as to solve the problem that the configuration of the existing configuration mode is low in efficiency and high in error rate.
  • an embodiment of the present invention provides a transmission path configuration method, where the method includes:
  • the first node device receives the first packet sent by the second node device by using each of the N physical links, where the first packet includes a priority parameter of the second node device and a device identifier of the second node device
  • the first node device and the second node device include N physical links, where N is an integer greater than or equal to 1, and the first node devices include N first ports and one N physical links.
  • the N second ports included in the second node device are connected to the N physical links one-to-one;
  • the first node device determines that the priority of the first node device is higher than the priority of the second node device according to the priority parameter of the second node device in the first packet and the device identifier of the second node device, the first node The device determines a first set of labels and a first PHY label for each of the N first ports, wherein the first set of labels is used to indicate a first PHY of each of the N first ports
  • the labels belong to the same flexible Ethernet FlexE group, and the first PHY label of each of the N first ports is unique in the FlexE group;
  • the first node device sends a second packet to the second node device via each of the N physical links, where the second packet includes the first group of labels, and each of the N physical links a first PHY label of the first port corresponding to the link, where the second packet is used to trigger the second node device to determine, according to the second packet, the second group label and each of the second ports Second physical layer PHY label.
  • the second node device sends the priority parameter of the second node device and the device identifier of the second node device to the first node device by using the first packet, so that the first node device can be according to the second
  • the priority parameter of the node device and the device identifier of the second node device determine whether the priority of the first node device is higher than the priority of the second node device.
  • the first node device determines a first group label, and a first physical layer PHY label of each of the N first ports, That is, the first node device configures the N physical links with the ports of the local end as a FlexE interface.
  • the first node device adds the first group label, and the first PHY label of each of the N first ports to the second packet, and sends the second packet to the second node. device.
  • the second node device After receiving the second packet, the second node device reads the first group label and the N PHY labels, and determines a second group label and a second PHY label of each of the N second ports, ie, The second node device configures the N physical links with the local port as a FlexE interface. It can be seen that the two nodes connected to each other in the solution are configured with the label of each port of the local end, and the port of the local end is configured as a FlexE interface. Then, the peer node device is configured according to the port of the local node device. The label is a label for the corresponding port of the peer node device. The port of the peer node device is configured as a FlexE interface. The automatic configuration of the FlexE interface can improve the configuration efficiency and ensure the correct configuration rate.
  • the first node device and the second node device further include M physical links, where M is an integer greater than or equal to 1, the first node The M third ports of the device are connected to the M physical links one by one, and the M fourth ports of the second node device are connected to the M physical links one by one; when the first node device has a high priority When the priority of the second node device is used, the method further includes:
  • the first node device determines a third physical layer PHY label of the third group label and each of the M third ports, wherein the third group label is used to indicate each of the M third ports
  • the third PHY label of the port belongs to the same FlexE group, and the third PHY label of each third port of the M third ports is unique in the FlexE group;
  • the first node device sends a third packet to the second node device via each of the M physical links, the third packet includes a third group of labels, and each physical medium of the M physical links a third PHY label of the third port corresponding to the link, where the third packet is used to trigger the second node device to determine, according to the third packet, the fourth group label and each of the fourth port ports.
  • the fourth physical layer PHY number is used to trigger the second node device to determine, according to the third packet, the fourth group label and each of the fourth port ports.
  • the M physical links may be bound to obtain two FlexE groups.
  • the M physical links may be independent of the N physical links, that is, the first node device and the second node device include at least M+N physical links, and may also include N physical links. Part of the link. Since the logical function of a FlexE group is a virtual transmission link, the embodiment of the present invention can flexibly bind the FlexE group by using the implementation manner, so that the paths of different transmission rates and different transmission bandwidths can be flexibly configured, and thus, The solution can adapt to a variety of options and has wide applicability.
  • the first node device determines the first node device according to the priority parameter of the second node device in the first packet and the device identifier of the second node device The priority of the device is higher than the priority of the second node device, including:
  • the first node device compares whether the priority parameter of the first node device is smaller than the priority parameter of the second node device
  • the first node device determines that the priority of the first node device is higher than the priority of the second node device.
  • the priority parameter is a preset binary value, which is used to indicate the priority of the peer node device and the local node device.
  • the first node device reads the priority parameter of the local end, and then compares with the priority parameter of the second node device. For example, in this embodiment, the smaller the priority parameter is, the higher the priority is. If the priority parameter of the first node device is smaller than the priority parameter of the second node device, the priority of the first node device is higher. The priority of the second node device. It can be seen that, in this implementation manner, the two connected node devices can be provided with the determining conditions for actively initiating the configuration, thereby providing the first trigger condition for the implementation of the solution.
  • the first node device compares the device identifier of the first node device Whether it is smaller than the device identifier of the second node device;
  • the first node device determines that the priority of the first node device is higher than the priority of the second node device.
  • the priority parameter of the node device may not be set. If the priority parameter of the node device is not set, the default value may be defaulted. Based on this, if the priority parameter of the first node device and the priority parameter of the second node device are not set, the priority parameters of the first node device and the second node device are both default values, then the first node The device has the same priority as the second node device.
  • the first node device can read the device identifier of the local device, and determine whether the device identifier of the local device is smaller than the device identifier of the second node device, and if the device identifier of the local device is smaller than the device identifier of the second node device, The priority is higher than the priority of the second node device.
  • the device identifier may be any specific identifier of the corresponding node device. Because the specific identifier of the node device is unique, the device identifier of the first node device and the device identifier of the second node device are inevitably different, so that it can be clear Determine the priority of the two node devices, and then fully prepare for the automatic configuration of the FlexE transmission path.
  • the first packet further includes a group label that is occupied by the second node device and a PHY label that is occupied by the second node device, and determines the first group label and a first PHY label of each of the N first ports, including:
  • the first node device reads the group label that the second node device has occupied and the PHY label that the second node device has occupied;
  • the first node device determines a group label different from the group label already occupied by the second node device as the first group label, and the first node device determines the PHY label different from the PHY label occupied by the second node device as N A first PHY label for each of the first ports.
  • each node needs to be configured as a FlexE interface by connecting two groups of ports connecting its upstream node and its downstream node. Because the two ports of the same node belong to different FlexE transmission paths, the labels of the two groups are the same as the labels of different FlexE interfaces. Therefore, the labels of the two groups are likely to appear. The same PHY label and the same group label may result in inconvenient data management. Based on this, the second node device may further add the occupied PHY label and the occupied group label in the first packet.
  • the first node device configures a group label different from the occupied group label as the first group label, and configures a PHY label different from the occupied PHY label as any one of the N first PHY labels, thereby avoiding the same
  • the different ports of the node device use the same label, which in turn makes the solution more perfect.
  • the first packet further includes a line card number of the second node device connected to each physical link of the N physical links, the first node The device determines the first physical layer PHY label of the first group label and each of the N first ports, and specifically includes:
  • the first node device determines, in the first packet, the S physical links of the second node device that have the same line card card number, where S is less than or equal to N;
  • the first node device determines that the line card number of the first node device corresponding to the S physical links is the same;
  • the first node device sends the second packet to the second node device by using each of the N physical links, where the first node device sends the first physical link to each of the S physical links.
  • the second node sends a second packet, where the second packet includes a first group of labels, and a first PHY label of the first port corresponding to each physical link of the S physical links, where the second packet And a second physical layer PHY label for triggering the second node device to determine, according to the second packet, the second group label and each of the second ports.
  • the S physical links may be used. Bind to a FlexE group. Where S is greater than or equal to 1 and less than or equal to N.
  • the S physical links may be bound to S FlexE groups, that is, each physical link in the S physical links may be Bind to a FlexE group.
  • the S-i physical links in the S physical links are bound to the first FlexE group, and the remaining i physical links are bound to the second FlexE group. Where i is greater than or equal to 1 and less than S. It can be seen that the solution can provide multiple solutions for binding the FlexE group, so that the paths of different transmission rates and different transmission bandwidths can be flexibly configured, thereby enabling the solution to adapt to multiple solutions and having wide applicability.
  • the first packet is a link layer discovery protocol (LLDP) packet
  • the LLDP packet carries the priority parameter of the second node device and the second The device ID of the node device.
  • the first node device and the second node device run the link layer discovery protocol (LLDP), and the LLDP protocol carries the LLDP packet.
  • the traditional LLDP packet does not include the device information of the node device.
  • the second node device may add an extension field to the LLDP packet, and carry the device information in the added extension field to obtain the first packet.
  • the extension field is a new sub-type of a dedicated extension of the Optical Internetworking Forum (OIF), or the extension field is a new type length value (type, length, value, TLV). )Types of. Therefore, an execution basis is provided for determining a node device with a higher priority, and thus an information foundation is provided for the implementation of the solution.
  • the extension field further carries the PHY label that the second node device has occupied and the group label that the second node device has occupied.
  • the second node device uses the PHY label occupied by the second node device and the group occupied by the second node device.
  • the label is carried in the extension field, so that different ports of the same node device can be prevented from using the same label, and thus the scheme is more perfect.
  • the second packet is an LLDP packet, where the LLDP packet carries the first group label through a fixed field of the FlexE overhead frame, and the N physical links The first PHY label of the first port corresponding to each physical link in the medium.
  • the data transmission mode may be switched to the FlexE mode, and then the first PHY label and the first group label are carried in the FlexE overhead frame (flex Ethernet overhead frame).
  • the FlexE overhead frame Flex Ethernet overhead frame
  • the second message is obtained.
  • the first node device schedules and encapsulates the data block corresponding to the Ethernet data packet according to the mode specified by the transmission protocol of the FlexE, and sends the data block to the PHY link, and the second node device can receive the data block, and according to the schedule (Calendar) Recovery of Ethernet data packets. Therefore, the LLDP packet can be directly used for data transmission without further extension of the LLDP protocol.
  • the embodiment of the present invention further provides a transmission path configuration method, where the method includes:
  • the second node device sends a first packet to the first node device by using each physical link of the N physical links, where the first packet includes a priority parameter of the second node device and a device identifier of the second node device, where a message is used to trigger the first node device to determine that the priority of the first node device is higher than the priority of the second node device according to the priority parameter of the second node device in the first packet and the device identifier of the second node device.
  • the second node device and the first node device include N physical links, where N is an integer greater than or equal to 1, and the N first ports included in the first node device are connected to the N physical links one-to-one.
  • the N second ports included in the second node device are connected to the N physical links one-to-one;
  • the second node device receives the second packet sent by the first node device by using each of the N physical links, where the second packet includes the first group of labels, and each of the N physical links a first PHY label of the first port corresponding to the physical link, where the first group label is used to indicate that the first PHY labels of each of the N first ports belong to the same flexible Ethernet FlexE group.
  • the first PHY label of each of the N first ports is unique among the FlexE groups;
  • the second node Determining, by the second node, the second physical layer PHY label of the second group label and each of the N second ports according to the second packet, where the second group label is used to indicate the N second ports
  • the second physical layer PHY label for each second port belongs to the FlexE group, and the second PHY label for each of the N second ports is unique among the FlexE groups.
  • the second node device and the first node device further include M physical links, where M is an integer greater than or equal to 1, the first node The M third ports of the device are connected to the M physical links one by one, and the M fourth ports of the second node device are connected to the M physical links one by one; when the first node device has a high priority
  • the method further includes:
  • the second node device receives the third packet sent by the first node device, where the third packet includes a third group label, and a third PHY label of the third port corresponding to each physical link of the M physical links.
  • the third group of labels is used to indicate that the third PHY labels of each of the three third ports belong to the same FlexE group, and the third PHY of each of the M third ports The label is unique in the FlexE group;
  • the second node device determines, according to the third packet, a fourth physical layer PHY label of the fourth group label and each of the M fourth ports, where the fourth group label is used to indicate the M fourth ports.
  • the fourth physical layer PHY label for each fourth port belongs to the FlexE group, and the fourth physical layer PHY label for each of the M fourth ports is unique among the FlexE groups.
  • the first packet further includes a line card number of the second node device to which each physical link of the N physical links is connected.
  • the second node device adds an extension field in the link layer discovery protocol LLDP packet to obtain the first packet, where the extension field carries the second node.
  • the priority parameter of the device and the device identifier of the second node device is not limited to the second node device.
  • the extension field further carries the PHY label that the second node device has occupied and the group label that the second node device has occupied.
  • the second packet is an LLDP packet
  • the LLDP packet carries the first group label through a fixed field of the FlexE overhead frame, and the N physical links The first PHY label of the first port corresponding to each physical link in the medium.
  • the second aspect and the second possible implementation manners of the second aspect protect the implementation corresponding to the first aspect and the possible implementation manner of the first aspect. Therefore, each implementation of the second aspect and the second aspect
  • the technical effects produced by the method are the same as those of the first aspect and the corresponding implementation of the first aspect, and are not described herein again in the embodiments of the present invention.
  • an embodiment of the present invention further provides a transmission path configuration apparatus, where the apparatus is disposed in a first node device, and includes a module for performing the method steps in the first aspect and the implementation manners of the first aspect.
  • an embodiment of the present invention further provides a transmission path configuration apparatus, where the apparatus is disposed in a second node device, and includes a module for performing the method steps in the implementation manners of the second aspect and the second aspect.
  • an embodiment of the present invention provides a node device, including a transceiver, a processor, and a memory.
  • the transceiver, the processor and the memory can be connected by a bus system.
  • the memory is for storing a program, instruction or code
  • the processor is for executing a program, instruction or code in the memory, completing the first aspect, or the method of any one of the possible aspects of the first aspect.
  • an embodiment of the present invention further provides a node device, including a transceiver, a processor, and a memory.
  • the transceiver, the processor and the memory can be connected by a bus system.
  • the memory is for storing a program, instruction or code
  • the processor is for executing a program, instruction or code in the memory, completing the second aspect, or the method of any one of the possible aspects of the second aspect.
  • an embodiment of the present invention provides a computer readable storage medium, where the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform the first aspect, the second aspect, and the first aspect.
  • the first node device and the second node device include N physical links, where N is an integer greater than or equal to 1, and the first node device includes N first The port is connected to the N physical links one by one, and the N second ports included in the second node device are connected to the N physical links one-to-one.
  • the first node device determines a first PHY label of the first group label and each of the N first ports, and N The first port is configured as a FlexE interface.
  • the second node device determines, according to the first group label and the N first PHY labels, the second group label and the second PHY label of each of the N second ports, and configures the N second ports For the FlexE interface.
  • the node device at one end is configured with a label for each port of the local end, and the port of the local end is configured as a FlexE interface
  • the peer node device is configured according to the local node device.
  • the label of the port is configured with the label of the corresponding port of the peer node device.
  • the port of the peer node device is configured as a FlexE interface.
  • the automatic configuration of the FlexE interface can improve the configuration efficiency and ensure the correct configuration rate.
  • FIG. 1 is a schematic diagram of a FlexE transmission path according to an embodiment of the present invention.
  • FIG. 2 is a signaling interaction diagram of a transmission path configuration method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a connection structure of an implementation manner of a first node device and a second node device according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of a connection structure of another implementation manner of a first node device and a second node device according to an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of a sub-type according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a TLV according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a second implementation manner of a sub-type according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a third implementation manner of a sub-type according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a fourth implementation manner of a sub-type according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a second implementation manner of a TLV according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a third implementation manner of a TLV according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a fourth implementation manner of a TLV according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a virtual device of a first node device according to an embodiment of the present disclosure
  • FIG. 14 is a schematic structural diagram of a physical device of a first node device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a virtual device of a second node device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a physical device of a second node device according to an embodiment of the present disclosure.
  • the node devices of the service data transmission network are transmitted based on the Ethernet transmission protocol.
  • the service data is divided into multiple data blocks, and each data block is separately scheduled with independent bandwidth. After being transmitted to the peer device, the data is divided according to the divided data block and the scheduling rule. Block reorganization. Therefore, if each hop of the service data transmission network is a FlexE transmission path, when the service data is transmitted, not only the bandwidth can be strictly guaranteed, but also the service isolation can be provided for the transmission of the service data, thereby ensuring the transmission of the service data. QoS, therefore, the configuration of the FlexE transmission path is necessary.
  • node A and node B in FIG. 1 are two nodes in a transmission path, and node A transmits data to node B through four physical links.
  • the transmission path between node A and node B is configured as a FlexE transmission path
  • the transmission port of four physical links, port A1, port A2, port A3, and port A4, and the receiving port B1 and port are required.
  • B2, port B3, and port B4 are configured separately (PHY number).
  • four physical links need to be bound to form a FlexE group between node A and node B according to the rule, and the virtual port of the transmitting end of node A and the virtual port of the receiving end of node B are also respectively configured for the FlexE group. Group number.
  • the FlexE group includes at least one PHY link, and one FlexE group is a virtual transmission link disposed between the node A and the node B.
  • the bandwidth of the virtual transmission link is the total bandwidth of the PHY link in the FlexE group.
  • node A includes one virtual port of the FlexE group
  • node B includes another virtual port of the FlexE group.
  • the node A sends a data packet to the node B through the port A1, the port A2, the port A3, and the port A4.
  • the data packet includes the PHY number and group corresponding to port A1, port A2, port A3, and port A4. Number.
  • Node B reads the PHY number and group number in the data packet, checks whether the PHY numbers at both ends of each PHY link are the same, and whether the group numbers at both ends of each FlexE group are the same. Specifically, the PHY number of the port B1 is the same as the PHY number of the port A1, and the group number corresponding to the port B1 is the same as the group number corresponding to the port A1, and the verification method for the other three links is similar. , will not repeat them here.
  • Node B sends a notification message of successful verification to Node A, and Node A can transmit data to Node B through the FlexE transmission mode. Otherwise, Node B sends a configuration error message to the network management device or network controller.
  • a FlexE group includes at least two PHY links
  • the PHY numbers of any two PHY links cannot be the same.
  • the port The PHY numbers of A1, port A2, port A3, and port A4 are different from each other.
  • the node A and the node B include at least two FlexE groups, the group numbers of any two FlexE groups are also different from each other, for example, the link formed by the port A1 and the port B1 in FIG.
  • the link formed by port B2 belongs to the first FlexE group, the link formed by port A3 and port B3, and the link formed by port A4 and port B4, belonging to the second FlexE group, the group number and the second of the first FlexE group.
  • the group number of the FlexE group cannot be the same.
  • the port number and the PHY number of the port of the node A and the port of the node B are currently manually configured, and the node A and the node B respectively include a plurality of ports. Therefore, the configuration efficiency is low and the error rate is also high.
  • the data transmission network includes a plurality of transmission nodes, that is, a connection structure including a plurality of interconnected nodes A and B, and generally, a group number and a PHY of each node of the plurality of nodes of the data transmission network The number is also manually configured. Since the configuration amount is much larger than that of the two nodes shown in FIG. 1 when the data transmission network is based on the data transmission network, the disadvantage of the manual configuration will be more prominent. Based on this, the present inventors have found out that the solution is found.
  • FIG. 2 is a signaling interaction diagram of a method for configuring a transmission path according to an embodiment of the present invention.
  • the method for configuring a transmission path according to an embodiment of the present invention can automatically perform configuration, which not only improves configuration efficiency, but also reduces configuration errors. possibility.
  • the transmission path of the service data is configured as a FlexE transmission path
  • the interface of the connected node device is configured as a FlexE interface
  • the interface of the node device can be configured as a FlexE interface, provided that the node device supports the FlexE interface. .
  • the device involved supports FlexE by default, and the embodiment of the present invention does not emphasize this later.
  • the implementation of this embodiment is based on any two connected node devices in the network.
  • the two node devices are referred to as a first node device and a second node device.
  • the first node device and the second node device include N physical links, where the N physical links include: N first ports that are set on the first node device, and are set on the second node device.
  • N second ports, and N first ports are respectively connected to the N second ports one by one to form a channel.
  • N is an integer greater than or equal to 1. For example, as shown in FIG. 1, N is 4.
  • configuring the FlexE transmission path specifically configures a PHY number for each of the N first ports, and configures a PHY number for each of the N second ports.
  • the N physical links need to be bound into a FlexE group according to the rules. Then, the first node device and the second node device respectively set virtual ports for the FlexE group, and then, the first node device and the first set for the FlexE group. The virtual port of the two-node device is configured with the group number.
  • the embodiment of the present invention may be described in the context of a FlexE group, where the FlexE group includes N physical links.
  • the group number corresponding to the first node device is referred to as a first group number
  • the group number corresponding to the second node device is referred to as a second group number
  • each of the N first ports is used.
  • the PHY number of the first port is referred to as a first PHY number
  • the PHY number of each of the N second ports is referred to as a second PHY number.
  • the first group number indicates that the N first PHY numbers belong to the FlexE group
  • the second group number indicates that the N second PHY numbers belong to the FlexE group.
  • Step S21 The second node device sends a first packet to the first node device by using each physical link of the N physical links, where the first packet includes a priority parameter of the second node device. And determining, by the first node device, the priority of the first node device is higher than the first node device according to the priority parameter of the second node device and the device identifier of the second node device in the first packet a priority of the two-node device; in step S23, the first node device determines a first PHY number of each of the first group number and the N first ports; and in step S24, the first node device passes the N physical chains Each physical link in the path sends a second packet to the second node device. In step S25, the second node device determines, according to the second packet, the second group number and each of the second ports. Second PHY number.
  • the first packet includes the device information of the second node device, and the device information of the second node device may include at least one of the following information: whether the second node device supports the FlexE and the second node.
  • the device identifier of the device the line card number of the second node device connected to the N physical links, and the priority parameter of the second node device.
  • the priority parameter is a preset binary value, which is used to indicate the priority of the peer node device and the local node device.
  • the node device with the higher priority is the device that actively initiates the configuration of the FlexE interface
  • the node device with the lower priority is configured to passively configure the FlexE interface according to the configuration result of the node device with the higher priority.
  • the line card is a data transceiving component in the node device, capable of encoding/decoding, identifying, and switching data forwarding modes.
  • the line card can be set in one node device, and each line card has multiple ports.
  • the first node device and the second node device run a link layer discovery protocol (LLDP), and the LLDP protocol carries the LLDP packet.
  • the traditional LLDP packet does not include the device information of the node device.
  • the second node device may add an extension field to the LLDP packet, and carry the device information in the added extension field to obtain the first packet, thereby determining priority.
  • a higher-level node device provides an execution basis, which in turn provides an information base for the implementation of the solution.
  • the extension field is a new sub-type of a dedicated extension of an Optical Internetworking Forum (OIF), or the extension field is a new one.
  • Type length value type, length, value, TLV
  • the format of the extension field and the adding process are described in detail below, and will not be described here.
  • the second node device usually sends an LLDP packet to each of the N second ports. Therefore, the first node device receives an LLDP packet through the N physical links.
  • the LLDP packet is used to advertise the device information of the first node device and the second node device. Therefore, the device attribute information included in each LLDP packet is the same in the N LLDP packets, for example, the second node device.
  • the priority parameter and the device identification information of the second node device, and the N LLDP packets are respectively sent from one of the N second ports, so the port-related information included in each LLDP packet is included.
  • the information parameter is an information parameter of the second port that sends the LLDP packet. For example, the port number of the second port that sends the LLDP packet, and the line card number of the second node device to which the second port is connected.
  • the first node device may read the priority parameter and the device identifier of the second node device from the LLDP packet, and then the first node device may be configured according to the second node device.
  • the priority parameter determines whether the priority of the local end is higher than the priority of the second node device, and further determines whether the local end can initiate automatic configuration of the FlexE interface.
  • the first node device may determine according to the device identifier of the second node device.
  • the first node device can read the priority parameter of the local end, and then compare with the priority parameter of the second node device. For example, in this embodiment, the smaller the priority parameter is, the higher the priority is. If the priority parameter of the first node device is smaller than the priority parameter of the second node device, the priority of the first node device is higher. The priority of the second node device. Correspondingly, if the priority parameter of the first node device is greater than the priority parameter of the second node device, the priority of the second node device is higher than the priority of the first node device.
  • the priority parameter of the node device may not be set. If the priority parameter of the node device is not set, the default value may be defaulted. For example, in an alternative example of the invention, the default value may be 32768. Based on this, if the priority parameter of the first node device and the priority parameter of the second node device are not set, the priority parameters of the first node device and the second node device are both default values, then the first node The device has the same priority as the second node device.
  • the first node device can read the device identifier of the local device, and determine whether the device identifier of the local device is smaller than the device identifier of the second node device, and if the device identifier of the local device is smaller than the device identifier of the second node device, The priority is higher than the priority of the second node device.
  • the device identifier may be any specific identifier of the corresponding node device, and the specific identifier of the node device includes, but is not limited to, an internet protocol address (IP) address and a MAC address of the node device.
  • IP internet protocol address
  • a node device may set multiple IP addresses or multiple MAC addresses. When the device identifier of the node device is set to a MAC address, any one of the multiple MAC addresses or the smallest MAC address may be selected as the MAC address.
  • Equipment Identity Of course, if the device ID of the node device is set to an IP address or other identifier, the selection mode is similar.
  • the manner of determining the priority of the node device and the determining rule are all optional embodiments of the present invention, and are not limited to the embodiment of the present invention.
  • two node devices connected to each other automatically determine the node devices that actively configure the FlexE interface through certain rules, and fully prepare for automatically configuring the FlexE transmission path, which is the first step of automatically configuring the FlexE transmission path.
  • the first node device can read each physical chain of the N physical links from each LLDP packet of the N LLDP packets.
  • the line card number of the second node device connected to the road, and further, each line can be determined according to the line card number of the second node device connected to each physical link and the line card card number of the connected first node device The FlexE group to which the physical link belongs.
  • the transmitting end converts the Ethernet data frame into a PHY data frame, and sends the PHY data frame to the receiving end according to the corresponding time slot.
  • the receiving end restores the PHY data frame to the Ethernet data frame according to the corresponding time slot.
  • the transmitting end since the PHY data frame is transmitted according to the time slot, the transmitting end switches the data transmission mode of the transmitting port before transmitting the PHY data frame.
  • the receiving port of the receiving end receives the PHY data frame in the corresponding transmission mode, so that the PHY data frame can be restored to the Ethernet data frame according to the corresponding time slot.
  • the sender port and the receiver port of the PHY data frame should transmit data according to the same time slot, and the corresponding PHY data frame can be transmitted smoothly.
  • the transmission mode of the port switching port according to the time slot, and the recovery of the PHY data frame into the Ethernet data frame according to the time slot are all performed by the line card, and one line card usually transmits and receives data according to a time slot.
  • the logical function of a FlexE group is a virtual transmission link, and the corresponding time slot of the transmitting end of one transmission link is the same as the time slot corresponding to the receiving end data.
  • the ports located on different line cards may have different time slots, which may result in the PHY data frame not being transmitted smoothly, or the PHY data frame cannot be restored to the Ethernet data frame.
  • a FlexE group includes a link
  • the sender port and the receiver port of the link are respectively connected to one line card
  • a FlexE group includes multiple links, usually each link in multiple links
  • the sender port is connected to the same line card, and the receiver port of each link of the multiple links is also connected to the same line card.
  • the S physical links are bound to a FlexE group. Where S is greater than or equal to 1 and less than or equal to N, the S physical links are part or all of the physical links of the N physical links. In this embodiment, S is equal to N. Binding each physical link of the S physical links to one FlexE if the S card physical link corresponds to the line card number of the second node device, or the corresponding line card card number of the first node device. group.
  • the S physical links may be bound to S FlexE groups, that is, each of the S physical links.
  • a physical link can be bound to a FlexE group.
  • the S-i physical links in the S physical links are bound to the first FlexE group, and the remaining i physical links are bound to the second FlexE group.
  • i is greater than or equal to 1 and less than S.
  • other binding schemes may also be included, which are not described here.
  • the specific binding policy may be pre-configured and stored in the first node device and the second node device. The method of the present invention is not described in detail in the embodiments of the present invention.
  • the first node device configures the local port as a FlexE interface.
  • the local port of the first node device refers to the local port.
  • the first node device determines a first PHY number for each of the N first ports, and obtains N first PHY numbers.
  • the first node device further determines the first group number by binding the obtained FlexE group to the N physical links.
  • the first group number indicates that the N first PHY numbers belong to the FlexE group, and since the N first PHY numbers belong to the same FlexE group, each of the N first PHY numbers is first.
  • the PHY number is unique in this FlexE group.
  • the value range of the PHY number is theoretically 0-255.
  • the protocol standards 0 and 255 are used as reserved items, the PHY number is taken as a value between 1 and 254, and the length of the PHY number is 8 bits.
  • the group number is usually in the range 0-255, and the length of the group number is 20 bits. In the configuration, the PHY number and the group number may be set in a random or sequential manner, which is not limited in this embodiment of the present invention.
  • the first node device may not configure the first group number. According to the OIF protocol, if the first group number is not configured, the first group number defaults to 0.
  • the first node device may first determine N first PHY numbers, perform FlexE group binding operations, or perform FlexE group binding operations, and then perform determining N first PHY numbers and A group number operation.
  • the first node device may first determine the N first PHY numbers, determine the first group number, or determine the first group number, and then determine the first PHY number, which is not limited in this embodiment of the present invention.
  • the N second packets are generated, and each of the first PHY numbers in the N first PHY numbers is respectively carried in the N second packets.
  • each second packet of the N second packets carries a group number corresponding to the corresponding first PHY number.
  • the N first PHY numbers are all corresponding to the first group number. Therefore, the N second packets carry the first group number.
  • the first node device sends a second packet to the second node device by using each of the N first ports. The second packet sent by each first port carries the first PHY number corresponding to the first port.
  • the second node device may read the first PHY number and the first group number in each second packet, and determine the second according to the first group number and each first PHY number.
  • Group number and a second PHY number of each of the N second ports since the PHY numbers at both ends of the same PHY link should be the same, the group number at both ends of the same FlexE group should be the same. Therefore, the second PHY number of each of the N second ports should be the same.
  • the first PHY number in the second packet corresponding to the second port is the same, and correspondingly, the second group number is the same as the first group number, and the second group number indicates that the N second PHY numbers belong to the foregoing The FlexE group described.
  • the node device When configuring a FlexE interface, not only the PHY number and the group number are usually configured. After the FlexE group is bound, the node device also generates a PHY map. Among them, a FlexE group corresponds to a PHY map, and the PHY map includes all PHY numbers belonging to the FlexE group. Based on this, in the embodiment, the first node device further generates a PHY map, where the PHY map includes N first PHY numbers. When the first node device sends the second packet to the second node device, the second packet may also carry the PHY map.
  • the data transmission mode may be first switched to the FlexE mode, and then the first PHY number, the first group number, and the PHY map are carried.
  • the switch data transfer mode refers to the device that supports FlexE, and the function of FlexE is enabled.
  • the first node device schedules and encapsulates the data block corresponding to the Ethernet data packet according to the mode specified by the transmission protocol of the FlexE, and sends the data block to the PHY link, and the second node device can receive the data block, and according to the schedule (Calendar) Recovery of Ethernet data packets.
  • the information transmitted by the overhead frame is a mature technology in the field, and the embodiments of the present invention are not described in detail herein.
  • the “first” and “second” are merely for clarifying the relationship between the two node devices, and the present solution is not limited.
  • this embodiment is only an optional example of the present invention. In actual operation, the execution process of the second node device and the first node device are the same. Therefore, in the embodiment, the first node device and the second device. Node devices can be interchanged.
  • the local node device can determine whether it can initiate automatic configuration according to the device information of the peer node device. If the local node device can initiate automatic configuration, the local port can be automatically configured. It is a FlexE interface and triggers the configuration of the peer node device automatically, which can improve the configuration efficiency and ensure the correctness of the configured labels.
  • first node device and the second node device further include M physical links, where M is an integer greater than or equal to 1.
  • M is an integer greater than or equal to 1.
  • the M third ports included in the first node device are connected to the M physical links one by one, and the M fourth ports included in the second node device are connected to the M physical links one-to-one.
  • the M physical links can also be bound into one. FlexE group.
  • the process of configuring the FlexE transmission path is similar to the description of the foregoing embodiment. Since the priority of the first node device is higher than the priority of the second node device, the first node device determines the third group. Number, and the third PHY number of each third port of the M third ports, and then generating a third packet, and sending the third packet to the second node device via the M physical links, the second node The device determines, according to the third packet, a fourth PHY number of the fourth group number and each of the M fourth ports. For the specific determination process and the content of the third packet, reference may be made to the description of the foregoing embodiment, which is not described in detail in this embodiment.
  • the FlexE group corresponding to the M physical links the FlexE group corresponding to the N physical links in the foregoing embodiment are included in the transmission path of the first node device and the second node device,
  • the first group number and the third group number are different, and can also be described as the second group number and the fourth group number are different.
  • the first node device obtains the device information of the second node device from the first packet when the N physical links are configured, and determines that the priority of the first node device is higher than that of the second node device, then A node device may store the priority determination result, and in this embodiment, invoke the priority determination result, and further perform a configuration operation on the M physical links. Therefore, it is not necessary to repeatedly perform the reading of the device information of the second node device, and the operation of determining the priority according to the device information of the second node device, which simplifies the execution process.
  • the second node device sends the fourth packet by using the M physical links, and the fourth packet also includes the device information of the second node device, and the first node device determines again according to the fourth packet.
  • the priority of the first node device is higher than the priority of the second node device.
  • the M physical links may be independent of the foregoing N physical links, that is, the first node device and the second node device include at least M+N physical links.
  • the line card of the first node device to which the M physical links are connected may be the same as the line card of the first node device connected to the N physical links, and/ Or, the line card of the second node device to which the M physical links are connected may be the same as the line card of the second node device to which the N physical links are connected.
  • the M physical links may further include a part of the N physical links.
  • the M physical links may include N-S physical links in the N physical links.
  • the line cards of the first node device connected to the M physical links are the same as the line cards of the first node device connected to the S physical links, and the M physical links are connected.
  • the line card of the second node device is the same as the line card of the second node device to which the S physical links are connected.
  • the technical solution of the embodiment of the present invention can flexibly bind the FlexE group between the two connected node devices, thereby flexibly configuring paths of different transmission rates and different transmission bandwidths, thereby enabling the solution to be adapted.
  • a variety of programs a wide range of applicability.
  • each node since the other nodes are connected to the two nodes except the start node and the terminating node in the transport network, each node needs to connect its upstream node and two sets of ports connecting its downstream nodes. , respectively configured as a FlexE interface. Because the two ports of the same node belong to different FlexE transmission paths, the labels of the two groups are the same as the labels of different FlexE interfaces. Therefore, the labels of the two groups are likely to appear. The same PHY number, and / or the same group number, which may result in data inconvenience management.
  • the second node device may also add the occupied PHY number in the first packet, and/or The occupied group number.
  • the first node device can read the occupied group number of the second node device from the first packet, before configuring the first group number and the N first PHY numbers. And/or, the PHY number is occupied, and then a group number different from the occupied group number is configured as the first group number, and a PHY number different from the occupied PHY number is configured as any one of the N first PHY numbers. PHY number. Therefore, it is possible to prevent different ports of the same node device from using the same label, thereby further improving the solution.
  • the solution adds an extension field to the LLDP packet, so that the solution can be implemented.
  • two ways of adding an extension field are provided, which are described in detail below.
  • TLV is the basic component of LLDP. It is identified by the TLV-type number. Each TLV-type number corresponds to a TLV, and certain information is stored. In the TLV in which the TLV-type is 127 in the LLDP protocol, an OIF-specific extension field is set, and the OIF-specific extension field may include multiple sub-types, each sub-type corresponding to a different number, and different sub-types carrying different information. When the device information needs to be carried, a new sub-type number may be applied in the OIF dedicated extension field, and then the device information is added to the sub-type corresponding to the new sub-type number, and the new sub-type number is corresponding. The sub-type is added to the OIF-specific extension field.
  • FIG. 5 is a schematic structural diagram of a sub-type according to an embodiment of the present invention, where the sub-type subtype belongs to a TLV whose TLV-type is 127, and the TLV is set with a TLV information length and a unique organization.
  • the identifier (Organization Unique Identification (OUI)
  • the length of the TLV information is the total length of the TLV data frame.
  • the OUI is equal to 000F40, indicating a dedicated extension allocated to the OIF.
  • the new sub-type number of the OIF-specific extension field application is 100, then the FlexE version number, the identification bit, the FlexE priority parameter, the device identifier, the FlexE granularity, and the reserved bit are set in the sub-type.
  • the length of the sub-type is 1 byte.
  • the FlexE version number identifies the version number of the FlexE supported by the device. For example, it can be 1.0; the identifier bit is 8 bits, and two identification parameters can be set.
  • one is M bit, which is used to indicate whether the PHY number occupied by the device is carried, and the other bit is G bit, which is used to indicate whether the group number occupied by the device is carried; the length of the FlexE priority parameter is 16 bits.
  • the length of the device identifier is 48 bits; the FlexE granularity can be 5G; the reserved bits are the extension bits set in the data frame to facilitate the addition of new data, the default is 0.
  • Method 2 Add a new TLV to the LLDP protocol. Similar to adding a new sub-type, LLDP can apply for a new TLV-type number and then add device information to the TLV corresponding to the new TLV-type number.
  • FIG. 6 is a schematic structural diagram of a TLV according to an embodiment of the present invention, where a TLV includes a TLV-type number, a TLV information length, a FlexE version number, an identifier bit, a FlexE priority parameter, a device identifier, and a FlexE granularity. Reserved bit.
  • the meanings and contents of the data information are the same as those in the embodiment shown in FIG. 5, and details are not described herein again.
  • the length of the TLV-type number is 7 bits
  • the length of the device priority parameter is 16 bits
  • the length of the device identifier is 48 bits.
  • FIG. 5 and FIG. 6 are only optional implementation manners provided by the present invention. In the actual operation, in the newly added sub-type and TLV, other information may be added as needed. No restrictions.
  • the extension field may also carry the PHY number and the occupied group number that the node device has occupied.
  • the G bit in the identification bit can be set to 1, and the M bit can be set to 0, thereby indicating that only The group number that the node device has occupied is carried.
  • a supplemental bit is also set.
  • the supplemental bit is a byte reserved bit in the frame structure.
  • N is a large number of bits, and when the total number of bytes of the "FlexE group label N" exceeds 8 bits, the excess data can be written to the "FlexE group label N". Supplementary bit.
  • FIG. 8 is a schematic structural diagram of a third implementation manner of a sub-type according to an embodiment of the present invention.
  • the sub-type only carries the PHY number occupied by the node device, and accordingly, correspondingly,
  • the G bit in the flag is set to 0, and the M bit is set to 1.
  • the PHY number occupied by the node device may be represented by a PHY map. As shown in FIG. 8 , the 0-255 PHY number carried by the sub-type is a PHY map, where may be 0 in advance. -255 sets the occupancy flag separately. If the label is occupied, the occupancy flag can be set to 1, otherwise it is set to 0.
  • FIG. 9 is a schematic structural diagram of a fourth implementation manner of a sub-type according to an embodiment of the present invention.
  • a sub-type carries a PHY number and a group number occupied by a node device, and accordingly, corresponding
  • the G bit and the M bit in the flag bit are set to 1.
  • the PHY number and/or group number that the foregoing node device has occupied can also be carried in the form of mode 2.
  • FIG. 10 is a schematic structural diagram of a second implementation manner of a TLV according to an embodiment of the present invention.
  • the TLV only carries the group number occupied by the node device, and the G bit in the identifier bit. Set to 1, M bit is set to 0, and the carrying form is similar to that shown in Figure 7.
  • FIG. 11 is a schematic structural diagram of a third embodiment of a TLV according to an embodiment of the present invention.
  • the TLV only carries the PHY number occupied by the node device.
  • the G bit in the flag is set to 0
  • the M bit is set to 1
  • the occupied PHY number is also carried in the form of a PHY map.
  • FIG. 12 is a schematic structural diagram of a fourth implementation manner of a TLV according to an embodiment of the present invention.
  • a TLV carries a PHY number and a group number occupied by a node device, and a G bit in the identifier bit.
  • the M bit is set to 1.
  • the scheme can send the local device information of the node device to the peer node device by adding an extension field in the LLDP protocol, thereby providing an implementation condition for the node device to automatically configure the FlexE, and further, the two phases can be triggered.
  • the connected node device automatically configures FlexE.
  • FIG. 13 is a schematic diagram of a node device 1300 according to an embodiment of the present invention.
  • the node device 1300 can be applied to the scenario shown in FIG. 3 and FIG. 4 as the first node device for performing the method corresponding to FIG. 2 .
  • the node device 1300 includes a receiving module 1301, a determining module 1302, and a sending module 1303.
  • the receiving module 1301 is configured to perform various information reception performed by the first node device in the foregoing method, where the sending module 1303 is configured to perform various information transmissions performed by the first node device in the foregoing method;
  • the module 1302 is specifically configured to perform other processing in addition to information transceiving of the first node device in the foregoing method.
  • the receiving module 1301 may be configured to receive, by using each physical link of the N physical links, a first packet sent by the second node device, where the first packet includes a priority parameter of the second node device, and
  • the device identifier of the two-node device, the first node device and the second node device include N physical links, where N is an integer greater than or equal to 1, and the first node device includes N first ports and N physical links.
  • the links are connected one by one, and the N second ports included in the second node device are connected in one-to-one correspondence with the N physical links.
  • the determining module 1302 may be configured to: when determining, according to the priority parameter of the second node device in the first packet and the device identifier of the second node device, that the priority of the first node device is higher than the priority of the second node device Determining, by the first group of labels, a first physical layer PHY label of each of the N first ports, wherein the first group label is used to indicate a first port of each of the N first ports A PHY label belongs to the same flexible Ethernet FlexE group, and the first PHY label of each of the N first ports is unique among the FlexE groups.
  • the sending module 1303 can be configured to send a second packet to the second node device by using each of the N physical links, where the second packet includes the first group of labels, and the N physical links a first PHY label of the first port corresponding to each physical link, where the second packet is used to trigger the second node device to determine each of the second group label and the N second ports according to the second packet The second physical layer PHY label of the second port.
  • the receiving module 1301 and the sending module 1303 may be implemented by a transceiver, and the determining module 1302 may be implemented by a processor.
  • the node device 1300 can include a processor 1401, a transceiver 1402, and a memory 1403.
  • the memory 1403 may be used to store a program/code pre-installed when the node device 1300 is shipped from the factory, or may store a code or the like for execution of the processor 1401.
  • the node device 1300 may correspond to a first node device in a method according to an embodiment of the present invention, wherein the transceiver 1402 is configured to perform various information performed by the first node device in the above method.
  • the transceiver 140 is configured to perform processing other than information transceiving of the first node device in the foregoing method. I will not repeat them here.
  • FIG. 15 is a schematic diagram of a node device 1500 according to an embodiment of the present invention.
  • the node device 1500 as a second node device can be applied to the scenarios shown in FIG. 3 and FIG. 4 for performing the method corresponding to FIG. 2.
  • the node device 1500 includes a sending module 1501, a receiving module 1502, and a determining module 1503.
  • the sending module 1501 is configured to perform various information transmissions performed by the second node device in the foregoing method
  • the receiving module 1502 is configured to perform various information receiving performed by the second node device in the foregoing method
  • the module 1503 is configured to perform other processing in addition to information transceiving of the second node device in the foregoing method.
  • the sending module 1501 may be configured to send, by using each physical link of the N physical links, a first packet to the first node device, where the first packet includes a priority parameter of the second node device and the second node.
  • the device identifier of the device, the first packet is used to trigger the first node device to determine that the priority of the first node device is higher than the first node device according to the priority parameter of the second node device in the first packet and the device identifier of the second node device.
  • the priority of the two-node device, the second node device and the first node device include N physical links, where N is an integer greater than or equal to 1, and the first node device includes N first ports and N physical interfaces.
  • the links are connected one by one, and the N second ports included in the second node device are connected in one-to-one correspondence with the N physical links.
  • the receiving module 1502 is configured to receive, by using each physical link of the N physical links, a second packet sent by the first node device, where the second packet includes the first group of labels, and the N physical links a first PHY label of the first port corresponding to each physical link, where the first group label is used to indicate that the first PHY label of each of the N first ports belongs to the same flexible ether In the network FlexE group, the first PHY label of each of the N first ports is unique among the FlexE groups.
  • the determining module 1503 is configured to determine, according to the second packet, a second physical layer PHY label of the second group label and each of the N second ports, where the second group label is used to indicate N
  • the second physical layer PHY label for each of the second ports belongs to the FlexE group, and the second PHY label for each of the N second ports is unique among the FlexE groups.
  • the sending module 1501 and the receiving module 1502 may be implemented by a transceiver
  • the determining module 1503 may be implemented by a processor.
  • the node device 1500 can include a processor 1601, a transceiver 1602, and a memory 1603.
  • the memory 1603 may be used to store a program/code pre-installed by the node device 1500 at the factory, or may store a code or the like for execution of the processor 1601.
  • a node device 1500 may correspond to a second node device in a method according to an embodiment of the present invention, wherein the transceiver 1602 is configured to perform various information performed by the second node device in the above method.
  • the transceiver 160 is configured to perform other processing than the information transmission and reception of the second node device in the foregoing method. I will not repeat them here.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium is stored in any device, and the program may be executed when the program is executed. Some or all of the steps of the transmission path configuration method provided in FIGS. 2 through 12 are included.
  • the storage medium in any device may be a magnetic disk, an optical disk, a read-only memory (English: read-only memory, or ROM) or a random access memory (English: random access memory, RAM for short).
  • the transceiver may be a wired transceiver, a wireless transceiver, or a combination thereof.
  • the wired transceiver can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless transceiver can be, for example, a wireless local area network transceiver, a cellular network transceiver, or a combination thereof.
  • the processor may be a central processing unit (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviated: NP) or a combination of CPU and NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (abbreviated as PLD), or a combination thereof.
  • the above PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), field-programmable gate array (English: field-programmable gate array, abbreviation: FPGA), general array logic (English: generic array Logic, abbreviation: GAL) or any combination thereof.
  • the memory may include a volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); the memory may also include non-volatile memory (English: non-volatile memory).
  • read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, Abbreviation: SSD); the memory may also include a combination of the above types of memory.
  • the 14 and 16 may also include a bus interface, which may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by the processor and various circuits of memory represented by the memory.
  • the bus interface can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • the transceiver provides a unit for communicating with various other devices on a transmission medium.
  • the processor is responsible for managing the bus architecture and the usual processing, and the memory can store the data that the processor uses when performing operations.
  • a general purpose processor may be a microprocessor.
  • the general purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • the processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.
  • the steps of the method or algorithm described in the embodiments of the present invention may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art.
  • the storage medium can be coupled to the processor such that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and the storage medium may be disposed in an ASIC, and the ASIC may be disposed in the UE. Alternatively, the processor and the storage medium may also be located in different components in the UE.
  • the size of the sequence number of each process does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken by the embodiment of the present invention.
  • the implementation process constitutes any qualification.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • first and second are merely for clarifying the relationship between the two executing entities, and the present scheme is not limited.
  • this embodiment is merely an optional example of the present invention, and in actual operation, “first” and “second” may be interchanged.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Small-Scale Networks (AREA)

Abstract

Selon des modes de réalisation, l'invention concerne un procédé, un appareil et un dispositif de configuration de voie de transmission. Ledit procédé comprend les étapes suivantes : un premier dispositif nœud reçoit un premier message envoyé par un second dispositif nœud ; si la priorité du premier dispositif nœud est supérieure à la priorité du second dispositif nœud, le premier dispositif nœud détermine un premier numéro de groupe et un premier numéro de couche physique (PHY) de chaque premier port dans les N premiers ports ; le premier dispositif nœud envoie un second message au second dispositif nœud, le second message étant utilisé pour déclencher le second dispositif nœud afin de déterminer un second numéro de groupe et un second numéro de couche physique (PHY) de chaque second port dans les N seconds ports. Par conséquent, la présente solution peut exécuter une configuration automatique d'une interface de FlexE, améliorant l'efficacité de configuration, et garantissant la précision de la configuration.
PCT/CN2018/087947 2017-10-16 2018-05-23 Procédé, appareil et dispositif de configuration de voie de transmission Ceased WO2019076046A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710958369.7A CN109672513B (zh) 2017-10-16 2017-10-16 传输路径配置方法、装置及设备
CN201710958369.7 2017-10-16

Publications (1)

Publication Number Publication Date
WO2019076046A1 true WO2019076046A1 (fr) 2019-04-25

Family

ID=66139192

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/087947 Ceased WO2019076046A1 (fr) 2017-10-16 2018-05-23 Procédé, appareil et dispositif de configuration de voie de transmission

Country Status (2)

Country Link
CN (1) CN109672513B (fr)
WO (1) WO2019076046A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4072043A4 (fr) * 2019-12-12 2023-01-18 ZTE Corporation Procédé, appareil, dispositif et support de réception multitrame aérienne d'ethernet flexible
US20230142251A1 (en) * 2020-07-03 2023-05-11 Huawei Technologies Co., Ltd. Flexible Ethernet Flexe Automatic Configuration Method and Apparatus

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112217661B (zh) * 2019-07-12 2024-02-02 华为技术有限公司 一种端口模式自适应的方法及装置
CN110601910A (zh) * 2019-10-24 2019-12-20 北京通畅电信规划设计院有限公司 一种基于flexE业务的信息传输系统及其传输方法
CN112953883A (zh) * 2019-12-10 2021-06-11 中兴通讯股份有限公司 设备协议互通方法、设备及存储介质
CN113595751B (zh) * 2020-04-30 2025-03-28 中兴通讯股份有限公司 FlexE组创建方法、装置、设备及介质
CN115242267B (zh) * 2022-06-01 2025-05-02 华为数字能源技术有限公司 一种电力线通信plc方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102364892A (zh) * 2011-10-12 2012-02-29 华为技术有限公司 一种lacp链路切换、数据传输方法与装置
CN106330630A (zh) * 2015-07-03 2017-01-11 华为技术有限公司 传输灵活以太网的数据流的方法、发射机和接收机
CN106803814A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种灵活以太网路径的建立方法、装置及系统
CN106850465A (zh) * 2016-12-27 2017-06-13 深圳市海思半导体有限公司 一种Flex E数据交换方法及交换设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10637604B2 (en) * 2014-10-24 2020-04-28 Ciena Corporation Flexible ethernet and multi link gearbox mapping procedure to optical transport network
CN105991435B (zh) * 2015-02-05 2019-08-27 华为技术有限公司 用于获取端口路径的方法及装置
US10218823B2 (en) * 2015-06-30 2019-02-26 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
CN106803785A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种链路管理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102364892A (zh) * 2011-10-12 2012-02-29 华为技术有限公司 一种lacp链路切换、数据传输方法与装置
CN106330630A (zh) * 2015-07-03 2017-01-11 华为技术有限公司 传输灵活以太网的数据流的方法、发射机和接收机
CN106803814A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种灵活以太网路径的建立方法、装置及系统
CN106850465A (zh) * 2016-12-27 2017-06-13 深圳市海思半导体有限公司 一种Flex E数据交换方法及交换设备

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4072043A4 (fr) * 2019-12-12 2023-01-18 ZTE Corporation Procédé, appareil, dispositif et support de réception multitrame aérienne d'ethernet flexible
US20230142251A1 (en) * 2020-07-03 2023-05-11 Huawei Technologies Co., Ltd. Flexible Ethernet Flexe Automatic Configuration Method and Apparatus
EP4164149A4 (fr) * 2020-07-03 2023-11-01 Huawei Technologies Co., Ltd. Procédé et dispositif de configuration automatique ethernet flexible (flexe)

Also Published As

Publication number Publication date
CN109672513A (zh) 2019-04-23
CN109672513B (zh) 2021-10-22

Similar Documents

Publication Publication Date Title
WO2019076046A1 (fr) Procédé, appareil et dispositif de configuration de voie de transmission
CN112688754B (zh) 基于灵活以太网FlexE传输业务流的方法和装置
EP4012989B1 (fr) Procédé et dispositif de transmission de paquets de service
CN111727589B (zh) 用于配置Flex以太网节点的方法和设备
CN110650002B (zh) 一种FlexE组中PHY的调整方法、相关设备及存储介质
WO2019019906A1 (fr) Procédé et dispositif de communication, et support d'informations
WO2018196600A1 (fr) Procédé et dispositif de configuration d'un groupe de liaison
CN108156074A (zh) 保护倒换方法、网络设备及系统
CN113330719B (zh) 用于串行总线系统的用户站和在串行总线系统中通信的方法
CN107770085B (zh) 一种网络负载均衡方法、设备及系统
US20220337477A1 (en) Flexible Ethernet Group Management Method, Device, and Computer-Readable Storage Medium
CN113557696B (zh) 在网络中路由FlexE数据
CN109691031B (zh) 业务报文传输方法及节点设备
US11750310B2 (en) Clock synchronization packet exchanging method and apparatus
WO2021115452A1 (fr) Procédé, appareil, dispositif et support de réception multitrame aérienne d'ethernet flexible
WO2021197208A1 (fr) Procédé de réglage de flux de service et dispositif de communication
US11356372B2 (en) Data traffic processing method, device, and system
US11362958B2 (en) Device and method for transferring identification and/or data flow control information between devices
WO2023116284A1 (fr) Négociation de créneaux et dispositif pour service à grain fin dans un ethernet flexible (flexe)
CN113810281B (zh) 双归保护方法、系统和设备
CN110830152A (zh) 接收码块流的方法、发送码块流的方法和通信装置
WO2014127633A1 (fr) Procédé de transmission de paquets lldp et dispositif dcb
CN117176632A (zh) 报文接收方法、发送方法、转发方法、装置及系统
CN119697124B (zh) 服务质量控制方法、装置及可读存储介质
WO2023169285A1 (fr) Procédé et appareil de communication, dispositif de réseau et système

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18868526

Country of ref document: EP

Kind code of ref document: A1