Method, architecture, apparatus and system for offloading data traffic flows from edge network of cellular network to non-cellular network

Abstract

A process, method, architecture, apparatus, system, apparatus, and computer program product for offloading a flow of data traffic received by a wireless transmit-receive unit (WTRU) via an edge network of a cellular network or transmitted by the WTRU via the edge network of the cellular network to a non-cellular network. The WTRU may determine that a stream of data traffic received and transmitted by the WTRU is transmitted by the edge network and take appropriate action.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 303,602, filed on January 27, 2022, which is incorporated herein by reference. Background Art

[0003] The present disclosure relates generally to the fields of communications, software, and coding, including, for example, methods, architectures, apparatuses, and systems for offloading traffic associated with edge services and provided to user equipment to a wireless local area network. Summary of the invention

[0004] A user equipment (UE) or wireless transmit-receive unit (WTRU) may be equipped with a wireless local area network (WLAN) (e.g., WiFi and radio) that allows the WTRU to obtain connectivity to a data network without utilizing a 5G system. However, when a WLAN (e.g., WiFi) network becomes available and the WTRU chooses to stop using the 5G system for data network connectivity, it cannot be assumed that the WTRU will be able to continue to access the same edge data network available via the 5G system. Therefore, when the WTRU moves to a location where it is preferred to use the WLAN (e.g., WiFi) to access a data network without traversing the 5G system, the WTRU will lose access to any edge services that the WTRU accessed via the 5G system. Improvements are therefore needed.

[0005] According to one aspect of the present disclosure, in accordance with the described embodiments and appended claims, there is provided a method implemented by a WTRU having a WLAN radio access technology (RAT) transceiver and a cellular network RAT transceiver.

[0006] According to another aspect of the present disclosure, embodiments of a WTRU having a WLAN radio access technology (RAT) transceiver and a cellular network RAT transceiver are described and claimed in the appended claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] A more detailed understanding can be obtained from the following detailed description, which is given by way of example in conjunction with its accompanying drawings. As with the detailed description, the figures in such drawings are examples. Therefore, the drawings (figures) and specific embodiments should not be considered limiting, and other equally effective examples are possible and contemplated. In addition, like reference numerals ("ref.") in the figures indicate similar elements, and wherein:

[0008] Figure 1A is a system diagram illustrating an example communication system;

[0009] Figure 1B is an example that can be Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system;

[0010] Figure 1C is an example that can be Figure 1A a system diagram of an example Radio Access Network (RAN) and an example Core Network (CN) used within the illustrated communication system;

[0011] Figure 1D is an example that can be Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0012] Figure 2 Different SSC modes in 5G system are shown;

[0013] Figure 3 is the user plane architecture for the uplink classifier;

[0014] Figure 4 It is an overview of the 5GC connection model for edge computing;

[0015] Figure 5 is a multi-homed PDU session illustrating local access to the same DN;

[0016] Figure 6 It is an architecture for enabling edge applications;

[0017] Figure 7 Shows WTRU handling of edge traffic and non-edge traffic when non-seamless offloading becomes possible;

[0018] Figure 8 The edge service indication in the URSP rule is shown;

[0019] Fig. 9 shows edge service indication in NAS notification;

[0020] Fig.10 is a flow chart of a method according to an embodiment; and

[0021] Fig.11 is a flow chart of a method according to an embodiment. DETAILED DESCRIPTION

[0022] In the following detailed description, many specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it should be understood that such embodiments and examples can be practiced without some or all of the specific details set forth herein. In other cases, well-known methods, processes, components and circuits are not described in detail to avoid blurring the following description. In addition, the embodiments and examples not specifically described herein can be practiced in place of the embodiments and other examples explicitly, implicitly and / or inherently described, disclosed or otherwise provided (collectively referred to as "provided") herein, or practiced in combination with these embodiments and examples. Although various embodiments are described and / or claimed herein, wherein devices, systems, equipment, etc. and / or any of their elements perform operations, processes, algorithms, functions, etc. and / or any part thereof, it should be understood that any embodiments described herein and / or protected by the claims assume that any device, system, equipment, etc. and / or any of its elements are configured to perform any operations, processes, algorithms, functions, etc. and / or any part thereof.

[0023] Example Communication System

[0024] The methods, devices, and systems provided herein are well suited for communications involving both wired and wireless networks. Figures 1A to 1D An overview of various types of wireless devices and infrastructure is provided, wherein various elements of the network can utilize the methods, apparatuses, and systems provided herein, perform the methods, apparatuses, and systems provided herein, be arranged according to the methods, apparatuses, and systems provided herein, and / or be adapted and / or configured for the methods, apparatuses, and systems provided herein.

[0025] Figure 1A is a system diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ 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 (ZT) unique word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0026] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the UE 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to send and / or receive wireless signals and may include (or may be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0027] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to, for example, facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the network 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node B (NB), an evolved Node B (eNB), a Home Node B (HNB), a Home evolved Node B (HeNB), a gNode B (gNB), a NR Node B (NR NB), a site controller, an access point (AP), a wireless router, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0028] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.

[0029] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0030] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access (HSUPA).

[0031] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).

[0032] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using New Radio (NR).

[0033] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for example using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

[0034] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Enhanced Data Rates for Evolution (EDGE), GSM EDGE (GERAN), etc.

[0035] Figure 1AThe base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of a microcell, a picocell, or a femtocell. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0036] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the accompanying drawings, the CN 106 / 115 may be used to provide a plurality of WTRUs 102a, 102b, 102c, 102d, and / or ... Figure 1A Although not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs any of GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.

[0037] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 114 or a different RAT.

[0038] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0039] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other elements / peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0040] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of 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), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together, such as in an electronic package or chip.

[0041] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station via an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In one embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, an IR, UV or visible light signal. In one embodiment, the send / receive element 122 may be configured to send and / or receive both an RF signal and an optical signal. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.

[0042] Although the transmit / receive element 122 Figure 1B 102 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0043] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0044] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0045] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0046] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0047] The processor 118 may also be coupled to other components / peripherals 138, which may include one or more software modules / units and / or hardware modules / units that provide additional features, functionality, and / or wired or wireless connectivity. For example, the components / peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (e.g., for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, FM radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. Components / peripherals 138 may include one or more sensors, which may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0048] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via hardware (e.g., a choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via the processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0049] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with one embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0050] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0051] Each of the eNodeBs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to manage radio resource management decisions, handover decisions, user scheduling in the uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0052] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements is depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0053] The MME 162 may be connected to each of the evolved Node-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0054] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0055] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0056] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.

[0057] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

[0058] In a representative embodiment, the other network 112 may be a WLAN.

[0059] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may 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 may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link establishment (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0060] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0061] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0062] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by the transmitter STA. At the receiver of the receiver STA, the above-mentioned operation for 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC) layer, entity, etc.

[0063] 802.11af and 802.11ah support operating modes below 1 GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0064] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only a 1MHz operating mode) is sending to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.

[0065] 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. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0066] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As noted above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0067] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the WTRUs 102a, 102b, 102c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may send multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).

[0068] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., including varying numbers of OFDM symbols and / or varying absolute time lengths).

[0069] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.

[0070] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to manage radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0071] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one data network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0072] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c, for example, based on the type of services used by the WTRU 102a, 102b, 102c. For example, different network slices may 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, services for MTC access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as Wi-Fi.

[0073] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure the traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy implementation and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0074] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, for example, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0075] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0076] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to any of the following may be performed by one or more simulation elements / devices (not shown): WTRU 102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182b, UPF 184a-184b, SMF 183a-183b, DN 185a-185b and / or any other element / device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0077] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communications to perform testing.

[0078] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) can be used by the simulation device to send and / or receive data.

[0079] introduction

[0080] Listed below are some acronyms used in this document.

[0081] AC - Application Client

[0082] AMF – Access and Mobility Function

[0083] AN – Access Network

[0084] API - Application Programming Interface

[0085] AT - Attention

[0086] DN – Data Network

[0087] DNN - Data Network Name

[0088] EAS - Edge Application Server

[0089] ECS - Edge Configuration Server

[0090] EDN - Edge Data Network

[0091] EEC - Edge Enabled Client

[0092] EES - Edge Enabling Server

[0093] ePDG - Evolved Packet Data Gateway

[0094] FQDN - Fully Qualified Domain Name

[0095] GUI - Graphical User Interface

[0096] IP – Internet Protocol

