WO2017201953A1

WO2017201953A1 - Method and device for processing customer service

Info

Publication number: WO2017201953A1
Application number: PCT/CN2016/102740
Authority: WO
Inventors: 向俊凌
Original assignee: 华为技术有限公司
Priority date: 2016-05-25
Filing date: 2016-10-20
Publication date: 2017-11-30
Also published as: CN107438028B; CN107438028A

Abstract

Disclosed in the embodiments of the present invention are a method and a device for processing a customer service. The method for processing a customer service comprises: receiving a customer service, mapping the customer service to M slots according to a first forwarding label carried by the customer service, the first forwarding label indicating a first forwarding destination address; sending, by means of the M slots, the customer service to a target physical channel, the target physical channel corresponding to the first forwarding destination address; where M is a positive integer greater than or equal to 1. The technical solution of the present invention implements the switching of multiple services on the same switching plane of the Flexible Ethernet.

Description

Method and device for processing customer business

Technical field

The present invention relates to the field of communications, and in particular, to a method and device for processing a client service.

Background technique

Currently, the Optical Internetworking Forum (OIF) is discussing the expansion of traditional Ethernet technologies to support sub-rate, channelization, and reverse multiplexing applications for Ethernet services, and to expand Ethernet technology. It is called Flexible Ethernet (FlexE) technology. For example, the application scenario of the sub-rate for the Ethernet service can support the transmission of the 250G Ethernet service by using three existing 100GE Physical Medium Dependent (PMD). The application scenario of the reverse multiplexing of the Ethernet service can support the transmission of the 200G Ethernet service by using two existing 100GE PMDs. A channelized application scenario for Ethernet services can support multiplexing multiple low-rate Ethernet services into high-speed flexible Ethernet. A large number of Ethernet networks are used as the service bearer network in the access network and the metropolitan area network. The FlexE technology supports the application scenarios of the sub-rate, channelization, and reverse multiplexing of the Ethernet service, which enhances the application flexibility of the Ethernet interface. .

At present, FlexE technology only supports point-to-point applications as interface technology, but it has attracted the attention of the industry as a potential network transmission technology. The development of FlexE into network transport technology will inevitably require the exchange of FlexE node devices.

In the prior art, the flexible Ethernet adopts a Cell (cell) unified switching scheme, that is, a unified switching is performed by using a Cell switching network for different types of services. For example, for Time Division Multiplexing (TDM) services, it is adapted to the Cell switching network, and the switching is completed according to the slot configuration information of the FlexE service layer slot (Calendar). For the Ethernet data service, it is restored to the Ethernet frame, and then adapted to the Cell switching network, and the exchange is completed based on the Media Access Control (MAC) address. In the scheme of Cell unified switching, there are L1 layer and L2 layer processing, which is equivalent to designing two switching planes on the node device, which increases the design complexity, power consumption and cost of the device.

Summary of the invention

In view of this, the embodiments of the present invention provide a method and a device for processing a customer service, which can solve the problem of design complexity, power consumption, and cost of service switching on a node device.

In a first aspect, an embodiment of the present invention provides a method for processing a client service, including: receiving a client service, and mapping the client service to M time slots according to a first forwarding label carried in the client service, where The first forwarding label indicates a first forwarding destination address; the client service is sent to the target physical channel by using the M time slots, and the target physical channel has a corresponding relationship with the first forwarding destination address; M is a positive integer greater than or equal to 1.

The customer service may include a data service and a TDM service, and the customer service is mapped into the M time slots through the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing Multiple services are exchanged in the same switching plane of flexible Ethernet.

In a possible implementation, the mapping, by the first forwarding label carried in the customer service, the customer service into the M time slots, including: the first forwarding label and the M time The slots have a corresponding relationship, and the customer service is mapped into the M time slots according to the first forwarding label.

By establishing a correspondence between the first forwarding label and the time slot, the customer service can be mapped to the corresponding time slot according to the first forwarding label, so that multiple services are exchanged in the same switching plane of the flexible Ethernet.

In a possible implementation, the sending, by the M time slots, the customer service to the target physical channel includes: the M time slots and the target physical channel have a corresponding relationship.

In a possible implementation, the client service is encoded, and the client service forms a code block stream; and the first forwarding label is added in an S code block of the customer service, where the S code block is One of the code block types in the code block stream.

In a possible implementation manner, the first forwarding label is added in an L code block of the customer service, where the L code block is obtained by deleting an idle code block of the customer service, where the idle code block is obtained. A type of code block in a code block stream.

In a possible implementation manner, the method further includes: adding the first forwarding label to a frame header positioning overhead of the client service.

In a possible implementation manner, a second forwarding label is added to the client service, and the second forwarding label indicates a second forwarding destination address of the client service.

In a first aspect, an embodiment of the present invention provides a method for processing a customer service, including: acquiring M time slots of a customer service from a target physical channel, and acquiring the customer service from the M time slots; a first forwarding label in the client service, deleting the first forwarding label and/or adding a third forwarding label; wherein the first forwarding label indicates a first forwarding destination address, the target physical channel and the first A forwarding destination address has a corresponding relationship; M is a positive integer greater than or equal to 1.

By obtaining the first forwarding label from the client service, deleting the first forwarding label, and/or adding the third forwarding label, the exchange of multiple services in the same switching plane of the flexible Ethernet is realized.

In a possible implementation, the deleting the first forwarding label and/or adding the third forwarding label comprises: the first forwarding label is an inbound label, and the third forwarding label is an outgoing label; The first forwarding label acquires a third forwarding label; wherein the first forwarding label and the third forwarding label have a corresponding relationship.

In a possible implementation, the adding the third forwarding label includes: deleting an idle code block of the customer service, converting the S code block carrying the first forwarding label into an L code block, and increasing carrying The S code block of the third forwarding label; the idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.

