Network equipment and data processing method

Abstract

The embodiment of the invention provides network equipment and a data processing method, and relates to the technical field of communication, the network equipment comprises a FlexE interface board, a backboard and at least one forwarding board; the FlexE interface board is provided with a first VLAN configuration unit, and the first VLAN configuration unit is connected with the backboard through a serializer / deserializer; a mapping relation between a FlexE service port and a FlexE channel is stored in the first VLAN configuration unit; at least one forwarding board is provided with a second VLAN configuration unit, and the second VLAN configuration unit is connected with the backboard through a serializer / deserializer; a mapping relation between a FlexE service port and a FlexE channel is stored in the second VLAN configuration unit; and the serializer / deserializer transmits data frames by adopting an Ethernet backplane protocol. According to the scheme, the chip type selection difficulty and the hardware cost of the network equipment can be reduced, and the expandability of the network equipment is improved.

Description

Technical Field

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

[0002] In network equipment, the Flexible Ethernet (FlexE) interface board and forwarding board are connected to the backplane through serializer / deserializer (such as SerDes), and the FlexE interface board and forwarding board use flexible channelization protocols (such as Interlaken protocol) to achieve flexible channelization on the serializer / deserializer data link, ensuring the forwarding resources of the forwarding board are hard-isolated from the service.

[0003] However, there are few chips that support the Interlaken protocol, which makes it difficult to select chips for FlexE interface boards and forwarding boards. In addition, the cost of chips that support the Interlaken protocol is high, which increases the hardware cost of network equipment. The existing various communication protocols and technical specifications cannot fully meet the needs of flexible channelization on the FlexE interface card system side, so there are great technical compatibility problems in solution design, which is not conducive to the innovation and upgrade of network equipment, and the scalability of network equipment is poor. Summary of the invention

[0004] The purpose of the embodiments of the present 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 improve the scalability of the network device. The specific technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a network device, including a FlexE interface board, a backplane, and at least one forwarding board;

[0006] A first virtual local area network (VLAN) configuration unit is provided on the FlexE interface board, and the first VLAN configuration unit is connected to the backplane through a serializer / deserializer; a mapping relationship between a FlexE service port and a FlexE channel is stored in the first VLAN configuration unit;

[0007] A second VLAN configuration unit is provided on the at least one forwarding board, and the second VLAN configuration unit is connected to the backplane through a serializer / deserializer; the second VLAN configuration unit stores a mapping relationship between the FlexE service port and the FlexE channel;

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

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

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

[0011] Determine a target FlexE channel corresponding to the target FlexE service port according to a mapping relationship between the FlexE service port and the FlexE channel;

[0012] Adding 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 an identifier of the target FlexE channel;

[0013] The second data frame is sent to an active forwarding board among the at least one forwarding board.

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

[0015] If the first data frame carries a second VLAN tag, obtain the first VLAN tag corresponding to the target FlexE channel, and fill 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 identification field;

[0016] The padded first VLAN tag is added to the first data frame to obtain a second data frame.

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

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

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

[0020] The first data frame is post-processed according to the logical ingress 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 to:

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

[0023] Determine a target FlexE channel corresponding to the target FlexE service port according to a mapping relationship between the FlexE service port and the FlexE channel;

[0024] Adding 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 an identifier of the target FlexE channel;

[0025] Sending the fourth data frame to the FlexE interface board.

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

[0027] If the third data frame carries a third VLAN tag, obtain a first VLAN tag corresponding to the target FlexE channel, and fill other fields included in the first VLAN tag with other fields included in the third VLAN tag, where the other fields are fields other than the VLAN identification field;

[0028] The filled first VLAN tag is added to the third data frame to obtain a fourth data frame.

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

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

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

[0032] Determine, according to a mapping relationship between a FlexE service port and a FlexE channel, 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 a source media access control MAC address field and an Ethernet type field of a data frame.

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

[0036] In some embodiments, the at least one forwarding board further includes a central processing unit (CPU), wherein the CPU is configured to:

[0037] Creating multiple VLAN logical ports according to the specifications of the FlexE interface board, and initializing a mapping relationship between the FlexE service port and the FlexE channel according to the multiple VLAN logical ports, wherein the VLAN logical ports correspond to the FlexE channels one by one;

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

[0039] When the remaining FlexE service port bandwidth is greater than or equal to the target bandwidth and there is an unoccupied FlexE channel, allocating a target FlexE channel with the target bandwidth 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] In a second aspect, an embodiment of the present application provides a data processing method, which is applied to any of the above-mentioned network devices, 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 provided on the FlexE interface board receives a first data frame from a target FlexE service port on the FlexE interface board; determines a target FlexE channel corresponding to the target FlexE service port according to a 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 an identifier of the target FlexE channel; and sends the second data frame to a primary forwarding board among the at least one forwarding board;

[0043] The second VLAN configuration unit provided on the main 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, obtaining a first VLAN tag corresponding to the target FlexE channel;

[0046] Filling 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 identification field;

