QOS flows with multiplexed xr flows

Abstract

A network node may be configured with packet detection rules (PDRs). The PDRs may allow the network node to identify one or more extended reality (XR) streams. The network node may be configured with forward action rules (FARs). The FARs may include information related to how one or more XR streams should be routed. The network node may invoke a user plane function (UPF). The UPF may be configured using information from the PDRs and / or the FARs. The network node may establish a protocol data unit (PDU) session. The network node may identify one or more XR streams indicated in the PDU session based on, at least, its configured PDRs. The network node may forward one or more XR streams according to the information in the FARs.

Description

QoS FLOWS WITH MULTIPLEXED XR FLOWSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 595,473, filed November 2, 2023, the entire contents of which are incorporated herein by reference as if fully set forth.BACKGROUND

[0002] To support protocol data unit (PDU) Set based quality of service (QoS) handling, a PDU session anchor (PSA) user plane function (UPF) may identify one or more PDUs that belong to PDU Sets. The PSA may determine PDU Set Information and send the PDU set information to a next generation radio access network (NG-RAN) (e.g., in the general packet radio service (GPRS) tunneling protocol - user plane (GTP-U) header). The PDU Set information can be used by the NG-RAN for PDU Set based QoS handling

[0003] The PDU Set Information may comprise one or more of: a PDU Set Sequence Number; an Indication of an End PDU of the PDU Set; a PDU Sequence Number within a PDU Set; a PDU Set Size (e.g., in bytes); and / or a PDU Set Importance, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow.SUMMARY

[0004] Methods and apparatuses are disclosed herein for quality of service (QoS) flows with multiplexed extended reality (XR) flows. A user plane function (UPF) may receive downlink traffic from an extended Reality Media (XRM) service. The UPF may be configured (e.g., with configuration information) by a session management function (SMF). The UPF may be configured by the SMF with one or more Packet Detection Rules (PDRs), for example, to identify one or more individual XR streams (e.g., using IP 5-tuple, synchronization source (SSRC), payload type, protocol, etc.). The UPF may be configured by the SMF with one or more Forward Action Rules related to how to forward the one or more individual XR streams and / or create a general packet radio service(GPRS) tunneling protocol - user plane (GTP-U) packet header. The UPF may receive one or more protocol data units (PDUs) from an application server. The UPF may identify an XR stream, based on the one or more configured PDRs. The UPF may map the identified XR stream to a QoS flow. The UPF may create a GTP-U packet, for example, to forward it to the radio access network (RAN) node. The GTP-U packet header may be generated by the UPF based on the identification of the stream, one or more stream characteristics, one or more stream PDU set QoS requirements, and / or the one or more configured forward action rules.

[0005] One or more packet filter sets may be used for the one or more PDRs. A forward action rule may be used to request the UPF to mark one or more PDU sets with stream information. The UPF may add stream metadata to the GTP-U header, for example, based on one or more desired per stream PDU set QoS requirements. The UPF may modify PDU Set metadata based on, for example, one or more desired per stream PDU set QoS requirements.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0008] FIG. 1 C is a 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.

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

[0010] FIG. 2 is a diagram depicting an example of quality of service (QoS) management.

[0011] FIG. 3 is a diagram depicting example multiplexed streams.

[0012] FIG. 4 is a diagram depicting an example creation of multiplexed streams.

[0013] FIG. 5 is a diagram depicting an example handling of multiple downlink (DL) extended reality (XR) streams in a QoS flow.

[0014] FIG. 6 is a diagram depicting example intra-stream protocol data unit (PDU) set characteristics.DETAILED DESCRIPTION

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

[0016] 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 subscriptionbased 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 WTRU.

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

[0018] 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 multipleinput 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.

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

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

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

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

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

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

[0025] 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 cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 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.

[0026] 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. 1 A, 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, whichmay 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.

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

[0028] 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. 1 A 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.

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

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

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

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

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

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

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

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

[0037] 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, and / or a humidity sensor.

[0038] 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 WRTU 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 downlink (e.g., for reception)).

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

[0040] 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 implementMIMO 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.

[0041] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

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

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

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

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

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

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

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

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

[0050] 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 primarychannel. 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 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.

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

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

[0053] Sub 1 GHz modes of operation are supported by 802.11 af 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.11 n, 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, such as MTC devices in a macro coveragearea. 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).

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

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

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

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

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

[0059] 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 communicatewith 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.

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

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

[0062] 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 RAN113 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.

[0063] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the ON 115 via an N11 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 WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IPbased, non-IP based, Ethernet-based, and the like.

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

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

[0066] In view of Figures 1 A-1 D, and the corresponding description of Figures 1 A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, 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 (notshown). 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.

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

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

[0069] To support protocol data unit (PDU) Set based quality of service (QoS) handling, a PDU session anchor (PSA) user plane function (UPF) may identify one or more PDUs that belong to PDU Sets. The PSA UPF may determine PDU Set Information and may send the PDU Set Information to the next generation radio access network (NG-RAN) (e.g., in the general packet radio service (GPRS) tunneling protocol - user plane (GTP- U) header). The PDU Set information can be used by the NG-RAN for PDU Set based QoS handling.

[0070] The PDU Set Information may comprise a PDU Set Sequence Number, an indication of an end PDU of the PDU Set, a PDU Sequence Number within a PDU Set,a PDU Set Size in bytes, and / or a PDU Set Importance. The PDU set importance may identify a relative importance of a PDU Set compared to other PDU Sets within a QoS Flow.

[0071] To determine the PDU set information, the PSA UPF may rely on information carried in the received packets and / or on implementation. For example, if extended Reality Media (XRM) traffic is carried over real-time transport protocol (RTP), the RTP header may include one or more of the following fields: an end PDU of the PDU set field, an end of data burst field, a PDU set importance field, a PDU set sequence number field, a PDU sequence number within a PDU set field, or a PDU set size field. The End PDU of the PDU Set [E] field (e.g., 1 bit) may be a flag that shall be set to 1 for the last PDU of the PDU Set and set to 0 for one or more (e.g., all) other PDUs of the PDU Set. The End of Data Burst [EDB] field (e.g., 3 bits) may be 3 bits in length and may indicate the end of a Data Burst. The (e.g., 3) bits may encode the End of Data Burst indication. The PDU Set Importance [PSI] field (e.g., 4 bits) may indicate an importance of a PDU Set compared to other PDU Sets within the same QoS flow.Lower values may indicate a higher importance PDU Set with the highest importance PDU Set indicated by 0 and the lowest importance PDU Set indicated by 15. The PDU Set Sequence Number [PSSN] field (e.g., 10 bits) may encode the sequence number of the PDU Set to which the current PDU belongs acting as a 10-bit numerical identifier for the PDU Set. The PDU Sequence Number within a PDU Set [PSN] field (e.g., 6 bits) may be the sequence number of the current PDU within the PDU Set. The PSN may be set to 0 for the first PDU in the PDU Set and incremented monotonically for every PDU in the PDU set in order of transmission from the sender. The PDU Set Size [PSSize] field (e.g., 24 bits) may indicate the total size of one or more (e.g., all) PDUs of the PDU Set to which this PDU belongs. This field may be optional and may be subject to a Signal Description Protocol (SDP) signaling offer / answer negotiation, where the Application Server may indicate whether it will be able to provide the size of the PDU Set for that RTP stream. If the PDU Set Size field is not enabled, the field may not (e.g., should not) be present. If the PDU Set Size field is enabled, but the Application Server is not able to determine the PDU Size for a particular PDU Set, it may (e.g., should) set the value to 0 in one or more (e.g., all) PDUs of that PDU Set. The PSSizemay indicate the size of a PDU Set including RTP / UDP / IP header encapsulation overhead of its corresponding PDUs. The PSSize may be expressed in bytes.