[0097] LADN - Local Area Data Network

[0098] MT – Mobile Terminated

[0099] NAS - Non Access Stratum

[0100] NAS-MM - NAS Mobility Management

[0101] NAS-SM -NAS Session Manager

[0102] NSSAI - Network Slicing Selection Assistance Information

[0103] N3IWF - Non-3GPP Interworking Function

[0104] PCF - Policy Control Function

[0105] PDU – Protocol Data Unit

[0106] PLMN - Public Land Mobile Network

[0107] PSA - PDU Session Anchor

[0108] RAT – Radio Access Technology

[0109] RSD - Routing Descriptor

[0110] SMF - Session Management Function

[0111] SSC - Session and Service Continuity

[0112] SSID - Service Set Identifier

[0113] S-NSSAI - Single NSSAI

[0114] TE - Terminal Equipment

[0115] UE - User Equipment

[0116] UL CL - Uplink Classifier

[0117] UPF – User Plane Function

[0118] URSP - UE (WTRU) Routing Policy

[0119] WLAN - Wireless Local Area Network

[0120] Although most often described herein with examples relating to the fifth generation technology standard for broadband cellular networks (5G), the present principles are not limited to 5G and may be applicable to 6G technology or other subsequent technology standards (further indicated as "xG") for broadband cellular networks.

[0121] In the context below, "accessing" or "using" or "utilizing" edge computing resources refers to the WTRU transmitting IP packets to and receiving IP packets from an application server residing in the edge network.

[0122] In the context below, an edge network may be any data network (eg, a packet data network). However, an edge data network is typically a data network that is geographically closer to the WTRU than some larger data networks (such as the Internet).

[0123] In the following context, application traffic refers to data packets (ie, IP packets) transmitted to and from applications hosted in the WTRU.

[0124] In this document, the term Wireless Local Area Network (WLAN) is used. Non-limiting examples of WLAN are Wi-Fi networks, WiMAX networks, and Bluetooth networks. In the context of this document, a WLAN may also be referred to as a "non-cellular network".

[0125] This document discusses how the WTRU communicates with the AMF. The communication between the WTRU and the AMF is done over the N1 interface using the NAS protocol.

[0126] This document discusses how the WTRU communicates with the SMF. The communication between the WTRU and the SMF is done via NAS signaling (i.e., the communication between the WTRU and the SMF is done via the AMF over the N1 interface). The communication protocol between the UE and the SMF is called NAS-SM.

[0127] In the context below, the term "non-seamless (WLAN) offload" is used to indicate a connection change that results in the removal of at least some data traffic between a WTRU and a data network (e.g., the Internet) from an edge network that provides the WTRU's connection to the data network, and the replacement of the WTRU's connection to the data network via the edge network by the connection to the data network via the WLAN for the at least some data traffic. The term "offload" indicates the use of a supplementary network technology (such as WLAN) to exchange data with a data network that originally used a cellular network and is "offloaded" to a different network (such as WLAN). Instead of "offload", the term "handover" may also be used. The advantages of offloading include reducing the amount of data carried on the cellular frequency band, freeing up bandwidth for other uses / users, and improving connectivity in (geographic) locations (e.g., indoor or outdoor locations) where cellular network coverage is poor. The term "non-seamless" is used in this context to indicate that the connection change results in the interruption of at least some data traffic due to the connection change; for example, a data / streaming session may be interrupted. A seamless handover does not significantly impact the user experience, while a "non-seamless" offload / handover does. For example, a "non-seamless" offload / handover may cause the WTRU to completely lose connectivity to the service, or may cause the WTRU to temporarily disconnect and reconnect to the service via a new (i.e., WLAN) network connection. Non-seamless WLAN offload is achieved by the WTRU acquiring a local IP address on the WLAN, certain IP flows are routed via the WLAN without passing through the 3GPP core network, and no IP address preservation in the core network is provided between the WLAN and 3GPP accesses for mobility.

[0128] In the context below, the phrase “non-seamless offloading is / becomes available / possible” is used to indicate that the WTRU is / becomes within the wireless coverage of a WLAN and has established / can establish access to a Wi-Fi network that provides access to a data network (e.g., the Internet) without using the 5G system.

[0129] Session and Service Continuity (SSC) Mode

[0130] Data session continuity and session continuity are key to ensure that the user experience is not interrupted regardless of any changes in the WTRU IP address or changes in the core network anchor point. For example, the continuity of the IP session can be maintained by preserving the WTRU's PDU session IP address (session address) (see below) regardless of the WTRU's mobility.

[0131] In the 5G system architecture, Session and Service Continuity (SSC) support is able to address various continuity requirements for different applications and services for WTRUs. However, even if service continuity is required, not all applications require guaranteed IP session continuity. The 5G system provides different types of session continuity depending on the WTRU or service type. The 5G system uses the PDU session frame (session frame) to carry application services. When events such as changes in IP addresses and WTRU mobility occur, application services have varying requirements on how application layer sessions and services remain continuous (i.e., seamless).

[0132] Each PDU session in the 5G system is associated with one of the three SSC modes. The 5G system allows service providers to set a specific SSC mode for a given PDU session. Some characteristics related to the SSC mode:

[0133] -SSC mode determines the flow of packets across the network in mobility scenarios;

[0134] -The PDU session is configured to use a specific "Session and Service Continuity" (SSC) mode;

[0135] -3GPP specifications provide three different types of SSC modes;

[0136] - The WTRU may request a specific mode using the "SSC Mode" field within NAS using the PDU Session Establishment Request;

[0137] -SMF uses PDU session establishment to accept the "Selected SSC Mode" used within NAS

[0138] field to specify the mode of allocation;

[0139] -SSC Mode 1 and SSC Mode 2 can be applicable to both IP and Ethernet type PDUs, while SSC Mode 3 is applicable only to IP type PDU sessions.

[0140] exist Figure 2The different SSC modes in a 5G system are illustrated with the help of . The figure shows: a diagram of SSC mode 1 (200) with one UPF (202) for a service (201), two gNBs (203, 204), and one WTRU (205); a diagram of SSC mode 2 (220) with two UPFs (223, 224) for different services (221, 222), two network nodes (gNBs) (225, 226), and one WTRU (227); and a diagram of SSC mode 3 (240). For the SSC modes, there are two network nodes (gNBs) with two UPFs (243, 244) for different services (241, 242), two network nodes (gNBs) (245, 247), one WTRU (248), and a temporary data path (246) between UPF #1 (243) and the gNB (247).

[0141] For a PDU session of SSC mode 1 (200), the UPF (202) that acts as the PDU session anchor when the PDU session is established for the service (201) is maintained regardless of the mobility of the WTRU (205). For PDU session types of IPv4 or IPv6 or IPv4v6 type, the IP address is retained. In this case, the user plane function (UPF) that acts as the PDU session anchor is maintained (remains the same) until the WTRU (205) releases the PDU session.

[0142] For a PDU session of SSC mode 2 (220), if the PDU session has a single PDU session anchor, the network may trigger the release of the PDU session and instruct the WTRU to immediately establish a new PDU session to the same data network. The triggering condition depends on the operator policy, for example, a request from an application function, based on load status, etc. When establishing a new PDU session, a new UPF (224) may be selected to act as the PDU session anchor. A use case for this is that if there is a load balancing requirement at the anchor UPF, the network may release the connection. Here, the PDU session may be moved to a different anchor UPF by releasing the existing PDU session and then establishing a new PDU session.

[0143] For PDU sessions in SSC Mode 3 (240), the network allows the WTRU (248) to establish a connection to the same data network via a new PDU session anchor before the connection between the WTRU and the previous PDU session anchor is released. This is illustrated by the dashed line (246) between the gNB (247) and UPF #1 (243). The network maintains the provided connection to the WTRU (248), but there may be some impact during certain procedures. For example, if the anchor UPF changes, the IP address assigned to the WTRU (248) will be updated, but the change procedure will ensure that the connection is maintained, i.e., the connection towards the new anchor UPF (244) is established before releasing the connection to the old anchor UPF (243).

[0144] UE (WTRU) Routing Selection Policy (URSP)

[0145] UE (WTRU) Routing Selection Policy (URSP) rules are policies used by the WTRU to determine how to route outgoing traffic. Traffic may be routed to an established PDU Session, may be offloaded to a non-3GPP access outside of a PDU Session, may be routed outside of a PDU Session via a ProSe Layer 3 WTRU to Network Relay, or may trigger the establishment of a new PDU Session.

