WO2019071369A1 - 光网络中数据传输方法及光网络设备 - Google Patents

光网络中数据传输方法及光网络设备 Download PDF

Info

Publication number
WO2019071369A1
WO2019071369A1 PCT/CN2017/105306 CN2017105306W WO2019071369A1 WO 2019071369 A1 WO2019071369 A1 WO 2019071369A1 CN 2017105306 W CN2017105306 W CN 2017105306W WO 2019071369 A1 WO2019071369 A1 WO 2019071369A1
Authority
WO
WIPO (PCT)
Prior art keywords
service data
synchronization information
data stream
optical
transmitted
Prior art date
Application number
PCT/CN2017/105306
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 PCT/CN2017/105306 priority Critical patent/WO2019071369A1/zh
Priority to PCT/CN2018/072144 priority patent/WO2019071870A1/zh
Priority to EP18866197.9A priority patent/EP3687088A4/en
Priority to CN201880065536.8A priority patent/CN111201728B/zh
Publication of WO2019071369A1 publication Critical patent/WO2019071369A1/zh
Priority to US16/843,520 priority patent/US11082199B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H04L7/0075—Arrangements for synchronising receiver with transmitter with photonic or optical means
    • 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
    • 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
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0647—Synchronisation among TDM nodes
    • H04J3/065—Synchronisation among TDM nodes using timestamps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • 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/0028—Local loop
    • 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/0075—Connection-oriented
    • 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
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0658—Clock or time synchronisation among packet nodes
    • H04J3/0661—Clock or time synchronisation among packet nodes using timestamps
    • H04J3/0667—Bidirectional timestamps, e.g. NTP or PTP for compensation of clock drift and for compensation of propagation delays