[0072] In addition to the PDU set information carried in the GTP-U header, the network may also be configured with PDU set QoS requirements (e.g., or information). The PDU set QoS requirements may be defined per QoS flow, and as a result the PDU set QoS requirements may be the same for one or more (e.g., all) PDU sets carried in a QoS flow. The following PDU set QoS requirements may be defined for XRM traffic flows.

[0073] A PDU Set Delay Budget (PSDB) may define an upper bound for the delay that a PDU Set may experience for the transfer between the WTRU and the N6 termination point at the UPF, for example, the duration between the reception time of the first PDU (e.g., at the N6 termination point for DL or the WTRU for UL) and the time when one or more (e.g., all) PDUs of a PDU Set have been successfully received (e.g., at the WTRU for DL or N6 termination point for UL).

[0074] A PDU Set Error Rate (PSER) may define an upper bound for the rate of PDU Sets that have been processed by the sender of a link layer protocol (e.g., RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g., PDCP in RAN of a 3GPP access).

[0075] A PDU Set Integrated Handling Information (PSIHI) may indicate whether one or more (e.g., all) PDUs of the PDU Set are needed for the usage of the PDU Set by the application layer on the receiver side.

[0076] FIG. 2 is a diagram that shows an example of QoS Management at 200. At 202, an Application Function (AF) may provision the network (e.g., PCF) with one or more QoS requirements of the traffic flows (e.g., using a NEF service API such as Nnef_AFsessionWithQoS_Create). At 204, the policy control function (PCF) may use QoS information to configure policy and charging (PCC) rules. Based on the rules configured in PCF, the SMF may then configure radio access network (RAN) node with a QoS profile (e.g., 208), the user plane function (UPF) with packet detection rules (PDRs) (e.g., 210), and the WTRU with QoS rules (e.g., 206). A PDU may arrive at the UPF over the N6 interface at 212. The UPF may map the traffic to a QoS flow 214 using the configured PDRs. The UPF may create a tunnel to the RAN node and sendthe arriving PDU to the RAN node (e.g., in a GTP-U packet). The RAN node may use the configured QoS profile to determine how to manage the GTP-U packet. The RAN node may determine how to schedule the packet to the WTRU and whether the packet should be discarded. If scheduled, the packet may be transmitted to the WTRU on a configured Data Radio Bearer (DRB) 216.

[0077] Additional processing has been defined for extended reality (XR) media traffic. Namely, the XR traffic may be transmitted as PDU sets. The QoS profile has requirements that target PDU sets. Furthermore, the header of the GTP-U PDU may carry PDU set information. In some systems, there may be an assumption that a single XR stream is mapped to a QoS flow.

[0078] XR Media services may include multiple types of flows, (e.g., video stream, audio stream, haptic, other metadata, or sensor data) for more immersive experience. To enable these immersive services, different media types can be multiplexed into a single data flow before arriving at the 5GS ingress. Each stream could have its own PDU set properties. The result is that the QoS flow carries multiplexed streams, as shown in FIG. 3.

[0079] FIG. 3 is a diagram showing example multiplexed streams at 300. Multiplexing of the XR streams may occur at the application layer (e.g., such as at the RTP), at the transport layer (e.g., using the Internet Engineering Task Force (IETF) QUIC protocol), and / or based on Policy and Charging Control (PCC) rules provided to UPF.

[0080] FIG. 4 is a diagram showing examples of creation of multiplexed streams. Multiple XR streams may be allowed over a single QoS flow. At 402, an example is shown wherein multiple application flows are mapped using PCC rules to the same QoS flow, wherein multiple PCC rules point to the same QoS flow, and wherein each PCC rule selects a single application flow. The example shown at 402 may also be referred to as Multiplexing Option 1. At 404, an example is shown wherein multiple application flows map to a single QoS flow, wherein a PCC rule selects a plurality of application flows for the one QoS flow. The example shown at 404 may also be referred to as Multiplexing Option 2. At 406, an example is shown wherein an application flow that uses QUIC with many multiplexed streams is mapped to a QoS flow. The example shown at 406 may also be referred to as Multiplexing Option 3. At 408, an example isshown wherein an application flow that is multiplexed at the application layer (e.g., RTP) is mapped to a QoS flow. The example shown at 408 may also be referred to as Multiplexing Option 4.

[0081] Enhancements may be needed for traffic detection and QoS Flow mapping when different media types and data flows are multiplexed within a single end to end transport connection.

[0082] In some technologies, a single XR stream may be mapped to a QoS flow. The XR stream may have protocol data unit (PDU) set QoS requirements, which are configured in the radio access network (RAN) node in a QoS profile. This may allow the RAN node to provide some differentiated handling of the XR traffic.

[0083] Limiting the network to map a single XR stream over a QoS Flow is inefficient. First, mapping a single XR stream over a QoS flow may be against prevalent QoS principles (e.g., the principle that streams having similar characteristics are mapped to the same QoS flow). This would prevent the network from handling cases where the multiplexing may happen at the application layer or the transport layer. Second, mapping a single XR stream over a QoS flow may lead to a large number of QoS flows - resulting in unnecessary per QoS flow processing (e.g., QoS monitoring). Third, mapping a single XR stream over a QoS flow may pose an issue for WTRUs, which have a limit on the number of packet detection filters they support (e.g., because every stream would require its own packet detection filter).

[0084] One or more enhancements may be implemented to support traffic detection and / or QoS Flow mapping for different media types and data flows multiplexed within a single end to end transport connection, which may also be referred to as QoS flows with multiplexed streams.

[0085] One of the issues with QoS flows with multiplexed streams, is that each of the multiplexed streams may have its own PDU set characteristics and PDU set QoS requirements. How the system manages QoS for this multiplexed QoS flow may be undefined. The following may need to be considered. As a first consideration, additional information may be needed in the packet detection rules provided to the UPF and WTRU, for example, to identify the individual XR streams. As a second consideration, the WTRU and UPF may need to map the individual XR streams to QoSflows. As a third consideration, when a QoS flow has multiplexed XR streams with different PDU Set QoS parameters, the RAN node may need to be configured with the PDU set QoS requirements for the individual streams. The RAN node may additionally need to enforce PDU set QoS requirements for the individual streams. Additionally, the UPF and WTRU may need to perform actions on the user plane packets to assist the RAN node to enforce PDU set QoS requirements for the individual streams.

[0086] The terms stream, data flow, or sub-flow may be used interchangeably herein. A data flow may represent a traffic from an application source (e.g., an application server or WTRU). In examples, the data flow may be a video data flow, an audio data flow, and / or a haptic data flow. The data flows may have a relationship in time. For example, an audio data flow may need to be time synchronized with a video data flow.

[0087] The term “stream” may refer to a service subflow (e.g., a media service subflow) multiplexed in a service flow (e.g., multiplexed in an application connection). “Stream” and “XR stream” may be used interchangeably herein.

[0088] The streams may be assumed to be XR streams. This is for illustrative purposes. It should be understood that the streams may be of any type.

