WO2025137133A1 - ENABLER CLIENT FOR QoS MANAGEMENT - Google Patents

Abstract

In some implementations, a WTRU may receive connection information corresponding to a connection to a data network via a wireless network, the connection information including at least one of a UPF-C address and a UPF-C port number. The WTRU may receive, from a hosted application, two or more application layer configurations and corresponding flow information, and send, to the UPF-C, the two or more the application layer configurations and corresponding flow information. The WTRU may receive, from the UPF-C, QoS rules associated with the flow information and an indication of an application layer configuration supported by the wireless network, send, to the hosted application, an indication of the application layer configuration supported by the wireless network, and receive, from the hosted application, uplink traffic and applying packet markings to the uplink traffic based on the QoS rules associated with the application layer configuration supported by the wireless network.

Description

ENABLER CLIENT FOR QoS MANAGEMENT

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63/611 ,915, filed December 19, 2023, the contents of which are incorporated herein by reference.

BACKGROUND

[0002] A wireless transmit/receive unit (WTRU) may support IP traffic. When traffic flow is an IP traffic flow, the flow may be described by an IP address and port number combination. For bidirectional traffic flow, the traffic flow may be described by a destination IP address, destination port number, source IP address, and source port number. A WTRU may have a connection to a packet data network (PDN). The PDN connection is logical association between a WTRU and PDN gateway (GW) and is associated with an access point name (APN). An APN is associated with a data network. A WTRU may maintain state information (i.e., context) for PDN connections, and the WTRU may use PDN connections to send data to a data network and to receive data that was sent to the WTRU via a data network. The packets that are sent in a PDN connection may be called PDUs. The WTRU may be configured with QoS Rules for a PDN Connection and the QoS Rules may be used by the WTRU to determine what packet markings to apply to uplink packets and what radio bearers to use to transmit uplink packets. In advanced wireless networks, for example 5G, a WTRU may have a PDU session which is a logical association between a WTRU and a user plane function (UPF). A PDU session may be associated with a data network name (DNN).

[0003] A WTRU may maintain state information (i.e., context) for PDU Session. The WTRU may use PDU sessions to send data to a data network and to receive data that was sent to the WTRU via a data network. The packets that are sent in a PDU Session may be called PDUs. The WTRU may be configured with QoS Rules for a PDU session and the QoS Rules may be used by the WTRU to determine what packet markings to apply to uplink packets and what radio bearers to use to transmit uplink packets.

[0004] A QoS parameter notification control feature is a feature where the radio access network (RAN) notifies a session management function (SMF) when the QoS requirements of a QoS Flow can no longer be guaranteed. This SMF may then notify a policy control function (PCF) that the QoS parameters that are associated with a flow cannot be guaranteed. The PCF may then notify an application server (AS) or application function (AF) that is associated with the flow that the QoS Parameters associated with a flow cannot be guaranteed. The AS/AF may then, based on the notification, reconfigure the flow. Reconfiguring the flow may mean that the AS negotiates new application layer settings with an application that is hosted by the WTRU. Examples of application layer settings are codec configurations and data rates. The ability to dynamically adjust application layer settings, based on network conditions, is only possible when the WTRU hosted application communicates with an AS that can receive notifications from the PCF. In some cases, a WTRU hosted application may communicate with an AS that is not able to receive notifications from the PCF (e.g., when communicating with an Application Server that is hosted on another WTRU).

[0005] The WTRU can transmit a PDU Session Modification Request to request that a traffic flow, which is described by a packet filter, be assigned to a QoS Flow. However, the WTRU has no way of coordinating alternative QoS profiles with the SMF and no way of receiving a notification that the QoS of a particular flow can no longer be guaranteed. The SMF may send a PDU Session Modification Command to the WTRU with updated QoS Rules, however, the WTRU would be unaware of the cause of the update.

[0006] The architecture of the advanced wireless networks, for example 5G, does not provide a means for a WTRU hosted application to coordinate alternative QoS Profiles and QoS changes with the core network when an application server (AS) that the WTRU hosted application communicates with does not have access to APIs that are exposed by the core network (i.e., exposed by the PCF and network exposure function (NEF)). Thus, the need exists for a solution enabling a WTRU to coordinate QoS treatment of traffic flows.

SUMMARY

[0007] A system of one or more computers may be configured to perform particular operations or actions by virtue of having software, hardware, or a combination of the installed on the system that in operation causes the system in operation to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.

[0008] In one general aspect, a method is performed by a wireless transmit/receive unit (WTRU) hosted client. The method may include receiving connection information corresponding to a connection to a data network, via a wireless network, the connection information including at least one of a user plane function (UPF) control plane (UPF-C) address and a UPF-C port number; receiving, from a hosted application, two or more application layer configurations and flow information corresponding to the two or more application layer configurations; sending, to the UPF-C, the two or more the application layer configurations and the corresponding flow information; receiving, from the UPF-C, quality of service (QoS) rules associated with the flow information and an indication of at least one application layer configuration that is supported by the wireless network. The method may include sending, to the hosted application, an indication of the at least one application layer configuration that is supported by the wireless network; and receiving, from the hosted application, uplink traffic and applying packet markings to the uplink traffic based on the QoS rules associated with the at least one application layer configuration supported by the wireless network. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

[0009] Implementations may include one or more of the following features. The method may include sending, to the UPF-C, an indication of an active application layer configuration. The method may include receiving, from the UPF-C, confirmation of at least one active application layer configuration applied by the UPF-C. The method may include receiving, from the UPF-C, a notification to apply a second application layer configuration to the flow information. The method may include sending, to the UPF-C, an acknowledgement of the notification to apply the second application layer configuration to the flow information. The method may include sending, to the hosted application, a notification to apply the second application layer configuration to the flow information. Each of the two or more application layer configurations include one or more of: a protocol type, a maximum bit rate for data sent between the hosted application and an application server (AS), a delay budget for the data sent between the hosted application and the AS, an indication of whether a packet data unit (PDU) set QoS is enabled, or a direction being in an uplink (UL) or a down link (DL). The flow information corresponds with traffic flows between the hosted application and an application server (AS). The corresponding flow information, received from the hosted application, depicts the traffic flows as one or more internet protocol (IP) 4-tuples.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, wherein like reference numerals in the figures indicate like elements, and wherein:

[0011] FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;

[0012] FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment; [0013] FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (GN) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment;

[0014] FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0015] FIG. 2 illustrates an example user plane protocol stack;

[0016] FIG. 3 illustrates an example WTRU/UPF measurements-related protocol stack for 3GPP access and for an MA PDU Session with type IP;

[0017] FIG. 4 illustrates an example of NAS transport for SM, SMS, WTRU Policy and LCS;

[0018] FIG. 5 illustrates an example system architecture for routing PDUs between a WTRU and

UPF;

[0019] FIG. 6 illustrates an example process for negotiating QoS; and

