CN107438028B - Method and equipment for processing customer service - Google Patents

Abstract

Embodiments of the present invention disclose a method and device for processing client services, wherein the method for processing client services includes: receiving client services, and mapping the client services to M number of client services according to a first forwarding label carried in the client services In the time slot, the first forwarding label indicates the first forwarding destination address; the client service is sent to the target physical channel through the M time slots, and the target physical channel and the first forwarding destination address have the same value. Corresponding relationship; wherein, M is a positive integer greater than or equal to 1. Through the technical scheme of the present invention, multiple service exchanges are realized in the same switching plane of the flexible Ethernet.

Description

A method and device for customer business processing

technical field

The present invention relates to the field of communications, and in particular, to a method and device for processing customer services.

Background technique

Currently, the Optical Internetworking Forum (OIF) is discussing the extension of traditional Ethernet technology to support application scenarios such as sub-rate, channelization, and inverse multiplexing for Ethernet services. It is called flexible Ethernet (Flexible Ethernet, FlexE) technology. For example, for the application scenario of the sub-rate of the Ethernet service, it can support the transmission of the 250G Ethernet service by using the existing 100GE physical medium dependent sublayer (Physical Medium Dependent, PMD) of three channels. For the application scenario of inverse multiplexing of Ethernet services, it can support the transmission of 200G Ethernet services using two existing 100GE PMDs. For the application scenario of channelization of Ethernet services, it can support multiplexing multiple low-rate Ethernet services into high-rate flexible Ethernet. A large number of Ethernets are used as service bearer networks in access networks and metropolitan area networks. Since FlexE technology supports application scenarios such as sub-rate, channelization, and inverse multiplexing of Ethernet services, the application flexibility of Ethernet interfaces is enhanced. .

At present, FlexE technology only supports point-to-point applications as an interface technology, but it has attracted the attention of the industry as a potential network transmission technology. To develop FlexE into a network transmission technology, there must be switching requirements for FlexE node devices.

In the prior art, the flexible Ethernet adopts a solution of unified switching of cells (cells), that is, a Cell switching network is used for unified switching for different types of services. For example, for a time division multiplexing (Time Division Multiplexing, TDM) service, it is adapted to the Cell switching network, and the switching is completed according to the time slot configuration information of the FlexE service layer time slot (Calendar). For the Ethernet data service, the Ethernet frame is recovered, and then it is adapted to the Cell switching network, and the switching is completed based on the Media Access Control (Media Access Control, MAC) address. In the cell unified switching solution, there are L1 layer and L2 layer processing, which is equivalent to designing two switching planes on the node device, which increases the design complexity, power consumption and cost of the device.

SUMMARY OF THE INVENTION

In view of this, the embodiments of the present invention provide a method and device for processing client services, which can solve the problems of design complexity, power consumption and cost of service switching on node devices.

In a first aspect, an embodiment of the present invention provides a method for processing client services, including: receiving client services, mapping the client services to M time slots according to a first forwarding label carried in the client services, and The first forwarding label indicates a first forwarding destination address; the client service is sent to a target physical channel through the M time slots, and the target physical channel has a corresponding relationship with the first forwarding destination address; wherein, M is a positive integer greater than or equal to 1.

The customer service can include data service and TDM service. The customer service is mapped to M time slots through the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots. Multiple services are exchanged in the same switching plane of the flexible Ethernet.

In a possible implementation manner, the mapping of the client service into M timeslots according to the first forwarding label carried in the client service includes: the first forwarding label and the M timeslots The slots have a corresponding relationship, and the client traffic is mapped into the M time slots according to the first forwarding label.

By establishing the correspondence between the first forwarding label and the time slot, the customer service can be mapped to the corresponding time slot according to the first forwarding label, thereby realizing the exchange of multiple services in the same switching plane of the flexible Ethernet.

In a possible implementation manner, the sending the client service to the target physical channel through the M time slots includes: the M time slots and the target physical channel have a corresponding relationship.

In a possible implementation manner, the client service is encoded, and the client service forms a code block stream; the first forwarding label is added to the S code block of the client service, and the S code block is A codeblock type in the codeblock stream.

In a possible implementation manner, the first forwarding label is added to the L code block of the client service, and the L code block is obtained by deleting the idle code block of the client service, where the idle code block is located. A codeblock type in the codeblock stream described above.

In a possible implementation manner, the method further includes: adding the first forwarding label to the frame header positioning overhead of the client service.

In a possible implementation manner, a second forwarding label is added to the client service, and the second forwarding label indicates a second forwarding destination address of the client service.

In a first aspect, an embodiment of the present invention provides a method for processing client services, including: acquiring M timeslots of client services from a target physical channel, acquiring the client services from the M timeslots; the first forwarding label in the customer service, delete the first forwarding label and/or add a third forwarding label; wherein, the first forwarding label indicates a first forwarding destination address, and the target physical channel is associated with the first forwarding label. A forwarding destination address has a corresponding relationship; M is a positive integer greater than or equal to 1.

By acquiring the first forwarding label from the customer service, deleting the first forwarding label and/or adding the third forwarding label, the switching of multiple services in the same switching plane of the flexible Ethernet is realized.

In a possible implementation manner, the deleting the first forwarding label and/or adding the third forwarding label includes: the first forwarding label is an incoming label, and the third forwarding label is an outgoing label; according to The first forwarding label acquires a third forwarding label; wherein, the first forwarding label and the third forwarding label have a corresponding relationship.

In a possible implementation manner, the adding a third forwarding label includes: deleting an idle code block of the customer service, converting an S code block carrying the first forwarding label into an L code block, and adding a code carrying the first forwarding label. The S code block of the third forwarding label; the idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the encoding of the customer service.

In a possible implementation manner, the deleting the first forwarding label includes: deleting the first forwarding label, and restoring the code block carrying the first forwarding label to a normal code block; wherein the The normal code block includes any one of the S code block, the L code block, and the frame header positioning overhead, and the S code block and the L code block are respectively two kinds of code blocks in the code block stream formed by the encoding of the customer service. type.