[0089] The term end to end connection may be used to refer to a connection between a WTRU and an application server used to transfer one or more data flows. For example, the end to end connection may be a real-time protocol (RTP) session. Additionally, or alternatively, this may be a QUIC protocol connection where multiple streams are multiplexed. The different streams may, in examples, be audio and video, and / or different video layers each on its own stream.

[0090] A PDU Set may refer to one or more PDUs carrying the payload of one unit of information generated at the application level (e.g., frame(s) and / or video slice(s), etc., for extended Reality (XR) Services). As a result, a PDU set may have one PDU or multiple PDUs. One or more (e.g., all) PDUs in the PDU Set may carry PDU set information.

[0091] The term PDU Set Information may be used to refer to information that is carried with the PDUs of the PDU set. PDU Set Information may help to characterize the PDU set. Examples include the PDU set size, the PDU set sequence number, the End PDU indication, etc.

[0092] The terms PDU Set QoS requirements, PDU Set QoS information, and PDU Set QoS parameters may be used interchangeably herein. The PDU Set QoS requirements may be used to refer to QoS requirements that deal with PDU set properties of the PDU set. In examples, PDU set properties may include a PDU set delay budget (PSDB), a PDU Set Error Rate (PSER), and / or a PDU Set Integrated Handling Indication (PSIHI).

[0093] Multi-modal data may refer to data from different kinds of devices / sensors or the output data to different kinds of destinations (e.g., one or more WTRUs) required for the same task or application. Multi-modal data may include more than one single-modal data. There may be strong dependencies among each single-modal data within multimodal data. Single-modal data can be seen as one type of data.

[0094] Each stream may be assumed to have a different PDU set information and / or PDU set QoS parameters and / or each stream may be identified individually by the UPF and / or WTRU. It should be understood that the procedures described herein may also apply to a group of streams that have similar PDU set information and / or PDU set QoS parameters and are treated as a Stream Group. The procedures then may apply to the stream group rather than the individual streams.

[0095] The term “Stream Characteristics” may be used to refer to characteristics of a stream. Stream Characteristics may include an identifier, an indication of whether the stream is PDU set based, and / or etc.

[0096] The term “Mechanisms to Identify streams” may be used to refer to one or more methods employed at the UPF or WTRU, to help identify the streams in a multiplexed flow.

[0097] The term “base” packet filter may be used to refer to the criteria (e.g., IP 5-tuple) used in the PDR to help identify a PDU, and / or to map this PDU to a QoS flow.

[0098] The term “IP 5-tuple” may be used to refer to the combination of source IP address / port number, destination IP address / port number and the protocol in use for an end to end connection.

[0099] The term “stream metadata” may be used to refer to information that is added to a PDU and / or that is related to some stream context.

[0100] The term “PDU Set metadata” may be used to refer to information that is added to a PDU and / or that is related to PDU set information.

[0101] The term “QoS flow end of burst” may be used to describe an end of burst that occurs over the QoS flow, for example, taking into account the multiplexed streams. This may refer to the time at which the last PDU of the multiplexed streams is received before a period of inactivity on the QoS flow.

[0102] The term “Stream end of burst” may be used to describe the end of burst of a particular stream. This may refer to the time at which the last PDU of a stream is received before a period of inactivity on the stream.

[0103] The solutions proposed herein may provide one or more common benefits. The benefits of the proposed solutions may include but are not limited to one or more of the following: support of QoS flows with multiplexed XR streams and meeting different QoS requirements for the individual XR streams. Each stream may have independent and / or different PDU set information and / or PDU set QoS requirements.

[0104] A UPF may receive downlink traffic for an XR Media (XRM) service. The UPF may be configured by a session management function (SMF), for example, with configuration information. The UPF may be configured by the SMF with one or more Packet Detection Rules (PDRs) (e.g., in the configuration information), for example, to identify one or more individual extended reality (XR) streams. As discussed more fully below, the PDRs may be used to identify XR streams (e.g., associated with a PDU) based on one or more of: an IP 5-tuple, a Synchronization Source (SSRC), a payload type, and / or a protocol associated with the PDU. The UPF may be configured by the SMF with one or more Forward Action Rules related to how to forward the one or more individual XR streams and / or create a general packet radio service (GPRS) tunneling protocol - user plane (GTP-U) packet header. The UPF may receive a protocol data unit (PDU) from an application server. The UPF may identify an XR stream, based on the one or more configured PDRs. The UPF may map the identified XR stream to a Quality of Service QoS flow. The UPF may create a packet (e.g., a GTP-U packet), in examples, to forward to a network (e.g., RAN) node. The (e.g., GTP-U) packet header may be generated by the UPF based on the identification of the stream, one or more stream characteristics, one or more stream PDU set QoS requirements, and / or the one or more configured forward action rules.

[0105] One or more packet filter sets may be used for the one or more PDRs. A forward action rule may be used to request the UPF to mark one or more PDU sets with stream information. The UPF may add stream metadata to the GTP-U header, for example, based on one or more desired per stream PDU set QoS requirements. The UPF may modify PDU Set metadata, for example, based on one or more desired per stream PDU set QoS requirements.

[0106] FIG. 5 is a diagram depicting an example handling 500 of DL XR streams in a QoS flow. It should be appreciated that the example handling 500 may be performed at the WTRU 522 for UL XR streams in a QoS flow. At 502, an application function (AF) 532 may provision one or more network nodes with PDU set QoS requirements for the individual XR streams that are to be multiplexed over the QoS flow. A policy control function (PCF) 530 may generate one or more policy and charging control (PCC) rules and provide them to a session management function 528 (SMF 528) at 504. The SMF 528 may determine the QoS profile(s) and may send the QoS profile(s) to the RAN node 524 at 508. The SMF 528 may determine the QoS rules and may send the QoS rules to the WTRU 522 at 510. The SMF 528 may determine the N4 rules and may send the N4 rules to the UPF 526 at 506. The N4 rules may include one or more PDRs and / or one or more forward action rules (FARs). A PDU from the XR streams may arrive at the UPF 526 at 512. At 514, the UPF 526 may identify the XR stream of the arriving PDU based on, for example, the one or more configured PDRs. The UPF 526 may map the PDU to a QoS flow at 516. The UPF 526 may prepare the GTP-U packet that carries the PDU to the RAN node 524. The UPF 526 may determine GTP-U header information. The GTP-U header information may include PDU set metadata and stream metadata. The GTP-U PDU may be sent to the RAN node 524. At 518, the RAN node 524 may enforce per stream PDU set QoS requirements. The PDU set QoS requirements may be included in the QoS profile. The RAN node 524 may send the PDU to the WTRU 522 over a data radio bearer at 520. The identification, mapping, and processing shown in the UPF 526 may apply to DL traffic. It should be noted that the same identification, mapping, and processing may also apply at the WTRU 522 for uplink (UL) traffic. For example, the handling 500 shown in FIG. 5 may be applied in the UL at the WTRU 522.

[0107] For example, the WTRU 522 may identify PDlls based on one or more configured PDRs, map the PDUs to QoS flows as discussed above, and / or prepare and send packets (e.g., GTP-U packets) indicating the QoS requirements of the PDUs. For example, the WTRU 522 may receive configuration information from a network node (e.g., such as the SMF 528). The configuration information may include one or more PDRs. The one or more PDRs may be applied to identify a PDU based on an IP 5-tuple associated with the PDU and one or more of a synchronization source (SSRC), a payload type, or a protocol associated with the PDU. The WTRU 522 may generate a plurality of PDUs, wherein a first PDU and a second PDU of the plurality of PDUs are associated with a single internet protocol (IP) 5-tuple value. The WTRU 522 may identify a first XR stream for the first PDU and a second XR stream for the second PDU by applying the one or more PDRs to the first PDU and the second PDU. The WTRU 522 may map the first XR stream to a first Quality of Service (QoS) flow and the second XR stream to a second QoS flow.

