Energy-saving method and related equipment

Abstract

The embodiment of the invention provides an energy-saving method and related equipment, and the method comprises the steps: obtaining a plurality of instances, interleaving the plurality of instances, and distributing the interleaved instances to a plurality of service flows, the plurality of service flows comprising a first type of service flows and a second type of service flows, the first type of service flows being only composed of idle instances, and the second type of service flows comprising non-idle instances; closing PCS processing on the first type of service flow, and performing PCS processing on the second type of service flow to obtain a service code stream; generating a pseudo-random code stream; performing PMA bit multiplexing on the service code stream and the pseudo-random code stream to obtain target data; and sending the target data at the physical port.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an energy-saving method and related equipment. Background Art

[0002] Flexible Ethernet (FlexE) is a technology developed on the basis of Ethernet technology to meet the needs of flexible bandwidth configuration, service isolation, etc. It breaks the one-to-one mapping relationship between the MAC layer and the PHY layer, realizes flexible and refined management of interface resources, and solves the problem of imbalance between different customer service needs and network capabilities.

[0003] FlexE has evolved from FlexE 1.0 (100G), FlexE 2.0 (200G / 400G), and FlexE 2.1 (50G), and the FlexE architecture based on 800G / 1.6T is also under discussion. The 800G / 1.6T Ethernet architecture has changed from the previous 200G / 400G / 100G / 50G Ethernet architecture, from the original single-stream architecture to a dual-stream architecture, and the interleaving granularity of different instances has changed from a single 64B / 66B in the low-speed era to a 4×66B granularity equivalent to 256B / 257B.

[0004] In order to save energy in the 800G / 1.6T Ethernet architecture, one possible energy-saving method is to directly shut down the related processing of a single service flow, but this method may have an impact on the service. Summary of the invention

[0005] The present application provides an energy-saving method and related equipment, which are used to achieve energy saving in a flexible Ethernet with a multi-stream architecture by shutting down related processing of business flows without affecting the business.

[0006] The first aspect of the present application provides an energy-saving method, which is applied to a sending-end network device in a flexible Ethernet with a multi-stream architecture:

[0007] Acquire multiple instances, including N idle instances and non-idle instances, N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow; distribute the multiple instances to multiple service flows after interleaving, the multiple service flows include first-type service flows and second-type service flows, the first-type service flows are composed of idle instances only, and the second-type service flows include non-idle instances; turn off physical coding sublayer (PCS) processing of the first-type service flow, and perform PCS processing on the second-type service flow to obtain a service code stream; generate a pseudo-random code stream; perform bit multiplexing of the service code stream and the pseudo-random code stream on a physical medium attachment sublayer (PMA) to obtain target data; send the target data at a physical port.

[0008] In the present application, when the number of idle instances is greater than or equal to the maximum number of instances carried by a single service flow, the idle instances can be distributed to the same service flow through a specific interleaving method. For such service flows, no PCS processing is required. At the same time, in order to ensure the normal bit multiplexing of PMA, a pseudo-random code stream can be generated, and the pseudo-random code stream is used as the result of PCS processing of the above service flow, and it is involved in the bit multiplexing of PMA, thereby achieving energy saving while ensuring the normal operation of the service.

[0009] In a possible implementation, multiple instances are interleaved and distributed to multiple service flows as follows:

[0010] Multiple instances are interleaved in a manner of selecting a code block set of one instance from the multiple instances for interleaving each time, the code block set includes S code blocks, and the code block sets of two non-idle instances are separated by K-1 code block sets of idle instances, where K is the number of multiple business flows; each code block set in the interleaved multiple instances is staggered and distributed to the multiple business flows one by one.

[0011] In the present application, the code block sets of two non-idle instances are spaced by K-1 code block sets of idle instances during interleaving, thereby ensuring that the non-idle instances can be distributed to the same service flow.

[0012] In one possible implementation, S is 1 or 4.

[0013] In a possible implementation, the PCS processing includes transcoding, scrambling, forward error correction (FEC) encoding, and alignment marker insertion.

[0014] In a possible implementation, the pseudo-random code stream is a PRBS31 code stream, a PRBS9 code stream, a PRBS21 code stream, a PRBS23 code stream, or a PRBS7 code stream.

[0015] In one possible implementation, the interface rate of the transmitting network device is 800G, including two service flows.

[0016] In one possible implementation, M is 4, and a single instance carries 100G of customer services.

[0017] The second aspect of the present application provides an energy-saving method, which is applied to a sending-end network device in a flexible Ethernet with a multi-stream architecture:

[0018] Acquire multiple instances, including N idle instances and non-idle instances, N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow; distribute the multiple instances to multiple service flows after interleaving, the multiple service flows include first-type service flows and second-type service flows, the first-type service flows are composed of idle instances only, and the second-type service flows include non-idle instances; turn off PCS processing, PMA processing, and PMD processing for the first-type service flows; perform PCS processing on the second-type service flows to obtain a service code stream; perform PMA bit multiplexing on the service code stream, and the rule of bit multiplexing is to multiplex the data of multiple virtual channels of the same service code stream onto one physical port to obtain target data; send the target data on the physical port.

[0019] In the present application, when the number of idle instances is greater than or equal to the maximum number of instances carried by a single service flow, the idle instances can be distributed to the same service flow through a specific interleaving method. For such a service flow, no PCS processing, PMA processing, and physical medium dependent (PMD) processing is required. At the same time, in order to ensure the normal bit multiplexing of PMA, the data of multiple VLs of the same service code stream can be multiplexed to one physical port, thereby achieving energy saving while ensuring the normal operation of the service.

[0020] In a possible implementation, multiple instances are interleaved and distributed to multiple service flows as follows:

[0021] Multiple instances are interleaved in a manner of selecting a code block set of one instance from the multiple instances for interleaving each time, the code block set includes S code blocks, and the code block sets of two non-idle instances are separated by K-1 code block sets of idle instances, where K is the number of multiple business flows; each code block set in the interleaved multiple instances is staggered and distributed to the multiple business flows one by one.

