WO2020133897A1 - 运营维护管理信息处理方法和装置 - Google Patents

运营维护管理信息处理方法和装置 Download PDF

Info

Publication number
WO2020133897A1
WO2020133897A1 PCT/CN2019/088196 CN2019088196W WO2020133897A1 WO 2020133897 A1 WO2020133897 A1 WO 2020133897A1 CN 2019088196 W CN2019088196 W CN 2019088196W WO 2020133897 A1 WO2020133897 A1 WO 2020133897A1
Authority
WO
WIPO (PCT)
Prior art keywords
code block
data code
oam
function
oam data
Prior art date
Application number
PCT/CN2019/088196
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 US17/434,054 priority Critical patent/US11924079B2/en
Publication of WO2020133897A1 publication Critical patent/WO2020133897A1/zh

Links

Images

Classifications

    • 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/14—Monitoring arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0041—Arrangements at the transmitter end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0061—Error detection codes
    • 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • 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/0057—Operations, administration and maintenance [OAM]
    • H04J2203/006—Fault tolerance and recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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/0685—Clock or time synchronisation in a node; Intranode synchronisation
    • H04J3/0697—Synchronisation in a packet node
    • 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/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H04L43/106—Active monitoring, e.g. heartbeat, ping or trace-route using time related information in packets, e.g. by adding timestamps
    • 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/16—Threshold monitoring

