WO2019029419A1 - 透传业务频率的方法和设备 - Google Patents

透传业务频率的方法和设备 Download PDF

Info

Publication number
WO2019029419A1
WO2019029419A1 PCT/CN2018/098143 CN2018098143W WO2019029419A1 WO 2019029419 A1 WO2019029419 A1 WO 2019029419A1 CN 2018098143 W CN2018098143 W CN 2018098143W WO 2019029419 A1 WO2019029419 A1 WO 2019029419A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
statistical duration
code block
frequency information
information
Prior art date
Application number
PCT/CN2018/098143
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 JP2020529796A priority Critical patent/JP7019938B2/ja
Priority to KR1020207007041A priority patent/KR102383297B1/ko
Priority to EP18843757.8A priority patent/EP3664390A4/en
Publication of WO2019029419A1 publication Critical patent/WO2019029419A1/zh
Priority to US16/786,507 priority patent/US11412074B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H04L7/02—Speed or phase control by the received code signals, the signals containing no special synchronisation information
    • H04L7/027—Speed or phase control by the received code signals, the signals containing no special synchronisation information extracting the synchronising or clock signal from the received signal spectrum, e.g. by using a resonant or bandpass circuit
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00—Encapsulation of packets

Definitions

  • the present application relates to the field of transport networks and, more particularly, to a method and apparatus for transparently transmitting traffic frequencies.
  • FlexE Flexible Ethernet
  • CPRI Common Public Radio Interface
  • SDH Synchronous Digital Hierarchy
  • CBR Constant Bit Rate
  • the present application provides a method and device for transparently transmitting a service frequency, which can support multiple service data with service frequency transparent transmission requirements and simultaneously access the link of the FlexE without changing the existing Flexe standard.
  • the first aspect provides a method for transparently transmitting a service frequency, where the first device determines the first service frequency information Xn, where the first service frequency information Xn is used to indicate that the first device is within the first statistical duration.
  • the number of n-bit first service data sent, the first statistical duration is based on a transmission frequency of the first device, where n is a positive integer; the first device uses the first service frequency information Xn Encapsulating into the first S/T bit code block, inserting the first S/T bit code block into the data stream of the first service data, and transmitting the same to the second device, where S and T are positive Integer.
  • the first aspect of the method for transparently transmitting service frequencies can support multiple service data with service frequency transparent transmission requirements to simultaneously access the links of the FlexE without changing the existing Flexe standard.
  • each service that has a service frequency transparent transmission requirement inserts a padding block into the data stream of the service for rate matching.
  • the first method inserts the first service frequency information into the data stream of the first service data.
  • Medium, the reasonable allocation to the bandwidth of the service does not affect other services.
  • n-bit first service data is the unit used when counting the first service data.
  • the first statistical duration may be determined based on the rate of the first traffic data. If the rate of the first service data is lower than a certain threshold, a longer first statistical duration may be determined, for example, the first statistic is longer than the length of one basic frame or one multiframe; if the rate of the first service data is higher than a certain A threshold may determine a shorter first statistical duration, for example, the first statistical duration is shorter than the length of one basic frame or one multiframe.
  • the S/T bit code block may be a 64/66B code block or an 8/10B code block or the like.
  • the first S/T bit code block is an S/T bit code block identified by an O code.
  • the code block encapsulating the first service frequency information Xn is marked with a special identifier, so that the lower-level device can identify and parse the S/T bit code block.
  • O code refers to O code, and its type field may be 0x4B.
  • O code of the FlexE overhead block 1 defined by the OIF FlexE Implementation Agreement (IA) 1.0 is 0x5.
  • the first S/T bit code block is further encapsulated with first statistical duration information, where the first statistical duration information is used to indicate the first statistical duration .
  • the first statistical duration is a first target number of sending clock cycles, and the first statistical duration information includes the first target number.
  • the statistical duration is decoupled from the basic frame and the multiframe period, and the optimal statistical duration can be selected according to the rate of the service, so that the statistical service frequency information is more accurate.
  • the method further includes: determining, by the first device, the first statistical duration according to a rate of the first service data; the first device determining the first service
  • the frequency information Xn includes: the first device statistics the number of n bits of the first service data sent within the first statistical duration.
  • the first device functions as an access node.
  • the method further includes: receiving, by the first device, a data flow of the first service data sent by a third device, and a data flow from the first service data Decoding the first service frequency information Yn in the second S/T bit code block; the first device determining the first service frequency information Xn, the first device according to the first service frequency information Yn, Calculating the number of n bits of the first service data sent within the first statistical duration to obtain the first service frequency information Xn.
  • the first device serves as an intermediate node, so that the implementation manner can support the multi-hop cascading networking mode.
  • the second S/T bit code block is further encapsulated with first statistical duration information, where the first statistical duration information is used to indicate the first statistical duration .
  • the method further includes: the first device determining the second service frequency information Wm, where the second service frequency information Wm is used to indicate that the first device is in the first The number of m-bit second service data sent in the second statistical duration, the second statistical duration is based on the transmission frequency of the first device, where m is a positive integer; the first device will be the second The service frequency information Wm is encapsulated into a third S/T bit code block, and the third S/T bit code block is inserted into the data stream of the second service data and sent to the second device.
  • the method of the implementation manner can support multiple service data with service frequency transparent transmission requirements and access the device at the same time.
  • the first service frequency information Xn A ⁇ F client /F FlexE , where A is a frequency coefficient, and F client is a service frequency of the first service data, F FlexE is the transmission frequency of the first device.
  • the second aspect provides a method for transparently transmitting a service frequency, where the fourth device receives a data flow of the first service data sent by the fifth device, where the data flow of the first service data includes the first S/T a bit code block, the first S/T bit code block includes a first service frequency information Zn, and the first service frequency information Zn is used to indicate that the fifth device sends the first statistical duration.
  • a quantity of the first service data, the first statistical duration is based on a transmission frequency of the fifth device, where n, S, and T are positive integers; and the fourth device is configured according to the first service frequency information Zn, recovering a clock corresponding to the first service data.
  • the method for transparently transmitting the service frequency can support multiple service data having the service frequency transparent transmission requirement and simultaneously access the link of the FlexE without changing the existing Flexe standard.
  • each service that has a service frequency transparent transmission requirement inserts a padding block into the data stream of the service for rate matching.
  • the first service frequency information is inserted into the data of the first service data. In the flow, the bandwidth allocated to the service is reasonably utilized without affecting other services.
  • the first S/T bit code block is an S/T bit code block identified by an O code.
  • the first S/T bit code block is further encapsulated with first statistical duration information, where the first statistical duration information is used to indicate the first statistical duration Recovering the clock corresponding to the first service data according to the first service frequency information Zn, the fourth device: the fourth device according to the first service frequency information Zn and the first statistical duration And recovering a clock corresponding to the first service data.
  • the first statistical duration is a first target number of sending clock cycles
  • the first statistical duration information includes the first target number
  • the method further includes: receiving, by the fourth device, a data stream of the second service data that is sent by the fifth device, where the data stream of the second service data includes a second S/T bit code block, the second S/T bit code block includes a second service frequency information Vm, and the second service frequency information Vm is used to indicate that the fifth device is in a second statistical period
  • the number of n-bit second service data transmitted, the second statistical duration is based on the transmission frequency of the fifth device, where m is a positive integer; the fourth device is based on the second service frequency information Vm, recovering a clock corresponding to the second service data.
  • the first service frequency information Zn A ⁇ F client /F FlexE , where A is a frequency coefficient, and F client is a service frequency of the first service data, F FlexE is the transmission frequency of the fifth device.
  • the third aspect provides a device for transparently transmitting a service frequency, where the device is a first device, and is used to perform the method in any one of the foregoing first aspect or the first aspect.
  • the device that transparently transmits the service frequency may include a unit for performing the method in the first aspect or any of the possible implementation manners of the first aspect.
  • the fourth aspect provides a device for transparently transmitting a service frequency, where the device is a fourth device, and is used to perform the method in any of the foregoing second aspect or the second aspect.
  • the device for transmitting the service frequency may include a unit for performing the method in any of the possible implementations of the second aspect or the second aspect.
  • the fifth aspect provides a device for transparently transmitting a service frequency, where the device that transmits the service frequency is a first device, and the device that transparently transmits the service frequency includes a processor, a memory, and a network interface, where the memory is used to store an instruction,
  • the processor and network interface are for executing instructions stored by the memory, and execution of instructions stored in the memory causes the processor and network interface to perform any of the first aspect or any possible implementation of the first aspect The method in the way.
  • the sixth aspect provides a device for transparently transmitting a service frequency, where the device for transmitting a service frequency is a fourth device, where the device for transparently transmitting a service frequency includes a processor, a memory, and a network interface, where the memory is used to store an instruction,
  • the processor and network interface are for executing instructions stored by the memory, and execution of instructions stored in the memory causes the processor and network interface to perform any of the possible implementations of the second aspect or the second aspect The method in the way.
  • a seventh aspect provides a computer storage medium having stored thereon instructions that, when executed on a computer, cause the computer to perform the method of any of the possible implementations of the first aspect or the first aspect .
  • An eighth aspect provides a computer storage medium having stored thereon instructions that, when executed on a computer, cause the computer to perform the method of any one of the possible implementations of the second aspect or the second aspect .
  • a ninth aspect provides a computer program product comprising instructions, when the computer runs the finger of the computer program product, the computer performs the method of any of the first aspect or the first aspect of the first aspect .
  • a tenth aspect provides a computer program product comprising instructions, when the computer runs the finger of the computer program product, the computer performs the method of any one of the possible implementations of the second aspect or the second aspect .
  • FIG. 1 is a schematic diagram of a FlexE architecture of an embodiment of the present application.
  • FIG. 2 is a schematic diagram of code blocks on a PHY link in accordance with an embodiment of the present application.
  • FIG. 3 is a schematic diagram of overhead code blocks in a FlexE basic frame according to an embodiment of the present application.
  • Figure 4 is a schematic diagram of the loss of the service clock during the transmission of the service data in the FlexE.
  • Figure 5 is a schematic diagram of circuitry for mapping traffic data in an OTN.
  • FIG. 6 is a schematic diagram of circuitry for demapping traffic data in an OTN.
  • Figure 7 is a schematic diagram of a synchronous Ethernet technology in FlexE.
  • Figure 8 is a schematic diagram of transparent transmission of service frequencies using synchronous Ethernet technology in FlexE.
  • FIG. 9 is a schematic structural diagram of a system for transparently transmitting service frequencies according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a system for transparently transmitting a service frequency according to another embodiment of the present application.
  • 11 is a schematic diagram of a method for an access node to perform a transparent transmission service frequency according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a method for an intermediate node to perform a transparent transmission service frequency according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a method for an outbound node to perform a transparent transmission service frequency according to an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of an apparatus for transparently transmitting a service frequency according to an embodiment of the present application.
  • FIG. 15 is a schematic block diagram of an apparatus for transparently transmitting a service frequency according to another embodiment of the present application.
  • FIG. 16 is a schematic block diagram of an apparatus for transparently transmitting a service frequency according to another embodiment of the present application.
  • FIG. 17 is a schematic block diagram of an apparatus for transparently transmitting a service frequency according to another embodiment of the present application.
  • link in the embodiment of the present application may be simply referred to as a “link”, and the link in the FlexE may also be referred to as a “physical layer (PHY) link”.
  • PHY physical layer
  • Ethernet The 802.3 protocol-based Ethernet defined by the Institute of Electrical and Electronics Engineers (IEEE) has been widely used and developed in the past quite a while.
  • IEEE Institute of Electrical and Electronics Engineers
  • An Ethernet port usually appears as a logical concept for data, called a logical port or simply a port.
  • An Ethernet physical interface appears as a concept on a hardware, called a physical interface or simply an interface.
  • an Ethernet port is tagged with a Media Access Control (MAC) address.
  • the rate of the traditional Ethernet port is determined based on the rate of the Ethernet physical interface. In general, the maximum bandwidth of an Ethernet port corresponds to the bandwidth of an Ethernet physical interface.
  • the Ethernet interface rate has been increased by 10 times, and has evolved from 10 Mbps to 100 Mbps, 1000 Mbps (1 Gbps), 10 Gbps, 40 Gbps, 100 Gbps, and 400 Gbps.
  • the bandwidth growth required by mainstream applications does not exhibit a 10-fold growth characteristic.
  • the bandwidth required for mainstream applications includes 50 Gbps, 75 Gbps, and 200 Gbps. If 50Gbps is transmitted with 100GE, there will be waste of resources.
  • 200Gbps there is currently no corresponding Ethernet standard particle that can be carried, and so on. Therefore, the industry hopes to provide support for Ethernet ports (virtual connections) with bandwidths of 50 Gbps, 60 Gbps, 75 Gbps, 200 Gbps, and 150 Gbps.
  • Ethernet ports can use one or several Ethernet physical interfaces together. For example, two 40GE ports and two 10GE ports use one 100G physical interface together. For example, Ethernet. Ports can be flexibly adjusted as demand changes, such as from 200Gbps to 330Gbps, or 50Gbps to 20Gbps to increase Ethernet port efficiency or extend their lifecycle. For fixed-rate physical links, they can be bundled in cascade to support stacking of logical port rates (for example, bundling two 100GE physical interface stacks to support 200GE logical ports).
  • the bandwidth resources obtained by the flexible stacking of the physical interfaces can be pooled, and the bandwidth is allocated to a specific Ethernet logical port according to the granularity (for example, 5G is a granularity), and several Ethernet virtual connection pairs are cascaded. Efficient sharing of physical link groups.
  • FlexE specifically builds several Ethernet PHY links into a flexible Ethernet group (FlexE Group) and provides a common mechanism to support different Ethernet MAC rates to support binding for Ethernet services. , sub-rate, channelization and other functions.
  • the MAC rate provided by FlexE can be greater than the rate of a single PHY link (by binding) or less than the rate of a single PHY link (through sub-rate and channelization).
  • the 200G Ethernet service (MAC code stream) can be transmitted by using two existing 100GE Physical Medium Dependent (PMD).
  • PMD Physical Medium Dependent
  • the 50G Ethernet service can be transmitted by using one existing 100GE PMD.
  • PMD Physical Medium Dependent
  • FlexE is a group bound by K PHY links, and K is a positive integer.
  • the FlexE Group shown in Figure 1 includes four PHY links.
  • the current flexible Ethernet implementation recommends only supporting 100G PHY links.
  • FlexE's PHY link can support 400G PHY links.
  • the Flex Ethernet Client (FlexE Client) is a MAC-based Ethernet traffic that can be at the same or different rate than an existing Ethernet PHY link, such as 10Gb/s, 40Gb/s, or 25Gb/s. .
  • the client can be called a client, or a client, or a service.
  • the Flex Ethernet Shim (FlexE Shim) is the logical layer used to map FlexE Client data to the FlexE Group and to demap FlexE Group data to the FlexE Client. Similar to Multi-Link Gearbox (MLG) technology, FlexE Shim acts as a multiplexing function in the transmit direction, mapping data from the FlexE Client to the FlexE Group; instead, it is demultiplexed in the receive direction. Function to unmap data from FlexE Group to FlexE Client.
  • MLG Multi-Link Gearbox
  • FlexE uses the Synchronous Digital Hierarchy (SDH)/Optical Transport Network (OTN) technology to construct a fixed frame format for physical interface transmission and time division multiplexing (TDM) slot division.
  • . 2 is a schematic diagram of code blocks on a PHY link in accordance with an embodiment of the present application. Different from SDH/OTN, FlexE's TDM slot division granularity is 66 bits, which can correspond to a 64B/66B coded block. The data on each PHY link of FlexE is aligned by periodically inserting FlexE overhead (Overhead, OH) code blocks, specifically inserting a 66B FlexE overhead code block every 1023 ⁇ 20 66B data code blocks, as shown in the figure. 2 is shown. For the scenario of a 100G PHY link, the interval between adjacent FlexE overhead code blocks is 13.1 microseconds.
  • SDH Synchronous Digital Hierarchy
  • OTN Optical Transport Network
  • the FlexE 1.0 standard specifies that the FlexE Client is 64/66B encoded to obtain a block stream. After Idle Insert/Delete is used for rate adaptation, a block stream of flexible Ethernet services is formed. The code blocks in the code block stream of the flexible Ethernet service are placed in a time slot allocated to the flexible Ethernet service. The idle code block may also be referred to as a stuff code block.
  • the frames of the FlexE are classified into basic frames and multiframes.
  • a FlexE basic frame contains 8 lines, and the first 66B block position of each line is a FlexE overhead code block, and the overhead code block is followed by a payload area for slot division (1023 ⁇ 20 66B payload data code blocks).
  • the bandwidth of a 100GE interface is divided into 20 time slots, and the bandwidth of each time slot is about 5 Gbps.
  • the 32 basic frames constitute a multiframe.
  • FIG. 3 is a schematic diagram of overhead code blocks in a FlexE basic frame according to an embodiment of the present application.
  • the first code block in the FlexE basic frame has a "0x4B" or "0x5" field as a tag field for identifying the code block as an overhead code block.
  • the receiving end device After the receiving end device recognizes the overhead code block, it can receive the next overhead code block after receiving 1023 ⁇ 20 64/66B code blocks (data code blocks), and so on, and can extract the entire FlexE from the code block stream.
  • the overhead code block includes some fields for a particular indication.
  • the FlexE overhead code block transmitted on each link includes a FlexE Group Number, a Physical Link Map (PHY Map), a Physical Link Number (PHY Number), and a Time Slot Allocation Table (Calendar).
  • A Calendar B and other fields.
  • the FlexE Group Number is used to indicate the flexible Ethernet group number in which the link is located;
  • the distribution of the PHY map is used to control which PHYs are members of this group; the physical link number can be 1 to 254; Calendar A and Calendar B Used to indicate the current Calendar configuration and alternate Calendar configuration for the FlexE Group.
  • each FlexE basic frame There are 16 bits in the third code block of each FlexE basic frame to indicate the number of the service data transmitted on the time slot.
  • the first FlexE frame in each FlexE multiframe carries the number of the service data transmitted in slot 0 (slot 0), and so on, until the 20th FlexE basic frame in the FlexE multiframe carries the corresponding slot 19 The number of the transmitted business data.
  • the receiving device After receiving the FlexE basic frame information on all links in the FlexE Group, the receiving device can obtain the time slot allocation mode of each service data in the FlexE Group.
  • field C is used to indicate the calendar configuration in use.
  • OMF is an Overhead Multiframe Indicator.
  • RPF is a Remote PHY Fault. Res and Reserved are reserved fields.
  • the PHY Number is the Identity of this PHY within the group in the FlexE Group.
  • CR is a switch request slot allocation table (Calendar Switch Request).
  • the CA is a switch confirmation time slot allocation table (Calendar Switch Acknowledge).
  • Ss is a valid sync header bit, including 2 bits, and 2 bits can be 01 or 10.
  • the CRC is a Cyclic Redundancy Check bit. It can be seen from Figure 3 that there are still some reserved fields in the overhead code block, in addition to five 66B code blocks used as management channels for transmitting information outside the data payload between the two FlexE devices.
  • FIG. 4 is a schematic diagram of the loss of the service clock during the transmission of the service data in the FlexE.
  • Services that need to transparently transmit service frequencies are generally CBR services, such as CPRI services and SDH services.
  • the service data of the CBR service (the code block 1 to the code block 8 of the service data shown in FIG. 4) is carried in the process of the respective networks, and the service clock is usually carried in order to ensure a fixed bit rate. Transfer together.
  • the time between one rising edge and the next rising edge of the service clock is called a clock cycle, and the number of clock cycles per second is called a clock frequency.
  • the service data of the CBR service is transmitted by the network of the original transmission CBR service being mapped to several time slots of the FlexE.
  • the time slot bandwidth allocated by the FlexE for the CBR service is larger than the bandwidth of the CBR service, so the mapping of the service data to the FlexE belongs to the asynchronous mapping.
  • the current method is to insert a stuffing block (such as the code block S shown in FIG. 4) into the code block stream of the FlexE data in the code block stream of the service data, thereby realizing the service bandwidth and the transmission slot bandwidth of the FlexE. Rate matching between.
  • the code block stream of FlexE data is transmitted along with the Flexe clock in FlexE.
  • the egress node When the code block stream of the FlexE data is transmitted to the egress node, the egress node removes the stuff block block therein, but the service clock of the service data itself is lost. Since the service clock and the Flexe clock are different sources, the service clock cannot be recovered. In other words, FlexE does not support business frequency passthrough. For services that require transparent transmission of service frequencies, loss of service clock or service frequency is unacceptable.
  • OTN Optical Transmission Network
  • FIG. 5 is a schematic diagram of circuitry for mapping traffic data in an OTN.
  • Figure 5 is a schematic diagram of the processing circuitry of the access node of the CBR service.
  • the access node receives the client data and the client clock, caches the service data, and determines Cn (buffer and determine Cn).
  • the read control reads the server clock and the client clock and uses both to determine Cn.
  • the access node of the CBR service calculates Cn according to the service clock (corresponding to the service frequency, that is, the receiving frequency of the access node) and the service layer clock (corresponding to the service layer frequency, that is, the transmission frequency of the access node), and inserts Cn into the chain.
  • server data is formed for transmission.
  • FIG. 6 is a schematic diagram of circuitry for demapping traffic data in an OTN.
  • Figure 6 is a schematic diagram of the processing circuitry of the egress node of the CBR service.
  • the egress node receives the server data and the server clock, caches the service layer data, and generates a client clock.
  • the read control reads the server clock and Cn and uses both to generate a client clock.
  • the outbound node of the CBR service recovers the service clock (corresponding to the service frequency, that is, the sending frequency of the outgoing node) according to the service layer clock (corresponding to the service layer frequency, that is, the receiving frequency of the outgoing node) and Cn.
  • FlexE For FlexE, if Cn is similarly calculated and Cn is inserted into the overhead code block of the PHY link, the FlexE standard needs to be modified to re-plan the use of the fields in the overhead code block of FlexE.
  • Cn if Cn is transmitted in the overhead code block, Cn must be calculated by using the basic frame period or the multiframe period of the PHY link as a statistical period, which makes the statistical period of Cn and the basic frame period or multiframe period of the PHY link. Strong correlation.
  • FlexE carries various types of services. For different service rates, calculating Cn by the same statistical period will result in poor accuracy of Cn. For example, for a service with a lower rate, if the statistical period is shorter, the error will be larger.
  • FlexE is based on the Ethernet core.
  • the basic frame structure or multiframe structure defined by FlexE has periodicity, which is caused by the insertion of the alignment marker (AM) in the physical coding sublayer (PCS).
  • the jitter of the overhead code block period of FlexE directly affects the accuracy of the Cn calculation, which causes the outbound node of the CBR service to deteriorate according to the quality of the service clock recovered by Cn.
  • the schematic diagram shown in FIG. 4 is directed to a single-hop networking mode, that is, the access node and the egress node are directly connected by a communication cable, and there is no other device in the middle, that is, there is no intermediate node in the middle.
  • the techniques for transparently transmitting service frequencies in the OTN shown in FIG. 5 and FIG. 6 only consider the case of the single-hop networking mode, and cannot solve the problem of frequency transparent transmission in the multi-hop cascaded networking mode.
  • the multi-hop cascading networking mode there are other intermediate nodes between the access node and the egress node.
  • FlexE there are both single-hop networking mode and multi-hop cascade networking mode.
  • Figure 7 is a schematic diagram of a synchronous Ethernet technology in FlexE. Two adjacent devices in the FlexE are connected by a one-hop physical interface and a PHY link.
  • the synchronous Ethernet technology can be used to determine the master slave relationship of the two devices, and the slave device frequency and the master device are implemented. Frequency synchronization.
  • FIG 8 is a schematic diagram of transparent transmission of service frequencies using synchronous Ethernet technology in FlexE.
  • the business data is transmitted as a FlexE customer signal from the client device to the FlexE device via the customer link.
  • the FlexE device which is the access node of the service, uses the service clock as a reference source to generate the FlexE clock through the phase-locked loop as the clock of the FlexE PHY link.
  • On the FlexE transport link one or more FlexE devices acting as intermediate nodes are frequency hop-by-hop using synchronous Ethernet technology.
  • the FlexE device that serves as the egress node of the service uses the FlexE clock as a reference source to generate a service clock to transparently transmit the service clock.
  • the synchronous transmission of the service frequency of the service can only be based on the service clock of a service in the FlexE.
  • FlexE carries various types of services, such as CPRI services and SDH services.
  • FIG. 9 is a schematic structural diagram of a system for transparently transmitting service frequencies according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a multi-hop cascading networking mode of the FlexE. The following is an example of the presence of an intermediate node. However, the multi-hop cascading networking mode of the embodiment of the present application is not limited thereto.
  • the communication link can be unidirectional or bidirectional.
  • FIG. 9 illustrates a communication link in a unidirectional multi-hop cascading networking mode as an example.
  • the system of the multi-hop cascading networking mode of the one-way communication link includes an access node, an intermediate node, and an egress node.
  • the PHY link mapped to Flexe is transmitted to the lower device, and the lower device can be an intermediate node.
  • An access node may have one or more intermediate nodes cascaded.
  • the intermediate node and the intermediate node and the intermediate node and the outgoing node transmit data through the PHY link.
  • the egress node de-maps the service data from the PHY link and re-transmits the subsequent link through the client link.
  • the access node includes a clock processing unit TIMING TX, a service processing (CLIENT) unit 1, a layer mapping (SHIM_MUX) unit 1, and a PHY link 1.
  • the service processing unit 1 operates in the mapping direction, and is used for the first service data to complete the rate matching of the service data and the insertion of the first service frequency information Xn.
  • the clock processing unit TIMING TX receives the service frequency F client from the service processing unit 1 and receives the transmission frequency F FlexE1 of the FlexE from the PHY link 1 to generate the first service frequency information Xn.
  • the layer mapping unit 1 may be a SHIM_MUX unit defined by the FlexE standard for mapping service data to the PHY link 1.
  • PHY Link 1 is the interface defined by the FlexE standard.
  • the access node records the service frequency information of each service (for example, the first service frequency information Xn corresponding to the first service data and the second service frequency information Wm corresponding to the second service data, etc.) , transferred to the subordinate device.
  • the service frequency information can be transmitted to the subordinate device through the overhead code block of the Flex, so that one or more fields need to be defined in the overhead code block of the Flex to carry the service frequency information of one or more services.
  • the service frequency information of each service can also be transmitted in one channel along with the respective data, that is, the service frequency information of each service is encapsulated into a data stream inserted into the service data in the code block and transmitted.
  • the service frequency information may be encapsulated in a code block identified by the O code.
  • code blocks that encapsulate service frequency information may be tagged with other special identifiers.
  • the code block used to encapsulate the service frequency information may be that the S/T bit code block may be a 64/66B code block or an 8/10B code block.
  • O code refers to O code, and its type field may be 0x4B.
  • O code refers to O code, and its type field may be 0x4B.
  • 802.3 standardized O codes use 0x0 and 0xF.
  • the O code of the FlexE overhead block1 defined by OIF FlexE IA 1.0 is currently 0x5.
  • the intermediate node includes a clock processing unit TIMING REGENERATE, a PHY link 2, a layer demapping (SHIM_DEMUX) unit 1, a service processing unit 2, a gateway (SWITCH), a service processing (CLIENT) unit 3, a layer mapping unit 2, and a PHY link 3. .
  • the layer demapping unit 1 may be a SHIM_DEMUX unit defined by the FlexE standard for demapping traffic data from the PHY link 2.
  • the service processing unit 2 is used in the demapping direction to complete the analysis of the service data and the analysis of the service frequency information.
  • the gateway is the switching component of FlexE.
  • the service processing unit 3 operates in the mapping direction, and is used for the first service data to complete the rate matching of the service data and the insertion of the first service frequency information Zn.
  • the processing unit TIMING REGENERATE receives the reception frequency F FlexE1 of the FlexE from the PHY link 2, receives the first service frequency information Xn from the service processing unit 2, and receives the transmission frequency F FlexE2 of the FlexE from the PHY link 3, and generates a new number according to the above information.
  • the layer mapping unit 2 may be a SHIM_MUX unit defined by the FlexE standard for mapping the first service data to the PHY link 3.
  • PHY Link 2 and PHY Link 3 are interfaces defined by the FlexE standard.
  • the service frequency information may be re-statistically calculated according to the actual FlexE frequency (including the transmission frequency and the receiving frequency) of the intermediate node.
  • the intermediate node of the service transmission link it is not necessary to parse all the service data, or even to recover the service frequency.
  • the service frequency information can be recalculated according to the receiving frequency of the intermediate node, the service frequency information, and the transmission frequency of the intermediate node.
  • the intermediate node may encapsulate the newly calculated service frequency information into a data stream inserted into the service data into the code block and transmit the data to the lower device.
  • the outgoing node includes a clock processing unit TIMING RX, a PHY link 4, a layer demapping unit 2, and a service processing unit 4.
  • PHY Link 4 is the interface defined by the FlexE standard.
  • the layer demapping unit 2 may be a SHIM_DEMUX unit defined by the FlexE standard for demapping traffic data from the PHY link 4.
  • the service processing unit 4 is used in the demapping direction to complete the analysis of the service data and the analysis of the service frequency information.
  • the processing unit TIMING RX receives the first service frequency information Zn from the service processing unit 4 and receives the reception frequency F FlexE2 of the FlexE from the PHY link 4, and recovers the service frequency F client of the first service data according to the above information. .
  • FIG. 10 is a schematic structural diagram of a system for transparently transmitting a service frequency according to another embodiment of the present application.
  • FIG. 10 illustrates a communication link in a one-way single-hop networking mode as an example.
  • the system of the one-hop networking mode of the one-way communication link includes an access node and an egress node. After the service data enters the access node through the client link, the PHY link mapped to Flexe is transmitted to the lower device, that is, the egress node. The egress node de-maps the service data from the PHY link and re-transmits the subsequent link through the client link.
  • the access node includes a clock processing unit TIMING TX, a service processing (CLIENT) unit 1, a layer mapping (SHIM_MUX) unit 1, and a PHY link 1.
  • the service processing unit 1 operates in the mapping direction for completing rate matching of the service data and insertion of the service frequency information Xn.
  • the processing unit TIMING TX receives the service frequency F client of the first service data from the service processing unit 1 and the transmission frequency F FlexE1 of the FlexE from the PHY link 1 to generate the first service frequency information Xn.
  • the layer mapping unit 1 may be a SHIM_MUX unit defined by the FlexE standard for mapping the first service data to the PHY link 1.
  • PHY Link 1 is the interface defined by the FlexE standard.
  • the outgoing node includes a clock processing unit TIMING RX, a PHY link 2, a layer demapping unit 1, and a service processing unit 2.
  • PHY Link 2 is the interface defined by the FlexE standard.
  • the layer demapping unit 1 may be a SHIM_DEMUX unit defined by the FlexE standard for demapping the data stream of the first service data from the PHY link 2.
  • the service processing unit 2 is used in the demapping direction to complete the analysis of the service data and the analysis of the service frequency information.
  • the processing unit TIMING RX receives the first service frequency information Xn from the service processing unit 2 and receives the reception frequency F FlexE1 of the FlexE from the PHY link 2, and recovers the service frequency F client of the first service data according to the above information. .
  • the access node or the intermediate node is regarded as the first device, the lower device is the second device, and the second device may be the intermediate node or the outgoing node.
  • 11 is a schematic diagram of a method for an access node to perform a transparent transmission service frequency according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a method for an intermediate node to perform a transparent transmission service frequency according to an embodiment of the present application. Referring to FIG. 11 and FIG. 12, the method for transparently transmitting a service frequency may include the following steps.
  • Step 1 the first device determines the first service frequency information Xn, where the first service frequency information Xn is used to indicate the number of n-bit first service data sent by the first device in the first statistical duration, the first statistical duration is as described above.
  • the transmission frequency of the first device is a reference, where n is a positive integer.
  • the first business data here is the data of the target business we are discussing.
  • the first statistical duration may be determined based on the rate of the first traffic data. If the rate of the first service data is lower than a certain threshold, a longer first statistical duration may be determined, for example, the first statistic is longer than the length of one basic frame or one multiframe; if the rate of the first service data is higher than a certain A threshold may determine a shorter first statistical duration, for example, the first statistical duration is shorter than the length of one basic frame or one multiframe.
  • the first statistical duration is a number of transmission clock cycles that can be the first target.
  • the determining, by the first device, the first service frequency information Xn may include: the first device calculating the first service frequency information Xn by using a first target number (for example, ticks) of transmission clock cycles as a statistical window.
  • a first target number for example, ticks
  • Cn is counted in a frame period in the OTN.
  • FlexE may carry various types of services, and the rates of different types of services vary greatly. For a service with a lower rate, if the statistics period is shorter, the error will be larger. For a service with a higher rate, the statistics period does not need to be too long.
  • the first service frequency information Xn is calculated with reference to the ticks transmission clock period.
  • the ticks can be customized by the network administrator according to the frequency of the service (which can be defined in advance or defined in real time with the transmission of the service), or can be defined by the control device in the corresponding FlexE according to the frequency of the service to adapt to different rates of service. .
  • the network administrator or the control device in the FlexE can set the appropriate statistical duration (statistic window length) according to the rate of the service.
  • the sending clock period of the ticks FlexE is the statistical duration.
  • the statistical duration is decoupled from the basic frame and the multi-frame period, and the optimal statistical duration can be selected according to the rate of the service, so that the statistical service frequency information is more accurate.
  • the FlexE overhead is affected by the AM insertion, and the overhead period is unstable.
  • the custom statistical duration of the embodiment of the present application is not affected by other overheads, and is periodically stable without jitter.
  • the stable statistical duration also makes the statistical service frequency information smoother, and the clock recovered by the out node according to the service frequency information is smoother and the jitter is smaller.
  • the first device may encapsulate the first statistical duration information used to indicate the first statistical duration with the first service frequency information Xn in a first S/T bit code block and send the information to the second device.
  • the first statistical duration information may be an absolute duration of the first statistical duration, or may be information of the first target number (ticks) to save the number of bits.
  • the first statistical duration information and the first service frequency information may also be separately encapsulated and sent to the second device.
  • the first S/T bit code block may also be referred to as an Operations, Administration, Maintenance (OAM) code block.
  • OAM Operations, Administration, Maintenance
  • the ticks can be system presets, at which point it is not necessary to transmit information indicating the number of targets (ticks). Alternatively, the ticks can be uniformly notified to the devices in the system by the control elements of the system. Certainly, the first device may also calculate the first service frequency information Xn by using the basic frame or the multiple frame as the first statistical duration, which is not limited in this embodiment of the present application.
  • the method may further include: determining, by the first device, the first statistical duration according to the rate of the first service data; and determining, by the first device, the first service frequency information Xn, including: The first device counts the number of n-bit first service data transmitted within the first statistical duration. This number is Xn.
  • the first device may determine the first statistic duration according to the rate of the first service data. For example, if the rate of the first service data is lower, a longer first statistic duration may be determined, for example, longer than one basic frame or one multiframe. Length; if the rate of the first service data is high, a shorter first statistical duration may be determined, such as shorter than one basic frame or the length of one multiframe.
  • the first service data that needs to transmit the service frequency enters the access node through a user network interface (UNI) with a bit width that is an integer multiple of n bits.
  • the UNI is also called a user-side interface, that is, between the network and the user. Interface, which is the client link interface.
  • the service frequency of the first service is F client , which is also the receiving frequency of the access node.
  • the clock frequency of FlexE is F FlexE1 , which is also the transmission frequency of the access node.
  • the access node calculates the first service frequency information Xn of the first service.
  • the access node may count the number of n-bit first service data sent in the first statistical duration, for example, the number of n-bit first service data sent by the first device in the ticks transmission clock period, to obtain Xn; Or the first device can calculate Xn in other ways.
  • the first service frequency information Xn may be as shown in the following formula (1).
  • the first service frequency information Xn may not include n. Therefore, the first service frequency information Xn can be as shown in the following formula (2).
  • F client is the original service frequency of the first service data
  • F FlexE1 is the transmission frequency of the access node.
  • the value of the first service frequency information Xn may be equal to the number of n-bit first service data sent within the first statistical duration, or may not It is equal to the quantity, but only corresponds to the quantity or the lower-level device can calculate a value of the quantity according to the related information, which is not limited by the embodiment of the present application.
  • the first device When the first device is an intermediate node, the first device further receives the data stream of the first service data sent by the third device, and parses out the second S/T bit code block of the data stream of the first service data.
  • the first service frequency information Yn The first device determines the first service frequency information Xn, and the first device calculates, according to the first service frequency information Yn, the number of n-bit first service data sent in the first statistical duration.
  • the first service frequency information Xn is obtained.
  • the second S/T bit code block is further encapsulated with the first statistical duration information, where the first statistical duration information is used to indicate the first statistical duration.
  • the first statistical duration information may be the first target quantity.
  • the intermediate node receives the first FlexE data sent by the upper node through the NNI, and the first FlexE data includes an information ticks value indicating the first target quantity and the first service frequency information Yn.
  • the intermediate node demaps the first FlexE data through the layer demapping unit and reads the Yn and ticks values therefrom. Specifically, for example, the OAM code block of the code block can be found to find the OAM code block, and the Yn and ticks values are read.
  • the clock processing unit TIMING REGENERATE uniformly disperses Yn into the received first FlexE data according to the receiving frequency F FlexE1 , and uses the transmission clock period of the Flexe intermediate nodes (corresponding to the transmission frequency F FlexE2 ) as a statistical window.
  • the first service frequency information after the break-up is counted to obtain Xn. It should be understood that if the intermediate node recovers the service data and needs to add the buffer to absorb the data gap after the padding is removed, the recovery of the service data requires a clock recovery circuit, and the cost is also higher. In the embodiment of the present application, the intermediate node does not need to parse and recover the service data, but directly reads out the service frequency information Yn and ticks values of the superior node, and does not need to add additional cache, and the service delay is lower.
  • Step 2 The first device encapsulates the first service frequency information Xn into the first S/T bit code block, inserts the first S/T bit code block into the data stream of the first service data, and sends the second S/T bit code block to the second service data stream.
  • Device where S and T are positive integers.
  • the first S/T bit code block is an S/T bit code block identified by an O code.
  • the access node encapsulates the calculated first service frequency information Xn and ticks values into an S/T bit code block identified by the O code, ie, an OAM code block.
  • An Idle Adjust Processor also known as an idle add/drop unit, places an OAM code block at a position where a normal fill code block is to be placed, or an OAM code block is used as a type of padding block, and is filled in The data code block for carrying the first service data; or, the IAP fills the pad code block between the data code blocks carrying the first service data, and then replaces the pad code block with the OAM code block.
  • the IAP maps these code blocks to the PHY link through the layer mapping unit.
  • the Xn and ticks values form the data stream of the first FlexE data along with the service code blocks in the FlexE data, and are transmitted to the lower-level device through the Network to Network Interface (NNI).
  • NNI Network to Network Interface
  • a second service can also be transmitted in the link of the FlexE.
  • the method for transparently transmitting the service frequency may further include: the first device determining the second service frequency information Wm, where the second service frequency information Wm is used to indicate that the first device is sent within the second statistical duration The number of m-bit second service data, the second statistical duration is based on the transmission frequency of the first device, where m is a positive integer; the first device encapsulates the second service frequency information Wm And the third S/T bit code block is inserted into the data stream of the second service data and sent to the second device.
  • the method for transparently transmitting the service frequency in the embodiment of the present application can support multiple service data with service frequency transparent transmission requirements to simultaneously access the link of the FlexE without changing the existing Flexe standard.
  • each service having a service frequency transparent transmission requirement inserts a padding block into the data stream of the service for rate matching.
  • the method in the embodiment of the present application inserts each service frequency information into the data stream of the respective service data. In the medium, the bandwidth allocated to the service is reasonably utilized, and the other services are not affected, and the scalability is strong.
  • FIG. 13 is a schematic diagram of a method for an outbound node to perform a transparent transmission service frequency according to an embodiment of the present application. Referring to FIG. 13, the method of transparently transmitting a service frequency may include the following steps.
  • Step 1 the fourth device receives the data stream of the first service data sent by the fifth device, where the data stream of the first service data includes a first S/T bit code block, the first S/T bit
  • the code block includes a first service frequency information Zn, and the first service frequency information Zn is used to indicate the number of n-bit first service data sent by the fifth device in the first statistical duration, the first statistical duration Based on the transmission frequency of the fifth device, where n, S, and T are positive integers.
  • the first S/T bit code block is an S/T bit code block identified by an O code.
  • the first service frequency information Zn A ⁇ F client /F FlexE , where A is a frequency coefficient, F client is an original service frequency of the first service data, and F FlexE is a transmission frequency of the fifth device.
  • Step 2 The fourth device recovers the clock corresponding to the first service data according to the first service frequency information Zn.
  • the method for transparently transmitting the service frequency may further include: the first S/T bit code block is further encapsulated with first statistical duration information, where the first statistical duration information is used to indicate the first statistic
  • the second device recovers the clock corresponding to the first service data according to the first service frequency information Zn, and may include: the fourth device according to the first service frequency information Zn and the The first statistical duration information is used to recover the clock corresponding to the first service data.
  • the egress node receives the first FlexE data sent by the upper node through the NNI, where the first FlexE data includes the first service frequency information Zn and the ticks value.
  • the exit node demaps the first FlexE data through the layer demapping unit and reads the Zn and ticks values therefrom.
  • the processing unit TIMING RX recovers the service frequency F client of the first service according to the receiving frequency F FlexE , Zn and ticks values, that is, recovers the service clock of the first service as the transmission clock of the client link.
  • a second service can also be transmitted in the link of the FlexE.
  • the method for transparently transmitting the service frequency may further include: the fourth device receives a data flow of the second service data sent by the fifth device, where the data flow of the second service data includes a second S/T ratio a second code channel, the second service frequency information Vm is used to indicate the n bits sent by the fifth device in the second statistical duration. a quantity of the second service data, where the second statistical duration is based on a transmission frequency of the fifth device, where m is a positive integer; and the fourth device recovers the information according to the second service frequency information Vm The clock corresponding to the second service data.
  • the access node and the egress node of the foregoing embodiment may form a FlexE system in a single-hop networking mode, and the access node generates service frequency information, and the egress node recovers the service clock according to the service frequency information to implement the function of transparently transmitting the service frequency;
  • the node, the at least one intermediate node, and the egress node may form a multi-hop cascading network mode FlexE system, the access node generates service frequency information, the intermediate node regenerates the service frequency information, and the egress node recovers the service clock according to the service frequency information, so as to achieve The function of transmitting business frequencies.
  • the single-hop networking mode has a simple environment and there is no process of recalculating the service frequency information of the intermediate nodes. It should be understood that the simpler the networking environment is, the less the transmission of service frequency information is damaged, and the more accurate the recovered service frequency/service clock.
  • the device of the transparent transmission service frequency of the present application may correspond to a packet bearer device, for example, a network protocol (IP) radio access network (RAN) device, a packet transport network (Packet Transport Network, which plans to load FlexE). PTN) equipment, etc.
  • IP network protocol
  • RAN radio access network
  • Packet Transport Network Packet Transport Network, which plans to load FlexE). PTN
  • the device at the access node of the network for example, the box device can implement the generation of the service frequency information and insert the service frequency information into the filler code block through the interface chip of the line card through the interface card or the frame device.
  • the device at the intermediate node of the network for example, the box device can implement the function of regenerating the service frequency information in the embodiment of the present application through the interface chip of the line card through the interface card or the frame device.
  • the device that is in the outbound node of the network for example, the box device can implement the function of restoring the service clock in the embodiment of the present application through the
  • FIG. 14 is a schematic block diagram of a device 1400 for transparently transmitting service frequencies according to an embodiment of the present application.
  • the device 1400 that transmits the service frequency is the first device.
  • the device 1400 that transmits the service frequency may include:
  • the clock processing unit 1410 is configured to determine the first service frequency information Xn, where the first service frequency information Xn is used to indicate the number of n-bit first service data that is sent by the first device in the first statistical duration.
  • the first statistical duration is based on the transmission frequency of the first device, where n is a positive integer.
  • the service processing unit 1420 is configured to encapsulate the first service frequency information Xn determined by the clock processing unit 1410 into a first S/T bit code block, and insert the first S/T bit code block into Sending to the second device to the data stream of the first service data, where S and T are positive integers.
  • the first S/T bit code block is an S/T bit code block identified by an O code.
  • the first S/T bit code block is further encapsulated with first statistical duration information, where the first statistical duration information is used to indicate the first statistical duration.
  • the first statistical duration is a first target number of sending clock cycles, and the first statistical duration information includes the first target number.
  • the clock processing unit 1410 is further configured to: determine the first statistical duration according to a rate of the first service data; and the clock processing unit 1420 prepares to determine a first service frequency.
  • the information Xn includes: counting the number of n bits of the first service data sent within the first statistical duration.
  • the service processing unit 1420 is further configured to: receive a data flow of the first service data sent by a third device, and a second data flow from the first service data.
  • the first service frequency information Yn is parsed in the S/T bit code block; the clock processing unit 1410 is specifically configured to: calculate, according to the first service frequency information Yn, the n sent in the first statistical duration The number of the first service data is bit-bited to obtain the first service frequency information Xn.
  • the second S/T bit code block is further encapsulated with first statistical duration information, where the first statistical duration information is used to indicate the first statistical duration.
  • the clock processing unit 1410 is further configured to: determine second service frequency information Wm, where the second service frequency information Wm is used to indicate that the first device is in a second statistical duration.
  • the number of m-bit second service data transmitted, the second statistical duration is based on the transmission frequency of the first device, where m is a positive integer;
  • the service processing unit 1420 is further configured to:
  • the second service frequency information Wm is encapsulated into a third S/T bit code block, and the third S/T bit code block is inserted into the data stream of the second service data and sent to the second device.
  • the first service frequency information Xn A ⁇ F client /F FlexE , where A is a frequency coefficient, and F client is a service frequency of the first service data, F FlexE Is the transmission frequency of the first device.
  • clock processing unit 1410 may correspond to the clock processing unit TIMING TX or the clock processing unit TIMING REGENERATE of FIGS. 9 and 10.
  • Traffic processing unit 1420 may correspond to the traffic processing unit, layer mapping unit, and PHY link of FIG. 9 and FIG.
  • clock processing unit 1410 and the service processing unit 1420 in the embodiments of the present application may be implemented by a processor or a processor-related circuit component, and some functions of the service processing unit 1420 may be performed by a network interface or a network interface related circuit component. achieve.
  • the embodiment of the present application further provides a device 1500 for transparently transmitting a service frequency, where the device 1500 for transmitting a service frequency is a first device, and the device 1500 for transmitting a service frequency includes a processor 1510, and a memory 1520.
  • the memory 1520 is used to store instructions, and the processor 1510 and the network interface 1530 are configured to execute instructions stored by the memory 1520.
  • the device 1400 of the transparent transmission service frequency shown in FIG. 14 or the device 1500 of the transparent transmission service frequency shown in FIG. 15 may be used to perform operations or processes related to the terminal device in the foregoing method embodiment, and transparently transmit the service frequency.
  • the operation and/or function of each module in the device 1400 or the device 1500 of the transparent transmission service frequency are respectively implemented in order to implement the corresponding processes in the foregoing method embodiments, and are not described herein again for brevity.
  • FIG. 16 is a schematic block diagram of a device 1600 for transparently transmitting service frequencies according to an embodiment of the present application.
  • the device 1600 that transmits the service frequency is the fourth device.
  • the device 1600 that transparently transmits the service frequency may include:
  • the service processing unit 1610 is configured to receive a data stream of the first service data sent by the fifth device, where the data stream of the first service data includes a first S/T bit code block, where the first S/T bit is The code block includes a first service frequency information Zn, and the first service frequency information Zn is used to indicate the number of n-bit first service data sent by the fifth device in the first statistical duration, the first statistical duration Based on the transmission frequency of the fifth device, where n, S, and T are positive integers.
  • the clock processing unit 1620 is configured to recover a clock corresponding to the first service data according to the first service frequency information Zn.
  • the first S/T bit code block is an S/T bit code block identified by an O code.
  • the first S/T bit code block is further configured with first statistical duration information, where the first statistical duration information is used to indicate the first statistical duration.
  • the clock processing unit 1620 is specifically configured to: recover the clock corresponding to the first service data according to the first service frequency information Zn and the first statistical duration information.
  • the first statistical duration is a first target number of sending clock cycles, and the first statistical duration information includes the first target number.
  • the service processing unit 1610 is further configured to: receive a data flow of the second service data sent by the fifth device, where the data flow of the second service data includes the second S/ a T-bit code block, the second S/T bit code block includes a second service frequency information Vm, and the second service frequency information Vm is used to indicate that the fifth device is sent within a second statistical time period.
  • the number of n-bit second service data, the second statistical duration is based on the transmission frequency of the fifth device, where m is a positive integer;
  • the clock processing unit 1620 is further configured to: according to the second service The frequency information Vm recovers a clock corresponding to the second service data.
  • the first service frequency information Zn A ⁇ F client /F FlexE , where A is a frequency coefficient, and F client is a service frequency of the first service data, F FlexE Is the transmission frequency of the fifth device.
  • clock processing unit 1620 may correspond to the clock processing unit TIMING RX of FIGS. 9 and 10.
  • Traffic processing unit 1610 may correspond to the traffic processing unit, layer demapping unit, PHY link, etc. of Figures 9 and 10.
  • clock processing unit 1620 and the service processing unit 1610 in the embodiments of the present application may be implemented by a processor or a processor-related circuit component, and some functions of the service processing unit 1610 may be performed by a network interface or a network interface related circuit component. achieve.
  • the embodiment of the present application further provides a device 1700 that transmits a service frequency, where the device 1700 that transmits the service frequency is a fourth device, and the device 1700 that transmits the service frequency includes a processor 1710, and the memory 1720. And a network interface 1730 for storing instructions, the processor 1710 and the network interface 1730 for executing instructions stored by the memory 1720.
  • processors mentioned in the embodiment of the present application may be a central processing unit (CPU), and may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits ( Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory referred to in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM). SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synchronous Connection Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (DR RAM).
  • processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) is integrated in the processor.
  • memories described herein are intended to comprise, without being limited to, these and any other suitable types of memory.
  • the embodiment of the present application further provides a computer readable storage medium, where stored with instructions stored, when the instructions are run on a computer, causes the computer to execute the method of the foregoing method embodiments.
  • the computer may be the first device or the fourth device described above.
  • the embodiment of the present application further provides a computer program product comprising instructions, wherein when the computer runs the finger of the computer program product, the computer executes the method of the foregoing method embodiment.
  • the computer program product can run on the first device or the fourth device.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (DVD)), or a semiconductor medium (for example, a solid state hard disk (Solid State Disk, SSD)) and so on.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • semiconductor medium for example, a solid state hard disk (Solid State Disk, SSD)
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Time-Division Multiplex Systems (AREA)
  • Communication Control (AREA)