In a third aspect, an embodiment of the present invention provides a device for processing client services, including: a receiving module, configured to receive client services; and a mapping module, configured to convert the client services according to a first forwarding label carried in the client services. The customer service is mapped into M time slots, and the first forwarding label indicates the first forwarding destination address; the sending module is configured to send the customer service to the target physical channel through the M time slots, and the target The physical channel has a corresponding relationship with the first forwarding destination address; wherein, M is a positive integer greater than or equal to 1.

The customer service can include data service and TDM service. The customer service is mapped to M time slots through the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots. Multiple services are exchanged in the same switching plane of the flexible Ethernet.

In a possible implementation manner, the mapping module is configured to: the first forwarding label has a corresponding relationship with the M timeslots, and map the client service to the M timeslots according to the first forwarding label in M time slots.

By establishing the correspondence between the first forwarding label and the time slot, the customer service can be mapped to the corresponding time slot according to the first forwarding label, thereby realizing the exchange of multiple services in the same switching plane of the flexible Ethernet.

In a possible implementation manner, the M time slots and the target physical channel have a corresponding relationship.

In a possible implementation manner, the device further includes: an encoding module, configured to encode the client service, and the client service forms a code block stream; a first adding module, configured to encode the client service in the The first forwarding label is added to an S code block, where the S code block is a code block type in the code block stream.

In a possible implementation manner, the first adding module is further configured to: add the first forwarding label to the L code block of the customer service, and the L code block deletes the The idle code block is obtained, and the idle code block is a type of code block in the code block stream.

In a possible implementation manner, the device includes a second adding module, configured to: add the first forwarding label to the frame header positioning overhead of the client service.

In a possible implementation manner, the device further includes a third adding module, configured to: add a second forwarding label to the customer service, where the second forwarding label indicates a second forwarding purpose of the customer service address.

In a fourth aspect, an embodiment of the present invention provides a device for processing client services, including: a client service acquisition module configured to acquire M time slots of the client service from a target physical channel, and obtain M time slots from the M time slots the customer service; a forwarding label acquisition module, used to obtain the first forwarding label in the customer service; a forwarding label addition and deletion module, used to delete the first forwarding label and/or add a third forwarding label; wherein, the The first forwarding label indicates a first forwarding destination address, and the target physical channel has a corresponding relationship with the first forwarding destination address; M is a positive integer greater than or equal to 1.

Obtaining the first forwarding label from the customer service, deleting the first forwarding label and/or adding the third forwarding label, realizes the exchange of multiple services in the same switching plane of the flexible Ethernet.

In a possible implementation manner, the forwarding label obtaining module is configured to: the first forwarding label is an incoming label, the third forwarding label is an outgoing label; and the third forwarding label is obtained according to the first forwarding label; The first forwarding label and the third forwarding label have a corresponding relationship.

In a possible implementation manner, the forwarding label addition and deletion module is configured to: delete the idle code block of the customer service, convert the S code block carrying the first forwarding label into an L code block, and increase the carrying The S code block of the third forwarding label; the idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the encoding of the customer service.

In a possible implementation manner, the forwarding label addition and deletion module is configured to: delete the first forwarding label, and restore the code block carrying the first forwarding label to a normal code block; wherein the normal code The block includes any one of the S code block, the L code block and the frame header positioning overhead, the S code block and the L code block are respectively two code block types in the code block stream formed by the encoding of the client service.

In a fifth aspect, an embodiment of the present invention provides a computer device, including: a processor, a memory, a bus, and a communication interface; the memory is used to store computer execution instructions, the processor and the memory are connected through a bus, and when the computer is running, the processor The computer-implemented instructions stored in the memory are executed to cause the computer to perform the method as described in the first aspect and any one of the possible implementations of the first aspect.

In a sixth aspect, an embodiment of the present invention provides a computer device, including: a processor, a memory, a bus, and a communication interface; the memory is used to store computer execution instructions, the processor and the memory are connected through a bus, and when the computer is running, the processor The computer-implemented instructions stored in the memory are executed to cause the computer to perform the method as described in the second aspect and any one of the possible implementations of the second aspect.

In a seventh aspect, an embodiment of the present invention provides a network system, including, as the third aspect or a device in any possible implementation manner of the third aspect, and as in the fourth aspect or any possible implementation of the fourth aspect device in the way.

Description of drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the accompanying drawings used in describing the background technology and the embodiments will be briefly introduced below.

1 is a schematic diagram of a layered structure of a flexible Ethernet according to an embodiment of the present invention;

2 is a data frame format of a flexible Ethernet provided by an embodiment of the present invention;

3 is a schematic structural diagram of a flexible Ethernet service processing provided by an embodiment of the present invention;

4 is a schematic structural diagram of a flexible Ethernet service processing provided by an embodiment of the present invention;

5 is a schematic diagram of a field format of an S code block provided by an embodiment of the present invention;

6 is a schematic diagram of the format of a label defined by MPLS according to an embodiment of the present invention;

7 is a schematic diagram of a field format of an L code block provided by an embodiment of the present invention;

8 is a schematic structural diagram of a FlexE overhead code block provided by an embodiment of the present invention;

9 is a network architecture diagram of a flexible Ethernet provided by an embodiment of the present invention;

10 is a schematic structural diagram of an edge node device according to an embodiment of the present invention;

11 is a schematic diagram of an overhead structure of an OTN frame provided by an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of a switching node device according to an embodiment of the present invention;

FIG. 13 is an exemplary flowchart of a method for processing customer services provided by an embodiment of the present invention;

FIG. 14 is an exemplary flowchart of a method for processing client services provided by an embodiment of the present invention;

15 is a schematic diagram of a logical structure of a device for processing client services provided by an embodiment of the present invention;

16 is a schematic diagram of a logical structure of a device for processing client services provided by an embodiment of the present invention;

FIG. 17 is a schematic structural diagram of a computer device according to an embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

