A network device and a data processing method

Abstract

This application provides a network device and a data processing method, relating to the field of communication technology. The network device includes a FlexE interface board, a backplane, and at least one forwarding board. A first VLAN configuration unit is configured on the FlexE interface board, and the first VLAN configuration unit is connected to the backplane via a serializer / deserializer. The first VLAN configuration unit stores a mapping relationship between FlexE service ports and FlexE channels. At least one forwarding board is configured with a second VLAN configuration unit, and the second VLAN configuration unit is connected to the backplane via a serializer / deserializer. The second VLAN configuration unit also stores a mapping relationship between FlexE service ports and FlexE channels. The serializer / deserializer uses an Ethernet backplane protocol to transmit data frames. This solution can reduce the difficulty of chip selection and hardware costs for network devices, and improve the scalability of network devices.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a network device and a data processing method. Background Technology

[0002] In network devices, Flex Ethernet (FlexE) interface boards and forwarding boards are connected to the backplane via serializers / deserializers (such as SerDes), and FlexE interface boards and forwarding boards use flexible channelization protocols (such as the Interlaken protocol) to achieve flexible channelization on the serializer / deserializer data link, ensuring hard isolation between the forwarding resources of the forwarding board and services.

[0003] However, the limited availability of chips supporting the Interlaken protocol makes chip selection for FlexE interface boards and forwarding boards difficult, and the high cost of Interlaken-supporting chips increases the hardware cost of network equipment. Existing communication protocols and technical specifications cannot fully meet the flexible channelization requirements of FlexE interface cards on the system side, posing significant technical compatibility challenges in solution design, hindering network equipment innovation and upgrades, and resulting in poor scalability. Summary of the Invention

[0004] The purpose of this application is to provide a network device and a data processing method to reduce the difficulty of chip selection and hardware cost of the network device, and to improve the scalability of the network device. The specific technical solution is as follows:

[0005] In a first aspect, embodiments of this application provide a network device, including a FlexE interface board, a backplane, and at least one forwarding board;

[0006] The FlexE interface board is equipped with a first Virtual Local Area Network (VLAN) configuration unit, which is connected to the backplane via a serializer / deserializer; the first VLAN configuration unit stores the mapping relationship between FlexE service ports and FlexE channels;

[0007] At least one forwarding board is equipped with a second VLAN configuration unit, which is connected to the backplane via a serializer / deserializer; the second VLAN configuration unit stores the mapping relationship between FlexE service ports and FlexE channels;

[0008] The serializer / deserializer uses an Ethernet backplane protocol to transmit data frames.

[0009] In some embodiments, the first VLAN configuration unit is used to:

[0010] Receive the first data frame from the target FlexE service port on the FlexE interface board;

[0011] Based on the mapping relationship between FlexE service ports and FlexE channels, determine the target FlexE channel corresponding to the target FlexE service port;

[0012] Add a first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain a second data frame. The VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel.

[0013] The second data frame is sent to the primary forwarding board in the at least one forwarding board.

[0014] In some embodiments, the first VLAN configuration unit is specifically used for:

[0015] If the first data frame carries a second VLAN tag, then obtain the first VLAN tag corresponding to the target FlexE channel, and fill the other fields included in the first VLAN tag with the other fields included in the second VLAN tag, wherein the other fields are fields other than the VLAN identifier field;

[0016] Add the padded first VLAN tag to the first data frame to obtain the second data frame.

[0017] In some embodiments, the second VLAN configuration unit is used for:

[0018] Receive the second data frame from the FlexE interface board;

[0019] Obtain the identifier of the target FlexE channel included in the first VLAN tag carried in the second data frame, and delete the first VLAN tag carried in the second data frame to obtain the first data frame;

[0020] The first data frame is processed by the logical input port of the forwarding board corresponding to the identifier of the target FlexE channel.

[0021] In some embodiments, the second VLAN configuration unit is used for:

[0022] Obtain the third data frame sent to the target FlexE service port on the FlexE interface board;

[0023] Based on the mapping relationship between FlexE service ports and FlexE channels, determine the target FlexE channel corresponding to the target FlexE service port;

[0024] A first VLAN tag corresponding to the target FlexE channel is added to the third data frame to obtain a fourth data frame, wherein the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel;

[0025] The fourth data frame is sent to the FlexE interface board.

[0026] In some embodiments, the second VLAN configuration unit is specifically used for:

[0027] If the third data frame carries a third VLAN tag, then the first VLAN tag corresponding to the target FlexE channel is obtained, and the other fields included in the first VLAN tag are filled with the other fields included in the third VLAN tag. The other fields are fields other than the VLAN identifier field.

[0028] The first VLAN tag, after being padded, is added to the third data frame to obtain the fourth data frame.

[0029] In some embodiments, the first VLAN configuration unit is used to:

[0030] Receive the fourth data frame from the at least one forwarding board;

[0031] The first VLAN tag carried in the fourth data frame is deleted to obtain the third data frame;

[0032] Based on the mapping relationship between FlexE service ports and FlexE channels, determine the target FlexE service port corresponding to the identifier of the target FlexE channel included in the first VLAN tag;

[0033] The third data frame is forwarded through the target FlexE service port.

[0034] In some embodiments, the first VLAN tag is added between the source Media Access Control MAC address field and the Ethernet type field of the data frame.

[0035] In some embodiments, the first VLAN tag is added between the source MAC address field of the data frame and the VLAN tag carried by the data frame.

[0036] In some embodiments, the at least one forwarding board further includes a central processing unit (CPU), the CPU being used for:

[0037] Multiple VLAN logical ports are created according to the specifications of the FlexE interface board, and the mapping relationship between FlexE service ports and FlexE channels is initialized according to the multiple VLAN logical ports. The VLAN logical ports correspond one-to-one with the FlexE channels.

[0038] Receive a creation command for the target FlexE service port, the creation command including the client identifier of the target FlexE service port and the required target bandwidth;

[0039] When the remaining FlexE service port bandwidth is greater than or equal to the target bandwidth, and there are unused FlexE channels, the target FlexE channel with the target bandwidth is allocated to the target FlexE service port.

[0040] The mapping relationship between the target FlexE service port and the target FlexE channel is sent to the first VLAN configuration unit and the second VLAN configuration unit.

[0041] Secondly, embodiments of this application provide a data processing method applied to any of the network devices described above, wherein the network device includes a FlexE interface board, a backplane, and at least one forwarding board; the method includes:

[0042] The first VLAN configuration unit on the FlexE interface board receives a first data frame from the target FlexE service port on the FlexE interface board; determines the target FlexE channel corresponding to the target FlexE service port according to the mapping relationship between the FlexE service port and the FlexE channel; adds a first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain a second data frame, wherein the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel; and sends the second data frame to the primary forwarding board in the at least one forwarding board.

[0043] The second VLAN configuration unit on the primary forwarding board performs post-processing on the second data frame.

[0044] In some embodiments, the step of adding a first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain a second data frame includes:

[0045] If the first data frame carries a second VLAN tag, then obtain the first VLAN tag corresponding to the target FlexE channel;

[0046] Fill the other fields included in the first VLAN tag with the other fields included in the second VLAN tag, wherein the other fields are fields other than the VLAN identifier field;

[0047] Add the padded first VLAN tag to the first data frame to obtain the second data frame.

[0048] In some embodiments, the step of performing post-processing on the second data frame includes:

[0049] Obtain the identifier of the target FlexE channel included in the first VLAN tag carried in the second data frame, and delete the first VLAN tag carried in the second data frame to obtain the first data frame;

[0050] The first data frame is processed by the logical input port of the forwarding board corresponding to the identifier of the target FlexE channel.

[0051] In some embodiments, the first VLAN tag is added between the source MAC address field and the Ethernet type field of the first data frame.

[0052] In some embodiments, the first VLAN tag is added between the source MAC address field of the first data frame and the second VLAN tag carried by the first data frame.

[0053] Thirdly, embodiments of this application provide a data processing method applied to any of the network devices described above, wherein the network device includes a FlexE interface board, a backplane, and at least one forwarding board; the method includes:

[0054] The second VLAN configuration unit on the primary forwarding board in at least one forwarding board acquires a third data frame sent to the target FlexE service port on the FlexE interface board; determines the target FlexE channel corresponding to the target FlexE service port according to the mapping relationship between the FlexE service port and the FlexE channel; adds a first VLAN tag corresponding to the target FlexE channel to the third data frame to obtain a fourth data frame, wherein the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel; and sends the fourth data frame to the FlexE interface board.

[0055] The first VLAN configuration unit on the FlexE interface board forwards the fourth data frame through the target FlexE service port.

[0056] In some embodiments, the step of adding the first VLAN tag corresponding to the target FlexE channel to the third data frame to obtain the fourth data frame includes:

[0057] If the third data frame carries a third VLAN tag, then the first VLAN tag corresponding to the target FlexE channel is obtained;

[0058] Fill the other fields included in the first VLAN tag with the other fields included in the third VLAN tag, wherein the other fields are fields other than the VLAN identifier field;

[0059] The first VLAN tag, after being padded, is added to the third data frame to obtain the fourth data frame.

[0060] In some embodiments, the step of forwarding the fourth data frame through the target FlexE service port includes:

[0061] The first VLAN tag carried in the fourth data frame is deleted to obtain the third data frame;

[0062] Based on the mapping relationship between FlexE service ports and FlexE channels, determine the target FlexE service port corresponding to the identifier of the target FlexE channel included in the first VLAN tag;

[0063] The third data frame is forwarded through the target FlexE service port.

[0064] In some embodiments, the first VLAN tag is added between the source MAC address field and the Ethernet type field of the third data frame.

[0065] In some embodiments, the first VLAN tag is added between the source MAC address field of the third data frame and the third VLAN tag carried by the third data frame.

[0066] Beneficial effects of the embodiments in this application:

[0067] In the technical solution provided in this application embodiment, VLAN configuration units are respectively set on the FlexE interface board and the forwarding board. The VLAN configuration units are connected to the backplane through a serializer / deserializer (such as SerDes). The serializer / deserializer uses the Ethernet backplane protocol to transmit data frames. The Ethernet backplane protocol is a standard protocol, and most existing FlexE interface boards and forwarding boards support the Ethernet backplane protocol. This reduces the difficulty of chip selection for FlexE interface boards and forwarding boards, and eliminates the need to use dedicated chips that support the Interlaken protocol, thus reducing the hardware cost of network equipment. In this application embodiment, the difficulty of chip selection is reduced, the hardware cost is reduced, and the Ethernet backplane protocol is a standard protocol. The use of the Ethernet backplane protocol adapts to the flexible channelization requirements of the FlexE interface card system side, has good technical compatibility, provides more choices for network equipment manufacturing, improves the manufacturing flexibility of network equipment, and enhances the scalability of network equipment.

[0068] Of course, implementing any product or method of this application does not necessarily require achieving all of the advantages described above at the same time. Attached Figure Description

[0069] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other embodiments can be obtained based on these drawings.

[0070] Figure 1 A schematic diagram of the structure of an existing network device;

[0071] Figure 2 A schematic diagram of the structure of a network device provided in an embodiment of this application;

[0072] Figure 3 A first schematic diagram of the FlexE service port creation process provided in this application embodiment;

[0073] Figure 4 This is a second schematic diagram of the FlexE service port creation process provided in the embodiments of this application;

[0074] Figure 5 A schematic diagram of a FlexE tag provided in an embodiment of this application;

[0075] Figure 6 A schematic diagram of a data processing flow in the message receiving direction provided in an embodiment of this application;

[0076] Figure 7a This is a first schematic diagram illustrating the addition of the FlexE tag according to an embodiment of this application;

[0077] Figure 7b This is a second schematic diagram illustrating the addition of the FlexE tag as provided in an embodiment of this application;

[0078] Figure 8 This is a third schematic diagram illustrating the addition of the FlexE tag in an embodiment of this application;

[0079] Figure 9 A schematic diagram of a data processing flow in the message transmission direction provided in an embodiment of this application;

[0080] Figure 10 This is a schematic diagram of a first type of data processing method provided in an embodiment of this application;

[0081] Figure 11 This is a second flowchart illustrating the data processing method provided in an embodiment of this application. Detailed Implementation

[0082] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art based on this application are within the scope of protection of this application.

[0083] With the rapid development of network technology, the demands for transmission bandwidth and flexibility in services such as data centers and broadband access are constantly increasing. FlexE technology, as a new Ethernet standard, can meet the needs of different speeds and service levels through flexible scheduling of Ethernet channels. FlexE technology is widely used in network devices, achieving a low-cost, highly reliable, and dynamically allocable interface technology by decoupling the Ethernet Media Access Control (MAC) layer from the physical (PHY) layer.

[0084] The structure of network devices is as follows Figure 1 As shown, it includes a FlexE interface board, multiple forwarding boards, and a backplane, as follows: Figure 1The diagram shows the primary and backup forwarding boards. The FlexE interface board and multiple forwarding boards are connected to the backplane via SerDes (serializer / deserializer). The FlexE interface board may include an Intellectual Property Core (IP Core), a Time Synchronized Mesh Protocol for Media Access Control (TS-MAC) module, and system-side communication IP Cores, while the forwarding boards may include forwarding chips and a Central Processing Unit (CPU).

[0085] The FlexE IP Core is used to implement the FlexE Shim layer and the Physical Coding Sublayer (PCS) / Physical Medium Attachment (PMA) layer, and to perform mapping and demapping for FlexE Clients and FlexE Groups. The TS-MAC module is used to implement FlexE Client rate matching. The communication IP Core on the system side and the communication IP Core on the forwarding chip are used to achieve flexible channeling between the FlexE interface board and the forwarding board. The CPU is used to control the forwarding chip and various modules on the FlexE interface board.