[0146] Note that a WTRU application may request network connectivity using non-seamless offload or ProSe layer 3 WTRU to network relay offload. In this case, the WTRU will use non-seamless offload for the application without evaluating the URSP rules. Otherwise, the WTRU will use the URSP rules to determine how to route the application traffic.

[0147] Each URSP rule consists of 2 parts. The first part of the URSP rule is a service descriptor used to determine when the rule is applicable. When each component in the service descriptor matches the corresponding information from the application, it is determined that the URSP rule is applicable. The second part of the URSP rule is a routing descriptor (RSD) list. The routing descriptor list contains one or more routing descriptors. The RSDs are listed in order of priority and describe the characteristics of PDU sessions that can be used to carry uplink application data. The characteristics of a PDU session include SSC mode, DNN, and S-NSSAI. The RSD may alternatively include a non-seamless offload indication, which indicates that the service can be transmitted outside any PDU session via a non-3GPP access (e.g., WiFi).

[0148] For each newly detected application, the WTRU evaluates the URSP rules in order of rule priority and determines whether the application matches the traffic descriptor of any URSP rule. When a URSP rule is determined to be applicable for a given application, the WTRU selects a routing descriptor within that URSP rule in order of routing descriptor priority.

[0149] When a valid routing descriptor is found, the WTRU determines if there is an existing PDU Session that matches all the components in the selected routing descriptor. When there is a matching PDU Session, the WTRU associates the application with the existing PDU Session, i.e., the WTRU routes the traffic of the detected application on this PDU Session. If none of the existing PDU Sessions matches the RSD, the WTRU attempts to establish a new PDU Session using the values ​​specified by the selected routing descriptor.

[0150] Once the traffic from the application is associated with a PDU session, an event may cause the WTRU to re-evaluate the URSP rules and associate the traffic from the application with a different PDU session. Two examples of events that may trigger a URSP re-evaluation are a re-evaluation timer that depends on the specific implementation and the WTRU establishing access to a WLAN network that provides Internet access without using the 5G system (i.e., non-seamless offload becomes possible).

[0151] The traffic descriptor can be an application descriptor, IP descriptor, domain descriptor, non-IP descriptor, DNN or connection capability. The IP descriptor can be a target IP 3-tuple (i.e., IP address or IPv6 network prefix, port number, protocol ID for protocol over IP).

[0152] Wi-Fi connection

[0153] Different types of Radio Access Technologies (RATs) can be used to access the 5G system and get a connection to a data network such as the Internet or an edge data network. NR and WiFi are two types of RATs that can be used to access the 5G system and get a connection to a data network such as the Internet or an edge data network.

[0154] The WTRU may be equipped with a WLAN (e.g., WiFi, WiMAX, Bluetooth) radio that can be used to obtain a connection to a data network such as the Internet or an edge data network without using the 5G system. A common example of such a connection occurs when a smartphone discovers a WiFi SSID, connects to the network identified by that SSID, and obtains an Internet connection that does not traverse the 5G system. This type of network connection may be generally referred to as a "non-seamless offload" or "non-seamless WLAN offload." This type of network connection change is generally referred to as a "non-seamless offload" because when the data flow moves ("offloads") from a cellular network to a non-cellular network (i.e., to a WLAN), the data session anchor point (e.g., UPF) must change, and typically the WTRU will not even be able to automatically connect to the same data network. Since the IP address and data network connection cannot be maintained, the user will experience some degree of service interruption (e.g., the user may need to restore the connection to the data network via a connection to a non-cellular network). Therefore, the movement of data from one network to another does not appear seamless to the user.

[0155] Connection Model in 5G System

[0156] NR systems such as 5G systems support multiple connection models to enable WTRUs to access edge computing resources.

[0157] Three connection models for accessing edge computing resources are described below and are presented in Figure 4 Illustrated are WTRUs (401, 421, 441), UPFs (402, 422, 442, 424, 445), data networks (403, 423, 443, 425, 446), radio sites (450), local sites (451), and central sites (452).

[0158] One connectivity option for accessing edge computing resources is called a "distributed anchor point" (400). When this option is used, the PSA UPF (402) is located in the edge network (451) (i.e., close to the location of the WTRU). The PDU sessions used to carry traffic to / from the PSA UPF may use SSC Mode 2 or SSC Mode 3. Therefore, the PSA UPF may change when the location of the WTRU changes. The process for changing the PSA UPF is determined based on whether SSC Mode 2 or SSC Mode 3 is used.

[0159] The second connection option is called "Session Break" (420). When this option is used, the PDU session used to carry traffic to / from the edge network may be associated with 2 PSA UPFs. The first PSA UPF (424) may be called a C-PSA and may be located in a central site (452). The central site is not necessarily geographically close to the WTRU. The second PSA UPF (422) may be called an L-PSA and may be located in a local network (451). The local network is typically geographically close to the WTRU (421). This connection model is Figure 3 The figure illustrates AMF (301), SMF (302), WTRU (303), access network (304), UPF uplink classifier (305), UPF PDU session anchor 1 (306), first data network (307), UPF PDU session anchor 2 (308) and second data network (309). Insertion or removal of UL CL in a PDU session is determined and controlled by the SMF. The SMF can decide to insert a UPF supporting UL CL function in the data path of a PDU session during or after PDU session establishment, or remove a UPF supporting UL CL function from the data path of a PDU session after the PDU session is established. In a 5G system, if a ULCL UPF is added to or removed from a PDU session, the SMF does not notify the WTRU.

[0160] The third connection option is called "Multiple PDU Sessions" (440). When this option is used, the WTRU (441) uses PDU sessions to access edge computing resources in the edge network (451). In other words, the PSA UPF (442) of the PDU session is in the edge network. When the WTRU moves, SSC Mode 3 can be used to change the PSA UPF of the edge network PDU session. When this option is used, the WTRU uses other PDU sessions to access resources that are not in the edge data network. The PSA UPF (445) of these other PDU sessions are not in the edge network and are typically not geographically close to the WTRU.

[0161] URSP rules may be used to configure the WTRU to use any of the above connection options. URSP rules are required in order to use the "Multi-PDU Session" connection model.

[0162] IPv6 multi-homing for PDU sessions in 5G systems

[0163] A multi-host PDU session may also provide access to the data network via more than one PDU Session Anchor Point. Different user plane paths leading to different PDU Session Anchor Points branch at a "common" UPF called a UPF that supports the "branching point" functionality. The branching point forwards UL traffic towards different PDU Session Anchor Points and merges DL traffic to the WTRU (i.e., merges traffic from different PDU Session Anchor Points on the link towards the WTRU).

[0164] Insertion or removal of UPF supporting branch points is determined and controlled by SMF. SMF can decide to insert UPF supporting branch point function in the data path of PDU session during or after PDU session establishment, or remove UPF supporting branch point function from the data path of PDU session after PDU session establishment.

[0165] Multi-homed PDU sessions may be used to support situations where a WTRU needs to access both local services (e.g., a local server) and central services (e.g., the Internet). Figure 5 This figure is similar to Figure 3 , the difference is that UPF branch point 501 replaces Figure 3 UPF uplink classifier 305.

[0166] When the SMF (302) removes or adds a branch point, the SMF notifies the WTRU (303) of the updated IPv6 prefix. The SMF transmits IPv6 multi-homed routing rules to the WTRU to influence the source IPv6 prefix selection in the IPv6 Router Advertisement (RA) message. The message is transmitted via the UPF.

[0167] LADN Information

[0168] The 5G system is able to inform the WTRU about the data networks available to the WTRU and about the capabilities of the data networks available to the WTRU. The "LADN Information" information element is a mechanism by which the network can transmit the DNN to the WTRU and the geographical area where the WTRU can use the data network.

[0169] The LADN information (i.e., LADN service area information and LADN DNN) is provided to the WTRU by the AMF during the registration procedure or the WTRU configuration update procedure. For each LADN DNN configured in the AMF, the corresponding LADN service area information includes the set of tracking areas belonging to the registration area assigned to the WTRU by the AMF (i.e., the intersection of the LADN service area and the assigned registration area).

[0170] When the WTRU indicates to the AMF that it is capable of receiving LADN information in a registration request, the LADN information may be transmitted by the AMF to the WTRU.

[0171] Application layer architecture for enabling edge applications

[0172] Figure 6 An example architecture for edge applications is illustrated. From left to right, a WTRU (601), a (3GPP) core network (604), and an edge data network (605) are shown.

