Slicing method, service processing method, communication node and storage medium

Abstract

The application provides a slicing method, a service processing method, a communication node and a storage medium. The method comprises the following steps: obtaining a physical layer to be sliced; slicing the physical layer to be sliced to obtain a target frame slice; the target frame slice comprises a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but without a fixed frame structure.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and for example to a slicing method, a service processing method, a communication node, and a storage medium. Background Technology

[0002] The network for integrated services will cover tens of millions of industries. The network requirements of various services are very different. The network needs end-to-end slicing to ensure the differentiated carrying of services. Many new industries also need to be isolated through network slicing.

[0003] Slicing Packet Network (SPN) / Metro Transport Network (MTN) uses Flexible Ethernet (FlexE) as its service layer, implementing a rigid end-to-end service pipeline. It further refines time-slot bandwidth to a minimum granularity of 10 Mb / s using fine-grained time-slotting technology. However, current methods for carrying packet services using fine-grained technology, regardless of whether hard isolation is required, necessitate encapsulation and mapping into fine-grained data frame structures for transmission. This results in numerous encapsulation layers and low bandwidth utilization. Summary of the Invention

[0004] This application provides a slicing method, a service processing method, a communication node, and a storage medium.

[0005] This application provides a slicing method, including:

[0006] Obtain the physical layer to be sliced;

[0007] The physical layer to be sliced ​​is sliced ​​to obtain a target frame slice; the target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure.

[0008] This application also provides a business processing method, including:

[0009] Obtain business data;

[0010] A business data stream is generated based on the aforementioned business data;

[0011] The service data stream is mapped to a frame slice of at least one target frame slice; the target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure.

[0012] This application also provides a communication node, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the above-described slicing method or business processing method.

[0013] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described slicing method or business processing method. Attached Figure Description

[0014] Figure 1 A flowchart of a slicing method provided in one embodiment;

[0015] Figure 2 A schematic diagram of the frame structure of a target frame slice provided in one embodiment;

[0016] Figure 3 A schematic diagram of the frame structure of another target frame slice provided in one embodiment.

[0017] Figure 4 A schematic diagram of the frame structure of a first frame slice provided in one embodiment;

[0018] Figure 5 A schematic diagram illustrating a 64B / 66B coded block format conforming to IEEE 802.3, provided as an embodiment;

[0019] Figure 6 A schematic diagram of the frame structure of a sub-slice frame provided in one embodiment;

[0020] Figure 7 A schematic diagram of the frame structure for the slice overhead of a target frame slice is provided in one embodiment;

[0021] Figure 8 A schematic diagram of a service layer for a target frame slice provided in one embodiment;

[0022] Figure 9 This is a schematic diagram of a target frame slice that does not include slicing overhead, provided as an embodiment.

[0023] Figure 10 A schematic diagram of the frame structure of another sub-slice frame provided in one embodiment;

[0024] Figure 11 A schematic diagram of the structure of a sub-slice frame overhead provided in one embodiment;

[0025] Figure 12 A schematic diagram of a frame structure including slicing overhead for a target frame slice is provided as an embodiment;

[0026] Figure 13 A schematic diagram of the slicing overhead of another target frame slice provided in one embodiment;

[0027] Figure 14 A schematic diagram of the frame structure of a second frame slice provided in one embodiment;

[0028] Figure 15 This is a schematic diagram of the structure of a target frame slice in which the first frame slice and the second frame slice are interleaved, as provided in one embodiment.

[0029] Figure 16 A flowchart of a business processing method provided in one embodiment;

[0030] Figure 17 A schematic diagram illustrating the principle of a business processing method provided in one embodiment;

[0031] Figure 18 A schematic diagram of a slicing device provided in one embodiment;

[0032] Figure 19 A schematic diagram of the structure of a service processing apparatus provided in one embodiment;

[0033] Figure 20 This is a schematic diagram of the hardware structure of a communication node provided in one embodiment. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be arbitrarily combined with each other.

[0035] The steps illustrated in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases the steps shown or described may be performed in a different order than that presented here.

[0036] To effectively isolate business data and meet the differentiated Service-Level Agreement (SLA) requirements of various services, Virtual Private Network (VPN) technology was proposed. VPN technology is a simple solution for fragmenting a bearer network, but it struggles to perfectly resolve bandwidth contention issues between different services and cannot guarantee SLAs for different services. Many data center networks employ Jumbo Frame technology to improve bandwidth utilization, but this also exacerbates packet scheduling wait times between fragments, impacting the SLA provisioning capabilities of other fragments.

[0037] Currently, Flexible Ethernet (FlexE) provides a general mechanism for transmitting a range of services with different Media Access Control (MAC) rates. This can be a single service with a relatively high MAC rate or a collection of services with relatively low MAC rates, no longer limited to services with a single MAC rate. However, the FlexE standard supports a customer service granularity of N×5Gb / s (N≧1), meaning the minimum customer service granularity it can carry is 5Gb / s. It does not support hard isolation or rigid pipes for services smaller than 5Gb / s.

[0038] SPN and MTN use FlexE as the service layer, implementing a rigid end-to-end service pipeline. Fine-grained technology further segments the SPN / MTN path layer channel or 10GE Ethernet interface into time slots, refining the fine-grained time slot bandwidth to a minimum granularity of 10Mb / s for carrying packet services. However, this service carrying method, regardless of whether hard isolation is required, needs to be encapsulated and mapped into a fine-grained frame structure for transmission, resulting in multiple encapsulation layers and low bandwidth utilization.

[0039] To solve the above technical problems, Figure 1 A flowchart of a slicing method provided in one embodiment, such as Figure 1 As shown, the method provided in this embodiment includes steps 110 and 120.

[0040] In step 110, the physical layer to be sliced ​​is obtained.

[0041] In this embodiment, the physical layer to be sliced ​​can be understood as the physical layer waiting to be sliced, such as the physical control sublayer (PCS) of Ethernet. The role of the PCS is to provide a data path for communication nodes (or terminal devices) to transmit data. The data path can be a single physical medium or a combination of multiple physical media. The physical layer to be sliced ​​can conform to a preset specification, such as the IEEE 802.3 PCS layer 64B / 66B specification.

[0042] In step 120, the physical layer to be sliced ​​is sliced ​​to obtain the target frame slice; the target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure.