[0022] In one possible implementation, S is 1 or 4.

[0023] In a possible implementation, the PCS processing includes transcoding, scrambling, FEC encoding, and alignment marker insertion.

[0024] In one possible implementation, the interface rate of the transmitting network device is 800G, including two service flows.

[0025] In one possible implementation, M is 4, and a single instance carries 100G of customer services.

[0026] The third aspect of the present application provides an energy-saving method, which is applied to a receiving-end network device in a flexible Ethernet with a multi-stream architecture:

[0027] Acquire multiple instances, including N idle instances and non-idle instances, N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow. Divide the multiple instances into multiple instance groups, including a first type group and a second type group, the first type group only includes idle instances, and the second type group includes non-idle instances. Interleave the instances in the same instance group to obtain a corresponding service flow. Turn off PCS processing for the first type of service flow, and perform PCS processing on the second type of service flow to obtain a service code stream, the first type of service flow is obtained by interleaving the instances in the first type group, and the second type of service flow is obtained by interleaving the instances in the second type group. Generate a pseudo-random code stream, and perform PMA bit multiplexing on the service code stream and the pseudo-random code stream to obtain target data. Send the target data on the physical port.

[0028] In the present application, since the first type of service flow only includes idle instances, PCS processing is not required for this type of service flow. At the same time, in order to ensure the normal bit multiplexing of PMA, a pseudo-random code stream can be generated and included in the bit multiplexing of PMA, thereby achieving energy saving while ensuring the normal operation of the service.

[0029] A fourth aspect of the present application provides an energy-saving method, which is applied to a receiving-end network device in a flexible Ethernet with a multi-stream architecture:

[0030] Receive target data from a transmitting network device at a physical port; demultiplex the target data to obtain a pseudo-random code stream and a service code stream, where the service code stream is obtained by performing PCS processing on a target type service stream by the transmitting network device, and the target type service stream is a service stream including non-idle instances; discard the demultiplexed pseudo-random code stream, and perform reverse PCS processing on the service code stream.

[0031] In the present application, after demultiplexing the target data, the receiving end network device directly discards the pseudo-random code stream and does not perform subsequent reverse PCS processing, thereby achieving energy saving.

[0032] A fifth aspect of the present application provides a network device, used as a sending end network device, including:

[0033] An acquisition unit, used to acquire multiple instances, wherein the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow;

[0034] A processing unit, distributing the multiple instances to multiple service flows after interleaving, wherein the multiple service flows include first-type service flows and second-type service flows, wherein the first-type service flows are composed of only idle instances, and the second-type service flows include non-idle instances;

[0035] The processing unit is further used to turn off the physical coding sublayer PCS processing of the first type of service flow, and perform PCS processing on the second type of service flow to obtain a service code stream;

[0036] The processing unit is also used to generate a pseudo-random code stream;

[0037] The processing unit is further used to perform bit multiplexing of the physical medium attachment sublayer PMA on the service code stream and the pseudo-random code stream to obtain target data;

[0038] The sending unit is used to send target data at the physical port.

[0039] In one possible implementation,

[0040] A processing unit, specifically used to interleave multiple instances, wherein the interleaving method is to select a code block set of one instance from the multiple instances for interleaving each time, the code block set includes S code blocks, and the code block sets of two non-idle instances are separated by K-1 code block sets of idle instances, where K is the number of multiple service flows;

[0041] The processing unit is specifically used to distribute each code block set in the multiple interleaved instances to multiple service flows one by one in a staggered manner.

[0042] In one possible implementation, S is 1 or 4.

[0043] In a possible implementation, the PCS processing includes transcoding, scrambling, FEC encoding, and alignment marker insertion.

[0044] In a possible implementation, the pseudo-random code stream is a PRBS31 code stream, a PRBS9 code stream, a PRBS21 code stream, a PRBS23 code stream, or a PRBS7 code stream.

[0045] In one possible implementation, the interface rate of the transmitting network device is 800G, including two service flows.

[0046] In one possible implementation, M is 4, and a single instance carries 100G of customer services.

[0047] A sixth aspect of the present application provides a network device, used as a sending end network device, including:

[0048] An acquisition unit, used to acquire multiple instances, wherein the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow;

[0049] A processing unit, configured to distribute the multiple instances to multiple service flows after interleaving, wherein the multiple service flows include first-type service flows and second-type service flows, wherein the first-type service flows are composed of only idle instances, and the second-type service flows include non-idle instances;

[0050] The processing unit is further used to turn off PCS processing, PMA processing and PMD processing for the first type of service flow;

[0051] The processing unit is further used to perform PCS processing on the second type of service flow to obtain a service code stream;

[0052] The processing unit is further used to perform PMA bit multiplexing on the service code stream. The rule of bit multiplexing is to multiplex the data of multiple virtual channels of the same service code stream onto one physical port to obtain target data.

[0053] The sending unit is used to send target data at the physical port.

[0054] In one possible implementation,

[0055] A processing unit, specifically used to interleave multiple instances, wherein the interleaving method is to select a code block set of one instance from the multiple instances for interleaving each time, the code block set includes S code blocks, and the code block sets of two non-idle instances are separated by K-1 code block sets of idle instances, where K is the number of multiple service flows;

[0056] The processing unit is specifically used to distribute each code block set in the multiple interleaved instances to multiple service flows one by one in a staggered manner.

[0057] In one possible implementation, S is 1 or 4.

[0058] In a possible implementation, the PCS processing includes transcoding, scrambling, FEC encoding, and alignment marker insertion.

[0059] In one possible implementation, the interface rate of the transmitting network device is 800G, including two service flows.

[0060] In one possible implementation, M is 4, and a single instance carries 100G of customer services.

[0061] A seventh aspect of the present application provides a network device, used as a sending end network device, including:

[0062] The acquisition unit is used to acquire multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single business flow.

[0063] The processing unit is further used to divide the multiple instances into multiple instance groups, the multiple instance groups include a first type group and a second type group, the first type group includes only idle instances, and the second type group includes non-idle instances.

