WO2022194290A1 - 光网络中以太数据处理的方法、装置以及系统 - Google Patents

光网络中以太数据处理的方法、装置以及系统 Download PDF

Info

Publication number
WO2022194290A1
WO2022194290A1 PCT/CN2022/081794 CN2022081794W WO2022194290A1 WO 2022194290 A1 WO2022194290 A1 WO 2022194290A1 CN 2022081794 W CN2022081794 W CN 2022081794W WO 2022194290 A1 WO2022194290 A1 WO 2022194290A1
Authority
WO
WIPO (PCT)
Prior art keywords
optical network
network device
frame
data
channel information
Prior art date
Application number
PCT/CN2022/081794
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 华为技术有限公司
Publication of WO2022194290A1 publication Critical patent/WO2022194290A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • 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
    • 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/1664—Optical Transport Network [OTN] carrying hybrid payloads, e.g. different types of packets or carrying frames and packets in the paylaod

Definitions

  • the present disclosure relates to the field of optical communication, and in particular, to a method, an apparatus and a system for processing Ethernet data in an optical network.
  • Flexible Ethernet (FlexE) interface technology for example, FlexE IA 1.0/2.0/2.1.
  • FlexE Flexible Ethernet
  • the term “FlexE” used in this document refers to an interface technology that implements service isolation on the bearer network, decoupling of service bandwidth requirements from physical interface bandwidth, and network slicing.
  • n 100G PHYs, or m 200G PHYs, or m 400G PHYs, or m 50G PHYs multiple FlexE services at different rates can be transmitted, such as 10G, n*25G, 40G and other FlexE services, which are mainly used in Data center equipment interconnection, etc.
  • OTN optical transport network
  • the standards related to OTN carrying FlexE data are formulated by the International Telecommunication Union-Telecommunication Standardization Sector (ITU-T).
  • the segment layer of the Metro Transport Network being defined in ITU-T reuses the FlexE interface technology.
  • MTN is mainly used for 5G bearer, and the entire network is required to support high-precision clocks.
  • the MTN/FlexE passes through the OTN. Therefore, in the case of MTN/FlexE passing through OTN, the OTN also needs to support the transparent transmission of the FlexE high-precision clock carried by the OTN, and also needs to support the data communication channel (Data Communication Network, DCN) data transparent transmission.
  • the DCN is located in overhead code blocks #4, #5, #6, #7, and #8 of the FlexE interface.
  • the DCN data mainly includes information such as management and control of the MTN/FlexE interface.
  • Example embodiments of the present disclosure provide solutions for Ethernet data processing in optical networks.
  • a communication method is provided.
  • the optical network device obtains the first data frame.
  • the optical network device maps the service data in the first data frame to the first part of the second data frame.
  • the optical network device also maps the management channel information in the first data frame to the second part of the second data frame. In this way, separate processing of service data and management channel information is achieved, thereby helping to meet the requirements for transparent transmission of management channel information and high-precision clocks.
  • the first data frame is a first flexible Ethernet FlexE interface frame
  • the second data frame is a second FlexE interface frame
  • acquiring the first data frame by the optical network device includes: the optical network device receives the flexible Optical data unit ODUflex frame.
  • the optical network device demaps the ODUflex frame to obtain the first FlexE interface frame. In this way, the entire OTN network can be prevented from participating in the processing of data.
  • the optical network device extracts the first synchronization information and obtains the clock from the synchronization information channel overhead of the FlexE interface frame.
  • the optical network device generates the second FlexE interface frame based on the clock.
  • the optical network device generates the second synchronization information based on the first synchronization information and inserts the second FlexE interface frame. In this way, transparent transmission of the high-precision clock is achieved.
  • the optical network device maps the second FlexE interface frame to a flexible optical data unit ODUflex frame.
  • Optical network equipment sends ODUflex frames. In this way, the separate processing of the service data and the management channel information of the data frame at the ingress device of the OTN network is achieved.
  • the first data frame is a flexible Ethernet FlexE interface frame
  • the second data frame is a flexible optical payload unit OPUflex frame.
  • the FlexE interface frame is transmitted by binding multiple physical links, and the second data frame includes multiple OPUflex frames.
  • the optical network device will extract management communication channel information from each of the plurality of physical links.
  • the optical network device maps the management communication channel information extracted from each physical link to corresponding OPUflex frames among the plurality of OPUflex frames, respectively.
  • a FlexE interface frame is transmitted over a bound first physical link) and a second physical link
  • the second data frame includes a first OPUflex frame and a second OPUflex frame.
  • the optical network device mapping the management channel information in the first data frame to the second part of the data frame includes: the optical network device extracts the first management channel information from the first physical link.
  • the optical network device performs rate adaptation on the first management channel information; the optical network device maps the rate-adapted first management channel information to the first OPUflex frame.
  • the optical network device extracts the second management channel information from the second physical link.
  • the optical network device performs rate adaptation on the second management channel information.
  • the optical network device maps the rate-adapted second management channel information to the second OPUflex frame. In this way, increasing the complexity of the data frame is avoided.
  • the FlexE interface frame is transmitted by binding multiple physical links, and the second data frame includes an OPUflex frame.
  • the optical network device will extract management communication channel information from each of the plurality of physical links.
  • the optical network equipment maps the management communication channel information extracted from each physical link to the OPUflex frame.
  • the FlexE interface frame passes through the bonded first physical link and the second PHY physical link, and the second part includes the first OPUflex frame, wherein the optical network device converts the management in the first data frame
  • the mapping of the channel information to the second portion of the data frame includes the optical network device extracting the first management channel information from the first physical link.
  • the optical network device extracts the second management channel information from the second physical link.
  • the optical network device performs rate adaptation on the first management channel information and the first management channel information.
  • the optical network device maps the rate-adapted first management channel information and the rate-adapted second management channel information to the first OPUflex frame. In this way, the complexity of detecting data frames is avoided.
  • the optical network device extracts the first synchronization information and obtains the clock from the synchronization information channel overhead of the FlexE interface frame.
  • the optical network device generates non-ODUflex channel information based on the clock.
  • the optical network device generates the second synchronization information based on the first synchronization information and inserts the second synchronization information into the non-ODUflex channel for transmission. In this way, transparent transmission of the high-precision clock is achieved.
  • a communication method includes: the optical network device demaps service data from the first part of the first data frame; the optical network device extracts management channel information from the second part of the first data frame; the optical network device generates the first data based on the clock and the service data. two data frames; and the optical network device maps the management channel information to the second data frames.
  • the first data frame is a flexible optical payload unit OPUflex frame
  • the second data frame is a flexible Ethernet Flex interface frame.
  • the first data frame includes a first flexible optical payload unit OPUflex frame and a second OPUflex frame
  • the second data frame is transmitted over the bonded first physical link and the second physical link
  • the optical Extracting the management channel information from the second part of the first data frame by the network device includes: the optical network device extracts the first management channel information for the first physical link from the first OPUflex frame; and the optical network device extracts the first management channel information for the first physical link from the second OPUflex frame; The second management channel information for the second physical link is extracted from the frame. In this way, increasing the complexity of the data frame is avoided.
  • the first data frame includes a first flexible optical payload unit OPUflex frame
  • the second data frame is transmitted over the bonded first physical link and the second physical link
  • the optical network device from the first physical link Extracting the management channel information from the second part of the data frame includes: the optical network device extracts the first management channel information for the first physical link from the first OPUflex frame; and the optical network device extracts the first management channel information from the first OPUflex frame for the first physical link Second management channel information of the second physical link.
  • the method further includes: the optical network device receiving clock information on a non-ODUflex channel; and the optical network device generating another non-ODUflex channel based on the clock information. In this way, transparent transmission of the high-precision clock is achieved.
  • an apparatus for data processing comprises means for performing the method according to any one of the possible implementations of the first aspect or the second aspect above.
  • the present disclosure provides a chip.
  • the chip is configured to perform operations according to the method in any of the possible implementations of the first aspect or the second aspect above.
  • an apparatus for data processing includes: a processor for executing the method according to any one of the possible implementations of the first aspect or the second aspect; and an interface for interacting with the processor to receive and send data sent and received by the processor .
  • an optical network device includes: means for executing the method according to any one of the possible implementations of the first aspect or the second aspect; and an optical transceiver for connecting with an interface, so as to interact with the interface to implement the method by the interface. The transmission and reception of data frames processed by the device.
  • a computer program product is provided.
  • the computer program product is tangibly stored on a computer-readable medium and includes computer-executable instructions that, when executed, cause an apparatus to implement any of the possible implementations according to the first to second aspects above method operation.
  • FIG. 1 shows a schematic block diagram of a communication environment to which embodiments of the present disclosure are applicable
  • FIG. 2 shows a schematic diagram of a possible network device hardware structure
  • FIG. 3 shows a schematic flowchart of a possible data processing method
  • Fig. 4 shows a possible schematic diagram of Ethernet data and overhead processing
  • FIG. 5 shows an interactive signaling diagram of a communication process according to some embodiments of the present disclosure
  • FIG. 6 shows a data frame structure diagram according to some embodiments of the present disclosure
  • FIG. 7 shows an interactive signaling diagram of a communication process according to other embodiments of the present disclosure.
  • Figure 8 shows a flow diagram according to some embodiments of the present disclosure
  • FIG. 9 shows an interactive signaling diagram of a communication process according to further embodiments of the present disclosure.
  • FIG. 10 shows another possible schematic diagram of Ethernet data and overhead processing
  • FIG. 11A and 11B show schematic diagrams of rate matching, respectively.
  • 12A and 12B respectively show schematic diagrams of management channel information mapping
  • Figure 13 shows a schematic block diagram of a communication device according to some embodiments of the present disclosure
  • FIG. 14 shows a schematic block diagram of a communication apparatus according to some other embodiments of the present disclosure.
  • FIG. 15 shows a simplified block diagram of an example device suitable for implementing embodiments of the present disclosure.
  • the term “comprising” and the like should be understood as open-ended inclusion, ie, “including but not limited to”.
  • the term “based on” should be understood as “based at least in part on”.
  • the terms “one embodiment” or “the embodiment” should be understood to mean “at least one embodiment”.
  • the terms “first”, “second”, etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.
  • the embodiments of the present application are applicable to an optical network, such as an optical transport network (Optical transport Network, OTN for short).
  • An optical network is usually composed of multiple devices connected by optical fibers, and can be composed of different topology types such as line, ring, and mesh according to specific needs.
  • the communication system 100 shown in FIG. 1 includes an optical network 101 and communication nodes (eg, communication node 130 and communication node 140).
  • the optical network 101 is a network composed of optical network devices 110 (eg, optical network device 110-1, optical network device 110-2, and optical network device 110-N, where N is any positive integer). It will be appreciated that the optical network 101 may include any number of optical network devices.
  • 103 indicates an optical fiber
  • 104 indicates a customer service interface, which is used to realize the transmission of customer service data.
  • a network may have multiple customer service interfaces 104.
  • the client service interface is also sometimes referred to as the User Network Interface (UNI).
  • UNI User Network Interface
  • optical network equipment may have different functions.
  • optical network devices are classified into optical layer devices, electrical layer devices, and optoelectronic hybrid devices.
  • Optical layer devices refer to devices capable of processing optical layer signals, such as optical amplifiers (Optical Amplifier, OA), optical add/drop multiplexers (Optical Add/Drop Multiplexer, OADM).
  • An OA can also be called an Optical Line Amplifier (OLA), which is mainly used to amplify an optical signal to support longer distance transmission on the premise of ensuring the specific performance of the optical signal.
  • the electrical layer device refers to a device capable of processing electrical layer signals, for example, a device capable of processing Optical Data Unit (ODU) signals.
  • An optoelectronic hybrid device refers to a device capable of processing both optical layer signals and electrical layer signals. It should be noted that, according to specific integration needs, the optical network device can integrate a variety of devices with different functions. This application is applicable to optical network equipment of different forms and integration levels. Unless otherwise specified, the equipment that implements the technology disclosed in this application includes at least the processing capability of electrical layer signals.
  • FIG. 2 shows a schematic diagram of the hardware structure of an optical network device 110 .
  • the device 100 includes a power supply 201, a fan 202, an auxiliary board 203, and may also include a tributary board 204, a circuit board 205, a cross board 206, an optical layer processing board (not shown in the figure), programmable The service board 207 and the system control and communication board 208.
  • the type and number of boards specifically included in a device 110 may be different.
  • a network device that is a core node may not have tributary board 204 .
  • a network device that is an edge node may have multiple tributary boards 204 .
  • the power supply 201 is used to supply power to the device, and may include a main power supply and a backup power supply.
  • Fan 202 is used to dissipate heat from the device.
  • the auxiliary board 203 is used to provide auxiliary functions such as external alarm or access to an external clock.
  • the tributary board 204, the cross board 206, the line board 205 and the programmable service board 207 are mainly used for processing electrical layer signals of the optical network (eg, ODU frames in OTN).
  • the tributary board 204 is used to realize the reception and transmission of various customer services, such as Synchronous Digital Hierarchy (SDH) services, packet services, Ethernet services, and fronthaul services.
  • SDH Synchronous Digital Hierarchy
  • the tributary board 204 can be divided into client-side optical modules and processors.
  • the client-side optical module may be an optical transceiver for receiving and/or transmitting client signals.
  • the processor is used to implement mapping and demapping processing of client signals to ODU frames.
  • the cross-connect board 206 is used to realize the exchange of ODU frames, and complete the exchange of one or more types of ODU signals.
  • the line board 205 mainly implements the processing of ODU frames on the line side.
  • the circuit board 205 can be divided into a line-side optical module and a processor.
  • the line-side optical module may be a line-side optical transceiver for receiving and/or sending ODU signals.
  • the processor is used to implement multiplexing and demultiplexing, or mapping and de-mapping processing of ODU frames on the line side.
  • the programmable service board 207 is used to implement the data processing method disclosed in this application.
  • the system control and communication board 208 is used to implement system control and communication. Specifically, information can be collected from different boards through the backplane, or control instructions can be sent to the corresponding board. It should be noted that, unless otherwise specified, there may be one or more specific components (eg, processors), which are not limited in this application. It should also be noted that the embodiments of the present application do not impose any restrictions on the types of boards included in the device, and the specific functional design and quantity of the boards.
  • the equipment mentioned later includes at least a programmable service board 207 .
  • the programmable service board 207 can also be integrated with other boards into a single board. This application does not make any restrictions on the names of boards that specifically implement the data processing technology disclosed in this application.
  • FlexE defined by the standard has three transmission modes on OTN: FlexE non-aware mode, FlexE aware mode and FlexE termination mode.
  • FlexE non-aware mode the optical network device directly transparently transmits the FlexE physical link (PHY) signal.
  • FlexE awareness mode the optical network device parses the FlexE shim layer, deletes the invalid FlexE time slot, and transparently transmits the remaining part.
  • the termination mode the optical network equipment terminates the FlexE overhead, extracts different FlexE client services, and performs mapping and transmission based on the FlexE client.
  • none of these three modes can meet the requirements of transparent transmission of management channel information and FlexE high-precision clock at the same time.
  • both FlexE non-aware mode and FlexE aware mode belong to FlexE data bit transparent transmission (that is, data plane clock transparent transmission, which naturally supports data communication network (DCN) transparent transmission), and the FlexE in-band high-precision clock transparent transmission is achieved in
  • the clock source switching problem (from data plane clock switching to hop-by-hop regeneration of high-precision clocks) is also involved at the OTN exit, which requires rate adaptation.
  • FlexE-agnostic and FlexE-aware modes cannot be supported on the data plane.
  • optical network equipment can achieve high-precision clock transparent transmission in the OTN network by extracting packet information (for example, Precision Time Synchronization Protocol (PTP) and/or Synchronization State Information (SSM)) hop-by-hop termination regeneration.
  • PTP Precision Time Synchronization Protocol
  • SSM Synchronization State Information
  • the optical network device separately processes the service data and manages the channel information.
  • the optical network equipment maps service data and management channel information to different parts of the data frame respectively. In this way, the requirements of management channel information and high-precision clock transparent transmission can be met at the same time. It can be understood that the embodiments of the present disclosure can be used in any suitable data processing technology in an optical network.
  • Example embodiments of the present disclosure will be discussed in detail below with reference to the accompanying drawings. For ease of discussion, the flow of data processing and signaling interaction between communication entities according to an example embodiment of the present disclosure will be described with reference to the example communication environment of FIG. 1 . It should be understood that example embodiments of the present disclosure may be similarly applied in other communication environments.
  • FIG. 3 is a schematic diagram of the flow of an exemplary data processing method 300 .
  • method 300 may be implemented at an ingress-side optical network device, eg, optical network device 110-1.
  • method 300 may be implemented at an optical network device on the egress side, eg, optical network device 110-2.
  • FIG. 4 shows an exemplary frame structure diagram. It can be understood that the frame structure shown in FIG. 4 is only for the purpose of illustration and not limitation, and the frame structure may include other parts not shown in FIG. 4 . In addition, as shown in FIG. 4 , any two parts in the frame structure may be directly adjacent parts, or there may be other parts therebetween.
  • FIG. 3 will now be described in conjunction with FIG. 4 .
  • the method 300 includes: (1) acquiring a data frame; (2) processing service data in the data frame; and (3) processing overhead in the data frame.
  • the method 300 includes:
  • the optical network device obtains a first data frame 410 in the format of a flexible Ethernet FlexE interface frame.
  • the optical network device 110 - 1 may receive the first data frame 410 from the communication node 130 .
  • optical network device 110-2 may receive flexible optical data unit ODUflex frames from optical network device 110-1. In this case, the optical network device 110 - 2 may demap the ODUflex frame to obtain the first data frame 410 .
  • the optical network device maps the traffic data 412 in the first data frame 410 to the first portion 422 in the second data frame 420 .
  • the format of the second data frame 420 may be a FlexE interface frame.
  • the format of the second data frame 420 may be an OTN frame.
  • the first part 422 is the payload area of the flexible optical payload unit OPUflex frame.
  • the optical network device maps the management channel information 411 in the first data frame 410 to the second portion 421 in the second data frame 420 .
  • the format of the second data frame 420 may be a FlexE interface frame.
  • the format of the second data frame 420 may be an OTN frame.
  • the second portion 422 may be an OPUflex frame.
  • the second portion 422 may be a payload area of an OPUflex frame.
  • the second portion 422 may be an overhead area of an OPUflex frame.
  • the optical network device extracts the first synchronization information from the synchronization information channel overhead 413 of the first data frame 410 and obtains the clock.
  • the clock may be a high precision clock.
  • the term "high-precision clock” refers to a clock with an accuracy error smaller than a predetermined error, or a clock with an accuracy requirement greater than a predetermined accuracy.
  • the optical network device also generates second synchronization information based on the extracted first synchronization information.
  • the optical network device generates the second data frame 420 based on the acquired clock, and the format of the second data frame 420 may be a FlexE interface frame. In this embodiment, the optical network device maps the generated new synchronization information into the second data frame 420 .
  • the optical network device may generate non-ODUflex channel information based on the acquired high precision clock.
  • the optical network device maps the generated new synchronization information into the non-ODUflex channel information for transmission.
  • the newly generated synchronization information can be transmitted through an Optical Supervisory Channel (OSC).
  • OSC Optical Supervisory Channel
  • the inserting method may include, for example, direct inserting, inserting after performing mathematical operations, or inserting after buffering. In this way, unnecessary regeneration of synchronization information is avoided.
  • FIG. 5 shows a signaling diagram of the interaction 500 between various devices when the method 300 is implemented on the device (eg, the optical network device 110-2) on the OTN egress side.
  • the communication node 130 sends 5002 the first FlexE interface frame to the optical network device 110-1.
  • the first FlexE interface frame includes service data.
  • the first FlexE interface frame includes one or more FlexE service data streams.
  • the first FlexE interface frame 600 includes a FlexE client (Client) service data stream 6010 (eg, data part 6010-1, data part 6010-2, data part 6010-3, and data part 6010-4) and FlexE Client service data flow 6020 (eg, data part 6020-1, data part 6020-2, data part 6020-3, and data part 6020-4).
  • the first FlexE interface frame 600 also includes an overhead portion 610 .
  • the overhead portion 610 includes management channel information, eg, DCN information.
  • the overhead portion 610 may further include one or more of a FlexE group ID, an instance number of the FlexE interface frame, or a time slot distribution pattern.
  • the optical network device 110-1 maps 5005 the first FlexE interface frame to an ODUflex frame.
  • the optical network device 110-1 may map the first FlexE interface frame to the ODUflex frame using the awareness mode. For example, the optical network device 110-1 may directly transparently transmit the FlexE PHY of the first FlexE interface frame.
  • the optical network device 110-1 may map the first FlexE interface frame to the ODUflex frame using the non-aware mode. For example, the optical network device 110-1 may parse the FlexE shim layer of the first FlexE interface frame and delete invalid time slots. Then, the optical network device 110-1 can transparently transmit the remaining part.
  • the optical network device 110-1 sends 5010 the ODUflex frame to the optical network device 110-2.
  • the optical network device 110-2 is located at the egress side of the OTN network. In this way, the participation of the entire OTN network in data processing can be avoided, and the probability of errors in the data processing process can be reduced.
  • the optical network device 110 - 2 demaps 5015 the received ODUflex frame, thereby obtaining the first FlexE interface frame 600 .
  • the way of demapping here depends on the way of mapping at 5005 .
  • the optical network device 110-2 may perform overhead termination processing on the first FlexE interface frame 600.
  • the optical network device 110-2 acquires 5020 the service data stream from the first FlexE interface frame 600.
  • the optical network device 110-2 extracts 5025 the management channel information from the first FlexE interface frame 600.
  • the optical network device 110-2 may directly extract the DCN information (eg, 66b code block stream) from the overhead portion 610.
  • the optical network device 110-2 extracts 5030 synchronization information from the first FlexE interface frame 600, and generates 5035 new synchronization information based on the extracted synchronization information.
  • the optical network device 110-2 may extract the PTP and/or SSM message information from the overhead portion 610, and generate new PTP and/or SSM message information.
  • the optical network device 110-2 may also obtain a high-precision clock from the overhead part 610, and generate 5040 a second FlexE interface frame based on the high-precision clock.
  • the optical network device 110-2 maps 5045 the service data frame to the second FlexE interface frame.
  • the optical network device 110-2 may also add the overhead of the second FlexE interface frame.
  • the overhead may include one or more of a FlexE group ID, an instance number of the FlexE interface frame, or a time slot distribution pattern.
  • the optical network device 110-2 may perform rate adaptation 5050 on the extracted management channel information.
  • the optical network device 110-2 may utilize free 66b code blocks for rate adaptation. For example, the optical network device 110-2 inserts a free 66b code block between the start (S) code block and the end (T) code block, or inserts one or more free 66b code blocks between the S code block and the T code block delete. Such an adaptation method has good compatibility.
  • the optical network device 110-2 inserts 5055 the adapted management channel information into the second FlexE interface frame.
  • the optical network device 110-2 also inserts 5060 the generated new synchronization information into the second FlexE interface frame. It should be understood that the order of occurrence of steps 5015-5060 may be different from the order shown in FIG. 5 .
  • the optical network device 110-2 sends 5065 the second FlexE interface frame to the communication node 150. In this way, transparent transmission of management channel information and high-precision clocks is achieved, and good compatibility is achieved.
  • FIG. 7 shows a signaling diagram of interaction 700 between various devices when method 300 is implemented on a device (eg, optical network device 110-1) on the ingress side of the OTN. It should be understood that the same or similar steps in FIG. 7 as in FIG. 5 are identified with the same reference numerals.
  • the communication node 130 sends 5002 the first FlexE interface frame to the optical network device 110-1.
  • the information included in the first FlexE interface frame reference may be made to the description for FIG. 5 , and details are not repeated here.
  • the optical network device 110-1 may perform overhead termination processing on the first FlexE interface frame 600.
  • the optical network device 110-1 acquires 5020 the service data flow from the first FlexE interface frame.
  • the optical network device 110-1 extracts 5025 the management channel information from the first FlexE interface frame.
  • the optical network device 110-1 may directly extract the DCN information (eg, 66b code block stream) from the overhead portion of the first FlexE interface frame.
  • the optical network device 110-1 extracts 5030 the first synchronization information from the first FlexE interface frame, and generates 5035 the second synchronization information based on the extracted synchronization information.
  • the optical network device 110-1 may extract PTP and/or SSM message information from the overhead part, and generate new PTP and/or SSM message information.
  • the optical network device 110-1 may also obtain a clock from the overhead part, and generate 5040 a second FlexE interface frame based on the clock.
  • the optical network device 110-1 maps 5045 the service data frame to the second FlexE interface frame.
  • the optical network device 110-1 may also add the overhead of the second FlexE interface frame.
  • the overhead may include one or more of a FlexE group ID, an instance number of the FlexE interface frame, or a time slot distribution pattern.
  • the optical network device 110-1 may perform rate adaptation 5050 on the extracted management channel information.
  • the optical network device 110-2 may utilize free 66b code blocks for rate adaptation.
  • rate adaptation process reference may be made to the description for FIG. 5 , which is not repeated here.
  • the optical network device 110-1 inserts 5055 the adapted management channel information into the second FlexE interface frame.
  • the optical network device 110-1 also inserts 5060 the generated second synchronization information into the second FlexE interface frame.
  • the optical network device 110-1 maps 7065 the second FlexE interface frame into the ODUflex frame.
  • mapping manner of mapping the second FlexE interface frame to the ODUflex frame reference may be made to the description of the mapping manner from the first FlexE interface frame to the ODUflex frame in FIG. 5 , which is not repeated here. It can be understood that the order of occurrence of the above-mentioned steps may be different from the order shown in FIG. 7 .
  • Optical network device 110-1 sends 7070 the ODUflex frame to optical network device 110-2.
  • the optical network device 110-2 demaps 7075 the received ODUflex frame to obtain a second FlexE interface frame.
  • the way of demapping here depends on the way of mapping at 7065. In this way, transparent transmission of management channel information and high-precision clocks is achieved, and good compatibility is achieved.
  • the optical network device 110 - 2 sends 7080 the second FlexE interface frame to the communication node 140 .
  • FIG. 8 is a schematic diagram of the flow of another data processing method 800 in an example.
  • Method 800 may be implemented at an optical network device on the egress side, eg, optical network device 110-2. It is to be understood that the following description of method 800 is only a general description of the embodiments.
  • the optical network device 110-2 demaps the traffic data from the first portion of the first data frame.
  • the format of the first data frame is an OTN frame
  • the first part is an OPUflex payload area.
  • the optical network device 110-2 may demap one or more FlexE service data flows from the OPUflex payload area.
  • the optical network device 110-2 de-extracts management channel information from the second portion of the first data frame.
  • the second part is an OPUflex frame.
  • the optical network device 110-2 may extract the management channel information from the overhead portion of the OPUflex frame.
  • the optical network device 110-2 may extract the management channel information from the payload portion of the OPUflex frame.
  • the optical network device 110-2 may directly extract the DCN information (eg, 66b block stream).
  • the optical network device 110-2 generates a second data frame based on the high precision clock and traffic data.
  • the first data frame is a Flex interface frame.
  • the optical network device 110-2 receives high precision clock information on the non-ODUflex channel and generates a FlexE interface based on the high precision clock information.
  • the optical network device 110-2 adds the management channel information to the second data frame.
  • the optical network device 110-2 may add management channel information to the overhead portion of the second data frame.
  • FIG. 9 shows a signaling diagram of interaction 900 between various devices when the device on the ingress side of the OTN implements the method 300 and the device on the egress side implements the method 800 .
  • the communication node 130 sends 5002 the first FlexE interface frame to the optical network device 110-1.
  • the first FlexE interface frame includes service data.
  • the first FlexE interface frame includes one or more FlexE service data streams.
  • the first FlexE interface frame 111 includes the FlexE Client service data flow 1010 (for example, the data part 1010-1, the data part 1010-2, the data part 1010-3 and the data part 1010-4) and the FlexE Client service Data stream 1020 (eg, data portion 1020-1, data portion 1020-2, data portion 1020-3, and data portion 1020-4).
  • the first FlexE interface frame 1000 also includes an overhead portion 1000 .
  • the overhead portion 1000 includes management channel information, eg, DCN information.
  • the overhead portion 1000 may also include one or more of a FlexE group ID, an instance number of the FlexE interface frame, or a time slot distribution pattern.
  • the optical network device 110-1 acquires 5020 service data from the first FlexE interface frame.
  • the optical network device 110-1 maps 9025 the obtained service data to the first part of the second data frame.
  • the optical network device 110 - 1 maps the service data stream 1010 to the payload portion 1030 - 1 of the OPUflex frame of the second data frame 112 .
  • the optical network device 110-1 maps the traffic data stream 1020 to the payload portion 1030-2 of the OPUflex frame of the same data data frame.
  • the optical network device 110-1 maps the traffic data stream 1020 to a payload portion (not shown) of an OPUflex frame of another data data frame.
  • the optical network device 110-1 extracts 5025 the management channel information from the first FlexE interface frame.
  • the optical network device 110-1 extracts the management channel information from the overhead portion 1000 of the first FlexE interface frame 111.
  • the optical network device 110-1 may extract DCN information from the 7th code block and the 8th code block of the overhead part 1000, and sequentially form the 66b code block of the DCN.
  • the optical network device 110 - 1 may extract the DCN information from the 4th code block, the 5th code block, the 6th code block, the 7th code block or the 8th code block of the overhead part 1000 .
  • Embodiments of the present disclosure are not limited in this regard.
  • the optical network device 110-1 performs rate adaptation 9035 on the management channel information.
  • the optical network device 110-2 may utilize free 66b code blocks for rate adaptation.
  • the optical network device 110-1 inserts idle 66b code blocks 1113-1 and 1113-2 between the S code block 1111 and the T code block 1112. It will be appreciated that any suitable number of idle blocks may be inserted by the optical network device 110-1.
  • the optical network device 110-1 may delete one or more free 66b code blocks between the S code block and the T code block. Such an adaptation method has good compatibility.
  • the optical network device 110-1 may use a special 66b code block for rate adaptation.
  • the optical network device 110-1 places a special 66b code block 1114 between any two code blocks. It will be appreciated that any suitable number of idle blocks may be inserted by the optical network device 110-1.
  • Such an adaptation method has good compatibility, is simple, and is easy to implement. It can be understood that the rate adaptation manners shown in FIG. 11A and FIG. 11B are only examples and are not restrictive.
  • the optical network device 110-1 maps 9040 the rate-adapted management channel information to the second part of the second data frame.
  • the second part may be the payload part of the OPUflex frame.
  • the second part may be the overhead part of the OPUflex frame.
  • the optical network device 110-1 may map the management channel information to the payload area 1030-1 of the OPUflex frame.
  • the optical network device 110-1 may map the management channel information to the overhead portion 1040 of the OPUflex frame.
  • management channel information may be mapped to J1 to J2. It will be appreciated that the mapped management channel information may occupy any suitable number of overhead bytes and any suitable number of overhead bytes.
  • the first data frame may be transmitted over a bonded multiplex PHY.
  • the first data frame may be transmitted through FlexE PHY 1210-1, FlexE PHY 1210-2, ..., FlexE PHY 1210-N, where N is any suitable positive integer.
  • Each FlexE PHY contains corresponding management channel information.
  • the optical network device 110-1 may extract the first management channel information 1220-1 from the first FlexE PHY 1210-1, and map the first management channel information 1220-1 to the first OPUflex frame 1230- 1.
  • the optical network device 110-1 may extract the second management channel information 1220-2 from the second FlexE PHY 1210-2, and map the second management channel information 1220-2 to the second OPUflex frame 1230-2.
  • the optical network device 110-1 may extract the Nth management channel information 1220-N from the Nth FlexE PHY 1210-N, and map the Nth management channel information 1220-N to the Nth OPUflex frame 1230-N.
  • the optical network device 110-1 may extract the first management channel information 1220-1 from the first FlexE PHY 1210-1 and extract the second management channel information 1220 from the second FlexE PHY 1210-2 -2, extract the Nth management channel information 1220-N from the Nth FlexE PHY 1210-N.
  • the optical network device 110-1 may map the management channel information 1220-1, 1220-2, . . . , 1220-N to the first OPUflex frame 1230-1.
  • the optical network device 110-1 extracts 5030 the first synchronization information. As shown in Figure 10, the optical network device 110-1 can extract synchronization information from the overhead 1000. For example, the optical network device 110-1 may extract the PTP and/or SSM from the 6th code block of the overhead. The optical network device 110-1 generates 5035 the second synchronization information. The optical network device 110-1 may also acquire a clock and generate non-ODUflex channel information based on the clock. The optical network device 110-1 inserts the generated second synchronization information into the non-ODUflex channel information for transmission 9055.
  • the optical network device 110-1 sends 9060 the second data frame.
  • the second data frame includes service data and management channel information of the first data frame. It can be understood that the order of occurrence of the above steps may be different from the order shown in FIG. 9 . Similarly, the order of occurrence of steps 9055 and 9060 may also be different from the order shown in FIG. 9 .
  • the optical network device 110-2 obtains 9065 service data. As shown in FIG. 10 , the optical network device 110 - 2 may extract the service data stream 1010 from the payload portion 1030 - 1 of the OPUflex frame of the second data frame 112 . In some embodiments, the optical network device 110-2 may demap the service data stream 1020 from the payload portion 1030-2 of the OPUflex frame of the same data data frame. In other embodiments, the optical network device 110-2 may demap the service data stream 1020 from a payload portion (not shown) of an OPUflex frame of another data data frame.
  • the optical network device 110-2 extracts 9070 the management channel information. As shown in FIG. 10 , the optical network device 110 - 2 may extract the management channel information from the payload portion 1030 - 1 of the OPUflex frame of the second data frame 112 . Alternatively, the optical network device 110 - 2 may extract the management channel information from the overhead portion 1040 of the OPUflex frame of the second data frame 112 . In some embodiments, the second portion of the second data frame may include a first OPUflex frame and a second OPUflex frame, the first data frame being transmitted over the bonded first and second PHYs.
  • the optical network device 110-2 extracts management channel information for the first PHY from the first OPUflex frame, and extracts management channel information for the second PHY from the second OPUflex frame.
  • the network device 110-2 extracts the management channel information for the first PHY and the management channel information for the second PHY from the first OPUflex frame.
  • the optical network device 110-2 generates a 9075FlexE interface frame.
  • the optical network device 110-2 receives high precision clock information on a non-ODUflex channel and generates a high precision synchronous clock.
  • the optical network device 110-2 may generate a FlexE interface frame based on the high-precision synchronization clock and service data.
  • the optical network device 110-2 maps the service data to the FlexE interface frame.
  • the optical network device 110-2 maps 9080 the management channel information to the FlexE interface frame.
  • the FlexE interface frame includes service data and management channel information of the first FlexE interface frame.
  • the optical network device 110-2 transmits the 9085FlexE interface frame.
  • FIG. 13 shows a schematic block diagram of an apparatus 1300 for data processing according to some embodiments of the present disclosure.
  • the apparatus 1300 may be implemented as a device or a chip in a device, and the scope of the present disclosure is not limited in this regard.
  • the apparatus 1300 may be implemented as an optical network device 110 as shown in FIG. 1 or as a part of the optical network device 110 .
  • the units/components included in the apparatus 1300 may be implemented in one or more of the tributary board 204 , the crossover board 206 , the circuit board 205 and the programmable service board 207 as shown in FIG. 2 .
  • the apparatus 1300 includes: an obtaining unit 1301 configured to obtain the first data frame.
  • the acquiring unit 1301 may perform step 5010 as shown in FIG. 5 (receive the ODUflex frame) and the acquiring unit 1301 may also perform step 5015 as shown in FIG. 5 .
  • the obtaining unit 1301 may perform step 5002 as shown in FIG. 7 (ie, receive the FlexE interface frame from the communication node).
  • the apparatus 1300 further includes a first mapping unit 1302 configured to map the service data in the first data frame to the first part of the second data frame.
  • the first mapping unit 1302 may perform step 5045 shown in FIG. 5 and FIG. 7 .
  • the first mapping unit 1302 may perform step 9025 shown in FIG. 9 .
  • the apparatus 1300 further includes a second mapping unit 1303 configured to map the management channel information in the first data frame to the second part of the second data frame.
  • the second mapping unit 1303 may perform step 5055 shown in FIG. 5 and FIG. 7 .
  • the first mapping unit 1303 may perform step 9040 shown in FIG. 9 .
  • the apparatus 1300 also includes means for implementing the method 300 described with reference to FIG. 3 .
  • the apparatus 1300 may include means for implementing the steps performed by the optical network device 110-2 in FIG. 5 .
  • the apparatus 1300 may also include means for implementing the steps performed by the optical network device and 110-1 in FIG. 7 .
  • the apparatus 1300 may include means for implementing the steps performed by the optical network device and 110-1 in FIG. 9 .
  • details are not repeated here.
  • FIG. 14 shows a schematic block diagram of an apparatus 1400 for data processing according to some embodiments of the present disclosure.
  • the apparatus 1400 may be implemented as a device or a chip in a device, and the scope of the present disclosure is not limited in this regard.
  • the apparatus 1400 may be implemented as an optical network device 110 as shown in FIG. 1 or as a part of the optical network device 110 .
  • the units/components included in the apparatus 1400 may be implemented in one or more of the tributary board 204 , the crossover board 206 , the circuit board 205 and the programmable service board 207 as shown in FIG. 2 .
  • the apparatus 1400 includes: a de-mapping unit 1401, configured to de-map service data from the first part of the first data frame.
  • the obtaining unit 1401 may perform step 9065 as shown in FIG. 9 .
  • the apparatus 1400 includes an extraction unit 1402 configured to extract management channel information from the second part of the first data frame.
  • the extraction unit 1402 may perform step 9070 as shown in FIG. 9 .
  • the apparatus 1400 includes a generating unit 1403 configured to generate a second data frame based on the high-precision clock and service data.
  • the generating unit 1403 may perform step 9075 as shown in FIG. 9 .
  • the apparatus 1400 includes a mapping unit 1404 configured to map the management channel information to the second data frame.
  • the mapping unit 1404 may perform step 9080 of FIG. 9 .
  • the apparatus 1400 also includes means for implementing the method 400 described with reference to FIG. 4 .
  • the apparatus 1400 may also be used to implement the unit of the steps performed by the optical network equipment and 110-2 in FIG. 9 .
  • details are not repeated here.
  • Device 1500 is a simplified block diagram of an example device 1500 suitable for implementing embodiments of the present disclosure.
  • Device 1500 may be used to implement optical network device 110 as shown in FIG. 1 .
  • the device 1500 includes one or more processors 1510 , one or more memories 1520 coupled to the processors 1510 , and a communication module 1540 coupled to the processors 1510 .
  • the communication module 1540 may be used for two-way communication.
  • the communication module 1540 may have at least one communication interface for communication.
  • Communication interfaces may include any interface necessary to communicate with other devices.
  • the processor 1510 may be of any type suitable for a local technical network, and may include, but is not limited to, at least one of the following: a general purpose computer, a special purpose computer, a microcontroller, a Digital Signal Processor (DSP), or a control-based One or more of the multi-core controller architectures of the server.
  • Device 1500 may have multiple processors, such as application specific integrated circuit chips, that are temporally slaved to a clock synchronized with the main processor.
  • Memory 1520 may include one or more non-volatile memories and one or more volatile memories.
  • non-volatile memory include, but are not limited to, at least one of the following: Read-Only Memory (ROM) 1524, Erasable Programmable Read Only Memory (EPROM), flash memory, hard disk , Compact Disc (CD), Digital Versatile Disc (DVD) or other magnetic and/or optical storage.
  • volatile memory include, but are not limited to, at least one of the following: Random Access Memory (RAM) 1522, or other volatile memory that does not persist for the duration of a power outage.
  • RAM Random Access Memory
  • Computer program 1530 includes computer-executable instructions for execution by associated processor 1510 .
  • Program 1530 may be stored in ROM 1520.
  • Processor 1510 may perform any suitable actions and processes by loading program 1530 into RAM 1520.
  • Embodiments of the present disclosure may be implemented by means of program 1530 such that device 1500 may perform any process as described with reference to any of FIGS. 3-9.
  • Embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • program 1530 may be tangibly embodied on a computer-readable medium, which may be included in device 1500 (such as in memory 1520 ) or other storage device accessible by device 1500 .
  • Program 1530 may be loaded into RAM 1522 from a computer-readable medium for execution.
  • Computer readable media may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, and the like.
  • the various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or using some other pictorial representation, it should be understood that the blocks, apparatuses, systems, techniques or methods described herein may be implemented, without limitation, as Illustrative examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controllers or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium.
  • the computer program product includes computer-executable instructions, eg, instructions included in program modules, that execute in a device on a target's real or virtual processor to perform the processes/methods as described above with reference to FIGS. 3-9 .
  • program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or divided among the program modules as desired.
  • Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed facility, program modules may be located in both local and remote storage media.
  • Computer program code for implementing the methods of the present disclosure may be written in one or more programming languages. Such computer program code may be provided to a processor of a general purpose computer, special purpose computer or other programmable data processing apparatus such that the program code, when executed by the computer or other programmable data processing apparatus, causes the flowchart and/or block diagrams The functions/operations specified in are implemented.
  • the program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server.
  • computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform the various processes and operations described above.
  • carriers include signals, computer-readable media, and the like.
  • signals may include electrical, optical, radio, acoustic, or other forms of propagated signals, such as carrier waves, infrared signals, and the like.
  • a computer-readable medium may be any tangible medium that contains or stores a program for or in connection with an instruction execution system, apparatus, or device.
  • the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium.
  • Computer-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例涉及光通信领域，尤其涉及光网络中以太数据处理的方法、装置以及系统。在一种数据处理的方法中，光网络设备分开处理业务数据以及管理通道信息。光网络设备将业务数据和管理通道信息分别映射到数据帧的不同部分。以此方式，实现了同时满足管理通道信息和高精度时钟透传的需求。

