Oscillation Monitoring in a Wireless Communication Network

Description

1 / 60 “OSCILLATION MONITORING IN A WIRELESS COMMUNICATION NETWORK” CROSS-REFERENCE TO RELATED REQUESTS

[001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 457,684, filed April 6, 2023, the disclosure of which is incorporated herein by reference in its entirety. BACKGROUND

[002] Mobile communications using wireless communication continue to evolve. A fifth generation may be called 5G. A previous (legacy) generation of mobile communication may be, for example, the fourth generation (4G) of long-term evolution (LTE). Wireless communication traffic can be transmitted in one or more protocol data units (PDUs). Due to the nature of the network that carries the PDUs (e.g., from an application server (AS) to a network device), the PDUs may exhibit different delays, and the difference in delays experienced by the PDUs can be measured by ripple. SUMMARY

[003] The systems, methods, and instruments related to oscillation monitoring in a wireless communication network are described in this document. A network device associated with the wireless communication network can receive information about one or more aspects of oscillation monitoring within the wireless communication network. The network device can determine an oscillation monitoring policy based on the information received and send it to another device on the wireless communication network. After sending the oscillation monitoring policy to the other device on the wireless communication network, the network device can receive an indication of an oscillation measurement result from the other device. Petition 870250090750, dated 06 / 10 / 2025, page 11 / 94 2 / 60

[004] In examples, the network device may receive information regarding one or more aspects of oscillation monitoring within the wireless communication network from a network exposure function (NEF) associated with an application server (AS) or an application function (AF). In examples, the network device may transmit the oscillation measurement result indication to the NEF.

[005] In examples, information regarding one or more aspects of ripple monitoring within the wireless communication network may indicate that ripple monitoring should be performed at a protocol data unit (PDU) set level or at a burst level. In examples, the ripple monitoring policy may be associated with a PDU session that includes extended reality traffic.

[006] In examples, information regarding one or more aspects of oscillation monitoring in the wireless communication network may indicate an oscillation measurement period and / or an oscillation sampling period. In examples, information regarding one or more aspects of oscillation monitoring in the wireless communication network may indicate an oscillation monitoring trigger condition. In examples, the network device may be configured to determine and send the oscillation monitoring policy as a quality of service monitoring rule.

[007] In examples, information regarding one or more aspects of fluctuation monitoring within the wireless communication network may be received through a policy authorization request, and wherein the network device may be further configured to transmit a policy authorization response that confirms the use of the information received through the policy authorization request. In examples, the network device may be a policy control function of the wireless communication network, and the other Petition 870250090750, dated 06 / 10 / 2025, page 12 / 94 The 3 / 60 device may be a wireless communication network session handling function. BRIEF DESCRIPTION OF THE DRAWINGS

[008] Figure 1A is a system diagram that illustrates an exemplary communications system in which one or more disclosed modalities can be implemented;

[009] Figure 1B is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that can be used within the communications system illustrated in Figure 1A according to one mode;

[010] Figure 1C is a system diagram illustrating an exemplary radio access network (RAN) and an exemplary central network (CN) that can be used within the communications system illustrated in Figure 1A according to a modality;

[011] Figure 1D is a system diagram that illustrates an additional exemplary RAN and an additional exemplary CN that can be used within the communications system illustrated in Figure 1A according to a modality;

[012] Figure 2 is a diagram that illustrates an example of a connected-mode discontinuous reception (CDRX) configuration based on oscillation information.

[013] Figure 3 is a diagram that illustrates an example having more than one service data flow (SDF) for a QoS flow.

[014] Figure 4 is a diagram that illustrates exemplary approaches to performing oscillation measurements at a PDU array level.

[015] Figure 5 is a diagram that illustrates an example of a procedure for setting up an oscillation monitoring (or oscillation measurement) requirement for an XRM service. Petition 870250090750, dated 06 / 10 / 2025, page 13 / 94 4 / 60

[016] Figure 6 is a diagram that illustrates an exemplary procedure for provisioning oscillation monitoring, oscillation measurement and / or oscillation reporting for a WTRU with connected devices.

[017] Figure 7 is a diagram that illustrates an example of a set-level playback delay buffer for PDUs.

[018] Figure 8 is a diagram that illustrates an exemplary procedure for monitoring and reducing oscillation based on PDU set playback buffers and / or PDU set importance values.

[019] Figure 9 is a diagram that illustrates an exemplary procedure for a radio access network (RAN) to configure CDRX for multiple SDFs in a QoS stream.

[020] Figure 10 is a diagram that illustrates an example of determining a downlink periodicity (DL) and / or a relative time difference associated with several SDFs.

[021] Figure 11 is a diagram that illustrates an example of determining an XRD cycle based on several SDFs with the same periodicity.

[022] Figure 12 is a diagram that illustrates an example of determining an XRD cycle based on several SDFs with different periodicities. DETAILED DESCRIPTION

[023] Figure 1A is a diagram illustrating an exemplary 100 communications system, in which one or more disclosed modalities may be implemented. The 100 communications system may be a multiple access system that provides content, such as voice, data, video, messages, streaming, etc., to multiple wireless users. The 100 communications system may allow multiple wireless users to access this content by sharing system resources, including wireless bandwidth. For example, 100 communications systems may employ one or more channel access methods, such as Petition 870250090750, dated 06 / 10 / 2025, page 14 / 94 5 / 60 Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tailed Single-Word DFT Propagation OFDM (ZT UW DTS-s OFDM), Single-Word OFDM (UWOFDM), Feature Block Filtered OFDM, Filter Bank Multicarrier (FBMC) and similar.

[024] As shown in Figure 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, although it is recognized that the disclosed embodiments may encompass 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, WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a mobile phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook,A personal computer, a wireless sensor, a Mi-Fi access point or device, an Internet of Things (IoT) device, a watch or other wearable device, 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 industrial and / or automated process chain contexts), a consumer electronic device, a device operating on commercial and / or industrial wireless networks, and the like. Any of WTRUs 102a, 102b, 102c, and 102d may be referred to alternatively as a UE. Petition 870250090750, dated 06 / 10 / 2025, page 15 / 94 6 / 60

[025] Communication 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 interact with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110 and / or other networks 112. By way of example, base stations 114a and 114b may be a base transceiver station (BTS), a B Node, an Evolved B Node, a Domestic B Node, a Domestic Evolved B Node, a gNB, an NR B Node, a site controller, an access point (AP), a wireless router and the like. Although base stations 114a and 114b are represented as a single element, it will be recognized that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[026] Base station 114a may be part of 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. Base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be called 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 for a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors.Thus, in one embodiment, base station 114a may include three transceivers, that is, one for each sector of the cell. In another embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. Petition 870250090750, dated 06 / 10 / 2025, p. 16 / 94 7 / 60 cell. For example, beamforming can be used to transmit and / or receive signals in desired spatial directions.

[027] Base stations 114a, 114b can communicate with one or more of WTRUs 102a, 102b, 102c, 102d via an air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter waves, micrometer waves, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 can be established using any suitable radio access technology (RAT).

[028] More specifically, as noted above, 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, base station 114a in RAN 104 / 113 and WTRUs 102a, 102b and 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 HSPA Enhanced (HSPA+). HSPA may include High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Ultra Packet Access (HSUPA).

[029] In one embodiment, base station 114a and 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 Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).

[030] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement a radio technology, such as NR Radio Access, which can establish the 116 air interface using New Radio (NR). Petition 870250090750, dated 06 / 10 / 2025, p. 17 / 94 8 / 60

[031] In one embodiment, base station 114a and WTRUs 102a, 102b, and 102c may implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c may implement LTE radio access and NR radio access together, for example, using dual connectivity (DC) principles. Thus, the air interface used by WTRUs 102a, 102b, and 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).

[032] In other embodiments, base station 114a and 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), GSM Evolution Enhanced Data Rates (EDGE), GSM EDGE (GERAN) and similar.

[033] Base station 114b in Figure 1A can be a wireless router, a Home B Node, an Evolved Home B Node, or an access point, for example, and can utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as a workplace, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a highway, and the like. In one embodiment, base station 114b and WTRUs 102c, 102d can implement a radio technology, such as IEEE 802.11, to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c and 102d can implement a radio technology, such as IEEE 802.15, to establish a wireless personal area network (WPAN). In another configuration, base station 114b and WTRUs 102c and 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A). Petition 870250090750, dated 06 / 10 / 2025, page 18 / 94 9 / 60 Pro, NR, etc.) to establish a picocell or femtocell. As shown in Figure 1A, the 114b base station can have a direct connection to the 110 Internet. Thus, the 114b base station may not need to access the 110 Internet via the 106 / 115 CNs.

[034] RAN 104 / 113 may be in communication with CN 106 / 115, which may be any type of network configured to provide voice, data, application and / or voice over internet protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements and the like. CN 106 / 115 may provide call control, billing services, location-based mobile services, prepaid calls, internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication.Although not shown in Figure 1A, it is possible to observe that RAN 104 / 113 and / or CN 106 / 115 may be in direct or indirect communication with other RANs that use the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to being connected to RAN 104 / 113, which may use NR radio technology, CN 106 / 115 may also be in communication with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[035] CN 106 / 115 can also serve as a gateway for WTRUs 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110 and / or other networks 112. PSTN 108 may include circuit-switched telephone networks that provide simple telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as Transmission Control Protocol (TCP), the Petition 870250090750, dated 06 / 10 / 2025, p. 19 / 94 10 / 60 User Datagram Protocol (UDP) and / or Internet Protocol (IP) in the TCP / IP internet protocol suite. Networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, networks 112 may include another NC connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

[036] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multimode capabilities (for example, WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communication with different wireless networks via different wireless links). For example, WTRU 102c shown in Figure 1A may be configured to communicate with base station 114a, which may employ cellular-based radio technology, and with base station 114b, which may employ IEEE 802 radio technology.

[037] Figure 1B is a system diagram illustrating an exemplary WTRU 102. As shown in Figure 1B, 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 supply 134, a global positioning system (GPS) chipset 136 and / or other peripherals 138, among others. It should be noted that the WTRU 102 may include any subcombination of the above elements, while remaining consistent with an embodiment.

[038] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application-Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. Processor 118 may execute Petition 870250090750, dated 06 / 10 / 2025, page 20 / 94 11 / 60 signal encoding, data processing, power control, input / output processing, and / or any other functionality that allows the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, which can be coupled to the transmit / receive element 122. Although Figure 1B represents the processor 118 and the transceiver 120 as separate components, it will be recognized that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.