In a possible implementation, the deleting the first forwarding label includes: deleting the first forwarding label, and restoring the code block carrying the first forwarding label to a normal code block; The normal code block includes any one of an S code block, an L code block, and a frame header positioning overhead, where the S code block and the L code block are respectively two code blocks in the code block stream formed by the coding of the client service. Types of.

In a third aspect, an embodiment of the present invention provides a device for processing a client service, including: a receiving module, configured to receive a client service; and a mapping module, configured to: according to the first forwarding label carried in the client service The client service is mapped to the M time slots, the first forwarding label indicates the first forwarding destination address, and the sending module is configured to send the client service to the target physical channel by using the M time slots, where the target The physical channel has a corresponding relationship with the first forwarding destination address; where M is a positive integer greater than or equal to 1.

In a possible implementation, the mapping module is configured to: the first forwarding label and the M time slots have a corresponding relationship, and map the client service to the In M time slots.

In a possible implementation manner, the M time slots and the target physical channel have a corresponding relationship.

In a possible implementation manner, the device further includes: an encoding module, configured to encode the client service, where the client service forms a code block stream; and a first adding module, configured to be in the client service The first forwarding label is added to the S code block, and the S code block is a type of code block in the code block stream.

In a possible implementation manner, the first adding module is further configured to: add the first forwarding label in an L code block of the customer service, where the L code block is deleted by deleting the customer service An idle code block is obtained, the idle code block being one of the code block types.

In a possible implementation manner, the device includes a second adding module, configured to: add the first forwarding label in a frame header positioning overhead of the client service.

In a possible implementation, the device further includes a third adding module, configured to: add a second forwarding label in the customer service, where the second forwarding label indicates a second forwarding destination of the customer service address.

In a fourth aspect, an embodiment of the present invention provides a device for processing a customer service, including: a client service obtaining module, configured to acquire M time slots of a customer service from a target physical channel, and obtain the M time slots from the M time slots. The client service; a forwarding label obtaining module, configured to acquire a first forwarding label in the client service; and a forwarding label adding and deleting module, configured to delete the first forwarding label and/or add a third forwarding a label, where the first forwarding label indicates a first forwarding destination address, and the target physical channel has a corresponding relationship with the first forwarding destination address; M is a positive integer greater than or equal to 1.

The first forwarding label is obtained from the customer service, the first forwarding label is deleted, and/or the third forwarding label is added, so that multiple services are exchanged in the same switching plane of the flexible Ethernet.

In a possible implementation, the forwarding label obtaining module is configured to: the first forwarding label is an inbound label, the third forwarding label is an outgoing label, and the third forwarding label is obtained according to the first forwarding label; The first forwarding label and the third forwarding label have a corresponding relationship.

In a possible implementation manner, the forwarding label addition and deletion module is configured to: delete an idle code block of the customer service, convert an S code block that carries the first forwarding label into an L code block, and increase carrying The S code block of the third forwarding label; the idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.

In a possible implementation, the forwarding label addition and deletion module is configured to: delete the first forwarding label, and restore the code block carrying the first forwarding label to a normal code block; wherein the normal code The block includes any one of an S code block, an L code block, and a frame header positioning overhead, where the S code block and the L code block are respectively two code block types in the code block stream formed by encoding the client service.

In a fifth aspect, an embodiment of the present invention provides a computer device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor and the memory are connected through a bus, and when the computer is running, the processor The computer executing the memory storage executes instructions to cause the computer to perform the method as described in the first aspect and any one of the possible implementations of the first aspect.

In a sixth aspect, an embodiment of the present invention provides a computer device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer to execute an instruction, and the processor and the memory are connected through a bus, and when the computer is running, the processor The computer executing the memory storage executes instructions to cause the computer to perform the method of any one of the second aspect and the second aspect.

The seventh aspect, the embodiment of the present invention provides a network system, including the device in any one of the possible implementation manners of the third aspect or the third aspect, and any possible implementation of the fourth aspect or the fourth aspect The device in the way.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the prior art, the drawings used in the description of the background and the embodiments will be briefly described below.

1 is a schematic diagram of a layered structure of a flexible Ethernet according to an embodiment of the present invention;

2 is a data frame format of a flexible Ethernet according to an embodiment of the present invention;

3 is a schematic structural diagram of a flexible Ethernet service processing according to an embodiment of the present invention;

4 is a schematic structural diagram of a flexible Ethernet service processing according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a field format of an S code block according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of a format of a label defined by an MPLS according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of a field format of an L code block according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a FlexE overhead code block according to an embodiment of the present invention;

FIG. 9 is a network architecture diagram of a flexible Ethernet according to an embodiment of the present invention; FIG.

FIG. 10 is a schematic structural diagram of an edge node device according to an embodiment of the present disclosure;

FIG. 11 is a schematic diagram of an overhead structure of an OTN frame according to an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of a switching node device according to an embodiment of the present disclosure;

FIG. 13 is an exemplary flowchart of a method for processing customer services according to an embodiment of the present invention;

FIG. 14 is an exemplary flowchart of a method for processing a client service according to an embodiment of the present invention;

15 is a schematic diagram of a logical structure of a device for processing a client service according to an embodiment of the present invention;

16 is a schematic diagram of a logical structure of a device for processing a client service according to an embodiment of the present invention;

FIG. 17 is a schematic structural diagram of a computer device according to an embodiment of the present invention.

detailed description

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

