An SDH data quality analysis method and system

Abstract

The present invention discloses an SDH data quality analysis method and system. The method includes performing data analysis on SDH data at the transport layer and the application layer respectively. The data analysis at the transport layer includes: extracting single-frame data from the SDH input data, extracting various overhead bytes related to verification, calculating and comparing the checksum of each frame. If the calculated checksum of the current frame data is consistent with the overhead checksum of the previous frame, the data is considered correct; if not, an error code is considered to occur. The data analysis at the application layer includes: S1: extracting single-frame and multiple-frame data from the SDH input data, parsing the overhead bytes to obtain the multiplexing structure, the carried service type, and the payload data; S2: performing quality checks on the payload data of C-4-Xc or C-4, C-3, C-2, C-12, C-11 and the time slot TS data according to the carried service type in S1. The technical solution of the present invention realizes a comprehensive analysis of SDH data at the transport layer and the application layer.

Description

Technical Field

[0001] The present invention relates to the technical field of data analysis, and particularly relates to a method and system for analyzing SDH data quality. Background Art

[0002] Most of the current SDH data quality analysis methods adopt a transmission layer overhead field calculation scheme, that is, a method of calculating through the original data and comparing with the overhead bytes. Its processing framework is as Figure 1 shown. Among them, the checksum of the previous frame is obtained by calculating the checksum SUM1 of the previous frame through the original data of the previous frame. The overhead field of the current frame is used to obtain the checksum SUM2 of the previous frame through overhead fields such as B1, B2, B3, and V5. The error code statistics is to compare SUM1 and SUM2 to obtain the error code situation. Generally, the analysis method only has transmission layer error code statistics and does not support application layer data error code statistics, and the actual available situation of the application layer cannot be known.

[0003] Therefore, there are defects in the prior art and improvement is needed. Summary of the Invention

[0004] The main object of the present invention is to propose a method and system for analyzing SDH data quality, aiming to comprehensively analyze SDH data at the transmission layer and the application layer.

[0005] To achieve the above object, a method for analyzing SDH data quality proposed by the present invention includes separately performing data analysis on the transmission layer and the application layer of SDH data;

[0006] The data analysis of the transmission layer includes: extracting single-frame data from the SDH input data, extracting various overhead bytes related to checksum and calculating and comparing the checksum of each frame. If the checksum calculated from the current frame data is consistent with the overhead checksum of the previous frame, the data is considered correct; if not, it is considered that an error code occurs once.

[0007] The data analysis of the application layer includes:

[0008] S1: Extracting single-frame and multiple-frame data from the SDH input data, parsing the overhead bytes to obtain the multiplexing structure, the carried service type, and the payload data;

[0009] S2: Performing quality inspection on the payload data of C-4-Xc or C-4, C-3, C-2, C-12, C-11 and the time slot TS data according to the carried service type in S1.

[0010] Preferably, the data analysis of the transmission layer specifically includes:

[0011] Step 1: Extract the B1 byte of the current frame's RSOH (Regenerator Section Overhead), and at the same time perform an XOR operation on all bytes of the scrambled STM-N frame of the previous frame to obtain the BIP-N*8 checksum B1' of the previous frame, and check whether B1 and B1' are consistent;

[0012] Step 2: Extract the B2B2B2 bytes of the current frame's MSOH (Multiplex Section Overhead), and at the same time perform an XOR operation on all bytes of the scrambled STM-N frame of the previous frame in groups of N*3 bytes to obtain the BIP-N*24 checksum B2'B2'B2' of the previous frame, and check whether B2B2B2 and B2'B2'B2' are consistent;

[0013] Step 3: Extract the B3 bytes of the current VC-4-Xc, VC-4, and VC3 frames, and at the same time perform an XOR operation on all bytes of the previous VC-4-Xc, VC-4, and VC3 to obtain the BIP-N*8 checksum B3' of the previous frame, and check whether B3 and B3' are consistent;

[0014] Step 4: For VC-2, VC-12, and VC-11, the BIP-2 checksum is stored in V5. Extract the V5 bytes of the current frame, including b1b2, and at the same time perform an XOR operation on the 1st, 3rd, 5th, and 7th bits of all bytes of the previous frame to obtain b1', and perform an XOR operation on the 2nd, 4th, 6th, and 8th bits to obtain b2', and check whether b1b2 and b1'b2' are consistent.

