CN105991437B

CN105991437B - Message forwarding processing method and device, controller and route forwarding equipment

Info

Publication number: CN105991437B
Application number: CN201510085557.4A
Authority: CN
Inventors: 祝沈财; 廖婷
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2015-02-16
Filing date: 2015-02-16
Publication date: 2020-05-15
Anticipated expiration: 2035-02-16
Also published as: CN105991437A; WO2016131225A1

Abstract

The invention discloses a message forwarding processing method, a device, a controller and a route forwarding device, wherein the method comprises the following steps: acquiring label splicing capability information used for identifying whether one or more routing forwarding devices support label splicing, and/or path identification capability information used for identifying whether one or more routing forwarding devices support path identification; the invention solves the problem that whether the splicing and/or path identification functions of SR LIST are supported or not can not be known between related devices for forwarding the message in related technologies, so that the message can not be effectively forwarded, further achieves the effect of informing whether the capability information of label splicing and/or path identification is supported or not between the devices, and further achieves the effect of forwarding the message.

Description

Message forwarding processing method and device, controller and route forwarding equipment

Technical Field

The present invention relates to the field of communications, and in particular, to a method, an apparatus, a controller, and a route forwarding device for packet forwarding processing.

Background

Segment Routing (Segment Routing) is a Routing method based on a source address, a layer of node information influencing the forwarding of the existing shortest path is superposed outside a data message and carried outside the data message, and the message carries out shortest path forwarding according to the node information of the specified path. Fig. 1 is a schematic diagram of a main packet format of segment routing in the related art, and as shown in fig. 1, when a packet including a segment routing packet header is transmitted in an SR network domain, a network device (generally, a router) performs corresponding operations according to segment operation instructions in the segment routing packet header, where the operation instructions include Push, Next, and Continue, through specified SR node path information carried in the segment routing header. When the operation instruction is Push operation, the network device presses an SRHeader (segment routing message header) into the IP message, or adds other segment instructions in the segment routing message header; the Next and Continue operations indicate through the pointer of Ptr, when judging that the operation of the current segment has been finished, the pointer moves to the Next segment, and the segment pointed by the pointer indicates that the segment is an active segment for forwarding the Next hop; the Continue operation is that the segment operation has not ended and the pointer remains on the current segment. By means of the SR appointed path forwarding function, the load balance and flow engineering of the network and complex network functions such as fast rerouting and the like can be achieved very conveniently. The segment Operation instruction may also be extended to implement a service-based or topology-based routing instruction, and then the segment routing may also implement service-based network virtualization and application in the aspects of Operation, Administration, management, and Maintenance (OAM).

The Segment Routing technology makes full use of a Multi-Protocol label switching (MPLS) encapsulation technology in the related art, a packet Header of an MPLS network or an IPv6 packet Header in the related art carries a Segment Routing Header (Segment Routing Header), fig. 2 is a schematic format diagram of an MPLS packet in the related art, and as shown in fig. 2, the MPLS packet Header has 32bits (4 bytes), where a 20-bit label field and a 3-bit TC field are used for indicating the priority of the packet. The stack bottom mark of 1bit is used for nesting operation of MPLS, and the TTL field of 8bits is used for TTL counting in the MPLS network. The segment routing technology can be completely compatible and inherit the existing MPLS forwarding data plane, and the forwarding of the segment routing can be realized without modifying the message header of the MPLS.

In MPLS data encapsulation, the segment list in SR Header is described by means of label stack: wherein SRPtr points to a currently executing segment (active segment) corresponding to a top-level label in the MPLS label stack; continue operation defined for SR Header in SR corresponds to label SWAP operation in MPLS; performing SWAP operation of an incoming label and an outgoing label carrying the same label value through a local SR forwarding table; the Next operation defined for SR Header in SR corresponds to the label POP operation in MPLS; i.e. pop-up of top-level labels; the PUSH operation defined for SR Header in SR corresponds to the PUSH operation in MPLS, i.e. pushing the label. However, if the stack depth exceeds the processing capability of the forwarding device, SR LIST cannot be established, and one feasible solution is SR LIST splicing or path identification.

However, in the related art, it is not known among the related devices that forward the packet whether to support the concatenation and/or path identification functions of SRLIST, so that the packet cannot be forwarded effectively.

Disclosure of Invention

The invention provides a message forwarding processing method, a message forwarding processing device, a controller and routing forwarding equipment, which are used for at least solving the problem that whether the splicing and/or path identification functions of SRLIST are supported or not can not be known among related equipment for forwarding a message in related technologies, so that the message cannot be effectively forwarded.

According to an aspect of the present invention, a method for forwarding a packet is provided, including: acquiring label splicing capability information used for identifying whether one or more routing forwarding devices support label splicing, and/or path identification capability information used for identifying whether one or more routing forwarding devices support path identification; and issuing a forwarding strategy for forwarding the message to be forwarded to the one or more routing forwarding devices according to the acquired label splicing capability information and/or the acquired path identification capability information.

Preferably, issuing the forwarding policy for forwarding the packet to be forwarded to the one or more routing forwarding devices according to the acquired tag splicing capability information and/or the path identification capability information includes: determining a splicing node for the message to be forwarded from the one or more routing forwarding devices according to the label splicing capability information, and/or determining an identification node for the message to be forwarded from the one or more routing forwarding devices according to the path identification capability information; and issuing a splicing label to the determined splicing node and/or issuing an identification label to the determined identification node, wherein the splicing label is used for indicating the splicing node to splice and package the message and then forward the message, and the identification label is used for indicating the identification node to forward the message according to the path identified by the identification label.

Preferably, determining the splicing node for the packet to be forwarded from the one or more routing forwarding devices according to the label splicing capability information, and/or determining the identification node for the packet to be forwarded from the one or more routing forwarding devices according to the path identification capability information includes: selecting a standby splicing node and/or a standby identification node for the message to be forwarded according to the stack processing capacity of the one or more routing forwarding devices; judging whether the standby splicing node supports label splicing or not and/or whether the standby identification node supports path identification or not according to the label splicing capacity information; and if so, determining the standby splicing node as the splicing node and/or the standby identification node as the identification node.