[0047] The padded first VLAN tag is added to the first data frame to obtain a second data frame.

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

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

[0050] The first data frame is post-processed according to the logical ingress 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 a source MAC address field and an Ethernet type field of the first data frame.

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

[0053] In a third aspect, an embodiment of the present application provides a data processing method, which is applied to any of the above-mentioned network devices, 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 set on the main forwarding board of the at least one forwarding board obtains 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 the 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 set 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, obtaining a first VLAN tag corresponding to the target FlexE channel;

[0058] Filling 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 identification field;

[0059] The filled first VLAN tag is added to the third data frame to obtain a fourth data frame.

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

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

[0062] Determine, according to a mapping relationship between a FlexE service port and a FlexE channel, 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 a source MAC address field and an Ethernet type field of the third data frame.

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

[0066] Beneficial effects of the embodiments of the present application:

[0067] In the technical solution provided in the embodiment of the present application, VLAN configuration units are respectively arranged on the FlexE interface board and the forwarding board, and the VLAN configuration unit is connected to the backplane through a serializer / deserializer (such as SerDes), and the serializer / deserializer adopts the Ethernet backplane protocol to transmit data frames. The Ethernet backplane protocol is a standard protocol, and most of the existing FlexE interface boards and forwarding boards support the Ethernet backplane protocol, which reduces the difficulty of chip selection for the FlexE interface board and the forwarding board, and there is no need to use a dedicated chip that supports the Interlaken protocol, thereby reducing the hardware cost of the network equipment. In the embodiment of the present application, the chip selection difficulty is reduced, and the hardware cost is reduced, and the Ethernet backplane protocol is a standard protocol. The Ethernet backplane protocol is adopted to meet the needs of flexible channelization on the system side of the FlexE interface card, and the technical compatibility is good, which provides more options for the manufacture of network equipment, improves the flexibility of the manufacture of network equipment, and improves the scalability of network equipment.

[0068] Of course, implementing any product or method of the present application does not necessarily require achieving all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0070] Figure 1 A structural diagram of an existing network device;

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

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

[0073] Figure 4 A second schematic diagram of the FlexE service port creation process provided in an embodiment of the present application;

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

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

[0076] Figure 7a A first schematic diagram of adding a FlexE tag provided in an embodiment of the present application;

[0077] Figure 7b A second schematic diagram of adding a FlexE tag provided in an embodiment of the present application;

[0078] Figure 8 A third schematic diagram of adding a FlexE tag provided in an embodiment of the present application;

[0079] Fig. 9 A schematic diagram of a data processing flow in the message sending direction provided in an embodiment of the present application;

[0080] Fig.10 A first flow chart of a data processing method provided in an embodiment of the present application;

[0081] Fig.11 A second flow chart of the data processing method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0082] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field based on the present application belong to the scope of protection of the present application.

[0083] With the rapid development of network technology, the demand for transmission bandwidth and flexibility for services such as data centers and broadband access is increasing. As a new Ethernet standard, FlexE technology can meet the needs of different rates and service levels through flexible scheduling of Ethernet channels. FlexE technology is widely used in network equipment. By decoupling the Ethernet multimedia access control (Media Access Control, MAC) layer and the physical (Physics, PHY) layer, it realizes low-cost, highly reliable, and dynamically allocable interface technology.

[0084] The structure of network equipment is as follows Figure 1 As shown in the figure, it includes a FlexE interface board, multiple forwarding boards and a backplane. Figure 1The main forwarding board and the standby forwarding board are shown. The FlexE interface board and multiple forwarding boards are connected to the backplane through SerDes (serializer / deserializer). Among them, the FlexE interface board can include the FlexE intellectual property core (Intellectual Property Core, IP Core), the Time Synchronized Mesh Protocol for Media Access Control (TS-MAC) module and the communication IP Core on the system side, etc. The forwarding board can include a forwarding chip and a central processing unit (CPU), etc.

[0085] Among them, the FlexE IP Core is used to implement the FlexE shim layer and the Physical Coding Sublayer (PCS) / Physical Medium Attachment (PMA), and to map and demap the FlexE Client and FlexE Group; the TS-MAC module is used to implement the FlexE client rate matching; the communication IP Core on the system side and the communication IP Core set on the forwarding chip are used to implement flexible channelization between the FlexE interface board and the forwarding board. The CPU is used to control the forwarding chip and each module on the FlexE interface board.

[0086] In network equipment, FlexE interfaces are generally expanded in the form of FlexE interface boards. The panel side of the FlexE interface board is connected to the remote device through an optical module, and the panel side of the FlexE interface board uses the FlexE shim layer to achieve decoupling of the MAC layer and the PHY layer of the FlexE interface; the system side of the FlexE interface board is connected to the forwarding board. Usually, the FlexE interface uses hardware chips such as Field-Programmable Gate Array (FPGA) or MAC chips to implement hard channelization of the FlexE service port. The system side of the FlexE interface board also needs to implement channelization slicing to ensure the hard isolation of the forwarding resources of the forwarding board and the service, which requires that the channel between the system side of the FlexE interface board and the forwarding board must meet flexible channelization.

