Detecting and indicating the end of bursts by a user plan function.

Description

1 / 57 “DETECTION AND INDICATION OF END OF BURST BY A USER PLANE FUNCTION” CROSS-REFERENCE TO RELATED REQUESTS

[001] This application claims the benefit of Provisional Patent Application No. 63 / 454,209, filed on March 23, 2023, the content of which is incorporated herein by reference. BACKGROUND

[002] Mobile communications using wireless communication continue to evolve. A fifth generation of mobile communication radio access technology (RAT) may be called new radio (NR) 5G. A previous (legacy) generation of mobile communication RAT may be, for example, the long-term evolution (LTE) of fourth generation (4G). SUMMARY

[003] This disclosure describes devices and methods for detecting and indicating the end of a burst by a user plane function (e.g., by a network node).

[004] The network node can receive configuration information indicating a condition indicative of the end of a burst of packet data unit (PDU) sets. The network node can receive the burst of PDU sets, where the burst of PDU sets comprises one PDU. The network node can detect, based on the PDU that satisfies the condition, the end of the burst of PDU sets. The network node can send, to a base station, an indication of the end of the burst of PDU sets.

[005] The configuration information may include an information element (IE) indicating the start of a second burst of PDU sets. The network node may receive the second burst of PDU sets. The network node may detect the end of the first burst of PDU sets by determining, based on the Petition 870250078356, dated 02 / 09 / 2025, page 9 / 94 2 / 57 start of the second burst of PDU sets, a number of PDU sets in the second burst of PDU sets. The network node can determine a burst pattern based on the number of PDU sets in the second burst of PDU sets. The network node can determine that the PDU satisfies the condition based on the burst pattern.

[006] The network node can determine a first timestamp associated with a first set of PDUs in the burst of PDU sets. The network node can determine a second timestamp associated with a second set of PDUs. The second timestamp can be different from the first timestamp. The network node can determine that the PDU satisfies the condition based on the second timestamp being different from the first timestamp.

[007] The network node can identify a message header of a PDU in the burst of PDU sets. The message header can indicate the end of the burst of PDU sets. The network node can determine that the PDU satisfies the condition based on the indication in the message header.

[008] The network node can determine that a set of PDUs was received during a first time duration. The burst of PDU sets can include the set of PDUs. The network node can determine a second time duration based on the determination that the set of PDUs was received during the first time duration. The network node can, under a condition that the second time duration has elapsed, determine that the PDU satisfies the condition.

[009] The network node can determine a number of PDU sets in the burst of PDU sets. The network node can determine a PDU set based on the determined number of PDU sets. The network node can determine the expected byte size value of the determined PDU set. The network node can determine a received byte size value. The received byte size value Petition 870250078356, dated 02 / 09 / 2025, page 10 / 94 3 / 57 of bytes may indicate a calculated byte size of the given set of PDUs. The network node may, under the condition that the received byte size value is within an acceptable range of the expected byte size value, determine that the PDU satisfies the condition.

[010] The network node can determine an expected byte size value from the burst of PDU sets. The network node can determine a received byte size value based on the burst of PDU sets. The network node can, under a condition that the received byte size value is within an acceptable range of the expected byte size value, determine that the PDU satisfies the condition.

[011] The network node can determine a number of PDU sets that are associated with the burst of PDU sets. The network node can determine an expected byte size value from the number of PDU sets. The network node can determine a received byte size value based on the number of PDU sets. The network node can, under a condition that the received byte size value is within an acceptable range of the expected byte size value, determine that the PDU satisfies the condition.

[012] The configuration information may include an information element (IE) indicating a PDU set identifier (ID). The network node may determine a burst pattern based on the PDU set identifier. The network node may determine a number of PDU sets based on the burst pattern. The number of PDU sets may be associated with the PDU set burst. The network node may determine that the PDU satisfies the condition based on the determined number of PDU sets. BRIEF DESCRIPTION OF THE DRAWINGS

[013] Figure 1A is a system diagram that illustrates an example of a communications system in which one or more advertised modes can be Petition 870250078356, dated 02 / 09 / 2025, page 11 / 94 4 / 57 implemented.

[014] Figure 1B is a system diagram that illustrates an example of a wireless transmit / receive unit (WTRU) that can be used within the communications system illustrated in Figure 1A, according to one embodiment.

[015] Figure 1C is a system diagram that illustrates an example of a radio access network (RAN) and an example of a central network (CN) that can be used within the communications system illustrated in Figure 1A, according to one embodiment.

[016] Figure 1D is a system diagram that illustrates an example of an additional RAN and an example of an additional CN that can be used within the communications system illustrated in Figure 1A, according to one embodiment.

[017] Figure 2 illustrates examples of data bursts and burst periodicity.

[018] Figure 3 illustrates an example of a user plane function (UPF) detecting the end of a burst.

[019] Figure 4 illustrates an example of a UPF configuration with burst information.

[020] Figure 5 illustrates an example of an RTP header extension using a one-byte header format.

[021] Figure 6 illustrates an example of an RTP header extension using a two-byte header format.

[022] Figure 7 illustrates an example of an RTP header format.

[023] Figure 8 illustrates an example of a UPF indicating the end of a detected burst. DETAILED DESCRIPTION

[024] Figure 1A is a diagram that illustrates an example of a communications system 100 in which one or more advertised modes can be Petition 870250078356, dated 02 / 09 / 2025, page 12 / 94 5 / 57 implemented. The 100 communications system can be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The 100 communications system can allow multiple wireless users to access this content by sharing system resources, including wireless bandwidth. For example, 100 communications systems can employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero-tail single-word DFT propagation OFDM (ZT UW DTS-s OFDM), single-word OFDM (UWOFDM), resource block filtered OFDM, filter bank multicarrier (FBMC), and the like.

[025] 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 important to note that the disclosed embodiments contemplate any number of WTRUs, base stations, networks and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment.By way of example, 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 hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a. Petition 870250078356, dated 02 / 09 / 2025, page 13 / 94 6 / 57 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 in commercial and / or industrial wireless networks and the like. Any of WTRUs 102a, 102b, 102c and 102d may be referred to alternatively as UE.

[026] Communication systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a and 114b may be any type of device configured to wirelessly interact with at least one of the WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. As an example, base stations 114a and 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR NodeB, 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 is important to note that base stations 114a and 114b can include any number of interconnected base stations and / or network elements.

[027] 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 referred to as a cell (not shown). These frequencies may be in the licensed spectrum, the unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide Petition 870250078356, dated 02 / 09 / 2025, p. 14 / 94 7 / 57 coverage for a wireless service for a specific geographic area that may be relatively fixed or that may change over time. The cell may additionally be 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, i.e., one for each cell sector. In another embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each cell sector. For example, beamforming may be used to transmit and / or receive signals in the desired spatial directions.

[028] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c and 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).

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

[030] In one mode, base station 114a and WTRUs 102a, 102b and Petition 870250078356, dated 02 / 09 / 2025, page 15 / 94 8 / 57 102c may implement a radio technology, such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the 116 air interface using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[031] In one embodiment, base station 114a and WTRUs 102a, 102b and 102c can implement a radio technology, such as NR Radio Access, which can establish the 116 air interface using New Radio (NR).

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

[033] 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), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN) and the like.

[034] Base station 114b in Figure 1A can be a wireless router, a Home Node B, a Home eNode B, 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 Petition 870250078356, dated 02 / 09 / 2025, page 16 / 94 9 / 57 highway and similar. In one embodiment, base station 114b and WTRUs 102c and 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 yet another embodiment, base station 114b and WTRUs 102c and 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. As shown in Figure 1A, base station 114b can have a direct connection to the 110 Internet. Thus, base station 114b may not need to access the 110 Internet via CN 106 / 115.

[035] 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 and 102d. The data may have varying Quality of Service (QoS) requirements, such as different requirements for throughput, latency, error tolerance, reliability, data throughput, mobility 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 important to note 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 communicating with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology. Petition 870250078356, dated 02 / 09 / 2025, p. 17 / 94 10 / 57

[036] CN 106 / 115 may 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), User Datagram Protocol (UDP) and / or the 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, 112 networks may include another CN connected to one or more RANs, which may employ the same RAT as RAN 104 / 113 or a different RAT.

[037] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communications system 100 may include multimode capabilities (for example, WTRUs 102a, 102b, 102c, and 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.

[038] Figure 1B is a system diagram illustrating an example of a 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 numeric keypad 126, a touch-sensitive display / keyboard 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, remaining consistent with a Petition 870250078356, dated 02 / 09 / 2025, page 18 / 94 11 / 57 modality.

[039] 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 perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that allows WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmit / receive element 122.Although Figure 1B depicts processor 118 and transceiver 120 as separate components, it is important to note that processor 118 and transceiver 120 can be integrated into a single electronic package or chip.

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

[041] Although the transmission / reception element 122 is represented in Petition 870250078356, dated 02 / 09 / 2025, page 19 / 94 12 / 57 Figure 1B shows that 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.

[042] 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, WTRU 102 can have multimode capabilities. Thus, transceiver 120 can include multiple transceivers to allow WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[043] The WTRU 102 processor 118 can be coupled with and receive user input data from the speaker / microphone 124, the keyboard 126, and / or the touch-sensitive display / keyboard 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 numeric keypad 126, and / or the touch-sensitive display / keyboard 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 Subscriber Identity Module (SIM) card, a memory card, a Secure Digital Memory Card (SD), and the like.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). Petition 870250078356, dated 02 / 09 / 2025, page 20 / 94 13 / 57

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

