[go: up one dir, main page]

WO2025174890A1 - Configuration et rapport de rejet d'unité de données par paquets actifs pour des applications de réalité étendue - Google Patents

Configuration et rapport de rejet d'unité de données par paquets actifs pour des applications de réalité étendue

Info

Publication number
WO2025174890A1
WO2025174890A1 PCT/US2025/015598 US2025015598W WO2025174890A1 WO 2025174890 A1 WO2025174890 A1 WO 2025174890A1 US 2025015598 W US2025015598 W US 2025015598W WO 2025174890 A1 WO2025174890 A1 WO 2025174890A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
indication
discarding
pdus
report
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2025/015598
Other languages
English (en)
Inventor
Achref METHENNI
Michael Starsinic
Xavier De Foy
Rocco Di Girolamo
Srinivas GUDUMASU
Michel Roy
Kevin Di Lallo
Magurawalage Chathura Madhusanka Sarathchandra
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025174890A1 publication Critical patent/WO2025174890A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/31—Flow control; Congestion control by tagging of packets, e.g. using discard eligibility [DE] bits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • the device may receive a packet data unit (PDU) message that includes a PDU (e.g., a first PDU).
  • the PDU message may include a header.
  • the header may include the reference ID and/or a QoS flow ID (QFI).
  • QFI QoS flow ID
  • the device may determine, based on the QoS profile, that the PDU is to be discarded (e.g., actively discarded).
  • the device may discard the PDU, and/or send a report to a wireless transmit/receive unit (WTRU).
  • WTRU wireless transmit/receive unit
  • the report may include the reference ID and/or an indication that the PDU has been discarded (e.g., actively discarded).
  • the QoS profile may further include an indication of a content ratio value.
  • the content ratio value may indicate a minimum number of PDUs required to reconstruct (e.g., the minimum number of PDUs required for a WTRU application to use application layer forward error correction (AL- FEC) to recover) a PDU set.
  • the device may determine, based on the content ratio value, that one or more PDUs of the PDU set are to be discarded.
  • the device may discard the determined one or more PDUs.
  • the report may further include an indication that the one or more PDUs have been discarded.
  • the QoS profile may include a QFI.
  • the device may determine, based on the indication to perform the discarding and the QFI, that the discarding is to be performed on one or more PDUs associated with the QoS flow (e.g., the QoS flow may be associated with the QFI).
  • the device may determine the one or more PDUs based on the reference ID associated with the QoS flow.
  • the QoS profile may include an indication of a PDU set importance value.
  • the device may determine, further based on the PDU set importance value, that the PDU is to be discarded.
  • the QoS profile may include an indication that the discarding is to be performed for a PDU set that has a size equal to or larger than a PDU set size threshold and that the discarding is not to be performed for a PDU set that has a size smaller than the PDU set size threshold.
  • the QoS profile may further include an indication of a period associated with determining and reporting a number of PDUs that are to be discarded during the period.
  • the report to the WTRU may be sent per the period.
  • the report may further include an indication of the number of PDUs that have been discarded during the period.
  • the QoS profile may further include an indication to send the report via a radio resource control (RRC) message.
  • RRC radio resource control
  • the report may further indicate at least another PDU that has been discarded.
  • the report may further include an indication that the one or more PDUs were not dropped due to network congestion.
  • the device may determine (e.g., at a later time) an occurrence of the network congestion.
  • the device may disable the discarding based on the occurrence of the network congestion.
  • the device may send a report that includes an indication that the discarding has been disabled.
  • the device may be included in a base station.
  • 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;
  • WTRU wireless transmit/receive unit
  • 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. 1 A according to an embodiment;
  • RAN radio access network
  • CN core network
  • 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
  • FIG. 2 illustrates an example for configuring RAN to perform and report active PDU discarding.
  • FIG. 3 illustrates an example of activation/deactivation of PDU active dropping feature by the
  • FIG. 4 illustrates an example of PDU active dropping feature, for example, by the RAN.
  • 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.
  • 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.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a ON 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.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • 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 I nternet 110, and/or the other networks 112.
  • 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.
  • 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.
  • BSC base station controller
  • RNC radio network controller
  • 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.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e. , one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • 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).
  • RAT radio access technology
  • 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.
  • 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).
  • 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).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • 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).
  • POTS plain old telephone service
  • 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.
  • 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.
  • 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).
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • 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.
  • GPS global positioning system
  • 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.
  • 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.
  • 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.
  • SIM subscriber identity module
  • SD secure digital
  • 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).
  • 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 locationdetermination method while remaining consistent with an embodiment.
  • a base station e.g., base stations 114a, 114b
  • the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.
  • 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.
  • 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.
  • FM frequency modulated
  • 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.
  • 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.
  • 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 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).
  • the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • 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.
  • 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.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • 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.
  • the CN 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.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may serve as a control node.
  • 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.
  • 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.
  • 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.
  • 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.
  • the other network 112 may be a WLAN.
  • 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).
  • the DLS may use an 802.11e 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.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • 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.
  • 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.
  • 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.
  • 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.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting 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).
  • MAC Medium Access Control
  • 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.11 af 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
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • 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.
  • 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.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • 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.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • 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.
  • 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.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • 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.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • 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).
  • TTIs subframe or transmission time intervals
  • 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.
  • 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).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • 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.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • 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.
  • 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.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 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.
  • SMF Session Management Function
  • 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.
  • 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.
  • 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.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • the AMF 182 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 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 UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.
  • 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.
  • the CN 115 may facilitate communications with other networks.
  • 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.
  • IMS IP multimedia subsystem
  • 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.
  • 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.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • 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.
  • 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 performing testing using over-the-air wireless communications.
  • 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.
  • 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 testing 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.
  • RF circuitry e.g., which may include one or more antennas
  • a device may receive a quality of service (QoS) profile.
  • the QoS profile may include one or more of an indication to perform discarding (e.g., active discarding), a reference identifier (ID) associated with a QoS flow, or an indication to report the discarding.
  • an indication to perform discarding e.g., active discarding
  • ID reference identifier
  • the device may receive a packet data unit (PDU) message that includes a PDU (e.g., a first PDU).
  • the PDU message may include a header.
  • the header may include the reference ID and/or a QoS flow ID (QFI).
  • QFI QoS flow ID
  • the device may determine, based on the QoS profile, that the PDU is to be discarded (e.g., actively discarded).
  • the device may discard the PDU, and/or send a report to a wireless transmit/receive unit (WTRU).
  • WTRU wireless transmit/receive unit
  • the report may include the reference ID and/or an indication that the PDU has been discarded (e.g., actively discarded).
  • the QoS profile may further include an indication of a content ratio value.
  • the content ratio value may indicate a minimum number of PDUs required to reconstruct (e.g., the minimum number of PDUs required for a WTRU application to use application layer forward error correction (AL- FEC) to recover) a PDU set.
  • the device may determine, based on the content ratio value, that one or more PDUs of the PDU set are to be discarded.
  • the device may discard the determined one or more PDUs.
  • the report may further include an indication that the one or more PDUs have been discarded.
  • the QoS profile may include a QFI.
  • the device may determine, based on the indication to perform the discarding and the QFI, that the discarding is to be performed on one or more PDUs associated with the QoS flow (e.g., the QoS flow may be associated with the QFI).
  • the device may determine the one or more PDUs based on the reference ID associated with the QoS flow.
  • the QoS profile may include an indication of a PDU set importance value.
  • the device may determine, further based on the PDU set importance value, that the PDU is to be discarded.
  • the QoS profile may include an indication that the discarding is to be performed for a PDU set that has a size equal to or larger than a PDU set size threshold and that the discarding is not to be performed for a PDU set that has a size smaller than the PDU set size threshold.
  • the QoS profile may further include an indication of a period associated with determining and reporting a number of PDUs that are to be discarded during the period.
  • the report to the WTRU may be sent per the period.
  • the report may further include an indication of the number of PDUs that have been discarded during the period.
  • the QoS profile may further include an indication to send the report via a radio resource control (RRC) message.
  • RRC radio resource control
  • the report may further indicate at least another PDU that has been discarded.
  • the report may further include an indication that the one or more PDUs were not dropped due to network congestion.
  • the device may determine (e.g., at a later time) an occurrence of the network congestion.
  • the device may disable the discarding based on the occurrence of the network congestion.
  • the device may send a report that includes an indication that the discarding has been disabled.
  • the device may be included in a base station.
  • Systems, methods, and instrumentalities are described herein related to an active discarding technique.
  • a device may receive a quality of service (QoS) profile.
  • QoS quality of service
  • the notification information may be sent to a wireless transmit/receive unit (WTRU) in a radio resource control (RRC) message.
  • WTRU wireless transmit/receive unit
  • RRC radio resource control
  • the one or more downlink packets may be received in a general packet radio service tunnelling protocol user plane (GTP-U) message.
  • GTP-U general packet radio service tunnelling protocol user plane
  • An RAN node may be configured by an SMF, for example, based on an indication from the WTRU application at the WTRU, to actively drop one or more PDUs of a PDU set (e.g., according to a certain content ratio).
  • the RAN may be configured to report or notify the WTRU of the dropped PDU(s).
  • the configuration may be received in the QoS profile that may include one or more of the active dropping indication, a content ratio value, as well as a reference ID to allow the RAN and WTRU to identify the traffic being actively dropped.
  • the RAN may inform the SMF (e.g., via an N2 message) and/or the WTRU (e.g., directly via an RRC message), that the active dropping feature is enabled. If the RAN detects certain event(s) (e.g., a congestion event), the RAN may (e.g., later on) disable the active dropping feature and/or inform the SMF (e.g., via an N2 message) or the WTRU (e.g., directly via an RRC message).
  • certain event(s) e.g., a congestion event
  • the RAN may (e.g., later on) disable the active dropping feature and/or inform the SMF (e.g., via an N2 message) or the WTRU (e.g., directly via an RRC message).
  • the term “active dropping” and the term “active discarding” may be used interchangeably.
  • the term enabli ng/disabli ng of a feature and the term activating/deactivating of a feature may be used interchangeably.
  • a PDU may be used to refer to a packet data unit or a protocol data unit, and “packet data unit” and “protocol data unit” may be used interchangeably.
  • a RAN node may be configured to apply PDU active discarding and/or send reporting/notification to the WTRU.
  • Active discarding is related to resource preservation and/or optimization, for example, as opposed to discarding due to network congestion.
  • a RAN node may perform one or more of the following actions.
  • the RAN node may (e.g., as shown at 2c of FIG. 2) receive a QoS profile (e.g., from an SMF) including information related to PDU active discarding.
  • a QoS profile may indicate one or more QoS attributes associated with a QoS flow (e.g., a QoS flow carrying one or more service flows).
  • a RAN node may dynamically enabled/disable a PDU active discarding feature based on events (e.g., such as network congestion).
  • a RAN node may perform one or more of the following actions.
  • a RAN node may (e.g., as shown at 0 of FIG. 3) be configured (e.g., by the SMF) to apply PDU active discarding.
  • Configuration may be performed, for example, by receiving a QoS profile with active discarding information (e.g., including a content ratio).
  • a RAN node may (e.g., as shown at Option 1 , 1 a or Option 2, 2a of FIG. 3) determine to enable the PDU active dropping feature.
  • XR media may be generated, encoded, and/or delivered (e.g., by an XR server) depending on the adaptive media request sent by an XR device.
  • the device may work in one or more (e.g., two) channels.
  • a channel e.g., a first channel
  • a channel e.g., a second channel
  • a channel may use the tracking sensors to collect 3 degrees of freedom (3DoF) parameters, and translate them into an adaptive media request which may be sent to an XR server by using a delivery system (e.g., 5GS delivery system).
  • a delivery system e.g., 5GS delivery system
  • a base station may be the network entity (e.g., in the 5G system) that is responsible for performing PDU set based QoS handling and/or related functionality on downlink data.
  • a base station that provides PDU set based QoS handling may be configured to consider (e.g., be enhanced to consider) whether traffic in a PDU set is protected, for example, by AL-FEC.
  • the base station may be configured with the content ratio of a PDU set (e.g., each PDU set).
  • the base station may be (e.g., may need to be) configured with an AL-FEC awareness based on input from an application.
  • the base station may start dropping packets (e.g., because the base station may know that some packets are not needed to recover the data).
  • the application may detect that packets are being dropped and/or conclude that it is to use (e.g., needs to use) a lower bit rate or more FEC (e.g., inaccurately assuming a congestion or low radio quality).
  • the Application may be (e.g., may need to be) informed when the base station actively drops PDUs, for example, based on aspects such as AL-FEC content ratio.
  • the 5GS may support a feature where the 5GS informs an application in the WTRU or AS that packets are discarded based on FEC related handling or due to congestion.
  • One or more examples herein may be used to describe how a RAN node that supports PDU active dropping feature may be configured to use the active dropping feature, how the RAN may apply the feature and/or report discarded PDUs information to the WTRU.
  • One or more examples herein may be used to describe how the RAN may adaptively enable or disable the PDU active discarding feature, for example, based on certain events or conditions such as network congestion.
  • RAN configuration and reporting of PDU active discarding may be implemented.
  • a WTRU application may send an indication that the feature (e.g., the active dropping feature) may be used and/or supported and may include a content ratio value and/or reporting parameters that are applicable or acceptable to the WTRU application.
  • the 5GS may receive this indication from the WTRU and determine to configure the serving RAN node of such information (e.g., the SMF may send the serving RAN node an indication indicating that the active dropping feature may be used and/or supported).
  • the RAN node may use the PDU active dropping feature and/or report related dropping information, for example, to the WTRU.
  • FIG. 2 illustrates an example for configuring RAN to perform and report active PDU discarding.
  • a PDU session between WTRU and the 5GS may be established to carry user plane traffic for extended reality and media services (XRM).
  • XRM extended reality and media services
  • the WTRU may be triggered to initiate a packet data unit (PDU) session modification procedure, e.g., to setup/modify quality of service (QoS) flow for XRM traffic.
  • PDU packet data unit
  • QoS quality of service
  • An application e.g., the application hosted in WTRU
  • the WTRU may determine (e.g., based on an indication from the application hosted on WTRU) that application layer forward error correction (AL-FEC) is enabled and/or may determine a content ratio.
  • the WTRU may initiate a PDU session modification procedure and/or send a request for QoS treatment for the downlink (DL) flow.
  • the WTRU may indicate requested QoS rules and/or requested QoS flow descriptions.
  • the WTRU may include Requested QoS rules IE indicating requested QoS rules or Requested QoS flow descriptions IE indicating requested QoS flow descriptions.
  • the Requested QoS rules IE may include one or more packet filters which describe the service data flows requested by the WTRU.
  • the QoS parameters may be specified in the Requested QoS flow descriptions IE.
  • the QoS parameters may include the content ratio.
  • a content ratio value may indicate the ratio of PDUs of the PDU set requested by the WTRU to be able to reconstruct the original content.
  • a request (e.g., the PDU session modification request as described at 1 b of FIG. 2) may include an indication that a report or notification about actively discarded PDUs related to AL-FEC is to be used (e.g., is needed).
  • the request may include a period over which to account for actively discarded PDUs and send the related report.
  • the request may indicate that the RAN is to (e.g., needs to) send a report to the WTRU regarding actively dropped PDUs every 10 seconds.
  • a message (e.g., the message for sending the PDU session modification request) may include a size or threshold (value), to indicate to send a notification if the number of actively discarded PDUs related to FEC reaches the threshold value.
  • the message may indicate that the RAN is to send a notification to the WTRU if 100 PDUs were actively discarded, or every time 100 PDUs are discarded.
  • the message may include a size or threshold value per period. For example, the message may indicate that RAN is to send a notification to WTRU if 100 PDUs were actively dropped over 3 seconds.
  • the access and mobility management function may receive the WTRU request (e.g., the PDU session modification request) and forward the WTRU request to the serving session management function (SMF).
  • WTRU request e.g., the PDU session modification request
  • SMF serving session management function
  • the SMF may configure a user plane function (UPF) (e.g., the UPF in FIG. 2) and radio access network (RAN) (e.g., the RAN in FIG. 2).
  • UPF user plane function
  • RAN radio access network
  • the SMF may indicate (e.g., may interact with the PCF to indicate) the requested QoS parameters for the traffic flow of interest.
  • the SMF may provide an indication (e.g., to the policy control function (PCF)) that AL-FEC is enabled for this traffic flow (e.g., along with active PDU discarding parameters that were provided in the request at 1 of FIG. 2).
  • PCF policy control function
  • the UPF may be configured with N4 rules.
  • the N4 rules may include, for example, an association between the packet filter for the traffic flow of interest, and the reference ID (e.g., the reference ID derived by the SMF).
  • the UPF may use this indication (e.g., an indication included in the N4 rules) to detect the traffic flow of interest and/or add the reference ID (e.g., in the GTP-U header of the packet when sending it to the RAN over the user plane).
  • the SMF may send the N4 rules to the UPF.
  • the SMF may update the QoS profile for the RAN, for example, with information related to active PDU discarding.
  • the QoS profile may include an indication indicating that active PDU discarding may take place for a certain QoS flow (e.g., with a QoS flow ID (QFI), which may, for example, be included in a header of a PDU message).
  • QFI QoS flow ID
  • the QoS profile may include (e.g., additionally include) a content ratio value (e.g., the content ratio value for the active discarding for the QoS flow). This value (e.g., the content ratio value) may be derived from the content ratio received by the SMF from the WTRU and/or equal to (e.g., set to be equal to) the content ratio received by the SMF from the WTRU.
  • the QoS profile may include a reference ID (e.g., a reference ID associated with the PDU active discarding).
  • the reference ID e.g., the reference ID associated with a QoS flow
  • the reference ID may be used (e.g., by the RAN) to determine which PDU(s) or PDU set(s) of the QoS flow to apply active discarding to.
  • the QoS profile may include, for the QoS flow, multiple reference IDs (e.g., two reference IDs, one for each traffic flow) and the associated content ratio for active discarding (e.g., the reference ID may be included in the GTP-U header of the PDUs of the PDU set eligible for active discarding.)
  • multiple reference IDs e.g., two reference IDs, one for each traffic flow
  • the associated content ratio for active discarding e.g., the reference ID may be included in the GTP-U header of the PDUs of the PDU set eligible for active discarding.
  • the SMF may include (e.g., additionally include) an indication (e.g., a new indication) with the reference ID in the QoS profile.
  • the indication may indicate to the RAN to send notification information associated with active discarding. For example, the indication may tell the RAN that it needs to send an RRC message/report to the WTRU to indicate how much data has been intentionally dropped not due to congestion(s)).
  • the notification information (e.g., the report) may include the reference ID.
  • the indication (e.g., the new indication) may include a period over which the RAN may monitor and/or send the notification information (e.g., the RRC message/report) to the WTRU, for example, regarding actively dropped PDUs.
  • the indication may include (e.g., additionally include) a threshold value to indicate, for example, that if the number of actively discarded PDUs reaches this threshold value, the RAN is to send (e.g., needs to send) an RRC message/notification to the WTRU.
  • the threshold value may indicate, for example, that if the number of PDUs actively dropped within a certain period x reaches a certain value, the RAN is to (e.g., needs to) stop actively dropping for that time period/window (e.g., the quota for actively dropping for that time window is reached).
  • the RAN node may stop actively dropping for a certain amount of time, for example, before it may start actively dropping again.
  • the SMF may send a PDU session modification command (e.g., to the WTRU) and/or include the reference I D(s).
  • downlink data may arrive at (e.g., come to) the base station.
  • the base station may receive the downlink data.
  • the UPF may send a message (e.g., the GTP-U message) with the data packet (e.g., a PDU message may be sent) and/or reference ID to the RAN node.
  • a message e.g., the GTP-U message
  • the data packet e.g., a PDU message may be sent
  • the bases station may determine to drop one or more packets according to the content ratio.
  • the RAN may use (e.g., additionally use) the indication (e.g., the new indication) in the QoS profile to determine to send notification information (e.g., an RRC message/report) to the WTRU.
  • the RAN may use the indication to determine if the condition(s) to send the notification information (e.g., an RRC message/report) to the WTRU are met.
  • the RAN may determine, if a period has passed, to send the notification information to the WTRU.
  • the notification information e.g., an RRC message/report
  • the RAN may send notification information (e.g., an RRC message/report) to the WTRU.
  • the notification information (e.g., the report) may include the reference ID.
  • the notification information (e.g., the report) may indicate, for example, the total number of actively dropped PDUs within a time window.
  • the notification information may include (e.g., additionally include) a notification or indication that the number of actively discarded PDUs has reached the threshold value.
  • the notification information e.g., the message
  • the period over which this threshold value has been reached e.g., 200 PDUs were actively dropped, the threshold of 200 is reached, and it took 2 seconds to reach this threshold.
  • the WTRU may send the notification information (e.g., the message) to the WTRU application (e.g., XR).
  • the WTRU application e.g., the XR application
  • the WTRU application may use the notification information to determine whether and/or how to send adaptive media request(s).
  • the WTRU application may use the notification information (e.g., the message) to determine that a content ratio may be updated (e.g., the content ratio provided earlier may need to be updated, for example, the content ratio may be increased, meaning that fewer PDUs are recommended to be actively dropped by the 5GS, without changing the codec setting, bit rate or other parameters).
  • the WTRU application may determine (e.g., using the report) that missing packets were intentionally dropped by the network (e.g., not due to network congestion) and, therefore, application layer configuration(s) may not need to be changed.
  • the WTRU may (e.g., once the WTRU receives the new content ratio) send a content ratio value (e.g., the new content ratio value) to the SMF, for example, using a PDU session modification procedure.
  • a content ratio value e.g., the new content ratio value
  • Active discarding activation/deactivation may be performed, for example, during network congestion(s).
  • An example for how an RAN node may inform the 5GS (e.g., the SMF) that it supports PDU active discarding feature(s) and/or that the feature(s) is enabled may be described herein.
  • the example e.g., the procedure
  • the example may show how the 5GS (e.g., the RAN or SMF) may send an indication to a WTRU, indicating that the feature is enabled.
  • the RAN may (e.g., later) decide to disable the active dropping feature, for example, if the RAN detects congestion(s).
  • the RAN may inform the SMF, and/or the 5GS may notify the WTRU to make proper assessments (e.g., differentiate between packets lost due to congestion(s) (e.g., network congestion) from packets lost due to active discarding).
  • FIG. 3 illustrates an example of activation/deactivation of PDU active dropping feature by the RAN.
  • the SMF may configure a RAN node (e.g., the RAN node serving the WTRU) with a support of PDU active dropping feature(s).
  • the SMF may send a QoS profile to the RAN that includes an active discarding indication.
  • the SMF may include a reference ID, for example, to allow the RAN to determine one or more flows to apply (e.g., eventually apply) the active discarding to.
  • the RAN may determine whether to enable or disable the active dropping feature and/or use the SMF to send this indication (e.g., the indication of whether to enable or disable the active dropping feature) to the WTRU.
  • the RAN node may send a message to the SMF, for example, via N2 interface.
  • This message may indicate that the active dropping feature(s) is enabled or activated.
  • the message may indicate the PDU session ID for which the feature is enabled, and/or a WTRU identifier.
  • the message may include (e.g., additionally include) a reference ID to indicate the traffic for which the feature is to be enabled.
  • the RAN node may indicate a reason (e.g., may include a reason value to reflect the cause of activation of the feature). For example, the message may indicate “saving radio resource while no congestion” as a reason value for activating the feature.
  • the SMF may send a non-access stratum (NAS) message to the WTRU to indicate that the active dropping feature is now enabled.
  • the message may include the PDU session ID for which the feature is enabled.
  • the SMF may provide the content ratio that is to be used by the RAN for this PDU session ID.
  • the SMF may include the reference ID to the WTRU.
  • the RAN may send a message (e.g., an RRC message) to the WTRU (e.g., directly, as shown in 2a of FIG. 3, to indicate that the active dropping feature is enabled).
  • the RAN may include the content ratio that it is to use for this feature with the WTRU traffic.
  • the RAN may include the reference ID (e.g., indicate the reference ID) to the WTRU, for example, to help determine the traffic to which the feature is applied.
  • the WTRU may inform the WTRU application that the active dropping feature is enabled, for example, along with other related information such as the content ratio of use.
  • the RAN node may (e.g., later) determine to disable the active dropping feature. For example, in Option 1 , 1 d and Option 2, 2c of FIG. 3, the RAN may detect congestion(s) at the network and/or decide to disable the active dropping feature.
  • the RAN may send a message to the SMF (e.g., via the N2 interface to indicate that the active dropping feature is now disabled).
  • the RAN may include one or more of: a reference ID for the traffic of interest, the PDU session ID, or WTRU identifier(s).
  • the RAN may include (e.g., additionally include) a reason value for the deactivation of the feature, e.g., “Congestion detected”.
  • the SMF may send a message (e.g., a NAS message) to the WTRU to inform the WTRU that the active dropping feature is disabled/deactivated.
  • the SMF may include, for example, the PDU session ID as well as the reference ID.
  • the RAN may send a message (e.g., an RRC message directly) to the WTRU to indicate that the active dropping feature is disabled.
  • the RAN may include a reference ID in this message.
  • the WTRU may notify the WTRU application that the active dropping feature is now disabled, or enabled, for example, for the traffic of interest.
  • the notification may indicate what/which traffic the feature is enabled or disabled for.
  • the notification may indicate that the feature is enabled or disabled for the whole PDU session.
  • the notification may indicate that the feature is enabled or disabled for the certain flow(s) (e.g. destination port numbers) of a PDU session.
  • the notification may be sent to the WTRU application, for example, via an Attention (AT) Command.
  • ADHD Attention
  • the WTRU application may use the notification to detect the reason for missing packets. For example, when the notification indicates that the feature (e.g., the active dropping feature) is enabled, the WTRU application may detect that one or more packets were not received. In examples, if the WTRU application is able to successfully recover the application payloads, the WTRU application may conclude that the missing packets were dropped related to resource preservation (e.g., intentionally dropped by the network in order to conserve network resources). Therefore, the WTRU application may determine that application layer settings (e.g. data rates and codec settings) do not need to change.
  • application layer settings e.g. data rates and codec settings
  • the WTRU application may detect that one or more packets were not received. The WTRU application may conclude that the missing packets were dropped at some point in the network or before the packets reached the network (e.g. due to congestion). Therefore, the WTRU application may determine that application layer settings (e.g. data rates and codec settings) are to be changed (e.g., need to change in order to account for the unreliable nature of the network connectivity).
  • application layer settings e.g. data rates and codec settings
  • An RAN may notify the WTRU of PDU active dropping for a (e.g., each) PDU set.
  • the RAN node may not need to wait for a period throughout multiple PDU sets to determine to send a report or notification to the WTRU regarding dropped PDUs.
  • the RAN may send a message (e.g., an RRC message) to the WTRU to inform the WTRU about this.
  • the message from the RAN may indicate to the WTRU that a number of PDUs were actively dropped and/or provide the length of the dropped PDUs of the PDU set or the sequence number of the first discarded PDU of the PDU set (for example, if the WTRU received the first PDU(s) of the PDU set successfully and in order, then the sequence number of the first PDU(s) of the PDU set that was discarded may be useful).
  • This indication may allow the WTRU and/or WTRU application to have a dynamic notification (e.g., a real time notification) regarding the active dropping of PDUs.
  • FIG. 4 illustrates an example of PDU active dropping feature by the RAN.
  • RAN may receive a quality of service (QoS) profile.
  • the QoS profile may include one or more of an indication to perform active discarding and/or a reference identifier (ID) associated with a QoS flow.
  • ID a reference identifier associated with a QoS flow.
  • AS may send downlink traffic to UPF.
  • the RAN may be indicated that active discarding is enabled.
  • the RAN may receive PDUs for which active discarding may be performed.
  • the RAN may receive a PDU message that includes a DL packet (e.g., a PDU).
  • the PDU message may include a header (e.g., a GTP-U header).
  • the header may include the reference ID and/or a QoS flow ID (QFI).
  • QFI QoS flow ID
  • the RAN may perform active discarding (e.g., active PDU dropping) using the QoS profile, a QFI and/or the reference ID.
  • active discarding may be performed on a QoS flow (e.g., an entire QoS flow), and/or the RAN may use the QFI (e.g., only the QFI) to determine one or more PDUs to be actively discarded.
  • the RAN may determine to send a report that indicates the active discarding, for example, to a WTRU.
  • the RAN may send the report, for example, via an RRC message, to a WTRU.
  • the report may include the reference ID and/or an indication that the PDU has been actively discarded.
  • the RAN may send an active discarding report to the WTRU so that the WTRU is notified of the cause of the discard.
  • the processes described above may be implemented in a computer program, software, and/or firmware incorporated in a computer-readable medium for execution by a computer and/or processor.
  • Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and/or wireless connections) and/or computer-readable storage media.
  • Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as compact disc (CD)-ROM disks, and/or digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and/or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un dispositif peut recevoir un profil de qualité de service (QoS). Le profil de QoS peut comprendre un ou plusieurs éléments parmi une indication d'exécution d'un rejet actif, un identifiant de référence (ID) associé à un flux de QoS ou une indication de rapport du rejet actif. Le dispositif peut recevoir un message d'unité de données par paquets (PDU) qui comprend une PDU. Le message de PDU peut comprendre un en-tête. L'en-tête peut comprendre l'ID de référence et/ou un ID de flux QoS (QFI). Le dispositif peut déterminer, sur la base du profil de QoS, que la PDU doit être rejetée. Le dispositif peut rejeter la PDU et/ou envoyer un rapport à une unité d'émission/réception sans fil (WTRU). Le rapport peut comprendre l'ID de référence et/ou une indication selon laquelle la PDU a été activement rejetée. Dans des exemples, le profil de QoS peut en outre comprendre une indication d'une valeur de rapport de contenu qui peut être utilisée pour déterminer la PDU.