[0173] A WTRU (601) may host an edge enabled client (EEC) (602). An EEC is an application that provides services to other applications hosted on the WTRU and accesses services in an edge data network.

[0174] The WTRU may host an application client (AC) (603). An AC is an application that accesses services in an edge data network.

[0175] The EDGE-5 interface (line between the EEC and the AC) is an interface for exchanging information between the AC and the EEC. The EDGE-5 interface may be an API-based interface.

[0176] Edge Application Server (EAS) (607) and Edge Enablement Server (EES) (606) are types of servers that provide edge services to application clients and EEC. EAS and EES are typically deployed in an edge data network (605) that is geographically close to a WTRU.

[0177] The Edge Configuration Server (ECS) (608) is a server that transmits configuration information to the EEC. The configuration information includes information about the EES and EAS accessible to the EEC.

[0178] Overview

[0179] The common theme of the above edge computing connection models is that they all rely on the 5G system to provide the WTRU with access to the PSA UPF in the edge network. It is also worth noting that all three connection models allow the PSA UPF to change when the WTRU's location changes.

[0180] As described above, the WTRU may be equipped with a WLAN (e.g., WiFi) radio that allows the WTRU to obtain connectivity to a data network without utilizing a 5G system. However, when a WLAN (e.g., WiFi) network becomes available and the WTRU chooses to stop using the 5G system for data network connectivity, it cannot be assumed that the WTRU will be able to continue to access the same edge data network available via the 5G system. Therefore, when the WTRU moves to a location where it is preferred to use the WLAN (e.g., WiFi) to access a data network without traversing the 5G system, the WTRU will lose access to any edge services that the WTRU accessed via the 5G system.

[0181] According to one embodiment, the 5G system is enhanced so that the WTRU can determine which PDU session or what service is utilizing the edge service.

[0182] According to another embodiment, once the WTRU makes this determination, the WTRU can terminate its application layer connection to the edge service in a manner that allows the application to be alerted of the impending termination, or selectively use non-seamless offload for some application layer services and not use non-seamless offload for other application layer services.

[0183] In the following, enhancements to a radio system (e.g., a 5G, 6G, or xG radio system) are described that enable a WTRU to determine what traffic is being routed to an edge data network. In addition, in the following, actions that a WTRU may take when an edge data network becomes inaccessible to the WTRU via a preferred access network because the WTRU is using the radio system to access the edge data network and the WTRU has determined that it is preferred that at least some of the WTRU's traffic be routed to and from the data network via a WLAN network without traversing the 5G system (i.e., the WTRU has detected that non-seamless WLAN offloading may be used). This process is described in Figure 7 Example in.

[0184] In step 701, the WTRU is registered to the 5G system and non-seamless WLAN offload is not available.

[0185] The WTRU establishes multiple PDU sessions in step 702. At least one PDU session is used to route data to / from the edge data network.

[0186] In step 703, non-seamless WLAN offload becomes possible for the WTRU; that is, the WTRU is within the radio coverage of the WLAN and has access to the WLAN.

[0187] In step 704, the WTRU identifies which traffic flows are routed to the edge network. This is not possible in current 5G system designs. Note that the order of steps 3 and 4 is interchangeable.

[0188] In step 705a, the WTRU releases some PDU Sessions and uses non-seamless offload for traffic routed via the released PDU Sessions.

[0189] In step 705b, the WTRU determines how to handle edge-routed traffic (i.e., keep the traffic in the 5G system, terminate it, or try to move it gracefully). This is not possible in current 5G system designs.

[0190] Several embodiments are described below involving how the WTRU may determine what services are being routed to the edge data network. These embodiments are complementary, and which embodiment the WTRU uses may depend on which connection models the WTRU uses to access the edge data network. For example, according to one embodiment, when the connection model of the PDU session is "session interruption" (i.e., when the SMF independently decides to route some services to the edge), the WTRU may receive an indication from the SMF that the PDU session is being used to access the edge data network. According to another embodiment, when the connection model of the PDU session is "distributed anchor point" or "multiple PDU sessions" (i.e., when the WTRU establishes a PDU specifically to the edge DNN or uses SCC mode 2 or SCC mode 3 so that the PSA UPF will always be located close to the WTRU), the WTRU may use URSP rules to determine that the PDU session is being used to access the edge data network. These two embodiments may exist simultaneously.

[0191] Detecting edge services

[0192] Embodiments of a method implemented by a WTRU to associate an edge service indication with a PDU session or service associated with a service descriptor are described.

[0193] When an edge service indication is associated with a PDU session and / or a service that matches a service descriptor, the WTRU may use the indication as a hint that the associated PDU session may be used to access services that are only available in the edge data network and that abruptly switching the associated application service to a different PDU session or terminating the PDU session may impact any user experience associated with the application service.

[0194] Several embodiments of how a WTRU may receive an edge service indication from the network are described herein. Not all WTRUs may be able to receive or understand an edge service indication. Therefore, before receiving an edge service indication, the WTRU may indicate to the network that it supports receiving an edge service indication in a registration request or a PDU session establishment request. Alternatively, when the WTRU decides to use a PDU session for data that may be routed to the edge, the WTRU may request an edge service indication in a PDU session establishment request or a PDU session modification request. For example, if a PDU session is being used to route data to an edge data network, the WTRU may indicate to the SMF that the WTRU expects an edge service indication.

[0195] When re-evaluating URSP rules, the WTRU may use this edge service indication to help determine how to handle existing PDU sessions. For example, when the WTRU is connected to a WLAN network, the URSP rules may be re-evaluated. The following embodiments relate to how the WTRU may use edge service indications to influence how PDU sessions are handled when the WTRU is connected to a WLAN network.

[0196] Implementations Related to RSD-Based Indications

[0197] According to one embodiment, the WTRU may receive an edge service indication as part of the RSD.

[0198] The WTRU receives one or more URSP rules, and each URSP rule includes a traffic descriptor and one or more RSDs. According to one embodiment, the format of the RSD may be enhanced so that the WTRU may receive one or more RSDs including an edge service indication.

[0199] According to one embodiment, when the WTRU evaluates the RSD or URSP rules including the edge service indication and determines to establish a new PDU session using information from the RSD, the WTRU may associate the PDU session with the edge service indication.

[0200] According to one embodiment, when the WTRU evaluates the RSD of a URSP rule including an edge service indication, determines that the information in the RSD matches an existing PDU session and determines to use the existing PDU session to transmit a service matching the service of the URSP rule, the WTRU may associate the existing PDU session with the edge service indication.

[0201] According to one embodiment, when the WTRU evaluates the URSP rule and determines to use a new or existing PDU session that matches an RSD that includes an edge service indication, the WTRU may associate the service descriptor of the URSP rule with the edge service indication. In other words, the WTRU may determine to associate any service that matches the service descriptor and any PDU session that carries the service with the edge service indication.

[0202] Implementation related to traffic descriptor-based indication

[0203] According to one embodiment, the WTRU may receive an edge service indication as part of a traffic descriptor.

[0204] The WTRU receives one or more URSP rules, and each URSP rule includes a service descriptor and one or more RSDs. According to one embodiment, the format of the service descriptor may be enhanced so that the WTRU can receive a service descriptor including an edge service indication. Alternatively, according to one embodiment, if the edge service indication applies to all services matching the service descriptor, the edge service indication may be included in all RSDs of the URSP rules associated with the service descriptor. The above describes an embodiment of how the edge service indication may be included in the RSD.

[0205] According to one embodiment, when the WTRU determines that the service matches the service descriptor of the URSP rule, the service descriptor is associated with the edge service indication, and the WTRU determines to use the information from the RSD of the URSP rule to establish a new PDU session, the WTRU can associate the PDU session with the edge service indication.

[0206] According to one embodiment, when the WTRU determines that the service matches the service descriptor of the URSP rule, the service descriptor is associated with the edge service indication, the WTRU determines that the information in the RSD of the URSP rule matches the existing PDU session, and determines to use the existing PDU session to transmit the service matching the service of the URSP rule, the WTRU can associate the PDU session with the edge service indication.

[0207] Figure 8 An example flow of an implementation of how a WTRU (810) may receive an edge service indication in a URSP rule and use the edge service indication to determine how to handle edge traffic when non-seamless offload becomes available is shown in sequence chart form.

[0208] In 801, the WTRU transmits a registration request to the network. As described above, the registration request may include an indication that the WTRU is capable of receiving or understanding edge service indications.

