Detection and indication of end of bursts by a user plane function

Abstract

A method, performed by a network node. The network node may receive configuration information that indicates a condition indicative of an end of a burst of packet data unit (PDU) sets. The network node may receive the burst of PDU sets. The burst of PDU sets may include a PDU. The network node may detect, based on the PDU satisfying the condition, the end of the burst of PDU sets. The network node may send, to a base station, an indication of the detected end of the burst of PDU sets.

Description

DETECTION AND INDICATION OF END OF BURSTS BY A USER PLANE FUNCTION CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No.63 / 454,209, filed March 23, 2023, the contents of which are hereby incorporated by reference herein. BACKGROUND

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

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

[0004] The network node may receive configuration information that indicates a condition indicative of an end of a burst of packet data unit (PDU) sets. The network node may receive the burst of PDU sets, wherein the burst of PDU sets comprises a PDU. The network node may detect, based on the PDU satisfying the condition, the end of the burst of PDU sets. The network node may send, to a base station, an indication of the end of the burst of PDU sets.

[0005] The configuration information may include an information element (IE) indicating a 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 start of the second burst of PDU sets, a number of PDU sets in the second burst of PDU sets. The network node may determine a burst pattern based on the number of PDU sets in the second burst of PDU sets. The network node may determine that the PDU satisfies the condition based on the burst pattern.

[0006] The network node may determine 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. The second timestamp may be different from the first timestamp. The network node may determine that the PDU satisfies the condition based on the second timestamp being different from the first timestamp.

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

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

[0009] The network node may determine a number of PDU sets in the burst of PDU sets. The network node may determine a PDU set based on the determined number of PDU sets. The network node may determine the expected byte size value of the determined PDU set. The network node may determine a received byte size value. The received byte size value may indicate a calculated byte size of the determined PDU set. The network node may, on a condition that the received byte size value is within an acceptable range from the expected byte size value, determine that the PDU satisfies the condition.

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

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

[0012] 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 burst of PDU sets. The network node may determine that the PDU satisfies the condition based on the determined number of PDU sets. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0017] FIG.2 illustrates example data bursts and burst periodicity.

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

[0019] FIG.4 illustrates an example of configuring the UPF with burst information.

[0020] FIG.5 illustrates an example RTP header extension using a one-byte header format.

[0021] FIG.6 illustrates an example RTP header extension using a two-byte header format.

[0022] FIG.7 illustrates an example RTP header format.

[0023] FIG.8 illustrates an example of a UPF indicating a detected end of burst. DETAILED DESCRIPTION

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

[0025] As shown in FIG.1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, alaptop, 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, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0026] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0027] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

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

[0029] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA,SC-FDMA, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

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

[0032] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

[0033] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, 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.

[0034] The base station 114b in FIG.1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-basedRAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG.1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

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

[0036] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

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

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

[0039] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG.1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0040] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

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

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

[0043] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display(LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0044] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

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

[0046] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0047] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

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

[0049] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

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

[0051] The CN 106 shown in FIG.1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0052] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0053] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

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

[0055] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

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

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

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

[0059] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0060] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0061] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

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

[0063] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0064] In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code.

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

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

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

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

[0069] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG.1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

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

[0071] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g.,handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0072] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet- based, and the like.

[0073] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

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

[0075] In view of Figures 1A-1D, and the corresponding description of Figures 1A-1D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b,DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0076] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may performing testing using over-the-air wireless communications.

[0077] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be testing equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0078] Reference to a timer herein may refer to a time, a time period, a tracking of time, a tracking of a period of time, a combination thereof, and / or the like. Reference to a timer expiration herein may refer to determining that the time has occurred or that the period of time has expired.

[0079] Devices and methods for detecting end of bursts are provided herein. 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 may be performed by the user plane function (UPF) or radio access network (RAN). If the UPF performs the detection, the UPF may signal an EOB indication to the RAN. The RAN may use the EOB detection and / or indication to set the WTRU in a low power state.

[0080] Feature(s) associated with UPF-based detection and indication of EOBs are provided herein. The UPF may receive configuration information for detecting the EOB of packet data unit (PDU) sets. The UPF may detect the EOB. The UPF may send an indication of the EOB to the RAN.

[0081] Feature(s) associated with RAN-based detection and usage of EOBs are provided herein. The RAN may receive configuration information for detecting the EOB of PDU sets. The RAN may detect the EOB. The RAN may control the sleep state of the WTRU based on the detection.

[0082] The following acronyms are used herein: AF Application Function AS Application Server DRX Discontinuous Reception EOB End of Burst (e.g., End of a Burst) EOBI End-of-Burst Indication GTP-U GPRS Tunnelling Protocol User Plane Protocol HE Header Extension MOQ Media over Quic Protocol NG-RAN Next-Generation Radio Access Network PCC Policy and Charging 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

[0083] The terms “server,” “application server,” and “application function” may be used interchangeably herein.

[0084] Feature(s) associated with UPF-based detection and indication of EOBs are provided herein.

[0085] A network function (e.g., the UPF) may receive configuration information for detecting the EOB of PDU sets. The configuration information may indicate a condition indicative of the EOB of the burst of PDU sets. For example, network exposure function (NEF) application programming interfaces (API) may define trigger information elements (IEs) to identify the start and / or end of burst, and / or an inter-PDU timeout within a burst.

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

[0087] The UPF may detect the EOB of the burst of PDU sets. The UPF may detect the EOB of the burst of PDU sets based on a PDU in the burst of PDUs satisfying a condition. For example, the UPF may detect the EOB of the PDU sets based on a timestamp change, specific fields in RTP / SRTP headers / extension / payload, a timeout, a number of PDU sets, a traffic pattern, and / or the like.

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

[0089] Feature(s) associated with RAN-based detection and usage of EOB are provided herein.