In order to better understand the technical solution of the embodiment of the present invention, a brief introduction of the hierarchical structure of the flexible Ethernet is first made. FIG. 1 is a schematic diagram of a hierarchical structure of a flexible Ethernet according to an embodiment of the present invention. As shown in Figure 1, the flexible Ethernet can include the FlexE client layer and the FlexE service layer. FlexE client layer It is mainly used to support the aggregation of customer services, including, for example, the Media Access Control (MAC) layer, the Reconciliation Sublayer (RS), and the 64B/66B codec in the FlexE SHIM layer. The FlexE client layer can include Ethernet interfaces with bandwidths of 10G, 25G, 40G, and N*50G. The FlexE service layer is mainly used to support the bearer of FlexE client services, including functional layers other than 64B/66B codec in the FlexE SHIM layer, Physical Coding Sublayer (PCS), Forward Error Correction (Forward Error). Correction, FEC) layer, Physical Medium Attachment (PMA), Physical Medium Dependent (PMD). The FlexE service layer can be implemented by N-channel 100GE physical layer device (PHY), and can also be implemented by N-channel 400GE PHY.

The FlexE SHIM layer introduces the concept of data frames and slots. FIG. 2 is a flexible Ethernet data frame format provided by an embodiment of the present invention. As shown in FIG. 2, the FlexE data frame is a data frame structure of 8 rows and (1+1023x20) columns, and is composed of 8x (1+1023x20) 66B code blocks. The FlexE data frame includes a control code block, a data code block, and may also include an idle (IDLE) code block. The control code block may include an overhead code block (O code block), a start code block (S code block), a tag code block (L code block), and the like. In FIG. 2, the eight code blocks of the first column are O code blocks for carrying overhead information of the FlexE data frame. Among the remaining control code blocks, S code blocks and L code blocks can be used to carry forwarding labels. The data code block is used to carry data information of the customer service. The IDLE code block may be a code block inserted when the client service performs rate adaptation.

FIG. 3 is a schematic structural diagram of a flexible Ethernet service process according to an embodiment of the present invention. As shown in FIG. 3, the service processing process may be a process of service multiplexing, and may be implemented on a transmitting end device of a flexible Ethernet. For the specific process of service multiplexing, reference may be made to the following description: after receiving the multi-channel client customer service, for example, the customer service a, the customer service b, the customer service z, the network device performs 64B/66B encoding on the received multi-channel customer service. A 66B code block stream is formed, and the code block stream of the client service is rate-fitted by inserting or deleting an idle (IDLE) code block. The code block stream of the customer service is sent to the FlexE service layer slot (Calendar) for exchange. The code block stream of multiple client services is distributed into the sub-Calendar of the N-way PHY through the FlexE service layer time slot, and is in a certain interval period (for example, 20x66B) in the sub-Calendar of each PHY. Insert FlexE overhead to identify the frame structure of FlexE or to identify the order of each PHY. Scrambling the sub-Calendar of each PHY, then The multiplexed PCS channel, which divides the sub-Calendar of each PHY, is inserted into the Alignment Marker (AM) and distributed to the PMA.

FIG. 4 is a schematic structural diagram of a flexible Ethernet service process according to an embodiment of the present invention. As shown in FIG. 4, the service processing process may be a process of demultiplexing a service, and may be implemented on a receiving end device of a flexible Ethernet. The receiving device and the transmitting device of the flexible Ethernet can be different network devices or the same network device. The process of service demultiplexing is opposite to the process of the service multiplexing process shown in FIG. 4, and the principle is similar, and details are not described herein again.

In the embodiment of the present invention, in the flexible Ethernet service processing process shown in FIG. 3 or FIG. 4, by adding a forwarding label to the control code block in the code block flow of the customer service, and performing service exchange according to the added forwarding label, Implement multiple service exchanges in the same switching plane of flexible Ethernet.

The first forwarding label may be added to the control code block of the customer service, for example, the S code block, for indicating the first forwarding destination address of the customer service. The field format of the S code block is as shown in FIG. 5. The S code block includes a synchronization header (10), a block type field (0x78), and data fields (D1 to D7). The first forwarding label can be carried by the data fields (D1 to D7) in the S code block.

The first forwarding label can adopt a label format defined in Multiprotocol Label Switching (MPLS), as shown in FIG. 6. The total length of labels defined by MPLS is 32 bits, which can be divided into the following fields:

Label: The length is 20 bits and is used to identify the forwarding relationship of the service. The forwarding relationship of the service may include the forwarding destination address of the service, and may also include the forwarding source address of the service. For example, the forwarding relationship of the service includes the outgoing interface of the packet on a device, and may also include an inbound interface. The label can include an outgoing label and an incoming label, respectively, for identifying the outgoing interface and the incoming interface of the service on a certain device.

Exp: The length is 3 bits and is used to identify the quality of service (QoS) of the service. For example, eight priority levels can be identified, including service types corresponding to different services such as voice, video, and data.

TTL: The length is 8 bits, which is used to prevent loops when services are transmitted.

The total length of a tag is 32 bits. Therefore, an S code block can carry at most one layer of labels, for example, the first forwarding label. In order to support multi-layer tag nesting, it can be implemented by deleting an idle (IDLE) code block in a code block stream of a client service and adding a control code block. For example, the added control code block is called L The code block can also be a 66b code block. The field format of the L code block is shown in FIG. The format of the L code block and the S code block are similar, and the label is also carried by D1 to D7, except that the block type field is 0x79. The L code block can carry a forwarding label, such as a second forwarding label. The first forwarding label and the second forwarding label may be labels for different types of network devices, for example, the first forwarding label is for a network device of the access network, and the second forwarding label is for a network device of the transmission network. By deleting an IDLE code block, adding an L code block plus an S code block can support 3[(7*8*2)/32=3.5] layer tag nesting, by deleting two IDLE code blocks, adding two L code blocks plus S code blocks can support 5[(7*8*3)/32=5.25] layer tag nesting.

Optionally, signaling such as transport routing, label distribution, etc. can be carried over the FlexE overhead. The network device may include a control plane and a data plane. The control plane is used for service control and configuration of the data plane, and the data plane transmits service data under the control of the control plane. The transmission route and the label distribution signaling are used to configure a forwarding relationship of the service on the control plane of the network device. For example, the service is on the inbound interface and the outbound interface of a certain network device. When the data plane of the network device receives the client service, the forwarding relationship of the client service in the control plane is forwarded according to the forwarding label carried in the client service. The FlexE overhead can be added when the code block stream of the customer service enters each FlexE physical interface (PHY), and the FlexE overhead can be represented by the O code block. The structure diagram of the FlexE overhead code block is shown in Figure 8. The signaling channel, label distribution and other signaling can be carried through the management channel in the FlexE overhead.