[0087] Currently, network devices generally use a specified flexible channelization protocol (such as the Interlaken protocol) to implement flexible channelization on SerDes data links. Figure 1The communication IP Core shown may be an Interlaken IP Core. The Interlaken protocol is a high-bandwidth, high-performance data transmission protocol for inter-chip communication. It optimizes SerDes technology and reduces the complexity of protocol processing to achieve efficient and flexible communication. The main features of the Interlaken protocol are scalability and low-latency data transmission, which adapts to the flexible channelization requirements of the FlexE interface board system side.

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

[0089] (1) Limited chip support: In network equipment, especially the selection of chips for FlexE interface boards and forwarding boards, a major problem 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 increases the hardware cost of R&D and deployment.

[0090] (2) High hardware cost: To meet the needs of flexible channelization, 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: The existing communication protocols and technical specifications cannot fully meet the requirements of flexible channelization on the FlexE interface card system side. This leads to great technical compatibility problems in solution design, which is not conducive to the innovation and upgrade of network equipment. For chips that support the Interlaken protocol in some slots, the scalability of the new chassis design is poor.

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

[0093] To solve the above problems, the present application provides 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 In the figure, only two forwarding boards 203 are used as an example for explanation, which is not limiting.

[0094] A first VLAN configuration unit 211 is provided on the FlexE interface board 201, and the first VLAN configuration unit 211 is connected to the backplane 202 through a serializer / deserializer; a mapping relationship between a FlexE service port and a FlexE channel is stored in the first VLAN configuration unit 211;

[0095] A second VLAN configuration unit 213 is provided on the at least one forwarding board 203, and the second VLAN configuration unit 213 is connected to the backplane 202 through a serializer / deserializer; the second VLAN configuration unit 213 stores a mapping relationship between the FlexE service port and the FlexE channel;

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

[0097] In the technical solution provided in the embodiment of the present application, VLAN configuration units are respectively arranged on the FlexE interface board and the forwarding board, and the VLAN configuration unit is connected to the backplane through a serializer / deserializer (such as SerDes), and the serializer / deserializer adopts the Ethernet backplane protocol to transmit data frames. The Ethernet backplane protocol is a standard protocol, and most of the existing FlexE interface boards and forwarding boards support the Ethernet backplane protocol, which reduces the difficulty of chip selection for the FlexE interface board and the forwarding board, and there is no need to use a dedicated chip that supports the Interlaken protocol, thereby reducing the hardware cost of the network equipment. In the embodiment of the present application, the chip selection difficulty is reduced, and the hardware cost is reduced, and the Ethernet backplane protocol is a standard protocol. The Ethernet backplane protocol is adopted to meet the needs of flexible channelization on the system side of the FlexE interface card, and the technical compatibility is good, which provides more options for the manufacture of network equipment, improves the flexibility of the manufacture of network equipment, and improves the scalability of network equipment.

[0098] In the embodiment of the present application, the network device may 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 further include a FlexE IP Core and a TS-MAC module, and the forwarding board 203 may further include a CPU, and the like.

[0099] The FlexE IP Core is used to implement the FlexE Shim layer and PCS / PMA, and to map and demap the FlexE Client and FlexE Group. The TS-MAC module is used to implement the 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 of the FlexE interface board 201 can be FPGA or MAC chip with FlexE function. A VLAN configuration unit, namely the first VLAN configuration unit 211, is set on the FlexE interface board 201. The first VLAN configuration unit 211 is located on the system side of the FlexE interface board 201. The first VLAN configuration unit 211 is responsible for parsing and configuring the FlexE tag (TAG) of the Ethernet backplane channel, and realizes the mutual mapping between the channel identifier (Channel ID) of the FlexE tag and the FlexE Client ID.

[0101] When the network device includes multiple forwarding boards 203, the multiple forwarding boards 203 may include one active forwarding board and one or more standby forwarding boards. Figure 2 The example of a main forwarding board and a standby forwarding board is taken as an example, which does not serve as a limitation. A VLAN configuration unit is set on the forwarding board 203, that is, a second VLAN configuration unit 213. The second VLAN configuration unit 213 can be set on a forwarding chip in the forwarding board 203, such as Figure 2 As shown in the figure, the forwarding chip can be a switching chip or a network processor (NP) chip. 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 the backplane 202 and a serializer / deserializer (such as SerDes). On the serializer / deserializer data link, the data frame is transmitted using the Ethernet backplane protocol, which is compatible with most forwarding chips.

[0103] In the embodiment of the present application, in order to achieve fine-grained resource management and data isolation, when the FlexE interface board is initialized, according to the forwarding chip resources and product specifications (i.e., the specifications of the FlexE interface board), the system side of the FlexE interface board and the forwarding board respectively statically initialize one or more Ethernet ports. For example, if the specification of the FlexE interface board is 100G and the specification of one Ethernet port is 100G, then one Ethernet port can be statically initialized on the system side of the FlexE interface board and the forwarding board respectively; if the specification of one Ethernet port is 50G, then two Ethernet ports can be statically initialized on the system side of the FlexE interface board and the forwarding board respectively.