Abstract

本申请提供了一种透传业务频率的方法和设备，该方法包括：第一设备确定第一业务频率信息Xn，第一业务频率信息Xn用于指示第一设备在第一统计时长内发送的n比特第一业务数据的数量，第一统计时长以第一设备的发送频率为基准；第一设备将第一业务频率信息Xn封装到第一S/T比特码块中，将第一S/T比特码块插入到第一业务数据的数据流中发送给第二设备。本申请的方法可以支持多个有业务频率透传需求的业务数据同时接入FlexE的链路，而不需要改动现有Flexe标准，由于Flexe中，每个有业务频率透传需求的业务本身都会在业务的数据流中插入填充码块进行速率匹配，本方法合理地利用分配给该业务带宽，不对其它业务造成影响。

Description

透传业务频率的方法和设备
本申请要求于2017年08月11日提交中国专利局、申请号为201710687136.8、申请名称为“透传业务频率的方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及传送网领域，并且更具体地，涉及一种透传业务频率的方法和设备。
背景技术
光联网论坛(Optical Internetworking Forum，OIF)在2016年4月发布的技术建议中提出了灵活以太网(Flexible Ethernet，FlexE)的概念，随后FlexE得到越来越广泛的应用。以FlexE为基础的承载网络，在应用中会接收各种类型的业务。其中一些业务有频率透传的需求，例如通用公共无线接口(Common Public Radio Interface，CPRI)业务和同步数字体系(Synchronous Digital Hierarchy，SDH)业务等固定比特率(Constant Bit Rate，CBR)业务。目前FlexE并不支持业务频率透传。尤其是多种业务都有频率透传的需求，而这几种业务的频率又不同源时，现有的设备难以实现透传业务频率。
发明内容
本申请提供一种透传业务频率的方法和设备，能够支持多个有业务频率透传需求的业务数据同时接入FlexE的链路，而不需要改动现有Flexe标准。
第一方面，提供了一种透传业务频率的方法，包括：第一设备确定第一业务频率信息Xn，所述第一业务频率信息Xn用于指示所述第一设备在第一统计时长内发送的n比特第一业务数据的数量，所述第一统计时长以所述第一设备的发送频率为基准，其中，n为正整数；所述第一设备将所述第一业务频率信息Xn封装到第一S/T比特码块中，将所述第一S/T比特码块插入到所述第一业务数据的数据流中发送给第二设备，其中，S和T为正整数。
第一方面的透传业务频率的方法，可以支持多个有业务频率透传需求的业务数据同时接入FlexE的链路，而不需要改动现有Flexe标准。由于Flexe中，每个有业务频率透传需求的业务本身都会在业务的数据流中插入填充码块进行速率匹配，第一方面的方法将第一业务频率信息插入到第一业务数据的数据流中，合理地利用分配给该业务带宽，不对其它业务造成影响。
应理解，n比特第一业务数据是统计第一业务数据时使用的单位
还应理解，第一统计时长可以是基于第一业务数据的速率确定的。如果第一业务数据的速率低于某一阈值，可以确定一个较长的第一统计时长，例如第一统计时长长于一个基本帧或者一个复帧的长度；如果第一业务数据的速率高于某一阈值，可以确定一个较短的 第一统计时长，例如第一统计时长短于一个基本帧或者一个复帧的长度。
还应理解，S/T比特码块可以是64/66B码块或者8/10B码块等。
在第一方面的一种可能的实现方式中，所述第一S/T比特码块为O码标识的S/T比特码块。在本实现方式中，以特殊的标识符标记封装有第一业务频率信息Xn的码块，方便下级设备识别并解析该S/T比特码块。
应理解，O码是指O code，其类型字段(type field)可以为0x4B。目前802.3已经标准化的O码使用0x0和0xF。目前OIF FlexE执行协议(Implementation Agreement，IA)1.0定义的FlexE开销码块(overhead block)1的O码为0x5。
在第一方面的一种可能的实现方式中，所述第一S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长。
在第一方面的一种可能的实现方式中，所述第一统计时长为第一目标数量个发送时钟周期，所述第一统计时长信息包括所述第一目标数量。本实现方式中计算业务频率信息时，统计时长与基本帧和复帧周期解耦，可根据业务的速率，针对性地选择最佳的统计时长，使得统计的业务频率信息更准确。
在第一方面的一种可能的实现方式中，所述方法还包括：所述第一设备根据所述第一业务数据的速率确定所述第一统计时长；所述第一设备确定第一业务频率信息Xn，包括：所述第一设备统计在所述第一统计时长内所发送的n比特所述第一业务数据的数量。本实现方式中，第一设备作为接入节点。
在第一方面的一种可能的实现方式中，所述方法还包括：所述第一设备接收第三设备发送的所述第一业务数据的数据流，从所述第一业务数据的数据流的第二S/T比特码块中解析出第一业务频率信息Yn；所述第一设备确定第一业务频率信息Xn，包括：所述第一设备根据所述第一业务频率信息Yn，计算在所述第一统计时长内所发送的n比特所述第一业务数据的数量，得到所述第一业务频率信息Xn。本实现方式中，第一设备作为中间节点，使得本实现方式可以支持多跳级联组网模式。
在第一方面的一种可能的实现方式中，所述第二S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长。
在第一方面的一种可能的实现方式中，所述方法还包括：所述第一设备确定第二业务频率信息Wm，所述第二业务频率信息Wm用于指示所述第一设备在第二统计时长内发送的m比特第二业务数据的数量，所述第二统计时长以所述第一设备的发送频率为基准，其中，m为正整数；所述第一设备将所述第二业务频率信息Wm封装到第三S/T比特码块中，将所述第三S/T比特码块插入到所述第二业务数据的数据流中发送给所述第二设备。本实现方式的方法可以支持多个有业务频率透传需求的业务数据同时接入设备。
在第一方面的一种可能的实现方式中，所述第一业务频率信息Xn＝A·F client/F FlexE，其中，A为频率系数，F client为所述第一业务数据的业务频率，F FlexE为所述第一设备的发送频率。
第二方面，提供了一种透传业务频率的方法，包括：第四设备接收第五设备发送的第一业务数据的数据流，所述第一业务数据的数据流中包括第一S/T比特码块，所述第一S/T比特码块中包括第一业务频率信息Zn，所述第一业务频率信息Zn用于指示所述第五设备在第一统计时长内发送的n比特第一业务数据的数量，所述第一统计时长以所述第五 设备的发送频率为基准，其中，n、S和T为正整数；所述第四设备根据所述第一业务频率信息Zn，恢复所述第一业务数据对应的时钟。
第二方面的透传业务频率的方法，可以支持多个有业务频率透传需求的业务数据同时接入FlexE的链路，而不需要改动现有Flexe标准。由于Flexe中，每个有业务频率透传需求的业务本身都会在业务的数据流中插入填充码块进行速率匹配，第二方面的方法，将第一业务频率信息插入到第一业务数据的数据流中，合理地利用分配给该业务带宽，不对其它业务造成影响。
在第二方面的一种可能的实现方式中，所述第一S/T比特码块为O码标识的S/T比特码块。
在第二方面的一种可能的实现方式中，所述第一S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长，所述第四设备根据所述第一业务频率信息Zn，恢复所述第一业务数据对应的时钟，包括：所述第四设备根据所述第一业务频率信息Zn和所述第一统计时长信息，恢复所述第一业务数据对应的时钟。
在第二方面的一种可能的实现方式中，所述第一统计时长为第一目标数量个发送时钟周期，所述第一统计时长信息包括所述第一目标数量。
在第二方面的一种可能的实现方式中，所述方法还包括：所述第四设备接收第五设备发送的第二业务数据的数据流，所述第二业务数据的数据流中包括第二S/T比特码块，所述第二S/T比特码块中包括第二业务频率信息Vm，所述第二业务频率信息Vm用于指示所述第五设备在第二统计时长内发送的n比特第二业务数据的数量，所述第二统计时长以所述第五设备的发送频率为基准，其中，m为正整数；所述第四设备根据所述第二业务频率信息Vm，恢复所述第二业务数据对应的时钟。
在第二方面的一种可能的实现方式中，所述第一业务频率信息Zn＝A·F client/F FlexE，其中，A为频率系数，F client为所述第一业务数据的业务频率，F FlexE为所述第五设备的发送频率。
第三方面，提供了一种透传业务频率的设备，所述设备为第一设备，用于执行上述第一方面或第一方面的任一可能的实现方式中的方法。具体地，所述透传业务频率的设备可以包括用于执行第一方面或第一方面的任一可能的实现方式中的方法的单元。
第四方面，提供了一种透传业务频率的设备，所述设备为第四设备，用于执行上述第二方面或第二方面的任一可能的实现方式中的方法。具体地，所述透传业务频率的设备可以包括用于执行第二方面或第二方面的任一可能的实现方式中的方法的单元。
第五方面提供一种透传业务频率的设备，该透传业务频率的设备为第一设备，所述透传业务频率的设备包括处理器、存储器和网络接口，所述存储器用于存储指令，所述处理器和网络接口用于执行所述存储器存储的指令，并且对所述存储器中存储的指令的执行使得所述处理器和网络接口执行第一方面或第一方面的任一可能的实现方式中的方法。
第六方面提供一种透传业务频率的设备，该透传业务频率的设备为第四设备，所述透传业务频率的设备包括处理器、存储器和网络接口，所述存储器用于存储指令，所述处理器和网络接口用于执行所述存储器存储的指令，并且对所述存储器中存储的指令的执行使得所述处理器和网络接口执行第二方面或第二方面的任一可能的实现方式中的方法。
第七方面提供一种计算机存储介质，其上存储有指令，当所述指令在计算机上运行时， 使得所述计算机执行第一方面或第一方面的任一种可能的实现方式所述的方法。
第八方面提供一种计算机存储介质，其上存储有指令，当所述指令在计算机上运行时，使得所述计算机执行第二方面或第二方面的任一种可能的实现方式所述的方法。
第九方面提供一种包括指令的计算机程序产品，当计算机运行所述计算机程序产品的所述指时，所述计算机执行第一方面或第一方面的任一种可能的实现方式所述的方法。
第十方面提供一种包括指令的计算机程序产品，当计算机运行所述计算机程序产品的所述指时，所述计算机执行第二方面或第二方面的任一种可能的实现方式所述的方法。
第二方面至第十方面所能获得的效果与第一方面所能获得的效果对应，此处不再一一赘述。
附图说明
图1是本申请实施例的FlexE架构的示意图。
图2是本申请一个实施例的PHY链路上码块的示意图。
图3是本申请一个实施例的FlexE基本帧中开销码块的示意图。
图4是业务数据在FlexE中传输的过程中业务时钟丢失的示意图。
图5是OTN中用于映射业务数据的电路的示意图。
图6是OTN中用于解映射业务数据的电路的示意图。
图7是FlexE中同步以太网技术的示意图。
图8是FlexE中采用同步以太网技术透传业务频率的示意图。
图9是本申请一个实施例的透传业务频率的系统的示意性架构图。
图10是本申请另一个实施例的透传业务频率的系统的示意性架构图。
图11是本申请一个实施例的接入节点执行透传业务频率的方法的示意图。
图12是本申请一个实施例的中间节点执行透传业务频率的方法的示意图。
图13是本申请一个实施例的出节点执行透传业务频率的方法的示意图。
图14是本申请一个实施例的透传业务频率的设备的示意性框图。
图15是本申请另一个实施例的透传业务频率的设备的示意性框图。
图16是本申请另一个实施例的透传业务频率的设备的示意性框图。
图17是本申请另一个实施例的透传业务频率的设备的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
应理解，本申请实施例的技术方案可以应用于FlexE或其他基于以太网技术的网络或灵活光传送网(Flexible OTN，FlexO)等网络，本申请实施例对此不作限定。下文中仅以FlexE为例进行描述。
应理解，本申请实施例的物理连接链路可以简称为“链路”，在FlexE中链路也可以称为“物理层(Physical Layer，PHY)链路”。
下面对本说明书中涉及的概念进行简单的介绍。
FlexE技术：
电气和电子工程师协会(Institute of Electrical and Electronics Engineers，IEEE)定义 的基于802.3协议的以太网在过去的相当一段时间内获得了广泛的应用和长足的发展。在以太网中，以太网端口通常作为面向数据的逻辑上的概念出现，称为逻辑端口或简称为端口，以太网物理接口则为硬件上的概念出现，称为物理接口或简称为接口。通常，一个以太网端口以一个介质访问控制(Media Access Control，MAC)地址标记。传统的以太网端口的速率的确定以以太网物理接口的速率为基础。一般情况下，一个以太网端口最大带宽对应一个以太网物理接口的带宽。
近年来，以太网接口速率以10倍提升，从10Mbps向100Mbps、1000Mbps(1Gbps)、10Gbps、40Gbps、100Gbps、400Gbps不断演进发展。但是随着技术的发展，各种场景对带宽颗粒的要求差异越大，使得现有的以太网与实际的应用需求期望产生了较大的偏差。具体而言，主流应用需求的带宽增长并不呈现10倍增长特征，例如主流应用需求的带宽包括50Gbps、75Gbps、200Gbps等。50Gbps如果用100GE来传输会存在资源浪费，200Gbps当前没有对应的以太网标准颗粒可以承载，等等。因此，业界希望提供对50Gbps、60Gbps、75Gbps、200Gbps和150Gbps等带宽的以太网端口(虚拟连接)的支持。
业界希望能够提供一些灵活带宽的以太网端口，这些以太网端口可以共同使用一个或者若干个以太网物理接口，例如2个40GE端口和2个10GE端口共同使用一个100G物理接口；再如，以太网端口能够随着需求的变化做出灵活的速率调整，例如从200Gbps调整为330Gbps，或者50Gbps调整为20Gbps，以提高以太网端口使用效率或者延长其使用生命周期。对于固定速率的物理链路，可以将其级联捆绑，以支持逻辑端口速率的堆叠增加(例如，将2个100GE物理接口堆叠级联捆绑以支持200GE逻辑端口)。另一方面，能够将物理接口灵活堆叠所得到的带宽资源池化，将其带宽按照颗粒(例如，5G为一个颗粒)分配给特定的以太网逻辑端口，实现若干以太网虚拟连接对堆叠级联的物理链路组的高效共享。
OIF在2016年4月发布的灵活以太网实现建议(Flex Ethernet Implementation Agreement)中，提出了FlexE的概念。FlexE具体是将几个以太网PHY链路建立成一个灵活以太网群(Flex Ethernet Group，FlexE Group)，并提供一种支持不同以太网MAC速率的通用机制，以支持针对以太网业务的绑定、子速率、通道化等功能。
FlexE提供的MAC速率可以大于单条PHY链路的速率(通过绑定实现)，也可以小于单条PHY链路的速率(通过子速率和通道化实现)。例如，针对以太网业务的绑定场景，能够支持将200G的以太网业务(MAC码流)采用2路现有的100GE的物理媒质相关子层(Physical Medium Dependent，PMD)进行传送。针对以太网业务的子速率应用场景，能够支持将50G的以太网业务采用1路现有的100GE的PMD进行传送。还有一种针对以太网业务的通道化场景，能够支持若干个逻辑端口共同使用一个或者多个物理接口，能够支持将一个150G太网业务和2个25G太网业务采用2路现有的100GE的PMD进行传送。
现有的一种FlexE的具体架构的示意图可以如图1所示。FlexE是由K条PHY链路绑定的群，K的取值为正整数，图1中示出的FlexE Group中包括4条PHY链路。当前的灵活以太网实现建议仅支持100G的PHY链路，未来待IEEE P802.3bs完善400GE的标准之后，FlexE的PHY链路可以支持400G的PHY链路。灵活以太网客户(Flex Ethernet Client，FlexE Client)是基于MAC的以太网数据流，其速率可以与现有以太网PHY链路的速率 相同或不同，例如10Gb/s、40Gb/s或25Gb/s。其中，Client可以称为客户，也可以称为客户端，或者称为业务。灵活以太网层(Flex Ethernet Shim，FlexE Shim)是用来将FlexE Client的数据映射到FlexE Group以及将FlexE Group的数据解映射到FlexE Client的逻辑层。类似于多链路变速箱(Multi-Link Gearbox，MLG)技术，FlexE Shim在发送方向起到复用的功能，将数据从FlexE Client映射到FlexE Group；相反，在接收方向起到解复用的功能，将数据从FlexE Group解映射到FlexE Client。
FlexE借鉴同步数字体系(Synchronous Digital Hierarchy，SDH)/光传送网(Optical Transport Network，OTN)技术，对物理接口传输构建固定帧格式，并进行时分复用(Time Division Multiplexing，TDM)的时隙划分。图2是本申请一个实施例的PHY链路上码块的示意图。与SDH/OTN不同的是，FlexE的TDM时隙划分粒度是66比特，正好可以对应承载一个64B/66B编码块。FlexE每条PHY链路上的数据通过周期性插入FlexE开销(Overhead，OH)码块来实现对齐，具体是每间隔1023×20个66B数据码块插入1个66B的FlexE开销码块，如图2所示。对应100G的PHY链路的场景，相邻FlexE开销码块出现的时间间隔是13.1微秒。
FlexE 1.0标准规定将FlexE Client进行64/66B编码后得到码块流(block stream)，经过空闲码块插入/删除(Idle Insert/Delete)进行速率适配之后形成灵活以太网业务的码块流，将灵活以太网业务的码块流中的码块轮流放入分配给该灵活以太网业务的时隙中。其中，空闲码块也可以称为填充(stuff)码块。
FlexE的帧区分为基本帧和复帧。一个FlexE基本帧包含8行，每行第一个66B块位置为FlexE开销码块，开销码块后为进行时隙划分的净荷区域(1023×20个66B净荷数据码块)。以100GE为例，100GE接口的带宽划分20个时隙，每个时隙的带宽约为5Gbps。32个基本帧构成一个复帧。
图3是本申请一个实施例的FlexE基本帧中开销码块的示意图。FlexE基本帧中第一个码块以“0x4B”或“0x5”字段作为标记字段，以用于识别该码块为开销码块。当接收端设备识别到该开销码块后，再接收1023×20个64/66B码块(数据码块)后可收到下一个开销码块，依次类推可从码块流中提取出整个FlexE基本帧。从图3中可以看出开销码块包括用于特定指示的一些字段。例如，各个链路上传输的FlexE开销码块中包括灵活以太网组编号(FlexE Group Number)、物理链路图(PHY Map)、物理链路编号(PHY Number)、时隙分配表(Calendar)A、Calendar B等字段。FlexE Group Number用于指示该链路所在的灵活以太网组编号；PHY Map(一个FlexE复帧中共需8×32＝256bits来指示)用于指示该链路所在的灵活以太网组中包括的PHY的分布，即PHY图(PHY Map)用于控制哪些条PHY链路是群组的成员(control of which PHYs are members of this group)；物理链路编号可以是1～254；Calendar A与Calendar B分别用于指示该FlexE Group的当前Calendar配置与备用Calendar配置。每个FlexE基本帧的第三个码块中有16bit用于指示时隙上所传输的业务数据的编号。每个FlexE复帧中的第一个FlexE帧携带对应时隙0(slot 0)中所传输的业务数据的编号，以此类推，直到FlexE复帧中第20个FlexE基本帧携带对应slot 19中所传输的业务数据的编号。接收端设备收到FlexE Group中所有链路上的FlexE基本帧信息后，即可得到该FlexE Group中各个业务数据的时隙分配方式。
此外，字段C用于指示被使用的时隙分配表(calendar configuration in use)。OMF 为开销多帧指示符(Overhead Multiframe Indicator)。RPF为远程PHY故障(Remote PHY Fault)。Res和Reserved为保留字段。PHY编号(PHY Number)是FlexE Group中该PHY的标识(Identity of this PHY within the group)。CR是开关请求时隙分配表(Calendar Switch Request)。CA是开关确认时隙分配表(Calendar Switch Acknowledge)。ss是有效同步头比特(Valid sync header bits)，包括2比特，2比特可以为01或10。CRC是循环冗余校验(Cyclic Redundancy Check)位。从图3中可以看出目前开销码块中还有一些保留字段，此外还有5个66B的码块用作管理通道，用于在两个FlexE设备之间传输数据净荷之外的信息。
业务频率和业务时钟：
图4是业务数据在FlexE中传输的过程中业务时钟丢失的示意图。需要透传业务频率的业务一般为CBR业务，例如CPRI业务和SDH业务等。如图4所示，CBR业务的业务数据(如图4所示的业务数据的码块1至码块8)在各自的网络进行传输的过程中，为了保证固定的比特率，通常携带业务时钟一起传输。其中，业务时钟的一个上升沿到下一个上升沿之间的时间称为时钟周期，每秒内时钟周期的个数称为时钟频率。
在接入节点处，CBR业务的业务数据由原传输CBR业务的网络被映射到FlexE的若干个时隙中传输。通常，FlexE为CBR业务分配的时隙带宽大于CBR业务的带宽，因此业务数据映射到FlexE属于异步映射。当前采用的方法是在业务数据的码块流中插入填充(stuff)码块(如图4所示的码块S)形成FlexE数据的码块流，从而实现业务带宽和FlexE的传输时隙带宽之间的速率匹配。FlexE数据的码块流在FlexE中携带Flexe时钟一起传输。FlexE数据的码块流被传输到出节点时，出节点将其中的stuff码块移除，但是业务数据本身的业务时钟丢失。由于业务时钟和Flexe时钟是不同源的，所以业务时钟无法恢复，这会。换句话说，FlexE并不支持业务频率透传。对于需要透传业务频率的业务来说，业务时钟或者说业务频率的丢失是不可接受的。
光传输网络(Optical Transmission Network，OTN)中透传业务频率的技术：
OTN采用使用OTN开销传递单个服务帧或者服务复帧承载的n比特业务数量(number of client n-bit data entities per server frame or server multiframe，Cn)的方式来透传业务频率。图5是OTN中用于映射业务数据的电路的示意图。换句话说，图5是CBR业务的接入节点的处理电路的示意图。接入节点接收业务数据(client data)和业务时钟(client clock)，将业务数据进行缓存，并确定Cn(buffer and determine Cn)。具体而言，读取控件(read control)读取服务层时钟(server clock)和业务时钟(client clock)，并将二者用于确定Cn。CBR业务的接入节点根据业务时钟(对应于业务频率，即接入节点的接收频率)和服务层时钟(对应于服务层频率，即接入节点的发送频率)计算Cn，将Cn插入到链路的开销(overhead)码块中，形成服务层数据(server data)进行传输。
图6是OTN中用于解映射业务数据的电路的示意图。换句话说，图6是CBR业务的出节点的处理电路的示意图。出节点接收服务层数据(server data)和服务层时钟(server clock)，将服务层数据进行缓存，并生成业务时钟(client clock)。具体而言，读取控件(read control)读取服务层时钟(server clock)和Cn，并将二者用于生成业务时钟(client clock)。CBR业务的出节点根据服务层时钟(对应于服务层频率，即出节点的接收频率)和Cn，恢复出业务时钟(对应于业务频率，即出节点的发送频率)。
对于FlexE而言，如果类似地，计算Cn并将Cn插入到PHY链路的开销码块中传输，需要改动FlexE标准，重新规划FlexE的开销码块中各字段的使用。另外，Cn放在开销码块中传输，就必须以PHY链路的基本帧周期或者复帧周期为统计周期来计算Cn，这使得Cn的统计周期与PHY链路的基本帧周期或者复帧周期强相关。然而，FlexE承载各种类型的业务，对于不同的业务速率而言，以相同的统计周期来统计计算Cn，会导致Cn的精度比较差。例如，对于速率比较低的业务，如果统计周期较短，误差就会比较大。此外，FlexE是基于以太网内核的，FlexE定义的基本帧结构或者复帧结构具有周期性，在物理编码子层(physical coding sublayer，PCS)，由于对齐标记(Alignment Marker，AM)的插入，导致了FlexE的开销码块周期的抖动。开销码块周期的抖动直接影响Cn计算的准确性，会导致CBR业务的出节点根据Cn恢复的业务时钟质量变差。
图4示出的示意图针对的是单跳组网模式，即接入节点和出节点这两台设备直接通过通信线缆进行物理连接，中间没有其他设备，即中间没有中间节点。图5和图6示出的OTN中透传业务频率的技术，也只考虑了单跳组网模式的情况，无法解决多跳级联组网模式下频率透传的问题。多跳级联组网模式下，接入节点和出节点之间还有其他的中间节点。FlexE中既存在单跳组网模式又存在多跳级联组网模式。对于多跳级联组网模式，在传输FlexE数据的过程中，每一级设备虽然具有相同的标称频率，但实际频率会有一定的差别。如果仍采用图5和图6的技术，由于Cn是相对接入节点的频率计算的，直接透传Cn的话会导致恢复的业务时钟质量很差。
FlexE中透传业务频率的技术：
图7是FlexE中同步以太网技术的示意图。FlexE中两个相邻的设备之间通过一跳物理接口和PHY链路连接，可以采用同步以太网技术确定两个设备的主(master)从(slave)关系，并实现从设备频率与主设备频率同步。
图8是FlexE中采用同步以太网技术透传业务频率的示意图。业务数据作为FlexE的客户信号从客户设备经由客户链路被传输至FlexE设备。作为业务的接入节点的FlexE设备以业务时钟作为参考源，通过锁相环产生FlexE时钟，作为FlexE的PHY链路的时钟。在FlexE的传输链路上，采用同步以太技术，对作为中间节点的一个或多个FlexE设备逐跳进行频率同步。作为业务的出节点的FlexE设备以FlexE时钟作为参考源，产生业务时钟，实现业务时钟的透传。
然而，采用同步以太网技术透传业务频率，只能以FlexE中一个业务的业务时钟为参考，只能解决一项业务的业务频率透传需求。FlexE作为承载网络，会承载各种类型的业务，例如CPRI业务和SDH业务等。当有多个业务都有业务频率透传需求，而这几个业务的业务时钟又不同源时，同步以太网技术并不能实现多个业务的业务频率透传。
为了解决上述问题，本申请实施例提供了一种透传业务频率的方法。图9是本申请一个实施例的透传业务频率的系统的示意性架构图。图9示出的是FlexE的多跳级联组网模式的架构，图中以存在一个中间节点为例进行说明，但本申请实施例的多跳级联组网模式不限于此。
在FlexE中通信链路可以是单向的，也可以是双向的。
图9以单向的多跳级联组网模式的通信链路为例进行说明。单向通信链路的多跳级联组网模式的系统中包括接入节点、中间节点和出节点。业务数据通过客户链路进入接入节 点后，映射到Flexe的PHY链路传输到下级设备，下级设备可以是中间节点。接入节点可以有一个或多个中间节点级联。中间节点与中间节点以及中间节点与出节点之间通过PHY链路传输数据。出节点将业务数据从PHY链路中解映射出来，重新通过客户链路进行后续的传输。
接入节点包括时钟处理单元TIMING TX、业务处理(CLIENT)单元1、层映射(SHIM_MUX)单元1和PHY链路1。业务处理单元1工作在映射方向，对于第一业务数据而言，用于完成业务数据的速率匹配和第一业务频率信息Xn的插入。时钟处理单元TIMING TX从业务处理单元1接收业务频率F client以及从PHY链路1接收FlexE的发送频率F FlexE1，生成第一业务频率信息Xn。层映射单元1可以是FlexE标准定义的SHIM_MUX单元，用于将业务数据映射到PHY链路1。PHY链路1是FlexE标准定义的接口。
本申请实施例中，在接入节点将每个业务的业务频率信息(例如，第一业务数据对应的第一业务频率信息Xn和第二业务数据对应的第二业务频率信息Wm等)记录下来，传输至下级设备。在接入节点，以接入节点的发送频率(即FlexE的频率)为基准，计算每个业务的业务频率和接入节点的FlexE的发送频率F FlexE1之间的关系，得到业务频率信息。业务频率信息可以通过Flex的开销码块传输到下级设备，这样需要在Flex的开销码块中定义一个或多个字段来携带一个或多个业务的业务频率信息。各业务的业务频率信息也可以随各自的数据在一个通道中传递，即每个业务的业务频率信息被封装到码块中插入到业务数据的数据流中传递。可选地，业务频率信息可以封装在在O码标识的码块中。或者，封装了业务频率信息的码块可以以其他特殊标识符来标记。
应理解，本申请各实施例中，用于封装业务频率信息的码块可以是S/T比特码块可以是64/66B码块或者8/10B码块等。
还应理解，O码是指O code，其类型字段(type field)可以为0x4B。目前802.3已经标准化的O码使用0x0和0xF。目前OIF FlexE IA 1.0定义的FlexE overhead block1的O码为0x5。
中间节点包括时钟处理单元TIMING REGENERATE、PHY链路2、层解映射(SHIM_DEMUX)单元1、业务处理单元2、网关(SWITCH)、业务处理(CLIENT)单元3、层映射单元2和PHY链路3。层解映射单元1可以是FlexE标准定义的SHIM_DEMUX单元，用于从PHY链路2将业务数据解映射。业务处理单元2在解映射方向，用于完成业务数据的解析和业务频率信息的解析。网关是FlexE的交换组件。业务处理单元3工作在映射方向，对于第一业务数据，用于完成业务数据的速率匹配和第一业务频率信息Zn的插入。处理单元TIMING REGENERATE从PHY链路2接收FlexE的接收频率F FlexE1，从业务处理单元2接收第一业务频率信息Xn以及从PHY链路3接收FlexE的发送频率F FlexE2，根据以上信息生成新的第一业务频率信息Zn。层映射单元2可以是FlexE标准定义的SHIM_MUX单元，用于将第一业务数据映射到PHY链路3。PHY链路2和PHY链路3是FlexE标准定义的接口。
对于多跳级联组网模式，在传输FlexE数据的过程中，每一级设备虽然具有相同的标称频率，但实际频率会有一定的差别。在每个FlexE设备处使用标称FlexE频率做参考，会造成业务频率信息统计结果不准，最终业务频率恢复性能差。本申请实施例中，在每一个中间节点，可以根据该中间节点的实际FlexE频率(包括发送频率和接收频率)的情况， 重新统计计算业务频率信息。
在业务传输链路的中间节点，不需要将业务数据全部解析出来，甚至不用恢复出业务频率。根据中间节点的接收频率、业务频率信息以及中间节点的发送频率，可以重新计算业务频率信息。中间节点可以将新计算的业务频率信息封装到码块中插入到业务数据的数据流中传递到下级设备。
出节点包括时钟处理单元TIMING RX、PHY链路4、层解映射单元2和业务处理单元4。PHY链路4是FlexE标准定义的接口。层解映射单元2可以是FlexE标准定义的SHIM_DEMUX单元，用于从PHY链路4将业务数据解映射。业务处理单元4在解映射方向，用于完成业务数据的解析和业务频率信息的解析。对于第一业务数据，处理单元TIMING RX从业务处理单元4接收第一业务频率信息Zn以及从PHY链路4接收FlexE的接收频率F FlexE2，根据上述信息恢复出第一业务数据的业务频率F client。
图10是本申请另一个实施例的透传业务频率的系统的示意性架构图。图10以单向的单跳组网模式的通信链路为例进行说明。单向通信链路的单跳组网模式的系统中包括接入节点和出节点。业务数据通过客户链路进入接入节点后，映射到Flexe的PHY链路传输到下级设备，即出节点。出节点将业务数据从PHY链路中解映射出来，重新通过客户链路进行后续的传输。
接入节点包括时钟处理单元TIMING TX、业务处理(CLIENT)单元1、层映射(SHIM_MUX)单元1和PHY链路1。业务处理单元1工作在映射方向，用于完成业务数据的速率匹配和业务频率信息Xn的插入。对于第一业务数据，处理单元TIMING TX从业务处理单元1接收第一业务数据的业务频率F client以及从PHY链路1接收FlexE的发送频率F FlexE1，生成第一业务频率信息Xn。层映射单元1可以是FlexE标准定义的SHIM_MUX单元，用于将第一业务数据映射到PHY链路1。PHY链路1是FlexE标准定义的接口。
出节点包括时钟处理单元TIMING RX、PHY链路2、层解映射单元1和业务处理单元2。PHY链路2是FlexE标准定义的接口。层解映射单元1可以是FlexE标准定义的SHIM_DEMUX单元，用于从PHY链路2将第一业务数据的数据流解映射。业务处理单元2在解映射方向，用于完成业务数据的解析和业务频率信息的解析。对于第一业务数据，处理单元TIMING RX从业务处理单元2接收第一业务频率信息Xn以及从PHY链路2接收FlexE的接收频率F FlexE1，根据上述信息恢复出第一业务数据的业务频率F client。
单跳组网模式的各节点的作用与多跳级联组网模式的相应节点的作用相类似，此处不再进行赘述。
下面从每个节点的角度详细说明本申请实施例的透传业务频率的方法。
将接入节点或中间节点视为第一设备，其下级设备为第二设备，第二设备可以是中间节点也可以是出节点。图11是本申请一个实施例的接入节点执行透传业务频率的方法的示意图。图12是本申请一个实施例的中间节点执行透传业务频率的方法的示意图。结合图11和图12，透传业务频率的方法可以包括以下步骤。
步骤1，第一设备确定第一业务频率信息Xn，第一业务频率信息Xn用于指示第一设备在第一统计时长内发送的n比特第一业务数据的数量，第一统计时长以所述第一设备的发送频率为基准，其中，n为正整数。
应理解，这里的第一业务数据是我们要讨论的目标业务的数据。在FlexE中，可以有更多的业务数据，例如第二业务数据、第三业务数据等等，本申请实施例对此不作限定。
还应理解，第一统计时长可以是基于第一业务数据的速率确定的。如果第一业务数据的速率低于某一阈值，可以确定一个较长的第一统计时长，例如第一统计时长长于一个基本帧或者一个复帧的长度；如果第一业务数据的速率高于某一阈值，可以确定一个较短的第一统计时长，例如第一统计时长短于一个基本帧或者一个复帧的长度。
第一统计时长为可以第一目标数量个发送时钟周期。第一设备确定第一业务频率信息Xn，可以包括：第一设备以第一目标数量(例如ticks)个发送时钟周期为统计窗口，计算第一业务频率信息Xn。应理解，在OTN中以帧为周期统计Cn。FlexE作为承载网络，可能会承载各种类型的业务，不同类型的业务的速率差别较大。对于速率比较低的业务，如果统计周期较短，误差就会比较大；对于速率比较高的业务，统计周期又无需过长。因此，本申请实施例中，以ticks个发送时钟周期为参考，计算第一业务频率信息Xn。ticks可以由网络管理员根据业务的频率自定义(可以是提前定义或者随着业务的传输实时定义)，也可以由相应的FlexE中的控制设备根据业务的频率定义，以适配不同速率的业务。换句话说，网络管理员或者FlexE中的控制设备可以根据业务的速率制定合适的统计时长(统计窗口长度)，例如ticks个FlexE的发送时钟周期为统计时长。本申请实施例中计算业务频率信息时，统计时长与基本帧和复帧周期解耦，可根据业务的速率，针对性地选择最佳的统计时长，使得统计的业务频率信息更准确。并且，FlexE开销会受AM插入的影响，而导致开销周期不稳定，本申请实施例的自定义的统计时长不受其它开销的影响，周期性稳定，不存在抖动。稳定的统计时长，也使得统计的业务频率信息更加平滑，出节点根据业务频率信息恢复出的时钟也就更加平滑，抖动更小。
可选地，第一设备可以将用于指示所述第一统计时长的第一统计时长信息与第一业务频率信息Xn一起封装在第一S/T比特码块中发送给第二设备。第一统计时长信息可以是第一统计时长的绝对时长，也可以是第一目标数量(ticks)的信息以节省比特数量。可选地，第一统计时长信息和第一业务频率信息也可以分别被单独封装并发送给第二设备。第一S/T比特码块也可以称为运营管理维护(Operations,Administration,Maintenance，OAM)码块。
ticks可以是系统预设值，此时不必传输用于指示目标数量(ticks)的信息。或者，ticks可以由系统的控制元件统一通知系统中的各设备。当然，第一设备也可以以基本帧或复帧为第一统计时长，计算第一业务频率信息Xn，本申请实施例对此不做限定。
具体地，在第一设备为接入节点的情况下，该方法还可以包括：第一设备根据第一业务数据的速率确定第一统计时长；第一设备确定第一业务频率信息Xn，包括：第一设备统计在第一统计时长内所发送的n比特第一业务数据的数量。该数量即为Xn。
第一设备可以根据第一业务数据的速率确定第一统计时长，例如，如果第一业务数据的速率较低，可以确定一个较长的第一统计时长，例如长于一个基本帧或者一个复帧的长度；如果第一业务数据的速率较高，可以确定一个较短的第一统计时长，例如短于一个基本帧或者一个复帧的长度。
需要透传业务频率的第一业务数据以n bit的整数倍的位宽通过用户网络接口(User Network Interface，UNI)进入接入节点，UNI也称为用户侧接口，即网络与用户之间的接 口，是客户链路接口。第一业务的业务频率为F client，这也是接入节点的接收频率。FlexE的时钟频率为F FlexE1，这也是接入节点的发送频率。接入节点计算第一业务的第一业务频率信息Xn。具体地，接入节点可以统计第一统计时长内所发送的n比特第一业务数据的数量，例如ticks个发送时钟周期内第一设备发送的n比特第一业务数据的数量，来得到Xn；或者第一设备可以采用其他的方式计算Xn。
可选地，第一业务频率信息Xn可以如下述公式(1)所示。
Xn＝(F client/n)×(ticks/F FlexE1)    (1)
应理解，第一业务频率信息Xn中还可以引入其他的参数或系数。或者，当n为系统预设的或FlexE网络中各设备均知晓的参数时，第一业务频率信息Xn中也可以不包括n。因此，第一业务频率信息Xn可以如下述公式(2)所示。
Xn＝A·F client/F FlexE1       (2)
其中，A为频率系数，F client为第一业务数据的原始的业务频率，F FlexE1为接入节点的发送频率。
应理解，在第一业务频率信息Xn中引入其他的参数或系数的情况下，第一业务频率信息Xn的值可以等于第一统计时长内发送的n比特第一业务数据的数量，也可以不等于该数量，而只是与该数量对应或者下级设备可以根据相关信息推算出该数量的一个值，本申请实施例对此不作限定。
在第一设备为中间节点的情况下，第一设备还接收第三设备发送的第一业务数据的数据流，从第一业务数据的数据流的第二S/T比特码块中解析出第一业务频率信息Yn；第一设备确定第一业务频率信息Xn，包括：第一设备根据第一业务频率信息Yn，计算在第一统计时长内所发送的n比特第一业务数据的数量，得到第一业务频率信息Xn。
可选地，第二S/T比特码块中还封装有第一统计时长信息，第一统计时长信息用于指示第一统计时长。第一统计时长信息可以为第一目标数量。
中间节点通过NNI接收上级节点发送的第一FlexE数据，第一FlexE数据中包括用于指示第一目标数量的信息ticks值和第一业务频率信息Yn。中间节点通过层解映射单元将第一FlexE数据解映射，并从中读取出Yn和ticks值。具体地，例如可以码块的O码标识找到OAM码块，而读取出Yn和ticks值。时钟处理单元TIMING REGENERATE按照接收频率F FlexE1，将Yn均匀地打散到接收的第一FlexE数据中，以ticks个中间节点的Flexe的发送时钟周期(对应于发送频率F FlexE2)为统计窗口，重新统计打散后的第一业务频率信息，得到Xn。应理解，如果中间节点恢复业务数据需要添加缓存吸收移除填充码块后的数据缺口，恢复业务数据需要时钟恢复电路，成本也更高。本申请实施例中，中间节点不需要解析恢复出业务数据，而是直接读取出上级节点的业务频率信息Yn和ticks值，不需要额外添加缓存，业务延时更低。
步骤2，第一设备将第一业务频率信息Xn封装到第一S/T比特码块中，将第一S/T比特码块插入到第一业务数据的数据流中发送给第二设备，其中，S和T为正整数。
可选地，所述第一S/T比特码块为O码标识的S/T比特码块。
在一个具体的例子中，接入节点把计算的第一业务频率信息Xn和ticks值，封装到一个O码标识的S/T比特码块，即OAM码块中。空闲调整单元(Idle Adjust Processor，IAP)，又称空闲增加/删除单元将OAM码块放置在原本要放置普通填充码块的位置，或者说将 OAM码块当做填充码块的一种，填充在用于承载第一业务数据的数据码块间；或者，IAP将填充码块填充到承载第一业务数据的数据码块间，然后用OAM码块替换填充码块。IAP将这些码块通过层映射单元映射到PHY链路。换句话说，Xn和ticks值随FlexE数据中的业务码块形成第一FlexE数据的数据流，通过网络网络接口(Network to Network Interface，NNI)一起传输至下级设备。
可选地，在FlexE的链路中还可以传输第二业务。可选地，透传业务频率的方法还可以包括：所述第一设备确定第二业务频率信息Wm，所述第二业务频率信息Wm用于指示所述第一设备在第二统计时长内发送的m比特第二业务数据的数量，所述第二统计时长以所述第一设备的发送频率为基准，其中，m为正整数；所述第一设备将所述第二业务频率信息Wm封装到第三S/T比特码块中，将所述第三S/T比特码块插入到所述第二业务数据的数据流中发送给所述第二设备。应理解，本申请实施例的透传业务频率的方法，可以支持多个有业务频率透传需求的业务数据同时接入FlexE的链路，而不需要改动现有Flexe标准。由于Flexe中，每个有业务频率透传需求的业务本身都会在业务的数据流中插入填充码块进行速率匹配，本申请实施例的方法，将各业务频率信息插入到各自业务数据的数据流中，合理地利用分配给该业务带宽，不对其它业务造成影响，扩展性强。
接下来，从出节点的角度来说明透传业务频率的方法。出节点为第四设备，出节点的上级节点为第五设备。图13是本申请一个实施例的出节点执行透传业务频率的方法的示意图。结合图13，透传业务频率的方法可以包括以下步骤。
步骤1，第四设备接收第五设备发送的第一业务数据的数据流，所述第一业务数据的数据流中包括第一S/T比特码块，所述第一S/T比特码块中包括第一业务频率信息Zn，所述第一业务频率信息Zn用于指示所述第五设备在第一统计时长内发送的n比特第一业务数据的数量，所述第一统计时长以所述第五设备的发送频率为基准，其中，n、S和T为正整数。
可选地，所述第一S/T比特码块为O码标识的S/T比特码块。
可选地，第一业务频率信息Zn＝A·F client/F FlexE，其中，A为频率系数，F client为第一业务数据的原始的业务频率，F FlexE为第五设备的发送频率。
步骤2，第四设备根据第一业务频率信息Zn，恢复第一业务数据对应的时钟。
可选地，透传业务频率的方法还可以包括：所述第一S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长，；步骤2所述第四设备根据所述第一业务频率信息Zn，恢复所述第一业务数据对应的时钟，可以包括：所述第四设备根据所述第一业务频率信息Zn和所述第一统计时长信息，恢复所述第一业务数据对应的时钟。
具体地，出节点通过NNI接收上级节点发送的第一FlexE数据，第一FlexE数据中包括第一业务频率信息Zn和ticks值。出节点通过层解映射单元将第一FlexE数据解映射，并从中读取出Zn和ticks值。处理单元TIMING RX根据接收频率F FlexE、Zn和ticks值，恢复出第一业务的业务频率F client，即恢复出第一业务的业务时钟，作为客户链路的发送时钟。
可选地，在FlexE的链路中还可以传输第二业务。可选地，透传业务频率的方法还可以包括：所述第四设备接收第五设备发送的第二业务数据的数据流，所述第二业务数据的 数据流中包括第二S/T比特码块，所述第二S/T比特码块中包括第二业务频率信息Vm，所述第二业务频率信息Vm用于指示所述第五设备在第二统计时长内发送的n比特第二业务数据的数量，所述第二统计时长以所述第五设备的发送频率为基准，其中，m为正整数；所述第四设备根据所述第二业务频率信息Vm，恢复所述第二业务数据对应的时钟。
上述实施例的接入节点和出节点可以组成单跳组网模式的FlexE系统，接入节点产生业务频率信息，出节点根据业务频率信息恢复出业务时钟，实现透传业务频率的功能；接入节点、至少一个中间节点和出节点可以组成多跳级联组网模式的FlexE系统，接入节点产生业务频率信息，中间节点再生业务频率信息，出节点根据业务频率信息恢复出业务时钟，实现透传业务频率的功能。单跳组网模式环境简单，没有中间节点的业务频率信息的重新计算的过程。应理解，组网环境越简单，业务频率信息的传递损伤越少，恢复的业务频率/业务时钟越精确。
上文描述了本申请实施例提供的透传业务频率的方法，下文将描述本申请实施例提供的透传业务频率的设备。
本申请的透传业务频率的设备可以对应于分组承载设备，例如规划加载FlexE的网络协议(Internet Protocol，IP)无线电接入网(Radio Access Network，RAN)设备、分组传送网(Packet Transport Network，PTN)设备等。处于网络的接入节点的设备，例如，盒式设备可以通过接口卡或框式设备可以通过线卡的接口芯片，实施本申请实施例的业务频率信息的产生以及将业务频率信息插入填充码块的功能。处于网络的中间节点的设备，例如，盒式设备可以通过接口卡或框式设备可以通过线卡的接口芯片，实施本申请实施例的业务频率信息再生的功能。处于网络的出节点的设备，例如，盒式设备可以通过接口卡或框式设备可以通过线卡的接口芯片，实施本申请实施例的恢复业务时钟的功能。
图14是本申请一个实施例的透传业务频率的设备1400的示意性框图。该透传业务频率的设备1400为第一设备，如图14所示，透传业务频率的设备1400可以包括：
时钟处理单元1410，用于确定第一业务频率信息Xn，所述第一业务频率信息Xn用于指示所述第一设备在第一统计时长内发送的n比特第一业务数据的数量，所述第一统计时长以所述第一设备的发送频率为基准，其中，n为正整数。
业务处理单元1420，用于将所述时钟处理单元1410确定的所述第一业务频率信息Xn封装到第一S/T比特码块中，将所述第一S/T比特码块插入到所述第一业务数据的数据流中发送给第二设备，其中，S和T为正整数。
可选地，作为一个可选实施例，所述第一S/T比特码块为O码标识的S/T比特码块。
可选地，作为一个可选实施例，所述第一S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长。
可选地，作为一个可选实施例，所述第一统计时长为第一目标数量个发送时钟周期，所述第一统计时长信息包括所述第一目标数量。
可选地，作为一个可选实施例，所述时钟处理单元1410还用于：根据所述第一业务数据的速率确定所述第一统计时长；所述时钟处理单元1420备确定第一业务频率信息Xn，包括：统计在所述第一统计时长内所发送的n比特所述第一业务数据的数量。
可选地，作为一个可选实施例，所述业务处理单元1420还用于：接收第三设备发送的所述第一业务数据的数据流，从所述第一业务数据的数据流的第二S/T比特码块中解析 出第一业务频率信息Yn；所述时钟处理单元1410具体用于：根据所述第一业务频率信息Yn，计算在所述第一统计时长内所发送的n比特所述第一业务数据的数量，得到所述第一业务频率信息Xn。
可选地，作为一个可选实施例，所述第二S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长。
可选地，作为一个可选实施例，所述时钟处理单元1410还用于：确定第二业务频率信息Wm，所述第二业务频率信息Wm用于指示所述第一设备在第二统计时长内发送的m比特第二业务数据的数量，所述第二统计时长以所述第一设备的发送频率为基准，其中，m为正整数；所述业务处理单元1420还用于：将所述第二业务频率信息Wm封装到第三S/T比特码块中，将所述第三S/T比特码块插入到所述第二业务数据的数据流中发送给所述第二设备。
可选地，作为一个可选实施例，所述第一业务频率信息Xn＝A·F client/F FlexE，其中，A为频率系数，F client为所述第一业务数据的业务频率，F FlexE为所述第一设备的发送频率。
应理解，时钟处理单元1410可以对应于图9和图10的时钟处理单元TIMING TX或时钟处理单元TIMING REGENERATE。业务处理单元1420可以对应于图9和图10的业务处理单元、层映射单元、和PHY链路等。
应理解，本申请实施例中的时钟处理单元1410和业务处理单元1420的部分功能可以由处理器或处理器相关电路组件实现，业务处理单元1420的部分功能可以由网络接口或网络接口相关电路组件实现。
如图15所示，本申请实施例还提供一种透传业务频率的设备1500，该透传业务频率的设备1500是第一设备，该透传业务频率的设备1500包括处理器1510，存储器1520与网络接口1530，该存储器1520用于存储指令，该处理器1510与网络接口1530用于执行该存储器1520存储的指令。
应理解，图14所示的透传业务频率的设备1400或图15所示的透传业务频率的设备1500可用于执行上述方法实施例中与终端设备相关的操作或流程，并且透传业务频率的设备1400或透传业务频率的设备1500中的各个模块的操作和/或功能分别为了实现上述方法实施例中的相应流程，为了简洁，在此不再赘述。
图16是本申请一个实施例的透传业务频率的设备1600的示意性框图。该透传业务频率的设备1600为第四设备，如图16所示，透传业务频率的设备1600可以包括：
业务处理单元1610，用于接收第五设备发送的第一业务数据的数据流，所述第一业务数据的数据流中包括第一S/T比特码块，述第一S/T比特码块中包括第一业务频率信息Zn，所述第一业务频率信息Zn用于指示所述第五设备在第一统计时长内发送的n比特第一业务数据的数量，所述第一统计时长以所述第五设备的发送频率为基准，其中，n、S和T为正整数。
时钟处理单元1620，用于根据所述第一业务频率信息Zn，恢复所述第一业务数据对应的时钟。
可选地，作为一个可选实施例，所述第一S/T比特码块为O码标识的S/T比特码块。
可选地，作为一个可选实施例，所述第一S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长，所述时钟处理单元1620具体用于： 根据所述第一业务频率信息Zn和所述第一统计时长信息，恢复所述第一业务数据对应的时钟。
可选地，作为一个可选实施例，所述第一统计时长为第一目标数量个发送时钟周期，所述第一统计时长信息包括所述第一目标数量。
可选地，作为一个可选实施例，所述业务处理单元1610还用于：接收第五设备发送的第二业务数据的数据流，所述第二业务数据的数据流中包括第二S/T比特码块，所述第二S/T比特码块中包括第二业务频率信息Vm，所述第二业务频率信息Vm用于指示所述第五设备在第二统计时长内发送的n比特第二业务数据的数量，所述第二统计时长以所述第五设备的发送频率为基准，其中，m为正整数；所述时钟处理单元1620还用于：根据所述第二业务频率信息Vm，恢复所述第二业务数据对应的时钟。
可选地，作为一个可选实施例，所述第一业务频率信息Zn＝A·F client/F FlexE，其中，A为频率系数，F client为所述第一业务数据的业务频率，F FlexE为所述第五设备的发送频率。
应理解，时钟处理单元1620可以对应于图9和图10的时钟处理单元TIMING RX。业务处理单元1610可以对应于图9和图10的业务处理单元、层解映射单元和PHY链路等。
应理解，本申请实施例中的时钟处理单元1620和业务处理单元1610的部分功能可以由处理器或处理器相关电路组件实现，业务处理单元1610的部分功能可以由网络接口或网络接口相关电路组件实现。
如图17所示，本申请实施例还提供一种透传业务频率的设备1700，该透传业务频率的设备1700是第四设备，该透传业务频率的设备1700包括处理器1710，存储器1720与网络接口1730，该存储器1720用于存储指令，该处理器1710与网络接口1730用于执行该存储器1720存储的指令。
应理解，本申请实施例中提及的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus  RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供一种计算机可读存储介质，其上存储有存储有指令，当所述指令在计算机上运行时，使得所述计算机执行上述方法实施例的方法。具体地，该计算机可以为上述第一设备或第四设备。
本申请实施例还提供一种包括指令的计算机程序产品，其特征在于，当计算机运行所述计算机程序产品的所述指时，所述计算机执行上述方法实施例的方法。具体地，该计算机程序产品可以运行于上述第一设备或第四设备上。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如，固态硬盘(Solid State Disk，SSD))等。
应理解，本文中涉及的第一、第二以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请的范围。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通 过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (32)

  1. 一种透传业务频率的方法，其特征在于，包括：
    第一设备确定第一业务频率信息Xn，所述第一业务频率信息Xn用于指示所述第一设备在第一统计时长内发送的n比特第一业务数据的数量，所述第一统计时长以所述第一设备的发送频率为基准，其中，n为正整数；
    所述第一设备将所述第一业务频率信息Xn封装到第一S/T比特码块中，将所述第一S/T比特码块插入到所述第一业务数据的数据流中发送给第二设备，其中，S和T为正整数。
  2. 根据权利要求1所述的方法，其特征在于，所述第一S/T比特码块为O码标识的S/T比特码块。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长。
  4. 根据权利要求3所述的方法，其特征在于，所述第一统计时长为第一目标数量个发送时钟周期，所述第一统计时长信息包括所述第一目标数量。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备根据所述第一业务数据的速率确定所述第一统计时长；
    所述第一设备确定第一业务频率信息Xn，包括：
    所述第一设备统计在所述第一统计时长内所发送的n比特所述第一业务数据的数量。
  6. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收第三设备发送的所述第一业务数据的数据流，从所述第一业务数据的数据流的第二S/T比特码块中解析出第一业务频率信息Yn；
    所述第一设备确定第一业务频率信息Xn，包括：
    所述第一设备根据所述第一业务频率信息Yn，计算在所述第一统计时长内所发送的n比特所述第一业务数据的数量，得到所述第一业务频率信息Xn。
  7. 根据权利要求6所述的方法，其特征在于，所述第二S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备确定第二业务频率信息Wm，所述第二业务频率信息Wm用于指示所述第一设备在第二统计时长内发送的m比特第二业务数据的数量，所述第二统计时长以所述第一设备的发送频率为基准，其中，m为正整数；
    所述第一设备将所述第二业务频率信息Wm封装到第三S/T比特码块中，将所述第三S/T比特码块插入到所述第二业务数据的数据流中发送给所述第二设备。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述第一业务频率信息Xn＝A·F client/F FlexE，其中，A为频率系数，F client为所述第一业务数据的业务频率，F FlexE为所述第一设备的发送频率。
  10. 一种透传业务频率的方法，其特征在于，包括：
    第四设备接收第五设备发送的第一业务数据的数据流，所述第一业务数据的数据流中 包括第一S/T比特码块，所述第一S/T比特码块中包括第一业务频率信息Zn，所述第一业务频率信息Zn用于指示所述第五设备在第一统计时长内发送的n比特第一业务数据的数量，所述第一统计时长以所述第五设备的发送频率为基准，其中，n、S和T为正整数；
    所述第四设备根据所述第一业务频率信息Zn，恢复所述第一业务数据对应的时钟。
  11. 根据权利要求10所述的方法，其特征在于，所述第一S/T比特码块为O码标识的S/T比特码块。
  12. 根据权利要求10或11所述的方法，其特征在于，所述第一S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长，
    所述第四设备根据所述第一业务频率信息Zn，恢复所述第一业务数据对应的时钟，包括：
    所述第四设备根据所述第一业务频率信息Zn和所述第一统计时长信息，恢复所述第一业务数据对应的时钟。
  13. 根据权利要求12所述的方法，其特征在于，所述第一统计时长为第一目标数量个发送时钟周期，所述第一统计时长信息包括所述第一目标数量。
  14. 根据权利要求10至13中任一项所述的方法，其特征在于，所述方法还包括：
    所述第四设备接收第五设备发送的第二业务数据的数据流，所述第二业务数据的数据流中包括第二S/T比特码块，所述第二S/T比特码块中包括第二业务频率信息Vm，所述第二业务频率信息Vm用于指示所述第五设备在第二统计时长内发送的n比特第二业务数据的数量，所述第二统计时长以所述第五设备的发送频率为基准，其中，m为正整数；
    所述第四设备根据所述第二业务频率信息Vm，恢复所述第二业务数据对应的时钟。
  15. 根据权利要求10至14中任一项所述的方法，其特征在于，所述第一业务频率信息Zn＝A·F client/F FlexE，其中，A为频率系数，F client为所述第一业务数据的业务频率，F FlexE为所述第五设备的发送频率。
  16. 一种透传业务频率的设备，所述设备为第一设备，其特征在于，包括：
    时钟处理单元，用于确定第一业务频率信息Xn，所述第一业务频率信息Xn用于指示所述第一设备在第一统计时长内发送的n比特第一业务数据的数量，所述第一统计时长以所述第一设备的发送频率为基准，其中，n为正整数；
    业务处理单元，用于将所述时钟处理单元确定的所述第一业务频率信息Xn封装到第一S/T比特码块中，将所述第一S/T比特码块插入到所述第一业务数据的数据流中发送给第二设备，其中，S和T为正整数。
  17. 根据权利要求16所述的设备，其特征在于，所述第一S/T比特码块为O码标识的S/T比特码块。
  18. 根据权利要求16或17所述的设备，其特征在于，所述第一S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长。
  19. 根据权利要求18所述的设备，其特征在于，所述第一统计时长为第一目标数量个发送时钟周期，所述第一统计时长信息包括所述第一目标数量。
  20. 根据权利要求16至19中任一项所述的设备，其特征在于，所述时钟处理单元还用于：
    根据所述第一业务数据的速率确定所述第一统计时长；
    所述时钟处理单元备确定第一业务频率信息Xn，包括：
    统计在所述第一统计时长内所发送的n比特所述第一业务数据的数量。
  21. 根据权利要求16至19中任一项所述的设备，其特征在于，所述业务处理单元还用于：
    接收第三设备发送的所述第一业务数据的数据流，从所述第一业务数据的数据流的第二S/T比特码块中解析出第一业务频率信息Yn；
    所述时钟处理单元具体用于：
    根据所述第一业务频率信息Yn，计算在所述第一统计时长内所发送的n比特所述第一业务数据的数量，得到所述第一业务频率信息Xn。
  22. 根据权利要求21所述的设备，其特征在于，所述第二S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长。
  23. 根据权利要求16至22中任一项所述的设备，其特征在于，所述时钟处理单元还用于：
    确定第二业务频率信息Wm，所述第二业务频率信息Wm用于指示所述第一设备在第二统计时长内发送的m比特第二业务数据的数量，所述第二统计时长以所述第一设备的发送频率为基准，其中，m为正整数；
    所述业务处理单元还用于：
    将所述第二业务频率信息Wm封装到第三S/T比特码块中，将所述第三S/T比特码块插入到所述第二业务数据的数据流中发送给所述第二设备。
  24. 根据权利要求16至23中任一项所述的设备，其特征在于，所述第一业务频率信息Xn＝A·F client/F FlexE，其中，A为频率系数，F client为所述第一业务数据的业务频率，F FlexE为所述第一设备的发送频率。
  25. 一种透传业务频率的设备，所述设备为第四设备，其特征在于，包括：
    业务处理单元，用于接收第五设备发送的第一业务数据的数据流，所述第一业务数据的数据流中包括第一S/T比特码块，所述第一S/T比特码块中包括第一业务频率信息Zn，所述第一业务频率信息Zn用于指示所述第五设备在第一统计时长内发送的n比特第一业务数据的数量，所述第一统计时长以所述第五设备的发送频率为基准，其中，n、S和T为正整数；
    时钟处理单元，用于根据所述第一业务频率信息Zn，恢复所述第一业务数据对应的时钟。
  26. 根据权利要求25所述的设备，其特征在于，所述第一S/T比特码块为O码标识的S/T比特码块。
  27. 根据权利要求25或26所述的设备，其特征在于，所述第一S/T比特码块中还封装有第一统计时长信息，所述第一统计时长信息用于指示所述第一统计时长，
    所述时钟处理单元具体用于：
    根据所述第一业务频率信息Zn和所述第一统计时长信息，恢复所述第一业务数据对应的时钟。
  28. 根据权利要求27所述的设备，其特征在于，所述第一统计时长为第一目标数量个发送时钟周期，所述第一统计时长信息包括所述第一目标数量。
  29. 根据权利要求25至28中任一项所述的设备，其特征在于，所述业务处理单元还用于：
    接收第五设备发送的第二业务数据的数据流，所述第二业务数据的数据流中包括第二S/T比特码块，所述第二S/T比特码块中包括第二业务频率信息Vm，所述第二业务频率信息Vm用于指示所述第五设备在第二统计时长内发送的n比特第二业务数据的数量，所述第二统计时长以所述第五设备的发送频率为基准，其中，m为正整数；
    所述时钟处理单元还用于：
    根据所述第二业务频率信息Vm，恢复所述第二业务数据对应的时钟。
  30. 根据权利要求25至29中任一项所述的设备，其特征在于，所述第一业务频率信息Zn＝A·F client/F FlexE，其中，A为频率系数，F client为所述第一业务数据的业务频率，F FlexE为所述第五设备的发送频率。
  31. 一种计算机存储介质，其特征在于，其上存储有指令，当所述指令在计算机上运行时，使得所述计算机执行权利要求1至9中任一项所述的方法。
  32. 一种计算机存储介质，其特征在于，其上存储有指令，当所述指令在计算机上运行时，使得所述计算机执行权利要求10至15中任一项所述的方法。
