Method, architecture, apparatus, and system for multi-flow synchronization - Patents.com

The WTRU synchronizes multiple data flows in XR communications by adjusting resource configurations and transmission priorities, addressing unsynchronized data delivery issues and enhancing user experience in XR applications.

JP2024542122APending Publication Date: 2024-11-13INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024526763
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-04-27
Filing Date
2022-11-01
Publication Date
2024-11-13

AI Technical Summary

Technical Problem

Existing technologies face challenges in synchronizing multiple data flows in extended reality (XR) communications, leading to potential delays and discomfort for users due to unsynchronized data delivery, which can cause motion sickness and poor user experience.

Method used

A wireless transmit/receive unit (WTRU) synchronizes multiple data flows by determining resource configurations and adjusting transmission priorities to ensure that inter-flow packet delay budgets are within expected time of arrival thresholds, using timers and priority levels to manage data transmission and reception.

Benefits of technology

This approach ensures that data flows are synchronized, meeting joint quality of service requirements, thereby improving the user experience in XR applications by reducing delays and discomfort.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024542122000001_ABST
    Figure 2024542122000001_ABST
Patent Text Reader

Abstract

Procedures, methods, architectures, apparatus, systems, devices, and computer program products are described for synchronization of multiple traffic flows of information, such as protocol data unit (PDU) flows associated with applications and / or services. In an example embodiment, a device may receive one or more forwarding configurations for use when transmitting data in the multiple flows. The forwarding configurations may effect synchronous transmission of the multiple flows such that a delay between a (e.g., last or latest) PDU in a first flow and a (e.g., last or latest) PDU in a second flow meets one or more parameters, such as different expected arrival time thresholds. In some embodiments, a PDU may be associated with an application data unit (ADU) in the first flow and an ADU in the second flow.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of (i) U.S. Provisional Patent Application No. 63 / 275,133, filed November 3, 2021, and (ii) U.S. Provisional Patent Application No. 63 / 335,285, filed April 27, 2022, each of which is incorporated by reference herein. Summary of the Invention [Problem to be solved by the invention]

[0002] The present disclosure is generally directed to the fields of communications, software, and coding, including methods, architectures, apparatus, and systems directed to ensuring synchronization of multiple data flows, such as, for example, multiple data flows associated with extended reality (XR) communications.

[0003] In certain representative embodiments, a wireless transmit / receive unit (WTRU) may determine a resource (e.g., transmission) configuration to use when transmitting and / or receiving multiple flows (e.g., in the uplink and / or downlink) to synchronize the transmissions. The multiple flows may be synchronized such that, for example, a delay between a (e.g., latest) protocol data unit (PDU) in a first flow and a (e.g., latest) PDU in a second flow is less than or equal to different expected time of arrival (ETA) thresholds, such as inter-flow packet delay budgets (PDBs). For example, the PDUs in the first and second flows may be received from either the WTRU, another WTRU, a base station, and / or an application and / or service (e.g., generating information in the payload of the PDU) executed by a network entity. [Brief description of the drawings]

[0004] A more detailed understanding may be had from the following detailed description, taken by way of example in conjunction with the accompanying drawings. Such drawing figures, like the detailed description, are examples. Thus, the figures and detailed description should not be considered as limiting, as other equally effective examples are possible and likely. Moreover, like reference numerals ("references") in the figures indicate like elements. [Figure 1A] FIG. 1A is a system diagram illustrating an example communication system. [Figure 1B] FIG. 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A. [Figure 1C] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A. [Figure 1D] FIG. 1D is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communications system illustrated in FIG. 1A. [Diagram 2] FIG. 2 is a system diagram illustrating an example of multi-flow synchronization that may be used within the communication systems described herein. [Diagram 3] FIG. 3 is a system diagram illustrating another example of multi-flow synchronization that may be used within the communication systems described herein. [Figure 4] FIG. 4 is a system diagram illustrating a further example of multi-flow synchronization that may be used within the communication systems described herein. [Diagram 5] FIG. 5 is a procedure diagram illustrating an exemplary procedure for synchronizing multiple flows. [Figure 6] FIG. 6 is a procedure diagram illustrating another exemplary procedure for synchronizing multiple flows. [Figure 7] FIG. 7 is a procedure diagram illustrating an exemplary procedure for synchronizing multiple flows. [Figure 8] FIG. 8 is a procedure diagram illustrating another exemplary procedure for synchronizing multiple flows. [Figure 9] FIG. 9 is a procedure diagram illustrating an example for transmitting multiple flows using priority levels. [Figure 10] FIG. 10 is a procedure diagram illustrating an example for receiving multiple flows using priority levels. [Figure 11] FIG. 11 is a procedure diagram illustrating an exemplary procedure for coordinating resource configuration information for synchronizing multiple flows. [Figure 12] FIG. 12 is a procedure diagram illustrating another exemplary procedure for coordinating resource configuration information for synchronizing multiple flows. [Figure 13] FIG. 13 is a procedure diagram illustrating a further exemplary procedure for coordinating resource configuration information for synchronizing multiple flows. [Figure 14] FIG. 14 is a procedure diagram illustrating an exemplary procedure for coordinating resource configuration information for synchronizing multiple flows. [Figure 15] FIG. 15 is a procedure diagram illustrating another exemplary procedure for coordinating resource configuration information for synchronizing multiple flows. [Figure 16] FIG. 16 is a procedure diagram illustrating a further exemplary procedure for coordinating resource configuration information for synchronizing multiple flows. [Figure 17] FIG. 17 is a procedure diagram illustrating an exemplary procedure for maintaining joint Quality of Service (QoS) for multiple flows. [Figure 18] FIG. 18 is a procedure diagram illustrating another exemplary procedure for maintaining joint quality of service (QoS) for multiple flows. [Figure 19] FIG. 19 is a procedure diagram illustrating a further exemplary procedure for synchronizing multiple flows. [Figure 20] FIG. 20 is a flow diagram illustrating a further example for transmitting multiple flows using priority levels. [Figure 21] FIG. 21 is a procedure diagram illustrating a further exemplary procedure for coordinating resource configuration information for synchronizing multiple flows. [Figure 22] FIG. 22 is a procedure diagram illustrating an exemplary procedure for maintaining joint quality of service (QoS) for multiple flows. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0005] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of or in combination with embodiments and other examples explicitly, implicitly and / or inherently (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which apparatus, systems, devices, etc. and / or any elements thereof perform operations, processes, algorithms, functions, etc. and / or any portions thereof, it should be understood that any embodiment described and / or claimed herein assumes that any apparatus, system, device, etc. and / or any elements thereof are configured to perform any operations, processes, algorithms, functions, etc. and / or any portions thereof.

[0006] Exemplary Communication System The methods, apparatus, and systems provided herein are well suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with reference to Figures 1A-1D, in which various elements of a network may utilize, execute, be arranged in accordance with, and / or be adapted and / or configured for the methods, apparatus, and systems provided herein.

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

[0008] 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or “STA,” may be configured to transmit and / or receive wireless signals and may include (or be) 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, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), household electronic devices, devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

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

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

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

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

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

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

[0015] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, e.g., using dual connectivity (DC) principles. Thus, the radio interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to and from multiple types of base stations (e.g., eNBs and gNBs).

[0016] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology such as IEEE 802.11 (i.e., Wireless Fidelity, Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access, WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communication (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), or the like.

[0017] 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as, for example, an office, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish either a small cell, a pico cell, or a femto cell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.

[0018] The RAN 104 / 113 may communicate with the 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 the WTRUs 102a, 102b, 102c, 102d. The data may have various quality of service (QoS) requirements, such as, for example, different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, the CN 106 / 115, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, may communicate with another RAN (not shown) that employs any of GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.

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

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

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

[0022] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated into an electronic package or chip, for example.

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

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

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

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

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

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

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

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

[0031] 1C is a system diagram illustrating the RAN 104 and the CN 106, according to one embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 102b, and 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.

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

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

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

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

[0036] The SGW 164 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions such as fixing the user plane during inter-eNodeB handover, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.

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

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

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

[0040] In an exemplary embodiment, the other network 112 may be a WLAN.

[0041] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a distribution system (DS) or another type of wired / wireless network that carries traffic within and / or outside the BSS. Traffic originating from outside the BSS to the STAs may arrive through the AP and be distributed to the STAs. Traffic originating from the STAs to destinations outside the BSS may be sent to the AP and transmitted to the respective destination. Traffic between STAs in the BSS may be transmitted, for example, through the AP, where the source STA may transmit traffic to the AP, which may distribute the traffic to the destination STA. Traffic between STAs in the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted between (e.g., directly between) the source STA and the destination STA using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode is sometimes referred to herein as an "ad-hoc" communication mode.

[0042] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel may be the operating channel of the BSS, but may be used by STAs to establish a connection with the AP. In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. With CSMA / CA, STAs (e.g., all STAs), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0043] High throughput (HT) STAs may use, for example, a 40 MHz wide channel for communication via a combination of a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0044] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. A 40 MHz and / or 80 MHz channel may be formed by combining multiple contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data may pass through a segment parser that may split the data into two streams. Inverse fast fourier transform (IFFT) processing and time domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the above-mentioned operations for the 80+80 configuration may be reversed and the combined data may be transmitted to a medium access control (MAC) layer, entity, etc.

[0045] Sub-1 GHz operation modes are supported by 802.11af and 802.11ah. The 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 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter-type control / machine-type communication (MTC) such as MTC devices in macro coverage areas. MTC devices may have limited capabilities, including specific capabilities, for example, support for specific bandwidths and / or limited bandwidths (e.g., support for only these). The MTC device may include a battery that has a battery life above a threshold (eg, to maintain a very long battery life).

[0046] WLAN systems that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that may be designated as a primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STAs among all STAs operating in the BSS that support the smallest bandwidth operating mode. In an 802.11ah example, the primary channel may be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only) 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 sensing and / or network allocation vector (NAV) setting may depend on the state of the primary channel. For example, if the primary channel is busy due to STAs (that only support 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered busy even though most of the frequency band may remain idle and available for use.

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

[0048] 1D is a system diagram illustrating the RAN 113 and the CN 115, according to one embodiment. As mentioned above, the RAN 113 may employ NR radio technology and communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also communicate with the CN 115.

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

[0050] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including varying numbers of OFDM symbols and / or varying lengths of absolute time durations).

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

[0052] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.

[0053] 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 at least one Data Network (DN) 185a, 185b. Although each of the foregoing elements is illustrated as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

[0055] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

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

[0057] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b through the UPFs 184a, 184b via an N3 interface with the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.

[0058] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to any of the WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other element(s) / device(s) described herein may be performed by one or more emulation elements / devices (not shown). An emulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

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

[0060] The one or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, for example, one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0061] The following abbreviations may be used herein as follows:

[0062] [Table 1]

[0063] overview In certain representative embodiments, the WTRU may determine a resource (e.g., transmission) configuration to use when transmitting and / or receiving the multiple flows (e.g., in the uplink and / or downlink) to synchronize the transmissions. The multiple flows may be synchronized, for example, such that a delay between a (e.g., latest) PDU in a first flow and a (e.g., latest) PDU in a second flow is less than or equal to a different expected time of arrival (ETA) threshold (e.g., inter-flow PDB). For example, the PDUs in the first and second flows may be received from either the WTRU, another WTRU, a base station, and / or an application and / or service (e.g., generating information in the payload of the PDU) performed by a network entity.

[0064] For example, the WTRU may be configured to do any of the following: receiving information (e.g., configuration information) from a base station (e.g., gNB) indicating primary and secondary ETA thresholds (e.g., time instances and / or durations) and one or more transmission configurations associated with different priorities (e.g., at least one default transmission configuration (e.g., logical channel (LCH)) per flow for transmitting PDUs in each flow having a default priority value; ● receiving a PDU associated with a first flow (e.g., “Flow 1”) and / or transmitting the PDU using a default forwarding configuration associated with the first flow; Determining a time of arrival (ToA) of a PDU associated with a second flow (e.g., “Flow 2”), e.g., by using (e.g., starting) a timer and / or based on a time instance when a PDU in the first flow was received; ● Provided that a PDU in the second flow is received (e.g., at a time instance) before (e.g., before) the primary ETA threshold has elapsed; transmitting the PDUs in the second flow using a default forwarding configuration associated with the second flow; provided that a PDU in the second flow is received (e.g., at a time instance) after the primary ETA threshold and before (e.g., before the secondary ETA threshold has elapsed); determining a (e.g. new) priority for PDUs in the second flow, the new priority being higher than the default priority; transmitting the PDUs in the second flow using a preferred (e.g., determined) forwarding configuration that matches the determined new priority; Provided that a PDU in the second flow is received (e.g., at a time instance) after (e.g., after) a secondary ETA threshold has elapsed; Sending a status indication to a base station (e.g., gNB) indicating recent PDU reception (e.g., information indicating the priority of the recent PDU and / or the time when the recent PDU was received); Transmitting the PDU using a best-effort configuration or an available transmission configuration, such as after receiving an instruction from a base station to transmit the PDU in a best-effort configuration; Dropping (e.g., discarding) a PDU, such as after receiving an instruction to drop (any) recent PDU, transmitting one or more PDUs of either the first flow and / or the second flow (e.g., multiple flows) using one or more preferred (e.g., determined) forwarding configurations to satisfy a QoS requirement (e.g., a joint QoS requirement based on an association between the first flow and the second flow); ● Sending information indicating one or more (e.g., determined) forwarding configurations for satisfying (e.g., ensuring) synchronization of data in a first flow and / or a second flow (e.g., multiple flows), such as within an RTT requirement.

[0065] In certain representative embodiments, the WTRU may determine a forwarding configuration to use when transmitting data in multiple flows (e.g., in the uplink) to synchronize the transmission. The multiple flows may be synchronized, for example, such that a delay between a (e.g., last and / or latest) PDU of an ADU in a first flow and a (e.g., last and / or latest) PDU of an ADU in a second flow is less than or equal to a different expected time of arrival (ETA) threshold (e.g., inter-flow PDB). For example, the PDUs in the first and second flows may be received from either the WTRU, another WTRU, a base station, and / or an application and / or service (e.g., generating information in the payload of the PDU) executed by a network entity.

[0066] For example, the WTRU may be configured to do any of the following: receiving information (e.g., configuration information) from a base station (e.g., gNB) indicating first, second, and third ETA thresholds (e.g., time instances and / or durations) and one or more transmission configurations associated with different priorities (e.g., at least one default transmission configuration (e.g., LCH) per flow for transmitting PDUs in each flow having a default priority value); ● receiving one or more PDUs of an ADU in a first flow and / or transmitting a PDU (e.g., of the ADU) using a default forwarding configuration associated with the first flow; ● determining a time of arrival (ToA) of one or more PDUs in a second flow based on a time instance when a first PDU of the ADU in the first flow is received; determining a ToA by starting first, second, and third timers associated with first, second, and third ETA thresholds; provided that a (e.g., last and / or most recent) PDU of the ADU in the first flow and / or one or more PDUs of the ADU in the second flow are received by the WTRU before (e.g., before) a first ETA threshold; transmitting a PDU of the ADU in the first flow and a PDU of the ADU in the second flow using a default forwarding configuration associated with the first flow and the second flow (e.g., either of them); provided that a (e.g., some or any) PDU of the ADU in the first flow and / or a (e.g., some or any) PDU of the ADU in the second flow is received after (e.g., after the first ETA threshold has elapsed) and / or before (e.g., before the second ETA threshold has elapsed); o determining a (e.g. new) priority for a (e.g. recent) PDU of an ADU in a first flow (e.g. the new priority may be higher than the default priority); o transmitting PDUs of the ADUs in the first flow using the associated (e.g. preferred) forwarding configuration (e.g. corresponding to the determined new priority); transmitting a PDU of the ADU in the second flow using a default forwarding configuration associated with the second flow; sending a status indication and / or a request indication to a base station (e.g., a gNB) on condition that a forwarding configuration is not available for transmitting the PDUs of the ADU in the first flow; and / or Transmitting PDUs of the ADU in the first flow using a best effort or available forwarding configuration based on an instruction received from the gNB (e.g., to transmit PDUs in a best effort configuration); provided that (e.g., some or any) PDUs of the ADU in the second flow are received after (e.g., after) a second ETA threshold and / or before (e.g., before) a third ETA threshold; o determining a (e.g. new) priority for the (e.g. most recent) PDU of the ADU in the second flow (e.g. the new priority may be higher than the default priority); - transmitting PDUs of the ADUs in the second flow using the associated forwarding configuration (e.g. corresponding to the determined new priority); sending a status indication and / or a request indication to a base station (e.g. gNB) provided that a relevant (e.g. preferred) forwarding configuration is not available for transmitting the PDUs of the ADU in the second flow; and / or ■ Transmitting PDUs of the ADU in the second flow using a best effort transmission configuration (e.g., based on instructions received from the base station); provided that (e.g., some or any) PDUs of the ADU in the second flow are received after (e.g., after) a third ETA threshold; Sending a status indication and / or a request indication to a base station (e.g., gNB) on a recent PDU, o transmitting PDUs of the ADUs in the second flow using a best effort transmission configuration and / or dropping the PDUs (e.g. based on an indication received from a base station); transmit one or more PDUs of any of the first flow, the second flow, and / or the third flow using one or more preferred (e.g., determined) forwarding configurations to satisfy a QoS requirement (e.g., a joint QoS requirement based on an association between the first flow, the second flow, and / or the third flow); and / or ● Sending information indicating one or more (e.g., determined) forwarding configurations to meet (e.g., ensure) synchronization of data in a first flow, a second flow, and / or a third flow (e.g., multiple flows), such as within an RTT requirement.

[0067] overview The term extended reality (XR) may be used as an umbrella term for different types of immersive experiences, including any of virtual reality (VR), augmented reality (AR), mixed reality (MR), and / or any reality interpolated between them. For example, virtual reality (VR) may refer to a rendered version of a delivered visual and / or auditory scene. The rendering may be designed to mimic (e.g., as naturally as possible) real-world visual (e.g., stereoscopic 3D) and / or auditory stimuli to an observer or user as the observer or user moves within limits defined by the application. For example, augmented reality (AR) may refer to where a user is provided with additional information and / or artificially generated objects and / or content overlaid on the current environment. Mixed reality (MR) may refer to an advanced form of AR where some virtual elements are inserted (e.g., intentionally) into a physical scene to provide the illusion that these elements are part of the real scene. As used herein, the term XR may include any combined real and / or virtual environment and human-machine interaction generated by computer technology and wearables.

[0068] The concept of immersion in the context of XR services may refer to providing a sense of being surrounded by and / or being physically and spatially located within a virtual environment. The level of virtualization may range from partial sensory input to fully immersive multi-sensory input leading to a virtual reality that may be virtually indistinguishable from actual reality.

[0069] XR devices may (e.g., typically) be associated with the ability to provide varying degrees of spatial tracking. XR devices may be equipped with various sensors that enable spatial tracking, such as monocular cameras, stereo cameras, depth cameras, radio beacons, GPS, inertial sensors, etc. Spatial tracking may be performed at different levels, such as 3 degrees of freedom (DoF) (e.g., rotational movement along the X, Y, and Z axes) or 6DoF (e.g., rotational and / or translational movement along the X, Y, and Z axes). For example, spatial tracking may result in some form of interaction to experience virtual content. A user may act within and / or interact with components within the extended reality. For example, actions and / or interactions may include movements, gestures, eye tracking, etc. Spatial tracking may be a feature that enables an immersive XR experience. For example, some form of head and / or motion tracking may ensure that simulated visual and / or auditory components from the user's perspective are updated to match the user's movements. Inaccurate and / or delayed spatial tracking may result in discomfort and / or a feeling of motion sickness for the user.

[0070] As described herein, a WTRU (e.g., user equipment) may correspond to any XR device and / or node, which may appear in various form factors. WTRUs (e.g., XR WTRUs) include, but are not limited to, the following: head-mounted displays (HMDs), optical see-through glasses and camera see-through HMDs for AR and / or MR, mobile devices with position tracking and / or cameras, wearables, etc. In addition to the above, several different types of XR WTRUs may be envisioned based on XR device capabilities, such as display, camera, sensor, sensor processing, wireless connectivity, XR / media processing, power, etc., provided by one or more devices, wearables, actuators, controllers, and / or accessories. One or more devices and / or nodes (e.g., WTRUs) may be grouped into a cooperative XR group to support XR applications and / or services.

[0071] Traffic Models for XR Applications and Use Cases In one particular representative embodiment, the services and / or traffic flows for (e.g., different) XR applications and / or use cases are specified (e.g., described) in 3GPP TR 26.928.

[0072] Virtual Reality 1 (VR1) For example, a VR1 application (e.g., immersive 6DoF streaming) can be modeled using service flows applicable to a viewport-dependent streaming architecture. Similar to adaptive streaming (e.g., dynamic adaptive streaming over HTTP, DASH), viewport-dependent streaming can enable dynamically updating media and / or video quality based on available bitrates in the network and / or air interface. According to the service and / or traffic flow, tracking and / or attitude information of the XR device's viewport (e.g., small packet size less than 100B) is periodically transmitted to the XR server at a relatively low data rate (e.g., 0.5-2Mbps, 60-500Hz) in the UL. In response, the XR server may transmit in the DL at relatively high data rates (e.g., 6-18MBps for 4k omnidirectional and / or FoV area streaming) and adaptively quasi-periodically transmit viewport-optimized media (e.g., H.264 / 265 video) (e.g., 40 / 60 / 120fps), which is then rendered on the XR device display.

[0073] For example, the traffic characteristics of VR1 can be described as follows: UL traffic: attitude and / or viewport information (including, for example, information about 6DoF) ○ Small packet size (e.g., relatively constant size less than 100B), low data rate (e.g., 0.5-2Mbps) and / or single flow, ○ Periodic: (e.g., periodicity range of 60-500 Hz), and / or DL traffic: (1) media and / or video including viewport-optimized scenes (e.g., high quality) and / or 2) media and / or video for non-viewport scenes (e.g., low quality) Large packet sizes (e.g., variable size with Gaussian distribution or fixed size of 1500B), high data rates (e.g., 6-18Mbps), E2E latency (e.g., 50ms), multiple flows (e.g., video flows with different bitrates, 3D media, metadata), Quasi-periodic (e.g. periodicity as a function of frame rate, e.g. 40 / 60 / 120 fps).

