Service data processing method, service data exchange method, service data extraction method, and computer-readable media

Abstract

The present application provides a service data processing method, which includes: generating a service block for each of a plurality of client services based on service data of the client services; mapping the service block for each of the client services to a payload area of ​​at least one subslicing frame SSF; and setting an overhead area field of each of the SSF frames to obtain the at least one SSF frame, where each of the SSF frames carries a service block for each of a plurality of different client services. The present application also provides a service data exchange method, a service data extraction method, a provider edge device, a provider exchange device, and a computer-readable medium.

Description

Technical Field

[0004]

[0001] Embodiments of the present disclosure relate to the technical field of communications, but are not limited thereto.

Background Art

[0002] Flexible Ethernet (FlexE) technology was initiated by the Optical Internetworking Forum (OIF), an international standards organization, in March 2015, and the related technical standards were formally determined by voting in March 2016. Flexible Ethernet technology transmits a series of services with different Media Access Control (MAC) speeds through a common mechanism. The services to be transmitted are not limited to services with a single MAC speed, and may be services with a high single MAC speed or a set of services with multiple low MAC speeds.

Summary of the Invention

Problems to be Solved by the Invention

[0003] Embodiments of the present disclosure provide a service data processing method, a service data exchange method, a service data extraction method, a provider edge device, a provider exchange device, and a computer-readable medium.

Means for Solving the Problems

[0005] A second aspect of the embodiments of this disclosure provides a service data exchange method. This service data exchange method includes identifying the outbound port of each service block in an inbound SSF frame received by an inbound port, mapping the service blocks corresponding to the same outbound port to at least one outbound SSF frame, and transmitting the outbound SSF frame through the outbound port, where each of the inbound SSF frames carries a service block of multiple different client services, and each of the outbound SSF frames carries a service block of multiple different client services.

[0006] A third aspect of the embodiments of this disclosure provides a service data extraction method. This service data extraction method includes extracting a service block of a predetermined client service from at least one SSF frame, and decoding the service block of the predetermined client service to extract the service data of the predetermined client service. Here, each of the SSF frames carries a plurality of different client service service blocks.

[0007] A fourth aspect of the embodiments of this disclosure provides a provider edge device (PE). The provider edge device (PE) comprises one or more processors, a storage device storing one or more programs, and one or more I / O interfaces connected between the processors and the storage device and installed to enable information communication between the processors and the storage device. When the one or more programs are executed by the one or more processors, the one or more processors are made to implement one of the above-described service data processing methods or one of the above-described service data extraction methods.

[0008] A fifth aspect of the embodiments of this disclosure provides a provider exchange device. The provider exchange device comprises one or more processors, a storage device storing one or more programs, and one or more I / O interfaces connected between the processors and the storage device and installed to enable information communication between the processors and the storage device. When the one or more programs are executed by the one or more processors, the one or more processors are made to implement one of the above-described service data exchange methods.

[0009] A sixth aspect of the embodiments of this disclosure provides a computer-readable medium on which a computer program is stored. When the program is executed by a processor, any one of the above service data processing methods, any one of the above service data exchange methods, or any one of the above service data extraction methods is realized. [Brief explanation of the drawing]

[0010] The drawings are for further understanding of embodiments of this disclosure and constitute part of this specification. The drawings are also for interpreting this disclosure together with embodiments of this disclosure and do not limit this disclosure. A detailed description of embodiments illustrated with reference to the drawings will further clarify the above-mentioned features, other features, and advantages for those skilled in the art.

[0011] [Figure 1] Figure 1 is a flowchart showing a service data processing method according to one embodiment of the present disclosure. [Figure 2] Figure 2 is a schematic diagram showing the service bearer hierarchy in one embodiment of the present disclosure. [Figure 3] Figure 3 is a flowchart showing some steps of another service data processing method according to one embodiment of the present disclosure. [Figure 4] Figure 4 is a schematic diagram showing the mapping of a client service to a corresponding SSC time slot in one embodiment of the present disclosure. [Figure 5] Figure 5 is a schematic diagram showing the format of a 64 / 66B block. [Figure 6] Figure 6 is a schematic diagram showing one embodiment of a termination block according to one embodiment of the present disclosure. [Figure 7] Figure 7 is a schematic diagram showing one embodiment of the SSF frame structure and time slot division in one embodiment of the present disclosure. [Figure 8] Figure 8 is a schematic diagram showing one embodiment of the SSMF multiframe structure and time slot division in one embodiment of the present disclosure. [Figure 9] Figure 9 is a schematic diagram showing another embodiment of the SSF frame structure and time slot division in one embodiment of the present disclosure. [Figure 10] Figure 10 is a flowchart showing some steps of another service data processing method according to one embodiment of the present disclosure. [Figure 11] This flowchart shows some steps of a further service data processing method according to one embodiment of the present disclosure. [Figure 12] Figure 12 is a schematic diagram showing one embodiment of overhead in an SSF frame according to one embodiment of the present disclosure. [Figure 13] Figure 13 is a flowchart showing some steps of a further service data processing method according to one embodiment of the present disclosure. [Figure 14]FIG. 14 is a flowchart showing some steps of a further service data processing method according to an embodiment of the present disclosure. [Figure 15] FIG. 15 is a schematic diagram showing the definition of a specific field of overhead in an SSF frame according to an embodiment of the present disclosure. [Figure 16] FIG. 16 is a flowchart showing some steps of a further service data processing method according to an embodiment of the present disclosure. [Figure 17] FIG. 17 is a flowchart showing some steps of a further service data processing method according to an embodiment of the present disclosure. [Figure 18] FIG. 18 is a flowchart showing some steps of a further service data processing method according to an embodiment of the present disclosure. [Figure 19] FIG. 19 is a schematic diagram showing an embodiment of an SSC channel data stream in an embodiment of the present disclosure [Figure 20] FIG. 20 is a flowchart showing some steps of a further service data processing method according to an embodiment of the present disclosure. [Figure 21] FIG. 21 is a flowchart showing a service data exchange method according to an embodiment of the present disclosure. [Figure 22] FIG. 22 is a flowchart showing some steps of another service data exchange method according to an embodiment of the present disclosure. [Figure 23] FIG. 23 is a schematic diagram showing an implementation manner of slot intersection in an embodiment of the present disclosure. [Figure 24] FIG. 24 is a flowchart showing some steps of another service data exchange method according to an embodiment of the present disclosure. [Figure 25] FIG. 25 is a flowchart showing some steps of another service data exchange method according to an embodiment of the present disclosure. [Figure 26] FIG. 26 is a flowchart showing some steps of another service data exchange method according to an embodiment of the present disclosure. [Figure 27]Figure 27 is a flowchart showing a service data extraction method according to one embodiment of the present disclosure. [Figure 28] Figure 28 is a flowchart showing some steps of a different service data extraction method according to one embodiment of the present disclosure. [Figure 29] Figure 29 is a flowchart showing some steps of another service data extraction method according to one embodiment of the present disclosure. [Figure 30] Figure 30 is a schematic diagram illustrating an implementation method for constructing an SSC channel in one embodiment of the present disclosure. [Figure 31] Figure 31 is a schematic diagram illustrating another implementation of constructing an SSC channel in one embodiment of the present disclosure. [Figure 32] Figure 32 is a schematic diagram illustrating an implementation method of SCL crossing in one embodiment of the present disclosure. [Figure 33] Figure 33 is a block diagram of a provider edge device according to one embodiment of the present disclosure. [Figure 34] Figure 34 is a block diagram of a provider exchange device according to one embodiment of the present disclosure. [Figure 35] Figure 35 is a block diagram of a computer-readable medium according to one embodiment of the present disclosure. [Modes for carrying out the invention]

[0012] To enable those skilled in the art to better understand the technical proposals of this disclosure, the service data processing method, service data exchange method, service data extraction method, provider edge device, provider exchange device, and computer-readable media relating to this disclosure will be described in detail below with reference to the drawings.

