Data processing method, network-side device and storage medium

By identifying and processing error blocks in the PCS data format on the receiving end, the adverse effects caused by error blocks in the receiving end data sequence are solved, ensuring the correctness and reliability of the data sequence.

WO2024239742A1PCT designated stage expired Publication Date: 2024-11-28ZTE CORP
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/078859
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-25
Filing Date
2024-02-27
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

When the receiving end receives a data sequence encapsulated in the PCS data format, when an error block occurs, the prior art cannot effectively process it, resulting in adverse effects on the use of the data sequence.

Method used

By receiving the data sequence, the error block in the first flag block, data block or second flag block is determined, and the data sequence is processed according to the type of the block, including restoring or replacing the inner layer block or small particle layer service, and extracting or discarding overhead , perform cyclic redundancy checks to determine the type and location of the error block.

Benefits of technology

Effectively handle error blocks to avoid their adverse effects on the data sequence and ensure the correctness and reliability of the data sequence.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024078859_28112024_PF_FP_ABST
    Figure CN2024078859_28112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application belongs to the technical field of communications. Disclosed are a data processing method, a network-side device and a storage medium. The method comprises: receiving a data sequence (102), wherein the data sequence comprises a plurality of types of blocks, and block types comprise a first flag block, a data block and a second flag block; determining a block having an error from among the first flag block, the data block and the second flag block (104); and processing the data sequence according to a block type corresponding to the block having an error (106).
Need to check novelty before this filing date? Find Prior Art

Description

Data processing method, network side device and storage medium

[0001] Cross-references

[0002] This invention claims priority to a Chinese patent application filed with the Patent Office of China on May 25, 2023, with application number 202310611791.0 and invention name “Data processing method, network side device and storage medium”. The entire contents of this application are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a data processing method, network-side equipment, and storage medium. Background Art

[0004] Providing low-latency, hard-isolated bearer technology for low-rate, fine-grained services is a current service requirement. One current bearer solution for low-rate or fine-grained services uses the physical coding sublayer (PCS) data format defined by IEEE802.3 as the encapsulation format for low-rate, fine-grained services. The PCS data format consists of a start block (S block), L data blocks (D blocks), and a end block (T block). Each 64-bit / 66-bit (64B / 66B) block includes a 2-bit synchronization header and a 64-bit payload. When the 2-bit synchronization header is 0b01, it indicates that the 64B / 66B block is a data block. When the 2-bit synchronization header is 0b10, it indicates that the 64B / 66B block is a control block, such as an S block or a T block.

[0005] In some scenarios, the data format of some business data is also the PCS data format (inner layer), that is, the data format of the business data is also composed of an S block, a D block, and a T block. When encapsulating the business data, the business data of this data format is encapsulated in the PCS format and then encapsulated into the channel layer (outer layer). Among them, due to abnormal conditions such as bit errors in the underlying layer, at least one of the S block, D block, and T block in the outer layer may have an error and become an error block, and the data in the corresponding S block, D block, and T block in the inner layer will also be affected. However, when the receiving end receives a data sequence encapsulated in the PCS data format, it will use the data normally regardless of whether there is an error block in the data sequence, which causes adverse effects. Therefore, how to deal with the error block in the data sequence encapsulated in the PCS data format received by the receiving end is a technical problem that needs to be solved by those skilled in the art.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a data processing method, a network-side device, and a storage medium, which can solve the problem of how to handle error blocks in a data sequence encapsulated in a PCS data format received at a receiving end.

[0008] In a first aspect, an embodiment of the present application provides a method for processing data, the method comprising: receiving a data sequence, the data sequence comprising multiple types of blocks, the types of the blocks comprising a first flag block, a data block, and a second flag block; determining an erroneous block from the first flag block, the data block, or the second flag block; and processing the data sequence according to the type of block corresponding to the erroneous block.

[0009] Optionally, determining the block with errors from the first flag block, the data block or the second flag block includes: determining the block with synchronization header errors from the first flag block, the data block or the second flag block as the block with errors; or determining the block with type domain errors from the first flag block or the second flag block as the block with errors.

[0010] Optionally, before processing the data sequence according to the type of the block corresponding to the erroneous block, the method further includes: determining the type of the block according to an expected position of a 64-bit / 66-bit block.

[0011] Optionally, determining the type of the block according to the expected position of the 64-bit / 66-bit block includes: determining the type of the previous 64-bit / 66-bit block or the type of the next 64-bit / 66-bit block according to the type of the current 64-bit / 66-bit block, or determining the type of the 64-bit / 66-bit block according to whether the 64-bit / 66-bit block contains overhead, or determining the type of the 64-bit / 66-bit block according to the data sequence structure, or determining the type of the 64-bit / 66-bit block according to the data sequence length.

[0012] Optionally, the type of the block further includes an error block, and the method further includes: determining the error block as a block with an error.

[0013] Optionally, the data sequence is processed according to the type of block corresponding to the erroneous block, including: if the block received at the expected position is the second marker block in the data sequence, but what is actually received is the erroneous block in the data sequence, then when the second marker block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the erroneous block; if the block received at the expected position is the data block in the data sequence, but what is actually received is the erroneous block, then when the data block is restored to the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the erroneous block.

[0014] Optionally, the data sequence is processed according to the type of block corresponding to the erroneous block, including: if the block received at the expected position is the first marker block in the data sequence, but the block actually received is an erroneous block, then the data sequence is discarded or other blocks of the data sequence are continued to be processed or the first marker block is used to restore the content of the inner block or small particle layer service, and the corresponding inner block or small particle layer service is replaced with the erroneous block.

[0015] Optionally, the first marker block contains overhead, and the processing of the data sequence according to the type of block corresponding to the erroneous block includes: when the type of block corresponding to the erroneous block is the first marker block, extracting the overhead from the first marker block; if the cyclic redundancy check in the overhead is correct, extracting the overhead or payload in the first marker block for processing; if the cyclic redundancy check in the overhead is wrong, discarding the data sequence or replacing the first marker block with an erroneous block, or discarding the overhead and continuing to process the payload.

[0016] Optionally, the data sequence is processed according to the type of block corresponding to the block with error, including: when the type of block corresponding to the block with error is the first flag block, extracting the data content of the first flag block for processing; or replacing the block with an error block; when the first flag block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the error block.

[0017] Optionally, the data sequence is processed according to the type of block corresponding to the block with error, including: when the type of block corresponding to the block with error is the second marker block, extracting the data content of the second marker block for processing; or replacing the block with the error block; when the second marker block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the error block.

[0018] Optionally, the second flag block contains overhead, and the processing of the data sequence according to the type of the block corresponding to the erroneous block includes:

[0019] In a case where the type of block corresponding to the erroneous block is the second marker block, overhead is extracted from the second marker block; if the cyclic redundancy check in the overhead is correct, the overhead or payload in the second marker block is extracted for processing; if the cyclic redundancy check in the overhead is wrong, the data sequence is discarded or the second marker block is replaced by the erroneous block, or the overhead is discarded and the payload continues to be processed.

