WO2020177693A1 - 客户业务数据流的方法及装置、存储介质 - Google Patents

客户业务数据流的方法及装置、存储介质 Download PDF

Info

Publication number
WO2020177693A1
WO2020177693A1 PCT/CN2020/077670 CN2020077670W WO2020177693A1 WO 2020177693 A1 WO2020177693 A1 WO 2020177693A1 CN 2020077670 W CN2020077670 W CN 2020077670W WO 2020177693 A1 WO2020177693 A1 WO 2020177693A1
Authority
WO
WIPO (PCT)
Prior art keywords
block
oam overhead
oam
blocks
data stream
Prior art date
Application number
PCT/CN2020/077670
Other languages
English (en)
French (fr)
Inventor
张源斌
杨剑
古渊
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020177693A1 publication Critical patent/WO2020177693A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H04L43/026—Capturing of monitoring data using flow identification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • This application relates to the field of communications, for example, to a method and device for sending customer service data streams, and a storage medium.
  • Flexible Ethernet Flexible Ethernet (FlexE-Flexible Ethernet, FlexE) technology was formally voted by the International Organization for Standardization Optical Internet Forum (OIF) to pass relevant technical documents.
  • Flexible Ethernet technology provides a general mechanism to transmit a series of services with different Media Access Control (MAC) rates, which can be services with a single MAC with a relatively high rate or multiple MACs with a relatively low rate. The collection of services is no longer limited to services with a single MAC rate.
  • the general structure of flexible Ethernet is shown in Figure 1.
  • One feature of flexible Ethernet is to bind multiple physical layers (PHYs) of the same Ethernet to transmit services with a relatively large MAC rate. For example, three 100G Ethernet PHYs are bound to support a MAC rate of 300G services, that is, services are transmitted in multiple Ethernet PHYs.
  • PHYs physical layers
  • flexible Ethernet has an extra layer (FlexE Shim) in the MAC layer and the Physical Coding Sublayer (PCS) layer.
  • FlexE Shim a time slot structure
  • n is the number of bound Ethernet PHYs
  • each 66b block represents a 5G time slot.
  • services with different MAC rates are packed into corresponding 66b blocks in accordance with the multiple relationship with 5G. Every 20 66b blocks form a sub-slot structure (sub-Calendar), and a calendar with a size of 20*n is distributed into n sub-Calendars.
  • a flexible Ethernet group refers to a group formed by binding one to n Ethernet PHYs, as shown in Figure 1.
  • 5G bearer is a topic that is currently discussed in the industry.
  • the point-to-point technology originally defined in OIF needs to be extended to end-to-end technology.
  • Related standards have been published in the International Telecommunication Union (International Telecommunication Union).
  • Telecommunications U nion, ITU) standards organization formally established the project.
  • OAM operation, management and maintenance
  • the embodiment of the present invention provides a method and device for sending a customer service data stream, and a storage medium, so as to at least solve the problem that the current OAM overhead mechanism in related technologies cannot satisfy the end-to-end monitoring of the service.
  • a method for sending a customer service data stream including: acquiring a customer service data stream; adding OAM overhead frames to the customer service data stream; sending customer services including OAM overhead frames Data stream; the OAM overhead frame includes: at least one OAM overhead block, and the OAM overhead block includes: a data block or a control block.
  • an apparatus for sending a customer service data stream including: an acquisition module configured to acquire a customer service data stream; and an adding module configured to add OAM overhead frames to the customer service In the data stream; the sending module is configured to send a customer service data stream containing an OAM overhead frame; the OAM overhead frame includes: at least one OAM overhead block, and the OAM overhead block includes: a data block or a control block.
  • a storage medium with a computer program stored in the storage medium, and the computer program is configured to execute any of the above-mentioned client service data stream sending when running. method.
  • the customer service data stream is obtained; the OAM overhead frame is added to the customer service data stream; the customer service data stream including the OAM overhead frame is sent; the OAM overhead frame includes: at least one OAM overhead block, the The OAM overhead block includes: data block or control block.
  • Figure 1 is a schematic diagram of a general FlexE network scenario in related technologies
  • Figure 2 is a flowchart of a method for sending customer service data streams according to an embodiment of the present invention
  • Figure 3 is a structural block diagram of a device for sending customer service data streams according to an embodiment of the present invention
  • Figure 4 is a schematic diagram of a scenario according to an alternative embodiment of the present invention.
  • Fig. 5 is a schematic diagram of an OAM overhead frame structure according to an optional embodiment of the present invention.
  • FIG. 6 is a schematic diagram of customer service data flow of end-to-end monitoring information according to an optional embodiment of the present invention.
  • Fig. 7 is a schematic diagram of another OAM overhead frame structure according to an optional embodiment of the present invention.
  • Fig. 8 is a schematic diagram of an OAM overhead frame structure according to an optional embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for sending a customer service data stream according to an embodiment of the present invention. As shown in FIG. 2, the method includes the following steps.
  • Step S202 Obtain the customer service data stream.
  • Step S204 Add OAM overhead frames to the customer service data stream.
  • Step S206 Send a customer service data stream including an OAM overhead frame; the OAM overhead frame includes: at least one OAM overhead block, and the OAM overhead block includes: a data block or a control block.
  • the customer service data stream is obtained; the operation maintenance management OAM overhead frame is added to the customer service data stream; the customer service data stream including the OAM overhead frame is sent; the OAM overhead frame includes: at least one OAM overhead block
  • the OAM overhead block includes: a data block or a control block.
  • Step S204 may be implemented in multiple ways.
  • adding operation, maintenance and management OAM overhead frames to the customer service data stream can be implemented in the following ways: For each customer service, OAM overhead The frame is added between the T block and the S block of the customer service data flow. The OAM overhead frame is used for end-to-end monitoring of the customer service.
  • the S block is the initial control block in the customer service data flow.
  • T block is the termination control block in the customer service data flow.
  • the frame header block of the OAM overhead frame is a data block, and the OAM overhead frame contains a frame header identification code
  • the data block between the T block and the S block is detected and the detected data block is determined
  • the frame header identification code is included in the OAM overhead frame
  • the frame header block of the OAM overhead frame is locked; if the frame header block of the OAM overhead frame is a control block, the frame header block of the OAM overhead frame is locked by detecting the control block type.
  • the first IDLE control block or redundant sequel between the T block and the S block after the N1 first coding block When there is no IDLE control block or redundant sequel between the T block and the S block, the first IDLE control block or redundant sequel between the T block and the S block after the N1 first coding block The remaining sequel is replaced with OAM overhead block, that is, if there is no IDLE control block or redundant sequel between the current T block and S block, then the OAM overhead block cannot be inserted between the T block and the S block, then from The next IDLE control block or redundant sequel (that is, the first IDLE control block between the T block and S block after N1 first code blocks or the redundant sequel) is replaced with an OAM overhead block;
  • the difference between the T block and the S block is replaced with the header block of the OAM overhead frame;
  • N1 and N2 are both positive integers, and N2 meets the minimum period for transmitting the OAM overhead frame in the service data stream;
  • the first coding block includes at least one of the following: an S block and a T block; the second coding block includes at least one of the following: a data block and a control block.
  • the OAM overhead block and the previous OAM overhead block are separated by a predetermined number of N3 first coding blocks, and the number of the second coding blocks separated from the previous OAM overhead block is less than N4, between the T block and the S block Adding the OAM overhead block in between;
  • N3 and N4 are both positive integers, and N4 meets the minimum period for transmitting the OAM overhead frame in the service data stream;
  • the first coding block includes at least one of the following: an S block and a T block; the second coding block includes at least one of the following: a data block and a control block.
  • IDLE control block or redundant sequel addition and deletion operations on the customer service data stream may be performed after the header block of the OAM overhead frame is added to the T block and the S block.
  • This embodiment of the present invention does not do this. limited.
  • the OAM overhead block of the OAM overhead frame carries indication information, and the indication information is used to indicate whether other OAM overhead blocks are included after the OAM overhead block, and when other OAM overhead blocks are included after the OAM overhead block , Location information of the next OAM overhead block of the OAM overhead block;
  • the The header block of the OAM overhead frame is added between the T block and the S block,
  • the number of indications of the location information includes the number of third coding blocks between OAM overhead blocks; the N5 is a positive integer, and the N5 satisfies the minimum period for transmitting the OAM overhead frame in the service data stream;
  • the third coding block includes at least one of the following: S blocks, T blocks or the total number of other control blocks and data blocks that do not contain IDLE control blocks (that is, the third coding block may also be the total number of control blocks and data blocks, This control block is the other control block that does not include the IDLE control block).
  • IDLE control block or redundant sequel addition and deletion operations on the customer service data stream may be performed after the header block of the OAM overhead frame is added to the T block and the S block.
  • This embodiment of the present invention does not do this. limited.
  • bytes may also be allocated to other OAM overhead blocks, and the bytes are used to verify the other OAM overhead blocks, and the OAM overhead blocks are in the OAM overhead frame, except for the frame header block Other OAM overhead blocks.
  • OAM overhead blocks For each customer service, add at least one OAM overhead block to the customer service data stream.
  • OAM overhead blocks carry the overhead of end-to-end monitoring of the customer service, and distribute the customer service inserted into the OAM overhead block to the FlexE time slot In, the service is transmitted through the physical layer PHY.
  • At least one OAM overhead block forms an OAM overhead frame.
  • the first OAM overhead block is the OAM overhead frame header block.
  • the frame header block of the OAM overhead frame can be a data block or a control block.
  • the remaining OAM of the OAM overhead frame is a data block.
  • the frame header block of the OAM overhead frame is added to the customer service data stream every fixed number of coding blocks or at a fixed time, which meets the minimum period required to transmit OAM information in the customer service data stream.
  • the OAM overhead frame header block is a data block
  • the OAM overhead frame contains the frame header identification code
  • the frame of the OAM overhead frame is performed by detecting the data block between the T block and the S block and judging whether the data block contains the frame header identification code Header block lock; if it is a control block, the frame header block of OAM overhead frames is locked by detecting the control block type. Further, in order to increase the reliability of OAM overhead block detection, the frame header block of the OAM overhead frame is excluded For the rest of the OAM overhead blocks, some bytes can be allocated for verification.
  • the first byte is a fixed format, such as 0xF6; the first byte is the bit interleaving check of the previous OAM overhead block (Bit Interleaved Parity (BIP) 8 or Cyclic Redundancy Check (Cyclic Redundancy Check-8, CRC-8) calculation result.
  • BIP Bit Interleaved Parity
  • Cyclic Redundancy Check Cyclic Redundancy Check-8, CRC-8
  • the S block is the start control block in the customer service data stream
  • the T block is the end control block in the customer service data stream. Its coding specification complies with the IEEE802.3 standard.
  • N1 the predetermined number of data blocks N1 is separated from the previous OAM overhead block, for example, the S block or T block or the customer service code that does not contain the IDLE control block Block
  • the predetermined number of N2 coding blocks are separated from the previous OAM overhead block
  • the S block or T block separated from the previous OAM overhead frame If the number is less than N1, add the OAM overhead frame header block again between the T block and the S block in the customer service data stream.
  • the number of OAM overhead blocks contained in the OAM overhead frame and the number of reservations N1 and N2 need to be specified in advance and are a fixed value.
  • the condition selected by N2 meets the minimum period required to transmit OAM information in the customer service data stream.
  • N1 can be based on actual conditions. Need to be set; the way to add OAM overhead block includes replacing the IDLE control block or redundant sequel between the T block and the S block with the OAM overhead block.
  • the reserved number N1 is an absolute number. There is a certain offset in the implementation; or the IDLE control block or redundant sequel addition and deletion operations are performed in advance, and then the OAM overhead block is inserted at the reserved position.
  • the IDLE control block or redundant sequel addition and deletion operations are performed on the customer service data stream in advance, and the OAM overhead block is added between the T block and the S block in the customer service at the reserved position.
  • the OAM overhead frame header block is used for carrying indication information. After indicating whether the OAM overhead frame header block includes other OAM overhead blocks and the location information of the next OAM overhead block, the location information can be through the S block or T block between two adjacent OAM overhead blocks or does not include the IDLE control block Represents the number of customer service code blocks. The location information between two adjacent OAM overhead blocks may be different.
  • the OAM overhead is added again between the T block and the S block in the customer service Block, when there is a predetermined number of N4 coding blocks separated from the previous OAM overhead block, and the number of S blocks separated from the previous OAM overhead frame or the number of T blocks is less than N3, between the T block and the S block in the customer service data stream Add the OAM overhead frame header block again.
  • the reservation number N3 is the indication information carried in the previous OAM overhead block.
  • the number of OAM overhead blocks contained in the OAM overhead frame and the reserved number N3 do not need to be specified in advance, and can be adjusted as needed.
  • the reservation number N4 needs to be specified in advance and is a fixed value, which satisfies the minimum period required to transmit OAM information in the customer service data stream.
  • a device for sending a customer service data stream is also provided, and the device is used to implement the above-mentioned embodiments and optional implementation manners, and those that have been described will not be repeated.
  • the term "module” can implement a combination of software and/or hardware with predetermined functions.
  • the devices described in the following embodiments are preferably implemented by software, hardware or a combination of software and hardware is also possible and conceived.
  • Fig. 3 is a structural block diagram of a device for sending customer service data streams according to an embodiment of the present invention. As shown in Fig. 3, the device includes:
  • the obtaining module 30 is configured to obtain customer service data streams
  • the adding module 32 is configured to add operation, maintenance and management OAM overhead frames to the customer service data stream;
  • the sending module 34 is configured to send a client service data stream including an OAM overhead frame; the OAM overhead frame includes: at least one OAM overhead block, and the OAM overhead block includes: a data block or a control block.
  • the customer service data stream is obtained; the operation maintenance management OAM overhead frame is added to the customer service data stream; the customer service data stream added with the OAM overhead frame is sent; the OAM overhead frame contains: at least one OAM Overhead block, the OAM overhead block includes: a data block or a control block.
  • the adding module 32 is further configured to add an OAM overhead frame between the T block and S block of the customer service data stream for each customer service, and the OAM overhead frame is used for End-to-end monitoring of the customer service is performed, the S block is the start control block in the customer service data flow, and the T block is the end control block in the customer service data flow.
  • the adding module 32 is further configured to: if the frame header block of the OAM overhead frame is a data block, and the OAM overhead frame contains a frame header identification code, then by detecting the data block between the T block and the S block and determining the detected data Whether the frame header identification code is included in the block to lock the header block of the OAM overhead frame; if the header block of the OAM overhead frame is a control block, the header block of the OAM overhead frame is locked by detecting the control block type .
  • the adding module 32 is further configured to: when a predetermined number of N1 first coding blocks are separated from the previous OAM overhead block, and the number of second coding blocks separated from the previous OAM overhead block is less than N2,
  • the adding module 32 is further configured to: perform an IDLE control block or redundant sequel addition and deletion operations on the customer service data stream; a predetermined number N3 of first codes are separated between the OAM overhead block and the previous OAM overhead block Block, and the number of second coded blocks separated from the previous OAM overhead block is less than N4, the OAM overhead block is added between the T block and the S block; the predetermined number is separated from the previous OAM overhead block When the second coding block of N4 and the number of first coding blocks separated from the previous OAM overhead block is less than N3, the header block of the OAM overhead frame is added between the T block and the S block; N3 and N4 All are positive integers, and N4 meets the minimum period for transmitting the OAM overhead frame in the service data stream; the first coding block includes at least one of the following: S blocks, T blocks; the second coding block includes at least the following One: data block, control block.
  • IDLE control block or redundant sequel addition and deletion operations on the customer service data stream may be performed after the header block of the OAM overhead frame is added to the T block and the S block.
  • This embodiment of the present invention does not do this. limited.
  • the adding module 32 is further configured to perform an IDLE control block or redundant sequel addition and deletion operations on the customer service data stream;
  • the OAM overhead block of the OAM overhead frame carries indication information, and the indication information is used for When indicating whether other OAM overhead blocks are included after the OAM overhead block, and when other OAM overhead blocks are included after the OAM overhead block, the location information of the next OAM overhead block of the OAM overhead block; in the OAM overhead When a block is separated from the previous OAM overhead block by the number of first encoding blocks indicated by the location information, and the number of second encoding blocks separated from the previous OAM overhead block is less than N5, between the T block and the S block Add the OAM overhead block; in the second coding block separated from the previous OAM overhead block by a predetermined number N5, and the number of first coding blocks separated from the previous OAM overhead block is less than the location information indication
  • the number of OAM overhead frames is added between the T block and the S block, and the number indicated by the position information includes the number of the third
  • IDLE control block or redundant sequel addition and deletion operations on the customer service data stream may be performed after the header block of the OAM overhead frame is added to the T block and the S block.
  • This embodiment of the present invention does not do this. limited.
  • the adding module 32 is also configured to allocate bytes for other OAM overhead blocks, the bytes are used to check the other OAM overhead blocks, and the OAM overhead blocks are in the OAM overhead frame, except for the frame header block Other OAM overhead blocks.
  • Embodiment 1 to Embodiment 2 described above can be used in combination or used alone, which is not limited in the embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a scenario according to an alternative embodiment of the present invention.
  • a 50G Ethernet client service is to be transmitted between network device A and network device B, and there is a 50G Ethernet client service between network device A and network device B.
  • the service does not land on network device C.
  • An OAM overhead frame is composed of 8 66b OAM overhead blocks.
  • Step 1 At network device A, obtain a 50G Ethernet customer service data stream.
  • Step 2 Perform IDLE or redundant sequel deletion and insertion speed adjustment processing on the 50G Ethernet customer service flow.
  • Step 3 Insert the OAM overhead frame header block between the T block and S block of the 50G Ethernet client service flow after speed adjustment.
  • the OAM overhead frame header block is an ordered set of 66b, including the synchronization header 10.
  • the control block type is 0x4B, and the O code is 0xC.
  • the ordered set has 3 bytes that can be used to carry OAM information (it can be understood as the OAM overhead frame in the above embodiment).
  • Step 4 After 10 T blocks from the OAM overhead frame header block, insert the second OAM overhead block of the OAM overhead frame between the T block and S block of the 50G Ethernet client service flow, and so on until it is inserted The last OAM overhead block. If there are 512*1024 66b coding blocks separated from the previous OAM overhead block, and the number of T blocks separated from the previous OAM overhead block is less than 10, the OAM overhead frame header block is inserted at a predetermined position. In the OAM overhead frame, the remaining 7 OAM overhead blocks except for the OAM overhead frame header block are data blocks, including a synchronization header 01 and 8 bytes of available space. Its structure is shown in Figure 5. After adding the OAM overhead frame, a customer service data stream with end-to-end monitoring is formed, as shown in Figure 6.
  • Step 4 Perform speed adjustment again on the 50G Ethernet customer service with end-to-end monitoring, and then distribute the 10 5G time slots in the FlexE calendar for transmission through the physical layer PHY.
  • a 50G Ethernet client service needs to be transmitted between network device A and network device B.
  • the OAM overhead frame consists of one 66b OAM overhead block.
  • Step 1 At network device A, obtain 50G Ethernet customer service flow.
  • Step 2 Obtain a 50G Ethernet client service flow, and replace the identified IDEL block or redundant sequel with an OAM overhead block.
  • the OAM overhead frame header block is a 66b data block, which is composed of synchronization header 01 and frame Header identification code OxF6, this ordered set has 7 bytes that can be used to carry OAM information.
  • the schematic diagram is shown in Figure 7.
  • Step 3 After 10 T blocks from the previous OAM overhead block, replace the IDEL block or redundant sequel with the OAM overhead block between the next appropriate T block and S block in the 50G Ethernet customer service flow, namely The interval between two OAM overhead blocks may be greater than 10 T blocks. If there are 512*1024 66b coded blocks separated from the previous OAM overhead block, and the number of T blocks separated from the previous OAM overhead block is less than 10, the IDEL block or between the next appropriate T block and S block The redundant sequel is replaced with an OAM overhead frame header block.
  • Step 4 Perform speed adjustment on the 50G Ethernet customer service with end-to-end monitoring, and then distribute the 10 5G time slots in the FlexE calendar for transmission through the physical layer PHY.
  • Step 5 Network device B recovers the FlexE calendar from the physical layer PHY, and extracts 50G client services with end-to-end monitoring information from the corresponding 10 5G time slots.
  • Step 6 In the 50G customer service data stream with end-to-end monitoring information, after the T block and before the S block, the data block with the synchronization header of 01 is retrieved, and the frame header identification code OxF6 is the corresponding OAM overhead block. Extract information from the OAM overhead block to obtain end-to-end monitoring information of the business.
  • a 50G Ethernet client service needs to be transmitted between network device A and network device B.
  • the OAM overhead frame is composed of multiple 66b OAM overhead blocks, the specific number of which is determined according to actual requirements.
  • Step 1 At network device A, obtain 50G Ethernet customer service flow.
  • Step 2 Perform speed adjustment of IDLE deletion and insertion on the 50G Ethernet customer service flow.
  • Step 3 Insert the OAM overhead frame header block between the T block and the S block of the 50G Ethernet customer service flow to the 50G Ethernet customer service flow after speed adjustment.
  • the OAM overhead frame header block is a 66b block.
  • the sequence set consists of the synchronization header 10, the control block type 0x4B, and the O code 0xC.
  • the sequence set has 3 bytes that can be used to carry OAM information, of which D4 (the fourth byte of the OAM block) (the fourth byte of the OAM block) Bytes) the first two bits are used to indicate whether there is an OAM overhead block after the OAM overhead frame, 00 indicates no OAM overhead block, 11 indicates there is an OAM overhead block, and D4 (the fourth byte of the OAM block) is the last 6 bits It is used to indicate the position of the next OAM overhead block, which is the number of T blocks separated from the header block of the OAM overhead frame.
  • Step 4 In the header block of the OAM overhead frame, the first two bits of D4 (the 4th byte of the OAM block) are 11, and the last 6 bits of D4 (the 4th byte of the OAM block) are 001010.
  • the second OAM overhead block of the OAM overhead frame is inserted between the T block and the S block of the 50G Ethernet client service flow.
  • the OAM overhead block is a data block and its synchronization header is 01. There are 8 bytes, where the first two bits in D8 (the eighth byte of the OAM block) are used to indicate whether there is an OAM overhead block after the OAM overhead frame, 00 indicates no OAM overhead block, and 11 indicates there is an OAM overhead block.
  • the last 6 bits of D8 (the eighth byte of the OAM block) are used to indicate the position of the next OAM overhead block, which can be the number of T blocks separated from the previous OAM overhead block or the header block of the OAM overhead frame. In this embodiment Take the number of T blocks separated from the previous OAM overhead block as an example.
  • the two bits of D8 (the eighth byte of the OAM block) are 11, and the last six bits of D8 (the eighth byte of the OAM block) are 001110, which is 14 bits apart from the previous OAM overhead block
  • the OAM overhead block is a data block with a synchronization header of 01 and 8 bytes , Where the first two bits in D8 (the eighth byte of the OAM block) are used to indicate whether there is an OAM overhead block after the OAM overhead frame, 00 indicates no OAM overhead block, 11 indicates there is an OAM overhead block, and D8 (the OAM block first) 8 bytes)
  • the last 6 bits are used to indicate the position of the next OAM overhead block, which can be the number of T blocks separated from the previous OAM overhead block or the frame header block of the OAM overhead frame. Take the number of T blocks between overhead blocks as an example.
  • the two bits of D8 (the eighth byte of the OAM block) in the third OAM overhead block are 00, which means that there is no OAM overhead block following the OAM overhead block, and at this time the OAM overhead frame includes 3 OAM overhead blocks.
  • the schematic diagram is shown in Figure 8.
  • the OAM overhead frame header block is inserted between the next appropriate T block and S block.
  • Step 5 Perform speed adjustment again on the 50G Ethernet client service with end-to-end monitoring, and then distribute the 10 5G time slots in the FlexE calendar for transmission through the physical layer PHY.
  • the embodiment of the present invention also provides a storage medium, the storage medium includes a stored program, and the above-mentioned program executes any of the above-mentioned methods when the program is running.
  • the foregoing storage medium may be configured to store program code for executing the following steps:
  • S3 Send a customer service data stream including an OAM overhead frame; the OAM overhead frame includes: at least one OAM overhead block, and the OAM overhead block includes: a data block or a control block.
  • the above-mentioned storage medium may include, but is not limited to: U disk, ROM, RAM, mobile hard disk, magnetic disk, or optical disk and other media that can store program codes.
  • modules or steps of this application can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed in a network composed of multiple computing devices.
  • they can be implemented by program codes executable by a computing device, so that they can be stored in a storage device for execution by the computing device, and in some cases, they can be different from those here.
  • the steps shown or described are executed in sequence, or they are respectively fabricated into individual integrated circuit modules, or multiple modules or steps of them are fabricated into a single integrated circuit module for implementation. In this way, this application is not limited to any specific hardware and software combination.