[0104] The Ethernet backplane protocol is configured between the system side of the FlexE interface 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 be connected to the backplane 202 through the serializer / deserializer using the Ethernet backplane protocol on the Ethernet port, thereby realizing the connection between the forwarding board 203 and the FlexE interface board 201 using the Ethernet backplane protocol.

[0105] Based on the Ethernet port, the CPU on the forwarding board 203 side performs VLAN division according to the specifications of the FlexE interface board, that is, statically creates a VLAN logical port (i.e., a virtual interface) corresponding to the specifications of the FlexE service port to ensure that each VLAN logical port has independent forwarding resources to achieve fine-grained resource management and data isolation. For example, the minimum granularity of FlexE is 5G, and the specification of the 100GFlexE interface board is 100G / 5G=20 FlexE service ports, that is, the 100GFlexE interface board can create up to 20 FlexE service ports. When the FlexE interface board 201 is initialized, the system side of the forwarding board 203 and the FlexE interface board 201 creates a 100G Ethernet port, and creates 20 VLAN logical ports based on this Ethernet port. The VLAN logical ports correspond to the FlexE service ports one by one, as shown in Table 1.

[0106] Table 1

[0107]

[0108] Table 1, the client ID corresponds to the FlexE service port, that is, the Client IDs numbered from 1 to 20 correspond to one FlexE service port respectively. The channel ID corresponds to the VLAN logical port, that is, the Channel IDs numbered from 1 to 20 correspond to one VLAN logical port respectively. In the embodiment of the present application, a VLAN logical port is a FlexE channel, and the identifier (Channel ID) of the FlexE channel is the VLAN identifier (VLAN ID) of the VLAN logical port.

[0109] By initializing the VLAN logical port, FlexE initializes multiple VLAN logical ports on the interface board and forwarding board through different VLAN IDs, which can achieve the purpose of resource separation and isolation. In addition, the CPU can obtain the static mapping relationship between the FlexE service port and the FlexE channel. Subsequently, the CPU of the active forwarding board can execute dynamic creation of 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 the FlexE service port and the FlexE channel, please refer to the relevant description of the initialization part of the FlexE interface board above, which will not be repeated here.

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

[0113] In an embodiment of the present application, a management module of a FlexE interface board may be designed. The management module provides an interface and a control plane. A user may use the management module to construct a command line for creating a FlexE service port, such as a command for creating a target FlexE service port. The management module sends a command for creating a target FlexE service port, i.e., the above-mentioned creation command, to the CPU.

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

[0115] After receiving the create command, the CPU can extract the client ID and target bandwidth of the target FlexE service port from the create command, and then determine whether the service port resources are remaining, that is, whether the remaining FlexE service port bandwidth is greater than or equal to the target bandwidth, and whether there are unoccupied FlexE channels. If the service port resources are remaining, that is, the remaining FlexE service port bandwidth is greater than or equal to the target bandwidth, and there are unoccupied FlexE channels, the CPU can allocate the target FlexE channel with the target bandwidth to the target FlexE service port.

[0116] If there are no remaining service port resources, 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 prompt message indicating insufficient service port resources to prompt the user to solve the problem as soon as possible.

[0117] For example, the CPU initializes the 100G FlexE interface board, and the mapping relationship is shown in Table 1. The CPU receives the creation command 1, which includes Client ID 2 and the target bandwidth 50G. The CPU determines that the remaining FlexE service port bandwidth is 100G>50G, and all 20 FlexE channels are not occupied. Then, a 50G FlexE channel is allocated to the FlexE service port of Client ID 2, such as FlexE channel 1. At this time, the mapping relationship between the dynamically created FlexE service port and the FlexE channel is shown in Table 2.

[0118] Table 2

[0119]

[0120] The CPU receives the creation command 2, which includes the Client ID 21 and the target bandwidth 40G. The CPU determines that the remaining FlexE service port bandwidth is 100G-50G=50G>40G, and 19 FlexE channels are not occupied, so a 40G FlexE channel is allocated to the FlexE service port of Client ID 21, such as FlexE channel 2. At this time, the mapping relationship between the dynamically created FlexE service port and the FlexE channel is shown in Table 3.

[0121] Table 3

[0122]

[0123] The CPU receives creation command 3, which includes Client ID 1 and target bandwidth 20G. The CPU determines that the remaining FlexE service port bandwidth is 50G-40G=10G<20G, and outputs a prompt message indicating that the service port resources are insufficient. No FlexE channel is allocated 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 FlexE channel of the target bandwidth to the target FlexE service port, the CPU obtains the mapping relationship between the target FlexE service port and the target FlexE channel, and can then issue the mapping relationship to the first VLAN configuration unit 211 and the second VLAN configuration unit 213 .

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

[0127] Step S401: The management module sends a command line for creating a FlexE service port to the CPU. For details, please refer to the relevant description of the above step S302.

