US 12,445,382 B2
Application mobility based on enhanced MPTCP
Michelle Perras, Montréal (CA); Robert G. Gazda, Spring City, PA (US); Debashish Purkayastha, Collegeville, PA (US); and Antonio de la Oliva, Madrid (ES)
Assigned to InterDigital Patent Holdings, Inc., Wilmington, DE (US)
Appl. No. 16/964,795
Filed by INTERDIGITAL PATENT HOLDINGS, INC., Wilmington, DE (US)
PCT Filed Jan. 25, 2019, PCT No. PCT/US2019/015201
§ 371(c)(1), (2) Date Jul. 24, 2020,
PCT Pub. No. WO2019/147970, PCT Pub. Date Aug. 1, 2019.
Claims priority of provisional application 62/622,586, filed on Jan. 26, 2018.
Prior Publication US 2021/0058329 A1, Feb. 25, 2021
Int. Cl. H04L 47/24 (2022.01); H04L 45/24 (2022.01); H04L 47/193 (2022.01); H04L 69/14 (2022.01)
CPC H04L 47/24 (2013.01) [H04L 45/24 (2013.01); H04L 47/193 (2013.01); H04L 69/14 (2013.01)] 6 Claims
OG exemplary drawing
 
1. A method implemented in a wireless transmit/receive unit (WTRU), the method comprising:
communicating data traffic over a transmission control protocol (TCP) session with a multipoint transmission control protocol (MPTCP) stack running on the WTRU;
anchoring to a first mobile edge (ME) device;
exchanging the data traffic with a server application over a first MPTCP sub-flow on the first ME host device; wherein the first MPTCP sub-flow is configured to a regular priority, sub-flow wherein the regular priority means that a subflow is to be used now;
anchoring to a second ME host device;
responsive to anchoring to the second ME host device, receiving a first message, from the second ME host device, indicating to the WTRU an establishment of a second MPTCP sub-flow;
responsive to the first message, accepting the establishment of the second MPTCP sub-flow, wherein the second MPTCP sub-flow is configured to a pre-allocated priority, wherein the pre-allocated priority means that a subflow is created but not yet to be used to exchange data traffic;
after the second MPTCP sub-flow is established, receiving a second message, from the second ME host device, indicating configuring the second MPTCP sub-flow to the regular priority to start to exchange data traffic;
responsive to the second message, changing the configuration of the second MPTCP sub-flow from the pre-allocated priority configuration to the regular priority configuration, and
exchanging the data traffic with the server application over the second MPTCP sub-flow on the second ME host device;
changing the configuration of the first MPTCP sub flow to a not-available priority, wherein the not-available priority means that a subflow is maintained but no longer used for data traffic; and
closing any other MPTCP sub flow associated with the first ME host device.