[0015] Preferably, S1 in the application layer data analysis specifically includes:

[0016] Obtain the grouping information and the number of cascades of VC-4-Xc based on the H1 and H2 information of the AU-4 pointer. The value range of the number of cascades X for each group is 4, 16, 64;

[0017] Obtain the payload type of each VC-4-Xc or VC-4 based on the signal label byte C2 of the high-order path overhead HPOH, including TUG, HDLC, GFP, EOS, ATM, and extract the C-4-Xc or C-4 payload data; for the GFP payload type of VC-4, it is also necessary to judge whether it belongs to the virtual concatenation type according to the TU position indication byte H4 of the HPOH.

[0018] Preferably, for the payload type with C2 being HDLC, judge its scrambling mode and CRC method according to the C-4-Xc or C-4 payload data;

[0019] For the payload type with C2 being TUG, comprehensively judge whether it is a TUG3 or DS3 structure according to the H4 byte of the HPOH and the H1 byte of the TU-3 pointer;

[0020] For the DS3 structure, determine whether it belongs to the GFP or ATM or HDLC payload type according to the C2 byte, determine whether it belongs to the virtual concatenation type according to the H4 byte, and extract the C-3 payload data;

[0021] For the TUG3 and DS3 structures, determine whether the underlying structure is TU2 or TU12 or TU11 according to the SS bit of V1;

[0022] For the TU2 structure, determine whether it belongs to the HDLC payload type according to the C-2 payload data;

[0023] For the TU12 structure, determine whether it belongs to the GFP or ATM or HDLC payload type and whether it belongs to the virtual concatenation type according to K4; extract the C-12 payload data and determine whether it belongs to the E1 type; extract the C-11 payload data and determine whether it belongs to the T1 type;

[0024] For the E1 type and T1 type, extract the time slot data and comprehensively determine whether it belongs to the ATM or HDLC payload type through the same start and end rule, the maximum similarity principle, and the protocol distribution characteristics.

[0025] Preferably, S2 in the application layer data analysis specifically includes:

[0026] For POS or EOS or GFP or HDLC data, count the total number of packets, overlong packets, ultra-short packets, packet length distribution, packet flow, and count the number of correct and incorrect CRCs through CRC16 or 32 verification;

[0027] For ATM data, count the total number of cells and the number of correct and incorrect times of CRC16 verification of the cell header; after the payload is descrambled by X43+1, for the HDLC-type bearer data, count the total number of packets, overlong packets, ultra-short packets, packet length distribution, packet flow, and count the number of correct and incorrect CRCs through CRC16 or 32 verification;

[0028] For E1 or T1 data, count the number of correct and incorrect synchronization times.

[0029] Preferably, it further includes an SDH data quality analysis system, which includes an overhead processing unit for performing transmission layer data analysis on SDH data, a payload extraction unit and an application processing unit for performing application layer data analysis on SDH data;

[0030] The overhead processing unit is used to extract single-frame data from the SDH input data, extract various overhead bytes related to verification and calculate and compare the checksum of each frame. If the calculated checksum of the current frame data is consistent with the overhead checksum of the previous frame, the data is considered correct; if not, it is considered that an error code has occurred once;

[0031] The load extraction unit is used to extract single-frame and multiplexed-frame data from the SDH input data, parse the overhead bytes, obtain the multiplexing structure, the carried service type, and the payload data, and send them to the application processing unit;

[0032] The application processing unit is used to perform quality checks on the payload data of C-4-Xc or C-4, C-3, C-2, C-12, C-11 and the time slot TS data according to the received carried service type.

[0033] Compared with the prior art, the beneficial effects of the present invention are as follows: it improves the existing method for analyzing SDH data quality. Following the ITU-T G.707 recommendation, based on the comparison of traditional overhead fields, the error code statistics of some main application layer data are added, and then in-depth processing of E1 and T1 is carried out according to the ITU-T G.703 / 704 recommendations, enabling users to understand the actual availability of application layer data, thereby obtaining a more comprehensive SDH data quality analysis report. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on the structures shown in these drawings without creative efforts.

[0035] Figure 1 It is a block diagram for analyzing and processing traditional SDH data quality;

[0036] Figure 2 It is a block diagram of the principle of the present invention;

[0037] Figure 3 It is a block diagram of the overhead processing unit structure of the present invention;

[0038] Figure 4 It is a block diagram of the load extraction unit structure of the present invention;

