A service carrying, extraction method, data exchange method and device

Abstract

The present disclosure provides a service carrying method, a data exchange method, a service extraction method, an operator edge device, an operator switching device, and a computer-readable storage medium. The service carrying method and the service extraction method are applied to the operator edge device PE node, and the data exchange method is applied to the operator switching device P node. The service carrying method includes: mapping the customer service to the flexible channel sublayer FCS information element, the FCS information element includes the channel identifier of the flexible channel FlexC carrying the customer service, and all FlexCs constitute the flexible channel sublayer FCS; according to the granularity of the customer service, the FlexC carrying the customer service is mapped to the service layer channel of the FCS to send the FCS information element. The present disclosure can flexibly support customer services of different granularities, and at the same time, it is well compatible with existing Ethernet, FlexE, SPN, MTN, OTN and other standard systems.

Description

Technical Field

[0001] The present disclosure relates to the field of communications, and in particular, to a service bearing method, a data exchange method, a service extraction method, an operator edge device, an operator switching device, and a computer-readable storage medium. Background Art

[0002] Flexible Ethernet (FlexE) technology was initiated by the International Organization for Standardization (OIF) in March 2015, and the relevant technical standards were officially voted and approved in March 2016. Flexible Ethernet technology provides a universal mechanism to transmit a series of services with different media access control (MAC) rates, which can be a single service with a relatively large MAC rate or a collection of services with relatively small MAC rates. It is no longer limited to services with a single MAC rate.

[0003] However, the current FlexE standard has limitations on service granularity and lacks compatibility with networks of different architectures. Summary of the invention

[0004] To solve at least one aspect of the above-mentioned problems existing in the prior art, the present disclosure provides a service carrying method, a data exchange method, a service extraction method, an operator edge device, an operator switching device, and a computer-readable storage medium.

[0005] As a first aspect of the present disclosure, a service bearing method is provided, which is applied to an operator edge server PE node, including:

[0006] Mapping the customer service into a flexible channel sublayer FCS cell, wherein the FCS cell includes a channel identifier of a flexible channel FlexC carrying the customer service, and all FlexCs constitute a flexible channel sublayer FCS;

[0007] The FlexC carrying the customer service is mapped to the service layer channel of the FCS according to the granularity of the customer service to send the FCS cell.

[0008] Optionally, the step of mapping the FlexC carrying the customer service to the service layer channel of the FCS according to the granularity of the customer service to send the FCS cell includes:

[0009] Determine a target time slot according to the granularity of the customer service, where the target time slot is a time slot allocated to the FlexC in the service layer channel;

[0010] The FCS cell is transmitted via the target time slot.

[0011] Optionally, the step of determining the target time slot according to the granularity of the customer service includes:

[0012] The service layer channel is divided into a plurality of unit time slots according to the rate of the service layer channel and the granularity of the customer service, and each n consecutive unit time slots constitute a time slot cycle, wherein n is a positive integer, and the number n of the unit time slots in a time slot cycle is determined according to the rate of the service layer channel and the rate of the unit time slot;

[0013] The number and position of the unit time slots serving as the target time slots in each time slot cycle are determined according to the granularity of the customer service and the rate of the unit time slots.

[0014] Optionally, the number of unit time slots in one time slot cycle is calculated by the following formula:

[0015] n=R sr ×(1-100ppm)×E c ×E OH / [R m (1+100ppm)]

[0016] Where n is the number of unit time slots in a time slot cycle, R sr is the service layer channel rate, R m is the rate of the unit time slot, E c is the FCS cell encapsulation efficiency, E OH is the service layer channel overhead efficiency.

[0017] Optionally, the step of determining the target time slot according to the granularity of the customer service includes:

[0018] Dividing the service layer channel into one or more levels of time slots, wherein the next level of time slots of the multiple levels of time slots is a sub-time slot of the previous level of time slots;

[0019] According to the granularity of the customer service and the rate of the i-level time slot, determine the number and position of the i-level time slots as the target time slots in the i-level time slots,

[0020] Wherein, i is the number of the time slot level in the multi-level time slot, and the i-level time slot is obtained by dividing at least one i-1-level time slot, and an i-1-level time slot is divided into m i i-level time slots, m i is a positive integer determined according to the rate of the i-1 level time slot and the rate of the i level time slot.

[0021] Optionally, the number of level i time slots divided from the level i-1 time slot is calculated according to the following formula:

[0022] m i =v i-1 / v i

[0023] Among them, m i is the number of i-1 level time slots divided into i-level time slots, v i-1 is the rate of the i-1 level time slot, v i is the rate of the i-level time slot, where i is a positive integer.

[0024] Optionally, the service bearing method further includes:

[0025] An idle FCS cell is sent in an idle time slot, where the idle time slot is a time slot other than a time slot allocated to the FlexC that carries customer services.

[0026] Optionally, the step of mapping the FlexC carrying the customer service to the service layer channel of the FCS according to the granularity of the customer service to send the FCS cell includes:

[0027] The FlexC is mapped to the service layer channel according to the packet queue scheduling method to send the FCS cell.

[0028] Optionally, the service layer channel includes any one of an Ethernet channel, a sliced ​​packet network SPN channel, a metropolitan area transport network MTN channel, a flexible Ethernet FlexE channel, and an optical transmission network OTN channel.

[0029] Optionally, the FCS cell includes at least one of a cell header, operation and maintenance information, and a payload.

[0030] Optionally, the step of mapping the customer service into the FCS cell includes:

[0031] Mapping the service code stream of the customer service to the payload;

[0032] The channel identifier is configured in the cell header.

[0033] Optionally, the FCS cell is composed of 64 / 66B blocks that comply with IEEE 802.3 coding specifications.

[0034] Optionally, the 64 / 66B blocks constituting the FCS cell include a start block, at least one data block, and a termination block, and the cell length of the FCS cell is fixed.

[0035] Optionally, the step of mapping the customer service into the FCS cell includes:

[0036] Mapping the service code stream of the client service to the at least one data block and / or the termination block;

[0037] The channel identifier is configured in the starting block or the designated data block.

[0038] Optionally, the starting block includes:

[0039] A flexible channel label, used to identify a flexible channel FlexC that carries the customer service;

[0040] A cell identifier, used to distinguish the start block of the FCS cell from the start block of the IEEE 802.3 standard cell;

[0041] Business type, used to identify the type of the customer's business;

[0042] Sequence number, used to count the cycles of FSC cells sent by FlexC;

[0043] Verification information, used to verify the data in the starting block;

[0044] Operation and maintenance information.

[0045] Optionally, each of the data blocks and the termination block includes a data area;

[0046] The step of mapping the service code stream of the client service to the at least one data block and / or the termination block comprises:

[0047] Map the service code stream of the client service to the data area of ​​the data block and / or the data area of ​​the termination block.

[0048] Optionally, the customer service is an Ethernet service;

[0049] The step of mapping the service code stream of the customer service to the data area of ​​the data block and / or the data area of ​​the termination block includes:

[0050] Each service block in the Ethernet service code stream is mapped to the data area of ​​the data block and / or the data area of ​​the termination block.

[0051] Optionally, the customer service is an Ethernet service;

[0052] The step of mapping the service code stream of the customer service to the data area of ​​the data block and / or the data area of ​​the termination block includes:

[0053] Compressing and transcoding the Ethernet service code stream;

[0054] Each service block of the compressed and transcoded Ethernet service code stream is mapped to the data area of ​​the data block and / or the data area of ​​the termination block.

[0055] Optionally, the customer service is a time division multiplexing TDM service;

[0056] The step of mapping the service code stream of the customer service to the data area of ​​the data block and / or the data area of ​​the termination block includes:

[0057] Converting the TDM service code stream into an Ethernet service code stream;

[0058] Each service block in the Ethernet service code stream is mapped to the data area of ​​the data block and / or the data area of ​​the termination block.

[0059] Optionally, the customer service is a time division multiplexing TDM service;

[0060] The step of mapping the service code stream of the customer service to the data area of ​​the data block and / or the data area of ​​the termination block includes:

[0061] The TDM service code stream is mapped to the data area of ​​the data block and / or the data area of ​​the termination block according to the service bytes.

[0062] As a second aspect of the present disclosure, a data exchange method is provided, which is applied to a switching device P node, including:

[0063] Modify the inbound channel identifier in the inbound FCS cell received by the inbound port to an outbound channel identifier, and generate an outbound FCS cell, wherein the inbound FCS cell is the FCS cell in the service bearing method according to the first aspect of the present disclosure, the inbound channel identifier is the channel identifier of the inbound flexible channel FlexC that carries the customer service, and the outbound channel identifier is the channel identifier of the outbound FlexC that carries the customer service;

[0064] The outgoing FCS cell is sent through an outgoing port.

[0065] Optionally, the step of sending the outgoing FCS cell through the outgoing port includes:

[0066] Determine an outbound timeslot of an outbound port allocated to an outbound FlexC carrying the customer service;

[0067] The outbound FCS cell is sent via the outbound time slot.

[0068] Optionally, the inbound port and / or the outbound port includes any one of an Ethernet port, a slice channel layer SCL port, an MTN Path channel port, a FlexE Client port, and an ODUk interface of OTN.

[0069] As a third aspect of the present disclosure, a service extraction method is provided, which is applied to a PE node, comprising:

[0070] Extracting an FCS cell from the received cell code stream according to the channel identifier, wherein the FCS cell is an outbound FCS cell in the data exchange method according to the second aspect of the present disclosure;

[0071] The FCS cell is demapped to obtain customer services.

[0072] As a fourth aspect of the present disclosure, a PE device is provided, the PE device comprising:

[0073] A storage module on which an executable program is stored;

[0074] One or more processors, wherein the one or more processors are capable of calling the executable program so that the one or more processors implement the service carrying method described in the first aspect of the present disclosure, or the service extraction method described in the third aspect of the present disclosure.

[0075] As a fifth aspect of the present disclosure, an operator switching device is provided, where the operator switching device is applied to a P node and includes:

[0076] A storage module on which an executable program is stored;

[0077] One or more processors, wherein the one or more processors are capable of calling the executable program so that the one or more processors implement the data exchange method described in the second aspect of the present disclosure.

[0078] As the sixth aspect of the present disclosure, a computer-readable storage medium is provided, on which an executable program is stored. When the executable program is executed, it can implement the service carrying method described in the first aspect of the present disclosure, or the data exchange method described in the second aspect of the present disclosure, or the service extraction method described in the third aspect of the present disclosure.

[0079] The present disclosure proposes an FCS cell and a flexible channel FlexC based on the FCS cell. The FlexC can carry customer services of different granularities and is no longer subject to the restrictions on the minimum customer service granularity of existing standards such as FlexE, SPN, and MTN. It realizes the transmission of flexible granular services in rigid pipes and meets the transmission requirements of low latency, low jitter, hard isolation, and flexible bandwidth. In the present disclosure, customer services can be Ethernet services or fixed-rate TDM services with flexible service rates. In addition, in the present disclosure, any one of SPN, MTN, Ethernet, OTN, etc. can be used as the service layer of FCS, achieving good compatibility with existing Ethernet, FlexE, SPN, MTN, OTN and other standard systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] The accompanying drawings are used to provide a further understanding of the present disclosure and constitute a part of the specification. Together with the following specific embodiments, they are used to explain the present disclosure but do not constitute a limitation of the present disclosure. In the accompanying drawings:

[0081] Figure 1 is a flow chart of an implementation of the service bearing method in the present disclosure;

[0082] Figure 2 is a schematic diagram of the flexible granular service bearing hierarchy in the present disclosure;

[0083] Figure 3 is a flow chart of another implementation of the service bearing method in the present disclosure;

[0084] Figure 4 is a flow chart of another implementation of the service bearing method in the present disclosure;

[0085] Figure 5 is a schematic diagram of an implementation method of time slot division in the present disclosure;

[0086] Figure 6 is a schematic diagram of an implementation method of a flexible channel mapping method in the present disclosure;

[0087] Figure 7 is a flow chart of another implementation of the service bearing method in the present disclosure;

[0088] Figure 8 is a schematic diagram of an implementation method of multi-level time slot division in the present disclosure;

[0089] Fig. 9 is a flow chart of another implementation of the service bearing method in the present disclosure;

[0090] Fig.10 is a flow chart of another implementation of the service bearing method in the present disclosure;

[0091] Fig.11 is a schematic diagram of an implementation of the FCS cell structure in the present disclosure;

[0092] Fig.12 is a flow chart of another implementation of the service bearing method in the present disclosure;

[0093] Fig.13 is a flow chart of another implementation of the service bearing method in the present disclosure;

[0094] Fig.14 is a flow chart of another implementation of the service bearing method in the present disclosure;

[0095] Fig.15is a schematic diagram of an implementation method for mapping customer services to FCS cells;

[0096] Fig.16 This is a schematic diagram of the transcoding specification from 64 / 66B encoding to 256 / 257B encoding;

[0097] Fig.17 is a schematic diagram of another implementation method of mapping customer services to FCS cells;

[0098] Fig.18 It is a schematic diagram of TDM service mapping and encapsulation into Ethernet messages;

[0099] Fig.19 is a flow chart of an implementation of the data exchange method in the present disclosure;

[0100] Fig. 20 is a flow chart of another implementation of the data exchange method in the present disclosure;

[0101] Fig.21 is a flow chart of an implementation of the business extraction method in the present disclosure;

[0102] Fig. 22 is a module schematic diagram of an implementation of a PE device in the present disclosure;

[0103] Fig.23 It is a module schematic diagram of an implementation mode of the operator switching device in the present disclosure;

[0104] Fig.24 is a schematic diagram of an implementation of a computer-readable storage medium in the present disclosure;

[0105] Fig.25 is a schematic diagram of an end-to-end FlexC based on Ethernet in the present disclosure;

[0106] Fig.26 is a schematic diagram of an end-to-end FlexC based on SPN in the present disclosure;

[0107] Fig. 27 It is a schematic diagram of SCL exchange in end-to-end FlexC based on SPN;

[0108] Fig.28 It is a schematic diagram of an implementation of the data exchange method in the present disclosure. DETAILED DESCRIPTION

[0109] The specific embodiments of the present disclosure are described in detail below in conjunction with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to illustrate and explain the present disclosure, and are not used to limit the present invention.

[0110] The Slicing Packet Network (SPN) and Metro Transport Network (MTN) use FlexE as the service layer to implement end-to-end service rigid pipes (Channels). However, the customer service granularity supported by the current FlexE, SPN, and MTN standards is N*5Gb / s (N≧1), that is, the minimum customer service granularity carried is 5Gb / s, and hard isolation and rigid pipes for services less than 5Gb / s are not supported; in addition, the minimum service granularity supported by the Optical Transport Network (OTN) technology is 1.25Gb / s, and services less than 1.25Gb / s are not yet supported. The inventors of the present invention have found that the methods for supporting small-granularity customer services in the prior art are all to make improvements on the time slots of the original 5G particles of FlexE, and there are mainly the following problems: (1) There are still restrictions on the service granularity. For example, the service granularity is required to be no less than 1Gb / s, and small-granularity services such as 10Mb / s or 100Mb / s are not supported; (2) The flexibility is low. Although the transmitted services are no longer limited to services with a single MAC rate, it is difficult to support mixed transmission of small-granularity customer services of different granularities in a single 5G time slot; (3) There is a lack of compatibility. It is not compatible with the current Ethernet, FlexE, SPN, and MTN standards, and cannot communicate with existing equipment. For example, it cannot pass through the P (Provider) node of the standard SPN equipment.