[0074] Virtual Reality 2 (VR2) For example, a VR2 application (e.g., an immersive gaming spectator mode) can be modeled using service flows applicable to a split rendering architecture. In such a case, the XR server may perform pre-rendering and / or encoding of 2D media and / or video frames based on pose information sent by the XR device periodically at a low data rate (e.g., 0.5-2 Mbps, 60-500 Hz). Rendering may be performed (e.g., primarily) in the XR server and transmitted in the DL at a high data rate and low latency (e.g., 30-45 Mbps, 10-20 ms). The XR device may perform asynchronous time-warping (ATW) to decompress the received media and / or video and correct the viewport based on the latest pose information. The RTT latency for sending pose information in the UL and receiving pre-rendered media in the DL may range up to 50 ms, while the ATW may meet the motion-to-photon latency requirement (e.g., less than 20 ms) based on in-device processing.

[0075] For example, the traffic characteristics of VR2 can be described as follows: ●UL: Attitude and / or viewport information Small packet size (e.g., a certain size less than 100B), low data rate (e.g., 0.5-2Mbps), single flow, ○ Periodic (e.g., periodicity range of 60-500 Hz), and / or ●DL: 3D scene in frame buffer Large packet sizes (e.g., Gaussian distribution and / or up to 1500B, or unlimited), high data rates (e.g., 30-45Mbps), latency (e.g., around 30ms and / or up to 50ms RTT), multiple flows (3D video and / or media, metadata), Quasi-periodic (e.g. periodicity as a function of frame rate, e.g. 60 / 90 fps).

[0076] Augmented Reality 1 (AR1) For example, an AR1 application (e.g., real-time communication with a store clerk) may be characterized using a service flow applicable to a distributed computing architecture. According to the service and / or traffic flow, the XR device may transmit pose information (e.g., 0.5-2 Mbps, 60-500 Hz) and / or video (e.g., 10 Mbps, 10 Hz frame update rate) to the XR server in the UL. The received information may be used by the XR server to generate a scene, which is then converted into a 2D (e.g., video) or 3D media (e.g., 3D object) format along with metadata (e.g., scene description). The compressed media and metadata (e.g., characterized by a Pareto distribution) may be delivered (e.g., quasi-periodically) in the DL at a high data rate (e.g., 30-45 Mbps, 40 / 60 / 120 fps). The XR device may then locally generate the AR scene by overlaying the 3D objects onto the 2D video, rendering the scene within the device display, etc.

[0077] For example, the traffic characteristics of AR1 are as follows: ●UL: Attitude information and / or 2D video stream information Posture: Small packet size, low data rate (e.g., 0.5-2Mbps), periodic (e.g., 60-500Hz). Video: large packet size, higher data rate (e.g., 10 Mbps), periodic (e.g., 10 Hz update periodicity), multi-flow video, and / or ●DL: 2D and / or 3D pre-rendered media and XR metadata Large packet sizes (e.g., Pareto distribution), high data rates (e.g., 30-45 Mbps), multi-flows (2D and / or 3D media and / or metadata). Quasi-periodic (e.g. periodicity as a function of frame rate 60 / 90 fps).

[0078] Augmented Reality 2 (AR2) For example, AR2 applications (e.g., XR conference, AR animated avatar call) may use services and / or traffic flows applicable to the XR conversation architecture, such as when two or more XR clients and / or devices can perform peer-to-peer communication with intermediate media processing in the network. Based on the type of user representation, including any of 2D+ / RGBD (e.g., 2.7 Mbps), 3D mesh (e.g., 30 Mbps), 3D Video point cloud coding (VPCC), and / or Geometry-based point cloud compression (GPCC) (e.g., 5-50 Mbps), may be supported for the AR2 application. In an exemplary XR traffic flow, an XR client in a device may initiate a call setup procedure, based on which a session control function may trigger network-based media processing. The SMF may forward the call setup to the second XR client and / or device, and then forward real-time media processing and streaming to both clients with low latency (e.g., E2E<100 ms). During an XR call, 2D and / or 3D media, and possibly user pose information, may be transmitted quasi-periodically on the UL and DL between the XR client and / or device.

[0079] For example, the traffic characteristics of AR2 can be described as follows: UL: 2D and / or 3D media, poses and / or videos of the user Large packet sizes and / or data rates (e.g., 2.7-50 Mbps), PDB (e.g., less than 150 ms), multi-flow (2D and / or 3D media), Quasi-periodic (e.g., 60-500 Hz), and / or DL: 2D and / or 3D media, poses and / or videos of the user Large packet sizes (e.g., truncated Gaussian distribution) and / or data rates (e.g., 2.7-50 Mbps), E2E PDB (e.g., less than 100 ms), multi-flow (2D and / or 3D media), o Quasi-periodic (e.g., 60-500 Hz).

[0080] XR Conference For example, an XR conferencing application may provide an immersive conferencing experience between geographically separated users, such as by representing the users in a 3D volumetric representation (e.g., point cloud and / or mesh). One or more cameras (e.g., with depth perception capabilities) may be placed at each user's location to enable interaction (e.g., seeing, hearing, rotating, zooming in, resizing, etc.) with each other's full 3D volumetric representation on their respective headsets and / or glasses. An XR conferencing application may support simultaneous UL and DL media traffic. The media traffic may include either audio, video, and / or 3D objects. Media formats that may be applied to capture users in a 3D volumetric format include either 2D+ / RGBD (e.g., >2.7 Mbps for one camera, >5.4 Mbps for two cameras), 3D mesh (e.g., about 30 Mbps), 3D VPCC and / or GPCC (e.g., 5-50 Mbps). The media processors may be located centrally (e.g., in a core network) or distributed (e.g., in an edge network). Services and / or traffic flows between XR clients and / or users via the in-network media processors may be expected to be similar to the AR2 and XR conversation use cases. Joining an XR conference session may result in an initial download peak to download the virtual environment and associated media objects in the XR application. Throughout the remainder of the session, data rates may vary depending on the number of users, their upload formats, and / or the refresh rate of the virtual 2D and / or 3D objects and / or environments.

[0081] For example, the traffic characteristics of an XR conference can be described as follows: UL: User's 2D and / or 3D media, poses and / or real-time video Large packet sizes and / or data rates (e.g., 2.7-50 Mbps), multi-flow (2D and / or 3D media), Quasi-periodic (e.g., 60-500 Hz), ○ Low encoder PER (e.g. 10 -3 less than 100,000 yen), and / or ● DL: User's 2D and / or 3D media, pose and / or real-time video, 2D and / or 3D objects and / or environment (possibly from a third party) Large packet sizes and / or data rates (e.g., 2.7-50 Mbps), E2E PDB (e.g., less than 100 ms), multi-flow (2D and / or 3D media), Quasi-periodic (e.g., 60-500 Hz), ○Low encoder PER (e.g., 10 -3 less than).

[0082] Cloud Gaming (CG) For example, CG applications (e.g., 5G online games) may rely primarily on an adaptive streaming architecture, where video and / or media rendered in the network are streamed to thin clients in devices (e.g., smartphones, tablets). In a typical service and / or traffic flow for CG, an XR device may transmit (e.g., periodically) pose information (e.g., 100-250B) related to the viewport to an XR server in UL (e.g., 0.1-1Mbps, 60-500Hz). The generated viewport-related video and / or media (e.g., 1500B) is encoded and / or compressed (e.g., H.264 and / or H.265 video) and quasi-periodically transmitted by the XR server in DL (e.g., 30-45Mbps, 30 / 50 / 60 / 90 / 120fps, PER:10). -3). The received video and / or media may then be rendered in the XR device upon decoding and processing. The RTT latency to support certain high-end CG applications (e.g., category D for photorealistic or natural video games) may be determined by the round trip interaction delay (e.g., 50 ms). For other CG applications (e.g., categories A, B, and / or C), the UL PDB may be 10 ms and the DL streaming PDB may range from 50 ms to 200 ms.

[0083] For example, the traffic characteristics of CG can be described as follows: ●UL: Attitude and / or viewport information ○Small packet size (e.g., 100-250B), low data rate (e.g., 0.1-1Mbps), PDB: 10ms, single flow, ○ Periodic (e.g., periodicity range of 60-500 Hz), and / or ● DL: User's 2D and / or 3D media and / or images Large packet size (e.g. up to 1500), high data rate (e.g. 30-45Mbps), PDB: 20ms, multi-flow (2D and / or 3D media, video) ○ Quasi-periodic (e.g. periodicity as a function of frame rate: 30 / 50 / 60 / 90 / 120 fps), ○PER:10e-3.

[0084] An XR application may be associated with (e.g., generates and / or receives) multiple data flows per application and / or service that may be transmitted independently over the Uu interface. The multiple data flows may originate from different devices (e.g., HMD, smartphone, haptic gloves) associated with the WTRU. For example, a possible use case is a shared XR experience where users equipped with multiple XR devices can interact with each other while physically located in different places (e.g., while two people are waving at different locations).

[0085] For example, each data flow may have different traffic characteristics (e.g., packet size and / or arrival distribution). For example, each data flow may have independent and / or different QoS (e.g., packet error rate, delay budget) requirements. The WTRU may be configured (e.g., attempts) to ensure that the QoS requirements for each flow are met independently. Similarly, traffic prioritization at the scheduler in the network may also be performed independently for each QoS flow. The WTRU may also support other additional applications that may have a higher priority value for flows associated with the XR application supported by the WTRU.

[0086] In addition to the RAN QoS (e.g., PER and / or latency) that each data flow may be required to meet (e.g., independently), coordination between data flows may be required so that bounds on inter-flow time delays can be guaranteed. For example, even slight delays and / or lack of synchronization between data flows may lead to poor QoE and / or sudden discomfort or illness to the user (e.g., vomiting, disorientation).

[0087] In this regard, coordination of multiple data (e.g., QoS) flows of an XR experience that may originate from different devices may be important such that the flows are delivered in the UL to the gNB and application server (e.g., an edge server co-located with the gNB) within a specified synchronization time window to ensure that all flows can be processed and / or rendered together. Similar issues may need to be addressed when flows are delivered in the DL such that different flows are received at the WTRU from the gNB within a synchronization time window.

[0088] Determine the transfer configuration to ensure multiple data flows are synchronized In a particular representative embodiment, a WTRU (e.g., an XR WTRU) may perform transmission of PDUs in one or more data flows (e.g., associated with an application). For example, the PDUs may be transmitted to ensure that the PDUs in the different flows are transmitted and / or received to satisfy one or more joint QoS requirements. As an example, the QoS requirements may be based on any of the following: thresholds, configurations, triggers, conditions, and / or criteria received from the network and / or application (e.g., an application function hosted by the WTRU). In one example, the WTRU may perform transmission of PDUs in the different flows such that the difference in terms of achievable QoS (e.g., latency, data rate, reliability) between the PDUs in the different flows is within the QoS requirements associated with the application. In another example, the WTRU may perform transmission of PDUs in a synchronized manner (e.g., transmitted simultaneously or with a minimum reception time difference) such that the flows are received at a receiving entity (e.g., a base station, an application function, a CN function) within a synchronization window.

[0089] In certain representative embodiments, the synchronization window may be associated with a synchronization requirement. The synchronization requirement may depend on the application supported by the WTRU. For example, an application consisting of two data flows (e.g., a video data flow and an attitude data flow) may prefer (e.g., require) that PDUs in the different data flows are received at one or more entities and / or functions (e.g., WTRU, gNB, edge server function, remote server function) within a QoS bound (e.g., latency bound) that may correspond to a QoS difference between the PDUs in the first and second data flows.

[0090] The synchronization window may be applicable to any QoS metric including latency, data rate, and / or reliability. If the synchronization window is associated with (e.g., corresponds to) a data rate, then the PDUs in one or more associated flows may be considered synchronized, e.g., when a PDU is transmitted and / or received with a data rate value associated with an individual flow satisfying any of the joint minimum and / or joint maximum data rate values ​​associated with one or more flows associated with an application. If the synchronization window is associated with (e.g., corresponds to) a latency, then the PDUs in one or more associated flows may be considered synchronized, e.g., when a PDU is transmitted and / or received with a latency bound (e.g., PDB) associated with an individual flow satisfying any of the joint minimum and / or joint maximum latency bounds associated with one or more flows belonging to an application.

[0091] In certain representative embodiments, PDUs in different data flows may be received at the WTRU from other devices (e.g., associated with the WTRU) and / or from other functions and / or entities (e.g., higher layer, application layer functions) (e.g., co-located with the WTRU). For example, if PDUs in different associated flows are processed and / or forwarded independently of one another during forwarding and / or transmission, a drift condition may be introduced such that PDUs in different associated data flows may drift with respect to one another (e.g., reception time drift). This drift may cause PDUs in different data flows to arrive at the receiving entity (e.g., gNB) beyond a synchronization window required by an application.

[0092] In certain representative embodiments, the network may include any of base stations (e.g., gNBs, TRPs, RAN nodes), core network functions, and / or application functions (e.g., edge server functions, remote server functions). In certain representative embodiments, the flows may correspond to any of QoS flows and / or data flows (e.g., flows of data or PDUs) that may be associated with one or more QoS requirements, such as latency, data rate, and / or reliability. In certain representative embodiments, the transport configuration may be associated with (e.g., may correspond to) one or more radio bearers, one or more logical channels, one or more configuration parameters in individual layers in the access stratum protocol stack (e.g., SDAP, PDCP, RLC, MAC, and / or PHY), one or more parameters associated with logical channel prioritization (LCP) (e.g., priority, PBR, and / or BSD), parameters associated with mapping of data flows and / or QoS flows to radio bearers (e.g., parameters in the SDAP), one or more carriers, one or more BWPs, and one or more links (e.g., used to deliver PDUs in the UL or DL ​​direction).

[0093] Determining Associations Between Data Flows Based on Configured Parameters and / or Identifiers In certain representative embodiments, a WTRU (e.g., an XR WTRU) may determine whether one or more data flows received and / or transmitted by the WTRU are associated with an application and / or service based on explicit and / or implicit parameters and / or identifiers detectable by the WTRU in the data flows. For example, the parameters and / or identifiers for determining the association between flows may be configured in the WTRU (e.g., via RRC signaling, NAS layer signaling, and / or application layer signaling).

[0094] As an example, the parameters and / or identifiers used by the WTRU to identify an association between multiple data flows (e.g., a first, second, or more flows) may include any of the following (e.g., any combination thereof): -Identifiers and / or IDs associated with flows and / or applications o The WTRU may determine that the first flow and the second flow may be associated with an application, e.g., if the WTRU may detect a common ID associated with an application in the PDUs of the first flow and / or the second flow (e.g., in the header and / or payload of the data unit). The ID of the application may be pre-configured in the WTRU, for example. Priority and / or importance information associated with the flow o For example, the WTRU may determine that the first flow and the second flow may be associated with an application, such as by the WTRU detecting common and / or similar priority and / or importance indications in the PDUs of the first flow and the second flow (e.g., in the header and / or payload). o For example, the WTRU may determine that the first flow and the second flow may be associated, such as when an indication of priority and / or importance detected by the WTRU (e.g., in a header or payload of a data unit) is likely to be above and / or below one or more priority and / or importance thresholds. -Time and / or timing information within the associated flow o The WTRU may determine that the first and second flows may be associated, such as if one or more PDUs in the first flow and one or more PDUs in the second flow may be received by the WTRU within a duration and / or window. For example, the duration / window may correspond to a time difference between the reception time of a PDU in the first flow (e.g., at "t1") and the reception time of a PDU in the second flow (e.g., at "t2"). For example, the WTRU may determine that the first and second flows may be associated when the time difference (e.g., t2-t1) meets (e.g., is less than) a duration and / or window threshold. For example, the WTRU may determine that the first and second flows may be associated based on a common format and / or granularity of timing information (e.g., timestamps) carried in (e.g., PDUs associated with) the first and second flows. - spatial and / or pose information within the associated flow o For example, the WTRU may determine that the first flow and the second flow may be associated, such as when PDUs carrying spatial information correspond to common spatial parameters. The spatial parameters may include, for example, any of the following: direction and / or orientation of the device's FoV, slices and / or tiles of a video and / or media frame, position information (e.g., coordinates), attitude information, etc. The spatial parameters may be determined by the WTRU, for example, based on detection for a particular PDU transporting spatial information (e.g., attitude and / or control PDUs that may be identified by the WTRU based on a data type identifier) ​​and / or detection of other PDUs that may include spatial information within the PDU (e.g., in the header and / or payload).