[0020] Optionally, the data sequence is processed according to the type of block corresponding to the block with error, including: when the type of block corresponding to the block with error is a data block and the data block is the first data block in the data sequence, extracting the overhead from the first data block, and if the cyclic redundancy check in the overhead is correct, extracting the overhead or payload in the first data block for processing; if the cyclic redundancy check in the overhead is wrong, replacing the data block with an error block, or discarding the overhead and continuing to process the payload; when there are errors in other data blocks in the data sequence except the first data block, extracting the data content of the data block for processing, or replacing the data block with an error block or when the data block restores the inner block or small particle layer service, the corresponding inner block or the small particle layer service is replaced with an error block.

[0021] Optionally, the data format of the business data corresponding to the data sequence is a physical coding sublayer data format, the business data includes multiple data blocks, the first flag block and the second flag block of the data sequence contain at least one data block of the business data, and after determining the erroneous block from the first flag block, the data block and the second flag block, the method further includes: marking the data content in the data block corresponding to the business data corresponding to the erroneous block as erroneous.

[0022] Optionally, after processing the data sequence according to the type of block corresponding to the block with error, it also includes: when the first flag block, the data block or the second flag block restores the inner block or the small particle layer service, if the corresponding inner block or the small particle layer service has a type domain error or a synchronization header error, the corresponding inner block or the small particle layer service is replaced with an error block.

[0023] Optionally, the first marker block is a start block, and the second marker block is an end block.

[0024] In second aspect, an embodiment of the present application provides a data processing device, which includes: a receiving module for receiving a data sequence, the data sequence including multiple types of blocks, the types of the blocks including a first flag block, a data block, and a second flag block; an execution module for determining an erroneous block from the first flag block, the data block, or the second flag block; and a processing module for processing the data sequence according to the type of block corresponding to the erroneous block.

[0025] In a third aspect, an embodiment of the present application provides a network side device, which includes a processor, a memory, and a program or instruction stored on the memory and runnable on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0026] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0027] In an embodiment of the present application, a data sequence is received, the data sequence includes multiple types of blocks, and the types of the blocks include a first flag block, a data block, and a second flag block; a block with an error is determined from the first flag block, the data block, or the second flag block; and the data sequence is processed according to the type of block corresponding to the block with the error. It is possible to determine the block with an error from the data sequence and process the error in the data sequence according to the type of the error block, thereby avoiding the error in the data sequence from having an adverse effect on the data sequence. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1 is a flow chart of a data processing method provided in an embodiment of the present application;

[0029] FIG2 is a schematic diagram of a low-rate or fine-grained service encapsulation format provided in an embodiment of the present application;

[0030] FIG3 is a schematic diagram of a service package provided in an embodiment of the present application;

[0031] FIG4 is a schematic diagram of a 64B / 66B block format provided in an embodiment of the present application;

[0032] FIG5 is a schematic diagram of a control block format provided in an embodiment of the present application;

[0033] FIG6 is a schematic diagram of an error block format provided in an embodiment of the present application;

[0034] FIG7 is a schematic diagram of a service package provided in an embodiment of the present application;

[0035] FIG8 is a schematic diagram of the structure of a data sequence provided in an embodiment of the present application;

[0036] FIG9 is a schematic diagram of the structure of another data sequence provided in an embodiment of the present application;

[0037] FIG10 is a schematic diagram of the structure of another data sequence provided in an embodiment of the present application;

[0038] FIG11 is a schematic structural diagram of a data processing device provided in an embodiment of the present application;

[0039] FIG12 is a schematic structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0041] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that the objects distinguished by "first," "second," and the like are generally of the same type, and do not limit the number of objects; for example, the first object can be one or more. In addition, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects connected are in an "or" relationship.

[0042] The data processing method, network-side device, and storage medium provided in the embodiments of the present application are described in detail below with reference to specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0043] FIG1 illustrates a data processing method provided by an embodiment of the present invention. The method may be executed by a network-side device, which may include a server and / or a terminal device. In other words, the method may be executed by software or hardware installed on the network-side device. The method includes the following steps:

[0044] Step 102: Receive a data sequence, where the data sequence includes multiple types of blocks.

[0045] Specifically, a network-side device serving as a receiving end may receive a data sequence encapsulating service data of a customer service, wherein the data sequence includes multiple types of blocks, including a first flag block, a data block (D block), and a second flag block.

[0046] In one implementation, the first marker block is a start block, and the second marker block is an end block.

[0047] In an embodiment of the present application, the first marker block may be a start block (S block), and the second marker block may be an end block (T block). As shown in FIG2 , a first marker block (S block), L data blocks (D blocks), and a second marker block (T block) together constitute a complete data sequence, i.e., a 64-bit / 66-bit (64B / 66B) block with a fixed length of L+2. Wherein, L is an integer greater than or equal to 1, the first marker block (start block) marks the beginning of the data sequence, and the second marker block (end block) marks the end of the data sequence. In addition, providing a low-latency, hard-isolated bearer technology for low-rate, small-granularity layer services (Ethernet client services) is a current business requirement. As shown in FIG3 , after adding overhead, OAM messages and other information to the small-granularity layer service, an inner block is obtained. The small-granularity layer service may also be composed of an S block, L D blocks, and a T block. As shown in FIG3 , the inner block includes the small-granularity layer service and the OAM block, and the inner block may be encapsulated into the payload of the data sequence.

[0048] Step 104: Determine a block with an error from the first marker block, the data block, or the second marker block.

[0049] Specifically, when an abnormal situation occurs in the network, an erroneous block may appear in the data sequence, such as a bit error in the block, an error block, etc. In the embodiment of the present application, it is necessary to determine the erroneous block from the first marker block, the data block, and the second marker block in the data sequence.

[0050] Step 106: Process the data sequence according to the type of block corresponding to the block with error.

[0051] Specifically, after determining the block with errors from the data sequence, it is necessary to determine the type of block corresponding to the block with errors, that is, to determine whether the erroneous block is a first flag block, a second flag or a data block, and perform corresponding processing on the data sequence according to the type of block corresponding to the block with errors.

[0052] The data processing method provided by an embodiment of the present invention receives a data sequence, where the data sequence includes multiple types of blocks, determines a block with errors from a first marker block, a data block, or a second marker block, and processes the data sequence according to the type of block corresponding to the block with errors. This method can process errors in the data sequence and prevent the errors in the data sequence from having an adverse effect on the use of the data sequence.

[0053] In one implementation, determining the block with errors from the first marker block, the data block, or the second marker block includes:

[0054] Determine from the first flag block, the data block or the second flag block a block with a synchronization header error as the block with error; or determine from the first flag block or the second flag block a block with a type field error as the block with error.

[0055] As shown in Figure 4, the 64B / 66B block format has a 2-bit sync header and a 64-bit payload. A 2-bit sync header of 0b01 indicates that the 64B / 66B block is a data block. A 2-bit sync header of 0b10 indicates that the 64B / 66B block is a control block. Control blocks can include S blocks, T blocks, O blocks, and so on. Control blocks, as shown in Figure 5, can be distinguished by the different values ​​in the block type field (1 byte), for example, 0x78 indicates an S block, 0x87 indicates a T0 block, 0xFF indicates a T7 block, and 0x4B indicates an O block.

[0056] In an embodiment of the present application, a block with a synchronization header error can be determined from the first flag block, the data block or the second flag block as the above-mentioned block with errors, or a block with a type domain error can be determined from the first flag block or the second flag block as the above-mentioned block with errors.