[0064] The processing unit is further used to interleave instances in the same instance group to obtain a corresponding service flow.

[0065] The processing unit is also used to turn off PCS processing on the first type of business flow and perform PCS processing on the second type of business flow to obtain a business code stream. The first type of business flow is obtained by interleaving instances in the first type group, and the second type of business flow is obtained by interleaving instances in the second type group.

[0066] The processing unit is also used to generate a pseudo-random code stream, and perform PMA bit multiplexing on the service code stream and the pseudo-random code stream to obtain target data.

[0067] The sending unit is used to send target data at the physical port.

[0068] In an eighth aspect, the present application provides a network device, used as a receiving end network device, including:

[0069] A receiving unit, used for receiving target data from a sending end network device at a physical port;

[0070] A processing unit, used for demultiplexing the target data to obtain a pseudo-random code stream and a service code stream, wherein the service code stream is obtained by performing PCS processing on the target type service stream by the transmitting end network device, and the target type service stream is a service stream including a non-idle instance;

[0071] The processing unit is also used to discard the pseudo-random code stream obtained by demultiplexing and perform reverse PCS processing on the service code stream.

[0072] A ninth aspect of the present application provides a network device, used as a sending end network device, including:

[0073] A memory is used to store instructions; a processor is used to execute the instructions in the memory, so that the network device executes the methods in the first aspect, the second aspect and the third aspect mentioned above.

[0074] A tenth aspect of the present application provides a network device, used as a receiving end network device, including:

[0075] A memory is used to store instructions; a processor is used to execute the instructions in the memory, so that the network device executes the method in the aforementioned fourth aspect.

[0076] In an eleventh aspect, the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed on a computer, the computer executes the method in any of the aforementioned aspects.

[0077] A twelfth aspect of the present application provides a computer program product, which includes instructions. When the instructions are executed on a computer, the computer executes the method in any of the aforementioned aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1 This is a schematic diagram of the FlexE architecture;

[0079] Figure 2 Another schematic diagram of FlexE architecture;

[0080] Figure 3 A schematic diagram of the working mechanism of FlexE;

[0081] Figure 4 This is another schematic diagram of the working mechanism of FlexE;

[0082] Figure 5a This is another schematic diagram of the working mechanism of FlexE;

[0083] Figure 5b A schematic diagram of another working mechanism of FlexE;

[0084] Figure 6 A schematic diagram of an application scenario of this application;

[0085] Figure 7 A schematic diagram of a flow chart of the energy-saving method of the present application;

[0086] Figure 8 Another schematic diagram of the energy-saving method of the present application;

[0087] Fig. 9 Another schematic diagram of the energy-saving method of the present application;

[0088] Fig.10Another schematic diagram of the energy-saving method of the present application;

[0089] Fig.11 Another schematic diagram of the energy-saving method of the present application;

[0090] Fig.12 Another schematic diagram of the energy-saving method of the present application;

[0091] Fig.13a Another schematic diagram of the energy-saving method of the present application;

[0092] Fig.13b Another schematic diagram of the energy-saving method of the present application;

[0093] Fig.13c Another schematic diagram of the energy-saving method of the present application;

[0094] Fig.14 A structural diagram of a sending end network device of the present application;

[0095] Fig.15 Another structural diagram of the sending end network device of the present application;

[0096] Fig.16 Another structural diagram of the sending end network device of the present application;

[0097] Fig.17 A schematic diagram of the structure of the receiving end network device of the present application;

[0098] Fig.18 This is another structural diagram of a sending end network device or a receiving end network device of the present application. DETAILED DESCRIPTION

[0099] The following describes the embodiments of the present application in conjunction with the accompanying drawings. Obviously, the described embodiments are only embodiments of a part of the present application, rather than all embodiments. It is known to those skilled in the art that with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0100] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0101] With the diversification of services and application scenarios, network development has put forward higher requirements for the bandwidth of the bearer network. At the same time, users also hope to carry various services through a unified network, including home broadband services, dedicated line access services, mobile bearer services, etc. These requirements have put forward higher requirements for network interfaces. The current standard Ethernet interface has the following problems when used as a network interface: 1. It does not support more flexible bandwidth granularity: With the diversification of services and application scenarios, users hope that the Ethernet interface can provide more flexible bandwidth granularity without being restricted by the 10-25-40-50-100-200-400G ladder-type rate system established by the standard. 2. Mutual dependence on the capabilities of optical transmission equipment: The Ethernet interface capabilities of IP equipment are not synchronized with the capabilities of optical transmission equipment. For example, optical transmission equipment does not have a 25 / 50G interface, but when the two are networked and interconnected, the link rate of the optical transmission network needs to be strictly matched with the Ethernet rate of the IP device. 3. Does not support enhanced QoS capabilities for multi-service bearer: The standard Ethernet interface is based on QoS message priority scheduling, which may cause long packets to block short packets, resulting in longer short packet delays and mutual impact between services.

[0102] Therefore, in the Flex Ethernet Implementation Agreement technical recommendations released by OIF, the concept of flexible Ethernet (FlexE) was proposed, which supports sub-rate, channelization, inverse multiplexing and other functions for Ethernet services. Figure 1FlexE technology decouples the MAC and PHY layers by introducing the FlexE Shim layer, thereby achieving flexible rate matching. Among them, the MAC sublayer is a sublayer of the data link layer, connected to the logical link control sublayer. The physical layer can be divided into the physical coding sublayer (PCS), the physical medium attachment (PMA) sublayer and the PMD sublayer. The functions of each of the above layers are implemented by the corresponding chips or modules. In the process of sending signals, PCS is used to encode, scramble, insert overhead (OH) and insert alignment markers (AM) on the data; in the process of receiving signals, PCS will perform the inverse process of the above steps. Sending and receiving signals can be implemented by different functional modules of PCS. The main functions of the PMA sublayer are link monitoring, carrier monitoring, encoding and decoding, transmission clock synthesis and reception clock recovery. The main functions of the PMD sublayer are scrambling / descrambling, encoding and decoding of data streams, and DC recovery and adaptive equalization of received signals.