[0111] In view of this, as a first aspect of the present disclosure, a service bearing method is provided, which is applied to an operator edge server PE node, such as Figure 1 As shown, the service bearing method includes:

[0112] In step S110, the customer service is mapped into a flexible channel sublayer FCS information element, wherein the FCS information element includes a channel identifier of a flexible channel FlexC that carries the customer service, and all FlexCs constitute a flexible channel sublayer FCS;

[0113] In step S120, the FlexC carrying the customer service is mapped to the service layer channel of the FCS according to the granularity of the customer service to send the FCS cell.

[0114] In the present disclosure, there is no special limitation on the type of the customer service. Figure 2 As shown, the client service (Client) can be an Ethernet service (Ethernet Service) or a time division multiplexing (TDM, Time Division Multiplexing) service (TDM Service) with a fixed rate.

[0115] The present disclosure does not make any special limitation on the granularity of the customer service. The customer service may be a service with a granularity smaller than 5G, for example, the granularity of the customer service is 1Gb / s, 100Mb / s, 10Mb / s, etc.; it may also be a 5G granular service, that is, the granularity of the customer service is 5Gb / s; it may also be a service with a granularity larger than 5G, for example, the granularity of the customer service is 6Gb / s, 8Gb / s, etc.

[0116] In the present disclosure, a Flexible Channel Sublayer (FCS) cell is proposed, and a Flexible Channel (FlexC) is proposed based on the FCS cell. In step S110 of the present disclosure, a service code stream of a customer service, such as a service code stream of an Ethernet service or a service code stream of a TDM service, is encapsulated and mapped into an FCS cell according to the cell structure of the FCS cell, and the customer service can be sent through the FlexC.

[0117] In the present disclosure, each FlexC has its channel identifier, and each FlexC corresponds to a customer service. In the same provider edge server (PE, Provider Edge), the channel identifiers of different FlexCs are different. As an optional implementation, in different PE nodes, the channel identifiers of FlexCs carrying the same customer service can be the same or different.

[0118] In the present disclosure, the channel identifier is configured in the FCS cell to distinguish different customer services and determine the FlexCs that carry the customer services respectively. All FlexCs that carry different customer services constitute the FCS. It should be noted that in the present disclosure, the granularity of the customer services carried by each FlexC is not required to be the same, that is, the FCS can carry customer services of different rates, such as Ethernet services or TDM services of different rates.

[0119] It should be noted that the FlexC described in the present disclosure is a logical channel established between different PE nodes, and the FCS is a logical channel sublayer. For example, FCS is a channel sublayer located between the physical coding sublayer (PCS) and the media access control layer (MAC) of IEEE802.3. FCS sends customer services through its service layer. When the FCS cell is sent through the service layer channel of FCS in step S120, each FlexC carrying different customer services is mapped to the service layer channel of FCS according to the granularity of the customer service, and the FCS cell can be sent out. The present disclosure does not make any special limitation on the FCS service layer. For example, Figure 2 As shown, the service layer of FCS can be the slicing channel layer (SCL) of SPN, that is, Figure 2 The SPN SCL in the MTN can also be the Path layer of MTN, that is, Figure 2 The MTN Path in it can also be FlexE or the Ethernet port physical layer (PHY). Figure 2 In addition, the service layer of FCS can also be the optical transport network (OTN, Optical Transport Network).

[0120] It is understandable that when the FCS cell is sent through the service layer channel, it needs to be processed by the corresponding service layer before being sent. For example, when the service layer channel is Ethernet PHY, the FCS cell needs to go through the scrambling, block distribution, physical medium adaptation layer (PMA), physical medium association layer interface (PMD) of the PCS, and then be sent out from the Ethernet port.

[0121] The service carrying method provided in the present disclosure proposes an FCS cell and a flexible channel FlexC based on the FCS cell. The FlexC can carry customer services of different granularities and is no longer subject to the restrictions on the minimum customer service granularity of existing standards such as FlexE, SPN, and MTN. It realizes the transmission of flexible granular services in rigid pipelines and meets the transmission requirements of low latency, low jitter, hard isolation, and flexible bandwidth. In the present disclosure, customer services can be Ethernet services or fixed-rate TDM services, and the service rate is flexible. In addition, in the present disclosure, any one of SPN, MTN, Ethernet, OTN, etc. can be used as the service layer of FCS, achieving good compatibility with existing Ethernet, FlexE, SPN, MTN, OTN and other standard systems.

[0122] As an optional implementation, in step S120 of the present disclosure, the FlexC carrying the customer service is mapped to the service layer channel of the FCS by means of time slot scheduling, so as to ensure that the FCS provides a fixed rate bandwidth and rigid isolation for the carried customer service. Figure 3 As shown, step S120 specifically includes:

[0123] In step S1211, a target time slot is determined according to the granularity of the customer service, where the target time slot is a time slot allocated to the FlexC in the service layer channel;

[0124] In step S1212, the FCS cell is sent via the target time slot.

[0125] It should be noted that, in step S1211, different customer services correspond to different target time slots, and each target time slot can be regarded as a FlexC. It should also be noted that the target time slots corresponding to different customer services include at least one time slot of a service layer channel. In the service layer channel, on the basis of the rate determination of the service layer channel, the service rate that can be carried by each target time slot allocated to the FlexC is also determined, and each target time slot matches the granularity of the customer service it carries.

[0126] The present disclosure provides an optional implementation for determining the target time slot, such as Figure 4 As shown, step S1211 specifically includes:

[0127] In step S1211a, the service layer channel is divided into a plurality of unit time slots according to the rate of the service layer channel and the granularity of the customer service, and each n consecutive unit time slots constitute a time slot cycle, wherein n is a positive integer, and the number n of the unit time slots in a time slot cycle is determined according to the rate of the service layer channel and the rate of the unit time slots;

[0128] In step S1211b, the number and position of unit time slots serving as the target time slots in each time slot cycle are determined according to the granularity of the customer service and the rate of the unit time slots.

[0129] In order to further explain step S1211a to step S1211b, a specific embodiment of determining the target time slot through step S1211a to step S1211b is provided.

[0130] Embodiment 1

[0131] like Figure 5As shown, the time slot of the service layer channel is divided into a series of unit time slots, each of which can be used to send cells. The rate of the unit time slot is determined according to parameters such as the service layer channel rate and the customer service granularity.

[0132] In this embodiment, there is no special limitation on how to determine the rate of the unit time slot. For example, when sending customer services, the service rate of the customer services to be sent can be used as the rate of the unit time slot according to the granularity of the customer services to be sent, and the service layer channels can be divided; when sending multiple customer services with different granularities at the same time, the service rate of the customer services with the smallest granularity can be used as the rate of the unit time slot to divide the service layer channels; the rate of the unit time slot can also be determined based on the relationship between the service rates of customer services with different granularities, for example, the common divisor of the service rates of each customer service with different granularities is taken as the rate of the unit time slot to divide the service layer channels. It should be noted that the above examples are only for illustrative explanation of this embodiment and are not intended to limit the present invention.

[0133] In this embodiment, every n consecutive unit time slots constitute a time slot cycle (Slot-Cycle), and the number n of the unit time slots in a time slot cycle is determined according to the rate of the service layer channel and the rate of the unit time slot. In this embodiment, the number of the unit time slots in a time slot cycle is determined by formula (1):