[0043] In this embodiment, the target frame slice can be understood as a frame slice of fixed length formed after the physical layer to be sliced ​​has been sliced. The target frame slice includes slices with fixed frame structure and slices without fixed frame structure, which can be flexibly set according to business needs. Therefore, the target frame slice can also be regarded as a fixed-length frame structure with flexible slicing capability, that is, a flexible frame slice (FFS). In this embodiment, FFS can be used to represent the target frame slice.

[0044] Figure 2 This is a schematic diagram of the frame structure of a target frame slice provided in one embodiment. For example... Figure 2 As shown, the target frame slice (FFS) includes a first frame slice and a second frame slice. The first frame slice refers to a slice with a fixed length and fixed frame structure, which can be considered a constant frame slice (CFS) that implements rigid hard pipes. In this embodiment, CFS can be used to represent the first frame slice. The first frame slice (CFS) can be further divided into multiple time slots to carry different services, thereby providing rigid hard pipes and hard isolation for customer services, which can meet the service requirements of low latency, low jitter, and hard isolation.

[0045] The second frame slice refers to a slice with a fixed length but no fixed frame structure. For example, it can be a Packet Stream Slice (PSS) that implements a flexible packet pipeline. In this embodiment, PSS can be used to represent the second frame slice. The second frame slice PSS does not require re-encapsulation of service data and can directly carry packet services, simplifying the service encapsulation process, improving bandwidth utilization, and overcoming the problems of multiple encapsulation layers and low bandwidth utilization in methods based on fine-grained techniques for carrying packet services. It can meet the needs of flexible, adaptable, and highly utilized services.

[0046] in addition, Figure 3 This is a schematic diagram of the frame structure of another target frame slice provided in one embodiment. For example... Figure 3 As shown, the target frame slice FFS includes, in addition to the first frame slice CFS and the second frame slice PSS, the slice overhead OH_FFS.

[0047] In this embodiment, both the first frame slice and the second frame slice can be constructed based on 64 / 66B coded blocks of the PCS layer. The PCS layer can conform to a preset specification, such as IEEE 802.3. The length of the first frame slice is N1 coded blocks, the length of the second frame slice is N2 coded blocks, and the length of the target frame slice is N1+N2 coded blocks.

[0048] The bandwidth allocation ratio between the first frame slice and the second frame slice at the physical layer can be flexibly adjusted according to service requirements; this embodiment does not impose any restrictions on this. The slicing method for the target frame slice obtained by slicing the physical layer of the slice to be sliced ​​can be any slicing method, and the resulting target frame slice can have a certain distribution structure. No limitations are imposed here on the slicing method or the distribution structure of the target frame slice.

[0049] This embodiment achieves slicing and hard isolation of rigid hard pipes and flexible packet pipes by slicing the physical layer to be sliced ​​into a first frame slice with a fixed length and a fixed frame structure and a second frame slice with a fixed length but no fixed frame structure. This can meet different service requirements and make up for the problems of multiple encapsulation layers and low bandwidth utilization in the method of carrying packet services based on fine-grained technology.

[0050] In one embodiment, the distribution structure of the target frame slice includes: a region-based sequential distribution structure or an interleaved distribution structure.

[0051] In this embodiment, the region-based sequential distribution structure means that the first and second frame slices of the target frame are sequentially distributed in two different regions of the physical layer. The physical layer is divided into a first region and a second region, with the first frame slice distributed in the first region and the second frame slice distributed in the second region.

[0052] Interleaved distribution structure refers to the interleaved distribution of sub-slices between the first frame slice and the second frame slice. The first frame slice may include i sub-slicing frames (SSF), denoted as SSF1 to SSFi. The second frame slice is then divided into sub-slices with the same number of sub-slicing frames as the first frame slice, namely Sub-PSS1 to Sub-PSSi. One sub-slice is interleaved after each sub-slicing frame SSF, forming an interleaved distribution structure of SSF1, Sub-PSS1, SSF2, Sub-PSS2, ..., SSF1, Sub-PSSi.

[0053] In one embodiment, the first frame slice is composed of multiple sub-slice frames with the same frame structure and the same length.

[0054] In this embodiment, the first frame slice CFS is composed of multiple consecutive sub-slice frames SSF, and each sub-slice frame SSF has the same frame structure and the same length. Figure 4 This is a schematic diagram of the frame structure of a first frame slice provided in one embodiment. For example... Figure 4 As shown, the number of sub-slice frames SSF included in the first frame slice is Num_SSF. Num_SSF is configurable. Each SSF frame has a length of L coding blocks. Therefore, the length of the first frame slice is N1 = Num_SSF × L.

[0055] In one embodiment, the frame structure of the first frame slice includes: a single frame structure or a multi-frame structure.

[0056] In this embodiment, the sub-slice frames SSF contained in the first frame slice with a single frame structure have the same frame structure, that is, they include the same sub-slice frame overhead OH_SSF and time slots; the sub-slice frames SSF contained in the first frame slice with a multi-frame structure have different frame structures, for example, they may contain different time slots.

[0057] In one embodiment, slicing the physical layer to be sliced ​​to obtain a target frame slice further includes:

[0058] At least one free block is inserted between two adjacent sub-slice frames; the free block is a 64B / 66B encoded block conforming to a preset specification;

[0059] The data transmission rate of the first frame slice is adjusted by adjusting the number of free blocks.

[0060] In this embodiment, after slicing the physical layer to be sliced ​​into multiple sub-slice frames, one or more idle blocks can be inserted between two adjacent sub-slice frames. The block type of the idle block can be 0x1E. The number of idle blocks can be increased or decreased, and the data transmission rate of the first frame slice can be adjusted by adjusting the number of idle blocks.

[0061] In one embodiment, the sub-slice frame adopts a first data block format; the first data block format includes: a start block, at least one data block, and an end block;

[0062] The start block, data block, and end block are all 64B / 66B encoded blocks that conform to the preset specifications.

[0063] In this embodiment, the sub-slice frame SSF adopts a first data code block format composed of multiple coded blocks. For example... Figure 4 As shown, the coded block includes a start block (S block), at least one data block (D block), and a termination block (T block). The S block, D block, and T block can all be 64B / 66B coded blocks conforming to a preset specification, which can be the IEEE 802.3 PCS layer 64B / 66B specification.