[0095] Transmitting support information regarding application parameters and / or requirements to the network In certain representative embodiments, a WTRU (e.g., an XR WTRU) may transmit information associated with applications supported in the WTRU to the network, such as to support application awareness functionality in the network. For example, information related to the applications may be transmitted to the network as assistance information, status information, and / or indications thereof.

[0096] For example, information associated with the application that may be transmitted by the WTRU to the network may include any of the following (eg, any combination of the following): -Applications supported by the WTRU For example, the WTRU may transmit numbers and / or IDs associated with the supported applications. The WTRU may (e.g., further) transmit information regarding relative and / or absolute priority values ​​associated with the supported applications. -Data flows associated with applications For example, the WTRU may transmit numbers and / or IDs associated with supported data flows for each application. The WTRU may (e.g., further) transmit information regarding relative and / or absolute priority values ​​associated with the data flows. -Devices associated with the application o For example, the WTRU may send numbers and / or IDs associated with supported devices and / or device associations per application. - Data and / or traffic types associated with the data flows per application For example, the WTRU may transmit information regarding the data types in the first and second flows associated with the application, such as where the data types may include any of video data (e.g., I frame data, P frame data, B frame data), RGB-D data, 360 degree video data, haptic data, attitude and / or positioning data, audio data, etc. -Characteristics and / or parameters of data and / or traffic associated with data flows per application o For example, the WTRU may transmit information regarding characteristics of the first and second flows associated with the application, including whether the data is periodic, aperiodic, semi-persistent, quasi-periodic, etc. For example, the WTRU may transmit information regarding the number of PDUs (e.g., per ADU) expected in one or more flows per application. The information regarding the number of PDUs (e.g., per ADU) may (e.g., further) include statistical information including any of an average, a minimum, a maximum, and / or a standard deviation value. For example, the WTRU may transmit QoS requirements for one or more flows associated with the application, such as including any of a data rate, latency (e.g., PDB), reliability (e.g., PER), absolute priority value and / or relative priority value, etc.

[0097] For example, the WTRU may send information associated with a number of data flows associated with an application and / or service to the network based on any of the following (e.g., any combination thereof): During connection and / or session establishment and / or (re)configuration (e.g. procedures) o For example, during any of the RRC connection, PDU session, application session establishment, and / or (re)configuration procedures. -When changing and / or updating data flows per application o For example, when adding a new flow and / or releasing an existing flow associated with the application. When receiving higher layer and / or application information Upon receiving an indication (eg, from an application function hosted in the WTRU and / or the network) indicating any changes in, for example, supported data types, traffic characteristics, and / or QoS requirements. -When detecting changes in measurements and movements For example, when any of the RSRP, RSRQ, RSSI measurements of any signal, channel, radio link, carrier, etc. (which may be associated with one or more data flows) go above and / or below a threshold. For example, when attitude and / or positioning measurements (e.g., position information and / or attitude in 6DoF) go above and / or below an attitude threshold. -When detecting a change in time and / or timing attributes o For example, the WTRU may transmit the information periodically or when a time period (eg, a timer) associated with transmitting the assistance information is set and / or elapses (eg, expires).

[0098] For example, the WTRU may send information associated with multiple data flows associated with an application and / or service, such as assistance information, to the network via AS layer signaling (e.g., either RRC signaling and / or messages, MAC CE and / or DCI) or non-AS (Non-AS, NAS) layer signaling (e.g., PDU session related messages).

[0099] Receiving configuration information to ensure synchronous transmission of multiple flows In a particular representative embodiment, a WTRU (e.g., an XR WTRU) may perform transmission of PDUs in one or more (e.g., associated) data flows, such as based on one or more parameters, thresholds, and / or trigger conditions that may be received by the WTRU from the network as configuration information.

[0100] For example, the configuration information received by the WTRU may include any (eg, any combination) of the following parameters: - Estimated Time of Arrival (ETA) threshold For example, the WTRU may receive one or more ETA thresholds associated with (e.g., corresponding to) an expected time for receiving a PDU in a data flow, such as where the PDU may be the first PDU or any subsequent PDU after receiving a preceding PDU (e.g., the first PDU). o The ETA threshold may be associated with an expected time for receiving a first PDU in a second data flow after receiving a first PDU in a first data flow, such as when the first and second data flows are associated with an application. In one embodiment, the ETA threshold may be associated with a duration or time value. The WTRU may start a timer at a time instance when it receives a first PDU in the first flow and stop the timer when it expires at a time instance corresponding to the ETA threshold and / or when it receives a first PDU in the second flow (e.g., the first and second flows are associated with the same application). The WTRU may determine the elapsed time between receiving a (e.g., first) PDU in the first flow and receiving a (e.g., first) PDU in the first flow. -Expected data rate (EDR) threshold For example, the WTRU may receive one or more expected data rate threshold (EDR) values ​​associated with an expected data rate for receiving a PDU in a data flow (e.g., a first PDU or a subsequent PDU after receiving a preceding PDU). The data rate may correspond to any of the following units: PDUs per second, frames per second, and / or bits per second, etc. In another embodiment, the EDR threshold may be associated with an expected data rate for a PDU in a second associated data flow after receiving a PDU in a first data flow having the first data rate value. -Expected reliability threshold For example, the WTRU may receive one or more expected reliability threshold (EER) values ​​associated with an expected reliability for receiving a PDU in a data flow (e.g., a first PDU or a subsequent PDU after receiving a preceding PDU). The reliability value may correspond to any of the following units: packet error rate, frame error rate, and / or probability of error, etc. In another embodiment, the EER threshold may be associated with an expected reliability for one or more PDUs in a second associated data flow after receiving one or more PDUs in a first data flow having a first reliability value. -Transfer configuration parameters For example, as part of a forwarding configuration, the WTRU may receive one or more default and / or reference priority values ​​associated with (e.g., corresponding to) flow channels (e.g., radio bearers and / or LCHs) associated with an application. For example, a first flow channel may be associated with a first priority value and / or a second flow channel may correspond to a second priority value. The first and second flow channels may be associated with the same application, and the first and second default priority values ​​may be intended, for example, to achieve default QoS performance (e.g., default latency and / or default data rate) for PDUs in the first and second flow channels during transmission. For example, the WTRU may (e.g., further) receive a set of one or more alternative configurations (e.g., non-default configurations), e.g., including alternative parameters and / or thresholds that may be used by the WTRU when performing a data transmission. In one embodiment, the alternative configurations may include one or more priority values ​​associated with flow channels that the WTRU may be permitted to use when performing a data transmission. For example, the WTRU may be permitted to use an alternative configuration consisting of a first and / or second priority value when using a first LCH associated with a first data flow, and / or may be permitted to use an alternative configuration consisting of a third and / or fourth priority value when using a second LCH associated with a second data flow (e.g., the first and second data flows are associated with an application). For example, the WTRU may (e.g., further) receive criteria indicating when and / or how the WTRU may use the default and / or alternate configuration. For example, the criteria may indicate using the default configuration when PDUs in the first and / or second data flows are received within a first expected threshold (e.g., an ETA threshold) and / or using the alternate configuration when PDUs in the first and / or second data flows are received after the first expected threshold (e.g., an ETA threshold).

[0101] For example, the WTRU may receive configuration information (e.g., default and / or alternative configurations) associated with performing transmissions of PDUs in different associated data flows via AS layer signaling (e.g., either RRC signaling and / or messages, MAC CE and / or DCI) or non-AS (NAS) layer signaling (e.g., PDU session related messages).

[0102] Transmission of PDUs in different associated flows within a synchronized time window In certain representative embodiments, the WTRU may perform transmission of PDUs in different data flows associated with applications and / or services based on one or more ETA thresholds and / or information about how PDUs in different flows may be associated with one another (e.g., using flow IDs) such that the PDUs may be transmitted and / or received within a synchronized time window.

[0103] For example, the WTRU may receive configuration information from the network that includes any of the following parameters (e.g., any combination thereof): -First Estimated Time of Arrival (ETA) threshold For example, the first ETA threshold may be associated with a first duration (e.g., a normal duration or a default duration) expected for receiving one or more PDUs in the first flow and / or the second flow. -Second Estimated Time of Arrival (ETA) threshold For example, the second ETA threshold may be associated with a second duration (e.g., greater than and / or longer than the normal duration, such as used to advance a delayed PDU) expected to receive one of the more PDUs in the first flow and / or the second flow. -One or more transport configurations (e.g., LCHs and / or radio bearers) having different priority values, e.g., at least one transport configuration may be associated with a first data flow and a second transport configuration may be associated with a second data flow, and the first and second data flows may be associated with the same application and / or service. For example, the first and / or second forwarding configurations may be associated with default priority values ​​and / or alternative priority values. Identifiers and other parameters (e.g., timestamps and / or sequence numbers) found in the PDUs in the first and second flows o For example, PDUs in the first and second flows may carry the same or similar identifiers and / or IDs (e.g., in packet headers) when the flows are associated with the same application and / or service. For example, the WTRU may use timestamp information and / or a sequence number (e.g., in a packet header) to determine timing information associated with the PDU (e.g., arrival time, packet creation time, departure time, and / or remaining time to transmit the PDU).

[0104] In certain representative embodiments, after receiving the configuration information, the WTRU (e.g., an XR WTRU) may receive a first PDU in a first data flow from an associated device and / or function (e.g., over a sidelink and / or over a function and / or entity co-located with the WTRU). For example, the WTRU may determine that the first PDU in the first flow may belong to an application and / or service (e.g., an XR application) supported by the WTRU based on an identifier and / or ID detectable in the PDU header. For example, the first PDU may be received by the WTRU at the SDAP layer or in a buffer associated with the first LCH. As an example, the WTRU may transmit the first PDU in the first data flow (e.g., over the first LCH) using a default forwarding configuration (e.g., a default priority value associated with the first LCH), such as when transmitting a PDU in the UL to the gNB.

[0105] In a particular representative embodiment, the WTRU may start a first timer after receiving a first PDU in a first data flow. For example, the first timer may operate for a duration (e.g., span) to a first ETA threshold. In a particular representative embodiment, the WTRU may start a second timer after receiving a first PDU in a first data flow. For example, the second timer may operate for a duration (e.g., span) to a second ETA threshold. In one embodiment, the WTRU may start the first and second timers simultaneously, and the WTRU may operate the timers for their respective ETA threshold durations. In another embodiment, the WTRU may start and / or stop the timers sequentially. The second timer may be started after expiration of the first timer (e.g., of the first ETA threshold) and / or the second timer may be operated for a duration to the second ETA threshold.

[0106] In a particular representative embodiment, the WTRU may have a first duration associated with receiving a first PDU in the first data flow (e.g., may be configured with a first duration). For example, the first duration may correspond to a first ETA threshold. In a particular representative embodiment, the WTRU may have a second duration associated with receiving a first PDU in the first data flow (e.g., may be configured with a second duration). For example, the second timer may correspond to a second ETA threshold. In one example, the WTRU may determine the start of the first and second durations simultaneously, and the WTRU may determine whether the first duration and / or the second duration have elapsed. In another example, the WTRU may determine the start of the first and second durations sequentially, and / or the WTRU may determine whether the first duration and / or the second duration have elapsed sequentially. The second duration may begin after the first duration has elapsed (e.g., after the first ETA threshold has elapsed) and / or the second duration may be determined to have elapsed using the second ETA threshold. The first duration may be determined to have elapsed using the first ETA threshold.

[0107] In a particular representative embodiment, the WTRU may take any of the following actions (e.g., any combination of the following actions) depending on when a first PDU in a second data flow (e.g., associated with a first PDU in a first data flow) may be received by the WTRU: For example, when a first PDU in the second flow is received by the WTRU before a first ETA threshold (e.g., before expiration of a first timer or lapse of the first ETA threshold), the WTRU: The first PDU in the second flow may be transmitted using a default forwarding configuration associated with the second flow (e.g., using a default priority value associated with the second LCH), such as when transmitting the PDU to the gNB in ​​the UL. For example, when a first PDU in a second flow is received by the WTRU after a first ETA threshold (e.g., after expiration of a first timer or the passage of a first ETA threshold) and / or before the end of a second ETA threshold (e.g., before expiration of a second timer or the passage of a second ETA threshold), the WTRU may perform one or more of the following: o Determine a priority to assign to the first PDU of the second flow based on the time instance when the first PDU of the first flow is received, the time instance when the first PDU of the second flow is received, and the first ETA threshold. For example, the WTRU may determine the time instance when the first PDU in the first and / or second flow is received based on the timestamp information. o Determine a priority to assign to the first PDU of the second flow based on the reception time of the PDU in the first flow (e.g., at “t1”) and the reception time of the PDU of the second flow (e.g., at “t2”). For example, the priority may be assigned such that the time difference between the PDUs in the first and second flows is less than or equal to a first ETA threshold. o Determine the time difference between receipt of the first PDU of the first flow and receipt of the first PDU of the second flow. The WTRU may use a higher priority for delayed PDUs (e.g., PDUs received after the ETA threshold has elapsed) by determining a compensation latency value that may allow the delayed PDU to be transmitted in the UL sooner than using a default priority value. o Determine (e.g., calculate) a compensated latency value by subtracting a first ETA threshold from the time difference (e.g., t2-t1-first ETA threshold). For example, the priority to assign to the PDU may be determined based on a mapping relationship between the calculated compensated latency value and the priority to assign. For example, the mapping relationship between the compensated latency and the priority may be received by the WTRU as (e.g., as part of) the configuration information. For example, the WTRU may be pre-configured with one or more transmission configurations that may be associated with different priority values ​​and / or with at least a transmission configuration having a priority value that matches the priority value determined to compensate for latency for the PDUs in the second flow. A transmission configuration may be selected with the matching priority value. For example, the WTRU may transmit the first PDU in the second flow in the UL to the gNB using the selected transmission configuration. o For example, the WTRU may not be configured with at least an active forwarding configuration (e.g., pre-configured and / or activated) that may be associated with a priority value matching the determined priority value for compensating latency for PDUs in the second flow, and / or may not be able to determine that active forwarding configuration, or it may be determined that a forwarding configuration with a matching priority is not available (e.g., due to a higher load condition where the number of buffered PDUs in the forwarding configuration or LCH is greater than a threshold), the WTRU may send an indication to the network to request to configure and / or activate a forwarding configuration with the determined priority value. For example, the WTRU may send an indication of the determined priority value to assign to the forwarding configuration. o After receiving an indication from the network indicating configuration and / or activation of the selected transmission configuration, the WTRU may transmit the first PDU in the second flow using the configured and / or activated transmission configuration, such as when transmitting a PDU in the UL. For example, when a first PDU in a second flow is received by the WTRU after a second ETA threshold (e.g., after expiration of a second timer or passage of the second ETA threshold), the WTRU may perform one or more of the following: For example, sending an indication to the gNB (e.g., in AS layer signaling, MAC CE, UCI) indicating reception of a PDU in the second flow after the second ETA threshold (e.g., the reception time exceeded the second timer). o After receiving an instruction (e.g., from a gNB) to transmit a PDU in the second flow using an available and / or activated transmission configuration (e.g., LCH) having an indicated priority value, transmit the first PDU in the second flow using the transmission configuration having the indicated priority value, such as when transmitting a PDU in the UL. o After receiving an instruction (e.g., from a gNB) to transmit a PDU in the second flow using a best effort transmission configuration (e.g., LCH), the WTRU may transmit the first PDU in the second flow using an available transmission configuration having the highest priority value and / or a best effort priority value, such as when transmitting a PDU in the UL. o After receiving an instruction (e.g., from a gNB) to drop a PDU in the second flow, the PDU may be dropped and / or no PDU may be transmitted in the UL.

[0108] Transmission of a group of related associated PDUs in different associated flows within a synchronized time window In certain representative embodiments, the WTRU may perform transmission of one or more associated PDUs (e.g., associated with ADUs) in different associated data flows based on configuration information, association information of the ADUs in the different flows, and / or monitoring of the reception times (e.g., arrival time instances) of the PDUs. For example, when transmitting PDUs in first and second flows that may be associated with an application and / or service, the WTRU may ensure that a transmission time difference for transmitting a last PDU associated with an ADU in the first flow and a last PDU associated with an ADU in the second flow is less than or equal to a synchronization time window (e.g., an inter-flow latency bound). For example, the synchronization time window may be associated with an application and / or service.

[0109] In a particular representative embodiment, the WTRU may receive configuration information from the network, where the configuration information may include any of the following (eg, any combination of the following): -First Estimated Time of Arrival (ETA) threshold For example, the first ETA threshold may be associated with a first duration (e.g., a normal duration or a default duration) expected for receiving one or more PDUs (e.g., associated with one or more ADUs) in the first and second flows. -Second Estimated Time of Arrival (ETA) threshold For example, the second ETA threshold may be associated with a second duration (e.g., greater than and / or longer than a normal duration, e.g., to advance a delayed PDU) expected for receiving one or more PDUs (e.g., associated with one or more ADUs) in the first flow. For example, the second ETA threshold may be associated with a first duration (e.g., a normal duration or a default duration) expected for receiving one or more PDUs (e.g., associated with one or more ADUs) in the second flow. For example, the second ETA threshold may be used to determine whether to transmit PDUs in the first and second flows using a normal and / or default forwarding configuration and / or an alternative forwarding configuration (e.g., for rapid transmission and / or delivery). -Third Estimated Time of Arrival (ETA) threshold For example, the third ETA threshold may be associated with a second and / or third duration (e.g., greater than and / or longer than a normal duration) expected for receiving one or more PDUs (e.g., associated with one or more ADUs) in the first flow and / or second flow (e.g., to advance a delayed PDU and / or to decide whether to drop a PDU or to transmit a PDU in a best effort configuration). - the expected number of PDUs per ADU in the first flow and in the second flow o For example, the first and second flows may be associated with an application and / or a service. o For example, a first flow may have N PDUs per ADU and a second flow may have M PDUs per ADU (eg, where N and M may be different integer values). - one or more transport configurations (e.g. LCH and / or radio bearers) with different priority values For example, at least one forwarding configuration may be associated with a first data flow and a second forwarding configuration may be associated with a second data flow. For example, the first and second forwarding configurations may be associated with default priority values ​​and / or alternative priority values. Identifiers and / or other parameters detected in the PDUs in the first flow and in the second flow o For example, information indicating a timestamp and / or a sequence number may be found in the PDU. o For example, PDUs in the first and second flows may carry the same or similar identifiers and / or IDs (e.g., in packet headers), such as when the flows are associated with the same application and / or service. For example, the PDUs in the first and second flows may carry (e.g., in packet headers) identifiers and / or IDs indicating association with the ADUs in the respective flows. As an example, one or more PDUs associated with an ADU may carry information about the ADU (e.g., ADU ID and / or data type of the ADU). For example, the WTRU may use timestamp information (e.g., in a packet header) to determine timing information associated with a PDU and / or ADU (e.g., arrival time, packet creation time, departure time, and / or remaining time to transmit the PDU). For example, the WTRU may use a sequence number (e.g., in a packet and / or PDU header) and / or ADU information (e.g., an ADU ID) to determine whether a PDU is the first, second, or Nth PDU associated with an ADU.