[0013] Embodiments will be described in detail below with reference to the drawings, but the embodiments described herein can be realized in different forms and are not limited to those described herein. These embodiments are provided to clearly and completely illustrate the herein, and those skilled in the art will be able to fully understand the scope of the herein from these embodiments.

[0014] Where there is no inconsistency, the features of each embodiment of this disclosure may be combined.

[0015] As used herein, the term "and / or" includes any and all combinations of one or more related elements listed.

[0016] The terms used herein are for the sole purpose of describing specific embodiments and are not intended to limit the disclosure. The singular forms “one” and “the said” as used herein are intended to include the plural form unless the context explicitly indicates otherwise. Furthermore, the terms “including” and / or “consisting of” as used herein specify the presence of the aforementioned features, wholes, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements and / or groups thereof.

[0017] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as those commonly understood by those skilled in the art. Terms as defined in commonly used dictionaries should have a meaning consistent with their meaning in the context of the relevant art and this disclosure, and should not be construed as having an idealized or overly formal meaning unless expressly limited herein.

[0018] Slicing Packet Networks (SPNs) and Metro Transport Networks (MTNs) use FlexE as the service layer to achieve end-to-end rigid channels for services. However, the minimum granularity of client services supported by current FlexE, SPN, and MTN standards is 5 Gb / s, and they do not support hard isolation and rigid channels for services smaller than 5 Gb / s. Similarly, Optical Transport Network (OTN) technology supports services with a minimum granularity of 1.25 Gb / s, but does not support services smaller than 1.25 Gb / s. The inventors of this disclosure have found that methods in the prior art that support small-granular client services are all improvements from FlexE's 5 Gb / s time slots and have the following main problems: (1) They are still limited in terms of service granularity. For example, they require a service granularity of 1 Gb / s or more and do not support small-granularity services such as 10 Mb / s or 100 Mb / s. (2) It has low flexibility; although the services being transmitted are no longer limited to single MAC rate services, it is difficult to support the mixed transmission of small-grained client services with different granularities in a single 5G time slot. (3) It has low compatibility; it is not compatible with current Ethernet, FlexE, SPN, and MTN standards, and cannot communicate with existing equipment, such as being unable to pass through the P (Provider) node of standard SPN equipment.

[0019] In view of the above, with reference to Figure 1, a first aspect of the embodiments of this disclosure provides a service data processing method. This service data processing method includes steps S110, S120, and S130. In step S110, a service block for each of the client services is generated based on the service data of a plurality of client services. In step S120, all of the service blocks for each of the client services are mapped to the payload area of ​​at least one sub-slicing frame SSF. In step S130, the overhead area field of each SSF frame is configured to obtain at least one SSF frame, where each of the SSF frames carries service blocks for a plurality of different client services.

[0020] In embodiments of this disclosure, a Sub-Slicing Frame (SSF) is proposed. This SSF frame includes an overhead region and a payload region capable of carrying at least one client service. Each client service corresponds to one Sub-Slicing Channel (SSC), and the SSC channels of all client services constitute a Sub-Slicing Channel Layer (SSCL).

[0021] In the embodiments of this disclosure, the SSC channel is a logical channel configured on the service layer channel, and the SSCL is a logical channel sublayer configured in the service layer. For example, the SSCL is a channel sublayer located between the IEEE 802.3 Physical Coding Sublayer (PCS) and the Medium Access Control (MAC). The embodiments of this disclosure do not particularly limit the service layer. For example, as shown in Figure 2, the service layer may be the Slicing Channel Layer (SCL) of an SPN corresponding to an SPN Slicing Channel, the Path Layer of an MTN corresponding to an MTN Path Channel, FlexE, or the Physical Layer (PHY) of an Ethernet port, i.e., the IEEE 802.3 PHY in Figure 2. The service layer may also be an Optical Transport Network (OTN).

[0022] In embodiments of this disclosure, the frame structure for SSF frames is predefined, but this disclosure does not particularly limit the predefined frame structure. At a Source Provider Edge (PE) node, step S110 packages / encodes service data for different client services according to a predetermined format and generates service blocks that conform to the predetermined frame structure of the SSF frame. The service blocks for different client services that conform to the predefined frame structure of the SSF frame are identical in both format and size. In step S120, the service blocks for each client service are assembled according to a predetermined mapping scheme. In step S130, the overhead field for each SSF frame is set, and at least one SSF frame conforming to the predefined frame structure is generated. Furthermore, in embodiments of this disclosure, the execution order of step S130 relative to steps S110 and S120 is not limited. For example, the overhead field for the SSF frame may be set before mapping the service block for each client service to at least one SSF frame. Alternatively, the overhead field of the SSF frame may be set after mapping the service block of each client service to at least one SSF frame.

[0023] Embodiments of this disclosure do not particularly limit the type of client service. For example, as shown in Figure 2, the client service may be an Ethernet service or a fixed-rate time-division multiplexing (TDM) service. Furthermore, in step S110, the plurality of client services may be N Ethernet services or N TDM services. Alternatively, there may be M Ethernet services and L TDM services, where M + L = N, N is a positive integer, and L and M are natural numbers. Embodiments of this disclosure are not particularly limited thereto.

[0024] In the embodiments of this disclosure, there are no particular limitations on the granularity of the client service. The client service may have a granularity smaller than 5G. For example, the granularity of the client service may be 1Gb / s, 100Mb / s, 10Mb / s, etc. Alternatively, the service may have a granularity of 5G. That is, the granularity of the client service may be 5Gb / s. Furthermore, the service may have a granularity larger than 5G. For example, the granularity of the client service may be 6Gb / s, 8Gb / s, etc.

[0025] In the embodiments of this disclosure, each SSF frame carries multiple different client services. That is, each SSF frame consists of service blocks for multiple different client services. In embodiments of this disclosure, if there are multiple client services, the service blocks for multiple client services may be incorporated into the same SSF frame. Alternatively, two or more adjacent SSF frames may be combined to form a Sub-Slicing Multi-Frame (SSMF), and multiple client services may be mapped to the SSMF multi-frame. Embodiments of this disclosure are not limited thereto. For example, based on a predefined frame length of the SSF frame, the number of each client service, and the granularity, it may be determined whether to map multiple client services to a single SSF frame or to an SSMF multi-frame consisting of multiple SSF frames.

[0026] In embodiments of this disclosure, the granularity of the multiple client services may differ. In step S120, client services of different granularity realize SSC channels of different bandwidths capable of carrying client services of different granularity by having a different number of service blocks mapped to SSF frames or SSMF multiframes. Steps S110 to S130 can realize SSC channels of any bandwidth. In other words, the granularity of client services is not limited in embodiments of this disclosure.

[0027] Furthermore, the SSF frames generated by the source PE node may also include other data that constitutes the SSF frame, such as Operation Administration and Maintenance (OAM) information, but the embodiments of this disclosure are not limited thereto.

[0028] In a service data processing method according to an embodiment of this disclosure, an SSF frame is proposed. Each SSF frame can carry multiple different client services. Multiple SSF frames constitute an SSMF multiframe. In an embodiment of this disclosure, different client services are packaged and encoded according to a predefined SSF frame format to generate service blocks for different client services, and a corresponding number of service blocks are mapped to an SSF frame or SSMF multiframe according to the granularity of the different client services to constitute an SSF frame or SSMF multiframe. In this way, simultaneous transmission of client services of different granularity can be achieved. The service data processing method according to an embodiment of this disclosure enables transmission of services of different granularity over a rigid channel, satisfying the transmission requirements of low latency, low jitter, hard isolation, and different bandwidths, and is not limited by conventional standards such as FlexE, SPN, and MTN for the smallest granularity client service. Furthermore, it can simultaneously support multiple Ethernet services and / or TDM services, and the service speed is flexible. Furthermore, it can transmit SSF frames using any one of the following as the service layer: SPN, MTN, Ethernet, OTN, etc., ensuring good compatibility with existing standard systems such as Ethernet, FlexE, SPN, MTN, and OTN.