Preferably, the issuing the splicing label to the determined splicing node and/or the issuing the identification label to the determined identification node includes: and issuing the splicing label to the determined splicing node and/or issuing the identification label to the determined identification node in a mode of carrying the splicing label and/or the identification label at the corresponding position of the SR-ERO expansion sub-object.

Preferably, the label splicing capability information for identifying whether the one or more routing forwarding devices support label splicing, and/or the path identification capability information for identifying whether the one or more routing forwarding devices support path identification is obtained by: and acquiring the label splicing capability information and/or the path identification capability information by acquiring a field value corresponding to an extension field in a type length value TLV attribute of the segment routing SR capability, wherein the field value is used for identifying whether the one or more routing forwarding devices support label splicing and/or identifying whether the one or more routing forwarding devices support path identification.

According to another aspect of the present invention, a method for forwarding a packet is provided, including: acquiring label splicing capacity information for identifying whether a controller supports label splicing and/or path identification capacity information for identifying whether the controller supports path identification; and forwarding the message to be forwarded according to the acquired label splicing capability information and/or the path identification capability information and a forwarding strategy issued by the controller.

Preferably, the forwarding the packet to be forwarded according to the acquired tag splicing capability information and/or the path identifier capability information and the forwarding policy issued by the controller includes: receiving a splicing label and/or an identification label issued by the controller; and performing forwarding processing after the message to be forwarded is spliced and encapsulated according to the splicing label, and/or performing forwarding processing on the message to be forwarded according to the path marked by the identification label.

Preferably, the receiving the splicing label and/or the identification label issued by the controller by the following method includes: and receiving the splicing label and/or the identification label sent by the controller in a mode of carrying the splicing label and/or the identification label at the corresponding position of the SR-ERO expansion sub-object.

Preferably, the tag splicing capability information for identifying whether the controller supports tag splicing and/or the path identification capability information for identifying whether the controller supports path identification is acquired by: and acquiring the label splicing capability information and/or the path identification capability information by acquiring a field value corresponding to an extension field in a type length value TLV attribute of the segment routing SR capability, wherein the field value is used for identifying whether the controller supports label splicing and/or identifying whether the controller supports path identification.

According to an aspect of the present invention, there is provided a packet forwarding processing apparatus, including: a first obtaining module, configured to obtain label splicing capability information used for identifying whether one or more routing forwarding devices support label splicing, and/or path identification capability information used for identifying whether one or more routing forwarding devices support path identification; and the issuing module is used for issuing a forwarding strategy for forwarding the message to be forwarded to the one or more routing forwarding devices according to the acquired label splicing capability information and/or the acquired path identification capability information.

Preferably, the issuing module includes: a determining unit, configured to determine a splicing node for the packet to be forwarded from the one or more routing forwarding devices according to the tag splicing capability information, and/or determine an identification node for the packet to be forwarded from the one or more routing forwarding devices according to the path identification capability information; and the issuing unit is used for issuing a splicing label to the determined splicing node and/or issuing an identification label to the determined identification node, wherein the splicing label is used for indicating the splicing node to splice and encapsulate the message and then forward the message, and the identification label is used for indicating the identification node to forward the message according to the path identified by the identification label.

Preferably, the determination unit includes: a selecting subunit, configured to select a standby concatenation node and/or a standby identifier node for the packet to be forwarded according to the stack processing capability of the one or more routing forwarding devices; a judging subunit, configured to judge, according to the tag splicing capability information, whether the standby splicing node supports tag splicing, and/or whether the standby identification node supports path identification; and the determining subunit is configured to determine, if the determination result is yes, that the standby splicing node is the splicing node, and/or that the standby identification node is the identification node.

Preferably, the issuing unit is further configured to issue the splicing label to the determined splicing node and/or issue the identification label to the determined identification node in a manner that the splicing label and/or the identification label are carried at a position corresponding to an extended sub-object of the SR-ERO.

Preferably, the first obtaining module is further configured to obtain the tag splicing capability information and/or the path identification capability information by obtaining a field value corresponding to an extension field in a type length value TLV attribute of a segment routing SR capability, where the field value is used to identify whether the one or more routing forwarding devices support tag splicing, and/or is used to identify whether the one or more routing forwarding devices support path identification.

According to another aspect of the present invention there is provided a controller comprising the apparatus of any one of the above.

According to an aspect of the present invention, there is provided a packet forwarding processing apparatus, including: a second obtaining module, configured to obtain tag splicing capability information used for identifying whether a controller supports tag splicing, and/or path identification capability information used for identifying whether the controller supports path identification; and the processing module is used for forwarding the message to be forwarded according to the acquired label splicing capability information and/or the path identification capability information and the forwarding strategy issued by the controller.

Preferably, the processing module comprises: the receiving unit is used for receiving the splicing label and/or the identification label sent by the controller; and the processing unit is used for carrying out forwarding processing after splicing and packaging the message to be forwarded according to the splicing label, and/or carrying out forwarding processing on the message to be forwarded according to the path marked by the identification label.

Preferably, the receiving unit is further configured to receive the splicing label and/or the identification label sent by the controller in a manner that the splicing label and/or the identification label is carried at a position corresponding to an extended sub-object of the SR-ERO.

Preferably, the second obtaining module is further configured to obtain the tag splicing capability information and/or the path identification capability information by obtaining a field value corresponding to an extension field in a type length value TLV attribute of segment routing SR capability, where the field value is used to identify whether the controller supports tag splicing and/or identify whether the controller supports path identification.

According to another aspect of the present invention, there is provided a route forwarding device, including any one of the above-mentioned apparatuses.

According to the invention, label splicing capability information used for identifying whether one or more routing forwarding devices support label splicing and/or path identification capability information used for identifying whether one or more routing forwarding devices support path identification is obtained; and issuing a forwarding strategy for forwarding the message to be forwarded to the one or more routing forwarding devices according to the acquired label splicing capability information and/or the acquired path identification capability information, so that the problem that whether the splicing and/or path identification functions of SR LIST are supported or not cannot be known between related devices for forwarding the message in the related technology, and the message cannot be effectively forwarded is solved, and the capability information of whether the label splicing and/or path identification is supported or not can be notified between the devices, so that the effect of forwarding the message is achieved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a diagram illustrating a main message format of a segment route in the related art;