[0020] FIG. 7 is a flowchart of an example process of a negotiating application layer configuration with an access server.

DETAILED DESCRIPTION

[0021] Abbreviations and Acronyms

5GS 5G System

AF Application Function

AMF Access and Mobility Management Function

AN Access Network

APN Access Point Name

AS Application Server

AT Attention

DN Data Network

DNN Data Network Name

DRB Data Radio Bearer

EPS Evolved Packet System

GPRS General Packet Radio Service

GTP-U GPRS Tunneling Protocol User Plane GUTI 5G Globally Unique Temporary Identifier

LCS Location Services

L1 Layer 1

L2 Layer 2

MME Mobility Management Entity

MT Mobile Termination

NAS Non-Access Stratum

NAS-MM NAS Mobility Management

NAS-SM NAS Session Management

NEF Network Exposure Function

NR New Radio

NSSAI Network Slice Selection Assistance Information

NSI ID Network Slice Instance Identifier

N3IWF Non-3GPP Interworking Function

OS Operating System

PCF Policy Control Function

PDN Packet Data Network

PDN-GW PDN Gateway

PDU Protocol Data Unit

PLMN Public Land Mobile Network

PMF Performance Measurement Function

PSA PDU Session Anchor

PSAS PDU Session Anchor Selection Service

PUC PSA UPF Connection

QFI QoS Flow Identifier

QoS Quality of Service

RACH Random Access Channel

RAN Radio Access Network

RRC Radio Resource Control

SDAP Service Data Adaptation Protocol SMS Short Message Service

SRB Signaling Radio Bearers

S-NSSAI Single NSSAI

SUPI Subscription Permanent Identifier

TE Terminal Equipment

TNGF Trusted Non-3GPP Gateway Function

UDM User Data Management

UDP User Datagram Protocol

UDR User Data Repository

UE User Equipment

UPF User Plane Function

UPF-C UPF Control Plane Part

UPF-D UPF Data Plane Part

URSP UE Route Selection Policy

WLAN Wireless Local Area Networks and related technologies (IEEE 8O2.xx domain)

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

[0023] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, a public switched telephone network (PSTN) 108, the Internet 1 10, and other networks 1 12, though it will be appreciated 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 WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and/or receive wireless signals and may include a user equipment (U E) , a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0024] The communications systems 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 configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and/or the other networks 112. By way of example, the base stations 1 14a, 1 14b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 1 14a, 1 14b are each depicted as a single element, it will be appreciated that the base stations 114a, 1 14b may include any number of interconnected base stations and/or network elements.

[0025] The base station 1 14a may be part of the RAN 104, 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), relay nodes, and the like. The base station 1 14a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 1 14a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 1 14a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions. [0026] 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).

[0027] More specifically, as noted above, the communications 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, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High- Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA).

[0028] In an 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), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE- Advanced Pro (LTE-A Pro).

[0029] In an 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 NR. NR is a radio access that may be used with 5G.

[0030] In an 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 instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).

[0031] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1 X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like. [0032] The base station 1 14b in FIG. 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, 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 an 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 yet another 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 a picocell or femtocell. As shown in FIG. 1A, the base station 1 14b may have a direct connection to the Internet 1 10. Thus, the base station 1 14b may not be required to access the Internet 110 via the CN 106.

[0033] The RAN 104 may be in communication with the CN 106, 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 varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology. [0034] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 1 10, and/or the other networks 112. The PSTN 108 may include circuit- switched telephone networks that provide 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), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 1 12 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT. [0035] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications 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 over different wireless links). For example, the WTRU 102c shown in FIG. 1A 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.

[0036] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include 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 peripherals 138, among others. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.

[0037] 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 in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. The processor 1 18 may perform signal coding, 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. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 1 18 and the transceiver 120 may be integrated together in an electronic package or chip.

[0038] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 1 16. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

[0039] Although the transmit/receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, 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.

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

[0041] The processor 1 18 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or 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 1 18 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), 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, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0042] The processor 1 18 may receive power from the power source 134, and may be configured to distribute and/or control the 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, and the like.

[0043] 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 over the air interface 1 16 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0044] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e- compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors. The sensors may be one or more of 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, a humidity sensor and the like.

[0045] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate selfinterference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a halfduplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).

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

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

[0048] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [0049] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0050] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c 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, and the like. 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.

[0051] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the 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 user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0052] 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.

[0053] 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 communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves 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 the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.

[0054] Although the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0055] In representative embodiments, the other network 112 may be a WLAN.

[0056] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the 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 in to and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11 e DLS or an 802.11 z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0057] When using the 802.11 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.1 1 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/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.

[0058] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0059] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC). [0060] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.1 1 n, and 802.11 ac. 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.1 1 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.1 1 ah may support Meter Type Control/Machine-Type Communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0061] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11 ac, 802.11 af, and 802.1 1ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest 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, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.

[0062] In the United States, the available frequency bands, which may be used by 802.11 ah, are from 902 MHz to 928 MHz In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.

[0063] FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 1 16. The RAN 104 may also be in communication with the CN 106.

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

[0065] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology For example, the 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 gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

[0066] 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 the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.

[0067] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0068] The CN 106 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0069] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non- access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 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, and the like. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 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.

[0070] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N1 1 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

[0071] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 1 10, 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 DL packets, providing mobility anchoring, and the like.

[0072] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves 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 the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0073] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a- b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

[0074] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, 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. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.

[0075] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data. [0076] Examples provided herein do not limit applicability of the subject matter to other wireless technologies, e.g., using the same or different principles as may be applicable.

[0077] As explained herein, a wireless transmit/receive unit (WTRU) may be an example of a user equipment (UE). Hence the terms UE and WTRU may be used with equal scope herein.

[0078] In the description, the following term definitions are used herein and help refine the understanding of those skilled in the art with respect to the terms expressed herein.

[0079] A traffic flow may be an IP Flow. When a traffic flow is an IP Flow the flow may be described as all the traffic to an IP Address and Port Number combination. When a traffic flow is bi-directional, the traffic flow may be described by a destination IP Address, destination Port Number, source IP Address, and source Port Number.

[0080] A traffic flow may be an Application Flow. When a traffic flow is an Application Flow the flow may be described as all data that is sent to and from the Application.

[0081] A traffic flow may be certain traffic within an IP Flow. For example, a traffic flow may be all traffic that is sent a certain IP Address and Port Number combination and has certain information in the packet header (e.g., a QUIC stream).

[0082] The term RAN Node is used in this paper. The action and ideas that are described as applying to the RAN Node may also be applied to an N3IWF or TNGF.

[0083] A cellular base station may be a type of RAN Node.

[0084] The PDU Session Anchor (PSA) is used in the paper. A PDU Session anchor may be a UPF.

[0085] The description may be related to services that may be invoked, may invoke other services, and may provide information. Services may be invoked by a Network Function.