[045] Processor 118 can also be coupled to GPS chipset 136, which can be configured to provide location information (e.g., longitude and latitude) regarding the current location of WTRU 102. In addition to, or replacing, GPS chipset 136 information, WTRU 102 can 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 WTRU 102 can acquire location information through any suitable location determination method, remaining consistent with a modality.

[046] The processor 118 may additionally 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 Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, a Petition 870250078356, dated 02 / 09 / 2025, page 21 / 94 14 / 57 activity tracker and similar. Peripherals 138 may include one or more sensors, which 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.

[047] The 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 may include an interference management 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 WTRU 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)) may be concurrent and / or simultaneous.

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

[049] RAN 104 may include eNode-Bs 160a, 160b, and 160c, although it is important to note that RAN 104 may include any number of eNode-Bs, remaining consistent with a modality. eNode-Bs 160a, 160b, and 160c Petition 870250078356, dated 02 / 09 / 2025, p. 22 / 94 15 / 57 may each include one or more transceivers for communication with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Thus, eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from WTRU 102a.

[050] Each of the eNode-Bs 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the UL and / or DL, and the like. As shown in Figure 1C, the eNode-Bs 160a, 160b, and 160c can communicate with each other via an X2 interface.

[051] The CN 106 shown in Figure 1C may include a mobility management 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 described 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.

[052] MME 162 can be connected to each of the eNode-Bs 160a, 160b, and 160c 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, and 102c, activating / deactivating the carrier, selecting a specific service gateway during an initial connection of WTRUs 102a, 102b, and 102c, and similar tasks. MME 162 can provide a control plane function for switching between RAN 104 and other RANs (not shown) that employ other radio technologies such as GSM and / or WCDMA.

[053] The SGW 164 can be connected to each of the eNodes B 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can generally route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The Petition 870250078356, dated 02 / 09 / 2025, page 23 / 94 16 / 57 SGW 164 can perform other functions, such as anchoring user plans during handovers between B eNodes, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, managing and storing contexts for WTRUs 102a, 102b, and 102c, and similar functions.

[054] SGW 164 can be connected to PGW 166, 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.

[055] CN 106 can facilitate communications with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communications between WTRUs 102a, 102b, and 102c and traditional fixed-line communication devices. For example, CN 106 can 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 can provide WTRUs 102a, 102b, and 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.

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

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

[058] 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 can have access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic from Petition 870250078356, dated 02 / 09 / 2025, page 24 / 94 17 / 57 BSS entry and / or exit. Traffic to 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 originating and destination STAs with a Direct Link System (DLS) configuration. In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all STAs) within or using the IBSS can communicate directly with each other.The IBSS communication mode may sometimes be referred to in the present invention as an "ad-hoc" communication mode.

[059] 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, the specific STA can back off. An STA (e.g., only one station) can transmit at any time on a given BSS.

[060] High Throughput (HT) STAs can use a 40 channel Petition 870250078356, dated 02 / 09 / 2025, p. 25 / 94 18 / 57 MHz of bandwidth for communication, for example, by combining the primary 20 MHz channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.

[061] Very High Throughput (VHT) STAs can support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 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 referred to as 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. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed on each stream separately. Streams can be mapped to the two 80 MHz channels, and data can be transmitted via a STA transmitter.At 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).

[062] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. The operating channel 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 Petition 870250078356, dated 02 / 09 / 2025, page 26 / 94 19 / 57 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).

[063] 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 operating mode with the lowest bandwidth. In the 802.11ah example, the primary channel may have a 1 MHz bandwidth for STAs (e.g., MTC-type devices) that support (e.g., only support) 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 (which only supports 1 MHz operating mode) transmitting to the AP, all available frequency bands can be considered occupied, even if most frequency bands remain idle and could be available.

[064] In the United States, the available frequency bands that can be used by 802.11ah range from 902 MHz to 928 MHz. In Korea, the available frequency bands range from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands range from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah ranges from 6 MHz to 26 MHz, depending on the country code.

[065] 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 Petition 870250078356, dated 02 / 09 / 2025, p. 27 / 94 20 / 57 to CN 115.

[066] 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 the 116 air interface. In a modality, gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may use beamforming to transmit and / or receive signals from gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, can use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, WTRU 102a. In one embodiment, the gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, the 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 may implement Coordinated Multipoint Technology (CoMP). For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

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

[068] 180a, 180b, 180c gNBs can be configured to communicate Petition 870250078356, dated 02 / 09 / 2025, p. 28 / 94 21 / 57 with WTRUs 102a, 102b, 102c in a standalone and / or 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., eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c can use one or more of the gNBs 180a, 180b, 180c as a mobility docking 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, 180b, and 180c, while also communicating / connecting to another RAN, such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement CC principles to communicate with one or more gNBs 180a, 180b, and 180c and one or more eNode-Bs 160a, 160b, and 160c substantially simultaneously.In the non-standalone configuration, eNode-Bs 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.

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

[070] The CN 115 shown in Figure 1D may include at least one AMF Petition 870250078356, dated 02 / 09 / 2025, page 29 / 94 22 / 57 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 CN 115, it is important to note that any of these elements may be owned and / or operated by an entity other than the CN operator.

[071] The AMF 182a, 182b can be connected to one or more gNBs 180a, 180b, 180c in RAN 113 via an N2 interface and can serve as a control node. For example, the AMF 182a, 182b can be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, managing the log area, terminating NAS signaling, managing mobility, and the like. 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 in WTRUs 102a, 102b, and 102c.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 services. 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.

[072] 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, Petition 870250078356, dated 02 / 09 / 2025, page 30 / 94 23 / 57 how to manage and allocate UE IP addresses, manage PDU sessions, control policy and QoS enforcement, provide downlink data notifications, and similar tasks. A PDU session type can be IP-based, non-IP-based, Ethernet-based, and similar.

[073] UPF 184a, 184b can be connected to one or more of gNBs 180a, 180b, 180c in RAN 113 via an N3 interface, 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. UPF 184, 184b can perform other functions such as packet routing and forwarding, user plane policy enforcement, support for multihomed PDU sessions, user plane QoS handling, downlink packet buffering, mobility tethering provision, and the like.

[074] CN 115 can facilitate communications with other networks. For example, CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between CN 115 and PSTN 108. In addition, CN 115 may 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, via interface N3 to UPF 184a, 184b and an interface N6 between UPF 184a, 184b and DN 185a, 185b.

[075] 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 invention relate to one or more of the following: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a. Petition 870250078356, dated 02 / 09 / 2025, p. 31 / 94 24 / 57 b, DN 185a-be / or any other devices described in this invention may be implemented 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 invention. For example, the emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[076] 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 may perform one or more, or all, of the functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more emulation devices may perform one or more, or all, of the functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for testing purposes and / or may perform tests using wireless over-the-air communications.

[077] One or more emulation devices may perform one or more, including all, of the functions while not 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 (e.g., under test) wired and / or wireless communication network to implement tests of one or more components. The emulation device(s) may be test equipment. Direct RF coupling and / or wireless communications via an RF circuit array (e.g., which may include one or more antennas) may be used. Petition 870250078356, dated 02 / 09 / 2025, p. 32 / 94 25 / 57 by emulation devices to transmit and / or receive data.

[078] Reference to a timer in the present invention may refer to a time, a period of time, a time tracking, a tracking of a period of time, a combination thereof and / or similar. Reference to the expiration of a timer in the present invention may refer to the determination that the time has elapsed or that the period of time has expired.

[079] Devices and methods for detecting end-of-bursts are provided in the present invention. For example, this disclosure describes devices and methods for detecting end-of-bursts (EOBs) in extended reality (XR) traffic and configuring such detection. EOB detection can be performed by the user plane function (UPF) or the radio access network (RAN). If the UPF performs the detection, the UPF can signal an EOB indication to the RAN. The RAN can use the EOB detection and / or indication to put the WTRU into a low-power state.

[080] Feature(s) associated with the detection and indication of UPF-based EOBs is / are provided in the present invention. The UPF can receive configuration information to detect the EOB from bundled data unit (PDU) sets. The UPF can detect EOB. The UPF can send an indication of the EOB to the RAN.

[081] Feature(s) associated with RAN-based detection and the use of EOBs is / are provided in the present invention. The RAN can receive configuration information to detect the EOB of PDU sets. The RAN can detect the EOB. The RAN can control the hibernation state of the WTRU based on the detection. The following abbreviations are used in the present invention: AF Application Function COMO Application Server DRX Discontinuous Reception EOB End of Burst (e.g., End of a burst) EOBI End of Burst Indication GTP-U Tunneling Protocol GPRS User Plane Protocol HE Header Extension Petition 870250078356, dated 02 / 09 / 2025, page 33 / 94 26 / 57 MOQ Media over Fast Protocol NG-RAN Next Generation Radio Access Network PCC Policy and Tariff Control PCF Policy Control Function PDU Packet Data Unit RTP Real-Time Protocol SMF Session Management Function SRTP Secure Real-Time Protocol UE User Equipment UPF User Plane Function WTRU Wireless Transmit / Receive Unit XR Extended Reality