[0103] See also Figure 2, the FlexE general architecture includes FlexE Client, FlexE Shim and FlexE Group, where FlexE Client corresponds to various user interfaces observed externally in the network, which is consistent with the traditional service interfaces in the existing IP / Ethernet network. Each FlexE Client can be flexibly configured according to bandwidth requirements, supports Ethernet MAC data streams of various rates, and transmits the data stream to the FlexE Shim layer through 64B / 66B encoding; FlexE Shim is a logical layer inserted between the MAC layer and the PHY layer, and implements the core architecture of FlexE technology through the Slot distribution mechanism based on the time slot allocator Calendar; FlexE Group is essentially various Ethernet PHY layers, and the bandwidth of PHY is pooled into 5G granular resources by default. The MAC rate provided by FlexE can be greater than the rate of a single PHY (achieved by binding) or less than the rate of a single PHY (achieved by sub-rate and channelization). For example, for the binding scenario of Ethernet services, it can support the transmission of 200G Ethernet services (MAC code streams) using two existing 100GE PMDs. For the sub-rate application scenario of Ethernet services, it can support the transmission of 50G Ethernet services using one existing 100GE PMD. There is also a channelization scenario for Ethernet services, which can support several logical ports sharing one or more physical interfaces, and can support the transmission of one 150G Ethernet service and two 25G Ethernet services using two existing 100GE PMDs.

[0104] FlexE draws on SDH / OTN technology to build a fixed frame format for physical interface transmission and perform time division multiplexing (TDM) time slot division. Unlike SDH / OTN, the current FlexE TDM time slot division granularity is 66B, and the time slots are interleaved according to 66B, which can just correspond to carrying a 64 / 66B coding block. Figure 3For 100G PHY interface, the data code block stream consists of 64B / 66B code blocks with a period of 20, corresponding to 20 time slots. The bandwidth of each time slot is about 5G, which is called slot. The data on each PHY of FlexE is aligned by periodically inserting FlexE overhead code blocks. Specifically, a 66B overhead code block FlexE overhead is inserted every 1023x20 66B payload data code blocks. FlexE frames are divided into basic frames and multiframes. A single frame contains 8 rows × 1 column of 66B overhead code blocks FlexE overhead and 8 rows × (1023 × 20) columns of 66B payload code blocks. 32 single frames constitute a multiframe. In the frame structure of the FlexE overhead code block FlexE overhead, there is currently some space as a reserved field. In addition, 5 66B code blocks are provided as management channels for transmitting information other than data payload between two FlexE devices.

[0105] See also Figure 4 , Figure 4 The diagram shows the principle of mapping FlexE client data streams into FlexE Group. Calendar shows the corresponding relationship between slots in FlexE Group and FlexE clients. Sub-calendar shows the corresponding relationship between slots in a 100G in FlexE Group and FlexE clients. For 10G FlexE Client, 2 slots can be allocated to carry it; for 25G FlexE Client, 25G can be allocated to carry it. The slots of the same FlexE Client can be distributed in different 100G PMDs for transmission. Please refer to Figure 5a , Figure 5a The principle of demapping the FlexE client data stream from the FlexE Group is shown. According to the Calendar configuration, the FlexE client recovers the data stream from the FlexE Group.

[0106] In the 200G / 400G era, in order to maximize the reuse of 100G FlexE design and evolve towards the future, FlexE first introduced the instance architecture, dividing a single port into multiple FlexE instances. For example, 400G FlexE is composed of 4 100G instances. The rate, frame format, and overhead of each 100G instance are all the same. Figure 5bTaking 400GFlexE as an example, a single target frame encapsulates and processes a single 400G FlexE instance, mainly including frame encapsulation of each instance, inserting two 66B adaptation code blocks PADs at intervals of 163830 code blocks for each instance, and then interleaving all four instances corresponding to 400G FlexE, with the interleaving granularity being a single 66B code block.

[0107] In an optional implementation, 800G FlexE has a similar architecture to the above 400G FlexE, except that a single green box includes the encapsulation of 8 instance frames, which are then interleaved to the underlying part of 800G PHY. The instance interleaving granularity may change from a single 64B / 66B in the low-speed era to a 4×66B granularity equivalent to 256B / 257B. Since the 800G Ethernet architecture is a dual-stream architecture, in 800GFlexE, the instance may be distributed to two service flows.

[0108] The present application provides an energy-saving method for realizing energy saving in a flexible Ethernet with a multi-stream architecture by shutting down relevant processing of a service flow without affecting the service.

[0109] The energy-saving method of this application can be applied to network devices in scenarios such as B5G mobile bearer, ToB dedicated line, DCI interconnection, cloud dedicated line, computing network, East-West computing, etc. The network device supports FlexE technology with multi-stream architecture, and the multi-stream architecture includes but is not limited to 800G / 1.6T Ethernet architecture. Figure 6 , in a specific application scenario, including network device 1, network device 2 and several user devices, network device 1 can be connected to the user device through other network devices, or directly connected to the user device. Network device 2 can be connected to the user device through other network devices, or directly connected to the user device. Network device 1 includes FlexE interface 1, and network device 2 includes FlexE interface 2. FlexE interface 1 is adjacent to FlexE interface 2. Each FlexE interface includes a sending port and a receiving port. The difference from the traditional Ethernet interface is that a FlexE interface can carry multiple clients, and the FlexE interface as a logical interface can be composed of multiple physical interfaces. The sending end network device in this application is, for example, network device 1, and the receiving end network device is, for example, network device 2. The above-mentioned network devices include but are not limited to routers and switches.

[0110] See also Figure 7 , the following is an introduction to a process of the energy-saving method in this application:

[0111] 701. Acquire multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow;

[0112] This embodiment is introduced by taking the application in 800G Ethernet architecture as an example, wherein the interface rate of network device 1 and network device 2 is 800G, including two service flows, the maximum number of instances carried by each service flow is 4, and a single instance carries 100G customer services. Of course, the above is only an example and should not be understood as a limitation to this application.

