WO2022193767A1

WO2022193767A1 - Ethernet packet processing method and related device

Info

Publication number: WO2022193767A1
Application number: PCT/CN2021/140402
Authority: WO
Inventors: 庄艳; 董鹏; 郑合文; 蒋有军
Original assignee: 华为技术有限公司
Priority date: 2021-03-17
Filing date: 2021-12-22
Publication date: 2022-09-22
Also published as: CN115174699A

Abstract

The embodiments of the present application provide an Ethernet packet processing method and a related device, which are used for supporting the sending and processing of an Ethernet packet where the frame length of which is less than 64 bytes. The Ethernet packet processing method provided in the embodiments of the present application specifically comprises: after receiving a first Ethernet packet sent by a second device, a first device detecting whether the first Ethernet packet carries first identification information, wherein the first identification information is used for indicating that the second device supports the processing of a first-Ethernet-type packet, and the first-Ethernet-type packet comprises an Ethernet packet where the frame length of which is less than 64 bytes; and if the first Ethernet packet carries the first identification information, the first device processing the first Ethernet packet according to the first identification information.

Description

An Ethernet packet processing method and related equipment

This application claims the priority of the Chinese patent application filed on March 17, 2021 with the State Intellectual Property Office of China, the application number is 202110286473.2, and the invention name is "An Ethernet message processing method and related equipment", the entire content of which is approved by Reference is incorporated in this application.

technical field

The present application relates to the field of communications, and in particular, to a method for processing an Ethernet packet and related equipment.

Background technique

With the continuous development of Ethernet standards, the rate of Ethernet interfaces continues to increase. Whether it is the 400GE Ethernet interface that is currently entering commercial use, or the 800GbE/1.6TbE Ethernet interface specification that will soon be established, the Ethernet standard has been pursuing the continuous improvement of interface bandwidth. Speed up. In terms of business, the Ethernet network has also expanded from the traditional carrier network to the server-based cloud data center network, and even to the current data-centric, big data analysis, artificial intelligence (AI) A high-performance and low-latency data center network with applications and high-performance computing services as the axis.

For the above applications, different applications correspond to different message characteristics. For example, high performance computing (HPC) applications have a high proportion of small messages, while applications such as AI have a high proportion of large messages, which are inside Ethernet. The current forwarding limit of Ethernet packets is: for Ethernet packets smaller than 64 bytes, it needs to be padded to 64 bytes before sending, or for Ethernet packets larger than 1518 bytes, it needs to be truncated to 1518 bytes and then sent. Filling Ethernet packets in this way will waste effective bandwidth and limit the amount of message forwarding; truncating Ethernet packets will increase the overhead of a single Ethernet packet.

Therefore, it is urgent to solve the forwarding problem of Ethernet packets with frame lengths less than 64 bytes and Ethernet packets with frame lengths greater than 1518 bytes.

SUMMARY OF THE INVENTION

Embodiments of the present application provide an Ethernet packet processing method and related equipment, which are used to support the sending and processing of Ethernet packets whose frame length is less than 64 bytes.

In a first aspect, an embodiment of the present application provides a method for processing an Ethernet packet, which specifically includes: after the first device receives the first Ethernet packet sent by the second device, detecting whether the first Ethernet packet carries the first Ethernet packet. identification information, wherein the first identification information is used to indicate that the second device supports processing a first Ethernet type packet, wherein the first Ethernet type packet includes an Ethernet packet whose frame length is less than 64 bytes; if the If the first Ethernet packet carries the first identification information, the first device processes the first Ethernet packet according to the first identification information.

In this embodiment, when the first Ethernet type packet includes Ethernet packets with multiple frame lengths, it may be referred to as a flexible Ethernet (Flex Frame or Flex Ethernet Frame) type packet or a computing Ethernet (Computing Ethernet) type packet ; and for Ethernet packets with different frame lengths, other names can also be given. For example, for an Ethernet packet whose frame length is less than 64 bytes, the first Ethernet type packet may also be referred to as a mini frame/mini frame (Mini Frame) type packet.

In this embodiment, when the first device supports processing of the first Ethernet type packet, when the first device receives an Ethernet packet whose frame length is less than 64 bytes, the first device processes the Ethernet packet according to the identification information, so that the The Ethernet protocol stack can support the receiving and processing of Ethernet packets whose frame length is less than 64 bytes, which improves the packet throughput rate of the Ethernet network.

In conjunction with the first aspect, in a possible implementation manner, the first device may also perform the following steps before processing the first Ethernet packet:

The first device determines the frame length of the first Ethernet packet and whether it supports processing the first Ethernet type packet; if the first device supports processing the Ethernet packet whose frame length is less than 64 bytes, and the If the frame length of an Ethernet packet is less than 64 bytes, the first device will perform an operation of processing the first Ethernet packet according to the first identification information.

Optionally, if the first device does not support processing the first Ethernet packet, and the frame length of the first Ethernet packet is less than 64 bytes, the first device discards the first Ethernet packet.

In this embodiment, the first Ethernet type packet includes an Ethernet packet with a frame length less than 64 bytes and an Ethernet packet with a frame length greater than 1518 bytes, so that the first device can simultaneously process small packets (frame length). Ethernet packets less than 64 bytes), large packets (Ether packets with a frame length greater than 1518 bytes), and existing Ethernet Ethernet packets.

In a possible implementation manner in combination with the first aspect, the first device may also send a second Ethernet packet to other devices. The specific methods are as follows:

The first device carries second identification information in the second Ethernet packet, where the second identification information is used to indicate that the first device supports processing the first Ethernet type packet, and the first Ethernet type packet includes the frame length Ethernet packet less than 64 bytes; finally, the first device sends the second Ethernet packet.

In this embodiment, when the first device supports processing of the first Ethernet type packet, the identification information is carried for the Ethernet packet whose frame length is less than 64 bytes, so that other devices in the Ethernet protocol stack that support processing the first Ethernet type packet It can receive and process Ethernet packets whose frame length is less than 64 bytes, thereby improving the packet throughput rate of the Ethernet network. Since the Ethernet packets whose frame length is less than 64 bytes no longer need to be filled, the packet overhead is reduced. , thereby improving the transmission efficiency of the first device.

With reference to the first aspect, in a possible implementation manner, the first device may further perform the following steps before sending the second Ethernet packet:

In a possible implementation manner, the first device determines whether it supports processing the first ether type packet, and if the first device supports processing the first ether type packet, the first device executes the execution in the second ether type packet. The operation of carrying the second identification information in the packet. That is, as long as the first device enables itself to support processing the first Ethernet type message, it does not need to judge the frame length of the second Ethernet message, and can directly carry the second identification information in the second Ethernet message.

In another possible implementation manner, the first device determines the frame length of the second Ethernet packet and whether it supports processing the first Ethernet type packet; if the first device supports processing the first Ethernet type packet , and the frame length of the second Ethernet packet is less than 64 bytes, the first device will perform the operation of carrying the second identification information in the second Ethernet packet. That is, when the first device enables itself to support the processing of the first Ethernet type packet, it also needs to judge the frame length of the second Ethernet packet. The second identification information is carried in the Ethernet packet.

Optionally, in combination with the above solution, in the existing Ethernet processing process, the first device may implement the solution that supports the first Ethernet type message and the solution that does not support the first Ethernet type message. as follows:

When the first device enables itself to support the processing of the first ether type packet, the first device can execute the above solution; if the first device enables itself to not support processing the first ether type packet, the first device A device can perform the following schemes:

If the first device does not support processing the first Ethernet packet, and the frame length of the second Ethernet packet is less than 64 bytes, the first device fills the frame length of the second Ethernet packet to 64 bytes section, and then the first device sends the filled second Ethernet packet; if the first device does not support processing the first Ethernet type packet, and the frame length of the second Ethernet packet is greater than 1518 bytes , the first device truncates the frame length of the second Ethernet packet to 1518 bytes, and then sends the truncated Ethernet packet with a frame length of 1518 bytes, while the Ethernet packet exceeding 1518 bytes is sent. It will be judged again before sending. For example, after truncating the second Ethernet packet to 1518 bytes, the part of the second Ethernet packet exceeding 1518 bytes is sent as the next Ethernet packet. If the frame length of the part exceeding 1518 bytes is less than 64 bytes, it will be padded to 64 bytes before sending; if the frame length of the part exceeding 1518 bytes will be greater than 1518 bytes, it will be truncated to 1518 bytes later send. Regardless of whether the first device supports processing the first Ethernet type packet, but the frame length of the second Ethernet packet is greater than or equal to 64 bytes and less than or equal to 1518 bytes, the first device can directly send the first Ethernet packet. Two Ethernet packets. In this way, small packets (Ethernet packets with a frame length of less than 64 bytes), large packets (Ethernet packets with a frame length greater than 1518 bytes) and existing Ethernet packets can be compatible at the same time.

In the above solution, the first device can read the identification information in its own register to enable itself whether it supports processing the first ether type message. For example, the first device can be implemented to support processing the first Ethernet through hardware upgrades at the physical layer (such as applying a new chip, or flashing a new field programmable gate array (FPGA code)) Type of message function.

With reference to the above aspects, in a possible implementation manner, the first Ethernet type packet further includes an Ethernet packet with a frame length greater than or equal to 64 bytes and less than or equal to 1518 bytes. That is, the first device identifies an Ethernet packet with any frame length.

With reference to the first aspect, the specific method of processing the first Ethernet packet by the first device according to the first identification information may be implemented in the following possible ways:

In a possible implementation, the first device detects the preamble that the first Ethernet message generates at the media access control layer (media access control, MAC), and the frame head delimiter (start frame delimiter, SFD) location information as the first identification information; then the first device processes the first Ethernet packet according to the first identification information. That is, in the preamble, the position information of the frame header delimiter which is different from the existing Ethernet packet can be used as the first identification information.

In another possible implementation manner, the first device detects a preamble generated by the first Ethernet packet at the MAC layer, and the target identification field in the preamble is used as the first identification information; An identification information processes the first Ethernet packet. That is, in the preamble, a specific identification field can be used as the first identification information. Specifically, the target identification field may be located at any position after the SFD and before the cyclic redundancy check (cyclic redundancy check, CRC). It can be understood that the position information of the frame head delimiter and the target identification field can be used as the first identification information at the same time, as long as the frame length of the first Ethernet packet can be correctly indicated. In this embodiment, the target identification field may also be referred to as a computing Ethernet identification (Computing Ethernet), a computing identification (Computing) or a mini frame (Mini Frame) identification, a flexible Ethernet identification (Flex Ethernet), and the like. Specifically, it can be other unused fields such as 0x5F.

In another possible implementation manner, the first device detects the encoding of the first Ethernet packet generated by a physical coding sublayer (PCS), wherein the encoded block type is used as the first identification information; then The first device processes the first Ethernet packet according to the first identification information. It can be understood that the encoding of the block type may be different from the encoding of the existing block type. For example, 0x00; or you can select codes that are not selected in the IEEE 802.3-2018 table, but you need to ensure that the Hamming distance from other codes is at least 4, such as 0xE1. In this embodiment, the encoded block type may include the block type of at least one block generated during the encoding process of the first Ethernet packet. For example, two blocks (blocks) are generated in the first Ethernet packet during the encoding process, and the block type of the start block of the first Ethernet packet can be used to indicate the first identification information; the first Ethernet packet can be used to indicate the first identification information. The block type of the second block indicates the first identification information; the first identification information can be indicated by the block type of the start block of the first Ethernet packet and the block type of the second block at the same time. The specific method is not limited here.

It can be understood that, in the above two manners, the first devices can be used separately or simultaneously. That is, the first device can independently detect the first identification information carried in the MAC layer, can detect the first identification information carried in the PCS layer alone, or can simultaneously detect the first identification information carried in the MAC layer and the PCS layer. The above describes the method for the first device to detect the first identification information carried in the first Ethernet packet. When the first device carries the second identification information in the second Ethernet packet, the above-mentioned manner may also be used. The details are not repeated here.