[0209] In 802, the AMF (820) obtains the URSP rules of the WTRU from the PCF (830).

[0210] The WTRU receives URSP rules from the network at 803. As described above, the Registration Accept may include URSP rules including an edge service indication.

[0211] In 804, the WTRU uses the edge service indication in the URSP rules to detect which traffic is being routed to the edge data network.

[0212] In 805, the WTRU determines that non-seamless offload is available.

[0213] In 806, the WTRU takes action to handle the edge-routed traffic (i.e., determines to terminate the application traffic, attempts to move the traffic to non-seamless offload, or retains the traffic in the 5G system).

[0214] Implementations Related to Indications from the SMF to the WTRU

[0215] As mentioned above, the SMF may insert a branch point UPF or a UL CL UPF in a PDU session. The reason why the SMF adds a branch point UPF or a UL CL UPF may be to forward some services from the PDU session to the edge data network.

[0216] According to one embodiment, when a branch point UPF or UL CL UPF is added to a PDU session, the network may transmit an indication to the WTRU that the PDU session is being used to access edge services. According to one embodiment, the notification may be referred to as an edge service indication. According to one embodiment, when the WTRU receives the edge service indication, the WTRU may associate the notification with the PDU session. According to one embodiment, the notification may include the PDU session ID of the PDU session associated with the notification. According to one embodiment, when the SMF inserts the branch point UPF or UL CL UPF, the edge service indication may be transmitted to the WTRU by the SMF in a NAS-SM message. In addition, according to one embodiment, when the branch point UPF or UL CL UPF is removed, the SMF may transmit a notification to the WTRU to indicate to the WTRU that the branch point UPF or UL CL UPF has been removed. According to one embodiment, when the WTRU receives a notification that the branch point UPF or UL CL UPF has been removed, the WTRU may disassociate the edge service indication from the PDU session. According to one embodiment, the notification that the branch point UPF or UL CL UPF has been removed may include the associated PDU session ID.

[0217] According to one embodiment, the SMF may be configured not to transmit a notification to the WTRU every time the SMF adds a branch point UPF or ULCL UPF to a PDU session. Instead, according to one embodiment, the SMF may be configured to transmit a notification only when the branch point UPF or ULCL UPF is configured to route traffic to and from the edge data network. According to one embodiment, the SMF may be configured with information for determining which IP addresses in the data network are associated with the edge data network. Therefore, according to an embodiment, the notification from the SMF will serve as a warning or indication to the WTRU that the PDU session is being used to access edge services, and the warning will be considered by the WTRU when determining whether to use non-seamless WLAN offload for any traffic associated with the PDU session.

[0218] Example implementations of information elements that may be carried in a notification are listed in the following table:

[0219]

[0220] Fig. 9 An example flow is shown in the form of a sequence diagram in which the SMF detects that traffic in a PDU session is being routed to the edge and transmits a NAS-SM notification to the WTRU to indicate to the WTRU that some traffic from the PDU session is being routed to the edge according to one embodiment. The entities shown are, from left to right, the WTRU (910), the AMF (920), and the SMF (930).

[0221] In step 901, the WTRU transmits a PDU session establishment request to the network (ie, SMF). As described above, according to one embodiment, the PDU session establishment request may include an indication that the WTRU is capable of receiving or understanding edge service indications.

[0222] In step 902, the SMF transmits a PDU session establishment accept message (Session Establishment Accept message) to the WTRU. According to one embodiment, if the SMF detects that some traffic from the PDU session is being routed to the edge, the message may indicate to the WTRU that the SMF will transmit an edge service indication to the WTRU.

[0223] In step 903, according to one embodiment, the SMF determines that some traffic from the PDU session is being routed to the edge. For example, the SMF may make this determination when adding a branch point or an uplink classifier to the PDU session.

[0224] In step 904, according to one embodiment, as described above, the SMF transmits a NAS-SM notification with an edge service indication to the WTRU.

[0225] In step 905, according to one embodiment, the WTRU determines that non-seamless offload is available.

[0226] In step 906, according to one embodiment, the WTRU takes action to handle edge-routed traffic (i.e., determines to terminate application traffic, attempts to move traffic to non-seamless offload, or retains traffic in the 5G system).

[0227] Implementation related to per-PDU session indication

[0228] According to one embodiment, the SMF may be configured with information that the SMF may use to determine whether a PDU session may be used to access an edge data network. For example, according to one embodiment, the SMF may be configured to know that PDU sessions associated with certain S-NSSAI / DNN combinations may be used to access an edge data network. According to one embodiment, the configuration information may also indicate that a PDU session may only be used to access an edge data network if the PDU session is established by a specific WTRU.

[0229] According to one embodiment, when the WTRU transmits a PDU session establishment request, the SMF may check whether the information in the PDU session establishment request is associated with an edge data network. According to one embodiment, the information in the PDU session establishment request may include an S-NSSAI and a DNN. According to one embodiment, if the information in the PDU session establishment request is associated with an edge data network, the SMF may include an edge service indication in the PDU session establishment accept message. Including this notification from the SMF will serve as a warning or indication to the WTRU that the PDU session can be used to access edge services, and the warning will be considered by the WTRU when determining whether to use non-seamless WLAN offloading for any services associated with the PDU session.

[0230] The ability of a PDU session to access an edge data network may change when the WTRU moves from one registration area to another, when the SMF associated with the PDU session changes, or when the UPF associated with the PDU session changes. For example, edge services may become available or may no longer be available. When the ability to access an edge data network is added or removed, the SMF may transmit a PDU Session Modification message (Session Modification message) to the WTRU.

[0231] According to one embodiment, the PDU Session Modification message may indicate to the WTRU whether an edge service indication should be associated with the PDU session, and the WTRU may update any context stored for the PDU session accordingly (ie, remove the edge service indication).

[0232] Implementation schemes associated with each DNN instruction

[0233] As previously described, LADN information is a mechanism that the network can use to transmit information about the data network to the WTRU. According to one embodiment, the LADN mechanism can be enhanced so that the edge service indication can be included in the LADN information and associated with the DNN. In addition, according to one embodiment, if the network needs to provide an indication to the WTRU for a geographically unrestricted data network, the network can indicate to the WTRU that the DNN is available throughout the registration area. According to one embodiment, the network can indicate to the WTRU that the DNN is available throughout the registration area by not providing service area information, thereby indicating that there is no service area restriction, or by providing a wildcard indication in the service area information element.

[0234] Alternatively, according to one embodiment, a new information element may be defined that allows the network (i.e., AMF) to provide the DNN and associated edge service indications to the WTRU. According to one embodiment, when the WTRU provides a request edge service indication in the registration request message, the AMF may know to provide this information to the WTRU.

[0235] Implementations related to EDN configuration and EAS profile-based instructions

[0236] The WTRU may host an edge enabled client (EEC). The EEC may receive service provisioning information from an edge configuration server (ECS). The service provisioning information includes the information required by the WTRU to access edge services. This process allows the ECS to consider the WTRU's location, service requirements, service preferences, and connection information when determining what service information to provide to the EEC.

[0237] For each EDN that the WTRU can access, the ECS may provide the EEC with EDN connection information and a list of edge enabling servers (EES) available in the EDN.

[0238] The EDN configuration information may include the DNN, S-NSSAI, and the service area of ​​the EDN. The service area may be a set of cell IDs, PLMN IDs, or tracking area identifiers, where the EDN is available.

[0239] When the EEC determines to communicate with the EES selected from the provisioning information, the EEC may use information from the EDN configuration information (i.e., DNN, S-NSSAI) to establish a PDU session to the EDN. For example, the EEC hosted in the TE portion of the WTRU may invoke an AT command to request the MT portion of the WTRU to establish a PDU session to a DNN / S-NSSAI combination that can be used to reach the EES. The EEC may provide the DNN / S-NSSAI information to the MT portion of the WTRU. In addition, according to one embodiment, the provisioning information may be enhanced to include an edge service indication. According to one embodiment, when the EEC requests the use of a PDU session to transmit data to the EES, the edge service indication may be provided to the MT portion of the WTRU as part of a service descriptor using the above process. According to one embodiment, the edge service indication may be provided to the WTRU for some edge services (EES) but not to other edge services (other EES). The reason why this indication may be associated with some EESs and not others is that some EESs are reachable when non-seamless WLAN offloading is used, and other EESs are reachable even when non-seamless WLAN offloading is used. According to one embodiment, an edge service indication may be provided for unreachable EESs when non-seamless WLAN offloading is used. Thus, the indication serves as a warning to the EEC and the WTRU that the traffic associated with the PDU session should remain in the 5G system and not be offloaded.

