CN116264590A

CN116264590A - Service processing method, device and system

Info

Publication number: CN116264590A
Application number: CN202210096188.9A
Authority: CN
Inventors: 李呈; 夏阳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-12-14
Filing date: 2022-01-26
Publication date: 2023-06-16
Also published as: WO2023109672A1

Abstract

A service processing method, device and system belong to the technical field of networks. The method comprises the following steps: the network equipment receives a message comprising an option field, wherein the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different; the network device processes the message according to the first service information. In the application, the service information of at least two different services can be carried in the same option field of the same message, so that the message cost is reduced.

Description

Service processing method, device and system

The present application claims priority from chinese patent application No. 202111527212.1 entitled "IPv 6 Option for aggregating service information," whose entire contents are incorporated herein by reference, on application day 2021, 12, 14.

Technical Field

The present invention relates to the field of network technologies, and in particular, to a service processing method, device, and system.

Background

In the current development of network technology, multiple services can be developed for internet protocol version 6 (internet protocol version, ipv 6) messages. For example, these services may include slice (slice) services, stream-following detection services, application-aware network (APN) services, deterministic network (deterministic networking, detNet) services, and so forth. The on-stream detection service may include an on-stream detection (in-situ flow information telemetry, IFIT) service or an in-band operation management maintenance (in-suitoam operations administration and maintenance, IOAM) service.

Currently, different option fields are extended for each service in an IPv6 extension header of an IPv6 packet to carry service information of a corresponding service. For example, when a certain IPv6 packet needs to support both the slice service and the IFIT service, two option fields are required to be extended in the IPv6 extension header of the IPv6 packet for the slice service and the IFIT service, and service information of the corresponding service is carried in the option fields corresponding to the slice service and the IFIT service.

However, according to the protocol specification, a type (type) subfield, a length (length) subfield, etc. should be included in the option field for describing the fixed contents of the option field. Therefore, when the option fields are respectively extended for each service, each extended option field includes these fixed contents, which results in a larger length of the IPv6 extension header, a larger overhead of the IPv6 extension header, and a larger message overhead.

Disclosure of Invention

The application provides a service processing method, device and system. The technical scheme of the application is as follows:

in a first aspect, a service processing method is provided, where the method includes: the network equipment receives a message comprising an option field, wherein the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different; the network device processes the message according to the first service information. For example, the network device processes the message according to the option field.

According to the technical scheme, the first service information and the second service information are carried in the same option field of the message, the first service information corresponds to the first service, the second service information corresponds to the second service, and the first service and the second service are different. That is, the same option field of the same message carries service information of at least two different services. In other words, the same option field of the same message can carry service information of at least two different services. Therefore, the option fields do not need to be respectively expanded for each service, and compared with the scheme of respectively expanding the option fields for each service at present, the method can save the cost caused by some fixed contents in the option fields and is beneficial to reducing the message cost.

In addition, in the current scheme of expanding the option fields for each service, each option field generally further includes some optional subfields for alignment or future expansion, and these optional subfields also tend to cause a large overhead of the message. In the technical scheme provided by the application, the same option field of the same message can carry service information of at least two different services, and compared with the scheme of respectively expanding the option fields aiming at each service at present, the method and the device can save the cost brought by some optional subfields and reduce the message cost.

Furthermore, after the network device acquires (e.g., receives or generates) the message, it is often necessary to process the message, such as forwarding the message or performing some business processing on the message. In the current scheme of expanding option fields for each service, the length of the message is larger, which results in higher complexity of processing the message by the network device and lower forwarding performance of the network device. In the technical scheme provided by the application, the same option field of the same message can carry the service information of at least two different services, so that the length of the message can be reduced, the complexity of processing the message by the network equipment is facilitated, and the forwarding performance of the network equipment is improved.

Optionally, the option field includes a first subfield and a second subfield, where the first subfield carries the first service information, and the second subfield carries the second service information. The first sub-field and the second sub-field may be referred to as service sub-fields, where the first sub-field may correspond to a first service, and the second sub-field may correspond to a second service, so that the first sub-field may carry first service information, and the second sub-field may carry second service information.

According to the technical scheme, the first sub-field corresponding to the first service and the second sub-field corresponding to the second service are arranged in the same option field, the first service information is carried through the first sub-field, and the second service information is carried through the second sub-field, so that the option field can carry the service information of at least two different services.

Optionally, the length of the first subfield is the same as the length of the second subfield.

According to the technical scheme, the length of the first sub-field corresponding to the first service is the same as the length of the second sub-field corresponding to the second service in the same option field, so that in the process that the network equipment processes the message according to the option field included in the message, if the network equipment does not support the first service and/or the second service, the network equipment can directly skip the first sub-field and/or the second sub-field, and the processing logic of the network equipment is facilitated to be simplified. And, the length of the first sub-field is the same as the length of the second sub-field, which can facilitate alignment of the first sub-field and the second sub-field.

Optionally, the option field further includes a third subfield, where third subfield carries third service information, the third service information corresponds to a third service, and the first service, the second service, and the third service are different from each other; the first sub-field, the second sub-field and the third sub-field are sequentially arranged, and the length of the third sub-field is different from that of the first sub-field. The third subfield may be referred to as a service subfield, and the third subfield corresponds to a third service, so that the third subfield may carry third service information.

According to the technical scheme, the same option field can comprise a plurality of service subfields, the lengths of the service subfields except the last service subfield in the plurality of service subfields are the same, and the length of the last service subfield is different from the lengths of the rest of service subfields. For example, the first subfield, the second subfield and the third subfield are all service subfields, and because the length of the first subfield is the same as the length of the second subfield in the same option field, in the process that the network device processes the message according to the option field included in the message, if the network device does not support the first service and/or the second service, the network device can skip the first subfield and/or the second subfield, and process the message directly according to the service information carried in the next subfield (for example, the third subfield), which is helpful to simplify the processing logic of the network device. Because the third subfield is arranged after the second subfield, the third subfield may be the last service subfield in the option field, so in the process that the network device processes the packet according to the option field included in the packet, if the network device does not support the third service, the network device may directly skip the option field, so that the length of the third subfield may be set to be different from the length of the first subfield, that is, the length of the third subfield does not need to be limited, so that the option field flexibly supports each service.

Optionally, the length of the third subfield is greater than the length of the first subfield. For example, the third subfield is the last traffic subfield in the option field. I.e. the length of the last service subfield is larger than the length of the remaining service subfields.

According to the technical scheme, the length of the third sub-field is larger than that of the first sub-field, so that the service with relatively longer service information can be used as the third service, and the service information of the third service is carried through the third sub-field. For example, the service information of the IFIT service is generally long, and the third service may be the IFIT service.

Optionally, the length of the third subfield is smaller than the length of the first subfield. For example, the third subfield is the last traffic subfield in the option field. I.e. the length of the last service subfield is smaller than the length of the remaining service subfields.

According to the technical scheme, the length of the third sub-field is smaller than that of the first sub-field, so that the service with relatively short service information can be used as the third service, and the service information of the third service is carried through the third sub-field.

Optionally, the length of the third subfield is equal to the length of the first subfield.

Optionally, the length of the first subfield and the length of the second subfield are both 2 ⁿ Bit, n is an integer greater than or equal to 3.

According to the technical scheme, the length of the first sub-field and the length of the second sub-field are 2 ⁿ Bits, therefore, may facilitate alignment of the first subfield with the second subfield and alignment of the first subfield, the second subfield with other subfields in the option field.

Optionally, the length of the first subfield and the length of the second subfield are each 8 bits, 16 bits, 32 bits or 64 bits. For example, the length of the first subfield and the length of the second subfield are both 32 bits.

According to the technical scheme, the length of the first sub-field and the length of the second sub-field are 8 bits, 16 bits, 32 bits or 64 bits, so that the first sub-field and the second sub-field can be aligned conveniently, and the first sub-field, the second sub-field and other sub-fields in the option field can be aligned conveniently.

Optionally, the option field further includes a fourth subfield, where the fourth subfield indicates a length of the first subfield and a length of the second subfield. For example, the fourth subfield indicates that the length of the first subfield and the length of the second subfield are both 32 bits. The fourth subfield may also be referred to as a length flag subfield or a length indication subfield.

According to the technical scheme, the fourth sub-field is arranged in the option field, the length of the first sub-field and the length of the second sub-field in the option field are indicated through the fourth sub-field, and network equipment can conveniently know the length of the first sub-field and the length of the second sub-field. Thus, when the network device supports the first service and/or the second service, the network device acquires the first service information from the first subfield according to the length of the first subfield, and/or acquires the second service information from the second subfield according to the length of the second subfield; when the network device does not support the first service and/or the second service, the network device skips the first sub-field and/or the second sub-field according to the length of the first sub-field and/or the length of the second sub-field.

Optionally, the option field includes a service flag subfield, where the service flag subfield corresponds to m services, the m services are different from each other, the m services include a first service and a second service, the service flag subfield indicates that the option field carries first service information and second service information, and m is an integer greater than or equal to 2. For example, the service label subfield indicates that the option field carries service information of k services in the m services, where k includes a first service and a second service, k is less than or equal to m, and k is a positive integer. The traffic sign subfield may also be referred to as a traffic indication subfield.

According to the technical scheme, the service mark sub-field is set in the option field, and the service mark sub-field is set to correspond to m services, so that the network equipment can conveniently acquire service information of which services in the m services are carried in the option field according to the service mark sub-field. For example, the network device learns, according to the service flag subfield, that the option field carries first service information corresponding to the first service and second service information corresponding to the second service.

Optionally, the service label subfield corresponds to m services by means of bit mapping. Specifically, the service marking subfield includes m flag bits, where the m flag bits correspond to the m services one by one. For example, each flag bit in the m flag bits indicates whether the option field carries service information of the service corresponding to the flag bit, a value in each flag bit may be 0 or 1, "1" indicates that the option field carries service information of the service corresponding to the flag bit, and "0" indicates that the option field does not carry service information of the service corresponding to the flag bit. In the application, a first flag bit in the m flag bits corresponds to a first service, a second flag bit in the m flag bits corresponds to a second service, the first flag bit indicates that the option field carries first service information, and the second flag bit indicates that the option field carries second service information. The value in the first flag bit and the value in the second flag bit may both be 1.

According to the technical scheme, the service mark sub-field comprises m flag bits corresponding to m services one by one, so that the network equipment can conveniently acquire whether the option field carries service information of the service corresponding to the flag bits according to each flag bit, and the message is processed according to the service information carried in the option field included in the message.

Optionally, the first flag bit and the second flag bit are arranged in sequence, and the first service information and the second service information are arranged in sequence, and the arrangement sequence of the first service information and the second service information corresponds to the arrangement sequence of the first flag bit and the second flag bit. For example, the first service information is carried in a first subfield, the second service information is carried in a second subfield, and the arrangement order of the first subfield and the second subfield corresponds to the arrangement order of the first flag bit and the second flag bit, so that the arrangement order of the first service information and the second service information corresponds to the arrangement order of the first flag bit and the second flag bit. Specifically, the first subfield and the second subfield are service subfields, the option field may include k service subfields, the k service subfields correspond to k services one by one, and each service subfield carries service information corresponding to the service of the service subfield. The m flag bits are arranged in sequence, the k service subfields are arranged in sequence, and the arrangement sequence of the k subfields corresponds to the arrangement sequence of the k flag bits corresponding to the k services.

According to the technical scheme, the option field comprises the service mark sub-field, the first sub-field corresponding to the first service and the second sub-field corresponding to the second service, the service mark sub-field comprises the first mark bit corresponding to the first service and the second mark bit corresponding to the second service, and the arrangement sequence of the first sub-field and the second sub-field corresponds to the arrangement sequence of the first mark bit and the second mark bit, so that the network equipment can conveniently determine the first sub-field and the second sub-field according to the arrangement sequence of the first mark bit and the second mark bit, and the first service information and the second service information are determined.

Optionally, the first service information is basic service information, the option field includes a service flag subfield, the service flag subfield corresponds to m services, the m services are different from each other, the m services include a second service, the service flag subfield indicates that the option field carries the second service information, and m is a positive integer.

Since the first service information is basic service information, the first service is a basic service. Optionally, the first service is different from the m services. That is, the base service is different from the m services.

Optionally, the service flag subfield indicates that the option field carries service information of k services in the m services, where the service information of the k services is located after the basic service information.

Optionally, the sub-field carrying the basic service information in the option field is a basic sub-field, and the option field includes k service sub-fields corresponding to the k services one by one, where the k service sub-fields are located after the basic sub-field.

Optionally, the length of the basic subfield is a constant value. For example, the base subfield has a length of 8 bits, 16 bits, 32 bits, or 64 bits.

According to the technical scheme, the basic sub-field is set in the option field, and the basic service information is carried by the basic sub-field, so that the option field can carry the basic service information.

Alternatively, m is greater than or equal to 4. That is, a message including the option field may support at least 4 services.

Optionally, the option field further includes a reserved subfield adjacent to the service flag subfield.

According to the technical scheme, the reserved subfield is adjacent to the service sign subfield, so that the reserved subfield can support the length expansion of the service sign subfield, and the service subfield can be expanded in the option field.

Optionally, the lowest bit of the reserved subfield is adjacent to the highest bit of the traffic flag subfield.

According to the technical scheme, the service mark subfields correspond to m services, the option fields comprise k service subfields corresponding to k services in the m services, the k service subfields are arranged in sequence, the lengths of the first k-1 service subfields in the k service subfields are the same, and the length of the last service subfield is different from the length of the first k-1 service subfields. The modification to the option field is smaller for the extended service subfield before the 1 st service subfield than for the extended service subfield after the last service subfield, and it is more convenient to extend the service subfield before the 1 st service subfield. Therefore, the lowest bit of the reserved subfield is set to be adjacent to the highest bit of the service sign subfield, so that if the service subfield needs to be expanded in the option field, the service subfield is expanded before the 1 st service subfield, and the bits are expanded from the high bit of the service sign subfield, thereby being beneficial to improving the convenience of expanding the service subfield.

Optionally, the option field further includes a type subfield and a length subfield, the type subfield indicates a type of the option field, and the length subfield indicates a length of the option field.

Optionally, the message is an IPv6 message, and the message includes an IPv6 extension header, where the IPv6 extension header includes the option field.

According to the technical scheme, the service information of at least two different services is carried in the same option field of the IPv6 extension header of the same message, compared with the scheme that the option field is respectively extended for each service, the method and the device can save the cost caused by some fixed contents in the option field, are beneficial to reducing the length of the IPv6 extension header and the cost of the IPv6 extension header.

Optionally, the IPv6 extension header includes any one of a hop-by-hop header (hop by hop header, HBH) and a destination option header (destination options header, DOH). In this way, the present application helps reduce the length of HBH or DOH.

Optionally, the first service includes any one of a slice service, a stream-following detection service, an APN service and a DetNet service; alternatively, the second service includes any one of a slice service, a flow-following detection service, an APN service, and a DetNet service. The flow-following detection service may include an IFIT service or an IOAM service, among others.

Optionally, the first service includes a slice service, and the first service information includes a slice identifier.

Optionally, the first service includes a flow-following detection service, and the first service information includes a flow identifier.

Optionally, the first service includes an APN service, and the first service information includes at least one of a user group identifier and an application group identifier.

Optionally, the first service includes a DetNet service, and the first service information includes a path identifier.

Optionally, the first service information includes a path identifier, and the first service is a path-oriented service. For example, the first traffic is a path-oriented operations administration maintenance (operations administration and maintenance, OAM) traffic, a path-oriented visualization traffic, a path-oriented traffic statistics traffic, a path-oriented performance measurement traffic, etc.

Optionally, the network device supports a first service and a second service, and the method further includes: the network device processes the message according to the second service information. For example, the second service information is carried in the second subfield, and the network device first obtains the second service information from the second subfield, and then processes the message according to the second service information.

Optionally, the network device supports the first service but not the second service, and the method further includes: the network device skips the second traffic information. For example, the second service information is carried in a second subfield, which the network device skips.

Optionally, the network device processes the message according to the first service information, including at least one of the following: the network equipment counts the message according to the first service information; the network device forwards the message according to the first service information.

Optionally, the network device processes the message according to the first service information, including: the network device processes the message according to the first service information and the local configuration information associated with the first service. The local configuration information may be program instructions.

Optionally, the first service information and the second service information are arranged in sequence, and the network device processes the message according to the arrangement sequence of the first service information and the second service information.

According to the technical scheme, the first service information and the second service information are arranged in sequence, so that in the process that the network equipment processes the message according to the option field included in the message, if the network equipment does not support the first service and/or the second service, the network equipment can skip the first service information and/or the second service information, and process the message directly according to the next service information, and the processing logic of the network equipment is facilitated to be simplified.

In a second aspect, a service processing method is provided, and the method includes: the network equipment generates a message comprising an option field, wherein the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different; the network device sends the message.

Optionally, the option field includes a first subfield and a second subfield, where the first subfield carries the first service information, and the second subfield carries the second service information.

Optionally, the option field further includes a third subfield, where third service information is carried in the third subfield, the third service information corresponds to a third service, and the first service, the second service, and the third service are different from each other; the first sub-field, the second sub-field and the third sub-field are sequentially arranged, and the length of the third sub-field is different from that of the first sub-field.

Optionally, the length of the third subfield is greater than the length of the first subfield.

Optionally, the length of the third subfield is smaller than the length of the first subfield.