In combination with the above possible implementations, if the first identification information is only used to indicate that the second device can support processing the first Ethernet type packet, the first device can also detect the first Ethernet packet carried in the first Ethernet packet for indicating The service type identifier of the frame length type of the first Ethernet packet. Here, the frame length type of the first Ethernet packet may be a small packet (that is, an Ethernet packet with a frame length of less than 64 bytes), a large packet (that is, an Ethernet packet with a frame length greater than 1518 bytes), and a frame Ethernet packets whose length is less than or equal to 64 bytes and less than or equal to 1518 bytes. Therefore, the specific manner in which the first device detects the service type identifier carried in the first Ethernet packet may be as follows:

In a possible implementation manner, the first device detects the service type identifier carried in the preamble of the first Ethernet packet. Specifically, the second device may use different identification fields to identify the frame length type of the Ethernet packet. The service type identifier may be located after the above target identifier field and before the CRC.

In another possible implementation manner, when the first device detects that the first Ethernet packet is encoded at the PCS layer, the service type identifier carried in at least one byte after the block type of the first Ethernet packet .

Optionally, in this embodiment, the first Ethernet type packet may also include an Ethernet packet with a frame length greater than 1518 bytes. In this embodiment, the processing method of the Ethernet packet whose frame length is greater than 1518 bytes is the same as that of the Ethernet packet whose frame length is less than 64 bytes, and details are not described herein again.

With reference to the first aspect, in a possible implementation manner, before processing the first Ethernet packet, the first device may further negotiate with the second device to determine whether both parties support processing the first Ethernet type packet. For example, the first device is switch A, the second device is switch B that is on the same link with switch A, and data transmission is performed between switch A and switch B.

Optionally, the first device and the second device may negotiate in the following possible implementation manners:

In a possible implementation manner, the first device and the second device negotiate whether to support processing the first Ethernet packet by sending an auto-negotiation pulse, and the auto-negotiation pulse carries negotiation information, and the negotiation information is used for Instructing the first device or the second device to support processing of the first Ethernet type packet.

Optionally, the bits that have not been used in the link code word base page of the self-negotiation pulse indicate the negotiation information; or the message code value (that is, the Message Code value in the link code word extension page of the self-negotiation pulse) value) indicates the negotiation information.

In another possible implementation manner, the first device and the second device negotiate whether to support processing the first Ethernet type packet by sending and sending a link layer discovery protocol (LLDP). Carrying the negotiation information, where the negotiation information is used to indicate that the first device or the second device supports processing the first Ethernet type packet.

Optionally, an elastic Ethernet TLV type is generated in the LLDP, and the TLV type indicates the negotiation information. In a second aspect, an embodiment of the present application provides a method for processing an Ethernet packet, which specifically includes: when a first device sends a second Ethernet packet, carrying second identification information in the second Ethernet packet, and the first device carries second identification information in the second Ethernet packet. The second identification information is used to indicate that the first device supports processing of the first Ethernet type packet, and the first Ethernet type packet includes an Ethernet packet whose frame length is less than 64 bytes; then the first device sends the second Ethernet packet message.

When the first Ethernet type packet includes Ethernet packets with multiple frame lengths, it may be called a Flex Frame (Flex Frame or Flex Ethernet Frame) type packet or a Computing Ethernet (Computing Ethernet) type packet; and for different frames Long Ethernet packets, which may have other names. For example, for an Ethernet packet whose frame length is less than 64 bytes, the first Ethernet type packet may also be referred to as a mini frame/mini frame (Mini Frame) type packet.

In combination with the first aspect, in a possible implementation manner, during the transmission of an Ethernet packet, the first device may also receive a first Ethernet packet, where the first Ethernet packet carries first identification information, and the first Ethernet packet carries first identification information. The identification information is used to indicate that the second device supports processing of the first Ethernet type packet, the first Ethernet type packet includes an Ethernet packet with a frame length of less than 64 bytes, and the second device and the first device are in the same two ends of the link; then the first device processes the first Ethernet packet according to the first identification information.

In this embodiment, when receiving an Ethernet packet with a frame length of less than 64 bytes, the first device processes the Ethernet packet according to the identification information, so that the Ethernet protocol stack can support the Ethernet packet with a frame length of less than 64 bytes. Sending and processing improves the packet throughput of the Ethernet network.

With reference to the first aspect, in a possible implementation manner, the first device may further perform the following steps before processing the first Ethernet packet:

The first device determines the frame length of the first Ethernet packet and whether it supports processing the first Ethernet type packet; if the first device supports forwarding the Ethernet packet whose frame length is less than 64 bytes, and the If the frame length of an Ethernet packet is less than 64 bytes or the frame length of the first Ethernet packet is greater than 1518 bytes, the first device will perform an operation of processing the first Ethernet packet.

Optionally, if the first device does not support processing Ethernet packets whose frame length is less than 64 bytes or whose frame length is greater than 1518 bytes, and the frame length of the first Ethernet packet is less than 64 bytes or the first Ethernet packet If the frame length of the packet is greater than 1518 bytes, the first device discards the first Ethernet packet. In this way, small packets (Ethernet packets with a frame length of less than 64 bytes), large packets (Ethernet packets with a frame length greater than 1518 bytes) and existing Ethernet packets can be compatible at the same time.

With reference to the first aspect, in a possible implementation manner, the first identification information may further indicate that the frame length of the first Ethernet packet is greater than or equal to 64 bytes and less than or equal to 1518 bytes of Ethernet packets. That is, the first device identifies an Ethernet packet with any frame length.

With reference to the first aspect, the specific method for the first device to carry the second identification information in the second Ethernet packet may be implemented in the following possible ways:

In a possible implementation, the first device generates a preamble at the media access control layer (media access control, MAC), and the frame head delimiter (start frame delimiter, SFD) position information of the preamble is used as the second. identification information. That is, in the preamble, the position information of the frame header delimiter that is different from the existing Ethernet packet can be used as the second identification information.

In another possible implementation manner, the first device generates a preamble at the MAC layer, and a target identification field in the preamble is used as the second identification information. That is, in the preamble, a specific identification field can be used as the second identification information. Specifically, the target identification field may be located at any position after the SFD and before the cyclic redundancy check (cyclic redundancy check, CRC). It can be understood that the frame head delimiter position information and the target identification field can be used as the second identification information at the same time, as long as the frame length of the second Ethernet packet can be correctly indicated. In this embodiment, the target identification field may also be referred to as a computing Ethernet identification (Computing Ethernet), a computing identification (Computing) or a mini frame (Mini Frame) identification, a flexible Ethernet identification (Flex Ethernet), and the like. Specifically, it can be other unused fields such as 0x5F.

In another possible implementation manner, the first device generates a code of the second Ethernet packet in a physical coding sublayer (physical coding sublayer, PCS), where the block type of the code is used as the second identification information. It can be understood that the encoding of the block type may be different from the encoding of the existing block type. For example, 0x00; or you can select codes that are not selected in the IEEE802.3-2018 version table, but you need to ensure that the Hamming distance from other codes is at least 4, such as 0xE1. In this embodiment, the encoded block type may include the block type of at least one block generated during the encoding process of the second Ethernet packet. For example, in the encoding process of the second Ethernet packet, two blocks (blocks) are generated, and the block type of the start block of the second Ethernet packet can be used to indicate the second identification information; the second Ethernet packet can be used to indicate the second identification information. The block type of the second block of the second block indicates the second identification information; the block type of the start block of the second Ethernet packet and the block type of the second block can be used to indicate the second identification information. The specific method is not limited here.

It can be understood that, in the above two manners, the first devices can be used separately or simultaneously. That is, the first device may carry the second identification information at the MAC layer alone, may carry the second identification information at the PCS layer alone, or may simultaneously carry the second identification information at the MAC layer and the PCS layer. The above describes the method for the first device to carry the second identification information in the second Ethernet packet, and the second Ethernet packet may also be carried by other devices in the above-mentioned manner. The details are not repeated here.

In combination with the above possible implementations, if the second identification information is only used to indicate that the first device can support processing the first Ethernet type packet, the first device may also carry in the second Ethernet packet to indicate the The service type identifier of the frame length type of the second Ethernet packet. Here, the frame length type of the second Ethernet packet may be a small packet (that is, an Ethernet packet with a frame length of less than 64 bytes), a large packet (that is, an Ethernet packet with a frame length greater than 1518 bytes), and a frame Ethernet packets whose length is less than or equal to 64 bytes and less than or equal to 1518 bytes. Therefore, the specific manner in which the first device carries the service type identifier in the second Ethernet packet may be as follows:

In a possible implementation manner, the service type identifier is carried in the preamble of the second Ethernet packet. Specifically, the first device may use different identification fields to identify the frame length type of the Ethernet packet. The service type identifier may be located after the above target identifier field and before the CRC.

In another possible implementation manner, when the second Ethernet packet is encoded at the PCS layer, the service type identifier is carried in at least one byte after the block type of the second Ethernet packet.

With reference to the first aspect, in a possible implementation manner, before sending the second Ethernet packet, the first device may further negotiate with the second device to determine whether both parties support processing the first Ethernet type packet. At this time, the first device and the second device are devices at two ends of the same link. For example, the first device is switch A, the second device is switch B that is on the same link with switch A, and data transmission is performed between switch A and switch B.

Optionally, an elastic Ethernet TLV type is generated in the LLDP, and the TLV type indicates the negotiation information.

In a third aspect, the present application provides an Ethernet packet processing device having a function of implementing the behavior of the first device in the first aspect above. This function can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a possible implementation manner, the Ethernet packet processing device includes a unit or module for executing each step of the above first aspect. For example, the device includes: a transceiver module configured to receive a first Ethernet packet sent by a second device, where the first Ethernet packet carries first identification information, and the first identification information is used to indicate that the second device supports processing the first Ethernet packet. an ether type module, the first ether type message includes an ether message whose frame length is less than 64 bytes;

The processing module processes the first Ethernet packet according to the first identification information.

Optionally, it also includes a storage module for storing necessary program instructions and data of the first device.

In a possible implementation manner, the apparatus includes: a processor and a transceiver, where the processor is configured to support the first device to perform corresponding functions in the method provided in the first aspect. The transceiver is used to instruct the communication between the first device and the second device, and send the Ethernet packet involved in the above method to the second device. Optionally, the apparatus may further include a memory, which is used for coupling with the processor, and which stores necessary program instructions and data of the first device.

In a possible implementation manner, when the device is a chip in the first device, the chip includes: a processing module and a transceiver module. The transceiver module, which can be, for example, an input/output interface, a pin or a circuit on the chip, receives a signal received by the antenna, such as receiving the first Ethernet packet sent by the second device, and transmits the first Ethernet packet to the second device. An Ethernet packet is transmitted to other chips or modules coupled to this chip, wherein the first Ethernet packet carries first identification information, and the first identification information is used to indicate that the first device supports processing the first An Ethernet type packet, where the first Ethernet type packet includes an Ethernet packet whose frame length is less than 64 bytes. For example, the processing module may be a processor, and the processor is configured to process the first Ethernet packet according to the first identification information. The processing module can execute the computer-executed instructions stored in the storage unit, so as to support the first device to execute the method provided in the first aspect. Optionally, the storage unit can be a storage unit in the chip, such as a register, a cache, etc., and the storage unit can also be a storage unit located outside the chip, such as a read-only memory (read-only memory, ROM) or a memory unit. Other types of static storage devices that store static information and instructions, random access memory (RAM), etc.

In a possible implementation manner, the apparatus includes: a processor, a baseband circuit, a radio frequency circuit and an antenna. The processor is used to control the functions of each circuit part, and the baseband circuit is used to generate the Ethernet message, which is sent to the second device through the antenna after analog conversion, filtering, amplification and frequency up-conversion processing by the radio frequency circuit. Optionally, the apparatus further includes a memory, which stores necessary program instructions and data of the first device.

