Network resource allocation based on delay information.

Description

1 / 52 “NETWORK RESOURCE ALLOCATION BASED ON DELAY INFORMATION” CROSS-REFERENCE TO RELATED ORDERS

[001] This application claims the benefit of U.S. Provisional Application No. 63 / 457,512, filed April 6, 2023, the full contents of which are incorporated herein by reference. BACKGROUND

[002] An application function (AF) can provide assistance information related to the protocol data unit (PDU) set for billing and dynamic policy control (PCC). Parameters can be included in the PDU set QoS parameters. A parameter can include a PDU set delay budget (PSDB). A PSDB can include an upper limit for the delay that a PDU set can experience in the transfer between a wireless transmit / receive unit (WTRU) and the N6 termination point on the UPF, for example, the duration between the time of reception of the first PDU and the time when all PDUs in a PDU set have been successfully received. SUMMARY

[003] This disclosure relates to devices, methods and systems for allocating network resources based on extended reality and media (XRM) traffic delay requirements. Devices, methods and systems for latency and coverage enhancement for network resource allocation and, in particular, network resource allocation based on XRM traffic delay requirements are provided herein.

[004] Devices, methods, and systems refer, for example, to round-trip time (RT) requirements with uplink and downlink delay limits. Devices, methods, and systems refer, for example, to determining QoS requirements based on attributes defined by PDUs. In a Petition 870250090043, dated 02 / 10 / 2025, page 12 / 81 In 2 / 52 or more cases, devices, methods, and systems receive a message comprising RT latency requirements, where RT latency requirements include uplink delay information and downlink delay information. In one or more cases, devices, methods, and systems use the uplink delay information and downlink delay information to create billing policy and controls (PCC) rules and send the PCC rules to a session management function (SMF). In one or more cases, devices, methods, and systems receive a notification that the delay associated with a flow is not within the range required by the PCC rule. In one or more cases, devices, methods, and systems perform, based on the notification received,One of the following actions: use the uplink delay and downlink delay information to determine new PCC rules and send the new PCC rules to the SMF; determine that PCC rules that meet all the requirements indicated in the RT latency requirements, uplink delay information, and downlink delay information cannot be created and, based on this determination, send a notification to an AF; and determine a new set of RT latency requirements, uplink delay information, and downlink delay information, calculate new PCC rules based on the new set of RT latency requirements, uplink delay information, and downlink delay information, use the new uplink delay information and downlink delay information to determine new PCC rules, and send the new PCC rules to the SMF.

[005] A device (for example, at least one network entity) can receive a message. The message may include round-trip (RT) latency requirements. The RT latency requirements may include information about uplink delay and / or downlink delay. The device may generate the Petition 870250090043, dated 02 / 10 / 2025, page 13 / 81 3 / 52 First Billing and Control Policy (PCC) rules, for example, based on information about uplink delay and / or downlink delay. The device can send the first information indicating the first PCC rules, for example, to a session management function (SMF). The device can receive a notification that one or more uplink delays and / or downlink delays are associated with a flow. The notification may include an indication that one or more uplink delays and / or downlink delays associated with the flow are not within a range required by the first PCC rules. The device can determine the second PCC rules, for example, based on information about uplink delay and downlink delay. The device can send a second piece of information indicating the second PCC rules, for example, to the SMF.The message may include one or more multimodal service identifiers (IDs) and / or one or more traffic descriptors. The traffic descriptor(s) may include an indication of one or more uplink data flows and / or a downlink data flow.

[006] The device may send a (for example, a second) notification, for example, to an application function (AF). The notification may include an indication that PCC rules that meet one or more of the RT latency requirements, uplink delay information, and / or downlink delay information cannot be generated. RT latency requirements may include the first RT latency requirements. Uplink delay information may include the first uplink delay information. Downlink delay information may include the first downlink delay information. The device may determine the second RT latency requirements. The second RT latency requirements may include the second link delay information. Petition 870250090043, dated 02 / 10 / 2025, page 14 / 81 4 / 52 uplink and / or the second downlink delay information. The device can determine third PCC rules, for example, based on the latency requirements of the second RT. The device can send the third PCC rules to the SMF.

[007] Uplink delay information may include an indication of one or more of an uplink maximum packet delay budget (PDB) and / or an uplink maximum delay budget defined by protocol data unit (PDU). Downlink delay information may include an indication of one or more of a downlink maximum PDB and / or a downlink maximum PSDB. The device may include a policy control function (PCF). The device may generate N4 rules, for example, based on second PCC rules. The device may send one or more of a Quality of Service (QoS) profile to an access network and / or a QoS rule to a wireless transmit / receive unit (WTRU).The flow associated with one or more uplink delays and / or downlink delays may, additionally or alternatively, be associated with one or more of the first PCC rules and / or second PCC rules.

[008] A device can receive information about the protocol data unit (PDU) set delay budget (PSDB), for example, from an application function (AF). The PSDB information can indicate a first PSDB value for PDU set sizes above a threshold and / or a second PSDB value for PDU set sizes below the threshold. The device can generate a rule. The rule can indicate that PDU sets with set sizes smaller than the threshold should be assigned to a first Quality of Service (QoS) flow and / or that PDU sets with set sizes larger than the threshold should be assigned to a second QoS flow. The device can send information indicating the rule, for example, to one or more units of Petition 870250090043, dated 02 / 10 / 2025, p. 15 / 81 5 / 52 wireless transmission / reception (WTRU), a user plane function (UPF) or a radio access network (RAN).

[009] The rule may include an indication of a QoS profile, which, for example, may indicate that sets of PDUs from a first QoS flow with set sizes below the threshold should be associated with the first PSDB value. The QoS profile may additionally or alternatively indicate that sets of PDUs from the first QoS flow with set sizes above the threshold should be associated with the second PSDB value. The device may include a session management function (SMF). The device may receive policy billing and control (PCC) rules, for example, from a policy control function (PCF). The device may generate N4 rules, for example, based on the PCC rules. The device may send information indicating the N4 rules, for example, to a user plane function (UPF).The device can send an indication of whether one or more of the first QoS stream and / or the second QoS stream are within a delay range required by the rule. The rule may include an indication of a QoS rule that, for example, may indicate that sets of PDUs that match a first packet detection rule and / or have set sizes smaller than a threshold should be associated with the first QoS stream. The QoS rule may additionally or alternatively indicate that sets of PDUs that match the first packet detection rule and / or have set sizes larger than the threshold should be associated with a second QoS stream. An indication of the threshold may be included in the PSDB information. BRIEF DESCRIPTION OF THE DRAWINGS

[010] A more detailed understanding can be obtained from the following description, provided as an example in conjunction with the attached drawings, in Petition 870250090043, dated 02 / 10 / 2025, page 16 / 81 6 / 52 which similar reference numbers in the Figures indicate similar elements.

[011] Figure 1A is a system diagram that illustrates an example communications system in which one or more advertised modalities can be implemented.

[012] Figure 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that can be used within the communications system illustrated in Figure 1A.

[013] Figure 1C is a system diagram that illustrates an example radio access network (RAN) and an example main network (CN) that can be used within the communications system illustrated in Figure 1A.

[014] Figure 1D is a system diagram that illustrates an example additional RAN and an example additional CN that can be used within the communications system illustrated in Figure 1A.

[015] Figure 2 illustrates an example procedure for configuring multimodal requirements.

[016] Figure 3 illustrates an example procedure for configuring QoS monitoring. DETAILED DESCRIPTION

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

[018] As shown in Figure 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, although it is important to note that the disclosed embodiments contemplate any number of WTRUs, base stations, networks and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a mobile phone, a personal digital assistant (PDA), a smartphone, a laptop,a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in industrial and / or automated process chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks. Petition 870250090043, dated 02 / 10 / 2025, page 18 / 81 8 / 52 and similar. Any of the WTRUs 102a, 102b, 102c and 102d may be referred to interchangeably as WTRU.

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

