Ethernet frame framing method and apparatus

Abstract

The embodiment of the present application provides an Ethernet frame framing method and device, the method comprises the following steps: a receiving end receives a data stream with a fine-grained basic unit Fg-BU; the receiving end judges whether the Fg-BU frame is locked or unlocked according to whether the Fg-BU frame in the data stream is normal or not. In the present application, the receiving end can judge whether the Fg-BU frame is locked or unlocked according to whether the received Fg-BU frame is normal or not.

Description

Technical Field

[0001] The present invention relates to the field of communications, and more specifically, to an Ethernet frame fixing method and apparatus. Background Technology

[0002] In existing Ethernet technology, in order to solve the problem of flexible access of services of different granularities to the bearer network, a fine-granularity-basic unit (Fg-BU) is defined in the Ethernet Physical Coding Sublayer (PCS) layer to carry small-granularity services.

[0003] The Fine-Grained Basic Unit (Fg-BU) adopts the 64B / 66B coding type of IEEE 802.3 Clause 82. The Fg-BU frame has a fixed length, containing a start (S) block, h (h is an integer greater than or equal to 1) data (D) blocks, and an end (T) block, for a total length of h+2 64B / 66B blocks. The start (S) block format is as follows: Figure 1 As shown, the data (D) code block is as follows Figure 2 As shown, the end (T) code block is as follows Figure 3 As shown, where, Figure 3 The block type value can be 0x87, 0x99, 0xAA, 0xB4, 0xCC, 0xD2, 0xE1, or 0xFF. The format of the Fg-BU frame is as follows: Figure 5 As shown, in Figure 5 In the example, h=195, and the ending code block is T7. The format of the T7 code block is as follows: Figure 4 As shown, attached Figure 6 This is a schematic diagram of the Fg-BU frame overhead format.

[0004] The 195 data blocks and the end (T7) block provide 195 × 8 + 7 bytes of content, for a total length of 1567 bytes. Each Fg-BU contains 7 bytes of overhead and 1560 bytes of payload. The specific format definition of the 7-byte overhead is as follows: Figure 6 As shown. Among them: the Multiple Frame Indication (MFI) is 6 bits long and is used to indicate the number of each basic unit in the multiframe. For the first basic unit in the multiframe, the MFI is 0, and the MFI value of subsequent basic units is incremented by 1. For 5G channels, the MFI value ranges from 0 to 19; CRC: 7 bits long, calculated from the first 41 bits (including the fields after Flag, excluding the initial 2-bit reserved bits and the 6-bit MFI).

[0005] For a 5Gbps transmission bandwidth, one Fg-BU contains 24 sub-slots, each sub-slot being 65 bytes and capable of carrying eight 65-bit code blocks (64B / 66B code blocks compressed into 65-bit code blocks). Each sub-slot can be independently allocated to a single client. j Fg-BU frames form a multiframe, providing 24 × 20 = 480 sub-slots when j equals 20. Each sub-slot has a bandwidth of 10Mbps.

[0006] Each sub-slot carries eight 64B / 66B code blocks from customer services, with eight error code blocks filling unused time slots not allocated to services. The total of 24 × 8 = 192 64B / 66B code blocks from the 24 sub-slots are compressed from 66 bits to 65 bits (e.g., the first bit of 65B is 0 for data code blocks and 1 for control code blocks) and then filled into the payload time slots. After adding 7 bytes of overhead, these are sequentially filled into the payload of the D and T7 code blocks of the fg-BU.

[0007] The specific format of the 56-bit overhead for each Fg-BU frame is as follows: Figure 6 As shown, this includes the Multiframe Indicator (MFI), Overhead Channel Usage Indicator (Flag), Slot Increase Adjustment Announcement (S bit), Slot Activation Indicator (C bit), Slot Adjustment Request (CR bit), Slot Adjustment Response (CA bit), GCC Channel, Client ID, Sub-slot ID, and CRC. The GCC Channel shares bit positions with the Client ID and Sub-slot ID. When the Flag value is 11, it represents... Figure 6 The corresponding bit position after CA is used by the GCC channel. When the Flag value is 00, it means that the corresponding bit position is used by the client ID and sub-slot ID.

[0008] There is currently no clear definition on how the receiver determines whether an Fg-BU frame is locked or unlocked after it is sent from the sender to the receiver. Summary of the Invention

[0009] This invention provides an Ethernet frame fixing method and apparatus to at least solve the problem of how the receiving end determines the locking and unlocking of Fg-BU frames in related technologies.