[0029] In embodiments of this disclosure, the mapping method for mapping each of the client service service blocks to the payload area of ​​at least one sub-slicing frame SSF in step S120 is not particularly limited. In one optional embodiment, a time slot scheduling scheme may be used to map service blocks of different client services to an SSF frame or an SSMF multiframe. Specifically, the payload area of ​​the SSF frame or SSMF multiframe is divided into fixed-length time slots to ensure that fixed-rate bandwidth and rigid isolation are provided for the services of different client services carried by the SSF frame.

[0030] Accordingly, with reference to Figure 3, in some embodiments, step S120 specifically includes steps S121 and S122. In step S121, the payload region of the at least one SSF frame is divided into a plurality of time slots. In step S122, each service block of the client service is mapped to a different time slot in the plurality of time slots, where the time slots corresponding to different client services constitute a sub-slicing channel SSC that carries each of the client services, respectively.

[0031] In one of the embodiments of this disclosure, as an optional embodiment, in step S121, the payload region of a single SSF frame may be divided to obtain multiple time slots.

[0032] Alternatively, in one optional embodiment, in step S121, an SSMF multiframe may be constructed from two or more SSF frames, and the payload region of the SSMF multiframe may be divided to obtain multiple time slots.

[0033] In embodiments of this disclosure, the size of the time slots obtained by dividing the payload region of an SSF frame or SSMF multiframe is not particularly limited. For example, the size of the time slots can be equal to the size of the service block in step S110. If the service block is a 64 / 66B block conforming to the IEEE 802.3 coding standard, the size of the time slots is 66 bits. Alternatively, the size of the time slots may be determined according to the granularity of each client service. Furthermore, for example, the granularity size of the smallest client service among multiple client services may be determined as the size of the time slots. Furthermore, the size of the time slots may be determined based on a common divisor of the granularity of multiple client services.

[0034] JPEG0007835687000001.jpg25170

number

[0035] JPEG0007835687000003.jpg30170

[0036] In step S122, each service block of a client service is mapped to a different time slot within the plurality of time slots, based on the granularity of each client service and the speed of the time slot specified by equation (1).

[0037] JPEG0007835687000004.jpg16170

number

[0038] JPEG0007835687000006.jpg28170

[0039] A service block of the same client service may be mapped to multiple adjacent time slots or to multiple non-adjacent time slots. Embodiments of this disclosure are not limited thereto. A time slot carrying a client service may be considered as an SSC channel carrying the client service. If the time slots constituting the SSC channels carrying different client services are different, the bandwidth of the SSC channels carrying different client services will also be different. On the other hand, the same client service may be considered as a continuous code stream within the time slot carrying the client service.

[0040] First Embodiment In the first embodiment, as shown in Figure 4, the SSF frame includes, but is not limited to, overhead (OH) and payload.

[0041] In Figure 4, the SSF frame payload is divided into m time slots of the same size, from slot1 to slotm. Slot1 and slot2 form the SSCA channel carrying client service ClientA, and sloti forms the SSCB channel carrying client service ClientB. The bandwidth of the SSCA channel is equal to the sum of the speeds of slot1 and slot2, and the bandwidth of the SSCB channel is equal to the speed of sloti.

[0042] In the first embodiment, other different client services may also exist. Each client service is carried by an SSC channel consisting of the corresponding time slots from slot1 to slotm shown in Figure 4. The bandwidths of the SSC channels carrying different client services may differ.

[0043] Second Embodiment In the second embodiment, the structure of the SSF frame is defined based on the IEEE 802.3 PCS layer 64 / 66B encoding standard.

[0044] There are three types of 64 / 66B blocks that make up an SSF frame: one start block (also called an S block), n data blocks (also called D blocks), and one terminate block (also called a T block). The length of an SSF frame is (n+2)*66 bits, where n is a different value depending on the design. In other words, an SSF frame may have any other fixed length. For example, if n=495, the length of the SSF frame will be 32802 bits.

[0045] In the second embodiment, the S block, D block, and T block are 66B blocks conforming to the IEEE 802.3 PCS64 / 66B encoding standard. Figure 5 shows the format of a 64 / 66B block according to the IEEE 802.3 standard. As shown in Figure 5, the first two bits of a 66B block are a sync header used to distinguish between a control block and a data block. In Figure 5, 10 represents a control block and 01 represents a data block. Here, the S block and T block belong to the control block, and the D block belongs to the data block. For the control block, the first byte after the sync header represents the block type. In the second embodiment, the block type of the first block (S block) of the SSF frame is 0x78, and the block type of the last block (T block) of the SSF frame is 0xFF. As shown in Figure 6, bytes D0 to D6 (bits 10 to 65) of the T block are the payload data.

[0046] In a second embodiment, the D and T blocks of the SSF frame are used to carry the payload. Different client services are packaged / encoded in the form of D or T blocks, generating D or T blocks as service blocks. The S block and the initial D block extension of the SSF frame are used to carry overhead.

[0047] Figure 7 is a schematic diagram of a second embodiment in which a single SSF frame is divided into multiple time slots. As shown in Figure 7, the payload carried by the second to nth D blocks and T blocks of the SSF frame is divided, resulting in m time slots of the same size, slot1 to slotm.

[0048] Figure 8 is a schematic diagram illustrating how an SSMF multiframe is divided into multiple time slots in a second embodiment. As shown in Figure 8, the k SSF frames constituting the SSMF multiframe are divided in a similar manner; that is, the payload carried by the 2nd to nth D blocks and T blocks of each SSF frame is divided into m time slots of the same size, from slot1 to slotm, resulting in a total of m × k time slots.

[0049] Third Embodiment In the third embodiment, the structure of the SSF frame is defined based on the IEEE 802.3 PCS layer 64 / 66B encoding standard. The definitions of the S block, D block, and T block that constitute the SSF frame are as described in the second embodiment.

[0050] JPEG0007835687000007.jpg40170

[0051] JPEG0007835687000008.jpg10170

[0052] In some embodiments, as shown in Figure 10, step S122 specifically includes steps S1221 and S1222. In step S1221, the location and number of time slots carrying each of the different client services are identified in the plurality of time slots based on the granularity of the different client services. In step S1222, the service blocks of the different client services are mapped to the corresponding time slots based on the location and number of time slots carrying the different client services.

[0053] In embodiments of this disclosure, when step S121 divides the payload area of ​​an SSF frame or SSMF multiframe into multiple time slots of the same size, the bandwidth of the SSC channels composed of different numbers of time slots will also differ. Accordingly, for client services with different granularities, the number of time slots constituting the SSC channel carrying each client service will also differ. For example, in Figure 4, the granularity of client service ClientA is twice that of client service ClientB, and accordingly, the SSCA channel carrying client service ClientA is composed of slot1 and slot2, the SSCB channel carrying client service ClientB is composed of sloti, and the bandwidth of the SSCA channel is twice that of the SSCB channel.

[0054] The embodiments of this disclosure do not particularly limit how the location of time slots that constitute SSC channels carrying different client services in an SSF frame or SSMF frame is determined. For example, several consecutive time slots in the SSF frame or SSMF frame may be selected for each client service to constitute an SSC channel carrying that client service. Alternatively, several adjacent or non-adjacent time slots in the SSF frame or SSMF frame may be selected for each client service to constitute an SSC channel carrying that client service. Alternatively, several time slots may be selected in the SSF frame or SSMF frame by a uniform distribution method to constitute an SSC channel carrying client services.