[0110] In certain representative embodiments, after receiving the configuration information, the WTRU may receive one or more PDUs associated with the ADUs in the first data flow from the associated device and / or function. For example, the WTRU may determine that one or more PDUs in the first flow may belong to an application and / or service (e.g., an XR application) supported by the WTRU and / or the ADU based on an identifier and / or ID and / or sequence number detectable in the PDU header. The first PDU may be received by the WTRU, for example, at the SDAP layer or in a buffer associated with the first LCH. The WTRU may transmit the one or more PDUs in the first data flow (e.g., the first LCH) using a default forwarding configuration (e.g., a default priority value associated with the first LCH), such as when transmitting the PDUs in the UL to the gNB.

[0111] In a particular representative embodiment, the WTRU may start a first timer after receiving a first PDU associated with an ADU in a first data flow. For example, the timer may run for a duration up to a first ETA threshold. The WTRU may determine (e.g., based on a sequence number in the PDU) a number of PDUs associated with the ADU in the first flow that may be received before the end of the first ETA threshold (e.g., before expiration of the first timer). The WTRU may (e.g., further) determine a number of PDUs associated with another ADU received in a second flow before the end of the first ETA threshold.

[0112] In a particular representative embodiment, the WTRU may associate a first duration with reception of a first PDU associated with an ADU in a first data flow. For example, the first duration may correspond to or be based on a first ETA threshold. The WTRU may determine (e.g., based on a sequence number in the PDU) a number of PDUs associated with the ADU in the first flow, which may be received prior to (e.g., upon) the expiration of the first duration. The WTRU may (e.g., further) determine a number of PDUs associated with another ADU received in a second flow prior to (e.g., upon) the expiration of the first duration.

[0113] In certain representative embodiments, the WTRU may start the second timer and / or the third timer after receiving the first PDU in the first data flow. For example, the second and / or third timers may operate for a duration up to the second ETA threshold and / or the third ETA threshold (e.g., respectively). In one embodiment, the WTRU may start the first, second, and third timers simultaneously, and the WTRU may cause the timers to run for a duration up to their respective ETA thresholds. In another embodiment, the WTRU may start the timers sequentially, and the second timer may start after expiration of the first timer (e.g., at the first ETA threshold) and / or the third timer may start after expiration of the second timer (e.g., at the second ETA threshold). For example, the WTRU may cause the second timer and / or the third timer to operate for a duration up to their respective ETA thresholds (e.g., the second and third thresholds).

[0114] In certain representative embodiments, the WTRU may associate a second timer and / or a third timer with the reception of the first PDU in the first data flow. For example, the second duration may correspond to or be based on a second ETA threshold. For example, the third duration may correspond to or be based on a third ETA threshold. In one embodiment, the first, second, and / or third durations may correspond to the same start time. Each of the first, second, and / or third durations may be determined according to their respective ETA thresholds. In another embodiment, the first, second, and / or third durations may be set sequentially, such as where the second duration may start after the passage of the first duration (e.g., after the first ETA threshold time from the reference time or PDU reception time) and / or where the third duration may start after the passage of the second duration (e.g., after the second ETA threshold time from the reference time or PDU reception time). For example, the WTRU may use the second and / or third ETA thresholds to determine the second and / or third durations.

[0115] In a particular representative embodiment, a WTRU (e.g., an XR WTRU) may perform any of the following actions (e.g., any combination of the following actions) depending on when a PDU associated with an ADU in a first data flow and / or a PDU associated with an ADU in a second data flow is received: For example, when a last PDU associated with an ADU in a first flow and / or one or more PDUs associated with an ADU in a second flow are received (e.g., by the WTRU) before a first ETA threshold (e.g., before expiration of a first timer or before a first duration has elapsed); o Transmit the last PDU associated with the ADU in the first flow and / or one or more PDUs associated with the ADU in the second flow using the respective default forwarding configurations associated with the first flow and / or the second flow (e.g. using default priority values ​​associated with the first and / or second LCHs), such as when transmitting a PDU to the gNB in ​​the UL. For example, when one or more PDUs associated with an ADU in a first flow and / or one or more PDUs associated with an ADU in a second flow are received (e.g., by the WTRU) after a first ETA threshold (e.g., after expiration of a first timer or after a first duration has elapsed) and / or before the end of a second ETA threshold (e.g., before expiration of a second timer or before a second duration has elapsed); o Determine a priority to assign to one or more PDUs (e.g., including a last PDU) associated with an ADU in the first flow based on the time instances when the different PDUs (e.g., a batch thereof) of the first flow are received. For example, the different PDUs of the first flow may include a batch of PDUs received before and after a first ETA threshold (e.g., before and after a first duration has elapsed). For example, the WTRU may determine the time instances when the PDUs in the first flow are received based on the timestamp information. o Determine a priority to assign to one or more PDUs (e.g., including the last) of the first flow received after the first ETA threshold based on a reception time of a PDU in a first batch in the first flow (e.g., PDUs received before the time duration associated with the first ETA threshold has elapsed) and a reception time of a PDU in a second batch in the first flow (e.g., PDUs received after the time duration associated with the first ETA threshold has elapsed). For example, the priority may be determined and / or assigned such that a time difference between the last PDU in the first batch in the first flow (e.g., at “t1”) and the last PDU in the second batch (e.g., at “t2”) is less than or equal to the first ETA threshold. For example, the WTRU may use a higher priority for any delayed PDUs (e.g., PDUs received after the time duration associated with the ETA threshold has elapsed) by determining a compensation latency value that may allow the delayed PDU to be transmitted on the UL faster than using a default priority value. Calculate a compensated latency value, such as by subtracting a first ETA threshold from the time difference (e.g., t2-t1-first ETA threshold). For example, the priority to assign to the PDUs in the second batch may be determined based on a mapping relationship between the calculated compensated latency value and the priority to assign. For example, the mapping relationship between the compensated latency and the priority may be received by the WTRU as (e.g., as part of) the configuration information. o Transmit one or more PDUs associated with an ADU in the second flow using a default forwarding configuration associated with the second flow (e.g., using a default priority value associated with the second LCH), such as when transmitting a PDU to the gNB in ​​the UL. If the WTRU is pre-configured with one or more transmission configurations that may be associated with different priority values ​​and / or at least a transmission configuration having a priority value that matches the priority value determined to compensate for the latency of the PDUs in the second batch in the first flow, select the transmission configuration with the matching priority value. For example, the WTRU may transmit the PDUs in the first flow (e.g., in the second batch) in the UL to the gNB using the selected transmission configuration. o If the WTRU is unable to find and / or determine at least an active transmission configuration (e.g., pre-configured and / or activated) that may be associated with a priority value that matches the determined priority value for compensating for latency of the PDUs in the second batch in the first flow, or if it may be determined that a transmission configuration with a matching priority is not available, send an indication to the network to request that a transmission configuration with the determined priority value be configured and / or activated. For example, the WTRU may send the determined priority value to assign to the transmission configuration in the indication. o After receiving information from the network indicating configuration and / or activation of the selected forwarding configuration, transmit the PDUs in the second batch in the first flow using the configured / activated forwarding configuration, such as when transmitting PDUs in the UL to the gNB. For example, when one or more PDUs associated with an ADU in a second flow are received by the WTRU after a second ETA threshold (e.g., after expiration of a second timer or after the second duration has elapsed) and / or before the end of a third ETA threshold (e.g., before expiration of a third timer or before the third duration has elapsed); o Determine a priority to assign to one or more PDUs (e.g., including a last PDU) associated with an ADU in the second flow based on time instances at which different batches of PDUs of the second flow are received. For example, the different batches may be received before and after the first and / or second ETA thresholds (e.g., before and after a duration has elapsed). For example, the WTRU may determine the time instances at which PDUs in the second flow are received based on timestamp information. o Based on the reception times of the PDUs in a first batch in the second flow (e.g., PDUs received before the first and / or second ETA thresholds or before the first and / or second durations have elapsed) and based on the reception times of the PDUs in a second batch in the second flow (e.g., PDUs received after the second ETA threshold or after the second duration has elapsed), determine a priority to assign to one or more PDUs (e.g., including the last PDU) of the second flow received after the second ETA threshold (e.g., after the second duration has elapsed). For example, the priority may be determined such that the time difference between the last PDU in the first batch in the second flow (e.g., at "t1") and the last PDU in the second batch (e.g., at "t2") is less than or equal to the second ETA threshold. Calculate a compensated latency value, such as by subtracting a first ETA threshold from the time difference (e.g., t2-t1-first ETA threshold). For example, the WTRU may determine priorities to assign to the PDUs in the second batch based on a mapping relationship between the calculated compensated latency value and the priorities to assign. o If the WTRU may be pre-configured with one or more transmission configurations that may be associated with different priority values, and / or at least with a transmission configuration having a priority value that matches the priority value determined to compensate for the latency of the PDUs in the second batch in the second flow, select the transmission configuration with the matching priority value. For example, the WTRU may transmit the PDUs in the second batch in the second flow using the selected transmission configuration, such as in the UL to the gNB. o If the WTRU cannot find and / or determine at least an active transmission configuration (e.g., pre-configured and / or activated) that may be associated with a priority value that matches the determined priority value for compensating for latency of PDUs in the second batch in the second flow, or if it may be determined that a transmission configuration with a matching priority is not available, transmit information to the network indicating a request to configure and / or activate a transmission configuration with the determined priority value. For example, the WTRU may transmit in an indication, e.g., the determined priority value to assign to a transmission configuration. o After receiving an indication from the network indicating configuration and / or activation of the selected transmission configuration, transmit PDUs in a second batch in a second flow using the configured and / or activated transmission configuration, such as when transmitting PDUs in the UL. when one or more PDUs in the first flow are received by the WTRU after a second ETA threshold (e.g., after expiration of a second timer or after the second duration has elapsed) and / or one or more PDUs in the second flow are received by the WTRU after a third ETA threshold (e.g., after expiration of a third timer or after the third duration has elapsed); o Sending information to the gNB (e.g., in AS layer signaling, MAC CE, and / or UCI) indicating reception of PDUs in the first flow and / or second flow after the second and / or third ETA threshold (e.g., after the reception time exceeds the second and / or third timer, or after the reception time has elapsed for the second and / or third duration). o If an indication is received (e.g., from a gNB) indicating to transmit PDUs in the first and / or second flow using an available and / or activated transmission configuration (e.g., LCH) having an indicated priority value, transmit the PDUs in the first flow and / or the second flow using the transmission configuration with the respective indicated priority value, such as when transmitting PDUs in the UL. o If an indication is received (e.g., from a gNB) indicating to transmit PDUs in the first flow and / or the second flow using a best effort transmission configuration (e.g., LCH), the WTRU may transmit the PDUs in the first flow and / or the second flow using the available transmission configuration with the highest priority value and / or best effort priority value when transmitting the PDUs in the UL. o If an instruction is received (e.g., from a gNB) indicating to drop a PDU in the first flow and / or the second flow, drop the PDU and / or do not transmit the PDU to the gNB, e.g., in the UL.

[0116] Satisfying QoS requirements based on association between multiple flows In certain representative embodiments, the WTRU may determine one or more actions to perform with respect to the multiple data flows (e.g., the first and second flows). For example, upon determining an association between one or more UL and / or DL ​​data flows (e.g., based on an indication regarding traffic characteristics that may be configured and / or detected by the WTRU), the WTRU may perform one or more actions to satisfy QoS requirements (e.g., associated with the UL and / or DL ​​data flows).

[0117] For example, the WTRU may determine an association for one or more PDUs (e.g., PDU sets and / or ADUs) from different data flows to forward and / or deliver (e.g., in a coordinated manner). One or more (e.g., joint) QoS requirements, such as any of a synchronization time window, latency, and / or data rate, may be common and applicable to and satisfied by one or more associated flows (e.g., among different data flows). In an embodiment, any of the actions performed by the WTRU based on the determined association between the multiple flows may correspond to ensuring synchronization of data in the data flows during transmission and / or reception. For example, any of the actions that may be performed by the WTRU may include any of: selecting and / or modifying resource (e.g., forwarding) configurations used to forward and / or deliver data in the different data flows; selecting and / or modifying forwarding configuration parameters used to forward and / or deliver data in the different data flows; and / or transmitting information (e.g., to the network and / or higher layers) indicative of the selected and / or modified forwarding configurations and / or forwarding configuration parameters.

[0118] In certain representative embodiments, the association between different data flows may be detected by the WTRU. The WTRU may detect the association between different data flows either at different layers, such as the application layer, the NAS layer, and / or at the access stratum layer (e.g., radio bearer, SDAP, PDCP, MAC, PHY). For example, when the association between the flows is detected at the SDAP layer (e.g., based on receiving an indication from a higher layer / application indicating a common ID in the PDUs of the two flows), the WTRU may perform a specific action to forward the PDUs in the second flow (e.g., by selecting a set of parameters configured at the MAC layer), such as when it detects a specific traffic and / or QoS related event (e.g., latency increases beyond a threshold) when forwarding the PDUs in the first flow.

[0119] As another example, the association between data flows may change and / or be determined in a combination of different dimensions and / or domains including the time domain (e.g., the association may be applicable over a time window and / or duration), the frequency domain (e.g., the association may be applicable when transmission and / or reception is performed over a set of channels, carriers, links, and / or frequency resources), and / or the spatial domain (e.g., a common location and / or area from which the data flows may originate or be intended / destined, and / or a common set of beams used to transmit and / or receive the flows). The WTRU may perform certain actions upon determining any changes to the association between data flows in different dimensions and / or domains. To determine the association between one or more data flows in the UL and / or DL, any indication and / or trigger may be configured in the WTRU, and / or the corresponding actions to ensure coordinated transmission / reception of the associated flows may include any of the following: -Changes in achievable and / or expected QoS For example, the WTRU may determine whether one or more flows may be associated with it and / or whether a corresponding action may be taken upon detecting a particular change in achievable and / or expected QoS related measurements in any of the associated flows (e.g., latency and / or data rate increasing above a threshold and / or latency and / or data rate decreasing below a threshold). -Changes in channel / link measurements o For example, the WTRU may determine whether any action may be performed when transmitting and / or receiving data in a different associated flow, such as when detecting a particular change in a measurement (e.g., an RSRP measurement increases and / or decreases above or below a threshold) for a channel, link, and / or beam used during transmission and / or reception of the data flow. For example, upon detecting degradation in measurements made on a first channel (e.g., CSI-RS associated with a first resource set and / or beam set) used to transmit data in a first flow, the WTRU may perform a particular action (e.g., drop and / or suspend transmission) when transmitting data in a second flow using a second channel (e.g., a second resource set and / or beam set). For example, the WTRU may perform an action to transmit data in the second flow regardless of whether the second channel may be experiencing any degradation. -receiving instructions from the network and / or higher layers o For example, the WTRU may determine whether any action may be performed upon receiving (e.g., from the network and / or higher layers) one or more indications and / or one or more notifications indicating any change (e.g., some change) regarding traffic forwarding and / or delivery of data in any of the associated flows. The indications and / or notifications may include any of the following: status reports, feedback (e.g., HARQ ACK / NACK), flow control indications, error rates (e.g., PER for a PDU or set of PDUs), and / or uncertainty information (e.g., due to QoS estimation and / or prediction). For example, the one or more indications and / or notifications may be used by the WTRU to determine whether (e.g., joint) QoS requirements may be met for the associated flows. -Timer / Periodic o For example, the WTRU may be configured with a timer (e.g., duration and / or periodicity) for determining whether any action may be performed. The timer (e.g., duration and / or periodicity) may be applied upon detecting one or more events related to and / or associated with a data flow (e.g., a delay between receipt of a first PDU in a first flow and receipt of a first PDU in a second flow is greater (or less) than a threshold). As an example, the WTRU may start a timer (e.g., determine the start of the duration and / or interval) upon detecting an associated event and / or may determine a corresponding action prior to expiration of the timer (e.g., prior to the lapse of the duration and / or interval). As another example, the WTRU may be configured to determine (e.g., periodically) whether an action may be performed based on determining (e.g., periodically) an association between one or more flows in the UL and / or DL.

[0120] In certain representative embodiments, the WTRU may perform actions to ensure that joint QoS requirements can be met based on a determination of an association between data flows during UL transmission and / or DL ​​reception. For example, the WTRU may perform any one or more of the following actions (e.g., a combination thereof): -Performing QoS compensation during data transmission within the associated flow. For example, a WTRU may be configured with one or more resource (e.g., transmission) configurations (e.g., radio bearer configuration, LCH configuration, and / or resource configurations such as configured grants, BWP, etc.). Upon detecting any event that may affect synchronization between data transmission and / or reception and / or association between flows (e.g., actual QoS differs from expected QoS), the WTRU may select a pre-configured transmission configuration to compensate for the change in QoS in one or more associated flows. o For example, upon detecting delayed reception and / or transmission of one or more PDUs in a first flow, the WTRU may select a pre-configured transmission configuration (e.g., a new configured grant having a higher periodicity and / or payload size). The WTRU may select the transmission configuration based on a determination of a difference between the delays incurred for PDUs in the associated second flow and the associated first flow (e.g., PDUs in the first flow may be transmitted to catch up with PDUs in the second flow while reducing and / or minimizing the delay difference). For example, the WTRU may send an indication to the network requesting to activate a (e.g., pre-configured) transmission configuration and / or configure a (e.g., new) transmission configuration to compensate for QoS. o For example, upon detecting a delayed transmission of one or more PDUs in a first flow, the WTRU may decide (e.g., based on one or more criteria) whether to transmit and / or drop the transmission of one or more PDUs in an associated second flow. The WTRU may decide whether to receive a PDU in a first flow when the reception of a PDU in an associated second flow may be delayed (e.g., based on another criterion). The criteria (e.g., conditions) for making the decision (e.g., whether to transmit, receive, drop, and / or skip a PDU) may include the degree of association between the flows (e.g., fully or partially associated based on an association value), the priority and / or importance of the PDUs in the associated flows, and / or the amount of difference between the QoS achievable for the PDUs in the associated flows. For example, when a priority value of a PDU in the second flow is greater than a threshold, the WTRU may decide to transmit and / or receive a PDU, such as when detecting a delay between the transmission and / or reception of a PDU in a first flow. For example, when a priority value of a PDU in the second flow is below a threshold, the WTRU may decide to drop transmission and / or skip reception of a PDU in the second flow when a PDU in the first flow is delayed. -Re-adjusting / re-aligning the QoS within the associated flows, and / or For example, the WTRU may determine an amount of adjustment (e.g., re-adjustment and / or realignment) that may be applied to the QoS of one or more flows upon detecting a change in the achievable QoS in one or more other associated flows (e.g., during data transmission and / or reception). For example, when the WTRU detects an increase or decrease in QoS (e.g., data rate and / or latency) in a first flow by a certain amount (e.g., greater than or less than a threshold), the WTRU may determine a corresponding increase or decrease in QoS for the associated second flow, such as based on an association between the flows. Provided that the QoS of the first flow decreases by X%, the WTRU may determine (e.g., infer) that the QoS of the second flow may also decrease by X%. The UE may determine a matching and / or adjustment (e.g., similar or corresponding) amount to the QoS in the second flow (e.g., align QoS so that the QoS in both flows are matched), such as by indicating a change in forwarding configuration to the network to match the QoS and / or change forwarding configuration parameters to match the determined amount. For example, the WTRU may determine an offset amount relative to a start time (e.g., of a slot, minislot, subframe, frame, or other TTI) for the periodic data transmission of the first flow using the first resource (e.g., the first configured grant) based on the determination of an offset amount (e.g., similar or corresponding) for starting the periodic data transmission of the associated second flow using the second resource (e.g., the second configured grant). The WTRU may send an indication to the network (e.g., in an RRC, MAC CE, and / or UCI), for example, indicating the determined offset amount for the first and / or second configured grant configurations. - Sending instructions and / or information regarding the associated flow to the network For example, the WTRU may send one or more indications to the network (e.g., in an RRC, MAC CE, and / or UCI) based on detection of one or more events and / or triggers. The one or more events and / or triggers may be associated with (e.g., ensure) synchronization and / or association of different flows. The one or more indications may include any of the following: a request for assistance in synchronizing transmission and / or reception of data in multiple associated flows, a request to configure a (e.g., new) forwarding configuration, a request to update and / or change parameters of a pre-configured forwarding configuration, a request to activate and / or deactivate any of the parameters and / or configurations of a selected forwarding configuration, and / or a request to release any forwarding configuration.