[0113] The network device 1 receives the customer data from the user device and carries the customer data to the instance. After completing the configuration of the instance, the instance on the network device 1 can be divided into N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow.

[0114] For example, among the total 8 instances in the 800G Ethernet architecture, instance0, instance1, instance2, and instance3 are idle instances, and instance4, instance5, instance6, and instance7 are non-idle instances.

[0115] 702. Interweave the multiple instances and distribute them to the multiple service flows, where the multiple service flows include a first type service flow and a second type service flow, where the first type service flow consists of only idle instances, and the second type service flow includes non-idle instances;

[0116] See also Figure 8 , the network device 1 interleaves the above multiple instances, and the interleaving method is to select a code block set of one instance from the multiple instances for interleaving each time, and the code block set includes S 64 / 66B code blocks, and the code block sets of two non-idle instances need to be separated by K-1 code block sets of idle instances, where K is the number of all service flows, which is 2 in this embodiment. In a possible implementation, the above S can be 1 or 4.

[0117] Exemplarily, a possible order after interleaving is the code block set of instance0, the code block set of instance4, the code block set of instance1, the code block set of instance5, the code block set of instance2, the code block set of instance6, the code block set of instance3, the code block set of instance7, and so on.

[0118] After the interleaving is completed, the network device 1 distributes each code block set in the interleaved multiple instances to multiple service flows one by one. Figure 8 , exemplarily, network device 1 distributes a code block set of instance0 to service flow 0, distributes a code block set of instance4 to service flow 1, distributes a code block set of instance1 to service flow 0, distributes a code block set of instance5 to service flow 1, distributes a code block set of instance2 to service flow 0, distributes a code block set of instance6 to service flow 1, distributes a code block set of instance3 to service flow 0, distributes a code block set of instance7 to service flow 1, and so on. It is not difficult to see that based on the above interleaving method, it can ensure that non-idle instances are distributed to the same service flow, thereby ensuring that a service flow including only idle instances can be distributed.

[0119] It should be noted that the above interleaving method is only an example. In actual implementation, other interleaving methods may be adopted. It is only necessary to ensure that the above-mentioned first type of service flow and second type of service flow can be distributed after interleaving. Specific examples are not given here. Of course, the second type of service flow may include only non-idle instances, or may include both non-idle instances and idle instances.

[0120] 703. Disable the physical coding sublayer PCS processing of the first type of service flow, and perform PCS processing on the second type of service flow to obtain a service code stream;

[0121] See also Fig. 9 After completing the above processing, network device 1 sends service flow 0 and service flow 1 to the PCS sublayer. The PCS sublayer includes a transcoding module, a scramble module, an alignment insertion module, a pre-FEC distribution module, an FEC En-code module, and a distribution and interleave module. In the traditional solution, the PCS sublayer will perform PCS processing such as transcoding, scrambling, FEC encoding, and alignment identifier insertion on the service flow. In this embodiment, since all instances distributed to service flow 0 are idle instances, there is no need to perform PCS processing on service flow 0 in the PCS sublayer, thereby achieving energy saving. Since non-idle instances are distributed to service flow 1, service flow 1 performs PCS processing such as transcoding, scrambling, FEC encoding, and alignment identifier insertion in the PCS sublayer, thereby obtaining a service code stream, and sending the service code stream to the PMA sublayer for subsequent bit multiplexing in the PMA sublayer and multiplexing to the physical lane.

[0122] 704. Generate a pseudo-random code stream;

[0123] The distribution and interleave module of the PCS sublayer on the service flow 0 side generates a pseudo-random code stream and sends the pseudo-random code stream to the PMA sublayer for subsequent bit multiplexing at the PMA sublayer and multiplexing to the physical lane. The pseudo-random code stream may be, for example, a PRBS31 code stream.

[0124] 705. Perform bit multiplexing of the service code stream and the pseudo-random code stream at the PMA sublayer to obtain target data;

[0125] See also Fig.10 Specifically, the distribution and interleave module of the PCS sublayer will send the code stream from 16 virtual channels (VL) to the PMA sublayer, where the virtual channels numbered 0 to 15 correspond to the aforementioned pseudo-random code stream, and the virtual channels numbered 16 to 31 correspond to the aforementioned service code stream.

[0126] At the PMA sublayer, the network device 1 multiplexes the data of the two VLs of the pseudo-random code stream and the data of the two VLs of the service code stream onto one physical lane. In an example, the multiplexing method can be to multiplex the data of VL0, VL1, VL16, and VL17 into one physical lane; multiplex the data of VL2, VL3, VL18, and VL19 into one physical lane; multiplex the data of VL4, VL5, VL20, and VL21 into one physical lane; multiplex the data of VL6, VL7, VL22, and VL23 into one physical lane; multiplex the data of VL8, VL9, VL24, and VL25 into one physical lane; multiplex the data of VL10, VL11, VL26, and VL27 into one physical lane; multiplex the data of VL12, VL13, VL28, and VL29 into one physical lane; and multiplex the data of VL14, VL15, VL130, and VL31 into one physical lane.

[0127] 706. Send target data at the physical port.

[0128] Afterwards, network device 1 sends the corresponding data to network device 2 from 8 physical lanes.

[0129] Correspondingly, after receiving data from the eight physical lanes, network device 2 demultiplexes the data to restore the service code stream and pseudo-random code stream. For the pseudo-random code stream, network device 2 will directly discard it without subsequent reverse PCS processing; for the service code stream, network device 2 performs reverse PCS processing and a series of subsequent operations. For details, please refer to the description in the existing protocol, which will not be repeated here.

[0130] In this application, when the number of idle instances is greater than or equal to the maximum number of instances carried by a single service flow, the idle instances can be distributed to the same service flow through a specific interleaving method. For such service flows, no PCS processing is required. At the same time, in order to ensure the normal bit multiplexing of PMA, a pseudo-random code stream can be generated and involved in the bit multiplexing of PMA, thereby achieving energy saving while ensuring the normal operation of the service.