Description

光网络中以太数据处理的方法、装置以及系统
本申请要求于2021年3月18日提交中国国家知识产权局、申请号202110291629.6、申请名称为“光网络中以太数据处理的方法、装置以及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本公开涉及光通信领域，具体地，涉及光网络中以太数据处理的方法、装置以及系统。
背景技术
当前，光互联论坛(Optical Internetworking Forum，OIF)在制定灵活以太网(Flexible Ethernet，FlexE)接口技术相关的标准，例如，FlexE IA 1.0/2.0/2.1。本文中使用的术语“FlexE”是指承载网实现业务隔离，业务带宽需求与物理接口带宽解耦合以及网络切片的一种接口技术。通过绑定n个100G PHY，或者m个200G PHY，或者m个400G PHY，或者m个50G PHY实现多路不同速率的FlexE业务传送，例如10G、n*25G、40G等FlexE业务，主要应用于数据中心设备互联等。对于FlexE数据的长距传输，可以通过光传送网(Optical transport network，OTN)进行承载传送。OTN承载FlexE数据相关的标准由国际电信联盟电信标准化部门(International Telecommunication Union-Telecommunication Standardization Sector，ITU-T)制定。
另外ITU-T中正在定义的城域传输网络(Metro Transport Network，MTN)的段层重用了FlexE接口技术。MTN主要用于5G承载，要求全网支持高精度时钟。在某些场景下，存在通过OTN网络传送情况，即MTN/FlexE通过OTN。因此在MTN/FlexE通过OTN情况下，同样需要OTN支持承载的FlexE高精度时钟透传，同时还需要支持数据通信通道(Data Communication Network，DCN)数据透传。其中，DCN位于FlexE接口的开销码块#4，#5，#6，#7，#8。该DCN数据主要包含MTN/FlexE接口的管理控制等信息。
发明内容
本公开的示例实施例提供了光网络中以太数据处理的方案。
在本公开的第一方面，提供了一种通信方法。该方法中，光网络设备获取第一数据帧。该光网络设备将第一数据帧中的业务数据映射到第二数据帧的第一部分。该光网络设备还将第一数据帧中的管理通道信息映射到第二数据帧的第二部分。以此方式，实现了业务数据和管理通道信息的分开处理，从而有助于满足管理通道信息和高精度时钟透传的需求。
在某些实施例中，第一数据帧为第一灵活以太网FlexE接口帧，第二数据帧为第二FlexE接口帧，并且，该光网络设备获取第一数据帧包括：光网络设备接收灵活光数据单元ODUflex帧。该光网络设备对ODUflex帧解映射，以获得第一FlexE接口帧。以此方式，可以在避免全OTN网络参与数据的处理。
在某些实施例中，光网络设备从FlexE接口帧的同步信息通道开销中提取第一同步信息并获取时钟。光网络设备基于时钟，生成第二FlexE接口帧。光网络设备基于第一同步信息来生成第二同步信息并插入第二FlexE接口帧。以此方式，实现了高精度时钟的透传。
在某些实施例中，光网络设备将第二FlexE接口帧映射到灵活光数据单元ODUflex帧。光网络设备发送ODUflex帧。以此方式，实现在OTN网络的入口设备处对数据帧的业务数据和管理通道信息的分开处理。
在某些实施例中，第一数据帧为灵活以太网FlexE接口帧，以及第二数据帧为灵活光净荷单元OPUflex帧。以此方式，实现在OTN网络的入口设备处对数据帧的业务数据和管理通道信息的分开处理。
在某些实施例中，FlexE接口帧通过绑定多个物理链路传送，第二数据帧包括多个OPUflex帧。光网络设备将从多个物理链路中每个物理链路提取管理通信信道信息。光网路设备将从每个物理链路提取的管理通信信道信息分别映射到多个OPUflex帧中的相应的OPUflex帧。例如，在某些实施例中，FlexE接口帧通过绑定的第一物理链路)和第二物理链路传送，第二数据帧包括第一OPUflex帧和第二OPUflex帧。光网络设备将第一数据帧中的管理通道信息映射到数据帧的第二部分包括：光网络设备从第一物理链路提取第一管理通道信息。光网络设备对第一管理通道信息进行速率适配；光网络设备将速率适配后的第一管理通道信息映射到第一OPUflex帧。光网络设备从第二物理链路提取第二管理通道信息。光网络设备对第二管理通道信息进行速率适配。光网络设备将速率适配后的第二管理通道信息映射到第二OPUflex帧。以此方式，避免增加数据帧的复杂性。
在某些实施例中，FlexE接口帧通过绑定多个物理链路传送，第二数据帧包括一个OPUflex帧。光网络设备将从多个物理链路中每个物理链路提取管理通信信道信息。光网路设备将从每个物理链路提取的管理通信信道信息映射到该OPUflex帧。例如，在某些实施例中，FlexE接口帧通过绑定的第一物理链路和第二PHY物理链路，第二部分包括第一OPUflex帧，其中光网络设备将第一数据帧中的管理通道信息映射到数据帧的第二部分包括光网络设备从第一物理链路提取第一管理通道信息。光网络设备从第二物理链路提取第二管理通道信息。光网络设备对第一管理通道信息和第一管理通道信息进行速率适配。光网络设备将速率适配后的第一管理通道信息以及速率适配后的第二管理通道信息映射到第一OPUflex帧。以此方式，避免了检测数据帧的复杂性。
在某些实施例中，光网络设备从FlexE接口帧的同步信息通道开销中提取第一同步信息并获取时钟。光网络设备基于时钟，生成非ODUflex通道信息。光网络设备基于第一同步信息生成第二同步信息并插入非ODUflex通道传送。以此方式，实现了高精度时钟的透传。
在本公开的第二方面，提供了一种通信方法。该方法包括：光网络设备从第一数据帧的第一部分中解映射出业务数据；光网络设备从第一数据帧的第二部分中提取管理通道信息；光网络设备基于时钟和业务数据生成第二数据帧；以及光网络设备将管理通道信息映射到第二数据帧。以此方式，以此方式，实现了业务数据和管理通道信息的分开处理，从而有助于满足管理通道信息和高精度时钟透传的需求。
在某些实施例中，第一数据帧为灵活光净荷单元OPUflex帧，第二数据帧为灵活以太网Flex接口帧。以此方式，实现在OTN网络的入口设备处对数据帧的业务数据和管理通道信息的分开处理。
在某些实施例中，第一数据帧包括第一灵活光净荷单元OPUflex帧和第二OPUflex帧，第二数据帧通过绑定的第一物理链路和第二物理链路传送，其中光网络设备从第一数据帧的第二部分中提取管理通道信息包括：光网络设备从第一OPUflex帧中提取用于第一物理链路的第一管理通道信息；以及光网络设备从第二OPUflex帧中提取用于第二物理链路的第二管 理通道信息。以此方式，避免增加数据帧的复杂性。
在某些实施例中，第一数据帧包括第一灵活光净荷单元OPUflex帧，第二数据帧通过绑定的第一物理链路和第二物理链路传送，其中光网络设备从第一数据帧的第二部分中提取管理通道信息包括：光网络设备从第一OPUflex帧中提取用于第一物理链路的第一管理通道信息；以及光网络设备从第一OPUflex帧中提取用于第二物理链路的第二管理通道信息。以此方式，避免了检测数据帧的复杂性。
在某些实施例中，该方法还包括：光网络设备在非ODUflex通道上接收时钟信息；以及所述光网络设备基于所述时钟信息，生成另一非ODUflex通道。以此方式，实现了高精度时钟的透传。
在本公开的第三方面，提供了一种用于数据处理的装置。该装置包括用于执行根据上述第一方面或第二方面中任意一种可能的实现方式中的方法的部件。
在本公开的第四方面，本公开提供了一种芯片。该芯片被配置为执行根据上述第一方面或第二方面中任意一种可能的实现方式中的方法的操作。
在本公开的第五方面，提供了一种用于数据处理的装置。该装置包括：处理器，用于执行根据上述第一方面或第二方面中任意一种可能的实现方式中的方法；以及接口，用于与该处理器交互，以收发该处理器收发的数据。
在本公开的第六方面，提供了一种光网络设备。该网络设备包括：装置，用于执行根据上述第一方面或第二方面中任意一种可能的实现方式中的方法；以及光收发器，用于与接口连接，以与该接口交互实现由该装置处理的数据帧的收发。
在本公开的第七方面，提供了一种计算机程序产品。计算机程序产品被有形地存储在计算机可读介质上并且包括计算机可执行指令，计算机可执行指令在被执行时使设备实现根据上述第一方面到第二方面中任意一种可能的实现方式中的方法的操作。
附图说明
结合附图并参考以下详细说明，本公开各实现方式的特征、优点及其他方面将变得更加明显。在此以示例性而非限制性的方式示出了本公开的若干实现方式，在附图中：
图1示出了本公开的实施例可应用的通信环境的示意框图；
图2示出了一种可能的网络设备硬件结构示意图；
图3示出了一种可能的数据处理方法流程示意图；
图4示出了一种可能的以太数据和开销处理示意图；
图5示出了根据本公开的一些实施例的通信过程的交互信令图；
图6示出了根据本公开的一些实施例的数据帧结构图；
图7示出了根据本公开的另一些实施例的通信过程的交互信令图；
图8示出了根据本公开的一些实施例的流程图；
图9示出了根据本公开的又一些实施例的通信过程的交互信令图；
图10示出了另一种可能的以太数据和开销处理示意图；
图11A和图11B分别示出了速率匹配的示意图；
图12A和图12B分别示出了管理通道信息映射的示意图；
图13示出了根据本公开的一些实施例的通信装置的示意框图；
图14示出了根据本公开的另一一些实施例的通信装置的示意框图；
图15示出了适合实现本公开的实施例的示例设备的简化框图。
在各个附图中，相同或相似参考数字表示相同或相似元素。
具体实施方式
下面将参照附图更详细地描述本公开的实施例。虽然附图中显示了本公开的某些实施例，然而应当理解的是，本公开可以通过各种形式来实现，而且不应该被解释为限于这里阐述的实施例，相反提供这些实施例是为了更加透彻和完整地理解本公开。应当理解的是，本公开的附图及实施例仅用于示例性作用，并非用于限制本公开的保护范围。
在本公开的实施例的描述中，术语“包括”及其类似用语应当理解为开放性包含，即“包括但不限于”。术语“基于”应当理解为“至少部分地基于”。术语“一个实施例”或“该实施例”应当理解为“至少一个实施例”。术语“第一”、“第二”等等可以指代不同的或相同的对象。下文还可能包括其他明确的和隐含的定义。
本申请的实施例适用于光网络，例如：光传送网络(Optical transport Network，简称OTN)。一个光网络通常由多个设备通过光纤连接而成，可以根据具体需要组成如线型、环形和网状等不同的拓扑类型。如图1所示的通信系统100包括光网络101以及通信节点(例如，通信节点130和通信节点140)。如图1所示，光网络101是由光网络设备110(例如，光网络设备110-1、光网络设备110-2以及光网络设备110-N，其中N为任意正整数)组成的网络。可以理解，光网络101可以包括任意数目的光网络设备。其中，103指示的是光纤；104指示的客户业务接口，用于实现客户业务数据的传输。一个网络可能有多个客户业务接口104。客户业务接口有时也被称为用户网络接口(User Network Interface，UNI)。根据实际的需要，光网络设备可能具备不同的功能。一般地来说，光网络设备分为光层设备、电层设备以及光电混合设备。光层设备指的是能够处理光层信号的设备，例如：光放大器(Optical Amplifier，OA)、光分插复用器(Optical Add/Drop Multiplexer,OADM)。OA也可被称为光线路放大器(Optical Line Amplifier，OLA)，主要用于对光信号进行放大，以支持在保证光信号的特定性能的前提下传输更远的距离。电层设备指的是能够处理电层信号的设备，例如：能够处理光数据单元(Optical Data Unit,ODU)信号的设备。光电混合设备指的是同时具备处理光层信号和电层信号能力的设备。需要说明的是，根据具体的集成需要，光网络设备可以集合多种不同功能的设备。本申请对适用于不同形态和集成度的光网络设备。除非特殊说明，本申请后续提到实施本申请揭示的技术的设备至少包括电层信号的处理能力。
图2给出了一个光网络设备110的硬件结构示意图。具体地，该设备100包括电源201、风扇202、辅助类单板203，还可能包括支路板204、线路板205、交叉板206、光层处理单板(图中未示出)、可编程业务板207以及系统控制和通信类单板208。需要说明的是，根据具体的需要，一个设备110具体包含的单板类型和数量可能不相同。例如，作为核心节点的网络设备可能没有支路板204。作为边缘节点的网络设备可能有多个支路板204。其中，电源201用于为设备供电，可能包括主用和备用电源。风扇202用于为设备散热。辅助类单板203用于提供外部告警或者接入外部时钟等辅助功能。支路板204、交叉板206、线路板205和可编程业务板207主要是用于处理光网络的电层信号(例如，OTN中的ODU帧)。其中，支路板204用于实现各种客户业务的接收和发送，例如同步数字体系(Synchronous Digital Hierarchy,SDH)业务、分组业务、以太网业务和前传业务等。更进一步地，支路板204可以划分为客户侧光模块和处理器。其中，客户侧光模块可以为光收发器，用于接收和/或发送客户信号。处 理器用于实现对客户信号到ODU帧的映射和解映射处理。交叉板206用于实现ODU帧的交换，完成一种或多种类型的ODU信号的交换。线路板205主要实现线路侧ODU帧的处理。具体地，线路板205可以划分为线路侧光模块和处理器。其中，线路侧光模块可以为线路侧光收发器，用于接收和/或发送ODU信号。处理器用于实现对线路侧的ODU帧的复用和解复用，或者映射和解映射处理。可编程业务板207用于实现本申请揭示的数据处理方法。系统控制和通信类单板208用于实现系统控制和通信。具体地，可以通过背板从不同的单板收集信息，或者将控制指令发送到对应的单板上去。需要说明的是，除非特殊说明，具体的组件(例如：处理器)可以是一个或多个，本申请不做任何限制。还需要说明的是，本申请实施例不对设备包含的单板类型，以及单板具体的功能设计和数量做任何限制。除非特殊说明，后续提及的设备至少包括具备可编程业务板207。需要说明的是，可编程业务板207也可以跟其他单板集成为一个单板。本申请对具体实现本申请揭示的数据处理技术的单板名称不做任何限制。
目前标准定义的FlexE在OTN上存在三种传送模式：FlexE不感知模式、FlexE感知模式和FlexE终结模式。在FlexE不感知模式中，光网络设备直接透传FlexE物理链路(PHY)信号。在FlexE感知模式中，光网络设备解析FlexE shim层，将无效FlexE时隙删除，并且将剩余部分进行透明传送。在终结模式中，光网络设备终结FlexE开销，提取出不同的FlexE client业务，并且基于FlexE client进行映射传送。然而，这三种模式都无法同时满足透传管理通道信息和FlexE高精度时钟透传需求。具体地，FlexE不感知模式和FlexE感知模式都属于FlexE数据比特透传(即数据面时钟透传，天然支持数据通信网络(DCN)透传)，而做到FlexE带内高精度时钟透传在OTN出口处又会涉及时钟源切换问题(从数据面时钟切换到逐跳再生高精度时钟)，这样必然要进行速率适配，FlexE不感知模式和FlexE感知模式在数据面无法支持。在终结模式下，光网络设备可以在OTN网络里通过提取报文信息(例如，精准时间同步协议(PTP)和/或同步状态信息(SSM))逐跳终结再生实现高精度时钟透传，但由于FlexE开销终结无法支持DCN透传。因此，传统的FlexE在OTN上的传送模式无法同时支持管理通道信息和高精度时钟的透传。
针对上述问题以及其他潜在的问题，根据本公开的实施例，光网络设备分开处理业务数据以及管理通道信息。光网络设备将业务数据和管理通道信息分别映射到数据帧的不同部分。以此方式，实现了同时满足管理通道信息和高精度时钟透传的需求。可以理解，本公开的实施例可以用于任意合适的光网络中的数据处理技术。
下文将参考附图来具体讨论本公开的示例实施例。为便于讨论，将参考图1的示例通信环境来描述根据本公开示例实施例的数据处理的流程以及通信实体间信令交互。应理解，本公开的示例实施例可以类似应用于其他通信环境中。
图3给出了一种示例的数据处理方法300的流程的示意图。在一些实施例中，方法300可以实现在入口侧的光网络设备处，例如，光网络设备110-1。备选地，方法300可以实现在出口侧的光网络设备处，例如，光网络设备110-2。图4示出了示例性的帧结构图。可以理解，图4所示的帧结构仅为说明的目的而非限制性的，帧结构可以包括其他在图4中没有示出的部分。此外，图4中示出了帧结构中的任意两部分之间可以为直接相邻的部分，也可以在二者间存在其他部分。现结合图4对图3进行描述。简言之，该方法300包括：(1)获取数据帧；(2)数据帧中业务数据的处理；以及(3)数据帧中开销处理。具体地，该方法300包括：
在框310处，光网络设备(例如，光网络设备110-1或光网络设备110-2)获取第一数 据帧410，第一数据帧410的格式为灵活以太网FlexE接口帧。在某些实施例中，如果方法300实现在光网络设备110-1处，光网络设备110-1可以从通信节点130接收第一数据帧410。
在其他实施例中，如果方法300实现在光网络设备110-2处，光网络设备110-2可以从光网络设备110-1接收灵活光数据单元ODUflex帧。在此情况下，光网络设备110-2可以对该ODUflex帧进行解映射，以获取第一数据帧410。
在框320处，光网络设备将第一数据帧410中的业务数据412映射到第二数据帧420中的第一部分422。在某些实施例中，第二数据帧420的格式可以为FlexE接口帧。在其他实施例中，第二数据帧420的格式可以为OTN帧。在此情况下，第一部分422为灵活光净荷单元OPUflex帧的净荷区。
在框330处，光网络设备将第一数据帧410中的管理通道信息411映射到第二数据帧420中的第二部分421。在某些实施例中，第二数据帧420的格式可以为FlexE接口帧。在其他实施例中，例如，当方法300实现在光网络设备110-1处时，第二数据帧420的格式可以为OTN帧。在此情况下，第二部分422可以为OPUflex帧。在某些实施例中，第二部分422可以是OPUflex帧的净荷区。在其他实施例中，第二部分422可以是OPUflex帧的开销区。以此方式，实现了业务数据和管理通道信息的分开处理，从而有助于同时满足管理通道信息和高精度时钟的透传需求。
在一些实施例中，光网络设备从第一数据帧410的同步信息通道开销413中提取第一同步信息并获取时钟。该时钟可以是高精度时钟。本文中使用的术语“高精度时钟”是指精度误差小于预定误差的时钟，或精度要求大于预定精度的时钟。光网络设备还基于提取的第一同步信息生成第二同步信息。在某些实施例中，光网络设备基于获取的时钟来生成第二数据帧420，并且第二数据帧420的格式可以为FlexE接口帧。在此实施例中，光网络设备将生成的新的同步信息映插入到第二数据帧420中。在其他实施例中，光网络设备可以基于获取的高精度时钟来生成非ODUflex通道信息。在此实施例中，光网络设备将生成的新的同步信息映插入到非ODUflex通道信息中进行传送。例如，可以通过光监控通道(Optical Supervisory Channel，OSC)来传递新生成的同步信息。可以理解，插入的方法可以包括，例如：直接插入、进行数学运算后插入或先缓存后再插入等。以此方式，避免了同步信息的不必要的再生成。
可以理解，上述针对方法300的描述仅为实施例的概括性描述。下面将附图5-9来描述具体的示例实施例。图5示出了当方法300在OTN出口侧的设备(例如，光网络设备110-2)实现时，各个设备之间的交互500的信令图。
如图5所示，通信节点130向光网络设备110-1发送5002第一FlexE接口帧。该第一FlexE接口帧包括业务数据。例如，该第一FlexE接口帧包括一个或多个FlexE业务数据流。如图6所示，第一FlexE接口帧600包括FlexE客户(Client)业务数据流6010(例如，数据部分6010-1，数据部分6010-2，数据部分6010-3以及数据部分6010-4)以及FlexE Client业务数据流6020(例如，数据部分6020-1，数据部分6020-2，数据部分6020-3以及数据部分6020-4)。第一FlexE接口帧600还包括开销部分610。例如，开销部分610包括管理通道信息，例如，DCN信息。在某些实施例中，开销部分610还可以包括FlexE组ID、该FlexE接口帧的实例号或时隙分布图案中的一项或多项。
光网络设备110-1将第一FlexE接口帧映射5005到ODUflex帧。在某些实施例中，光网络设备110-1可以利用感知模式将第一FlexE接口帧映射到ODUflex帧。例如，光网络设备110-1可以直接透传第一FlexE接口帧的FlexE PHY。备选地，光网络设备110-1可以利用 非感知模式将第一FlexE接口帧映射到ODUflex帧。例如，光网络设备110-1可以解析第一FlexE接口帧的FlexE shim层并删除无效时隙。继而，光网络设备110-1可以将剩余部分进行透明传送。光网络设备110-1将ODUflex帧发送5010到光网络设备110-2。该光网络设备110-2位于OTN网络的出口侧。以此方式，可以避免全OTN网络参与数据的处理，降低数据处理过程中错误的概率。光网络设备110-2解映射5015接收到的ODUflex帧，从而获得第一FlexE接口帧600。此处的解映射方式取决于在5005处的映射方式。例如，非感知模式下，第一数据帧到ODUflex帧的映射/解映射过程为，例如：FlexE接口<＝>ODUflex。
光网络设备110-2可以对第一FlexE接口帧600进行开销终结处理。光网络设备110-2从第一FlexE接口帧600获取5020业务数据流。光网络设备110-2从第一FlexE接口帧600提取5025管理通道信息。例如，光网络设备110-2可以直接从开销部分610提取出DCN信息(例如，66b码块流)。
光网络设备110-2从第一FlexE接口帧600提取5030同步信息，并且基于提取的同步信息来生成5035新的同步信息。例如，光网络设备110-2可以从开销部分610提取出PTP和/或SSM报文信息，并且生成新的PTP和/或SSM报文信息。
光网络设备110-2还可以从开销部分610获取高精度时钟，并且基于该高精度时钟来生成5040第二FlexE接口帧。光网络设备110-2将业务数据帧映射5045到第二FlexE接口帧。光网络设备110-2还可以添加第二FlexE接口帧的开销。例如，开销可以包括FlexE组ID、该FlexE接口帧的实例号或时隙分布图案中的一项或多项。
光网络设备110-2可以对提取的管理通道信息进行速率适配5050。在某些实施例中，光网络设备110-2可以利用空闲66b码块进行速率适配。例如，光网络设备110-2将空闲66b码块插入开始(S)码块和终结(T)码块之间，或者将S码块和T码块之间的一个或多个空闲66b码块删除。这样的适配方式具有良好的兼容性。
光网络设备110-2将适配后的管理通道信息插入5055到第二FlexE接口帧。光网络设备110-2还将生成的新的同步信息插入5060到第二FlexE接口帧。应理解，步骤5015-5060的发生顺序可以与图5所示的顺序不同。光网络设备110-2将第二FlexE接口帧发送5065发送到通信节点150。以此方式，实现了管理通道信息和高精度时钟的透传，并且具有良好的兼容性。
图7示出了当方法300在OTN入口侧的设备(例如，光网络设备110-1)实现时各个设备之间的交互700的信令图。应理解，图7中与图5中相同或类似的步骤使用相同的附图标记标识。
如图7所示，通信节点130向光网络设备110-1发送5002第一FlexE接口帧。该第一FlexE接口帧所包括的信息可以参照针对图5的描述，在此不赘述。
光网络设备110-1可以对第一FlexE接口帧600进行开销终结处理。光网络设备110-1从第一FlexE接口帧获取5020业务数据流。光网络设备110-1从第一FlexE接口帧提取5025管理通道信息。例如，光网络设备110-1可以直接从第一FlexE接口帧的开销部分提取出DCN信息(例如，66b码块流)。
光网络设备110-1从第一FlexE接口帧提取5030第一同步信息，并且基于提取的同步信息来生成5035第二同步信息。例如，光网络设备110-1可以从开销部分提取出PTP和/或SSM报文信息，并且生成新的PTP和/或SSM报文信息。
光网络设备110-1还可以从开销部分获取时钟，并且基于该时钟来生成5040第二FlexE 接口帧。光网络设备110-1将业务数据帧映射5045到第二FlexE接口帧。光网络设备110-1还可以添加第二FlexE接口帧的开销。例如，开销可以包括FlexE组ID、该FlexE接口帧的实例号或时隙分布图案中的一项或多项。
光网络设备110-1可以对提取的管理通道信息进行速率适配5050。例如，光网络设备110-2可以利用空闲66b码块进行速率适配。具体的速率适配过程可以参照针对图5的描述，在此不赘述。
光网络设备110-1将适配后的管理通道信息插入5055到第二FlexE接口帧。光网络设备110-1还将生成的第二同步信息插入5060到第二FlexE接口帧。光网络设备110-1将第二FlexE接口帧映射7065到ODUflex帧中。第二FlexE接口帧映射到ODUflex帧的映射方式可以参照针对图5的从第一FlexE接口帧映射到ODUflex帧的映射方式进行的描述，在此不赘述。可以理解，上述多个步骤的发生顺序可以与图7所示的顺序不同。
光网络设备110-1将ODUflex帧发送7070到光网络设备110-2。光网络设备110-2解映射7075接收到的ODUflex帧，从而获得第二FlexE接口帧。此处的解映射方式取决于在7065处的映射方式。以此方式，实现了管理通道信息和高精度时钟的透传，并且具有良好的兼容性。光网络设备110-2将第二FlexE接口帧发送7080到通信节点140。
图8给出了一种示例的另一数据处理方法800的流程的示意图。方法800可以实现在出口侧的光网络设备处，例如，光网络设备110-2。可以理解，下述针对方法800的描述仅为实施例的概括性描述。
在框810处，光网络设备110-2从第一数据帧的第一部分解映射出业务数据。在某些实施例中，第一数据帧的格式为OTN帧，第一部分为OPUflex净荷区。例如，光网络设备110-2可以从该OPUflex净荷区解映射出一个或多个FlexE业务数据流。
在框820处，光网络设备110-2从第一数据帧的第二部分解提取管理通道信息。某些实施例中，第二部分为OPUflex帧。在某些实施例中，光网络设备110-2可以从OPUflex帧的开销部分提取管理通道信息。备选地，光网络设备110-2可以从OPUflex帧的净荷部分提取管理通道信息。在某些实施例中，光网络设备110-2可以直接提取出DCN信息(例如，66b码块流)。
在框830处，光网络设备110-2基于高精度时钟和业务数据生成第二数据帧。在某些实施例中，第一数据帧为Flex接口帧。在某些实施例中，光网络设备110-2在非ODUflex通道上接收高精度时钟信息，并且基于该高精度时钟信息来生成FlexE接口。
在框840处，光网络设备110-2将管理通道信息添加到第二数据帧。例如，光网络设备110-2可以将管理通道信息添加到第二数据帧的开销部分。
图9示出了在OTN入口侧的设备实现方法300以及在出口侧的设备实现方法800时，各个设备之间的交互900的信令图。
如图9所示，通信节点130向光网络设备110-1发送5002第一FlexE接口帧。该第一FlexE接口帧包括业务数据。例如，该第一FlexE接口帧包括一个或多个FlexE业务数据流。如图10所示，第一FlexE接口帧111包括FlexE Client业务数据流1010(例如，数据部分1010-1，数据部分1010-2，数据部分1010-3以及数据部分1010-4)以及FlexE Client业务数据流1020(例如，数据部分1020-1，数据部分1020-2，数据部分1020-3以及数据部分1020-4)。第一FlexE接口帧1000还包括开销部分1000。例如，开销部分1000包括管理通道信息，例如，DCN信息。在某些实施例中，开销部分1000还可以包括FlexE组ID、该FlexE接口帧的实 例号或时隙分布图案中的一项或多项。
光网络设备110-1从第一FlexE接口帧获取5020业务数据。光网络设备110-1将获得的业务数据映射9025到第二数据帧的第一部分。如图10所示，光网络设备110-1将业务数据流1010映射到第二数据帧112的OPUflex帧的净荷部分1030-1。在某些实施例中，光网络设备110-1将业务数据流1020映射到同一数据数据帧的OPUflex帧的净荷部分1030-2。在其他的实施例中，光网络设备110-1将业务数据流1020映射到另一数据数据帧的OPUflex帧的净荷部分(未示出)。
光网络设备110-1从第一FlexE接口帧提取5025管理通道信息。在某些实施例中，光网络设备110-1从第一FlexE接口帧111的开销部分1000提取管理通道信息。例如，光网络设备110-1可以从开销部分1000的第7码块和第8码块提取DCN信息，并且按顺序形成DCN的66b码块。备选地，光网络设备110-1可以从开销部分1000的第4码块、第5码块、第6码块、第7码块或第8码块提取DCN信息。本公开的实施例在此方面不受限制。
光网络设备110-1对管理通道信息进行速率适配9035。在某些实施例中，光网络设备110-2可以利用空闲的66b码块进行速率适配。如图11A所示，光网络设备110-1将空闲66b码块1113-1以及1113-2插入S码块1111和T码块1112之间。可以理解，光网络设备110-1可以插入任意合适数目的空闲码块。备选地，光网络设备110-1可以将S码块和T码块之间的一个或多个空闲66b码块删除。这样的适配方式具有良好的兼容性。
可选地，光网络设备110-1可以使用特殊的66b码块进行速率适配。如图11B所示，光网络设备110-1将特殊的66b码块1114任意两个码块之间。可以理解，光网络设备110-1可以插入任意合适数目的空闲码块。这样的适配方式具有良好的兼容性，且简单，便于实现。可以理解，图11A和图11B所示的速率适配方式仅示例，而非限制性的。
光网络设备110-1将速率适配后的管理通道信息映射9040到第二数据帧的第二部分。在某些实施例中，第二部分可以为OPUflex帧的净荷部分。备选地，第二部分可以为OPUflex帧的开销部分。例如，光网络设备110-1可以将管理通道信息映射到OPUflex帧的净荷区1030-1。在其他实施例中，光网络设备110-1可以将管理通道信息映射到OPUflex帧的开销部分1040。仅作为示例，管理通道信息可以被映射到J1到J2。可以理解，经映射的管理通道信息可以占用任意合适的开销字节数目以及任意合适的开销字节。
在某些实施例中，第一数据帧可以通过绑定的多路PHY传送。如图12A和12B所示，第一数据帧可以通过FlexE PHY 1210-1，FlexE PHY 1210-2，...，FlexE PHY 1210-N传送，N为任意合适的正整数。每个FlexE PHY包含相应的管理通道信息。如图12A所示，光网络设备110-1可以从第一FlexE PHY 1210-1提取第一管理通道信息1220-1，并将该第一管理通道信息1220-1映射到第一OPUflex帧1230-1。类似地，光网络设备110-1可以从第二FlexE PHY 1210-2提取第二管理通道信息1220-2，并将该第二管理通道信息1220-2映射到第二OPUflex帧1230-2。光网络设备110-1可以从第N FlexE PHY 1210-N提取第N管理通道信息1220-N，并将该第N管理通道信息1220-N映射到第N OPUflex帧1230-N。
备选地，如图12B所示，光网络设备110-1可以从第一FlexE PHY 1210-1提取第一管理通道信息1220-1，从第二FlexE PHY 1210-2提取第二管理通道信息1220-2，从第N FlexE PHY1210-N提取第N管理通道信息1220-N。光网络设备110-1可以将管理通道信息1220-1、1220-2、...、1220-N映射到第一OPUflex帧1230-1。
光网络设备110-1提取5030第一同步信息。如图10所示，光网络设备110-1可以从开 销1000提取同步信息。例如，光网络设备110-1可以从开销的第6码块提取PTP和/或SSM。光网络设备110-1生成5035第二同步信息。光网络设备110-1还可以获取时钟，并且基于该时钟生成非ODUflex通道信息。光网络设备110-1将生成的第二同步信息插入非ODUflex通道信息进行传送9055。
光网络设备110-1发送9060第二数据帧。该第二数据帧包括第一数据帧的业务数据以及管理通道信息。可以理解，上述步骤的发生顺序可以与图9所示的顺序不同。类似地，步骤9055和9060的发生顺序也可以与图9所示的顺序不同。
光网络设备110-2获得9065业务数据。如图10所示，光网络设备110-2可以从第二数据帧112的OPUflex帧的净荷部分1030-1提取业务数据流1010。在某些实施例中，光网络设备110-2可以从同一数据数据帧的OPUflex帧的净荷部分1030-2解映射出业务数据流1020。在其他的实施例中，光网络设备110-2可以从另一数据数据帧的OPUflex帧的净荷部分(未示出)解映射出业务数据流1020。
光网络设备110-2提取9070管理通道信息。如图10所示，光网络设备110-2可以从第二数据帧112的OPUflex帧的净荷部分1030-1提取管理通道信息。备选地，光网络设备110-2可以从第二数据帧112的OPUflex帧的开销部分1040提取出管理通道信息。在某些实施例中，第二数据帧的第二部分可以包括第一OPUflex帧和第二OPUflex帧，第一数据帧通过绑定的第一PHY和第二PHY传送。在此情况下，光网络设备110-2从第一OPUflex帧提取用于第一PHY的管理通道信息，并且从第二OPUflex帧提取用于第二PHY的管理通道信息。备选地，网络设备110-2从第一OPUflex帧提取用于第一PHY的管理通道信息以及用于第二PHY的管理通道信息。
光网络设备110-2生成9075FlexE接口帧。例如，光网络设备110-2在非ODUflex通道上接收高精度时钟信息，并且生成高精度同步时钟。光网络设备110-2可以基于该高精度同步时钟以及业务数据来生成FlexE接口帧。光网络设备110-2将业务数据映射到FlexE接口帧。光网络设备110-2将管理通道信息映射9080到该FlexE接口帧。该FlexE接口帧包括第一FlexE接口帧的业务数据以及管理通道信息。光网络设备110-2发送9085FlexE接口帧。
图13示出了根据本公开的一些实施例的用于数据处理的装置1300的示意框图。该装置1300可以被实现为设备或者设备中的芯片，本公开的范围在此方面不受限制。该装置1300可以被实现为如图1中示出的光网络设备110或者光网络设备110的一部分。例如，该装置1300所包括的单元/部件可以被实现在如图2所示的支路板204、交叉板206、线路板205和可编程业务板207中的一个或多个中。
如图13所示，该装置1300包括：获取单元1301，被配置获取第一数据帧。在某些实施中，获取单元1301可以执行如图5步骤5010(接收ODUflex帧)以及获取单元1301还可以执行如图5所示的步骤5015。在某些实施例中，获取单元1301可以执行如图7所示的步骤5002(即，从通信节点接收FlexE接口帧)。该装置1300还包括第一映射单元1302，被配置为将第一数据帧中的业务数据映射到第二数据帧的第一部分。例如，第一映射单元1302可以执行图5和图7所示的步骤5045。在某些实施例中，第一映射单元1302可以执行图9所示的步骤9025。该装置1300还包括第二映射单元1303，被配置为将第一数据帧中的管理通道信息映射到第二数据帧的第二部分。例如，第二映射单元1303可以执行图5和图7所示的步骤5055。在某些实施例中，第一映射单元1303可以执行图9所示的步骤9040。该装置1300还包括实现参考图3所描述的方法300的单元。例如，该装置1300可以包括用于实现 图5中光网络设备110-2所执行的步骤的单元。该装置1300还可以包括用于实现图7中光网络设备和110-1所执行的步骤的单元。在其他实施例中，该装置1300可以包括用于实现图9中光网络设备和110-1所执行的步骤的单元。为了简明的目的，在此不做赘述。
图14示出了根据本公开的一些实施例的用于数据处理的装置1400的示意框图。该装置1400可以被实现为设备或者设备中的芯片，本公开的范围在此方面不受限制。该装置1400可以被实现为如图1中示出的光网络设备110或者光网络设备110的一部分。例如，该装置1400所包括的单元/部件可以被实现在如图2所示的支路板204、交叉板206、线路板205和可编程业务板207中的一个或多个中。
如图14所示，该装置1400包括：解映射单元1401，被配置为从第一数据帧的第一部分中解映射出业务数据。例如，获取单元1401可以执行如图9步骤9065。该装置1400包括提取单元1402，被配置为从第一数据帧的第二部分中提取管理通道信息。例如，提取单元1402可以执行如图9步骤9070。该装置1400包括生成单元1403，被配置为基于高精度时钟和业务数据生成第二数据帧。例如，生成单元1403可以执行如图9步骤9075。该装置1400包括映射单元1404，被配置为将管理通道信息映射到第二数据帧。例如，映射单元1404可以执行如图9步骤9080。该装置1400还包括实现参考图4所描述的方法400的单元。例如，该装置1400还可以用于实现图9中光网络设备和110-2所执行的步骤的单元。为了简明的目的，在此不做赘述。
图15是适合于实现本公开的实施例的示例设备1500的简化框图。设备1500可以用于实现如图1所示的光网络设备110。如图所示，设备1500包括一个或多个处理器1510，耦合到处理器1510的一个或多个存储器1520，以及耦合到处理器1510的通信模块1540。
通信模块1540可以用于双向通信。通信模块1540可以具有用于通信的至少一个通信接口。通信接口可以包括与其他设备通信所必需的任何接口。
处理器1510可以是适合于本地技术网络的任何类型，并且可以包括但不限于以下至少一种：通用计算机、专用计算机、微控制器、数字信号处理器(Digital Signal Processor，DSP)、或基于控制器的多核控制器架构中的一个或多个。设备1500可以具有多个处理器，例如专用集成电路芯片，其在时间上从属于与主处理器同步的时钟。
存储器1520可以包括一个或多个非易失性存储器和一个或多个易失性存储器。非易失性存储器的示例包括但不限于以下至少一种：只读存储器(Read-Only Memory，ROM)1524、可擦除可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、硬盘、光盘(Compact Disc，CD)、数字视频盘(Digital Versatile Disc,DVD)或其他磁存储和/或光存储。易失性存储器的示例包括但不限于以下至少一种：随机存取存储器(Random Access Memory，RAM)1522、或不会在断电持续时间中持续的其他易失性存储器。
计算机程序1530包括由关联处理器1510执行的计算机可执行指令。程序1530可以存储在ROM 1520中。处理器1510可以通过将程序1530加载到RAM 1520中来执行任何合适的动作和处理。
可以借助于程序1530来实现本公开的实施例，使得设备1500可以执行如参考图3至图9任一描述的任何过程。本公开的实施例还可以通过硬件或通过软件和硬件的组合来实现。
在一些实施例中，程序1530可以有形地包含在计算机可读介质中，该计算机可读介质可以包括在设备1500中(诸如在存储器1520中)或者可以由设备1500访问的其他存储设备。可以将程序1530从计算机可读介质加载到RAM 1522以供执行。计算机可读介质可以包括任 何类型的有形非易失性存储器，例如ROM、EPROM、闪存、硬盘、CD、DVD等。
通常，本公开的各种实施例可以以硬件或专用电路、软件、逻辑或其任何组合来实现。一些方面可以用硬件实现，而其他方面可以用固件或软件实现，其可以由控制器，微处理器或其他计算设备执行。虽然本公开的实施例的各个方面被示出并描述为框图，流程图或使用一些其他图示表示，但是应当理解，本文描述的框，装置、系统、技术或方法可以实现为，如非限制性示例，硬件、软件、固件、专用电路或逻辑、通用硬件或控制器或其他计算设备，或其某种组合。
本公开还提供有形地存储在非暂时性计算机可读存储介质上的至少一个计算机程序产品。该计算机程序产品包括计算机可执行指令，例如包括在程序模块中的指令，其在目标的真实或虚拟处理器上的设备中执行，以执行如上参考图3至图9的过程/方法。通常，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、库、对象、类、组件、数据结构等。在各种实施例中，可以根据需要在程序模块之间组合或分割程序模块的功能。用于程序模块的机器可执行指令可以在本地或分布式设备内执行。在分布式设备中，程序模块可以位于本地和远程存储介质中。
用于实现本公开的方法的计算机程序代码可以用一种或多种编程语言编写。这些计算机程序代码可以提供给通用计算机、专用计算机或其他可编程的数据处理装置的处理器，使得程序代码在被计算机或其他可编程的数据处理装置执行的时候，引起在流程图和/或框图中规定的功能/操作被实施。程序代码可以完全在计算机上、部分在计算机上、作为独立的软件包、部分在计算机上且部分在远程计算机上或完全在远程计算机或服务器上执行。
在本公开的上下文中，计算机程序代码或者相关数据可以由任意适当载体承载，以使得设备、装置或者处理器能够执行上文描述的各种处理和操作。载体的示例包括信号、计算机可读介质、等等。信号的示例可以包括电、光、无线电、声音或其它形式的传播信号，诸如载波、红外信号等。
计算机可读介质可以是包含或存储用于或有关于指令执行系统、装置或设备的程序的任何有形介质。计算机可读介质可以是计算机可读信号介质或计算机可读存储介质。计算机可读介质可以包括但不限于电子的、磁的、光学的、电磁的、红外的或半导体系统、装置或设备，或其任意合适的组合。此外，尽管在附图中以特定顺序描述了本公开的方法的操作，但是这并非要求或者暗示必须按照该特定顺序来执行这些操作，或是必须执行全部所示的操作才能实现期望的结果。相反，流程图中描绘的步骤可以改变执行顺序。附加地或备选地，可以省略某些步骤，将多个步骤组合为一个步骤执行，和/或将一个步骤分解为多个步骤执行。还应当注意，根据本公开的两个或更多装置的特征和功能可以在一个装置中具体化。反之，上文描述的一个装置的特征和功能可以进一步划分为由多个装置来具体化。
以上已经描述了本公开的各实现，上述说明是示例性的，并非穷尽的，并且也不限于所公开的各实现。在不偏离所说明的各实现的范围和精神的情况下，对于本技术领域的普通技术人员来说许多修改和变更都是显而易见的。本文中所用术语的选择，旨在很好地解释各实现的原理、实际应用或对市场中的技术的改进，或者使本技术领域的其他普通技术人员能理解本文公开的各个实现方式。

