CN115442238A

CN115442238A - Service processing method, network device and computer readable storage medium

Info

Publication number: CN115442238A
Application number: CN202110625954.1A
Authority: CN
Inventors: 陈捷; 刘爱华
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2021-06-04
Filing date: 2021-06-04
Publication date: 2022-12-06

Abstract

The embodiment of the invention discloses a service processing method, network equipment and a computer readable storage medium, wherein the method comprises the following steps: encapsulating data of at least one customer service in a payload field of a service frame, wherein the payload field comprises a plurality of timeslots, the data of each of the at least one customer service being encapsulated in at least one of the timeslots; and sending the service frame to a next hop node, wherein the next hop node is an intermediate node or a sink node. The embodiment of the invention divides the payload field of the service frame into a plurality of time slots, and can realize slicing division and isolation of a plurality of client services by utilizing the time slots so as to bear flexible particle services, thereby realizing small particle channelized transmission of Ethernet and meeting the transmission requirements of low time delay, low jitter, hard isolation and flexible bandwidth of the services.

Description

Service processing method, network device and computer readable storage medium

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a service processing method, a network device, and a computer-readable storage medium.

Background

In the current communication network, a bearer network facing comprehensive services covers tens of millions of industries, and various services have great network requirement differentiation, so that the network needs end-to-end slicing to ensure the service differentiation bearer, and many new industries also need to be isolated by network slicing, thereby reducing the influence on the whole network when new services are online. Slice-based network architectures can be the fundamental capability requirement of future bearer networks.

In the related technology of realizing service Network fragmentation and isolation bearer in a bearer Network, the Virtual Private Network (VPN) technology has the problem of seizing different service bandwidths; the minimum client service granularity carried by the Flexible Ethernet (FlexibleEthernet) technology is 5Gb/s, and the hard isolation and the rigid pipeline of the service smaller than 5Gb/s are not supported.

Therefore, how to implement flexible isolated bearer for services with different grain sizes and meet the transmission requirement of flexible bandwidth is a technical problem which needs to be solved urgently.

Disclosure of Invention

The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

Embodiments of the present invention provide a service processing method, a network device, and a computer-readable storage medium, so as to implement flexible isolated bearer for services with different particle sizes and meet transmission requirements of flexible bandwidth.

In a first aspect, an embodiment of the present invention provides a service processing method, which is applied to a source node, and the method includes:

encapsulating data of at least one client service in a payload field of a service frame, wherein the payload field comprises a plurality of time slots, and the data of each client service in the at least one client service is encapsulated in at least one time slot;

sending the service frame to a next hop node, wherein the next hop node is an intermediate node or a host node;

and when the next hop node is an intermediate node, forwarding the data of each client service in the service frame through the intermediate node respectively, so as to forward the data of the client service to the sink node corresponding to the client service through one or more intermediate nodes.

In a second aspect, an embodiment of the present invention provides a service processing method, which is applied to an intermediate node, where the method includes:

receiving an incoming service frame, wherein the incoming service frame carries data of at least one client service, the incoming service frame comprises an incoming payload field, the incoming payload field comprises a plurality of incoming time slots, and the data of each client service in the at least one client service is loaded in at least one incoming time slot;

respectively determining an outgoing port and an outgoing time slot corresponding to each customer service;

generating an outbound service frame, and mapping the data of the client service to an outbound payload field of the outbound service frame, wherein the payload field of the outbound service frame comprises a plurality of outbound time slots, and the data of the client service is mapped to the outbound time slot corresponding to the client service;

and sending the outgoing service frame to a next hop intermediate node or a sink node through the outgoing port corresponding to the customer service.

In a third aspect, an embodiment of the present invention provides a service processing method, which is applied to a sink node, where the method includes:

receiving a service frame, wherein the service frame carries data of at least one client service, the service frame comprises a payload field, the payload field comprises a plurality of time slots, and the data of each client service in the at least one client service is carried in at least one time slot;

and for each client service, analyzing the data of the client service from the time slot according to the time slot mapped by the client service in the payload field.

In a fourth aspect, an embodiment of the present invention provides a network device, including: the service processing method provided by the first aspect, the second aspect, or the third aspect of the embodiments of the present invention is implemented by a memory, a processor, and a computer program stored in the memory and executable on the processor.

In a fifth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the service processing method provided in the first aspect, the second aspect, or the third aspect of the embodiment of the present invention is implemented.