[0090] The RAN (e.g., NG-RAN) may receive configuration information (e.g., in a QoS profile). The RAN may use the configuration information to detect the EOB of a burst of PDU sets. For example, the configuration information may indicate a condition indicative of the EOB of the burst of PDU sets. The RAN may use the EOB to control the sleep state of a WTRU.

[0091] The RAN may receive PDUs of service data flows (SDF) corresponding to XR traffic.

[0092] The RAN may detect an EOB (e.g., of PDU sets). The RAN may not be able to see the content of headers but may be able to use timer-based approaches to detect an EOB.

[0093] The RAN may control the sleep state (e.g., low power state) of a WTRU.

[0094] Feature(s) associated with data bursts are provided herein.

[0095] A data burst may be a set of one or more PDUs generated and sent by an application in a short period of time. A data burst may be (e.g., typically) associated with a burst periodicity. The burst periodicity may be configured in the control plane for an XR flow or set of flows. A data burst may include one or multiple PDU sets. For example, a data burst may carry an application data unit such as a frame, or a group of pictures. For example, a data burst (e.g., a same data burst) may carry different PDU sets including media types corresponding to the same frame displayed to the user. The terms “data bursts,” “bursts,” and “burst transmissions” may be used interchangeably herein.

[0096] FIG.2 illustrates example data bursts and burst periodicity. A burst that takes too long to transmit (e.g., takes longer than a burst periodicity to transmit) may merge with subsequent periodic transmissions to form a single contiguous burst.

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

[0098] XR traffic may be transported over RTP / SRTP sessions or other protocols (e.g., MOQ or RTP over QUIC).