[0064] Figure 5 This is a schematic diagram illustrating a 64B / 66B coded block format conforming to IEEE 802.3, provided as an embodiment. Figure 5As shown, the first two bits of block 66B are the synchronization header, used to distinguish between control blocks and data blocks. 10 indicates a control block, and 01 indicates a data block. S-blocks and T-blocks belong to control blocks, while D-blocks are data blocks. For control blocks, the first byte after the synchronization header (i.e., sync is 10) indicates the block type. The first block of the sub-slice frame SSF (i.e., S-block) has a block type of 0x78, and the last block of the SSF frame (i.e., T-block) has a block type of 0xFF.

[0065] In one embodiment, the sub-slice frame includes, but is not limited to, sub-slice frame overhead and payload; the payload includes, a plurality of time slots of the same size arranged according to a preset arrangement.

[0066] In this embodiment, the sub-slice frame includes, but is not limited to, the sub-slice frame overhead (OH_SSF) and the payload. The payload includes multiple time slots of the same size arranged according to a preset arrangement, with each time slot serving as a basic physical channel for carrying service mapping. By dividing the payload of the sub-slice frame SSF into multiple time slots of the same size (i.e., fixed-length time slot division), fixed-rate bandwidth and rigid isolation of the time slots can be achieved.

[0067] Figure 6 This is a schematic diagram of the frame structure of a sub-slice frame provided in one embodiment. For example... Figure 6 As shown, the payload of the sub-slice frame SSF is divided into m time slots, each of the same size (Sizeofslot(bit)). These time slots are arranged sequentially within the payload area of ​​the SSF according to a preset arrangement. The D and T blocks of the sub-slice frame SSF are used to carry the payload and sub-slice frame overhead. Different types of services are mapped to the data areas of the D and T blocks using corresponding mapping methods. A portion of the data area can also be used for overhead.

[0068] In one embodiment, the preset arrangement includes: a sequential arrangement or an interleaved arrangement.

[0069] In this embodiment, the sequential arrangement means that the time slot numbers corresponding to the m time slots, slot 1 to slot m, are arranged sequentially in the payload, such as slot 1, slot 2, slot 3, slot 4, ..., slot m-1, slot m. The interleaved arrangement means that the time slot numbers corresponding to the m time slots, slot 1 to slot m, are interleaved in the payload, such as slot 1, slot 3, slot 2, slot 4, ..., slot m-2, slot m.

[0070] In one embodiment, the size of the time slot is an integer multiple of the size of the service data packet, and the service data packet is a 66-bit service data encoded block or a compressed 65-bit service data encoded block.

[0071] In this embodiment, the size of the time slot can be an integer multiple (i.e., n times, where n is a positive integer) of the service data packet to facilitate service mapping. The service data packet is a 66-bit service data encoded block or a compressed 65-bit service data encoded block. For example, if the 64B / 66B encoded service data packet is directly mapped to the time slot, then the time slot size Sizeofslot = n × 66 bits is selected; if the service data packet is mapped to the time slot after 64B / 65B compression encoding, then the time slot size Sizeofslot = n × 65 bits is selected, or other specifications are used.

[0072] In one embodiment, it further includes:

[0073] A time slot channel is constituted according to at least one of the time slots;

[0074] Different time slot channels are used to carry different service data packets.

[0075] In this embodiment, one or more time slots can form time slot channels with different bandwidths to carry end-to-end services, and different time slot channels carry different services.

[0076] In one embodiment, slicing the data frame to obtain a target frame slice includes:

[0077] Configure the bytes occupied by the sub-slice frame overhead;

[0078] The bytes occupied by the sub-slice frame overhead include at least one of the following:

[0079] The first preset byte in the start block, the data area in the data block, and the data area in the end block.

[0080] In this embodiment, the sub-slice frame overhead OH_SSF can be extended using the first preset bytes of the S block (e.g., bytes D1 to D7), or a portion of the data area of ​​the D block (e.g., using the first D block to store the overhead), or the data area of ​​the T block. If the overhead requires more bits, one or more of the following can be used simultaneously: bytes D1 to D7 of the S block, the data area of ​​the D block, and the data area of ​​the T block. The data areas of the D block and the T block are part of the payload; therefore, the occupancy bytes of the sub-slice frame overhead can be set through configuration information, allowing the sub-slice frame overhead OH_SSF to be extended to the payload.

[0081] In one embodiment, where the target frame slice does not include slice overhead, the first frame feature information of the first frame slice is used as the frame header of the target frame slice.

[0082] In this embodiment, if the target frame slice includes a first frame slice and a second frame slice, but does not include the slice overhead, that is, when the target frame slice has a simplified structure, the target frame slice can use the first frame feature information of the first frame slice as the frame header.

[0083] In one embodiment, the second frame slice adopts the second data code block format and directly carries the service data packet formed by 64B / 66B encoding;

[0084] The second data block format includes: a sequence of service data packets consisting of a start block, at least one data block, and a stop block, as well as free blocks between the service data packets;

[0085] The start block, the data block, the end block, and the free block are all 64B / 66B encoded blocks that conform to a preset specification.

[0086] In one embodiment, the target frame slice further includes slice overhead.

[0087] In one embodiment, the data code block format used for the slice overhead includes:

[0088] Third data block format, or fourth data block format;

[0089] The third data block format includes: a start block and a stop block;

[0090] The fourth data block format includes: a start block, a data block, and a stop block.

[0091] In this embodiment, the slicing overhead can adopt the fourth data block format (i.e., the fixed-length S-block + D-block + T-block data block format), and all data blocks conform to the IEEE 802.3 PCS layer 64 / 66B encoding specification.

[0092] Figure 7 This is a schematic diagram of the frame structure for the slice overhead of a target frame slice, provided as an embodiment. For example... Figure 7 As shown, the slicing overhead can also be simplified to the third data block format (i.e., the data block format of S block + T block).

[0093] In one embodiment, when the data code block format of the slice overhead is a first data code block format, the slice overhead serves as the frame header of the target frame slice.

[0094] In one embodiment, the service layer of the target frame slice includes at least one of the following:

[0095] The slice channel layer of SPN, the channel layer of MTN, Flexible Ethernet (FlexE), Ethernet physical layer, and Optical Transmission Network (OTN).