[0010] According to an embodiment of the present invention, an Ethernet frame fixing method is provided, comprising: a receiving end receiving a data stream having fine-grained basic units (Fg-BU); the receiving end determining whether the Fg-BU frame is locked or unlocked based on whether the Fg-BU frame in the data stream is normal.

[0011] In an exemplary embodiment, the receiving end determines whether the Fg-BU frame is locked based on whether the Fg-BU frame in the data stream is normal, including: if the receiving end receives N consecutive normal Fg-BU frames, then it determines that the Fg-BU frame is locked, where N is an integer greater than or equal to 1.

[0012] In an exemplary embodiment, the Fg-BU frame is considered normal when it meets one or more of the following conditions: the start block of the Fg-BU frame is normal; the CRC check in the overhead of the Fg-BU frame is correct; the end block of the Fg-BU frame is normal; a data blocks of the Fg-BU frame are normal, where a is an integer greater than or equal to 0; and the length of the Fg-BU frame is a predetermined number of blocks.

[0013] In an exemplary embodiment, the receiving end determines whether the Fg-BU frame is out of lock based on whether the Fg-BU frame in the data stream is normal, including: if the receiving end receives M consecutive abnormal Fg-BU frames, then it determines that the Fg-BU frame is out of lock, where M is an integer greater than or equal to 1.

[0014] In an exemplary embodiment, the Fg-BU frame is considered abnormal when it meets one or more of the following conditions: the start block of the Fg-BU frame is abnormal; the end block of the Fg-BU frame is abnormal; the CRC check in the overhead of the Fg-BU frame is incorrect; b data blocks of the Fg-BU frame are abnormal, where b is an integer greater than or equal to 0; or the length of the Fg-BU frame is not the set number of blocks.

[0015] In an exemplary embodiment, after the receiving end determines that the Fg-BU frame is locked, the method further includes: the receiving end extracting the Fg-BU frame for processing.

[0016] In an exemplary embodiment, after the receiving end determines that the Fg-BU frame has lost its lock, the method further includes: the receiving end reporting alarm information about the Fg-BU frame losing its lock.

[0017] In an exemplary embodiment, after the receiving end determines that the Fg-BU frame is locked, the method further includes: the receiving end determines whether the Fg-BU multiframe is locked or unlocked based on the multiframe indication MFI value.

[0018] In an exemplary embodiment, the receiving end determines Fg-BU multiframe locking based on the multiframe indication MFI value by: if the MFI values ​​of X consecutive Fg-BU frames received by the receiving end are normal, then the receiving end determines that Fg-BU multiframe locking is achieved, where X is an integer greater than or equal to 1.

[0019] In an exemplary embodiment, the receiving end determines that the Fg-BU multiframe is out of lock based on the multiframe indication MFI value: if the MFI values ​​of Y consecutive Fg-BU frames received by the receiving end are abnormal, then it is determined that the Fg-BU multiframe is out of lock, where Y is an integer greater than or equal to 1.

[0020] In an exemplary embodiment, after the receiving end determines that the Fg-BU multiframe is locked, the method further includes: the receiving end extracting the Fg-BU multiframe for processing.

[0021] In an exemplary embodiment, after the receiving end determines that the multiframe has lost lock, the method further includes: the receiving end reporting alarm information about the multiframe losing lock.

[0022] According to another embodiment of the present invention, an Ethernet frame fixing device is provided, applied at a receiving end. The device includes: a receiving module for receiving a data stream having a fine-grained basic unit (Fg-BU); and a first judging module for judging whether the Fg-BU frame in the data stream is locked or unlocked based on whether the Fg-BU frame is normal.

[0023] In an exemplary embodiment, the first determination module includes: a first determination unit, configured to determine that the Fg-BU frame is locked when N consecutive normal Fg-BU frames are received, where N is an integer greater than or equal to 1.

[0024] In an exemplary embodiment, the first judgment module includes: a second judgment unit, configured to determine that the Fg-BU frame is out of lock when M consecutive abnormal Fg-BU frames are received, where M is an integer greater than or equal to 1.

[0025] In one exemplary embodiment, the apparatus further includes a second determination module, configured to determine whether the multiframe is locked or unlocked based on the multiframe indication MFI value when the Fg-BU frame is locked.

[0026] In an exemplary embodiment, the second determining module includes a third determining unit, configured to determine that the multiframe is locked if the MFI values ​​of the received consecutive X frames are normal, wherein X is an integer greater than or equal to 1.