[0086] In network equipment, FlexE interfaces are typically expanded using FlexE interface boards. The front panel of the FlexE interface board connects to the remote device via an optical module, and the FlexE interface board uses a FlexE Shim layer to decouple the MAC and PHY layers of the FlexE interface. The system side of the FlexE interface board connects to the forwarding board. Typically, FlexE interfaces use hardware chips such as Field-Programmable Gate Arrays (FPGAs) or MAC chips to implement hard channelization of the FlexE service ports. The system side of the FlexE interface board also needs to implement channel slicing to ensure hard isolation between the forwarding resources and services on the forwarding board. Therefore, the channel between the system side of the FlexE interface board and the forwarding board must meet the requirements of flexible channelization.

[0087] Currently, network devices commonly use specified flexible channelization protocols (such as the Interlaken protocol) to implement flexible channelization on SerDes data links, such as... Figure 1The communication IP Core shown can be an Interlaken IP Core. The Interlaken protocol is a high-bandwidth, high-performance data transmission protocol for inter-chip communication. By optimizing SerDes technology and reducing protocol processing complexity, it achieves efficient and flexible communication. The main features of the Interlaken protocol are scalability and low-latency data transmission, adapting to the flexible channelization requirements of the FlexE interface board system side.

[0088] However, network devices based on the Interlaken protocol face the following challenges:

[0089] (1) Limited chip support: A major problem in the selection of chips for network equipment, especially FlexE interface boards and forwarding boards, is that most current forwarding chips and FlexE interface boards do not support the Interlaken protocol. This limitation greatly increases the difficulty of chip selection and raises the hardware costs of research and development and deployment.

[0090] (2) High hardware cost: In order to meet the flexible channelization requirements, network equipment needs to use dedicated chips, such as chips that support the Interlaken protocol. Dedicated chips are expensive and may increase the complexity of the overall system design, bringing more technical and economic burdens to the research and development and application of network equipment.

[0091] (3) Technical compatibility: Existing communication protocols and technical specifications cannot fully meet the flexible channelization requirements of the FlexE interface card system side. This presents significant technical compatibility challenges in solution design, hindering the innovation and upgrading of network equipment. For chips with some slots supporting the Interlaken protocol, the new chassis design has poor scalability.

[0092] In addition, there are few chips that support the Interlaken protocol, and the Interlaken protocol is incompatible with most chips, which results in poor scalability of network devices.

[0093] To address the aforementioned problems, embodiments of this application provide a network device, such as... Figure 2 As shown, the network device includes a FlexE interface board 201, a backplane 201, and at least one forwarding board 203. Figure 2 The example only uses two forwarding boards 203 as examples and is not intended to be limiting.

[0094] A first VLAN configuration unit 211 is set on the FlexE interface board 201. The first VLAN configuration unit 211 is connected to the backplane 202 through a serializer / deserializer. The first VLAN configuration unit 211 stores the mapping relationship between FlexE service ports and FlexE channels.

[0095] A second VLAN configuration unit 213 is provided on at least one of the aforementioned forwarding boards 203. The second VLAN configuration unit 213 is connected to the backplane 202 through a serializer / deserializer. The second VLAN configuration unit 213 stores the mapping relationship between FlexE service ports and FlexE channels.

[0096] The serializer / deserializer uses an Ethernet backplane protocol to transmit data frames.

[0097] In the technical solution provided in this application embodiment, VLAN configuration units are respectively set on the FlexE interface board and the forwarding board. The VLAN configuration units are connected to the backplane through a serializer / deserializer (such as SerDes). The serializer / deserializer uses the Ethernet backplane protocol to transmit data frames. The Ethernet backplane protocol is a standard protocol, and most existing FlexE interface boards and forwarding boards support the Ethernet backplane protocol. This reduces the difficulty of chip selection for FlexE interface boards and forwarding boards, and eliminates the need to use dedicated chips that support the Interlaken protocol, thus reducing the hardware cost of network equipment. In this application embodiment, the difficulty of chip selection is reduced, the hardware cost is reduced, and the Ethernet backplane protocol is a standard protocol. The use of the Ethernet backplane protocol adapts to the flexible channelization requirements of the FlexE interface card system side, has good technical compatibility, provides more choices for network equipment manufacturing, improves the manufacturing flexibility of network equipment, and enhances the scalability of network equipment.

[0098] In this embodiment, the network device can be a distributed network device or a centralized network device. The network device may also include other components such as a chassis, and the FlexE interface board 201 and the forwarding board 203 may also include other modules, such as... Figure 2 As shown, the FlexE interface board 201 may also include a FlexE IP Core and a TS-MAC module, and the forwarding board 203 may also include a CPU.

[0099] The FlexE IP Core is used to implement the FlexE Shim layer and PCS / PMA, and to perform mapping and demapping of FlexE Client and FlexE Group; the TS-MAC module is used to implement FlexE Client rate matching. The CPU is used to control the forwarding chip and various modules on the FlexE interface board.

[0100] The data communication chip selection for the FlexE interface board 201 can be either an FPGA or a MAC chip with FlexE functionality. A VLAN configuration unit, namely the first VLAN configuration unit 211, is set up on the FlexE interface board 201 on the system side. The first VLAN configuration unit 211 is responsible for the parsing and configuration of the FlexE tags (TAGs) for the Ethernet backplane channels, realizing the mapping between the FlexE tag channel ID and the FlexE Client ID.

[0101] When a network device includes multiple forwarding boards 203, these multiple forwarding boards 203 may include a primary forwarding board and one or more backup forwarding boards. Figure 2 This example only uses one primary forwarding board and one backup forwarding board, and is not intended to be limiting. A VLAN configuration unit, namely the second VLAN configuration unit 213, is configured on forwarding board 203. The second VLAN configuration unit 213 can be configured on the forwarding chip within forwarding board 203, such as... Figure 2 As shown. The forwarding chip can be a switching chip or a network processor (NP) chip, etc. On the forwarding chip, the FlexE service port is represented by a logical ingress port, that is, one FlexE service port corresponds to one logical ingress port.

[0102] The first VLAN configuration unit 211 and the second VLAN configuration unit 213 are connected via a backplane 202 and a serializer / deserializer (such as SerDes). On the serializer / deserializer data link, data frames are transmitted using the Ethernet backplane protocol, which is compatible with most forwarding chips.

[0103] In this embodiment, to achieve fine-grained resource management and data isolation, during FlexE interface board initialization, one or more Ethernet ports are statically initialized on both the system side and the forwarding board, according to the requirements of the forwarding chip resources and product specifications (i.e., the specifications of the FlexE interface board). For example, if the FlexE interface board is 100G and one Ethernet port is 100G, then one Ethernet port needs to be statically initialized on both the system side and the forwarding board; if one Ethernet port is 50G, then two Ethernet ports need to be statically initialized on both the system side and the forwarding board.