[0096] In this embodiment, Figure 8 This is a schematic diagram of a service layer for a target frame slice provided in one embodiment. For example... Figure 8 As shown, the service layer of the target frame slice can be the Slicing Channel Layer (SCL) of a Slicing Packet Network (SPN), the Path Layer of a Metro Transport Network (MTN), FlexE, the Ethernet Port Physical Layer (PHY), such as IEEE 802.3 PHY, or the Optical Transport Network (OTN).

[0097] The following examples illustrate how to obtain target frame slices using a slicing method.

[0098] Figure 9 This is a schematic diagram of a target frame slice that does not include slicing overhead, provided as an embodiment. Taking an Ethernet port as an example, as... Figure 9 As shown, the target frame slice FFS has a length of 19,800 66B coded blocks, of which the first frame slice CFS has a length of 3,960 66B coded blocks and the second frame slice PSS has a length of 15,840 66B coded blocks. The first frame slice CFS includes 20 sub-slice frames SSF, and each sub-slice frame SSF includes 197 66B coded blocks consisting of 1 S block, 195 D blocks, and 1 T7 block.

[0099] Figure 10 This is a schematic diagram of the frame structure of another sub-slice frame provided in one embodiment. For example... Figure 10 As shown, the first 7 bytes of the first D block are the sub-slice frame overhead (OH_SSF), and the data areas of the other D blocks and the T7 block belong to the payload. The payload is divided into 24 time slots, each time slot being 65 bytes (65×8 bits) long. Therefore, the first frame slice CFS contains a total of 480 (20×24) time slots.

[0100] For a 10GE Ethernet port, the rate of each slot in the sub-slice frame SSF of the first frame slice CFS is:

[0101] Rateofslot=(Sizeofslot / SizeofFFS)×Rateofserver×Encapsu

[0102] =(65×8 / ((2+3960+3958)×66bit))×10312.5Mb / s×64 / 65

[0103] =10.1Mb / s

[0104] The channel rate of the second frame slice PSS is:

[0105] RateofPSS=(SizeofPSS / SizeofFFS)×Rateofserver×Encapsu

[0106] =(3958×66bit / ((2+3960+3958)×66bit))×10.3125Gb / s×64 / 66

[0107] = 4.9975Gb / s

[0108] For a 25GE Ethernet port, the rate of each slot in the sub-slice frame SSF of the first frame slice CFS is:

[0109] Rateofslot=(Sizeofslot / SizeofFFS)×Rateofserver×Encapsu

[0110] =(65×8 / ((3960+15840)×66bit))×25781.25Mb / s×64 / 65

[0111] =10.1Mb / s

[0112] The channel rate of the second frame slice PSS is:

[0113] RateofPSS=(SizeofPSS / SizeofFFS)×Rateofserver×Encapsu

[0114] =(15840×66bit / ((3960+15840)×66bit))×25.78125Gb / s×64 / 66

[0115] =20Gb / s

[0116] Wherein, Encapsu is the efficiency of client encapsulation mapping to time slots. If the service data is compressed and encoded using the 64B / 65B encoding standard and then mapped to time slots, then Encapsu = 64 / 65; if the service data is encoded using the 64B / 66B encoding standard and then mapped to time slots, then Encapsu = 64 / 66; Rateofslot is the time slot rate; RateofPSS is the channel rate of the second frame slice PSS; Rateofserver is the service layer channel rate; SizeofPSS is the length of the second frame slice; Sizeofslot is the length of the time slot; SizeofFFS is the length of the target frame slice FFS.

[0117] Figure 11 This is a schematic diagram illustrating the structure of a sub-slice frame overhead according to one embodiment. For example... Figure 11 As shown, the first frame slice (CFS) in this embodiment is a slice with 20 multiframes. The sub-slice frame overhead (OH_SSF) of the sub-slice frame (SSF) of the first frame slice (CFS) has 7 bytes. The fields of the sub-slice frame overhead (OH_SSF) are as follows: Multiframe Indicator (MFI) (6 bits), indicating the sequence number of the sub-slice frame (SSF) in the multiframe of the first frame slice (CFS), incrementing from 0 and cycling. The MFI value corresponding to the first frame slice (CFS) with 20 multiframes is 0 to 19. OH Information (41 bits) indicates the overhead information defined as needed, such as indicating the relationship between time slots and customer services. CRC7 (7 bits): generated by performing CRC7 checksum calculation on the overhead information (OH Information) part (41 bits). RES (2 bits): reserved, all 0s.

[0118] Figure 12 This is a schematic diagram of a frame structure for a target frame slice, including slicing overhead, provided as an embodiment. Taking a 10GE Ethernet port as an example, as... Figure 12 As shown, the target frame slice FFS has a length of 7920 66B blocks, the first frame slice CFS has a length of 3960 66B blocks, the second frame slice PSS has a length of 3958 66B blocks, and the slice overhead OH_FFS has a length of 2 66B blocks. The first frame slice CFS is a multiframe composed of 20 sub-slice frames SSF, each of which has a length of 197 66B blocks. There is one idle block between adjacent sub-slice frames.

[0119] Figure 13 This is a schematic diagram illustrating the structure of the slice overhead for another target frame slice provided in one embodiment. For example... Figure 13As shown, the slice overhead OH_FFS of the target frame slice consists of S blocks and T blocks. The overhead content occupies 7 data bytes in the T block, and the fields are described as follows: FSF_MFI (8 bits): FFS multiframe indicator. For target frame slices with multiframe structure, this indicator represents the multiframe sequence number of the target frame slice, incrementing from 0 and cycling through the frame, ranging from 0 to 255. Num_SSF (8 bits): Number of sub-slice frame SSFs. Indicates the number of sub-slice frames contained in the target frame slice. Num_SSF can be configured through the network management system. GCC channel (32 bits): Used for transmitting management information, etc. RES (1 bit): Reserved, all 0s. CRC7 (7 bits): Generated by performing CRC7 checksum calculation on the overhead content (41 bits) of Num_SSF, GCC, and RES.

[0120] Figure 14 This is a schematic diagram of the frame structure of a second frame slice provided in one embodiment. For example... Figure 14 As shown, the second frame slice PSS includes: multiple packets, each packet adopting the second data block format, the second data block format including: a sequence of service data packets consisting of a start block S block, at least one data block D block and a stop block T block, and an idle block I block between service data packets.