FIG. 9 is a network architecture diagram of a flexible Ethernet according to an embodiment of the present invention. As shown in FIG. 9, an edge node device and a switching node device may be included in the Ethernet. Typically, the edge node device is used to connect to the client device and receive client traffic from the client device. The switching node device and the edge node device and the different switching node devices are connected through interfaces, for example, P1, P2, P3, Pn, etc., for transmitting customer services. The side where the edge node device is connected to the client device may be referred to as the client side, and the side to which the edge node device is connected to one side of the switching node device or the two switching node devices is referred to as the line side.

FIG. 10 is a schematic structural diagram of an edge node device according to an embodiment of the present invention. As shown in FIG. 10, the device may include a client signal processing module 101, a tag encapsulation module 102, a FlexE SHIM module 103, a tag assignment module 104, an overhead processing module 105, a routing table generation/update module 106, and at least one PHY module 107. Wherein, the modules may be circuit modules integrated on one chip, or Independent circuit module. The functions implemented by the edge node device in the sending direction include:

The client signal processing module 101 is configured to receive a customer service from the client device and determine a service type of the client service. The service type of the customer service received by the edge node device may include: a data service and a TDM service. The data service may be a packet service, an Ethernet data service, an MPLS service, or an Internet Protocol (IP) service. The TDM service may be a Synchronous Digital Hierarchy (SDH) service or an Optical Transport Network (OTN) service.

The label encapsulation module 102 is configured to perform 64B/66B encoding on the customer service to form a 66B code block stream. The first forwarding label is obtained from the label distribution module 104, and the first forwarding label is added to the control code block in the 66B code block stream formed by the customer service. For example, the control code block can be an S code block. For the structure of the S code block and the first forwarding label, refer to FIG. 5 and FIG. 6 respectively. How to add the first forwarding label to the S code block can also be referred to the foregoing embodiment, and details are not described herein again.

If the received client service is a data service, such as an Ethernet data service, the client service itself carries the S code block. If the client service of the receiving is a TDM service, such as an OTN service, the client service itself does not carry the S code block. For the TDM service, the OTN service is taken as an example to describe how to increase the S code block for the OTN service.

The overhead structure of the OTN frame is shown in Figure 11. The initial 6-byte frame alignment signal (FAS) of the OTN frame is the frame positioning overhead, and the fixed pattern is 0xf6f6f6282828. When the OTN service is mapped to the FlexE service layer, the OTN service is stream sliced to divide the bit block, and the IDLE code block is rate-adjusted and adapted. An implementation manner of adding an S code block in an OTN service may include:

Manner 1: When the OTN service is stream sliced, the 6 frame positioning overhead (FAS) of the OTN frame header is converted into an S code block. For example, when the OTN frame header indication comes, the 6-byte FAS of the OTN frame header is deleted, the S-code block is inserted, and the subsequent data stream continues to be sliced.

Manner 2: When the OTN service is stream sliced, an S code block can be added to the OTN service. For example, when the OTN frame header indication comes, an S code block is inserted, and at the same time, an IDLE code block can be deleted to adapt to the signal rate after the S code block is added. The data stream is then sliced starting from the first byte of the OTN frame.

If the client service requires multiple layers of tag nesting, the second forwarding tag can also be added by deleting the IDLE code block in the client service and adding the L code block. For the structure diagram of the L code block, refer to FIG. 7. How to add the second forwarding label to the L code block can also be referred to the foregoing embodiment, and details are not described herein again.

Before adding the first forwarding label and/or the second forwarding label in the customer service, the client service may be 64B/66B encoded, the customer service is converted into a 66B code block stream, and then the 66B code block stream is rate-adapted, for example, The IDLE code block can be inserted or deleted in the 66B code block stream. Optionally, the rate adaptation of the 66B code block stream may also be performed after adding the first forwarding label and/or the second forwarding label, or may also add the first forwarding while performing rate adaptation on the 66B code block stream. The label and/or the second forwarding label are not limited in the present invention.

The label distribution module 104 is configured to perform forwarding label allocation on the customer service. The forwarding label includes the first forwarding label, the second forwarding label, and the like as described above, and the allocation principles of the forwarding labels of different levels may be the same. Here, the first forwarding label is taken as an example for description. For the data service, for example, the Ethernet data service, the label distribution module 104 may allocate the first forwarding label according to any one or more of the IP header, the MAC address, and the flow identifier of the customer service. For example, the first forwarding label can be assigned according to the principle of Forwarding Equivalence Class (FEC). Forwarding equivalence classes refer to forwarding a group of services in the same way, for example, through the same channel or with the same forwarding destination address. The same first forwarding label can be used if the subsequent client service belongs to the same stream as the previous client service, for example with a common IP or common quintuple information. Optionally, if the client service encapsulation module 102 determines that the current client service can use the same first forwarding label as the previous client service, the forwarding label may not be obtained from the label distribution module 104, and the first customer service is directly added. A forwarding label. The label allocation module 104 can also allocate the number of time slots occupied by the customer service according to the bandwidth of the customer service and the bandwidth granularity of the network. For example, a FlexE service layer in flexible Ethernet has a slot granularity of 5G. For a 10G customer service, two slots can be allocated for the 10G customer service.

For TDM services, such as OTN services, forwarding labels can be assigned based on pre-configured information. The pre-configured information may include forwarding tag information, time slot information, and the like. When the service is enabled, the TDM service can be pre-configured with forwarding label information, time slot information, and so on. For example, a 10G TDM The service allocates 2 slots and uses label 1 as the first forwarding label.

