Communication method and network device

Abstract

Embodiments of the present application provide a communication method and network device, and relate to the technical field of communication, which can reduce the waste of bandwidth. A sending device receives data code blocks and marker code blocks of multiple physical coding sublayer (PCS) channels; inserts an Ethernet service identifier into the marker code blocks of the multiple PCS channels, the Ethernet service identifier being used to indicate an Ethernet service carried by the data code blocks in the PCS channel where the marker code blocks are located; maps the data code blocks and the marker code blocks in the multiple PCS channels to an optical transport network (OTN) container; and sends the OTN container to an optical transport network.

Description

Technical Field

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

[0002] Ethernet based on 802.3, as defined by the Institute of Electrical and Electronics Engineers (IEEE), is already used as a service interface in various applications. Currently, the Optical Internetworking Forum (OIF) is discussing expanding the application scenarios of traditional Ethernet to support features such as sub-rate, channelization, and reverse multiplexing for Ethernet services, calling this Ethernet technology Flex Ethernet (FlexE). For example, for sub-rate applications of Ethernet services, it supports transmitting 50G Ethernet services using existing 100GE PMD (physical medium dependent) layers. For reverse multiplexing scenarios of Ethernet services, it supports transmitting 200G Ethernet services using two existing 100GE PMD layers. For channelized application scenarios of Ethernet services, this technology combines sub-rate and reverse multiplexing techniques. It supports the reverse multiplexing of multiple standard Ethernet PMDs into a high-bandwidth FlexE service layer. The FlexE service layer carries multiple FlexE services; for example, one 250G and five 10G FlexE services are transmitted through a 300G FlexE service layer, which is composed of three 100G EPMDs reverse-multiplexed. In traditional OTN (optical transport network) network transmission, the destinations of the various FlexE services carried by the FlexE service layer are different, making it impossible to transmit the FlexE service layer as a whole. The traditional solution is to identify each FlexE service and directly map each FlexE service to an ODUk (Optical Channel Data Unit-k) container or an ODUflex (Optical Channel Data Unit-flexible) container for transmission, with one FlexE service corresponding to one ODUk / ODUflex container. Thus, when FlexE services exceed the bandwidth of a single line interface in a traditional OTN network, the bandwidth of the line interface must be upgraded. This requires end-to-end transformation of the traditional OTN network according to the service path, resulting in high network construction costs for OTN networks.

[0003] To address the aforementioned issues, high-bandwidth FlexE services can be transmitted using multiple low-bandwidth ODUk / ODUflex containers. Typically, the FlexE service is divided into multiple data queues that satisfy the requirements of these low-bandwidth ODUk / ODUflex containers. Furthermore, control blocks for identifying the FlexE service are inserted between the data blocks that make up each data queue. However, these additional control blocks consume bandwidth, requiring pre-allocated bandwidth and rate adaptation in advance, resulting in wasted bandwidth resources. Summary of the Invention

[0004] The embodiments of this application provide a communication method and network device that can reduce bandwidth waste.

[0005] Firstly, a communication method is provided. This method can be executed by a transmitting device, which may be a module or chip within the transmitting device, or a chip or system-on-a-chip. The method includes the following steps: First, the transmitting device receives data code blocks and tag code blocks from multiple Physical Coding Sublayer (PCS) channels; second, it inserts an Ethernet service identifier into the tag code blocks of the multiple PCS channels, the Ethernet service identifier indicating the Ethernet service carried by the data code blocks in the PCS channel where the tag code blocks reside; third, it maps the data code blocks and tag code blocks from the multiple PCS channels to an optical transport network container; exemplarily, the optical transport network container includes an optical channel data unit (OCR) container or a flexible OCR container; fourth, it sends the optical transport network container into an optical transport network. In the above scheme, when the transmitting device receives data code blocks and marker code blocks from multiple Physical Coding Sublayer (PCS) channels, each PCS channel includes multiple marker code blocks spaced apart. Adjacent marker code blocks are separated by multiple data code blocks used to carry the original data stream. In this scheme, the transmitting device directly inserts the Ethernet service identifier into the marker code blocks of the multiple PCS channels for Ethernet services, without performing any other processing on the code blocks carried by the PCS channels. Then, the data code blocks and marker code blocks carried by the multiple PCS channels are mapped to an optical transport network container. For example, the sub-data streams carried by the multiple PCS channels can be combined into one or more data streams. Each sub-data stream includes a data queue formed by data code blocks and marker code blocks from the PCS channels. Each data stream can... The system includes at least one physical sublayer PCS channel carrying sub-data streams. These combined data streams are then mapped to optical transport network containers with matching bandwidth and transmitted to the optical transport network. Each PCS channel carries an identification code block for data block alignment. Since each identification code block corresponds to one PCS channel, and in this application's scheme, the identification code block also carries an Ethernet service identifier indicating the Ethernet service carried by the data blocks in the PCS channel containing the identification code block, the receiving device, upon receiving the optical transport network container transmitted from the optical transport network, can align the data blocks of each PCS channel according to the identification code block. Furthermore, based on the PCS channel corresponding to the identification code block and the carried Ethernet service identifier, it can combine the data blocks in the PCS channels with the same Ethernet service identifier to recover the original data stream. This avoids bandwidth consumption because it eliminates the need to insert additional control code blocks between multiple data blocks in a PCS channel.

[0006] In one possible implementation, the tag block includes an alignment identifier (AM), and the Ethernet service identifier is set in the BIP7 field of the AM. Taking 100GE Ethernet service as an example, the tag block can adopt the AM mentioned above. The encoding corresponding to the AM includes the fields M0, M1, M2, BIP3, M3, M4, M5, M6, and BIP7 in the format specified by the IEEE 802.3 standard. In the embodiments of this application, the Ethernet service identifier (e.g., client identifier (CID)) can be set in the BIP7 field of the AM.

[0007] In one possible implementation, the codeword marker includes a rate compensation (RC) identifier. The PCS channel identifier is carried in bits [29:26] of the rate compensation RC identifier, and the Ethernet service identifier is carried in bits [65:58] of the RC identifier. Taking 200G / 400GE Ethernet service as an example, in the G.709 protocol, the codeword marker (CWM) of the Reed-Solomon forward error correction (RSFEC) layer of 200G / 400GE Ethernet service, namely AM, is replaced with a rate compensation (RC) identifier. RC and AM are in the same position in the PCS channel but have different contents. Since the protocol requires scrambling of both RC and data code blocks according to the PCS channel they belong to, the encoding of RC cannot directly distinguish the PCS channel. In the embodiment of this application, the PCS channel number can be entered and exited in bits [29:26] of RC0 / RC1. The Ethernet service identifier (e.g., client ID, CID) is filled in bits [65:58]. For 200GE Ethernet services, each PCS channel supports a minimum bandwidth of 200 / 8 = 25G. Therefore, 200GE Ethernet services have 8 RC pairs, and bits [29:26] in the 8 different RC0 / 1 channels are filled with 0x0 / 0x1 / 0x2 / 0x3… / 0x7 respectively. For 400GE Ethernet services, each PCS channel supports a minimum granularity of 400 / 16 = 25G. Therefore, 400GE Ethernet services have 16 RC pairs, and bits [29:26] in the 16 different RC0 / 1 channels are filled with 0x0 / 0x1 / 0x2 / 0x3… / 0xf respectively.