[039] The transmit / receive element 122 can be configured to transmit or receive signals from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, the transmit / receive element 122 can be a transmitter / detector configured to transmit and / or receive infrared, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 can be configured to transmit and / or receive RF and light signals. It should be noted that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.

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

[041] Transceiver 120 can be configured to modulate the signals to be transmitted by the transmit / receive element 122 and to demodulate the signals received by the transmit / receive element 122. As noted above, the WTRU 102 can have multimode capabilities. Thus, transceiver 120 can include Petition 870250090750, dated 06 / 10 / 2025, p. 21 / 94 12 / 60 multiple transceivers to allow the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[042] The WTRU 102 processor 118 can be coupled with and 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) unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also send user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 can access information and store data in any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 can include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a SIM card (subscriber identity module), a memory card, a secure digital memory card (SD), and similar items.In other configurations, processor 118 can access information and store data in memory that is not physically located in WTRU 102, such as in a server or a home computer (not shown).

[043] Processor 118 can receive power from power supply 134 and can be configured to distribute and / or control power to the other components in WTRU 102. Power supply 134 can be any device suitable for powering WTRU 102. For example, power supply 134 can 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.

[044] Processor 118 can also be coupled to the GPS chipset 136, which can be configured to provide location information (e.g., longitude and latitude) relating to the current location of WTRU 102. In addition to Petition 870250090750, dated 06 / 10 / 2025, page 22 / 94 13 / 60 GPS chipset information 136, or in place thereof, the WTRU 102 may receive location information via air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the reception time of signals from two or more nearby base stations. It is important to note that the WTRU 102 may acquire location information by any suitable location determination method, remaining consistent with a modality.

[045] The processor 118 may also be coupled with other peripherals 138, which may include one or more software and / or hardware modules that provide additional wired or wireless features, functionality and / or connectivity. For example, peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photographs and / or video), a USB port (Universal Serial Bus), 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.Peripherals 138 may include one or more sensors, the sensors may be one or more of the following: 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.

[046] A WTRU 102 may include a full duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for the UL (e.g., for transmission) and the downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio Petition 870250090750, dated 06 / 10 / 2025, page 23 / 94 14 / 60 duplex may include an interference handling unit to substantially reduce and / or eliminate self-interference by means of hardware (e.g., an inductor) or signal processing by means of a processor (e.g., a separate processor (not shown) or by means of processor 118). In one embodiment, the WRTU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for the UL (e.g., for transmission) or the downlink (e.g., for reception)) are combined.

[047] Figure 1C is a system diagram illustrating RAN 104 and CN 106 according to one mode. As noted above, RAN 104 can employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 can also be in communication with CN 106.

[048] RAN 104 may include Evolved B Nodes 160a, 160b, 160c, although it is important to note that RAN 104 may include any number of Evolved B Nodes, remaining consistent with a mode. Evolved B Nodes 160a, 160b, 160c may each include one or more transceivers for communication with WTRUs 102a, 102b, 102c via air interface 116. In a mode, Evolved B Nodes 160a, 160b, 160c may implement MIMO technology. Thus, Evolved B Node 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from WTRU 102a.

[049] Each of the Evolved B Nodes 160a, 160b, 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource manipulation decisions, transfer decisions, user scheduling in the UL and / or DL, and the like. As shown in Figure 1C, the Evolved B Nodes 160a, 160b, 160c can communicate with each other via an X2 interface. Petition 870250090750, dated 06 / 10 / 2025, page 24 / 94 15 / 60

[050] The CN 106 shown in Figure 1C may include a mobility handling entity (MME) 162, a service gateway (SGW) 164, and a packet data network gateway (PDN) (or PGW) 166. Although each of the foregoing elements is represented as part of 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.

[051] MME 162 can be connected to each of the Evolved B Nodes 162a, 162b, 162c in RAN 104 via an S1 interface and can serve as a control node. For example, MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, 102c, carrier activation / deactivation, selection of a specific service gateway during an initial connection of WTRUs 102a, 102b, 102c, and similar. MME 162 can provide a control plane function to switch between RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[052] SGW 164 can be connected to each of the Evolved B Nodes 160a, 160b, and 160c in RAN 104 via the S1 interface. SGW 164 can generally route and forward user data packets to / from WTRUs 102a, 102b, and 102c. SGW 164 can perform other functions such as anchoring user planes during transfers between Evolved B Nodes, initiating paging when DL data is available for WTRUs 102a, 102b, and 102c, handling and storing contexts of WTRUs 102a, 102b, and 102c, and similar functions.

[053] SGW 164 can be connected to PGW 166, which can provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices.

[054] CN 106 can facilitate communications with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to switched networks via Petition 870250090750, dated 06 / 10 / 2025, p. 25 / 94 A 16 / 60 circuit, such as PSTN 108, facilitates communication between WTRUs 102a, 102b, and 102c and traditional fixed-line communication devices. For example, CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 106 and PSTN 108. Additionally, CN 106 may provide WTRUs 102a, 102b, and 102c with access to other 112 networks, which may include other wired and / or wireless networks owned and / or operated by other service providers.

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

[056] In representative modalities, the other 112 network may be a WLAN.

[057] A WLAN in Basic Services Infrastructure Set (BSS) mode can have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or other type of wired / wireless network that carries inbound and / or outbound traffic from the BSS. Traffic to the STAs originating from outside the BSS can arrive through the AP and be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS can be sent to the AP to be delivered to the respective destinations. Traffic between STAs within the BSS can be sent through the AP, for example, where the originating STA can send traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within a BSS can be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between (e.g., directly between) the source and destination STAs with a Direct Link System (DLS) configuration.In certain representative configurations, DLS may use either 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all). Petition 870250090750, dated 06 / 10 / 2025, p. 26 / 94 17 / 60 as STAs) within or using IBSS can communicate directly with each other. The IBSS communication mode may sometimes be referred to in this document as an “ad-hoc” communication mode.

[058] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit a beacon on a fixed channel, such as a primary channel. The primary channel can have a fixed width (e.g., 20 MHz bandwidth) or a width dynamically defined through signaling. The primary channel can be the BSS's operating channel and can be used by STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) can be implemented, for example, in 802.11 systems. For CSMA / CA, STAs (e.g., each STA), including the AP, can sense the primary channel. If the primary channel is sensed / detected and / or determined to be occupied by a specific STA, that STA can back off. An STA (e.g., only one station) can transmit at any time on a given BSS.

[059] High-throughput (HT) STAs can use a 40 MHz wide channel for communication, for example, by combining the 20 MHz primary channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.

[060] Very High Throughput (VHT) STAs can support channels of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz width. 40 MHz and / or 80 MHz channels can be formed by combining contiguous 20 MHz channels. A 160 MHz channel can be formed by combining 8 contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which can be called an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, can be passed through a segment analyzer that can split the data into two streams. Fast Fourier Transform processing Petition 870250090750, dated 06 / 10 / 2025, page 27 / 94 18 / 60 Inverse (IFFT) and time-domain processing can be performed on each stream separately. The streams can be mapped to the two 80 MHz channels, and the data can be transmitted by a transmitting STA. At the receiver of the receiving STA, the operation described above for the 80+80 configuration can be reversed, and the combined data can be sent to the Medium Access Control (MAC).

[061] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV White Space (TVWS) spectrum, and 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support Meter Type Control / Machine Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain features, for example, limited features, including support for (e.g., support only for) certain bandwidths and / or limited bandwidths. MTC devices may include a battery with a lifespan exceeding a certain limit (e.g., to maintain a very long lifespan).