[0121] Figure 15 This is a schematic diagram illustrating the structure of a target frame slice where the first frame slice and the second frame slice are interleaved, as provided in one embodiment. Taking a 5Gbps path channel of SPN as an example, as... Figure 15 As shown, the length of the target frame slice FFS is 3960 66B blocks, of which the length of the first frame slice CFS is 1980 66B blocks, and the length of the second frame slice PSS is 1980 66B blocks. In this embodiment, the first frame slice CFS is a multiframe composed of 10 sub-slice frames SSF, each of which is 197 66B blocks long, followed by one idle block. The frame structure of the sub-slice frames SSF of the first frame slice is the same as in the first embodiment above. The second frame slice PSS is divided into 10 PSS sub-slices, the same number (10) of SSF frames contained in the first frame slice CFS, denoted as sub-PSS 1 to sub-PSS 10. Then, a PSS sub-slice is interspersed after each SSF frame, forming an interspersed structure of SSF 1, sub-PSS 1, SSF 2, sub-PSS 2, ... SSF 10, sub-PSS 10.

[0122] For the 5Gbps channel of SPN, the first frame slice CFS is a multiframe consisting of 10 SSF frames, containing a total of 240 time slots, with each time slot having a rate of:

[0123] Rateofslot=(Sizeofslot / SizeofFSF)×Rateofserver×Encapsu

[0124] =(65×8 / ((1980+1980)×66bit))×5156.25Mb / s×64 / 65

[0125] =10.1Mb / s

[0126] For the 5Gbps channel of SPN, the channel rate of the second frame slice PSS is:

[0127] RateofPSS=(SizeofPSS / SizeofFSF)×Rateofserver×Encapsu

[0128] =(1980×66bit / ((1980+1980)×66bit))×5.15625Gb / s×64 / 66

[0129] =2.5Gb / s

[0130] =20Gb / s

[0131] Where, Encapsu = 64 / 65 indicates that the service data is compressed and encoded using the 64B / 65B encoding standard and then mapped to the time slot; Encapsu = 64 / 66 indicates that the service data is encoded using the 64B / 66B encoding standard and then mapped to the time slot; Rateofslot is the rate of the time slot; RateofPSS is the channel rate of the second frame slice PSS; Rateofserver is the rate of the service layer; SizeofPSS is the length of the second frame slice; Sizeofslot is the length of the time slot; SizeofFFS is the length of the target frame slice FFS.

[0132] Figure 16 A flowchart of a business processing method provided in one embodiment, such as Figure 16 As shown, the method provided in this embodiment includes steps 210, 220 and 230.

[0133] In step 210, business data is obtained.

[0134] In this embodiment, the type of service data can be Ethernet service, ordinary Ethernet service, or time division multiplexing (TDM) service with a fixed rate; there is no limitation on the type of service data here.

[0135] In step 220, the service data is encoded to form a service data bitstream.

[0136] In this embodiment, service data is encoded to obtain service data packets, and multiple service data packets form a service data stream. For example, Ethernet services client A and client B, after being encoded using IEEE 802.3 PCS, form a 64B / 66B block stream.

[0137] In step 230, the service data stream is mapped to at least one target frame slice; the target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure.

[0138] In this embodiment, the target frame slice includes a first frame slice and a second frame slice. Service data streams can be mapped to either the first or second frame slice of at least one target frame slice according to different customer service requirements. The first frame slice is a slice with a fixed length and fixed frame structure, providing rigid hard pipes and hard isolation for customer services. Therefore, the first frame slice can be used to carry Ethernet services or TDM services that require rigid hard pipes. The second frame slice is a slice with a fixed length but no fixed frame structure, and can be used to carry ordinary Ethernet services that do not require rigid hard pipes.

[0139] This embodiment uses a first frame slice with a fixed length and fixed frame structure and a target frame slice with a fixed length but no fixed frame structure to carry the service data bitstream. This can meet the transmission requirements of low latency, low jitter and hard isolation for rigid hard pipe services, as well as the transmission requirements of elasticity, flexibility and high utilization for packet pipe services.

[0140] In one embodiment, mapping the service data stream to a frame slice of at least one target frame slice includes:

[0141] Based on the first preset mapping method, the service data stream is mapped to a preset time slot of the first frame slice of the target frame slice;

[0142] Alternatively, based on the second preset mapping method, the service data stream can be mapped to the second frame slice of the target frame slice.

[0143] In this embodiment, the target frame slice includes a first frame slice and a second frame slice. Since the first frame slice and the second frame slice have different structures, the first frame slice can be further divided into multiple time slots to carry service data packets in the service data stream, while the second frame slice has no fixed frame structure. Therefore, the preset mapping method used to map the service data stream to the preset time slots of the first frame slice or the second frame slice is also different.

[0144] In one embodiment, the first preset mapping method includes: a direct mapping method or a compressed mapping method;

[0145] The direct mapping method involves directly mapping each service data packet in the service data stream to the corresponding preset time slot of the first frame slice of the target frame slice.

[0146] The compression mapping method involves compressing and transcoding each service data packet of the service data stream and then mapping it to the corresponding preset time slot of the first frame slice of the target frame slice.

[0147] The service data message is a 66-bit service data encoding block.

[0148] In this implementation, the service data packets in the service data stream are 66-bit service data encoded blocks. The first mapping method used to map the service data packets in the service data stream to the preset time slot of the first frame slice of the target frame slice can include: direct mapping and compressed mapping. Direct mapping directly maps the 66-bit service data encoded block to the corresponding preset time slot of the first frame slice of the target frame slice. Compressed mapping first compresses and transcodes the 66-bit service data encoded block into a 65-bit service data encoded block, and then maps the 65-bit service data encoded block to the corresponding preset time slot of the first frame slice of the target frame slice.

[0149] In one embodiment, after mapping the service data stream to at least one first frame slice of the target frame slice, the method further includes:

[0150] Based on the time slot cross-configuration table, the service data packets carried by the time slots of the first frame slice are forwarded to the preset time slots corresponding to the first frame slices of the next communication node.

[0151] In this embodiment, the time slot cross-configuration table can be understood as a configuration table that includes the cross-relationship of inbound and / or outbound time slots of service data packets, used to indicate the forwarding path of service data packets. Through the time slot cross-relationship in the time slot cross-configuration table, the service data packets carried by the time slots of the current target frame slice are forwarded to the corresponding time slots of the first frame slice of the next communication node.

[0152] In one embodiment, the second preset mapping method includes: a complete data packet mapping method or a data packet concatenation mapping method;