[0008] In one possible implementation, a PCS channel includes multiple marker blocks spaced apart, with multiple data blocks between adjacent marker blocks, and each PCS channel corresponds to one type of marker block; the data blocks carry the raw data stream of Ethernet services.

[0009] In one possible implementation, the marker block and the data block are 66-bit blocks formed using a 64 / 66-bit encoding method.

[0010] In one possible implementation, in a PCS channel, there is a gap of 16,383 data blocks between two adjacent marker blocks.

[0011] Secondly, a communication method is provided. This method can be executed by a receiving device, which can be a module or chip within the receiving device, or a chip or system-on-a-chip. The method includes the following steps: First, the receiving device demaps data blocks and tag blocks in multiple PCS channels transmitted in the optical transport network. The tag blocks contain Ethernet service identifiers, which are used to indicate the Ethernet service carried by the data blocks in the PCS channels where the tag blocks are located. Second, the receiving device recovers the original data stream of the Ethernet service from the data blocks in the PCS channels where the tag blocks with the same Ethernet service identifier are located. Since the PCS channel itself carries identification code blocks for data block alignment, and each identification code block corresponds to one PCS channel, and in the scheme of this application, the identification code block carries an Ethernet service identifier, the receiving device, after receiving the optical transport network container transmitted from the optical transport network, can align the data code blocks of each PCS channel according to the identification code blocks, and combine the data code blocks in the PCS channel corresponding to the same Ethernet service identifier to recover the original data stream based on the PCS channel corresponding to the identification code block and the carried Ethernet service identifier. This avoids bandwidth occupation because there is no need to insert additional control code blocks between multiple data code blocks in the PCS channel.

[0012] In one possible implementation, the tag block includes AM, and the Ethernet service identifier is set in the BIP7 domain of AM.

[0013] In one possible implementation, the tag block includes a rate matching RC identifier, the PCS channel identifier carried in the bits of the rate matching RC identifier [29:26], and the Ethernet service identifier carried in the bits of the rate matching RC identifier [65:58].

[0014] In one possible implementation, a PCS channel includes multiple marker blocks spaced apart, with multiple data blocks between adjacent marker blocks, and each PCS channel corresponds to one type of marker block; the data blocks carry the raw data stream of Ethernet services.

[0015] In one possible implementation, the data code block includes a 66-bit code block; the receiving device recovers the original data stream of the Ethernet service from the data code blocks in the PCS channel where the marker code blocks with the same Ethernet service identifier are located, including: decoding the data code blocks in the PCS channel where the marker code blocks with the same Ethernet service identifier are located in a 64 / 66-bit decoding mode and combining them into the original data stream of the Ethernet service.

[0016] In one possible implementation, in a PCS channel, there is a gap of 16,383 data blocks between two adjacent marker blocks.

[0017] Thirdly, a transmitting device is provided, which can be a module or chip within the transmitting device, or the transmitting device can be a chip or a system-on-a-chip, comprising: a receiver for receiving data code blocks and marker code blocks of multiple Physical Coding Sublayer (PCS) channels; a processor for inserting Ethernet service identifiers into the marker code blocks of the multiple PCS channels, the Ethernet service identifiers being used to indicate the Ethernet service carried by the data code blocks in the PCS channel where the marker code blocks are located; mapping the data code blocks and marker code blocks in the multiple PCS channels to an optical transport network container; and a transmitter for transmitting the optical transport network container into an optical transport network.

[0018] Fourthly, a receiving device is provided, which can be a module or chip within the receiving device, or a chip or system-on-a-chip, comprising: a receiver for receiving multiple optical transport network containers transmitted in an optical transport network; a processor for demapping data code blocks and tag code blocks in multiple PCS channels in the multiple optical transport network containers transmitted in the optical transport network, wherein the tag code block contains an Ethernet service identifier, and the Ethernet service identifier is used to indicate the Ethernet service carried by the data code block in the PCS channel where the tag code block is located; and recovering the original data stream of the Ethernet service from the data code blocks in the PCS channel where the tag code blocks with the same Ethernet service identifier are located.

[0019] Fifthly, a computer-readable storage medium is provided for storing a computer program, the computer program including instructions for executing the communication methods described in the first or second aspect and their possible implementations.

[0020] Sixthly, a computer program product is provided, the computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform the communication method as described in the first or second aspect and its possible implementations.

[0021] In a seventh aspect, a communication system is provided, comprising the transmitting device and the receiving device described in the preceding aspects.

[0022] The technical effects of any design method in the third aspect are similar to those of the different design methods in the first aspect, and will not be repeated here. The technical effects of any design method in the fourth aspect are similar to those of the different design methods in the second aspect, and will not be repeated here. The technical effects of any design method in the fifth, sixth, and seventh aspects are similar to those of the different design methods in the first and second aspects, and will not be repeated here. Attached Figure Description

[0023] Figure 1 A partial architecture diagram of an Ethernet network provided for embodiments of this application;

[0024] Figure 2 A schematic diagram of the field structure of AM provided for an embodiment of this application;

[0025] Figure 3 This is a schematic diagram of the structure of an Ethernet communication system provided in an embodiment of the present invention;

[0026] Figure 4 This is a schematic diagram of the structure of the transmitting device and the receiving device provided in the embodiments of this application;

[0027] Figure 5 A schematic diagram of a communication method provided for an embodiment of this application;

[0028] Figure 6 A schematic diagram illustrating a method for transmitting data code blocks and marker code blocks, provided for an embodiment of this application;

[0029] Figure 7 A schematic diagram of an RC structure provided for an embodiment of this application;

[0030] Figure 8 A schematic diagram of an RC structure is provided for another embodiment of this application;

[0031] Figure 9 A schematic diagram illustrating the combination of sub-data streams from multiple PCS channels into multiple data streams, provided for embodiments of this application;

[0032] Figure 10 A schematic diagram of a communication method provided for another embodiment of this application;

[0033] Figure 11 A schematic diagram illustrating the splitting of multiple data streams into multiple PCS channels is provided for embodiments of this application;

[0034] Figure 12 A schematic diagram of the structure of a transmitting device is provided for another embodiment of this application;

[0035] Figure 13 This is a schematic diagram of a receiving device provided for another embodiment of this application. Detailed Implementation