[0055] In some embodiments, as shown in Figure 11, step S130 specifically includes steps S131 and S132. In step S131, a correspondence is established between each client service and the time slot that carries each client service in the overhead region of the at least one SSF frame. In step S132, other overhead fields are set for the at least one SSF frame to obtain the at least one SSF frame.

[0056] Fourth Embodiment In the fourth embodiment, the structure of the SSF frame is defined based on the IEEE 802.3 PCS layer 64 / 66B encoding standard. The definitions of the S block, D block, and T block that constitute the SSF frame are as described in the second embodiment.

[0057] In the fourth embodiment, as shown in Figure 12, bytes D1 to D7 (bits 10 to 65) of the extended S block are used to store overhead.

[0058] Fifth Embodiment In the fifth embodiment, the structure of the SSF frame is defined based on the IEEE 802.3 PCS layer 64 / 66B encoding standard. The definitions of the S-block, D-block, and T-block that constitute the SSF frame are as described in the second embodiment. In the fifth embodiment, the extended S-block and D-block are used to store overhead.

[0059] In the fifth embodiment, as shown in Figure 7, the S block and the first D block in the SSF frame are extended to accommodate the overhead.

[0060] In the fifth embodiment, as shown in Figure 8, the S block and the first D block of each SSF frame constituting the SSMF multiframe are extended to accommodate the overhead.

[0061] In the embodiments of this disclosure, the location and size of the overhead in the S-blocks, T-blocks, and D-blocks of the SSF frame or SSMF multi-frame are not particularly limited. The first, second, third, fourth, and fifth embodiments are for illustrative purposes to illustrate the use of S-blocks, T-blocks, or D-blocks to carry overhead, and are not intended to limit the embodiments of this disclosure.

[0062] In embodiments of this disclosure, there is a one-to-one correspondence between different client services and the SSC channels that carry those client services. In one optional embodiment, each SSC channel may be assigned a channel identifier, SSCID. Identifying the time slots that constitute the SSC channels allows for the identification of the correspondence between client services and time slots.

[0063] Accordingly, in some embodiments, as shown in Figure 13, step S131 specifically includes steps S1311 and S1312. In step S1311, time slot information carrying the client service is set in the time slot identification field of the overhead area. In step S1312, SSC channel information carrying the client service is set in the channel identification field of the overhead area.

[0064] The time slot identification field is used to identify the time slot carrying the client service. The channel identification field is used to identify the SSC channel carrying the client service.

[0065] In embodiments of this disclosure, as one selectable embodiment, the time slot identifier may be a time slot number. If, in step S121, an SSF frame is divided to obtain multiple time slots, the time slots within the SSF frame are numbered, and the time slot number of each time slot is used as the time slot identifier. If, in step S121, an SSMF multiframe consisting of multiple SSF frames is divided to obtain multiple time slots, the time slots in all SSF frames constituting the SSMF multiframe are numbered to obtain the time slot number of each time slot.

[0066] In some embodiments, when an SSMF multiframe is configured with multiple SSF frames, as shown in Figure 14, step S131 includes step S1313 in addition to steps S1311 to S1312 described above. In step S1313, the multiframe instruction field in the overhead region is set with position information of the SSF frames in the SSMF multiframe consisting of multiple SSF frames.

[0067] In some embodiments, other overhead fields of the SSF frame include a frame type field for indicating the SSF frame structure, a fault indicator field for indicating a fault state of the service layer channel, a service type field for identifying the type of client service, and a check field for storing check information.

[0068] Sixth Embodiment In the sixth embodiment, the structure of the SSF frame is defined based on the IEEE 802.3 PCS layer 64 / 66B encoding standard. The definitions of the S block, D block, and T block that constitute the SSF frame are as described in the second embodiment.

[0069] In the sixth embodiment, the overhead is carried by the first 7 bytes of the first D block, totaling 56 bits. As shown in Figure 15, in the sixth embodiment, the overhead includes the following fields:

[0070] The FrameType field (4 bits) indicates a different SSF frame structure definition. For example, an SSF frame structure is defined as FrameType=0x1. For SSF frame structures of other FrameType types, the definition may be extended as needed.

[0071] Fault Indication Field RPF / RDI (1 bit): Indicates RPF (Remote PHY Fault) when the service layer is EthernetPHY. Indicates RDI (Remote Defect Indication) when the service layer is SCL / MTN channel. In one selectable embodiment, the RPF / RDI field is set to 1 if there is a failure in the local service layer, and the RPF / RDI field is set to 1 if there is no failure in the local service layer.

[0072] The MultiFrame instruction field MultiFrameSN (10 bits) indicates the sequence number within the multiframe of the SSF, incrementing from 1 and cyclically. In one optional embodiment, MultiFrameSN indicates the time slot number corresponding to the SSCMap and CS_TypeMap, i.e., time slot number = MultiFrameSN. In this case, the number of SSF frames within the multiframe is the same as the number of time slots.

[0073] Channel identification field SSCMap (20 bits): Indicates the SSCID number of the SSC channel to which the time slot belongs, and the time slot is indicated by MultiFrameSN.

[0074] The service type field CS_TypeMap (4 bits) indicates the service type to be carried in the time slot, which is indicated by MultiFrameSN. In one selectable embodiment, the values ​​of CS_TypeMap are defined as follows: 0000b indicates that no client service is carried, 0001b indicates that the carried client service is an Ethernet service, and 0010b indicates that the carried client service is a TDM service.

[0075] Reserved (13-bit): Reserved, all values ​​are 0.

[0076] Check field CRC4 (4 bits): The CRC4 check information checks the first 52 bits (excluding CRC4) in the overhead. The algorithm polynomial is X4 + X + 1, and its initial value is 0. The most significant bit of the CRC check result is stored in bit 53, and the least significant bit is stored in bit 56. CRC4 can also be used to identify SSF frames.

[0077] In some embodiments, as shown in Figure 16, the service data processing method further includes step S140 after step S110. In step S140, an Operation Maintenance Management (OAM) block is inserted into a service block code stream consisting of service blocks of the same type of client service.

[0078] Furthermore, after the OAM block is inserted into the service block code stream, in step S120, the service block and OAM block of the client service are mapped to an SSF frame or an SSMF multiframe.

[0079] Seventh Embodiment In the seventh embodiment, the structure of the SSF frame is defined based on the IEEE 802.3 PCS layer 64 / 66B encoding standard. The definitions of the S block, D block, and T block that constitute the SSF frame are as described in the second embodiment.

[0080] In the seventh embodiment, the client service is packaged / encoded to generate a 64 / 66B block code stream. Within the SSC channel, OAM blocks may be inserted at the locations of inter-packet gaps (IPGs) in the service code stream. In the seventh embodiment, the OAM block insertion / extraction mechanism and the definition of the OAM blocks may use the same mechanism and definition as SPN's SCL OAM (or MTN's Path OAM).

[0081] In some embodiments, as shown in Figure 17, the service data processing method further includes step S150 after step S110. In step S150, a service idle block (Idle block) is inserted into the service block code stream, which consists of service blocks of the same type of client service.

[0082] The service idle block is a service block in which no client service is being delivered. In embodiments of this disclosure, service idle blocks may be added or removed to match the speed of the client service with the speed of the time slot.

[0083] Furthermore, after the service Idle block is inserted into the service block code stream, in step S120, the service block and OAM block of the client service are mapped to an SSF frame or SSMF multiframe.

[0084] In some embodiments, as shown in Figure 18, the service data processing method further includes step S160 after step S130. In step S160, interframe idle blocks are inserted between adjacent SSF frames depending on the speed of the SSF frames and the speed of the service layer port.

[0085] Eighth Embodiment In the eighth embodiment, the structure of the SSF frame is defined based on the IEEE 802.3 PCS layer 64 / 66B encoding standard. The definitions of the S block, D block, and T block that constitute the SSF frame are as described in the second embodiment.

