Supporting packet data unit set based handling over non-3GPP access

Abstract

Methods, apparatuses, and computer-readable storage media enable non-3GPP access nodes and WTRUs to be configured to support PDU Set based QoS handling and detection of end of data bursts for a WTRU's downlink and uplink traffic. For uplink, the WTRU may be configured with rules indicating how to map PDU Set importance information and end of burst information to DSCP values. The WTRU may use DSCP markings to determine how to prioritization packets when transmitting over a non-3GPP access. For downlink, non-3GPP access nodes may be configured with rules on how to map PDU Set information. The non-3GPP access node may send the PDU to the WTRU in an IPSec tunnel that is associated with a QoS Flow, along with the marked (e.g., mapped) DSCP values in the IP packets that carries the PDUs.

Description

SUPPORTING PACKET DATA UNIT SET BASED HANDLING OVER NON- 3GPP ACCESSCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application Number 63 / 552,477, filed February 12, 2024, which is hereby incorporated herein by reference in its entirety.BACKGROUND

[0002] A user equipment (UE), also referred to as a wireless transmit / receive unit (WTRU), may be connected to a 5G (fifth generation) system or network via a non-3GPP (third generation partnership project) access system or network. In this scenario, some 5G functions may not be supported.SUMMARY

[0003] Network nodes and WTRUs may be configured to support various 5G functions.Procedures described herein may enable network devices, such as non-3GPP access nodes and WTRUs to be configured to support PDU (packet data unit) Set based QoS (quality of service) handling and detection of end of data bursts for a WTRU’s downlink and uplink traffic. An example network device may include a non-3GPP access node, a N3IWF (Non-3GPP Interworking Function), a TNGF (Trusted Non-3GPP Gateway Function), a W-AGF (Wireline Access Gateway Function), or the like, or any appropriate combination thereof.

[0004] 5G-based apparatuses and processes as described herein, may enable network devices (e.g., non-3GPP access nodes) to be configured to provide PDU Set based QoS handling and detection of end of data bursts for a WTRU’s downlink traffic. Augmenting the 5G system to provide PDU Set based QoS handling and detection of end of data bursts for a WTRU’s downlink traffic may result in improved user experience when the WTRU is connected to thenetwork via a non-3GPP access, may result in improved allocation of network resources, and may result in decreased WTRU power consumption.

[0005] For uplink traffic, a WTRU may be configured with rules indicating how to map PDU Set Importance information and end of burst information to DSCP (Differentiated Services Code Point) Values. The WTRU may use DSCP markings to determine how to prioritize packets when transmitting the packets over a non-3GPP access node. The DSCP markings also may be used by network nodes (e.g., routers, access points, or the like) to determine how to prioritize the packets.

[0006] For downlink traffic, network devices (e.g., non-3GPP access nodes) may be configured with rules about how to map PDU Set information, such as, PDU Set Importance Information and / or the End of Burst Indication, that is received in the GTP-U (general packet radio service tunnelling protocol user plane) header over the N3 (non-3GPP) interface, to corresponding DSCP values. The network device may send the PDU to the WTRU in an IPSec (internet protocol security) tunnel that is associated with the QoS Flow, along with the marked DSCP values in the IP packets that carries the PDUs. The DSCP markings may be used by network nodes (e.g. routers, access points, or the like) to determine how to prioritization the packets.

[0007] As described herein, a network device may comprise an N3IWF, a TNGF, a W-AGF, or the like, which may be referred to herein as non-3GPP access nodes.

[0008] An example method performed by a WTRU may comprise sending a packet data unit (PDU) session establishment request message to a session management function (SMF). The method may comprise receiving a message, wherein the message comprises an indication regarding how to map a quality of service flow identifier (QFI) to a security association, and wherein the message may comprise an indication of a mapping rule regarding how to map PDU set importance information to a differentiated services code point (DSCP) value. The method may comprise receiving a packet for transmission. The method may comprise determining a QFI that is associated with the packet. The method may comprise determining a DSCP marking for the packet, wherein the determination may be based on the mapping rule. And the method may comprise transmitting the packet on a Wi-Fi link. The PDU session establishment request message from the WTRU may be forwarded to the SMF by one of a non-3GPP interworkingfunction (N3IWF) or a trusted non-3GPP gateway function (TNGF). The PDU session establishment request message may comprise an indication that the WTRU supports PDU set handling over non-3GPP access. The mapping rule may comprise an indication regarding how to map end of burst information to a DSCP value. The PDU session establishment request message may comprise an indication of a protocol type to be used to for determining the PDU set importance information. The PDU session establishment request message may comprise an indication of a protocol type to be used to for determining end of burst information.

[0009] An example WTRU may comprise a transceiver and a processor. The processor may be configured to send, via the transceiver, a packet data unit (PDU) session establishment request message to a session management function (SMF). The processor may be configured to receive, via the transceiver, a message, wherein the message comprises an indication regarding how to map a quality of service flow identifier (QFI) to a security association, and wherein the message comprises an indication of a mapping rule regarding how to map PDU set importance information to a differentiated services code point (DSCP) value. The processor may be configured to receive, via the transceiver, a packet for transmission. The processor may be configured to determine a QFI that is associated with the packet. The processor may be configured to determine a DSCP marking for the packet, wherein the determination may be based on the mapping rule. And the processor may be configured to transmit, via the transceiver, the packet on a Wi-Fi link. The PDU session establishment request message from the WTRU may be forwarded to the SMF by one of a non-3GPP interworking function (N3IWF) or a trusted non-3GPP gateway function (TNGF). The PDU session establishment request message may comprise an indication that the WTRU supports PDU set handling over non-3GPP access. The mapping rule may comprise an indication regarding how to map end of burst information to a DSCP value. The PDU session establishment request message may comprise an indication of a protocol type to be used to for determining the PDU set importance information. The PDU session establishment request message may comprise an indication of a protocol type to be used to for determining end of burst information.