[062] WLAN systems, which can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the highest common operational bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be defined and / or limited by an STA, among all STAs operating in a BSS, that supports the lowest bandwidth operating mode. In the 802.11ah example, the primary channel can have a bandwidth of 1 MHz for STAs (e.g., MTC-type devices) that Petition 870250090750, dated 06 / 10 / 2025, page 28 / 94 19 / 60 supports (for example, only supports) the 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 Sense and / or Network Allocation Vector (NAV) settings may depend on the primary channel status. If the primary channel is busy, for example, due to an STA (that only supports the 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered occupied, even if most frequency bands remain idle and could be available.

[063] In the United States, the available frequency bands that can be used by 802.11ah 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.11ah is from 6 MHz to 26 MHz, depending on the country code.

[064] Figure 1D is a system diagram illustrating RAN 113 and CN 115 according to a modality. As noted above, RAN 113 can employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 113 can also be in communication with CN 115.

[065] RAN 113 may include gNBs 180a, 180b, 180c, although it is possible to observe that RAN 113 may include any number of gNBs, remaining consistent with a modality. gNBs 180a, 180b, 180c may each include one or more transceivers for communication with WTRUs 102a, 102b, 102c via air interface 116. In a modality, gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a and 108b may use beamforming to transmit and / or receive signals from gNBs 180a, 180b, and 180c. Thus, the gNB 180a, for example, can use multiple antennas to transmit and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b and Petition 870250090750, dated 06 / 10 / 2025, p. 29 / 94 20 / 60 180c satellites can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be in unlicensed spectrum, while the remaining component carriers may be in licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement CoMP (Coordinated Multipoint) technology. For example, WTRU 102a can receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[066] WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable durations (e.g., containing a variable number of OFDM symbols and / or lasting varying absolute durations).

[067] gNBs 180a, 180b, 180c can be configured to communicate with WTRUs 102a, 102b, 102c in a standalone configuration and / or in a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., as Evolved B Nodes 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, and 102c can use one or more of gNBs 180a, 180b, and 180c as a mobility anchor point. In a standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in an unlicensed band. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect to gNBs 180a and 180b. Petition 870250090750, dated 06 / 10 / 2025, page 30 / 94 21 / 60 and 180c, while also communicating / connecting to another RAN, such as the Evolved B Nodes 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate with one or more gNBs 180a, 180b, and 180c and one or more Evolved B Nodes 160a, 160b, and 160c substantially simultaneously. In the non-autonomous configuration, the Evolved B Nodes 160a, 160b, and 160c can serve as a mobility anchor for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput to serve WTRUs 102a, 102b, and 102c.

[068] Each of the gNBs 180a, 180b, 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource manipulation decisions, transfer decisions, user scheduling in the UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, user plane data routing to the User Plane Function (UPF) 184a, 184b, control plane information routing to the Access and Mobility Management Function (AMF) 182a, 182b, and similar. As shown in Figure 1 D, the gNBs 180a, 180b, 180c can communicate with each other via an Xn interface.

[069] The CN 115 shown in Figure 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b and possibly a Data Network (DN) 185a, 185b. Although each of the above elements is represented as part of the CN 115, it should be noted that any of these elements may be owned and / or operated by an entity other than the CN operator.

[070] AMF 182a, 182b can be connected to one or more of the gNBs 180a, 180b, 180c in RAN 113 via an N2 interface and can serve as a control node. For example, AMF 182a, 182b can be responsible for authenticating users of WTRUs 102a, 102b, 102c, support for network slicing (e.g., Petition 870250090750, dated 06 / 10 / 2025, page 31 / 94 22 / 60 handling of different PDU sessions with different requirements), selection of a specific SMF 183a, 183b, register area handling, NAS signaling termination, mobility handling, and similar. Network slicing can be used by AMF 182a and 182b to customize CN support for WTRUs 102a, 102b, and 102c based on the types of services used. For example, different network slices can be established for different use cases, such as services that rely on ultra-reliable low-latency access (URLLC), services that rely on enhanced massive mobile broadband (eMBB) access, services for machine-type communication (MTC) access, and / or similar. The AMF 162 can provide a control plane function to switch between 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.

[071] SMF 183a, 183b can be connected to AMF 182a, 182b on CN 115 via an N11 interface. SMF 183a, 183b can also be connected to UPF 184a, 184b on CN 115 via an N4 interface. SMF 183a, 183b can select and control UPF 184a, 184b and configure traffic routing through UPF 184a, 184b. SMF 183a, 183b can perform other functions such as manipulating and allocating UE IP addresses, handling PDU sessions, controlling policy and QoS enforcement, providing downlink data notifications, and similar functions. A PDU session type can be IP-based, non-IP-based, Ethernet-based, and similar.

[072] UPF 184a, 184b can be connected to one or more of the gNBs 180a, 180b and 180c in RAN 113 via an N3 interface, which can provide WTRUs 102a, 102b and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between WTRUs 102a, 102b and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as packet routing and forwarding, user plane policy enforcement, support for Petition 870250090750, dated 06 / 10 / 2025, page 32 / 94 23 / 60 PDU sessions with multi-homing, user-plane QoS handling, downlink packet buffering, mobility tethering provision, and similar features.

[073] CN 115 can facilitate communications with other networks. For example, CN 115 can include or communicate with an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between CN 115 and PSTN 108. In addition, CN 115 can provide WTRUs 102a, 102b, 102c with access to other 112 networks, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, 102c can be connected to a local Data Network (DN) 185a, 185b via UPF 184a, 184b through interface N3 to UPF 184a, 184b and an interface N6 between UPF 184a, 184b and DN 185a, 185b.

[074] In view of Figures 1A-1D and the corresponding description of Figures 1A-1D, one or more, or all, of the functions described in this document in relation to one or more of the following: WTRU 102a-d, Base Station 114a-b, Evolved Node 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 in this document, 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 in this document. For example, emulation devices can be used to test other devices and / or simulate network and / or WTRU functions.

[075] Emulation devices can be designed to implement one or more tests of other devices in a laboratory environment and / or in a carrier network environment. For example, one or more emulation devices can perform one or more, or all, of the functions while being fully or partially implemented and / or deployed as part of a network of Petition 870250090750, dated 06 / 10 / 2025, page 33 / 94 24 / 60 wired and / or wireless communication in order to test other devices within the communication network. One or more emulation devices can perform one or more, or all, of the functions while temporarily deployed as part of a wired and / or wireless communication network. The emulation device can be directly coupled to another device for testing purposes and / or can perform tests using wireless communications.

[076] One or more emulation devices may perform one or more functions, including all, without being implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used in a test scenario in a test laboratory and / or in an undeployed wired and / or wireless communication network (e.g., for testing) in order to implement tests of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuits (e.g., which may include one or more antennas) may be used by emulation devices to transmit and / or receive data.

[077] The systems, methods, and instruments described herein relate to oscillation monitoring. The systems, methods, and instruments may be associated with extended reality and / or multimodal services (XRM). The term “oscillation monitoring” may be used herein interchangeably with the term “oscillation measurement”.

[078] A network device or node, such as a policy control function (PCF), may be configured with (e.g., additional information) relating to swing monitoring or swing measurement (e.g., by a WTRU and / or a user plane function (UPF)), for example, at a protocol data unit (PDU) set level or at a burst level. Where mentioned herein, a burst may refer to a set of PDUs. Petition 870250090750, dated 06 / 10 / 2025, page 34 / 94 25 / 60 or to one or more sets of PDUs generated and sent (e.g., by an application) within a time period. The (e.g., additional) information configured for the network device may include or indicate one or more of the following: information about whether ripple monitoring should be performed at a PDU level, a set of PDUs level, or a burst level; information about whether ripple monitoring is related to a (e.g., each) media modality (e.g., video, audio, touch, etc.); and / or an indication of which method should be used to calculate a ripple or what type of ripple should be measured, among other parameters. The PCF may generate a ripple monitoring policy (e.g., one or more policy billing and control (PCC) rules that include ripple monitoring information) based on the information received.A PCF can provide (e.g., forward) the swing monitoring policy (e.g., one or more PCC rules) to one or more other network devices, such as a Session Manipulation Function (SMF), a UPF, and / or a WTRU. The PCF can receive swing measurement results subsequent to providing the swing monitoring policy. The PCF can notify an application server (AS) or application function (AF) about swing-related events (e.g., swing monitoring results), for example, through a network exposure function (NEF) that exposes the PCF and / or other network devices to the AS / AF.

[079] A WTRU and / or a UPF may use a playback or PDU-level ripple compensation buffer, for example, to minimize ripple. The WTRU and / or UPF may receive configuration information about one or more buffer characteristics (e.g., buffer size). The WTRU and / or UPF may receive ripple monitoring parameters via one or more QoS rules (e.g., for the WTRU) and / or one or more N4 rules (e.g., for the UPF). WTRU and / or UPF may Petition 870250090750, dated 06 / 10 / 2025, p. 35 / 94 26 / 60 perform oscillation measurements. The WTRU and / or UPF can report the measurement results to an SMF and / or a PCF. The PCF can send the oscillation measurement results to an AF / AS (e.g., via a NEF). The AF / AS can provide information to help modify the PDU set-level oscillation compensation buffer in the WTRU and / or UPF.

[080] The systems, methods, and instruments described in this document relate to flicker monitoring for extended reality and / or multimodal (XRM) services. The systems, methods, and instruments described in this document relate to the provisioning of flicker monitoring policies and / or requirements (e.g., at a PDU set level) in a wireless communication network (e.g., as a fifth-generation (5GS) system).

[081] A network device (for example, a device that understands or is configured to perform a policy control function (PCF)) can be configured to perform one or more of the following actions. The network device (for example, the PCF) can receive a message that includes ripple monitoring information. The message can include an indication of whether ripple monitoring is enabled (for example, required) and / or whether ripple monitoring should be performed at a PDU level, a set of PDUs level, or a burst level (for example, for a media mode). The message can include an indication of which method can be used to calculate ripple and / or what type of ripple can be measured.An application function (AF) can predict (e.g., for some modalities, such as a video modality) different codec settings that a modality (e.g., a video modality) can adopt, for example, for an extended reality and / or multimodal (XRM) service. AF can provide (e.g., indicate to a network device) different flicker monitoring parameters. Petition 870250090750, dated 06 / 10 / 2025, p. 36 / 94 27 / 60 different combinations of video resolutions and / or frame rates. AF can provide trigger conditions for flicker monitoring (e.g., for certain modes). AF can provide a delay budget, a set delay budget for PDUs, and / or delay budget monitoring for one (e.g., each) mode. AF can provide a delay difference threshold between different modes of an XRM service. AF can provide flicker monitoring parameters for burst level monitoring.

[082] A network device, such as a PCF, can use the information provided by an AF / AS (e.g., via a NEF) to determine or generate one or more fluctuation monitoring policies for a multimodal service (e.g., extended reality (XR) service). One or more policies can be determined or generated as part of a quality of service (QoS) monitoring rule (e.g., in the form of one or more policy billing and control (PCC) rules). The network device can send the policies and / or rules to one or more other network devices, including, for example, a device that understands or is configured to perform a session handling function (SMF).

[083] The network device (e.g., PCF) can receive (e.g., from an SMF) a notification about a wobble measurement result, for example, if the measured wobble amount has exceeded a certain limit. The network device can send an indication of the wobble measurement result (e.g., a notification related to the wobble measurement result) to the AF, for example, via a NEF.

[084] A device (for example, a WTRU and / or a network device / node configured as a UPF) can perform one or more of the following actions. The device can receive flicker monitoring information included in one or more QoS rules provided by a PCF (for example, via a Petition 870250090750, dated 06 / 10 / 2025, page 37 / 94 28 / 60 (SMF). The device can perform oscillation measurements based on received oscillation monitoring information (e.g., which may include one or more oscillation measurement parameters). The device can send an oscillation measurement result to the SMF, which can then forward the result to the PCF.

[085] A device as described herein may include a processor configured to perform one or more actions configured for the device. For example, a device (e.g., a NEF) as described herein may include a processor configured to receive, from a requesting entity (e.g., an AS / AF), a request for a multimodal session with a WTRU and / or swing monitoring information. The device may send a policy authorization request to another device (e.g., to a PCF) for the multimodal session and / or swing monitoring associated with the multimodal session. The device may receive a policy authorization response (e.g., from the PCF), where the policy authorization response may confirm authorization of the policy authorization request.The device can send a message to the requesting entity (e.g., AS / AF) to confirm the multimodal session. The device can receive at least one oscillation measurement result or a notification related to the oscillation measurement result (e.g., from PCF) and can send the oscillation measurement result or the notification related to the oscillation measurement result to the requesting entity.

[086] The oscillation monitoring information described in this document may indicate whether oscillation monitoring should be performed, a type of oscillation calculation or an oscillation calculation method, an index for a set of oscillation monitoring parameters, etc. The set of oscillation monitoring parameters may comprise a parameter of Petition 870250090750, dated 06 / 10 / 2025, page 38 / 94 29 / 60 respective oscillation monitoring associated with a condition. A message confirming the multimodal session may indicate confirmation of the information and / or parameters provided by the requesting entity when requesting the multimodal session and providing the oscillation monitoring information. The requesting entity may be an application function.

[087] Traffic in a flow can be periodic. For example, a downlink flow from a server (e.g., an application server) to a WTRU can carry PDUs, and the PDUs can be transmitted (e.g., from the server to the WTRU) in a periodic pattern. The periodic pattern can be, for example, one PDU sent every time period.

[088] The delay that each PDU experiences may be different, for example, due to the nature of the network carrying downlink data (e.g., from an AS to a UPF or a WTRU). Wiggle can be a measure of how much the delay experienced by each PDU varies. Wiggle can be a measure of how much the time period used to transmit each PDU varies (e.g., as measured by the UPF).

[089] An application server associated with a wireless network or communication system can provide a network device (e.g., a PCF) with the expected periodicity of a traffic flow. The network device (e.g., the PCF) can provide the expected periodicity of the traffic flow to another network device, such as an SMF. The SMF can provide the information to another network device, such as a UPF.

[090] The UPF can report oscillation measurements to the SMF. The SMF can provide the oscillation measurements to a RAN node, such as a base station. The RAN node can use the information to adjust the connected-mode discontinuous receive (CDRX) settings of a WTRU. Petition 870250090750, dated 06 / 10 / 2025, page 39 / 94 30 / 60

[091] The UPF can report wobble measurements to the application server. Wobble measurement reports can be sent directly to the application server or indirectly, for example, via SMF, PCF and / or a NEF. The application server can use the wobble measurement information to configure one or more wobble buffers in a server application and / or a WTRU application.

[092] PDU Set Integrated Handling Information (PSIHI) can indicate whether one or more (e.g., all) PDUs in a PDU set must be transmitted / received before the PDU set can be used by an application layer (e.g., on the receiver side). PSIHIs can be provided to a network device (e.g., a PCF) by the application server. PSIHIs (e.g., if enabled) can be applied to (e.g., all) traffic from a PDU set in a QoS flow.

[093] A counter-swing buffer can (for example, be configured to) remove the effects of wobble from a received stream, for example, by buffering each incoming packet for a short interval before playing them back synchronously. A fixed counter-swing buffer can maintain a constant size. An adaptive counter-swing buffer can (for example, have the ability to) dynamically adjust the buffer size to optimize a trade-off between delay and discard.

[094] A counter-swing buffer size (JBS) can be defined as the maximum time packets can remain in the buffer. A counter-swing buffer delay (JBD) may be called counter-swing delay, wait time, or playback delay. A JBD may correspond to the time packets remain in the buffer, which may be less than the counter-swing buffer size. The departure time of each packet can be determined by reading the timestamp information provided by a real-time transport protocol (RTP), for example. Petition 870250090750, dated 06 / 10 / 2025, page 40 / 94 31 / 60

[095] Swing can be used for CDRX configuration. A network device (e.g., a UPF) can be configured with a session reporting rule to assist a RAN node (e.g., a base station) in establishing CDRX configuration parameters for a WTRU. The session reporting rule might be, for example, “N6 Swing Measurement Report per QoS Flow”. The rule might include N6 swing measurement control information that might indicate that the network device (e.g., UPF) should report N6 swing information associated with a downlink periodicity (DL) for a QoS flow in a downlink direction (e.g., to assist the RAN node in configuring CDRX for the WTRU). An N6 swing measurement report can be generated by the network device (e.g., the UPF) and sent to another network device (e.g., an SMF).The report may indicate an N6 oscillation measurement result for the QoS stream periodicity.

[096] In establishing a PDU session with a QoS (e.g., by an AS / AF), a network (e.g., a 5G system) may receive periodicity information. Periodicity information may be provided by the AF to a first network device (e.g., a PCF) via a NEF, or directly to the first network device, e.g., if / when the AF is reliable. The first network device (e.g., the PCF) may send the periodicity information received from the AF to a second network device (e.g., an SMF). The first network device may include (e.g., within one or more PCC rules) an indication for the second network device to request that a third network device (e.g., a UPF) perform ripple measurements, e.g., according to the operator's local policies.

[097] The second network device (e.g., the SMF) can (e.g., upon receiving the PCC rule(s)) determine assistance information to Petition 870250090750, dated 06 / 10 / 2025, p. 41 / 94 32 / 60 time-sensitive communication (TSCAI) and can forward TSCAI to a RAN node (e.g., a base station). The second network device (e.g., the SMF) can send a DL periodicity indication (e.g., the time period between two data bursts) to the third network device (e.g., the UPF), for example, if the PCC rule(s) include an indication to perform ripple measurements. The second network device can request that the third network device periodically monitor and / or report ripple information associated with the DL periodicity, for example, using an N4 session modification procedure. The second network device can provide the DL periodicity in the request to the third network device. How the third network device derives the N6 ripple may depend on the implementation.The way the third network device derives the DL periodicity when not provided by an AF can also depend on the implementation.

[098] The second network device (e.g., the SMF) can receive flicker measurement results from the third network device (e.g., the UPF), for example, in an N4 session-level report. The second network device can include the flicker measurement information, for example, along with the associated periodicity, in the TSCAI that the second network device can forward to a RAN node (e.g., via a NG Application Protocol (NGAP) message). The third network device can send the N6 flicker measurement report periodically or if / when (e.g., only if / when) the measured flicker is greater than a threshold. This can prevent frequent updates from the third network device.

[099] Figure 2 illustrates an example of oscillation measurement / reporting and determination of a CDRX configuration based on oscillation information.

[0100] As shown in Figure 2, in 1, a first network device (e.g., a PCF) can send DL periodicity information (by Petition 870250090750, dated 06 / 10 / 2025, page 42 / 94 33 / 60 example, which may be received from an AF / AS) and / or an indication to perform oscillation measurements to a second network device (e.g., an SMF), and the second network may forward the received information to a third network device (e.g., a UPF) configured to perform the oscillation measurements. In some examples, the second network device (e.g., the SMF) may not receive the DL periodicity information and may request that the third network device (e.g., the UPF) determine the DL periodicity.

[0101] In 2, the third network device (e.g., the UPF) can, after receiving control information related to the flicker measurement (e.g., N6 flicker measurement control information), perform one or more flicker measurements based on the control information. For example, the third network device can measure and / or report, based on the received control information, which may include the flicker monitoring indications and / or rules described in this document, N6 flicker information associated with a DL periodicity for a QoS flow in the downlink direction. As part of the process, the third network device can map a service data flow (SDF) to a QoS flow.

[0102] In 3, the third network device (e.g., the UPF) can provide oscillation measurement information (e.g., an oscillation measurement result) to the second network device (e.g., the SMF).

[0103] In 4, the second network device (e.g., the SMF) can provide swing information to a RAN node, such as a base station.

[0104] In 5, the RAN node can use the received swing information to configure the CDRX for a WTRU.

[0105] The example shown and described in relation to Figure 2 may assume that the second network device (e.g., SMF) can provide DL periodicity information per traffic flow (e.g., per SDF), or that the second Petition 870250090750, dated 06 / 10 / 2025, page 43 / 94 A 34 / 60 network device (e.g., SMF) can request a third network device (e.g., UPF) to measure the DL periodicity per traffic flow (or per SDF). The example shown and described in relation to Figure 2 can also assume that a traffic flow (e.g., or SDF) can be mapped to a QoS flow, and / or that the flicker can be measured per QoS flow.

[0106] A wireless communication network (e.g., a 5G (5GS) system) can perform ripple measurements for XRM traffic. A QoS flow associated with one or more sets of PDUs can be associated with a PDU Set Delay Budget (PSDB). Ripple between sets of PDUs can be measured and reported, for example, if PDU set-based handling is enabled in the communication system. An AF / AS can configure or request ripple monitoring at a PDU set level and / or at a burst level, for example, to facilitate integrated PDU set handling. This is because, when integrated PDU set handling is enabled, an application layer can make use of a PDU if (e.g., only if) the entire PDU set has been received. In these situations, ripple between PDUs may be less relevant than ripple between sets of PDUs.

[0107] In some examples, a WTRU can facilitate communication between a device connected (e.g., plugged in or associated) to the WTRU and an application server (AS). As described in this document, the AS (or AF) can configure or request a network (e.g., a wireless communication network) to measure and report instability between the AS and the connected device.

[0108] The wireless communication network (e.g., a 5GS) can leverage the manipulation of the PDU set to help reduce flicker at the application layer, so that flicker does not negatively impact the user experience. In some examples, a payload playback buffer Petition 870250090750, dated 06 / 10 / 2025, page 44 / 94 35 / 60 can be deployed for RTP flows. Some traffic characteristics or specific sets of traffic may have different jitter requirements. For example, an application may prefer that jitter between I-frames (e.g., for video content) be reduced with a higher priority than jitter between P-frames. PDU set manipulation can be used to perform PDU set-level buffering, for example, to minimize jitter, taking into account XRM traffic information such as PDU set importance values.

[0109] The wireless communication network (e.g., a 5GS) can help a RAN node, such as a base station, to configure CDRX parameters, for example, if more than one traffic flow (e.g., more than one SDF) is linked to the same QoS flow.

[0110] Figure 3 illustrates an exemplary scenario with more than one SDF per QoS flow. As shown in Figure 3, DL periodicity can be a property of an SDF and / or of the DL traffic arriving at a network device (e.g., a UPF) through the SDF. The network device may receive information that can help it calculate the DL periodicity, for example, if the network device is requested to derive the periodicity (e.g., when the DL periodicity is not provided by the AF).

[0111] As shown in Figure 3, oscillation can be measured by QoS stream. There can be multiple multiplexed SDFs for a QoS stream, and the SDFs can have different periodicities. The DL transmissions associated with the SDFs may not be time-aligned, even if the SDFs have the same periodicity. A network can provide support for calculating oscillation by QoS stream.

[0112] The modalities of the present disclosure contemplate that the oscillation monitoring at a set level of PDUs and / or at a level of Petition 870250090750, dated 06 / 10 / 2025, p. 45 / 94 A 36 / 60 burst can be performed. The oscillation between two packets can indicate (for example, be defined as) the difference (for example, in absolute value) between the forwarding delay of the two packets (for example, which may be received consecutively) that may belong to the same flow.

[0113] Considering two consecutive sets of PDUs, the first PDUs received from the sets of PDUs can be denoted as PDUi and PDUi', respectively, and the last PDUs received from each set of PDUs can be denoted as PDUn and PDUn', respectively. If we denote tri and tR1 as the transmission and reception times of PDUi, tn- and Irt as the transmission and reception times of PDUi', tTN and tRN as the transmission and reception times of PDUn, tTN' and tRN1' as the transmission and reception times of PDUn', the oscillation J1 between the respective first PDUs received from the two sets of PDUs can be calculated according to Eq. (1): J1 = |(tR1- tT1) — (tR1'- tT1')| (1)

[0114] The J2 oscillation between the respective last PDUs received from the two sets of PDUs can be calculated according to Eq. (2): J2 = |(tRN- tTN) - (tRN'- tTN')| (2)

[0115] In some examples, the set oscillation of PDUs can be determined or measured as the average of oscillation J1 and oscillation J2, for example, according to Eq. (3), which may be referred to in this document as a first approach: PDU_Set_Jitter = (J1+J2) / 2 (3)

[0116] In some examples, the jitter of the PDU set can be determined or measured as the jitter for the respective first PDUs received from the two PDU sets, for example, PDU_Set_Jitter = J1, which may be referred to in this document as a second approach. Petition 870250090750, dated 06 / 10 / 2025, p. 46 / 94 37 / 60

[0117] In some examples, the jitter of the PDU set can be determined or measured as the jitter for the respective last PDUs received from the two PDU sets, for example, PDU_Set_Jitter = J2, which may be referred to in this document as a third approach.

[0118] A PDU Set Delay (PSD) can indicate (e.g., be defined as) the delay that a set of PDUs can experience in the transfer between a WTRU and an N6 termination point (e.g., in a UPF). For example, the PSD can be calculated as the time between the reception of the first PDU and the reception of the last PDU in the PDU Set. Using this definition, the PDU set delays for PDU set 1 and PDU set 2 can be determined (e.g., using the previous notations) according to Eq. (4): PSD1 = |tRN- tT1| and PSD2 = |tRN'- trr| (4)

[0119] The oscillation related to two sets of PDU can also be measured, for example, based on the difference between PSD measurements, for example, according to Eq. (5), which may be referred to in this document as a fourth approach: PS_Jitter = |PSD1 - PSD2| (5)

[0120] The exemplary approaches described in this document may differ and may contain different information about the delay difference relative to the sets of PDUs. One or more (e.g., all) of the approaches may be relevant to an application function. For example, measuring flicker using Eq. (3) may indicate how much the flicker per PDU changes on average during the transmission of the set of PDUs. Measuring flicker using Eq. (5) may indicate how much the set-of-PDUs delay varies from one set of PDUs to the next, which may be useful, for example, in setting the PSDB value for the QoS stream carrying the set of PDUs. Petition 870250090750, dated 06 / 10 / 2025, p. 47 / 94 38 / 60

[0121] Figure 4 illustrates exemplary approaches for performing oscillation measurements at a set level of PDUs. Similar approaches for calculating and measuring oscillation at a burst level can be used, for example, by considering the respective first and last PDUs successfully delivered from two bursts (e.g., using any of the equations or approaches described in this document) to calculate an oscillation. The oscillation measurement and calculation can use, for example, the first PDU and / or set of PDUs in the burst, and the last PDU and / or set of PDUs in the burst.

[0122] PDU array oscillation monitoring requirements can be provisioned on a wireless communication network (e.g., a 5GS). In some examples, an application function (AF) may request the establishment of a multimodal XRM session with a WTRU via the wireless communication network (e.g., 5GS). The AF can provide requirements and / or configuration information related to oscillation monitoring. Figure 5 illustrates an example of how the wireless communication network (e.g., 5GS) can be configured with the information to support a multimodal service between the AF and the WTRU.

[0123] In 1 of Figure 5, the AF (or an AS) can request the configuration of a multimodal session with the WTRU via the wireless communication network (e.g., 5GS), for example, by invoking an NEF application programming interface (API). As an example, the API can be modeled after the Nnef_AFsessionWithQoS service operation. The AF can provide (e.g., in the request) service information such as flow description information, WTRU address, and / or a combination of data network name (DNN) and single network slice selection assistance (S-NSSAI) information. The AF can provide service requirements related to the multimodal service, for example, including requirements for Petition 870250090750, dated 06 / 10 / 2025, page 48 / 94 39 / 60 QoS monitoring and / or QoS parameters, such as a packet delay budget for a (e.g., each) media mode.

[0124] AF can provide flicker monitoring information (e.g., flicker monitoring parameters) for the multimodal service (e.g., which may be an XRM service). The flicker monitoring information / parameters for the XRM service may indicate, for example, one or more of the following: an indication of whether flicker monitoring is required; an indication of whether flicker monitoring should be performed at a PDU level, a set of PDUs level, or a burst level (e.g., for a media modality); a flicker monitoring period or flicker monitoring frequency (e.g., for downlink traffic and / or for a modality); an indication of which method should be used to calculate the flicker and / or which type of flicker should be measured; CODEC settings associated with a video modality of the XRM service;events / conditions that may trigger the wireless communication network to perform certain operations (e.g., reporting oscillation measurements and / or oscillation monitoring events to AF); uplink oscillation monitoring mode(s) and / or parameters; oscillation monitoring parameters related to round trip (RT); conditions for triggering oscillation monitoring for certain modes; PSIHI enablement and / or indication; oscillation monitoring parameters for burst level monitoring; a multimodal service ID; etc.;

[0125] AF can provide an indication of whether swing monitoring is needed and, if so, an indication of whether swing monitoring should be performed at a PDU level, a PDU pool level, or a burst level for a mode (e.g., each). AF can provide (e.g., for downlink traffic and / or for each Petition 870250090750, dated 06 / 10 / 2025, p. 49 / 94 40 / 60 mode) an oscillation monitoring period and / or an oscillation monitoring frequency. AF can provide oscillation monitoring requirements for the PDU set (e.g., frequency, period, etc., for each mode) if PDU set manipulation is enabled for an XRM service.

[0126] AF can provide an indication of which method should be used to calculate the oscillation and / or which type of oscillation should be measured. AF can indicate which method it prefers the wireless communication network to use, for example, if AF is aware of or has a pre-agreement with the wireless communication network about the possible methods to be used to calculate the oscillation (e.g., PDU array oscillation).

[0127] AF can provide (for example, for some modes, such as the video mode) different codec settings that the video mode may be able to adopt for the XRM service. For example, AF can provide different flicker monitoring parameters for different video resolutions, frame rate combinations, etc. AF can provide the parameters in advance so that when the wireless communication network is aware that the codec settings have been changed or are about to be changed, the wireless communication can change or recover the flicker monitoring parameters accordingly. The parameter sets can be indexed so that if the index of the codec setting used has been changed, the wireless communication network knows which flicker monitoring parameters are being used.

[0128] The AF can specify events that can trigger the wireless communication network to perform certain operations, including, for example, reporting oscillation measurements and / or oscillation monitoring events to the AF. For example, the AF can provide threshold values ​​for the oscillation of a set of PDUs, of Petition 870250090750, dated 06 / 10 / 2025, p. 50 / 94 41 / 60 so that, if a PDU array oscillation measurement exceeds the limit, the wireless communication network can report the event to the AF (for example, the report can additionally indicate the oscillation measurement results). For example, the AF can provide different limits and / or ranges for oscillation values ​​(for example, for each mode), and the wireless communication network can report to the AF to which range the oscillation belongs (for example, or perform a specific action, if possible).

[0129] AF can provide an uplink oscillation monitoring mode and / or parameters, for example, similar to those of the downlink (e.g., measurement period, reporting frequency and / or event notification configuration). AF can provide oscillation monitoring parameters related to round trip (RT). In some scenarios, AF may be interested in round trip oscillation measurement information, for example, instead of DL or UL oscillation measurement information.

[0130] AF can specify conditions that may trigger ripple monitoring for one or more specific modes. For example, AF can provide a delay budget (e.g., PDU set delay budget) and / or delay budget monitoring for one (e.g., each) mode. AF can provide a delay difference threshold between different modes of the XRM service. AF can deem it irrelevant to measure ripple, for example, if the delay measurement is above a (e.g., determined) value. AF can instruct the wireless communication network to stop ripple monitoring for certain modes, for example, if the delay difference measurement between two modes is above a (e.g., determined) threshold (e.g., because synchronization between modes is not maintained by a threshold value). Related monitoring versus Petition 870250090750, dated 06 / 10 / 2025, page 51 / 94 42 / 60 separate monitoring may not be relevant or unnecessary, for example, if other monitoring is not satisfactory.

[0131] AF can provide an indication of whether integrated PDU set handling is enabled and / or an indication of PSIHI. When integrated PDU set handling is enabled, some or all of the PDUs in a PDU set may be required for the PDU set to be useful in an application layer. For example, if all PDUs in a PDU set are required for the PDU set to be useful, the PDU set may be discarded if one of its PDUs is lost. In some examples, the absence of an indication of integrated PDU set handling being enabled may mean that it is possible to lose one or more (e.g., some) PDUs from a PDU set (e.g., no more than a certain percentage of PDUs) without considering the PDU set irrelevant and discardable (e.g., the PDU set may be retained in this situation).In some instances (e.g., depending on the presence of an integrated PDU set handling enable indication), the AF may (e.g., implicitly) instruct a wireless communication network to perform oscillation monitoring differently (e.g., for each mode). An integrated PDU set handling enable indication may impact which PDU sets can be considered for a PDU set oscillation measurement and / or how the oscillation can be measured (e.g., for partially recovered PDU sets or fully received PDU sets). The AF may provide one or more parameters indicating the method or approach to be used and / or which type of PDU set to use for oscillation monitoring (e.g., for each mode).

[0132] AF can provide oscillation monitoring parameters for oscillation monitoring at the burst level. AF can provide information on Petition 870250090750, dated 06 / 10 / 2025, page 52 / 94 43 / 60 traffic description for bursts, which may be in the form of a 3-tuple IP. If, for example, more than one mode is carried within a QoS flow, the AF may provide equal or different burst-level swing measurements for each mode. The AF may, in this case, provide different monitoring parameters for the traffic descriptor of each XRM mode. The AF may specify whether it requests intra-burst (e.g., within the burst itself) and / or inter-burst (e.g., between consecutive bursts) swing measurements. The AF may provide a measurement period, which may be a period of time during which a swing measurement can be performed. The AF may provide a sampling period, which may represent the frequency with which the wireless communication network (e.g., a 5GS) can collect a sample of PDUs / set of PDUs and use it in the burst-level swing calculation.For example, AF might indicate that, within a 20 ms measurement period, the wireless communication network should sample a PDU / set of PDUs every 4 ms and use the sample (e.g., including transmission and reception times) for the flicker measurement.

[0133] AF can provide several sets of PDUs to be used for burst-level oscillation measurement over a (e.g., specified) period of time. For example, AF can request the use of five (5) sets of PDUs every 30 ms to measure oscillation. AF (e.g., if possible) can specify which sets of PDUs to use for a measurement. For example, AF can indicate that you want the wireless communication network to include the first set of PDUs as well as the last set of PDUs in the burst(s) to be used to calculate oscillation. AF can use traffic characteristics as parameters. For example (for example, for a video mode), AF might request the use of 75% I frames and 25% non-I frames in the burst wobble calculation, and / or AF might provide a frame pattern to be used to calculate burst-level wobble (for example, using the IPPPI pattern to calculate wobble). Petition 870250090750, dated 06 / 10 / 2025, page 53 / 94 44 / 60

[0134] The AF can provide a multimodal service ID, which can be an identifier that associates multimodal flows belonging to the same multimodal service. The AF can send the multimodal session configuration request and / or the oscillation monitoring information (e.g., oscillation monitoring parameters) to the NEF in 1 of Figure 5.

[0135] In 2 of Figure 5, the NEF can authorize the AF request.

[0136] In 3a of Figure 5, the NEF can send a policy authorization request to another network device, such as a PCF. The NEF can send to the PCF (for example, in the policy authorization request or in a separate message) the information that was provided to the NEF in 1. The information may include, for example, traffic flow descriptors, a WTRU address, and / or a multimodal service ID. The information may include the set of PDUs and / or other swing monitoring parameters.

[0137] In 3b of Figure 5, the PCF can authorize the NEF request. The PCF can generate flicker monitoring policies for the relevant multimodal XRM service based on the request. The policies can be part of a QoS monitoring rule (e.g., which can be included in one or more PCC rules), for example, if other parameters, such as the PDU set delay, are requested for monitoring by the AF for the XRM service. The PCF can associate multiple (e.g., two) QoS monitoring rules with a common identifier.

[0138] In 4 of Figure 5, the PCF can send a policy authorization response message to the NEF, for example, to confirm authorization of the service request.

[0139] In 5 of Figure 5, NEF can send a message to AF, for example, to confirm the provisioning of the XRM service with the parameters and information provided by AF in 1. Petition 870250090750, dated 06 / 10 / 2025, p. 54 / 94 45 / 60

[0140] In 6a and 6b of Figure 5, the PCF can send information about the oscillation monitoring (e.g., the oscillation monitoring policy determined by the PCF) to another network device, such as the SMF, and the SMF can forward the oscillation monitoring policy to another network device, such as the UPF. This information (e.g., the policy) provided in 6a and 6b may include or reflect the information provided in 1, and the UPF can use the information (e.g., a measurement period and / or a sampling period) to configure an oscillation measurement procedure (e.g., with the corresponding periods and appropriate timers).For example, UPF can use the information to determine the granularity of the oscillation monitoring / measurement to be performed (e.g., for each mode), such as whether oscillation monitoring / measurement should be performed per PDU, per set of PDUs, or per burst; whether oscillation monitoring / measurement is for the uplink and / or the downlink; and / or which method to use for oscillation monitoring / measurement.

[0141] UPF can use the information to configure triggers and conditions for sending a notification about oscillation measurement (e.g., a measurement report) to SMF. For example, triggers and conditions can include a reporting frequency. As another example, triggers and conditions can include a threshold value for sending the notification to SMF (e.g., the notification can be sent if the measured oscillation exceeds the threshold value).

[0142] As described in this document, PDU cluster manipulation can be enabled on a wireless communication network (e.g., a 5GS) for a PDU session carrying XRM traffic. PDU cluster oscillation or burst level monitoring can be requested, and the UPF can use PDU sequence numbers, PDU cluster sequence numbers, and / or an end-of-burst indication to determine which Petition 870250090750, dated 06 / 10 / 2025, p. 55 / 94 46 / 60 PDUs or sets of PDUs are used for oscillation measurement (e.g., to add timestamps). Some of this information may be available to the UPF in a header (e.g., a GTP-U header) of the PDUs in the set of PDUs.

[0143] UPF may use (e.g., if available) PDU set importance information to determine whether a given set of PDUs should be considered for a flicker calculation. UPF may use the PDU set importance value to differentiate between I-frames and P-frames (e.g., for the video modality), for example, if a standard for flicker measurement (e.g., for burst-level flicker monitoring) has been provided and / or if a percentage of I-frames to be used for flicker measurement (e.g., for burst-level flicker monitoring) has been provided.

[0144] In 6c of Figure 5, the wobble monitoring policy described in this document (e.g., including wobble monitoring parameters) can be sent to a WTRU. The wobble monitoring policy can be sent to the WTRU, for example, by the SMF, which can send wobble monitoring-related rules to the WTRU as part of a QoS rule. As another example, the wobble monitoring policy can be provided to the WTRU by the PCF (e.g., through a WTRU configuration update procedure).

[0145] In 7 of Figure 5, the WTRU and / or UPF can perform oscillation measurement (e.g., for DL ​​and / or UL traffic), for example, using one or more of the oscillation calculation techniques described in this document.

[0146] In 8a and 8b of Figure 5, the UPF and / or WTRU can send an indication of the oscillation measurement results to a network device, such as an SMF. Petition 870250090750, dated 06 / 10 / 2025, p. 56 / 94 47 / 60

[0147] In 9 of Figure 5, the PCF can send the result of the ripple measurement or a notification related to the ripple manipulation result to the AF (e.g., via the NEF). The AF (or AS) can leverage the ripple manipulation result. For example, the AF can adjust the ripple buffer parameters at the application level. For instance, the AF might decide to reduce the size of the ripple buffers for a mode, such as a mode where the ripple is considerably low. The AF might decide to increase the PDU set delay budget (PSDB) for a mode, for example, if the AF receives an indication that the PDU set-level ripple for the mode has exceeded a given threshold. An increase in the PSDB for a mode can allow the application server to take into account ripple greater than the threshold variation, which can aid in QoS manipulation based on the PDU set in the RAN.

[0148] AF can use oscillation between WTRU and UPF along with N6 oscillation (e.g., between AS and UPF) that AF already knows to evaluate the overall oscillation. AF can decide to adjust its buffers based on the overall oscillation assessment.

[0149] AF may decide to change the frame rate of a video mode based on the result of the flicker measurement. For example, for videos supplied at 120 fps, if AS determines that the set-level PDU flicker is high (e.g., exceeds a threshold), AS may switch to a 90 fps setting so that the flicker decreases and has less effect on the video mode.

[0150] Oscillation monitoring requirements related to the PDU array can be provided for devices connected (e.g., fixed) to a WTRU. In one example, a WTRU exchanging traffic with an AF / AS for an XRM service can be connected to other devices (e.g., augmented reality glasses and / or haptic gloves) and can receive XRM traffic. Petition 870250090750, dated 06 / 10 / 2025, page 57 / 94 48 / 60 associated with these devices. In this scenario, AF and a wireless communication network can configure oscillation measurement / reporting between the WTRU and a network device (e.g., UPF) for a connected link for each mode.

[0151] Figure 6 illustrates an example of a procedure for provisioning oscillation monitoring, oscillation measurement and / or reporting for a WTRU with connected devices.

[0152] As shown in Figure 6, in 1, with the connection enabled, an AF can request the configuration of a multimodal session (e.g., for XMR services) with a WTRU via a wireless communication network (e.g., a 5GS). The AF can do this, for example, by invoking a NEF API. The AF can provide swing monitoring parameters for the connected link. The AF can provide end-to-end swing monitoring requirements. Based on the information provided by the AF, the wireless communication network can derive one or more swing monitoring rules or requirements for one or more communication links or segments, including, for example, a UPF-WTRU segment and / or a connected segment. The swing monitoring requirements may include a connected device requirement. Based on the requirements, the WTRU can monitor a connection transmission delay between the WTRU and the connected device.WTRU can report monitored connection transmission delay to AF.

[0153] ] In the example shown in Figure 6, a PCF can authorize a swing monitoring request (e.g., from AF) and generate one or more swing monitoring policies for the multimodal session (e.g., related to XRM services). The swing monitoring policies can include WTRU swing monitoring parameters for the UPF and / or connection swing monitoring parameters. The PCF can send the policies to an SMF, which can forward them to a UPF and to the WTRU. Petition 870250090750, dated 06 / 10 / 2025, page 58 / 94 49 / 60

[0154] In 2 of Figure 6, WTRU can configure oscillation monitoring with the device connected.

[0155] In 3 of Figure 6, the WTRU can perform oscillation measurement for the connected link.

[0156] In 4a of Figure 6, the WTRU can send the oscillation measurement results to the SMF. In examples, the measurement results sent to the SMF may not indicate a delay quote request, but may indicate a measurement or an estimate of the transmission delay between the WTRU and the connected device. Such an estimate may be based on a pre-configuration. For example, the WTRU may be configured to report transmission delays for devices connected to the WTRU via Bluetooth. The WTRU may be configured to calculate delays based on a formula. The inputs to the formula may be, for example, the type of RAT used to connect to the WTRU and the distance between the WTRU and the connected device. In the measurement results sent to the SMF, the WTRU may include a 4-tuple IP to which the measurement results may be associated.

[0157] In 4b of Figure 6, the SMF can report a PCF connection measurement result, based on the measurement results provided by the WTRU.

[0158] In 5 of Figure 6, the PCF can use the information reported by the SMF to create or change PCC rules. For example, the PCF can know, from the reported information, that significant flicker may come from the connected link, and the PCF can send a notification (e.g., regarding changes to PCC rules and / or changes to QoS parameters) to the AF so that one or more application layer settings can be adjusted (e.g., by the AF) to reduce the flicker (e.g., the PCF may not be able to resolve the flicker problem on its own).

[0159] In 6 of Figure 6, the PCF can send the oscillation measurement results and / or a notification related to the oscillation measurement results. Petition 870250090750, dated 06 / 10 / 2025, p. 59 / 94 50 / 60 for AF (e.g., via NEF). For example, if the PCF knows that a significant oscillation is coming from the connected link, the PCF can indicate to the AF that the oscillation cannot be improved further.

[0160] A PDU-set level payload playback buffer can be implemented in a WTRU and / or a UPF. A PDU-set level playback delay buffer can be implemented in a WTRU and / or a UPF. Buffers can be configured, used, and / or manipulated at the PDU-set level (e.g., considering PDU-set information when storing and / or releasing data to reduce jitter associated with a PDU set). Figure 7 illustrates an example of a PDU-set level playback delay buffer. The buffer can be similar to a payload playback buffer used in an application layer to reduce jitter associated with a data stream (e.g., comprising RTP packets). Buffers can be used to reduce jitter in a wireless communication network.A WTRU can be configured with PDU set handling capabilities to reduce jitter associated with downlink traffic at the PDU set level. A network device, such as a UPF, can be configured with PDU set handling capabilities to reduce jitter associated with uplink traffic at the PDU set level. These capabilities can use either PDU set-level playback buffering or PDU set-level playback delay buffering for PDU sets. The buffer can be used to handle PDU set-level packets. The buffer can be characterized by a jitter buffer size and / or a buffer delay. These parameters can be different and may change for various scenarios and deployments.

[0161] The handling of PDU sets with the playback buffer may depend on the type of PDU sets, the mode associated with the sets of Petition 870250090750, dated 06 / 10 / 2025, p. 60 / 94 51 / 60 PDUs, based on the sizes of the PDU sets and / or the respective importance of the PDU sets. For example, PDU sets with certain importance values ​​(e.g., I-frames) may be prioritized over PDU sets with other importance values.

[0162] Monitoring and flicker reduction (e.g., for XRM services) can be performed based on the importance of PDU sets. Figure 8 illustrates an example of a procedure for monitoring and minimizing flicker based on PDU set playback buffers and / or PDU set importance.

[0163] As shown in Figure 8, in 1, the procedure shown in Figure 5 (e.g., steps 1 to 6c) regarding the provisioning of oscillation monitoring information to a wireless communication network (e.g., a 5GS) and / or a WTRU can be performed. In addition to the oscillation monitoring parameters described in association with the procedure shown in Figure 5, an AF can provide additional and / or alternative parameters. For example, the AF can provide periodicity information to the wireless communication network to facilitate the configuration of oscillation measurement by PDU set importance value. The AF can provide different oscillation monitoring parameters depending on the PDU set importance value. The AF can provide the importance level (e.g., a threshold importance level) of a PDU set for which an oscillation measurement should be performed.For example, for a video modality, AF might be interested in knowing the flicker related to I-frames; therefore, AF can provide an importance level or indication to show that flicker for sets of PDUs associated with I-frames should be measured. AF can provide multiple importance values ​​for sets of PDUs for which flicker monitoring should be performed (e.g., I-frame versus B-frame for a...). Petition 870250090750, dated 06 / 10 / 2025, p. 61 / 94 52 / 60 video mode). AF can provide information that helps configure the playback delay buffer parameters of the PDU set, such as buffer sizes and / or buffer delay sizes.