[0086] In the eighth embodiment, an S block + D block + T block conforming to the definition of an SSF frame structure is called an SSF block. As shown in Figure 19, in the eighth embodiment, the data stream of the SSC channel consists of SSF blocks and inter-frame idle blocks. In Figure 19, block I is an inter-frame idle block. In the eighth embodiment, the block type of the inter-frame idle block is 0x1E, and there may be zero or more inter-frame idle blocks between SSF blocks. Matching the rate of SSF frames with the rate of the service layer may be performed by adding or removing inter-frame idle blocks in the SSC channel.

[0087] In some embodiments, the SSF frame according to the embodiments of this disclosure consists of 64 / 66B blocks conforming to the IEEE 802.3 coding standard.

[0088] In some embodiments, the SSF frame includes a start block, at least one data block, and a terminate block. The frame length of the SSF frame is fixed.

[0089] For definitions of SSF frames and the start block, data block, terminate block, etc., within SSF frames, please refer to the second embodiment, and a detailed explanation will not be repeated here.

[0090] In some embodiments, the service data processing method further includes carrying the payload of the SSF frame to the data block and / or the terminate block, and carrying the overhead of the SSF frame in at least one of the start block, the data block, and the terminate block.

[0091] Specific embodiments of carrying the overhead of the SSF frame to at least one of the start block, data block, and terminate block are referenced in the second to fifth embodiments, and a detailed description is not repeated here.

[0092] As described above, in the embodiments of this disclosure, the client service may be an Ethernet service or a TDM service.

[0093] Accordingly, in some embodiments, the client service includes an Ethernet service.

[0094] Furthermore, when Ethernet services are encoded using IEEE 802.3 PCS, a 64 / 66B block code stream is formed.

[0095] In some embodiments, the 64 / 66B blocks in the Ethernet service code stream are used as the service blocks in step S110. Also, in step S120, Ethernet service blocks of different client services are mapped to at least one of the SSF frames.

[0096] In some embodiments, in step S110, the Ethernet service block of the client service is compressed and transcoded to generate the service block.

[0097] Ninth Embodiment In the ninth embodiment, 256 / 257B coding is used to compress and transcode 64 / 66B blocks of Ethernet services to generate service blocks of Ethernet services.

[0098] In the ninth embodiment, the transcoding method from 64 / 66B encoding to 256 / 257B encoding conforms to the IEEE 802.3 standard. That is, four 64 / 66B blocks are compressed and transcoded into one 256 / 257B block.

[0099] Tenth Embodiment In the tenth embodiment, 65B coding is used to compress and transcode 64 / 66B blocks of Ethernet services to generate service blocks of Ethernet services.

[0100] In the tenth embodiment, when compressing and transcoding a 64 / 66B block into a 65B block, the two bits of the sink header of the 64 / 66B block are compressed to one bit. For example, only the first bit of the sink header of the 64 / 66B block may be taken and the second bit deleted. Alternatively, only the second bit of the sink header of the 64 / 66B block may be taken and the first bit deleted.

[0101] In some embodiments, the client service includes a time-division multiplexed TDM service.

[0102] Eleventh Embodiment Based on the Circuit Emulation Services over Ethernet (CESoETH) defined in the "MEF 8 Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks" standard issued by the MetroEthernetForum (MEF), the TDM service is mapped to and packaged in an Ethernet packet. According to the 9th or 10th embodiment, the TDM service generates a service block from the packaged Ethernet packet.

[0103] Twelfth Embodiment The bitstream of a fixed-rate TDM service is packaged and encoded as is using service bytes or bits to generate 64 / 66B blocks compliant with the IEEE 802.3 encoding standard as service blocks for the TDM service.

[0104] In some embodiments, as shown in Figure 20, the service data processing method further includes step S170 in addition to steps S110 to S130 described above. In step S170, service layer processing is performed on the SSF frame so that the SSF frame is transmitted through the service layer.

[0105] In some embodiments, the service layer includes one of the following: the physical layer of an IEEE 802.3 Ethernet port (Ethernet PHY), a slicing packet network (SPN), a metropolitan area transport network (MTN), flexible Ethernet (FlexE), and an optical transport network (OTN).

[0106] If the service layer is the physical layer (PHY) of an IEEE 802.3 Ethernet port, that is, if the source PE node transmits data via the IEEE 802.3 Ethernet PHY, then in step S170, specifically, the SSF frame is scrambled and distributed in 64 / 66B block format by the IEEE 802.3 Physical Coding Sublayer (PCS), transmitted from the Ethernet port via the Physical Media Adaptation Layer (PMA) and the Physical Media Related Layer Interface (PMD).

[0107] If the service layer is a Slicing Packet Network (SPN), Metropolitan Area Transport Network (MTN), Flexible Ethernet (FlexE), or Optical Transport Network (OTN), in step S170, the SSF frame is transmitted after the corresponding service layer processing has been performed.

[0108] Referring to Figure 21, a second aspect of the embodiments of the present disclosure provides a service data exchange method. This service data exchange method includes steps S210, S220, and S230. In step S210, the outbound port of each service block in the inbound SSF frame received by the inbound port is identified. Here, each inbound SSF frame carries a service block of multiple different client services. In step S220, the service blocks corresponding to the same outbound port are mapped to at least one outbound SSF frame. Here, each outbound SSF frame carries a service block of multiple different client services. In step S230, the outbound SSF frame is transmitted via the outbound port.

[0109] In a provider switching device (also called a provider or P-node), the port that receives SSF frames is the inbound port, and the port that transmits SSF frames is the outbound port. Accordingly, SSF frames received by the inbound port are inbound SSF frames, and SSF frames transmitted by the outbound port are outbound SSF frames.

[0110] In the embodiments of this disclosure, an inbound SSF frame received by the inbound port of a P node carries service blocks for multiple different client services, with each different client service corresponding to a different outbound port. The P node transmits each service block of the inbound SSF frame to its corresponding outbound port, and the outbound port maps and incorporates the service blocks of the different client services into the outbound SSF frame, then transmits the outbound SSF frame from the outbound port. Each outbound SSF frame carries a different client service.

[0111] Furthermore, an inbound port may receive an inbound SSMF multiframe consisting of multiple inbound SSF frames. On an outbound port, an outbound SSMF multiframe may be configured with multiple outbound SSF frames, and service blocks of different client services may be mapped to the SSMF multiframe.

[0112] The service data exchange method according to the embodiments of this disclosure establishes an SSC channel carrying different client services and enables simultaneous transmission of client services of different granularity by exchanging different client services between the inbound and outbound ports of a P node based on an SSF frame capable of carrying multiple different client services, or an SSMF multiframe consisting of multiple SSF frames. The service data exchange method according to the embodiments of this disclosure enables rigid channel transmission of services of different granularity, satisfying the requirements of low latency, low jitter, hard isolation, and different bandwidth transmission, and the minimum granularity of client services is no longer limited by conventional standards such as FlexE, SPN, and MTN. Furthermore, it can simultaneously support multiple Ethernet services and / or TDM services, and the service rate is flexible. In addition, it is possible to transmit SSF frames with any one of SPN, MTN, Ethernet, OTN, etc. as the service layer, achieving good compatibility with existing standard systems such as Ethernet, FlexE, SPN, MTN, and OTN.

[0113] As one optional embodiment, in an embodiment of the present disclosure, a time slot scheduling method may be used to perform time slot crossing at a P node from a time slot in an inbound SSMF frame to a time slot in an outbound SSF frame, or from a time slot in an inbound SSMF multiframe to a time slot in an outbound SSMF multiframe.

[0114] Accordingly, as shown in Figure 22, step S210 specifically includes step S211. In step S211, the outbound ports of service blocks in different inbound time slots received by the inbound port are identified. Here, the inbound slot is a time slot in at least one inbound SSF frame. Step S220 specifically includes step S221. In step S221, service blocks in different inbound time slots corresponding to the same outbound port are mapped to different outbound time slots. Here, the outbound time slot is a time slot in at least one outbound SSF frame.