[0104] The system side of the FlexE interface board is configured with an Ethernet backplane protocol between the Ethernet port on the forwarding board and the Ethernet port on the forwarding board. In this way, the first VLAN configuration unit 211 and the second VLAN configuration unit 213 can connect to the backplane 202 on the Ethernet port using the Ethernet backplane protocol via a serializer / deserializer, thereby enabling the forwarding board 203 to establish a connection with the FlexE interface board 201 using the Ethernet backplane protocol.

[0105] Based on the Ethernet port, the CPU on the forwarding board 203 performs VLAN segmentation according to the specifications of the FlexE interface board. This involves statically creating VLAN logical ports (i.e., virtual interfaces) corresponding to the specifications of the FlexE service ports, ensuring that each VLAN logical port has independent forwarding resources and achieving fine-grained resource management and data isolation. For example, the smallest granularity of FlexE is 5G, and the specification of a 100G FlexE interface board is 100G / 5G = 20 FlexE service ports, meaning a 100G FlexE interface board can create a maximum of 20 FlexE service ports. During the initialization of the FlexE interface board 201, the system side of the forwarding board 203 and the FlexE interface board 201 creates a 100G Ethernet port and, based on this Ethernet port, creates 20 VLAN logical ports. The VLAN logical ports correspond one-to-one with the FlexE service ports, as shown in Table 1.

[0106] Table 1

[0107]

[0108] Table 1 shows that the Client ID corresponds to a FlexE service port, with each Client ID numbered from 1 to 20 corresponding to a FlexE service port. The Channel ID corresponds to a VLAN logical port, with each Channel ID numbered from 1 to 20 corresponding to a VLAN logical port. In this embodiment, one VLAN logical port is equivalent to one FlexE channel, and the Channel ID is the VLAN ID of the VLAN logical port.

[0109] By initializing VLAN logical ports with different VLAN IDs, FlexE initializes multiple VLAN logical ports on the interface board and forwarding board, achieving resource separation and isolation. Furthermore, the CPU can obtain a static mapping relationship between FlexE service ports and FlexE channels. Subsequently, the CPU on the primary forwarding board can dynamically create FlexE service ports, such as... Figure 3 The FlexE service port creation process shown may include the following steps.

[0110] Step S301: Create multiple VLAN logical ports according to the specifications of the FlexE interface board, and initialize the mapping relationship between the FlexE service port and the FlexE channel according to the multiple VLAN logical ports.

[0111] For the initialization of the mapping relationship between FlexE service ports and FlexE channels, please refer to the relevant description in the initialization section of the FlexE interface board mentioned above, which will not be repeated here.

[0112] Step S302: Receive the creation command for the target FlexE service port. The creation command includes the client identifier of the target FlexE service port and the required target bandwidth.

[0113] In this embodiment, a management module for the FlexE interface board can be designed. The management module provides the interface and control plane. Users can use the management module to construct command lines for creating FlexE service ports, such as a command to create a target FlexE service port. The management module sends the command to the CPU to create the target FlexE service port, i.e., the aforementioned creation command.

[0114] Step S303: When the remaining FlexE service port bandwidth is greater than or equal to the target bandwidth and there is an unused FlexE channel, allocate the target FlexE channel with the target bandwidth to the target FlexE service port.

[0115] After receiving the creation command, the CPU can extract the client ID and target bandwidth of the target FlexE service port from the command. It then determines whether service port resources are available, specifically whether the remaining FlexE service port bandwidth is greater than or equal to the target bandwidth, and whether there are any unused FlexE channels. If service port resources are available (i.e., the remaining FlexE service port bandwidth is greater than or equal to the target bandwidth) and there are unused FlexE channels, the CPU can allocate a target FlexE channel with the target bandwidth to the target FlexE service port.

[0116] If there are no service port resources remaining, that is, the remaining FlexE service port bandwidth is less than the target bandwidth, or all FlexE channels are occupied, the CPU can output a message indicating insufficient service port resources to prompt the user to resolve the issue as soon as possible.

[0117] For example, when the CPU initializes a 100G FlexE interface board, the resulting mapping is shown in Table 1. Upon receiving Creation Command 1, which includes Client ID 2 and a target bandwidth of 50G, the CPU determines that the remaining FlexE service port bandwidth is 100G > 50G, and that all 20 FlexE channels are unused. Therefore, it allocates a 50G FlexE channel to the FlexE service port of Client ID 2, such as FlexE channel 1. The mapping relationship between the dynamically created FlexE service ports and FlexE channels at this time is shown in Table 2.

[0118] Table 2

[0119]

[0120] When the CPU receives Creation Command 2, which includes Client ID 21 and a target bandwidth of 40G, it determines that the remaining FlexE service port bandwidth is 100G - 50G = 50G > 40G, and since the 19 FlexE channels are unused, it allocates a 40G FlexE channel to the FlexE service port of Client ID 21, such as FlexE channel 2. The mapping relationship between dynamically created FlexE service ports and FlexE channels is shown in Table 3.

[0121] Table 3

[0122]

[0123] When the CPU receives Creation Command 3, which includes Client ID 1 and target bandwidth 20G, it determines that the remaining FlexE service port bandwidth is 50G-40G=10G<20G. Therefore, it outputs a message indicating insufficient service port resources and will not allocate a FlexE channel to the FlexE service port of Client ID 1.

[0124] Step S304: Send the mapping relationship between the target FlexE service port and the target FlexE channel to the first VLAN configuration unit and the second VLAN configuration unit.

[0125] After allocating the target bandwidth to the target FlexE service port via the target FlexE channel, the CPU obtains the mapping relationship between the target FlexE service port and the target FlexE channel, and can then send the mapping relationship to the first VLAN configuration unit 211 and the second VLAN configuration unit 213.

[0126] In this embodiment of the application, the FlexE interface board 201 may also include a FlexE IP Core, etc., which will also participate in the creation of the FlexE service port, such as... Figure 4 As shown, the steps may include the following.

[0127] In step S401, the management module issues a command line to the CPU to create a FlexE service port. See the relevant description in step S302 above for details.

[0128] In step S402, the CPU determines whether service port resources are remaining. If service port resources are remaining, proceed to step S403; if service port resources are not remaining, proceed to step S407. See the relevant description in section S303 above for details.

[0129] In step S403, the CPU adds the Client ID from the command line to the port device chain. This facilitates the CPU's management of the FlexE service port. The port device chain stores the Client IDs of the FlexE service ports.

[0130] In step S404, the CPU requests service port resources and assigns a unique VLAN tag to the entire machine.

[0131] In this embodiment, the CPU allocates a FlexE channel and bandwidth to the FlexE service port, and assigns a unique VLAN tag to the corresponding FlexE service port. This VLAN tag is the FlexE tag. Figure 5 As shown, it includes the Tag Protocol Identifier (TPID) and the Customer Tag (C-Tag). The Customer Tag includes the Priority Code Point (PCP), the Drop Eligible Indicator (DEI), and the Channel Identifier (i.e., the VLAN Identifier).

[0132] In the VLAN tagging, TPID, PCP, and DEI can all use default values, such as TPID=0x8100, which are preset in the CPU.