In the embodiment of the invention, the data of at least one client service is encapsulated in the payload field of the service frame, wherein the payload field comprises a plurality of time slots, and the data of each client service in the at least one client service is encapsulated in at least one time slot; and sending the service frame to a next hop node, wherein the next hop node is an intermediate node or a sink node. The embodiment of the invention can realize the slicing division and isolation of a plurality of customer services by dividing the payload field of the service frame into a plurality of time slots and utilizing the time slots to bear the flexible particle service, thereby realizing the small particle channelized transmission of the Ethernet and meeting the transmission requirements of low time delay, low jitter, hard isolation and flexible bandwidth of the service.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.

Fig. 1 is a diagram illustrating a frame structure of a traffic frame according to the related art;

fig. 2 is a schematic diagram of a frame structure of a service frame according to an embodiment of the present invention;

fig. 3 is a schematic diagram of a frame structure of another service frame provided in the embodiment of the present invention;

fig. 4 is a schematic diagram of a frame structure of another service frame according to an embodiment of the present invention;

fig. 5 is a frame structure diagram of another service frame provided in the embodiment of the present invention;

fig. 6 is a frame structure diagram of another service frame provided in the embodiment of the present invention;

fig. 7 is a frame structure diagram of another service frame provided in the embodiment of the present invention;

fig. 8 is a schematic diagram of a transmission scenario of a traffic frame;

fig. 9 is a flowchart illustrating a service processing method according to an embodiment of the present invention;

fig. 10 is another schematic flow chart of a service processing method according to an embodiment of the present invention;

fig. 11 is another schematic flow chart of a service processing method according to an embodiment of the present invention;

fig. 12 is a service bearer architecture diagram of a service processing method provided by an embodiment of the present invention;

fig. 13a is an exemplary flowchart of a service processing method according to an embodiment of the present invention;

FIG. 13b is a diagram illustrating the contents of traffic frame #1 in the example shown in FIG. 13 a;

fig. 13c is a diagram illustrating the contents of traffic frame #2 in the example shown in fig. 13 a;

fig. 13d is a diagram illustrating the contents of traffic frame #3 in the example shown in fig. 13 a;

fig. 14 is a schematic structural diagram of a network device according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

It should be understood that in the description of the embodiments of the present invention, if there is any description of "first", "second", etc., it is only for the purpose of distinguishing technical features, and it is not to be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features or implicitly indicating the precedence of the indicated technical features. "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, and indicates that three relationships may exist, for example, a and/or B, and may indicate that a exists alone, a and B exist simultaneously, and B exists alone. Wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c may represent: a, b, c, a and b, a and c, b and c or a and b and c, wherein a, b and c can be single or multiple.

In addition, the technical features involved in the respective embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.

It should be understood that the service type to which the service processing method provided in the embodiment of the present invention is applicable may be an ethernet service, or may also be a Time Division Multiplexing (TDM) service with a fixed rate.

Fig. 1 is a schematic diagram of a frame structure of an ethernet Media Access Control (MAC) message defined in the IEEE 802.3 standard according to the related art. The message shown in fig. 1 includes a preamble field, a start-of-frame delimiter field, a destination address field, a source address field, a length/type field, a MAC client data field, and a frame check field. The MAC client data field is used to carry client service data, and can generally carry data of only one client service. Different MAC messages can carry different client services, but the messages carrying different clients lack strict isolation mechanisms and are easy to affect each other (such as congestion, preemption, and the like).

Fig. 2 is a schematic diagram of a frame structure of a service frame according to an embodiment of the present invention. The service frame shown in fig. 2 is an extended MAC service frame based on the IEEE 802.3 standard, and specifically includes, but is not limited to, four fields, namely a frame header, an overhead, a payload, and a frame check.

It should be appreciated that the frame length of the traffic frame of the embodiments of the present invention is fixed. In the frame structure of the traffic frame shown in fig. 2, the payload part may be divided into m slots (slot 1 to slot m), and the length of each slot is the same.

In the service frame shown in fig. 2, the frame header may include the following fields: preamble, start of frame delimiter, destination address, source address, length/type.

In the service frame shown in fig. 2, the overhead may specifically include the following fields:

multiframe indication (MFI): the sequence number, which indicates that the traffic frame is in a multiframe, is incremented from 0 and loops. For the case of the complex frame number of 40, the complex frame indication value is 0 to 39.

Slot adjustment request (CR): and the method is used for sending a time slot adjusting request, and when the CR bit is 1, the corresponding overhead carries the Client ID and the time slot ID information related to the adjustment.

And the time Slot adjusting response (CA) is used for adjusting the time Slot response after receiving the time Slot adjusting request, and when the bit of the time Slot adjusting response is 1, the corresponding overhead carries information of the Client ID and the Slot ID related to adjustment.

And the time slot effective indication (C) is used for indicating the time slot adjustment to be effective. When the bit C is 1, the corresponding overhead carries the information of the Client ID and the Slot ID related to the adjustment.