Definitions

  • This application relates to flexible Ethernet (FlexE, Flex) technology, but is not limited to flexible Ethernet technology, and particularly relates to an operation and maintenance (OAM, Operation, Administration and Maintenance) information processing method and device.
  • OAM operation and maintenance
  • FlexE is proposed to solve the fixed rate of Ethernet interface and limit the flexibility of Ethernet routers and switches. It is an interface technology for the bearer network to achieve service isolation and network fragmentation. It has developed rapidly in the past two years and has been widely accepted by major standards organizations;
  • OAM is a very important function. OAM can guarantee the quality of service, simplify operations, and reduce operating costs.
  • the OAM data code block is processed by the FlexE layer, and then sent to the MAC processing, and then sent to the main switching chip (Switch Core) for OAM message processing.
  • the main switching chip Switch Core
  • the technical solution of the embodiment of the present application is implemented as follows:
  • the embodiment of the present application provides an OAM information processing method for operation, maintenance and management, the method including:
  • An embodiment of the present application also provides an operation and maintenance management information processing device, which includes: an acquisition module and a processing module; wherein,
  • the acquiring module is configured to acquire the data code block sent by the communication peer at the FlexE layer, and determine the first OAM data code block among the data code blocks according to a preset first determination rule;
  • the processing module is configured to determine the OAM function corresponding to the first OAM data code block according to a preset second determination rule; according to the function type corresponding to the first OAM data code block, a preset analysis rule is used to parse out Parsing data in the first OAM data code block; using the parsing data to perform the OAM function.
  • An embodiment of the present application further provides a storage medium on which an executable program is stored, and when the executable program is executed by a processor, the steps of the operation and maintenance management information processing method according to any one of the foregoing methods are implemented.
  • An embodiment of the present application also provides an operation and maintenance management information processing device, including a processor, a memory, and an executable program stored on the memory and capable of being run by the processor, when the processor runs the executable program The steps of the operation and maintenance management information processing method described in any of the above methods are performed.
  • the operation and maintenance management information processing method and device obtain the data code block sent by the communication peer at the FlexE layer, and determine the first OAM data code block among the data code blocks according to a preset first determination rule; Determine the OAM function corresponding to the first OAM data code block according to a preset second determination rule; according to the function type corresponding to the first OAM data code block, use a preset parsing rule to parse out the first OAM data code Parsing data in the block; using the parsing data to perform the OAM function.
  • the OAM data module is processed directly at the FlexE layer to improve the real-time performance of the OAM data block processing and improve the system response performance; the preset first determination rule and the second determination rule are used to identify the OAM data code block and its function type, adapt Different OAM data code block forms.
  • FIG. 1 is a schematic flowchart of an operation and maintenance management information processing method according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a network architecture of an operation and maintenance management information processing method according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of a data code block format according to an embodiment of this application.
  • FIG. 4 is a schematic diagram of an OAM data code block format according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of OAM data code block formats with different functions according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of an overall flow of operation, maintenance and management information processing according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an OAM data code parsing process according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a processing flow of a BAS function OAM data code block according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a processing flow of a CV function OAM data code block according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a processing flow of a 1DM function OAM data code block according to Embodiment 1 of the present application;
  • FIG. 11 is a schematic diagram of the processing flow of the OAM data code block of the 2MDM function according to Embodiment 2 of the present application;
  • FIG. 12 is a schematic diagram of a processing flow of OAM data code blocks with 2 DMR functions according to an embodiment of the present application
  • FIG. 13 is a schematic flowchart of sending OAM data code blocks according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of an operation and maintenance management information processing device according to an embodiment of the present application.
  • the data code block sent by the communication peer is obtained at the FlexE layer, and the first OAM data code block in the data code block is determined according to the preset first determination rule; the determination is performed according to the preset second determination rule
  • the operation and maintenance management information processing method provided by the embodiment of the present application, as shown in FIG. 1, the method includes:
  • Step 101 Obtain the data code block sent by the communication peer at the FlexE layer, and determine the first OAM data code block in the data code block according to the preset first determination rule;
  • FlexE is an intermediary layer created between MAC and PHY. FlexE provides a general mechanism to divide a physical Ethernet port into multiple Ethernet flexible hard pipes based on time slot scheduling. The data of each client (Client or FlexE Client) interface is scheduled and distributed to multiple different sub-channels in a time slot manner. And can achieve business isolation.
  • the OAM management adopted in the existing technology is implemented through protocols such as Ether OAM above the MAC layer, such as the main switching chip (Switch Core);
  • a processing engine may be provided to perform OAM management at the FlexE layer and process data code blocks of the FlexE layer encoded in 64B/66B; the FlexE OAM processing engine may be implemented by an ASIC or the like.
  • the data code blocks of the FlexE layer are usually transmitted to the FlexE layer by the communication peer through the PHY.
  • the preset first determination rule can be set according to the format of the OAM data code block, and the first OAM data code block in the data code block transmitted in the FlexE layer can be extracted into the processing engine through the information of the specific position of the OAM data code block deal with.
  • the format of the OAM data code block can be customized. As shown in FIG. 3, the format of the OAM data code block can be transmitted in the same 64B/66B format as the ordinary data code block, and the control code block is used. The 0 code in the code is distinguished. The 0 code is the 2nd to 9th bits.
  • 0x4B can be used to indicate that the data code block is the control code block; the C code is configurable by default, and 0xC can be used; when the C code in the 0x4B control code block 0xC, it is determined that the data code block is an OAM data code block; the OAM data code block can use 6 Data in the control block to carry OAM messages, and the specific field format of the OAM data code block can be shown in FIG. 4, where,
  • 0x4B is a 0 code, occupying 8 bits, and 0x48 indicates that the code block is a control code block;
  • Resv occupying 2bit, reserved field, default is 0;
  • Type occupying 6 bits, identifies different function types for different operations, maintenance and management;
  • Value (Value), occupying 32bit, the content of a specific type of OAM message
  • Sequence number (Seq, Sequence) number, occupying 4 bits, used to identify the sequence number of each data code block in the OAM data code block composed of multiple data code blocks;
  • Cyclic Redundancy Check Code 4 (CRC4), occupying 4 bits, for OAM code blocks, CRC4 bits are excluded, a total of 60 bits check; the algorithm polynomial of CRC4 can be x ⁇ 4+x+1.
  • the first OAM data code block includes more than one data code block
  • the first OAM data code block may be composed of one or more data code blocks, and the OAM data code block composition rule may be preset to set the data content in each data code block.
  • the OAM data code block may implement different management functions, and the function types of the OAM data code block may include: basic (BAS, BASIC) functions, automatic protection switching (APS, Automatic Protection) switching functions, connectivity CV (Connectivity Verification) function, one-way delay detection (1DM, One-way Delay Measurement) function, two-way delay detection information (2DMM, Two-Way Delay Measurement) message function, two-way delay detection response (2DMR , Two-Way Delay Measurement (Reply) function or customer signal (CS, Client signal) function, etc.;
  • the BAS function may include: connectivity check function, bit interleaved parity check (BIP, Bit Interleaved Parity) function, remote fault indication (RDI, Remote Defect Indication) function, remote error indication (REI, Remote Error Error Indication) ) Function, bit error rate (BER, Bit Error) calculation function, customer link near-end failure (CS_LF) function and/or customer link far-end failure (CS_RF) function.
  • BIP bit interleaved parity check
  • RDI Remote Defect Indication
  • REI Remote Error Error Indication
  • BER Bit Error
  • CS_LF customer link near-end failure
  • CS_RF customer link far-end failure
  • OAM data code block format can be as shown in Figure 5.
  • OAM data code blocks of different functions can be in the form of a single code block, which is composed of one data code block, or in the form of multiple code blocks, which is composed of multiple data code blocks.
  • the functions, identification information, and priority of different OAM data code blocks The level can be shown in Table 1;
  • out-of-band information corresponding to the first OAM data code block may be obtained
  • the out-of-band information may be independently transmitted using a channel different from the ordinary data code block, or it may be information that counts the data code block.
  • the out-of-band information of the same transmission time slot as the first OAM data code block may be determined as the out-of-band information corresponding to the first OAM data code block; the out-of-band information may include: a client ID (Client ID), a client Link signal quality information, BIP check information, time stamp when receiving data code blocks, etc.: Client ID can be determined according to time slot, BIP check information can be obtained by local technology, time stamp when receiving data code blocks is FlexE layer Reception timestamp.
  • the out-of-band information can be used for processing OAM data code blocks.
  • Step 102 Determine the OAM function corresponding to the first OAM data code block according to a preset second determination rule; according to the function type corresponding to the first OAM data code block, use a preset parsing rule to parse out the first Parsing data in the OAM data code block; using the parsing data to perform the OAM function.
  • the second determination rule here may be determined according to the field format of the first OAM data code block. Taking the first OAM data code block in FIG. 5 as an example, the OAM function type corresponding to the first OAM data code block may be determined according to the type field;
  • the preset parsing rule can be determined according to the code block format corresponding to each OAM function type of the first OAM data code block; taking the BIP function of the BAS code block as an example, as can be seen from the code block format of the OAMOAM data code block in FIG. 5, Parse the 50th to 57th bits into a BIP check code; you can also analyze the data in multiple OAM data code blocks that make up CV and other functions.
  • the first OAM data code block is parsed according to the OAM function type, and the required analysis data can be extracted according to the field format of the first OAM data code block of each OAM function type, and the OAM function is executed.
  • the parsing data and the out-of-band information may be used to perform the OAM function
  • the first OAM data code block of some function types usually needs to be combined with out-of-band information to perform the corresponding OAM function.
  • the acquired out-of-band information can be combined for processing.
  • the BIP function in BAS needs to compare the BIP check code in the first OAM data code block with the BIP check code in out-of-band information;
  • the overall flow of the FlexE OAM processing engine in receiving data code blocks for processing, as shown in FIG. 6 includes:
  • Step 601 Receive data code blocks and out-of-band information, and extract OAM data code blocks.
  • the out-of-band information may include Client ID, customer link signal quality information, BIP check information, and time stamp when the code block is received;
  • step 602 may be performed for OAM data code blocks, and out-of-band information may be transmitted to the processing module of the FlexE OAM processing engine through the bus in the OAM processing engine, and processed in combination with the parsed OAM data code blocks;
  • Step 602 Parse out the data of the OAM data code block according to the OAM data code block type
  • Step 603 Process the data and out-of-band information of the parsed OAM data code block according to the OAM function type
  • Step 604 If the OAM function type includes sending information to the communication peer, reply to the corresponding information.
  • the method before using the first OAM data code block, or using the first OAM data code block and the out-of-band information, before performing the OAM function, the method further includes: An OAM data code block is checked for legality; the legality check includes calculation and checking of CRC values;
  • the FlexE OAM processing engine parsing process may be as shown in FIG. 7 and includes:
  • Step 701 The module first checks the validity of the received OAM code block, including the calculation and check of the CRC value;
  • Steps 702 to 706 Perform data analysis according to different function types of OAM data code blocks, and put the analyzed content into the internal BUS of the processing engine for specific processing modules of each code block.
  • the parsing process may be a process of extracting data required for each function type from the OAM data code block from a single code block OAM data code block or a multi code block OAM data code block.
  • the order of steps 702 to 706 may be in no particular order.
  • the functions included in them can be processed in sequence, and the processing flow can be as shown in FIG. 8; here, steps 801 to 807 can be executed in the order shown in FIG. 8 or can be passed Customized order execution;
  • Step 801 RDI information processing, used to determine the remote fault condition according to the RDI information in the OAM data code block;
  • Step 802 CS information processing, according to the CS_LF and/or CS_RF indication information in the OAM data code block, determine the link failure status;
  • Step 803 Periodic check, according to the data in the OAM data code block, determine the periodic status
  • Step 804 BIP information processing, used to compare the BIP check code in the BAS with the BIP check code in the out-of-band information to determine whether there is a transmission problem;
  • Step 805 BER bit error rate calculation processing, used to calculate the bit error rate of the network transmission
  • Step 806 REI processing, used to indicate the error code of the remote network connection
  • Step 807 APS can be triggered according to the link failure condition.
  • the link failure condition can include the bit error rate of step 805, etc.
  • the bit error rate can be adjusted to the user set signal error rate (SF) and signal degradation (SD) error rate
  • SF user set signal error rate
  • SD signal degradation
  • the CV function usually uses the received source access point identifier (SAPI, Source Access Point Identifier) and destination access point identifier (DAPI, Destination Access Point Identifier) to compare with the preset comparison value, and generates a warning when there is a mismatch; here,
  • SAPI received source access point identifier
  • DAPI Destination Access Point Identifier
  • the processing flow of the parsed CV function OAM data code block may be as shown in FIG. 9 and includes:
  • Step 901 The CV code block processing module includes sequence number (SequenceNumber) check;
  • the CV function OAM data code block can be composed of multiple data code blocks, as shown in FIG. 5 can be composed of 8 data code blocks, and the integrity of the CV function OAM data code block can be checked by a preset sequence number;
  • Step 902 Integrate the multi-data code blocks of the CV function OAM data code blocks SAPI/DAPI and store the multi-code blocks of SAPI/DAPI;
  • the data in multiple data code blocks can be read in sequence, integrated into complete SAPI/DAPI data, and stored;
  • Step 903 and when the multi-module reception is complete, the SAPI/DAPI comparison process corresponding to the locally configured Client, according to the comparison processing result, determine whether a mismatch error occurs and report to the system.
  • the CS function OAM data code block is used to compare the client signal with the pre-stored signal; the processing flow of the parsed CS function OAM data code block may only include the CS type check. From the received code block, the CS type and Compare the locally configured CS types, determine whether there is a mismatch error, and report to the system.
  • the CS type may include: unloaded, Ethernet, Synchronous Digital Hierarchy (SDH, Synchronous Digital Hierarchy), etc.
  • the 1DM function OAM data code block is used to detect the delay status sent to the receiver.
  • the processing flow of the parsed CV function OAM data code block can be as shown in FIG. 10, including:
  • Step 1001 In the processing module, the DM storage entry is indexed according to the Client ID of the out-of-band information, the serial number is checked, the multi-code block integration processing logic is performed, and the multi-code block time stamp storage of the 1DM, and when the multi-code block is received When it is complete, for the 1DM function OAM data code block shown in FIG. 5, two consecutive legal 1DM code blocks are correctly received to indicate complete reception;
  • Step 1002 Use the timestamp in the received 1DM function OAM data code block as the timestamp Ttx when sending to the far end, and the timestamp in the out-of-band information is the first 1DM OAM data code block received
  • the 2DMM function OAM data code block is used to detect the delay status of bidirectional transmission and reception. Usually, the 2DMR data code block is sent after receiving the 2DMM function OAM data code block. As shown in FIG. 5, the 2DMM function OAM data code block can be composed of 6 data The code block is the longest, and the processing flow of the parsed OAM data code block of the CV function can be shown in FIG. 11:
  • Step 1101; in the 2DMM processing module, the 2DMM function OAM data code block reception and integration processing, and the method of obtaining the time stamp are similar to the 1DM function OAM data code block processing method;
  • Step 1102 when the OAM data code block of the multi-code block 2DMM function is completely received, a process of replying to the 2DMR is required, and the 2DMR includes a total of 6 consecutive OAM data code blocks.
  • the timestamp content in the two data code blocks with Seq value of 0 and Seq value of 1 is copied from 2DMM; the timestamp in the out-of-band information is the timestamp of receiving 2DMM, and the timestamp of 2DMM will be received
  • the 2DMR function OAM data code block is used to detect the delay status of the two-way transmission and reception. Usually, the 2DMR data code block sent by the received communication peer is measured for delay.
  • the processing flow of the parsed 2DMR function OAM data code block can be As shown in Figure 12:
  • Step 1201 In the 2DMR processing module, the data code block is first subjected to multi-code block OAM data code block reception, integration processing, storage and other processing;
  • Step 1202 When the multiple code blocks are completely received, the time delay information in the 2DMR needs to be calculated.
  • the corresponding 2DMM transmission time stamp (Tx_f_TS can be taken from the 6 code blocks of the 2DMR ), 2DMM receiving timestamp (Rx_b_TS), 2DMR sending timestamp (Tx_b_TS), and expressing the timestamp in the out-of-band information as the timestamp of receiving the 2DMR OAM data code block, that is, the 2DMR receiving timestamp).
  • the two-way delay calculation expression can be: (2DMR receive timestamp-2DMM send timestamp)-(2DMR send timestamp-2DMM receive timestamp), which is used by upper-layer system.
  • the second OAM data code block may be sent to the illustrated communication peer at the FlexE layer
  • the second OAM data code block may be a data code block that transmits in the opposite direction to the first OAM data code block, and is sent directly from the FlexE layer through the OAM processing engine, which can improve the real-time performance of OAM data code block processing and enhance the system Response performance;
  • the second OAM data code block may be a reply data code block that receives the OAM data code block sent by the communication peer, or an OAM data code block actively sent to the communication peer.
  • 16K data code block time pulses may be used as the transmission time unit, and the second OAM data code block is sent to the communication peer by a preset number of the transmission time units;
  • 16K data code block time pulses can be used as a time unit to perform time counting to indicate the transmission time of each OAM data code block.
  • Each function code block has a corresponding transmission count configuration.
  • the transmission count configuration value is based on the time of 16K code blocks. Therefore, different time intervals can be configured for the transmission count configuration value.
  • all client related entries are read at a time interval of 16K code blocks.
  • the send count configured in the entry is decremented by 1. When it is reduced to 0, it means that the class needs to be sent at this moment.
  • the processing of the sending module is performed, and the occurrence count is reset to the configured code block transmission period, which is used for time counting of the next OAM data code block.
  • the second OAM data code block when the second OAM data code block is a BAS function, a BIP check code corresponding to the second OAM data code block is set in the FlexE layer to the second OAM data code block; the first When the second OAM data code block is the 1DM function or the 2DMM function, the sending time of the second OAM data code block at the FlexE layer is set as a sending timestamp in the second OAM data block;
  • the control flag that needs to add BIP information needs to be added to the out-of-band information that is sent to the FlexE layer at the same time.
  • the FlexE layer edits the calculated BIP check code into the corresponding position; for DM-related code blocks , You need to place a control flag with a timestamp added in the out-of-band information, and the FlexE layer will edit the obtained timestamp into the corresponding position when sending the code block.
  • the operation and maintenance management information processing device includes: an acquisition module 141 and a processing module 142; wherein,
  • the obtaining module 141 is configured to obtain the data code block sent by the communication peer at the FlexE layer, and determine the first OAM data code block among the data code blocks according to a preset first determination rule;
  • FlexE is an intermediary layer created between MAC and PHY. FlexE provides a general mechanism to divide a physical Ethernet port into multiple Ethernet flexible hard pipes based on time slot scheduling. The data of each client (Client or FlexE Client) interface is scheduled and distributed to multiple different sub-channels in a time slot manner. And can achieve business isolation.
  • the OAM management adopted in the prior art is implemented through protocols such as Ether OAM at the MAC layer such as Switch Core.
  • a processing engine may be provided to perform OAM management at the FlexE layer and process data code blocks of the FlexE layer encoded in 64B/66B; the FlexE OAM processing engine may be implemented by an ASIC or the like.
  • the data code blocks of the FlexE layer are usually transmitted to the FlexE layer by the communication peer through the PHY.
  • the preset first determination rule can be set according to the format of the OAM data code block, and the first OAM data code block in the data code block transmitted in the FlexE layer can be extracted into the processing engine through the information of the specific position of the OAM data code block deal with.
  • the format of the OAM data code block can be customized. As shown in FIG. 3, the format of the OAM data code block can be transmitted in the same 64B/66B format as the ordinary data code block, and the control code block is used. The 0 code in the code is distinguished. The 0 code is the 2nd to 9th bits.
  • 0x4B can be used to indicate that the data code block is the control code block; the C code is configurable by default, and 0xC can be used; when the C code in the 0x4B control code block If it is 0xC, it is determined that the data code block is an OAM data code block; the OAM data code block can use 6 Data in the control block to carry OAM messages, and the specific field format of the OAM data code block can be as shown in FIG. 4, where,
  • 0x4B is a 0 code, occupying 8 bits, and 0x48 indicates that the code block is a control code block;
  • Resv occupying 2bit, reserved field, default is 0;
  • Type occupying 6 bits, identifies different function types for different operations, maintenance and management;
  • Seq occupying 4 bits, is used to identify the sequence number of each data code block in the OAM data code block composed of multiple data code blocks;
  • CRC4 occupies 4 bits. For OAM code blocks, CRC4 bits are excluded, a total of 60 bits are checked; the algorithm polynomial of CRC4 can be x ⁇ 4+x+1.
  • the first OAM data code block includes more than one data code block
  • the first OAM data code block may be composed of one or more data code blocks, and the OAM data code block composition rule may be preset to set the data content in each data code block.
  • the OAM data code block may implement different management functions, and the function types of the OAM data code block may include: BAS function, APS function, CV function, 1DM function, 2DMM function, 2DMR function or CS function, etc. ;
  • the BAS function may include: connectivity check function, BIP function, RDI function, REI function, BER calculation function, CS_LF function and/or CS_RF function.
  • OAM data code block format can be as shown in Figure 5.
  • OAM data code blocks of different functions can be in the form of a single code block, which is composed of one data code block, or in the form of multiple code blocks, which is composed of multiple data code blocks.
  • the functions, identification information, and priority of different OAM data code blocks The level can be shown in Table 1;
  • out-of-band information corresponding to the first OAM data code block may be obtained
  • the out-of-band information may be independently transmitted using a channel different from the ordinary data code block, or may be information for statistically calculating the data code block.
  • the out-of-band information of the same transmission time slot as the first OAM data code block may be determined as the out-of-band information corresponding to the first OAM data code block; the out-of-band information may include: Client ID, customer link signal quality Information, BIP check information, time stamp when receiving data code blocks, etc.: Client ID can be determined according to the time slot, BIP check information can be obtained by local technology, the time stamp when receiving data code blocks is the receiving time stamp of FlexE layer .
  • the out-of-band information can be used for processing OAM data code blocks.
  • the processing module 142 is configured to determine the OAM function corresponding to the first OAM data code block according to a preset second determination rule; according to the function type corresponding to the first OAM data code block, a preset analysis rule is used to analyze Output the parsed data in the first OAM data code block; use the parsed data to perform the OAM function.
  • the second determination rule here may be determined according to the field format of the first OAM data code block. Taking the first OAM data code block in FIG. 5 as an example, the OAM function type corresponding to the first OAM data code block may be determined according to the type field;
  • the preset parsing rule can be determined according to the code block format corresponding to each OAM function type of the first OAM data code block; taking the BIP function of the BAS code block as an example, as can be seen from the code block format of the OAMOAM data code block in FIG. 5, Parse the 50th to 57th bits into a BIP check code; you can also analyze the data in multiple OAM data code blocks that make up CV and other functions.
  • the first OAM data code block is parsed according to the OAM function type, and the required analysis data can be extracted according to the field format of the first OAM data code block of each OAM function type, and the OAM function is executed.
  • the parsing data and the out-of-band information may be used to perform the OAM function
  • the first OAM data code block of some function types usually needs to be combined with out-of-band information to perform the corresponding OAM function.
  • the acquired out-of-band information can be combined for processing.
  • the BIP function in the BAS needs to compare the BIP check code in the first OAM data code block with the BIP check code in the out-of-band information.
  • the overall flow of the FlexE OAM processing engine in receiving data code blocks for processing, as shown in FIG. 6 includes:
  • Step 601 Receive data code blocks and out-of-band information, and extract OAM data code blocks.
  • the out-of-band information may include Client ID, customer link signal quality information, BIP check information, and time stamp when the code block is received;
  • step 602 may be performed for OAM data code blocks, and out-of-band information may be transmitted to the processing module of the FlexE OAM processing engine through the bus in the OAM processing engine, and processed in combination with the parsed OAM data code blocks;
  • Step 602 Parse out the data of the OAM data code block according to the OAM data code block type
  • Step 603 Process the data and out-of-band information of the parsed OAM data code block according to the OAM function type
  • Step 604 If the OAM function type includes sending information to the communication peer, reply to the corresponding information.
  • the method before using the first OAM data code block, or using the first OAM data code block and the out-of-band information, before performing the OAM function, the method further includes: An OAM data code block is checked for legality; the legality check includes calculation and checking of CRC values;
  • the FlexE OAM processing engine parsing process may be as shown in FIG. 7 and includes:
  • Step 701 The module first checks the validity of the received OAM code block, including the calculation and check of the CRC value;
  • Steps 702 to 706 Perform data analysis according to different function types of OAM data code blocks, and put the analyzed content into the internal BUS of the processing engine for specific processing modules of each code block.
  • the parsing process may be a process of extracting data required for each function type from the OAM data code block from a single code block OAM data code block or a multi code block OAM data code block.
  • the order of steps 702 to 706 may be in no particular order.
  • the functions included in them can be processed in sequence, and the processing flow can be as shown in FIG. 8; here, steps 801 to 807 can be executed in the order shown in FIG. 8 or can be passed Customized order execution;
  • Step 801 RDI information processing, used to determine the remote fault condition according to the RDI information in the OAM data code block;
  • Step 802 CS information processing, according to the CS_LF and/or CS_RF indication information in the OAM data code block, determine the link failure status;
  • Step 803 Periodic check, according to the data in the OAM data code block, determine the periodic status
  • Step 804 BIP information processing, used to compare the BIP check code in the BAS with the BIP check code in the out-of-band information to determine whether there is a transmission problem;
  • Step 805 BER bit error rate calculation processing, used to calculate the bit error rate of the network transmission
  • Step 806 REI processing, used to indicate the error code of the remote network connection
  • Step 807 APS can be triggered according to the link failure condition.
  • the link failure condition can include the bit error rate of step 805, etc.
  • the bit error rate can be adjusted to the user set signal error rate (SF) and signal degradation (SD) error rate
  • SF user set signal error rate
  • SD signal degradation
  • the CV function usually uses SAPI and DAPI to compare with the preset comparison value, and generates a warning when there is no match; here, the processing flow of the parsed CV function OAM data code block can be shown in Figure 9, including:
  • Step 901 The CV code block processing module includes Sequence and Number check;
  • the CV function OAM data code block can be composed of multiple data code blocks, as shown in FIG. 5 can be composed of 8 data code blocks, and the integrity of the CV function OAM data code block can be checked by a preset sequence number;
  • Step 902 Integrate the multi-data code blocks of the CV function OAM data code blocks SAPI/DAPI and store the multi-code blocks of SAPI/DAPI;
  • the data in multiple data code blocks can be read in sequence, integrated into complete SAPI/DAPI data, and stored;
  • Step 903 and when the multi-module reception is complete, the SAPI/DAPI comparison process corresponding to the locally configured Client, according to the comparison processing result, determine whether a mismatch error occurs and report to the system.
  • the CS function OAM data code block is used to compare the client signal with the pre-stored signal; the processing flow of the parsed CS function OAM data code block may only include the CS type check. From the received code block, the CS type and Compare the locally configured CS types, determine whether there is a mismatch error, and report to the system.
  • the CS type may include: unloaded, Ethernet, SDH, etc.
  • the 1DM function OAM data code block is used to detect the delay status sent to the receiver.
  • the processing flow of the parsed CV function OAM data code block can be as shown in FIG. 10, including:
  • Step 1001 In the processing module, the DM storage entry is indexed according to the Client ID of the out-of-band information, the serial number is checked, the multi-code block integration processing logic is performed, and the multi-code block time stamp storage of the 1DM, and when the multi-code block is received When it is complete, for the 1DM function OAM data code block shown in FIG. 5, two consecutive legal 1DM code blocks are correctly received to indicate complete reception;
  • Step 1002 Use the timestamp in the received 1DM function OAM data code block as the timestamp Ttx when sending to the far end, and the timestamp in the out-of-band information is the first 1DM OAM data code block received
  • the 2DMM function OAM data code block is used to detect the delay status of bidirectional transmission and reception. Usually, the 2DMR data code block is sent after receiving the 2DMM function OAM data code block. As shown in FIG. 5, the 2DMM function OAM data code block can be composed of 6 data The code block is the longest, and the processing flow of the parsed OAM data code block of the CV function can be shown in FIG. 11:
  • Step 1101; in the 2DMM processing module, the 2DMM function OAM data code block reception and integration processing, and the method of obtaining the time stamp are similar to the 1DM function OAM data code block processing method;
  • Step 1102 when the OAM data code block of the multi-code block 2DMM function is completely received, a process of replying to the 2DMR is required, and the 2DMR includes a total of 6 consecutive OAM data code blocks.
  • the timestamp content in the two data code blocks with Seq value of 0 and Seq value of 1 is copied from 2DMM; the timestamp in the out-of-band information is the timestamp of receiving 2DMM, and the timestamp of 2DMM will be received
  • the 2DMR function OAM data code block is used to detect the delay status of the two-way transmission and reception. Usually, the 2DMR data code block sent by the received communication peer is measured for delay.
  • the processing flow of the parsed 2DMR function OAM data code block can be As shown in Figure 12:
  • Step 1201 In the 2DMR processing module, the data code block is first subjected to multi-code block OAM data code block reception, integration processing, storage and other processing;
  • Step 1202 When the multiple code blocks are completely received, the time delay information in the 2DMR needs to be calculated.
  • the corresponding 2DMM transmission time stamp (Tx_f_TS can be taken from the 6 code blocks of the 2DMR ), 2DMM receiving timestamp (Rx_b_TS), 2DMR sending timestamp (Tx_b_TS), and expressing the timestamp in the out-of-band information as the timestamp of receiving the 2DMR OAM data code block, that is, the 2DMR receiving timestamp).
  • the two-way delay calculation expression can be: (2DMR receive timestamp-2DMM send timestamp)-(2DMR send timestamp-2DMM receive timestamp), which is used by upper-layer system.
  • the apparatus may further include a sending module 143, configured to send a second OAM data code block to the indicated communication peer at the FlexE layer;
  • the second OAM data code block may be a data code block that transmits in the opposite direction to the first OAM data code block, and is sent directly from the FlexE layer through the OAM processing engine, which can improve the real-time performance of OAM data code block processing and enhance the system Response performance;
  • the second OAM data code block may be a reply data code block that receives the OAM data code block sent by the communication peer, or an OAM data code block actively sent to the communication peer.
  • 16K data code block time pulses may be used as the transmission time unit, and the second OAM data code block is sent to the communication peer by a preset number of the transmission time units;
  • 16K data code block time pulses can be used as one time unit, and the line time count is used to indicate the transmission time of each OAM data code block.
  • Each function code block has a corresponding transmission count configuration.
  • the transmission count configuration value is based on the time of 16K code blocks. Therefore, different time intervals can be configured for the transmission count configuration value.
  • all client related entries are read at a time interval of 16K code blocks.
  • the send count configured in the entry is decremented by 1. When it is reduced to 0, it means that the class needs to be sent at this moment.
  • the processing of the sending module is performed, and the occurrence count is reset to the configured code block transmission period, which is used for time counting of the next OAM data code block.
  • the second OAM data code block when the second OAM data code block is a BAS function, a BIP check code corresponding to the second OAM data code block is set in the FlexE layer to the second OAM data code block; the first When the second OAM data code block is the 1DM function or the 2DMM function, the sending time of the second OAM data code block at the FlexE layer is set as a sending timestamp in the second OAM data block;
  • the control flag that needs to add BIP information needs to be added to the out-of-band information that is sent to the FlexE layer at the same time.
  • the FlexE layer edits the calculated BIP check code into the corresponding position; for DM-related code blocks , You need to place a control flag with a timestamp added in the out-of-band information, and the FlexE layer will edit the obtained timestamp into the corresponding position when sending the code block.
  • the acquisition module 141, the processing module 142, and the sending module 143 can all be operated by a CPU, a microprocessor (MCU), a digital signal processor (DSP), or field programmable in an operation and maintenance management information processing system Gate array (FPGA) and other implementations.
  • MCU microprocessor
  • DSP digital signal processor
  • FPGA field programmable in an operation and maintenance management information processing system Gate array
  • the storage medium provided by the embodiment of the present application stores an executable program on it, and when the executable program is executed by the processor, an operation maintenance management information processing method is implemented. As shown in FIG. 1, the method includes:
  • Step 101 Obtain the data code block sent by the communication peer at the FlexE layer, and determine the first OAM data code block in the data code block according to the preset first determination rule;
  • FlexE is an intermediary layer created between MAC and PHY. FlexE provides a general mechanism to divide a physical Ethernet port into multiple Ethernet flexible hard pipes based on time slot scheduling. The data of each client (Client or FlexE Client) interface is scheduled and distributed to multiple different sub-channels in a time slot manner. And can achieve business isolation.
  • the OAM management adopted in the existing technology is implemented through protocols such as Ether OAM above the MAC layer such as Switch Core;
  • a processing engine may be provided to perform OAM management at the FlexE layer and process data code blocks of the FlexE layer encoded in 64B/66B; the FlexE OAM processing engine may be implemented by an ASIC or the like.
  • the data code blocks of the FlexE layer are usually transmitted to the FlexE layer by the communication peer through the PHY.
  • the preset first determination rule can be set according to the format of the OAM data code block, and the first OAM data code block in the data code block transmitted in the FlexE layer can be extracted into the processing engine through the information of the specific position of the OAM data code block deal with;
  • the format of the OAM data code block can be customized. As shown in FIG. 3, the format of the OAM data code block can be transmitted in the same 64B/66B format as the ordinary data code block, and the control code block is used. The 0 code in the code is distinguished. The 0 code is the 2nd to 9th bits.
  • 0x4B can be used to indicate that the data code block is the control code block; the C code is configurable by default, and 0xC can be used; when the C code in the 0x4B control code block 0xC, it is determined that the data code block is an OAM data code block; the OAM data code block can use 6 Data in the control block to carry OAM messages, and the specific field format of the OAM data code block can be shown in FIG. 4, where,
  • 0x4B is a 0 code, occupying 8 bits, and 0x48 indicates that the code block is a control code block;
  • Resv occupying 2bit, reserved field, default is 0;
  • Type occupying 6 bits, identifies different function types for different operations, maintenance and management;
  • Seq occupying 4 bits, is used to identify the sequence number of each data code block in the OAM data code block composed of multiple data code blocks;
  • CRC4 occupies 4 bits. For OAM code blocks, CRC4 bits are excluded, a total of 60 bits are checked; the algorithm polynomial of CRC4 can be x ⁇ 4+x+1.
  • the first OAM data code block includes more than one data code block
  • the first OAM data code block may be composed of one or more data code blocks, and the OAM data code block composition rule may be preset to set the data content in each data code block.
  • the OAM data code block may implement different management functions, and the function types of the OAM data code block may include: BAS function, APS function, CV function, 1DM function, 2DMM function, 2DMR function or CS function, etc. ;
  • the BAS function may include: connectivity check function, BIP function, RDI function, REI function, BER calculation function, CS_LF function and/or CS_RF function.
  • OAM data code block format can be as shown in Figure 5.
  • OAM data code blocks of different functions can be in the form of a single code block, which is composed of one data code block, or can be used in the form of multiple code blocks, which is composed of multiple data code blocks.
  • the functions, identification information, and priority of different OAM data code blocks The level can be shown in Table 1;
  • out-of-band information corresponding to the first OAM data code block may be obtained
  • the out-of-band information may be independently transmitted using a channel different from the ordinary data code block, or may be information for statistically calculating the data code block.
  • the out-of-band information of the same transmission time slot as the first OAM data code block may be determined as the out-of-band information corresponding to the first OAM data code block; the out-of-band information may include: Client ID, customer link signal quality Information, BIP check information, time stamp when receiving data code blocks, etc.: Client ID can be determined according to the time slot, BIP check information can be obtained by local technology, the time stamp when receiving data code blocks is the receiving time stamp of FlexE layer .
  • the out-of-band information can be used for processing OAM data code blocks.
  • Step 102 Determine the OAM function corresponding to the first OAM data code block according to a preset second determination rule; according to the function type corresponding to the first OAM data code block, use a preset parsing rule to parse out the first Parsing data in the OAM data code block; using the parsing data to perform the OAM function.
  • the second determination rule here may be determined according to the field format of the first OAM data code block. Taking the first OAM data code block in FIG. 5 as an example, the OAM function type corresponding to the first OAM data code block may be determined according to the type field;
  • the preset parsing rule can be determined according to the code block format corresponding to each OAM function type of the first OAM data code block; taking the BIP function of the BAS code block as an example, as can be seen from the code block format of the OAMOAM data code block in FIG. 5, Parse the 50th to 57th bits into a BIP check code; you can also analyze the data in multiple OAM data code blocks that make up CV and other functions.
  • the first OAM data code block is parsed according to the OAM function type, and the required analysis data can be extracted according to the field format of the first OAM data code block of each OAM function type, and the OAM function is executed.
  • the parsing data and the out-of-band information may be used to perform the OAM function
  • the first OAM data code block of some function types usually needs to be combined with out-of-band information to perform the corresponding OAM function.
  • the acquired out-of-band information can be combined for processing.
  • the BIP function in BAS needs to compare the BIP check code in the first OAM data code block with the BIP check code in out-of-band information;
  • the overall flow of the FlexE OAM processing engine in receiving data code blocks for processing, as shown in FIG. 6 includes:
  • Step 601 Receive data code blocks and out-of-band information, and extract OAM data code blocks.
  • the out-of-band information may include Client ID, customer link signal quality information, BIP check information, and time stamp when the code block is received;
  • step 602 may be performed for OAM data code blocks, and out-of-band information may be transmitted to the processing module of the FlexE OAM processing engine through the bus in the OAM processing engine, and processed in combination with the parsed OAM data code blocks;
  • Step 602 Parse out the data of the OAM data code block according to the OAM data code block type
  • Step 603 Process the data and out-of-band information of the parsed OAM data code block according to the OAM function type
  • Step 604 If the OAM function type includes sending information to the communication peer, reply to the corresponding information.
  • the method before using the first OAM data code block, or using the first OAM data code block and the out-of-band information, before performing the OAM function, the method further includes: An OAM data code block is checked for legality; the legality check includes calculation and checking of CRC values;
  • the FlexE OAM processing engine parsing process may be as shown in FIG. 7 and includes:
  • Step 701 The module first checks the validity of the received OAM code block, including the calculation and check of the CRC value;
  • Steps 702 to 706 Perform data analysis according to different function types of OAM data code blocks, and put the analyzed content into the internal BUS of the processing engine for specific processing modules of each code block.
  • the parsing process may be a process of extracting data required for each function type from the OAM data code block from a single code block OAM data code block or a multi code block OAM data code block.
  • the order of steps 702 to 706 may be in no particular order.
  • the functions included in them can be processed in sequence, and the processing flow can be as shown in FIG. 8; here, steps 801 to 807 can be executed in the order shown in FIG. 8 or can be passed Customized order execution;
  • Step 801 RDI information processing, used to determine the remote fault condition according to the RDI information in the OAM data code block;
  • Step 802 CS information processing, according to the CS_LF and/or CS_RF indication information in the OAM data code block, determine the link failure status;
  • Step 803 Periodic check, according to the data in the OAM data code block, determine the periodic status
  • Step 804 BIP information processing, used to compare the BIP check code in the BAS with the BIP check code in the out-of-band information to determine whether there is a transmission problem;
  • Step 805 BER bit error rate calculation processing, used to calculate the bit error rate of the network transmission
  • Step 806 REI processing, used to indicate the error code of the remote network connection
  • Step 807 APS can be triggered according to the link failure condition.
  • the link failure condition can include the bit error rate of step 805, etc.
  • the bit error rate can be adjusted to the user set signal error rate (SF) and signal degradation (SD) error rate
  • SF user set signal error rate
  • SD signal degradation
  • the CV function usually uses SAPI and DAPI to compare with the preset comparison value, and generates a warning when there is no match; here, the processing flow of the parsed CV function OAM data code block can be shown in Figure 9, including:
  • Step 901 The CV code block processing module includes Sequence and Number check;
  • the CV function OAM data code block can be composed of multiple data code blocks, as shown in FIG. 5 can be composed of 8 data code blocks, and the integrity of the CV function OAM data code block can be checked by a preset sequence number;
  • Step 902 Integrate the multi-data code blocks of the CV function OAM data code blocks SAPI/DAPI and store the multi-code blocks of SAPI/DAPI;
  • the data in multiple data code blocks can be read in sequence, integrated into complete SAPI/DAPI data, and stored;
  • Step 903 and when the multi-module reception is complete, the SAPI/DAPI comparison process corresponding to the locally configured Client, according to the comparison processing result, determine whether a mismatch error occurs and report to the system.
  • the CS function OAM data code block is used to compare the client signal with the pre-stored signal; the processing flow of the parsed CS function OAM data code block may only include the CS type check. From the received code block, the CS type and Compare the locally configured CS types, determine whether there is a mismatch error, and report to the system.
  • the CS type may include: unloaded, Ethernet, SDH, etc.
  • the 1DM function OAM data code block is used to detect the delay status sent to the receiver.
  • the processing flow of the parsed CV function OAM data code block can be as shown in FIG. 10, including:
  • Step 1001 In the processing module, the DM storage entry is indexed according to the Client ID of the out-of-band information, the serial number is checked, the multi-code block integration processing logic is performed, and the multi-code block time stamp storage of the 1DM, and when the multi-code block is received When it is complete, for the 1DM function OAM data code block shown in FIG. 5, two consecutive legal 1DM code blocks are correctly received to indicate complete reception;
  • Step 1002 Use the timestamp in the received 1DM function OAM data code block as the timestamp Ttx when sending to the far end, and the timestamp in the out-of-band information is the first 1DM OAM data code block received
  • the 2DMM function OAM data code block is used to detect the delay status of bidirectional transmission and reception. Usually, the 2DMR data code block is sent after receiving the 2DMM function OAM data code block. As shown in FIG. 5, the 2DMM function OAM data code block can be composed of 6 data The code block is the longest, and the processing flow of the parsed OAM data code block of the CV function can be shown in FIG. 11:
  • Step 1101; in the 2DMM processing module, the 2DMM function OAM data code block reception and integration processing, and the method of obtaining the time stamp are similar to the 1DM function OAM data code block processing method;
  • Step 1102 when the OAM data code block of the multi-code block 2DMM function is completely received, a process of replying to the 2DMR is required, and the 2DMR includes a total of 6 consecutive OAM data code blocks.
  • the timestamp content in the two data code blocks with Seq value of 0 and Seq value of 1 is copied from 2DMM; the timestamp in the out-of-band information is the timestamp of receiving 2DMM, and the timestamp of 2DMM will be received
  • the 2DMR function OAM data code block is used to detect the delay status of the two-way transmission and reception. Usually, the 2DMR data code block sent by the received communication peer is measured for delay.
  • the processing flow of the parsed 2DMR function OAM data code block can be As shown in Figure 12:
  • Step 1201 In the 2DMR processing module, the data code block is first subjected to multi-code block OAM data code block reception, integration processing, storage and other processing;
  • Step 1202 When the multiple code blocks are completely received, the time delay information in the 2DMR needs to be calculated.
  • the corresponding 2DMM transmission time stamp (Tx_f_TS can be taken from the 6 code blocks of the 2DMR ), 2DMM receiving timestamp (Rx_b_TS), 2DMR sending timestamp (Tx_b_TS), and expressing the timestamp in the out-of-band information as the timestamp of receiving the 2DMR OAM data code block, that is, the 2DMR receiving timestamp).
  • the two-way delay calculation expression can be: (2DMR receive timestamp-2DMM send timestamp)-(2DMR send timestamp-2DMM receive timestamp), used to provide upper-layer system use.
  • the second OAM data code block may be sent to the illustrated communication peer at the FlexE layer
  • the second OAM data code block may be a data code block that transmits in the opposite direction to the first OAM data code block, and is sent directly from the FlexE layer through the OAM processing engine, which can improve the real-time performance of OAM data code block processing and enhance the system Response performance;
  • the second OAM data code block may be a reply data code block that receives the OAM data code block sent by the communication peer, or an OAM data code block actively sent to the communication peer.
  • 16K data code block time pulses may be used as the transmission time unit, and the second OAM data code block is sent to the communication peer by a preset number of the transmission time units;
  • 16K data code block time pulses can be used as a time unit, and the line time count is used to indicate the transmission time of each OAM data code block.
  • Each function code block has a corresponding transmission count configuration.
  • the transmission count configuration value is based on the time of 16K code blocks. Therefore, different time intervals can be configured for the transmission count configuration value.
  • all client related entries are read at a time interval of 16K code blocks.
  • the send count configured in the entry is decremented by 1. When it is reduced to 0, it means that the class needs to be sent at this moment.
  • the processing of the sending module is performed, and the occurrence count is reset to the configured code block transmission period, which is used for time counting of the next OAM data code block.
  • the second OAM data code block when the second OAM data code block is a BAS function, a BIP check code corresponding to the second OAM data code block is set in the FlexE layer to the second OAM data code block; the first When the second OAM data code block is the 1DM function or the 2DMM function, the sending time of the second OAM data code block at the FlexE layer is set as the sending timestamp in the second OAM data block;
  • the control flag that needs to add BIP information needs to be added to the out-of-band information that is sent to the FlexE layer at the same time.
  • the FlexE layer edits the calculated BIP check code into the corresponding position; for the DM-related code blocks , You need to place a control flag with a timestamp added in the out-of-band information, and the FlexE layer will edit the obtained timestamp into the corresponding position when sending the code block.
  • the operation and maintenance management information processing device includes a processor, a memory, and an executable program stored on the memory and capable of being run by the processor, and the processor executes and implements the operation when the executable program is run
  • the maintenance management information processing method as shown in FIG. 1, the method includes:
  • Step 101 Obtain the data code block sent by the communication peer at the FlexE layer, and determine the first OAM data code block in the data code block according to the preset first determination rule;
  • FlexE is an intermediary layer created between MAC and PHY. FlexE provides a general mechanism to divide a physical Ethernet port into multiple Ethernet flexible hard pipes based on time slot scheduling. The data of each client (Client or FlexE Client) interface is scheduled and distributed to multiple different sub-channels in a time slot manner. And can achieve business isolation.
  • the OAM management adopted in the existing technology is implemented through protocols such as Ether OAM above the MAC layer such as Switch Core;
  • a processing engine may be provided to perform OAM management at the FlexE layer and process data code blocks of the FlexE layer encoded in 64B/66B; the FlexE OAM processing engine may be implemented by an ASIC or the like.
  • the data code blocks of the FlexE layer are usually transmitted to the FlexE layer by the communication peer through the PHY.
  • the preset first determination rule can be set according to the format of the OAM data code block, and the first OAM data code block in the data code block transmitted in the FlexE layer can be extracted into the processing engine through the information of the specific position of the OAM data code block deal with;
  • the format of the OAM data code block can be customized. As shown in FIG. 3, the format of the OAM data code block can be transmitted in the same 64B/66B format as the ordinary data code block, and the control code block is used. The 0 code in the code is distinguished. The 0 code is the 2nd to 9th bits.
  • 0x4B can be used to indicate that the data code block is the control code block; the C code is configurable by default, and 0xC can be used; when the C code in the 0x4B control code block 0xC, it is determined that the data code block is an OAM data code block; the OAM data code block can use 6 Data in the control block to carry OAM messages, and the specific field format of the OAM data code block can be shown in FIG. 4, where,
  • 0x4B is a 0 code, occupying 8 bits, and 0x48 indicates that the code block is a control code block;
  • Resv occupying 2bit, reserved field, default is 0;
  • Type occupying 6 bits, identifies different function types for different operations, maintenance and management;
  • Seq occupying 4 bits, is used to identify the sequence number of each data code block in the OAM data code block composed of multiple data code blocks;
  • CRC4 occupies 4 bits. For OAM code blocks, CRC4 bits are excluded, a total of 60 bits are checked; the algorithm polynomial of CRC4 can be x ⁇ 4+x+1.
  • the first OAM data code block includes more than one data code block
  • the first OAM data code block may be composed of one or more data code blocks, and the OAM data code block composition rule may be preset to set the data content in each data code block.
  • the OAM data code block may implement different management functions, and the function types of the OAM data code block may include: BAS function, APS function, CV function, 1DM function, 2DMM function, 2DMR function or CS function, etc. ;
  • the BAS function may include: a connectivity check function, a BIP function, an RDI function, a REI function, a BER calculation function, a CS_LF function, and/or a CS_RF function.
  • OAM data code block format can be as shown in Figure 5.
  • OAM data code blocks of different functions can be in the form of a single code block, which is composed of one data code block, or in the form of multiple code blocks, which is composed of multiple data code blocks.
  • the functions, identification information, and priority of different OAM data code blocks The level can be shown in Table 1;
  • out-of-band information corresponding to the first OAM data code block may be obtained
  • the out-of-band information may be independently transmitted using a channel different from the ordinary data code block, or may be information for statistically calculating the data code block.
  • the out-of-band information of the same transmission time slot as the first OAM data code block may be determined as the out-of-band information corresponding to the first OAM data code block; the out-of-band information may include: Client ID, customer link signal quality Information, BIP check information, time stamp when receiving data code blocks, etc.: Client ID can be determined according to the time slot, BIP check information can be obtained by local technology, the time stamp when receiving data code blocks is the receiving time stamp of FlexE layer .
  • the out-of-band information can be used for processing OAM data code blocks.
  • Step 102 Determine the OAM function corresponding to the first OAM data code block according to a preset second determination rule; according to the function type corresponding to the first OAM data code block, use a preset parsing rule to parse out the first Parsing data in the OAM data code block; using the parsing data to perform the OAM function.
  • the second determination rule here may be determined according to the field format of the first OAM data code block. Taking the first OAM data code block in FIG. 5 as an example, the OAM function type corresponding to the first OAM data code block may be determined according to the type field;
  • the preset parsing rule can be determined according to the code block format corresponding to each OAM function type of the first OAM data code block; taking the BIP function of the BAS code block as an example, as can be seen from the code block format of the OAMOAM data code block in FIG. 5, Parse the 50th to 57th bits into a BIP check code; you can also analyze the data in multiple OAM data code blocks that make up CV and other functions.
  • the first OAM data code block is parsed according to the OAM function type, and the required analysis data can be extracted according to the field format of the first OAM data code block of each OAM function type, and the OAM function is executed.
  • the parsing data and the out-of-band information may be used to perform the OAM function
  • the first OAM data code block of some function types usually needs to be combined with out-of-band information to perform the corresponding OAM function.
  • the acquired out-of-band information can be combined for processing.
  • the BIP function in BAS needs to compare the BIP check code in the first OAM data code block with the BIP check code in out-of-band information;
  • the overall flow of the FlexE OAM processing engine in receiving data code blocks for processing, as shown in FIG. 6 includes:
  • Step 601 Receive data code blocks and out-of-band information, and extract OAM data code blocks.
  • the out-of-band information may include Client ID, customer link signal quality information, BIP check information, and time stamp when the code block is received;
  • step 602 may be performed for OAM data code blocks, and out-of-band information may be transmitted to the processing module of the FlexE OAM processing engine through the bus in the OAM processing engine, and processed in combination with the parsed OAM data code blocks;
  • Step 602 Parse out the data of the OAM data code block according to the OAM data code block type
  • Step 603 Process the data and out-of-band information of the parsed OAM data code block according to the OAM function type
  • Step 604 If the OAM function type includes sending information to the communication peer, reply to the corresponding information.
  • the method before using the first OAM data code block, or using the first OAM data code block and the out-of-band information, before performing the OAM function, the method further includes: An OAM data code block is checked for legality; the legality check includes calculation and checking of CRC values;
  • the FlexE OAM processing engine parsing process may be as shown in FIG. 7 and includes:
  • Step 701 The module first checks the validity of the received OAM code block, including the calculation and check of the CRC value;
  • Steps 702 to 706 Perform data analysis according to different function types of OAM data code blocks, and put the analyzed content into the internal BUS of the processing engine for specific processing modules of each code block.
  • the parsing process may be a process of extracting data required for each function type from the OAM data code block from a single code block OAM data code block or a multi code block OAM data code block.
  • the order of steps 702 to 706 may be in no particular order.
  • the functions included in them can be processed in sequence, and the processing flow can be as shown in FIG. 8; here, steps 801 to 807 can be executed in the order shown in FIG. 8 or can be passed Customized order execution;
  • Step 801 RDI information processing, used to determine the remote fault condition according to the RDI information in the OAM data code block;
  • Step 802 CS information processing, according to the CS_LF and/or CS_RF indication information in the OAM data code block, determine the link failure status;
  • Step 803 Periodic check, according to the data in the OAM data code block, determine the periodic status
  • Step 804 BIP information processing, used to compare the BIP check code in the BAS with the BIP check code in the out-of-band information to determine whether there is a transmission problem;
  • Step 805 BER bit error rate calculation processing, used to calculate the bit error rate of the network transmission
  • Step 806 REI processing, used to indicate the error code of the remote network connection
  • Step 807 APS can be triggered according to the link failure condition.
  • the link failure condition can include the bit error rate of step 805, etc.
  • the bit error rate can be adjusted to the user set signal error rate (SF) and signal degradation (SD) error rate
  • SF signal error rate
  • SD signal degradation
  • the CV function usually uses SAPI and DAPI to compare with the preset comparison value, and generates a warning when there is no match; here, the processing flow of the parsed CV function OAM data code block can be shown in Figure 9, including:
  • Step 901 The CV code block processing module includes Sequence and Number check;
  • the CV function OAM data code block can be composed of multiple data code blocks, as shown in FIG. 5 can be composed of 8 data code blocks, and the integrity of the CV function OAM data code block can be checked by a preset sequence number;
  • Step 902 Integrate the multi-data code blocks of the CV function OAM data code blocks SAPI/DAPI and store the multi-code blocks of SAPI/DAPI;
  • the data in multiple data code blocks can be read in sequence, integrated into complete SAPI/DAPI data, and stored;
  • Step 903 and when the multi-module reception is complete, the SAPI/DAPI comparison process corresponding to the locally configured Client, according to the comparison processing result, determine whether a mismatch error occurs and report to the system.
  • the CS function OAM data code block is used to compare the client signal with the pre-stored signal; the processing flow of the parsed CS function OAM data code block may only include the CS type check. From the received code block, the CS type and Compare the locally configured CS types, determine whether there is a mismatch error, and report to the system.
  • the CS type may include: unloaded, Ethernet, SDH, etc.
  • the 1DM function OAM data code block is used to detect the delay status sent to the receiver.
  • the processing flow of the parsed CV function OAM data code block can be as shown in FIG. 10, including:
  • Step 1001 In the processing module, the DM storage entry is indexed according to the Client ID of the out-of-band information, the serial number is checked, the multi-code block integration processing logic is performed, and the multi-code block time stamp storage of the 1DM, and when the multi-code block is received When it is complete, for the 1DM function OAM data code block shown in FIG. 5, two consecutive legal 1DM code blocks are correctly received to indicate complete reception;
  • Step 1002 Use the timestamp in the received 1DM function OAM data code block as the timestamp Ttx when sending to the far end, and the timestamp in the out-of-band information is the first 1DM OAM data code block received
  • the 2DMM function OAM data code block is used to detect the delay status of bidirectional transmission and reception. Usually, the 2DMR data code block is sent after receiving the 2DMM function OAM data code block. As shown in FIG. 5, the 2DMM function OAM data code block can be composed of 6 data The code block is the longest, and the processing flow of the parsed OAM data code block of the CV function can be shown in FIG. 11:
  • Step 1101; in the 2DMM processing module, the 2DMM function OAM data code block reception and integration processing, and the method of obtaining the time stamp are similar to the 1DM function OAM data code block processing method;
  • Step 1102 when the OAM data code block of the multi-code block 2DMM function is completely received, a process of replying to the 2DMR is required, and the 2DMR includes a total of 6 consecutive OAM data code blocks.
  • the timestamp content in the two data code blocks with Seq value of 0 and Seq value of 1 is copied from 2DMM; the timestamp in the out-of-band information is the timestamp of receiving 2DMM, and the timestamp of 2DMM will be received
  • the 2DMR function OAM data code block is used to detect the delay status of the two-way transmission and reception. Usually, the 2DMR data code block sent by the received communication peer is measured for delay.
  • the processing flow of the parsed 2DMR function OAM data code block can be As shown in Figure 12:
  • Step 1201 In the 2DMR processing module, the data code block is first subjected to multi-code block OAM data code block reception, integration processing, storage and other processing;
  • Step 1202 When the multiple code blocks are completely received, the time delay information in the 2DMR needs to be calculated.
  • the corresponding 2DMM transmission time stamp (Tx_f_TS can be taken from the 6 code blocks of the 2DMR ), 2DMM receiving timestamp (Rx_b_TS), 2DMR sending timestamp (Tx_b_TS), and expressing the timestamp in the out-of-band information as the timestamp of receiving the 2DMR OAM data code block, that is, the 2DMR receiving timestamp).
  • the two-way delay calculation expression can be: (2DMR receive timestamp-2DMM send timestamp)-(2DMR send timestamp-2DMM receive timestamp), used to provide upper-layer system use.
  • the second OAM data code block may be sent to the illustrated communication peer at the FlexE layer
  • the second OAM data code block may be a data code block that transmits in the opposite direction to the first OAM data code block, and is sent directly from the FlexE layer through the OAM processing engine, which can improve the real-time performance of OAM data code block processing and enhance the system Response performance;
  • the second OAM data code block may be a reply data code block that receives the OAM data code block sent by the communication peer, or an OAM data code block actively sent to the communication peer.
  • 16K data code block time pulses may be used as the transmission time unit, and the second OAM data code block is sent to the communication peer by a preset number of the transmission time units;
  • 16K data code block time pulses can be used as one time unit, and the line time count is used to indicate the transmission time of each OAM data code block.
  • Each function code block has a corresponding transmission count configuration.
  • the transmission count configuration value is based on the time of 16K code blocks. Therefore, different time intervals can be configured for the transmission count configuration value.
  • all client related entries are read at a time interval of 16K code blocks.
  • the send count configured in the entry is decremented by 1. When it is reduced to 0, it means that the class needs to be sent at this moment.
  • the processing of the sending module is performed, and the occurrence count is reset to the configured code block transmission period, which is used for time counting of the next OAM data code block.
  • the second OAM data code block when the second OAM data code block is a BAS function, a BIP check code corresponding to the second OAM data code block is set in the FlexE layer to the second OAM data code block; the first When the second OAM data code block is the 1DM function or the 2DMM function, the sending time of the second OAM data code block at the FlexE layer is set as a sending timestamp in the second OAM data block;
  • the control flag that needs to add BIP information needs to be added to the out-of-band information that is sent to the FlexE layer at the same time.
  • the FlexE layer edits the calculated BIP check code into the corresponding position; for the DM-related code blocks , You need to place a control flag with a timestamp added in the out-of-band information, and the FlexE layer will edit the obtained timestamp into the corresponding position when sending the code block.