PCT/US2025/015598 2024-02-15 2025-02-12 Configuration et rapport de rejet d'unité de données par paquets actifs pour des applications de réalité étendue Pending WO2025174890A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463553915P 2024-02-15 2024-02-15
US63/553,915 2024-02-15

Publications (1)

Publication Number Publication Date
WO2025174890A1 true WO2025174890A1 (fr) 2025-08-21

Family

ID=94974202

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/015598 Pending WO2025174890A1 (fr) 2024-02-15 2025-02-12 Configuration et rapport de rejet d'unité de données par paquets actifs pour des applications de réalité étendue

Country Status (1)

Country Link
WO (1) WO2025174890A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023207846A1 (fr) * 2022-04-29 2023-11-02 华为技术有限公司 Procédé et appareil de communication
US20240049047A1 (en) * 2022-08-04 2024-02-08 Samsung Electronics Co., Ltd. Device and method for managing congestion and burst state in wireless communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023207846A1 (fr) * 2022-04-29 2023-11-02 华为技术有限公司 Procédé et appareil de communication
US20250056319A1 (en) * 2022-04-29 2025-02-13 Huawei Technologies Co., Ltd. Communication method and apparatus
US20240049047A1 (en) * 2022-08-04 2024-02-08 Samsung Electronics Co., Ltd. Device and method for managing congestion and burst state in wireless communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
BENOIST SEBIRE ET AL: "Stage 2 Overview of XR Enhancements", vol. RAN WG2, no. Xiamen, CN; 20231009 - 20231013, 29 September 2023 (2023-09-29), XP052528876, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_123bis/Docs/R2-2309876.zip R2-2309876 XR Draft Stage 2.docx> [retrieved on 20230929] *