[0108] XR streams may have a number of characteristics, including but not limited to those discussed in this section. The streams may have one or more of the following “Stream Characteristics.” A stream may be periodic or aperiodic. If periodic, the stream may have a certain periodicity. The stream may have more than one periodicity, if some PDUs of the stream have one periodicity and other PDUs have a different periodicity. A stream may be transmitted in bursts or not (e.g., it can be expected that a periodic burst is followed by no transmission until the next period). In some periodic streams, the idle time between bursts or periods may be similar. In some periodic streams, the idle time between bursts or periods may vary. The stream may have a certain priority level (e.g., stream priority). The priority may be a numeric value, with a lower number representing a higher priority. Alternatively, the priority may be a numeric value, with a higher number representing a higher priority. As another alternative, the priority may be a relative value such as “high,” “medium,” or “low”. The stream may be PDU set based or non-PDU set based. A PDU Set based stream may be a stream where for one unit of information generated at the application level (e.g., frame(s) or video slice(s)) the application generates one or more PDUs. The one or more PDUs may be referred to as a PDU set. A non-PDU Set based stream may be a streamwhere one unit of information generated at the application level (e.g., frame(s) or video slice(s)) is always transmitted by one PDU. A PDU set may be identified by its PDU set header parameters. A stream that was once a non-PDU set based stream, may be changed dynamically to a PDU set based stream, and vice versa.

[0109] For a PDU set based stream, the stream may have characteristics of the PDU sets which are included over the stream. For example, some of the characteristics may include a PDU set sequence number, a PDU set size, and / or PDU set importance. In examples, the stream may have PDU set sizes (e.g., only PDU set sizes) larger than a threshold, or PDU set sizes within a certain range.

[0110] For a PDU set based stream, the stream may have QoS requirements related to the PDU set. For example, the PDU set delay budget (PSDB), PSIHI, PSER. A PDU set based stream may have a QoS requirement where partial PDU set handling is required. For example, if a PDU set may tolerate error or loss of PDUs up to a certain percentage or ratio or threshold, then the stream may have a partial PDU set handling indication that includes an error / loss threshold.

[0111] FIG. 6 is a diagram showing an example of intra-stream PDU set characteristics. For a PDU set based stream, the stream may have intra-stream PDU set characteristics and / or requirements. For example, one characteristic may be based on relative importance of PDU sets. Typical examples are shown in FIG. 6. The relative importance characteristic may be time based. For example, at 602, FIG. 6 shows an example where PDU set 1 may be needed for the PDU sets received for the next K msec (shown shaded). Additionally, or alternatively, relative importance characteristics may be count based. For example, at 604, FIG. 6, shows an example that a PDU set may be needed for the reception of the next K PDU sets (shown shaded). Additionally, or alternatively, the relative importance characteristic may be priority based. For example, at 606, FIG. 6 shows an example where a PDU set may be needed for the reception of one or more (e.g., all) PDU sets received until the reception of a PDU set of equal or higher priority. The priority at 606 may be based on the PSI.

[0112] In examples, for a PDU set based stream, the stream may have inter-stream PDU Set characteristics and requirements. For example, the streams may be multiple streams from a multi-modality data service. The streams may have a strict timingrelationship between each other. For example, the PDU sets on stream 1 and stream 2 may need to be received within a delay tolerance limit. If the delay between the streams exceeds this limit, either one or both of the PDU sets may not be useful to the recipient or may affect the user’s perceived quality of experience (QoE).

[0113] A non PDU set based stream may also have inter-stream characteristics and / or requirements with a PDU set based stream or another non PDU set based stream. For example, a certain stream may include PDUs or PDU sets that represent a certain modality, (e.g., a video frame). The server may have used forward error correction on the PDUs or PDU sets of the stream, to generate redundancy PDUs. These redundancy PDUs may be carried in a different stream than the video frame PDUs themselves.

[0114] An AF may provision stream based PDU set QoS parameters. An AF may assist the network in managing Multiplexed XR streams. The AF may configure the 5G network with the XR stream related QoS parameters and characteristics using an API enhanced for multiplexed streams. For example, a network exposure function (NEF) service application protocol interface (API) such as “Nnef_AFsessionWithQoS_Create” may be enhanced to include, without limiting, one or more of the following elements. A NEF service API may include a number of XR streams in the end to end connection. A NEF service API may include a PDU set QoS requirement per stream. A NEF service API may include an indication of how streams are to be identified in end to end connection. For example, this may be an indication that the streams should be identified by application layer stream ID, or SSRC. A NEF service API may include a Specific identifier of a stream. A NEF service API may include a Modality of the stream (e.g., audio, video, haptic). A NEF service API may include Inter-stream correlation information (e.g., streams that have strict timing relationships). A NEF service API may include an Inter-stream PDU set correlation information (e.g., information on how to identify PDU sets from multiple streams that should be delivered within a delay tolerance limit). A NEF service API may include a stream type (e.g., redundancy / FEC stream or non FEC stream, primary or secondary stream, etc.). A NEF service API may include traffic pattern information indicating how the PDU sets from different streams will be multiplexed (e.g., for the lifetime of the application or for a certain period). Forexample, the traffic pattern information may indicate that stream 1 PDU sets have even PDU set sequence numbers, while stream 2 PDU sets have odd PDU set sequence numbers.

[0115] A UPF may manage QoS flows with multiplexed streams. The UPF may identify the different streams using mechanisms to identify streams. These mechanisms may be used at the UPF and / or the WTRU. Numerous different mechanisms may be used to generate a multiplexed stream over a QoS flow. Example mechanisms include but are not limited to: Multiplexing Option 1 and 2, where the multiplexing occurs at the UPF; Multiplexing Option 3 where the multiplexing occurs at the application layer (e.g., RTP); and Multiplexing Option 4 where the multiplexing occurs at the transport layer (e.g., QUIC). Multiplexing Options 1 and 2 are examples of mechanisms where the multiplexed stream may not be end to end (between WTRU and Application Server), but rather between the WTRU and the UPF. Multiplexing Options 3 and 4 are examples of mechanisms where the multiplexed stream may be end to end (e.g., between WTRU and Application Server).

[0116] A multiplexed stream over the QoS flow may be generated by the UPF, based on the configured QoS mapping rules. The UPF may be provided with Packet Detection Rules (PDRs), which allow it to select the PDU sets arriving over the N6 interface. The PDU sets arriving over the N6 interface may be on different IP flows (e.g., they may have a different internet protocol (IP) 5-tuple), for example, where each of the IP flows is a stream. As the UPF is selecting the traffic to be multiplexed over the QoS flow, it may identify which PDU set comes from which stream.

[0117] A multiplexed stream over the QoS flow may be generated by the application layer (e.g., RTP layer) of the Application Server. The streams may be in a single end to end connection and have the same IP 5-tuple information. In this case, the UPF may need a mechanism to help identify which PDU sets and which PDUs are from the same stream. Several possible options include, but are not limited to, the following.