Landscapes

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

Abstract

本申请公开了一种运营维护管理(OAM)信息处理方法，在灵活以太网(FlexE)层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。本申请公开了一种运营维护管理信息处理装置、存储介质。

Description

运营维护管理信息处理方法和装置
相关申请的交叉引用
本申请基于申请号为201811601987.7、申请日为2018年12月26日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及灵活以太网(FlexE，Flex Ethernet)技术但不限于灵活以太网技术，尤其涉及一种运营维护管理(OAM，Operation Administration and Maintenance)信息处理方法和装置。
背景技术
FlexE为解决以太网接口的固定速率，限制以太网路由器，交换机的灵活性的问题而提出。是承载网实现业务隔离承载和网络分片的一种接口技术，近两年发展迅速，被各大标准组织广泛接纳；
如同其他各种网络技术一样，OAM对于是非常重要的功能，通过OAM可以保证服务质量，简化操作，降低运营成本。
通常，OAM数据码块是经FlexE层的处理后，送至MAC处理，然后送至主交换芯片(Switch Core)进行OAM报文处理，如此，实时性不高，系统响应性能低；
同时，对于网络运营商提出了客制化的OAM数据码块新格式，目前并没有新的处理方式可以处理。
因此，如何提高OAM数据码块处理实时性，提升系统响应性能，并适应不同OAM数据码块形式，是亟待解决的问题。
发明内容
本申请实施例的技术方案是这样实现的：本申请实施例提供了一种运营维护管理OAM信息处理方法，所述方法包括：
在FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；
根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。
本申请实施例还提供了一种运营维护管理信息处理装置，所述装置包括：获取模块和处理模块；其中，
所述获取模块，配置为FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；
所述处理模块，配置为根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。
本申请实施例还提供了一种存储介质，其上存储由可执行程序，所述可执行程序被处理器执行时实现如上述方法中任一种所述运营维护管理信息处理方法的步骤。
本申请实施例还提供了一种运营维护管理信息处理装置，包括处理器、存储器及存储在存储器上并能够有所述处理器运行的可执行程序，所述处理器运行所述可执行程序时执行如上述方法中任一种所述运营维护管理信息处理方法的步骤。
本申请实施例所提供的运营维护管理信息处理方法和装置，在FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。如此，在FlexE层直接处理OAM数据模块，提高OAM数据码块处理实时性，提升系统响应性能；采用预设的第一确定规则和第二确定规则，识别OAM数据码块及其功能类型，适应不同OAM数据码块形式。
附图说明
图1为本申请实施例运营维护管理信息处理方法的流程示意图；
图2为本申请实施例运营维护管理信息处理方法网络架构示意图；
图3为本申请实施例数据码块格式示意图；
图4为本申请实施例OAM数据码块格式示意图；
图5为本申请实施例不同功能OAM数据码块格式示意图；
图6为本申请实施例运营维护管理信息处理整体流程示意图；
图7为本申请实施例OAM数据码块解析流程示意图；
图8为本申请实施例BAS功能OAM数据码块处理流程示意图；
图9为本申请实施例CV功能OAM数据码块处理流程示意图；
图10为本申请实施例1DM功能OAM数据码块处理流程示意图；
图11为本申请实施例2DMM功能OAM数据码块处理流程示意图；
图12为本申请实施例2DMR功能OAM数据码块处理流程示意图；
图13为本申请实施例发送OAM数据码块流程示意图；
图14为本申请实施例运营维护管理信息处理装置组成结构示意图。
具体实施方式
本申请实施例中，在FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。
下面结合实施例对本申请再作进一步详细的说明。
本申请实施例提供的运营维护管理信息处理方法，如图1所示，所述方法包括：
步骤101：在FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；
如图2所示，FlexE是在MAC和PHY之间创造的一个中介层，FlexE提供了一种通用机制，基于时隙调度将一个物理以太网端口划分为多个以太网弹性硬管道，将多个客户(Client或FlexE Client)接口的数据按照时隙方式调度并分发至多个不同的子通道。并可实现业务隔离。现有技术采用的OAM管理都是通过Ether OAM等协议在MAC层以上如主交换芯片(Switch Core)实现的；
这里，可以设置一个处理引擎，在FlexE层进行OAM管理，对以64B/66B编码的FlexE层的数据码块进行处理；所述FlexE OAM处理引擎可以由ASIC等实现。所述FlexE层的数据码块通常由通信对端通过PHY传输到FlexE层。
所述预设第一确定规则可以根据OAM数据码块的格式设置，通过OAM数据码块特定位置的信息将在FlexE层传输的数据码块中的第一OAM数据码块提取到处理引擎中进行处理。
在一些实施例中，可以自定义OAM数据码块的格式，如图3所示，OAM数据码块的格式可以使用和普通的数据码块相同的64B/66B格式进行传输，并使用控制码块中的0代码区分，0代码为第2至9位，可以用0x4B表示该数据码块为控制码块；C代码缺省为可配置，可以采用0xC；当0x4B的控制码块中的C代码为0xC，则确定所述数据码块为OAM数据码块；OAM数据码块可以使用控制块内的6个Data承载OAM消息，OAM数据码块具体字段格式可以如图4所示，其中，
0x4B为0代码，占据8位(bit)，0x48表示该码块为控制码块；
Resv，占据2bit，预留字段，缺省采用0；
类型(Type)，占据6bit，标识不同操作维护管理的不同功能类型；
值(Value)，占据32bit，特定类型的OAM消息的内容；
C码，占据4bit，缺省为0xC，支持设置，表示数据码块为FlexE OAM数据码块；
序列号(Seq，Sequence number)，占据4bit，用于标识由多个数据码块构成的OAM数据码块中各数据码块的序号；
循环冗余校验码4(CRC4)，占据4bit，对OAM码块，排除CRC4位，共60bit校验；CRC4的算法多项式可以为x^4+x+1。
在一些实施例中，所述第一OAM数据码块包括一个以上的数据码块；
第一OAM数据码块可以由1个或多个数据码块组成，可以预设OAM数据码块组成规则，设置在各数据码块中的数据内容。
在一些实施例中，所述OAM数据码块可以实现不同的管理功能，OAM数据码块的功能类型可以包括：基础(BAS，BASIC)功能、自动保护倒换(APS，Automatic Protection Switching)功能、连通性检测(CV，Connectivity Verification)功能、单向时延检测(1DM，One-way Delay Measure)功能、双向时延检测信息(2DMM，Two-Way Delay Measurement Message)功能、 双向时延检测响应(2DMR，Two-Way Delay Measurement Reply)功能或客户信号(CS，Client signal)功能等；
所述BAS功能可以包括：连通性检查功能、比特交错奇偶校验(BIP，Bit Interleaved Parity)功能、远端故障指示(RDI，Remote Defect Indication)功能、远端误码指示(REI，Remote Error Indication)功能、误码率(BER，Bit Error Rate)计算功能、客户链路近端失效(CS_LF)功能和/或客户链路远端失效(CS_RF)功能。
对应不同的OAM功能，OAM数据码块格式可以如图5所示。不同功能的OAM数据码块可以采用单码块形式即由一个数据码块构成，也可以采用多码块形式即由多个个数据码块构成，不同OAM数据码块的功能、识别信息和优先级等可以如表1所示；
Figure PCTCN2019088196-appb-000001
表1
在一些实施例中，可以获取所述第一OAM数据码块对应的带外信息；
所述带外信息可以使用与普通数据码块不同的通道独立传送，也可以 是对数据码块进行统计的信息等。可以将与第一OAM数据码块相同传输时隙的带外信息确定为与所述第一OAM数据码块对应的带外信息；所述带外信息可以包括：客户标识(Client ID)，客户链路信号质量信息，BIP校验信息，接收数据码块时的时间戳等：Client ID可以根据时隙确定，BIP校验信息可以由本地技术得到，接收数据码块时的时间戳为FlexE层的接收时间戳。所述带外信息可以用于OAM数据码块的处理。
步骤102：根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。
这里所述第二确定规则可以根据第一OAM数据码块的字段格式确定，以图5的第一OAM数据码块为例，可以根据type字段确定第一OAM数据码块对应的OAM功能类型；
所述预设解析规则可以根据第一OAM数据码块各OAM功能类型对应的码块格式确定；以BAS码块的BIP功能为例，由图5的OAMOAM数据码块的码块格式可知，可以将第50位至第57位解析为BIP校验码；也可以将组成CV等功能的多个OAM数据码块中的数据进行解析。
将第一OAM数据码块根据OAM功能类型进行解析，可以根据各OAM功能类型第一OAM数据码块的字段格式提取需要的解析数据，执行所述OAM功能。
在一些实施例中，可以采用所述解析数据和所述带外信息，执行所述OAM功能；
通常，一些功能类型的第一OAM数据码块，通常需要结合带外信息，才能执行对应的OAM功能，这里可以结合获取的带外信息进行处理。如BAS中的BIP功能，需要将第一OAM数据码块中的BIP校验码与带外信 息中的BIP校验码进行对比等；
在一些实施例中，FlexE OAM处理引擎在接收数据码块进行处理的总体流程，如图6所示包括：
步骤601：接收数据码块和带外信息，提取OAM数据码块，带外信息可以包括Client ID，客户链路信号质量信息，BIP校验信息，接收码块时的时间戳等；
在一些实施例中，对于OAM数据码块可以执行步骤602，对于带外信息可以通过OAM处理引擎中的总线传输到FlexE OAM处理引擎的处理模块中，结合解析的OAM数据码块进行处理；
步骤602：根据OAM数据码块类型，解析出OAM数据码块的数据；
步骤603：根据OAM功能类型，处理解析出的OAM数据码块的数据和带外信息；
步骤604：如果OAM功能类型包含向通信对端发送信息，则回复对应信息。
在一些实施例中，采用所述第一OAM数据码块，或采用所述第一OAM数据码块和所述带外信息，执行所述OAM功能之前，所述方法还包括：对所述第一OAM数据码块进行合法性检查；所述合法性检查包括CRC值的计算和检查；
在一些实施例中，FlexE OAM处理引擎解析流程可以如图7所示，包括：
步骤701：该模块首先对接收到的OAM码块做合法性检查，包括CRC值的计算和检查；
步骤702～706：根据不同的OAM数据码块的功能类型，分别进行数据解析，将解析的内容放入处理引擎内部BUS中，用于各码块具体处理模块。这里，所述解析过程可以是从单码块OAM数据码块或多码块OAM数据码 块中，将各功能类型所需的数据从OAM数据码块中提取的过程。步骤702至步骤706顺序可以不分先后。
对解析后的BAS功能OAM数据码块，可以依次对其包括的功能进行处理，处理流程可以如图8所示；这里，步骤801至步骤807可以按照图8所示的顺序执行，也可以通过自定义的顺序执行；
步骤801：RDI信息处理，用于根据OAM数据码块中RDI信息确定远端的故障状况；
步骤802：CS信息处理，根据OAM数据码块中CS_LF和/或CS_RF指示信息，确定链路失效状况；
步骤803：周期检查，根据OAM数据码块中的数据，确定周期状况；
步骤804：BIP信息处理，用于将BAS中的BIP校验码与带外信息中的BIP校验码进行比较，确定是否出现传输问题；
步骤805：BER误码率计算处理，用于计算网络传输的误码率；
步骤806：REI处理，用于指示远端网络连接的误码；
步骤807：可以根据链路失效状况触发APS，链路失效状况可以包括步骤805的误码率等，可以将误码率与用户设置的信号失效(SF)和信号劣化(SD)的误码率门限进行比较，超过相应门限值，则认为产生SF或SD，触发APS处理；当误码率低于SF或SD的误码率门限值，则清除SF或SD，触发可配置的APS回切处理。
CV功能通常采用接收的源接入点标识(SAPI，Source Access Point Identifier)和目的接入点标识(DAPI，Destination Access Point Identifier)和预设的对比值进行比较，不匹配时生成警告；这里，对解析后的CV功能OAM数据码块的处理流程可以如图9所示，包括：
步骤901：CV码块处理模块包括，序列号(Sequence Number)检查；
这里，CV功能OAM数据码块可以由多个数据码块组成，如图5所示 可以由8个数据码块组成，可以通过预设的序号检查CV功能OAM数据码块完整性；
步骤902：将CV功能OAM数据码块SAPI/DAPI的多数据码块整合处理，并存储SAPI/DAPI的多码块；
这里，可以依次读取多个数据码块中的数据，整合成完整的SAPI/DAPI数据，并进行存储；
步骤903：以及当多模块接收完整时，和本地配置的Client对应的SAPI/DAPI的比较处理，根据比较处理结果，判断是否出现不匹配错误，上报系统。
CS功能OAM数据码块用于比较客户信号的与预存信号进行比较；对解析后的CS功能的OAM数据码块的处理流程可以仅包含CS类型检查，从接收到的码块中的CS类型与本地配置的CS类型进行比较，判断是否出现不匹配错误，上报系统。这里，CS类型可以包括：未装载、以太网、同步数字体系(SDH，Synchronous Digital Hierarchy)等。
1DM功能OAM数据码块用于检测发送于接收的延迟状况，对解析后的CV功能的OAM数据码块的处理流程可以如图10所示，包括：
步骤1001处理模块中，根据带外信息的Client ID来索引DM存储表项，进行序列号的检查，进行多码块整合处理逻辑，以及1DM的多码块时戳存储，以及当多码块接收完整时，对于图5所示的1DM功能OAM数据码块而言，连续合法的两个1DM码块正确接收即表示完整接收；
步骤1002，从用接收到的1DM功能OAM数据码块中的时间戳，作为为远端设置发送时的时间戳Ttx，带外信息的中的时间戳为接收到第一个1DM OAM数据码块的时间戳Trx，根据规范定义，计算线路延时为Delay＝Trx–Ttx，并可以做表项记录，用于提供上层系统使用。
2DMM功能OAM数据码块用于检测双向发送于接收的延迟状况，通 常在接收2DMM功能OAM数据码块后发送2DMR数据码块，如图5所示，2DMM功能OAM数据码块可以由6个数据码块最长，对解析后的CV功能的OAM数据码块的处理流程可以如图11所示：
步骤1101；在2DMM处理模块中，2DMM功能OAM数据码块接收和整合处理，以及获取时间戳的方法与1DM功能OAM数据码块的处理方法类似；
步骤1102，当多码块2DMM功能OAM数据码块接收完整时，需要做回复2DMR的处理，2DMR共包括6个连续的OAM数据码块。回复的2DMR中，Seq值为0和Seq值为1的两个数据码块中的时间戳内容从2DMM中复制；带外信息中的时间戳为接收2DMM的时间戳，将接收2DMM的时间戳编辑在回复Seq值为2和Seq值为3的两个2DMM功能OAM数据码块中；并将回复DMR时的时间戳编辑在Seq值为4和Seq值为5两个2DMM功能OAM数据码块中。2DMR发送至通信对端FlexE设备，进行时延测量(DM，Delay Measure)的计算。
2DMR功能OAM数据码块用于检测双向发送于接收的延迟状况，通常对接收的通信对端发送的2DMR数据码块，进行时延测量，对解析后的2DMR功能OAM数据码块的处理流程可以如图12所示：
步骤1201：在2DMR处理模块中，首先对数据码块，进行多码块OAM数据码块进行接收、整合处理，存储等处理；
步骤1202：当多码块接收完整时，需要对2DMR中的时戳信息进行时延计算，如图5中2DMR格式所示，可以从2DMR的6个码块中取出对应2DMM发送时戳(Tx_f_TS)，2DMM接收时戳(Rx_b_TS)，2DMR发送时戳(Tx_b_TS)，并将带外信息中时间戳表达为接收到2DMR OAM数据码块的时戳，即2DMR接收时戳)。双向延时计算表达式可以是：(2DMR接收时戳-2DMM发送时戳)-(2DMR发送时戳-2DMM接收时戳)，用于 提供上层系统使用。
在一些实施例中，可以在FlexE层，向所示通信对端发送第二OAM数据码块；
这里，所述第二OAM数据码块可以是与第一OAM数据码块传输方向相反的数据码块，通过OAM处理引擎直接从FlexE层进行发送，可以提高OAM数据码块处理实时性，提升系统响应性能；第二OAM数据码块可以是接收到通信对端发送的OAM数据码块的回复数据码块，也可以是向通信对端主动发送的OAM数据码块。
在一些实施例中，可以将16K个数据码块时间脉冲作为发射时间单位，间隔预设个数的所述发射时间单位向通信对端发送所述第二OAM数据码块；
这里，如图13所示，可以以16K个数据码块时间脉冲作为一个时间单位，进行时间计数，用于指示各个OAM数据码块的发送时间。各功能码块都有相应的发送计数配置，发送计数配置值以16K个码块的时间为单位，由此发送计数配置值可以配置不同的时间间隔。整个时间循环，按16K个码块的时间间隔脉冲读取所有Client的相关表项，每处理一次，表项中配置的发送计数则减1，当减到0时，表示该时刻需要发送该类OAM数据码块，则进行发送模块的处理，并将发生计数重置到配置的码块发送周期，用于下一个OAM数据码块的时间计数。
在一些实施例中；所述第二OAM数据码块为BAS功能时，在所述FlexE层向第二OAM数据码块中设置第二OAM数据码块对应的BIP的校验码；所述第二OAM数据码块为1DM功能或2DMM功能时，将所述第二OAM数据码块在所述FlexE层的发送时间，在所述第二OAM数据块中设置为发送时间戳；
对于BAS，需在伴随发送码块同时发送至FlexE层的带外信息中增加 需要添加BIP信息的控制Flag，由FlexE层将计算的BIP的校验码编辑入相应位置；对于DM相关的码块，需要在带外信息中放置添加时间戳的控制Flag，由FlexE层在发送码块时将取得的时间戳编辑入相应位置。
本申请实施例提供的运营维护管理信息处理装置，如图14所示，所述装置包括：获取模块141和处理模块142；其中，
所述获取模块141，配置为在FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；
如图2所示，FlexE是在MAC和PHY之间创造的一个中介层，FlexE提供了一种通用机制，基于时隙调度将一个物理以太网端口划分为多个以太网弹性硬管道，将多个客户(Client或FlexE Client)接口的数据按照时隙方式调度并分发至多个不同的子通道。并可实现业务隔离。现有技术采用的OAM管理都是通过Ether OAM等协议在MAC层以上如Switch Core实现的。
这里，可以设置一个处理引擎，在FlexE层进行OAM管理，对以64B/66B编码的FlexE层的数据码块进行处理；所述FlexE OAM处理引擎可以由ASIC等实现。所述FlexE层的数据码块通常由通信对端通过PHY传输到FlexE层。
所述预设第一确定规则可以根据OAM数据码块的格式设置，通过OAM数据码块特定位置的信息将在FlexE层传输的数据码块中的第一OAM数据码块提取到处理引擎中进行处理。
在一些实施例中，可以自定义OAM数据码块的格式，如图3所示，OAM数据码块的格式可以使用和普通的数据码块相同的64B/66B格式进行传输，并使用控制码块中的0代码区分，0代码为第2至9位，可以用0x4B表示该数据码块为控制码块；C代码缺省为可配置，可以采用0xC；当0x4B的控制码块中的C代码为0xC，则确定所述数据码块为OAM数据码块； OAM数据码块可以使用控制块内的6个Data承载OAM消息，OAM数据码块具体字段格式可以如图4所示，其中，
0x4B为0代码，占据8bit，0x48表示该码块为控制码块；
Resv，占据2bit，预留字段，缺省采用0；
Type，占据6bit，标识不同操作维护管理的不同功能类型；
Value，占据32bit，特定类型的OAM消息的内容；
C码，占据4bit，缺省为0xC，支持设置，表示数据码块为FlexE OAM数据码块；
Seq，占据4bit，用于标识由多个数据码块构成的OAM数据码块中各数据码块的序号；
CRC4，占据4bit，对OAM码块，排除CRC4位，共60bit校验；CRC4的算法多项式可以为x^4+x+1。
在一些实施例中，所述第一OAM数据码块包括一个以上的数据码块；
第一OAM数据码块可以由1个或多个数据码块组成，可以预设OAM数据码块组成规则，设置在各数据码块中的数据内容。
在一些实施例中，所述OAM数据码块可以实现不同的管理功能，OAM数据码块的功能类型可以包括：BAS功能、APS功能、CV功能、1DM功能、2DMM功能、2DMR功能或CS功能等；
所述BAS功能可以包括：连通性检查功能、BIP功能、RDI功能、REI功能、BER计算功能、CS_LF功能和/或CS_RF功能。
对应不同的OAM功能，OAM数据码块格式可以如图5所示。不同功能的OAM数据码块可以采用单码块形式即由一个数据码块构成，也可以采用多码块形式即由多个个数据码块构成，不同OAM数据码块的功能、识别信息和优先级等可以如表1所示；
在一些实施例中，可以获取所述第一OAM数据码块对应的带外信息；
所述带外信息可以使用与普通数据码块不同的通道独立传送，也可以是对数据码块进行统计的信息等。可以将与第一OAM数据码块相同传输时隙的带外信息确定为与所述第一OAM数据码块对应的带外信息；所述带外信息可以包括：Client ID，客户链路信号质量信息，BIP校验信息，接收数据码块时的时间戳等：Client ID可以根据时隙确定，BIP校验信息可以由本地技术得到，接收数据码块时的时间戳为FlexE层的接收时间戳。所述带外信息可以用于OAM数据码块的处理。
所述处理模块142，配置为根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。
这里所述第二确定规则可以根据第一OAM数据码块的字段格式确定，以图5的第一OAM数据码块为例，可以根据type字段确定第一OAM数据码块对应的OAM功能类型；
所述预设解析规则可以根据第一OAM数据码块各OAM功能类型对应的码块格式确定；以BAS码块的BIP功能为例，由图5的OAMOAM数据码块的码块格式可知，可以将第50位至第57位解析为BIP校验码；也可以将组成CV等功能的多个OAM数据码块中的数据进行解析。
将第一OAM数据码块根据OAM功能类型进行解析，可以根据各OAM功能类型第一OAM数据码块的字段格式提取需要的解析数据，执行所述OAM功能。
在一些实施例中，可以采用所述解析数据和所述带外信息，执行所述OAM功能；
通常，一些功能类型的第一OAM数据码块，通常需要结合带外信息，才能执行对应的OAM功能，这里可以结合获取的带外信息进行处理。如 BAS中的BIP功能，需要将第一OAM数据码块中的BIP校验码与带外信息中的BIP校验码进行对比等。
在一些实施例中，FlexE OAM处理引擎在接收数据码块进行处理的总体流程，如图6所示包括：
步骤601：接收数据码块和带外信息，提取OAM数据码块，带外信息可以包括Client ID，客户链路信号质量信息，BIP校验信息，接收码块时的时间戳等；
在一些实施例中，对于OAM数据码块可以执行步骤602，对于带外信息可以通过OAM处理引擎中的总线传输到FlexE OAM处理引擎的处理模块中，结合解析的OAM数据码块进行处理；
步骤602：根据OAM数据码块类型，解析出OAM数据码块的数据；
步骤603：根据OAM功能类型，处理解析出的OAM数据码块的数据和带外信息；
步骤604：如果OAM功能类型包含向通信对端发送信息，则回复对应信息。
在一些实施例中，采用所述第一OAM数据码块，或采用所述第一OAM数据码块和所述带外信息，执行所述OAM功能之前，所述方法还包括：对所述第一OAM数据码块进行合法性检查；所述合法性检查包括CRC值的计算和检查；
在一些实施例中，FlexE OAM处理引擎解析流程可以如图7所示，包括：
步骤701：该模块首先对接收到的OAM码块做合法性检查，包括CRC值的计算和检查；
步骤702～706：根据不同的OAM数据码块的功能类型，分别进行数据解析，将解析的内容放入处理引擎内部BUS中，用于各码块具体处理模块。 这里，所述解析过程可以是从单码块OAM数据码块或多码块OAM数据码块中，将各功能类型所需的数据从OAM数据码块中提取的过程。步骤702至步骤706顺序可以不分先后。
对解析后的BAS功能OAM数据码块，可以依次对其包括的功能进行处理，处理流程可以如图8所示；这里，步骤801至步骤807可以按照图8所示的顺序执行，也可以通过自定义的顺序执行；
步骤801：RDI信息处理，用于根据OAM数据码块中RDI信息确定远端的故障状况；
步骤802：CS信息处理，根据OAM数据码块中CS_LF和/或CS_RF指示信息，确定链路失效状况；
步骤803：周期检查，根据OAM数据码块中的数据，确定周期状况；
步骤804：BIP信息处理，用于将BAS中的BIP校验码与带外信息中的BIP校验码进行比较，确定是否出现传输问题；
步骤805：BER误码率计算处理，用于计算网络传输的误码率；
步骤806：REI处理，用于指示远端网络连接的误码；
步骤807：可以根据链路失效状况触发APS，链路失效状况可以包括步骤805的误码率等，可以将误码率与用户设置的信号失效(SF)和信号劣化(SD)的误码率门限进行比较，超过相应门限值，则认为产生SF或SD，触发APS处理；当误码率低于SF或SD的误码率门限值，则清除SF或SD，触发可配置的APS回切处理。
CV功能通常采用SAPI和DAPI和预设的对比值进行比较，不匹配时生成警告；这里，对解析后的CV功能OAM数据码块的处理流程可以如图9所示，包括：
步骤901：CV码块处理模块包括，Sequence Number检查；
这里，CV功能OAM数据码块可以由多个数据码块组成，如图5所示 可以由8个数据码块组成，可以通过预设的序号检查CV功能OAM数据码块完整性；
步骤902：将CV功能OAM数据码块SAPI/DAPI的多数据码块整合处理，并存储SAPI/DAPI的多码块；
这里，可以依次读取多个数据码块中的数据，整合成完整的SAPI/DAPI数据，并进行存储；
步骤903：以及当多模块接收完整时，和本地配置的Client对应的SAPI/DAPI的比较处理，根据比较处理结果，判断是否出现不匹配错误，上报系统。
CS功能OAM数据码块用于比较客户信号的与预存信号进行比较；对解析后的CS功能的OAM数据码块的处理流程可以仅包含CS类型检查，从接收到的码块中的CS类型与本地配置的CS类型进行比较，判断是否出现不匹配错误，上报系统。这里，CS类型可以包括：未装载、以太网、SDH等。
1DM功能OAM数据码块用于检测发送于接收的延迟状况，对解析后的CV功能的OAM数据码块的处理流程可以如图10所示，包括：
步骤1001处理模块中，根据带外信息的Client ID来索引DM存储表项，进行序列号的检查，进行多码块整合处理逻辑，以及1DM的多码块时戳存储，以及当多码块接收完整时，对于图5所示的1DM功能OAM数据码块而言，连续合法的两个1DM码块正确接收即表示完整接收；
步骤1002，从用接收到的1DM功能OAM数据码块中的时间戳，作为为远端设置发送时的时间戳Ttx，带外信息的中的时间戳为接收到第一个1DM OAM数据码块的时间戳Trx，根据规范定义，计算线路延时为Delay＝Trx–Ttx，并可以做表项记录，用于提供上层系统使用。
2DMM功能OAM数据码块用于检测双向发送于接收的延迟状况，通 常在接收2DMM功能OAM数据码块后发送2DMR数据码块，如图5所示，2DMM功能OAM数据码块可以由6个数据码块最长，对解析后的CV功能的OAM数据码块的处理流程可以如图11所示：
步骤1101；在2DMM处理模块中，2DMM功能OAM数据码块接收和整合处理，以及获取时间戳的方法与1DM功能OAM数据码块的处理方法类似；
步骤1102，当多码块2DMM功能OAM数据码块接收完整时，需要做回复2DMR的处理，2DMR共包括6个连续的OAM数据码块。回复的2DMR中，Seq值为0和Seq值为1的两个数据码块中的时间戳内容从2DMM中复制；带外信息中的时间戳为接收2DMM的时间戳，将接收2DMM的时间戳编辑在回复Seq值为2和Seq值为3的两个2DMM功能OAM数据码块中；并将回复DMR时的时间戳编辑在Seq值为4和Seq值为5两个2DMM功能OAM数据码块中。2DMR发送至通信对端FlexE设备，进行DM的计算。
2DMR功能OAM数据码块用于检测双向发送于接收的延迟状况，通常对接收的通信对端发送的2DMR数据码块，进行时延测量，对解析后的2DMR功能OAM数据码块的处理流程可以如图12所示：
步骤1201：在2DMR处理模块中，首先对数据码块，进行多码块OAM数据码块进行接收、整合处理，存储等处理；
步骤1202：当多码块接收完整时，需要对2DMR中的时戳信息进行时延计算，如图5中2DMR格式所示，可以从2DMR的6个码块中取出对应2DMM发送时戳(Tx_f_TS)，2DMM接收时戳(Rx_b_TS)，2DMR发送时戳(Tx_b_TS)，并将带外信息中时间戳表达为接收到2DMR OAM数据码块的时戳，即2DMR接收时戳)。双向延时计算表达式可以是：(2DMR接收时戳-2DMM发送时戳)-(2DMR发送时戳-2DMM接收时戳)，用于 提供上层系统使用。
在一些实施例中，所述装置还可以包括发送模块143，用于在FlexE层，向所示通信对端发送第二OAM数据码块；
这里，所述第二OAM数据码块可以是与第一OAM数据码块传输方向相反的数据码块，通过OAM处理引擎直接从FlexE层进行发送，可以提高OAM数据码块处理实时性，提升系统响应性能；第二OAM数据码块可以是接收到通信对端发送的OAM数据码块的回复数据码块，也可以是向通信对端主动发送的OAM数据码块。
在一些实施例中，可以将16K个数据码块时间脉冲作为发射时间单位，间隔预设个数的所述发射时间单位向通信对端发送所述第二OAM数据码块；
这里，如图13所示，可以以16K个数据码块时间脉冲作为一个时间单位，行时间计数，用于指示各个OAM数据码块的发送时间。各功能码块都有相应的发送计数配置，发送计数配置值以16K个码块的时间为单位，由此发送计数配置值可以配置不同的时间间隔。整个时间循环，按16K个码块的时间间隔脉冲读取所有Client的相关表项，每处理一次，表项中配置的发送计数则减1，当减到0时，表示该时刻需要发送该类OAM数据码块，则进行发送模块的处理，并将发生计数重置到配置的码块发送周期，用于下一个OAM数据码块的时间计数。
在一些实施例中；所述第二OAM数据码块为BAS功能时，在所述FlexE层向第二OAM数据码块中设置第二OAM数据码块对应的BIP的校验码；所述第二OAM数据码块为1DM功能或2DMM功能时，将所述第二OAM数据码块在所述FlexE层的发送时间，在所述第二OAM数据块中设置为发送时间戳；
对于BAS，需在伴随发送码块同时发送至FlexE层的带外信息中增加 需要添加BIP信息的控制Flag，由FlexE层将计算的BIP的校验码编辑入相应位置；对于DM相关的码块，需要在带外信息中放置添加时间戳的控制Flag，由FlexE层在发送码块时将取得的时间戳编辑入相应位置。
在实际应用中，所述获取模块141、处理模块142和发送模块143均可以由运营维护管理信息处理系统中的CPU、微处理器(MCU)、数字信号处理器(DSP)、或现场可编程门阵列(FPGA)等实现。
本申请实施例提供的存储介质，其上存储由可执行程序，所述可执行程序被处理器执行时实现运营维护管理信息处理方法，如图1所示，所述方法包括：
步骤101：在FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；
如图2所示，FlexE是在MAC和PHY之间创造的一个中介层，FlexE提供了一种通用机制，基于时隙调度将一个物理以太网端口划分为多个以太网弹性硬管道，将多个客户(Client或FlexE Client)接口的数据按照时隙方式调度并分发至多个不同的子通道。并可实现业务隔离。现有技术采用的OAM管理都是通过Ether OAM等协议在MAC层以上如Switch Core实现的；
这里，可以设置一个处理引擎，在FlexE层进行OAM管理，对以64B/66B编码的FlexE层的数据码块进行处理；所述FlexE OAM处理引擎可以由ASIC等实现。所述FlexE层的数据码块通常由通信对端通过PHY传输到FlexE层。
所述预设第一确定规则可以根据OAM数据码块的格式设置，通过OAM数据码块特定位置的信息将在FlexE层传输的数据码块中的第一OAM数据码块提取到处理引擎中进行处理；
在一些实施例中，可以自定义OAM数据码块的格式，如图3所示， OAM数据码块的格式可以使用和普通的数据码块相同的64B/66B格式进行传输，并使用控制码块中的0代码区分，0代码为第2至9位，可以用0x4B表示该数据码块为控制码块；C代码缺省为可配置，可以采用0xC；当0x4B的控制码块中的C代码为0xC，则确定所述数据码块为OAM数据码块；OAM数据码块可以使用控制块内的6个Data承载OAM消息，OAM数据码块具体字段格式可以如图4所示，其中，
0x4B为0代码，占据8bit，0x48表示该码块为控制码块；
Resv，占据2bit，预留字段，缺省采用0；
Type，占据6bit，标识不同操作维护管理的不同功能类型；
Value，占据32bit，特定类型的OAM消息的内容；
C码，占据4bit，缺省为0xC，支持设置，表示数据码块为FlexE OAM数据码块；
Seq，占据4bit，用于标识由多个数据码块构成的OAM数据码块中各数据码块的序号；
CRC4，占据4bit，对OAM码块，排除CRC4位，共60bit校验；CRC4的算法多项式可以为x^4+x+1。
在一些实施例中，所述第一OAM数据码块包括一个以上的数据码块；
第一OAM数据码块可以由1个或多个数据码块组成，可以预设OAM数据码块组成规则，设置在各数据码块中的数据内容。
在一些实施例中，所述OAM数据码块可以实现不同的管理功能，OAM数据码块的功能类型可以包括：BAS功能、APS功能、CV功能、1DM功能、2DMM功能、2DMR功能或CS功能等；
所述BAS功能可以包括：连通性检查功能、BIP功能、RDI功能、REI功能、BER计算功能、CS_LF功能和/或CS_RF功能。
对应不同的OAM功能，OAM数据码块格式可以如图5所示。不同功 能的OAM数据码块可以采用单码块形式即由一个数据码块构成，也可以采用多码块形式即由多个个数据码块构成，不同OAM数据码块的功能、识别信息和优先级等可以如表1所示；
在一些实施例中，可以获取所述第一OAM数据码块对应的带外信息；
所述带外信息可以使用与普通数据码块不同的通道独立传送，也可以是对数据码块进行统计的信息等。可以将与第一OAM数据码块相同传输时隙的带外信息确定为与所述第一OAM数据码块对应的带外信息；所述带外信息可以包括：Client ID，客户链路信号质量信息，BIP校验信息，接收数据码块时的时间戳等：Client ID可以根据时隙确定，BIP校验信息可以由本地技术得到，接收数据码块时的时间戳为FlexE层的接收时间戳。所述带外信息可以用于OAM数据码块的处理。
步骤102：根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。
这里所述第二确定规则可以根据第一OAM数据码块的字段格式确定，以图5的第一OAM数据码块为例，可以根据type字段确定第一OAM数据码块对应的OAM功能类型；
所述预设解析规则可以根据第一OAM数据码块各OAM功能类型对应的码块格式确定；以BAS码块的BIP功能为例，由图5的OAMOAM数据码块的码块格式可知，可以将第50位至第57位解析为BIP校验码；也可以将组成CV等功能的多个OAM数据码块中的数据进行解析。
将第一OAM数据码块根据OAM功能类型进行解析，可以根据各OAM功能类型第一OAM数据码块的字段格式提取需要的解析数据，执行所述OAM功能。
在一些实施例中，可以采用所述解析数据和所述带外信息，执行所述OAM功能；
通常，一些功能类型的第一OAM数据码块，通常需要结合带外信息，才能执行对应的OAM功能，这里可以结合获取的带外信息进行处理。如BAS中的BIP功能，需要将第一OAM数据码块中的BIP校验码与带外信息中的BIP校验码进行对比等；
在一些实施例中，FlexE OAM处理引擎在接收数据码块进行处理的总体流程，如图6所示包括：
步骤601：接收数据码块和带外信息，提取OAM数据码块，带外信息可以包括Client ID，客户链路信号质量信息，BIP校验信息，接收码块时的时间戳等；
在一些实施例中，对于OAM数据码块可以执行步骤602，对于带外信息可以通过OAM处理引擎中的总线传输到FlexE OAM处理引擎的处理模块中，结合解析的OAM数据码块进行处理；
步骤602：根据OAM数据码块类型，解析出OAM数据码块的数据；
步骤603：根据OAM功能类型，处理解析出的OAM数据码块的数据和带外信息；
步骤604：如果OAM功能类型包含向通信对端发送信息，则回复对应信息。
在一些实施例中，采用所述第一OAM数据码块，或采用所述第一OAM数据码块和所述带外信息，执行所述OAM功能之前，所述方法还包括：对所述第一OAM数据码块进行合法性检查；所述合法性检查包括CRC值的计算和检查；
在一些实施例中，FlexE OAM处理引擎解析流程可以如图7所示，包括：
步骤701：该模块首先对接收到的OAM码块做合法性检查，包括CRC值的计算和检查；
步骤702～706：根据不同的OAM数据码块的功能类型，分别进行数据解析，将解析的内容放入处理引擎内部BUS中，用于各码块具体处理模块。这里，所述解析过程可以是从单码块OAM数据码块或多码块OAM数据码块中，将各功能类型所需的数据从OAM数据码块中提取的过程。步骤702至步骤706顺序可以不分先后。
对解析后的BAS功能OAM数据码块，可以依次对其包括的功能进行处理，处理流程可以如图8所示；这里，步骤801至步骤807可以按照图8所示的顺序执行，也可以通过自定义的顺序执行；
步骤801：RDI信息处理，用于根据OAM数据码块中RDI信息确定远端的故障状况；
步骤802：CS信息处理，根据OAM数据码块中CS_LF和/或CS_RF指示信息，确定链路失效状况；
步骤803：周期检查，根据OAM数据码块中的数据，确定周期状况；
步骤804：BIP信息处理，用于将BAS中的BIP校验码与带外信息中的BIP校验码进行比较，确定是否出现传输问题；
步骤805：BER误码率计算处理，用于计算网络传输的误码率；
步骤806：REI处理，用于指示远端网络连接的误码；
步骤807：可以根据链路失效状况触发APS，链路失效状况可以包括步骤805的误码率等，可以将误码率与用户设置的信号失效(SF)和信号劣化(SD)的误码率门限进行比较，超过相应门限值，则认为产生SF或SD，触发APS处理；当误码率低于SF或SD的误码率门限值，则清除SF或SD，触发可配置的APS回切处理。
CV功能通常采用SAPI和DAPI和预设的对比值进行比较，不匹配时 生成警告；这里，对解析后的CV功能OAM数据码块的处理流程可以如图9所示，包括：
步骤901：CV码块处理模块包括，Sequence Number检查；
这里，CV功能OAM数据码块可以由多个数据码块组成，如图5所示可以由8个数据码块组成，可以通过预设的序号检查CV功能OAM数据码块完整性；
步骤902：将CV功能OAM数据码块SAPI/DAPI的多数据码块整合处理，并存储SAPI/DAPI的多码块；
这里，可以依次读取多个数据码块中的数据，整合成完整的SAPI/DAPI数据，并进行存储；
步骤903：以及当多模块接收完整时，和本地配置的Client对应的SAPI/DAPI的比较处理，根据比较处理结果，判断是否出现不匹配错误，上报系统。
CS功能OAM数据码块用于比较客户信号的与预存信号进行比较；对解析后的CS功能的OAM数据码块的处理流程可以仅包含CS类型检查，从接收到的码块中的CS类型与本地配置的CS类型进行比较，判断是否出现不匹配错误，上报系统。这里，CS类型可以包括：未装载、以太网、SDH等。
1DM功能OAM数据码块用于检测发送于接收的延迟状况，对解析后的CV功能的OAM数据码块的处理流程可以如图10所示，包括：
步骤1001处理模块中，根据带外信息的Client ID来索引DM存储表项，进行序列号的检查，进行多码块整合处理逻辑，以及1DM的多码块时戳存储，以及当多码块接收完整时，对于图5所示的1DM功能OAM数据码块而言，连续合法的两个1DM码块正确接收即表示完整接收；
步骤1002，从用接收到的1DM功能OAM数据码块中的时间戳，作为 为远端设置发送时的时间戳Ttx，带外信息的中的时间戳为接收到第一个1DM OAM数据码块的时间戳Trx，根据规范定义，计算线路延时为Delay＝Trx–Ttx，并可以做表项记录，用于提供上层系统使用。
2DMM功能OAM数据码块用于检测双向发送于接收的延迟状况，通常在接收2DMM功能OAM数据码块后发送2DMR数据码块，如图5所示，2DMM功能OAM数据码块可以由6个数据码块最长，对解析后的CV功能的OAM数据码块的处理流程可以如图11所示：
步骤1101；在2DMM处理模块中，2DMM功能OAM数据码块接收和整合处理，以及获取时间戳的方法与1DM功能OAM数据码块的处理方法类似；
步骤1102，当多码块2DMM功能OAM数据码块接收完整时，需要做回复2DMR的处理，2DMR共包括6个连续的OAM数据码块。回复的2DMR中，Seq值为0和Seq值为1的两个数据码块中的时间戳内容从2DMM中复制；带外信息中的时间戳为接收2DMM的时间戳，将接收2DMM的时间戳编辑在回复Seq值为2和Seq值为3的两个2DMM功能OAM数据码块中；并将回复DMR时的时间戳编辑在Seq值为4和Seq值为5两个2DMM功能OAM数据码块中。2DMR发送至通信对端FlexE设备，进行DM的计算。
2DMR功能OAM数据码块用于检测双向发送于接收的延迟状况，通常对接收的通信对端发送的2DMR数据码块，进行时延测量，对解析后的2DMR功能OAM数据码块的处理流程可以如图12所示：
步骤1201：在2DMR处理模块中，首先对数据码块，进行多码块OAM数据码块进行接收、整合处理，存储等处理；
步骤1202：当多码块接收完整时，需要对2DMR中的时戳信息进行时延计算，如图5中2DMR格式所示，可以从2DMR的6个码块中取出对应 2DMM发送时戳(Tx_f_TS)，2DMM接收时戳(Rx_b_TS)，2DMR发送时戳(Tx_b_TS)，并将带外信息中时间戳表达为接收到2DMR OAM数据码块的时戳，即2DMR接收时戳)。双向延时计算表达式可以是：(2DMR接收时戳-2DMM发送时戳)-(2DMR发送时戳-2DMM接收时戳)，用于提供上层系统使用。
在一些实施例中，可以在FlexE层，向所示通信对端发送第二OAM数据码块；
这里，所述第二OAM数据码块可以是与第一OAM数据码块传输方向相反的数据码块，通过OAM处理引擎直接从FlexE层进行发送，可以提高OAM数据码块处理实时性，提升系统响应性能；第二OAM数据码块可以是接收到通信对端发送的OAM数据码块的回复数据码块，也可以是向通信对端主动发送的OAM数据码块。
在一些实施例中，可以将16K个数据码块时间脉冲作为发射时间单位，间隔预设个数的所述发射时间单位向通信对端发送所述第二OAM数据码块；
这里，如图13所示，可以以16K个数据码块时间脉冲作为一个时间单位，行时间计数，用于指示各个OAM数据码块的发送时间。各功能码块都有相应的发送计数配置，发送计数配置值以16K个码块的时间为单位，由此发送计数配置值可以配置不同的时间间隔。整个时间循环，按16K个码块的时间间隔脉冲读取所有Client的相关表项，每处理一次，表项中配置的发送计数则减1，当减到0时，表示该时刻需要发送该类OAM数据码块，则进行发送模块的处理，并将发生计数重置到配置的码块发送周期，用于下一个OAM数据码块的时间计数。
在一些实施例中；所述第二OAM数据码块为BAS功能时，在所述FlexE层向第二OAM数据码块中设置第二OAM数据码块对应的BIP的校验码； 所述第二OAM数据码块为1DM功能或2DMM功能时，将所述第二OAM数据码块在所述FlexE层的发送时间，在所述第二OAM数据块中设置为发送时间戳；
对于BAS，需在伴随发送码块同时发送至FlexE层的带外信息中增加需要添加BIP信息的控制Flag，由FlexE层将计算的BIP的校验码编辑入相应位置；对于DM相关的码块，需要在带外信息中放置添加时间戳的控制Flag，由FlexE层在发送码块时将取得的时间戳编辑入相应位置。
本申请实施例提供的运营维护管理信息处理装置，包括处理器、存储器及存储在存储器上并能够有所述处理器运行的可执行程序，所述处理器运行所述可执行程序时执行实现运营维护管理信息处理方法，如图1所示，所述方法包括：
步骤101：在FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；
如图2所示，FlexE是在MAC和PHY之间创造的一个中介层，FlexE提供了一种通用机制，基于时隙调度将一个物理以太网端口划分为多个以太网弹性硬管道，将多个客户(Client或FlexE Client)接口的数据按照时隙方式调度并分发至多个不同的子通道。并可实现业务隔离。现有技术采用的OAM管理都是通过Ether OAM等协议在MAC层以上如Switch Core实现的；
这里，可以设置一个处理引擎，在FlexE层进行OAM管理，对以64B/66B编码的FlexE层的数据码块进行处理；所述FlexE OAM处理引擎可以由ASIC等实现。所述FlexE层的数据码块通常由通信对端通过PHY传输到FlexE层。
所述预设第一确定规则可以根据OAM数据码块的格式设置，通过OAM数据码块特定位置的信息将在FlexE层传输的数据码块中的第一 OAM数据码块提取到处理引擎中进行处理；
在一些实施例中，可以自定义OAM数据码块的格式，如图3所示，OAM数据码块的格式可以使用和普通的数据码块相同的64B/66B格式进行传输，并使用控制码块中的0代码区分，0代码为第2至9位，可以用0x4B表示该数据码块为控制码块；C代码缺省为可配置，可以采用0xC；当0x4B的控制码块中的C代码为0xC，则确定所述数据码块为OAM数据码块；OAM数据码块可以使用控制块内的6个Data承载OAM消息，OAM数据码块具体字段格式可以如图4所示，其中，
0x4B为0代码，占据8bit，0x48表示该码块为控制码块；
Resv，占据2bit，预留字段，缺省采用0；
Type，占据6bit，标识不同操作维护管理的不同功能类型；
Value，占据32bit，特定类型的OAM消息的内容；
C码，占据4bit，缺省为0xC，支持设置，表示数据码块为FlexE OAM数据码块；
Seq，占据4bit，用于标识由多个数据码块构成的OAM数据码块中各数据码块的序号；
CRC4，占据4bit，对OAM码块，排除CRC4位，共60bit校验；CRC4的算法多项式可以为x^4+x+1。
在一些实施例中，所述第一OAM数据码块包括一个以上的数据码块；
第一OAM数据码块可以由1个或多个数据码块组成，可以预设OAM数据码块组成规则，设置在各数据码块中的数据内容。
在一些实施例中，所述OAM数据码块可以实现不同的管理功能，OAM数据码块的功能类型可以包括：BAS功能、APS功能、CV功能、1DM功能、2DMM功能、2DMR功能或CS功能等；
所述BAS功能可以包括：连通性检查功能、BIP功能、RDI功能、REI 功能、BER计算功能、CS_LF功能和/或CS_RF功能。
对应不同的OAM功能，OAM数据码块格式可以如图5所示。不同功能的OAM数据码块可以采用单码块形式即由一个数据码块构成，也可以采用多码块形式即由多个个数据码块构成，不同OAM数据码块的功能、识别信息和优先级等可以如表1所示；
在一些实施例中，可以获取所述第一OAM数据码块对应的带外信息；
所述带外信息可以使用与普通数据码块不同的通道独立传送，也可以是对数据码块进行统计的信息等。可以将与第一OAM数据码块相同传输时隙的带外信息确定为与所述第一OAM数据码块对应的带外信息；所述带外信息可以包括：Client ID，客户链路信号质量信息，BIP校验信息，接收数据码块时的时间戳等：Client ID可以根据时隙确定，BIP校验信息可以由本地技术得到，接收数据码块时的时间戳为FlexE层的接收时间戳。所述带外信息可以用于OAM数据码块的处理。
步骤102：根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。
这里所述第二确定规则可以根据第一OAM数据码块的字段格式确定，以图5的第一OAM数据码块为例，可以根据type字段确定第一OAM数据码块对应的OAM功能类型；
所述预设解析规则可以根据第一OAM数据码块各OAM功能类型对应的码块格式确定；以BAS码块的BIP功能为例，由图5的OAMOAM数据码块的码块格式可知，可以将第50位至第57位解析为BIP校验码；也可以将组成CV等功能的多个OAM数据码块中的数据进行解析。
将第一OAM数据码块根据OAM功能类型进行解析，可以根据各OAM 功能类型第一OAM数据码块的字段格式提取需要的解析数据，执行所述OAM功能。
在一些实施例中，可以采用所述解析数据和所述带外信息，执行所述OAM功能；
通常，一些功能类型的第一OAM数据码块，通常需要结合带外信息，才能执行对应的OAM功能，这里可以结合获取的带外信息进行处理。如BAS中的BIP功能，需要将第一OAM数据码块中的BIP校验码与带外信息中的BIP校验码进行对比等；
在一些实施例中，FlexE OAM处理引擎在接收数据码块进行处理的总体流程，如图6所示包括：
步骤601：接收数据码块和带外信息，提取OAM数据码块，带外信息可以包括Client ID，客户链路信号质量信息，BIP校验信息，接收码块时的时间戳等；
在一些实施例中，对于OAM数据码块可以执行步骤602，对于带外信息可以通过OAM处理引擎中的总线传输到FlexE OAM处理引擎的处理模块中，结合解析的OAM数据码块进行处理；
步骤602：根据OAM数据码块类型，解析出OAM数据码块的数据；
步骤603：根据OAM功能类型，处理解析出的OAM数据码块的数据和带外信息；
步骤604：如果OAM功能类型包含向通信对端发送信息，则回复对应信息。
在一些实施例中，采用所述第一OAM数据码块，或采用所述第一OAM数据码块和所述带外信息，执行所述OAM功能之前，所述方法还包括：对所述第一OAM数据码块进行合法性检查；所述合法性检查包括CRC值的计算和检查；
在一些实施例中，FlexE OAM处理引擎解析流程可以如图7所示，包括：
步骤701：该模块首先对接收到的OAM码块做合法性检查，包括CRC值的计算和检查；
步骤702～706：根据不同的OAM数据码块的功能类型，分别进行数据解析，将解析的内容放入处理引擎内部BUS中，用于各码块具体处理模块。这里，所述解析过程可以是从单码块OAM数据码块或多码块OAM数据码块中，将各功能类型所需的数据从OAM数据码块中提取的过程。步骤702至步骤706顺序可以不分先后。
对解析后的BAS功能OAM数据码块，可以依次对其包括的功能进行处理，处理流程可以如图8所示；这里，步骤801至步骤807可以按照图8所示的顺序执行，也可以通过自定义的顺序执行；
步骤801：RDI信息处理，用于根据OAM数据码块中RDI信息确定远端的故障状况；
步骤802：CS信息处理，根据OAM数据码块中CS_LF和/或CS_RF指示信息，确定链路失效状况；
步骤803：周期检查，根据OAM数据码块中的数据，确定周期状况；
步骤804：BIP信息处理，用于将BAS中的BIP校验码与带外信息中的BIP校验码进行比较，确定是否出现传输问题；
步骤805：BER误码率计算处理，用于计算网络传输的误码率；
步骤806：REI处理，用于指示远端网络连接的误码；
步骤807：可以根据链路失效状况触发APS，链路失效状况可以包括步骤805的误码率等，可以将误码率与用户设置的信号失效(SF)和信号劣化(SD)的误码率门限进行比较，超过相应门限值，则认为产生SF或SD，触发APS处理；当误码率低于SF或SD的误码率门限值，则清除SF或SD， 触发可配置的APS回切处理。
CV功能通常采用SAPI和DAPI和预设的对比值进行比较，不匹配时生成警告；这里，对解析后的CV功能OAM数据码块的处理流程可以如图9所示，包括：
步骤901：CV码块处理模块包括，Sequence Number检查；
这里，CV功能OAM数据码块可以由多个数据码块组成，如图5所示可以由8个数据码块组成，可以通过预设的序号检查CV功能OAM数据码块完整性；
步骤902：将CV功能OAM数据码块SAPI/DAPI的多数据码块整合处理，并存储SAPI/DAPI的多码块；
这里，可以依次读取多个数据码块中的数据，整合成完整的SAPI/DAPI数据，并进行存储；
步骤903：以及当多模块接收完整时，和本地配置的Client对应的SAPI/DAPI的比较处理，根据比较处理结果，判断是否出现不匹配错误，上报系统。
CS功能OAM数据码块用于比较客户信号的与预存信号进行比较；对解析后的CS功能的OAM数据码块的处理流程可以仅包含CS类型检查，从接收到的码块中的CS类型与本地配置的CS类型进行比较，判断是否出现不匹配错误，上报系统。这里，CS类型可以包括：未装载、以太网、SDH等。
1DM功能OAM数据码块用于检测发送于接收的延迟状况，对解析后的CV功能的OAM数据码块的处理流程可以如图10所示，包括：
步骤1001处理模块中，根据带外信息的Client ID来索引DM存储表项，进行序列号的检查，进行多码块整合处理逻辑，以及1DM的多码块时戳存储，以及当多码块接收完整时，对于图5所示的1DM功能OAM数据码块 而言，连续合法的两个1DM码块正确接收即表示完整接收；
步骤1002，从用接收到的1DM功能OAM数据码块中的时间戳，作为为远端设置发送时的时间戳Ttx，带外信息的中的时间戳为接收到第一个1DM OAM数据码块的时间戳Trx，根据规范定义，计算线路延时为Delay＝Trx–Ttx，并可以做表项记录，用于提供上层系统使用。
2DMM功能OAM数据码块用于检测双向发送于接收的延迟状况，通常在接收2DMM功能OAM数据码块后发送2DMR数据码块，如图5所示，2DMM功能OAM数据码块可以由6个数据码块最长，对解析后的CV功能的OAM数据码块的处理流程可以如图11所示：
步骤1101；在2DMM处理模块中，2DMM功能OAM数据码块接收和整合处理，以及获取时间戳的方法与1DM功能OAM数据码块的处理方法类似；
步骤1102，当多码块2DMM功能OAM数据码块接收完整时，需要做回复2DMR的处理，2DMR共包括6个连续的OAM数据码块。回复的2DMR中，Seq值为0和Seq值为1的两个数据码块中的时间戳内容从2DMM中复制；带外信息中的时间戳为接收2DMM的时间戳，将接收2DMM的时间戳编辑在回复Seq值为2和Seq值为3的两个2DMM功能OAM数据码块中；并将回复DMR时的时间戳编辑在Seq值为4和Seq值为5两个2DMM功能OAM数据码块中。2DMR发送至通信对端FlexE设备，进行DM的计算。
2DMR功能OAM数据码块用于检测双向发送于接收的延迟状况，通常对接收的通信对端发送的2DMR数据码块，进行时延测量，对解析后的2DMR功能OAM数据码块的处理流程可以如图12所示：
步骤1201：在2DMR处理模块中，首先对数据码块，进行多码块OAM数据码块进行接收、整合处理，存储等处理；
步骤1202：当多码块接收完整时，需要对2DMR中的时戳信息进行时延计算，如图5中2DMR格式所示，可以从2DMR的6个码块中取出对应2DMM发送时戳(Tx_f_TS)，2DMM接收时戳(Rx_b_TS)，2DMR发送时戳(Tx_b_TS)，并将带外信息中时间戳表达为接收到2DMR OAM数据码块的时戳，即2DMR接收时戳)。双向延时计算表达式可以是：(2DMR接收时戳-2DMM发送时戳)-(2DMR发送时戳-2DMM接收时戳)，用于提供上层系统使用。
在一些实施例中，可以在FlexE层，向所示通信对端发送第二OAM数据码块；
这里，所述第二OAM数据码块可以是与第一OAM数据码块传输方向相反的数据码块，通过OAM处理引擎直接从FlexE层进行发送，可以提高OAM数据码块处理实时性，提升系统响应性能；第二OAM数据码块可以是接收到通信对端发送的OAM数据码块的回复数据码块，也可以是向通信对端主动发送的OAM数据码块。
在一些实施例中，可以将16K个数据码块时间脉冲作为发射时间单位，间隔预设个数的所述发射时间单位向通信对端发送所述第二OAM数据码块；
这里，如图13所示，可以以16K个数据码块时间脉冲作为一个时间单位，行时间计数，用于指示各个OAM数据码块的发送时间。各功能码块都有相应的发送计数配置，发送计数配置值以16K个码块的时间为单位，由此发送计数配置值可以配置不同的时间间隔。整个时间循环，按16K个码块的时间间隔脉冲读取所有Client的相关表项，每处理一次，表项中配置的发送计数则减1，当减到0时，表示该时刻需要发送该类OAM数据码块，则进行发送模块的处理，并将发生计数重置到配置的码块发送周期，用于下一个OAM数据码块的时间计数。
在一些实施例中；所述第二OAM数据码块为BAS功能时，在所述FlexE层向第二OAM数据码块中设置第二OAM数据码块对应的BIP的校验码；所述第二OAM数据码块为1DM功能或2DMM功能时，将所述第二OAM数据码块在所述FlexE层的发送时间，在所述第二OAM数据块中设置为发送时间戳；
对于BAS，需在伴随发送码块同时发送至FlexE层的带外信息中增加需要添加BIP信息的控制Flag，由FlexE层将计算的BIP的校验码编辑入相应位置；对于DM相关的码块，需要在带外信息中放置添加时间戳的控制Flag，由FlexE层在发送码块时将取得的时间戳编辑入相应位置。
以上所述，仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围，凡在本申请的精神和原则之内所作的任何修改、等同替换和改进等，均应包含在本申请的保护范围之内。