[0039] Figure 5 It is a block diagram of the application processing unit structure of the present invention;

[0040] The realization, functional features, and advantages of the object of the present invention will be further described with reference to the embodiments and the drawings. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0041] A method for analyzing SDH data quality proposed in this embodiment includes separately performing data analysis on the transport layer and the application layer of the SDH data;

[0042] Data analysis of the transport layer includes: extracting single-frame data from the SDH input data, extracting various overhead bytes related to verification, calculating and comparing the checksum of each frame. If the calculated checksum of the current frame data is the same as the overhead checksum of the previous frame, the data is considered correct; if not, an error code is considered to have occurred.

[0043] Data analysis of the application layer includes:

[0044] S1: Extract single-frame and multiple-frame data from the SDH input data, parse the overhead bytes to obtain the multiplexing structure, the type of carried service, and the payload data.

[0045] S2: Perform quality checks on the payload data of C-4-Xc or C-4, C-3, C-2, C-12, C-11 and the time slot TS data according to the type of carried service in S1.

[0046] It should be noted that the above SDH data sources include real-time acquisition cards, network interfaces, or non-real-time file interfaces.

[0047] Furthermore, the data analysis of the transport layer specifically includes:

[0048] Step 1: Extract the B1 byte of the RSOH regenerator section overhead of the current frame, and at the same time perform an XOR operation on all bytes of the scrambled STM-N frame of the previous frame to obtain the BIP-N*8 checksum of the previous frame as B1'. Check whether B1 and B1' are the same; among them, the first 9*N bytes of the regenerator section overhead are not included in the checksum operation range.

[0049] Step 2: Extract the B2B2B2 bytes of the MSOH multiplex section overhead of the current frame, and at the same time perform an XOR operation on all bytes of the scrambled STM-N frame of the previous frame in groups of N*3 bytes to obtain the BIP-N*24 checksum of the previous frame as B2'B2'B2'. Check whether B2B2B2 and B2'B2'B2' are the same; among them, the first 1-3 rows of 3*9*N bytes of the regenerator section overhead are not included in the checksum operation range.

[0050] Step 3: Extract the B3 bytes of the current VC-4-Xc, VC-4, and VC3 frames, and at the same time perform an XOR operation on all bytes of the previous VC-4-Xc, VC-4, and VC3 to obtain the BIP-N*8 checksum of the previous frame as B3'. Check whether B3 and B3' are the same;

[0051] Step 4: VC-2, VC-12, and VC-11 all use V5 to store the BIP-2 checksum. Extract the V5 bytes of the current frame, including b1b2. At the same time, perform an XOR operation on the 1st, 3rd, 5th, and 7th bits of all bytes of the previous frame to obtain b1′, and perform an XOR operation on the 2nd, 4th, 6th, and 8th bits to obtain b2′. Check whether b1b2 is consistent with b1′b2′. Among them, the V1, V2, V3, and V4 bytes are not included in the checksum operation range, and the operation range is adjusted according to the ITU-T G.707 recommendation specification.

[0052] Further, S1 in the application layer data analysis specifically includes:

[0053] Obtain the grouping information and concatenation number of VC-4-Xc based on the H1 and H2 information of the AU-4 pointer. The concatenation number X of each group ranges from 4, 16, to 64;

[0054] Obtain the payload type of each VC-4-Xc or VC-4 based on the signal label byte C2 of the high-order path overhead HPOH, including TUG, HDLC, GFP, EOS, ATM, and extract the C-4-Xc or C-4 payload data; for the GFP payload type of VC-4, it is also necessary to determine whether it belongs to the virtual concatenation type according to the TU position indication byte H4 of the HPOH.

[0055] Further, for the payload type with C2 being HDLC, determine its scrambling mode and CRC method based on the C-4-Xc or C-4 payload data;

[0056] For the payload type with C2 being TUG, comprehensively determine whether it is a TUG3 or DS3 structure based on the H4 byte of the HPOH and the H1 byte of the TU-3 pointer;

[0057] For the DS3 structure, determine whether it belongs to the GFP or ATM or HDLC payload type according to the C2 byte, determine whether it belongs to the virtual concatenation type according to the H4 byte, and extract the C-3 payload data;

[0058] For the TUG3 and DS3 structures, determine whether the structure below is TU2 or TU12 or TU11 based on the SS bit of V1;

[0059] For the TU2 structure, determine whether it belongs to the HDLC payload type according to the C-2 payload data;