[0115] Figure 23 shows one selectable embodiment of time slot crossing at node P.

[0116] In Figure 23, the P node is equipped with two inbound ports, SSCSI1 and SSCSI2, and two outbound ports, SSCSI3 and SSCSI4. The time slots in the inbound SSF frame received by SSCSI1 correspond to some of the time slots in the outbound SSF frame on SSCSI3, and the other part corresponds to some of the time slots in the outbound SSF frame on SSCSI4. Similarly, the time slots in the inbound SSF frame received by SSCSI2 correspond to some of the time slots in the outbound SSF frame on SSCSI3, and the other part corresponds to some of the time slots in the outbound SSF frame on SSCSI4.

[0117] In one selectable embodiment, in an embodiment of the present disclosure, the P node stores the correspondence between time slots of inbound SSF frames or inbound SSMF frames at different inbound ports and time slots of outbound SSF frames or outbound SSMF frames at different outbound ports.

[0118] Accordingly, in some embodiments, as shown in Figure 24, step S211 specifically includes step S2111. In step S2111, the outbound ports of service blocks in different inbound time slots received by the inbound ports are identified according to a time slot crossover configuration table in which the correspondence between each inbound time slot and each outbound time slot is stored.

[0119] In the embodiments of this disclosure, the time slot crossover configuration table may be pre-configured by a network manager, a software-defined network (SDN) controller, or a dynamic protocol.

[0120] In embodiments of this disclosure, there may be a small difference (less than 200 ppm) between the rates of each outbound port and each inbound port of a P node. As one optional embodiment, in the transmission direction, a service idle block may be added or removed in each time slot of an SSF frame or SSMF multiframe to achieve rate matching from the time slot of each inbound port to the time slot of each outbound port.

[0121] Accordingly, in some embodiments, as shown in Figure 25, the service data exchange method further includes steps S241 and / or S242 in addition to steps S211 to S221. In step S241, a service Idle block is added or removed in a service block code stream consisting of service blocks in the same outbound time slot, based on the rate of the local system clock and the outbound time slot. In step S242, a service Idle block is added or removed in a service block code stream consisting of service blocks in the same inbound time slot, based on the rate of the local system clock and the inbound time slot.

[0122] In the embodiments of this disclosure, step S241 may be performed only, and step S242 may not be performed. Alternatively, step S242 may be performed only, and step S241 may not be performed. Or, both steps S241 and S242 may be performed. For example, if it is necessary to match the rate of client services in an outbound time slot with the rate of the outbound time slot, step S241 is performed. If it is necessary to match the rate of client services in an inbound time slot with the rate of the inbound time slot, step S242 is performed. If it is necessary to match the rate of client services in an inbound time slot with the rate of the inbound time slot, and to match the rate of client services in an outbound time slot with the rate of the outbound time slot, both steps S241 and S242 are performed. Furthermore, this disclosure does not particularly limit the order in which steps S241 and / or step S242 are performed.

[0123] In embodiments of this disclosure, there may be a small difference between the outbound SSF frame rate and the outbound port rate. In one optional embodiment, interframe idle blocks may be inserted between SSF frames to match the SSF frame rate with the service layer rate.

[0124] Accordingly, in some embodiments, as shown in Figure 26, the service data exchange method further includes steps S251 and / or S252 in addition to steps S211 to S221. In step S251, inter-frame idle blocks are added or removed between outbound SSF frames on the same outbound port based on the local system clock and the outbound port rate (step S251). In step S252, inter-frame idle blocks are added or removed between inbound SSF frames on the same inbound port based on the local system clock and the inbound port rate.

[0125] In the embodiments of this disclosure, step S251 may be performed only, and step S252 may not be performed. Alternatively, step S252 may be performed only, and step S251 may not be performed. Furthermore, both steps S251 and S252 may be performed. For example, if it is necessary to match the SSF frame rate at an outbound port with the rate at the outbound port, step S251 is performed. If it is necessary to match the SSF frame rate at an inbound port with the rate at the inbound port, step S252 is performed. If it is necessary to match the SSF frame rate at an inbound port with the service tier rate at the inbound port, and to match the SSF frame rate at an outbound port with the service tier rate at the outbound port, both steps S251 and S252 are performed. Also, this disclosure does not particularly limit the order in which steps S251 and / or step S252 are performed.

[0126] In some embodiments, the inbound port and / or the outbound port includes one of the following: an Ethernet port, a slice channel layer (SCL) port, an MTN path channel port, a FlexE client port, and an ODUk interface for OTN.

[0127] Referring to Figure 27, a third aspect of an embodiment of the present disclosure provides a service data extraction method. This service data extraction method includes steps S310 and S320. In step S310, a service block of a predetermined client service is extracted from at least one SSF frame, where each SSF frame carries a plurality of different client service service blocks. In step S320, the service block of the predetermined client service is decoded to extract the service data of the predetermined client service.

[0128] In the embodiments of this disclosure, the predetermined client service is a client service transmitted from the source PE node to the current sink PE node. When the sink PE node receives an SSF frame or SSMF multiframe, it extracts the service block of the predetermined client service from the SSF frame or SSMF multiframe, decodes the service block of the predetermined client service, and extracts the service data of the client service.

[0129] Furthermore, decrypting the service block of a given client service on a sink PE node is the reverse process of generating the service block according to the client service on a source PE node.

[0130] According to the service data extraction method according to the embodiments of this disclosure, a predetermined client service is extracted from an SSF frame capable of carrying multiple different client services, or from an SSMF multiframe consisting of multiple SSF frames, an SSC channel is established from a source PE node to a sink PE node, and the bandwidth of the SSC channel corresponding to client services of different granularity is different. The service data extraction method according to the embodiments of this disclosure enables the transmission of services of different granularity over a rigid channel, satisfying the transmission requirements of low latency, low jitter, hard isolation, and different bandwidths, and the minimum granularity of client services is no longer limited by conventional standards such as FlexE, SPN, and MTN. Furthermore, it can support multiple Ethernet services and / or TDM services simultaneously, and the service rate is flexible. In addition, it is possible to transmit SSF frames with any one of SPN, MTN, Ethernet, OTN, etc. as the service layer, achieving good compatibility with existing standard systems such as Ethernet, FlexE, SPN, MTN, and OTN.

[0131] As one optional embodiment, in an embodiment of the present disclosure, the sync PE node may extract service blocks of a given client service from time slots of an SSF frame or SSMF multiframe by a time slot scheduling scheme.

[0132] Accordingly, in some embodiments, as shown in Figure 28, step S310 specifically includes step S311. In step S311, a service block of a predetermined client service is extracted from a predetermined time slot of an SSF frame, where the predetermined time slot is a time slot that carries a predetermined client service within at least one SSF frame.

[0133] In some embodiments, as shown in Figure 29, the service data extraction method further includes step S312 following step S311. In step S312, the OAM blocks extracted from the predetermined time slots are separated.

[0134] As described above, in the embodiments of this disclosure, the client service may be an Ethernet service or a TDM service.

[0135] Accordingly, in some embodiments, the predetermined client service includes an Ethernet service.

[0136] In some embodiments, if the source PE node uses a 64 / 66B block in the code stream of an Ethernet service as the service block for a predetermined service, in step S320, it decodes the 64 / 66B Ethernet service block of the predetermined client service that conforms to the IEEE 802.3 encoding standard and extracts the service data for the predetermined client service.

[0137] In some embodiments, the source PE node compresses and transcodes the Ethernet service block of a predetermined client service to generate a service block of the predetermined client service. In this case, it is necessary to decompress the service block of the predetermined client service into a 64 / 66B Ethernet service block compliant with the IEEE 802.3 encoding standard, decode the 64 / 66B Ethernet service block, and extract the service data of the predetermined client service.