Claims (16)

  1. 一种运营维护管理OAM信息处理方法，所述方法包括：
    在灵活以太网FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；
    根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；
    根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；
    采用所述解析数据，执行所述OAM功能。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    获取所述第一OAM数据码块对应的带外信息，采用所述解析数据和所述带外信息，执行所述OAM功能。
  3. 根据权利要求1所述的方法，其中，所述第一OAM数据码块对应的OAM功能，包括：
    基础BAS功能、自动保护倒换APS功能、连通性检测CV功能、单向时延检测1DM功能、双向时延检测信息2DMM功能、双向时延检测响应2DMR功能或客户信号CS功能；
    所述BAS功能包括：连通性检查功能、比特交错奇偶校验BIP校验功能、远端故障指示RDI功能、远端误码指示REI功能、客户链路近端失效CS_LF功能和/或客户链路远端失效CS_RF功能。
  4. 根据权利要求1所述的方法，其中，所述第一OAM数据码块包括一个以上的数据码块。
  5. 根据权利要求1至4任一项所述的方法，其中，所述方法还包括： 在FlexE层，向所述通信对端发送第二OAM数据码块。
  6. 根据权利要求5所述的方法，其中，所述向所述通信对端发送第二OAM数据码块，包括：将16K个数据码块时间脉冲作为发射时间单位，间隔预设个数的所述发射时间单位，向所述通信对端发送所述第二OAM数据码块。
  7. 根据权利要求6所述的方法，其中，所述方法还包括：
    所述第二OAM数据码块为BAS功能时，在所述FlexE层向第二OAM数据码块中设置第二OAM数据码块对应的BIP的校验码；
    所述第二OAM数据码块为1DM功能或2DMM功能时，将所述第二OAM数据码块在所述FlexE层的发送时间，在所述第二OAM数据块中设置为发送时间戳。
  8. 一种运营维护管理信息处理装置，所述装置包括：获取模块和处理模块；其中，
    所述获取模块，配置为在FlexE层获取通信对端发送的数据码块，根据预设第一确定规则，确定数据码块中的第一OAM数据码块；
    所述处理模块，配置为根据预设第二确定规则确定所述第一OAM数据码块对应的OAM功能；根据所述第一OAM数据码块对应的功能类型，采用预设解析规则，解析出所述第一OAM数据码块中的解析数据；采用所述解析数据，执行所述OAM功能。
  9. 根据权利要求8所述的装置，其中，
    所述获取模块，还配置为获取所述第一OAM数据码块对应的带外信息；
    所述处理模块，还配置为采用所述解析数据和所述带外信息，执行所述OAM功能。
  10. 根据权利要求8所述的装置，其中，所述第一OAM数据码块对应 的OAM功能，包括：
    基础BAS功能、自动保护倒换APS功能、连通性检测CV功能、单向时延检测1DM功能、双向时延检测信息2DMM功能、双向时延检测响应2DMR功能或客户信号CS功能；
    所述BAS功能包括：连通性检查功能、比特交错奇偶校验BIP校验功能、远端故障指示RDI功能、远端误码指示REI功能、客户链路近端失效CS_LF功能和/或客户链路远端失效CS_RF功能。
  11. 根据权利要求8所述的装置，其中，所述第一OAM数据码块包括一个以上的数据码块。
  12. 根据权利要求8至11任一项所述的装置，其中，所述装置还包括：发送模块，配置为在FlexE层，向所示通信对端发送第二OAM数据码块。
  13. 根据权利要求12所述的装置，其中，所述发送模块，配置为：将16K个数据码块时间脉冲作为发射时间单位，间隔预设个数的所述发射时间单位，向所述通信对端发送所述第二OAM数据码块。
  14. 根据权利要求13所述的装置，其中，所述发送模块，还配置为：
    所述第二OAM数据码块为BAS功能时，在所述FlexE层向第二OAM数据码块中设置第二OAM数据码块对应的BIP的校验码；
    所述第二OAM数据码块为1DM功能或2DMM功能时，将所述第二OAM数据码块在所述FlexE层的发送时间，在所述第二OAM数据块中设置为发送时间戳。
  15. 一种存储介质，其上存储由可执行程序，其中，所述可执行程序被处理器执行时实现如权利要求1至7任一项所述运营维护管理信息处理方法的步骤。
  16. 一种运营维护管理信息处理装置，包括处理器、存储器及存储在存储器上并能够有所述处理器运行的可执行程序，其中，所述处理器运行 所述可执行程序时执行如权利要求1至7任一项所述运营维护管理信息处理方法的步骤。