[0131] See also Fig.11 , another process of the energy-saving method in this application is introduced below:

[0132] 1101. Acquire multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow;

[0133] This step is similar to the aforementioned step 701 and will not be described in detail again.

[0134] 1102. Interweave the multiple instances and distribute them to the multiple service flows, where the multiple service flows include a first type service flow and a second type service flow, where the first type service flow consists of only idle instances, and the second type service flow includes non-idle instances;

[0135] This step is similar to the aforementioned step 702, and will not be described in detail again.

[0136] 1103. Disable PCS processing, PMA processing, and PMD processing for the first type of service flow;

[0137] See also Fig.12 , network device 1 sends service flow 0 and service flow 1 to the PCS sublayer. Since all instances distributed to service flow 0 are idle instances, there is no need to perform PCS processing on service flow 0 at the PCS sublayer, and no subsequent PMA processing and PMD processing will be performed.

[0138] 1104. Perform PCS processing on the second type of service flow to obtain a service code stream;

[0139] For service stream 1, the PCS sublayer performs PCS processing on it to obtain a service code stream.

[0140] 1105. Perform PMA bit multiplexing on the service code stream. The rule of bit multiplexing is to multiplex the data of N virtual channels of the service code stream into one physical channel to obtain target data.

[0141] Network device 1 sends the service code stream to the PMA sublayer, where the service code stream is bit-multiplexed and multiplexed onto the physical lane. For details, see Fig.13a , the service code stream is sent to the PMA sublayer through 16 VLs. In the PMA sublayer, network device 1 multiplexes the data of the 4 VLs of the service code stream into one physical lane. In an example, the multiplexing method can be to multiplex the data of VL16, VL17, VL18, and VL19 into one physical lane; the data of VL20, VL21, VL22, and VL23 into one physical lane; the data of VL24, VL25, VL26, and VL27 into one physical lane; and the data of VL28, VL29, VL30, and VL31 into one physical lane.

[0142] 1106. Send target data at the physical port.

[0143] Afterwards, network device 1 sends the corresponding data to network device 2 from 4 physical lanes.

[0144] Correspondingly, after network device 2 receives data from the four physical lanes, it demultiplexes the data to restore the service code stream, and performs reverse PCS processing and a series of subsequent operations on it. For details, please refer to the description in the existing protocol, which will not be repeated here.

[0145] In this application, when the number of idle instances is greater than or equal to the maximum number of instances carried by a single service flow, the idle instances can be distributed to the same service flow through a specific interleaving method. For such a service flow, no PCS processing, PMA processing, and PMD processing are required. At the same time, in order to ensure the normal bit multiplexing of PMA, the data of multiple VLs of the same service code stream can be multiplexed to one physical lane, thereby achieving energy saving while ensuring the normal operation of the service.

[0146] See also Fig.13b , another process of the energy-saving method in this application is introduced below:

[0147] A01. Obtain multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow;

[0148] This step is similar to the aforementioned step 701 and will not be described in detail again.

[0149] A02. Divide the multiple instances into multiple instance groups, where the multiple instance groups include a first type group and a second type group, where the first type group includes only idle instances, and the second type group includes non-idle instances;

[0150] See also Fig.13c , the FlexE shim layer consists of 8 100G FlexE instances, each of which has the same frame format and the same rate. Multiple FlexE clients (66B encoding) enter the FlexE shim, perform idle addition and deletion rate adaptation according to possible rate deviations, and then map clients and time slots according to the calendar, a table of correspondence between clients and time slots. Then, each interface instance is encapsulated into an instance frame according to the time slot carrying data and overhead (Overhead) it owns. An instance frame corresponds to a Sub-calendar structure in the figure. After encapsulation into a frame, multiple FlexE instances are divided into multiple groups, including first-type groups and second-type groups, where the first-type group only includes idle instances, and the second-type group includes non-idle instances. For example, 800G has a total of 8 instances, of which instance0, instance1, instance2, and instance3 are idle instances, and instance4, instance5, instance6, and instance7 are non-idle instances. The above 8 instances can be divided into two groups, each group includes half the number of instances of a single port. Specifically, instances 0 to 3 are group 1, that is, the first type group; instances 4 to 7 are group 2, that is, the second type group. Of course, the above division method is only an example. In actual implementation, the second type group can include only non-idle instances, or both non-idle instances and idle instances.

[0151] A03. Interweave the instances in the same instance group to obtain a corresponding service flow;

[0152] Interleave the instances in Group 1 into one stream, recorded as Stream 1; interleave the instances in Group 2 into one stream, recorded as Stream 2. The interleaving granularity is P×4×66B code blocks, P>=1, and P is a positive integer. Rate adaptation PADs are inserted into the two interleaved single-channel 66B code block streams, respectively, where the PAD insertion granularity is Y×4×66B code blocks, every T 66B code blocks, where Y and T are both positive integers, both>=1. Finally, the two independent 66B code block streams of the FlexE shim layer are mapped to the two 400G flows of the Ethernet PHY bottom layer.

[0153] A04. Turn off PCS processing for the first type of service flow, and perform PCS processing on the second type of service flow to obtain a service code stream, where the first type of service flow is obtained by interleaving instances in the first type group, and the second type of service flow is obtained by interleaving instances in the second type group;

[0154] The above-mentioned flow 1 is the first type of service flow, and flow 2 is the second type of service flow. This step is similar to the above-mentioned step 703, and will not be repeated here.

[0155] A05, generate pseudo-random code stream;

[0156] This step is similar to the above-mentioned step 704 and will not be repeated here.

[0157] A06, performing PMA bit multiplexing on the service code stream and the pseudo-random code stream to obtain target data;

[0158] This step is similar to the above-mentioned step 705 and will not be repeated here.

[0159] A07. Send the target data at the physical port.

[0160] This step is similar to the above-mentioned step 706 and will not be repeated here.