Definitions

  • the present application relates to the field of wireless communications, and in particular, to a data transmission method and an optical network device in an optical network.
  • the current 5th Generation (5G) wireless technology is in the process of gradual development and commercialization, mainly for Enhanced Mobile Broadband (eMBB), MassiveMachine Type Communication (mMTC) and high reliability and low latency.
  • Communication Ultra-Reliable and Low-Latency Communication, uRLLC
  • OTN Optical Transport Network
  • OAM optical Transport Network
  • TCM Tandem Connection Monitoring
  • FEC out-of-band Forward Error Correction
  • the wireless service is forwarded by means of transparent transmission, for example, the common public radio interface (CPRI) service bits are directly mapped to the flexible data optical data unit (Optical Data Unit). -flex, ODUflex), and then multiplex the ODUflex to the optical transport unit k (OTUk) for transmission.
  • CPRI common public radio interface
  • ODUflex flexible data optical data unit
  • OFTUk optical transport unit k
  • the present invention provides a data transmission method and an optical network device in an optical network, which are used to solve the problem that the time synchronization accuracy is not high in the prior art.
  • the application provides a data transmission method in an optical network, including:
  • the first device acquires first synchronization information from the first service data flow, and determines a service data flow to be transmitted;
  • the first device generates second synchronization information according to the first synchronization information
  • the first device maps the second synchronization information and the to-be-transmitted service data stream to an optical bearer container
  • the first device transmits the optical bearing container.
  • the first device obtains the first synchronization information from the first service data flow, and determines the service data flow to be transmitted, including:
  • the first device acquires first synchronization information from the first service data stream
  • the first device deletes the first synchronization information in the first service data flow to obtain the service data flow to be transmitted.
  • the first device deletes the first synchronization information in the first service data flow, and after obtaining the service data flow to be transmitted, the method further includes:
  • the first device marks a location of the first synchronization information in the to-be-transmitted service data stream.
  • the service data stream to be transmitted is the first service data stream.
  • the first device mapping the second synchronization information and the to-be-transmitted service data stream to the optical bearer container includes:
  • mapping by the first device, the second synchronization information to a time slot corresponding to the second synchronization information in the optical bearer container, and mapping the to-be-transmitted service data flow to the optical bearer container The time slot corresponding to the traffic data stream to be transmitted.
  • the first device mapping the second synchronization information and the to-be-transmitted service data stream to the optical bearer container includes:
  • mapping by the first device, the second synchronization information to an overhead area in the optical bearer, and mapping the to-be-transmitted service data flow to the corresponding to-be-transmitted service data flow in the optical bearer Time slot.
  • the optical carrier container comprises: a flexible optical transport network frame structure
  • the flexible optical transmission frame structure includes: an alignment indication, an overhead area, and a payload area; the payload area is divided into a plurality of time slots.
  • the present application provides an optical network device, the device comprising a processor and a transceiver for supporting the first aspect and the method mentioned in the various possible designs of the first aspect.
  • the transceiver is operative to perform the receiving and transmitting actions in the method
  • the processor is operative to support other processing steps of the above method.
  • the application provides a data transmission method in an optical network, including:
  • the second device receives the optical bearing container
  • the second device generates fourth synchronization information according to the third synchronization information
  • the second device inserts the fourth synchronization information into the second service data stream to obtain a third service data stream.
  • the second device inserts the fourth synchronization information into the second service data stream to obtain a third service data stream, including:
  • the second device replaces the original synchronization information by using the fourth synchronization information to obtain a third service data stream.
  • the second device inserts the fourth synchronization information into the second service data stream to obtain a third service data stream, including:
  • the second device inserts the fourth synchronization information into the second service data stream according to a location identifier of the original synchronization information in the second service data stream, to obtain The third business data stream.
  • the present application provides an optical network device, the device comprising a processor and a transceiver for supporting the method of the third aspect and the various possible designs of the third aspect. Specifically, wherein the receipt The transmitter is operative to perform the receiving and transmitting actions in the method, and the processor is operative to support other processing steps of the above method.
  • the present application provides a computer storage medium for storing computer software instructions for use in the apparatus mentioned in the second aspect or the fourth aspect above, comprising a program designed to perform the above aspects.
  • the application provides a system comprising the optical network device provided by the second aspect and the fourth aspect.
  • the first device obtains the first synchronization information from the first service data stream, determines the service data stream to be transmitted, and generates the second synchronization according to the first synchronization information.
  • the information maps the second synchronization information and the service data stream to be transmitted to the optical bearer container, and sends the optical bearer container.
  • the second device may obtain the second service data flow and the third synchronization information in the optical bearer, and then generate fourth synchronization information according to the third synchronization information, and insert the fourth synchronization information into the second service data flow.
  • the third service data stream is obtained, and the third service data stream is sent, thereby improving the time synchronization precision.
  • FIG. 1 is a schematic diagram of a possible application scenario of an embodiment of the present application
  • FIG. 2 is a schematic diagram of a hardware structure of a possible optical transmission network device
  • FIG. 3 is a schematic flowchart of a data transmission method in an optical network according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of service transmission in a 5G preamble network according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of an optical bearing container according to an embodiment of the present application.
  • FIG. 6 is a schematic structural view of a light carrying container according to another embodiment of the present application.
  • FIG. 7 is a schematic structural view of a light carrying container according to another embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of an optical bearing container according to another embodiment of the present application.
  • FIG. 9 is a schematic diagram of time slot distribution in an optical bearing container according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of a sequence of time slots in an optical bearing container according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of a slot overhead indication according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a slot overhead according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of an optical network device according to an embodiment of the present disclosure.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems, as the network architecture evolves and the new service scenario occurs.
  • OTN Optical Transport Network
  • An OTN is usually connected by multiple devices through optical fibers. It can be composed of different topology types such as line type, ring shape and mesh type according to specific needs.
  • FIG. 1 is a schematic diagram of a possible application scenario of an embodiment of the present application.
  • OTN 5G pre-transmission network as shown in Figure 1.
  • the network includes a plurality of OTN nodes, such as NE#A, NE#B, NE#C, NE#D and the like as shown in FIG.
  • a three-way 5G wireless service enhanced public radio interface (eCPRI) is connected to the node NE#A.
  • NE#B accesses 2 channels of 5G wireless service eCPRI.
  • the eCPRI is connected to the eCPRI wireless device (eRE) of the corresponding 5G wireless network.
  • Each of the nodes NE#C and NE#D is connected to one channel 5G wireless service eCPRI, and is connected to the eCPRI wireless device controller (eREC) of the 5G wireless network.
  • eCPRI wireless device controller
  • These eCPRI services are transmitted through the OTN network to implement interworking between 5G wireless devices such as eRE and eREC.
  • an OTN device herein may refer to the OTN node in FIG.
  • an OTN device includes a power supply, a fan, and an auxiliary board, and may also include a tributary board, a circuit board, a cross board, an optical layer processing board, and a system control and communication type board.
  • a network device that is a core node may not have a tributary board.
  • a network device that is an edge node may have multiple tributary boards.
  • the power supply is used to power the OTN equipment and may include primary and backup power supplies.
  • the fan is used to dissipate heat from the device.
  • Auxiliary boards are used to provide external alarms or access auxiliary functions such as an external clock.
  • the tributary board, the cross board and the circuit board are mainly used to process the electrical layer signals of the OTN.
  • the tributary board is used for receiving and transmitting various customer services, such as SDH service, packet service, Ethernet service, and pre-transmission service.
  • the tributary board can be divided into a customer side optical module and a signal processor.
  • the client side optical module may be an optical transceiver for receiving and/or transmitting a client signal.
  • the signal processor is used to implement mapping and demapping processing of the client signal to the ODU frame.
  • the cross-board is used to implement the exchange of ODU frames to complete the exchange of one or more types of ODU signals.
  • the circuit board mainly implements processing of the line side ODU frame.
  • 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 transmitting an ODU signal.
  • the signal processor is used to implement multiplexing and demultiplexing of the ODU frame on the line side, or mapping and demapping processing.
  • 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 commands can be sent to the corresponding boards.
  • a specific component for example, a signal processor
  • the present application does not impose any limitation. It should be noted that the embodiment of the present application does not impose any limitation on the type of the board included in the device, and the specific functional design and quantity of the board.
  • FIG. 3 is a schematic flowchart of a data transmission method in an optical network according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of service transmission in a 5G preamble network according to an embodiment of the present application.
  • the method includes:
  • the first device acquires first synchronization information from the first service data flow, and determines a service data flow to be transmitted.
  • the first device is the OTN device, and the first service data stream may be sent by a 5G wireless device or the like connected to the OTN device.
  • the eRE, the eREC, and the like in FIG. 1 are not limited herein.
  • the service data stream sent by the second device may include three parts: eCPRI user data, Control and Management (C&M) information, and synchronization information. These three parts are all encapsulated into MAC frames in the Media Access Control (MAC) layer.
  • the physical (PHY) layer performs Ethernet physical coding processing, and then transmits through a standard Ethernet interface, for example, 10GE, 25GE Ethernet interface, or the like.
  • the first device may consider that the first service data stream is a 10GE or 25GE Ethernet data stream.
  • the synchronization information in this application may be time synchronization information.
  • the synchronization information may include: time synchronization information, phase synchronization information, and frequency synchronization information. That is, the time, frequency, and phase between the devices can be synchronized.
  • the process of acquiring the first synchronization information is as follows: the first device parses the first service data stream, and first obtains a data stream in a physical layer coding format, for example, a 66B code block data stream, from which the synchronization message is identified and the synchronization information is extracted. .
  • a physical layer coding format for example, a 66B code block data stream
  • the first device may identify that the synchronization message is in the data stream of the physical layer coding format, where the first device identifies the start code block in the data stream corresponding to the Ethernet frame (for example, the 66B code block data corresponding to the Ethernet frame).
  • the start code block of the stream, and the corresponding field of the identifier synchronization message is viewed from the data code block (for example, the D code block) in the subsequent Ethernet frame, and if it is the synchronization message, the data stream corresponding to the Ethernet frame is used. All code blocks between the starting code block and the next Ethernet frame tail code block (for example, T code block) are extracted and the synchronization information is parsed.
  • the first device further decodes the data stream of the physical layer coding format (for example, the 66B code block data stream), restores the MAC frame data stream in the MAC layer format, and identifies the corresponding field of the synchronization message in the MAC frame, if Synchronize the message, extract the MAC frame, and parse the synchronization information.
  • the physical layer coding format for example, the 66B code block data stream
  • the data information may be located between multiple synchronization information.
  • the identification process if a synchronization message is not recognized, no processing is performed.
  • the first device generates second synchronization information according to the first synchronization information.
  • the main purpose of this step is to regenerate the synchronization information.
  • the first device may use the 1588 time synchronization protocol to perform synchronization information regeneration according to the extracted first synchronization information and local clock information, and based on a flexible OTN interface (FlexO) frame header as a timestamp reference point. .
  • FlexO flexible OTN interface
  • the synchronization information extracted by the first device from the first service data stream may include: a precision time protocol (PTP) and a synchronization status message (SSM), where the PTP is used. Used to transfer high-precision clock frequency, clock phase, and time. SSM is used to transfer information such as the quality of the clock source.
  • the first device calculates a path delay between the path delay and the master-slave clock according to the extracted first synchronization information and the local clock information, synchronizes the local clock (slave clock) to the master clock, and regenerates the inclusion based on the FlexO frame header as a timestamp reference.
  • High-precision clock frequency, clock phase, and time information such as PTP packets and SSM messages containing information such as clock source quality.
  • the second synchronization information includes the regenerated PTP packet and the SSM packet. That is to say, the second synchronization information is jointly determined according to the first synchronization information and the local clock information.
  • the FlexO frame is only an example, and may also be other OTN interfaces (OTN frames).
  • the first device maps the second synchronization information and the to-be-transmitted service data stream to the optical bearer container.
  • the first device may map the second synchronization information to the time slot corresponding to the second synchronization information in the optical bearer container, and map the service data flow to be transmitted to the time slot corresponding to the service data flow to be transmitted in the optical bearer container.
  • the first device maps the second synchronization information to the overhead area in the optical bearer container, and maps the service data flow to be transmitted to the time slot corresponding to the service data flow to be transmitted in the optical bearer container.
  • the first device maps the to-be-transmitted service data flow to a Generic Mapping Procedure (GMP) or an Idle Mapping Procedure (IMP) to
  • GMP Generic Mapping Procedure
  • IMP Idle Mapping Procedure
  • the optical data unit-flex (ODUflex) is mapped and the second synchronization information is mapped to the overhead area of the ODUflex.
  • the ODUflex is mapped to the optical data tributary unit Fn.ts (Optical Data Tributary Unit-Fn.ts, ODTUFn.ts), and the ODTUFn.ts are multiplexed into the optical bearer container, and corresponding overhead is added.
  • Fn.ts Optical Data Tributary Unit-Fn.ts, ODTUFn.ts
  • ODTUFn.ts represents ts time slots (Tributary slot/Timeslot, TS) of n*FlexO (n FlexO), and Fn represents n-way FlexO.
  • ODTUFn.60 represents an optical data tributary unit consisting of 60 500M time slots of an n*25G FlexO instance frame, where n is an integer greater than zero.
  • the timeslots in this application may be referred to as branch time slots, tributary time slots, time slots, etc., and are not specifically limited.
  • the first device maps the to-be-transmitted service data stream to the ODUflex through GMP or IMP, and then maps the ODUflex to the ODTUGn.ts, and the ODTUFn.ts is multiplexed to the optical bearer container, and the corresponding overhead is added.
  • the first device encapsulates the second synchronization information into an overhead area of the optical bearer container, or a mapped overhead area, or a dedicated time slot of the optical bearer, or a dedicated wavelength of the optical bearer.
  • the second synchronization information is encapsulated into an Optical Supervisory Channel (OSC).
  • OSC Optical Supervisory Channel
  • the first device directly maps the to-be-transmitted service data stream to ODTUFn.ts, and the ODTUFn.ts is multiplexed to the optical bearer container and adds corresponding overhead.
  • the first device synchronously encapsulates the second synchronization information into the overhead area of the optical bearer container, or the associated path mapping overhead area, or a dedicated time slot of the optical bearer container, or a dedicated wavelength of the optical bearer container, for example, the second synchronization information Encapsulated into the OSC.
  • the second synchronization information is synchronously encapsulated into the overhead area of the optical bearer container, or the associated overhead area of the optical path, or a dedicated time slot of the optical bearer, or a dedicated wavelength of the optical bearer
  • general framing may be adopted.
  • the Generic Framing Procedure-Frame Mapped (Frame-Mapped Framing Generic Procedure, GFP-F) mapping method encapsulates the second synchronization information into the GFP-F frame, and then puts it into the overhead area of the optical bearer container or the associated mapping overhead. Zone, or a dedicated time slot of the optical carrier, or a dedicated wavelength of the optical carrier.
  • the optical bearer container can carry multiple service data streams and synchronization information corresponding to each service data stream.
  • the second synchronization information is placed in the overhead area of the optical bearer (for example, the overhead area of the n*25G FlexO instance frame)
  • the position of the Optical Synchronization Message Channel (OSMC) placed in each FlexO instance frame may be prioritized.
  • MFAS Multiframe Alignment Signal
  • the first device sends the optical bearing container.
  • the second device receives the optical bearing container.
  • the second device may be an OTN device corresponding to the first device.
  • the third device is an OTN receiver device.
  • the second device demaps the second service data flow and the third synchronization information from the optical bearer.
  • the demapping process here is a reverse process in which the first device maps the second synchronization information and the service data stream to be transmitted to the optical bearer container.
  • an optical bearer container as an n*25G FlexO instance frame as an example, demultiplexing multiple ODTUFn.ts from the FlexO according to the overhead information of the FlexO, respectively, from the multi-channel ODTUFn.ts
  • the middle solution maps out the corresponding ODUflex. De-mapping the second service data from the ODUflex payload area through GMP or IMP Streaming, parsing the third synchronization information from the overhead area of the ODUflex.
  • the multi-channel ODTUFn.ts is demultiplexed from the FlexO according to the overhead information of the FlexO, respectively, from the multi-channel ODTUFn.
  • the corresponding ODUflex is mapped out in ts.
  • the second service data stream is further demapped from the ODUflex payload area by GMP or IMP.
  • the third synchronization information is parsed from the overhead area of the optical bearer, or the associated overhead area of the optical path, or a dedicated time slot of the optical bearer, or a dedicated wavelength of the optical bearer, such as an OSC.
  • the optical bearer is an n*25G FlexO instance frame
  • the second service data stream is directly demapped from the FlexO according to the overhead information of the FlexO, that is, according to the FlexO.
  • the overhead information is demultiplexed from the FlexO to the multi-channel ODTUFn.ts, and the corresponding second service data stream is demapped from the multi-channel ODTUFn.ts.
  • the third synchronization information is parsed from the overhead area of the optical bearer, or the associated overhead area of the optical path, or a dedicated time slot of the optical bearer, or a dedicated wavelength of the optical bearer, such as an OSC.
  • the third synchronization information is parsed from the overhead area of the optical bearer container, or the associated path mapping overhead area, or a dedicated time slot of the optical bearer container, or a dedicated wavelength of the optical bearer container.
  • the GFP-F frame is extracted, and the third synchronization information is parsed from the GFP-F frame, but not limited thereto.
  • the second device generates fourth synchronization information according to the third synchronization information.
  • the main purpose of the step is to regenerate the synchronization information.
  • the main purpose of the step is to regenerate the synchronization information.
  • the second device inserts the fourth synchronization information into the second service data stream to obtain a third service data stream.
  • the first device obtains the first synchronization information from the first service data flow, determines the service data flow to be transmitted, and generates the second synchronization information according to the first synchronization information, and the second synchronization information and the to-be-transmitted service.
  • the data stream is mapped to the optical carrier and the optical carrier is sent.
  • the second device may obtain the second service data stream and the third synchronization information in the optical bearer container, and may also regenerate the fourth synchronization information according to the third synchronization information, and insert the regenerated fourth synchronization information into the second
  • the service data stream is obtained as a third service data stream.
  • the synchronization information of the optical network device is realized, and the time synchronization precision is improved.
  • the transit OTN device receives the optical carrier container sent by the first device, and then the optical carrier container
  • the medium solution maps the service data and the synchronization information, and regenerates the synchronization information according to the demapping synchronization information, and then maps the regenerated synchronization information and the determined service data stream to the optical bearer container, and finally sends the optical bearer container to the next OTN device.
  • the processing performed by the OTN node in the network as shown in FIG. 1 after receiving the optical bearer container is the same, and will not be repeated here.
  • the first device obtains the first synchronization information from the first service data flow sent by the second device, and determines that the service data flow to be transmitted may specifically include: the first service data that is sent by the first device from the second device.
  • the first synchronization information is obtained in the flow, and the first device deletes the first synchronization information in the first service data flow to obtain the service data flow to be transmitted.
  • the first synchronization information may not be deleted, that is, the service data flow to be determined to be transmitted is the first service data stream. If the sending device (that is, the first device) adopts the mode, the second device replaces the synchronization information in the service data stream to be the second synchronization after receiving the second synchronization information and the service data stream to be transmitted. information.
  • the second service data stream obtained by the second device de-mapping may be the first service data stream
  • the third synchronization information may be the second synchronization information.
  • the first device deletes the first synchronization information in the first service data stream, and after obtaining the service data stream to be transmitted, may also mark the location of the first synchronization information in the service data stream to be transmitted.
  • the idle code block (for example, the IDLE code block) between the Ethernet frames may be inserted at the position where the first synchronization information is extracted.
  • a special pattern code block or the like is inserted at a position where the first synchronization information is extracted to mark the position of the first synchronization information.
  • the special pattern code block may be a pre-preset pattern code block, which is not limited herein.
  • the service data stream to be transmitted after the first synchronization information is deleted does not include the synchronization packet, and may be specifically a 66B code block stream.
  • the rate adaptation is simply performed, and the inserted IDLE code block is not necessarily at the position of the original first synchronization information.
  • the MAC frame gap padding information may be inserted at the location where the first synchronization information is extracted, or the MAC idle frame or the like may be inserted to mark the first synchronization information. s position.
  • the service data stream to be transmitted after the first synchronization information is deleted does not include the synchronization packet, and may be specifically a MAC frame data stream.
  • the inserted MAC frame gap filling information, the MAC idle frame, and the like are not necessarily at the position of the original first synchronization information.
  • the second device inserts the fourth synchronization information into the second service data flow to obtain the third service data flow, and the following situations exist:
  • the second service data stream does not include the synchronization information, that is, the first device deletes the synchronization information in the first service data stream as in the foregoing embodiment. Then, the second device inserts the fourth synchronization information into the location of the synchronization information marked in the second service data stream, that is, the location of the first synchronization information inserted into the first device identifier. Specifically, the second device inserts the fourth synchronization information into the second service data stream according to the location identifier of the original synchronization information in the second service data stream, to obtain the third service data stream.
  • the location tag of the original synchronization information may be a specific tag, or may be an idle frame or the like as a tag, and the second device only needs to know where to insert the fourth synchronization information.
  • the second device replaces the IDLE code block with the fourth synchronization information based on the data stream of the physical layer format; or the second device replaces the special pattern code block with the fourth synchronization information.
  • the second device replaces the MAC idle frame with the fourth synchronization information; or the second device replaces the MAC frame gap filling information with the fourth synchronization information.
  • the IDLE code block may not be in the position of the original first synchronization information, and the fourth synchronization information may not be in the position of the original first synchronization information after replacing the DLE code block, which is not limited in this application.
  • the MAC frame gap filling information and the MAC idle frame are not necessarily at the position of the original first synchronization information, and the fourth synchronization information may not be at the position of the original first synchronization information after replacing the MAC frame gap filling information or the MAC idle frame.
  • the second service data stream includes synchronization information, that is, the foregoing first synchronization information. Then, the second device replaces the original synchronization information in the second service data stream by using the fourth synchronization information.
  • the optical bearer container in the present application may include a flexible optical transport network frame structure, such as: n*25G FlexO instance frame, n*50G FlexO instance frame, n*100G FlexO instance frame, and the like.
  • Other OTN frames such as an optical transport unit Cn (OTUCn), an optical transport unit k (Optical Transport Unit-k, OTUk), and the like.
  • OTNn optical transport unit
  • k optical transport unit-k
  • the n*25G FlexO can transmit a multi-service service data stream, and the service data stream to be transmitted sent by the first device can be one of the service data streams.
  • n*25G FlexO instance frame is different from the flexible OTN interface–Short reach (FlexO-SR) defined in the current standard G.709.1. Specifically, n*100G FlexO-SR In each case, each FlexO-SR is 100G, and the optical transport unit C (OTUC) signal is synchronously mapped to complete the bearer of the OTUCn signal. It does not perform time slot division, cannot carry small granular services, and cannot mix and carry multiple different rate services.
  • the optical bearer container n*25G FlexO instance frame selected in this application is extended on the basis of FlexO-SR, introduces the slot concept, and asynchronous mapping, which can realize mixed bearer of multi-channel service data streams with different rates, and multiple channels.
  • the n*25G FlexO instance frame is essentially a transmission interface, including n logical interfaces, wherein a 25G FlexO instance frame is the basic frame of the transmission interface. .
  • Each FlexO instance frame is divided into 48 500 megabytes (M) time slots, and the n*25G FlexO instance frame contains a total of 48*n 500M time slots.
  • FIG. 5 is a schematic structural diagram of an optical bearing container according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a light carrying container according to another embodiment of the present application.
  • the n*25G FlexO instance frame may specifically include: an Alignment Marker (AM), an overhead (OH) area, and a payload area, and a total of 128 lines and 5140 bit columns.
  • the payload area can be divided into multiple time slots so that synchronization information and service data streams are mapped to corresponding time slots.
  • the AM is 256 bits
  • the OH area is 256 bits
  • the payload area is (128*5140-512) bits.
  • the 25G FlexO instance frame is divided into 48 time slots in its payload area based on a 16-byte granularity, each time slot having a rate of about 500M.
  • Each 25G FlexO instance frame payload area contains 48*107 16-byte blocks, such that each time slot has exactly 107 16-bytes in each 25G FlexO instance frame.
  • each super line includes 5140*16B.
  • FIG. 7 is a schematic structural diagram of a light carrying container according to another embodiment of the present application. The structure of the overhead area in the n*25GFlexO instance frame is shown in FIG.
  • the overhead area of the n*25G FlexO instance frame of the present application adds the following overhead to the existing standard: Trail Trace Identifier (TTI) overhead, state overhead, and bit interleave parity.
  • TTI Trail Trace Identifier
  • BIP-8 Check Interrupted Parity-8
  • BEI Back Error Indication
  • DM Delay Measurement
  • PSI Payload Structure Indication
  • TSOH trajectory overhead
  • OMFI Optical Multiframe Identifer
  • the TTI cost, the state cost, the BIP-8 cost, the BEI cost, and the DM cost belong to the channel layer monitoring overhead.
  • the PSI overhead is a multiplex section overhead.
  • the TTI overhead occupies two bytes in each 8-frame multiframe (consisting of 8 FlexO instance frames) of each FlexO, which may be the overhead area in the second FlexO instance frame of the 8-frame multiframe. 4th byte and 5th byte.
  • the state overhead occupies 3 bits in each FlexO instance frame, located in the 6th to 8th bits of the 2nd byte of the overhead area in each FlexO instance frame.
  • the BEI overhead occupies 4 bits in each 8 frame multiframe of each FlexO, and may be located in the 2nd to 5th bits of the 2nd byte of the overhead area in the first FlexO instance frame of the 8 frame multiframe.
  • the BIP-8 overhead occupies 1 byte in each 8-frame multiframe of each FlexO, which may be the 6th byte of the overhead area in the second FlexO instance frame of the 8 frame multiframe.
  • the DM overhead occupies 1 byte in each 8 frame multiframe of each FlexO, and can be located in the 4th byte of the overhead area in the third FlexO instance frame of the 8 frame multiframe.
  • PSI overhead One byte in each 8-frame multiframe of each FlexO, which can be located in the third byte of the overhead area in the third FlexO instance frame of the 8-frame multiframe, used to indicate the time in the FlexO instance frame The gap is occupied by various services.
  • the OMFI overhead occupies 3 bits in each 8-frame multiframe of each FlexO, and can be located in the 38th to 40th bits of the overhead area in the first FlexO instance frame of the 8-frame multiframe, which has a value range of 0. To 5, the value of the OMFI overhead for each 8-frame multiframe is incremented by one.
  • the TSOH occupies 4 bytes in each FlexO instance frame of each FlexO, and can be located in the 29th to 32nd bytes of the overhead area of each FlexO instance frame, specifically, one time slot overhead corresponding to each time slot. Instructions can be made via OMFI and MFAS.
  • the overhead area further includes: Multi-frame Alignment (MFAS) overhead, Reserved/unused (RES) overhead, PHY/member map (MAP) overhead, and Group Identification (GID). Overhead, Cyclic Redundancy Check (CRC) overhead, PHY/member Identification (PID) overhead, FlexO Communications Channel (FCC), Optical Transport Unit C (OTUC Availability, AVAIL) overhead OTN Synchronization Message Channel (OSMC) overhead.
  • MFAS Multi-frame Alignment
  • RES Reserved/unused
  • MAP PHY/member map
  • GID Group Identification
  • CRC Cyclic Redundancy Check
  • PHY/member Identification PHY/member Identification
  • FCC FlexO Communications Channel
  • OTUC Availability FlexO Communications Channel
  • AVAIL Optical Transport Unit C
  • OSMC Synchronization Message Channel
  • FIG. 8 is a schematic structural diagram of a light carrying container according to another embodiment of the present application.
  • the multiframe can be indicated by the 6, 00, 8 bits (denoted as MFAS [678]) of "OMFI Overhead” and "MFAS Overhead” in the above overhead area.
  • OMFI binary 101
  • MFAS [678] Binary 111, representing the 48th frame.
  • the ODUflex is mapped to the ODTUFn.ts, and then the ODTUFn.ts are multiplexed to the optical bearer container, which can be specifically described with reference to FIG. 8 as follows:
  • the 25GE service is mapped to ODUflex and represented by ODUflex (25GE).
  • ODUflex (25GE) is mapped to ODTUGn.48 (composed of 48 500M slots of n*25G FlexO) through GMP, and then ODTUFn.48 is multiplexed to n*25G FlexO, where ODTUFn.48 occupies n*25G FlexO 48 500M time slots.
  • FIG. 9 is a schematic diagram of a time slot distribution in an optical bearer container according to an embodiment of the present disclosure
  • FIG. 10 is a schematic diagram of a time slot sequence in an optical bearer container according to an embodiment of the present disclosure.
  • the n*25G FlexO can be divided into 48 500M time slots.
  • the numbering and sequence of these 48 time slots can be seen in Figure 9 and Figure 10:
  • the slot number format in this application is TS#A.B.
  • A identifies the number of the 25G FlexO instance frame, A is an integer greater than 0 and less than or equal to n; B identifies the encoding of the time slot in each 25G FlexO instance frame, B is greater than 0 and less than or equal to 48 Integer.
  • the order of time slots is: TS1.1, TS2.1, ..., TSn.1, TS1.2, TS2.2, ..., TSn.2, ..., TS1.48, TS2.48, ..., TSn.48.
  • FIG. 11 is a schematic diagram of a slot overhead indication according to an embodiment of the present application.
  • mapping multiple service data streams to an n*25G FlexO instance frame it is necessary to map the multiple service data streams to ODTUFn.ts, and then multiplex multiple ODTUFn.ts to n*25G. FlexO instance frame. That is, the first device maps multiple to-be-transmitted service data streams or multiple ODUflexs that encapsulate the service data streams to be transmitted into multiple ODTUFn.ts, and the mapping overhead is placed at the last time slot overhead position of the occupied time slots.
  • the mapping overhead refers specifically to the mapping overhead information generated when mapping the service data stream to ODTUFn.ts, and is placed in the TSOH.
  • ODTUFn.ts is composed of ts time slots inter-column insertion, a total of 48 rows of 107*N columns, each column having a size of 16 bytes. It also contains 1 TSOH, which is the slot overhead corresponding to the last slot.
  • FIG. 12 is a schematic structural diagram of a slot overhead according to an embodiment of the present disclosure.
  • the GMP mapping service data stream When the GMP mapping service data stream is sent to ODTUFn.ts, its mapping overhead is placed in the TSOH corresponding to the last slot of ODTUFn.ts.
  • the TSOH is located at the 29th to 32nd bytes of the frame overhead area of each 25G FlexO instance.
  • the TSOH specifically includes: 14 bits of Ci (i is an integer of 1 to 14, the 14 bits of Ci are represented by Cm), and 8 bits of Dj (j is an integer of 1 to 8, and the 8-bit Dj passes CnD. Representation), 8-bit CRC-8.
  • the Cm indicates the number of service data flows mapped to ODTUFn.ts, and the unit is 16 bytes.
  • CnD indicates the service clock information generated when the service data stream is mapped to ODTUFn.ts.
  • CRC-8 collectively covers Cm and CnD, and the specific generator polynomial can reuse the existing definition of G.709, such as x 8 + x 3 + x 2 +1, where x represents the specific variable of the generator polynomial.
  • FIG. 13 is a schematic structural diagram of an optical network device according to an embodiment of the present disclosure. As shown in FIG. 13, the device includes a processor 21 and a transceiver 22.
  • a memory 20 may also be included, wherein the memory 20, the processor 21, and the transceiver 22 may be connected by a bus 24.
  • the transceiver 22 can be connected to an antenna.
  • the transceiver 22 can receive information sent by other devices through the antenna and send the information to the processor 21 for processing; in the opposite direction, the processor 21 processes the data and transmits it to the other device through the transceiver 22.
  • transceiver 22 can include a transmitter and a receiver.
  • the transceiver is a separate device that can have both transmit and receive functions.
  • the device can be used to implement the optical network device with different behaviors mentioned in the foregoing embodiments, and the method provided by the foregoing method embodiment is implemented, and the implementation principle and the technical effect are similar, and details are not described herein again.
  • the optical network device is the foregoing first device, and is configured to perform an action performed by the foregoing first device.
  • the optical network device is the foregoing second device, and is configured to perform an action performed by the foregoing second device.
  • the units may be located in the circuit board and/or the tributary board.
  • the present invention does not impose any limitation on the position of the board in which the respective units are specifically described.
  • the frame structure employed by the device or node is the various frame structures described in the "Overall Overview" section.
  • the design of the specific frame structure can be differently selected according to needs, and the present invention does not impose any limitation on this.
  • the processing unit or processor may be a central processing unit, a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device. , transistor logic, hardware components, or any combination thereof. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the computer program product includes one or more computer instructions.
  • the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Optics & Photonics (AREA)
  • Computing Systems (AREA)
  • Electromagnetism (AREA)
  • Time-Division Multiplex Systems (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)
  • Optical Communication System (AREA)

