Network controlled route selection

The method for WTRU and NF interaction in determining DNN and S-NSSAI values addresses URSP limitations, enabling efficient PDU session management and improved data routing in wireless communication systems.

WO2026235956A1PCT designated stage Publication Date: 2026-11-12INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/025632
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-04-28
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently routing application traffic due to limitations in User Equipment Route Selection Policy (URSP) rules, particularly in determining appropriate Protocol Data Unit (PDU) sessions for application data transmission.

Method used

A method for a wireless transmit/receive unit (WTRU) to request information for routing application data, receive responses on using existing or establishing PDU sessions, and a network function (NF) to determine and communicate appropriate DNN and S-NSSAI values for routing, enabling efficient PDU session management.

Benefits of technology

Enhances the ability to select or establish optimal PDU sessions for application data routing, improving network efficiency and data transmission quality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026025632_12112026_PF_FP_ABST
    Figure US2026025632_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method performed by a WTRU may comprise: transmitting, to a NF, a request message requesting information for routing WTRU application data; receiving, from the NF, a response message indicating whether the WTRU application data can be routed using one of one or more existing PDU sessions; on a condition that an existing PDU session can be used to carry the WTRU application data, transmitting a PDU session modification request; and on a condition that no existing PDU session can be used to carry the WTRU application data, transmitting a PDU session establishment request.
Need to check novelty before this filing date? Find Prior Art

Description

NETWORK CONTROLLED ROUTE SELECTIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Non-Provisional Application No. 19 / 202,090, filed May 8, 2025, the contents of which are incorporated herein by reference.BACKGROUND

[0002] In wireless communication systems, such as Fifth Generation (5G) networks, a wireless transmit / receive unit (WTRU) may utilize User Equipment Route Selection Policy (URSP) rules to determine the appropriate protocol data unit (PDU) session for routing application traffic. Inputs to the URSP rule evaluation may include parameters such as the WTRU application type, destination fully qualified domain name (FQDN), and destination IP address. Based on these inputs, the URSP rule evaluation produces a set of PDU session characteristics, such as the data network name (DNN) and single network slice selection assistance information (S-NSSAI). The WTRU then selects or establishes a PDU session that matches these characteristics.SUMMARY

[0003] A method performed by a wireless transmit / receive unit (WTRU) may comprise: transmitting, to a network function (NF), a request message requesting information for routing WTRU application data; receiving, from the NF, a response message indicating that no existing packet data unit (PDU) session can be used to carry the WTRU application data; and transmitting a PDU session establishment request.

[0004] A method performed by a WTRU may comprise: transmitting, to a NF, a request message requesting information for routing WTRU application data; receiving, from the NF, a response message indicating whether the WTRU application data can be routed using one of one or more existing PDU sessions; on a condition that an existing PDU session can be used to carry the WTRU application data, transmitting a PDU session modification request; and on a condition that no existing PDU session can be used to carry the WTRU application data, transmitting a PDU session establishment request.

[0005] A method performed by a NF may comprise: receiving, from a WTRU, a request message requesting information for routing WTRU application data; determining a data network name (DNN) value and a single network slice selection assistance information (S-NSSAI) value for a route to carry the application data; determining whether the DNN value and the S-NSSAI value correspond to one of one or more existing PDU sessions; on a condition that the DNN value and S-NSSAI value correspond to an existing PDU session, transmitting a response message to the WTRU, indicating the WTRU to use the existing PDU session; and on a condition that the DNN value and S-NSSAI value do not correspond to an existing PDU session, transmitting a response message to the WTRU, indicating the WTRU to establish a new PDU session.- 1 - 9694042.1IDC-2025P00315WQBRIEF DESCRIPTION OF THE DRAWINGS

[0006] 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:

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

[0008] FIG. 1B 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;

[0009] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (ON) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment;

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

[0011] FIG. 2 illustrates an example network-controlled route selection procedure;

[0012] FIG. 3 illustrates an example network-controlled route selection with application authentication and authorization procedure;

[0013] FIG. 4 illustrates an example network-controlled route selection procedure as performed by a WTRU;

[0014] FIG. 5 illustrates an example network-controlled route selection procedure as performed by a WTRU; and

[0015] FIG. 6 illustrates an example network-controlled route selection procedure as performed by a network function.DETAILED DESCRIPTION

[0016] The following acronyms and abbreviations may be referred to:AAA-S Authentication, Authorization and Accounting ServerAF Application FunctionAMF Access and Mobility Management FunctionApplication Identifier App IDAS Application ServerASP Application Service ProviderDNN Data Network NameDNS Domain Name SystemDRB Data Radio BearerEAP Extensible Authentication ProtocolFQDN Fully Qualified Domain NameGPSI Generic Public Subscription IdentifierH-PCF Home PCF- 2 - 9694042.1IDC-2025P00315WCHPLMN Home PLMNID IdentifierIMS IP Multimedia SubsystemIP Internet ProtocolMMS Multimedia Messaging ServiceMNO Mobile Network OperatorMT Mobile TerminationNAS Non-Access StratumNF Network FunctionNRF Network Repository FunctionPCC Policy and charging controlPCF Policy Control FunctionPCF ID PCF IdentifierPCO Protocol Configuration OptionsPDU Protocol Data UnitPLMN Public Land Mobile NetworkPM Policy ManagementRAN Radio Access NetworkRSD Route Selection DescriptorS-NSSAI Single Network Slice Selection Assistance Information SBI Service Based InterfaceSDF Service Data FlowSM Session ManagementSMF Session Management FunctionSRB Signaling Radio BearerSRV ServiceSSC Session and Service ContinuityTTL Time To LiveUDM Unified Data ManagementUE User EquipmentUPF User Plane FunctionURSP UE Route Selection PolicyV-PCF Visited PCFVPLMN Visited PLMNWTRU Wireless Transmit I Receive Unit- 3 - 9694042.1IDC-2025P00315WC

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

[0018] As shown in FIG. 1 A, 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 110, and other networks 112, 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 (ST A), may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), 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.

[0019] 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 GN 106, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b 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 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0020] The base station 114a 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 114a 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 - 4 - 9694042.1IDC-2025P00315WGprovide 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 114a may include three transceivers, i.e. , one for each sector of the cell. In an embodiment, the base station 114a 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.

[0021] 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).

[0022] 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).

[0023] 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).

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

[0025] 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).

[0026] 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 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0027] The base station 114b 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 - 5 - 9694042.1IDC-2025P00315WQsuch 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 cellularbased 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 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the GN 106.

[0028] The RAN 104 may be in communication with the GN 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 GN 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 GN 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 GN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0029] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, 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 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0030] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multimode 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.

[0031] FIG. 1B 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 sub-combination of the foregoing elements while remaining consistent with an embodiment.- 6 - 9694042.1IDC-2025P00315WG

[0032] 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 118 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. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0033] 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 116. 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.

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

[0035] 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 RAT s, such as NR and I EEE 802.11 , for example.

[0036] The processor 118 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 118 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).

[0037] The processor 118 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 - 7 - 9694042.1for 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.