[083] The terms “server”, “application server” and “application function” may be used interchangeably in the present invention.

[084] Feature(s) associated with the detection and indication of UPF-based EOBs is / are provided in the present invention.

[085] A network function (e.g., UPF) can receive configuration information to detect the EOB of PDU clusters. The configuration information can indicate a condition indicative of the EOB of the burst of PDU clusters. For example, network burst function (NEF) application programming interfaces (APIs) can define trigger information elements (IEs) to identify the start and / or end of the burst and / or a timeout between PDUs within a burst.

[086] The network node (e.g., the UPF) can receive sets of PDUs (e.g., on the N6 Interface, e.g., via RTP / SRTP). For example, the network node can receive a burst of PDU sets. The burst of PDU sets can include at least one PDU.

[087] UPF can detect the EOB of a burst of PDU sets. UPF can detect the EOB of a burst of PDU sets based on a PDU in the burst of PDUs that satisfies a condition. For example, UPF can detect the EOB of PDU sets based on a timestamp change, specific fields in RTP / SRTP headers / extensions / payload, a timeout, a Petition 870250078356, dated 02 / 09 / 2025, p. 34 / 94 27 / 57 number of PDU sets, a traffic pattern and / or similar.

[088] The UPF can signal the EOB to the RAN (e.g., NG-RAN) or it can provide the RAN with information that the RAN can use to detect the EOB. For example, the UPF can send an EOB indication (EOBI) and / or information (e.g., size information, etc.) to the RAN in GTP-U messages. As an example, the UPF can send an EOB indication from the PDU clusters to a base station.

[089] Resource(s) associated with the detection and use of RAN-based EOB is / are provided in the present invention.

[090] A RAN (e.g., NG-RAN) can receive configuration information (e.g., in a QoS profile). The RAN can use the configuration information to detect the EOB of a burst of PDU arrays. For example, the configuration information can indicate a condition indicative of the EOB of the burst of PDU arrays. The RAN can use EOB to control the hibernation state of a WTRU.

[091] The RAN can receive Service Data Stream (SDF) PDUs corresponding to XR traffic.

[092] RAN can detect an EOB (for example, from sets of PDUs). RAN may not be able to see the contents of the headers, but it can use timer-based approaches to detect an EOB.

[093] RAN can control the hibernation state (e.g., low power state) of a WTRU.

[094] Resource(s) associated with data bursts is / are provided in the present invention.

[095] A data burst can be a set of one or more PDUs generated and sent by an application in a short period of time. A data burst can be (for example, typically) associated with a burst periodicity. Petition 870250078356, dated 02 / 09 / 2025, p. 35 / 94 28 / 57 The burst periodicity can be configured in the control plane for an XR stream or set of streams. A data burst can include one or more sets of PDUs. For example, a data burst can carry a data unit from the application, such as a frame or a group of images. For example, a data burst (e.g., the same data burst) can carry different sets of PDUs, including media types corresponding to the same frame displayed to the user. The terms “data bursts,” “bursts,” and “burst transmissions” can be used interchangeably in the present invention.

[096] Figure 2 illustrates example bursts of data and burst periodicity. A burst that takes a long time to transmit (for example, takes longer than a burst periodicity to transmit) may merge with subsequent periodic transmissions to form a single contiguous burst.

[097] A data burst can occur in traffic associated with XR services. XR traffic can be transmitted in bursts. For example, an AS might send a data burst to a WTRU. The data burst might represent audio information, video information, and / or similar. After the data burst is transmitted to the WTRU, a period of time may elapse before the AS transmits another data burst to the WTRU.

[098] XR traffic can be carried over RTP / SRTP sessions or other protocols (e.g. MOQ or RTP over QUIC).

[099] Feature(s) associated with an EOB indication is / are provided in this invention.

[0100] The central network (e.g., UPF) can send an “End of Data Burst” (EOBI) indication to the RAN (e.g., NG-RAN). The RAN can use the indication to configure a WTRU power saving management scheme (e.g., DRX connected mode).

[0101] A PCF can determine a protocol description for a flow. A Petition 870250078356, dated 02 / 09 / 2025, p. 36 / 94 29 / 57 Protocol descriptions may be based on local policies or information provided by the AF. Examples of protocol descriptions may include traffic with RTP payload. For example, protocol descriptions may include traffic with versatile video encoding payload (e.g., VVC, H.265, H.266, MPEG, and / or similar).

[0102] The PCF can provision the protocol description within the PCC rules (for example, which can be sent to the SMF).

[0103] The SMF can configure the UPF to detect the last PDU of the data burst. The UPF configuration can be based on the protocol description of the PCC rules. The protocol description can indicate the type of headers and / or payloads found in the traffic. The UPF can use the protocol description to detect the end of the data burst.

[0104] If the UPF detects the end of a data burst, the UPF can provide an end-of-data-burst indication (EOBI) to the RAN. The EOBI can be sent from the UPF to the RAN in GTP-U messages.

[0105] If the RAN receives the EOBI in the GTP-U header of a message carrying a PDU, the RAN may assume that the PDU is the last PDU of a given burst of data and may put the WTRU into hibernation state.

[0106] Resource(s) associated with an RTP header extension for marking a set of PDUs is / are provided in the present invention.

[0107] An example of an RTP header extension is provided in the present invention. The header extension may include fields that can be used to derive information such as a PDU set sequence number, an indication of a final PDU in the PDU set, a PDU sequence number within a PDU set, a PDU set size (e.g., in bytes), and a PDU set importance. The header may not address how to use the information in the RTP header extension to detect Petition 870250078356, dated 02 / 09 / 2025, p. 37 / 94 30 / 57 the end of a burst of PDU sets.

[0108] Example header extensions may include fields that carry an extension element identifier, a flag indicating that the PDU is the first PDU in a set of PDUs, an end flag indicating that the PDU is the last PDU in a set of PDUs, a flag indicating that the PDU can be discarded without significant impact on the reconstructed media, a field indicating priority, a sequence number of the set of PDUs, the number of PDUs in the set of PDUs, a sequence number of the PDU and / or a size of the set of PDUs (e.g., indicating the size in bytes) of one or more (e.g., all) of the PDUs in the set of PDUs.

[0109] Resource(s) associated with the GTP-U protocol is / are provided in this invention.

[0110] G-PDU can be an example of a GTP-U message type. The user payload can be transmitted in G-PDU packets. An example of a G-PDU might be a packet that includes a GTP-U header and a user data packet (also known as a T-PDU). A G-PDU can include extension headers.

[0111] Feature(s) associated with the UPF configuration to detect the end of a burst of PDUs is / are provided in the present invention. The UPF can detect the end of a burst of PDUs using techniques that may depend on the application layer protocols used to encode downlink traffic (e.g., the format of the downlink traffic).

[0112] Feature(s) associated with indicating the end of a burst of PDUs for the NG-RAN in a GTP-U header is / are provided in the present invention.

[0113] To detect the end of a burst of PDUs (for example, and signal the end of a burst of PDUs), a system may consider that the PDUs may be received out of order by the UPF and / or the RAN (for example, NG-RAN).

[0114] Resource(s) associated with the RAN configuration (e.g., NG) Petition 870250078356, dated 02 / 09 / 2025, p. 38 / 94 31 / 57 RAN) to detect the end of a burst of PDUs is / are provided in the present invention.

[0115] A UPF can receive configuration information from an SMF. The UPF can use the configuration information to detect the end of a burst of PDU sets in the downlink traffic of a WTRU. The UPF can send an indication or information to the RAN so that the RAN can detect the end of a burst of PDU sets. The RAN can use the indication or information to determine whether the WTRU should be placed in hibernation state or in low power state (e.g., saving WTRU power and increasing WTRU battery life).

[0116] Figure 3 illustrates an example of a UPF detecting an EOB.

[0117] Feature(s) associated with the configuration and behavior of the UPF is / are provided in this invention.

[0118] Feature(s) associated with configuring a UPF to detect the end of a burst is / are provided in the present invention. The configuration information can be sent to the UPF via the SMF (e.g., via the N4 interface).

[0119] Burst identification information (BII) (also sometimes referred to as burst information in the present invention) may include a set of IE(s). The set of IE(s) may be used to identify / manipulate bursts and burst transitions. Different BIIs may be used to customize EOB detection depending on the context (e.g., as the media transport protocol, media type, and / or application). BIIs may be associated with an SDF (e.g., in a PCC rule including a traffic filter that identifies the flow) or a QoS flow. BIIs may include one or more of the following: one or more trigger IE IDs and associated burst start and / or end values; a protocol ID; a burst periodicity; a burst size (e.g., sum of PDU sizes in bytes, or e.g., sum of payload RTP in bytes). Petition 870250078356, dated 02 / 09 / 2025, p. 39 / 94 32 / 57 etc.); and / or a time limit between PDUs in a burst (for example, which could be a maximum time between PDUs within a burst).