[0118] In examples, the application layer in the Application server may add an identifier in the stream application layer packet header to help identify the streams. For example, a new RTP header extension may be defined “stream ID” which is unique for each stream within an end to end connection. The PDR provided to the UPF may beexpanded to include “stream ID” in the Service data flow filter. This may be an indication to the UPF to use the “stream ID” to help identify the different streams. Alternatively, this may be the value of the “stream ID.”

[0119] In examples, the application layer in the Application server may use the Synchronization source (SSRC) and / or Contributing source (CSRC) to help identify the stream. The SSRC identifier may uniquely identify the source of a stream. The synchronization sources within the same RTP session (e.g., end to end connection) may be unique. The CSRCs identifiers (IDs) may enumerate contributing sources to a stream that has been generated from multiple sources. The PDR provided to the UPF may be expanded to include the “SSRC” and / or “CSRC” in the Service data flow filter. This may be an indication to the UPF to use the “SSRC” and / or “CSRC” to help identify the different streams. Alternatively, this may be the value of the “SSRC” and / or “CSRC.”

[0120] In examples, the application layer in the Application server may add an indication of when the next PDU set (or PDU) in the stream is expected. For example, if the stream is periodic, the Application server may include a field in an RTP header extension that indicates that the next PDU Set (or PDU) of the stream is to be expected in K msec. The PDR provided to the UPF may be expanded to include the “Expected Arrival Time” in the Service data flow filter. This may be an indication to the UPF to determine the time of the next arriving PDU Set (or PDU). The UPF may use this determined time to help identify streams. For example, a UPF may receive a PDU set from stream 1 at time T1 and may determine that the next arriving PDU set for stream 1 is in K msec. The PDU set arriving at T1 + K msec may be identified as belonging to stream 1. The UPF may determine the time of next arrival from knowledge of the stream periodicity, for example, provided by the SMF. Alternatively, each PDU set may include the information regarding the time of the next arrival. For example, the application layer may provide this time in an RTP header extension. When the application server provides an “Expected Arrival Time” value and / or indication to the UPF for different streams, the application server may need to be mindful of the resolution of the provided arrival time values. The UPF may receive two PDUs belonging to different streams at a similar time, if the values K1 and K2 for a stream 1and stream 2 are multiple of each other (e.g.,, if PDU 2 is received at T2 = T1 + 1 ms, and K2=1 ms and K1 =2ms, in this case, time T2+K2 = T2 + 1 ms = T1 + 1 ms +1 ms = T1 +K1 , hence the UPF will receive two PDUs pertaining to different streams at a similar time). The application server may provide additional information in addition to values K to help resolve this potential resolution issue. The application server may also provide a margin of error where the next PDU is expected to arrive at the UPF, to account for jitter / delay variation over N6.

[0121] In examples, the application layer / AF may provide traffic pattern information indicating how the PDU sets from different streams will be multiplexed (e.g., for the lifetime of the application or for a certain period). This traffic pattern information may be used (e.g., by a WTRU, UPF or the RAN). For example, an AF may specify that one or more (e.g., all) PDU sets with odd PDU set sequence numbers belong to stream 1 , while PDU sets with even PDU set sequence numbers belong to stream 2. In examples, AF may specify that streams (e.g., 1 through 3) that the PDU sets belong to, are changed after every 5 PDU sets, identified by the PDU set sequence number within the connection (therefore, PSSN 1 - 5 may belong to stream 1 , PSSN 6- 10 may belong to stream 2 and PSSN 11 -15 may belong to streams, and repeat).

[0122] A multiplexed stream over the QoS flow may be generated by the transport layer (e.g., QUIC layer) of the Application Server. The streams may be in a single end to end connection and have the same IP 5-tuple information. In this case, the UPF may need a mechanism to help identify which PDU sets and which PDUs are from the same stream. Several possible options include, but are not limited to, the following.

[0123] In examples, the transport layer in the Application Server may add an identifier in the stream to help identify the streams. For example, the QUIC layer may use a “Connection ID” to help identify the streams. The PDR provided to the UPF may be expanded to include the “Connection ID” in the Service data flow filter. This may be an indication to the UPF to use the “Connection ID” to help identify the different streams. Alternatively, this may be the value of the “Connection ID” or of a subset of the “Connection ID.”

[0124] In examples, multiplexed flows can be transported over a tunnel between WTRU and UPF, or between an AS and UPF. This can be a multiplexed application substrateover quick encryption (MASQUE) connection, a generic tunneling protocol (GTP) tunnel, or another tunnel protocol. In such cases, the WTRU and / or AS may identify each media stream using MASQUE / GTP / tunnel signaling. For example, a media stream can be transmitted over a MASQUE stream between AS and UPF, when the stream is associated with a media stream ID (e.g., provided in a message at stream initiation time). In examples, a media stream may be transmitted over MASQUE datagrams between AS and UPF, where the datagrams include a context ID that is associated with the media flow ID (e.g., they can be equal, or a mapping can be provided by AS to UPF in a MASQUE message).

[0125] In examples, the UPF may act as a trusted proxy (e.g., a Media over QUIC or RTP over QUIC proxy), which terminates the QUIC connections to WTRU and AS, and forwards PDUs between the connection. The UPF / proxy may have access to metadata not encrypted end to end (e.g., MOQ track ID or RTP headers and extension headers). Such metadata may be used to identify the different streams (e.g., based on payload type or protocol).

[0126] Additional, or alternative “Mechanisms to Identify streams” include but are not limited to the following.

[0127] In examples, the IP layer in the Application Server may add a stream identifier in the header in IP packet including the PDUs of the PDU set. The stream identifier may be a new or existing IP header. For example, the IP layer may use a different Flow Label in the IPv6 packet header for each stream. Additionally, or alternatively the IP layer may use a different ToS / TC in in the IP packet header for each stream (e.g., each stream may have a different differentiated services code point (DSCP) value). The IP layer in the AS may add an IP option or user datagram protocol (UDP) option, including a stream identifier. In any of these cases, the PDR provided to the UPF may be expanded to include the new stream identifier in the Service data flow filter.

[0128] In examples, the streams may be of different types. The types may be based on one or more “Stream Characteristics.” For example, some streams may be PDU set based, and others may be non-PDU set based. Some streams may be periodic, and others may be aperiodic. The UPF may identify a stream based on the type and / or based on a combination of types. For example, Stream 1 is periodic and PDU setbased, Stream 2 is aperiodic, Stream 3 is periodic and non-PDU based. The PDR provided to the UPF may be expanded to include the type (or combination of types) in the Service data flow filter.

[0129] In examples, the application layer may add clues in the PDU sets that would help the UPF identify the streams. The PDR provided to the UPF may be expanded to include the clues in the Service data flow filter. For example, the clue may be some combination of values in the header fields that is unique and may help uniquely identify a stream.

[0130] Streams may be mapped to QoS flows. The PCC rule may have a Service data flow template, which provides a list of service data flow filters. A service data flow filter may include information for matching user plane packets for IP PDU traffic or Ethernet PDU traffic. This is in terms of packet filters. As discussed herein, packet filters may be based on PDRs. The packet filter set may define how the traffic over the N6 interface is mapped to QoS flows. For IP, a “base” packet filter is based on at least any combination of: a source / destination IP address or IPv6 prefix; a source / destination port number; a protocol ID of the protocol above IP / Next header type; a type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask; a Flow Label (IPv6) a Security parameter index; and / or Packet Filter direction. These parameters may be referred to as an IP 5- tuple.