[0057] In this way, by judging whether the synchronization header of the block is wrong, the block with errors can be determined from the first flag block, the data block or the second flag block. By judging whether the type field of the block is wrong, the block with errors can be determined from the first flag block or the second flag block. Then, the block with errors can be processed to avoid the erroneous block from having an adverse effect on the data sequence.

[0058] In one implementation, before processing the data sequence according to the type of the block corresponding to the block with error, the method further includes:

[0059] The type of the block is determined based on the expected position of the 64-bit / 66-bit block.

[0060] In an embodiment of the present application, before processing the data sequence based on the block type corresponding to the erroneous block, the block type may be determined based on the expected position of the 64-bit / 66-bit block. Specifically, the expected position may be determined by one or more of the following methods:

[0061] (1) The length of the data sequence.

[0062] (2) The structure of the data sequence.

[0063] (3) Overhead of data sequence.

[0064] (4) Synchronization headers of the start block (S block), data block (D block), and end block (T block).

[0065] (5) Types of start block (S block), data block (D block), and end block (T block).

[0066] (6) The order of the start block (S block), data block (D block), and end block (T block).

[0067] More specifically, in one implementation, determining the type of the block according to the expected position of the 64-bit / 66-bit block includes:

[0068] Determine the type of the previous 64-bit / 66-bit block or the type of the next 64-bit / 66-bit block based on the type of the current 64-bit / 66-bit block, or determine the type of the 64-bit / 66-bit block based on whether the 64-bit / 66-bit block contains overhead, or determine the type of the 64-bit / 66-bit block based on the data sequence structure, or determine the type of the 64-bit / 66-bit block based on the data sequence length.

[0069] In an embodiment of the present application, the type of the previous 64-bit / 66-bit block or the type of the next 64-bit / 66-bit block can be determined based on the type of the current 64-bit / 66-bit block. The type of the 64-bit or 66-bit block can also be determined based on whether the 64-bit or 66-bit block contains overhead. Alternatively, the type of the 64-bit or 66-bit block can be determined based on the data sequence structure, or the type of the 64-bit / 66-bit block can be determined based on the length of the data sequence. As an example, after the network-side device receives the data sequence, if the T block of the previous data sequence is correct and the next received 64B / 66B block is not an idle block and is not an O block, then based on the block type and sequence, it can be determined that the block received at the expected position is the first marker block (S block). As another example, if the current block is the first marker block (start block), the next block is expected to be a data block (based on the structure of the data sequence, the first block is an S block, the second block is a D block, the third block is a D block, and the L+2th block is a T block). In this way, the block type can be determined based on the expected position of the 64-bit / 66-bit block.

[0070] In one implementation, the block type further includes an error block, and the method further includes:

[0071] The error block is determined as a block having an error.

[0072] Specifically, block types also include error blocks. Due to certain anomalies, the outer 64B / 66B block may become an error block (as shown in FIG6 ). In this case, the content of the inner 64B / 66B block will be affected. In the embodiment of the present application, the error block is also determined to be an error block. As shown in FIG7 , the 66B blocks of Ethernet client services (such as block A and block B) are encapsulated into a data sequence (such as block 1 and block 2), and the last 2 bits of block 1 and the first 62 bits of block 2 are encapsulated into the payload of block B. If block B becomes an error block during transmission, both block 1 and block 2 are affected. In this way, the error block is also determined to be an error block, and the error block can also be processed to prevent the error block from adversely affecting the data sequence.

[0073] In one implementation, the processing of the data sequence according to the type of the block corresponding to the block with the error includes:

[0074] If the block received at the expected position is the second marker block in the data sequence, but what is actually received is an error block in the data sequence, then when the second marker block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced by the error block; if the block received at the expected position is the data block in the data sequence, but what is actually received is the error block, then when the data block is restored to the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced by the error block.

[0075] Specifically, if the block received at the expected position is the second marker block in the data sequence, the second marker block may be the end block, but what is actually received is an error block in the data sequence. In this case, the content of the inner block or small-granular layer service can be restored from the second marker block. That is, when the inner block or small-granular layer service is extracted from the second marker block, the corresponding inner block or small-granular layer service is replaced with the error block. If the block received at the expected position is a data block in the data sequence, but what is actually received is an error block, when the data block is restored to the inner block or small-granular layer service, the corresponding inner block or small-granular layer service can be replaced with the error block. For example, if a 64B / 66B block in a data sequence is expected to be the second marker block (end block), but what is received is an error block, the data sequence is discarded, or the data sequence continues to be processed, or when the error block is restored to the inner block or small-granular layer service, the corresponding inner block (small-granular layer service) is replaced with an error block. If a 64B / 66B block in a data sequence is used to restore an inner block or a small-granule layer service, and the corresponding inner block (small-granule layer service) has a synchronization header or type field error, it is replaced with an Error block. For another example, if a 64B / 66B block in a data sequence is expected to be a data block, but an Error block is received, then when the Error block is used to restore an inner block or a small-granule layer service, the corresponding inner block (small-granule layer service) is replaced with an Error block. In this way, the block received at the expected position can be processed in cases where the block received at the expected position is the second marker block in the data sequence, but the block actually received is an error block in the data sequence, or where the block received at the expected position is a data block in the data sequence, but the block actually received is an error block.

[0076] In one implementation, the processing of the data sequence according to the type of the block corresponding to the block with the error includes:

[0077] If the block received at the expected position is the first marker block in the data sequence, but what is actually received is an error block, the data sequence is discarded or other blocks of the data sequence are continued to be processed, or the first marker block is used to restore the content of the inner block or small particle layer service, and the corresponding inner block or small particle layer service is replaced with the error block.

[0078] In an embodiment of the present application, if the block received at the expected position is the first marker block in the data sequence, the first marker block can be the start block, but what is actually received is an error block. In this case, the data sequence can be discarded or other blocks in the data sequence can be processed continuously. Alternatively, when the first marker block is used to restore the contents of the inner block or small-granular layer service, that is, when the inner block or small-granular layer service is extracted from the first marker block, the corresponding inner block or small-granular layer service is replaced with the error block. For example, if a 64B / 66B block in a data sequence is expected to be the first marker block (start block), but what is received is an Error block, the data sequence can be discarded, or the data sequence can be processed continuously. Alternatively, when the Error block is used to restore the contents of the inner block or small-granular layer service, the corresponding inner block (small-granular layer service) is replaced with an Error block. In this way, the block received at the expected position can be processed when it is the first marker block in the data sequence, but what is actually received is an error block.

[0079] In one implementation, the first flag block includes overhead, and the processing of the data sequence according to the type of block corresponding to the block with error includes:

[0080] In the case that the type of block corresponding to the erroneous block is a first marker block (the synchronization header or type field of the received block does not match the first marker block), the overhead is extracted from the first marker block. If the cyclic redundancy check in the overhead is correct, the overhead or payload in the first marker block is extracted for processing. If the cyclic redundancy check in the overhead is wrong, the data sequence is discarded or the first marker block is replaced by an erroneous block, or the overhead is discarded and the payload continues to be processed.