[0134] v slot =v c / n (1)

[0135] Among them, v slot is the rate per time slot, v c is the rate of the service layer channel, and n is the number of unit time slots in one time slot cycle.

[0136] In this embodiment, the customer service is carried by FlexC. In each time slot cycle, the same FlexC can be mapped to one or more unit time slots, that is, the target time slot can be one or more unit time slots. The relationship between the number of unit time slots used as target time slots in a time slot cycle, the rate of FlexC, and the rate of the unit time slot satisfies formula (2):

[0137] v FlexC =q×v slot (2)

[0138] Among them, v FlexC is the rate of FlexC, v slotis the rate of the unit time slot, and q is the number of unit time slots as target time slots in one time slot cycle.

[0139] In this embodiment, the service rates of customer services of different granularities are different, and for different customer services, the number of unit time slots serving as their target time slots is also different. Figure 6 FIG. 1 is a schematic diagram of mapping FlexCs carrying customer services of different granularities to unit time slots of a service layer channel. Figure 6 As shown in the figure, the service rate of client A is 3 Gb / s, so the rate of FlexC A carrying Client A should be 3 Gb / s; the service rate of client B is 2 Gb / s, so the rate of FlexC A carrying Client A should be 2 Gb / s; the rate of the unit time slot is 1 Gb / s. According to formula (2), the number of unit time slots allocated to FlexC A is 3, and the number of unit time slots allocated to FlexC B is 2.

[0140] In this embodiment, there is no special limitation on how to determine the position of the unit time slots allocated to the same FlexC in a time slot cycle. For example, the unit time slots allocated to the same FlexC are evenly distributed in the time slot cycle.

[0141] In the present disclosure, the number n of the unit time slots in one time slot cycle is related to the rate of the service layer channel and the rate of the unit time slot, as well as the efficiency of cell encapsulation, the efficiency of service layer overhead, etc. Accordingly, as an optional implementation, in step S1211a, the number of the unit time slots in one time slot cycle is determined by formula (3):

[0142] n=R sr ×(1-100ppm)×E c ×E OH / [R m (1+100ppm)] (3)

[0143] Where n is the number of unit time slots in a time slot cycle, R sr is the service layer channel rate, R m is the rate of the unit time slot, E c is the FCS cell encapsulation efficiency, E OH is the service layer channel overhead efficiency.

[0144] Embodiment 2

[0145] In this embodiment, the service layer of FCS is 10GE Ethernet, that is, the rate of the service layer channel is 10Gb / s, the rate of the unit time slot is 10Mb / s, the ratio of the service payload length to the cell length of the FCS cell is 28 / 30, and the service layer overhead of Ethernet is 1, then:

[0146] R sr =10×10 9 bit / s;

[0147] R sr =10×10 6 bit / s;

[0148] E c =0.933;

[0149] E OH =1;

[0150] From formula (3), we can get n=933.

[0151] In order to more flexibly adapt to the simultaneous transmission of customer services of different granularities, reduce the number of time slots, and facilitate time slot scheduling, as an optional implementation method, the present disclosure proposes a multi-level time slot structure. Figure 7 As shown, step S1211 specifically includes:

[0152] In step S1211c, the service layer channel is divided into one or more levels of time slots, wherein the next level of time slots of the multiple levels of time slots is a sub-time slot of the previous level of time slots;

[0153] In step S1211d, according to the granularity of the customer service and the rate of the i-level time slot, the number and position of the i-level time slot as the target time slot in the i-level time slot are determined, wherein i is the number of the time slot level in the multi-level time slot, and the i-level time slot is obtained by dividing at least one i-1-level time slot, and an i-1-level time slot is divided into m i i-level time slots, m i is a positive integer determined according to the rate of the i-1 level time slot and the rate of the i level time slot.

[0154] As an optional implementation, the number of level i time slots divided from level i-1 time slots is calculated according to formula (4):

[0155] m i =v i-1 / v i (4)

[0156] Among them, m i is the number of i-1 level time slots divided into i-level time slots, v i-1 is the rate of the i-1 level time slot, vi is the rate of the i-level time slot, where i is a positive integer.

[0157] In order to further explain step S1211c to step S1211d, a specific embodiment of determining the target time slot through step S1211a to step S1211b is provided.

[0158] Embodiment 3

[0159] like Figure 8 As shown, the service layer channel is divided into x levels of time slots from 0 to x-1, wherein the jth level time slot is a sub-time slot of the j-1th level time slot, and the j+1th level time slot is a sub-time slot of the jth level time slot, that is, the multi-level time slot structure is obtained through recursive division. Specifically, a j-1th level time slot is divided into m j time slots to get j-level time slots, and divide a j-level time slot into m j+1 The rate of the j-level time slot and the rate of the j-level time slot satisfy the formula (5):

[0160] v j =v j-1 / m j (5)

[0161] Among them, v j is the rate of the j-level time slot, v j-1 is the rate of the j-1 level time slot, m j A j-1 level time slot is divided into m j time slots to obtain j-level time slots.

[0162] It should be noted that the level 0 time slot is obtained by dividing the service layer channel, and each m0 continuous level 0 time slots constitute a level 0 time slot cycle. The number m0 of the level 0 time slots in a level 0 time slot cycle is determined according to the rate of the service layer channel and the rate of the level 0 time slot. In this embodiment, the relationship between the rate of the level 0 time slot, the rate of the service layer channel, and the number of the level 0 time slots in a level 0 time slot cycle satisfies formula (6):

[0163] v0=v c / m0 (6)

[0164] Among them, v0 is the rate of the 0-level time slot, v c is the rate of the service layer channel, and m0 is the number of the level 0 time slots in one time slot cycle.

[0165] In this embodiment, when determining the target time slot for a customer service, first, based on the granularity of the customer service and the time slot rate of each time slot level in the multi-level time slots, the time slot level (for example, level j) in which the time slot serving as the target time slot for the customer service is located is determined, and then, in the level j time slots, based on the granularity of the customer service and the rate of the level j time slots, the number and position of the level j time slots serving as the target time slots are determined.

[0166] It should be noted that the number and position of the j-level time slots as target time slots refer to the number and position of the j-level time slots in each 0-level time slot cycle. It should also be noted that for customer services with different granularities, the time slot levels of the time slots as their target time slots may be different, while for customer services with the same time slot level but different granularities, the number and position of the time slots as their target time slots are different.

[0167] In the present disclosure, the FCS cell also includes an idle FCS cell, which is an FCS cell that does not carry customer services. The FCS cell is used for rate adjustment. Accordingly, as an optional implementation, Fig. 9 As shown, step S120 includes steps S1211 to S1212, and further includes:

[0168] In step S1213, an idle FCS cell is sent in an idle time slot, where the idle time slot is a time slot other than the time slot allocated to the FlexC that carries the customer service.

[0169] As another optional implementation, in step S120 of the present disclosure, the FlexC carrying the customer service is mapped to the service layer channel of the FCS by using a packet scheduling method. Fig.10 As shown, step S120 specifically includes:

[0170] In step S122, the FlexC is mapped to the service layer channel according to the packet queue scheduling method to send the FCS cell.

[0171] The present disclosure does not specifically limit the packet scheduling method. For example, the FCS cell can be sent through a priority queue (PQ), a weighted fair queue (WFQ), or a deficit weighted round robin queue (DWRR).

[0172] As mentioned above, the service bearing method provided by the present disclosure is compatible with existing Ethernet, FlexE, SPN, MTN, OTN and other standard systems. Accordingly, as an optional implementation, the service layer channel includes any one of an Ethernet channel, a sliced ​​packet network SPN channel, a metropolitan area transport network MTN channel, a flexible Ethernet FlexE channel, and an optical transport network OTN channel.