[0027] In an exemplary embodiment, the second judgment module includes: a fourth judgment unit, configured to determine that the multiframe is out of lock when the MFI value of the received consecutive Y frames is abnormal, wherein Y is an integer greater than or equal to 1.

[0028] According to yet another embodiment of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to perform the steps in any of the above method embodiments when executed.

[0029] According to yet another embodiment of the present invention, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0030] In the above embodiments of the present invention, the receiving end determines whether the Fg-BU frame is locked or unlocked based on whether the received Fg-BU frame is normal, thereby realizing the determination of whether the Fg-BU frame is locked or unlocked. Attached Figure Description

[0031] Figure 1 This is a schematic diagram of the start (S) code block format based on related technologies;

[0032] Figure 2 This is a schematic diagram of the data (D) code block format based on related technologies;

[0033] Figure 3 This is a schematic diagram of the end (T) code block format based on relevant technologies;

[0034] Figure 4 It is based on the diagram of the end (T7) code block format of the relevant technology.

[0035] Figure 5 Based on the Fg-BU frame format diagram of related technologies;

[0036] Figure 6 This is a schematic diagram of the Fg-BU frame overhead format based on relevant technologies;

[0037] Figure 7 This is a schematic diagram of a computer terminal structure according to an embodiment of the present invention;

[0038] Figure 8 This is a flowchart of an Ethernet frame fixing method according to an embodiment of the present invention;

[0039] Figure 9 This is a schematic diagram of the Ethernet frame fixing device according to an embodiment of the present invention;

[0040] Figure 10 This is a schematic diagram of an Ethernet frame fixing device according to another embodiment of the present invention;

[0041] Figure 11 This is a schematic diagram of the Fg-BU frame locking and unlocking determination method according to Embodiment 1 of the present invention;

[0042] Figure 12 This is a schematic diagram of the Fg-BU frame locking and unlocking determination method according to Embodiment 2 of the present invention;

[0043] Figure 13 This is a schematic diagram of the Fg-BU frame locking and unlocking determination method according to Embodiment 3 of the present invention;

[0044] Figure 14 This is a schematic diagram of the Fg-BU multiframe locking and unlocking determination method according to Embodiment 4 of the present invention;

[0045] Figure 15 This is a schematic flowchart of the Fg-BU frame locking and unlocking determination method according to Embodiment 5 of the present invention. Detailed Implementation

[0046] The embodiments of the present invention will be described in detail below with reference to the accompanying drawings and examples.

[0047] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0048] The methods and embodiments provided in this application can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking running on a computer terminal as an example, Figure 7 This is a hardware structure block diagram of a computer terminal according to an embodiment of the present invention. Figure 7 As shown, a computer terminal may include one or more ( Figure 7 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The computer terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 7 The structure shown is for illustrative purposes only and does not limit the structure of the computer terminal described above. For example, the computer terminal may also include components that are more complex than those described above. Figure 7 The more or fewer components shown, or having the same Figure 7 The different configurations shown.

[0049] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the Ethernet frame fixing method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0050] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the computer terminal. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0051] This embodiment provides an Ethernet frame framing method that can run on the aforementioned computer terminal. Figure 8 This is a flowchart of an Ethernet frame framing method according to an embodiment of the present invention, such as... Figure 8 As shown, the process includes the following steps:

[0052] Step S802: The receiving end receives a data stream with fine-grained basic units Fg-BU;

[0053] Step S804: The receiving end determines whether the Fg-BU frame is locked or unlocked based on whether the Fg-BU frame in the data stream is normal.

[0054] In this embodiment, for the fine-grained basic unit (Fg-BU), the following four methods can be used to determine Fg-BU frame locking:

[0055] Method 1: The receiving end receives N consecutive normal Fg-BU frames (N is an integer greater than or equal to 1). The determination of a normal Fg-BU frame requires that the following two conditions be met simultaneously:

[0056] 1) The start (S) block is normal, meaning the 2-bit synchronization header and / or 8-bit block type value of the S block are normal. In this embodiment, the S block synchronization header and block type value are as follows: Figure 1 As shown.

[0057] 2) Each frame is h+2 blocks long (h is an integer greater than or equal to 1), including a start (S) block, h data (D) blocks, and an end (T) block. This is equivalent to verifying that the synchronization headers of the a data (D) blocks (a is an integer less than or equal to h and greater than or equal to zero), as well as the synchronization header and / or block type of the end (T) block, are all normal. In this embodiment, the data (D) block synchronization header is as follows... Figure 2 As shown. The end (T) block synchronization header and type value are as follows. Figure 3 As shown.