Optionally, the length of the first subfield and the length of the second subfield are each 8 bits, 16 bits, 32 bits or 64 bits.

Optionally, the option field further includes a fourth subfield, where the fourth subfield indicates a length of the first subfield and a length of the second subfield.

Optionally, the option field includes a service flag subfield, the service flag subfield corresponds to m services, the m services are different from each other, the m services include a first service and a second service, the service flag subfield indicates that the option field carries first service information and second service information, and m is an integer greater than or equal to 2.

Optionally, the service flag subfield includes m flag bits, where the m flag bits correspond to m services one by one; a first flag bit in the m flag bits corresponds to a first service, a second flag bit in the m flag bits corresponds to a second service, the first flag bit indicates that the option field carries first service information, and the second flag bit indicates that the option field carries second service information.

Optionally, the first flag bit and the second flag bit are arranged in sequence, and the first service information and the second service information are arranged in sequence, and the arrangement sequence of the first service information and the second service information corresponds to the arrangement sequence of the first flag bit and the second flag bit.

Optionally, the first service is different from the m services.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Optionally, the option field further includes a reserved subfield, and the reserved subfield is adjacent to the service flag subfield.

Optionally, the option field includes a type subfield and a length subfield, the type subfield indicating a type of the option field, and the length subfield indicating a length of the option field.

Optionally, the IPv6 extension header includes any one of HBH and DOH.

Optionally, the first service information includes a path identifier, and the first service is a path-oriented service. For example, the first traffic is a path-oriented OAM traffic, a path-oriented visualization traffic, a path-oriented traffic statistics traffic, a path-oriented performance measurement traffic, etc.

Optionally, the network device supports the first service, and the method further includes: the network device processes the message according to the first service information.

Optionally, the network device further supports a second service, and the method further includes: the network device processes the message according to the second service information.

Optionally, the network device does not support the second service, and the method further includes: the network device skips the second traffic information.

Optionally, the first service information and the second service information are arranged in sequence, and the network device processes the message according to the first service information and the second service information according to the arrangement sequence of the first service information and the second service information.

Optionally, before the network device generates the message including the option field, the method further includes: the network equipment receives indication information sent by the controller, wherein the indication information is used for indicating the network equipment to generate a message comprising the option field; correspondingly, the network device generates a message including an option field, including: the network device generates the message including the option field according to the indication information.

In a third aspect, a service processing method is provided, and the method includes: the controller sends indication information to the head node, the indication information is used for indicating the head node to generate a message comprising an option field, the option field carries first service information and second service information, the first service information corresponds to the first service, the second service information corresponds to the second service, and the first service and the second service are different.

Optionally, the first service is different from the m services.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Optionally, the indication information is used for indicating the head node to generate an IPv6 message including an IPv6 extension header, where the IPv6 extension header includes the option field.

Optionally, the IPv6 extension header includes any one of HBH and DOH.

In a fourth aspect, a service processing method is provided, and the method includes: the method comprises the steps that a head node receives indication information sent by a controller, the indication information is used for indicating the head node to generate a message comprising an option field, the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different; the head node generates a message including the option field according to the indication information.

Optionally, the first service is different from the m services.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Optionally, the indicating information is configured to instruct the head node to generate an IPv6 packet including an IPv6 extension header, where the IPv6 extension header includes the option field, and the head node generates the packet including the option field according to the indicating information, including: and the head node generates an IPv6 message comprising the IPv6 extension head according to the indication information.

Optionally, the IPv6 extension header includes any one of HBH and DOH.

In a fifth aspect, a service processing apparatus is provided, which is applied to a network device, and includes a transceiver module and a processing module, where the transceiver module is configured to perform a transceiver operation in the method provided in any one of the first aspect to the fourth aspect, or the first aspect to the fourth aspect, and the processing module is configured to perform an operation other than the transceiver operation in the method provided in any one of the first aspect to the fourth aspect, or the first aspect to the fourth aspect. Wherein the transceiving operation may be a receiving and/or transmitting operation.

The device comprises:

the receiving and transmitting module is used for receiving a message comprising an option field, wherein the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different;

and the processing module is used for processing the message according to the first service information.

Optionally, the option field further includes a third subfield, where third subfield carries third service information, the third service information corresponds to a third service, and the first service, the second service, and the third service are different from each other; the first sub-field, the second sub-field and the third sub-field are sequentially arranged, and the length of the third sub-field is different from that of the first sub-field.

Optionally, the option field includes a service flag subfield, where the service flag subfield corresponds to m services, the m services are different from each other, the m services include the first service and the second service, and the service flag subfield indicates that the option field carries the first service information and the second service information, and m is an integer greater than or equal to 2.

Optionally, the service flag subfield includes m flag bits, where the m flag bits correspond to the m services one by one; a first flag bit in the m flag bits corresponds to the first service, a second flag bit in the m flag bits corresponds to the second service, the first flag bit indicates that the option field carries the first service information, and the second flag bit indicates that the option field carries the second service information.

Optionally, the first flag bit and the second flag bit are arranged in sequence, the first service information and the second service information are arranged in sequence, and the arrangement sequence of the first service information and the second service information corresponds to the arrangement sequence of the first flag bit and the second flag bit.

Optionally, the first service information is basic service information, the option field includes a service flag subfield, the service flag subfield corresponds to m services, the m services are different from each other, the m services include the second service, and the service flag subfield indicates that the option field carries the second service information, and m is a positive integer.

Optionally, the first service is different from the m services.

Optionally, the service label subfield indicates that the option field carries service information of k services in the m services, where the service information of the k services is located after the basic service information.

Optionally, the sub-field carrying the basic service information in the option field is a basic sub-field, the option field includes k service sub-fields corresponding to the k services one by one, and the k service sub-fields are located behind the basic sub-field.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Optionally, the option field further includes a type subfield and a length subfield, wherein the type subfield indicates a type of the option field, and the length subfield indicates a length of the option field.

Optionally, the message is an IPv6 message, the message includes an IPv6 extension header, and the IPv6 extension header includes the option field.

Optionally, the IPv6 extension header includes any one of HBH and DOH.

Optionally, the first service includes any one of a slice service, a flow detection service, an APN service and a DetNet service; alternatively, the second service includes any one of a slice service, a flow-following detection service, an APN service, and a DetNet service. Wherein, the flow-following detection service comprises an IFIT service or an IOAM service.

Optionally, the network device supports the first service and the second service, and the processing module is further configured to process the packet according to the second service information.

Optionally, the network device supports the first service but does not support the second service, and the processing module is further configured to skip the second service information.

Optionally, the processing module is configured to perform at least one of: counting the message according to the first service information; and forwarding the message according to the first service information.

Optionally, the processing module is specifically configured to process the packet according to the first service information and local configuration information associated with the first service.

Optionally, the first service information and the second service information are arranged in sequence, and the processing module is specifically configured to process the packet according to the arrangement sequence of the first service information and the second service information.

In a sixth aspect, a service processing apparatus is provided, applied to a network device, where the apparatus includes:

the processing module is used for generating a message comprising an option field, wherein the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different;

and the receiving and transmitting module is used for transmitting the message.

Optionally, the first service is different from the m services.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Optionally, the option field includes a type subfield and a length subfield, the type subfield indicates a type of the option field, and the length subfield indicates a length of the option field.

Optionally, the IPv6 extension header includes any one of HBH and DOH.

Optionally, the network device supports the first service, and the processing module is further configured to process the packet according to the first service information.

Optionally, the network device further supports the second service, and the processing module is further configured to process the packet according to the second service information.

Optionally, the network device does not support the second service, and the processing module is further configured to skip the second service information.

Optionally, the transceiver module is further configured to receive indication information sent by the controller, where the indication information is used to instruct the network device to generate a packet including the option field;

the processing module is specifically configured to generate the message including the option field according to the indication information.

In a seventh aspect, there is provided a service processing apparatus for use in a controller, the apparatus comprising:

the receiving and transmitting module is used for sending indication information to the head node, the indication information is used for indicating the head node to generate a message comprising an option field, the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service is different from the second service.

Optionally, the first service is different from the m services.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Optionally, the IPv6 extension header includes any one of HBH and DOH.

An eighth aspect provides a service processing apparatus for use in a head node, the apparatus comprising:

the receiving and transmitting module is used for receiving indication information sent by the controller, the indication information is used for indicating the head node to generate a message comprising an option field, the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service is different from the second service;

And the processing module is used for generating a message comprising the option field according to the indication information.

Optionally, the first service is different from the m services.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Optionally, the indication information is used for indicating the head node to generate an IPv6 message including an IPv6 extension header, the IPv6 extension header includes the option field, and the processing module is used for generating the IPv6 message including the IPv6 extension header according to the indication information.

Optionally, the IPv6 extension header includes any one of HBH and DOH.

The modules in the fifth to eighth aspects described above may be implemented based on software, hardware, or a combination of software and hardware, and the modules may be arbitrarily combined or divided based on specific implementations.

A ninth aspect provides a service processing apparatus, comprising a memory and a processor;

the memory is used for storing a computer program;

the processor is configured to execute a computer program stored in the memory to cause the service processing apparatus to perform the service processing method as provided in the first aspect or any of the alternatives of the first aspect.

In a tenth aspect, a service processing apparatus is provided, including a memory and a processor;

the memory is used for storing a computer program;

the processor is configured to execute a computer program stored in the memory to cause the service processing apparatus to perform the service processing method as provided in the second aspect or any of the alternatives of the second aspect described above.

An eleventh aspect provides a service processing apparatus, including: a memory and a processor;

the memory is used for storing a computer program;

the processor is configured to execute a computer program stored in the memory to cause the service processing apparatus to execute the service processing method as provided in the third aspect described above.

A twelfth aspect provides a service processing apparatus, including: a memory and a processor;

the memory is used for storing a computer program;

the processor is configured to execute a computer program stored in the memory to cause the service processing apparatus to execute the service processing method as provided in the fourth aspect described above.

In a thirteenth aspect, a service processing system is provided, including a first network device and a second network device;

the first network device is used for generating a message comprising an option field, and sending the message to the second network device, wherein the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different;

and the second network equipment is used for receiving the message and processing the message according to the first service information.

Optionally, the service processing system further includes: a controller, configured to send indication information to a first network device, where the indication information is configured to instruct the first network device to generate a packet including an option field;

correspondingly, the first network device is configured to generate a message including the option field according to the indication information.

Optionally, the first network device is a head node on a forwarding path of the packet, and the second network device is an intermediate node or a tail node on the forwarding path.

Optionally, the first network device is a head node or an intermediate node on a forwarding path of the packet, and the second network device is a tail node on the forwarding path.

Optionally, the service processing apparatus provided in the fifth aspect or any optional implementation manner of the fifth aspect may be used as an intermediate node or a tail node on a forwarding path of a packet, the service processing apparatus provided in the sixth aspect or any optional implementation manner of the sixth aspect may be used as a head node on a forwarding path of a packet, and the service processing apparatus provided in the seventh aspect or any optional implementation manner of the seventh aspect may be used as a controller.

Alternatively, the service processing apparatus provided by the fifth aspect or any optional implementation manner of the fifth aspect may be used as a tail node, the service processing apparatus provided by the sixth aspect or any optional implementation manner of the sixth aspect may be used as a head node or an intermediate node, and the service processing apparatus provided by the seventh aspect or any optional implementation manner of the seventh aspect may be used as a controller.

Alternatively, the service processing apparatus provided by the seventh aspect or any optional implementation manner of the seventh aspect may be used as a controller, and the service processing apparatus provided by the eighth aspect or any optional implementation manner of the eighth aspect may be used as a head node.

Alternatively, the service processing apparatus provided in the ninth aspect may be used as an intermediate node or a tail node on a forwarding path of a packet, and the service processing apparatus provided in the tenth aspect may be used as a head node on the forwarding path of the packet, where the controller includes the service processing apparatus provided in the eleventh aspect.

Alternatively, the service processing apparatus provided in the ninth aspect may be used as a tail node on a forwarding path of a packet, the service processing apparatus provided in the tenth aspect may be used as a head node or an intermediate node on the forwarding path of the packet, and the service processing apparatus provided in the eleventh aspect may be used as a controller.

Alternatively, the service processing apparatus provided in the eleventh aspect may be used as a controller, and the service processing apparatus provided in the twelfth aspect may be used as a head node on a forwarding path of a packet.

A fourteenth aspect provides a computer readable storage medium having stored therein a computer program which, when executed, implements a method of service processing as provided in any one of the above first aspect or the first aspect, or implements a method of service processing as provided in any one of the above second aspect or the second aspect, or implements a method of service processing as provided in any one of the above third aspect or the third aspect, or implements a method of service processing as provided in any one of the above fourth aspect or the fourth aspect.

A fifteenth aspect provides a computer program product comprising a program or code which, when executed, implements a method of service processing as provided in any of the above first aspect or the first aspect, or a method of service processing as provided in any of the above second aspect or the second aspect, or a method of service processing as provided in any of the above third aspect or the third aspect, or a method of service processing as provided in any of the above fourth aspect or the fourth aspect.

In a sixteenth aspect, there is provided a chip comprising programmable logic circuitry and/or program instructions, the chip, when run, implementing a method of service processing as provided in any of the above-described first aspects or any of the above-described second aspects or any of the above-described third aspects or any of the above-described fourth aspects.

In a seventeenth aspect, a data structure is provided, where the data structure includes an option field, where the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service is different from the second service. That is, the same option field carries service information of at least two different services.

Optionally, the first service is different from the m services.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Technical effects of the second aspect to the seventeenth aspect may refer to the first aspect, and are not repeated here.

The beneficial effects that this application provided technical scheme brought are:

Furthermore, after the network device acquires (e.g., receives or generates) the message, it is often necessary to process the message, such as forwarding the message or performing some business processing on the message. In the current scheme of expanding option fields for each service, the length of the message is larger, which results in higher complexity of processing the message by the network device and lower forwarding performance of the network device. In the technical scheme provided by the application, the same option field of the same message can carry the service information of at least two different services, so that the length of the message can be reduced, the complexity of processing the message by the network equipment is simplified, and the forwarding performance of the network equipment is improved.

Drawings

FIG. 1 is a schematic diagram of an option field;

FIG. 2 is a schematic diagram of another option field;

FIG. 3 is a schematic diagram of the structure of yet another option field;

FIG. 4 is a schematic diagram of one configuration of an option data subfield in the option fields shown in FIG. 3;

FIG. 5 is another schematic diagram of an alternative configuration of an option data subfield in the option field shown in FIG. 3;

FIG. 6 is a schematic diagram of still another configuration of an option data subfield in the option fields shown in FIG. 3;

FIG. 7 is a schematic diagram of yet another configuration of an option data subfield in the option fields shown in FIG. 3;

FIG. 8 is a schematic diagram of yet another option field;

FIG. 9 is a schematic diagram of yet another option field;

FIG. 10 is a schematic diagram of yet another option field;

fig. 11 is a schematic diagram of an application scenario provided in an embodiment of the present application;

fig. 12 is a schematic diagram of another application scenario provided in an embodiment of the present application;

fig. 13 is a flowchart of a service processing method provided in an embodiment of the present application;

FIG. 14 is a schematic diagram of the structure of an option field according to an embodiment of the present application;

FIG. 15 is a schematic diagram of another option field provided in an embodiment of the present application;

FIG. 16 is a schematic diagram of a structure of a further option field provided by an embodiment of the present application;

FIG. 17 is a schematic diagram of a structure of yet another option field provided by an embodiment of the present application;

fig. 18 is a schematic structural diagram of a service identifier subfield according to an embodiment of the present application;

fig. 19 is a schematic structural diagram of another service identifier subfield provided in an embodiment of the present application;

fig. 20 is a flowchart of another service processing method provided in an embodiment of the present application;

fig. 21 is a flowchart of still another service processing method provided in an embodiment of the present application;

fig. 22 is a flowchart of yet another service processing method provided in an embodiment of the present application;

fig. 23 is a flowchart of a network device processing a packet according to an embodiment of the present application;

fig. 24 is a schematic diagram of a service processing method provided in an embodiment of the present application;

FIG. 25 is a schematic diagram of a specific structure of an option field according to an embodiment of the present application;

fig. 26 is a schematic structural diagram of a service processing device according to an embodiment of the present application;

fig. 27 is a schematic structural diagram of another service processing apparatus according to an embodiment of the present application;

fig. 28 is a schematic structural diagram of still another service processing apparatus according to an embodiment of the present application;

Fig. 29 is a schematic structural diagram of yet another service processing apparatus according to an embodiment of the present application;

fig. 30 is a schematic structural diagram of still another service processing apparatus according to an embodiment of the present application;

fig. 31 is a schematic structural diagram of yet another service processing apparatus according to an embodiment of the present application;

fig. 32 is a schematic structural diagram of yet another service processing system according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

In the current development of network technology, a plurality of services can be developed for IPv6 messages. For example, these services may include a slice service, a follow-up detection service, an APN service, a DetNet service, and the like. At present, different option fields are respectively extended in an IPv6 extension header of the IPv6 packet for each service to carry service information of the corresponding service, so that the IPv6 packet can support each service. Wherein the option fields for different service extensions are independent of each other.