[0010] An example non-transitory computer-readable storage medium may comprise executable instructions for configuring at least one processor to send a packet data unit (PDU) session establishment request message to a session management function (SMF). The executableinstructions may configure the processor to receive a message, wherein the message comprises an indication regarding how to map a quality of service flow identifier (QFI) to a security association, and wherein the message comprises an indication of a mapping rule regarding how to map PDU set importance information to a differentiated services code point (DSCP) value. The processor may be configured to receive a packet for transmission. The executable instructions may configure the processor to determine a QFI that is associated with the packet. The processor may be configured to determine a DSCP marking for the packet, wherein the determination may be based on the mapping rule. And the executable instructions may configure the processor to transmit the packet on a Wi-Fi link. The PDU session establishment request message from the WTRU may be forwarded to the SMF by one of a non-3GPP interworking function (N3IWF) or a trusted non-3GPP gateway function (TNGF). The PDU session establishment request message may comprise an indication that the WTRU supports PDU set handling over non-3GPP access. The mapping rule may comprise an indication regarding how to map end of burst information to a DSCP value. The PDU session establishment request message may comprise an indication of a protocol type to be used to for determining the PDU set importance information. The PDU session establishment request message may comprise an indication of a protocol type to be used to for determining end of burst information.

[0011] An example network device may comprise a processor. The processor may be configured to receive a PDU comprising a GTP-U header. The GTP-U header may comprise PDU set importance information associated with the PDU. The processor may be configured to determine a DSCP value for the PDU based on the mapping rules and the PDU set importance information from the GTP-U header. The mapping rules may comprise an indication regarding how to map PDU set importance information to DSCP values. The processor may be configured to determine an IPSec tunnel for transmitting the PDU. The processor may be configured to send, via the IPSec tunnel, the PDU in an IP packet marked with the determined DSCP value for the PDU.

[0012] The GTP-U header may comprise end of burst information. The mapping rules may comprise an indication regarding how to map the end of burst information to DSCP values. The determined DSCP value may be based on the PDU set importance information and the end of burst information.

[0013] The mapping rules may comprise rules regarding how to map PDU set quality of service (QoS) parameters to DSCP values. An outer header of the IP packet may be marked with the determined DSCP value. The network device may comprise a non-3GPP interworking function (N3IWF). The network device may comprise a trusted non-3GPP gateway function (TNGF). The network device may comprise a wireline access gateway function (W-AGF). The PDU in the IP packet marked with the mapped DSCP value may be sent, via the IPSec tunnel, to a WTRU.

[0014] An example method performed by a network device may comprise receiving a PDU comprising a GTP-U header. The GTP-U header may comprise PDU set importance information associated with the PDU. The method may comprise determining a DSCP value for the PDU based on the mapping rules and the PDU set importance information from the GTP-U header. The mapping information may comprise an indication regarding how to map PDU set importance information to DSCP values. The method may comprise determining an IPSec tunnel for transmitting the PDU. The method may comprise sending, via the IPSec tunnel, the PDU in an IP packet marked with the determined DSCP value for the PDU.

[0015] The GTP-U header may comprise end of burst information. The mapping rules may comprise an indication regarding how to map the end of burst information to DSCP values. The determined DSCP value may be based on the PDU set importance information and the end of burst information.

[0016] The mapping rules may comprise rules regarding how to map PDU set quality of service (QoS) parameters to DSCP values. An outer header of the IP packet may be marked with the determined DSCP value. The network device may comprise a non-3GPP interworking function (N3IWF). The network device may comprise a trusted non-3GPP gateway function (TNGF). The network device may comprise a wireline access gateway function (W-AGF). The PDU in the IP packet marked with the mapped DSCP value may be sent, via the IPSec tunnel, to a WTRU.

[0017] An example non-transitory computer-readable storage medium may comprise executable instructions for configuring at least one processor to receive a PDU comprising a GTP-U header. The GTP-U header may comprise PDU set importance information associated with the PDU. The executable instructions may configure the processor to determine a DSCP value for the PDU based on the mapping rules and the PDU set importance information from theGTP-U header. The mapping rules may comprise an indication regarding how to map PDU set importance information to DSCP values. The executable instructions may configure the processor to determine an IPSec tunnel for transmitting the PDU. The executable instructions may configure the processor to send, via the IPSec tunnel, the PDU in an IP packet marked with the determined DSCP value for the PDU.

[0018] The GTP-U header may comprise end of burst information. The mapping rules may comprise an indication regarding how to map the end of burst information to DSCP values. The determined DSCP value may be based on the PDU set importance information and the end of burst information.