The FlexE SHIM module 103 is used to map customer services into FlexE service layer slots. The client service may be mapped to the corresponding time slot according to the forwarding label information, and the customer service may be mapped into the corresponding time slot according to the time slot information. Optionally, the forwarding label has a correspondence relationship with N time slots occupied by the client service. For example, a 10G client service occupies slot 1 and slot 2, and the first forwarding label of the client service is label 1, and label 1 has a corresponding relationship with slot 1 and slot 2. The FlexE SHIM module 103 can map the customer service to the time slot 1 and the time slot 2 according to the first forwarding label label 1 carried by the customer service, or according to the time slot information of the customer service (occupying the time slot 1 and the time slot 2). ), mapping customer traffic into slot 1 and slot 2. The first forwarding label may indicate which one or more PHY modules are used to send the customer service. FlexE service layer time slots carrying customer traffic can be distributed to one or more PHY modules while inserting FlexE overhead.

The PHY module 107 is configured to send client traffic to a physical transmission link on the line side. The edge node device has at least one physical interface, and the customer service is sent to the physical transmission link of the line side through the physical interface. For example, in the optical fiber, the customer service can be received or forwarded by the target device through the physical transmission link. A physical interface may include at least one PHY module, each PHY module corresponding to a respective time slot. For example, a 100G PHY module corresponds to 20 5G granular FlexE time slots. After mapping the customer service to N time slots, the client service is distributed to the corresponding PHY module according to the correspondence between the time slot and the PHY module. For example, slot 1 and slot 2 occupied by the 10G client service correspond to PHY1, and slot 1 and slot 2 of the customer service are distributed to PHY1.

The overhead processing module 105 is configured to insert a FlexE overhead. In the process of distributing N time slots of the customer service to one or more PHY modules 107, FlexE overhead can also be inserted in each PHY module. The FlexE overhead is used to monitor the link status, and the generation and update of the link status can direct the routing table generation/update module 106 to generate and/or update the routing table. The routing table includes the topology information of the network and the forwarding relationship of the service, and can provide a basis for allocating forwarding labels for the customer service. The signaling of the routing, label distribution, and the like may also be carried in the FlexE overhead. For details, refer to the embodiment shown in FIG. 8.

The functions implemented by the edge node device in the receiving direction include:

The PHY module 107 is configured to receive client services from the line side. Can pass one or more PHY modules Receive customer traffic from the physical transport link. For example, a 10G customer service is received from PHY1.

The FlexE SHIM module 103 is configured to receive customer traffic from one or more PHY modules 107. At this time, the client service can be a 66B code block stream. The FlexE overhead is extracted in the 66B code block stream and data alignment is performed. The FlexE service layer time slot (Calendar) is restored, and each client service is recovered according to the time slot information. For example, the 10G client service corresponding to slot 1 and slot 2 is recovered from PHY1. Optionally, the FlexE SHIM module 103 can also send the FlexE overhead information to the overhead processing module 105, so that the overhead processing module 105 performs link state monitoring according to the FlexE overhead information.

The label encapsulating module 102 performs recovery processing on the first forwarding label information of the client signal. For example, for the data service, the first forwarding label information in the S code block may be deleted and restored to the original S code block before the first forwarding label is added. The rate adaptation is then performed by adding or deleting an IDLE code block, etc., and the 66B code block stream is decoded and then sent to the client signal processing module 101. For the TDM service, if the S code block is added by deleting the IDLE code block, the S code block can be discarded; if the S code block is formed by the frame positioning overhead conversion, the S code block can be restored to the frame header positioning overhead. The sync header of the 66B code block stream is then removed and sent to the client signal processing module 101.

The client signal processing module 101 is configured to receive the 64B/66B decoded code block stream and recover the original client service, for example, TDM service, data service, and the like.

In the embodiment of the present invention, the edge node device adds a first forwarding label to the client service, performs service switching according to the first forwarding label, and sends the client service to the target physical channel to implement the same switching plane on the flexible Ethernet. Exchange of various services.

FIG. 12 is a schematic structural diagram of a switching node device according to an embodiment of the present invention. As shown in FIG. 12, as shown in FIG. 10, the device may include a PHY module 201/207, a FlexE SHIM module 202/206, a tag encapsulation module 203, a frame header alignment module 204, a switch module 205, a tag assignment module 208, and overhead. The processing module 209 and the routing table generation/update module 210. Among them, these modules may be circuit modules integrated on one chip, or may be independent circuit modules. The switching node device has the same function in the sending direction and the signal in the receiving direction. The following functions are implemented in the sending direction as an example:

The PHY module 201 is configured to receive client services from the line side. For example, customer service is received from an edge node device or other switching node device through one or more PHY modules.

The FlexE SHIM module 202 is configured to receive client traffic from one or more PHY modules 201. At this time, the client service can be a 66B code block stream. The FlexE overhead is extracted in the 66B code block stream and data alignment is performed. The FlexE service layer time slot (Calendar) is restored, and each client service is recovered according to the time slot information. For example, the 10G client service corresponding to slot 1 and slot 2 is recovered from PHY1. Optionally, the FlexE SHIM module 202 can also send the FlexE overhead information to the overhead processing module 209, so that the overhead processing module 209 performs link state monitoring according to the FlexE overhead information.

The label encapsulating module 203 is configured to apply for a new first forwarding label (such as a label) to the label distribution module 208 according to a customer service, for example, a first forwarding label (such as an inbound label) carried in the S code block, and may also apply for a labeling behavior. Instructions. The label distribution module 208 can store the forwarding label information table. As shown in Table 1, the forwarding label information table can include information such as the node device identifier NE2, the inbound interface P2, the inbound label label 1, the outbound interface P3, and the outgoing label 2. It can also include tag behavior indications, such as tag nesting. The function of the label distribution module 208 is similar to that of the label distribution module 104 in the edge node device, and details are not described herein again.