[0121] Instructions for changing resource configuration In certain representative embodiments, the WTRU may transmit one or more indications (e.g., in the RRC, MAC CE, and / or UCI) to the network. For example, the WTRU may transmit information indicating either that it is unable to determine and / or select a suitable transport configuration, to update the QoS during subsequent transmission and / or reception for one or more sets of previously transmitted PDUs in different flows, and / or to drop one or more sets of previously transmitted PDUs.

[0122] In a particular representative embodiment, the WTRU may be configured with one or more resource configurations. The one or more resource configurations may include one or more configured grant (CG) configurations and / or one or more semi-persistent scheduling (SPS) configurations. The CG configuration may include one or more CG parameters (e.g., start offset time, periodicity, payload size), such as to ensure that data transmission in the UL and / or reception in the DL for one or more associated flows can be performed within a synchronous RTT window. The SPS configuration may include one or more SPS parameters (e.g., start offset time, periodicity, payload size), such as to ensure that data transmission in the UL and / or reception in the DL for one or more associated flows can be performed within a synchronous RTT window. The RTT latency (e.g., for a given data flow) may be measured between the transmission of one or more PDUs (e.g., PDU sets or ADUs) in the UL and the reception of one or more PDUs (e.g., PDU sets or ADUs) in the DL. For example, the RTT latency may be measured between the transmission of one or more PDUs on the UL during the active time of the CG configuration and the reception of one or more PDUs on the DL (e.g., associated with the UL transmission) during the active time of the SPS configuration.

[0123] In a particular representative embodiment, the synchronous RTT window may refer to the RTT time difference between the transmission and reception of one or more PDUs (e.g., PDU sets or ADUs) in a first (e.g., associated) flow and the transmission and reception of one or more PDUs (e.g., PDU sets or ADUs) in a second (e.g., associated) flow. The WTRU may be configured with (e.g., joint) QoS requirements. For example, the QoS requirements may ensure that the synchronous RTT window (e.g., multi-flow RTT time difference between multiple flows) remains above (or below) a threshold. The WTRU may be configured to monitor whether any change is observed in the per-flow RTT and / or multi-flow RTT time difference (e.g., between different associated flows) per flow. Based on the monitoring, the WTRU may determine whether any changes may be applied to parameters of the resource configurations (e.g., CG and / or SPS configurations) and / or may select a (e.g., new or pre-configured) set of resource configurations (e.g., CG and / or SPS configurations) that may ensure that the (e.g., joint) QoS requirements (e.g., RTT time difference is below a threshold and / or remains within range) are met.

[0124] In certain representative embodiments, the WTRU may be configured by the network with one or more resource configurations based on statistical information (e.g., average, standard deviation, minimum, maximum) regarding the RTT latencies of different associated flows. For example, the WTRU may provide and / or indicate the statistical information in assistance information to a base station in a RAN and / or CN function (e.g., AMF, SMF). The one or more resource configurations may include one or more configured grant (CG) configurations and / or one or more semi-persistent scheduling (SPS) configurations. For example, the WTRU may be (e.g., further) configured with (1) one or more per-flow RTT thresholds for one or more flows (e.g., corresponding to a maximum or minimum difference in latency from an average / expected RTT latency value) and / or (2) one or more multi-flow RTT time difference thresholds between different associated flows. For example, the WTRU may be (e.g., further) configured with information indicating an association between the per-flow RTT thresholds and / or multi-flow RTT thresholds and the resource configurations (e.g., CG and / or SPS configurations). For example, the information may (e.g., further) indicate the effectiveness of using either the CG and / or SPS configuration when sending and / or receiving data within a per-flow and / or multi-flow RTT threshold. As another example, the information may (e.g., further) indicate parameters (e.g., offset values, periodicity) of the CG and / or SPS configuration that may be changed, such as to realign the CG and / or SPS configuration with changes in the per-flow and / or multi-flow RTT.

[0125] In certain representative embodiments, one or more (e.g., triggering) events and / or conditions may be monitored by the WTRU. The monitoring of events and / or conditions may be performed by the WTRU to determine whether any resource configurations and / or parameters of resource configurations (e.g., for CG and / or SPS) may be changed, such as to meet per-flow and / or multi-flow RTT latency. For example, the (e.g., triggering) events and / or conditions may include any of the following: -Connectivity and / or session (re)configuration For example, when receiving and / or transmitting any signaling messages associated with an RRC connection, an RRC state, a PDU session, and / or an application layer session (re)configuration for one or more associated flows, For example, when changing the RRC state of the WTRU from RRC_CONNECTED to RRC_INACTIVE or IDLE, or vice versa: - Receiving higher layer and / or application layer instructions o upon receiving an indication, for example, from any higher layer, from one or more PDUs (e.g., information in the headers of one or more PDUs) of one or more associated flows, and / or from network information indicating any of the following changes in subsequent data that may be transmitted and / or received using any of the CG configurations and / or SPS configurations: ■ Data type (e.g. the next frame changes from a P / B frame to an I frame), ■ Priority, importance, and / or the relative priority and / or importance of a data type (e.g., I-frames or P-frames); ■ A failed upper layer frame (e.g., the application layer failed to decode an I-frame), ■ Traffic characteristics (e.g., the number of PDUs in a PDU set is expected or determined to be above or below a threshold, the PDU or PDU set delay bound is expected or determined to be above or below a threshold, the PER or PDU set error rate is expected or determined to be above or below a threshold, and / or the frame rate is expected or determined to be above or below a threshold); ■ the priority of the data (e.g., the priority value of a PDU or set of PDUs is expected or determined to be above or below a threshold); ■ the QFI and / or any QoS indications and / or markings (e.g., the QFI value is expected or determined to be greater than or less than a threshold value); -Duration, interval, and / or periodicity For example, the WTRU may determine whether any of the CG and / or SPS configurations may be changed when a timer (e.g., duration and / or interval) configured to monitor per-flow and / or multi-flow RTT latency starts and / or expires. As another example, the WTRU may periodically determine changes to the CG and / or SPS configuration to meet the RTT latency. The periodicity may be based on a configured periodicity (e.g., a periodicity associated with a frame rate), -Change and / or update data flows per application For example, when adding one or more (e.g., new) flows and / or releasing (e.g., existing) flows associated with an application; -Jitter measurement For example, when a measured jitter value (e.g., the difference between an expected timeslot or other TTI when data is expected to be received and an actual timeslot or other TTI when data is actually received) in one or more data flows is above or below a threshold value; -Radio link measurements For example, when RSRP, RSRQ, and / or RSSI measurements of a signal, channel, beam, carrier, and / or link (e.g., associated with one or more data flows transmitted and / or received by the WTRU) are above and / or below a threshold value; -Changes in movement, and / or For example, the WTRU may determine that attitude / positioning measurements (e.g., position information and / or attitude in 6DoF) are above and / or below attitude and / or position thresholds; - Change power saving configuration For example, when changing any of the parameters and / or configurations associated with CDRX and / or DRX used during transmission and / or reception of data in different flows (e.g., cycle duration, on-time, and / or inactive time).

[0126] In certain representative embodiments, the WTRU may determine a per-flow RTT and / or multi-flow RTT latency for an associated data flow. For example, provided that the WTRU is configured with one or more resource (e.g., CG and / or SPS) configurations, the WTRU may determine the per-flow RTT and / or multi-flow RTT latency based on a measurement of a time difference between transmission and / or reception of PDUs in different associated flows, or based on another indication received from a higher layer and / or the network. For example, the WTRU may compare the measured per-flow RTT and / or multi-flow RTT latency against a set of (e.g., configured) thresholds to determine whether any of the resource (e.g., CG and / or SPS) configurations are valid for transmitting and / or receiving data. For example, upon the WTRU determining that the per-flow RTT and / or multi-flow RTT latency is above and / or below a set of configured thresholds, the WTRU may send an indication and / or request to the network (e.g., via an RRC message, MAC CE, and / or UCI) to change parameters of a resource (e.g., CG and / or SPS) configuration or select a (e.g., new) resource (e.g., CG and / or SPS) configuration such that data transmission and / or reception in different flows may be aligned with the determined per-flow RTT latency and / or multi-flow RTT latency.

[0127] In one example, when determining that the per-flow RTT latency for a first flow is higher than a threshold, the WTRU may infer a similar and / or corresponding (e.g., equivalent) change in the per-flow RTT latency for an associated second flow. Upon determining the change in the per-flow RTT latency, the WTRU may determine one or more updates and / or modifications to the resource (e.g., CG and / or SPS) configuration and / or parameters thereof that may be made to (re)align the transmission / reception of PDUs in both flows (e.g., the first and second flows) such that the multi-flow RTT latency remains below a threshold. The WTRU may send an indication (e.g., explicit or implicit) to the network (e.g., in an RRC, MAC CE, and / or UCI) indicating the determined change to the resource (e.g., CG and / or SPS) configuration and / or perform data transmission and / or reception in the different data flows using the updated and / or modified resource configuration. For example, the WTRU may perform data transmission and / or reception in a different data flow using the updated and / or modified resource configuration after receiving an indication and / or confirmation (e.g., explicit or implicit) from the network (e.g., in an RRC, MAC CE, and / or DCI). As another example, the WTRU may perform data transmission and / or reception in a different data flow using the updated and / or modified resource configuration after a timer expires (e.g., after a duration).

[0128] FIG. 2 is a system diagram illustrating an example of multi-flow synchronization that may be used within a communication system described herein. In FIG. 2, one or more devices, such as WTRUs 102-a and / or 102-b, may transmit multiple flows (e.g., as a group or individually) to a base station 204 (e.g., gNB 180), such as over a sidelink using an anchor or relay WTRU 202. For example, a first flow may comprise multiple PDUs, such as a first PDU 206 and a second PDU 208. In certain representative embodiments, the PDUs comprising the first flow may form multiple ADUs, such as a first PDU 206 and a second PDU belonging to a first ADU 210 of the first flow. For example, a second flow may comprise multiple PDUs, such as a first PDU 212 and a second PDU 214. In some representative embodiments, the PDUs comprising the first flow may form multiple ADUs, such as a first PDU 212 and a second PDU 214 belonging to a second ADU 216 of a second flow. The WTRU 202 may be configured with a synchronization time window (e.g., interval). The WTRU 202 may be configured with at least a first resource configuration. For example, a first threshold (e.g., time point) 218 ​​and a second threshold (e.g., time point) 220 may form or define the synchronization time window.

[0129] In FIG. 2, the WTRU 202 may receive the PDUs 206, 208, 212, 214 from the WTRU 102-a and / or WTRU 102-b before the first and second thresholds have elapsed (e.g., from a previous ADU of the first and / or second flows). The WTRU 202 may proceed to transmit (e.g., forward) the PDUs 206, 208, 212, 214 using a first resource configuration. For example, the first resource configuration may be a configured grant (CG) resource configuration that includes resources for multiple transmission occasions 222, 224, 226, etc. In FIG. 2, the WTRU 202 may transmit the PDUs 206, 208, 212, 214 to the base station 204 using the transmission occasion 222. For example, the first transmission occasion 222 may ensure synchronization between the first flow and the second flow such that the PDUs 208, 206, 212, 214 transmitted using the first transmission occasion 222 are received at the base station 204 within a third threshold 230 (e.g., latency between PDUs, ADUs and / or flows) from the perspective of the base station 204.

[0130] 3 is a system diagram illustrating another example of multi-flow synchronization that may be used within a communication system described herein. In FIG. 3, one or more devices, such as WTRUs 102-a and / or 102-b, may transmit multiple flows (e.g., as a group or individually) to a base station 204 (e.g., gNB 180), such as over a sidelink using an anchor or relay WTRU 202. For example, a first flow may comprise multiple PDUs, such as a first PDU 206 and a second PDU 208. In certain representative embodiments, the PDUs comprising the first flow may form multiple ADUs, such as a first PDU 206 and a second PDU belonging to a first ADU 210 of the first flow. For example, a second flow may comprise multiple PDUs, such as a first PDU 212 and a second PDU 214. In some representative embodiments, the PDUs comprising the first flow may form multiple ADUs, such as a first PDU 212 and a second PDU 214 belonging to a second ADU 216 of a second flow. The WTRU 202 may be configured with a synchronization time window (e.g., interval). The WTRU 202 may be configured with at least a first resource configuration and a second resource configuration. For example, a first threshold (e.g., time point) 218 ​​and a second threshold (e.g., time point) 220 may form or define the synchronization time window.

[0131] In FIG. 3, the WTRU 202 may receive the PDUs 206, 208, 212, 214 from the WTRU 102-a and / or WTRU 102-b after the first threshold has elapsed and before the second threshold has elapsed (e.g., from a previous ADU of the first and / or second flow). The WTRU 202 may proceed to transmit (e.g., forward) the PDUs 206, 212, 214 using a first resource configuration. For example, the first resource configuration may be a configured grant (CG) resource configuration that includes resources for multiple transmission occasions 222, 224, 226, etc. In FIG. 3, the WTRU 202 may transmit the PDUs 206, 212, 214 to the base station 204 using the transmission occasion 222. Due to the PDU 208 being received by the WTRU 202 after the first threshold 218 but before the second threshold 220, the WTRU 202 may proceed to transmit (e.g., forward) the PDU 208 using the second resource configuration. For example, the second resource configuration may be a configured grant (CG) resource configuration that includes resources for multiple transmit occasions 302, 304, etc. In FIG. 3, the WTRU 202 may transmit the PDU 208 to the base station 204 using the transmit occasion 302 (e.g., following the transmit occasion 222). For example, the use of the transmit occasions 222 and 302 may ensure synchronization between the first and second flows such that the PDUs 206, 212, 214 transmitted by the WTRU 202 are received at the base station 204 within the third threshold 230 (e.g., latency between PDUs, ADUs, and / or flows) from the perspective of the base station 204.

[0132] 4 is a system diagram illustrating a further example of multi-flow synchronization that may be used within a communication system described herein. In FIG. 4, one or more devices, such as WTRUs 102-a and / or 102-b, may transmit multiple flows (e.g., as a group or individually) to a base station 204 (e.g., gNB 180), such as over a sidelink using an anchor or relay WTRU 202. For example, a first flow may comprise multiple PDUs, such as a first PDU 206 and a second PDU 208. In certain representative embodiments, the PDUs comprising the first flow may form multiple ADUs, such as a first PDU 206 and a second PDU belonging to a first ADU 210 of the first flow. For example, a second flow may comprise multiple PDUs, such as a first PDU 212 and a second PDU 214. In some representative embodiments, the PDUs comprising the first flow may form multiple ADUs, such as a first PDU 212 and a second PDU 214 belonging to a second ADU 216 of a second flow. The WTRU 202 may be configured with a synchronized time window (e.g., a time interval). The WTRU 202 may be configured with at least a first resource configuration. For example, a first threshold (e.g., time point) 218 ​​and a second threshold (e.g., time point) 220 may form or define the synchronized time window.

[0133] In FIG. 4, the WTRU 202 may receive the PDUs 206, 212, 214 from the WTRU 102-a and / or WTRU 102-b before the first and second thresholds have elapsed (e.g., from a previous ADU of the first and / or second flow). The WTRU 202 may receive the PDU 208 after the first and second thresholds have elapsed (e.g., outside the synchronization time window). The WTRU 202 may proceed to transmit (e.g., forward) the PDUs 206, 208, 212, 214 using the first resource configuration. For example, the first resource configuration may be a configured grant (CG) resource configuration that includes resources for multiple transmission occasions 222, 224, 226, etc. In FIG. 4, the WTRU 202 may transmit the PDUs 206, 212, 214 to the base station 204 using the transmission occasion 222. For example, the first transmission occasion 222 may ensure synchronization between the first and second flows such that the PDUs 206, 212, 214 transmitted using the first transmission occasion 222 are received at the base station 204 within the third threshold 230 (e.g., latency between PDUs, ADUs, and / or flows) from the perspective of the base station 204. Furthermore, the WTRU 202 may transmit at least the PDUs 208 to the base station 204 using the transmission occasion 224. Synchronization between the first and second flows may not be ensured due to the PDUs 208 being received after the first and second thresholds, resulting in the PDUs 208 being received at the base station 204 outside or after the third threshold 230.

[0134] In certain representative embodiments, multiple flows may be synchronized on a per-PDU and / or per-ADU basis, such as in Figures 2-4. In other representative embodiments, flow synchronization may be performed on a basis other than a PDU or ADU, such as, but not limited to, a set of PDUs.

[0135] FIG. 5 is a procedural diagram illustrating an example procedure for synchronizing multiple flows. In a particular representative embodiment, the procedure of FIG. 5 may be generally performed by a WTRU 102, such as the WTRU 202. At 502, the WTRU 102 may transmit (e.g., to the base station 204) information indicating (1) an association between a first flow and a second flow and (2) a maximum time difference between an ADU of the first flow and an ADU of the second flow. At 504, the WTRU 102 may receive (e.g., from a base station) information indicating any of a first resource configuration, a second resource configuration, a first time threshold, and / or a second time threshold (e.g., greater than the first time threshold). After 504, the WTRU 102 may receive (e.g., from a higher layer, another WTRU 102) one or more PDUs of the first ADU of the first flow and one or more PDUs of the second ADU of the second flow at 506. At 508, the WTRU 102 may transmit one or more PDUs of the first ADU of the first flow (e.g., to or towards the base station 204) using the first resource configuration. At 510, the WTRU 102 may transmit at least a last PDU of the second ADU of the second flow using the second resource configuration, provided that (1) a first time threshold has elapsed since receipt of the last PDU of the first ADU of the first flow and (2) a second time threshold has elapsed since receipt of the last PDU of the first ADU of the first flow.