[0133] Step S405: The CPU sends the VLAN client mapping relationship to the hardware.

[0134] In this embodiment of the application, the CPU can obtain the mapping relationship between the FlexE channel and the FlexE service port (i.e., the VLAN client mapping relationship) in step S404. The CPU sends the mapping relationship to the VLAN configuration unit of the forwarding chip and the FlexE interface board, and sends the FlexE service port and allocated bandwidth information to the FlexE IP Core.

[0135] In step S406, the FlexE IP Core creates the corresponding FlexE service port based on the received information.

[0136] Subsequently, the FlexE IP Core can send messages to remote devices through this FlexE service port, and then receive messages sent by remote devices.

[0137] In step S407, the CPU returns a message to the management module indicating insufficient service port resources.

[0138] In this embodiment, users can flexibly configure VLAN segmentation rules and channel mapping rules to dynamically adjust the FlexE service ports and VLAN logical ports. Through reasonable VLAN segmentation and allocation of required bandwidth to FlexE channels, a hard slicing-like effect is achieved, ensuring that different FlexE channels have independent and isolated forwarding resources, avoiding excessive hardware overhead, and achieving efficient utilization of hardware resources, thus improving cost-effectiveness. Furthermore, the system side of the FlexE interface board uses VLAN technology for FlexE channel segmentation, enabling flexible pairing with different types of forwarding chips, allowing the device to adapt to various network environments and application scenarios.

[0139] After the mapping relationship between FlexE service ports and FlexE channels is distributed to the hardware, network devices can use the corresponding FlexE service ports for data processing. The data processing flow is explained below using two scenarios—message reception and message transmission—as examples.

[0140] In the message receiving direction, the first VLAN configuration unit 211 can be used to: receive a first data frame from the target FlexE service port on the FlexE interface board 21; determine the target FlexE channel corresponding to the target FlexE service port according to the mapping relationship between the FlexE service port and the FlexE channel; add a first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain a second data frame, wherein the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel; and send the second data frame to the primary forwarding board in at least one forwarding board 23. Correspondingly, the second VLAN configuration unit 213 can be used to: receive a second data frame from the FlexE interface board 21; obtain the identifier of the target FlexE channel included in the first VLAN tag carried in the second data frame, and delete the first VLAN tag carried in the second data frame to obtain a first data frame; and perform post-processing on the first data frame according to the logical ingress port of the forwarding board corresponding to the identifier of the target FlexE channel. For the specific data processing flow, please refer to [link to relevant documentation]. Figure 6 Steps S601 to S606 are shown.

[0141] In this embodiment, the target FlexE service port is any FlexE service port dynamically created by the CPU. The first data frame is any data frame received through the target FlexE service port. After receiving the first data frame through the target FlexE service port, the FlexE IP Core sends the first data frame to the first VLAN configuration unit 211 through the TS-MAC module.

[0142] The first VLAN configuration unit 211 determines the target FlexE channel corresponding to the target FlexE service port based on the mapping relationship between the FlexE service port and the FlexE channel issued by the CPU, and then obtains the corresponding VLAN tag, such as the first VLAN tag. The first VLAN tag corresponding to the target FlexE channel is added to the first data frame to obtain the second data frame.

[0143] In this embodiment, the first VLAN tag can be added to a pre-defined position in the data frame. However, to adapt to existing standards and facilitate the implementation of this embodiment, the first VLAN tag can be added between the source MAC address (SA) field and the Ethernet type (E-Type) field of the first data frame, such as... Figure 7a The 4-byte FlexE tag shown (i.e., the first VLAN tag) is located in the VLAN tag position specified in existing standard protocols. In the case of a second VLAN tag carried in the first data frame, the first VLAN tag is added between the source MAC address field of the first data frame and the second VLAN tag carried in the first data frame, as shown below. Figure 7b The 4-byte FlexE tag shown is the first VLAN tag. At this time, the first VLAN tag is still located in the VLAN tag position specified in the existing standard protocol. Figure 7b The VLAN tag in the data frame is the original VLAN tag carried in the data frame, such as the second VLAN tag.

[0144] Figure 7a and Figure 7b In addition, the data frame may also include the destination MAC address field (DA), the cyclic redundancy check (CRC) field, and the payload field.

[0145] In some embodiments, the first data frame carries a second VLAN tag. In this case, the first VLAN configuration unit 211 can specifically be used to: if the first data frame carries a second VLAN tag, obtain the first VLAN tag corresponding to the target FlexE channel, fill the other fields included in the first VLAN tag with the other fields included in the second VLAN tag, wherein the other fields are fields other than the VLAN identifier field; add the filled first VLAN tag to the first data frame to obtain the second data frame. Figure 8 The data frame shown uses the same PCP and DEI fields in the FlexE tag as the original VLAN tag. This reuse of other fields from the original VLAN tag facilitates traffic tiering control of the data frame.

[0146] After the first VLAN configuration unit 211 obtains the second data frame, it sends the second data frame to the backplane 22 through a serializer / deserializer using the Ethernet backplane protocol; the backplane 22 then sends the second data frame to the second VLAN configuration unit 213 through a serializer / deserializer using the Ethernet backplane protocol.

[0147] After receiving the second data frame, the second VLAN configuration unit 213 can obtain the identifier of the target FlexE channel from the first VLAN tag carried in the second data frame, thereby determining the logical ingress port of the forwarding board corresponding to the identifier of the target FlexE channel, and deleting the first VLAN tag carried in the second data frame to restore the first data frame to its original state. The second VLAN configuration unit 213 can transmit the logical ingress port of the forwarding board corresponding to the identifier of the target FlexE channel to the processing unit of the forwarding chip. The processing unit performs subsequent processing on the first data frame according to the logical ingress port and the forwarding table, which ensures the normal processing of the first data frame.

[0148] The processing unit can perform post-processing on the first data frame by sending it to the FlexE interface board via the second VLAN configuration unit 213, which then forwards it to the remote device. Alternatively, the processing unit can send the first data frame to the CPU for processing. This application embodiment does not limit the specific method of post-processing of the first data frame.

[0149] In this embodiment, after receiving the second data frame, the second VLAN configuration unit 213 may also send the second data frame to the CPU for processing. This embodiment does not limit the specific method by which the second VLAN configuration unit 213 processes the second data frame.

[0150] In the message transmission direction, the second VLAN configuration unit 213 can be used to: acquire a third data frame sent to the target FlexE service port on the FlexE interface board; determine the target FlexE channel corresponding to the target FlexE service port according to the mapping relationship between the FlexE service port and the FlexE channel; add a first VLAN tag corresponding to the target FlexE channel to the third data frame to obtain a fourth data frame, wherein the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel; and send the fourth data frame to the FlexE interface board. Correspondingly, the first VLAN configuration unit 211 can be used to: receive a fourth data frame from at least one forwarding board; delete the first VLAN tag carried in the fourth data frame to obtain a third data frame; determine the target FlexE service port corresponding to the identifier of the target FlexE channel included in the first VLAN tag according to the mapping relationship between the FlexE service port and the FlexE channel; and forward the third data frame through the target FlexE service port. For the specific data processing flow, please refer to [link to relevant documentation]. Figure 9 Steps S901 to S907 are shown.