Abstract

本申请提供一种光网络中数据传输方法及光网络设备，该方法包括：第一设备从第一业务数据流中获取第一同步信息，并确定待传输业务数据流；根据所述第一同步信息生成第二同步信息；将所述第二同步信息和所述待传输业务数据流映射至光承载容器；发送所述光承载容器。第二设备接收光承载容器，从所述光承载容器中解映射第二业务数据流和第三同步信息，根据所述第三同步信息生成第四同步信息；将所述第四同步信息插入所述第二业务数据流，得到第三业务数据流。从而实现了时间同步精度的提高。

Description

光网络中数据传输方法及光网络设备 技术领域
本申请涉及无线通信领域，尤其涉及一种光网络中数据传输方法及光网络设备。
背景技术
当前第五代(5th Generation，5G)无线技术正处于逐步制定和商用化过程，主要面向满足增强移动宽带(Enhanced Mobile Broadband，eMBB)、海量连接(MassiveMachine Type Communication，mMTC)和高可靠低时延通信(Ultra-Reliable andLow-Latency Communication，uRLLC)三大类应用场景。低时延、大带宽、网络切片、高精度时间同步等成为第五代无线技术的关键技术特征，同时也是对承载传送网络提出的主要需求。光传送网(Optical Transport Network，OTN)作为下一代传送网的核心技术，具备丰富的操作、管理与维护(Operation Administration and Maintenance，OAM)能力、强大的串联连接监视(Tandem Connection Monitoring，TCM)能力和带外前向错误纠正(Forward Error Correction，FEC)能力，能够实现大容量业务的灵活调度和管理。因为这些特性，OTN技术日益成为骨干传送网的主流技术，也将用于5G承载。
目前通过OTN传送无线业务的过程中，通过透传的方法完成无线业务的前传，例如直接将通用公共无线接口(Common Public Radio Interface，CPRI)业务比特同步映射到灵活速率光数据单元(Optical Data Unit-flex，ODUflex)，之后将ODUflex复用到光传输单元k(Optical Transport Unit－k，OTUk)进行传送，但是由于OTN传送上下行路径，以及内部处理等存在不对称问题，因此上下行传输的延时有较大差异，因此仍然采用透传的方法，无法提供高精度的时间同步性能，不能满足5G业务的需求。
发明内容
本申请提供一种光网络中数据传输方法及光网络设备，用于解决现有技术中时间同步精度不高的问题。
第一方面，本申请提供一种光网络中数据传输方法，包括：
第一设备从第一业务数据流中获取第一同步信息，并确定待传输业务数据流；
所述第一设备根据所述第一同步信息生成第二同步信息；
所述第一设备将所述第二同步信息和所述待传输业务数据流映射至光承载容器；
所述第一设备发送所述光承载容器。
在一种可能的设计中，所述第一设备从第一业务数据流中获取第一同步信息，并确定待传输业务数据流，包括：
所述第一设备从第一业务数据流中获取第一同步信息；
所述第一设备将所述第一业务数据流中的所述第一同步信息删除，得到所述待传输业务数据流。
在一种可能的设计中，所述第一设备将所述第一业务数据流中的所述第一同步信息删除，得到所述待传输业务数据流之后，还包括：
所述第一设备在所述待传输业务数据流中标记所述第一同步信息的位置。
在一种可能的设计中，所述待传输业务数据流为所述第一业务数据流。
在一种可能的设计中，所述第一设备将所述第二同步信息和所述待传输业务数据流映射至光承载容器，包括：
所述第一设备将所述第二同步信息映射至所述光承载容器中所述第二同步信息对应的时隙、以及将所述待传输业务数据流映射至所述光承载容器中所述待传输业务数据流对应的时隙。
在一种可能的设计中，所述第一设备将所述第二同步信息和所述待传输业务数据流映射至光承载容器，包括：
所述第一设备将所述第二同步信息映射至所述光承载容器中的开销区、以及将所述待传输业务数据流映射至所述光承载容器中所述待传输业务数据流对应的时隙。
在一种可能的设计中，所述光承载容器包括：灵活光传送网帧结构；
所述灵活光传送帧结构包括：对齐指示、开销区以及净荷区；所述净荷区划分为多个时隙。
第二方面，本申请提供一种光网络设备，所述设备包括处理器和收发器，用于支持所述第一方面和所述第一方面各种可能的设计中提及的方法。具体地，其中所述收发器用于执行所述方法中的接收和发送动作，而处理器用于支持上述方法的其他处理步骤。
第三方面，本申请提供一种光网络中数据传输方法，包括：
第二设备接收光承载容器；
所述第二设备从所述光承载容器中解映射第二业务数据流和第三同步信息；
所述第二设备根据所述第三同步信息生成第四同步信息；
所述第二设备将所述第四同步信息插入所述第二业务数据流，得到第三业务数据流。
在一种可能的设计中，所述第二设备将所述第四同步信息插入所述第二业务数据流，得到第三业务数据流，包括：
若所述第二业务数据流包含原同步信息，则所述第二设备采用所述第四同步信息替换所述原同步信息，得到第三业务数据流。
在一种可能的设计中，所述第二设备将所述第四同步信息插入所述第二业务数据流，得到第三业务数据流，包括：
若所述第二业务数据流无同步信息，则所述第二设备根据所述第二业务数据流中原同步信息的位置标记将所述第四同步信息插入所述第二业务数据流中，得到第三业务数据流。
第四方面，本申请提供一种光网络设备，所述设备包括处理器和收发器，用于支持所述第三方面和所述第三方面各种可能的设计中提及的方法。具体地，其中所述收 发器用于执行所述方法中的接收和发送动作，而处理器用于支持上述方法的其他处理步骤。
第五方面，本申请提供一种计算机存储介质，用于存储为上述第二方面或第四方面所提及的设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第六方面，本申请提供一种系统，所述系统包含第二方面和第四方面提供的光网络设备。
本申请提供的光网络中数据传输方法及光网络设备中，第一设备从第一业务数据流中获取第一同步信息，并确定待传输业务数据流，进而根据第一同步信息生成第二同步信息，将第二同步信息和待传输业务数据流映射至光承载容器，并发送光承载容器。第二设备收到光承载容器后可以获取光承载容器中的第二业务数据流和第三同步信息，进而根据第三同步信息生成第四同步信息，将第四同步信息插入第二业务数据流得到第三业务数据流，再发送第三业务数据流，从而提高了时间同步精度。
附图说明
下面将参照所示附图对本申请实施例进行更详细的描述：
图1为本申请实施例一种可能的应用场景示意图；
图2为一种可能的光传送网络设备的硬件结构示意图；
图3为本申请一实施例提供的光网络中数据传输方法流程示意图；
图4为本申请一实施例提供的5G前传网络中业务传输示意图；
图5为本申请一实施例提供的光承载容器结构示意图；
图6为本申请另一实施例提供的光承载容器结构示意图；
图7为本申请又一实施例提供的光承载容器结构示意图；
图8为本申请另一实施例提供的光承载容器结构示意图；
图9为本申请一实施例提供的光承载容器中时隙分布示意图；
图10为本申请一实施例提供的光承载容器中时隙顺序示意图；
图11为本申请一实施例提供的时隙开销指示示意图；
图12为本申请一实施例提供的时隙开销结构示意图；
图13为本申请一实施例提供的光网络设备结构示意图。
具体实施方式
本申请实施例描述的网络架构以及业务场景是为了更加清楚地说明本申请实施例的技术方案，并不构成对本申请实施例提供的技术方案的限制。本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题同样适用。
总体概述：
本申请的实施例适用于光网络，例如：光传送网络(Optical transport Network，OTN)。一个OTN通常由多个设备通过光纤连接而成，可以根据具体需要组成如线型、环形和网状等不同的拓扑类型。
图1为本申请实施例一种可能的应用场景示意图。如图1所示的OTN 5G前传网 络包括多个OTN节点，例如图1中所示的NE#A，NE#B，NE#C，NE#D等OTN节点。
在节点NE#A中接入了3路5G无线业务增强通用公共无线接口(enhancedcommon public radio interface，eCPRI)。类似地，NE#B中接入2路5G无线业务eCPRI。其中，eCPRI和对应的5G无线网络的eCPRI无线设备(eRE)相连。
在节点NE#C和NE#D中各自接入1路5G无线业务eCPRI，和5G无线网络的eCPRI无线设备控制器(eREC)相连。这些eCPRI业务通过OTN网络进行传送，实现eRE、eREC等5G无线设备互通。
图2为一种可能的光传送网络设备的硬件结构示意图。这里的OTN设备可以指图1中的OTN节点。具体地，一个OTN设备包括电源、风扇、辅助类单板，还可能包括支路板、线路板、交叉板、光层处理单板，以及系统控制和通信类单板。
需要说明的是，根据具体的需要，每个设备具体包含的单板类型和数量可能不相同。例如：作为核心节点的网络设备可能没有支路板。作为边缘节点的网络设备可能有多个支路板。其中，电源用于为OTN设备供电，可能包括主用和备用电源。风扇用于为设备散热。辅助类单板用于提供外部告警或者接入外部时钟等辅助功能。支路板、交叉板和线路板主要是用于处理OTN的电层信号。其中，支路板用于实现各种客户业务的接收和发送，例如SDH业务、分组业务、以太网业务和前传业务等。更进一步地，支路板可以划分为客户侧光模块和信号处理器。其中，客户侧光模块可以为光收发器，用于接收和/或发送客户信号。信号处理器用于实现对客户信号到ODU帧的映射和解映射处理。交叉板用于实现ODU帧的交换，完成一种或多种类型的ODU信号的交换。线路板主要实现线路侧ODU帧的处理。具体地，线路板可以划分为线路侧光模块和信号处理器。其中，线路侧光模块可以为线路侧光收发器，用于接收和/或发送ODU信号。信号处理器用于实现对线路侧的ODU帧的复用和解复用，或者映射和解映射处理。系统控制和通信类单板用于实现系统控制和通信。具体地，可以通过背板从不同的单板收集信息，或者将控制指令发送到对应的单板上去。需要说明的是，除非特殊说明，具体的组件(例如：信号处理器)可以是一个或多个，本申请不做任何限制。还需要说明的是，本申请实施例不对设备包含的单板类型，以及单板具体的功能设计和数量做任何限制。
本申请为了提高OTN传输的时间同步精度，提出一种新的光网络中数据传输方法。
图3为本申请一实施例提供的光网络中数据传输方法流程示意图。图4为本申请一实施例提供的5G前传网络中业务传输示意图。
如图3所示，该方法包括：
S301、第一设备从第一业务数据流中获取第一同步信息，并确定待传输业务数据流。
其中，第一设备为上述OTN设备，第一业务数据流可以是与OTN设备连接的5G无线设备等发送的，例如图1中的eRE、eREC等，本申请不作限制。
如图4所示，第二设备发送的业务数据流可以包括三部分内容：eCPRI用户数据、控制管理(Control and Management，C&M)信息以及同步(synchronization)信息。这三部分内容在媒体接入控制(Media Access Control，MAC)层全部封装为MAC帧， 并在物理(PHY)层进行以太物理编码处理，之后通过标准以太接口发送，例如10GE、25GE的以太接口等发送。相应地，第一设备接收到第一业务数据流后，可以认为第一业务数据流是10GE或25GE的以太数据流。
需要说明的是，本申请中同步信息可以是时间同步信息。进一步地，该同步信息可以包括：时间同步信息、相位同步信息、频率同步信息。即可以要求设备之间时间、频率、相位都同步。
具体获取第一同步信息的过程如下：第一设备对第一业务数据流进行解析处理，首先得到物理层编码格式的数据流，例如66B码块数据流，从中识别出同步报文并提取同步信息。
更具体地，第一设备从物理层编码格式的数据流中识别出同步报文可以是：第一设备识别以太帧对应的数据流中的起始码块(例如以太帧对应的66B码块数据流的起始码块)，并从后续以太帧中的数据码块(例如D码块)中，查看标识同步报文的对应字段，若为同步报文，则将上述以太帧对应的数据流中的起始码块到下一个以太帧尾码块(例如T码块)之间的所有码块提取出来，并解析出同步信息。
或者，第一设备将物理层编码格式的数据流(例如66B码块数据流)进一步解码，恢复MAC层格式的MAC帧数据流，通过MAC帧中标识同步报文的对应字段进行识别，若为同步报文，则将该MAC帧提取出来，并解析出同步信息。
需要说明的是，数据信息可能位于多个同步信息之间。在识别过程中，如果识别到不是同步报文，则不做任何处理。
S302、第一设备根据第一同步信息生成第二同步信息。
该步骤的主要目的是再生同步信息。具体地，第一设备可以根据提取的第一同步信息以及本地时钟信息，并基于灵活光传送网接口(Flexible OTN interface，FlexO)帧头作为时间戳参考点，采用1588时间同步协议进行同步信息再生。
需要说明的是，第一设备从第一业务数据流中提取的同步信息可以包括：精确时间协议(precision time protocol，PTP)和同步状态信息(synchronization status message，SSM)两种报文，其中PTP用于传递高精度时钟频率、时钟相位以及时间等信息。SSM用于传递时钟源质量等信息。第一设备根据提取的第一同步信息和本地时钟信息计算路径延迟和主从时钟之间的时间差，将本地时钟(从时钟)同步到主时钟，基于FlexO帧头作为时间戳参考，重新生成包含高精度时钟频率、时钟相位以及时间等信息PTP报文以及包含时钟源质量等信息的SSM报文。第二同步信息包含重新生成的PTP报文和SSM报文。也就是说，第二同步信息是根据第一同步信息和本地时钟信息共同决定。需要说明的是，FlexO帧仅是一个示例，还可以是其它OTN接口(OTN帧)。
S303、第一设备将第二同步信息和待传输业务数据流映射至光承载容器。
其中，第一设备可以将第二同步信息映射至光承载容器中第二同步信息对应的时隙、以及将待传输业务数据流映射至光承载容器中待传输业务数据流对应的时隙。或者，第一设备将第二同步信息映射至光承载容器中的开销区、以及将待传输业务数据流映射至光承载容器中待传输业务数据流对应的时隙。
可选地，一种方式中，第一设备将待传输业务数据流通过通用映射规程(GenericMapping Procedure，GMP)或空闲映射规程(Idle Mapping Procedure，IMP)映射到 灵活速率光数据单元(Optical Data Unit-flex，ODUflex)，并将第二同步信息映射到ODUflex的开销区。进而将ODUflex映射到光数据支路单元Fn.ts(Optical Data TributaryUnit–Fn.ts，ODTUFn.ts)，ODTUFn.ts复用到光承载容器，并添加相应开销。
其中，ODTUFn.ts表示由n*FlexO(n个FlexO)的ts个时隙(Tributary slot/Timeslot，TS)组成，Fn表示n路FlexO。举例说明：ODTUFn.60，则代表由n*25G FlexO实例帧的60个500M时隙组成的光数据支路单元，其中n为大于0的整数。
本申请中的时隙可以指分支时隙、支路时隙、时隙等，具体不做限制。
可选地，另一种方式中，第一设备将待传输业务数据流通过GMP或IMP映射到ODUflex，进而将ODUflex映射到ODTUFn.ts，ODTUFn.ts复用到光承载容器，并添加相应开销。另外，第一设备将第二同步信息封装到光承载容器的开销区、或者随路映射开销区、或者光承载容器的某个专用时隙、或者光承载容器的专用波长。例如将第二同步信息封装到光监控信道(Optical Supervisory Channel，OSC)。
可选地，再一种方式中，第一设备将待传输业务数据流直接映射到ODTUFn.ts，ODTUFn.ts复用到光承载容器并添加相应开销。第一设备将第二同步信息同步封装到光承载容器的开销区、或者随路映射开销区、或者光承载容器的某个专用时隙、或者光承载容器的专用波长，例如将第二同步信息封装到OSC。
具体地，将第二同步信息同步封装到光承载容器的开销区、或者随路映射开销区、或者光承载容器的某个专用时隙、或者光承载容器的专用波长时，可以采用通用成帧规程(Generic Framing Procedure-Frame Mapped,Frame-Mapped Framing GenericProcedure，GFP-F)映射方式，将第二同步信息封装到GFP-F帧，之后再放入光承载容器的开销区、或者随路映射开销区、或者光承载容器的某个专用时隙、或者光承载容器的专用波长。
需要说明的是，光承载容器可以携带多路业务数据流，以及各路业务数据流对应的同步信息。第二同步信息放入光承载容器的开销区(例如n*25G FlexO实例帧的开销区)时，可以优先考虑放入每个FlexO实例帧的光同步信息通道(OpticalSynchronization Message Channel，OSMC)位置，通过复帧对齐信号(MultiframeAlignment Signal，MFAS)进行区别指示，不同FlexO实例帧的OSMC承载不同路的同步信息。例如MFAS＝0，该FlexO实例帧携带第1路业务数据流对应的同步信息；MFAS＝1，该FlexO实例帧携带第2路业务数据流对应的同步信息，以此类推。
S304、第一设备发送该光承载容器。
S305、第二设备接收到上述光承载容器。
这里第二设备可以是OTN设备，与第一设备相对应。可选地，第一设备为OTN发送端设备时，第三设备为OTN接收端设备。
S306、第二设备从该光承载容器中解映射第二业务数据流和第三同步信息。
这里解映射过程为第一设备将第二同步信息和待传输业务数据流映射至光承载容器的逆过程。
可选地，一种实现方式中，以光承载容器为n*25G FlexO实例帧为例，根据FlexO的开销信息从FlexO中解复用出多路ODTUFn.ts，分别从这多路ODTUFn.ts中解映射出对应的ODUflex。进而通过GMP或IMP从ODUflex净荷区解映射出第二业务数据 流、从ODUflex的开销区解析出第三同步信息。
可选地，另一种实现方式中，以光承载容器为n*25G FlexO实例帧为例，根据FlexO的开销信息从FlexO中解复用出多路ODTUFn.ts，分别从这多路ODTUFn.ts中解映射出对应的ODUflex。进而通过GMP或IMP从ODUflex净荷区解映射出第二业务数据流。另外，从光承载容器的开销区、或者随路映射开销区、或者光承载容器的某个专用时隙、或者光承载容器的专用波长，例如OSC中解析出第三同步信息。
可选地，又一种实现方式中，以光承载容器为n*25G FlexO实例帧为例，根据FlexO的开销信息从FlexO中直接解映射出多路第二业务数据流，也即根据FlexO的开销信息从FlexO中解复用出多路ODTUFn.ts，分别从这多路ODTUFn.ts中解映射出对应的第二业务数据流。另外，从光承载容器的开销区、或者随路映射开销区、或者光承载容器的某个专用时隙、或者光承载容器的专用波长，例如OSC中解析出第三同步信息。
需要说明的是，将第三同步信息从光承载容器的开销区、或者随路映射开销区、或者光承载容器的某个专用时隙、或者光承载容器的专用波长中解析出来时，可以先将GFP-F帧提取出来，进而将第三同步信息从GFP-F帧中解析出来，但不以此为限。
S307、第二设备根据第三同步信息生成第四同步信息。
该步骤的主要目的也是再生同步信息，具体过程可参见第一设备根据第一同步信息生成第二同步信息的过程，在此不再赘述。
S308、第二设备将第四同步信息插入该第二业务数据流，得到第三业务数据流。
本实施例中，第一设备从第一业务数据流中获取第一同步信息，并确定待传输业务数据流，进而根据第一同步信息生成第二同步信息，将第二同步信息和待传输业务数据流映射至光承载容器，并发送光承载容器。第二设备收到光承载容器后可以获取光承载容器中的第二业务数据流和三同步信息，也可以根据第三同步信息再生第四同步信息，并把再生的第四同步信息插入第二业务数据流，得到第三业务数据流。实现了光网络设备再生同步信息，提高时间同步精度。
需要说明的是，如果第一设备和第二设备之间还有其他OTN设备(记为“中转OTN设备”)，那么中转OTN设备接收到第一设备发送的光承载容器后，从光承载容器中解映射业务数据和同步信息，并根据解映射的同步信息再生同步信息，进而将再生的同步信息和确定发送的业务数据流一起映射到光承载容器，最后向下一OTN设备发送光承载容器。也就是说，如图1所示网络中的OTN节点在收到光承载容器后执行的处理过程相同，在此不一一赘述。
可选地，上述第一设备从第二设备发送的第一业务数据流中获取第一同步信息，并确定待传输业务数据流可以具体包括：第一设备从第二设备发送的第一业务数据流中获取第一同步信息，进而第一设备将第一业务数据流中的第一同步信息删除，得到该待传输业务数据流。
当然，也可以不删除第一同步信息，也就是说该待确定传输的业务数据流就是所述第一业务数据流。如果发送端设备(也就是第一设备)采用这种方式，第二设备在收到第二同步信息和待传输业务数据流后，会将待传输业务数据流中的同步信息替换为第二同步信息。在前述实施例的基础上，第二设备解映射得到的第二业务数据流可以是该第一业务数据流、第三同步信息可以是该第二同步信息。
进一步地，第一设备将第一业务数据流中的第一同步信息删除，得到待传输业务数据流之后，还可以在待传输业务数据流中标记该第一同步信息的位置。
需要说明的是，若第一设备从物理层编码格式的数据流识别同步报文，那么可以在提取第一同步信息的位置插入以太帧之间的空闲码块(例如IDLE码块)进行速率适配，或者，在提取第一同步信息的位置插入特殊图案码块等来标记第一同步信息的位置。特殊图案码块可以是提前预设好的图案码块，在此不作限制。删除第一同步信息后的待传输业务数据流不再包含同步报文，可以具体为66B码块流。
其中，对于插入IDLE码块的情况，也可以是在删除第一同步信息后，单纯进行速率适配，那么插入的IDLE码块不一定在原第一同步信息的位置。
或者，若第一设备从MAC层格式的MAC帧数据流中识别同步报文，那么可以在提取第一同步信息的位置插入MAC帧间隙填充信息、或者插入MAC空闲帧等来标记第一同步信息的位置。删除第一同步信息后的待传输业务数据流不再包含同步报文，可以具体为MAC帧数据流。类似地，插入的MAC帧间隙填充信息、MAC空闲帧等不一定在原第一同步信息的位置。
需要说明的是，第二设备将第四同步信息插入第二业务数据流，得到第三业务数据流，存在以下不同情况：
一种情况下，第二业务数据流中不包含同步信息，即如前述实施例中第一设备将第一业务数据流中的同步信息删除了。那么，第二设备将第四同步信息插入第二业务数据流中标记的同步信息位置，即插入到第一设备标记的第一同步信息的位置。具体地，第二设备根据第二业务数据流中原同步信息的位置标记将第四同步信息插入第二业务数据流中，得到第三业务数据流。这里原同步信息的位置标记可以是特定的标记，也可以是将空闲帧等当做标记，第二设备只需获知将第四同步信息插入哪里即可。相应地，基于物理层格式的数据流，第二设备采用第四同步信息替换IDLE码块；或者，第二设备采用第四同步信息替换特殊图案码块。或者，基于MAC层格式的数据流，第二设备采用第四同步信息替换MAC空闲帧；或者，第二设备采用第四同步信息替换MAC帧间隙填充信息。
需要说明的是，IDLE码块也可能不在原第一同步信息的位置，那么第四同步信息替换DLE码块后也可能不在原第一同步信息的位置，本申请不作限制。类似地，MAC帧间隙填充信息、MAC空闲帧也不一定在原第一同步信息的位置，第四同步信息替换MAC帧间隙填充信息或MAC空闲帧后也可能不在原第一同步信息的位置。
另一种情况下，第二业务数据流中包含同步信息，即包含前述第一同步信息。那么第二设备采用第四同步信息替换第二业务数据流中的原同步信息即可。
可选地，本申请中光承载容器可以包括灵活光传送网帧结构，例如：n*25G FlexO实例帧、n*50G FlexO实例帧、n*100G FlexO实例帧等。也可以是其他OTN帧，例如光传输单元Cn(Optical Transport Unit－Cn，OTUCn)，光传输单元k(Optical TransportUnit－k，OTUk)等。以n*25G FlexO实例帧为例，n*25G FlexO可以传输多路业务数据流，上述第一设备发送的待传输业务数据流可以是其中一路业务数据流。
n*25G FlexO实例帧不同于当前标准G.709.1中定义的n*100G灵活光传送网短距接口(Flexible OTN interface–Short reach，FlexO-SR)。具体地，n*100G FlexO-SR 中，每路FlexO-SR为100G，针对光传输单元C(Optical Transport Unit－C，OTUC)信号进行同步映射，完成OTUCn信号的承载。其没有进行时隙划分，无法承载小颗粒业务，也无法混合承载多路不同速率业务。本申请选用的光承载容器n*25G FlexO实例帧在FlexO-SR的基础上进行了扩展定义，引入时隙概念，以及异步映射，能够实现多路不同速率业务数据流的混合承载，以及多路业务数据流对应的同步信息承载。
以n*25G FlexO(n个25G的FlexO)实例帧为例，n*25G FlexO实例帧本质上是一个传输接口，包括n个逻辑接口，其中，一个25G FlexO实例帧是该传输接口的基本帧。每路FlexO实例帧划分为48个500兆(M)时隙，则n*25G FlexO实例帧共包含48*n个500M时隙。
图5为本申请一实施例提供的光承载容器结构示意图。图6为本申请另一实施例提供的光承载容器结构示意图。
如图5所示，n*25G FlexO实例帧可以具体包括：对齐指示(Alignment Marker，AM)、开销(overhead，OH)区、净荷区三部分，共128行5140比特列。净荷区可以划分为多个时隙，以便同步信息、业务数据流映射到对应的时隙。
其中AM为256比特(bit)，OH区为256比特，净荷区为(128*5140-512)比特。25G FlexO实例帧基于16字节粒度在其净荷区依次划分为48个时隙，每个时隙约500M速率。每个25G FlexO实例帧净荷区包含48*107个16字节块，这样每个时隙在每个25G FlexO实例帧中正好有107个16字节。
如图6所示，由于25G FlexO实例帧的每行为5140比特，不是16字节(B)的整数倍，为了便于展示，可以考虑组合128行作为一个超行，也即一个25G FlexO实例帧，通过超行进行展示，这样每个超行包括5140*16B。
图7为本申请又一实施例提供的光承载容器结构示意图。图7中示出了n*25GFlexO实例帧中开销区的结构。
如图7所示：本申请n*25G FlexO实例帧的开销区在现有标准基础上增加了如下开销：路径踪迹标识(Trail Trace Identifier，TTI)开销、状态(State)开销、比特间插奇偶校验-8比特(Bit Interleaved Parity-8，BIP-8)开销，后向错误指示(Back ErrorIndication，BEI)，延时测量(Delay Measurement，DM)开销；净荷结构指示(PayloadStructure Indication，PSI)开销，时隙开销(tributary slot overhead，TSOH)以及光复帧指示(Optical Multiframe Identifer，OMFI)开销。
其中，TTI开销、状态开销、BIP-8开销、BEI开销、DM开销属于通道层监控开销。PSI开销属于复用段开销。
具体地，TTI开销在每一路FlexO的每个8帧复帧(由8个FlexO实例帧构成)中占两个字节，可以是该8帧复帧的第二个FlexO实例帧中开销区的第4字节和第5字节。状态开销在每个FlexO实例帧中占3比特，位于每个FlexO实例帧中开销区的第2字节的第6到第8比特。BEI开销在每一路FlexO的每个8帧复帧中占4比特，可以位于该8帧复帧的第一个FlexO实例帧中开销区的第2字节的第2到第5比特。BIP-8开销在每一路FlexO的每个8帧复帧中占1个字节，可以是该8帧复帧的第二个FlexO实例帧中开销区的第6字节。DM开销在每一路FlexO的每个8帧复帧中占1个字节，可以位于该8帧复帧的第三个FlexO实例帧中开销区的第4字节。PSI开销 在每一路FlexO的每个8帧复帧中占1个字节，可以位于该8帧复帧的第三个FlexO实例帧中开销区的第3字节，用于指示FlexO实例帧中各时隙被各路业务占用情况。OMFI开销在每一路FlexO的每个8帧复帧中占3个比特，可以位于该8帧复帧的第一个FlexO实例帧中开销区的第38到第40比特，其取值范围为0到5，每个8帧复帧OMFI开销的值加1。TSOH在每一路FlexO的每个FlexO实例帧中占4个字节，可以位于每个FlexO实例帧开销区的第29到第32字节，具体地，每个时隙对应的一个时隙开销，可以通过OMFI和MFAS进行指示。
进一步地，开销区还包括：复帧(Multi-frame Alignment，MFAS)开销、保留(Reserved/unused，RES)开销、设备映射(PHY/member map，MAP)开销、组标识(Group Identification，GID)开销、循环冗余校验(Cyclic Redundancy Check，CRC)开销、设备标识(PHY/member Identification，PID)开销、FlexO传输通道(FlexOCommunications Channel，FCC)、光传输单元C可用(OTUC Availability，AVAIL)开销、OTN同步信息通道(OTN Synchronization Message Channel，OSMC)开销等。
图8为本申请另一实施例提供的光承载容器结构示意图。
如图8所示，在多路业务复用光承载容器时，48个25G FlexO实例帧构成一个复帧，基于16字节粒度将其划分为48个时隙，每个时隙包含5136*16字节。
可以通过上述开销区中“OMFI开销”和“MFAS开销”的6、7、8比特(记为MFAS[678])来指示复帧。具体地，OMFI开销从0开始计数，每8帧加1，在计数值达到5时再次循环计数。例如：OMFI＝二进制000、且MFAS[678]＝二进制000，代表第1帧；OMFI＝二进制000、且MFAS[678]＝二进制001，代表第2帧；依次类推，OMFI＝二进制101、且MFAS[678]＝二进制111，代表第48帧。
举例说明，前述实施例中，将ODUflex映射到ODTUFn.ts，进而ODTUFn.ts复用到光承载容器，可以参照图8具体说明如下：
例如将25GE的业务映射到ODUflex，通过ODUflex(25GE)表示。然后将ODUflex(25GE)通过GMP映射到ODTUFn.48(n*25G FlexO的48个500M时隙组成)，之后将该ODTUFn.48复用到n*25G FlexO，其中ODTUFn.48占用n*25G FlexO的48个500M时隙。
图9为本申请一实施例提供的光承载容器中时隙分布示意图，图10为本申请一实施例提供的光承载容器中时隙顺序示意图。
n*25G FlexO可以划分为48个500M时隙，这48个时隙的编号和顺序可以参见图9和图10：
如图9所示，本申请中时隙编号格式为TS#A.B。其中A标识25G FlexO实例帧的编号，A为大于0、且小于或等于n的整数；B标识在每个25G FlexO实例帧中的时隙的编码，B为大于0、且小于或等于48的整数。
如图10所示，时隙的顺序为：TS1.1、TS2.1、…、TSn.1、TS1.2、TS2.2、…、TSn.2、…、TS1.48、TS2.48、…、TSn.48。
图11为本申请一实施例提供的时隙开销指示示意图。
如前述实施例所说，当映射多路业务数据流到n*25G FlexO实例帧时，需要将多路业务数据流分别映射到ODTUFn.ts，再将多路ODTUFn.ts复用到n*25G FlexO实例 帧。也就是第一设备将多路待传输业务数据流或者多路封装了待传输业务数据流的ODUflex映射入多路ODTUFn.ts，映射开销放置在其占用时隙的最后一个时隙开销位置。
这里映射开销具体指将业务数据流映射到ODTUFn.ts时生成的映射开销信息，放置于TSOH中。
如图11所示，示出了ODTUFn.ts的结构示意，ODTUFn.ts由ts个时隙按列间插组成，共48行107*N列，每列的大小16字节。另外也包含1个TSOH，该TSOH为最后一个时隙对应的时隙开销。
图12为本申请一实施例提供的时隙开销结构示意图。
采用GMP映射业务数据流到ODTUFn.ts时，其映射开销放入ODTUFn.ts的最后一个时隙对应的TSOH。TSOH位于每个25G FlexO实例帧开销区的第29到第32字节。
如图12所示，TSOH中具体包括：14比特Ci(i为1～14的整数，该14比特Ci通过Cm表示)、8比特Dj(j为1～8的整数，该8比特Dj通过CnD表示)、8比特CRC-8。其中，Cm指示映射到ODTUFn.ts中的业务数据流数量，单位为16字节。CnD指示将业务数据流映射到ODTUFn.ts时生成的业务时钟(clock)信息。CRC-8共同覆盖Cm和CnD，具体的生成多项式可重用G.709的现有定义，例如x8+x3+x2+1，其中，x表示该生成多项式的具体变量。
图13为本申请一实施例提供的光网络设备结构示意图。如图13所示，该设备包括：处理器21和收发器22。
可选地，还可以包括存储器20，其中，存储器20、处理器21以及收发器22可以通过总线24连接。
其中，收发器22可以与天线连接。收发器22可以通过天线接收其他设备发送的信息，并将信息发送给处理器21进行处理；相反地方向上，处理器21对数据进行处理，并通过收发器22发送给其他设备。
具体地，收发器22可以包括：发送器和接收器。或者收发器为一个独立的设备，可以具备发送和接收功能。
该设备可以用于实现上述实施例提及的不同行为的光网络设备，执行前述方法实施例所提供的方法，其实现原理和技术效果类似，在此不再赘述。
在一种可能的实施方式中，该光网络设备为前述第一设备，用于执行前述第一设备执行的动作。
在另一种可能的实施方式中，该光网络设备为前述第二设备，用于执行前述第二设备执行的动作。
需要说明的是，所述各单元在图2所述的OTN硬件结构图中，可能位于线路板和/或支路板中。本发明对所述各单元具体的所述的单板位置不做任何限制。
还需要说明的是，设备或者节点所采用的帧结构为“总体概述”部分描述的各种帧结构。具体帧结构的设计，可以根据需要来进行不同的选择，本发明对此不做任何限制。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，随机接入存储器等。具体地，例如：上述处理单元或处理器可以是中央处理器，通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。上述的这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
当使用软件实现时，上述实施例描述的方法步骤可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。