fig. 2 is a schematic diagram of a format of an MPLS packet in the related art;

fig. 3 is a flowchart of a first message forwarding processing method according to an embodiment of the present invention;

fig. 4 is a flowchart of a second message forwarding processing method according to the embodiment of the present invention;

fig. 5 is a block diagram of a first packet forwarding processing apparatus according to an embodiment of the present invention;

fig. 6 is a block diagram of an optimal structure of the down-sending module 54 in the first message forwarding processing apparatus according to the embodiment of the present invention;

fig. 7 is a block diagram of an optimal structure of the determination unit 62 in the down-sending module 54 in the first message forwarding processing apparatus according to the embodiment of the present invention;

FIG. 8 is a block diagram of a controller according to an embodiment of the present invention;

fig. 9 is a block diagram of a preferred structure of a second message forwarding processing apparatus according to an embodiment of the present invention;

fig. 10 is a block diagram of a preferred structure of the processing module 94 in the second message forwarding processing apparatus according to the embodiment of the present invention;

fig. 11 is a block diagram of the structure of a route forwarding apparatus according to an embodiment of the present invention;

fig. 12 is a schematic diagram of a network architecture for performing label splicing and/or path identification according to an embodiment of the present invention;

FIG. 13 is a diagram illustrating a label forwarding table format for label concatenation according to an embodiment of the present invention;

fig. 14 is a message format diagram of an SR capability TLV advertisement concatenation capability and/or path identification capability according to the preferred embodiment of the present invention;

fig. 15 is a message format diagram of SR-ERO advertisement concatenation and path identification SID according to the preferred embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

In this embodiment, a method for forwarding a packet is provided, and fig. 3 is a flowchart of a first method for forwarding a packet according to an embodiment of the present invention, and as shown in fig. 3, the flowchart includes the following steps:

step S302, obtaining label splicing capability information for identifying whether one or more route forwarding devices support label splicing, and/or path identification capability information for identifying whether one or more route forwarding devices support path identification;

step S304, according to the acquired label splicing ability information and/or path identification ability information, a forwarding strategy for forwarding the message to be forwarded is issued to one or more routing forwarding devices.

Through the steps, the controller issues the forwarding strategy for forwarding the message to the route forwarding equipment by acquiring the label splicing capability information of whether the route forwarding equipment supports label splicing and/or the path identification capability information of whether the route forwarding equipment supports the path identification, so that the problem that whether the splicing and/or path identification functions of the SRLIST are supported cannot be known between the relevant equipment for forwarding the message in the related technology, and the message cannot be effectively forwarded is solved, and the capability information of whether the label splicing and/or path identification is supported can be notified between the equipment, so that the effect of forwarding the message is achieved.

When a forwarding policy for forwarding a message to be forwarded is issued to one or more routing forwarding devices according to the acquired tag splicing capability information and/or path identification capability information, multiple modes may be adopted, for example, a splicing node may be determined for the message to be forwarded from one or more routing forwarding devices according to the tag splicing capability information, and/or an identification node may be determined for the message to be forwarded from one or more routing forwarding devices according to the path identification capability information; and then, issuing a splicing label to the determined splicing node, and/or issuing an identification label to the determined identification node, wherein the splicing label is used for indicating the splicing node to splice and package the message and then forward the message, and the identification label is used for indicating the identification node to forward the message according to the path identified by the identification label.

The determining of the splicing node for the packet to be forwarded from the one or more routing forwarding devices according to the label splicing capability information, and/or the determining of the identification node for the packet to be forwarded from the one or more routing forwarding devices according to the path identification capability information may also be performed in various manners, for example, a relatively simple processing manner includes: firstly, selecting a standby splicing node and/or a standby identification node for a message to be forwarded according to the stack processing capacity of one or more routing forwarding devices; then, judging whether the standby splicing node supports label splicing and/or whether the standby identification node supports path identification according to the label splicing capacity information; and under the condition that the judgment result is yes, determining the standby splicing node as the splicing node and/or determining the standby identification node as the identification node. That is, only if the routing forwarding device satisfies a certain stack processing capability and supports the corresponding label splicing capability and/or path identification capability, the routing forwarding device can be determined as a splicing node for splicing the packet and/or an identification node for identifying the forwarding path.

And issuing the splicing label to the determined splicing node and/or issuing the identification label to the determined identification node in a plurality of ways, preferably in the following way, by carrying the splicing label and/or the identification label at the corresponding position of the extended sub-object of the SR-ERO, issuing the splicing label to the determined splicing node and/or issuing the identification label to the determined identification node.

In addition, when obtaining label splicing capability information used for identifying whether one or more routing forwarding devices support label splicing, and/or path identification capability information used for identifying whether one or more routing forwarding devices support path identification, multiple ways may also be adopted, such as: the tag splicing capability information and/or the path identification capability information may be obtained by obtaining a field value corresponding to an extension field in a type length value TLV attribute of the segment routing SR capability, where the field value is used to identify whether one or more routing forwarding devices support tag splicing, and/or is used to identify whether one or more routing forwarding devices support path identification.

Fig. 4 is a flowchart of a second message forwarding processing method according to an embodiment of the present invention, and as shown in fig. 4, the flowchart includes the following steps:

step S402, acquiring label splicing ability information for identifying whether the controller supports label splicing and/or path identification ability information for identifying whether the controller supports path identification;

and step S404, forwarding the message to be forwarded according to the acquired label splicing capability information and/or path identification capability information and the forwarding strategy issued by the controller.

Through the steps, the routing forwarding device obtains the label splicing capability information of whether the controller supports label splicing and/or the path identification capability information of whether the controller supports path identification, and forwards the message to be forwarded by the forwarding strategy issued by the controller, so that the problem that whether the splicing and/or path identification functions of SR LIST are supported or not can not be known among related devices which forward the message in the related technology, and the message cannot be effectively forwarded is solved, the capability information of whether label splicing and/or path identification is supported or not can be notified among the devices, and the effect of forwarding the message is achieved.