[0086] A radio bearer is a type of network resource. A radio bearer may be described by a combination of a frequency range and time period.

[0087] There are two types of radio bearers in the 5G system. The first type of radio bearer is an signaling radio bearers (SRB). SRBs are used for the transmission of RRC and NAS messages. Data Radio Bearers (DRB)s are used to transmit user plane data. Since DRBs are used to transmit data from a QoS Flow of a PDU Session, usage of a DRB may be associated with a network slice.

[0088] QoS Rules are used by the WTRU to determine packet marks to append to uplink traffic. The packet markings are used by the network to determine how to prioritize the packet. QoS Rules, or the applied packet markings, are also used to determine what logical channel and what radio bearer to use to transmit uplink packets. [0089] In the Evolved Packet System (EPS), a WTRU may have a Packet Data Network (PDN) Connection. A PDN Connection is logical association between a WTRU and PDN gateway (GW). A PDN Connection is associated with an Access Point Name (APN). An APN is associated with a data network. A UE maintains state information (i.e., context) for PDN Connections. The WTRU uses PDN Connections to send data to a data network. A WTRU uses PDN Connections to receive data that was sent to the WTRU via a data network. The packets that are sent in a PDN Connection may be called PDUs. The WTRU may be configured with QoS Rules for a PDN Connection and the QoS Rules may be used by the WTRU to determine what packet markings to apply to uplink packets and what radio bearers to use to transmit uplink packets.

[0090] In the EPS, a WTRU may have a PDN Connection. A PDN Connection is logical association between a WTRU and PDN GW A PDN Connection is associated with an APN . An APN is associated with a data network. A WTRU maintains state information (i.e., context) for PDN Connections. The WTRU uses PDN Connections to send data to a data network. A WTRU uses PDN Connections to receive data that was sent to the WTRU via a data network. The packets that are sent in a PDN Connection may be called PDUs. The WTRU may be configured with QoS Rules for a PDN Connection and the QoS Rules may be used by the WTRU to determine what packet markings to apply to uplink packets and what radio bearers to use to transmit uplink packets.

[0091] In the 5GS, a WTRU may have a PDU Session. A PDU Session is logical association between a WTRU and UPF. A PDU Session is associated with a data network name (DNN). An DNN is associated with a data network. A WTRU maintains state information (i.e., context) for PDU Session. The WTRU uses PDU Sessions to send data to a data network. A WTRU uses PDU Sessions to receive data that was sent to the WTRU via a data network. The packets that are sent in a PDU Session may be called PDUs. The WTRU may be configured with QoS Rules for a PDU Session and the QoS Rules may be used by the WTRU to determine what packet markings to apply to uplink packets and what radio bearers to use to transmit uplink packets. The terms connection and session may be used interchangeably in this description.

[0092] In the 5G System, a PDU Session may have the following characteristics.

[0093] A PDU Session is session between a WTRU and one or more anchor UPF(s). A PDU Session is associated with an single network slice selection assistance information (S-NSSAI) and a DNN. A PDU Session may be associated with multiple access network connections. For example, a WTRU may send PDUs in a PDU Session over both New Radio (NR) and non-3GPP (i.e. Wi-Fi access). A PDU Session is made up of one or more QoS Flows and each QoS Flow is associated with only one access. [0094] For each access network node (e.g. RAN Node or Non-3GPP Interworking Function (N31WF)) that is associated with a WTRU's PDU Session, there is a General Packet Radio Service Tunneling Protocol User Plane (GTP-U) tunnel between the access network node and a UPF of the PDU Session.

[0095] In the 5G System, the WTRU may be configured with WTRU Route Selection Policy (URSP) Rules that are used by the WTRU to associate uplink traffic with a PDU Session. The URSP Rules can be used to configure the WTRU with information to determine a DNN and S-NSSAI combination that should be associated with the PDU Session that carries uplink traffic that is associated with an application.

[0096] A DNN is a human readable string of characters. Some Applications are designed such that they provide a DNN to the mobile terminal (MT) part of the WTRU so that the WTRU can use the DNN to determine the properties of the PDU Session that should carry the applications uplink traffic.

[0097] An S-NSSAI does not identify a slice. Rather, it is a piece of information that is used by the network to select an slice. When a WTRU registers to a slice that is associated with an S-NSSAI, the identity of the slice that the WTRU registers is not provided to the WTRU . There may or may not be a one-to-one mapping between S-NSSAI and Network Slice Instance Identifier (NSI ID).

[0098] When a WTRU establishes PDU Session in multiple network slices, the WTRU indicates the S-NSSAI that should be associated with each PDU Session. Thus, the WTRU has some awareness of what network slice is used in a PDU Session. Furthermore, the WTRU must register to a network slice prior to using the network slice to send and receive PDUs.

[0099] The AMF performs network slice selection in the 5G System. The WTRU is involved in the network slice selection procedure in the sense that the WTRU may provide an S-NSSAI to the AMF and the AMF uses the S-NSSAI in the network slice selection procedure.

[0100] The WTRU may request that the network provide certain type of QoS handling for an SDF. The UE may make this request by sending a PDU Session Modification Request to the network. The PDU Session Modification Request may include a packet filer that is associated with the SDF and an information that indicates the type of QoS handling that is requested.

[0101] FIG. 2 illustrates a protocol stack for a PDU session.

[0102] As illustrated in FIG. 2, PDU layer 210a resides on WTRU 202. A PDU session anchor (UPF) is illustrated at 208. Also illustrated is RAN 304 and UPF 306. In the example protocol stack for a PDU session shown in FIG. 2, the PDU Layer represents the layer that passes PDUs to and from the WTRU. Examples of PDUs are IP Packets and Ethernet packets It can be seen that that there is no way for WTRU 202 to convey information to UPF 206 when delivering a PDU. [0103] FIG. 3 illustrates an example protocol stack with an access traffic steering, switching, and splitting (ATSSS) feature deployed. When the ATSSS function is deployed, the PMF protocol may be used between WTRU 302 and PSA UPF 308 to exchange measurement information and traffic steering configuration. An example of the PMF 312a and 312b protocol stack is shown in FIG. 3 as well as UDP 310a and 310b.

[0104] FIG. 4 illustrates an example of NAS transport for SM, SMS, UE Policy and LCS.

[0105] In advanced communication systems like 5G systems, all control plane messages that are sent from the WTRU to the 5G core (i.e. NAS Messages) are transparently passed through a RAN Node and to the AMF serving the WTRU. When WTRU 402 transmits a NAS message 414a, AMF 404 receives the NAS message 414b and may forward parts of the message to other network functions such as SMF 406. Notice that AMF 404 must act as a router for various types of control plane messaging from WTRU 402. Thus, AMF 404 is both the main network function that deals with mobility management processing and a network function that must deal with all session management signaling between the WTRU and the network (SMF 406, SMSF 408, PCF 410, and LMF 412).

