WO2020029893A1 - 接收码块流的方法、发送码块流的方法和通信装置 - Google Patents

接收码块流的方法、发送码块流的方法和通信装置 Download PDF

Info

Publication number
WO2020029893A1
WO2020029893A1 PCT/CN2019/099111 CN2019099111W WO2020029893A1 WO 2020029893 A1 WO2020029893 A1 WO 2020029893A1 CN 2019099111 W CN2019099111 W CN 2019099111W WO 2020029893 A1 WO2020029893 A1 WO 2020029893A1
Authority
WO
WIPO (PCT)
Prior art keywords
code block
type
stream
ordered set
code
Prior art date
Application number
PCT/CN2019/099111
Other languages
English (en)
French (fr)
Inventor
孙德胜
陈启昌
钟其文
牛乐宏
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2021506430A priority Critical patent/JP7192195B2/ja
Priority to EP19846007.3A priority patent/EP3823189A4/en
Priority to KR1020217006267A priority patent/KR102498937B1/ko
Publication of WO2020029893A1 publication Critical patent/WO2020029893A1/zh
Priority to US17/168,502 priority patent/US11902403B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0057—Block codes
    • H04L1/0058—Block-coded modulation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0057—Block codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00—Baseband systems
    • H04L25/38—Synchronous or start-stop systems, e.g. for Baudot code
    • H04L25/40—Transmitting circuits; Receiving circuits
    • H04L25/49—Transmitting circuits; Receiving circuits using code conversion at the transmitter; using predistortion; using insertion of idle bits for obtaining a desired frequency spectrum; using three or more amplitude levels ; Baseband coding techniques specific to data transmission systems
    • H04L25/4906—Transmitting circuits; Receiving circuits using code conversion at the transmitter; using predistortion; using insertion of idle bits for obtaining a desired frequency spectrum; using three or more amplitude levels ; Baseband coding techniques specific to data transmission systems using binary codes
    • H04L25/4908—Transmitting circuits; Receiving circuits using code conversion at the transmitter; using predistortion; using insertion of idle bits for obtaining a desired frequency spectrum; using three or more amplitude levels ; Baseband coding techniques specific to data transmission systems using binary codes using mBnB codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/741—Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/323—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the physical layer [OSI layer 1]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet

Definitions

  • Embodiments of the present application relate to the field of communications, and more specifically, to a method for receiving a code block stream, a method for sending a code block stream, and a communication device.
  • Ethernet technology has been widely cited in the network industry. Ethernet technology is greatly welcomed by network manufacturers for its simple, best-effort transmission methods and standardized interconnection and interconnection mechanisms. At present, the Ethernet technology has developed to a Flexible Ethernet 1.0 implementation protocol (hereinafter referred to as FlexE) based on the 100 Gigabit (G) Ethernet standard. FlexE's rate aggregation allows high-speed Ethernet service data flows to be carried together using multiple low-rate physical interfaces. Sub-rate and channelization allow multiple low-rate data flows to be carried concurrently within an Ethernet physical interface. A large number of network devices supporting Ethernet interfaces are deployed in the access network and metropolitan area networks. FlexE interfaces are compatible with standard Ethernet and expand the functions and flexibility of Ethernet. Before and after the 5th generation (5G) system Transmission network, data center interconnection and other deterministic low-latency, high-bandwidth scenarios have high market application prospects and development space.
  • 5G 5th generation
  • the transmission speed of FlexE can be measured in gigabit per second (Gbps).
  • customer signals in FlexE can include the following modes: Ethernet physical interface (5Gbps baseband, 5GBASE-R) that supports 5Gbps Mode, an Ethernet physical interface (10Gbps base range, 40GBASE-R) mode supporting a 10Gbps rate, and an Ethernet physical interface (25Gbps baserange, n ⁇ 25GBASE-R) mode supporting a 25Gbps rate.
  • the above-mentioned customer signals need to be forwarded via an Ethernet transmission network.
  • the Ethernet transmission network can use, for example, a 100 Gbps Ethernet physical interface (100 Gbps base range, 100 GBASE-R), a 200 Gbps Ethernet physical interface (200 Gbps base range, 200GBASE-R), 400Gbps Ethernet physical interface (400Gbps base range, 400GBASE-R) mode.
  • some ordered set type code blocks (such as 0x2d type code block or 0x55 type code block) in some modes such as 5GBASE-R, 10GBASE-R, or 25GBASE-R, etc. And not present in higher rate modes. Therefore, the code blocks of the ordered set type cannot be transmitted through a transmission network based on an interface with a rate of 100G and above, which affects the accuracy of communication.
  • the present application provides a method for sending and receiving a code block stream, a method for sending a code block stream, and a communication device, which can ensure the transmission of control code blocks and improve the accuracy of communication.
  • a method for receiving a code block stream including: a receiving device receives a code block stream of a first rate mode including a plurality of code blocks from a transmission network; and the receiving device determines a target code from the code block stream Block, wherein the target code block is a code block received by the receiving device within a packet gap of the code block stream, the target code block includes a first target code block, and the first target code block is a data type code block ; And / or the target code block includes a second target code block, the second target code block is an end type code block; the receiving device modifies the target code block to modify the target code block to a second rate An ordered set type of code block.
  • the target code block is a code generated by the sending device of the code block stream of the first rate mode and modifying the ordered set type code blocks in the code block stream of the second rate mode received from the client device. Piece.
  • the sending device can modify the code blocks of the ordered set type to data type code blocks or end type code blocks that can be recognized by the transmission network, so that the receiving device can change
  • the data type code block or end type code block located in the packet gap is determined to be modified based on the ordered set type code block, and the data type code block or end type code block located in the packet gap can be modified back to Ordered block type, which can ensure that the ordered set type block can be transmitted through the transmission network, and can also ensure that the receiving device reliably recognizes the ordered set type block, which can further improve communication. Accuracy.
  • the code block stream of the first rate mode may be an Ethernet signal (for example, a high-speed Ethernet signal) transmitted in a transmission network (for example, a network supporting FlexE) and is physically encoded in the layer PCS processing (for example, a code block stream (or bit code block stream or bit stream).
  • a transmission network for example, a network supporting FlexE
  • the layer PCS processing For example, a code block stream (or bit code block stream or bit stream).
  • the code stream of the second rate mode may be processed in a PCS in an Ethernet signal (for example, a low-to-medium-speed Ethernet signal) transmitted before a client device and a transmission device (for example, an ingress device or an egress device of a transmission network).
  • Ethernet signal for example, a low-to-medium-speed Ethernet signal
  • transmission device for example, an ingress device or an egress device of a transmission network.
  • Code block stream (or bit code block stream or bit stream).
  • the code block stream in the first rate mode sent by the sending device may be generated after the sending device performs processing such as transcoding on the code block stream in the second rate mode.
  • the receiving device may be an egress device transmitting a code block stream (or an Ethernet signal including the code block stream of the first rate mode) for the first rate mode in the network. That is, the Ethernet signal flows into the destination network of the Ethernet signal (including the destination client device of the Ethernet signal) from the transmission network via the egress device.
  • the sending device may be an entry device transmitting a code block stream (or an Ethernet signal including a code block stream of the first rate mode) for the first rate mode in the network. That is, the Ethernet signal flows into the transmission network from the source network of the Ethernet signal (including the source client device of the Ethernet signal) via the entry device.
  • the rate corresponding to the second rate mode is less than or equal to the rate corresponding to the first rate mode.
  • the rate corresponding to the second rate mode is less than or equal to the rate corresponding to the first rate mode
  • the signal of the first rate mode as the signal of the high speed mode can be composed of the signal including the second rate mode in The signals in one or more low-speed modes are aggregated.
  • the rate corresponding to the second rate mode is less than or equal to the rate corresponding to the first rate mode
  • the rate corresponding to the second rate mode can be understood as that the number of time slots that the signal of the first rate mode can include is greater than that of the signal of the second rate mode The number of time slots.
  • the first rate mode may include a 40GBASE-R mode, a 100GBASE-R mode, a 200GBASE-R mode, or a 400GBASE-R mode.
  • the transmission network may include Ethernet physical links in 40GBASE-R mode, 100GBASE-R mode, 200GBASE-R mode, or 400GBASE-R mode, or the transmission network may support rates of 40Gbps, 100Gbps, 200Gbps, or 400Gbps Ethernet physical interface mode.
  • the transmission equipment in the transmission network performs Ethernet signal forwarding based on 40GBASE-R mode, 100GBASE-R mode, 200GBASE-R mode, or 400GBASE-R mode.
  • the number of transmissions of the code stream in the first rate mode may be 40 Gbps, 100 Gbps, 200 Gbps, or 400 Gbps.
  • the Ethernet signal including the code block stream in the first rate mode may be an Ethernet signal in a 40GBASE-R mode, an Ethernet signal in a 100GBASE-R mode, an Ethernet signal in a 200GBASE-R mode, or an Ethernet signal in a 400GBASE-R mode. Ethernet signals.
  • the second rate mode may include a 5GBASE-R mode, a 10GBASE-R mode, or a 25GBASE-R mode.
  • the link between the client device and the ingress or egress device of the transport network may include an Ethernet physical link in 5GBASE-R mode, 10GBASE-R mode, or 25GBASE-R mode, or the client device may Supports Ethernet physical interface modes at 5Gbps, 10Gbps, or 25Gbps.
  • the client device and the ingress or egress device of the transmission network forward Ethernet signals based on the 5GBASE-R mode, 10GBASE-R mode, or 25GBASE-R mode.
  • the transmission amount of the code block stream in the second rate mode may be 5 Gbps, 10 Gbps, or 25 Gbps.
  • the Ethernet signal including the code block stream in the second rate mode may be a signal in a 5GBASE-R mode, a signal in a 10GBASE-R mode, or a signal in a 25GBASE-R mode.
  • the code blocks in the code block stream may be 64-bit code blocks, or the code blocks in the code block stream may be 66-bit code blocks.
  • the code block of the ordered set type may also be called an ordered set (O) code block.
  • the O code block may include a code block whose information carried in a block type field (block type field) is 0x2d.
  • the O-code block may include a code block whose information carried in the code block type field is 0x55.
  • bits carried in the sync header field of the O-code block are 10.
  • bit “10” can be understood as a binary (0b) bit or a value “10”. In the following, in order to avoid redundant description, the description of the same or detailed information is omitted.
  • the modification of the target code block by the receiving device includes: the receiving device modifies information carried in a code block type field of the second target code block to code block type information corresponding to the ordered set type.
  • the T code block may include a code block whose information carried in the code block type field is at least one of the following information:
  • the modification of the information carried in the code block type field of the target code block by the receiving device includes: the receiving device carries the information carried in the code block type field of the second target code block from 0x87, 0x99, 0xAA, 0xB4, 0xCC One of 0xD2, 0xE1, and 0xFF is modified to 0x2d or 0x55.
  • the receiving device modifies the information carried in the code block type field of the second target code block to the code block type information corresponding to the ordered set type, including: the receiving device changes the first end type according to the mapping relationship.
  • the information carried in the code block type field of the second target code block is modified to information corresponding to the first ordered set type, where the mapping relationship is used to indicate the relationship between at least two end types and at least two ordered set types.
  • a one-to-one mapping relationship, the first ordered set type corresponds to the first ending type, and the first ending type is any one of the at least two ending types.
  • the receiving device modifies the information carried in the code block type field of the second target code block to the code block type information corresponding to the ordered set type includes: the receiving device determines at least two end type code blocks and at least A one-to-one mapping relationship between two ordered set type code blocks; when the second target code block is a first end type code block, the receiving device, according to the mapping relationship, sets the code block type field of the target code block The information carried is modified to the information corresponding to the first ordered set type code block, where the first ordered set type code block is an ordered set type code block corresponding to the first end type code block indicated by the mapping relationship, The first end-type code block is any one of the at least two end-type code blocks.
  • an O code block whose information carried in the code block type field is 0x2d may correspond to a T code block whose information carried in the code block type field is 0xE1.
  • an O code block with information carried in the code block type field of 0x55 may correspond to a T code block with information carried in the code block type field of 0xFF.
  • bit carried in the synchronization header field of the T code block is 10.
  • the modification of the target code block by the receiving device includes: the receiving device modifies information carried in a synchronization header field of the first target code block into synchronization header information corresponding to the ordered set type.
  • This data type code block may also be referred to as a data (D, D) code block.
  • the receiving device modifies the information carried by the code block type field of the target code block includes: the receiving device changes the information carried by the code block type field of the first target code block from 01 Amended to 10.
  • the bit carried in the synchronization header field of the D code block is 01.
  • the receiving device modifies the information carried in the synchronization header field of the target code block to the information corresponding to the ordered set type code block includes: the receiving device modifies the information carried in the synchronization header field of the target code block from 01 to 10 .
  • the packet gap can also be called a frame gap, which refers to the transmission time interval between two Ethernet data packets.
  • Each data packet includes multiple code blocks.
  • the first code block of a data packet may be an S code block, and the last code block of a data packet may be a T code block.
  • the method further includes: the receiving device determines an end position of the packet gap according to a start type code block in the code block stream; The receiving device determines a start position of the packet gap according to an end type code block in the code block stream.
  • any one IPG may be located between two data packets (referred to as, data packet # 1 and data packet # 2), and the transmission order of data packet # 1 is located on data packet # 2.
  • the starting position of the IPG # 1 can be determined by the ending position of the data packet # 1, that is, the starting position of the IPG # 1 can be determined by the T code block in the data packet # 1. That is, when a device in the Ethernet receives the T code block in the data packet # 1, it can be considered that IPG # 1 starts.
  • the end position of the IPG # 2 may be determined by the start position of the data packet # 2, that is, the start position of the IPG # 1 may be determined by the T code block in the data packet # 1. That is, when the device in the Ethernet receives the S-code block in the data packet # 2, it can be considered that IPG # 1 ends.
  • each T code block in the Ethernet signal indicates the end of the packet, so that the start position of the frame gap can be determined according to T The position of the code block is determined.
  • the receiving device determines the target code block from the Ethernet signal, including: the receiving device will receive the target code block within a period in which the value of the first packet gap indication information is a preset first value.
  • the data type code block is determined as the target code block, where the first packet gap indication information is set to a preset second value when the receiving device receives the start type code block, and the receiving device receives the end type code
  • the first packet gap indication information is set to the first value at the time of the block.
  • the receiving device determines a target code block from the Ethernet signal, including: the receiving device determines a code block located after a T code block as a target code block (ie, a first target code block).
  • the receiving device determines a target code block from the Ethernet signal, including: the receiving device determines a code block located before the S code block as a target code block (ie, a first target code block).
  • some T code blocks in the Ethernet signal may be generated by modifying the control O code block.
  • the start position of the frame gap can be determined according to the position of the first T code block after the S code block.
  • the receiving device determines the start position of the packet gap according to the end type code block in the code block stream, including: the receiving device determines the first end type code block in the code block stream.
  • the first end type code block is the first end type code block that is located after the start type code block in the transmission order.
  • the receiving device determines a target code block from the Ethernet signal, including: the receiving device will receive an end type code block within a period during which the value of the first packet gap indication information is a preset first value. Is determined as the target code block (ie, the second target code block), where the first packet gap indication information is set to a preset second value when the receiving device receives the start type code block, and the receiving device The first packet gap indication information is set to the first value when the end type code block is received within a period during which the value of the first packet gap indication information is the second value.
  • a method for receiving a code block stream including: the sending device determines a code block stream in a first rate mode according to a code block stream in a second rate mode of multiple code blocks, where the second rate The ordered set type code block in the code block stream of the mode is modified to a data type code block, and / or the ordered set type code block in the code block stream of the second rate mode is modified to an end type.
  • Code block the sending device sends the code block stream of the first rate mode to a transmission network.
  • the sending device can modify the code blocks of the ordered set type to data type code blocks or end type code blocks that can be recognized by the transmission network, so that the receiving device can change
  • the data type code block or end type code block located in the packet gap is determined to be modified based on the ordered set type code block, and the data type code block or end type code block located in the packet gap can be modified back to Ordered block type, which can ensure that the ordered set type block can be transmitted through the transmission network, and can also ensure that the receiving device reliably recognizes the ordered set type block, which can further improve communication. Accuracy.
  • the code stream of the first rate mode may be an Ethernet signal (for example, a high-speed Ethernet signal) transmitted in a transmission network (for example, a FlexE network) and is physically encoded in a layer PCS process (for example, Code block stream (or bit code block stream or bit stream).
  • a transmission network for example, a FlexE network
  • a layer PCS process for example, Code block stream (or bit code block stream or bit stream).
  • the code stream of the second rate mode may be processed in a PCS in an Ethernet signal (for example, a low-to-medium-speed Ethernet signal) transmitted before a client device and a transmission device (for example, an ingress device or an egress device of a transmission network).
  • Ethernet signal for example, a low-to-medium-speed Ethernet signal
  • transmission device for example, an ingress device or an egress device of a transmission network.
  • Code block stream (or bit code block stream or bit stream).
  • the code block stream in the first rate mode sent by the sending device may be generated after the sending device performs processing such as transcoding on the code block stream in the second rate mode.
  • the receiving device may be an egress device transmitting a code block stream (or an Ethernet signal including the code block stream of the first rate mode) for the first rate mode in the network. That is, the Ethernet signal flows into the destination network of the Ethernet signal (including the destination client device of the Ethernet signal) from the transmission network via the egress device.
  • the sending device may be an entry device transmitting a code block stream (or an Ethernet signal including a code block stream of the first rate mode) for the first rate mode in the network. That is, the Ethernet signal flows into the transmission network from the source network of the Ethernet signal (including the source client device of the Ethernet signal) via the entry device.
  • the rate corresponding to the second rate mode is less than or equal to the rate corresponding to the first rate mode.
  • the rate corresponding to the second rate mode is less than or equal to the rate corresponding to the first rate mode
  • the signal of the second rate mode as the signal of the high speed mode can be composed of the signal including the first rate mode in The signals in one or more low-speed modes are aggregated.
  • the rate corresponding to the second rate mode is less than or equal to the rate corresponding to the first rate mode
  • the number of time slots that the signal of the second rate mode can include is greater than that of the signal of the first rate mode. The number of time slots.
  • the first rate mode may include a 40GBASE-R mode, a 100GBASE-R mode, a 200GBASE-R mode, or a 400GBASE-R mode.
  • the transmission network may include Ethernet physical links in 40GBASE-R mode, 100GBASE-R mode, 200GBASE-R mode, or 400GBASE-R mode, or the transmission network may support rates of 40Gbps, 100Gbps, 200Gbps, or 400Gbps Ethernet physical interface mode.
  • the transmission equipment in the transmission network performs Ethernet signal forwarding based on 40GBASE-R mode, 100GBASE-R mode, 200GBASE-R mode, or 400GBASE-R mode.
  • the number of transmissions of the code stream in the first rate mode may be 40 Gbps, 100 Gbps, 200 Gbps, or 400 Gbps.
  • the Ethernet signal including the code block stream in the first rate mode may be an Ethernet signal in a 40GBASE-R mode, an Ethernet signal in a 100GBASE-R mode, an Ethernet signal in a 200GBASE-R mode, or an Ethernet signal in a 400GBASE-R mode. Ethernet signals.
  • the second rate mode may include a 5GBASE-R mode, a 10GBASE-R mode, or a 25GBASE-R mode.
  • the link between the client device and the ingress or egress device of the transport network may include an Ethernet physical link in 5GBASE-R mode, 10GBASE-R mode, or 25GBASE-R mode, or the client device may Supports Ethernet physical interface modes at 5Gbps, 10Gbps, or 25Gbps.
  • the client device and the ingress or egress device of the transmission network forward Ethernet signals based on the 5GBASE-R mode, 10GBASE-R mode, or 25GBASE-R mode.
  • the transmission amount of the code block stream in the second rate mode may be 5 Gbps, 10 Gbps, or 25 Gbps.
  • the Ethernet signal including the code block stream in the second rate mode may be a signal in a 5GBASE-R mode, a signal in a 10GBASE-R mode, or a signal in a 25GBASE-R mode.
  • the code blocks in the code block stream may be 64B / 66B code blocks, or may be any M-bit / N-bit code block, where M is less than or equal to N.
  • the code block of the ordered set type may also be called an O code block.
  • the O code block may include a code block whose information carried in the code block type field is 0x2d.
  • the O-code block may include a code block whose information carried in the code block type field is 0x55.
  • the bit carried in the synchronization header field of the O-code block is 10.
  • the information carried in the code block type field of the code block of the ordered set type is modified to code block type information corresponding to the end type.
  • the T code block may include a code block whose information carried in the code block type field is at least one of the following information:
  • the method includes: the sending device modifies information carried in a code block type field of an ordered set type code block from 0x2d or 0x55 to one of 0x87, 0x99, 0xAA, 0xB4, 0xCC, 0xD2, 0xE1, 0xFF .
  • the sending device determines the code block stream of the first rate mode according to the code block stream of the second rate mode of the multiple code blocks, including: the sending device converts the first ordered set type according to the mapping relationship.
  • the information carried in the code block type field of the code block is modified to the information corresponding to the first end type.
  • the mapping relationship is used to indicate a one-to-one mapping relationship between at least two end types and at least two ordered set types.
  • the first ordered set type corresponds to the first ending type, and the first ordered set type is any one of the at least two ordered set types.
  • an O code block whose information carried in the code block type field is 0x2d may correspond to a T code block whose information carried in the code block type field is 0xE1.
  • an O code block with information carried in the code block type field of 0x55 may correspond to a T code block with information carried in the code block type field of 0xFF.
  • bit carried in the synchronization header field of the T code block is 10.
  • the information carried in the synchronization header field of the code block of the ordered set type is modified to the synchronization header information corresponding to the data type.
  • the method includes: the receiving device modifies information carried in a synchronization header field of a code block of an ordered set type into synchronization header information corresponding to the data type.
  • This data type code block may also be referred to as a data (D, D) code block.
  • the bit carried in the synchronization header field of the D code block is 01.
  • the receiving device modifies the information carried in the synchronization header field of the code block of the ordered set type to the synchronization header information corresponding to the data type includes: the receiving device changes the synchronization header of the code block of the ordered set type.
  • the information carried in the field was changed from 10 to 01.
  • the packet gap IPG can also be called a frame gap, which refers to the transmission time interval between two Ethernet data packets.
  • Each data packet includes multiple code blocks.
  • the first code block of a data packet may be an S code block, and the last code block of a data packet may be a T code block.
  • a communication device includes a unit for performing each step of the method in the first or second aspect and the implementations thereof.
  • the communication device is a communication chip
  • the communication chip may include an input circuit or interface for transmitting information or data, and an output circuit or interface for receiving information or data.
  • the communication device is a communication device (for example, an entry device or an exit device), and the communication chip may include a transmitter for transmitting information or data, and a receiver for receiving information or data.
  • a communication device including a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory, so that the communication device executes the first aspect or any possible implementation manner of the first aspect Methods.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory is separately provided from the processor.
  • the communication device may include a coding device.
  • a communication device including a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory, so that the communication device executes the second aspect or any possible implementation manner of the second aspect Methods.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory is separately provided from the processor.
  • the communication device may include a decoding device.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes any one of the first aspect to the second aspect and any possible implementation manner of the first aspect to the second aspect.
  • the processor may be a chip
  • the input circuit may be an input pin
  • the output circuit may be an output pin
  • the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • An input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • a signal output by the output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter
  • the circuits may be the same circuit, which are used as input circuits and output circuits respectively at different times.
  • the embodiments of the present application do not limit specific implementations of the processor and various circuits.
  • a processing device including: a memory and a processor.
  • the processor is configured to read an instruction stored in the memory, and can receive a signal through a receiver and transmit a signal through a transmitter to execute any one of the first aspect to the second aspect and the first aspect to the second aspect.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory is separately provided from the processor.
  • the memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated on the same chip as the processor, or may be separately set in different On the chip, the embodiment of the present application does not limit the type of the memory and the way of setting the memory and the processor.
  • ROM read-only memory
  • a chip including a processor and a memory, where the memory is used to store a computer program, the processor is used to call and run the computer program from the memory, and the computer program is used to implement the first aspect to the second Aspect and the method in any one of the possible implementation manners from the first aspect to the second aspect.
  • a computer program product includes a computer program (also referred to as code or instructions), and when the computer program is executed, causes a computer to execute the first aspect to the first aspect.
  • a computer-readable medium stores a computer program (also referred to as code, or instructions), which when executed on a computer, causes the computer to execute the first aspect to the first aspect.
  • a computer program also referred to as code, or instructions
  • the sending device can modify the code blocks of the ordered set type into data type code blocks or end type code blocks that can be recognized by the transmission network. Therefore, the receiving device can determine that the data type code block or the end type code block located in the packet gap is modified based on the code block of the ordered set type, and can further determine the data type code block or end type located in the packet gap.
  • the code block of the order set is modified back to the code block of the ordered set type, thereby not only ensuring that the code block of the ordered set type can be transmitted through the transmission network, but also ensuring that the receiving device can reliably identify the code block of the ordered set type Furthermore, the accuracy of communication can be improved.
  • FIG. 1 is a schematic diagram of an example of a communication system of the present application.
  • FIG. 2 is a schematic diagram of an example of a transmission network of the present application.
  • FIG. 3 is a diagram showing an example of an encoding format used by a low-to-medium-speed Ethernet interface.
  • FIG. 4 is a diagram showing an example of a code stream of an Ethernet signal.
  • FIG. 5 is a diagram showing an example of a coding format used by a high-speed Ethernet interface.
  • FIG. 6 is a schematic interaction diagram of an example of a transmission process of an Ethernet signal of the present application.
  • FIG. 7 is a schematic diagram of an example of a code block stream structure of a low-to-medium-speed Ethernet signal of the present application.
  • FIG. 8 is a schematic diagram of an example of a change of a 0x2d code block in the modification process of the present application.
  • FIG. 9 is a schematic diagram of an example of a change of a 0x55 code block in a modification process of the present application.
  • FIG. 10 is a diagram illustrating an example of a modified code block stream structure.
  • FIG. 11 is a schematic diagram of another example of changes of the 0x2d code block in the modification process of the present application.
  • FIG. 12 is a schematic diagram of another example of changes in the 0x2d code block of the present application during modification.
  • FIG. 13 is a schematic diagram of another example of changes in the 0x55 code block of the present application during modification.
  • FIG. 14 is a schematic diagram of another example of a modified code block stream structure.
  • FIG. 15 is a schematic diagram of an example of a process in which an egress PE device determines a frame gap.
  • 16 is a schematic diagram of another example of a process in which an egress PE device determines a frame gap.
  • FIG. 17 is a schematic diagram of an example of a change of a D code block or a T code block located in a frame gap in a recovery process of the present application.
  • FIG. 18 is a schematic diagram of another example of changes in a T-code block located in a frame gap during a recovery process of the present application.
  • FIG. 19 is a schematic diagram of another example of a change of a T-code block located in a frame gap in a recovery process of the present application.
  • FIG. 20 is a schematic diagram of another example of changes in a T-code block located in a frame gap during a recovery process of the present application.
  • FIG. 21 is a schematic diagram of an apparatus for transmitting a code block stream according to the present application.
  • 22 is a schematic diagram of an apparatus for receiving a code block stream according to the present application.
  • FIG. 23 is a schematic configuration diagram of an example of a transmission device of the present application.
  • FIG. 1 is a schematic diagram showing an example of the Ethernet system 100 of the present application.
  • the communication system includes at least three client devices.
  • the communication system may include multiple client devices 110.
  • the multiple client devices 110 may communicate with each other through a transmission network (also referred to as a forwarding network).
  • a transmission network also referred to as a forwarding network
  • the transmission network may be, for example, an optical communication network.
  • the transmission network may include a plurality of transmission devices 120.
  • each client device 110 may be communicatively connected with one or more transmission devices 120.
  • FIG. 2 is a schematic diagram showing an example of a configuration of a transmission network.
  • the transmission network may include a network edge (PE) device and a network (P) device.
  • PE network edge
  • P network
  • the P device is configured with a network-side interface (NNI).
  • NNI network-side interface
  • the NNI interface is used to transmit data conforming to the communication protocol of the transmission network.
  • the NNI interface may include a common Ethernet interface (for example, a 100GBASE-R mode interface), or the NNI interface may include a FlexE interface.
  • the PE device is also provided with a user-side interface (UNI).
  • UNI user-side interface
  • the UNI interface is used for data transmission between PE equipment and customer equipment.
  • the PE device connected to the source client device of the Ethernet signal may be referred to as an entry device (or ingress transmission device) for the Ethernet signal, and a destination client device for the Ethernet signal.
  • the connected PE device may be called an egress device (or an egress transmission device) for the Ethernet signal.
  • the source client device When the source client device sends a signal to the destination client device, the source client device can generate a signal and transmit the signal to a transmission device that is in communication with the source client device, so that the transmission network can route (or, say, forward) the signal to the The target customer device for the signal.
  • the ingress transmission device for the source client device in the transmission network may also process the signal (for example, forwarding processing, or encapsulation processing) to convert the signal into a signal that can be transmitted in the transmission network, and The signal is transmitted to other transmission devices in the transmission network for transmitting the signal to the destination receiving device (for example, an exit transmission device for the target client device).
  • the signal for example, forwarding processing, or encapsulation processing
  • the transmission device can also receive signals from other transmission devices or client devices that need to be sent to the client device that is communicatively connected to it, and can process the signals (for example, transcoding processing, or decapsulation processing) to The signal is converted into a signal that can be recognized by the client device, and the processed signal is transmitted to the client device, so that the client device can analyze the received signal to obtain data carried in the signal.
  • signals for example, transcoding processing, or decapsulation processing
  • signals transmitted between any two client devices may be processed and forwarded by one transmission device, or may be processed and forwarded by multiple transmission devices, which is not particularly limited in this application.
  • FIG. 1 the number of client devices and transmission devices shown in FIG. 1 is only an exemplary description, and the present application is not particularly limited.
  • the client device may be, for example, a client device such as a personal computer, and the client device can communicate via a medium such as Ethernet or optical fiber.
  • the client device may also be a network device, and the network device may be a server that provides various services for the user device, for example, a software-defined network (SDN) server, a web server, and a file.
  • SDN software-defined network
  • FTP File transfer protocol
  • enterprise critical application server and other mission-critical servers for example, servers providing firewall services
  • SPU service processing single board
  • CT field of communication
  • the transmission device may be a device such as a gateway device, a switch, or a router.
  • the client device may be a signal transmitting end or a signal receiving end.
  • the client device at the sending end can generate a client Ethernet signal that can be recognized by the receiving end Ethernet device according to the Ethernet protocol.
  • the sending-end client device may send the client Ethernet signal to an ingress transfer device in a transmission network that is communicatively connected with the sending-end client device.
  • the ingress transmission device can encapsulate the customer's Ethernet signal into a forwarded Ethernet signal that can be recognized by the transmission device in the transmission network according to the Ethernet protocol.
  • the transmission network routes the forwarded Ethernet signal to an egress transmission device that is communicatively connected to the receiving client device.
  • the egress transmission device can decapsulate the forwarded Ethernet signal to restore the customer Ethernet signal and send it to the customer device.
  • the client Ethernet signal may be a low-to-medium-speed Ethernet signal, or the interface mode of the client Ethernet signal may be a 5GBASE-R mode, a 10GBASE-R mode, or a 25GBASE-R mode.
  • the low-to-medium-speed Ethernet signal may be composed of 64-bit (bit, B) / 66B code blocks of the low-to-medium-speed Ethernet.
  • the 64B / 66B code block of the low-to-medium-speed Ethernet may include a 2-bit sync header field and a 8-byte (ie 64-bit) code block payload.
  • the 64B / 66B code block of the low-to-medium-speed Ethernet may include a data code block and a control code block.
  • the control code block may also include an ordered set (O) type code block, referred to as O code block, a started type code block, referred to as an S code block, and a terminated type code block, referred to as T Code blocks.
  • O code block ordered set
  • S code block started type code block
  • T Code blocks terminated type code block
  • the information (specifically, a 2-bit character) carried in the synchronization field of the control code block may include 10.
  • the code block load in the control code block may include a 1-byte code block type field.
  • a code block may include a 2-bit synchronization header field, an 8-bit (1 byte) code block type field, and a 56-bit (7 byte) payload field (payload). field).
  • FIG. 3 is a schematic diagram showing an example of an encoding format of a 64B / 66B code block of the low-to-medium-speed Ethernet.
  • the information (specifically, hexadecimal characters) carried in the code block type field of the O code block may include, but is not limited to, 0x2d and 0x55.
  • a code block whose information carried in the code block type field is 0x2d is referred to as a 0x2d code block
  • a code block whose information carried in the code block type field is 0x55 is called a 0x55 code block.
  • the encoding format of the 64B / 66B code block of the low-to-medium-speed Ethernet shown in FIG. 3 is only an exemplary description, and this application is not limited thereto. In the prior art, other codes that can The coding formats of the blocks all fall within the protection scope of the present application, for example, error code blocks, idle code blocks, and low power idle (LPI) code blocks.
  • LPI low power idle
  • the encoding process of the 64B / 66B code blocks of the low-to-medium-speed Ethernet can be performed in the physical encoding sublayer (PCS) entity of the client device at the transmitting end.
  • PCS physical encoding sublayer
  • the physical coding sublayer is located between a coordination sublayer (RS) and a physical medium access sublayer (PMAS).
  • RS coordination sublayer
  • PMAS physical medium access sublayer
  • the physical coding sublayer is used to map the well-defined Ethernet MAC functions to the existing coding and physical layer signal system functions.
  • the physical coding sublayer is used for line coding and cyclic redundancy check (CRC) check coding.
  • the decoding process of the 64B / 66B code blocks of the low-to-medium-speed Ethernet can be performed in the physical encoding sublayer entity of the receiving client device.
  • the Ethernet signal formed by the 64B / 66B code blocks of the low-to-medium-speed Ethernet may include a plurality of packets.
  • FIG. 4 shows an example of an Ethernet code stream having the above structure.
  • each data packet may include one S code block, multiple D code blocks, and one T code block.
  • the S code block is used to indicate the start of a data packet
  • the T code block is used to indicate the end of a data packet.
  • this time interval may also be referred to as a packet gap or a frame gap.
  • FIG. 4 it can be used to transmit O code blocks and the like between the packet gaps.
  • the encoding and decoding process of the client Ethernet signal may be similar to the prior art.
  • detailed description is omitted.
  • High-speed Ethernet signals transmitted in a transport network can also be referred to as FlexE clients.
  • the FlexEClient is used to encapsulate the user's data and transmit the data according to the data transmission method defined by the FlexE interface.
  • a FlexEClient can carry a user's data stream.
  • the Ethernet system can divide time slots by, for example, time division multiplexing (TDM), etc., to achieve hard isolation of transmission channel bandwidth, and a service data stream can be allocated to one or more time slots In the realization of the matching of various speed services.
  • TDM time division multiplexing
  • a FlexE group can include one or more bundled physical link interfaces of the same rate (for example, 100GBASE-R, 200GBASE-R, or 400GBASE-R). Each FlexE group carries one or more FlexE instances ( Instance).
  • the forwarded Ethernet signal may be a high-speed Ethernet signal, or the interface mode of the forwarded Ethernet signal may be a 100GBASE-R mode, a 200GBASE-R mode, or a 400GBASE-R mode.
  • the FlexE instance can refer to a unit carrying a FlexEClient, and each FlexE instance can support a rate of, for example, 100Gbps.
  • the slot allocation table corresponding to the FlexE group is called a FlexE slot calendar (calendar), and the slot mapping table corresponding to a single FlexE client is called a sub-slot allocation table (sub-calendar).
  • a FlexE group's calendar consists of one or more sub-calendars, and each sub-calendar indicates how these time slots are allocated to the corresponding FlexE client.
  • a FlexE client represents a client data stream transmitted at a specified time slot (one or more time slots) on a FlexE instance on a FlexE group.
  • a FlexE group can carry multiple FlexE Clients.
  • One FlexE Client can correspond to one or more user service data streams (MAC Clients), and the FlexE thin layer (Shim) can provide data adaptation and conversion from FlexE Client to MAC Clients.
  • MAC Clients user service data streams
  • Shim FlexE thin layer
  • each physical interface can have 20 5Gb subslots, so the FlexEGroup has 20 ⁇ 4 subslots (sub- calendar).
  • the high-speed Ethernet signal may be composed of a 64-bit (bit, B) / 66B code block of the high-speed Ethernet.
  • the 64B / 66B code block of the high-speed Ethernet may include a 2-bit synchronization header field and an 8-byte code block payload.
  • the 64B / 66B code block of the high-speed Ethernet may include a data code block and a control code block.
  • the control code block may also include an O code block, an S code block, and a T code block.
  • the information (specifically, a 2-bit character) carried in the synchronization field of the control code block may include 10.
  • the code block load in the control code block may include a 1-byte code block type field.
  • FIG. 5 is a schematic diagram showing an example of an encoding format of a 64B / 66B code block of the high-speed Ethernet.
  • the information (specifically, hexadecimal characters) carried in the code block type field of the O code block may include, but is not limited to, 0x4B.
  • the encoding format of the 64B / 66B code block of the high-speed Ethernet shown in FIG. 5 is only an exemplary description, and the present application is not limited thereto. In the prior art, other code blocks capable of being used in the low-speed Ethernet The encoding formats all fall within the protection scope of this application, for example, error code blocks, idle code blocks, and low energy idle code blocks.
  • the conversion (or encapsulation) process from 64B / 66B code blocks of low-to-medium-speed Ethernet to 64B / 66B code blocks of high-speed Ethernet, or the encapsulation process from low-to-medium-speed Ethernet signals to high-speed Ethernet signals can The physical encoding sublayer entity of the ingress transmission device is performed.
  • the encapsulation process can be performed in the physical encoding sublayer entity of the egress transmission device.
  • the Ethernet signal composed of the 64B / 66B code blocks of the high-speed Ethernet may include multiple data packets.
  • each data packet may include one S code block, multiple D code blocks, and one T code block.
  • the S code block is used to indicate the start of a data packet
  • the T code block is used to indicate the end of a data packet.
  • this time interval may also be referred to as a packet gap or a frame gap. As shown in FIG. 4, it can be used to transmit O code blocks and the like between the packet gaps.
  • O-code blocks in the encoding format of low-to-medium-speed Ethernet signals such as 0x2d or 0x55 code blocks, do not exist at high speed.
  • the encoding format of Ethernet signals (or, in other words, forwarding Ethernet signals).
  • a transmission error may result because the transmitting device cannot identify the 0x2d code block or 0x55 code block.
  • this application can adopt the following processing procedures to avoid transmission errors.
  • FIG. 6 shows a schematic interaction diagram of an example of a transmission process 200 of an Ethernet signal of the present application.
  • the client device #A can generate the Ethernet signal #A.
  • the Ethernet signal #A may be a low-to-medium-speed Ethernet signal, that is, the interface mode of the Ethernet signal #A may be a 5GBASE-R mode, a 10GBASE-R mode, or a 25GBASE-R mode.
  • FIG. 7 shows an example of a code block stream structure of the PCS layer of the Ethernet signal #A.
  • the code block stream of the PCS layer of the Ethernet signal #A may include multiple data packets.
  • there is a packet gap between two adjacent data packets in the transmission order and there may be, for example, an idle code block, a 0x2d code block (as shown by “O 1 ” in FIG. 7), and 0x4B in the packet gap.
  • Code blocks shown as “O 2 ” in FIG. 7
  • 0x55 code blocks shown as “O 3 ” in FIG. 7
  • other O code blocks and idle code blocks shown as “I” in FIG. 7).
  • code block stream structure shown in FIG. 7 is only an exemplary description, and this application is not limited thereto.
  • code block stream structure shown in FIG. 7 is only an exemplary description, and this application is not limited thereto.
  • only one of a 0x2d code block and a 0x55 code block may exist in the packet gap.
  • the code block to be modified involved in this application does not involve the 0x4B code block.
  • Ethernet signal #A may be similar to the prior art.
  • a detailed description is omitted.
  • the client device #A may send the Ethernet signal #A to a PE device that is in communication with the client device #A.
  • the PE device is referred to as: entrance PE device #B.
  • the ingress PE device #B may modify the Ethernet signal #A to replace the code block (ie, the 0x2d code) in the Ethernet signal #A that cannot be recognized by the transmission network (specifically, each transmission device). Block and / or 0x55 code block) into code blocks that can be recognized by the transport network.
  • the code block ie, the 0x2d code
  • Block and / or 0x55 code block into code blocks that can be recognized by the transport network.
  • the ingress PE device #B may modify the 0x2d code block into a D code block.
  • FIG. 8 is a schematic diagram showing changes in a 0x2d code block during a modification of the first manner.
  • the ingress PE device #B can modify the information carried in the synchronization header field of the 0x2d code block from the information corresponding to the control type code block (for example, “10”) to the information corresponding to the data type code block (for example, "01").
  • the ingress PE device #B may modify the 0x55 code block into a D code block.
  • FIG. 9 is a schematic diagram showing a change of a 0x55 code block in a modification process of the first manner.
  • the ingress PE device #B can modify the information carried in the synchronization header field of the 0x55 code block from the information corresponding to the control type code block (for example, "10") to the information corresponding to the data type code block (for example, "01").
  • FIG. 10 shows a change of a code block stream of the PCS layer based on the Ethernet signal shown in FIG. 7 after being modified according to the method 1.
  • 0x2d code blocks and / or 0x55 code blocks in the code block stream of the PCS layer of the low-speed Ethernet signal are converted into D code blocks.
  • the ingress PE device #B may modify the 0x2d code block into a T code block.
  • the ingress PE device #B can modify the information carried in the code block type field of the 0x2d code block from the information corresponding to the 0x2d code block (for example, “0x2d”) to the information corresponding to the T code block (for example, “0x87” , “0x99”, “0xAA”, “0xB4", "0xCC”, “0xD2", “0xE1”, “0xFF”).
  • the ingress PE device #B may modify the 0x55 code block into a T code block.
  • the entry PE device #B may modify the information carried in the code block type field of the 0x55 code block from the information corresponding to the 0x55 code block (for example, "0x55") to the information corresponding to the T code block (for example, “0x87” , “0x99", “0xAA”, “0xB4", "0xCC”, “0xD2”, “0xE1", “0xFF”).
  • the egress PE device may not be able to determine whether T code block # 1 in the received Ethernet signal should be restored to 0x2d code block or 0x55 code.
  • the egress PE device may be a PE device that is communicatively connected to the destination client device of the Ethernet signal #A.
  • the PE device is referred to as: egress PE device #C.
  • mapping relationship #A may be stored in advance in the egress PE device #C and the ingress PE device #B.
  • the mapping relationship #A may be used to indicate a correspondence between a 0x2d code block and a T code block (denoted as: T code block #a), and the mapping relationship #A may be used to indicate 0x55 and another T code block ( Let it be written: the corresponding relationship of T code block #b).
  • the ingress PE device #B may modify the information carried in the code block type field of the 0x2d code block from the information corresponding to the 0x2d code block (for example, "0x2d") to the code of the T code block #a according to the indication of the mapping relationship #A.
  • Information corresponding to the block type field may be modified from the information corresponding to the 0x2d code block (for example, "0x2d") to the code of the T code block #a according to the indication of the mapping relationship #A.
  • Information corresponding to the block type field for example, "0x2d"
  • the T code block #a may be a T6 code block, that is, the T code block #a may be that the information corresponding to the code block type field is "0xE1".
  • T code block #a may be any code block from T0 to T7, as long as the T The code block #a and the T code block #b may be different.
  • FIG. 11 is a schematic diagram showing changes of a 0x2d code block in a modification process of the second manner.
  • the ingress PE device #B may modify the information carried in the code block type field of the 0x2d code block from "0x2d" to "0xE1".
  • the ingress PE device #B may also shift the information carried in the “O4” byte in the 0x2d code block to the “D0” byte in the T6 code block.
  • the information carried in the "D5" byte in the 0x2d code block can be shifted to the "D1" byte in the T6 code block, and the information carried in the "D6" byte in the 0x2d code block can be shifted From the bit to the "D2" byte in the T6 code block, the information carried in the "D7" byte in the 0x2d code block can be shifted to the "D3" byte in the T6 code block.
  • the entry PE device #B may also fill in predetermined bits, such as "0”, in the "D4", “D5", “D6", and “D7” bytes in the T6 code block generated based on the above modification.
  • the information carried in the "O4" byte in the 0x2d code block since the information carried in the "O4" byte in the 0x2d code block includes less than one byte, the information carried in the "O4" byte in the 0x2d code block only occupies the T6 code block. Some bits in the "D0" byte; information carried in the "D5" byte in the 0x2d code block occupies another part of the “D0” byte in the T6 code block and some of the bits in the "D1" byte ; The information carried in the "D6" byte in the 0x2d code block occupies another part of the bits in the "D1” byte and part of the "D2" byte in the T6 code block; the "D7" in the 0x2d code block The information carried in the byte occupies another part of the "D2" byte in the T6 code block and part of the "D3" byte.
  • another part of the "D3" byte in the T6 code block (that is, a bit that is not filled with the information carried in the "D7" byte in the 0x2d code block) may be filled with a prescribed bit, such as "0".
  • the ingress PE device #B may also add the “O4” byte, “D5” byte, “D6” byte, and “D7” in the 0x2d code block.
  • the information carried in the "" byte is shifted to the "D0” byte, "D1” byte, “D2” byte, and "D3” byte in the T6 code block, and between the bits after the shift,
  • the positional relationship is the same as the positional relationship between the bits before the shift.
  • the T code block #b may be a T7 code block, that is, the T code block #b may be a code block type field with the information "0xFF".
  • T code block #b may be any code block from T0 to T7, as long as the T The code block #a and the T code block #b may be different.
  • FIG. 13 is a schematic diagram showing a change of a 0x55 code block in a modification process of the second manner.
  • the ingress PE device #B may modify the information carried in the code block type field of the 0x2d code block from "0x55" to "0xFF".
  • mapping relationship #A may be determined by a management device in the transmission network and delivered to each transmission device, or the above-mentioned mapping relationship #A may be predetermined by a communication system or a communication protocol, or The above-mentioned mapping relationship #A may be determined through negotiation between the ingress PE and the egress PE, or the above-mentioned mapping relationship #A may be entered by the user or the administrator into the ingress PE and the egress PE, or the above-mentioned mapping relationship #A It may be configured in the ingress PE and egress PE by a manufacturer or an operator, and this application is not particularly limited.
  • FIG. 14 shows the change of the code block stream of the PCS layer based on the Ethernet signal shown in FIG. 7 after the modification of the method 2.
  • 0x2d code blocks and / or 0x55 code blocks in the code block stream of the PCS layer of the low-speed Ethernet signal are converted into T code blocks.
  • the ingress PE device #B may modify the 0x2d code block into a D code block.
  • the ingress PE device #B may modify the 0x55 code block into a T code block.
  • the ingress PE device #B may modify the 0x2d code block into a T code block.
  • the ingress PE device #B may modify the 0x55 code block into a D code block.
  • the modification process for each code block may be similar to the process described in the method 1 or the method 2.
  • detailed descriptions thereof are omitted.
  • the recovery method adopted by the exit PE device #C needs to be modified from that adopted by the entry PE device #B.
  • Corresponding methods for example, the recovery method and the modification method are processed inversely to each other) to ensure the accuracy of the restoration.
  • the modification adopted by the entry device #A may be specified in advance by the communication system or communication protocol, or the modification adopted by the entry device #A may be adopted by the exit PE device #C and the entry PE device.
  • #B is determined through negotiation, or the modification method adopted by the entry device #A may be determined by the management device of the transmission network and delivered to the entry PE device #B, and the management device may issue the recovery method corresponding to the modification method to Exit PE equipment #C.
  • the ingress PE device #B can generate a high-speed Ethernet signal (for example, an Ethernet signal supported by FlexEClient) in the transmission network according to the modified Ethernet signal #A.
  • a high-speed Ethernet signal for example, an Ethernet signal supported by FlexEClient
  • It is Ethernet signal #B.
  • the ingress PE device #B may send the Ethernet signal #B to the egress PE device #C via the transmission network.
  • the process may be similar to that in the prior art, and detailed descriptions are omitted here to avoid redundant descriptions.
  • the egress PE device #C can determine the code block modified by the ingress PE device #B from the code block stream of the PCS layer of the received Ethernet signal #B.
  • code block #A In the following, for ease of understanding and distinction, note : Code block #A.
  • the PE device #C is exported.
  • the code block #A may be determined based on the frame gap of the code block stream of the PCS layer of the Ethernet signal #B.
  • the code block #A may include only a D code block (ie, case 1) or the code block #A may include a T code block (ie, case 2).
  • a method for determining a frame gap is different. Different, in the following, the process of determining the frame gap by the exit PE device #C in the above case is described in detail.
  • the code block #A may include only the D code block. It can be understood that the entry PE device #B has modified both the 0x2d code block or the 0x55 code block into the D code block. The code blocks are all modified to T code blocks.
  • the T code blocks in the code block stream of the PCS layer of the Ethernet signal #B are all T code blocks in the code block stream of the PCS layer of the Ethernet signal #A. That is, each T code block in the code block stream of the PCS layer of the Ethernet signal #B may indicate the end of the data packet to which it belongs. In other words, each T code block in the code block stream of the PCS layer of the Ethernet signal #B can be determined to start at the packet gap that follows it.
  • the egress PE device #C may determine the packet gap in the code block stream of the PCS layer of the Ethernet signal #B according to the T code block and the S code block in the code block stream of the PCS layer of the Ethernet signal #B, that is, , Any packet gap (for example, packet gap # 1) satisfies the following conditions:
  • the packet gap # 1 is located between the data packet # 1 and the data packet # 2 adjacent in the transmission sequence, or the packet gap # 1 is located between the T code block of the data packet # 1 and the S code of the data packet # 2. Between blocks.
  • the egress PE device #C can determine the D code block received in the packet gap as the code block #A.
  • the egress PE device #C can determine the D code block received later as the code block #A until the S code block is received.
  • FIG. 15 shows an example of a processing procedure of the exit PE device #C.
  • IPG information may be stored in the egress PE device #C, and the IPG information may be used to determine a packet gap.
  • the PE device #A may set the value of the IPG information to a value indicating that the current period belongs to a packet gap, for example, "1".
  • the PE device #A may set the value of the IPG information to a value indicating that the current period does not belong to the packet gap, for example, "0".
  • the egress PE device #C may determine the D code block received during the value of the IPG information as "1" as the code block #A.
  • the value of the IPG information can be set to "1", so that there is a packet gap before the first data packet of the Ethernet signal #A, In the case where an O-code block exists in the packet gap, it can be ensured that the exit PE device #C recognizes the D-code block modified based on the O-code block.
  • the code block #A may include a T code block. It may be understood that the code block #A may include only a T code block. That is, both the 0x2d code block and the 0x55 code block are modified into T code blocks for the ingress PE device #B.
  • the code block #A may include T, which may be understood as: the code block #A may include both a T code block and a D code block. That is, entry PE device #B changes one of the 0x2d code block or 0x55 code block to a T code block, and entry PE device #B changes the other of the 0x2d code block or 0x55 code block to a D code block.
  • the T code block in the code block stream of the PCS layer of the Ethernet signal #B may include the T code block in the code block stream of the PCS layer of the Ethernet signal #A, and the T code generated based on the O code block.
  • part of the T code blocks in the code block stream of the PCS layer of the Ethernet signal #B may indicate the end of the data packet to which it belongs, and the other part of the T code blocks may not indicate the end of the data packet.
  • part of the T code blocks in the code block stream of the PCS layer of the Ethernet signal #B can determine the start of the subsequent packet gap, and the other part of the T code block cannot indicate the start of the packet gap.
  • the egress PE device #C may determine the packet gap in the code block stream of the PCS layer of the Ethernet signal #B according to the T code block and the S code block in the code block stream of the PCS layer of the Ethernet signal #B, that is, , Any packet gap (for example, packet gap # 1) satisfies the following conditions:
  • the packet gap # 1 is located between the data packet # 1 and the data packet # 2 adjacent in the transmission sequence, or the packet gap # 1 is located between the T code block of the data packet # 1 and the S code of the data packet # 2. Between blocks.
  • the T code block of the data packet # 1 is the first T code block after the S code block of the data packet # 2.
  • the egress PE device #C can determine the D code block or T code block received in the packet gap as the code block #A.
  • the export PE device #C may determine the first T code block after the S code block, and determine the T code block to receive the D code block or T code block received later. Is code block #A until the S code block is received.
  • FIG. 16 shows an example of a processing procedure of the exit PE device #C.
  • IPG information may be stored in the egress PE device #C, and the IPG information may be used to determine a packet gap.
  • the PE device #A may set the value of the IPG information to a value indicating that the current period does not belong to the packet gap, for example, "0".
  • the PE device #A receives the T code block, if the value of the IPG information is “0”, the value of the IPG information may be set to a value indicating that the current period belongs to a packet gap, such as “1”.
  • the value of the IPG information may be set to a value indicating that the current period belongs to a packet gap, such as "1".
  • the egress PE device #C may determine the D code block or T code block received during the value of the IPG information as "1" as the code block #A.
  • the value of the IPG information can be set to "1", so that there is a packet gap before the first data packet of the Ethernet signal #A, In the case where an O-code block exists in the packet gap, it can be ensured that the exit PE device #C recognizes the D-code block modified based on the O-code block.
  • the exit PE device #C performs recovery processing on the code block #A to restore the code block #A to its corresponding code block (ie, 0x2d code block and / or 0x55 code block) in the Ethernet signal #A, .
  • the egress PE device #C may modify the code block #A to a 0x2d code block or a 0x55 code block.
  • FIG. 17 is a schematic diagram showing a change of a code block #A during a modification of the method a.
  • the egress PE device #C may modify the information carried in the synchronization header field of the code block #A from information corresponding to the data type code block (for example, "01") to information corresponding to the control type code block (for example, , "10").
  • the code block #A may be a 0x2d code block or a 0x55 code block, which is not particularly limited in this application.
  • the egress PE device #C can modify the code block #A to a 0x2d code block or 0x55
  • the egress PE device #C can change the information carried in the code block type field of the code block #A from the information corresponding to the T code block (for example, "0x87”, “0x99", “0xAA”, “0xB4", "0xCC”, " Any information of 0xD2, 0xE1, and 0xFF) is modified to information corresponding to a 0x2d code block (for example, "0x2d"), or information corresponding to a 0x55 code block (for example, "0x55").
  • the export PE device #C may not be able to determine that the information corresponding to the T code block is modified to 0x2d
  • the information corresponding to the code block is also the information corresponding to the 0x55 code block.
  • mapping relationship #A may be stored in advance in the egress PE device #C and the ingress PE device #B.
  • the mapping relationship #A may be used to indicate a correspondence between a 0x2d code block and a T code block (denoted as: T code block #a), and the mapping relationship #A may be used to indicate 0x55 and another T code block ( Let it be written: the corresponding relationship of T code block #b).
  • the T code block #a may be a T6 code block, that is, the T code block #a may be that the information corresponding to the code block type field is "0xE1".
  • T code block #a may be any code block from T0 to T7, as long as the T The code block #a and the T code block #b may be different.
  • the egress PE device #C may modify the information carried in the code block type field of the T code block #a to the information corresponding to the 0x2d code block (for example, "0x2d") according to the indication of the mapping relationship #A.
  • FIG. 18 is a schematic diagram showing a change of the T code block #a during the modification of the second method.
  • the egress PE device #C may modify the information carried in the code block type field of the 0x2d code block of the T code block #a located in the packet gap in the Ethernet signal #B from "0xE1" to "0x2d".
  • the export PE device #C may also shift the information carried in the "D0" byte in the T6 code block to the "O4" byte in the 0x2d code block ,
  • the information carried in the "D1" byte in the T6 code block can be shifted to the "D5" byte in the 0x2d code block, and the information carried in the "D2" byte in the T6 code block can be shifted From the bit to the "D6" byte in the 0x2d code block, the information carried in the "D3" byte in the T6 code block can be shifted to the "D7" byte in the 0x2d code block.
  • the egress PE device #C may also fill in the prescribed bits in the "C0”, “C1”, “C2”, and “C03" bytes in the 0x2d code block generated based on the above modification.
  • the T code block #b may be a T7 code block, that is, the T code block #b may be that the information corresponding to the code block type field is "0xFF".
  • T code block #b may be any code block from T0 to T7, as long as the T The code block #a and the T code block #b may be different.
  • FIG. 20 is a schematic diagram showing a change of a T7 code block during a modification of the method b.
  • the egress PE device #C may modify the information carried in the code block type field of the T7 code block from "0xFF" to "0x55".
  • mapping relationship #A may be determined by a management device in the transmission network and delivered to each transmission device, or the above-mentioned mapping relationship #A may be predetermined by a communication system or a communication protocol, or The above-mentioned mapping relationship #A may be determined through negotiation between the ingress PE and the egress PE, or the above-mentioned mapping relationship #A may be entered by the user or the administrator into the ingress PE and the egress PE, or the above-mentioned mapping relationship #A It may be configured in the ingress PE and egress PE by a manufacturer or an operator, and this application is not particularly limited.
  • the egress PE device #C may modify the D code block received in the packet gap to a 0x2d code block.
  • the T code block received in the packet gap is modified to a 0x55 code block.
  • the egress PE device #C may modify the D code block received in the packet gap to a 0x55 code block.
  • the T code block received in the packet gap is modified into a 0x2d code block.
  • the modification process for each code block may be similar to the process described in the method 1 or the method 2.
  • detailed descriptions thereof are omitted.
  • the recovery method adopted by the exit PE device #C needs to be modified from that adopted by the entry PE device #B.
  • Corresponding methods for example, the recovery method and the modification method are processed inversely to each other) to ensure the accuracy of the restoration.
  • the modification adopted by the entry device #A may be specified in advance by the communication system or communication protocol, or the modification adopted by the entry device #A may be adopted by the exit PE device #C and the entry PE device.
  • #B is determined through negotiation, or the modification method adopted by the entry device #A may be determined by the management device of the transmission network and delivered to the entry PE device #B, and the management device may issue the recovery method corresponding to the modification method to Exit PE equipment #C.
  • the egress PE device #C can send the signal (denoted as Ethernet signal #C) generated by the restoration process to the client device #D, so that the client device #D can obtain the bearer based on the Ethernet signal #C Information in Ethernet signal #A.
  • the conversion process of the O-code block from the low-to-medium-speed Ethernet signal to the tell Ethernet signal can be completed without losing information.
  • the above code block conversion process has a transcoding efficiency of 1: 1, no additional bit overhead is required, no bandwidth expansion is caused, and no transmission resource is wasted. It can realize that 5GE only occupies one 5G slot of FlexE, 10GE only occupies two 5G slots of FlexE, and 25GE only occupies five 5G slots of FlexE.
  • the existing PCS layer coding specifications of 10GBASE-R, 25GBASE-R, and 100GBASE-R can be fully complied with without affecting standard code block processing mechanisms (such as the IDLE-based code block adjustment mechanism).
  • the Ethernet signal from the client device can be transmitted in a transmission network based on a codeword transparent method.
  • the codeword is a binary code composed of a set of several bits.
  • the combination of codeword transparency means that the transmission network carrying a certain type of user-customer signal will not lose or tamper with any codeword information in the data stream of the user-customer signal when transmitting a data stream carrying this type of codeword.
  • FIG. 21 is a schematic diagram of a communication device 10 according to an embodiment of the present application.
  • the device 10 may be an ingress transmission device (that is, a receiving device, for example, an egress PE device) or a chip.
  • OR circuit such as a chip or circuit that can be provided in the ingress transfer device.
  • the communication device 10 may include a processing unit 11 (that is, an example of a processing unit) and a storage unit 12.
  • the storage unit 12 is configured to store instructions
  • the processing unit 11 is configured to execute the instructions stored by the storage unit 12 so that the 10 is implemented by the transmitting device (ie, the receiving device, for example, the exit PE device #C) in the method described above.
  • the transmitting device ie, the receiving device, for example, the exit PE device #C
  • the device 10 may further include an input port 13 (that is, an example of a communication unit) and an output port 14 (that is, another example of a communication unit).
  • the processing unit 11, the storage unit 12, the input port 13 and the output port 14 can communicate with each other through an internal connection path to transfer control and / or data signals.
  • the storage unit 12 is used to store a computer program, and the processing unit 11 may be used to call and run the computer program from the storage unit 12 to control the input port 13 to receive signals and control the output port 14 to send signals to complete the above method. Steps for the terminal device.
  • the storage unit 12 may be integrated in the processing unit 11, or may be provided separately from the processing unit 11.
  • the input port 13 is a receiver
  • the output port 14 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 13 is an input interface
  • the output port 14 is an output interface
  • the functions of the input port 13 and the output port 14 may be considered to be implemented through a transceiver circuit or a dedicated chip for transceiver.
  • the processing unit 11 may be implemented by a dedicated processing chip, a processing circuit, a processing unit, or a general-purpose chip.
  • a manner of using a general-purpose computer may be considered to implement the receiving device provided in the embodiment of the present application.
  • the program code that is to implement the functions of the processing unit 11, the input port 13, and the output port 14 is stored in the storage unit 12.
  • the general processing unit implements the functions of the processing unit 11, input port 13, and output port 14 by executing the codes in the storage unit 12. .
  • the input port 13 is configured to receive a code block stream of a first rate mode including a plurality of code blocks from a transmission network; and the processing unit 11 is configured to determine a target code block from the code block stream.
  • the target code block is a code block received by the receiving device within a packet gap of the code block stream, the target code block includes a first target code block, and the first target code block is a data type code block; and / or the The target code block includes a second target code block.
  • the second target code block is an end type code block.
  • the processing unit 11 is configured to modify the target code block to modify the target code block into a second rate mode. For code blocks of the set type, the rate corresponding to the second rate mode is smaller than the rate corresponding to the first rate mode.
  • the processing unit 11 is configured to determine an end position of the packet gap according to a start type code block in the code block stream, and determine a start of the packet gap according to an end type code block in the code block stream. Starting position.
  • the processing unit 11 is configured to determine a start position of the packet gap according to a first end type code block in the code block stream, where the first end type code block is located at the start in a transmission sequence. The first end type code block after the type code block.
  • the processing unit 11 is configured to modify the information carried in the synchronization header field of the first target code block to the synchronization header information corresponding to the ordered set type; and / or to modify the information of the second target code block.
  • the information carried in the code block type field is modified to the code block type information corresponding to the ordered set type.
  • the processing unit 11 is configured to modify the information carried in the code block type field of the second target code block of the first end type to the information corresponding to the first ordered set type according to the mapping relationship, where the mapping The relationship is used to indicate a one-to-one mapping relationship between at least two ending types and at least two ordered set types, the first ordered set type and the.
  • each module or unit in the device 10 listed above are only exemplary descriptions, and each module or unit in the device 10 may be used to perform the execution of the transmission device (for example, the exit PE device #C) in the above method. Each action or process is omitted here to avoid detailed description.
  • the sending device can modify the code blocks of the ordered set type to data type code blocks or end type code blocks that can be recognized by the transmission network, so that the receiving device can change
  • the data type code block or end type code block located in the packet gap is determined to be modified based on the ordered set type code block, and the data type code block or end type code block located in the packet gap can be modified back to Ordered block type, which can ensure that the ordered set type block can be transmitted through the transmission network, and can also ensure that the receiving device reliably recognizes the ordered set type block, which can further improve communication. Accuracy.
  • FIG. 22 is a schematic diagram of a communication device 30 according to an embodiment of the present application.
  • the device 30 may be a transmitting device (that is, a transmitting device, for example, the entrance PE device #B), or may be Chip or circuit, such as a chip or circuit that can be placed in a network device.
  • the device 30 may include a processing unit 31 and a storage unit 32.
  • the storage unit 32 is configured to store instructions
  • the processing unit 31 is configured to execute the instructions stored by the storage unit 32 to enable the apparatus 30 to implement the steps performed by the sending device in the foregoing method.
  • the device 30 may further include an input port 33 (that is, an example of a communication unit) and an output port 33 (that is, another example of a processing unit).
  • an input port 33 that is, an example of a communication unit
  • an output port 33 that is, another example of a processing unit.
  • processing unit 31, the storage unit 32, the input port 33 and the output port 34 can communicate with each other through an internal connection path to transfer control and / or data signals.
  • a general-purpose computer to implement the network device provided in the embodiment of the present application.
  • the program code that is to implement the functions of the processing unit 31, the input port 33, and the output port 34 is stored in a storage unit, and the general-purpose processing unit implements the functions of the processing unit 31, input port 33, and output port 34 by executing the code in the storage unit.
  • the storage unit 32 is configured to store a computer program.
  • the processing unit 31 may be configured to call and run the calculation program from the storage unit 32 to determine the first rate mode according to the code block stream of the second rate mode of the multiple code blocks.
  • Code block stream, the rate corresponding to the second rate mode is lower than the rate corresponding to the first rate mode, wherein the code block of the ordered set type in the code block stream of the second rate mode is modified to a data type code block , And / or the code block of the ordered set type in the code block stream of the second rate mode is modified to an end type code block; the output port 34 is used to send the code block stream of the first rate mode to the transmission network. .
  • the information carried in the synchronization header field of the code block of the ordered set type is modified to the synchronization header information corresponding to the data type.
  • the information carried in the code block type field of the code block of the ordered set type is modified to code block type information corresponding to the end type.
  • the processing unit 31 is configured to modify the information carried in the code block type field of the code blocks of the first ordered set type to the information corresponding to the first end type according to the mapping relationship, where the mapping relationship is used for Indicates a one-to-one mapping relationship between at least two ending types and at least two ordered set types, the first ordered set type corresponds to the first ending type, and the first ordered set type is the at least two Any of the ordered set types.
  • each module or unit in the device 30 listed above are only exemplary descriptions, and each module or unit in the device 30 may be used to perform the transmission device (that is, the sending device, for example, the entrance PE device) in the above method.
  • the transmission device that is, the sending device, for example, the entrance PE device
  • the sending device can modify the code blocks of the ordered set type to data type code blocks or end type code blocks that can be recognized by the transmission network, so that the receiving device can change
  • the data type code block or end type code block located in the packet gap is determined to be modified based on the ordered set type code block, and the data type code block or end type code block located in the packet gap can be modified back to Ordered block type, which can ensure that the ordered set type block can be transmitted through the transmission network, and can also ensure that the receiving device reliably recognizes the ordered set type block, which can further improve communication. Accuracy.
  • FIG. 23 is a schematic block diagram of an example of a transfer device (for example, an entrance transfer device or an exit transfer device) of the present application.
  • a transfer device for example, an entrance transfer device or an exit transfer device
  • the transmission device includes one or more client-side interface boards 41, a switch board 42, and one or more FlexE-side interface boards 43.
  • the client-side interface board 41 includes an external interface 411, a transcoder 413, and an internal interface 415.
  • the FlexE-side interface board 43 includes an internal interface 431, a transcoder 433, and an external interface 435.
  • the transmission device is the ingress PE device:
  • the external interface 411 is used to receive low-speed Ethernet signals (for example, signals with a rate of 5Gps, 10Gps, or 25Gps) from a client device.
  • low-speed Ethernet signals for example, signals with a rate of 5Gps, 10Gps, or 25Gps
  • the transcoder 413 is used to convert the low-speed Ethernet signal into a high-speed Ethernet signal (for example, a signal with a rate of 40 Gps, 100 Gps, 200 Gps, or 400 Gps). Specifically, the transcoder 413 is configured to convert the code blocks in the PCS layer code block stream of the low-to-medium-speed Ethernet signal into a code block stream that meets the PCS layer transmission requirements of the high-speed Ethernet signal.
  • the internal interface 415 is used to send the high-speed Ethernet signal to the switch board 42.
  • the switching board 42 is configured to forward the high-speed Ethernet signal to the FlexE-side interface board 43 capable of routing the high-speed Ethernet signal to the egress transmission device based on a preset routing rule.
  • the internal interface 431 is used to receive a high-speed Ethernet signal from the conversion board 42.
  • the external interface 435 is used to send the high-speed Ethernet signal to a transmission network, such as a FlexE network.
  • the external interface 435 is used to receive a high-speed Ethernet signal (for example, a signal at a rate of 40 Gps, 100 Gps, 200 Gps, or 400 Gps) from a transmission network, such as a FlexE network.
  • a high-speed Ethernet signal for example, a signal at a rate of 40 Gps, 100 Gps, 200 Gps, or 400 Gps
  • a transmission network such as a FlexE network.
  • the transcoder 433 is used to convert the high-speed Ethernet signal into a low-to-medium-speed Ethernet signal (for example, a signal with a rate of 5Gps, 10Gps, or 25Gps). Specifically, the transcoder 433 is configured to convert code blocks in the PCS layer code block stream of the high- and low-speed Ethernet signals into code block streams that meet the PCS layer transmission requirements of the low- and medium-speed Ethernet signals.
  • the internal interface 431 is configured to send the low-to-medium-speed Ethernet signal to the switch board 42.
  • the switching board 42 is configured to forward the low-to-medium-speed Ethernet signal to the client-side interface board 41 capable of routing the low-to-medium-speed Ethernet signal to a destination client device based on a preset routing rule.
  • the internal interface 415 is used to receive low-to-medium-speed Ethernet signals from the conversion board 42.
  • the external interface 411 is configured to send the low-to-medium-speed Ethernet signal to a destination client device.
  • the action of the client-side interface board 41 may correspond to the action of the input port 13 described above.
  • the transcoder The action of 413 may correspond to the action of the processing unit 11 described above.
  • a detailed description is omitted to avoid redundant description.
  • the repeater may modify the information carried in the synchronization header field of the code block of the ordered set type in the code block in the PCS layer code block stream of the Ethernet signal to the synchronization header information corresponding to the data type.
  • the repeater may modify the information carried in the code block type field of the code block of the ordered set type in the code blocks in the code block stream of the PCS layer of the Ethernet signal to the code block type information corresponding to the end type.
  • the forwarder may modify the information carried in the code block type field of the code block of the first ordered set type to the information corresponding to the first end type according to the mapping relationship, where the mapping relationship is used to indicate at least two end A one-to-one mapping relationship between a type and at least two sorted set types, the first sorted set type corresponds to the first ending type, and the first sorted set type is among the at least two sorted set types Any of the ordered set types.
  • the action of the FlexE-side interface board 43 may correspond to the action of the output port 34 described above.
  • the action of 433 may correspond to the action of the processing unit 31 described above.
  • a detailed description is omitted to avoid redundant description.
  • the transcoder may determine the end position of the packet gap according to the start type code block in the code block stream; the receiving device determines the start position of the packet gap according to the end type code block in the code block stream. .
  • the repeater may determine a start position of the packet gap according to a first end type code block in the code block stream, where the first end type code block is a code block located in the start type in a transmission sequence. The first end-type code block after that.
  • the transcoder may modify the information carried in the synchronization header field of the first target code block to the synchronization header information corresponding to the ordered set type.
  • the transcoder modifies the information carried in the code block type field of the second target code block to the code block type information corresponding to the ordered set type.
  • the repeater may modify the information carried in the code block type field of the second target code block of the first end type to the information corresponding to the first ordered set type according to the mapping relationship, where the mapping relationship is used for Indicates a one-to-one mapping relationship between at least two ending types and at least two ordered set types, the first ordered set type corresponds to the first ending type, and the first ending type is the at least two ending types Any of the end types.
  • the code blocks in the PCS layer code block stream of the Ethernet signal may include 64-bit / 66-bit code blocks.
  • the code blocks of the ordered set type in the PCS layer code block stream of the low-to-medium-speed Ethernet signal include code blocks whose information carried in the code block type field is 0x2d or 0x55.
  • the transponder (incoming, transcoder 413 or transcoder 433) may be implemented by a processor.
  • the processor is mainly used to process communication protocols and communication data, and control the entire transmission device, execute a software program, and process data of the software program, for example, to support the transmission device to perform the actions described in the foregoing method embodiments.
  • the memory is mainly used for storing software programs and data.
  • the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program.
  • the processor may include a baseband processor and a central processor.
  • the baseband processor is mainly used to process communication protocols and communication data.
  • the central processor is mainly used to control the entire terminal device, execute software programs, and process software programs. data.
  • the baseband processor and the central processing unit may also be separate processors, which are interconnected through technologies such as a bus.
  • the terminal device may include multiple baseband processors to adapt to different network standards, the terminal device may include multiple central processors to enhance its processing capabilities, and various components of the terminal device may be connected through various buses.
  • the baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processing unit may also be expressed as a central processing circuit or a central processing chip.
  • the function of processing communication protocols and communication data may be built in the processor or stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.
  • the processor may be a central processing unit (CPU), and the processor may also be another general-purpose processor, digital signal processor (DSP), or special-purpose integration.
  • Circuit application specific integrated circuit, ASIC
  • ready-made programmable gate array field programmable gate array, FPGA
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrical memory Erase programmable read-only memory (EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access Access memory
  • double SDRAM double data rate synchronous dynamic random access memory
  • enhanced SDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access Fetch memory
  • direct RAMbus RAM direct RAMbus RAM, DR RAM
  • the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any other combination.
  • the above embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions or computer programs.
  • the processes or functions according to the embodiments of the present application are wholly or partially generated.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (for example, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like, including one or more sets of available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium.
  • the semiconductor medium may be a solid state drive.
  • the size of the sequence numbers of the above processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not deal with the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit. If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • the foregoing storage medium includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • Spectroscopy & Molecular Physics (AREA)
  • Quality & Reliability (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Time-Division Multiplex Systems (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)

Abstract

本申请提供了一种接收码块流的方法和通信设备，该方法包括：接收设备从传送网络接收包括多个码块的第一速率模式的码块流；该接收设备从该码块流中确定目标码块，其中，该目标码块是该接收设备在该码块流的包间隙内接收到的码块，该目标码块包括第一目标码块，该第一目标码块为数据类型的码块，和/或该目标码块包括第二目标码块，该第二目标码块为结束类型的码块；该接收设备对该目标码块进行修改，以将该目标码块修改为第二速率模式的有序集类型的码块，能够确保控制码块的传输，提高通信的准确性。

Description

接收码块流的方法、发送码块流的方法和通信装置
本申请要求于2018年08月07日提交中国专利局、申请号为201810893109.0、申请名称为“接收码块流的方法、发送码块流的方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及接收码块流的方法、发送码块流的方法和通信装置。
背景技术
以太网技术在网络业界取得了广泛的引用，以太网技术以其简洁、尽力而为的传输方式和标准化互通互联的机制受到网络厂商的极大欢迎。目前，以太网技术已经发展到了基于100吉比特(gigabit，G)以太网标准的灵活以太网(flexible ethernet)1.0实现协议(以下简称FlexE)。FlexE的速率聚合支持高速以太网业务数据流使用低速率的多个物理接口一同承载，子速率和通道化则允许一个以太网物理接口内并发的承载多个低速率的数据流。现网中的接入和城域网大量部署了支持以太网接口的网络设备，FlexE接口兼容标准以太网且扩展了以太网的功能和灵活性，在第五代(5th generation，5G)系统前后传网络、数据中心互联等确定性低时延、高带宽场景拥有很高的市场应用前景和发展空间。
其中，FlexE的传输速度可以吉比特每秒(gigabit per second，Gbps)为单位，目前，FlexE中的客户信号可以包括以下模式：支持5Gbps速率的以太网物理接口(5Gbps base range，5GBASE-R)模式、支持10Gbps速率的以太网物理接口(10Gbps base range，40GBASE-R)模式、支持25Gbps速率的以太网物理接口(25Gbps base range，n×25GBASE-R)模式。
上述客户信号需要经由以太网的传送网络转发，以太网的传送网络可以使用例如支持100Gbps速率的以太网物理接口(100Gbps base range，100GBASE-R)、200Gbps速率的以太网物理接口(200Gbps base range，200GBASE-R)、400Gbps速率的以太网物理接口(400Gbps base range，400GBASE-R)模式。
其中，在5GBASE-R、10GBASE-R或25GBASE-R等模式中某些有序集类型码块(例如0x2d类型码块或0x55类型码块)，在100GBASE-R、200GBASE-R、400GBASE-R以及更高速率模式中不存在。因此，该有序集类型的码块无法通过基于100G及以上速率的接口的传送网络进行传输，影响了通信的准确性。
发明内容
本申请提供一种发送接收码块流的方法、发送码块流的方法和通信装置，能够确保控制码块的传输，提高通信的准确性。
第一方面，提供了一种接收码块流的方法，包括：接收设备从传送网络接收包括多个码块的第一速率模式的码块流；该接收设备从该码块流中确定目标码块，其中，该目标码块是该接收设备在该码块流的包间隙内接收到的码块，该目标码块包括第一目标码块，该第一目标码块为数据类型的码块；和/或该目标码块包括第二目标码块，该第二目标码块为结束类型的码块；该接收设备对该目标码块进行修改，以将该目标码块修改为第二速率模式的有序集类型的码块。
其中，该目标码块是该第一速率模式的码块流的发送设备对所接收到的来自客户设备的第二速率模式的码块流中的有序集类型码块进行修改后生产的码块。
由于有序集类型的码块在包间隙中传输，因此，发送设备可以将有序集类型的码块修改为传送网络能够识别的数据类型码块或结束类型码块，从而，接收设备能够将位于包间隙的数据类型码块或结束类型码块确定为是基于有序集类型的码块修改而成的，进而可以将位于包间隙的数据类型的码块或结束类型的码块修改回有序集类型的码块，从而，既能够确保该有序集类型的码块能够通过传送网络被传输，又能够确保接收设备可靠地识别出该有序集类型的码块，进而，能够提高通信的准确性。
在本申请中，该第一速率模式的码块流可以是在传送网络(例如，支持FlexE的网络)中传输的以太网信号(例如，高速以太网信号)中在物理编码自层PCS处理(例如，编码或解码)的码块流(或者说，比特码块流或比特流)。
另外，该第二速率模式的码块流可以是在客户设备和传送设备(例如，传送网络的入口设备或出口设备)之前传输的以太网信号(例如，中低速以太网信号)中在PCS处理的码块流(或者说，比特码块流或比特流)。
此外，该发送设备发送的第一速率模式的码块流可以是发送设备对该第二速率模式的码块流进行例如转码等处理后生成的。
其中，该接收设备可以是传送网络中针对该第一速率模式的码块流(或者说，包括第一速率模式的码块流的以太网信号)的出口设备。即，该以太网信号经由该出口设备从传送网络流入该以太网信号的目的网络(包括该以太网信号的目的客户设备)。
该发送设备可以是传送网络中针对该第一速率模式的码块流(或者说，包括第一速率模式的码块流的以太网信号)的入口设备。即，该以太网信号经由该入口设备从该以太网信号的源网络(包括该以太网信号的源客户设备)流入传送网络。
在本申请中，该第二速率模式对应的速率小于或等于该第一速率模式对应的速率。
其中，“该第二速率模式对应的速率小于或等于该第一速率模式对应的速率”可以以理解为作为高速模式的信号的该第一速率模式的信号可以由包括第二速率模式的信号在内的一个或多个低速模式的信号聚合而成。
或者，“该第二速率模式对应的速率小于或等于该第一速率模式对应的速率”可以以理解为该第一速率模式的信号能够包括的时隙的数量大于第二速率模式的信号包括的时隙的数量。
作为示例而非限定，该第一速率模式可以包括40GBASE-R模式、100GBASE-R模式、200GBASE-R模式或400GBASE-R模式。
或者说，该传送网络可以包括40GBASE-R模式、100GBASE-R模式、200GBASE-R模式或400GBASE-R模式的以太网物理链路，或者说，该传送网络可以支持速率为 40Gbps、100Gbps、200Gbps或400Gbps的以太网物理接口模式。
或者说，该传送网络中的传送设备基于40GBASE-R模式、100GBASE-R模式、200GBASE-R模式或400GBASE-R模式进行以太网信号的转发。
该第一速率模式的码块流(或者说，包括第一速率模式的码块流的以太网信号)的传输数量可以是40Gbps、100Gbps、200Gbps或400Gbps。
或者说，包括第一速率模式的码块流的以太网信号可以是40GBASE-R模式的以太网信号、100GBASE-R模式的以太网信号、200GBASE-R模式的以太网信号或400GBASE-R模式的以太网信号。
作为示例而非限定，该第二速率模式可以包括5GBASE-R模式、10GBASE-R模式或25GBASE-R模式。
或者说，该客户设备和传送网络的入口设备或出口设备之间的链路可以包括5GBASE-R模式、10GBASE-R模式或25GBASE-R模式的以太网物理链路，或者说，该客户设备可以支持速率为5Gbps、10Gbps或25Gbps的以太网物理接口模式。
或者说，该客户设备和传送网络的入口设备或出口设备之间基于5GBASE-R模式、10GBASE-R模式或25GBASE-R模式进行以太网信号的转发。
该第二速率模式的码块流(或者说，包括第二速率模式的码块流的以太网信号)的传输数量可以是5Gbps、10Gbps或25Gbps。
或者说，包括第二速率模式的码块流的以太网信号可以是5GBASE-R模式的信号、10GBASE-R模式的信号或25GBASE-R模式的信号。
可选地，该码块流中的码块可以为64比特码块，或者，该码块流中的码块可以为66比特码块。
该有序集类型的码块也可以称为有序集(order set，O)码块。
例如，该O码块可以包括码块类型字段(block type field)承载的信息为0x2d的码块。
再例如，该O码块可以包括码块类型字段承载的信息为0x55的码块。
其中，该O码块的同步头字段(sync header field)承载的比特为10。
其中，该比特“10”可以理解为二进制(0b)的比特或数值“10”，以下，为了避免赘述，省略对相同或详细情况的说明。
可选地，该接收设备对该目标码块进行修改，包括：该接收设备将该第二目标码块的码块类型字段承载的信息修改为该有序集类型对应的码块类型信息。
例如，该T码块可以包括码块类型字段承载的信息为以下至少一种信息的码块：
0x87、0x99、0xAA、0xB4、0xCC、0xD2、0xE1、0xFF。
即，该接收设备对该目标码块的码块类型字段承载的信息进行修改包括：该接收设备将该第二目标码块的码块类型字段承载的信息从0x87、0x99、0xAA、0xB4、0xCC、0xD2、0xE1、0xFF中的一种修改为0x2d或0x55。
可选地，该接收设备将该第二目标码块的码块类型字段承载的信息修改为该有序集类型对应的码块类型信息，包括：该接收设备根据映射关系，将第一结束类型的第二目标码块的码块类型字段承载的信息修改为第一有序集类型对应的信息，其中，该映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，该第一有序集类型与该第一结束类型相对应，该第一结束类型是该至少两种结束类型中的任意一种结束类型。
可选地，该接收设备将该第二目标码块的码块类型字段承载的信息修改为该有序集类型对应的码块类型信息包括：该接收设备确定至少两种结束类型码块与至少两种有序集类型码块之间的一一映射关系；当该第二目标码块为第一结束类型码块时，该接收设备根据该映射关系，将该目标码块的码块类型字段承载的信息修改为第一有序集类型码块对应的信息，其中，该第一有序集类型码块是该映射关系指示的与第一结束类型码块对应的有序集类型码块，该第一结束类型码块是该至少两种结束类型码块中的任意一种结束类型码块。
例如，码块类型字段承载的信息为0x2d的O码块可以对应码块类型字段承载的信息为0xE1的T码块。
再例如，码块类型字段承载的信息为0x55的O码块可以对应码块类型字段承载的信息为0xFF的T码块。
另外，该T码块的同步头字段承载的比特为10。
该接收设备对该目标码块进行修改，包括：该接收设备将该第一目标码块的同步头字段承载的信息修改为该有序集类型对应的同步头信息。
该数据类型码块也可以称为数据(data，D)码块。
此情况下，可选地，即，该接收设备对该目标码块的码块类型字段承载的信息进行修改包括：该接收设备将该第一目标码块的码块类型字段承载的信息从01修改为10。
其中，该D码块的同步头字段承载的比特为01。
即，该接收设备将该目标码块的同步头字段承载的信息修改为有序集类型码块对应的信息包括：该接收设备将该目标码块的同步头字段承载的信息从01修改为10。
另外，该包间隙(inter packet gap，IPG)也可以称为帧间隙，是指两个以太网数据包之间的传输时间间隔。
其中，每个数据包包括多个码块，一个数据包的首个码块可以为S码块，一个数据包的最后一个码块可以为T码块。
可选地，在所述接收设备从所述码块流中确定目标码块之前，该方法还包括：该接收设备根据该码块流中的开始类型的码块，确定该包间隙结束位置；该接收设备根据该码块流中的结束类型的码块，确定该包间隙的起始位置。
具体地说，任意一个IPG(记做IPG#1)可以位于两个数据包(记做，数据包#1和数据包#2)之间，设数据包#1的传输顺序位于数据包#2之前，则该IPG#1的起始位置可以由该数据包#1的结束位置确定，即，可以通过该数据包#1中的T码块来确定该IPG#1的起始位置。即，当以太网中的设备接收到数据包#1中的T码块时，可以认为IPG#1开始。并且，该IPG#2的结束位置可以由该数据包#2的起始位置确定，即，可以通过该数据包#1中的T码块来确定该IPG#1的起始位置。即，当以太网中的设备接收到数据包#2中的S码块时，可以认为IPG#1结束。
例如，当该目标码块包括数据类型码块(即，第一目标码块)时，以太网信号中的每个T码块均表示包的结束，从而，帧间隙的起始位置可以根据T码块的位置确定。
此情况下，可选地，该接收设备从该以太网信号中确定目标码块，包括：该接收设备将在第一包间隙指示信息的值为预设的第一值的期间内接收到的数据类型码块，确定为目标码块，其中，在该接收设备接收到开始类型码块时该第一包间隙指示信息被置为预设的 第二值，在该接收设备接收到结束类型码块时该第一包间隙指示信息被置为该第一值。
或者，可选地，该接收设备从该以太网信号中确定目标码块，包括：该接收设备将位于T码块之后的码块确定为目标码块(即，第一目标码块)。
或者，可选地，该接收设备从该以太网信号中确定目标码块，包括：该接收设备将位于S码块之前的码块确定为目标码块(即，第一目标码块)。
再例如，当该目标码块包括结束类型码块(即，第二目标码块)时，以太网信号中的部分T码块可能是由控制O码块经修改后生成的，此情况下，帧间隙的起始位置可以根据S码块之后的首个T码块的位置确定。
此情况下，该接收设备根据该码块流中的结束类型的码块，确定该包间隙的起始位置，包括：该接收设备根据该码块流中的第一结束类型的码块，确定该包间隙的起始位置，该第一结束类型的码块是在传输顺序上位于该开始类型的码块之后的首个结束类型的码块。
可选地，该接收设备从该以太网信号中确定目标码块，包括：该接收设备将在第一包间隙指示信息的值为预设的第一值的期间内接收到的结束类型码块，确定为目标码块(即，第二目标码块)，其中，在该接收设备接收到开始类型码块时该第一包间隙指示信息被置为预设的第二值，在该接收设备在第一包间隙指示信息的值为该第二值的期间内接收到结束类型码块时该第一包间隙指示信息被置为该第一值。
第二方面，提供了一种接收码块流的方法，包括：发送设备根据多个码块的第二速率模式的码块流，确定第一速率模式的码块流，其中，该第二速率模式的码块流中的有序集类型的码块被修改为数据类型的码块，和/或该第二速率模式的码块流中的有序集类型的码块被修改为结束类型的码块；该发送设备向传送网络发送该第一速率模式的码块流。
由于有序集类型的码块在包间隙中传输，因此，发送设备可以将有序集类型的码块修改为传送网络能够识别的数据类型码块或结束类型码块，从而，接收设备能够将位于包间隙的数据类型码块或结束类型码块确定为是基于有序集类型的码块修改而成的，进而可以将位于包间隙的数据类型的码块或结束类型的码块修改回有序集类型的码块，从而，既能够确保该有序集类型的码块能够通过传送网络被传输，又能够确保接收设备可靠地识别出该有序集类型的码块，进而，能够提高通信的准确性。
在本申请中，该第一速率模式的码块流可以是在传送网络(例如，FlexE网络)中传输的以太网信号(例如，高速以太网信号)中在物理编码自层PCS处理(例如，编码或解码)的码块流(或者说，比特码块流或比特流)。
另外，该第二速率模式的码块流可以是在客户设备和传送设备(例如，传送网络的入口设备或出口设备)之前传输的以太网信号(例如，中低速以太网信号)中在PCS处理的码块流(或者说，比特码块流或比特流)。
此外，该发送设备发送的第一速率模式的码块流可以是发送设备对该第二速率模式的码块流进行例如转码等处理后生成的。
其中，该接收设备可以是传送网络中针对该第一速率模式的码块流(或者说，包括第一速率模式的码块流的以太网信号)的出口设备。即，该以太网信号经由该出口设备从传送网络流入该以太网信号的目的网络(包括该以太网信号的目的客户设备)。
该发送设备可以是传送网络中针对该第一速率模式的码块流(或者说，包括第一速率模式的码块流的以太网信号)的入口设备。即，该以太网信号经由该入口设备从该以太网 信号的源网络(包括该以太网信号的源客户设备)流入传送网络。
在本申请中，该第二速率模式对应的速率小于或等于该第一速率模式对应的速率。
其中，“该第二速率模式对应的速率小于或等于该第一速率模式对应的速率”可以以理解为作为高速模式的信号的该第二速率模式的信号可以由包括第一速率模式的信号在内的一个或多个低速模式的信号聚合而成。
或者，“该第二速率模式对应的速率小于或等于该第一速率模式对应的速率”可以以理解为该第二速率模式的信号能够包括的时隙的数量大于第一速率模式的信号包括的时隙的数量。
作为示例而非限定，该第一速率模式可以包括40GBASE-R模式、100GBASE-R模式、200GBASE-R模式或400GBASE-R模式。
或者说，该传送网络可以包括40GBASE-R模式、100GBASE-R模式、200GBASE-R模式或400GBASE-R模式的以太网物理链路，或者说，该传送网络可以支持速率为40Gbps、100Gbps、200Gbps或400Gbps的以太网物理接口模式。
或者说，该传送网络中的传送设备基于40GBASE-R模式、100GBASE-R模式、200GBASE-R模式或400GBASE-R模式进行以太网信号的转发。
该第一速率模式的码块流(或者说，包括第一速率模式的码块流的以太网信号)的传输数量可以是40Gbps、100Gbps、200Gbps或400Gbps。
或者说，包括第一速率模式的码块流的以太网信号可以是40GBASE-R模式的以太网信号、100GBASE-R模式的以太网信号、200GBASE-R模式的以太网信号或400GBASE-R模式的以太网信号。
作为示例而非限定，该第二速率模式可以包括5GBASE-R模式、10GBASE-R模式或25GBASE-R模式。
或者说，该客户设备和传送网络的入口设备或出口设备之间的链路可以包括5GBASE-R模式、10GBASE-R模式或25GBASE-R模式的以太网物理链路，或者说，该客户设备可以支持速率为5Gbps、10Gbps或25Gbps的以太网物理接口模式。
或者说，该客户设备和传送网络的入口设备或出口设备之间基于5GBASE-R模式、10GBASE-R模式或25GBASE-R模式进行以太网信号的转发。
该第二速率模式的码块流(或者说，包括第二速率模式的码块流的以太网信号)的传输数量可以是5Gbps、10Gbps或25Gbps。
或者说，包括第二速率模式的码块流的以太网信号可以是5GBASE-R模式的信号，、10GBASE-R模式的信号或25GBASE-R模式的信号。
可选地，该码块流中的码块可以为64B/66B码块，或者，可以为任意M比特/N比特的码块，其中M小于或等于N。
该有序集类型的码块也可以称为O码块。
例如，该O码块可以包括码块类型字段承载的信息为0x2d的码块。
再例如，该O码块可以包括码块类型字段承载的信息为0x55的码块。
其中，该O码块的同步头字段承载的比特为10。
可选地，该有序集类型的码块的码块类型字段承载的信息被修改为结束类型对应的码块类型信息。
例如，该T码块可以包括码块类型字段承载的信息为以下至少一种信息的码块：
0x87、0x99、0xAA、0xB4、0xCC、0xD2、0xE1、0xFF。
即，该方法包括：该发送设备将有序集类型的码块的码块类型字段承载的信息从0x2d或0x55修改为0x87、0x99、0xAA、0xB4、0xCC、0xD2、0xE1、0xFF中的一种。
可选地，该发送设备根据多个码块的第二速率模式的码块流，确定第一速率模式的码块流，包括：该发送设备根据该映射关系，将第一有序集类型的码块的码块类型字段承载的信息修改为第一结束类型对应的信息，其中，该映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，该第一有序集类型与该第一结束类型相对应，该第一有序集类型是该至少两种有序集类型中的任意一种有序集类型。
例如，码块类型字段承载的信息为0x2d的O码块可以对应码块类型字段承载的信息为0xE1的T码块。
再例如，码块类型字段承载的信息为0x55的O码块可以对应码块类型字段承载的信息为0xFF的T码块。
另外，该T码块的同步头字段承载的比特为10。
可选地，该有序集类型的码块的同步头字段承载的信息被修改为数据类型对应的同步头信息。
即，该方法包括：该接收设备将有序集类型的码块的同步头字段承载的信息修改为该数据类型对应的同步头信息。
该数据类型码块也可以称为数据(data，D)码块。
其中，该D码块的同步头字段承载的比特为01。
即，此情况下，该接收设备将有序集类型的码块的同步头字段承载的信息修改为该数据类型对应的同步头信息包括：该接收设备将有序集类型的码块的同步头字段承载的信息从10修改为01。
另外，该包间隙IPG也可以称为帧间隙，是指两个以太网数据包之间的传输时间间隔。
其中，每个数据包包括多个码块，一个数据包的首个码块可以为S码块，一个数据包的最后一个码块可以为T码块。
第三方面，提供了一种通信装置，包括用于执行上述第一方面或第二方面及其各实现方式中的方法的各步骤的单元。
在一种设计中，该通信装置为通信芯片，通信芯片可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
在另一种设计中，所述通信装置为通信设备(例如，入口设备或出口设备)，通信芯片可以包括用于发送信息或数据的发射机，以及用于接收信息或数据的接收机。
第四方面，提供了一种通信设备，包括收发器、处理器和存储器。该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得通信设备执行第一方面或第一方面任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
作为示例而非限定该通信设备可以包括编码设备。
第五方面，提供了一种通信设备，包括收发器、处理器和存储器。该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得通信设备执行第二方面或第二方面任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
作为示例而非限定该通信设备可以包括解码设备。
第六方面，提供一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面至第二方面以及第一方面至第二方面任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第七方面，提供一种处理装置，包括：存储器和处理器。所述处理器用于读取所述存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第二方面以及第一方面至第二方面任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第八方面，提供了一种芯片，包括处理器和存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，该计算机程序用于实现第一方面至第二方面以及第一方面至第二方面任一种可能实现方式中的方法。
第九方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第二方面以及第一方面至第二方面中任一种可能实现方式中的方法。
第十方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第二方面以及第一方面至第二方面中任一种可能实现方式中的方法。
根据本申请的方案，由于有序集类型的码块在包间隙中传输，因此，发送设备可以将有序集类型的码块修改为传送网络能够识别的数据类型码块或结束类型码块，从而，接收设备能够将位于包间隙的数据类型码块或结束类型码块确定为是基于有序集类型的码块修改而成的，进而可以将位于包间隙的数据类型的码块或结束类型的码块修改回有序集类 型的码块，从而，既能够确保该有序集类型的码块能够通过传送网络被传输，又能够确保接收设备可靠地识别出该有序集类型的码块，进而，能够提高通信的准确性。
附图说明
图1是本申请的通信系统的一例的示意图。
图2是本申请的传送网络的一例的示意图。
图3是中低速以太网接口使用的编码格式的一例的示意图。
图4是以太网信号的码流的一例的示意图。
图5是高速以太网接口使用的编码格式的一例的示意图。
图6是本申请的以太网信号的传输过程的一例的示意性交互图。
图7是本申请的中低速以太网信号的码块流结构的一例的示意图。
图8是本申请的0x2d码块在修改过程中的变化的一例的示意图。
图9是本申请的0x55码块在修改过程中的变化的一例的示意图。
图10是经过修改后码块流结构的一例的示意图。
图11是本申请的0x2d码块在修改过程中的变化的另一例的示意图。
图12是本申请的0x2d码块在修改过程中的变化的另一例的示意图。
图13是本申请的0x55码块在修改过程中的变化的另一例的示意图。
图14是经过修改后码块流结构的另一例的示意图。
图15是出口PE设备判断帧间隙的过程的一例的示意图。
图16是出口PE设备判断帧间隙的过程的另一例的示意图。
图17是本申请的位于帧间隙的D码块或T码块在恢复过程中的变化的一例的示意图。
图18是本申请的位于帧间隙的T码块在恢复过程中的变化的另一例的示意图。
图19是本申请的位于帧间隙的T码块在恢复过程中的变化的另一例的示意图。
图20是本申请的位于帧间隙的T码块在恢复过程中的变化的另一例的示意图。
图21是本申请的发送码块流的装置的示意图。
图22是本申请的接收码块流的装置的示意图。
图23是本申请的传送设备的一例的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1示出了本申请的以太网系统100的一例的示意图。
在本申请实施例中，该通信系统包括至少三个客户设备，例如，如图1所示，该通信系统可以包括多个客户设备110。
并且，在本申请实施例中，该多个客户设备110彼此之间可以通过传送网络(也可以称为，转发网络)进行通信。
作为示例而非限定，在本申请实施例中，该传送网络可以是例如，光通信网络。
在本申请实施例中，传送网络可以包括多个传送设备120。
在本申请中，每个客户设备110可以与一个或多个传送设备120通信连接。
图2示出了传送网络的结构的一例的示意图。
如图2所示，该传送网络可以包括网络边缘(provider edge，PE)设备和网络(provider，P)设备。
其中，P设备中配置有网络侧接口(network to network interface，NNI)。该NNI接口用于传输符合传送网络的通信协议的数据。其中，该NNI接口可以包括普通以太网接口(例如，100GBASE-R模式接口)，或者，该NNI接口可以包括FlexE接口。
该PE设备中除该NNI外，还设置有用户侧接口(user network interface，UNI)。该UNI接口用于PE设备与客户设备之间的数据传输。
其中，对于一个以太网信号，与该以太网信号的源客户设备连接的PE设备可以称为针对该以太网信号的入口设备(或者说，入口传送设备)，与该以太网信号的目的客户设备连接的PE设备可以称为针对该以太网信号的出口设备(或者说，出口传送设备)。
源客户设备在向目的客户设备发送信号时，该源客户设备可以生成信号，并将该信号传输至与其通信连接的传送设备，从而该传送网络可以将该信号路由(或者说，转发)至该信号的目标客户设备。
另外，传送网络中针对该源客户设备的入口传送设备还可以对该信号进行处理(例如，转发处理，或者说，封装处理)，以将该信号转换为能够在传送网络中传输的信号，并将该信号传输至该传送网络中用于向该目的接收设备传输信号的其他传送设备(例如，针对该目标客户设备的出口传送设备)。
此外，传送设备还可以从其他传送设备或客户设备接收需要发送至与其通信连接的客户设备的信号，并且，可以对该信号进行处理(例如，转码处理，或者说，解封装处理)，以将该信号转换为客户设备能够识别的信号，并将处理后的信号传输给客户设备，从而客户设备能够对所接受到的信号进行解析以获取承载于所述信号中的数据。
另外，在本申请实施例中，在任意两个客户设备之间传输的信号可以经由一个传送设备的处理和转发，也可以经由多个传送设备的处理和转发，本申请并未特别限定。
应理解，图1所示的客户设备和传送设备的数量仅为示例性说明，本申请并未特别限定。
在本申请实施例中，客户设备可以是例如，个人计算机等客户端设备，该客户端设备能够经以太网或光纤等媒介进行通信。
在本申请实施例中，客户设备还可以是网络设备，网络设备可以是为用户设备提供各种业务的服务器，例如，软件定义网络(software defined network，SDN)服务器，万维网(web)服务器、文件传输协议(file transfer protocol，FTP)服务器、企业关键应用服务器和其它关键任务服务器(例如，提供防火墙服务的服务器)、通信(communication technology，CT)领域中的业务处理单板(service process unit，SPU)等。
在本申请实施例中，传送设备可以是网关设备、交换机或路由器等设备。
在本申请实施例中，该客户设备可以是信号的发送端，也可以是信号的接收端。
发送端客户设备可以根据以太网协议规定，生成接收端以太网设备能够识别的客户以太网信号。并且，发送端客户设备可以将该客户以太网信号发送给传送网络中与该发送端客户设备通信连接的入口传送设备。
入口传送设备可以根据以太网络协议规定，将该客户以太网信号封装为传送网络中的传送设备能够识别的转发以太网信号。
传送网络将该转发以太网信号路由至与接收端客户设备通信连接的出口传送设备。
该出口传送设备可以对该转发以太网信号进行解封装，以还原该客户以太网信号，并发送给客户设备。
下面结合图3，对该客户以太网信号进行说明。
其中，该客户以太网信号可以是中低速以太网信号，或者说，该客户以太网信号的接口模式可以是5G BASE-R模式、10GBASE-R模式或25G BASE-R模式。
并且，该中低速以太网信号可以是由中低速以太网的64比特(bit，B)/66B码块(block)构成。
其中，该中低速以太网的64B/66B码块可以包括2比特的同步头字段(sync header field)和8个字节(即，64bit)的码块负载(block payload)。
另外，该中低速以太网的64B/66B码块可以包括数据码块(data block)和控制码块(control block)。
其中，该控制码块也可以包括有序集(ordered set，O)类型码块，简称O码块、开始(started)类型码块，简称S码块和结束(terminated)类型码块，简称T码块。
在本申请中，该控制码块的同步都字段承载的信息(具体地说，是2比特字符)可以包括10。
在本申请中，在控制码块的码块负载可以包括1个字节的码块类型字段(block type field)。
即，在本申请中，一个码块可以包括2个比特的同步头字段，8个比特(1个字节)的码块类型字段和56个比特(7个字节)的净荷字段(payload field)。
图3示出了该中低速以太网的64B/66B码块的编码格式的一例的示意图。如图3所示，例如，该在该O码块的码块类型字段所承载的信息(具体地说，是16进制字符)可以包括但不限于0x2d和0x55。
其中，“0x”可以用于标识其后的数值为十六进制。以下，省略对相同或相似情况的说明。
以下，为了便于理解和区分，将码块类型字段所承载的信息为0x2d的码块称为0x2d码块，将码块类型字段所承载的信息为0x55的码块称为0x55码块。
应理解，图3所示该中低速以太网的64B/66B码块的编码格式仅为示例性说明，本申请并未限定于此，现有技术中，其他能够在该中低速以太网的码块的编码格式均落入本申请的保护范围内，例如，错误(error)码块、空闲(idle)码块和低能耗空闲(low power idle，LPI)码块。
另外，该中低速以太网的64B/66B码块的编码过程可以在发送端客户设备的物理编码子层(physical coding sublayer，PCS)实体中进行。
其中，物理编码子层位于协调子层(reconciliation sublayer，RS)和物理介质接入子层(physical medium attachment sublayer，PMAS)之间。
物理编码子层用于将经过完善定义的以太网MAC功能映射到现存的编码和物理层信号系统的功能上去。并且，物理编码子层用于线路编码和循环冗余校验(cyclic redundancy check，CRC)校验编码。
对应的，该中低速以太网的64B/66B码块的解码过程可以在接收端客户设备的物理编 码子层实体中进行。
在本申请中，该中低速以太网的64B/66B码块构成的以太网信号可以包括多个数据包(packet)。
图4示出了具有上述结构的以太网码流的一例。如图4所示，每个数据包可以包括一个S码块多个D码块和一个T码块。
其中，该S码块用于指示数据包开始，T码块用于指示数据包结束。
并且，在本申请中，相邻的两个数据包之间可以具有时间间隔，该时间间隔也可以称为包间隙或帧间隙。
如图4所示，在该包间隙之间可以用于传输O码块等。
另外，该客户以太网信号的编解码过程可以与现有技术相似，这里，为了避免赘述，省略其详细说明。
下面结合图5，对该转发以太网信号进行说明。
在传送网络中传输的高速以太网信号也可以称为FlexE客户(client)。
FlexE Client用于封装用户的数据，并按照FlexE接口定义的数据传输方式传输该数据，一个FlexE Client可以承载一个用户的数据流。
具体地说，以太网系统可以通过例如，时分多路复用(time division multiplexing，TDM)方式等划分时隙，实现传输管道带宽的硬隔离，一个业务数据流可以分配到一到多个时隙中，实现了对各种速率业务的匹配。
一个FlexE组(Group)可以包含一个或多个捆绑的同速率(例如，100GBASE-R，200GBASE-R或400GBASE-R)的物理链路接口，每个FlexE Group上承载一个或多个FlexE实例(Instance)。
即，在本申请中，该转发以太网信号可以是高速以太网信号，或者说，该转发以太网信号的接口模式可以是100G BASE-R模式、200GBASE-R模式或400G BASE-R模式。
其中，FlexE Instance可以是指承载FlexEClient的单元，每个FlexE Instance可以支持例如，100Gbps的速率。
FlexE Group对应的时隙分配表叫FlexE时隙日历(calendar)，单个FlexE Client对应的时隙映射表叫子时隙分配表(sub-calendar)，每个时隙颗粒度为5Gb或25Gb。一个FlexE Group的calendar由一个或多个sub-calendar组成，每个sub-calendar指示了这些时隙如何分配给相应的FlexE client。FlexE client代表在FlexE Group上指定FlexE实例上的指定时隙(一个或多个时隙)传输的客户数据流，一个FlexE Group上可承载多个FlexE Client。
一个FlexE Client可对应一个到多个用户业务数据流(MAC Client)，FlexE薄层(Shim)可以提供FlexE Client到MAC Client的数据适配和转换。
例如，一个跨4个物理接口(例如，100GBASE-R的物理接口)的FlexE Group中，每个物理接口可以拥有20个5Gb子时隙，因此该FlexE Group拥有20×4个子时隙(sub-calendar)。
并且，该高速以太网信号可以是由高速以太网的64比特(bit，B)/66B码块(block)构成。
其中，该高速以太网的64B/66B码块可以包括2比特的同步头字段和8个字节的码块 负载。
另外，该高速以太网的64B/66B码块可以包括数据码块(data block)和控制码块(control block)。
其中，该控制码块也可以包括O码块、S码块和T码块。
在本申请中，该控制码块的同步都字段承载的信息(具体地说，是2比特字符)可以包括10。
在本申请中，在控制码块的码块负载可以包括1个字节的码块类型字段。
图5示出了该高速以太网的64B/66B码块的编码格式的一例的示意图。如图5所示，例如，该在该O码块的码块类型字段所承载的信息(具体地说，是16进制字符)可以包括但不限于0x4B。
应理解，图5所示该高速以太网的64B/66B码块的编码格式仅为示例性说明，本申请并未限定于此，现有技术中，其他能够在该中低速以太网的码块的编码格式均落入本申请的保护范围内，例如，错误码块、空闲码块和低能耗空闲码块等。
另外，从中低速以太网的64B/66B码块到高速以太网的64B/66B码块的转换(或者说，封装)过程，或者说，从中低速以太网信号到高速以太网信号的封装过程可以在入口传送设备的物理编码子层实体中进行。
对应的，从高速以太网的64B/66B码块到中低速以太网的64B/66B码块的转换(或者说，解封装)过程，或者说，从高速以太网信号到中低速以太网信号的封装过程可以在出口传送设备的物理编码子层实体中进行。
与由中低速以太网的64B/66B码块构成的以太网信号类似，在本申请中，由该高速以太网的64B/66B码块构成的以太网信号可以包括多个数据包。
如图4所示，每个数据包可以包括一个S码块多个D码块和一个T码块。
其中，该S码块用于指示数据包开始，T码块用于指示数据包结束。
并且，在本申请中，相邻的两个数据包之间可以具有时间间隔，该时间间隔也可以称为包间隙或帧间隙。如图4所示，在该包间隙之间可以用于传输O码块等。
如图3和图5所示，在中低速以太网信号(或者说，客户以太网信号)的编码格式中的某些O码块，例如，0x2d码块或0x55码块，并不存在于高速以太网信号(或者说，转发以太网信号)的编码格式中。
如果该0x2d码块或0x55码块进入传送网络，会导致因传送设备无法识别该0x2d码块或0x55码块而导致传输错误。
对此，本申请可以采用以下处理过程，避免传输错误。
图6示出了本申请的以太网信号的传输过程200的一例的示意性交互图。
如图6所示，在S210，客户设备#A可以生成以太网信号#A。其中，该以太网信号#A可以是中低速以太网信号，即，以太网信号#A的接口模式可以是5GBASE-R模式、10GBASE-R模式或25GBASE-R模式。
图7示出了该以太网信号#A的PCS层的码块流结构的一例，如图7所示，其中，该以太网信号#A的PCS层的码块流可以包括多个数据包，并且，在发送顺序上相邻的两个数据包之间存在有包间隙，并且，在包间隙中可以存在例如空闲码块，0x2d码块(如图7中“O 1”所示)、0x4B码块(如图7中“O 2”所示)、0x55码块(如图7中“O 3”所示) 等O码块以及空闲码块(如图7中“I”所示)。
需要说明的是图7所示的码块流结构仅为示例性说明，本申请并未限定于此，例如，该包间隙中可以仅存在0x2d码块和0x55码块中的一方。
并且，由于0x4B码块同时存在于中低速以太网信号和高速以太网信号中，因此，本申请所涉及的需要修改的码块不涉及该0x4B码块。
另外，上述以太网信号#A的生成过程可以与现有技术相似，这里，为了避免赘述，省略其详细说明。
在S220，客户设备#A可以将该以太网信号#A发送至与该客户设备#A通信连接的PE设备，以下，为了便于理解和区分，将该PE设备记做：入口PE设备#B。
在S230，入口PE设备#B可以对该以太网信号#A进行修改，以将以太网信号#A中不能被传送网络(具体地说是，各传送设备)识别的码块(即，0x2d码块和/或0x55码块)转换为传送网络能够识别的码块。
作为实例而非限定，在本申请中，可以列举以下修改方式。
方式1
当该以太网信号#A的PCS层的码块流包括0x2d码块时，入口PE设备#B可以将0x2d码块修改为D码块。
图8示出了该方式1的修改过程中，0x2d码块的变化的示意图。如图8所示，入口PE设备#B可以将0x2d码块的同步头字段承载的信息从控制类型码块对应的信息(例如，“10”)修改为数据类型码块对应的信息(例如，“01”)。
当该以太网信号#A的PCS层的码块流包括0x55码块时，入口PE设备#B可以将0x55码块修改为D码块。
图9示出了该方式1的修改过程中，0x55码块的变化的示意图。如图9所示，入口PE设备#B可以将0x55码块的同步头字段承载的信息从控制类型码块对应的信息(例如，“10”)修改为数据类型码块对应的信息(例如，“01”)。
图10示出了基于方式1修改后的图7所示的以太网信号的PCS层的码块流的变化情况。如图10所示，经过方式1修改后，低速以太网信号的PCS层的码块流中的0x2d码块和/或0x55码块被转换为D码块。
方式2
当该以太网信号#A的PCS层的码块流包括0x2d码块时，入口PE设备#B可以将0x2d码块修改为T码块。
具体地说，入口PE设备#B可以将0x2d码块的码块类型字段承载的信息从0x2d码块对应的信息(例如，“0x2d”)修改为T码块对应的信息(例如，“0x87”、“0x99”、“0xAA”、“0xB4”、“0xCC”、“0xD2”、“0xE1”、“0xFF”中的任意一种信息)。
当该以太网信号#A的PCS层的码块流包括0x55码块时，入口PE设备#B可以将0x55码块修改为T码块。
具体地说，入口PE设备#B可以将0x55码块的码块类型字段承载的信息从0x55码块对应的信息(例如，“0x55”)修改为T码块对应的信息(例如，“0x87”、“0x99”、“0xAA”、“0xB4”、“0xCC”、“0xD2”、“0xE1”、“0xFF”中的任意一种信息)。
需要说明的是，由于在实际传输中可能存在以太网信号中同时存在0x2d码块和0x55 码块的情况，此情况下，如果将0x2d码块和0x55码块的码块类型字段承载的信息修改为同一T码块(记做，T码块#1)对应的信息，则可能导致出口PE设备无法确定所接受到的以太网信号中的T码块#1应该还原为0x2d码块还是0x55码块。其中，该出口PE设备可以是与该以太网信号#A的目的客户设备通信连接的PE设备，以下，为了便于理解和区分，将该PE设备记做：出口PE设备#C。
对此，在本申请中，可以在出口PE设备#C和入口PE设备#B中预先存储映射关系#A。
该映射关系#A可以用于指示0x2d码块与一种T码块(记做：T码块#a)的对应关系，该映射关系#A可以用于指示0x55与另一种T码块(记做：T码块#b)的对应关系。
即，入口PE设备#B可以根据映射关系#A的指示将0x2d码块的码块类型字段承载的信息从0x2d码块对应的信息(例如，“0x2d”)修改为T码块#a的码块类型字段对应的信息。
作为实例而非限定，该T码块#a可以T6码块，即，该T码块#a可以是码块类型字段对应的信息为“0xE1”。
由于T6码块中可用于承载数据的字节的数量较多，因此通过将0x2d码块修改为T6码块，能够确保修改后的码块不发生信息丢失，从而，进一步提高本申请的效果。
应理解，以上列举的T码块#a的具体实例仅为示例性说明，本申请并未限定于此，该T码块#a可以是T0～T7中任意一种码块，只要确保该T码块#a与T码块#b相异即可。
图11示出了该方式2的修改过程中，0x2d码块的变化的示意图。如图11所示，入口PE设备#B可以将0x2d码块的码块类型字段承载的信息从“0x2d”修改为“0xE1”。
可选地，如图12所示，在本申请中，入口PE设备#B还可以将0x2d码块中的“O4”字节中承载的信息移位至T6码块中的“D0”字节中，可以将0x2d码块中的“D5”字节中承载的信息移位至T6码块中的“D1”字节中，可以将0x2d码块中的“D6”字节中承载的信息移位至T6码块中的“D2”字节中，可以将0x2d码块中的“D7”字节中承载的信息移位至T6码块中的“D3”字节中。
并且，入口PE设备#B还可在基于上述修改而生成的T6码块中“D4”、“D5”、“D6”和“D7”字节中的填充规定的比特，例如“0”。
另外，由于0x2d码块中的“O4”字节中承载的信息包括的比特的数量小于一个字节，因此，0x2d码块中的“O4”字节中承载的信息仅占据T6码块中的“D0”字节中的部分比特；0x2d码块中的“D5”字节中承载的信息占据T6码块中的“D0”字节中的另一部分比特以及“D1”字节中的部分比特；0x2d码块中的“D6”字节中承载的信息占据T6码块中的“D1”字节中的另一部分比特以及“D2”字节中的部分比特；0x2d码块中的“D7”字节中承载的信息占据T6码块中的“D2”字节中的另一部分比特以及“D3”字节中部分。
并且，此情况下，可以在T6码块中的“D3”字节另一部分比特(即，未填充0x2d码块中的“D7”字节中承载的信息的比特)可以填充规定的比特，例如“0”。
即，综上所述，图12所示，在本申请中，入口PE设备#B还可以将0x2d码块中的“O4”字节、“D5”字节、“D6”字节和“D7”字节中承载的信息移位至T6码块中的“D0”字节、“D1”字节、“D2”字节和“D3”字节，并且，移位后的各比特之间的位置关系与移位前的各比特之间的位置关系相同。
作为实例而非限定，该T码块#b可以T7码块，即，该T码块#b可以是码块类型字 段对应的信息为“0xFF”。
由于T7码块中可用于承载数据的字节的数量较多，因此通过将0x55码块修改为T7码块，能够确保修改后的码块不发生信息丢失，从而，进一步提高本申请的效果。
应理解，以上列举的T码块#b的具体实例仅为示例性说明，本申请并未限定于此，该T码块#b可以是T0～T7中任意一种码块，只要确保该T码块#a与T码块#b相异即可。
图13示出了该方式2的修改过程中，0x55码块的变化的示意图。如图13所示，入口PE设备#B可以将0x2d码块的码块类型字段承载的信息从“0x55”修改为“0xFF”。
需要说明的是，上述映射关系#A可以是由传送网络中的管理设备确定并下发给各传送设备的，或者，上述映射关系#A也可以是有通信系统或通信协议预先规定的，或者，上述映射关系#A可以是由入口PE和出口PE协商确定的，或者，上述映射关系#A可以是由使用者或管理员输入至入口PE和出口PE中的，或者，上述映射关系#A可以是由制造商或运营商配置在入口PE和出口PE中的，本申请并未特别限定。
图14示出了基于方式2修改后的图7所示的以太网信号的PCS层的码块流的变化情况。如图14所示，经过方式2修改后，低速以太网信号的PCS层的码块流中的0x2d码块和/或0x55码块被转换为T码块。
方式3
当该以太网信号#A的PCS层的码块流包括0x2d码块时，入口PE设备#B可以将0x2d码块修改为D码块。
当该以太网信号#A的PCS层的码块流包括0x55码块时，入口PE设备#B可以将0x55码块修改为T码块。
方式4
当该以太网信号#A的PCS层的码块流包括0x2d码块时，入口PE设备#B可以将0x2d码块修改为T码块。
当该以太网信号#A的PCS层的码块流包括0x55码块时，入口PE设备#B可以将0x55码块修改为D码块。
其中，方式3和方式4中，针对各码块的修改过程可以与方式1或方式2中描述的过程类似，这里，为了避免赘述，省略其详细说明。
需要说明的是，在本申请中，由于出口PE设备#C需要对经过上述修改的码块进行还原，因此，出口PE设备#C所采用的恢复方式需要与入口PE设备#B所采用的修改方式相对应(例如，该恢复方式与修改方式互为逆处理)，以确保还原的准确定。
作为实例而非限定，在本申请中，入口设备#A所采用修改方式可以由通信系统或通信协议预先规定，或者，入口设备#A所采用修改方式可以由出口PE设备#C和入口PE设备#B协商确定，或者，入口设备#A所采用修改方式可以由传送网络的管理设备确定并下发至入口PE设备#B，并且，管理设备可以将于该修改方式对应的恢复方式下发至出口PE设备#C。
并且，在S240，入口PE设备#B可以根据修改后以太网信号#A生成在传送网络中传输高速以太网信号(例如，FlexE Client支持的以太网信号)，以下，为了便于理解和说明，称为以太网信号#B。并且，入口PE设备#B可以经由传送网络将该以太网信号#B发送至出口PE设备#C。其中，过程可以与现有技术相似，这里为了避免赘述，省略其详细 说明。
在S250，出口PE设备#C可以从所接收到的以太网信号#B的PCS层的码块流中确定被入口PE设备#B修改过的码块，以下，为了便于理解和区分，记做：码块#A。
由于该码块#A是入口PE设备#B对O码块(例如，0x2d码块或0x55码块)修改后生成的，并且，该O码块存在于IPG中，因此，出口PE设备#C可以基于该以太网信号#B的PCS层的码块流的帧间隙，确定码块#A。
其中，该码块#A可以仅包括D码块(即，情况1)或者，该码块#A可以包括T码块(即，情况2)，上述不同情况下，确定帧间隙的方法有所不同，下面，分别对上述情况下出口PE设备#C确定帧间隙的过程，进行详细说明。
情况1
该码块#A可以仅包括D码块，可以理解为入口PE设备#B将0x2d码块或0x55码块均修改为D码块，或者说，入口PE设备#B未将0x2d码块或0x55码块均修改为T码块。
此情况下，以太网信号#B的PCS层的码块流中的T码块均为以太网信号#A的PCS层的码块流中的T码块。即，以太网信号#B的PCS层的码块流中的每个T码块均可以表示其所属于的数据包的结束。或者说，以太网信号#B的PCS层的码块流中的每个T码块均可以确定位于其后的包间隙开始。
例如，出口PE设备#C可以根据以太网信号#B的PCS层的码块流中的T码块和S码块，确定以太网信号#B的PCS层的码块流中的包间隙，即，任意一个包间隙(例如，包间隙#1)满足以下条件：
该包间隙#1位于在传输顺序上相邻的数据包#1和数据包#2之间，或者说，该包间隙#1位于数据包#1的T码块和数据包#2的S码块之间。
从而，出口PE设备#C可以将在包间隙中接收到的D码块确定为码块#A。
再例如，出口PE设备#C在接收一个T码块之后，可以将之后所接收到的D码块确定为码块#A，直至接收到S码块。
再例如，图15示出了出口PE设备#C的处理过程的一例。如图15所示，在出口PE设备#C中可以保存IPG信息，该IPG信息可以用于确定包间隙。
即，当PE设备#A在接收到T码块之后可以将该IPG信息的值置为表示当前时段属于包间隙的值，例如“1”。
并且，当PE设备#A在接收到T码块之后可以将该IPG信息的值置为表示当前时段不属于包间隙的值，例如“0”。
从而，出口PE设备#C可以将该IPG信息的值为“1”期间接收到的D码块确定为码块#A。
可选地，在出口PE设备#C上电(或者说，启动后)可以将该IPG信息的值置为“1”，从而，在以太网信号#A的首个数据包之前存在包间隙、且该包间隙中存在O码块的情况下，能够确保出口PE设备#C识别出基于该O码块修改的D码块。
情况2
该码块#A可以包括T码块，可以理解为：该码块#A可以仅包括T码块。即，为入口PE设备#B将0x2d码块或0x55码块均修改为T码块。
或者，该码块#A可以包括T，可以理解为：码块该码块#A可以包括T码块和D码块 双方。即，入口PE设备#B将0x2d码块或0x55码块中的一方改为T码块，入口PE设备#B将0x2d码块或0x55码块中的另一方改为D码块。
此情况下，以太网信号#B的PCS层的码块流中的T码块可以包括以太网信号#A的PCS层的码块流中的T码块，以及基于O码块生成的T码块。即，以太网信号#B的PCS层的码块流中的部分T码块可以表示其所属于的数据包的结束，另一部分T码块不能表示数据包的结束。或者说，以太网信号#B的PCS层的码块流中的部分T码块均可以确定位于其后的包间隙开始，另一部分T码块不能表示包间隙开始。
例如，出口PE设备#C可以根据以太网信号#B的PCS层的码块流中的T码块和S码块，确定以太网信号#B的PCS层的码块流中的包间隙，即，任意一个包间隙(例如，包间隙#1)满足以下条件：
该包间隙#1位于在传输顺序上相邻的数据包#1和数据包#2之间，或者说，该包间隙#1位于数据包#1的T码块和数据包#2的S码块之间。
其中，该数据包#1的T码块是该数据包#2的S码块之后的首个T码块。
从而，出口PE设备#C可以将在包间隙中接收到的D码块或T码块确定为码块#A。
再例如，出口PE设备#C在接收一个S码块之后，可以确定该S码块之后的首个T码块，并将该T码块将之后所接收到的D码块或T码块确定为码块#A，直至接收到S码块。
再例如，图16示出了出口PE设备#C的处理过程的一例。如图16所示，在出口PE设备#C中可以保存IPG信息，该IPG信息可以用于确定包间隙。
即，当PE设备#A在接收到S码块之后可以将该IPG信息的值置为表示当前时段不属于包间隙的值，例如“0”。
并且，当PE设备#A在接收到T码块之后，如果IPG信息的值为“0”，则可以将该IPG信息的值置为表示当前时段属于包间隙的值，例如“1”。
另外，当PE设备#A在接收到T码块之后，如果IPG信息的值为“1”，则可以将该IPG信息的值置为表示当前时段属于包间隙的值，例如“1”。
从而，出口PE设备#C可以将该IPG信息的值为“1”期间接收到的D码块或T码块确定为码块#A。
可选地，在出口PE设备#C上电(或者说，启动后)可以将该IPG信息的值置为“1”，从而，在以太网信号#A的首个数据包之前存在包间隙、且该包间隙中存在O码块的情况下，能够确保出口PE设备#C识别出基于该O码块修改的D码块。
并且，出口PE设备#C对码块#A进行恢复处理，以将码块#A还原为其在以太网信号#A中对应的码块(即，0x2d码块和/或0x55码块)，。
作为实例而非限定，在本申请中，可以列举以下修改方式。
方式a
当入口PE设备#B采用上述方式1进行修改时，出口PE设备#C可以将码块#A修改为0x2d码块或0x55码块。
图17示出了该方式a的修改过程中码块#A码块的变化的示意图。如图17所示，出口PE设备#C可以将码块#A的同步头字段承载的信息从数据类型码块对应的信息(例如，“01”)修改为控制类型码块对应的信息(例如，“10”)。
需要说明的是，方式a中，码块#A可以是0x2d码块也可以是0x55码块，本申请并未特别限定。
方式b
当入口PE设备#B采用上述方式2进行修改时，出口PE设备#C可以将码块#A修改为0x2d码块或0x55
出口PE设备#C可以将码块#A的码块类型字段承载的信息从T码块对应的信息(例如，“0x87”、“0x99”、“0xAA”、“0xB4”、“0xCC”、“0xD2”、“0xE1”、“0xFF”中的任意一种信息)修改为0x2d码块对应的信息(例如，“0x2d”)，或者0x55码块对应的信息(例如，“0x55”)。
需要说明的是，由于在实际传输中可能存在以太网信号中同时存在0x2d码块和0x55码块的情况，此情况下，出口PE设备#C可能无法确定将T码块对应的信息修改为0x2d码块对应的信息还是0x55码块对应的信息。
对此，在本申请中，可以在出口PE设备#C和入口PE设备#B中预先存储映射关系#A。
该映射关系#A可以用于指示0x2d码块与一种T码块(记做：T码块#a)的对应关系，该映射关系#A可以用于指示0x55与另一种T码块(记做：T码块#b)的对应关系。
作为实例而非限定，该T码块#a可以是T6码块，即，该T码块#a可以是码块类型字段对应的信息为“0xE1”。
由于T6码块中可用于承载数据的字节的数量较多，因此通过将0x2d码块修改为T6码块，能够确保修改后的码块不发生信息丢失，从而，进一步提高本申请的效果。
应理解，以上列举的T码块#a的具体实例仅为示例性说明，本申请并未限定于此，该T码块#a可以是T0～T7中任意一种码块，只要确保该T码块#a与T码块#b相异即可。
从而，出口PE设备#C可以根据映射关系#A的指示将T码块#a的码块类型字段承载的信息修改为0x2d码块对应的信息(例如，“0x2d”)。
图18示出了该方式2的修改过程中，T码块#a的变化的示意图。如图18所示，出口PE设备#C可以将以太网信号#B中位于包间隙的T码块#a的0x2d码块的码块类型字段承载的信息从“0xE1”修改为“0x2d”。
可选地，如图19所示，在本申请中，出口PE设备#C还可以将T6码块中的“D0”字节中承载的信息移位至0x2d码块中的“O4”字节中，可以将T6码块中的“D1”字节中承载的信息移位至0x2d码块中的“D5”字节中，可以将T6码块中的“D2”字节中承载的信息移位至0x2d码块中的“D6”字节中，可以将T6码块中的“D3”字节中承载的信息移位至0x2d码块中的“D7”字节中。
并且，出口PE设备#C还可在基于上述修改而生成的0x2d码块中“C0”、“C1”、“C2”和“C03”字节中的填充规定的比特。
作为实例而非限定，该T码块#b可以T7码块，即，该T码块#b可以是码块类型字段对应的信息为“0xFF”。
由于T7码块中可用于承载数据的字节的数量较多，因此通过将0x55码块修改为T7码块，能够确保修改后的码块不发生信息丢失，从而，进一步提高本申请的效果。
应理解，以上列举的T码块#b的具体实例仅为示例性说明，本申请并未限定于此，该T码块#b可以是T0～T7中任意一种码块，只要确保该T码块#a与T码块#b相异即可。
图20示出了该方式b的修改过程中，T7码块的变化的示意图。如图20所示，出口PE设备#C可以将T7码块的码块类型字段承载的信息从“0xFF”修改为“0x55”。
需要说明的是，上述映射关系#A可以是由传送网络中的管理设备确定并下发给各传送设备的，或者，上述映射关系#A也可以是有通信系统或通信协议预先规定的，或者，上述映射关系#A可以是由入口PE和出口PE协商确定的，或者，上述映射关系#A可以是由使用者或管理员输入至入口PE和出口PE中的，或者，上述映射关系#A可以是由制造商或运营商配置在入口PE和出口PE中的，本申请并未特别限定。
方式c
当入口PE设备#B采用上述方式c进行修改时，出口PE设备#C可以将在包间隙中接收到的D码块修改为0x2d码块。并将在包间隙中接收到的T码块修改为0x55码块。
方式d
当入口PE设备#B采用上述方式c进行修改时，出口PE设备#C可以将在包间隙中接收到的D码块修改为0x55码块。并将在包间隙中接收到的T码块修改为0x2d码块。
其中，方式3和方式4中，针对各码块的修改过程可以与方式1或方式2中描述的过程类似，这里，为了避免赘述，省略其详细说明。
需要说明的是，在本申请中，由于出口PE设备#C需要对经过上述修改的码块进行还原，因此，出口PE设备#C所采用的恢复方式需要与入口PE设备#B所采用的修改方式相对应(例如，该恢复方式与修改方式互为逆处理)，以确保还原的准确定。
作为实例而非限定，在本申请中，入口设备#A所采用修改方式可以由通信系统或通信协议预先规定，或者，入口设备#A所采用修改方式可以由出口PE设备#C和入口PE设备#B协商确定，或者，入口设备#A所采用修改方式可以由传送网络的管理设备确定并下发至入口PE设备#B，并且，管理设备可以将于该修改方式对应的恢复方式下发至出口PE设备#C。
在S260，出口PE设备#C可以将经过上述恢复处理而生成的信号(记作，以太网信号#C)发送给客户设备#D，从而，客户设备#D能够基于以太网信号#C获取承载于以太网信号#A中的各信息。
根据本申请提供的方案，能够在不丢失信息的情况下，完成O码块从中低速以太网信号到告诉以太网信号的转换过程。能够实现完全码字透明，不损失原始码块流中的信息
并且，上述码块转换过程为1:1的转码效率，无需额外的比特位开销，不会造成带宽膨胀，不会造成传输资源的浪费。能够实现5GE只占用FlexE的1个5G时隙(slot)，10GE只占用FlexE的2个5G slot，25GE只占用FlexE的5个5G slot。
根据本申请提供的方案，能够完全遵循已有10GBASE-R、25GBASE-R、100GBASE-R的PCS层编码规范，不影响标准的码块处理机制(比如基于IDLE的码块调整机制)。
根据本申请提供的方案，来自客户设备的以太网信号(即，上述中低速以太网信号)在传送网络中可以基于码字透明(codeword transparent)方式传输，码字为由一组若干位二进制代码的组合，码字透明指承载传送某种用户客户信号的传送网络在传输携带该类码字的数据流时不会丢失、篡改用户客户信号数据流中任何码字的信息。
根据前述方法，图21为本申请实施例提供的通信装置10的示意图，如图21所示，该装置10可以为入口传送设备(即，接收设备，例如，出口PE设备)，也可以为芯片或 电路，比如可设置于入口传送设备的芯片或电路。
通信装置10可以包括处理单元11(即，处理单元的一例)和存储单元12。该存储单元12用于存储指令，该处理单元11用于执行该存储单元12存储的指令，以使该10实现如上述方法中传送设备(即，接收设备，例如，出口PE设备#C)执行的步骤。
进一步的，该装置10还可以包括输入口13(即，通信单元的一例)和输出口14(即，通信单元的另一例)。进一步的，该处理单元11、存储单元12、输入口13和输出口14可以通过内部连接通路互相通信，传递控制和/或数据信号。该存储单元12用于存储计算机程序，该处理单元11可以用于从该存储单元12中调用并运行该计算计程序，以控制输入口13接收信号，控制输出口14发送信号，完成上述方法中终端设备的步骤。该存储单元12可以集成在处理单元11中，也可以与处理单元11分开设置。
可选地，若该通信装置10为传送设备，该输入口13为接收器，该输出口14为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该通信装置10为芯片或电路，该输入口13为输入接口，该输出口14为输出接口。
作为一种实现方式，输入口13和输出口14的功能可以考虑通过收发电路或者收发的专用芯片实现。处理单元11可以考虑通过专用处理芯片、处理电路、处理单元或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的接收设备。即将实现处理单元11、输入口13和输出口14功能的程序代码存储在存储单元12中，通用处理单元通过执行存储单元12中的代码来实现处理单元11、输入口13和输出口14的功能。
在一种实现方式中，输入口13用于从传送网络接收包括多个码块的第一速率模式的码块流；处理单元11用于从该码块流中确定目标码块，其中，该目标码块是该接收设备在该码块流的包间隙内接收到的码块，该目标码块包括第一目标码块，该第一目标码块为数据类型的码块；和/或该目标码块包括第二目标码块，该第二目标码块为结束类型的码块，处理单元11用于对该目标码块进行修改，以将该目标码块修改为第二速率模式的有序集类型的码块，该第二速率模式对应的速率小于该第一速率模式对应的速率。
可选地，该处理单元11用于根据该码块流中的开始类型的码块，确定该包间隙结束位置；并根据该码块流中的结束类型的码块，确定该包间隙的起始位置。
可选地，该处理单元11用于根据该码块流中的第一结束类型的码块，确定该包间隙的起始位置，该第一结束类型的码块是在传输顺序上位于该开始类型的码块之后的首个结束类型的码块。
可选地，该处理单元11用于将该第一目标码块的同步头字段承载的信息修改为该有序集类型对应的同步头信息；和/或用于将该第二目标码块的码块类型字段承载的信息修改为该有序集类型对应的码块类型信息。
可选地，该处理单元11用于根据该映射关系，将第一结束类型的第二目标码块的码块类型字段承载的信息修改为第一有序集类型对应的信息，其中，该映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，该第一有序集类型与该。
其中，以上列举的装置10中各模块或单元的功能和动作仅为示例性说明，装置10中各模块或单元可以用于执行上述方法中传送设备(例如，出口PE设备#C)所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
该装置10所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
由于有序集类型的码块在包间隙中传输，因此，发送设备可以将有序集类型的码块修改为传送网络能够识别的数据类型码块或结束类型码块，从而，接收设备能够将位于包间隙的数据类型码块或结束类型码块确定为是基于有序集类型的码块修改而成的，进而可以将位于包间隙的数据类型的码块或结束类型的码块修改回有序集类型的码块，从而，既能够确保该有序集类型的码块能够通过传送网络被传输，又能够确保接收设备可靠地识别出该有序集类型的码块，进而，能够提高通信的准确性。
根据前述方法，图22为本申请实施例提供的通信装置30的示意图，如图22所示，该装置30可以为传送设备(即，发送设备，例如，入口PE设备#B)，也可以为芯片或电路，如可设置于网络设备内的芯片或电路。
该装置30可以包括处理单元31和存储单元32。该存储单元32用于存储指令，该处理单元31用于执行该存储单元32存储的指令，以使该装置30实现前述方法中发送设备执行的步骤。
进一步的，该装置30还可以包括输入口33(即，通信单元的一例)和输出口33(即，处理单元的另一例)。
再进一步的，该处理单元31、存储单元32、输入口33和输出口34可以通过内部连接通路互相通信，传递控制和/或数据信号。
另外，可以考虑使用通用计算机的方式来实现本申请实施例提供的网络设备。即将实现处理单元31、输入口33和输出口34功能的程序代码存储在存储单元中，通用处理单元通过执行存储单元中的代码来实现处理单元31、输入口33和输出口34的功能。
该存储单元32用于存储计算机程序。
在一种实现方式中，该处理单元31可以用于从该存储单元32中调用并运行该计算计程序，以根据多个码块的第二速率模式的码块流，确定第一速率模式的码块流，该第二速率模式对应的速率小于该第一速率模式对应的速率，其中，该第二速率模式的码块流中的有序集类型的码块被修改为数据类型的码块，和/或该第二速率模式的码块流中的有序集类型的码块被修改为结束类型的码块；该输出口34用于向传送网络发送该第一速率模式的码块流。
可选地，该有序集类型的码块的同步头字段承载的信息被修改为数据类型对应的同步头信息。
可选地，该有序集类型的码块的码块类型字段承载的信息被修改为结束类型对应的码块类型信息。
可选地，该处理单元31用于根据该映射关系，将第一有序集类型的码块的码块类型字段承载的信息修改为第一结束类型对应的信息，其中，该映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，该第一有序集类型与该第一结束类型相对应，该第一有序集类型是该至少两种有序集类型中的任意一种有序集类型。
其中，以上列举的装置30中各模块或单元的功能和动作仅为示例性说明，装置30中各模块或单元可以用于执行上述方法中传送设备(即，发送设备，例如，入口PE设备#B)所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
该装置30所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
由于有序集类型的码块在包间隙中传输，因此，发送设备可以将有序集类型的码块修改为传送网络能够识别的数据类型码块或结束类型码块，从而，接收设备能够将位于包间隙的数据类型码块或结束类型码块确定为是基于有序集类型的码块修改而成的，进而可以将位于包间隙的数据类型的码块或结束类型的码块修改回有序集类型的码块，从而，既能够确保该有序集类型的码块能够通过传送网络被传输，又能够确保接收设备可靠地识别出该有序集类型的码块，进而，能够提高通信的准确性。
图23是本申请的传送设备(例如，入口传送设备或出口传送设备)的一例的示意性框图。
如图23所示，该传送设备包括一个或多个客户侧接口板41、交换板42和一个或多个FlexE侧接口板43。
其中，客户侧接口板41包括：外部接口411、转码器413和内部接口415。
并且，FlexE侧接口板43包括：内部接口431、转码器433和外部接口435。
当传送设备作为入口PE设备时：
该外部接口411用于从客户设备接收低速以太网信号(例如，速率为5Gps、10Gps或25Gps的信号)。
转码器413用于将该低速以太网信号转换为高速以太网信号(例如，速率为40Gps、100Gps、200Gps或400Gps的信号)。具体地说，转码器413用于将该中低速以太网信号的PCS层码块流中的码块转换为符合高速以太网信号的PCS层传输要求的码块流。
内部接口415用于将该高速以太网信号发送至交换板42。
交换板42用于基于预设的路由规则，将该高速以太网信号转发至该能够将该高速以太网信号路由至出口传送设备的FlexE侧接口板43。
内部接口431用于从转换板42接收高速以太网信号。
外部接口435用于将该高速以太网信号发送至传送网络，例如，FlexE网络。
当传送设备作为出口PE设备时：
外部接口435用于从传送网络，例如，FlexE网络，接收高速以太网信号(例如，速率为40Gps、100Gps、200Gps或400Gps的信号)。
转码器433用于将该高速以太网信号转换为中低速以太网信号(例如，速率为5Gps、10Gps或25Gps的信号)。具体地说，转码器433用于将该高低速以太网信号的PCS层码块流中的码块转换为符合中低速速以太网信号的PCS层传输要求的码块流。
内部接口431用于将该中低速以太网信号发送至交换板42。
交换板42用于基于预设的路由规则，将该中低速以太网信号转发至该能够将该中低速以太网信号路由至目的客户设备的客户侧接口板41。
内部接口415用于从转换板42接收中低速以太网信号。
外部接口411用于将该中低速以太网信号发送至目的客户设备。
其中，当传送设备作为入口PE设备时，该客户侧接口板41(具体地说，是客户侧接口板41中的各模块或单元)的动作可以对应上述输入口13的动作，该转码器413的动作可以对应上述该处理单元11的动作，这里，为了避免赘述省略其详细说明。
例如，转发器可以将以太网信号的PCS层码块流中的码块中的有序集类型的码块的同步头字段承载的信息修改为数据类型对应的同步头信息。
再例如，转发器可以将以太网信号的PCS层码块流中的码块中的有序集类型的码块的码块类型字段承载的信息修改为结束类型对应的码块类型信息。
具体地，转发器可以根据映射关系，将第一有序集类型的码块的码块类型字段承载的信息修改为第一结束类型对应的信息，其中，该映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，该第一有序集类型与该第一结束类型相对应，该第一有序集类型是该至少两种有序集类型中的任意一种有序集类型。
并且，当传送设备作为出口PE设备时，该FlexE侧接口板43(具体地说，是FlexE侧接口板43中的各模块或单元)的动作可以对应上述输出口34的动作，该转码器433的动作可以对应上述该处理单元31的动作，这里，为了避免赘述省略其详细说明。
例如，转码器可以根据该码块流中的开始类型的码块，确定该包间隙结束位置；该接收设备根据该码块流中的结束类型的码块，确定该包间隙的起始位置。
具体地，转发器可以根据该码块流中的第一结束类型的码块，确定该包间隙的起始位置，该第一结束类型的码块是在传输顺序上位于该开始类型的码块之后的首个结束类型的码块。
再例如，转码器可以将该第一目标码块的同步头字段承载的信息修改为该有序集类型对应的同步头信息。
再例如，转码器将该第二目标码块的码块类型字段承载的信息修改为该有序集类型对应的码块类型信息。
具体地说，转发器可以根据该映射关系，将第一结束类型的第二目标码块的码块类型字段承载的信息修改为第一有序集类型对应的信息，其中，该映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，该第一有序集类型与该第一结束类型相对应，该第一结束类型是该至少两种结束类型中的任意一种结束类型。
在本申请中，以太网信号的PCS层码块流中的码块可以包括64比特/66比特码块。
作为示例而非限定，该中低速以太网信号的PCS层码块流中的有序集类型的码块包括码块类型字段承载的信息为0x2d或0x55的码块。
在本申请中，该转发器(流入，转码器413或转码器433)可以由处理器实现。处理器主要用于对通信协议以及通信数据进行处理，以及对整个传送设备进行控制，执行软件程序，处理软件程序的数据，例如用于支持传送设备执行上述方法实施例中所描述的动作。存储器主要用于存储软件程序和数据。
当终端设备开机后，处理器可以读取存储单元中的软件程序，解释并执行软件程序的指令，处理软件程序的数据。
例如，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端设备进行控制，执行软件程序，处理软件程序的数据。本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独 立的处理器，通过总线等技术互联。本领域技术人员可以理解，终端设备可以包括多个基带处理器以适应不同的网络制式，终端设备可以包括多个中央处理器以增强其处理能力，终端设备的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储单元中，由处理器执行软件程序以实现基带处理功能。
应理解，本申请实施例中，该处理器可以为中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种接收码块流的方法，其特征在于，包括：
    接收设备从传送网络接收包括多个码块的第一速率模式的码块流；
    所述接收设备从所述码块流中确定目标码块，其中，所述目标码块是所述接收设备在所述码块流的包间隙内接收到的码块，
    所述目标码块包括第一目标码块，所述第一目标码块为数据类型的码块，和/或
    所述目标码块包括第二目标码块，所述第二目标码块为结束类型的码块；
    所述接收设备对所述目标码块进行修改，以将所述目标码块修改为第二速率模式的有序集类型的码块。
  2. 根据权利要求1所述的方法，其特征在于，在所述接收设备从所述码块流中确定目标码块之前，所述方法还包括：
    所述接收设备根据所述码块流中的开始类型的码块，确定所述包间隙结束位置；
    所述接收设备根据所述码块流中的结束类型的码块，确定所述包间隙的起始位置。
  3. 根据权利要求2所述的方法，其特征在于，所述接收设备根据所述码块流中的结束类型的码块，确定所述包间隙的起始位置，包括：
    所述接收设备根据所述码块流中的第一结束类型的码块，确定所述包间隙的起始位置，所述第一结束类型的码块是在传输顺序上位于所述开始类型的码块之后的首个结束类型的码块。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述接收设备对所述目标码块进行修改，包括：
    所述接收设备将所述第一目标码块的同步头字段承载的信息修改为所述有序集类型对应的同步头信息；和/或
    所述接收设备将所述第二目标码块的码块类型字段承载的信息修改为所述有序集类型对应的码块类型信息。
  5. 根据权利要求4所述的方法，其特征在于，所述接收设备将所述第二目标码块的码块类型字段承载的信息修改为所述有序集类型对应的码块类型信息，包括：
    所述接收设备根据映射关系，将第一结束类型的第二目标码块的码块类型字段承载的信息修改为第一有序集类型对应的信息，其中，所述映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，所述第一有序集类型与所述第一结束类型相对应，所述第一结束类型是所述至少两种结束类型中的任意一种结束类型。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第二速率模式包括5吉比特每秒Gbps模式、10Gbps模式和25Gbps模式中的至少一种模式；
    所述第一速率模式包括40Gbps模式、100Gbps模式、200Gbps模式或400Gbps模式中的至少一种模式。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述码块包括64比特/66比特码块。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述码块包括物理编码 子层PCS码块。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述第二速率模式的有序集类型的码块包括码块类型字段承载的信息为0x2d或0x55的码块。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述传送网络包括灵活以太网FlexE网络。
  11. 一种发送码块流的方法，其特征在于，包括：
    发送设备根据多个码块的第二速率模式的码块流，确定第一速率模式的码块流，其中
    所述第二速率模式的码块流中的有序集类型的码块被修改为数据类型的码块，和/或
    所述第二速率模式的码块流中的有序集类型的码块被修改为结束类型的码块；
    所述发送设备向传送网络发送所述第一速率模式的码块流。
  12. 根据权利要求11所述的方法，其特征在于，所述有序集类型的码块的同步头字段承载的信息被修改为数据类型对应的同步头信息。
  13. 根据权利要求11或12所述的方法，其特征在于，所述有序集类型的码块的码块类型字段承载的信息被修改为结束类型对应的码块类型信息。
  14. 根据权利要求13所述的方法，其特征在于，所述发送设备根据多个码块的第二速率模式的码块流，确定第一速率模式的码块流，包括：
    所述发送设备根据映射关系，将第一有序集类型的码块的码块类型字段承载的信息修改为第一结束类型对应的信息，其中，所述映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，所述第一有序集类型与所述第一结束类型相对应，所述第一有序集类型是所述至少两种有序集类型中的任意一种有序集类型。
  15. 根据权利要求11至14中任一项所述的方法，其特征在于，所述第二速率模式包括5吉比特每秒Gbps模式、10Gbps模式和25Gbps模式中的至少一种模式；
    所述第一速率模式包括40Gbps模式、100Gbps模式、200Gbps模式或400Gbps模式中的至少一种模式。
  16. 根据权利要求11至15中任一项所述的方法，其特征在于，所述码块包括64比特/66比特码块。
  17. 根据权利要求11至16中任一项所述的方法，其特征在于，所述码块包括物理编码子层PCS码块。
  18. 根据权利要求11至17中任一项所述的方法，其特征在于，所述第二速率模式的有序集类型的码块包括码块类型字段承载的信息为0x2d或0x55的码块。
  19. 根据权利要求11至18中任一项所述的方法，其特征在于，所述传送网络包括灵活以太网FlexE网络。
  20. 一种接收码块流的装置，其特征在于，包括：
    收发单元，用于从传送网络接收包括多个码块的第一速率模式的码块流；
    处理单元，用于从所述码块流中确定目标码块，其中，所述目标码块是所述接收设备在所述码块流的包间隙内接收到的码块，所述目标码块包括第一目标码块，所述第一目标码块为数据类型的码块，和/或所述目标码块包括第二目标码块，所述第二目标码块为结束类型的码块，并对所述目标码块进行修改，以将所述目标码块修改为第二速率模式的有序集类型的码块。
  21. 根据权利要求20所述的装置，其特征在于，所述处理单元用于根据所述码块流中的开始类型的码块，确定所述包间隙结束位置；并根据所述码块流中的结束类型的码块，确定所述包间隙的起始位置。
  22. 根据权利要求21所述的装置，其特征在于，所述处理单元用于根据所述码块流中的第一结束类型的码块，确定所述包间隙的起始位置，所述第一结束类型的码块是在传输顺序上位于所述开始类型的码块之后的首个结束类型的码块。
  23. 根据权利要求20至22中任一项所述的装置，其特征在于，所述处理单元用于将所述第一目标码块的同步头字段承载的信息修改为所述有序集类型对应的同步头信息；和/或用于将所述第二目标码块的码块类型字段承载的信息修改为所述有序集类型对应的码块类型信息。
  24. 根据权利要求23所述的装置，其特征在于，所述处理单元用于根据映射关系，将第一结束类型的第二目标码块的码块类型字段承载的信息修改为第一有序集类型对应的信息，其中，所述映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，所述第一有序集类型与所述第一结束类型相对应，所述第一结束类型是所述至少两种结束类型中的任意一种结束类型。
  25. 一种发送码块流的装置，其特征在于，包括：
    处理单元，用于根据多个码块的第二速率模式的码块流，确定第一速率模式的码块流其中，所述第二速率模式的码块流中的有序集类型的码块被修改为数据类型的码块，和/或所述第二速率模式的码块流中的有序集类型的码块被修改为结束类型的码块；
    收发单元，用于向传送网络发送所述第一速率模式的码块流。
  26. 根据权利要求25所述的装置，其特征在于，所述有序集类型的码块的同步头字段承载的信息被修改为数据类型对应的同步头信息。
  27. 根据权利要求25或26所述的装置，其特征在于，所述有序集类型的码块的码块类型字段承载的信息被修改为结束类型对应的码块类型信息。
  28. 根据权利要求27所述的装置，其特征在于，所述处理单元用于根据映射关系，将第一有序集类型的码块的码块类型字段承载的信息修改为第一结束类型对应的信息，其中，所述映射关系用于指示至少两种结束类型与至少两种有序集类型之间的一一映射关系，所述第一有序集类型与所述第一结束类型相对应，所述第一有序集类型是所述至少两种有序集类型中的任意一种有序集类型。
  29. 一种通信设备，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述通信设备执行权利要求1至19中任一项所述的方法。
  30. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至19中任意一项所述的方法。
PCT/CN2019/099111 2018-08-07 2019-08-02 接收码块流的方法、发送码块流的方法和通信装置 WO2020029893A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2021506430A JP7192195B2 (ja) 2018-08-07 2019-08-02 コードブロックストリームの受信方法、コードブロックストリームの送信方法、および通信装置
EP19846007.3A EP3823189A4 (en) 2018-08-07 2019-08-02 METHOD OF RECEIVING A CODE BLOCK STREAM, METHOD OF SENDING A CODE BLOCK STREAM, AND COMMUNICATION DEVICE
KR1020217006267A KR102498937B1 (ko) 2018-08-07 2019-08-02 코드 블록 스트림 수신 방법, 코드 블록 스트림 송신 방법 및 통신 장치
US17/168,502 US11902403B2 (en) 2018-08-07 2021-02-05 Method for receiving code block stream, method for sending code block stream, and communications apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810893109.0A CN110830153B (zh) 2018-08-07 2018-08-07 接收码块流的方法、发送码块流的方法和通信装置
CN201810893109.0 2018-08-07

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/168,502 Continuation US11902403B2 (en) 2018-08-07 2021-02-05 Method for receiving code block stream, method for sending code block stream, and communications apparatus

Publications (1)

Publication Number Publication Date
WO2020029893A1 true WO2020029893A1 (zh) 2020-02-13

Family

ID=69413391

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/099111 WO2020029893A1 (zh) 2018-08-07 2019-08-02 接收码块流的方法、发送码块流的方法和通信装置

Country Status (6)

Country Link
US (1) US11902403B2 (zh)
EP (1) EP3823189A4 (zh)
JP (1) JP7192195B2 (zh)
KR (1) KR102498937B1 (zh)
CN (1) CN110830153B (zh)
WO (1) WO2020029893A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114979311B (zh) * 2022-05-24 2024-09-06 苏州盛科通信股份有限公司 以太网报文控制码块检验方法、装置、服务器及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101399823A (zh) * 2007-09-29 2009-04-01 华为技术有限公司 编码块格式转换的方法和用于编码块格式转换的装置
US9294418B2 (en) * 2012-11-28 2016-03-22 Marvell International Ltd. 64B/66B codec for ethernet applications
CN107786299A (zh) * 2016-08-25 2018-03-09 华为技术有限公司 一种发送和接收业务的方法、装置和网络系统
CN108242969A (zh) * 2016-12-23 2018-07-03 华为技术有限公司 一种传输速率的调整方法及网络设备

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227450B (zh) * 2007-01-16 2013-04-24 华为技术有限公司 一种开销信息的传输方法、系统及设备
JP2009135767A (ja) * 2007-11-30 2009-06-18 Nec Access Technica Ltd 管理機能付き伝送装置、状態管理システム、状態管理方法及び状態管理プログラム
US7995621B2 (en) * 2008-10-01 2011-08-09 Nortel Netwoeks Limited Techniques for time transfer via signal encoding
CN101692633B (zh) * 2009-09-10 2012-12-19 中兴通讯股份有限公司 一种编码/解码的方法及装置
WO2014153784A1 (zh) 2013-03-29 2014-10-02 华为技术有限公司 一种以太网中传输数据的方法、装置及系统
CN103534968B (zh) * 2013-04-01 2016-09-28 华为技术有限公司 一种以太网物理层的编码、解码方法和装置
US9088403B1 (en) * 2014-03-24 2015-07-21 Applied Micro Circuts Corporation Identification codewords for a rate-adapted version of a data stream
CN107786320B (zh) 2016-08-25 2021-06-22 华为技术有限公司 一种发送和接收业务的方法、装置和网络系统
WO2018080566A1 (en) * 2016-10-28 2018-05-03 Intel Corporation Subframe structure and communication procedure for 5g nr-things vehicle to vehicle
CN111788794B (zh) * 2017-12-22 2022-07-08 瑞典爱立信有限公司 用于配置灵活以太网节点的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101399823A (zh) * 2007-09-29 2009-04-01 华为技术有限公司 编码块格式转换的方法和用于编码块格式转换的装置
US9294418B2 (en) * 2012-11-28 2016-03-22 Marvell International Ltd. 64B/66B codec for ethernet applications
CN107786299A (zh) * 2016-08-25 2018-03-09 华为技术有限公司 一种发送和接收业务的方法、装置和网络系统
CN108242969A (zh) * 2016-12-23 2018-07-03 华为技术有限公司 一种传输速率的调整方法及网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3823189A4

Also Published As

Publication number Publication date
KR102498937B1 (ko) 2023-02-10
EP3823189A4 (en) 2021-10-27
JP2021533656A (ja) 2021-12-02
US20210160346A1 (en) 2021-05-27
CN110830153B (zh) 2021-04-09
EP3823189A1 (en) 2021-05-19
US11902403B2 (en) 2024-02-13
KR20210039429A (ko) 2021-04-09
JP7192195B2 (ja) 2022-12-20
CN110830153A (zh) 2020-02-21

Similar Documents

Publication Publication Date Title
WO2017202158A1 (zh) 转发数据的方法和设备
US7519080B2 (en) Fibre channel frame-mode GFP with distributed delimiter
US7684419B2 (en) Ethernet encapsulation over optical transport network
US11563521B2 (en) Method and apparatus for port channelization at physical layer
WO2019029419A1 (zh) 透传业务频率的方法和设备
WO2020181462A1 (zh) 交互时钟同步报文的方法及装置
US11251905B2 (en) Method for receiving code block stream, method for transmitting code block stream, and communications apparatus
CN113330696A (zh) Cpri数据块传输方法和设备
WO2020029893A1 (zh) 接收码块流的方法、发送码块流的方法和通信装置
JP2021533691A (ja) サービスビットストリームを処理する方法及び装置
US20070086479A1 (en) Techniques to buffer traffic in a communications system
WO2022001166A1 (zh) 接口、电子设备和通信系统
CN116455516A (zh) 编码方法、解码方法、装置、设备、系统及可读存储介质
WO2021115215A1 (zh) 一种数据传输方法、通信设备及存储介质
WO2024002188A1 (zh) 用于灵活以太网的方法、网络设备及存储介质
WO2023083175A1 (zh) 报文传输方法及通信装置
WO2023141777A1 (zh) 通信方法及网络设备
EP3664371B1 (en) Switching method and apparatus
JP7346662B2 (ja) データ送信方法および転送デバイス
WO2019023824A1 (zh) 一种比特块流处理、速率匹配、交换的方法和装置
WO2022022724A1 (zh) 比特块的发送方法及装置
WO2022262614A1 (zh) 通信方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19846007

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021506430

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019846007

Country of ref document: EP

Effective date: 20210215

ENP Entry into the national phase

Ref document number: 20217006267

Country of ref document: KR

Kind code of ref document: A