[0058] Method 2: The receiving end receives N consecutive normal Fg-BU frames (N is an integer greater than or equal to 1). The following conditions must be met to determine if an Fg-BU frame is normal:

[0059] The start (S) block is normal, meaning the 2-bit synchronization header and / or 8-bit block type value of the S block are normal. In this embodiment, the S block synchronization header and block type value are as follows: Figure 1 As shown. Alternatively, the CRC check in the Fg-BU frame overhead is correct, where the Fg-BU frame overhead format is as follows: Figure 6 As shown. Or the end (T) block is normal, that is, the 2-bit sync header and / or 8-bit block type value of the T block are normal.

[0060] Method 3: The receiving end receives N consecutive normal Fg-BU frames (N is an integer greater than or equal to 1). The determination that an Fg-BU frame is normal requires that the following two conditions be met simultaneously:

[0061] 1) The start (S) block is normal, meaning the 2-bit sync header and / or 8-bit block type value of the S block are normal. The S block sync header and block type values ​​are as follows: Figure 1 As shown. Alternatively, the CRC check in the Fg-BU frame overhead is correct, where the Fg-BU overhead format is as follows: Figure 6 As shown.

[0062] 2) Each frame is h+2 blocks long (h is an integer greater than or equal to 1), including a start (S) block, h data (D) blocks, and an end (T) block. This is equivalent to verifying p+r (where p and r are integers less than or equal to h and greater than or equal to zero, and p+r = h) 64B / 66B blocks after the start block (where for p data blocks, only the length of the synchronization header is checked to ensure it is p multiplied by 66 bits, and for r data blocks, the synchronization header is checked to ensure it is a data block), and that the synchronization header and / or block type of the end (T) block are normal. In this embodiment, the synchronization header and type values ​​of the end (T) block are as follows: Figure 3 As shown.

[0063] Method 4: The receiving end receives U+V consecutive normal Fg-BU frames (where U and V are integers greater than or equal to 0, and U+V=N). The determination that an Fg-BU frame is normal requires that the following three conditions be met simultaneously:

[0064] 1) U Fg-BU frames are normal: U start (S) blocks are normal, meaning the 2-bit sync header and / or 8-bit block type value of the S blocks are normal. The sync header and block type value of the S blocks are as follows: Figure 1 As shown.

[0065] 2) V Fg-BU frames are normal: The CRC check in the overhead of the V Fg-BU frames is correct. The Fg-BU overhead format is as follows: Figure 6 As shown.

[0066] 3) Each Fg-BU frame is h+2 blocks long (h is an integer greater than or equal to 1), including a start (S) block, h data (D) blocks, and an end (T) block. This is equivalent to verifying that the synchronization headers of a (a is an integer less than or equal to h and greater than or equal to zero) data (D) blocks, and that the synchronization header and / or block type of the end (T) block are all normal. In this embodiment, the data (D) block synchronization header is as follows... Figure 2 As shown. The end (T) block synchronization header and type value are as follows. Figure 3 As shown.

[0067] In this embodiment, after the receiving end determines that the Fg-BU frame is locked, the process may further include: the receiving end extracting the Fg-BU frame for processing.

[0068] In this embodiment, for fine-grained basic units (Fg-BU), the following method can be used to determine frame loss:

[0069] Method 1: M consecutive Fg-BU frames (M is an integer greater than or equal to 1) are abnormal, including: abnormal S blocks, i.e., the 2-bit synchronization header of the S block is incorrect and / or the 8-bit block type value is incorrect; or the Fg-BU length is not h+2 blocks. This is equivalent to checking b (b is an integer greater than or equal to zero and less than or equal to h) D block synchronization headers, and checking if any one of the synchronization header or block type of the T block is incorrect.

[0070] Method 2: M consecutive Fg-BU frames (M is an integer greater than or equal to 1) are abnormal, including: an abnormal S block, i.e., the 2-bit synchronization header of the S block is incorrect and / or the 8-bit block type value is incorrect; or the CRC check in the Fg-BU frame overhead is incorrect. The Fg-BU overhead format is as follows: Figure 6 As shown; or the length of Fg-BU is not h+2 blocks. That is, it is equivalent to checking b (b is an integer greater than or equal to zero and less than or equal to h) D block synchronization headers, and any one of the T block synchronization headers or T block types is incorrect.