In this application, the slice service refers to a service related to a network slice. The on-stream detection service refers to a service related to on-stream detection. APN traffic refers to application aware network related traffic. DetNet traffic refers to deterministic network-related traffic. The flow detection service may include an IFIT service or an IOAM service, etc. The designations of slice traffic, flow-following detection traffic, APN traffic, and DetNet traffic may be different in different network scenarios. For example, in some network scenarios, slice traffic is also referred to as virtual transport network (virtual transport network, VTN) traffic.

The following describes service information of the service and an option field of the service information carrying the service at present.

By way of example, the traffic information of the slice traffic may include a slice identity (slice identification, slice ID). For VTN traffic, the slice identity may be a VTN resource identity (VTN resource ID). The option field for the VTN service extension may now be referred to in fig. 1. As shown in fig. 1, the option field includes a type subfield, a length subfield, and a VTN resource ID subfield. The length of the type subfield and the length of the length subfield are 8 bits and the length of the VTN resource ID subfield is 4 bytes. The type subfield is used to indicate the type of the option field. The length subfield is used to indicate the length of the data field (e.g., VTN resource ID subfield) of the option field. The VTN resource ID subfield is used to carry the VTN resource ID.

By way of example, the traffic information of the IFIT traffic may include a flow identification (flow identification, flow ID), packet loss measurement (packet loss measurement) identification, delay measurement (packet delay measurement) identification, etc., which may also be referred to as a flow label, flow monitoring identification (flow monitoring identification, FMonID), etc., indicating the flow to be measured. The options field currently extended for IFIT services may be referred to in fig. 2. As shown in fig. 2, the option fields include a type subfield, a length subfield, an FMonID subfield, an L flag bit, a D flag bit, and a reserved subfield. The length of the type subfield and the length of the length subfield are 8 bits, the length of the FMonID subfield is 20 bits, and the length of the reserved subfield is 10 bits. The type subfield is used to indicate the type of the option field. The length subfield is used to indicate the length of the data fields (including FMonID subfield, L flag bit, D flag bit, and reserved subfield) of the option field. The FMonID subfield is used to carry FMonID. The L flag bit may be used to carry a packet loss measurement identifier to indicate whether to perform packet loss measurement (e.g., a value of 1 in the L flag bit indicates that packet loss measurement is needed, and a value of 0 in the L flag bit indicates that packet loss measurement is not needed). The D flag bit is used to carry a delay measurement identifier to indicate whether to perform delay measurement (e.g., a value of 1 in the D flag bit indicates that delay measurement is needed, and a value of 1 in the D flag bit indicates that delay measurement is not needed). In some embodiments, the L flag bit is used to carry a packet loss measurement identifier and a delay measurement identifier, a value of 1 in the L flag bit indicates that packet loss measurement and delay measurement are required, and a value of 0 in the L flag bit indicates that packet loss measurement and delay measurement are not required.

For example, the traffic information of the IOAM traffic may include a flow identification indicating the flow to be measured. The options field for the IOAM service extension may now be referred to in fig. 3. As shown in fig. 3, the option fields include a type subfield, a length subfield, a reserved subfield, an IOAM type subfield, and an option data subfield. The length of the type subfield, the length of the length subfield, the length of the reserved subfield and the length of the IOAM type subfield are all 8 bits, and the length of the option data subfield is variable. The type subfield is used to indicate the type of the option field. The length subfield is used to indicate the length of the option field. The IOAM type subfield is used to indicate the type of the option data subfield. The option data subfield is used to carry IOAM data. The IOAM data may include flow identification, message identification, IOAM data for IOAM nodes (referring to IOAM-enabled nodes) on the forwarding path of the message, etc. The IOAM data of any IOAM node may include a node identifier of the IOAM node, an ingress port of a message into the IOAM node, an egress port of a message output from the IOAM node, an ingress timestamp of a message into the IOAM node, an egress timestamp of a message output from the IOAM node, a transmission delay of a message at the IOAM node, and the like.

Types of option data subfields may include an IOAM pre-allocation tracking option Type (IOAM pre-allocated trace option-Type), an IOAM delta tracking option Type (IOAM incremental trace option-Type), an IOAM transfer verification option Type (IOAM proof of transit option-Type, IOAM POT option-Type), an IOAM end-to-end option Type (IOAM edge-to-edge option-Type, IOAM E2E option-Type), and an IOAM direct output option Type (IOAM direct export option-Type, IOAM DEX option-Type), among others. The formats of the different types of option data subfields are different. For example, when the type of the option data subfield is the IOAM pre-allocation tracking option type or the IOAM delta tracking option type, the format of the option data subfield may be as shown in fig. 4. When the type of the option data subfield is the IOAM POT option type, the format of the option data subfield may be as shown in fig. 5. When the type of the option data subfield is the IOAM E2E option type, the format of the option data subfield may be as shown in fig. 6. When the type of the option data subfield is the IOAM DEX option type, the format of the option data subfield may be as shown in fig. 7.

Referring to fig. 4, when the type of the option data subfield is the IOAM pre-allocation trace option type or the IOAM delta trace option type, the option data subfield includes a name space (namespace) ID subfield, a node length (nodelen) subfield, a flags (flags) subfield, a remaining length (remaining) subfield, an IOAM trace type subfield, a reserved subfield, and p node data list (node data list) subfields. The length of the name space ID sub-field is 16 bits, the length of the node length sub-field is 5 bits, the length of the mark sub-field is 4 bits, the length of the remaining length sub-field is 7 bits, the length of the IOAM tracking type sub-field is 24 bits, the length of the reserved sub-field is 8 bits, and the length of the node data table field is 32 bits. Wherein the namespace ID subfield is used to carry a namespace ID. The node length subfield is used to instruct the IOAM node to add data in multiples of 4 bytes in the option data subfield. The remaining length subfield is used to indicate that data is added in the option data subfield in multiples of the remaining 4 bytes at the IOAM node. The IOAM trace type subfield is used to indicate the data type in the node data table. The p node data table subfields correspond to the p IOAM nodes, and each node data table subfield is used for carrying the IOAM data of the corresponding IOAM node, wherein the IOAM data comprises a node identifier, an entry timestamp of a message into the IOAM node, an exit timestamp of the message output from the IOAM node, and the like.

Referring to fig. 5, when the type of option data subfield is the IOAM POT option type, the option data subfield includes a namespace ID subfield, an IOAM POT type subfield, an IOAM POT flag subfield, and a POT option data subfield. The length of the name space ID subfield is 16 bits, the length of the IOAM POT type subfield and the length of the IOAM POT flag subfield are both 8 bits, and the length of the POT option data subfield is variable. Wherein the namespace ID subfield is used to carry a namespace ID. The IOAM POT type subfield is used to carry the IOAM POT type. The IOAM POT flag subfield is used for carrying an IOAM POT flag, the POT option data subfield is used for carrying IOAM POT data, and the IOAM POT data comprises a message identifier and the like.

Referring to fig. 6, when the type of the option data subfield is the IOAM E2E option type, the option data subfield includes a namespace ID subfield, an IOAM E2E type subfield, and an E2E option data subfield. The length of the name space ID subfield and the length of the IOAM E2E type subfield are both 16 bits, and the length of the E2E option data subfield is variable. Wherein the namespace ID subfield is used to carry a namespace ID. The IOAM E2E type subfield is used to carry the IOAM E2E type. The E2E option data subfield is used to carry IOAM E2E data, where the IOAM E2E data includes a packet sequence number (sequence number) for detecting packet loss, packet reordering, intra-packet repetition, etc., and the IOAM E2E data may further include an ingress timestamp of a packet into the IOAM node, an egress timestamp of a packet output from the IOAM node, etc., for detecting a packet transmission delay.

Referring to fig. 7, when the type of the option data subfield is the IOAM DEX option type, the option data subfield includes a name space ID subfield, a flag subfield, an IOAM trace type subfield, a reserved subfield, a flow identification subfield, and a sequence number subfield. The length of the name space ID sub-field and the length of the mark sub-field are both 16 bits, the length of the IOAM tracking type sub-field is 24 bits, the length of the reserved sub-field is 8 bits, and the length of the stream identification sub-field and the length of the sequence number sub-field are both 32 bits. The namespace ID subfield is used to carry the IOAM namespace. The label subfield is used to carry the IOAM DEX label. The IOAM type subfield is used to indicate which data fields should be output. The flow identification field is used to carry a flow identification. The sequence number subfield is used to carry the packet group sequence number for detecting packet loss, packet reordering, packet repetition within a group, etc.

For example, the service information of the APN service may include an APN attribute (attribute). The APN attribute may include an APN ID and an APN parameter (parameters). The APN ID may include a user group identity (user group identification, user group ID) and an application group identity (application group identification, APP group ID). The APN parameters include network performance parameters, which may include at least one of bandwidth requirement parameters, delay requirement parameters, jitter requirement parameters, and packet loss rate requirement parameters. Taking an APN parameter including a bandwidth requirement parameter, a delay requirement parameter, a jitter requirement parameter and a packet loss rate requirement parameter as an example for illustration, the current option field for APN service extension may refer to fig. 8. As shown in fig. 8, the option fields include an APN ID type subfield, a flag subfield, an APN parameter type subfield, an APN ID subfield, an intention (intent) subfield, a bandwidth requirement parameter subfield, a delay requirement parameter subfield, a jitter requirement parameter subfield, and a packet loss rate requirement parameter subfield. The length of the APN ID type subfield and the length of the mark subfield are both 8 bits, the length of the APN parameter type subfield is 16 bits, the length of the APN ID subfield is 32 bits or 128 bits, and the length of the intention subfield, the length of the bandwidth requirement parameter subfield, the length of the delay requirement parameter subfield, the length of the jitter requirement parameter subfield and the length of the packet loss rate requirement parameter subfield are both 32 bits. The APN ID type subfield is used for indicating the type of the APN ID, the type of the APN ID comprises a short APN ID and a long APN ID, the length of the APN ID subfield carrying the short APN ID is 32 bits, and the length of the APN ID subfield carrying the long APN ID is 128 bits. The flags subfield is used to carry the version of the future definition. The APN parameter type subfield is used for indicating which APN parameters are carried in the option field; for example, in bits arranged from high to low in the sub-field of the APN parameter type, the 1 st bit corresponds to the bandwidth requirement, the 2 nd bit corresponds to the delay requirement, the 3 rd bit corresponds to the jitter requirement, and the 4 th bit corresponds to the packet loss rate requirement; when the 1 st bit is set to 1, indicating that the option field carries a bandwidth requirement parameter; when the 2 nd bit is set to 1, indicating that the option field carries a time delay requirement parameter; when the 3 rd bit is set to 1, indicating that the option field carries a jitter requirement parameter; when the 4 th bit is set to 1, the option field is indicated to carry a packet loss rate requirement parameter. The APN ID sub-field is used for carrying APN ID; the APN ID subfield may include an application group identifier space and a user group identifier space, and may further include a reserved space, where the application group identifier space is used to carry an application group identifier, and the user group identifier space is used to carry a user group identifier, where the length of the application group identifier space and the length of the user group identifier space are both variable. The intention subfield is an optional subfield indicating a set of service requirements for the network. The bandwidth requirement parameter subfield is used to carry the bandwidth requirement parameter. The time delay requirement parameter subfield is used for carrying time delay requirement parameters; for example, the latency requirement parameter subfield includes a 24-bit latency requirement space for carrying the latency requirement parameter and an 8-bit reserved space. The jitter requirement parameter subfield is used for carrying jitter requirement parameters; for example, the jitter requirement parameter subfield includes a jitter requirement space of 24 bits for carrying the jitter requirement parameter and a reserved space of 8 bits. The packet loss rate requirement parameter subfield is used for carrying a packet loss rate requirement parameter; for example, the packet loss rate requirement parameter subfield includes a 24-bit packet loss rate requirement space for carrying the packet loss rate requirement parameter and an 8-bit reserved space.

For example, the traffic information of the DetNet traffic may include a path identifier (path identification, path ID) indicating a forwarding path that the packet is to traverse. The option field for the DetNet service extension may now be referred to in FIG. 9 or FIG. 10. The option field shown in fig. 9 is a DetNet strict path (strict path) option field. As shown in fig. 9, the option field includes a type subfield, a length subfield, and a path identification subfield; the length of the type subfield and the length of the length subfield are both 8 bits, and the length of the path identification subfield is 16 bits; the type subfield is used for indicating the type of the option field; the length subfield is used for indicating the length of the option field; the path identification subfield is used to carry a path identification indicating a strict path. The option field shown in fig. 10 is a DetNet loose path (drop path) option field. AS shown in fig. 10, the option fields include a type subfield, a length subfield, a system of origin (autonomous system, AS) subfield, and a path identification subfield; the length of the type subfield and the length of the length subfield are both 8 bits, the length of the source AS subfield is 16 bits, and the length of the path identification subfield is 32 bits; the type subfield is used for indicating the type of the option field; the length subfield is used for indicating the length of the option field; the source AS subfield is used to indicate the AS from which the path originated; the path identification subfield is used to carry a path identification indicating a loose path.

Currently, when a certain IPv6 packet needs to support a slicing service, an IFIT service and an APN service at the same time, option fields (for example, three option fields need to be extended for the slicing service, the IFIT service and the APN service) need to be respectively extended in an IPv6 extension header of the IPv6 packet, the option fields corresponding to the slicing service, the IFIT service and the APN service are one-to-one, service information of the slicing service is carried in an option field corresponding to the slicing service, service information of the IFIT service is carried in an option field corresponding to the IFIT service, and service information of the APN service is carried in an option field corresponding to the APN service. For example, the option field shown in fig. 1 needs to be extended for slice traffic, the option field shown in fig. 2 for IFIT traffic, and the option field shown in fig. 8 for APN traffic.

However, according to the protocol specification, the option field should include a type subfield, a length subfield, etc. for describing the fixed contents of the option field (e.g., the type subfield and the length subfield are included in the option fields shown in fig. 1 to 3 and 9 to 10). When the option fields are respectively extended for each service, each extended option field includes the fixed contents, which results in a larger length of the IPv6 extension header, a larger overhead of the IPv6 extension header, and a larger overhead of the IPv6 message. In addition, the option field typically further includes some optional subfields for alignment or future expansion (for example, the option fields shown in fig. 2 and 3 each include a reserved subfield, which may be used for alignment or future expansion), and these optional subfields also result in a larger length of the IPv6 extension header, which results in a larger overhead of the IPv6 packet. For example, when a certain IPv6 packet needs to support a slice service, an IFIT service, and an APN service at the same time, three option fields need to be extended in an IPv6 extension header of the IPv6 packet according to the current processing manner, and the length of the IPv6 extension header will be at least 70 bytes. In addition, the network device needs to process the IPv6 message in the process of forwarding the IPv6 message, the length of the IPv6 extension header is increased, and complexity of the network device in processing the IPv6 message is easily increased, so that forwarding performance of the network device is reduced.

Compared with the scheme of expanding the option fields for each service expansion respectively, the embodiment of the application provides a technical scheme that the same option field can carry service information of at least two different services, so that the cost caused by some fixed contents (such as type subfields and length subfields) in the option field can be saved, and the message cost can be reduced. And, the overhead caused by some optional subfields in the option field can be saved. The technical scheme of the embodiment of the application can reduce the length of the message, simplify the complexity of processing the message by the network equipment and improve the forwarding performance of the network equipment.

The following describes the technical solutions of the embodiments of the present application. First, an application scenario of the embodiment of the present application is described.

Please refer to fig. 11, which illustrates a schematic diagram of an application scenario provided in an embodiment of the present application. The application scenario provides a communication network, for example, the communication network is an IPv6 network. The communication network includes a plurality of network devices 101 to 106 (i.e., network device 101, network device 102, network device 103, network device 104, network device 105, and network device 106), and the network devices 101 to 106 are connected in sequence. Network devices 101-106 may be used to forward messages. For example, the network devices 101 to 106 include edge network devices, which may be used for the workstations to access the communication network, and the network devices 101 to 106 may be used for forwarding messages between different workstations accessing the communication network, so as to implement communications between the different workstations.

Each of the network devices 101 to 106 may be a switch, a router (router), a virtual switch, or a virtual router. Network devices 101-106 may be the same network device, e.g., network devices 101-106 are all routers. Alternatively, at least two of network devices 101-106 are different network devices, e.g., one of network devices 101-106 is a router and the other is a switch. The workstation accessing the above communication network may be a host, a server, a base station, a Virtual Machine (VM), etc., and the host may be a smart phone, a tablet, a desktop computer, or an internet of things (internet of things, ioT) device, etc., which is not limited in the embodiments of the present application.

The communication network includes a forwarding path for forwarding the message, and the forwarding path may include a plurality of network devices. According to the forwarding direction of the message, the network devices on the forwarding path comprise an ingress (ingress) device, an egress (egress) device and at least one transit (transit) device located between the ingress device and the egress device. The message flows into the forwarding path through the ingress device and flows out of the forwarding path through the egress device. Depending on the length of the forwarding path, the number of forwarding devices on the forwarding path is different, or the forwarding path includes only the ingress device and the egress device, but no forwarding device. In some implementations, the network device is also referred to as a network node, gateway device, routing node, routing device, or the like; the entry devices are also called head node, head node device, etc.; the egress devices are also referred to as tail nodes, tail node devices, etc.; the transfer device is also called a transfer node, an intermediate node or an intermediate node device, etc.; the forwarding path may also be referred to as a transmission path, a communication link, a communication path, a communication tunnel, a tunnel path, or the like. As shown in fig. 11, the communication network includes a forwarding path P, where the forwarding path P is: network device 101- > network device 102- > network device 103- > network device 104- > network device 105- > network device 106. Network device 101 is the head node of the forwarding path P, network device 106 is the tail node of the forwarding path P, and network devices 102 to 105 are all intermediate nodes of the forwarding path P.

