WO2020221141A1 - 光传送网中的数据传输方法及装置 - Google Patents

光传送网中的数据传输方法及装置 Download PDF

Info

Publication number
WO2020221141A1
WO2020221141A1 PCT/CN2020/086831 CN2020086831W WO2020221141A1 WO 2020221141 A1 WO2020221141 A1 WO 2020221141A1 CN 2020086831 W CN2020086831 W CN 2020086831W WO 2020221141 A1 WO2020221141 A1 WO 2020221141A1
Authority
WO
WIPO (PCT)
Prior art keywords
service data
payload
frame
type
service
Prior art date
Application number
PCT/CN2020/086831
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 EP20798158.0A priority Critical patent/EP3955479A4/en
Publication of WO2020221141A1 publication Critical patent/WO2020221141A1/zh
Priority to US17/513,438 priority patent/US11967992B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/27—Arrangements for networking
    • 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/03—Protocol definition or specification 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J14/00—Optical multiplex systems
    • H04J14/08—Time-division multiplex systems
    • 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]
    • 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/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • 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
    • 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/0089—Multiplexing, e.g. coding, scrambling, SONET
    • H04J2203/0091—Time slot assignment

Definitions

  • This application relates to the field of optical communication technology, and in particular to a data transmission method and device in an optical transport network.
  • the sender can map the service data to the payload area of the optical payload unit k (OPUk) frame, and then add OPUk overhead and optical data unit to the payload area of the OPUk frame k (optical data unit-k, ODUk) overhead to obtain an ODUk frame; then, add optical transport unit k (optical transport unit-k, OTUk) overhead to the ODUk frame to obtain the OTUk frame, and finally, send the OTUk to the receiving end frame.
  • the bit rate that is, the transmission rate
  • the bit rate of the OTU2 frame is 10 gigabit (Gbit)/second (s); the bit rate of the OTU4 frame is 100 Gbit/s.
  • OTN equipment uses time division multiplexing technology for data transmission. For example, divide the OTN frame into multiple 1.25G time slots. Based on this, during data transmission, the sender first determines the number of time slots to be occupied according to the bit rate of the service data. For example, for an ODU2 frame divided into 8 1.25G time slots, if the service data rate is 3Gbit/s, the service data occupies 3 1.25G time slots. Then allocate the occupied idle time slot to the service data. In fact, the service data does not fully utilize the occupied bandwidth of the 3 time slots, resulting in a waste of 0.75G bandwidth. When multi-channel service data is mixedly transmitted, each service occupies a fixed number of time slots. In reality, not all services can fully utilize the occupied time slot bandwidth, which will cause more bandwidth waste and result in bandwidth Low utilization rate.
  • the embodiments of the present application provide a data transmission method and device in an optical transport network (OTN), which help reduce bandwidth waste, thereby improving bandwidth resource utilization.
  • OTN optical transport network
  • an embodiment of the present application provides a data transmission method in OTN, including: mapping first-type service data to a payload block at a specific position among multiple consecutive payload blocks; wherein the multiple consecutive payload blocks The payload block occupies the payload area of the ODU frame.
  • the second type of service data is mapped to a payload block at any location in the plurality of consecutive payload blocks except the payload block at the specific location. Specifically, the second type of service data is mapped to any unoccupied payload block in the plurality of consecutive payload blocks except the payload block at the specific location.
  • the ODU frame is mapped to an OTU frame or a flexible OTN (FlexO) frame. Then, the OTU frame or FlexO frame is sent.
  • the second type of service data can be mapped to any unoccupied location in the unspecified location, when multiple channels of the second type of service data need to be transmitted, the payload block of the unspecified location can be shared, thereby helping to reduce bandwidth resources The waste of bandwidth and improve the utilization of bandwidth resources.
  • the ODU payload area is directly divided into multiple bearer periods, and a bearer period includes n consecutive payload blocks, eliminating the concept of time slots.
  • the embodiment of the present application does not limit the value of n, for example, n ⁇ 100, or n ⁇ 200.
  • n 100, 200, 500, or 1000, etc.
  • n can be infinite, and accordingly, the rate of a single payload block can be infinitely small.
  • one or more payload blocks can be formed into a flexible tributary unit, so that the rate of the formed flexible tributary unit and the service rate are as completely consistent as possible. This helps each channel of business data occupy the most suitable bandwidth, thereby minimizing bandwidth waste and greatly improving bandwidth resource utilization.
  • the first type of service data includes time division multiplexing (TDM) service data.
  • the second type of service data includes at least one of fixed rate packet (PKT-CBR) service data and variable rate packet (PKT-VBR) service data.
  • the first type of service data includes at least one of TDM service data and PKT-CBR service data.
  • the second type of service data includes PKT-VBR service data.
  • the multiple consecutive payload blocks are a bearer period.
  • the first type of business data includes first business data.
  • the position of the payload block occupied by the first service data in the first bearer period is the same as the position of the payload block occupied by the second bearer period.
  • the first bearing period and the second bearing period may be any two bearing periods.
  • the multiple consecutive payload blocks are a bearer period.
  • the second type of business data includes second business data.
  • the location of the payload block occupied by the second service data in the first bearer period is different from the location of the payload block occupied by the second bearer period. That is to say, the embodiment of the present application supports the same channel of type 2 service data occupying different positions of the payload block in different bearer periods. In this way, it is helpful to realize that multiple channels of the second type of service data share the payload block of the non-specific position in the bearer cycle.
  • the first bearing period and the second bearing period may be any two bearing periods.
  • the payload blocks at a specific location are evenly distributed among the multiple consecutive payload blocks.
  • the first type of service data is a service that requires high clock performance, such as a TDM service
  • the clock transparent transmission requirement can be met, thereby ensuring that the service clock recovered by the receiving end meets the performance requirement.
  • the payload block carrying the first type of service data carries the tributary port identifier of the first type of service data. In this way, it helps the receiving end to identify the first type of service data.
  • the payload block carrying the second type of service data carries the tributary port identifier of the second type of service data. In this way, it is helpful for the receiving end to recognize the second type of service data.
  • the branch port identifier of the service data may also be called the identifier of the service data.
  • the method further includes: sending the first information.
  • the first information is used to indicate the position of the payload block at a specific location in the multiple consecutive payload blocks. In this way, it is helpful for the receiving end to identify the payload block at a specific location, thereby identifying the first type of service data.
  • the first information is carried in the OPU overhead or the ODU overhead included in the ODU frame.
  • mapping the first type of service data to the payload block at a specific position in the plurality of consecutive payload blocks includes: mapping the first type of service data to the first service frame. Then, the first service frame is mapped to the payload block at a specific location. In this way, it is helpful for end-to-end management of business data and improving the quality of service delivery.
  • mapping the second type of service data to the payload block at any position in the plurality of consecutive payload blocks except for the payload block at a specific location includes: mapping the second type of service data Map to the second service frame. Then, the second service frame is mapped to a payload block at any position among the plurality of consecutive payload blocks except for the payload block at the specific position. Specifically, the second service frame is mapped to an unoccupied arbitrary position of the payload block except for the specific position of the plurality of consecutive payload blocks. In this way, it is helpful for end-to-end management of business data and improving the quality of service delivery.
  • the business frame includes overhead and payload.
  • the overhead includes (or is used to carry) mapping information, and the mapping information is used to characterize the mapping rules used when mapping service data to the service frame.
  • the payload includes (or is used to carry) service data.
  • the size of the first service frame is equal to an integer multiple of the size of the payload block. In this way, it helps to reduce the complexity of mapping business data, thereby reducing equipment costs.
  • the size of the first service frame is equal to the size of one payload block. In this way, it helps to further reduce the complexity of mapping business data, thereby further reducing equipment costs.
  • the size of the second service frame is equal to an integer multiple of the size of the payload block. In this way, it helps to reduce the complexity of mapping business data, thereby reducing equipment costs.
  • the size of the second service frame is equal to the size of one payload block. In this way, it helps to further reduce the complexity of mapping business data, thereby further reducing equipment costs.
  • the method further includes: sending the second information.
  • the second information is used to indicate the position of the first payload block of the multiple consecutive payload blocks in the payload area of the ODU frame.
  • the receiving end can determine the starting position of the bearer period in the payload area of the ODU frame based on the second information, thereby quickly determining the continuous bearer period boundary. In other words, quickly identify the bearer period, or quickly determine the correspondence between the payload area of the ODU frame and the bearer period.
  • the second information is carried in the OPU overhead or the ODU overhead included in the ODU frame.
  • the method before mapping the first type of service data to the payload block at a specific position among the multiple consecutive payload blocks, the method further includes: according to the bit rate of the first type of service data and the single net The bit rate of the payload block determines the number of payload blocks at a specific location. Then, according to the determined number of payload blocks at the specific location, the location of the payload block at the specific location in the plurality of consecutive payload blocks is determined.
  • n is an integer greater than or equal to 2.
  • the first type of service data includes third service data and fourth service data.
  • mapping the first type of service data to the payload block at a specific position among the multiple consecutive payload blocks includes: mapping the third service data to the first integer of the multiple consecutive payload blocks The payload block at a specific location.
  • the fourth service data is mapped to a second integer number of payload blocks at specific positions in the plurality of consecutive payload blocks.
  • the third service data and the fourth service data may be any two channels of service data in the first type of service data.
  • the first integer and the second integer may be equal or not equal. It can be seen that the embodiment of the present application supports mixed transmission of the second type of service data and multiple channels of the first type of service data.
  • the second type of service data includes fifth service data and sixth service data.
  • mapping the second type of service data to a payload block at any position among multiple consecutive payload blocks except for the payload block at a specific position includes: according to the fifth service data and the sixth service data At least one of the priority order and polling mode, the fifth service data and the sixth service data are mapped to any position of the plurality of consecutive payload blocks except the specific location of the payload block Payload block.
  • the fifth service data and the sixth service data may be any two channels of service data in the first type of service data. It can be seen that the embodiment of the present application supports mixed transmission of the first type of service data and multiple channels of the second type of service data.
  • an embodiment of the present application provides a data transmission method in OTN, including: receiving an OTU frame or a FlexO frame. Then, demap the OTU frame or FlexO frame to obtain the ODU frame. Among them, the payload block at a specific position among multiple consecutive payload blocks in the payload area of the ODU frame carries the first type of service data. In addition, the payload blocks of the plurality of consecutive payload blocks except the payload block at the specific position carry the second type of service data. Then, the first type of service data and the second type of service data are obtained from the multiple consecutive payload blocks.
  • the first type of service data includes TDM service data.
  • the second type of service data includes at least one of PKT-CBR service data and PKT-VBR service data.
  • the first type of service data includes at least one of TDM service data and PKT-CBR service data.
  • the second type of service data includes PKT-VBR service data.
  • the multiple consecutive payload blocks are a bearer period.
  • the first type of business data includes first business data.
  • the position of the payload block occupied by the first service data in the first bearer period is the same as the position of the payload block occupied by the second bearer period.
  • the multiple consecutive payload blocks are a bearer period.
  • the second type of business data includes second business data. The location of the payload block occupied by the second service data in the first bearer period is different from the location of the payload block occupied by the second bearer period.
  • the payload block at the specific location is evenly distributed among the multiple consecutive payload blocks.
  • obtaining the first type of service data from the multiple consecutive payload blocks includes: taking the service data carried in the first target payload block as the first type of service data.
  • the first target payload block is a payload block of the plurality of consecutive payload blocks that carries the tributary port identifier of the first type of service data.
  • obtaining the second type of service data from the multiple consecutive payload blocks includes: using the service data carried in the second target payload block as the second type of service data.
  • the second target payload block is a payload block of the plurality of consecutive payload blocks that carries the tributary port identifier of the second type of service data.
  • the method further includes: receiving the first information.
  • the first information is used to indicate the position of the payload block at the specific location in the multiple consecutive payload blocks.
  • obtaining the first type of service data from multiple consecutive payload blocks includes: taking the service data carried in the third target payload block as the first type of service data.
  • the third target payload block is a payload block located in the position indicated by the first information among the multiple consecutive payload blocks.
  • the first information is carried in the OPU overhead or the ODU overhead included in the ODU frame.
  • the method further includes: determining the number of payload blocks at the specific location according to the bit rate of the first type of service data and the bit rate of a single payload block. Then, according to a predefined rule, the position of the payload block at the specific location in the plurality of consecutive payload blocks is determined. Based on this, acquiring the first type of service data from the multiple consecutive payload blocks includes: using the service data carried in the fourth target payload block as the first type of service data.
  • the fourth target payload block is a payload block in the plurality of consecutive payload blocks and located at a position determined according to the predefined rule.
  • obtaining the first type of service data from the multiple consecutive payload blocks includes: demapping the multiple consecutive payload blocks to obtain the first service frame. Then, the service data obtained by demapping the first service frame is used as the first type of service data.
  • obtaining the second type of service data from the multiple consecutive payload blocks includes: demapping the multiple consecutive payload blocks to obtain the second service frame. Then, the service data obtained by demapping the second service frame is used as the second type of service data.
  • the service frame (such as the first service frame or the second service frame) includes overhead and payload.
  • This overhead includes mapping information.
  • the mapping information is used to characterize the mapping rules used when mapping service data to the service frame.
  • the payload includes business data.
  • the size of the first service frame is equal to an integer multiple of the size of the payload block.
  • the size of the first service frame is equal to the size of one payload block.
  • the size of the second service frame is equal to an integer multiple of the size of the payload block.
  • the size of the second service frame is equal to the size of one payload block.
  • the method further includes: receiving second information, the second information being used to indicate the position of the first payload block of the plurality of consecutive payload blocks in the payload area of the ODU frame . Then, according to the second information, the position of the first payload block in the payload area of the ODU frame is determined.
  • the second information is carried in the OPU overhead or the ODU overhead included in the ODU frame.
  • the first type of service data includes third service data and fourth service data.
  • obtaining the first type of service data from the multiple consecutive payload blocks includes: taking the service data carried on the first integer number of specific positions of the multiple consecutive payload blocks as the first Three service data; and, taking the service data carried on the second integer number of the specific location payload block in the plurality of consecutive payload blocks as the fourth service data.
  • an embodiment of the present application provides a data transmission device in an OTN, which can be used to implement the foregoing first aspect or any method provided by any possible design of the first aspect.
  • the device can be an OTN device or chip.
  • the device may be divided into functional modules according to the method provided in the first aspect or any of the possible designs of the first aspect.
  • each functional module may be divided corresponding to each function, or Integrate two or more functions into one processing module.
  • the device may include a memory and a processor.
  • the memory is used to store computer programs.
  • the processor is used to invoke the computer program to execute the first aspect or any one of the possible designs provided in the first aspect.
  • the sending step in the first aspect or the corresponding possible design of the first aspect may be an output step executed by the processor in this possible design.
  • the processor may be used to call a computer program stored in the memory to perform the following steps: First, map the first type of service data to a payload at a specific location in a plurality of consecutive payload blocks Piece. Wherein, the multiple consecutive payload blocks occupy the payload area of the ODU frame.
  • the second type of service data is mapped to a payload block at any position in the plurality of consecutive payload blocks except for the payload block at the specific location. Then, map the ODU frame to the OTU frame or FlexO frame. Then, output the OTU frame or FlexO frame.
  • an embodiment of the present application provides a data transmission device in an OTN, which can be used to implement the foregoing second aspect or any method provided by any possible design of the second aspect.
  • the device can be an OTN device or chip.
  • the device can be divided into functional modules according to the method provided by the second aspect or any of the possible designs of the second aspect.
  • each functional module can be divided corresponding to each function, or Integrate two or more functions into one processing module.
  • the device may include a memory and a processor, and the memory is used to store a computer program.
  • the processor is used to invoke the computer program to execute the second aspect or any one of the possible designs provided by the second aspect.
  • the embodiments of the present application provide a computer-readable storage medium, such as a non-transitory computer-readable storage medium.
  • a computer program (or instruction) is stored thereon, and when the computer program (or instruction) runs on a computer, the computer executes any method provided by the first aspect or any possible design of the first aspect .
  • embodiments of the present application provide a computer-readable storage medium, such as a computer-readable storage medium that is non-transitory.
  • a computer program (or instruction) is stored thereon, and when the computer program (or instruction) runs on a computer, the computer executes any method provided by the second aspect or any possible design of the second aspect .
  • the embodiments of the present application provide a computer program product, which when running on a computer, enables any method provided in the first aspect or any one of the possible designs of the first aspect to be executed.
  • the embodiments of the present application provide a computer program product that, when it runs on a computer, enables any method provided in the second aspect or any possible design of the second aspect to be executed.
  • any of the data transmission devices, computer storage media, or computer program products in the OTN provided above can be applied to the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to The beneficial effects of the corresponding method will not be repeated here.
  • FIG. 1 is a schematic diagram of a network architecture applicable to embodiments of the present application
  • FIG. 2 is a schematic diagram of the hardware structure of an OTN device applicable to an embodiment of the present application
  • FIG. 3 is a schematic diagram of a frame structure of an OTUk frame (k ⁇ Cn) applicable to an embodiment of the present application;
  • 5A is a schematic diagram of the correspondence between n consecutive payload blocks and the payload area of an ODU frame provided by an embodiment of this application;
  • 5B is a schematic diagram of another correspondence between n consecutive payload blocks and the payload area of an ODU frame provided by an embodiment of this application;
  • FIG. 6 is a schematic diagram of interaction of a data transmission method in an optical transport network provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of service data mapping provided based on FIG. 6 according to an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of an ODU frame provided by an embodiment of this application.
  • FIG. 9 is a schematic diagram of interaction of another data transmission method in an optical transport network provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram of a service data mapping provided based on FIG. 9 according to an embodiment of the application.
  • FIG. 11 is a schematic diagram of interaction of another data transmission method in an optical transport network provided by an embodiment of the application.
  • FIG. 12 is a schematic diagram of a service data mapping provided based on FIG. 11 according to an embodiment of the application.
  • FIG. 13 is an interactive schematic diagram of another data transmission method in an optical transport network provided by an embodiment of this application.
  • FIG. 14 is a schematic structural diagram of another ODU frame provided by an embodiment of this application.
  • 15 is a schematic structural diagram of a data transmission device in an optical transport network provided by an embodiment of this application.
  • FIG. 16 is a schematic structural diagram of another data transmission device in an optical transport network provided by an embodiment of this application.
  • OTN optical networks
  • An OTN is usually formed by connecting multiple OTN devices through optical fibers, and can be composed of different topologies such as linear, ring, and mesh according to specific needs.
  • FIG. 1 shows a schematic diagram of a network architecture applicable to embodiments of the present application.
  • the OTN shown in FIG. 1 includes two OTN networks (OTN network 1 and OTN network 2 respectively).
  • Each OTN network includes a certain number of OTN devices (indicated by N in FIG. 1).
  • the links between devices in the OTN network are intra-domain links, and the links between devices between OTN networks are inter-domain links.
  • an OTN device may have one or more functions.
  • OTN equipment is divided into optical layer equipment, electrical layer equipment, and photoelectric hybrid equipment.
  • Optical layer equipment refers to equipment capable of processing optical layer signals, such as optical amplifier (optical amplifier, OA).
  • Electrical layer equipment refers to equipment capable of processing electrical layer signals, for example: equipment capable of processing ODU signals.
  • Optoelectronic hybrid equipment refers to equipment capable of processing optical layer signals and electrical layer signals. It should be noted that, according to specific integration needs, one OTN device can integrate multiple different functions. The technical solution provided in this application is applicable to OTN equipment of different forms and integration levels.
  • FIG. 2 shows a schematic diagram of the hardware structure of an OTN device applicable to the embodiments of the present application.
  • an OTN device includes power supplies, fans, auxiliary boards, and may also include tributary boards, circuit boards, crossover boards, and system control and communication boards.
  • the circuit boards may also include optical layer processing boards. .
  • the type and number of boards contained in each device may be different.
  • a network device as a core node may not have a tributary board.
  • a network device as an edge node may have multiple tributary boards.
  • the power supply is used to supply power for OTN equipment, and may include main and backup power supplies.
  • the fan is used to dissipate heat for the device.
  • Auxiliary boards are used to provide auxiliary functions such as external alarms or access to external clocks.
  • Tributary boards, cross-connect boards, and circuit boards are mainly used to process electrical layer signals of the OTN (referred to as OTN frames later).
  • the tributary board 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 can be divided into a client-side optical module and a signal processor.
  • the client-side optical module may be an optical transceiver for receiving and/or sending client signals.
  • the signal processor is used to implement the mapping and demapping processing of the client signal to the OTN frame.
  • the cross-connect board is used to implement the exchange of OTN frames and complete the exchange of one or more types of OTN frames.
  • the circuit board mainly realizes the processing of the OTN frame on the line side.
  • the circuit board can be divided into a line-side optical module and a signal processor.
  • the line-side optical module may be a line-side optical transceiver for receiving and/or sending OTN frames.
  • the signal processor is used to implement multiplexing and demultiplexing, or mapping and demapping processing of the OTN frame on the line side.
  • System control and communication boards are 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 boards. Unless otherwise specified, there can be one or more specific components (such as branch boards), and this application does not make any restrictions. It should be noted that the embodiments of the present application do not limit the types of boards included in the device, and the specific functional design and number of boards.
  • ODU frame such as ODUk frame
  • OTU frame such as OTUk frame
  • the OTN frame processed by the OTN device can adopt the frame format defined by the International Telecommunication Union-Telecommunication Standard Sector (ITU-T).
  • ITU-T International Telecommunication Union-Telecommunication Standard Sector
  • the existing standards have defined multiple rate OTN frames, such as OPUk frames, ODUk frames, and OTUk frames.
  • k 0, 1, 2, 3, 4, Cn and flex respectively indicate that the bit rate is 1.25Gbit/s, 2.5Gbit/s, 10Gbit/s, 40Gbit/s, 100Gbit/s, n*100Gbit/s and n*1.25Gbit/s (n ⁇ 2).
  • the bit rates mentioned above are approximate values.
  • the bit rate of the OPU4 frame is more accurately 104.35597533 Gbit/s. Other examples will not be listed one by one.
  • an OTUk frame has 4 rows*4080 columns.
  • the OPUk payload area and OPUk overhead area i.e. OPUk OH
  • the OPUk frame and ODUk overhead area i.e. ODUk OH
  • ODUk frame, OTUk overhead area i.e. OTUk OH
  • frame alignment signal The frame alignment signal (FAS) and forward error correction (forward error correction, FEC) check areas constitute an OTUk frame.
  • columns 1-7 in the first row of the OTUk frame are FAS and multiframe alignment signal (MFAS)
  • columns 8-14 in the first row are OTUk OH
  • rows 1 to 2-4 Column 14 is ODUk OH
  • columns 15-16 in rows 1 to 4 are OPUk OH
  • columns 17 to 3824 in rows 1 to 4 are OPUk payload areas
  • columns 3825 to 4080 in rows 1 to 4 are FEC check Area.
  • the OTUCn frame is composed of n OTUC instance frames (denoted as OTUC#1 to OTUC#n in Fig. 4), and C indicates that the bit rate is 100 Gbit/s.
  • the OTUC instance frame does not include the FEC check area.
  • An OTUCn frame includes an OPUCn frame (that is, columns 15 to 3824 in an OTUCn frame), and an OPUCn frame is composed of n OPUC instance frames (that is, columns 15 to 3824 in an OTUC instance frame).
  • the payload area of the OPUCn frame may be formed by interleaving the payload areas of n OPUC instance frames according to a certain number of bytes.
  • the OTUC instance frame refers to the basic frame unit that constitutes the OTUCn frame, and may also be called the OTUC basic frame or other names, and this application does not make any limitation on this.
  • the payload block is located in the payload area of the ODU frame, and is composed of one byte or multiple consecutive bytes, or multiple consecutive bits.
  • the size of a payload block can be an integer multiple of bytes, or an integer multiple of 8 bytes, such as 64 bytes, 128 bytes, 192 bytes, or 256 bytes.
  • the sizes of different payload blocks are the same, and the following specific examples are all described as examples.
  • the payload block may also be called a code block or other names, which is not limited in this application.
  • a payload block is the smallest unit (also referred to as the smallest tributary unit) that carries service data.
  • the rate of a payload block can be arbitrarily small. Multiple payload blocks can be combined as a flexible tributary unit for carrying service data at a corresponding rate.
  • the two consecutive bytes mentioned in this application may be two adjacent bytes in the same row of the payload area of an ODU frame. Or, it may be the last byte in a row of the payload area of an ODU frame and the first byte in the next row of the row. Or, it may also be the last byte in the payload area of an ODU frame and the first byte in the payload area of the next ODU frame of the ODU frame.
  • "Byte" can be replaced with "bit".
  • a payload block can be located in the same row in the payload area of an ODU frame, or it can cross rows; it can also cross the payload area of the ODU frame.
  • n is an integer greater than or equal to 2.
  • the embodiment of the present application does not limit the specific value of n.
  • the n consecutive payload blocks may be located in the payload area of one ODU frame, or may span the payload areas of multiple ODU frames. When n consecutive payload blocks are located in the payload area of an ODU frame, they may be located in one row in the payload area or across multiple rows.
  • n consecutive payload blocks occupy an integer multiple of the payload area of the ODU frame.
  • n consecutive payload blocks occupy the payload area of one ODU frame or the payload area of two ODU frames.
  • Fig. 5A shows a type of n consecutive payload blocks occupying the payload area of 2 ODU frames.
  • n consecutive payload blocks occupy the payload area of a non-integer multiple of ODU frames.
  • n consecutive payload blocks occupy 0.4 ODU frame payload area or 1.5 ODU frame payload area, etc.
  • Fig. 5B shows a kind of n consecutive payload blocks occupying the payload area of 1.5 ODU frames.
  • FIG. 5A and 5B both take the ODUk frame contained in the OTUk frame shown in FIG. 3 as an example.
  • a and b are schematic diagrams of the structure of the j-th ODUk frame and the j+1-th ODUk frame, and j is an integer greater than or equal to 1;
  • Figure c is a schematic diagram of n consecutive payload blocks (shown in shaded areas) and the overhead area (ie, OH) corresponding to the n consecutive payload blocks.
  • the overhead area in figure c corresponds to (i.e.
  • the payload block shown by the "slash shade” in the n consecutive payload blocks corresponds to ( That is, occupying) the payload area of the ODU frame in figure a (as shown by the oblique line shading in figure a), the payload block shown by the "square shade” in the n consecutive payload blocks corresponds to (ie Occupation) The payload area of the ODU frame in figure b (as shown by the shaded squares in figure b).
  • this application supports loose coupling of n consecutive payload blocks with the payload area of the ODU frame.
  • the embodiment of the present application may not limit the relationship between the size of n consecutive payload blocks and the size of the payload area of the ODU frame.
  • the transmission sequence of the service data carried in the first to nth payload blocks in n consecutive payload blocks is the same as the payload area of the ODU frame occupied by the n consecutive payload blocks.
  • the transmission sequence of the service data carried in the data is the same.
  • the service data carried in the payload area of an ODU frame is transmitted in the order of its position in the payload area "from top to bottom, from left to right". For example, with reference to Figure 3, the service data mapped to the first row, columns 17 to 3824, row 2, columns 17 to 3824, row 3, columns 17 to 3824, and row 4, columns 17 to 3824 are transmitted sequentially.
  • n consecutive payload blocks are referred to as one bearer period.
  • the bearer period can also be referred to as a transmission period, a mapping period, or a data intermediate frame.
  • the embodiment of the present application does not limit it.
  • the number of payload blocks included in each bearer period is the same.
  • the last payload block included in one bearer period and the first payload block included in the next bearer period of the bearer period are two adjacent payloads in the payload area of the ODU frame Piece. That is, multiple consecutive bearer periods occupy multiple consecutive bytes (or bits) in the payload area of one or more ODU frames.
  • the number (or index) of the payload block in each bearer period uses 1 to n.
  • the numbers #1 to #n are taken as examples for description, and the descriptions are unified here, and the details are not repeated below.
  • the first type of service data may include at least one of time division multiplexing (TDM) service data and fixed-rate packet-constants bit rate (PKT-CBR) service data.
  • TDM time division multiplexing
  • PTT-CBR fixed-rate packet-constants bit rate
  • the second type of service data may include at least one of PKT-CBR service data and packet-variable bit rate (PKT-VBR).
  • PKT-CBR service data and packet-variable bit rate (PKT-VBR).
  • PKT-VBR packet-variable bit rate
  • the PKT-CBR service data can be used as the first type of service data or the second type of service data.
  • the sending end and the receiving end can determine which business data is the first type of business data and which business data is the second type of business data based on predefined rules (such as the rules predefined by the protocol).
  • the technical solutions provided in the embodiments of the present application are used in scenarios where the foregoing two types of service data are mixedly transmitted. Specifically, it may be a hybrid transmission of one or more channels of type 1 service data, and one or more channels of type 2 service data.
  • the first to sixth service data described below all refer to one channel of service data. It is understandable that the business data from different customer sources are different channels of business data. In addition, the business data from the same customer source can also be divided into different channels of business data.
  • the business frame includes overhead and payload.
  • the overhead of the service frame can be used to monitor and manage the service data and carry mapping information.
  • the mapping information can be used to characterize the mapping rules used when mapping service data to service frames.
  • the overhead of a service frame includes but is not limited to service frame header indication, trail trace identifier (TTI), X bit-interleaved parity (BIP-X), backward error indication ( backward error indication (BEI), backward defect indication (BD), status indication (status, STAT), time stamp, sequence identification, mapping overhead, etc.
  • the payload of the service frame is used to carry service data.
  • the service frame may be an optical service unit (OSU).
  • first service frame and “second service frame” are introduced. They are used to carry (or map) the first type of service data and the second type of service data respectively.
  • the size of the first service frame and the size of the second service frame are both equal to an integer multiple of the size of the payload block. In this way, the complexity of mapping business data can be reduced, thereby reducing equipment costs. Or, the size of the first service frame and the size of the second service frame are both equal to the size of one payload block. In this way, it helps to further reduce the complexity of mapping business data, thereby further reducing equipment costs.
  • the size of a service frame may refer to the sum of the size of the overhead of the service frame and the size of the payload of the service frame. Or, the size of a service frame may refer to the size of the payload of the service frame.
  • the sending end refers to a device that sends service data in OTN
  • the receiving end refers to a device that receives service data in OTN. Both the sending end and the receiving end may be the OTN devices described above.
  • At least one (species) in the embodiments of the present application includes one (species) or more (species).
  • Multiple (species) means two (species) or more than two (species).
  • at least one of A, B and C includes: A alone, B alone, A and B simultaneously, A and C simultaneously, B and C simultaneously, and A, B and C simultaneously.
  • plural means two or more than two.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect. It can be understood that words such as “first” and “second” do not limit the quantity and execution order.
  • the order of execution of the two steps is in no particular order, including: executing one of the steps first and then executing the other step; or executing the other step during the execution of one step; or executing the two steps simultaneously Wait.
  • FIG. 6 a schematic diagram of interaction of a data transmission method in an optical transport network provided by an embodiment of this application.
  • “hybrid transmission of one type of first type service data and one path of type second service data, and the service data is directly mapped to the payload area of the ODU frame” is taken as an example for description.
  • the method shown in Figure 6 includes the following steps:
  • the sending end receives the first service data and the second service data.
  • the first business data belongs to the first type of business data
  • the second business data belongs to the second type of business data.
  • the sending end receives the first service data and the second service data from the customer source.
  • the sending end determines the number m of payload blocks occupied by the first service data in one bearer period according to the bit rate of the first service data and the bit rate of a single payload block.
  • m is an integer greater than or equal to 1.
  • m is a value obtained by rounding up the "value obtained by dividing the bit rate of the first service data by the bit rate of a single payload block".
  • n is an integer greater than or equal to 2.
  • the value of n can be arbitrarily configured according to specific conditions.
  • the value of b is related to the ODU frame type. For example, in an ODU2 frame, b is 10Gbit/s.
  • the value of the number n of payload blocks included in a bearer period can be pre-configured.
  • the bit rate a of a single payload block can be obtained by dividing the payload rate b of the ODU frame by n.
  • S103 The sending end determines the positions of m payload blocks used to carry the first service data.
  • the location of a payload block refers to the location of the payload block in the bearer period to which the payload block belongs.
  • the number (or index) of a payload block may be used to characterize the position of the payload block in the bearer period to which the payload block belongs.
  • the m payload blocks are m payload blocks at specific locations. This step can be understood as: the sending end determines the position patterns (or fixed position patterns) of the payload blocks of m specific positions.
  • the first type of service data is a service that requires high clock performance, such as a TDM service
  • the clock transparent transmission requirement can be met, thereby ensuring that the service clock recovered by the receiving end meets the performance requirement.
  • TDM services have a fixed bit rate and have their own clock performance requirements.
  • clock drift and jitter indicators, etc. which require the sending end to transmit service data to the receiving end at the original fixed bit rate of this type of service as much as possible in real time.
  • the payload blocks of the m specific positions are evenly distributed in a bearer cycle” helps the sending end to transmit service data to the receiving end at the original fixed bit rate of this type of service as much as possible in real time.
  • the sending end may determine the positions of the payload blocks of the m specific positions according to a predefined rule.
  • the predefined rule may be a predefined algorithm such as a sigma-delta algorithm.
  • the predefined rule may be a rule that both the sender and the receiver can know in advance, or a rule that the sender defines by itself but the receiver does not know in advance.
  • S104 The sending end maps the first service data and the second service data to the payload area of the ODU frame.
  • the sender maps the first service data to m specific positions of the payload block in the bearer period according to the fixed position pattern determined in S103.
  • the sender maps the second service data to any unoccupied payload block in the non-specific location of the payload block. For example, when the data volume of the second service data received by the sender reaches the size of one payload block, the sender maps these data to any unoccupied payload block among the payload blocks at the non-specific location.
  • the positions of the payload blocks carrying the first service data are the same in different carrying periods.
  • the positions of the payload blocks that carry the second service data may be the same or different in different bearing periods.
  • the number of payload blocks that carry the second service data may be the same or different.
  • the number of payload blocks occupied by the second service data may be determined based on the real-time traffic of the second service data. Suppose that in a certain bearer period, the traffic of the second service data is T; then, in the bearer period, the number of payload blocks that the second service data needs to occupy is at most T divided by the rate of a single payload block value.
  • FIG. 7 is a schematic diagram illustrating the mapping of the first service data and the second service data in 2 bearer cycles (that is, the first bearer cycle and the second bearer cycle). And, specifically, one bearer cycle is composed of 40 payload blocks (numbers are #1 to #40, respectively), and the numbers of the m payload blocks at specific positions are: #1, #11, #21, # 31 is an example for illustration. Referring to FIG. 7, in these two bearer periods, the first service data is mapped in the payload blocks numbered #1, #11, #21, and #31.
  • the second service data is mapped in the payload blocks numbered #5, #8, #23, #25, and in the second bearer cycle, the second service data is mapped in the number In the payload block #2, #5, #7, #28, and #40.
  • S105 The sending end adds OPU overhead and ODU overhead to the payload area of the ODU frame to obtain an ODU frame; and maps the ODU frame to an OTU frame or a flexible OTN (flexible OTN, FlexO) frame.
  • OTN flexible OTN, FlexO
  • ODU frame when the ODU frame is specifically an ODUk frame, and k ⁇ Cn:
  • OTU overhead and the like may be added to the ODU frame to obtain the OTU frame.
  • the ODU frame can be mapped to other high-order ODU frames first. For example, mapping the ODU1 frame to the ODU2 frame or ODU3 frame, etc. Then add OTU overhead and so on to the high-order ODU frame to obtain an OTU frame.
  • the ODUk (k ⁇ Cn) frame may be mapped to the ODUCn frame first, and OTU overhead etc. may be added to the ODUCn frame to obtain the OTUCn frame. Then, map the OTUCn frame into a FlexO frame.
  • S106 The transmitting end sends the OTU frame or FlexO frame.
  • the FlexO frame can be sent through the FlexO interface.
  • the service data received by the sending end first is sent first, and the service data received later is sent later.
  • the embodiment of this application does not limit the order in which the sending end receives and sends the service data. Based on this, in S104, when mapping the same channel of service data to the payload area of the ODU frame, the mapping can be performed based on the order of "top to bottom, left to right" in the payload area of the ODU frame.
  • S107 The receiving end demaps the received OTU frame or FlexO frame to obtain an ODU frame.
  • the service data carried in the ODU frame can refer to the above-mentioned mapping result of S104.
  • the receiving end identifies the bearer period according to the correspondence between the payload area of the ODU frame and the bearer period, and parses the payload blocks included in the bearer period to obtain the first service data and the second service data.
  • the correspondence between the payload area and the bearer period of the ODU frame may be predefined.
  • the correspondence between the two may be as shown in FIG. 5A or FIG. 5B.
  • Identifying the bearer period can be understood as: determining the position of a bearer period in the payload area of the ODU frame, such as which bytes (or bits) in the payload area of the ODU frame are occupied by a bearer period.
  • the sender may carry the tributary port identifier of the first service data in the payload block that carries the first service data (that is, the m payload blocks at specific locations). This step can occur during or after S104. Based on Manner 1, the receiving end may use the service data carried in the payload block of the tributary port identifier carrying the first service data in a bearer cycle as the first service data.
  • one channel of service data has a branch port identifier.
  • the branch port identifier of the service data can also be called the identifier of the service data.
  • the service data may be the first service data, or may also be the second to sixth service data described below.
  • the sending end can send the first information to the receiving end.
  • the first information is used to indicate the positions of the m specific positions of the payload blocks in the bearer period to which they belong.
  • the first information may be carried in the OPU overhead included in the ODU frame or in the ODU overhead.
  • the receiving end may use the service data carried in the payload block located in the position indicated by the first information in a bearer cycle as the first service data.
  • the MFAS in the OPU overhead in an ODU frame and the super-frame alignment signal (SFAS) can be used to indicate a bearer period The location of one of the payload blocks in.
  • SFAS super-frame alignment signal
  • MSI multiplex structure identifier
  • the MSI can also be used to indicate the tributary port identifier of the payload block at the corresponding location, so that the receiving end can identify based on the tributary port identifier which service data carried in the payload block at the corresponding location belongs to All the way business data.
  • MFAS is used to count ODU frames.
  • MFAS occupies 8 bits and is located in the first row and seventh column of the ODU frame.
  • the value of MFAS ranges from 0 to 255.
  • the MFAS value of each ODU frame is increased by 1. That is, if the value of MFAS carried in the i-th ODU frame is less than 255, the value of MFAS carried in the i+1-th ODU frame is increased compared to the value of MFAS carried in the i-th ODU frame Up 1.
  • i is an integer greater than or equal to 1. Based on this, 256 ODU frames can be regarded as a multi-frame period. Of course, the embodiment of the present application does not limit the number of ODU frames included in one multiframe period.
  • SFAS is used for MFAS counting.
  • SFAS is a newly defined field in the embodiment of this application.
  • the value of the SFAS carried by the ODU frames in the same multiframe period is the same. Taking the range of SFAS from 0 to 255 as an example, the value of SFAS is increased by 1 for each multi-frame period. That is to say, if the value of SFAS carried in the ODU frame in the j-th multiframe period is less than 255, the value of SFAS carried in the ODU frame in the j+1-th multiframe period is higher than that of the j-th multiframe period. The value of the SFAS carried in the ODU frame in the multiframe period is increased by 1.
  • the value of the SFAS carried in the ODU frame in the j-th multiframe period is equal to 255, the value of the SFAS carried in the ODU frame in the j+1th multi-frame period is 0.
  • j is an integer greater than or equal to 1.
  • MSI is used to indicate whether the payload block at the corresponding position in a bearer cycle (that is, the payload block jointly determined by MFAS and SFAS) is a payload block at a specific position.
  • MSI[MFAS*SFAS] indicates whether the MFAS*SFAS-th payload block of a bearer period is a payload block at a specific location.
  • the first bit is 1 of MSI indicates that the MFAS*SFAS-th payload block is a specific location
  • the first bit is 0 indicates that the MFAS*SFAS-th payload block is not a specific location.
  • the payload block is used to indicate whether the payload block at the corresponding position in a bearer cycle (that is, the payload block jointly determined by MFAS and SFAS) is a payload block at a specific position.
  • MSI[MFAS*SFAS] indicates whether the MFAS*SFAS-th payload block of a bearer period is a payload block at a specific location.
  • the 2nd to 8th bits may represent the tributary port identifier of the service data carried on the MFAS*SFASth payload block.
  • FIG. 8 it is a schematic diagram of the structure of an ODU frame provided based on this example.
  • the ODU frame shown in Figure 8 is drawn based on Figure 3.
  • the SFAS is located in the fourth row and the 16th column of the ODU frame as an example for description.
  • "Occupation" in Figure 8 can be understood as an occupation identifier, which is used to indicate whether the payload block at the MSI[MFAS*SFAS] location corresponding to the current ODU frame is a payload block at a specific location. It should be noted that the embodiments of this application do not limit the number of bits occupied by SFAS and MSI and the range of representation, and can be flexibly configured according to actual conditions.
  • Method 3 The receiving end can determine the position of the payload block of the m specific positions according to the same predefined algorithm (such as sigma-delta algorithm, or a self-defined algorithm of the receiving end and the sending end, etc.) as used by the sending end , Thereby taking the service data carried in the payload block at the determined position in a bearer cycle as the first service data. In this way, the sending end does not need to transmit the positions of the m specific-position payload blocks to the receiving end, which helps to reduce the complexity of data processing.
  • the same predefined algorithm such as sigma-delta algorithm, or a self-defined algorithm of the receiving end and the sending end, etc.
  • a part of the payload block carrying the first service data carries the tributary port identifier of the first service data.
  • the sending end indicates to the receiving end the position of another part of the payload block in the bearer period to which it belongs.
  • the network management or software defined network may also pre-configure the m payload blocks at specific locations for the sender and the receiver.
  • the network management and SDN are software functional modules, and the physical entity where they are located may be the above-mentioned sender or receiver, or a device independent of the above-mentioned sender and receiver. Both network management and SDN can be used to manage devices in OTN.
  • the sending end may carry the tributary port identifier of the second service data in the payload block carrying the second service data.
  • the receiving end may use the service data carried in the payload block of the tributary port identifier carrying the second service data in one bearer cycle as the second service data.
  • the first type of service data is mapped to a payload block at a specific position among a plurality of consecutive payload blocks
  • the second type of service data is mapped to the plurality of consecutive payload blocks
  • the second type of business data it can be mapped to any unoccupied location in the non-specific location. Therefore, when multiple channels of the second type of business data need to be transmitted, the payload block of the non-specific location can be shared, which helps In order to reduce the waste of bandwidth resources, thereby improving bandwidth resource utilization.
  • each bearer cycle is mapped to m payload blocks at specific locations. And, m specific positions are evenly distributed in one load cycle.
  • the first type of service data is a service that requires high clock performance, such as a TDM service
  • the clock transparent transmission requirement can be met, thereby ensuring that the service clock recovered by the receiving end meets the performance requirement.
  • FIG. 9 it is a schematic diagram of interaction of a data transmission method in an optical transport network provided by an embodiment of this application.
  • “hybrid transmission of multiple channels of type 1 service data and multiple channels of type 2 service data, and the service data is directly mapped to the payload area of the ODU frame” is taken as an example for description.
  • the method shown in Figure 9 includes the following steps:
  • the sending end receives third service data, fourth service data, fifth service data, and sixth service data.
  • the third service data and the fourth service data belong to the first type of service data
  • the fifth service data and the sixth service data belong to the second type of service data.
  • the third service data and the fourth service data are different channels of service data
  • the fifth service data and the sixth service data are different channels of service data.
  • one of the third service data and the fourth service data may be the same as the above-mentioned first service data.
  • the third service data and the fourth service data may also be the same as the above first service data.
  • one of the fifth service data and the sixth service data may be the same as the above-mentioned second service data.
  • the fifth service data and the sixth service data may also be different from the above-mentioned second service data.
  • S202 The sending end determines the number m1 of payload blocks occupied by the third service data in one bearer period according to the bit rate of the third service data and the bit rate of a single payload block. And according to the bit rate of the fourth service data and the bit rate of a single payload block, the number m2 of the payload blocks occupied by the fourth service data in one bearer period is determined. Both m1 and m2 are integers greater than or equal to 1. The value of m1 and the value of m2 can be equal or not equal.
  • the sending end determines the positions of m1 payload blocks for carrying the third service data and the positions of m2 payload blocks for carrying the fourth service data. That is to say, the fixed position patterns of the m1 specific positions of the payload blocks and the fixed position patterns of the m2 specific positions of the payload blocks are determined.
  • the m1 payload blocks at specific positions are evenly distributed in the carrying period.
  • the m2 payload blocks at specific locations are evenly distributed during the load cycle.
  • S204 The sender mixes and maps the third service data, fourth service data, fifth service data, and sixth service data to the payload area of the ODU frame (specifically, part or all of the payload area of one or more ODU frames) .
  • the sender maps the third service data to the m1 specific location payload block in the bearer cycle, and maps the fourth service data to the m2 specific location payload block in the bearer cycle Payload block.
  • the order of execution of these two steps can be in no particular order.
  • the sender maps the fifth service data and the sixth service data to any unoccupied payload blocks in the non-specific location payload blocks.
  • the order of execution of these two steps can be in no particular order. For example, when the data volume of the received fifth service data reaches the size of one payload block, the fifth service data is mapped to any unoccupied payload block among the payload blocks at the non-specific location. When the data volume of the received sixth service data reaches the size of one payload block, the sixth service data is mapped to any unoccupied payload block among the payload blocks at the non-specific location.
  • the sender can follow the priority order of the fifth service data and the sixth service data and/ Or in a polling manner, the fifth service data and the sixth service data are mapped to any unoccupied payload blocks in the non-specific location payload blocks.
  • the priority order of the fifth service data and the sixth service data may be pre-configured, and the polling manner may be according to the service identification order or the pre-configured order.
  • the positions of the payload blocks that carry the third service data are the same in different bearing periods.
  • the positions of the payload blocks that carry the fourth service data are the same in different bearing periods.
  • the positions of the payload blocks carrying the fifth service data and the sixth service data in different bearing periods may be the same or different.
  • FIG. 10 is a schematic diagram illustrating the mapping of the third to sixth service data in 2 bearer cycles (that is, the first bearer cycle and the second bearer cycle).
  • one bearer cycle is composed of 40 payload blocks (numbers are #1 to #40, respectively).
  • the numbers of the payload blocks at m1 specific positions are: #1, #11, #21 and #31.
  • the numbers of the payload blocks at m2 specific positions are #2, #10, #18, #26, #34, respectively.
  • the third service data is mapped in the payload blocks numbered #1, #11, #21, and #31, and the fourth service data is mapped in the payload blocks numbered #2, #10, #18, #26, and #34 in the payload block.
  • the fifth service data is mapped in the payload blocks numbered #5, #8, #23, and #25
  • the sixth service data is mapped in the payload block numbered #3 .
  • the fifth service data is mapped to the payload blocks numbered #5, #8, and #23, and the sixth service data is mapped to the payload blocks numbered #7, #9, and #12. in.
  • S205 ⁇ S207 Refer to S105 ⁇ S107 above.
  • the receiving end identifies the bearer period according to the correspondence between the payload area of the ODU frame and the bearer period. And analyze and obtain the third to sixth service data from the payload blocks included in the bearer period.
  • the service data carried on the payload blocks of the m1 specific positions in the bearer period is analyzed to obtain the third service data.
  • the specific implementation of these two steps can refer to the above-mentioned method for obtaining the first service data.
  • the method for the receiving end to parse and obtain the fifth service data and the sixth service data may refer to the above method for obtaining the second service data.
  • FIG. 11 it is a schematic diagram of interaction of a data transmission method in an optical transport network provided by an embodiment of this application.
  • “hybrid transmission of one type of first type service data and one path of type second service data, and the service data is indirectly mapped to the payload area of the ODU frame” is taken as an example for description.
  • the method shown in Figure 11 includes the following steps:
  • S301 to S303 Refer to S101 to S103 above.
  • S304 The sending end maps the first service data to the first service frame, and maps the second service data to the second service frame. And, the first service frame and the second service frame are mixed and mapped to the payload area of the ODU frame.
  • the first service data is mapped to the payload area of the first service frame, and the overhead of the first service frame is added to the overhead area of the service frame.
  • Map the second service data to the payload area of the second service frame, and add the overhead of the second service frame to the overhead area of the service frame.
  • the sender maps the first service frame to m specific location payload blocks in the bearer period according to the fixed position pattern determined in S303.
  • the second service frame is mapped to any unoccupied payload block in the non-specific location of the payload block.
  • FIG. 12 a schematic diagram of service data mapping provided by an embodiment of this application.
  • the service data targeted in FIG. 12 may be the first service data or the second service data.
  • the service data is first mapped to the payload area of a service frame, and then the service frame is mapped to the payload area of the ODU frame.
  • the payload area of the ODU frame is specifically a bearer period as an example for illustration.
  • the embodiment of the present application does not limit the specific implementation manner in which the sending end maps the first type of service data (such as the first service data) to the service frame.
  • first type of service data such as the first service data
  • synchronous mapping or asynchronous mapping can be performed.
  • a generic mapping procedure generator mapping procedure, GMP
  • other mapping methods may be used to map the first type of service data to the service frame.
  • the embodiment of the present application does not limit the specific implementation manner for the sending end to map the second type of service data (such as the second service data) to the service frame.
  • synchronous mapping or asynchronous mapping may be performed.
  • GMP generic frame procedure-framing (GFP-F), idle mapping procedure (IMP), or other mapping methods may be used to map the second type of service data to service frames.
  • GMP generic frame procedure-framing
  • IMP idle mapping procedure
  • S305 to S307 Refer to S105 to S107 above.
  • the receiving end identifies the bearer period according to the correspondence between the payload area of the ODU frame and the bearer period. And analyze and obtain the first service frame and the second service frame from the bearer period. Then, demap the first service frame to obtain the first service data. The second type of business data is demapped to obtain the second business data.
  • the receiving end may use the service frame mapped in the payload block of the tributary port identifier carrying the first service data in a bearer period as the first service frame; or the receiving end may be located at the position indicated by the first information in a bearer period As the first service frame; or according to the same predefined algorithm (such as sigma-delta algorithm, etc.) used by the sender, determine the position of the m payload blocks at specific locations, so that the The service frame serves as the first service frame and so on.
  • the same predefined algorithm such as sigma-delta algorithm, etc.
  • the receiving end may use the service frame mapped in the payload block of the tributary port identifier carrying the second service data in one bearer cycle as the second service frame.
  • the service data is first mapped to the service frame, and then the service frame is mapped to the payload area of the ODU frame. In this way, it is helpful for end-to-end management of business data and improving the quality of service delivery.
  • FIG. 13 it is a schematic diagram of interaction of a data transmission method in an optical transport network provided by an embodiment of this application.
  • “hybrid transmission of multiple channels of type 1 service data and multiple channels of type 2 service data, and the service data is indirectly mapped to the payload area of the ODU frame” is taken as an example for description.
  • the method shown in Figure 13 includes the following steps:
  • S401 ⁇ S403 Refer to S201 ⁇ S203 above.
  • S404 The sender maps the third to sixth service data to the service frame, and maps the service frame to the payload area of the ODU frame. Among them, different road service data are mapped to different service frames.
  • the sender maps the service frame bearing the third service data to the m1 payload blocks at the specific location according to the fixed location pattern determined in S403. Map the service frame carrying the fourth service data to the m2 payload blocks at specific locations.
  • the order of execution of these two steps can be in no particular order.
  • the sender maps each service frame that bears the fifth service data or the sixth service data to any unoccupied payload block in the non-specific location of the payload block.
  • S405 ⁇ S407 Refer to S205 ⁇ S207 above.
  • the receiving end identifies the bearer period according to the correspondence between the payload area of the ODU frame and the bearer period.
  • the service frame is parsed from the bearer period, and then the service frame is demapped to obtain the third to sixth service data.
  • the receiving end may demap the service frame mapped in the payload block of the tributary port identifier carrying the third service data in a bearer cycle to obtain the third service data frame.
  • the receiving end may demap the service frame mapped in the payload block of the tributary port identifier carrying the fourth service data in one bearer cycle to obtain the fourth service data frame.
  • the receiving end may demap the service frame mapped in the payload block of the tributary port identifier carrying the fifth service data in a bearer cycle to obtain the fifth service data frame.
  • the receiving end may demap the service frame mapped in the payload block of the tributary port identifier carrying the sixth service data in one bearer cycle to obtain the sixth service data frame.
  • the sending end may send the second information to the receiving end.
  • the second information is used to indicate the position of the payload block of the target position in the payload area of the ODU frame in one bearer period.
  • the receiving end can determine the starting position of the bearer period in the payload area of the ODU frame based on the second information, thereby quickly determining the continuous bearer period boundary.
  • the target position in a bearer cycle may be a position pre-appointed by the sending end and the receiving end.
  • the target position in each bearing period is the same, of course, the target position in different bearing periods may also be different.
  • a common implementation manner may be that the payload block at the target position in each bearer cycle is the first payload block (or called the initial payload block) in the bearer cycle.
  • the second information is carried in the OPU overhead included in the ODU frame or in the ODU overhead, such as the OPU overhead included in the ODU frame where the payload block (such as the first payload block) carried at the target location is located Or ODU overhead.
  • a payload block start overhead (payload block start, PBS) can be defined.
  • the PBS can be placed in any reserved bit of the current OPU overhead area, and the number of bits occupied by the PBS can be flexibly set according to the total number of possible positions of the first payload block in a bearer period that needs to be indicated.
  • the PBS may be located in the lower 6 bits of the first row and the 15th column and all 8 bits of the 16 columns of the ODUk frame, a total of 14 bits, as shown in FIG. 14.
  • Figure 14 shows a schematic diagram of the structure of ODU frame #i ⁇ ODU frame #i+x (that is, the i-th ODU frame to the i+x-th ODU frame). Both i and x are integers greater than or equal to 1. 14 is drawn based on Figure 3.
  • a bearer period includes n payload blocks, and the numbers are #1 to #n in sequence, 1 ⁇ j ⁇ n, and j and n are integers.
  • the arrow shown by the dotted line in FIG. 14 is used to indicate that the PBS in the ODU frame #i indicates the position of the payload block numbered #1 in the ODU frame #i in the payload area of the ODU frame.
  • the value range of the 14-bit PBS can be expressed as a decimal number of 0-15232.
  • all 0s may be used to indicate that the first payload block in a bearer period is not in the payload area of the current ODU frame
  • 1-15232 may be used to indicate that the first payload block in a bearer period is in the current ODU frame.
  • the embodiment of the present application may divide the sending end or the receiving end into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 15 a schematic structural diagram of a data transmission device 150 in an OTN provided by an embodiment of this application.
  • the device 150 may be the sender mentioned above.
  • the device 150 may be used to execute the steps performed by the sending end in the method shown in FIG. 6, FIG. 9, FIG. 11, or FIG.
  • the device 150 includes a processing unit 1501 and a sending unit 1502.
  • the processing unit 1501 is configured to perform the following steps: map the first type of service data to a payload block at a specific position in a plurality of consecutive payload blocks; wherein the multiple consecutive payload blocks occupy the payload of the ODU frame Area.
  • the second type of service data is mapped to a payload block at any location in the plurality of consecutive payload blocks except the payload block at the specific location.
  • the sending unit 1502 is used to send the OTU frame or FlexO frame.
  • the processing unit 1501 is specifically configured to perform S104 to S105; the sending unit 1502 is specifically configured to perform S106.
  • the processing unit 1501 is specifically configured to perform S204 to S205; the sending unit 1502 is specifically configured to perform S206.
  • the processing unit 1501 is configured to execute S304 to S305; the sending unit 1502 is specifically configured to execute S306.
  • the processing unit 1501 is configured to execute S404 to S405; the sending unit 1502 is specifically configured to execute S406.
  • the sending unit 1502 is further configured to: send the first information.
  • the first information is used to indicate the position of the payload block at the specific location in the plurality of consecutive payload blocks. Specifically, the first information is placed in OPU overhead or ODU overhead.
  • the processing unit 1501 is specifically configured to: map the first type of service data to the first service frame, and map the first service frame to the payload block at the specific location. And/or, map the second type of service data to the second service frame, and map the second service frame to the payload at any position of the plurality of consecutive payload blocks except the payload block at the specific location.
  • the business frame includes overhead and payload.
  • the overhead includes mapping information, which is used to characterize the mapping rules used when mapping service data to service frames.
  • the payload includes business data.
  • the processing unit 1501 may be specifically configured to perform S304.
  • the processing unit 1501 may be specifically configured to perform S404.
  • the sending unit 1502 is further configured to send second information.
  • This information is used to indicate the position of the first payload block among multiple consecutive payload blocks in the payload area of the ODU frame.
  • the second information is placed in the OPU overhead or ODU overhead.
  • the processing unit 1501 is further configured to determine the number of payload blocks at the specific location according to the bit rate of the first type of service data and the bit rate of a single payload block. Then, according to the determined number of payload blocks at the specific location, the location of the payload block at the specific location in the plurality of consecutive payload blocks is determined.
  • the processing unit 1501 is specifically configured to execute S302 and S303.
  • the processing unit 1501 is specifically configured to execute S202 and S203.
  • the first type of service data includes third service data and fourth service data.
  • the processing unit 1501 is specifically configured to map the third service data to the first integer number of payload blocks at specific positions in the plurality of consecutive payload blocks. And, mapping the fourth service data to the second integer number of specific position payload blocks in the plurality of consecutive payload blocks.
  • the processing unit 1501 is specifically configured to perform the step of mapping the third and fourth service data in S204.
  • the processing unit 1501 is specifically configured to perform the step of mapping the third and fourth service data in S404.
  • the second type of service data includes fifth service data and sixth service data.
  • the processing unit 1501 is specifically configured to: according to at least one of the priority order of the fifth service data and the sixth service data, and the polling mode, map the fifth service data and the sixth service data to the multiple A payload block at any position among consecutive payload blocks except the one at the specific location.
  • the processing unit 1501 is specifically configured to perform the steps of mapping the fifth and sixth service data in S204.
  • the processing unit 1501 is specifically configured to perform the steps of mapping the fifth and sixth service data in S404.
  • FIG. 16 it is a schematic structural diagram of a data transmission device 160 in an OTN provided by an embodiment of this application.
  • the device 160 may be the above receiving end.
  • the device 160 can be used to execute the steps performed by the receiving end in the method shown in FIG. 6, FIG. 9, FIG. 11, or FIG.
  • the device 160 includes a receiving unit 1601 and a processing unit 1602.
  • the receiving unit 1601 is configured to receive OTU frames or FlexO frames.
  • the processing unit 1602 is configured to perform the following steps: demapping the OTU frame or FlexO frame to obtain an ODU frame.
  • the payload block at a specific position among multiple consecutive payload blocks in the payload area of the ODU frame carries the first type of service data.
  • the payload blocks of the plurality of consecutive payload blocks except the payload block at the specific location carry the second type of service data.
  • the first type of service data and the second type of service data are obtained from the multiple consecutive payload blocks.
  • the receiving unit 1601 is specifically configured to perform the receiving step corresponding to S106.
  • the processing unit 1602 may be specifically configured to execute S107 to S108.
  • the receiving unit 1601 is specifically configured to perform the receiving step corresponding to S206.
  • the processing unit 1602 is specifically configured to execute S207 to S208.
  • the receiving unit 1601 is specifically configured to execute the receiving step corresponding to S306.
  • the processing unit 1602 is specifically configured to execute S307 to S308.
  • the receiving unit 1601 is specifically configured to execute the receiving step corresponding to S406.
  • the processing unit 1602 is specifically configured to execute S407 to S408.
  • the processing unit 1602 is specifically configured to: use the service data carried in the first target payload block as the first type of service data.
  • the first target payload block is a payload block of the multiple consecutive payload blocks that carries the tributary port identifier of the first type of service data.
  • the second target payload block is a payload block of the plurality of consecutive payload blocks that carries the tributary port identifier of the second type of service data.
  • the receiving unit 1601 is further configured to receive the first information.
  • the first information is used to indicate the position of the payload block at the specific location in the multiple consecutive payload blocks.
  • the processing unit 1602 is specifically configured to: use the service data carried in the third target payload block as the first type of service data.
  • the third target payload block is a payload block located in the position indicated by the first information among the multiple consecutive payload blocks.
  • the first information is carried in OPU overhead or ODU overhead.
  • the processing unit 1602 is further configured to determine the number of payload blocks at the specific location according to the bit rate of the first type of service data and the bit rate of a single payload block. Then, according to a predefined rule, the position of the payload block at the specific location in the plurality of consecutive payload blocks is determined.
  • the processing unit 1602 is specifically configured to: use the service data carried in the fourth target payload block as the first type of service data.
  • the fourth target payload block is a payload block in the plurality of consecutive payload blocks and located at a position determined according to the predefined rule.
  • the processing unit 1602 is specifically configured to: demap the multiple consecutive payload blocks to obtain the first service frame and the second service frame.
  • the business frame includes overhead and payload.
  • the overhead includes mapping information, and the mapping information is used to characterize the mapping rules used when mapping the service data to the service frame.
  • the payload includes business data. Then, the service data obtained by demapping the first service frame is used as the first type of service data. The service data obtained by demapping the second service frame is used as the second type of service data.
  • the receiving unit 1601 is further configured to receive second information.
  • the second information is used to indicate the position of the first payload block of the multiple consecutive payload blocks in the payload area of the ODU frame. Then, according to the second information, the position of the first payload block in the payload area of the ODU frame is determined. Specifically, the second information is carried in OPU overhead or ODU overhead.
  • the first type of service data includes third service data and fourth service data.
  • the processing unit 1602 is specifically configured to: use the service data carried on the first integer number of specific positions of the plurality of consecutive payload blocks as the third service data. And, the service data carried on the second integer number of the specific location payload block in the plurality of consecutive payload blocks is used as the fourth service data.
  • each unit may be located in the circuit board in the OTN hardware structure diagram shown in FIG. 2. In this regard, this application is not restricted.
  • the aforementioned processing unit, sending unit, receiving unit, and communication unit may also be replaced with a processor, a transmitter, and a receiver.
  • the transmitting unit may be an optical module with only a transmitting function or with both functions of transmitting and receiving
  • the receiving unit may be an optical module with only a function of receiving or with both functions of transmitting and receiving.
  • the functions of the above multiple units are all executed by the processor. In this regard, this application is not restricted.
  • the processor described above can be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated in the processor, or located outside the processor and exist independently.
  • the embodiment of the present application also provides a chip.
  • the chip integrates a circuit and one or more interfaces for realizing the functions of the above-mentioned processor.
  • the chip is connected to the optical module through the interface, so that the optical module is used to send the OTU frame or FlexO frame mentioned in the above method embodiment to other communication devices, or receive other communications from the optical module OTU frame or FlexO frame sent by the device.
  • the chip is not integrated with memory, it can be connected to an external memory through this interface, and the chip implements the internal execution of the communication device (transmitting end or receiving end) in the above-mentioned embodiment according to the program code stored in the external memory.
  • the functions supported by the chip may include processing actions of the sending end or the receiving end in the embodiments described in FIG. 6, FIG. 9, FIG. 11, and FIG. 13, which will not be repeated here.
  • the program can be stored in a computer-readable storage medium.
  • the aforementioned storage medium may be a read-only memory, a random access memory, and the like.
  • the above-mentioned processing unit or processor may be a central processing unit, a general-purpose processor, an application specific integrated circuit (ASIC), a microprocessor (digital signal processor, DSP), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the embodiments of the present application also provide a computer program product containing instructions, which when the instructions are run on a computer, cause the computer to execute any one of the methods in the foregoing embodiments.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. Computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • computer instructions may be transmitted from a website, computer, server, or data center through a cable (such as Coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or may include one or more data storage devices such as a server or a data center that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the foregoing devices for storing computer instructions or computer programs provided in the embodiments of the present application are non-transitory. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Time-Division Multiplex Systems (AREA)

Abstract

本申请公开了光传送网中的数据传输方法及装置，涉及光通信技术领域，有助于减少带宽浪费，从而提高带宽资源利用率。该方法包括：将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块；其中，该多个连续的净荷块占用光数据单元(ODU)帧的净荷区；将第二类业务数据映射到该多个连续的净荷块中的除该特定位置的净荷块之外的任意位置的净荷块；将该ODU帧映射到光传输单元(OTU)帧或灵活OTN(FlexO)帧中；发送该OTU帧或FlexO帧。本申请公开的技术方案可以应用于混合传输业务数据的场景中。

Description

光传送网中的数据传输方法及装置
本申请要求于2019年04月30日提交国家知识产权局、申请号为201910365275.8、申请名称为“光传送网中的数据传输方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及光通信技术领域，尤其涉及一种光传送网中的数据传输方法及装置。
背景技术
在光传送网(optical transport network，OTN)中，发送端可以将业务数据映射到光净荷单元k(OPUk)帧的净荷区中，再为OPUk帧的净荷区添加OPUk开销和光数据单元k(optical data unit-k，ODUk)开销，得到ODUk帧；接着，为ODUk帧添加光传输单元k(optical transport unit-k，OTUk)开销等，得到OTUk帧，最后，向接收端发送该OTUk帧。其中，k取不同值时，OTUk帧的比特速率(即传输速率)不同。如OTU2帧的比特速率是10吉比特(Gbit)/秒(s)；OTU4帧的比特速率是100Gbit/s。
OTN设备采用时分复用技术进行数据传输。例如，将OTN帧划分为多个1.25G时隙。基于此，在进行数据传输时，发送端先根据业务数据的比特速率，确定其要占用的时隙数量。例如，对于划分了8个1.25G时隙的ODU2帧来说，若业务数据速率是3Gbit/s，则该业务数据占用3个1.25G时隙。然后将伟被占用的空闲时隙分配给该业务数据。而实际上该业务数据并未将所占用的3个时隙带宽完全利用，造成0.75G的带宽浪费。当多路业务数据混合传输时，每路业务都占用固定数量的时隙，实际情况并不是所有业务都能将所占用的时隙带宽完全利用，这样会造成更多的带宽浪费，从而造成带宽利用率低。
发明内容
本申请实施例提供了光传送网(OTN)中的数据传输方法及装置，有助于减少带宽浪费，从而提高带宽资源利用率。
第一方面，本申请实施例提供了一种OTN中的数据传输方法，包括：将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块；其中，该多个连续的净荷块占用ODU帧的净荷区。将第二类业务数据映射到该多个连续的净荷块中的除该特定位置的净荷块之外的任意位置的净荷块。具体地，将第二类业务数据映射到该多个连续的净荷块中的除该特定位置的净荷块之外的未被占用的任意位置的净荷块。然后，将该ODU帧映射到OTU帧或灵活OTN(FlexO)帧中。接着，发送该OTU帧或FlexO帧。由于第二类业务数据可以映射到非特定位置中未被占用的任意位置，因此，需要传输多路第二类业务数据时，可以共享非特定位置的净荷块，从而有助于减少带宽资源的浪费，提高带宽资源利用率。
本申请实施例提供的技术方案，可以理解为：将ODU净荷区直接划分为多个承载周期，一个承载周期包括n个连续的净荷块，消除了时隙概念。其中，本申请实施例对n的取值不进行限定，例如，n≥100，或n≥200等。例如，n＝100、200、500或1000等。 可选的，n可以取无限大，相应地，单个净荷块的速率可以无限小。可选的，可以将一个或多个净荷块构成灵活支路单元，使所构成的灵活支路单元的速率和业务速率尽量完全一致。这有助于每路业务数据占用到最合适的带宽，从而尽量减小带宽浪费，大大提高带宽资源利用率。
在一种可能的设计中，第一类业务数据包括时分复用(TDM)业务数据。第二类业务数据包括固定速率的分组(PKT-CBR)业务数据和可变速率的分组(PKT-VBR)业务数据中的至少一种。在另一种可能的设计中，第一类业务数据包括TDM业务数据和PKT-CBR业务数据中的至少一种。第二类业务数据包括PKT-VBR业务数据。
在一种可能的设计中，该多个连续的净荷块为一个承载周期。第一类业务数据包括第一业务数据。第一业务数据在第一承载周期中占用的净荷块的位置与在第二承载周期中占用的净荷块的位置相同。其中，第一承载周期和第二承载周期可以是任意的两个承载周期。这样，发送端不需要向接收端发送用于表示第一业务数据在每个承载周期中占用的净荷块的位置的信息，从而可以降低传输开销。
在一种可能的设计中，该多个连续的净荷块为一个承载周期。第二类业务数据包括第二业务数据。第二业务数据在第一承载周期中占用的净荷块的位置与在第二承载周期中占用的净荷块的位置不同。也就是说，本申请实施例支持同一路第二类业务数据在不同承载周期中占用不同位置的净荷块。这样，有助于实现多路第二类业务数据共享承载周期中的非特定位置的净荷块。其中，第一承载周期和第二承载周期可以是任意的两个承载周期。
在一种可能的设计中，特定位置的净荷块在该多个连续的净荷块中均匀分布。这样，当第一类业务数据是对时钟性能要求较高的业务如TDM类业务时，可以满足时钟透明传送需求，从而保证接收端恢复的业务时钟满足性能要求。
在一种可能的设计中，承载第一类业务数据的净荷块中携带第一类业务数据的支路端口标识。这样，有助于接收端识别出第一类业务数据。
在一种可能的设计中，承载第二类业务数据的净荷块中携带第二类业务数据的支路端口标识。这样，有助于接收端识别出第二类业务数据。
其中，业务数据的支路端口标识也可以被称作业务数据的标识。
在一种可能的设计中，该方法还包括：发送第一信息。该第一信息用于指示特定位置的净荷块在该多个连续的净荷块中的位置。这样，有助于接收端识别出特定位置的净荷块，从而识别出第一类业务数据。
在一种可能的设计中，第一信息携带在ODU帧所包括的OPU开销中或者ODU开销中。
在一种可能的设计中，将第一类业务数据映射到该多个连续的净荷块中特定位置的净荷块包括：将第一类业务数据映射到第一业务帧。然后，将第一业务帧映射到特定位置的净荷块。这样，有助于对业务数据进行端到端管理，提高业务传送质量。
在一种可能的设计中，将第二类业务数据映射到该多个连续的净荷块中的除特定位置的净荷块之外的任意位置的净荷块包括：将第二类业务数据映射到第二业务帧。然后，将第二业务帧映射到该多个连续的净荷块中的除特定位置的净荷块之外的任意位置的净荷块。具体地，将第二业务帧映射到该多个连续的净荷块中的除特定位置的净荷块之外的未被占用的任意位置的净荷块。这样，有助于对业务数据进行端到端管理，提高业务 传送质量。
其中，业务帧包括开销和净荷。开销包括(或用于承载)映射信息，该映射信息用于表征将业务数据映射到该业务帧时所采用的映射规则。净荷包括(或用于承载)业务数据。
在一种可能的设计中，第一业务帧的大小等于净荷块的大小的整数倍。这样，有助于降低业务数据的映射复杂度，从而降低设备成本。可选地，第一业务帧的大小等于一个净荷块的大小。这样，有助于进一步降低业务数据的映射复杂度，从而进一步降低设备成本。
在一种可能的设计中，第二业务帧的大小等于净荷块的大小的整数倍。这样，有助于降低业务数据的映射复杂度，从而降低设备成本。可选地，第二业务帧的大小等于一个净荷块的大小。这样，有助于进一步降低业务数据的映射复杂度，从而进一步降低设备成本。
在一种可能的设计中，该方法还包括：发送第二信息。该第二信息用于指示该多个连续的净荷块中的首个净荷块在ODU帧的净荷区中的位置。这样，接收端可以基于第二信息确定该承载周期在ODU帧的净荷区中的起始位置，从而快速确定连续的承载周期边界。或者说快速识别承载周期，或者说快速确定ODU帧的净荷区与承载周期之间的对应关系。
在一种可能的设计中，第二信息携带在ODU帧所包括的OPU开销中或者ODU开销中。
在一种可能的设计中，在将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块之前，该方法还包括：根据第一类业务数据的比特速率和单个净荷块的比特速率，确定特定位置的净荷块的数量。然后，根据所确定的所述特定位置的净荷块的数量，确定特定位置的净荷块在该多个连续的净荷块中的位置。
其中，单个净荷块的比特速率a、一个承载周期所包括的净荷块的数量n和ODU帧的净荷速率b之间满足公式a*n＝b。其中，n为大于等于2的整数。
在一种可能的设计中，第一类业务数据包括第三业务数据和第四业务数据。该情况下，将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块，包括：将第三业务数据映射到该多个连续的净荷块中的第一整数个特定位置的净荷块。将第四业务数据映射到该多个连续的净荷块中的第二整数个特定位置的净荷块。其中，第三业务数据和第四业务数据可以是第一类业务数据中的任意两路业务数据。第一整数和第二整数可以相等，也可以不相等。可见，本申请实施例支持第二类业务数据与多路第一类业务数据混合传输。
在一种可能的设计中，第二类业务数据包括第五业务数据和第六业务数据。该情况下，将第二类业务数据映射到多个连续的净荷块中的除特定位置的净荷块之外的任意位置的净荷块，包括：按照第五业务数据与第六业务数据的优先级顺序，以及轮询方式中的至少一种，将第五业务数据和第六业务数据映射到该多个连续的净荷块中的除特定位置的净荷块之外的任意位置的净荷块。其中，第五业务数据和第六业务数据可以是第一类业务数据中的任意两路业务数据。可见，本申请实施例支持第一类业务数据与多路第二类业务数据混合传输。
第二方面，本申请实施例提供了一种OTN中的数据传输方法，包括：接收OTU帧 或FlexO帧。然后，对该OTU帧或FlexO帧进行解映射，得到ODU帧。其中，ODU帧的净荷区的多个连续的净荷块中特定位置的净荷块承载第一类业务数据。并且，该多个连续的净荷块中的除该特定位置的净荷块之外的净荷块承载第二类业务数据。接着，从该多个连续的净荷块中获取第一类业务数据和第二类业务数据。
在一种可能的设计中，第一类业务数据包括TDM业务数据。第二类业务数据包括PKT-CBR业务数据和PKT-VBR业务数据中的至少一种。在另一种可能的设计中，第一类业务数据包括TDM业务数据和PKT-CBR业务数据中的至少一种。第二类业务数据包括PKT-VBR业务数据。
在一种可能的设计中，该多个连续的净荷块为一个承载周期。第一类业务数据包括第一业务数据。第一业务数据在第一承载周期中占用的净荷块的位置与在第二承载周期中占用的净荷块的位置相同。
在一种可能的设计中，该多个连续的净荷块为一个承载周期。第二类业务数据包括第二业务数据。第二业务数据在第一承载周期中占用的净荷块的位置与在第二承载周期中占用的净荷块的位置不同。
在一种可能的设计中，该特定位置的净荷块在该多个连续的净荷块中均匀分布。
在一种可能的设计中，从该多个连续的净荷块中获取第一类业务数据包括：将第一目标净荷块中承载的业务数据作为第一类业务数据。第一目标净荷块是该多个连续的净荷块中的且携带第一类业务数据的支路端口标识的净荷块。
在一种可能的设计中，从该多个连续的净荷块中获取第二类业务数据包括：将第二目标净荷块中承载的业务数据作为第二类业务数据。第二目标净荷块是该多个连续的净荷块中的且携带第二类业务数据的支路端口标识的净荷块。
在一种可能的设计中，该方法还包括：接收第一信息。第一信息用于指示该特定位置的净荷块在该多个连续的净荷块中的位置。该情况下，从稿多个连续的净荷块中获取第一类业务数据，包括：将第三目标净荷块中承载的业务数据作为第一类业务数据。第三目标净荷块是该多个连续的净荷块中的且位于该第一信息所指示的位置的净荷块。
在一种可能的设计中，第一信息携带在ODU帧所包括的OPU开销中或者ODU开销中。
在一种可能的设计中，该方法还包括：根据第一类业务数据的比特速率和单个净荷块的比特速率，确定该特定位置的净荷块的数量。然后，根据预定义规则，确定该特定位置的净荷块在该多个连续的净荷块中的位置。基于此，从该多个连续的净荷块中获取第一类业务数据，包括：将第四目标净荷块中承载的业务数据作为第一类业务数据。第四目标净荷块是该多个连续的净荷块中的且位于根据该预定义规则所确定的位置的净荷块。
在一种可能的设计中，从该多个连续的净荷块中获取第一类业务数据，包括：对该多个连续的净荷块进行解映射，得到第一业务帧。然后，将对第一业务帧进行解映射得到的业务数据作为第一类业务数据。
在一种可能的设计中，从该多个连续的净荷块中获取第二类业务数据，包括：对该多个连续的净荷块进行解映射，得到第二业务帧。然后，将对第二业务帧进行解映射得到的业务数据作为第二类业务数据。
其中，业务帧(如第一业务帧或第二业务帧)包括开销和净荷。该开销包括映射信 息。该映射信息用于表征将业务数据映射到该业务帧时所采用的映射规则。该净荷包括业务数据。
在一种可能的设计中，第一业务帧的大小等于净荷块的大小的整数倍。可选地，第一业务帧的大小等于一个净荷块的大小。
在一种可能的设计中，第二业务帧的大小等于净荷块的大小的整数倍。可选地，第二业务帧的大小等于一个净荷块的大小。
在一种可能的设计中，该方法还包括：接收第二信息，该第二信息用于指示该多个连续的净荷块中的首个净荷块在ODU帧的净荷区中的位置。然后，根据该第二信息，确定该首个净荷块在ODU帧的净荷区中的位置。
在一种可能的设计中，第二信息携带在ODU帧所包括的OPU开销中或者ODU开销中。
在一种可能的设计中，第一类业务数据包括第三业务数据和第四业务数据。该情况下，从多个连续的净荷块中获取第一类业务数据，包括：将该多个连续的净荷块中的第一整数个特定位置的净荷块上承载的业务数据作为第三业务数据；以及，将该多个连续的净荷块中的第二整数个特定位置净荷块上承载的业务数据作为第四业务数据。
上述第二方面及其可能的设计所提供的技术方案与上述第一方面或其相应的可能的设计所提供的方案对应。因此，相关解释及所能达到的有益效果可以参考上文，此处不再赘述。
第三方面，本申请实施例提供了一种OTN中的数据传输装置，该装置可用于执行上述第一方面或第一方面的任一种可能的设计提供的任一种方法。该装置可以是OTN设备或芯片。
在一种可能的设计中，可以根据上述第一方面或第一方面的任一种可能的设计提供的方法对该装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。
在一种可能的设计中，该装置可以包括存储器和处理器。存储器用于存储计算机程序。处理器用于调用该计算机程序，以执行上述第一方面或第一方面的任一种可能的设计提供的方法。可以理解的是，上述第一方面或第一方面的相应可能的设计中的发送步骤，在该可能的设计中，可以是处理器执行的输出步骤。示例的，结合上述第一方面，处理器可以用于调用存储器中存储的计算机程序，以执行以下步骤：首先，将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块。其中，该多个连续的净荷块占用ODU帧的净荷区。并且，将第二类业务数据映射到该多个连续的净荷块中的除该特定位置的净荷块之外的任意位置的净荷块。然后，将ODU帧映射到OTU帧或FlexO帧中。接着，输出该OTU帧或FlexO帧。
第四方面，本申请实施例提供了一种OTN中的数据传输装置，该装置可用于执行上述第二方面或第二方面的任一种可能的设计提供的任一种方法。该装置可以是OTN设备或芯片。
在一种可能的设计中，可以根据上述第二方面或第二方面的任一种可能的设计提供的方法对该装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。
在一种可能的设计中，该装置可以包括存储器和处理器，存储器用于存储计算机程 序。处理器用于调用该计算机程序，以执行上述第二方面或第二方面的任一种可能的设计提供的方法。
第五方面，本申请实施例提供了一种计算机可读存储介质，如计算机非瞬态的可读存储介质。其上储存有计算机程序(或指令)，当该计算机程序(或指令)在计算机上运行时，使得该计算机执行上述第一方面或第一方面的任一种可能的设计提供的任一种方法。
第六方面，本申请实施例提供了一种计算机可读存储介质，如计算机非瞬态的可读存储介质。其上储存有计算机程序(或指令)，当该计算机程序(或指令)在计算机上运行时，使得该计算机执行上述第二方面或第二方面的任一种可能的设计提供的任一种方法。
第七方面，本申请实施例提供了一种计算机程序产品，当其在计算机上运行时，使得第一方面或第一方面的任一种可能的设计提供的任一种方法被执行。
第八方面，本申请实施例提供了一种计算机程序产品，当其在计算机上运行时，使得第二方面或第二方面的任一种可能的设计提供的任一种方法被执行。
可以理解的是，上述提供的任一种OTN中的数据传输装置或计算机存储介质或计算机程序产品等均可以应用于上文所提供的对应的方法，因此，其所能达到的有益效果可参考对应的方法中的有益效果，此处不再赘述。
附图说明
图1为可适用于本申请实施例的一种网络架构的示意图；
图2为可适用于本申请实施例的一种OTN设备的硬件结构示意图；
图3为可适用于本申请实施例的一种OTUk帧(k≠Cn)的帧结构示意图；
图4为可适用于本申请实施例的一种OTUk帧(k＝Cn)的帧结构示意图；
图5A为本申请实施例提供的一种n个连续的净荷块与ODU帧的净荷区之间的对应关系的示意图；
图5B为本申请实施例提供的另一种n个连续的净荷块与ODU帧的净荷区之间的对应关系的示意图；
图6为本申请实施例提供的一种光传送网中的数据传输方法的交互示意图；
图7为本申请实施例基于图6提供的一种业务数据映射示意图；
图8为本申请实施例提供的一种ODU帧的结构示意图；
图9为本申请实施例提供的另一种光传送网中的数据传输方法的交互示意图；
图10为本申请实施例基于图9提供的一种业务数据映射示意图；
图11为本申请实施例提供的另一种光传送网中的数据传输方法的交互示意图；
图12为本申请实施例基于图11提供的一种业务数据映射示意图；
图13为本申请实施例提供的另一种光传送网中的数据传输方法的交互示意图；
图14为本申请实施例提供的另一种ODU帧的结构示意图；
图15为本申请实施例提供的一种光传送网中的数据传输装置的结构示意图；
图16为本申请实施例提供的另一种光传送网中的数据传输装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
本申请实施例描述的网络架构和业务场景是为了更清楚地说明本申请实施例的技术 方案，并不构成对本申请实施例提供的技术方案的限制。本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似技术问题同样适用。
本申请实施例提供的技术方案可适用于光网络，例如：OTN。一个OTN通常由多个OTN设备通过光纤连接而成，可以根据具体需要组成如线型、环形和网状等不同的拓扑类型。
图1给出了可适用于本申请实施例的一种网络架构的示意图。如图1所示的OTN包括两个OTN网络(分别为OTN网络1和OTN网络2)。每一个OTN网络包括一定数量的OTN设备(图1中用N表示)，OTN网络内的设备之间的链路为域内链路，OTN网络间的设备之间的链路为域间链路。根据实际需要，一个OTN设备可能具备一种或多种功能。一般来说，OTN设备分为光层设备、电层设备以及光电混合设备。光层设备指的是能够处理光层信号的设备，例如：光放大器(optical amplifier，OA)。电层设备指的是能够处理电层信号的设备，例如：能够处理ODU信号的设备。光电混合设备指的是具备处理光层信号和电层信号能力的设备。需要说明的是，根据具体的集成需要，一台OTN设备可以集合多种不同的功能。本申请提供的技术方案适用于不同形态和集成度的OTN设备。
图2给出了可适用于本申请实施例的一种OTN设备的硬件结构示意图。具体地，一个OTN设备包括电源、风扇、辅助类单板，还可能包括支路板、线路板、交叉板，以及系统控制和通信类单板，其中，线路板也可包括光层处理单板。需要说明的是，根据具体的需要，每个设备具体包含的单板类型和数量可能不相同。例如，作为核心节点的网络设备可能没有支路板。作为边缘节点的网络设备可能有多个支路板。其中，电源用于为OTN设备供电，可能包括主用和备用电源。风扇用于为设备散热。辅助类单板用于提供外部告警或者接入外部时钟等辅助功能。支路板、交叉板和线路板主要是用于处理OTN的电层信号(后续称为OTN帧)。其中，支路板用于实现各种客户业务的接收和发送，例如同步数字体系(synchronous digital hierarchy，SDH)业务、分组业务、以太网业务和前传业务等。更进一步地，支路板可以划分为客户侧光模块和信号处理器。其中，客户侧光模块可以为光收发器，用于接收和/或发送客户信号。信号处理器用于实现对客户信号到OTN帧的映射和解映射处理。交叉板用于实现OTN帧的交换，完成一种或多种类型的OTN帧的交换。线路板主要实现线路侧OTN帧的处理。具体地，线路板可以划分为线路侧光模块和信号处理器。其中，线路侧光模块可以为线路侧光收发器，用于接收和/或发送OTN帧。信号处理器用于实现对线路侧的OTN帧的复用和解复用，或者映射和解映射处理。系统控制和通信类单板用于实现系统控制和通信。具体地，可以通过背板从不同的单板收集信息，或者将控制指令发送到对应的单板上去。除非特殊说明，具体的组件(例如支路板)可以是一个或多个，本申请不做任何限制。需要说明的是，本申请实施例对设备包含的单板类型，以及单板具体的功能设计和数量不做限制。
为了更加清楚的理解本申请，以下对本申请实施例中使用的部分术语和技术作简单介绍。
1)、ODU帧(如ODUk帧)和OTU帧(如OTUk帧)
在电层上，OTN设备所处理的OTN帧可以采用国际电信联盟-电信标准分部(International Telecommunication Union-Telecommunication standard sector，ITU-T)定义 的帧格式。例如，G.709标准和G.709.1标准等，以实现设备之间的互通。现有的标准中已经定义了多种速率的OTN帧，如OPUk帧、ODUk帧和OTUk帧。其中，k＝0、1、2、3、4、Cn和flex分别表示比特速率为1.25Gbit/s、2.5Gbit/s、10Gbit/s、40Gbit/s、100Gbit/s、n*100Gbit/s和n*1.25Gbit/s(n≥2)。需要说明的是，上述提及的比特速率均为近似值。例如，OPU4帧的比特速率更准确的为104.35597533Gbit/s。其他示例不再一一列举。
图3和图4分别示出了k≠Cn和k＝Cn时，OTUk帧的帧结构示意图。
当k≠Cn时，如图3所示，一个OTUk帧有4行*4080列。OPUk净荷区和OPUk开销区(即OPUk OH)构成了OPUk帧，OPUk帧和ODUk开销区(即ODUk OH)构成了ODUk帧，ODUk帧、OTUk开销区(即OTUk OH)、帧对齐信号(frame alignment signal，FAS)和前向错误纠正(forward error correction，FEC)校验区构成了OTUk帧。具体地，OTUk帧中的第1行的1～7列为FAS和复帧对齐信号(multiframe alignment signal，MFAS)，第1行的8～14列为OTUk OH，第2～4行的1～14列为ODUk OH，第1～4行的15～16列为OPUk OH，第1～4行的17～3824列为OPUk净荷区，第1～4行的3825～4080列为FEC校验区。
当k＝Cn时，如图4所示，OTUCn帧由n个OTUC实例帧(图4中记为OTUC#1至OTUC#n)组成，C表示比特速率为100Gbit/s。OTUC实例帧不包括FEC校验区。OTUCn帧包括OPUCn帧(即OTUCn帧中的第15～3824列)，OPUCn帧由n个OPUC实例帧(即一个OTUC实例帧中的第15～3824列)组成。其中，OPUCn帧的净荷区可以由n个OPUC实例帧的净荷区按照一定字节数间插组成。例如，按照16列间插。需要说明的是，OTUC实例帧指的是构成OTUCn帧的基本帧单位，也可以称为OTUC基础帧或其他名称，本申请对此不作任何限定。
2)、净荷块
净荷块，位于ODU帧的净荷区，由一个字节或连续的多个字节构成，或者连续的多个比特构成。具体地，一个净荷块的大小可以是字节的整数倍，也可以是8字节的整数倍，如64字节、128字节、192字节或256字节等。可选地，不同净荷块的大小相等，下文中的具体示例均以此为例进行说明。净荷块也可以被称作码块或其他名字，本申请对此不做限定。
需要说明的是，具体实现时，一个净荷块为承载业务数据的最小单元(亦可以称为最小支路单元)。一个净荷块的速率可以任意小。多个净荷块可以组合作为一个灵活支路单元，用于承载对应速率的业务数据。
本申请提到的连续的两个字节，可以是一个ODU帧的净荷区的同一行中相邻的两个字节。或者，也可以是一个ODU帧的净荷区的一行中的最后一个字节和该行的下一行中的第一个字节。或者，还可以是一个ODU帧的净荷区中的最后一个字节和该ODU帧的下一个ODU帧的净荷区中的第一个字节。“字节”可以替换为“比特”。也就是说，一个净荷块可以位于一个ODU帧的净荷区中的同一行，也可以跨行；还可以跨ODU帧的净荷区。
3)、n个连续的净荷块和承载周期
n是大于或等于2的整数。本申请实施例对n的具体取值不进行限定。n个连续的净荷块可以位于一个ODU帧的净荷区，也可以跨多个ODU帧的净荷区。当n个连续的净荷块位于一个ODU帧的净荷区时，具体可以位于净荷区中的一行也可以跨多行。
在一种实现方式中，n个连续的净荷块占用整数倍个ODU帧的净荷区。例如，n个连续的净荷块占用1个ODU帧的净荷区或2个ODU帧的净荷区。图5A给出了一种n个连续的净荷块占用2个ODU帧的净荷区。在另一种实现方式中，n个连续的净荷块占用非整数倍个ODU帧的净荷区。例如，n个连续的净荷块占用0.4个ODU帧的净荷区或1.5个ODU帧的净荷区等。图5B给出了一种n个连续的净荷块占用1.5个ODU帧的净荷区。
图5A和图5B均以图3所示的OTUk帧中所包含的ODUk帧为例。并且，对图5A和图5B中的任一附图来说，a图和b图分别为第j个ODUk帧和第j+1个ODUk帧的结构示意图，j是大于或等于1的整数；c图为n个连续的净荷块(如阴影部分所示)和该n个连续的净荷块对应的开销区(即OH)的示意图。其中，c图中的开销区对应于(即占用)a图和b图中的ODUk OH和OPUk OH；n个连续的净荷块中的“斜线阴影”所示的净荷块对应于(即占用)a图中的ODU帧的净荷区(如a图中的斜线阴影所示)，n个连续的净荷块中的“方格阴影”所示的净荷块对应于(即占用)b图中的ODU帧的净荷区(如b图中的方格阴影所示)。
综上可知，本申请支持n个连续的净荷块与ODU帧的净荷区松耦合。换言之，本申请实施例可以不限定n个连续的净荷块的大小与ODU帧的净荷区的大小之间的关系。
可以理解的是，n个连续的净荷块中的第1至第n个净荷块中承载的业务数据的传输顺序，与该n个连续的净荷块所占用的ODU帧的净荷区中承载的业务数据的传输顺序相同。其中，一个ODU帧的净荷区中承载的业务数据，是按照其在该净荷区中所处的位置“从上到下、从左到右”的顺序进行传输的。例如，结合图3，映射至第1行第17～3824列、第2行第17～3824列、第3行第17～3824列和第4行第17～3824列的业务数据依次传输。
在本申请一些实施例中，为了方便描述，将n个连续的净荷块称为一个承载周期。承载周期也可以被称作发送周期、映射周期或数据中间帧等。对此，本申请实施例不进行限定。
可选地，每个承载周期所包括的净荷块的数量相同。
可选地，一个承载周期所包括的最后一个净荷块与该承载周期的下一个承载周期所包括的第一个净荷块之间是ODU帧的净荷区中相邻的两个净荷块。也就是说，连续的多个承载周期占用一个或多个ODU帧的净荷区中连续的多个字节(或比特)。
为了方便描述，在本申请实施例中，每个承载周期中的净荷块的编号(或索引)使用1～n。在附图中标记为#1～#n为例进行说明，在此统一说明，下文不再赘述。
4)、第一类业务数据和第二类业务数据
可选地，第一类业务数据可以包括时分复用(time division multiplexing，TDM)业务数据和固定速率的分组(packet-constants bit rate，PKT-CBR)业务数据中的至少一种。
可选地，第二类业务数据可以包括PKT-CBR业务数据和可变速率的分组业务(packet-variable bit rate，PKT-VBR)中的至少一种。
也就是说，PKT-CBR业务数据可以作为第一类业务数据，也可以作为第二类业务数据。具体实现时，发送端和接收端可以基于预定义的规则(如协议预定义的规则)，确定哪些业务数据是第一类业务数据，哪些业务数据是第二类业务数据。
本申请实施例提供的技术方案用于混合传输上述两类业务数据的场景中。具体地， 可以是混合传输一路或多路第一类业务数据，以及，一路或多路第二类业务数据。下文描述的第一至第六业务数据均是指一路业务数据。可以理解的是，来自不同客户源的业务数据是不同路业务数据，另外，来自同一客户源的业务数据也可以划分为不同路业务数据。
5)、业务帧，第一业务帧和第二业务帧
业务帧包括开销和净荷。业务帧的开销可以用于对业务数据进行监控管理以及承载映射信息等。该映射信息可以用于表征将业务数据映射到业务帧时所采用的映射规则。例如，业务帧的开销包括但不限于业务帧头指示，路径踪迹指示(trail trace identifier，TTI)、X比特间插奇偶校验(X bit-interleaved parity，BIP-X)、后向错误指示(backward error indication，BEI)、后向缺陷指示(backward defect indication，BD)、状态指示(status，STAT)、时戳、顺序标识、映射开销等。业务帧的净荷用于承载业务数据。示例的，业务帧可以是光业务单元(optical service unit，OSU)。
为了方便描述，在本申请的一些实施例中，引入了“第一业务帧”和“第二业务帧”的概念。它们分别用于承载(或映射)第一类业务数据和第二类业务数据。
可选地，第一业务帧的大小和第二业务帧的大小都等于净荷块的大小的整数倍。这样，可以降低业务数据的映射复杂度，从而降低设备成本。或者，第一业务帧的大小和第二业务帧的大小都等于一个净荷块的大小。这样，有助于进一步降低业务数据的映射复杂度，从而进一步降低设备成本。其中，一个业务帧的大小可以是指该业务帧的开销的大小和该业务帧的净荷的大小之和。或者，一个业务帧的大小可以是指该业务帧的净荷的大小。
6)、发送端和接收端
本申请实施例中，发送端是指OTN中发送业务数据的设备，接收端是指OTN中接收业务数据的设备。该发送端和接收端均可以是上文中描述的OTN设备。
7)、其他术语
本申请实施例中的术语“至少一个(种)”包括一个(种)或多个(种)。“多个(种)”是指两个(种)或两个(种)以上。例如，A、B和C中的至少一种，包括：单独存在A、单独存在B、同时存在A和B、同时存在A和C、同时存在B和C，以及同时存在A、B和C。
在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
在本申请的描述中，“多个”是指两个或多于两个。在本申请实施例中，为了便于清楚描述所提供的技术方案，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。可以理解，“第一”、“第二”等字样并不对数量和执行次序进行限定。
在本申请实施例中，两个步骤的执行顺序不分先后，包括：先执行其中一个步骤再执行另一个步骤；或者在执行一个步骤的过程中执行另一个步骤；或者同时执行这两个步骤等。
以下，结合附图，对本申请实施例提供的光传送网中的数据传输方法进行说明。
如图6所示，为本申请实施例提供的一种光传送网中的数据传输方法的交互示意图。 本实施例中是以“混合传输一路第一类业务数据和一路第二类业务数据，且业务数据直接映射到ODU帧的净荷区”为例进行说明的。图6所示的方法包括如下步骤：
S101：发送端接收第一业务数据和第二业务数据。其中，第一业务数据属于第一类业务数据，第二业务数据属于第二类业务数据。
例如，发送端接收来自客户源的第一业务数据和第二业务数据。
S102：发送端根据第一业务数据的比特速率和单个净荷块的比特速率，确定第一业务数据在一个承载周期中占用的净荷块的数量m。m是大于或等于1的整数。例如，m为对“第一业务数据的比特速率除以单个净荷块的比特速率后得到的值”向上取整后得到的值。
单个净荷块的比特速率a、一个承载周期所包括的净荷块的数量n和ODU帧的净荷速率b之间满足公式a*n＝b。其中，n为大于等于2的整数。n的取值可以根据具体情况任意配置。b的取值跟ODU帧类型相关。例如，ODU2帧时，b为10Gbit/s。
可选地，可以预先配置一个承载周期所包含的净荷块数量n的取值。该情况下，通过ODU帧的净荷速率b除以n可以得到单个净荷块的比特速率a。
可选地，可以预先配置单个净荷块的比特速率a的取值。例如假定净荷块的大小为128字节，设定单个净荷块的发送频率为每秒2000个，即每秒发送2000个承载周期。那么，单个净荷块的比特速率a为128*8*2000＝2.048Mbit/s。该情况下，通过ODU帧的净荷速率b除以单个净荷块速率a可以得到一个承载周期所包含的净荷块数量n的取值。
S103：发送端确定用于承载第一业务数据的m个净荷块的位置。
一个净荷块的位置是指该净荷块在该净荷块所属的承载周期中的位置。例如，可以使用一个净荷块的编号(或索引)来表征该净荷块在该净荷块所属的承载周期中的位置。该m个净荷块为m个特定位置的净荷块。该步骤可以理解为：发送端确定m个特定位置的净荷块的位置图案(或固定位置图案)。
可选地，该m个特定位置的净荷块在一个承载周期中均匀分布。例如，假设一个承载周期由40个净荷块(编号分别是#1～#40)构成，m＝4，且m个特定位置的净荷块的编号可以分别是：#1、#11、#21、#31。这样，当第一类业务数据是对时钟性能要求较高的业务如TDM类业务时，可以满足时钟透明传送需求，从而保证接收端恢复的业务时钟满足性能要求。可以理解的是，TDM类业务为固定比特速率，且有自己的时钟性能要求。例如时钟漂移和抖动指标等，这就需要发送端尽量实时地按照该类业务的原始固定比特速率向接收端传送业务数据。而“该m个特定位置的净荷块在一个承载周期中均匀分布”有助于发送端尽量实时地按照该类业务的原始固定比特速率向接收端传送业务数据。
可选地，发送端可以根据预定义规则，确定该m个特定位置的净荷块的位置。例如，该预定义规则可以是一种预定义算法如sigma-delta算法等。其中，该预定义规则可以是发送端和接收端均预先可以获知的规则，也可以是发送端自行定义而接收端预先不知道的规则。
S104：发送端将第一业务数据和第二业务数据映射到ODU帧的净荷区。
具体地：
在每个承载周期中，发送端根据S103中所确定的固定位置图案，将第一业务数据映射到该承载周期中的m个特定位置的净荷块。
在每个承载周期中，发送端将第二业务数据映射到非特定位置的净荷块中未被占用 的任意位置的净荷块。例如，发送端在接收到第二业务数据的数据量达到一个净荷块的大小时，将这些数据映射到非特定位置的净荷块中未被占用的任意一个净荷块。
关于ODU帧的净荷区与承载周期之间的对应关系可以参考上文，例如图5A或图5B。
基于S104可知，承载第一业务数据的净荷块在不同承载周期中的位置均相同。承载第二业务数据的净荷块在不同承载周期中的位置可能相同，也可能不同。
另外，在不同承载周期中，承载第二业务数据的净荷块的数量可以相同，也可以不同。第二业务数据占用的净荷块的数量，可以基于第二业务数据的实时流量确定。假设在某个承载周期内，第二业务数据的流量为T；那么，在该承载周期内，第二业务数据需要占用的净荷块的数量最多为T除以单个净荷块速率后得到的值。
如图7所示，为本申请实施例提供的一种业务数据映射示意图。其中，图7中是示意出了2个承载周期(即第1个承载周期和第2个承载周期)中第一业务数据和第二业务数据的映射示意图。并且，具体是以一个承载周期由40个净荷块(编号分别是#1～#40)构成，且m个特定位置的净荷块的编号分别是：#1、#11、#21、#31为例进行说明的。参见图7，在这两个承载周期中，第一业务数据均映射在编号为#1、#11、#21、#31的净荷块中。并且，在第1个承载周期中，第二业务数据映射在编号为#5、#8、#23、#25的净荷块中，在第2个承载周期中，第二业务数据映射在编号为#2、#5、#7、#28、#40的净荷块中。
需要说明的是，为了方便描述和便于理解，本申请的一些具体示例(如图7或图9等)中是以一个承载周期由40个净荷块构成为例进行说明的。在实际实现时，一个承载周期中可以由n(n＞40)个净荷块构成，例如，n＝100、200、300或1000等。
S105：发送端为ODU帧的净荷区添加OPU开销和ODU开销，得到ODU帧；并将ODU帧映射到OTU帧或灵活OTN(flexible OTN，FlexO)帧。
具体地，当ODU帧具体是ODUk帧，且k≠Cn时：在一种实现方式中，可以为该ODU帧添加OTU开销等，得到OTU帧。在另一种实现方式中，可以先将ODU帧映射到其他高阶ODU帧中。例如，将ODU1帧映射到ODU2帧或ODU3帧中等。然后为该高阶ODU帧添加OTU开销等，得到OTU帧。在另一种实现方式中，可以先将ODUk(k≠Cn)帧映射到ODUCn帧，为该ODUCn帧添加OTU开销等，得到OTUCn帧。然后，将OTUCn帧映射成FlexO帧。当ODU帧具体是ODUk帧，且k＝Cn时，为该ODU帧添加OTU开销等，得到OTUCn帧；再将OTUCn帧映射成FlexO帧。
S106：发送端发送该OTU帧或FlexO帧。
例如，当在S105中将ODU帧映射成FlexO帧时，可以通过FlexO接口发送该FlexO帧。
可选地，对于同一路业务数据来说，发送端先接收到的业务数据先被发送，后接收到的业务数据后被发送。对于不同路业务数据来说，本申请实施例对发送端接收和发送业务数据的顺序不进行限定。基于此，在S104中，将同一路业务数据映射到ODU帧的净荷区时，可以基于ODU帧的净荷区中“从上到下、从左到右”的顺序进行映射。
S107：接收端对所接收到的OTU帧或FlexO帧进行解映射，得到ODU帧。
其中，ODU帧中承载的业务数据可以参考上述S104的映射结果。
S108：接收端根据ODU帧的净荷区与承载周期之间的对应关系，识别出承载周期，并从该承载周期所包括的净荷块中解析得到第一业务数据和第二业务数据。
其中，ODU帧的净荷区与承载周期之间的对应关系可以是预定义，例如，二者之间的对应关系可以如图5A或图5B所示。识别出承载周期，可以理解为：确定一个承载周期在ODU帧的净荷区中的位置，如一个承载周期占用ODU帧的净荷区中的哪些字节(或比特)。
为了使接收端识别出第一业务数据，本申请实施例提供了以下具体实现方式：
方式1：发送端可以在承载第一业务数据的净荷块(即该m个特定位置的净荷块)中携带第一业务数据的支路端口标识。该步骤可以发生在S104的过程中或S104之后。基于方式1，接收端可以将一个承载周期中的且携带第一业务数据的支路端口标识的净荷块中承载的业务数据作为第一业务数据。
其中，一路业务数据具有一个支路端口标识。业务数据的支路端口标识也可以被称作该业务数据的标识。该路业务数据可以是第一业务数据，或者，也可以是下文中描述的第二至第六业务数据。
方式2：发送端可以向接收端发送第一信息。第一信息用于指示该m个特定位置的净荷块在其所属的承载周期中的位置。可选地，第一信息可以携带在ODU帧所包括的OPU开销中或者ODU开销中。基于方式2，接收端可以将一个承载周期中的且位于第一信息所指示的位置的净荷块中承载的业务数据作为第一业务数据。
可选地，当第一信息携带在ODU帧所包括的OPU开销中时，可以通过一个ODU帧中的OPU开销中的MFAS和超帧指示(super-frame alignment signal，SFAS)来指示一个承载周期中的一个净荷块的位置。并且，可以结合该OPU开销区中的复用结构指示(multiplex structure identifier，MSI)来指示一个承载周期中相应位置的净荷块(即由MFAS和SFAS共同确定的净荷块)是否是特定位置的净荷块。可选地，MSI还可以用于指示该相应位置的净荷块的支路端口标识，以使得接收端可以基于该支路端口标识识别出该相应位置的净荷块中承载的业务数据属于哪一路业务数据。
其中，MFAS用于进行ODU帧计数。在目前的ODU帧结构(例如图3所示的ODUk帧结构)中，MFAS占用8比特，位于ODU帧的第1行第7列。MFAS的取值范围为0～255。每个ODU帧MFAS的取值加1。也就是说，如果第i个ODU帧所携带的MFAS的取值小于255，则第i+1个ODU帧中携带的MFAS的取值相比第i个ODU帧所携带的MFAS的取值增加了1。如果第i个ODU帧所携带的MFAS的取值等于255，则第i+1个ODU帧中携带的MFAS的取值为0。i是大于或等于1的整数。基于此，可以将256个ODU帧作为一个复帧周期。当然本申请实施例并不限定一个复帧周期所包括的ODU帧的个数。
SFAS用于进行MFAS计数。SFAS为本申请实施例新定义的字段。SFAS所占的比特数可以是基于一个承载周期所包括的净荷块的个数与MFAS所占的比特数确定的。例如，当一个承载周期所包括的净荷块的个数是65536、且MFAS占用8比特时，SFAS可以占用8比特。该情况下，SFAS可以表示的范围为0～255，通过MFAS和SFAS即可表示范围256*256＝65536。
同一复帧周期中的ODU帧所携带的SFAS的取值相同。以SFAS的表示范围为0～255为例，每个复帧周期SFAS的取值加1。也就是说，如果第j个复帧周期中的ODU帧所携带的SFAS的取值小于255，则第j+1个复帧周期中的ODU帧所携带的SFAS的取值相比第j个复帧周期中的ODU帧所携带的SFAS的取值增加了1。如果第j个复帧周期 中的ODU帧所携带的SFAS的取值等于255，则第j+1个复帧周期中的ODU帧所携带的SFAS的取值为0。其中，j是大于或等于1的整数。
MSI用于指示一个承载周期中相应位置的净荷块(即由MFAS和SFAS共同确定的净荷块)是否是特定位置的净荷块。例如，通过MSI[MFAS*SFAS]表示一个承载周期的第MFAS*SFAS个净荷块是否是特定位置的净荷块。具体地，MSI的“第1个比特是1”表示第MFAS*SFAS个净荷块是特定位置的净荷块，“第1个比特是0”表示第MFAS*SFAS个净荷块不是特定位置的净荷块。第2～8个比特可以表示第MFAS*SFAS个净荷块上承载的业务数据的支路端口标识。如图8所示，为基于该示例提供的一种ODU帧的结构示意图。图8中所示的ODU帧是基于图3进行绘制的。并且，图8中是以SFAS位于ODU帧的第4行第16列为例进行说明的。图8中的“占用”可以理解为占用标识，用于指示当前ODU帧所对应的MSI[MFAS*SFAS]位置的净荷块是否为特定位置的净荷块。需要说明的是，本申请实施例对SFAS和MSI占用的比特数和表示的范围不做限定，根据实际情况可灵活配置。
方式3：接收端可以根据与发送端所采用的同样的预定义算法(如sigma-delta算法、或者接收端和发送端自定义的算法等)，确定该m个特定位置的净荷块的位置，从而将一个承载周期中的该所确定的位置的净荷块中承载的业务数据作为第一业务数据。这样，发送端不需要向接收端传输该m个特定位置的净荷块的位置，有助于降低数据处理的复杂度。
可以理解的是，在不冲突的情况下，上述方式1和方式2可以结合使用。例如，承载第一业务数据的一部分净荷块中携带第一业务数据的支路端口标识。并且，发送端向接收端指示另一部分净荷块在其所属的承载周期中的位置。
需要说明的是，在具体实现时，还可以由网管或软件定义网络(software defined network，SDN)预先为发送端和接收端配置该m个特定位置的净荷块。其中，网管和SDN是软件功能模块，其所在的物理实体可以是上述发送端或接收端，或独立于上述发送端和接收端的一个设备。网管和SDN均可以用于管理OTN中的设备。
为了使接收端识别出第二业务数据，本申请实施例提供了以下具体实现方式：发送端可以在承载第二业务数据的净荷块中携带第二业务数据的支路端口标识。该情况下，接收端可以将一个承载周期中的且携带第二业务数据的支路端口标识的净荷块中承载的业务数据作为第二业务数据。
本实施例提供的技术方案中，将第一类业务数据映射到多个连续的净荷块中的特定位置的净荷块，并将第二类业务数据映射到该多个连续的净荷块中的除该特定位置中之外的未被占用的任意位置的净荷块。由于对于第二类业务数据来说，可以映射到非特定位置中未被占用的任意位置，因此，需要传输多路第二类业务数据时，可以共享非特定位置的净荷块，从而有助于减少带宽资源的浪费，从而提高带宽资源利用率。
需要说明的是，在本申请的一些实施例中，对于第一类业务数据，在每个承载周期中都映射到m个特定位置的净荷块。并且，m个特定位置在一个承载周期中均匀分布。这样，当第一类业务数据是对时钟性能要求较高的业务如TDM类业务时，可以满足时钟透明传送需求，从而保证接收端恢复的业务时钟满足性能要求。
如图9所示，为本申请实施例提供的一种光传送网中的数据传输方法的交互示意图。本实施例中是以“混合传输多路第一类业务数据和多路第二类业务数据，且业务数据直 接映射到ODU帧的净荷区”为例进行说明的。图9所示的方法包括如下步骤：
S201：发送端接收第三业务数据、第四业务数据、第五业务数据和第六业务数据。其中，第三业务数据和第四业务数据均属于第一类业务数据，第五业务数据和第六业务数据均属于第二类业务数据。并且，第三业务数据和第四业务数据是不同路业务数据，第五业务数据和第六业务数据是不同路业务数据。
可以理解的是，第三业务数据和第四业务数据中的其中一个业务数据与上述的第一业务数据可以相同，当然，第三业务数据和第四业务数据也可以均与上第一业务数据不同。同理，第五业务数据和第六业务数据中的其中一个业务数据与上述第二业务数据可以相同，当然，第五业务数据和第六业务数据也可以均与上述第二业务数据不同。
S202：发送端根据第三业务数据的比特速率和单个净荷块的比特速率，确定第三业务数据在一个承载周期中占用的净荷块的数量m1。并根据第四业务数据的比特速率和单个净荷块的比特速率，确定第四业务数据在一个承载周期中占用的净荷块的数量m2。m1和m2均是大于或等于1的整数。m1的取值与m2的取值可以相等，也可以不相等。
S203：发送端确定用于承载第三业务数据的m1个净荷块的位置，以及用于承载第四业务数据的m2个净荷块的位置。也就是说，确定该m1个特定位置的净荷块的固定位置图案，以及该m2个特定位置的净荷块的固定位置图案。可选地，该m1个特定位置的净荷块在承载周期中均匀分布。可选地，该m2个特定位置的净荷块在承载周期中均匀分布。
S204：发送端将第三业务数据、第四业务数据、第五业务数据和第六业务数据混合映射到ODU帧的净荷区(具体是一个或多个ODU帧的部分或全部净荷区)。
具体地：
在每个承载周期中，发送端将第三业务数据映射到该承载周期中的该m1个特定位置的净荷块，并将第四业务数据映射到该承载周期中的该m2个特定位置的净荷块。这两个步骤的执行顺序可以不分先后。
在每个承载周期中，发送端将第五业务数据和第六业务数据分别映射到非特定位置的净荷块中未被占用的任意位置的净荷块。这两个步骤的执行顺序可以不分先后。例如，在接收到第五业务数据的数据量达到一个净荷块的大小时，将这些第五业务数据映射到非特定位置的净荷块中未被占用的任意一个净荷块。在接收到第六业务数据的数据量达到一个净荷块的大小时，将这些第六业务数据映射到非特定位置的净荷块中未被占用的任意一个净荷块。
可选地，如果同一时刻，第五业务数据和第六业务数据的数据量均达到了一个净荷块的大小，则发送端可以根据第五业务数据和第六业务数据的优先级顺序和/或轮询方式，将第五业务数据和第六业务数据映射到非特定位置的净荷块中未被占用的任意位置的净荷块。其中，第五业务数据和第六业务数据的优先级顺序可以是预先配置的，轮询方式可以是按照业务标识顺序或者预先配置的顺序。
基于S204可知：承载第三业务数据的净荷块在不同承载周期中的位置均相同。承载第四业务数据的净荷块在不同承载周期中的位置均相同。但是，承载第五业务数据和第六业务数据的净荷块在不同承载周期中的位置可能相同，也可能不同。
如图10所示，为本申请实施例提供的一种业务数据映射示意图。其中，图10中是示意出了2个承载周期(即第1个承载周期和第2个承载周期)中第三至第六业务数据 的映射示意图。并且，一个承载周期由40个净荷块(编号分别是#1～#40)构成。m1个特定位置的净荷块的编号分别是：#1、#11、#21和#31。m2个特定位置的净荷块的编号分别是#2、#10、#18、#26、#34。参见图10，在这两个承载周期中，第三业务数据均映射在编号为#1、#11、#21和#31的净荷块中，第四业务数据均映射在编号为#2、#10、#18、#26和#34的净荷块中。另外，在第1个承载周期中，第五业务数据映射在编号为#5、#8、#23和#25的净荷块中，第六业务数据映射在编号为#3的净荷块中。在第2个承载周期中，第五业务数据映射在编号为#5、#8和#23的净荷块中，第六业务数据映射在编号为#7、#9和#12的净荷块中。
S205～S207：可以参考上述S105～S107。
S208：接收端根据ODU帧的净荷区与承载周期之间的对应关系，识别出承载周期。并从该承载周期所包括的净荷块中解析得到第三至第六业务数据。
具体地，解析该承载周期中的该m1个特定位置的净荷块上承载的业务数据，得到第三业务数据。解析该承载周期中的该m2个特定位置净荷块上承载的业务数据，得到第四业务数据。这两个步骤的具体实现方式可以参考上述获得第一业务数据的方法。接收端解析得到第五业务数据和第六业务数据的方法可以参考上文中获得第二业务数据的方法。
本实施例提供的技术方案的有益效果可以参考上述图6所示的实施例的有益效果。另外，多路第二类业务可共享每个承载周期中的非特定位置的净荷块，有助于提高带宽利用率。
如图11所示，为本申请实施例提供的一种光传送网中的数据传输方法的交互示意图。本实施例中是以“混合传输一路第一类业务数据和一路第二类业务数据，且业务数据间接映射到ODU帧的净荷区”为例进行说明的。图11所示的方法包括如下步骤：
S301～S303：可以参考上述S101～S103。
S304：发送端将第一业务数据映射到第一业务帧，将第二业务数据映射到第二业务帧。以及，将第一业务帧和第二业务帧混合映射到ODU帧的净荷区。
具体地：将第一业务数据映射到第一业务帧的净荷区，并添加第一业务帧的开销到该业务帧的开销区。将第二业务数据映射到第二业务帧的净荷区，并添加第二业务帧的开销到该业务帧的开销区。在每个承载周期中，发送端根据S303中所确定的固定位置图案，将第一业务帧映射到该承载周期中的m个特定位置的净荷块。在每个承载周期中，将第二业务帧映射到非特定位置的净荷块中未被占用的任意位置的净荷块。
如图12所示，为本申请实施例提供的一种业务数据映射示意图。其中，图12中所针对的业务数据可以是第一业务数据，也可以是第二业务数据。参见图12可知，对于一路业务数据来说，先将该业务数据映射到一个业务帧的净荷区，再将该业务帧映射到ODU帧的净荷区。其中，图12中是以ODU帧的净荷区具体是一个承载周期为例进行说明的。
本申请实施例对发送端将第一类业务数据(如第一业务数据)映射至业务帧的具体实现方式不进行限定。例如可以进行同步映射或异步映射。例如，可以采用通用映射规程(generic mapping procedure，GMP)或其他映射方式将第一类业务数据映射到业务帧。
本申请实施例对发送端将第二类业务数据(如第二业务数据)映射至业务帧的具体实现方式不进行限定，例如可以进行同步映射或异步映射。例如，可以采用GMP、通用 成帧规程(generic frame procedure-framing，GFP-F)、空闲映射规程(idle mapping procedure，IMP)或者其他映射方式将第二类业务数据映射到业务帧。
S305～S307：可以参考上述S105～S107。
S308：接收端根据ODU帧的净荷区与承载周期之间的对应关系，识别出承载周期。并从该承载周期中解析得到第一业务帧和第二业务帧。然后，对第一业务帧进行解映射，得到第一业务数据。对第二类业务数据进行解映射，得到第二业务数据。
具体地，接收端可以将一个承载周期中携带第一业务数据的支路端口标识的净荷块中映射的业务帧作为第一业务帧；或者将一个承载周期中位于第一信息所指示的位置的业务帧作为第一业务帧；或者根据与发送端所采用的同样的预定义算法(如sigma-delta算法等)，确定该m个特定位置的净荷块的位置，从而将位于该位置的业务帧作为第一业务帧等。
具体地，接收端可以将一个承载周期中携带第二业务数据的支路端口标识的净荷块中映射的业务帧作为第二业务帧。
本实施例提供的技术方案的有益效果可以参考上述图6所示的实施例的有益效果。另外，本实施例提供的技术方案中，先将业务数据映射到业务帧中，再将业务帧映射到ODU帧的净荷区。这样，有助于对业务数据进行端到端管理，提高业务传送质量。
如图13所示，为本申请实施例提供的一种光传送网中的数据传输方法的交互示意图。本实施例中是以“混合传输多路第一类业务数据和多路第二类业务数据，且业务数据间接映射到ODU帧的净荷区”为例进行说明的。图13所示的方法包括如下步骤：
S401～S403：可以参考上述S201～S203。
S404：发送端将第三至第六业务数据均映射到业务帧，以及，将业务帧映射到ODU帧的净荷区。其中，不同路业务数据被映射到不同业务帧。
具体地，在每个承载周期中，发送端根据S403中所确定的固定位置图案，将承载第三业务数据的业务帧映射到该m1个特定位置的净荷块。将承载第四业务数据的业务帧映射到该m2个特定位置的净荷块。这两个步骤的执行顺序可以不分先后。
在每个承载周期中，发送端将每个承载第五业务数据或第六业务数据的业务帧映射到非特定位置的净荷块中未被占用的任意位置的净荷块。
S405～S407：可以参考上述S205～S207。
S408：接收端根据ODU帧的净荷区与承载周期之间的对应关系，识别出承载周期。并从该承载周期中解析得到业务帧，然后对业务帧进行解映射，得到第三至第六业务数据。
例如，接收端可以对一个承载周期中携带第三业务数据的支路端口标识的净荷块中映射的业务帧进行解映射，得到第三业务数据帧。接收端可以对一个承载周期中携带第四业务数据的支路端口标识的净荷块中映射的业务帧进行解映射，得到第四业务数据帧。
例如，接收端可以对一个承载周期中携带第五业务数据的支路端口标识的净荷块中映射的业务帧进行解映射，得到第五业务数据帧。接收端可以对一个承载周期中携带第六业务数据的支路端口标识的净荷块中映射的业务帧进行解映射，得到第六业务数据帧。
本实施例提供的技术方案的有益效果可以参考图8和图10所示的实施例的有益效果。
基于上文中所描述的任意一个实施例，可选地，发送端可以向接收端发送第二信息。第二信息用于指示一个承载周期中目标位置的净荷块在所述ODU帧的净荷区中的位置。 这样，接收端可基于第二信息确定该承载周期在ODU帧的净荷区中的起始位置，从而快速确定连续的承载周期边界。
其中，一个承载周期中的目标位置可以是发送端和接收端预先约定的位置。可选地，每个承载周期中的目标位置相同，当然不同承载周期中的目标位置也可以不同。为了便于实现，通常的实现方式可以为：每个承载周期中目标位置的净荷块均是该承载周期中的首个净荷块(或称为起始净荷块)。
可选地，第二信息携带在ODU帧所包括的OPU开销中或者ODU开销中，如携带在该目标位置的净荷块(如该首个净荷块)所在的ODU帧所包括的OPU开销或者ODU开销中。
在一种实现方式中，可以定义净荷块起始开销(payload block start，PBS)。PBS可以放置在当前的OPU开销区的任意保留位，且PBS所占的比特数可以根据需要指示的一个承载周期中的首个净荷块的可能的位置的总数量灵活设置。
例如，结合图3中所示的ODUk帧，PBS可以位于ODUk帧的第1行第15列的低6比特和16列的全部8个比特，共计14比特，如图14所示。图14中示意出了ODU帧#i～ODU帧#i+x(即第i个ODU帧至第i+x个ODU帧)的结构示意图，i和x均是大于或等于1的整数，图14是基于图3进行绘制的。在图14中，一个承载周期包括n个净荷块，且编号依次是#1～#n，1≤j≤n，j和n均是整数。图14中的虚线所示的箭头用于表示ODU帧#i中的PBS指示的是：ODU帧#i中编号为#1的净荷块在该ODU帧的净荷区的位置。
可以理解的是，14比特的PBS的取值范围可以表示成十进制数0～15232。在一个示例中，可以采用全0表示一个承载周期中的首个净荷块不在当前ODU帧的净荷区，采用1～15232分别表示一个承载周期中的首个净荷块在当前ODU帧净荷的第1～15232个字节。
上述主要从方法的角度对本申请实施例提供的方案进行了介绍。为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对发送端或接收端进行功能模块的划分，例如可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
如图15所示，为本申请实施例提供的一种OTN中的数据传输装置150的结构示意图。作为一个示例，该装置150可以是上文中的发送端。作为一个示例，该装置150可以用于执行图6、图9、图11或图13所示的方法中发送端所执行的步骤。
该装置150包括处理单元1501和发送单元1502。其中，处理单元1501用于执行以下步骤：将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块；其中，该多个连续的净荷块占用ODU帧的净荷区。将第二类业务数据映射到该多个连续的净荷块中的除该特定位置的净荷块之外的任意位置的净荷块。以及，将ODU帧映射到光传输单元 OTU帧或FlexO帧中。发送单元1502用于发送该OTU帧或FlexO帧。例如，结合图6，处理单元1501具体用于执行S104～S105；发送单元1502具体用于执行S106。例如，结合图9，处理单元1501具体用于执行S204～S205；发送单元1502具体用于执行S206。例如，结合图11，处理单元1501用于执行S304～S305；发送单元1502具体用于执行S306。例如，结合图13，处理单元1501用于执行S404～S405；发送单元1502具体用于执行S406。
可选地，发送单元1502还用于：发送第一信息。第一信息用于指示该特定位置的净荷块在所述多个连续的净荷块中的位置。具体地，第一信息放置在OPU开销中或ODU开销中。
可选地，处理单元1501具体用于：将第一类业务数据映射到第一业务帧，将第一业务帧映射到该特定位置的净荷块。和/或，将第二类业务数据映射到第二业务帧，将第二业务帧映射到该多个连续的净荷块中的除所述特定位置的净荷块之外的任意位置的净荷块。其中，业务帧包括开销和净荷。开销包括映射信息，该映射信息用于表征将业务数据映射到业务帧时所采用的映射规则。该净荷包括业务数据。例如，结合图11，处理单元1501具体可以用于执行S304。例如，结合图13，处理单元1501具体可以用于执行S404。
可选地，发送单元1502还用于发送第二信息。该信息用于指示多个连续的净荷块中的首个净荷块在ODU帧的净荷区中的位置。具体地，第二信息放置在OPU开销或ODU开销中。
可选地，处理单元1501还用于，根据第一类业务数据的比特速率和单个净荷块的比特速率，确定该特定位置的净荷块的数量。然后，根据所确定的所述特定位置的净荷块的数量，确定该特定位置的净荷块在该多个连续的净荷块中的位置。例如，结合图6，处理单元1501具体用于执行S302和S303。例如，结合图9，处理单元1501具体用于执行S202和S203。
可选地，第一类业务数据包括第三业务数据和第四业务数据。该情况下，处理单元1501具体用于：将第三业务数据映射到该多个连续的净荷块中的第一整数个特定位置的净荷块。以及，将第四业务数据映射到该多个连续的净荷块中的第二整数个特定位置的净荷块。例如，结合图9，处理单元1501具体用于执行S204中映射第三和第四业务数据的步骤。例如，结合图13，处理单元1501具体用于执行S404中映射第三和第四业务数据的步骤。
可选地，第二类业务数据包括第五业务数据和第六业务数据。该情况下，处理单元1501具体用于：按照第五业务数据与第六业务数据的优先级顺序，以及轮询方式中的至少一种，将第五业务数据和第六业务数据映射到该多个连续的净荷块中的除该特定位置的净荷块之外的任意位置的净荷块。例如，结合图9，处理单元1501具体用于执行S204中映射第五和第六业务数据的步骤。例如，结合图13，处理单元1501具体用于执行S404中映射第五和第六业务数据的步骤。
关于上述可选方式的具体描述参见前述的方法实施例，此处不再赘述。此外，上述提供的任一种装置150的解释以及有益效果的描述均可参考上述对应的方法实施例，不予赘述。
如图16所示，为本申请实施例提供的一种OTN中的数据传输装置160的结构示意图。作为一个示例，该装置160可以是上文中的接收端。作为一个示例，该装置160可 以用于执行图6、图9、图11或图13所示的方法中接收端所执行的步骤。
该装置160包括接收单元1601和处理单元1602。其中，接收单元1601用于接收OTU帧或FlexO帧。处理单元1602用于执行以下步骤：对该OTU帧或FlexO帧进行解映射，得到ODU帧。其中，ODU帧的净荷区的多个连续的净荷块中特定位置的净荷块承载第一类业务数据。该多个连续的净荷块中的除该特定位置的净荷块之外的净荷块承载第二类业务数据。然后，从该多个连续的净荷块中获取第一类业务数据和第二类业务数据。例如，结合图6，接收单元1601具体用于执行S106所对应的接收步骤。处理单元1602具体可以用于执行S107～S108。例如，结合图9，接收单元1601具体用于执行S206所对应的接收步骤。处理单元1602具体用于执行S207～S208。例如，结合图11，接收单元1601具体用于执行S306所对应的接收步骤。处理单元1602具体用于执行S307～S308。例如，结合图13，接收单元1601具体用于执行S406所对应的接收步骤。处理单元1602具体用于执行S407～S408。
可选地，处理单元1602具体用于：将第一目标净荷块中承载的业务数据作为第一类业务数据。第一目标净荷块是该多个连续的净荷块中的且携带所述第一类业务数据的支路端口标识的净荷块。和/或，将第二目标净荷块中承载的业务数据作为第二类业务数据。第二目标净荷块是该多个连续的净荷块中的且携带第二类业务数据的支路端口标识的净荷块。
可选地，接收单元1601还用于，接收第一信息。第一信息用于指示该特定位置的净荷块在该多个连续的净荷块中的位置。该情况下，处理单元1602具体用于：将第三目标净荷块中承载的业务数据作为第一类业务数据。第三目标净荷块是该多个连续的净荷块中的且位于第一信息所指示的位置的净荷块。具体地，第一信息携带在OPU开销中或者ODU开销中。
可选地，处理单元1602还用于：根据第一类业务数据的比特速率和单个净荷块的比特速率，确定该特定位置的净荷块的数量。然后，根据预定义规则，确定该特定位置的净荷块在该多个连续的净荷块中的位置。该情况下，处理单元1602具体用于：将第四目标净荷块中承载的业务数据作为第一类业务数据。第四目标净荷块是该多个连续的净荷块中的且位于根据该预定义规则所确定的位置的净荷块。
可选地，处理单元1602具体用于：对该多个连续的净荷块进行解映射，得到第一业务帧和第二业务帧。其中，业务帧包括开销和净荷。该开销包括映射信息，该映射信息用于表征将业务数据映射到业务帧时所采用的映射规则。该净荷包括业务数据。然后，将对第一业务帧进行解映射得到的业务数据作为第一类业务数据。将对第二业务帧进行解映射得到的业务数据作为第二类业务数据。
可选地，接收单元1601还用于，接收第二信息。第二信息用于指示该多个连续的净荷块中的首个净荷块在ODU帧的净荷区中的位置。然后，根据第二信息，确定该首个净荷块在ODU帧的净荷区中的位置。具体地，第二信息携带在OPU开销中或者ODU开销中。
可选地，第一类业务数据包括第三业务数据和第四业务数据。处理单元1602具体用于：将该多个连续的净荷块中的第一整数个特定位置的净荷块上承载的业务数据作为第三业务数据。以及，将该多个连续的净荷块中的第二整数个特定位置净荷块上承载的业务数据作为第四业务数据。
关于上述可选方式的具体描述参见前述的方法实施例，此处不再赘述。此外，上述提供的任一种装置160的解释以及有益效果的描述均可参考上述对应的方法实施例，不再赘述。
需要说明的是，上述各个单元对应执行的动作仅是具体举例，各个单元实际执行的动作参照上述基于图11所述的实施例的描述中提及的动作或步骤。还需要说明的是，各单元在图2所示的OTN硬件结构图中，可能位于线路板中。对此，本申请不做限制。
还需要说明的是，上述处理单元、发送单元和接收单元和通信单元也可以替换为处理器、发送器和接收器。还需要说明的是，发送单元可以是仅具备发送功能或具备收发两种功能的光模块，接收单元可以是仅具备接收功能或具备收发两种功能的光模块。或者，上述多个单元的功能均由处理器执行。对此，本申请不做限制。
需要说明的是，上文中所描述的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。该存储器可以集成在处理器中，也可以位于处理器之外，独立存在。
本申请实施例还提供了一种芯片。该芯片中集成了用于实现上述处理器的功能的电路和一个或者多个接口。当该芯片中集成了存储器时，该芯片通过该接口与光模块连接，从而利用光模块来发送上述方法实施例中提及的OTU帧或FlexO帧给其他通信装置，或者从光模块接收其他通信装置发送的OTU帧或FlexO帧。当该芯片中未集成存储器时，可以通过该接口与外置的存储器连接，该芯片根据外置的存储器中存储的程序代码来实现上述实施例中通信装置(发送端或接收端)内部执行的动作，并借助跟其连接光模块来发送和接收OTU帧或Flex帧。可选地，芯片支持的功能可以包括基于图6、图9、图11和图13所述的实施例中发送端或接收端的处理动作，此处不再赘述。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可通过程序来指令相关的硬件完成。所述的程序可以存储于一种计算机可读存储介质中。上述提到的存储介质可以是只读存储器，随机接入存储器等。上述处理单元或处理器可以是中央处理器，通用处理器、特定集成电路(application specific integrated circuit，ASIC)、微处理器(digital signal processor，DSP)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。
本申请实施例还提供了一种包含指令的计算机程序产品，当该指令在计算机上运行时，使得计算机执行上述实施例中的任意一种方法。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
应注意，本申请实施例提供的上述用于存储计算机指令或者计算机程序的器件，例如但不限于，上述存储器、计算机可读存储介质和通信芯片等，均具有非易失性(non-transitory)。
在实施所要求保护的本申请过程中，本领域技术人员通过查看附图、公开内容、以及所附权利要求书，可理解并实现公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。

Claims (30)

  1. 一种光传送网OTN中的数据传输方法，其特征在于，包括：
    将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块；其中，所述多个连续的净荷块占用光数据单元ODU帧的净荷区；
    将第二类业务数据映射到所述多个连续的净荷块中的除所述特定位置的净荷块之外的任意位置的净荷块；
    将所述ODU帧映射到光传输单元OTU帧或灵活OTN(FlexO)帧中；
    发送所述OTU帧或FlexO帧。
  2. 根据权利要求1所述的方法，其特征在于，所述第一类业务数据包括第一业务数据，所述多个连续的净荷块为一个承载周期；所述第一业务数据在第一承载周期中占用的净荷块的位置与在第二承载周期中占用的净荷块的位置相同。
  3. 根据权利要求1所述的方法，其特征在于，所述第二类业务数据包括第二业务数据，所述多个连续的净荷块为一个承载周期，所述第二业务数据在第一承载周期中占用的净荷块的位置与在第二承载周期中占用的净荷块的位置不同。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述特定位置的净荷块在所述多个连续的净荷块中均匀分布。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，承载所述第一类业务数据的净荷块中携带所述第一类业务数据的支路端口标识；和/或，承载所述第二类业务数据的净荷块中携带所述第二类业务数据的支路端口标识。
  6. 根据权利要求1至4任一项所述的方法，其特征在于，所述方法还包括：发送第一信息，所述第一信息用于指示所述特定位置的净荷块在所述多个连续的净荷块中的位置。
  7. 根据权利要求6所述的方法，其特征在于，所述第一信息携带在所述ODU帧所包括的OPU开销中或者ODU开销中。
  8. 根据权利要求1至7任一项所述的方法，其特征在于，
    所述将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块包括：将所述第一类业务数据映射到第一业务帧，将所述第一业务帧映射到所述特定位置的净荷块；
    和/或，所述将第二类业务数据映射到所述多个连续的净荷块中的除所述特定位置的净荷块之外的任意位置的净荷块包括：将所述第二类业务数据映射到第二业务帧，将所述第二业务帧映射到所述多个连续的净荷块中的除所述特定位置的净荷块之外的任意位置的净荷块；
    其中，业务帧包括开销和净荷，所述开销包括映射信息，所述映射信息用于表征将业务数据映射到所述业务帧时所采用的映射规则，所述净荷包括业务数据。
  9. 根据权利要求8所述的方法，其特征在于，所述第一业务帧的大小和所述第二业务帧的大小都等于净荷块的大小的整数倍。
  10. 根据权利要求9所述的方法，其特征在于，所述第一业务帧的大小和所述第二业务帧的大小都等于一个净荷块的大小。
  11. 根据权利要求1至10任一项所述的方法，其特征在于，所述方法还包括：发 送第二信息，所述第二信息用于指示所述多个连续的净荷块中的首个净荷块在所述ODU帧的净荷区中的位置。
  12. 根据权利要求11所述的方法，其特征在于，所述第二信息携带在所述ODU帧所包括的OPU开销中或者ODU开销中。
  13. 根据权利要求1至12任一项所述的方法，其特征在于，
    所述第一类业务数据包括时分复用TDM业务数据，且所述第二类业务数据包括固定速率的分组PKT-CBR业务数据和可变速率的分组PKT-VBR业务数据；
    或者，所述第一类业务数据包括TDM业务数据和PKT-CBR业务数据，且所述第二类业务数据包括PKT-VBR业务数据。
  14. 根据权利要求1至13任一项所述的方法，其特征在于，在所述将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块之前，所述方法还包括：
    根据所述第一类业务数据的比特速率和单个净荷块的比特速率，确定所述特定位置的净荷块的数量；
    根据所确定的所述特定位置的净荷块的数量，确定所述特定位置的净荷块在所述多个连续的净荷块中的位置。
  15. 根据权利要求1至14任一项所述的方法，其特征在于，所述第一类业务数据包括第三业务数据和第四业务数据；所述将第一类业务数据映射到多个连续的净荷块中特定位置的净荷块，包括：
    将所述第三业务数据映射到所述多个连续的净荷块中的第一整数个特定位置的净荷块；
    将所述第四业务数据映射到所述多个连续的净荷块中的第二整数个特定位置的净荷块。
  16. 根据权利要求1至15任一项所述的方法，其特征在于，所述第二类业务数据包括第五业务数据和第六业务数据；所述将第二类业务数据映射到所述多个连续的净荷块中的除所述特定位置的净荷块之外的任意位置的净荷块，包括：
    按照所述第五业务数据与所述第六业务数据的优先级顺序，以及轮询方式中的至少一种，将所述第五业务数据和所述第六业务数据映射到所述多个连续的净荷块中的除所述特定位置的净荷块之外的任意位置的净荷块。
  17. 一种光传送网OTN中的数据传输方法，其特征在于，包括：
    接收光传输单元OTU帧或灵活OTN(FlexO)帧；
    对所述OTU帧或FlexO帧进行解映射，得到光数据单元ODU帧；其中，所述ODU帧的净荷区的多个连续的净荷块中特定位置的净荷块承载第一类业务数据，所述多个连续的净荷块中的除所述特定位置的净荷块之外的净荷块承载第二类业务数据；
    从所述多个连续的净荷块中获取所述第一类业务数据和所述第二类业务数据。
  18. 根据权利要求17所述的方法，其特征在于，所述第一类业务数据包括第一业务数据，所述多个连续的净荷块为一个承载周期；所述第一业务数据在第一承载周期中占用的净荷块的位置与在第二承载周期中占用的净荷块的位置相同。
  19. 根据权利要求17所述的方法，其特征在于，所述第二类业务数据包括第二业务数据，所述多个连续的净荷块为一个承载周期，所述第二业务数据在第一承载周期 中占用的净荷块的位置与在第二承载周期中占用的净荷块的位置不同。
  20. 根据权利要求17至19任一项所述的方法，其特征在于，所述特定位置的净荷块在所述多个连续的净荷块中均匀分布。
  21. 根据权利要求17至20任一项所述的方法，其特征在于，所述从所述多个连续的净荷块中获取所述第一类业务数据和所述第二类业务数据，包括：
    将第一目标净荷块中承载的业务数据作为所述第一类业务数据，所述第一目标净荷块是所述多个连续的净荷块中的且携带所述第一类业务数据的支路端口标识的净荷块；和/或，将第二目标净荷块中承载的业务数据作为所述第二类业务数据，所述第二目标净荷块是所述多个连续的净荷块中的且携带所述第二类业务数据的支路端口标识的净荷块。
  22. 根据权利要求17至20任一项所述的方法，其特征在于，所述方法还包括：
    接收第一信息，所述第一信息用于指示所述特定位置的净荷块在所述多个连续的净荷块中的位置；
    所述从所述多个连续的净荷块中获取所述第一类业务数据，包括：
    将第三目标净荷块中承载的业务数据作为所述第一类业务数据，所述第三目标净荷块是所述多个连续的净荷块中的且位于所述第一信息所指示的位置的净荷块。
  23. 根据权利要求22所述的方法，其特征在于，所述第一信息携带在所述ODU帧所包括的OPU开销中或者ODU开销中。
  24. 根据权利要求17至20任一项所述的方法，其特征在于，所述方法还包括：根据所述第一类业务数据的比特速率和单个净荷块的比特速率，确定所述特定位置的净荷块的数量；
    根据预定义规则，确定所述特定位置的净荷块在所述多个连续的净荷块中的位置；
    所述从所述多个连续的净荷块中获取所述第一类业务数据，包括：
    将第四目标净荷块中承载的业务数据作为所述第一类业务数据，所述第四目标净荷块是所述多个连续的净荷块中的且位于根据所述预定义规则所确定的位置的净荷块。
  25. 根据权利要求17至24任一项所述的方法，其特征在于，所述从所述多个连续的净荷块中获取所述第一类业务数据和第二类业务数据，包括：
    对所述多个连续的净荷块进行解映射，得到第一业务帧和第二业务帧；其中，所述业务帧包括开销和净荷，所述开销包括映射信息，所述映射信息用于表征将业务数据映射到所述业务帧时所采用的映射规则，所述净荷包括业务数据；
    将对所述第一业务帧进行解映射得到的业务数据作为所述第一类业务数据，并将对所述第二业务帧进行解映射得到的业务数据作为所述第二类业务数据。
  26. 根据权利要求25所述的方法，其特征在于，所述第一业务帧的大小和所述第二业务帧的大小都等于净荷块的大小的整数倍。
  27. 根据权利要求17至26任一项所述的方法，其特征在于，所述方法还包括：
    接收第二信息，所述第二信息用于指示所述多个连续的净荷块中的首个净荷块在所述ODU帧的净荷区中的位置；
    根据所述第二信息，确定所述首个净荷块在所述ODU帧的净荷区中的位置。
  28. 根据权利要求17至27任一项所述的方法，其特征在于，
    所述第一类业务数据包括时分复用TDM业务数据，且所述第二类业务数据包括固定速率的分组PKT-CBR业务数据和可变速率的分组PKT-VBR业务数据；
    或者，所述第一类业务数据包括TDM业务数据和PKT-CBR业务数据，且所述第二类业务数据包括PKT-VBR业务数据。
  29. 一种光传送网中的数据传输装置，其特征在于，包括：存储器和处理器，所述存储器用于存储计算机程序，所述处理器用于执行所述计算机程序，以执行权利要求1至16任一项所述的方法。
  30. 一种光传送网中的数据传输装置，其特征在于，包括：存储器和处理器，所述存储器用于存储计算机程序，所述处理器用于执行所述计算机程序，以执行权利要求17至28任一项所述的方法。
PCT/CN2020/086831 2019-04-30 2020-04-24 光传送网中的数据传输方法及装置 WO2020221141A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20798158.0A EP3955479A4 (en) 2019-04-30 2020-04-24 METHOD AND DEVICE FOR TRANSMITTING DATA IN AN OPTICAL TRANSPORT NETWORK
US17/513,438 US11967992B2 (en) 2019-04-30 2021-10-28 Data transmission method and apparatus in optical transport network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910365275.8A CN111865887B (zh) 2019-04-30 2019-04-30 光传送网中的数据传输方法及装置
CN201910365275.8 2019-04-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/513,438 Continuation US11967992B2 (en) 2019-04-30 2021-10-28 Data transmission method and apparatus in optical transport network

Publications (1)

Publication Number Publication Date
WO2020221141A1 true WO2020221141A1 (zh) 2020-11-05

Family

ID=72965940

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/086831 WO2020221141A1 (zh) 2019-04-30 2020-04-24 光传送网中的数据传输方法及装置

Country Status (4)

Country Link
US (1) US11967992B2 (zh)
EP (1) EP3955479A4 (zh)
CN (2) CN111865887B (zh)
WO (1) WO2020221141A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113949743A (zh) * 2021-11-22 2022-01-18 烽火通信科技股份有限公司 Odu净荷承载方法及系统
CN116192634A (zh) * 2022-12-14 2023-05-30 北京格林威尔科技发展有限公司 一种数据传输方法和装置

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115515033A (zh) * 2019-09-30 2022-12-23 华为技术有限公司 一种光传送网中的业务处理的方法、装置和系统
CN112929355A (zh) * 2021-01-29 2021-06-08 中兴通讯股份有限公司 一种光传送网的安全管理信息处理方法及装置
CN115134036A (zh) * 2021-03-26 2022-09-30 中国移动通信有限公司研究院 业务数据传输方法、装置、相关设备及存储介质
WO2022241639A1 (zh) * 2021-05-18 2022-11-24 华为技术有限公司 映射方法和映射系统
CN116112829A (zh) * 2021-11-09 2023-05-12 深圳市中兴微电子技术有限公司 光传送网的映射复用方法、装置、电子设备及存储介质
CN116264587A (zh) * 2021-12-13 2023-06-16 华为技术有限公司 一种数据传输的方法以及相关装置
CN114245241B (zh) * 2021-12-22 2023-11-03 烽火通信科技股份有限公司 一种延时自适应的bmp映射实现方法及系统
CN116489537A (zh) * 2022-01-14 2023-07-25 华为技术有限公司 一种光传送网中的业务处理的方法、装置和系统
WO2023151483A1 (zh) * 2022-02-11 2023-08-17 华为技术有限公司 数据帧的处理方法和装置
CN117376739A (zh) * 2022-06-29 2024-01-09 深圳市中兴微电子技术有限公司 一种端口业务映射处理方法、装置、存储介质及电子装置
CN117353820A (zh) * 2022-07-04 2024-01-05 中兴通讯股份有限公司 超100g电中继的控制方法、控制器以及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101384093A (zh) * 2008-09-28 2009-03-11 华为技术有限公司 业务数据映射方法和装置及复映射方法
CN101841749A (zh) * 2009-03-18 2010-09-22 华为技术有限公司 数据传输方法、通信装置及通信系统
US20120134674A1 (en) * 2010-11-30 2012-05-31 Electronics And Telecommunications Research Institute Apparatus and method for mapping a client signal
CN102783178A (zh) * 2012-05-15 2012-11-14 华为技术有限公司 一种光传送网的数据处理方法、相关设备及系统
US9473832B2 (en) * 2014-11-13 2016-10-18 Fujitsu Limited GCC0 tunneling over an OTN transport network

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6765928B1 (en) * 1998-09-02 2004-07-20 Cisco Technology, Inc. Method and apparatus for transceiving multiple services data simultaneously over SONET/SDH
CN100596043C (zh) * 2004-08-26 2010-03-24 华为技术有限公司 实现低速信号在光传输网络中透明传送的方法和装置
CN1881845B (zh) * 2006-05-15 2010-05-12 中兴通讯股份有限公司 实现多路多种数据业务汇聚传送的装置及其方法
CN101834688B (zh) * 2009-03-09 2011-08-31 华为技术有限公司 光传送网中的映射、解映射方法及装置
CN102026045B (zh) * 2009-09-17 2014-12-03 华为技术有限公司 数据帧的发送处理和接收处理方法、装置和系统
US9054832B2 (en) * 2009-12-08 2015-06-09 Treq Labs, Inc. Management, monitoring and performance optimization of optical networks
CN107040314A (zh) * 2016-02-03 2017-08-11 中兴通讯股份有限公司 一种业务传送的方法及装置
CN109981209B (zh) * 2017-12-28 2022-01-28 中兴通讯股份有限公司 光传送网中业务发送、接收方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101384093A (zh) * 2008-09-28 2009-03-11 华为技术有限公司 业务数据映射方法和装置及复映射方法
CN101841749A (zh) * 2009-03-18 2010-09-22 华为技术有限公司 数据传输方法、通信装置及通信系统
US20120134674A1 (en) * 2010-11-30 2012-05-31 Electronics And Telecommunications Research Institute Apparatus and method for mapping a client signal
CN102783178A (zh) * 2012-05-15 2012-11-14 华为技术有限公司 一种光传送网的数据处理方法、相关设备及系统
US9473832B2 (en) * 2014-11-13 2016-10-18 Fujitsu Limited GCC0 tunneling over an OTN transport network

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113949743A (zh) * 2021-11-22 2022-01-18 烽火通信科技股份有限公司 Odu净荷承载方法及系统
CN116192634A (zh) * 2022-12-14 2023-05-30 北京格林威尔科技发展有限公司 一种数据传输方法和装置

Also Published As

Publication number Publication date
CN114866618A (zh) 2022-08-05
CN111865887B (zh) 2022-05-13
US11967992B2 (en) 2024-04-23
CN111865887A (zh) 2020-10-30
EP3955479A4 (en) 2022-06-08
US20220052762A1 (en) 2022-02-17
EP3955479A1 (en) 2022-02-16

Similar Documents

Publication Publication Date Title
WO2020221141A1 (zh) 光传送网中的数据传输方法及装置
US11234055B2 (en) Service data processing method and apparatus
US11233571B2 (en) Method for processing low-rate service data in optical transport network, apparatus, and system
US11700083B2 (en) Method and apparatus for processing service data in optical transport network
US11082199B2 (en) Data transmission method in optical network and optical network device
US9225462B2 (en) Method, apparatus and system for transmitting and receiving client signals
WO2020034964A1 (zh) 客户业务数据传送方法、装置、光传送网设备及存储介质
US11245491B2 (en) Method and apparatus for transmitting optical transport unit signal
WO2020192533A1 (zh) 一种业务数据的处理方法及装置
CN111989933B (zh) 光传送网中的数据传输方法及装置
WO2023134508A1 (zh) 一种光传送网中的业务处理的方法、装置和系统
WO2024109725A1 (zh) 数据映射方法、数据解映射方法及相关设备
US9647761B1 (en) Flexible rate communication signalling
WO2023221966A1 (zh) 一种传输数据的方法和装置
WO2024051586A1 (zh) 一种光传送网中的数据帧的处理方法、装置和系统
WO2023151483A1 (zh) 数据帧的处理方法和装置
WO2023083254A1 (zh) 一种光信号传送方法及装置
WO2024109580A1 (zh) 数据传输的方法和装置
WO2023232097A1 (zh) 业务数据处理方法和装置
WO2023231764A1 (zh) 业务数据处理的方法和装置
CN116488768A (zh) 开销信息传输方法、通信装置和系统
EP2784956B1 (en) Asymmetric OTN network traffic support

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020798158

Country of ref document: EP

Effective date: 20211110