When forwarding the message to be forwarded according to the acquired tag splicing capability information and/or path identification capability information and the forwarding policy issued by the controller, multiple processing modes may be adopted, for example, the splicing tag and/or the identification tag issued by the controller may be received first; and then, carrying out forwarding processing on the message to be forwarded after splicing and packaging the message to be forwarded according to the splicing label, and/or carrying out forwarding processing on the message to be forwarded according to the path marked by the identification label.

The splicing label and/or the identification label sent by the controller may also be received in various manners, for example, the splicing label and/or the identification label sent by the controller may be received in a manner of carrying the splicing label and/or the identification label at a position corresponding to the extended sub-object of the SR-ERO.

In addition, when the label splicing capability information for identifying whether the controller supports label splicing and/or the path identification capability information for identifying whether the controller supports path identification are obtained, multiple processing manners may also be adopted, for example, the label splicing capability information and/or the path identification capability information may be obtained by obtaining a field value corresponding to an extension field in a type length value TLV attribute of the segment routing SR capability, where the field value is used to identify whether the controller supports label splicing and/or is used to identify whether the controller supports path identification.

In this embodiment, a message forwarding processing apparatus is further provided, and the apparatus is used to implement the foregoing embodiments and preferred embodiments, and details of which have been already described are omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 5 is a block diagram of a first packet forwarding processing apparatus according to an embodiment of the present invention, and as shown in fig. 5, the apparatus includes a first obtaining module 52 and a sending module 54, which will be described below.

A first obtaining module 52, configured to obtain label splicing capability information used to identify whether one or more routing forwarding devices support label splicing, and/or path identification capability information used to identify whether one or more routing forwarding devices support path identification; and the issuing module 54 is connected to the first obtaining module 52, and configured to issue a forwarding policy for forwarding a packet to be forwarded to one or more routing forwarding devices according to the obtained tag splicing capability information and/or path identification capability information.

Fig. 6 is a block diagram of a preferred structure of an issuing module 54 in a first message forwarding processing apparatus according to an embodiment of the present invention, and as shown in fig. 6, the issuing module 54 includes: a determination unit 62 and a distribution unit 64, which are described below with respect to the distribution module 54.

A determining unit 62, configured to determine a splicing node for the packet to be forwarded from the one or more routing forwarding devices according to the tag splicing capability information, and/or determine an identification node for the packet to be forwarded from the one or more routing forwarding devices according to the path identification capability information; and an issuing unit 64, connected to the determining unit 62, configured to issue a splicing label to the determined splicing node, and/or issue an identification label to the determined identification node, where the splicing label is used to instruct the splicing node to perform splicing encapsulation on the packet and then forward the packet, and the identification label is used to instruct the identification node to forward the packet according to the path identified by the identification label.

Fig. 7 is a block diagram of a preferred structure of the determining unit 62 in the first intermediate sending module 54 of the message forwarding processing apparatus according to the embodiment of the present invention, and as shown in fig. 7, the determining unit 62 includes: a selection subunit 72, a judgment subunit 74, and a determination subunit 76, which are explained below with respect to the determination unit 62.

A selecting subunit 72, configured to select a standby concatenation node and/or a standby identifier node for the packet to be forwarded according to stack processing capabilities of one or more routing forwarding devices; a judging subunit 74, connected to the selecting subunit 72, configured to judge, according to the tag splicing capability information, whether the standby splicing node supports tag splicing, and/or whether the standby identification node supports path identification; and a determining subunit 76, connected to the judging subunit 74, for determining the spare splicing node as the splicing node and/or the spare identification node as the identification node if the judgment result is yes.

Preferably, the issuing unit 64 is further configured to issue the splicing label to the determined splicing node and/or issue the identification label to the determined identification node in a manner that the splicing label and/or the identification label are carried at the corresponding position of the SR-ERO extended sub-object.

Preferably, the first obtaining module 52 is further configured to obtain the label splicing capability information and/or the path identification capability information by obtaining a field value corresponding to an extension field in a type length value TLV attribute of the segment routing SR capability, where the field value is used to identify whether one or more routing forwarding devices support label splicing, and/or is used to identify whether one or more routing forwarding devices support path identification.

Fig. 8 is a block diagram of a controller according to an embodiment of the present invention, and as shown in fig. 8, the controller 80 includes any one of the first message forwarding processing devices 82.

Fig. 9 is a block diagram of a preferred structure of a second message forwarding processing apparatus according to an embodiment of the present invention, and as shown in fig. 9, the apparatus includes: a second acquisition module 92 and a processing module 94, which will be described below.

A second obtaining module 92, configured to obtain tag splicing capability information used for identifying whether the controller supports tag splicing, and/or path identification capability information used for identifying whether the controller supports path identification; and a processing module 94, connected to the second obtaining module 92, configured to forward the packet to be forwarded according to the obtained tag splicing capability information and/or the path identifier capability information, and a forwarding policy issued by the controller.

Fig. 10 is a block diagram of a preferred structure of a processing module 94 in a second message forwarding processing apparatus according to an embodiment of the present invention, and as shown in fig. 10, the processing module 94 includes: a receiving unit 102 and a processing unit 104, which processing module 94 will be explained below.

A receiving unit 102, configured to receive a splicing label and/or an identification label issued by a controller; and the processing unit 104 is connected to the receiving unit 102, and is configured to perform forwarding processing after performing splicing encapsulation on the packet to be forwarded according to the splicing label, and/or perform forwarding processing on the packet to be forwarded according to the path identified by the identification label.

Preferably, the receiving unit 102 is further configured to receive the splicing label and/or the identification label sent by the controller in a manner that the splicing label and/or the identification label is carried at a position corresponding to the extended sub-object of the SR-ERO.

Preferably, the second obtaining module 92 is further configured to obtain the tag splicing capability information and/or the path identification capability information by obtaining a field value corresponding to an extension field in a type length value TLV attribute of the segment routing SR capability, where the field value is used to identify whether the controller supports tag splicing and/or identify whether the controller supports path identification.

Fig. 11 is a block diagram of a routing forwarding apparatus according to an embodiment of the present invention, and as shown in fig. 11, the routing forwarding apparatus 110 includes any one of the second packet forwarding processing devices 112.

