WO2016115927A1 - 一种利用以太网信道传输业务信号的方法及通信设备 - Google Patents

一种利用以太网信道传输业务信号的方法及通信设备 Download PDF

Info

Publication number
WO2016115927A1
WO2016115927A1 PCT/CN2015/091878 CN2015091878W WO2016115927A1 WO 2016115927 A1 WO2016115927 A1 WO 2016115927A1 CN 2015091878 W CN2015091878 W CN 2015091878W WO 2016115927 A1 WO2016115927 A1 WO 2016115927A1
Authority
WO
WIPO (PCT)
Prior art keywords
service signal
signal
service
bandwidth
ethernet
Prior art date
Application number
PCT/CN2015/091878
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 EP15878596.4A priority Critical patent/EP3242430B1/en
Priority to EP19189528.3A priority patent/EP3627736B1/en
Priority to ES15878596T priority patent/ES2760514T3/es
Publication of WO2016115927A1 publication Critical patent/WO2016115927A1/zh
Priority to US15/656,479 priority patent/US10476791B2/en
Priority to US16/669,148 priority patent/US11165698B2/en

Links

Images

Classifications

    • 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/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • 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
    • 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/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H04L1/0011—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding applied to payload information
    • 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/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/0079—Formats for control data
    • H04L1/008—Formats for control data where the control data relates to payload of a different packet
    • 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/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/0086—Unequal error protection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H04L43/028—Capturing of monitoring data by filtering
    • 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]

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and a communication device for transmitting a service signal by using an Ethernet channel.
  • an embodiment of the present invention provides a method for transmitting a service signal by using an Ethernet channel.
  • an embodiment of the present invention provides a method for transmitting a service signal by using an Ethernet channel, where the Ethernet channel includes multiple Ethernet physical coding sub-layer PCS channels, and each Ethernet PCS channel passes through a fixed-length bearer area. Transmitting a service signal, the method comprising: receiving a first service signal and a second service signal; multiplexing the first service signal and the second service signal into a bearer area of an Ethernet PCS channel, where A portion of at least one of the at least one Ethernet PCS channel in the Ethernet channel carries the first traffic signal, and another portion of the at least one bearer zone carries Having the second service signal; transmitting the first service signal and the second service signal carried in a bearer area of the Ethernet PCS channel.
  • the embodiment of the present invention further provides a method for transmitting a service signal by using an Ethernet channel, where the Ethernet channel includes multiple Ethernet physical coding sub-layer PCS channels, and each Ethernet PCS channel passes a fixed length bearer. And transmitting a service signal, the method comprising: receiving a service signal transmitted over the Ethernet channel, wherein the service signal includes a first service signal and a second service signal, at least one of the Ethernet channels A part of at least one bearer area of the network PCS channel carries the first service signal, and another part of the at least one bearer area carries the second service signal; distributing the first service signal and the second Business signal.
  • the communication method and device provided by the embodiments of the present invention can carry multiple service signals to the same bearer area of the same Ethernet PCS channel, and realize multiple service signals sharing the Ethernet channel, so that multiple service signals can share the chain.
  • the resources of the road resources and the interface modules provide the basis for the integration and integration of devices in the multi-technology system, which can improve the utilization of link resources, reduce the number of devices in the metropolitan area network, occupation, power consumption, and maintenance costs.
  • Figure 1 shows the data structure of the data transmitted in the Ethernet
  • Figure 2 is a layer reference model of an Ethernet interface
  • FIG. 3 is a schematic diagram of a method for transmitting data by MII in an Ethernet
  • 4 is a correspondence diagram of a 64B/66B encoded data stream and a code block
  • FIG. 5 is a flowchart of a method for sending a direction according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of an Ethernet frame according to an embodiment of the present disclosure.
  • FIG. 7 is a flowchart of a method for receiving a direction according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a transmission direction communication device according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a receiving direction communication device according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of an Ethernet frame in Embodiment 1 of the present invention.
  • FIG. 11 is a front-end service and a back-end service distribution diagram according to Embodiment 1 of the present invention.
  • FIG. 12 is a schematic diagram of an overhead bearer area in an Ethernet frame structure according to Embodiment 1 of the present invention.
  • FIG. 13 is a system architecture diagram of an embodiment of the first embodiment of the present invention.
  • FIG. 14 is a schematic diagram of a signal received by an RS layer according to Embodiment 1 of the present invention.
  • FIG. 15 is a schematic structural diagram of a signal sent by an RS layer according to Embodiment 1 of the present invention.
  • FIG. 16 is a schematic diagram of a signal received by a RS layer from a PCS layer according to Embodiment 1 of the present invention.
  • FIG. 17 is a schematic structural diagram of a signal received by an RS layer according to Embodiment 1 of the present invention.
  • FIG. 18 is a schematic diagram of an overhead bearer area according to Embodiment 2 of the present invention.
  • FIG. 19 is a schematic diagram of an overhead bearer area according to Embodiment 2 of the present invention.
  • FIG. 20 is a system architecture diagram of an embodiment of a third embodiment of the present invention.
  • FIG. 21 is a schematic diagram of a Cn value indication in Embodiment 3 of the present invention.
  • FIG. 22 is a schematic structural diagram of a frame of an OTN signal sharing Ethernet interface according to Embodiment 3 of the present invention.
  • FIG. 23 is a schematic diagram of a principle of an OTN signal sharing Ethernet interface according to Embodiment 3 of the present invention.
  • Embodiment 4 is a system architecture diagram of an embodiment of Embodiment 4 of the present invention.
  • FIG. 27 is a schematic diagram of an overhead bearer area according to Embodiment 6 of the present invention.
  • FIG. 28 is a schematic diagram of still another embodiment of Embodiment 6 of the present invention.
  • Figure 1 shows how data is transmitted over Ethernet.
  • (A) if there is no data transmission on the interface for a certain period of time, the idle bytes are continuously sent to maintain the normal transmission and reception status of the hardware on both sides of the Ethernet interface.
  • (B) If there is packet data to be transmitted during this period of time, the packet data covers the idle byte for transmission.
  • the packet has a variable length within a certain range, and the idle byte between the two packets is at least 12 bytes, and the length is not limited.
  • Ethernet packet contains the first 7 bytes of the pilot code "0xAA 0xAA 0xAA 0xAA 0xAA 0xAA 0xAA 0xAA”, the 1-byte frame starts with the SFD flag "0xAB”, followed by the 6-byte length destination address, 6-byte length Source address, 2-byte length packet type/length information, at least 46 bytes of packet payload information and padding information bytes (when the payload is less than 46 bytes, padded to 46 bytes with PAD), and finally Is a 4-byte frame check byte used to verify the integrity of the packet.
  • the 7-byte preamble and the frame start byte SFD are not included, and the packet is shortest to 64 bytes and up to 1518 bytes.
  • the preamble and frame start bytes are 72 bytes and 1526 bytes, respectively.
  • An idle byte after the Ethernet packet also known as the Control End Byte (EFD).
  • FIG. 2 shows the layer reference model for the Ethernet interface.
  • the Ethernet includes seven layers: an application layer, a presentation layer, a session layer, a transport layer, a network layer, a link layer, and a physical layer (PHY).
  • the link layer includes a logical link control layer, an Ethernet OAM layer (optional), an Ethernet MAC control layer (optional), and a MAC layer
  • the physical layer includes a Reconciliation Sub-layer (RS), and a physical layer.
  • the RS layer and the PCS layer are connected by a Medium Dependent Interface (MII).
  • MII Medium Dependent Interface
  • the GMII interface is only the object
  • the interface rate is 1 Gbps
  • XGMII is 10 Gbps
  • XLGMII is 40 Gbps
  • CGMII 100 Gbps.
  • the MI logical concept interface matures with the evolution of the interface rate. It is a nibble 4-bit data bit width at 100M, a 1-byte 8-bit data bit width at GE, and a 4-byte 32-bit data bit width at 10GE.
  • the MII interface with super 10G rate has been developed into an abstract logical interface, which is uniformly defined as an 8-byte 64-bit data bit width.
  • the first functional layer of the interface physical layer from top to bottom is RS; the Reconciliation Sublayer reconciles the sublayer, and the RS sublayer connects through the MII interface and other PHY functional layers including sublayers such as the PCS physical coding sublayer to perform data. Transceiver two-way transmission.
  • the MII interface data constructed by the RS reconciliation sublayer transmission direction is mainly based on the data bit width of the MII interface, and the packet data packet is taken from the packet buffer according to the agreed physical interface rate, and the physical code is obtained by determining the MII interface of the rate bit width.
  • the layer transports the Ethernet packet data in parallel, replaces the first byte of the packet preamble with S bytes, fills the control byte information of idle, T, O, etc.
  • the MII interface data format conforms to the physical coding sublayer.
  • the requirements for example, the frame requirements on the 10GE XGMII interface are aligned with the XGMII interface boundary, and the starting byte S can only be placed on the MII first channel.
  • the corresponding MII interface data obtained after receiving and decoding from the encoding sublayer is recovered from the encoding sublayer and the Ethernet packet data is recovered and stored in the packet buffer, and various padding and control byte information are discarded and terminated.
  • TX_EN/TX_ER/TXC on the MII interface is used to indicate the beginning of the first byte of the preamble of the Ethernet packet and the end of the last byte of the packet.
  • the first byte of the preamble is replaced by the /S/ character by the RS, and the first control character after the Ethernet packet is the /T/ character.
  • the byte from the /S/ character to the /T/ character is a data character. Characters other than data characters are control characters, as shown in the left figure below. It should be noted that the 8-bit byte data characters have 0x00 ⁇ 0xFF.
  • control characters such as /I/, /S/, /T/.
  • /I/ has the same meaning as I, and indicates the frame interval idle character byte;
  • S/ has the same meaning as S, which indicates the Ethernet frame start character;
  • T/ has the same meaning as T, and both indicate the Ethernet frame end character.
  • control characters such as /I/, /S/, /T/.
  • I/ has the same meaning as I, and indicates the frame interval idle character byte;
  • S/ has the same meaning as S, which indicates the Ethernet frame start character;
  • /T/ has the same meaning as T, and both indicate the Ethernet frame end character.
  • the common characters for the XGMII interface are shown in the following table.
  • the GMII uses an 8-bit wide and 125MHz clock
  • the XGMII uses a 32-bit wide and 312.5MHz clock
  • XGMII uses the TXC 4-byte to indicate whether the four 8-bit bytes of the 32-bit width data are data characters or control characters, respectively.
  • the 40GE/100GE further extends the MII interface bit width to 64 bits, and only serves as an abstract logical interface. The physical interface format is no longer defined. Subsequent 25GE, 50GE, and 400GE may follow this rule.
  • FIG. 3 shows a schematic diagram of the data sent by the MII interface.
  • TX_CLK is a clock signal sent by the RS layer to the PCS layer
  • TXC is used to indicate the transmission control signal
  • TXD is the transmitted data.
  • the TXC includes a sequence of 0 and 1, with 0 indicating that the corresponding byte transmitted is a data byte and 1 indicates that the corresponding byte transmitted is a control byte.
  • TX_CLK TXC[0:3], TXD[0:7], TXD[8:15], TXD[16:23], TXD [24:31]
  • TXC[0:3] 1000, it means that TXD[0:7] transmits the control byte, while TXD[8:15], TXD[16:23], TXD[24:31]
  • the data bytes are transferred.
  • the data byte is the data that needs to be transferred, and the specific meaning of the control byte is shown in Table 1. For example, if TXC[0:3] indicates that TXD[0:7] is a control byte and TXD[0:7] carries a value of 0xFB, it can be known from Table 1 that TXD[0:7] carries a frame. Start character /S/.
  • the MII transmits information and the encoding method of the PCS layer can cooperate.
  • the 64-bit information required for encoding comes from two consecutive 32-bit wide information of the XGMII interface, or a 64-bit wide information of XL/CGMII, a total of 8 bytes of information, indicated by the TXC information. Whether the byte is a control byte or a data byte.
  • Figure 4 shows the 64b/66b code table.
  • the 64b/66b code block includes 66 bits including a 2-bit sync header and an 8-byte bearer area.
  • the sync header 2 bit indicates 01
  • the 8 bytes following the sync header in the code block are data bytes
  • the sync header 2 bits indicate 10
  • the first byte is used to indicate the codeword structure.
  • D is used to indicate a data byte
  • C is used to indicate a control byte (the specific meaning of the value carried therein is shown in Table 1)
  • 0 indicates padding 0.
  • Ethernet technology Because of the wide range of Ethernet applications, hardware and interface devices have good scale effects that make them cost-effective.
  • the current 40GE, 100GE, NG100GE and next-rate Ethernet interfaces (such as 400GE, 1000GE) will also have a relative cost advantage.
  • the invention designs a multiplexing technology, supports multi-technology system multiplexing to share one link resource, and thus supports device hybrid integration of multi-technology system, and integrates one set of equipment for one set of links for networking, thereby improving equipment Utilization, reduced power consumption, reduced floor space and management and maintenance investment.
  • an embodiment of the present invention provides a method for transmitting a service signal by using an Ethernet channel, where the Ethernet channel includes multiple Ethernet physical coding sub-layer PCS channels, each of which is Ethernet.
  • the network PCS channel transmits traffic signals through a fixed length bearer area, and the method includes the following steps.
  • Step 101 Receive a first service signal and a second service signal.
  • Step 102 The first service signal and the second service signal are multiplexed into a bearer area of an Ethernet PCS channel, wherein at least one of the at least one Ethernet PCS channel of the Ethernet channel A part of the bearer carries the first service signal, and another part of the at least one bearer area carries the second service signal.
  • Step 103 Send the first service signal and the second service signal that are carried in a bearer area of the Ethernet PCS channel.
  • the at least one bearer area includes an overhead bearer area and a payload bearer area, where the bandwidth bearer area carries bandwidth indication information, where the bandwidth indication information is used to indicate the The bandwidth in the payload bearer area occupied by a traffic signal.
  • the bandwidth indication information is bandwidth particle quantity information, where the bandwidth particle quantity information is used to indicate the number of bandwidth particles in the payload bearer area occupied by the first service signal, where each The length of the bandwidth particles is fixed.
  • the first service signal is an Ethernet service signal, or a synchronous digital system SDH service signal, or an optical transmission network OTN service signal, or a general public radio interface CPRI service signal;
  • the second service signal is an Ethernet service signal.
  • the receiving the first service signal and the second service signal includes: sending a service identification signal to a sending end of the first service signal and a sending end of the second service signal, and a clock signal, the first service signal sent by the transmitting end of the first service signal, and the second service signal sent by the sending end of the second service signal, where the service identification signal is The first identifier is sent by the sending end of the first service signal, where the sending end of the second service signal does not send a service signal, and when the service identifier signal is the second identifier, The transmitting end of the second service signal sends the second service signal, where the sending end of the first service signal does not send a service signal, the first identifier corresponds to the first service signal, and the second identifier Corresponding to the second service signal.
  • sending the first service signal and the second service signal that are carried in a bearer area of the Ethernet PCS channel including sending the at least one Ethernet PCS channel At least one bearer area, and a transmit clock signal and an indication signal, the indication signal being used to indicate a pair with the at least one bearer area
  • the alignment should identify the location of the AM.
  • the indication signal is further used to indicate a location of an overhead bearer zone of the at least one bearer zone and a location of a payload bearer zone of the at least one bearer zone.
  • the Ethernet PCS channel is regarded as a container with a fixed capacity, which can be used for mixing and transmitting a variety of service signals, and is of course compatible with the case of transmitting only one service signal.
  • the reconciliation sub-layer RS first receives the service signal.
  • the service signal may be an Ethernet service signal from an upper layer, a CPRI service signal, an OTN signal, an FC service signal of a Fibre Channel (FC), an SDH signal, or any combination of these signals.
  • it can be two or more Ethernet service signals, or an Ethernet service signal and a CPRI service signal.
  • the manner in which the RS receives the corresponding service signal may be received through a separate physical interface, or may be received through a respective logical port.
  • the two service signals are respectively referred to as a first service signal and a second service signal
  • the RS sends a service identification signal and a clock signal to the transmitting end of the first service signal and the transmitting end of the second service signal, and receives the The first service signal sent by the sending end of the first service signal, and the second service signal sent by the sending end of the second service signal, where when the service identification signal is the first identifier,
  • the sending end of the first service signal sends the first service signal, the sending end of the second service signal does not send a service signal, and when the service identification signal is the second identifier, the sending of the second service signal Sending, by the terminal, the second service signal, the sending end of the first service signal does not send a service signal, the first identifier is corresponding to the first service signal, and the second identifier is
  • the second service signal sends a service identification signal and a clock signal to the transmitting end of the first service signal and the transmitting end of the second service signal, and receives the The first
  • the sending end of the first service signal and the sending end of the second service signal are logical sending ends, which may be physically the same hardware component, that is, the hardware component has the first service signal and the second service simultaneously processed.
  • the ability of the signal may also be different hardware components.
  • each Ethernet PCS channel can correspond to one or more service signals.
  • each Ethernet PCS channel can correspond to 0-2 service signals, that is, zero does not carry any service, one carries one clerk, and two carries two services.
  • Each service signal uses a corresponding service identifier, and the service identifier and the identifier carried in the service identifier signal may be the same.
  • the Ethernet PCS channel can correspond to two service signals, one is called a front-end service, and the other is called a back-end service.
  • the corresponding correspondence table can store an identifier of an Ethernet PCS channel, and an identifier of a front-end service.
  • An identifier of the back-end service where the identifier of the front-end service and the identifier of the back-end service correspond to the Ethernet PCS channel identifier.
  • the corresponding sending end of the first service signal or the sending end of the second service signal receives the corresponding service identification signal and the clock signal, if the identifier indicated by the corresponding service identification signal matches the local identifier, then The corresponding service signal is sent to the RS in the corresponding clock cycle. If the identifier indicated by the corresponding service identification signal does not match the local identifier, the service signal is not sent to the RS in the corresponding clock cycle.
  • the RS generates a service identification signal by assigning an identifier in each clock cycle, and broadcasts the signal to the transmitting end of the first service signal and the sending end of the second service signal, so that different transmitting ends can be prevented from being simultaneously sent to the RS.
  • Business signals cause conflicts.
  • 40GE Ethernet can include 4 rows and 16384 columns of 64/66b code block frame structures.
  • the frame structure that is continuous in time constitutes an Ethernet channel.
  • the frame structure of each line is equivalent to an Ethernet PCS channel.
  • the Ethernet rate of other rates is analogous, and the manner of the embodiment of the present invention is also applicable.
  • 100GE Ethernet includes 20 rows and 16384 columns of 64/66b code block frame structures.
  • the 64/66b code block is used as the granularity, and other sizes may also be used.
  • the data block is used as a granularity, such as a granularity of bits, or a granularity of bytes, or a granularity of 10 bytes, etc., which is not limited in the embodiment of the present invention.
  • a length of a 64/66b code block is allocated as AM, and a 64/66b code block overhead (OH) code block is allocated every certain length.
  • OH 64/66b code block overhead
  • the length and position of the AM and OH in the present invention are only examples, and other positions and lengths may be set, depending on the granularity, for example, the length of the AM may be 1, 2, 3, ... OH may also be 1, 2, 3, ... 100 pieces of length.
  • each line can be set, for example, a length of 8192 can be set as one line, and other lengths can be set as one line, which is not limited in the embodiment of the present invention.
  • Each row includes an AM, one or more subframe structures, each subframe including an overhead bearer area OH, and a payload bearer area.
  • the overhead bearer area in the embodiment of the present invention is optional.
  • the static communication service can be configured with no cost. In this case, the sender and the receiver need to be consistent or configured by the network management system.
  • a check field may be included in the overhead bearer area of each row for subsequent verification.
  • each row may also separately reserve a corresponding check field, or each subframe reserves a corresponding check field in the respective payload bearer area.
  • the RS After receiving the corresponding service signal, the RS multiplexes the corresponding service signal into the corresponding payload bearer area.
  • the RS can determine the size of the bandwidth occupied by the corresponding service signal in the payload bearer area or the number of granularities according to the specific multiplexing mode and the bandwidth required by the service signal, and its corresponding position in the payload area.
  • the bandwidth size or the number of granularities occupied by the service signal is determined by the RS according to one or more of a fixed configuration, a network management configuration, a negotiation result, or a predetermined bandwidth allocation policy.
  • the corresponding position of the service signal in the payload area may be directly determined according to a specific multiplexing technique, or may be determined by using a proprietary algorithm, or determined by using a fixed configuration, which is not limited in the embodiment of the present invention.
  • different services may be separately multiplexed into different Ethernet PCS channels.
  • the first service signal is multiplexed to the first Ethernet PCS channel
  • the second service signal is multiplexed to the second Ethernet PCS channel, and so on.
  • an Ethernet PCS channel can carry one service signal, and can also be used to carry multiple service signals, and one service signal can be carried on an Ethernet PCS. It can also be carried in multiple Ethernet PCS channels.
  • an Ethernet PCS channel, or one of the above frame structures may carry a first service and a second service.
  • the first service signal can be carried in multiple Ethernet PCS channels, and the bandwidth of the first service signal is equal to the sum of the bandwidths occupied by the corresponding multiple Ethernet PCS channels. In this way, the service signal in the embodiment of the present invention can occupy any size of bandwidth, and the system flexibility is high.
  • the embodiment of the present invention may further generate corresponding cost information according to the corresponding service, and carry the overhead information in the foregoing overhead bearer area.
  • the specific content of the overhead information is optional according to the specific architecture.
  • the cost information may include one or more of the following information: the size of the occupied bandwidth, the number of occupied granularities, the indication of the change of the bandwidth, the identifier of the Ethernet PCS channel to which it belongs, the indication of the amount of granularity occupied, and the corresponding school. Inspection information, location distribution information of service signals in the payload bearer area, type information of service signals, identification information of service signals, and change information of service signals (such as identification change information of service signals, such as bandwidth adjustment information of service signals) .
  • the overhead information mentioned in all the embodiments of the present invention can be combined with the same, and the overhead information between different embodiments can also be combined with each other.
  • the corresponding overhead information is optional. For static, fixed-configuration services, overhead information may not be needed.
  • the step of adding the corresponding overhead information may be performed by the RS, or may be sent by the RS to the Ethernet PHY layer, and is implemented by the PCS layer of the PHY layer or other layers.
  • the RS may add a corresponding AM and/or overhead bearer, or may fill a fixed padding byte at a corresponding location of the corresponding AM and/or overhead bearer OH, or may be padded at a corresponding location of the AM and/or overhead bearer OH.
  • the idle character is reserved for the PCS layer or other hierarchy of the PHY layer with the actual fixed padding or idle character with the actual AM and/or overhead bearer area OH.
  • the overhead information in the overhead bearer area may be explicit or implicit.
  • the bandwidth occupation information of the first service signal or the amount occupied by the granularity may be selected only in the overhead bearer area, and the remaining bandwidth is used.
  • the number of granularities is occupied by the second service signal by default, which can reduce the overhead information that needs to be transmitted. Inter-grounding increases bandwidth utilization.
  • the bandwidth occupation information of the first service signal and the second service signal or the number of granularity occupied by the first service signal and the second service signal are respectively carried in the overhead bearer area, which can improve the reliability of the overhead information transmission.
  • the RS sends the service signal carried in the bearer area of the Ethernet PCS channel, such as the first service signal and the second service signal, to the PCS of the Ethernet PHY layer. Layer or other level. Or, the service signal carried in the bearer area of the Ethernet PCS channel is also sent, and the corresponding processing device sends the service signal carried in the bearer area of the corresponding Ethernet PCS channel to the transmission link. go with.
  • the transmitting step of the embodiment of the present invention includes: transmitting a data stream encapsulating the corresponding service signal, and transmitting a clock signal and an indication signal, the indication signal being used to indicate that the at least one bearer area is corresponding to
  • the alignment identifies the location of the AM. That is, the RS may simultaneously transmit an indication signal indicating that the AM is transmitted during the current clock cycle within the clock cycle in which the AM is transmitted.
  • the positions of both the AM and the overhead bearer area may be relatively fixed. When the location of the AM is indicated, the location of the corresponding overhead bearer area is correspondingly specified.
  • the indication signal may further indicate that the AM, the overhead bearer, or the payload bearer is transmitted in the current clock cycle.
  • the indication signal is 1, the payload bearer is transmitted in the current clock cycle.
  • the indication signal is 2, the AM is transmitted in the current clock cycle, and when the indication signal is 3, the overhead bearer zone is transmitted in the current clock cycle.
  • the indication signal indicating the payload bearer zone is indicated.
  • the indication signal indicating the overhead bearer area and the indication signal indicating the AM may be any combination of 1-100, or may be any combination of other signal indication manners.
  • the service identification signal sent by the RS to the sending end of the first service signal and the sending end of the second service signal in the embodiment of the present invention may be a signal, or may be a combination of multiple signals, and the RS is sent to the PCS layer.
  • the transmitted indication signal may be one signal or a combination of multiple signals.
  • the indication manner in the following first embodiment can be incorporated herein.
  • the communication method and device described in the embodiments of the present invention can carry multiple service signals to the same bearer area of the same Ethernet PCS channel, and realize a plurality of service signals sharing an Ethernet channel, so that multiple service signals can share the chain.
  • Road resources and interface module resources It provides a basis for device integration and integration of multi-technology systems, which can improve link resource utilization, reduce the number of devices in the metropolitan area network, occupation, power consumption, and maintenance costs.
  • an embodiment of the present invention provides a method for transmitting a service signal by using an Ethernet channel, where the Ethernet channel includes multiple Ethernet physical coding sub-layer PCS channels, and each Ethernet PCS channel has a fixed length.
  • a bearer area for transmitting a service signal the method comprising: receiving a service signal transmitted over the Ethernet channel, wherein the service signal includes a first service signal and a second service signal, at least one of the Ethernet channels Portion of at least one of the Ethernet PCS channels carrying the first service signal, another portion of the at least one bearer area carrying the second service signal; distributing the first service signal and the first Two business signals.
  • the at least one bearer area includes an overhead bearer area and a payload bearer area, where the bandwidth bearer area carries bandwidth indication information, where the bandwidth indication information is used to indicate the a bandwidth in the payload bearer area occupied by a service signal; the distributing the first service signal and the second service signal, including acquiring bandwidth indication information in the overhead bearer area, according to the The bandwidth indication information and the identifier of the first service signal and the identifier of the second service signal that are stored locally generate a service identification signal, a sending clock signal, the service identification signal, and the at least one bearer area, the service identifier The signal is used to indicate a location occupied by the first service signal and the second service signal in the payload bearer area.
  • the bandwidth indication information in the overhead bearer area is bandwidth particle quantity information, where the bandwidth particle quantity information is used to indicate the number of bandwidth particles in the payload bearer area occupied by the first service signal. Wherein each of the bandwidth particles has a fixed length.
  • the first service signal is an Ethernet service signal, or a synchronous digital system SDH service signal, or an optical transmission network OTN service signal, or a general public radio interface CPRI service signal;
  • the second service signal is an Ethernet service signal.
  • the method further includes: receiving a clock signal and an indication signal, where the indication signal is used to indicate a location of the overhead bearer area.
  • the PHY layer receives the service signal and sends it to the RS layer, and then the RS layer transmits the signal to the upper layer.
  • the PHY layer such as the PCS layer of the PHY layer
  • the AM is optional, and the AM may not be sent.
  • the cost bearer area is optional, and the corresponding cost information is also optional.
  • the PCS layer While transmitting the service signal to the RS, the PCS layer also sends a clock signal and an indication signal, where the indication signal is used to indicate whether the payload bearer area, whether the payload bearer area (if any) or the AM is transmitted in each clock cycle. If yes).
  • the RS receives the signals in the respective Ethernet PCS channels.
  • the RS can identify the signals of different Ethernet PCS channels through the AM sent by the PCS.
  • the corresponding overhead bearer area can carry the identifier of the corresponding Ethernet PCS channel, and the RS can identify the corresponding Ethernet PCS according to the identifier of the Ethernet PCS channel in the overhead bearer area.
  • the RS After receiving the signal carried in the corresponding Ethernet PCS channel, the RS obtains the bandwidth indication information in the overhead bearer area or determines the payload bearer area according to the bandwidth indication information or the bandwidth allocation information according to the locally stored bandwidth allocation information.
  • the bearer location of the corresponding service signal For example, when the corresponding payload bearer carries the first service signal and the second service signal, the RS generates a service identifier signal by determining the bearer location of each service signal and the identifier of the corresponding service signal stored locally. Then, the RS broadcasts the signal received from the corresponding Ethernet PCS channel to the receiving end of the corresponding first service and the receiving end of the second service, and simultaneously transmits the corresponding clock signal and the corresponding service identification signal. The corresponding receiving end receives the service indicated by the service identification signal and matches its own identity.
  • the embodiment of the present invention further provides a corresponding communication device.
  • the communication device introduced in the embodiment of the present invention is used to perform the method provided in the embodiment of the present invention, and the method introduced in the embodiment of the present invention can be performed by using the communication device provided in the embodiment of the present invention.
  • Communication equipment and methods complement each other, in the party
  • the description in the method embodiment is also applicable to the communication device, and the description of the communication device is also applicable to the corresponding method.
  • the technical means in the corresponding method embodiment can be combined in the communication device, in the corresponding device implementation manner.
  • Technical means can be combined in the corresponding method.
  • an embodiment of the present invention provides a communication device, where the communication device includes: a processing unit, configured to receive a first service signal and a second service signal, and the first service signal and the second The service signal is multiplexed into a bearer area of the Ethernet PCS channel, wherein a portion of at least one of the at least one Ethernet PCS channel of the Ethernet channel carries the first service signal, the at least one The other part of the bearer area carries the second service signal, and the sending unit is configured to send the first service signal and the second service signal that are carried in the bearer area of the Ethernet PCS channel.
  • the at least one bearer area includes an overhead bearer area and a payload bearer area, where the bandwidth bearer area carries bandwidth indication information, where the bandwidth indication information is used to indicate the The bandwidth in the payload bearer area occupied by a traffic signal.
  • the bandwidth indication information is bandwidth particle quantity information, where the bandwidth particle quantity information is used to indicate the number of bandwidth particles in the payload bearer area occupied by the first service signal. Wherein each of the bandwidth particles has a fixed length.
  • the first service signal is an Ethernet service signal, or a synchronous digital system SDH service signal, or an optical transmission network OTN service signal, or a general public radio interface CPRI service signal;
  • the second service signal is an Ethernet service signal.
  • the receiving the first service signal and the second service signal includes: sending a service identification signal to a sending end of the first service signal and a sending end of the second service signal, and a clock signal, the first service signal sent by the transmitting end of the first service signal, and the second service signal sent by the sending end of the second service signal, where the service identification signal is When the first identifier is sent, the sending end of the first service signal sends the first service signal, and the second service signal The transmitting end does not send the service signal, and when the service identification signal is the second identifier, the sending end of the second service signal sends the second service signal, and the sending end of the first service signal does not send the service signal
  • the first identifier corresponds to the first service signal
  • the second identifier corresponds to the second service signal.
  • sending the first service signal and the second service signal that are carried in a bearer area of the Ethernet PCS channel including sending the at least one Ethernet PCS channel At least one bearer area, and a transmit clock signal and an indication signal, the indication signal being used to indicate a location of the alignment identifier AM corresponding to the at least one bearer area.
  • the indication signal is further used to indicate a location of an overhead bearer zone of the at least one bearer zone and a location of a payload bearer zone of the at least one bearer zone.
  • All the methods and steps except the sending step in the embodiment of the present invention may be implemented in the processing unit, and the corresponding processing unit may be used to implement all the steps except the sending step in the above method embodiment.
  • the corresponding processing unit may be a device such as an ASIC, an FPGA, or a CPU, or may be a combination of two or more devices such as an ASIC, an FPGA, or a CPU.
  • the corresponding ASIC, FPGA, CPU, etc. devices include a series of executable instructions that, when executed, cause the corresponding ASIC, FPGA or CPU to perform the corresponding function, or to execute the corresponding method.
  • Corresponding instructions can be stored in a storage medium or cured in a corresponding ASIC or FPGA.
  • the corresponding sending unit may be an interface having a function of transmitting a signal stream connected to the processing unit, or a function module integrating the PMA, the PMD, and the transmitter, and optionally, an FEC function module.
  • the corresponding PMA, PMD, and FEC functions can be integrated into one or more ASICs, FPGAs, or CPUs.
  • an embodiment of the present invention provides a communication device, where the communication device includes: a receiving unit, configured to receive a service signal transmitted by using the Ethernet channel, where the service signal includes a first service signal. And a second service signal, a part of at least one of the at least one Ethernet PCS channel of the Ethernet channel carrying the first service signal, and another part of the at least one bearer area carrying the Second industry a processing unit, configured to distribute the first service signal and the second service signal.
  • the at least one bearer area includes an overhead bearer area and a payload bearer area, where the bandwidth bearer area carries bandwidth indication information, where the bandwidth indication information is used to indicate the a bandwidth in the payload bearer area occupied by a service signal; the distributing the first service signal and the second service signal, including acquiring bandwidth indication information in the overhead bearer area, according to the The bandwidth indication information and the identifier of the first service signal and the identifier of the second service signal that are stored locally generate a service identification signal, a sending clock signal, the service identification signal, and the at least one bearer area, the service identifier The signal is used to indicate a location occupied by the first service signal and the second service signal in the payload bearer area.
  • the bandwidth indication information is bandwidth particle quantity information, where the bandwidth particle quantity information is used to indicate the number of bandwidth particles in the payload bearer area occupied by the first service signal. Wherein each of the bandwidth particles has a fixed length.
  • the first service signal is an Ethernet service signal, or a synchronous digital system SDH service signal, or an optical transmission network OTN service signal, or a general public radio interface CPRI service signal;
  • the second service signal is an Ethernet service signal.
  • the receiving unit is further configured to receive a clock signal and an indication signal
  • the processing unit is further configured to determine a location of the overhead bearer area according to the indication signal.
  • All the methods and steps except the receiving step in the embodiment of the present invention may be implemented in the processing unit, and the corresponding processing unit may be used to implement all the steps except the receiving step in the above method embodiment.
  • the corresponding processing unit may be a device such as an ASIC, an FPGA, or a CPU, or may be a combination of two or more devices such as an ASIC, an FPGA, or a CPU.
  • the corresponding ASIC, FPGA, CPU, etc. devices include a series of executable instructions that, when executed, cause the corresponding ASIC, FPGA or CPU to perform the corresponding function, or to execute the corresponding method.
  • Corresponding instructions can be stored in a storage medium or cured in a corresponding ASIC or FPGA.
  • the corresponding receiving unit may be an interface having a function of receiving a signal stream connected to the processing unit, or a function module integrating the PMA, the PMD, and the receiver, and optionally, an FEC function module.
  • the corresponding PMA, PMD, and FEC functions can be integrated into one or more ASICs, FPGAs, or CPUs.
  • Each logical channel periodically includes an Alignment Marker (AM) for every 16384 64/66b code blocks, and AM is used for synchronization and alignment of all parallel physical coding sub-layer logical channels to recover a single 100GE data stream. Therefore, its interface physical layer has a typical 20-row 16384-column data frame periodic structure. This 20-row 16384-column data frame periodic structure is equivalent to dividing 20 time slots.
  • AM Alignment Marker
  • the 40GE case is similar, with four physical coding sub-layer logical channels (PCS Lane), and its interface physical layer has a typical data frame periodic structure of 4 rows and 16384 columns, which is equivalent to dividing 4 time slots.
  • PCS Lane physical coding sub-layer logical channels
  • PCS Lane 100GE multi-physical coding sub-layer logical channel (PCS Lane) 20 rows of 16384 columns 64/66b code block frame structure, 40GE multi-physical coding sub-layer logical channel (PCS Lane) 4 rows of 16384 columns 64/66b code block frame structure,
  • PCS Lane 40GE multi-physical coding sub-layer logical channel (PCS Lane) 4 rows of 16384 columns 64/66b code block frame structure,
  • a multiplex frame with a length of 16384 for each channel a plurality of multiplexed subframes may be further divided and an overhead is defined. For example, as shown in FIG.
  • each logical channel multiplexed frame further removes the sync alignment code block (Alignment Marker: AM)
  • the 16383 blocks other than the average are divided into 3 multiplex sub-frames, and the first 64/66b code block of each sub-frame (including 8 bytes + 2 bit sync headers, a total of 66 bits) is defined as a sub-frame overhead area.
  • the rest are multiplexed bearer regions, containing 5460 64/66b code blocks, each 64/66b code block or its corresponding 8-character byte before encoding as a distributable bandwidth granule.
  • the 40GE physical layer interface has four physical coding sub-layer logical channels, and each channel has a length of 16384 multiplexed frames that can be differentiated into three multiplexed sub-frames.
  • the bit-multiplexed time slot is divided on the 40GE and 100GE interfaces.
  • the bandwidth on the partial time slots is allocated as needed to multiplex the CPRI interface data, and the remaining bandwidth is completely used for the original Ethernet statistical multiplexing.
  • the transmission of packet data is divided on the 40GE and 100GE interfaces.
  • the data packet is statistically multiplexed with link resources, and the effective traffic is high and low.
  • the system design and network deployment are generally designed according to the peak demand.
  • an invalid idle padding byte is transmitted on the link, which causes waste of resources.
  • a 40GE has only 60% of effective traffic, 40% of its bandwidth is actually wasted.
  • This embodiment describes a case where a fixed rate (CBR) circuit CPRIx20 interface data shares and multiplexes a 40GE physical interface and link with the above-described Ethernet packet data of only 60% of effective traffic.
  • CBR fixed rate
  • Both the fixed rate circuit and the CPRIx20 interface operate at a nominal clock frequency with a nominal interface information rate.
  • CBR track rate rate fixed rate
  • Bandwidth resource allocation is performed according to the 64/66b block.
  • the frame synchronization header of CPRI-20 is originally 20 0x50 bytes.
  • /66b encodes the first byte of the block 8-byte granule. In order to ensure compatibility with 64/66b in this embodiment, it is also required that the character /S/ appears in the first byte of the 8-byte particle of the 64/66b code block.
  • the number of 64/66b block bandwidth particles allocated to 70,912 subframes is 5,369
  • the /66b block bandwidth particle number is 5368.70912.
  • the interleaving and arrangement relationship can be determined by an algorithm. For example, the number of bandwidth particles allocated in each subframe of the first 50 subframes and the interleaving and arrangement relationship can be determined by the following methods:
  • the specific arrangement sequence is: [...5368, 5369, 5369, 5368, 5369, 5369, 5369, 5368...], so the arrangement can reduce the need for caching, and the theoretically effective data buffer accumulation depth can be controlled within 1 .
  • Algorithm 2 The same result can be obtained by Algorithm 2 below.
  • the second step is to solve the problem of allocation and arrangement of bandwidth particles in the sub-frame, and determine whether each particle is allocated to the CPRIx10 interface circuit service or still reserved for the Ethernet statistical multiplexing packet service. In order for the Ethernet statistical multiplexing packet service to be able to use the remaining total link bandwidth resources.
  • the assignment of bandwidth particles within a subframe or the determination of attribution may be determined in the following manner. Let the number of assignable 64/66b particles in the sub-frame be: Pc_subframe, the current subframe needs to be allocated to the 64/66b particle number Cn_subframe of the circuit service; then the allocation arrangement of the 64/66b particles marked as 1 ⁇ Pc_subframe in the sub-frame can be It is determined that the j-th particle is a bandwidth particle allocated to the TDM service if the relationship of mod(j*Cn_subframe, Pc_subframe) ⁇ Cn_subframe is established. Otherwise, it is reserved for Ethernet statistics multiplexing packet services. Thereby solving the problem of shared multiplexing of link resources of the two services.
  • each of the aforementioned sub-frames (5460 particles) needs to allocate 5368 or 5369 bandwidth particles per frame at intervals.
  • the receiver only needs to know the value of Cn_subframe in advance, and can also determine the assignment of each bandwidth particle by the same algorithm rule.
  • clock drift and jitter or other reasons such as adjusting the rate of the CPRIx20 circuit interface to CPRIx10, etc., may be accompanied by slow or fast changes of the Cn_subframe, therefore, the origin needs only need real time.
  • the value of the Cn_subframe corresponding to the subframe is transmitted to the receiving end.
  • the bandwidth particles reserved for the Ethernet service of each physical coding sublayer channel of the 100GE will be uniformly used for multiplexing of Ethernet services.
  • the first subframe of the first channel allocates 5368 particles, and one reserved bandwidth has a granular interval of 58 or 59 allocations.
  • the bandwidth particles, the second sub-frame and the third sub-frame are all allocated 5369 particles, and one reserved bandwidth is separated by 59 allocated bandwidth particles.
  • the third key point is that it is also required to provide a communication mechanism at the two ends of the physical link for indicating the distribution of the bandwidth particles to the receiving end of the physical link. Realize the reliable transmission of the bandwidth particle allocation value Cn_subframe of each sub-frame from the transmitting end to the receiving end.
  • the first 64/66b code block of each subframe of the improved high speed Ethernet physical interface of the present invention is an overhead block. As shown in FIG. 12, the overhead block can be used as a special data block, and the synchronization header is a two-bit data block synchronization header "0b01", and the 8-byte portion is used for the transmission of the Cn_subframe of each subframe from the originating end of the link to the receiving. .
  • the Cn_subframe indicates that Table 6 gives the specific meaning of the Cn_subframe indication.
  • Cn_subframe has two meanings, one is to indicate the amount of bandwidth particles allocated, and the other is to implicitly indicate the amount of bandwidth particles reserved.
  • the Cn_subframe value is zero, indicating that the current sub-frame bandwidth particles are completely reserved.
  • the indication of relative change can also be used to verify and verify that the Cn_subframe is reliably transmitted for verification purposes.
  • the change is generally +1 or -1.
  • Both the originating MII RS Master module and the receiving MII RS Master module have been informed of the type and identification ID of the two services, and are stored in a form or other form for future reference.
  • the CPRI-20 service is transmitted on the allocated bandwidth granules, which is called the front-end service.
  • the original Ethernet statistic multiplexed packet service is transmitted on the reserved bandwidth granules, which is called the back-end service.
  • the table marks the front and rear end service configurations for each channel.
  • the MII RS Master module on the transceiver side controls the transmission and reception of data according to the table.
  • the originating MII RS Master module generates control indication signal signals ⁇ Tx En> and ⁇ Tx ID> under the driving of the transmission clock ⁇ Tx Clk> according to the table contents and the multiplexing frame period.
  • ⁇ Tx En> (0,0), (0,1), (0,2), (0,3) respectively indicate that the bandwidth particles corresponding to the current clock cycle are the sync alignment code blocks AM0 ⁇ of channels 0 to n, respectively.
  • ⁇ Tx ID> has no indication meaning, and the service cannot be transmitted.
  • ⁇ Tx En> (1,1) indicates that the current n bandwidth particles belong to the first subframe.
  • the bandwidth particle data of each channel of the device is arranged and transmitted in the order of Lane_0 ⁇ Lane_n.
  • ⁇ Tx ID> indicates the allocation and retention of the current data block bandwidth.
  • the specific value of ⁇ Tx ID> is determined by the Cn_subframe of the channel and the subframe in which it is located, and the front-end service ID or back-end service configured on the channel is configured. That is, the attribution of bandwidth particles in the clock cycle is indicated.
  • ⁇ Tx ID> 0, which is represented as Ethernet bandwidth granularity
  • ⁇ Tx ID> 1, which is expressed as the bandwidth of the Ethernet.
  • ⁇ Tx Data C> is a time division multiplexing merge of data ⁇ Tx Data A> and ⁇ Tx Data B>.
  • ⁇ Tx Data D>, the last time division multiplexing merge ⁇ Tx Data E> is sent to the physical layer for processing and physical link transmission.
  • En (1,3), 1 is the indication data; 3 is the meaning of the third subframe.
  • the position indication of the synchronization alignment code blocks AM0 to AMn of ⁇ Tx En> and the channels 0 to n has an equivalent meaning.
  • ⁇ Tx Data D> and ⁇ Tx Data E> may not contain meaningful AM0 to AMn data information.
  • the scrambling code processing of the PCS performs scrambling processing on the code blocks other than the AM0 to AMn code blocks.
  • ⁇ Rx Clk> and the corresponding pre-decoded data sequence are obtained, and the PCS synchronizes the code blocks of the channels 0 to n that are not scrambled.
  • AM0 ⁇ AMn are identified, synchronized and aligned.
  • the data sequence is decoded and descrambled to recover the ⁇ Rx Data A> data sequence.
  • ⁇ Rx En> The position indication of the synchronization alignment code blocks AM0 to AMn of the channels 0 to n has an equivalent meaning.
  • the ⁇ Rx Data A> may not contain meaningful AM0 to AMn data information, such as ⁇ Rx Data A in FIG. '>.
  • ⁇ Rx Clk>, ⁇ Rx En>, ⁇ Rx Data A> are sent to the receiving MII RS Master module for processing.
  • the MII RS Master module of the receiving end is based on the ⁇ Rx En> explicit indication indicated by the frame period of the fixed channel alignment codeword, combined with the physical coding sublayer logical channel of the receiving side and the corresponding front end service ID and the backend service ID, by the subframe overhead.
  • the Cn_subframe in OH0 ⁇ OHn determines the assignment of bandwidth particles for each clock cycle.
  • ⁇ Rx Clk>, ⁇ Rx En>, ⁇ Rx ID>, ⁇ Rx Data B> are delivered to the adaptation sublayer of each service interface, and each adaptation sublayer is at ⁇ Rx Clk>, ⁇ Rx En>, ⁇ Rx Receive and extract data of its own under the instruction of ID>.
  • the receiver needs to know the Cn value in a relatively fast manner and determine the sub-location arrangement of its intra-band bandwidth particles. If the receiver cannot complete the calculation to determine the attribution of each bandwidth particle in a sufficiently short time, it is recommended that the overhead block (OverHead) be sent one frame ahead of time. That is, the overhead block in the current subframe corresponds to the bandwidth particle allocation in the next subframe, and so on. The receiver is allowed to react enough time to calculate the assignment of bandwidth particles within the sub-frame.
  • the overhead block (OverHead) be sent one frame ahead of time. That is, the overhead block in the current subframe corresponds to the bandwidth particle allocation in the next subframe, and so on.
  • the receiver is allowed to react enough time to calculate the assignment of bandwidth particles within the sub-frame.
  • hybrid bearer CPRI-10 in a bit multiplexed slot opened by a 100GE Ethernet link will be described below.
  • the frame synchronization header of CPRI-20 is originally 20 0x50 bytes.
  • /66b encodes the first byte of the block bandwidth.
  • CPRI-10 can also adopt the same processing method as the frame synchronization head of CPRI-20. This is 10 0x50 bytes. In order to use 8/10b encoding, the first and second bytes of 0xBC and 0x50/C5 are still reserved as 0x50 bytes, that is, the 8th and 9th are replaced by T/S characters. Bytes (#Z.0.7, #Z.0.8), that is, 64/66b encoding can be used in conjunction with and using Ethernet PCS. There are also three types of encoding blocks involved, which is consistent with CPRI-20. If the CPRI-10 is shared with a 100GE Ethernet statistical multiplexing packet service with a small effective traffic, the 100GE physical interface and link are shared. This embodiment multiplexes the track rate rate fixed rate (CBR) circuit CPRIx10 interface data onto the first physical coding sublayer logical channel (Lane 0) of the nominal rate 100GE physical interface.
  • CBR track rate rate fixed rate
  • Bandwidth resource allocation is performed according to the 64/66b block.
  • the number of 64/66b block bandwidth particles allocated to 70,912 subframes is 5,369
  • the /66b block bandwidth particle number is 5368.70912.
  • the specific implementation manner is basically the same as that in the foregoing embodiment 1. Please refer to FIG. 10 to FIG. 17 , and details are not described herein again.
  • the reserved bytes in the overhead block of the first embodiment, as shown in FIG. 18, can be further used.
  • the encoding information of Cn_subframe and Cn_subframe Change is transmitted three times or more. It is also possible to simultaneously transmit the binary original value and the binary inverse value to the same bit (the inverse of binary 1 is 0, and the inversion is 1) to ensure reliable Cn. Transmission and detection of errors.
  • the code is as follows.
  • Cn_subframe and Cn_subframe Change can ensure reliable transmission and reception of Cn_subframe and Cn_subframe Change according to the principle of majority agreement.
  • the shared multiplexed physical layer interface is a codec using 8b/10b
  • the current frame sync header byte definition of CPRIx10 can be reserved.
  • the pre-encoding information rate of the interface of the OTN OTU2/ODU2 is higher than that of the 10GE Ethernet interface. It is also higher than the pre-encoding information rate of the physical coding sub-layer channel of a 10G bandwidth in 40GE, and two 5G in 100GE. The total pre-encoding information rate of the physical coding sub-layer channel of the bandwidth is high. As a result, ODU2 or OTU2 cannot be multiplexed into a 10G bandwidth physical coding sublayer channel of 40GE at the nominal rate, and the 10GE physical interface of the nominal rate cannot be reused for transmission. deal with. This embodiment uses two physical coding sublayer channels in 40GE.
  • the OTU2 signal is used as a typical TDM signal.
  • This embodiment describes multiplexing and multiplexing the OTU2 signal with the statistical multiplexing packet Ethernet to a 40GE interface.
  • This embodiment uses two physical coding sublayer logical channels lane 1+lane 2 in 40GE.
  • OTN OTU2 is used as the front-end service on the two channels.
  • the transceiver receives such configuration information or determines the service ID configuration table through protocol negotiation, as shown in FIG.
  • each sub-frame needs to allocate 5824 or 5825 64/66b code blocks of bandwidth for the OTU2 signal, which has exceeded the total number of distributable bandwidth particles per cell (5460), which needs to be cascaded.
  • a 40GE physical coding sublayer channel (time slot) is used for bandwidth particle allocation.
  • Cn_subframe is the sum of the Cn values of the two channels.
  • Cn_subframe Cn2+Cn1.
  • the two ways are equivalent. Taking mode 1 as an example, the distribution is as shown in FIG. 21, which is more uniform than mode 2. Here is a recommended way.
  • the first channel Lane01 is fully allocated.
  • the second channel Lane02 timely supplements a bandwidth particle required for a unit of time, and 364 or 365 particles are evenly distributed in the sub-frame.
  • the OTN combines the physical layer to perform scrambling processing on data other than the FAS to perform framing.
  • the original structure of the OTU2 frame may be reserved, and the task of the framing is performed by the OTN RS; or the MII RS Master module of the present invention may cooperate with the 64/66b encoding function of the physical coding sublayer to perform OTU.
  • the framing indication of the frame As indicated in Figure 22, the first two bytes of the OTU2 frame will be.
  • OA1, OA1 is replaced by the T/S character matched by the 64/66b encoding function of the physical coding sublayer, indicating the start and end of the frame.
  • the former as shown by Tx Data C1, has only one type of coded block, the latter is shown by Tx Data C2, and the coded block type is three.
  • the transmission direction OTN RS can simply replace the first two bytes of the FAS field in the frame of OUT1 with /T/, /S/ characters, and then pass the 8-byte 64-bit TXD/RXD data bits.
  • the MII interface of the wide and 8-bit TXC/RXC is sent to the physical layer function such as the 64/66b physical coding sublayer for encoding and transmission; in the receiving direction, the MII receives the MII interface data of the physical layer decoding output, and recovers /T/, /
  • the S/character is the two OA1 bytes of the original FAS, thereby restoring the OTU1 frame.
  • the data sent on the MII interface follows the rule that the S character appears on the first byte TXD/RXD[0:7].
  • the former does not have this special requirement for all OTU1 frames to be treated as data bytes.
  • the situation with the CPRI interface is similar.
  • the FEC overhead included in the OTN frame is optional in the present embodiment. Because the FEC belongs to the task of the physical interface layer, the lower layer of the embodiment has an optional FEC function for ensuring the transmission error performance of the system.
  • the front-end service ID and the back-end background service ID are marked to lay the foundation for multiple services to share one physical interface link.
  • the interface can multiplex three logical Ethernet statistical multiplexing packet services, CBR CPRI services, CBR OTN services, and statistical multiplexing Fibre Channel services.
  • Each service allocates different service IDs and allocates them to different Ethernet physical coding sub-layer logical channels as front-end services or back-end background services.
  • Fiber Channel FC itself is also a packet-based technology, but it can be handled as a CBR circuit according to its physical interface rate, or it can be treated as a packet statistical multiplexing service like Ethernet, depending on Application scenarios and implementation requirements for FC RS functional modules. It is assumed here that the Fiber Channel is the CBR service of different rate grades such as FC-1G ⁇ 2G ⁇ 4G ⁇ 8G. That is, the FC, CPRI, and OTN services here are all CBR circuit services.
  • Cn_subframe In the vicinity of the expected value of one FC-2G, it is switched to change near the expected value of the FC-4G.
  • the interface rate difference is at least 9G, and the maximum difference is 300G.
  • the need for packet statistical multiplexing of the bandwidth of some intermediate particles, such as 30G, 80G, etc., is difficult to meet.
  • the present invention divides a physical coding sub-layer logical channel into a high-speed interface, and introduces a front-end logical sub-port and a back-end logical sub-port on a combination of channels or channels, that is, the channel or channel group bandwidth can be realized by Cn_subframe.
  • the Cn_subframe combines the characteristics of the packet statistical multiplexing Ethernet service.
  • the Cn_subframe can be consistent with the foregoing embodiment, varies around an approximated expected value, and is explicitly indicated in the overhead. The explicit indication helps the system to implement the lossless service in the system. Bandwidth adjustment control.
  • the Cn_subframe is a fixed value, which is configured or negotiated at both ends of the physical interface.
  • the Cn_subframe does not need to be transmitted in the overhead. Therefore, the overhead block may not exist, and the bandwidth particles in which the overhead block is located may be allocated or retained as distributable particles.
  • the reserved bandwidth may also be allocated or reserved in accordance with the subframe, or may be allocated or reserved for the entire multiplexed frame of 16384 granular length. Without Cn_subframe transmission indication, the system can only be set to static configuration. Therefore, when the bandwidth adjustment is performed, that is, when the Cn_subframe needs to be changed, it is more difficult for the transceiver to perform synchronous matching.
  • the transceiver end performs data multiplexing and demultiplexing based on the explicit Cn_subframe, Cn_subframe Change information, front-end service ID information, and back-end service ID information in the subframe overhead, ensuring matching and synchronization of transmission and reception.
  • the negotiation of the service ID of the shared-multiplexed end of the link needs to be negotiated through other means, such as a control plane protocol or a management plane protocol.
  • a control plane protocol or a management plane protocol.
  • the management plane is fixed statically, and changes are not allowed during the service startup, otherwise it will be difficult to accurately demultiplex.
  • Cn_subframe and Cn_subframe Change are fixed static values, as described in Embodiment 5, the overhead block does not need to exist, and 16383 particles per multiplex frame (5,461 particles per subframe) Allocation and retention can be performed, and the fixed Cn_subframe value can be negotiated by the protocol at both ends of the transceiver or statically configured by the management plane.
  • the CBR service analyzes the value of the Cn_subframe and its sequence change according to the nominal rate.
  • interfaces such as Ethernet, CPRI, and Fibre Channel allow absolute frequency differences of +/-100 ppm from the nominal frequency, SDH and OTN. Allows an absolute frequency difference of +/-20ppm from the nominal frequency.
  • Cn_subframe depends on the specific real rate of the CBR circuit interface to determine.
  • the sub-frame of the shared multiplexed Ethernet physical layer interface can allocate 64/66b particle number: Pc.subframe, 64/66b particle number Po.subframe for overhead; sub-frame frequency F.subfame; then channel equivalent 64/66b code line bandwidth particle rate is
  • C.subframe (Pc.subframe+Po.subframe)*F.subfame.
  • C.cbr has a correspondence with the clock of the service CDR recovery.
  • the C.subframe has a corresponding relationship with the local reference clock of the shared multiplex physical layer interface.
  • the CBR circuit service enters the clock isolation FIFO buffer memory under the recovered clock ticks, and then fetches and leaves the clock isolation FIFO buffer memory as needed according to the local reference clock.
  • N and K are positive integers.
  • Choosing the appropriate N/K value is beneficial to the realization of the system, avoiding the circuit such as the counter working at a certain frequency allowed. Within the scope.
  • the receiving end can recover the clock of the circuit service from the line CDR clock of the receiving end by the relationship between Cn_subframe and (Pc.subframe+Po.subframe).
  • Method 2 Adjust the Cn_subframe to track its changes by monitoring the change in the queue length of the FIFO buffer or the change in the write address of its FIFO buffer.
  • the data is written to the clock isolation FIFO buffer under the clock ticks recovered by the CDR.
  • the FIFO length changes, and the same manner as in the first mode, C.cbr can be obtained. *N/K information, thus obtaining Cn_subframe, and let Cn_subframe follow the data queue write address and its change, FIFO length changes and change, to ensure that the value of Cn_subframe matches the real rate of business data and can track its change.
  • Mode 2 applies not only to CBR circuit services, but also to VBR statistical multiplexing packet services.
  • the Cn_subframe and its changes, front-end and back-end service ID configurations are explicitly transmitted, the Cn_subframe and front-end back-end service IDs can be changed on demand in real time.
  • the bandwidth of each service does not have similar strict constraints on CBR circuit services. It may be explicitly transmitted by Cn_subframe.
  • the front-end and back-end service IDs are implicitly indicated, and are not transmitted in real time. The way. In this case, the channel can be increased or decreased as follows.
  • the front-end service and the back-end service can adjust the Cn_subframe as needed to allocate bandwidth between the front-end service and the back-end service.
  • the ID configuration can be adjusted and modified.
  • the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes the steps of the foregoing method embodiment; and the foregoing storage medium includes: A variety of media that can store program code, such as ROM, RAM, disk, or optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Small-Scale Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例提供一种通信方法及设备，可以将多个业务信号承载到同一以太网PCS通道的同一承载区中，实现了多种业务信号共用以太网信道，从而多种业务信号能共享链路资源和接口模块资源，为多技术体制的设备融合集成提供了基础，可以提高链路资源利用率，降低城域网的设备数量，占地，功耗，维护成本等。

Description

一种利用以太网信道传输业务信号的方法及通信设备 技术领域
本发明涉及通信技术领域，具体涉及一种利用以太网信道传输业务信号的方法及通信设备。
背景技术
随着通信技术的发展，先后出现了同步数字体系SDH，光传送网络OTN、通用公共无线电接口CPRI、以太网等不同的体系。在城域网中，业务需求复杂，往往是多种设备互相竞争也互相补充，导致城域网中存在多套并行或平行运行的多套设备，例如甚至在一个机房中就同时存在一套SDH设备，一套OTN设备，一套以太网交换机或者路由器等分组设备，相应的配备多条链路，但设备和链路的资源利用率都不高，普遍在30％左右甚至更低，多套设备占用比较多的机房空间，引入了比较大的电源功率消耗、耗费多套人员进行维护管理，已经成为了城域网需要重点考虑和解决的问题。
发明内容
有鉴于此，本发明实施例提供一种利用以太网信道传输业务信号的方法。
一方面，本发明实施例提供一种利用以太网信道传输业务信号的方法，所述以太网信道包括多个以太网物理编码子层PCS通道，每个以太网PCS通道通过长度固定的承载区来传输业务信号，所述方法包括：接收第一业务信号和第二业务信号；将所述第一业务信号和所述第二业务信号复用到以太网PCS通道的承载区中，其中，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载 有所述第二业务信号；发送承载于所述以太网PCS通道的承载区中的所述第一业务信号和所述第二业务信号。
另一方面，本发明实施例还提供一种利用以太网信道传输业务信号的方法，所述以太网信道包括多个以太网物理编码子层PCS通道，每个以太网PCS通道通过长度固定的承载区来传输业务信号，所述方法包括：接收通过所述以太网信道传输的业务信号，其中，所述业务信号包括第一业务信号和第二业务信号，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载有所述第二业务信号；分发所述第一业务信号和所述第二业务信号。
本发明实施例所提供的通信方法及设备，可以将多个业务信号承载到同一以太网PCS通道的同一承载区中，实现了多种业务信号共用以太网信道，从而多种业务信号能共享链路资源和接口模块资源，为多技术体制的设备融合集成提供了基础，可以提高链路资源利用率，降低城域网的设备数量，占地，功耗，维护成本等。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图做一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领保护域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为以太网中传输数据的数据结构；
图2为以太网络接口的层参考模型；
图3为以太网中MII发送数据的方法示意图；
图4为64B/66B编码数据流与码块对应关系图；
图5为本发明实施例发送方向方法的流程图；
图6为本发明实施例提供的以太网帧结构示意图；
图7为本发明实施例接收方向方法的流程图；
图8为本发明实施例发送方向通信设备示意图；
图9为本发明实施例接收方向通信设备示意图；
图10为本发明实施例一中的以太网帧结构示意图；
图11为本发明实施例一中前端业务和后端业务分布图；
图12为本发明实施例一中以太网帧结构中开销承载区示意图；
图13为本发明实施例一中实施方式的系统架构图；
图14为本发明实施例一中RS层接收信号的示意图；
图15为本发明实施例一中RS层发送的一种信号的结构示意图；
图16为本发明实施例一中RS层接收来自PCS层的信号的示意图；
图17为本发明实施例一中RS层接收到的一种信号的结构示意图；
图18为本发明实施例二中开销承载区示意图；
图19为本发明实施例二中开销承载区示意图；
图20为本发明实施例三中实施方式的系统架构图；
图21为本发明实施例三中Cn值指示情况示意图；
图22为本发明实施例三中OTN信号共用以太网接口的帧结构示意图；
图23为本发明实施例三中OTN信号共用以太网接口的原理示意图；
图24为本发明实施例四中实施方式的系统架构图；
图25为本发明实施例五中实施方式的系统架构图；
图26为本发明实施例五中又一实施方式的系统架构图；
图27为本发明实施例六中开销承载区示意图；
图28为本发明实施例六中又一实施方式示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是 全部的实施例。基于本发明中的实施例，本领保护域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
图1给出了以太网中传输数据的方式。如图1所示，(A)在某一段时间内接口无数据发送，则连续发送空闲字节，以维持以太网接口两侧的硬件的正常发送和接收状态。(B)如果在这一段时间内有分组数据需要传输，则分组数据覆盖空闲字节进行发送。分组具有一定范围内的可变长度，两个分组之间的空闲字节，至少12字节，长度不限。
如图1所示，以太网分组的典型封装如下，以8位元组(字节)为基本单位。一个以太网分组中先后包含前7字节的导码”0xAA 0xAA 0xAA 0xAA 0xAA 0xAA 0xAA”，1字节的帧开始SFD标记”0xAB”，随后是6字节长度目的地址，6字节长度的源地址，2字节长度的分组类型/长度信息，至少为46字节的一定长度的分组载荷信息及填充信息字节(载荷不足46字节的时候，用PAD填充至46字节)，最后是4字节的帧校验字节，用于校验分组的完整性。不包含7字节前导码和帧开始字节SFD，分组最短为64字节，最长为1518字节。包含前导码和帧开始字节则分别为72字节和1526字节。以太网分组之后的一个空闲字节，作为控制字节又称为帧结束定界(EFD)。
图2给出了以太网络接口的层参考模型。如图2所示，以太网包括应用层、表示层、会话层、传输层、网络层、链路层、物理层(PHY)七个层次。其中，链路层包括逻辑链路控制层、以太网OAM层(可选)、以太网MAC控制层(可选)、MAC层，物理层包括调和子层(Reconciliation Sub-layer，RS)，物理编码子层(Physical Coding Sub-layer，PCS)，FEC层(可选)、物理媒质连接子层(Physical Medium Attachment，PMA)和物理媒质相关子层(Physical Medium Dependent，PMD)。RS层和PCS层之间通过媒质不相关接口(Medium Dependent Interface，MII)连接。自100M以太网开始，逐渐形成了概念稳定的MII逻辑接口，随速率的提升而右不同的命名。GMII接口只的是物 理接口速率为1Gbps，XGMII为10Gbps，XLGMII为40Gbps，CGMII为100Gbps等。MI逻辑概念接口随着接口速率的演进而成熟完善，100M时为半字节4比特数据位宽，GE时为1字节8比特数据位宽，10GE时为4字节32比特数据位宽，超10G速率的MII接口则已经发展为抽象逻辑接口，统一定义为8字节64比特数据位宽。
典型地，接口物理层自上而下的第一个功能层次为RS；Reconciliation Sublayer调和子层，RS子层通过MII接口和包含PCS物理编码子层等子层的其他PHY功能层连接，进行数据的收发双向传输。RS调和子层发送方向所构造的MII接口数据，主要为根据MII接口的数据位宽，按照约定的物理接口速率从分组缓存中取分组数据包并通过确定速率位宽的MII接口向物理编码子层并行输送出以太网分组数据，替换分组前导码首字节为S字节，在没有分组传输的时候填充空闲、T、O等控制字节信息，并保证MII接口数据格式符合物理编码子层的要求，例如10GE XGMII接口上的帧要求与XGMII接口边界对齐，开始字节S只能放在MII第一通道上。在接收方向上，将通过MII接口从编码子层获得接收解码后到得的对应的MII接口数据恢复出以太网分组数据并存储到分组缓存，丢弃和终止各种填充和控制字节信息。
MII接口上TX_EN/TX_ER/TXC用于指示以太网分组的前导码第一字节的开始和分组最后一个字节的结束。前导码的第一字节被RS替换为/S/字符，以太网分组后的第一个控制字符为/T/字符。从/S/字符开始到/T/字符之间的字节为数据字符。数据字符之外的字符为控制字符，如下左图所示。需要指出的是，8位元字节数据字符有0x00～0xFF 256种信息组合合法，而控制字符只有少数几种组合合法，例如/I/、/S/、/T/等控制字符。/I/与I含义相同，均表示帧间隔空闲字符字节；/S/与S含义相同，均表示以太网帧开始字符；/T/与T含义相同，均表示以太网帧结束字符。例如，XGMII接口的常见字符如下表所示。
表1
Figure PCTCN2015091878-appb-000001
Figure PCTCN2015091878-appb-000002
GMII采用8比特位宽和125MHz的时钟，XGMII采用32比特位宽和312.5MHz的时钟。XGMII则用TXC 4位元组来指示32比特位宽数据的4个8位元字节分别是数据字符还是控制字符。40GE/100GE则进一步将MII接口位宽扩展到64bit，并仅作为抽象的逻辑接口，不再定义物理接口形式，后续的25GE、50GE、400GE等将可能沿用这一规则。
图3给出了MII接口发送数据的示意图。图中TX_CLK中为RS层发送给PCS层的时钟信号，TXC为用于指示传送控制信号，TXD为传送的数据。TXC中包括0和1的序列，0表示传送的相应字节为数据字节，1表示传送的相应字节为控制字节。如图3所示，在10G XGMII接口32比特数据位宽的情况下，TX_CLK、TXC[0:3]、TXD[0:7]、TXD[8:15]、TXD[16:23]、TXD[24:31]从RS层向PCS层并行传送。例如，当TXC[0:3]的值为1000时，表示TXD[0:7]传送的是控制字节，而TXD[8:15]、TXD[16:23]、TXD[24:31]传送的是数据字节。64位宽的情况、以及接收方向的情况以此类推。数据字节为需要传送的数据，而控制字节的具体含义见表1。例如，如果TXC[0:3]指示TXD[0:7]为控制字节，而TXD[0:7]承载的值为0xFB，通过表1即可以知道TXD[0:7]承载的是帧开始字符/S/。
这种MII传送信息的方式与PCS层的编码方式可以相互配合。 如对于64b/66b编码，编码所需的64比特信息来自XGMII接口两个连续的32位宽信息，或者是XL/CGMII的一个64位宽信息，共8字节信息，由TXC信息指示每个字节是控制字节还是数据字节。由于/S/,/O/等字节被限制在MII接口的第一个字节通道上，40GE、100GE延续使用64b/66b编码，但由于采用了64位宽的MII接口，并限定/S/字符的位置在XLGMII/CGMII接口8字节的第一个字节，所以对应的64b/66b PCS编码块的种类有所减少，总共只有12种编码块。
图4给出了64b/66b编码表。64b/66b码块包括66比特，其中包括一个2比特的同步头和8个字节的承载区。当同步头2比特指示为01时，该码块中同步头后面的8个字节均为数据字节；当同步头2比特指示为10时，该码块中同步头后面的8个字节为控制字节和数据字节的组合，这时第一个字节用于指示码字结构。图4的编码表中，D用于指示数据字节，C用于指示控制字节(其中承载的值的具体含义见表1)，0表示填充0。
以上即为以太网技术的基本情况。因为以太网应用广泛，硬件和接口器件具有良好的规模效应而使得成本及其低廉。当前40GE，100GE，NG100GE以及下一速率以太网接口(例如400GE、1000GE)也将具备相对而然的地成本优势。
本发明设计一种复用技术，支持多技术体制复用共享一个链路资源，也从而支持多技术体制的设备混合集成，以整合的一套设备一套链路用于组网，从而提高设备利用率，降低功耗，减少占地面积和管理维护的投入。
一方面，如图5所示，本发明实施例提供一种利用以太网信道传输业务信号的方法，其特征在于，所述以太网信道包括多个以太网物理编码子层PCS通道，每个以太网PCS通道通过长度固定的承载区来传输业务信号，所述方法包括以下步骤。
步骤101，接收第一业务信号和第二业务信号。
步骤102，将所述第一业务信号和所述第二业务信号复用到以太网PCS通道的承载区中，其中，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载有所述第二业务信号。
步骤103，发送承载于所述以太网PCS通道的承载区中的所述第一业务信号和所述第二业务信号。
其中，结合以上方法，可选的，所述至少一个承载区中包括开销承载区和净荷承载区；所述开销承载区中承载有带宽指示信息，所述带宽指示信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽。进一步可选的，所述带宽指示信息为带宽颗粒数量信息，所述带宽颗粒数量信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽颗粒数量，其中，每个带宽颗粒的长度固定。
其中，结合以上所有实施方式，可选的，所述第一业务信号为以太网业务信号，或同步数字体系SDH业务信号，或光传送网络OTN业务信号，或通用公共无线电接口CPRI业务信号；所述第二业务信号为以太网业务信号。
结合以上所有实施方式，可选的，所述接收第一业务信号和第二业务信号，包括：向所述第一业务信号的发送端和所述第二业务信号的发送端发送业务标识信号和时钟信号，接收所述第一业务信号的发送端发送的所述第一业务信号，以及所述第二业务信号的发送端发送的所述第二业务信号，其中，当所述业务标识信号为第一标识时，所述第一业务信号的的发送端发送所述第一业务信号，所述第二业务信号的发送端不发送业务信号，当所述业务标识信号为第二标识时，所述第二业务信号的的发送端发送所述第二业务信号，所述第一业务信号的发送端不发送业务信号，所述第一标识与所述第一业务信号对应，所述第二标识与所述第二业务信号对应。
结合以上所有实施方式，可选的，发送承载于所述以太网PCS通道的承载区中的所述第一业务信号和所述第二业务信号，包括，发送所述至少一个以太网PCS通道中的至少一个承载区，以及发送时钟信号和指示信号，所述指示信号用于指示与所述至少一个承载区对 应的对齐标识AM的位置。进一步可选的，所述指示信号还用于指示所述至少一个承载区的开销承载区的位置，以及所述至少一个承载区的净荷承载区的位置。
如前所述，请参考图1，传统的以太网中，当无数据发送时，连续发送空闲字节，有数据(数据长度可变)需要传输时，则传输相应的数据。在以太网物理层PHY层中，会去除相应的空闲字节，并每隔固定字节插入相应的对齐标识(Alignment Marker，AM)，以供接收端对齐及恢复数据之用。这种方式中，因为相应的以太网是按照流量峰值配置的，在通常情况下，带宽利用率不足，又不能用于传输其他业务，造成了带宽的浪费。
本发明实施例中，将以太网PCS通道视为容量固定的容器，可用于混传多种业务信号，当然也兼容只传输一种业务信号的情形。
具体的，在发送侧，调和子层RS先接收业务信号。该业务信号可以是来自上层的以太网业务信号、CPRI业务信号、OTN信号、光纤信道(Fiber Channel，FC)的FC业务信号，也可以是SDH信号，还可以是这些信号的任何组合。比如，可以是两个或更多个以太网业务信号，或者是一个以太网业务信号和一个CPRI业务信号。
可选的，这里的RS接收相应的业务信号的方式可以是通过各自独立的物理接口接收，也可以是通过各自的逻辑端口接收。
下面，将对不同逻辑端口的接收方式展开描述。不同的逻辑端口，可以共用一个物理端口。以有两个业务信号的情形为例，其他情形以此类推。这两个业务信号分别称为第一业务信号和第二业务信号，RS向所述第一业务信号的发送端和所述第二业务信号的发送端发送业务标识信号和时钟信号，接收所述第一业务信号的发送端发送的所述第一业务信号，以及所述第二业务信号的发送端发送的所述第二业务信号，其中，当所述业务标识信号为第一标识时，所述第一业务信号的发送端发送所述第一业务信号，所述第二业务信号的发送端不发送业务信号，当所述业务标识信号为第二标识时，所述第二业务信号的发送端发送所述第二业务信号，所述第一业务信号的发送端不发送业务信号，所述第一标识与所述第一业务信号对应，所述第二标识与 所述第二业务信号对应。所述第一业务信号的发送端和所述第二业务信号的发送端为逻辑上的发送端，在物理上可能为同一硬件组件，即该硬件组件具有同时处理第一业务信号和第二业务信号的能力。当然，所述第一业务信号的发送端和所述第二业务信号的发送端也可以为不同的硬件组件。
可选的，RS保存相应的以太网PCS通道与业务信号的对应关系，该对应关系可以存储在一个对应关系表中，也可以以其他方式存储。如每个以太网PCS通道可以对应一个或多个业务信号。在一种实施方式中，每个以太网PCS通道可以对应0-2个业务信号，即，零个即不承载任何业务，一个即承载一个业务员，两个即承载两个业务。各个业务信号分别使用相应的业务标识，该业务标识与上述业务标识信号里携带的标识可以是同一的。可选的，以太网PCS通道可以对应两个业务信号，一个称为前端业务，一个称为后端业务，相应的对应关系表中可以存储一个以太网PCS通道的标识，一个前端业务的标识，一个后端业务的标识，该前端业务的标识、后端业务的标识与该以太网PCS通道标识相对应。
相应的所述第一业务信号的发送端或所述第二业务信号的发送端接收到相应的业务标识信号和时钟信号时，如果相应的业务标识信号指示的标识与本地的标识匹配时，则在相应的时钟周期内向RS发送相应的业务信号，如果相应的业务标识信号指示的标识与本地的标识不匹配，则在相应的时钟周期内不向RS发送业务信号。RS通过在每个时钟周期内分配一个标识形成业务标识信号，广播给所述第一业务信号的发送端和所述第二业务信号的发送端，如此即可避免不同的发送端同时给RS发送业务信号而造成冲突。
以40GE的以太网情况为例，如图6所示，40GE以太网可以包括4行16384列64/66b码块帧结构，其中时间上连续不断的这种帧结构即构成以太网信道，连续不断的每一行的帧结构相当于一个以太网PCS通道。其他速率的以太网情况以此类推，本发明实施例的方式同样适用，比如，100GE以太网包括20行16384列64/66b码块帧结构。本发明实施例中以64/66b码块作为粒度，也可以以其他大小 的数据块作为粒度，如以比特为粒度、或者以字节为粒度，或者以10字节为粒度等等，本发明实施例不做限制。如图6所示，本发明实施例中分配了一个64/66b码块的长度作为AM，并且每隔一定长度分配一个64/66b码块的开销(Overhead，OH)码块。值得说明的是，本发明中AM、OH的长度、位置仅为示例，也可以设置其他位置、长度，视不同的粒度，比如AM的长度可以是1、2、3……100个粒度的长度，OH也可以是1、2、3……100个粒度的长度。每一行的长度是可以设置的，如可以设置一半的长度8192列作为一行，也可以设置其他长度作为一行，本发明实施例不做限制。每一行包括一个AM，一个或多个子帧结构，每个子帧包括一个开销承载区OH，和一个净荷承载区。值得注意的是，本发明实施例中的开销承载区为可选，事实上对于固定配置好的静态业务，可以不需要开销，这种情况下发送端和接收端需要协商一致或者由网管进行配置。此外，可选的，每一行的开销承载区中可以包括相应的校验字段，以供后续校验之用。可选的，在AM、OH、净荷承载区之外，每一行还可以单独预留相应的检验字段，或者每个子帧在各自的净荷承载区中预留相应的校验字段。
RS接收到相应的业务信号后，把相应的业务信号复用到相应的净荷承载区中。RS根据具体的复用方式，以及业务信号所需的带宽可以确定相应的业务信号在净荷承载区中所占用的带宽的大小或者粒度的数量，以及其在净荷区中相应的位置。业务信号占用的带宽大小或者粒度的数量，是RS根据固定配置、网管配置、协商结果或既定带宽分配策略中的一个或多个确定的。业务信号在净荷区中相应的位置，可以根据具体的复用技术直接确定，也可以利用私有的算法确定，或者使用固定的配置确定，本发明实施例不做限制。
可选的，本发明实施例中，可以将不同的业务分别复用到不同的以太网PCS通道中。如将第一业务信号复用到第一以太网PCS通道，将第二业务信号复用到第二以太网PCS通道，以此类推。
可选的，一个以太网PCS通道中可以承载一个业务信号，也可以用于承载多个业务信号，一个业务信号可以承载于一个以太网PCS 中，也可以承载于多个以太网PCS通道中。如一个以太网PCS通道，或者说一个上述的帧结构中可以一部分承载第一业务，另一部分承载第二业务。再如，第一业务信号可以承载于多个以太网PCS通道中，该第一业务信号的带宽等于其在相应的多个以太网PCS通道中所占用的带宽之和。通过这种方式，本发明实施例中的业务信号可以占用任何大小的带宽，系统灵活性高。
可选的，本发明实施例还可以根据相应业务生成相应的开销信息，并将开销信息承载于上述的开销承载区。开销信息的具体内容，根据具体的架构，均为可选。如开销信息中可以包括以下信息中的一项或多项：占用带宽的大小、占用粒度的数量、带宽的变化指示、所属的以太网PCS通道标识、占用的粒度数量的变化指示、相应的校验信息、业务信号在净荷承载区中的位置分布信息、业务信号的类型信息、业务信号的标识信息、业务信号的变更信息(如业务信号的标识变更信息、如业务信号的带宽调整信息)。本发明所有实施例中所提及的开销信息均可结合与此，并且不同的实施例间的开销信息亦可相互结合。
值得注意的是，相应的开销信息是可选的，对于静态的、固定配置的业务，可以不需要开销信息。同时，添加相应的开销信息的步骤可以由RS来完成，也可以由RS发送给以太网PHY层，由PHY层的PCS层或者其他层级来完成，本发明实施例对此不做限制。
RS可以添加相应的AM和/或开销承载区，也可以在相应的AM和/或开销承载区OH的相应位置填充固定填充字节，或者可以在AM和/或开销承载区OH的相应位置填充空闲字符，以留待PHY层的PCS层或其他层级用实际的AM和/或开销承载区OH替代相应的固定填充字节或空闲字符。
值得说明的是，开销承载区中的开销信息可以是显性的，也可以是隐性的。如当一个以太网PCS通道由第一业务信号和第二业务信号两个业务信号占用时，可以选择只在开销承载区承载第一业务信号的带宽占用信息或者粒度占用的数量，而剩余的带宽或粒度的数量即默认为由第二业务信号占用，这种方式可以减少需要传递的开销信息， 间接地提高了带宽利用率。可选的，也可以显性在开销承载区分别承载第一业务信号和第二业务信号的带宽占用信息或者粒度占用的数量，这种方式可以提高开销信息传输的可靠性。
在封装好相应的业务信号后，RS将承载于所述以太网PCS通道的承载区中的业务信号，如所述第一业务信号和所述第二业务信号，发送给以太网PHY层的PCS层或其他层级。或者，发送承载于所述以太网PCS通道的承载区中的业务信号，也可以理解为，相应的处理设备将承载于相应的以太网PCS通道的承载区中的业务信号发送到传输链路中去。对于发送给PCS层的情形，本发明实施例的发送步骤包括发送封装了相应的业务信号的数据流，以及发送时钟信号和指示信号，所述指示信号用于指示与所述至少一个承载区对应的对齐标识AM的位置。也即，RS可在发送AM的时钟周期内，同时发送指示信号指示当前时钟周期内传输的为AM。在存在开销承载区的情况下，可以将AM和开销承载区两者的位置相对固定，在指示了AM的位置的情况，相应的开销承载区的位置也就相应的指定了。可选的，指示信号还可以分别指示当前时钟周期内传输的是AM、开销承载区或是净荷承载区，如当指示信号为1时，则当前时钟周期内传输的是净荷承载区，当指示信号为2时，则当前时钟周期内传输的是AM，当指示信号为3时，则当前时钟周期内传输的是开销承载区，此处仅为举例，指示净荷承载区的指示信号、指示开销承载区的指示信号和指示AM的指示信号可以为1-100的任意组合，或者可以是其他信号指示方式的任何组合。
本发明实施例中的RS向所述第一业务信号的发送端和所述第二业务信号的发送端发送的业务标识信号可以是一个信号，也可以是多个信号的组合，RS向PCS层发送的指示信号可以是一个信号，也可以是多个信号的组合。比如，下述实施例一中的指示方式可以被结合于此。
本发明实施例所介绍的通信方法及设备，可以将多个业务信号承载到同一以太网PCS通道的同一承载区中，实现了多种业务信号共用以太网信道，从而多种业务信号能共享链路资源和接口模块资源， 为多技术体制的设备融合集成提供了基础，可以提高链路资源利用率，降低城域网的设备数量，占地，功耗，维护成本等。
下面本发明实施例将结合附图，阐述接收方向的方法。
如图7所示，本发明实施例提供一种利用以太网信道传输业务信号的方法，所述以太网信道包括多个以太网物理编码子层PCS通道，每个以太网PCS通道通过长度固定的承载区来传输业务信号，所述方法包括：接收通过所述以太网信道传输的业务信号，其中，所述业务信号包括第一业务信号和第二业务信号，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载有所述第二业务信号；分发所述第一业务信号和所述第二业务信号。
结合以上所有实施方式，可选的，所述至少一个承载区中包括开销承载区和净荷承载区；所述开销承载区中承载有带宽指示信息，所述带宽指示信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽；所述分发所述第一业务信号和所述第二业务信号，包括，获取所述开销承载区中的带宽指示信息，根据所述带宽指示信息和本地存储的所述第一业务信号的标识和所述第二业务信号的标识生成业务标识信号，发送时钟信号、所述业务标识信号和所述至少一个承载区，所述业务标识信号用于指示所述第一业务信号和第二业务信号在所述净荷承载区中所占用的位置。进一步可选的，所述开销承载区中的带宽指示信息为带宽颗粒数量信息，所述带宽颗粒数量信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽颗粒数量，其中，每个带宽颗粒的长度固定。
结合以上所有实施方式，可选的，所述第一业务信号为以太网业务信号，或同步数字体系SDH业务信号，或光传送网络OTN业务信号，或通用公共无线电接口CPRI业务信号；所述第二业务信号为以太网业务信号。
结合以上所有实施方式，可选的，所述方法还包括：接收时钟信号以及指示信号，所述指示信号用于指示开销承载区的位置。
接收方向，PHY层接收到业务信号后发送给RS层，然后RS层再将信号往上层传。现有技术中存在从多种PHY层向RS层发送数据的方法，均可用于本发明实施例，本发明对此不予展开。本发明实施例仅描述与现有技术不同的发送方式。本发明实施例中，在PHY层，如PHY层的PCS层往RS层发送业务信号时，AM为可选，即可不发送AM。对于静态配置业务，开销承载区为可选，相应的开销信息亦是可选。PCS层在向RS发送业务信号的同时，还发送时钟信号和指示信号，指示信号用于指示每个时钟周期内发送的具体是净荷承载区，还是开销承载区(如有)，还是AM(如有)。
RS接收相应的各个以太网PCS通道中的信号。比如，RS可以通过PCS发送的AM来识别不同以太网PCS通道的信号。再或者，相应的开销承载区中可以承载相应的以太网PCS通道的标识，RS可以根据开销承载区中的以太网PCS通道的标识来识别相应的以太网PCS。
RS接收到承载于相应的以太网PCS通道中的信号后，获取所述开销承载区中的带宽指示信息或者根据本地存储的带宽分配信息，根据带宽指示信息或带宽分配信息确定净荷承载区中相应的业务信号的承载位置。如，当相应的净荷承载区承载了第一业务信号和第二业务信号时，RS通过确定的各业务信号的承载位置以及本地存储的相应的业务信号的标识生成业务标识信号。然后，RS向相应的第一业务的接收端和第二业务的接收端广播其从相应的以太网PCS通道中接收到的信号，同时发送相应的时钟信号和相应的业务标识信号。相应的接收端接收业务标识信号指示的与自己的标识相匹配的业务。
本发明实施例发送方向和接收方向的方法相辅相成，原理是统一的，相应的技术细节可以相互结合不受限制。
结合以上方法实施方式，本发明实施例还提供相应的通信设备。本领域技术人员可以理解，本发明实施例中介绍的通信设备用于执行本发明实施例中提供的方法，本发明实施例中介绍的方法可以利用本发明实施例中提供的通信设备执行。通信设备与方法相辅相成，在方 法实施方式中的说明同样适用于通信设备，而对于通信设备的描述也同样适用于相应的方法，相应的方法实施方式中的技术手段可以被结合于通信设备中，相应的设备实施方式中的技术手段可以被结合于相应的方法中。
如图8所示，本发明实施例提供一种通信设备，所述通信设备包括：处理单元，用于接收第一业务信号和第二业务信号，将所述第一业务信号和所述第二业务信号复用到以太网PCS通道的承载区中，其中，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载有所述第二业务信号；发送单元，用于发送承载于所述以太网PCS通道的承载区中的所述第一业务信号和所述第二业务信号。
结合以上所有实施方式，可选的，所述至少一个承载区中包括开销承载区和净荷承载区；所述开销承载区中承载有带宽指示信息，所述带宽指示信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽。
结合以上所有实施方式，可选的，所述带宽指示信息为带宽颗粒数量信息，所述带宽颗粒数量信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽颗粒数量，其中，每个带宽颗粒的长度固定。
结合以上所有实施方式，可选的，所述第一业务信号为以太网业务信号，或同步数字体系SDH业务信号，或光传送网络OTN业务信号，或通用公共无线电接口CPRI业务信号；所述第二业务信号为以太网业务信号。
结合以上所有实施方式，可选的，所述接收第一业务信号和第二业务信号，包括：向所述第一业务信号的发送端和所述第二业务信号的发送端发送业务标识信号和时钟信号，接收所述第一业务信号的发送端发送的所述第一业务信号，以及所述第二业务信号的发送端发送的所述第二业务信号，其中，当所述业务标识信号为第一标识时，所述第一业务信号的发送端发送所述第一业务信号，所述第二业务信号 的发送端不发送业务信号，当所述业务标识信号为第二标识时，所述第二业务信号的发送端发送所述第二业务信号，所述第一业务信号的发送端不发送业务信号，所述第一标识与所述第一业务信号对应，所述第二标识与所述第二业务信号对应。
结合以上所有实施方式，可选的，发送承载于所述以太网PCS通道的承载区中的所述第一业务信号和所述第二业务信号，包括，发送所述至少一个以太网PCS通道中的至少一个承载区，以及发送时钟信号和指示信号，所述指示信号用于指示与所述至少一个承载区对应的对齐标识AM的位置。进一步可选的，所述指示信号还用于指示所述至少一个承载区的开销承载区的位置，以及所述至少一个承载区的净荷承载区的位置。
本发明实施例中除了发送步骤以外的所有方法、步骤均可以在处理单元实现，相应的处理单元可用于实现以上方法实施方式中除发送步骤以外的所有步骤。
具体的，相应的处理单元可以是ASIC、FPGA或CPU等器件，也可以是两个或多个ASIC、FPGA或CPU等器件的组合。相应的ASIC、FPGA、CPU等器件中包括系列可执行的指令，当这些指令被执行时会促使相应的ASIC、FPGA或CPU执行相应的功能，或者说执行相应的方法。相应的指令可以被存储于存储介质中或者固化在相应的ASIC或FPGA中。
具体的，相应的发送单元，可以是指与处理单元连接的具有发送信号流功能的接口，也可以指集成了PMA、PMD及发送器的功能模块，可选的，还可以包括FEC功能模块。相应的PMA、PMD及FEC功能可以集成于一个或多个ASIC、FPGA或CPU中。
如图9所示，本发明实施例提供一种通信设备，所述通信设备包括：接收单元，用于接收通过所述以太网信道传输的业务信号，其中，所述业务信号包括第一业务信号和第二业务信号，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载有所述第二业 务信号；处理单元，用于分发所述第一业务信号和所述第二业务信号。
结合以上所有实施方式，可选的，所述至少一个承载区中包括开销承载区和净荷承载区；所述开销承载区中承载有带宽指示信息，所述带宽指示信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽；所述分发所述第一业务信号和所述第二业务信号，包括，获取所述开销承载区中的带宽指示信息，根据所述带宽指示信息和本地存储的所述第一业务信号的标识和所述第二业务信号的标识生成业务标识信号，发送时钟信号、所述业务标识信号和所述至少一个承载区，所述业务标识信号用于指示所述第一业务信号和所述第二业务信号在所述净荷承载区中所占用的位置。
结合以上所有实施方式，可选的，所述带宽指示信息为带宽颗粒数量信息，所述带宽颗粒数量信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽颗粒数量，其中，每个带宽颗粒的长度固定。
结合以上所有实施方式，可选的，所述第一业务信号为以太网业务信号，或同步数字体系SDH业务信号，或光传送网络OTN业务信号，或通用公共无线电接口CPRI业务信号；所述第二业务信号为以太网业务信号。
结合以上所有实施方式，可选的，所述接收单元，还用于接收时钟信号以及指示信号；所述处理单元，还用于根据所述指示信号确定开销承载区的位置。
本发明实施例中除了接收步骤以外的所有方法、步骤均可以在处理单元实现，相应的处理单元可用于实现以上方法实施方式中除接收步骤以外的所有步骤。
具体的，相应的处理单元可以是ASIC、FPGA或CPU等器件，也可以是两个或多个ASIC、FPGA或CPU等器件的组合。相应的ASIC、FPGA、CPU等器件中包括系列可执行的指令，当这些指令被执行时会促使相应的ASIC、FPGA或CPU执行相应的功能，或者说执行相应的方法。相应的指令可以被存储于存储介质中或者固化在相应的ASIC或FPGA中。
具体的，相应的接收单元，可以是指与处理单元连接的具有接收信号流功能的接口，也可以指集成了PMA、PMD及接收器的功能模块，可选的，还可以包括FEC功能模块。相应的PMA、PMD及FEC功能可以集成于一个或多个ASIC、FPGA或CPU中。
下面将结合具体情形详细描述本发明具体实施例。
实施例一
下面将结合附图详细描述本发明实施例。
100GE以太网物理接口中划分了20个物理编码子层逻辑通道(PCS Lane)。每个逻辑通道周期性地每16384个64/66b码块的包含一个对齐标识(Alignment Marker:AM)，AM用于所有并行的物理编码子层逻辑通道的同步和对齐以便恢复出单一100GE数据流，因此其接口物理层具备典型的20行16384列的数据帧周期性结构。这种20行16384列的数据帧周期性结构，相当于划分了20个时隙。
40GE的情况类似，具有四个物理编码子层逻辑通道(PCS Lane)，其接口物理层具有4行16384列的典型数据帧周期性结构，等同于划分了4个时隙。
100GE多物理编码子层逻辑通道(PCS Lane)的20行16384列64/66b码块帧结构，40GE多物理编码子层逻辑通道(PCS Lane)的4行16384列64/66b码块帧结构，对每个通道的长度为16384的复用帧可进一步划分出若干复用子帧并定义开销，例如图10做如下定义，各个逻辑通道复用帧进一步将除去同步对齐码块(Alignment Marker:AM)以外的16383个块均分为3个复用子帧，每个子帧的第一个64/66b码块(包含8字节+2比特同步头共66比特)定义为子帧开销区域。其余为复用承载区域，包含5460个64/66b码块，每个64/66b码块或其对应的编码前的8个字符字节作为一个可分配的带宽颗粒。同样地，40GE物理层接口具备4个物理编码子层逻辑通道，每个通道的长度为16384的复用帧可以分化为3个复用子帧。
下面将详细描述在40GE以太网链路中混合复用CPRI-20的情形。
40GE、100GE接口上已进行比特复用时隙的划分，本发明中，将部分时隙上的带宽按需分配，用于复用CPRI接口数据，剩余带宽完全用于原有以太网统计复用分组数据的传输。
以太网分组业务中，数据分组统计复用链路资源，有效流量时高时低，系统设计和网络部署一般按照峰值需求设计。有效流量低的时候，链路上传输无效的空闲填充字节，造成了资源的浪费。例如某40GE只有60％的有效流量的时候，其40％的带宽实际上被闲置浪费了。本实施例描述一个固定速率(CBR)电路CPRIx20接口数据与上述只有60％有效流量的以太网分组数据共享复用一个40GE物理接口和链路的情形。
40GE物理接口和CPRIx20物理接口的标称时钟和接口信息速率以及其正负100ppm频偏情况下的极端速率如下表所示：
表2
Figure PCTCN2015091878-appb-000003
为了叙述方便，假设上述60％有效流量的40GE以太网物理接口 和固定速率电路CPRIx20接口都工作在标称时钟频率下，具备标称的接口信息速率。本实施例将这一路标称速率的固定速率(CBR)电路CPRIx20接口数据复用到标称速率的40GE物理接口的第一个物理编码子层逻辑通道(Lane 0)上。也即本发明从以太网接口链路带宽中划分出一部分(1/4＝25％)逻辑通道带宽资源以备按需要分配给其他技术体制的接口，实现接口和链路资源的共享复用。
按照64/66b块进行带宽资源分配。CPRI-20的帧同步头，原本为20个0x50字节，为配合使用64/66b编码，其适配子层使用帧结束字符/T/＝0xFD和帧开始字符/S/＝0xFB分别替换了其同步头20个0x50字节得第8第9个字节(#Z.0.7、#Z.0.8)，并在MII接口上以TXC＝1指示为控制字符，并让字符/S/出现64/66b编码块8字节颗粒的首字节。本实施例中为保证和64/66b的兼容，也要求字符/S/出现64/66b编码块8字节颗粒的首字节。
复用帧子帧标称帧频率为Fc＝(100*10^9)/64/20/16384*3＝28610.2294921875Frame/second；子帧带宽颗粒数为5460个(64/66b块)。对CPRIx20标称速率，每一个复用子帧平均需要分配(0.49152*10^9)/64*20/Fc＝5368.70912个带宽颗粒。则100000个子帧中，有70912个子帧分配的64/66b块带宽颗粒数为5369，有100000-70912＝29088个子帧分配的64/66b块带宽颗粒数为5368，就可以逼近实现平均分配的64/66b块带宽颗粒数为5368.70912的效果。为了尽量做到均匀，70912:29088＝2.437843784378438:1，大约间隔分配5369带宽颗粒的2到3个子帧之间间隔一个分配5368带宽颗粒一个子帧，以降低对缓存的需求。可以通过算法确定其间插和排布关系。如前50个子帧的每个子帧分配的带宽颗粒数量以及其间插和排布关系可用下面得方式确定：
表3
Figure PCTCN2015091878-appb-000004
具体排布序列为：【……5368,5369,5369,5368,5369,5369,5369,5368……】，如此排布可低对缓存的需求，理论上有效的数据缓存累积深度可以控制1以内。下面的算法二也可以得到同样的结果。
表4
Figure PCTCN2015091878-appb-000005
上面作为第一关键点，解决了子帧分配的带宽颗粒数量以及其排布序列。第二步就要解决子帧内带宽颗粒的分配和排布问题，确定各个颗粒是分配给CPRIx10接口电路业务还是仍保留给以太网统计复用分组业务。以便以太网统计复用分组业务能够使用剩余的全部链路带宽资源。
第二关键点，由于5369:(5460-5369)＝5369:91＝59:1，5460＝91*60， 5369＝91*59；也就是对于需要分配5369个带宽颗粒的子帧，每个子帧恰好等分为60颗粒的91等份，每60颗粒里面分配59个颗粒给CPRIx20，其余的1个颗粒仍保留给以太网统计复用分组业务。另5368:(5460-5368)＝5368:92＝58.3478:1，5460＝60*59+32*60，5368＝60*58+32*59；60:32＝15:8；也就是对于需要分配5368个带宽颗粒的子帧，可以将子帧分出59颗粒的60份，60颗粒的32份；每份都仍保留一个带宽颗粒给以太网统计复用分组业务，其余58或者59颗粒分配给CPRIx20。
子帧内的带宽颗粒的分配指派或者是归属的确定，可以又下面的方式确定。令子帧内的可分配64/66b颗粒数为：Pc_subframe，当前子帧需要分配给电路业务的64/66b颗粒数Cn_subframe；则子帧中标记为1～Pc_subframe的64/66b颗粒的分配排布可以如此确定：第j个颗粒如果使得mod(j*Cn_subframe,Pc_subframe)<Cn_subframe的关系成立，则为分配给TDM业务的带宽颗粒。否则保留给以太网统计复用分组业务。从而解决了两种业务的链路资源的共享复用问题。
表5
Figure PCTCN2015091878-appb-000006
本实施例中前述每子帧(5460颗粒)需要间隔地每帧分配5368或者5369个带宽颗粒。在接收端，接收机只需要提前获知Cn_subframe的数值，也可以通过同样的算法规则判定各个带宽颗粒的分配归属。特别地，在实际情况下，存在时钟的飘移和抖动，或者其他原因如调整了CPRIx20电路接口的速率降低为CPRIx10等变更，可能伴随有Cn_subframe的缓慢或者快速变化，因此，发端需要也仅仅需要实时地向收端传输子帧对应的Cn_subframe的数值。
100GE各个物理编码子层通道的所有的保留给以太网业务的带宽颗粒将统一用于以太网业务的复用。如图11所示，第一通道的第一子帧分配5368个颗粒，1个保留带宽颗粒间隔58或者59个分配 的带宽颗粒，第二子帧和第三子帧都分配5369个颗粒，1个保留带宽颗粒间隔59个分配的带宽颗粒。
第三关键点，还需要在物理链路的两端，为物理链路的发端向收端指示上述带宽颗粒的分配提供通信机制。实现每个子帧的带宽颗粒分配数值Cn_subframe由发送端到接收端的可靠传输。本发明改进的高速以太网物理接口的每个子帧的第一个64/66b码块为开销块。如图12所示，开销块可以作为特殊的数据块，同步头为两比特数据块同步头“0b01”，其8个字节部分用于每个子帧的Cn_subframe从链路的发端向收的传输。
如图12所示，每个子帧上包含5460个可分配带宽颗粒，需要一个13比特长度的Cn_subframe指示(2^12＝4096,2^13＝8192)，图中为block count的字段可用于承载该Cn_subframe指示，表6给出了Cn_subframe指示的具体含义。Cn_subframe有两层意义，一是指示出分配的带宽颗粒数量，二是隐式指示保留的带宽颗粒数量。Cn_subframe数值为零，标示当前子帧带宽颗粒完全保留。
表6
Figure PCTCN2015091878-appb-000007
在上述Cn_subframe数值绝对指示的同时，可进一步提供一种相对的指示，也即本帧的Cn_subframe数值相对上一帧的变化，编码如下表7所示。
表7
Figure PCTCN2015091878-appb-000008
相对变化的指示也可以用于印证和检验Cn_subframe是否得到可靠传输，起到校验作用。变化一般为+1或者-1。
如图13所示，可以为CPRI-20分配的业务标识ID为ID＝1，全局以太网统计复用分组业务的业务标识ID为ID＝0。发端的MII RS Master模块以及收端的MII RS Master模块均已据悉两个业务的类型和标识ID，以一张表格的形式或者其他形式存储备查。CPRI-20业务在分配出来的带宽颗粒上传输，称为前端业务，原有以太网统计复用分组业务在保留的带宽颗粒上传输，称为后端业务。表格标记了各个通道的前后端业务配置。收发端的MII RS Master模块根据表格控制数据的发送和接收。
如图14所示，发送侧，发端的MII RS Master模块根据表格内容和复用帧周期，在发送时钟<Tx Clk>的驱动下，生成控制指示信号信号<Tx En>、<Tx ID>。<Tx Clk>、<Tx En>、<Tx ID>一并用于控制和指导以太网适配子层(Ethernet RS,ID＝0)和CPRI适配子层(CPRI RS,ID＝1)的数据发送，以及物理编码子层对数据的编码扰码等处理。<Tx En>＝(0,0)、(0,1)、(0,2)、(0,3)分别指示当前时钟周期对应的带宽颗粒分别为通道0～n的同步对齐码块AM0～AMn、第一子帧开销OH0～OHn、第二子帧开销OH0～OHn、第三子帧开销OH0～OHn，此时<Tx ID>无指示意义，业务不能传输。本实施例40GE有四个通道(lane)，n＝4。<Tx En>＝(1,1)表示当前n个带宽颗粒属于第一子帧， <Tx En>＝(1,2)表示当前n个带宽颗粒属于第二子帧，<Tx En>＝(1,3)表示当前n个带宽颗粒属于第三子帧。器件各个通道(Lane)的带宽颗粒数据按Lane_0～Lane_n的先后顺序排列和传输。<Tx ID>指示当前数据块带宽颗粒的分配和保留归属，<Tx ID>的具体取值，由所在通道和所在子帧的Cn_subframe的确定，去该通道配置的前端业务ID或者后端业务，也即指示该时钟周期内带宽颗粒的归属。本实施例中，<Tx ID>＝0，表示为以太网的带宽颗粒，以太网适配子层(Ethernet RS,ID＝0)按指示发送数据，发送的数据如<Tx Data A>。<Tx ID>＝1，表示为以太网的带宽颗粒，CPRI适配子层(CPRI RS,ID＝1)按指示发送数据，发送的数据如<Tx Data B>。<Tx Data C>为数据<Tx Data A>和<Tx Data B>的时分复用合并。发端的MII RS Master模块填充的通道0～n的同步对齐码块AM0～AMn、第一子帧开销OH0～OHn、第二子帧开销OH0～OHn、第三子帧开销OH0～OHn数据块序列如<Tx Data D>，最后时分复用合并<Tx Data E>送物理层进行处理并上物理链路传输。En＝(1,3),1为指示数据；3为第三个子帧的意思。可选的，在一种实施方式中，请参考图14，En＝(0,0)，第一个0指示为非数据，第二个零第一子帧AM/OH，En＝(0,1),第一个0指示为非数据，1为第二子帧OH；En＝(0,2)，第一个0指示为非数据，2为第三子帧OH。
<Tx En>和通道0～n的同步对齐码块AM0～AMn的位置指示存在等同意义，可选地，<Tx Data D>、<Tx Data E>可以不包含有意义的AM0～AMn数据信息，如图15中<Tx Data D’>、<Tx Data E’>所示。PCS可以根据<Tx En>的指示，直接在<Tx En>＝(0,0)的位置上直接插入对应的AM0～AMn 64/66b编码块。
在<Tx En>的指示下，PCS的扰码处理进对AM0～AMn码块以外的码块进行扰码处理。
如图16所示，接收端物理层进行时钟和数据恢复后，得到<Rx Clk>和相应的解码前的数据序列，PCS一方面对未经扰码处理的通道0～n的同步对齐码块AM0～AMn进行识别、同步和对齐，至此AM0～AMn完成了使命，PCS可以输出<Rx En>序列。另一方面对数据序列进行解码和解扰码后恢复出<Rx Data A>数据序列。<Rx En> 和通道0～n的同步对齐码块AM0～AMn的位置指示存在等同意义，可选地，<Rx Data A>可以不包含有意义的AM0～AMn数据信息，如图17中的<Rx Data A’>。<Rx Clk>、<Rx En>、<Rx Data A>被送达收端的MII RS Master模块进行处理。收端的MII RS Master模块根据固定通道对齐码字的帧周期指示的<Rx En>显式指示，结合接收侧的物理编码子层逻辑通道和对应的前端业务ID和后端业务ID，由子帧开销OH0～OHn中的Cn_subframe确定各个时钟周期带宽颗粒的归属。<Rx Clk>、<Rx En>、<Rx ID>、<Rx Data B>被送达各个业务接口的适配子层，各适配子层在<Rx Clk>、<Rx En>、<Rx ID>的指示下接收和提取属于自己的数据。以太网适配子层(Ethernet RS,ID＝0)接收和提取<Rx En>＝(1,1)、(1,2)、(1,3)时，<Rx ID>＝0时的数据；CPRI适配子层(CPRI RS,ID＝1)接收和提取<Rx En>＝(1,1)、(1,2)、(1,3)时，<Rx ID>＝1时的数据。
另外，需要特别指出的是，接收机需要以比较快的方式获知Cn数值并确定其帧内带宽颗粒的分归属配排布。如果接收机无法在足够短的时间内完成计算确定每个带宽颗粒的归属，则建议开销块(OverHead)提前一帧发送。即当前子帧中的开销块对应指示下一子帧中的带宽颗粒分配，以此类推。使得接收机具有足够的时间进行反应，计算出子帧内的带宽颗粒的归属。
实施例二
下面将介绍在100GE以太网链路所开辟的比特复用时隙中混合承载CPRI-10的情形。
CPRI-20的帧同步头，原本为20个0x50字节，为配合使用64/66b编码，其适配子层使用帧结束字符/T/＝0xFD和帧开始字符/S/＝0xFB分别替换了其同步头20个0x50字节得第8第9个字节(#Z.0.7、#Z.0.8)，并在MII接口上以TXC＝1指示为控制字符，并让字符/S/出现64/66b编码块带宽可以的首字节。涉及的4/66b编码块的类型也为三种。
CPRI-10也可以采取与CPRI-20的帧同步头一样的处理方式，原 本为10个0x50字节，为了配合使用也8/10b编码，替换为0xBC、0x50/C5的第一、二字节仍保留为0x50字节，即使用T/S字符替换第8第9个字节(#Z.0.7、#Z.0.8)，即可以配合和使用以太网PCS进行64/66b编码，则涉及的编码块的类型也为三种，与CPRI-20一致。如果将CPRI-10与一个有效流量比较小的100GE以太网统计复用分组业务共享复用100GE物理接口和链路。本实施例将这一路标称速率的固定速率(CBR)电路CPRIx10接口数据复用到标称速率的100GE物理接口的第一个物理编码子层逻辑通道(Lane 0)上。
按照64/66b块进行带宽资源分配。复用帧子帧标称帧频率为Fc＝(100*10^9)/64/20/16384*3＝14305.11474609375Frame/second；子帧带宽颗粒数为5460个(64/66b块)。对CPRIx10标称速率，每一个复用子帧平均需要分配(0.49152*10^9)/64*10/Fc＝5368.70912个带宽颗粒。则100000个子帧中，有70912个子帧分配的64/66b块带宽颗粒数为5369，有100000-70912＝29088个子帧分配的64/66b块带宽颗粒数为5368，就可以逼近实现平均分配的64/66b块带宽颗粒数为5368.70912的效果。为了尽量做到均匀，70912:29088＝2.437843784378438:1，大约间隔分配5369带宽颗粒的2到3个子帧之间间隔一个分配5368带宽颗粒一个子帧，以降低对缓存的需求。具体实施方式与上述实施例一基本一致，请参见图10-图17，此处不再赘述。
此外，每个子帧中各个带宽颗粒的归属的确定，依赖于Cn_subframe，接收端也依赖Cn_subframe进行准确的数据解复用。因此Cn_subframe的可靠传输至关重要。因此对Cn_subframe、Cn_subframe Change的编码信息的传输，可以引入冗余和校验。有很多的不同方式可以引入冗余和校验，例如多次传输和增加CRC8、BIP8奇偶校验结果的传输等，图18给出了多次传输的实施图例。
实施例一的开销块中的保留字节，如图18所示，可以进一步使用。Cn_subframe、Cn_subframe Change的编码信息的传输三次以上，还可以对同一比特同时传输其二进制原值和二进制取反值(二进制1的取反为0,0的取反为1)，以保证Cn的可靠传输和对错误的可检测。 例如编码如下。
表8
Figure PCTCN2015091878-appb-000009
如图19所示，又或者引入多次传输加上行列组合偶校验，由于有行和列的监督校验，可以修正一个比特的错误，发现多个比特的错误，结合多次重复传输的Cn_subframe、Cn_subframe Change的编码信息，可以按照多数一致原则，保证Cn_subframe、Cn_subframe Change的可靠传输和接收。
补充一点，如果共享复用的物理层接口为使用8b/10b的编解码器，则可以保留CPRIx10的当前帧同步头字节定义。但需要重新设计共享复用帧的结构和开销信息特特别是Cn_subframe、Cn_subframe Change的编码信息的传输。
实施例三
下面将描述OTN数据如何利用本发明实施例提供的复用技术。
OTN OTU2/ODU2的接口的编码前信息速率比10GE以太网接口的编码前信息速率要高，也比40GE中的一个10G带宽的物理编码子层通道的编码前信息速率、100GE中的两个5G带宽的物理编码子层通道的总的编码前信息速率都要高。其结果是ODU2或OTU2无法复用到标称速率的40GE中的一个10G带宽的物理编码子层通道上，也无法重用标称速率的10GE物理接口进行传输，需要提速或者其他 处理。本实施例使用40GE中两个物理编码子层通道。
表9
Figure PCTCN2015091878-appb-000010
OTU2信号作为一个典型的TDM信号，本实施例描述将OTU2信号与统计复用分组以太网共享复用到一个40GE接口上。本实施例使用40GE中两个物理编码子层逻辑通道lane 1+lane 2。OTN OTU2作为该两个通道上的前端业务，分配的ID标示为ID＝2，统计复用以太网分组业务为所有通道上的后端背景业务ID＝0。收发端获得这样的配置信息或者通过协议协商确定业务ID配置表，如图20所示。
数值上看，平均每个子帧需要为OTU2信号分配5824或者5825个64/66b码块的带宽颗粒，已经超过了单通道每个子帧的可分配带宽颗粒的总数(5460)，需级联的两个40GE的物理编码子层通道(时隙)为其进行带宽颗粒的分配。
两个通道Lane00+Lane01的如何分配带宽颗粒任务，有不同的方式，例如下面的方式一和方式二，如表10所示。因为两个通道的前端业务配置ID都为2，Cn_subframe为两个通道的Cn数值的和。Cn_subframe＝Cn2+Cn1。
表10
Figure PCTCN2015091878-appb-000011
两种方式相当。以方式一为例，分布如图21所示，较方式二均匀。这里推荐方式一。第一通道Lane01全分配。第二通道Lane02适时增补相当一段单位时间内所需要一个带宽颗粒，364或者365个颗粒均匀分布在子帧内。
OTN具有定长帧结构，OTN帧本身具有6字节同步序列FAS＝<OA1,OA1,OA1,OA2,OA2,OA2>，其中OA1＝0xF6，OA2＝0x28，为固定比特图案。OTN据此结合物理层对FAS以外的数据进行扰码处理进行定帧。可选地，本实施例中可以保留OTU2帧的原始结构，将定帧的任务交由OTN RS进行处理；也可以由本发明的MII RS Master模块配合物理编码子层的64/66b编码功能进行OTU帧的定帧指示。如图22所标示，将OTU2帧的第一二字节。OA1,OA1,替换为物理编码子层的64/66b编码功能匹配的T、S字符，指示帧的开始和结束。
其另一区别在于发送和接收的数据序列伴随的字符属性指示信息TXC\RXC，前者均为0，OA1、OA2字节也作为数据字节以TXC\RXC＝0指示，与其他数据字节<D>一致。后者则将T、S字符字节作为控制字节以TXC\RXC＝1加以指示。如图23所示，前者如Tx Data C1所示，编码后的码块类型只有一种，后者如Tx Data C2所示，编码后的码块类型三种。
后者在实现上：发送方向OTN RS可简单地将OUT1的帧中FAS字段的第一二字节分别替换为/T/、/S/字符，然后通过8字节64比特TXD/RXD数据位宽和8比特TXC/RXC的MII接口，送往64/66b物理编码子层等物理层功能进行编码和传输；在接收方向上MII接收物理层解码输出的MII接口数据，恢复/T/、/S/字符为原始FAS的两个OA1字节，从而恢复OTU1帧。MII接口上送的数据遵从S字符出现在第一字节上TXD/RXD[0:7]的规则。前者对OTU1帧全部视为数据字节，则无此特殊要求。CPRI接口的情况也类似。
另外需要指出的是，OTN帧中所包含的FEC开销，在本实施例中的传输与否是可选的。因为FEC属于物理接口层的任务，实施例中下层的具有可选的FEC功能用于保证系统的传输误码性能。
值得说明的是，关于OTN数据流中添加/T/、/S/字符，并在以太 网MII接口传输的技术在中国专利201410805443.8已经有详细描述，该专利的全部内容被结合于本专利申请中。
实施例四
前端业务ID、后端背景业务ID的标记，为多个业务共享一个物理接口链路奠定了基础。
如图24所示，接口可以复用三个逻辑以太网统计复用分组业务和CBR CPRI业务、CBR OTN业务、统计复用Fibre Channel业务等。各个业务分配不同的业务ID，分配到不同的以太网物理编码子层逻辑通道作为前端业务或者后端背景业务。下图中以40GE物理层接口和链路为例子，划分了三个分组统计复用以太网逻辑子端口，标记为ID＝0、ID＝1、ID＝2；CBR电路CPRI-100业务的ID＝3，CBR电路OTU2业务的ID＝4，Fiber Channel FC(1G\2G\4G\8G)业务的ID＝5等。Fiber Channel FC本身也是一种基于分组的技术，但可以按照其物理接口速率，将其作为CBR电路来处理，也可以对其看做和以太网一样的分组统计复用业务来处理，具体取决于应用场景和实现对FC RS功能模块的要求。这里假设Fiber Channel为FC-1G\2G\4G\8G等不同速率等级的CBR业务先。也即这里的FC、CPRI、OTN业务都为CBR电路业务。
如图24所示，在一个40GE物理接口上，通道Lane 00的前端业务为CBR电路CPRI-10业务的ID＝3，后端背景业务为分组统计复用以太网逻辑子端口，业务ID＝0；两个业务大约都为5G带宽，CPRI的带宽占比略小，共享一个通道Lane 00。通道Lane 01+Lane 02的前端业务为CBR电路OTU2业务的ID＝4，后端背景业务为分组统计复用以太网逻辑子端口，业务ID＝1；两个业务大约都为10G带宽，OTU2的带宽占比略高，共享两个通道Lane 01+Lane 02。Fiber Channel FC(1G\2G\4G\8G)业务的ID＝5，作为前端业务和后端背景业务为分组统计复用以太网逻辑子端口，业务ID＝2一起共享通道Lane03的情况类似。甚至允许OTN、FC业务在不损失业务的前提下切换业务的速率等级，例如FC从2G切换为4G或其反过程。Cn_subframe 在逼近一个FC-2G的期望值的附近变化，切换为在逼近FC-4G的期望值附近变化。
实施例五
高速以太网接口速率越发展，接口的速率差异越大。例如目前常见的GE、10GE、40GE、100GE、400GE。接口速率差异最小9G，最大差异300G。对一些中间颗粒的带宽的分组统计复用以太网接口的需求，例如30G、80G等需求，难以满足。
如图25所示，本发明通过对高速接口划分物理编码子层逻辑通道，在通道或通道的组合上引入前端逻辑子端口和后端逻辑子端口，即可以由Cn_subframe实现通道或通道组带宽在两个逻辑子端口之间的无级分配。甚至于做到小数点后若干位基本的带宽分配或者带宽的百分比的分配。如100GE分为28.55GE、71.45GE等，或者80GE的89％、11％等。Cn_subframe结合分组统计复用以太网业务的特征，Cn_subframe可以与前述实施例一致，在一个逼近的期望值附近变化，并在开销中显式指示，显式指示有助于系统实现在系统的无损业务的带宽调整控制。
或者，Cn_subframe是一个固定值，由物理接口两端配置或者协商确定，可选地，Cn_subframe不需要在开销中传输。因此开销块可以不存在，开销块所在带宽颗粒可以作为可分配颗粒进行分配或者保留。也可按照子帧分配或保留保留带宽，也可以按照16384颗粒长度的整个复用帧分配或者保留带宽颗粒。无Cn_subframe传输指示，系统只能设置成静态配置。因此在进行带宽调整的时候，也即需要变化Cn_subframe的时候，收发端进行同步匹配的难度加大。
应该指出的是，无开销指示的情况下，不需要对现有以太网物理接口做规格变更，本发明可以此方式完美兼容当前40GE和100GE物理接口，具有现实的使用意义，应当特别重视。
实施例六
实施例中五已经提及，在开销中显式Cn_subframe、Cn_subframe  Change信息有利于系统实现在系统的无损业务的带宽调整。同样地，如果在开销中显式地传输当前子帧的业务ID配置信息，则有利于系统实现在系统的无损业务的业务配置调整。因为显式的指示，收发端完全基于子帧开销中的显式Cn_subframe、Cn_subframe Change信息、前端业务ID信息、后端业务ID信息进行数据的复用和解复用，保证了收发的匹配和同步。
如图27所示，在某些特殊情况下，所有用到的后端业务ID都默认为一个基本后端背景统计复用以太网业务的时候，例如保留ID＝0用来标记该业务，则后端业务ID信息不需要在开销中传输，只需要传输前端业务ID信息。
进一步地，如图28所示，如果前后端业务ID信息都不在开销中传输，链路的收发端进行共享复用的业务ID的协商就需要通过其他途径，例如控制平面协议或者管理平面协议来协商匹配可能存在的调整。或者管理平面固定静态配置，在业务开通期间不允许变更，否则将难以准确地进行解复用。
更进一步地，如果Cn_subframe、Cn_subframe Change都是固定不变的静态的数值，如实施例五中所描述，开销块不需要存在，每个复用帧16383个颗粒(每个子帧5461个颗粒)都可以进行分配和保留，则固定的Cn_subframe数值可以由协议在收发两端进行协商或者由管理平面进行静态配置。
实施例七
上述实施例中，CBR业务都按照标称速率来分析Cn_subframe的取值以及其序列变化。实际中，由于各种接口的时钟频率总与标称频率存在一定的差异，例如以太网、CPRI、Fibre Channel等接口都允许与标称频率有+/-100ppm的绝对频率差异，SDH、OTN都允许与标称频率有+/-20ppm绝对频率差异。所以在实际中，Cn_subframe要依赖CBR电路接口的具体真实速率来确定。统计复用以太网的子端口划分和灵活带宽配置，如实施例五中的按照百分比来划分子通道带宽，则无此类要求。本实施例给出一些切实可行的确定每子帧为CPRI、 OTN接口分配的带宽颗粒数的方法。
共享复用的以太网物理层接口的子帧可分配64/66b颗粒数：Pc.subframe，用于开销的64/66b颗粒数Po.subframe；子帧频率F.subfame；则通道的等效的64/66b编码线路带宽颗粒速率为
C.subframe＝(Pc.subframe+Po.subframe)*F.subfame。
速率不确定的电路业务的等效的64/66b编码线路带宽颗粒速率C.cbr。C.cbr<＝C.subframe的CBR业务，可以在既定的通道上作为前端业务。C.cbr与业务CDR恢复的时钟有对应关系。C.subframe与共享复用物理层接口的本地参考时钟有对应关系。CBR电路业务在恢复出来的时钟节拍下进入时钟隔离FIFO缓冲存储器，然后按照本地参考时钟按需取出并离开时钟隔离FIFO缓冲存储器。
两种方式，方式一：对比CBR业务的CDR恢复时钟计数和共享复用的物理接口发送参考时钟计数。
令系统本地参考时钟频率F.SystemClock＝(Pc.subframe+Po.subframe)*F.subfame*N/K＝C.subframe*N/K，该时钟用于一个计数深度为(Pc.subframe+Po.subframe)*N/K计数器的计数，每次计数满归零时可产生和输出一个频率为F.subfame的定时脉冲。
另外一个计数器，允许的计数深度也为(Pc.subframe+Po.subframe)*N/K，对与业务CDR恢复的时钟有对应关系时钟频率F.cbr＝C.cbr*N/K的脉冲进行计数，每当第一计数器计满归零的时候，读取第二计数器中的计数值，CounterValue*K/N取整作为Cn输出，同时第二计数器CounterValue减去Cn*N/K，为下一个Cn数值的输出做准备。从而为实际解决上述第一步提供了可行方法。保证Cn_subframe的数值与业务数据的真实速率匹配并能跟踪其变化。
N、K均为正整数，当N/K＝1时，计数器一个计数单位对应一个带宽颗粒；当N/K＝2时，计数器一个计数单位对应0.5个带宽颗粒；当N/K＝3时，计数器一个计数单位对应1/3个带宽；N/K＝2/3时，计数器一个计数单位对应2/3个带宽颗粒；当N/K＝4时，计数器一个计数单位对应0.25个带宽颗粒；以此类推。选择合适的N/K值，有利于系统的实现，避免计数器等电路工作在允许的一定的频率 范围内。
接收端可以由Cn_subframe和(Pc.subframe+Po.subframe)的关系，从收端的线路CDR时钟恢复出电路业务的时钟。
方式二：通过监测FIFO缓存的队列长度变化或者其FIFO缓存的写入地址变化，调整Cn_subframe跟踪其变化
方式一提到，数据是在其CDR恢复出来的时钟节拍下写入时钟隔离FIFO缓存的，通过监测数据队列写入地址与其变化、FIFO长度变化，和方式一一样，能够获得，C.cbr*N/K的信息，从而获得Cn_subframe，并让Cn_subframe跟随数据队列写入地址与其变化、FIFO长度变化而变化，保证Cn_subframe的数值与业务数据的真实速率匹配并能跟踪其变化。
方式二不但适用于CBR电路业务，也适用于VBR统计复用分组业务。
实施例八
在Cn_subframe以及其变化、前端后端业务ID配置都显式传输的时候，Cn_subframe、前端后端业务ID都可以实时按需变更。
在前后端业务均为统计复用分组业务的时候，各个业务的带宽不存在CBR电路业务类似的严格约束，可能采取Cn_subframe显式传输的，前端后端业务ID都隐式指示，不实时传输的的方式。这种情况下，可按下面方式增减通道。
既定的ID配置情况下，0<＝Cn_subframe<＝Pc.subframe的时候，前端业务和后端业务可以按需调整Cn_subframe，在前端业务和后端业务之间合理分配带宽。Cn_subframe＝0或者Cn_subframe＝Pc.subframe时候，可以调整和修改ID配置。
减少前端业务ID的通道数量配置
1、调整并确认某一通道的Cn_subframe＝0；按照规则显式传输Cn_subframe以及其变化。
2、删除该前端业务ID在该通道配置表的配置；并在两端达成协 商一致。
3、继续调整该前端业务ID所在通道的Cn_subframe到期望；按照规则显式传输Cn_subframe以及其变化。
增加前端业务ID的通道数量配置
1、调整并确认某一通道的Cn_subframe＝0。按照规则显式传输Cn_subframe以及其变化。
2、将前端业务ID配置增加该通道配置表的配置中；并在两端达成协商一致。
3、继续调整该前端业务ID所在通道的Cn_subframe到期望；按照规则显式传输Cn_subframe以及其变化。
减少前端业务ID的通道数量配置
1、调整并确认某一通道的Cn_subframe＝Pc.subframe。按照规则显式传输Cn_subframe以及其变化。
2、将后端业务ID配置从该通道的配置中删除；并在收发两端达成协商一致。
3、继续调整该前端业务ID所在通道的Cn_subframe到期望；按照规则显式传输Cn_subframe以及其变化。
增加后端业务ID的通道数量配置
1、调整并确认某一通道的Cn_subframe＝Pc.subframe；按照规则显式传输Cn_subframe及其变化。
2、将后端业务ID配置增加该通道配置表的配置中；并在两端达成协商一致。
3、继续调整该前端业务ID所在通道的Cn_subframe到期望；按照规则显式传输Cn_subframe以及其变化。
本领保护域普通技术人员可以理解：实现上述方法实施例的全部 或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领保护域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (24)

  1. 一种利用以太网信道传输业务信号的方法，其特征在于，所述以太网信道包括多个以太网物理编码子层PCS通道，每个以太网PCS通道通过长度固定的承载区来传输业务信号，所述方法包括：
    接收第一业务信号和第二业务信号；
    将所述第一业务信号和所述第二业务信号复用到以太网PCS通道的承载区中，其中，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载有所述第二业务信号；
    发送承载于所述以太网PCS通道的承载区中的所述第一业务信号和所述第二业务信号。
  2. 根据权利要求1所述方法，其特征在于：
    所述至少一个承载区中包括开销承载区和净荷承载区；
    所述开销承载区中承载有带宽指示信息，所述带宽指示信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽。
  3. 根据权利要求2所述方法，其特征在于：
    所述带宽指示信息为带宽颗粒数量信息，所述带宽颗粒数量信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽颗粒数量，其中，每个带宽颗粒的长度固定。
  4. 根据权利要求1至3任一所述方法，其特征在于：
    所述第一业务信号为以太网业务信号，或同步数字体系SDH业务信号，或光传送网络OTN业务信号，或通用公共无线电接口CPRI业务信号；
    所述第二业务信号为以太网业务信号。
  5. 根据权利要求1至4任意一项所述方法，其特征在于，所述接收第一业务信号和第二业务信号，包括：
    向所述第一业务信号的发送端和所述第二业务信号的发送端发送业务标识信号和时钟信号，接收所述第一业务信号的发送端发送的所述第一业务信号，以及所述第二业务信号的发送端发送的所述第二业务信号，其中，当所述业务标识信号为第一标识时，所述第一业务 信号的发送端发送所述第一业务信号，所述第二业务信号的发送端不发送业务信号，当所述业务标识信号为第二标识时，所述第二业务信号的发送端发送所述第二业务信号，所述第一业务信号的发送端不发送业务信号，所述第一标识与所述第一业务信号对应，所述第二标识与所述第二业务信号对应。
  6. 根据权利要求1至5任意一项所述方法，其特征在于，发送承载于所述以太网PCS通道的承载区中的所述第一业务信号和所述第二业务信号，包括，发送所述至少一个以太网PCS通道中的至少一个承载区，以及发送时钟信号和指示信号，所述指示信号用于指示与所述至少一个承载区对应的对齐标识AM的位置。
  7. 根据权利要求6所述方法，其特征在于：
    所述指示信号还用于指示所述至少一个承载区的开销承载区的位置，以及所述至少一个承载区的净荷承载区的位置。
  8. 一种利用以太网信道传输业务信号的方法，其特征在于，所述以太网信道包括多个以太网物理编码子层PCS通道，每个以太网PCS通道通过长度固定的承载区来传输业务信号，所述方法包括：
    接收通过所述以太网信道传输的业务信号，其中，所述业务信号包括第一业务信号和第二业务信号，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载有所述第二业务信号；
    分发所述第一业务信号和所述第二业务信号。
  9. 根据权利要求8所述方法，其特征在于：
    所述至少一个承载区中包括开销承载区和净荷承载区；
    所述开销承载区中承载有带宽指示信息，所述带宽指示信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽；
    所述分发所述第一业务信号和所述第二业务信号，包括，获取所述开销承载区中的带宽指示信息，根据所述带宽指示信息和本地存储的所述第一业务信号的标识和所述第二业务信号的标识生成业务标识信号，发送时钟信号、所述业务标识信号和所述至少一个承载区，所述业务标识信号用于指示所述第一业务信号和所述第二业务信号 在所述净荷承载区中所占用的位置。
  10. 根据权利要求9所述方法，其特征在于：
    所述带宽指示信息为带宽颗粒数量信息，所述带宽颗粒数量信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽颗粒数量，其中，每个带宽颗粒的长度固定。
  11. 根据权利要求8至10任一所述方法，其特征在于：
    所述第一业务信号为以太网业务信号，或同步数字体系SDH业务信号，或光传送网络OTN业务信号，或通用公共无线电接口CPRI业务信号；
    所述第二业务信号为以太网业务信号。
  12. 根据权利要求9至11任意一项所述方法，其特征在于，所述方法还包括：
    接收时钟信号以及指示信号，所述指示信号用于指示开销承载区的位置。
  13. 一种通信设备，其特征在于，所述通信设备包括：
    处理单元，用于接收第一业务信号和第二业务信号，将所述第一业务信号和所述第二业务信号复用到以太网PCS通道的承载区中，其中，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载有所述第二业务信号；
    发送单元，用于发送承载于所述以太网PCS通道的承载区中的所述第一业务信号和所述第二业务信号。
  14. 根据权利要求13所述通信设备，其特征在于：
    所述至少一个承载区中包括开销承载区和净荷承载区；
    所述开销承载区中承载有带宽指示信息，所述带宽指示信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽。
  15. 根据权利要求14所述通信设备，其特征在于，所述带宽指示信息为带宽颗粒数量信息，所述带宽颗粒数量信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽颗粒数量，其中，每个带宽颗粒的长度固定。
  16. 根据权利要求13至15任一所述通信设备，其特征在于：
    所述第一业务信号为以太网业务信号，或同步数字体系SDH业务信号，或光传送网络OTN业务信号，或通用公共无线电接口CPRI业务信号；
    所述第二业务信号为以太网业务信号。
  17. 根据权利要求13至16任一所述通信设备，其特征在于，所述接收第一业务信号和第二业务信号，包括：
    向所述第一业务信号的发送端和所述第二业务信号的发送端发送业务标识信号和时钟信号，接收所述第一业务信号的发送端发送的所述第一业务信号，以及所述第二业务信号的发送端发送的所述第二业务信号，其中，当所述业务标识信号第一标识时，所述第一业务信号的发送端发送所述第一业务信号，所述第二业务信号的发送端不发送业务信号，当所述业务标识信号第二标识时，所述第二业务信号的发送端发送所述第二业务信号，所述第一业务信号的发送端不发送业务信号，所述第一标识与所述第一业务信号对应，所述第二标识与所述第二业务信号对应。
  18. 根据权利要求13至17任意一项所述通信设备，其特征在于，发送承载于所述以太网PCS通道的承载区中的所述第一业务信号和所述第二业务信号，包括，发送所述至少一个以太网PCS通道中的至少一个承载区，以及发送时钟信号和指示信号，所述指示信号用于指示与所述至少一个承载区对应的对齐标识AM的位置。
  19. 根据权利要求18所述通信设备，其特征在于：
    所述指示信号还用于指示所述至少一个承载区的开销承载区的位置，以及所述至少一个承载区的净荷承载区的位置。
  20. 一种通信设备，其特征在于，所述通信设备包括：
    接收单元，用于接收通过所述以太网信道传输的业务信号，其中，所述业务信号包括第一业务信号和第二业务信号，所述以太网信道中的至少一个以太网PCS通道中的至少一个承载区的一部分承载有所述第一业务信号，所述至少一个承载区的另一部分承载有所述第二业务信号；
    处理单元，用于分发所述第一业务信号和所述第二业务信号。
  21. 根据权利要求20所述通信设备，其特征在于：
    所述至少一个承载区中包括开销承载区和净荷承载区；
    所述开销承载区中承载有带宽指示信息，所述带宽指示信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽；
    所述分发所述第一业务信号和所述第二业务信号，包括，获取所述开销承载区中的带宽指示信息，根据所述带宽指示信息和本地存储的所述第一业务信号的标识和所述第二业务信号的标识生成业务标识信号，发送时钟信号、所述业务标识信号和所述至少一个承载区，所述业务标识信号用于指示所述第一业务信号和所述第二业务信号在所述净荷承载区中所占用的位置。
  22. 根据权利要求21所述通信设备，其特征在于：
    所述带宽指示信息为带宽颗粒数量信息，所述带宽颗粒数量信息用于指示所述第一业务信号所占用的所述净荷承载区中的带宽颗粒数量，其中，每个带宽颗粒的长度固定。
  23. 根据权利要求20至22任一所述通信设备，其特征在于：
    所述第一业务信号为以太网业务信号，或同步数字体系SDH业务信号，或光传送网络OTN业务信号，或通用公共无线电接口CPRI业务信号；
    所述第二业务信号为以太网业务信号。
  24. 根据权利要求21至23任一所述通信设备，其特征在于：
    所述接收单元，还用于接收时钟信号以及指示信号；
    所述处理单元，还用于根据所述指示信号确定开销承载区的位置。
PCT/CN2015/091878 2015-01-22 2015-10-13 一种利用以太网信道传输业务信号的方法及通信设备 WO2016115927A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP15878596.4A EP3242430B1 (en) 2015-01-22 2015-10-13 Service signal transmission method and communication device using ethernet channel
EP19189528.3A EP3627736B1 (en) 2015-01-22 2015-10-13 Method for transmitting service signal by using ethernet channel and communications device
ES15878596T ES2760514T3 (es) 2015-01-22 2015-10-13 Método de transmisión de señal de servicio y un dispositivo de comunicaciones que utiliza un canal de Ethernet
US15/656,479 US10476791B2 (en) 2015-01-22 2017-07-21 Method for transmitting service signal by using ethernet channel and communications device
US16/669,148 US11165698B2 (en) 2015-01-22 2019-10-30 Method for transmitting service signal by using ethernet channel and communications device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510031514.8A CN105871502B (zh) 2015-01-22 2015-01-22 一种利用以太网信道传输业务信号的方法及通信设备
CN201510031514.8 2015-01-22

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/656,479 Continuation US10476791B2 (en) 2015-01-22 2017-07-21 Method for transmitting service signal by using ethernet channel and communications device

Publications (1)

Publication Number Publication Date
WO2016115927A1 true WO2016115927A1 (zh) 2016-07-28

Family

ID=56416390

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/091878 WO2016115927A1 (zh) 2015-01-22 2015-10-13 一种利用以太网信道传输业务信号的方法及通信设备

Country Status (5)

Country Link
US (2) US10476791B2 (zh)
EP (2) EP3242430B1 (zh)
CN (2) CN105871502B (zh)
ES (1) ES2760514T3 (zh)
WO (1) WO2016115927A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108347317A (zh) * 2017-01-22 2018-07-31 华为技术有限公司 一种业务的传输方法、网络设备及网络系统
KR20200035142A (ko) * 2017-08-11 2020-04-01 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 주파수를 투명하게 전송하기 위한 방법 및 디바이스

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106788855B (zh) * 2015-11-23 2018-12-07 华为技术有限公司 一种灵活以太网业务的光传送网承载方法及装置
CN107786320B (zh) * 2016-08-25 2021-06-22 华为技术有限公司 一种发送和接收业务的方法、装置和网络系统
CN108243128B (zh) * 2016-12-27 2020-10-23 华为技术有限公司 一种传输无线接口前传信号的方法、网络设备和系统
US11032103B2 (en) 2017-03-08 2021-06-08 Credo Technology Group Limited Ethernet link extension method and device
CN108631908B (zh) * 2017-03-21 2022-03-01 中兴通讯股份有限公司 使用FlexE承载信号帧的方法、FlexE信号帧还原的方法及装置
US10212260B2 (en) * 2017-07-19 2019-02-19 Credo Technology Group Limited SerDes architecture with a hidden backchannel protocol
CN109379207A (zh) 2017-08-08 2019-02-22 华为技术有限公司 一种业务复用方法、业务解复用方法以及相关设备
CN109600188B (zh) * 2017-09-30 2020-04-28 华为技术有限公司 数据传输方法、传输设备和传输系统
CN109802742B (zh) * 2017-11-16 2020-05-19 华为技术有限公司 一种传输数据的方法、设备及系统
US10951508B2 (en) * 2018-01-09 2021-03-16 Ciena Corporation End-to-end data path integrity validation at layer 2
CN111937329B (zh) * 2018-03-31 2021-12-31 华为技术有限公司 传输数据的方法和转发设备
CN110460405B (zh) 2018-05-07 2021-04-09 华为技术有限公司 业务信号传输方法及装置
CN110830152B (zh) 2018-08-07 2021-04-09 华为技术有限公司 接收码块流的方法、发送码块流的方法和通信装置
CN110932923B (zh) * 2018-09-20 2022-04-01 中国移动通信有限公司研究院 计算带宽利用率的方法及设备
CN111356037B (zh) 2018-12-21 2021-08-20 深圳市海思半导体有限公司 光传送网线路带宽切换方法及装置
US11228991B2 (en) 2019-02-01 2022-01-18 Cisco Technology, Inc. Link auto-negotiation between a radio equipment controller (REC) and radio equipment (RE) in an ethernet-based fronthaul network
CN112019312B (zh) * 2019-05-31 2023-06-16 中兴通讯股份有限公司 一种服务处理方法及装置和车联网设备
CN117692099A (zh) * 2019-06-04 2024-03-12 华为技术有限公司 一种以太网数据传输的方法和通信设备
CN112398756B (zh) * 2019-08-13 2024-05-17 华为技术有限公司 用于传输业务数据的方法和装置
US10863386B1 (en) * 2019-09-17 2020-12-08 Cisco Technology, Inc. State machine handling at a proxy node in an ethernet-based fronthaul network
US11637713B1 (en) * 2020-02-14 2023-04-25 Marvell Asia Pte, Ltd. Energy-efficient Ethernet transceiver that adjusts based on environmental conditions
JP2023523982A (ja) * 2020-04-27 2023-06-08 華為技術有限公司 サービス処理方法および装置およびデバイス
US11349704B2 (en) 2020-06-17 2022-05-31 Credo Technology Group Limited Physical layer interface with redundant data paths
US11646959B2 (en) 2020-07-20 2023-05-09 Credo Technology Group Limited Active ethernet cable with broadcasting and multiplexing for data path redundancy
CN114095435A (zh) * 2020-07-31 2022-02-25 华为技术有限公司 比特块的发送方法及装置
WO2022056884A1 (zh) * 2020-09-18 2022-03-24 华为技术有限公司 一种线路编码方法及装置
US11356302B1 (en) 2020-11-30 2022-06-07 Credo Technology Group Limited Equalizer training during link speed negotiation
CN112866362B (zh) * 2021-01-06 2023-04-28 北京腾红电子科技有限公司 物理连接装置
CN115037287B (zh) 2021-03-05 2023-07-28 默升科技集团有限公司 扩频时钟转换器
US11424968B1 (en) 2021-06-10 2022-08-23 Credo Technology Group Limited Retimer training during link speed negotiation and link training
WO2023141777A1 (zh) * 2022-01-25 2023-08-03 华为技术有限公司 通信方法及网络设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8411703B1 (en) * 2009-07-30 2013-04-02 Xilinx, Inc. Method and apparatus for a reduced lane-lane skew, low-latency transmission system
CN103502985A (zh) * 2013-04-12 2014-01-08 华为技术有限公司 一种数据处理的方法、装置及系统
CN103875205A (zh) * 2013-09-13 2014-06-18 华为技术有限公司 传输数据的方法和装置
US20150071311A1 (en) * 2013-09-09 2015-03-12 Applied Micro Circuits Corporation Reformating a plurality of signals to generate a combined signal comprising a higher data rate than a data rate associated with the plurality of signals

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1691666B (zh) * 2004-04-21 2010-04-14 华为技术有限公司 多协议通用线路传输方法及其装置
CN100442761C (zh) * 2005-03-09 2008-12-10 华为技术有限公司 波分复用网络中以太业务信号的传送方法和处理装置
JP2007074256A (ja) * 2005-09-06 2007-03-22 Of Networks:Kk 複数ｌｌｉｄ処理装置
US7676733B2 (en) * 2006-01-04 2010-03-09 Intel Corporation Techniques to perform forward error correction for an electrical backplane
CN101227450B (zh) 2007-01-16 2013-04-24 华为技术有限公司 一种开销信息的传输方法、系统及设备
CN101267386B (zh) * 2007-03-15 2011-12-07 华为技术有限公司 传输多路独立以太网数据的方法、装置和系统
CN101615967B (zh) 2008-06-26 2011-04-20 华为技术有限公司 一种业务数据的发送、接收方法、装置和系统
CN101729940B (zh) * 2008-10-22 2013-06-05 华为技术有限公司 向多路通信通道发送数据的方法及接收数据的方法
CN101841749B (zh) * 2009-03-18 2013-10-02 华为技术有限公司 数据传输方法、通信装置及通信系统
KR20120017286A (ko) * 2010-08-18 2012-02-28 한국전자통신연구원 얼라인먼트 장치 및 방법
KR101717296B1 (ko) * 2010-12-15 2017-03-16 한국전자통신연구원 선택적 레인 운용을 위한 이더넷 장치 및 방법
US8934783B2 (en) * 2011-02-17 2015-01-13 International Business Machines Corporation Adaptor system for an ethernet network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8411703B1 (en) * 2009-07-30 2013-04-02 Xilinx, Inc. Method and apparatus for a reduced lane-lane skew, low-latency transmission system
CN103502985A (zh) * 2013-04-12 2014-01-08 华为技术有限公司 一种数据处理的方法、装置及系统
US20150071311A1 (en) * 2013-09-09 2015-03-12 Applied Micro Circuits Corporation Reformating a plurality of signals to generate a combined signal comprising a higher data rate than a data rate associated with the plurality of signals
CN103875205A (zh) * 2013-09-13 2014-06-18 华为技术有限公司 传输数据的方法和装置

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108347317A (zh) * 2017-01-22 2018-07-31 华为技术有限公司 一种业务的传输方法、网络设备及网络系统
CN108347317B (zh) * 2017-01-22 2020-11-10 华为技术有限公司 一种业务的传输方法、网络设备及网络系统
US11223438B2 (en) 2017-01-22 2022-01-11 Huawei Technologies Co., Ltd. Service transmission method, network device, and network system
KR20200035142A (ko) * 2017-08-11 2020-04-01 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 주파수를 투명하게 전송하기 위한 방법 및 디바이스
EP3664390A4 (en) * 2017-08-11 2020-07-29 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR THE TRANSITION OF SERVICE FREQUENCY
KR102383297B1 (ko) * 2017-08-11 2022-04-08 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 주파수를 투명하게 전송하기 위한 방법 및 디바이스
US11412074B2 (en) 2017-08-11 2022-08-09 Huawei Technologies Co., Ltd. Method and device for transparently transmitting service frequency

Also Published As

Publication number Publication date
US10476791B2 (en) 2019-11-12
CN105871502B (zh) 2020-01-03
EP3242430B1 (en) 2019-09-25
US11165698B2 (en) 2021-11-02
EP3627736B1 (en) 2022-04-13
EP3627736A1 (en) 2020-03-25
US20170324657A1 (en) 2017-11-09
EP3242430A1 (en) 2017-11-08
EP3242430A4 (en) 2018-01-24
US20200076731A1 (en) 2020-03-05
ES2760514T3 (es) 2020-05-14
CN111147185A (zh) 2020-05-12
CN105871502A (zh) 2016-08-17

Similar Documents

Publication Publication Date Title
WO2016115927A1 (zh) 一种利用以太网信道传输业务信号的方法及通信设备
EP3089423B1 (en) Ethernet signal transmission method, scheduling method and device and system thereof
US10623327B2 (en) Data transmission method, transmitter, and receiver
CN107566075B (zh) 一种发送和接收业务的方法、装置和网络系统
WO2019062227A1 (zh) 数据传输方法、传输设备和传输系统
CN107786320B (zh) 一种发送和接收业务的方法、装置和网络系统
WO2008110119A1 (en) A method for transporting multiple channels ethernet data, the device and the system thereof
WO2016101682A1 (zh) 一种处理信号的方法及通信设备
CN113330696B (zh) Cpri数据块传输方法和设备
WO2022183875A1 (zh) 确定传输时隙的方法和相关装置
WO2019100982A1 (zh) 数据传输方法和设备
CN116264587A (zh) 一种数据传输的方法以及相关装置
WO2024032269A1 (zh) 通信方法、相关装置及计算机可读存储介质
CN115065439B (zh) 一种spn网络恒定比特率业务传送方法和设备

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: 15878596

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015878596

Country of ref document: EP