[0071] Method 3: M consecutive Fg-BU frames (M is an integer greater than or equal to 1) are abnormal, including: E ​​S blocks (E is an integer greater than or equal to 0 and less than M) being abnormal, i.e., the 2-bit synchronization header of the S block is incorrect and / or the 8-bit block type value is incorrect; or F F F (F is an integer greater than or equal to 0 and less than M) Fg-BU frame overheads have incorrect CRC checks. The Fg-BU overhead format is as follows: Figure 6 As shown; or G (G is an integer greater than or equal to 0 and less than M) Fg-BU frames with a length not equal to h+2 (h is an integer greater than or equal to 1) blocks, which is equivalent to checking b (b is an integer less than or equal to h and greater than or equal to zero) data blocks (not checking whether the synchronization header is a data block, only checking whether the block length is b*66 bits), and whether any one of the synchronization header or type of block T is incorrect. Where E+F+G=M, M is an integer greater than or equal to 1.

[0072] In this embodiment, after the receiving end determines that the Fg-BU frame has lost its lock, it may further include: the receiving end reporting an alarm message indicating that the Fg-BU frame has lost its lock.

[0073] In this embodiment, after the receiving end determines that the Fg-BU frame is locked, it may further include: determining whether the multiframe is locked or unlocked based on the multiframe indicator MFI value. That is, given that the frame is already locked, the MFI (6 bits) is further checked.

[0074] In this embodiment, for fine-grained basic unit multiframes, the following method can be used to determine locking and unlocking:

[0075] If the MFI values ​​of X consecutive frames (where X is an integer greater than or equal to 1) are normal, that is, the MFI values ​​increase sequentially and conform to the MFI value range definition (such as 0-19, or other predefined ranges), then it is determined that the multiframe is locked; if the MFI values ​​of Y consecutive frames are abnormal, that is, the MFI values ​​do not increase sequentially, or do not conform to the MFI value range definition, then it is determined that the multiframe is unlocked.

[0076] In this embodiment, after the receiving end determines that the multiframe has lost lock, it may further include: the receiving end reporting alarm information for the multiframe loss.

[0077] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they 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 invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0078] This embodiment also provides an Ethernet frame fixing device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the terms "module" or "unit" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0079] Figure 9 This is a structural block diagram of an Ethernet frame fixing device according to an embodiment of the present invention, as shown below. Figure 9 As shown, the Ethernet frame fixing device is applied to the receiving end, and the device includes a receiving module 10 and a first judgment module 20.

[0080] The receiving module 10 is used to receive a data stream with fine-grained basic units Fg-BU.

[0081] The first judgment module 20 is used to determine whether the Fg-BU frame is locked or unlocked based on whether the Fg-BU frame in the data stream is normal.

[0082] Figure 10 This is a structural block diagram of an Ethernet frame fixing device according to another embodiment of the present invention, such as... Figure 10As shown, the device includes, in addition to Figure 9 In addition to all the modules shown, a second determination module 30 is also included. The second determination module 30 is used to determine whether the multiframe is locked or unlocked based on the multiframe indication MFI value when the Fg-BU frame is locked.

[0083] In this embodiment, the first judgment module 20 further includes a first judgment unit 21 and a second judgment unit 22.

[0084] The first judgment unit 21 is used to determine that the Fg-BU frame is locked when N consecutive normal Fg-BU frames are received, where N is an integer greater than or equal to 1.

[0085] The second judgment unit 22 is used to determine that the Fg-BU frame is out of lock when M consecutive abnormal Fg-BU frames are received, where M is an integer greater than or equal to 1.

[0086] In this embodiment, the second judgment module 30 may further include a third judgment unit 31 and a fourth judgment unit 32.

[0087] The third judgment unit 31 is used to determine the multiframe lock when the MFI values ​​of the received consecutive X frames are normal, where X is an integer greater than or equal to 1.

[0088] The fourth judgment unit 32 is used to determine that the multiframe is out of lock when the MFI value of the received consecutive Y frames is abnormal, where Y is an integer greater than or equal to 1.

[0089] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0090] To facilitate understanding of the technical solutions provided in the embodiments of the present invention, the following description will be based on specific scenarios.

[0091] Example 1

[0092] This embodiment provides a method for determining frame locking and unlocking at the fine-grained basic unit (Fg-BU) level. For example... Figure 11 As shown, the main steps include the following:

[0093] Step S1101: In Ethernet or a metro transport network (MTN) and a slicing packet network (SPN) based on Ethernet technology, the sending end transmits a data stream with fine-grained basic units (Fg-BU).

[0094] Step S1102: After receiving the data stream, the receiving end determines whether the Fg-BU frame is locked or unlocked.

[0095] In this embodiment, if the receiving end receives N consecutive normal Fg-BU frames (N is an integer greater than or equal to 1), it is determined that the Fg-BU frame is locked. The determination that the Fg-BU frame is normal is based on the following two conditions.