Similar Documents

Publication Publication Date Title
US11711729B2 (en) User plane relocation
US11812299B2 (en) Enabling a non-public network communication
US20240340766A1 (en) Wtru-to-network relay associated with mint
US20230199894A1 (en) Method of multimedia broadcast/multicast service (mbms) delivery mode switch
US20250168638A1 (en) Personal internet of things network connectivity
WO2024039843A1 (fr) Politique de sélection de réseau local sans fil (wlan)
WO2025174890A1 (fr) Configuration et rapport de rejet d&#39;unité de données par paquets actifs pour des applications de réalité étendue
WO2025240874A1 (fr) Détection et rapport d&#39;événements de rejet actif
WO2025035098A1 (fr) Ensembles de pdu dl avec atsss
WO2025029919A1 (fr) Améliorations de système 5gs sensibles à la latence de bout en bout pour xrm
WO2024233633A1 (fr) Dispositifs de réseau cœur associés à une libération ou à un rétablissement de session pdu
EP4595666A1 (fr) Transmissions de signal de commande court
WO2025034325A1 (fr) Sélection de ressources pour de multiples porteuses avec porteuses sous licence et sans licence
WO2024211891A1 (fr) Systèmes et procédés de détection d&#39;état de relais u2u sans découverte autonome
WO2025212903A1 (fr) Procédés, architectures, appareils et systèmes de sélection de dispositif membre à l&#39;aide de critères de filtrage de consommation d&#39;énergie
WO2024211895A1 (fr) Systèmes et procédés d&#39;établissement de sécurité entre une unité d&#39;émission-réception sans fil cible (wtru) et une wtru relais u2u
WO2024211885A1 (fr) Systèmes et procédés de détection d&#39;état de relais u2u pendant une découverte
WO2024173312A1 (fr) Schéma de retransmission basé sur une condition de déclenchement
WO2024233889A1 (fr) Radiorecherche pour dispositifs de l&#39;internet des objets ambiant
WO2025240862A1 (fr) Rejet actif basé sur une corrélation d&#39;ensembles de pdu
WO2024211827A1 (fr) Systèmes et procédés associés à un mode de direction redondant et à une signalisation pmf
WO2025213085A1 (fr) Rapport d&#39;utilisation de données amélioré pour applications xrm
WO2025034324A1 (fr) Rlf sl spécifique à une porteuse basée sur un comptage harq
WO2024211821A1 (fr) Systèmes et procédés associés à un mode de direction redondant et à une mobilité sur une branche d&#39;accès
WO2025075939A1 (fr) Découverte de relais et améliorations de sécurité de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25711853

Country of ref document: EP

Kind code of ref document: A1