[0038] 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 116 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.

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

[0040] 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 self-interference 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)).

[0041] FIG. 1C is a system diagram illustrating the RAN 104 and the ON 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 116. The RAN 104 may also be in communication with the ON 106.

[0042] 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 116. 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.- 8 - 9694042.1IDC-2025P00315WC

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

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

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

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

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

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

[0049] Although the WTRU is described in FIGS. 1A-1D 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.

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

[0051] 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 - 9 - 9694042.1IDC-2025P00315WC(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.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (I BSS) 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.

[0052] When using the 802.11ac 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.11 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.

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

[0054] 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).

[0055] Sub 1 GHz modes of operation are supported by 802.11af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11 ah relative to those used in 802.11n, and 802.11ac.802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 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 - 10 - 9694042.1including 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).

[0056] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11 ac, 802.11 af, and 802.11 ah, 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.11ah, 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.

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

[0058] FIG. 1D 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 116. The RAN 104 may also be in communication with the CN 106.

[0059] 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 gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, 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 g NB 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).

[0060] 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- 11 - 9694042.1IDC-2025P00315WGintervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and / or lasting varying lengths of absolute time).

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

[0062] 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. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0063] The CN 106 shown in FIG. 1D 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.

[0064] 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 WiFi.- 12 - 9694042.1IDC-2025P00315WQ

[0065] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 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 IPbased, non-IP based, Ethernet-based, and the like.

[0066] 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 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184a, 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.

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

[0068] In view of FIGs. 1A-1D, and the corresponding description of FIGs. 1A-1D, 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.

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

[0070] 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 - 13 - 9694042.1IDC-2025P00315WCmay 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.

[0071] Hereinafter, the PCF is a network function that is used to make policy decisions or recommend actions that are based on policies. The policies may be configured in the PCF by an MNO. The WTRU may send messages to a PCF and may receive messages from the PCF. The PCF is not a PCF that is associated with a specific network slice. There is a PCF that stores policies that are used to determine what network slice should be accessed by a WTRU. The policies that are stored in the PCF may be associated with many network slices, or network slice types.

[0072] Hereinafter, the messages that are sent from the WTRU to the PCF and vice versa may be carried via the NAS protocol and may be transmitted via signaling radio bearers (SRBs). The messages that are sent from the WTRU to the PCF and vice versa may be carried via a PDU session and may be transmitted via data radio bearers (DRBs). If the messages are sent in a PDU session (i.e., over the DRBs), the protocol that is used to communicate between the WTRU and PCF may be an IP-based protocol.

[0073] Hereinafter, the actions that are described as taking place in the PCF in this paper may instead be implemented in a network function or a server that is used to provide the WTRU with route selection information. The route selection information (e.g., DNN / S-NSSAI, Access type preference, SSC modes etc.) is used by the WTRU for selecting or establishing a PDU session for specific traffic.

[0074] Hereinafter, the terms route, route information and route selection information are used. A route may refer to a PDU session or a user plane path that may carry data traffic. Route information or route selection information may refer to information or attributes that can be used to select / obtain / setup a route / PDU session for the WTRU traffic.

[0075] A PCF determining route selection information / route information because of a (route selection) request from the WTRU may mean that the PCF identifies / determines information or attributes that characterize a suitable route / path / PDU session for the WTRU traffic, such as DNN / S-NSSAI, Access type preference, SSC modes, etc. which may be used by the WTRU for selecting or establishing a PDU session for specific traffic.

[0076] A PCF obtaining / determining / selecting a route for the WTRU traffic as a result of a request from the WTRU may refer to (1) the PCF determining route information / route selection information for the WTRU request and (2) determining whether there exists a route / PDU session that can carry WTRU traffic using the determined route information and potentially (3) selecting from the existing routes / PDU session one or more routes for WTRU traffic to choose from.

[0077] Hereinafter, the terms route information, route selection information and route may be used interchangeably. A "determining route information / route selection information” step may need to occur before a “determining / selecting a route” occurs.

[0078] In 5G systems, a network may utilize URSP rules to control how a WTRU maps application traffic to an existing route or initiates the establishment of a new one. A "route” corresponds to a PDU session, which is uniquely identified by a combination of a DNN and a S-NSSAI value. Therefore, the network must provision the WTRU with URSP rules that cover any PDU session the WTRU may need to establish.- 14 - 9694042.1IDC-2025P00315WC

[0079] To maintain synchronization, the network must also track which policies are currently stored on the WTRU. In support of this, the WTRU is required to report its installed URSP rules to the network. For example, during registration, the WTRU may include a WTRU Route Selection Policy Container (also referred to as a WTRU STATE INDICATION) to inform the network of its current policy state. Additionally, some URSP rules are specific to certain locations, such as PLMNs, which may necessitate a greater number of rules or larger information elements (e.g., more RSDs) to accommodate the location-specific granularity.

[0080] In future wireless systems, such as Sixth Generation (6G) systems, it would be advantageous to introduce a framework that enables the network to influence or determine the routing of application traffic (i.e., which PDU session to use or establish) without requiring extensive policy provisioning to the WTRU. It is also desirable to avoid situations where the network and WTRU need to perform procedures so that the network can keep track of what policies have been provisioned in the WTRU.

[0081] FIG. 2 illustrates an exemplary procedure for network-controlled route selection. As shown in FIG. 2, WTRU 202 may host application 203 and include MT 205.

[0082] At 220, WTRU 202 may perform a registration procedure with the network to gain access to network services. Upon successful completion of registration, the network may optionally provide the WTRU with an identifier of the PCF, referred to as the PCF ID. This identifier enables WTRU 202 to directly communicate with PCF 212 for policy-related signaling, assuming such capability is supported.

[0083] For example, WTRU 202 may receive the PCF ID as part of the PCO included in the Registration Complete message. Alternatively, the PCO may contain information related to the NRF, which allows WTRU 202 to discover network functions dynamically. If both the network and WTRU 202 support NRF-based service discovery, WTRU 202 may query the NRF to obtain endpoint details for PCF 212, enabling direct communication with the appropriate policy control function.

[0084] At 222, application 203 may have some traffic ready to be sent. In this case, WTRU application 203 indicates to MT 205 that application traffic needs to be sent.

[0085] At 224, based on the data from the WTRU application 203 that some traffic needs to be sent, WTRU 202 may determine a traffic descriptor for the received application data. WTRU 202 may use information such as a destination IP 3-tuple that may be obtained from the IP header of the data traffic received from the WTRU application 203 to determine a traffic descriptor. This destination IP 3-tuple information may include a destination IP address, destination port number, and protocol type values. WTRU 202 may use an application ID value associated with the traffic of interest as a part of the traffic descriptor.

[0086] At 226, WTRU 202 may transmit a message to PCF 212, requesting information about the appropriate route to be used for a given application's traffic. This message may include a traffic descriptor determined by WTRU 202 for example, at 224. The traffic descriptor may comprise, for example, a destination IP 3-tuple (source IP, destination IP, port), an application identifier (App ID), or an application type identifier.- 15 - 9694042.1IDC-2025P00315WC