Claims (20)

  1. 一种光网络中数据传输方法，其特征在于，包括：
    第一设备从第一业务数据流中获取第一同步信息，并确定待传输业务数据流；
    所述第一设备根据所述第一同步信息生成第二同步信息；
    所述第一设备将所述第二同步信息和所述待传输业务数据流映射至光承载容器；
    所述第一设备发送所述光承载容器。
  2. 根据权利要求1所述的方法，其特征在于，所述第一设备从第一业务数据流中获取第一同步信息，并确定待传输业务数据流，包括：
    所述第一设备从第一业务数据流中获取第一同步信息；
    所述第一设备将所述第一业务数据流中的所述第一同步信息删除，得到所述待传输业务数据流。
  3. 根据权利要求2所述的方法，其特征在于，所述第一设备将所述第一业务数据流中的所述第一同步信息删除，得到所述待传输业务数据流之后，还包括：
    所述第一设备在所述待传输业务数据流中标记所述第一同步信息的位置。
  4. 根据权利要求1所述的方法，其特征在于，所述待传输业务数据流为所述第一业务数据流。
  5. 根据权利要求1所述的方法，其特征在于，所述第一设备将所述第二同步信息和所述待传输业务数据流映射至光承载容器，包括：
    所述第一设备将所述第二同步信息映射至所述光承载容器中所述第二同步信息对应的时隙、以及将所述待传输业务数据流映射至所述光承载容器中所述待传输业务数据流对应的时隙。
  6. 根据权利要求1所述的方法，其特征在于，所述第一设备将所述第二同步信息和所述待传输业务数据流映射至光承载容器，包括：
    所述第一设备将所述第二同步信息映射至所述光承载容器中的开销区、以及将所述待传输业务数据流映射至所述光承载容器中所述待传输业务数据流对应的时隙。
  7. 根据权利要求1或5或6所述的方法，其特征在于，所述光承载容器包括：灵活光传送网帧结构；
    所述灵活光传送帧结构包括：对齐指示、开销区以及净荷区；所述净荷区划分为多个时隙。
  8. 一种光网络中数据传输方法，其特征在于，包括：
    第二设备接收光承载容器；
    所述第二设备从所述光承载容器中解映射第二业务数据流和第三同步信息；
    所述第二设备根据所述第三同步信息生成第四同步信息；
    所述第二设备将所述第四同步信息插入所述第二业务数据流，得到第三业务数据流。
  9. 根据权利要求8所述的方法，其特征在于，所述第二设备将所述第四同步信息插入所述第二业务数据流，得到第三业务数据流，包括：
    若所述第二业务数据流包含原同步信息，则所述第二设备采用所述第四同步信息替换所述原同步信息，得到第三业务数据流。
  10. 根据权利要求8所述的方法，其特征在于，所述第二设备将所述第四同步信息插入所述第二业务数据流，得到第三业务数据流，包括：
    若所述第二业务数据流无同步信息，则所述第二设备根据所述第二业务数据流中原同步信息的位置标记将所述第四同步信息插入所述第二业务数据流中，得到第三业务数据流。
  11. 一种光网络设备，其特征在于，所述设备包括：处理器和收发器；
    所述处理器，用于从第一业务数据流中获取第一同步信息，并确定待传输业务数据流；根据所述第一同步信息生成第二同步信息；将所述第二同步信息和所述待传输业务数据流映射至光承载容器；
    所述收发器，用于发送所述光承载容器。
  12. 根据权利要求11所述的设备，其特征在于，所述处理器，具体用于从第一业务数据流中获取第一同步信息；将所述第一业务数据流中的所述第一同步信息删除，得到所述待传输业务数据流。
  13. 根据权利要求12所述的设备，其特征在于，所述处理器，还用于在所述待传输业务数据流中标记所述第一同步信息的位置。
  14. 根据权利要求11所述的设备，其特征在于，所述待传输业务数据流为所述第一业务数据流。
  15. 根据权利要求11所述的设备，其特征在于，所述处理器，还用于将所述第二同步信息映射至所述光承载容器中所述第二同步信息对应的时隙、以及将所述待传输业务数据流映射至所述光承载容器中所述待传输业务数据流对应的时隙。
  16. 根据权利要求11所述的设备，其特征在于，所述处理器，还用于将所述第二同步信息映射至所述光承载容器中的开销区、以及将所述待传输业务数据流映射至所述光承载容器中所述待传输业务数据流对应的时隙。
  17. 根据权利要求11或15或16所述的设备，其特征在于，所述光承载容器包括：灵活光传送网帧结构；
    所述灵活光传送帧结构包括：对齐指示、开销区以及净荷区；所述净荷区划分为多个时隙。
  18. 一种光网络设备，其特征在于，所述设备包括：处理器和收发器；
    所述收发器，用于接收光承载容器；
    所述处理器，用于从所述光承载容器中解映射第二业务数据流和第三同步信息；根据所述第三同步信息生成第四同步信息；将所述第四同步信息插入所述第二业务数据流，得到第三业务数据流。
  19. 根据权利要求18所述的设备，其特征在于，所述处理器，具体用于在所述第二业务数据流包含原同步信息时，采用所述第四同步信息替换所述原同步信息，得到第三业务数据流。
  20. 根据权利要求18所述的设备，其特征在于，所述处理器，具体用于在所述第二业务数据流无同步信息时，根据所述第二业务数据流中原同步信息的位置标记将所述第四同步信息插入所述第二业务数据流中，得到第三业务数据流。