[0131] A value left unspecified in a Packet Filter may match any value of the corresponding information in a packet. An IP address or Prefix may be combined with a prefix mask. Port numbers may be specified as port ranges.

[0132] If the streams are identified by different IP tuple, different Flow Label, or different Type of Service (ToS) and / or Traffic Class, the “base” packet filter set may be used to map the different streams to different QoS flows. For the other “Mechanisms to Identify streams,” the Service data flow template may be modified to include one or more additions to the “base” packet filter, including, but not limited to, the following exemplary additions.

[0133] The Service data flow template may be modified to include a Stream ID. “Stream ID” may refer to a new field in the RTP header extension or in other protocols e.g., MASQUE, QUIC, GTP, tunnel protocol). This may be a value of the “Stream ID.”Additionally, or alternatively, this may be an indication to use this field to identify different streams. In the latter case, UPF may know (e.g., only know) that different “Stream ID” values would correspond to different streams, but the UPF would not be configured with the value of “Stream ID” for these streams.

[0134] The Service data flow template may be modified to include “SSRC” and / or “CSRC.” SSRC and / or CSRC may refer to an existing field in the RTP header. This may be a value of the “SSRC” and / or “CSRC.” Additionally, or alternatively, this may be an indication to use this field to identify different streams. In the latter case, UPF may know (e.g., only know) that different “SSRC” and / or “CSRC” values would correspond to different streams, but the UPF would not be configured with the value of “SSRC” and / or “CSRC” for these streams. For example, if the application server carried forward error correction (FEC) PDUs of different modalities or streams on a single stream, then the Service data flow template may include, in addition to the “base” packet filter, a “Stream ID” field of a certain value x, as well as a “SSRC” field, which will indicate to the UPF to differentiate the FEC PDUs having the same “Stream ID” value x, based on the modality of the PDUs they are used with using FEC. These modalities may have different “SSRC” values.

[0135] The Service data flow template may be modified to include Expected Arrival Time. “Expected Arrival Time” may indicate to the UPF that it should identify the stream based on the expected arrival time of the next PDU set of the stream. The UPF may be configured with a periodicity of the different streams in the end to end to connection. Additionally, or alternatively the UPF may be configured to obtain the expected arrival time by reading the information carried in the RTP header extension.

[0136] The Service data flow template may be modified to include a Connection ID. “Connection ID” may refer to the existing field in the QUIC header. This may be a value of the “Connection ID.” Additionally, or alternatively, this may be an indication to use this field to identify different streams. In the latter case, UPF may know (e.g., only know) that different “Connection ID” values would correspond to different streams, but the UPF would not be configured with the value of “Connection ID” for these streams.

[0137] The Service data flow template may be modified to include Stream Characteristics. “Stream Characteristics” may indicate to the UPF that it should identifythe stream based on one or more stream characteristics. This may be a list of conditions that may need to be matched to identify the stream. For example, conditions may include: whether the stream is PDU set based, whether the traffic over the stream is periodic, if the periodicity is within a certain range, if the PDU set size characteristic is larger than a threshold, if the PDU set characteristic is of a certain priority (e.g., based on PSI), if the stream is a primary stream (or secondary stream), the payload type of the stream, the protocol used, and / or etc. Note that some of these may be specified as a range of values.

[0138] The UPF may perform actions for the PDUs of the identified and mapped streams. Once the UPF identifies the PDUs of a stream and maps these streams to QoS flows, the UPF may send the PDU to the RAN node via a GTP-U tunnel. This may result in multiple streams being multiplexed over the QoS flow. Alternatively, as discussed above, each stream may be assigned its own QoS flow. The UPF may create a GTP-U packet to carry the identified PDU. The UPF may be configured with FARs which tell the UPF how to forward these GTP-U packets to the RAN node and what to include in the headers of these GTP-U packets. In order to assist the RAN node (for example for scheduling, packet discarding, setting CDRX parameters, etc.), the UPF may add PDU set metadata as well as stream metadata in the GTP-U header,

[0139] Stream metadata may include the QoS flow Stream ID (QFSID). The QFSID may be an identifier that uniquely identifies the stream in the QoS flow. The UPF may maintain a mapping of identified stream to QFSID. For example, if the stream is identified based on SSRC, the UPF may maintain a mapping of (IP 5-tuple, SSRC) to QFSID. In examples, if the stream is identified based on DSCP value, the UPF may maintain a mapping of (IP 5-tuple, DSCP) to QFSID. This stream metadata, (e.g., these tuples) may need to be differentiable, or resolvable. For example, if one mapping uses (IP 5-tuple, SSRC = 2, “DSCP”) to QFSID and another mapping uses (IP 5-tuple, “SSRC”) to QFSID mapping, then it can occur that one PDU may be mapped to a different QFSID if a different mapping rule is used. One way to resolve this is by using a precedence value or an order of applying the mapping rules. For example, the (IP 5- tuple, SSRC = 2, “DSCP”) mapping may have a lower precedence (e.g., meaning ahigher priority) than the (IP 5-tuple, “SSRC”) mapping, to allow for further granularity of mapping.

[0140] Stream metadata may include the stream priority. The UPF may examine the PDll set importance (PSI) of one or more (e.g., all) PDU sets multiplexed over the QoS flow and maintain stream priority based on the PSI. For example, this may be based on the highest priority PDU set that is carried on the stream. Additionally, or alternatively, this may be based on the highest priority PDU set that is carried in the last K msec. Additionally or alternatively, this may be based on some weighted average of the priorities of the PDU sets carried over the stream. In one example, the stream priority may be weighted based on the sizes of the PDU sets and the PSI. Alternatively, the stream priority may be provisioned by the AF.

[0141] Stream metadata may include an indication if the stream is a primary stream or a secondary stream. For secondary streams, the metadata may also include the Stream ID of the Primary Stream. For primary streams, the metadata may also include a list of Stream IDs of the secondary streams. For example, the secondary stream may be an FEC stream, and the primary stream may be a video modality stream.

[0142] Stream metadata may include an indication of how to change a configured PDU set QoS parameter. The QoS profile provided to the RAN node may have a single set of PDU set QoS requirements. However, the streams may require different PDU set QoS requirements. The UPF may include in the stream metadata, information to allow the RAN node to adjust its configured PDU set QoS requirements for the data on the incoming stream. For example, a QoS flow may have multiple streams, one of which does not require PSIHI (e.g., stream x). The RAN node may be configured with a QoS profile with PDU set QoS requirements that indicate that PSIHI is required (e.g., as most streams of the QoS flow require it). Upon identifying and mapping a PDU of stream x, the UPF may include stream metadata to indicate that the RAN node does not need to apply PSIHI for this particular PDU set. This may be in a new GTP-U header. For example “PSIHI_required’ may be set to ‘FALSE.’ In examples, a QoS flow may have multiple streams one of which has a very low PSDB (e.g., stream y). The RAN node may be configured with a QoS profile with PDU set QoS requirements that indicate the PSDB required for most streams of the QoS flow. Upon identifying and mapping a PDUof stream y, the UPF may include stream metadata to indicate that the RAN node should reduce the PSDB by K msec or by a factor of K. This may be in a new GTP-ll header. For example “PSDB_scaled’ may be set to ‘K.’

[0143] Stream metadata may include an indication of whether the PDU should follow the PDU set QoS requirements configured in the QoS profile. For example, some streams in the multiplexed QoS flow may be of very low importance and may not need PDU set based QoS handling. If so, after identifying and mapping the PDU to a QoS flow, the UPF may add a new GTP-U header indicating that this PDU is from a stream that does not need PDU set based QoS handling and should therefore not follow the configured PDU set QoS requirements. For example, “PDUSetHandling” may be set to ‘FALSE.’