Before the description of the preferred embodiment of the present invention, the label splicing and path identification scheme of SR LIST is described in two examples. By extending the management SRGB block, free labels are used to indicate the splice or path identification.

The label splicing mode can be realized as follows:

fig. 12 is a schematic diagram of a network architecture for performing label splicing and/or path identification according to an embodiment of the present invention, as shown in fig. 12: in the figure, the SID allocated by the NODE ID of each device is 101-:

1. the label of 100 on the controller is not assigned, and the label of 100 is used as the splicing identification of each segment. (the label of 100 is not the SID of a node or link, but is used to represent a splice.)

2. Sending the information to each LIST segment splicing node, namely the corresponding node needing to splice the LIST package of the message header, and the corresponding LIST processing information (the information is sent by a southbound interface protocol, such as extension sending of protocols such as PCEP, OpenFlow, and the like):

for the R1 node, the encapsulation required for issuing the packet header of the traffic that needs to be forwarded to the policy path is 102-.

For the R3 node, it is necessary to send an identifier that is mapped to 100 and 106 and 108 and 100, and guide the splicing and encapsulation to form a forwarding table, fig. 13 is a format schematic diagram of a label forwarding table spliced by labels corresponding to the embodiment of the present invention, as shown in fig. 13, when the incoming label is 100, multiple labels are on the Push, and the next hop and the outgoing interface are copied to be the forwarding table of the outermost label 105 of the mapping fragment.

For the R8 node, it needs to send the identifiers of 100 to 107 and 109 and 110 to guide the splicing encapsulation to form a forwarding table, as shown in fig. 13, when it is found that the incoming label is 100, multiple labels are on the Push, and the forwarding table of the outermost label of the mapping fragment is copied by the next hop and the outgoing interface.

3. The message forwarding process is as follows:

the message arrives at the R1 node, and the 4-layer message header 102-. Looking up forwarding table item according to outer label 102, and forwarding to node R2

The R2 receives the traffic carrying the message head 102-;

the subsequent message is forwarded to the R8 node as above, and the splicing identifier mapped by 100 is searched for repackaging 107-.

Therefore, the message is forwarded to the destination address according to the path strategy information under the condition that the chip packaging processing capacity of the equipment is not required to be changed.

The path identification mode can be realized as follows:

as shown in fig. 12, SID allocated to NODE IDs of each device in the figure is 101-:

1. the label of 100 on the controller is not assigned and the label of 100 is used to identify the policy path on the controller. (the label 100 is not a SID for a node or link, but is used only for path identification.)

2. And the controller issues the path and the path identification information to each strategy sub-path head node according to the acquired deep processing capability of the node stack and the strategy path information, namely the node which needs splicing the LIST package of the SR message header correspondingly. From the acquired stack depth processing capabilities, it is known that segmentation will occur on R1, R4, R5, R8. (information is issued through a southbound interface protocol, such as an extension of protocols such as PCEP and OpenFlow):

for the R1 node, the issued path identifier and path information are: 100: 101,102, 103,105,106, 107,109, 110; r1 knows that it is the source node and the stack depth processing capability of itself is 3, then directly forms encapsulation {102, 104, 100} to be loaded in the header and the next hop edge 102 to be forwarded.

For the R4 node, 100: 101-.

For the R5 node, 100: 101-.

For the R8 node, 100: 101-.

3. The message forwarding process is as follows:

the message arrives at the R1 node, and the layer 3 label header 102 and 104 and 100 are encapsulated according to the policy for the flow. Searching a forwarding table item according to the outer layer label 102, and forwarding the forwarding table item to the node R2;

r2 receives the traffic carrying the message header 102 and 104 and 100, finds that the outmost label is the SID of itself, pops up the 102 label and forwards the label according to 104, and forwards the label to the R4 node;

r4 receives the flow carrying the message header 104 and 100, finds that the outmost label is the SID of itself, pops up the 104 label and forwards according to 100, finds that the forwarding table of 100 needs to package 3-fold labels 103 and 105 and 100, finds that the next hop and outgoing interface is the next hop and outgoing interface of 103, and forwards the message to R3;

r3 receives the traffic carrying the message header 103 and 105 and 100, finds that the outmost label is the SID of itself, pops up the 103 label and forwards the label according to 105, and forwards the label to the R5 node;

r5 receives the flow carrying the message header 105 and 100, finds that the outmost label is SID of itself, pops up 105 label and forwards according to 100, finds that the forwarding table of 100 needs to package 3-fold label 106 and 108 and the next hop and outgoing interface is 106, and forwards the message to R6;

r6 receives the traffic carrying the message header 106 and 108 and 100, finds that the outermost label is the SID of the outermost label, pops up the 106 label and forwards the label according to 108, and forwards the label to the R8 node;

r8 receives the traffic carrying the message header 108 and 100, finds that the outmost label is SID of itself, pops up 108 label and forwards according to 100, finds that the forwarding table of 100 needs to package 3-fold label 107 and 109 and the next hop and outgoing interface is the next hop and outgoing interface of 107, and forwards the message to R7;

r7 receives the traffic carrying the message header 107-109-110, finds that the outmost label is the SID of itself, pops up the 107 label and forwards the label according to 109, and forwards the label to the R9 node;

r9 receives the traffic carrying the message header 109-110, finds that the outmost label is the SID of itself, pops up the 109 label and forwards the label according to 110, and forwards the label to the R10 node;

r10 receives the flow carrying message header 110, finds out that the outmost label is SID of itself, pops up 110 label, and restores the original message forwarding.

In the preferred embodiment, by extending a Path Computation Element Communication Protocol (PCEP), the device may notify whether SR LIST concatenation (i.e., the above label concatenation) or a Path identification function is supported, and the PCEP Protocol may carry SR LIST information and a corresponding concatenation or Path identification label and perform corresponding processing to form forwarding information under the condition supported by the device. The scheme mainly comprises the following steps: the controller collects network topology through SR service and calculates corresponding SR LIST according to application requirement; splicing or sending path identification information to a first node of a sub-path by adopting a mode of sending SR LIST in a segmented mode when the SRLIST exceeds the maximum label stack depth of the equipment; whether splicing or path identification capability of the SR LIST is supported on the PCEP collecting equipment is used as a basis for the controller to carry out SR LIST segmentation, and finally SR LIST segmentation information or path identification information is issued to a required intermediate node; when the forwarding equipment receives the splicing or path identification information, a label forwarding table is formed; and when each node receives the corresponding forwarding message, packaging and forwarding the corresponding message according to the forwarding table.