[0106] In 5G system, for example, the SMF may send to the RAN a prioritized list of Alternative QoS Profile(s) for a PDU session. An Alternative QoS Profile represents a combination of QoS parameters packet delay budget (PDB), packet error rate (PER), averaging window and guaranteed flow bit rate (GFBR) to which the application traffic is able to adapt. The RAN may determine that it cannot fulfill the QoS Profile that is currently applied to the traffic (e.g., due to network conditions such as congestion) and may send a notification to the SMF that the QoS profile is not fulfilled. The RAN Node may also indicate which of the Alternative QoS Profiles the RAN can fulfill. The notification from the RAN may trigger the SMF to update the WTRU's QoS Rules so that they align with the QoS Profile that is currently fulfilled and send a notification to the PCF to indicate what QoS Profile is currently fulfilled. The PCF may then notify an AF/AS with information about what QoS treatment can be provided so that the AF/AS can adapt the application traffic accordingly. The indication to the AF/AS may be sent from PCF via the network exposure function (NEF).

[0107] A described above, the QoS Parameter Notification control feature is a feature where the RAN notifies the SMF when the QoS requirements of a QoS Flow can no longer be guaranteed. This SMF may then notify the PCF that the QoS Parameters that are associated with a flow cannot be guaranteed. The PCF may then notify an Application Server/Application Function (AS/AF) that is associated with the flow that the QoS Parameters that are associated with a flow cannot be guaranteed. The AS/AF may then, based on the notification, reconfigure the flow.

- 72 - [0108] Reconfiguring the flow may mean that the AS negotiates new Application Layer settings with an application that is hosted by the WTRU. Examples of Application Layer settings are codec configurations and data rates.

[0109] The ability to dynamically adjust application layer settings, based on network conditions, is only possible when the WTRU Application communicates with an Application Server that can receive notifications from the PCF. In some cases, a WTRU Application may communicate with an Application Server that is not able to receive notifications from the PCF (e.g., when communicating with an Application Server that is hosted on another WTRU).

[01 10] The WTRU can transmit a PDU Session Modification Request to request that a traffic flow, which is described by a packet filter, be assigned to a QoS Flow. However, the WTRU has no way of coordinating alternative QoS profiles with the SMF and no way of receiving a notification that the QoS of a particular flow can no longer be guaranteed. The SMF may send a PDU Session Modification Command to the WTRU with updated QoS Rules, however, the WTRU would be unaware of the cause of the update. However, the architecture of the 5G network does not provide a way for a WTRU Hosted Application to coordinate alternative QoS Profiles and QoS changes with the core network when the Application Server that the WTRU Hosted Application communicates with does not have access to APIs that are exposed by the core network (i.e., exposed by the PCF and NEF).

[01 11] FIG. 5 illustrates an example system architecture for routing PDUs between a WTRU and UPF. In this example architecture, when WTRU 502 wants to establish a connection, or session, with a data network 504, WTRU 502 uses control plane signaling to communicate with a PDU Session Anchor Selection Service (PSAS) 506 in the core network. The result of the interaction with the PSAS 506 is that a UPF will be selected to serve the WTRU's connection to the data network 504.

[01 12] Communication between WTRU 502 and PSAS 506 takes place over the reference point that is labeled Reference-Point-1 508. Once a UPF is selected, an enabler client 510 in WTRU 502 may then communicate directly with the UPF for session management signaling. An advantage of this architecture is that session management signaling between the WTRU and UPF may be sent via the same network resources (e.g., radio bearers and network functions).

[01 13] The communication between WTRU 502 and UPF for session management signaling takes place over the reference point that is label Reference-Point-2 512. PDUs are send from WTRU 502 to RAN Node 514 and forwarded by RAN Node 514 to the UPF.

[01 14] The enabler client 510 in WTRU 502 may be called a PSA UPF Connection Enabler Client (PUC Enabler Client). WTRU 502 may host a multiple PUC Enabler Clients 510 that each communicate with only UPF Control Plane Part (UPF-C)(s) 516 of a single PDU session or WTRU 502 may be a single PUC Enabler Client that communicates with the UPF-C(s) 516 of all the WTRU's PDU sessions. If WTRU 502 hosts multiple PUC Enabler Clients, each PUC Enabler Client may be associated with a DNN and WTRU Hosted Applications 518 may invoke an attention (AT) Command or operating system application program interface (OS API) to discover and associate with the PUC Enabler Client 510 that is associated with the PDU Session that carries WTRU 502 Hosted Application's traffic. The WTRU Hosted Application 518 may provide the DNN or the WTRU Hosted Application's IP Address to the AT Command or OS API in order to determine the PUC Enabler Client identity.

[0115] The UPF may have a control plane part. The control plane part of the UPF may be called UPF-C 516. UPF-C 516 may be the termination point and source of session management signaling between the UPF and WTRU.

[0116] The UPF may have a data plane part. The data plane part of the UPF may be called UPF Data Plane Part (UPF-D) 520. UPF-D 520 may be the termination point and source of data plane traffic between the UPF and WTRU.

[0117] The UPF-C 516 and UPF-D 520 may have an interface. The interface may be used by the UPF to configure the UPF-D. The UPF-C and UPF-D may be different network functions.

[0118] The Application Function (AF) may invoke an API of the NEF to provide information about a traffic flow of the WTRU. For example, the AF may provide information about the QoS requirements of the WTRU's traffic flows. The traffic flows may be described in the API invocation by a combination of source IP Address, destination IP Address, DNN, and S-NSSAI The NEF may determine what PCF 524 serves the traffic flow and provide the QoS requirements to PCF 524. The QoS Requirements may be stored in PCF 524 or in the subscription information of the WTRU in the UDM/UDR 522. When a UPF is selected for the WTRU, PSAS 506 may obtain the QoS Requirements from PCF 524 or UDM/UDR 522 and use the QoS Requirements to determine a QoS configuration for the UPF, WTRU, and RAN Node.

[0119] The described system architecture includes a network function that handles mobility management signaling for the WTRU. However, the network function that handles mobility management signaling does not need to be involved in session management signaling. Specifically, the network function that handles mobility management signaling does not need to route session management signaling. Note that mobility management function is not shown in FIG. 5.

[0120] This following description is related to examples of how a WTRU may host PUC Enabler Client functionality. The PUC Enabler Client may establish contact with a UPF-C and coordinate QoS treatment of flows with the UPF-C. Coordinating QoS treatment of traffic flows may mean that the PUC Enabler Client indicates to the UPF-C what types of QoS treatment are requested for a traffic flow and the UPF-C may indicate to the PUC Client what type(s) of QoS treatment can be provided, guaranteed, or promised, by the network. The PUC enabler client may know what types of QoS treatment are needed for a flow based on information that is received from a WTRU hosted application. The PUC enabler client may provide information to the WTRU hosted application about what types of QoS treatment can be provided, guaranteed, or promised, by the network. The WTRU hosted application may then use the information about what types of QoS treatment can be provided, guaranteed, or promised, by the network to negotiate application layer configuration(s) with an Application Server.