[0096] 1) The S-block is normal, including the 2-bit sync header and / or the 8-bit block type value. The S-block sync header and block type value are as follows: Figure 1 As shown.

[0097] 2) Each frame is h+2 blocks long (h is an integer greater than or equal to 1). This is equivalent to verifying the synchronization headers of h D blocks, and confirming that the synchronization headers and block types of the T blocks are normal. The synchronization header of the D blocks is as follows: Figure 2 As shown. The T-block synchronization header and type value are as follows. Figure 3 As shown.

[0098] In this embodiment, if the receiving end receives M consecutive (M is an integer greater than or equal to 1) abnormal Fg-BU frames, including: abnormal S blocks, i.e., the 2-bit synchronization header is incorrect or the 8-bit block type value is incorrect; or the length of the Fg-BU frame is not h+2 (h is an integer greater than or equal to 1), which is equivalent to checking h D block synchronization headers, and any one of the synchronization headers or T block types is incorrect, then it is determined that the Fg-BU frame is out of lock.

[0099] Step S1103: After the receiving end determines that the Fg-BU frame is locked, it extracts the Fg-BU frame for processing.

[0100] Step S1104: After the receiver determines that the Fg-BU has lost lock, it reports the corresponding alarm.

[0101] Example 2

[0102] This embodiment provides a method for determining frame locking and unlocking at the fine-grained basic unit (Fg-BU) level. For example... Figure 12 As shown, the main steps include the following:

[0103] Step S1201: In Ethernet or a Metro Transport Network (MTN) and Slicing Packet Network (SPN) based on Ethernet technology, the sending end transmits a data stream with fine-grained basic units (Fg-BU).

[0104] Step S1202: After receiving the data stream, the receiving end determines whether the Fg-BU frame is locked or unlocked.

[0105] In this embodiment, if the receiving end receives N consecutive normal Fg-BU frames (N is an integer greater than or equal to 1), it is determined that the Fg-BU frame is locked. The determination that the Fg-BU frame is normal is based on the following two conditions.

[0106] 1) The S-block is normal, including the 2-bit sync header and / or the 8-bit block type value. The S-block sync header and block type value are as follows: Figure 1 As shown.

[0107] 2) Each frame is h+2 blocks long (h is an integer greater than or equal to 1). This is equivalent to verifying that there are h 64B / 66B blocks after block S (without verifying whether the synchronization header is a data block), and that the synchronization header and / or block type of block T are normal. The synchronization header and type values ​​for block T are as follows: Figure 3 As shown.

[0108] In this embodiment, if the receiving end receives M consecutive (M is an integer greater than or equal to 1) abnormal Fg-BU frames, including: abnormal S block, i.e., the 2-bit synchronization header is incorrect and / or the 8-bit block type value is incorrect; or the Fg-BU length is not h+2 blocks, i.e., there are h 64B / 66B blocks after the S block (without checking whether its synchronization header is a data block); or the synchronization header or type value of the T block is incorrect, then it is determined that the Fg-BU frame is out of lock.

[0109] Step S1203: After the receiving end determines that the Fg-BU frame is locked, it extracts the Fg-BU frame for processing.

[0110] Step S1204: After the receiver determines that the Fg-BU has lost lock, it reports the corresponding alarm.

[0111] Example 3

[0112] This embodiment provides a method for locking and unlocking fine-grained basic unit (Fg-BU). For example... Figure 13 As shown, the main steps include the following:

[0113] Step S1301: The receiving end receives the Fg-BU frame;

[0114] Step S1302: If N consecutive Fg-BU frames are normal, then it is determined that the Fg-BU frame is locked. The determination that an Fg-BU frame is normal is based on the following two conditions:

[0115] 1) The S-block is normal, including the 2-bit sync header and / or the 8-bit block type value. (The S-block sync header and block type value, such as...) Figure 1 (as shown), or the CRC check in the Fg-BU frame overhead is correct (e.g. Figure 6 (As shown).

[0116] 2) Each frame is h+2 blocks long (h is an integer greater than or equal to 1), which is equivalent to verifying the synchronization headers of a (a is an integer greater than or equal to 0 and less than or equal to h) D blocks, and ensuring that the synchronization headers and block types of the T blocks are normal. The D block synchronization header is as follows: Figure 2 As shown. The T-block synchronization header and type value are as follows. Figure 3 As shown.

[0117] In step S1303, after the receiving end determines that the Fg-BU frame is locked, it extracts the Fg-BU frame for processing.