[0120] A trigger IE ID can include an ID that identifies an IE field in a message (e.g., media transport, protocol message, and / or similar). For example, ID=1 might identify the IE containing a presentation timestamp, and ID=2 might identify the IE containing a layer ID. A protocol ID can be used to identify the IE. For example, an RTP protocol ID and a trigger IE ID “presentation timestamp” can (e.g., together) identify the presentation timestamp IE present in the RTP protocol header. A trigger IE ID can be the ID of a virtual IE field. The virtual IE field can (e.g., depending on which media transport protocol is used) correspond to different IEs or different combinations of IEs in the media transport protocol. An example of such a trigger IE ID could be the PDU set ID.The PDU set ID can be a virtual trigger IE (for example, if no explicit PDU set ID IE is present in a PDU set).

[0121] A trigger IE can be an IE present in a PDU (e.g., a field in a header in an RTP packet). A trigger IE can be an IE present in a set of PDUs (e.g., a field in a header in an MOQ stream). Examples of trigger IEs include: a presentation timestamp; a sending timestamp; a sequence number; a marker (e.g., frame boundary marker); a payload type; a frame start indication; a frame end indication; a standalone frame indication; a drop-down frame indication; a base layer synchronization (e.g., an indicator that a frame within a layer depends only on the base temporal layer); a temporal ID (e.g., temporal layer ID); a layer ID (e.g., spatial layer ID); an index Petition 870250078356, dated 02 / 09 / 2025, page 40 / 94 33 / 57 image of temporal layer 0 (e.g., a cyclic counter that labels frames of the base layer); a PDU set ID; an end-of-PDU set indication; a PDU set sequence number; a defined PDU importance (e.g., a defined PDU importance indicator); PDU set size; a burst ID (e.g., as defined in the present invention); and / or an indication of the last PDU set in a burst of PDU sets.

[0122] The burst start value may include a tuple associated with a firing IE ID. The burst start value may include: a value type (e.g., selected from {transition to a different value, invalid value, fixed valid value, transition to a higher value}), a new PDU set indication, and / or a fixed value.

[0123] For some value types (e.g., including transitions and invalid types), the fixed value may not be used (e.g., it may be 0). The new PDU set indication may be used to indicate that a burst start may be (e.g., may only be) detected on the first PDU received for a PDU set. On some systems, the new PDU set indication may be implicit for one or more burst start values ​​(e.g., and therefore may not be required). The burst start value may be used to determine the transition between one burst and the next.

[0124] The burst end value can be defined as a tuple associated with a firing IE ID. The burst end value can include: a value type (e.g., selected from {pattern of transitions detected, number of transitions to a different value}), an indication of end of PDU set, and / or a fixed value.

[0125] For detected transition patterns, the fixed value may represent the number of consecutive observations of a pattern before using it for detection. Petition 870250078356, dated 02 / 09 / 2025, page 41 / 94 34 / 57 the end of a burst. For a detected transition pattern, the fixed value can be set to 0 (for example, thus allowing the UPF to determine an appropriate number of repetitions based on other settings or logic). For a different number of transitions, the fixed value can represent the number of transitions.

[0126] The PDU end-of-set indication can be used to indicate that an EOB can be (e.g., can be (e.g., only) detected when a set of PDUs is complete (e.g., one or more PDUs from the set have been received, or one or more PDUs from the set have been received or considered lost, e.g., after a timeout has elapsed). In some systems, the “PDU end-of-set” may be implicit for one or more burst end values ​​(e.g., and therefore may not be required). The burst end value can be used to determine when a burst is complete (e.g., that a burst has been fully received or that any missing PDU from the burst is considered lost).

[0127] Feature(s) associated with the configuration and behavior of a UPF using trigger IE IDs is / are provided in the present invention. AF can configure burst information for a given QoS and / or SDF stream. The burst information can include a burst periodicity and BII in the PCF (e.g., via NEF). The burst information can be configured in the PCF (e.g., in the PCC rule), transferred by the PCF to the SMF (e.g., in the PCC rule), and transferred by the SMF to the UPF (e.g., in an N4 message).

[0128] Figure 4 illustrates an example of a UPF configuration with burst information.

[0129] In 1a, the AF can invoke an API (e.g., Nnef_AFsessionWithQoS) to provide burst information to the network. In 1b, the NEF Petition 870250078356, dated 02 / 09 / 2025, page 42 / 94 35 / 57 can respond to the API call.

[0130] In 2a, the NEF can invoke an API (e.g., Npcf_PolicyAuthorization) to provide burst information to the PCF. The PCF can use the burst information to construct a PCC rule. The PCC rule can include all or part of the burst information. In 1b, the PCF can respond to the API call.

[0131] In 3, the PCF can send the PCC rule to the SMF. The PCF can send the PCC rule to the SMF (for example, if the SMF invokes an API such as Npcf_SMPolicyControl). For example, the SMF can invoke Npcf_SMPolicyControl during PDU session establishment. If the PDU session has been (for example, has already been) established when the PCF creates the PCC rules, the PCF can use an Npcf_SMPolicyControl API notification operation to forward the PCC rules to the SMF. For example, the sending of the PCC rules to the SMF can be initiated by the PCF or the SMF.

[0132] In 4, the SMF can send the burst information to the UPF (for example, in an N4 message).

[0133] Resource(s) associated with the detection and use of an EOB is / are provided in the present invention.

[0134] Feature(s) associated with the initialization and steady-state of burst processing is / are provided in this invention. For example, at the beginning of a flow, the UPF can start in a burst processing initialization state and detect the start of bursts using burst start values. For example, the UPF can detect a first PDU from a set of PDUs corresponding to a transition in a firing IE. The UPF can (for example, in response to the detection of the first PDU from the set of PDUs) start a timer with burst periodicity to estimate the start of the next burst. If the UPF determines a new burst start, the UPF can compare the real-time between bursts. Petition 870250078356, dated 02 / 09 / 2025, p. 43 / 94 36 / 57 with the expected burst periodicity. If the difference is consistently within an acceptable jitter range (e.g., based on the network operator configuration), the UPF can reach a steady state of burst processing. The steady state of burst processing can indicate a match between the burst periodicity and the actual behavior of the media traffic. The UPF can then begin to detect and use EOB as described in the present invention.

[0135] A similar steady-state burst processing can be achieved by the RAN if the RAN performs EOB detection. In examples, no burst periodicity can be configured, and the UPF / RAN can use burst start detection to estimate the burst periodicity. Based on this estimate, the UPF / RAN can measure the jitter and enter the steady-state burst processing. If an error occurs during steady-state burst processing operation, the UPF can return to the initial burst processing state. For example, the UPF can interrupt EOB detection until it is able to re-enter a steady-state burst processing. Initialization and steady-state burst processing can be used to enable the EOB detection mechanisms described in the present invention.

[0136] Feature(s) associated with EOB detection in multiple streams is / are provided in the present invention. For example, multiple streams (e.g., video, audio, tactile) can compose the XR traffic sent to a WTRU. In some examples, these streams (e.g., streams) can be multiplexed. If the streams are multiplexed, a burst can be composed of a combination of the streams and can be detected and processed as described in the present invention. The multiple streams can be sent in different streams (e.g., different SDF and / or QoS streams). In this case, the EOB can be detected separately for each stream. The UPF / RAN can (e.g., determine) wait for the EOBs (e.g., Petition 870250078356, dated 02 / 09 / 2025, page 44 / 94 37 / 57 all EOBs) must be detected in each related flow (e.g., in all flows towards the same WTRU associated with PDU set-based QoS handling) before using the EOB (e.g., for the UPF, to send EOBIs to the RAN and / or for the RAN to control the WTRU's hibernation state). The UPF can send each EOBI to the RAN independently. The RAN can wait for the related EOBIs (e.g., all) to be received before using them (e.g., to control the WTRU's hibernation state).

[0137] Feature(s) associated with the use of EOB for non-XR traffic is / are provided in the present invention. If non-XR traffic is sent to the WTRU, the RAN may consider non-XR flows when deciding whether to use EOB / EOBI to control the WTRU hibernation state. For example, when determining the EOB, the RAN may wait until one or more (e.g., all) PDUs queued for the WTRUs are transmitted. The RAN may (e.g., may then) calculate a value that is the minimum PSDB on all other QoS flows for the WTRU. The RAN may calculate the time until the next start of a burst. The RAN may set the WTRU hibernation time to the time until the next start of a burst. In this case, the RAN can ensure that a new PDU can still be transmitted within the appropriate PSDB (for example, even if the new PDU is received immediately after putting the WTRU into hibernation mode).

[0138] Feature(s) associated with the use of specific header extensions to detect an EOB is / are provided in the present invention.

[0139] Feature(s) associated with EOB detection when RTP traffic uses specific header extensions is / are provided in the present invention. If EOB is detected, the UPF can trigger an indication to the RAN (e.g., NG-RAN) to indicate the EOB.

[0140] Feature(s) associated with EOB detection based on specific header extensions is / are provided in the present invention. Petition 870250078356, dated 02 / 09 / 2025, p. 45 / 94 38 / 57

[0141] As described in the present invention (and illustrated in Figure 4), the UPF can be configured by the SMF with information indicating what type of traffic (e.g., what type of header) may be present in the traffic of a flow. The UPF can use the traffic type information to detect information in the downlink traffic (e.g., the headers) and use the detected information to detect the end of data bursts.

[0142] An RTP header extension may include a flag indicating that the PDU is part of the last set of PDUs in a burst of PDU sets. The UPF can determine that the end of a burst is detected (for example, when the entire set of PDUs has been received by the UPF). The UPF can determine that the entire set of PDUs has been received if the number of bytes in the set of PDUs matches the size of the set of PDUs. The UPF can determine that the entire set of PDUs has been received if a PDU from the set of PDUs is received and the end-of-PDU flag is set in the header.

[0143] If the UPF counts the number of bytes in the set of PDUs that has been received to determine the EOB, the UPF can detect the end of the set of PDUs even if the packets are received by the UPF in a different order than the order in which the packets were sent.

[0144] If the UPF uses the end flag to detect the end of a set of PDUs, the UPF may not (i.e., may not need to) count the number of packets that have been received up to that point from the set of PDUs (i.e., therefore requiring less memory to maintain the state associated with the set of PDUs).

[0145] An RTP header extension may include the time the next set of PDUs in the service data stream is due to arrive. Based on this information and / or the BII, the UPF can determine which set of PDUs might be the last set of PDUs in a burst. The UPF can determine that the Petition 870250078356, dated 02 / 09 / 2025, p. 46 / 94 39 / 57 The end of a burst is detected if all PDUs from the last set of PDUs in a burst have been received by the UPF.

[0146] An end-of-burst indication can be signaled in the PDU set information header extension. A burst identifier can be signaled in the PDU set information header extension.

[0147] Figures 5 and 6 illustrate examples of syntax and semantics for the end of a data burst (e.g., 2 bits long) and / or burst ID (e.g., 8 bits long) in the PDU set information header extension. Figure 5 illustrates an example of an RTP header extension using a one-byte header format. Figure 6 illustrates an example of an RTP header extension using a two-byte header format.

[0148] The EOB flag (e.g., 2 bits long) can be set to 0x01 for the last PDU in the data burst. The EOB flag can be set to 0x00 if the current PDU is not the last PDU in the data burst. The EOB flag can be set to 0x10 if the end-of-burst indication is not shown in the PDU set information RTP header extension. The EOB flag can be set to 0x11 if the PDU is part of the last set of PDUs in the data burst.

[0149] The burst ID (e.g., 8 bits long) can have a value defined as an identifier for a burst. For example, PDUs that are intended to be sent in a single burst (e.g., that correspond to the same displayed time) can have the same burst ID.

[0150] The end of the burst in a media stream can be identified by setting the EOB field of the RTP header extension to 0x01 for the last PDU of a reference frame. Reference frames in a media stream can be larger in size. Reference frames can use (e.g., require) multiple PDUs and sets of PDUs to transmit the encoded frame data. Petition 870250078356, dated 02 / 09 / 2025, page 47 / 94 40 / 57

[0151] The end of the burst can be indicated for the last PDU of an encoded image (e.g., each encoded image) or for the last PDU of a group of encoded images (GOP). In video encoding, a GOP structure can indicate the order in which intra- and inter-encoded frames are arranged. The GOP can include a collection of successive images within an encoded video stream. An encoded video stream (e.g., each encoded video stream) can include successive GOPs, from which visible frames are generated.

[0152] The end of the burst can be indicated for PDUs (e.g., all PDUs) in the last set of PDUs of a reference frame or GOP (e.g., using the EOB field value of the RTP header extension 0x11). In this case, the UPF / RAN can detect an EOB when the UPF / RAN completely receives the PDUs from the set of PDUs (e.g., by comparing the number of bytes received for the set of PDUs with the size information element (IE) of the set of PDUs).

[0153] The burst identifier can be derived from a media timestamp (e.g., a media decoding timestamp or a media display timestamp). The burst identifier can be a subset of the bits in the timestamp (e.g., which may allow successive bursts to have a different identifier). Generating the burst identifier based on the timestamp bits may allow multiple decoders (e.g., for different media types) in the same session to obtain the same burst identifier without coordination between the decoders.

[0154] The burst identifier can be a sequence number (for example, set by the sender when starting a new standalone frame). In this case, PDUs carrying different types of media may have a different burst ID (for example, even if they carry data that will be displayed) Petition 870250078356, dated 02 / 09 / 2025, p. 48 / 94 41 / 57 simultaneously, simultaneously or at a similar time), unless the different decoders cooperate to synchronize the sequence numbers. In that case, the UPF can (for example, separately) detect the start and end of bursts for different types of streams / media.