Table 1

The inbound interface and/or the ingress label may indicate which one or which PHY modules on the node device NE2 the client service receives, and the outbound interface and the outbound label may indicate which PHY module of the client device is sent by the PHY module on the node device NE2. The first forwarding label carried by the customer service may be an incoming label, and the new first forwarding label is an outgoing label. The inbound label and the outbound label establish a corresponding relationship in the forwarding label information table. Therefore, the label can be obtained according to the inbound label, and the outbound interface can also be obtained. Tag behavior indications can include tag nesting, tag popping, tag switching, and the like. When tag nesting is required, an IDLE code block may be deleted, and the S code block currently carrying the first forwarding label is converted into an L code block, and an S code block carrying a new first forwarding label is added in front of the L code block. . If the outer label needs to be ejected, the S code block carrying the outer label is discarded, and one L code block following the S code block is converted into an S code block. When a label is required to be popped up, if there is only one layer of label, the S code block in which the layer label is located is restored to the original S code block, that is, the label information is restored to the original data field. For TDM services, the last layer of labels generally cannot be popped up in advance.

The frame header alignment module 204 is configured to align the 66B code block stream of each client service, and send the aligned code block stream to the switch module 205.

The switching module 205 is configured to perform data exchange according to the first forwarding label carried by the customer service. The first forwarding label here may be that the label encapsulating module 203 applies to the label distribution module 208 for a new first forwarding label, that is, an outgoing label. Optionally, data exchange can also be performed according to the outbound interface. The switching module 205 is equivalent to determining which PHY module 207 the client service is sent out from.

The FlexE SHIM module 206 is configured to map customer traffic into a time slot (Calendar) of the FlexE service layer. The client service may be mapped to the corresponding time slot according to the forwarding label information, and the customer service may be mapped into the corresponding time slot according to the time slot information. Optionally, the forwarding label has a correspondence relationship with N time slots occupied by the client service. For example, a 10G client service occupies slot 1 and slot 2, and the first forwarding label of the client service is label 2, and label 2 has a corresponding relationship with slot 1 and slot 2. The FlexE SHIM module 206 can map the customer service to the time slot 1 and the time slot 2 according to the first forwarding label 2 carried by the customer service, or according to the time slot information of the customer service (occupying the time slot 1 and the time slot 2). ), mapping customer traffic into slot 1 and slot 2. The first forwarding label may indicate which one or more PHY modules are used to send the customer service. FlexE service layer time slots carrying customer traffic can be distributed to one or more PHY modules while inserting FlexE overhead. Optionally, a certain buffer may also be added for QoS processing of data services.

The PHY module 207 is configured to send client traffic to the other side line side. The functions of the PHY module 207 and the PHY 107 in the edge node device are similar and will not be described again.

The functions of the overhead processing module 209 and the routing table generation/update module 210 are similar to those of the overhead processing module 105 and the table generation/update module 106 in the edge node device, and are not described herein again.

In the embodiment of the present invention, the first forwarding label is carried in the customer service received by the switching node device, and the service is exchanged according to the first forwarding label, so that the exchange of multiple services in the same switching plane of the flexible Ethernet is implemented.

FIG. 13 is an exemplary flowchart of a method for processing customer services according to an embodiment of the present invention. The method can be performed by an Ethernet device, an OTN device, a router, a switch, etc., and includes the following steps:

S1301: Receive a client service, and map the client service to the M timeslots according to the first forwarding label carried in the client service, where the first forwarding label indicates the first forwarding destination address.

Optionally, the first forwarding label and the M time slots have a corresponding relationship, and the customer service is mapped into the M time slots according to the first forwarding label.

Optionally, encoding the client service, where the client service forms a code block stream; adding the first forwarding label to the S code block of the customer service, where the S code block is the code block stream A type of code block in .

Optionally, the first forwarding label is added in an L code block of the customer service, where the L code block is obtained by deleting an idle code block of the customer service, where the idle code block is in the code block stream. A type of code block.

Optionally, the first forwarding label is added in a frame header positioning overhead of the client service.

Optionally, a second forwarding label is added to the client service, and the second forwarding label indicates a second forwarding destination address of the client service.

S1302: Send the client service to the target physical channel by using the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address; where M is a positive integer greater than or equal to 1.

Optionally, the M time slots and the target physical channel have a corresponding relationship.

The first forwarding destination address may be the destination MAC address of the next hop node device forwarded by the client service, or the outbound port identifier of the node device that forwards the client service or the identifier of the PHY module.

In the embodiment of the present invention, the customer service is mapped into the M time slots by using the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing the flexible Ethernet. Exchange of multiple services in the same switching plane.

FIG. 14 is an exemplary flowchart of a method for processing customer services according to an embodiment of the present invention. The method can be performed by an Ethernet device, an OTN device, a router, a switch, etc., and includes the following steps:

S1401: Obtain M time slots of the customer service from the target physical channel, and obtain the customer service from the M time slots.

S1402: Acquire a first forwarding label in the customer service, delete the first forwarding label, and/or add a third forwarding label, where the first forwarding label indicates a first forwarding destination address, and the target physical channel Corresponding to the first forwarding destination address; M is a positive integer greater than or equal to 1.

Optionally, the first forwarding label is an inbound label, and the third forwarding label is an outgoing label; and the third forwarding label is obtained according to the first forwarding label, where the first forwarding label and the third forwarding label are Have a corresponding relationship.

Optionally, deleting the idle code block of the customer service, converting the S code block carrying the first forwarding label into an L code block, and adding an S code block carrying the third forwarding label; the idle code The block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.

Optionally, the first forwarding label is deleted, and the code block carrying the first forwarding label is restored to a normal code block, where the normal code block includes an S code block, an L code block, and a frame header positioning overhead. Any one of the S code blocks and the L code blocks are respectively two code block types in the code block stream formed by the coding of the client service.