[0081] In an embodiment of the present application, the first marker block may be a start block, and the first marker block contains overhead. When the type of block corresponding to the erroneous block is the first marker block (the synchronization header or type field of the received block does not match the synchronization header or type field of the first marker block), the overhead can be extracted from the first marker block and a cyclic redundancy check (CRC) is performed on the overhead. The cyclic redundancy check is a technology that generates a checksum to detect whether data is transmitted incorrectly when transmitting data. If the cyclic redundancy check in the overhead of the first marker block is correct, the overhead or payload in the first marker block can be extracted for processing. If the cyclic redundancy check in the overhead is wrong, the data sequence can be discarded or the first marker block can be replaced with an erroneous block, or the overhead can be discarded and the payload can continue to be processed. In this way, the first marker block can be processed when the first marker block contains overhead and the type of block corresponding to the erroneous block is the first marker block.

[0082] In one implementation, the processing of the data sequence according to the type of the block corresponding to the block with the error includes:

[0083] When the type of block corresponding to the erroneous block is the first marker block (the synchronization header or type field of the received block does not match the synchronization header or type field of the first marker block), the data content of the first marker block is extracted for processing; or the block is replaced with an erroneous block; when the first marker block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the erroneous block.

[0084] Specifically, if it is determined that the block type corresponding to the error block is a first marker block (start block), the data content of the first marker block can be extracted for processing, or the block can be replaced with an error block. When the first marker block recovers the content of the inner block or small-granule layer service, that is, when the inner block or small-granule layer service is extracted from the first marker block, the corresponding inner block or small-granule layer service can be replaced with the error block. For example, if a 64B / 66B block in a data sequence is expected to be the first marker block (start block), but the received 64B / 66B block is incorrect (the synchronization header or type field is incorrect, or the synchronization header or type field does not match the expected one), one or more of the following operations can be performed: replacing the 64B / 66B block with an error block; continuing to process other blocks in the data sequence; or, when the 64B / 66B block recovers the inner block or small-granule layer service, replacing the corresponding inner block (small-granule layer service) with an error block; or discarding the data sequence. In this way, if the block type corresponding to the error block is a first marker block, the first marker block can be processed.

[0085] In one implementation, the processing of the data sequence according to the type of the block corresponding to the block with the error includes:

[0086] When the type of block corresponding to the erroneous block is the second marker block (the synchronization header or type field of the received block does not match the synchronization header or type field of the second marker block), the data content of the second marker block is extracted for processing; or the block is replaced with the erroneous block; when the second marker block restores the content of the inner layer block or the small particle layer service, the corresponding inner layer block or the small particle layer service is replaced with the erroneous block.

[0087] Specifically, if it is determined that the block type corresponding to the erroneous block is a second marker block (the synchronization header or type field of the received block does not match the synchronization header or type field of the second marker block), the data content of the second marker block can be extracted for processing, or the second marker block can be replaced with the erroneous block. When the content of the inner block or small-granule layer service is restored using the second marker block, that is, when the inner block or small-granule layer service is extracted from the second marker block, the corresponding inner block or small-granule layer service can be replaced with the erroneous block. For example, if a 64B / 66B block in a data sequence is expected to be a second marker block (end block), but the received 64B / 66B block is incorrect (the synchronization header or type field is incorrect, or the synchronization header or type field does not match the expected one), one or more of the following operations can be performed: replacing the 64B / 66B block with an error block; or when the 64B / 66B block is restored to the inner block or small-granule layer service, replacing the corresponding inner block (small-granule layer service) with an error block; or discarding the data sequence. In this way, if it is determined that the block type corresponding to the erroneous block is a second marker block, the erroneous block can be processed.

[0088] In one implementation, the second flag block contains overhead, and the processing of the data sequence according to the type of the block corresponding to the erroneous block includes:

[0089] In a case where the type of block corresponding to the erroneous block is the second marker block, overhead is extracted from the second marker block; if the cyclic redundancy check in the overhead is correct, the overhead or payload in the second marker block is extracted for processing; if the cyclic redundancy check in the overhead is wrong, the data sequence is discarded or the second marker block is replaced by the erroneous block, or the overhead is discarded and the payload continues to be processed.

[0090] Specifically, the second marker block (end block) may also contain overhead. If it is determined that the block type corresponding to the erroneous block is the second marker block, the overhead can be extracted from the second marker block. If the cyclic redundancy check in the overhead is correct, the overhead or payload in the second marker block can be extracted for processing. If the cyclic redundancy check in the overhead is incorrect, the data sequence can be discarded, the second marker block can be replaced with the erroneous block, or the overhead can be discarded and the payload can continue to be processed. In this way, if the second marker block contains overhead and it is determined that the block type corresponding to the erroneous block is the second marker block, the erroneous block can be processed.

[0091] In one implementation, the processing of the data sequence according to the type of the block corresponding to the block with the error includes:

[0092] When the type of block corresponding to the erroneous block is a data block (the synchronization header of the received block does not match the data block synchronization header) and the data block is the first data block in the data sequence, the overhead is extracted from the first data block. If the cyclic redundancy check in the overhead is correct, the overhead or payload in the first data block is extracted for processing; if the cyclic redundancy check in the overhead is wrong, the data block is replaced with an erroneous block, or the overhead is discarded and the payload is continued to be processed; when there are errors in other data blocks except the first data block in the data sequence, the data content of the data block is extracted for processing, or the data block is replaced with an erroneous block or when the data block restores the inner block or small particle layer service, the corresponding inner block or the small particle layer service is replaced with the erroneous block.

[0093] Specifically, if the block type corresponding to the erroneous block is a data block and the data block is the first data block in the data sequence, the overhead can be extracted from the first data block and a cyclic redundancy check (CRC) check in the overhead can be determined to be correct. If the CRC check in the overhead is correct, the overhead or payload in the first data block can be extracted for processing. If the CRC check in the overhead is incorrect, the data block can be replaced with the erroneous block, or the overhead can be discarded and the payload can continue to be processed.

[0094] In addition, when errors exist in data blocks other than the first data block in the data sequence, the data content of the data block can be extracted for processing, or the data block with the error can be replaced with an error block, or when the data block recovers the inner block or small particle layer service, the corresponding inner block or small particle layer service is replaced with the error block. For example, if a 64B / 66B block in a data sequence is expected to be a data block, but the synchronization header of the received 64B / 66B block is erroneous or inconsistent with expectations, one or more of the following operations can be performed: extract the payload content of the 64B / 66B block for processing; or replace the 64B / 66B block with an Error block; or when the 64B / 66B block recovers the inner block or small particle layer service, the corresponding inner block (small particle layer service) is replaced with an Error block.

[0095] In this way, the data block can be processed when the type of block corresponding to the erroneous block is a data block and the data block is the first data block in the data sequence, and the erroneous data block can also be processed when errors exist in other data blocks except the first data block in the data sequence.

[0096] In one implementation, after processing the data sequence according to the type of the block corresponding to the block with error, the method further includes:

[0097] When the first flag block, the data block or the second flag block restores the inner block or the small particle layer service, if the corresponding inner block or the small particle layer service has a type domain error or a synchronization header error, the corresponding inner block or the small particle layer service is replaced with an error block.