[0128] In step S402, the CPU determines whether there are any remaining service port resources. If there are any remaining service port resources, step S403 is executed; if there are no remaining service port resources, step S407 is executed. For details, please refer to the relevant description of step S303 above.

[0129] Step S403: The CPU adds the Client ID in the command line to the port device chain. This facilitates the CPU to manage the FlexE service port. The port device chain is used to store the Client ID of the FlexE service port.

[0130] Step S404: The CPU applies for service port resources and allocates a unique VLAN tag for the entire machine.

[0131] In the embodiment of the present application, the CPU allocates a FlexE channel and the bandwidth of the FlexE channel to the FlexE service port, and divides a unique VLAN tag of the entire machine corresponding to the FlexE service port. The VLAN tag is the FlexE tag, such as Figure 5 As shown in the figure, it includes a tag protocol identifier (TPID) and a customer tag (C-Tag). The customer tag includes a priority code point (PCP), a drop eligible indicator (DEI) and a channel identifier (ie, a VLAN identifier).

[0132] In the divided VLAN tags, TPID, PCP and DEI can all use default values, such as TPID=0x8100, and the default value is pre-set in the CPU.

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

[0134] In an embodiment of the present 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, and 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] Step S406: The FlexE IP Core creates a corresponding FlexE service port according to the received information.

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

[0137] Step S407: The CPU returns a prompt message indicating that service port resources are insufficient to the management module.

[0138] In the embodiment of the present application, users can flexibly configure VLAN division rules and channel mapping rules to achieve dynamic adjustment of FlexE service ports and VLAN logical ports. Through reasonable VLAN division and allocation of FlexE channels with required bandwidth, a similar effect to hard slicing is achieved, ensuring that different FlexE channels have independent and isolated forwarding resources, avoiding excessive hardware overhead, and achieving efficient use of hardware resources, improving cost performance. In addition, the system side of the FlexE interface board uses VLAN technology to divide FlexE channels, which can achieve flexible pairing with different types of forwarding chips, allowing the device to adapt to a variety of network environments and application scenarios.

[0139] After the mapping relationship between the FlexE service port and the FlexE channel is sent to the hardware, the network device can use the corresponding FlexE service port to process data. The following uses the two scenarios of message receiving direction and message sending direction as examples to illustrate the data processing process.