Landscapes

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

Abstract

本文提供了一种客户业务数据流的发送方法及装置、存储介质，该方法包括：获取客户业务数据流；将操作维护管理OAM开销帧加入到所述客户业务数据流中；发送包含OAM开销帧的客户业务数据流；所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块。

Description

客户业务数据流的方法及装置、存储介质
本申请要求在2019年03月06日提交中国专利局、申请号为201910169628.7的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，例如涉及一种客户业务数据流的发送方法及装置、存储介质。
背景技术
灵活以太网(FlexE-Flexible Ethernet，FlexE)技术由国际标准化组织光互联网论坛(Optical Internetworking Forum，OIF)正式表决通过相关的技术文档。灵活以太网技术提供一种通用的机制来传送一系列不同媒体接入控制(Media Access Control，MAC)速率的业务，可以是单个MAC速率比较大的业务，也可以是多个MAC速率比较小的业务的集合，不在限定为单一MAC速率的业务。灵活以太网的通用结构如图1所示。灵活以太网一个特性就是：绑定多个速率相同的以太网的物理层(Physical Layer，PHY)来传输MAC速率比较大的业务，例如绑定3个100G的以太网PHY用来支持MAC速率为300G的业务，即业务是在多条以太网PHY中传输的。
灵活以太网与传统以太网结构上的区别在于灵活以太网在MAC层和物理编码子层(Physical Coding Sublayer，PCS)层多了一个垫层(FlexE Shim)，该垫层的功能是构建一个大小为20*n个66b块的时隙结构(Calendar)，n为绑定的以太网PHY个数，每个66b块代表一个5G的时隙。在复用侧，不同MAC速率的业务按照与5G的倍数关系，装进对应个数66b块中。每20个66b块构成一个子时隙结构(sub-Calendar)，大小为20*n的Calendar分布到n个sub-Calendar中。对于每个sub-Calendar，每20*1023个66b块添加一个66b块的开销，用来存储相关的映射关系，每个sub-Calendar在单个100G的以太网PHY中传送。在解复用侧，n个sub-Calendar组成一个大小为20*n的Calendar，根据开销中存储的映射关系从相应个数的66b块中提取出对应的客户业务。灵活以太网组(FlexE group)指的是由一个1到n条以太网PHY绑定起来形成的一个组，如图1所示。
5G承载是当前业界讨论比较多的一个话题，为了实现利用FlexE技术来进行5G承载，原先在OIF定义的点到点的技术需要扩展到端到端技术，相关的标准已经在国际电信联盟(International Telecommunications U nion，ITU)标准组织正式立项。目前FlexE的运行、管理和维护(Operation Administration and Maintenance，OAM)开销只能对点到点的路径进行监控，如果扩展到层网络，则目前的OAM开销机制无法满足对客户业务端到端的监控。
针对相关技术中，目前的OAM开销机制无法满足对客户业务端到端的监控等问题，尚未提出有效的技术方案。
发明内容
本发明实施例提供了一种客户业务数据流的发送方法及装置、存储介质，以至少解决相关技术中目前的OAM开销机制无法满足对业务端到端的监控等问题。
根据本发明的一个实施例，提供了一种客户业务数据流的发送方法，包括：获取客户业务数据流；将OAM开销帧加入到所述客户业务数据流中；发送包含OAM开销帧的客户业务数据流；所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块。
根据本发明的另一个实施例，还提供了一种客户业务数据流的发送装置，包括：获取模块，设置为获取客户业务数据流；添加模块，设置为将OAM开销帧加入到所述客户业务数据流中；发送模块，设置为发送包含OAM开销帧的客户业务数据流；所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块。
根据本发明的另一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，所述计算机程序被设置为运行时执行以上任一项所述的客户业务数据流的发送方法。
通过本申请，获取客户业务数据流；将OAM开销帧加入到所述客户业务数据流中；发送包含OAM开销帧的客户业务数据流；所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块，采用上述技术方案，解决了相关技术中目前的OAM开销机制无法满足对业务端到端的监控等问题，通过本申请提供的OAM开销机制，能够实现对客户业务端到端的监控。
附图说明
图1为相关技术中FlexE通用网络场景示意图；
图2为根据本发明实施例的客户业务数据流的发送方法的流程图；
图3是根据本发明实施例的客户业务数据流的发送装置的结构框图；
图4为根据本发明可选实施例的场景示意图；
图5为根据本发明可选实施例的OAM开销帧结构示意图；
图6为根据本发明可选实施例的端到端监控信息的客户业务数据流示意图；
图7为根据本发明可选实施例的又一OAM开销帧结构示意图；
图8为根据本发明可选实施例的OAM开销帧结构示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本发明实施例提供了一种客户业务数据流的发送方法，图2为根据本发明实施例的客户业务数据流的发送方法的流程图，如图2所示，该方法包括如下步骤。
步骤S202，获取客户业务数据流。
步骤S204，将OAM开销帧加入到所述客户业务数据流中。
步骤S206，发送包含OAM开销帧的客户业务数据流；所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块。
通过上述步骤，获取客户业务数据流；将操作维护管理OAM开销帧加入到所述客户业务数据流中；发送包含OAM开销帧的客户业务数据流；所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块，采用上述技术方案，解决了相关技术中目前的OAM开销机制无法满足对业务端到端的监控等问题，通过本申请提供的OAM开销机制，能够实现对客户业务端到端的监控。
步骤S204可能有多种实现方式，在一个可选的实施例中，将操作维护管理OAM开销帧加入到所述客户业务数据流中，可以通过以下方式实现：对于每一 个客户业务，将OAM开销帧添加到所述客户业务数据流的T块和S块之间，所述OAM开销帧用于对客户业务进行端到端的监控，所述S块为所述客户业务数据流中起始控制块，T块为所述客户业务数据流中终结控制块。
在本发明实施例中，若所述OAM开销帧的帧头块为数据块，OAM开销帧包含帧头识别码，则通过检测T块与S块之间的数据块以及判断检测出的数据块中是否包含帧头识别码进行OAM开销帧的帧头块锁定；若所述OAM开销帧的帧头块为控制块，则通过对控制块类型的检测，进行OAM开销帧的帧头块锁定。
对于上述将OAM开销帧添加到所述客户业务数据流的T块和S块之间的技术方案，本申请以下实施例主要提供了三种实现方式：
第一种实现方式
未对客户业务数据流进行空闲(IDLE)控制块或冗余的有续集的增删操作；
当与上一OAM开销块间隔预定数量N1的第一编码块，且与上一OAM开销块间隔的第二编码块数量小于N2时，
当所述T块与所述S块之间存在IDLE控制块或冗余的有续集时，将所述T块和S块之间的所述IDLE控制块或冗余的有续集替换为OAM开销块；
当所述T块与所述S块之间不存在IDLE控制块或冗余的有续集时，将N1个第一编码块之后第一个位于T块与S块之间的IDLE控制块或冗余的有续集替换为OAM开销块，即如果当前的T块和S块之间不存在IDLE控制块或冗余的有续集，那么OAM开销块无法插入到T块和S块之间，那么从下一个IDLE控制块或冗余的有续集(即N1个第一编码块之后第一个位于T块与S块之间的IDLE控制块或冗余的有续集)替换为OAM开销块；
当与上一OAM开销块间隔了预定数量N2的第二编码块，且与所述上一OAM开销块间隔的第一编码块的数量小于N1时，将所述T块和S块之间的IDLE控制块替换为OAM开销帧的帧头块；
N1和N2均为正整数，N2满足所述业务数据流中传递所述OAM开销帧的最小周期；
所述第一编码块包括以下至少之一：S块，T块；所述第二编码块包括以下至少之一：数据块，控制块。
第二种实现方式
预先对所述客户业务数据流进行IDLE控制块或冗余的有续集的增删操作；
对所述客户业务数据流进行IDLE控制块或冗余的有续集的增删操作；
在所述OAM开销块与上一OAM开销块间隔了预定数量N3的第一编码块，且与上一OAM开销块间隔的第二编码块数量小于N4时，在所述T块和S块之间加入所述OAM开销块；
在与所述上一OAM开销块间隔了预定数量N4的第二编码块，且与所述上一OAM开销块间隔的第一编码块的数量小于N3时，在所述T块和S块之间加入OAM开销帧的帧头块；
N3和N4均为正整数，N4满足所述业务数据流中传递所述OAM开销帧的最小周期；
所述第一编码块包括以下至少之一：S块，T块；所述第二编码块包括以下至少之一：数据块，控制块。
需要说明的是，上述对客户业务数据流进行IDLE控制块或冗余的有续集的增删操作可以是在T块和S块添加了OAM开销帧的帧头块之后，本发明实施例对此不作限定。
第三种实现方式
对所述客户业务数据流进行IDLE控制块或冗余的有续集的增删操作；
在所述OAM开销帧的OAM开销块中携带有指示信息，所述指示信息用于指示所述OAM开销块之后是否包含其他OAM开销块，以及在所述OAM开销块之后包含其他OAM开销块时，所述OAM开销块的下一OAM开销块的位置信息；
在所述OAM开销块与上一OAM开销块间隔了所述位置信息标示的数量的第一编码块，且与上一OAM开销块间隔的第二编码块数量小于N5时，在所述T块和S块之间加入所述OAM开销块；
在与所述上一OAM开销块间隔了预定数量N5的第二编码块，且与所述上一OAM开销块间隔的第一编码块的数量小于所述位置信息标示的数量时，在所述T块和S块之间加入OAM开销帧的帧头块，
所述位置信息标示的数量包括OAM开销块之间的第三编码块的数量；所述N5为正整数，所述N5满足所述业务数据流中传递所述OAM开销帧的最小周期；所述第三编码块包括以下至少之一：S块，T块或不包含IDLE控制块的其他控制块和数据块的总的数量(即第三编码块还可以是控制块和数据块总的数量，该控制块是不包括IDLE控制块的其他控制块)。
需要说明的是，上述对客户业务数据流进行IDLE控制块或冗余的有续集的增删操作可以是在T块和S块添加了OAM开销帧的帧头块之后，本发明实施例对此不作限定。
一实施例中，还可以为其他OAM开销块分配字节，所述字节用于校验所述其他OAM开销块，所述OAM开销块为所述OAM开销帧中，除帧头块之外的其他OAM开销块。
以上结合一示例对上述客户业务数据流的发送流程进行说明，但不用于限定本发明实施例的技术方案。
对于每一个客户业务，加入至少一个OAM开销块到客户业务数据流中，这些OAM开销块中承载对该客户业务进行端到端监控的开销，将插入OAM开销块的客户业务分发到FlexE时隙中，通过物理层PHY进行业务传输。
至少一个OAM开销块组成一个OAM开销帧，第一个OAM开销块为OAM开销帧帧头块，OAM开销帧的帧头块可为数据块，也可为控制块，该OAM开销帧其余的OAM开销块为数据块。OAM开销帧的帧头块每隔固定的数量的编码块或固定时间加入到客户业务数据流中，其满足在客户业务数据流中传递OAM信息所需要的最小周期。
若OAM开销帧帧头块为数据块，OAM开销帧包含帧头识别码，通过检测T块与S块之间的数据块以及判断该数据块中是否包含帧头识别码进行OAM开销帧的帧头块锁定；若为控制块，则通过对控制块类型的检测，进行OAM开销帧的帧头块锁定，进一步地，为了增加OAM开销块检测的可靠性，在除OAM开销帧的帧头块之外的其余OAM开销块，可分配一些字节进行校验，例如第一个字节为固定的格式，例如0xF6；第一个字节为上一个OAM开销块的比特间插校验(Bit Interleaved Parity，BIP)8或循环冗余校验(Cyclic Redundancy Check-8，CRC-8)计算结果。
S块为客户业务数据流中起始控制块，T块为客户业务数据流中终结控制块，其编码规范符合IEEE802.3标准。
第一种实现方式
在客户业务中的T块与S块之间加入OAM开销块，当与之前的OAM开销块间隔了预订数量N1的数据块之后，例如S块或T块或不包含IDLE控制块的客户业务编码块，在客户业务中的T块与S块之间再次加入OAM开销块，当与之前的OAM开销块间隔了预订数量N2的编码块，且与之前的OAM开销帧 间隔的S块或T块数量不足N1，在客户业务数据流中的T块与S块之间再次加入OAM开销帧帧头块。
OAM开销帧包含的OAM开销块数量以及预订数量N1和N2需要提前指定，且为一个固定的值，N2选取的条件满足在客户业务数据流中传递OAM信息所需要的最小周期，N1可根据实际需要进行设定；OAM开销块加入的方式包括将T块与S块之间的IDLE控制块或冗余的有续集替换为OAM开销块，在此处理方式下，预订数量N1为绝对数量，实际实现上存在一定的偏移量；或预先进行IDLE控制块或冗余的有续集的增删操作，然后在预订的位置插入OAM开销块。
第二种实现方式
预先对客户业务数据流进行IDLE控制块或冗余的有续集的增删操作，在预订位置的客户业务中的T块与S块之间加入OAM开销块，OAM开销帧帧头块携带指示信息用于指示该OAM开销帧头块之后是否包含其他OAM开销块以及下一个OAM开销块的位置信息，位置信息可通过相邻两个OAM开销块之间的S块或T块或不包含IDLE控制块的客户业务编码块数量表示。相邻两个OAM开销块之间的位置信息可不相同。当与之前的OAM开销块间隔了预订数量N3的S块或T块之后且与之前的OAM开销块间隔的编码块数量不足N4，在客户业务中的T块与S块之间再次加入OAM开销块，当与之前的OAM开销块间隔了预订数量N4的编码块，且与之前的OAM开销帧间隔的S块或T块数量不足N3，在客户业务数据流中的T块与S块之间再次加入OAM开销帧帧头块。预订数量N3为上一个OAM开销块中携带的指示信息。
OAM开销帧包含的OAM开销块数量以及预订数量N3无需提前指定，可以按需进行调整。预订数量N4需要提前指定，且为固定值，其满足在客户业务数据流中传递OAM信息所需要的最小周期。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是较佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如只读存储器(Read-Only Memory，ROM)/随机存取存储器(Random Access Memory，RAM)、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务 器，或者网络设备等)执行本发明各个实施例的方法。
实施例2
在本实施例中还提供了一种客户业务数据流的发送装置，该装置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的客户业务数据流的发送装置的结构框图，如图3所示，该装置包括：
获取模块30，设置为获取客户业务数据流；
添加模块32，设置为将操作维护管理OAM开销帧加入到所述客户业务数据流中；
发送模块34，设置为发送包含OAM开销帧的客户业务数据流；所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块。
通过本申请，获取客户业务数据流；将操作维护管理OAM开销帧加入到所述客户业务数据流中；发送添加了包含OAM开销帧的客户业务数据流；所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块，采用上述技术方案，解决了相关技术中目前的OAM开销机制无法满足对业务端到端的监控等问题，通过本申请提供的OAM开销机制，能够实现对客户业务端到端的监控。
在一个可选的实施例中，添加模块32，还设置为对于每一个客户业务，将OAM开销帧添加到所述客户业务数据流的T块和S块之间，所述OAM开销帧用于对客户业务进行端到端的监控，所述S块为所述客户业务数据流中起始控制块，T块为所述客户业务数据流中终结控制块。
添加模块32，还设置为：若所述OAM开销帧的帧头块为数据块，OAM开销帧包含帧头识别码，则通过检测T块与S块之间的数据块以及判断检测出的数据块中是否包含帧头识别码进行OAM开销帧的帧头块锁定；若所述OAM开销帧的帧头块为控制块，则通过对控制块类型的检测，进行OAM开销帧的帧头块锁定。
添加模块32，还设置为：当与上一OAM开销块间隔预定数量N1的第一编 码块，且与上一OAM开销块间隔的第二编码块数量小于N2时，
当所述T块与所述S块之间存在IDLE控制块或冗余的有续集时，将所述T块和S块之间的所述IDLE控制块或冗余的有续集替换为OAM开销块；当所述T块与所述S块之间不存在IDLE控制块或冗余的有续集时，将N1个第一编码块之后第一个位于T块与S块之间的IDLE控制块或冗余的有续集替换为OAM开销块，即如果当前的T块和S块之间不存在控制块或冗余的有续集，那么OAM开销块无法插入到T块和S块之间，那么从下一个IDLE控制块或冗余的有续集(即N1个第一编码块之后第一个位于T块与S块之间的IDLE控制块或冗余的有续集)替换为OAM开销块；当与上一OAM开销块间隔了预定数量N2的第二编码块，且与所述上一OAM开销块间隔的第一编码块的数量小于N1时，将所述T块和S块之间的IDLE控制块替换为OAM开销帧的帧头块；N1和N2均为正整数，N2满足所述业务数据流中传递所述OAM开销帧的最小周期；所述第一编码块包括以下至少之一：S块，T块；所述第二编码块包括以下至少之一：数据块，控制块。
添加模块32，还设置为：对所述客户业务数据流进行IDLE控制块或冗余的有续集的增删操作；在所述OAM开销块与上一OAM开销块间隔了预定数量N3的第一编码块，且与上一OAM开销块间隔的第二编码块数量小于N4时，在所述T块和S块之间加入所述OAM开销块；在与所述上一OAM开销块间隔了预定数量N4的第二编码块，且与所述上一OAM开销块间隔的第一编码块的数量小于N3时，在所述T块和S块之间加入OAM开销帧的帧头块；N3和N4均为正整数，N4满足所述业务数据流中传递所述OAM开销帧的最小周期；所述第一编码块包括以下至少之一：S块，T块；所述第二编码块包括以下至少之一：数据块，控制块。
需要说明的是，上述对客户业务数据流进行IDLE控制块或冗余的有续集的增删操作可以是在T块和S块添加了OAM开销帧的帧头块之后，本发明实施例对此不作限定。
添加模块32，还设置为：对所述客户业务数据流进行IDLE控制块或冗余的有续集的增删操作；在所述OAM开销帧的OAM开销块中携带有指示信息，所述指示信息用于指示所述OAM开销块之后是否包含其他OAM开销块，以及在所述OAM开销块之后包含其他OAM开销块时，所述OAM开销块的下一OAM开销块的位置信息；在所述OAM开销块与上一OAM开销块间隔了所述 位置信息标示的数量的第一编码块，且与上一OAM开销块间隔的第二编码块数量小于N5时，在所述T块和S块之间加入所述OAM开销块；在与所述上一OAM开销块间隔了预定数量N5的第二编码块，且与所述上一OAM开销块间隔的第一编码块的数量小于所述位置信息标示的数量时，在所述T块和S块之间加入OAM开销帧的帧头块，所述位置信息标示的数量包括OAM开销块之间的第三编码块的数量；所述N5为正整数，所述N5满足所述业务数据流中传递所述OAM开销帧的最小周期；所述第三编码块包括以下至少之一：S块，T块或不包含IDLE控制块的控制块和数据块总的数量(即第三编码块还可以是控制块和数据块总的数量，该控制块是不包括IDLE控制块的控制块)。
需要说明的是，上述对客户业务数据流进行IDLE控制块或冗余的有续集的增删操作可以是在T块和S块添加了OAM开销帧的帧头块之后，本发明实施例对此不作限定。
添加模块32，还设置为为其他OAM开销块分配字节，所述字节用于校验所述其他OAM开销块，所述OAM开销块为所述OAM开销帧中，除帧头块之外的其他OAM开销块。
需要说明的是，上述实施例1-实施例2的技术方案可以结合使用，也可以单独使用，本发明实施例对此不作限定。
以下结合可选实施例对上述技术方案进行说明，但不用于限定本发明实施例的技术方案。
可选实施例1
图4为根据本发明可选实施例的场景示意图，如图4所示，网络设备A与网络设备B之间要传送一个50G的以太网客户业务，网络设备A和网络设备B之间有一个网络设备C，业务在网络设备C处不落地，一个OAM开销帧由8个66b OAM开销块组成，基于上述场景，上述客户业务数据流的实现过程如下：
步骤1，在网络设备A，获取50G的以太网客户业务数据流。
步骤2，对50G的以太网客户业务流进行IDLE或冗余有续集删插的调速处理。
步骤3，插入OAM开销帧帧头块到调速后的50G以太网客户业务流的T块和S块之间，该OAM开销帧帧头块为一个66b的有序集，包括同步头10，控制块类型0x4B，以及O码0xC，该有序集有3个字节可以用来承载OAM信息(可以理解为上述实施例的OAM开销帧)。
步骤4，在与OAM开销帧帧头块相隔10个T块之后，在50G以太网客户业务流的T块和S块之间插入OAM开销帧的第二个OAM开销块，依此类推直到插入最后一个OAM开销块。若在与之前的OAM开销块间隔了512*1024个66b编码块，且与之前的OAM开销块间隔的T块数量不足10个，则在预定位置插入OAM开销帧帧头块。OAM开销帧中除OAM开销帧帧头块外的其余7个OAM开销块为数据块，包含同步头01以及8个字节的可用空间。其结构如图5所示。加入OAM开销帧后，形成带端到端监控的客户业务数据流，示意图如图6所示。
步骤4，将带有端到端监控的50G以太网客户业务，再次进行调速处理，然后分发FlexE calendar中10个5G时隙中，通过物理层PHY进行传输。
可选实施例2
如图2所示，网络设备A与网络设备B之间要传送一个50G的以太网客户业务，网络设备A和网络设备B之间有一个网络设备C，业务在网络设备C处不落地，一个OAM开销帧由1个66b OAM开销块组成。
步骤1，在网络设备A，获取50G的以太网客户业务流。
步骤2，获取50G的以太网客户业务流，将识别到的IDEL块或冗余的有续集替换为OAM开销块，该OAM开销帧帧头块为一个66b的数据块，由同步头01，帧头识别码OxF6，该有序集有7个字节可以用来承载OAM信息。其示意图如图7所示。
步骤3，在与上一个OAM开销块相隔10个T块之后，在50G以太网客户业务流下一个合适的T块和S块之间将IDEL块或冗余的有续集替换为OAM开销块，即两个OAM开销块间隔可能大于10个T块。若在与之前的OAM开销块间隔了512*1024个66b编码块，且与之前的OAM开销块间隔的T块数量不足10个，则在下一个合适的T块和S块之间将IDEL块或冗余的有续集替换为OAM开销帧帧头块。
步骤4，将带有端到端监控的50G以太网客户业务，进行调速处理，然后分发FlexE calendar中10个5G时隙中，通过物理层PHY进行传输。
步骤5，网络设备B从物理层PHY恢复出FlexE calendar，从对应的10个5G时隙中，提取出带端到端监控信息的50G客户业务。
步骤6，在带端到端监控信息的50G客户业务数据流中在T块之后S块之前，检索到同步头为01的数据块，且帧头识别码OxF6，则为对应的OAM开销 块，从OAM开销块中提取信息，获取业务端到端的监控信息。
可选实施例3
如图4所示，网络设备A与网络设备B之间要传送一个50G的以太网客户业务，网络设备A和网络设备B之间有一个网络设备C，业务在网络设备C处不落地，一个OAM开销帧由多个66b OAM开销块组成，其具体数量根据实际需求确定。
步骤1，在网络设备A，获取50G的以太网客户业务流。
步骤2，对50G的以太网客户业务流进行IDLE删插的调速处理。
步骤3，在50G的以太网客户业务流的T块和S块之间插入OAM开销帧帧头块到调速后的50G以太网客户业务流，该OAM开销帧帧头块为一个66b的有序集，由同步头10，控制块类型0x4B，以及O码0xC，该有序集有3个字节可以用来承载OAM信息，其中D4(OAM块第4个字节)(OAM块第4个字节)前两个比特用于指示OAM开销帧后面是否还有OAM开销块，00指示无OAM开销块，11指示有OAM开销块，D4(OAM块第4个字节)后6个比特用于指示下一个OAM开销块的位置，为与OAM开销帧的帧头块间隔的T块数量。
步骤4，OAM开销帧帧头块中D4(OAM块第4个字节)前两个比特为11，D4(OAM块第4个字节)后6个比特为001010，在与OAM开销帧帧头块相隔10个T块之后，在50G以太网客户业务流的T块和S块之间插入OAM开销帧的第二个OAM开销块，该OAM开销块为数据块，其同步头为01，有8个字节，其中D8(OAM块第8个字节)中前两个比特用于指示OAM开销帧后面是否还有OAM开销块，00指示无OAM开销块，11指示有OAM开销块，D8(OAM块第8个字节)后6个比特用于指示下一个OAM开销块的位置，可为与上一个OAM开销块或OAM开销帧的帧头块间隔的T块数量，本实施例以与上一个OAM开销块的间隔的T块数量为例。
第二个OAM开销块中D8(OAM块第8个字节)两个比特为11，D8(OAM块第8个字节)后6个比特为001110，在与上一个OAM开销块相隔14个T块之后，在50G以太网客户业务流的T块和S块之间插入OAM开销帧的第三个OAM开销块，该OAM开销块为数据块，其同步头为01，有8个字节，其中D8(OAM块第8个字节)中前两个比特用于指示OAM开销帧后面是否还有OAM开销块，00指示无OAM开销块，11指示有OAM开销块，D8(OAM块 第8个字节)后6个比特用于指示下一个OAM开销块的位置，可为与上一个OAM开销块或OAM开销帧的帧头块间隔的T块数量，本实施例以与上一个OAM开销块的间隔的T块数量为例。
第三个OAM开销块中D8(OAM块第8个字节)两个比特为00，则表示该OAM开销块后面无OAM开销块，此时该OAM开销帧包含3个OAM开销块。其示意图如图8所示。
与之前的OAM开销块间隔了512*1024个66b编码块，且与之前的OAM开销块间隔的T块数量不足上一个OAM开销块D8(OAM块第8个字节)后6个比特指示的个数，则在下一个合适的T块和S块之间插入OAM开销帧帧头块。
步骤5，将带有端到端监控的50G以太网客户业务，再次进行调速处理，然后分发FlexE calendar中10个5G时隙中，通过物理层PHY进行传输。
实施例3
本发明的实施例还提供了一种存储介质，该存储介质包括存储的程序，上述程序运行时执行上述任一项的方法。
在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，获取客户业务数据流；
S2，将操作维护管理OAM开销帧加入到所述客户业务数据流中；
S3，发送包含OAM开销帧的客户业务数据流；所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块。
在本实施例中，上述存储介质可以包括但不限于：U盘、ROM、RAM、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，一实施例中，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们 分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。