[0151] In this embodiment, the target FlexE service port is any FlexE service port dynamically created by the CPU. The third data frame is any data frame sent to the target FlexE service port.

[0152] The second VLAN configuration unit 213 determines the target FlexE channel corresponding to the target FlexE service port based on the mapping relationship between the FlexE service port and the FlexE channel issued by the CPU, and then obtains the corresponding VLAN tag, such as the first VLAN tag. The first VLAN tag corresponding to the target FlexE channel is added to the third data frame to obtain the fourth data frame.

[0153] In this embodiment, the first VLAN tag can be added to a pre-defined position in the data frame. However, to adapt to existing standards and facilitate the implementation of this embodiment, the first VLAN tag can be added between the source MAC address field and the Ethernet type field of the third data frame, such as... Figure 7a The 4-byte FlexE tag is shown. In the case of a third VLAN tag carried in the third data frame, the first VLAN tag is added between the source MAC address field of the third data frame and the third VLAN tag carried in the third data frame, as shown below. Figure 7b The 4-byte FlexE tag shown. Figure 7b The VLAN tag in the data frame is the VLAN tag carried by the data frame, such as the third VLAN tag.

[0154] In some embodiments, the third data frame carries the original third VLAN tag. In this case, the second VLAN configuration unit 213 can specifically be used to: if the third data frame carries the third VLAN tag, obtain the first VLAN tag corresponding to the target FlexE channel, fill the other fields included in the first VLAN tag with the other fields included in the third VLAN tag, wherein the other fields are fields other than the VLAN identifier field; add the filled first VLAN tag to the third data frame to obtain the fourth data frame. Figure 8 The data frame shown uses the same PCP and DEI fields in the FlexE tag as the original VLAN tag. This reuse of other fields from the original VLAN tag facilitates traffic tiering control of the data frame.

[0155] After the second VLAN configuration unit 213 obtains the fourth data frame, it sends the fourth data frame to the backplane 22 through a serializer / deserializer using the Ethernet backplane protocol; the backplane 22 then sends the fourth data frame to the first VLAN configuration unit 211 through a serializer / deserializer using the Ethernet backplane protocol.

[0156] After receiving the fourth data frame, the first VLAN configuration unit 211 can delete the first VLAN tag carried in the fourth data frame to restore the fourth data frame to the third data frame. Based on the mapping relationship between the FlexE service port and the FlexE channel issued by the CPU, it determines the target FlexE service port corresponding to the identifier of the target FlexE channel included in the first VLAN tag. The third data frame is then sent to the FlexE IP Core through the TS-MAC module. The FlexE IP Core sends the third data frame to the remote device through the target FlexE service port.

[0157] In this embodiment, after receiving the fourth data frame, the first VLAN configuration unit 211 can also directly send the fourth data frame to the FlexE IP Core via the TS-MAC module. The FlexE IP Core then sends the fourth data frame to the remote device through the target FlexE service port. In this case, the remote device only needs to support the identification and deletion of the first VLAN tag. This embodiment does not limit the specific method by which the first VLAN configuration unit 211 processes the fourth data frame.

[0158] The technical solution provided in this application addresses the issues of limited chip support, high hardware costs, and technical compatibility in network devices, as detailed below:

[0159] (1) Expanded compatibility: Based on the Ethernet backplane protocol, VLAN technology is used to divide channels, that is, VLAN logical port division, which improves the compatibility of flexible channelization implementation scheme with FlexE interface board and forwarding board, avoids only being able to choose high-cost dedicated chips that support the Interlaken protocol, expands the range of usable chip categories, and thus provides more choices and flexibility for equipment manufacturing.

[0160] In addition, the FlexE interface board and forwarding board use VLAN technology for channel division, which can achieve flexible pairing with different types of forwarding chips, making the device adaptable to various network environments and application scenarios.

[0161] (2) Reduce hardware costs: Without replacing the existing network equipment infrastructure, the Ethernet backplane protocol and VLAN technology are used to achieve efficient interconnection and flexible scheduling of network equipment, which reduces the system hardware procurement and maintenance costs, ensures that the overall cost of equipment manufacturing and assembly is within an acceptable range, adapts to different scenario requirements, and is particularly suitable for the construction of large-scale network equipment.

[0162] In addition, by properly partitioning VLANs and scheduling forwarding resources, excessive hardware overhead can be avoided, efficient use of hardware resources can be achieved, and cost-effectiveness can be improved.

[0163] (3) Increase system flexibility: Provides flexible VLAN division methods, that is, without changing the physical network topology, different VLAN logical ports can be implemented between the FlexE interface board and the forwarding board, and services can be allocated and bandwidth and forwarding resources can be adjusted through VLAN tags, providing flexible and convenient adjustment means for multiple service scenarios.

[0164] In addition, the management module can provide a flexible control plane, allowing users to remotely configure and dynamically adjust VLAN partitioning rules and channel mapping policies (i.e., bandwidth and resource policies) according to actual needs, in order to adapt to different business requirements and network conditions and improve network management efficiency.

[0165] (4) Achieve hard slicing effect: Use VLAN technology to divide and manage Ethernet channels, realize physical and logical isolation of channels and resources, ensure that each service data has independent bandwidth and forwarding resources, provide an effect similar to professional hard slicing, make network resources more efficient and secure to be used, thereby enhancing the security and stability of network resources.

[0166] By isolating VLAN logical ports and allocating independent bandwidth, it is ensured that services with different service quality requirements can obtain stable transmission bandwidth and resources, thereby improving the overall service quality of the network.

[0167] (5) Improve system performance and reliability: Through the high-speed SerDes interface and standard Ethernet backplane protocol, high-speed and low-latency data transmission is achieved, ensuring the performance of the system; in addition, hard channelization and resource partitioning technology (i.e. the above-mentioned technology of using VLAN technology to partition and manage Ethernet channels) ensure the load balance and stable operation of the system, and improve the overall reliability of the system.

[0168] The technical solutions proposed in this application utilize VLAN technology and Ethernet backplane protocols to solve chip selection and compatibility issues, reducing hardware costs and deployment complexity. This application provides a flexible and efficient method for channel partitioning and resource management, achieving high compatibility, low cost, flexible management, efficient transmission, and stable operation. This significantly improves the system's economic efficiency and operational flexibility, meeting the challenges of modern network equipment's high bandwidth and diversified service requirements.

[0169] Corresponding to the aforementioned network devices, embodiments of this application also provide a data processing method, such as... Figure 10 As shown, this method is applied to the aforementioned network device, which may include a FlexE interface board, a backplane, and at least one forwarding board. For details, please refer to [reference needed]. Figure 2 As shown; the method includes the following steps:

[0170] Step S1001: The first VLAN configuration unit set on the FlexE interface board receives the first data frame from the target FlexE service port on the FlexE interface board.

[0171] Step S1002: The first VLAN configuration unit determines the target FlexE channel corresponding to the target FlexE service port based on the mapping relationship between the FlexE service port and the FlexE channel.

[0172] Step S1003: The first VLAN configuration unit adds the first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain the second data frame. The VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel.

[0173] Step S1004: The first VLAN configuration unit sends a second data frame to the primary forwarding board in at least one forwarding board;

[0174] In step S1005, the second VLAN configuration unit set on the primary forwarding board performs post-processing on the second data frame.

[0175] In the technical solution provided in this application embodiment, VLAN configuration units are respectively set on the FlexE interface board and the forwarding board. The VLAN configuration units are connected to the backplane through a serializer / deserializer (such as SerDes). The serializer / deserializer uses the Ethernet backplane protocol to transmit data frames. The Ethernet backplane protocol is a standard protocol, and most existing FlexE interface boards and forwarding boards support the Ethernet backplane protocol. This reduces the difficulty of chip selection for FlexE interface boards and forwarding boards, and eliminates the need to use dedicated chips that support the Interlaken protocol, thus reducing the hardware cost of network equipment. In this application embodiment, the difficulty of chip selection is reduced, the hardware cost is reduced, and the Ethernet backplane protocol is a standard protocol. The use of the Ethernet backplane protocol adapts to the flexible channelization requirements of the FlexE interface card system side, has good technical compatibility, provides more choices for network equipment manufacturing, improves the manufacturing flexibility of network equipment, and enhances the scalability of network equipment.

[0176] In some embodiments, the step of adding a first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain a second data frame includes:

[0177] If the first data frame carries the second VLAN tag, then obtain the first VLAN tag corresponding to the target FlexE channel;

[0178] Fill the other fields included in the first VLAN tag with the other fields included in the second VLAN tag, where the other fields are fields other than the VLAN identifier field;

[0179] The first VLAN tag, after being padded, is added to the first data frame to obtain the second data frame.

[0180] In some embodiments, the step of performing post-processing on the second data frame includes:

[0181] Obtain the identifier of the target FlexE channel included in the first VLAN tag carried in the second data frame, and delete the first VLAN tag carried in the second data frame to obtain the first data frame.

[0182] Based on the logical input port of the forwarding board corresponding to the identifier of the target FlexE channel, the first data frame is processed in the subsequent stage.

[0183] In some embodiments, a first VLAN tag is added between the source MAC address field and the Ethernet type field of the first data frame.

[0184] In some embodiments, a first VLAN tag is added between the source MAC address field of the first data frame and the second VLAN tag carried in the first data frame.

[0185] Corresponding to the aforementioned network devices, embodiments of this application also provide a data processing method, such as... Figure 11 As shown, this method is applied to the aforementioned network device, which may include a FlexE interface board, a backplane, and at least one forwarding board. For details, please refer to [reference needed]. Figure 2 As shown; the method includes the following steps:

[0186] Step S1101: The second VLAN configuration unit set on the primary forwarding board in at least one forwarding board obtains the third data frame sent to the target FlexE service port on the FlexE interface board.

[0187] Step S1102: The second VLAN configuration unit determines the target FlexE channel corresponding to the target FlexE service port based on the mapping relationship between the FlexE service port and the FlexE channel.

[0188] Step S1103: The second VLAN configuration unit adds the first VLAN tag corresponding to the target FlexE channel to the third data frame to obtain the fourth data frame. The VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel.

[0189] Step S1104: The second VLAN configuration unit sends a fourth data frame to the FlexE interface board;

[0190] In step S1105, the first VLAN configuration unit set on the FlexE interface board forwards the fourth data frame through the target FlexE service port.

[0191] In the technical solution provided in this application embodiment, VLAN configuration units are respectively set on the FlexE interface board and the forwarding board. The VLAN configuration units are connected to the backplane through a serializer / deserializer (such as SerDes). The serializer / deserializer uses the Ethernet backplane protocol to transmit data frames. The Ethernet backplane protocol is a standard protocol, and most existing FlexE interface boards and forwarding boards support the Ethernet backplane protocol. This reduces the difficulty of chip selection for FlexE interface boards and forwarding boards, and eliminates the need to use dedicated chips that support the Interlaken protocol, thus reducing the hardware cost of network equipment. In this application embodiment, the difficulty of chip selection is reduced, the hardware cost is reduced, and the Ethernet backplane protocol is a standard protocol. The use of the Ethernet backplane protocol adapts to the flexible channelization requirements of the FlexE interface card system side, has good technical compatibility, provides more choices for network equipment manufacturing, improves the manufacturing flexibility of network equipment, and enhances the scalability of network equipment.

[0192] In some embodiments, the step of adding a first VLAN tag corresponding to the target FlexE channel to a third data frame to obtain a fourth data frame includes:

[0193] If the third data frame carries the third VLAN tag, then obtain the first VLAN tag corresponding to the target FlexE channel;

[0194] Fill the other fields included in the first VLAN tag with the other fields included in the third VLAN tag, where the other fields are fields other than the VLAN identifier field;

[0195] The first VLAN tag, now padded, is added to the third data frame to obtain the fourth data frame.

[0196] In some embodiments, the step of forwarding a fourth data frame through a target FlexE service port includes:

[0197] The first VLAN tag carried in the fourth data frame is deleted to obtain the third data frame;

[0198] Based on the mapping relationship between FlexE service ports and FlexE channels, determine the target FlexE service port corresponding to the identifier of the target FlexE channel included in the first VLAN tag;

[0199] The third data frame is forwarded through the target FlexE service port.

[0200] In some embodiments, the first VLAN tag is added between the source MAC address field and the Ethernet type field of the third data frame.

[0201] In some embodiments, a first VLAN tag is added between the source MAC address field of the third data frame and the third VLAN tag carried by the third data frame.

[0202] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as 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 this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0203] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0204] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the method embodiments are basically similar to the network device embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the network device embodiments.

[0205] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application are included within the scope of protection of this application.

Claims

1. A network device, characterized in that, Includes a Flexible Ethernet FlexE interface board, a backplane, and at least one forwarding board; The FlexE interface board is equipped with a first virtual local area network (VLAN) configuration unit, which is connected to the backplane via a serializer / deserializer. The first VLAN configuration unit stores the mapping relationship between FlexE service ports and FlexE channels. At least one forwarding board is equipped with a second VLAN configuration unit, which is connected to the backplane via a serializer / deserializer; the second VLAN configuration unit stores the mapping relationship between FlexE service ports and FlexE channels; The serializer / deserializer uses an Ethernet backplane protocol to transmit data frames. The first VLAN configuration unit is used for: Receive the first data frame from the target FlexE service port on the FlexE interface board; Based on the mapping relationship between FlexE service ports and FlexE channels, determine the target FlexE channel corresponding to the target FlexE service port; Add a first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain a second data frame. The VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel. Send the second data frame to the primary forwarding board in the at least one forwarding board; The second VLAN configuration unit is used to receive the second data frame from the FlexE interface board.