[0098] Specifically, after receiving the data sequence, when the inner block or small particle layer service is restored in the first flag block, data block or second flag block, that is, when the inner block or small particle layer service is extracted from the data sequence, if it is found that the inner block or small particle layer service in the data sequence has a type domain error or a synchronization header error, the above-mentioned inner block or small particle layer service can be replaced with an error block to avoid the erroneous inner block or small particle layer service from having an adverse effect on the data sequence.

[0099] In one implementation, the data format of the business data corresponding to the data sequence is a physical coding sublayer data format, the business data includes multiple data blocks, the first flag block and the second flag block of the data sequence contain at least one data block of the business data, and after determining the erroneous block from the first flag block, the data block and the second flag block, the method further includes: marking the data content in the data block corresponding to the business data corresponding to the erroneous block as an error.

[0100] Specifically, in the embodiment of the present application, the service data corresponding to the data sequence can be a small particle layer service, and the data format of the service data corresponding to the data sequence is also the physical coding sublayer data format, that is, the service data also includes multiple data blocks (D blocks). As shown in Figure 3, the service data (small particle layer service) needs to be encapsulated into a data sequence. In the data sequence, the data block and the second flag block contain at least one data block of the above-mentioned service data (small particle layer service). After determining that there is an erroneous block in the data sequence, the data content in the data block corresponding to the service data corresponding to the erroneous block is marked as an error.

[0101] In this way, after determining that there is an erroneous block in the data sequence, the data content in the database corresponding to the business data corresponding to the erroneous block can be marked as erroneous, and then the data content marked as erroneous can be processed to avoid the erroneous block from having an adverse impact on the content of the business data and the use of the business data.

[0102] The data processing method provided in the embodiments of the present application is described in detail below through specific examples.

[0103] Example 1:

[0104] Figure 8 shows a schematic diagram of the structure of a data sequence encapsulating service data provided by an embodiment of the present application. As shown in Figure 2, the data sequence consists of a first marker block (S block), L data blocks (D blocks), and a second marker block (T block), where L is an integer greater than or equal to 1, and the overhead is placed in the first data block. The data processing method includes the following steps:

[0105] Step 1: The network-side device receives the data sequence.

[0106] Step 2: If the expected position is the first marker block, the next block is expected to be a data block (according to the structure of the data sequence, the first block is an S block, the second block is a D block, the third block is a D block, and the L+2th block is a T block).

[0107] If the expected position is the first marker block and the first marker block of the received data sequence is incorrect (the received block synchronization header is not 0b10 and / or the type field is not 0x78), the first marker block is replaced with an Error block; or when the first marker block is restored to an inner block or a small particle layer service, the corresponding inner block (small particle layer service) is replaced with an Error block.

[0108] Step 3: If the expected position is a data block, but the data block is an erroneous block, then:

[0109] (1) If the expected location is a data block, but the synchronization header of the data block is incorrect (the synchronization header of the received block is not 0b01), extract the overhead in the data block. If the CRC in the overhead is correct, extract the overhead or payload in the data block for processing; if the CRC in the overhead is incorrect, replace the data block with an error block, or discard the overhead and continue processing the payload.

[0110] (2) Or if the expected position is a data block, but the synchronization header of the data block is incorrect, you can do one of the following:

[0111] The data content of the data block is extracted for processing, or the data block is replaced with an Error block, or when the data block restores the inner block or small particle layer service, the corresponding inner block (small particle layer service) is replaced with an Error block.

[0112] Step 4: If the next 64B / 66B block after the first data block is expected to be a data block, then:

[0113] (1) If the expected position is a data block, but the data block is an Error block, when restoring the data block to an inner block or a small granular layer service, the corresponding inner block (small granular layer service) is replaced by an Error block.

[0114] (2) If the expected location is a data block, but the synchronization header of the data block is incorrect, the data content of the data block is extracted for processing; or the block is replaced with an Error block. Alternatively, when the data block recovers an inner block or a small granular layer service, the corresponding inner block (small granular layer service) is replaced with an Error block.

[0115] Step 5: Based on the length of the data sequence, determine whether the next 64B / 66B block is a data block or a second marker block (based on the structure of the data sequence, the first block is an S block, the second block is a D block, the third block is a D block, and the L+2th block is a T block). If it is a data block, repeat step 4. If it is a second marker block, proceed to step 6.

[0116] Step 6: If the expected position is the second marker block, but the second marker block is an erroneous block, then:

[0117] (1) If the expected position is the second marker block, but the second marker block is an Error block, when the second marker block restores the content of the inner block or the small granular layer, the corresponding inner block (small granular layer service) is replaced by the Error block.

[0118] (2) If the expected position is the second marker block, but the synchronization header of the second marker block is wrong (the received block synchronization header is not 0b10), extract the data content of the second marker block for processing; or replace the block with an Error block; when the second marker block restores the content of the inner block or small particle layer, the corresponding inner block (small particle layer service) is replaced with an Error block.

[0119] (3) If the expected position is the second marker block, but the type field of the second marker block is wrong (the received block type field does not match the second marker block), extract the data content of the second marker block for processing; or replace the block with an Error block; when the second marker block restores the content of the inner block or the small particle layer, the corresponding inner block (small particle layer service) is replaced with an Error block.

[0120] Example 2:

[0121] Figure 9 shows a schematic diagram of the structure of a data sequence encapsulating service data provided by an embodiment of the present application. As shown in Figure 9, the data sequence consists of a first marker block (S block), L data blocks (D blocks), and a second marker block (T block), where L is an integer greater than or equal to 1, and the overhead is placed in the first marker block. The data processing method includes the following steps:

[0122] Step 1: The network-side device receives the data sequence.

[0123] Step 2: If the T block of the previous data sequence is correct, and the next received 64B / 66B block is not an idle block and is not an O block, then the expected received block is determined to be the first marker block (S block) based on the block type and sequence. If the first marker block is an erroneous block, then:

[0124] (1) If the expected position is the first marker block, but the first marker block is an Error block, continue to process other blocks of the data sequence or discard the data sequence.

[0125] (2) If the expected position is the first marker block, but the synchronization header of the first marker block is incorrect, the overhead in the first marker block is extracted. If the CRC in the overhead is correct, the overhead or payload in the first marker block is extracted for processing; if the CRC in the overhead is incorrect, the data sequence is discarded; the first marker block is replaced with an error block, or the overhead is discarded and the payload is processed.

[0126] (3) If the expected location is the first marker block, but the type field of the first marker block is incorrect, extract the overhead. If the CRC in the overhead is correct, extract the overhead or payload in the first marker block for processing. If the CRC in the overhead is incorrect, discard the data sequence; either replace the first marker block with an error block, or discard the overhead and continue processing the payload.

[0127] Step 3: The next 64B / 66B after the first marker block is expected to be a data block, then:

[0128] (1) If the expected position is a data block, but the data block is an Error block, when the data block restores the content of the inner block or the small granular layer, the corresponding inner block (small granular layer service) is replaced by the Error block.

[0129] (2) If the expected position is a data block, but the synchronization header of the data block is incorrect, you can perform one of the following operations:

[0130] The data content of the data block is extracted for processing, or the data block is replaced with an Error block, or when the data block restores the inner block or small particle layer service, the corresponding inner block (small particle layer service) is replaced with an Error block.