[0099] Feature(s) associated with an EOB indication are provided herein. [000100] The core network (e.g., the UPF) may send an “End of Data Burst” indication (EOBI) to the RAN (e.g., NG-RAN). The RAN may use the indication to configure a WTRU power saving management scheme (e.g., connected mode DRX). [000101] The PCF may determine a protocol description for a flow. The protocol description may be based on local policies or information provided by the AF. Examples of protocol descriptions may include traffic with an RTP payload. For example, protocol descriptions may include traffic with versatile video coding (e.g., VVC, H.265, H.266, MPEG, and / or the like) payload. [000102] The PCF may provision the protocol description within PCC rules (e.g., which may be sent to the SMF). [000103] The SMF may configure the UPF to detect the last PDU of the data burst. The UPF configuration may be based on the protocol description from the PCC rules. The protocol description may indicate the type of headers and / or payloads found in the traffic. The UPF may use the protocol description to detect the end of the data burst. [000104] If the UPF detects the end of a data burst, the UPF may provide an end of data burst indication (EOBI) to the RAN. The EOBI may be sent from the UPF to the RAN in GTP-U messaging. [000105] If the RAN receives the EOBI in the GTP-U header of a message that carries a PDU, the RAN may assume that the PDU is the last PDU of a given data burst and may put the WTRU into a sleep state. [000106] Feature(s) associated with an RTP header extension for PDU set marking are provided herein. [000107] An example of an RTP header extension is provided herein. The header extension may include fields that may be used to derive information such as a PDU set sequence number, an indication of an end PDU of the PDU set, a PDU sequence number within a PDU set, a PDU set size (e.g., in bytes), and a PDU set importance. The header may not address how to use information in the RTP header extension to detect an end of a burst of PDU sets. [000108] Example header extensions may include fields that carry an extensions element identifier, a flag that indicates that the PDU is the first PDU of a PDU set, an End Flag that indicates that the PDU is the lastPDU of a PDU set, a flag that indicates that the PDU may be discarded without significant impact to the reconstructed media, a field that indicates priority, a sequence number of the PDU set, the number of PDUs in the PDU set, a sequence number of the PDU, and / or a PDU set size (e.g., that indicates the size in bytes) of one or more (e.g., all) PDUs of the PDU set. [000109] Feature(s) associated with the GTP-U protocol are provided herein. [000110] G-PDU may be an example GTP-U message type. User payload may be transmitted in G-PDU packets. An example G-PDU may be a packet including a GTP-U header and a user data packet (also known as T-PDU). A G-PDU may include extension headers. [000111] Feature(s) associated with configuring the UPF to detect the end of a burst of PDUs are provided herein. The UPF may detect an end of a burst of PDUs using techniques that may be dependent on application layer protocol(s) used to encode the downlink traffic (e.g., the format of the downlink traffic). [000112] Feature(s) associated with indicating the end of a burst of PDUs to the NG-RAN in a GTP-U header are provided herein. [000113] To detect the end of a burst of PDUs (e.g., and signal the end of a burst of PDUs), a system may consider that PDUs may be received out of order by the UPF and / or the RAN (e.g., NG-RAN). [000114] Feature(s) associated with configuring the RAN (e.g., NG-RAN) to detect the end of a burst of PDUs are provided herein. [000115] A UPF may receive configuration information from an SMF. The UPF may use the configuration information to detect the end of a burst of PDU sets in a WTRU’s downlink traffic. The UPF may send an indication or information to the RAN so that the RAN may detect the end of a burst of PDU sets. The RAN may use the indication or information to determine whether to place the WTRU in a sleep state or a low power state (e.g., thereby saving WTRU power and increasing the battery life of the WTRU). [000116] FIG.3 illustrates an example of a UPF detecting an EOB. [000117] Feature(s) associated with configuration and UPF behavior are provided herein. [000118] Feature(s) associated with configuring a UPF to detect the end of a burst are provided herein. Configuration information may be sent to the UPF by the SMF (e.g., over the N4 interface). [000119] Burst identification information (BII) (also sometimes called burst information herein) may include a set of IE(s). The set of IE(s) may be used to identify / handle bursts and burst transitions. Different BII may be used to tailor EOB detection depending on context (e.g., such as the media transport protocol, type of media, and / or application). BII may be associated with an SDF (e.g., in a PCC rule including a traffic filter identifying the flow), or with a QoS flow. BII may include one or more of the following: one or more trigger IE IDs and associated start-of-burst values and / or end-of-burst values; a protocol ID; a burst periodicity; aburst size (e.g., sum of PDU sizes in bytes, or e.g., sum RTP of payload in bytes, etc.); and / or an in-burst inter-PDU timeout (e.g., which may be a maximum time between PDUs inside a burst). [000120] A trigger IE ID may include an ID that identifies an IE field in a message (e.g., media transport, protocol message, and / or the like). For example, ID=1 may identify the IE holding a presentation timestamp, and ID=2 may identify the IE holding a layer ID. A protocol ID may be used to identify the IE. For example, an RTP protocol ID and trigger IE ID “presentation timestamp” may (e.g., together) identify the presentation timestamp IE present in the RTP protocol header. A trigger IE ID may be the ID for a virtual IE field. The virtual IE field may (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 may be the PDU set ID. The PDU set ID may be a virtual trigger IE (e.g., if no explicit PDU set ID IE is present in a PDU set). [000121] A trigger IE may be an IE present in a PDU (e.g., a field in a header in an RTP packet). A trigger IE may be an IE present in a PDU set (e.g., a field in a header in a MOQ stream). Examples of trigger IEs include: a presentation timestamp; a sending timestamp; a sequence number; a marker (e.g., frame boundaries marker); a payload type; a start-of-frame indication; an end-of-frame indication; an independent frame indication; a discardable frame indication; a base layer sync (e.g., an indicator that a frame within a layer only depends on the base temporal layer); a temporal ID (e.g., temporal layer ID); a layer ID (e.g., a spatial layer ID); a temporal layer 0 picture index (e.g., a cyclic counter labeling base layer frames); a PDU set ID; an end of PDU set indication; a PDU set sequence number; a PDU set importance (e.g., a PDU set importance indicator); PDU set size; a burst ID (e.g., as defined herein); and / or a last PDU set of a burst of PDU sets indication. [000122] The start-of-burst value may include a tuple associated with a trigger IE ID. The start-of-burst value may include: a value type (e.g., selected from among {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. [000123] For some value types (e.g., including transitions and invalid types), the fixed value may not be used (e.g., may be 0). The new PDU set indication may be used to indicate that a start-of-burst may be (e.g., may only be) detected on the first PDU received for a PDU set. In some systems, the new PDU set indication may be implicit for one or more start-of-burst values (e.g., and therefore may not be needed). The start-of-burst value may be used to determine the transition between a burst and the next burst. [000124] The end-of-burst value may be defined as a tuple associated with a trigger IE ID. The end-of- burst value may include: a value type (e.g., selected from among {detected pattern of transitions, number of transitions to a different value}), an end of PDU set indication, and / or a fixed value.[000125] For detected patterns of transitions, the fixed value may represent the number of consecutive observations of a pattern before using the pattern to detect end-of-burst. For a detected pattern of transitions, the fixed value may be set to 0 (e.g., thereby allowing the UPF to determine a suitable number of repetitions based on other configurations or logic). For a number of transitions to a different value, the fixed value may represent the number of transitions. [000126] The end of PDU set indication may be used to indicate that an EOB may be (e.g., may a (e.g., only) be) detected when a PDU set is completed (e.g., one or more PDUs of the set were received, or one or more PDUs of the set are either received or are considered lost, for example, after a timeout elapsed). In some systems, “end of PDU set” may be implicit for one or more end-of-burst values (e.g., and therefore may not be needed). The end-of-burst value may be used to determine when a burst is complete (e.g., that a burst was entirely received, or that any missing PDU from the burst is determined to be lost). [000127] Feature(s) associated with the configuration and behavior of a UPF using trigger IEs IDs are provided herein. The AF may configure burst information for a given QoS flow and / or SDF. The burst information may include a burst periodicity and BII in the PCF (e.g., through the NEF). Burst information may 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). [000128] FIG.4 illustrates an example of configuring the UPF with burst information. [000129] At 1a, the AF may invoke an API (e.g., Nnef_AFsessionWithQoS) to provide the network with burst information. At 1b, the NEF may respond to the API call. [000130] At 2a, the NEF may invoke an API (e.g., Npcf_PolicyAuthorization) to provide the burst information to the PCF. The PCF may use the burst information to construct a PCC rule. The PCC rule may include all or part of the burst information. At 1b, the PCF may respond to the API call. [000131] At 3, the PCF may send the PCC rule to the SMF. The PCF may send the PCC rule to the SMF (e.g., if the SMF invokes an API such as Npcf_SMPolicyControl). For example, the SMF may invoke Npcf_SMPolicyControl during PDU session establishment. If the PDU session has been (e.g., already been) established when the PCF creates the PCC rules, the PCF may use a notify operation of the Npcf_SMPolicyControl API to forward the PCC rules to the SMF. For example, sending the PCC rules to the SMF may be initiated by the PCF or the SMF. [000132] At 4, the SMF may send the burst information to the UPF (e.g., in an N4 message). [000133] Feature(s) associated with detecting and using an EOB are provided herein. [000134] Feature(s) associated with burst processing initialization and steady state are provided herein. For example, at the start of a flow, the UPF may start in a burst processing initialization state and detect thestart of bursts using start-of-burst values. For example, the UPF may detect a first PDU of a PDU set corresponding to a transition in a trigger IE. The UPF may (e.g., in response to detecting the first PDU of the PDU set) start a timer with burst periodicity to estimate the start of the next burst. If the UPF determines a new burst start, the UPF may compare the actual inter-burst time with the expected burst periodicity. If the difference is consistently within an acceptable jitter range (e.g., based on network operator configuration), the UPF may reach a burst processing steady state. The burst processing steady state may indicate a match between the burst periodicity and the actual behavior of the media traffic. The UPF may start detecting and using EOB as described herein. [000135] A similar burst processing steady state may be reached by the RAN if the RAN performs EOB detection. In examples, no burst periodicity may be configured, and UPF / RAN may use start-of-burst detection to estimate the burst periodicity. Based on this estimation, the UPF / RAN may measure jitter and enter the burst processing steady state. If an error occurs during the burst processing steady state operation, the UPF may transition back to the burst processing initialization state. For example, the UPF may stop EOB detection until the UPF is able to reenter a burst processing steady state. Burst processing initialization and steady state may be used to enable EOB detection mechanisms described herein. [000136] Feature(s) associated with detecting EOB on multiple streams are provided herein. For example, multiple streams (e.g., video, audio, haptics) may compose XR traffic sent to a WTRU. In some examples, these streams (e.g., flows) may be multiplexed. If the streams are multiplexed, a burst may be composed of a combination of the streams and may be detected and processed as described herein. The multiple streams may be sent in different flows (e.g., different SDF and / or QoS flows). In this case, EOB may be detected separately for each flow. The UPF / RAN may (e.g., determine to) wait for the EOBs (e.g., all EOBs) to be detected on each related flow (e.g., on all flows towards the same WTRU that are associated with PDU set-based QoS handling) before using the EOB (e.g., for UPF, sending EOBI to the RAN, and / or for RAN, to control WTRU sleep state). The UPF may independently send each EOBI to the RAN. The RAN may wait for the (e.g., all) related EOBIs to be received before using the EOBIs (e.g., to control a WTRU sleep state). [000137] Feature(s) associated with using EOB for non-XR traffic are provided herein. If non-XR traffic is sent to the WTRU, the RAN may consider the non-XR flows when deciding whether to use EOB / EOBI to control the sleep state of the WTRU. For example, upon determining EOB, the RAN may wait until one or more (e.g., all) queued PDUs for the WTRUs are transmitted. The RAN may (e.g., may then) calculate a value that is the minimum of the PSDB on all other QoS flows to the WTRU. The RAN may calculate the time until the next start of a burst. The RAN may set the WTRU sleep time to the time until the next start ofa burst. In this case, the RAN may ensure that a new PDU may still be transmitted within the appropriate PSDB (e.g., even if the new PDU is received immediately after placing the WTRU in sleep mode). [000138] Feature(s) associated with using specific header extensions to detect an EOB are provided herein. [000139] Feature(s) associated with detecting the EOB when RTP traffic uses specific header extensions are provided herein. If the EOB is detected, the UPF may trigger an indication to the RAN (e.g., NG-RAN) to indicate the EOB. [000140] Feature(s) associated with detecting the EOB based on specific header extensions are provided herein. [000141] As described herein (and illustrated in FIG.4), the UPF may be configured by the SMF with information that indicates what type of traffic (e.g., what type of header) may be present in the traffic of a flow. The UPF may 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. [000142] An RTP header extension may include a flag that indicates that the PDU is part of the last PDU set of a burst of PDU sets. The UPF may determine that the end of a burst is detected (e.g., when the entire PDU set has been received by the UPF). The UPF may determine that the entire PDU set has been received if the number of bytes of the PDU set matches the PDU set size. The UPF may determine that the entire PDU set has been received if a PDU of the PDU set is received and the PDU’s end flag is set in the header. [000143] If the UPF counts the number of bytes of the PDU set that has been received to determine the EOB, the UPF may detect the end of the PDU set even if the packets are received by the UPF in an order that is different than the order in which the packets were sent. [000144] If the UPF uses the end flag to detect the end of a PDU set, the UPF may not (e.g., may not need to) count the number of packets that have been received so far from the PDU set (e.g., thereby needing less memory to maintain state associated with the PDU set). [000145] An RTP header extension may include the time at which the next PDU set on the service data flow is expected to arrive. Based on this information and / or the BII, the UPF may determine which PDU set may be the last PDU set in a burst. The UPF may determine that the end of a burst is detected if all PDUs of the last PDU set in a burst have been received by the UPF. [000146] An end-of-burst indication may be signaled in the PDU set information header extension. A burst identifier may be signaled in the PDU set information header extension.[000147] FIGs.5 and 6 illustrate example syntax and semantics for the end of data burst (e.g., 2 bits in length) and / or burst ID (e.g., 8 bits in length) in PDU set information header extension. FIG.5 illustrates an example RTP header extension using a one-byte header format. FIG.6 illustrates an example RTP header extension using a two-byte header format. [000148] The EOB flag (e.g., 2 bits in length) may be set to 0x01 for the last PDU of the data burst. The EOB flag may be set to 0x00 if the current PDU is not the last PDU of the data burst. The EOB flag may be set to 0x10 if the end-of-burst indication is not indicated in the PDU set information RTP header extension. The EOB flag may be set to 0x11 if the PDU is part of the last PDU set of the data burst. [000149] The burst ID (e.g., 8 bits in length) may have a value set to 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) may have the same burst ID. [000150] The end-of-burst in a media stream may be identified by setting the RTP header extension EOB field to 0x01 for the last PDU of a reference frame. The reference frames in a media stream may be larger in size. The reference frames may use (e.g., require) several PDUs and PDU sets to transmit the coded frame data. [000151] The end-of-burst may be indicated for the last PDU of a coded picture (e.g., each coded picture) or the last PDU of a coded group of pictures (GOP). In video coding, a GOP structure may indicate the order in which intra and inter coded frames are arranged. The GOP may include a collection of successive pictures within a coded video stream. A coded video stream (e.g., each coded video stream) may include successive GOPs, from which the visible frames are generated. [000152] The end-of-burst may be indicated for PDUs (e.g., all the PDUs) in the last PDU set of a reference frame or GOP (e.g., using RTP header extension EOB field value 0x11). In this case, the UPF / RAN may detect an EOB when the UPF / RAN completely receives the PDUs of the PDU set (e.g., by comparing the number of bytes received for the PDU set with the PDU set size information element (IE)). [000153] The burst identifier may be derived from a media timestamp (e.g., a media decoding timestamp, or a media display timestamp). The burst identifier may be a subset of the bits in the timestamp (e.g., which may enable successive bursts to have a different identifier). Generating the burst identifier based on bits of the timestamp may enable multiple decoders (e.g., for different media types) in the same session to obtain the same burst identifier without coordination between the decoders. [000154] The burst identifier may be a sequence number (e.g., set by the sender when starting a new independent frame). In this case, PDUs that carry different media types may have a different burst ID (e.g., even if they carry data that will be displayed at a time, at a same time, or at a similar time) unless thedifferent decoders cooperate to synchronize the sequence numbers. In this case, the UPF may (e.g., separately) detect the start and end of bursts for different flows / media types. [000155] Using a burst identifier may enable the UPF to detect the start of a burst and the end of a burst (e.g., with limited processing requirements). For example, the UPF may use a change in burst ID to determine that a burst has merged with the next burst. The UPF may count PDU sets belonging to a (e.g., single) burst or may count the number of bytes in a (e.g., single) burst. The UPF may (e.g., may then) use one of the techniques described herein to detect an EOB. [000156] Feature(s) associated with using existing RTP / SRTP headers, header extensions, and payloads to detect an EOB are provided herein. [000157] Feature(s) associated with detecting the EOB if the RTP traffic uses existing RTP / SRTP headers, header extensions, and payloads are provided herein. If an EOB is detected, the UPF may trigger an indication to the RAN (e.g., NG-RAN) to indicate the EOB. [000158] Feature(s) associated with detecting an EOB based on timestamp changes are provided herein. [000159] As described herein (and illustrated in FIG.4), the UPF may be configured by the SMF with rules that may be used to detect information in the downlink traffic (e.g., the headers). The UPF may use the detected information to detect the end of data bursts. [000160] The UPF may be configured with a (e.g., single) trigger IE ID RTP timestamp. The trigger may indicate (e.g., using an associated start-of-burst IE) to the UPF that a new burst may be detected when the RTP timestamp transitions to a higher value. The UPF may determine a pattern. For example, within a burst (e.g., between two consecutive “start-of-burst” PDUs), the burst may include seven PDU sets. A PDU set (e.g., each PDU set) may include PDUs with the same RTP timestamp. To determine which pattern to look for, the UPF may use an “end-of-burst” IE. For example, the “end-of-burst” IE may describe a burst pattern based on the PDU set ID. If the UPF observes several consecutive occurrences of the pattern, the UPF may enter a steady state (e.g., where the UPF expects this measured number to be stable). The UPF may stay in the stable state if (e.g., as long as) the UPF continues to regularly observe the measured number. In the steady state, the UPF may report an end-of-burst on the last PDU of the last PDU set of the seven PDU sets following a start-of-burst, if the seven PDU sets are complete. The UPF may detect a PDU set is complete (e.g., based on one or more of the PDU set size, end of PDU set indication, and / or PDU sequence number within the PDU set). To enable detection of end-of-burst, if some PDU sets are incomplete, the UPF may reset a timer (e.g., using the in-burst inter-PDU timeout from BII) after each received PDU on a given burst and trigger a timeout if the timer expires before an end-of-burst is detected. If the UPF triggers a timeout, the UPF may send a GTP-U message, including an end-of-burst indication for the QoS flow / SDF.[000161] The UPF may 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 multilayer media encoding scheme) and the RTP timestamp transitions to a different value, the related start-of-burst IE may indicate to detect a start-of-burst. The UPF may detect a new burst even if the video player jumps to an earlier position in the stream. [000162] Feature(s) associated with detecting EOB based on an RTP timestamp are provided herein. [000163] FIG.7 illustrates an example RTP header format. The EOB may be detected if the timestamp value of the media changes in an RTP header (e.g., as illustrated in FIG.7). The media data belonging to a particular time may be sent as a burst. For example, PDUs (e.g., all PDUs) that are associated with a burst may have the same timestamp. If a new timestamp is detected in the RTP packet header of an RTP stream, the end-of-burst notification may be signaled in the PDU set information RTP header extension, or the UPF may 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 type (e.g., each different type) of media, the RTP timestamp may be related to the sampling instant by pairing the RTP timestamp with a timestamp from a reference clock (e.g., wall clock) that represents the time when the data corresponding to the RTP timestamp was sampled. For example, to determine if two or more media flows are part of the same burst, the timestamps in an RTP packet header may not be compared directly. The timestamps in the RTP packet header may be compared to a reference clock to determine if the timestamps were transmitted at the same time. [000164] Feature(s) associated with detecting EOB based on a marker bit in the RTP header are provided herein. [000165] The EOB may be detected if the marker (M) bit in the RTP header is set. The marker bit may allow significant events (e.g., such as frame boundaries) to be marked in the RTP packet stream. If a marker bit is set, the marker bit may indicate that the frame boundary has been reached. In this case, the corresponding PDU may be marked with an end-of-burst notification in the RTP header extension, or the UPF may send a GTP-U message including an end-of-burst indication. [000166] Feature(s) associated with detecting an EOB based on traffic patterns are provided herein. [000167] If the EOB is detected upon the reception of a PDU by the UPF, the UPF may transmit the PDU to the RAN with an EOB indication set in the GTP-U header that encapsulates the PDU sent to the RAN. If the EOB is detected following a timeout by the UPF, the UPF may send a pseudo PDU (e.g., a size 0 PDU, associated with the QoS flow / SDF) to the RAN. The pseudo PDU may be associated with an EOB indication set in the GTP-U header. [000168] Feature(s) associated with detecting an EOB based on inter-PDU timeout are provided herein.[000169] EOB detection may be based on an inter-PDU timeout (e.g., based on a configuration including a BII with an in-burst inter-PDU timeout IE). The UPF may (e.g., initially) detect a start-of-burst using start-of- burst values. If a start-of-burst is detected, the UPF may start (e.g., begin) a timer for inter-PDU timeout and reset the timer value each time a PDU of this service data flow is received. If the timer expires, the UPF may determine that the end of a burst is detected. The UPF may signal the EOBI to RAN (e.g., the UPF may send an empty GTP-U packet including an EOBI for this SDF or QoS flow). [000170] The UPF may determine that a PDU set is the last PDU set of a burst (e.g., in a case where there is a single PDU set per burst or when the number of PDU sets per burst is known / learned by the UPF). For example, the UPF may determine that a PDU is the last PDU of the PDU set by comparing the number of bytes received in the PDU set with the PDU set size IE value. 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 received PDU of the PDU set. [000171] Feature(s) associated with detecting an EOB based on a number of PDU sets or a burst size are provided herein. [000172] Feature(s) associated with detecting an EOB based on counting the PDU sets in a burst are provided herein. For example, the EOB may be detected based on a configuration including a BII with a trigger IE “PDU Set ID” associated with 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 may learn the number of PDU sets in a burst (e.g., during the burst processing initialization state) by analyzing traffic (e.g., instead of obtaining a fixed number of PDU sets from BII). [000173] If a start-of-burst is detected, the UPF may count the PDU sets following the start-of-burst. If the number of completed received PDU sets corresponds to the configured / learned number of PDU sets per burst, the UPF may determine that the end of a burst is detected. The UPF may determine that a PDU set is completed if all PDUs of the set are received, or if all PDUs of the set are either received or determined to have been lost (e.g., after a timeout has elapsed). [000174] The UPF may count the received bytes and compare the number of received bytes with the burst size configured in BII. The UPF may detect the EOB if the received size (e.g., received number of bytes) reaches the configured burst size, and if no other start of burst was determined in the meantime. [000175] Feature(s) associated with detecting an EOB based on other traffic patterns are provided herein. [000176] An EOB may be detected based on traffic patterns (e.g., based on a configuration including BII with a trigger IE “PDU Set ID” associated with end-of-burst IE with “detected pattern of transitions”). The UPF may detect a start-of-burst using start-of-burst values. For example, the UPF may measure the jitteron successive start-of-burst. The UPF may use trigger IEs IDs to identify patterns in a burst. If a pattern is repeated n times in a row (e.g., n being a value based on protocol ID, configuration, or internal algorithm), the UPF may use this pattern to detect the end-of-burst. [000177] Feature(s) associated with indicating an EOB to the RAN (e.g., NG-RAN) are provided herein. [000178] The UPF may indicate (e.g., to the NG-RAN) that the end of a burst has been detected. The indication may be sent in a GTP-U message. The RAN (e.g., NG-RAN) may use this indication to put the WTRU into a sleep (e.g., low power) state. FIG.8 illustrates an example of the UPF indicating a detected EOB. [000179] In FIG.8, at 1, the AS may transmit DL PDUs to a WTRU. The DL PDUs may enter the 5G system at the UPF. The DL PDUs may be received in an order that is different than the order in which they were transmitted by the AS. [000180] At 2, the UPF may use configuration information (e.g., the burst information that was received, as illustrated in FIG.4) to detect the end of PDU set bursts. The UPF may send end of burst information to the RAN. Feature(s) associated with sending EOB information to the RAN are described herein. [000181] At 3, the RAN may use the EOB information to determine whether and / or when to place the WTRU into a sleep (e.g., low power) state (e.g., by configuring a WTRU power saving management scheme such as connected mode DRX). [000182] The EOB indication may be sent to the RAN in a G-PDU GTP-U message. The header extension of the G-PDU packet may include an EOBI. The UPF may determine whether and / or when to include the EOBI. [000183] The UPF may receive (e.g., after the UPF sends the EOBI to the NG-RAN) another PDU that is part of the same PDU set burst associated with the EOBI. For example, the UPF may receive another PDU from the same PDU set burst if packets (e.g., PDUs) are received by the UPF in an order that may be different than the order in which they were transmitted by the AS. To decrease the likelihood that the EOBI may trigger the RAN to put the WTRU into a sleep state before additional PDU(s) of the burst are received, the UPF may send a wait-time to the RAN with the EOBI. The wait-time may be included in the header extension. The wait-time may be an indication to the RAN that the end of a burst may not be assumed until after the wait-time has expired and the EOBI has been received. [000184] The UPF may be configured with the wait-time by the SMF (e.g., as illustrated in Fig.4) or the UPF may determine the wait-time based on the content of the burst identification information (e.g., the protocol ID). The wait-time may be sent to the RAN as part of a QoS profile.[000185] If the UPF detects that the UPF has received the first PDU of a burst, the UPF may 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 may identify the burst and indicate the size of the burst. The RAN may (e.g., may then) use this information to detect the end of the burst. For example, the RAN may determine that the burst has ended if the amount of data received matches the indicated size of the burst. The burst may be identified by a QoS flow identifier. Identifying the burst with a QoS flow identifier may be used if the QoS flow is not expected to carry data that is not associated with the burst until the burst is over (e.g., during transmission of the burst, the QoS flow is expected to only carry data associated with the burst). The burst may be identified by one or more PDU set identifiers. The one or more PDU set identifiers may include an indication to the RAN that data that is part of the identified PDU sets (e.g., only 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 is expected to carry data (e.g., also carry data) that is not associated with the burst. [000186] The new GTP-U message may indicate a time value for the RAN to use to configure a timer. The RAN may determine (e.g., assume) that the burst is over when the timer expires. For example, if the timer is expired, the RAN may determine (e.g., assume) that the burst is over even if the amount of received data does not match the indicated size. The UPF may be triggered to send the new GTP-U message when the UPF receives the first PDU of a burst. However, the first PDU that is detected by the UPF may not be the first PDU that was transmitted by the AS (e.g., because the packets may not be received in the same order that the packets were sent). The UPF may send the new GTP-U message to the RAN to indicate the start of a burst and provide information about the burst (e.g., so that NG-RAN can detect the end of the burst). This technique may be more accurate than some other techniques (e.g., as 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 may be more accurate because PDUs from the burst may be received even after the UPF detects an indication (e.g., in the application layer header) that the burst is over (e.g., because packets may be received in an order that is different from the order in which the packets were transmitted). [000187] Feature(s) associated with RAN-based detection of EOB are provided herein. [000188] Feature(s) associated with configuration and behavior of the RAN are provided herein. [000189] The RAN may be configured to detect the end of a burst. The configuration information may be sent to the RAN by the SMF (e.g., in a QoS profile IE). [000190] A QoS profile may include a BII IE. [000191] The BII sent to the RAN may include trigger IE IDs. The trigger IE IDs may identify IEs present in GTP-U messages that encapsulate a PDU. For example, the trigger IE IDs may identify PDU set IEs suchas 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, burst size, burst time length, and / or an EOBI. [000192] A start-of-burst may be identified (e.g., in the BII) as the first received PDU of a PDU set (e.g., any independent PDU set that is marked as not depending on any other PDU set for decoding). [000193] A start-of-burst may be identified (e.g., in the BII) if the RAN receives more than N PDUs in a row or in short succession (e.g., separated by a time shorter than the configured in-burst inter-PDU timeout). The value of N may be configured (e.g., in a start-of-burst value in the BII). [000194] An end-of-burst may be identified (e.g., in the BII) if an inter-PDU timeout occurs. [000195] An end-of-burst may be identified (e.g., in the BII) if N PDU sets are completely received (e.g., with all PDUs being received or determined as lost, for example, based on a timeout). The value of N may be configured (e.g., in a start-of-burst value in the BII). [000196] An end-of-burst may be identified (e.g., in the BII) if a PDU is received from the UPF with the EOBI set (e.g., in a GTP-U header). More than one EOB detection technique (e.g., both RAN-based and UPF-based EOB detection) may be active at the same time. In this case, the BII used to configure the RAN may describe two end-of-bursts (e.g., one end-of-burst for detecting EOB using EOBI, and another end-of- burst for detecting EOB using another technique, as described herein). [000197] An example BII may include information that identifies a start-of-burst using a timestamp change. An example BII may include information that identifies an end-of-burst (e.g., using a technique based on inter-PDU timeout or on a trigger IE). The UPF may obtain the timestamp (or a value derived from the timestamp, for example, a subset of the bits used to encode the timestamp) in order to use the technique based on a timestamp change, and the UPF may provide the timestamp to the RAN (e.g., in a GTP-U header field). [000198] The UPF or RAN may identify an EOB if the size of the received PDUs reaches the expected size of a burst (e.g., as configured in BII and / or sent by the UPF to the RAN as described herein, for example, using a GTP-U message containing the burst size). [000199] Feature(s) associated with the RAN detecting an EOB based on a traffic pattern are provided herein. [000200] Feature(s) described herein related to UPF-based detection of EOB (e.g., using an inter-PDU timeout, a number of PDU sets, and other traffic patterns) may be similarly performed by the RAN (e.g., based on configured BII). The RAN may use the indication or information to help determine whether and / orif / when to place the WTRU in a sleep (low power) state (e.g., thereby saving WTRU power and increasing the battery life of the WTRU). [000201] 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). [000202] The network node may receive configuration information for detecting an end of a burst of packet data unit (PDU) sets. The network node may receive the burst of PDU sets. The network node may detect, based on the configuration information, the end of the burst of PDU sets. The network node may send, to a base station, an indication of the detected end of the burst of PDU sets. [000203] The configuration information may include an IE indicating a time value of when a start of the burst of PDU sets may 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. [000204] Detecting the end of the burst of PDU sets may involve determining a first timestamp associated with a first PDU set and the burst of PDU sets, determining a second timestamp associated with a second PDU set, and determining the end of the burst of PDU sets using the first timestamp and the second timestamp. The second timestamp may be different from the first timestamp. The burst of PDU sets may include the first PDU set. [000205] Detecting the end of the burst of PDU sets may involve identifying (e.g., determining) a message header (e.g., of 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 may determine that the PDU satisfies the EOB condition based on the indication in the message header. The indication may be sent to the base station when the end of the burst of PDU sets is determined using the message header. [000206] Detecting the end of the burst of PDU sets may involve determining a set of PDUs was received during a first duration of time. The network node may determine a second duration of time based on the determination that the set of PDUs was received during the first duration of time. The network node may determine the end of the burst of PDU sets when the second duration of time has elapsed. The burst of PDU sets may include the set of PDUs. [000207] Detecting the end of the 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 of the determined PDU set. The network node may determine a received byte size value that indicates a calculated byte sizeof 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. [000208] Detecting the end of the burst of PDU sets may involve determining an expected byte size value of the burst of PDU sets. The network node may determine a received byte size value using the burst of PDU sets. The network node may determine the end of the burst of PDU sets when the received byte size value is within an acceptable range of (e.g., similar to) the expected byte size value. [000209] Detecting the end of the burst of PDU sets may involve determining a number of PDU sets that are associated with the burst of PDU sets. The network node may determine an expected byte size value of the number of the 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 burst of PDU sets when the received byte size value is within an acceptable range of (e.g., similar to) the expected byte size value. [000210] The configuration information may include an information element (IE) indicating a PDU set identifier (ID). Detecting the end of the burst of PDU sets may involve determining a PDU pattern using the PDU set identifier. The network node may determine a number of PDU sets associated with the burst of PDU sets using the PDU pattern. The network node may determine the end of the burst of PDU sets using the determined number of PDU sets. [000211] This disclosure describes devices and methods for detecting and indicating the end of a burst by a radio access network (e.g., by a base station). [000212] The base station may receive configuration information for detecting an end of a burst of packet data unit (PDU) sets. The base station may receive the burst of PDU sets. The base station may detect, based on the configuration information, the end of the burst of PDU sets. The base station may send, based on the end of the burst of PDU sets being detected, a message to change the configuration of a device (e.g., a wireless transmit / receive unit (WTRU)). The configuration of the device may indicate a time for the device to enter a sleep state. The base station may determine that the burst of PDU is associated with extended reality (XR) traffic. [000213] The configuration information may include an information element (IE) indicating a start of a burst of PDU sets (e.g., 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 number of PDU sets associated with the burst of PDU sets. The network node may determine a burst pattern using the number of PDU sets in the burst of PDU sets. The network node may determine the end of the burst of PDU sets using the PDU pattern. For example, the network node may determine that the PDU satisfies the condition based on the burst pattern. The time value may include a timestamp value.[000214] Detecting the EOB of the 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. [000215] Detecting the end of the burst of PDU sets may involve determining a set of PDUs (e.g., in the burst of PDU sets) was received during a first duration of time. The network node may determine a second duration of time based on the determination that the set of PDUs was received during the first duration of time. The network node may determine that the PDU satisfies the condition (e.g., may detect the end of the burst of PDU sets) if the second duration of time has elapsed. The burst of PDU sets may include the set of PDUs. [000216] Detecting the end of the 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 of 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 if / when the received byte size value is within an acceptable range of (e.g., similar to) the expected byte size value. [000217] Detecting the end of the burst of PDU sets may involve determining an expected byte size value of the burst of PDU sets. The network node may determine a received byte size value using the burst of PDU sets. The network node may 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. Detecting the end of the burst of PDU sets may involve determining a number of PDU sets that are associated with the burst of PDU sets. The network node may determine an expected byte size value of the number of the 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 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. [000218] The configuration information may include an information element (IE) indicating a PDU set identifier (ID). Detecting the end of the burst of PDU sets 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 burst of PDU sets. The network node may determine the end of the burst of PDU sets using the determined number of PDU sets.[000219] Although features and elements described above are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without other features and elements. [000220] Although the implementations described herein may consider 3GPP specific protocols, it is understood that the implementations described herein are not restricted to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well. [000221] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and / or wireless connections) and / or computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact disc (CD)-ROM disks, and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

CLAIMS What is Claimed:

1. A network node, the network node comprising: a processor configured to: receive configuration information that indicates a condition indicative of an end of a burst of packet data unit (PDU) sets; receive the burst of PDU sets, wherein the burst of PDU sets comprises a PDU; detect, based on the PDU satisfying the condition, 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.

2. The network node of claim 1, wherein the burst of PDU sets is a first burst of PDU sets, the configuration information further comprises an information element (IE) indicating a 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, based on the PDU satisfying the condition, 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 the condition based on the burst pattern.

3. The network node of claim 1, wherein the processor being configured to detect, based on the PDU satisfying the condition, 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 the condition based on the second timestamp being different from the first timestamp.

4. The network node of claim 1, wherein the processor being configured to detect, based on the PDU satisfying the condition, 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 the condition based on the indication in the message header.

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

6. The network node of claim 1, wherein the processor being configured to detect, based on the PDU satisfying the condition, 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 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 from the expected byte size value, determine that the PDU satisfies the condition.

7. The network node of claim 1, wherein the processor being configured to detect, based on the PDU satisfying the condition, 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 from the expected byte size value, determine that the PDU satisfies the condition.

8. The network node of claim 1, wherein the processor being configured to detect, based on the PDU satisfying the condition, the end of the burst of PDU sets comprises the processor being configured to: 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 the PDU sets; determine a received byte size value based on the number of PDU sets; andon a condition that the received byte size value is within an acceptable range from the expected byte size value, determine that the PDU satisfies the condition.

9. The network node of claim 1, wherein the configuration information further comprises an information element (IE) indicating a PDU set identifier (ID), and wherein the processor being configured to detect, based on the PDU satisfying the condition, 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 the condition based on the determined number of PDU sets.

10. A method, to be performed by a network node, the method comprising: receiving configuration information that indicates a condition indicative of an end of a burst of packet data unit (PDU) sets; receiving the burst of PDU sets, wherein the burst of PDU sets comprises a PDU; detecting, based on the PDU satisfying the condition, 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.

11. The method of claim 10, wherein the burst of PDU sets is a first burst of PDU sets, the configuration information further comprises an information element (IE) indicating a start of a second burst of PDU sets, the method further comprises receiving the second burst of PDU sets, and detecting, based on the PDU satisfying the condition, 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 the condition based on the burst pattern.

12. The method of claim 10, wherein detecting, based on the PDU satisfying the condition, 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; anddetermining that the PDU satisfies the condition based on the second timestamp being different from the first timestamp.

13. The method of claim 10, wherein detecting, based on the PDU satisfying the condition, the end of the 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 the condition based on the indication in the message header.

14. The method of claim 10, wherein detecting, based on the PDU satisfying the condition, the end of the burst of PDU sets comprises: determining a set of PDUs was received during a first duration of time, wherein the burst of PDU sets comprises the set of PDUs; determining a second duration of time based on the determination that the set of PDUs was received during the first duration of time; and on a condition that the second duration of time has elapsed, determining that the PDU satisfies the condition.

15. The method of claim 10, wherein detecting, based on the PDU satisfying the condition, 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 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 from the expected byte size value, determining that the PDU satisfies the condition.

16. The method of claim 10, wherein detecting, based on the PDU satisfying the condition, the end of the 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; andon a condition that the received byte size value is within an acceptable range from the expected byte size value, determining that the PDU satisfies the condition.

17. The method of claim 10, wherein detecting, based on the PDU satisfying the condition, the end of the 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 the 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 from the expected byte size value, determining that the PDU satisfies the condition.

18. The method of claim 10, wherein the configuration information further comprises an information element (IE) indicating a PDU set identifier (ID), and wherein detecting, based on the PDU satisfying the condition, the end of the burst of PDU sets 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 burst of PDU sets; and determining that the PDU satisfies the condition based on the determined number of PDU sets.

Images