2. The network device according to claim 1, characterized in that, The first VLAN configuration unit is specifically used for: If the first data frame carries a second VLAN tag, then obtain the first VLAN tag corresponding to the target FlexE channel, and fill the other fields included in the first VLAN tag with the other fields included in the second VLAN tag, wherein the other fields are fields other than the VLAN identifier field; Add the padded first VLAN tag to the first data frame to obtain the second data frame.

3. The network device according to claim 1, characterized in that, The second VLAN configuration unit is used for: Receive the second data frame from the FlexE interface board; Obtain the identifier of the target FlexE channel included in the first VLAN tag carried in the second data frame, and delete the first VLAN tag carried in the second data frame to obtain the first data frame; The first data frame is processed by the logical input port of the forwarding board corresponding to the identifier of the target FlexE channel.

4. The network device according to claim 1, characterized in that, The second VLAN configuration unit is used for: Obtain the third data frame sent to the target FlexE service port on the FlexE interface board; Based on the mapping relationship between FlexE service ports and FlexE channels, determine the target FlexE channel corresponding to the target FlexE service port; A first VLAN tag corresponding to the target FlexE channel is added to the third data frame to obtain a fourth data frame, wherein the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel; The fourth data frame is sent to the FlexE interface board.

5. The network device according to claim 4, characterized in that, The second VLAN configuration unit is specifically used for: If the third data frame carries a third VLAN tag, then the first VLAN tag corresponding to the target FlexE channel is obtained, and the other fields included in the first VLAN tag are filled with the other fields included in the third VLAN tag. The other fields are fields other than the VLAN identifier field. The first VLAN tag, after being padded, is added to the third data frame to obtain the fourth data frame.

6. The network device according to claim 4, characterized in that, The first VLAN configuration unit is used for: Receive the fourth data frame from the at least one forwarding board; The first VLAN tag carried in the fourth data frame is deleted to obtain the third data frame; Based on the mapping relationship between FlexE service ports and FlexE channels, determine the target FlexE service port corresponding to the identifier of the target FlexE channel included in the first VLAN tag; The third data frame is forwarded through the target FlexE service port.

7. The network device according to claim 1, characterized in that, The first VLAN tag is added between the source Media Access Control MAC address field and the Ethernet type field of the data frame.

8. The network device according to claim 7, characterized in that, The first VLAN tag is added between the source MAC address field of the data frame and the VLAN tag carried by the data frame.

9. The network device according to claim 1, characterized in that, The at least one forwarding board further includes a central processing unit (CPU), the CPU being used for: Multiple VLAN logical ports are created according to the specifications of the FlexE interface board, and the mapping relationship between FlexE service ports and FlexE channels is initialized according to the multiple VLAN logical ports. The VLAN logical ports correspond one-to-one with the FlexE channels. Receive a creation command for the target FlexE service port, the creation command including the client identifier of the target FlexE service port and the required target bandwidth; When the remaining FlexE service port bandwidth is greater than or equal to the target bandwidth, and there are unused FlexE channels, the target FlexE channel with the target bandwidth is allocated to the target FlexE service port. The mapping relationship between the target FlexE service port and the target FlexE channel is sent to the first VLAN configuration unit and the second VLAN configuration unit.

10. A data processing method, characterized in that, Applied to the network device according to any one of claims 1-9, the network device comprising a Flexible Ethernet (FlexE) interface board, a backplane, and at least one forwarding board; the method comprising: The first VLAN configuration unit on the FlexE interface board receives a first data frame from the target FlexE service port on the FlexE interface board; determines the target FlexE channel corresponding to the target FlexE service port according to the mapping relationship between the FlexE service port and the FlexE channel; adds a first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain a second data frame, wherein the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel; and sends the second data frame to the primary forwarding board in the at least one forwarding board. The second VLAN configuration unit on the primary forwarding board performs post-processing on the second data frame.

11. The method according to claim 10, characterized in that, The step of adding the first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain the second data frame includes: If the first data frame carries a second VLAN tag, then obtain the first VLAN tag corresponding to the target FlexE channel; Fill the other fields included in the first VLAN tag with the other fields included in the second VLAN tag, wherein the other fields are fields other than the VLAN identifier field; Add the padded first VLAN tag to the first data frame to obtain the second data frame.

12. The method according to claim 10, characterized in that, The step of performing post-processing on the second data frame includes: Obtain the identifier of the target FlexE channel included in the first VLAN tag carried in the second data frame, and delete the first VLAN tag carried in the second data frame to obtain the first data frame; The first data frame is processed by the logical input port of the forwarding board corresponding to the identifier of the target FlexE channel.

13. The method according to any one of claims 10-12, characterized in that, The first VLAN tag is added between the source MAC address field and the Ethernet type field of the first data frame.

14. The method according to claim 13, characterized in that, The first VLAN tag is added between the source MAC address field of the first data frame and the second VLAN tag carried in the first data frame.

15. A data processing method, characterized in that, Applied to the network device according to any one of claims 1-9, the network device comprising a Flexible Ethernet (FlexE) interface board, a backplane, and at least one forwarding board; the method comprising: The second VLAN configuration unit on the primary forwarding board in at least one forwarding board acquires a third data frame sent to the target FlexE service port on the FlexE interface board; determines the target FlexE channel corresponding to the target FlexE service port according to the mapping relationship between the FlexE service port and the FlexE channel; adds a first VLAN tag corresponding to the target FlexE channel to the third data frame to obtain a fourth data frame, wherein the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel; and sends the fourth data frame to the FlexE interface board. The first VLAN configuration unit on the FlexE interface board forwards the fourth data frame through the target FlexE service port.

16. The method according to claim 15, characterized in that, The step of adding the first VLAN tag corresponding to the target FlexE channel to the third data frame to obtain the fourth data frame includes: If the third data frame carries a third VLAN tag, then the first VLAN tag corresponding to the target FlexE channel is obtained; Fill the other fields included in the first VLAN tag with the other fields included in the third VLAN tag, wherein the other fields are fields other than the VLAN identifier field; The first VLAN tag, after being padded, is added to the third data frame to obtain the fourth data frame.

17. The method according to claim 15, characterized in that, The step of forwarding the fourth data frame through the target FlexE service port includes: The first VLAN tag carried in the fourth data frame is deleted to obtain the third data frame; Based on the mapping relationship between FlexE service ports and FlexE channels, determine the target FlexE service port corresponding to the identifier of the target FlexE channel included in the first VLAN tag; The third data frame is forwarded through the target FlexE service port.

18. The method according to any one of claims 15-17, characterized in that, The first VLAN tag is added between the source MAC address field and the Ethernet type field of the third data frame.

19. The method according to claim 18, characterized in that, The first VLAN tag is added between the source MAC address field of the third data frame and the third VLAN tag carried in the third data frame.

Images