[0138] 13th Embodiment In the 13th embodiment, the source PE node compresses and transcodes a 64 / 66B block of Ethernet service using 256 / 257B encoding to generate a service block for the predetermined client service. Accordingly, the sink PE node decompresses the service block for the predetermined client service into a 64 / 66B Ethernet service block using 256 / 257B encoding.

[0139] The transcoding method from 256 / 257B encoding to 64 / 66B encoding conforms to the IEEE 802.3 standard. In other words, one 256 / 257B block is decompressed and transcoded into four 64 / 66B blocks.

[0140] Embodiment 14 In the 14th embodiment, the source PE node compresses and transcodes a 64 / 66B block of an Ethernet service using 65B coding to generate a service block for the predetermined client service. Accordingly, the sink PE node decompresses the service block for the predetermined client service into a 64 / 66B Ethernet service block using 65B coding.

[0141] Furthermore, if the first bit in the sink header of the 64 / 66B block is deleted when the source PE node compresses and transcodes a 64 / 66B block into a 65B block, in the 14th embodiment, one bit is added before the first bit in the sink header of the 65B block. If the second bit in the sink header of the 64 / 66B block is deleted when the source PE node compresses and transcodes a 64 / 66B block into a 65B block, in the 14th embodiment, one bit is added after the first bit in the sink header of the 65B block.

[0142] In some embodiments, the predetermined client service includes a time-division multiplexed TDM service.

[0143] Embodiment 15 In the 15th embodiment, the source PE node maps and packages the TDM service to an Ethernet packet based on the Circuit Emulation Services over Ethernet (CESoETH) specified in the "MEF 8 Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks" standard issued by the MetroEthernetForum (MEF), and generates a service block for the predetermined client service according to the 9th or 10th embodiment. Accordingly, the sink PE node demaps the service block for the predetermined client service to a TDM service code stream according to CESoETH and extracts the service data for the predetermined client service from the TDM service code stream.

[0144] Embodiment 16 In the sixteenth embodiment, the source PE node packages and encodes a bitstream of a TDM service at a constant rate using service bytes or bits to generate a 64 / 66B block compliant with the IEEE 802.3 encoding standard, which serves as the service block for the predetermined client service. Accordingly, the sink PE node decodes the 64 / 66B block into a TDM service code stream according to the IEEE 802.3 encoding standard and extracts the service data for the predetermined client service from the TDM service code stream.

[0145] Embodiment 17 In the 17th embodiment, as shown in Figure 30, the service layer is Ethernet, and an end-to-end SSC channel capable of carrying services with flexible granularity, i.e., a Sub Slicing Channel in Figure 30, is established by the time slot intersection of the Ethernet link and the SSC layer of the P node. As shown in Figure 30, the connections between the source PE node and the P node, and between the sink PE node and the P node, are both standard Ethernet connections (such as 10GE). Client services transmitted over these two Ethernet connections form an end-to-end SSC channel from the PE source node to the PE sink node via an SSC time slot intersection at the P node.

[0146] Embodiment 18 In the 18th embodiment, as shown in Figure 31, the service layer is an SPN, and the slicing channel connection provided by the SPN and the time slot intersection of the SSC layer at the P3 node establish an end-to-end SSC channel capable of carrying services with flexible granularity, i.e., sub-slicing channels 1-5 in Figure 31. As shown in Figure 31, the SCL intersection at P nodes P2 and P4 forms the service layer channels Slicing Channel 1-3 and Slicing Channel 3-5 of the SSC channel. In these two SCL channels, the SSC channel carrying Client Service A forms an end-to-end SSC channel carrying Client Service A from PE1 to PE5 nodes, i.e., sub-slicing channels 1-5 in Figure 31, through a time slot intersection at the P3 node.

[0147] In the case of SCL crossing of the SPN SCL layer between P2 and P4 nodes, since the SSF frame has a standard S+D+T structure, the SSF frame itself is service data for the SCL (or MTN Path), and the SCL (or MTN Path) does not need to perceive the SSF frame and can complete the SCL (or MTN Path) crossing as is. The SCL (or MTN Path) crossing method for P2 or P4 nodes is as shown in Figure 32.

[0148] Furthermore, the P2 and P4 nodes only perform SCL (or MTN Path) crossings and do not need to sense SSF frames, so conventional SPN devices are sufficient. On the other hand, the PE1, P3, and PE5 nodes are devices that support the SSC channel. Therefore, the 14th embodiment is also a scenario in which devices that support the SSC channel and conventional SPN devices communicate with each other.

[0149] A fourth aspect of the embodiments of this disclosure provides a provider edge device (PE). This provider edge device (PE) comprises one or more processors 101, a memory 102 that stores one or more programs and, when the one or more programs are executed by the one or more processors, causes the one or more processors to implement one of the above-mentioned service data exchange methods, and one or more I / O interfaces 103 connected between the processors and the memory and arranged to enable information communication between the processors and the storage device.

[0150] Here, the processor 101 is a device capable of processing data, and includes, but is not limited to, a central processing unit (CPU). The memory 102 is a device capable of storing data, and includes, but is not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH). The I / O interface (read / write interface) 103 is connected between the processor 101 and the memory 102 and enables information communication between the processor 101 and the memory 102, and includes, but is not limited to, a data bus (Bus).

[0151] In some embodiments, the processor 101, memory 102, and I / O interface 103 are connected to each other via a bus 104 and further connected to other components of the computing device.

[0152] Furthermore, the PE device functions as a source PE node when transmitting data and as a sink PE node when receiving data.

[0153] The service data processing method and the service data extraction method have been described in detail above and will not be repeated here.

[0154] Referring to Figure 34, a fifth aspect of the embodiments of the present disclosure provides a provider exchange device. This provider exchange device comprises one or more processors 201, a memory 202 which stores one or more programs and, when the one or more programs are executed by the one or more processors, causes the one or more processors to implement one of the above-described service data exchange methods, and one or more I / O interfaces 203 connected between the processors and the memory and arranged to enable information communication between the processors and the memory.

[0155] Here, the processor 201 is a device capable of processing data, and includes, but is not limited to, a central processing unit (CPU). The memory 202 is a device capable of storing data, and includes, but is not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH). The I / O interface (read / write interface) 203 is connected between the processor 201 and the memory 202 and enables information communication between the processor 201 and the memory 202, and includes, but is not limited to, a data bus (Bus).

[0156] In some embodiments, the processor 201, memory 202, and I / O interface 203 are connected to each other via a bus 204 and further connected to other components of the computing device.

[0157] The service data exchange method has been explained in detail above, so it will not be repeated here.

[0158] Referring to Figure 35, a sixth aspect of the embodiments of this disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, it enables any one of the above-described service data processing methods, any one of the above-described service data exchange methods, or any one of the above-described service data extraction methods. The computer-readable medium includes, but is not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH).

[0159] The service data processing method, the service data extraction method, and the service data exchange method have been described in detail above and will not be repeated here.

[0160] Those skilled in the art will understand that all or some of the functional modules / units in the steps, systems, and devices disclosed above may be implemented as software, firmware, hardware, or appropriate combinations thereof. In the case of hardware, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components. For example, one physical component may have multiple functions, or multiple physical components may cooperate to perform a single function or step. Some or all of the physical components may be implemented as software executed by a processor such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit such as an application-specific integrated circuit. Such software may be distributed on computer-readable media, including computer storage media (or non-temporary media) and communication media (or temporary media). As those skilled in the art know, the term computer storage media includes volatile and non-volatile media, removable and non-removable media, implemented in any method or technique for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tapes, magnetic disk storage or other magnetic storage devices, or other media that store desired information and can be accessed from a computer. It is also known to those skilled in the art that communication media typically include computer-readable instructions, data structures, program modules, other data in modulated data signals such as carrier waves or other transmission mechanisms, and any information distribution media.