Claims (10)

  1. 一种客户业务数据流的发送方法，包括：
    获取客户业务数据流；
    将操作维护管理OAM开销帧加入到所述客户业务数据流中；
    发送包含所述OAM开销帧的客户业务数据流；
    其中，所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块，所述OAM开销帧用于对客户业务进行端到端的监控。
  2. 根据权利要求1所述的方法，其中，所述将OAM开销帧加入到所述客户业务数据流中，包括：
    对于每一个客户业务，将所述OAM开销帧添加到所述客户业务数据流的T块和S块之间，其中，所述S块为所述客户业务数据流中起始控制块，所述T块为所述客户业务数据流中终结控制块。
  3. 根据权利要求2所述的方法，还包括：
    若所述OAM开销帧的帧头块为数据块，所述OAM开销帧的帧头块包含帧头识别码，通过检测所述T块与所述S块之间的数据块以及判断检测出的数据块中是否包含帧头识别码进行所述OAM开销帧的帧头块锁定；
    若所述OAM开销帧的帧头块为控制块，则通过对控制块类型的检测，进行所述OAM开销帧的帧头块锁定。
  4. 根据权利要求2所述的方法，其中，所述将所述OAM开销帧添加到所述客户业务数据流的T块和S块之间包括：
    当与上一OAM开销块间隔预定数量N1的第一编码块，且与所述上一OAM开销块间隔的第二编码块数量小于N2时，
    当所述T块与所述S块之间存在空闲IDLE控制块或冗余的有续集时，将所述T块和所述S块之间的所述IDLE控制块或所述冗余的有续集替换为OAM开销块；
    当所述T块与所述S块之间不存在IDLE控制块或冗余的有续集时，将N1个第一编码块之后第一个位于所述T块与所述S块之间的IDLE控制块或冗余的有续集替换为OAM开销块；
    当与所述上一OAM开销块间隔了预定数量N2的第二编码块，且与所述上一OAM开销块间隔的第一编码块的数量小于N1时，将所述T块和所述S块之间的IDLE控制块替换为所述OAM开销帧的帧头块；
    其中，N1和N2均为正整数，N2满足所述业务数据流中传递所述OAM开销帧的最小周期；
    其中，所述第一编码块包括以下至少之一：S块，T块；所述第二编码块包括以下至少之一：数据块，控制块。
  5. 根据权利要求2所述的方法，其中，所述将所述OAM开销帧添加到所述客户业务数据流的T块和S块之间包括：
    对所述客户业务数据流进行IDLE控制块或冗余的有续集的增删操作；
    在所述OAM开销块与上一OAM开销块间隔了预定数量N3的第一编码块，且与所述上一OAM开销块间隔的第二编码块数量小于N4时，在所述T块和所述S块之间加入所述OAM开销块；
    在与所述上一OAM开销块间隔了预定数量N4的第二编码块，且与所述上一OAM开销块间隔的第一编码块的数量小于N3时，在所述T块和所述S块之间加入所述OAM开销帧的帧头块；
    其中，N3和N4均为正整数，N4满足所述业务数据流中传递所述OAM开销帧的最小周期；
    其中，所述第一编码块包括以下至少之一：S块，T块；所述第二编码块包括以下至少之一：数据块，控制块。
  6. 根据权利要求2所述的方法，其中，所述将所述OAM开销帧添加到所述客户业务数据流的T块和S块之间包括：
    对所述客户业务数据流进行IDLE控制块或冗余的有续集的增删操作；
    在所述OAM开销帧的OAM开销块中携带有指示信息，其中，所述指示信息用于指示所述OAM开销块之后是否包含其他OAM开销块，以及在所述OAM开销块之后包含其他OAM开销块时，所述OAM开销块的下一OAM开销块的位置信息；
    在所述OAM开销块与上一OAM开销块间隔了所述位置信息标示的数量的第一编码块，且与所述上一OAM开销块间隔的第二编码块数量小于N5时，在所述T块和所述S块之间加入所述OAM开销块；
    在与所述上一OAM开销块间隔了预定数量N5的第二编码块，且与所述上一OAM开销块间隔的第一编码块的数量小于所述位置信息标示的数量时，在所述T块和所述S块之间加入所述OAM开销帧的帧头块，其中，
    所述位置信息标示的数量包括OAM开销块之间的第三编码块的数量；所述N5为正整数，所述N5满足所述业务数据流中传递所述OAM开销帧的最小周期；其中，所述第三编码块包括以下至少之一：S块，T块，或不包含IDLE控制块的 其他控制块和数据块的总的数量。
  7. 根据权利要求1-6中任一项所述的方法，还包括：
    为其他OAM开销块分配字节，其中，所述字节用于校验所述其他OAM开销块，所述OAM开销块为所述OAM开销帧中，除帧头块之外的其他OAM开销块。
  8. 一种客户业务数据流的发送装置，包括：
    获取模块，设置为获取客户业务数据流；
    添加模块，设置为将操作维护管理OAM开销帧加入到所述客户业务数据流中；
    发送模块，设置为发送包含所述OAM开销帧的客户业务数据流；
    其中，所述OAM开销帧包含：至少一个OAM开销块，所述OAM开销块包括：数据块或控制块。
  9. 根据权利要求8所述的装置，其中，所述添加模块，还设置为对于每一个客户业务，将所述OAM开销帧添加到所述客户业务数据流的T块和S块之间，其中，所述S块为所述客户业务数据流中起始控制块，T块为所述客户业务数据流中终结控制块。
  10. 一种存储介质，存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至7任一项中所述的方法。