[0155] The use of a burst identifier can allow the UPF to detect the start and end of a burst (e.g., with limited processing requirements). For example, the UPF can use a change in the burst ID to determine that one burst has merged with the next. The UPF can count sets of PDUs belonging to a burst (e.g., single) or can count the number of bytes in a burst (e.g., single). The UPF can (e.g., can then) use one of the techniques described in the present invention to detect an EOB.

[0156] Resource(s) associated with the use of existing RTP / SRTP headers, header extensions and payloads to detect an EOB is / are provided in the present invention.

[0157] Feature(s) associated with EOB detection if RTP traffic uses existing RTP / SRTP headers, header extensions and payloads is / are provided in the present invention. If an EOB is detected, the UPF can trigger an indication to the RAN (e.g., NG-RAN) to indicate the EOB.

[0158] Feature(s) associated with detecting an EOB based on timestamp changes is / are provided in this invention.

[0159] As described in the present invention (and illustrated in Figure 4), the UPF can be configured by the SMF with rules that can be used to detect information in downlink traffic (e.g., headers). The UPF can use the detected information to detect the end of data bursts.

[0160] The UPF can be configured with a unique firing IE ID RTP timestamp (e.g., unique). The firing can indicate (e.g., using an associated burst start IE) to the UPF that a new burst can be detected. Petition 870250078356, dated 02 / 09 / 2025, p. 49 / 94 42 / 57 when the RTP timestamp transitions to a higher value. The UPF can determine a pattern. For example, within a burst (e.g., between two consecutive “burst start” PDUs), the burst might include seven sets of PDUs. A set of PDUs (e.g., each set of PDUs) might include PDUs with the same RTP timestamp. To determine which pattern to look for, the UPF might use an “end of burst” IE. For example, the “end of burst” IE might describe a burst pattern based on the PDU set ID. If the UPF observes multiple consecutive occurrences of the pattern, it might enter a stable state (e.g., when the UPF expects that measured number to be stable). The UPF might remain in the stable state if (e.g., while) it continues to regularly observe the measured number.In the steady state, the UPF can report an end-of-burst on the last PDU of the last set of PDUs out of seven sets of PDUs after a burst starts, if all seven sets of PDUs are complete. The UPF can detect that a set of PDUs is complete (for example, based on one or more of the following factors: PDU set size, end-of-PDU set indication, and / or PDU sequence number within the PDU set). To allow end-of-burst detection, if some sets of PDUs are incomplete, the UPF can reset a timer (for example, using the BII burst PDU timeout) after each PDU received in a given burst and trigger a timeout if the timer expires before an end-of-burst is detected. If the UPF triggers a timeout, it can send a GTP-U message, including an end-of-burst indication, to the QoS / SDF stream.

[0161] The UPF can be configured with trigger IE IDs (e.g., including {RTP timestamp, layer ID}). If the payload matches the indicated layer (e.g., the layer ID indicates a base layer in a multi-layer media encoding scheme) and the RTP timestamp changes Petition 870250078356, dated 02 / 09 / 2025, p. 50 / 94 43 / 57 for a different value, the related burst start IE may indicate the detection of a burst start. The UPF can detect a new burst even if the video player jumps to a previous position in the stream.

[0162] Feature(s) associated with EOB detection based on an RTP timestamp on an RT is / are provided in the present invention.

[0163] Figure 7 illustrates an example of an RTP header format. An EOB can be detected if the media timestamp value changes in an RTP header (e.g., as illustrated in Figure 7). Media data belonging to a specific schedule can be sent as a burst. For example, PDUs (e.g., all PDUs) associated with a burst may have the same timestamp. If a new timestamp is detected in the RTP packet header of an RTP stream, end-of-burst notification can be signaled in the PDU set information extension of the RTP header, or the UPF can send a GTP-U message (e.g., including an end-of-burst indication). Comparing (e.g., directly comparing) RTP timestamps from different media may not be effective for end-of-burst indication.For a given type (e.g., each different type) of media, the RTP timestamp can be related to the sampling instant by pairing the RTP timestamp with a timestamp from a reference clock (e.g., a wall clock) that represents the moment when the data corresponding to the RTP timestamp was sampled. For example, to determine if two or more media streams are part of the same burst, the timestamps in an RTP packet header may not be directly compared. The timestamps in the RTP packet header can be compared to a reference clock to determine if the timestamps were transmitted at the same time.

[0164] Resource(s) associated with bit-based EOB detection Petition 870250078356, dated 02 / 09 / 2025, p. 51 / 94 A 44 / 57 marker in the RTP header is provided in this invention.

[0165] An EOB can be detected if the marker bit (M) in the RTP header is set. The marker bit can allow significant events (e.g., frame boundaries) to be marked in the RTP packet stream. If a marker bit is set, the marker bit can indicate that the frame boundary has been reached. In that case, the corresponding PDU can be marked with an end-of-burst notification in the RTP header extension, or the UPF can send a GTPU message including an end-of-burst indication.