[0161] The specific terms used in the embodiments of this disclosure should be interpreted as general descriptive terms and not as limiting. It will be obvious to those skilled in the art that, in some examples, unless otherwise explicitly stated, features, characteristics, and / or elements described in a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in another embodiment. Accordingly, it will be understood that various modifications are possible without departing from the scope of this disclosure as described in the appended claims.

Claims

1. Based on the service data of multiple client services, a service block for each of the said client services is generated, Mapping each of the client service's service blocks and / or operation and maintenance management (OAM) blocks to the payload area of ​​at least one sub-slicing frame (SSF), Set the overhead area field for each SSF frame so that at least one SSF frame is obtained, Includes, Each of the aforementioned SSF frames carries a service block of multiple different client services. Mapping each of the client service's service blocks and / or operation and maintenance management (OAM) blocks to the payload area of ​​at least one sub-slicing frame SSF is: Dividing the payload region of at least one SSF frame into multiple time slots, Each of the client service's service blocks and / or operation and maintenance management (OAM) blocks is mapped to a different time slot in the plurality of time slots, Includes, After generating a service block for each of the client services based on the service data of multiple client services, Inserting an operation, maintenance, and management OAM block into a service block code stream consisting of service blocks of the same type of client service, After generating a service block for each of the client services based on the service data of multiple client services, Inserting a service idle block into a service block code stream consisting of service blocks of the same type of client service, This further includes at least one of the following: A method for processing service data using a computer.

2. The aforementioned SSF frame consists of 64B / 66B blocks conforming to the IEEE 802.3 encoding standard. The service data processing method according to claim 1.

3. The SSF frame includes a start block, at least one data block, and a terminate block, and the frame length of the SSF frame is fixed. The service data processing method according to claim 2.

4. The data block and / or the termination block carry the payload of the SSF frame, In at least one of the start block, the data block, and the terminate block, the overhead of the SSF frame is carried. The service data processing method according to claim 3, further comprising:

5. In mapping the service block and / or operation and maintenance management (OAM) block of each client service to the payload area of ​​at least one sub-slicing frame SSF, the service block and / or operation and maintenance management (OAM) block of each client service is mapped to the payload area of ​​a plurality of SSF frames. Dividing the payload region of the aforementioned at least one SSF frame into multiple time slots is, This includes dividing the payload region of a sub-slicing multi-frame SSMF, which includes a plurality of the aforementioned SSF frames, into the plurality of time slots. The service data processing method according to claim 1.

6. Mapping each of the client service's service blocks and / or operation and maintenance management (OAM) blocks to different time slots in the plurality of time slots is: In accordance with the granularity of different client services, the location and number of time slots carrying different client services within the aforementioned multiple time slots are identified, Based on the location and number of time slots carrying different client services, the service blocks and / or Operational Maintenance Management (OAM) blocks of different client services are mapped to the corresponding time slots. The service data processing method according to claim 1, including the method described in claim 1.

7. Setting the overhead area field for each SSF frame to obtain at least one SSF frame is: In the overhead region of at least one SSF frame, a correspondence is established between each client service and the time slot that carries each client service. The process involves setting other overhead fields for the at least one SSF frame and obtaining the at least one SSF frame, Includes, In the overhead region of at least one SSF frame, setting a correspondence between each client service and the time slot that carries each client service is: The time slot identification field in the overhead area is set to contain information about the time slot carrying the client service. The channel identification field in the overhead area is set to contain information about the SSC channel carrying the client service, The service data processing method according to claim 1, including the method described in claim 1.

8. In dividing the payload region of at least one SSF frame into multiple time slots, the payload regions of multiple SSF frames are divided into multiple time slots. In the overhead region of at least one SSF frame, setting a correspondence between each client service and the time slot that carries each client service is: The overhead region further includes setting position information of the SSF frames in an SSMF multiframe consisting of multiple SSF frames in the multiframe instruction field of the overhead region. The service data processing method according to claim 7.

9. Other overhead fields of the aforementioned SSF frame are: A frame type field for indicating the structure of the aforementioned SSF frame, A failure indicator field to show the failure status of the service layer channel, A service type field to identify the type of client service, A check field for storing check information and The service data processing method according to claim 7, including the method described in claim 7.

10. After setting the overhead area field of each SSF frame to obtain at least one sub-slicing frame SSF, the service data processing method: Depending on the rate of the SSF frames and the rate of the service layer port, the further includes inserting inter-frame idle blocks between adjacent SSF frames. The service data processing method according to claim 1.

11. The aforementioned client service includes an Ethernet service, Generating a service block for each of the client services based on the service data of multiple client services is: The client service will be a 64B / 66B Ethernet service block that conforms to the IEEE 802.3 encoding standard, The client service compresses and transcodes a 64B / 66B Ethernet service block compliant with the IEEE 802.3 encoding standard to generate the service block. including at least one of the following The service data processing method according to claim 2.

12. Compressing and transcoding a 64B / 66B Ethernet service block compliant with the IEEE 802.3 encoding standard for client services to generate the said service block is: Using 256B / 257B encoding, the 64B / 66B Ethernet service block is compressed and transcoded into a 256B / 257B block compliant with the IEEE 802.3 standard, Using 65B coding, the 64B / 66B Ethernet service block is compressed into a 65B block and transcoded, It includes at least one of the following: Using 65B coding, compressing and transcoding the 64B / 66B Ethernet service block into a 65B block is: This includes obtaining the 65B block by deleting one bit in the sink header of the 64B / 66B Ethernet service block according to a predetermined rule, wherein the predetermined rule includes deleting the first bit of the sink header or deleting the second bit of the sink header. The service data processing method according to claim 11.

13. The aforementioned client service includes a time-division multiplexing (TDM) service, Generating a service block for each of the client services based on the service data of multiple client services is: Based on the Ethernet line emulation service (CESoETH), the service code stream of the TDM service is mapped to the Ethernet service code stream to generate an Ethernet service block, Encoding the service code stream of the TDM service to generate 64B / 66B blocks compliant with the IEEE 802.3 encoding standard, including at least one of the following The service data processing method according to claim 2.

14. The service layer further includes processing the SSF frame so that it is transmitted via the service layer. The service data processing method according to claim 1.

15. Identifying the outbound port of each service block within the inbound SSF frame received by the inbound port, Mapping service blocks corresponding to the same outbound port to at least one outbound SSF frame, Transmitting the outbound SSF frame via the outbound port, Includes, Here, each of the aforementioned inbound SSF frames carries a service block of multiple different client services. Each of the aforementioned outbound SSF frames carries a service block of multiple different client services. The payload region of the aforementioned SSF frame is divided into multiple time slots, Each of the client service service blocks and / or operation and maintenance management (OAM) blocks is mapped to a different time slot in the plurality of time slots. The operation and maintenance management OAM block is inserted into a service block code stream consisting of service blocks of the same type of client service, and the service idle block is inserted into a service block code stream consisting of service blocks of the same type of client service, further comprising at least one of these: A method of exchanging service data using computers.

16. Extracting a service block of a given client service from at least one SSF frame, Decrypting the service block of the predetermined client service and extracting the service data of the predetermined client service, Includes, Here, each of the aforementioned SSF frames carries a service block of multiple different client services. The payload region of the at least one SSF frame is divided into multiple time slots, Each of the client service service blocks and / or operation and maintenance management (OAM) blocks is mapped to a different time slot in the plurality of time slots. The operation and maintenance management OAM block is inserted into a service block code stream consisting of service blocks of the same type of client service, and the service idle block is inserted into a service block code stream consisting of service blocks of the same type of client service, further comprising at least one of these: A method for extracting service data using a computer.

17. When a computer program is stored and the program is executed by a processor, the service data processing method described in any one of claims 1 to 14, the service data exchange method described in claim 15, or the service data extraction method described in claim 16 is realized. Computer-readable media.

Images