PCT/CN2020/077670 2019-03-06 2020-03-04 客户业务数据流的方法及装置、存储介质 WO2020177693A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910169628.7A CN111669771A (zh) 2019-03-06 2019-03-06 客户业务数据流的方法及装置、存储介质
CN201910169628.7 2019-03-06

Publications (1)

Publication Number Publication Date
WO2020177693A1 true WO2020177693A1 (zh) 2020-09-10

Family

ID=72337689

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/077670 WO2020177693A1 (zh) 2019-03-06 2020-03-04 客户业务数据流的方法及装置、存储介质

Country Status (2)

Country Link
CN (1) CN111669771A (zh)
WO (1) WO2020177693A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160119076A1 (en) * 2014-10-24 2016-04-28 Ciena Corporation Channelized oduflex systems and methods
CN106612220A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 灵活以太网的通道管理方法和装置
CN108123813A (zh) * 2016-11-28 2018-06-05 华为技术有限公司 操作、管理和维护oam数据的传输方法和装置
CN109257194A (zh) * 2017-07-12 2019-01-22 中兴通讯股份有限公司 处理承载通道的oam信息的方法、装置、设备及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160119076A1 (en) * 2014-10-24 2016-04-28 Ciena Corporation Channelized oduflex systems and methods
CN106612220A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 灵活以太网的通道管理方法和装置
CN108123813A (zh) * 2016-11-28 2018-06-05 华为技术有限公司 操作、管理和维护oam数据的传输方法和装置
CN109257194A (zh) * 2017-07-12 2019-01-22 中兴通讯股份有限公司 处理承载通道的oam信息的方法、装置、设备及系统