[0118] Step S1304: If the receiver receives M consecutive (M is an integer greater than or equal to 1) abnormal Fg-BU frames, including abnormal S blocks (i.e., the 2-bit synchronization header is incorrect, or the 8-bit block type value is incorrect); or the CRC checksum in the Fg-BU frame overhead (e.g., ...) is abnormal... Figure 6 If the Fg-BU frame is not correctly identified (as shown), or if the length of the Fg-BU is not h+2 blocks (equivalent to checking b D block synchronization headers, where b is an integer greater than or equal to 0 and less than or equal to h, and any one of the T block synchronization headers or T block types is incorrect), then the Fg-BU frame is considered to be out of lock.

[0119] In step S1305, after the receiving end determines that Fg-BU has lost lock, it reports the corresponding alarm.

[0120] Example 4

[0121] This embodiment provides a method for locking and unlocking multiple frames using fine-grained basic unit (Fg-BU). For example... Figure 14 As shown, the main steps include the following:

[0122] Step 1401: In an Ethernet or Ethernet-based MTN or SPN network, the transmitting end transmits a data stream with fine-grained basic units (Fg-BU).

[0123] Step S1402: After receiving the data stream, the receiving end determines whether the Fg-BU frame is locked, and then further determines whether the multiframe is locked or unlocked.

[0124] In this embodiment, if the receiving end receives X consecutive frames (X is an integer greater than or equal to 1) with normal MFI values, that is, the MFI values ​​increase sequentially and meet the definition of the MFI value range, then it is determined to be multiframe locking.

[0125] In step S1403, after the receiving end determines that the Fg-BU multiframe is locked, it extracts the Fg-BU multiframe for processing.

[0126] In this embodiment, if the receiving end receives consecutive Y frames with abnormal MFI values, that is, the MFI values ​​do not increase sequentially or do not conform to the definition of the MFI value range, it is determined that the multiframe is out of lock.

[0127] In step S1404, after the receiving end determines that the Fg-BU multiframe has lost lock, it reports a multiframe loss alarm.

[0128] Example 5

[0129] This embodiment provides a method for locking and unlocking fine-grained basic unit (Fg-BU). For example... Figure 15 As shown, the main steps include the following:

[0130] Step S1501: The receiving end receives the Fg-BU frame;

[0131] Step S1502: If N consecutive Fg-BU frames are normal, then determine that the Fg-BU frame is locked. The determination that an Fg-BU frame is normal is based on the following condition:

[0132] The start (S) block is normal, meaning the 2-bit synchronization header and / or 8-bit block type value of the S block are normal. In this embodiment, the S block synchronization header and block type value are as follows: Figure 1 As shown. Alternatively, the CRC check in the Fg-BU frame overhead is correct, where the Fg-BU frame overhead format is as follows: Figure 6 As shown. Alternatively, the end (T) block is normal, meaning the 2-bit sync header and / or 8-bit block type value of the T block are normal. The T block format is as follows: Figure 3 As shown.

[0133] In step S1503, after the receiving end determines that the Fg-BU frame is locked, it extracts the Fg-BU frame for processing.

[0134] Step S1504: If the receiving end receives M consecutive (M is an integer greater than or equal to 1) abnormal Fg-BU frames, including abnormal S blocks (i.e., the 2-bit synchronization header is incorrect, or the 8-bit block type value is incorrect); or the CRC checksum in the Fg-BU frame overhead (e.g., ...) is abnormal... Figure 6 If the following conditions are met: (as shown) is incorrect; or (either the synchronization header or the type of the T block is incorrect), then the Fg-BU frame is considered to be out of lock.

[0135] In step S1505, after the receiving end determines that Fg-BU has lost lock, it reports the corresponding alarm.

[0136] Embodiments of the present invention also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to perform the steps in any of the above method embodiments when executed.

[0137] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0138] Embodiments of the present invention also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0139] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0140] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0141] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those described herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0142] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for Ethernet frame fixing, characterized in that, include: The receiving end receives a data stream with fine-grained basic units (Fg-BU). The receiving end determines whether the Fg-BU frame is locked or unlocked based on whether the Fg-BU frame in the data stream is normal. An Fg-BU frame is considered normal when it meets one or more of the following conditions: the start block of the Fg-BU frame is normal; the CRC check in the overhead of the Fg-BU frame is correct; the end block of the Fg-BU frame is normal; a data blocks of the Fg-BU frame are normal, where a is an integer greater than or equal to 0; and the length of the Fg-BU frame is the set number of blocks.