[0166] Resource(s) associated with the detection of an EOB based on traffic patterns are provided in the present invention.

[0167] If EOB is detected upon receipt of a PDU by the UPF, the UPF may transmit the PDU to the RAN with an EOB indication defined in the GTP-U header that encapsulates the PDU sent to the RAN. If EOB is detected after a timeout by the UPF, the UPF may send a pseudo PDU (e.g., a size 0 PDU associated with the QoS / SDF flow) to the RAN. The pseudo PDU may be associated with an EOB indication defined in the GTP-U header.

[0168] Feature(s) associated with the detection of an EOB based on the timeout between PDUs are provided in the present invention.

[0169] EOB detection can be based on a timeout between PDUs (e.g., based on a configuration that includes a BII with a burst (IE) timeout between PDUs). The UPF can (e.g., initially) detect a burst start using burst start values. If a burst start is detected, the UPF can start (e.g., initialize) a timer for the PDU timeout and reset the timer value each time a PDU from that service data stream is received. If the timer expires, the UPF can determine that the end of a burst has been detected. Petition 870250078356, dated 02 / 09 / 2025, p. 52 / 94 45 / 57 or QoS).

[0170] The UPF can determine that a set of PDUs is the last set of PDUs in a burst (for example, in a case where there is a single set of PDUs per burst or when the number of sets of PDUs per burst is known / learned by the UPF). For example, the UPF can determine that a PDU is the last PDU in the set of PDUs by comparing the number of bytes received in the set of PDUs with the IE value of the size of the set of PDUs. In this case, the UPF may not (e.g., may not need to) wait for a timeout and may send an empty GTP-U packet, including an EOBI. The UPF may signal an EOBI in the GTP-U packet that the UPF sends to the RAN. The EOBI may indicate the last PDU received from the set of PDUs.

[0171] Feature(s) associated with detecting an EOB based on a number of PDU sets or a burst size are provided in the present invention.

[0172] Feature(s) associated with detecting an EOB based on counting PDU sets in a burst is / are provided in the present invention. For example, the EOB can be detected based on a configuration that includes a BII with a trigger IE “PDU Set ID” associated with an end-of-burst IE with “number of transitions to a different value” and a fixed value indicating the number of PDU set ID transitions. The UPF can learn the number of PDU sets in a burst (e.g., during the initialization state of burst processing) by analyzing the traffic (e.g., instead of obtaining a fixed number of PDU sets from the BII).

[0173] If a burst start is detected, the UPF may count the PDU sets after the burst starts. If the number of completed received PDU sets matches the configured / learned number of PDU sets per burst, the UPF may determine that the end of a burst has been detected. The UPF may determine that a PDU set is complete if all PDUs in the set are Petition 870250078356, dated 02 / 09 / 2025, p. 53 / 94 46 / 57 received, or if all PDUs in the set are received or considered lost (for example, after a timeout has elapsed).

[0174] The UPF can count the received bytes and compare the number of received bytes with the burst size configured in the BII. The UPF can detect the EOB if the received size (e.g., the number of received bytes) reaches the configured burst size and if no other burst start has been determined in the interim.

[0175] Feature(s) associated with detecting an EOB based on other traffic patterns is / are provided in the present invention.

[0176] An EOB can be detected based on traffic patterns (e.g., based on a configuration that includes BII with a trigger IE “PDU Set ID” associated with an end-of-burst IE with “transition pattern detected”). UPF can detect a burst start using burst start values. For example, UPF can measure jitter in successive burst starts. UPF can use trigger IE IDs to identify patterns in a burst. If a pattern is repeated n consecutive times (e.g., where n is a value based on the protocol ID, configuration, or internal algorithm), UPF can use that pattern to detect the end of the burst.

[0177] Resource(s) associated with indicating an EOB for the RAN (e.g., NG-RAN) is / are provided in this invention.

[0178] The UPF can indicate (for example, to NG-RAN) that the end of a burst has been detected. The indication can be sent in a GTP-U message. The RAN (e.g., NG-RAN) can use this indication to put the WTRU into a hibernation state (e.g., low power consumption). Figure 8 illustrates an example of the UPF indicating a detected EOB.

[0179] In Figure 8, in 1, the AS can transmit DL PDUs to a WTRU. DL PDUs can enter the 5G system at the UPF. DL PDUs can be received at Petition 870250078356, dated 02 / 09 / 2025, p. 54 / 94 47 / 57 a different order from that in which they were transmitted by AS.

[0180] In 2, the UPF can use configuration information (e.g., the burst information that has been received, as illustrated in Figure 4) to detect the end of the bursts defined by the PDU. The UPF can send end-of-burst information to the RAN. The features associated with sending EOB information to the RAN are described in the present invention.

[0181] In 3, the RAN can use the EOB information to determine if and / or when to put the WTRU into a hibernation state (e.g., low power consumption) (e.g., by configuring a WTRU power saving management scheme, such as DRX connected mode).

[0182] The EOB indication can be sent to the RAN in a GTP-U G-PDU message. The G-PDU packet header extension can include an EOBI. The UPF can determine whether and / or when to include the EOBI.

[0183] The UPF may receive (for example, after the UPF sends the EOBI to the NG-RAN) another PDU that is part of the same burst set of PDUs associated with the EOBI. For example, the UPF may receive another PDU from the same burst set of PDUs if the packets (e.g., PDUs) are received by the UPF in an order that may be different from the order in which they were transmitted by the AS. To decrease the likelihood of the EOBI triggering the RAN to put the WTRU into hibernation before additional burst PDU(s) are received, the UPF may send a timeout to the RAN with the EOBI. The timeout may be included in the header extension. The timeout may be an indication to the RAN that the end of a burst cannot be assumed until the timeout has expired and the EOBI has been received.

[0184] The UPF can be configured with the delay time by the SMF (for example, as illustrated in Figure 4) or the UPF can determine the delay time based on the content of the burst identification information (by Petition 870250078356, dated 02 / 09 / 2025, page 55 / 94 48 / 57 example, the protocol ID). The wait time can be sent to the RAN as part of a QoS profile.

[0185] If the UPF detects that it has received the first PDU of a burst, the UPF can send a GTP-U message (e.g., a new GTP-U message) to the RAN node (e.g., the NG-RAN node). The new GTP-U message can identify the burst and indicate its size. The RAN can (e.g., can then) use this information to detect the end of the burst. For example, the RAN can determine that the burst has ended if the amount of data received matches the indicated burst size. The burst can be identified by a QoS flow identifier. Identifying the burst with a QoS flow identifier can be used if the QoS flow is not expected to carry data not associated with the burst until it ends (e.g., during burst transmission, the QoS flow is expected to carry only data associated with the burst). The burst can be identified by one or more PDU set identifiers.One or more PDU set identifiers may include an indication to the RAN that the data that is part of the identified PDU sets (e.g., only the data that is part of the identified PDU sets) is part of the burst. The burst may be identified with one or more PDU set identifiers if the QoS flow must carry data (e.g., also carry data) that is not associated with the burst.

[0186] The new GTP-U message can indicate a time value for the RAN to use to set a timer. The RAN can determine (e.g., assume) that the burst ends when the timer expires. For example, if the timer expires, the RAN may determine (e.g., assume) that the burst ends even if the amount of data received does not match the indicated size. The UPF can be triggered to send the new GTP-U message when the UPF receives the first PDU of a burst. However, the first PDU detected by the UPF may Petition 870250078356, dated 02 / 09 / 2025, p. 56 / 94 49 / 57 may not be the first PDU transmitted by the AS (for example, because packets may not be received in the same order in which they were sent). The UPF can send the new GTP-U message to the RAN to indicate the start of a burst and provide information about the burst (for example, so that the NG-RAN can detect the end of the burst). This technique can be more accurate than some other techniques (for example, compared to an approach where the UPF detects the end of a data burst by checking for an indication in the application traffic header). For example, this technique can be more accurate because burst PDUs can be received even after the UPF detects an indication (for example, in the application layer header) that the burst has ended (for example, because packets may be received in a different order than they were transmitted).

[0187] Feature(s) associated with RAN-based EOB detection is / are provided in the present invention.

[0188] Feature(s) associated with the configuration and behavior of the RAN is / are provided in the present invention.

[0189] The RAN can be configured to detect the end of a burst. The configuration information can be sent to the RAN via the SMF (e.g., in a QoS profile IE).

[0190] A QoS profile can include an IE BII.

[0191] The BII sent to RAN may include trigger IE IDs. Trigger IE IDs may identify IEs present in GTP-U messages that encapsulate a PDU. For example, trigger IE IDs may identify PDU set IEs, such as a PDU set ID, a PDU set size, a PDU set start indication, a PDU set end indication, a PDU set importance, a PDU sequence number within the set, a PSII, PDU set dependency information, size of Petition 870250078356, dated 02 / 09 / 2025, p. 57 / 94 50 / 57 burst, burst duration and / or an EOBI.

[0192] A burst start can be identified (for example, in BII) as the first PDU received from a set of PDUs (for example, any independent set of PDUs that is marked as not dependent on any other set of PDUs for decoding).