Claims (18)

  1. 一种在光网络中处理数据的方法，其特征在于，所述方法包括：
    光网络设备获取第一数据帧；
    所述光网络设备将所述第一数据帧中的业务数据映射到第二数据帧的第一部分；以及
    所述光网络设备将所述第一数据帧中的管理通道信息映射到所述第二数据帧的第二部分。
  2. 根据权利要求1所述的方法，其特征在于，所述第一数据帧为第一灵活以太网FlexE接口帧，所述第二数据帧为第二FlexE接口帧，其中，光网络设备获取第一数据帧包括：
    所述光网络设备接收灵活光数据单元ODUflex帧；以及
    所述光网络设备对所述ODUflex帧解映射，以获得所述第一FlexE接口帧。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述光网络设备从所述FlexE接口帧的同步信息通道开销中提取同步信息并获取时钟；
    所述光网络设备基于所述时钟，生成所述第二FlexE接口帧；以及
    所述光网络设备基于所述第一同步信息来生成第二同步信息并插入所述第二FlexE接口帧。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述方法还包括：
    所述光网络设备将所述第二FlexE接口帧映射到灵活光数据单元ODUflex帧；以及所述光网络设备发送所述ODUflex帧。
  5. 根据权利要求1所述的方法，其特征在于，所述第一数据帧为灵活以太网FlexE接口帧，以及所述第二数据帧为灵活光净荷单元OPUflex帧。
  6. 根据权利要求5所述的方法，其特征在于，所述FlexE接口帧通过绑定的第一物理链路和第二物理链路传送，所述第二数据帧包括第一OPUflex帧和第二OPUflex帧，其中所述光网络设备将所述第一数据帧中的管理通道信息映射到数据帧的第二部分包括：
    所述光网络设备从所述第一物理链路提取第一管理通道信息；
    所述光网络设备对所述第一管理通道信息进行速率适配；
    所述光网络设备将所述速率适配后的第一管理通道信息映射到所述第一OPUflex帧；
    所述光网络设备从所述第二物理链路提取第二管理通道信息；
    所述光网络设备对所述第二管理通道信息进行速率适配；以及
    所述光网络设备将所述速率适配后的第二管理通道信息映射到所述第二OPUflex帧。
  7. 根据权利要求5所述的方法，其特征在于，所述FlexE接口帧通过绑定的第一物理链路和第二物理链路传送，所述第二部分包括第一OPUflex帧，其中所述光网络设备将所述第一数据帧中的管理通道信息映射到数据帧的第二部分包括：
    所述光网络设备从所述第一物理链路提取第一管理通道信息；
    所述光网络设备从所述第二物理链路提取第二管理通道信息；
    所述光网络设备对所述第一管理通道信息和所述第一管理通道信息进行速率适配；以及
    所述光网络设备将所述速率适配后的第一管理通道信息以及所述速率适配后的第二管理通道信息映射到所述第一OPUflex帧。
  8. 根据权利要求5-7中任一项所述的方法，其特征在于，所述方法还包括：
    所述光网络设备从所述FlexE接口帧的同步信息通道开销中提取第一同步信息并获取时 钟；
    所述光网络设备基于所述时钟，生成非ODUflex通道信息；以及
    所述光网络设备基于所述第一同步信息生成第二同步信息并插入非ODUflex通道传送。
  9. 一种在光网络中处理数据的方法，其特征在于，所述方法包括：
    光网络设备从第一数据帧的第一部分中解映射出业务数据；
    所述光网络设备从第一数据帧的第二部分中提取管理通道信息；
    所述光网络设备基于时钟和所述业务数据生成第二数据帧；以及
    所述光网络设备将所述管理通道信息映射到所述第二数据帧。
  10. 根据权利要求9所述的方法，其特征在于，所述第一数据帧为灵活光净荷单元OPUflex帧，所述第二数据帧为灵活以太网Flex接口帧。
  11. 根据权利要求9或10所述的方法，其特征在于，所述第一数据帧包括第一灵活光净荷单元OPUflex帧和第二OPUflex帧，所述第二数据帧通过绑定的第一物理链路和第二物理链路传送，其中所述光网络设备从第一数据帧的第二部分中提取管理通道信息包括：
    所述光网络设备从所述第一OPUflex帧中提取用于所述第一物理链路的第一管理通道信息；以及
    所述光网络设备从所述第二OPUflex帧中提取用于所述第二物理链路的第二管理通道信息。
  12. 根据权利要求9或10所述的方法，其特征在于，所述第一数据帧包括第一灵活光净荷单元OPUflex帧，所述第二数据帧通过绑定的第一物理链路和第二物理链路传送，其中所述光网络设备从第一数据帧的第二部分中提取管理通道信息包括：
    所述光网络设备从所述第一OPUflex帧中提取用于所述第一物理链路的第一管理通道信息；以及
    所述光网络设备从所述第一OPUflex帧中提取用于所述第二物理链路的第二管理通道信息。
  13. 根据权利要求9-12中任一项所述的方法，其特征在于，所述方法还包括：
    所述光网络设备在非ODUflex通道上接收时钟信息；以及
    所述光网络设备基于所述时钟信息，生成FlexE接口。
  14. 一种用于数据处理的装置，所述装置应用于一个光网络设备中，其特征在于，包括：
    处理器，用于执行根据权利要求1-8中任一项所述的方法；以及
    接口，用于与所述处理器交互，以收发所述处理器收发的数据帧。
  15. 一种用于数据处理的装置，所述装置应用于一个光网络设备中，其特征在于，包括：
    处理器，用于执行根据权利要求9-13中任一项所述的方法；以及
    接口，用于与所述处理器交互，以收发所述处理器收发的数据帧。
  16. 一种光网络设备，其特征在于，包括：
    装置，用于执行根据权利要求1-8中任一项所述的方法；以及
    光收发器，用于与接口连接，以与所述接口交互实现由所述装置处理的数据帧的收发。
  17. 一种光网络设备，其特征在于，包括：
    装置，用于执行根据权利要求9-13中任一项所述的方法；以及
    光收发器，用于与接口连接，以与所述接口交互实现由所述装置处理的数据帧的收发。
  18. 一种芯片，被配置为执行根据权利要求1至8中任一项或权利要求9至13中任一项。
