Simplified architecture for 6g based on user-plane tunnels
The simplified 6G network architecture addresses UP session challenges by configuring WTRUs to use enhanced UP functions and QoS treatment for efficient packet handling, improving data transmission quality in 6G networks.
Patent Information
- Application Number
- PCT/US2026/026085
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-04-30
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face challenges in efficiently establishing and managing user plane (UP) sessions for wireless transmit/receive units (WTRUs) connecting to data networks, particularly in the context of evolving 6G networks, where efficient QoS treatment and packet marking are crucial for optimal data transmission.
A simplified architecture for 6G networks is introduced, where WTRUs receive router advertisement messages to configure IP addresses, select enhanced UP functions, and send IP packets with marking descriptors based on quality of service (QoS) treatment, enabling efficient UP session establishment and operation.
This approach enhances the efficiency and effectiveness of UP sessions by optimizing packet handling and QoS treatment, ensuring reliable and high-quality data transmission in 6G networks.
Smart Images

Figure US2026026085_12112026_PF_FP_ABST
Abstract
Description
IDC-2025P00305WQSIMPLIFIED ARCHITECTURE FOR 6G BASED ON USER-PLANE TUNNELSCROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of U.S. Non-Provisional Application No. 19 / 202,572, filed May 8, 2025, the contents of which are incorporated herein by reference.BACKGROUND
[0002] A mobile network may provide wireless transmit / receive units (WTRUs) (e.g., user equipments (UEs)) with data connectivity toward a data network (DN). The DN may be identified by a Data Network Name (DNN). Examples of a DN may include the Internet (e.g., identified by a DNN "internet”), an operator specific data network for Internet protocol (IP) multimedia subsystem (IMS), a local enterprise, and / or an industrial network.
[0003] A WTRU that wants to connect to a DN may request the establishment of a protocol data unit (PDU) session and may provide a requested DNN to indicate which DN to connect to, as well as other PDU session parameters. A PDU session enables the transport of PDUs between the WTRU and the DN, and this connection is part of the user plane (UP) of the mobile network. The type of PDU may depend on the type of PDU session, and may for example include IP packets with a PDU session of type "IPv4v6”, Ethernet frames ("Ethernet” type), IPv4 packets ("IPv4” type), IPv6 packets ("IPv6” type), and / or any PDUs with a PDU session of type "Unstructured”.SUMMARY
[0004] Procedures for network registration, proxy information discovery, and PDU session establishment and operation are disclosed herein. A wireless transmit / receive unit (WTRU) may receive, from a first network node including an access router (AR), a router advertisement message. The WTRU may configure, based on the received router advertisement message, a service Internet protocol (IP) address of the WTRU. The WTRU may receive, from a second network node, policy information including proxy information describing proxies that can be used to establish a protocol data unit (PDU) session. The WTRU may select an enhanced user plane function (eUPF) based on the proxy information. The WTRU may send, to a third network node including the selected eUPF, a Hypertext Transfer Protocol (HTTP) connect request message to create a connect stream, wherein the HTTP connect request message is a user plane (UP) message including PDU session parameters and the service IP address of the WTRU as a source IP address. The WTRU may receive, from the third network node including the selected eUPF, an HTTP response message indicating creation of the connect stream, wherein the HTTP response message includes a first marking descriptor indicating how to mark packets of the connect stream. The WTRU may generate an IP packet including an uplink (UL) PDU over the connect stream, wherein the IP packet has a marking based on the first marking descriptor. The WTRU may send, to a base station, the IP packet using a quality of service (QoS) treatment based on the IP packet marking.IDC-2025P00305WGBRIEF DESCRIPTION OF THE DRAWINGS
[0005] 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:
[0006] FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;
[0007] 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;
[0008] 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;
[0009] 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;
[0010] FIG. 2 is a system diagram illustrating an example simplified sixth generation (6G) architecture based on user plane (UP) tunnels;
[0011] FIG. 3 shows an example protocol stack for systems where the access router (AR) includes an Internet protocol (IP( router functionality;
[0012] FIG. 4 shows an example protocol stack for systems where the AR does not include an IP router functionality, or where the IP router functionality of the AR is not activated;
[0013] FIG. 5 is a flow diagram illustrating an example UP connectivity establishment and operation procedure in a simplified architecture for 6G based on UP tunnels;
[0014] FIG. 6 is a flow diagram illustrating an example registration procedure for a WTRU to register to the network and establish a 6G PDU session (6PS) session (part 1 of 2);
[0015] FIG. 7 is a flow diagram illustrating an example registration procedure for a WTRU to register to the network and establish a 6PS session (part 2 of 2);
[0016] FIG. 8 is a flow diagram illustrating an example configuration procedure for the network to configure the WTRU with service IP address and proxy information; and
[0017] FIG. 9 is a flow diagram illustrating an example procedure performed by a WTRU for network registration, proxy information discovery, and PDU session establishment and operation.DETAILED DESCRIPTION
[0018] 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 accessIDC-2025P00305WGmethods, 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.
[0019] 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-Fl 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.
[0020] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or the other networks 112. By way of example, the base stations 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.
[0021] 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 provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 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.IDC-2025P00305WC
[0022] 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).
[0023] 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).
[0024] 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).
[0025] 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.
[0026] 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).
[0027] 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.
[0028] 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 such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a 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 CN 106.IDC-2025P00305WC
[0029] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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 theIDC-2025P00305WGtransceiver 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.
[0034] 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.
[0035] 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.
[0036] 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.
[0037] 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).
[0038] 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 for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
[0039] 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 thesignals 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.
[0040] 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.
[0041] 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)).
[0042] 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.
[0043] 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.
[0044] 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. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
[0045] The ON 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 partIDC-2025P00305WGof 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.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] 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.
[0050] 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.
[0051] In representative embodiments, the other network 112 may be a WLAN.
[0052] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use anIDC-2025P00305WC802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc” mode of communication.
[0053] 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.
[0054] 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.
[0055] 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).
[0056] 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 including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
[0057] 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 otherIDC-2025P00305WCSTAs 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.
[0058] 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.
[0059] 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.
[0060] 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).
[0061] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and / or lasting varying lengths of absolute time).
[0062] 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 DCIDC-2025P00305WQprinciples 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.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] 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.
[0067] 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,IDC-2025P00305WQsupporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.
[0068] 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.
[0069] 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.
[0070] 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.
[0071] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.
[0072] The following abbreviations and acronyms may be used herein:
[0073] 5GS 5G System
[0074] 5QI 5G QoS Identifier
[0075] 6PS 6G PDU Session (also called 6PS session)
[0076] 6QS 6G QoS Service (also called "6QS service)
[0077] 6QI 6G QoS Identifier (equivalent to the 5QI but in the context of a 6G system)
[0078] AF Application FunctionIDC-2025P00305WC
[0079] AN Access Network
[0080] AR Access Router
[0081] AS Application Server
[0082] CP Control Plane
[0083] DHCP Dynamic Host Configuration Protocol
[0084] DL Downlink
[0085] DN Data Network
[0086] DNN Data Network Name
[0087] DNS Domain Name System
[0088] DSCP Differentiated Services Code Point
[0089] eUPF enhanced UPF
[0090] eSMF enhanced SMF
[0091] ePCF enhanced PCF
[0092] FQDN Fully Qualified Domain Name
[0093] HTTP Hypertext Transfer Protocol
[0094] ID Identifier
[0095] IE Information Element
[0096] IP Internet Protocol (IPv4: IP version 4, IPv6: IP version 6)
[0097] N4 Interface defined by 3GPP between UPF and SMF
[0098] N6 Interface defined by 3GPP between UPF and DN
[0099] NAS Non-Access Stratum
[0100] NEF Network Exposure Function
[0101] NF Network Function
[0102] CAM Operation, Administration and Management
[0103] PCF Policy Control Function
[0104] PDB Packet Delay Budget
[0105] PDU Protocol Data Unit
[0106] PER Packet Error Rate
[0107] PMF Performance Measurement Functionality
[0108] PSA UPF PDU Session Anchor UPF
[0109] PSDB PDU Set Delay BudgetIDC-2025P00305WQ
[0110] PSER PDU Set Error Rate
[0111] PvD Provisioning Domain
[0112] QoS Quality of Service
[0113] RAN Radio Access Network
[0114] SBI Service Based Interface
[0115] SDF Service Data Flow
[0116] SLAAC IPv6 Stateless Address Auto-configuration
[0117] SMF Session Management Function
[0118] S-NSSAI Single Network Slice Selection Assistance Information
[0119] UDP User Datagram Protocol
[0120] WTRU User Equipment
[0121] UL Uplink
[0122] UP User Plane
[0123] UPF User Plane Function
[0124] URL Universal Resource Locator
[0125] URI Universal Resource Identifier
[0126] URSP UE Route Selection Policy
[0127] The term RAN node may be used herein to represent any RAN node such as a gNodeB, eNodeB or any new generation NodeB, and more generally a base station. The term Information Element (IE) may be used herein to represent one or more parameters. An IE may be made up of one or more other lEs. The term "eUPF” may be used herein to designate an enhanced PSA UPF or an intermediate enhanced UPF (and may be used interchangeably with UPF). In an example, an SDF is or includes a data flow (e.g., 5-tuple composed of a transport protocol, source and destination IP addresses and ports) that is subject to specific quality of service and policy control rules. All enhanced interfaces and functions described herein using a prefix “e” (e.g., such as eSMF) or suffix “+” (e.g., such as N4+), designate an interface or function that is based on an existing interface or function, and includes enhancements to support the methods and procedures defined herein, including to support a 6PS based on user plane tunnels and to support a RAN and WTRU including a QoS function based on IP packet marking. The prefix “e” may be omitted interchangeably. The expressions "configuring a 6G QoS service” and "activating a 6G QoS service” are used interchangeably herein, to designate the configuration of a 6G QoS service in the RAN node and WTRU.
[0128] A mobile network may provide wireless transmit / receive units (WTRUs) (e.g., user equipments (UEs)) with data connectivity toward a data network (DN). The DN may be identified by a Data Network Name (DNN). Examples of a DN may include the Internet (e.g., identified by a DNN "internet”), an operator specific data network for Internet protocol (IP) multimedia subsystem (IMS), a local enterprise, and / or an industrial network.IDC-2025P00305WQ
[0129] A WTRU that wants to connect to a DN may request the establishment of a protocol data unit (PDU) session and may provide a requested DNN to indicate which DN to connect to, as well as other PDU session parameters. A PDU session enables the transport of PDUs between the WTRU and the DN, and this connection is part of the user plane (UP) of the mobile network. The type of PDU may depend on the type of PDU session, and may for example include IP packets with a PDU session of type "IPv4v6”, Ethernet frames ("Ethernet” type), IPv4 packets ("IPv4” type), IPv6 packets ("IPv6” type), and / or any PDUs with a PDU session of type "Unstructured”.
[0130] In an example PDU session establishment procedure, a WTRU may send a PDU session establishment request to the SMF, through the RAN node and the AMF, which selects the SMF based on the requested DNN and S-NSSAI. The WTRU may send the request when the WTRU determines that the WTRU needs connectivity (e.g., when a WTRU application opens a network socket), however the network may also trigger the WTRU to send the request. The WTRU may send the request over a 3GPP access node (e.g. gNodeB, eNodeB, base station) or over a non-3GPP access node (e.g., WLAN access node). The request may include a request type (e.g., initial or existing), PDU session ID, requested PDU session type, requested SSC mode, requested DNN, S-NSSAI, and other parameters.
[0131] The SMF may retrieve, from the UDM, subscription data related to session management. Secondary authentication between the WTRU and an authentication server may occur. The SMF selects a PCF, initiates the establishment of an SM policy session and retrieves, from the PCF, an initial set of PCC rules applicable to the session. The SMF may select an IP address for the WTRU and may establish an N4 session with the UPF. The SMF may send a message including a PDU session establishment accept message to the WTRU (including selected PDU session type, selected SSC mode, authorized QoS rules, IP address, session UL and DL AMBR), as well as PDU Session information for the RAN node (including GTP-U tunnel endpoint information and QoS information). The SMF may send the message, through the AMF, towards the RAN node, which forwards the PDU session establishment accept message to the WTRU.
[0132] Upon receiving the message, the RAN and WTRU may configure the requested resources and reply to the SMF through the AMF. The reply may include the RAN GTP-U tunnel endpoint information. Upon receiving the reply, the SMF may configure the UPF, including with the RAN GTP-U tunnel endpoint information. The configuration of the UPF results in the UP connection being established between the WTRU and DN, such that PDUs may be transported over a GTP-U tunnel between the RAN node and the UPF. The SMF may send a message to the UDM, to register itself as the serving SMF for this PDU session ID.
[0133] The Multiplexed Application Substrate over Quick UDP Internet Connections (QUIC) Encryption (MASQUE) is a set of protocols and extensions to HTTP that allow proxying traffic flows over an HTTP connection (e.g., over an HTTP / 3 over QUIC connection). A MASQUE proxy may be used to proxy UDP, IP, Ethernet or TCP traffic. For example, a MASQUE proxy relays the PDU (e.g., UDP, IP, Ethernet, or TCP) traffic between a MASQUE client and a remote endpoint, by, on the client side of the proxy, tunneling the traffic PDUs (or PDU payloads) between the client and the proxy and, on the remote endpoint side of the proxy, forwarding the traffic PDUs to and from the remote endpoint (e.g., over UDP, IP, Ethernet or TCP).IDC-2025P00305WQ
[0134] To establish a MASQUE connection (also referred to as a MASQUE tunnel), the client first establishes an HTTP (e.g., HTTP / 3 over QUIC) connection with the MASQUE proxy. On a stream of the HTTP connection, the client sends an HTTP CONNECT request to the proxy, which is an HTTP request including a method field with the value "CONNECT,” a protocol field with a value corresponding to the protocol to proxy, for example "connect-udp,” "connect-ip”, "connect-ethernet” or "connect-tcp.” The proxy sends, to the client, an HTTP response to indicate that the CONNECT request is accepted or rejected. Once the request is accepted, the MASQUE proxy can forward the protocol PDUs (e.g., IP packets or Ethernet frames) or PDU payloads (e.g., UDP or TCP payload) in an HTTP datagram, between the client and the proxy, over the stream used to send the CONNECT request. This stream is referred to herein as the "CONNECT stream”. The MASQUE proxy forwards PDUs between the CONNECT stream and the remote endpoint. If necessary (e.g., for UDP and TCP), the MASQUE proxy adds a protocol header to the payload and forwards the resulting packet to the remote endpoint, and in the other direction, the MASQUE proxy removes the protocol header and forwards the payload to the client.
[0135] Since the connection between the MASQUE client and the MASQUE proxy is an HTTP connection, it is possible for the client and proxy to exchange HTTP traffic on some streams, while exchanging proxied traffic on one or more CONNECT streams. Multiple CONNECT streams can be established in a same HTTP connection (e.g., to tunnel traffic of distinct types and / or to different destination endpoints).
[0136] MASQUE-based protocols may be derived from MASQUE, by using new HTTP headers to use in HTTP CONNECT, new capsule messages and / or new header fields in HTTP datagrams. Furthermore, since the communication between MASQUE client and proxy is based on HTTP, MASQUE-based protocols may be derived from MASQUE by using HTTP messages such as HTTP GET or HTTP POST, between the MASQUE client and proxy, possibly within the same HTTP connection used for the HTTP CONNECT. MASQUE-based protocols (MASQUE-P and MASQUE-U) are described herein. MASQUE-P may refer to MASQUE-PDU session (i.e., a MASQUE-based protocol enhanced to support establishing and operating 6G PDU sessions), and MASQUE-U may refer to MASQUE-User Plane session (i.e., a MASQUE-based protocol enhanced to support establishing and operating a tunnel between a RAN node and a eUPF, for transporting User Plane traffic and related lEs).
[0137] Regarding protocols for IP routers, an IPv6 router may send IPv6 Router Advertisements to inform hosts connected to the router over a layer-2 link (e.g., Ethernet) about the presence of the router. The Router Advertisement may include information enabling hosts to configure an IPv6 address, for example using IPv6 Stateless Address Autoconfiguration (SLAAC). DHCP is an alternative protocol that may be used to provide, to hosts on the link, information to configure an IP address. An IPv6 router may include Provisioning Domain (PvD) identifiers in a Router Advertisement, which may enable a host to retrieve PvD information from the network. PvDs are sets of network configuration information, which may for example be used to describe proxies reachable through the IPv6 router.
[0138] Existing mobile networks (e.g., 5G) may be limited due to complex, excessive or redundant CP signaling, exposure of unnecessary information to the WTRU, and limited ability to exchange control User Plane information with the UPF. In a 5G network, establishing a PDU session may involve both reserving resources in the CN (e.g., for routing to / from the appropriate DN) and in the RAN (e.g., to provide the appropriate QoS). While this provides a very granular control over individual flows, it couples UPF and RAN resource management, which leads to complex controlIDC-2025P00305WQmessages with many lEs of different nature. This coupling makes the system design difficult to evolve over time. For example, it is difficult for applications to dynamically adapt the QoS treatment based on application logic, because the QoS rules (in the WTRU) and QoS profiles (in the RAN node) need to be adapted dynamically for the flow. For example, such a dynamic adaptation may require coordinating changes across multiple entities, such as the PCF, SMF, and UPF, which may be a complex process. In another example, adding an SDF to a PDU session may require the WTRU to send a CP PDU session modification message (e.g., to add a new traffic filter), which may unnecessarily increase CN network load.
[0139] In a5G network, the WTRU must be aware of the network slice ID (e.g., S-NSSAI) associated with a network service. However, exposing the network slice ID to the WTRU may be add unnecessary complexity, since what matters is that the network service is made available to the WTRU.
[0140] In a 5G network, there is no general mechanism for the WTRU, or for a WTRU application, to exchange control information with the UPF. As a result, any updates triggered by changes in the WTRU's operational state or network conditions must be initiated via the CP. For instance, even if the frame rate of a video application changes, reconfiguration must be performed through the CP, as direct communication between the WTRU and the UPF is not supported. While the PMF protocol has been developed to enable a specific type of control information to be exchanged (e.g., measurements), PMF was not designed for a more general purpose. For example, there is no prior mechanism to exchange between the WTRU and UPF, information such as rate recommendation or UL / DL media related information, which may be useful for future extension of XR traffic support in new use cases (e.g., UL XR traffic towards another WTRU, or for DL XR traffic relayed through the WTRU). In a 5G network, the WTRU, and WTRU applications, do not have a user plane interface to CN functions, which limits the opportunity for system designers to develop new WTRU functionalities.
[0141] Thus, there is an opportunity to address the mobile network limitations identified above, by designing a 6G system for establishing and operating WTRU connectivity, to address the following requirements or needs. As an example need, the 6G system should decouple RAN resource reservation from CN resource reservation mechanisms (e.g., to reduce system complexity), while maintaining policy control. The 6G system should reduce CP signaling and instead leverage existing Internet and transport layer protocols to perform some operations over the user plane. The 6G system should enable WTRUs (e.g., WTRU applications) to dynamically adapt the QoS treatment of an SDF, based on application logic, with limited impact on CP signaling. As another example need, the 6G system should provide a user plane mechanism to connect network slices to the WTRU without exposing network slice identities (e.g., S-NSSAI) to the WTRU. As another example need, the 6G system should enable the WTRU (and / or a WTRU application) and UPF to exchange control messages and per-PDU metadata over the user plane. As another example need, the 6G system should enable the WTRU to use a Service-Based Interface (SBI) to communicate with CN nodes over the user plane. Furthermore, in relation to the last two example needs, a solution should enable a WTRU application (e.g., a user-space WTRU software component) to communicate with CN nodes, which may facilitate the development of new services. Solutions to address this needs are described herein.
[0142] Embodiments described herein describe in an example a simplified user-plane architecture for 6G, based on user plane IP-based tunnels to address issues such as complex, excessive, or redundant CP signaling. In thisIDC-2025P00305WQarchitecture, a 6G PDU session may be a PDU session over a WTRU-UPF tunnel based on the MASQUE protocol. IP packets of the MASQUE tunnel may be marked by the WTRU and UPF. The network may configure a 6G QoS service in the RAN node and WTRU. The 6G QoS service may be applied by the RAN node and WTRU, based on the IP packets marking. The RAN node may include an IP router functionality, which enables the WTRU to configure a service IP address to initiate the WTRU-UPF tunnel. The WTRU may receive proxy information from the network, to enable the WTRU to establish the WTRU-UPF tunnel. A 6G PDU session may be used for CP messages over the UP, through an eUPF connected to the CN.
[0143] An example procedure for a WTRU to register to the network and request resources for a flow is described herein. The WTRU may register with the network by performing the following steps 1-5. In step 1, the WTRU may send a registration message to the network. The registration message may include capabilities such as: support for IP connectivity from AR, support for proxy information discovery from AR, support for UP tunnel (e.g., for the MASQUE-P protocol between WTRU and eUPF), support for CP messages over UP. As part of configuring a 6G QoS service, steps 2-4 (described in the following) may occur at least once, here after step 1, and / or after step 8. Steps 2-4 may be omitted after step 1 if there is no default 6G QoS service. Steps 2-4 may be omitted after step 8 if the 6G QoS service for the SDF is already configured.
[0144] In step 2, the WTRU may receive a QoS service configuration request message, including QoS information (e.g., QoS rules) and marking filter I E(s). The QoS service configuration request message may include information to configure a Data Radio Bearer, for example in an RRCReconfiguration message IE. The QoS service configuration request message may be received from a RAN node (e.g., from a CN node through the RAN node). The QoS service configuration procedure (steps 2-3-4) may occur before the establishment of the 6PS session (steps 8-9). For example, if the QoS service was established because it is a default QoS service, or because it is required by another 6PS session. The service configuration procedure may occur before the WTRU obtains a service IP address from the AR.
[0145] In step 3, the WTRU may configure a QoS treatment (e.g., where a QoS treatment may include a Data Radio Bearer) based on the request message and configures, based on the marking filter IE(s), packet filter(s) which are associated with the QoS treatment. The WTRU may be configured to transmit PDUs that match a packet filter through the Data Radio Bearer associated with the packet filter. IP packet marking may correspond to the marking of the outer IP packet that includes the PDU. In step 4, the WTRU may send a QoS service configuration response indicating the success of the configuration operation. In step 5, in a system where the AR includes an IP-router functionality, after step 4 the WTRU may receive a message from the AR (e.g., Router Advertisement). Based on the message from the AR, the WTRU may configure the service IP address (which is used in other steps). The AR may transmit the Router Advertisement message to the WTRU, over a 6QS session established in steps 2-3-4 (e.g., over a Data Ratio Bearer of this 6QS session).
[0146] The WTRU may discover proxy information by performing step 6. In step 6, The WTRU may receive, from the network, policy information including marking generation descriptors, which describe how to mark IP packets of the 6PS session, and / or proxy information, which describe proxies that may be used to establish a 6PS session. The proxy information may include lEs that characterize the 6PS session provided through this proxy, (e.g., including a CP-over-UP indication and / or Traffic Steering Policies). There may be multiple ways to receive marking descriptor(s)and proxy information. The proxy information may be obtained, for example from ePCF, eSMF, eUPF, or AR. The marking descriptor(s) may be obtained (e.g., in policy rules from ePCF or eSMF), in 6PS response messages from eUPF or eSMF, or in response message to the CONNECT request from the eUPF (as described in FIGs. 6 and 7). The messages including marking descriptor(s), and / or proxy information may be referred to as "policy information" herein.
[0147] The WTRU may establish a 6G PDU session in steps 7-12. In step 7, the WTRU may receive a trigger to request resources for a new SDF. In step 8, based on information from previous steps, the WTRU may determine connectivity information, including one or more of: proxy information, WTRU service IP address, existing MASQUE-P connection if applicable, CONNECT protocol, and / or marking descriptor. The WTRU may identify the eUPF based on the determined proxy information. The determination may be in part based on an eURSP rule that matches the SDF, which in some systems may include proxy information and / or marking descriptor. In systems where the eURSP rules include proxy information, the WTRU may identify the eUPF based on the proxy information included in the eURSP rule selected for the SDF. In systems where the eURSP rules do not include proxy information, the WTRU may identify the eUPF based on the desired characteristics of the connection, such as DNN and SSC mode, which may be learned from the selected eURSP rule, and which may be matched with lEs within the proxy information obtained through other means (e.g., in PvDs).
[0148] In step 9, the WTRU may send, to the identified eUPF, a 6PS request message including 6PS parameters, where the eUPF is identified based on the proxy information, and where the 6PS request message is a UP message using a WTRU service IP address as source IP address. If the 6G QoS service(s) used by this SDF are not configured yet, the WTRU may be configured as in steps 2-3-4. In an example, the message sent by WTRU in step 9 may be an HTTP CONNECT message, including 6PS parameters. In this case, step 10 may indicate the creation of the CONNECT stream and steps 11-12 may not needed, unless for example to request a second CONNECT stream for a second SDF. In some cases, a WTRU application may send the 6PS request message (i.e., the endpoint of the 6PS session on the WTRU may be a WTRU application, in some cases).
[0149] In step 10, the WTRU may receive a 6PS response message. The response message may include a marking descriptor, which indicates how to mark packets of the MASQUE-P session. In step 11, the WTRU may send an HTTP CONNECT request, including 6PS parameters, to the eUPF, to create a CONNECT stream. In some cases, a WTRU application may send the HTTP CONNECT request (i.e., the endpoint of the 6PS session on the WTRU may be a WTRU application, in some cases). In step 12, the WTRU may receive an HTTP response indicating the creation of the CONNECT stream. The response message may include a marking descriptor, which indicates how to mark packets of the CONNECT stream.
[0150] The WTRU may operate the 6G PDU session in step 13-15. In step 13, the WTRU may receive (e.g., from a WTRU application or device such as a Personal loT Network Element connected to the WTRU or a software component on the WTRU), an IP packet including a UL PDU over the CONNECT stream. In addition to step 13 or as an alternative step 13, the WTRU may send an IP packet including a UL PDU over the CONNECT stream, and the WTRU may mark the IP packet, based on the marking descriptor. In this case, the UL PDU may be provided by an endpoint of the SDF, which may be for example a WTRU application, by a software component on the WTRU, or byIDC-2025P00305WQan external device connected to the WTRU such as over a wireless link such as a Bluetooth link. The marking descriptor may be the marking descriptor in the response to the CONNECT request, if provided, or the marking descriptor in the 6PS response message, if provided, or the marking descriptor in a policy rule (e.g., the eURSP rule selected for the SDF. In step 14, the WTRU may transmit the IP packet to the RAN node, and may apply a QoS treatment to the IP packet, based on the IP packet marking (e.g., the WTRU may transmit the IP packet over a Data Radio Bearer (DRB) associated with the IP packet marking). In step 15, the WTRU may receive a DL PDU over the CONNECT stream. The WTRU may provide the DL PDU to the endpoint of the SDF (e.g., to the WTRU application, software component on the WTRU, or external device).
[0151] In addition to the above step, in some systems where the AR includes an IP-router functionality, the WTRU may obtain proxy information based on the message from the AR (e.g., the WTRU may obtain proxy information using a PvD ID in the message from the AR). In cases where the trigger to request resources for the new SDF is a CP-over-UP message, the WTRU may identify an eUPF based on a subset of the proxy information corresponding to proxies that are indicated as supporting sending control plane messages over the UP (i.e., CP-over-UP), and / or the WTRU may add in the 6PS establishment request, an indication that the 6PS is for CP-over-UP. In this case, the messages in steps 13 to15 may be CP messages over UP, sent to and received from a CN node.
[0152] An example procedure for RAN node operation for configuration and operation of a 6QS service is described herein. A RAN node may configured the 6QS service by performing the following steps 1-5. In step 1, the AR may receive, from the eUPF, a QoS service configuration request message including QoS information (e.g., QoS profiles and QoS rules) and marking filter lEs. In step 2, the AR may configure one or more Data Radio Bearers based on the QoS profiles, and the AR may configure itself to enable PDUs to receive the QoS treatment (e.g., to be transmitted over one of the configured Data Radio Bearers) based on IP packet marking described by the marking filter IE(s). IP packet marking may correspond to the marking of the outer IP packet that includes the PDU. In step 3, the AR may send a QoS service configuration request message to the WTRU, including QoS information (e.g., QoS rules and information to configure the Data Radio Bearers on the WTRU) and marking filter lEs. In step 4, the AR may receive the QoS service configuration response from the WTRU. In step 5, the AR may send, to the eUPF, the QoS service configuration response.
[0153] The RAN node may operate the 6QS service by performing the following steps 6-8. In step 6, the AR may receive a DL IP packet including a DL PDU, where the DL IP packet includes a marking. In step 7, the AR may apply the QoS treatment to the DL IP packet including a DL PDU, based on the marking (e.g., the AR transmits the DL IP packet over a Data Radio Bearer indicated by the marking). In step 8, the AR may send the DL IP packet including a DL PDU to the WTRU.
[0154] An example procedure for an ePCF to configure a 6QS service is described herein. In step 1, the ePCF may be an ePCF for the WTRU or an ePCF for a 6PS session. The ePCF may receive a trigger, such as a policy control request message (e.g., from AMF or eSMF). The request message may identify a WTRU that is registering with the network, or the request message may identify an SDF that a WTRU requests service for. In step 2, he ePCF may identify 6QS services that are required for the WTRU or for the SDF, and the ePCF determines marking filter lEs corresponding to each 6QS service. For example, the ePCF may retrieve default 6QS service(s) for the WTRU or theIDC-2025P00305WQePCF may identify 6QS service(s) for the SDF based on PCC rules. In step 3, the ePCF may send a QoS service configuration request message to the WTRU through the RAN node. The request message may include QoS information (QoS profile, QoS rules) and / or marking filter IPs. In step 4, the ePCF may receive a 6QS service configuration response message, which indicates the success of the 6QS service configuration operation. In step 5, if the policy control request message (step 1) identified an SDF, the ePCF may determine a marking descriptor corresponding to the SDF (e.g., from PCC rules). In step 6, the ePCF may send a policy control response message (e.g., to AMF or eSMF), including a marking descriptor if the policy control request message (step 1 ) identified an SDF.
[0155] An example procedure for an eUPF to establish a 6PS session based on a WTRU request and obtains configuration information from the eSMF is described herein. In step 1, the eUPF may receive a 6PS request message from the WTRU, including 6PS parameters. In step 2, the eUPF may select an eSMF for the session (e.g., by providing 6PS parameters to the NRF and receiving an eSMF from NRF). In step 3, the eUPF may send an N4 session request message to the eSMF, including 6PS parameters. In step 4, the eUPF may receive an N4 session response from the eSMF, including a marking descriptor and traffic handling rules. The response may include an end-to-end IP address.
[0156] In step 5, the eUPF may send a 6PS response message to the WTRU, including a marking descriptor. The response may include an end-to-end IP address. In step 6, the eUPF may receive, from the WTRU, an HTTP CONNECT message, which may include 6PS parameters. The eUPF may send an N4 session request message to the eSMF, including 6PS parameters. The eUPF may receive an N4 session response from the eSMF, including a marking descriptor, and which may also include an end-to-end IP address. In step 7, the eUPF may send, to the WTRU, an HTTP response message, which may include a marking descriptor. The response may include an end-to-end IP address. In step 8, the eUPF may receive a UL PDU over the CONNECT stream, and may forward it towards the PDU destination endpoint (e.g., host in DN or CN node in CN). In step 9, the eUPF may receive a DL PDU from the endpoint, and may forward the DL PDU over the CONNECT stream, while marking the outer IP header of the packet holding the PDU, based on the marking descriptor.
[0157] A simplified user plane architecture is described herein to address the needs and requirements identified above. A core aspect of the simplified user plane architecture is to evolve the 5G PDU session into the composition of a 6G PDU session and a 6G QoS service.
[0158] A 6G PDU session (6PS, also called 6PS session herein) is a UP connection between a WTRU and DN, which is based on a UP tunnel. The UP tunnel is a tunnel between a WTRU side endpoint (e.g., the WTRU, a WTRU application, a device connected to the WTRU) and a proxy endpoint on or collocated with the (e.g., anchor) eUPF. For simplicity, the WTRU-side endpoint of the UP tunnel may be designated as the WTRU herein, and the proxy endpoint on or collocated with the eUPF may be designated as the eUPF herein. The tunnel protocol may be based on MASQUE, and for example use the MASQUE-P protocol described herein. As opposed to a 5G PDU session establishment, a 6PS session establishment does not include the reservation of QoS network resources in the RAN and WTRU. Instead, the WTRU and eUPF mark the IP packets of the 6PS tunnel, and the WTRU and RAN apply a QoS service based on this marking. The 6PS parameters characterizing a 6PS may include DNN, S-NSSAI, and SSC mode.IDC-2025P00305WQ
[0159] A 6G QoS service (6QS, also called 6QS service herein) is a network service provided by a set of resources configured in a RAN node and WTRU, which enables providing a QoS treatment to DL and UL PDUs. A 6QS service may be characterized by a marking (defined hereinafter) and 6QS parameters. The selection, by a WTRU or RAN node, of a 6QS service to apply for a PDU, is determined based on the marking of the packet holding the PDU. The 6QS parameters characterizing a 6QS service may include any one or more of the following example parameters: a 6G QoS Identifier (6QI), Allocation and Retention Priority (ARP), Reflective QoS Attribute (RQA), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), per Session Aggregate Maximum Bit Rate (Session-AMBR), per WTRU Aggregate Maximum Bit Rate (WTRU-AMBR), Maximum Packet Loss Rate, Packet Delay Budget (PDB), PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), and / or PDU Set Integrated Handling Information (PSI HI). In an example system, the QoS treatment may be provided to PDUs of an SDF by the WTRU (e.g., for UL PDUs) and RAN node (e.g., for DL PDUs) using a Data Radio Bearer. Upon receiving a PDU (e.g., an IP packet of a MASQUE-P connection) for transmission over the air interface, the WTRU and RAN node may queue the PDU for transmission by a Data Radio Bearer, which has been configured for the 6QS service, based on 6QS parameters. The selection of the Data Radio Bearer to use may be based on the marking of the IP packet.
[0160] The term "marking” herein may designate setting the value of certain fields in packet headers, such as the differentiated services IPv6 and IPv4 fields, traffic class IPv6 header field, type of service IPv4 header field, or flow label IPv6 header field. A flow may be identified, for example, based on the "3-tuple”, which is composed of one or more of: the flow label, source IP address, and destination IP address. In some cases, a flow may be identified based on the "5-tuple”, which is the composed of one or more of: the source IP address, destination IP address, IP protocol, source port, and destination port. A marking, in some cases in combination with a traffic filter (e.g., including source and destination IP addresses) may correspond to a 6QS service. A RAN node or WTRU may filter packets based on markings (and, for example source and destination IP addresses) and may apply the QoS service corresponding to the marking value of a packet.
[0161] Since the packets are tunneled between WTRU and anchor eUPF, the markings may be within outer packet headers, for example in the IP header of the tunnel packet that carries the PDU between WTRU and eUPF. The WTRU may apply markings (i.e., set values in packet header fields) to UL tunnel packets. The anchor eUPF may apply markings to DL tunnel packets. A marking may also be in a combination of multiple fields (e.g., a DSCP codepoint and a flow label). For example, even if a sender marks all packets of a flow with a DSCP code point, the sender may mark the packets of different sub-flows with different flow labels, which enable the AR to apply different QoS services to the different sub-flows. In this last case, the flow labels may be considered unique for a single pair of source and destination IP address (e.g., WTRU and eUPF IP addresses), which is why a marking filter including a non-zero flow label may be configured along with a source and destination IP addresses. All marking filtering described herein, when it involves a non-zero flow label, is assumed to include the filtering of source and / or destination IP addresses as well. Furthermore, all marking filtering described herein, when it involves a non-zero flow label, may equivalently be performed using a 5-tuple value.
[0162] Herein, the RAN node may be an "Access Router” (AR). In an example, the RAN node may include an IP router functionality. In an example, the RAN node may not include an IP router functionality. The terms "RAN node”IDC-2025P00305WCand "AR” are used interchangeably herein. An AR that includes an IP router functionality may designate, equivalently, an AR that includes a router functionality in the AR device itself (e.g., a gNodeB or a 6G node B, or generally a base station), or it may designate an AR which is connected to an IP router device.
[0163] A WTRU may be configured with at least one service IP address, which may be used as a source address by the WTRU to communicate with the tunnel endpoint on the eUPF. The WTRU may obtain a service IP address from an AR (e.g., if the AR includes an IP router functionality) or from an eSMF (e.g., if the AR does not include an IP router functionality). When a WTRU establishes a 6PS session, the network may configure the WTRU with an end-to-end address (e.g., IP address or MAC address), which the WTRU may use to communicate with remote endpoint over the 6PS session. The WTRU may send CP messages over a 6PS session, which is referred to herein as CP-over-UP (which stands for "CP messages over the UP” and may equivalently be called "CP / UP” herein) feature herein. The CP messages may be (e.g., HTTP) messages that the WTRU and a CN node exchange over the UP.
[0164] In an example, the WTRU-side endpoint of the UP tunnel of a 6PS session may be a WTRU application. This 6PS session may be designated as an application-terminated 6PS session. For example, a WTRU may provide proxy information to a 6PS-aware WTRU application, which may initiate an application-terminated 6PS session by connecting to the proxy identified in the proxy information. This enables the WTRU application to dynamically control the level of service provided by the network (e.g., by directly controlling the marking of the IP packets it sends, and / or by exchanging control messages and per-PDU metadata with the eUPF).
[0165] FIG. 2 is a system diagram illustrating an example simplified 6G architecture 200 based on UP tunnels. Boxes represent devices network functions, and / or groups of network functions, lines represent interfaces (e.g., reference points), and dotted lines represent interfaces that are carried over other interfaces. The example 6G architecture 200 may include WTRU 202, AR 204, AMF 206, ePCF 208, eSMF 210, intermediate-eUPF (l-eUPF) 212, l-eUPF 214, CN-eUPF 216, eUPF 218, DN 220, and CN nodes 222 (e.g., including AMF, eSMF, ePCF). In simplified architecture for 6G 200 based on UP tunnels, functions may be based on existing mobile network functions, and enhanced to support the protocols, mechanisms and procedures defined herein. A eUPF 218 is a User Plane Function (UPF) enhanced to be an endpoint of the UP tunnel that carries the PDUs of a 6PS session. An eSMF 210 is a Session Management Function (SMF) enhanced to manage 6G PDU sessions, which are based on UP tunnels. The eSMF 210 and eUPF 218 may communicate over an N4 interface enhanced to support the establishment and maintenance of the UP tunnel (N4+). An ePCF 208 is a Policy and Control Function (PCF) enhanced to handle policy rules for 6PS sessions and for 6QS services, and to configure 6QS services. The WTRU 202 may communicate on the control plane through an Access and Mobility Management Function (AMF) 206.
[0166] In the simplified architecture for 6G 200 based on UP tunnels, the WTRU 202 is connected to the network through an AR 204, over an Access Network (AN) interface (e.g., an air interface such as Uu). The AR 204 is connected to an anchor eUPF 216 or 218 over the N3+ interface. CN-eUPF 216 is an anchor eUPF that is connected to CN nodes 222 (e.g., over a SBI), while eUPF 218 is an anchor eUPF that is connected to a CN nodes 222 over the N6 interface. The N3+ interface is based on an N3 interface, enhanced to use the MASQUE-U protocol described herein, while in an example, it may use the GTP-U protocol, and in yet other systems, it may use the SRv6 protocol. An Intermediate eUPF (l-eUPF) 212 or 214 may be present between the AR 204 and the anchor eUPF 216 or 218, inIDC-2025P00305WQwhich case the 1-eUPF 212 or 2124 is connected to the anchor eUPF 216 or 218 over the N9+ interface. The N9+ interface is based on an N9 interface, enhanced to use the MASQUE-U protocol described herein, while in an example, it may use the GTP-U protocol, and in yet other systems, it may use the SRv6 protocol.
[0167] The UP tunnel between the WTRU 202 and anchor eUPF (or CN-eUPF 216) may be used to transport PDUs as well as control messages and per-PDU metadata, using a tunnel protocol such as MASQUE-P, described herein. The WTRU-CN-eUPF interface over the (e.g., MASQUE-P) tunnel is designated as Ncn, the WTRU-eUPF interface over the tunnel is designated as Npdu. For example, the WTRU 202 may communicate with CN nodes 222 such as the AMF, ePCF and eSMF, using an SBI interface, accessed through the Ncn interface.
[0168] Advantages of the solution described herein include limiting CP signaling, thus reducing the network load on mobile networks. For example, if a 6QS is already activated, there is no need to communicate with the RAN again to add a new SDF or 6PS session that uses the already activated 6QS service. Furthermore, the solution described herein also enables consistent QoS treatment in the WTRU, RAN node and the transport network (e.g., the network between the anchor eUPF and the RAN node), for example by marking packets with a DSCP codepoint which maps to a consistent QoS treatment among them.
[0169] FIG. 3 and FIG. 4 protocol stack diagrams illustrating two example user plane protocol stacks 300 and 400, respectively, of a simplified 6G architecture based on UP tunnels. FIG. 3 shows an example protocol stack 300 for systems where the AR 304 includes an IP router functionality. The system pertaining to protocol stack 300 may include: WTRU 302, AR 304, l-eUPF 315, and eUPF 318. FIG. 4 shows an example protocol stack 400 for systems where the AR 404 does not include an IP router functionality, or where the IP router functionality of the AR 404 is not activated. The system pertaining to protocol stack 400 may include: WTRU 402, AR 404, l-eUPF 415, and eUPF 418.
[0170] Systems where the AR includes an IP router functionality may have a simpler operation than systems where the AR does not include an IP router functionality, as described herein. An AR including an IP router functionality enables configuring a WTRU service IP address upon connecting to (e.g., attaching to) the AR, which makes it possible to initiate a 6PS session over the user plane using the service IP address. Otherwise, the WTRU may need to obtain a WTRU service IP address from the CN, for example when setting up the 6PS session. The WTRU service IP address may be IP-routable towards the UPFs that are reachable through the AR (e.g., over an IP network that interconnects the AR and UPFs). If the AR includes multiple virtual routers, the WTRU may configure a WTRU service IP address for each virtual router, and the WTRU service IP may be IP-routable towards the UPFs that are reachable through the corresponding virtual router. For added security, the network operator may configure the network, in such a way that the WTRU service IP address is not IP-routable beyond the portion of the network between the AR (or virtual router) and the UPF.
[0171] An AR including an IP router functionality enables discovering proxy information upon connecting to the AR, which makes it possible for the WTRU to directly initiate a 6PS session by connecting, over the user plane, to the anchor eUPF. It also makes it possible to provide proxy information to a 6PS-aware WTRU application, which the WTRU application may use to establish an application-terminated 6PS. An AR including an IP router functionality enables future evolutions of the AR-eUPF interface N3+. Since in this case IP routing may be used to steer packetsIDC-2025P00305WQover the whole path between the WTRU and eUPF, no tunnel is necessary between the AR and eUPF, which enables for example a simpler SRv6-based protocol on N3+.
[0172] In an example, some 6G simplified architecture systems may include RAN nodes that do not include an IP router functionality. For those cases where the RAN node does not include an IP router functionality, the UP connectivity establishment setup procedure described herein may include for example steps E.641 -E.644 in FIG. 6 (described below), in which the WTRU may obtain WTRU service IP address and proxy information from the network, over the control plane. Steps E.641-E.644 in FIG. 6 may be omitted if the RAN node includes an IP router functionality, which reduces CP usage and is therefore more advantageous from network load standpoint. However, supporting RAN nodes that do not include an IP router functionality may be useful to some network operators, for example in cases where some legacy network equipment prevents activating the IP router functionality in an AR.
[0173] FIGs. 3 and 5 include the MASQUE-P and MASQUE-U protocols, in accordance with embodiments described herein. The new MASQUE-P protocol disclosed herein (described below) may be used to tunnel PDUs between the WTRU and the anchor eUPF.
[0174] To enable control and metadata communication between the eUPF and the RAN node, a tunneling protocol may be used. GTP-U is used for this purpose in a (e.g., 5G) mobile network, and may be used in some systems using the simplified 6G architecture based on UP tunnels. MASQUE-U is a new protocol described herein that may replace GTP-U in some systems and provides similar functionalities. One advantage of using MASQUE-U over GTP-U is that the MASQUE-U tunnel may be established without requiring tunnel endpoint IDs to be exchanged beforehand, which further reduces the need for CP signaling.
[0175] The MASQUE-U protocol is a tunnel protocol, based on MASQUE, over the N3+ interface between the AR and eUPF, and N9+ interface between eUPFs. The MASQUE-U protocol may include: MASQUE extensions to carry control signaling protocols such as the PDU session user plane protocol, the PDU set information user plane protocol, using for example HTTP datagram extensions to encode per-PDU metadata, and / or HTTP capsule messages to encode control messages.
[0176] FIG. 5 is a flow diagram illustrating an example UP connectivity establishment and operation procedure 500 in a simplified architecture for 6G based on UP tunnels, which may be performed by a WTRU. Each step in the UP connectivity establishment and operation procedure 500 is described in detail hereinafter. In step 501, a WTRU registers with the network and provides its capabilities to the network, which may result in the network configuring default 6QS services. In step 502, 6QS services are configured in the RAN node and WTRU. In step 503, the WTRU may be provided with the means to configure service IP addresses. In step 504, the WTRU may be provided with proxy information to enable establishing the 6PS session with a proxy on the (e.g., anchor) eUPF. In step 505, the WTRU may trigger the establishment or modification of a 6PS session. In step 506, a 6PS may be established to enable CP messages to be exchanged over the UP between the WTRU and CN nodes.
[0177] Example information elements (IE) are described in the following. Any of the following example identifiers (IDs) may be used in the embodiments described herein. A 6G PDU session ID (6PSID) may identify a 6PS session. The 6PSID may be generated by the WTRU (e.g., in a manner to be unique per WTRU) and transmitted in the 6PSestablishment request message described hereinafter. The eSMF may store the 6PSID in UDM, to indicate that this eSMF is the managing eSMF for the 6PS. In an example, the 6PSID may be an integer value.
[0178] A 6G QoS service ID (6QSID) may identify a 6QS service. The 6QSID may be generated by the network (e.g., ePCF) and transmitted in 6QS configuration messages to the RAN node and WTRU, which may both store the 6QSID locally for future use. The 6QSID may be used in other configuration messages to modify or release a 6QS. The 6QSID may be stored in PCC rules, to indicate that a 6PS should use marking that corresponds to the 6QS service identified by the 6QSID. The 6QSID may be, for example, an integer value or a string. In an example, to simplify the correspondence between 6QS and marking, the 6QSID may be a marking value (e.g., a DSCP codepoint). In an example, some well-known stable 6QSIDs may be marking values (e.g., a value within a subset of the DSCP codepoint space, corresponding to well-known DSCP codepoints), and other 6QSIDs may have values not corresponding to a DSCP codepoint. For those other 6QSI Ds, a DSCP codepoint may be allocated dynamically on demand when needed (e.g., out of a pool of DSCP codepoint reserved for local use).
[0179] Any of the following example proxy information may be used in the embodiments described herein. The network may provide, to the WTRU, proxy information (e.g., in one or more proxy information IPs) that identifies the remote endpoint of the UP tunnel on (or collocated with) the eUPF. The term "proxy” is used herein to designate the UP tunnel endpoint on (or collocated with) the eUPF. A proxy information IE includes parameters that describe the proxy. Any of the following example proxy information may be used in the embodiments described herein: IP address or FQDN, which identifies the proxy; (e.g., UDP) port, which further identifies the proxy; An CP-over-UP indication, which indicates that the proxy is connected to the CN and may be used to communicate with the CN Network Functions; one or more DNN(s). one or more DNAI(s), which identify access points to DNs (e.g., access routers); one or more S-NSSAI(s), for example in systems where the network slice information is exposed to the WTRU; indication of supported session and service continuity (SSC) mode(s); indication of support for identifying and / or transporting media related information or PDU set information; indication of support for virtual LAN services (e.g., 5GLAN); identifiers of WTRU groups that are allowed to use the proxy (e.g., 5GLAN groups); indication of the type of services available through the proxy (e.g., edge computing); identification of the application services available through the proxy (e.g., a video rendering service); and / or Traffic Steering Policies (e.g. TSP IDs) to support Service Function Chaining.
[0180] In an example, the network may include one or more TSP IDs in the proxy information, to indicate the services provided through service function chaining. The WTRU may select a proxy based on TSP IDs which are needed or preferred for an SDF (e.g., based on application preference indicated in local WTRU configuration or in a URSP rule including TSP IDs). In an example, the WTRU may include a TSP ID in a 6PS establishment request or in the CONNECT request message, to indicate that the service function chain identified by the TSP ID should be used for this 6PS session or CONNECT stream. Upon receiving a 6PS establishment request or CONNECT request message including a TSP ID, the UPF may configure itself to chain traffic to / from the 6PS session or CONNECT stream as indicated by the TSP ID.
[0181] In cases where the AR includes an IP router functionality, the proxy information may be associated with an AR IP address, for example the proxy information may include the associated AR IP address, and / or the proxy information be provided through a PvD that is advertised from the associated AR IP address. The network operatorIDC-2025P00305WQmay set up the network in such a way that the proxy may only be accessed through the associated AR IP address. For example, the proxy may be connected, through a network slice, to a virtual router on the AR, which is configured with the associated AR IP address. The network slice may be identified with an S-NSSAI, which may be exposed to the WTRU in some systems and may not be exposed to the WTRU in some other systems.
[0182] PCC rules may enhanced, as described herein, to describe services associated with 6PS sessions and 6QS services in a related but independent manner (e.g., in a manner that enables activating a 6QS service, based on 6QS service rules, separately from establishing or modifying a 6PS session for an SDF, and / or based on transport PCC rules). The parameters of a 6QS service PCC rule or a transport PCC rule may be configured in the network (e.g., ePCF or UDM) by the network operator or by an AF.
[0183] A 6QS service PCC rule (also referred to as 6QS service rule) is a policy rule that describes a 6QS service. A 6QS service rule may include any of the following information: 6QSID, one or more marking filter template IPs that describe how to identify packets that should receive the 6QS service, policy control IPs that define a QoS treatment (e.g., policy control lEs such as 6QI, UL / DL maximum bitrate, UL / DL guaranteed bitrate, UL / DL sharing indications, PDB, PER, PSDB, PSER, etc.), charging lEs (charging key, service identifier, etc.), RAN support information (e.g., UL / DL maximum packet loss rate), QoS monitoring lEs, alternative QoS parameters set, traffic parameter information, PDU set control information, and / or indication to use data burst information.
[0184] A transport PCC rule describes the network service applied to an SDF, as part of an 6PS session. The transport PCC rule may include any of the following information: 6QSIDs identifying the 6QS service required for the SDF, a marking descriptor (define hereinafter) that describes how to mark packets, service data flow detection lEs (e.g., to identify the SDF), access network information reporting, usage monitoring control, N6-LAN Traffic Steering Enforcement Control, Application Function influence on traffic routing Enforcement Control, Handling of Payload Headers Control, MA PDU Session Control, Traffic Parameter Measurement, Downlink Data Notification Control, Data Burst Handling Information, Protocol Description Information, and / or On-path N6 Signaling.
[0185] Some lEs may be relevant in both 6QS service and transport PCC rules. For example, some charging, monitoring or reporting lEs may appear to different rules, depending on if they apply to a 6PS session or to an SDF (e.g., a CONNECT stream) within the 6PS session, or to a 60S service.
[0186] A 60S marking descriptor (also referred to as a marking descriptor or marking generation descriptor herein) is an IE that describes how the WTRU or (e.g., anchor) eUPF should apply marking to traffic of a 6PS session. A marking descriptor is provided to the WTRU and anchor eUPF during the 6PS establishment procedure and / or may be provided to the WTRU and anchor eUPF when adding new SDFs to a 6PS. A marking descriptor is associated with one or more SDFs, such as a marking descriptor provided in a CONNECT request applies to all PDUs transported over the CONNECT stream. In an example, a marking descriptor provided in a 6PS establishment request message may apply to all PDUs transported over the 6PS session.
[0187] A marking descriptor may include any of the following example information: 6QSID; one or more making values; default marking value; and / or marking method IE. The 6QSID may be used to associate the marking descriptor with a corresponding 60S service, in some systems. For example, this may enable a WTRU-based QoS serviceIDC-2025P00305WQconfiguration, where the WTRU obtains the 6QSID from an eURSP rule matching the SDF, and then sends the 6QSID in a message to the network, to request the establishment of the 6QS service corresponding to the 6QSID. In another example, the ePCF may obtain the 6QSID from a transport PCC rule (defined herein) and then use the 6QSID to identify the 6QS service PCC rule (defined herein) which describes the 6QS service. In another example, the 6QSID may be used to retrieve the marking values generated for the 6QSID for this WTRU (e.g., DSCP codepoints and / or flow labels).
[0188] A marking value may include the value of one or more fields (e.g., a first value holds the DSCP codepoint value or 0 for no DSCP marking, a second field holds the flow label value or 0 for no flow label marking). In an example, the marking values are generated when activating a 6QS service, and are retrieved from the CN (e.g., UDM) using the 6QSID and WTRU ID. A default marking value may indicate which marking to apply by default. A marking method IE may indicate an algorithm by which the WTRU or eUPF determine which marking to apply to a PDU. For example, when using a "single marking” method, the WTRU / eUPF marks every (respectively) UL / DL PDU of the associated SDFs with a single marking value provided in the marking descriptor. For example, when using an "expedited forwarding” method, the WTRU / eUPF marks every UL / DL PDU of the associated SDFs with a default marking value provided in the marking descriptor, unless an expedited forwarding indication is present (e.g., in the PDU), in which case the WTRU / eUPF marks the PDU with a second marking value provided in the marking descriptor. The marking method IE that indicates "expedited forwarding” may also include a protocol IE, which indicates how the expedited forwarding indication is signaled (e.g., in a field of the PDU or in an out-of-band way such as using a socket parameter).
[0189] For example, when using a "DSCP mapping” method, the WTRU / eUPF marks every UL / DL PDU based on the DSCP codepoint of the PDU. This makes it possible for an application to influence marking based on application logic. For example, a WTRU application may send packets using different sockets, each associated with a different DSCP value. A marking method IE that indicates "DSCP mapping” may also include a list of tuples (DSCP codepoint, marking), where the second tuple value is the marking that the WTRU / eUPF applies to the tunnel IP header, when the PDU's DSCP codepoint is the first tuple value. If the PDU has a DSCP codepoint which is not in the list, the WTRU / eUPF may mark the tunnel IP header with the default marking value indicated in the marking descriptor. For example, when using an "allowed marking” method, the WTRU may verify that the marking applied on the tunnel IP header by the WTRU application is one of the marking values in the marking descriptor. This method may be used when the WTRU application is the user plane tunnel endpoint, which is also designated herein as application-terminated 6PS session.
[0190] A RAN node or WTRU may use a Marking Filter IE to configure a traffic filter, which may direct incoming traffic towards a QoS treatment corresponding to the marking filter IE. For example, the network sends a QoS configuration request message which includes QoS information and a marking filter IE, which the WTRU and RAN use to configure the QoS treatment, and the corresponding traffic filter. A marking filter I E may include: one or more marking lEs; one or more traffic filter lEs; priority value; and / or direction for the traffic (uplink (UL) or downlink (DL).
[0191] A marking IE may include one or more field value lEs, each indicating the value of a header field (e.g., a first field value IE holds the DSCP codepoint value, a second field value IE holds the flow label value). Zero, or one,IDC-2025P00305WQor more traffic filter lEs may for example include source and destination IP addresses (or portions of IP addresses), IP protocol, and / or port. For example, the traffic filter lEs may be used to match packets to / from a specific WTRU service IP address, and / or to / from a specific eUPF proxy. This makes it possible to use a same marking IE for different QoS treatments (e.g., for SDFs using different slices). For example, a network operator may configure the ARs in such a way that some bits of the AR IP addresses, and WTRU service IP addresses indicate the slice ID being used, which makes it possible to filter traffic per slice. A priority value may indicate the priority of the marking filter with respect to other marking filters.
[0192] The network may use a Marking Filter Template IE to create a marking filter. For example, the network may obtain a marking filter template from a 6QS service PCC rule, generate a marking filter from it, and send the marking filter and QoS information to configure the RAN node and WTRU. The actual marking filter used may be stored by the ePCF (e.g., in UDM), and this may be used to generate new unique marking filters after this (e.g., this enables generating currently unused DSCP and / or flow labels). A reason for using marking filter template is that the number of bits for IP header markings is limited (e.g., there are only 64 distinct DSCP codepoints, and some DSCP codepoints have a standard-defined meaning which further reduces the available pool in some cases). A conflict may occur if the system activated two 6QS services for the same WTRU, with the same marking filter (e.g., using the same DSCP codepoint). Various marking filter allocation strategies may be used, to avoid conflicts. A marking filter template may include the following fields: marking generation strategy IE; one or more marking field values; a number of flow labels to generate; priority value; and / or direction for the traffic (uplink (UL) or downlink (DL).
[0193] The marking generation strategy IE may identify strategies such as: "fixed” strategy, where the marking field values provided in the template are used; "dynamic DSCP” strategy, where the marking field values are generated dynamically, using a currently unused DSCP codepoint; "dynamic DSCP with flow labels” strategy, where the marking field values are generated dynamically, using a currently unused DSCP codepoint, and one or more currently unused flow labels are generated (e.g., unused for a given pair of WTRU IP address and eUPF IP address). This restricts the application of the QoS treatment of the 6QS service to only flows that are marked with one of these flow labels (e.g., and source and destination IP addresses) and the DSCP codepoint. This makes it possible to use a DSCP codepoint for more than one 6QS service, which enables scaling beyond the 64 DSCP values limitation.
[0194] A WTRU Route Selection Policy rule (URSP) is a policy rule that indicates how to route outgoing traffic (e.g., an SDF), in a 5G network. A URSP rule may include a traffic descriptor that is used to match the characteristics of an SDF (e.g., including an application ID and / or IP descriptors), and one or more route selection descriptors that indicate the characteristics of a PDU session for the traffic (e.g., including DNN, SSC mode, S-NSSAI).
[0195] An enhanced WTRU Route Selection Policy rule (URSP) is a policy rule that indicates how to route outgoing traffic (e.g., an SDF) in a 6G network based on an architecture described herein. The WTRU may evaluate the eURSP rules against the characteristics of the SDF (e.g., application ID, an FQDN, destination IP address and port, etc.), and may select an eURSP rule that matches those characteristics, when the WTRU needs to request network resources for a new SDF (e.g., when a WTRU application opens a network socket). A eURSP rule may include a traffic descriptor and route selection descriptors, including lEs defined for a URSP rule.IDC-2025P00305WC
[0196] An eURSP rule may include a marking descriptor (e.g., in a route selection descriptor). When a WTRU selects an eURSP rule for a new SDF (e.g., for a traffic flow to and from a WTRU application), the WTRU may use the marking descriptor from the selected rule to determine how to mark outgoing UL packets that hold UL PDUs from this SDF. In cases where the WTRU application initiates the UP tunnel establishment, the WTRU application may mark the outgoing packets, and the WTRU may use the marking descriptor to verify that the markings by the WTRU application are allowed (e.g., if they are included in the marking descriptor) and otherwise to overwrite the packet marking with an allowed value (e.g., with a "default marking” present in the marking descriptor). The eUPF may mark outgoing DL packets that hold DL PDUs, based on a marking descriptor (e.g., provided by eSMF in a FAR rule in an N4 session message).
[0197] An eURSP rule may include proxy information (e.g., in a route selection descriptor). The network (e.g., ePCF) may configure eURSP policy rules including proxy information in the WTRU (e.g., using a configuration update procedure, or using a registration procedure). eURSP policy rules including proxy information include at least one rule that includes proxy information, such as a proxy address (e.g., IP address, FQDN, and / or UDP port), and / or other proxy information IPs as described herein. Once configured with eURSP rules including proxy information, the WTRU may determine the proxy information to use for a 6PS session, based on the selected eURSP rule including proxy information.
[0198] An eURSP rule may include in its traffic descriptor a CP-over-UP indication, which indicates that the eURSP rule applies to CP-over-UP traffic. When the WTRU determines it needs a 6PS for CP-over-UP traffic, it may use the CP-over-UP indication to determine which eURSP rule to select.
[0199] 6PS parameters may be used in multiple messages between the WTRU and (e.g., anchor) eUPF. 6PS parameters may be indicated using for example HTTP header fields (in HTTP request or response messages), or in HTTP capsule messages. 6PS parameters may apply to a 6PS session or to a CONNECT stream of the 6PS session (e.g., to an SDF). 6PS parameters may include any of the following information: 6PS session ID; CP-over-UP indication; indication of SSC mode; DNN; S-NSSAI; traffic filter; DL and / or UL media related information protocol indication; rate recommendation indicator; other metadata indicators; and / or other 6PS parameters derived from 5G PDU session parameters.
[0200] A 6PS session ID may be used for future reference, for example to modify or release or report information about this 6PS session. A CP-over-UP indication may indicate that the requested 6PS session is for transmitting CP messages over UP. An SSC mode may indicate how the network should handle session continuity for this 6PS. In some cases, the requested SSC mode may not be necessary if the proxy is dedicated to one SSC mode. For example, the SSC mode may be provided within the information for this proxy. An DNN may indicate which DN to connect to. In some cases, the requested DNN may not be necessary, if the proxy is dedicated to connecting to one DN. For example, the DNN may be provided within the information for this proxy. An S-NSSAI may indicate which slice to connect through. In some cases, the requested S-NSSAI may not be necessary, if the proxy is dedicated to one slice. For example, the S-NSSAI may be provided within the information for this proxy, or in some systems the proxy information may be advertised with an AR IP address that is connected to a network slice.IDC-2025P00305WC
[0201] A traffic filter may indicate the traffic that is allowed on a 6PS or on an SDF or on a CONNECT stream. For example, when included in a CONNECT request message, a traffic filter indicates that the traffic that is transmitted over the CONNECT stream is limited to flows that match the traffic filter. A DL and / or UL media related information protocol indication may indicate that PDU set information and / or media related information such as burst size or time-to-next burst should be communicated between eUPF and RAN (e.g., in GTP-U or MASQUE-U or SRv6 protocol). The protocol indication further indicates how to identify the PDU set information and / or media related information. The indication may be enhanced to also indicate that the PDU set information and / or media related information should be exchanged over the UP tunnel between WTRU and eUPF. A rate recommendation indicator may indicate that the eUPF may send rate recommendations to the WTRU. Other metadata indicators may indicate that the eUPF or WTRU may send a specific type of per-PDU or non-per-PDU metadata over MASQUE-P. Other 6PS parameters derived from 5G PDU session parameters may include for example "always-on PDU session” and / or "URSP rule enforcement report”.
[0202] A first aspect, in accordance with embodiments disclosed herein, is the WTRU registering with the network. The WTRU may send a network registration request message to the network function handling registration through the RAN node. For example, the network function handling registration may be an AMF. Hereinafter, the AMF may represent such a network function. In an example, the network registration message may include WTRU capabilities indicating any of the following: support for IP connectivity from AR; support for proxy information discovery from AR; support for UP tunnel (e.g., for MASQUE-P protocol); and / or support for CP messages over UP.
[0203] Upon receiving the network registration request, the AMF may send an indication message to the AR, which indicates that the AR should operate as an IP router with the WTRU. This indication may be based on the WTRU capability "support for IP connectivity from AR”. Further, the AMF may send an indication message to the AR, which indicates that the AR should advertise proxy information to the WTRU (e.g., using PvD). This indication may be based on the WTRU capability "support for proxy information discovery from AR”. Further, the AMF may select an ePCF for the WTRU. The ePCF selection by the AMF may be based on the WTRU capability "support for UP tunnel” (e.g., the AMF may select an ePCF that supports providing 6PS policies).
[0204] The AMF may send, to the selected ePCF, an (e.g., AM) Policy Control Create request message. The ePCF may determine a set of default 6QS for the WTRU, for example a set of 6QSs the WTRU may assume to always be available when registered to the network. The ePCF may configure the default 6QSs, as described herein, which may include a 6QS for CP-over-UP traffic (e.g., based on the WTRU capability "support for CP messages over UP”), a 6QS for best effort traffic, and a 6QS for emergency traffic. Once the default 6QS(s) are configured, the ePCF may send a policy control create response message, including policy information (e.g., transport PCC rules).
[0205] The ePCF may receive different triggers to establish a 6QS service. For example, a trigger may be that an AF configures a new 6QS service through the NEF or ePCF and include in the 6QS configuration a "default 6QS service” indication, which indicates that the ePCF should configure the 6QS service in the RAN node when the WTRU is registered with the network. For example, a trigger may be that the network operator configures a new 6QS service including a default 6QS service indication. For example, a trigger may be that an AF configures a new 6QS service through the NEF or ePCF, with a corresponding marking descriptor and SDF, which indicates the new 6QS serviceIDC-2025P00305WQshould be used for the SDF. If the traffic for the SDF is already transported by an established 6PS session, the ePCF may configure the new 6QS service in the RAN and WTRU and may provide the eSMF with modified ePCC rules including the SDF, marking descriptor and new 6QS identifier, which triggers the eSMF to send an N4 message to the eUPF to update the marking descriptor for the 6PS. The eUPF may send a UP message to the WTRU to update the marking descriptor (e.g., using a new HTTP capsule message MARKING_DESCRIPTOR, including an indication of the marking descriptor to use for UL traffic in the CONNECT stream or 6PS session).
[0206] In an example, the ePCF may send to the AMF (e.g., in the policy control create response) policy information that includes proxy information. The AMF may send a registration response message to the WTRU, including policy information that includes proxy information. An example of policy information that includes proxy information is an eURSP rule, which includes proxy information, a DNN (indicating that the proxy may be used to access the DNN), and / or S-NSSAI (indicating that the proxy may be used to access the S-NSSAI).
[0207] A second aspect, in accordance with embodiments disclosed herein, is configuring a 6QS Service. An ePCF may determine that a 6QS service should be established, for example in response to a request message from an AMF, indicating that a WTRU is in the process of registering with the network, the ePCF may determine that one or more default 6QS services should be established for a WTRU. Default 6QS services may include: a 6QS service for communication between the WTRU and network nodes (e.g., with the AR, a CN-eUPF, CN nodes through the CN-eUPF), a 6QS service for emergency calls, a 6QS service for best effort communication (e.g., for best effort Internet access). In another example, the ePCF may determine that a 6QS service should be established in response to a request message from an eSMF, indicating that a WTRU requested the establishment of a 6PS, the ePCF may determine that the 6PS requires a 6QS which is not currently activated in the RAN node.
[0208] The ePCF may determine the marking filter for a 6QS service, based on a 6QS service rule (described herein) and in some cases based on currently active marking filters (described herein). The ePCF may obtain the 6QS service rule (e.g., from the UDM) using a 6QSID (e.g., obtained from a list of default 6QSID in ePCF configuration or in WTRU subscriber data, or obtained from a transport PCC rule). The ePCF may obtain the list of active marking filters for a WTRU from the network (e.g., UDM). Once a 6QS service is activated, the ePCF may update the list of active marking filters in the network (e.g., UDM). In some cases (e.g., when the marking filter type is fixed), the ePCF may determine to use the marking filter based on the value in the 6QS service rule. In some cases (e.g., when the marking filter type is dynamic), the ePCF may determine a marking filter that is currently not in use (e.g., an unused DSCP codepoint or an unused combination of DSCP codepoint and IP flow label(s), in combination with source and destination IP addresses).
[0209] The ePCF may configure a 6QS service in a RAN node and WTRU, by sending a QoS service configuration request message including QoS information for the RAN (e.g., QoS profiles), QoS information for the WTRU (e.g., QoS rules) and the determined marking filter lEs. The QoS service configuration request may be sent to the RAN through the AMF. Upon receiving the QoS service configuration request message, the RAN node configures the 6QS service in the RAN node to provide QoS treatment based on the QoS profile, on PDUs that matches the marking filter indicated in the marking filter IE. Upon receiving the QoS service configuration request message, the WTRU configuresIDC-2025P00305WQthe 6QS service in the WTRU to provide QoS treatment based on the QoS rule, on PDUs that matches the marking filter indicated in the marking filter IE.
[0210] In an example, the 6QS service configuration may be determined by the WTRU. In such systems, the WTRU may be configured with 6QSIDs (e.g., in eURSP rules). When the WTRU determines to request a 6PS session, the WTRU may select an eURSP rule including a 6QSID. The 6QSID from the selected eURSP rule indicates which 6QS service should be used for this 6PS session. The WTRU may determine if the 6QSID is activated, which the WTRU knows based on local information on the WTRU, since to be activated, a 6QS service must be configured on the RAN node and on the WTRU as well. To activate a 6QS service, the WTRU may send a QoS service configuration request message to the network, including the 6QSID (e.g., to the AMF or to the ePCF or eSMF through the AMF). Once the 6QS service is activated, the AMF / eSMF / ePCF may configure the 6QS service in the RAN node and WTRU (e.g., according to steps A.601-A.610 in FIG. 6).
[0211] A third aspect, in accordance with embodiments disclosed herein, is configuring IP service connectivity and configuring the service IP address of the WTRU. In systems where the AR includes an IP router functionality, the WTRU and AR establish a communication channel for exchanging IP messages. The AR and the WTRU establish one or more radio bearers to exchange IP messages (as described hereinafter). The radio bearers to exchange IP messages may be signaling radio bearers or data radio bearers. In an example, a new RRC message may be used to carry WTRU-AR IP messages over a signaling radio bearer. In an example, a user plane data radio bearer may be established for a default 6QS service after the WTRU registers with the network (e.g., using steps A.6-A.10), and the WTRU-AR IP communication may be transmitted over the data radio bearer of the 6QS service. In an example, the AR may configure (e.g., by sending an RRCReconfiguration message to the WTRU after the initial WTRU-RAN connection setup) a user plane data radio bearer that is dedicated to WTRU-AR IP communication.
[0212] In systems where the AR includes an IP router functionality, the AR may be configured to send Router Advertisement messages to the WTRU when the WTRU connects to the AR over the air interface (e.g., Uu interface), and after the WTRU registers with the network. The AR may be configured (e.g., by the network operator using QAM messages) with one or multiple IP addresses on its air interface, corresponding to one or more network slices. The AR may send a Router Advertisement for each IP address that the WTRU should have access to (I . e. , for each network slice that the WTRU should have access to). The AMF may provide to the AR the list of slices (e.g., S-NSSAIs) that the WTRU has access to (e.g., in the registration response message). The WTRU may use information from the Router Advertisement to configure its service IP address (e.g., using SLAAC). Alternatively, the AR may be configured to use the DHCP protocol, and the WTRU may obtain its service IP address from the AR using DHCP, after registering with the network.
[0213] In systems where the AR includes an IP router functionality, the AR may also be configured with DNS server information, which may be provided to the WTRU in Router Advertisement messages or DHCP messages. The DNS server information may include one or more DNS server IP addresses. The WTRU may use a DNS server associated with a service IP address to resolve FQDNs for its connectivity needs over the service IP address (e.g., to resolve the FQDN of an eUPF). The operator may configure the DNS servers with the IP addresses of eUPFs and other nodes that a WTRU may need to access from its service IP address.IDC-2025P00305WQ
[0214] In systems where the AR does not include an IP router functionality, the WTRU may obtain its service IP address from an eSMF. In this case, the WTRU may send a 6PS request message to the eSMF, over the CP through AMF. The eSMF may select an eUPF for the 6PS and selects a service IP address suitable for communicating with the eUPF (e.g., in the same subnet as the eUPF proxy IP address). The eSMF may send the WTRU service IP address to the WTRU in a 6PS response message, over the CP through AMF.
[0215] A fourth aspect, in accordance with embodiments disclosed herein, is discovering proxy information. In systems where the AR includes an IP router functionality, the AR may be configured to provide the means for the WTRU to obtain proxy information. For example, the network operator may configure the AR to include a PvD ID in its Router Advertisement messages, where the PvD ID is an FQDN, which may be resolved into the IP address of an HTTP server (e.g., in the operator's CN). The network operator may configure the HTTP server with proxy information, for example corresponding to all services (e.g., corresponding to a combination of DNN and network services such as PDU sets for XR traffic) reachable within a given slice (e.g., S-NSSAI). Upon receiving a Router Advertisement including a PvD ID, the WTRU may send a DNS request to resolve the PvD ID and may receive the IP address of an HTTP server. The WTRU may send an HTTP GET request to the HTTP server and may receive a (e.g., JSON) document that includes proxy information.
[0216] In other systems where the AR includes an IP router functionality, the WTRU may receive proxy information over the CP. For example, the network (e.g., PCF) may configure the WTRU, with eURSP policy rules including proxy information. In other systems where the AR includes an IP router functionality, the WTRU may request proxy information over the UP. The network operator may configure an address (e.g., FQDN or anycast IP address) of a "default eUPF” into the WTRU. The WTRU may send a 6PS request message (e.g., as described herein) to the default eUPF, over the user plane (e.g., an HTTP request sent from the WTRU service IP address). The eUPF may transmit the request to an eSMF and / or ePCF, which validates that the WTRU is authorized to access the requested service, and which selects an appropriate eUPF (e.g., an eUPF that supports the requested services such as PDU set). The eSMF / ePCF may provide the selected eUPF proxy address (e.g., FQDN or IP address) and port to the default eUPF, which sends an HTTP response (e.g., an HTTP redirect response) including the address / port of the selected eUPF. The WTRU may establish a 6PS session with the selected eUPF.
[0217] In systems where the AR does not include an IP router functionality, the WTRU may obtain the proxy information from eSMF. In this case, the WTRU may send a 6PS request message to the eSMF, over the CP through AMF. The eSMF may select an eUPF for the 6PS. The eSMF may send, to the WTRU, proxy information including the IP address (or FQDN) and (e.g., UDP) port of the eUPF proxy. The WTRU may use the proxy information received from the eSMF to determine the remote endpoint of the (e.g., MASQUE-P) UP tunnel. The WTRU may establish a MASQUE-P connection with the remote endpoint.
[0218] A fifth aspect, in accordance with embodiments disclosed herein, is establishing and modifying a 6G PDU session (6PS). The MASQUE-P protocol may be used between WTRU and anchor eUPF, to tunnel PDUs and exchange control messages and per-PDU metadata between WTRU and anchor eUPF. The MASQUE-P connection is based on a MASQUE connection described above. The MASQUE-P protocol may also be used directly by a WTRU application (e.g., a WTRU application may establish a MASQUE-P tunnel with an eUPF, which is describedhereinbefore as "application-terminated 6PS session”). When a WTRU needs to send traffic for a new SDF (e.g., when a WTRU application is started and opens a socket), the WTRU may look up the eURSP rules, and may determine if an existing matching MASQUE-P connection (i.e., an existing 6PS session) may be used, or if a new MASQUE-P connection (i.e., a new 6PS session) should be established for the SDF. To determine if a MASQUE-P connection matches, the WTRU may compare the eURSP rule parameters (e.g., DNN, SSC mode, S-NSSAI) and the parameters corresponding to the MASQUE-P connection (e.g., DNN / SSC mode / S-NSSAI from the proxy information or from the 6PS parameters).
[0219] The WTRU may establish a MASQUE-P connection by establishing an HTTP connection with an endpoint (e.g., an anchor eUPF). In an example, the WTRU may send a 6PS session establishment message to the eUPF, to request some parameter values for this 6PS session. The eUPF may provide, in its response, a marking descriptor that indicates how to mark the packets for this 6PS session. The WTRU may send a CONNECT request message to the eUPF, to request proxying an SDF. The CONNECT request message may also request some parameter values for this CONNECT stream. The CONNECT request message, and in some cases additional messages sent over the CONNECT stream (such as ADDRESS_ASSIGN), may include information that identifies one or more SDF that will be transported over the CONNECT stream (e.g., in HTTP headers). The eUPF may use the information that identifies the SDF to configure packet detection rules to identify the SDFs, which enables the eUPF to route traffic between N6 and the CONNECT stream. The eUPF may provide, in its response to the CONNECT request message, a marking descriptor that indicates how to mark packets for this CONNECT stream. The WTRU and eUPF may exchange other control messages (e.g., using HTTP messages, and / or HTTP capsule messages) for example within a control stream. Within a CONNECT stream, the WTRU and / or eUPF may send per-PDU metadata information (e.g., PDU set information or other media related information).
[0220] The AR may establish an AR-eUPF tunnel when forwarding the initial packet of the HTTP connection establishment towards the eUPF. For example, the AR may receive the initial packet from the WTRU, establish a MASQUE-U connection to the destination IP of the initial packet from the WTRU (e.g., the anchor eUPF), and may forward the initial packet from the WTRU over a CONNECT stream of MASQUE-U connection. The WTRU may send a 6PS session establishment message, e.g., an HTTP POST message or an HTTP capsule message, to the eUPF. The 6PS session establishment message may include 6PS session parameters indicating requested parameters for the session. Upon receiving the message, the eUPF may communicate with the eSMF, to validate that the WTRU has the right to obtain the requested services. In cases where a 6PS session is for a single SDF or a known set of SDFs, the eSMF may verify that the 6QS service(s) required for the SDF (e.g., from the PCC rules) are activated in the AR, and otherwise the eSMF may activate the 6QS service(s). The eSMF may provide in this case the corresponding marking descriptor(s) to the eUPF.
[0221] The eUPF may send a 6PS establishment response message indicating if the request is accepted (e.g., with a 200 OK status code). The HTTP response may include a marking descriptor (as described herein) or a reference to a marking descriptor, which indicates how to mark the packets of this 6PS session tunnel. The HTTP response may include 6PS parameters indicating accepted parameter values for the session.IDC-2025P00305WQ
[0222] The WTRU may send CONNECT request message(s) to enable the tunneling of SDFs, for example inside a CONNECT stream of the HTTP connection. The WTRU may send more than one CONNECT request message over the lifetime of the MASQUE-P connection (e.g., to tunnel different SDFs), for example over different protocols like UDP, IP, Ethernet, and / or TCP, and / or possibly towards different remote endpoints. The WTRU may send a CONNECT request message that include the appropriate “connect-udp / i p / ethernet / tcp” protocol value and may include one or more 6PS parameters indicating requested characteristics of the CONNECT stream. Upon receiving the message, the eUPF may send a message to the eSMF, including lEs of the CONNECT request such as protocol and 6PS parameters, to validate that the WTRU has the right to obtain the requested services, and to receive a marking descriptor and 6PS parameters for the response. The eSMF may retrieve policy rules from the ePCF. The ePCF or eSMF may verify that the 6QS service(s) required for the SDF(s) are activated in the AR, and otherwise the eSMF / ePCF activates the 6QS service(s). The eSMF may send a response to the eUPF, which may include marking descriptor(s) and / or 6PS parameters. The eUPF may use some 6PS parameters to configure itself. For example, based on a "protocol description for PDU set” 6PS parameter, the eUPF may configure itself to identify PDU set information and provide PDU set information to the RAN (e.g., in HTTP datagram headers in the MASQUE-U connection, or in GTP-U headers). The eUPF may send an HTTP response to the WTRU, in response to the CONNECT request, including marking information and / or 6PS parameters. For example, the eUPF may include an HTTP header in the response message, which indicates that HTTP datagram header will be used in the MASQUE-P to carry PDU set information to the WTRU.
[0223] The eUPF may send an HTTP response message, indicating if the CONNECT request message is accepted (e.g., with a 200 OK status code). The HTTP response may include a marking descriptor or a reference to a marking descriptor, which indicates how to mark the packets of this CONNECT stream. The HTTP response may include 6PS parameters as well, for example indicating accepted values.
[0224] The WTRU or the eUPF may close a CONNECT stream to stop transmitting an SDP or close a MASQUE-P connection to release a 6PS session. The eUPF may communicate this closing event to the eSMF, which may for example release a 6QS service if no other 6PS is using the 6QS service. The eSMF may start a timer, and release an unused 6QS once the timer elapses, to reduce the amount of signaling in some cases. To connect to the eUPF over the MASQUE-P protocol, a WTRU may need a service IP address. If the WTRU does not have a service IP address (e.g., the WTRU is connected to an AR without IP router functionality), then the WTRU may send a 6PS request message to an eSMF, over the CP. The 6PS request message may include 6PS parameters to enable the eSMF to select an appropriate eUPF.
[0225] Examples of per-PDU metadata in MASQUE-P CONNECT streams may include: a WTRU that needs to forward XR traffic towards another WTRU or device, may be able to use PDU set information and burst information to save energy while forwarding the XR traffic, such that the WTRU may request PDU set information and burst information metadata to be provided with DL PDUs in a CONNECT stream; and / or in a case where a WTRU sends XR traffic towards a remote WTRU through the network, the network may request the sender WTRU to provide PDU set information and burst information with UL PDUs in a CONNECT stream.IDC-2025P00305WQ
[0226] A sixth aspect, in accordance with embodiments disclosed herein, is enabling CP message over UP (i.e., CP-over-UP or CP / UP). The network registration message sent by the WTRU to the network (e.g., through AMF) may include a CP-over-UP WTRU capability. The CP-over-UP WTRU capability may indicate that the WTRU supports sending CP messages over the UP, which may include: the WTRU establishing a 6PS session for CP-over-UP, the WTRU sending CP messages over the 6PS, and / or the WTRU marking the packets it sends over the 6PS with markings that correspond to a 6QS service appropriate for CP-over-UP traffic. In an example, the CP-over-UP WTRU capability may be implicit (e.g., all WTRUs may support CP-over-UP).
[0227] The network may configures a default 6QS for CP-over-UP (e.g., referred to as "CN-6QS” herein), based on the network registration request and / or the CP-over-UP WTRU capability. The network may configure more than one CN-6QS with different QoS parameters, to support differentiated QoS for CN traffic (e.g., to provide higher QoS treatment to important or emergency messages). The marking values associated with the CN-6QS services may be configured on the WTRU (e.g., in eURSP rules that match CN / UP traffic).
[0228] The WTRU may request establishing a 6PS for CP-over-UP, based on a trigger. The trigger may be that the WTRU successfully registered with the network. The trigger may be that the WTRU has a CP message to send over the UP. The trigger may be that the CN has a CP message to send over the UP, and the CN triggers the WTRU to establish the CP-over-UP 6PS. The 6PS establishment for CP-over-UP may be initiated by any of the following example approaches: it some systems, the WTRU discovers, or is configured with proxy information including an indication that the proxy supports CP-over-UP, and the WTRU sends, to the proxy, a 6PS establishment request; and / or in an example, the WTRU sends, to the network, a 6PS establishment request over the control plane (e.g., NAS) including an indication that the 6PS is for CP-over-UP, and the network (e.g., eSMF) uses the indication to select an eUPF that supports CP-over-UP.
[0229] Following any of these establishment requests, the CP-over-UP 6PS session is established as described herein. The anchor eUPF of a CP-over-UP 6PS may be referred to herein as a CN-eUPF. The CN-eUPF is interconnected with the CN, and tunnels PDUs between the CN and the WTRU. In an example, a CP-over-UP 6PS may be a long-lived 6PS. In an example, a CP-over-UP 6PS may be closed when not used (e.g., after a timer elapsed without traffic), and may be re-established on demand (e.g., when the WTRU or CN has a CP message to send over the UP).
[0230] FIGs. 6 and 7 describe example procedures for a WTRU to register to the network and establish a 6PS session. FIG. 6 is a flow diagram illustrating an example registration procedure 600 for a WTRU 652 to register to the network and establish a 6PS session (part 1 of 2). The system performing the example registration procedure 600 may include: WTRU 652; AR 654 (or RAN, or RAN node, or base station); CN 665; AMF 666; eSMF 668 (or SMF); eUPF 670 (or UPF); and ePCF 672 (or PCF).
[0231] The steps in section "A" (with prefix "A”) are part of network subscription by the WTRU 652. In step A.601, in systems where the AR 654 includes an IP router functionality, the network operator configures the AR 654 with IP addresses and subnets, as well as IP routing rules. This configuration may be related to network slicing (e.g., the network operator may configure multiple virtual IP routers in the AR 654, each corresponding to a network slice). ForIDC-2025P00305WQexample, a first virtual router may be configured with IP address IP-vn1 -air on the air interface and IP-vn1 -eth on a second network interface and be connected to a virtual network VN1 through the second network interface, where VN1 is an instance of a first network slice identified with S-NSSAI1. A second virtual router may be configured with IP address IP-vn2-air on the air interface and IP-vn2-eth on a second network interface and be connected to a virtual network VN2 through the second network interface, where VN2 is an instance of a second network slice identified with S-NSSAI2. As a result, a WTRU 652 connected to the AR 654 may be able to be configured (e.g., in step C), with 2 service IP addresses, IP-vn1-WTRU in the same subnet as IP-vn1 -air and using IP1 -vn1 -air as default route, IP-vn2-WTRU in the same subnet as IP-vn2-air and using IP-vn2-air as default route. The WTRU 652 could, in this example, establish a 6PS session using IP-vn1-WTRU as source IP address for the MASQUE-P tunnel between WTRU 652 and UPF 670, whose traffic is routed through IP-vn1-air, to receive a service within the network slice S-NSSAI1. The WTRU 652 may, in this example, establish a 6PS session using IP-vn2-WTRU as source IP address for the MASQUE-P tunnel between WTRU 652 and UPF 670, whose traffic is routed through IP-vn2-air, to receive a service within the network slice S-NSSAI2.
[0232] In step A.602, the WTRU 652 sends a network registration request message to the network, through the AR 654. The AR 654 may select an AMF 666 and forward the request to the selected AMF 666. The request message may include capabilities, as described herein. In step A.603, the AMF 666 selects an ePCF 672 for the WTRU 652. In step A.604, the AMF 666 sends an AM Policy Control Create request to the WTRU 652 including a WTRU ID (e.g., SUPI). In step A.605, based on the received policy control message, the ePCF 672 retrieves policy control subscription data for the WTRU 652 (e.g., from the UDR) and determines if there are default 6QS(s) for the WTRU 652, where a default 6QS is a 6QS that should always be activated in the RAN node (AR 654), as long as the WTRU 652 is registered. A default 6QS may be useful to limit CP operations (and therefore latency) when setting up a 6PS. For example, policy information for a WTRU 652 may indicate that there are three default 6QS: one for best-effort Internet traffic, one for CP messages over UP, and one for emergency traffic.
[0233] Steps A.606-A.610 describe the ePCF 672 configuring one or more 6QS services (e.g., in this example, default 6QS identified in step A.5). In an example, the eSMF 668 (e.g., instead of the ePCF 672) may configure the 6QS services. In an example, the WTRU 652 may trigger the 6QS service configuration, as described herein. In step A.606, the ePCF 672 determines the marking filter I E(s) for the 6QS service as described herein. The ePCF 672 sends a QoS Service configuration request message, including QoS information (e.g., QoS profile(s) for the RAN / AR 654, QoS rule(s) for the WTRU 652), and marking filter IE(s), as defined herein. QoS information may include a QoS identifier (e.g., like 5QI) that identifies a set of detailed QoS information elements, and / or detailed QoS information elements which may include any of the following: Allocation and Retention Priority, guaranteed or maximum bit rate, reflective QoS attribute, QoS monitoring and reporting information, packet error rate, packet delay budget, PDU set error rate, PDU set delay budget, and / or Maximum Data Burst Volume. The request message may be a CP message sent through the AMF 666 towards the AR 654. The request message may be composed of an inner message for the WTRU 652 (e.g., including QoS information for the WTRU 652 and marking filter I E(s)) and an outer message for the RAN / AR 654 (e.g., including QoS information for the RAN 654 and marking filter IE(s)). In an example, other nodes than the ePCF 672, such as eSMF 668, may be able to send a QoS Service configuration request message.IDC-2025P00305WQ
[0234] In step A.607, the AR 654, upon receiving the QoS Service configuration request, configures one or more QoS treatments based on the QoS information. For example, the AR 654 configures Data Radio Bearers on the WTRU 652 and AR 654, to transmit traffic and provide the QoS treatment corresponding to the QoS configuration provided in the request. The AR 654 configures one or more packet filters based on the marking filter I E(s). The AR 654 associates the configured packet filters with the configured QoS treatments (e.g., with the Data Radio Bearers), in such a way that MASQUE-P IP packets matching the packet filter are applied the associated QoS treatment (e.g., the IP packets matching the packet filter are forwarded over the associated Data Radio Bearer). In step A.608, the AR 654 sends, to the WTRU 652, a QoS service configuration request message (e.g., including the inner message for the WTRU 652), including updated QoS information, which can include QoS rules and Data Radio Bearer configuration information, and marking filter IE(s).
[0235] In step A.609, the WTRU 652 configures one or more QoS treatment (e.g., including Data Radio Bearers) based on the updated QoS information (e.g., based on the Data Radio Bearer configuration information). The WTRU 652 configures one or more packet filters based on the marking filter IE(s) and QoS rules. The WTRU 652 associates each configured QoS treatment with a configured packet filter, in such a way that PDUs in MASQUE-P packet matching the packet filter are applied the associated QoS treatment. In step A.610, the WTRU 652 sends a QoS service configuration response to the ePCF 672, through the AR 654 and AMF 666. The response indicates the success of the configuration operation. The ePCF 672 may store the 6QS service activation status in the UDM (not shown), along with a WTRU ID such as SUPI, and / or the 6QSID. The ePCF 672 / eSMF 668 may retrieve 6QS service activation status to determine whether a 6QS service needs to be configured in the AR 654.
[0236] In step A.611, the ePCF 672 sends an (e.g., AM) Policy Control Create response to the AMF 666. In an example, the response may include proxy information, for example any of the following proxy information: providing proxy information corresponding to network services such as best-effort Internet, CP messages over UP, and / or emergency traffic, which correspond to default 6QS services. Proxy information may alternatively or additionally be provided to the WTRU 652 using other methods, as described herein. In step A.612, the AMF 666 sends a registration accept message to the WTRU 652, indicating success or failure of the network registration operation. The response may include proxy information, such as received in step A.611. Proxy information may alternatively or additionally be provided to the WTRU 652 using other methods, as described herein.
[0237] The steps in section "B" (with prefix “B”) are the configuration of WTRU policies by the network. For example, the section “B” may be based on a WTRU Configuration Update procedure.
[0238] In step B.621, the ePCF 672 (e.g., ePCF 672 for the WTRU 652 selected in step A.603, or another ePCF) decides to update WTRU policy based on a triggering condition (e.g., WTRU initial registration, registration with 5GS when the WTRU 652 moves from one access technology to another technology, creation or modification of a WTRU policy rule based on network operator action or based on AF request). In step B. 622, the ePCF 672 sends a message including WTRU policies to the WTRU 652 (e.g., through the AMF 666). The WTRU policies may include eURSP rules including marking descriptor and / or proxy information, as described herein. Upon receiving the message, the WTRU 652 configures the WTRU policies on the WTRU 652. Proxy information may alternatively or additionally be providedIDC-2025P00305WCto the WTRU 652 using other methods, as described herein. In step B. 623, the WTRU 652 sends a message including the WTRU policies delivery operation result to the ePCF 672 through the AMF 666.
[0239] In an example, steps of section “C” (step C.630) are executed. In step C.630, the service IP address and proxy information are configured in systems where the AR 654 includes an IP router functionality (details of section “C” are described in FIG. 8). In an example, the service IP address and proxy information may be configured on the WTRU 652 through the AR 654, using the user plane, as described in section C. In an example, the service IP address and proxy information may be configured on the WTRU 652 through the control plane, as described in section E of FIG. 6. Proxy information may alternatively or additionally be provided to the WTRU 652 using other methods, as described herein.
[0240] The steps in section "D" (with prefix “D”) are operations on the WTRU 652 to initiate network service for a new SDF. In step D.631 , the WTRU 652 receives a trigger to request resources for a new SDF. For example, a WTRU application starts and opens a socket to communicate with a remote AS (not shown). For example, the WTRU 652 determines that it needs to send a CP message over UP (e.g., as part of an existing or new procedure, such as sending measurements to the NWDAF). In step D.632, the WTRU 652 looks up the eURSP rules and selects a rule matching the characteristics of the SDF. The selected eURSP rule includes route selector information that indicates 6PS parameters for a 6PS session or a flow (e.g., a CONNECT stream) of the 6PS session. In an example, the eURSP rule includes a marking descriptor and / or a proxy information, which enables the WTRU 652 to select the marking descriptor and / or proxy information associated with the 6PS session or a flow of the 6PS session.
[0241] In an example, steps of section “E” (with prefix “E”) are executed. The steps in section "E" (with prefix “E”) are how the WTRU 652 may, over the CP, request service IP address, marking descriptor and / or proxy information (which may be used in steps “F” in FIG. 7) to establish the 6PS session. Section “E” steps may be useful to get request service IP address, marking descriptor and / or proxy information, in systems where these lEs are not available through other means. For example, in a system where the AR 654 includes an IP router functionality, the WTRU 652 may obtain its service IP address and proxy information in steps C, and receive marking descriptors in steps F.709 and / or F.712 of FIG. 7. In another example, in another system where the AR 654 includes an IP router functionality, the WTRU 652 may obtain its service IP address in steps C, proxy information and marking descriptors in steps B. In another example, in yet another system where the AR 654 includes an IP router functionality, the WTRU 652 may obtain its service IP address in steps C, proxy information in steps B and marking descriptors in steps F.719 and / or F.712 of FIG. 7.
[0242] In step E.641, the WTRU 652 sends to the eSMF 668 (e.g., through the AMF 666) a CP 6PS establishment request message including 6PS parameters (e.g., based on lEs such as DNN and others from the selected eURSP rule). The AMF 666 may select the eSMF 668 to forward the message to, based on 6PS parameters (e.g., based on DNN, S-NSSAI). In step E. 642, the eSMF 668 selects an ePCF 672 for the 6PS session, which may be the same as or different than the ePCF 672 for the WTRU 652. The eSMF 668 requests and receives, from the ePCF 672, PCC rules for the 6PS session.
[0243] In step E. 643, the eSMF 668 selects an eUPF 670 for the 6PS session, based on the 6PS parameters, for example based on the DNN and / or S-NSSAI and / or PDU set support and / or other 6PS parameters. The eSMF 668may generate a service IP address for the WTRU 652, and / or an end-to-end IP address for the WTRU 652. The eSMF 668 may send an N4 session request message to the eUPF 670, including 6PS parameters, to request the eUPF 670 to create a MASQUE-P proxy instance for the 6PS session. The eUPF 670 may send an N4 session response message to the eSMF 668, including proxy information. In an example, the eSMF 668 may generate proxy information and provide it to the eUPF 670 in the request. In step E. 644, the eSMF 668 sends a CP 6PS establishment response message to the WTRU 652 (e.g., through the AMF 666). The response message may include a service IP address, a marking descriptor, and / or proxy information. In an example, the response message may also include an eSMF ID (e.g., an FQDN) that the WTRU 652 may provide to the eUPF 670 in step F.702 of FIG. 7.
[0244] FIG. 7 is a flow diagram illustrating an example registration procedure 700 for a WTRU 752 to register to the network and establish a 6PS session (part 2 of 2). The system performing the example registration procedure 700 may include: WTRU 752; AR 754 (or RAN, or RAN node, or base station); CN 765; AMF 766; eSMF 768 (or SMF); eUPF 770 (or UPF); ePCF 772 (or PCF); and endpoint 774. These entities may corresponding to the equivalent entities in FIG. 6.
[0245] The steps in section "F" (with prefix “F”) are how the WTRU 752 triggers the establishment of a 6PS session. In step F.701, the WTRU 752 selects a set of characteristics for the establishment of a 6PS session, including one or more of the following characteristics: proxy information; one or more WTRU service IP addresses; a CONNECT protocol; an existing MASQUE-P connection; and / or a marking descriptor. Proxy information may be used to determine the eUPF 770 proxy for the MASQUE-P connection of the 6PS session. One or more WTRU service IP addresses may be used to determine the source IP address of the WTRU 752 for the MASQUE-P connection of the 6PS session. Several WTRU service IP addresses may be used for a multi-access 6PS session. A single WTRU service IP address may be used for a single access 6PS session. The WTRU 752 may include / indicate a CONNECT protocol in the CONNECT request message to create the CONNECT stream to carry the SDF. The CONNECT protocol may be, for example, connect-udp, connect-tcp, connect-ethernet, or connect-ip. The CONNECT protocol may be determined by the WTRU 752 based on the SDF protocol (e.g., connect-udp for a UDP flow), and / or based on a WTRU policy provided by the network (e.g., a CONNECT protocol field in the selected eURSP rule). An existing MASQUE-P connection may match characteristics and 6PS parameters of the 6PS session (e.g., same DNN, same N-SSAI, same or some common markings, same proxy information, support for PDU sets, and / or other 6PS parameters). A marking descriptor may indicate how the WTRU 752 should mark outgoing MASQUE-P packets that hold PDUs of the SDF.
[0246] In step F.702, the WTRU 752 establishes a MASQUE-P connection (e.g., an HTTP connection) with the eUPF 770 identified by the proxy information, and the WTRU 752 sends to the eUPF 770 a 6PS request message including 6PS parameters. In an example, the request message may include an eSMF ID (e.g., in systems where steps E from FIG. 6 are used, in which case the eSMF 768 may provide its eSMF ID to the WTRU 752 in the message E.644 in FIG 6). For example, the 6PS request message may be an HTTP POST message. If the WTRU 752 determines to use an existing MASQUE-P connection, the WTRU 752 may select the existing MASQUE-P connection and directly send an HTTP CONNECT request (step F.710), skipping steps F.702 to F.709.
[0247] In an example, the message F.702 may be an HTTP POST or PUT message, which may be used to create an HTTP resource on the eUPF 770, which corresponds to the PDU session. In another example, the message F.702IDC-2025P00305WQis an HTTP CONNECT request message, and in this case steps F.710 and F.702 are performed concurrently based on a single HTTP CONNECT message, and steps F.712 and F.709 also correspond to the same response message.
[0248] In step F.703, the eUPF 770 selects an eSMF 768 for the 6PS session. The selection may be based on the eSMF ID from step F.702, if provided. The eUPF 770 may request an eSMF 768 to be selected by another CN node (e.g., NRF, not shown) and provide 6PS parameters to the other CN node to enable the selection. The selection of eSMF 768 by the CN node may be based on eSMF characteristics (e.g., an eSMF 768 may be configured with capabilities to handle 6PS sessions of a certain kind, such as for CP-over-UP, certain DNNs, or WTRUs with certain WTRU capabilities; the eSMF 768 may provide eSMF capabilities to the NRF, which may select the eSMF 768 based on 6PS parameters and these eSMF capabilities).
[0249] Steps F.704-F.710 describe how eUPF 770, eSMF 768, and ePCF 772 retrieve policy rules, marking information, end-to-end IP address, traffic handling rules related to a 6PS session or SDF, and how the 6QS services related to the 6PS session or SDF are configured. Steps F.704-F.710 may be executed to configure a 6QS service for traffic over the 6PS session (here, after step F.703) or steps F.704-F.710 may be executed to configure a 6QS service for traffic over a CONNECT stream (after step F.711).
[0250] In step F.704, the eUPF 770 sends an N4 session request message to the selected eSMF 768, including 6PS parameters obtained earlier from the WTRU 752 (e.g., steps F.702 or F.710). Upon receiving the request, the eSMF 768 selects an ePCF 772 for the 6PS session, which may be the same as or different than the ePCF 772 for the WTRU 752. In step F.705, the eSMF 768 sends an (e.g., SM) Policy Control Update or Create request message. Upon receiving the request, the ePCF 772 retrieves the policy information (e.g., PCC rules) and the marking descriptor(s) related to the 6PS session or SDF. In step F.706, based on the policy information, the ePCF 772 determines if some 6QS service(s) required for the 6PS session or SDF are activated (e.g., by obtaining the 6QS service activation indication from the UDM, not shown). If needed, the ePCF 772 configures the 6QS service(s) as described in steps A.606-A.610 in FIG. 6. In an example, the eSMF 768 may (e.g., instead of the ePCF 772), for after step F.707, determine if some 6QS service(s) are required for the 6PS session or SDF and configure the 6QS service(s).
[0251] In step F.707, the ePCF 772 sends a Policy Control response message including the marking descriptor to the eSMF 768. The response message may include PCC rules, for example to enable the eSMF 768 to configure the eUPF 770. The response message may include QoS information (e.g., to enable the eSMF 768 to configure 6QS services(s)).
[0252] In step F.708, the eSMF 768 sends an N4 session response message to the eUPF 770, including the marking descriptor, end-to-end IP address, and / or traffic handling rules such as forwarding action rule (FAR) and packet detection rule (PDR). For example, PDR and FAR may be based on PCC rules received from the ePCF 772. Upon receiving the response message, the eUPF 770 configures its traffic handling based on the rules (e.g., FAR and PDR). The traffic handling includes forwarding PDUs from and to the MASQUE-P connection or from and to a specific CONNECT stream of the MASQUE-P connection. The traffic handling may include additional operations, such as forwarding to and from a tunnel over N6, counting traffic volume, identifying PDU set information, including PDU set information in MASQUE-P headers, including PDU set information in MASQUE-U, GTP-U, or SRv6 header, etc.
[0253] In step F.709, the eUPF 770 sends a 6PS response message, for example an HTTP response indicating success or failure of the 6PS session establishment. The response may include a marking descriptor, which indicates to the WTRU 752 how to mark UL packets including UL PDUs over this MASQUE-P connection. The response may include an end-to-end IP address, which indicates to the WTRU 752 which source IP address to use when sending IP PDUs over the MASQUE-P connection. The marking descriptor and end-to-end IP address may alternatively be provided using approaches described herein.
[0254] In step F.710, the WTRU 752 sends, to the eUPF 770, an HTTP CONNECT request message including 6PS parameters, to request a CONNECT stream to forward the SDF. One of the 6PS parameters may be a description of the SDF. For example, for a connect-udp stream, the request may include the IP address and UDP port of a remote endpoint on an AS. For example, for a connect-ip stream, the request may include an IP subnetwork identifying the allowed target IP addresses for the connection. For example, the CONNECT message may include a description of the SDF parameters in HTTP headers (e.g., application ID, traffic flow 5-tuple). In step F.711, similar to steps F.704-F.708, the eUPF 770, eSMF 768 and ePCF 772 retrieve policy rules, marking information, end-to-end IP address, traffic handling rules related to the SDF, and the ePCF 772 / eSMF 768 may configure 6QS service(s) required for the SDF.
[0255] In step F.712, the eUPF 770 sends an HTTP response message indicating success or failure of the CONNECT request message. The response may include a marking descriptor, which indicates to the WTRU 752 how to mark UL packets including UL PDUs over this CONNECT stream. The response may include an end-to-end IP address, which indicates to the WTRU 752 which source IP address to use when sending IP PDUs over the MASQUE-P connection. The marking descriptor and end-to-end IP address may alternatively be provided using different means described herein. In steps F.713 to F.716, the WTRU 752 may request an end-to-end IP address that it may use as source IP address for PDUs within a CONNECT stream of type connect-ip, by sending an ADDRESS_REQUEST to the eUPF 770. The eUPF 770 may request an end-to-end IP address from the eSMF 768. The eSMF 768 may select an end-to-end WTRU IP address and send it to the eUPF 770. The eUPF 770 may send the end-to-end WTRU IP address to the WTRU 752 in an ADDRESS_ASSIGN message.
[0256] The steps in section "G" (with prefix “G”) are for the transmission of a UL PDU over the established CONNECT stream. In step G.721, the WTRU 752 sends an UL PDU in CONNECT stream, and marks the IP packet (e.g., marks the DSCP field of the IP header of the MASQUE-P packet that includes the UL PDU). The WTRU 752 sends the IP packet down the IP stack. A lower layer component of the WTRU 752 (e.g., in the MT component of the WTRU) applies QoS treatment based on the marking. For example, the WTRU 752 transmits the IP packet over a Data Radio Bearer selected based on the IP packet marking. In step G.722, the WTRU 752 transmits the UL PDU over the CONNECT stream (with marking applied on the IP packet). In step G.723, the eUPF 770 receives the UL PDU from the WTRU 752, and forwards it to the end-to-end connection remote endpoint 774 (e.g., and AS or remote WTRU, not shown).
[0257] The steps in section "H" (with prefix “H”) are for the transmission of a DL PDU over the established CONNECT stream established. In step H.731, the remote endpoint 774 sends a DL PDU to the WTRU 752, through the eUPF 770 (e.g., if the DL PDU is an IP PDU, the DL PDU may be routed through the data network, towards theIDC-2025P00305WCeUPF 770). In step H.732, the eUPF 770 forwards the DL PDU over the CONNECT stream corresponding to the SDF (e.g., in an IP packet that includes a CONNECT stream header and the DL PDU or the payload of the DL PDU). For example, the eUPF 770 may determine that the DL PDU matches a PDR rule, and the corresponding FAR rule indicates to forward the DL PDU over the CONNECT stream. The eUPF 770 marks the IP packet including the DL PDU, based on the marking descriptor associated with the CONNECT stream or 6PS session. In step H.733, the AR 754 receives the IP packet including the DL PDU. The AR 754 matches the IP packet against the configured marking filters, until a matching marking filter is selected. The AR 754 applies the QoS treatment associated with the matching marking filter. For example, the AR 754 (RAN) transmits the IP packet over a Data Radio Bearer selected based on the IP packet marking. In step H.734, the AR 754 forwards the IP packet including the DL PDU, to the WTRU 752.
[0258] FIG. 8 is a flow diagram illustrating an example configuration procedure 800 for the network to configure the WTRU 852 with service IP address and proxy information. The system performing the example configuration procedure 800 may include: WTRU 852; AR 854 (or RAN, or RAN node, or base station); CN 865; AMF 866; eSMF 868 (or SMF); eUPF 870 (or UPF); and ePCF 872 (or PCF). In step C.801, the network operator configures the AR 854 with IP addresses, as described herein. Some IP addresses may correspond to certain slices (e.g., identified by S-NSSAI). Step C.801 may occur earlier, for during a network management operation, and / or before the WTRU 852 attaches to the network.
[0259] A prerequisite for steps C.802 and subsequent steps may be that the WTRU 852 is connected to the mobile network through an AR 854 (i.e., a RAN node including an IP router functionality). The WTRU 852 is registered with the network, and a communication channel (e.g., a Data Radio Bearer) is established for exchanging IP traffic between the AR, as described herein. In step C.802, the ePCF 872 (e.g., the ePCF for the WTRU 852, selected by the AMF 866 when the WTRU 852 registers with the network) determines proxy information for the WTRU 852. For example, the ePCF 872 may retrieve the network services that are available to the WTRU 852, based on PCC rules. Some network services may correspond to different network slices (e.g., XR services may be provided over a network slice dedicated to XR services, identified by an S-NSSAI). The ePCF 872 creates proxy information for each available network service.
[0260] In step C.803, the ePCF 872 sends an AR configuration request including a WTRU ID (e.g., SUPI) and the determined proxy information. In step C.804, the AR 854 configures the received proxy information for the WTRU 852, for example in PvD descriptors that correspond to PvD IDs, where the PvD IDs are associated with an AR IP address related to the network slice appropriate for the network service provided through the proxy information. In step C.805, the AR 854 sends a configuration response message to the ePCF 872, indicating success of the operation. In step C.806, once the WTRU 852 attaches to the AR 854, the AR 854 sends a Router Advertisement message to the WTRU 852 (e.g., over the air interface, step C.807). The Router Advertisement includes the PvD IDs configured in earlier steps. The WTRU 852 uses information inside the Router Advertisement to configure a service IP address (e.g., using SLAAC).
[0261] In steps C.807-C808, the WTRU 852 retrieves the PvD descriptor corresponding to a PvD ID from the Router Advertisement, for example by sending an HTTP GET request message to a URL including the PvD ID, and receiving, from the HTTP server, an HTTP response message including the proxy information. As an alternative toIDC-2025P00305WQsteps C.802-C.805 and C.807-C.808, the WTRU 852 may receive the proxy information in an enhanced URSP rule, or the WTRU 852 may request the proxy information from the network, as described herein. In such cases, the WTRU 852 uses the Router Advertisement (C.806) to configure a service IP address but may not need to retrieve proxy information using PvDs.
[0262] FIG. 9 is a flow diagram illustrating an example procedure 900 performed by a WTRU for network registration, proxy information discovery, and PDU session establishment and operation (e.g., for a 6G PDU session). In step 902, the WTRU may receive, from a first network node including an access router (AR), a router advertisement message. In step 904, the WTRU may configure, based on the received router advertisement message, a service Internet protocol (IP) address of the WTRU. In step 906, the WTRU may receive, from a second network node, policy information including proxy information describing proxies that can be used to establish a protocol data unit (PDU) session. In step 908, the WTRU may select an enhanced user plane function (eUPF) based on the proxy information.
[0263] In step 910, the WTRU may send, to a third network node including the selected eUPF, a Hypertext Transfer Protocol (HTTP) connect request message to create a connect stream, wherein the HTTP connect request message is a user plane (UP) message including PDU session parameters and the service IP address of the WTRU as a source IP address. In step 912, the WTRU may receive, from the third network node including the selected eUPF, an HTTP response message indicating creation of the connect stream, wherein the HTTP response message includes a first marking descriptor indicating how to mark packets of the connect stream. In step 914, the WTRU may generate an IP packet including an uplink (UL) PDU over the connect stream, wherein the IP packet has a marking based on the first marking descriptor. In step 916, the WTRU may send, to a base station, the IP packet using a quality of service (QoS) treatment based on the IP packet marking.
[0264] Further to the steps above, the PDU session may be a sixth generation (6G) PDU session. The WTRU may send, to the third network node including the selected eUPF, a PDU session request message including PDU session parameters, wherein the PDU session request message is a UP message and includes the service IP address of the WTRU as a source IP address. The PDU session request message may include an indication that the PDU session is for sending CP messages over a UP. The PDUs over the connect stream may be CP messages between the WTRU and a core network node. The WTRU may select the eUPF based on a subset of the proxy information corresponding to proxies that are indicated as sending control plane (CP) messages over a UP. The WTRU may receive, from the first network node including the AR, a QoS service configuration request message including at least one of: QoS information; marking filter information; or data radio bearer configuration information. The WTRU may configure, based on the QoS service configuration request message, the QoS treatment and one or more packet filters associated with the QoS treatment.
[0265] The policy information includes marking descriptors. The WTRU may determine the first marking descriptor based on the policy information. The WTRU may receive, from the third network node including the selected eUPF, a PDU session response message including a second marking descriptor indicating how to mark packets of a multiplexed application substrate over quick user datagram protocol (UDP) internet connection (QUIC) encryption PDU (MASQUE-P) session. The IP packet including the UL PDU over the connect stream may be received from an application running on the WTRU or running on a device connected to the WTRU. The IP packet may have a markingIDC-2025P00305WQbased on the first marking descriptor. The WTRU may send, to the first network node including the AR, a registration message, and the registration message may include one or more of: indication of support for IP connectivity from the AR; indication of support for proxy information discovery from the AR; indication of support for UP tunnel; or indication of support for control plane (CP) messages over a UP.
[0266] The mechanisms and procedures described herein decouples RAN resources reservation (with 6G QoS service configuration requests) from CN resources reservation (with 6G PDU establishment requests and CONNECT requests), which reduces system complexity. For example, the mechanisms and procedures described herein reduce CP signaling and leverage the QUIC protocol (and QUIC proxying, MASQUE) to perform operations over the user plane. For example, the mechanisms and procedures described herein enable WTRUs to dynamically adapt the QoS treatment of an SDF with limited impact on CP signaling, by dynamically adapting the marking of IP packets that carry PDUs.
[0267] The mechanisms and procedures described herein provide a user plane mechanism to connect network slices to the WTRU, based on different virtual IP routers in the AR, which the WTRU may use to access services in different network slices without knowing network slices identities. For example, the WTRU may configure itself with multiple WTRU service IP addresses based on different Router Advertisement messages from the AR. The multiple WTRU service IP addresses may be used as source addresses to access different services deployed in different slices. The mechanisms and procedures described herein enable the WTRU, or a WTRU application, to use an SBI to the CN nodes (e.g., to send CP messages to the CN nodes) over a MASQUE-P connection between the WTRU and a CN-eUPF connected to the CN.
[0268] The mechanisms and procedures described herein enable the WTRU and UPF to exchange control messages and per-PDU metadata over the MASQUE-P connection. Furthermore, the mechanisms and procedures described herein enable a WTRU application to establish a 6PS session, which enables an individual WTRU application to dynamically adapt its QoS based on application logic, exchange control messages and per-PDU metadata with the UPF and communicate with CN nodes.
[0269] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
Claims
IDC-2025P00305WCCLAIMSWhat is Claimed:
1. A wireless transmit / receive unit (WTRU) comprising:a transceiver; anda processor, wherein the transceiver and the processor are configured to:receive, from a first network node, policy information including proxy information describing proxies that can be used to establish a protocol data unit (PDU) session;select an enhanced user plane function (eUPF) based on the proxy information;send, to a second network node including the selected eUPF, a Hypertext Transfer Protocol (HTTP) connect request message to create a connect stream, wherein the HTTP connect request message is a user plane (UP) message including PDU session parameters and a service Internet protocol (IP) address of the WTRU as a source IP address;receive, from the second network node including the selected eUPF, an HTTP response message indicating creation of the connect stream, wherein the HTTP response message includes a first marking descriptor indicating how to mark packets of the connect stream;generate an IP packet including an uplink (UL) PDU over the connect stream, wherein the IP packet has a marking based on the first marking descriptor; andsend, to a base station, the IP packet using a quality of service (QoS) treatment based on the IP packet marking.
2. The WTRU of claim 1, wherein the PDU session is associated with a sixth generation (6G) system.
3. The WTRU of claim 1 , wherein the transceiver and the processor are further configured to:send, to the second network node including the selected eUPF, a PDU session request message including PDU session parameters, wherein the PDU session request message is a UP message and includes the service IP address of the WTRU as a source IP address.
4. The WTRU of claim 3, wherein the PDU session request message includes an indication that the PDU session is for sending control plane (CP) messages over a UP, and wherein the PDUs over the connect stream are CP messages between the WTRU and a core network node.
5. The WTRU of claim 1, wherein the transceiver and the processor are configured to select the eUPF based on a subset of the proxy information corresponding to proxies that are indicated as sending control plane (CP) messages over a UP.
6. The WTRU of claim 1 , wherein the transceiver and the processor are further configured to:IDC-2025P00305WQreceive, from a third network node including an access router (AR), a QoS service configuration request message including at least one of: QoS information; marking filter information; or data radio bearer configuration information; andconfigure, based on the QoS service configuration request message, the QoS treatment and one or more packet filters associated with the QoS treatment.
7. The WTRU of claim 1 , wherein the transceiver and the processor are further configured to:receive, from a third network node including an access router (AR), a router advertisement message; and configure, based on the received router advertisement message, the service IP address of the WTRU.
8. The WTRU of claim 1 , wherein the transceiver and the processor are further configured to:receive, from the second network node including the selected eUPF, a PDU session response message including a second marking descriptor indicating how to mark packets of a multiplexed application substrate over quick user datagram protocol (UDP) internet connection (QUIC) encryption PDU (MASQUE-P) session.
9. The WTRU of claim 1 , wherein the IP packet including the UL PDU over the connect stream is received from an application running on the WTRU or running on a device connected to the WTRU.
10. The WTRU of claim 1, wherein the transceiver and the processor are further configured to:send, to the first network node including the AR, a registration message, and wherein the registration message includes one or more of: indication of support for IP connectivity from the AR; indication of support for proxy information discovery from the AR; indication of support for UP tunnel; or indication of support for control plane (CP) messages over a UP.
11. A method performed by a wireless transmit / receive unit (WTRU), the method comprising:receiving, from a first network node, policy information including proxy information describing proxies that can be used to establish a protocol data unit (PDU) session;selecting an enhanced user plane function (eUPF) based on the proxy information;sending, to a second network node including the selected eUPF, a Hypertext Transfer Protocol (HTTP) connect request message to create a connect stream, wherein the HTTP connect request message is a user plane (UP) message including PDU session parameters and a service Internet protocol (IP) address of the WTRU as a source IP address;receiving, from the second network node including the selected eUPF, an HTTP response message indicating creation of the connect stream, wherein the HTTP response message includes a first marking descriptor indicating how to mark packets of the connect stream;generating an IP packet including an uplink (UL) PDU over the connect stream, wherein the IP packet has a marking based on the first marking descriptor; andIDC-2025P00305WQsending, to a base station, the IP packet using a quality of service (QoS) treatment based on the IP packet marking.
12. The method of claim 11, wherein the PDU session is associated with a sixth generation (6G) PDU system.
13. The method of claim 11, further comprising:sending, to the second network node including the selected eUPF, a PDU session request message including PDU session parameters, wherein the PDU session request message is a UP message and includes the service IP address of the WTRU as a source IP address.
14. The method of claim 13, wherein the PDU session request message includes an indication that the PDU session is for sending control plane (CP) messages over a UP, and wherein the PDUs over the connect stream are CP messages between the WTRU and a core network node.
15. The method of claim 11, wherein the selecting the eUPF is based on a subset of the proxy information corresponding to proxies that are indicated as sending control plane (CP) messages over a UP.
16. The method of claim 11, further comprising:receiving, from a third network node including an access router (AR), a QoS service configuration request message including at least one of: QoS information; marking filter information; or data radio bearer configuration information; andconfiguring, based on the QoS service configuration request message, the QoS treatment and one or more packet filters associated with the QoS treatment.
17. The method of claim 11, further comprising:receiving, from a third network node including an access router (AR), a router advertisement message; and configuring, based on the received router advertisement message, the service IP address of the WTRU.
18. The method of claim 11, further comprising:receiving, from the second network node including the selected eUPF, a PDU session response message including a second marking descriptor indicating how to mark packets of a multiplexed application substrate over quick user datagram protocol (UDP) internet connection (QUIC) encryption PDU (MASQUE-P) session.
19. The method of claim 11, wherein the IP packet including the UL PDU over the connect stream is received from an application running on the WTRU or running on a device connected to the WTRU.
20. The method of claim 11 , wherein further comprising:IDC-2025P00305WCsending, to the first network node including the AR, a registration message, and wherein the registration message includes one or more of: indication of support for IP connectivity from the AR; indication of support for proxy information discovery from the AR; indication of support for UP tunnel; or indication of support for control plane (CP) messages over a UP.