Also Published As

Publication number Publication date
CN111669771A (zh) 2020-09-15

Similar Documents

Publication Publication Date Title
CN110266612B (zh) 数据传输方法及装置、网络设备及存储介质
US8514897B2 (en) Method and device for mapping ethernet code blocks to OTN for transmission
CN112134652B (zh) Oam消息传输方法、传输设备及存储介质
CN109600188B (zh) 数据传输方法、传输设备和传输系统
US8238373B2 (en) Method and device for mapping ethernet code blocks to OTN for transmission
CN113784437B (zh) 一种FlexE承载小颗粒业务的实现方法和装置
CN106911426A (zh) 一种灵活以太网中传输数据的方法及设备
JPH06169325A (ja) データ及び音声両フレームを送信するフレーム中継システム及びその処理方法
CN109672560B (zh) 灵活以太网管理通道扩展方法及设备
CN112994843A (zh) 以太网帧定帧方法和装置
CN109802742B (zh) 一种传输数据的方法、设备及系统
CN109428837A (zh) 数据传输方法及装置
CN112994839A (zh) 灵活以太网开销复帧接收方法、装置、设备及介质
CN113765619A (zh) 64b/66b码流发送方法、64b/66b码流接收方法及设备
WO2020177693A1 (zh) 客户业务数据流的方法及装置、存储介质
CA2529599C (en) Method and apparatus for providing tandem connection, performance monitoring, and protection architectures over ethernet protocols
WO2023179198A1 (zh) 一种传输多优先级数据帧的方法
US20050002265A1 (en) Header compression
WO2021196774A1 (zh) 发送和处理信息的方法、以太网设备、计算机可读介质
US8982913B2 (en) Multiple E-carrier transport over DSL
CN116746093A (zh) 一种灵活以太网开销帧处理方法及装置
US20060153249A1 (en) Multiplexing device and data processing method thereof
US20210399992A1 (en) Service transmitting method and device, and service receiving method and device
WO2023143577A1 (zh) 一种光传送网中的数据帧的处理方法、装置和系统
WO2018108672A1 (en) Efficient transport mechanism in ethernet transport networks

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

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

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS (EPO FORM 1205A DATED 28.01.2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20765883

Country of ref document: EP

Kind code of ref document: A1