Client ID (Client ID): representing the customer identification of the channel. All 0 s indicate no use. When any 1 of CR, CA or C is valid, the corresponding Client ID and Slot ID represent the time Slot adjustment information. And when CR, CA and C are all invalid (0), the Client ID and Slot ID may be used to transmit the current Slot configuration information (i.e., the calenar table).

Slot ID (Slot ID): indicating the slot identification. For a 10GE channel, the slot ID ranges from 0 to 959.

General Communication Channel (GCC): for management information and the like.

RES: reserved, all 0 s.

Fig. 3 is a schematic frame structure diagram of a service frame according to an embodiment of the present invention. The service frame shown in fig. 3 is an extended MAC service frame based on the IEEE 802.1Q standard, and specifically includes, but is not limited to, four fields, i.e., a frame header, an overhead, a payload, and a frame check.

It should be understood that the service frame according to the embodiment of the present invention is not limited to the service frame based on the MAC message. For example, fig. 4 is a schematic frame structure diagram of another service frame provided in an embodiment of the present invention, and the service frame shown in fig. 3 is an MPLS service frame defined based on a Multi-Protocol Label Switching (MPLS) Protocol. The frame structure of the service frame shown in fig. 4 includes three parts, namely a frame header, an overhead and a payload, wherein the frame header carries MPLS label information, and the payload is divided into m time slots with the same length.

Fig. 5 is a schematic diagram of a frame structure of another service frame according to an embodiment of the present invention, and the service frame shown in fig. 4 is an Internet Protocol (IP) service frame. The frame structure of the traffic frame shown in fig. 5 includes an IP header, an overhead, and a payload, wherein the payload is divided into m slots having the same length.

Fig. 6 is a schematic view of a frame structure of another service frame according to an embodiment of the present invention, and the service frame shown in fig. 5 is a Transmission Control Protocol (TCP) service frame. The frame structure of the traffic frame shown in fig. 6 includes an IP header, a TCP header, an overhead, and a payload, and the payload is divided into m slots having the same length.

Fig. 7 is a schematic diagram of a frame structure of another service frame according to an embodiment of the present invention, where the service frame shown in fig. 7 is a User Datagram Protocol (UDP) service frame. The frame structure of the traffic frame shown in fig. 7 is IP header, UDP header, overhead and payload, and the payload is divided into m slots of the same length.

Based on the frame structures of the service frames shown in fig. 2 to fig. 7, it can be known that the service processing method according to the embodiment of the present invention is applicable to, but not limited to, transmission of MAC service frames, MPLS service frames, IP service frames, TCP service frames, and UDP service frames.

Fig. 8 is a schematic diagram illustrating a transmission scenario of a traffic frame, where as shown in fig. 8, a transmission path of the traffic frame includes a source node, at least one intermediate node, and a sink node. The source node is used for generating a service frame carrying client service data and sending the service frame to the intermediate node; the intermediate node is used for forwarding the service frame so as to forward the service frame to the host node; the host node is used for receiving the service frame of the intermediate node and analyzing the client service data from the service frame. The source node and the sink node may also be referred to as an ingress PE (provider edge) node and an egress PE node, respectively, and the intermediate node may also be referred to as a P (provider) node.

Fig. 9 is a flowchart illustrating a service processing method according to an embodiment of the present invention. The traffic processing method shown in fig. 9 can be applied to the source node shown in fig. 8, including but not limited to the following steps:

s110, encapsulating the data of at least one client service in the payload field of the service frame.

Wherein the payload field comprises a plurality of slots, data for each of the at least one customer service being encapsulated in at least one of the slots.

It is to be understood that the traffic frame described herein may employ any of the frame structures shown in fig. 2 through 7.

It will be appreciated that the payload field of the traffic frame may carry one or more client traffic. For example, in a scenario where the payload field carries multiple customer services, the payload field is divided into 10 slots, slots 1 to 3 encapsulating the data of customer service 1, slots 4 to 8 encapsulating the data of customer service 2, and slots 9 to 10 encapsulating the data of customer service 3.

It will be appreciated that to ensure that fixed rate bandwidth and hard isolation is provided for the bearer service, fixed length time slot division may be performed on the payload of the service frame. For example, for the service frame shown in fig. 2, the payload of the service frame is divided into m slots, each slot has a Size _ of _ slots (bytes), the slots are sequentially arranged in the payload area, and the service can be regarded as a continuous code stream in the slots.

The payload field length is: size _ of _ payload = m Size _ of _ slots (bytes);

the rate per slot is:

Rate_of_slot＝(Size_of_slot/(j*(Size_of_EMF+Size_of_IPG))*Rate_of_server

wherein Size _ of _ EMF is the length of a single service frame, j is the number of multiframes, size _ of _ IPG is the packet gap length, and Rate _ of _ server is the service layer channel Rate. j. The value of m can be designed according to parameters such as the channel rate of a service layer, the minimum particle service rate and the like.

The client service can be loaded to a plurality of time slots according to the bandwidth requirement, and the rate relationship is as follows:

rate of customer traffic = number of slots carrying customer traffic Rate of slots.

It can be seen that the embodiment of the present invention may provide a flexible service Rate (n × Rate _ of _ slots Mb/s) for the client service, where n is the number of slots occupied by the client service, that is, the length occupied by the client service in the payload area of the service frame is n × Size _ of _ slots (bytes), that is, the slice length of the client service. Wherein, n can be flexibly valued according to the service rate requirement of the client.

Illustratively, before encapsulating the data of the at least one client service in the payload field of the service frame, the method further includes: determining the number of time slots required to be occupied by the client service in a service frame according to the service rate requirement of the client service and the rate of each time slot; and slicing the data of the client service according to the time slot number to obtain data slice data slices of the client service. For example, the bandwidth requirement of a certain client service is a service rate of 100Mb/S, and it is assumed that the timeslot rate of each timeslot in a service frame is 10Mb/S, so that it may be determined that the client service needs to occupy 10 timeslots (n = 10) in the service frame, and then the data of the client service is sliced according to the length of 10 timeslots, and each service frame bears the data slice of the client service through 10 timeslots, so as to meet the bandwidth requirement of the client service, and implement providing a flexible service rate for the client service.

For the data encapsulation of the client service, in a possible implementation manner, the data of at least one client service may be encapsulated in a time slot of the payload field in a direct encapsulation manner.

For example, encapsulating data of at least one customer service in a payload field of the service frame may include:

S111A, obtaining at least one data slice of the customer service;

S111B, determining the time slot mapped by the client service from the payload field of the service frame according to the number of the time slots occupied by the client service in the service frame;

and S111C, encapsulating the data slice of the customer service in the mapped time slot.

It can be understood that the length of each time slot of the payload field is fixed, and after the number of the time slots occupied by the payload field is determined according to the bandwidth requirement (i.e. the traffic rate requirement) of the client traffic, the data slice length of each client traffic is also determined. For each client service, a time slot allocation relation table can be configured in advance according to the number of time slots required to be used by the client service, namely, a time slot mapped with the client service is selected from a plurality of time slots in a payload field. During mapping, according to the time slot distribution relation table, the data of the client service can be directly encapsulated in the mapped time slot, so that the client service is loaded in the time slot of the payload field. After the data of the client service is encapsulated in the time slot, the service can be regarded as a continuous code stream in the time slot.

Optionally, before slicing the data of the client service, 64/66B coding may be performed on the data of each client service to obtain 66B coded blocks of the client service.

Correspondingly, slicing the data of the customer service to obtain a data slice of the customer service, including: and slicing the 66B coding blocks of the client service to obtain the coding block slices of the client service.

S112A, obtaining a coding block slice of the client service;

S112B, determining the time slot mapped by the client service from the payload field of the service frame according to the number of the time slots occupied by the client service in the service frame;

and S112C, encapsulating the coding block slices of the client services in the mapped time slots.

Thus, the data of each client service is firstly subjected to 64/66B coding to obtain a 66B coding block of the client service, then the 66B coding block of the client service is sliced to obtain a slice based on the 66B coding block, and then the slice of the 66B coding block is encapsulated in a time slot of a payload field. It is understood that, for ethernet traffic, the traffic data may be directly encapsulated in the timeslot of the payload field through the above steps S111A to S111C or steps S112A to S112C; for the TDM service, an Ethernet Circuit Emulation service (CESoETH) may be adopted to convert the data of the TDM service into the data of the Ethernet service, and then the service data is encapsulated in the timeslot of the payload field through the above steps S111A to S111C or steps S112A to S112C.

In the specific implementation process, for the unused timeslot (i.e. Idle timeslot) in the payload field, a fixed value (e.g. 0x 00) may be filled in the timeslot, or an Idle code block may be filled in the timeslot.

It can be understood that, to implement label-based service frame forwarding, a label corresponding to the client service may be determined separately for each client service, and the label corresponding to the client service is encapsulated in the service frame. The labels are used to identify different customer services, and for example, the addresses of the next hop nodes of the customer services can be determined by the labels.

For example, the tag corresponding to the customer service may be encapsulated in the time slot mapped by the customer service together with the data of the customer service. It will be appreciated that in this case the data tag of the customer traffic is equal to the length of one or n elementary time slots, where n should be less than or equal to the total number of slots of the payload field.

It is to be understood that, after the data of the client service is encoded into the 66B coded block, the tag corresponding to the client service may be encapsulated with the 66B coded block in the time slot to which the client service is mapped.

Illustratively, the tag corresponding to the customer service may also be encapsulated in the header of the service frame, for example, using the destination address field in fig. 2, using the virtual local area network ID field in fig. 3, or using the tag field in fig. 4, etc.

It can be understood that, in order to implement the detection of the service quality of the customer service channel, such as the conditions of the bit error rate, the delay time, the service discard, and the like, operation, administration, and Maintenance (OAM) information of the customer service may also be inserted into the time slot mapped by the customer service. It should be appreciated that in this case, the length of the data of the customer traffic (which may be 66B coded blocks) plus the OAM information, or the length of the data of the customer traffic (which may be 66B coded blocks) tagged with OAM information, should be equal to the length of one or n basic time slots, where n should be less than or equal to the total number of time slots of the payload field.

And S120, sending the service frame to a next hop node, wherein the next hop node is an intermediate node or a sink node.

It is to be understood that the next hop node may be an intermediate node, so that the intermediate node forwards data of each customer service in the service frame, respectively, and forwards the data of the customer service to a sink node corresponding to the customer service through one or more intermediate nodes.

It can be understood that after the data of one or more client services are encapsulated into the payload field, the service frame may be sent to the intermediate node, so that the intermediate node forwards the data of each client service in the service frame, and forwards the data of the client service to the sink node corresponding to the client service through the one or more intermediate nodes.

Of course, the next hop node may also be a sink node, and the source node directly sends the traffic frame to the sink node.

It can be understood that the payload field in the service frame of the embodiment of the present invention may be divided into m time slots of the same size, one or more time slots may form service slicing channels of different bandwidths to carry end-to-end services, and different service slicing channels carry different client services to implement service isolation. Because each client service monopolizes the mapped time slot resource and the bandwidth is strictly ensured, the channelized transmission of the small-particle service can be realized, the flexible bearing effect is achieved, the bandwidth waste is avoided, and the transmission requirements of the service on low time delay, low jitter, hard isolation and flexible bandwidth are met.

Fig. 10 is a flowchart illustrating a service processing method according to an embodiment of the present invention. The traffic processing method shown in fig. 10 can be applied to the intermediate node shown in fig. 8, including but not limited to the following steps:

s210, receiving an incoming service frame.

The incoming service frame carries data of at least one client service, the incoming service frame comprises an incoming payload field, the incoming payload field comprises a plurality of incoming time slots, and the data of each client service in the at least one client service is carried in at least one incoming time slot.

It is to be understood that the intermediate node may receive an ingress traffic frame sent by the previous hop intermediate node or the source node from the ingress port. The incoming traffic frame may be any one of the frame structures shown in fig. 2 to 7.

S220, aiming at each customer service, respectively determining an outgoing port and an outgoing time slot corresponding to the customer service.

It can be understood that, after receiving the ingress service frame, for each client service carried by the service frame, it is necessary to confirm the forwarding direction of the client service, that is, confirm the egress port mapped by the client service. In addition, it is also necessary to confirm which slot or slots in the outbound traffic frame the customer traffic will map into, i.e., confirm the outbound slot to which the customer traffic maps. It should be appreciated that the outbound traffic frames herein are associated with the acknowledged outbound port.

In a possible implementation manner, the mapping from the service data carried by the ingress time slot to the egress port and the egress time slot may be completed based on a preset mapping relationship between the ingress time slot and the egress port and the egress time slot. For example, the mapping relationship between the ingress and egress time slots and the egress and egress time slots may be pre-configured through a time slot cross configuration table, and the time slot cross configuration table may be pre-configured by a network management node, an SDN controller, or a dynamic protocol.

Illustratively, determining an outbound port and an outbound slot corresponding to the customer traffic comprises:

S221A, using the inbound timeslot carrying the data of the client service as a first inbound timeslot.

For example, data of the client service is encapsulated in slot #1 of the payload field of the inbound service frame, and slot #1 is taken as the first inbound slot.

And S221B, determining the outgoing port and the outgoing time slot mapped by the first incoming time slot from a preset time slot cross configuration table to obtain the outgoing port and the outgoing time slot mapped with the client service.

For example, the first inbound timeslot is timeslot #1, and the outbound port and the outbound timeslot mapped to timeslot #1 are looked up in a preset timeslot crossing configuration table, so as to obtain the outbound port and the outbound timeslot mapped to the client traffic.

In another possible implementation manner, the ingress service frame carries an ingress label corresponding to the client service, and in this case, an egress port and an egress timeslot mapped by the client service may be determined according to the ingress label corresponding to the client service.

Illustratively, determining outgoing ports and outgoing timeslots to which the customer traffic is mapped comprises:

S222A, acquiring an incoming label corresponding to the customer service from the incoming service frame.

It is understood that the incoming label may be located in a time slot mapped with the client service, or in a frame header, and the label corresponding to the client service may be obtained from a preset label field.

S222B, determining an outbound port and an outbound time slot mapped by the inbound label from a preset label switching configuration table, and obtaining the outbound port and the outbound time slot corresponding to the customer service.

For example, the mapping relationship between the label and the outbound port and the outbound time slot is stored through a preset label switching configuration table, and after the label corresponding to the customer service is obtained, the outbound port and the outbound time slot having the mapping relationship with the label can be searched and obtained in the preset label switching configuration table.

S230, generating an outbound service frame, and mapping the data of the client service to an outbound payload field of the outbound service frame.

Wherein the outbound payload field comprises a plurality of outbound slots, the data of the client traffic being mapped into the outbound slots mapped with the client traffic.

It should be appreciated that the outbound traffic frame may be any of the frame structures shown in fig. 2-7.

It can be understood that, after determining the outbound port and the outbound timeslot mapped to the client service, the outbound service frame corresponding to the outbound port is obtained, and the data of the client service is mapped to the payload field of the outbound service frame, specifically, to the outbound timeslot mapped to the client service.

It can be understood that, in a scenario of forwarding according to a label, when determining an egress port and an egress timeslot mapped by an ingress label from a preset label switching configuration table, an egress label mapped by the ingress label can also be determined at the same time, so as to obtain an egress label corresponding to the customer service. And when the data of the client service is mapped to the outgoing payload field of the outgoing service frame, mapping an outgoing label corresponding to the client service to the outgoing service frame so as to update the label of the client service from the incoming label to the outgoing label and complete label switching. Specifically, the label corresponding to the customer service is mapped to the frame header of the outbound service frame, or mapped to the outbound timeslot corresponding to the customer service.

Optionally, when the data of the client service is mapped to the outbound time slot mapped to the client service, OAM information corresponding to the client service may also be inserted into the outbound time slot mapped to the client service, so as to complete time slot crossing of OAM information.

And S240, sending the outgoing service frame to a next hop intermediate node or a sink node through an outgoing port corresponding to the client service.

It can be understood that, after the encapsulation of the outgoing service frame of the client service is completed, the outgoing service frame is sent to the next-hop intermediate node or the sink node through the outgoing port mapped by the client service, so as to implement the forwarding of the client service.

Fig. 11 is a flowchart illustrating a service processing method according to an embodiment of the present invention. The traffic processing method shown in fig. 11 can be applied to the sink node shown in fig. 8, including but not limited to the following steps:

s310, receiving the service frame.

The service frame carries data of at least one client service, the service frame comprises a payload field, the payload field comprises a plurality of time slots, and the data of each client service in the at least one client service is carried in at least one time slot.

It is understood that the sink node receives the traffic frame transmitted by the intermediate node, and the traffic frame may be any one of the frame structures shown in fig. 2 to fig. 7.

And S320, analyzing the data of the client service from the time slot according to the time slot mapped by the client service in the payload field aiming at each client service.

It can be understood that, after receiving the service frame, the sink node parses the client service in the service frame to extract the data of the client service.

In some embodiments, the data of the client service is a 66B encoded block, in which case parsing the data of the client service from the payload field may be achieved by:

s321, parsing the 66B coding block of the client service from the payload field;

s322, decoding the 66B coding block to obtain the decoding data of the client service.

Optionally, when the client service carries the OAM information of the client service in the time slot mapped by the payload field, when the data of the client service is parsed from the payload field, the OAM information of the client service is also parsed from the payload field.

In order to facilitate better understanding of the service processing method provided by the embodiment of the present invention, the following further describes the embodiment of the present invention by using specific examples.

Fig. 12 is a service bearer architecture diagram of a service processing method according to an embodiment of the present invention. As shown in fig. 12, the time slots in the service frame provided by the embodiment of the present invention may form multiple MAC Slicing Channels (MSCs) that implement transmission, face end-to-end connection, have rigid isolation, and carry flexible granular service. All MSCs constitute a MAC Slice Channel Layer (MSCL), which is a channel sublayer located between the MAC Layer and the client Layer of IEEE 802.3. That is, the service layer of the MSCL is a standard MAC layer, and below the MAC layer, an IEEE 802.3 physical layer (PHY) of a standard ethernet, a FlexE, a Metro Transport Network (MTN) based on the FlexE, or a slice Packet Transport Network (SPN) may be provided.

It should be understood that both the MTN and SPN based on FlexE are sliced and channelized in the Physical Coding Sublayer (PCS) of ethernet, and therefore cannot communicate with ethernet devices or IP devices. The slicing and channelizing of the embodiment of the invention are carried out on the MAC layer, so that the invention has good interoperability, keeps good compatibility with standard systems of Ethernet, flexe, SPN and MTN, and can not only be used for intercommunication of traditional Ethernet equipment, but also be used as slicing technology for realizing small-particle service intercommunication of the Ethernet equipment and the SPN and MTN equipment.

As an example, assuming that a node a (source node) has a client service #1 waiting to be transmitted to a node B (sink node # 1) and a client service #2 waiting to be transmitted to a node C (sink node # 2), referring to fig. 13a, a process of implementing transmission of the client service #1 and the client service #2 by using the service processing method provided by the embodiment of the present invention may include the following steps:

s401, the node a encapsulates the data of the client service #1 and the client service #2 in the payload field of the service frame 1. Illustratively, the client service #1 is encapsulated in the slot #1 of the payload field, the client service #2 is encapsulated in the slot #2 of the payload field, and the content of the service frame #1 is shown in fig. 13b.

S402, the node a inserts the OAM information of the client traffic #1 and the client traffic #2 into the slot #1 and the slot #2 correspondingly.

S403, the node a sends the traffic frame #1 to the intermediate node, and correspondingly, the intermediate node receives the traffic frame #1 sent by the source node from the ingress port #2, and takes the traffic frame #1 as an ingress traffic frame.

S404, the intermediate node determines, according to a preset time slot cross configuration table: the outgoing port and the outgoing slot mapped to the client traffic #1 are port #4 and slot #6, and the outgoing port and the outgoing slot mapped to the client traffic #2 are port #6 and slot #3.

S405, the intermediate node switches the data of the client service #1 from the timeslot #1 of the service frame #1 to the timeslot #6 of the outgoing service frame #2 corresponding to the port #4, and the content of the service frame #2 can be seen in fig. 13 c; the data of the client traffic #2 is switched from slot #2 of traffic frame #1 to slot #3 of outgoing traffic frame #3 corresponding to port #6, and the content of traffic frame #2 can be seen in fig. 13d.

S406, the intermediate node transmits the traffic frame #2 to the node B through the port #4, and transmits the outgoing traffic frame #3 to the node C through the port # 6.

In S407, the node B receives the traffic frame #2 transmitted from the intermediate node, and then parses the data of the client traffic #1 from the slot #6 of the outgoing traffic frame # 2.

S408, after receiving the traffic frame #3 transmitted from the intermediate node, the node C parses the data of the client traffic #2 from the slot #3 of the outgoing traffic frame #3.

Referring to fig. 14, fig. 14 illustrates a network device 500 according to an embodiment of the present invention. The network device 500 includes, but is not limited to:

a memory 501 for storing a program;

and a processor 502 for executing the program stored in the memory 501, wherein when the processor 502 executes the program stored in the memory 501, the processor 502 is configured to execute the service processing method.

The processor 502 and the memory 501 may be connected by a bus or other means.

The memory 501, which is a non-transitory computer readable storage medium, may be used to store a non-transitory software program and a non-transitory computer executable program, such as the business process method described in any embodiment of the present invention. The processor 502 implements the business process methods described above by running non-transitory software programs and instructions stored in the memory 501.

The memory 501 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store and execute the service processing method described above. Further, the memory 501 may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, memory 501 may optionally include memory located remotely from processor 502, which may be connected to processor 502 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The non-transitory software programs and instructions needed to implement the business process methods described above are stored in the memory 501 and, when executed by the one or more processors 502, perform the business process methods provided by any of the embodiments of the invention.

The embodiment of the present invention further provides a storage medium, which stores computer-executable instructions, where the computer-executable instructions are used to execute the service processing method.

In an embodiment, the storage medium stores computer-executable instructions, which are executed by one or more control processors 502, for example, by one processor 502 in the network device 500, and can cause the one or more processors 502 to execute the service processing method provided by any embodiment of the present invention.

The above described embodiments are merely illustrative, wherein elements illustrated as separate components may or may not be physically separate, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.

It will be understood by those of ordinary skill in the art that all or some of the steps, systems, and methods disclosed above may be implemented as software, firmware, hardware, or suitable combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as is well known to those skilled in the art.

While the preferred embodiments of the present invention have been described in detail, it is to be understood that the present invention is not limited to the above-described embodiments, and that those skilled in the art can easily modify the present invention without departing from the spirit thereof. Under the shared conditions, various equivalent modifications or substitutions can be made, and the equivalent modifications or substitutions are included in the scope of the invention defined by the claims.

Claims

1. A service processing method is applied to a source node, and the method comprises the following steps:

2. The method of claim 1, wherein the traffic frame is any one of a Media Access Control (MAC) traffic frame, a multi-protocol label switching (MPLS) traffic frame, an Internet Protocol (IP) traffic frame, a Transmission Control Protocol (TCP) traffic frame, and a User Datagram Protocol (UDP) traffic frame.

3. The method of claim 1, wherein before encapsulating the data of the at least one client service in the payload field of the service frame, further comprising:

acquiring the service rate requirement of each client service;

determining the number of time slots required to be occupied by the customer service in the service frame according to the service rate requirement of the customer service and the rate of each time slot;

slicing the data of the customer service according to the time slot number to obtain data slices of the customer service;

the encapsulating of the data of the at least one client service in the payload field of the service frame comprises:

acquiring a data slice of at least one customer service;

determining the time slot mapped by the client service from the payload field of the service frame according to the time slot number;

and encapsulating the data slice of the client service in the mapped time slot.

4. The method of claim 3, wherein the data slice is a 66B coded block data slice.

5. The method of claim 1, wherein prior to transmitting the traffic frame to an intermediate node, further comprising:

respectively determining a label corresponding to the customer service for each customer service;

and encapsulating the label corresponding to the customer service in the service frame.

6. The method of claim 5, wherein the label corresponding to the customer service is encapsulated in a header of the service frame or in a slot mapped by the customer service.

7. The method of claim 1, wherein prior to sending the traffic frame to an intermediate node, further comprising:

and inserting operation, administration and maintenance (OAM) information of the customer service into the time slot mapped by the customer service.

8. A service processing method is applied to an intermediate node, and the method comprises the following steps:

receiving an incoming service frame, wherein the incoming service frame carries data of at least one customer service, the incoming service frame comprises an incoming payload field, the incoming payload field comprises a plurality of incoming time slots, and the data of each customer service in the at least one customer service is carried in at least one incoming time slot;

9. The method of claim 8, wherein determining outgoing ports and outgoing timeslots corresponding to the customer traffic comprises:

taking the inbound time slot bearing the data of the customer service as a first inbound time slot;

and determining the outgoing port and the outgoing time slot mapped by the first incoming time slot from a preset time slot cross configuration table to obtain the outgoing port and the outgoing time slot corresponding to the customer service.

10. The method of claim 8, wherein the incoming traffic frame carries an incoming label corresponding to the customer traffic;

the determining an outbound port and an outbound timeslot corresponding to the customer service includes:

acquiring an incoming label corresponding to the client service from the incoming service frame;

and determining the outgoing port and the outgoing time slot mapped by the incoming label from a preset label switching configuration table to obtain the outgoing port and the outgoing time slot corresponding to the client service.

11. The method according to claim 10, wherein when determining the outgoing port and the outgoing timeslot mapped by the incoming label from a preset label switching configuration table, further determining the outgoing label mapped by the incoming label from a preset label switching configuration table, and obtaining the outgoing label corresponding to the customer service;

before the sending the outbound traffic frame to the next-hop intermediate node or the sink node through the outbound port, the method further includes:

and mapping the outgoing label corresponding to the customer service to the outgoing service frame.

12. The method of claim 10, wherein before the sending the outbound traffic frame to a next-hop intermediate node or sink node through the outbound port, further comprising:

and inserting OAM information corresponding to the customer service into an outgoing time slot corresponding to the customer service.

13. A service processing method is applied to a sink node, and the method comprises the following steps:

14. The method of claim 13, wherein the data of the customer service is 66B encoded blocks;

analyzing the data of the client service from the payload field, wherein the data comprises:

parsing out the 66B encoded blocks of the customer service from the payload field;

and decoding the 66B coding block to obtain the decoded data of the client service.

15. The method of claim 13, wherein the customer traffic carries OAM information for the customer traffic in a timeslot mapped by the payload field;

when the data of the client service is analyzed from the payload field, the method further comprises:

and analyzing the OAM information of the client service from the payload field.

16. A network device, comprising: memory, processor and computer program stored on the memory and executable on the processor, which when executed by the processor implements a method of service processing as claimed in any one of claims 1 to 15.

17. A computer-readable storage medium, in which a computer program is stored which, when executed by a processor, implements a service processing method according to any one of claims 1 to 15.