A flow label negotiation method for multi-path forwarding, comprising: constructing, by an ingress node of a forwarding path, a resource reservation protocol-traffic engineering, RSVP-TE, path message, characterized in that the RSVP-TE path message comprises: a first flow label, FL, capability flag bit and a flow label indicator, FLI; the method further comprises: marking, by the ingress node, an FL transmit and receive capability in the first FL capability flag bit, wherein the FL transmit and receive capability is used to identify whether the ingress node can process an FL; sending, by the ingress node, the RSVP-TE path message to an egress node of the forwarding path through a load distribution node of the forwarding path, wherein the load distribution node is an intermediate node of the forwarding path, wherein the FLI of the RSVP-TE path message is used by the egress node to identify the FL; receiving, by the ingress node, an RSVP-TE resv message which is sent by the egress node, wherein the RSVP-TE resv message comprises: a second FL capability flag bit; and obtaining, by the ingress node, from the second FL capability flag bit, an FL transmit and receive capability of the egress node, wherein the FL transmit and receive capability of the egress node is used to identify whether the egress node can process an FL; judging, according to the first FL capability flag bit and the second FL capability flag bit, whether a path from the ingress node to the egress node supports FL forwarding; wherein when both the ingress node and the egress node have the FL transmit and receive capability, determining that the path from the ingress node to the egress node supports the FL forwarding, or when either the ingress node or the egress node does not have the FL transmit and receive capability, determining that the path from the ingress node to the egress node does not support the FL forwarding. constructing, by an ingress node of a forwarding path, a resource reservation protocol-traffic engineering, RSVP-TE, path message, characterized in that the RSVP-TE path message comprises: a first flow label, FL, capability flag bit and a flow label indicator, FLI; the method further comprises: marking, by the ingress node, an FL transmit and receive capability in the first FL capability flag bit, wherein the FL transmit and receive capability is used to identify whether the ingress node can process an FL; sending, by the ingress node, the RSVP-TE path message to an egress node of the forwarding path through a load distribution node of the forwarding path, wherein the load distribution node is an intermediate node of the forwarding path, wherein the FLI of the RSVP-TE path message is used by the egress node to identify the FL; receiving, by the ingress node, an RSVP-TE resv message which is sent by the egress node, wherein the RSVP-TE resv message comprises: a second FL capability flag bit; and obtaining, by the ingress node, from the second FL capability flag bit, an FL transmit and receive capability of the egress node, wherein the FL transmit and receive capability of the egress node is used to identify whether the egress node can process an FL; judging, according to the first FL capability flag bit and the second FL capability flag bit, whether a path from the ingress node to the egress node supports FL forwarding; wherein when both the ingress node and the egress node have the FL transmit and receive capability, determining that the path from the ingress node to the egress node supports the FL forwarding, or when either the ingress node or the egress node does not have the FL transmit and receive capability, determining that the path from the ingress node to the egress node does not support the FL forwarding. marking, by the ingress node, an FL transmit and receive capability in the first FL capability flag bit, wherein the FL transmit and receive capability is used to identify whether the ingress node can process an FL; sending, by the ingress node, the RSVP-TE path message to an egress node of the forwarding path through a load distribution node of the forwarding path, wherein the load distribution node is an intermediate node of the forwarding path, wherein the FLI of the RSVP-TE path message is used by the egress node to identify the FL; receiving, by the ingress node, an RSVP-TE resv message which is sent by the egress node, wherein the RSVP-TE resv message comprises: a second FL capability flag bit; and obtaining, by the ingress node, from the second FL capability flag bit, an FL transmit and receive capability of the egress node, wherein the FL transmit and receive capability of the egress node is used to identify whether the egress node can process an FL; judging, according to the first FL capability flag bit and the second FL capability flag bit, whether a path from the ingress node to the egress node supports FL forwarding; wherein when both the ingress node and the egress node have the FL transmit and receive capability, determining that the path from the ingress node to the egress node supports the FL forwarding, or when either the ingress node or the egress node does not have the FL transmit and receive capability, determining that the path from the ingress node to the egress node does not support the FL forwarding.