The first forwarding destination address may be a destination MAC address of a node device that receives the client service, or an ingress port identifier of the node device that receives the client service, or an identifier of the PHY module. The third forwarding label may indicate the destination MAC address of the next hop node device forwarded by the client service, or may be the outbound port identifier of the node device that forwards the client service or the identifier of the PHY module.

In the embodiment of the present invention, the first forwarding label is obtained from the customer service, the first forwarding label is deleted, and/or the third forwarding label is added, so that the exchange of multiple services in the same switching plane of the flexible Ethernet is implemented.

FIG. 15 is a schematic diagram of a logical structure of a device for processing a client service according to an embodiment of the present invention. The device may be implemented by an Ethernet device, an OTN device, a router, a switch, or the like, and includes: a receiving module 1501, a mapping module 1502, and a sending module 1503.

The receiving module 1501 is configured to receive a customer service.

The mapping module 1502 is configured to map the customer service into M time slots according to the first forwarding label carried in the customer service, where the first forwarding label indicates the first forwarding destination address.

Optionally, the mapping module 1502 is configured to: the first forwarding label and the M time slots have a corresponding relationship, and map the customer service to the M time slots according to the first forwarding label. in.

The sending module 1503 is configured to send the client service to the target physical channel by using the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address, where M is greater than or equal to 1 Positive integer.

Optionally, the device further includes: an encoding module, configured to encode the client service, where the client service forms a code block stream; and a first adding module, configured to add in the S code block of the customer service The first forwarding label, the S code block is a type of code block in the code block stream.

Optionally, the first adding module is further configured to: add the first forwarding label in an L code block of the customer service, where the L code block is obtained by deleting an idle code block of the customer service, The idle code block is one of the code block types in the code block stream.

Optionally, the device includes a second adding module, configured to: add the first forwarding label in a frame header positioning overhead of the client service.

Optionally, the device further includes a third adding module, configured to: add a second forwarding label in the customer service, where the second forwarding label indicates a second forwarding destination address of the customer service.

FIG. 16 is a schematic diagram of a logical structure of a device for processing a client service according to an embodiment of the present invention. The device can be executed by an Ethernet device, an OTN device, a router, a switch, and the like, and includes: a client service obtaining module 1601, a forwarding label obtaining module 1602, and a forwarding label adding and deleting module 1603.

The customer service obtaining module 1601 is configured to acquire M time slots of the customer service from the target physical channel, and obtain the customer service from the M time slots;

The forwarding label obtaining module 1602 is configured to acquire a first forwarding label in the customer service.

Optionally, the forwarding label obtaining module 1602 is configured to: the first forwarding label is an inbound label, the third forwarding label is an outgoing label, and the third forwarding label is obtained according to the first forwarding label; The first forwarding label and the third forwarding label have a corresponding relationship.

The forwarding label addition and deletion module 1603 is configured to delete the first forwarding label and/or add a third forwarding label, where the first forwarding label indicates a first forwarding destination address, the target physical channel and the first forwarding The destination address has a corresponding relationship; M is a positive integer greater than or equal to 1.

Optionally, the forwarding label addition and deletion module 1603 is configured to: delete an idle code block of the customer service, convert an S code block carrying the first forwarding label into an L code block, and increase carrying the third Forwarding the S code block of the tag; the idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.

Optionally, the forwarding label addition and deletion module 1603 is configured to: delete the first forwarding label, and restore the code block carrying the first forwarding label to a normal code block; where the normal code block includes an S code. Any one of a block, an L code block, and a frame header locating overhead, wherein the S code block and the L code block are respectively two code block types in the code block stream formed by the coding of the client service.

FIG. 17 is a schematic structural diagram of a computer device according to an embodiment of the present invention. As shown in FIG. 17, computer device 1700 includes a processor 1701, a memory 1702, an input/output interface 1703, a communication interface 1704, and a bus 1705. The processor 1701, the memory 1702, the input/output interface 1703, and the communication interface 1704 implement a communication connection with each other through the bus 1705.

The processor 1701 can use a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or at least one integrated circuit for executing related programs to implement the present invention. The technical solution provided by the embodiment of the invention.

The memory 1702 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). Memory 1702 You can store operating systems and other applications. When the technical solution provided by the embodiment of the present invention is implemented by software or firmware, the program code for implementing the technical solution provided by the embodiment of the present invention is stored in the memory 1702 and executed by the processor 1701.

The input/output interface 1703 is for receiving input data and information, and outputting data such as an operation result.

Communication interface 1704 enables communication between computer device 1700 and other devices or communication networks using transceivers such as, but not limited to, transceivers.

Bus 1705 can include a path for communicating information between various components of computer device 1700, such as processor 1701, memory 1702, input/output interface 1703, and communication interface 1704.

The computer device 1700 executes the code stored in the memory 1702 by the processor 1701, and implements the steps of: receiving a customer service, and mapping the customer service into M time slots according to the first forwarding label carried in the customer service, The first forwarding label indicates a first forwarding destination address, and the client service is sent to the target physical channel by using the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address; Is a positive integer greater than or equal to 1.

The computer device 1700 executes the code stored in the memory 1702 by the processor 1701, and implements the steps of: acquiring M time slots of the customer service from the target physical channel, acquiring the customer service from the M time slots; acquiring the a first forwarding label in the customer service, deleting the first forwarding label and/or adding a third forwarding label; wherein the first forwarding label indicates a first forwarding destination address, the target physical channel and the first The forwarding destination address has a corresponding relationship; M is a positive integer greater than or equal to 1.