[0121] A WTRU may host a PSA UPF Connection Enabler Client (PUC Enabler Client) in the Terminal Equipment (TE) part of the WTRU. The PUC Enabler Client may be part of the operating system or run as an application on top of the operating system.

[0122] The PUC Client may have an interface to the Mobile Terminal (MT) Part of the WTRU. The interface to the MT part of the WTRU may be used by the PUC Client to establish a connection to a data network.

[0123] The interface between the PUC Client and MT part of the WTRU may be used by the PUC Client to request the establishment of a connection between the WTRU and a data network.

[0124] The interface between the PUC Client and MT part of the WTRU may be used by the PUC Client to receive the contact information for a PSA UPF that can be used to send and receive traffic to and from the data network. The content information may be an IP Address and port number of the UPF-C. Alternatively, the content information may be an IP Address of a DNS Server and an FQDN of the UPF-C.

[0125] The PUC Client may have an interface to the UPF-C The interface between PUC client and UPF-C is shown in FIG. 5 as Reference-Point-2 (516).

[0126] Reference-Point-2 may be used by PUC client to send information to the UPF-C. The information that is sent to the UPF-C may indicate QoS Requirements for traffic flows that are between the WTRU and UPF-C. Reference-Point-2 may be used by PUC client to receive information to the UPF-C. The information that is sent to the UPF-C may indicate the QoS treatment that will be received traffic flows between the WTRU and UPF-C.

[0127] The PUC Client may have an interface to the WTRU Hosted Applications. The interface may be defined as an API interface. The interface 526 between PUC Client and WTRU Hosted Application(s) is shown in FIG. 4 as Reference-Point-3. Reference-Point-3 may be used by a WTRU Hosted Application to send information to the PUC Client. The information that is sent to the PUC Client may indicate QoS Requirements for traffic flows that are associated with the WTRU Hosted Application.

[0128] Reference-Point-2 may be used by PUC Client to send information to the WTRU Hosted Application. The information that is sent to the WTRU Hosted Application may indicate the QoS treatment that will be received traffic flows that are associated with the WTRU Hosted Application.

[0129] An advantage of a WTRU architecture that includes a PUC Client is that the Reference- Point-3 interface can be used by the WTRU Hosted Application to configure how the WTRU Hosted Application's traffic is treated. As shown in FIG 5, the data plane traffic of the WTRU Hosted Application does not need to be processed by the PUC Client. Rather, the WTRU Hosted Application and PUC Client can interface for the purpose of configuring how the data plane traffic is treated. This architecture gives the WTRU Hosted Application some control and visibility of how the data plane traffic is treated .

[0130] Another advantage of the architecture of FIG. 5 is that control signaling that is related to the PDU Session can be sent within the PDU Session. Thus, DRBs that are associated with the PDU session and the network slice may be used to send the control signaling. Thus, the use of SRBs, which are generally transmitted with higher priority and consume more network resources than DRBs, can be avoided. In this context, network resources refers to using an amount of spectrum for a time duration.

[0131] Alternatively, QoS Rules may be sent to the WTRU that indicate that the control traffic of the PDU Session should be transmitted with SRBs. For example, a QoS Rule may indicate that the traffic that is sent to the IP Address and Port Number of the UPF-C should be sent on a QoS Flow that uses SRBs.

[0132] FIG. 6 illustrates an example procedure for negotiating QoS.

[0133] The example procedure of FIG. 6 shows how a WTRU Hosted Application may configure the QoS treatment of user plane traffic that is associated with the WTRU Hosted Application. An example procedure for how the PUC Enabler Client and UPF-C can negotiate the QoS treatment that may be applied to traffic flows in shown in FIG. 6. This example procedure also shows that the QoS treatment can be coordinated with the WTRU Hosted Application and Application Server.

[0134] Prior to the process at 618, it is assumed that the WTRU is registered to the wireless network and has established a secure connection with the RAN Node 608.

[0135] At 618 the MT part 606 of the WTRU may be triggered to send a NAS message to the network to request a connection to a PSA UPF 614. The request may include the identity of a DNN and value that is associated with the identity of the DNN. [0136] The MT part 606 of the WTRU may be triggered to send the NAS Message when it detects new traffic from the WTRU Hosted Application 602 and the MT part 606 of the WTRU may determine the identity of a DNN, or value that is associated with identity of the DNN, based on the identity, or type, of WTRU Hosted Application.

[0137] The MT part 606 of the WTRU may be triggered to send the NAS Message based on a request from the WTRU Hosted Application 602. The request from the WTRU Hosted Application may include the DNN, or a value that is associated with the DNN. The WTRU Hosted Application may be triggered to request the connection when the application is started.

[0138] The MT part 606 of the WTRU may be triggered to send the NAS Message based on a request from the PUC Enabler Client 604. The request from the PUC Enabler Client 604 may include the DNN, or a value that is associated with the DNN. The PUC Client 604 may be triggered to request the connection based on interaction with the WTRU Hosted Application 602. For example, the PUC Client 604 may trigger the request when it receives an indication from the WTRU Hosted Application 602 that the WTRU Hosted Application has started or has existed a dormant state.

[0139] In response to NAS request, the MT part 606 of the WTRU may receive an indication that the connection between the WTRU and PSA UPF 614 is established. The WTRU may also receive information about the connection to the PSA UPF 614. The information may include an IP Address and Port Number of the UPF-C. Alternatively, the information may be an IP Address of a DNS Server and an FQDN of the UPF-C. Additionally, the information may include a DNS Server address that should be used to service DNS look ups that are received from WTRU applications.

[0140] The information about the connection to the PSA UPF 614 may also include 2 QoS Rules. The first QoS Rule may apply to all traffic that is sent to the IP Address and Port Number of the UPF- C. The second QoS Rule may be a default QoS Rule for the connection to the PSA UPF 614 and may apply to all traffic that targets the DN (i.e. does not target the UPF-C). The second QoS Rule may apply to all traffic that the first QoS Rule does not apply to. The second QoS Rule may be sent to the PUC Enabler Client 604 so that the PUC Enabler Client is aware of what QoS treatment will be provided to traffic that is generated by applications that are hosted on the WTRU. Since the first QoS Rule only applies to control traffic from the PUC Enabler Client and does not apply to WTRU hosted applications, it might not be necessary for the first QoS Rule to PUC Enabler Client.

[0141] In response to receiving the IP Address and Port Number of the UPF-C, the MT part 606 of the WTRU may configure the PUC Enabler Client 604. Configuring the PUC Enabler Client means providing the IP Address and Port Number of the UPC-C to the PUC Enabler Client 604. Configuring the PUC Enabler Client 604 may also mean providing the DNN that is associated with the