[0193] A burst start can be identified (e.g., in BII) if the RAN receives more than N PDUs in sequence or in short succession (e.g., separated by a time shorter than the configured burst PDU timeout). The value of N can be configured (e.g., in a burst start value in BII).

[0194] A burst end can be identified (for example, in BII) if a timeout occurs between PDUs.

[0195] A burst end can be identified (e.g., in BII) if N sets of PDUs are completely received (e.g., with all PDUs being received or determined as lost, e.g., based on a timeout). The value of N can be configured (e.g., in a burst start value in BII).

[0196] A burst end can be identified (e.g., in the BII) if a PDU is received from the UPF with the EOBI set (e.g., in a GTPU header). More than one EOB detection technique (e.g., RAN-based and UPF-based EOB detection) can be active simultaneously. In this case, the BII used to configure the RAN can describe two burst ends (e.g., one burst end to detect EOB using EOBI and another burst end to detect EOB using another technique, as described in the present invention).

[0197] A sample BII may include information that identifies the start of a burst using a timestamp change. A sample BII may include information that identifies the end of a burst (e.g., using a Petition 870250078356, dated 02 / 09 / 2025, p. 58 / 94 51 / 57 timeout-based technique between PDUs or in a firing IE). The UPF can obtain the timestamp (or a value derived from the timestamp, for example, a subset of the bits used to encode the timestamp) to use the timestamp-based technique, and the UPF can provide the timestamp to the RAN (for example, in a GTP-U header field).

[0198] The UPF or RAN can identify an EOB if the size of the received PDUs reaches the expected size of a burst (for example, as configured in BII and / or sent by the UPF to the RAN as described in the present invention, for example, using a GTP-U message containing the burst size).

[0199] Resource(s) associated with the detection of an EOB by the RAN based on a traffic pattern is / are provided in the present invention.

[0200] Feature(s) described in the present invention related to EOB detection based on UPF (e.g., using a timeout between PDUs, a number of PDU sets, and other traffic patterns) can be similarly performed by the RAN (e.g., based on the configured BII). The RAN can use the indication or information to help determine whether and / or when to put the WTRU into a hibernation (low power) state (e.g., saving WTRU power and increasing WTRU battery life).

[0201] This disclosure describes devices and methods for detecting and indicating the end of a burst by a user plane function (e.g., by a network node).

[0202] The network node can receive configuration information to detect the end of a burst of packet data unit (PDU) sets. The network node can receive the burst of PDU sets. The network node can detect, with Petition 870250078356, dated 02 / 09 / 2025, page 59 / 94 52 / 57 based on configuration information, the end of the PDU cluster burst. The network node can send an indication to a base station indicating the detected end of the PDU cluster burst.

[0203] The configuration information may include an IE indicating a time value for when a burst of PDU sets can be received. Detecting the end of the burst of PDU sets may involve determining a number of PDU sets using the time value. The network node may determine a PDU pattern using the number of PDU sets. The network node may determine the end of the burst of PDU sets using the PDU pattern. The number of PDU sets may be associated with the burst of PDU sets. The time value may include a timestamp value.

[0204] Detecting the end of a PDU set burst may involve determining a first timestamp associated with a first PDU set and the PDU set burst, determining a second timestamp associated with a second PDU set, and determining the end of the PDU set burst using the first timestamp and the second timestamp. The second timestamp may be different from the first timestamp. The PDU set burst may include the first PDU set.

[0205] Detecting the end of a burst of PDU sets may involve identifying (e.g., determining) a message header (e.g., from a PDU in the burst) that indicates the end of the burst of PDU sets, and determining the end of the burst of PDU sets using the message header. The network node can determine that the PDU satisfies the EOB condition based on the indication in the message header. The indication can be sent to the base station when the end of the burst of PDU sets is determined using the message header.

[0206] Detecting the end of a burst of PDU sets may involve determining that a set of PDUs was received during an initial duration of Petition 870250078356, dated 02 / 09 / 2025, p. 60 / 94 53 / 57 time. The network node can determine a second time duration based on the determination that the set of PDUs was received during the first time duration. The network node can determine the end of the burst of PDU sets when the second time duration has elapsed. The burst of PDU sets can include the set of PDUs.

[0207] Detecting the end of a burst of PDU sets may involve determining a number of PDU sets associated with the burst of PDU sets. The network node may determine a PDU set using the determined number of PDU sets. The network node may determine an expected byte size value for the determined PDU set. The network node may determine a received byte size value that indicates a calculated byte size of the determined PDU set. The network node may determine the end of the burst of PDU sets when the received byte size value is similar to the expected byte size value.

[0208] Detecting the end of the PDU set burst may involve determining an expected byte size value for the PDU set burst. The network node can determine a received byte size value using the PDU set burst. The network node can determine the end of the PDU set burst when the received byte size value is within an acceptable range of (e.g., similar to) the expected byte size value.

[0209] Detecting the end of a PDU set burst may involve determining the number of PDU sets associated with the PDU set burst. The network node may determine an expected byte size value from the number of PDU sets. The network node may determine a received byte size value using the number of PDU sets. The network node may determine the end of the PDU set burst when the received byte size value is within an acceptable range of (e.g., similar to) Petition 870250078356, dated 02 / 09 / 2025, pp. 61 / 94 54 / 57 is the expected value for the byte size.

[0210] The configuration information may include an information element (IE) indicating a PDU set identifier (ID). Detecting the end of the PDU set burst may involve determining a PDU pattern using the PDU set identifier. The network node may determine a number of PDU sets associated with the PDU set burst using the PDU pattern. The network node may determine the end of the PDU set burst using the determined number of PDU sets.

[0211] This disclosure describes devices and methods for detecting and indicating the end of a burst over a radio access network (e.g., by a base station).

[0212] The base station can receive configuration information to detect the end of a burst of packet data unit (PDU) sets. The base station can receive the burst of PDU sets. The base station can detect, based on the configuration information, the end of the burst of PDU sets. The base station can send, based on the detection of the end of the burst of PDU sets, a message to change the configuration of a device (for example, a wireless transmit / receive unit (WTRU)). The device configuration can indicate a time for the device to enter hibernation mode. The base station can determine that the burst of PDUs is associated with extended reality (XR) traffic.

[0213] The configuration information may include an information element (IE) indicating the start of a burst of PDU sets (for example, a time value associated with the start of the burst of PDU sets may be received). The network node may determine a number of PDU sets in the burst of PDU sets based on the start of the burst. For example, detecting the end of the burst of PDU sets may involve determining, using the time value, a Petition 870250078356, dated 02 / 09 / 2025, pp. 62 / 94 55 / 57 is the number of PDU sets associated with the PDU set burst. The network node can determine a burst pattern using the number of PDU sets in the PDU set burst. The network node can determine the end of the PDU set burst using the PDU pattern. For example, the network node can determine that the PDU satisfies the condition based on the burst pattern. The time value can include a timestamp value.

[0214] Detecting the EOB of PDU sets may involve determining a first timestamp associated with a first PDU set in the burst of PDU sets. The network node may determine a second timestamp associated with a second PDU set in the burst of PDU sets. The network node may determine the EOB of the PDU sets using the first timestamp and the second timestamp. For example, the network node may determine that the PDU satisfies the condition based on the second timestamp being different from the first timestamp. The second timestamp may be different from the first timestamp. The burst of PDU sets may include the first PDU set.

[0215] Detecting the end of a burst of PDU sets may involve determining that a set of PDUs (e.g., in a burst of PDU sets) was received during a first time duration. The network node may determine a second time duration based on the determination that the set of PDUs was received during the first time duration. The network node may determine that the PDU satisfies the condition (e.g., it may detect the end of the burst of PDU sets) if the second time duration has elapsed. The burst of PDU sets may include the set of PDUs.

[0216] Detecting the end of a burst of PDU sets may involve determining a number of PDU sets associated with the burst of PDU sets. The network node can determine a set of PDUs using the determined number of Petition 870250078356, dated 02 / 09 / 2025, p. 63 / 94 56 / 57 sets of PDUs. The network node can determine an expected byte size value for the determined set of PDUs. The network node can determine a received byte size value that indicates a calculated byte size for the determined set of PDUs. The network node can determine the end of the burst of PDU sets if / when the received byte size value is within an acceptable range of (e.g., similar to) the expected byte size value.

[0217] Detecting the end of a PDU set burst may involve determining an expected byte size value for the PDU set burst. The network node can determine a received byte size value using the PDU set burst. The network node can determine the end of the PDU set burst if / when the received byte size value is within an acceptable range of (e.g., similar to) the expected byte size value. Detecting the end of a PDU set burst may involve determining the number of PDU sets associated with the PDU set burst. The network node can determine an expected byte size value from the number of PDU sets. The network node can determine a received byte size value using the number of PDU sets.The network node can determine the end of the burst of PDU sets if / when the received byte size value is within an acceptable range of (e.g., similar to) the expected byte size value.

[0218] The configuration information may include an information element (IE) indicating a PDU set identifier (ID). Detecting the end of the PDU set burst may involve determining a PDU pattern using the PDU set identifier. The network node may determine, using the PDU pattern, a number of PDU sets associated with the PDU set burst. The network node may determine the end of the PDU set burst using the determined number of PDU sets. Petition 870250078356, dated 02 / 09 / 2025, pages 64 / 94 57 / 57