In order to better understand the technical solutions of the embodiments of the present invention, a brief introduction to the layered structure of the flexible Ethernet is made first. FIG. 1 is a schematic diagram of a layered structure of a flexible Ethernet provided by an embodiment of the present invention. As shown in Figure 1, flexible Ethernet can include a FlexE client layer and a FlexE service layer. The FlexE client layer is mainly used to support the aggregation of client services, such as the media access control (Media Access Control, MAC) layer, the reconciliation sublayer (Reconciliation Sublayer, RS) and the 64B/66B codec in the FlexE SHIM layer. The FlexE client layer can include Ethernet interfaces with bandwidths of 10G, 25G, 40G, and N*50G. The FlexE service layer is mainly used to support the bearer of FlexE customer services, such as the functional layers other than 64B/66B encoding and decoding in the FlexE SHIM layer, the Physical Coding Sublayer (PCS), and Forward Error Correction (Forward Error Correction). Correction, FEC) layer, Physical Medium Attachment (Physical Medium Attachment, PMA), Physical Medium Dependent (Physical Medium Dependent, PMD). The FlexE service layer can be implemented by using N channels of 100GE physical layer devices (Physical Layer Device, PHY), and can also be implemented by N channels of 400GE PHYs.

The FlexE SHIM layer introduces the concept of a data frame and a time slot (Calendar). FIG. 2 is a data frame format of a flexible Ethernet provided by an embodiment of the present invention. As shown in Figure 2, the FlexE data frame is a data frame structure with 8 rows and (1+1023x20) columns, and is composed of 8x(1+1023x20) 66B code blocks. The FlexE data frame includes control code blocks, data code blocks, and may also include idle (IDLE) code blocks. The control code blocks may include overhead code blocks (O code blocks), start code blocks (S code blocks), label code blocks (L code blocks), and the like. In FIG. 2, the 8 code blocks in the first column are O code blocks, which are used to carry the overhead information of the FlexE data frame. Among the remaining control code blocks, the S code block and the L code block can be used to carry forwarding labels. The data code block is used to carry the data information of the customer service. The IDLE code block may be a code block inserted during rate adaptation of client services.

FIG. 3 is a schematic structural diagram of a flexible Ethernet service processing provided by an embodiment of the present invention. As shown in FIG. 3 , the service processing process may be a process of service multiplexing, which may be implemented in the sending end device of the flexible Ethernet. The specific process of service multiplexing can refer to the following description: after the network device receives multiple customer customer services, such as customer service a, customer service b... customer service z, it performs 64B/66B encoding on the received multi-channel customer service. A 66B code block stream is formed, and rate adaptation is performed on the code block stream of the client service by inserting or deleting idle (IDLE) code blocks. The code block stream of the client service is sent to the FlexE service layer time slot (Calendar) for exchange. Distribute the code block streams of multiple client services to the sub-time division channels (sub-Calendar) of N channels of PHY through the FlexE service layer time slot, and in the sub-Calendar of each channel of PHY according to a certain interval period (for example, 20x66B) The FlexE overhead is inserted to identify the frame structure of FlexE or the sequence of each PHY. The sub-Calendar of each PHY is scrambled, and then the sub-Calendar of each PHY is divided into multiple PCS channels, inserted into an Alignment Marker (AM) and distributed to the PMA.

FIG. 4 is a schematic structural diagram of a flexible Ethernet service processing provided by an embodiment of the present invention. As shown in FIG. 4 , the service processing process may be a process of service demultiplexing, which may be implemented in a receiving end device of the flexible Ethernet. The receiving end device and the sending end device of the flexible Ethernet may be different network devices, or may be the same network device. The process of service demultiplexing is opposite to the processing flow of the service multiplexing process shown in FIG. 4 , and the principle is similar, which will not be repeated here.

In the embodiment of the present invention, in the flexible Ethernet service processing process shown in FIG. 3 or FIG. 4 , by adding a forwarding label to the control code block in the code block flow of the customer service, and performing service exchange according to the added forwarding label, you can Realize the exchange of multiple services in the same switching plane of the flexible Ethernet.

A first forwarding label may be added to the control code block of the customer service, for example, the S code block, to indicate the first forwarding destination address of the customer service. The field format of the S code block is shown in FIG. 5 , and the S code block includes a synchronization header (10), a block type field (0x78), and a data field (D1-D7). The first forwarding label may be borne by the data fields (D1-D7) in the S code block.

The first forwarding label may adopt a label format defined in Multiprotocol Label Switching (Multiprotocol Label Switching, MPLS), as shown in FIG. 6 . The total length of the label defined by MPLS is 32 bits, which can be divided into the following fields:

Label: 20 bits in length, used to identify the forwarding relationship of the service. The forwarding relationship of the service may include the forwarding destination address of the service, and may also include the forwarding source address of the service. For example, the forwarding relationship of the service may also include the outgoing interface of the packet on a certain device, and may also include the incoming interface. Labels can include outgoing labels and incoming labels, which are used to identify the outgoing interface and incoming interface of a service on a device, respectively.

Exp: has a length of 3 bits and is used to identify the quality of service (Quality of Service, QoS) of the service. For example, 8 priorities can be identified, including service types corresponding to different services such as voice, video, and data.

TTL: 8 bits in length, used to prevent loops during service transmission.

The total length of a label is 32 bits, so one S-code block can carry at most one layer of labels, for example, the first forwarding label. In order to support multi-layer label nesting, it can be realized by deleting the idle (IDLE) code block in the code block stream of the customer service and adding a control code block. For example, the added control code block is called an L code block, and can also be a 66b code block. The field format of the L code block is shown in Figure 7. The format of the L code block is similar to that of the S code block, and the tags are also carried through D1 to D7. The difference is that the block type field is 0x79. The L code block may carry a forwarding label, such as a second forwarding label. The first forwarding label and the second forwarding label may be labels for different types of network devices, for example, the first forwarding label is directed to the network device of the access network, and the second forwarding label is directed to the network device of the transport network. By deleting an IDLE code block, an added L code block plus an S code block can support 3[(7*8*2)/32=3.5] layers of label nesting. By deleting two IDLE code blocks, the added two The number of L code blocks plus the S code block can support 5[(7*8*3)/32=5.25] levels of label nesting.