-7J - configuration to the PUC Enabler Client. In this procedure, the WTRU Hosted Application 602 may receive an indication that the connection to the PSA UPF 614 has been established.

[0142] At 620, the WTRU Application and Application Server may begin to communicate. At this point in the procedure, the WTRU, RAN Node, and UPF may assume that a set of default QoS Rules are applied to all traffic of the connection between the WTRU and PSA UPF. The WTRU Application and Application Server may use a protocol such as SDP to negotiate one or application layer configurations that may be used for application layer traffic between the WTRU Application and Application Server. Each application layer configuration may include: a protocol type (e.g., RTP), a maximum bit rate for the data that is sent between the WTRU application and Application Server, a delay budget for the data that is sent between the WTRU application and Application Server, an indication of whether PDU Set QoS Handling is enabled, and a direction for the configuration (i.e., uplink or downlink).

[0143] The WTRU Application and Application Server may negotiate to form a list of application layer configurations that both the WTRU Application and Application Server can support. They may also negotiate a priority order for the application layer configurations. In other words, they may determine which application layer configuration is highest in priority (i.e., most preferred) and which application layer configuration is lowest in priority (i.e., least preferred).

[0144] At 622, the WTRU Application may invoke an API of the PUC Enabler Client 604. The API may be invoked so that the WTRU Application can provide the negotiated list of application layer configurations to the PUC Enabler Client 604. The WTRU Application provides the application layer configurations to the PUC Enabler Client so that the PUC Enabler Client 604 can negotiate with the network to determine which application layer configuration(s) can be supported by the network.

[0145] In addition to the application layer configuration, the WTRU Application will also provide flow information to the PUC Enabler Client 604. The flow information describes traffic flows between the WTRU Application and Application Server 616. The flow information may describe the traffic flows as one or more IP 4 tuples (i.e., a source address, destination address, source port number, and destination port number). The WTRU Application may need to provide this information so that PUC Enabler Client knows what traffic the application layer configuration(s) are associated with.

[0146] An advantage to the PUC Enabler Client is demonstrated here. The WTRU Application does not need to interact directly with the Cellular Core Network and can be agnostic to what type of transport network carries the application layer traffic (e.g., cellular, fixed wire, or Wi-Fi). The WTRU Application only needs to provide the application layer configuration(s) to the Enabler Client and the re WTRU Application can later receive guidance on which application layer configuration should be applied.

[0147] At 624, the PUC Enabler Client 604 will send a PSA Connection Update Request to the PSA UPF-C. This message will be sent to the IP Address and Port number that were received by the MT Part 606 and sent by the MT part of the WTRU to the PUC Enabler Client at 618.

[0148] The PUC Enabler Client 604 and PSA UPF-C may communicate by using a protocol that runs on top of IP. The PSA Connection Update Request may include the application layer config uration(s) and flow information that the PUC Enabler Client received at 622.

[0149] AT 626 , the UPF-C may determine a set of QoS Rule(s) for each of the application layer config uration(s). The UPF-C determines which application layer configuration(s) are allowed. In a roaming scenario, the UPF-D may be part of the WTRUs HPLMN and the RAN Node 608 may be part of a VPLMN. In a roaming scenario, the UPF-C may query a network function of the VPLMN to determine which application layer configuration(s) or types of QoS are allowed.

[0150] The UPF-C may use policies that were received from the PCF to determine which application layer configuration(s) are allowed. For example, policies that were received from the PCF may indicate what types of services and levels of services are authorized for the WTRU.

[0151] For each application layer configuration, the UPF-C may determine a set of QoS Rules that can be used to provide the connection quality that is necessary to support the application layer configuration. The UPC-C may use pre-configured information to determine what QoS Rules can be used to support each application layer configuration. The UPF may determine a set(S) of QoS Rules, or application layer configuration(s), that can be used.

[0152] The UPF-C may use information about network conditions to determine which sets of QoS Rules, application layer configurations, can be used. For example, the UPF-C may receive information the network conditions (e.g., congestion levels) from the RAN or QAM system. The UPF-C may determine that an application layer configuration that requires a high data rate should not be used because the congestion level in the RAN is high.

[0153] The UPF-C may send a PSA Connection Update Command to the PUC Enabler Client. The PSA Connection Update Command may indicate a set of QoS Rules that is associated with each application layer configuration. Furthermore, the UPF-C may indicate which sets of QoS Rules and application layer configurations may be used.

[0154] At 628 the UPF-C may configure the RAN Node with QoS profiles. The QoS profiles describe the QoS treatment that should be applied to the uplink and downlink packets that are sent between the WTRU and UPF. [0155] AT 630, the PUC Enabler Client 604 sends a message (e.g., a notification message) to the WTRU Hosted Application 602. The message indicates which of the application layer configurations that were provided at 622 may be used . The PUC Enabler Client 604 uses the information from the UPF-C to determine which application layer configurations may be used. In other words, the application layer configurations that may be used are based on whether the network can provide the QoS guarantees that are necessary for supporting the application layer configurations. The application layer configurations that may be used may be called Available Application Layer Configurations.

[0156] At 632, the WTRU Application sends a message to the Application Server 616 to indicate which application layer configurations are part of the list of Available Application Layer Configurations The Application Server may reply with a list of application layer configurations that it considers to be available. Alternatively, the Application Server may respond with an indication of which of the Available Application Layer Configurations should be used . The point of this process is that the WTRU Application and Application Server exchange information about what application configurations they believe can be supported by their associated access networks and then select an application layer configuration to use. The application layer configuration that is selected to be used may be called the Selected Application Layer Configuration.

[0157] At 634, the WTRU Application invokes an API to indicate the Selected Application Layer Configuration to the PUC Enabler Client. At 636 the PUC Enabler Client 604 may indicate the Selected Application Layer Configuration to the UPF-C. This message will be sent to the IP Address and Port number that were received by the MT Part 606 and sent by the MT part of the WTRU to the PUC Enabler Client 604 at 618.

[0158] At 638, the UPF-C will respond to the message of 636 to confirm that the Selected Application Layer Configuration has been applied by the UPF. In other words, the UPF confirms that QoS treatment has been configured for the application flows based on the Selected Application Layer Configuration and that the WTRU should use the QoS Rules that are associated with the Application Layer Configuration.

[0159] At 640, the WTRU Application and Application server may each begin to send and receive traffic. The traffic will receive QoS treatment from the network based on the Selected Application Layer Configuration. Receiving QoS treatment means that packet markings will be applied to the uplink application layer traffic based on the QoS Rules that are associated with the Selected Application Layer Configuration. The packet markings may be used by the RAN node to determine how to treat uplink traffic when the RAN node sends the traffic to the UPF. Receiving QoS treatment means that the QoS Rules that are associated with the Selected Application Layer Configuration or the associated packet markings will be used to determine what logical channel and what radio bearers should be used to transmit the uplink traffic.