[0136] In certain representative embodiments, the first resource configuration may be a first configured grant configuration, and the second resource configuration may be a second configured grant configuration. For example, a size of a transmission occasion (e.g., a time and / or frequency resource) associated with the first resource configuration is larger than a size of a transmission occasion associated with the second resource configuration. For example, the first resource configuration may include a first plurality of transmission occasions having a first periodicity, and the second resource configuration may include a second plurality of transmission occasions having a second periodicity that is smaller than the first periodicity.

[0137] In a particular representative embodiment, transmitting one or more PDUs of the first ADU of the first flow using the first resource configuration may include transmitting, using a (e.g., single) transmission occasion in accordance with the first resource configuration, one or more PDUs of the first ADU of the first flow and one or more PDUs of the second ADU received before the last PDU of the second ADU.

[0138] In a particular representative embodiment, transmitting at least a last PDU of the second ADU of the second flow using the second resource configuration has a timing offset that is after transmitting one or more PDUs of the first ADU of the first flow using the first resource configuration.

[0139] In certain representative embodiments, the first resource configuration may be associated with the first flow and / or the second flow, and in certain representative embodiments, any of the second resource configuration, the first time threshold, and / or the second time threshold may be associated with the first flow and / or the second flow.

[0140] In a particular representative embodiment, the ADUs of the first flow and the second flow are received by the WTRU 102 from another WTRU 102 (eg, using sidelink resources).

[0141] In certain representative embodiments, a second ADU of a second flow may correspond to a first ADU of a first flow, and / or vice versa. For example, one or more PDUs of a first ADU of a first flow may include identification information, timing information, and / or sequence information associated with the first ADU. For example, one or more PDUs of a second ADU of a second flow may include identification information, timing information, and / or sequence information associated with the second ADU. The identification information, timing information, and / or sequence information may indicate a correspondence between the PDUs and / or ADUs.

[0142] FIG. 6 is a procedural diagram illustrating another example procedure for synchronizing multiple flows. In a particular representative embodiment, the procedure of FIG. 6 may be generally performed by a WTRU 102, such as the WTRU 202. In FIG. 6, the WTRU 102 may transmit (e.g., to a base station) at 602 information indicating (1) an association between a first flow and a second flow, and (2) a maximum time difference between an ADU of the first flow and an ADU of the second flow. At 604, the WTRU 102 may receive (e.g., from a base station) information indicating any of a first resource configuration, a second resource configuration, a first time threshold, and a second time threshold (e.g., greater than the first time threshold). At 606, the WTRU 102 may receive one or more PDUs of the first ADU of the first flow and one or more PDUs of the second ADU of the second flow. After 606, the WTRU may transmit (e.g., to or towards) one or more PDUs of the first ADU of the first flow using a first transmission occasion indicated by the first resource configuration at 608. At 610, the WTRU 102 may transmit at least a last PDU of the second ADU of the second flow using a second transmission occasion indicated by the first resource configuration, provided that (1) the last PDU of the second ADU of the second flow is received after a first time threshold and a second time threshold have elapsed since receipt of the last PDU of the first ADU of the first flow.

[0143] In certain representative embodiments, the first resource configuration may be a first configured grant configuration and / or the second resource configuration may be a second configured grant configuration. For example, a size of a transmission occasion (e.g., a time and / or frequency resource) associated with the first resource configuration may be larger than a size of a transmission occasion associated with the second resource configuration. For example, the first resource configuration may include a first plurality of transmission occasions having a first periodicity and / or the second resource configuration may include a second plurality of transmission occasions having a second periodicity smaller than the first periodicity.

[0144] In a particular representative embodiment, transmitting one or more PDUs of a first ADU of a first flow using a first transmission occasion of a first resource configuration may include transmitting at least one other PDU of a second ADU of a second flow, which is received before a last PDU of the second ADU, using the first transmission occasion of the first resource configuration.

[0145] In certain representative embodiments, the first resource configuration may be associated with the first flow and / or the second flow. In certain representative embodiments, either the first time threshold and / or the second time threshold may be associated with the first flow and / or the second flow.

[0146] In a particular representative embodiment, the ADUs of the first flow and the second flow are received by the WTRU 102 from another WTRU 102 (eg, using sidelink resources).

[0147] In certain representative embodiments, a second ADU of a second flow may correspond to a first ADU of a first flow, and / or vice versa. For example, one or more PDUs of a first ADU of a first flow may include identification information, timing information, and / or sequence information associated with the first ADU. One or more PDUs of a second ADU of a second flow may include identification information, timing information, and / or sequence information associated with the second ADU. For example, the identification information, timing information, and / or sequence information may indicate a correspondence between the PDUs and / or ADUs of the flows.

[0148] FIG. 7 is a procedural diagram illustrating an example procedure for synchronizing multiple flows. In a particular representative embodiment, the procedure of FIG. 7 may generally be implemented by a base station, such as the gNB 180. At 702, the base station may receive information from the WTRU 102 indicating (1) an association between a first flow and a second flow, and (2) a maximum time difference between ADUs of the first flow and the second flow. At 704, the base station may transmit information to the WTRU indicating any of the first resource configuration, the second resource configuration, the first time threshold, and / or the second time threshold. At 706, the base station may receive (e.g., from the WTRU 102) one or more PDUs of the first ADU of the first flow using the first resource configuration. At 708, the base station may receive (e.g., from the WTRU 102) at least the last PDU of the second ADU of the second flow using the second resource configuration. For example, receipt of the last PDU of the second ADU of the second flow using the second resource configuration may indicate (e.g., to a base station) that the last PDU of the second ADU of the second flow was received by WTRU 102 (1) after a first threshold has elapsed since receipt by WTRU 102 of the last PDU of the first ADU of the first flow, and (2) before a second threshold has elapsed since receipt by WTRU 102 of the last PDU of the ADU of the first flow.

[0149] FIG. 8 is a procedural diagram illustrating another example procedure for synchronizing multiple flows. In a particular representative embodiment, the procedure of FIG. 8 may generally be implemented by a base station, such as the gNB 180. At 802, the base station may receive information from the WTRU 102 indicating (1) an association between a first flow and a second flow and (2) a maximum time difference between ADUs of the first flow and the second flow. At 804, the base station may transmit information to the WTRU 102 indicating any of a first resource configuration, a first time threshold, and / or a second time threshold. At 806, the base station may receive (e.g., from the WTRU 102) one or more PDUs of a first ADU of the first flow using a first transmission occasion of the first resource configuration. At 808, the base station may receive (e.g., from the WTRU 102) at least a last PDU of a second ADU in the second flow using a second transmission occasion of the first resource configuration. For example, reception of at least the last PDU of the second ADU in the second flow using the second transmission occasion may indicate (e.g., to a base station) that the last PDU of the second ADU of the second flow has been received by WTRU 102 after a first threshold and a second threshold have elapsed since WTRU 102's reception of the last PDU of the first ADU of the first flow.

[0150] FIG. 9 is a procedural diagram illustrating an example for transmitting multiple flows using priority levels. In a particular representative embodiment, the procedure of FIG. 9 may be generally performed by a WTRU 102, such as the WTRU 202. At 902, the WTRU 102 may receive (e.g., from a base station) first information indicating any of a first time threshold, a second time threshold, and / or a plurality of resource configurations associated with a plurality of priority levels. At 904, the WTRU 102 may receive (e.g., from another WTRU 102 and / or higher layers) a first protocol data unit (PDU) of a first flow. At 906, the WTRU 102 may transmit (e.g., to or toward a base station) a first PDU of the first flow using a first resource configuration of the plurality of resource configurations. At 908, the WTRU may receive (e.g., from another WTRU 102 and / or higher layers) a second PDU of a second flow. At 910, the WTRU 102 may determine a priority level for the second PDU based on the reception time of the second PDU, the reception time of the first PDU, the first time threshold, and the second time threshold. At 912, the WTRU 102 may transmit the second PDU of the second flow using one of a plurality of resource configurations associated with the determined priority level.

[0151] In certain representative embodiments, determining the priority level of the second PDU may be based on a difference between a reception time of the second PDU and a reception time of the first PDU, a first time threshold, and a second time threshold, as described herein. For example, the determined priority level may be the first priority level, provided that the difference is less than the first time threshold. Transmitting the second PDU of the second flow may use a first resource configuration associated with the first priority level. For example, transmitting the first PDU and transmitting the second PDU may use one (e.g., a single) transmission occasion indicated by the first resource configuration.

[0152] In certain representative embodiments, the determined priority level may be the second priority level, provided that the difference is greater than the first time threshold and less than the second time threshold. For example, transmitting the second PDU of the second flow may use a second resource configuration of the multiple resource configurations associated with the second priority level. For example, transmitting the first PDU may use a first transmission occasion indicated by the first resource configuration, and transmitting the second PDU may use a second transmission occasion indicated by the second resource configuration (e.g., following the first transmission occasion and / or offset from the first transmission occasion). For example, the second transmission occasion may be offset in time from the first transmission occasion.

[0153] In certain representative embodiments, the WTRU 102 may transmit (eg, prior to receiving the first information) second information indicating an association between the first flow and the second flow.

[0154] In certain representative embodiments, a first PDU may be associated with a first ADU of a first flow and / or a second PDU may be associated with a second ADU of a second flow. For example, the first PDU may include identification, timing and / or sequence information associated with the first ADU and / or the first flow. For example, the second PDU may include identification, timing and / or sequence information associated with the second ADU and / or the second flow. For example, the identification, timing and / or sequence information may be used to determine a correspondence between the PDUs.

[0155] In one particular representative embodiment, the information contained in the second ADU information is related to the information contained in the first ADU.

[0156] FIG. 10 is a procedural diagram illustrating an example for receiving multiple flows using priority levels. In certain representative embodiments, the procedure of FIG. 10 may generally be implemented by a base station, such as the gNB 180. At 1002, the base station may transmit (e.g., to the WTRU 102) first information indicating any of a plurality of resource configurations associated with a first time threshold, a second time threshold, and / or a plurality of priority levels. At 1004, the base station may receive (e.g., from the WTRU 102) a first PDU of a first flow using a first resource configuration of the plurality of resource configurations. At 1008, the base station may receive (e.g., from the WTRU 102) a second PDU of a second flow. For example, one of the plurality of resource configurations used (e.g., by the WTRU 102) to transmit the second PDU may be associated with a priority level of the second PDU. For example, the priority level of the second PDU may indicate (e.g., to a base station) a relationship between the reception time of the second PDU (e.g., by the WTRU 102), the reception time of the first PDU (e.g., by the WTRU 102), the first time threshold, and the second time threshold.

[0157] FIG. 11 is a procedural diagram illustrating an example procedure for adjusting resource configuration information for synchronizing multiple flows. In a particular representative embodiment, the procedure of FIG. 11 may be generally performed by a WTRU 102, such as the WTRU 202. At 1102, the WTRU 102 may receive (e.g., from a base station) information indicating either one or more first resource configurations, one or more second resource configurations, and / or a time threshold. At 1104, the WTRU 102 may transmit (e.g., to a base station) one or more PDUs associated with a first flow using the one or more first resource configurations. At 1106, the WTRU 102 may receive (e.g., from a base station) one or more PDUs associated with a second flow using the one or more second resource configurations. After 1106, on the condition that the RTT between a first PDU of the one or more PDUs associated with the first flow and a second PDU of the one or more PDUs associated with the second flow is greater than a time threshold, the WTRU 102 may transmit (e.g., to a base station) adjustment information for one or more parameters of either the first resource configuration and / or the second resource configuration.

[0158] In certain representative embodiments, the adjustment information may be determined (e.g., by the WTRU 102) to ensure synchronization between the flows. For example, the adjustment information may indicate changes to one or more parameters, such as to satisfy a joint QoS for the flows, as described herein.

[0159] In a particular representative embodiment, the first resource configuration may include one or more CG configurations. In a particular representative embodiment, the second resource configuration may include one or more SPS configurations.

[0160] In certain representative embodiments, the adjustment information may include information indicating changes to any of the offset time, periodicity, payload size, and / or amount of time / frequency resources.

[0161] In certain representative embodiments, one of the first resource configurations may be associated with a different priority level as described herein.

[0162] FIG. 12 is a procedural diagram illustrating another example procedure for adjusting resource configuration information for synchronizing multiple flows. In a particular representative embodiment, the procedure of FIG. 12 may generally be performed by a WTRU 102, such as the WTRU 202. At 1202, the WTRU 102 may receive information (e.g., from a base station) indicating any of a first resource configuration, a second resource configuration, a third resource configuration, and / or a time threshold. At 1204, the WTRU 102 may transmit (e.g., to a base station) one or more PDUs associated with a first flow using the first resource configuration. At 1206, the WTRU may receive one or more PDUs associated with a second flow using the second resource configuration. After 1206, on the condition that the RTT between a first PDU of the one or more PDUs associated with the first flow and a second PDU of the one or more PDUs associated with the second flow is greater than a time threshold, the WTRU 102 may switch to transmitting the one or more PDUs associated with the first flow using at least a third resource configuration at 1208.

[0163] In a particular representative embodiment, the switching at 1208 may be determined (e.g., by the WTRU 102) to ensure synchronization between the flows. For example, the switching may be performed to satisfy a joint QoS for the flows, as described herein.

[0164] In a particular representative embodiment, the first resource configuration and / or the third resource configuration may include one or more CG configurations. In a particular representative embodiment, the second resource configuration may include one or more SPS configurations.

[0165] In certain representative embodiments, the first resource configuration and / or the third resource configuration may differ in any of the offset time, periodicity, payload size, and / or amount of time / frequency resources.

[0166] In certain representative embodiments, any one of the first resource configuration and / or the third resource configuration may be associated with a different priority level, as described herein.

[0167] FIG. 13 is a procedural diagram illustrating a further example procedure for adjusting resource configuration information for synchronizing multiple flows. In a particular representative embodiment, the procedure of FIG. 13 may be generally performed by a WTRU 102, such as the WTRU 202. At 1302, the WTRU 102 may receive information indicating any of a first resource configuration, a second resource configuration, a third resource configuration, and / or a time threshold. At 1304, the WTRU 102 may transmit (e.g., forward to a base station) one or more PDUs associated with a first flow using the first resource configuration. At 1306, the WTRU 102 may receive (e.g., from a base station) one or more PDUs associated with a second flow using the second resource configuration. At 1308, on the condition that the RTT between a first PDU of the one or more PDUs associated with the first flow and a second PDU of the one or more PDUs associated with the second flow is greater than a time threshold, the WTRU 102 may transmit information indicating that the RTT between the first PDU of the one or more PDUs associated with the first flow and a second PDU of the one or more PDUs associated with the second flow is greater than a time threshold. At 1310, after 1308, the WTRU 102 may receive one or more PDUs associated with the second flow using at least the third resource configuration.

[0168] In a particular representative embodiment, the switch at 1208 may be determined (e.g., by the WTRU 102) to ensure synchronization between the flows. For example, the switch may be performed to satisfy a joint QoS for the flows as described herein.

[0169] In a particular representative embodiment, the first resource configuration and / or the third resource configuration may include one or more CG configurations. In a particular representative embodiment, the second resource configuration may include one or more SPS configurations.

[0170] In certain representative embodiments, the first resource configuration and / or the third resource configuration may differ in any of the offset time, periodicity, payload size, and / or amount of time / frequency resources.

[0171] FIG. 14 is a procedural diagram illustrating an example procedure for adjusting resource configuration information for synchronizing multiple flows. In certain representative embodiments, the procedure of FIG. 14 may generally be implemented by a base station, such as the gNB 180. At 1402, the base station may transmit (e.g., to the WTRU 102) information indicating any of one or more first resource configurations, one or more second resource configurations, and / or a time threshold. At 1404, the base station may receive (e.g., from the WTRU 102) one or more PDUs associated with a first flow using the one or more first resource configurations. At 1406, the base station may receive (e.g., from the WTRU 102) one or more PDUs associated with a second flow using the one or more second resource configurations. At 1408, the base station may receive (e.g., from the WTRU) adjustment information for one or more parameters of any of the first resource configurations and / or the second resource configuration. For example, the adjustment information may be associated with an RTT between a first PDU of one or more PDUs associated with a first flow and a second PDU of one or more PDUs associated with a second flow that is greater than a time threshold.

[0172] In certain representative embodiments, the adjustment information may be associated with one or more parameters of a resource configuration, as described herein.

[0173] In certain representative embodiments, the coordination information may be determined, such as to ensure synchronization between flows, as described herein.

[0174] FIG. 15 is a procedural diagram illustrating another example procedure for adjusting resource configuration information for synchronizing multiple flows. In certain representative embodiments, the procedure of FIG. 15 may generally be implemented by a base station, such as the gNB 180. At 1502, the base station may transmit (e.g., to the WTRU 102) information indicating any of a first resource configuration, a second resource configuration, a third resource configuration, and / or a time threshold. At 1504, the base station may receive (e.g., from the WTRU 102) one or more PDUs associated with the first flow using the first resource configuration. At 1506, the base station may receive (e.g., from the WTRU 102) one or more PDUs associated with the second flow using the second resource configuration. At 1508, the base station may receive (e.g., from the WTRU 102) one or more PDUs associated with the first flow using at least the third resource configuration. For example, use of the third resource configuration may indicate (e.g., to a base station) an RTT between a first PDU of the one or more PDUs associated with the first flow and a second PDU of the one or more PDUs associated with the second flow that is greater than a time threshold.

[0175] In certain representative embodiments, adjustment information may be determined for any of the resource configurations, as described herein. For example, the adjustment information may ensure that the RTT meets a particular requirement of the flow. For example, the adjustment information may modify one or more parameters, as described herein, such that synchronization between the flows is ensured.

[0176] FIG. 16 is a procedural diagram illustrating a further example procedure for adjusting resource configuration information for synchronizing multiple flows. In certain representative embodiments, the procedure of FIG. 16 may generally be implemented by a base station, such as the gNB 180. At 1602, the base station may transmit (e.g., to the WTRU 102) information indicating any of a first resource configuration, a second resource configuration, a third resource configuration, and / or a time threshold. At 1604, the base station may receive (e.g., from the WTRU 102) one or more PDUs associated with a first flow using the first resource configuration. At 1606, the base station may receive (e.g., from the WTRU 102) one or more PDUs associated with a second flow using the second resource configuration. At 1608, the base station may receive (e.g., from the WTRU 102) information indicating that an RTT between a first PDU of the one or more PDUs associated with the first flow and a second PDU of the one or more PDUs associated with the second flow is greater than a time threshold. At 1610, the base station may receive (eg, from the WTRU 102) one or more PDUs associated with the second flow using at least the third resource configuration.