[0173] As an optional implementation manner, the FCS cell in step S110 includes at least one of a cell header, operation and maintenance information, and a payload.

[0174] In the present disclosure, there is no special limitation on the combination of the three parts of the FCS cell, namely, the cell header, the operation and maintenance information, and the payload. For example, the FCS cell may include the cell header + the operation and maintenance information, or the cell header + the payload, or the cell header + the operation and maintenance information + the payload.

[0175] Fig.11 An optional implementation of the FCS cell structure is shown. Fig.11 In the figure, Header represents the cell header, OAM represents the operation and maintenance information, and Payload represents the payload.

[0176] Further, as an optional implementation, as Fig.12 As shown, step S110 specifically includes:

[0177] In step S1111, mapping the service code stream of the customer service to the payload;

[0178] In step S1112, the channel identifier is configured in the cell header.

[0179] As another optional implementation, the FCS cell in step S110 is composed of 64 / 66B blocks that comply with IEEE 802.3 coding specifications.

[0180] Accordingly, as an optional implementation manner, the 64 / 66B blocks constituting the FCS cell include a start block, at least one data block, and a termination block, and the cell length of the FCS cell is fixed.

[0181] In the FCS cell proposed in the present disclosure, the control information is carried in the start block, and the customer service is carried in the data block and / or the end block. Accordingly, Fig.13 As shown, step S110 specifically includes:

[0182] In step S1121, mapping the service code stream of the client service to the at least one data block and / or the termination block;

[0183] In step S1122, the channel identifier is configured in the starting block or the designated data block.

[0184] In the present disclosure, the starting block is extended to carry the cell header and operation administration and maintenance (OAM) information in the starting block. Accordingly, as an optional implementation, the starting block optionally includes:

[0185] A cell identifier, used to distinguish the start block of the FCS cell from the start block of the IEEE 802.3 standard cell;

[0186] A flexible channel label, used to identify a flexible channel FlexC that carries the customer service;

[0187] Business type, used to identify the type of the customer's business;

[0188] Sequence number, used to count the cycles of FSC cells sent by FlexC;

[0189] Verification information, used to verify the data in the starting block;

[0190] Operation and maintenance information.

[0191] Embodiment 4

[0192] In this embodiment, the start block (S block), the data block (D block), and the terminate block (T block) are 66B blocks that comply with the IEEE 802.3 PCS 64 / 66B encoding specification.

[0193] The cell identifier CM is located at bit 10 to bit 11 of the S block and has a value of 10b. It is used to identify and distinguish FCS cells from standard S blocks of IEEE802.3.

[0194] The flexible channel label (FCI, FlexC Identifier) ​​is located in bits 12 to 31 of the S block. The FCI is used to identify different FlexCs (which also correspond to different customer services) and is valid within the node. The FCIs of FlexCs in different internal FCS server layer ports (FCS SI, FCS Server Interface) can be the same, but different FlexCs in the same FCS server layer port must be distinguished by different FCIs.

[0195] The service type ST is located in bits 32 to 34 of the S block. ST = 001b indicates Ethernet service, and ST = 010b indicates TDM service. ST = 000b indicates that the FCS cell is an idle cell and does not carry any customer service. ST = 111b indicates that the FCS cell is a dedicated overhead cell.

[0196] The sequence number SEQ is located in bits 35 to 42 of the S block. SEQ is used to cyclically count the FCS cells sent by FlexC, for example, counting from 0x00 to 0xFF, and so on. SEQ can be used by the receiving side to check whether there is cell loss, and can also be used for multi-frame counting of specific OAM. The counting range is set as needed;

[0197] The CRC4 check information is located in bits 62 to 65 of the S block, and the 60 bits in bits 2 to 61 of the S block are checked. The algorithm polynomial is: X 4 +X+1, the initial value is 0. The high bit of the CRC4 check result is stored in bit62, and the lowest bit is stored in bit65. CRC4 can also be used for FCS cell identification (combined with the cell identifier CM for double verification), so as to distinguish it from the standard S block.

[0198] The OAM information is located in bits 43 to 61 of the S block.

[0199] In this embodiment, the OAM fields are defined as follows:

[0200] Type: 4 bits (bit 43 to 46), identifying different types of operations, maintenance and management functions, such as CC (connectivity check), BIP check, RDI, REI, CV (connectivity verification), delay measurement, etc.

[0201] Value: 15 bits (bit 47 to 61), the content of a specific type of OAM message;

[0202] Type=0x1 is defined as a BASE code block, and its OAM fields are defined in detail as shown in Table 1.

[0203] Table 1

[0204]

[0205] Other types of OAM can be expanded and defined as needed.

[0206] It should be noted that in the present disclosure, a partial bit area may be extended and defined in the termination block to store OAM information, or a partial data block may be used to store OAM information, for example, the first data block may be used to store OAM information, and the present disclosure is not limited to the fourth embodiment. The fourth embodiment of the present disclosure is only used to explain the present disclosure and does not constitute a limitation on the present disclosure.

[0207] The embodiment described above is only a specific implementation process of the present invention. Any easily conceivable changes in cell length, OAM length, position, etc. are all within the scope of protection of this patent.

[0208] In the FCS cell that complies with the 64 / 66B encoding specification defined by IEEE 802.3, the start block (S block, StartBlock), the data block (D block, Data Block), and the termination block (T block, Terminate Block) are 66B blocks that comply with the IEEE 802.3PCS64 / 66B encoding specification. In the 66B block, a synchronization header (sync header) and a data area are included. The synchronization header is used to distinguish between a control block and a data block, wherein the S block and the T block belong to the control block, and the D block belongs to the data block. Accordingly, as an optional implementation, each of the data block and the termination block includes a synchronization header and a data area.

[0209] Furthermore, if Fig.14 As shown, step S1121 specifically includes:

[0210] In step S1121a, the service code stream of the client service is mapped to the data area of ​​the data block and / or the data area of ​​the termination block.

[0211] In the present disclosure, the client service may be an Ethernet service or a time division multiplexing (TDM) service with a fixed rate.

[0212] When the client service is an Ethernet service, the Ethernet service is coded by the PCS of IEEE 802.3 to form a service code stream of 64 / 66B blocks. The FCS cell in the present disclosure complies with the 64 / 66B coding specification defined by IEEE 802.3, so the 64 / 66B block of the Ethernet service can be directly mapped to the FCS cell. In addition, the 64 / 66B block of the Ethernet service can be transcoded and compressed by compression coding, and then mapped to the FCS cell, thereby saving the cell space.

[0213] The following are specific embodiments of mapping Ethernet services to FCS cells, wherein Embodiment 5 directly maps 64 / 66B blocks of Ethernet services to the FCS cells; Embodiment 6 transcodes and compresses 64 / 66B blocks of Ethernet services and then maps them to FCS cells.

[0214] Embodiment 5

[0215] like Fig.15As shown in the figure, taking the FCS cell length of 30 64 / 66B blocks as an example, the FCS cell consists of 1*S block + 28*D block + 1*T block, a total of 1980 bits. Then the cell payload length = 28 D block payloads + T block payload = 28*64bit + 56bit = 1848bit, which can just store 28 64 / 66B service blocks of Ethernet services (28*66 = 1848bit).

[0216] Embodiment 6

[0217] The 64 / 66B-encoded service code stream is first transcoded into the 256 / 257B encoding format and then mapped to the payload area of ​​the FCS cell, thereby saving cell space.