[0036] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0037] In Ethernet, Ethernet ports typically appear as a logical, data-oriented concept, called logical ports or simply ports, while Ethernet physical interfaces are a hardware concept, called physical interfaces or simply interfaces. An Ethernet port is usually identified by a Media Access Control Address (MAC) address. Traditionally, the speed of an Ethernet port is determined based on the speed of the Ethernet physical interface. Generally, the maximum bandwidth of an Ethernet port corresponds to the bandwidth of an Ethernet physical interface, such as 10 megabits per second (Mbps), 100 Mbps, 1000 Mbps (1Gbps), 10 Gbps, 40 Gbps, 100 Gbps, and 400 Gbps. Ethernet has seen widespread application and significant development over a considerable period. Ethernet port speeds have increased tenfold, evolving from 10 Mbps to 100 Mbps, 1000 Mbps (1Gbps), 10 Gbps, 40 Gbps, 100 Gbps, and 400 Gbps. As technology advances, the granularity of bandwidth varies more, making it easier for discrepancies to arise between the expected bandwidth and actual application needs. The bandwidth growth required by mainstream applications does not exhibit a tenfold increase, such as 50Gbps, 75Gbps, or 200Gbps. The industry hopes to provide support for Ethernet ports (virtual connections) with bandwidths of 50Gbps, 60Gbps, 75Gbps, 200Gbps, and 150Gbps.

[0038] On the one hand, there is a further desire to provide ports with flexible bandwidth, which can share one or more Ethernet physical interfaces. For example, two 40GE ports and two 10GE ports can share a single 100G physical interface. These ports can also be flexibly adjusted in response to changing demands, such as from 200Gbps to 330Gbps, or from 50Gbps to 20Gbps, to improve port utilization efficiency or extend their lifespan. For fixed-rate physical links, they can be cascaded to support the stacking of logical port rates (e.g., stacking and cascading two 100GE physical interfaces to support a 200GE logical port). On the other hand, the bandwidth resources obtained from the flexible stacking of physical interfaces can be pooled, allocating their bandwidth to specific Ethernet logical ports in granular units (e.g., 5G as a unit), enabling efficient sharing of several Ethernet virtual connections across stacked physical link groups. Thus, the concept of FlexE emerged; Flexible Ethernet is also known as Flexible Virtual Ethernet. FlexE supports functions such as sub-rates, channelization, and reverse multiplexing for Ethernet services. For example, in sub-rate Ethernet service applications, FlexE can support the transmission of 250G Ethernet services (MAC streams) using three existing 100GE physical interfaces. In reverse multiplexing Ethernet services, FlexE can support the transmission of 200G Ethernet services using two existing 100GE PMD layers. In channelization Ethernet services, FlexE can support several logical ports sharing one or more physical interfaces, enabling the multiplexing of multiple low-speed Ethernet services into high-speed flexible Ethernet.

[0039] Since Ethernet is widely used as the service interface in access networks and metropolitan area networks, FlexE technology, which aggregates service traffic based on Ethernet, can achieve seamless connection with the Ethernet interface of the underlying service network. The introduction of FlexE's sub-rate, channelization, and reverse multiplexing functions has greatly expanded the application scenarios of Ethernet, enhanced the flexibility of Ethernet applications, and enabled Ethernet technology to gradually penetrate into the transport network field.

[0040] FlexE provides a viable evolution direction for the virtualization of Ethernet physical links. Flexible Ethernet requires supporting several virtual Ethernet data connections on a cascaded set of physical interfaces. For example, four 100GE physical interfaces can be cascaded and bundled to support several logical ports. If the bandwidth of some logical ports decreases, the bandwidth of others increases, and the total decrease in bandwidth equals the total increase in bandwidth. The bandwidth block rate of these logical ports can be flexibly adjusted, all sharing the four 100GE physical interfaces. FlexE borrows from Synchronous Digital Hierarchy (SDH) / Optical Transfer Network (OTN) technologies to construct a fixed frame format for physical interface transmission and performs time-division multiplexing (TDM) time slot allocation. Taking the existing FlexE frame format as an example, FlexE's TDM time slot granularity is 66 bits, which can precisely correspond to carrying a 64B / 66B bit block. A FlexE frame consists of 8 lines. The first 64B / 66B bit block in each line is the FlexE overhead block. Following the overhead block is the payload area for time slot allocation, with 66-bit granularity, corresponding to 20 x 1023 66-bit bearer spaces. A 100GE interface bandwidth is divided into 20 time slots, each with a bandwidth of approximately 5Gbps. FlexE implements multiple transmission channels, i.e., multiple time slots, on a single physical interface through interleaving and multiplexing. Several physical interfaces can be bundled, and all the time slots of these interfaces can be combined to carry a single Ethernet logical port. For example, 10GE requires two time slots, 25GE requires five time slots, and so on. The logical port still displays sequentially transmitted 64B / 66B bit blocks. Each logical port corresponds to a MAC address, transmitting corresponding Ethernet packets. The identification of packet start and end points and idle padding is the same as in traditional Ethernet. FlexE is merely an interface technology that can transmit M1 / M2 bit block streams over Ethernet physical layer links. For example, 1G Ethernet uses 8 / 10-bit encoding, so 1GE physical layer links transmit 8 / 10-bit bit block streams; 10GE / 40GE / 100GE uses 64 / 66-bit encoding, so 10GE / 40GE / 100GE physical layer links transmit 64 / 66-bit bit block streams. In the future, with the development of Ethernet technology, other encoding methods will emerge, such as 128 / 130-bit encoding and 256 / 258-bit encoding.For M1 / M2 bit block streams, there are different types of bit blocks and they are clearly specified in the standard. The following explanation uses the code definition of 64 / 66-bit encoding as an example. The first two bits, "10" or "01", are the synchronization header bits of the 64 / 66 bit block, and the last 64 bits are used to carry the payload data.