2. The method according to claim 1, characterized in that, The receiving end determines whether the Fg-BU frame is locked based on whether the Fg-BU frame in the data stream is normal, including: If the receiving end receives N consecutive normal Fg-BU frames, it determines that the Fg-BU frames are locked, where N is an integer greater than or equal to 1.

3. The method according to claim 1, characterized in that, The receiving end determines whether the Fg-BU frame is out of lock based on whether the Fg-BU frame in the data stream is normal, including: If the receiving end receives M consecutive abnormal Fg-BU frames, it is determined that the Fg-BU frames are out of lock, where M is an integer greater than or equal to 1.

4. The method according to claim 3, characterized in that, in, The Fg-BU frame is considered abnormal when it meets one or more of the following conditions: The start code block of the Fg-BU frame is abnormal; The end code block of the Fg-BU frame is abnormal; The CRC check in the Fg-BU frame overhead is incorrect; The Fg-BU frame has b data code blocks that are abnormal, where b is an integer greater than or equal to 0; The length of the Fg-BU frame is not the set number of code blocks.

5. The method according to claim 2, characterized in that, After the receiving end determines that the Fg-BU frame is locked, it also includes: The receiving end extracts the Fg-BU frame for processing.

6. The method according to claim 3, characterized in that, After the receiving end determines that the Fg-BU frame has lost lock, it also includes: The receiving end reports an alarm message indicating that the Fg-BU frame has lost lock.

7. The method according to claim 2, characterized in that, After the receiving end determines that the Fg-BU frame is locked, it also includes: The receiving end determines whether the Fg-BU multiframe is locked or unlocked based on the multiframe indication MFI value.

8. The method according to claim 7, characterized in that, The receiver determines Fg-BU multiframe locking based on the multiframe indication MFI value, including: If the MFI values ​​of X consecutive Fg-BU frames received by the receiving end are normal, then it is determined that the Fg-BU multiframe is locked, where X is an integer greater than or equal to 1.

9. The method according to claim 2, characterized in that, The receiver determines Fg-BU multiframe lock loss based on the multiframe indication (MFI) value, including: If the MFI value of Y consecutive Fg-BU frames received by the receiving end is abnormal, it is determined that the Fg-BU multiframe is out of lock, where Y is an integer greater than or equal to 1.

10. The method according to claim 8, characterized in that, After the receiving end determines that the Fg-BU multiframe is locked, it also includes: The receiving end extracts the Fg-BU multiframe and processes it.

11. The method according to claim 9, characterized in that, After the receiving end determines that the multiframe is out of lock, it also includes: The receiving end reports an alarm message indicating that the multiframe has lost lock.

12. An Ethernet frame fixing device, applied at a receiving end, characterized in that, include: The receiving module is used to receive data streams with fine-grained basic units (Fg-BU). The first judgment module is used to determine whether the Fg-BU frame is locked or unlocked based on whether the Fg-BU frame in the data stream is normal. The Fg-BU frame is normal when it meets one or more of the following conditions: the start code block of the Fg-BU frame is normal; the CRC check in the overhead of the Fg-BU frame is correct; the end code block of the Fg-BU frame is normal; a data code blocks of the Fg-BU frame are normal, where a is an integer greater than or equal to 0; and the length of the Fg-BU frame is a set number of code blocks.

13. The apparatus according to claim 12, characterized in that, The first judgment module includes: The first judgment unit is used to determine that the Fg-BU frame is locked when N consecutive normal Fg-BU frames are received, where N is an integer greater than or equal to 1.

14. The apparatus according to claim 12, characterized in that, The first judgment module includes: The second judgment unit is used to determine that the Fg-BU frame is out of lock when M consecutive abnormal Fg-BU frames are received, where M is an integer greater than or equal to 1.

15. The apparatus according to claim 12, characterized in that, Also includes: The second judgment module is used to determine whether the Fg-BU multiframe is locked or unlocked based on the multiframe indication MFI value when the Fg-BU frame is locked.

16. The apparatus according to claim 15, characterized in that, The second judgment module includes: The third judgment unit is used to determine that the Fg-BU multiframe is locked if the MFI value of X consecutive Fg-BU frames is normal, where X is an integer greater than or equal to 1.

17. The apparatus according to claim 15, characterized in that, The second judgment module includes: The fourth judgment unit is used to determine that the Fg-BU multiframe is out of lock when the MFI value of Y consecutive Fg-BU frames is abnormal, where Y is an integer greater than or equal to 1.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 11.

19. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 11.

Images