[0160] At 640, the UPF-C may determine that the QoS treatment that is required by the Application Layer Configuration can no longer be guaranteed. For example, at 640a, RAN 608 may determine that there is a congestion situation in the RAN and that the QoS guarantee can no longer be maintained. RAN 608 may notify the UPF-C at 640b that the QoS guarantee can no longer be maintained. The UPF-C's determination that the QoS treatment that is required by the Application Layer Configuration can no longer be guaranteed may be based on the notification at 640b. For example, the UPF-C may receive a notification from the PCF or QAM System that the QoS guarantee can no longer be maintained or that the WTRU may no longer be provided certain QoS guarantees. The UPF-C's determination that the QoS treatment that is required by the Application Layer Configuration can no longer be guaranteed may be based on the notification from the PCF or QAM System.

[0161] At 642, based on the determination at 640, the UPF-C may send a message to the PUC Enabler Client 604 to indicate that a different application layer configuration should be applied. The message will identify the application layer configuration should now be applied.

[0162] At 644, based on receiving the message at 642, the PUC Enabler Client 604 will apply the QoS Rules that are associated with the application layer configuration that should now be applied. The PUC Enabler Client 604 may then send a message to the UPF-C to acknowledge the request to apply the new application layer configuration. At 646, the PUC Enabler Client 604 will notify the WTRU Hosted Application 602 that the new application layer configuration should be applied.

[0163] At 648 the UE Hosted Application 602 will notify that the Application Server 616 that the application layer configuration(s) that it can support have changed. The WTRU Hosted Application 602 and the Application Server 616 will begin to use the new application layer configuration. At 650, the WTRU Application and Application server continue to send and receive traffic. The traffic will receive QoS treatment from the network based on the new Selected Application Layer Configuration. [0164] In view of FIG. 6, a WTRU may receive information about a connection to a data network at 618. The information includes an IP Address and Port Number of the UPF-C. The information about the connection to the PSA UPF may also include 2 QoS Rules. The first QoS Rule may apply to all traffic that is sent to the IP Address and Port Number of the UPF-C. The second QoS Rule may be a default QoS Rule for the connection to the PSA UPF and may apply to all traffic that targets the DN (i.e. does not target the UPF-C). [0165] The WTRU may at 622 receive, from an Application, information about a flow. The information identifies the flow and includes application layer configuration(s) that are associated with the flow. The application layer configuration(s) describes requirements of the flow (e.g. , data rate and latency). The WTRU may, at 624, send a request to the IP Address and Port Number of the UPF-C. The request may include the application layer configuration(s) and information that identifies the flow. The WTRU may, at 624, receive a response form the UPF-C. The response indicates which application layer configuration(s) can be supported by the network and includes QoS Rule(s) for the application layer configuration(s) that can be supported. At 630, the WTRU may send information to a hosted application. The information that is sent to the application indicates which application layer config uration(s) can be supported by the network. The WTRU may, at 634, receive an indication from the hosted application identifying what application layer configuration will be used. The WTRU may, at 636, send a message to the IP Address and Port Number of the UPF-C. The message indicates which application layer configuration is used for the flow (i.e. which application layer configuration is selected). The WTRU may, at 638, receive an indication from the UPF-C that the QoS Rule that is associated with the application layer configuration may be applied. The WTRU may, at 640, transmit uplink data from the application and uses the QoS Rules to determine what packet markings to apply to the uplink traffic and what radio bearers to use to transmit the uplink traffic

[0166] The WTRU may optionally, at 642, receive receives a message from the UPF-C that a different application layer configuration, which is association with a second set of QoS Rules, should be applied, and may optionally transmit uplink data from the application and use the second set of QoS Rules to determine what packet markings to apply to the uplink traffic and what radio bearers to use to transmit the uplink traffic at 644. The WTRU may optionally, at 646, notify the WTRU Hosted Application that the different application layer configuration should be used.

[0167] The PUC Enabler Client may be hosted (i.e., may run) in the TE part of the WTRU. In this scenario, the PUC Enabler Client may have an interface to the MT part of the WTRU. The interface to the MT part of the WTRU may be based on AT Commands or a set of APIs. As described at 618 of FIG. 6, the interface to the MT part of the WTRU may be used by the PUC Enabler client to receive information about the connection to the PSA UPF. The information may include an IP Address and Port Number of the UPF-C. In this scenario, the PUC Enabler client may run as an application or may be part of the OS. The PUC Enabler Client may expose an API interface to WTRU Host Applications as described above.

[0168] The PUC Enabler Client may be hosted (i.e., may run) in the MT part of the WTRU. The PUC Enabler Client may expose an API interface to WTRU Host Applications as described above and the API interface may be based on AT commands. In this scenario, it may be the case that the MT part of the WTRU provides the functionality of the PUC Enabler Client.

[0169] FIG. 7 is a flowchart of an example process 700 of a negotiating application layer configuration with an access server. In some implementations, one or more process blocks of FIG. 7 may be performed by a WTRU.

[0170] As shown in FIG. 7, process 700 may include, at 702, receiving connection information corresponding to a connection to a data network, via a wireless network, the connection information including at least one of an User Plane Function (UPF) Control Plane (UPF-C) address and an UPF- C port number. For example, a WTRU hosted client may receive connection information corresponding to a connection to a data network, via a wireless network the connection information including at least one of a UPF-C address and a UPF-C port number, as described above. As also shown in FIG. 7, process 700 may include, at 704, receiving, from a hosted application, two or more application layer configurations and flow information corresponding to the two or more application layer configurations. For example, The WTRU may receive, from a hosted application, two or more application layer configurations and flow information corresponding to the two or more application layer configurations, as described above. As further shown in FIG. 7, process 700 may include sending, to the UPF-C, the two or more the application layer configurations and the corresponding flow information AT 706. For example, the WTRU may send, to the UPF-C, the two or more the application layer configurations and the corresponding flow information, as described above. As also shown in FIG. 7, process 700 may include receiving, from the UPF-C, quality of service (QoS) rules associated with the flow information and an indication of at least one application layer configuration that is supported by the wireless network at 708. For example, the WTRU may receive, from the UPF- C, QoS rules associated with the flow information and an indication of at least one application layer configuration that is supported by the wireless network, as described above. As further shown in FIG. 7, process 700 may include sending, to the hosted application, an indication of the at least one application layer configuration that is supported by the wireless network at 710. For example, the WTRU may send, to the hosted application, an indication of the at least one application layer configuration that is supported by the wireless network, as described above. As also shown in FIG. 7, process 700 may include receiving, from the hosted application, uplink traffic and applying packet markings to the uplink traffic based on the QoS rules associated with the at least one application layer configuration supported by the wireless network at 712. For example, the WTRU may receive, from the hosted application, uplink traffic and applying packet markings to the uplink traffic based on the QoS rules associated with the at least one application layer configuration supported by the wireless network, as described above. [0171] Process 700 may include additional implementations, such as any single implementation or any combination of implementations described below and/or in connection with one or more other processes described elsewhere herein. A first implementation, process 700 may include sending, to the UPF-C, an indication of an active application layer configuration. A second implementation, alone or in combination with the first implementation, process 700 may include receiving, from the UPF-C, confirmation of at least one active application layer configuration applied by the UPF-C.