[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 the first VLAN tag corresponding to the target FlexE channel in the first data frame to obtain a second data frame, and the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel; send the second data frame to the main 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 the first data frame; 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 Figure 6 Steps S601 to S606 are shown.

[0141] In the embodiment of the present application, 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 the FlexE IP Core receives the first data frame through the target FlexE service port, it 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 according to 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, and adds the first VLAN tag corresponding to the target FlexE channel to the first data frame to obtain the second data frame.

[0143] In the embodiment of the present application, the first VLAN tag can be added to the data frame at a preset position. In order to adapt to existing standards and facilitate the implementation of the embodiment of the present application, 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 (i.e., the first VLAN tag) shown in FIG. 4 is a VLAN tag located at the VLAN tag position specified in the existing standard protocol. In the case of the second VLAN tag carried by 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 by the first data frame, such as Figure 7b The 4-byte FlexE tag (ie, the first VLAN tag) is shown. At this time, the first VLAN tag is still located at the VLAN tag position specified in the existing standard protocol. Figure 7b The VLAN tag in is the original VLAN tag carried by the data frame, such as the second VLAN tag.

[0144] Figure 7a and Figure 7b In the data frame, the data frame may also include a destination MAC address field DA, a cyclic redundancy check (CRC) field, and a 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 be specifically used to: if the first data frame carries a second VLAN tag, obtain the first VLAN tag corresponding to the target FlexE channel, fill other fields included in the first VLAN tag with other fields included in the second VLAN tag, and the other fields are fields other than the VLAN identification field; add the filled first VLAN tag to the first data frame to obtain the second data frame. Figure 8 In the data frame shown, the PCP field and DEI field included in the FlexE tag reuse the PCP field and DEI field included in the VLAN tag originally carried by the data frame. By reusing other fields included in the VLAN tag originally carried by the data frame, it is convenient to perform traffic classification control on the data frame.

[0146] After obtaining the second data frame, the first VLAN configuration unit 211 sends the second data frame to the backplane 22 via the serializer / deserializer using the Ethernet backplane protocol; the backplane 22 sends the second data frame to the second VLAN configuration unit 213 via the 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 by the second data frame, and then determine the logical inbound port of the forwarding board corresponding to the identifier of the target FlexE channel, and delete the first VLAN tag carried in the second data frame to restore the first data frame to the first data frame. The second VLAN configuration unit 213 can transmit the logical inbound port of the forwarding board corresponding to the identifier of the target FlexE channel to the processing unit of the forwarding chip, and the processing unit performs post-processing on the first data frame according to the logical inbound port and the forwarding table, which ensures the normal processing of the first data frame.

[0148] The above-mentioned processing unit performs post-processing on the first data frame, which may be: sending the first data frame to the FlexE interface board through the second VLAN configuration unit 213, and the FlexE interface board forwards it to the remote device. The processing unit performs post-processing on the first data frame, which may also be: sending the first data frame to the CPU, and the CPU processes the first data frame. The embodiment of the present application does not limit the specific method of post-processing the first data frame.

[0149] In the embodiment of the present application, after receiving the second data frame, the second VLAN configuration unit 213 may also send the second data frame to the CPU, and the CPU processes the second data frame. The embodiment of the present application does not limit the specific manner in which the second VLAN configuration unit 213 processes the second data frame.

[0150] In the message sending direction, the second VLAN configuration unit 213 can be used to: obtain a third data frame to be 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 the first VLAN tag corresponding to the target FlexE channel to the third data frame to obtain a fourth data frame, and the VLAN identifier included in the first VLAN tag is the identifier of the target FlexE channel; 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 Fig. 9 Steps S901 to S907 are shown.

[0151] In the embodiment of the present application, 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 according to 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, and adds the first VLAN tag corresponding to the target FlexE channel to the third data frame to obtain a fourth data frame.

[0153] In the embodiment of the present application, the first VLAN tag can be added to the data frame at a preset position. In order to adapt to existing standards and facilitate the implementation of the embodiment of the present application, 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 In the case where the third data frame carries a third VLAN tag, 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, as shown in FIG. Figure 7b The 4-byte FlexE tag is shown. Figure 7b The VLAN tag in 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 be specifically used to: if the third data frame carries the third VLAN tag, obtain the first VLAN tag corresponding to the target FlexE channel, fill other fields included in the first VLAN tag with other fields included in the third VLAN tag, and the other fields are fields other than the VLAN identification field; add the filled first VLAN tag to the third data frame to obtain a fourth data frame. Figure 8 In the data frame shown, the PCP field and DEI field included in the FlexE tag reuse the PCP field and DEI field included in the VLAN tag originally carried by the data frame. By reusing other fields included in the VLAN tag originally carried by the data frame, it is convenient to perform traffic classification control on the data frame.

[0155] After receiving the fourth data frame, the second VLAN configuration unit 213 sends the fourth data frame to the backplane 22 via the serializer / deserializer using the Ethernet backplane protocol; the backplane 22 sends the fourth data frame to the first VLAN configuration unit 211 via the 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, and 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 issued by the CPU, and send the third data frame 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 the embodiment of the present application, 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 through the TS-MAC module, and the FlexE IP Core 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. The embodiment of the present application does not limit the specific manner in which the first VLAN configuration unit 211 processes the fourth data frame.

[0158] The technical solution provided in the embodiments of the present application solves the problems of limited chip support, high hardware cost and technical compatibility in network equipment, as follows:

[0159] (1) Extended compatibility: Based on the Ethernet backplane protocol, VLAN technology is used to divide channels, that is, VLAN logical port division, to improve the compatibility of the flexible channelization implementation solution with the FlexE interface board and forwarding board, avoiding the selection of high-cost dedicated chips that support the Interlaken protocol, expanding the range of usable chip categories, and thus providing more choices and flexibility for equipment manufacturing.

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

[0161] (2) Reduce hardware costs: Without the need to replace the existing network equipment infrastructure, the Ethernet backplane protocol and VLAN technology are used to achieve efficient interconnection and flexible scheduling of network equipment, reducing the system hardware procurement and maintenance costs, ensuring that the overall cost of equipment manufacturing and assembly is within an acceptable range, and adapting to the needs of different scenarios. It is particularly suitable for the construction of large-scale network equipment.

[0162] In addition, through reasonable VLAN division and forwarding resource scheduling, 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: Provide a flexible VLAN division method, that is, without changing the physical network topology, implement different VLAN logical ports between the FlexE interface board and the forwarding board, and use VLAN tags to allocate services, as well as adjust bandwidth and forwarding resources, providing flexible and convenient adjustment methods for multiple business scenarios.

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

[0165] (4) Realizing the effect of hard slicing: Using VLAN technology to divide and manage Ethernet channels, physical and logical isolation of channels and resources is achieved, ensuring that each service data has independent bandwidth and forwarding resources, providing an effect similar to professional hard slicing, enabling network resources to be used more efficiently and securely, thereby enhancing the security and stability of network resources.

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

[0167] (5) Improve system performance and reliability: Through the high-speed SerDes interface and standard Ethernet backplane protocol, high-speed, low-latency data transmission is achieved, ensuring the performance of the system; in addition, hard channel processing and resource partitioning technology (that is, the above-mentioned technology of using VLAN technology to divide and manage Ethernet channels) ensures the load balancing and stable operation of the system, improving the overall reliability of the system.

[0168] Through the technical solution proposed in the embodiment of this application, the network equipment uses VLAN technology and Ethernet backplane protocol to solve chip selection and compatibility problems, reduce hardware costs and deployment complexity. The implementation of this application provides a flexible and efficient channel division and resource management method, achieves high compatibility, low cost, flexible management, efficient transmission and stable operation, greatly improves the economic benefits and operational flexibility of the system, and meets the challenges of modern network equipment for high bandwidth and diversified service requirements.

[0169] Corresponding to the above network device, the embodiment of the present application also provides a data processing method, such as Fig.10 As shown, the method is applied to the above network device, the network device may include a FlexE interface board, a backplane and at least one forwarding board, and the specific structure can be referred to in Figure 2 As shown; the method comprises the following steps:

[0170] Step S1001, a first VLAN configuration unit set on the FlexE interface board receives a first data frame from a target FlexE service port on the FlexE interface board;

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

[0172] Step S1003: The first VLAN configuration unit 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;

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

[0174] Step S1005: The second VLAN configuration unit provided on the active forwarding board performs post-processing on the second data frame.

[0175] In the technical solution provided in the embodiment of the present application, VLAN configuration units are respectively arranged on the FlexE interface board and the forwarding board, and the VLAN configuration unit is connected to the backplane through a serializer / deserializer (such as SerDes), and the serializer / deserializer adopts the Ethernet backplane protocol to transmit data frames. The Ethernet backplane protocol is a standard protocol, and most of the existing FlexE interface boards and forwarding boards support the Ethernet backplane protocol, which reduces the difficulty of chip selection for the FlexE interface board and the forwarding board, and there is no need to use a dedicated chip that supports the Interlaken protocol, thereby reducing the hardware cost of the network equipment. In the embodiment of the present application, the chip selection difficulty is reduced, and the hardware cost is reduced, and the Ethernet backplane protocol is a standard protocol. The Ethernet backplane protocol is adopted to meet the needs of flexible channelization on the system side of the FlexE interface card, and the technical compatibility is good, which provides more options for the manufacture of network equipment, improves the flexibility of the manufacture of network equipment, and improves the scalability of network equipment.

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

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

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

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

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

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

[0182] According to the logical ingress port of the forwarding board corresponding to the identifier of the target FlexE channel, the first data frame is post-processed.

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

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

[0185] Corresponding to the above network device, the embodiment of the present application also provides a data processing method, such as Fig.11 As shown, the method is applied to the above network device, the network device may include a FlexE interface board, a backplane and at least one forwarding board, and the specific structure can be referred to in Figure 2 As shown; the method comprises the following steps:

[0186] Step S1101: a second VLAN configuration unit set on a master forwarding board among at least one forwarding board acquires a third data frame sent to a target FlexE service port on a FlexE interface board;

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

[0188] Step S1103: The second VLAN configuration unit adds a first VLAN tag corresponding to the target FlexE channel to the third data frame to obtain a fourth data frame, where 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] 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 the embodiment of the present application, VLAN configuration units are respectively arranged on the FlexE interface board and the forwarding board, and the VLAN configuration unit is connected to the backplane through a serializer / deserializer (such as SerDes), and the serializer / deserializer adopts the Ethernet backplane protocol to transmit data frames. The Ethernet backplane protocol is a standard protocol, and most of the existing FlexE interface boards and forwarding boards support the Ethernet backplane protocol, which reduces the difficulty of chip selection for the FlexE interface board and the forwarding board, and there is no need to use a dedicated chip that supports the Interlaken protocol, thereby reducing the hardware cost of the network equipment. In the embodiment of the present application, the chip selection difficulty is reduced, and the hardware cost is reduced, and the Ethernet backplane protocol is a standard protocol. The Ethernet backplane protocol is adopted to meet the needs of flexible channelization on the system side of the FlexE interface card, and the technical compatibility is good, which provides more options for the manufacture of network equipment, improves the flexibility of the manufacture of network equipment, and improves the scalability of network equipment.

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

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

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

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

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