[0164] In 2a of Figure 8, user plane XRM DL traffic can be sent from AF to a WTRU.

[0165] In 2b of Figure 8, the PDU pool traffic arriving at the WTRU can pass through a PDU pool-level replay delay buffer to reduce jitter (e.g., before the traffic is sent to an application layer).

[0166] In 3a of Figure 8, the WTRU can exchange UL traffic with a network device, such as a UPF.

[0167] In 3b of Figure 8, the UL PDU pool traffic arriving at the UPF can be passed through a PDU pool replay buffer to reduce jitter.

[0168] In 3c of Figure 8, the UPF can forward UL traffic to the AF.

[0169] In 4 of Figure 8, the WTRU and / or the UPF can perform oscillation measurements, for example, using one or more of the oscillation determination techniques described in this document.

[0170] In 5 of Figure 8, the wireless communication network (e.g., WTRU, UPF, and PCF) can send an oscillation measurement result and / or corresponding event notifications to the AF (e.g., via NEF).

[0171] In 6 of Figure 8, AF can, according to the oscillation measurement results received and / or notifications, decide to change the parameters of the PDU set playback delay buffer, such as buffer size and / or buffer delay size.

[0172] In 7 of Figure 8, AF can provide changes in the wireless communication network, for example, using the procedure shown in Figure 5. Petition 870250090750, dated 06 / 10 / 2025, p. 62 / 94 53 / 60