[0019] The mapping rules may comprise rules regarding how to map PDU set quality of service (QoS) parameters to DSCP values. An outer header of the IP packet may be marked with the determined DSCP value. The network device may comprise a non-3GPP interworking function (N3IWF). The network device may comprise a trusted non-3GPP gateway function (TNGF). The network device may comprise a wireline access gateway function (W-AGF). The PDU in the IP packet marked with the mapped DSCP value may be sent, via the IPSec tunnel, to a WTRU.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] FIG. IB is an example system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.

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

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

[0024] FIG. 2 depicts an example process for enabling PDU set based QoS handling on downlink traffic when a WTRU uses non-3GPP access to access a 5G system.

[0025] FIG. 3 depicts an example process for enabling PDU set based QoS handling on uplink traffic when a WTRU uses non-3GPP access to access a 5G system.EXAMPLE NETWORKS FOR IMPLEMENTATION OF THE INVENTION

[0026] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multi carrier (FBMC), and the like.

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

[0028] 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 / 115, 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 Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a 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.

[0029] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. 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.

[0030] 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 communicationlink (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).

[0031] 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 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 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 UL Packet Access (HSUPA).

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

[0033] 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 New Radio (NR).

[0034] 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., a eNB and a gNB).

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

[0036] The base station 114b in FIG. 1 A 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. 1 A, 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 / 115.

[0037] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have 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 / 115 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 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0038] The CN 106 / 115 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 / 113 or a different RAT.

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

[0040] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a di splay / 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.

[0041] 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) circuits, 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. Theprocessor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0043] Although the transmit / receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

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

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

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

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

[0048] 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 temperaturesensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0049] 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 downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit 139 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 half-duplex 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 downlink (e.g., for reception)).

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

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

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

[0053] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Whileeach of 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.

[0054] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an SI 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 attachment 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.

[0055] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the SI 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.

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

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

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

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

[0060] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.1 le DLS or an 802.1 Iz 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.

[0061] When using the 802.1 lac 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 via signaling. 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.

[0062] 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 nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0063] Very High Throughput (VHT) STAs may support 20 MHz, 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).

[0064] Sub 1 GHz modes of operation are supported by 802.1 laf and 802.1 lah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in 802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.1 lah may support Meter Type Control / Machine-Type Communications, 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).

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

[0066] In the United States, the available frequency bands, which may be used by 802. 1 lah, 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.1 lah is 6 MHz to 26 MHz depending on the country code.

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

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

[0069] 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 / ordifferent 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 varying number of OFDM symbols and / or lasting varying lengths of absolute time).

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

[0071] 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 UE and / or DL, support of network slicing, dual connectivity, 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. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0072] The CN 115 shown in FIG. ID 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 each of the foregoing elements are depicted as part of theCN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0073] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 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 PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of 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 machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP (third generation partnership project) access technologies such as WiFi.

[0074] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an Ni l interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 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 downlink data notifications, and the like. A PDU session type may be IP -based, non-IP based, Ethernet -based, and the like.