In the embodiment of the present application, the same option field can carry service information of at least two different services, and the network device on the forwarding path may generate a packet including the option field. For example, the header node on the forwarding path adds the option field to the initial message to obtain a message including the option field, or the intermediate node on the forwarding path modifies the message to obtain a message including the option field, where the message received by the intermediate node includes the option field. Here, the header node will be given as an example of generating a message including the option field. After the head node generates the message including the option field, the message may be sent to the next hop device of the head node. After the next hop device receives the message including the option field, the message may be processed according to the service information carried in the option field to obtain a processed message, where the processed message includes the option field. After the next-hop device obtains the processed message, the processed message may be sent to the next-hop device of the next-hop device. After the next-hop device of the next-hop device receives the message including the option field, the message can be processed according to the service information carried in the option field. This is repeated until the message including the option field is forwarded to the tail node. The tail node can process the message according to the service information carried in the option field in the received message, and the tail node can also remove the option field in the message. For example, as shown in fig. 11, the network device 101 as the head node may generate a message including the option field and send the message to the network device 102. Then, the message including the option field is forwarded to the network device 106 as the tail node through the network device 102, the network device 103, the network device 104 and the network device 105 in sequence, and each of the network devices 101 to 106 can process the message according to the service information carried in the option field in the received message. The network device 106 acting as the tail node may also remove the option field in the message.

In a specific embodiment of the application, the head node maintains the option field, and the head node generates a message including the option field according to the option field. Or in another specific embodiment of the present application, the head node generates a message including the option field according to the indication information sent by the controller. In this another embodiment, the application scenario provided in the embodiment of the present application further includes a controller, where the controller is connected to the head node, and the controller may send indication information to the head node to instruct the head node to generate a packet including the option field. For example, please refer to fig. 12, which shows a schematic diagram of another application scenario provided in an embodiment of the present application, where the application scenario provides a communication network, and the communication network further includes a controller 100, where the controller 100 is connected to a network device 101. The controller 100 may also be connected to at least one of the controllers 102-106 (not shown in fig. 12), which is not limited in this embodiment.

The controller 100 may integrate functions such as network management, traffic control, and network analysis. The controller 100 may be a functional module deployed in a server, or a server cluster formed by a plurality of servers, or a cloud computing service center, or other devices or modules with network control functions.

The controller 100 may generate and transmit indication information to the network device 101. The network device 101 may generate a message including the option field according to the indication information. Optionally, the indication information is indication information of the option field (for example, is an identifier of the option field), where the indication information indicates the option field, the network device 101 may maintain multiple option fields, and the network device 101 determines, from the multiple option fields maintained by the network device 101, the option field indicated by the indication information according to the indication information, so as to generate a packet including the option field. Or, the indication information includes configuration information of the option field, and the network device 101 generates the option field according to the indication information, and further generates a message including the option field. Alternatively, the indication information includes the option field, and the network device 101 generates a message including the option field according to the indication information, which is not limited in the embodiment of the present application.

It should be noted that the application scenarios shown in fig. 11 and fig. 12 are only used as examples, and are not used to limit the technical solutions of the present application. In an implementation, the controller may also be integrated in the network device, e.g. the controller is integrated in the head node. The communication network may include more or fewer devices than those shown in fig. 11 and 12, and the number of network devices and the number of controllers may be configured as desired, which is not limited in this embodiment of the present application.

The above is an introduction to the application scenario of the present application, and the following describes an embodiment of the service processing method of the present application.

Referring to fig. 13, a flowchart of a service processing method provided in an embodiment of the present application is shown. The method may be applied to a service processing system comprising network device a and network device B. By way of example, the service processing system is a communication network as shown in fig. 11 or 12, the network device a may be the network device 101, and the network device B may be any one of the network devices 102 to 106. As shown in fig. 13, the method includes the following steps S301 to S304.

S301, the network equipment A generates a message A comprising an option field, wherein the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different.

In a specific embodiment, the network device a is a head node, and the network device a adds an option field to an initial message from a workstation (e.g., a host) accessing the network device a to obtain a message a including the option field. In another embodiment, the network device a is an intermediate node, and the option field is included in the packet B received by the network device a from the previous hop device of the network device a, and the network device a may modify the packet B to obtain the packet a including the option field. For example, the network device a modifies the option field included in the packet B, and specifically, the network device a modifies the information carried in the option field included in the packet B, which is not limited in this embodiment of the present application.

In this embodiment of the present application, the message a may be an IPv6 message, where the message a includes an IPv6 extension header, and the option field may be located in the IPv6 extension header. As an example, network device a is a header node, and encapsulates an IPv6 extension header including the option field in an initial message to obtain a message a; or the initial message comprises an IPv6 extension header, and the network equipment A adds the option field in the IPv6 extension header of the initial message to obtain the message A. As another example, network device a is an intermediate node, and a message B received by network device a from a previous hop device of network device a includes an IPv6 extension header, where the IPv6 extension header includes the option field, and network device a modifies the IPv6 extension header to obtain a message a.

In the IPv6 technology, the IPv6 extension header may include HBH, DOH, routing Header (RH), fragment Header (FH), etc., and, according to service requirements, one IPv6 packet may include at least one IPv6 extension header. In the embodiment of the present application, the IPv6 extension header including the option field may be HBH or DOH. That is, the option field may be located in HBH or DOH. For example, the packet a includes an HBH, and the option field may be located in the HBH. Alternatively, the message a includes a DOH, and the option field may be located in the DOH. As an example, the message a includes RH and two DOHs, where one of the two DOHs is located before RH and the other DOH is located after RH (e.g., the DOH located before RH is referred to as a first DOH and the DOH located after RH is referred to as a second DOH), and the option field may be located in the first DOH or in the second DOH. If the option field is located in the HBH, each network device that receives the packet a may process the packet a according to the option field. If the option field is located in the first DOH, each network device that receives the message a and hits in the destination address of the message a may process the message a according to the option field. If the option field is located in the second DOH, the tail node only needs to process the message A according to the option field.

In a specific embodiment, the option field may include a first subfield and a second subfield, where the first subfield may correspond to a first service,the second sub-field may correspond to a second service, where the first sub-field carries the first service information, and the second sub-field carries the second service information, so that the option field carries the first service information and the second service information. The length of the first subfield and the length of the second subfield may be constant values, and the length of the first subfield and the length of the second subfield may be the same. Optionally, the length of the first subfield and the length of the second subfield are both 2 ⁿ Bit, n is an integer greater than or equal to 3. For example, n is equal to 3, 4, 5 or 6, corresponding to 2 ⁿ Equal to 8, 16, 32 or 64. That is, the length of the first subfield and the length of the second subfield may each be 8 bits, 16 bits, 32 bits, or 64 bits. As a specific example, the length of the first subfield and the length of the second subfield are both 32 bits.

In a specific embodiment, the option field further includes a third subfield, where third service information is carried in the third subfield, the third service information corresponds to a third service, and the first service, the second service, and the third service are different from each other. For example, the first service is a slice service, the second service is an APN service, and the third service is an IFIT service. The first sub-field, the second sub-field and the third sub-field may be sequentially arranged, the length of the third sub-field may be variable, and the length of the third sub-field may be different from the length of the first sub-field. For example, the length of the third subfield is greater than the length of the first subfield. In other embodiments, the length of the third subfield may be less than or equal to the length of the first subfield, which is not limited in the embodiments of the present application.

As can be seen from the foregoing description, the first subfield, the second subfield and the third subfield are all used to carry service information, and thus, the first subfield, the second subfield and the third subfield can be referred to as service subfields. In some embodiments, the traffic subfields are also referred to as spaces (spaces) or containers (containers). For example, a first subfield may be referred to as a first space or a first container, a second subfield may be referred to as a second space or a second container, and a third subfield may be referred to as a third space or a third container. In a specific embodiment, the option field includes k service subfields, where the k service subfields correspond to k services one by one, the k services are different from each other, and k is a positive integer. The k service subfields may be sequentially arranged, lengths of the first k-1 service subfields of the k service subfields may be the same, and lengths of the kth service subfield (i.e., the last service subfield) and the first k-1 service subfields may be different. The first subfield and the second subfield may be two service subfields of the first k-1 service subfields, and the third subfield may be the kth service subfield.

In a specific embodiment, the option field further includes a fourth subfield, where the fourth subfield indicates a length of the first subfield and a length of the second subfield. For example, the fourth subfield indicates that the length of the first subfield and the length of the second subfield are both 32 bits. The fourth subfield indicates the length of the first subfield and the length of the second subfield indicates that the value in the fourth subfield indicates the length of the first subfield and the length of the second subfield. Optionally, the option field includes k service subfields, and the first k-1 service subfields of the k service subfields include a first subfield and a second subfield, and the fourth subfield may indicate the length of the first k-1 service subfields, so that the fourth subfield may indicate the length of the first subfield and the length of the second subfield. Since the fourth subfield indicates the length of the service subfield, the fourth subfield may also be referred to as a length flag subfield or a length indication subfield, which is not limited in the embodiment of the present application.

In a specific embodiment, the option field includes a service flag subfield, where the service flag subfield corresponds to m services, the service flag subfield indicates that service information of k services in the m services is carried in the option field, the m services are different from each other, m is a positive integer, and k is an integer less than or equal to m. Alternatively, m.gtoreq.4, e.g. m=8.

In a specific embodiment, the service flag subfield indicates that the option field includes k service subfields corresponding to the k services one by one, and the k service subfields are corresponding to service information carrying the k services one by one, so that the service flag subfield indicates that the option field carries service information of the k services. The lengths of the first k-1 service subfields of the k service subfields may be the same, and the length of the last service subfield may be different from the length of the first k-1 service subfields. In other embodiments, the length of the last service subfield may be the same as the length of the first k-1 service subfields, which is not limited in this embodiment of the present application. In the embodiment of the present application, since the service flag subfield indicates that the option field carries service information, the service flag subfield may also be referred to as a service indication subfield.

In a specific embodiment, the service flag subfield includes m flag bits, where the m flag bits correspond to the m services one by one, and each flag bit is used to indicate whether the option field carries service information corresponding to the service corresponding to the flag bit. For example, the value in each flag bit may be 0 or 1, where "1" indicates that the option field carries service information of the service corresponding to the flag bit, and "0" indicates that the option field does not carry service information of the service corresponding to the flag bit. The m flag bits may be arranged in sequence, and service information of k services carried in the option field may also be arranged in sequence, where an arrangement order of the service information of k services may correspond to an arrangement order of the m flag bits. For example, the service information of the k services is carried in k service subfields in a one-to-one correspondence, the k service subfields are arranged in sequence, and the arrangement sequence of the k service subfields corresponds to the arrangement sequence of the m flag bits. In this embodiment of the present application, the m flag bits may be arranged in order from high to low, or may be arranged in order from low to high. The k service subfields are arranged in order from the direction closer to the service logo subfield to the direction farther from the service logo subfield (e.g., in order from the 1 st 32 bits closer to the option field to the 1 st 32 bits farther from the option field). The arrangement sequence of the k service subfields corresponds to the arrangement sequence of the m flag bits, and includes: the arrangement sequence of the k service subfields corresponds to the m flag bits according to the arrangement sequence from the high order to the low order, namely the k service subfields correspond to the m flag bits in sequence; or, the arrangement sequence of the k service subfields corresponds to the m flag bits from the low order to the high order, that is, the k service subfields correspond to the m flag bits in the reverse order, which is not limited in the embodiment of the present application.

In a first specific embodiment of the present application, the m services corresponding to the service identifier subfield include a first service and a second service, and the service identifier subfield indicates that the option field carries first service information and second service information. For example, the service label subfield indicates that the option field carries service information of k services in the m services, where the k services include a first service and a second service, so that the service label subfield indicates that the option field carries the first service information and the second service information. The m flag bits in the service flag subfield include a first flag bit and a second flag bit, where the first flag bit corresponds to a first service, the second flag bit corresponds to a second service, the first flag bit indicates that the option field carries first service information, and the second flag bit indicates that the option field carries second service information. The first flag bit and the second flag bit may be arranged in sequence, and the first service information and the second service information may be arranged in sequence, where the arrangement sequence of the first service information and the second service information corresponds to the arrangement sequence of the first flag bit and the second flag bit. For example, the arrangement order of the first service information and the second service information corresponds to the arrangement order of the first flag bit and the second flag bit from the high position to the low position, or the arrangement order of the first service information and the second service information corresponds to the arrangement order of the first flag bit and the second flag bit from the low position to the high position, which is not limited in the embodiment of the present application.

In this embodiment of the present application, the option field may carry basic service information, where the basic service information corresponds to a basic service, and the basic service may be any one of a slice service, a flow-following detection service, and a DetNet service, and the flow-following detection may include an IFIT service or an IOAM service. The basic service may or may not belong to m services corresponding to the service identifier subfield. In a specific embodiment, the basic service belongs to m services corresponding to the service marking subfield, and the basic service may be any one of the k services. For example, the basic service is the first service, the basic service information is the first service information, and the content of the option field may refer to the first embodiment. In another specific embodiment, the basic service does not belong to m services corresponding to the service label subfield. For example, the basic service is the first service, the basic service information is the first service information, but the first service does not belong to m services corresponding to the service label subfield, and the content of the option field may refer to the following second embodiment.

In a second specific embodiment of the present application, the first service is a basic service, the first service information is basic service information, and the m services corresponding to the service marking subfield include a second service, where the service marking subfield indicates that the option field carries the second service information. For example, the service label subfield indicates that the option field carries service information of k services of the m services, where the k services include the second service, so that the service label subfield indicates that the option field carries the second service information. For example, the m flag bits in the service flag subfield include a second flag bit, where the second flag bit corresponds to a second service, and the second flag bit indicates that the option field carries second service information.

Wherein the second service information may be located after the basic service information. For example, the service information of the k services may be located after the basic service information (i.e., the first service information), and the service information of the k services may be arranged in sequence. In a specific embodiment, the option field includes a basic subfield (for example, the first subfield is a basic subfield) and k service subfields corresponding to the k services one to one, where the basic subfield carries basic service information, and the k service subfields are arranged in sequence after the basic subfield. Wherein the length of the basic subfield is a constant value, for example, the length of the basic subfield is 8 bits, 16 bits, 32 bits or 64 bits. The length of the base subfield may be equal to the length of the first k-1 traffic subfields of the k traffic subfields, e.g., the length of the base subfield and the length of the first k-1 traffic subfields are 32 bits. In other embodiments, the length of the basic subfield may be variable, and the length of the basic subfield may not be equal to the length of the first k-1 service subfields, which is not limited in this embodiment of the present application.

In the second embodiment, the option field carries basic service information, but the basic service information is not indicated by the service label subfield. In other words, in the second embodiment, the option field will generally necessarily carry basic service information, or default the option field carries basic service information.

In a specific embodiment, the option field further includes a reserved (reserved) subfield, the reserved subfield is adjacent to the service flag subfield, and the reserved subfield can be used for length extension of the service flag subfield, so as to support extension of the service subfield in the option field. For example, the lowest bit of the reserved subfield is adjacent to the highest bit of the traffic flag subfield. Since the service flag subfield corresponds to m services, the option field includes k service subfields corresponding to k services in the m services one by one, lengths of first k-1 service subfields in the k service subfields may be the same, and lengths of the kth service subfields may be different from lengths of the first k-1 service subfields. Compared with the expansion service subfield after the kth service subfield, the expansion service subfield before the 1 st service subfield has less change to the option field and more convenient expansion service subfield before the 1 st service subfield, so that the setting of the lowest bit of the reserved subfield adjacent to the highest bit of the service sign subfield in the embodiment of the application is beneficial to improving the convenience of expanding the service subfield. The reserved subfield can also be used for other functional extensions, which are not limited by the embodiments of the present application.

In a specific embodiment, the option field further includes a type subfield and a length subfield, the type subfield indicates a type of the option field, and the length subfield indicates a length of the option field. The option field may be a type length value (type lenght value, TLV) field, where the k service subfields, the length flag subfield (i.e., the fourth subfield), the service flag subfield, the base subfield, and the reserved subfield all belong to a value (value) subfield of the option field.

As an example of the present application, fig. 14 is a schematic structural diagram of an option field provided in an embodiment of the present application. The option field includes a type subfield, a length subfield, a reserved subfield, a service flag subfield, and k service subfields (service subfield 1 to service subfield k). The length of the type subfield, the length of the length subfield, the length of the reserved subfield and the length of the service identification subfield are all 8 bits. The k service subfields are arranged in order from the near service flag subfield to the far service flag subfield, the length of the first k-1 service subfields in the k service subfields is 32 bits, and the length of the kth service subfield (i.e., the last service subfield) is greater than the length of the first k-1 service subfields, for example, the length of the kth service subfield is 64 bits.

As another example of the present application, fig. 15 is a schematic structural diagram of another option field provided in an embodiment of the present application. Unlike the option field shown in fig. 14, the option field shown in fig. 15 further includes a length label subfield (i.e., the aforementioned fourth subfield). The length label subfield indicates the length of the first k-1 traffic subfields of the k traffic subfields. In the option field shown in fig. 15, the length flag subfield has a length of 2 bits and the reserved subfield has a length of 6 bits.