The following describes a preferred embodiment of the present invention with reference to the above label splicing and path identification schemes and the accompanying drawings.

SR LIST splicing or path identification capability advertisement and use

Since the SR LIST splicing or path identification function requires support from a forwarding device (i.e., the above-mentioned route forwarding device), the splicing or path identification label is recognized and processed. The controller needs to know whether the forwarding device supports SR LIST splicing or path identification capabilities. The function can be obtained by expanding on the basis that the PCEP supports the SR function protocol draft (draft-ietf-pce-segment-routing-00).

The current draft defines an SR CAPABILITY TLV (SR-PCE-CAPABILITY TLV) for notifying whether SR LIST establishment is supported between the forwarding device and the controller, and notifies the maximum label stack depth supported by the forwarding device through an msd (maximum SID depth) field, where currently, Flags and Reserved fields are set to 0 by default. Fig. 14 is a message format diagram of an SR capability TLV advertisement splicing capability and/or a path identification capability according to the preferred embodiment of the present invention, and as shown in fig. 14, on the basis of the SR capability TLV, a j (joint) bit is added to an extended Flags field to indicate whether an SR LIST splicing function is supported. Setting J to 1 indicates that stitching is supported and resetting J to 0 indicates that stitching is not supported. The extended Flags field is incremented by a P (Path Id) bit to indicate whether the path identification function is supported. Setting P to 1 indicates that the path ID is supported, and resetting P to 0 indicates that the path ID is not supported. The SR LIST on the controller can only select one mode of label splicing or path identification for the same node, and simultaneously issues the two modes, and the forwarding equipment considers to be abnormal and does not process the information issued by the next node.

The notification process of the label splicing capability is as follows:

the forwarding device informs the controller of the splicing capability procedure:

1. if the forwarding device supports splicing, the forwarding device sets up the J position 1 of the SR capability TLV in an initialization message when the PCC client where it resides establishes a PCEP session with the controller.

2. After receiving the SR capacity TLV in the initialization message, the PCE on the controller records whether the forwarding equipment supports the SRLIST splicing function, and simultaneously records the maximum label stack depth limit of the equipment.

The controller informs the forwarding device of the splicing capability procedure:

1. if the PCE service end on the controller sends the J position 1, the controller is shown to support the SR LIST segment splicing function.

2. The PCC on the forwarding equipment receives the J bit information in the SR capacity TLV in the initialization message, and can record or not process according to the local strategy, but even if the segmentation splicing function is not supported, the error does not need to be replied, the information is ignored, and the conversation is established according to the normal mode.

The notification and processing process of the path identification capability is the same as the label splicing capability, and only the P bit is adopted for notification.

After the controller collects and records the maximum label stack depth supported by each forwarding device and whether SR LIST splicing or path identification capability is supported, whether SR LIST splicing or path identification is required or not is judged according to the maximum label stack depth limit, and a corresponding splicing or identification node is selected.

SR LIST splicing or path identification information issuing mode:

the controller calculates the SR LIST and then sends the SR LIST through a PCEP channel, and the SR LIST information is defined in a draft-ietf-pce-segment-routing-00 and is carried by using an SR-ERO sub-object by expanding the sub-type of the ERO. The splice or path identification tag may also be carried by further extending the SR-ERO. Fig. 15 is a schematic diagram of a message format of SR-ERO advertisement concatenation and path identifier SID according to the preferred embodiment of the present invention, as shown in fig. 15, an original Flags field in the SR-ERO only uses 4 bits, and they are set to 1 meaning: m indicates that SID is a tag and the first 20bits are valid, C indicates that the tag' S additional attribute bits are valid, S indicates that the SID value is not carried, and F indicates that the NAI portion is not carried. We add a J (joint) bit on this basis, where a J set to 1 indicates that SID is a splice tag, and a J reset to 0 indicates a non-splice tag. Meanwhile, a P (Path Id) bit is added, the setting of P to 1 indicates that SID is a path identification tag, and the resetting of P to 0 indicates a non-path identification tag.

The controller issues the setting of the relevant bits of the splicing label SR-ERO as follows: m is 1, C is 0, S is 0, F is 1, J is 1, and P is 0. If the PCC residing on the forwarding device cannot process such SR-ERO, the PCErr message Error-Type is replied to 10, and Error-value is replied to 8 (does not support path identifier or splicing label), and meanwhile, the corresponding Error SR-ERO object is carried to the controller, and the whole message is ignored. The spliced label issued by the controller can only appear at the top of the SR-ERO label stack or two positions lower than the stack. The PCC only processes the splicing labels at the top of the stack. The splicing label appears at other positions and needs to reply a PCErr message Error-Type of 10 and Error-value of 9 (path identifier or splicing label format Error), and simultaneously carries the whole ERO object to the controller and ignores the whole message.

The controller issues the setting of the relevant bits of the path identification label SR-ERO as follows: m is 1, C is 0, S is 0, F is 1, J is 0, and P is 1. If the PCC residing on the forwarding device cannot process such SR-ERO, the PCErr message Error-Type is replied to 10, and Error-value is replied to 8 (does not support path identifier or splicing label), and meanwhile, the corresponding Error SR-ERO object is carried to the controller, and the whole message is ignored. The path identification label issued by the controller can only appear at the top of the SR-ERO label stack. The PCC only processes the path identification label at the top of the stack. The identification tag appears at other positions and needs to reply to a PCErr message Error-Type of 10 and Error-value of 9 (a path identifier or a splicing tag format Error), and simultaneously carries the whole ERO object to the controller and ignores the whole message.

The following describes the splicing delivery process and the path identifier delivery process of SR LIST.

SR LIST splicing issuing processing process

As shown in fig. 12: in the figure, the SID assigned to the NODE ID of each device is 101-. And the label of 100 on the controller is not distributed, the label of 100 is adopted to perform mapping maintenance on the policy path on the controller, and the policy path is sent to the splicing node as a splicing label.