[0177] In certain representative embodiments, the use of the third resource configuration may ensure that flow synchronization is satisfied, for example, the use of the third resource configuration may reduce the RTT between the first flow and the second flow.

[0178] FIG. 17 is a procedural diagram illustrating an example procedure for maintaining joint quality of service (QoS) for multiple flows. In a particular representative embodiment, the procedure of FIG. 17 may be generally performed by a WTRU 102, such as the WTRU 202. At 1702, the WTRU 102 may receive (e.g., from a base station) information indicating either a first resource configuration, a second resource configuration, and / or joint quality of service (QoS) information associated with multi-flow synchronization. At 1704, the WTRU 102 may receive (e.g., from a base station) a plurality of PDUs of a first flow and a plurality of PDUs of a second flow. At 1706, the WTRU 102 may transmit (e.g., to a base station) a first set of PDUs of the first flow and a second set of PDUs of the second flow using either the first resource configuration and / or the second resource configuration. At 1708, the WTRU 102 may determine (e.g., estimate) a change in QoS associated with the second flow based on the change in QoS associated with the first flow. At 1710, the WTRU 102 may modify either the first resource configuration and / or the second resource configuration, provided that the change in QoS associated with the second flow does not satisfy the joint QoS. At 1712, the WTRU 102 may transmit (e.g., to a base station) a third set of PDUs for the first flow and a fourth set of PDUs for the second flow using either the modified first resource configuration and / or the modified second resource configuration.

[0179] In certain representative embodiments, the first resource configuration may be a first configured grant configuration and / or the second resource configuration may be a second configured grant configuration. For example, a size of a transmission occasion associated with the first resource configuration may be greater than a size of a transmission occasion associated with the second resource configuration. For example, the first resource configuration may include (e.g., information indicative of) a first plurality of transmission occasions having a first periodicity and / or the second resource configuration may include a second plurality of transmission occasions having a second periodicity that is less than the first periodicity.

[0180] In certain representative embodiments, either the first resource configuration and / or the second resource configuration may be associated with the first flow and / or the second flow.

[0181] In certain representative embodiments, the PDUs of the first flow and / or the second flow may be received from another WTRU 102 (eg, using sidelink resources).

[0182] In a particular representative embodiment, a PDU of a first flow may comprise one or more ADUs of the first flow and / or a PDU of a second flow may comprise one or more ADUs of the second flow.

[0183] In certain representative embodiments, one or more of the PDUs of a first flow may include identification, timing, and / or sequence information associated with the first flow. In certain representative embodiments, one or more of the PDUs of a second flow may include identification, timing, and / or sequence information associated with the second flow. For example, the identification, timing, and / or sequence information may indicate a correspondence between the PDUs of the flows.

[0184] In certain representative embodiments, the joint QoS information may include any of a synchronization time window, a latency, and / or a data rate associated with the multi-flow synchronization. For example, the joint QoS information may be associated with any of the first flow, the second flow, the first resource configuration, and / or the second resource configuration.

[0185] FIG. 18 is a procedural diagram illustrating another example procedure for maintaining joint quality of service (QoS) for multiple flows. In a particular representative embodiment, the procedure of FIG. 18 may be generally performed by a WTRU 102, such as the WTRU 202. At 1802, the WTRU 102 may receive (e.g., from a base station) information indicating either a first resource configuration, a second resource configuration, and / or joint quality of service (QoS) information associated with multi-flow synchronization. At 1804, the WTRU 102 may receive (e.g., from another WTRU 102 and / or from a higher layer) a plurality of PDUs of a first flow and a plurality of PDUs of a second flow. At 1806, the WTRU 102 may transmit (e.g., to a base station) a first set of PDUs of the first flow and a second set of PDUs of the second flow using either the first resource configuration and / or the second resource configuration. At 1808, the WTRU 102 may determine (e.g., estimate) a change in QoS associated with the second flow based on the change in QoS associated with the first flow. At 1810, if the change in QoS associated with the second flow does not satisfy the joint QoS, the WTRU 102 may transmit (e.g., to a base station) information indicating a change (e.g., an adjustment) to either the first resource configuration and / or the second resource configuration.

[0186] In a particular representative embodiment, the WTRU 102 may receive (e.g., from a base station) adjustment information associated with either the first resource configuration and / or the second resource configuration. For example, the adjustment information may indicate a change to one or more parameters of either of the resource configurations. For example, the adjustment information may ensure that a joint QoS is satisfied for the flows.

[0187] In a particular representative embodiment, the WTRU 102 may transmit (e.g., to a base station) the third set of PDUs and the fourth set of PDUs using either the modified first resource configuration and / or the modified second resource configuration.

[0188] In certain representative embodiments, the first resource configuration may be a first configured grant configuration and / or the second resource configuration may be a second configured grant configuration. For example, a size of a transmission occasion associated with the first resource configuration may be greater than a size of a transmission occasion associated with the second resource configuration. For example, the first resource configuration may include a first plurality of transmission occasions having a first periodicity and / or the second resource configuration may include a second plurality of transmission occasions having a second periodicity that is less than the first periodicity.

[0189] In a particular representative embodiment, either the first resource configuration and / or the second resource configuration is associated with the first flow and / or the second flow.

[0190] In certain representative embodiments, the PDUs of the first flow and / or the second flow are received from another WTRU (eg, using sidelink resources).

[0191] In a particular representative embodiment, a PDU of a first flow may comprise one or more ADUs of the first flow and / or a PDU of a second flow may comprise one or more ADUs of the second flow.

[0192] In certain representative embodiments, one or more of the PDUs of a first flow may include identification, timing, and / or sequence information associated with the first flow. In certain representative embodiments, one or more of the PDUs of a second flow may include identification, timing, and / or sequence information associated with the second flow. For example, the identification, timing, and / or sequence information may indicate a correspondence between the PDUs of the flows.

[0193] In certain representative embodiments, the joint QoS information may include any of a synchronization time window, latency, and / or data rate associated with the multi-flow synchronization.

[0194] In certain representative embodiments, the joint QoS information may be associated with any of the first flow, the second flow, the first resource configuration, and / or the second resource configuration.

[0195] FIG. 19 is a procedural diagram illustrating a further example procedure for synchronizing multiple flows. In a particular representative embodiment, the procedure of FIG. 19 may be generally performed by a WTRU 102, such as the WTRU 202. At 1902, the WTRU 102 may transmit (e.g., to a base station) information indicating a maximum time difference between a first flow and a second flow. For example, the second flow and the first flow may be associated with each other. At 1904, the WTRU 102 may receive (e.g., from a base station) information indicating either a first resource configuration and / or a second resource configuration. At 1906, the WTRU 102 may receive (e.g., from another WTRU 102 and / or from a higher layer) one or more PDUs of the first flow and one or more PDUs of the second flow. At 1908, the WTRU 102 may transmit (e.g., to a base station) one or more PDUs of the first flow using the first resource configuration. At 1910, the WTRU 102 may transmit (e.g., to a base station) at least the last PDU of the second flow using the second resource configuration, provided that (1) the last PDU of the second flow is received after a first time threshold has elapsed since receipt of the associated PDU of the first flow and (2) before a second time threshold has elapsed since receipt of the associated PDU of the first flow.

[0196] FIG. 20 is a procedural diagram illustrating a further example for transmitting multiple flows using priority levels. In a particular representative embodiment, the procedure of FIG. 20 may be generally performed by a WTRU 102, such as the WTRU 202. At 2002, the WTRU 102 may receive (e.g., from a base station) reception information indicating multiple resource configurations associated with multiple priority levels. At 2004, the WTRU 102 may receive (e.g., from another WTRU 102 and / or higher layers) one or more protocol data units (PDUs) of a first flow and one or more PDUs of a second flow. At 2006, the WTRU 102 may transmit (e.g., to a base station) one or more PDUs of the first flow using a first resource configuration of the multiple resource configurations. In 2008, the WTRU 102 may determine a priority level of at least one of the PDUs of the second flow based on a reception time of at least one of the PDUs of the second flow, a reception time of at least one of the PDUs of the first flow, a first time threshold, and a second time threshold. For example, if the difference in reception time meets the first threshold, the priority may be a first priority. For example, if the difference in reception time meets the second threshold but does not meet the first threshold, the priority may be a second priority. For example, if the difference in reception time does not meet the first threshold and does not meet the second threshold, the priority may be a third priority. In 2010, the WTRU 102 may transmit (e.g., to a base station) at least one of the PDUs of the second flow using a second resource configuration of the multiple resource configurations associated with the determined priority level.

[0197] FIG. 21 is a procedural diagram illustrating a further example procedure for adjusting resource configuration information for synchronizing multiple flows. In certain representative embodiments, the procedure of FIG. 21 may generally be performed by a WTRU 102, such as the WTRU 202. At 2102, the WTRU 102 may receive information (e.g., from a base station) indicating either a first resource configuration or a second resource configuration. At 2104, the WTRU 102 may transmit (e.g., to a base station) one or more PDUs associated with the first flow using the first resource configuration. At 2106, the WTRU 102 may receive (e.g., from a base station) one or more PDUs associated with the second flow using the second resource configuration. At 2108, on the condition that the RTT between the first PDU associated with the first flow and the second PDU associated with the second flow is greater than a time threshold, the WTRU 102 may transmit (e.g., to a base station) information indicating an adjustment to one or more parameters of either the first resource configuration and / or the second resource configuration.

[0198] FIG. 22 is a procedural diagram illustrating an example procedure for maintaining joint quality of service (QoS) for multiple flows. In a particular representative embodiment, the procedure of FIG. 22 may be generally performed by a WTRU 102, such as the WTRU 202. At 2202, the WTRU 102 may receive (e.g., from a base station) information indicating either a first resource configuration, a second resource configuration, and / or joint quality of service (QoS) information associated with multi-flow synchronization. At 2204, the WTRU 102 may receive (e.g., from another WTRU 102 and / or from a higher layer) a plurality of PDUs of a first flow and a plurality of PDUs of a second flow. At 2206, the WTRU 102 may transmit (e.g., to a base station) a first set of PDUs of the first flow and a second set of PDUs of the second flow using either the first resource configuration and / or the second resource configuration. At 2208, the WTRU 102 may determine (e.g., estimate) a change in QoS associated with the first flow and a change in QoS associated with the second flow. At 2210, provided that the change in QoS associated with the first flow and / or the second flow does not satisfy the joint QoS, the WTRU 102 may modify one or more parameters of either the first resource configuration and / or the second resource configuration. In another embodiment, the WTRU 102 may select or receive another (e.g., a third) resource configuration. At 2212, the WTRU 102 may transmit (e.g., to a base station) the third set of PDUs and the fourth set of PDUs for the first flow using either the modified first resource configuration and / or the modified second resource configuration. In another embodiment, the third and / or fourth sets of PDUs may be transmitted using the other (e.g., the third resource configuration).

[0199] In a particular representative embodiment, the WTRU 102 may receive information indicating first and second durations and information indicating a plurality of transmission configurations including a first default transmission configuration associated with a first flow and a second default transmission configuration associated with a second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. Conditional on the second PDU being received before the first duration elapses relative to receiving the first PDU, the WTRU 102 may transmit the second PDU using the second default transmission configuration.

[0200] In a particular representative embodiment, the WTRU 102 may receive information indicating first and second durations and information indicating a plurality of transmission configurations including a first default transmission configuration associated with a first flow and a second default transmission configuration associated with a second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. Provided that the second PDU is received after the first duration has elapsed for receiving the first PDU and before the second duration has elapsed for receiving the first PDU, the WTRU 102 may transmit the second PDU using one of the plurality of transmission configurations associated with a priority of the second flow that is higher than a priority associated with the second default transmission configuration.

[0201] In a particular representative embodiment, the WTRU 102 may receive information indicating a first and a second duration and information indicating a plurality of transmission configurations including a first default transmission configuration associated with a first flow and a second default transmission configuration associated with a second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. Conditional on the second PDU being received after the first duration has elapsed for receiving the first PDU and after the second duration has elapsed for receiving the first PDU, the WTRU 102 may transmit information indicating a reception status associated with the second PDU. The WTRU 102 may receive information indicating one of the plurality of transmission configurations associated with the second PDU and / or the second flow. The WTRU 102 may transmit the second PDU using the indicated one of the plurality of transmission configurations.

[0202] In a particular representative embodiment, the WTRU 102 may receive information indicating a first and a second duration and information indicating a plurality of transmission configurations including a first default transmission configuration associated with a first flow and a second default transmission configuration associated with a second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. Provided that the second PDU is received after the first duration has elapsed for receiving the first PDU and after the second duration has elapsed for receiving the first PDU, the WTRU may transmit information indicating a reception status associated with the second PDU. The WTRU 102 may then receive information indicating to drop the second PDU.

[0203] In a particular representative embodiment, the WTRU 102 may receive information indicating first and second durations and information indicating a plurality of transmission configurations including a first default transmission configuration associated with a first flow and a second default transmission configuration associated with a second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. The WTRU may transmit the last PDU of the first ADU using the first default transmission configuration and transmit the second PDU of the second ADU using the second default transmission configuration, provided that (1) the last PDU of the first ADU is received before the first duration elapses for receiving the first PDU of the first ADU and / or (2) the second PDU of the second ADU is received before the first duration elapses for receiving the first PDU of the first ADU.

[0204] In a particular representative embodiment, the WTRU 102 may receive information indicating the first and second durations and information indicating a plurality of transmission configurations including a first default transmission configuration associated with the first flow and a second default transmission configuration associated with the second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. The WTRU 102 may receive a third PDU of the first ADU corresponding to the first flow. Conditional on (1) a third PDU of the first ADU is received after a first duration has elapsed for receiving the first PDU of the first ADU and before a second duration has elapsed for receiving the first PDU of the first ADU, and / or (2) a second PDU of the second ADU is received after the first duration has elapsed for receiving the first PDU of the first ADU and before a second duration has elapsed for receiving the first PDU of the first ADU, the WTRU 102 may transmit the third PDU using one of a plurality of transmission configurations associated with a higher priority than the priority associated with the first default transmission configuration and transmit the second PDU using the second default transmission configuration.

[0205] In a particular representative embodiment, the WTRU 102 may receive information indicating first and second durations and information indicating a plurality of transmission configurations including a first default transmission configuration associated with a first flow and a second default transmission configuration associated with a second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. Provided that the second PDU is received after the first and second durations have elapsed for receiving the first PDU and before the third duration has elapsed for receiving the first PDU, the WTRU 102 may transmit the second PDU using one of the plurality of transmission configurations associated with a priority of the second flow that is higher than a priority associated with the second default transmission configuration.

[0206] In a particular representative embodiment, the WTRU 102 may receive information indicating a first and a second duration and information indicating a plurality of transmission configurations including a first default transmission configuration associated with a first flow and a second default transmission configuration associated with a second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. Conditional on the second PDU being received after the first and second durations have elapsed for receiving the first PDU and before the third duration has elapsed for receiving the first PDU, the WTRU 102 may transmit information indicating a reception status associated with the second PDU. The WTRU 102 may receive information indicating one of a plurality of transmission configurations associated with the second PDU and / or the second flow, and the WTRU 102 may transmit the second PDU using the indicated one of the plurality of transmission configurations.

[0207] In a particular representative embodiment, the WTRU 102 may receive information indicating the first and second durations and information indicating a plurality of transmission configurations including a first default transmission configuration associated with a first flow and a second default transmission configuration associated with a second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. Provided that the second PDU is received after the first, second, and third durations have elapsed for receiving the first PDU and before the third duration has elapsed for receiving the first PDU, the WTRU may transmit information indicating a reception status associated with the second PDU. The WTRU 102 may receive information indicating one of a plurality of transmission configurations associated with the second PDU and / or the second flow, and the WTRU may transmit the second PDU using the indicated one of the plurality of transmission configurations.

[0208] In a particular representative embodiment, the WTRU 102 may receive information indicating a first and second duration and information indicating a plurality of transmission configurations including a first default transmission configuration associated with a first flow and a second default transmission configuration associated with a second flow. The WTRU 102 may receive a first protocol data unit (PDU) corresponding to the first flow and may transmit the first PDU using the first default transmission configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. Provided that the second PDU is received after the first, second, and third durations have elapsed for receiving the first PDU and before the third duration has elapsed for receiving the first PDU, the WTRU 102 may transmit information indicating a reception status associated with the second PDU. The WTRU 102 may then receive information indicating to drop the second PDU.

[0209] In a particular representative embodiment, the WTRU 102 may receive information indicating multiple resource configurations, including a first resource configuration associated with a first flow and a second resource configuration associated with a second flow. The WTRU 102 may communicate (e.g., transmit or receive) a first protocol data unit (PDU) corresponding to the first flow using the first resource configuration. The WTRU 102 may communicate (e.g., transmit or receive) a second PDU corresponding to the second flow using the second resource configuration. Subject to a round trip time (RTT) associated with either the first flow and / or the second flow being above a threshold, the WTRU 102 may determine a change to either the first and / or second resource configurations to reduce the RTT below the threshold. The WTRU 102 may then transmit and / or receive one or more PDUs of either the first and / or second flows using either the changed first and / or second resource configurations. In other embodiments, the WTRU 102 may use QoS requirements in combination with or instead of the RTT.

[0210] In a particular representative embodiment, the WTRU 102 may receive information indicating multiple resource configurations including a first resource configuration associated with a first flow and a second resource configuration associated with a second flow. The WTRU 102 may communicate (e.g., transmit or receive) a first protocol data unit (PDU) corresponding to the first flow using the first resource configuration. The WTRU 102 may communicate (e.g., transmit or receive) a second PDU corresponding to the second flow using the second resource configuration. Provided that a round trip time (RTT) associated with either the first flow and / or the second flow falls below a threshold, the WTRU may determine a modification to either the first and / or second resource configurations to increase the RTT above the threshold. The WTRU may then transmit and / or receive one or more PDUs of either the first and / or second flow using either the modified first and / or second resource configurations. In other embodiments, the WTRU 102 may use QoS requirements in combination with or instead of the RTT.

[0211] In some embodiments and examples herein, procedures are described that may be performed for multi-flow synchronization on a per-PDU and / or per-ADU basis, while in other examples, multi-flow synchronization may be performed on a per-PDU set basis.

[0212] conclusion Although features and elements are provided above in specific combinations, one skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited in terms of the specific embodiments described in this application, which are intended as illustrations of various aspects. As will be apparent to those skilled in the art, many modifications and variations may be made without departing from the spirit and scope of the present invention. No element, operation, or instruction used in the description of this application should be construed as critical or essential to the invention unless expressly set forth as such. In addition to those enumerated herein, functionally equivalent methods and apparatuses within the scope of the present disclosure will be apparent to those skilled in the art from the foregoing description. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that the present disclosure is not limited to any particular method or system.

[0213] The foregoing embodiments are discussed with respect to the terminology and structure of infrared-enabled devices (i.e., infrared emitters and receivers) for simplicity, however, the discussed embodiments are not limited to these systems and may also be applied to other systems that use other forms of electromagnetic waves, or non-electromagnetic waves such as acoustic waves.