[0161] In the present application, a plurality of instances are divided into a first type group and a second type group, and the instances in each group are interleaved separately to obtain a first type service flow and a second type service flow. Since the first type service flow only includes idle instances, PCS processing is not required for such service flow. At the same time, in order to ensure the normal bit multiplexing of PMA, a pseudo-random code stream can be generated and involved in the bit multiplexing of PMA, thereby achieving energy saving while ensuring the normal operation of the service.

[0162] The energy saving method in the present application is described above. The sending end network device and the receiving end network device in the present application are introduced below:

[0163] See also Fig.14 The sending end network device 1400 in the present application includes an acquisition unit 1401, a processing unit 1402, and a sending unit 1403.

[0164] An acquiring unit 1401 is configured to acquire multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is a maximum number of instances carried by a single service flow;

[0165] The processing unit 1402 distributes the multiple instances to multiple service flows after interleaving, where the multiple service flows include a first type of service flow and a second type of service flow, where the first type of service flow consists of only idle instances, and the second type of service flow includes non-idle instances;

[0166] The processing unit 1402 is further configured to disable the physical coding sublayer PCS processing of the first type of service flow, and perform PCS processing on the second type of service flow to obtain a service code stream;

[0167] The processing unit 1402 is further configured to generate a pseudo-random code stream;

[0168] The processing unit 1402 is further configured to perform bit multiplexing of the physical medium attachment sublayer PMA on the service code stream and the pseudo random code stream to obtain target data;

[0169] The sending unit 1403 is used to send target data at the physical port.

[0170] In one possible implementation,

[0171] The processing unit 1402 is specifically configured to interleave the multiple instances, wherein the interleaving manner is to select a code block set of one instance from the multiple instances for interleaving each time, the code block set includes S code blocks, and the code block sets of two non-idle instances are separated by K-1 code block sets of idle instances, where K is the number of the multiple service flows;

[0172] The processing unit 1402 is specifically configured to distribute each code block set in the multiple interleaved instances to the multiple service flows one by one in a staggered manner.

[0173] In one possible implementation, S is 1 or 4.

[0174] In a possible implementation, the PCS processing includes transcoding, scrambling, FEC encoding, and alignment marker insertion.

[0175] In a possible implementation, the pseudo-random code stream is a PRBS31 code stream, a PRBS9 code stream, a PRBS21 code stream, a PRBS23 code stream, or a PRBS7 code stream.

[0176] In one possible implementation, the interface rate of the transmitting network device is 800G, including two service flows.

[0177] In one possible implementation, M is 4, and a single instance carries 100G of customer services.

[0178] See also Fig.15 The sending end network device 1500 in the present application includes an acquisition unit 1501, a processing unit 1502, and a sending unit 1503.

[0179] An acquiring unit 1501 is used to acquire multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow;

[0180] The processing unit 1502 is configured to distribute the multiple instances to multiple service flows after interleaving, where the multiple service flows include a first type of service flow and a second type of service flow, where the first type of service flow consists of only idle instances, and the second type of service flow includes non-idle instances;

[0181] The processing unit 1502 is further configured to disable PCS processing, PMA processing, and PMD processing for the first type of service flow;

[0182] The processing unit 1502 is further configured to perform PCS processing on the second type of service flow to obtain a service code stream;

[0183] The processing unit 1502 is further used to perform PMA bit multiplexing on the service code stream. The rule of bit multiplexing is to multiplex the data of multiple virtual channels of the same service code stream onto one physical port to obtain target data.

[0184] The sending unit 1503 is used to send target data at the physical port.

[0185] In one possible implementation,

[0186] The processing unit 1502 is specifically configured to interleave the multiple instances, wherein the interleaving manner is to select a code block set of one instance from the multiple instances for interleaving each time, the code block set includes S code blocks, and the code block sets of two non-idle instances are separated by K-1 code block sets of idle instances, where K is the number of the multiple service flows;

[0187] The processing unit 1502 is specifically configured to distribute each code block set in the multiple interleaved instances to the multiple service flows one by one in a staggered manner.

[0188] In one possible implementation, S is 1 or 4.

[0189] In a possible implementation, the PCS processing includes transcoding, scrambling, FEC encoding, and alignment marker insertion.

[0190] In one possible implementation, the interface rate of the transmitting network device is 800G, including two service flows.

[0191] In one possible implementation, M is 4, and a single instance carries 100G of customer services.

[0192] See also Fig.16The sending end network device 1600 in the present application includes an acquisition unit 1601, a processing unit 1602, and a sending unit 1603.

[0193] The acquisition unit 1601 is used to acquire multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow.

[0194] The processing unit 1602 is configured to divide the multiple instances into multiple instance groups, where the multiple instance groups include a first type group and a second type group, where the first type group includes only idle instances, and the second type group includes non-idle instances.

[0195] The processing unit 1602 is further configured to interleave the instances in the same instance group to obtain a corresponding service flow.

[0196] The processing unit 1602 is also used to turn off PCS processing on the first type of business flow, and perform PCS processing on the second type of business flow to obtain a business code stream, the first type of business flow is obtained by interleaving instances in the first type group, and the second type of business flow is obtained by interleaving instances in the second type group.

[0197] The processing unit 1602 is further configured to generate a pseudo-random code stream, and perform PMA bit multiplexing on the service code stream and the pseudo-random code stream to obtain target data.

[0198] The sending unit 1603 is used to send target data at the physical port.

[0199] See also Fig.17 The receiving end network device 1700 in the present application includes a receiving unit 1701 and a processing unit 1702.

[0200] The receiving unit 1701 is used to receive target data from a sending end network device at a physical port;

[0201] The processing unit 1702 is used to demultiplex the target data to obtain a pseudo-random code stream and a service code stream, where the service code stream is obtained by the transmitting end network device performing PCS processing on the target type service stream, and the target type service stream is a service stream including a non-idle instance;

[0202] The processing unit 1702 is further configured to discard the pseudo-random code stream obtained by demultiplexing and perform reverse PCS processing on the service code stream.