Optionally, signaling such as transmission routing and label distribution can be carried through FlexE overhead. The network device may include a control plane and a data plane. The control plane is used to perform service control and configuration on the data plane, and the data plane transmits service data under the control and guidance of the control plane. The transmission route and label distribution signaling are used to configure the forwarding relationship of the service on the control plane of the network device, for example, the service is on the inbound interface and the outbound interface of a certain network device. When the data plane of the network device receives the customer service, it can obtain the forwarding relationship configured on the control plane for the customer service according to the forwarding label carried in the customer service and forward it. The FlexE overhead can be added when the code block flow of the customer service enters each FlexE physical interface (PHY), and the FlexE overhead can be represented by an O code block. The schematic diagram of the structure of the FlexE overhead code block is shown in Figure 8, and signaling such as transmission routing and label distribution can be carried through the management channel in the FlexE overhead.

FIG. 9 is a network architecture diagram of a flexible Ethernet provided by an embodiment of the present invention. As shown in FIG. 9 , the Ethernet may include edge node devices and switching node devices. Generally, edge node devices are used to connect with client devices and receive client services from client devices. The switching node devices and edge node devices, as well as different switching node devices, are connected through interfaces, such as P1, P2, P3, Pn, etc., for transferring customer services. The side connecting the edge node device to the client device can be called the client side, and the side connecting the edge node device and the switching node device or the side connecting the two switching node devices is called the line side.

FIG. 10 is a schematic structural diagram of an edge node device according to an embodiment of the present invention. As shown in FIG. 10 , the device may include a client signal processing module 101 , a label encapsulation module 102 , a FlexE SHIM module 103 , a label assignment module 104 , an overhead processing module 105 , a routing table generation/update module 106 and at least one PHY module 107 . Wherein, these modules may be circuit modules integrated on a chip, or may be independent circuit modules. The functions implemented by the edge node device in the sending direction include:

The client signal processing module 101 is configured to receive the client service from the client device and determine the service type of the client service. The service types of the customer service received by the edge node device may include: data service and TDM service. The data service may be a packet service, an Ethernet data service, an MPLS service, an Internet Protocol (Internet Protocol, IP) service, and the like. The TDM service may be a Synchronous Digital Hierarchy (SDH) service, an Optical Transport Network (Optical Transport Network, OTN) service, and the like.

The label encapsulation module 102 is used to perform 64B/66B encoding on the customer service to form a 66B code block stream. The first forwarding label is acquired from the label assigning module 104, and the first forwarding label is added to the control code block in the 66B code block stream formed by the customer service. For example, the control code block may be an S code block. The schematic structural diagrams of the S code block and the first forwarding label may refer to FIG. 5 and FIG. 6, respectively, and how to add the first forwarding label to the S code block may also refer to the above-mentioned embodiments, which will not be repeated here.

If the received client service is a data service, such as an Ethernet data service, the client service itself carries the S code block. If the received client service is a TDM service, such as an OTN service, the client service itself does not carry the S code block. For the TDM service, the OTN service is taken as an example to describe how to add an S code block to the OTN service.

The overhead structure of the OTN frame is shown in FIG. 11 , the frame alignment signal (Frame Alignment Signal, FAS) of the first 6 bytes of the OTN frame is the frame alignment overhead, and the fixed pattern is 0xf6f6f6282828. When the OTN service is mapped to the FlexE service layer, the stream slice is divided into bit blocks for the OTN service, and the rate adjustment and adaptation are performed on the IDLE code block. The implementation manner of adding the S code block in the OTN service may include:

Manner 1: When stream slicing is performed on the OTN service, the six frame positioning overheads (FAS) of the OTN frame header are converted into S code blocks. For example, when the OTN frame header indicates the arrival, delete the 6-byte FAS of the OTN frame header, insert the S code block, and continue to slice the subsequent data stream.

Mode 2: When stream slicing is performed on the OTN service, an S code block may be added to the OTN service. For example, when the OTN frame header indicates the arrival, an S code block is inserted, and at the same time, an IDLE code block can also be deleted to adapt to the signal rate after the S code block is added. The data stream is then sliced from the first byte of the OTN frame.

If the customer service requires multiple layers of label nesting, the second forwarding label can also be added by deleting the IDLE code block in the customer service and adding the L code block. The schematic diagram of the structure of the L code block may refer to FIG. 7 , and how to add the second forwarding label to the L code block may also refer to the foregoing embodiment, which will not be repeated here.

Before adding the first forwarding label and/or the second forwarding label to the customer service, 64B/66B encoding can be performed on the customer service, the customer service can be converted into a 66B code block stream, and then rate adaptation is performed on the 66B code block stream, for example , IDLE code blocks can be inserted or deleted in the 66B code block stream. Optionally, the rate adaptation for the 66B code block stream may be completed after adding the first forwarding label and/or the second forwarding label, or the first forwarding may be added while the rate adaptation is performed on the 66B code block stream. The label and/or the second forwarding label are not limited in the present invention.

The label assignment module 104 is used for forwarding label assignment to customer services. The forwarding label includes the first forwarding label, the second forwarding label, etc. mentioned above, and the principles of allocating forwarding labels at different levels may be the same. Here, the first forwarding label is taken as an example for description. For data services, for example, Ethernet data services, the label assignment module 104 may assign the first forwarding label according to any one or more of the IP header, MAC address, and flow identifier of the client service. For example, the first forwarding label may be allocated according to the principle of forwarding equivalence class (Forwarding Equivalence Class, FEC). The forwarding equivalence class refers to forwarding a group of services in the same way, for example, through the same channel or with the same forwarding destination address. If the subsequent customer service and the previous customer service belong to the same flow, for example, have common IP or common quintuple information, the same first forwarding label can be used. Optionally, if the customer service encapsulation module 102 determines that the current customer service can use the same first forwarding label as the previous customer service, it can also directly add the first forwarding label of the previous customer service without obtaining the forwarding label from the label assignment module 104. A forwarding label. The label allocation module 104 can also allocate the number of time slots occupied for the customer service according to the bandwidth of the customer service and the bandwidth granularity of the network. For example, the time slot granularity of a FlexE service layer in a flexible Ethernet is 5G, and for a 10G customer service, two time slots can be allocated for the 10G customer service.

For TDM services, such as OTN services, forwarding labels can be allocated according to pre-configured information. The preconfigured information may include forwarding label information, time slot information, and the like. When the service is activated, the forwarding label information, time slot information, etc. can be pre-configured for the TDM service through the network management. For example, 2 time slots are allocated for 10G TDM service, and label 1 is used as the first forwarding label.