In one possible implementation, the apparatus includes a communication interface and logic circuitry. The communication interface is used to receive a first Ethernet packet sent by the second device, where the first Ethernet packet carries first identification information, and the first identification information is used to indicate that the first device supports processing the first Ethernet packet. An Ethernet type packet, where the first Ethernet type packet includes an Ethernet packet with a frame length of less than 64 bytes; the logic circuit is configured to process the first Ethernet packet according to the first identification information.

Wherein, the processor mentioned in any of the above may be a general-purpose central processing unit (Central Processing Unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more An integrated circuit for controlling program execution of the data transmission methods of the above aspects.

In a fourth aspect, the present application provides an Ethernet packet processing device, the Ethernet packet processing device having a function of implementing the behavior of the first device in the above-mentioned first aspect. This function can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a possible implementation manner, the Ethernet packet processing device includes a unit or module for executing each step of the above first aspect. For example, the device includes: a processing module configured to carry second identification information in the second Ethernet packet, where the second identification information is used to indicate that the first device supports processing of the first Ethernet type packet, the first Ethernet packet An Ethernet type packet includes an Ethernet packet whose frame length is less than 64 bytes;

A transceiver module, configured to send the second Ethernet message.

In a possible implementation manner, when the device is a chip in the first device, the chip includes: a processing module and a transceiver module. carries second identification information, where the second identification information is used to indicate that the first device supports processing a first Ethernet type packet, where the first Ethernet type packet includes an Ethernet packet with a frame length of less than 64 bytes. The transceiver module may be, for example, an input/output interface, a pin or a circuit on the chip, and transmits the Ethernet packet generated by the processor to other chips or modules coupled to the chip. The processing module can execute the computer-executed instructions stored in the storage unit, so as to support the first device to execute the method provided in the first aspect. Optionally, the storage unit can be a storage unit in the chip, such as a register, a cache, etc., and the storage unit can also be a storage unit located outside the chip, such as a read-only memory (read-only memory, ROM) or a memory unit. Other types of static storage devices that store static information and instructions, random access memory (RAM), etc.

In one possible implementation, the apparatus includes a communication interface and logic circuitry. The logic circuit is configured to carry second identification information in a second Ethernet packet, where the second identification information is used to indicate that the first device supports processing a first Ethernet type packet, and the first Ethernet type packet It includes an Ethernet packet whose frame length is less than 64 bytes; the communication interface is also used for sending the second Ethernet packet.

In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, where computer instructions are stored in the computer storage medium, and the computer instructions are used to execute the method in any possible implementation manner of any one of the foregoing aspects.

In a sixth aspect, the embodiments of the present application provide a computer program product including instructions, which, when executed on a computer, cause the computer to execute the method in any one of the foregoing aspects.

In a seventh aspect, the present application provides a chip system, the chip system includes a processor for supporting an Ethernet packet processing device to implement the functions involved in the above aspects, such as generating or processing the data involved in the above method and/or or information. In a possible design, the chip system further includes a memory, which is used for storing necessary program instructions and data of the device to realize the function of any one of the above aspects. The chip system can be composed of chips, and can also include chips and other discrete devices.

In an eighth aspect, an embodiment of the present application provides a communication system, where the system includes the Ethernet packet processing device of the above aspect.

Description of drawings

Figure 1 is a schematic diagram of the frame format of an IEEE 802.3 Ethernet message;

Figure 2 is a schematic diagram of the frame length constraint of the IEEE 802.3 MAC Frame;

3 is a combined schematic diagram of an Ethernet packet processing device in an embodiment of the application;

4a is a schematic flowchart of an Ethernet message sending side in an embodiment of the application;

FIG. 4b is another schematic flowchart of the sending side of the Ethernet message in the embodiment of the application;

FIG. 4c is a schematic flowchart of an Ethernet message receiving side in an embodiment of the present application;

5a is a schematic diagram of a system architecture in which the MAC layer carries identification information in an embodiment of the present application;

5b is a schematic diagram of a system architecture in which the PCS layer carries identification information in an embodiment of the application;

6 is a schematic diagram of an embodiment of a method for processing an Ethernet packet in an embodiment of the present application;

7 is a schematic diagram of a code block generated in 64b/66b encoding in an embodiment of the present application;

8 is a schematic diagram of a block format in 64b/66b encoding in an embodiment of the present application;

9 is a schematic diagram of the PCS layer utilizing the block type identification information in the embodiment of the application;

FIG. 10 is a schematic diagram of using the block type identification information by the PCS layer in the embodiment of the application

11 is a schematic diagram of the PCS layer utilizing block type identification information in the implementation of the application;

12 is a schematic diagram of the PCS layer utilizing the block type identification information in the embodiment of the application;

13 is a schematic diagram of another embodiment of a method for processing an Ethernet packet in an embodiment of the present application;

14 is a schematic diagram of another embodiment of a method for processing an Ethernet packet in an embodiment of the present application;

15 is a schematic diagram of another embodiment of a method for processing an Ethernet packet in an embodiment of the present application;

16 is a schematic diagram of another embodiment of a method for processing an Ethernet packet in an embodiment of the present application;

17 is a schematic diagram of another embodiment of a method for processing an Ethernet packet in an embodiment of the present application;

18 is a schematic diagram of another embodiment of a method for processing an Ethernet packet in an embodiment of the present application;

FIG. 19 is a schematic diagram of an embodiment in which a first device and a second device negotiate and determine to support a first Ethernet type packet in an embodiment of the present application;

Fig. 20a is the format schematic diagram of LCW Base Page;

Figure 20b is a schematic diagram of selecting a bit that has not been used at present in the LCW Base Page to identify the support for the first ether type message;

Figure 20c is a schematic diagram of the format of the Message Next page in the LCW extended page;

Figure 20d is a schematic diagram of the format of the Unformatted Next page in the LCW extended page;

FIG. 21 is a schematic diagram of another embodiment in which the first device and the second device negotiate and determine to support the first ether type packet in the embodiment of the application;

22 is a schematic diagram of the format of LLDP carrying negotiation information in an embodiment of the present application;

23 is a schematic structural diagram of an Ethernet packet processing device in an embodiment of the application;

FIG. 24 is a schematic structural diagram of an Ethernet packet processing device in an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application are described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. . Those of ordinary skill in the art know that with the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

The terms "first", "second" and the like in the description and claims of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It is to be understood that data so used may be interchanged under appropriate circumstances so that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or modules is not necessarily limited to those expressly listed Rather, those steps or modules may include other steps or modules not expressly listed or inherent to the process, method, product or apparatus. The naming or numbering of the steps in this application does not mean that the steps in the method flow must be executed in the time/logical sequence indicated by the naming or numbering, and the named or numbered process steps can be implemented according to the The technical purpose is to change the execution order, as long as the same or similar technical effects can be achieved. The division of units in this application is a logical division. In practical applications, there may be other division methods. For example, multiple units may be combined or integrated into another system, or some features may be ignored. , or not implemented, in addition, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, and the indirect coupling or communication connection between units may be electrical or other similar forms. There are no restrictions in the application. In addition, the units or sub-units described as separate components may or may not be physically separated, may or may not be physical units, or may be distributed into multiple circuit units, and some or all of them may be selected according to actual needs. unit to achieve the purpose of the scheme of this application.

The technical solutions in the embodiments of the present application will be clearly described below with reference to the accompanying drawings in the embodiments of the present application. In the description of this application, unless otherwise stated, "/" means or means, for example, A/B can mean A or B; "and/or" in this application is only an association relationship that describes an associated object , which means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the present application, "at least one item" refers to one or more items, and "multiple items" refers to two or more items. "At least one item(s) below" or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one item (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .

In the current standard, the MAC frame format is shown in Figure 1, that is, an IEEE 802.3 Ethernet packet consists of a 7-byte preamble, a 1-byte start frame delimiter (SFD), and a 2-byte frame delimiter (SFD). Type/length (length/type), 6-byte source address field (source address) and 6-byte destination address field (destination address), payload (Payload), 4-byte frame check code sequence (Frame Check Sequence, FCS) and 12-byte frame interval (interpacket gap, IPG). Among them, the MAC frame contains, type length, address, payload and FCS fields. According to the frame length constraint of IEEE 802.3MAC Frame as shown in Figure 2, it can be known that: at the sending end, the minimum frame length of the Ethernet packet must meet 64 bytes, otherwise it needs to be filled to 64 bytes for transmission; the maximum length of the Ethernet basic frame It cannot exceed 1518 bytes, otherwise it needs to be truncated to 1518 bytes and sent; at the receiving end, when receiving an Ethernet packet with a frame length less than 64 bytes or an Ethernet packet with a frame length greater than 1518 bytes, the Ethernet packet is discarded. This will result in insufficient forwarding performance of Ethernet in applications with many small packets, while in applications with many large packets, Ethernet has a large overhead.

In order to solve the above problems, the embodiments of the present application provide the following technical solutions: when the first device sends the first Ethernet packet, the first identification information is carried in the first Ethernet packet, and the first identification information is used to indicate the The first device supports processing a first Ethernet type packet, where the first Ethernet type packet includes an Ethernet packet whose frame length is less than 64 bytes; and then the first device sends the first Ethernet packet. The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), Universal Mobile Communication system (universal mobile telecommunication system, UMTS), 5G communication system, and future wireless communication system, etc.

In this application, the first device may be user equipment or network equipment. User Equipment (UE) may also refer to terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication equipment, user agent or user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks or in future evolved PLMN networks, etc. The network device may be a device used to communicate with user equipment, for example, it may be a base station (base transceiver station, BTS) in a GSM system or CDMA, or a base station (nodeB, NB) in a WCDMA system, or It is an evolved base station (evolutional node B, eNB or eNodeB) in the LTE system, or the network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, and a network-side device in a 5G network or a public land that evolves in the future Network equipment in a mobile network (public land mobile network, PLMN) network, etc.

FIG. 3 is a schematic diagram of a hardware structure of an Ethernet packet processing device in an embodiment of the present application. The Ethernet packet processing device may be a possible implementation manner of the first device in the embodiment of the present application. As shown in FIG. 3 , the Ethernet packet processing device includes at least a processor 304 , a memory 303 , and a transceiver 302 , and the memory 303 is further configured to store instructions 3031 and data 3032 . Optionally, the Ethernet packet processing device may further include an antenna 306 , an I/O (input/output, Input/Output) interface 310 and a bus 312 . The transceiver 302 further includes a transmitter 3021 and a receiver 3022. In addition, the processor 304 , the transceiver 302 , the memory 303 and the I/O interface 310 are communicatively connected to each other through the bus 312 , and the antenna 306 is connected to the transceiver 302 .

The processor 304 may be a general-purpose processor, such as, but not limited to, a central processing unit (CPU), or a special-purpose processor, such as, but not limited to, a digital signal processor (DSP), an application Application specific integrated circuit (ASIC) and field programmable gate array (FPGA), etc. The processor 304 may also be a neural network processing unit (NPU). Furthermore, the processor 304 may also be a combination of multiple processors. In particular, in the technical solutions provided in the embodiments of the present application, the processor 304 may be configured to execute relevant steps of the method for generating an Ethernet packet in the subsequent method embodiments. The processor 304 may be a processor specially designed to perform the above steps and/or operations, or may be a processor that performs the above steps and/or operations by reading and executing the instructions 3031 stored in the memory 303, the processor 304 Data 3032 may be required in performing the steps and/or operations described above.

The transceiver 302 includes a transmitter 3021 and a receiver 3022 , and in an optional implementation manner, the transmitter 3021 is used to transmit signals through the antenna 306 . The receiver 3022 is used to receive signals through at least one of the antennas 306 . In particular, in the technical solutions provided by the embodiments of the present application, the transmitter 3021 may be specifically configured to be executed by at least one antenna among the antennas 306. For example, the method for processing an Ethernet packet in the subsequent method embodiments is applied to the Ethernet packet. The operation performed by the receiving module or the sending module in the Ethernet packet processing device.

In this embodiment of the present application, the transceiver 302 is configured to support the Ethernet packet processing device to perform the aforementioned receiving function and sending function. A processor with processing capabilities is considered processor 304 . The receiver 3022 may also be referred to as an input port, a receiving circuit, and the like, and the transmitter 3021 may be referred to as a transmitter or a transmitting circuit, or the like.

The processor 304 may be configured to execute the instructions stored in the memory 303 to control the transceiver 302 to receive messages and/or send messages, so as to complete the function of the Ethernet packet processing device in the method embodiment of the present application. As an implementation manner, the function of the transceiver 302 may be implemented by a transceiver circuit or a dedicated chip for transceiver. In this embodiment of the present application, receiving a message by the transceiver 302 may be understood as an input message by the transceiver 302 , and sending a message by the transceiver 302 may be understood as an output message by the transceiver 302 .

The memory 303 may be various types of storage media, such as random access memory (Random Access Memory, RAM), read only memory (Read Only Memory, ROM), non-volatile RAM (Non-Volatile RAM, NVRAM), or Programmable ROM (Programmable ROM, PROM), Erasable PROM (Erasable PROM, EPROM), Electrically Erasable PROM (Electrically Erasable PROM, EEPROM), Flash memory, optical memory and registers, etc. The memory 303 is specifically used to store the instructions 3031 and the data 3032, and the processor 304 can perform the steps and/or operations described in the method embodiments of the present application by reading and executing the instructions 3031 stored in the memory 303. Data 3032 may be required during the operations and/or steps of a method embodiment.

Optionally, the Ethernet packet processing device may further include an I/O interface 310, where the I/O interface 310 is configured to receive instructions and/or data from peripheral devices, and output instructions and/or data to peripheral devices.

In the technical solution provided by the present application, the transmission process of the Ethernet message mainly includes the sending process and the receiving process of the Ethernet message.

Please refer to FIG. 4a. FIG. 4a is an exemplary process flow of sending an Ethernet packet by the sender. In this sending process flow, when an Ethernet packet is to be sent, the Ethernet packet processing device determines whether the frame length of the Ethernet packet is less than 64 bytes or greater than 1518 bytes; if so, the Ethernet packet processing device Determine whether it supports processing the first Ethernet type packet; if not, the Ethernet packet processing device directly processes and sends according to the existing Ethernet packet sending process; if the Ethernet packet processing device enables itself to support processing the first Ethernet packet Ethernet type packet, the Ethernet packet processing device carries the identification information in the Ethernet packet for identifying that the Ethernet packet processing device supports processing the first Ethernet type packet, and then processes and sends it. If the Ethernet packet processing device is enabled and does not support processing the first Ethernet type packet, the Ethernet packet processing device fills the frame length of the Ethernet packet to 64 bytes according to the existing Ethernet packet processing flow or adds The frame length of the Ethernet packet is truncated to 1518 bytes before being processed and sent.

Please refer to FIG. 4b. FIG. 4b is another exemplary process flow of sending an Ethernet packet by the sender. In this sending process flow, when an Ethernet packet is to be sent, the Ethernet packet processing device determines whether it supports processing the first Ethernet type packet, and if so, the Ethernet packet processing device carries the Ethernet packet Identification information used to identify that the Ethernet packet processing device supports processing the first Ethernet type packet, and then processes and sends it; if the Ethernet packet processing device is enabled to not support processing the first Ethernet type packet, the Ethernet packet The packet processing device determines whether the frame length of the Ethernet packet is less than 64 bytes or greater than 1518 bytes; if the frame length of the Ethernet packet is greater than or equal to 64 bytes and less than or equal to 1518 bytes, the Ethernet packet processing device directly Processing and sending according to the existing Ethernet packet sending process; if the frame length of the Ethernet packet is less than 64 bytes or greater than 1518 bytes, the Ethernet packet processing device sends the Ethernet packet according to the existing Ethernet packet processing process. The frame length of the message is padded to 64 bytes or the frame length of the Ethernet message is truncated to 1518 bytes, and then processed and sent.

Please refer to FIG. 4c, which is an exemplary process flow of receiving an Ethernet packet by a receiving end. In this receiving processing flow, after the receiving end receives the Ethernet packet, the Ethernet packet processing device determines whether it supports processing the first Ethernet type packet; if so, the Ethernet packet processing device determines whether the Ethernet packet contains Carrying identification information for identifying the first Ethernet type packet, if the Ethernet packet processing device determines that the Ethernet packet carries identification information for identifying the first Ethernet type packet, it directly processes and forwards it; If the packet processing device determines that it does not support processing the first Ethernet type packet or the Ethernet packet processing device determines that the Ethernet packet does not carry identification information for identifying the first Ethernet type packet, the Ethernet packet processing device will The Ethernet packet is subjected to MAC layer frame length detection; it is judged whether the frame length of the Ethernet packet is less than 64 bytes or greater than 1518 bytes; if not, the Ethernet packet processing device processes the Ethernet packet according to the existing Ethernet packet receiving and processing flow Forward the Ethernet packet, and if so, discard the Ethernet packet.

Based on the above processing flow, in order to implement the identification information carried in the Ethernet packet, the embodiments of the present application provide system architecture diagrams of the following methods for processing Ethernet packets. Please refer to a system architecture diagram shown in FIG. 5a, the Ethernet message processing device is below the existing MAC layer and above the reconciliation sublayer (RS), and the Ethernet message processing device is identified by a preamble to support Process the first ether type packet. Please refer to a system architecture diagram shown in FIG. 5b, the Ethernet message processing device is below the RS layer and above the PCS layer, and the Ethernet message processing device supports the first Ethernet type message by using the encoded block type to identify.

First, some nouns in the embodiments of the present application are described:

The first Ethernet type packet: it includes an Ethernet packet whose frame length is less than 64 bytes. It can be understood that, when the Ethernet packet processing device enables all Ethernet packets to carry identification information, the first Ethernet type packet may also include an Ethernet packet whose frame length is greater than or equal to 64 bytes and less than or equal to 1518 bytes. Ethernet packets with a frame length greater than 1518 bytes. When it includes a plurality of frame length type Ethernet packets, the first Ethernet type packet may be referred to as a flexible Ethernet (Flex Frame or Flex Ethernet Frame) type packet or a computing Ethernet (Computing Ethernet) type packet. It can be understood that, for packets of different frame length types, the first Ethernet type packet may also have corresponding names. For example, an Ethernet packet whose frame length is less than 64 bytes can be called a mini frame/mini frame (Mini Frame) type packet.

Target identification field: or called Computing Ethernet, Computing, Flex Ethernet, or Mini Frame when the frame length of the Ethernet packet is less than 64 bytes Logo (Mini Frame), etc. It is specifically used to identify that the Ethernet packet processing device supports processing the first Ethernet type packet. Specifically, the target identification field can be located anywhere between the SFD and the CRC. The target identification field may specifically be other unused fields such as 0x5F.

Service type identifier: the frame length used to identify the Ethernet packet is less than 64 bytes or the frame length used to identify the Ethernet packet is greater than 1518 bytes. It can be understood that, when the Ethernet packet processing device enables all Ethernet packets to carry identification information, the service type identification can also identify that the frame length of the Ethernet packet is greater than or equal to 64 bytes and less than or equal to 1518 bytes.

The method part of the embodiment of the present application is described below. For convenience of description, the first device and the second device at two ends of the same link are used for introduction. Please refer to FIG. 6. FIG. 6 is a schematic diagram of an embodiment of an Ethernet packet processing method proposed by an embodiment of the present application, which specifically includes:

601. The first device carries first identification information in the first Ethernet packet, where the first identification information is used to indicate that the first device supports processing a first Ethernet type packet, and the first Ethernet type packet includes a frame Ethernet packets less than 64 bytes long.

In this embodiment, based on the system architecture diagram shown in FIG. 5a, it can be known that the first device can generate a preamble at the MAC layer, and the preamble carries the first identification information. Under the existing standard, the preamble together with the start marker contains a total of 8 bytes, and for different frames, there are differences in its format. For the common Ethernet shown in Table 1, the preamble includes 7 0x55 and 1 byte of 0xD5. The 0xD5 represents the SFD, and the SFD is located in the last byte of 8 bytes.

Table 1

0x55

0xD5

As shown in Table 2, the Ethernet Passive Optical Network (EPON) frame, the first byte and the second byte of the preamble are 0x55, and the third byte is 0xD5, as a logical chain Road identification (Logical Link identity, LLID) header delimiter (Start of LLID Delimiter, SLD), the sixth and seventh bytes are LLID, and the last byte is the CRC check code.

Table 2

0x55

0xD5

0x55

LLID

CRC

As shown in Table 3 or Table 4, the preemptive sent Ethernet identifier includes two definitions of preamble identifiers. The header delimiter (Start mPacket Delimiter, SMD) of the combined MAC packet has two meanings. Table 3 indicates that the Ethernet packet is a fragment of a complete packet, and is marked with a fragment count; Table 4 indicates that the Ethernet packet is an Express packet, or a complete packet that can be preempted , or the first fragment of a packet.

table 3

0x55

SMD

Frag-count

Table 4

0x55

SMD

Based on the above description, when the first device carries the first identification information in the preamble of the MAC layer, the following possible implementations can be adopted:

In a possible implementation manner, the first device generates a preamble at the MAC layer, and the position information of the frame header delimiter of the preamble is used as the first identification information. That is, as long as the location information of the SFD in the preamble is different from the location information of the SFD in the existing frame, the first identification information can be indicated. As shown in Table 5, the SFD of the preamble provided in this embodiment is located in the fourth byte, which means that the preamble carries the first identification information.

table 5

0x55

0xD5

0x55

CRC

In another possible implementation manner, the first device generates a preamble at the MAC layer, and a target identification field in the preamble is used as the first identification information. That is, a new identification field in the preamble is used to represent the first identification information. As shown in Table 6, the FE field of the fourth byte in the preamble provided by this embodiment (for example, 0x5F is used) represents the first identification information. In this solution, the target identification field may be located at any position between the SFD and the eighth byte (CRC), as long as the information of the first Ethernet packet can be completely identified.

Table 6

0x55

0xD5

0x5F

0x55

CRC

At the MAC layer, the preamble may further include a service type identifier for identifying the service type of the first Ethernet packet. As shown in Table 7, the SID is used to identify the service type.

Table 7

0x55

0xD5

0x5F

0x55

SID

CRC

It can be understood that, the service type identifier may be used in the preamble to identify the service type of the first Ethernet packet, or other manners may be used to identify the service type. For example, the target identification field selects different fields for identification. For example, the setting fields A, B, and C are used to indicate that the first device supports processing the first Ethernet type packet, but the field A is also used to identify the Ethernet packet as A small packet with a frame length of less than 64 bytes. This field B is used to identify an Ethernet packet as a large packet with a frame length greater than 1518 bytes. This field C is used to identify an Ethernet packet whose frame length is greater than or equal to 64 bytes. and less than or equal to 1518 bytes.

Similarly, when the SFD location information is used to indicate that the first device supports processing of the first Ethernet type packet, different location information may also identify different service types. For example, the set position A, position B and position C are all used to indicate that the first device supports processing the first Ethernet type packet, but the position A is also used to identify the Ethernet packet as a small packet with a frame length of less than 64 bytes The position B is used to identify the Ethernet packet as a large packet with a frame length greater than 1518 bytes, and the position C is used to identify the Ethernet packet as a packet with a frame length greater than or equal to 64 bytes and less than or equal to 1518 bytes .

In this embodiment, based on the system architecture diagram shown in FIG. 5b, it can be known that the first device can generate a code at the PCS layer, and the first identification information is indicated by the block type of the code.

In the existing standard, the PCS layer mainly performs coding (8b/10b or 64b/66b, etc., which are not limited here), scrambling code, and optionally forward error correction code (Forward Error Correction, FEC), and then distributed. In this embodiment, 64b/66b encoding is used for description. The encoding method of 64b/66b can be shown in Figure 7, that is, every 64 bits (bit) forms a block (block), and then adds a 2-bit header to form a 66-bit block. For each 66-bit block, it is classified into two types, namely, pure data blocks (with the sync header marked with 01) and control/control data blocks (with the sync header marked with 10). The first byte (8-bit) after the sync header of the latter is the block Type field, which identifies the data/control structure of the subsequent 7 bytes. The following takes the 64b/66b encoding of 40/100/200/400GBASE-R as an example to give the definition of the 64b/66b block format. As shown in Figure 8, the left control block format (control block format) identifies the input of the media interface (xGMII), and the right side is the corresponding 66bit code block after 64b/66b encoding. Among them, C represents the control signal, /S/ represents the start of the packet (Start of Packet, SOP), and /T/ represents the end of the packet (End of Packet, EOP). /O/ represents ordered sets, which are used to send remote/local failure status on the link. 0x1E indicates that the following 7 bytes are all control information; 0x78 indicates the start block of a data packet. T0 to T7 identify the possible ending positions of 8 packets. It can be seen that through different block type types, we can obtain the beginning and end of a message, and complete the delimitation of a message.

Based on the above description, when the first device carries the first identification information through encoding at the PCS layer, the following possible implementations may be adopted:

In a possible implementation manner, the first device encodes the first Ethernet packet at the PCS layer, and uses the encoded block type as the first identification information. As shown in Figure 9, the first device uses the block type 0x00 to identify the first identification information. It can be understood that the first Ethernet packet may be encoded to generate multiple code blocks during the encoding process, and for each code block, there is a block type identification field. When the first device uses the block type to identify the first identification information, the first device may use the block type of at least one code block for identification. As shown in Figure 9, the first Ethernet packet generates three code blocks during the encoding process, which are the first code block (also called the start block of the Ethernet packet), the second code block and the third code block. code block. Then this first Ethernet message can use the block type of the start block to identify the first identification information as shown in Figure 9; also can use the block type of the second code block to identify the first identification information as shown in Figure 10 ; Also as shown in Figure 11, use the block type of the 3rd code block to identify the first identification information; also as shown in Figure 12, use the start block, the second code block and the 3rd code The block type of the block identifies the first identification information. In this embodiment, the code of the block type may be 0x00, or it may be a code not selected in the IEEE 802.3-2018 version-5 table, and it is only necessary to ensure that the Hamming distance with other codes is at least 4, such as 0xE1.

At the PCS layer, the encoded code block may further include a service type identifier for identifying the service type of the first Ethernet packet. As shown in FIG. 9 to FIG. 12 , the P1 is used to identify the service type. The size of the P1 can be less than 1 byte, or greater than 1 byte (then it will occupy the space of the following D2). It can be understood that the encoded block type may also identify the service type of the first Ethernet packet. For example, the block type A, block type B and block type C are all set to indicate that the first device supports processing the first Ethernet type packet, but the block type A is also used to identify the Ethernet packet as having a frame length of less than 64 words The block type B is used to identify the Ethernet packet as a large packet with a frame length greater than 1518 bytes, and the block type C is used to identify the Ethernet packet as a frame length greater than or equal to 64 bytes and less than or equal to 1518-byte message.

In this embodiment, when the first device sends the first Ethernet packet, the MAC layer sends the indication information of the first Ethernet type packet to the xGMII interface, and then the xGMII interface generates a corresponding control word. At this time, the xGMII interface The control word generated by the interface is used to identify the first Ether type message; finally, when the PCS layer receives the data or control word sent by the xGMII interface, it performs corresponding encoding and converts the control word into a block type. It can be understood that, in this embodiment, xGMII is used to indicate a GMII interface of a certain rate. The name of the MII port for each rate is different. For example, at a rate of 400G, the corresponding GMII interface is a 200GMII interface or a 400GMII interface.

Based on the system architecture diagrams of FIG. 5a and FIG. 5b, the first device may carry the first identification information in the MAC layer and the PCS at the same time. The specific implementation is as described in the above solution, and details are not repeated here.

602. The first device sends the first Ethernet packet.

Optionally, on the sending side of the above Ethernet packet, the processing method of the Ethernet packet may also be as shown in Figure 13, which specifically includes:

1301. The first device determines whether the frame length of the first Ethernet packet is less than 64 bytes, and if so, executes step 1302, and if not, executes step 1306.

In this embodiment, the first device may determine the frame length of the first Ethernet packet by using the service type identifier in the first Ethernet packet;

Or, the first device detects the frame length of the MAC frame of the first Ethernet packet, and determines whether the frame length of the first Ethernet packet is less than 64 bytes.

1302. The first device determines whether it supports processing the first ether type packet, and if so, executes steps 1303 to 1304, and if not, executes step 1305.

In this embodiment, the first device reads the identification information in its own register, and determines whether it supports processing the first Ether type message according to the identification information. If the identification information indicates that the first device can support processing the first Ethernet type packet, the first device uses its own support to process the first Ethernet type packet.

1303. The first device carries the first identification information in the first Ethernet packet.

The first device may use the solution shown in step 601 to carry the first identification information in the first Ethernet packet.

1304. The first device sends the first Ethernet packet.

1305. The first device fills the frame length of the first Ethernet packet to 64 bytes, and sends it.

1306. The first device sends the first Ethernet packet, where the first Ethernet packet does not carry the first identification information.

Regarding the sending side of the above-mentioned Ethernet packet, the processing method of the Ethernet packet can also be shown in Figure 14, which specifically includes:

1401. The first device determines whether it supports processing the first ether type packet, if so, executes steps 1402 to 1403, and if not, executes step 1404.

In this embodiment, the first device reads the identification information in its own register, and determines whether it supports processing the first Ethernet type message according to the identification information. If the identification information indicates that the first device can support processing the first Ethernet type packet, the first device uses its own support to process the first Ethernet type packet.

1402. The first device carries the first identification information in the first Ethernet packet.

In this embodiment, the first device carries the first identification information for any Ethernet packet.

1403. The first device sends the first Ethernet packet.

1404. The first device determines whether the frame length of the first Ethernet packet is less than 64 bytes, and if so, executes step 1405, and if not, executes step 1406.

1405. The first device fills the frame length of the first Ethernet packet to 64 bytes, and sends it.

1406. The first device sends the first Ethernet packet, where the first Ethernet packet does not carry the first identification information.

It can be understood that the first Ether type packet also includes a large packet with a frame length greater than 1518 bytes. When the first Ethernet packet is an Ethernet packet with a frame length greater than 1518 bytes, the first device may also carry the first identification information in the first Ethernet packet in the above manner.

Optionally, on the sending side of the above-mentioned Ethernet packet, when the frame length of the Ethernet packet is greater than 1518 bytes, the processing method of the Ethernet packet may also be as shown in Figure 15, which specifically includes:

1501. The first device determines whether the frame length of the first Ethernet packet is greater than 1518 bytes, and if so, executes step 1502, and if not, executes step 1506.

Or, the first device detects the frame length of the MAC frame of the first Ethernet packet, and determines whether the frame length of the first Ethernet packet is greater than 1518 bytes.

1502. The first device determines whether it supports processing of the first ether type packet, and if so, executes steps 1503 to 1504, and if not, executes step 1505.

1503. The first device carries the first identification information in the first Ethernet packet.

1504. The first device sends the first Ethernet packet.

1505. The first device truncates the frame length of the first Ethernet packet to 1518 bytes, and sends it.

1506. The first device sends the first Ethernet packet, where the first Ethernet packet does not carry the first identification information.

In terms of the sending side of the above-mentioned Ethernet packet, the processing method of the Ethernet packet can also be as shown in Figure 16, which specifically includes:

1601. The first device determines whether it supports the processing of the first ether type packet, and if so, executes steps 1602 to 1603, and if not, executes step 1604.

1602. The first device carries the first identification information in the first Ethernet packet.

1603. The first device sends the first Ethernet packet.

1604. The first device determines whether the frame length of the first Ethernet packet is greater than 1518 bytes, and if so, executes step 1605, and if not, executes step 1606.

Alternatively, the first device may determine the frame length of the first Ethernet packet by using the service type identifier in the first Ethernet packet;

1605. The first device truncates the frame length of the first Ethernet packet to 1518 bytes, and sends it.

1606. The first device sends the first Ethernet packet, where the first Ethernet packet does not carry the first identification information.

It can be understood that, in the description of the Ethernet packet sending process performed by the first device as the sender, the mentioned first Ethernet packet is substantially equivalent to the second Ethernet packet in the claims of this application. The identification information is substantially equivalent to the second identification information in the claims of the present application.

The processing of the Ethernet packet in the embodiment of the present application will be described below with reference to the receiving processing flow of the Ethernet packet. Please refer to FIG. 17. FIG. 17 is a schematic diagram of an embodiment of an Ethernet packet processing method proposed by an embodiment of the present application, which specifically includes:

1701. The first device receives a second Ethernet packet.

In this embodiment, the first device receives the second Ethernet packet sent by the peer device through an antenna or other interface.

1702. The first device determines whether it supports processing of the first ether type packet, and if so, executes step 1703, and if not, executes step 1705.

1703. The first device determines whether the second Ethernet packet carries second identification information, where the second identification information is used to indicate that the peer device supports processing of the first Ethernet type packet, and the first Ethernet type packet includes a frame For the Ethernet packet whose length is less than 64 bytes, if yes, go to step 1704; if not, go to step 1705.

In this embodiment, the first device detects whether there is an identifier indicating the second identification information in the preamble of the second Ethernet packet or detects whether there is an identifier indicating the second identification information in the encoding, and if so, determines whether there is an identifier indicating the second identification information. The second Ethernet packet carries the second identification information, and the second Ethernet packet is a first Ethernet type packet. 1704. The first device processes the second Ethernet packet.

The first device directly decodes the second Ethernet packet or forwards the second Ethernet packet.

1705. The first device determines whether the frame length of the second Ethernet packet is less than 64 bytes, and if so, executes step 1706, and if not, executes step 1704.

In this embodiment, the first device may determine the frame length of the second Ethernet packet through the service type identifier in the second Ethernet packet;

or,

The first device detects the MAC frame length of the second Ethernet packet, so as to determine the frame length of the second Ethernet packet.

1706. The first device discards the second Ethernet packet.

Optionally, on the receiving side of the above-mentioned Ethernet packet, when the frame length of the Ethernet packet is greater than 1518 bytes, the processing method of the Ethernet packet may also be as shown in FIG. 18 , which is implemented in this application. A schematic diagram of an embodiment of an Ethernet packet processing method proposed in this example, which specifically includes:

1801. The first device receives a second Ethernet packet sent by the second device.

In this embodiment, the first device receives the second Ethernet packet sent by the second device through an antenna or other interface.

1802. The first device determines whether it supports processing of the first ether type packet, and if so, executes step 1803, and if not, executes step 1805.

1803. The first device determines whether the second Ethernet packet carries second identification information, where the second identification information is used to indicate that the second device supports processing a first Ethernet type packet, and the first Ethernet type packet includes a frame For an Ethernet packet longer than 1518 bytes, if yes, go to step 1804; if not, go to step 1805.

In this embodiment, the first device detects whether there is an identifier indicating the second identification information in the preamble of the second Ethernet packet or detects whether there is an identifier indicating the second identification information in the encoding, and if so, determines whether there is an identifier indicating the second identification information. The second Ethernet packet carries the second identification information, and the second Ethernet packet is a first Ethernet type packet.

1804. The first device processes the second Ethernet packet.

1805. The first device determines whether the frame length of the second Ethernet packet is greater than 1518 bytes, and if so, executes step 1806, and if not, executes step 1804.

or,

1806. The first device discards the second Ethernet packet.

It can be understood that, in the description of the above-mentioned first device as the receiving end to receive the Ethernet packet, the mentioned second Ethernet packet is substantially equivalent to the first Ethernet packet in the claims of this application, and the first The second identification information is substantially equivalent to the first identification information in the claims of this application. In the above solution, the first device can be understood as only to determine whether it supports the first Ethernet type message, and does not determine whether the peer device also supports processing the first Ethernet type message. However, in this embodiment, the first device and the second device at both ends of the same link may further negotiate to determine whether both parties support processing the first Ether-type packet. Referring to FIG. 19 , in this embodiment of the present application, an exemplary process for negotiating between the first device and the second device to determine whether to support processing of the first Ethernet type packet includes:

1901. The first device sends a first auto-negotiation pulse to the second device, where the first auto-negotiation pulse carries negotiation information, where the negotiation information is used to indicate that the first device supports processing of the first ether type packet.

Before the first device and the second device send/receive the foregoing first Ethernet type packet, the first device and the second device may negotiate whether the two parties are in a link layer auto-negotiation (AN) manner. It has the ability to support the processing of the first Ethernet type message. AN is an optional function provided by IEEE 802.3. Devices at both ends of the link negotiate two end capability. In this embodiment, the auto-negotiation pulse will carry negotiation information used to instruct the first device to support processing the first Ethernet type packet, and the negotiation information may be data information in the auto-negotiation pulse. The data information in the auto-negotiation pulse is encoded through a differential Manchester (Differential Manchester Encoding, DME) page. Each 48bit Data constitutes a DME page, that is, a link code word (LCW). The entire negotiation information can be composed of LCW base page and extended page. Therefore, when the auto-negotiation pulse carries the negotiation information, the following possible implementations can be adopted:

In a possible implementation manner, unused bits are used in the LCW Base Page to identify the support for the first ether type message. The format of the LCW Base Page shown in Figure 20a is known. A bit that has not been used at present may be selected from the technical capability information indicated by A0 to A26 to identify the support for the first Ethernet type message. A19, as shown in Figure 20b, is D40.

In another possible implementation manner, the message code value is used in the LCW extended page to identify the support of the first ether type message. In the existing standard, the LCW extended page has two encoding formats (Message Next page and Unformatted Next page), as shown in Figures 20c and 20d. The encoding format of the Message Next page shown in Figure 20c carries the Message Code Field, which means that the specific Message Page format is defined. The encoding format of the Unformatted Next page shown in Figure 20d is Unformatted page encoding, an unformatted page. These two formats are judged according to the setting of the Message Page (MP) bit. When MP is set to 1, it means Message page; when it is set to 0, it means unformatted page. According to the setting of Message Code Field, determine the meaning of subsequent D16~D47 positions. Based on the above description, the first device can generate a message code value in the Message Code Field to identify support for the first ether type message.

1902. The first device receives a second auto-negotiation pulse sent by the second device, where the second auto-negotiation pulse carries negotiation information, where the negotiation information is used to indicate that the second device supports processing of the first Ethernet type packet.

Similarly, the manner in which the negotiation information is carried in the second auto-negotiation pulse sent by the second device is the same as the manner in which the negotiation information is carried in the first auto-negotiation pulse in step 1901, and details are not repeated here.

1903. The first device determines, according to the second auto-negotiation pulse, that the second device supports processing of the first Ether-type packet, and enables itself to support the processing of the first Ether-type packet.

After receiving the second auto-negotiation pulse, the first device detects whether there is negotiation information in the auto-negotiation pulse, so as to determine that the second device supports processing the first Ethernet type packet. If it is determined that the second device supports the processing of the first ether type packet, it enables itself to support processing the first ether type packet.

1904. The second device determines, according to the first auto-negotiation pulse, that the first device supports the processing of the first Ether-type packet, and enables itself to support the processing of the first Ether-type packet.

After receiving the first self-negotiation pulse, the second device detects whether there is negotiation information in the self-negotiation pulse, so as to determine that the first device supports processing of the first Ethernet type message. If it is determined that the first device supports the processing of the first Ether-type packet, it enables itself to support the processing of the first Ether-type packet.

During this auto-negotiation process, steps 1901 to 1904 may be repeated between the first device and the second device for many times, so as to achieve a consensus. If the first device and the second device cannot reach an agreement through negotiation, neither the first device nor the second device is enabled to support the processing of the first ether type packet, and notify other neighbors.

It can be understood that there is no time sequence defined between steps 1901 and 1902 , and no time sequence is defined between steps 1903 and 1904 .

Referring to FIG. 21 , in this embodiment of the present application, an exemplary process for negotiating between the first device and the second device to determine whether to support processing of the first Ethernet type packet includes:

2101. The first device sends a first link layer discovery protocol packet to the second device, where the first link layer discovery protocol carries negotiation information, and the negotiation information is used to indicate that the first device supports processing the first ether type message.

Before the first device and the second device send/receive the aforementioned first Ethernet type message, the first device and the second device may send a Link Layer Discovery Protocol (LLDP) message through the communication between the first device and the second device. way, negotiate to determine whether the two parties have the ability to support the first Ethernet type message. After the ports of the first device and the second device are enabled (UP), the first device sends a first LLDP protocol packet to the second device. Wherein, an 802.3TLV type is generated in the LLDP protocol message to identify the negotiation information. As shown in Figure 22, the LLDP message format used to identify the negotiation information is generated, wherein the TLV type=127 of the first byte indicates that it is Organizationally Specific TLVs, and the subsequent OUI is marked with 802.3, indicating that it is a capability defined by 802.3. And subtype=8 is used to express the capability negotiation of supporting the first ether type packet (Flex Eth) or calculating the ether type packet or the small frame type packet.

2102. The first device receives a second link layer discovery protocol packet sent by the second device, where the second link layer discovery protocol packet carries negotiation information, and the negotiation information is used to instruct the second device to support processing the first link layer. An Ethernet type packet.

Similarly, the manner in which the negotiation information is carried in the second link layer discovery protocol packet sent by the second device is the same as the manner in which the negotiation information is carried in the first link layer discovery protocol packet in step 2101. No longer.

2103. The first device determines, according to the second link layer discovery protocol message, that the second device supports processing the first Ethernet type packet, and enables itself to support processing the first Ethernet type packet.

After receiving the second link layer discovery protocol packet, the first device detects whether there is negotiation information in the second link layer discovery protocol packet, so as to determine that the second device supports processing the first ether type message. If it is determined that the second device supports the processing of the first ether type packet, it enables itself to support processing the first ether type packet.

2104. The second device determines, according to the first link layer discovery protocol message, that the first device supports processing of the first ether type packet, and enables itself to support processing the first ether type packet.

After receiving the first link layer discovery protocol packet, the second device detects whether there is negotiation information in the first link layer discovery protocol packet, so as to determine that the second device supports processing the first ether type message. If it is determined that the second device supports the processing of the first ether type packet, it enables itself to support processing the first ether type packet.

In this embodiment, the negotiation based on the LLDP protocol can be run only after the port is enabled (UP). That is, in this negotiation mode, the first Ethernet type packet capability is initially disabled. The first device sends an LLDP message carrying the Flex Eth capability flag to the second device, and performs negotiation to enable the sending and receiving of the first Ether-type message. This LLDP negotiation can be triggered at any time while the port is running. During this auto-negotiation process, the first device and the second device may repeat the steps 2101 to 2104 for many times, so as to achieve the purpose of negotiation. If the first device and the second device cannot reach an agreement through negotiation, neither the first device nor the second device is enabled to support the processing of the first ether type packet, and notify other neighbors.

It can be understood that there is no time sequence defined between steps 2101 and 2102 , and no time sequence is defined between steps 2103 and 2104 .

The Ethernet packet processing method in the embodiments of the present application has been described above. It can be understood that, in order to implement the above functions, the Ethernet packet processing device includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that the present application can be implemented in hardware or in the form of a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In this embodiment of the present application, the Ethernet packet processing device can be divided into functional modules according to the foregoing method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.

The following describes the Ethernet packet processing device in this application in detail, please refer to FIG. 23, which is a schematic diagram of an embodiment of the Ethernet packet processing device in the embodiment of the application. The Ethernet packet processing device can be deployed in a switch (or router), and the Ethernet packet processing device 2300 includes:

A transceiver module 2301, configured to receive a first Ethernet packet sent by a second device, where the first Ethernet packet carries first identification information, and the first identification information is used to indicate that the second device supports processing the first Ethernet Type message, the first Ethernet type message includes an Ethernet message whose frame length is less than 64 bytes;

The processing module 2302 is configured to process the first Ethernet packet according to the first identification information.

In a possible implementation manner, the processing module 2302 is further configured to determine the frame length of the first Ethernet packet and whether it supports processing the first Ethernet type packet; When the frame length is less than 64 bytes and the processing of the first Ethernet type packet is supported, the operation of processing the first Ethernet packet according to the first identification information is performed.

In a possible implementation manner, the processing module 2302 is further configured to discard the second Ethernet packet when processing the first Ethernet type packet is not supported and the first Ethernet packet is less than 64 bytes .

In a possible implementation manner, the processing module 2302 is further configured to carry second identification information in the second Ethernet packet, where the second identification information is used to indicate that the first device supports processing the first Ethernet type message, the first Ethernet type message includes an Ethernet message with a frame length of less than 64 bytes;

The transceiver module 2301 is configured to send the second Ethernet packet.

In a possible implementation manner, the processing module 2302 is further configured to determine the frame length of the second Ethernet packet and whether it supports processing the first Ethernet type packet; When the frame length is less than 64 bytes, and when processing the first Ethernet type packet is supported, the operation of carrying the second identification information in the second Ethernet packet is performed.

In a possible implementation manner, the processing module 2302 is further configured to process the second Ethernet packet when processing the first Ethernet packet is not supported and the frame length of the second Ethernet packet is less than 64 bytes. The frame length of the Ethernet packet is padded to 64 bytes and sent; when the processing of the first Ethernet type packet is not supported and the frame length of the second Ethernet packet is greater than or equal to 64 bytes and less than or equal to 1518 bytes, Send the second Ethernet packet, where the second Ethernet packet does not carry the second identification information.

In a possible implementation manner, the first Ethernet type packet further includes an Ethernet packet whose frame length is greater than or equal to 64 bytes.

In a possible implementation manner, the processing module 2302 is specifically configured to detect the preamble of the first Ethernet packet, and the position information of the frame header delimiter of the preamble is used as the first identification information; The first identification information is used to process the first Ethernet packet.

In a possible implementation manner, the processing module 2302 is specifically configured to detect the preamble of the first Ethernet packet, and the target identification field in the preamble is used as the first identification information; according to the first The identification information processes the first Ethernet packet.

In a possible implementation manner, the processing module 2302 is further configured to detect the first service type identifier carried in the preamble of the first Ethernet packet, where the first service type identifier is used to indicate the first service type identifier. Type of Ethernet packet.

In a possible implementation manner, the processing module 2302 is specifically configured to detect the encoding of the first Ethernet packet, and the encoded block type is used as the first identification information; Describe the first Ethernet packet.

In a possible implementation manner, the encoded block type is the block type of the start block of the first Ethernet packet.

In a possible implementation manner, the processing module 2302 is further configured to detect a second service type identifier carried in at least one byte after the encoded block type, where the second service type identifier is used to indicate the Type of the first Ethernet packet.

In a possible implementation manner, the processing module 2302 is further configured to negotiate with the second device to determine whether to support processing of the first Ethernet type packet.

In a possible implementation manner, the transceiver module 2301 is further configured to negotiate with the second device whether to support processing the first Ethertype packet by sending an auto-negotiation pulse, and the auto-negotiation pulse carries negotiation information, The negotiation information is used to indicate that the first device or the second device supports processing of the first Ethernet type packet;

or,

The transceiver module 2301 is further configured to negotiate with the second device whether to support processing the first Ethernet type packet by sending a link layer discovery protocol LLDP, where the link layer discovery protocol carries the negotiation information, The negotiation information is used to indicate that the first device or the second device supports processing of the first Ethernet type packet.

In a possible implementation manner, the unused bits in the link code word base page of the auto-negotiation pulse indicate the negotiation information;

or,

The message code value in the link code word extension page of the auto-negotiation burst indicates the negotiation information.

In a possible implementation manner, an elastic capability identifier TLV type is generated in the link layer discovery protocol, and the TLV type indicates the negotiation information.

The Ethernet packet processing device in the foregoing embodiment may be a network device or user equipment, or may be a chip applied in the network device or other combined devices or components that can implement the functions of the foregoing network device. When the Ethernet packet processing device is a network device, the transceiver module may be a transceiver, and the transceiver may include an antenna and a radio frequency circuit, and the processing module may be a processor, such as a baseband chip. When the Ethernet packet processing device is a component having the function of the above-mentioned Ethernet packet processing device, the transceiver module may be a radio frequency unit, and the processing module may be a processor. When the Ethernet packet processing device is a chip system, the receiving part of the transceiver module can be the input port of the chip system, the sending part of the transceiver module can be the output interface of the chip system, and the processing module can be the chip system A processor, such as a central processing unit (CPU).

In the embodiments of the present application, the memory included in the Ethernet packet processing device is mainly used to store software programs and data, for example, to store the programs described in the foregoing embodiments. The Ethernet packet processing device also has the following functions:

a transceiver, configured to receive a first Ethernet packet sent by a second device, where the first Ethernet packet carries first identification information, and the first identification information is used to indicate that the second device supports processing the first Ethernet type message, the first Ethernet type message includes an Ethernet message with a frame length of less than 64 bytes;

a processor, configured to process the first Ethernet packet according to the first identification information.

In a possible implementation manner, the processor is further configured to determine the frame length of the first Ethernet packet and whether it supports processing the first Ethernet type packet; When the length is less than 64 bytes and the processing of the first Ethernet type packet is supported, the operation of processing the first Ethernet packet according to the first identification information is performed.

In a possible implementation manner, the processor is further configured to discard the second Ethernet packet when the processing of the first Ethernet packet is not supported and the first Ethernet packet is smaller than 64 bytes.

In a possible implementation manner, the processor is further configured to carry second identification information in the second Ethernet packet, where the second identification information is used to indicate that the first device supports processing of the first Ethernet type packet. The first Ethernet type packet includes an Ethernet packet whose frame length is less than 64 bytes;

The transceiver is configured to send the second Ethernet packet.

In a possible implementation manner, the processor is further configured to determine the frame length of the second Ethernet packet and whether it supports processing the first Ethernet type packet; When the length is less than 64 bytes and the processing of the first Ethernet type packet is supported, the operation of carrying the second identification information in the second Ethernet packet is performed.

In a possible implementation manner, the processor is further configured to process the second Ethernet packet when processing the first Ethernet packet is not supported and the frame length of the second Ethernet packet is less than 64 bytes. The frame length of the packet is padded to 64 bytes and sent; when the first Ethernet type packet cannot be processed and the frame length of the second Ethernet packet is greater than or equal to 64 bytes and less than or equal to 1518 bytes, send For the second Ethernet packet, the second Ethernet packet does not carry the second identification information.

In a possible implementation manner, the processor is specifically configured to detect the preamble of the first Ethernet packet, and the position information of the frame header delimiter of the preamble is used as the first identification information; according to the The first identification information processes the first Ethernet packet.

In a possible implementation manner, the processor is specifically configured to detect the preamble of the first Ethernet packet, and the target identification field in the preamble is used as the first identification information; according to the first identification The information processes the first Ethernet packet.

In one possible implementation, the processor is further configured to detect the first service type identifier carried in the preamble of the first Ethernet packet, where the first service type identifier is used to indicate the first Ethernet packet. Type of message.

In a possible implementation manner, the processor is specifically configured to detect the encoding of the first Ethernet packet, and the encoded block type is used as the first identification information; process the encoding according to the first identification information. The first Ethernet packet.

In a possible implementation manner, the processor is further configured to detect a second service type identifier carried in at least one byte after the encoded block type, where the second service type identifier is used to indicate the first An Ethernet packet type.

In a possible implementation manner, the processor is further configured to negotiate with the second device to determine whether to support processing of the first Ethernet type packet.

In a possible implementation manner, the transceiver is further configured to negotiate with the second device whether to support processing the first Ether-type packet by sending an auto-negotiation pulse, and the auto-negotiation pulse carries negotiation information, so the The negotiation information is used to instruct the first device or the second device to support processing the first ether type packet;

or,

The transceiver is further configured to negotiate with the second device whether to support processing the first Ethernet type packet by sending a link layer discovery protocol LLDP, where the link layer discovery protocol carries the negotiation information, so The negotiation information is used to indicate that the first device or the second device supports processing of the first Ethernet type packet.

or,

The following describes the Ethernet packet processing device in this application in detail, please refer to FIG. 24 , which is a schematic diagram of an embodiment of the Ethernet packet processing device in the embodiment of the application. The Ethernet packet processing device can be deployed in a switch (or router). The Ethernet packet processing device 2400 includes: a processing module 2401, configured to carry second identification information in the second Ethernet packet, where the second identification information is used for Instructing the first device to support processing of the first ether type packet, where the first ether type packet includes an ether packet with a frame length less than 64 bytes;

The transceiver module 2402 is configured to send the second Ethernet packet.

In a possible implementation manner, the processing module 2401 is further configured to determine the frame length of the second Ethernet packet and whether it supports processing the first Ethernet type packet; When the frame length is less than 64 bytes, and the first device supports processing the first Ethernet type packet, the operation of carrying the second identification information in the second Ethernet packet is performed.

In a possible implementation manner, the processing module 2401 is further configured to process the second Ethernet packet when processing the first Ethernet packet is not supported and the frame length of the second Ethernet packet is less than 64 bytes. The frame length of the Ethernet message is padded to 64 bytes and sent;

When processing of the first Ethernet type packet is not supported and the frame length of the second Ethernet packet is greater than or equal to 64 bytes and less than or equal to 1518 bytes, the second Ethernet packet is sent, and the second Ethernet packet is sent. The message does not carry the second identification information;

When processing of the first Ethernet packet is not supported and the frame length of the second Ethernet packet is greater than 1518 bytes, the frame length of the second Ethernet packet is truncated to 1518 bytes and sent.

In a possible implementation manner, the transceiver module 2402 is configured to receive a first Ethernet packet, where the first Ethernet packet carries first identification information, and the first identification information is used to indicate the first device support processing of the first ether type packet, the first ether type packet includes an ether packet whose frame length is less than 64 bytes;

The processing module 2401 is further configured to process the first Ethernet packet according to the first identification information.

In a possible implementation manner, the processing module 2401 is further configured to determine the frame length of the first Ethernet packet and whether it supports processing the first Ethernet type packet; When the frame length is less than 64 bytes and the processing of the first Ethernet type packet is supported, the operation of processing the first Ethernet packet according to the first identification information is performed.

In a possible implementation manner, the processing module 2401 is further configured to discard the first Ethernet packet when the processing of the first Ethernet type packet is not supported and the first Ethernet packet is less than 64 bytes .

In a possible implementation manner, the processing module 2401 is specifically configured to generate a preamble of the second Ethernet packet at the medium access control layer MAC, and the frame header delimiter position information of the preamble is used as the first code. 2. Identification information.

In a possible implementation manner, the processing module 2401 is specifically configured to generate a preamble of the second Ethernet packet at the medium access control layer MAC, and the target identification field in the preamble is used as the second identification information. .

In a possible implementation manner, the processing module 2401 is further configured to carry a first service type identifier in the preamble of the second Ethernet packet, and the first service type identifier is used to indicate the second Ethernet packet. Type of message.

In a possible implementation manner, the processing module 2401 is specifically configured to generate the encoding of the second Ethernet packet in the physical encoding sublayer PCS, and the encoded block type is used as the second identification information.

In a possible implementation manner, the encoded block type is the block type of the start block of the second Ethernet packet.

In a possible implementation manner, the processing module 2401 is further configured to carry a second service type identifier in at least one byte after the encoded block type, where the second service type identifier is used to indicate the first 2 Types of Ethernet packets.

In a possible implementation manner, the processing module 2401 is further configured to negotiate with a second device to determine whether to support processing the first Ethernet type packet, and the first device and the second device are on the same link. both ends.

In a possible implementation manner, the transceiver module 2402 is further configured to negotiate with the second device whether to support processing the first EtherType packet by sending an auto-negotiation pulse, and the auto-negotiation pulse carries negotiation information, The negotiation information is used to indicate that the first device or the second device supports processing of the first Ethernet type packet;

or,

The transceiver module 2402 is further configured to negotiate with the second device whether to support processing the first Ethernet type packet by sending a link layer discovery protocol LLDP, where the link layer discovery protocol carries the negotiation information, The negotiation information is used to indicate that the first device or the second device supports processing of the first Ethernet type packet.

or,

a processor, configured to carry second identification information in the second Ethernet packet, where the second identification information is used to indicate that the first device supports processing of the first Ethernet type packet, and the first Ethernet type packet includes Ethernet packets whose frame length is less than 64 bytes;

a transceiver, configured to send the second Ethernet packet.

In a possible implementation manner, the processor is further configured to determine the frame length of the second Ethernet packet and whether it supports processing the first Ethernet type packet; When the length is less than 64 bytes, and the first device supports processing the first Ethernet type packet, the operation of carrying the second identification information in the second Ethernet packet is performed.

In a possible implementation manner, the processor is further configured to process the second Ethernet packet when processing the first Ethernet packet is not supported and the frame length of the second Ethernet packet is less than 64 bytes. The frame length of the message is padded to 64 bytes and sent;

In a possible implementation manner, the transceiver is configured to receive a first Ethernet packet, where the first Ethernet packet carries first identification information, and the first identification information is used to indicate that the first device supports processing a first ether type packet, where the first ether type packet includes an ether packet whose frame length is less than 64 bytes;

The processor is further configured to process the first Ethernet packet according to the first identification information.

In a possible implementation manner, the processor is further configured to discard the first Ethernet packet when the processing of the first Ethernet type packet is not supported and the first Ethernet packet is smaller than 64 bytes.

In a possible implementation manner, the processor is specifically configured to generate a preamble of the second Ethernet packet at the medium access control layer MAC, and the frame header delimiter position information of the preamble is used as the second Ethernet packet. identification information.

In a possible implementation manner, the processor is specifically configured to generate a preamble of the second Ethernet packet at a medium access control layer MAC, and a target identification field in the preamble is used as the second identification information.

In a possible implementation manner, the processor is further configured to carry a first service type identifier in the preamble of the second Ethernet packet, and the first service type identifier is used to indicate the second Ethernet packet. type of text.

In a possible implementation manner, the processor is specifically configured to generate an encoding of the second Ethernet packet at the physical encoding sublayer PCS, and the encoded block type is used as the second identification information.

In a possible implementation manner, the processor is further configured to carry a second service type identifier in at least one byte after the encoded block type, where the second service type identifier is used to indicate the second service type identifier. Type of Ethernet packet.

In a possible implementation manner, the processor is further configured to negotiate with a second device to determine whether to support processing of the first Ethernet type packet, and the first device and the second device are on two sides of the same link. end.

or,

The embodiment of the present application also provides a processing device. The processing device includes a processor and an interface; the processor is configured to execute the method for processing an Ethernet packet according to any of the foregoing method embodiments.

It should be understood that the above-mentioned processing device may be a chip, and the processor may be implemented by hardware or software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, The processor may be a general-purpose processor, and is implemented by reading software codes stored in a memory, which may be integrated in the processor, or located outside the processor, and exists independently.

Wherein, "implemented by hardware" means that the functions of the above-mentioned modules or units are realized by a hardware processing circuit that does not have the function of processing program instructions. The hardware processing circuit can be composed of discrete hardware components or an integrated circuit. In order to reduce power consumption and reduce size, it is usually implemented in the form of integrated circuits. The hardware processing circuit may include ASIC (application-specific integrated circuit, application-specific integrated circuit), or PLD (programmable logic device, programmable logic device); wherein, PLD may include FPGA (field programmable gate array, field programmable gate array) , CPLD (complex programmable logic device, complex programmable logic device) and so on. These hardware processing circuits can be a single semiconductor chip packaged separately (such as packaged into an ASIC); they can also be integrated with other circuits (such as CPU, DSP) and packaged into a semiconductor chip, for example, can be formed on a silicon substrate A variety of hardware circuits and CPUs are individually packaged into a chip, which is also called SoC, or circuits and CPUs for implementing FPGA functions can also be formed on a silicon substrate and individually enclosed into a single chip. Also known as SoPC (system on a programmable chip, programmable system on a chip).

Embodiments of the present application further provide a computer-readable storage medium, including instructions, which, when run on a computer, cause the computer to control an Ethernet packet processing device to execute any one of the implementations shown in the foregoing method embodiments.

An embodiment of the present application also provides a computer program product, the computer program product includes computer program code, and when the computer program code is run on a computer, causes the computer to execute any one of the implementations shown in the foregoing method embodiments.

An embodiment of the present application further provides a chip system, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the chip executes any one of the implementations shown in the foregoing method embodiments. Way.

Embodiments of the present application further provide a chip system, including a processor, where the processor is configured to call and run a computer program, so that the chip executes any one of the implementations shown in the foregoing method embodiments.

In addition, it should be noted that the device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be A physical unit, which can be located in one place or distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment. In addition, in the drawings of the device embodiments provided in the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.

From the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general-purpose hardware. Special components, etc. to achieve. Under normal circumstances, all functions completed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structures used to implement the same function can also be various, such as analog circuits, digital circuits or special circuit, etc. However, a software program implementation is a better implementation in many cases for this application. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that make contributions to the prior art. The computer software products are stored in a readable storage medium, such as a floppy disk of a computer. , U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., including several instructions to make a computer device execute the methods described in the various embodiments of the present application.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can 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. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transferred from a website site, a computer, a first network device or a second network device, computing device, or data center to another website site, computer, first, by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) A network device or a second network device, computing device or data center transmits. The computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a first network device or a second network device, a data center, etc. that includes one or more available media integrated. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), and the like.