PCT/CN2019/088196 2018-12-26 2019-05-23 运营维护管理信息处理方法和装置 WO2020133897A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/434,054 US11924079B2 (en) 2018-12-26 2019-05-23 Operations, administration and management information processing method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811601987.7 2018-12-26
CN201811601987.7A CN109728948B (zh) 2018-12-26 2018-12-26 一种运营维护管理信息处理方法和装置

Publications (1)

Publication Number Publication Date
WO2020133897A1 true WO2020133897A1 (zh) 2020-07-02

Family

ID=66297182

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/088196 WO2020133897A1 (zh) 2018-12-26 2019-05-23 运营维护管理信息处理方法和装置

Country Status (3)

Country Link
US (1) US11924079B2 (zh)
CN (1) CN109728948B (zh)
WO (1) WO2020133897A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112134639A (zh) * 2020-09-17 2020-12-25 盛科网络（苏州）有限公司 Oam报文发送的方法、装置、计算机介质和电子设备

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109728948B (zh) * 2018-12-26 2022-05-13 苏州盛科通信股份有限公司 一种运营维护管理信息处理方法和装置
CN113132173A (zh) * 2019-12-31 2021-07-16 华为技术有限公司 时延确定方法及装置、网络传输系统
CN115314179B (zh) * 2022-08-05 2023-06-09 烽火通信科技股份有限公司 Mtnp oam消息发送方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106612220A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 灵活以太网的通道管理方法和装置
CN108123813A (zh) * 2016-11-28 2018-06-05 华为技术有限公司 操作、管理和维护oam数据的传输方法和装置
EP3393136A1 (en) * 2015-06-30 2018-10-24 Ciena Corporation Flexible ethernet node and method for oam
CN109728948A (zh) * 2018-12-26 2019-05-07 盛科网络（苏州）有限公司 一种运营维护管理信息处理方法和装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227450B (zh) * 2007-01-16 2013-04-24 华为技术有限公司 一种开销信息的传输方法、系统及设备
CN102957613B (zh) * 2011-08-29 2015-09-23 盛科网络（苏州）有限公司 Mpls-tp网络中oam报文和数据报文统一转发路径的方法及装置
US10218823B2 (en) * 2015-06-30 2019-02-26 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
CN109391461B (zh) * 2017-08-11 2021-08-13 华为技术有限公司 透传业务频率的方法和设备
CN112073245B (zh) * 2017-09-21 2023-05-09 中国移动通信有限公司研究院 Oam消息传输方法、传输设备及存储介质
CN107508732A (zh) * 2017-10-18 2017-12-22 盛科网络（苏州）有限公司 灵活对各类oam报文进行序列号检测和时间戳检测的方法
WO2019119389A1 (en) * 2017-12-22 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for configuring a flex ethernet node
CN109995604B (zh) * 2017-12-29 2023-05-16 华为技术有限公司 一种灵活以太网时延测量方法及相关设备
CN108521343B (zh) * 2018-03-26 2021-01-26 烽火通信科技股份有限公司 一种oam报文的处理方法及装置
US11522777B2 (en) * 2019-02-07 2022-12-06 Avago Technologies International Sales Pte. Limited Method and systems to monitor and isolate issues over layer1 paths using FlexE client OAM
US11916661B2 (en) * 2019-06-27 2024-02-27 Ciena Corporation Distributing timing over metro transport networking
CN113972997A (zh) * 2020-07-25 2022-01-25 华为技术有限公司 一种传输数据的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3393136A1 (en) * 2015-06-30 2018-10-24 Ciena Corporation Flexible ethernet node and method for oam
CN106612220A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 灵活以太网的通道管理方法和装置
CN108123813A (zh) * 2016-11-28 2018-06-05 华为技术有限公司 操作、管理和维护oam数据的传输方法和装置
CN109728948A (zh) * 2018-12-26 2019-05-07 盛科网络（苏州）有限公司 一种运营维护管理信息处理方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112134639A (zh) * 2020-09-17 2020-12-25 盛科网络（苏州）有限公司 Oam报文发送的方法、装置、计算机介质和电子设备
CN112134639B (zh) * 2020-09-17 2022-08-12 苏州盛科通信股份有限公司 Oam报文发送的方法、装置、计算机介质和电子设备