If all forwarding devices support the splicing function, the controller processes the issuing process as follows:

1. the R3 and R8 nodes are selected as splicing points according to the stack depth limit.

2. The calculation results of the head node R1 and the SR LIST issued by the splicing point R3 and R8 are respectively as follows: 102-104-103-100,100-105-106-108-100, 100-107-109-110.

3. The controller issues R1 nodes through a PCEP protocol: the R1 node receives the PCInitiate message to create a tunnel, and the SID label sequence in the SR-ERO sub-object of the LSP example in the message is 102,104,103,100. The PCC checks that the top label 102 is not a splicing label, and R1 directly forms a forwarding entry with 102 as forwarding information and 102 and 104 and 103 and 100 as label stacks.

4. The controller issues R3 nodes through a PCEP protocol: the R3 node receives the PCInitiate message to create a tunnel, and the SID label sequence in the SR-ERO sub-object of the LSP example in the message is 100,105,106,108,100. PCC checks find the top-of-stack label 100 to be a splice label and therefore do not count the total depth of the label stack and therefore are not considered to exceed the maximum label stack depth. Because the label at the top of the stack is a splicing label, the formed forwarding entry adopts the forwarding information of the next layer label 105, and forms a label stack of 105-.

5. The controller issues R8 nodes through a PCEP protocol: the R8 node receives the PCInitiate message to create a tunnel, the SID label sequence in the SR-ERO sub-object of the LSP example in the message is 100,107,109,110. because the top label of the stack is a splicing label, the formed forwarding entry adopts the forwarding information of the next label 107, and forms a label stack of 107 + 109 + 110. The forwarding table form is similar to the R3 node.

If the R8 node and the controller in fig. 12 establish a PCEP session, no tag splicing capability is advertised.

The controller considers the limitation of stack depth of 4 and also considers whether the node supports label stack splicing when selecting the splicing node. The controller can not select the R8 node when the SR LIST splicing point is selected, and the controller can select R3 and R6 as the splicing points. The SR LIST received by the head node R1 and the splice point R3, R6 are: 102-104-103-100,100-105-106-100, 100-108-107-109-110. The processing mode of each splicing point is not changed.

SR LIST path identifier issuing processing process

As shown in fig. 12: in the figure, the SID assigned to the NODE ID of each device is 101-. The label of 100 on the controller is not allocated, the label of 100 is adopted to perform mapping maintenance on the policy path on the controller, and the policy path is issued to the identification node as a path identification label. The controller processes the issuing process as follows:

1. the controller selects the R4, R5 and R8 nodes as the identification nodes according to the stack depth limit.

2. The controller adopts SR LIST under the route identification mode, the head node R1 and the SRLIST issued by the identification points R4, R5 and R8 are the same: 100-101-102-104-103-105-106-108-107-109-110.

3. The controller issues R1 nodes through a PCEP protocol: the R1 node receives the PCInitiate message to create a tunnel, and the SID label sequence in the SR-ERO sub-object of the LSP example in the message is 100,101,102,104,103,105,106,108,107,109,110. PCC check stack top label 100 is a path identification label, so SR LIST notified in ERO is a complete path and is not constrained by local stack depth, and no error message is replied. When the SR LIST is processed by R1, according to the constraint that the local maximum stack depth is 3, R1 forms forwarding information using SID value 102 immediately following local SID value 101, and selects SR LIST entries whose stack depth value is minus 1(3-1 ═ 2) from the local SID backward, and adds path identification tag 100 to form an SR LIST segment of 102-.

4. The controller sends the information and processing process of the R4 and R5 nodes to R1 through the PCEP protocol, and the formed stack pressing labels are 103-. The in-tag 100 forwarding behavior uses the forwarding behavior of the next SID value 103,106, respectively, that immediately follows the local SID.

5. The information and the processing process of the R8 node issued by the controller through the PCEP protocol are the same, but because the label stack depth is greater than or equal to the residual SR LIST after the local SID, the path identification label 100 does not need to be reused in the forwarding label, and the residual 107 and 109 and 110 are directly used as the forwarding push label. The forwarding of the incoming label 100 forms a forwarding behavior with 107.

The controller organizes the labels in a path identification mode, because the forwarding device also participates in the calculation formation of the label stack and does not know the path identification capability of other devices in the network, nodes which do not support the path identification labels cannot be avoided, and if the controller finds that the nodes found according to the label stack depth limitation do not support the path identification function, the controller abandons the SR LIST and carries out recalculation.

Control of orderly tunnel formation by SR LIST splicing or path identification

The head node and the splicing or identification node of the SR LIST both adopt the PCRpt message to inform the state of the SR LIST. The SDN controller may integrate the state information of the complete SR LIST according to the same concatenation or path identification tag carried by each node PCRpt message. Through the mutual cooperation of the PCRpt and the PCInitiate message, the controller can select to send the SR LIST to the intermediate point first, and then send the SR LIST to the head node after all the intermediate points report that the SR LIST state is available, so that the flow introduced by the head node is not lost.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A message forwarding processing method is characterized by comprising the following steps:

acquiring label splicing capability information used for identifying whether one or more routing forwarding devices support label splicing, and/or path identification capability information used for identifying whether one or more routing forwarding devices support path identification;

issuing a forwarding strategy for forwarding a message to be forwarded to the one or more routing forwarding devices according to the acquired label splicing capability information and/or the acquired path identification capability information;

wherein, issuing the forwarding policy for forwarding the packet to be forwarded to the one or more routing forwarding devices according to the acquired tag splicing capability information and/or the path identification capability information includes:

determining a splicing node for the message to be forwarded from the one or more routing forwarding devices according to the label splicing capability information, and/or determining an identification node for the message to be forwarded from the one or more routing forwarding devices according to the path identification capability information;

and issuing a splicing label to the determined splicing node and/or issuing an identification label to the determined identification node, wherein the splicing label is used for indicating the splicing node to splice and package the message and then forward the message, and the identification label is used for indicating the identification node to forward the message according to the path identified by the identification label.

2. The method according to claim 1, wherein determining the splicing node for the packet to be forwarded from the one or more routing forwarding devices according to the label splicing capability information, and/or determining the identification node for the packet to be forwarded from the one or more routing forwarding devices according to the path identification capability information comprises:

selecting a standby splicing node and/or a standby identification node for the message to be forwarded according to the stack processing capacity of the one or more routing forwarding devices;

judging whether the standby splicing node supports label splicing or not and/or whether the standby identification node supports path identification or not according to the label splicing capacity information;

and if so, determining the standby splicing node as the splicing node and/or the standby identification node as the identification node.

3. The method of claim 1, wherein issuing the splicing label to the determined splicing node and/or issuing the identification label to the determined identification node comprises:

and issuing the splicing label to the determined splicing node and/or issuing the identification label to the determined identification node in a mode of carrying the splicing label and/or the identification label at the corresponding position of the SR-ERO expansion sub-object.

4. The method according to any one of claims 1 to 3, wherein the label splicing capability information for identifying whether the one or more routing forwarding devices support label splicing and/or the path identification capability information for identifying whether the one or more routing forwarding devices support path identification is obtained by:

and acquiring the label splicing capability information and/or the path identification capability information by acquiring a field value corresponding to an extension field in a type length value TLV attribute of the segment routing SR capability, wherein the field value is used for identifying whether the one or more routing forwarding devices support label splicing and/or identifying whether the one or more routing forwarding devices support path identification.

5. A message forwarding processing method is characterized by comprising the following steps:

acquiring label splicing capacity information for identifying whether a controller supports label splicing and/or path identification capacity information for identifying whether the controller supports path identification;

forwarding the message to be forwarded according to the acquired label splicing capability information and/or the path identification capability information and a forwarding strategy issued by the controller;

wherein, forwarding the packet to be forwarded according to the acquired tag splicing capability information and/or the path identifier capability information and the forwarding policy issued by the controller includes:

receiving a splicing label and/or an identification label issued by the controller;

and performing forwarding processing after the message to be forwarded is spliced and encapsulated according to the splicing label, and/or performing forwarding processing on the message to be forwarded according to the path marked by the identification label.

6. The method of claim 5, wherein receiving the splice label and/or the identification label sent by the controller comprises:

and receiving the splicing label and/or the identification label sent by the controller in a mode of carrying the splicing label and/or the identification label at the corresponding position of the SR-ERO expansion sub-object.

7. The method according to claim 5, wherein the label splicing capability information for identifying whether the controller supports label splicing and/or the path identification capability information for identifying whether the controller supports path identification is obtained by:

and acquiring the label splicing capability information and/or the path identification capability information by acquiring a field value corresponding to an extension field in a type length value TLV attribute of the segment routing SR capability, wherein the field value is used for identifying whether the controller supports label splicing and/or identifying whether the controller supports path identification.

8. A message forwarding processing apparatus, comprising:

a first obtaining module, configured to obtain label splicing capability information used for identifying whether one or more routing forwarding devices support label splicing, and/or path identification capability information used for identifying whether one or more routing forwarding devices support path identification;

the issuing module is used for issuing a forwarding strategy for forwarding a message to be forwarded to the one or more routing forwarding devices according to the acquired label splicing capability information and/or the acquired path identification capability information;

wherein, the issuing module comprises: a determining unit, configured to determine a splicing node for the packet to be forwarded from the one or more routing forwarding devices according to the tag splicing capability information, and/or determine an identification node for the packet to be forwarded from the one or more routing forwarding devices according to the path identification capability information; and the issuing unit is used for issuing a splicing label to the determined splicing node and/or issuing an identification label to the determined identification node, wherein the splicing label is used for indicating the splicing node to splice and encapsulate the message and then forward the message, and the identification label is used for indicating the identification node to forward the message according to the path identified by the identification label.

9. The apparatus of claim 8, wherein the determining unit comprises:

a selecting subunit, configured to select a standby concatenation node and/or a standby identifier node for the packet to be forwarded according to the stack processing capability of the one or more routing forwarding devices;

a judging subunit, configured to judge, according to the tag splicing capability information, whether the standby splicing node supports tag splicing, and/or whether the standby identification node supports path identification;

and the determining subunit is configured to determine, if the determination result is yes, that the standby splicing node is the splicing node, and/or that the standby identification node is the identification node.

10. The apparatus of claim 8,

the issuing unit is further configured to issue the splicing label to the determined splicing node and/or issue the identification label to the determined identification node in a manner that the splicing label and/or the identification label is carried at a position corresponding to an extended sub-object of the SR-ERO.

11. The apparatus according to any one of claims 8 to 10,

the first obtaining module is further configured to obtain the tag splicing capability information and/or the path identification capability information by obtaining a field value corresponding to an extension field in a type length value TLV attribute of a segment routing SR capability, where the field value is used to identify whether the one or more routing forwarding devices support tag splicing, and/or is used to identify whether the one or more routing forwarding devices support path identification.

12. A controller comprising the apparatus of any one of claims 8 to 11.

13. A message forwarding processing apparatus, comprising:

a second obtaining module, configured to obtain tag splicing capability information used for identifying whether a controller supports tag splicing, and/or path identification capability information used for identifying whether the controller supports path identification;

the processing module is used for forwarding the message to be forwarded according to the acquired label splicing capability information and/or the path identification capability information and the forwarding strategy issued by the controller;

wherein the processing module comprises:

the receiving unit is used for receiving the splicing label and/or the identification label sent by the controller;

and the processing unit is used for carrying out forwarding processing after splicing and packaging the message to be forwarded according to the splicing label, and/or carrying out forwarding processing on the message to be forwarded according to the path marked by the identification label.

14. The apparatus of claim 13,

the receiving unit is further configured to receive the splicing label and/or the identification label issued by the controller in a manner that the splicing label and/or the identification label is carried at a position corresponding to an extended sub-object of the SR-ERO.

15. The apparatus of claim 13,

the second obtaining module is further configured to obtain the tag splicing capability information and/or the path identifier capability information by obtaining a field value corresponding to an extension field in a type length value TLV attribute of segment routing SR capability, where the field value is used to identify whether the controller supports tag splicing and/or identify whether the controller supports path identifier.

16. A route forwarding device comprising the apparatus of any one of claims 13 to 15.