[0173] A CDRX can be configured for a QoS flow that can be associated with multiple SDFs. A WTRU may be interested in receiving multiple traffic flows (e.g., or SDFs), such as XR traffic flows. A traffic flow (e.g., each) can be associated with a set of QoS requirements and / or QoS characteristics. Traffic for the traffic flows can be divided into sets of PDUs. The mapping of traffic flows (e.g., XR traffic flows) to QoS flows can be based on the QoS parameters of the XR flows. The QoS flow can represent the finest granularity of QoS differentiation in a PDU session. A QoS flow can be expected to (e.g., only) multiplex traffic that has similar QoS requirements and / or characteristics. The AF can provide assistance information related to the set of PDUs for dynamic PCC control.Figure 9 shows an example procedure (e.g., for a RAN node, such as a base station) for configuring CDRX for a WTRU interested in receiving multiple traffic flows (e.g., multiple SDFs), such as multiple XR traffic flows associated with a QoS flow.

[0174] As shown in Figure 9, in 0, an AF can provide the DL periodicity for a subset of SDFs (e.g., SDF_set1). As a result, the DL periodicity may be known for SDF_set1 and unknown for other SDFs (e.g., SDF_set2). One or more of the following PDU set-related assistance information can be provided to a NEF and / or a PCF, for example, using an AF session with a given QoS procedure: PDU set QoS parameters and / or a protocol description that may indicate the protocol and / or payload type used by an SDF.