The FlexE SHIM module 103 is used to map the customer service into the FlexE service layer time slot (Calendar). The customer service can be mapped to the corresponding time slot according to the forwarding label information, and the customer service can also be mapped to the corresponding time slot according to the time slot information. Optionally, there is a correspondence between the forwarding label and the N time slots occupied by the customer service. For example, a 10G client service occupies timeslot 1 and timeslot 2, and the first forwarding label of the client service is label 1, so label 1 has a corresponding relationship with timeslot 1 and timeslot 2. The FlexE SHIM module 103 can map the customer service to time slot 1 and time slot 2 according to the first forwarding label label 1 carried by the customer service, or can also map the customer service to the time slot 1 and time slot 2 according to the time slot information of the customer service (occupy time slot 1 and time slot 2). ), and map the customer service to time slot 1 and time slot 2. Wherein, the first forwarding label may indicate which one or several PHY modules are used to transmit the client service. The FlexE service layer time slots that carry customer traffic can be distributed to one or more PHY modules, while inserting FlexE overhead.

The PHY module 107 is used to send the client service to the physical transmission link on the line side. The edge node device has at least one physical interface. The client service is sent to a physical transmission link on the line side through the physical interface, such as an optical fiber. The client service can be received or forwarded by the target device through the physical transmission link. A physical interface may contain at least one PHY module, and each PHY module corresponds to a respective time slot. For example, a 100G PHY module corresponds to 20 FlexE time slots of 5G granularity. After the client service is mapped to N time slots, the client service is distributed to the corresponding PHY module according to the corresponding relationship between the time slot and the PHY module. For example, time slot 1 and time slot 2 occupied by the 10G client service both correspond to PHY1, then the time slot 1 and time slot 2 of the client service are distributed to PHY1.

The overhead processing module 105 is used for inserting the FlexE overhead. In distributing the N time slots of client traffic to one or more PHY modules 107, FlexE overhead may also be inserted in each PHY module. The FlexE overhead is used to monitor the link state, and the generation and update of the link state may instruct the routing table generation/update module 106 to generate and/or update the routing table. The routing table includes network topology information, service forwarding relationships, etc., which can provide a basis for allocating forwarding labels for customer services. The FlexE overhead may also carry signaling such as transmission routing and label distribution. For details, refer to the embodiment shown in FIG. 8 .

The functions implemented by the edge node device in the receiving direction include:

The PHY module 107 is used for receiving client services from the line side. Client traffic may be received from the physical transmission link through one or more PHY modules. For example, a 10G client service is received from PHY1.

The FlexE SHIM module 103 is used to receive client services from one or more PHY modules 107 . At this time, the client service can be a 66B code block stream. FlexE overhead is extracted in the 66B code block stream and data alignment is performed. The time slot (Calendar) of the FlexE service layer is restored again, and various customer services are restored according to the time slot information. For example, 10G client services corresponding to timeslot 1 and timeslot 2 are recovered from PHY1. Optionally, the FlexE SHIM module 103 may also send the FlexE overhead information to the overhead processing module 105, so that the overhead processing module 105 can monitor the link state according to the FlexE overhead information.

The label encapsulation module 102 restores the first forwarding label information of the client signal. For example, for a data service, the first forwarding label information in the S code block can be deleted and restored to the original S code block before adding the first forwarding label. Then, rate adaptation is performed by adding or deleting IDLE code blocks, etc., and the 66B code block stream is decoded and then sent to the client signal processing module 101 . For TDM services, if the S code block is added by deleting the IDLE code block, the S code block can be discarded; if the S code block is converted from the frame positioning overhead, the S code block can be restored to the frame header positioning overhead. Then, the synchronization header of the 66B code block stream is removed and sent to the client signal processing module 101 .

The client signal processing module 101 is used to receive the code block stream after 64B/66B decoding, and restore the original client service, such as TDM service, data service and so on.

In the embodiment of the present invention, the edge node device adds the first forwarding label to the customer service, performs service switching according to the first forwarding label, and sends the customer service to the target physical channel, thus realizing the same switching plane in the flexible Ethernet. exchange of various services.

FIG. 12 is a schematic structural diagram of a switching node device according to an embodiment of the present invention. As shown in FIG. 12, as shown in FIG. 10, the device may include a PHY module 201/207, a FlexE SHIM module 202/206, a label encapsulation module 203, a frame header alignment module 204, a switch module 205, a label allocation module 208, an overhead Processing module 209 and routing table generation/update module 210 . Wherein, these modules may be circuit modules integrated on a chip, or may be independent circuit modules. The functions implemented by the switching node device in the sending direction and in the receiving direction are the same. The following takes the functions implemented in the sending direction as an example to illustrate:

The PHY module 201 is used for receiving client services from the line side. For example, client traffic is received from edge node devices or other switch node devices through one or more PHY modules.

The FlexE SHIM module 202 is used to receive client traffic from one or more PHY modules 201 . At this time, the client service can be a 66B code block stream. FlexE overhead is extracted in the 66B code block stream and data alignment is performed. The time slot (Calendar) of the FlexE service layer is restored again, and various customer services are restored according to the time slot information. For example, 10G client services corresponding to timeslot 1 and timeslot 2 are recovered from PHY1. Optionally, the FlexE SHIM module 202 may also send the FlexE overhead information to the overhead processing module 209, so that the overhead processing module 209 can monitor the link state according to the FlexE overhead information.

The label encapsulation module 203 is configured to apply for a new first forwarding label (such as an outgoing label) to the label allocation module 208 according to customer services, such as the first forwarding label (such as an incoming label) carried in the S code block, and can also apply for label behavior instruct. The label assignment module 208 may store a forwarding label information table, as shown in Table 1, the forwarding label information table may include information such as node device identifier NE2, ingress interface P2, incoming label label 1, outgoing interface P3, outgoing label label 2, etc. Indications of tag behavior, such as tag nesting, can also be included. The function of the label allocation module 208 is similar to the function of the label allocation module 104 in the edge node device, and details are not repeated here.

Table 1