[0218] The transcoding method from 64 / 66B encoding to 256 / 257B encoding follows the IEEE 802.3 standard, that is, four 66-bit blocks (a total of 264 bits) can be transcoded and compressed into a 257-bit block. The transcoding method from 64 / 66B encoding to 256 / 257B encoding in the IEEE 802.3 standard is as follows: Fig.16 shown.

[0219] like Fig.17 As shown, taking the FCS cell length of 30 64 / 66B blocks as an example, that is, the FCS cell consists of 1*S block + 28*D block + 1*T block, a total of 1980 bits. Then the FCS cell payload length = 28 D block payloads + T block payload = 28*64bit + 56bit = 1848bit, which can store 7 257bit blocks (a total of 7*257 = 1799bit). The FCS cell payload area (1848bit) has 49 bits after storing 7 257bit blocks (1799bit), of which the last 32bits are used for CRC32 check to check all D blocks and T blocks, and the remaining 17bits are temporarily reserved, which can be expanded to control information such as OAM in the future. The 7 257bit blocks contain 28 64 / 66B service blocks before transcoding.

[0220] When the customer service is a TDM service, the service code stream of the TDM service can be first mapped and encapsulated into an Ethernet message, and then the Ethernet message encapsulating the TDM service can be mapped into an FCS cell according to the steps described in Example 5 or Example 6 of the present disclosure; the service code stream of the TDM service can also be mapped into the FCS cell by direct mapping.

[0221] Specific embodiments of mapping TDM services to FCS cells are given below, among which Embodiment 7 is to first map and encapsulate the service code stream of the TDM service into an Ethernet message, and then map the Ethernet message encapsulating the TDM service into the FCS cell according to the steps described in Embodiment 5 or Embodiment 6 of the present disclosure; Embodiment 8 is to map the service code stream of the TDM service into the FCS cell by direct mapping.

[0222] Embodiment 7

[0223] According to the CESoETH (Circuit Emulation Services over Ethernet) method specified in the standard "MEF 8 Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks" issued by the standards organization MEF (Metro Ethernet Forum), TDM services are mapped and encapsulated into Ethernet packets. Fig.18 The figure shows the process of mapping and encapsulating TDM services into Ethernet packets. Fig.18 As shown, the Ethernet service layer (Ethernet Service Layer) in the TDM service is mapped to the destination address (Destination Address), source address (Source Address), virtual VLAN tags (optional) (VLAN tags (optional)), Ethernet type (Ethertype) and other fields of the Ethernet message, and the adaptation function (Adaptation Function) is mapped to the emulated circuit identifier (ECID, Emulated Circuit Identifier), Ethernet emulation service control field (cesOeth Control Word), real-time transport protocol field (optional) (RTP (optional)) and other fields of the Ethernet message, and the CES application data (CES Application Data) is used as the TDM information field (TDM Payload) of the Ethernet message.

[0224] The Ethernet message encapsulating the TDM service is mapped to the FCS cell in accordance with the manner of mapping the Ethernet service to the FCS cell in the fifth or sixth embodiment, so as to complete the mapping and encapsulation of the TDM service to the FCS cell.

[0225] Embodiment 8

[0226] In this embodiment, the service code stream of the constant rate TDM service is directly mapped into the payload of the FCS cell according to service bytes or bits.

[0227] Take the FCS cell length of 30 64 / 66B blocks as an example, that is, the FCS cell consists of 1*S block + 28*D block + 1*T block, a total of 1980 bits. Then the cell payload length = 28 D block payloads + T block payload = 28*64bit + 56bit = 1848bit = 231byte, that is, it can store 231 bytes (1848bit) of service content.

[0228] As a second aspect of the present disclosure, a data exchange method is provided, which is applied to a switching device (or referred to as a P node), such as Fig.19 As shown, the data exchange method includes:

[0229] In step S210, the inbound channel identifier in the inbound FCS cell received by the inbound port is modified to an outbound channel identifier, and an outbound FCS cell is generated, wherein the inbound FCS cell is the FCS cell in the service bearing method according to the first aspect of the present disclosure, the inbound channel identifier is the channel identifier of the inbound flexible channel FlexC that carries the customer service, and the outbound channel identifier is the channel identifier of the outbound FlexC that carries the customer service;

[0230] In step S220, the outgoing FCS cell is sent through the outgoing port.

[0231] It should be noted that the inbound port in step S210 is the port in the P node that receives the FCS cell, and the outbound port is the port that sends the FCS cell.

[0232] In the present disclosure, each FlexC has its channel identifier, and each FlexC corresponds to a customer service. In the same FCS service layer port of the P node, the channel identifiers of different FlexCs are different. In different FCS service layer ports of the P node, the channel identifiers of the FlexCs carrying the same customer service can be the same or different.

[0233] In the data exchange method disclosed in the present disclosure, the P node stores the channel identifier of the FlexC that carries each customer service in each FCS service layer port. In step S210, the inbound channel identifier in the inbound FCS cell received by the inbound port is modified to the outbound channel identifier, so that the outbound port for sending the outbound FCS cell can be determined. In step S220, the outbound FCS cell is sent out from the outbound port, thereby completing the connection of the FCS service layer of different PE nodes and the FlexC exchange of FCS, and establishing an end-to-end FlexC between different PE nodes.

[0234] In the present disclosure, the inbound port and the outbound port of the P node may be any one of an Ethernet port, a slicing channel layer (SCL) port, an MTN Path channel port, a FlexE Client port, and an ODUk interface of OTN.

[0235] The following are specific embodiments of establishing an end-to-end FlexC through the data exchange method provided by the present disclosure. Embodiment 9 is an end-to-end FlexC based on Ethernet, and embodiment 10 is an end-to-end FlexC based on SPN.

[0236] Embodiment 9

[0237] The FCS service layer of this embodiment is the Ethernet port physical layer (Ethernet PHY), and through the Ethernet link and the FlexC exchange of the FCS layer, an end-to-end FlexC that can carry flexible granular services is established. Fig.25 As shown in the figure, between nodes PE1 and P3, and between nodes PE5 and P3, standard 10GE Ethernet connections are used. The FCS cells of the customer service "Client Service A" carried in these two Ethernet connections are exchanged through FCS at the P3 node, thereby forming an end-to-end FlexC "Flexible Channel 1-5" carrying "Client Service A" from the PE1 node to the PE5 node.

[0238] Embodiment 10

[0239] In this embodiment, the FCS service layer is SPN SCL or MTN Path. The FCS service layer is SCL as an example for description. Through the Slicing Channel connection provided by SPN and the FlexC switching of the FCS layer, an end-to-end Flexible Channel that can carry flexible granular services is established. Fig.26 As shown in the figure, through the SCL exchange of P nodes P2 and P4, the service layer channels "Slicing Channel 1-3" and "Slicing Channel 3-5" of FCS are formed. The FCS cells carrying the customer service "Client Service A" in these two SCL channels are exchanged through FCS at the P3 node, thereby forming an end-to-end FlexC channel "Flexible Channel 1-5" carrying "Client Service A" from the PE1 node to the PE5 node.

[0240] For SCL switching at the SPN SCL layer, when the FCS cell is a standard S+D+T structure, the FCS cell is the payload for the SCL (or MTN Path). The SCL (or MTN Path) does not need to sense the FCS Cell and directly completes the SCL layer switching. The FlexC channel identifier in the FCS cell remains unchanged. The SCL switching method of the P node (for example, P2, P4) is as follows: Fig. 27 As shown (the method based on MTNPath exchange is similar). Fig. 27 In the process, the FCS cells received by the incoming slicing channel layer port (SCI, SlicingChannel Interface) are sent out from the corresponding outgoing SCI through SCL layer switching.