[0203] Fig.181 is a schematic diagram of the structure of a network device provided by the present application, which may be a sending end network device or a receiving end network device and is used to implement the methods in the aforementioned embodiments. The network device 1800 may include one or more central processing units (CPU) 1801 and a memory 1805, in which one or more application programs or data are stored.

[0204] The memory 1805 may be a volatile storage or a persistent storage. The program stored in the memory 1805 may include one or more modules, each of which may include a series of instruction operations on the server. Furthermore, the central processor 1801 may be configured to communicate with the memory 1805 and execute a series of instruction operations in the memory 1805 on the network device 1800.

[0205] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0206] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

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

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

[0209] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. An energy saving method, applied to a transmitting end network device in a flexible Ethernet with a multi-stream architecture, characterized in that: include: Acquire multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow; Interweaving the multiple instances and distributing them to multiple service flows, the multiple service flows include a first type of service flow and a second type of service flow, the first type of service flow consists only of the idle instances, and the second type of service flow includes the non-idle instances; Turn off the physical coding sublayer PCS processing of the first type of service flow, and perform PCS processing on the second type of service flow to obtain a service code stream; Generate a pseudo-random code stream; The business code stream and the pseudo-random code stream are bit-multiplexed by the physical medium attachment sublayer PMA to obtain target data; The target data is sent at the physical port.

2. The method according to claim 1, characterized in that The interleaving of the multiple instances and distributing them to the multiple service flows comprises: Interleaving the multiple instances, wherein the interleaving manner is to select a code block set of one of the multiple instances for interleaving each time, the code block set includes S code blocks, and the code block sets of two non-idle instances are separated by K-1 code block sets of the idle instances, where K is the number of the multiple service flows; Each of the code block sets in the multiple interleaved instances are staggered and distributed to the multiple service flows one by one.

3. The method according to claim 2, characterized in that The S is 1 or 4.

4. The method according to any one of claims 1 to 3, characterized in that The PCS processing includes transcoding, scrambling, forward error correction (FEC) encoding, and alignment marker insertion.

5. The method according to claim 4, characterized in that The pseudo-random code stream is a PRBS31 code stream, a PRBS9 code stream, a PRBS21 code stream, a PRBS23 code stream, and a PRBS7 code stream.

6. The method according to claim 5, characterized in that The interface rate of the sending network device is 800G, including two service flows.

7. The method according to claim 6, characterized in that The M is 4, and a single instance carries 100G of customer services.

8. An energy saving method, applied to a transmitting end network device in a flexible Ethernet with a multi-stream architecture, characterized in that: include: Acquire multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow; Interweaving the multiple instances and distributing them to multiple service flows, the multiple service flows include a first type of service flow and a second type of service flow, the first type of service flow consists only of the idle instances, and the second type of service flow includes the non-idle instances; Turn off the physical coding sublayer PCS processing, the physical medium attachment sublayer PMA processing and the physical medium dependent sublayer PMD processing for the first type of service flow; Performing PCS processing on the second type of service flow to obtain a service code stream; The service code stream is bit-multiplexed by the physical medium attachment sublayer PMA, wherein the rule of the bit-multiplexing is to multiplex the data of multiple virtual channels of the same service code stream onto one physical port to obtain target data; The target data is sent at the physical port.

9. The method according to claim 8, characterized in that The interleaving of the multiple instances and distributing them to the multiple service flows comprises: Interleaving the multiple instances, wherein the interleaving manner is to select a code block set of one of the multiple instances for interleaving each time, the code block set includes S code blocks, and the code block sets of two non-idle instances are separated by K-1 code block sets of the idle instances, where K is the number of the multiple service flows; Each of the code block sets in the multiple interleaved instances are staggered and distributed to the multiple service flows one by one.

10. The method according to claim 9, characterized in that The S is 1 or 4.

11. The method according to any one of claims 8 to 10, characterized in that The PCS processing includes transcoding, scrambling, forward error correction (FEC) encoding, and alignment marker insertion.

12. According to the method of claim 11, the interface rate of the sending network device is 800G, including two business flows.

13. The method according to claim 12, characterized in that The M is 4, and a single instance carries 100G of customer services.

14. An energy saving method, applied to a transmitting end network device in a flexible Ethernet with a multi-stream architecture, characterized in that: include: Acquire multiple instances, where the multiple instances include N idle instances and non-idle instances, where N is greater than or equal to M, and M is the maximum number of instances carried by a single service flow; Dividing the multiple instances into multiple instance groups, the multiple instance groups include a first type group and a second type group, the first type group includes only the idle instances, and the second type group includes the non-idle instances; Interweaving the instances in the same instance group to obtain a corresponding service flow; Turn off the physical coding sublayer PCS processing of the first type of service flow, and perform PCS processing on the second type of service flow to obtain a service code stream, where the first type of service flow is obtained by interleaving the instances in the first type group, and the second type of service flow is obtained by interleaving the instances in the second type group; Generate a pseudo-random code stream; The business code stream and the pseudo-random code stream are bit-multiplexed by the physical medium attachment sublayer PMA to obtain target data; The target data is sent at the physical port.

15. An energy saving method, applied to a receiving end network device in a flexible Ethernet with a multi-stream architecture, characterized in that: include: receiving target data from a sending end network device at a physical port; Demultiplexing the target data to obtain a pseudo-random code stream and a service code stream, wherein the service code stream is obtained by the transmitting end network device performing PCS processing on the target type service stream, and the target type service stream is a service stream including a non-idle instance; The pseudo-random code stream is discarded, and the service code stream is subjected to reverse PCS processing.

16. A network device, used as a sending end network device, characterized in that: include: A memory for storing instructions; A processor, configured to execute instructions in the memory so that the network device executes the method according to any one of claims 1 to 14.

17. A network device, used as a receiving end network device, characterized in that: include: A memory for storing instructions; A processor, configured to execute instructions in the memory so that the network device executes the method of claim 15.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 15.

19. A computer program product, characterized in that The computer program product comprises instructions, which, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 15 .

Images