PCT/CN2017/105306 2017-10-09 2017-10-09 光网络中数据传输方法及光网络设备 WO2019071369A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2017/105306 WO2019071369A1 (zh) 2017-10-09 2017-10-09 光网络中数据传输方法及光网络设备
PCT/CN2018/072144 WO2019071870A1 (zh) 2017-10-09 2018-01-10 光网络中数据传输方法及光网络设备
EP18866197.9A EP3687088A4 (en) 2017-10-09 2018-01-10 METHOD OF DATA TRANSFER IN AN OPTICAL NETWORK AND OPTICAL NETWORK DEVICE
CN201880065536.8A CN111201728B (zh) 2017-10-09 2018-01-10 光网络中数据传输方法及光网络设备
US16/843,520 US11082199B2 (en) 2017-10-09 2020-04-08 Data transmission method in optical network and optical network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/105306 WO2019071369A1 (zh) 2017-10-09 2017-10-09 光网络中数据传输方法及光网络设备

Publications (1)

Publication Number Publication Date
WO2019071369A1 true WO2019071369A1 (zh) 2019-04-18

Family

ID=66100274

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2017/105306 WO2019071369A1 (zh) 2017-10-09 2017-10-09 光网络中数据传输方法及光网络设备
PCT/CN2018/072144 WO2019071870A1 (zh) 2017-10-09 2018-01-10 光网络中数据传输方法及光网络设备

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/072144 WO2019071870A1 (zh) 2017-10-09 2018-01-10 光网络中数据传输方法及光网络设备