PCT/CN2018/098143 2017-08-11 2018-08-01 透传业务频率的方法和设备 WO2019029419A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2020529796A JP7019938B2 (ja) 2017-08-11 2018-08-01 サービス周波数をトランスペアレントに伝送する方法およびデバイス
KR1020207007041A KR102383297B1 (ko) 2017-08-11 2018-08-01 서비스 주파수를 투명하게 전송하기 위한 방법 및 디바이스
EP18843757.8A EP3664390A4 (en) 2017-08-11 2018-08-01 METHOD AND DEVICE FOR THE TRANSITION OF SERVICE FREQUENCY
US16/786,507 US11412074B2 (en) 2017-08-11 2020-02-10 Method and device for transparently transmitting service frequency

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710687136.8A CN109391461B (zh) 2017-08-11 2017-08-11 透传业务频率的方法和设备
CN201710687136.8 2017-08-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/786,507 Continuation US11412074B2 (en) 2017-08-11 2020-02-10 Method and device for transparently transmitting service frequency

Publications (1)

Publication Number Publication Date
WO2019029419A1 true WO2019029419A1 (zh) 2019-02-14

Family

ID=65273172

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/098143 WO2019029419A1 (zh) 2017-08-11 2018-08-01 透传业务频率的方法和设备

Country Status (6)