[0241] In addition, because P2 and P4 nodes only complete SCL exchange and do not need to perceive FCS cells, P2 and P4 can be traditional SPN devices, while PE1, P3, and PE5 are devices that support FCS. Therefore, this embodiment is also a scenario in which FCS devices and SPN devices communicate with each other.

[0242] The data exchange method provided in the present disclosure establishes an end-to-end flexible channel FlexC between different PE nodes through the connection of the FCS service layer of different PE nodes and the FlexC exchange of FCS. The FlexC can carry customer services of different granularities and is no longer subject to the restrictions of the existing FlexE, SPN, MTN and other standards on the minimum customer service granularity, so as to realize the transmission of flexible granular services in rigid pipelines and meet the transmission requirements of low latency, low jitter, hard isolation and flexible bandwidth. In the present disclosure, the customer service can be an Ethernet service or a fixed-rate TDM service with flexible service rate. In addition, in the present disclosure, any one of SPN, MTN, Ethernet, OTN, etc. can be used as the service layer of FCS, achieving good compatibility with existing Ethernet, FlexE, SPN, MTN, OTN and other standard systems.

[0243] In the present disclosure, when the source PE node sends an incoming FCS cell by means of time slot scheduling, after the P node receives the incoming FCS cell at the inbound port, it also performs time slot switching at the outbound port by means of time slot scheduling, and then sends the outbound FCS cell. Fig. 20 As shown, step S220 specifically includes:

[0244] In step S221, determining an outbound timeslot of an outbound port allocated to an outbound FlexC carrying the customer service;

[0245] In step S222, the outbound FCS cell is sent via the outbound time slot.

[0246] A specific embodiment of data exchange based on time slot exchange is given below.

[0247] Embodiment 11

[0248] like Fig.28 As shown, the P node receives an incoming FCS cell from the incoming port;

[0249] Identify the FlexC tag (FCI) carried by the incoming FCS cell, query the pre-configured FCS switching configuration table, transform the FCI according to the FCS switching configuration table, and determine the outgoing port and outgoing timeslot; send the cell after the FCI transformation from the outgoing timeslot.

[0250] In this embodiment, according to different service layers of FCS, Fig.28 The FCS service layer port (FCS SI, FCS Server Interface) in can be an Ethernet port, an SCL port, an MTN Path channel port, a FlexE Client port, or an ODUk (k=0, 1, 2, 3, 4, flex) interface of OTN.

[0251] In this embodiment, the FCS switching configuration table can be pre-configured by a network management, SDN controller or dynamic protocol. Fig.28 The FCS switching configuration table is shown in Table 2.

[0252] Table 2

[0253]

[0254] by Fig.28 For example, in the inbound FCS service layer port FCS SI 1, the FCI of FlexC A is 100. After the switching network receives the FCS cell of FlexC A from the time slot in the FCS SI 1 port, it is found through querying the FCS switching configuration table that the outbound port corresponding to the FlexC with FCI 100 in FCS SI 1 is FCS SI 3, and the FCI of the corresponding FlexC in FCS SI 3 is 300, and the corresponding time slot can be obtained. The switching network changes the FCI of the FCS cell from 100 to 300, and then sends the FCS cell of FlexC A to the FCS SI 3 port, and sends the FCS cell with FCI 300 out of the time slot allocated to FlexC A by FCS SI 3.

[0255] As a third aspect of the present disclosure, a service extraction method is provided, which is applied to a PE node, such as Fig.21 As shown, the business extraction method includes:

[0256] In step S310, according to the channel identifier, an FCS cell is extracted from the received cell code stream, wherein the FCS cell is an outbound FCS cell in the data exchange method according to the second aspect of the present disclosure;

[0257] In step S320, the FCS cell is demapped to obtain customer services.

[0258] It should be noted that, in step S320 of the present disclosure, the process of demapping the FCS cell is the reverse process of mapping the customer service to the FCS cell in the service bearing method described in the first aspect of the present disclosure.

[0259] The service extraction method provided in the present disclosure can receive FCS cells from FlexC and extract customer services from FCS cells. The FlexC can carry customer services of different granularities and is no longer subject to the restrictions on the minimum customer service granularity of existing standards such as FlexE, SPN, and MTN, so as to achieve transmission of flexible granular services in rigid pipelines and meet the transmission requirements of low latency, low jitter, hard isolation, and flexible bandwidth. In the present disclosure, customer services can be Ethernet services or fixed-rate TDM services with flexible service rates. In addition, in the present disclosure, any one of SPN, MTN, Ethernet, OTN, etc. can be used as the service layer of FCS, achieving good compatibility with existing Ethernet, FlexE, SPN, MTN, OTN and other standard systems.

[0260] As a fourth aspect of the present disclosure, a PE device 100 is provided, such as Fig. 22 As shown, the PE device 100 includes:

[0261] A storage module 110 on which an executable program is stored;

[0262] One or more processors 120, the one or more processors being capable of calling the executable program so that the one or more processors implement the service carrying method described in the first aspect of the present disclosure, or the service extraction method described in the third aspect of the present disclosure.

[0263] The service bearing method described in the first aspect and the service extraction method described in the third aspect of the present disclosure have been described in detail above and will not be repeated here.

[0264] As a fifth aspect of the present disclosure, an operator switching device 200 is provided, and the operator switching device 200 is applied to a P node, such as Fig.23 As shown, the operator switching device 200 includes:

[0265] A storage module 210 on which an executable program is stored;

[0266] One or more processors 220, wherein the one or more processors are capable of calling the executable program so that the one or more processors implement the data exchange method described in the second aspect of the present disclosure.

[0267] The data exchange method described in the second aspect of the present disclosure has been described in detail above and will not be repeated here.

[0268] As a sixth aspect of the present disclosure, a computer-readable storage medium 300 is provided. Fig.24 As shown, an executable program is stored on the computer-readable storage medium, and when the executable program is executed, it can implement the service carrying method described in the first aspect of the present disclosure, or the data exchange method described in the second aspect of the present disclosure, or the service extraction method described in the third aspect of the present disclosure.

[0269] The service bearing method described in the first aspect, the data exchange method described in the second aspect, and the service extraction method described in the third aspect of the present disclosure have been described in detail above and will not be repeated here.

[0270] Among them, computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer-readable storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage media, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0271] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present disclosure, but the present disclosure is not limited thereto. For those of ordinary skill in the art, various modifications and improvements can be made without departing from the spirit and substance of the present disclosure, and these modifications and improvements are also considered to be within the scope of protection of the present disclosure.

Claims

1. A service bearing method, applied to an operator edge device PE node, comprising: Mapping the customer service into a flexible channel sublayer FCS cell, wherein the FCS cell includes a channel identifier of a flexible channel FlexC carrying the customer service, and all FlexCs constitute a flexible channel sublayer FCS; Mapping the FlexC carrying the customer service to the service layer channel of the FCS according to the granularity of the customer service to send the FCS cell; Wherein, the FCS cell is composed of 64 / 66B blocks that comply with the IEEE 802.3 coding specification; The 64 / 66B blocks constituting the FCS cell include a start block; The starting block includes: A flexible channel label, used to identify a flexible channel FlexC that carries the customer service; A cell identifier, used to distinguish the start block of the FCS cell from the start block of the IEEE 802.3 standard cell; Business type, used to identify the type of the customer's business; Sequence number, used to count the cycles of FSC cells sent by FlexC; Verification information, used to verify the data in the starting block; Operation and maintenance information.

2. The service carrying method according to claim 1, wherein: The step of mapping the FlexC carrying the customer service to the service layer channel of the FCS according to the granularity of the customer service to send the FCS cell includes: Determine a target time slot according to the granularity of the customer service, where the target time slot is a time slot allocated to the FlexC in the service layer channel; The FCS cell is transmitted via the target time slot.