As yet another example of the present application, fig. 16 is a schematic structural diagram of yet another option field provided in an embodiment of the present application. Unlike the option field shown in fig. 14, the option field shown in fig. 16 further includes a basic subfield. k service subfields are arranged after the basic subfield in order from near to far from the basic subfield. The basic subfield corresponds to a basic service, and the length of the basic subfield is 32 bits.

As yet another example of the present application, fig. 17 is a schematic structural diagram of yet another option field provided in an embodiment of the present application. Unlike the option field shown in fig. 14, the option field shown in fig. 17 further includes a length-marking subfield (i.e., the aforementioned fourth subfield) and a base subfield. k service subfields are arranged after the basic subfield in order from near to far from the basic subfield. The length label subfield indicates the length of the first k-1 traffic subfields of the k traffic subfields. The length of the length-marking subfield is 2 bits, the length of the reserved subfield is 6 bits, and the length of the basic subfield is 32 bits.

In the option fields shown in fig. 14 to 17, the service flag subfield corresponds to m services (for example, service 1 to service m), and the service flag subfield indicates that the option field carries service information of k services in the m services, where the k service subfields correspond to the k services one by one. For example, service subfield 1 corresponds to service S1, service subfield 2 corresponds to service S2, service subfield 3 corresponds to service S3. By way of example, fig. 18 and 19 show two structural diagrams of the traffic label subfield. The service flag subfield includes m flag bits (for example, m=8), where the m flag bits correspond to the m services one by one, and an arrangement sequence of the m flag bits corresponds to an arrangement sequence of the k service subfields. The m flag bits include flag bits 1 to flag bit m, and the flag bits 1 to flag bit m are in one-to-one correspondence with the service 1 to the service m. As shown in fig. 18, the flag bits 1 to m are arranged in sequence from the high order to the low order, and the arrangement sequence of the k service subfields corresponds to the flag bits 1 to m. As shown in fig. 19, the flag bits 1 to m are arranged in sequence from the lower bit to the upper bit, and the arrangement sequence of the k service subfields corresponds to the flag bits 1 to m and the reverse sequence.

For example, referring to fig. 14 to 17, for the first embodiment (the m services corresponding to the service reference subfield include a first service and a second service), the first service and the second service may be any two services in order from the service S1 to the service S (k-1), and the third service may be the service Sk. For example, the first service is service S1, the second service is service S2, the first subfield corresponding to the first service is service subfield 1, the second subfield corresponding to the second service is service subfield 2, and the third subfield corresponding to the third service is service subfield k. For another example, the first service is service S2, the second service is service S (k-1), the first subfield corresponding to the first service is service subfield 2, the second subfield corresponding to the second service is service subfield k-1, and the third subfield corresponding to the third service is service subfield k. For the second embodiment (the first service is the basic service, the m services corresponding to the service identifier subfields include the second service), the second service may be any one of the services S1 to Sk, for example, the second service may be the service S1, the third service may be the service Sk, the first subfield corresponding to the first service is the basic subfield, the second subfield corresponding to the second service is the service subfield 1, and the third subfield corresponding to the third service is the service subfield k. For another example, the second service is service S (k-1), the third service may be service Sk, the first subfield corresponding to the first service is the base subfield, the second subfield corresponding to the second service is service subfield k-1, and the third subfield corresponding to the third service is service subfield k.

The embodiment of the application takes the service mark subfield as an example, and m flag bits are included in the service mark subfield, and the m flag bits are arranged in sequence as an example, which does not form a limitation on the service mark subfield. The m flag bits may be arranged in other manners, or the service flag subfield may correspond to the m services in other manners, and the service flag subfield may indicate that the option field carries service information of the k services in other manners. For example, the service flag subfield includes m flag spaces corresponding to the m services one to one, at least one flag space of the m flag spaces has a length greater than 1 bit, the m flag spaces are arranged in sequence, and an arrangement order of the m flag spaces corresponds to an arrangement order of the k service subfields (may be sequentially corresponding or inversely corresponding). For example, the m flag spaces are each 2 bits in length. Alternatively, a part of the m flag spaces has a length of a bits (e.g., 1 bit) and another part has a length of b bits (e.g., 2 bits). Still alternatively, the m logo spaces may be different in length (e.g., the m logo spaces may be sequentially increasing in length). The embodiments of the present application are not limited in this regard.

As an example, a part of the m flag spaces has a length of a bits (e.g., 1 bit), another part has a length of b bits (e.g., 2 bits), the flag spaces having a length of a bits are arranged at intervals with the flag spaces having a length of b bits, and the m flag spaces correspond to k service subfields (may be sequentially corresponding or inversely corresponding). For example, k=3, where k services corresponding to the k service subfields include a slicing service, an APN service, and an IFIT service, and the service subfields corresponding to the slicing service, the APN service, and the IFIT service are sequentially arranged. In one case, m=k, the length of the flag space corresponding to the slice service and the length of the flag space corresponding to the IFIT service are both a bits, and the length of the flag space corresponding to the APN service is b bits; or the length of the mark space corresponding to the slice service and the length of the mark space corresponding to the IFIT service are both b bits, and the length of the mark space corresponding to the APN service is a bit. In another case, m is greater than k, and the length of the flag space corresponding to the slice service, the length of the flag space corresponding to the APN service and the length of the flag space corresponding to the IFIT service are all a bits; or the length of the mark space corresponding to the slicing service, the length of the mark space corresponding to the APN service and the length of the mark space corresponding to the IFIT service are b bits; or the length of the mark space corresponding to two services in the slicing service, the APN service and the IFIT service is a bit, and the length of the mark space corresponding to the other service is b bit; or the length of the mark space corresponding to two services in the slicing service, the APN service and the IFIT service is b bits, and the length of the mark space corresponding to the other service is a bits.

As an example, the m flag spaces are different in length (e.g., the m flag spaces are sequentially increased in length), and the m flag spaces are arranged in order from the large to the small in length, or are arranged in order from the small to the large in length, and the m flag spaces correspond to k service subfields (may be sequentially or inversely). For example, the k services corresponding to the k service subfields include a slicing service, an APN service, and an IFIT service, the service subfields corresponding to the slicing service, the service subfields corresponding to the APN service, and the service subfields corresponding to the IFIT service are sequentially arranged, the length of a flag space corresponding to the slicing service in the m flag spaces is a bit, the length of a flag space corresponding to the APN service is b bit, the length of a flag space corresponding to the IFIT service is c bit, and a, b, and c sequentially increase, or a, b, and c sequentially decrease.

As an example, the service flag subfield indicates, through the value of the service flag subfield, which services are carried in the option field. For example, the service label subfield has a first value (may be a binary value or a binary sequence), and indicates that the option field carries service information of service 1, service 2 and service 3; or the value of the service mark sub-field is a second value (can be a binary value or a binary sequence), and the service mark sub-field indicates that the option field carries service information of service 4, service 5 and service 6; or, the service label subfield has a third value (which may be a binary value or a binary sequence), and indicates that the option field carries service information of service 1, service 3, service 4, and so on.

In the embodiment of the present application, the first service may include any one of a slice service, a flow detection service, an APN service, and a DetNet service. The second service may include any one of a slice service, a flow-following detection service, an APN service, and a DetNet service. The third service may include any one of a slice service, a flow-following detection service, an APN service, and a DetNet service. And the first service, the second service, and the third service are different from each other. For example, the first service is a slice service, the second service is an APN service, and the third service is an on-stream detection service. The flow detection service includes IFIT service or IOAM service, and may also be other flow detection service, which is not limited in the embodiment of the present application.

In this embodiment of the present application, the service information of any service may include information related to the service, for example, the service information of any service includes the service information of the service carried in the option field when the option field is independently extended for the service at present, and may also include other information related to the service, which is not limited in this embodiment of the present application. Exemplary, the service information of the slice service includes a slice identifier; the service information of the stream-following detection service comprises a stream identifier; the service information of the APN service comprises an APN attribute, the APN attribute comprises an APN ID and an APN parameter, the APN ID comprises at least one of a user group identifier and an application group identifier, and the APN parameter comprises at least one of a bandwidth requirement parameter, a time delay requirement parameter, a packet loss rate requirement parameter and a jitter requirement parameter; the traffic information of the DetNet traffic includes a path identification.

S302, the network equipment A sends a message A to the network equipment B.

In a specific embodiment, the network device B is a next-hop device of the network device a, and the network device a searches a routing table of the network device a according to a destination address of the message a, so as to determine an output port corresponding to the message a in the network device a, and the network device a sends the message a to the network device B through the output port corresponding to the message a. For example, as shown in fig. 11 and 12, the network device a is the network device 101, the network device B is the network device 102, and the network device 101 sends the message a to the network device 102 through the output port corresponding to the message a. Alternatively, network device a is network device 102, network device B is network device 103, and network device 102 sends message a to network device 103 through the output port corresponding to message a.

In another embodiment, the network device B is not the next hop device of the network device a, and the network device B is connected to the network device a through another network device, and the network device a sends the message a to the network device B through the other network device. As shown in fig. 11 and 12, for example, network device a is network device 101, network device B is network device 103, and network device 101 sends a message a to network device 103 through network device 102, i.e., network device 101 forwards message a to network device 102, and network device 102 forwards message a to network device 103. Alternatively, network device a is network device 102 and network device B is network device 104, with network device 102 sending message a to network device 104 through network device 103, i.e., network device 102 forwarding message a to network device 103, and network device 103 forwarding message a to network device 104.

S303, the network equipment B receives the message A.

And the network equipment B receives the message A corresponding to the message A sent by the network equipment A to the network equipment B.

S304, the network equipment B processes the message A according to the first service information carried in the option field of the message A.

In the embodiment of the present application, the network device B may be an intermediate node or a tail node on the forwarding path of the packet a. As shown in S301, the option field may be located in the HBH, the first DOH, or the second DOH of the packet a. If the option field is located in the HBH, each network device that receives the packet a may process the packet a according to the option field. If the option field is located in the first DOH, each network device that receives the message a and hits in the destination address of the message a may process the message a according to the option field. If the option field is located in the second DOH, the tail node only needs to process the message A according to the option field.

In one embodiment, network device B is an intermediate node. If the option field is located in the HBH of the message a, the network device B processes the message a according to the option field. If the option field is located in the first DOH of the message a, the network device B determines whether the network device B hits the destination address of the message a, if the network device B hits the destination address of the message a, the network device B processes the message a according to the option field, and if the network device B does not hit the destination address of the message a, the network device B does not process the message a according to the option field. If the option field is located in the second DOH of the message a, the network device B does not process the message a according to the option field.

In another embodiment, network device B is a tail node. If the option field is located in the HBH of the message a, the network device B processes the message a according to the option field. If the option field is located in the first DOH of the message a, the network device B determines whether the network device B hits the destination address of the message a, if the network device B hits the destination address of the message a, the network device B processes the message a according to the option field, and if the network device B does not hit the destination address of the message a, the network device B does not process the message a according to the option field. If the option field is located in the second DOH of the message a, the network device B processes the message a according to the option field. In a specific embodiment, the network device B as the tail node may further remove the option field in the packet a, which is not limited in this embodiment of the present application.

In this embodiment, the network device B processes the packet a according to the option field. The option field may carry service information of k services, where the service information of the k services may be arranged in sequence, and the network device B may process the packet a sequentially according to the arrangement sequence of the service information of the k services. For example, the k services include a first service and a second service, first service information corresponding to the first service and second service information corresponding to the second service are arranged in sequence, and the network device B processes the packet a according to the arrangement sequence of the first service information and the second service information included in the packet a in sequence. In this embodiment of the present application, the network device B may support all the k services, or may not support at least one of the k services, and if the network device B supports a certain service in the process of processing the packet a according to the option field, the network device B processes the packet a according to the service information of the service included in the packet a, and if the network device B does not support a certain service, the network device B skips the service information of the service included in the packet a. For example, the option field includes a service flag field and k service subfields corresponding to the k services one by one, and for any one of the k services (for example, service S1), the network device B determines a service subfield (for example, service subfield 1) corresponding to the service S1 according to the service flag field; if the network equipment B supports the service S1, the network equipment acquires service information of the service S1 from the service subfield 1 included in the message A, and processes the message A according to the service information of the service S1; if the network device B does not support the service S1, the network device skips the service subfield 1 included in the message a, thereby skipping the service information of the service S1.

In this embodiment, the network device B supports the first service as an example, and the network device B processes the packet a according to the first service information (i.e., the service information of the first service) carried in the option field. In a specific embodiment, the network device B first obtains the first service information from the first subfield in the option field, and then processes the packet a according to the first service information and the local configuration information associated with the first service. The local configuration information associated with the first service may include program instructions associated with the first service in network device B, and may also include other configuration information associated with the first service in network device B. Wherein the program instructions comprise at least one processing action (action) which may comprise, for example, a statistical action, a detection action, a forwarding action, etc. In this embodiment of the present application, the processing, by the network device B, the packet a according to the first service information and the local configuration information associated with the first service may include: the network device B determines a program instruction associated with the first service from the network device B according to the first service information included in the message a, and then executes the program instruction to process the message a.

In a specific embodiment, the first service is a slice service, and the local configuration information associated with the first service in the network device B may include resource configuration information associated with the slice service in the network device B, program instructions associated with the slice service in the network device B, and the like. The resource configuration information associated with the slice service in the network device B may include a slice identifier of the slice service, a slice interface carrying the slice service in the network device B, a correspondence between the slice identifier of the slice service and the slice interface carrying the slice service in the network device B, and so on. The program instructions associated with the slice service in the network device B may include a slice identifier of the slice service and a processing action associated with the slice service in the network device B, for example, the processing action associated with the slice service in the network device B includes a forwarding action, a slice interface corresponding to the forwarding action, and so on. The first service is a slice service, the first service information is a slice identifier, and the network device B processes the packet a according to the first service information included in the packet a and local configuration information associated with the first service, where the packet a includes: the network device B determines the program instruction associated with the slice service from the network device B according to the slice identifier included in the packet a, and then executes the processing action included in the program instruction to process the packet a, for example, the network device B may send the packet a to the next hop device of the network device B through the slice interface associated with the slice service.

In another embodiment, the first service is a flow-along detection service, and the local configuration information associated with the first service in the network device B includes program instructions associated with the flow-along detection service in the network device B. Program instructions associated with the on-stream detection service in network device B may include a flow identification of the on-stream detection service and processing actions associated with the on-stream detection service in network device B, such as statistical actions, detection actions, etc., which may include, in particular, counting which content. For example, counting the receiving time stamp of the message of the stream detection service received by the network device B, counting the sending time stamp of the message of the stream detection service sent by the network device B, counting the message sequence number of the message of the stream detection service, counting the transmission time delay of the message of the stream detection service in the network device B, etc. The flow-following detection service may include an IFIT service or an IOAM service, among others. As an example, the first service is an IFIT service, the first service information is a flow identifier, and the network device B processes the packet a according to the first service information included in the packet a and local configuration information associated with the first service, including: the network device B determines the program instruction associated with the IFIT service from the network device B according to the flow identifier included in the message a, and then performs the processing action included in the program instruction to process the message a. For example, by executing the processing actions included in the program instruction, the network device B may count the receiving timestamp of the packet a received by the network device B, count the sending timestamp of the packet a sent by the network device B, count the packet sequence of the packet a, and other transmission quality information, and the network device B may report these transmission quality information and the flow identifier to the controller, so that the controller determines the transmission quality of the IFIT service according to the transmission quality information of the IFIT service sent by the network devices. As another example, the first service is an IOAM service, the first service information is a flow identifier, and the network device B processes the packet a according to the first service information included in the packet a and local configuration information associated with the first service, including: the network device B determines the program instruction associated with the IOAM service from the network device B according to the flow identifier included in the message a, and then performs a processing action included in the program instruction to process the message a. For example, the network device B performs detection processing such as service-level agreement (SLA) detection, path verification, and the like according to the message a by executing the processing actions included in the program instructions, and specifically may include adding, by the network device B, a reception timestamp that the network device B receives the message a, a transmission timestamp that the network device B transmits the message a, a transmission delay of the message a in the network device B, metadata (MD) of the network device B, and the like. The MD of network device B may include an identification of network device B. The network device B may also perform, for example, SLA quality determination, path verification, and so on, according to the detection information (for example, the identifier of the network device) carried in the packet a.

In still another embodiment, the first service is an APN service, and the local configuration information associated with the first service in the network device B may include resource configuration information associated with the APN service in the network device B, a program instruction associated with the APN service in the network device B, and so on. The resource configuration information associated with the APN service in the network device B may include a forwarding interface allocated by the network device B to the APN service, a bandwidth allocated by the network device B to the APN service, and so on, so as to ensure requirements of bandwidth, time delay, jitter, packet loss rate, and so on of the APN service. The program instructions associated with the APN service in the network device B may include an APN attribute of the APN service and a processing action associated with the APN service in the network device B, for example, including a forwarding action, a forwarding interface corresponding to the forwarding action, and so on. For example, the first service is an APN service, the first service information includes an APN attribute, the APN attribute includes an APN ID and an APN parameter, the APN ID includes a user group identifier and an application group identifier, the APN parameter includes at least one of a bandwidth requirement parameter, a delay requirement parameter, a jitter requirement parameter and a packet loss rate requirement parameter, and the network device B processes the packet a according to the first service information included in the packet a and local configuration information associated with the first service, where the packet a includes: and the network equipment B determines the program instruction associated with the APN service from the network equipment B according to the APN attribute included in the message A, and then executes the processing action included in the program instruction to process the message A. For example, the network device B sends the packet a to the next hop device of the network device B through the forwarding interface associated with the APN service.