[0175] The PDU set QoS parameters and / or the protocol description (e.g., provided by the AF) can be used by the PCF to determine a QoS profile and / or by a PDU session anchor UPF (PSA). Petition 870250090750, dated 06 / 10 / 2025, pp. 63 / 94 54 / 60 to identify PDU set information. PDU set information may include, for example, one or more of the following: a PDU set sequence number; an indication of a final PDU in the PDU set; a PDU sequence number within the PDU set; and / or a PDU set importance value, which may indicate the relative importance of the PDU set compared to other PDU sets within the QoS flow.

[0176] In 1 of Figure 9, the PCF can provide one or more policy rules to the UPF, for example, via the SMF. The policy rules can include PDU set QoS parameters, a protocol description, and / or N6 oscillation measurement control information, which can instruct the UPF to report N6 oscillation information associated with a DL periodicity for a QoS stream (e.g., one) in the downlink direction.Additional information that can be provided to UPF includes, for example, one or more of the following: a list of SDFs for which DL periodicity is provided (e.g., SDF_set1); a list of SDFs for which UPF can determine the DL periodicity for an SDF (e.g., SDF_set2); a list of SDFs for which UPF can determine the instability of an SDF (e.g., SDF_set3); an indication of which SDF can be the primary SDF; a reporting periodicity; reporting limits; and / or an instability calculation configuration.