[0131] Step 4: Based on the length of the data sequence, determine whether the next 64B / 66B block is expected to be a data block or a second marker block. If it is a data block, repeat step 3. If it is a second marker block, proceed to step 5.

[0132] Step 5: If the expected position is the second marker block, but the second marker block is an erroneous block, then:

[0133] (1) If the expected position is the second marker block, but the second marker block is an Error block, when the second marker block restores the content of the inner block or the small granular layer, the corresponding inner block (small granular layer service) is replaced by the Error block.

[0134] (2) If the expected position is the second marker block, but the synchronization header of the second marker block is wrong, the data content of the second marker block is extracted for processing; or the second marker block is replaced with an Error block; or when the second marker block is used to restore the content of the inner block or small particle layer, the corresponding inner block (small particle layer service) is replaced with an Error block.

[0135] (3) If the expected position is the second marker block, but the type field of the second marker block is wrong, the content of the second marker block data is extracted for processing; or the second marker block is replaced with an Error block; or when the second marker block is used to restore the content of the inner block or small particle layer, the corresponding inner block (small particle layer service) is replaced with an Error block.

[0136] Example 3:

[0137] Figure 10 shows a schematic diagram of the structure of a data sequence that encapsulates customer service data, provided by an embodiment of the present application. As shown in Figure 10, the data sequence consists of a first marker block (S block), L data blocks (D blocks), and a second marker block (T block), where L is an integer greater than or equal to 1, and the overhead is placed in the second marker block. The data processing method includes the following steps:

[0138] Step 1: The network-side device receives the data sequence.

[0139] Step 2: If the second marker block of the previous data sequence is correct, and the next received 64B / 66B block is not a free block and is not an O block, then the expected received block is the first marker block. If the received first marker block is an erroneous block, then:

[0140] (1) If the expected position is the first marker block, but the first marker block is an Error block, the data sequence is discarded or the subsequent data blocks and the second marker block are processed.

[0141] (2) If the expected position is the first marker block, but the synchronization header of the first marker block is incorrect, the data sequence is discarded or the first marker block is replaced by an Error block; or when the first marker block is restored to an inner block or a small particle layer service, the corresponding inner block (small particle layer service) is replaced by an Error block.

[0142] (3) If the expected position is the first marker block, but the type field of the first marker block is incorrect, the data sequence is discarded or the first marker block is replaced by an Error block; or when the first marker block is restored to an inner block or a small particle layer service, the corresponding inner block (small particle layer service) is replaced by an Error block.

[0143] Step 3: If the next 64B / 66B block after the first marker block is expected to be a data block, then:

[0144] (1) If the expected position is a data block, but the data block is an Error block, when the data block restores the content of the inner block or the small granular layer, the corresponding inner block (small granular layer service) is replaced by the Error block data block.

[0145] (2) If the expected position is a data block, but the synchronization header of the data block is wrong, the data content of the data block is extracted for processing; or the data block is replaced with an Error block; or when the data block recovers the inner block or small particle layer service, the corresponding inner block (small particle layer service) is replaced with an Error block.

[0146] Step 4: Based on the length of the data sequence, determine whether the next 64B / 66B block is expected to be a data block or a second marker block. If it is a data block, repeat step 3. If it is a second marker block, proceed to step 5.

[0147] Step 5: If the expected position is the second marker block, but the second marker block is an erroneous block, then:

[0148] (1) If the expected position is the second marker block, but the second marker block is an Error block, the data sequence can be discarded or when the second marker block restores the content of the inner block or small granular layer, the corresponding inner block (small granular layer service) is replaced by an Error block.

[0149] (2) If the expected position is the second marker block, but the synchronization header of the second marker block is incorrect, extract the overhead in the second marker block. If the CRC in the overhead is correct, extract the overhead or payload in the second marker block for processing. If the CRC in the overhead is incorrect, the data sequence can be discarded; or the second marker block can be replaced with an Error block; or the overhead can be discarded and the payload can be processed.

[0150] (3) If the expected position is the second marker block, but the type field of the second marker block is incorrect, the overhead in the second marker block can be extracted. If the CRC in the overhead is correct, the overhead or payload in the second marker block can be extracted for processing. If the CRC in the overhead is incorrect, the data sequence can be discarded; the second marker block can be replaced with an Error block, or the overhead can be discarded and the payload can be processed.

[0151] It should be noted that the data processing method provided in the embodiments of the present application can be executed by a data processing device or a control module in the data processing device for executing the data processing method. In the embodiments of the present application, the data processing device provided in the embodiments of the present application is described by taking the data processing device executing the data processing method as an example.

[0152] 11 is a schematic diagram of the structure of a data processing device according to an embodiment of the present invention. As shown in FIG11 , the data processing device 1100 includes: a receiving module 1110 , an executing module 1120 , and a processing module 1130 .

[0153] A receiving module 1110 is configured to receive a data sequence, wherein the data sequence includes multiple types of blocks, wherein the types of the blocks include a first marker block, a data block, and a second marker block; an executing module 1120 is configured to determine a block with an error from among the first marker block, the data block, or the second marker block; and a processing module 1130 is configured to process the data sequence according to the type of block corresponding to the block with the error.

[0154] In one implementation, the execution module 1120 is used to determine a block with a synchronization header error from the first flag block, the data block, or the second flag block as the block with the error; or, to determine a block with a type domain error from the first flag block or the second flag block as the block with the error.

[0155] In one implementation, the execution module 1120 is further configured to determine the type of the block according to the expected position of the 64-bit / 66-bit block.

[0156] In one implementation, the execution module 1120 is configured to determine the type of the previous 64-bit / 66-bit block or the type of the next 64-bit / 66-bit block based on the type of the current 64-bit / 66-bit block, or determine the type of the 64-bit / 66-bit block based on whether the 64-bit / 66-bit block contains overhead, or determine the type of the 64-bit / 66-bit block based on a data sequence structure, or determine the type of the 64-bit / 66-bit block based on a data sequence length.

[0157] In one implementation, the block type further includes an error block, and the execution module 1120 is further configured to determine the error block as a block with an error.

[0158] In one implementation, the processing module 1130 is used to, if the block received at the expected position is the second marker block in the data sequence, but what is actually received is an error block in the data sequence, then when the second marker block is used to restore the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the error block; if the block received at the expected position is the data block in the data sequence, but what is actually received is the error block, then when the data block is restored to the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the error block.

[0159] In one implementation, the processing module 1130 is used to discard the data sequence or continue processing other blocks of the data sequence if the block received at the expected position is the first marker block in the data sequence, but the block actually received is an error block, or when restoring the content of the inner block or small particle layer service with the first marker block, the corresponding inner block or small particle layer service is replaced with the error block.

[0160] In one implementation, the first marker block contains overhead, and the processing module 1130 is used to extract the overhead from the first marker block when the type of the block corresponding to the erroneous block is the first marker block; if the cyclic redundancy check in the overhead is correct, the overhead or payload in the first marker block is extracted for processing; if the cyclic redundancy check in the overhead is wrong, the data sequence is discarded or the first marker block is replaced with an erroneous block, or the overhead is discarded and the payload continues to be processed.