[0144] In addition, the UPF may perform new processing to adjust the PDU set metadata to efficiently and fairly combine different streams in a multiplexed QoS flow. This is in contrast to when the UPF reads the PDU set information from the RTP header and repeats this information in the GTP-U header.

[0145] In a PDU set metadata adjustment, the UPF may combine a per-stream end of data burst detection and / or signaling into a single End of Data Burst indication (e.g., carried in the GTP-U header). As the streams are multiplexed, an end of burst on one stream (e.g., a stream end of burst) does not necessarily mean that the RAN node should expect an end of burst on the QoS flow (a QoS flow end of burst). In fact, before the QoS flow end of burst, the RAN node may need to receive additional PDUs coming from a burst in a different stream. The UPF may have access to one or more (e.g., all) the streams that are multiplexed. The UPF may be able to determine when a true QoS flow end of burst occurs. The UPF may then include an End of Data Burst indication when it determines a QoS flow end of burst. For example, the UPF may maintain an expected “time to next PDU” for each multiplexed stream, and the UPF may determine to send a QoS flow end of burst on the last PDU transmitted to the RAN, when the “time to next PDU” is above a threshold on one or more (e.g., all) multiplexed streams.

[0146] In a PDU set metadata adjustment, the UPF may combine per-stream priority and the RTP extension header PSI to obtain a PSI to be included in the GTP-U header. In examples, the PSI in the RTP extension header may apply to the RTP PDU and be relative to one or more (e.g., all) multiplexed streams in an RTP session. Each streammay have its own stream priority, relative to other streams in the same multiplexed QoS flow. This may be known to the UPF through configuration from SMF. The UPF may then determine the PSI value to include in the GTP-U header based on the PSI in the RTP extension header of the received PDU, as well as some stream characteristics (e.g., such as stream priority or whether the stream is a primary stream or secondary stream). For example, the PSI may indicate that the PDU is of high importance. However, this PDU may be from a stream that is low importance (e.g., found from the stream priority information). The UPF may determine the PSI value to include in the GTP-U header based on some rules. In an example of PSI adjustment, the UPF may determine whether the PDU is from a high priority stream and set the GTP-U PSI value equal to the PSI of the RTP PDU (e.g., as found in the RTP extension header). In examples of PSI adjustment, if the PDU is from a low priority stream, the GTP-U PSI value may be set to a value lower than the PSI of the RTP PDU e.g., as found in the RTP extension header).

[0147] In examples of PSI adjustment, the UPF may calculate the GTP-U PSI to be the sum of the stream priority and the PSI of the PDU (e.g., as found in the RTP extension header). When time correlation information of PDU sets from different streams are provided, the PDU sets that are correlated in time and / or that need to be delivered within a delay tolerance limit, may be multiplexed into the same QoS flow. Note that the processing described for the UPF for DL traffic also applies to the WTRU for UL traffic.

[0148] Actions may be performed at the RAN node to manage QoS flows with multiplexed streams. A RAN node may manage QoS for QoS flows with multiplexed streams. The RAN node may be provided with the QoS profile, which tells the RAN node the QoS requirements of the QoS flow. These QoS requirements may be used for efficient scheduling over the access network and to handle cases of congestion over the access network.

[0149] In some systems, the RAN node is provided with a single set of QoS requirements that apply to traffic (e.g., all traffic) over the QoS flow. These requirements can include but are not limited to: 5G QoS Identifier (5QI); and Allocation and Retention Priority (ARP). For each QoS Flow, the QoS profile may also include the QoS parameters such as the PDU Set Delay Budget (PSDB), the PDU Set Error Rate(PSER) and / or the PDll Set Integrated Handling Information (PSIHI). For each Non- GBR QoS Flow (e.g., each Non-GBR QoS Flow only), the QoS profile may also include the QoS parameter Reflective QoS Attribute (RQA). For each GBR QoS Flow (e.g., each Non-GBR QoS Flow only), the QoS profile may also include QoS parameters such as the Guaranteed Flow Bit Rate (GFBR) for uplink (UL) and downlink (DL); and / or the Maximum Flow Bit Rate (MFBR) for UL and DL. In the case of a GBR QoS Flow (e.g., a GBR QoS Flow only), the QoS profile may also include one or more of the QoS parameters: Notification control; and / or Maximum Packet Loss Rate for UL and DL.

[0150] For multiplexed streams, a QoS flow may carry PDUs that have different QoS requirements. To handle this, there are QoS profile options.

[0151] In the QoS profile options, the QoS profile may have a single set of PDU Set QoS requirements. For example, this may be based on any combination of: the stream with the most stringent QoS requirements; the stream with the highest priority; and / or the PDU set QoS requirements of the majority of the streams in the QoS flow. Alternatively, or additionally, the network may be configured to always provide the QoS requirements of a stream with PDU sets enabled. Additionally, or alternatively, the SMF may determine an optimum QoS profile based on the QoS requirements of one or more (e.g., all the) streams in the QoS flow. For example, it may determine that stream 1 has the highest Guaranteed Flow Bit Rate (GFBR) and stream 2 has the lowest PDU Set Error Rate (PSER). So, the QoS profile would use this highest GFBR and this lowest PSER.

[0152] In the QoS profile options, the QoS profile may have a list of QoS parameters, one for each stream in the QoS flow. The QoS profile may have a common set of QoS parameters, (e.g., 5QI, ARP, GFBR, etc.). In addition, it may have a set of QoS parameters that are stream based, for example those based on PDU set QoS parameters.

[0153] These stream-based PDU Set QoS parameters may be differentiated per stream number. For example, the QoS profile may have a list of PDU set QoS parameters that is differentiated by stream number. In examples, the QoS profile of a case with K streams in the QoS flow may have a list of PDU set QoS parameters which is differentiated for a first stream, stream 1 ; a second stream, stream 2; and for eachstream up to and / or including stream K. For example: stream 1 (e.g., PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), PDU Set Integrated Handling Information (PSIHI)); stream 2 (e.g., PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), PDU Set Integrated Handling Information (PSIHI)); . . . stream K (e.g., PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), PDU Set Integrated Handling Information (PSIHI)).

[0154] Additionally, or alternatively, the PDU set QoS parameters may be grouped. For example, the QoS profile may have a list of PDU set QoS parameters that is differentiated by group number. In examples, the QoS profile of a case with K groups may have a list of PDU set QoS parameters which is differentiated for a first group, group 1 ; a second group, group 2; and for each stream group up to and / or including group K. For example: Group 1 (e.g., PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), PDU Set Integrated Handling Information (PSIHI)); group 2 (e.g., PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), PDU Set Integrated Handling Information (PSIHI)); a. . . group K ((e.g., PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), PDU Set Integrated Handling Information (PSIHI)).

[0155] Each stream may follow the PDU set QoS requirements of a certain group. After identifying a stream, the UPF may include a group indication in the GTP-U header. The RAN node may then apply the appropriate PDU set QoS requirement based on the group.

[0156] The PDU Set related QoS parameters may include a Partial PDU set handling indication. The Partial PDU set handling indication may indicate that even if a portion of the PDUs of a PDU set is received the PDU set is relevant and can be recovered.These parameters may include error / loss ratio(s).