[0240] The EEC hosted on the WTRU can perform an EAS discovery process with the EES. The EES can provide the EEC with an EAS profile of the EAS that the application client on the WTRU can access. The EAS profile may include EAS endpoint information. The EAS endpoint information may be an FQDN or an IP address of the EAS. In addition, according to one embodiment, the EAS profile may be enhanced to include an edge service indication. According to one embodiment, the application client can obtain the profile information from the EEC, and when the application client requests to use a PDU session to transmit data to the EAS, according to one embodiment, the above process can be used to provide the edge service indication as part of the service descriptor to the MT part of the WTRU.

[0241] Implementation related to edge data network (EDN) indication having information about non-3GPP access network (AN) selection Implementation plan

[0242] The above-described embodiment for providing edge service indication to the WTRU may be enhanced according to a further embodiment such that the edge service indication additionally includes an ePDG identifier configuration, an N3IWF identifier configuration, and non-3GPP access node selection information. The identified N3IWF or PDG may be used to establish a connection with the 5G system and establish a new PDU session toward the edge data network.

[0243] Consider edge services when switching to WLAN

[0244] As described above and in accordance with one embodiment, the network may provide an edge service indication to the WTRU, and the WTRU may associate the edge service indication with a PDU session or a specific service (ie, service to / from a specific application or service matching a specific service descriptor).

[0245] A WTRU with a PDU session with a 5G network may determine that it is able to access a WLAN access network and that the WLAN network may provide access to a data network without utilizing the 5G system (i.e., non-seamless WLAN offload). For example, the WTRU may make this determination when it receives a particular SSID.

[0246] When the WTRU detects a WLAN network that provides non-seamless WLAN offload, it may determine to stop using all PDU sessions that the WTRU has established with the 5G system and instead use the WLAN network to transmit and receive all application traffic. As previously mentioned, if any PDU session is used to access edge data network services, the abrupt switch to non-seamless WLAN offload may interrupt application layer services and negatively impact the user experience.

[0247] Alternatively, according to an embodiment, when the WTRU detects a WLAN network that provides non-seamless WLAN offload, the WTRU may trigger any combination of the following actions according to the embodiments described below.

[0248] First, according to one embodiment, the WTRU may transmit a notification to any application associated with an edge service indication that the WTRU will begin non-seamless WLAN offload. According to one embodiment, the notification may be transmitted to an EEC hosted in the WTRU, and the EEC may use the EDGE-5 reference point to transmit information from the notification to the application client hosted in the WTRU and accessing the edge service. According to one embodiment, the notification may include a timer value. According to one embodiment, the notification may trigger the application to take action to disconnect their application layer sessions with any service in the edge data network. According to one embodiment, the timer value may be interpreted by the application as the amount of time that the application must disconnect the application layer session before the PDU session is released.

[0249] When it is time to release the PDU session, the WTRU will transmit a PDU SESSION RELEASE message. Alternatively, according to one embodiment, a PDU SESSION MODIFY message may be used by the WTRU to provide a time value to the network, and when the timer expires, the network may initiate the release of the PDU session. A network-based approach to releasing the PDU session may be useful if the WTRU is expected to lose cellular coverage before the timer expires. According to one embodiment, notification to the application layer may be transmitted from the MT portion of the WTRU to the application in the TE portion of the WTRU via an AT command. According to one embodiment, the time value provided to the application may be based on the time value received from the network.

[0250] According to one embodiment, when the WTRU receives an indication that the service has been moved or terminated, the WTRU may determine that it is time to release the PDU session. According to one embodiment, the indication that the service has been moved or terminated may be received from an application such as an EEC. According to one embodiment, the indication may be received from the EEC by the MT portion of the WTRU via an AT command. According to one embodiment, the EEC may determine to transmit the indication when an application client hosted in the WTRU notifies the EEC using the EDGE-5 interface that the connection may be released.

[0251] Second, the WTRU may transmit a PDU session release request (Session Release Request) to the network for any PDU session not associated with an edge service indication. The WTRU may then use non-seamless WLAN offload for any traffic associated with a PDU session that is not associated with an edge service indication.

[0252] Third, according to one embodiment, the WTRU may start a timer for each PDU session associated with the edge service indication. According to one embodiment, when the timer expires, the WTRU may transmit a PDU session release request to the network for the PDU session associated with the timer. According to one embodiment, the WTRU may then use non-seamless WLAN offloading for any service associated with the PDU session that is associated with the edge service indication. According to one embodiment, while the timer is running, applications that are using the PDU session may begin executing a process to terminate their application layer sessions with the service in the edge data network. According to one embodiment, the amount of time the timer runs may be based on a time value received from the network. Alternatively, according to one embodiment, the WTRU may choose not to use non-seamless WLAN offloading for any service that is using the PDU session associated with the edge service indication.

[0253] Fourth, according to one embodiment, the GUI on the WTRU may display a message to the user indicating that access to the edge data network will soon be terminated. According to one embodiment, the GUI message may indicate that the reason for the loss of connection to the edge data network is that the WTRU's cellular connection is being released to facilitate non-seamless WLAN offload, according to one embodiment, the message may indicate the name of the edge data network (i.e., DNN) that the WTRU will no longer be able to access, and according to one embodiment, the message may indicate the amount of time that will pass before the connection to the edge data network will be lost. According to one embodiment, the indicated amount of time may be based on a time value received from the network. According to one embodiment, the GUI may also present the user with the ability to select how application traffic should be handled when application traffic is routed to the edge network and non-seamless offload becomes available to the WTRU. According to one embodiment, the user may indicate that the user prefers to terminate application traffic, attempt to move traffic to non-seamless offload, or retain traffic in the 5G system.

[0254] Fifth, according to one embodiment, if the edge service indication includes an ePDG identifier configuration, an N3IWF identifier configuration, and non-3GPP access node selection information, the WTRU may attempt to establish a connection with the N3IWF or ePDG (e.g., an NWu connection with the N3IWF) using non-seamless WLAN offloading, and establish a new PDU session with the edge data network before terminating the PDU session established via the 3GPP access network.

[0255] Sixth, according to one embodiment, a URSP rule re-evaluation may be triggered. During URSP re-evaluation, if the edge service indication is in the RSD or traffic descriptor, then according to one embodiment, the WTRU may interpret the indication as a signal that the traffic may not be routed via non-seamless offload. Thus, even when non-seamless offload becomes available, the WTRU may know which traffic should stay in the 5G system and what routes (i.e., PDU sessions) should be maintained.

[0256] Fig.10 is a flow chart of a method 1000 according to an embodiment. The method may be implemented by a WTRU. In 1001, the WTRU determines that at least one data traffic flow received and sent by the WTRU is transmitted via an edge network of a cellular network based on at least two data traffic flows received by the WTRU from a data network and sent to the data network. In 1002, the WTRU determines the connection of the WTRU to a wireless local area network, and for at least one data traffic flow transmitted via the edge network, terminates the at least one data traffic flow, or moves the at least one data traffic flow from the edge network to the wireless local area network.

[0257] According to another embodiment, the WTRU determines at least one data service flow transmitted via the edge network based on information contained in one of the following items: a routing descriptor received in a routing policy rule; a service descriptor received in a routing policy rule; a received session establishment acceptance message; a received session modification message.

[0258] According to another embodiment, the method includes: in order to move at least one data service flow from an edge network to a wireless local area network, sending information to an application associated with at least one data service flow transmitted via the edge network indicating that the WTRU has started to move at least one data service flow transmitted via the edge network from the edge network to the wireless local area network.

[0259] According to another embodiment, information indicating that the WTRU has begun to move at least one data service flow transmitted via an edge network from the edge network to a wireless local area network is sent to an edge-enabled client in the WTRU, which is configured to provide services to applications hosted on the WTRU and is configured to access services in the edge network.

[0260] According to another embodiment, the method includes sending, by the WTRU, a session release request for at least one data traffic flow received and sent by the WTRU that is not transmitted via an edge network.

[0261] According to another embodiment, when sending information indicating that the WTRU begins to move at least one data service flow transmitted via the edge network from the edge network to the wireless local area network to an application associated with at least one data service flow transmitted via the edge network, the WTRU starts a timer. When the timer expires, the WTRU sends a session release message for the at least one data service flow transmitted via the edge network.