In yet another embodiment, the first service is a DetNet service, and the local configuration information associated with the first service in the network device B includes resource configuration information associated with the DetNet service in the network device B, program instructions associated with the DetNet service in the network device B, and the like. The resource configuration information associated with the DetNet service in the network device B may include a path identifier of the DetNet service, a path resource of a forwarding path indicated by the path identifier in the network device B, for example, an interface corresponding to the forwarding path, an interface bandwidth corresponding to the forwarding path, an interface rate corresponding to the forwarding path, and so on. The program instructions associated with the DetNet service in network device B may include a path identifier of the DetNet service and a processing action associated with the DetNet service in network device B, including, for example, a forwarding action, a forwarding interface corresponding to the forwarding action, and so on. For example, the first service is a DetNet service, the first service information is a path identifier, and the network device B processes the packet a according to the first service information included in the packet a and local configuration information associated with the first service, where the packet a includes: the network equipment B determines the program instruction associated with the DetNet service from the network equipment B according to the path identifier included in the message A, and then executes the processing action included in the program instruction to process the message A. For example, the network device B determines, in the network device B, a path resource of a forwarding path indicated by the path identifier (for example, an interface corresponding to the forwarding path in the network device B), and sends the packet a to a next hop device of the network device B through the path resource.

The above description about the first service information, the local configuration information associated with the first service, and the network device B processes the packet a according to the first service information and the local configuration information associated with the first service is merely exemplary, and is not intended to limit the technical solution of the present application. The processing performed by the network device B according to the first service information is different according to the difference of the first service information and the difference of the local configuration information associated with the first service. In addition, the network device B may process the packet a according to other information carried in the packet a, in addition to processing the packet a according to the service information carried in the option field of the packet a, where the information may be carried in the option field or may be outside the option field. Further, in other embodiments, when the first traffic information includes a path identifier, the first traffic may be a path-oriented traffic, such as an OAM traffic oriented to a path, a visualization traffic oriented to a path, a traffic statistics traffic oriented to a path, a performance measurement traffic oriented to a path, and so on. When the first service information includes a flow identifier, the first service may be a flow-oriented service, for example, a flow-oriented OAM service, a flow-oriented visualization service, a flow-oriented traffic statistics service, a flow-oriented performance measurement service, and the like. When the first service information includes a slice identifier, the first service may be a service facing the network slice, for example, an OAM service facing the network slice, a visualization service facing the network slice, a traffic statistics service facing the network slice, a performance measurement service facing the network slice, and the like. When the first service information includes a user group identifier, the first service may be a service facing the user group, for example, an OAM service facing the user group, a visualization service facing the user group, a traffic statistics service facing the user group, a performance measurement service facing the user group, and the like. When the first service information includes an application group identifier, the first service may be an application group-oriented service, for example, an OAM service oriented to the application group, a visualization service oriented to the application group, a traffic statistics service oriented to the application group, a performance measurement service oriented to the application group, and so on.

In an alternative embodiment, the local configuration information associated with the first service in the different network devices may be the same or different. That is, for the same first service information carried in the packet a, the processing behavior of the first service association performed on different network devices is different. For example, the program instructions associated with the first service in some network devices include the first service information and the statistical action associated with the first service, the program instructions associated with the first service in other network devices include the first service information and the detection action associated with the first service, and the program instructions associated with the first service in other network devices include the first service information and the forwarding action associated with the first service, which is not limited in the embodiments of the present application. For example, the first service is an IFIT service, the first service information included in the packet is a flow identifier, and referring to fig. 11 or fig. 12, the program instructions associated with the IFIT service in the network device 101 may include: the flow identifier of the IFIT service and the transmission time stamp of the packet in which the statistical network device 101 transmits the IFIT service. Program instructions associated with the IFIT service in network device 102 may include: the flow identifier of the IFIT service and the reception timestamp of the packet in which the statistical network device 102 receives the IFIT service, and the transmission timestamp of the packet in which the statistical network device 102 transmits the IFIT service. Program instructions associated with the IFIT service in network device 103 may include: the flow identification of the IFIT service and the message sequence number of the message of the IFIT service are counted. Program instructions associated with the IFIT service in network device 104 may include: the flow identifier of the IFIT service and the transmission delay of the message of the IFIT service in the network device 104 are counted. Program instructions associated with the IFIT service in network device 105 may include: the flow identifier of the IFIT service reports to the controller the transmission quality information of the IFIT service, including, for example: the transmission time stamp of a message is sent by a certain or a plurality of network devices on the forwarding path of the message of the IFIT service, the reception time stamp of the message is received by a certain or a plurality of network devices, the transmission time delay of the message in a certain or a plurality of network devices, and the like. The first service information (for example, the flow identifier of the IFIT service) included in the program instruction associated with the first service is used by the network device to determine the local configuration information associated with the first service according to the first service information included in the message.

In addition, the embodiment of the application is illustrated by taking the option field included in the message a as an example. If the option field is not included in the message a, the network device B does not perform processing based on the option field on the message a, and the network device B may forward the message a in a conventional forwarding manner. For example, the message a is an IPv6 message and does not include the option field, and the network device B forwards the message a according to a conventional IPv6 forwarding manner, which is not limited in this embodiment of the present application.

In summary, according to the service processing method provided by the embodiment of the present application, since the service information of at least two different services can be carried in the same option field of the same packet, the overhead caused by some fixed contents and some optional subfields in the option field can be saved, which is helpful for reducing the packet overhead, further simplifying the complexity of processing the packet by the network device, and improving the forwarding performance of the network device. And because the lengths of the first k-1 business subfields in the k business subfields in the option field are equal, when the network equipment does not support a certain business, the business subfields corresponding to the business can be skipped directly according to the lengths of the business subfields corresponding to the business, the message analysis logic of the network equipment is clear, and the chip processing performance is good.

In a specific embodiment, the network device B supports a first service and a second service. The network device B may process the packet a according to the second service information carried in the option field of the packet a, in addition to processing the packet a according to the first service information carried in the option field of the packet a. As shown in fig. 20, the service processing method in the embodiment of the present application further includes the following step S305a.

S305a, the network equipment B processes the message A according to the second service information carried in the option field of the message A.

The implementation process of the network device B to process the packet a according to the second service information may refer to S304, which is not described herein.

In another embodiment, network device B supports a first service but not a second service. The network device B may skip the second service information carried in the option field of the packet a, in addition to processing the packet a according to the second service information carried in the option field of the packet a. As shown in fig. 21, the service processing method in the embodiment of the present application further includes the following step S305b.

S305B, the network equipment B skips the second service information carried in the option field of the message A.

That is, the network device B does not process the packet a according to the second service information.

The second service information corresponds to a second service, and the second service information is carried in a second subfield (i.e., a service subfield corresponding to the second service). Network device B may determine a second subfield from the traffic flag field in the option field, which network device B skips over, thereby skipping over the second traffic information.

In a specific embodiment, after the network device a generates the message a, the message a may also be processed according to the option field in the message a. For example, the network device a supports the first service and the second service, and the network device a processes the message a according to the first service information and the second service information carried in the option field. For another example, the network device a supports the first service but does not support the second service, and the network device a processes the message a according to the first service information carried in the option field, and the network device a skips the second service information. For another example, the network device a supports the second service but does not support the first service, and the network device a processes the message a according to the second service information carried in the option field, and the network device a skips the first service information. The process of processing the message a by the network device a according to the option field may refer to the process of processing the message a by the network device B according to the option field, which is not described herein in detail.

In a specific embodiment, the network device a generates the message a including the option field under the direction of the controller. Wherein the controller may be the controller 100 shown in fig. 11 or fig. 12. For example, please refer to fig. 22, which illustrates a flowchart of yet another service processing method provided in an embodiment of the present application. The method includes the following steps S2201 to S2206.

S2201, a controller sends indication information to a network device A, wherein the indication information is used for indicating the network device A to generate a message comprising an option field, the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different.

Alternatively, the controller first generates the indication information and then sends the indication information to the network device a. For example, the controller sends the indication information to network device a via a border gateway protocol (border gateway protocol, BGP) message, a network configuration protocol (network configuration protocol, netcon f) message, or other proprietary protocol message.

In a specific embodiment, the indication information includes configuration information of the option field, so as to instruct the network device a to generate a message including the option field. Alternatively, the indication information includes the option field, so as to instruct the network device a to generate a message including the option field. Or the indication information is an identifier of the option field or a name of the option field, etc., the network device a includes configuration information of the option field, and the indication information indicates the network device a to generate a message including the option field according to the configuration information of the option field in the network device a. Or the indication information is an identifier of the option field or a name of the option field, etc., and the network device a includes the option field, and the indication information instructs the network device a to generate a message including the option field according to the option field in the network device a. The configuration information of the option field may include information carried by the option field and structure information of the option field, for example, the information carried by the option field includes first service information, second service information, and the like, where the structure information of the option field includes a position of the first service information in the option field (for example, a position of the first subfield in the option field), a position of the second service information in the option field (for example, a position of the second subfield in the option field), and the embodiment of the application is not limited thereto.

S2202, the network equipment A receives the indication information sent by the controller.

For example, the network device a receives a BGP message, a netcon message, or other private protocol message that carries the indication information and is sent by the controller, and obtains the indication information from the received message.

S2203, the network equipment A generates a message A comprising the option field according to the indication information.

In a specific embodiment, the indication information includes configuration information of the option field, and the network device a generates the option field according to the configuration information of the option field, so as to generate the message a including the option field.

In another embodiment, the indication information includes the option field, and the network device a determines the option field from the indication information, so as to generate the message a including the option field.

In another embodiment, the indication information is an identifier of the option field or a name of the option field, and the network device a determines configuration information of the option field in the network device a according to the indication information, generates the option field according to the configuration information of the option field, and further generates the message a including the option field.

In another embodiment, the indication information is an identifier of the option field or a name of the option field, and the network device a determines the option field in the network device a according to the indication information, so as to generate a message a including the option field.

S2204, the network equipment A sends a message A to the network equipment B.

S2205, the network equipment B receives the message A.

S2206, the network equipment B processes the message A according to the first service information carried in the option field of the message A.

The implementation procedures of S2203 to S2206 may refer to the implementation procedures of S301 to S304 described above, and will not be described here again.

The embodiment shown in fig. 20 above is described taking the case that the network device a generates the message a including the option field according to the instruction of the controller as an example, in other embodiments, the option field may be statically configured in the network device a, and further, the network device a may generate the message including the option field, which is not limited in this embodiment of the present application.

In this embodiment of the present application, each network device on the forwarding path of the packet a may process the packet a, and at least one network device on the forwarding path of the packet a may process the packet a according to the option field in the packet a. For example, the forwarding path of the message a is the forwarding path P in fig. 11 or fig. 12 (the forwarding path P is: network device 101- > network device 102- > network device 103- > network device 104- > network device 105- > network device 106), and all of the network devices 101 to 106 can process the message a, and at least one of the network devices 101 to 106 processes the message a according to the option field in the message a. When the network device processes the message A according to the option field, the service information of the services carried by the option field is determined through the service mark field in the option field. For example, the flag bit i in the service flag field corresponds to the service i, and the network device determines whether the option field carries service information of the service i according to whether the flag bit i is set (i.e., whether the value in the flag bit i is 1). The process of processing message a by a network device on the forwarding path of message a will be described below using the example of processing message a by network device 102.

Referring to fig. 23, a flowchart of processing a message a by the network device 102 according to an embodiment of the present application is shown. The flow includes the following steps S2301 to S2309.

S2301, the network device 102 determines whether the IPv6 extension header of the message A includes the option field. If yes, S2302 to S2308 are performed; if not, S2309 is performed.

After receiving message a, network device 102 begins processing message a. Network device 102 first determines whether the option field is included in the IPv6 extension header of message a.

Wherein the IPv6 extension header includes, for example, HBH or DOH. The option field comprises a service sign sub-field, the service sign sub-field comprises m sign bits, the m sign bits are in one-to-one correspondence with m services, and the value in each sign bit is used for indicating whether the option field carries service information of the service corresponding to the sign bit.

In the embodiment of the present application, the function of processing the option field may be enabled on the network device 102 in advance, so that the network device 102 may perform this step S2301 after receiving the message a.

S2302. initializing i=1. The maximum value of i is m.

S2303, the network device 102 determines whether the ith flag bit in the service flag subfield included in the option field is set. If yes, S2304 to S2307 are performed; if not, S2308 is performed.

The network device 102 may determine whether the value in the i-th flag bit is 1. If the value in the i-th flag bit is 1, network device 102 determines that the i-th flag bit is set. If the value in the i-th flag bit is 0, network device 102 determines that the i-th flag bit is not set.

In the embodiment of the present application, if a certain flag bit in the service label subfield is set, it is indicated that the option field carries service information of a service corresponding to the flag bit; and if a certain flag bit in the service marking subfield is not set, indicating that the option field does not carry service information of the service corresponding to the flag bit. In S2303, if the network device 102 determines that the ith flag bit is set, the network device 102 determines that the option field carries service information of a service (for example, service i) corresponding to the ith flag bit, and the network device 102 performs S2304 to S2307. If the network device 102 determines that the ith flag bit is not set, the network device 102 determines that the option field does not carry service information of the service corresponding to the ith flag bit, and the network device 102 performs S2308.

S2304, the network device 102 determines whether the network device 102 supports the service i. If yes, S2305 to S2307 are performed; if not, S2308 is performed.

Service i refers to the service corresponding to the ith flag bit. If the network device 102 does not support the service i, the network device 102 skips the service information of the service i, and the network device 102 performs S2308.

S2305, the network device 102 processes the message A according to the service information of the service i carried in the option field.

The option field includes a service subfield corresponding to the service i, and the network device 102 obtains service information of the service i from the service subfield corresponding to the service i, and processes the message a according to the service information of the service i. The process of processing the packet a by the network device 102 according to the service information of the service i may refer to S304, which is not described herein.

S2306 the network device 102 determines if i is equal to m. If yes; s2307 is performed; if not, the method comprises the steps of; s2308 is performed.

Network device 102 may compare i to m to determine if i is equal to m. If i is equal to m, which indicates that the i-th flag bit is the last flag bit in the service flag subfield, the processing network device 102 of S2305 has already processed the packet a according to the service information of the service corresponding to the last flag bit, and the network device 102 ends the process of processing the packet a according to the option field, and executes S2307. If i is less than m, it indicates that the i-th flag bit is not the last flag bit in the traffic label subfield, and the option field may also carry unprocessed traffic information, so the network device 102 performs S2308.

S2307, forwarding the message A according to the processing result.

For example, the option field carries a slice identifier, and the network device 102 determines a slice interface in the network device 102 according to the slice identifier, and forwards the message a through the slice interface.

For another example, the option field carries a path identifier, and according to the path identifier, the network device 102 determines a path resource (such as an interface) of a forwarding path indicated by the path identifier in the network device 102, and forwards the message a through the path resource.

S2308. let i=i+1.

If in S2303 network device 102 determines that the i-th flag bit is not set; alternatively, in S2304 the network device 102 determines that the network device 102 does not support service i; alternatively, the network device 102 determines in S2306 that i is not equal to m; the network device 102 executes S2308, starting execution of S2303 to S2307 based on i+1.

S2309, the network device 102 forwards the message A according to the conventional IPv6 forwarding mode.

In order to facilitate understanding of the technical solution of the present application, a specific example is described below to describe the service processing method of the present application.

Fig. 24 is a schematic diagram of a service processing method according to an embodiment of the present application. Fig. 24 illustrates that a message is processed by a network device on a forwarding path P (forwarding path P is: network device 101- > network device 102- > network device 103- > network device 104- > network device 105- > network device 106) during transmission of the message on the forwarding path P. The packet includes a payload (payload), an IPv6 header, an HBH, and a medium access control (media access control, MAC) header (other contents may also be included, which will not be described herein). The HBH includes an option field therein.

Fig. 25 is a schematic diagram showing option fields in the message shown in fig. 24. As shown in fig. 25, the option field includes a type subfield, a length subfield, a reserved subfield, a service flag subfield, and four service subfields. The value in the traffic flag subfield is 00100111, and the traffic flag subfield includes 8 flag bits. In a specific embodiment, among the 8 flag bits, the service corresponding to the 3 rd flag bit arranged from the high position to the low position is a slice service, the service corresponding to the 6 th flag bit is an APN service, the service corresponding to the 7 th flag bit is a DetNet service, and the service corresponding to the 8 th flag bit is an IFIT service. In another embodiment, among the 8 flag bits, the service corresponding to the 1 st flag bit arranged from the low bit to the high bit is a slice service, the service corresponding to the 2 nd flag bit is an APN service, the service corresponding to the 3 rd flag bit is a DetNet service, and the service corresponding to the 6 th flag bit is an IFIT service. Of the four service subfields, the 1 st service subfield arranged in a direction from the service flag subfield to the service label subfield (for example, in a direction from the 1 st 32 bits to the option field), corresponds to a slice service, the 2 nd service subfield corresponds to an APN service, the 3 rd service subfield corresponds to a DetNet service, and the 4 th service subfield corresponds to an IFIT service. The service information (e.g., information 1) of the slice service is located in the 1 st service subfield, the service information (e.g., information 2) of the APN service is located in the 2 nd service subfield, the service information (e.g., information 3) of the DetNet service is located in the 3 rd service subfield, and the service information (e.g., information 4) of the IFIT service is located in the 4 th service subfield.