[0214] It should also be understood that the terms used herein are for purposes of describing particular embodiments only and are not intended to be limiting. As used herein, the term "video" or "image" may mean either a snapshot, a single image, and / or multiple images displayed over time. As another example, the term "user equipment" and its abbreviation "UE", the term "remote", and / or the term "head mounted display" and its abbreviation "HMD" as referred to herein may mean or include (i) a wireless transmitting and / or receiving unit (WTRU), (ii) any of several embodiments of a WTRU, (iii) a wireless enabled and / or wired enabled (e.g., tetherable) device specifically configured to have some or all of the structure and functionality of a WTRU, (iii) a wireless enabled and / or wired enabled device configured to have less than all of the structure and functionality of a WTRU, or (iv) the like. Details of an exemplary WTRU that may represent any WTRU listed herein are provided herein with respect to FIGS. 1A-1D. As another example, various embodiments disclosed herein above and below are described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than a head-mounted display may be utilized and that the present disclosure and any or all of the various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adaptive reality experience.

[0215] In addition, the methods provided herein may be implemented in a computer program, software, or firmware embodied 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), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0216] Modifications of the methods, apparatus, and systems provided above are possible without departing from the scope of the present invention. In view of the wide variety of embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be construed as limiting the scope of the following claims. For example, the embodiments provided herein include a portable device, which may include or be utilized with any suitable voltage source, such as a battery providing any suitable voltage.

[0217] Further, in the above embodiments, it should be noted that processing platforms, computing systems, controllers, and other devices including processors. These devices may include at least one Central Processing Unit (CPU) and memory. In accordance with the practices of those skilled in the art of computer programming, references to operations and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such operations and operations or instructions may be referred to as being "executed," "computer executed," or "CPU executed."

[0218] Those skilled in the art will appreciate that the operations and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. The electrical system represents data bits that may cause a resultant transformation or reduction of the electrical signals, and maintains the data bits in memory locations of the memory system, thereby reconfiguring or otherwise altering the operation of the CPU and the processing of other signals. The memory locations in which the data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be appreciated that the embodiments are not limited to the platforms or CPUs mentioned above, and that other platforms and CPUs may support the methods provided.

[0219] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read only memory (ROM)) mass storage system readable by a CPU. The computer readable medium may include computer readable media that resides exclusively on a processing system, or distributed, cooperative or interconnected among multiple interconnected processing systems that may be local or remote to a processing system. It should be understood that the embodiments are not limited to the memories mentioned above and that other platforms and memories may support the methods provided.

[0220] In an example embodiment, any of the operations, processes, etc. described herein may be implemented as computer readable instructions stored on a computer readable medium. The computer readable instructions may be executed by a processor of a mobile, a network element, and / or any other computing device.

[0221] There is little distinction between hardware and software implementations of aspects of the system. Whether to use hardware or software is generally a design choice that represents a cost vs. efficiency tradeoff (although in some circumstances the choice between hardware and software may be important). There may be a variety of vehicles (e.g., hardware, software, and / or firmware) in which the processes and / or systems and / or other techniques described herein may be effective, and the preferred vehicle may vary depending on the context in which the processes and / or systems and / or other techniques are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may select a primarily hardware and / or firmware vehicle. If flexibility is paramount, the implementer may select a primarily software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.

[0222] The foregoing detailed description has illustrated various embodiments of devices and / or processes through the use of block diagrams, flow charts, and / or examples. To the extent that such block diagrams, flow charts, and / or examples include one or more functions and / or operations, it will be appreciated by those skilled in the art that each function and / or operation within such block diagrams, flow charts, or examples may be individually and / or collectively implemented by a wide range of hardware, software, firmware, or substantially any combination thereof. In one embodiment, some portions of the subject matter described herein may be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated forms. However, those skilled in the art will recognize that certain aspects of the embodiments disclosed herein may be equivalently implemented, in whole or in part, in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as substantially any combination thereof, and that designing circuitry and / or writing software and / or firmware code is within the skill of those skilled in the art in light of this disclosure. In addition, those skilled in the art will recognize that the subject matter mechanisms described herein may be distributed as program products in a variety of forms, and that representative embodiments of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually effect the distribution. Examples of signal bearing media include, but are not limited to, recordable type media such as floppy disks, hard disk drives, CDs, DVDs, digital tape, computer memory, and transmission type media such as digital and / or analog communications media (e.g., fiber optic cables, wave guides, wired communications links, wireless communications links, etc.).

[0223] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner described herein and then use engineering techniques to integrate such described devices and / or processes into a data processing system. That is, at least a portion of the devices and / or processes described herein may be integrated into a data processing system through a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, memory such as volatile and non-volatile memory, a processor such as a microprocessor and a digital signal processor, computing entities such as an operating system, drivers, graphical user interfaces, and application programs, one or more interactive devices such as a touchpad or screen, and / or a control system including feedback loops and control motors (e.g., feedback to sense position and / or velocity, control motors to move and / or adjust components and / or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communication systems and / or network computing / communication systems.

[0224] The subject matter described herein may illustrate different components that are included within or connected to different other components. It should be understood that such depicted architectures are merely examples, and that in fact many other architectures that achieve the same functionality may be implemented. Conceptually, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Thus, any two components herein that are combined to achieve a particular functionality may be considered to be "associated" with one another such that the desired functionality is achieved, regardless of the architecture or intervening components. Similarly, any two components so associated may be considered to be "operably connected" or "operably coupled" with one another to achieve the desired functionality, and any two components that can be associated in this way may be considered to be "operably couplable" with one another to achieve the desired functionality. Examples of operably coupleable include, but are not limited to, physically matable and / or physically interacting components, and / or wirelessly interactable and / or wirelessly interacting components, and / or logically interacting and / or logically interacting components.

[0225] With respect to the use of substantially any plural and / or singular term herein, those of skill in the art may convert from plural to singular and / or from singular to plural as appropriate to the context and / or application. For purposes of clarity, various singular / plural permutations may be expressly set forth herein.

[0226] In general, those skilled in the art will understand that the terms used in this specification, and particularly in the appended claims (e.g., the body of the appended claims), are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," and the term "includes" should be interpreted as "includes but is not limited to"). Furthermore, those skilled in the art will understand that where a specific number of recitations of an introduced claim are intended, such intention is expressly set forth in the claim, and in the absence of such recitation, no such intention exists. For example, where only one item is intended, the term "single" or similar language may be used. To aid in understanding, the following appended claims and / or the description of this specification may include the use of the introductory phrases "at least one" and "one or more" to introduce the claim recitations. However, the use of such phrases should not be interpreted as meaning that the introduction of a claim recitation with the indefinite article "a" or "an" limits any particular claim that includes such an introduced claim recitation to an embodiment that includes only such one recitation, even if the same claim contains the introductory phrase "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. In addition, those skilled in the art will recognize that even if a specific number of recitations of an introduced claim are explicitly recited, such recitation should be interpreted to mean at least the recited number (e.g., the simple recitation "two recitations" without any other qualifiers means at least two recitations, or more than two recitations).Furthermore, when notation similar to "such as at least one of A, B, and C" is used, such structure is generally intended as a person of ordinary skill in the art would understand the notation (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). When notation similar to "such as at least one of A, B, or C" is used, such structure is generally intended as a person of ordinary skill in the art would understand the notation (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). Those skilled in the art will further appreciate that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" should be understood to include the possibilities of "A" or "B" or "A and B." Additionally, as used herein, the term "any of" followed by a list of items and / or a list of categories of items is intended to include "any of," "any combination of," "any more than," and / or "any more than," of the items and / or categories of items, individually or in combination with other items and / or other categories of items. Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. Also, as used herein, the term "multiple" is intended to be synonymous with "a plurality."

[0227] In addition, where features or aspects of the disclosure are described in terms of a Markush group, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual members or subgroups of members of the Markush group.

[0228] As will be appreciated by those skilled in the art, for all purposes, including in terms of providing a written description, all ranges disclosed herein also encompass any possible subranges and combinations of subranges thereof. Any recited range can be readily recognized as fully descriptive and allowing the same range to be broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, a middle third, an upper third, etc. As will also be appreciated by those skilled in the art, all words such as "up to," "at least," "greater than," "less than" and the like refer to ranges that include the recited numbers and that can be further broken down into subranges as discussed above. Finally, as will be appreciated by those skilled in the art, a range includes each individual element. Thus, for example, a group having 1 to 3 cells refers to a group having 1, 2, or 3 cells. Similarly, a group having 1 to 5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so on.

[0229] Moreover, the claims should not be read as limited to the provided order or to the provided elements unless specifically so stated. In addition, the use of the term "means for" in any claim is intended to invoke 35 U.S.C. ...

Claims

1. 1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: transmitting, to a base station, information indicating (1) an association between a first flow and a second flow, and (2) a maximum time difference between application data units (ADUs) of the first flow and the second flow; receiving information from the base station indicative of any of a first resource configuration, a second resource configuration, a first time threshold, and a second time threshold; receiving one or more protocol data units (PDUs) of a first ADU of the first flow and one or more PDUs of a second ADU of the second flow; transmitting the one or more PDUs of the first ADU of the first flow using the first resource configuration; transmitting at least the last PDU of the second ADU of the second flow using the second resource configuration, provided that (1) the last PDU of the second ADU of the second flow is received after the first time threshold has elapsed since receipt of the last PDU of the first ADU of the first flow, and (2) the last PDU of the second ADU of the second flow is received before the second time threshold has elapsed since receipt of the last PDU of the first ADU of the first flow.

2. The method of claim 1 , wherein the second time threshold is greater than the first time threshold.

3. The method of claim 1 or 2, wherein the first resource configuration is a first configured grant configuration and the second resource configuration is a second configured grant configuration.

4. The method according to any one of claims 1 to 3, wherein a size of a transmission occasion associated with the first resource configuration is greater than a size of a transmission occasion associated with the second resource configuration.

5. 5. The method according to claim 1, wherein the first resource configuration comprises a first plurality of transmission occasions having a first periodicity and the second resource configuration comprises a second plurality of transmission occasions having a second periodicity smaller than the first periodicity.

6. 6. The method of claim 1, wherein the transmitting the one or more PDUs of the first ADU of the first flow using the first resource configuration comprises transmitting the one or more PDUs of the first ADU of the first flow and one or more PDUs of the second ADU received before the last PDU of the second ADU using a transmission occasion according to the first resource configuration.

7. 7. The method of claim 1, wherein the transmitting of at least the last PDU of the second ADU of the second flow using the second resource configuration has a timing offset that is after the transmitting of the one or more PDUs of the first ADU of the first flow using the first resource configuration.

8. The method according to any one of claims 1 to 7, wherein the first resource configuration is associated with the first flow and / or the second flow.

9. 9. The method of claim 1, wherein any of the second resource configuration, the first time threshold, and / or the second time threshold are associated with the first flow and / or the second flow.

10. The method of any one of claims 1 to 9, wherein the ADUs of the first flow and the second flow are received from different WTRUs.

11. The method according to any one of claims 1 to 10, wherein the second ADU of the second flow corresponds to the first ADU of the first flow.

12. 12. The method of claim 1, wherein: (1) the one or more PDUs of the first ADU of the first flow include identification information, timing information, and / or sequence information associated with the first ADU; and / or (2) the one or more PDUs of the second ADU of the second flow include identification information, timing information, and / or sequence information associated with the second ADU.

13. 1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: transmitting, to a base station, information indicating (1) an association between a first flow and a second flow, and (2) a maximum time difference between application data units (ADUs) of the first flow and the second flow; receiving information from the base station indicative of any of a first resource configuration, a second resource configuration, a first time threshold, and a second time threshold; receiving one or more protocol data units (PDUs) of a first ADU of the first flow and one or more PDUs of a second ADU of the second flow; transmitting the one or more PDUs of the first ADU of the first flow using a first transmission occasion indicated by the first resource configuration; (1) transmitting at least the last PDU of the second ADU of the second flow using a second transmission occasion indicated by the first resource configuration, on condition that the last PDU of the second ADU of the second flow is received after the first time threshold and the second time threshold have elapsed since receipt of the last PDU of the first ADU of the first flow.

14. The method of claim 13 , wherein the second time threshold is greater than the first time threshold.

15. 15. The method of claim 13 or 14, wherein the first resource configuration is a first configured grant configuration and the second resource configuration is a second configured grant configuration.

16. The method according to any one of claims 13 to 15, wherein a size of a transmission occasion associated with the first resource configuration is greater than a size of a transmission occasion associated with the second resource configuration.

17. 17. The method according to claim 13, wherein the first resource configuration comprises a first plurality of transmission occasions having a first periodicity and the second resource configuration comprises a second plurality of transmission occasions having a second periodicity smaller than the first periodicity.

18. 18. The method of claim 13, wherein transmitting the one or more PDUs of the first ADU of the first flow using the first transmission occasion of the first resource configuration comprises transmitting at least one other PDU of the second ADU of the second flow, which is received before the last PDU of the second ADU, using the first transmission occasion of the first resource configuration.

19. The method according to any one of claims 13 to 18, wherein the first resource configuration is associated with the first flow and / or the second flow.

20. The method of any one of claims 13 to 19, wherein either the first time threshold and / or the second time threshold is associated with the first flow and / or the second flow.

21. The method of any one of claims 13 to 20, wherein the ADUs of the first flow and the second flow are received from another WTRU.

22. The method according to any one of claims 13 to 21, wherein the second ADU of the second flow corresponds to the first ADU of the first flow.

23. 23. The method of claim 13, wherein: (1) the one or more PDUs of the first ADU of the first flow include identification information, timing information, and / or sequence information associated with the first ADU; and / or (2) the one or more PDUs of the second ADU of the second flow include identification information, timing information, and / or sequence information associated with the second ADU.

24. 1. A wireless transmit / receive unit (WTRU), comprising: a processor and a transceiver, the processor and the transceiver comprising: transmitting, to a base station, information indicating (1) an association between a first flow and a second flow, and (2) a maximum time difference between application data units (ADUs) of the first flow and the second flow; receiving information from the base station indicative of any of a first resource configuration, a second resource configuration, a first time threshold, and a second time threshold; receiving one or more protocol data units (PDUs) of a first ADU of the first flow and one or more PDUs of a second ADU of the second flow; Transmitting the one or more PDUs of the first ADU of the first flow using the first resource configuration; a WTRU configured to transmit at least the last PDU of the second ADU of the second flow using the second resource configuration, on the condition that (1) the first time threshold has elapsed since receipt of the last PDU of the first ADU of the first flow, and (2) the last PDU of the second ADU of the second flow is received before the second time threshold has elapsed since receipt of the last PDU of the first ADU of the first flow.

25. The WTRU of claim 24, wherein the second time threshold is greater than the first time threshold.

26. The WTRU of claim 24 or 25, wherein the first resource configuration is a first configured grant configuration and the second resource configuration is a second configured grant configuration.

27. The WTRU of any one of claims 24 to 26, wherein a size of a transmission occasion associated with the first resource configuration is greater than a size of a transmission occasion associated with the second resource configuration.

28. 28. The WTRU of claim 24, wherein the first resource configuration includes a first plurality of transmission occasions having a first periodicity, and the second resource configuration includes a second plurality of transmission occasions having a second periodicity that is smaller than the first periodicity.

29. The WTRU of any one of claims 24 to 28, wherein the processor and the transceiver are configured to transmit the one or more PDUs of the first ADU of the first flow using the first resource configuration, which includes transmitting the one or more PDUs of the first ADU of the first flow and one or more PDUs of the second ADU received before the last PDU of the second ADU using a transmission occasion according to the first resource configuration.

30. The WTRU of any one of claims 24 to 29, wherein the processor and the transceiver are configured to transmit at least the last PDU of the second ADU of the second flow using the second resource configuration and a timing offset that is after transmitting the one or more PDUs of the first ADU of the first flow using the first resource configuration.

31. The WTRU of any one of claims 24 to 30, wherein the first resource configuration is associated with the first flow and / or the second flow.

32. The WTRU of any one of claims 24 to 31, wherein the second resource configuration, the first time threshold, and / or the second time threshold are associated with the first flow and / or the second flow.

33. The WTRU of any one of claims 24 to 32, wherein the ADUs of the first flow and the second flow are received from another WTRU.

34. The WTRU of any one of claims 24 to 33, wherein the second ADU of the second flow corresponds to the first ADU of the first flow.

35. The WTRU of any one of claims 24 to 34, wherein: (1) the one or more PDUs of the first ADU of the first flow include identification information, timing information, and / or sequence information associated with the first ADU; and / or (2) the one or more PDUs of the second ADU of the second flow include identification information, timing information, and / or sequence information associated with the second ADU.

36. 1. A wireless transmit / receive unit (WTRU), comprising: a processor and a transceiver, the processor and the transceiver comprising: transmitting, to a base station, information indicating (1) an association between a first flow and a second flow, and (2) a maximum time difference between application data units (ADUs) of the first flow and the second flow; receiving information from the base station indicative of any of a first resource configuration, a second resource configuration, a first time threshold, and a second time threshold; receiving one or more protocol data units (PDUs) of a first ADU of the first flow and one or more PDUs of a second ADU of the second flow; Transmitting the one or more PDUs of the first ADU of the first flow using a first transmission occasion indicated by the first resource configuration; (1) A WTRU configured to transmit at least the last PDU of the second ADU of the second flow using a second transmission occasion indicated by the first resource configuration, provided that the last PDU of the second ADU of the second flow is received after the first time threshold and the second time threshold have elapsed since receipt of the last PDU of the first ADU of the first flow.

37. The WTRU of claim 36, wherein the second time threshold is greater than the first time threshold.

38. 38. The WTRU of claim 36 or 37, wherein the first resource configuration is a first configured grant configuration and the second resource configuration is a second configured grant configuration.

39. The WTRU of any one of claims 36 to 38, wherein a size of a transmission occasion associated with the first resource configuration is greater than a size of a transmission occasion associated with the second resource configuration.

40. 40. The WTRU of claim 36, wherein the first resource configuration includes a first plurality of transmission occasions having a first periodicity, and the second resource configuration includes a second plurality of transmission occasions having a second periodicity that is smaller than the first periodicity.

41. The WTRU of any one of claims 36 to 40, wherein the processor and the transceiver are configured to transmit the one or more PDUs of the first ADU of the first flow using the first transmission occasion of the first resource configuration, which includes transmitting at least one other PDU of the second ADU of the second flow that is received before the last PDU of the second ADU using the first transmission occasion of the first resource configuration.

42. The WTRU of any one of claims 36 to 41, wherein the first resource configuration is associated with the first flow and / or the second flow.

43. The WTRU of any one of claims 36 to 42, wherein either the first time threshold and / or the second time threshold are associated with the first flow and / or the second flow.

44. The WTRU of any one of claims 36 to 43, wherein the ADUs of the first flow and the second flow are received from another WTRU.

45. The WTRU of any one of claims 36 to 44, wherein the second ADU of the second flow corresponds to the first ADU of the first flow.

46. The WTRU of any one of claims 36 to 45, wherein: (1) the one or more PDUs of the first ADU of the first flow include identification information, timing information, and / or sequence information associated with the first ADU; and / or (2) the one or more PDUs of the second ADU of the second flow include identification information, timing information, and / or sequence information associated with the second ADU.