[0041] More specifically, FlexE technology achieves decoupling between the MAC layer and the physical layer by introducing a FlexE shim layer on top of IEEE 802.3 (e.g., Figure 1 As shown by the dashed line in the diagram, from the perspective of the position of the FlexE shim layer implementing Flexible Ethernet technology within the IEEE 802.3 stack, after a data stream of a specific bandwidth reaches the MAC layer, it forms a parallel data stream through the media-independent interface (MII). This data stream is then combined into a 64-bit data signal. Subsequently, the FlexE shim layer encodes the data from the MII interface using 64B / 66B encoding, generating a 66-bit block consisting of two parts: a 2-bit synchronization header and a 64-bit payload. This logical serial stream of the 64B / 66B block is called the FlexE client in FlexE technology. In other words, FlexE technology adds a FlexE shim layer on top of the original scrambling, bypassing the original 64B / 66B encoding / decoding process, and placing the 64B / 66B encoding / decoding process on top of this FlexE shim layer. Its implementation is as follows... Figure 1 As shown, the FlexE architecture includes a MAC layer, a FlexE shim layer, and a physical layer. The MAC layer is a sublayer of the data link layer, connecting to the logical link control layer. The physical layer can be further divided into the physical coding sublayer (PCS), the physical medium attachment (PMA) sublayer, and the PMD sublayer. Figure 1 This also illustrates an architecture in traditional Ethernet where the MAC layer is directly connected to the physical layer. In this architecture, the data from the MAC layer is encoded in 64B / 66B at the PCS layer. The functions of each of these layers are implemented by corresponding chips or modules.

[0042] During signal transmission, the PCS performs operations such as data encoding, scrambling, overhead (OH), and alignment marker insertion. During signal reception, the PCS performs the reverse process. Signal transmission and reception can be implemented by different functional modules of the PCS.

[0043] The format of AM as defined in the existing IEEE P802.3ba standard is shown in Table 1. The processing of AM in the standard technology is described below. In the standard IEEE P802.3ba, to support skew correction at the receiving PCS to align data blocks in the PCS channel and reorder the individual PCS channels, AM is periodically added to each PCS channel. The form of AM is a specially defined 66-bit data block with a control block synchronization header. These AMs interrupt any ongoing data transmission, and AMs are inserted into all PCS channels simultaneously. The space for AMs is created by periodically deleting inter-packet gaps (IPGs) from the XLGMII / CGMII data stream. Other special properties of AMs are that they are unscrambled and do not conform to coding rules, because AMs are added after 64B / 66B data blocks in the transmitting PCS channel and are deleted before 64B / 66B decoding of data blocks in the receiving PCS channel. AMs are unscrambled to allow the receiving device to find AMs, align data blocks in the PCS channel, and reassemble the stream before descrambling. An AM (Advanced Media Arrangement) should be inserted after every 16383 66-bit data blocks on each PCS channel. Furthermore, the correspondence between the PCS lane number and the encoding of each channel during the above processing is shown in Table 1, providing a basis for judgment. In 100GbE technology, an AM is periodically added after each channel. The role of the AM is to reorder the PCS channels and recombine the overall data at the receiving end. At the receiving end, data from the PCS channels arrives at different times and in different orders due to skew during transmission. Therefore, it is necessary to rearrange the channel data and recombine the high-speed data stream based on the PCS lane number and encoding in the AM.

[0044]

[0045] Table 1

[0046] The PCS lane number indicates the lane number; each lane has a unique number, and the encoding of each PCSlane is different from each other. M0, M1, M2, BIP3, M3, M4, M5, M6, and BIP7 are fields defined in the AM format specified in the IEEE 802.3 standard, and their bit positions and lengths vary from [previous information]. Figure 2 As can be seen, M4, M5, and M6 are bitwise flips of M0, M1, and M2, respectively. Each alignment marker has two bit-interleaved parity fields, BIP3 and BIP7, where BIP7 is a bitwise flip of BIP3.

[0047] The main functions of the PMA sublayer are link monitoring, carrier monitoring, encoding and decoding, transmit clock synthesis, and receive clock recovery. The main functions of the PMD sublayer are scrambling / descrambling of the data stream, encoding and decoding, and DC recovery and adaptive equalization of the received signal.

[0048] It should be understood that the above Figure 1 The architecture shown is merely illustrative, and the architecture applicable to this application is not limited to traditional Ethernet, and Figure 1 The FlexE architecture shown can include, for example, a reconciliation sublayer (RS) between the MAC sublayer and the FlexE shim layer to provide a signal mapping mechanism between the MII and MAC sublayers; and a forward error correction (FEC) sublayer between the PCS and PMA sublayers to enhance the reliability of transmitted data, and so on.

[0049] See Figure 3 , Figure 3 This is a schematic diagram of an Ethernet communication system provided in an embodiment of the present invention. As shown in the figure, the network devices in the Ethernet communication system of this embodiment of the present invention may include at least a transmitting device 100 and a receiving device 200. The transmitting device 100 and the receiving device 200 can establish a communication connection through an optical transport network (OTN). The Ethernet communication system can realize uplink and downlink transmission, wherein uplink transmission is the transmitting device 100 sending FlexEthernet services to the OTN network, and downlink transmission is the receiving device 200 receiving FlexE services through the OTN network. Specifically, the network devices can be client devices such as routers and switches, or network-end devices such as Ethernet devices, OTN devices, and SDH devices.

[0050] Optionally, the network device in the embodiments of this application may also be referred to as a communication device, which may be a general-purpose device or a special-purpose device. The embodiments of this application do not specifically limit it in this regard.

[0051] Optional, such as Figure 4 The diagram shown is a structural schematic of the transmitting device 100 and the receiving device 200 provided in an embodiment of this application.

[0052] The transmitting device 100 includes at least one processor. Figure 4 (Example illustrated by including a processor 101) and at least one transceiver. Figure 4 (The example described herein includes a transceiver 103). Optionally, the transmitting device 100 may also include at least one memory. Figure 4 (Example illustrated by including a memory 102) When used as a user equipment, the transmitting device may further include at least one output device. Figure 4 (Example: This illustration includes an output device 104) and at least one input device. Figure 4 (The example described herein includes an input device 105).

[0053] The processor 101, memory 102, and transceiver 103 are connected via a communication line. The communication line may include a path for transmitting information between the aforementioned components.

[0054] Processor 101 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program according to the present application. In a specific implementation, as one embodiment, processor 301 may also include multiple CPUs, and processor 101 may be a single-core processor or a multi-core processor. Here, "processor" may refer to one or more devices, circuits, or processing cores used to process data (e.g., computer program instructions).

[0055] Memory 102 can be a device with storage function. For example, it can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory 102 can exist independently and be connected to processor 101 via a communication line. Memory 102 can also be integrated with processor 101.

[0056] The memory 102 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 101. Specifically, the processor 101 executes the computer execution instructions stored in the memory 102 to implement the communication method executed by the transmitting device in this embodiment of the application.

[0057] Alternatively, in this embodiment, the processor 101 may execute the functions related to the transmitting device in the communication method provided in the following embodiments of this application, and the transceiver 103 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0058] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code or computer program code, and the embodiments of this application do not specifically limit them.

[0059] Transceiver 103 can be any transceiver-like device used for communicating with other devices or communication networks. Transceiver 103 includes a transmitter (Tx) and a receiver (Rx), for example, in the embodiments of this application, the transmitting device 103 transmits an optical transport network container via the transmitter.

[0060] Output device 104 communicates with processor 101 and can display information in various ways. For example, output device 304 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc.

[0061] Input device 105 communicates with processor 101 and can accept user input in various ways. For example, input device 105 can be a mouse, keyboard, touch screen device, or sensing device.