[0075] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 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 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0076] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to 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 Data Network (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.

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

[0078] 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 may perform testing using over-the-air wireless communications.

[0079] 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 ormore 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.

[0080] Described herein are methods and apparatuses for supporting PDU set based handling over non-3GPP access. The procedures described herein may enable network devices, such as non-3GPP access nodes and WTRUs to be configured to support PDU Set based QoS handling and detection of end of data bursts for a WTRU’s downlink and uplink traffic. Examples of network devices may include an N31WF, a TNGF, and a W-AGF, or the like, or any appropriated combination thereof.

[0081] For uplink traffic a WTRU may be configured with rules indicating how to map PDU Set Importance information and end of burst information to a DSCP Value. The WTRU may use the DSCP marking to determine how to prioritization the packets when transmitting packets over a non-3GPP access. The DSCP markings may be used by network nodes (e.g. routers, access points, or the like) to determine how to prioritize the packets.

[0082] For downlink traffic a network device (e.g., non-3GPP access node) may be configured with rules on how to map PDU Set information, such as, PDU Set Importance Information and / or the End of Burst Indication, that is received in the GTP-U header over the N3 interface, to the corresponding DSCP value. The network device may send the PDU to the WTRU in an IPSec tunnel that is associated with the QoS Flow, along with the marked DSCP values in the IP packets that carries the PDUs. The DSCP markings may be used by network nodes (e.g. routers, access points, or the like) to determine how to prioritization the packets.

[0083] PDU sets are utilized in 5G systems. PDU Set QoS Parameters are used to support PDU Set based QoS handling in a NG-RAN (new generation-random access network). At least one PDU Set QoS Parameter may be sent to the NG-RAN to enable PDU Set based QoS handling. Example PDU Set QoS Parameters may include a PSDB (PDU Set Delay Budget), a PSER (PDU Set Error Rate), and a PSIHI (PDU Set Integrated Handling Information). For a given QoS Flow, the values of PSDB, PSER and PSIHI may differ for UL (uplink) and DL (downlink).

[0084] A QoS Profile may include the PDU Set QoS Parameters for UL and / or DL direction. A PCF (policy control function) may determine the PDU Set QoS Parameters based on information provided by an AF (application function) and / or local configuration. The PDU Set QoS parameters may be sent to an SMF (session management function) as part of PCC (policy and charging control) rule. The SMF may send PDU Set QoS parameters to a NG-RAN (new generation-radio access network) as part of the QoS Profile. The NG-RAN may enable PDU Set based QoS handling and may applies PDU Set QoS Parameters.

[0085] PDU Sets may be utilized in downlink transmissions. To support PDU Set based QoS handling, a PSA UPF (point of service user plane function) may identify PDUs that belong to PDU Sets. The PSA UPF may determine the PDU Set Information. The PSA UPF may send the PDU Set Information to the NG-RAN in the GTP-U header. The PDU Set information may be used by the NG-RAN for PDU Set based QoS handling.

[0086] PDU Set Information may comprise a PDU Set Sequence Number, an indication of End PDU of the PDU Set, a PDU Sequence Number within a PDU Set, a PDU Set Size (e.g., in bytes), a PDU Set Importance, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow, or the like, or any appropriate combination thereof.

[0087] The NG-RAN may use a Priority Level across QoS Flows and PDU Set Importance within a QoS Flow for PDU Set level packet discarding in presence of congestion. The PDU Set Information may be different for different PDU Sets within a QoS Flow. The SMF may instruct the PSA UPF to perform PDU Set marking and may provide the PSA UPF a Protocol Description used by the service data flow. The Protocol Description may be received in the PCC rule, based on information provided by the AF or by PCF local policies. The PSA UPF may identify the PDU Set Information using the Protocol Description and the received transport protocol headers and payload or using implementation-specific means.

[0088] For each DL PDU received on N6 (also referred to as N6-LAN, local area network, which is a domain positioned in a mobile network as an interface to the internet) for which PDU Set based QoS handling is indicated from the SMF, the PSA UPF may apply the rules for PDU Set identification and may provide the available PDU Set Information to the RAN in the GTP-Uheader. The PSA UPF may assign a unique PDU Set Sequence Number in the GTP-U header to each PDU Set of the QoS Flow.

[0089] Regarding PDU Set Based QoS Handling, an AF provided PDU Set QoS Parameters and Protocol Description may be used in determining the PCC Rule by the PCF. The Protocol Description may be used for identifying the PDU Set information by the PSA UPF. When the SMF receives the PCC rule, the SMF may perform binding of the PCC rule to a QoS Flow. If the PCC rule contains one or more PDU Set QoS Parameters (e.g., PSER, PSDB, PSIHI), the SMF may add these PDU Set QoS parameters to the QoS Profile of the QoS Flow. The SMF may be configured to support PDU Set based QoS Handling without receiving PCC rules from a PCF. For the downlink direction, the PSA UPF may identify PDUs that belong to PDU Sets and may mark them accordingly. If the PSA UPF receives a PDU that does not belong to a PDU Set based on Protocol Description for PDU Set identification, the PSA UPF may still map it to a PDU Set and may determine the PDU Set Information. For the uplink direction, the WTRU may identify PDU Sets. This may be accomplished according to any appropriate WTRU-based implementation. The SMF may send Protocol Description associated with the QoS rule to WTRU.

[0090] Regarding end of Data Burst Indication, an indication of End of Data Burst may be provided to the NG-RAN by the UPF, e.g., to configure WTRU power management schemes such as connected mode DRX (discontinuous reception), for example. Based on an End of Data Burst Marking Indication in a PCC rule and / or on local operator policies, the SMF may request the UPF to detect the last PDU of the data burst and mark the End of Data burst in the GTP-U header of the last PDU in downlink. The SMF may provide the PSA UPF the End of Data Burst Marking Indication and Protocol Description used by the service data flow. The Protocol Description may be received in the PCC rule, based on information provided by the AF or by PCF local policies. According to the request and information from the SMF, the UPF may identify the last PDU of a Data burst in the DL traffic based on the End indication according to the Protocol Description or UPF implementation and may provide an End of Data Burst indication to the NG-RAN over GTP-U of the last PDU of a Data burst. Some packets from the Data Burst may be received by NG-RAN after the PDU with End of Data Burst Indication if packets are received out of sequence.

[0091] Regarding QoS in the non-3GPP access networks, a TNGF (Trusted Non-3GPP Gateway Function) may send identities parameters to an AMF with N3 terminations supported, to be used for UPF selection. The AMF may send an N2 PDU Session Request message to N3IWF / TNGF to establish access resources for the PDU Session. This may include QoS related information, such as, for example, profiles, or a QFI (QoS flow identifier). Based on the received QoS profiles, the N3IWF / TNGF may determine the number of IPsec Child SAs (security associations) to establish and the QoS profiles associated with each IPsec Child SA (security association). The N3IWF / TNGF may send an WTRU an IKE (internet key exchange) Create Child SA request, to establish the first IPsec Child SA for the PDU Session. This request may include a 3GPP-specific Notify payload (including, for example, the QFI(s), the identity of the PDU Session, additional QoS Information, or any appropriate combination thereof). The N3IWF / TNGF may forward the PDU Session Establishment Response over the IPSec tunnel to WTRU. The N3IWF / TNGF may send to the AMF N2 the PDU Session Establishment Request. The WTRU may use the Additional QoS Information contained in this message to determine what QoS resources to reserve over the non-3GPP access.

[0092] Support for PDU Set mechanisms are described herein. The 5G system supports PDU Set based QoS handling in NG-RAN with the PSA UPF identifying PDUs that belong to PDU Sets based on Protocol Description for PDU Set identification and providing PDU Set Information to the RAN in the GTP-U header. 5GS support for PDU Set based handling is limited to NG-RAN access. However, the interaction between the application and 5GS via non- 3 GPP access may enhance efficiency and promote user experience. The user may be serviced by the 5GC via non-3GPP accesses such as trusted, untrusted, or wireline access, such as a device behind RG (residential gateway). To support PDU Set based QoS handling in the network device (UE / 5G-RG, N3IWF, TNGF, W-AGF), PDU Set QoS Parameters and PDU Set Information may be provided to the non-3GPP access nodes. Thus, PDU Set QoS Parameters specified for NG- RAN may be supported in network devices. PDU Set related assistance information (e.g., Protocol Description) specified for NG-RAN may be supported in non-3GPP access nodes. PDU Set Information specified for NG-RAN may be supported in network devices.

[0093] As described above, the 5G System supports PDU Set based QoS handling for a WTRU’s uplink and downlink traffic when the WTRU is connected to the system via an NG-RAN access network. The 5G System does not support PDU Set based QoS handling for a WTRU’s uplink and downlink traffic when the WTRU is connected to the system via an a non- 3GPP access network. Examples of non-3GPP access networks may include, but are not limited to a trusted Wi-Fi (wireless fidelity), an untrusted Wi-Fi, a wireline access network, or the like, or any appropriate combination thereof.

[0094] As described above, the 5G System supports detection of End of Data Bursts in a WTRU’s downlink traffic when the WTRU is connected to the system via an NG-RAN access network. Detection of End of Data Bursts in a WTRU’s downlink traffic is not supported when the WTRU is connected to the 5G System via an a non-3GPP access network.

[0095] Augmentations to a 5G System are described herein that allow network devices (e.g., non-3GPP access nodes) to be configured to provide PDU Set based QoS handling and detection of end of data bursts for a WTRU’s downlink traffic. Augmenting the 5G System to provide PDU Set based QoS handling and detection of end of data bursts for a WTRU’s downlink traffic may result in improved user experience when the WTRU is connected to the network via a network device, may result in improved allocation of network resources, and may result in decreased WTRU power consumption. Examples of network devices may include, but are not limited to an N3IWF, a TNGF, a W-AGF, or the like, or any appropriate combination thereof.

[0096] As described herein, 5G systems may provide support for PDU set based QoS handling to non-3GPP access networks. As described herein, 5G systems may support PDU Set based QoS handling in NG-RAN, wherein the PSA -UPF may identify PDUs that belong to PDU Sets based on Protocol Description for PDU Set identification and may provide PDU Set Information to the RAN in the GTP-U header. In an example configuration, 5GS (5G system) support for PDU Set based handling may be limited to NG-RAN access. Interaction between an application and a 5GS via non-3GPP access may enhance efficiency and may promote user experience. A user may be serviced by the 5GC (5G core network) via non-3GPP accesses such as trusted, untrusted, or wireline access, such as a device behind RG (residential gateway).

[0097] Described herein are mechanisms that support PDU set based QoS handling to non- 3 GPP access networks and address the potential impacts of such extension on the non-3GPP access-specific intermediate nodes. The procedures described herein enable network devices andWTRUs to be configured to support PDU Set based QoS handling and detection of end of data bursts for a WTRU’s downlink and uplink traffic. Examples of network devices may include, for example, an N3IWF, a TNGF, and a W-AGF.

[0098] For downlink traffic network devices may be configured with rules on how to map PDU Set information, such as, for example, PDU Set Importance Information and / or the End of Burst Indication, that is received in the GTP-U header over the N3 interface, to the corresponding DSCP values. The network device may receive a PDU and determine new DSCP values for the PDU based on the mapping rules. The network device may then send the PDU to a WTRU in the IPSec tunnel that is associated with the QoS Flow, along with the new DSCP values. The IPSec tunnel may be marked (e.g., in the outer header) with the new DSCP values in the IP packets that carries the PDUs. The DSCP markings also may be used by network nodes (e g. routers, access points, or the like) to determine how to prioritization the packets.

[0099] FIG. 2 depicts an example procedure for enabling PDU set based QoS handling on the downlink traffic when a WTRU uses non-3GPP access to access the 5G system. At step 1, a WTRU may send a PDU Session Establishment Request message to the SMF. The N3IWF / TNGF may transparently forward the PDU Session Establishment Request message to an SMF via an AMF in the 5GC. The WTRU may indicate in the PDU Session Establishment Request that the WTRU supports PDU Set handling over non-3GPP access. Based on this indication, the network (e g., the SMF) will know that PDU Set QoS Handling should be enabled for the WTRU on the WTRU’s non-3GPP access link.

[0100] At step 2, the SMF may send a message to the network device (e.g., N3IWF / TNGF) to establish the access resources for this PDU Session. The message may be sent via an N2 interface, and thus may be referred to herein as an N2 message. The message may include the NAS PDU Session Establishment Accept message to be delivered to the WTRU. The message also may include QoS Profiles for the PDU Session. The QoS profiles may include PDU Set QoS parameters, such as, for example, PDU Set Importance information and the End of Burst Indication. As explained herein, the network device may comprise mapping information (e.g., rules). Mapping information may be provided to the network device in any appropriate manner. For example, a network device may be configured with mapping information. For QoS flows that are configured for PDU set handling, the network device may, based on operator localconfigurations, for example, use the PDU set importance received in the GTP-U header to determine the DSCP vale for download (DL) packets. As another example, the message (step 2) may include mapping information. The message may comprise a GTP-U header that comprises mapping information (e.g., mapping rules) regarding how to map the PDU set importance information and / or the end of burst information to DSCP values. The mapping information (e.g., rules) may indicate how QoS Flow ID and PDU set QoS parameters such as, for example, the PDU Set Importance Information and / or the End of Burst Indication, are mapped, in the downlink, to DSCP values. The mapping information may indicate how the network device (e.g., N3IWF / TNGF) may determine the DSCP value that may be associated with each downlink packet based on information that is received in the GTP-U header of the message that delivered the packet to the N3IWF / TNGF. Examples of information in the GTP-U header may include QoS Flow ID, PDU Set Importance, and an indication of whether the PDU represents an end of a burst.

[0101] At step 3, the network device (e.g., N3IWF / TNGF) may determine the number of IPsec Child SAs to establish, and the QoS Flow(s) associated with each IPsec Child SA. This determination may be based on the PDU Set QoS parameters received at step 2 by the N3IWF / TNGF for determining IPSec Child SA that may include PDU set aware QoS handling in the downlink.

[0102] At step 4, the network device may establish the IPSec tunnel with the WTRU for each QoS Flow. At step 4a, the N3IWF / TNGF may send to the WTRU an IKE Create Child SA request. At step 4b, the WTRU may send an IKE Create Child SA response to the N3IWF / TNGF node.

[0103] At step 5, the network device may send to the WTRU via the signaling IPsec SA the PDU Session Establishment Accept message received at step 2. The PDU Session Establishment Accept message may indicate the flows and / or IPSec Child SA that are associated with PDU set aware QoS handling. When reflective QoS is enabled, this indication may be used by the WTRU to trigger uplink PDU Set aware QoS handling.

[0104] At step 6, the network device may send to the AMF an N2 PDU Session Response to the SMF.

[0105] At step 7a, the network device may receive DL PDU traffic via the N3 interface. The traffic that is received by the network device may already have DSCP markings in the outer IP header. The markings may have been applied by the UPF based on configuration information from the SMF. The network device may determine new markings (e.g., mapped DSCP values based on the mapping rules) for the DL traffic as it is sent towards the WTRU because the routers and access network that are between the N3IWF / TNGF and WTRU may be managed by a different network operator or may be configured to use DSCP values differently.

[0106] At step 7b, the network device may map DL packets / PDUs / flows to the corresponding IPsec Child SA when sending them over the non-3GPP Access network. The mapping may be based on PDU Set QoS information, such as, for example, PDU Set Importance Information and / or the End of Burst Indication. The network device may receive a PDU in a GTP-U message via the N3 interface. The network device may determine a DSCP values based on the mapping rules and the PDU set importance information from the GTP-U header. The network device may use the mapping rules that were received at step 2 to map the information from the GTP-U header (e g., QoS Flow ID, PDU Set Importance, and End of Burst Indication) to corresponding DSCP values. The network device may send the PDU to the WTRU in the IPSec tunnel that is associated with the QoS Flow and the outer header of the IP packet that carries the PDU that will be marked with the determined (e.g., mapped) DSCP value.

[0107] The network device may remove the GTP-U Header and may obtain the IP Packet (e.g., the PDU) to be sent to the WTRU. The network device may use the PDU Set Importance value and the mapping rules that were received in the QoS Profile to determine a DSCP Marking. The network device may mark an IP packet with the mapped DSCP value. The network device may then send the PDU in the IPSec tunnel that is identified in the GTP-U Header and apply the determined DSCP Marking to the outer header of the IP packet transmission. One or more routers may route the packet from the network device to a Wi-Fi access point. The routers may use the DSCP marking to determine how to prioritize the packet. When the packet is transmitted to the WTRU, for example by a Wi-Fi access point, the Wi-Fi access point may determine how to prioritize the packet on an 802.11 link. The prioritization may be determined based on the DSCP marking that was applied to the packet.

[0108] At step 8, the WTRU may receive PDUs and data packets on corresponding IPSec tunnels. The received PDUs and data packets may contain the determined DSCP markings which are based on the corresponding PDU Set QoS information.

[0109] FIG. 3 depicts an example process for enabling PDU set based QoS handling on uplink traffic when a WTRU uses non-3GPP access to access a 5G system. For uplink traffic, a WTRU may be configured with rules indicating how to map PDU Set Importance information and end of burst information to a DSCP Value. The WTRU may use the DSCP marking to determine how to prioritize the packets when transmitting packets over a non-3GPP access. The DSCP markings may also be used by network nodes (e.g. routers, access points, or the like) to determine how to prioritize the packets.

[0110] For example, as described in more detail below with reference to FIG. 3, a WTRU configured to support uplink PDU Sets based handling over non-3GPP access may select and connect to an access network based on an indication in configuration information that the access network has packet prioritization (e.g., QoS capabilities). The WTRU may select and connect to a network device, such as an N3IWF or TNGF based on an indication in the configuration information. The WTRU may send a PDU Session Establishment request to a network. The request may include an indication that the WTRU supports PDU Set handling over non-3GPP access. The WTRU may receive a message that indicates how to map QoS Flow ID to a Security Association and that indicates a mapping rule for how to map PDU Set Importance information to DSCP Values. The mapping rules may indicate how to map end of burst information to DSCP values. The message may indicate a protocol type that may be used to determine PDU Set Importance information or end of burst information. The WTRU may receive an application layer packet for uplink transmission, may determine a QoS Flow ID that is associated with the packet, and may use the mapping rule to determine a DSCP marking for the packet. The protocol type may be used to determine the PDU Set Importance and End of Burst Information of the Application Layer packet. The WTRU may transmit the packet on a Wi-Fi link. When transmitting the packet, the WTRU may use the DSCP marking to determine how to prioritization the packet. Prioritization means that the WTRU may determine what resources (e.g., time slot, frequency, or a combination thereof) to use to transmit the packet.

[0111] Referring to FIG. 3, at step 1 the WTRU may send a PDU Session Establishment Request message to the SMF. The network device may transparently forward the PDU Session Establishment Request message to the SMF via the AMF in the 5GC. The WTRU may include an indication in the PDU Session Establishment Request that indicates that the WTRU supports PDU Set handling over non-3GPP access. Based on this indication, the network (e.g., the SMF) may know that PDU Set QoS Handling may be enabled for the WTRU on the WTRU’s non- 3 GPP access link.

[0112] At step 2, the SMF may send a message (e.g., an N2 message) to the network device to establish access resources for this PDU Session. The message may include the NAS PDU Session Establishment Accept message to be delivered to the WTRU. The message also may include QoS Profiles for the PDU Session. The QoS profiles may include PDU Set information. The QoS profiles may include Protocol Descriptions of data flows. The QoS profile may include information on how PDU set QoS parameters such as, for example, the PDU Set Importance Information and / or the End of Burst Indication, are mapped, in the uplink, to different IPSec Tunnels or DSCP values. The message may indicate to the network device that the WTRU supports PDU Set based handling over non-3GPP access and that the N3IWF / TNGF may configure the WTRU for uplink PDU Set handling.

[0113] For each QoS Flow, the message may indicate what application protocol may be used in the uplink traffic. The application protocol may be provided so that the WTRU may be informed of the protocol type. Informing the WTRU of the protocol type may be provided so that the WTRU may detect the PDU Set related Application Layer information that is provided by the Application Layer. The message may include mapping information on how QoS Flow ID and PDU set QoS parameters such as, for example, the PDU Set Importance Information and / or the End of Burst Indication, may be mapped, in the uplink, to DSCP values. The mapping information may indicate how the WTRU may determine the DSCP value that may be associated with each uplink pack based on the QoS Flow ID and information that is received from the application layer of the WTRU. Examples of information that the Application Layer may provide include PDU Set Importance and an indication of whether the PDU represents an end of a burst.

[0114] At step 3, the network device may determine the number of IPsec Child SAs to establish and the QoS profiles associated with each IPsec Child SA. This determination may be based on the PDU Set QoS parameters received in step 2 by the network device for determining IPSec Child SA that may include PDU set aware QoS handling in the uplink.

[0115] At step 4, the network device may establish the IPSec tunnel with the WTRU for each QoS Flow. At step 4a, The network device may send to the WRU an IKE Create Child SA request. For each security association that is created, the network device may include a 3GPP- specific payload. The payload may indicate a QFI associated with the traffic that may be sent over the in the security association, and he type of application layer protocol that may be used within each QoS Flow and the mapping rules that can be used by the WTRU to determine an DSCP marking for traffic of the flow. Traffic within the security association may have different DSCP markings. This may be advantageous because, for example, a packet that is associated with a higher PDU Set importance may be assigned a DSCP value that is associated with a relatively low drop probability compared to the DSCP marking that is applied to a PDU that is associated with a lower PDU Set Importance. At step 4b, the WTRU may send an IKE Create Child SA response to the network device.

[0116] At step 5, the network device may send to WTRU via the signaling IPsec SA the PDU Session Establishment Accept NAS message that was received in step 2. At step 6, the network device may send to AMF an N2 PDU Session Response.

[0117] At step 7a, the WTRU may map UL packets / PDUs / flows to the corresponding IPsec Child SA when sending them over the non-3GPP Access. The mapping to an IPsec Child SA may be based on the QoS Flow ID that the WTRU determines is associated with the packet / PDU / flow. Each PDU may be assigned a DSCP marking value. The DSCP marking value may be determined based on the mapping rules that were received from the network device and based on the PDU Set Importance and End of Burst Indication. The WTRU may use the protocol description to determine the format of the application layer packet’s header so that the WTRU may determine the PDU Set Importance and determine whether the End of Burst Indication is present. The WTRU may transmit the packet(s) on the Wi-Fi link. When the packet(s) is transmitted by the WTRU, the WTRU may determine how to prioritize the packet(s) on the802.11 link. The prioritization may be determined based on the DSCP marking that was appliedto the packet(s). At step 7b, a Wi-Fi access point may receive the packet(s). Routers between the Wi-Fi access point may route the packet(s) to the N3IWF / TNGF. The packet(s) may contain DSCP markings corresponding to PDU Set QoS information and the routers may use this information to determine how to prioritize each packet.

[0118] At step 8, the UPF may receive PDUs and data packets on corresponding IPSec tunnels. The PDUs and data packets may contain DSCP markings corresponding to PDU Set QoS information.

[0119] Regarding access network selection and access node selection, as described herein, the WTRU may connect to a non-3GPP access network and select a network device, such as an N3IWF or TNGF, before establishing the PDU Session. To use PDU Set QoS handling over the non-3GPP access network, the WTRU may select a non-3GPP access network and network device that supports the feature. This may impact the user experience. For example, the user experience may not be adversely affected if traffic is not prioritized.

[0120] The WTRU may be configured with WLAN Selection Policy (WLANSP) rule(s). Each WLANSP rule may indicate if the rule may be applied when support of PDU Set QoS handling is used. Alternatively, the rule may indicate whether the 802.11 access network supports QoS treatment protocols such as 802. l ie. The WTRU may determine to select an access network that is described in a WLANSP Rule if the rule indicates that that the access network supports packet prioritization (e.g., QoS). For example, the WTRU may prefer an access network that supports packet prioritization because the applications that are running on the WTRU may expect QoS treatment in order to achieve good user experience.

[0121] Once the WTRU has selected an access network, the WTRU may select a network device, such as an N3IWF or TNGF, for example. The WTRU may be configured with network device configuration information or the WTRU may discover network device configuration information, and the configuration information may indicate an FQDN (fully qualified domain name) or IP address of network device that may be selected. The network device configuration information may indicate whether each network device supports PDU Set QoS handling. The WTRU may choose not to select a network device that does not support packet prioritization(e.g., QoS) and may choose to select a network device that does not support packet prioritization (e.g, QoS).

[0122] Once the WTRU connects to the network device, the WTRU may perform a registration procedure and establish a PDU Session. The WTRU may then send a receive PDU Sets and expect that PDU Set QoS handling will be enabled.

[0123] Although features and elements are provided 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. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods, apparatuses, and articles of manufacture, within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims.

[0124] In addition, methods provided 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 (which do not include transitory signals). Examples of computer-readable storage media, which are differentiated from signals, may 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.

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

Claims

CLAIMSWhat is claimed is:

1. A network device comprising: a processor configured to: receive a packet data unit (PDU) comprising a general packet radio service tunnelling protocol user plane (GTP-U) header, wherein the GTP-U header comprises PDU set importance information associated with the PDU; determine a differentiated services code point (DSCP) value for the PDU based on mapping rules and the PDU set importance information from the GTP-U header, wherein the mapping rules comprise an indication regarding how to map PDU set importance information to DSCP values; determine an internet protocol security (IPSec) tunnel for transmitting the PDU; and send, via the IPSec tunnel, the PDU in an IP packet marked with the determined DSCP value for the PDU.

2. The network device of claim 1, wherein the GTP-U header comprises end of burst information.

3. The network device of claim 2, wherein the mapping rules comprise an indication regarding how to map the end of burst information to DSCP values.

4. The network device of claim 3, wherein the determined DSCP value is based on the PDU set importance information and the end of burst information.

5. The network device of claim 1, wherein the mapping rules comprise rules regarding how to map PDU set quality of service (QoS) parameters to DSCP values.

6. The network device of claim 1, wherein an outer header of the IP packet is marked with the determined DSCP value.

7. The network device of claim 1, wherein the network device comprises a non-3GPP interworking function (N3IWF).

8. The network device of claim 1, wherein the network device comprises a trusted non-3GPP gateway function (TNGF).

9. The network device of claim 1, wherein the network device comprises a wireline access gateway function (W-AGF).

10. The network device of claim 1, wherein the PDU in the IP packet marked with the determined DSCP value is sent, via the IPSec tunnel, to a wireless transmit / receive unit (WTRU).

11. A method performed by a network device, the method comprising: receiving a packet data unit (PDU) comprising a general packet radio service tunnelling protocol user plane (GTP-U) header, wherein the GTP-U header comprises PDU set importance information associated with the PDU; determining a differentiated services code point (DSCP) value for the PDU based on the mapping rules and the PDU set importance information from the GTP-U header, wherein the mapping rules comprise an indication regarding how to map PDU set importance information to DSCP values; determining an internet protocol security (IPSec) tunnel for transmitting the PDU; and sending, via the IPSec tunnel, the PDU in an IP packet marked with the determined DSCP value for the PDU.

12. The method of claim 11, wherein the GTP-U header comprises end of burst information.

13. The method of claim 12, wherein the mapping rules comprise an indication regarding how to map the end of burst information to DSCP values.

14. The method of claim 13, wherein the determined DSCP value is based on the PDU set importance information and the end of burst information.

15. The method of claim 11, wherein the mapping rules comprise rules regarding how to map PDU set quality of service (QoS) parameters to DSCP values.

16. The method of claim 11, wherein an outer header of the IP packet is marked with the determined DSCP value.

17. The method of claim 11, wherein the network device comprises a non-3GPP interworking function (N3IWF).

18. The method of claim 11, wherein the network device comprises a trusted non-3GPP gateway function (TNGF).

19. The method of claim 11, wherein the network device comprises a wireline access gateway function (W-AGF).

20. The method of claim 11, wherein the PDU in the IP packet marked with the determined DSCP value is sent, via the IPSec tunnel, to a wireless transmit / receive unit (WTRU).

Images