PCT/CN2022/081794 2021-03-18 2022-03-18 光网络中以太数据处理的方法、装置以及系统 WO2022194290A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110291629.6A CN115118371A (zh) 2021-03-18 2021-03-18 光网络中以太数据处理的方法、装置以及系统
CN202110291629.6 2021-03-18

Publications (1)

Publication Number Publication Date
WO2022194290A1 true WO2022194290A1 (zh) 2022-09-22

Family

ID=83322072

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/081794 WO2022194290A1 (zh) 2021-03-18 2022-03-18 光网络中以太数据处理的方法、装置以及系统

Country Status (2)

Country Link
CN (1) CN115118371A (zh)
WO (1) WO2022194290A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110248260A (zh) * 2018-03-07 2019-09-17 华为技术有限公司 光网络中以太数据处理的方法、装置和系统
CN110875862A (zh) * 2018-08-31 2020-03-10 中兴通讯股份有限公司 一种报文传输方法及装置、计算机存储介质
US20200396050A1 (en) * 2018-01-24 2020-12-17 Ciena Corporation Systems and methods for precise time synchronization with optical modules
CN112491492A (zh) * 2019-09-12 2021-03-12 华为技术有限公司 一种时隙协商的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200396050A1 (en) * 2018-01-24 2020-12-17 Ciena Corporation Systems and methods for precise time synchronization with optical modules
CN110248260A (zh) * 2018-03-07 2019-09-17 华为技术有限公司 光网络中以太数据处理的方法、装置和系统
CN110875862A (zh) * 2018-08-31 2020-03-10 中兴通讯股份有限公司 一种报文传输方法及装置、计算机存储介质
CN112491492A (zh) * 2019-09-12 2021-03-12 华为技术有限公司 一种时隙协商的方法和设备