[0177] The PCF can provide a list of SDFs for which the DL periodicity is provided (e.g., SDF_set1). For example, for each SDF in SDF_set1, the DL periodicity can be provided. The PCF can provide a list of SDFs for which the UPF can determine the DL periodicity for an SDF (e.g., SDF_set2). For example, for each SDF in SDF_set2, an indication can be provided as to whether the UPF should report the determined DL periodicity to the SMF. The PCF can provide a list of SDFs for which the Petition 870250090750, dated 06 / 10 / 2025, pp. 64 / 94 55 / 60 UPF can determine the oscillation of an SDF (e.g., SDF_set3). For example, for each SDF in SDF_set3, an indication can be provided as to whether UPF should report the determined oscillation to the SMF. PCF can provide an indication of which SDF might be the primary SDF. A relative time difference (e.g., delta) calculated for the wireless communication network (e.g., a 5G system) can be relative to the primary SDF.

[0178] The PCF can provide a reporting periodicity, for example, a time interval between N6 oscillation measurement reports from the UPF to the SMF. The periodicity can be common to multiple SDFs (e.g., all) or common to a group of SDFs. For example, (e.g., all) SDFs with the same DL periodicity can be configured with the same reporting periodicity. The UPF can be configured with multiple thresholds. For example, periodicities can be related to a change in oscillation measurements, a change in measured DL periodicity, or a change in a relative time difference (e.g., delta) between an SDF and the primary SDF.

[0179] The PCF can provide one or more reporting thresholds. For example, an N6 oscillation measurement report for the SMF can be sent when the measured oscillation exceeds a configured threshold. The configured thresholds can be common to multiple SDFs (e.g., all) or to a group of one or more SDFs. For example, (e.g., all) SDFs with the same DL periodicity can be configured with the same threshold. The UPF can be configured with multiple thresholds. For example, the thresholds can be related to a change in oscillation measurements, a change in the measured DL periodicity, or a change in the relative time difference (delta) between an SDF and the primary SDF.

[0180] PCF can provide a swing calculation configuration, which may include configuration information about which metric to measure. For example, the metric could be a mean, a variance, a standard deviation, a median, or Petition 870250090750, dated 06 / 10 / 2025, p. 65 / 94 56th / 60th percentiles K-ths. The oscillation calculation setting can specify an observation window, for example, the time during which the metric is obtained. The oscillation calculation setting can specify an observation sample size, for example, the minimum number of oscillation measurements that can be performed to determine the metric.

[0181] In 2 of Figure 9, the UPF can determine the periodicity of the SDFs in SDF_set2. The UPF can also measure the flicker of the SDFs in SDF_set3. The UPF can perform the measurements according to the flicker calculation configuration. The UPF can rely on the PDU set QoS parameters and / or the protocol description to identify the SDFs and / or the PDU sets within an SDF. The UPF can determine the relative time difference (e.g., delta) between the DL traffic arriving at one (e.g., each) SDF and the primary SDF.