3. The service carrying method according to claim 2, wherein: The step of determining the target time slot according to the granularity of the customer service includes: The service layer channel is divided into a plurality of unit time slots according to the rate of the service layer channel and the granularity of the customer service. n The continuous unit time slots constitute a time slot cycle, wherein, n is a positive integer, the number of unit time slots in one time slot cycle n It is determined according to the rate of the service layer channel and the rate of the unit time slot; The number and position of the unit time slots serving as the target time slots in each time slot cycle are determined according to the granularity of the customer service and the rate of the unit time slots.

4. The service carrying method according to claim 3, wherein: The number of unit time slots in a time slot cycle is calculated by the following formula: in, n is the number of unit time slots in a time slot cycle, R sr is the service layer channel rate, R m is the rate of the unit time slot, E C is the FCS cell encapsulation efficiency, E OH is the service layer channel overhead efficiency.

5. The service carrying method according to claim 2, wherein: The step of determining the target time slot according to the granularity of the customer service includes: Dividing the service layer channel into one or more levels of time slots, wherein the next level of time slots of the multiple levels of time slots is a sub-time slot of the previous level of time slots; Based on the granularity of the customer's business i The rate of the time slot determines the i In the level time slot, the target time slot is the i The number and location of the time slots, in, i is the number of the time slot level in the multi-level time slot, i The time slot is to place at least one i-1 The time slot is divided into two levels, one i-1 The time slots are divided into m i indivual i Level time slot, m i According to the i-1 The rate of the time slot is the same as that of the i A positive integer that determines the rate of the level time slot.

6. The service carrying method according to claim 5, wherein: According to the following formula, the i-1 The time slots are divided into i Number of level time slots: m i =v i-1 / v i Among them, m i For the general i-1 The time slots are divided into i The number of time slots, v i-1 for i-1 The rate of the time slot, v i for i The rate of the time slot, i Is a positive integer.

7. The service carrying method according to claim 2, wherein: The service bearing method further includes: An idle FCS cell is sent in an idle time slot, where the idle time slot is a time slot other than a time slot allocated to the FlexC that carries customer services.

8. The service carrying method according to claim 1, wherein: The step of mapping the FlexC carrying the customer service to the service layer channel of the FCS according to the granularity of the customer service to send the FCS cell includes: The FlexC is mapped to the service layer channel according to the packet queue scheduling method to send the FCS cell.

9. The service carrying method according to any one of claims 1 to 8, wherein: The service layer channel includes any one of an Ethernet channel, a slice packet network SPN channel, a metropolitan area transport network MTN channel, a flexible Ethernet FlexE channel, and an optical transmission network OTN channel.

10. The service carrying method according to any one of claims 1 to 8, wherein: The FCS cell includes at least one of a cell header, operation and maintenance information, and a payload.

11. The service carrying method according to claim 10, wherein: The steps of mapping customer services into FCS cells include: Mapping the service code stream of the customer service to the payload; The channel identifier is configured in the cell header.

12. The service carrying method according to claim 1, wherein: The 64 / 66B blocks constituting the FCS cell also include at least one data block and a termination block, and the cell length of the FCS cell is fixed.

13. The service carrying method according to claim 12, wherein: The steps of mapping customer services into FCS cells include: Mapping the service code stream of the client service to the at least one data block and / or the termination block; The channel identifier is configured in the starting block or the designated data block.

14. The service carrying method according to claim 13, wherein: Each of the data blocks and the termination block includes a synchronization header and a data area; The step of mapping the service code stream of the client service to the at least one data block and / or the termination block comprises: Map the service code stream of the client service to the data area of ​​the data block and / or the data area of ​​the termination block.

15. The service carrying method according to claim 14, wherein: The customer service is an Ethernet service; The step of mapping the service code stream of the customer service to the data area of ​​the data block and / or the data area of ​​the termination block includes: Each service block in the Ethernet service code stream is mapped to the data area of ​​the data block and / or the data area of ​​the termination block.

16. The service carrying method according to claim 14, wherein: The customer service is an Ethernet service; The step of mapping the service code stream of the customer service to the data area of ​​the data block and / or the data area of ​​the termination block includes: Compress and transcode the Ethernet service code stream; Each service block of the compressed and transcoded Ethernet service code stream is mapped to the data area of ​​the data block and / or the data area of ​​the termination block.

17. The service carrying method according to claim 14, wherein: The customer service is a time division multiplexing (TDM) service; The step of mapping the service code stream of the customer service to the data area of ​​the data block and / or the data area of ​​the termination block includes: Converting the TDM service code stream into an Ethernet service code stream; Each service block in the Ethernet service code stream is mapped to the data area of ​​the data block and / or the data area of ​​the termination block.

18. The service carrying method according to claim 14, wherein: The customer service is a time division multiplexing TDM service; The step of mapping the service code stream of the customer service to the data area of ​​the data block and / or the data area of ​​the termination block includes: The TDM service code stream is mapped to the data area of ​​the data block and / or the data area of ​​the termination block according to the service bytes.

19. A data exchange method, applied to a switching device P node, comprising: Modify the inbound channel identifier in the inbound FCS cell received by the inbound port to an outbound channel identifier, and generate an outbound FCS cell, wherein the inbound FCS cell is the FCS cell in the service bearing method according to any one of claims 1 to 18, the inbound channel identifier is the channel identifier of the inbound flexible channel FlexC that carries the customer service, and the outbound channel identifier is the channel identifier of the outbound FlexC that carries the customer service; Sending the outgoing FCS cell through an outgoing port; Wherein, the FCS cell is composed of 64 / 66B blocks that comply with the IEEE 802.3 coding specification; The 64 / 66B blocks constituting the FCS cell include a start block; The starting block includes: A flexible channel label, used to identify a flexible channel FlexC that carries the customer service; A cell identifier, used to distinguish the start block of the FCS cell from the start block of the IEEE 802.3 standard cell; Business type, used to identify the type of the customer's business; Sequence number, used to count the cycles of FSC cells sent by FlexC; Verification information, used to verify the data in the starting block; Operation and maintenance information.

20. The data exchange method according to claim 19, wherein: The step of sending the outgoing FCS cell through the outgoing port comprises: Determine an outbound timeslot of an outbound port allocated to an outbound FlexC carrying the customer service; The outbound FCS cell is sent via the outbound time slot.

21. The data exchange method according to claim 19 or 20, wherein: The inbound port and / or the outbound port include any one of an Ethernet port, a slice channel layer SCL port, an MTN Path channel port, a FlexE Client port, and an ODUk interface of OTN.

22. A service extraction method, applied to a PE node, comprising: Extracting an FCS cell from the received cell code stream according to the channel identifier, wherein the FCS cell is an outgoing FCS cell in the data exchange method according to any one of claims 19 to 21; The FCS cell is demapped to obtain customer services.

23. A PE device, comprising: A storage module on which an executable program is stored; One or more processors, wherein the one or more processors are capable of calling the executable program so that the one or more processors implement the service carrying method described in any one of claims 1 to 18, or the service extraction method described in claim 22.

24. An operator switching device, the operator switching device being applied to a P node, comprising: A storage module on which an executable program is stored; One or more processors, wherein the one or more processors are capable of calling the executable program so that the one or more processors implement the data exchange method described in any one of claims 19 to 21.

25. A computer-readable storage medium having an executable program stored thereon, wherein the executable program, when executed, can implement the service carrying method described in any one of claims 1 to 18, or the data exchange method described in any one of claims 19 to 21, or the service extraction method described in claim 22.

Images