[0060] For the TU12 structure, determine whether it belongs to the GFP or ATM or HDLC payload type and whether it belongs to the virtual concatenation type according to K4; extract the C-12 payload data and determine whether it belongs to the E1 type; extract the C-11 payload data and determine whether it belongs to the T1 type;

[0061] For E1 type and T1 type, extract time slot data, and comprehensively judge whether it belongs to ATM or HDLC payload type through the same start and end rule, the principle of maximum similarity, and protocol distribution characteristics.

[0062] Furthermore, S2 in the application layer data analysis specifically includes:

[0063] For POS or EOS or GFP or HDLC data, count the total number of packets, overlong packets, ultra-short packets, packet length distribution, packet flow, and count the number of correct and incorrect CRCs through CRC16 or 32 checksum;

[0064] For ATM data, count the total number of cells and the number of correct and incorrect times of CRC16 checksum in the cell header; after the payload is descrambled by X43+1, for the HDLC-type bearer data, count the total number of packets, overlong packets, ultra-short packets, packet length distribution, packet flow, and count the number of correct and incorrect CRCs through CRC16 or 32 checksum;

[0065] For E1 or T1 data, count the number of correct and incorrect synchronization times.

[0066] Furthermore, it also includes an SDH data quality analysis system, which includes an overhead processing unit for performing transmission layer data analysis on SDH data, a payload extraction unit and an application processing unit for performing application layer data analysis on SDH data;

[0067] The overhead processing unit is used to extract single-frame data from the SDH input data, extract various overhead bytes related to checksum and calculate and compare the checksum of each frame. If the calculated checksum of the current frame data is the same as the overhead checksum of the previous frame, the data is considered correct; if not, it is considered that an error code occurs.

[0068] The payload extraction unit is used to extract single-frame and multi-frame data from the SDH input data, parse the overhead bytes, obtain the multiplexing structure, bearer service type and payload data, and send them to the application processing unit; it should be noted that the payload extraction unit adopts a multi-threaded structure and can extract the bearer service data of multiple branches at the same time.

[0069] The application processing unit is used to perform quality inspection on the payload data of C-4-Xc or C-4, C-3, C-2, C-12, C-11 and the time slot TS data according to the received bearer service type.

[0070] The above are only the preferred embodiments of the present invention, and do not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present invention, or directly or indirectly applied in other related technical fields, shall be included in the patent protection scope of the present invention by the same token.

Claims

1. A method for analyzing SDH data quality, characterized in that, Including data analysis of the transport layer and application layer for SDH data respectively; The data analysis of the transport layer includes: extracting single-frame data from the SDH input data, extracting various overhead bytes related to verification and calculating and comparing the checksum of each frame. If the calculated checksum of the current frame data is consistent with the overhead checksum of the previous frame, the data is considered correct; if not, it is considered that an error code occurs once; The data analysis of the application layer includes: S1: Extract single-frame and multiple-frame data from the SDH input data, parse the overhead bytes to obtain the multiplexing structure, the type of carried service, and the payload data; S2: Perform quality inspection on the payload data of C-4-Xc or C-4, C-3, C-2, C-12, C-11 and the time slot TS data according to the type of carried service in S1. Among them, the quality inspection includes counting the bit error rate of the application layer data; S1 in the data analysis of the application layer specifically includes: Obtaining the packet information and the number of cascades of VC-4-Xc according to the H1 and H2 information of the AU-4 pointer. The value range of the number of cascades X of each packet is 4, 16, 64; Obtaining the payload type of each VC-4-Xc or VC-4 according to the signal label byte C2 of the high-order path overhead HPOH, including TUG, HDLC, GFP, EOS, ATM, and extracting the C-4-Xc or C-4 payload data; for the GFP payload type of VC-4, it is also necessary to judge whether it belongs to the virtual cascade type according to the TU position indication byte H4 of the HPOH; Based on the C2 byte and H4 byte of the HPOH, the K4 byte of the TU12 structure, the H1 byte of the AU-4 pointer, and the V1 byte of the TUG3 and DS3 structures, judge the payload types of HDLC, GFP, and ATM finally carried by the TUG unit.