[0182] Figure 10 shows examples of a first SDF (e.g., SDF 1, which may be a primary SDF), a second SDF (e.g., SDF2), and a determination of a DL periodicity and / or a relative time difference associated with the SDFs. SDFs may have different periodicities. The periodicities may be known by the UPF, for example, based on the SMF configuration and / or based on internal measurements. As shown in Figure 10, in some cases, the sets of PDUs in one (e.g., each) SDF may arrive earlier than expected, while in other cases, the sets of PDUs in the SDF may arrive later than expected. The UPF can find the relative time difference between SDF2 and SDF1 (e.g., the primary SDF), which may suggest that a set of SDF2 PDUs arrives delta ms after a set of SDF1 PDUs.UPF can determine when sets of PDUs are expected in UPF, for example, based on knowledge of the periodicities of the two SDFs and the calculated delta. Petition 870250090750, dated 06 / 10 / 2025, p. 66 / 94 57 / 60

[0183] Going back to Figure 9, in 3, UPF can provide an oscillation measurement report, such as an N6 oscillation measurement report, for SMF.The ripple measurement report provided by UPF may include, for example, one or more of the following: ripple information measured by SDF; a relative time difference (delta) between an SDF and the primary SDF; an indication of which SDF the UPF may use as the primary SDF; an indication of the QoS flow to which these SDFs may be linked, which may be provided if the UPF has multiple QoS flows carrying XRM traffic flows; a relative time difference between QoS flows, which may be provided if the UPF has multiple QoS flows carrying XRM traffic flows; a respective DL periodicity for each SDF flow, which may be applied if the UPF is requested to determine the periodicity; and / or an indication of the cause of sending the measurement report (e.g., a periodic report of delta values ​​between SDF2 and SDF1, the ripple change of SDF1 exceeding a threshold, etc.).UPF can provide the measurement report, for example, based on a configured reporting frequency and / or reporting limits.

[0184] In 4 of Figure 9, the SMF can send DL periodicity information, swing information, and / or delta information to a RAN node, such as a base station. The SMF can send the information, for example, whenever it receives a measurement report from the UPF. The SMF (for example, alternatively) can be configured with its own periodicity and / or limits for sending DL periodicity information, swing information, and / or delta information to the RAN. This SMF configuration is not shown in Figure 9.

[0185] The SMF may send the information to the RAN node as part of the TSCAI or as part of a signaling exchange between the SMF and the RAN node. The information provided by the SMF to the RAN node may include, for example, one or more of the following: an SDF identifier, for example, to identify the SDF; a Petition 870250090750, dated 06 / 10 / 2025, pp. 67 / 94 58 / 60 QoS flow identifier, for example, to identify the QoS flow to which the SDF is linked; a primary SDF, for example, used for relative time difference calculations; a relative time difference (e.g., delta) between the SDF and the primary SDF; a fluctuation measured by SDF flow; and / or DL ​​periodicity by SDF flow.

[0186] In 5 of Figure 9, the RAN node can use the oscillation information and / or DL ​​periodicity to configure the CDRX for the WTRU. For example, the RAN node can use the information to determine the approximate arrival times of DL traffic over (e.g., all) QoS flows to the WTRU. The RAN node can send the CDRX configuration information to the WTRU via an RRCReconfiguration message.

[0187] Figure 11 shows an example where a WTRU has a QoS stream with two SDFs with the same DL periodicity, and a RAN node determines an XRD cycle with the same periodicity. As shown in Figure 11, the RAN node can determine the expected arrival times of the PDU sets at the RAN node, where the PDUs can be from SDF1 (PDU set 1) and / or SDF2 (PDU set 2). The RAN node can make the determination, for example, based on DL periodicity information, flicker information, and / or SMF delta information. The RAN node can determine how long the WTRU should remain active (e.g., X seconds every T seconds). The RAN node can set the XRD cycle and / or the XRD activation / deactivation durations according to the ratio of X to T, and can configure the WTRU accordingly.

[0188] Figure 12 shows an example where a WTRU has a QoS flow with two SDFs with different DL periodicities, and a RAN node determines an XRD cycle with different periodicities. The RAN node can determine the expected arrival times of the PDU sets at the RAN node, and the PDU sets can be from SDF1 (set 1 of PDUs) and from Petition 870250090750, dated 06 / 10 / 2025, p. 68 / 94 59 / 60 SDF2 (set 2 of PDUs). The RAN node can make the determination, for example, based on DL periodicity information, oscillation information, and / or SMF delta information. Depending on the expected arrival time of the PDU sets for each SDF, the RAN node may or may not be able to determine an efficient X and T that take the SDFs into account. The RAN node can (for example, in this case) determine an X and T for each SDF (e.g., X1 and T1 for SDF1 and X2 and T2 for SDF2). The RAN node can configure the WTRU with two XRD cycles (e.g., a first XRD cycle for SDF1 and a second XRD cycle for SDF2). The WTRU can (for example, in this case) enter a power-saving state when (e.g., only when) both XRD cycles are in an OFF state.

[0189] The exemplary procedures described in this document may assume that a primary SDF is defined for each QoS flow. In some implementations (e.g., alternatives), a single SDF may be used as the primary SDF for multiple (e.g., all) QoS flows. The UPF may, in these implementations, report the relative time difference of the SDFs in (e.g., all) QoS flows relative to this primary SDF. Furthermore, signaling may be performed in these implementations to indicate the QoS flow to which the primary SDF is bound. Such signaling may be performed, for example, by signaling the primary SDF (e.g., from the UPF to the SMF, or from the SMF to the RAN node).

[0190] Although the resources and elements described above are described in specific combinations, each resource or element can be used in isolation, without the other resources and elements of the preferred modes, or in various combinations with or without other resources and elements. Although the implementations described in this document may consider specific 3GPP protocols, it is understood that the implementations described in this document are not limited to this scenario and may be applicable to other wireless systems. Petition 870250090750, dated 06 / 10 / 2025, pp. 69 / 94 60 / 60 example, although the solutions described in this document consider specific LTE, LTE-A, New Radio (NR) or 5G protocols, it is understood that the solutions described in this document are not limited to this scenario and are also applicable to other wireless systems.

[0191] The processes described above can be implemented in a computer program, software, and / or firmware embedded 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 via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard drives and removable disks, magneto-optical media, and / or optical media such as compact discs (CD-ROMs) and / or digital versatile discs (DVDs).A processor, in conjunction with software, can be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer. Petition 870250090750, dated 06 / 10 / 2025, pp. 70 / 94

Claims

1 / 4 CLAIMS 1. A network device associated with a wireless communication network, wherein the network device is CHARACTERIZED in that it comprises a processor configured to: receive information about one or more aspects of oscillation monitoring within the wireless communication network; determine an oscillation monitoring policy based on the information received; send the oscillation monitoring policy to another device on the wireless communication network; and receive, after sending the oscillation monitoring policy to the other device on the wireless communication network, an indication of an oscillation measurement result from the other device.

2. Network device, according to claim 1, CHARACTERIZED in that the processor is configured to receive information relating to one or more aspects of oscillation monitoring within the wireless communication network from a network exposure function (NEF) associated with an application server (AS) or an application function (AF).

3. Network device, according to claim 2, CHARACTERIZED in that the processor is further configured to transmit the indication of the oscillation measurement result to the NEF.

4. Network device according to claim 1, CHARACTERIZED in that information regarding one or more aspects of oscillation monitoring within the wireless communication network indicates that oscillation monitoring should be performed at a protocol data unit (PDU) set level or at a burst level. Petition 870250090750, dated 10 / 06 / 2025, pp. 91 / 94 2 / 4 5. Network device, according to claim 4, CHARACTERIZED in that the oscillation monitoring policy is associated with a PDU session comprising extended reality traffic.

6. Network device, according to claim 1, CHARACTERIZED in that the information relating to one or more aspects of oscillation monitoring within the wireless communication network indicates an oscillation measurement period or an oscillation sampling period.

7. Network device, according to claim 1, CHARACTERIZED in that information relating to one or more aspects of oscillation monitoring within the wireless communication network indicates an oscillation monitoring trigger condition.

8. Network device, according to claim 1, CHARACTERIZED in that the processor is configured to determine and send the oscillation monitoring policy as a quality of service monitoring rule.

9. Network device according to claim 1, characterized in that information is received by means of a policy authorization request, and in that the processor is further configured to transmit a policy authorization response confirming the use of the information received by means of the policy authorization request.

10. Network device, according to claim 1, CHARACTERIZED in that the network device is a wireless communication network policy control function, and where the other device is a wireless communication network session handling function.

11. A method implemented by a network device associated with a wireless communication network, wherein the method is CHARACTERIZED by the fact that it comprises: Petition 870250090750, dated 06 / 10 / 2025, pp. 92 / 94 3 / 4 receiving information regarding one or more aspects of oscillation monitoring within the wireless communication network; determining an oscillation monitoring policy based on the information received; sending the oscillation monitoring policy to another device on the wireless communication network; and receiving, after sending the oscillation monitoring policy to the other device on the wireless communication network, an indication of an oscillation measurement result from the other device.

12. Method, according to claim 11, CHARACTERIZED in that information relating to one or more aspects of oscillation monitoring within the wireless communication network is received by a network exposure function (NEF) associated with an application server (AS) or an application function (AF).

13. Method, according to claim 12, CHARACTERIZED in that it further comprises transmitting the indication of the oscillation measurement result to the NEF.

14. Method according to claim 11, CHARACTERIZED in that information regarding one or more aspects of oscillation monitoring within the wireless communication network indicates that oscillation monitoring should be performed at a protocol data unit (PDU) set level or at a burst level.

15. Method, according to claim 14, CHARACTERIZED in that the oscillation monitoring policy is associated with a PDU session comprising extended reality traffic.

16. Method, according to claim 11, CHARACTERIZED in that the information relating to one or more aspects of monitoring oscillation within the wireless communication network indicates an oscillation measurement period or an oscillation sampling period.

17. Method according to claim 11, CHARACTERIZED in that information relating to one or more aspects of oscillation monitoring within the wireless communication network indicates an oscillation monitoring trigger condition.

18. Method, according to claim 11, CHARACTERIZED in that the oscillation monitoring policy is determined and sent as a service quality monitoring rule.

19. A method according to claim 11, characterized in that information relating to one or more aspects of oscillation monitoring within the wireless communication network is received by means of a policy authorization request, and in that the method further comprises sending a policy authorization response that confirms the use of the information received by means of the policy authorization request.

20. Method according to claim 11, CHARACTERIZED in that the network device is a policy control function of the wireless communication network, and the other device is a session manipulation function of the wireless communication network. Petition 870250090750, dated 06 / 10 / 2025, pp. 94 / 94

Images