[0262] According to another embodiment, the timer is set with a value received from the data network.

[0263] The present disclosure also relates to a wireless transmit-receive unit (WTRU), which includes at least one processor, and the at least one processor is configured to perform the steps of method 1000 and any one of the further embodiments described above.

[0264] Fig.111100 is a flow chart of a method 1100 implemented by a WTRU having a wireless local area network (WLAN) radio access technology (RAT) transceiver and a cellular network RAT transceiver. In 1101, the WTRU receives, via the cellular network RAT transceiver, an indication that at least one data traffic flow in a set of data traffic flows received and / or sent by the WTRU via the cellular network RAT transceiver is routed via an edge cellular network. In 1102, the WTRU discovers a WLAN via the WLAN RAT transceiver and connects to the discovered WLAN. In 1103, based on the received indication, the WTRU routes at least some data of at least one data traffic flow routed via the edge cellular network to the WLAN using the WLAN RAT transceiver, and terminates at least one data traffic flow routed via the edge cellular network.

[0265] According to one embodiment of the method, the method includes: sending a request via a cellular network RAT transceiver to receive an indication that at least one data service flow in a set of data service flows received and / or sent by the WTRU via the cellular network RAT transceiver is routed via an edge cellular network.

[0266] According to an embodiment of the method, the indication indicates that a protocol data unit session is used to access the edge service, the indication comprising a protocol data unit session identifier of the protocol data unit session associated with the indication.

[0267] According to one embodiment of the method, the indication is received in a non-access stratum session management message.

[0268] According to one embodiment, the request is included in one of: a registration request; a protocol data unit session establishment request; a protocol data unit session modification request.

[0269] According to one embodiment of the method, the indication is included in one of: a routing descriptor in a routing policy rule; a traffic descriptor in a routing policy rule; a received session establishment accept message; a received session modification message.

[0270] According to an embodiment of the method, the terminating comprises sending a protocol data unit session release request for the protocol data unit session associated with the indication, as identified by a protocol data unit session identifier included in the indication.

[0271] According to one embodiment, a wireless transmitter-receiver unit (WTRU) having a wireless local area network (WLAN) radio access technology (RAT) transceiver and a cellular network RAT transceiver is also disclosed. The WTRU includes at least one processor configured to: receive, via the cellular network RAT transceiver, an indication that at least one data service flow in a set of data service flows received and / or sent by the WTRU via the cellular network RAT transceiver is routed via an edge cellular network; discover a WLAN via the WLAN RAT transceiver and connect to the discovered WLAN; and based on the received indication, use the WLAN RAT transceiver to route at least some data of at least one data service flow routed via the edge cellular network to the WLAN, and terminate the at least one data service flow routed via the edge cellular network.

[0272] According to one embodiment, the at least one processor is configured to: send a request via a cellular network RAT transceiver for an indication that at least one data service flow in a set of data service flows received and / or sent by the WTRU via the cellular network RAT transceiver is routed via an edge cellular network.

[0273] According to one embodiment, the at least one processor is configured to: receive the indication via the cellular network RAT transceiver, the indication indicating that the protocol data unit session is used to access the edge service, the indication including a protocol data unit session identifier of the protocol data unit session associated with the indication.

[0274] According to one embodiment, the at least one processor is configured to receive the indication in a non-access stratum session management message.

[0275] According to one embodiment, the at least one processor is configured to include the request in one of: a registration request; a protocol data unit session establishment request; a protocol data unit session modification request.

[0276] According to one embodiment, the at least one processor is configured to receive the indication in one of: a routing descriptor in a routing policy rule; a traffic descriptor in a routing policy rule; a received session establishment accept message; a received session modification message.

[0277] According to one embodiment, the at least one processor is configured to terminate the at least one data service flow routed via the edge cellular network by sending a protocol data unit session release request for a protocol data unit session associated with the indication, as identified by a protocol data unit session identifier included in the indication.

[0278] in conclusion

[0279] Although features and elements are provided above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. The present disclosure is not limited to the specific embodiments described in this patent application, which are intended to be illustrative of various aspects. Many modifications and variations can be made without departing from the essence and scope of the present invention, as they will be apparent to those skilled in the art. Unless explicitly provided as such, any element, action or description used in the present application specification should not be understood as being essential or necessary to the present invention. According to the foregoing description, in addition to those listed herein, functionally equivalent methods and devices within the scope of the present disclosure will be apparent to those skilled in the art. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only to the terms of the appended claims and the full range of equivalent forms of such entitled claims. It should be understood that the present disclosure is not limited to a specific method or system.

[0280] For simplicity, the foregoing embodiments are discussed with respect to terminology and structure of infrared capable devices (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but may be applied to other systems using other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0281] It should also be understood that the terms used herein are used only for the purpose of describing specific embodiments and are not intended to be limiting. As used herein, the term "video" or the term "image" may mean any of a snapshot, a single image, and / or a plurality of images displayed on a time basis. For example, when referred to herein, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a plurality of embodiments of the WTRU; (iii) a wireless and / or wired (e.g., tetherable) device configured with (in particular) some or all of the structure and functionality of the WTRU; (iii) a wireless and / or wired device configured with less than all of the structure and functionality of the WTRU; or (iv), etc. This document is relative to Figures 1A to 1DDetails of an example WTRU are provided that may represent any WTRU described herein. As another example, various disclosed embodiments herein are described above and below as utilizing a head mounted display. Those skilled in the art will recognize that devices other than head mounted displays may be utilized, and some or all of the present disclosure and various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adapted reality experience.

[0282] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via a wired connection or a wireless connection) 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, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0283] Variations of the methods, devices, and systems provided above are possible without departing from the scope of the present invention. In view of the various embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be considered to limit the scope of the following claims. For example, the embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery, etc.) that provides any suitable voltage.

[0284] In addition, in the embodiments provided above, processing platforms, computing systems, controllers and other devices including processors are indicated. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to the symbolic representations of actions and operations or instructions may be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as being "executed", "computer executed" or "CPU executed".

[0285] Those of ordinary skill in the art will appreciate that the actions and symbolic representations of operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits, which may result in the ultimate transformation of electrical signals or reduction of electrical signals and the retention of data bits at memory locations in the memory system, thereby reconfiguring or otherwise changing the operation of the CPU and performing other processing of signals. The memory location that holds the data bits is a physical location that has specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may also support the provided methods.

[0286] The data bits may also be maintained on computer-readable media, including magnetic disks, optical disks, and any other volatile (e.g., random access memory ("RAM")) or non-volatile (e.g., read-only memory ("ROM")) mass storage system readable by the CPU. The computer-readable media may include cooperating or interconnected computer-readable media that reside solely on the processing system or distributed across multiple interconnected processing systems that may be local or remote relative to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories, and other platforms and memories may also support the provided methods.

[0287] In an exemplary embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0288] There is little difference between hardware implementation and software implementation of various aspects of the system. The use of hardware or software is usually (but not always, because in some contexts, the choice between hardware and software may become important) a design choice that represents a trade-off between cost and efficiency. There may be various media (e.g., hardware, software, and / or firmware) that can implement the processes and / or systems and / or other technologies described herein, and the preferred media may vary with the context of the deployment process and / or system and / or other technologies. For example, if the implementer determines that speed and accuracy are most important, the implementer may choose a media that is primarily hardware and / or firmware. If flexibility is most important, the implementer may choose a specific implementation that is primarily software. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0289] The above detailed description has listed various embodiments of the device and / or process by using block diagrams, flow charts and / or examples. In the case where such block diagrams, flow charts and / or examples include one or more functions and / or operations, it should be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware or almost any combination thereof. In one embodiment, several parts of the subject matter described herein can be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs) and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be equivalently implemented in integrated circuits as a whole or in part as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware or almost any combination thereof, and according to the present disclosure, designing circuits and / or writing software and / or firmware codes will be completely within the technical scope of those skilled in the art. Furthermore, those skilled in the art will appreciate that the mechanisms of the subject matter described herein can be distributed as a program product in a variety of forms, and that the illustrative embodiments of the subject matter described herein apply regardless of the specific type of signal-bearing medium used to actually perform the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable type media (such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memory, etc.); and transmission type media (such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.)).