Also Published As

Publication number Publication date
CN115118371A (zh) 2022-09-27

Similar Documents

Publication Publication Date Title
EP2312780B1 (en) A packet add/drop multiplexing device and a data transmission method of a packet add/drop multiplexing device
CN107438028B (zh) 一种客户业务处理的方法和设备
US20200235905A1 (en) Data Transmission Method In Optical Network And Optical Network Device
KR100567326B1 (ko) Ｓｏｎｅｔ／ｓｄｈ, ｐｄｈ, 그리고 이더넷 신호의 통합스위칭/전달 장치 및 그 방법
JP4844219B2 (ja) 光ネットワーク及びノード
US11271668B2 (en) Data transmission methods, apparatuses, devices, and system
WO2018090856A1 (zh) 用于建立灵活以太网群组的方法和设备
US9066163B2 (en) Optical transmission device including a bit rate adjustment function
US8625419B2 (en) Method and device for adjusting transmission of transport network data
WO2019114544A1 (zh) 一种数据传送的方法、设备和系统
AU2010230712A1 (en) Method and Device for Sending Data and Receiving Service Data
WO2019170064A1 (zh) 光网络中以太数据处理的方法、装置和系统
EP2472803B1 (en) Method, apparatus, system for hybrid-transmitting and bridging of circuit service and packet service
WO2019047110A1 (zh) 一种光传送网中时延测量的方法、装置和系统
CN102843293A (zh) 一种处理报文的方法和网元设备
WO2022194290A1 (zh) 光网络中以太数据处理的方法、装置以及系统
EP2579520A1 (en) Bandwidth allocation method and device for realizing bandwidth allocation
CN101965701B (zh) 任意速率的客户机信号的双重异步映射
US8699524B2 (en) Method and apparatus for generating resize control overhead in optical transport network
WO2021218721A1 (zh) 业务处理的方法和装置
JP2008236691A (ja) ＥｏＳ（ＥｔｈｅｒｏｖｅｒＳＯＮＥＴ）通信装置
JP2013258471A (ja) 伝送装置及び伝送方法
JP2002176408A (ja) マルチフレーム多重伝送装置
WO2021213225A1 (zh) 一种信号帧的处理方法及相关设备
CN118157809A (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: 22770642

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22770642

Country of ref document: EP

Kind code of ref document: A1