Also Published As

Publication number Publication date
US20220217067A1 (en) 2022-07-07
CN109728948B (zh) 2022-05-13
CN109728948A (zh) 2019-05-07
US11924079B2 (en) 2024-03-05

Similar Documents

Publication Publication Date Title
WO2020133897A1 (zh) 运营维护管理信息处理方法和装置
CN112134653B (zh) Oam消息传输方法、传输设备及存储介质
EP2063573A1 (en) Transmission method, system and apparatus of overhead information
JP6985492B2 (ja) 検出ブロック送信及び受信方法並びにネットワークデバイス及びシステム
EP3675398B1 (en) Check code processing method, electronic device, and storage medium
KR102382432B1 (ko) 비트 에러를 검출하기 위한 방법 및 장치
US8675501B2 (en) Transmission apparatus and reporting method for reporting fault
WO2020063593A1 (zh) 一种时延对称性测量方法、装置和系统
WO2021244660A1 (zh) 64b/66b码流发送方法、64b/66b码流接收方法及设备
WO2021254508A1 (zh) 一种确定码组丢失的方法及装置
WO2019015462A1 (zh) 一种检测块发送和接收的方法、网络设备和系统
WO2021017890A1 (zh) 一种通信方法和通信设备
CN113938246A (zh) 一种业务流误码指示方法和通信装置
CN110855580A (zh) 一种站内继电保护业务镜像处理方法及交换设备
JP5698107B2 (ja) ネットワーク評価方法、および、ネットワーク評価システム
KR101008780B1 (ko) Ｎｇ-ｓｄｈ 망과 이더넷 망간의 장애 검출 방법
JP2003348039A (ja) 冗長構成をとる通信システムおよび通信装置
CN116455842A (zh) 一种并行冗余以太网传输协议栈系统及实现方法
JP2017126936A (ja) 伝送品質評価装置、伝送品質評価方法、およびプログラム

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

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

Country of ref document: EP

Kind code of ref document: A1