The inbound interface and/or inbound label may indicate which PHY module or modules on the node device NE2 receive the client service, and the outbound interface and outbound label may indicate which PHY module or modules on the node device NE2 send the client traffic. The first forwarding label carried by the customer service may be an incoming label, and the new first forwarding label is an outgoing label. A corresponding relationship is established between the incoming label and the outgoing label in the forwarding label information table. Therefore, the outgoing label and the outgoing interface can be obtained according to the incoming label. Tab behavior indications may include tab nesting, tab popping, tab swapping, and the like. When label nesting is required, an IDLE code block can be deleted, and the S code block that currently carries the first forwarding label is converted into an L code block. At the same time, an S code block carrying a new first forwarding label is added before the L code block. . If the outer label needs to be ejected, the S code block carrying the outer label is discarded, and an L code block behind the S code block is converted into an S code block. When the label needs to be popped up, if there is only one layer of labels, the S code block where the layer label is located is restored to the original S code block, that is, the label information is restored to the original data field. For TDM services, the last layer of labels generally cannot be popped up in advance.

The frame header alignment module 204 is used for aligning the 66B code block streams of various customer services, and sending the aligned code block streams to the switching module 205 .

The exchange module 205 is configured to exchange data according to the first forwarding label carried by the customer service. The first forwarding label here may be that the label encapsulation module 203 applies for a new first forwarding label, that is, an outgoing label, from the label assigning module 208 . Optionally, data exchange can also be performed according to the outbound interface. The switching module 205 is equivalent to determining from which PHY module(s) 207 the client traffic is sent.

The FlexE SHIM module 206 is used to map the customer service to the time slot (Calendar) of the FlexE service layer. The customer service can be mapped to the corresponding time slot according to the forwarding label information, and the customer service can also be mapped to the corresponding time slot according to the time slot information. Optionally, there is a correspondence between the forwarding label and the N time slots occupied by the customer service. For example, a 10G customer service occupies time slot 1 and time slot 2, and the first forwarding label of the customer service is label 2, so label 2 has a corresponding relationship with time slot 1 and time slot 2. The FlexE SHIM module 206 can map the customer service to the time slot 1 and time slot 2 according to the first forwarding label label 2 carried by the customer service, or can also map the customer service to the time slot 1 and time slot 2 according to the time slot information of the customer service (occupy time slot 1 and time slot 2). ), and map the customer service to time slot 1 and time slot 2. Wherein, the first forwarding label may indicate which PHY module or modules are used to transmit the client service. The FlexE service layer time slots that carry customer traffic can be distributed to one or more PHY modules, while inserting FlexE overhead. Optionally, a certain buffer may also be added for QoS processing of data services.

The PHY module 207 is used to send the client service to the line side of the other side. The functions of the PHY module 207 are similar to those of the PHY 107 in the edge node device, and are not repeated here.

The functions of the overhead processing module 209 and the routing table generating/updating module 210 are similar to the functions of the overhead processing module 105 and the table generating/updating module 106 in the edge node device, and will not be repeated here.

In the embodiment of the present invention, the customer service received by the switching node device carries the first forwarding label, and performs service exchange according to the first forwarding label, thereby realizing the exchange of multiple services in the same switching plane of the flexible Ethernet.

FIG. 13 is an exemplary flowchart of a method for processing customer services provided by an embodiment of the present invention. The method can be performed by Ethernet devices, OTN devices, routers, switches, etc., and includes the following steps:

S1301: Receive a client service, and map the client service into M time slots according to a first forwarding label carried in the client service, where the first forwarding label indicates a first forwarding destination address.

Optionally, the first forwarding label has a corresponding relationship with the M timeslots, and the client service is mapped into the M timeslots according to the first forwarding label.

Optionally, the client service is encoded, and the client service forms a code block stream; the first forwarding label is added to the S code block of the client service, and the S code block is the code block stream A code block type in .

Optionally, the first forwarding label is added to the L code block of the client service, the L code block is obtained by deleting the idle code block of the client service, and the idle code block is in the code block stream. A code block type of .

Optionally, the first forwarding label is added to the frame header positioning overhead of the client service.

Optionally, a second forwarding label is added to the customer service, where the second forwarding label indicates a second forwarding destination address of the customer service.

S1302: Send the client service to a target physical channel through the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address; where M is a positive integer greater than or equal to 1.

Optionally, the M time slots and the target physical channel have a corresponding relationship.

The first forwarding destination address may be the destination MAC address of the next-hop node device forwarding the client service, or may be the egress port identifier or the identifier of the PHY module of the node device forwarding the client service.

In the embodiment of the present invention, the customer service is mapped into M time slots through the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing the flexible Ethernet network. Multiple services are exchanged in the same switching plane.

FIG. 14 is an exemplary flowchart of a method for processing customer services provided by an embodiment of the present invention. The method can be performed by Ethernet devices, OTN devices, routers, switches, etc., and includes the following steps:

S1401: Acquire M timeslots of client services from the target physical channel, and acquire the client services from the M timeslots.

S1402: Acquire the first forwarding label in the customer service, delete the first forwarding label and/or add a third forwarding label; wherein, the first forwarding label indicates a first forwarding destination address, the target physical channel There is a corresponding relationship with the first forwarding destination address; M is a positive integer greater than or equal to 1.

Optionally, the first forwarding label is an incoming label, and the third forwarding label is an outgoing label; a third forwarding label is obtained according to the first forwarding label, wherein the first forwarding label and the third forwarding label are have a corresponding relationship.

Optionally, delete the idle code block of the client service, convert the S code block carrying the first forwarding label into an L code block, and add an S code block carrying the third forwarding label; the idle code The block, the S code block, and the L code block are respectively three types of code blocks in the code block stream formed by the encoding of the client service.

Optionally, delete the first forwarding label, and restore the code block carrying the first forwarding label to a normal code block; wherein, the normal code block includes the S code block, the L code block, and the frame header positioning overhead. The S code block and the L code block are respectively two code block types in the code block stream formed by the encoding of the client service.

The first forwarding destination address may be the destination MAC address of the node device receiving the client service, or may be the ingress port identifier or the identifier of the PHY module of the node device receiving the client service, or the like. The third forwarding label may indicate the destination MAC address of the next-hop node device forwarding the client service, or may be the egress port identifier or the identifier of the PHY module of the node device forwarding the client service.