[0161] In one implementation, the processing module 1130 is used to extract the data content of the first marker block for processing when the type of block corresponding to the block with error is the first marker block; or replace the block with an error block; when the first marker block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the error block.

[0162] In one implementation, the processing module 1130 is used to extract the data content of the second marker block for processing when the type of the block corresponding to the erroneous block is the second marker block; or replace the block with the erroneous block; when the second marker block restores the content of the inner layer block or the small particle layer service, the corresponding inner layer block or the small particle layer service is replaced with the erroneous block.

[0163] In one implementation, the second marker block contains overhead, and the processing module 1130 is used to extract the overhead from the second marker block when the type of the block corresponding to the erroneous block is the second marker block; if the cyclic redundancy check in the overhead is correct, the overhead or payload in the second marker block is extracted for processing; if the cyclic redundancy check in the overhead is wrong, the data sequence is discarded or the second marker block is replaced by the erroneous block, or the overhead is discarded and the payload continues to be processed.

[0164] In one implementation, the processing module 1130 is used to extract the overhead from the first data block when the type of block corresponding to the block with error is a data block and the data block is the first data block in the data sequence; if the cyclic redundancy check in the overhead is correct, the overhead or payload in the first data block is extracted for processing; if the cyclic redundancy check in the overhead is wrong, the data block is replaced with an error block, or the overhead is discarded and the payload is continued to be processed; when there are errors in other data blocks other than the first data block in the data sequence, the data content of the data block is extracted for processing, or the data block is replaced with an error block or when the data block restores the inner block or small particle layer service, the corresponding inner block or the small particle layer service is replaced with the error block.

[0165] In one implementation, the data format of the business data corresponding to the data sequence is a physical coding sublayer data format, the business data includes multiple data blocks, the first flag block and the second flag block of the data sequence contain at least one data block of the business data, and the processing module 1130 is further used to mark the data content in the data block corresponding to the business data corresponding to the erroneous block as erroneous.

[0166] In one implementation, the processing module 1130 is also used to, when the first flag block, the data block or the second flag block restores the inner block or the small particle layer service, if the corresponding inner block or the small particle layer service has a type domain error or a synchronization header error, the corresponding inner block or the small particle layer service is replaced with an error block.

[0167] In one implementation, the first marker block is a start block, and the second marker block is an end block.

[0168] The data processing device in the embodiments of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. For example, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The non-mobile electronic device can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), an ATM, or an kiosks, etc., which are not specifically limited in the embodiments of the present application.

[0169] The data processing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0170] The data processing device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 1. To avoid repetition, it will not be described here.

[0171] Optionally, as shown in Figure 12, an embodiment of the present application further provides a network side device 1200, including a processor 1201 and a memory 1202, wherein the memory 1202 stores a program or instruction that can be run on the processor 1201, and when the program or instruction is executed by the processor 1201, it implements: receiving a data sequence, the data sequence including multiple types of blocks, the types of the blocks including a first flag block, a data block and a second flag block; determining an erroneous block from the first flag block, the data block or the second flag block; and processing the data sequence according to the type of the block corresponding to the erroneous block.

[0172] In one implementation, a block with a synchronization header error is determined from the first flag block, the data block, or the second flag block as the block with the error; or a block with a type domain error is determined from the first flag block or the second flag block as the block with the error.

[0173] In one implementation, before processing the data sequence according to the block type corresponding to the block with errors, the block type is determined according to the expected position of the 64-bit / 66-bit block.

[0174] In one implementation, the type of the previous 64-bit / 66-bit block or the type of the next 64-bit / 66-bit block is determined based on the type of the current 64-bit / 66-bit block, or the type of the 64-bit / 66-bit block is determined based on whether the 64-bit / 66-bit block contains overhead, or the type of the 64-bit / 66-bit block is determined based on the data sequence structure, or the type of the 64-bit / 66-bit block is determined based on the length of the data sequence.

[0175] In an implementation manner, the block type further includes an error block, and the error block is determined to be a block with an error.

[0176] In one implementation, if the block received at the expected position is the second marker block in the data sequence, but what is actually received is an error block in the data sequence, then when the second marker block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the error block; if the block received at the expected position is the data block in the data sequence, but what is actually received is the error block, then when the data block is restored to the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the error block.

[0177] In one implementation, if the block received at the expected position is the first marker block in the data sequence, but what is actually received is an error block, the data sequence is discarded or other blocks of the data sequence are continued to be processed or the first marker block is used to restore the content of the inner block or small particle layer service, and the corresponding inner block or small particle layer service is replaced with the error block.

[0178] In one implementation, the first marker block contains overhead. When the type of the block corresponding to the erroneous block is the first marker block, the overhead is extracted from the first marker block. If the cyclic redundancy check in the overhead is correct, the overhead or payload in the first marker block is extracted for processing. If the cyclic redundancy check in the overhead is wrong, the data sequence is discarded or the first marker block is replaced with an erroneous block, or the overhead is discarded and the payload continues to be processed.

[0179] In one implementation, when the type of block corresponding to the erroneous block is the first marker block, the data content of the first marker block is extracted for processing; or the block is replaced with an erroneous block; when the first marker block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the erroneous block.

[0180] In one implementation, when the type of block corresponding to the erroneous block is the second marker block, the data content of the second marker block is extracted for processing; or the block is replaced with the erroneous block; when the second marker block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced with the erroneous block.

[0181] In one implementation, the second marker block contains overhead. When the type of the block corresponding to the erroneous block is the second marker block, the overhead is extracted from the second marker block. If the cyclic redundancy check in the overhead is correct, the overhead or payload in the second marker block is extracted for processing. If the cyclic redundancy check in the overhead is wrong, the data sequence is discarded or the second marker block is replaced by the erroneous block, or the overhead is discarded and the payload continues to be processed.

[0182] In one implementation, when the type of block corresponding to the block with error is a data block and the data block is the first data block in the data sequence, the overhead is extracted from the first data block, and if the cyclic redundancy check in the overhead is correct, the overhead or payload in the first data block is extracted for processing; if the cyclic redundancy check in the overhead is wrong, the data block is replaced with an error block, or the overhead is discarded and the payload is continued to be processed; when there are errors in other data blocks in the data sequence except the first data block, the data content of the data block is extracted for processing, or the data block is replaced with an error block or when the data block restores the inner block or small particle layer service, the corresponding inner block or the small particle layer service is replaced with the error block.

[0183] In one implementation, the data format of the business data corresponding to the data sequence is a physical coding sublayer data format, the business data includes multiple data blocks, the first flag block and the second flag block of the data sequence contain at least one data block of the business data, and after determining the erroneous block from the first flag block, the data block and the second flag block, the data content in the data block corresponding to the business data corresponding to the erroneous block is marked as erroneous.

[0184] In one implementation, after the data sequence is processed according to the type of block corresponding to the erroneous block, when the first flag block, the data block or the second flag block restores the inner block or the small particle layer service, if the corresponding inner block or the small particle layer service has a type domain error or a synchronization header error, the corresponding inner block or the small particle layer service is replaced with an erroneous block.

[0185] In one implementation, the first marker block is a start block, and the second marker block is an end block.