[0062] The receiving device 200 includes at least one processor. Figure 4 The example described herein includes a processor 201 and at least one transceiver. Figure 4 (The example described herein includes a transceiver 203). Furthermore, the receiving device 200 may also include at least one network interface. Figure 4 (The example described herein includes a network interface 204). Optionally, the receiving device 200 may also include at least one memory. Figure 4 (The example described herein includes a memory 202.) The processor 201, memory 202, transceiver 203, and network interface 204 are connected via communication lines. The network interface 204 is used to connect to core network equipment via a link (e.g., an S1 interface), or to the network interfaces of other network devices via a wired or wireless link (e.g., an X2 interface). Figure 4 (Not shown in the text), this application embodiment does not specifically limit this. In addition, the relevant descriptions of the processor 201, memory 202 and transceiver 203 can be referred to the description of the processor 101, memory 102 and transceiver 103 in the transmitting device 100, and will not be repeated here.

[0063] The memory 202 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 101. Specifically, the processor 201 executes the computer execution instructions stored in the memory 202 to implement the communication method executed by the receiving device in this embodiment of the application.

[0064] Alternatively, in this embodiment, the processor 201 may perform the receiving device-related functions in the communication method provided in the following embodiments of this application, and the transceiver 203 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0065] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code or computer program code, and the embodiments of this application do not specifically limit them.

[0066] Transceiver 203 can be any transceiver-like device used for communicating with other devices or communication networks. Transceiver 203 includes a transmitter (Tx) and a receiver (Rx), for example, in the embodiments of this application, receiving device 200 transmits optical transport network containers through the receiver.

[0067] Understandable Figure 4 The illustrated structure does not constitute a specific limitation on the transmitting device 100 or the receiving device 200. For example, in other embodiments of this application, the transmitting device 100 or the receiving device 200 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. Furthermore, in some scenarios, the transmitting device 100 may also be used as a receiving device, and the receiving device 200 may also be used as a transmitting device.

[0068] The following will combine Figures 1 to 5 ,by Figure 3 Taking the uplink transmission of data from the transmitting device to the Ethernet as an example, the communication method provided in this application embodiment will be described in detail.

[0069] S101. The transmitting device receives data code blocks and marker code blocks from multiple Physical Coding Sublayer (PCS) channels.

[0070] A PCS channel comprises multiple marker blocks spaced at intervals, with multiple data blocks between adjacent marker blocks, as described in Table 1 above. Each PCS channel uses a specific marker block to number its PCS channel; that is, the multiple marker blocks spaced at intervals within a PCS channel are identical, while the marker blocks used in different PCS channels are different. The data blocks carry the raw data stream of the Ethernet service. Specifically, taking the data stream of a 100GE Ethernet service at the PCS layer as an example, it includes multiple blocks encoded in 66-bit atomic data blocks using a 64 / 66-bit encoding method, such as data blocks and marker blocks. Assuming each PCS channel supports 5G bandwidth granularity, the 66-bit blocks in the 100GE Ethernet service data stream at the PCS layer can be transmitted across 20 PCS channels. The marker blocks are used to align the data blocks in each PCS channel, and the data blocks carry the raw data stream of the MAC layer.

[0071] For example, taking 100GE Ethernet service as an example, the tag code block can adopt the AM mentioned above, such as... Figure 2 As shown in Table 1, since each AM corresponds to a different encoding, taking a 5G bandwidth PCS channel as an example, 20 PCS channels can be indicated. Specifically, after acquiring the Ethernet service, the transmitting device allocates 20 5G bandwidth PCS channels to the Ethernet service based on the bandwidth occupied by the Ethernet service.

[0072] S102. The transmitting device inserts Ethernet service identifiers into the marker blocks of multiple Physical Coding Sublayer (PCS) channels.

[0073] In step S102, the Ethernet service identifier is used to indicate the Ethernet service carried by the data block in the PCS channel where the marker block is located. Thus, if the 20 5G bandwidth PCS channels in step S101 are used to carry this Ethernet service, the Ethernet service identifier for this Ethernet service is inserted into the marker block in each of the 20 5G bandwidth PCS channels. For example, the Ethernet service identifier (specifically, the client identifier (CID)) can be inserted into the BIP7 field of the AM. See [link to documentation] for details. Figure 6 The diagram illustrates the transmission order of data blocks across multiple PCS channels. For example, refer to... Figure 6 This illustrates the transmission order of data blocks (66B) in each of the 20 PCS channels (0-19) defined in IEEE 802.3, arranged according to the PCS channel. Within each PCS channel, there is a 16383-block interval between every two adjacent AMs. Figure 6 As shown, there are 16383 data code blocks between AM1 and AM2. Figure 6 The black arrows indicate the transmission order of each data block and the AM (Advanced Modem). It should be noted that when transmitting data blocks in each PCS channel, scrambling can be applied to each data block according to the different PCS channels. However, since the AM is used to align the data blocks in each PCS channel at the receiving end, no scrambling is applied to the AM. It should be noted that... Figure 6 Each PCS channel contains marker blocks AM1 and AM2, and AM1 and AM2 are the same in the same PCS channel; AM1 and AM2 are different in different PCS channels. For example, AM1 and AM2 are the same in PCS channel 1, but they are inserted in different positions; in order to distinguish PCS channel 1 and PCS channel 2, AM1 and AM2 in PCS channel 1 are different from AM1 and AM2 in PCS channel 2.

[0074] Furthermore, taking 200G / 400GE Ethernet services as an example, the G.709 protocol replaces the code word marker (CWM) of the Reed-Solomon forward error correction (RSFEC) layer with a rate compensation (RC) marker. Specifically, refer to... Figure 7 As shown, the formats of RC0 and RC1 are illustrated, both with a length of 66 bytes, similar to AM. RC and AM are in the same position within the PCS channel but have different contents. Since the protocol requires scrambling both RC and data blocks according to their respective PCS channels, the encoding of RC cannot directly distinguish the PCS channel. In the embodiments of this application, refer to... Figure 8 As shown, the PCS channel number can be inserted into bits [29:26] of RC0 / RC1. The Ethernet service identifier (e.g., client ID, CID) is filled into bits [65:58]. For 200GE Ethernet services, each PCS channel supports a minimum bandwidth of 200 / 8 = 25G. Therefore, 200GE Ethernet services have 8 RC pairs, and bits [29:26] in 8 different RC0 / 1 channels are filled with 0x0 / 0x1 / 0x2 / 0x3… / 0x7 respectively. For 400GE Ethernet services, each PCS channel supports a minimum granularity of 400 / 16 = 25G. Therefore, 400GE Ethernet services have 16 RC pairs, and bits [29:26] in 16 different RC0 / 1 channels are filled with 0x0 / 0x1 / 0x2 / 0x3… / 0xf respectively.

[0075] S103. The transmitting device maps data code blocks and marker code blocks from multiple PCS channels into an optical transport network container.

