Granted Patent B2

US 12,445,382 · App. 16/964,795 · Granted Oct 14, 2025

Inventors: Michelle Perras (Montréal, CA); Robert G. Gazda (Spring City, PA); Debashish Purkayastha (Collegeville, PA); Antonio de la Oliva (Madrid, ES)

Assignee: InterDigital Patent Holdings, Inc.

H04L47/24H04L45/24H04L47/193H04L69/14

Abstract

Claims (28)

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.

2. The method of claim 1 , wherein the second message comprises an MP_PRIO message.

3. The method of claim 1 , wherein the first message comprises an MP_JOIN message.

4. A wireless transmit/receive unit (WTRU) comprising:

a processor configured to communicate data traffic over a transmission control protocol (TCP) session with a multipoint transmission control protocol (MPTCP) stack running on the WTRU;

the processor configured to anchor to a first mobile edge (ME) host device;

the processor configured to exchange 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, wherein the regular priority means that a subflow is to be used now;

the processor configured to anchor to a second ME host device;

the processor configured to, responsive to anchoring to the second ME host device, receive a first message, from the second ME host device, indicating to the WTRU an establishment a second MPTCP sub-flow;

the processor configured to, 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;

the processor configured to, after the second MPTCP sub-flow is established, receive 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;

the processor configured to, responsive to the second message, change the configuration of the second MPTCP sub-flow from the pre-allocated priority configuration to the regular priority configuration, and

exchange the data traffic with the server application over the second MPTCP sub-flow on the second ME host device;

the processor configured to change 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

the processor configured to close any other MPTCP sub flow associated with the first ME host device.

5. The WTRU of claim 4 , wherein the second message comprises an MP_PRIO message.

6. The WTRU of claim 4 , wherein the first message comprises an MP_JOIN message.

Assignments (2)

Continuity (2)

References Cited (27)