Country Link
US (1) US11412074B2 (zh)
EP (1) EP3664390A4 (zh)
JP (1) JP7019938B2 (zh)
KR (1) KR102383297B1 (zh)
CN (1) CN109391461B (zh)
WO (1) WO2019029419A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109728968B (zh) * 2017-10-31 2022-01-14 华为技术有限公司 获得目标传输路径的方法、相关设备及系统
CN110875796B (zh) * 2018-08-30 2021-02-23 华为技术有限公司 物理层端口通道化的方法和装置
CN109728948B (zh) * 2018-12-26 2022-05-13 苏州盛科通信股份有限公司 一种运营维护管理信息处理方法和装置
CN109951750B (zh) * 2019-03-01 2021-04-20 盛科网络（苏州）有限公司 基于FlexE一层交叉架构的数据处理方法及系统
CN112311510B (zh) * 2019-07-26 2024-04-09 华为技术有限公司 业务数据传输的方法和通信装置
CN112165434B (zh) * 2020-06-30 2021-12-07 中兴通讯股份有限公司 在分组交换系统中透传cbr信号的方法和系统
CN113938245A (zh) * 2020-07-13 2022-01-14 华为技术有限公司 一种速率适配方法及装置
CN114499788A (zh) * 2020-10-26 2022-05-13 南京中兴软件有限责任公司 Cbr信号传输方法、系统及设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170005742A1 (en) * 2015-06-30 2017-01-05 Ciena Corporation Flexible ethernet switching systems and methods
CN106411454A (zh) * 2015-07-30 2017-02-15 华为技术有限公司 用于数据传输的方法、发送机和接收机
CN106803814A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种灵活以太网路径的建立方法、装置及系统

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001197031A (ja) * 2000-01-07 2001-07-19 Nec Corp 加入者サービス信号の多重伝送方法
US7155532B2 (en) * 2002-01-04 2006-12-26 Scientific-Atlanta, Inc. Transmitting streams over asynchronous networks
JP4838677B2 (ja) * 2006-09-20 2011-12-14 富士通株式会社 伝送装置
CN101227450B (zh) * 2007-01-16 2013-04-24 华为技术有限公司 一种开销信息的传输方法、系统及设备
CN101330350B (zh) * 2007-06-21 2011-09-14 华为技术有限公司 适配载荷带宽传输数据的发送方法、接收处理方法及装置
US9425948B2 (en) * 2012-01-26 2016-08-23 Qualcomm Incorporated Techniques for synchronizing a clock of a wired connection when transmitted over a wireless channel
US10129182B2 (en) * 2012-06-29 2018-11-13 Juniper Networks, Inc. Methods and apparatus for providing services in distributed switch
CN105871502B (zh) * 2015-01-22 2020-01-03 华为技术有限公司 一种利用以太网信道传输业务信号的方法及通信设备
EP3065318B1 (en) * 2015-03-06 2020-04-22 Alcatel Lucent Transmission method
US10218823B2 (en) * 2015-06-30 2019-02-26 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
CN106612203A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 一种处理灵活以太网客户端数据流的方法及装置
CN106612220A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 灵活以太网的通道管理方法和装置
CN106788855B (zh) 2015-11-23 2018-12-07 华为技术有限公司 一种灵活以太网业务的光传送网承载方法及装置
JP6950215B2 (ja) * 2017-03-21 2021-10-13 富士通株式会社 通信装置及び信号中継方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170005742A1 (en) * 2015-06-30 2017-01-05 Ciena Corporation Flexible ethernet switching systems and methods
CN106411454A (zh) * 2015-07-30 2017-02-15 华为技术有限公司 用于数据传输的方法、发送机和接收机
CN106803814A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种灵活以太网路径的建立方法、装置及系统

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
JP2020530739A (ja) 2020-10-22
CN109391461A (zh) 2019-02-26
US11412074B2 (en) 2022-08-09
KR102383297B1 (ko) 2022-04-08
KR20200035142A (ko) 2020-04-01
EP3664390A1 (en) 2020-06-10
CN109391461B (zh) 2021-08-13
EP3664390A4 (en) 2020-07-29
JP7019938B2 (ja) 2022-02-16
US20200195760A1 (en) 2020-06-18