It is to be understood that reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic associated with the embodiment is included in at least one embodiment of the present application. Thus, appearances of "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Additionally, the terms "system" and "network" are often used interchangeably herein. It should be understood that, in this embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. Interchangeability, the above description has generally described the components and steps of each example in terms of function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above may refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application.

In a word, the above descriptions are only preferred embodiments of the technical solutions of the present application, and are not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the principles of this application shall be included within the protection scope of this application.

Claims

A method for processing an Ethernet message, comprising:

The first device receives the first Ethernet packet sent by the second device, the first Ethernet packet carries first identification information, and the first identification information is used to indicate that the second device supports processing of the first Ethernet type packet , the first Ethernet type packet includes an Ethernet packet whose frame length is less than 64 bytes;

The first device processes the first Ethernet packet according to the first identification information.
The method according to claim 1, wherein before the first device processes the first Ethernet packet according to the first identification information, the method further comprises:

The first device determines the frame length of the first Ethernet packet and whether it supports processing the first Ethernet type packet;

When the frame length of the first Ethernet packet is less than 64 bytes and the first device supports processing of the first Ethernet type packet, the first device executes the processing according to the first identification information. Operation of the first Ethernet packet.
The method according to claim 2, wherein the method further comprises:

When the first device does not support processing the first Ethernet packet and the first Ethernet packet is smaller than 64 bytes, the first device discards the second Ethernet packet.
The method according to any one of claims 1 to 3, wherein the method further comprises:

The first device carries second identification information in the second Ethernet packet, where the second identification information is used to indicate that the first device supports processing the first Ethernet type packet, and the first Ethernet type packet The message includes Ethernet messages whose frame length is less than 64 bytes;

The first device sends the second Ethernet packet.
The method according to claim 4, wherein before the first device carries the second identification information in the second Ethernet packet, the method further comprises:

The first device determines the frame length of the second Ethernet packet and whether it supports processing the first Ethernet type packet;

When the frame length of the first Ethernet packet is less than 64 bytes, and the first device supports processing of the first Ethernet type packet, the first device executes the process of carrying in the second Ethernet packet Operation of the second identification information.
The method according to claim 5, wherein the method further comprises:

When the first device does not support processing the first Ethernet packet and the frame length of the second Ethernet packet is less than 64 bytes, the first device converts the frame length of the second Ethernet packet to Pad to 64 bytes and send;

When the first device does not support processing the first Ethernet packet and the frame length of the second Ethernet packet is greater than or equal to 64 bytes and less than or equal to 1518 bytes, the first device sends the first Ethernet packet. Two Ethernet packets, the second Ethernet packets do not carry the second identification information.
The method according to claim 1, wherein the first Ethernet type packet further comprises an Ethernet packet whose frame length is greater than or equal to 64 bytes.
The method according to any one of claims 1 to 7, wherein the processing of the first Ethernet packet by the first device according to the first identification information comprises:

