Application mobility based on enhanced MPTCP
By configuring the MPTCP stack and sub-stream management of multi-ME host devices on the wireless terminal, the stability problem of URLLC connection in mobile devices is solved, and efficient mobility management in 5G communication is achieved.
Patent Information
- Application Number
- CN201980018379.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-01-26
- Filing Date
- 2019-01-25
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2039-01-25
AI Technical Summary
In mobile devices, existing technologies struggle to effectively maintain ultra-reliable and low-latency communication (URLLC) connections, especially when the device is in motion, where mobility management of the transport layer protocol stack presents challenges.
By configuring a Multipath Transmission Control Protocol (MPTCP) stack on the Wireless Terminal Unit (WTRU), and utilizing sub-stream management among multiple Mobile Edge (ME) host devices, data service switching and transmission can be achieved, ensuring communication reliability and low latency.
It achieves stability and reliability of URLLC connection maintenance in mobile devices, improves the mobility management capability of communication system, and adapts to the performance requirements of 5G wireless communication.
Smart Images

Figure CN111837371B_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 622,586, filed January 26, 2018, the contents of which are incorporated herein by reference. Background Technology
[0003] As wireless protocols and standards advance, new performance targets may arise from new use cases. For example, in 5G wireless communications, ultra-reliable and low-latency communication (URLLC) may be required. Example use cases could include autonomous vehicles performing collaborative and safety functions, monitoring and control of smart grids, haptic feedback for telemedicine procedures, control and coordination of unmanned aerial vehicles, robotics, industrial automation, and more. Therefore, it may be desirable to create and / or improve various capabilities, such as maintaining URLLC connectivity while devices are in motion. Summary of the Invention
[0004] A method, system, device, and WTRU are configured to handle the movement of the WTRU. A client application running on the WTRU is configured to transmit data traffic via a TCP session with an MPTCP stack running on the WTRU. This data traffic is exchanged with a server application via a first MPTCP sub-stream with a first mobile edge (ME) host device. The WTRU is anchored to a second ME anchor node. The WTRU receives a first message from the second ME host device instructing the WTRU to join a second MPTCP sub-stream with the second ME host device. The WTRU joins the second MPTCP sub-stream in response to the first message, wherein the second sub-stream is configured not to exchange data traffic. The WTRU receives a second message from the second ME host device configuring the second MPTCP sub-stream to exchange data traffic. The WTRU exchanges the data traffic with the server application via the second MPTCP sub-stream with the second ME host device. Attached Figure Description
[0005] A more detailed understanding can be obtained from the following detailed description given by way of example in conjunction with the accompanying drawings, wherein the same reference numerals in the drawings indicate the same elements, and wherein:
[0006] Figure 1A This is a system schematic diagram illustrating an exemplary communication system that can implement one or more of the disclosed embodiments;
[0007] Figure 1B It is shown that, according to the embodiment, it is possible to Figure 1AA schematic diagram of an exemplary wireless transmit / receive unit (WTRU) used within a communication system.
[0008] Figure 1C It is shown that, according to the embodiment, it is possible to Figure 1A The diagram shows an exemplary radio access network (RAN) and an exemplary core network (CN) used within the communication system.
[0009] Figure 1D It is shown that, according to the embodiment, it is possible to Figure 1A The diagram shows another exemplary RAN and another exemplary CN used within the communication system.
[0010] Figure 2 It shows a block diagram of an example standard TCP protocol stack and an example standard MPTCP protocol stack;
[0011] Figure 3 This is a block diagram illustrating a simplified example MEC topology;
[0012] Figure 4A This is a message sequence diagram illustrating an example scenario of losing connectivity during ME App mobility in a network;
[0013] Figure 4B To further explain in Figure 4A A message sequence diagram illustrating an example scenario of losing connectivity during ME App mobility in a network;
[0014] Figure 5A This is a message sequence diagram illustrating an example global view of the MPTCP stack mobility method;
[0015] Figure 5B To continue explaining Figure 5A Example global view of the MPTCP stack mobility method: message sequence diagram;
[0016] Figure 6 This is a sample message sequence diagram illustrating mobility subscription and triggering;
[0017] Figure 7A This is a message sequence diagram illustrating the preparation phase of an example MPTCP session transfer;
[0018] Figure 7B To continue explaining Figure 7A Example message sequence diagram of the MPTCP session transfer preparation phase;
[0019] Figure 8A This is a message sequence diagram illustrating the example MPTCP session transfer completion phase;
[0020] Figure 8B To continue explaining Figure 8A Example message sequence diagram of the MPTCP session transfer completion phase;
[0021] Figure 9 This is a bitmap illustrating an exemplary modified substream priority (MP_PRIO) option;
[0022] Figure 10 This is a bitmap illustrating an exemplary modified join (MP_JOIN) option;
[0023] Figure 11 This is a bitmap illustrating an exemplary modified join (MP_JOIN) option;
[0024] Figure 12A This is a message sequence diagram illustrating the example MPTCP session transfer preparation phase;
[0025] Figure 12B To continue explaining Figure 12A Example message sequence diagram of the MPTCP session transfer preparation phase;
[0026] Figure 13A This is a message sequence diagram illustrating the example MPTCP session transfer completion phase;
[0027] Figure 13B To continue explaining Figure 13A Example message sequence diagram of the MPTCP session transfer completion phase;
[0028] Figure 14 This is a bitmap illustrating an exemplary modified join (MP_JOIN) option;
[0029] Figure 15 This is a bitmap illustrating an exemplary modified join (MP_JOIN) option;
[0030] Figure 16 This is a bitmap illustrating an example of modifying the Add Address (ADD_ADDR) option;
[0031] Figure 17A This is a message sequence diagram illustrating an example of Network Address Translation (NAT) usage created by a PRE_ALLOCATED subflow initiated by a WTRU; and
[0032] Figure 17B It is a message sequence diagram, which continues to explain. Figure 17A Example Network Address Translation (NAT) usage created by the PRE_ALLOCATED substream initiated by WTRU. Detailed Implementation
[0033] Figure 1A This is a schematic diagram illustrating an exemplary communication system 100 that can implement one or more of the disclosed embodiments. The communication system 100 can be a multiple access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 can use one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail Unique Word DFT-Extended OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtering OFDM, and Filter Bank Multicarrier (FBMC), etc.
[0034] like Figure 1A As shown, the communication system 100 may include Wireless Transmit / Receive Units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, Core Network (CN) 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network components. The CN may represent a Next-Generation Core (NGC) network, such as a 5G system using New Radio (NR). Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, any of WTRUs 102a, 102b, 102c, and 102d can be referred to as a "station" and / or "STA," and can be configured to transmit and / or receive wireless signals. They can include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics, and devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d can be interchangeably referred to as a UE.
[0035] The communication system 100 may further include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to enable access to one or more communication networks (e.g., CN 106 / 115, Internet 110, and / or other networks 112) by wirelessly interfacing with at least one of WTRUs 102a, 102b, 102c, and 102d. For example, base stations 114a and 114b may be base transceiver stations (BTS), node B, e-node B, home node B, home e-node B, gNB, new radio (NR) node B, site controller, access point (AP), and wireless routers, etc. Although each of base stations 114a and 114b is described as a single component, it should be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network components.
[0036] Base station 114a may be part of RAN 104 / 113, and the RAN may also include other base stations and / or network components (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies called cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide radio service coverage for a specific geographic area that is relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., each transceiver corresponds to one sector of the cell. In embodiments, base station 114a may use multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, by using beamforming, signals can be transmitted and / or received in a desired spatial direction.
[0037] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116, wherein the air interface can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). Air interface 116 can be established using any suitable radio access technology (RAT).
[0038] More specifically, as described above, the communication system 100 can be a multiple access system and can use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, etc. For example, base station 114a in RAN 104 / 113 and WTRUs 102a, 102b, and 102c can implement a certain radio technology, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), wherein the technology can use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117. WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).
[0039] In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a certain radio technology, such as Evolved UMTS Terrestrial Radio Access (E-UTRA), wherein the technology may use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.
[0040] In an embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology that can establish an air interface 116 using a new radio (NR), such as NR radio access.
[0041] In this embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement various radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can jointly implement LTE radio access and NR radio access (e.g., using the dual connectivity (DC) principle). Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by various types of radio access technologies and / or transmissions sent to / from various types of base stations (e.g., eNBs and gNBs).
[0042] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement the following radio technologies, such as IEEE 802.11 (i.e., WiFi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate for GSM Evolution (EDGE), and GSM EDGE (GERAN), etc.
[0043] Figure 1A Base station 114b can be, for example, a wireless router, home node B, home e node B, or access point, and can use any suitable RAT to facilitate wireless connectivity in a local area, such as a business premises, residence, vehicle, campus, industrial facility, air corridor (e.g., for use by drones), and road, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can establish a wireless local area network (WLAN) by implementing radio technology such as IEEE 802.11. In another embodiment, base station 114b and WTRUs 102c, 102d can establish a wireless personal area network (WPAN) by implementing radio technology such as IEEE 802.15. In yet another embodiment, base station 114b and WTRUs 102c, 102d can establish a picocell or femtocell by using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). Figure 1A As shown, base station 114b can be directly connected to the Internet 110. Therefore, base station 114b does not need to access the Internet 110 via CN 106 / 115.
[0044] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, and 102d. This data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or can perform advanced security functions such as user authentication. Although in Figure 1AWhile not shown, it should be understood that RAN104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT or a different RAT as RAN 104 / 113. For example, in addition to connecting to RAN 104 / 113 which uses NR radio technology, CN 106 / 115 can also communicate with other RANs (not shown) that use GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technologies.
[0045] CN 106 / 115 can also act as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Simple Old-Style Telephone Service (POTS). The Internet 110 may include a global interconnected computer network equipment system using common communication protocols (e.g., TCP, UDP, and / or IP from the Transmission Control Protocol / Internet Protocol (TCP / IP) suite). Network 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, wherein the one or more RANs may use the same RAT or a different RAT as RAN 104 / 113.
[0046] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capability (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers communicating with different wireless networks on different wireless links). For example, Figure 1A The WTRU 102c shown can be configured to communicate with base station 114a using cellular-based radio technology, and with base station 114b using IEEE 802 radio technology.
[0047] Figure 1B This is a system schematic diagram illustrating an exemplary WTRU 102. (See attached diagram.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive unit 122, a speaker / microphone 124, a numeric keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or peripheral devices 138. It should be understood that, while remaining consistent with the embodiments, WTRU 102 may also include any sub-combination of the foregoing components.
[0048] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), and a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, and transceiver 120 can be coupled to transmitting / receiving unit 122. Although Figure 1B While the processor 118 and transceiver 120 are described as separate components, it should be understood that the processor 118 and transceiver 120 may also be integrated together in a single electronic component or chip.
[0049] Transmit / receive component 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmit / receive component 122 may be an antenna configured to transmit and / or receive RF signals. As an example, in another embodiment, transmit / receive component 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, transmit / receive component 122 may be configured to transmit and / or receive RF and optical signals. It should be understood that transmit / receive component 122 may be configured to transmit and / or receive any combination of wireless signals.
[0050] Although Figure 1B While the transmit / receive component 122 is described as a single component, the WTRU 102 may include any number of transmit / receive components 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive components 122 (e.g., multiple antennas) that transmit and receive wireless signals via the air interface 116.
[0051] Transceiver 120 can be configured to modulate signals to be transmitted by transmitter / receiver 122 and demodulate signals received by transmitter / receiver 122. As described above, WTRU 102 can have multimode capability. Therefore, transceiver 120 can include multiple transceivers that allow WTRU 102 to communicate using various RATs (e.g., NR and IEEE 802.11).
[0052] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a numeric keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit), and can receive user input data from these components. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Furthermore, the processor 118 can access and store information from any suitable memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 can include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 can include a subscriber identity module (SIM) card, memory stick, secure digital card (SD) memory card, etc. In other embodiments, the processor 118 can access and store information from memory that is not actually located in WTRU 102; for example, such memory could be located in a server or home computer (not shown).
[0053] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power for other components in the WTRU 102. The power supply 134 can be any suitable device that powers the WTRU 102. For example, the power supply 134 may include one or more dry cell battery packs (such as nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, and fuel cells, etc.
[0054] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. As a supplement or replacement to the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116, and / or determine its location based on signal timing received from two or more nearby base stations. It should be understood that, while remaining consistent with the embodiments, the WTRU 102 may acquire location information using any suitable positioning method.
[0055] The processor 118 can also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, the peripheral device 138 may include an accelerometer, electronic compass, satellite transceiver, digital camera (for photos and / or video), Universal Serial Bus (USB) port, vibration device, television transceiver, hands-free headset, etc. Modules, FM radio units, digital music players, media players, video game console modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and activity trackers, etc. The peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors, etc.
[0056] WTRU 102 may include a full-duplex wireless device, wherein the reception or transmission of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous for the wireless device. The full-duplex wireless device may include an interference management unit 139 that reduces and / or substantially eliminates self-interference by means of hardware (e.g., choke coils) or by means of a processor (e.g., a separate processor (not shown) or by means of processor 118) for signal processing. In embodiments, WTRU 102 may include a half-duplex wireless device that transmits and receives some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception).
[0057] Figure 1C This diagram illustrates a system schematic of RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.
[0058] RAN 104 may include eNodeBs 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of eNodeBs while remaining consistent with the embodiments. Each of eNodeBs 160a, 160b, and 160c may include one or more transceivers communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNodeBs 160a, 160b, and 160c may implement MIMO technology. Thus, for example, eNodeB 160a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.
[0059] Each of the eNodeB 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. For example... Figure 1C As shown, nodes B160a, 160b, and 160c can communicate with each other via the X2 interface.
[0060] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing components is described as part of the CN 106, it should be understood that any of these components may be owned and / or operated by an entity other than the CN operator.
[0061] The MME 162 can connect to each of the eNodeBs 162a, 162b, and 162c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, performing bearer activation / deactivation processes, and selecting a specific serving gateway during the initial attach process of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) using other radio technologies (such as GSM and / or WCDMA).
[0062] The SGW 164 can connect to each of the eNodeBs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 typically routes and forwards user data packets to / from WTRUs 102a, 102b, and 102c. Furthermore, the SGW 164 can perform other functions, such as anchoring the user plane during handover between eNBs, triggering paging processes when DL data is available to WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c, etc.
[0063] SGW 164 can be connected to PGW 146, which can provide packet-switched network (e.g., Internet 110) access for WTRUs 102a, 102b, and 102c to facilitate communication between WTRUs 102a, 102b, and 102c and IP-enabled devices.
[0064] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and conventional landline communication equipment. For example, CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), and the IP gateway may act as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRUs 102a, 102b, and 102c with access to the other network 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.
[0065] Although Figure 1A-1D The WTRU is described as a wireless terminal; however, it should be understood that in some representative embodiments, such a terminal may use a wired communication interface (e.g., temporary or permanent) with the communication network.
[0066] In a representative embodiment, the other network 112 may be a WLAN.
[0067] A WLAN employing an Infrastructure Basic Services Set (BSS) model may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may access or interface with a Distributed System (DS) or other types of wired / wireless networks that send traffic into and / or out of the BSS. Traffic originating outside the BSS and destined for a STA can be delivered to the STA via the AP. Traffic originating from a STA and destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send traffic to the AP and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between the source and destination STAs (e.g., directly therebetween) using Direct Link Establishment (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Channelized DLS (TDLS). For example, a WLAN using Standalone BSS (IBSS) mode does not have an access point (AP) and is located within the IBSS or the STAs using the IBSS (e.g., all STAs) can communicate directly with each other. Here, the IBSS communication mode is sometimes referred to as an "ad-hoc" communication mode.
[0068] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel (e.g., the primary channel). The primary channel can have a fixed width (e.g., a 20 MHz bandwidth) or a width dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by STAs to establish connections with the AP. In some representative embodiments, carrier-sense multiple access with collision avoidance (CSMA / CA) can be implemented (e.g., in an 802.11 system). For CSMA / CA, STAs, including the AP (e.g., each STA), can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can fall back. In a given BSS, at any given time, there is only one STA (e.g., only one station) transmitting.
[0069] High-throughput (HT) STAs can communicate using a 40MHz wide channel (e.g., by combining a 20MHz wide main channel with adjacent or non-adjacent 20MHz wide channels to form a 40MHz wide channel).
[0070] Very High Throughput (VHT) STAs can support channels with widths of 20MHz, 40MHz, 80MHz, and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels or by combining two non-consecutive 80MHz channels (this combination may be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, data is transmitted and passed through a segmented parser that splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed individually on each stream. The streams can be mapped onto two 80MHz channels, and the data can be transmitted by the STA performing the transmission. On the receiver of the STA performing the reception, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).
[0071] 802.11af and 802.11ah support sub-1 GHz operating modes. Compared to 802.11n and 802.11ac, 802.11af and 802.11ah utilize reduced channel bandwidth and carriers. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support instrument-type control / machine-type communication (MTC) (e.g., MTC devices in macro coverage areas). MTC devices may have certain capabilities, such as limited capabilities including support (e.g., only support) certain and / or limited bandwidths. MTC devices may include a battery with a battery life exceeding a threshold (e.g., for maintaining a very long battery life).
[0072] For WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah), these systems include a channel that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by a single STA, which is derived from all STAs operating in the BSS supporting the minimum bandwidth operating mode. In the example of 802.11ah, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes, the width of the primary channel can be 1MHz for STAs that support (e.g., only support) the 1MHz mode (e.g., MTC type devices). Carrier sensing and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy (e.g., because an STA (which only supports the 1MHz operating mode) is transmitting to the AP), then the entire available band can be considered busy even if most of the available band remains idle and available.
[0073] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.
[0074] Figure 1D This diagram illustrates a system schematic of RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.
[0075] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each of gNBs 180a, 180b, and 180c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may use beamforming to transmit and / or receive signals to and / or from gNBs 180a, 180b, and 180c. Thus, for example, gNB 180a may use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a. In embodiments, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In embodiments, gNBs 180a, 180b, and 180c may implement Cooperative Multipoint (CoMP) technology. For example, WTRU 102a can receive cooperative transmissions from gNB 180a and gNB 180b (and / or gNB 180c).
[0076] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable digital configurations. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can be different for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., containing different numbers of OFDM symbols and / or varying absolute durations).
[0077] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can use one or more of gNBs 180a, 180b, and 180c as mobile anchor points. In standalone configuration, WTRUs 102a, 102b, and 102c can use signals in unlicensed frequency bands to communicate with gNBs 180a, 180b, and 180c. In a non-standalone configuration, WTRUs 102a, 102b, and 102c communicate / connect with gNBs 180a, 180b, and 180c simultaneously with other RANs (e.g., eNodeBs 160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNodeBs 160a, 160b, and 160c, by implementing DC principles. In a non-standalone configuration, eNodeBs 160a, 160b, and 160c can act as mobile anchor points for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput to service WTRUs 102a, 102b, and 102c.
[0078] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support network slicing, dual connectivity, implement interoperability processing between NR and E-UTRA, route user plane data to User Plane Functions (UPF) 184a and 184b, and route control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.
[0079] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and may include Data Network (DN) 185a, 185b. The AMF 182a, 182b, UPF 184a, 184b, and SMF 183a, 183b may be the same or different types of devices, and the hardware of these devices may include processors, memory, transceivers, and other necessary data interfaces. In one example, the hardware of AMF 182a, 182b, UPF 184a, 184b, and SMF 183a, 183b may be similar to the hardware of the WTRU described herein. In another example, each of the AMF 182a, 182b, UPF 184a, 184b, and SMF 183a, 183b may include more than one device. Although each of the aforementioned components is described as part of CN 115, it should be understood that any of these components may be owned and / or operated by an entity other than a CN operator.
[0080] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different needs), selecting specific SMFs 183a and 183b, managing registration areas, terminating NAS signaling, and mobility management, etc. AMF 182a and 182b can use network slicing to customize the CN support provided to WTRU 102a, 102b, and 102c based on the service types used by WTRU 102a, 102b, and 102c. As an example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, and / or services for Machine-Type Communication (MTC) access, etc. AMF 182 can provide control plane functions for switching between RAN 113 and other RANs (not shown) using other radio technologies (e.g., LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi).
[0081] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and can configure traffic routing through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating WTRU or UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications, etc. PDU session types can be IP-based, non-IP-based, and Ethernet-based, etc.
[0082] UPF 184a and 184b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface, thus providing WTRU 102a, 102b, and 102c with access to a packet-switched network (e.g., Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring, etc.
[0083] CN 115 can facilitate communication with other networks. For example, CN 115 may include or can communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 115 and PSTN 108. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c can be connected to DNs 185a and 185b via the N3 interface connected to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and local data networks (DNs) 185a and 185b.
[0084] In view of Figure 1A-1D And about Figure 1A-1DThe corresponding descriptions herein refer to one or more of the following functions, which can be performed by one or more emulation devices (not shown): WTRU 102a-d, Base Station 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN185 ab, and / or one or more other devices described herein. These emulation devices can be one or more devices configured to simulate one or more of the functions described herein. For example, these emulation devices can be used to test other devices and / or simulate network and / or WTRU functions.
[0085] The simulation device can be designed to perform one or more tests on other devices in a laboratory environment and / or a carrier network environment. For example, the one or more simulation devices can perform one or more functions while being implemented and / or deployed, wholly or partially, as part of a wired and / or wireless communication network, to test other devices within the communication network. The one or more simulation devices can perform one or more functions while being implemented or deployed temporarily as part of a wired and / or wireless communication network. The simulation device can be directly coupled to other devices to perform tests, and / or can use over-the-air wireless communication to perform tests.
[0086] One or more simulation devices can perform one or more functions, including all functionalities, without being implemented or deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test laboratory and / or a test scenario where a wired and / or wireless communication network is not deployed (e.g., under test) to perform tests on one or more components. The one or more simulation devices can be test equipment. The simulation device can transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., the circuitry may include one or more antennas).
[0087] As discussed herein, the following abbreviations may be used: Branch Point (BP); Dual-Stack MIP (DSMIP); General Packet Radio Service (GPRS); GPRS Channelization Protocol (GTP); Mobile Edge (ME); Mobile Edge Computing, or equivalently, Multi-Access Edge Computing (MEC); ME Orchestrator (MEO); ME Platform (MEP); MEP Manager (MEPM); Mobile IP (MIP); Multipath TCP (MPTCP); Network Address Translation (NAT); Packet Data Unit (PDU); Proxy Mobile IP (PMIP); Access Point (PoA); Uplink Classifier (UL CL); User Plane Function (UPF); and Ultra-Reliable and Low-Latency Communication (URLLC). Furthermore, the orchestrator or MEO can be or includes a mobility controller entity within the edge or fog system that triggers ME App relocation across edge hosts. In the European Telecommunications Standards Institute (ETSI) MEC Reference Architecture, the orchestrator role can be implemented by the MEO, MEPM, MEP, or a combination of these MEC entities. ME App can be or includes applications (Apps) running on the network edge of the ME platform.
[0088] In some embodiments, application mobility (e.g., fast application mobility) can be achieved while maintaining a connection with a remote peer. This mobility can be implemented using MPTCP; for example, the MPTCP may be modified to support MPTCP session mobility.
[0089] MPTCP can include support for link failures, load balancing, and bandwidth aggregation. Multiple sub-flows can be created between two peers to support this. In some implementations, MPTCP can be used for other purposes, such as supporting application mobility while maintaining session connectivity between client applications and mobile edge (ME) applications. In some implementations, sub-flows can be created toward different hosts. For example, in such an implementation, multiple sub-flows can be created from a WTRU client application toward different destinations, resulting in an MPTCP session at the WTRU having a sub-flow toward a first peer and another sub-flow toward another peer associated with the same MPTCP session. In this case, a network architecture supporting multi-homing and session continuity can be assumed, for example, as provided by the 3rd Generation Partnership Project and / or the Internet Engineering Task Force (IETF). TM The network architecture defined by Distributed Mobility Management (DMM).
[0090] As discussed in this paper, redirection techniques can be used to maintain session continuity. For example, channelization protocols such as DSMIP, PMIP, or GTP can be used. In some cases, these protocols can be used to allow the WTRU to be reachable from the same IP address, even if the WTRU moves and attaches to one or more PoA or serving nodes. For example, in some implementations, data traffic is always directed to the anchor node that has already provided the WTRU with an IP address. If the WTRU moves from the anchor node to another node (e.g., a serving node), DL traffic can be channelized from the anchor node to the serving node and then provided to the WTRU from the serving node. Reverse paths can be used in the UL direction (i.e., WTRU to serving node, to anchor node, to corresponding node). In some cases, while channelization protocols can achieve session continuity, the resulting data path may not be optimal, for example, increasing latency.
[0091] Figure 2 This diagram illustrates an example of a standard application layer and TCP stack 200, as well as a block diagram of an example application layer and MPTCP protocol stack 240. Application layer and TCP stack 200 includes application layer 210 and a TCP stack, which includes TCP layer 220 and IP layer 230. Application layer and MPTCP protocol stack 240 includes application layer 250 and an MPTCP stack, which includes MPTCP layer 260, sub-stream layers 270 and 280, and IP layers 290 and 295.
[0092] MPTCP is an extension of TCP that allows hosts to use multiple paths (e.g., multiple IP addresses) to send and receive data belonging to a single connection. These multiple paths or substreams, used for various purposes within a TCP / IP session (e.g., simultaneous use), can improve resource utilization within the network and thus enhance the user experience, for example, through higher throughput and / or improved resilience (e.g., resilience to network failures). MPTCP operates at the transport layer and is transparent to both higher and lower layers. MPTCP can provide additional feature sets to applications that overlay the features of standard TCP, such as… Figure 2 As shown in the diagram, an MPTCP connection can include several TCP connections referred to as substreams. The MPTCP connection can manage the creation, removal, and utilization of these substreams for sending data. Note that while the example application layer and MPTCP protocol stack 240 show two substream layers 270, 280 (and associated IP layers 290, 295), an MPTCP connection can have fewer than or more than two substreams in various cases.
[0093] After an MPTCP connection has been established, additional substreams can be added to that connection. Hosts can know their own IP addresses and, for example, the IP addresses of other hosts through signaling exchange. If other paths are available, additional TCP sessions ("substreams") can be created on those paths, and these additional TCP sessions ("substreams") can be combined with existing MPTCP sessions. As shown in the example application layer and MPTCP protocol stack 240, the MPTCP layer will facilitate the MPTCP session continuing to behave as a single connection to both ends of the application, regardless of multiple substreams.
[0094] Some MPTCP implementations can take the input data stream from the application and divide it into one or more substreams. These substreams have sufficient control information to allow them to be reassembled and reliably and sequentially delivered to the receiving application. For example, MPTCP can add connection-level sequence numbers to allow the reassembly of segments arriving on multiple substreams with different network delays.
[0095] Some applications can store the IP addresses of TCP connections. Applications running on hosts that implement MPTCP (which are not configured to run on top of the MPTCP protocol) – “MPTCP unaware” applications – can track only the IP addresses of the first substream. Such applications can ignore the IP addresses used by other substreams.
[0096] Some MPTCP implementations can maintain MPTCP connections even if the original substream's IP address is no longer assigned to the host. In this case, the IP address exposed to applications unaware of MPTCP may differ from the address actually used by MPTCP. For example, if substream 270 is created first and later disconnected on the target host, MPTCP might only use IP address 295, while an application running on the target host unaware of MPTCP might believe it is using IP address 290. In other words, if substream 270 is created first and later disconnected on the target host, MPTCP might only use IP address 295, while IP address 290 is still exposed to applications running on the target host unaware of MPTCP.
[0097] In some cases, during the lifetime of an MPTCP connection, a deallocated IP address may be assigned to a different host. This can cause problems if the IP address is exchanged by multiple applications (e.g., within an application protocol). This problem can be addressed by enabling "fate sharing" (i.e., considering the initial substream and the MPTCP connection as a whole). In the fate sharing approach, if the initial substream is closed, the MPTCP session can also be closed. However, the fate sharing approach may sacrifice flexibility; for example, under such an approach, the MPTCP connection cannot be closed without closing the initial substream. The practicality of MPTCP can be reduced if the IP address of the first substream becomes unavailable, for example, due to a mobility event.
[0098] Figure 3 This illustrates an exemplary simplified MEC topology 300. The MEC can support user mobility and associated ME App migration between mobile edge instances. MEC support for ME App migration can include: (1) ME App instance relocation (i.e., virtual machine or container), where the complete ME App is migrated between MEP hosts (App state and executable), or (2) ME App state relocation, where a portion of the ME App state is migrated between MEC hosts. In either case, the ME App may follow the user. One benefit of following the user to move the ME App is providing the shortest possible data path, thereby keeping latency as low as possible. Additionally, compared to other methods (e.g., on channelization), fewer resources can be used in the network to serve WTRUs to maintain session continuity.
[0099] exist Figure 3 In the example MEC topology 300 shown, the application server (ME App 305) runs on the MEC node (Mobile Edge Host 310). ME App 305 is the server App that communicates with the client WTRU App 315 running on WTRU 320. An orchestrator is used to achieve application server mobility. The ME orchestrator MEO 325 (or ME Platform Manager (MEPM)) detects that WTRU 320 is moving away from ME host 310 and toward ME host 330. Therefore, MEO 325 prompts ME App 305 to move to the target ME host 330 as ME App 335, so that the ME App follows WTRU 320 either via ME App instance migration or via ME App state relocation.
[0100] DMM pushes mobility anchors to the edge of the network. In an MEC architecture, a Distributed Gateway (D-GW) logical entity can be placed at the network edge, close to mobile nodes. Multiple D-GWs can exist in a DMM domain and anchor mobility sessions of mobile nodes (e.g., WTRUs) attached to that domain. When a mobile node moves and performs a handover with a different attachment and anchor, the WTRU can acquire a new IP address. This can result in multiple IP addresses being assigned on the same interface. Session continuity for already running applications (i.e., before the handover to the new attachment and anchor) can be handled via data channelization between anchors. Already running applications can continue using the same IP address, and their traffic can be channelized to their anchor nodes. Newly launched applications (i.e., those launched after the handover to the new attachment and anchor) can be associated with a newly acquired IP address (from the new anchor), which can be directly anchored at the connected anchor node. This mechanism enables the selection of the shortest data path for new applications starting after the handover. Note that the IP address assigned to the WTRU and its associated D-GW IP address are stored in the core network (e.g., Home Subscriber Server (HSS) or Unified Data Management Server (UDM)) and are available to all D-GWs (i.e., anchor nodes).
[0101] The 5G core network can support PDU connectivity services (i.e., providing a service for PDU exchange between devices and the data network). A PDU session can be associated with multiple IPv6 prefixes. Such a session can be referred to as a multi-homed PDU session. This PDU session can provide access to the data network (DN) via more than one PDU (IPv6) anchor point. Different user plane paths to multiple IP anchor points can branch at a "common" user plane function (UPF), which is referred to as a UPF supporting "branch point" (BP) and / or "uplink classifier" (UL CL) functions. The branch point and uplink classifier can provide forwarding of UL traffic to different IP anchor points and merging of DL traffic to mobile devices (i.e., merging traffic from different IPv6 anchor points on the link to said device). Note that the co-location of the UL CL or branch point with the PDU session anchor point can be a deployment option.
[0102] 3GPP 5G requirements may include Ultra Reliable and Low Latency Communication (URLLC). Use cases for URLLC may include, but are not limited to, autonomous vehicles performing collaborative and safety functions, smart grid monitoring and control, haptic feedback for telemedicine procedures, control and coordination of unmanned aerial vehicles, robotics, industrial automation, and more. These use cases may require interactions with specific latency tolerances. For example, such use cases may require interactions with latency below a certain threshold, which may be referred to as, for example, low-latency interactions or very low-latency interactions. Such actions may not tolerate traffic being routed to a remote or "far-off" host using certain types of channelization methods, where latency exceeding the threshold would be introduced.
[0103] In some implementations, enhanced MPTCP methods can be used to address such use cases, for example, to enable rapid application mobility.
[0104] MEC supports application mobility, allowing application servers to "follow" a mobile device as it moves and connects to different access points and / or access networks, such as in a DMM as described above. For example, MEC can support moving an ME App from one ME host to another, as described above. Moving a ME App to follow a user can have advantages, for example, providing the shortest (or appropriately shortest) data path while attempting to keep latency as low as possible.
[0105] In the example scenario, the WTRU can connect to another PoA / anchor node and obtain a new IP address from the currently connected anchor while retaining its previously assigned IP address. Obtaining a new IP address from the currently connected anchor can have the advantage of achieving the shortest (or appropriately short) data path, for example, because mobility management processing (e.g., channelization) is not required when using the new IP address. However, the data path to the WTRU also depends on the location and / or anchoring of the corresponding node (i.e., the node communicating with the WTRU via the data path). For example, in the first case where the WTRU moves away from an ME App (peer) that remains in the same location (e.g., on a particular ME host) (e.g., moves to a different anchor), the data path between the client app on the WTRU and the ME App may be relatively longer than in the second case where the ME App moves to follow the WTRU (e.g., is transferred to an ME host closer to the WTRU). In the second case, assuming the new IP address is used, the data path can be shorter. To address this aspect of the data path, ME App mobility can be implemented to enable communication nodes to move closer to the WTRU and closer to their anchor nodes.
[0106] Since ME App mobility can be useful in addressing 5G use cases, note that MEC assumes the underlying network maintains connectivity between the mobile device and the edge application server when the edge application server is moved across ME hosts. Connectivity, as discussed herein, can refer to the TCP session established between a client application running on the WTRU and an application server running on the network side (e.g., on the ME host). Maintaining this TCP session (which is bound to a specific IP address associated with a specific network node) may be necessary to preserve connectivity.
[0107] If an application server (or ME App) running on an ME host is moved to another ME host, various connectivity issues may arise. From a connectivity perspective, ME App mobility can be handled differently depending on the circumstances.
[0108] Some ME mobility solutions may include a break-before-make approach using DNS redirection. In some examples, the ME App closes its TCP connection with its peer (i.e., the WTRU App) before moving to the new ME host. From this point on, no application data is exchanged between the WTRU App and the ME App. The WTRU App performs a DNS lookup for the ME App's URL, after which the WTRU App can be redirected to the new ME host via DNS redirection. A new TCP connection is established with the ME App now running on the new ME host, after which application data transfer between the WTRU App and the ME App can resume. In this break-before-make solution, the ME App follows the WTRU as needed; however, the break-before-make approach may result in a temporary loss of connectivity. This loss of connectivity may be unacceptable for applications with certain latency requirements (e.g., low-latency applications).
[0109] Some ME mobility solutions may employ a disconnect-then-reconnect approach without DNS redirection. In some examples, the MEApp closes its TCP connection before moving to the new ME host. From this point onward, no application data is exchanged between the WTRU App and the ME App. The WTRU App performs a DNS lookup for the specified ME App URL, but this lookup may not be immediately redirected, for example, because the ME host App URL is typically cached on the WTRU. Therefore, the WTRU App establishes a new TCP connection with the MEApp at its initial location. This reconnection can cause several problems. One example problem is that connectivity may be lost at some point, which may be unacceptable for applications with certain latency requirements (e.g., low-latency applications). Another example problem is that the ME App may still be running on the initial ME host, but the WTRU App session has been moved; therefore, application data transmission with the WTRU App may not continue from the point where the TCP connection was closed. A further example problem is that the ME App may no longer be running on the initial ME host and therefore may not re-establish communication with the WTRU App.
[0110] Some ME mobility solutions may include a disconnect-before-reconnect approach using application-specific communications. In some examples, the MEApp may notify the WTRU App, for example via application-specific communications, that it is moving or has moved to a new ME host. The IP address of the new ME host may be specified, and the WTRU App may close the initial TCP connection and establish a new TCP connection toward the new ME host. The WTRU App may not publish a DNS lookup, for example, because the information for reaching the new ME host (i.e., the new IP address) can be provided by the ME App via proprietary signaling (e.g., at the application layer). In this solution, connectivity is lost for a period of time. This loss of connectivity may be unacceptable for applications with certain latency requirements (e.g., low-latency applications). Such solutions involve the WTRU App participating in ME App mobility, which may be undesirable because it may require all apps supporting ME App mobility to be updated to support ME App mobility.
[0111] Some ME mobility solutions may include using an ME orchestrator (e.g., MEO, MEPM, and / or MEP) to employ a drop-before-connect approach. In some examples, the orchestrator may notify the WTRU App that the ME App is moving or has moved to a new ME host. The orchestrator may transmit the new ME host IP address to the WTRU App, after which the WTRU App may close its initial TCP connection and establish a new TCP connection toward the new ME host. The WTRU App may not publish a DNS lookup, for example, because the information used to reach the new ME host (i.e., the new IP address) is provided by the orchestrator. In this solution, connectivity is lost for a period of time. This loss of connectivity may be unacceptable for applications with certain latency requirements (e.g., low-latency applications).
[0112] Some ME mobility solutions employ a make-before-break approach using application-specific or orchestrator communications. In some examples, the ME App or orchestrator may notify the WTRU App that it is moving or has moved to a new ME host. Subsequently, the WTRU App can establish a new TCP connection to the new ME host, in addition to the existing TCP connection with the ME App running on the initial ME host. The ME App or orchestrator may notify the WTRU App when it is ready to receive data at its new location (i.e., the new ME host). At or after this time, the WTRU App and ME App can begin using the new TCP connection for data transfer, and the WTRU App can close the initial TCP connection. Such solutions involve the WTRU App participating in ME App mobility, which can be undesirable as it may require all apps supporting ME App mobility to be updated to support it. Furthermore, when the new TCP connection begins to be used (i.e., both ME App applications are running concurrently), the initial ME App and the new ME App may need to be synchronized. For example, sequence numbers may need to be synchronized. Such synchronization issues can impose new requirements on the ME App side, such as requiring further updates to such ME Apps.
[0113] Some ME mobility solutions may include session continuity achieved through channelization. In some examples, the ME App can be moved to a new ME host, and a mobility support service running on that ME host can establish a channel between the initial ME host and the target ME host, allowing the TCP connection to be preserved. The WTRU App may be unaware of the ME App relocation and can continue to send traffic with the initial ME host via the TCP connection. The initial ME host acts as a branch point or service node, redirecting UL traffic from the WTRU to the new ME host and DL traffic from the new ME host to the WTRU. Channeling (e.g., PMIP or GTP) can be used between the initial ME host and the new ME host for this purpose. Such a solution can preserve the TCP connection without data transmission interruption; however, latency may increase, for example, because the channelization requires encapsulating data packets and results in a longer data path. This increased latency may be unacceptable for applications with certain latency requirements (e.g., low-latency applications). This may conflict with some objectives of moving the ME App to the WTRU, such as maintaining the shortest possible data path and keeping latency as low as possible.
[0114] Some ME mobility solutions may include using a middlebox to handle connectivity between the WTRU and the ME App server. In some implementations, the middlebox is a device used to transform, inspect, filter, or otherwise manipulate data packets or other services for purposes other than packet forwarding. The middlebox can be used to isolate WTRU App and ME App mobility events; however, maintaining connectivity can be problematic. For example, the middlebox may need to establish a new TCP connection with the ME App on a new ME host and associate that new connection with an existing session of the WTRU App. Such a process may introduce latency, which may be unacceptable for applications with certain latency requirements (e.g., low-latency applications) and / or may not meet the latency requirements of 5G use cases.
[0115] As discussed above, by moving the ME App to another ME host, existing TCP sessions may no longer be used to reach the ME App (except in channelized scenarios) because the IP addresses associated with the existing TCP sessions are still addressing the initial ME host. Therefore, connectivity may be lost until a new TCP session is established between the client application (or middleware) and the ME App on the new ME host, introducing unacceptable latency and / or delays for applications with certain latency requirements (e.g., low-latency applications).
[0116] Applications that require limited latency interactions (e.g., very low latency interactions) and applications that require TCP session continuity (e.g., for long-running sockets) may not tolerate delays or latency associated with DNS redirection, TCP connection timeouts, and / or TCP connection reconstruction.
[0117] Figure 4 is a message sequence diagram illustrating an exemplary signaling between WTRU 400, first ME host 403, ME orchestrator MEO 406 (or ME platform manager MEPM), and second ME host 409, for an exemplary scenario of loss of connectivity during ME App mobility within a network. In this example, WTRU App 410 starts on WTRU 400, and ME App 413 starts on ME host 403. A first TCP connection 416 is established between WTRU App 410 and ME App 413. In operation 419, WTRU 400 moves (e.g., moves in space). MEC ME App mobility can be used to facilitate ME App "following" WTRU 400 (i.e., relocation or otherwise execution on a different ME host closer to a new location than WTRU 400). Here, MEO 406 detects (e.g., as described above) that WTRU 400 is moving in step 420 and triggers a transfer of ME App to the new ME host 409 as ME App 421. After step 420, the ME App running on (or previously running on) ME host 403 now runs as ME App 421 on ME host 409.
[0118] MEC can assume connectivity is maintained, for example, as described in the following examples. Example cases (a), (b), (c), and (d) each occur after ME App 421 on ME host 409 has started. In the first example case (a), during operation 430, the TCP connection to the ME App at ME host 403 may be lost or closed, for example, as a result of the ME App being moved to ME host 409. In case (a), WTRU App 410 can detect the loss of the TCP connection to the ME App at ME host 403 and can perform a DNS query in operation 435 to obtain the IP address of the ME App relocated to ME host 409. Note that the DNS query in operation 435 may add delay to the connectivity rebuild time.
[0119] In alternative scenario (b), in step 437, the WTRU App 410 executing on WTRU 400 may be notified (e.g., by MEO 406 or the ME App executing on ME host 403) to continue data transfer with the ME App 421 running on the new ME host 409. The ME App 410 may be provided with a new IP address for the ME App 421 executing on ME host 409, for example, by MEO 406 or the ME App executing on ME host 403. However, this involvement of WTRU App 410 in the ME App transfer may present various problems, as previously discussed. In operation 439, the TCP connection with the ME App at ME host 403 may be lost or closed.
[0120] In example case (c) (following case (a) or case (b)), WTRU 400 initiates a new TCP session 445 with ME host 409 in operation 440. The connectivity is lost, and data transmission is interrupted until a new TCP connection is established with ME host 409.
[0121] In example case (d), during operation 450, channelization between the initial ME host 403 and the target ME host 409 can be used to handle ME App mobility support. In this example, during operation 419, WTRU 410 has moved to ME host 409; however, the TCP connection between the WTRU App and the ME App executing on ME host 403 can be maintained by establishing channel 459 between ME host 409 and ME host 403. Here, for example, UL data 453 from WTRU 400 for the IP address of the ME App executing on ME host 403 is first transmitted to ME host 409 (assuming ME host 409 is the first hop of WTRU) and forwarded to ME host 403 via the usual IP route. ME host 403 then channelizes the UL data 453 to ME host 409 via channel 459. Maintaining TCP connectivity in this way may require data to always propagate through the initial ME host, resulting in longer data paths and increased latency / delay. Such a solution can maintain TCP connections without data transmission interruptions; however, latency may increase, for example, because the channelization requires encapsulating and decapsulating data packets, resulting in longer data paths. This increased latency may be unacceptable for applications with certain latency requirements (e.g., low-latency applications). This may conflict with some objectives of moving ME Apps to WTRU, such as maintaining the shortest possible data path and keeping latency as low as possible.
[0122] It may be desirable to maintain connectivity between a client app (e.g., a WTRU app) and the ME app while meeting latency requirements, such as a maximum latency threshold (e.g., a maximum latency threshold for 5G or another use case), when the ME app (instance or state) transitions between ME hosts. Here, ME app transition may involve creating a new instance of the ME app on the target ME host and configuring that new instance with the state of the ME app currently running on the initial ME host. In some cases, the ME app may already be running on the target ME host; in such cases, the ME app may not need to be re-instantiated but can be reconfigured with the state of the ME app currently running on the initial ME host. It is also desirable to establish a direct connection between the WTRU app and the ME app at its new location (ME host) when the WTRU app is not involved in ME app mobility operations.
[0123] Therefore, the MPTCP protocol can be used by WTRU and ME hosts to maintain connectivity and meet latency requirements, while the WTRU App does not necessarily need to participate in ME App mobility operations. Multiple TCP sessions are grouped under the protection of a single MPTCP session (i.e., using the concept of substreams), which is transparent to the application (e.g., without the application's involvement). In such an implementation, the MPTCP session can appear as a regular TCP session to the application. Therefore, ME App migration can be supported using MPTCP sessions by allowing the creation of additional MPTCP substreams (i.e., another TCP session) toward the new ME App instance (either the new ME App instance or the ME App instance on the target ME host) and allowing traffic to be redirected to that new connection once the ME App migration is complete. This allows data transmission to be uninterrupted, latency to be maintained, and the application migration to be transparent to the client application, which continues to send data to the same connection (i.e., the TCP connection). By intercepting the application's regular TCP session, the MPTCP stack allows the application to continue its TCP session as if it were using the same TCP connection, even if the MPTCP substreams (their own TCP connections) are modified below the MPTCP layer. In some implementations, the target ME host (e.g., selected by MEO or MEPM) can be selected before triggering the ME App migration and MPTCP session migration.
[0124] In some embodiments, MPTCP can be implemented on the WTRU (or the MPTCP agent on the middlebox) and the ME host to overcome various connectivity issues, such as those discussed above. However, such an approach may lead to other problems. For example, the MEC may expect ME App migrations to be handled by the MEO or MEPM (e.g., where an ME application instance is moved to a new ME host or the state of an ME application is transferred to a new ME host); however, the MEO (or MEPM or MEP) may not be aware whether the ME application is TCP-based and whether MPTCP was used on the previous ME host. Furthermore, when using MPTCP, the orchestrator or PM may not know which MPTCP session is being used and should be migrated to the new ME host. Additionally, MPTCP may need to be modified to support MPTCP session migrations.
[0125] Therefore, the ME App mobility approach can focus on ME App relocation, while the MPTCP approach can be transparent to the application. The MPTCP stack can create an MPTCP session using one or more substreams (i.e., TCP sessions), where the application may be unaware of the MPTCP session and substream creation / use. Therefore, in some implementations, MPTCP stack transfers (which may be necessary for the ME App) are not handled by the ME application itself. In some cases, even if the ME App is MPTCP-aware in some sense (e.g., the ME App knows MPTCP is running and can configure the MPTCP stack via API to control some of its behavior), the ME App may be unaware of the MPTCP stack internals. Therefore, in some implementations, MPTCP stack transfers are also not handled by the MPTCP-aware ME App. In some cases, the orchestrator may not know whether the ME App implements MPTCP. Therefore, it may be necessary to inform the orchestrator (ME) whether the ME host is using MPTCP and whether the ME App is TCP-based, so that the MPTCP stack can be moved to the new ME host along with the ME App.
[0126] MPTCP may need to support migrating existing MPTCP sessions to a new MPTCP stack instance and adapting that MPTCP session to a new host. In other words, the MPTCP stack may need to be configured or started using information about existing MPTCP sessions. An MPTCP session may need to be migrated from one ME host to another while maintaining connectivity with the WTRU peer and preserving the socket information linking the MPTCP stack to the associated ME App. Adapting the target MPTCP stack may include adapting the MPTCP session number to other existing MPTCP sessions (e.g., ensuring that the target MPTCP session's session number does not copy a session number already used by another MPTCP session).
[0127] The transfer of the MPTCP session and related information (e.g., including session identifiers, associated peer IP addresses, security keys, sequence numbers, etc.) may also need to be supported.
[0128] Therefore, in some implementations, the API can be used to enable another application (e.g., MEO / MEPM / MEP) to obtain or set MPTCP stack session information details, which may be necessary to support ME App-follow-WTRU (i.e., to a new ME host) mobility scenarios. In some implementations, direct communication can be provided between two MPTCP server instances, allowing MPTCP session transfer. In some implementations, MPTCP can be modified so that an MPTCP session can involve more than two peers (i.e., it can involve substreams with different peers associated with the same MPTCP session). In some implementations, socket descriptors can be transferred to a new host and can be adapted to existing sockets.
[0129] For some applications, certain latency targets may be required in 5G networks (e.g., latency below a desired threshold, or "very low latency"). In some implementations, migrating application servers (or web applications) to follow their users (e.g., a WTRU moving away from one ME host and closer to another ME host) while maintaining session continuity can make it possible to meet these requirements.
[0130] Some embodiments provide MPTCP session mobility, allowing an ME App to be moved to another ME host while maintaining connectivity between the ME App and its corresponding client application (e.g., a client application running on a WTRU) and maintaining low latency. In some implementations, ME App mobility allows an application server (e.g., an application server running on an ME host) to remain (e.g., physically) close to a mobile device (e.g., a WTRU), thereby enabling the use of the shortest data path in the network. This mobility, used in conjunction with TCP session persistence for WTRU applications using enhanced MPTCP (e.g., enhanced MPTCP as discussed herein), can reduce or minimize latency.
[0131] In some embodiments, MPTCP session transfer adds little or no delay to the application relocation process. For example, an ME application may pause data transmission while relocating to a target ME host and then resume data transmission after the relocation is complete. In some implementations, after the ME App relocation is complete, Enhanced MPTCP has already moved the MPTCP session. Therefore, application data can be immediately exchanged between the corresponding WTRU App and the ME App executing on the target ME host. In some implementations, such as those discussed further herein, MPTCP session transfer can reduce the total time required for ME App relocation and data transmission continuation.
[0132] In some embodiments, MPTCP can resolve various connectivity issues. For example, MPTCP can be used to help maintain session continuity between the WTRU App and the ME App during and after the transfer of the ME App to a new ME host. In some implementations, this MPTCP-facilitated ME App transfer and subsequent connectivity may be transparent to the WTRU App, and the ME App transfer and / or connectivity support may not require the involvement of the WTRU App, although in some implementations, an MPTCP stack running on the WTRU may be involved.
[0133] In some embodiments, the MPTCP session can be mobile, wherein the MPTCP session with the initial ME host (i.e., the session between the WTRU and the initial ME host) can be moved to the target ME host (i.e., such that the MPTCP session is between the WTRU and the target host). Various methods for such MPTCP session mobility are possible. In such methods, the MPTCP stack running on the WTRU can be modified as discussed herein.
[0134] In some embodiments, a third-party application (e.g., an orchestrator) may use one or more APIs that are natively provided on the ME host to obtain the MPTCP configuration and configure the target MPTCP instance (i.e., the MPTCP instance on the target ME host) with an existing MPTCP session (i.e., the MPTCP session on the initial ME host).
[0135] In some embodiments, new MPTCP messages can be used to facilitate MPTCP session transfers using mutual communication between MPTCP instances. In this case, some MPTCP instances may be "special" MPTCP peers. In this case, application communication paths may not be created, and application data traffic may not be exchanged between specific MPTCP peers—instead, MPTCP-specific information is exchanged between MPTCP instances. Typical (i.e., non-special) MPTCP peers may include, for example, applications with "client-server" roles. Such applications can run on top of the MPTCP stack that handles the transport of application traffic. However, using the various methods described herein, traffic may include server-to-server communication for MPTCP transfers, where this traffic is transparent to the "client" peers.
[0136] In some embodiments, an MPTCP session may have more than two active MPTCP peers (e.g., it may include the WTRU, the current ME host, and the target ME host). Therefore, in some embodiments, substreams can be created between the MPTCP session and more than one different peer. This communication between multiple peers can be transparent to the WTRU MPTCP stack and, in some implementations, can be achieved by using the same security key on both peers (e.g., on both ME hosts—the initial and the target ME hosts). In some embodiments, the MPTCP stack can be adapted to a new ME host environment. For example, the MPTCP stack can be transparently adapted to the MPTCP session user (e.g., the ME App), who can continue to use the same socket number to send and receive data to and from the WTRU App. In some embodiments, the MPTCP session can be preserved even if its initial substream is dropped or otherwise unavailable. This can have the advantage of avoiding fate-sharing solutions that may break connectivity and increase latency.
[0137] Note that while various embodiments are described herein with respect to a particular type of network for convenience and ease of description, the embodiments discussed herein are not limited to a particular type of network and can be employed in the context of any suitable communication system.
[0138] Table 1 shows a comparison of the following two methods at each step of the relocation: a TCP-based method for relocating an example application from the initial ME host to the target ME host, and an enhanced MPTCP-based method for the same relocation. For each method, statements marked (-) emphasize stages where application data may not be exchanged, while statements marked (+) emphasize stages where application data can be exchanged.
[0139] Table 1
[0140]
[0141] Figure 5 is a message sequence diagram illustrating exemplary communication between WTRU 500, first ME host 503, MEO 506 (or MEPM), and second ME host 509 in an exemplary case of managing ME App mobility using an enhanced MPTCP method. This example implements MPTCP stack mobility, where the ME App and MPTCP session are transferred to the new ME host.
[0142] As illustrated in Figure 5, MPTCP can be used on devices and application server nodes to support application server mobility. This support may involve the creation of more than just new MPTCP substreams / paths. Instead, a new MPTCP instance (or a current MPTCP instance that can continue execution) can be adapted to the new ME host and utilize new substreams, using an already active MPTCP session.
[0143] As used herein, "Orchestrator" can be considered a general term to refer to the ME Platform Manager (MEPM) or ME Platform (MEP) entity. For simplicity, as discussed herein and illustrated in the figures, the ME Orchestrator, MEPM, and sometimes the MEP may be specified in the same box; however, for example, terms related to... Figure 3 The corresponding architecture is shown and described. In this case, entities that interact directly with the MPTCP stack via the socket API can run on the same ME host and can therefore be assumed to be MEP entities. In this case, the interaction between the MEP, MEPM, and MEO can pass information to the MPTCP instance running on the target ME host.
[0144] The message sequence diagram in Figure 5 is shown and described in three parts, A, B, and C. Part A describes the operations prior to the WTRU 500 move, Part B describes the MPTCP session transfer preparation operations after the WTRU 500 begins its move, and Part C describes the MPTCP session transfer completion operations related to the MEApp transfer.
[0145] In part A of Figure 5, WTRU 500 begins running WTRU App 510, which communicates 520 with (or will communicate with) a network-based App running at the network edge (i.e., ME App 513 on ME host 503). MPTCP stack 516 runs on WTRU 500, and MPTCP stack 519 runs on ME host 503, where MPTCP stack 516 and MPTCP stack 519 are MPTCP peers. MPTCP can be transparent to the App; however, in some implementations, an application aware of MPTCP can be used on either device. WTRU App 510 can use socket interface 511 to create a TCP session, and MPTCP stack 516 intercepts this socket request. Therefore, MPTCP session 523 is created, and a TCP substream 526 handling the transmission of data traffic 529 is created between the two MPTCP stacks 516 and 519. Depending on the number of interfaces used on the WTRU 500 and ME host 503, and the number of IP addresses assigned to each of them, many sub-flows can be created between the WTRU 500 and ME host 503. For simplicity, only one sub-flow is shown in Figure 5.
[0146] Regarding part B, WTRU 500 moves, initiating handover 530. During handover 530, WTRU 500 attaches to another PoA and becomes anchored to another anchor node in the network, where the network supports session continuity as discussed here. WTRU obtains a new IP address from the new anchor point while retaining the IP address already in use and associated with subflow 526.
[0147] After switchover 530, the data path for substream 526 is longer than before switchover 530 because, after switchover 530, data service 529 is forwarded from WTRU 500 to ME host 503 via ME host 509. In this example, data service 529 is channelized between two anchor points; that is, it is channelized between the currently connected ME host 509 and the previously connected ME host 503 via channel 533. In step 536, MEO 506 is notified (e.g., by network notification, e.g., MEO 506 may register with the network to be notified when the WTRU moves / switches to another PoA / anchor point) of the movement of WTRU 500 and determines that MEApp 513 should be moved to another ME host to "follow" (i.e., physically closer to) the WTRU.
[0148] ME App mobility can be used to maintain the shortest data path between WTRU App 510 and ME App 513, for example, to achieve better data delivery performance. Additionally, compared to other methods, such as those based on channelization to maintain session continuity, fewer resources can be used in the network to serve the WTRU.
[0149] In step 539, to prepare for the ME App transfer and maintain the connectivity, the orchestrator triggers MPTCP session transfer preparation. During step 539, information (e.g., security keys, tokens, sequence numbers, etc.) is transferred to the target MPTCP stack 540 running on the target ME host 509, enabling the creation of a new sub-stream 543 associated with the existing MPTCP session 523 (i.e., MPTCP stack 516) on the WTRU 500 before the transfer of ME App 513 and MPTCP session 523 is completed. The new sub-stream 543 is pre-allocated (e.g., it can be created with the priority PRE_ALLOCATED) and is not used for data traffic at this point. Creating the sub-stream 543 with the target ME host 509 in this way facilitates data traffic between the target ME host 509 and the WTRU 500 as soon as possible after the ME App and MPTCP session relocation is completed, without interrupting data traffic between the WTRU App 510 and the ME App.
[0150] The IP address of the WTRU 500 created by the MPTCP stack 540 on ME host 509 for substream 543 can be the IP address assigned by the current anchor node during handover 530. In this example, the anchor node can access the WTRU's connectivity information, as previously discussed regarding DMM. This connectivity information can be made available to MEO 506, for example, to configure the MPTCP stack 540. The IP address assigned to the WTRU 500 by the current anchor node can be provided to the MPTCP stack 540 as part of the MPTCP session transfer process.
[0151] Substream 543 can be created using MPTCP messages exchanged between MPTCP stacks 516 and 540. MPTCP stack mobility can be transparent to MPTCP stack 516. Therefore, MPTCP stack 516 may not be aware that it is communicating with MPTCP stack 540 instead of MPTCP stack 519.
[0152] At the end of section B, substream 526 is used to transmit data service 529 between WTRU App 510 and ME App 513; however, this data path is now much longer than before switchover 530. This is because the "first hop" of the WTRU, or the entry point in the network, is now ME host 509, so data service 529 must travel from WTRU 500 through ME host 509 and then be routed to its destination as usual (in this case, ME App 513 running on ME host 503). The same path is used in the DL direction. Various aspects of the preparation steps (e.g., step 539) are further described herein.
[0153] Regarding part C, in step 546, MEO 506 triggers a transfer from ME App 513 to ME host 509 (where the transferred ME App is referred to as ME App 549). In step 550, MEO 506 triggers the completion of an MPTCP session transfer from MPTCP stack 519 to MPTCP stack 540. After the session transfer is completed, in step 550, MPTCP stack 540 on ME host 509 changes substream 543 from a pre-allocated state to a regular state (e.g., changing the priority from "PRE_ALLOCATED" to "REGULAR"). MPTCP stack 540 also (e.g., using the same MPTCP message) changes substream 526 to an unavailable state (e.g., changing the priority to "NOT_AVAILABLE"). In this example, changing substream 526 to an unavailable state triggers the use of substream 543 for data service 529 between WTRU App 510 and the relocated ME App 549. Note that substream 526 and substream 543 cannot transmit data simultaneously (i.e., they cannot both be in a normal state at the same time); however, the initial substream 526 can be reserved (e.g., in an unavailable state).
[0154] On the initial ME host 503, only the initial substream 526 is maintained and set to unavailable (e.g., its priority is set to NOT_AVAILABLE). If there are other substreams from the ME host 503, they are shut down. For example, if a redundant or standby (e.g., a substream with the priority "BACKUP") is configured between the WTRU 500 and the ME host 503 (i.e., to provide a standby or redundancy for substream 526), that substream is shut down before substream 543 is changed to its normal state.
[0155] In the example of Figure 5, the initial sub-stream 526 can be maintained even if it may not be used for data transmission, for example, to support an application on the WTRU, which has already associated the IP address of the initial sub-stream with the session or application. Therefore, to preserve the MPTCP session and avoid fate-sharing behavior, the initial sub-stream 526 can be retained, and its associated IP address can remain assigned to the WTRU until the MPTCP session is closed. During exceptional periods when it is no longer necessary to retain the initial sub-stream 526, it can be closed instead of remaining unavailable or otherwise altering its state.
[0156] After completing part C, WTRU App 510 can continue to send and receive data services 529 as usual, unaware of the new data path or ME App relocation, and the MPTCP session transfer can be considered complete. Further details of this completion, as well as other aspects of the example in Figure 5, are described further herein.
[0157] Note that MPTCP session relocation is performed only on those MPTCP sessions used by the moved ME App 513 (i.e., moved to ME host 509 as ME App 549). Any other MPTCP sessions (not shown) handled by the MPTCP stack 519 on ME host 503 are unaffected by the move and relocation. However, note that multiple MPTCP sessions can be moved simultaneously, following the same procedure described for a single MPTCP session.
[0158] Figure 6 This is a message sequence diagram illustrating example communication between WTRU 600, first ME host 603, and MEO 606 (or MEPM or MEP), showing example mobility subscription and triggering. Part A relates more specifically to mobility subscription, and Part B relates more specifically to triggering. Parts A and B will be discussed in more detail below. In this example, MEO 606 is aware of the mobility of WTRU 600 and, based on the WTRU's mobility (e.g., obtained from the network as described herein), determines whether MEApp 613 should be moved from ME host 603, and determines which target ME host MEApp 613 should be moved to. MEO 606 also determines which target ME host. While an orchestrator (which is MEO, MEPM, MEP, or any combination of these) as discussed herein can be responsible for mobility and triggering, the concepts involving orchestrators discussed herein can be performed by another entity serving this function.
[0159] ME App 613 may know whether it is TCP-based, but it may not be aware of WTRU 600's MPTCP usage (i.e., MPTCP stack 616). In some examples, MPTCP is transparent to ME App 613. Example implementations involving applications aware of MPTCP are described later.
[0160] The ME App can subscribe to receive client (i.e., WTRU)-related mobility events from the MEO 606. During this step, the ME App 613 can provide information (e.g., ME App identifier and WTRU identifier information) to the MEO 606. This information enables the orchestrator to map the specific WTRU identifier associated with the mobility event to the ME App. The MEO 606 thus has sufficient information to trigger the ME App mobility process.
[0161] MEO 606 may also need to determine whether the MPTCP session is being used by ME App 613. If so, the MPTCP session must also be transferred to the target ME host. Multiple MPTCP sessions may exist between ME App 613 and WTRU App 610 (e.g., multiple MPTCP sessions for different service types). If this is indeed the case, all of these MPTCP sessions must be transferred to the target ME host.
[0162] Therefore, in addition to the parameters specified above (i.e., the ME App identifier and the WTRU identifier), the socket descriptor used by ME App 613 for WTRU 600 can be specified by its type (e.g., TCP or UDP). In some examples, if UDP is specified, MPTCP is not used. Therefore, MEO 606 can ignore connectivity (UDP is connectionless). If TCP is specified, the socket descriptor can correspond to the MPTCP session identifier (e.g., the same as it), and it can be assumed that MPTCP has been started on the host and is automatically used when the TCP socket is opened. MEO 606 then uses this identifier to trigger an MPTCP session transfer, as discussed here.
[0163] Based on the mobility subscription from ME App 613, MEO 606 can determine, based on the socket descriptor, whether an MPTCP session must be transferred when WTRU mobility is detected, and which MPTCP session to transfer.
[0164] about Figure 6 The described subscription and notification steps are an example of how socket descriptors are passed to the orchestrator. In some implementations, the socket descriptor may be passed in other ways without affecting the MPTCP session transfer process, as discussed here.
[0165] Figure 6 Part A describes the subscription in more detail. Here, WTRU App 610 is launched on WTRU 600. WTRU App 610 intends to participate in communication 620 with a server (such as ME App 613 running on ME host 603). MPTCP stack 616 runs on WTRU 600, and MPTCP stack 619 runs on ME host 603. WTRU App 610 can create TCP sockets 611 to communicate with ME App 613 via a TCP connection. Since MPTCP stack 616 runs on WTRU 600, it can intercept socket requests and create an MPTCP session 623 with ME host 603 (i.e., via MPTCP stack 619). TCP substream 626 is created to handle data traffic 629 between WTRU App 610 and ME App 613 (i.e., between the client and server sides of the application). In this example, ME App 613 supports host relocation and sends a subscription 640 to MEO 606 to receive notifications of mobility events. This subscription (or related communication) may include information about the protocol (e.g., "proto_TCP") used by ME App 613 to communicate with WTRU App 610 and the corresponding socket descriptor (e.g., "sockfd").
[0166] Figure 6 Part B describes the triggering process in more detail. Here, MEO 606 receives mobility event 645 from WTRU 600. Since ME App 613 has subscribed to this event for that specific WTRU (i.e., WTRU 600), MEO 606 sends notification 650 to MEApp 613. MEO 606 also triggers an MPTCP session transfer in step 655 using the socket descriptor (e.g., "-sockfd") parameter received at the subscription time. The MPTCP stack can use the socket descriptor parameter to determine which MPTCP session needs to be transferred, for example, as further described here.
[0167] In some embodiments, MPTCP session transfer can be implemented using different methods. In a first example method, the transfer may be handled by an orchestrator using the socket API. In a second example method, the transfer may be handled via direct communication between the current MPTCP stack and the target MPTCP stack. Such methods are described in further detail herein. Both methods will be described using, for example, an orchestrator to trigger the MPTCP session transfer. To trigger an MPTCP session transfer, in some examples, the orchestrator must know the socket file descriptor that identifies the MPTCP session to be transferred. In the examples herein, it is assumed that the orchestrator obtains this information from the ME App during a mobility event subscription, for example, as previously described. However, note that in some embodiments, the orchestrator may obtain this information in another suitable manner.
[0168] Multiple MPTCP sessions used by the WTRU App may need to be moved; therefore, multiple MPTCP sessions may need to be moved. In such cases, in some implementations, the same mobility process is repeated multiple times, either sequentially or in parallel. Alternatively, in some implementations, a single procedure can be used to move multiple sessions simultaneously or concurrently.
[0169] For example, as shown and described with respect to section B of Figure 5, the orchestrator can trigger a preparation phase for MPTCP session relocation prior to ME App relocation. During the preparation phase, if the MPTCP stack is not already running, it can be instantiated on the target ME host. After instantiation, the target MPTCP stack can be ready to receive information related to the MPTCP session to be transferred. For example, as further described herein, such information may include security keys, tokens, sequence numbers, etc. The MPTCP stack can, for example, receive, in the MPTCP session configuration, an IP address that the WTRU has obtained from the ME host on which the MPTCP stack is running or from an anchor node close to the target ME host. The WTRU can obtain multiple IP addresses while attaching to different anchors. To obtain the shortest data path between the WTRU and the ME App, the WTRU IP address assigned by the target ME host or by the anchor node closest to the target ME host can be selected.
[0170] After these operations are completed, a new sub-stream can be created between the MPTCP instance running on the target host and the MPTCP client running on the WTRU. This new sub-stream can be initially created with its priority or type set to indicate that it is in a "pre-assigned" state; that is, it cannot be used for data transmission at this point. The IP address assigned to the WTRU by the target ME host (i.e., the ME host where the WTRU has moved to—the WTRU's current anchor node) can be used to create this new sub-stream, for example, so that the shortest data path is used for it.
[0171] In some implementations, communication between the target ME MPTCP stack and the WTRU MPTCP stack may require transferring security information (e.g., security keys) used for the original MPTCP session (i.e., the MPTCP session between the WTRU and the original ME host) to the target MPTCP stack. In some implementations, this transfer can be performed securely.
[0172] The WTRU may be unaware that a new (pre-allocated) sub-stream has been created to another ME host (i.e., the target MPTCP stack). This target MPTCP stack can use the same keys as the initial MPTCP stack on the original ME host. Communication and data transfer can still occur between the WTRU and the initial ME host at this time. As discussed herein, this "pre-"sub-stream creation" can be performed to accelerate the connection switchover from the original sub-stream (the sub-stream between the WTRU and the original ME host) to the new sub-stream (the sub-stream between the WTRU and the target ME host) once the ME App transfer is complete.
[0173] As shown and described, for example, with respect to part C of Figure 5, the orchestrator can trigger ME App relocation while completing MPTCP session relocation. In this step, the target MPTCP stack may already be configured with an existing MPTCP session being transferred, and a new subflow between the target ME host and the WTRU may have been created with its state or priority set to "pre-assigned". This can be handled during the preparation steps, as previously described.
[0174] After the ME App relocation is triggered, updates to dynamic information related to the sub-stream and data transmission (e.g., the sequence number of the MPTCP session) can be exchanged between the initial MPTCP stack and the target MPTCP stack via MEO. This MPTCP information transfer can be performed during the ME App transfer; therefore, in some cases, it does not prolong the ME App relocation process. At this point, the target ME host is ready to process data traffic from the WTRU. To begin processing this data traffic, a new MPTCP sub-stream from the WTRU to the target ME host (which is pre-created (i.e., created during the preparation phase)) can be configured as a "regular" sub-stream (i.e., its type or priority is changed from "pre-assigned"). After the new sub-stream is configured as a "regular" sub-stream, the initial sub-stream can be changed to an "unavailable" sub-stream. If other sub-streams associated with the original ME host exist, these other sub-streams can be shut down. After the initial sub-stream becomes "unavailable," data traffic can then be exchanged between the WTRU App and the target ME App via the new sub-stream.
[0175] Some applications can store the IP addresses assigned to TCP connections. Therefore, to support transparent MPTCP sessions and ME App mobility from the perspective of the WTRU App, the initial sub-stream associated with the MPTCP session can be maintained as long as the MPTCP session exists—even if it is no longer used for data services. Thus, such a sub-stream can be marked as unavailable (e.g., using a priority or state such as "NOT_AVAILABLE"). This priority indicates that the sub-stream must be maintained, even though it is no longer used for data services, and that no other sub-streams can be created using the ME host address associated with this sub-stream. A sub-stream priority (e.g., "MP_PRIO") message can be used by the original ME host to change the initial sub-stream priority from "normal" to "unavailable". The new sub-stream priority directed towards the target ME host can be changed from "pre-assigned" to "normal" by the target ME host.
[0176] In some implementations, based on MPTCP session transfer as discussed in this paper, the relocated ME App can resume business data transmission after the ME App transfer is complete, as if it were still on the previous ME host. This can be accomplished, for example, using the same socket descriptor without establishing a new TCP connection with the WTRU.
[0177] Regarding the MPTCP information to be transferred, in some embodiments, all MPTCP sessions associated with the ME App being relocated are transferred to the MPTCP stack running on the target host. For each MPTCP session to be transferred, information associated with that MPTCP session is also transferred. This information may include security keys (e.g., server security keys and client security keys), tokens identifying the session (e.g., server tokens and client tokens that may be needed for new substream creation or existing substream removal), and the sequence number of the entire MPTCP session, etc.
[0178] In some embodiments, MPTCP session transfers are handled by the orchestrator (as opposed to direct communication between MPTCP servers, as discussed later). Typically, the orchestrator is aware of the WTRU movement; this facilitates the orchestrator's coordination of MPTCP session transfers. In such embodiments, the orchestrator uses an API toward the current MPTCP stack (the MPTCP stack on the initial ME host) to obtain MPTCP information to be transferred to the target MPTCP stack. The target MPTCP stack can also be configured using an API. Examples of these APIs are discussed in further detail here.
[0179] Figure 7 is a message sequence diagram illustrating an example MPTCP session transfer during the preparation phase, showing example communication between WTRU 700, first ME host 703, MEO 706 (or MEPM), and second ME host 709, where the MPTCP session transfer is handled by an orchestrator. In this example, MEO 706 is shown together with its associated MEP instances MEP 1 and MEP 2. In this figure, MEP1 and MEP 2 run on ME host 703 and ME host 709, respectively, to interact with MEO 706. As shown in Figure 7, during the preparation of the data stream transfer, information related to the MPTCP session can be transferred to another MPTCP instance running on another ME host. The message sequence diagram of Figure 7 is shown and described in four sections, A, B, C, and D.
[0180] In part A of Figure 7, WTRU 700 starts running WTRU App 710, which is communicating or will communicate with ME App 713 running on ME host 703. MPTCP stack 716 runs on WTRU 700, and MPTCP stack 719 runs on ME host 703, where MPTCP stack 716 and MPTCP stack 719 are MPTCP peers. WTRU App 710 creates TCP socket 711 to communicate with ME App 713 via the corresponding TCP socket 704. The socket creation request is intercepted by MPTCP stack 716, which creates an MPTCP session with the associated substream 726, after which data traffic 729 can be exchanged between the client application side and the server application side (i.e., WTRU App 710 and ME App 713, respectively).
[0181] In part B of Figure 7, in step 730, WTRU 700 moves, attaches to a new anchor node at ME host 709, and obtains a new IP address from ME host 709. Although the data path using substream 726 is longer than before the switch in step 730, as shown in Figure 7, session continuity can be preserved for substream 726.
[0182] In this example, data service 729 is channelized between two anchor points; that is, it is channelized between the currently connected ME host 709 and the previously connected ME host 703 via channel 733. In step 736, MEO 706 is notified (e.g., by network notification. For example, MEO 706 may register with the network to be notified when the WTRU moves / switches to another PoA / anchor point) of the movement of WTRU 600 and determines that ME App 713 should be moved to another ME host to "follow" (i.e., physically closer to) the WTRU. In step 739, if MPTCP stack 740 is not already running, it is instantiated on ME host 709, and MEO 706 triggers preparation for MPTCP session transfer.
[0183] In this example, MEP 1 uses socket API 741 locally on ME host 703 to obtain MPTCP information 742 to be transferred, for example, to create a new substream. Information 742 may include, for example, the IP address of WTRU 700, security keys, etc. In some examples, the "getsockopt" socket API can be used for this purpose; however, other sockets can be used, such as those discussed further herein. The obtained information is transferred to MEO 706. Any existing substreams between MPTCP 716 and MPTCP 719 are not transferred to MPTCP 740; instead, a new substream is established between WTRU 700 and the target ME host 709.
[0184] Part C of Figure 7 illustrates the socket API used by the target ME host 709 to configure the MPTCP session. Here, MPTCP information 742 is passed from MEO 706 to ME host 709, and the MPTCP session is created on MPTCP stack 740 using information obtained from MPTCP stack 719. For example, the MPTCP session can be replicated on the target ME host 709 using the same socket file descriptor, security key, and sequence number. The "socket" socket API 750 and "setsockopt" socket API 755 can be used for this purpose. The IP address of WTRU 700 is obtained from ME host 709, associated with the transferred MPTCP session, and configured on MPTCP stack 740. The existing substream is associated with two addresses: a first IP address from WTRU 700 and a second IP address from the ME host. Because the IP address of ME host 703 is not valid on the target ME host 709, this information is not transferred.
[0185] In section D of Figure 7, after the MPTCP message transfer in section C is completed, the target MPTCP stack 740 initiates the creation of a new sub-stream 770 based on the IP address of WTRU 700 (obtained as part of the transferred message) and the local IP address valid on ME host 709. The creation of a new sub-stream 770, as a PRE_ALLOCATED sub-stream, is initiated from ME host 709 with MPTCP stack 716 (i.e., the MPTCP peer of sub-stream 770) by using MPTCP message 765 sent to WTRU 700. In this example, message 765 is an MP_JOIN message, but note that other suitable messages may be used in other implementations. Pre-allocated sub-streams are described elsewhere in this document. In some examples, multiple new pre-allocated sub-streams (not shown) may be pre-created to replace existing sub-streams. For example, if WTRU 700 initially has two sub-streams toward ME host 703 (e.g., two sub-streams using cellular and WiFi interfaces), then the IP address of ME host 709 can be used to create two pre-assigned sub-streams toward ME host 709 (e.g., using cellular and WiFi if supported on ME host 709).
[0186] After the MPTCP session transfer preparation phase described in Figure 7 is completed, data traffic continues to be exchanged between WTRU 700 and ME host 703. Only MPTCP session transfer preparation is performed at this point; therefore, ME App 713 can still run on ME host 703. Thus, although MPTCP session transfer may have begun and a new pre-allocated substream 770 may have been created toward ME host 709, this substream may not be used for data traffic transmission at this phase. Note that in other implementations, the creation of a new pre-allocated substream can be initiated by the WTRU, as described later herein.
[0187] Figure 8 is a message sequence diagram illustrating an example communication between WTRU 800, first ME host 803, MEO 806 (or MEPM), and second ME host 809 for the MPTCP session transfer completion phase, where the MPTCP session transfer is handled by the orchestrator. In this example, MEO 806 is shown together with its associated MEP instances MEP 1 and MEP 2. In this figure, MEP 1 and MEP 2 operate on ME host 803 and ME host 809, respectively, to interact with MEO 806. During the example completion phase, a pre-prepared MPTCP session transfer is completed, for example, as described with reference to Figure 7. The target MPTCP instance can be updated with dynamic information related to recent data transmissions. This update can occur between the preparation and completion steps, after which data traffic can be exchanged between the WTRU and the target ME host 809 via the MPTCP target instance.
[0188] Part A of Figure 8 illustrates WTRU App 810 executing on WTRU 800. The various components and communications shown in Part A of Figure 8 are substantially similar to the corresponding components and communications shown in Part A of Figure 7. WTRU App 810 interacts with ME App 813 executing on ME host 803. WTRU App 810 and ME App 813 can each operate in a client-server relationship. WTRU 800 runs MPTCP stack 816, and ME host 803 runs the corresponding MPTCP stack 819. WTRU App 810 creates TCP socket 811 to communicate with ME App 813 via the corresponding TCP socket 804. The TCP socket request is intercepted by MPTCP stack 816, which, based on TCP socket request 811, utilizes substream 826 of the corresponding MPTCP stack 819 to create an MPTCP session. Data traffic 829 is exchanged between WTRU App 810 and ME App 813 via substream 826.
[0189] Part B of Figure 8 illustrates the context after WTRU 800 moves and anchors to ME host 809. The various elements and communications shown in Part B of Figure 8 are substantially similar to the corresponding elements and communications shown in Part B of Figure 7. MEO 806 is notified of the WTRU move and determines that ME App 813 should be moved to ME host 809 to "follow" the WTRU. In this example, MEO 806 triggers preparation for MPTCP session transfer, and the MPTCP session can be transferred to MPTCP stack 840 on ME host 809. MPTCP stack 840 creates a new pre-allocated substream 870 between WTRU 800 and ME host 809 (e.g., where substream 870 has a priority of "PRE_ALLOCATED"). At the end of Part B of Figure 8, data traffic 829 between WTRU App 810 and ME App 813 continues to be transmitted via ME host 809 and channel 833 on substream 826.
[0190] In part C of Figure 8, MEO 806 triggers a transfer of ME App 813 to ME host 809 in step 834. The transferred ME App is referred to as ME App 849 in Figure 8. MEO 806 also triggers the completion of the MPTCP session transfer in step 850. Note that the application transfer (e.g., step 834) and the MPTCP session transfer (e.g., step 850) can be performed in parallel (e.g., simultaneously or concurrently).
[0191] MPTCP session-specific information has been transferred to the target MPTCP stack 840 (in section B). However, since data transmission may continue during the preparation phase, some information may need to be updated (e.g., MPTCP sequence number). In this example, this update is handled by MEO 806 sending message 851 to query MPTCP stack 819 on ME host 803 for the updated MPTCP session information (e.g., using the "getsockopt" function, as discussed further herein), which returns the information in message 852. MEO 806 sends message 853 with this information to MPTCP stack 840 on target ME host 809 (e.g., using the "setsockopt" function, as discussed further herein). MEO 806 can then notify MPTCP stack 819 on ME host 803 that the MPTCP session has been moved. MPTCP stack 840 on target ME host 809 completes the MPTCP session transfer on its side by sending message 855 to change the priority of pre-allocated substream 870 to REGULAR.
[0192] After substream 870 is changed to a regular substream, in step 890, all substreams associated with the transferred MPTCP session related to the ME host 803, except for the initial substream 826, are closed by sending an MPTCP message 891 from the MPTCP stack 819 on the ME host 803 to the MPTCP stack 816 on the WTRU 800. In this example, for ease of description, only one substream is shown; therefore, the example steps for closing other substreams are shown with dashed lines. As previously mentioned, the initial substream is a special case and in some implementations, it is retained even if it is no longer used for data transmission. Therefore, in this example, by sending an MP_PRIO message 893 from MPTCP stack 819 on ME host 803 to MPTCP stack 816 on WTRU 800, the priority associated with the initial substream is set to "NOT_AVAILABLE". The initial TCP substream can remain active, although unused, until it is closed from the WTRU side or expires at operation 894 (i.e., without a keep-alive response). The MPTCP session can be silently discarded when the remaining substreams are closed or if the MPTCP session is closed by the WTRU.
[0193] In some implementations, the silent MPTCP session is handled locally and exclusively on ME host 803; that is, at this point, nothing is sent to the WTRU because the MPTCP session may still exist for WTRU 800 and has been transferred to a different ME host. Therefore, the MPTCP stack 819 on the initial ME host 803 can perform memory cleanup to free up memory. If ME App 849 is later transferred to another ME host (e.g., ME host 3, not shown), all sub-streams associated with ME host 809 can be closed once the transfer of MEApp and MPTCP is complete. The MPTCP session on ME host 2 can also be silently dropped. This behavior differs from ME host 803 because the initial sub-stream is associated with ME host 803, not ME host 809. Therefore, ME host 809 can be completely cleaned up after the transfer of ME App 849.
[0194] At the end of part C, the ME App transfer to ME App 849 is completed in step 895, the MPTCP session transfer is completed, the initial substream 826 is reserved in non-data transmission priority (e.g., "NOT_AVAILABLE"), and data service 829 can be transmitted on substream 870 between WTRU App 810 on WTRU 800 and ME App 849 on ME host 809.
[0195] Note that in the alternative embodiment (not shown), the BACKUP priority instead of the PRE_ALLOCATED priority can be used for substreams created during the preparation step (e.g., substream 870 during part B of Figure 8). In this case, after all substreams on the initial ME host are shut down (and the initial substream is set to NOT_AVAILABLE), the BACKUP substream associated with the target ME host can be used as a normal standby substream. The priority of this substream can be changed to REGULAR later after the MPTCP session transfer is complete.
[0196] In this replacement, in addition to the BACKUP flag, additional flags may need to be set on the BACKUP substream (e.g., the DON'T_USE flag, discussed further here). This additional flag may be necessary if the initial substream fails after the preparation phase has ended but before the completion phase has begun. In such cases, the spare substream on the target ME host may not be used because the ME App has not yet been transferred to this ME host. Instead, a spare substream from the initial ME host (if available) can be used.
[0197] The orchestrator may use one or more new APIs, such as those described below, to obtain MPTCP-related information from the MPTCP stack running on the current ME host (e.g., ME host 1) and configure the MPTCP stack on the target ME host (e.g., ME host 2).
[0198] The socket file descriptor used by the ME App (e.g., "sockfd") can be obtained using existing commands on the ME host (e.g., commands like "netstat") or by viewing system files (e.g., system files like " / proc / net / tcp", " / proc / {pid} / fd"). Another possibility is that the file descriptor can be obtained directly from the ME App, for example, via a registration mechanism. This information can be provided to the orchestrator (MEP, MEPM, or MEO) via a registration mechanism. Note that in the various examples here, the MEO knows which WTRU is moving, the ME App knows which WTRU is associated with which user and which sockfd, the MEO needs to know which sockfd the MPTCP session should be transferred to, and the MEApp, knowing MPTCP, can directly trigger the MPTCP session transfer.
[0199] Table 2 describes example parameters for the function "socket" used to create a socket associated with an MPTCP session. The new socket protocol value (IPPROTO_MPTCP) enables the creation of a socket handled by the MPTCP stack, using a specified file descriptor value. After creating the MPTCP socket, socket configuration using setsockopt() can be expected. This socket can be called on the target ME host platform to create a socket associated with a specific file descriptor (sockfd). An example of the API for creating an MPTCP socket using a specified descriptor is as follows:
[0200] socket(domain,type,proto,sockfd)
[0201] Table 2
[0202]
[0203] Table 3 describes example parameters for the function "get MPTCP session info". Information related to the MPTCP session can be retrieved using the getsockopt() function call. This is achieved by introducing the new socket option MPTCP_GET_INFO. The MPTCP session can be identified by a field descriptor (sockfd). An example of the socket API used to retrieve MPTCP session information is as follows:
[0204] getsockopt(sockfd,IPPROTO_TCP,option,mptcp_info,mptcp_info_len)
[0205] Table 3
[0206]
[0207] Table 4 describes example parameters for the function "set MPTCP session info". This function can be called to configure the MPTCP session using information previously obtained via getsockopt(...,MPTCP_GET_INFO...). The IP address of the WTRU assigned from the current ME host can also be specified. Examples of the socket API are as follows:
[0208] setsockopt(sockfd,IPPROTO_TCP,option,mptcp_info,mptcp_info_len,nb_addr,WTRU's local addr)
[0209] Table 4
[0210]
[0211] Table 5 describes example parameters for the function "set MPTCP session moved". This function can be called to notify the MPTCP stack that the specified MPTCP session has been moved. Upon receiving this message, the MPTCP stack may need to immediately close all substreams except the initial substream, which may need to be maintained but no longer used for data service transmission. In this case, the priority NOT_AVAILABLE on the initial substream can be set by sending an MP_PRIO message to the WTRU. An example of the socket API is as follows:
[0212] setsockopt(sockfd,IPPROTO_TCP,option)
[0213] Table 5
[0214] option It is set to MPTCP_SESSION_MOVED.
[0215] Various MPTCP messages and protocols can be used in one or more embodiments disclosed herein. For example, Figure 9 Bitmap 900 illustrates an exemplary modified substream priority (MP_PRIO) option. The modified MP_PRIO option for MPTCP messages is enhanced to support the preservation of initial substreams while marking them as unavailable using a new priority. This new priority is: NOT_AVAILABLE (new) - N bits in the MP_PRIO option. In some implementations, this new priority is set using a bit marked "-N" in the bitmap. In the example implementation, the flag (N) is set to (1) to set the priority to NOT_AVAILABLE, otherwise it is set to (0).
[0216] Figure 10 and Figure 11 Bitmaps 1000 and 1100 are shown, illustrating exemplary modified join (MP_JOIN) options for initial SYN and SYN / ACK responses, respectively. This modified MP_JOIN option is enhanced to support substreams with priorities BACKUP and DON'T_USE, and in some implementations, it can be used as an alternative to the PRE_ALLOCATED priority.
[0217] The new substream type can be represented as: the DON'T_USE (new) -D bit in MSG. In some implementations, the new substream type is set using the bit marked "-D" in the bitmap. In one example implementation, the flag (D) can be set to (1) to create a substream that may not be used for data transmission, or even a spare regular substream; otherwise, it can be set to (0).
[0218] The various embodiments discussed above relate to MPTCP session transfers coordinated by an orchestrator (e.g., MEO). Conversely, in some embodiments, MPTCP mobility can be handled using direct communication between MPTCP stacks. In some examples, the MPTCP stacks discussed are MPTCP stacks running on the ME host initially connecting to the WTRU (e.g., ME host 1) and MPTCP stacks running on the target ME host (e.g., ME host 2). Such stacks typically handle server-side communication; therefore, implementations where MPTCP mobility is handled using direct communication between such instances involve server-to-server communication and, in some implementations, are transparent to the client (i.e., WTRU) side.
[0219] Some implementations of handling MPTCP mobility using direct communication between MPTCP stacks involve communication between "non-peer" MPTCP stacks.
[0220] Compared to typical communication where information is exchanged between two MPTCP peers to create an MPTCP session with related substreams for transmitting application data, in some embodiments, "non-peer" communication does not transmit data services (e.g., application data). Instead, it transfers MPTCP session information to a target MPTCP stack, allowing that target MPTCP stack to continue its existing communication with the MPTCP stack on the WTRU. To handle this communication, an IP connection can be established between the two ME MPTCP stacks.
[0221] Figure 12 is a message sequence diagram illustrating example communication between WTRU 1200, first ME host 1203, MEO 1206 (or MEPM), and second ME host 1209 for an example MPTCP session transfer during the preparation phase. The MPTCP session transfer is handled using direct communication between MPTCP stacks. In this example, MEO 1206 is shown together with its associated MEP instances MEP1 and MEP 2. In this diagram, MEP 1 and MEP 2 run on ME host 1203 and ME host 1209, respectively, to interact with MEO 1206. The message sequence diagram of Figure 12 is shown and described in four sections, A, B, C, and D.
[0222] Similar to the orchestrator approach, embodiments using direct communication between MPTCP stacks to handle MPTCP session transfer may include a preparation phase. In this case, information related to the MPTCP session may be transferred to another MPTCP stack running on another ME host to prepare for the data stream transfer. In some embodiments, the MPTCP session transfer is triggered by an orchestrator (e.g., MEO), which may notify the appropriate MEPM and / or MEP. At this time, socket interfaces can be used to complete the interaction with the MPTCP stack. In some embodiments, direct communication (e.g., IP-based communication) between the initial ME host and the target ME host is used to perform the MPTCP session transfer and the exchange of related information.
[0223] In part A of Figure 12, WTRU 1200 starts running WTRU App 1210, which is communicating or will communicate with ME App 1213 running on ME host 1203. MPTCP stack 1216 runs on WTRU 1200, and MPTCP stack 1219 runs on ME host 1203, where MPTCP stack 1216 and MPTCP stack 1219 are MPTCP peers. WTRU App 1210 creates TCP socket 1211 to communicate with ME App 1213 via a TCP connection. The socket creation request is intercepted by MPTCP stack 1216, which creates an MPTCP session with an associated substream 1226, after which data traffic 1229 can be exchanged between the client application side and the server application side (i.e., WTRU App 1210 and ME App 1213, respectively).
[0224] In part B of Figure 12, in step 1230, WTRU 1200 moves, attaches to the new anchor node at ME host 1209, and obtains a new IP address from ME host 1209. Although, as shown in Figure 12, the data path using sub-stream 1226 is longer than before the switch in step 1230, session continuity can be maintained for sub-stream 1226. In this example, data traffic 1229 is channelized between the two anchor points; that is, it is transmitted via channel 1233 between the currently connected ME host 1209 and the previously connected ME host 1203.
[0225] In step 1236, MEO 1206 is notified (e.g., by network notification. For example, MEO 1206 may register with the network to be notified when the WTRU moves / is indeed switched to another PoA / anchor point) of the movement of WTRU 1200 and determines that ME App 1213 should be moved to another ME host (i.e., ME host 1209) to "follow" (i.e., physically closer to) the WTRU. In step 1239, MPTCP stack 1240 (which has no associated substreams) is instantiated on ME host 1209 if it is not already running, and MEO 1206 triggers preparation for MPTCP session relocation in step 1241.
[0226] In this example, MEO 1206 (via MEP 1 running on ME host 1203) uses the local socket API 1242 on ME host 1203 to obtain MPTCP information 1243 to be transferred. Information 1243 may include, for example, the IP address of WTRU 1200, a security key, etc. MPTCP stack 1240 is configured with a security key obtained from MPTCP stack 1219 on ME host 1203. This key can be used to allow the establishment of a new substream associated with the transferred MPTCP session. MPTCP stack 1240 is also configured with an IP address assigned to WTRU 1200 by ME host 1209.
[0227] This can be accomplished, for example, using a regular socket API that has been modified to support MPTCP session transfer, as discussed herein. Local calls to configure MPTCP stack 1240 in this manner based on the socket API are shown in messages 1244, 1245, and 1246.
[0228] At this point, the key is used by ME host 1203 and WTRU 1200, which are two peers associated with the MPTCP session. For example, the target MPTCP stack can be notified via the MEP API that the MPTCP session relocation process has begun. In some examples, the target MPTCP stack can be notified via the MEP API using a socket interface or another interface; this interface can be described such that it can be socket-based, or it can be any other interface that can exist between MEO 1206 and the application running ME host 1209. This interface between the target MPTCP stack 1240 on MEO 1206 and ME host 1209 can be used to keep MEO 1206 informed of the transition state.
[0229] Since MEO 1206 itself does not handle the transfer in this example, MEO 1206 may need to be informed (or receive information it can use to determine) when to trigger the ME App transfer, such as once the MPTCP transfer is ready. The target MPTCP stack may also need to be informed (or receive information it can use to determine) when the MPTCP session transfer is complete, for example when the ME App transfer is triggered.
[0230] In part C of Figure 12, the target ME host 1209 can initiate the establishment of its own connection with ME host 1203 and then transmit that information. The connection between the two ME hosts can be a TCP session or a substream added to the MPTCP session to be relocated. The latter is illustrated in the example in Figure 12.
[0231] As shown in the figure, the target ME host 1209 can, for example, use message 1250 to initiate the creation of a sub-stream 1253 toward the current ME host 1203. In this example, message 1250 is an MP_JOIN (relocation) message establishing the MPTCP sub-stream 1253. The sub-stream 1253 can be associated with an existing MPTCP session and can be created using the MPTCP sub-stream priority RELOCATION (which is the opposite of the existing REGULAR and BACKUP priorities). In this example, the RELOCATION priority indicates that this sub-stream 1253 can only be used to transmit information related to the MPTCP session transfer (i.e., not to transmit data services). For this RELOCATION sub-stream, the security key to be used can be the security key configured when the MPTCP transfer is triggered (in step 2). When the target ME host uses the WTRU's key, the current ME host can continue to use its key.
[0232] Note that at this point, three peers are associated with the MPTCP session – WTRU 1200, the current ME host 1203, and the target ME host 1209. Each MPTCP sub-stream exists between only two peers; however, the multiple sub-streams do not have the same two peers. For example, sub-stream 1226 exists between ME host 1203 and WTRU 1200, while sub-stream 1253 exists between ME host 1203 and ME host 1209. As will be described later, another sub-stream 1260 will exist between ME host 1209 and WTRU 1200.
[0233] In this example, WTRU 1200 is not involved with substream 1253, may not be aware of its existence, and does not need to know that its two peers (i.e., ME host 1203 and ME host 1209) are different. Instead, WTRU 1200 may treat ME host 1203 and ME host 1209 as the same MPTCP peer.
[0234] After communication is established between ME host 1203 and ME host 1209, MPTCP session-related information can be transferred to the target ME host 1209. In this example, the MPTCP session-related information is transferred via substream 1253 using message 1256. Message 1256 can be, for example, an MP_SET_INFO(info) message.
[0235] In section D of Figure 12, after the MPTCP session transfer is completed, in step 1259, the target MPTCP stack 1240 triggers the establishment of a "pre-allocated" sub-flow 1260 with WTRU 1200. In this case, and for all other communications with WTRU, the target ME host 1209 can use a host security key, such as the ME host 1203 security key (instead of the WTRU 1200 key used for sub-flow relocation). In this example, MPTCP stack 1240 can establish sub-flow 1260 by sending message 1265 to MPTCP stack 1216. It should be noted that in other embodiments (not shown), alternatively, the "pre-allocated" sub-flow creation (between the target ME host 1209 and WTRU 1200) can be triggered by the current ME host 1203, which has previously queried the target ME host 1209 for an available IP address.
[0236] At this point, a substream 1260 is created between the WTRU and the target host, although it is not yet used to transmit application data traffic because it is a "pre-allocated" substream. Instead, application data is still exchanged between WTRUApp 1210 on WTRU 1204 and ME App 1213 on ME host 1203 via substream 1226. The MPTCP stack 1240 on the target ME host 1209 uses message 1270 to notify MEO 1206 that it is ready for the next stage of the transfer transport. In this example, message 1270 is a Notify (RelocReady) message.
[0237] Note that in other embodiments (not shown), a separate TCP connection (i.e., a connection “outside” the MPTCP session boundary) can be used to exchange information related to the MPTCP session to be transferred, instead of using the substream associated with that MPTCP session. In this case, the MEO 1206 can be configured with a separate security key on each side. A new set of security keys can be used for server-to-server communication and can be configured during part B of Figure 12 above when triggering the MPTCP session transfer (e.g., using a 3-way handshake not shown in Figure 13).
[0238] Figure 13 is a message sequence diagram illustrating example communication between WTRU 1300, first ME host 1303, MEO 1306 (or MEPM), and second ME host 1309 for an example MPTCP session transfer during the completion phase, where the MPTCP session transfer is handled using direct communication between MPTCP stacks. In this example, MEO 1306 is shown together with its associated MEP instances MEP 1 and MEP 2. In this figure, MEP 1 and MEP 2 operate on ME host 1303 and ME host 1309, respectively, to interact with MEO 1306. During the completion phase, the MPTCP session transfer, which has been prepared in advance as described herein, is completed. The target MPTCP instance is updated with dynamic information related to recent data transmissions, and the applied data can then be exchanged between the WTRU and the MPTCP target instance. The message sequence diagram of Figure 13 is shown and described in four sections A, B, C, and D.
[0239] In part A of Figure 13, WTRU 1300 starts running WTRU App 1310, which is communicating or will communicate with ME App 1213 running on ME host 1203. MPTCP stack 1316 runs on WTRU 1300, and MPTCP stack 1319 runs on ME host 1303, where MPTCP stack 1316 and MPTCP stack 1319 are MPTCP peers. WTRU App 1310 creates TCP socket 1311 to communicate with ME App 1313 via a TCP connection. The socket creation request is intercepted by MPTCP stack 1316, which creates an MPTCP session with an associated substream 1326, after which data traffic 1329 can be exchanged between the client application side and the server application side (i.e., WTRU App 1310 and ME App 1313, respectively).
[0240] In part B of Figure 13, WTRU 1300 moves, attaches to a new anchor node at ME host 1309, and obtains a new IP address from ME host 1309. Although the data path using sub-stream 1326 is longer than before the switch in step 1330, as shown in Figure 13, session continuity can be maintained for sub-stream 1326. In this example, data traffic 1329 is channelized between the two anchor points; that is, it is transmitted via channel 1333 between the currently connected ME host 1309 and the previously connected ME host 1303. MEO 1306 is notified (e.g., by network notification. For example, MEO 1306 may register with the network to be notified when the WTRU moves / makes a switch to another PoA / anchor point) of the movement of WTRU 1300 and determines that ME App 1313 should be moved to another ME host (i.e., ME host 1309) to "follow" (i.e., physically closer to) the WTRU. If MPTCP stack 1340 (without any associated substreams) is not already running, it is instantiated on ME host 1309, and MEO 1306 triggers preparation for MPTCP session relocation.
[0241] Relocation substream 1353 is created between ME host 1303 and ME host 1309. MPTCP session information is transferred to ME host 1309 via substream 1353, and pre-allocation substream 1360 is created between ME host 1309 and WTRU 1300, as described with respect to relocation substream 1253 and pre-allocation substream 1260 in Figure 12. Although the data path using substream 1326 is longer than before the WTRU 1300 was moved, as shown in Figure 13, session continuity is maintained for substream 1326. In this example, data traffic 1329 is channelized between two anchor points; that is, it is transmitted via channel 1333 between the currently connected ME host 1309 and the previously connected ME host 1303.
[0242] In part C of Figure 13, MEO 1306 triggers a transfer from ME App 1313 to ME host 1309 as MEApp 1345 in step 1341. MEO 1306 may transmit message 1347 to ME host 1309 via MEP on the target ME host 1309. Receipt of message 1347 in step 1350 may trigger the MPTCP session transfer completion phase. In this phase, MPTCP session-specific information may have been transferred to the target MPTCP stack 1340; however, since data transmission may continue during the preparation phase, some information (e.g., MPTCP sequence number) may need to be updated, which can be done at this point. The target MPTCP stack 1340 may, for example, notify the current MPTCP stack 1319 using message 1354 (which may be an MP_RELOC_READY message) that it is ready to receive the latest information and complete the MPTCP session transfer. In response, MPTCP stack 1319 may, for example, use message 1356 (which may be an MP_SET_INFO message) to send the updated information to MPTCP stack 1340.
[0243] After receiving update information related to the MPTCP session on the target ME host 1309, the MPTCP stack 1340 can change the priority of substream 1360 from PRE_ALLOCATED to REGULAR by sending message 1359 (which may be an MP_PRIO message) to the MPTCP stack 1316. This priority change can be repeated for each substream established between the MPTCP stack 1340 on WTRU 1300 and ME host 1309. However, for simplicity, only one such substream 1360 is shown in Figure 13.
[0244] Since the MPTCP session transfer to ME host 1309 is now complete, the sub-stream between MPTCP stack 1319 on ME host 1303 and MPTCP stack 1316 on WTRU 1300 can be closed in step 1390 by sending MPTCP message 1391, except for the initial sub-stream 1326. However, note that in this example, the initial sub-stream is retained even if it is no longer used. All other such sub-streams (if any) can be closed. For simplicity, only one sub-stream (the initial sub-stream) is used in the example of ME host 1; therefore, the example steps for closing other sub-streams are shown with dashed lines.
[0245] As previously mentioned, the initial substream 1326 is a special case and is retained in some implementations even if it is no longer used for data transmission. Therefore, in this example, the MPTCP stack 1319 on the ME host 1303 changes the priority of the initial substream to NOT_AVAILABLE by sending an MP_PRIO message 1393 from the MPTCP stack 1319 on the ME host 1303 to the MPTCP stack 1316 on the WTRU 1300.
[0246] At the end of part C, the ME App transfer to ME App 1345 is completed in step 1395, the MPTCP session transfer is completed, the initial sub-stream 1326 is reserved in a non-data transfer priority (e.g., "NOT_AVAILABLE"), and data service 1329 can be transmitted between WTRU App 1310 on WTRU 800 and ME App 1345 on ME host 1309 via sub-stream 1360.
[0247] In part D of Figure 13, the MPTCP session can be completely transferred to ME host 1309. In some embodiments, the remaining steps can be used for cleanup purposes. At this point, the relocation sub-stream 1353 used for server-to-server communication (i.e., communication between MPTCP stack 1319 on ME host 1303 and MPTCP stack 1340 on ME host 1309) is no longer needed, and therefore it is closed at 1398 using a FIN message.
[0248] On ME host 1303, the MPTCP session can be silently discarded (i.e., no messages are sent to the WTRU). The MPTCP session may no longer exist on ME host 1303; however, it can still be used on the WTRU with ME host 1309 as the new peer. Therefore, the initial TCP substream can remain active on both ME host 1303 and WTRU 1300 (although not used for transmitting application data services) until it is closed by WTRU 1300 or it expires (i.e., no keep-alive response). MPTCP stack 1340 on ME host 1309 can use message 1399 (which may be a Notify(RelocDone) message) to notify MEO 1306 that the MPTCP session transfer has been completed.
[0249] The MEP API can be used for MPTCP session relocation. The following API can be used to synchronize the orchestrator and MPTCP stack transfer phase. In embodiments where the orchestrator is not involved in the MPTCP session information transfer, it may be necessary to inform it when the MPTCP session transfer is ready for ME App transfer. It can be assumed that communication exists between the orchestrator / MEPM, the MEP, and the MEApp running on the ME host. In the examples herein, the MPTCP stack running on the ME host can be the ME application. This API facilitates the MPTCP session transfer when it is handled via direct communication between the current MPTCP stack and the target MPTCP stack. Alternatively, this API can be implemented using the socket API. Examples of the API are as follows:
[0250] Notify(notification_type,params,params_len).
[0251] Here are some example notification types:
[0252] RelocPrep (relocation preparation), RelocReady (relocation ready), Reloc (relocation), RelocDone (relocation complete).
[0253] Table 6 describes example RelocPrep notification parameters. This notification can be sent from the MEP to the target MPTCP stack to inform the MPTCP instance that an MPTCP session transfer will be performed, for example, to trigger the preparation phase. Table 6 lists example parameters that can be specified when using this notification.
[0254] Table 6
[0255] request ID The identifier number of the request. This will be associated with the "RelocReady()" call. sockfd This identifies the MPTCP session. It is acquired during registration.
[0256] Table 7 describes example RelocReady notification parameters. This notification can be sent from the target MPTCP stack to the MEP to indicate that the preparation steps have been completed, and, for example, that the MPTCP stack is ready to continue the MPTCP session transfer.
[0257] Table 7
[0258] request ID The identifier of the request. Obtained from the "RelocPrep()" call.
[0259] Table 8 describes exemplary Reloc notification parameters. This notification can be sent from the MEP to the target MPTCP stack to trigger the completion of the MPTCP session transfer. This can trigger the completion phase.
[0260] Table 8
[0261] request ID The identifier number of the request. This will be associated with the "RelocDone()" call.
[0262] Table 9 describes the example RelocDone notification parameters. This notification can be sent from the target MPTCP stack to the MEP to indicate that the MPTCP session transfer is complete.
[0263] Table 9
[0264] request ID The identifier of the request. Obtained from the "Reloc()" call.
[0265] The socket API can be used by the orchestrator to obtain MPTCP-related information from the MPTCP stack running on the current ME host (e.g., ME host 1) and to configure the MPTCP stack on the target ME host (e.g., ME host 2). As discussed earlier in this document, the Create MPTCP Socket API can be used.
[0266] Get MPTCP_RELOC is an option that can be used to prepare for the relocation of an MPTCP session. It can be sent to the current ME host (e.g., ME host 1) to indicate an impending MPTCP session transfer. Simultaneously, the security key associated with the MPTCP session can be retrieved and transferred to the target ME host. The specified security key is one that has already been used by the ME host (e.g., ME host 1) and the WTRU. Table 10 describes examples of Get MPTCP_RELOC API parameters. Below is an example of the socket API:
[0267] getsockopt(sockfd,IPPROTO_TCP,option,info,len).
[0268] Table 10
[0269]
[0270] `Set MPTCP_RELOC` is an option that can be used to prepare for the relocation of an MPTCP session to a target ME host. It can be sent to the target ME host (e.g., ME host 2) to trigger the MPTCP session transfer and configured with necessary information, such as a security key. The security key specified therein can be a security key used by the ME host (e.g., ME host 1) and the WTRU.
[0271] Table 11 describes the example Set MPTCP_RELOC API parameters. The following is an example of this socket API:
[0272] setsockopt(sockfd,IPPROTO_TCP,MPTCP_RELOC,info,len,nb_addr,WTRU'slocal addr).
[0273] Table 11
[0274]
[0275] Various MPTCP protocols and messages can be modified and defined to support MPTCP session transfer. For example, Figure 14 This is bitmap 1400, which shows an example modified join (MP_JOIN) option for the initial SYN. Figure 15 This is a bitmap 1500 illustrating an exemplary modified join connection (MP_JOIN) option for responding to SYN / AC. The MP_JOIN option, as discussed herein, can be further enhanced to support substreams with priority RELOCATION.
[0276] The new substream priority can be represented as the R bit in RELOCATION-MSG. In some implementations, the example flag (R) is set to (1) to establish a substream for transferring information related to MPTCP session relocation between the current MPTCP stack and the target MPTCP stack (e.g., server to server); otherwise, it can be set to (0).
[0277] MP_SET_INFO is an option that can be used to transfer MPTCP session information from the current MPTCP stack to the target MPTCP stack in preparation for an MPTCP session transfer. MP_SET_INFO can also be used during the completion phase to update dynamic information that may have changed during the preparation phase. Examples of information that can be transferred using this option include: security keys, tokens, and MPTCP session sequence numbers from ME host 1 (i.e., the initial host) and the MPTCP peer running on WTRU.
[0278] MP_RELOC_READY is an option that the target MPTCP stack can use to trigger the completion of the MPTCP session transfer. MP_RELOC_READY can indicate that the target MPTCP stack is ready to complete the transfer.
[0279] Some implementations include an ME App transfer mechanism to support maintained connectivity (i.e., where the App does not need to start a new TCP session on the target host). This mechanism may include reusing the same socket number for both the ME App and the MPTCP stack. For MPTCP, the socket information may be stored in the MPTCP session-related information transferred to the target host. For the ME App, the socket number may also need to be added to the information to be transferred to the target host.
[0280] In some cases, the MPTCP stack may already be running on the target ME host, and MPTCP sessions may already exist, one of which may be using the same session number (or socket number) as the transferred session. To address such situations, in some embodiments, the MPTCP socket file descriptor (fd) value may differ from the regular TCP socket fd (e.g., MPTCP uses a seed unique to its ME host to generate its own socket value). The probability of generating such a number on another ME host may be very low. In cases where it is unlikely that the exact same socket number already exists on the target platform, the MPTCP stack can create a new socket number that will be used on the target platform. This new number can be associated with the transferred MPTCP session and can be signaled to the orchestrator / MEPM / MEP. The new socket number can then be transferred to the ME App and added to its transfer information.
[0281] In one embodiment, the WTRU can initiate the creation of a PRE_ALLOCATED subflow. NAT prevents the ME host from establishing a new subflow toward the WTRU. In this case, the target ME host can pass its available address to the current ME host. The current ME host, which may already be communicating with the WTRU, can use the MPTCP ADD_ADDR option to advertise the target host's available address to the WTRU.
[0282] Figure 16 This is bitmap 1600 illustrating an exemplary modification of the Add Address (ADD_ADDR) option. The ME host may not have control over whether or when the WTRU (i.e., based on the MPTCP ADD_ADDR message) creates a new substream. In some embodiments, the ME host may not be able to force the WTRU to create (or notify the WTRU that it should) the new substream with a priority set to "pre-allocated".
[0283] Therefore, in some embodiments, the ME host can use Figure 16 This is achieved by modifying the ADD_ADDR option. In bitmap 1600, the IPVer field can represent the IP address version (i.e., IPv4 or IPv6). Therefore, this 4-bit field can be set to 0100 (4) or 0110 (6). Thus, two bits may be sufficient to encode the version, with the leftmost and rightmost bits always being 0. Therefore, in some embodiments, these two bits can be used to encode other information, such as the aforementioned priority and immediate bits, which instruct the receiver to immediately create a substream toward the specified address. Figure 16As shown, in some embodiments, bit "-D" can be set to 1 to indicate the DON'T_USE (pre-allocation) priority, and set to 0 to indicate REGULAR. In some embodiments, bit "-I" can be set to 1 to indicate that the substream needs to be created immediately; otherwise, it can be set to 0.
[0284] Figure 17 is a message sequence diagram illustrating an example NAT usage scenario (where the WTRU initiates the creation of the PRE_ALLOCATED subflow) and showing examples of MPTCP session transfers using either the first method discussed here (i.e., where MPTCP session transfers are coordinated by the orchestrator using the socket API) or the second method (i.e., where MPTCP session transfers are handled via direct communication between the MPTCP stack on the current ME host and the MPTCP stack on the target ME host). Figure 17 illustrates example communication between WTRU 1700, the first ME host 1703, MEO 1706 (or MEPM), and the second ME host 1709. In this example, MEO 1706 is shown together with its associated MEP instances MEP 1 and MEP 2. In this figure, MEP 1 and MEP 2 operate on ME host 1703 and ME host 1709, respectively, to interact with MEO 1706. The message sequence diagram of Figure 17 is shown and described in two sections, A and B.
[0285] The operations and signaling shown in Part A are the same as or similar to those shown and described with respect to Figures 12 and 7. Therefore, for the sake of brevity, a detailed description of Part A is omitted. In Part B, the current MPTCP stack 1719 can obtain an available address from the target ME host 1709 in step 1750 using either the first or second method.
[0286] For example, using method 1, MEO 1706 can use getsockopt(sockfd, MPTCP_GET_ADDR) at 1753, where the socket descriptor and the request MPTCP_GET_ADDR can be specified in the request, and the address can be returned in response message 1756. MEO 1706 can then use setsockopt(sockfd, MPTCP_SET_ADDR) at 1759 to configure the address to the initial ME host 1703. In another example, using method 2, the initial ME host 1703 can send MP_GET_ADDR(MPTCP session id, addr) to the target ME host 1709 in message 1763. The session can be provided in this request, and the address can be returned in response message 1766.
[0287] In either case, the initial ME host 1703 may send this address to the WTRU in message 1770 (using the MPTCP message ADD_ADDR), while requesting the immediate creation of a new pre-allocated substream (e.g., using bits I=1 and D=1, as discussed further herein). In step 1775, the WTRU 1700 receiving this request may initiate the creation of a pre-allocated substream toward the receiving address, which in this example is toward the target ME host 1709. The WTRU 1700 may select an address from its available addresses that has already been obtained from the current anchor node (i.e., the target ME host 1709). The MPTCP stack 1716 on the WTRU 1700 sends an MPTCP message 1780 (in this example, an MP_JOIN(PRE_ALLOCATED) message) to the MPTCP stack 1745 on the target ME host 1709 to initiate the creation of the substream, and thus a new pre-allocated substream 1785 is created between the WTRU 1700 and the target ME host 1709.
[0288] Note that this pre-allocated substream creation involves three peers. The initial ME host 1703 triggers the substream creation by configuring the address to be used for the substream and specifying "Create Now". WTRU 1700 and the target ME host 1709 exchange messages to establish the substream.
[0289] Some embodiments include a ME App aware of MPTCP. As mentioned above, the MPTCP session transfer procedure may assume that the ME App is unaware of MPTCP usage. However, in some embodiments, the transfer procedure may be used with an application aware of MPTCP, for example, with minor modifications to utilize MPTCP-specific APIs.
[0290] For example, an ME App running on the current ME host can trigger an MPTCP session transfer using the MPTCP-specific API. The ME App itself can request the MPTCP session transfer if it is aware of MPTCP usage. For the App, the sockfd can be associated with the communication channel that needs to be transferred with the App. The ME App can request MPTCP session mobility by passing the appropriate socket file descriptor (sockfd) to the MPTCP stack using the MPTCP-specific socket API. The orchestrator can trigger the ME App transfer, but may not be involved in the MPTCP session transfer.
[0291] ME App instances can be transferred to the target ME host (if it is not already running), and so can MPTCP sessions. A knowledgeable ME App on the current (source) ME host can handle the MPTCP session transfer by obtaining the MPTCP-specific information to be transferred and transferring it to the target ME host. This transfer can be processed at the ME App level. Once the MPTCP session information is received by the ME App on the target ME host, it can be passed to the MPTCP stack. The socket API can be used using either the first method discussed herein (i.e., where the MPTCP session transfer is coordinated by the orchestrator using the socket API) or the second method (i.e., where the MPTCP session transfer is handled via direct communication between the MPTCP stack on the current ME host and the MPTCP stack on the target ME host). The sockfd (which corresponds to the MPTCP session identifier) can be modified if it is already in use on the target ME host.
[0292] The ME App on the source (initial) ME host obtains information about the MPTCP session to be transferred from the local MPTCP stack (possibly using a socket interface), i.e., SRC App → obtains the information to be transferred (sockfd) → SRC MPTCP. The ME App on the initial ME host transfers the MPTCP session information to the ME App on the target ME host, i.e., SRC App → transfers MPTCP session-related information → DST App. The ME App on the target ME host uses the received information about the MPTCP session (possibly using a socket interface) to configure the local MPTCP stack, i.e., DST App → sets the MPTCP information from the transfer (sockfd) → DST MPTCP.
[0293] MPTCP session adaptation on the target ME host can be handled via the MPTCP-specific API. The MPTCP event "MPTCP Session Transfer Complete" can be used for this purpose. When the MPTCP transfer is complete, the ME App can receive this event and specify a new socket number to be used at that point to continue communication with the remote peer (i.e., WTRU). The sockfd can remain the same, meaning it can remain unchanged if it has not already been used on the target ME host. If the sockfd value has already been used, a new number can be generated by the MPTCP stack and associated with the transferred MPTCP session. This new number can be locally sent to the ME App on the target ME host via the new MPTCP-specific event. MPTCP stack → MPTCP Transfer Complete ((original_sockfd, new_sockfd) → ME App.
[0294] Although the features and elements described above are in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. Furthermore, the methods described herein can be implemented in computer programs, software, or firmware embedded in a computer-readable medium and executed by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, buffer memory, semiconductor storage devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM discs and digital multipurpose discs (DVDs). The processor associated with the software can be used to implement a radio frequency transceiver used in a WTRU, UE, terminal, base station, RNC, or any host computer.
Claims
1. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: Data services are transmitted via a Transmission Control Protocol (TCP) session and a Multipoint Transmission Control Protocol (MPTCP) stack running on the WTRU. Anchored to the first mobile edge (ME) host device; The data service is exchanged with the server application through a first MPTCP sub-stream on the first ME host device, wherein the first MPTCP sub-stream is configured with a normal priority, wherein the normal priority means that the sub-stream is now to be used; Anchored to the second ME host device; In response to anchoring to the second ME host device, a first message is received from the second ME host device, the first message instructing the WTRU to establish a second MPTCP substream; In response to the first message, the establishment of the second MPTCP sub-stream is accepted, wherein the second MPTCP sub-stream is configured to pre-allocate priority, wherein the pre-allocate priority means that the sub-stream is created but has not yet been used to exchange data services; After the second MPTCP substream is established, a second message is received from the second ME host device, which indicates that the second MPTCP substream is configured to the normal priority to start exchanging data services. In response to the second message, the configuration of the second MPTCP sub-stream is changed from the pre-allocated priority configuration to the regular priority configuration, and the data service is exchanged with the server application through the second MPTCP sub-stream on the second ME host device; Change the configuration of the first MPTCP sub-stream to an unavailable priority, where unavailable priority means that the sub-stream is maintained but no longer used for data services; and Close any other MPTCP sub-streams associated with the first ME host device.
2. The method according to claim 1, wherein the second message includes an MP_PRIO message.
3. The method according to claim 1, wherein the first message includes an MP_JOIN message.
4. A wireless transmit / receive unit (WTRU), the WTRU comprising: The processor is configured to transmit data traffic via a Transmission Control Protocol (TCP) session with a Multipoint Transmission Control Protocol (MPTCP) stack running on the WTRU. The processor is configured to be anchored to a first mobile edge (ME) host device; The processor is configured to exchange the data service with the server application via a first MPTCP sub-stream on the first ME host device, wherein the first MPTCP sub-stream is configured with a normal priority, wherein the normal priority means that the sub-stream is now to be used; The processor is configured to be anchored to a second ME host device; The processor is configured to receive a first message from the second ME host device in response to anchoring to the second ME host device, the first message instructing the WTRU to establish a second MPTCP substream; The processor is configured to accept the establishment of the second MPTCP substream in response to the first message, wherein the second MPTCP substream is configured to be pre-allocated priority, wherein the pre-allocated priority means that the substream is created but has not yet been used to exchange data services; The processor is configured to receive a second message from the second ME host device after the second MPTCP substream is established, the second message indicating that the second MPTCP substream be configured to the normal priority to begin exchanging data services; The processor is configured to, in response to the second message, change the configuration of the second MPTCP substream from a pre-allocated priority configuration to a regular priority configuration, and exchange the data service with the server application through the second MPTCP substream on the second ME host device; The processor is configured to change the configuration of the first MPTCP substream to an unavailable priority, wherein the unavailable priority means that the substream is maintained but no longer used for data services; and The processor is configured to shut down any other MPTCP sub-streams associated with the first ME host device.
5. The WTRU of claim 4, wherein the second message includes an MP_PRIO message.
6. The WTRU of claim 4, wherein the first message includes an MP_JOIN message.
Citation Information
Patent Citations
MPTCP connection mobile management method and apparatus
CN104285472A
Mobility management method, apparatus, and system
CN105874830A
Access management with multipath transport
CN106465436A
Multi-path transmission control protocol proxy service
EP2538637A2
Service transmission method, apparatus and device
WO2017107203A1