Similar Documents

Publication Publication Date Title
US11412074B2 (en) Method and device for transparently transmitting service frequency
US11252098B2 (en) Data transmission method, transmitter, and receiver
US11165698B2 (en) Method for transmitting service signal by using ethernet channel and communications device
CN109600188B (zh) 数据传输方法、传输设备和传输系统
WO2018090856A1 (zh) 用于建立灵活以太网群组的方法和设备
US11082199B2 (en) Data transmission method in optical network and optical network device
US7583664B2 (en) Techniques for transmitting and receiving traffic over advanced switching compatible switch fabrics
US8416770B2 (en) Universal service transport transitional encoding
EP3832914A1 (en) Oam message transmission method, sending device, receiving device, and readable storage device
EP3909209B1 (en) Ethernet signal format using 256b/257b block encoding
US20200288468A1 (en) Data transmission method and device
US8718069B2 (en) Transmission apparatus and signal transmission method for mapping packets in frames of synchronous network
US20060067314A1 (en) Overhead processing and generation techniques
US20230299880A1 (en) Code block identification method and apparatus
WO2023035776A1 (zh) 一种通信方法、相关装置以及存储介质
WO2023109424A1 (zh) 一种数据传输的方法以及相关装置
WO2020029892A1 (zh) 接收码块流的方法、发送码块流的方法和通信装置
WO2024032269A1 (zh) 通信方法、相关装置及计算机可读存储介质
US20230396353A1 (en) Communication Method and Device, and Chip System
WO2024051586A1 (zh) 一种光传送网中的数据帧的处理方法、装置和系统
WO2019023824A1 (zh) 一种比特块流处理、速率匹配、交换的方法和装置
WO2019042121A1 (zh) 一种交换方法和装置

Legal Events

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

Ref document number: 18843757

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020529796

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207007041

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018843757

Country of ref document: EP

Effective date: 20200305