[0172] A third implementation, alone or in combination with the first and second implementation, process 700 may include receiving, from the UPF-C, a notification to apply a second application layer configuration to the flow information. A fourth implementation, alone or in combination with one or more of the first through third implementations, process 700 may include sending, to the UPF-C, an acknowledgement of the notification to apply the second application layer configuration to the flow information.

[0173] A fifth implementation, alone or in combination with one or more of the first through fourth implementations, process 700 may include sending, to the hosted application, a notification to apply the second application layer configuration to the flow information. In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, each of the two or more application layer configurations include one or more of: a protocol type, a maximum bit rate for data sent between the hosted application and an application server (AS), a delay budget for the data sent between the hosted application and the AS, an indication of whether a packet data unit (PDU) set QoS is enabled, or a direction being in an uplink (UL) or a down link (DL).

[0174] In a seventh implementation, alone or in combination with one or more of the first through sixth implementations, the flow information corresponds with traffic flows between the hosted application and an application server (AS). In an eighth implementation, alone or in combination with one or more ofthe first through seventh implementations, the corresponding flow information, received from the hosted application, depicts the traffic flows as one or more internet protocol (IP) 4-tuples.

[0175] Although FIG. 7 shows example blocks of process 700, in some implementations, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0176] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

CLAIMS What is Claimed:

1 . A method performed by a wireless transmit/receive unit (WTRU) hosted client, the method comprising: receiving connection information corresponding to a connection to a data network, via a wireless network, the connection information including at least one of a User Plane Function (UPF) Control Plane (UPF-C) address and a UPF-C port number; receiving, from a hosted application, two or more application layer configurations and flow information corresponding to the two or more application layer configurations; sending, to the UPF-C, the two or more the application layer configurations and the corresponding flow information; receiving, from the UPF-C, quality of service (QoS) rules associated with the flow information and an indication of at least one application layer configuration that is supported by the wireless network; sending, to the hosted application, an indication of the at least one application layer configuration that is supported by the wireless network; and receiving, from the hosted application, uplink traffic and applying packet markings to the uplink traffic based on the QoS rules associated with the at least one application layer configuration supported by the wireless network.

2. The method of claim 1 , further comprising sending, to the UPF-C, an indication of an active application layer configuration.

3. The method of claim 2, further comprising receiving, from the UPF-C, confirmation of at least one active application layer configuration applied by the UPF-C.

4. The method of claim 3, further comprising receiving, from the UPF-C, a notification to apply a second application layer configuration to the flow information.

5. The method of claim 4, further comprising sending, to the UPF-C, an acknowledgement of the notification to apply the second application layer configuration to the flow information.

6. The method of claim 4, further comprising sending, to the hosted application, a notification to apply the second application layer configuration to the flow information.

7. The method of claim 1 , wherein each of the two or more application layer configurations include one or more of: a protocol type, a maximum bit rate for data sent between the hosted application and an application server (AS), a delay budget for the data sent between the hosted application and the AS, an indication of whether a packet data unit (PDU) set QoS is enabled, or a direction being in an uplink (UL) or a down link (DL).

8. The method of claim 1 , wherein the flow information corresponds with traffic flows between the hosted application and an application server (AS).

9. The method of claim 8, wherein the corresponding flow information, received from the hosted application, depicts the traffic flows as one or more internet protocol (IP) 4-tuples.

10. A wireless transmit/receive unit (WTRU), comprising: processor circuitry configured to host a client; and a transceiver communicatively coupled to the processor circuitry and configured to: receive connection information corresponding to a connection to a data network via a wireless network, the connection information including at least one of a User Plane Function (UPF) Control Plane (UPF-C) address and a UPF-C port number; receive, from a hosted application, two or more application layer configurations and flow information corresponding to the two or more application layer configurations; send, to the UPF-C, the two or more application layer configurations and the corresponding flow information; receive, from the UPF-C, quality of service (QoS) rules associated with the flow information and an indication of at least one application layer configuration that is supported by the wireless network; send, to the hosted application, an indication of the at least one application layer configuration that is supported by the wireless network; and receive, from the hosted application, uplink traffic and applying packet markings to the uplink traffic based on the QoS rules associated with the at least one application layer configuration supported by the wireless network.

11 . The WTRU of claim 10, wherein the transceiver is further configured to send, to the UPF-C, an indication of an active application layer configuration.

12. The WTRU of claim 11 , wherein the transceiver is further configured to receive, from the UPF-C, confirmation of at least one active application layer configuration applied by the UPF-C.

13. The WTRU of claim 12, wherein the transceiver is further configured to receive, from the UPF-C, a notification to apply a second application layer configuration to the flow information.

14. The WTRU of claim 13, wherein the transceiver is further configured to send, to the UPF-C, an acknowledgement of the notification to apply the second application layer configuration to the flow information.

15. The WTRU of claim 13, wherein the transceiver is further configured to send, to the hosted application, a notification to apply the second application layer configuration to the flow information.

16. The WTRU of claim 10, wherein each of the two or more application layer configurations include one or more of: a protocol type, a maximum bit rate for data sent between the hosted application and an application server (AS), a delay budget for the data sent between the hosted application and the AS, an indication of whether a packet data unit (PDU) set QoS is enabled, or a direction being in an uplink (UL) or a down link (DL).

17. The WTRU of claim 10, wherein the flow information corresponds with traffic flows between the hosted application and an application server (AS).

18. The WTRU of claim 17, wherein, wherein the corresponding flow information, received from the hosted application, depicts the traffic flows as one or more internet protocol (IP) 4-tuples.

19. A non-transitory computer readable storage medium storing computer readable instructions which when executed by processing circuitry cause the processing circuitry to: receive connection information corresponding to a connection to a data network via a wireless network, the connection information including at least one of a User Plane Function (UPF) Control Plane (UPF-C) address and a UPF-C port number; receive, from a hosted application, two or more application layer configurations and flow information corresponding to each of the two or more application layer configurations; send, to the UPF-C, the one or more application layer configurations and the corresponding flow information; receive, from the UPF-C, quality of service (QoS) rules associated with the flow information and an indication of at least one application layer configuration that is supported by the wireless network; sending, to the hosted application, an indication of the at least one application layer configuration that is supported by the wireless network; and receive, from the hosted application, uplink traffic and applying packet markings to the uplink traffic based on the QoS rules associated with the at least one application layer configuration supported by the wireless network.