[020] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be called cells (not shown). These frequencies may be in the licensed spectrum, the unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service for a specific geographic area, which may be relatively fixed or may change over time. The cell may also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors.Thus, in one embodiment, base station 114a may include three transceivers, that is, one for each sector of the cell. In another embodiment, base station 114a may employ multi-input technology. Petition 870250090043, dated 02 / 10 / 2025, p. 19 / 81 9 / 52 and multiple outputs (MIMO) and can use multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in the desired spatial directions.

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

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

[023] In one embodiment, base station 114a and WTRUs 102a, 102b and 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). Petition 870250090043, dated 02 / 10 / 2025, page 20 / 81 10 / 52

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

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

[026] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN) and the like.

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

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

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

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

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

[032] 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), circuits of Petition 870250090043, dated 02 / 10 / 2025, page 23 / 81 13 / 52 Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that allows the WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, which can be coupled to the transmit / receive element 122. Although Figure 1B represents processor 118 and transceiver 120 as separate components, it is important to note that processor 118 and transceiver 120 can be integrated into a single electronic package or chip.

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

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

[035] Transceiver 120 can be configured to modulate the signals to be transmitted by the transmit / receive element 122 and to demodulate the signals received by the transmit / receive element 122. As noted above, WTRU 102 can have multimode capabilities. Thus, transceiver 120 can include multiple transceivers to allow WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

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

[037] Processor 118 can receive power from power source 134 and can be configured to distribute and / or control power to the other components in WTRU 102. Power source 134 can be any device suitable for powering WTRU 102. For example, power source 134 can include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), Petition 870250090043, dated 02 / 10 / 2025, page 25 / 81 15 / 52 nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells and the like.

[038] Processor 118 can also be coupled to GPS chipset 136, which can be configured to provide location information (e.g., longitude and latitude) pertaining to the current location of WTRU 102. In addition to, or in place of, GPS chipset 136 information, WTRU 102 can receive location information via air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the reception time of signals from two or more nearby base stations. It is important to note that WTRU 102 can obtain location information by any suitable location determination method, remaining consistent with a modality.

[039] The processor 118 may also be coupled with other peripherals 138, which may include one or more software and / or hardware modules that provide additional wired or wireless features, functionality and / or connectivity. For example, peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photographs and / or video), a USB (Universal Serial Bus) 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.Peripherals 138 may include one or more sensors, which may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, orientation sensor, proximity sensor, temperature sensor, time sensor; a geolocation sensor; an altimeter, a light sensor, a sensor of. Petition 870250090043, dated 02 / 10 / 2025, page 26 / 81 16 / 52 touch, a magnetometer, a barometer, a gesture sensor, a biometric sensor and / or a humidity sensor.

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

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

[042] RAN 104 may include eNodes 160a, 160b, and 160c, although it is important to note that RAN 104 may include any number of eNodes while remaining consistent with one embodiment. eNodes 160a, 160b, and 160c may each include one or more transceivers for communication with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNodes 160a, 160b, and 160c may implement MIMO technology. Thus, eNode 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, WTRU 102a. Petition 870250090043, dated 02 / 10 / 2025, p. 27 / 81 17 / 52

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

[044] The CN 106 shown in Figure 1C may include a mobility management entity (MME) 162, a service gateway (SGW) 164, and a packet data network gateway (PDN) (or PGW) 166. Although each of the above elements is represented as part of CN 106, it is important to note that any of these elements may be owned and / or operated by an entity other than the CN operator.

[045] MME 162 can be connected to each of the eNode-Bs 162a, 162b, 162c in RAN 104 via an S1 interface and can serve as a control node. For example, MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, 102c, activating / deactivating the carrier, selecting a specific service gateway during an initial connection of WTRUs 102a, 102b, 102c, and similar. MME 162 can provide a control plane function to switch between RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM and / or WCDMA.

[046] SGW 164 can be connected to each of the B eNodes 160a, 160b, and 160c in RAN 104 via the S1 interface. SGW 164 can generally route and forward user data packets to / from WTRUs 102a, 102b, and 102c. SGW 164 can perform other functions such as anchoring user planes during transfers between B eNodes, initiating paging when DL data is available for WTRUs 102a, 102b, and 102c, managing and storing contexts for WTRUs 102a, 102b, and 102c, and similar functions. Petition 870250090043, dated 02 / 10 / 2025, p. 28 / 81 18 / 52

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

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

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

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

[051] A WLAN in Basic Services Infrastructure Set (BSS) mode can have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can have access or an interface to a Distribution System (DS) or other type of wired / wireless network that carries inbound and / or outbound traffic from the BSS. Traffic to STAs originating outside the BSS can arrive through the AP and be delivered to the STAs. Traffic originating from the STAs to destinations outside the BSS can be sent to the AP to be delivered to the respective destinations. Traffic between STAs within the BSS can be sent through the AP, for example, Petition 870250090043, dated 02 / 10 / 2025, p. 29 / 81 19 / 52 in which the source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within a BSS can be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between (e.g., directly between) the source and destination STAs with a direct link-through (DLS) configuration. In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to here as an ad-hoc communication mode.

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

[053] High-throughput (HT) STAs can utilize a 40 MHz wide channel for communication, for example, by combining the 20 MHz primary channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel. Petition 870250090043, dated 02 / 10 / 2025, p. 30 / 81 20 / 52

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

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

[056] WLAN systems, which can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the highest common operational bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be defined and / or limited by an STA, among all STAs operating in a BSS, that supports the operating mode with the lowest bandwidth. In the 802.11ah example, the primary channel may have a 1 MHz bandwidth for STAs (e.g., MTC-type devices) that support (e.g., only support) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings may depend on the primary channel status.If the primary channel is busy, for example, due to an STA (which only supports 1 MHz operating mode) transmitting to the AP, all available frequency bands can be considered occupied, even if most frequency bands remain idle and could be available.

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

[058] Figure 1D is a system diagram illustrating RAN 113 and CN 115 according to a modality. As noted above, RAN 113 can employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 113 can also be in communication with CN 115. Petition 870250090043, dated 02 / 10 / 2025, p. 32 / 81 22 / 52

[059] RAN 113 may include gNBs 180a, 180b, and 180c, although it is important to note that RAN 113 may include any number of gNBs while remaining consistent with a mode. gNBs 180a, 180b, and 180c may each include one or more transceivers for communication with WTRUs 102a, 102b, and 102c via air interface 116. In a mode, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 108b may use beamforming to transmit and / or receive signals from gNBs 180a, 180b, and 180c. Thus, the gNB 180a, for example, can use multiple antennas to transmit and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, the gNB 180a can transmit multiple component carriers to the WTRU 102a (not shown).A subset of these component carriers may be in unlicensed spectrum, while the remaining component carriers may be in licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c may implement CoMP (Coordinated Multi-Point) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[060] WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol spacing and / or the OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing a variable number of OFDM symbols and / or lasting variable absolute time lengths). Petition 870250090043, dated 02 / 10 / 2025, page 33 / 81 23 / 52

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

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

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

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

[065] SMF 183a, 183b can be connected to AMF 182a, 182b on CN 115 via an N11 interface. SMF 183a, 183b can also be connected to UPF 184a, 184b on CN 115 via an N4 interface. SMF 183a and 183b can select and control UPF 184a and 184b and configure traffic routing. Petition 870250090043, dated 02 / 10 / 2025, page 35 / 81 25 / 52 via UPF 184a and 184b. SMF 183a and 183b can perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy and QoS enforcement, providing downlink data notifications, and similar functions. A PDU session type can be IP-based, non-IP-based, Ethernet-based, and similar.