[0076] For example, the transmitting device can combine sub-data streams carried by multiple PCS channels into one or more data streams. A sub-data stream includes data code blocks in the PCS channel and a data queue formed by marker code blocks. Depending on the configuration, the sub-data streams contained in one or more PCS channels can be freely combined into p data streams, where the sum of the bandwidths of each data stream n1, n2…np equals 100G. The bandwidths of each data stream in n1, n2…np can be the same or different. For example, refer to… Figure 9 As shown, for any Ethernet service, combined with Figure 9The 66-bit code blocks shown are explained below. Each 66-bit code block is exemplarily labeled xy, where x represents the PCS channel identifier and y represents the position of the code block in the PCS channel (the y-th 66-bit code block). This allows data code blocks 0.0, 1.0, 2.0, and 3.0 of PCS channels 0-3, as well as data code blocks 0.1, 1.1, 2.1, and 3.1, to be combined into an n0 data stream, which is then loaded into a 20G bandwidth optical transport network container. Similarly, data code blocks 4.0, 10.0, and 11.0 of PCS channels 4, 10, and 11, as well as data code blocks 4.1, 10.1, and 12.1, to be combined into an n1 data stream, which is then loaded into a 15G bandwidth optical transport network container. Exemplarily, the optical transport network container includes an optical channel data unit (OCR) k container or a flexible OCR k container. In this step, the p combined data streams are bitmapped (BMP) and loaded into the payload of the optical transport network container.

[0077] S104. The transmitting device sends each optical transport network container to the optical transport network.

[0078] In the above scheme, when the transmitting device receives data code blocks and marker code blocks from multiple Physical Coding Sublayer (PCS) channels, each PCS channel includes multiple marker code blocks spaced apart. Adjacent marker code blocks are separated by multiple data code blocks used to carry the original data stream. In this scheme, the transmitting device directly inserts the Ethernet service identifier into the marker code blocks of the multiple PCS channels for Ethernet services, without performing any other processing on the code blocks carried by the PCS channels. Then, the data code blocks and marker code blocks carried by the multiple PCS channels are mapped to an optical transport network container. For example, the sub-data streams carried by the multiple PCS channels can be combined into one or more data streams. Each sub-data stream includes a data queue formed by data code blocks and marker code blocks from the PCS channels. Each data stream can... The method includes at least one physical sublayer PCS channel carrying sub-data streams. These combined data streams are then mapped to optical transport network containers with matching bandwidth and transmitted to the optical transport network. Since each PCS channel carries an identification code block for data block alignment, and each identification code block corresponds to one PCS channel, and in this application's scheme, the identification code block also carries an Ethernet service identifier indicating the Ethernet service carried by the data blocks in the PCS channel containing the identification code block, the receiving device, upon receiving the optical transport network container transmitted from the optical transport network, can align the data blocks of each PCS channel according to the identification code block. Furthermore, based on the PCS channel corresponding to the identification code block and the carried Ethernet service identifier, the data blocks in the PCS channels with the same Ethernet service identifier are combined to recover the original data stream. This avoids bandwidth consumption because it eliminates the need to insert additional control code blocks between multiple data blocks in a PCS channel. Furthermore, since no additional control code blocks are required, there is no time slot overhead on the PCS channel, thus enabling direct compatibility with current Ethernet communication methods. In addition, the solution provided by the embodiments of this application is that the code blocks in the PCS channel are directly encapsulated into the optical transport network container at the original rate. Since no control code blocks are added between the divided code blocks, the transmission rate is not changed, and clock pass-through can be supported.

[0079] The following will combine Figures 1 to 4 as well as Figure 10 ,by Figure 3 Taking the downlink transmission of data received from Ethernet by the receiving device shown as an example, the communication method provided in the embodiments of this application will be described in detail.

[0080] S201. The receiving device demaps the data code blocks and marker code blocks in multiple PCS channels in multiple optical transport network containers transmitted in the optical transport network.

[0081] Specifically, the receiving device can demap p ODUFlex blocks to obtain p data streams. Since the tag code block contains an Ethernet service identifier, which indicates the Ethernet service carried by the data code block in the PCS channel where the tag code block resides, the receiving device obtains the sub-data stream carried by each PCS channel based on the tag code block in the p data streams. Specifically, in step S201, the receiving device can divide each data stream into 66-bit portions (BW / 5) according to the data stream bandwidth (bandwidth). If the sum of the bandwidths of the p data streams n1, n2…np equals 100G, then after all p data streams are divided, all 20 sub-data streams of the PCS channels can be obtained. The sub-data streams include the data code blocks and the data queues formed by the tag code blocks in the PCS channels.

[0082] S202, The receiving device recovers the original data stream of the Ethernet service from the data code blocks in the PCS channel where the marked code blocks with the same Ethernet service identifier are located.

[0083] Since the data code blocks of each PCS channel are scrambled in step S101, descrambling is required before step S202. As mentioned above, in a 100GE Ethernet service scenario, when the marker code block uses AM, descrambling is not performed; in a 200G / 400GE Ethernet service scenario, when the marker code block uses RC, descrambling is required simultaneously. Then, the data code blocks contained in the sub-data streams of each PCS channel are aligned according to the marker code blocks. Finally, the data code blocks in each PCS channel are recombined and merged to obtain the original data stream. It is understood that merging requires first performing 64 / 66-bit decoding on each data code block.

[0084] For example, refer to Figure 11As shown, for data blocks 0.0, 1.0, 2.0, 3.0, 0.1, 1.1, 2.1, and 3.1 contained in data stream n0, the sub-data streams carried by each PCS channel are obtained sequentially according to the PCS channel identifier. This yields data blocks 0.0 and 0.1 in PCS channel 0, data blocks 1.0 and 1.1 in PCS channel 1, data blocks 2.0 and 2.1 in PCS channel 2, and data blocks 3.0 and 3.1 in PCS channel 3; and data blocks 4.0, 11.0, 12.0, 4.1, 11.1, and 12. 1. Based on the identifier of the PSC channel, sequentially obtain the sub-data streams carried by each PCS channel, thus obtaining data code blocks 11.0 and 11.1 in PCS channel 11 and data code blocks 12.0 and 12.1 in PCS channel 12; then merge the data code blocks of each PCS channel to obtain the first data code blocks 0.0, 1.0, 2.0, 3.0, 4.0, 11.0, and 12.0 of each PCS channel for Ethernet service, and the second data code blocks 0.1, 1.1, 2.1, 3.1, 4.1, 11.1, and 12.1 of each PCS channel for Ethernet service.