[0153] The complete data packet mapping method includes: mapping at least one complete service data packet in the service data stream to the second frame slice of the target frame slice; filling the remaining space of the second frame slice based on idle data blocks, wherein the remaining space is the space in the second frame slice where a complete service data packet cannot be mapped;

[0154] The data packet concatenation and mapping methods include:

[0155] Map the first part of the data block in the service data message to the remaining space of the second frame slice of the first target frame slice;

[0156] The second part of the data block in the service data message is mapped to the starting position of the second frame slice of the second target frame slice; the second target frame slice is the adjacent target frame slice of the first target frame slice; the first part of the data block is determined based on the remaining space of the second frame slice of the first target frame slice.

[0157] In this embodiment, the second mapping method used to map the service data packets in the service data stream to the second frame slice of the target frame slice may include: a complete data packet mapping method or a data packet splicing mapping method.

[0158] The complete data packet mapping method can be understood as the second frame slice consisting entirely of complete service data packets (S block + D block + T block). If the remaining space in the second frame slice is insufficient to accommodate the next complete service data packet, the remaining space is filled with idle data blocks. The advantage of this method is its good compatibility, allowing it to traverse SPN / MTN path channels. The disadvantage is some bandwidth waste.

[0159] The data packet concatenation mapping method can be understood as allowing service data packets (S block + D block + T block) to span the second frame slice of two adjacent target frame slices. When the remaining space in the second frame slice is insufficient to accommodate a complete customer service packet, the remaining space only stores the first part of the customer service packet's data block (i.e., the second frame slice ends with either the D block or the S block), and then the remaining part of the customer service data block (i.e., the second part of the data block) is placed at the beginning of the second frame slice of the next target frame slice (i.e., the beginning of the second frame slice is located in either the D block or the T block). The advantage of this method is high bandwidth utilization, but the disadvantage is that it cannot penetrate SPN / MTN path channels.

[0160] In one embodiment, under the data packet splicing and mapping method, the next communication node to which the service data stream is forwarded is the target communication node; the target communication node is the communication node corresponding to the receiver of the service data stream.

[0161] In this embodiment, the scenario applicable to mapping service data packets in the service data stream to the second frame slice of the target frame slice based on the message concatenation mapping method can be that the next communication node to which the service data stream is forwarded is the target communication node (i.e., the communication node corresponding to the receiver of the service data stream). After receiving the service data stream, the target communication node decodes the service data stream but does not encapsulate and forward it to the next communication node. It can also be considered an application scenario where termination occurs with only one hop, such as a 10GE Ethernet interface.

[0162] The following example illustrates the business processing method.

[0163] In one embodiment, Figure 17 This is a schematic diagram illustrating the principle of a business processing method provided in one embodiment. For example... Figure 17 As shown, for service data from customer services A, B, C, and D from the Ethernet MAC, they are encoded using 64B / 66B to form service data streams A, B, C, and D, respectively. Service data stream A is mapped to the first slot 1 and the second slot of the first frame slice CFS, service data stream B is mapped to the m-th slot 2 of the first frame slice CFS, and service data streams C and D are mapped to the second frame slice PSS.

[0164] In this implementation, the service data packets in service data streams A, B, C, and D can be 66-bit service data encoded blocks conforming to the IEEE 802.3 PCS layer 64B / 66B specification, or they can be 65-bit service data encoded blocks.

[0165] This application also provides a slicing device. Figure 18 This is a schematic diagram of a slicing device provided in one embodiment. Figure 18 As shown, the slicing device includes:

[0166] Module 310 is configured to acquire the physical layer to be sliced;

[0167] The slicing module 320 is configured to slice the physical layer to be sliced ​​to obtain a target frame slice; the target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure.

[0168] In one embodiment, the distribution structure of the target frame slice includes: a region-based sequential distribution structure or an interleaved distribution structure.

[0169] In one embodiment, the first frame slice is composed of multiple sub-slice frames having the same frame structure and the same length.

[0170] In one embodiment, the frame structure of the first frame slice includes: a single frame structure or a multi-frame structure.

[0171] In one embodiment, the slicing module 320 includes:

[0172] The insertion unit is configured to insert at least one free block between two adjacent sub-slice frames; the free block is a 64B / 66B encoded block conforming to a preset specification;

[0173] The adjustment unit is configured to adjust the data transmission rate of the first frame slice by adjusting the number of free blocks.

[0174] In one embodiment, the sub-slice frame adopts a first data block format; the first data block format includes: a start block, at least one data block, and a stop block;

[0175] The start block, the data block, and the end block are all 64B / 66B encoded blocks that conform to a preset specification.

[0176] In one embodiment, the sub-slice frame includes, but is not limited to, sub-slice frame overhead and payload; the payload includes, a plurality of time slots of the same size arranged according to a preset arrangement.

[0177] In one embodiment, the preset arrangement includes: a sequential arrangement or an interleaved arrangement.

[0178] In one embodiment, the size of the time slot is an integer multiple of the size of the service data packet, and the service data packet is a 66-bit service data encoded block or a compressed 65-bit service data encoded block.

[0179] In one embodiment, it further includes:

[0180] The channel configuration module is configured to construct a time-slot channel based on at least one of the time slots; different time-slot channels are used to carry different service data packets.

[0181] In one embodiment, the slicing module 320 is configured to configure the occupied bytes of the sub-slice frame overhead;

[0182] The bytes occupied by the sub-slice frame overhead include at least one of the following:

[0183] The bytes in the start block, the data area in the data block, and the data area in the end block.

[0184] In one embodiment, when the target frame slice does not include slice overhead, the first frame feature information of the first frame slice is used as the frame header of the target frame slice.

[0185] In one embodiment, the second frame slice adopts the second data block format and directly carries the service data packet formed by 64B / 66B encoding;

[0186] The second data block format includes: a sequence of service data packets consisting of a start block, at least one data block, and a stop block, as well as free blocks between the service data packets;

[0187] The start block, the data block, the end block, and the free block are all 64B / 66B encoded blocks that conform to a preset specification.

[0188] In one embodiment, the target frame slice further includes slice overhead.

[0189] In one embodiment, the data code block format used for the slice overhead includes:

[0190] Third data block format, or fourth data block format;

[0191] The third data block format includes: a start block and a stop block;

[0192] The fourth data block format includes: a start block, a data block, and a stop block.