[066] UPF 184a, 184b can be connected to one or more of gNBs 180a, 180b, 180c in RAN 113 via an N3 interface, which can provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices. UPF 184, 184b can perform other functions such as packet routing and forwarding, user plane policy enforcement, support for multihomed PDU sessions, user plane QoS handling, downlink packet buffering, mobility tethering provision, and the like.

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

[068] In view of Figures 1A-1D and the corresponding description of Figures 1A-1D, one or more, or all, of the functions described herein relate to one or more of the following: WTRU 102a-d, Base Station 114a-b, eNo-B 160a-c, MME 162, SGW Petition 870250090043, dated 02 / 10 / 2025, p. 36 / 81 26 / 52 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, or any other devices described herein may be implemented by one or more emulation devices (not shown). Emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[069] Emulation devices may be designed to implement one or more tests of other devices in a laboratory environment and / or in a carrier network environment. For example, one or more emulation devices may perform one or more, or all, of the functions while fully or partially deployed and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more emulation devices may perform one or more, or all, of the functions while temporarily deployed / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for testing purposes and / or may perform tests using wireless communications.

[070] One or more emulation devices may perform one or more, including all, of the functions while not implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used in a test scenario in a test laboratory and / or in an undeployed (e.g., under test) wired and / or wireless communication network to implement the testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuits (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data. Petition 870250090043, dated 02 / 10 / 2025, page 37 / 81 27 / 52

[071] A network (NW) can be configured with RT latency information (e.g., latency requirement). Additionally, or alternatively, the NW can be configured with information (e.g., in addition to the RT latency requirement), for example, in a policy control function (PCF). The information may include one or more maximum uplink delays and / or maximum downlink delays. The uplink and / or downlink delays may include a protocol data unit (PDU) defined delay budget (PSDB). For example, configuring the uplink delay and / or downlink delay to be (e.g., include) a PSDB may allow an application function (AF) to configure a round-trip time requirement.The round-trip time requirement may apply to a scenario in which traffic in one direction carries PDU set(s) and / or traffic in the other direction carries PDU(s) that are not part of a PDU set.

[072] A session management function (SMF) can receive PSDB information, for example, from the PCF. PSDB information can be used to determine a PSDB from a set of PDUs. PSDB information can include a PSDB determination rule that, for example, can map one or more traffic characteristics to a PSDB. One or more of the traffic characteristics may be related to the size of a set of PDUs. The network, for example, the SMF, can use the PSDB information to construct one or more rules. The one or more rules can be N4 rules. The SMF can send one or more rules (e.g., information indicating one or more rules), for example, to a user plane function (UPF). The network (e.g., SMF) can send information indicating the rule, for example, to one or more wireless transmit / receive units (WTRUs), a user plane function (UPF), or a radio access network (RAN).One or more rules may include packet detection rules. One or more rules may indicate, for example, to the UPF. Petition 870250090043, dated 02 / 10 / 2025, p. 38 / 81 28 / 52 sets of PDUs that match a given packet detection rule and / or are smaller than a given size must be assigned to a (e.g., given) Quality of Service (QoS) flow. The flow may be associated with one or more uplink or downlink delays. Additionally, or alternatively, the flow may be associated with one or more of the (e.g., first) PCC rules and / or the (e.g., second / new) PCC rules.

[073] The NW, for example, the PCF, may receive a message. The message may include RT latency requirements. The message may be received from the AF. RT latency requirements may include uplink delay information and / or downlink delay information. For example, the message may include a multimodal service identifier (ID). Additionally, or alternatively, the message may include one or more traffic descriptors that, for example, may identify uplink and / or downlink data streams. Uplink delay information may indicate (e.g., represent) a maximum uplink PDB and / or a maximum uplink PSDB. Additionally, or alternatively, uplink delay information may indicate a percentage representing the maximum percentage of RT latency requirement that may be applied to uplink traffic.Downlink delay information may represent a maximum downlink PDB and / or a maximum downlink PSDB. Additionally, or alternatively, downlink delay information may indicate a percentage representing the maximum percentage of RT latency requirement that can be applied to downlink traffic.

[074] The network network (NW), for example, the PCF, can use uplink and / or downlink delay information to generate (for example, Petition 870250090043, dated 02 / 10 / 2025, page 39 / 81 29 / 52 create) PCC rules. The PCF can send information indicating the PCC rules to an SMF. The network, for example, the PCF, may receive a notification that the delay associated with a flow (e.g., QoS flow) is not within the range required by the PCC rule. The NW, for example, the PCF, may determine (e.g., new) PCC rules. The NW may determine the PCC rules based on (e.g., receiving) the notification. For example, based on receiving the notification, the PCF may use uplink and / or downlink delay information to determine new PCC rules. Uplink and / or downlink delay information may include new (e.g., updated) uplink and / or downlink delay information. The PCF may send the new PCC rules, for example, to the SMF.

[075] The PCF may (e.g., based on receiving the notification) determine that PCC rules that meet (e.g., all) the requirements cannot be created. A requirement may be indicated in one or more of the RT latency requirements, uplink delay information, and / or downlink delay information. The PCF may send a notification to an AF, for example, based on the determination that PCC rules that meet (e.g., all) the requirements cannot be created. The notification may include an indication of whether one or more of the uplink delays and / or downlink delays cannot (e.g., or can) be met. The PCF may, for example, based on (e.g., receiving) the notification, determine one or more of a new set of RT latency requirements, uplink delay information, and / or downlink delay information.The PCF can calculate new PCC rules, for example, based on the new set of RT latency requirements, uplink delay information, and / or downlink delay information. The PCF can use the new uplink delay information and / or downlink delay information to... Petition 870250090043, dated 02 / 10 / 2025, p. 40 / 81 30 / 52 Determine new PCC rules. The PCF can send the new PCC rules, for example, to the SMF. The new set of RT latency requirements, uplink delay information, and / or downlink delay information can be based on a set of values ​​that, for example, was (e.g., previously) provided by the AF. The PCF can send a notification to an AF, for example, to notify the AF that the new set of values ​​has been used.

[076] NW, for example, SMF, can be configured to determine QoS requirements. For example, NW can determine QoS requirements based on one or more attributes of the PDU set. NW, for example, SMF, can receive PSDB information. PSDB information can be received from a PCF. PSDB information can be used to determine a PSDB for a PDU set. PSDB information can include a PSDB determination rule that, for example, maps traffic characteristics to a PSDB. At least one of the characteristics can be related to the size of a PDU set.

[077] The NW, for example, the SMF, can use the PSDB information to build N4 rules and / or send the N4 rules. The NW can send the N4 rules to the UPF. The N4 rules can include packet detection rules. The N4 rules can indicate, for example, to the UPF that sets of PDUs that match a first packet detection rule and / or are smaller than a certain size should be assigned to a first QoS flow. Additionally, or alternatively, the N4 rules can indicate that sets of PDUs that match the first packet detection rule (e.g., the same rule) and / or are greater than or equal to a certain size should be assigned to a second QoS flow. Size information can be included (e.g., integrated) in the packet detection rule. The NW, for example, the SMF, can use the PSDB information to build a QoS profile. The NW can send the profile. Petition 870250090043, dated 02 / 10 / 2025, page 41 / 81 31 / 52 of QoS, for example, for the RAN. The QoS profile can indicate, for example, for the RAN, that sets of PDUs from a first QoS stream that are smaller than a certain size should first be associated with a PSDB. Furthermore, or alternatively, the QoS profile can indicate, for example, for the RAN, that sets of PDUs from the first QoS stream (e.g., the same QoS stream) and / or are larger than or equal to the same determined size should be associated with a second PSDB.

[078] The NW, for example, the SMF, can use the PSDB information to build QoS rules. The NW can send the QoS rules, for example, to the WTRU. The SMF can send a QoS rule indicating (e.g., to the WTRU) that sets of PDUs that match a first packet detection and / or filter rule, and / or are smaller than a certain size (e.g., a threshold), should be assigned to a first QoS flow. The SMF can send an indication (e.g., to the WTRU) that sets of PDUs that match the first packet detection and / or filter rule (e.g., the same filter) and / or are greater than or equal to a certain size (e.g., a threshold), should be assigned to a second QoS flow. The indication can be sent as part of the indicated QoS rule and / or as a new QoS rule. Size information can be included (e.g., integrated) in the packet detection and / or filter rule.

[079] The PSDB determination rule and / or the QoS profile may indicate that any set of PDUs whose size is less than or equal to a first value may have a PSDB of a second value. The PSDB determination rule may indicate that any set of PDUs whose size is greater than the first value has a PSDB of a third value. The N4 rule and / or the QoS rule may indicate that a (e.g., any) set of PDUs whose size is less than or equal to a first value should be assigned to a first QoS stream. The determination rule Petition 870250090043, dated 02 / 10 / 2025, p. 42 / 81 32 / 52 PSDB can indicate that a (for example, any) set of PDUs whose size is greater than the first value should be assigned to a second QoS flow. The PSDB determination rule and / or QoS profile can include any number of mappings from PDU set size to PSDB. The N4 rule and / or QoS rule can include any number of mappings from PDU set size to QoS flow. The PDU set size in one or more of the PSDB determination rules, QoS profile, N4 rule, and / or QoS rule can be expressed as the total number of bytes in the PDU set and / or the total number of PDUs in the PDU set. The PSDB determination rule and / or QoS profile can indicate a time value (e.g., unique). The SMF and / or RAN can determine the PSDB, for example, by multiplying the PDU set size by the time value.For example, the time value can be multiplied by the number of PDUs in the PDU set and / or by the number of bytes in the PDU set. The PSDB determination rule can be included in the N4 rule and / or QoS rule. The PSDB determination rule can be a standalone rule.

[080] The WTRU can be configured to determine a QoS flow assignment, for example, based on one or more attributes of the PDU set. The WTRU can receive QoS rules, for example, from the SMF. The QoS rule can indicate (for example, to the WTRU) that PDU sets that match a first packet detection and / or filter rule, and / or are smaller than a certain size, should be assigned to a first QoS flow. Additionally, or alternatively, the QoS rule can indicate that PDU sets that match the first packet detection and / or filter rule (for example, the same filter) and / or are greater than or equal to a certain size should be assigned to a second QoS flow. Size information can also be integrated into the packet detection and / or filter rule. Petition 870250090043, dated 02 / 10 / 2025, p. 43 / 81 33 / 52

[081] A WTRU can assign PDUs from sets of PDUs to QoS flows, for example, based on size information in the received QoS rule. The QoS rule can indicate that any set of PDUs whose size is less than or equal to a first value should be assigned to a first QoS flow. Additionally, or alternatively, the QoS rule can indicate that any set of PDUs whose size is greater than the first value should be assigned to a second QoS flow. The QoS rule can include a number (e.g., any) of mappings from PDU set size to QoS flow.

[082] The network area network (NW) can be configured with a PSDB. The network, for example, an AF, can provide PDU set-related assistance information for dynamic PCC control. The PDU set-related assistance information can include one or more parameters. A parameter can be included in the PDU set QoS parameters. A parameter can include the PDU set delay budget. The PDU set delay budget (PSDB) can correspond to a maximum (e.g., limit) for a delay. The delay can be a delay that a PDU set can experience in the transfer between the WTRU and an N6 termination point, for example, at the UPF.The delay can include the duration between the moment the first PDU is received (e.g., at the N6 termination point for DL ​​and / or at the WTRU for UL) and the moment when all PDUs in a set of PDUs have been successfully received (e.g., at the WTRU for DL ​​or at the N6 termination point for UL). PSDB can be applied to one or more sets of DL PDUs received by the UPF from the PDU session anchor (PSA) via the N6 interface and / or to the set of UL PDUs sent by the WTRU. PSDB can override the packet delay budget (PDB), for example, when PSDB is available.

[083] NW can be configured with uplink and / or downlink policy control, for example, for XRM services. NW can Petition 870250090043, dated 02 / 10 / 2025, p. 44 / 81 34 / 52 can be configured with uplink and / or downlink policy control (e.g., for XRM services) based on round-trip (RT) latency. An RT latency indication may indicate that the service data flow needs to meet the service's RT latency requirement. The RT latency requirement may be twice a one-way delay requirement between the WTRU and the PSA UPF, for example, described by a QoS reference parameter and / or individual QoS parameter.

[084] Enhancements in a 5G system may enable policy control, for example, based on a round-trip latency requirement. The AF may indicate, for example, to the PCF, that a UL flow and / or DL ​​flow needs to meet an RT latency requirement. The RT latency requirement may include a maximum (e.g., limit), for example, for the sum of the UL delay and the DL delay of a data flow between the WTRU and the N6 termination point, for example, at the UPF. The PCF may monitor the delay in the UL and / or DL ​​flows (e.g., both). The PCF may adjust the UL PDB and / or the DL PDB, for example, based on observed network performance.

[085] XRM traffic can be transported using PDU sets. The QoS flow may not be associated with any PDB, for example, when a QoS flow carries PDU sets. The QoS flow may be (for example, only) associated with the PSDB. For example, when PDU sets are transported in one direction of the flow, an associated flow in the other direction may not carry PDU sets. Downlink traffic may be based on PDU sets, for example, in some XRM scenarios. Additionally, or alternatively, the corresponding uplink traffic may correspond to a data flow that does not carry PDU sets. For example, when a user uses VR glasses and / or tactile gloves for an XRM service, the downlink traffic that is fed to the VR glasses and / or tactile gloves may be in the form of Petition 870250090043, dated 02 / 10 / 2025, page 45 / 81 35 / 52 sets of PDUs (e.g., sets of PDUs for a video modality). Uplink traffic may carry posture information, for example, to inform the application server about the user's posture and / or haptic feedback. Posture information and / or haptic feedback may not be carried using sets of PDUs (e.g., using common PDUs). A downlink flow may carry sets of PDUs, and / or an uplink flow (e.g., associated) may carry acknowledgments and / or haptic feedback (e.g., traffic that is not carried in sets of PDUs). A margin (e.g., extra) may be added to the UL PDB, for example, when the DL traffic delay is below the PSDB. A margin (e.g., extra) may be added to the downlink PSDB, for example, when the uplink traffic delay is below the PDB.

[086] The system should not (e.g., always) assume that (e.g., all) the uplink delay margin must be added to the downlink PSDB. For example, some or no uplink delay margin may be added to the downlink PSDB. Downlink traffic may carry updated scene information and / or uplink traffic may carry acknowledgments of updated scene information. There may be a reduction in the quality of the user experience, for example, when the user may perceive a delay in viewing scene changes due to the delay in receiving updated scene information. The quality of the experience may degrade, for example, when the round-trip delay is evenly distributed between an uplink flow and a downlink flow.

[087] The XRM application service provider can be configured with / learn combinations (e.g., efficient) of UL / DL delays, for example, if the XRM application service provider is exposed to detailed information. Petition 870250090043, dated 02 / 10 / 2025, pp. 46 / 81 36 / 52 regarding uplink and / or downlink delays. The XRM application service provider can configure (e.g., customize) the UL / DL configuration, for example, to better suit the XRM application. Additionally, or alternatively, XRM traffic may include more than one uplink and / or downlink flow, for example, for each mode and / or for the same mode. UL / DL granularity can help the application provider adjust requirements across multiple flows. Round-trip delay measurements, for example, based on measuring the delay associated with individual packets, may not be sufficient. For example, RT delay measurements based on measuring the delay associated with individual packets may not be sufficient when sets of PDUs are sent in uplink and / or downlink directions.Enhancements to the 5G system are provided here, for example, where AF can configure an RT latency requirement for an uplink and / or downlink stream (e.g., combination). The uplink and / or downlink stream can carry sets of PDUs. AF can measure the delays associated with the stream combinations. AF can adjust the PSDB and / or PDB of a stream, for example, based on configuration information and / or measurement information.

[088] Some applications may (for example, need to) control latency for (for example, a combination of) more than one uplink and / or downlink stream. The time and / or quality of experience (QoE) for an application, for example, may depend on the combination of two downlink media streams and one uplink data stream. The systems and procedures described herein, for example, for a UL stream and a DL stream, may be used to enable AF (for example, to support such cases). The procedures described herein may specify UL and / or DL ​​delays for three or Petition 870250090043, dated 02 / 10 / 2025, page 47 / 81 37 / 52 more flows, for example, so that the combination of delays provides the round-trip time (RTT) needed for the application traffic.

[089] A 5G system can allow an AF to provide a PDU set delay budget (PSDB), for example, to the 5GC. The 5GC can associate the PSDB with a QoS flow. Associating the PSDB with a QoS flow can correspond to PCF using the PSDB to construct a PCC rule that can be sent to the SMF and / or the SMF can send the PSDB to the NG-RAN, for example, as part of the QoS profile. The 5G system can support enhancements that take into account the variation in the size of PDU sets in an application layer session (e.g., a Real-Time Transport Protocol (RTP) session). A single PSDB configured for a session may not be sufficient, for example, when the size of the PDU sets in an application layer session (e.g., an RTP session) can vary.PSDB can be set with a value large enough to accommodate the largest expected set of PDUs that may be sent in an application layer session, for example, when a single PSDB is provided. The 5G system, including NG-RAN, for example, can assume the same PSDB value (for example, even when dealing with relatively small sets of PDUs from the same application layer session). The 5G system can allow a very large delay when dealing with relatively small sets of PDUs, for example, when assuming the same PSDB value.

[090] NW can be configured to provision a set(s) of PDUs aware of the round-trip latency requirement on 5GS. Figure 2 illustrates an example procedure 200 for configuring multimodal requirements. Example procedure 200 may correspond to an application function requesting configuration requirements for a multimodal XRM session with a WTRU 202 via 5GS and / or providing requirements related to round-trip latency. A process may include configuring 5GS with requirements related to Petition 870250090043, dated 02 / 10 / 2025, pp. 48 / 81 38 / 52 round-trip latency, for example, to handle multimodal traffic between an application server and the WTRU.

[091] In 218, the NW, for example, an AF 216, can request the configuration of a multimodal session, for example, with WTRU 202 (e.g., via 5GS). The AF 216 can request the multimodal session configuration by invoking an application programming interface (API) NEF 214. The NEF 214 API can be based on (e.g., modeled from) an Nnef_AFsessionWithQoS service operation. In the request, for example, the AF 216 can provide service information. The service information can include one or more flow description information, a WTRU address, and / or a DNN / S-NSSAI combination. AF 216 can provide, for example, in the request, service requirements related to multimodal service, including a QoS monitoring requirement and / or QoS parameters. QoS parameters may include one or more packet delay budgets (e.g., for each mode) and / or flow.AF 216 can provide PDU-defined QoS parameters, for example, in the request. QoS parameters can include one or more PDU-defined delay budgets (e.g., for each mode) and / or flow.

[092] AF 216 can provide RT latency requirements, for example, for the XRM service. RT latency requirements may include one or more RT latency requirements, a maximum UL delay, and / or a maximum DL delay. The RT latency requirement may represent a maximum limit, for example, for the sum of the UL delay and the DL delay of a data stream between the WTRU and the N6 termination point (e.g., at the UPF). The maximum UL delay (e.g., limit) may represent a maximum UL PDB and / or a maximum UL PSDB. Alternatively, or additionally, the maximum UL delay may indicate a percentage that, for example, represents the maximum percentage of the RT latency requirement that can be applied to UL traffic. The percentage that represents Petition 870250090043, dated 02 / 10 / 2025, p. 49 / 81 39 / 52 The maximum RT latency requirement percentage may change over time. AF 216 can provide a time window for when the percentage is valid. AF 216 can provide different percentages with a time window for each percentage. The maximum DL delay (e.g., limit) may correspond to a maximum DL PDB or a maximum DL PSDB. Alternatively, or additionally, the maximum DL delay may indicate a percentage representing the maximum RT latency requirement percentage that, for example, may be applied to DL traffic. The percentage representing the maximum RT latency requirement percentage may change over time. Thus, AF 216 can provide a time window for when the percentage is valid. AF 216 can provide different percentages with a time window for each percentage.

[093] The AF 216 can provide multiple sets of RT latency, maximum UL delay, and / or maximum DL delay. A PCF 212 can choose the combination of RT latency, maximum UL delay, and / or maximum DL delay to apply. The PCF 212's decision on which combination of RT latency, maximum UL delay, and / or maximum DL delay to apply can be based on measurement reports, for example, that the PCF 212 receives. The measurement reports may relate to the delay measured on the associated uplink and / or downlink paths.

[094] Providing maximum UL delay and / or maximum DL delay, in addition to or as an alternative to providing an RT latency requirement, can be advantageous, for example, when UL and / or DL ​​flows carry sets of PDUs. Maximum UL delay and / or maximum DL delay can be used by PCF 212, for example, to limit increases in UL and / or DL ​​delay budgets. NW can limit how RT latency is split between uplink and downlink flows. Petition 870250090043, dated 02 / 10 / 2025, pp. 50 / 81 40 / 52

[095] AF 216 can provide a set of QoS parameters, for example, for different configurations for a (e.g., specific) modality. AF 216 can identify the different modalities (e.g., identified by their traffic descriptors), for example, with a multimodal service ID. For example, for a video modality, the AS can expect a certain value for frame rates and / or provide QoS parameters for each frame rate value. AF 216 can provide RT latency requirements, for example, for one or more configurations. A set of QoS requirements and parameters can be indexed by a specific integer value. By indexing the set of QoS requirements and parameters by a specific integer value, for example, 5GS and the AS can communicate more easily.For example, the AS and the 5GS can communicate to determine (e.g., select) a configuration for the XRM traffic mode (e.g., different index for different frame rate). The mode configuration can change, for example, due to a request from the AF and / or due to changes in network conditions. The 5GS can determine (e.g., relevant) RT latency requirements, for example, using the index of a (e.g., new) configuration (e.g., the configuration in use). The AF 216 can provide a multimodal service ID, for example, when the AF 216 provides the RT latency requirements. The multimodal service ID can be an identifier that associates multimodal flows, for example, belonging to the same multimodal service. The AF 216 can provide a packet detection rule identifier, for example, when the AF 216 meets the RT latency requirements.The packet detection rule identifier can, for example, be used by the network to detect which traffic applies to the rules.

[096] In 220, the NW, for example, NEF 214, can authorize the AF 216 request. In 222, the NW (for example, NEF 214) can send a policy authorization request, for example, to a PCF 212. The NW (for example, NEF Petition 870250090043, dated 02 / 10 / 2025, pp. 51 / 81 41 / 52 214) can send information, for example, provided by AF 216 (e.g., in 218), to PCF 212. The information may include one or more of the RT latency requirements, traffic flow descriptors, WTRU address, and / or multimodal service ID. NEF 214 may alternatively or additionally send a list of RT latency requirements (e.g., alternative). NEF 214 can send information to PCF 212 by invoking the PCF 212 Npcf_PolicyAuthorization service creation and / or update operation.

[097] In 224, the NW, for example, PCF 212, can authorize the request. In 224, PCF 212 can additionally or alternatively generate one or more policies, for example, for multimodal service (e.g., PCC rules). For RT latency requirements, for example, PCF 212 can generate two PCC rules. One PCC rule can be related to an uplink flow and / or another PCC rule can be related to a downlink flow. The uplink flow can be associated with the downlink flow. For example, the uplink flow can be associated with a PDB and / or the downlink flow can be associated with a PSDB.

[098] PCF 212 can use RT latency requirements (e.g., RT latency requirement, maximum UL delay, and / or maximum DL delay) to (e.g., initially) assign PCC rules to uplink and / or downlink flows. PCF 212 can create PCC rules, for example, when the maximum UL delay is greater than the maximum DL delay. The PCC rules can be such that the PDB associated with the uplink flow is greater than the PSDB associated with the downlink flow. Additionally, or alternatively, the PCC rules can specify that the sum of the UL PDB and the DL PDSB must be less than or equal to the RT latency requirement.

[099] PCF 212 can generate QoS monitoring rules for UL data traffic and / or DL ​​PDU cluster traffic, for example, to track latency. Petition 870250090043, dated 02 / 10 / 2025, p. 52 / 81 42 / 52 RT. PCF 212 can associate (for example, two) QoS monitoring rules to (for example, using) a common identifier. The common identifier can include a multimodal Service ID.

[0100] On 226, the NW, for example, PCF212, can send a policy authorization response, for example, to NEF 214. NEF 214 can receive the policy authorization response, for example, via the Npcf_PolicyAuthorization creation response message from PCF 212. The NW (e.g., NEF 214) can send (e.g., forward) the PCF 212 response to AF 216. On 230, the NW, for example, PCF 212, can send PCC rules, for example, to an SMF 210. On 232, the SMF 210 can send N4 rules to a UPF 208. On 234, the NW, for example, SMF 210, can send QoS rules, for example, to WTRU 202. The SMF 210 can send QoS profiles to RAN 204. PCF 212 can generate correlated QoS monitoring policies for the UL data stream and / or DL ​​PDU set.

[0101] The NW can be configured for behavior using QoS monitoring reports for RT latency. Figure 3 illustrates an example procedure 300 for configuring QoS monitoring. Systems and procedures can, for example, correspond to when a multimodal service has been established between an AF 316 and the WTRU 302 (e.g., with the RT latency requirement provisioned). Systems and procedures describe a monitoring aspect related to measuring RT latency and / or NW and application behavior, for example, as a result of QoS delay monitoring reports.

[0102] In 318, the NW (e.g., an AF 316) can request a session, for example, with specific requirements, for the multimodal service. The AF 316 can request the session, for example, using a procedure such as the one described here (e.g., as in Figure 2). The session (e.g., request) can be to establish and / or configure policies for an XRM service. In 320, one or more Petition 870250090043, dated 02 / 10 / 2025, pp. 53 / 81 43 / 52 policies for XRM traffic and QoS profiles, QoS rules and / or N4 rules can be established. Additionally, or alternatively, QoS monitoring for UL data and / or delay defined by the PDU DL can be established, for example, for RT latency tracking. The WTRU 302 and the application server can exchange XRM traffic, for example, through the user plane.

[0103] In 322, the NW, for example, UPF 308, can (for example, start to) perform QoS monitoring, for example, after the connection is established in the user plane and / or traffic is exchanged between WTRU 302 and AF 316. UPF 308 can perform QoS monitoring, for example, for RT latency-related delay measurement. UPF 308 can perform QoS monitoring for RT latency-related delay measurement based on a QoS monitoring policy, for example, generated by PCF 312. In the uplink direction, for example, UPF 308 can monitor the UL data packet delay between WTRU 302 and termination point N6. In the downlink direction, for example, the UPF 308 (e.g., with the aid of the NG-RAN 304 and / or the WTRU 302) can monitor the delay defined by the DL PDU between the N6 termination and the WTRU 302.The (e.g., two) monitoring procedures for the uplink direction and / or the downlink direction can be performed at similar times (e.g., the same). Performing (e.g., two) of the monitoring procedures at similar times can allow the UPF 208 to measure the round-trip latency of interest. The round-trip latency of interest can be the sum of the measurement delay of the uplink and the downlink.

[0104] In 324, NW, for example, UPF 308, it can report QoS monitoring results (e.g., for SMF 310). Monitoring results may include one or more UL packet delay measurements, the delay measurement defined by the DL PDU, and / or the sum of both delays (by Petition 870250090043, dated 02 / 10 / 2025, pp. 54 / 81 44 / 52 example, RT latency measurement). In 326, the NW, for example, SMF 310, can send a notification, for example, to PCF 312. For example, SMF 310 can send a notification to PCF 312 if the UL packet delay measurement and / or the downlink PDU-defined delay measurement are not within an acceptable range.

[0105] In 328, the NW, for example, PCF 312, can adjust policies with (e.g., new) PDB and / or PSDB rules; and / or update rules, for example, when the NW (e.g., the PCF) detects that the PDB and / or PSDB of a flow is not being met and / or the flow is associated with RT latency requirements. For example, when the NW (e.g., PCF 312) detects that the PDB and / or PSDB of a flow is not being met and / or the flow is associated with RT latency requirements, the PCF can calculate (e.g., new) delay budget values ​​for the uplink and / or downlink directions. PCF 312 can determine a (e.g., new) PSDB for the downlink flow and / or a (e.g., new) PDB for the uplink flow.For example, when PCF determines that the UL PDB is not being met and / or the DL PDSB is being met, PCF 312 may increase the packet delay budget for the uplink flow and / or reduce the packet-defined delay budget for the downlink flow. PCF 312 may additionally or alternatively maintain one or more UL PDBs lower than the maximum UL delay, DL PSDBs lower than the maximum DL delay, and / or the sum of the UL PDB and DL PSDB lower than the RT latency requirement. PCF 312 may use the RT latency requirements (e.g., the RT latency requirements of procedure 200), for example, to determine delay budget values ​​(e.g., new ones). PCF 312 may generate (e.g., new) PCC rules for (e.g., both) uplink and / or downlink directions. The PCF 312 can configure the uplink flow to use one. Petition 870250090043, dated 02 / 10 / 2025, pp. 55 / 81 45 / 52 PCC rule (e.g., new) and / or configure the downlink flow to use a PCC rule (e.g., new).

[0106] PCF 312 may determine that PCF 312 cannot increase the delay allocated to a flow whose PDB or PSDB is not being met, for example, when the NW (e.g., PCF) detects that the PDB and / or PSDB of a flow are not being met and / or the flow is associated with RT latency requirements. Additionally, or alternatively, PCF 312 may notify AF 316 that QoS requirements cannot be met. For example, PCF 312 may determine that increasing the delay (e.g., more than this) may violate the maximum delay requirement of the UL and / or the maximum delay requirement of the DL (e.g., the maximum delay requirement of the UL and / or the maximum delay requirement of the DL of procedure 200). PCF 312 can notify AF 316 that QoS requirements cannot be met, for example, when PCF 312 determines that it cannot increase the delay budget allocated to the flow whose PDB and / or PSDB is not being met.The AF 316 can adjust application layer settings (e.g., a codec setting) and / or adjust QoS requirements, for example, by resetting the installation and / or configuration of policies for the XRM service (e.g., as described in procedure 200) (e.g., to provide a new QoS configuration).

[0107] In 330 the NW, for example PCF 312, can generate rules (e.g., N4 rules), for example based on PCC rules. In 330, PCF 312 can additionally or alternatively send (e.g., forward) the updated PCC rules (e.g., a pair of) rules, for example, to SMF 310. SMF 310 can send (e.g., forward) the N4 rules, for example, to UPF 308. In 332, the NW, for example PCF 312, can send (e.g., forward) the updated QoS rules (e.g., to WTRU 302) and / or the Petition 870250090043, dated 02 / 10 / 2025, pp. 56 / 81 46 / 52 pair of updated QoS profiles (e.g., for RAN 304), via AMF 306.

[0108] In 334, the NW, for example, PCF 312, can send (e.g., provide) an informational notification, for example, to AF 316 (e.g., via NEF 314). PCF 312 can determine the PSDB value index (e.g., newly selected) (e.g., after an update), for example, when AF 316 has provided PSDB requirements (e.g., alternative) and / or RT latency requirements. PCF 312 can send the determined index, for example, to AF 316. In 336, AF 316 can determine which setting for the mode to use, for example, using the determined index. Additionally, or alternatively, in 336, AF 316 can adjust a codec setting, change a setting, and / or provide (e.g., new) RT requirements. The setting may include a codec setting, for example, for a video mode.

[0109] PCF 312 can inform AF 316 about the new delay requirement pair that is selected for UL and / or DL, for example, when PCF 312 has not received PSDB values ​​(e.g., alternative), for example, from AF 316. The delay requirements for UL and / or DL ​​can be determined and / or selected to (e.g., continue to) meet the RT latency requirement, for example, provided by AF 316. In 336, AF 316 can use the delay requirement pair information (e.g., internally), for example, to change one or more application parameters. The DL PSDB and / or UL PDB values ​​sent to AF 316 may not be indexed by 5GS, for example, if no alternative value is provided (e.g., previously) by AF 316. PCF 312 may inform AF 316 that the RT delay measurement exceeds the requirement, for example, when the RT delay requirement cannot be met. PCF 312 may provide the new RT measurement, for example, to AF 316.The AF 316 can provide (for example, new) RT measurement. Additionally, or alternatively, the AF 316 can provide... Petition 870250090043, dated 02 / 10 / 2025, pp. 57 / 81 47 / 52 one or more of the following: DL PDU adjustment delay, measured UL PDU delay, and / or an indication that the uplink delay and / or downlink delay cannot be met. In 336, AF 316 can use the information provided to evaluate and / or change the internal configuration of AF 316. For example, AF 316 can change the internal configuration based on the new codec. AF 316 can provide 5GS / PCF 312 (e.g., new) RT latency requirements.

[0110] On 338, the NW, for example, AF 316, can respond to the PCF message. For example, AF 316 can respond to the PCF message by changing application-level information. AF 316 can change application-level information, including codec configuration, for example, according to the PSDB DL index provided (e.g., on 334) by PCF 312. AF 316 can exchange XRM traffic with WTRU 302 on the user plane, for example, using the new codec configuration. AF 316 can confirm the change, for example, to PCF 312 (e.g., via NEF 314).

[0111] AF 316 can respond to the PCF message by re-evaluating the RT latency requirement provided to 5GS. AF 316 can provide an RT latency requirement (e.g., new) to PCF 312, for example, via NEF 314. PCF 312 can use the RT latency requirement and / or one or more other parameters to derive (e.g., new) PCC rules. For example, PCF 312 can use the RT latency requirement and / or one or more other parameters to derive new PCC rules. The (e.g., new) PCC rules can include one or more PCC rules with UL PDB and / or other PCC rules with DL PSDB for the XRM service.

[0112] AF 316 may determine that an acceptable user experience may not be supported by WTRU 302 under the given network conditions and / or may not respond to the PCF message appropriately. For example, AF 316 may Petition 870250090043, dated 02 / 10 / 2025, pp. 58 / 81 48 / 52 inform the user about such an event. AF 316 can trigger WTRU 302 to terminate the user's plan change, for example, to the XRM service.

[0113] NW can be optimized to handle varying sizes of PDU sets. AF 316 can invoke an NEF 314 API, for example, to provide the 5GC with information about the PSDB requirements of an application layer session. The application layer session can be used to send and / or receive PDU sets of varying sizes. For example, the NEF 314 API can include the Nnef_AFsessionWithQoS_Create and / or Nnef_AFsessionWithQoS_Update service operations. The procedure for invoking the NEF 314 API may include the same steps or steps similar to those described here, for example, as in Figure 2. The AF 316 can use the API to provide QoS parameters for the PDU set and / or a protocol description of a service data flow, for example, to the NEF 314. The protocol description may indicate a protocol and / or payload type, for example, used by the service data flow. The PDU set QoS parameters may include PSDB information.

[0114] PSDB information may include a rule. Additionally, or alternatively, PSDB information may include a threshold (e.g., size). Size and threshold may be used interchangeably here. The rule may be used by the 5GC to associate PDU set sizes with a PSDB value. For example, the rule may indicate that any PDU set whose size is less than or equal to a first value (e.g., threshold) has a PSDB of a second value. The rule may indicate that any PDU set whose size is greater than the first value (e.g., threshold) has a PSDB of a third value. The rule may include any number of PDU set size to PSDB mappings. The PDU set size may be expressed as the total number of bytes in the PDU set and / or the total number of PDUs in the PDU set. Additionally, or alternatively, the rule may indicate a time value (e.g., Petition 870250090043, dated 02 / 10 / 2025, pp. 59 / 81 49 / 52 example, unique). The NW can determine the PSDB, for example, by multiplying the size of the PDU set by the time value. The time value can be multiplied by the number of PDUs in the PDU set and / or by the number of bytes in the PDU set. Additionally, or alternatively, the rule can indicate a first value and / or range of values, for example, for an attribute of a PDU set. Additionally, or alternatively, the rule can indicate that any PDU set with an attribute value equal to the first value and / or within the range has a PSDB of a second value. The PDU set attribute can include one or more associations to the Layer 0 ID, payload independence from other PDU sets for decoding, payload dependence on other PDU sets for decoding, and / or a PDU set with importance 1.The attribute can be specified using an ID (e.g., independent PDU set, PDU set layer ID, importance, and / or etc.). The rule can include any attribute and / or value in the PSDB mappings. NW can determine the PSDB (e.g., first) by obtaining the attribute value (e.g., by parsing the transport headers of the PDUs) and / or by querying the attribute and / or value in the mapping(s).

[0115] NEF 314 can provide the rule to PCF 312. PCF 312 can send the rule to SMF 310, for example, as part of the PCC rules. SMF 310 can include rule information in N4 rules which, for example, can be sent by SMF 310 to UPF 308. For example, SMF 310 can send an N4 rule. The N4 rule can indicate (for example, to UPF 308) that sets of PDUs that match a first packet detection rule and / or are smaller than a certain size should be assigned to a first QoS flow. Additionally, or alternatively, the N4 rule can indicate (for example, to UPF 308) that sets of PDUs that match the first packet detection rule (for example, the same rule) and / or are greater than or equal to the same Petition 870250090043, dated 02 / 10 / 2025, pp. 60 / 81 50 / 52 specific size must be assigned to a second QoS flow. The set of PDUs, the PDU, and / or the packet may include information, for example, in a header. The information can be used to identify the traffic, for example, to which the packet belongs. If the information (e.g., in the header) matches and / or includes at least some of the same information as the information elements of a rule (e.g., packet detection rule (PDR)), it can be determined that the packet matches the PDR. The PDR may include information elements that can help identify the traffic and / or packets that belong to a particular traffic. Size information can be integrated into the packet detection rule.

[0116] The SMF 310 can include rule information in QoS profiles, for example, which are sent by the SMF 310 to the RAN 304. For example, the SMF 310 can send a QoS profile that indicates to the RAN 304 which sets of PDUs from a first QoS stream that are less than (e.g., have sizes less than) a certain size (e.g., a limit) should be associated with a first PSDB and / or which sets of PDUs from the first QoS stream (e.g., the same QoS stream) that are greater than or equal to (e.g., have sizes greater than or equal to) a certain size (e.g., a limit) should be associated with a second PSDB. The SMF 310 can send a QoS profile that indicates to the RAN 304 which sets of PDUs from a first QoS stream associated with certain values ​​and / or attribute ranges of PDU sets should be associated with a first PSDB.Additionally, or alternatively, the QoS profile may indicate that sets of PDUs from a first QoS stream (e.g., the same QoS stream) associated with other attribute values ​​and / or ranges of PDU sets should be associated with a second PSDB. To enable this association, for example, UPF 308 may define attribute values ​​in the GTP-U headers of the GTP-U packet used to transport PDUs from the PDU set. Petition 870250090043, dated 02 / 10 / 2025, pp. 61 / 81 51 / 52 Examples of General Packet Radio Service Tunneling Protocol (GTP-U) user plane header information elements (IEs) for attribute values ​​may include existing IEs, such as the importance of the PDU set. Examples of GTP-U header IEs for attribute values ​​may include one or more new IEs: independent PDU set (e.g., 0 means dependent, 1 independent), a layer ID (e.g., indicating the PDU payload decoding layer), and / or a base layer (e.g., 1 means the PDU payload contains a base layer for decoding, while 0 means it does not).

[0117] Note that providing rule information for UPF and RAN may be an alternative option. Additionally, or alternatively, the SMF 310 can include rule information in the QoS rules, for example, those sent by the SMF 310 to the WTRU 302. For example, the SMF 310 can send a QoS rule indicating (for example, to the WTRU 302) that sets of PDUs that match a first packet detection and / or filter rule, and / or are smaller than a certain size and / or match a certain attribute value / range, should be assigned to a first QoS stream. Alternatively, the QoS rule can indicate that sets of PDUs that match the first packet detection and / or filter rule (for example, the same filter), and / or are greater than or equal to a certain size and / or match another attribute value / range, should be assigned to a second QoS stream.Size information and / or attribute value can be integrated into packet detection and / or filtering rules.

[0118] Although the features and elements are described above in specific combinations, an expert in the field will understand that each feature or element can be used alone or in any combination with the other features and elements. Furthermore, the methods described herein may Petition 870250090043, dated 02 / 10 / 2025, pp. 62 / 81 52 / 52 can be implemented in a computer program, software, or firmware embedded in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROMs and digital versatile discs (DVDs). A processor in conjunction with software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer. Petition 870250090043, dated 02 / 10 / 2025, pp. 63 / 81

Claims

1 / 5 CLAIMS 1. Network entity, CHARACTERIZED in that it comprises: a processor configured to: receive a message containing round-trip (RT) latency requirements, wherein the RT latency requirements comprise uplink delay information and downlink delay information; generate initial billing and control policy (PCC) rules based on the uplink delay information and downlink delay information; send initial information indicating the initial PCC rules to a session management function (SMF); receive a notification that one or more of an uplink delay or a downlink delay is associated with a flow; determine the second PCC rules based on one or more of the uplink delay or the downlink delay; and send second information indicating the second PCC rules to the SMF.

2. Network entity, according to claim 1, CHARACTERIZED in that the notification is a first notification and in that the processor is additionally configured to send a second notification to an application function (AF), wherein the second notification includes an indication that PCC rules that meet one or more RT latency requirements, uplink delay information or downlink delay information cannot be generated.

3. Network entity, according to claim 1, CHARACTERIZED in that the RT latency requirements comprise the first RT latency requirements, the uplink delay information comprises the first uplink delay information and the downlink delay information comprises the first downlink delay information, and wherein the processor is additionally configured to: determine the second RT latency requirements, comprising the second uplink delay information and the second downlink delay information; determine the third PCC rules based on the second RT latency requirements; and send the third PCC rules to the SMF.

4. Network entity, according to claim 1, CHARACTERIZED in that the uplink delay information comprises an indication of one or more of an uplink maximum packet delay budget (PDB) or an uplink maximum protocol data unit (PDU) defined delay budget (PSDB), and in that the downlink delay information comprises an indication of one or more of a downlink maximum PDB or a downlink maximum PSDB.

5. Network entity, according to claim 4, CHARACTERIZED in that one or more of the maximum downlink PDB or maximum downlink PSDB of the uplink delay information are different from one or more of the maximum downlink PDB or maximum downlink PSDB of the downlink delay information.

6. Network entity, according to claim 1, CHARACTERIZED in that the message comprises one or more of a multimodal service identifier (ID) or one or more traffic descriptors. Petition 870250090043, dated 10 / 02 / 2025, pp. 78 / 81 3 / 5 7. Network entity according to claim 1, CHARACTERIZED in that the network entity comprises a policy control function (PCF).

8. Network entity, according to claim 1, CHARACTERIZED in that the notification comprises an indication that one or more of the uplink delay or downlink delay associated with the flow is not within the range required by the first PCC rules.

9. Network entity, according to claim 1, CHARACTERIZED in that the processor is additionally configured to generate N4 rules based on the second PCC rules.

10. Network entity, according to claim 1, CHARACTERIZED in that the flow associated with one or more of the uplink delay or downlink delay is additionally associated with one or more of the first PCC rules or the second PCC rules.

11. A method executed by at least one network entity, the method CHARACTERIZED by the fact that it comprises: receiving a message comprising round-trip (RT) latency requirements, wherein the RT latency requirements comprise uplink delay information and downlink delay information; generating initial billing and control policy (PCC) rules based on the uplink delay information and the downlink delay information; sending initial information indicating the initial PCC rules to a session management function (SMF); receiving a notification that one or more of an uplink delay or a downlink delay is associated with a flow; Petition 870250090043, dated 10 / 02 / 2025, p.79 / 81 4 / 5 determine second PCC rules based on one or more of the uplink delay or downlink delay; and send second information indicating the second PCC rules to the SMF.

12. Method according to claim 11, CHARACTERIZED in that the notification is a first notification and in that the method further comprises sending a second notification to an application function (AF), wherein the second notification includes an indication that PCC rules that meet one or more of the RT latency requirements, uplink delay information or downlink delay information cannot be generated.

13. A method according to claim 11, characterized in that the RT latency requirements comprise the first RT latency requirements, the uplink delay information comprises the first uplink delay information, and the downlink delay information comprises the first downlink delay information, and wherein the method further comprises: determining second RT latency requirements, comprising the second uplink delay information and the second downlink delay information; determining third PCC rules based on the second RT latency requirements; and sending the third PCC rules to the SMF.

14. Method according to claim 11, CHARACTERIZED in that the uplink delay information comprises an indication of one or more of a maximum uplink packet delay budget (PDB) or a maximum uplink protocol data unit (PDU) defined delay budget (PSDB), and wherein the downlink delay information comprises an indication of one or more of a maximum downlink PDB or a maximum downlink PSDB.

15. Method, according to claim 14, CHARACTERIZED in that one or more of the maximum downlink PDB or maximum downlink PSDB of the uplink delay information are different from one or more of the maximum downlink PDB or maximum downlink PSDB of the downlink delay information.

16. Method according to claim 11, CHARACTERIZED in that the message comprises one or more of a multimodal service identifier (ID) or one or more traffic descriptors.

17. Method according to claim 11, CHARACTERIZED in that the network entity comprises a policy control function (PCF).

18. Method, according to claim 11, CHARACTERIZED in that the notification comprises an indication that one or more of the uplink delay or downlink delay associated with the flow is not within the range required by the first CCP rules.

19. Method, according to claim 11, CHARACTERIZED in that it further comprises the generation of N4 rules based on the second CCP rules.

20. Method according to claim 11, CHARACTERIZED in that the flow associated with one or more of the uplink delay or downlink delay is additionally associated with one or more of the first PCC rules or the second PCC rules. Petition 870250090043, dated 10 / 02 / 2025, p. 81 / 81

Images