Country Status (4)

Country Link
US (1) US11082199B2 (zh)
EP (1) EP3687088A4 (zh)
CN (1) CN111201728B (zh)
WO (2) WO2019071369A1 (zh)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3178187A1 (en) * 2014-08-07 2017-06-14 Coherent Logix, Incorporated Multi-partition radio frames
CN115623363A (zh) 2018-05-25 2023-01-17 华为技术有限公司 传输数据的方法和装置
CN110649986B (zh) * 2018-06-26 2022-07-19 中兴通讯股份有限公司 使用灵活光网络的业务传输方法、装置、设备及存储介质
CN112672235A (zh) * 2019-10-15 2021-04-16 中兴通讯股份有限公司 一种同步方法、装置、设备和存储介质
CN112511915A (zh) * 2020-02-28 2021-03-16 中兴通讯股份有限公司 光传送网中业务处理方法、处理装置和电子设备
US12081427B2 (en) 2020-04-20 2024-09-03 Mellanox Technologies, Ltd. Time-synchronization testing in a network element
US11234163B1 (en) * 2020-09-18 2022-01-25 Nokia Solutions And Networks Oy Dynamic eCPRI header compression
CN114531424B (zh) * 2020-10-31 2023-11-10 华为技术有限公司 业务数据传输方法、通信网络、业务接收设备及存储介质
CN112615930B (zh) * 2020-12-25 2022-08-23 北京东土科技股份有限公司 多节点数据同步分发方法、装置、设备及存储介质
US12111681B2 (en) 2021-05-06 2024-10-08 Mellanox Technologies, Ltd. Network adapter providing isolated self-contained time services
US12028155B2 (en) * 2021-11-24 2024-07-02 Mellanox Technologies, Ltd. Controller which adjusts clock frequency based on received symbol rate
US11907754B2 (en) 2021-12-14 2024-02-20 Mellanox Technologies, Ltd. System to trigger time-dependent action
CN114245241B (zh) * 2021-12-22 2023-11-03 烽火通信科技股份有限公司 一种延时自适应的bmp映射实现方法及系统
US11835999B2 (en) 2022-01-18 2023-12-05 Mellanox Technologies, Ltd. Controller which adjusts clock frequency based on received symbol rate
CN114629589B (zh) * 2022-03-21 2024-09-20 新华三半导体技术有限公司 一种数据处理装置及方法
US12095506B2 (en) * 2022-06-28 2024-09-17 Ciena Corporation Time-sliced GMP mapping with modified sigma-delta mapping function
US11917045B2 (en) 2022-07-24 2024-02-27 Mellanox Technologies, Ltd. Scalable synchronization of network devices

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101707553A (zh) * 2009-11-10 2010-05-12 华为技术有限公司 异步业务数据的传输方法、装置和系统
CN103297165A (zh) * 2013-04-28 2013-09-11 烽火通信科技股份有限公司 基于cpri帧的wdm-pon移固综合接入方法
US9288006B1 (en) * 2012-09-21 2016-03-15 Pmc-Sierra Us, Inc. Demultiplexing high-order to low-order ODU signals in an optical transport network
CN106992838A (zh) * 2016-01-21 2017-07-28 华为技术有限公司 一种传输公共无线接口信号的方法和设备

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7136388B2 (en) * 2002-06-27 2006-11-14 Alcatel Clock synchronization system and method for use in a scalable access node
CN101489157B (zh) * 2009-02-13 2011-06-08 华为技术有限公司 将业务复用映射到光通道传送单元的方法和装置
CN101997669B (zh) * 2009-08-14 2015-10-21 中兴通讯股份有限公司 光传送网承载时间同步协议时的时间校正方法及系统
CN102195885A (zh) * 2011-05-27 2011-09-21 成都市华为赛门铁克科技有限公司 报文处理方法及装置
CN103780488B (zh) * 2012-10-23 2018-07-06 中国电信股份有限公司 广播报文处理方法和设备
WO2015104054A1 (en) * 2014-01-09 2015-07-16 Telefonaktiebolaget L M Ericsson (Publ) Mapping of data into data containers
EP3462650B1 (en) * 2014-01-23 2023-10-25 Huawei Technologies Co., Ltd. Optical line terminal communication method and device with data structure
CN103986658B (zh) * 2014-05-14 2017-06-06 北京锐安科技有限公司 一种报文输出方法及装置
CN105451102B (zh) * 2014-08-22 2019-05-28 华为技术有限公司 一种处理信号的方法、装置及系统
US9893826B2 (en) * 2015-01-28 2018-02-13 Alcatel-Lucent Usa Inc. Method for retaining clock traceability over an asynchronous interface
US9525482B1 (en) * 2015-02-09 2016-12-20 Microsemi Storage Solutions (U.S.), Inc. Apparatus and method for measurement of propagation time of a data stream in a transport network
WO2019020170A1 (en) * 2017-07-25 2019-01-31 Telefonaktiebolaget Lm Ericsson (Publ) METHODS, APPARATUS AND COMPUTER-READABLE MEDIA FOR SYNCHRONIZATION OVER AN OPTICAL NETWORK
US10256909B2 (en) * 2017-08-30 2019-04-09 Ciena Corporation Systems and methods for relative phase measurement and alignment of 66B encoded signals

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101707553A (zh) * 2009-11-10 2010-05-12 华为技术有限公司 异步业务数据的传输方法、装置和系统
US9288006B1 (en) * 2012-09-21 2016-03-15 Pmc-Sierra Us, Inc. Demultiplexing high-order to low-order ODU signals in an optical transport network
CN103297165A (zh) * 2013-04-28 2013-09-11 烽火通信科技股份有限公司 基于cpri帧的wdm-pon移固综合接入方法
CN106992838A (zh) * 2016-01-21 2017-07-28 华为技术有限公司 一种传输公共无线接口信号的方法和设备