Referring to fig. 24, the network device 101 as the head node first generates a message including the option field shown in fig. 25, and then processes the message according to the option field. Specifically, the network device 101 determines, according to the value in the service label subfield, that the option field carries service information (information 1) of the slice service, service information (information 2) of the APN service, service information (information 3) of the DetNet service, and service information (information 4) of the IFIT service, and determines that the service information of the slice service is located in the 1 st service subfield, the service information of the APN service is located in the 2 nd service subfield, the service information of the DetNet service is located in the 3 rd service subfield, and the service information of the IFIT service is located in the 4 th service subfield. The network device 101 traverses the four service subfields according to the arrangement sequence of the four service subfields, and processes the message according to the service information carried in the four service subfields in sequence. First, the network device 101 traverses to the 1 st traffic subfield; if the network device 101 supports the slice service, the network device 101 processes the message according to the information 1 carried in the 1 st service subfield; if the network device 101 does not support slice traffic, the network device 101 skips the 1 st traffic subfield. Then, the network device 101 traverses to the 2 nd service subfield; if the network equipment 101 supports the APN service, the network equipment 101 processes the message according to the information 2 carried in the 2 nd service subfield; if the network device 101 does not support APN traffic, the network device 101 skips the 2 nd traffic subfield. Thereafter, network device 101 traverses to the 3 rd traffic subfield; if the network device 101 supports the DetNet service, the network device 101 processes the message according to the information 3 carried in the 3 rd service subfield; if network device 101 does not support DetNet traffic, network device 101 skips the 3 rd traffic subfield. Finally, the network device 101 traverses to the 4 th traffic subfield; if the network device 101 supports the IFIT service, the network device 101 processes the message according to the information 4 carried in the 4 th service subfield; if the network device 101 does not support the IFIT service, the network device 101 skips the 4 th service subfield, e.g., the network device 101 skips the option field.

After processing the packet, the network device 101 obtains a packet 1, where the packet 1 includes an HBH, and the HBH includes an option field as shown in fig. 25. Network device 101 may send message 1 to network device 102. Since the option field is located in the HBH, after network device 102 receives message 1, network device 102 processes message 1 according to the option field.

After processing the packet 1, the network device 102 obtains a packet 2, where the packet 2 includes an HBH, and the HBH includes an option field as shown in fig. 25. Network device 102 may send message 2 to network device 103. Since the option field is located in the HBH, after the network device 103 receives the message 2, the network device 103 processes the message 2 according to the option field.

After processing the packet 2, the network device 103 obtains a packet 3, where the packet 3 includes an HBH, and the HBH includes an option field as shown in fig. 25. Network device 103 may send message 3 to network device 104. Since the option field is located in the HBH, after the network device 104 receives the packet 3, the network device 104 processes the packet 3 according to the option field.

After processing the packet 3, the network device 104 obtains a packet 4, where the packet 4 includes an HBH, and the HBH includes an option field as shown in fig. 25. Network device 104 may send message 4 to network device 105. Since the option field is located in the HBH, after the network device 105 receives the message 4, the network device 105 processes the message 4 according to the option field.

After processing the message 4, the network device 105 obtains a message 5, where the message 5 includes an HBH, and the HBH includes an option field as shown in fig. 25. Network device 105 may send message 5 to network device 106. Since the option field is located in the HBH, after the network device 106 receives the message 5, the network device 106 processes the message 5 according to the option field.

The process of processing the corresponding message by the network device 102 to the network device 106 according to the option field is similar to the process of processing the message by the network device 101 according to the option field, and will not be described herein. The network device 106 may also remove the option field in the packet 5 as a tail node, which is not limited in the embodiment of the present application.

The foregoing is an introduction to the method embodiments of the present application. Embodiments of the apparatus of the present application are described below, which may be used to perform the methods of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments.

Referring to fig. 26, a schematic structural diagram of a service processing device 2600 according to an embodiment of the present application is shown. The service processing device 2600 is applied to a network device. For example, service processing apparatus 2600 is a network device or a functional component in the network device. The network device is, for example, the network device B in the above-described method embodiment. As shown in fig. 26, the service processing device 2600 includes a transceiver module 2610 and a processing module 2620.

The transceiver module 2610 is configured to receive a message including an option field, where the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service is different from the second service. The functional implementation of the transceiver module 2610 may refer to the relevant description in S303 or S2205 above.

The processing module 2620 is configured to process the message according to the first service information. The functional implementation of the processing module 2620 may refer to the relevant description in S304 or S2206 above.

In a specific embodiment, the option field includes a first subfield and a second subfield, where the first subfield carries the first service information, and the second subfield carries the second service information.

In a specific embodiment, the length of the first subfield is the same as the length of the second subfield.

In a specific embodiment, the option field further includes a third subfield, the third subfield carries third service information, the third service information corresponds to a third service, and the first service, the second service and the third service are different from each other; the first sub-field, the second sub-field and the third sub-field are sequentially arranged, and the length of the third sub-field is different from that of the first sub-field.

In a specific embodiment, the length of the third subfield is greater than the length of the first subfield.

In a specific embodiment, the length of the first subfield and the length of the second subfield are both 2 ⁿ Bit, n is an integer greater than or equal to 3.

In a specific embodiment, the option field further includes a fourth subfield, where the fourth subfield indicates a length of the first subfield and a length of the second subfield.

In a specific embodiment, the option field includes a service flag subfield, where the service flag subfield corresponds to m services, the m services are different from each other, the m services include a first service and a second service, the service flag subfield indicates that the option field carries first service information and second service information, and m is an integer greater than or equal to 2.

In a specific embodiment, the service flag subfield includes m flag bits, where the m flag bits correspond to m services one by one; a first flag bit in the m flag bits corresponds to a first service, a second flag bit corresponds to a second service, the first flag bit indicates that the option field carries first service information, and the second flag bit indicates that the option field carries second service information.

In a specific embodiment, the first flag bit and the second flag bit are arranged in sequence, and the first service information and the second service information are arranged in sequence, and the arrangement sequence of the first service information and the second service information corresponds to the arrangement sequence of the first flag bit and the second flag bit.

In a specific embodiment, the first service information is basic service information, the option field includes a service flag subfield, the service flag subfield corresponds to m services, the m services are different from each other, the m services include a second service, the service flag subfield indicates that the option field carries the second service information, and m is a positive integer.

In a specific embodiment, the first service is different from the m services.

In a specific embodiment, the service label subfield indicates that the option field carries service information of k services in the m services, where the service information of the k services is located after the basic service information.

In a specific embodiment, the sub-field carrying the basic service information in the option field is a basic sub-field, where the option field includes k service sub-fields corresponding to the k services one to one, and the k service sub-fields are located after the basic sub-field.

In a specific embodiment, the length of the basic subfield is a constant value.

In a specific embodiment, m is greater than or equal to 4.

In a specific embodiment, the option field further includes a reserved subfield, and the reserved subfield is adjacent to the service flag subfield.

In a specific embodiment, the lowest bit of the reserved subfield is adjacent to the highest bit of the traffic flag subfield.

In a specific embodiment, the option field further includes a type subfield and a length subfield, the type subfield indicates a type of the option field, and the length subfield indicates a length of the option field.

In a specific embodiment, the message is an IPv6 message, where the message includes an IPv6 extension header, and the IPv6 extension header includes the option field.

In a specific embodiment, the IPv6 extension header includes any one of HBH and DOH.

In a specific embodiment, the first service includes any one of a slice service, a flow detection service, an APN service and a DetNet service; alternatively, the second service includes any one of a slice service, a flow-following detection service, an APN service, and a DetNet service. The flow-following detection service may include an IFIT service or an IOAM service, among others.

In a specific embodiment, the first service includes a slice service, and the first service information includes a slice identifier.

In a specific embodiment, the first service includes a flow-following detection service, and the first service information includes a flow identifier.

In a specific embodiment, the first service includes an APN service, and the first service information includes at least one of a user group identifier and an application group identifier.

In a specific embodiment, the first service includes a DetNet service, and the first service information includes a path identifier.

In a specific embodiment, the network device supports a first service and a second service, and the processing module 2620 is further configured to process the packet according to the second service information. The functional implementation of the processing module 2620 may also refer to the relevant description in S305 a.

In a specific embodiment, the network device supports the first service but not the second service, and the processing module 2620 is further configured to skip the second service information. The functional implementation of the processing module 2620 may also refer to the relevant description in S305 b.

In a specific embodiment, the processing module 2620 is specifically configured to process the packet according to the first service information and the local configuration information associated with the first service. The functional implementation of the processing module 2620 may also refer to the relevant description in S304 above.

In a specific embodiment, the first service information and the second service information are arranged in sequence, and the processing module 2620 is specifically configured to process the packet according to the arrangement sequence of the first service information and the second service information.

In summary, in the service processing apparatus provided in the embodiment of the present application, since the service information of at least two different services can be carried in the same option field of the same packet, the overhead caused by some fixed contents and some optional subfields in the option field can be saved, which is helpful for reducing the packet overhead, further simplifying the complexity of processing the packet by the network device, and improving the forwarding performance of the network device.

Referring to fig. 27, a schematic structural diagram of another service processing apparatus 2700 according to an embodiment of the present application is shown. The service processing apparatus 2700 is applied to a network device. For example, the service processing apparatus 2700 is a network device or a functional component in the network device. The network device is, for example, the network device a in the above-described method embodiment. As shown in fig. 27, the service processing apparatus 2700 includes a processing module 2710 and a transceiver module 2720.

The processing module 2710 is configured to generate a message including an option field, where the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service is different from the second service. The functional implementation of the processing module 2710 may be described with reference to the above in S301 or S2203.

A transceiver module 2720, configured to send the packet. The functional implementation of the transceiver module 2720 may refer to the relevant description in S302 or S2204 above.

In a specific embodiment, the first service is different from the m services.

In a specific embodiment, the sub-field carrying the basic service information in the option field is a basic sub-field, and the option field includes k service sub-fields corresponding to k services one by one, where the k service sub-fields are located behind the basic sub-field.

In a specific embodiment, the length of the basic subfield is a constant value.

In a specific embodiment, m is greater than or equal to 4.

In a specific embodiment, the option field includes a type subfield and a length subfield, the type subfield indicates the type of the option field, and the length subfield indicates the length of the option field.

In a specific embodiment, the network device supports the first service, and the processing module 2710 is further configured to process the packet according to the first service information.

In a specific embodiment, the network device further supports a second service, and the processing module 2710 is further configured to process the packet according to second service information.

In a specific embodiment, the network device does not support the second service, and the processing module 2710 is further configured to skip the second service information.

In a specific embodiment, the processing module 2710 is specifically configured to process the packet according to the first service information and the local configuration information associated with the first service.

In a specific embodiment, the first service information and the second service information are arranged in sequence, and the processing module 2710 is specifically configured to process the packet according to the arrangement sequence of the first service information and the second service information.

In a specific embodiment, the transceiver module 2720 is further configured to receive indication information sent by the controller, where the indication information is used to instruct the network device to generate a message including the option field. The functional implementation of the transceiver module 2720 may be referred to the relevant description in S2202 above.

The processing module 2710 is specifically configured to generate a message including the option field according to the indication information.

Referring to fig. 28, a schematic structural diagram of still another service processing apparatus 2800 provided in an embodiment of the present application is shown. The service processing device 2800 is applied to a controller. For example, the service processing device 2800 is a controller or a functional component in the controller. As shown in fig. 28, the service processing apparatus 2800 includes a transceiver module 2810.

The transceiver module 2810 is configured to send indication information to the head node, where the indication information is used to instruct the head node to generate a message that includes an option field, where the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service is different from the second service. The functional implementation of transceiver module 2810 may be as described above in connection with S2201.

Optionally, the length of the first subfield and the length of the second subfield are both 2 ⁿ Bit, n is an integer greater than or equal to 3。

Optionally, the service flag subfield includes m flag bits, where the m flag bits correspond to m services one by one; a first flag bit in the m flag bits corresponds to a first service, a second flag bit corresponds to a second service, the first flag bit indicates that the option field carries first service information, and the second flag bit indicates that the option field carries second service information.

Optionally, the first service is different from the m services.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Optionally, the IPv6 extension header includes any one of HBH and DOH.

Optionally, the first service includes any one of a slice service, a stream-following detection service, an APN service and a DetNet service; alternatively, the second service includes any one of a slice service, a flow-following detection service, an APN service, and a DetNet service.

In summary, in the service processing device provided in the embodiment of the present application, since the same option field of the same packet can carry service information of at least two different services, the overhead caused by some fixed contents and some optional subfields in the option field can be saved, which is helpful for reducing the packet overhead.

Referring to fig. 29, a schematic structural diagram of yet another service processing apparatus 2900 provided in an embodiment of the present application is shown. The traffic processing apparatus 2900 is applied to the head node. For example, the traffic processing apparatus 2900 is a head node or a functional component in the head node. As shown in fig. 29, the service processing apparatus 2900 includes a transceiver module 2910 and a processing module 2920.

The transceiver module 2910 is configured to receive indication information sent by the controller, where the indication information is used to instruct the head node to generate a message including an option field, where the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service is different from the second service. The functional implementation of transceiver module 2910 may be as described above in connection with S2202.

Processing module 2920 is configured to generate a message including the option field according to the indication information.

Optionally, the first service is different from the m services.

Optionally, the length of the basic subfield is a constant value.

Alternatively, m is greater than or equal to 4.

Optionally, the indication information is used to instruct the head node to generate an IPv6 packet including an IPv6 extension header, where the IPv6 extension header includes the option field, and the processing module 2920 is used to generate, according to the indication information, the IPv6 packet including the IPv6 extension header.

Optionally, the IPv6 extension header includes any one of HBH and DOH.

It should be understood that the service processing apparatus provided in the embodiments of the present application may also be implemented as an application-specific integrated circuit (ASIC-specific integrated circuit) or as a programmable logic device (programmable logic device, PLD). The PLD may be a complex program logic device (complex programmable logical device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), general-purpose array logic (generic array logic, GAL), or any combination thereof. The service processing method provided by the method embodiment may also be implemented by software, and when the service processing method provided by the method embodiment is implemented by software, each module in the service processing apparatus may also be a software module.

Referring to fig. 30, a schematic structural diagram of yet another service processing apparatus 3000 according to an embodiment of the present application is shown. The service processing apparatus 3000 may be a network device or a functional component in the network device. The network device may be network device a, network device B or a head node in the above-described method embodiments.

As shown in fig. 30, the service processing apparatus 3000 includes: a main control board 3010, an interface board 3030, and an interface board 3040. The plurality of interface boards may in case comprise a switching network board (not shown in fig. 30) for performing data exchange between the interface boards (interface boards also called line cards or service boards).

The main control board 3010 is used for completing functions such as system management, equipment maintenance, protocol processing, and the like. The interface board 3030 and the interface board 3040 are used to provide various service interfaces (e.g., POS interface, GE interface, ATM interface, etc.) and to implement message forwarding. The main control board 3010 mainly has 3 kinds of functional units: the system comprises a system management control unit, a system clock unit and a system maintenance unit. The main control board 3010, the interface board 3030 and the interface board 3040 are connected to the system back board by a system bus to realize intercommunication. The interface board 3030 includes one or more processors 3031 thereon. The processor 3031 is used for controlling and managing the interface board 3030 and communicating with the central processor 3012 on the main control board 3010. A memory 3032 on the interface board 3030 is used to store forwarding tables, local configuration information about the traffic, etc. If the service processing apparatus 3000 is the aforementioned network device a, the memory 3032 is further configured to store an option field or configuration information of the option field, the processor 3031 is configured to generate a message including the option field, and the processor 3031 is configured to process the message according to the option field. If the service processing apparatus 3000 is the aforementioned network device B, the processor 3031 processes the message according to the option field in the message. As shown in fig. 30, the main control board 3010 may include a memory 3014, and the memory 3014 on the main control board 3010 may also be used to store local configuration information about services, option fields, or configuration information of the option fields, etc., which is not limited in this embodiment of the present application. The interface board 3030 includes one or more network interfaces 3033 for receiving and transmitting messages, which the processor 3031 processes according to option fields in the messages received by the network interfaces 3033. The specific implementation process is not repeated here one by one. The specific functions of the processor 3031 are also not described in detail herein.

As shown in fig. 30, this embodiment includes a plurality of interface boards, and uses a distributed forwarding mechanism, where the operation on the interface board 3040 is substantially similar to the operation of the interface board 3030. For example, the interface board 3040 includes one or more network interfaces 3043 for receiving and transmitting messages, a memory 3042 for storing forwarding tables, local configuration information about traffic, etc., and a processor 3041 for controlling and managing the interface board 3040 and communicating with the central processor 3012 on the main control board 3010. For brevity, the interface board 3040 will not be described in detail herein.

It should be understood that the processor 3031 in the interface board 3030 and/or the processor 3041 in the interface board 3040 in fig. 30 may be dedicated hardware or a chip, such as a network processor or an application-specific integrated circuit, to implement the above-described functions, i.e., a so-called forwarding plane that uses dedicated hardware or a chip for processing. In other embodiments, the processor 3031 in the interface board 3030 and/or the processor 3041 in the interface board 3040 may also employ a general-purpose processor, such as a general-purpose central processing unit (central processing unit, CPU), to implement the functions described above.