[0219] 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 modalities, or in various combinations with or without other resources and elements.

[0220] Although the implementations described in the present invention may consider specific 3GPP protocols, it is understood that the implementations described in the present invention are not limited to this scenario and may be applicable to other wireless systems. For example, although the solutions described in the present invention consider specific LTE, LTE-A, New Radio (NR) or 5G protocols, it is understood that the solutions described in the present invention are not limited to this scenario and are also applicable to other wireless systems.

[0221] 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), registers, cache memory, semiconductor memory devices, magnetic media such as, but are not limited to, internal and removable hard disks, magneto-optical media, and / or optical media such as compact discs (CD-ROMs) and / or digital versatile discs (DVDs). A processor, in association 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 870250078356, dated 02 / 09 / 2025, p. 65 / 94

Claims

1 / 8 CLAIMS 1. Network node, the network node CHARACTERIZED in that it comprises: a processor configured to: receive configuration information comprising a request for the network node to detect the end of a burst of packet data unit (PDU) sets; receive the burst of PDU sets, wherein the burst of PDU sets comprises one PDU; in response to receiving the request, detect the end of the burst of PDU sets; and send, to a base station, an indication of the end of the burst of PDU sets, wherein the indication of the end of the burst of PDU sets is sent in an extension header of a GTP-U packet associated with the PDU.

2. Network node, according to claim 1, CHARACTERIZED in that the burst of PDU sets is a first burst of PDU sets, the configuration information further comprises an information element (IE) indicating the start of a second burst of PDU sets, the processor is further configured to receive the second burst of PDU sets, and the processor being configured to detect the end of the first burst of PDU sets comprises the processor being configured to: determine, based on the start of the second burst of PDU sets, a number of PDU sets in the second burst of PDU sets; determine a burst pattern based on the number of PDU sets in the second burst of PDU sets; and determine that the PDU satisfies a condition based on the burst pattern.

3. Network node, according to claim 1, CHARACTERIZED in that the processor being configured to detect the end of the burst of PDU sets comprises the processor being configured to: determine a first timestamp associated with a first PDU set in the burst of PDU sets; determine a second timestamp associated with a second PDU set, wherein the second timestamp is different from the first timestamp; and determine that the PDU satisfies a condition based on the second timestamp being different from the first timestamp.

4. Network node, according to claim 1, CHARACTERIZED in that the processor being configured to detect the end of the burst of PDU sets comprises the processor being configured to: identify a message header of a PDU in the burst of PDU sets, wherein the message header indicates the end of the burst of PDU sets; and determine that the PDU satisfies a condition based on the indication in the message header.

5. Network node, according to claim 1, CHARACTERIZED in that the processor being configured to detect the end of the burst of PDU sets comprises the processor being configured to: Determine that a set of PDUs was received during a first time duration, wherein the burst of PDU sets comprises the set of PDUs; determine a second time duration based on the determination that the set of PDUs was received during the first time duration; and on a condition that the second time duration has elapsed, determine that the PDU satisfies the condition.

6. Network node, according to claim 1, CHARACTERIZED by the fact Petition 870250078356, dated 02 / 09 / 2025, page 88 / 94 3 / 8 that the processor being configured to detect the end of the burst of PDU sets comprises the processor being configured to: determine a number of PDU sets, wherein the number of PDU sets is associated with the burst of PDU sets; determine a PDU set based on the determined number of PDU sets; determine the expected byte size value of the determined PDU set; determine a received byte size value, wherein the received byte size value indicates a calculated byte size of the determined PDU set; and on a condition that the received byte size value is within an acceptable range of the expected byte size value, determine that the PDU satisfies the condition.

7. Network node, according to claim 1, CHARACTERIZED in that the processor being configured to detect the end of the burst of PDU sets comprises the processor being configured to: determine an expected byte size value of the burst of PDU sets; determine a received byte size value based on the burst of PDU sets; and on a condition that the received byte size value is within an acceptable range of the expected byte size value, determine that the PDU satisfies the condition.

8. Network node, according to claim 1, CHARACTERIZED in that the processor being configured to detect the end of the burst of PDU sets comprises the processor being configured to: Petition 870250078356, dated 02 / 09 / 2025, page 89 / 94 4 / 8 determine a number of PDU sets that are associated with the burst of PDU sets; determine an expected byte size value of the number of PDU sets; determine a received byte size value based on the number of PDU sets; and on a condition that the received byte size value is within an acceptable range of the expected byte size value, determine that the PDU satisfies the condition.

9. Network node, according to claim 1, CHARACTERIZED in that the configuration information additionally comprises an information element (IE) indicating a PDU set identifier (ID), and wherein the processor being configured to detect the end of the burst of PDU sets comprises the processor being configured to: determine a burst pattern based on the PDU set identifier; determine a number of PDU sets based on the burst pattern, wherein the number of PDU sets is associated with the burst of PDU sets; and determine that the PDU satisfies a condition based on the determined number of PDU sets.

10. Network node, according to claim 1, CHARACTERIZED in that the extension header of the GTP-U packet associated with the PDU additionally comprises a timeout, and in that the timeout is associated with the indication of the end of the burst of PDU sets.

11. Method, to be performed by a network node, the method CHARACTERIZED by the fact that it comprises: receiving configuration information comprising a request for Petition 870250078356, dated 02 / 09 / 2025, page 90 / 94 5 / 8 the network node to detect the end of a burst of packet data unit sets (PDU); receiving the burst of PDU sets, wherein the burst of PDU sets comprises a PDU; in response to receiving the request, detecting the end of the burst of PDU sets; and sending, to a base station, an indication of the end of the burst of PDU sets, wherein the indication of the end of the burst of PDU sets is sent in an extension header of a GTP-U packet associated with the PDU.

12. A method according to claim 11, characterized in that the burst of PDU sets is a first burst of PDU sets, the configuration information further comprises an information element (IE) indicating the start of a second burst of PDU sets, the method further comprises receiving the second burst of PDU sets, and detecting the end of the first burst of PDU sets comprises: determining, based on the start of the second burst of PDU sets, a number of PDU sets in the second burst of PDU sets; determining a burst pattern based on the number of PDU sets in the second burst of PDU sets; and determining that the PDU satisfies a condition based on the burst pattern.

13. Method according to claim 11, CHARACTERIZED in that detecting the end of the burst of PDU sets comprises: determining a first timestamp associated with a first PDU set in the burst of PDU sets; determining a second timestamp associated with a second PDU set, wherein the second timestamp is different from the first timestamp; and Petition 870250078356, dated 02 / 09 / 2025, pp. 91 / 94 6 / 8 determining that the PDU satisfies a condition based on the second timestamp being different from the first timestamp.

14. A method according to claim 11, characterized in that detecting the end of a burst of PDU sets comprises: identifying a message header of a PDU in the burst of PDU sets, wherein the message header indicates the end of the burst of PDU sets; and determining that the PDU satisfies a condition based on the indication in the message header.

15. Method according to claim 11, CHARACTERIZED in that detecting the end of a burst of PDU sets comprises: determining that a set of PDUs was received during a first time duration, wherein the burst of PDU sets comprises the set of PDUs; determining a second time duration based on the determination that the set of PDUs was received during the first time duration; and on a condition that the second time duration has elapsed, determining that the PDU satisfies the condition.

16. Method according to claim 11, CHARACTERIZED in that detecting the end of the burst of PDU sets comprises: determining a number of PDU sets, wherein the number of PDU sets is associated with the burst of PDU sets; determining a PDU set based on the determined number of PDU sets; determining the expected byte size value of the determined PDU set; determining a received byte size value, wherein the received byte size value indicates a calculated byte size of the determined PDU set; and on a condition that the received byte size value is within an acceptable range of the expected byte size value, determining that the PDU satisfies the condition.

17. A method according to claim 11, characterized in that detecting the end of a burst of PDU sets comprises: determining an expected byte size value of the burst of PDU sets; determining a received byte size value based on the burst of PDU sets; and, on a condition that the received byte size value is within an acceptable range of the expected byte size value, determining that the PDU satisfies the condition.

18. A method according to claim 11, characterized in that detecting the end of a burst of PDU sets comprises: determining a number of PDU sets that are associated with the burst of PDU sets; determining an expected byte size value of the number of PDU sets; determining a received byte size value based on the number of PDU sets; and, on a condition that the received byte size value is within an acceptable range of the expected byte size value, determining that the PDU satisfies the condition.

19. Method according to claim 11, CHARACTERIZED in that the configuration information additionally comprises an information element (IE) indicating a PDU set identifier (ID), and wherein detecting the end of the PDU set burst comprises: determining a burst pattern based on the PDU set identifier; determining a number of PDU sets based on the burst pattern, wherein the number of PDU sets is associated with the PDU set burst; and determining that the PDU satisfies a condition based on the determined number of PDU sets.

20. Method according to claim 11, CHARACTERIZED in that the extension header of the GTP-U packet associated with the PDU additionally comprises a timeout, and in that the timeout is associated with the indication of the end of the burst of PDU sets. Petition 870250078356, dated 02 / 09 / 2025, p. 94 / 94

Images