2. The SDH data quality analysis method according to claim 1, wherein The data analysis of the transport layer specifically includes: Step 1: Extract the B1 byte of the current frame's RSOH (Regenerator Section Overhead), and at the same time perform an XOR operation on all bytes of the scrambled STM-N frame of the previous frame to obtain the BIP-N*8 checksum of the previous frame as B1 ‘ , check B1 and B1 ’ to see if they are consistent; Step 2: Extract the B2B2B2 bytes of the MSOH multiplex section overhead of the current frame. At the same time, perform an XOR operation on all bytes of the scrambled STM-N frame of the previous frame in groups of N * 3 bytes to obtain the BIP-N * 24 checksum of the previous frame as B2 ‘ B2 ‘ B2 ’ , check whether B2B2B2 is consistent with B2 ‘ B2 ‘ B2 ’ ; Step 3: Extract the B3 bytes of the current VC-4-Xc, VC-4, and VC3 frames, and at the same time perform an XOR operation on all the bytes of the previous VC-4-Xc, VC-4, and VC3 frames to obtain the BIP-N*8 checksum of the previous frame as B3 ‘ , check B3 and B3 ‘ to see if they are consistent; Step 4: VC-2, VC-12, and VC-11 all use V5 to store the BIP-2 checksum. Extract the V5 bytes of the current frame, including b1b2. At the same time, perform an XOR operation on the 1st, 3rd, 5th, and 7th bits of all bytes of the previous frame to obtain b1 ‘ , and perform an XOR operation on the 2nd, 4th, 6th, and 8th bits to obtain b2 ’ , and check whether b1b2 is consistent with or not.

3. The SDH data quality analysis method according to claim 1, wherein, For the payload type with C2 being HDLC, judge its scrambling mode and CRC method according to the C-4-Xc or C-4 payload data; For the payload type with C2 being TUG, comprehensively judge whether it is a TUG3 or DS3 structure according to the H4 byte of the HPOH and the H1 byte of the TU-3 pointer; For the DS3 structure, judge whether it belongs to the GFP or ATM or HDLC payload type according to the C2 byte, judge whether it belongs to the virtual cascade type according to the H4 byte, and extract the C-3 payload data; For the TUG3 and DS3 structures, judge whether the structure below is TU2 or TU12 or TU11 according to the SS bit of V1; For the TU2 structure, judge whether it belongs to the HDLC payload type according to the C-2 payload data; For the TU12 structure, judge whether it belongs to the GFP or ATM or HDLC payload type, and whether it belongs to the virtual cascade type according to K4; Extract the C-12 payload data and judge whether it belongs to the E1 type; extract the C-11 payload data and judge whether it belongs to the T1 type; For the E1 type and T1 type, extract the time slot data and comprehensively judge whether it belongs to the ATM or HDLC payload type through the same start and end rule, the maximum similarity principle, and the protocol distribution characteristics.

4. The SDH data quality analysis method according to claim 1, characterized in that, S2 in the application layer data analysis specifically includes: For POS or EOS or GFP or HDLC data, count the total number of packets, overlong packets, undershort packets, packet length distribution, packet traffic, and count the number of correct and incorrect CRCs through CRC16 or 32 checksum; For ATM data, count the total number of cells, the number of correct and incorrect times of CRC16 checksum in the cell header; after the payload is descrambled by X43+1, for the HDLC-type bearer data, count the total number of packets, overlong packets, undershort packets, packet length distribution, packet traffic, and count the number of correct and incorrect CRCs through CRC16 or 32 checksum; For E1 or T1 data, count the number of correct and incorrect synchronization times.

5. The SDH data quality analysis method according to any one of claims 1 to 4, characterized in that, It also includes an SDH data quality analysis system, which includes an overhead processing unit for performing transport layer data analysis on SDH data, a payload extraction unit and an application processing unit for performing application layer data analysis on SDH data; The overhead processing unit is used to extract single-frame data from the SDH input data, extract various overhead bytes related to checksum and calculate and compare the checksum of each frame. If the calculated checksum of the current frame data is consistent with the overhead checksum of the previous frame, the data is considered correct; if not, it is considered that there is one error code; The payload extraction unit is used to extract single-frame and multiple-frame data from the SDH input data, parse the overhead bytes, obtain the multiplexing structure, bearer service type and payload data, and send them to the application processing unit; The application processing unit is used to perform quality inspection on the payload data of C-4-Xc or C-4, C-3, C-2, C-12, C-11 and the time slot TS data according to the received bearer service type. Among them, the quality inspection includes counting the bit error rate of the application layer data.

Images