In the embodiment of the present invention, the first forwarding label is obtained from the customer service, the first forwarding label is deleted and/or the third forwarding label is added, so as to realize the exchange of multiple services in the same switching plane of the flexible Ethernet.

FIG. 15 is a schematic diagram of a logical structure of a device for processing client services according to an embodiment of the present invention. The device can be implemented as an Ethernet device, an OTN device, a router, a switch, etc., and includes: a receiving module 1501 , a mapping module 1502 and a sending module 1503 .

The receiving module 1501 is used for receiving customer services.

The mapping module 1502 is configured to map the client service into M time slots according to a first forwarding label carried in the client service, where the first forwarding label indicates a first forwarding destination address.

Optionally, the mapping module 1502 is configured to: the first forwarding label has a corresponding relationship with the M timeslots, and map the client service to the M timeslots according to the first forwarding label middle.

A sending module 1503, configured to send the client service to a target physical channel through the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address; where M is greater than or equal to 1 positive integer of .

Optionally, the M time slots and the target physical channel have a corresponding relationship.

Optionally, the device further includes: an encoding module for encoding the customer service, and the customer service forms a code block stream; a first adding module for adding in the S code block of the customer service For the first forwarding tag, the S code block is a code block type in the code block stream.

Optionally, the first adding module is further configured to: add the first forwarding label to the L code block of the customer service, where the L code block is obtained by deleting the idle code block of the customer service, The idle code block is a code block type in the code block stream.

Optionally, the device includes a second adding module, configured to: add the first forwarding label to the frame header positioning overhead of the customer service.

Optionally, the device further includes a third adding module, configured to: add a second forwarding label to the customer service, where the second forwarding label indicates a second forwarding destination address of the customer service.

In the embodiment of the present invention, the customer service is mapped into M time slots through the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing the flexible Ethernet network. Multiple services are exchanged in the same switching plane.

FIG. 16 is a schematic diagram of a logical structure of a device for processing customer services according to an embodiment of the present invention. The device can be implemented for Ethernet devices, OTN devices, routers, switches, etc., and includes: a customer service acquisition module 1601 , a forwarding label acquisition module 1602 , and a forwarding label addition and deletion module 1603 .

a client service acquisition module 1601, configured to acquire M time slots of the client service from the target physical channel, and acquire the client service from the M time slots;

The forwarding label obtaining module 1602 is configured to obtain the first forwarding label in the customer service.

Optionally, the forwarding label obtaining module 1602 is configured to: the first forwarding label is an incoming label, and the third forwarding label is an outgoing label; obtain a third forwarding label according to the first forwarding label; wherein the The first forwarding label and the third forwarding label have a corresponding relationship.

A forwarding label addition and deletion module 1603, configured to delete the first forwarding label and/or add a third forwarding label; wherein, the first forwarding label indicates a first forwarding destination address, and the target physical channel and the first forwarding label The destination addresses have a corresponding relationship; M is a positive integer greater than or equal to 1.

Optionally, the forwarding label addition and deletion module 1603 is configured to: delete the idle code block of the customer service, convert the S code block carrying the first forwarding label into an L code block, and add the third code block carrying the third forwarding label. The S code block of the forwarding label; the idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the encoding of the customer service.

Optionally, the forwarding label addition and deletion module 1603 is configured to: delete the first forwarding label, and restore the code block carrying the first forwarding label to a normal code block; wherein, the normal code block includes an S code Any one of the block, the L code block and the frame header positioning overhead, the S code block and the L code block are respectively two code block types in the code block stream formed by the encoding of the client service.

In the embodiment of the present invention, the first forwarding label is obtained from the customer service, the first forwarding label is deleted and/or the third forwarding label is added, so as to realize the exchange of multiple services in the same switching plane of the flexible Ethernet.

FIG. 17 is a schematic structural diagram of a computer device according to an embodiment of the present invention. As shown in FIG. 17 , the computer device 1700 includes a processor 1701 , a memory 1702 , an input/output interface 1703 , a communication interface 1704 and a bus 1705 . The processor 1701 , the memory 1702 , the input/output interface 1703 and the communication interface 1704 are connected to each other through the bus 1705 for communication.

The processor 1701 may use a general-purpose central processing unit (Central Processing Unit, CPU), a microprocessor, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or at least one integrated circuit, and is used to execute a relevant program to implement the present invention. The technical solutions provided by the embodiments of the invention.

The memory 1702 may be a read only memory (Read Only Memory, ROM), a static storage device, a dynamic storage device, or a random access memory (Random Access Memory, RAM). Memory 1702 may store operating systems and other applications. When implementing the technical solutions provided by the embodiments of the present invention through software or firmware, program codes for implementing the technical solutions provided by the embodiments of the present invention are stored in the memory 1702 and executed by the processor 1701 .

The input/output interface 1703 is used for receiving input data and information, and outputting data such as operation results.

Communication interface 1704 enables communication between computer device 1700 and other devices or a communication network using transceiving means such as, but not limited to, a transceiver.

The bus 1705 may include a path to communicate information between the various components of the computer device 1700 (eg, the processor 1701, the memory 1702, the input/output interface 1703, and the communication interface 1704).

The computer device 1700 executes the code stored in the memory 1702 through the processor 1701, and implements the following steps: receiving a customer service, mapping the customer service to M time slots according to the first forwarding label carried in the customer service, and the The first forwarding label indicates the first forwarding destination address; the client service is sent to the target physical channel through the M time slots, and the target physical channel has a corresponding relationship with the first forwarding destination address; wherein M is a positive integer greater than or equal to 1.

The computer device 1700 executes the code stored in the memory 1702 through the processor 1701, and implements the following steps: acquiring M timeslots of client services from the target physical channel, acquiring the client services from the M timeslots; acquiring the The first forwarding label in the customer service, delete the first forwarding label and/or add a third forwarding label; wherein, the first forwarding label indicates a first forwarding destination address, and the target physical channel is the same as the first forwarding label. The forwarding destination addresses have a corresponding relationship; M is a positive integer greater than or equal to 1.