[0085] In this application's solution, since each identifier code block corresponds to a PCS channel and carries a flexible Ethernet service identifier, the receiving device, upon receiving the optical transport network container transmitted from the optical transport network, can align the data code blocks of each PCS channel according to the identifier code block, and combine the data code blocks in the PCS channel corresponding to the same flexible Ethernet service identifier to recover the original data stream based on the PCS channel corresponding to the identifier code block and the carried flexible Ethernet service identifier. This avoids bandwidth occupation because there is no need to insert additional control code blocks between multiple data code blocks in the PCS channel. Furthermore, since no additional control code blocks are needed, there is no time slot overhead on the PCS channel, thus enabling direct compatibility with current Ethernet communication methods. Moreover, the solution provided in this application encapsulates the code blocks in the PCS channel directly into the optical transport network container at the original rate. Since no control code blocks are added between the divided code blocks, the transmission rate is not changed, thus supporting clock pass-through.

[0086] It is understood that the aforementioned network devices and terminal devices, etc., include corresponding hardware structures and / or software modules for performing each function in order to achieve the above-mentioned functions. Those skilled in the art should readily recognize that, based on the unit and algorithm operations of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0087] This application embodiment can divide the network device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0088] For example, when dividing the functional modules in an integrated manner, Figure 12 A schematic diagram of a transmitting device is shown. This transmitting device can be a chip or system-on-a-chip within a transmitting device, or other combined devices or components capable of implementing the functions of the transmitting device described above. This transmitting device can be used to perform the functions of the transmitting device involved in the above embodiments.

[0089] As one possible implementation method, Figure 12 The transmitting device shown includes a processing unit 1201, a transmitting unit 1202, and a receiving unit 1203. The receiving unit 1203 is used to receive data blocks and tag blocks from multiple Physical Coding Sublayer (PCS) channels; the processing unit 1201 is used to insert Ethernet service identifiers into the tag blocks of the multiple PCS channels, the Ethernet service identifiers indicating the Ethernet service carried by the data blocks in the PCS channel where the tag blocks are located; and to map the data blocks and tag blocks from the multiple PCS channels to an optical transport network container; the transmitting unit 1202 is used to transmit each of the optical transport network containers to the optical transport network.

[0090] In one possible implementation, the codeword mark includes an alignment identifier AM, and the Ethernet service identifier is set in the BIP7 field of the AM.

[0091] In one possible implementation, the codeword tag includes a rate matching (RC) identifier, the identifier of the physical coding sublayer channel is carried in the bits of the rate matching (RC) identifier [29:26], and the Ethernet service identifier is carried in the bits of the RC identifier [65:58].

[0092] In one possible implementation, a PCS channel includes multiple marker blocks spaced apart, with multiple data blocks between adjacent marker blocks, and each PCS channel corresponds to one type of marker block; the data blocks carry the raw data stream of Ethernet services.

[0093] In one possible implementation, the marker block and the data block are 66-bit blocks formed using a 64 / 66-bit encoding method.

[0094] In one possible implementation, in a physical coding sub-layer channel, there is a 16383 data code block interval between two adjacent marker code blocks.

[0095] All relevant content of each operation involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0096] In this embodiment, the transmitting device is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuitry, a processor and memory executing one or more software or firmware programs, integrated logic circuitry, and / or other devices that can provide the aforementioned functions. In a simplified embodiment, those skilled in the art will recognize that the transmitting device can employ... Figure 4 The form of the transmitting device is shown.

[0097] for example, Figure 4 The processor 101 can invoke computer execution instructions stored in the memory 103 to cause the transmitting device to execute the communication method in the above method embodiment.

[0098] For example, Figure 12 The functions / implementation processes of the receiving unit 1203, the transmitting unit 1202, and the processing unit 1201 can be understood through... Figure 4 The processor 101 in the memory calls computer execution instructions stored in the memory 103 to implement the function; or, Figure 12 The function / implementation process of the processing unit 1201 can be achieved through... Figure 4 The processor 101 in the memory calls computer execution instructions stored in the memory 103 to implement this. Figure 12 The function / implementation process of the transmitting unit 1202 can be achieved through... Figure 4 The transmitter in transceiver 103 is used to achieve this. Figure 12The function / implementation process of the receiving unit 1203 can be achieved through... Figure 4 The receiver in transceiver 103 is used to implement this.

[0099] Since the communication device provided in this embodiment can execute the above-described communication method, the technical effects it can achieve can be referred to the above-described method embodiments, and will not be repeated here.

[0100] This application embodiment can divide the receiving device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0101] For example, when dividing the functional modules in an integrated manner, Figure 13 A schematic diagram of a receiving device is shown. This receiving device can be a chip or system-on-a-chip (SoC) from the aforementioned receiving device, or other combined devices or components capable of implementing the functions of the aforementioned receiving device. This receiving device can be used to perform the functions of the receiving device involved in the above embodiments.

[0102] As one possible implementation method, Figure 13 The receiving device shown includes a receiving unit 1301 and a processing unit 1302. The receiving unit 1301 is used to receive multiple optical transport network containers (OPCs) transmitted in the optical transport network. The processing unit 1302 is used to demap data blocks and marker blocks from multiple PCS channels in the multiple OPCs transmitted in the optical transport network. The marker blocks contain Ethernet service identifiers, which are used to indicate the Ethernet service carried by the data blocks in the PCS channels where the marker blocks are located. The processing unit 1302 is used to recover the original data stream of the Ethernet service from the data blocks in the PCS channels where the marker blocks with the same Ethernet service identifier are located.

[0103] In one possible implementation, the codeword mark includes an alignment identifier AM, and the Ethernet service identifier is set in the BIP7 field of the AM.

[0104] In one possible implementation, the codeword tag includes a rate matching (RC) identifier, the identifier of the physical coding sublayer channel is carried in bits [29:26] of the rate matching RC identifier, and the Ethernet service identifier is carried in bits [65:58] of the rate matching RC identifier.

[0105] In one possible implementation, a PCS channel includes a plurality of marker blocks spaced apart, with a plurality of data blocks between adjacent marker blocks, and each PCS channel corresponds to one type of marker block; the data blocks carry the raw data stream of the Ethernet service.

[0106] In one possible implementation, the data code block includes a 66-bit code block; the processing unit 1302 is specifically used to decode the data code blocks in the PCS channel where the tag code blocks with the same Ethernet service identifier are located in a 64 / 66-bit decoding mode and combine them into the original data stream of the Ethernet service.

[0107] In one possible implementation, in one of the physical coding sub-layer channels, there is a 16383 data code block interval between two adjacent marker code blocks.

[0108] All relevant content of each operation involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0109] In this embodiment, the receiving device is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuitry, a processor and memory executing one or more software or firmware programs, integrated logic circuitry, and / or other devices that can provide the aforementioned functions. In a simplified embodiment, those skilled in the art will recognize that the receiving device can employ... Figure 4 The form of the receiving device shown.

[0110] for example, Figure 4 The processor 201 can invoke computer execution instructions stored in the memory 203 to cause the receiving device to execute the communication method in the above method embodiment.