[0197] Deleting the first VLAN tag carried in the fourth data frame to obtain a third data frame;

[0198] Determine, according to a mapping relationship between the FlexE service port and the FlexE channel, a 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 a source MAC address field and an Ethernet type field of the third data frame.

[0201] 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.

[0202] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using 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, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a 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 transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0203] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0204] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the method embodiment, since it is basically similar to the network device embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the network device embodiment.

[0205] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A network device, characterized in that: It includes a flexible Ethernet FlexE interface board, a backplane and at least one forwarding board; A first virtual local area network VLAN configuration unit is provided on the FlexE interface board, and the first VLAN configuration unit is connected to the backplane through a serializer / deserializer; a mapping relationship between a FlexE service port and a FlexE channel is stored in the first VLAN configuration unit; A second VLAN configuration unit is provided on the at least one forwarding board, and the second VLAN configuration unit is connected to the backplane through a serializer / deserializer; the second VLAN configuration unit stores a mapping relationship between the FlexE service port and the FlexE channel; The serializer / deserializer uses the Ethernet backplane protocol to transmit data frames.

2. The network device according to claim 1, characterized in that: The first VLAN configuration unit is used for: Receiving a first data frame from a target FlexE service port on the FlexE interface board; Determine a target FlexE channel corresponding to the target FlexE service port according to a mapping relationship between the FlexE service port and the FlexE channel; Adding 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 an identifier of the target FlexE channel; The second data frame is sent to an active forwarding board among the at least one forwarding board.