Specifically, the steps in the method embodiments shown in FIGS. 13 and 14 can be implemented by the computer device 1700 shown in FIG. It should be noted that although the computer device 1700 shown in FIG. 17 only shows the processor 1701, the memory 1702, the input/output interface 1703, the communication interface 1704, and the bus 1705, those skilled in the art will understand in the specific implementation process. Computer device 1700 also includes other devices necessary to achieve proper operation. Also, those skilled in the art will appreciate that computer device 1700 can also include hardware devices that implement other additional functions, depending on the particular needs. Moreover, those skilled in the art will appreciate that computer device 1700 may also only include the components necessary to implement embodiments of the present invention, and does not necessarily include all of the devices shown in FIG.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

A method for processing a customer service, characterized in that the method comprises:

Receiving the client service, mapping the client service to the M time slots according to the first forwarding label carried in the customer service, where the first forwarding label indicates the first forwarding destination address;

Transmitting the client service to the target physical channel by using the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address;

Where M is a positive integer greater than or equal to 1.
The method of claim 1, wherein the mapping the customer service to the M time slots according to the first forwarding label carried in the customer service comprises:

The first forwarding label and the M time slots have a corresponding relationship, and the customer service is mapped into the M time slots according to the first forwarding label.
The method of claim 1, wherein the transmitting the client service to the target physical channel by using the M time slots comprises:

The M time slots and the target physical channel have a corresponding relationship.
The method of any of claims 1-3, wherein the method further comprises:

Encoding the client service, the client service forming a code block stream;

Adding the first forwarding label to the S code block of the client service, where the S code block is one type of code block in the code block stream.
The method of claim 4, wherein the method further comprises:

Adding the first forwarding label to an L code block of the client service, where the L code block is obtained by deleting an idle code block of the client service, and the idle code block is a code in the code block stream. Block type.
The method of any of claims 1-5, wherein the method further comprises:

Adding the first forwarding label to a frame header positioning overhead of the client service.
The method of claim 1 wherein the method further comprises:

Adding a second forwarding label to the client service, where the second forwarding label indicates a second forwarding destination address of the client service.
A method for processing a customer service, characterized in that the method comprises:

Obtaining M time slots of the customer service from the target physical channel, and acquiring the customer service from the M time slots;

Obtaining a first forwarding label in the client service, deleting the first forwarding label, and/or adding a third forwarding label;

The first forwarding label indicates a first forwarding destination address, and the target physical channel has a corresponding relationship with the first forwarding destination address; M is a positive integer greater than or equal to 1.
The method of claim 8, wherein the deleting the first forwarding label and/or adding the third forwarding label comprises:

The first forwarding label is an inbound label, and the third forwarding label is an outgoing label; and the third forwarding label is obtained according to the first forwarding label;

The first forwarding label and the third forwarding label have a corresponding relationship.
The method according to claim 8 or 9, wherein the adding the third forwarding label comprises:

Deleting the idle code block of the customer service, converting the S code block carrying the first forwarding label into an L code block, and adding an S code block carrying the third forwarding label;

The idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.
The method of claim 8 or 9, wherein the deleting the first forwarding label comprises:

Deleting the first forwarding label, and restoring the code block carrying the first forwarding label to a normal code block;

The normal code block includes any one of an S code block, an L code block, and a frame header positioning overhead, where the S code block and the L code block are respectively in a code block stream formed by coding the client service. Two code block types.
A device for processing a customer service, characterized in that the device comprises:

a receiving module, configured to receive a customer service;

a mapping module, configured to map the customer service into M time slots according to the first forwarding label carried in the customer service, where the first forwarding label indicates a first forwarding destination address;

a sending module, configured to send the client service to the target physical channel by using the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address;

Where M is a positive integer greater than or equal to 1.
The device according to claim 12, wherein the mapping module is configured to:

The first forwarding label and the M time slots have a corresponding relationship, and the customer service is mapped into the M time slots according to the first forwarding label.
The device according to claim 12, wherein said M time slots and said target physical channel have a corresponding relationship.
The device according to any one of claims 12-14, wherein the device further comprises:

An encoding module, configured to encode the client service, where the client service forms a code block stream;

a first adding module, configured to add the first forwarding label in an S code block of the customer service, where the S code block is a code block type in the code block stream.
The device according to claim 15, wherein the first adding module is further configured to:

Adding the first forwarding label to an L code block of the client service, where the L code block is obtained by deleting an idle code block of the client service, and the idle code block is a code in the code block stream. Block type.
The device according to any one of claims 12-16, wherein the device comprises a second adding module for:

Adding the first forwarding label to a frame header positioning overhead of the client service.
The device according to claim 12, wherein the device further comprises a third adding module, configured to:

Adding a second forwarding label to the client service, where the second forwarding label indicates a second forwarding destination address of the client service.
A device for processing a customer service, characterized in that the device comprises:

a customer service obtaining module, configured to acquire M time slots of a customer service from a target physical channel, and obtain the customer service from the M time slots;

a forwarding label obtaining module, configured to acquire a first forwarding label in the client service;

And a forwarding label adding and deleting module, configured to delete the first forwarding label and/or add a third forwarding label;

The first forwarding label indicates a first forwarding destination address, and the target physical channel has a corresponding relationship with the first forwarding destination address; M is a positive integer greater than or equal to 1.
The device according to claim 19, wherein the forwarding tag acquisition module is configured to:

The first forwarding label is an inbound label, and the third forwarding label is an outgoing label; and the third forwarding label is obtained according to the first forwarding label;

The first forwarding label and the third forwarding label have a corresponding relationship.
The device according to claim 19 or 20, wherein the forwarding label addition and deletion module is configured to:

Deleting the idle code block of the customer service, converting the S code block carrying the first forwarding label into an L code block, and adding an S code block carrying the third forwarding label;

The idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.
The device according to claim 19 or 20, wherein the forwarding label addition and deletion module is configured to:

Deleting the first forwarding label, and restoring the code block carrying the first forwarding label to a normal code block;

The normal code block includes any one of an S code block, an L code block, and a frame header positioning overhead, where the S code block and the L code block are respectively in a code block stream formed by coding the client service. Two code block types.