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; the method further comprises: marking, by the ingress node, an FL transmit and receive capability of the ingress node in the first FL capability flag bit; 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, the load distribution node being an intermediate node of the forwarding path and a first node before branching; 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 the RSVP-TE resv message is constructed after the egress node obtains the FL transmit and receive capability of the ingress node from the RSVP-TE path message and determines that the ingress node can identify an FL, wherein an FL transmit and receive capability of the egress node is marked in the 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, determining that the egress node may identify an FL, and completing FL negotiation; wherein the completing the FL negotiation comprises: judging, according to the first FL capability flag bit and the second FL capability flag bit, whether a path from an ingress node to the egress node supports FL forwarding; wherein if either the ingress node or the egress node does not have the FL transmit and receive capability, the path from the ingress node to the egress node does not support the FL forwarding; and if both the ingress node and the egress node have the FL transmit and receive capability, the path from the ingress node to the egress node supports 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; the method further comprises: marking, by the ingress node, an FL transmit and receive capability of the ingress node in the first FL capability flag bit; 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, the load distribution node being an intermediate node of the forwarding path and a first node before branching; 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 the RSVP-TE resv message is constructed after the egress node obtains the FL transmit and receive capability of the ingress node from the RSVP-TE path message and determines that the ingress node can identify an FL, wherein an FL transmit and receive capability of the egress node is marked in the 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, determining that the egress node may identify an FL, and completing FL negotiation; wherein the completing the FL negotiation comprises: marking, by the ingress node, an FL transmit and receive capability of the ingress node in the first FL capability flag bit; 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, the load distribution node being an intermediate node of the forwarding path and a first node before branching; 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 the RSVP-TE resv message is constructed after the egress node obtains the FL transmit and receive capability of the ingress node from the RSVP-TE path message and determines that the ingress node can identify an FL, wherein an FL transmit and receive capability of the egress node is marked in the 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, determining that the egress node may identify an FL, and completing FL negotiation; wherein the completing the FL negotiation comprises: judging, according to the first FL capability flag bit and the second FL capability flag bit, whether a path from an ingress node to the egress node supports FL forwarding; wherein if either the ingress node or the egress node does not have the FL transmit and receive capability, the path from the ingress node to the egress node does not support the FL forwarding; and if both the ingress node and the egress node have the FL transmit and receive capability, the path from the ingress node to the egress node supports the FL forwarding.