In addition, it should be noted that the master control board may have one or more pieces, and the master control board may include a main master control board and a standby master control board when there are more pieces. The interface boards may have one or more, the more data processing capabilities the network device is, the more interface boards are provided. Under the condition of a plurality of interface boards, the interface boards can communicate through one or a plurality of exchange network boards, and load sharing redundancy backup can be realized jointly when a plurality of interface boards exist. Under the centralized forwarding architecture, the network device does not need a switching network board, and the interface board bears the processing function of the service data of the whole system. Under the distributed forwarding architecture, the network device comprises a plurality of interface boards, and data exchange among the plurality of interface boards can be realized through a switching network board, so that high-capacity data exchange and processing capacity are provided. Therefore, the data access and processing power of the network devices of the distributed architecture is greater than that of the devices of the centralized architecture. Which architecture is specifically adopted depends on the networking deployment scenario, and no limitation is made here.

In particular embodiments, memory 3032 and/or Memory 3042 may be, but is not limited to, read-only Memory (ROM) or other type of static storage device that may store static information and instructions, random access Memory (random access Memory, RAM) or other type of dynamic storage device that may store information and instructions, but may also be, but is not limited to, electrically erasable programmable read-only Memory (EEPROM), compact disc-read-only Memory (compact disc read-only Memory, CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 3032 may be separate and coupled to the processor 3031 by a communication bus or may be integral to the processor 3031. The memory 3042 may be provided separately, and may be connected to the processor 3041 via a communication bus, or may be integrated with the processor 3041.

The memory 3032 is used for storing program codes and is controlled to be executed by the processor 3031 to perform part or all of the steps of the service processing method provided in the above embodiment. The processor 3031 is used to execute program code stored in the memory 3032. One or more software modules may be included in the program code. The one or more software modules may be the functional modules provided in the embodiments shown in fig. 14 or fig. 15 described above. The memory 3042 may also be used for storing program codes and is controlled to be executed by the processor 3041 to perform part or all of the steps of the service processing method provided in the above embodiment. Similarly, the memory 3014 may also be used to store program codes and be controlled by the central processor 3012 to perform part or all of the steps of the service processing method provided in the above embodiment.

In particular embodiments, network interface 3033, network interface 3043 may be a device using any transceiver or the like for communicating with other devices or communication networks, such as ethernet, radio access network (radio access network, RAN), wireless local area network (wireless local area networks, WLAN), etc.

Referring to fig. 31, a schematic structural diagram of yet another service processing apparatus 3100 according to an embodiment of the present application is shown. The traffic processing device 3100 may be a controller. Referring to fig. 31, the service processing apparatus 3100 includes: a processor 3102, memory 3104, a communication interface 3106, and a bus 3108. The processor 3102, memory 3104, and communication interface 3106 are communicatively coupled to each other via a bus 3108. The connections between the processor 3102, the memory 3104, and the communication interface 3106 shown in fig. 31 are merely exemplary, and the processor 3102, the memory 3104, and the communication interface 3106 may be communicatively connected to each other using other connections than a bus 3108.

The memory 3104 may be used to store a computer program 31042, and the computer program 31042 may include program code. The memory 3104 may be various types of storage media such as RAM, ROM, nonvolatile RAM (NVRAM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (electrically erasable PROM, EEPROM), flash memory, optical memory, registers, and the like.

The processor 3102 may be a general-purpose processor or a special-purpose processor. A general-purpose processor may be a processor that performs certain steps and/or operations by reading and executing a computer program (e.g., computer program 31042) stored in a memory (e.g., memory 3104), which may be used in performing the steps and/or operations. A general purpose processor may be, for example, but is not limited to, a CPU. The special purpose processor may be a specially designed processor for performing the specific steps and/or operations, such as, but not limited to, a digital signal processor (digital signal processor, DSP), ASIC, FPGA, etc. Furthermore, the processor 3102 may also be a combination of multiple processors, such as a multi-core processor. The processor 3102 may include at least one circuit to perform all or part of the steps of the above-described embodiments to provide a business processing method.

The communication interface 3106 may include an input/output (I/O) interface, a physical interface, a logical interface, and the like for realizing interconnection of devices inside the service processing apparatus 3100, and an interface for realizing interconnection of the service processing apparatus 3100 with other communication apparatuses. The physical interface may be a Gigabit Ethernet (GE) interface, which may be used to implement the interconnection of the traffic processing device 3100 with other communication devices. The logical interface is an interface inside the service processing apparatus 3100, which may be used to implement device interconnection inside the service processing apparatus 3100. It is to be readily understood that the communication interface 3106 may be used for transmitting and receiving information between the service processing device 3100 and other communication devices, and that the communication interface 3106 may implement the functions associated with the transceiver module 2810 described above. In addition, the communication interface 3106 may further include a transceiver for receiving and transmitting information, which may also implement the functions associated with the transceiver module 2810.

Where bus 3108 may be any type of communication bus, such as a system bus, that interconnects processor 3102, memory 3104, and communication interface 3106.

The above devices may be provided on separate chips, or may be provided at least partially or entirely on the same chip. Whether the individual devices are independently disposed on different chips or integrally disposed on one or more chips is often dependent on the needs of the product design. The embodiment of the application does not limit the specific implementation form of the device.

The service processing device 3100 shown in fig. 31 is merely exemplary, and in implementation, the service processing device 3100 may further include other components, which are not listed herein. The service processing apparatus 3100 shown in fig. 31 may perform service processing by performing all or part of the steps of the service processing method provided by the above-described embodiment.

Referring to fig. 32, a schematic structural diagram of a service processing system 3200 according to an embodiment of the present application is shown. The traffic handling system 3200 includes a first network device 3210 and a second network device 3220.

The first network device 3210 is configured to generate a message including an option field, where the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service is different from the second service, and send the message to the second network device 3220.

The second network device 3220 is configured to receive the message and process the message according to the first service information.

In a specific embodiment, the service processing system 3200 further includes: the controller 3230 is configured to send indication information to the first network device 3210, where the indication information is configured to instruct the first network device 3210 to generate a message including an option field.

The first network device 3210 is specifically configured to generate a message including the option field according to the indication information.

In a specific embodiment, the first network device 3210 supports a first service, and the first network device 3210 is further configured to process the packet according to the first service information.

In a specific embodiment, the first network device 3210 further supports a second service, and the first network device 3210 is further configured to process the packet according to the second service information.

In a specific embodiment, the first network device 3210 does not support the second service, and the first network device 3210 is further configured to skip the second service information.

In a specific embodiment, the first network device 3210 is specifically configured to process the packet according to the first service information and local configuration information of the first network device.

In a specific embodiment, the first service information and the second service information are arranged in sequence, and the first network device 3210 is specifically configured to process the packet according to the arrangement sequence of the first service information and the second service information.

In a specific embodiment, the second network device 3220 supports the first service and the second service, and the second network device 3220 is further configured to process the packet according to the second service information.

In a specific embodiment, the second network device 3220 supports the first service but does not support the second service, and the second network device 3220 is further configured to skip the second service information.

In a specific embodiment, the second network device 3220 is specifically configured to process the packet according to the first service information and the local configuration information of the first network device.

In a specific embodiment, the first service information and the second service information are arranged in sequence, and the second network device 3220 is specifically configured to process the packet according to the arrangement sequence of the first service information and the second service information.

In a specific embodiment, the first network device 3210 is a head node on a forwarding path of the packet, and the second network device 3220 is an intermediate node or a tail node on the forwarding path. The service processing apparatus provided in fig. 27 or fig. 30 may be used as the head node; the service processing apparatus provided in fig. 26 or fig. 30 may be used as the intermediate node or the tail node; the service processing apparatus provided in fig. 28 or 31 may be the controller 3230.

In a specific embodiment, the first network device 3210 is a head node or an intermediate node on a forwarding path of the packet, and the second network device 3220 is a tail node on the forwarding path. The service processing apparatus provided in fig. 27 or fig. 30 may be used as the head node or the intermediate node; the service processing device provided in fig. 26 or fig. 30 may be used as the tail node; the service processing apparatus provided in fig. 28 or 31 may be used as the controller 3230.

In a specific embodiment, the service processing apparatus provided in fig. 29 may be used as the head node.

The present embodiments provide a data structure that includes the option fields provided by the above embodiments of the present application. For the description of the option field, please refer to the related description in the above embodiment of the present application, and the description is omitted here.

For example, the option field may be an option field as shown in any one of fig. 14 to 17.

In a specific embodiment, the option field may be an option field as shown in fig. 25.

The present application provides a computer readable storage medium having stored therein a computer program which, when executed (e.g., by a service processing apparatus, a network device, a controller, one or more processors, etc.), implements all or part of the steps of the service processing method provided by the method embodiments described above.

The present embodiments provide a computer program product comprising a program or code which, when executed (e.g. by a service processing apparatus, a network device, a controller, one or more processors, etc.), implements all or part of the steps of the service processing method provided by the method embodiments described above.

The embodiments of the present application provide a chip, where the chip includes programmable logic circuits and/or program instructions, and the chip is used in operation to implement all or part of the steps of the service processing method provided in the foregoing method embodiments.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be embodied in whole or in part in the form of a computer program product comprising one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a network of computers, or other programmable devices. The computer instructions may be stored in or transmitted from one computer readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means from one website, computer, server, or data center. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the available medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium, or a semiconductor medium (e.g., solid state disk), etc.

It should be understood that "at least one" in this application means one or more, and "a plurality" means two or more. "at least two" means two or more, and in this application, the symbol "/" means or unless otherwise indicated, for example, A/B may mean A or B. The term "and/or" in this application is merely an association relation describing an associated object, meaning that three relations may exist, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, for purposes of clarity of description, the words "first," "second," "third," "fourth," and the like are used herein to distinguish between identical or similar items that have substantially the same function or effect. Those skilled in the art will appreciate that words such as "first," "second," "third," "fourth," etc. do not limit the number and order of execution.

Different types of embodiments, such as a method embodiment and a device embodiment, provided in the embodiments of the present application may be mutually referred to, and the embodiments of the present application are not limited to this. The sequence of the operations of the method embodiment provided in the embodiment of the present application can be properly adjusted, the operations can also be increased or decreased according to the situation, and any method that is easily conceivable to be changed by a person skilled in the art within the technical scope of the present application is covered in the protection scope of the present application, so that no further description is provided.

In the corresponding embodiments provided in the present application, the disclosed apparatus and the like may be implemented by other structural manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules is merely a logical function division, and there may be additional divisions of actual implementation, e.g., multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical or other forms.

The modules illustrated as separate components may or may not be physically separate, and the components described as modules may or may not be physical units, may be located in one place, or may be distributed over multiple devices (e.g., network devices). Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

The foregoing is merely illustrative embodiments of the present application, and the scope of the present application is not limited thereto, and any equivalent modifications or substitutions will be apparent to those skilled in the art within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of service processing, the method comprising:

the method comprises the steps that network equipment receives a message comprising an option field, wherein the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different;

and the network equipment processes the message according to the first service information.

2. A method of service processing, the method comprising:

the method comprises the steps that network equipment generates a message comprising an option field, wherein the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service and the second service are different;

and the network equipment sends the message.

3. A method according to claim 1 or 2, characterized in that,

the option field comprises a first sub-field and a second sub-field, the first sub-field carries the first service information, and the second sub-field carries the second service information.

4. The method of claim 3, wherein the step of,

The length of the first subfield is the same as the length of the second subfield.

5. The method of claim 4, wherein the step of determining the position of the first electrode is performed,

the option field further comprises a third sub-field, third service information is carried in the third sub-field, the third service information corresponds to a third service, and the first service, the second service and the third service are different from each other;

the first sub-field, the second sub-field and the third sub-field are sequentially arranged, and the length of the third sub-field is different from that of the first sub-field.

6. The method of claim 5, wherein the step of determining the position of the probe is performed,

the length of the third subfield is greater than the length of the first subfield.

7. The method according to any one of claim 3 to 6, wherein,

the length of the first sub-field and the length of the second sub-field are both 2 ⁿ Bit, n is an integer greater than or equal to 3.

8. The method according to any one of claim 3 to 7, wherein,

the option field further comprises a fourth sub-field, wherein the fourth sub-field indicates the length of the first sub-field and the length of the second sub-field.

9. The method according to any one of claim 1 to 8, wherein,

the option field comprises a service sign subfield, the service sign subfield corresponds to m services, the m services are different from each other, the m services comprise the first service and the second service, the service sign subfield indicates that the option field carries the first service information and the second service information, and m is an integer greater than or equal to 2.

10. The method of claim 9, wherein the step of determining the position of the substrate comprises,

the service sign sub-field comprises m sign bits, and the m sign bits are in one-to-one correspondence with the m services;

a first flag bit in the m flag bits corresponds to the first service, a second flag bit in the m flag bits corresponds to the second service, the first flag bit indicates that the option field carries the first service information, and the second flag bit indicates that the option field carries the second service information.

11. The method of claim 10, wherein the step of determining the position of the first electrode is performed,

the first flag bit and the second flag bit are arranged in sequence, the first service information and the second service information are arranged in sequence, and the arrangement sequence of the first service information and the second service information corresponds to the arrangement sequence of the first flag bit and the second flag bit.

12. The method according to any one of claim 1 to 8, wherein,

the first service information is basic service information, the option field comprises a service mark subfield, the service mark subfield corresponds to m services, the m services are different from each other, the m services comprise the second service, the service mark subfield indicates that the option field carries the second service information, and m is a positive integer.

13. The method according to any one of claims 9 to 12, wherein m is ≡4.

14. The method according to any one of claims 9 to 13, wherein,

the option field also comprises a reserved subfield, and the reserved subfield is adjacent to the service sign subfield.

15. The method according to any one of claims 1 to 14, wherein,

the message is an internet protocol version 6 IPv6 message, the message comprises an IPv6 extension head, and the IPv6 extension head comprises the option field.

16. The method of claim 15, wherein the step of determining the position of the probe is performed,

the IPv6 extension header comprises any one of a hop-by-hop header HBH and a destination option header DOH.

17. The method according to any one of claims 1 to 16, wherein,

The first service comprises any one of a slice service, a stream following detection service, an application aware network APN service and a deterministic network DetNet service; or alternatively, the process may be performed,

the second service includes any one of a slice service, a flow-following detection service, an APN service, and a DetNet service.

18. The method according to any one of claims 1 to 16, wherein,

the first service includes a slice service, and the first service information includes a slice identifier.

19. The method according to any one of claims 1 to 16, wherein,

the first service includes a flow-following detection service, and the first service information includes a flow identifier.

20. The method according to any one of claims 1 to 16, wherein,

the first service includes an application aware network APN service, and the first service information includes at least one of a user group identity and an application group identity.

21. The method according to any one of claims 1 to 16, wherein,

the first traffic comprises deterministic network DetNet traffic and the first traffic information comprises path identification.

22. The method according to any one of claims 1 to 21, wherein,

The network device supports the first service and the second service, the method further comprising:

and the network equipment processes the message according to the second service information.

23. The method according to any one of claims 1 to 21, wherein,

the network device supporting the first service but not the second service, the method further comprising:

the network device skips the second service information.

24. The method according to any one of claims 1, 3 to 23, wherein,

the network device processes the message according to the first service information, and the message comprises at least one of the following:

the network equipment counts the message according to the first service information;

and the network equipment forwards the message according to the first service information.

25. The method according to any one of claims 1, 3 to 24, wherein,

the network device processes the message according to the first service information, including: and the network equipment processes the message according to the first service information and the local configuration information associated with the first service.

26. The method according to any one of claims 2 to 23, further comprising:

The network equipment receives indication information sent by a controller, wherein the indication information is used for indicating the network equipment to generate a message comprising the option field;

the network device generates a message including an option field, including: and the network equipment generates the message comprising the option field according to the indication information.

27. A service processing apparatus, comprising: a transceiver module and a processing module;

the transceiver module is configured to perform the transceiving operations in the method according to any of claims 1 to 26, and the processing module is configured to perform operations in the method according to any of claims 1 to 26 other than the transceiving operations.

28. A service processing apparatus, comprising: a memory and a processor;

the memory is used for storing a computer program;

the processor is configured to execute the computer program stored in the memory to cause the traffic processing device to perform the method of any one of claims 1 to 26.

29. A service processing system, comprising a first network device and a second network device;

the first network device is configured to generate a message including an option field, and send the message to the second network device, where the option field carries first service information and second service information, the first service information corresponds to a first service, the second service information corresponds to a second service, and the first service is different from the second service;

The second network device is configured to receive the packet and process the packet according to the first service information.

30. The system of claim 29, wherein the system further comprises: a controller;

the controller is configured to send indication information to the first network device, where the indication information is used to instruct the first network device to generate a packet including the option field;

the first network device is configured to generate the packet including the option field according to the indication information.

31. The system of claim 29 or 30, wherein the system comprises a plurality of sensors,

the first network device is a head node on a forwarding path of the message;

the second network device is an intermediate node or a tail node on the forwarding path.

32. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a computer program which, when executed, implements the method of any of claims 1 to 26.

33. A computer program product, characterized in that it comprises a program or code which, when executed, implements the method according to any of claims 1 to 26.