[0157] Additional information may be useful to a RAN node for multiplexed streams. The SMF may provide the RAN node an indication of how the streams in a QoS flow are related. For example, the SMF may indicate the PDUs of a first stream, stream 1 , require (e.g., can be associated with) the PDUs of a second stream, stream 2. Additionally, or alternatively, the SMF may provide an indication of which stream is a Primary stream, and which streams are Secondary streams. The SMF may explicitly provide the PDU set QoS requirements for the secondary streams, or the SMF mayindicate that these are implicitly related to the PDU set QoS requirements of the Primary stream. This could also be based on a percentage of the Primary PDU set QoS requirements. For example, the Secondary PDU Set QoS requirements may be K% of the Primary PDU set QoS requirements.

[0158] The SMF may provide temporal requirements between streams. For example, a WTRU may receive one or more of: a video stream, an audio stream, and / or a haptic stream. These streams may have a temporal relationship. For example, the video may show a baseball coming towards the user. The haptic stream indicating the sensation of catching the ball may be time synchronized with video showing the baseball entering the glove. The SMF may be configured with a maximum delay tolerance between streams.

[0159] An RAN node may use the QoS requirements of multiplexed streams. In examples, the RAN node may be configured to know the QoS requirements of each of the multiplexed streams as well as the QoS characteristics of each of the multiplexed streams. It may use this information to manage the WTRUs CDRX configuration (e.g., it may keep the WTRU awake based on the periodicity of the streams and the priority of the streams).

[0160] In examples, the RAN node may use a Stream Priority to determine which stream of a QoS flow to process. In some systems, the PSI is used to indicate the importance of a PDU set in relation to another PDU set in the same QoS flow.However, in such systems, the assumption is that the PDU sets are from a single stream. In cases with multiple streams, a second priority mechanism may be used. The second priority mechanism may indicate the priority of one stream with respect to another stream. In examples, the RAN node may perform scheduling of PDUs based on the relative stream importance. In examples, in cases of congestion, a RAN node may discard PDUs from lower priority streams. Furthermore, within the higher priority streams, the RAN node may use the PSI to determine which PDU sets within the stream to discard. In examples, the RAN node may use one or more of: Stream Priority, PSI, PSIHI, PSDB, and / or PSER to determine which PDU sets to prioritize or to determine if any PDU sets may be dropped. For example, a PDU set may be of highpriority, but the RAN node may know that it will not be able to meet the PSDB. In such a case, it may select to transmit a lower priority PDU set.

[0161] In examples, the RAN node may use the delay tolerance between streams to better schedule downlink traffic. If a PDU set on stream 2 does not meet the delay tolerance, it may be deleted by the RAN node. Alternatively, the RAN node may use this as a condition to change the stream priority.

Claims

CLAIMS:1 . A first network node comprising a processor, wherein the processor is configured to: receive configuration information from a second network node, the configuration information comprising one or more packet detection rules (PDRs), wherein the one or more PDRs are configured to identify a protocol data unit (PDU) based on an internet protocol (IP) 5-tuple associated with the PDU, and one or more of a synchronization source (SSRC), a payload type, or a protocol associated with the PDU; receive a plurality of PDUs, wherein a first PDU and a second PDU of the plurality of PDUs are associated with a single internet protocol (IP) 5-tuple value; identify a first extended reality (XR) stream for the first PDU and a second XR stream for the second PDU by applying the one or more PDRs to the respective first PDU and the second PDU; and map the first XR stream to a first Quality of Service (QoS) flow and the second XR stream to a second QoS flow.

2. The first network node of claim 1 , wherein the processor is further configured to: send a packet comprising an indication of a PDU set QoS requirement associated with the first XR stream or the second XR stream.

3. The first network node of claim 2, wherein the packet is a general packet radio service tunneling protocol - user plane (GTP-U) packet.

4. The first network node of claim 2, wherein the packet further comprises an indication of a characteristic of the first XR stream or the second XR stream.

5. The first network node of claim 1 , wherein the first XR stream is associated with a video data flow, and wherein the second XR stream is associated with an audio data flow.

6. The first network node of claim 1 , wherein the configuration information further comprises one or more forward action rules (FARs), wherein the processor is further configured to forward the first XR stream or the second XR stream in accordance with the one or more FARs.

7. The first network node of claim 6, wherein the one or more FARs further comprise information for creating a general packet radio service tunneling protocol - user plane (GTP-U) packet header.

8. A method to be used by a network node, the method comprising: receiving configuration information from a second network node, the configuration information comprising one or more packet detection rules (PDRs), wherein the one or more PDRs can be applied to identify a PDU based on an IP 5-tuple associated with the PDU, and one or more of a synchronization source (SSRC), a payload type, or a protocol associated with the PDU; receiving a plurality of protocol data units (PDUs), wherein a first PDU and a second PDU of the plurality of PDUs are associated with a single internet protocol (IP) 5-tuple value; identifying a first XR stream for the first PDU and a second XR stream for the second PDU by applying the one or more PDRs to the first PDU and the second PDU; and mapping the first XR stream to a first Quality of Service (QoS) flow and the second XR stream to a second QoS flow.

9. The method of claim 8, wherein the processor is further configured to: send a packet comprising an indication of a PDU set QoS requirement associated with the first XR stream or the second XR stream.

10. The method of claim 9, wherein the packet is a general packet radio service tunneling protocol - user plane (GTP-U) packet.11 . The method of claim 9, wherein the packet further comprises an indication of a characteristic of the first XR stream or the second XR stream.

12. The network node of claim 8, wherein the first XR stream is associated with a video data flow, and wherein the second XR stream is associated with an audio data flow.

13. The method of claim 8, wherein the configuration information further comprises one or more forward action rules (FARs), the method further comprising: forwarding the first XR stream or the second XR stream in accordance with the one or more FARs.

14. The network node of claim 13, wherein the one or more FARs further comprise information for creating a general packet radio service tunneling protocol - user plane (GTP-U) packet header.

15. A wireless transmit / receive unit (WTRLI) comprising a processor, wherein the processor is configured to: receive configuration information from a network node, the configuration information comprising one or more packet detection rules (PDRs), wherein the one or more PDRs can be applied to identify a PDU based on an IP 5-tuple associated with the PDU, and one or more of a synchronization source (SSRC), a payload type, or a protocol associated with the PDU; generate a plurality of protocol data units (PDUs), wherein a first PDU and a second PDU of the plurality of PDUs are associated with a single internet protocol (IP) 5-tuple value; identify a first XR stream for the first PDU and a second XR stream for the second PDU by applying the one or more PDRs to the first PDU and the second PDU; and map the first XR stream to a first Quality of Service (QoS) flow and the second XR stream to a second QoS flow.

16. The WTRLI of claim 15, wherein the processor is further configured to: send a packet comprising an indication of a PDU set QoS requirement associated with the first XR stream or the second XR stream.

17. The WTRLI of claim 15, wherein the configuration information further comprises one or more packet filters, and wherein the processor is further configured to map the first XR stream to the first QoS flow and the second XR stream to the second QoS flow based on the one or more packet filters.

18. The WTRLI of claim 16, wherein the packet further comprises an indication of a characteristic of the first XR stream or the second XR stream.

19. The WTRLI of claim 15, wherein the first XR stream is associated with a video data flow, and wherein the second XR stream is associated with an audio data flow.

20. The WTRLI of claim 16, wherein the packet further comprises a stream identifier to identify the first XR stream or the second XR stream.

Images