[0087] The message may also include an ASP ID or an AF ID, if such identifiers are available at the WTRU (e.g., obtained from the application itself or via configuration by an application server). Alternatively, the message may include the identifier of an existing PDU session (PDU session ID) along with supplemental information not included in the original traffic descriptor associated with that session.

[0088] WTRU 202 may send this request to PCF 212 using a NAS message. The message may be initially sent to the serving RAN node 206, which forwards it to a core network function, such as AMF 208. Upon receiving the message, AMF 208 may identify it as a WTRU policy-related request based on an indication within the message (e.g., a message type marked as "Policy Management”). The message may also include a PCF ID designating the intended recipient PCF. WTRU 202 may have acquired this identifier during the registration procedure at step 220.

[0089] Alternatively, if WTRU 202 is capable of directly communicating with PCF 212 over the SBI, and has discovered the PCF endpoint (e.g., by querying the NRF), it may send the message directly to PCF 212 without routing through the AMF 208. The AMF 208 may then forward the WTRU message to the PCF (i.e., the PCF that handles WTRU policies). The message sent by WTRU 202 to PCF 212 may be sent over IP between WTRU 202 and the core network (e.g., AMF 208 or PCF 212).

[0090] The traffic route request message may also include a list of PDU session IDs, to indicate the PDU sessions that WTRU 202 has already established with the network.

[0091] If the WTRU does not provide the list of active PDU session IDs, PCF 212 may retrieve this information independently. To do so, PCF 212 may access the WTRU's context stored in the network. Alternatively, PCF 212 may query the BSF to identify the PCFs responsible for SM policies. The PCF handling SM policies may already have knowledge of the WTRU's active PDU sessions or may acquire this information through interaction with the SMFs serving WTRU 202.

[0092] At 228, after PCF 212 receives the request message from WTRU 202, PCF 212 may determine to identify a route for the WTRU application traffic. PCF 212 may use the traffic descriptor provided by WTRU 202 at 226 to determine whether the data traffic associated with this traffic descriptor should be mapped to an existing PDU session. PCF 212 may first check whether there is an association between the traffic descriptor and any existing PDU sessions serving WTRU 202. Such information may be stored locally at PCF 212.

[0093] When WTRU 202 establishes a PDU session, information about the PDU session (e.g., PDU session ID, DNN, and S-NSSAI) may be reported to PCF 212. When the PDU session is released, PCF 212 may be notified accordingly. Thus, PCF 212 may maintain awareness of the active PDU sessions associated with WTRU 202. Alternatively, PCF 212 may query other network functions to obtain information about the association between the traffic descriptor and PDU sessions for WTRU 202.

[0094] PCF 212, which handles WTRU policies, may interact with another PCF that handles SM policies (e.g., SM-PCF) to obtain information about the association between a traffic descriptor and PDU sessions for WTRU 202. SM-PCF may retrieve such information from PCC rules related to WTRU traffic. For example, SM-PCF may determine whether a PCC rule includes the traffic descriptor in its SDF template. If such a rule exists, SM-PCF may determine the associated PDU session.- 16 - 9694042.1IDC-2025P00315WC

[0095] For example, if the traffic descriptor includes a destination IP 3-tuple, SM-PCF may check for a PCC rule that includes this IP 3-tuple in the SDF template. In another case, if the traffic descriptor includes an application ID, the SM-PCF may try to find a PCC rule that includes the application ID in its SDF template. When such a PCC rule is found, the SM-PCF may identify the associated PDU session and send the PDU session ID to PCF 212.

[0096] If the traffic descriptor includes multiple components (e.g., a destination IP 3-tuple and an application ID), and only a subset of the components is found in a PCC rule, the SM-PCF may still determine that there is a partial match. In this case, the traffic may still be associated with the corresponding PDU session.

[0097] For example, if WTRU 202 provided an IP 3-tuple, IP-3-tuple-1, and an application ID value, application ID 1 , in the traffic descriptor, the SM-PCF may look for PCC rules that have both of the IP 3-tuple and application ID components as part of the SDF template of the PCC rule. In the example where the SM-PCF finds a PCC rule, PCC rulel, that includes the application ID1, but not the IP-3-tuple-1 in the SDF template, then the SM-PCF may determine that the traffic of interest for the WTRU is or can be associated with the PDU session associated with the PCC rulel. SM-PCF may determine that there is a PCC rule, PCC rulel , that is active and associated with an existing PDU session (e.g., PDU session ID1), that supports traffic using application ID1 as part of the traffic detection information. In this case, even for a different IP 3-tuple, SM-PCF or PCF 212 may determine that the PDU session ID1 can be used to carry the WTRU application traffic (using IP-3-tuple-1 and / or application ID1 as part of the traffic description).

[0098] Alternatively, or additionally, PCF 212 may determine a suitable DNN / S-NSSAI combination for the traffic descriptor provided by WTRU 202.

[0099] PCF 212 may determine this information locally, or by interacting with other network functions such as the SM-PCF. PCF 212 may use information obtained from WTRU 202 such as application ID, ASP ID, AF ID (if provided) to determine which DNN / S-NSSAI combination is suitable for the WTRU application traffic.

[0100] When PCF 212 determines that DNN and S-NSSAI are suitable for the traffic descriptor of interest, PCF 212 may check whether there is an existing PDU session for WTRU 202 using that DNN / S-NSSAI combination.

[0101] The PCF 212 may interact with another network function (e.g., an SMF) that maintains WTRU context to determine if such a PDU session exists. If PCF 212 finds an existing PDU session ID associated with that DNN / S-NSSAI, PCF 212 may conclude that the application traffic can be routed through it.

[0102] If multiple PDU sessions are established with the same DNN / S-NSSAI, PCF 212 may use elements of the traffic descriptor (e.g., using traffic descriptor elements and checking if there is a PDU session that already carries application data that matches with one or more component of the traffic descriptor provided by WTRU 202 at 226), to further determine which PDU session ID is suitable for the WTRU application traffic. If no existing PDU session is found to be suitable, PCF 212 may determine that a new PDU session should be established.

[0103] The PCF 212 may also obtain the location of WTRU 202, either locally or through interaction with other network functions. The PCF 212 may use this location information to assist in selecting a suitable route, including DNN / S-NSSAI and potentially an associated PDU session ID.- 17 - 9694042.1IDC-2025P00315WC

[0104] In both scenario 230 and scenario 240, PCF 212 may send a reply message to WTRU 202 containing information related to the selection of a route for the WTRU's application traffic. As described in more detail below, scenario 230 may apply when an existing PDU session can be used, whereas scenario 240 may apply when a new PDU session must be established.

[0105] In scenario 230, if, at 228, PCF 212 determines that an existing PDU session for WTRU 202 is suitable to carry the application traffic of WTRU 202, then at 231, PCF 212 may include an indication in the response message to WTRU 202 to use that existing PDU session. This indication may take the form of a PDU session ID (e.g., PDU Session ID-b) included in the response message. The presence of the PDU session ID signals to WTRU 202 that the identified session may be used to route the uplink application traffic. Additionally, PCF 212 may include the corresponding DNN and S-NSSAI values (e.g., DNN-x and S-NSSAI-y) in the response message.

[0106] At 233, triggered by the response message at step 231 , WTRU 202 may initiate a PDU session modification procedure with the network, providing the relevant traffic descriptor associated with the application 203. The PDU session modification request may be associated with the identified existing PDU session.

[0107] In scenario 240, if at 228, PCF 212 determines DNN and S-NSSAI values for the application traffic of WTRU 202 and determines that no existing PDU session is appropriate for carrying this traffic, then at 241, PCF 212 may send a response message to WTRU 202 indicating that a new PDU session should be established.

[0108] PCF 212 may include the determined DNN-x and S-NSSAI-y values in the response message at 241. Alternatively, instead of explicitly including the DNN and S-NSSAI, the PCF may provide a PDU session Association Identifier that may be resolved by the network to the corresponding DNN / S-NSSAI combination. This allows the network to conceal the DNN and S-NSSAI values from WTRU 202, if needed. The absence of a PDU session ID in the response may be interpreted by WTRU 202 as an indication that no existing PDU session is suitable and that a new PDU session must be established to route the uplink application traffic.

[0109] At 243, WTRU 202 may be triggered by the message received at step 241 to establish a new PDU session with the network. The WTRU initiates a PDU session establishment procedure targeting the DNN-x / S-NSSAI-y combination. The PDU Session Establishment Request sent by the WTRU may include the DNN and S-NSSAI values received at 241 (i.e., DNN-x and S-NSSAI-y). Alternatively, the request may include a PDU Session Association Identifier received earlier (e.g., at 231) in place of the explicit DNN / S-NSSAI values. The request may also include the traffic descriptor to inform the network of the type of application traffic intended to be carried over the new PDU session.

[0110] At 250, WTRU 202 may transmit application traffic using the PDU session that was previously determined. The traffic is sent to the UPF 214, which then forwards it to the appropriate application server. The WTRU 202 may have a default route, such as a default PDU session established with the network to carry general or unspecified traffic. If PCF 212 determines that no other PDU session (i.e., other than the default session) is suitable for the application traffic, it may instruct WTRU 202 to use this default route or default PDU session for transmitting the application data.

[0111] In addition to the information provided in the response message at step 231 or 232, such as an indication to use a new or existing PDU session, the DNN / S-NSSAI values, and the PDU session ID, PCF 212 may also include additional information relevant to WTRU 202 for routing its application traffic.- 18 - 9694042.1IDC-2025P00315WC

[0112] In one embodiment, PCF 212 may determine a suitable SSC mode for routing WTRU application traffic.

[0113] PCF 212 may obtain subscription information for WTRU 202 from the UDM, indicating which SSC modes are permitted for specific DNN / S-NSSAI combinations. For example, if the subscription data specifies that only SSC mode 1 is allowed for the determined DNN-x and S-NSSAI-y, PCF 212 may check whether a PDU session already exists for WTRU 202 with that DNN / S-NSSAI combination using SSC mode 1. If such a session exists, PCF 212 may include the PDU session ID in the response to WTRU 202, instructing it to use that session for routing the application traffic.

[0114] In addition to subscription constraints, PCF 212 may also consider parameters such as the application ID, service type, or application group ID to determine the most appropriate SSC mode for the application traffic. For example, if the application ID corresponds to a gaming application that requires session continuity, such as maintaining the same WTRU IP address, PCF 212 may determine that SSC mode 1 is most suitable. Conversely, if the service type corresponds to streaming or another service that tolerates session interruptions, SSC mode 2 or SSC mode 3 may be deemed more appropriate.

[0115] In such cases, if PCF 212 identifies an existing PDU session for WTRU 202 that is associated with DNN-x and S-NSSAI-y and uses SSC mode 2 or 3, it may include this PDU session ID in the reply message, along with any additional relevant information. The PCF 212 may use information about which SSC modes WTRU 202 supports (e.g., WTRU capability related to supported SSC modes) and take it into consideration when determining a suitable SSC mode to route WTRU traffic of interest.

[0116] In another embodiment, PCF 212 may include information indicating a preferred access type for the route used to carry the WTRU's application traffic. For example, PCF 212 may determine that 3GPP access, non-3GPP access, or a multi-access route / PDU session is preferred, based on factors such as network status (e.g., congestion levels at RAN nodes), the availability of non-3GPP access for WTRU 202, or other network performance considerations.

[0117] In another embodiment, the reply message from PCF 212 may indicate that the association between the WTRU's application traffic and the provided routing information is valid only under certain location or time constraints. For example, the message may specify that the WTRU application traffic is permitted to use a route associated with DNN-x and S-NSSAI-y only in specific geographic areas, and is not valid outside those regions. In another example, the message may indicate that the route is valid only during a defined time window.

[0118] In another embodiment, the message from PCF 212 may indicate additional application descriptors that can be associated with the determined route. This information may allow WTRU 202 to avoid sending new route selection requests to the network when other applications generate uplink traffic that is already covered by the identified route.

[0119] For example, if the traffic descriptor provided by WTRU 202 includes destination IP 3-tuple- 1 , and PCF 212 determines that this traffic is associated with a particular application descriptor, PCF 212 may indicate that all traffic related to that application uses the same route. The PCF 212 may explicitly state that traffic containing application ID1- 19 - 9694042.1IDC-2025P00315WCmay be routed via PDU Session ID1. As a result, WTRU 202 may use this route for other traffic, such as one containing a different IP 3-tuple (e.g., IP 3-tuple-2), provided it pertains to the same application ID.

[0120] The application descriptor may include identifiers such as OSId or OSAppid, which are used to identify traffic associated with a specific application running on WTRU 202 (e.g., as determined by the WTRU's operating system).

[0121] The PCF 212 may also determine that a range of values associated with a destination IP 3-tuple can be mapped to the same route indicated in its message to WTRU 202. For example, PCF 212 may determine that for a given destination IP address (IP-1), a range of destination port numbers (e.g., Port-N 1 to Port-N50) may be associated with the same application traffic and can be carried over the identified route. In another case, the PCF may determine that multiple destination IP addresses or a range of IP addresses and port numbers can be used with the same route for carrying traffic through the network.

[0122] The PCF 212 may also determine that traffic from other applications can be routed using the same DNN / S-NSSAI combination if they fall within a common category. Parameters such as the application service provider identifier (ASP ID) or application group ID may be used to make this determination. For example, if application ID1 is associated with an immersive application provided by ASP ID1, then other immersive applications belonging to the same application group (e.g., an immersive service application group) and provided by ASP ID1 may also be routed using the same PDU session proposed for application ID1.

[0123] The message from PCF 212 may include one or more application descriptors or traffic descriptors that define which types of traffic are eligible to use the proposed route for WTRU 202.

[0124] In another embodiment, the reply message from PCF 212 may include a validity period for the route information. This validity period defines the time or duration during which the route information remains valid. Once this period expires, either due to the end of a specified time window or completion of the duration, the route information may be considered expired. In such cases, WTRU 202 may need to obtain updated route information for the associated application traffic.

[0125] The validity period or expiration condition indicated by PCF 212 may differ from temporary validity constraints, which define the specific time conditions during which WTRU 202 can use the route (e.g., time-of-day restrictions).

[0126] For example, when a validity period expires, WTRU 202 may be triggered to send a new route selection request to PCF 212 (similar to the request at 226). This request may include the traffic descriptor(s) for which the previous route information (e.g., route information-ID1 ) has expired. The message may also contain a list of existing PDU sessions established by WTRU 202 and additional parameters related to the last route used for the application traffic.

[0127] For example, WTRU 202 previously transmitted application traffic matching destination IP 3-tuple- 1. In response, PCF 212 had determined that the traffic should be routed via a new PDU session established to DNN-x and S-NSSAI-y, and provided corresponding route information (route information-ID1) with a validity period of 15 minutes.- 20 - 9694042.1IDC-2025P00315WCWTRU 202 subsequently established the new PDU session, assigned PDU Session ID2, and began transmitting the application traffic to the application server using that session. Once the 15-minute validity period expires, WTRU 202 may be triggered to stop using route information-ID1 and initiate a new route selection request to PCF 212 to obtain updated routing instructions.

[0128] The reply message from PCF 212 may also include an indication for WTRU 202 to use Non-Seamless Non-3GPP Offloading (NSN3 offloading) for the corresponding application traffic.

[0129] In its updated route selection request, similar to 226, WTRU 202 may include the relevant traffic descriptor(s), such as IP 3-tuple- 1 , and indicate the currently active PDU sessions. The message may also specify the PDU session most recently used to carry the traffic of interest (e.g., PDU Session ID2) and include associated route details such as DNN-x and S-NSSAI-y.

[0130] Upon receiving this new request (e.g., at step 228), PCF 212 may evaluate whether the previously used route remains valid for the WTRU's application traffic. For example, PCF 212 may assess whether DNN-x is still suitable or whether a different DNN-z should be used due to updated network status (e.g., congestion or time-of-day-based unavailability).

[0131] If PCF 212 determines that the route proposed to WTRU 202 can still be reused, PCF 212 may send a message to WTRU 202 (e.g., at 213 or 232), including the (same or similar) route information. The route information may include the DNN-x / S-NSSAI-y combination and duration value. The message from PCF 212 may further indicate to WTRU 202 to use the same PDU Session ID2 to carry the WTRU application traffic.

[0132] If the previously used route is no longer valid (e.g., due to suboptimal or unavailable DNN), PCF 212 may check whether a PDU session already exists to DNN-z / S-NSSAI-y. If PDU Session ID2 still corresponds to S-NSSAI-y, it may be partially reused. Alternatively, PCF 212 may determine that another existing or a new PDU session is needed.

[0133] Similarly to 231 or 232, PCF 212 may indicate to WTRU 202 whether to establish a new PDU session or use an existing PDU session and send new route information (e.g., route information-ID2 including DNN-z and S-NSSAI-y). The route information-ID2 may include other traffic or application descriptors that can be associated with the newly proposed route.

[0134] In response, WTRU 202 may perform a PDU session establishment or modification procedure with the network to be able to carry the WTRU traffic using the route proposed by PCF 212.

[0135] The old PDU session (e.g., PDU Session ID2), that was used to carry WTRU application traffic, may or may not be released. The WTRU may keep the PDU session active or not release the PDU Session ID2 until WTRU 202 receives the reply message from PCF 212 related to the WTRU application traffic. If the route proposed by PCF 212 is different that the previously proposed route, then WTRU 202 may proceed as follows.

[0136] If all the traffic that WTRU 202 is carrying using the old PDU Session ID2 would need to be carried into the new route, then WTRU 202 may determine to release the old PDU Session ID2 and establish a new PDU Session ID3 based on new route information.- 21 - 9694042.1IDC-2025P00315WC

[0137] If only part of the traffic for the WTRU application would need to be carried using the new route, and there would still be some traffic that would still be carried by the old PDU Session ID2, then WTRU 202 may keep (and not release) the old PDU Session ID2, and establish a new PDU Session ID3 to route the WTRU traffic of interest.

[0138] The PCF 212 may determine that for a certain route that can be used to carry WTRU application traffic, more than one SSC mode may be used. For example, SSC mode 2 or SSC mode 3 may be used for the selected route. In this case, PCF 212 may select one of the SSC mode values to be used for the WTRU.

[0139] For example, if there is an existing PDU Session-a that routes to DNN-x and S-NSSAI-y and uses SSC mode 2, then PCF 212 may select PDU Session-a and the message from PCF 212 to WTRU 202 may indicate, DNN-x, S-NSSAI-y, PDU Session-a, and SSC mode 2.

[0140] Alternatively, the message from PCF 212 may include all suitable SSC modes that can be used by WTRU 202, as well as existing PDU sessions that can be used to route WTRU application traffic. For example, the message from PCF 212 may include that a route to DNN-x and S-NSSAI-y is needed, and that for this route either SSC mode 2 or SSC mode 3 may be used. The message may further indicate that there is an existing PDU Session-a that may serve the WTRU traffic using SSC mode 2. In this case, WTRU 202 may use PDU Session-a to route WTRU application traffic of interest, using SSC mode 2.

[0141] WTRU 202 may also decide to use SSC mode 3 and hence is triggered to establish a new PDU Session-b to DNN-x and S-NSSAI-y combination, but using a different SSC mode, here SSC mode 3.

[0142] In some scenarios, WTRU 202 may be unable to establish a PDU session using the preferred route information provided by PCF 212 (e.g., due to access-type restrictions or resource unavailability). In such cases, WTRU 202 may fall back to using default route information to establish or modify a PDU session or may utilize an existing default PDU session to forward its application traffic.

[0143] In procedure 200, the WTRU interacts with the PCF responsible for WTRU policies to obtain route information for its application traffic. When the WTRU is registered with its Home PLMN (HPLMN), the PCF providing the route information is assumed to reside in the HPLMN.

[0144] When the WTRU is roaming in a Visited PLMN (VPLMN), the PCF that provides the route information may still reside in the WTRU's HPLMN. In this case, when the WTRU needs to determine a route for a particular application while registered in the VPLMN, it may send a route selection request to NFs in the VPLMN.

[0145] The WTRU may be provisioned with the identifier of the HPLMN-resident PCF (H-PCF) that serves its policies (for route selection). The WTRU may include this H-PCF ID in the route selection request message. This message may be transparently routed to the H-PCF via a VPLMN-resident PCF (V-PCF). The V-PCF may use the H-PCF ID provided by the WTRU, or, if preconfigured, may already know which H-PCF serves the WTRU and forward the request accordingly.

[0146] The H-PCF may receive the route selection request from the WTRU, which includes a traffic descriptor. The H-PCF may determine the identity of the VPLMN in which the WTRU is currently registered (e.g., based on the- 22 - 9694042.1IDC-2025P00315WCV-PCF that relayed the message). The H-PCF may consider this VPLMN ID when selecting a suitable route for the WTRU's application traffic.

[0147] Similar to procedure 200, the H-PCF may determine a suitable DNN / S-NSSAI combination for the WTRU traffic. This combination must be compatible with roaming (i.e., usable by the WTRU while registered in the VPLMN). The H-PCF may also determine PDU characteristics and indicate in the message that the selected route is valid while roaming. Additionally, the message may specify a time window during which the route is valid. For instance, the H-PCF may determine that certain high-throughput traffic is better served during nighttime hours in the HPLMN, which could correspond to daytime hours in the VPLMN. In such a case, the message may indicate that the route is valid between 8:00 AM and 6:00 AM VPLMN local time.

[0148] In another example, the message from the H-PCF may specify a preferred access type for the proposed route, such as non-3GPP access or multi-access. For instance, for high-bandwidth traffic, the H-PCF may determine that it is preferable not to overload 3GPP access nodes in the VPLMN with HPLMN-originating traffic, and thus suggest non-3GPP or multi-access alternatives.

[0149] Alternatively, for traffic requiring high reliability and low latency, the H-PCF may determine that 3GPP access is more robust than non-3GPP access. For example, serving roaming UEs over non-3GPP access in the VPLMN may be less reliable or have higher interruption risk compared to 3GPP access.

[0150] The H-PCF may check whether there is an existing PDU session that matches the selected route and is suitable to carry the WTRU traffic. If such a session exists, the H-PCF includes the corresponding PDU session ID in its reply.

[0151] If no existing PDU session matches the selected route, the H-PCF may indicate that a new PDU session needs to be established. The reply may include one or more DNN / S-NSSAI combinations, as well as a mapping between the S-NSSAIs in the HPLMN and their corresponding values in the VPLMN. The message may also include the specific location or region where the route is valid, along with a time window during which the route may be used by the WTRU.

[0152] As described above, in procedure 200 of FIG. 2, WTRU 202 may interact with PCF 212 (e.g., the PCF responsible for serving WTRU policies) to request a specific route for its application traffic. PCF 212 determines a suitable route based on information provided by the WTRU in its request message, as well as data obtained from other network functions. The PCF 212 may then send a response to WTRU 202, indicating the proposed route, along with guidance on whether the WTRU 202 should establish a new PDU session or reuse an existing one. The response may also include route validity parameters.

[0153] In one embodiment, the WTRU and PCF may perform the route selection procedure (as shown in procedure 200) using a DNS protocol, as described below.

[0154] Once WTRU 202 identifies application traffic to be transmitted (e.g., as in step 222) and determines that a route needs to be requested from the network (i.e., from the PCF), it may first derive a traffic descriptor for the application data (as in step 224).- 23 - 9694042.1IDC-2025P00315WQ

[0155] Similar to 226, the WTRU may send a DNS query / request message to the PCF. The message may include a QR field in the header with a value of ‘O', indicating that it is a query. The header may also include an Opcode set to 'QUERY' (e.g., OPCODE = QUERY) to specify that the message is a standard DNS query. Additionally, the message may include a unique transaction ID to correlate responses. The DNS query may contain the traffic descriptor as part of the query data.

[0156] The DNS query / request message may include a value in a QTYPE field. The QTYPE field may be set to a value indicating the type of information being requested. For example, a QTYPE value of DNN may indicate that the WTRU is requesting the DNN value for the desired route. The QTYPE may indicate that a DNN / S-NSSAI combination or a PDU session ID should be returned in the DNS response.

[0157] Upon receiving the DNS query from the WTRU, the PCF may process the request. The PCF may use the QTYPE field to determine the type of information to include in the DNS response. In this interaction, the WTRU acts as the DNS client.

[0158] The PCF may use the traffic descriptor provided by the WTRU in the DNS query, along with a QTYPE field value of "DNN” or "DNN / S-NSSAI,” to determine suitable values for DNN and S-NSSAI to carry the WTRU's application traffic. Based on this information, the PCF may determine that a combination such as DNN-x and S-NSSAI-y is suitable to carry WTRU application traffic. The PCF may perform a DNS lookup procedure either through a local DNS lookup or by querying a DNS server operated by the mobile network.

[0159] If the QTYPE field indicates a request for a "PDU Session ID” or similar, the PCF may also determine whether an existing PDU session for the WTRU can be reused to carry the traffic.

[0160] Similar to 230 and 240, the PCF may send a DNS response message to the WTRU. The response message may include the same ID that was provided by the WTRU in the DNS query message. The message header may include a QR field set to '1,' indicating it is a response message. The response message may contain an "Answer” field specifying information associated with the proposed route. For example, the response at 231 may include a PDU session ID, while the response at 241 may include the DNN-x / S-NSSAI-y combination or a PDU Session Association Identifier for use in session establishment. The PCF may also indicate that an existing PDU session (e.g., PDU Session ID 1) matches the proposed route.

[0161] If no existing PDU session can satisfy the route requirements, the PCF may indicate this by setting the PDU Session ID field to "empty” or "none,” thereby informing the WTRU that it must establish a new PDU session to carry its traffic.

[0162] The DNS response message from the PCF may include the proposed route information within an SRV record, which describes the service endpoint for routing the WTRU's traffic.

[0163] If the PCF determines an existing PDU session (e.g., PDU Session ID1) that can serve the WTRU, then the PCF may include the PDU Session ID1 in the response message to the WTRU. In addition to the DNN / S-NSSAI value and PDU session ID values, the response message may further include attributes related to the validity time of- 24 - 9694042.1IDC-2025P00315WCthe response message or the SRV record. For example, the message may include a TTL value, such as a specific time window (e.g., 8:00 AM to 9:00 AM) or a time duration (e.g., 1 hour).

[0164] The PCF may obtain other SRV record attributes, either locally or via interaction with the operator's DNS server, including a priority value and a weight value. The priority value may indicate the preferred order of SRV records (e.g., preference for one DNN / S-NSSAI combination over another). The weight value may further distinguish SRV records of the same priority, providing relative selection preferences.

[0165] The PCF may use this priority and weight information internally to select a single optimal route, without exposing multiple options to the WTRU. Alternatively, the PCF may include multiple routing options in the DNS response, along with the corresponding priority and weight values. The response may also include location and time constraints indicating where and when the SRV record is valid for use.

[0166] In an alternative deployment, the following may occur: (1) the WTRU may send a DNS request including the FQDN for the requested service; (2) the DNS server may be a DNS server in the mobile network and may have capabilities for communicating with a PCF; (3) the DNS server may communicate with the PCF to obtain information about the route proposed by the PCF; (4) the DNS server may send a DNS response to the WTRU that includes the information about the route proposed by the PCF; and (5) the WTRU may use the information about the route proposed by the PCF to re-use an existing PDU session as described herein.

[0167] When the WTRU sends the traffic descriptor to the PCF, the PCF may decide that the network wants to authenticate and authorize the WTRU application before the PCF replies. The PCF may trigger an AS to perform an EAP-based authentication and authorization procedure with the application. When the AS tells the PCF that the user has (or has not) been authenticated and authorized, the PCF will respond to the WTRU.

[0168] FIG. 3 illustrates a procedure 300 for network-controlled route selection with application authentication and authorization.

[0169] At 320, the WTRU 302 may be triggered to look for a route or route information for certain WTRU traffic. The WTRU may determine a traffic descriptor for the WTRU traffic of interest (similarly to 220 and 222 in FIG. 2).

[0170] At 322, the WTRU 302 may send a message to the PCF 312 to request route information. The message may include the traffic descriptor from 320.

[0171] At 324, the PCF 312 may determine route information for a route that carries WTRU traffic.

[0172] At 326, the PCF 312 may determine, based on the traffic descriptor, subscription information or other local configuration, that application-related authentication and authorization is needed for the application of interest. The PCF 312 may use the application ID, ASP ID and information from other network functions to determine that WTRU authentication and authorization for the application of interest is needed. In one example, the Application ID (e.g., corresponding to a premium game) may be associated with an indication (e.g., such as within the subscription data) that WTRU authentication and authorization are required before WTRU 302 is permitted to exchange traffic for that application. For example, the application ID may refer to a high throughput application, and for example in WTRU- 25 - 9694042.1IDC-2025P00315WCpolicies or WTRU subscription information, applications that require high throughput may need to go through application related authentication and authorization.

[0173] To avoid excessive or redundant authentication messaging with WTRU 302, PCF 312 may first verify whether the WTRU 302 has already been authorized for the relevant application traffic because of a prior procedure. The authentication and authorization result may be associated with traffic of one or more applications (e.g., Application IDs). PCF 312 may check for a previously stored WTRU authentication result either locally or by querying another network function (e.g., UDM, UDR, or WTRU Context Function). For example, if WTRU 302 has already been authorized to send traffic for a particular application, PCF 312 may bypass the authentication and authorization procedure described in steps 328 to 332. If no prior authorization is found, PCF 312 may proceed with the authentication and authorization steps as described below.

[0174] At 328 to 332, an EAP-based authentication and authorization procedure may take place between the WTRU and a certain AAA server (AAA-S). The PCF may mediate the message exchange between the WTRU 302 and AAA-S 314. Alternatively, the PCF 312 may request that other network functions perform the application-related authentication and authorization between the WTRU and AAA-S. Stated differently, PCF 312 may either act as the authenticator toward the AAA-S or delegate the authentication function to a dedicated authenticator network function (NF) that performs the operations on its behalf. In the case where an authenticator NF is used, PCF 312 may receive the final authentication result (e.g., EAP-Success or EAP-Failure) from that NF and subsequently forward the result to WTRU 302.

[0175] At 328, the PCF 312 may request the WTRU User ID for EAP authentication (EAP ID) for the application of interest. This request message from the PCF may be sent to the WTRU using a NAS transport message. The message from the PCF 312 may be sent over an IP connection between the PCF 312 and the WTRU 302. The PCF may include the application ID, and eventually an ASP ID. The message from the PCF may further include information stemming from the route the PCF determined. For example, the message from the PCF may include a S-NSSAI value and potentially a DNN value (route related information).

[0176] At 330, the WTRU 302 provides the EAP ID for the application alongside the application ID, and potentially the S-NSSAI and DNN, in a response message to the PCF. This message from the WTRU 302 may be a NAS transport message or an IP message.

[0177] At 332, the PCF 312 may send a message to the relevant AAA-S 314, forwarding the EAP ID provided by the WTRU 302, and the application ID, and eventually WTRU ID (e.g., GPSI). The message from the PCF 312 to the AAA-S 314 may also include route related information such as a S-NSSAI value and a DNN value. After successful completion of the authentication and authorization procedure, PCF 312 may store the authentication result either locally or via another network function (e.g., UDM or UDR) for use in subsequent authorization checks, as referenced above in 326.

[0178] In case the application related authentication and authorization between the WTRU 302 and the AAA-S 314 is completed successfully, then PCF 312 may further determine if there is a PDU session that is already established for the WTRU 302 that matches the route proposed by the PCF 312.- 26 - 9694042.1IDC-2025P00315WC

[0179] In a first scenario 340, the EAP authentication and authorization is successful. In the first scenario 340, similar to 231 and 232 of FIG, 2, the PCF 312 may send, at 341, a message to the WTRU 302 indicating which PDU session ID to use for the WTRU application traffic, or else, indicate that a new PDU session is needed and provides values DNN-x and S-NSSAI-y for route. PCF 312 may include the authentication result (e.g., EAP-Success or EAP-Failure) in the message. The WTRU 302 may also store the successful EAP authentication and authorization result.

[0180] At 343, the WTRU 302 may perform a PDU session establishment or modification procedure to include the WTRU application traffic and configure the PDU session to carry the application traffic. SMF 310 may verify whether WTRU 302 is authorized to exchange the relevant application traffic by consulting PCF 312 or another NF that stores the associated authentication and authorization result for that application.

[0181] At 345, the WTRU 302 may send uplink application traffic to an AS 316 via a UPF 308.

[0182] In a second scenario 350, the EAP authentication and authorization between the WTRU 302 and the AAA-S 314 fails. Here the PCF 312 may determine that the application traffic is not authorized to be exchanged between the WTRU 302 and the AS 316 using the network. The PCF 312 may also determine that the traffic related to the application of interest should not be exchanged between the WTRU 302 and the AS 316, using the route of interest, with DNN-x and S-NSSAI-y values (that are used for the EAP procedure). At 351, the PCF 312 sends this information to the WTRU 302.

[0183] The WTRU may store this information. The WTRU may use this information to determine to block traffic related to the application ID from being sent. At 353, such traffic may also be blocked by the network (e.g., an anchor UPF from reaching the WTRU 302 and AS 316).

[0184] The PCF 312 may determine that a different route may need to be determined for the WTRU application traffic, for which the authentication and authorization process would succeed.

[0185] Alternatively, the PCF 312 may indicate to the WTRU 302 that no route is available to carry WTRU application traffic with the application ID, until a successful authentication and authorization takes place.

[0186] At 355, the WTRU 302 may determine, either based on suggestions from the network (e.g., the PCF 312) or based on local policies, to carry the WTRU application traffic in a different route, for example, using a default PDU session (lower throughput).

[0187] FIG. 4 illustrates an exemplary procedure 400 performed by a WTRU for network-controlled route selection where no existing PDU session can be used to carry WTRU application data.

[0188] At 402, a WTRU may transmit, to a NF, a request message requesting information for routing WTRU application data. The NF may be a PCF and the request may include a traffic descriptor of the WTRU application data. Furthermore, the request message may be a DNS message.

[0189] At 404, the WTRU may receive, from the NF, a response message indicating that no existing PDU session can be used to carry the WTRU application data. The response message may be a DNS message. The response message may include a PDU session association identifier. The response message may further include a DNN value and / or a S-NSSAI value.- 27 - 9694042.1IDC-2025P00315WC

[0190] At 406, the WTRU may transmit a PDU session establishment request. The PDU establishment request may include the PDU session association identifier. The PDU establishment request may also include the DNN value and / or the S-NSSAI value.

[0191] FIG. 5 illustrates an exemplary procedure 500 performed by a WTRU for network-controlled route selection.

[0192] At 502, a WTRU may transmit, to a NF, a request message requesting information for routing WTRU application data. The NF may be a PCF and the request may include a traffic descriptor of the WTRU application data. Furthermore, the request message may be a DNS message.

[0193] At 504, the WTRU may receive, from the NF, a response message indicating whether the WTRU application data can be routed using one of one or more existing packet data unit (PDU) sessions.

[0194] At 506, on a condition that an existing PDU session can carry the WTRU application data, the WTRU may transmit a PDU session modification request. The response message indicating that the WTRU application data can be routed using an existing PDU session may include a PDU session ID identifying an existing PDU session. The response message indicating that the WTRU application data can be routed using an existing PDU session may also include a DNN value and a S-NSSAI value associated with the existing PDU session. The PDU session modification request may be associated with the identified PDU session and / or the DNN value and S-NSSAI value.

[0195] At 508, on a condition that no existing PDU session can carry the WTRU application data, the WTRU may transmit a PDU session establishment request. The response message indicating that a new PDU session is required may include a PDU session association identifier. The response message indicating that a new PDU session is required may include a DNN value and a S-NSSAI value. The PDU session establishment request may include the PDU session association identifier and / or the DNN value and the S-NSSAI value.

[0196] FIG. 6 illustrates an example procedure 600 performed by a NF for network-controlled route selection. The NF may be, for example, a PCF.

[0197] At 602, an NF may receive, from a WTRU, a request message requesting information for transmitting application data. The NF may be a PCF. The request message may include a traffic descriptor of the WTRU application data.

[0198] At 604, the NF may determine a DNN value and a S-NSSAI value for a route to carry the application data.

[0199] At 606, the NF may determine whether the DNN value and the S-NSSAI value correspond to an existing PDU session.

[0200] At 608, on a condition that the DNN value and S-NSSAI value correspond to an existing PDU session, when transmitting a response message to the WTRU, the NF may instruct the WTRU to use the existing PDU session. The response message indicating that the existing PDU session is to be used may include a PDU session identifier identifying the existing PDU session. The response message indicating that the existing PDU session is to be used may include a DNN value and a S-NSSAI value.

[0201] At 610, on a condition that the DNN value and S-NSSAI value do not correspond to an existing PDU session, when transmitting a response message to the WTRU, the NF may instruct the WTRU to establish a new PDU session.- 28 - 9694042.1The response message indicating that a new PDU session is to be established may include a PDU session association identifier.

[0202] 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 UE, WTRU, terminal, base station, RNC, or any host computer.- 29 - 9694042.1

Claims

CLAIMSWhat is Claimed:

1. A method performed by a wireless transmit / receive unit (WTRU), the method comprising:transmitting, to a network function (NF), a request message requesting information for routing WTRU application data;receiving, from the NF, a response message indicating that no existing packet data unit (PDU) session can be used to carry the WTRU application data; andtransmitting a PDU session establishment request.

2. The method of claim 1 , wherein the network function is a policy control function (PCF).

3. The method of any one of claims 1 or 2, wherein the request message includes a traffic descriptor of the WTRU application data.

4. The method of any one of claims 1 , 2, or 3, wherein the response message indicating that a new PDU session is required includes a PDU session association identifier, and wherein the PDU session establishment request includes the PDU session association identifier.

5. The method of any one of claims 1, 2, 3, or 4, wherein the response message indicating that a new PDU session is required includes a data network name (DNN) value and a single network slice selection assistance information (S-NSSAI) value, and wherein the PDU session establishment request includes the DNN value and the S-NSSAI value.

6. The method of any one of claims 1, 2, 3, 4, or 5, wherein the request message is a domain name system (DNS) message.

7. The method of any one of claims 1 , 2, 3, 4, 5, or 6, wherein the response message is a domain name system (DNS) message.

8. A wireless transmit / receive unit (WTRU) comprising:a transceiver; anda processor;wherein the transceiver and processor are configured to:transmit, to a network function (NF), a request message requesting information for routing WTRU application data;receive, from the NF, a response message indicating whether the WTRU application data can be routed using one or one or more existing packet data unit (PDU) sessions;on a condition that an existing PDU session can be used to carry the WTRU application data, transmit a PDU session modification request; and- 30 - 9694042.1on a condition that no existing PDU session can be used to carry the WTRU application data, transmit a PDU session establishment request.

9. The WTRU of claim 8, wherein the network function is a policy control function (PCF).

10. The WTRU of any one of claims 8 or 9, wherein the request message includes a traffic descriptor of the WTRU application data.

11. The WTRU of any one of claims 8, 9, or 10, wherein the response message indicating that the WTRU application data can be routed using the existing PDU session includes a PDU session identifier identifying an existing PDU session, and wherein the PDU session modification request is associated with the identified existing PDU session.

12. The WTRU of any one of claims 8, 9, 10, or 11, wherein the response message indicating that the existing PDU session can be used includes a data network name (DNN) value and a single network slice selection assistance information (S-NSSAI) value associated with the existing PDU session and wherein the PDU session modification request is associated with the DNN value and S-NSSAI value.

13. The WTRU of any one of claims 8, 9, 10, 11, or 12, wherein the response message indicating that a new PDU session is required includes a data network name (DNN) value and a single network slice selection assistance information (S-NSSAI) value, and wherein the PDU session establishment request includes the DNN value and the S-NSSAI value.

14. The WTRU of any one of claims 8, 9, 10, 11, 12, or 13, wherein the response message indicating that a new PDU session is required includes a PDU session association identifier, and wherein the PDU session establishment request includes the PDU session association identifier.

15. The WTRU of any one of claims 8, 9, 10, 11, 12, 13, or 14, wherein the request message is a domain name system (DNS) message.

16. A network function (NF) configured to:receive, from a wireless transmit / receive unit (WTRU), a request message requesting information for routing WTRU application data;determine a data network name (DNN) value and a single network slice selection assistance information (S-NSSAI) value for a route to carry the application data;determine whether the DNN value and the S-NSSAI value correspond to one of one or more existing packet data unit (PDU) sessions;on a condition that the DNN value and S-NSSAI value correspond to an existing PDU session, transmit a response message to the WTRU, indicating the WTRU to use the existing PDU session; and- 31 - 9694042.1on a condition that the DNN value and S-NSSAI value do not correspond to an existing PDU session, transmit a response message to the WTRU, indicating the WTRU to establish a new PDU session.

17. The NF of claim 16, wherein the request message includes a traffic descriptor of the WTRU application data.

18. The NF of any one of claims 16 or 17, wherein the response message indicating that the existing PDU session is to be used includes a PDU session identifier (ID) identifying to the existing PDU session.

19. The NF of any one of claims 16, 17, or 18, wherein the response message indicating that a new PDU session is to be establish includes a data network name (DNN) value and a single network slice selection assistance information (S-NSSAI) value.

20. The NF of any one of claims 16, 17, 18, or 19, wherein the response message indicating that a new PDU session is to be established includes a PDU session association identifier.- 32 - 9694042.1