[0193] In one embodiment, when the data block format of the slice overhead is a first data block format, the slice overhead serves as the frame header of the target frame slice.

[0194] In one embodiment, the service layer of the target frame slice includes at least one of the following:

[0195] The slice channel layer of SPN, the channel layer of MTN, Flexible Ethernet (FlexE), Ethernet physical layer, and Optical Transmission Network (OTN).

[0196] The slicing device proposed in this embodiment belongs to the same inventive concept as the slicing method proposed in the above embodiments. Technical details not described in detail in this embodiment can be found in any of the above embodiments. Furthermore, this embodiment has the same beneficial effects as the slicing method.

[0197] This application also provides a business processing apparatus. Figure 19 This is a schematic diagram of a service processing apparatus provided in one embodiment. Figure 19 As shown, the service processing device includes:

[0198] Module 410 is configured to acquire business data.

[0199] Encoding module 420 is configured to encode the business data to form a business data bitstream;

[0200] The mapping module 430 is configured to map the service data stream to at least one target frame slice; the target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure.

[0201] In one embodiment, the mapping module 430 includes:

[0202] The first mapping unit is configured to map the service data stream to a preset time slot of the first frame slice of the target frame slice based on a first preset mapping method.

[0203] The second mapping unit is configured to map the service data stream to the second frame slice of the target frame slice based on a second preset mapping method.

[0204] In one embodiment, the first preset mapping method includes: a direct mapping method or a compressed mapping method;

[0205] The direct mapping method involves directly mapping each service data packet in the service data stream to the corresponding preset time slot of the first frame slice of the target frame slice.

[0206] The compression mapping method involves compressing and transcoding each service data packet of the service data stream and then mapping it to the corresponding preset time slot of the first frame slice of the target frame slice.

[0207] The service data message is a 66-bit service data encoding block.

[0208] In one embodiment, the device further includes:

[0209] The forwarding module is configured to, after mapping the service data stream to the first frame slice of at least one of the target frame slices, forward the service data packets carried in the time slots of the first frame slice to the preset time slots corresponding to the first frame slices of the next communication node based on the time slot cross-configuration table.

[0210] In one embodiment, the second preset mapping method includes: a complete data packet mapping method or a data packet concatenation mapping method;

[0211] The complete data packet mapping method includes: mapping at least one complete service data packet in the service data stream to the second frame slice of the target frame slice; filling the remaining space of the second frame slice based on idle data blocks, wherein the remaining space is the space in the second frame slice where a complete service data packet cannot be mapped;

[0212] The data packet concatenation and mapping methods include:

[0213] Map the first part of the data block in the service data message to the remaining space of the second frame slice of the first target frame slice;

[0214] The second part of the data block in the service data message is mapped to the starting position of the second frame slice of the second target frame slice; the second target frame slice is the adjacent target frame slice of the first target frame slice; the first part of the data block is determined based on the remaining space of the second frame slice of the first target frame slice.

[0215] In one embodiment, under the data packet splicing and mapping method, the next communication node to which the service data stream is forwarded is the target communication node; the target communication node is the communication node corresponding to the receiver of the service data stream.

[0216] The business processing apparatus proposed in this embodiment belongs to the same inventive concept as the business processing method proposed in the above embodiments. Technical details not described in detail in this embodiment can be found in any of the above embodiments. Furthermore, this embodiment has the same beneficial effects as the business processing method.

[0217] This application also provides a communication node. Figure 20 This is a schematic diagram of the hardware structure of a communication node provided in one embodiment, such as... Figure 20 As shown, the communication node provided in this application may include a first terminal, a second terminal, and a third terminal. The communication node includes a memory 520, a processor 510, and a computer program stored in the memory and executable on the processor. When the processor 510 executes the program, it implements the above-mentioned slicing method or business processing method.

[0218] The communication node may also include a memory 520; the processor 510 in the communication node may be one or more. Figure 20 Taking a processor 510 as an example; memory 520 is used to store one or more programs; the one or more programs are executed by the one or more processors 510, so that the one or more processors 510 implement the slicing method or business processing method as described in the embodiments of this application.

[0219] The communication node also includes: a communication device 530, an input device 540, and an output device 550.

[0220] The processor 510, memory 520, communication device 530, input device 540, and output device 550 in the communication node can be connected via a bus or other means. Figure 20 Taking the example of a connection between China and Israel via a bus.

[0221] Input device 540 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the communication node. Output device 550 may include display devices such as a display screen.

[0222] The communication device 530 may include a receiver and a transmitter. The communication device 530 is configured to perform information transmission and reception communication under the control of the processor 510.

[0223] The memory 520, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the slicing method or service processing method described in the embodiments of this application (e.g., the acquisition module 310 and slicing module 320 in the slicing device; or the acquisition module 410, encoding module 420, and mapping module 430 in the service processing device). The memory 520 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created based on the use of the communication node, etc. Furthermore, the memory 520 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 520 may further include memory remotely located relative to the processor 510, and these remote memories can be connected to the communication node 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.

[0224] This application also provides a storage medium storing a computer program, which, when executed by a processor, implements any of the slicing methods or business processing methods described in this application.

[0225] In this embodiment of the application, the slicing method includes:

[0226] Obtain the physical layer to be sliced;

[0227] The physical layer to be sliced ​​is sliced ​​to obtain a target frame slice; the target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure.

[0228] In this embodiment of the application, the business processing method includes: obtaining the encoded attribute data of the point cloud;

[0229] Obtain business data;

[0230] The business data is encoded to form a business data bitstream;

[0231] The service data stream is mapped to at least one target frame slice; the target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure.

[0232] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable CD-ROM, optical storage device, magnetic storage device, or any suitable combination thereof. The computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0233] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in connection with an instruction execution system, apparatus, or device.

[0234] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, radio frequency (RF), etc., or any suitable combination thereof.

[0235] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0236] The above description is merely an exemplary embodiment of this application and is not intended to limit the scope of protection of this application.

[0237] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0238] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0239] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0240] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on memory. Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disk (CD), etc.). Computer-readable media may include non-transitory storage media. Data processors may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0241] A detailed description of exemplary embodiments of this application has been provided above through exemplary and non-limiting examples. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, without departing from the scope of this application. Therefore, the proper scope of this application will be determined by the claims.

Claims