[0111] For example, Figure 13 The functions / implementation of the receiving unit 1301 and processing unit 1302 can be achieved through... Figure 4 The processor 201 in the memory calls computer execution instructions stored in the memory 203 to implement the function; or, Figure 13 The function / implementation process of the processing unit 1302 can be achieved through... Figure 4 The processor 201 in the memory calls computer execution instructions stored in the memory 203 to implement this. Figure 13 The function / implementation process of the receiving unit 1301 can be achieved through... Figure 4 The receiver of transceiver 203 is used to implement this.

[0112] Since the receiving device provided in this embodiment can execute the above-described communication method, the technical effects it can achieve can be referred to the above-described method embodiments, and will not be repeated here.

[0113] Optionally, embodiments of this application also provide a communication device (e.g., the communication device may be a chip or a chip system), which includes a processor and an interface. The processor is used to read instructions to execute the methods in any of the above method embodiments. In one possible design, the communication device further includes a memory. The memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the methods in any of the above method embodiments. Of course, the memory may not be included in the communication device. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0114] Specifically, when the communication device is a transmitting device, the transmitting unit 1202 can be a transmitter when transmitting information; when the communication device is a receiving device, the receiving unit 1301 can be a receiver when receiving information. Furthermore, the transceiver, transmitter, or receiver can be a radio frequency circuit. When the communication device includes a storage unit, the storage unit is used to store computer instructions. The processor is communicatively connected to the memory, and the processor executes the computer instructions stored in the memory, causing the communication device to perform the method involved in the method embodiment. The processor can be a general-purpose central processing unit (CPU), a microprocessor, or an application-specific integrated circuit (ASIC).

[0115] When the communication device is a chip, the transmitting unit 1202 and the receiving unit 1301 can be input and / or output interfaces, pins, or circuits, etc. The processing unit 1201 and processing unit 1302 can execute computer execution instructions stored in the storage unit to cause the chip within the communication device to execute the method involved in the method embodiment. Optionally, the storage unit can be a storage unit within the chip, such as a register or cache. Alternatively, the storage unit can also be a storage unit located outside the chip within the terminal device or network device, such as a read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, such as random access memory (RAM).

[0116] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

[0117] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0118] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, include: The transmitting device receives data blocks and marker blocks from multiple Physical Coding Sublayer (PCS) channels; The transmitting device inserts an Ethernet service identifier into the marker code block of the multiple physical coding sublayer (PCS) channels. The Ethernet service identifier is used to indicate the Ethernet service carried by the data code block in the PCS channel where the marker code block is located. The transmitting device maps the data code blocks and marker code blocks in the plurality of PCS channels to an optical transport network container; The transmitting device sends the optical transport network container to the optical transport network.

2. The communication method according to claim 1, characterized in that, The marker block includes an alignment identifier (AM), and the Ethernet service identifier is set in the BIP7 field of the AM.

3. The communication method according to claim 1, characterized in that, The tag block includes a rate matching (RC) identifier, the identifier of the physical coding sublayer (PCS) channel is carried in bits [29:26] of the RC identifier, and the Ethernet service identifier is carried in bits [65:58] of the RC identifier.

4. The communication method according to any one of claims 1-3, characterized in that, A PCS channel includes multiple marker blocks spaced apart, and multiple data blocks are included between adjacent marker blocks. Each PCS channel corresponds to one type of marker block. The data blocks carry the raw data stream of the Ethernet service.

5. The communication method according to any one of claims 1-4, characterized in that, The marker code block and the data code block are 66-bit code blocks formed using a 64 / 66-bit encoding method.

6. The communication method according to any one of claims 1-5, characterized in that, In one of the PCS channels, there is a 16,383-block interval between two adjacent marker blocks.

7. A communication method, characterized in that, include: The receiving device demaps data blocks and marker blocks in multiple PCS channels in multiple optical transport network containers transmitted in the optical transport network. The marker blocks contain Ethernet service identifiers, which are used to indicate the Ethernet service carried by the data blocks in the PCS channels where the marker blocks are located. The receiving device recovers the original data stream of the Ethernet service from the data block in the PCS channel where the tag code block with the same Ethernet service identifier is located.

8. The communication method according to claim 7, characterized in that, The marker block includes an alignment identifier (AM), and the Ethernet service identifier is set in the BIP7 field of the AM.

9. The communication method according to claim 7, characterized in that, The tag block includes a rate matching (RC) identifier, the PCS channel identifier is carried in bits [29:26] of the rate matching RC identifier, and the Ethernet service identifier is carried in bits [65:58] of the rate matching RC identifier.

10. The communication method according to any one of claims 7-9, characterized in that, A PCS channel includes multiple marker blocks spaced apart, and multiple data blocks are included between adjacent marker blocks. Each PCS channel corresponds to one type of marker block. The data blocks carry the raw data stream of the Ethernet service.

11. The communication method according to any one of claims 7-10, characterized in that, The data code block includes a 66-bit code block; the receiving device recovers the original data stream of the Ethernet service from the data code blocks in the PCS channel where the marker code blocks with the same Ethernet service identifier are located, including: decoding the data code blocks in the PCS channel where the marker code blocks with the same Ethernet service identifier are located in a 64 / 66-bit decoding mode and combining them into the original data stream of the Ethernet service.

12. The communication method according to any one of claims 7-11, characterized in that, In one of the PCS channels, there is a 16,383-block interval between two adjacent marker blocks.

13. A transmitting device, characterized in that, include: The receiver is used to receive data code blocks and marker code blocks from multiple Physical Coding Sublayer (PCS) channels; The processor is configured to insert Ethernet service identifiers into the marker blocks of the plurality of Physical Coding Sublayer (PCS) channels, wherein the Ethernet service identifiers are used to indicate the Ethernet service carried by the data blocks in the PCS channel where the marker blocks are located; and to map the data blocks and marker blocks in the plurality of PCS channels to an optical transport network container. A transmitter for sending the optical transport network container to the optical transport network.

14. A receiving device, characterized in that, include: A receiver is used to receive multiple optical transport network containers transmitted in an optical transport network. A processor is configured to demap data blocks and tag blocks in multiple PCS channels in multiple optical transport network containers transmitted in an optical transport network, wherein the tag blocks contain Ethernet service identifiers, and the Ethernet service identifiers are used to indicate the Ethernet service carried by the data blocks in the PCS channels where the tag blocks are located; and to recover the original data stream of the Ethernet service from the data blocks in the PCS channels where the tag blocks with the same Ethernet service identifiers are located.

15. A computer-readable storage medium, characterized in that, Used to store a computer program, the computer program including instructions for performing the communication method as described in any one of claims 1-12.

16. A computer program product, characterized in that, The computer program product includes: computer program code, which, when run on a computer, causes the computer to perform the communication method as described in any one of claims 1-12.

Images