Also Published As

Publication number Publication date
WO2019071870A1 (zh) 2019-04-18
US11082199B2 (en) 2021-08-03
CN111201728A (zh) 2020-05-26
EP3687088A1 (en) 2020-07-29
US20200235905A1 (en) 2020-07-23
CN111201728B (zh) 2022-11-04
EP3687088A4 (en) 2020-11-18

Similar Documents

Publication Publication Date Title
US11082199B2 (en) Data transmission method in optical network and optical network device
US11764874B2 (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
US10462028B2 (en) Efficient ethernet signal transport and scheduling
US10771177B2 (en) Method for transmitting client signal in optical transport network, and optical transport device
US9225462B2 (en) Method, apparatus and system for transmitting and receiving client signals
CN107438028B (zh) 一种客户业务处理的方法和设备
EP4027650A1 (en) Method and device for service processing in optical transport network, and system
US8416770B2 (en) Universal service transport transitional encoding
WO2017201757A1 (zh) 一种业务传送方法和第一传送设备
US20200403698A1 (en) Method And Apparatus For Processing Ethernet Data In Optical Network, And System
US20110318001A1 (en) Method and device for sending and receiving service data
WO2019047110A1 (zh) 一种光传送网中时延测量的方法、装置和系统
CN102055727A (zh) 多业务传送网中的数据封装方法、封装设备和支路单元
WO2017181675A1 (zh) 一种以太网中数据处理的方法、设备及系统
WO2023109424A1 (zh) 一种数据传输的方法以及相关装置
US10826636B2 (en) Optical supervisory channel processing method and apparatus in optical network
WO2023232097A1 (zh) 业务数据处理方法和装置
CN118075641A (zh) 一种带宽调整方法及装置

Legal Events

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

Ref document number: 17928785

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17928785

Country of ref document: EP

Kind code of ref document: A1