3. The network device according to claim 2, characterized in that: The first VLAN configuration unit is specifically used for: If the first data frame carries a second VLAN tag, obtain the first VLAN tag corresponding to the target FlexE channel, and fill 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 identification field; The padded first VLAN tag is added to the first data frame to obtain a second data frame.

4. The network device according to claim 2, characterized in that: The second VLAN configuration unit is used for: receiving the second data frame from the FlexE interface board; Acquire the identifier of the target FlexE channel included in the first VLAN tag carried by the second data frame, and delete the first VLAN tag carried by the second data frame to obtain the first data frame; The first data frame is post-processed according to the logical ingress port of the forwarding board corresponding to the identifier of the target FlexE channel.

5. The network device according to claim 1, characterized in that: The second VLAN configuration unit is used for: Acquire a third data frame sent to a target FlexE service port on the FlexE interface board; Determine a target FlexE channel corresponding to the target FlexE service port according to a mapping relationship between the FlexE service port and the FlexE channel; Adding 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 an identifier of the target FlexE channel; Sending the fourth data frame to the FlexE interface board.

6. The network device according to claim 5, characterized in that: The second VLAN configuration unit is specifically used for: If the third data frame carries a third VLAN tag, obtain a first VLAN tag corresponding to the target FlexE channel, and fill other fields included in the first VLAN tag with other fields included in the third VLAN tag, where the other fields are fields other than the VLAN identification field; The filled first VLAN tag is added to the third data frame to obtain a fourth data frame.

7. The network device according to claim 5, characterized in that: The first VLAN configuration unit is used for: receiving the fourth data frame from the at least one forwarding board; Deleting the first VLAN tag carried in the fourth data frame to obtain the third data frame; Determine, according to a mapping relationship between a FlexE service port and a FlexE channel, 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.

8. The network device according to any one of claims 2 to 7, characterized in that: The first VLAN tag is added between a source media access control MAC address field and an Ethernet type field of the data frame.

9. The network device according to claim 8, 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.

10. The network device according to any one of claims 1 to 7, characterized in that: The at least one forwarding board further includes a central processing unit (CPU), wherein the CPU is used for: Creating multiple VLAN logical ports according to the specifications of the FlexE interface board, and initializing a mapping relationship between the FlexE service port and the FlexE channel according to the multiple VLAN logical ports, wherein the VLAN logical ports correspond to the FlexE channels one by one; Receive a creation command for a target FlexE service port, where the creation command includes a client identifier and a required target bandwidth of the target FlexE service port; When the remaining FlexE service port bandwidth is greater than or equal to the target bandwidth and there is an unoccupied FlexE channel, allocating a target FlexE channel with the target bandwidth 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.

11. A data processing method, characterized in that: Applied to the network device according to any one of claims 1 to 10, the network device comprises a Flexible Ethernet FlexE interface board, a backplane and at least one forwarding board; the method comprises: The first VLAN configuration unit provided on the FlexE interface board receives a first data frame from a target FlexE service port on the FlexE interface board; determines a target FlexE channel corresponding to the target FlexE service port according to a 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 an identifier of the target FlexE channel; and sends the second data frame to a primary forwarding board among the at least one forwarding board; The second VLAN configuration unit provided on the main forwarding board performs post-processing on the second data frame.

12. The method according to claim 11, 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, obtaining a first VLAN tag corresponding to the target FlexE channel; Filling 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 identification field; The padded first VLAN tag is added to the first data frame to obtain a second data frame.

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

14. The method according to any one of claims 11 to 13, characterized in that: The first VLAN tag is added between a source MAC address field and an Ethernet type field of the first data frame.

15. The method according to claim 14, 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 by the first data frame.

16. A data processing method, characterized in that: Applied to the network device according to any one of claims 1 to 10, the network device comprises a Flexible Ethernet FlexE interface board, a backplane and at least one forwarding board; the method comprises: The second VLAN configuration unit set on the main forwarding board of the at least one forwarding board obtains 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 the 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 set on the FlexE interface board forwards the fourth data frame through the target FlexE service port.

17. The method according to claim 16, characterized in that The step of adding the first VLAN tag corresponding to the target FlexE channel in the third data frame to obtain a fourth data frame includes: If the third data frame carries a third VLAN tag, obtaining a first VLAN tag corresponding to the target FlexE channel; Filling 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 identification field; The filled first VLAN tag is added to the third data frame to obtain a fourth data frame.

18. The method according to claim 16, characterized in that The step of forwarding the fourth data frame through the target FlexE service port includes: Deleting the first VLAN tag carried in the fourth data frame to obtain the third data frame; Determine, according to a mapping relationship between a FlexE service port and a FlexE channel, 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.

19. The method according to any one of claims 16 to 18, characterized in that: The first VLAN tag is added between a source MAC address field and an Ethernet type field of the third data frame.

20. The method according to claim 19, 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 by the third data frame.

Images