The first device detects the preamble of the first Ethernet message, and the frame head delimiter position information of the preamble is used as the first identification information;

The first device processes the first Ethernet packet according to the first identification information.
The method according to any one of claims 1 to 7, wherein the processing of the first Ethernet packet by the first device according to the first identification information comprises:

The first device detects the preamble of the first Ethernet message, and the target identification field in the preamble is used as the first identification information;

The first device processes the first Ethernet packet according to the first identification information.
The method according to any one of claims 8 or 9, wherein the method further comprises:

The first device detects the first service type identifier carried in the preamble of the first Ethernet packet, where the first service type identifier is used to indicate the type of the first Ethernet packet.
The method according to any one of claims 1 to 10, wherein the processing of the first Ethernet packet by the first device according to the first identification information comprises:

The first device detects the encoding of the first Ethernet message, and the encoded block type is used as the first identification information;

The first device processes the first Ethernet packet according to the first identification information.
The method according to claim 11, wherein the encoded block type is a start block of the first Ethernet packet.
The method according to claim 11 or 12, wherein the method further comprises:

The first device detects a second service type identifier carried in at least one byte after the encoded block type, where the second service type identifier is used to indicate the type of the first Ethernet packet.
The method according to any one of claims 1 to 13, wherein the method further comprises:

The first device negotiates with the second device to determine whether to support processing of the first Ethernet type packet.
The method of claim 14, wherein the method further comprises:

The first device and the second device negotiate whether to support processing the first Ethernet type packet by sending an auto-negotiation pulse, the auto-negotiation pulse carries negotiation information, and the negotiation information is used to indicate the first Ethernet type packet. The device or the second device supports processing of the first Ethernet type packet;

or,

The first device and the second device negotiate whether to support processing the first Ethernet type packet by sending the link layer discovery protocol LLDP, the link layer discovery protocol carries the negotiation information, the negotiation information It is used to instruct the first device or the second device to support processing the first Ethernet type packet.
The method according to claim 15, wherein an unused bit in the link code word base page of the auto-negotiation pulse indicates the negotiation information;

or,

The message code value in the link code word extension page of the auto-negotiation burst indicates the negotiation information.
The method according to claim 15, wherein an elastic capability identifier TLV type is generated in the link layer discovery protocol, and the TLV type indicates the negotiation information.
An Ethernet packet processing device, comprising:

A transceiver module, configured to receive a first Ethernet packet sent by a second device, where the first Ethernet packet carries first identification information, and the first identification information is used to indicate that the second device supports processing the first Ethernet type message, the first Ethernet type message includes an Ethernet message with a frame length of less than 64 bytes;