Specifically, the steps in the method embodiments shown in FIG. 13 and FIG. 14 can be implemented by the computer device 1700 shown in FIG. 17 . It should be noted that although the computer device 1700 shown in FIG. 17 only shows the processor 1701, the memory 1702, the input/output interface 1703, the communication interface 1704 and the bus 1705, those skilled in the art should understand that during the specific implementation process , the computer device 1700 also contains other devices necessary for normal operation. Meanwhile, according to specific needs, those skilled in the art should understand that the computer device 1700 may further include hardware devices that implement other additional functions. In addition, those skilled in the art should understand that the computer device 1700 may also only include the necessary devices for implementing the embodiments of the present invention, and does not necessarily include all the devices shown in FIG. 17 .

In the embodiment of the present invention, the customer service is mapped into M time slots through the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing the flexible Ethernet network. Multiple services are exchanged in the same switching plane.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. should be included within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (22)

1. A method for customer service processing, wherein the method comprises: receiving a client service, and mapping the client service into M time slots according to a first forwarding label carried in the client service, where the first forwarding label indicates a first forwarding destination address; Sending the client service to a target physical channel through the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address; Among them, M is a positive integer greater than or equal to 1. 2. The method according to claim 1, wherein the mapping of the client service into M time slots according to the first forwarding label carried in the client service comprises: The first forwarding label has a corresponding relationship with the M time slots, and the client service is mapped into the M time slots according to the first forwarding label. 3. The method according to claim 1, wherein the sending the client service to the target physical channel through the M time slots comprises: The M time slots have a corresponding relationship with the target physical channel. 4. The method according to any one of claims 1-3, wherein the method further comprises: encoding the client service, the client service forming a stream of code blocks; The first forwarding label is added to the S code block of the client service, where the S code block is a code block type in the code block stream. 5. The method of claim 4, wherein the method further comprises: The first forwarding label is added to the L code block of the client service, the L code block is obtained by deleting the idle code block of the client service, the idle code block is a code in the code block stream block type. 6. The method of claim 1, wherein the method further comprises: The first forwarding label is added to the frame header positioning overhead of the client service. 7. The method of claim 1, wherein the method further comprises: A second forwarding label is added to the client service, and the second forwarding label indicates a second forwarding destination address of the client service. 8. A method for customer business processing, wherein the method comprises: Obtain M timeslots of client services from the target physical channel, and obtain the client services from the M timeslots; acquiring the first forwarding label in the customer service, deleting the first forwarding label and/or adding a third forwarding label; The first forwarding label indicates a first forwarding destination address, and the target physical channel has a corresponding relationship with the first forwarding destination address; M is a positive integer greater than or equal to 1. 9. The method according to claim 8, wherein the deleting the first forwarding label and/or adding the third forwarding label comprises: The first forwarding label is an incoming label, and the third forwarding label is an outgoing label; obtaining a third forwarding label according to the first forwarding label; The first forwarding label and the third forwarding label have a corresponding relationship. 10. The method according to claim 8 or 9, wherein the adding a third forwarding label comprises: Deleting the idle code block of the customer service, converting the S code block carrying the first forwarding label into an L code block, and adding an S code block carrying the third forwarding label; The idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the encoding of the client service. 11. The method according to claim 8 or 9, wherein the deleting the first forwarding label comprises: Deleting the first forwarding label, and restoring the code block carrying the first forwarding label to a normal code block; The normal code block includes any one of the S code block, the L code block and the frame header positioning overhead, and the S code block and the L code block are respectively in the code block stream formed by the encoding of the customer service. Two code block types. 12. A device for customer service processing, characterized in that the device comprises: The receiving module is used to receive customer services; a mapping module, configured to map the client service into M time slots according to a first forwarding label carried in the client service, where the first forwarding label indicates a first forwarding destination address; a sending module, configured to send the client service to a target physical channel through the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address; Among them, M is a positive integer greater than or equal to 1. 13. The device of claim 12, wherein the mapping module is configured to: The first forwarding label has a corresponding relationship with the M time slots, and the client service is mapped into the M time slots according to the first forwarding label. 14. The device of claim 12, wherein the M time slots and the target physical channel have a corresponding relationship. 15. The device according to any one of claims 12-14, wherein the device further comprises: an encoding module, configured to encode the client service, and the client service forms a code block stream; A first adding module, configured to add the first forwarding label to the S code block of the client service, where the S code block is a code block type in the code block stream. 16. The device of claim 15, wherein the first adding module is further configured to: The first forwarding label is added to the L code block of the client service, the L code block is obtained by deleting the idle code block of the client service, the idle code block is a code in the code block stream block type. 17. The apparatus of claim 12, wherein the apparatus comprises a second addition module for: The first forwarding label is added to the frame header positioning overhead of the client service. 18. The device of claim 12, wherein the device further comprises a third addition module for: A second forwarding label is added to the client service, and the second forwarding label indicates a second forwarding destination address of the client service. 19. A device for customer service processing, characterized in that the device comprises: a client service acquisition module, configured to acquire M timeslots of client services from the target physical channel, and acquire the client services from the M timeslots; a forwarding label obtaining module, configured to obtain the first forwarding label in the customer service; a forwarding label addition and deletion module, configured to delete the first forwarding label and/or add a third forwarding label; The first forwarding label indicates a first forwarding destination address, and the target physical channel has a corresponding relationship with the first forwarding destination address; M is a positive integer greater than or equal to 1. 20. The device according to claim 19, wherein the forwarding label acquisition module is used for: The first forwarding label is an incoming label, and the third forwarding label is an outgoing label; obtaining a third forwarding label according to the first forwarding label; The first forwarding label and the third forwarding label have a corresponding relationship. 21. The device according to claim 19 or 20, wherein the forwarding label addition and deletion module is used for: Deleting the idle code block of the customer service, converting the S code block carrying the first forwarding label into an L code block, and adding an S code block carrying the third forwarding label; The idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the encoding of the client service. 22. The device according to claim 19 or 20, wherein the forwarding label addition and deletion module is used for: Deleting the first forwarding label, and restoring the code block carrying the first forwarding label to a normal code block; The normal code block includes any one of the S code block, the L code block and the frame header positioning overhead, and the S code block and the L code block are respectively in the code block stream formed by the encoding of the customer service. Two code block types.

Images