1. A slicing method, characterized in that, include: Obtain the physical layer to be sliced; The physical layer to be sliced ​​is sliced ​​to obtain the target frame slice; The target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure; The distribution structure of the target frame slices includes: a region-based sequential distribution structure or an interleaved distribution structure; the region-based sequential distribution structure means that the first frame slice and the second frame slice of the target frame slice are sequentially distributed in two different regions of the physical layer; the interleaved distribution structure means that the sub-slices of the first frame slice and the second frame slice are interleaved.

2. The method according to claim 1, characterized in that, The first frame slice is composed of multiple sub-slice frames with the same frame structure and the same length.

3. The method according to claim 1, characterized in that, The frame structure of the first frame slice includes: a single frame structure or a multi-frame structure; wherein, the sub-slice frames contained in the first frame slice with a single frame structure have the same frame structure, and the sub-slice frames contained in the first frame slice with a multi-frame structure have different frame structures.

4. The method according to claim 2, characterized in that, Slicing the physical layer to be sliced ​​to obtain a target frame slice further includes: At least one free block is inserted between two adjacent sub-slice frames; the free block is a 64B / 66B encoded block conforming to a preset specification; The data transmission rate of the first frame slice is adjusted by adjusting the number of free blocks.

5. The method according to claim 2, characterized in that, The sub-slice frame adopts a first data code block format; the first data code block format includes: a start block, at least one data block, and a stop block; The start block, the data block, and the end block are all 64B / 66B encoded blocks that conform to a preset specification.

6. The method according to claim 5, characterized in that, The sub-slice frame includes, but is not limited to, sub-slice frame overhead and payload; the payload includes, multiple time slots of the same size arranged according to a preset arrangement.

7. The method according to claim 6, characterized in that, The preset arrangement methods include: sequential arrangement or interleaved arrangement.

8. The method according to claim 6, characterized in that, The size of the time slot is an integer multiple of the size of the service data packet, and the service data packet is a 66-bit service data encoding block or a compressed 65-bit service data encoding block.

9. The method according to claim 6, characterized in that, Also includes: A time slot channel is constituted according to at least one of the time slots; Different time slot channels are used to carry different service data packets.

10. The method according to claim 6, characterized in that, Slicing the physical layer to be sliced ​​to obtain a target frame slice includes: Configure the bytes occupied by the sub-slice frame overhead; The bytes occupied by the sub-slice frame overhead include at least one of the following: The bytes in the start block, the data area in the data block, and the data area in the end block.

11. The method according to claim 1, characterized in that, The first frame feature information of the first frame slice is used as the frame header of the target frame slice.

12. The method according to claim 1, characterized in that, The second frame slice adopts the second data block format and directly carries the business data message formed by 64B / 66B encoding; The second data block format includes: a sequence of service data packets consisting of a start block, at least one data block, and a stop block, as well as free blocks between the service data packets; The start block, the data block, the end block, and the free block are all 64B / 66B encoded blocks that conform to a preset specification.

13. The method according to claim 1, characterized in that, The target frame slice also includes: slice overhead.

14. The method according to claim 13, characterized in that, The data code block format used for the slice overhead includes: Third data block format, or fourth data block format; The third data block format includes: a start block and a stop block; The fourth data block format includes: a start block, a data block, and a stop block.

15. The method according to claim 14, characterized in that, When the data block format of the slice overhead is a first data block format, the slice overhead serves as the frame header of the target frame slice.

16. The method according to claim 1, characterized in that, The service layer of the target frame slice includes at least one of the following: The slice channel layer of SPN, the channel layer of MTN, Flexible Ethernet (FlexE), Ethernet physical layer, and Optical Transmission Network (OTN).

17. A business processing method, characterized in that, include: Obtain business data; The business data is encoded to form a business data bitstream; Map the service data stream to at least one target frame slice; The target frame slice includes: a first frame slice and a second frame slice; the first frame slice is a slice with a fixed length and a fixed frame structure, and the second frame slice is a slice with a fixed length but no fixed frame structure; The distribution structure of the target frame slices includes: a region-based sequential distribution structure or an interleaved distribution structure; the region-based sequential distribution structure means that the first frame slice and the second frame slice of the target frame slice are sequentially distributed in two different regions of the physical layer; the interleaved distribution structure means that the sub-slices of the first frame slice and the second frame slice are interleaved.

18. The method according to claim 17, characterized in that, Mapping the service data stream to a frame slice of at least one target frame slice includes: Based on the first preset mapping method, the service data stream is mapped to a preset time slot of the first frame slice of the target frame slice; or, Based on the second preset mapping method, the service data stream is mapped to the second frame slice of the target frame slice.

19. The method according to claim 18, characterized in that, The first preset mapping method includes: direct mapping method or compressed mapping method; The direct mapping method involves directly mapping each service data packet in the service data stream to the corresponding preset time slot of the first frame slice of the target frame slice. The compression mapping method involves compressing and transcoding each service data packet of the service data stream and then mapping it to the corresponding preset time slot of the first frame slice of the target frame slice. The service data message is a 66-bit service data encoding block.

20. The method according to claim 18, characterized in that, After mapping the service data stream to at least one of the first frame slices of the target frame slice, the method further includes: Based on the time slot cross-configuration table, the service data packets carried by the time slots of the first frame slice are forwarded to the preset time slots corresponding to the first frame slices of the next communication node.

21. The method according to claim 18, characterized in that, The second preset mapping method includes: complete data packet mapping method or data packet concatenation mapping method; The complete data packet mapping method includes: mapping at least one complete service data packet in the service data stream to the second frame slice of the target frame slice; filling the remaining space of the second frame slice based on idle data blocks, wherein the remaining space is the space in the second frame slice where a complete service data packet cannot be mapped; The data packet concatenation and mapping methods include: Map the first part of the data block in the service data message to the remaining space of the second frame slice of the first target frame slice; The second part of the data block in the service data message is mapped to the starting position of the second frame slice of the second target frame slice; the second target frame slice is the adjacent target frame slice of the first target frame slice; the first part of the data block is determined based on the remaining space of the second frame slice of the first target frame slice.

22. The method according to claim 21, characterized in that, In the data packet concatenation and mapping method, the next communication node to which the service data stream is forwarded is the target communication node; the target communication node is the communication node corresponding to the receiver of the service data stream.

23. A communication node, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the method as described in any one of claims 1-22.

24. A storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-22.

Images