A processing module, configured to process the first Ethernet packet according to the first identification information.
The Ethernet packet processing device according to claim 18, wherein the processing module is further configured to determine the frame length of the first Ethernet packet and whether it supports processing the first Ethernet type packet; When the frame length of the first Ethernet packet is less than 64 bytes and the processing of the first Ethernet type packet is supported, the operation of processing the first Ethernet packet according to the first identification information is performed.
The device for processing an Ethernet packet according to claim 19, wherein the processing module is further configured to process the first Ethernet packet when the first Ethernet packet is not supported and the first Ethernet packet is less than 64 bytes. , discard the second Ethernet packet.
The Ethernet packet processing device according to any one of claims 18 to 20, wherein the processing module is configured to carry second identification information in the second Ethernet packet, and the second identification information is used for instructing the first device to support processing of the first ether type packet, where the first ether type packet includes an ether packet with a frame length less than 64 bytes;

The transceiver module is further configured to send the second Ethernet message.
The Ethernet packet processing device according to claim 21, wherein the processing module is further configured to determine the frame length of the second Ethernet packet and whether it supports processing the first Ethernet type packet; When the frame length of the second Ethernet packet is less than 64 bytes and supports processing of the first Ethernet type packet, the operation of carrying the second identification information in the second Ethernet packet is performed.
The device for processing an Ethernet packet according to claim 22, wherein the processing module is further configured to process the first Ethernet type packet and the frame length of the second Ethernet packet is less than 64 Bytes, fill the frame length of the second Ethernet packet to 64 bytes and send it; when the first Ethernet type packet cannot be processed and the frame length of the second Ethernet packet is greater than or equal to 64 bytes When the number of bytes is less than or equal to 1518 bytes, the second Ethernet packet is sent, and the second Ethernet packet does not carry the second identification information.
The Ethernet packet processing device according to claim 18, wherein the first Ethernet type packet further comprises an Ethernet packet whose frame length is greater than or equal to 64 bytes.
The Ethernet packet processing device according to any one of claims 18 to 24, wherein the processing module is specifically configured to detect the preamble of the first Ethernet packet, and the frame header of the preamble is The delimiter position information is used as the first identification information; the first Ethernet packet is processed according to the first identification information.
The Ethernet packet processing device according to any one of claims 18 to 24, wherein the processing module is specifically configured to detect a preamble of the first Ethernet packet, and the target in the preamble is The identification field is used as the first identification information; the first Ethernet packet is processed according to the first identification information.
The Ethernet packet processing device according to any one of claims 25 or 26, wherein the processing module is further configured to detect the first service type identifier carried in the preamble of the first Ethernet packet , the first service type identifier is used to indicate the type of the first Ethernet packet.
The Ethernet packet processing device according to any one of claims 18 to 27, wherein the processing module is specifically configured to detect the encoding of the first Ethernet packet, and the encoded block type is used as the the first identification information; and the first Ethernet packet is processed according to the first identification information.
The Ethernet packet processing device according to claim 28, wherein the encoded block type is a start block of the first Ethernet packet.
The Ethernet packet processing device according to claim 28 or 29, wherein the processing module is further configured to detect the second service type identifier carried in at least one byte after the encoded block type, the The second service type identifier is used to indicate the type of the first Ethernet packet.
The Ethernet packet processing device according to any one of claims 18 to 30, wherein the processing module is further configured to negotiate with the second device to determine whether to support processing the first Ethernet type packet .
The Ethernet packet processing device according to claim 31, wherein the transceiver module is further configured to negotiate with the second device whether to support processing the first Ethernet type packet by sending an auto-negotiation pulse, so The auto-negotiation pulse carries negotiation information, and the negotiation information is used to instruct the first device or the second device to support processing the first Ethernet type packet;

or,

The transceiver module is further configured to negotiate with the second device whether to support processing the first Ethernet type packet by sending a link layer discovery protocol LLDP, where the link layer discovery protocol carries the negotiation information, so the The negotiation information is used to indicate that the first device or the second device supports processing of the first Ethernet type packet.
The Ethernet packet processing device according to claim 32, wherein an unused bit in the link code word base page of the auto-negotiation pulse indicates the negotiation information;

or,

The message code value in the link code word extension page of the auto-negotiation burst indicates the negotiation information.
The Ethernet packet processing device according to claim 32, wherein a TLV type of elastic capability identifier is generated in the link layer discovery protocol, and the TLV type indicates the negotiation information.
A computer program, characterized in that, when the computer program is run on a computer, it causes the computer to execute the method according to any one of claims 1 to 17.
A computer-readable storage medium, characterized by comprising a program, which, when the program is run on a computer, causes the computer to execute the method according to any one of claims 1 to 17 .
A communication device, characterized in that it comprises a processor and a memory, the processor is coupled to the memory,

the memory for storing programs;

The processor is configured to execute a program in the memory, so that the communication device executes the method according to any one of claims 1 to 17.
A chip system, characterized in that the chip system includes one or more processors and a memory, the memory stores program instructions, and when the program instructions are executed in the one or more processors, The method as claimed in any one of claims 1 to 17 is caused to be performed.