[0290] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into a data processing system. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system generally may include one or more of the following: a system unit housing; a video display device; a memory, such as a volatile memory and a non-volatile memory; a processor, such as a microprocessor and a digital signal processor; a computing entity, such as an operating system, a driver, a graphical user interface, and an application; one or more interactive devices, such as a touch pad or a screen; and / or a control system, including a feedback loop and a control motor (e.g., a feedback for sensing position and / or velocity, a control motor for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented using any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0291] The subject matter described herein sometimes illustrates different components included in or connected to different other components.It should be understood that such depicted architectures are merely examples, and in fact many other architectures that achieve the same function can be realized.In a conceptual sense, any arrangement of components that achieve the same function is effectively "associated" so that the desired function can be realized.Therefore, any two components that are combined to realize a specific function in this article can be regarded as "associated" with each other so that the desired function can be realized, regardless of the architecture or intermediate components.Similarly, any two components so associated can also be regarded as "operably connected" or "operably coupled" to each other to achieve the desired function, and any two components that can be so associated can also be regarded as "operably coupleable" to each other to achieve the desired function.Specific examples of operable coupling include, but are not limited to, components that can physically cooperate and / or physically interact and / or components that can wirelessly interact and / or wirelessly interact and / or components that can logically interact and / or components that can logically interact.

[0292] With respect to substantially any plural and / or singular terms used herein, those skilled in the art may translate from the plural to the singular and / or from the singular to the plural as appropriate, as appropriate to the context and / or application. For clarity, various singular / plural arrangements may be explicitly listed herein.

[0293] It will be understood by those skilled in the art that, in general, the terms used herein, especially in the appended claims (e.g., the bodies of the appended claims), are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "including" should be interpreted as "including but not limited to", etc.) and / or "optional" terms (e.g., the term "is" can be interpreted as "can" or "may", the term "refers to" can be interpreted as "may refer to"). It will also be understood by those skilled in the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly stated in the claim, and in the absence of such a recitation, there is no such intent. For example, where only one item is expected, the term "single" or similar language may be used. To aid understanding, the following appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed as implying that any particular claim including such introduced claim recitations is limited to an embodiment including only one such recitation by the indefinite article "a" or "an" to introduce the claim recitation. This is true even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "a kind" (e.g., "a" and / or "a kind" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, one skilled in the art will recognize that such recitation should be interpreted as meaning at least the stated number (e.g., a bare recitation of "two recitations" without other modifiers means at least two recitations or two or more recitations). In addition, in those instances where a convention similar to "at least one of A, B, and C, etc." is used, generally speaking, the meaning of such construction is that one skilled in the art will understand the convention (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, a system having A alone, B alone, C alone, A and B simultaneously, A and C simultaneously, B and C simultaneously, and / or A, B, and C simultaneously, etc.). In those instances where a convention similar to “at least one of A, B, or C, etc.” is used, generally speaking, the meaning of such construction is that a person skilled in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include, but is not limited to, a system having A alone, B alone, C alone, A and B at the same time, A and C at the same time, B and C at the same time, and / or A, B, and C at the same time, etc.).It will also be understood by those skilled in the art that, in fact, any separate words and / or phrases presenting two or more alternative terms, whether in the specification, claims or drawings, should be understood to contemplate the possibility of including one of the terms, any of the terms, or both of the terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B". In addition, as used herein, the term "any of..." followed by a listing of multiple items and / or multiple item categories is intended to include "any of", "any combination", "any multiples" and / or "any combination of multiples" of items and / or item categories, either alone or in combination with other items and / or other item categories. In addition, as used herein, the term "set" is intended to include any number of items, including zero. In addition, as used herein, the term "quantity" is intended to include any number, including zero. And, as used herein, the term "multiple" is intended to be synonymous with "multiple".

[0294] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also described in terms of any individual member or subgroup of members of the Markush group.

[0295] As will be understood by those skilled in the art, for any and all purposes (such as for providing a written description), all ranges disclosed herein also encompass any and all possible subranges and combinations of their subranges. Any listed range can be easily identified as fully describing and enabling the same range to be divided into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be easily divided into a lower third, a middle third, and an upper third, etc. As will be understood by those skilled in the art, all languages ​​such as "up to", "at least", "greater than", "less than", etc. include the cited numbers and refer to ranges that can subsequently be divided into subranges as described above. Finally, as will be understood by those skilled in the art, ranges include each individual number. Thus, for example, a group having 1 to 3 units refers to a group having 1, 2, or 3 units. Similarly, a group having 1 to 5 units refers to a group having 1, 2, 3, 4, or 5 units, etc.

[0296] Furthermore, the claims should not be read as limited to the order or elements presented unless otherwise stated. Furthermore, the use of the term "means for..." in any claim is intended to invoke 35 U.S.C. § 112, 6 or means-plus-function claim format, and any claim without the term "means for..." is not intended to be so.

Claims

1. A method implemented by a wireless receive-transmit unit (WTRU) having a wireless local area network (WLAN) radio access technology (RAT) transceiver and a cellular network RAT transceiver, the method comprising: receiving, via the cellular network RAT transceiver, an indication that at least one data traffic flow from a set of data traffic flows received and / or sent by the WTRU via the cellular network RAT transceiver is routed via an edge cellular network; discovering a WLAN via the WLAN RAT transceiver, and connecting to the discovered WLAN; and Based on the received indication, at least some data of the at least one data traffic flow routed via the edge cellular network is routed to the WLAN using the WLAN RAT transceiver, and the at least one data traffic flow routed via the edge cellular network is terminated.

2. The method according to claim 1, comprising: and sending, via the cellular network RAT transceiver, a request to receive the indication that at least one data traffic flow from a set of data traffic flows received and / or sent by the WTRU via the cellular network RAT transceiver is routed via an edge cellular network.

3. The method according to claim 1 or 2, wherein the indication indicates that a protocol data unit session is used to access an edge service, the indication comprising a protocol data unit session identifier of the protocol data unit session associated with the indication. The method of claim 3 , wherein the indication is received in a non-access stratum session management message.

5. The method according to any one of claims 1 to 4, wherein the request is comprised in one of the following: Registration request; Protocol data unit session establishment request; Protocol Data Unit Session Modification Request.

6. The method according to any one of claims 1 to 4, wherein the indication is comprised in one of the following: Routing descriptors in routing policy rules; Traffic descriptors in routing policy rules; The received session establishment accept message; Received session modification message.

7. The method of claim 3, wherein the terminating comprises: A protocol data unit session release request is sent for the protocol data unit session associated with the indication, as identified by the protocol data unit session identifier included in the indication.

8. A wireless transmitter-receiver unit (WTRU) having a wireless local area network (WLAN) radio access technology (RAT) transceiver and a cellular network RAT transceiver, the WTRU comprising at least one processor, the at least one processor configured to: receiving, via the cellular network RAT transceiver, an indication that at least one data traffic flow from a set of data traffic flows received and / or sent by the WTRU via the cellular network RAT transceiver is routed via an edge cellular network; discovering a WLAN via the WLAN RAT transceiver, and connecting to the discovered WLAN; and Based on the received indication, at least some data of the at least one data traffic flow routed via the edge cellular network is routed to the WLAN using the WLAN RAT transceiver, and the at least one data traffic flow routed via the edge cellular network is terminated.

9. The WTRU of claim 8, wherein the at least one processor is configured to send, via the cellular network RAT transceiver, a request for receiving the indication that at least one data service flow in a set of data service flows received and / or sent by the WTRU via the cellular network RAT transceiver is routed via an edge cellular network.

10. The WTRU of claim 8 or 9, wherein the at least one processor is configured to: receive the indication via the cellular network RAT transceiver, the indication indicating that a protocol data unit session is used to access an edge service, the indication comprising a protocol data unit session identifier of the protocol data unit session associated with the indication.

11. The WTRU of claim 10, wherein the at least one processor is configured to receive the indication in a non-access stratum session management message.

12. The WTRU of any one of claims 9 to 11, wherein the at least one processor is configured to include the request in one of: Registration request; Protocol data unit session establishment request; Protocol Data Unit Session Modification Request.

13. The WTRU of any one of claims 9 to 11, wherein the at least one processor is configured to receive the indication in one of: Routing descriptors in routing policy rules; Traffic descriptors in routing policy rules; The received session establishment accept message; Received session modification message.

14. The WTRU of claim 10 , wherein the at least one processor is configured to terminate the at least one data service flow routed via the edge cellular network by sending a protocol data unit session release request for the protocol data unit session associated with the indication, as identified by the protocol data unit session identifier included in the indication.

Images