A method performed in a Multipath Transmission Control Protocol, MPTCP, scheduler which is scheduling a TCP flow between a first peer and an MPTCP capable second peer, the method comprising: setting up the TCP flow comprising at least two sub-flows connecting the MPTCP capable second peer, each sub-flow being associated with an address for the MPTCP capable second peer; receiving external information relating to at least one of the at least two sub-flows; and scheduling data in the TCP flow based on the received external information, wherein the scheduling comprises choosing which sub-flow or sub-flows of the at least two sub-flows to schedule the data via, based on the received external information characterized by the receiving external information comprises receiving information that one of the at least two sub-flows has been or will be terminated due to a handover for enabling the scheduler to send data via another sub-flow, without having to wait for a TCP acknowledgement for sent data which has been lost due to the sub-flow having been terminated, and wherein the scheduling, based on the received information of the sub-flow termination, comprises any of: the MPTCP scheduler initiating multi-casting so that a TCP packet or TCP packets of the TCP flow are sent temporarily on a plurality of the sub-flows; the MPTCP scheduler reducing the usage of the one of the at least two sub-flows; the MPTCP scheduler stops using the one of the at least two sub-flows; or the MPTCP scheduler re-sending the TCP packet or TCP packets already sent via the one of the at least two sub-flows via another of the at least two sub-flows without waiting for a time-out of acknowledgement of the already sent TCP packet or TCP packets. setting up the TCP flow comprising at least two sub-flows connecting the MPTCP capable second peer, each sub-flow being associated with an address for the MPTCP capable second peer; receiving external information relating to at least one of the at least two sub-flows; and scheduling data in the TCP flow based on the received external information, wherein the scheduling comprises choosing which sub-flow or sub-flows of the at least two sub-flows to schedule the data via, based on the received external information characterized by the receiving external information comprises receiving information that one of the at least two sub-flows has been or will be terminated due to a handover for enabling the scheduler to send data via another sub-flow, without having to wait for a TCP acknowledgement for sent data which has been lost due to the sub-flow having been terminated, and wherein the scheduling, based on the received information of the sub-flow termination, comprises any of: the MPTCP scheduler initiating multi-casting so that a TCP packet or TCP packets of the TCP flow are sent temporarily on a plurality of the sub-flows; the MPTCP scheduler reducing the usage of the one of the at least two sub-flows; the MPTCP scheduler stops using the one of the at least two sub-flows; or the MPTCP scheduler re-sending the TCP packet or TCP packets already sent via the one of the at least two sub-flows via another of the at least two sub-flows without waiting for a time-out of acknowledgement of the already sent TCP packet or TCP packets. the MPTCP scheduler initiating multi-casting so that a TCP packet or TCP packets of the TCP flow are sent temporarily on a plurality of the sub-flows; the MPTCP scheduler reducing the usage of the one of the at least two sub-flows; the MPTCP scheduler stops using the one of the at least two sub-flows; or the MPTCP scheduler re-sending the TCP packet or TCP packets already sent via the one of the at least two sub-flows via another of the at least two sub-flows without waiting for a time-out of acknowledgement of the already sent TCP packet or TCP packets.