[0186] The specific execution steps can refer to the various steps of the above-mentioned data processing method embodiment, and can achieve the same technical effect. To avoid repetition, they will not be described here.

[0187] It should be noted that the network side devices in the embodiments of the present application include: servers, terminals or other devices other than terminals.

[0188] The above network-side device structure does not constitute a limitation on the network-side device. The network-side device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, the input unit may include a graphics processing unit (GPU) and a microphone, and the display unit may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like to configure a display panel. The user input unit includes a touch panel and at least one of other input devices. The touch panel is also called a touch screen. Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0189] The memory can be used to store software programs and various data. The memory may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory may include a volatile memory or a non-volatile memory, or the memory may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM) and direct rambus random access memory (DRRAM).

[0190] The processor may include one or more processing units; optionally, the processor may integrate an application processor and a modem processor, wherein the application processor primarily handles operations related to the operating system, user interface, and application programs, and the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into the processor.

[0191] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned data processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0192] The processor is the processor on the network side described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as ROM, RAM, magnetic disk or optical disk.

[0193] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0194] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0195] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A method for processing data, wherein: The method comprises: Receive a data sequence, the data sequence comprising a plurality of types of blocks, the types of the blocks comprising a first flag block, a data block, and a second flag block; Determine a block with an error from the first marker block, the data block, or the second marker block; The data sequence is processed according to the type of the block corresponding to the block with error.

2. The method according to claim 1, wherein: The determining a block having an error from the first marker block, the data block or the second marker block comprises: Determine the block with a synchronization header error as the block with error from the first marker block, the data block or the second marker block; Alternatively, a block with a type domain error is determined from the first flag block or the second flag block as the block with error.

3. The method according to claim 1, wherein: Before processing the data sequence according to the type of the block corresponding to the block with error, the method further includes: The type of the 64-bit / 66-bit block is determined based on the expected position of the block.

4. The method according to claim 3, wherein: The determining the type of the block according to the expected position of the 64-bit / 66-bit block includes: The type of the previous 64-bit / 66-bit block or the type of the next 64-bit / 66-bit block is determined according to the type of the current 64-bit / 66-bit block, or the type of the 64-bit / 66-bit block is determined according to whether the 64-bit / 66-bit block contains overhead, or the type of the 64-bit / 66-bit block is determined according to the data sequence structure, or the type of the 64-bit / 66-bit block is determined according to the data sequence length.

5. The method according to claim 1, wherein: The type of the block further includes an error block, and the method further includes: The error block is determined as a block having an error.

6. The method according to claim 3, wherein: The processing of the data sequence according to the type of the block corresponding to the block with error includes: If the block received at the expected position is the second marker block in the data sequence, but what is actually received is an error block in the data sequence, when the second marker block restores the content of the inner block or the small particle layer service, the corresponding inner block or the small particle layer service is replaced by the error block; If the block received at the expected position is a data block in the data sequence, but what is actually received is the error block, when the data block is restored to an inner block or a small particle layer service, the corresponding inner block or the small particle layer service is replaced by the error block.

7. The method according to claim 3, wherein: The processing of the data sequence according to the type of the block corresponding to the block with error includes: If the block received at the expected position is the first marker block in the data sequence, but what is actually received is an error block, the data sequence is discarded or other blocks of the data sequence are continued to be processed, or the first marker block is used to restore the content of the inner block or small particle layer service, and the corresponding inner block or small particle layer service is replaced by the error block.

8. The method according to claim 2, wherein: The first flag block contains overhead, and the processing of the data sequence according to the type of the block corresponding to the block with error includes: In a case where the type of block corresponding to the erroneous block is a first marker block, overhead is extracted from the first marker block; if the cyclic redundancy check in the overhead is correct, the overhead or payload in the first marker block is extracted for processing; if the cyclic redundancy check in the overhead is wrong, the data sequence is discarded or the first marker block is replaced by an erroneous block, or the overhead is discarded and the payload continues to be processed.

9. The method according to claim 2, wherein: The processing of the data sequence according to the type of the block corresponding to the block with error includes: In the case that the type of block corresponding to the block with error is the first marking block, extracting the data content of the first marking block for processing; or replacing the block with an error block; When the first flag block restores the content of the inner layer block or the small particle layer service, the corresponding inner layer The block or the small particle layer business is replaced by the error block.

10. The method according to claim 2, wherein: The processing of the data sequence according to the type of the block corresponding to the block with error includes: In the case that the type of block corresponding to the block with error is the second marking block, extracting the data content of the second marking block for processing; or replacing the block with the error block; When the second marker block restores the content of the inner layer block or the small particle layer service, the corresponding inner layer block or the small particle layer service is replaced by an error block.

11. The method according to claim 2, wherein: The second flag block contains overhead, and the processing of the data sequence according to the type of the block corresponding to the block with error includes: In a case where the type of block corresponding to the erroneous block is the second marker block, the overhead is extracted from the second marker block; if the cyclic redundancy check in the overhead is correct, the overhead or payload in the second marker block is extracted for processing; if the cyclic redundancy check in the overhead is wrong, the data sequence is discarded or the second marker block is replaced by the erroneous block, or the overhead is discarded and the payload continues to be processed.

12. The method according to claim 2, wherein: The processing of the data sequence according to the type of the block corresponding to the block with error includes: In the case where the type of block corresponding to the block with error is a data block and the data block is the first data block in the data sequence, extracting overhead from the first data block, and if the cyclic redundancy check in the overhead is correct, extracting the overhead or payload in the first data block for processing; if the cyclic redundancy check in the overhead is wrong, replacing the data block with an error block, or discarding the overhead, and continuing to process the payload; When errors exist in data blocks other than the first data block in the data sequence, the data content of the data block is extracted for processing, or the data block is replaced with an error block or when the data block restores the inner block or small particle layer service, the corresponding inner block or small particle layer service is replaced with the error block.

13. The method according to any one of claims 1 to 12, wherein: The data format of the service data corresponding to the data sequence is a physical coding sublayer data format, the service data includes a plurality of data blocks, the first flag block and the second flag block of the data sequence contain at least one data block of the service data, and after determining the block with error from the first flag block, the data block and the second flag block, the method further includes: The data content in the data block corresponding to the business data corresponding to the erroneous block is marked as an error.

14. The method according to claim 1, wherein: After processing the data sequence according to the type of the block corresponding to the block with error, the method further includes: When the first marker block, the data block or the second marker block restores the inner block or the small particle layer service, if the corresponding inner block or the small particle layer service has a type domain error or a synchronization header error, the corresponding inner block or the small particle layer service is replaced with an error block.

15. The method according to claim 1, wherein: The first marker block is a start block, and the second marker block is an end block.

16. A network side device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method according to any one of claims 1 to 15 are implemented.

17. A readable storage medium storing a program or an instruction, wherein the program or the instruction, when executed by a processor, implements the steps of the method according to any one of claims 1 to 15.

Citation Information

Patent Citations

  • Communication method and device, and storage medium

    CN112468259A

  • Rate adaptation method and device

    CN113938245A

  • Code block processing method, node and medium

    CN113938247A

  • Data transmission method and electronic equipment

    CN114499772A

  • Data stream processing method and device, storage medium and electronic device

    CN115173988A