Method, architecture, apparatus and system for multi-stream synchronization

Abstract

A wireless transmit / receive unit (WTRU) and a method implemented thereby are provided. The method includes receiving configuration information associated with uplink (UL) traffic, the configuration information including information indicating a flow set and a timer amount; determining, for each stream in the set of streams, information comprising a time of arrival and associated characteristics of one or more sets of protocol data units (PDUs) associated with the respective stream; and transmitting assistance information to the network entity based on a timer associated with an amount of timer that is no longer running for at least one stream of the set of streams, the assistance information includes UL traffic information of the at least one flow indicating identifiers of the one or more PDU sets, the determined time of arrival, and associated characteristics of the one or more PDU sets.

Description

[0001] This application is a divisional application of the invention patent application with the application date of November 1, 2022, application number 202280080241.4, and invention name "Methods, architectures, devices and systems for multi-stream synchronization".

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of (i) U.S. Provisional Patent Application No. 63 / 275,133, filed on November 3, 2021, and (ii) U.S. Provisional Patent Application No. 63 / 335,285, filed on April 27, 2022; each of these applications is incorporated herein by reference. Background Art

[0004] The present disclosure relates generally to the fields of communications, software, and coding, including, for example, to methods, architectures, devices, and systems for ensuring synchronization of multiple data streams, such as multiple data streams associated with extended reality (XR) communications. Summary of the invention

[0005] In certain representative embodiments, a wireless transmit / receive unit (WTRU) may determine a resource (e.g., forwarding) configuration to be used when transmitting and / or receiving multiple streams (e.g., in an uplink and / or downlink) to synchronize the transmissions. For example, the multiple streams may be synchronized such that a delay between a (e.g., most recent) protocol data unit (PDU) in a first stream and a (e.g., most recent) PDU in a second stream is less than or equal to a different expected time of arrival (ETA) threshold, such as an inter-stream packet delay budget (PDB). For example, the PDUs in the first stream and the second stream may be received from any of an application and / or service (e.g., which generates information in a payload of the PDU) executed by the WTRU, another WTRU, a base station, and / or a network entity.

[0006] According to one embodiment of the present disclosure, a method implemented by a wireless transmit / receive unit (WTRU) is provided, the method comprising: receiving configuration information associated with an uplink (UL) service, the configuration information comprising information indicating a flow set and a timer amount; determining, for each flow in the flow set, information including an arrival time and associated characteristics of one or more protocol data unit (PDU) sets associated with the corresponding flow; and transmitting auxiliary information to a network entity based on a timer associated with a timer amount that is no longer running for at least one flow in the flow set, wherein the auxiliary information comprises UL service information of the at least one flow indicating an identifier of the one or more PDU sets, the determined arrival time, and associated characteristics of the one or more PDU sets.

[0007] According to another embodiment of the present disclosure, a wireless transmit / receive unit (WTRU) is provided, comprising: a processor, a memory, and a transceiver, configured to: receive configuration information associated with an uplink (UL) service, the configuration information comprising information indicating a flow set and a timer amount; determine, for each flow in the flow set, information including an arrival time and associated characteristics of one or more protocol data unit (PDU) sets associated with the corresponding flow; and transmit auxiliary information to a network entity based on a timer associated with a timer amount that is no longer running for at least one flow in the flow set, wherein the auxiliary information comprises UL service information of the at least one flow indicating an identifier of the one or more PDU sets, the determined arrival time, and the associated characteristics of the one or more PDU sets. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A more detailed understanding can be obtained from the following detailed description, which is given by way of example in conjunction with its accompanying drawings. As with the detailed description, the figures in such drawings are examples. Therefore, the drawings (figures) and specific embodiments should not be considered limiting, and other equally effective examples are possible and contemplated. In addition, like reference numerals ("ref.") in the figures indicate similar elements, and wherein:

[0009] Figure 1A is a system diagram illustrating an exemplary communication system;

[0010] Figure 1B It shows that Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within the communication system shown;

[0011] Figure 1C It shows that Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used within the illustrated communication system;

[0012] Figure 1D It shows that Figure 1A A system diagram of an additional exemplary RAN and an additional exemplary CN used within the illustrated communication system;

[0013] Figure 2 is a system diagram illustrating an example of multi-stream synchronization that may be used within the communication system described herein;

[0014] Figure 3 is a system diagram illustrating another example of multi-stream synchronization that may be used within the communication system described herein;

[0015] Figure 4 is a system diagram illustrating another example of multi-stream synchronization that may be used within the communication system described herein;

[0016] Figure 5 is a process diagram illustrating an example process for synchronizing multiple streams;

[0017] Figure 6 is a process diagram illustrating another example process for synchronizing multiple streams;

[0018] Figure 7 is a process diagram illustrating an example process for synchronizing multiple streams;

[0019] Figure 8 is a process diagram illustrating another example process for synchronizing multiple streams;

[0020] Fig. 9 is a process diagram illustrating an example for sending multiple streams using priority levels;

[0021] Fig.10 is a process diagram illustrating an example for receiving multiple streams using priority levels;

[0022] Fig.11 is a process diagram illustrating an example process for adjusting resource configuration information to synchronize multiple streams;

[0023] Fig.12 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams;

[0024] Fig.13 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams;

[0025] Fig.14 is a process diagram illustrating an example process for adjusting resource configuration information to synchronize multiple streams;

[0026] Fig.15 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams;

[0027] Fig.16 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams;

[0028] Fig.17 is a process diagram illustrating an example process for maintaining joint quality of service (QoS) for multiple flows;

[0029] Fig.18 is a process diagram illustrating another example process for maintaining joint quality of service (QoS) for multiple flows;

[0030] Fig.19is a process diagram illustrating another example process for synchronizing multiple streams;

[0031] Fig. 20 is a process diagram illustrating another example for sending multiple streams using priority levels;

[0032] Fig.21 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams; and

[0033] Fig. 22 is a process diagram illustrating an example process for maintaining joint quality of service (QoS) for multiple flows. DETAILED DESCRIPTION

[0034] In the following detailed description, many specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it should be understood that such embodiments and examples can be practiced without some or all of the specific details set forth herein. In other cases, well-known methods, procedures, components and circuits are not described in detail to avoid blurring the following description. In addition, the embodiments and examples not specifically described herein can be practiced in place of the embodiments and other examples explicitly, implicitly and / or inherently described, disclosed or otherwise provided (collectively referred to as "provided") herein, or practiced in combination with these embodiments and examples. Although various embodiments are described and / or claimed herein, wherein devices, systems, equipment, etc. and / or any of their elements perform operations, processes, algorithms, functions, etc. and / or any part thereof, it should be understood that any embodiments described herein and / or protected by the claims assume that any device, system, equipment, etc. and / or any of its elements are configured to perform any operations, processes, algorithms, functions, etc. and / or any part thereof.

[0035] Example Communication System

[0036] The methods, devices, and systems provided herein are well suited for communications involving both wired and wireless networks. Figures 1A to 1D An overview of various types of wireless devices and infrastructure is provided, wherein various elements of the network can utilize the methods, apparatuses, and systems provided herein, perform the methods, apparatuses, and systems provided herein, be arranged according to the methods, apparatuses, and systems provided herein, and / or be adapted and / or configured for the methods, apparatuses, and systems provided herein.

[0037] Figure 1A1 is a system diagram illustrating an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication 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 multi-carrier (FBMC), etc.

[0038] like Figure 1A As shown, the communication 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, but it should 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 send and / or receive wireless signals and may include (or may be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0039] 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 that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to, for example, facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the network 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node B (NB), an evolved Node B (eNB), a Home Node B (HNB), a Home evolved Node B (HeNB), a gNode B (gNB), a NR Node B (NR NB), a site controller, an access point (AP), a wireless router, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0040] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSC), radio network controllers (RNC), relay nodes, etc. Base station 114a and / or base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies (which may be referred to as cells (not shown)). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. A cell may also be divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Therefore, in an embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, 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 send and / or receive signals in a desired spatial direction.

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

[0042] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication 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).

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

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

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

[0046] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Enhanced Data Rates for Evolution (EDGE), GSM EDGE (GERAN), etc.

[0047] Figure 1A The base station 114b in 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 local area such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In an 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 any of a microcell, a picocell, or a femtocell. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0048] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as 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 described in detail in the text and video above, the CN 106 / 115 may be configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs any of GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.

[0049] The CN 106 / 115 may also act 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 that provides 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), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless 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 RAN 104 / 114 or a different RAT.

[0050] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0051] Figure 1B is a system diagram illustrating an exemplary WTRU 102. Figure 1B As shown, 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 appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0052] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors 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 decoding, data processing, power control, input / output processing, and / or any other functions that enable 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 Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together, for example, in an electronic package or chip.

[0053] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from a base station via an air interface 116. For example, in an embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In an embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, an IR, UV, or visible light signal. In an embodiment, the send / receive element 122 may be configured to send and / or receive both an RF signal and an optical signal. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.

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

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

[0056] The processor 118 of the WTRU 102 may be coupled to 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) and may receive user input data therefrom. 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 a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

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

[0058] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information 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 received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0059] The processor 118 may also be coupled to other components / peripherals 138, which may include one or more software modules / units and / or hardware modules / units that provide additional features, functionality, and / or wired or wireless connectivity. For example, the components / 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, module, FM radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. Components / peripherals 138 may include one or more sensors, which may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0060] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via signal processing performed by hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

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

[0062] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-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 evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

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

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

[0065] The MME 162 may be connected to each of the evolved Node-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, 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.

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

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

[0068] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication 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.

[0069] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

[0070] In a representative embodiment, the other network 112 may be a WLAN.

[0071] 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 an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and going to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and going to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Direct link establishment (DLS) may be used to transmit point-to-point traffic between the source STA and the destination STA (e.g., directly between them). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

[0072] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / 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.

[0073] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0074] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operations for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC) layer, entity, etc.

[0075] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz 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 certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0076] WLAN systems that can support multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah include channels that can be designated as primary channels. 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 a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only 1MHz operating mode) is sending to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.

[0077] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

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

[0079] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers to communicate 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 send signals to and / or receive signals from the WTRUs 102a, 102b, 102c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

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

[0081] 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 while also not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use 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 an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate or be connected with the gNB 180a, 180b, 180c while also communicating or being connected with another RAN, such as the eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle 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-B 160a, 160b, 160c may serve as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0082] 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 UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0083] Figure 1DThe illustrated CN 115 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 depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0084] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c, for example, based on the type of services used by the WTRU 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.

[0085] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure the traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating 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.

[0086] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the 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 UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0087] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to 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 via the UPFs 184a, 184b via the N3 interfaces to the UPFs 184a, 184b and the N6 interfaces between the UPFs 184a, 184b and the DNs 185a, 185b.

[0088] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to any of the following may be performed by one or more simulation elements / devices (not shown): WTRU102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182b, UPF 184a-184b, SMF 183a-183b, DN 185a-185b and / or any other element / device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

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

[0090] The one or more simulation devices may perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. The one or more simulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) may be used by the simulation device to send and / or receive data.

[0091] The following abbreviations may be used herein:

[0092] 6DOF 6 Degrees of Freedom

[0093] ACK

[0094] ADU Application Data Unit

[0095] AR Augmented Reality

[0096] BWP Bandwidth Part

[0097] CSI Channel State Information

[0098] CG Cloud Gaming

[0099] DL Downlink

[0100] DMRS Dedicated Demodulation Reference Signal

[0101] FDD Frequency Division Duplex

[0102] FoV

[0103] gNB NR Node B

[0104] fps frames per second

[0105] HARQ Hybrid Automatic Repeat Request

[0106] iBLER initial block error rate

[0107] LCH Logical Channel

[0108] MCS modulation and coding scheme

[0109] MTP Movement to Photons

[0110] NACK Negative Acknowledgement

[0111] PDCCH Physical Downlink Control Channel

[0112] PDB Packet Delay Budget

[0113] PDU Packet Data Unit

[0114] PER Packet Error Rate

[0115] PSG Power Saving Gain

[0116] PSR Grouping Power

[0117] PUCCH Physical Uplink Control Channel

[0118] PUSCH Physical Uplink Shared Channel

[0119] PDSCH Physical Downlink Shared Channel

[0120] RTT Round Trip Time

[0121] SR Scheduling Request

[0122] STD Standard Deviation

[0123] TDD Time Division Duplex

[0124] UE User Equipment

[0125] UL Uplink

[0126] VR Virtual Reality

[0127] XR

[0129] In certain representative embodiments, a WTRU may determine a resource (e.g., forwarding) configuration to be used when transmitting and / or receiving multiple streams (e.g., in uplink and / or downlink) to synchronize the transmissions. For example, the multiple streams may be synchronized such that a delay between a (e.g., most recent) PDU in a first stream and a (e.g., most recent) PDU in a second stream is less than or equal to a different expected time of arrival (ETA) threshold (e.g., inter-stream PDB). For example, the PDUs in the first stream and the second stream may be received from any of an application and / or service (e.g., which generates information in a payload of a PDU) executed by the WTRU, another WTRU, a base station, and / or a network entity.

[0130] For example, the WTRU may be configured to perform any of the following:

[0131] ● receiving information (e.g., configuration information) from a base station (e.g., a gNB) indicating a primary ETA threshold and a secondary ETA threshold (e.g., a time instance and / or a duration) and one or more forwarding configurations associated with different priorities (at least one default forwarding configuration (e.g., a logical channel (LCH)) per flow for forwarding PDUs having a default priority value in each flow);

[0132] • receiving a PDU associated with a first flow (eg, “flow 1”) and / or transmitting the PDU using a default forwarding configuration associated with the first flow;

[0133] • determining a time of arrival (ToA) of PDUs associated with a second flow (e.g., “flow 2”), such as by using (e.g., starting) a timer and / or based on a time instance when the PDUs in the first flow were received;

[0134] If a PDU in the second stream is received before the primary ETA threshold (e.g., has passed)

[0135] (e.g., at a certain time instance), then

[0136] o transmitting the PDU in the second flow using a default forwarding configuration associated with the second flow;

[0137] If a PDU in the second flow is received (eg, at some time instance) after the primary ETA threshold and before (eg, has passed) the secondary ETA threshold, then

[0138] o determining a (e.g., new) priority for the PDUs in the second flow, wherein the new priority is higher than the default priority,

[0139] o transmitting the PDU in the second flow using an appropriate (e.g., determined) forwarding configuration that matches the determined new priority;

[0140] If a PDU in the second stream is received after the secondary ETA threshold (e.g., has passed)

[0141] (e.g., at a certain time instance), then

[0142] o transmitting a status indication indicating late PDU reception to a base station (e.g., a gNB) (e.g., information indicating a priority of the late PDU and / or a time when the late PDU was received),

[0143] o transmitting the PDU using a best effort or available forwarding configuration, such as after receiving an indication from a base station to transmit a PDU with a best effort configuration;

[0144] o Discard (e.g., discard) the PDU, such as after receiving an instruction to discard (e.g., any) late PDU

[0145] transmitting one or more PDUs in any of the first flow and / or the second flow (e.g., multiple flows) using one or more suitable (e.g., determined) forwarding configurations to meet a QoS requirement (e.g., a joint QoS requirement based on an association between the first flow and the second flow),

[0146] ● transmitting information indicating one or more (e.g., determined) forwarding configurations to satisfy (e.g., ensure) the first flow and / or the second flow (e.g., multiple flows) such as within RTT requirements

[0147] in synchronization.

[0148] In certain representative embodiments, the WTRU may determine a forwarding configuration to use when sending data in multiple flows (e.g., in an uplink) to synchronize the transmissions. For example, the multiple flows may be synchronized 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 flow and the second flow may be received from any of an application and / or service (e.g., which generates information in a payload of a PDU) executed by the WTRU, another WTRU, a base station, and / or a network entity.

[0149] For example, the WTRU may be configured to perform any of the following:

[0150] Receive information (e.g., configuration information) from a base station (e.g., a gNB) indicating a first ETA threshold, a second ETA threshold, and a third ETA threshold (e.g., a time instance and / or a duration) and one or more forwarding configurations associated with different priorities (at least one default forwarding configuration (e.g., LCH) per flow for forwarding packets with different priorities in each flow);

[0151] PDU with default priority value);

[0152] ● receiving one or more PDUs of the ADU in the first stream and / or using the ADU associated with the first stream

[0153] to transmit a PDU (e.g., of an ADU) using a default forwarding configuration;

[0154] • Determine the second based on the time instance when the first PDU of the ADU in the first stream is received

[0155] The time of arrival (ToA) of one or more PDUs in the flow;

[0156] o Determine the ToA by starting a first timer, a second timer, and a third timer associated with the first ETA threshold, the second ETA threshold, and the third ETA threshold

[0157] If the WTRU receives the (e.g., last and / or latest) PDU of the ADU in the first stream and / or one or more PDUs of the ADU in the second stream before the first ETA threshold (e.g., has passed), then

[0158] o transmitting the PDUs of the ADU in the first flow and transmitting the PDUs 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);

[0159] If (e.g., some or any) PDUs of the ADU in the first stream and / or (e.g., some or any) PDUs of the ADU in the second stream are received after a first ETA threshold (e.g., has passed) and / or before a second ETA threshold (e.g., has passed), then:

[0160] o determining a (eg, new) priority for the (eg, late) PDUs of the ADU in the first flow (eg, the new priority may be higher than a default priority);

[0161] o transmitting the PDUs of the ADU in the first flow using a relevant (e.g., appropriate) forwarding configuration (e.g., matching the determined new priority);

[0162] o transmitting the PDUs of the ADU in the second flow using a default forwarding configuration associated with the second flow;

[0163] o If the forwarding configuration is not available for transmitting the PDUs of the ADU in the first flow, transmitting a status indication and / or a request indication to a base station (e.g., a gNB), and / or

[0164] ■ transmitting the PDUs of the ADU in the first flow using a best effort or available forwarding configuration, such as based on an indication received from the gNB (e.g., transmitting PDUs with a best effort configuration);

[0165] If (e.g., some or any) PDUs of the ADU in the second flow are received after the second ETA threshold (e.g., has passed) and / or before the third ETA threshold (e.g., has passed), then:

[0166] o determining a (eg, new) priority for the (eg, late) PDUs of the ADU in the second flow (eg, the new priority may be higher than the default priority);

[0167] o transmitting the PDUs of the ADU in the second flow using the relevant forwarding configuration (e.g. matching the determined new priority);

[0168] o If the relevant (e.g., suitable) forwarding configuration is not available for transmitting the PDU of the ADU in the second flow, transmitting a status indication and / or a request indication to the base station (e.g., gNB), and / or

[0169] ■ transmitting the PDUs of the ADU in the second flow using a best effort forwarding configuration (e.g., based on an indication received from the base station);

[0170] If (e.g. some or any) PDUs of the ADU in the second flow are received after a third ETA threshold (e.g. has passed), then:

[0171] o Transmitting a status indication and / or a request indication on a late PDU to a base station (e.g., gNB);

[0172] o transmit the PDUs of the ADU in the second flow using a best effort forwarding configuration and / or discard the PDUs (e.g., based on an indication received from the base station);

[0173] ● using one or more appropriate (e.g., determined) forwarding configurations to transmit one or more PDUs in any of the first flow, the second flow, and / or the third flow (e.g., multiple flows) to meet QoS requirements (e.g., a joint QoS requirement based on an association between the first flow, the second flow, and / or the third flow); and / or

[0174] ● transmitting information indicating one or more (eg, determined) forwarding configurations to satisfy (eg, ensure) the first flow, the second flow, and / or the third flow (eg, within RTT requirements)

[0175] multiple streams).

[0176] Overview

[0177] The term "extended reality" (XR) can 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 inserted between them. For example, virtual reality (VR) may refer to a rendered version of a delivered visual and / or audio scene. When an observer or user moves within the limits defined by the application, the rendering may be designed to (e.g., as naturally as possible) mimic the visual (e.g., stereoscopic 3D) and / or audio sensory stimulation of the real world to them. For example, augmented reality (AR) may refer to providing users with additional information and / or artificially generated objects and / or content superimposed on their current environment. Mixed reality (MR) may refer to an advanced form of AR, in which some virtual elements are inserted into a physical scene, (e.g., intended to) provide the illusion that these elements are part of the real scene. As used herein, the term "XR" may include any real and / or virtual combined environment, as well as human-computer interactions generated by computer technology and wearable devices.

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

[0179] XR devices may (e.g., typically) be associated with the ability to provide various degrees of spatial tracking. XR devices may be equipped with various sensors to enable spatial tracking, such as monocular, stereo and / or 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 motion along the X-axis, Y-axis, and Z-axis) or 6DoF (e.g., rotational motion and / or translational motion along the X-axis, Y-axis, and Z-axis). For example, spatial tracking may result in experiencing some form of interaction with virtual content. A user may perform actions in and / or interact with components within an extended reality. For example, actions and / or interactions may involve movement, gestures, eye tracking, etc. Spatial tracking may be an important feature of an immersive XR experience. For example, some form of head and / or motion tracking may ensure that the visual and / or audio components of the simulation from the user's perspective are updated to be consistent with the user's movement. Inaccurate and / or delayed spatial tracking may cause the user to feel uncomfortable and / or motion sickness.

[0180] As described herein, a WTRU (e.g., user equipment) may correspond to any XR device and / or node, which may have a variety of form factors. A WTRU (e.g., XR WTRU) may include, but is 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, wearable devices, etc. In addition to the above, several different types of XR devices may be envisioned based on XR device functionality, such as displays, cameras, sensors, sensor processing, wireless connectivity, XR / media processing, power supply, etc. provided by one or more devices, wearable devices, actuators, controllers, and / or accessories. One or more devices and / or nodes (e.g., WTRUs) may be grouped into collaborative XR groups for supporting XR applications and / or services.

[0181] Business models for XR applications and use cases

[0182] In certain representative embodiments, services and / or traffic flows for (eg, different) XR applications and / or use cases are identified (eg, described) in 3GPP TR 26.928.

[0183] Virtual Reality 1 (VR1)

[0184] For example, VR1 applications (e.g., streaming of immersive 6DoF) can be modeled using service flows suitable for viewport-dependent streaming architecture. Similar to adaptive streaming (e.g., Dynamic Adaptive Streaming over HTTP (DASH)), viewport-dependent streaming can allow the quality of media and / or video to be dynamically updated based on the available bit rate in the network and / or wireless interface. According to the service and / or business flow, the tracking and / or posture information (e.g., small packet size <100B) of the viewport of the XR device is periodically transmitted to the XR server in the UL at a relatively low data rate (e.g., 0.5Mbps to 2Mbps, 60Hz to 500Hz). In response, the XR server may transmit in the DL at a relatively high data rate (e.g., 6MBps to 18MBps for 4k omnidirectional and / or FoV regional streaming) and may adaptively transmit (e.g., H.264 / 265 video) viewport-optimized media quasi-periodically (e.g., 40 / 60 / 120fps) and then render the media in the XR device display.

[0185] For example, the service characteristics of VR1 can be described as:

[0186] UL services: posture and / or viewport information (e.g. including information about 6DoF)

[0187] o Small packet size (e.g., relatively constant size <100B), low data rate (e.g., 0.5Mbps to 2Mbps), and / or a single stream,

[0188] o Periodicity: (e.g., a periodicity range of 60 Hz to 500 Hz); and / or

[0189] DL services: (1) Media and / or video containing viewport-optimized scenes (e.g., higher quality)

[0190] and / or (2) for non-viewport scenes media and / or video (e.g., lower quality)

[0191] o Large packet size (e.g., variable size with Gaussian distribution or fixed size of 1500B), high data rate (e.g., 6Mbps to 18Mbps), E2E latency (e.g., 50ms), multiple streams (e.g., video streams with different bit rates, 3D media, metadata),

[0192] o Quasi-periodicity (eg, periodicity as a function of a frame rate such as 40 / 60 / 120 fps).

[0193] Virtual Reality 2 (VR2)

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

[0195] For example, the service characteristics of VR2 can be described as:

[0196] UL: pose and / or viewport information

[0197] o Small packet size (e.g., constant size < 100B), low data rate (e.g., 0.5Mbps to 2Mbps), single stream,

[0198] o Periodicity (e.g., a periodicity range of 60 Hz to 500 Hz); and / or

[0199] ●DL: 3D scene in frame buffer

[0200] o Large packet size (e.g., Gaussian distribution and / or up to 1500B, or unlimited), high data rate (e.g., 30Mbps to 45Mbps), latency (e.g., approximately 30ms and / or up to 50ms RTT), multiple streams (3D video and / or media, metadata),

[0201] o Quasi-periodicity (eg, periodicity as a function of a frame rate such as 60 / 90 fps).

[0202] Augmented Reality 1 (AR1)

[0203] For example, an AR1 application (e.g., real-time communication with a store clerk) can be characterized using a service flow suitable for a distributed computing architecture. Depending on the service and / or business flow, the XR device can transmit posture information (e.g., 0.5Mbps to 2Mbps, 60Hz to 500Hz) and / or video (e.g., 10Mbps, 10Hz frame update rate) to the XR server in the UL. The XR server can use the received information 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). Compressed media and metadata (e.g., characterized by a Pareto distribution) can be delivered in the DL at a high data rate (e.g., 30Mbps to 45Mbps, 40 / 60 / 120fps) (e.g., quasi-periodically). The XR device can then locally generate the scene, such as by overlaying a 3D object on a 2D video and rendering the AR scene in the device display.

[0204] For example, the service characteristics of AR1 are as follows:

[0205] UL: posture information and / or 2D video stream information

[0206] ○ Attitude: small packet size, low data rate (e.g., 0.5Mbps to 2Mbps), periodic (e.g., 60Hz to 500Hz),

[0207] o Video: large packet size, higher data rate (e.g., 10 Mbps), periodicity (e.g., 10 Hz update periodicity), multi-stream video; and / or

[0208] DL: 2D and / or 3D pre-rendered media and XR metadata

[0209] o Large packet sizes (e.g., Pareto distribution), high data rates (e.g., 30 Mbps to 45 Mbps), multiple streams (2D and / or 3D media and / or metadata),

[0210] o Quasi-periodicity (eg, periodicity as a function of frame rate of 60 / 90 fps).

[0211] Augmented Reality 2 (AR2)

[0212] For example, AR2 applications (e.g., XR conferencing, AR avatar calls) may use services and / or business flows applicable to the XR conversation architecture, such as where two or more XR clients and / or devices may perform peer-to-peer communication with intermediate media processing in the network. AR2 applications may support different types of media, such as based on user representation types, including any of 2D+ / RGBD (e.g., 2.7Mbps), 3D mesh (e.g., 30Mbps), 3D video point cloud coding (VPCC), and / or geometry-based point cloud compression (GPCC) (e.g., 5Mbps to 50Mbps). In an example XR business flow, the XR client in the device initiates a call setup process, and the session control function may trigger network-based media processing based on the call setup process. The SMF may forward the call setup to the second XR client and / or device, followed by real-time media processing and streaming to both clients with low latency (e.g., E2E <100ms). During an XR call, 2D and / or 3D media and possibly user pose information may be sent quasi-periodically in the UL and DL between XR clients and / or devices.

[0213] For example, the service characteristics of AR2 can be described as follows:

[0214] UL: 2D and / or 3D media, gestures and / or video of the user

[0215] o Large packet sizes and / or data rates (e.g., 2.7 Mbps to 50 Mbps), PDB

[0216] (e.g., <150ms), multiple streams (2D and / or 3D media),

[0217] ○ Quasi-periodic (e.g., 60 Hz to 500 Hz); and / or

[0218] DL: 2D and / or 3D media, gestures and / or video of the user

[0219] o Large packet size (e.g., truncated Gaussian distribution) and / or data rate (e.g., 2.7Mbps to 50Mbps), E2E PDB (e.g., <100ms), multiple streams (2D and / or 3D media),

[0220] ○ Quasi-periodic (e.g., 60 Hz to 500 Hz).

[0221] XR Conference

[0222] For example, an XR conference application may provide an immersive conference experience between geographically remote users, such as by representing the user in a 3D volume representation (e.g., a point cloud and / or a mesh). One or more cameras (e.g., with depth perception capabilities) may be placed at the location of each user to allow interaction (e.g., viewing, hearing, rotating, zooming in, resizing, etc.) with each other's full 3D volume representation on their respective headsets and / or glasses. The XR conference application may support simultaneous UL and DL media services. The media service may include any of audio, video, and / or 3D objects. Media formats that may be applied to capture users in a 3D volume format include any of 2D+ / RGBD (e.g., >2.7Mbps for 1 camera, >5.4Mbps for 2 cameras), 3D Mesh (e.g., about 30Mbps), 3DVPCC, and / or GPCC (e.g., 5Mbps to 50Mbps). The media processor may be centrally located (e.g., in a core network) or distributed (e.g., in an edge network). The service and / or traffic flow between XR clients and / or users via the in-network media processors can be expected to be similar to the AR2 and XR session use cases. Joining an XR conference session may result in a download spike at the beginning to download the virtual environment and associated media objects within the XR application. Throughout the rest of the session, the data rate may vary depending on the number of users, the upload format of the users, and / or the refresh rate of the virtual 2D and / or 3D objects and / or environment.

[0223] For example, the service characteristics of an XR conference can be described as follows:

[0224] UL: 2D and / or 3D media, gestures, and / or real-time video of the user

[0225] o Large packet size and / or data rate (e.g., 2.7Mbps vs. 50Mbps), multiple streams

[0226] (2D and / or 3D media),

[0227] ○ Quasi-periodic (e.g., 60 Hz to 500 Hz),

[0228] ○ Low encoder PER (e.g., <10 -3 ); and / or

[0229] DL: 2D and / or 3D media, gestures and / or live video of the user, 2D and / or 3D objects and / or environment (possibly from third parties)

[0230] o Large packet size and / or data rate (e.g., 2.7 Mbps to 50 Mbps), E2EPDB (e.g., <100 ms), multiple streams (2D and / or 3D media),

[0231] ○ Quasi-periodic (e.g., 60 Hz to 500 Hz),

[0232] ○ Low encoder PER (e.g., <10 -3 ).

[0233] Cloud Gaming (CG)

[0234] For example, CG applications (e.g., 5G online games) may rely primarily on an adaptive streaming architecture, in which rendered video and / or media in the network is streamed to a thin client in a device (e.g., a smartphone, tablet). In a typical service and / or business flow of CG, the XR device may (e.g., periodically) transmit posture information (e.g., 100 to 250B) related to the viewport in the UL (e.g., 0.1Mbps to 1Mbps, 60Hz to 500Hz) to the XR server. 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 the DL (e.g., 30Mbps to 45Mbps, 30 / 50 / 60 / 90 / 120fps, PER: 10 -3 ). The received video and / or media can then be rendered in the XR device after decoding and processing. The RTT latency for supporting certain high-end CG applications (e.g., Class D for photo-realistic or natural video games) can be determined by the round-trip interaction delay (e.g., 50ms). For other CG applications (e.g., Class A, Class B, and / or Class C), the UL PDB can be 10ms and the DL streaming PDB can range from 50ms to 200ms.

[0235] For example, the service characteristics of CG can be described as follows:

[0236] UL: pose and / or viewport information

[0237] ○ Small packet size (e.g., 100 to 250B), low data rate (e.g., 0.1Mbps to 1Mbps), PDB: 10ms, single stream,

[0238] o Periodicity (e.g., a periodicity range of 60 Hz to 500 Hz); and / or

[0239] DL: 2D and / or 3D media and / or video of the user

[0240] o Large packet size (e.g., up to 1500), high data rate (e.g., 30Mbps to 45Mbps), PDB: 20ms, multiple streams (2D and / or 3D media, video)

[0241] o Quasi-periodicity (e.g., periodicity as a function of frame rate 30 / 50 / 60 / 90 / 120fps),

[0242] ○PER: 10e-3.

[0243] An XR application may be associated with (e.g., generate and / or receive) multiple data streams for each application and / or service, which may be independently sent over the Uu interface. The multiple data streams may originate from different devices associated with the WTRU (e.g., HMD, smartphone, haptic glove). For example, one possible use case is a shared XR experience where users equipped with multiple XR devices may interact with each other while being physically located at different locations (e.g., two people shaking hands at different locations).

[0244] 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 to (e.g., attempt to) ensure that the QoS requirements of each flow are met independently. Similarly, traffic prioritization at a scheduler in the network may also be performed independently for each QoS flow. The WTRU may also support other additional applications that may have higher priority values ​​relative to the flows associated with the XR applications supported by the WTRU.

[0245] In addition to the RAN QoS (e.g., PER and / or latency) that each data flow may need to meet (e.g., independently), coordination between data flows may also 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 result in poor QoE and / or may cause acute discomfort or illness (e.g., vomiting, disorientation) to the user.

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

[0247] Determine the forwarding configuration used to ensure synchronization of multiple data streams

[0248] In certain representative embodiments, 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, PDUs may be sent to ensure that PDUs in different flows are sent and / or received to meet one or more joint QoS requirements. As an example, the QoS requirements may be based on any of: thresholds, configurations, triggers, conditions, and / or criteria received from a network and / or an application (e.g., an application function hosted by the WTRU). In one example, the WTRU may perform transmission of PDUs in different flows such that the differences in achievable QoS (e.g., latency, data rate, reliability) between PDUs in different flows are within the QoS requirements associated with the application. In another example, the WTRU may perform transmission of PDUs, such as in a synchronized manner (e.g., simultaneously transmitted 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.

[0249] 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 a posture data flow) may prefer (e.g., require) to receive PDUs in different data flows at one or more entities and / or functions (e.g., a WTRU, a gNB, an edge server function, a remote server function) within a QoS limit (e.g., a latency limit), which may correspond to a QoS difference between PDUs in the first data flow and the second data flow.

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

[0251] 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., co-located with the WTRU) (e.g., higher layer, application layer functions). For example, where PDUs in different associated flows are processed and / or forwarded independently of each other during forwarding and / or transmission, a drift condition may be introduced such that the PDUs in different associated data flows may drift with each other (e.g., reception time drift). Such drift may cause the PDUs in different data flows to arrive at a receiving entity (e.g., a gNB) outside of a synchronization window required by an application.

[0252] In certain representative embodiments, the network may include any of a base station (e.g., a gNB, a TRP, a RAN node), a core network function, and / or an application function (e.g., an edge server function, a remote server function). In certain representative embodiments, a flow may correspond to any of a QoS flow and / or a data flow (e.g., a flow 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, a forwarding configuration may be associated with (e.g., corresponding to) any of: one or more radio bearers, one or more logical channels, one or more configuration parameters in individual layers within an access layer 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 from data and / or QoS flows to radio bearers (e.g., parameters at SDAP), one or more carriers, one or more BWPs, and one or more links (e.g., for delivering PDUs in the UL direction or the DL direction).

[0253] Determine associations between data flows based on configured parameters and / or identifiers

[0254] In certain representative embodiments, a WTRU (e.g., an XR WTRU) may determine whether one or more data flows received and / or sent 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, parameters and / or identifiers for determining associations between flows may be configured in the WTRU (e.g., via RRC signaling, NAS layer signaling, and / or application layer signaling).

[0255] As an example, the parameters and / or identifiers used by the WTRU to identify an association between multiple data flows (e.g., a first flow, a second flow, or more flows) may include any of the following (e.g., a combination of any of the following):

[0256] - Identifiers and / or IDs associated with the stream and / or application

[0257] o For example, the WTRU may determine that the first flow and the second flow may be associated with an application, such as where the WTRU may detect a common ID associated with the application within a PDU of the first flow and / or the second flow (e.g., in a header and / or payload of a data unit).

[0258] The application ID may be pre-configured in the WTRU.

[0259] - Priority and / or importance information associated with the stream

[0260] o For example, the WTRU may determine that the first and second flows may be associated with an application, such as by detecting common and / or similar priority and / or importance indications in PDUs of the first and second flows (eg, in headers and / or payloads).

[0261] ○ For example, the WTRU may determine that the first flow and the second flow may be associated, such as when the priority and / or importance indication detected by the WTRU (e.g., in the header or payload of the data unit) may be above and / or below one or more priority and / or importance thresholds.

[0262] - Time and / or timing information in the associated stream

[0263] o For example, the WTRU may determine that the first stream and the second stream may be associated, such as where one or more PDUs in the first stream and one or more PDUs in the second stream may be received by the WTRU within a duration and / or window. For example, the duration / window may correspond to a time difference between a reception time of the PDU in the first stream (e.g., at "t1") and a reception time of the PDU in the second stream (e.g., at "t2"). For example, when the time difference (e.g., t2-t1) satisfies (e.g., is less than) a duration and / or window threshold, the WTRU may determine that the first stream and the second stream may be associated.

[0264] o For example, the WTRU may determine the first and second flows based on (e.g., the PDUs associated therewith)

[0265] The first stream and the second stream may be associated based on a common format and / or granularity of timing information (e.g., timestamp) carried in the first and second streams.

[0266] - Spatial and / or pose information in the associated stream

[0267] o For example, such as when the PDU carrying spatial information corresponds to a common spatial parameter,

[0268] The WTRU may determine that the first stream and the second stream may be associated. For example, the spatial parameters may include any of the following: direction and / or orientation of the device's FoV, slices and / or tiles of video and / or media frames, position information (e.g., coordinates), posture information, etc.

[0269] For example, the WTRU may determine spatial parameters based on detection of certain PDUs that transmit 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 contain spatial information within the PDU (e.g., in a header and / or payload).

[0270] Passing auxiliary information about application parameters and / or requirements to the network

[0271] In certain representative embodiments, a WTRU (e.g., an XR WTRU) may transmit information associated with applications supported in the WTRU to a network, such as to support application-aware features in the network. For example, information about an application may be transmitted to the network as assistance information, status information, and / or an indication thereof.

[0272] For example, the information associated with the application that may be transmitted by the WTRU to the network may include any (e.g., a combination of any) of the following:

[0273] -Applications supported by the WTRU

[0274] o For example, the WTRU may transmit numbers and / or IDs associated with supported applications.

[0275] The WTRU may (eg, also) communicate information regarding relative priority values ​​and / or absolute priority values ​​associated with supported applications.

[0276] -Data flows associated with the application

[0277] o For example, the WTRU may transmit a number and / or a unique identifier associated with the data streams supported by each application.

[0278] Or ID. The WTRU may (eg, also) transmit information regarding a relative priority value and / or an absolute priority value associated with the data flow.

[0279] -Device associated with the app

[0280] o For example, the WTRU may transmit a number and / or ID associated with each device supported by the application and / or an association of devices.

[0281] -Data and / or traffic types associated with each application's data flow

[0282] ○ For example, the WTRU may transmit information about the data types in the first stream and the second stream 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, tactile data, posture and / or positioning data, audio data, etc.

[0283] - Characteristics and / or parameters of the data and / or services associated with the data flows of each application

[0284] o For example, the WTRU may transmit information regarding characteristics of the first and second flows associated with an application, such as including whether the data is periodic, aperiodic, semi-persistent, quasi-periodic, etc.

[0285] o For example, the WTRU may transmit information about the expected number of PDUs (e.g., per ADU) in one or more flows per application. The information about the number of PDUs (e.g., per ADU) may (e.g., also) include statistical information including any of an average, minimum, maximum, and / or standard deviation value.

[0286] ○ For example, the WTRU may transmit QoS requirements for one or more flows associated with an application, such as any of data rate, latency (e.g., PDB), reliability (e.g., PER), absolute priority value and / or relative priority value, etc.

[0287] For example, the WTRU may transmit information associated with a plurality of data flows associated with an application and / or service to the network based on any (e.g., a combination of any) of the following:

[0288] - During connection and / or session establishment and / or (re)configuration (e.g. process)

[0289] o For example, during any of the RRC connection, PDU session, application session establishment and / or (re)configuration procedures.

[0290] -When changing and / or updating the data flow of each application

[0291] o For example, when a new flow is added and / or an existing flow associated with an application is released.

[0292] - When higher layer and / or application information is received

[0293] o For example, when an indication is received (eg, from an application function hosted in the WTRU and / or the network) indicating any change in supported data types, service characteristics and / or QoS requirements, etc.

[0294] -When changes in measurement and movement are detected

[0295] o For example, when the RSRP,

[0296] Any of RSRQ, RSSI measurements (which may be associated with one or more data streams)

[0297] Above and / or below a threshold.

[0298] ○ For example, when attitude and / or positioning measurements (e.g., position information and / or attitude in 6DoF) are above and / or below attitude thresholds.

[0299] -When a change in time and / or timing properties is detected

[0300] o For example, the WTRU may transmit the information periodically or when a time period (eg, a timer) associated with the transmission of the assistance information is set and / or elapses (eg, expires).

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

[0302] Receives configuration information to ensure simultaneous delivery of multiple streams

[0303] In certain representative embodiments, a WTRU (e.g., an XR WTRU) may perform transmission of PDUs in one or more (e.g., associated) data streams, such as based on one or more parameters, thresholds, and / or trigger conditions, which may be received by the WTRU from the network as configuration information.

[0304] For example, the configuration information received by the WTRU may include any of the following parameters (e.g., any combination of parameters):

[0305] - Expected Time of Arrival (ETA) threshold

[0306] ○ 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 stream, such as where the PDU may be the first PDU or any subsequent PDU after receiving a previous PDU (e.g., the first PDU).

[0307] ○ For example, the ETA threshold may be associated with an expected time for receiving a first PDU in a second data stream after receiving a first PDU in a first data stream, such as where the first and second data streams are associated with an application. In one example, the ETA threshold may be associated with a duration or time value. The WTRU may start a timer at a time instance when the first PDU in the first stream is received and stop the timer when the timer expires at a time instance corresponding to the ETA threshold and / or when the first PDU in the second stream is received (e.g., the first stream and the second stream are associated with the same application). The WTRU may determine the time that has passed between receiving the (e.g., first) PDU in the first stream and receiving the (e.g., first) PDU in the first stream.

[0308] -Expected Data Rate (EDR) threshold

[0309] o For example, the WTRU may receive one or more expected data rate threshold (EDR) values ​​associated with a data rate expected for receiving a PDU in a data stream (e.g., a first PDU or a subsequent PDU after receiving a previous 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 example, the EDR threshold may be associated with a data rate expected for a PDU in a second associated data stream after receiving a PDU having a first data rate value in a first data stream.

[0310] - Expected reliability threshold

[0311] o For example, the WTRU may receive one or more expected reliability threshold (EER) values ​​associated with the reliability expected for receiving a PDU in a data stream (e.g., a first PDU or a subsequent PDU after receiving a previous PDU). The reliability value may correspond to any of the following units: packet error rate, frame error rate, and / or error probability, etc. In another example, the EER threshold may be associated with the reliability expected for one or more PDUs in a second associated data stream after receiving one or more PDUs in a first data stream having a first reliability value.

[0312] - Forwarding configuration parameters

[0313] ○ For example, as part of the forwarding configuration, the WTRU may receive one or more default and / or reference priority values ​​associated with (e.g., corresponding to) a flow channel (e.g., a radio bearer and / or LCH) 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. For example, the first flow channel and the second flow channel may be associated with the same application, and the first default priority value and the second default priority value may be intended to achieve a default QoS performance (e.g., a default latency and / or a default data rate) for PDUs in the first flow channel and the second flow channel during transmission.

[0314] ○ For example, the WTRU may (e.g., also) receive a set of one or more alternative configurations (e.g., non-default configurations), including, for example, alternative parameters and / or thresholds that may be used by the WTRU when performing data transmission. In one example, the alternative configurations may include one or more priority values ​​associated with a stream channel, and the WTRU may be allowed to use the one or more priority values ​​when performing data transmission. For example, when using a first LCH associated with a first data stream, the WTRU may be allowed to use an alternative configuration consisting of a first priority value and / or a second priority value, and / or when using a second LCH associated with a second data stream, the WTRU may be allowed to use an alternative configuration consisting of a third priority value and / or a fourth priority value (e.g., the first data stream and the second data stream are associated with an application).

[0315] o For example, the WTRU may (e.g., also) receive criteria that instruct the WTRU when and / or how to use the default and / or alternative configurations. For example, the criteria may indicate that the default configuration is used when a PDU in the first data flow and / or the second data flow is received within a first expected threshold (e.g., an ETA threshold), and / or that the default configuration is used when a PDU in the first data flow and / or the second data flow is received within a first expected threshold (e.g., an ETA threshold).

[0316] The alternative configuration is used when a PDU in the first data stream and / or the second data stream is received after an ETA threshold).

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

[0318] Synchronize the transmission of PDUs in different associated flows within a time window

[0319] In certain representative embodiments, the WTRU may perform sending of PDUs in different data streams associated with an application and / or service based on one or more ETA thresholds and / or information about how PDUs in different streams may be associated with each other (e.g., using flow IDs) such that the PDUs may be transmitted and / or received within a synchronized time window.

[0320] For example, the WTRU may receive configuration information from the network that includes any of the following parameters (e.g., any combination of parameters):

[0321] -First Expected Time of Arrival (ETA) threshold

[0322] o For example, the first ETA threshold may be associated with a first duration (eg, a normal or default duration) expected for receiving one or more PDUs in the first stream and / or the second stream.

[0323] Associated.

[0324] - Second Expected Time of Arrival (ETA) Threshold

[0325] o For example, the second ETA threshold may be associated with a second duration expected for receiving one or more PDUs in the first flow and / or the second flow (eg, exceeding and / or greater than a normal duration, such as for accelerating delayed PDUs).

[0326] - One or more forwarding configurations (e.g., LCHs and / or radio bearers) having different priority values, such as where 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, where the first data flow and the second data flow may be associated with the same application and / or service.

[0327] o For example, the first forwarding configuration and / or the second forwarding configuration may be associated with a default priority value and / or an alternate priority value.

[0328] - Identifiers and other parameters (e.g. timestamps and / or sequence numbers) to be detected in the PDUs in the first and second streams

[0329] o For example, when the flows are associated with the same application and / or service, the PDUs in the first flow and the second flow may carry (eg, in a packet header) the same or similar identifier and / or ID.

[0330] o For example, the WTRU may use timestamp information and / or sequence numbers (eg, in a packet header) to determine timing information associated with a PDU (eg, arrival time, packet creation time, departure time, and / or remaining time for transmitting the PDU).

[0331] 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 stream from an associated device and / or function (e.g., via a side link and / or via a function and / or entity co-located with the WTRU). For example, the WTRU may identify, based on an identifier and / or ID detectable in a PDU header, that the first PDU in the first stream may belong to an application and / or service (e.g., an XR application) supported by the WTRU. For example, the first PDU may be received by the WTRU at the SDAP layer or at a buffer associated with a first LCH. For example, the WTRU may transmit the first PDU in the first data stream (e.g., via the first LCH) using a default forwarding configuration (e.g., a default priority value associated with the first LCH), such as when transmitting the PDU in the UL to a gNB.

[0332] In certain representative embodiments, the WTRU may start a first timer after receiving a first PDU in a first data stream. For example, the first timer may run (e.g., span) a duration of up to a first ETA threshold. In certain representative embodiments, the WTRU may start a second timer after receiving a first PDU in a first data stream. For example, the second timer may run (span) a duration of up to a second ETA threshold. In one example, the WTRU may start the first timer and the second timer simultaneously, and the WTRU may allow the timers to run for the duration of their respective ETA thresholds. In another example, the WTRU may start and / or stop the timers sequentially. The second timer may be started after the first timer (e.g., the first ETA threshold) expires, and / or the second timer may be allowed to run for the duration of up to the second ETA threshold.

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

[0334] In certain representative embodiments, depending on when the WTRU may receive a first PDU in a second data flow (e.g., associated with a first PDU in a first data flow), the WTRU may take any of the following actions (e.g., any combination of the following actions):

[0335] - For example, when the WTRU receives the first PDU in the second flow before the first ETA threshold (e.g., before the first timer expires or the first ETA threshold passes), the WTRU may:

[0336] o 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 in the UL to the gNB

[0337] To transmit the first PDU in the second stream.

[0338] - 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 after traversing the first ETA threshold) and / or before an end of a second ETA threshold (e.g., before expiration of a second timer or before traversing the second ETA threshold), the WTRU may perform one or more of the following:

[0339] o Determine a priority to be assigned to the first PDU of the second flow based on a time instance when the first PDU of the first flow was received, a time instance when the first PDU of the second flow was received, and a first ETA threshold. For example, the WTRU may determine the time instance when the first PDU in the first flow and / or the second flow was received based on the timestamp information.

[0340] o Determine a priority to be assigned to the first PDU of the second stream based on a reception time of the PDU in the first stream (e.g., at "t1") and a reception time of the PDU of the second stream (e.g., at "t2"). For example, the priority may be assigned such that the time difference between the PDUs in the first stream and the second stream is less than or equal to a first ETA threshold.

[0341] o Determining a time difference between reception of a first PDU of a first stream and a first PDU of a second stream. The WTRU may use a higher priority for delayed PDUs (e.g., PDUs received after an ETA threshold has passed) by determining a compensation delay value that may allow the delayed PDUs to be transmitted in the UL sooner than using a default priority value.

[0342] o Determine (e.g., calculate) a compensation delay value by subtracting a first ETA threshold from the time difference (e.g., t2-t1-first ETA threshold). For example, the priority to be assigned to the PDU may be determined based on a mapping relationship between the calculated compensation delay value and the priority to be assigned. For example, the mapping relationship between the compensation delay and the priority may be received by the WTRU as configuration information (e.g., part of the configuration information).

[0343] o For example, the WTRU may be preconfigured with one or more forwarding configurations that may be associated with different priority values ​​and / or may be preconfigured with at least a forwarding configuration having a priority value that matches the determined priority value to compensate for latency of the PDU in the second flow. The forwarding configuration having the matching priority value may be selected. For example, the WTRU may transmit the first PDU in the second flow to the gNB in ​​the UL using the selected forwarding configuration.

[0344] o For example, the WTRU may not be configured with and / or may not be able to determine at least one active forwarding configuration (e.g., pre-configured and / or activated) that may be associated with a priority value matching the determined priority value to compensate for the latency of the PDUs in the second flow, or a forwarding configuration with a matching priority may be determined to be unavailable (e.g., due to a higher load condition where the number of PDUs buffered in the forwarding configuration or LCH is greater than a threshold), the WTRU may transmit an indication to the network to request configuration and / or activation of a forwarding configuration with the determined priority value. The WTRU may transmit the determined priority value in the indication to be assigned to, for example, a forwarding configuration.

[0345] o After receiving an indication from the network indicating configuration and / or activation of a selected forwarding configuration, the WTRU may transmit the PDUs in the second flow using the configured and / or activated forwarding configuration, such as when transmitting the PDUs in the UL.

[0346] - For example, after a second ETA threshold (e.g., after a second timer expires or passes

[0347] When a first PDU in the second flow is received by the WTRU (after the second ETA threshold), the WTRU may perform one or more of the following:

[0348] o For example, transmitting to the gNB (e.g., in AS layer signaling, MAC CE, UCI) an indication that after a second ETA threshold (e.g., the reception time exceeds a second timer)

[0349] An indication of a PDU in a second flow is received.

[0350] o Upon receiving (e.g., from a gNB) an indication that an available and / or activated forwarding configuration (e.g., LCH) with an indicated priority value is used to transmit the PDU in the second flow, such as when the PDU is transmitted in the UL, transmitting the first PDU in the second flow using the forwarding configuration with the indicated priority value.

[0351] ○ Upon receiving (e.g., from a gNB) a best-effort forwarding configuration (e.g., LCH)

[0352] Following the indication to transmit the PDU in the second flow, the WTRU may transmit the first PDU in the second flow using an available forwarding configuration having a highest priority value and / or having a best effort priority value, such as when transmitting the PDU in the UL.

[0353] o Upon receiving (e.g., from the gNB) an indication to discard the PDUs in the second flow,

[0354] The PDU is discarded and / or may not be transmitted in the UL.

[0355] Transmission of associated PDU groups in different associated flows within a synchronized time window

[0356] 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, associated information of ADUs in different flows, and / or monitoring of reception times (e.g., time instances of arrival) of the PDUs. For example, when transmitting PDUs in a first flow and a second flow that may be associated with an application and / or a service, the WTRU may ensure that the difference in transmission time for transmitting the last PDU associated with the ADU in the first flow and the last PDU associated with the ADU in the second flow is less than or equal to a synchronization time window (e.g., an inter-flow delay limit). For example, the synchronization time window may be associated with an application and / or a service.

[0357] In certain representative embodiments, the WTRU may receive configuration information from the network, and the configuration information may include any (e.g., any combination) of the following:

[0358] -First Expected Time of Arrival (ETA) threshold

[0359] o For example, the first ETA threshold may be associated with a first duration (eg, a normal or default duration) expected for receiving one or more PDUs (eg, associated with one or more ADUs) in the first and second streams.

[0360] - Second Expected Time of Arrival (ETA) Threshold

[0361] o For example, the second ETA threshold may be associated with a second duration (e.g., beyond and / or greater than a normal duration, such as for accelerating delayed PDUs) expected for receiving one or more PDUs (e.g., associated with one or more ADUs) in the first flow.

[0362] Associated.

[0363] o For example, the second ETA threshold may be associated with a first duration (eg, a normal or default duration) expected for receiving one or more PDUs (eg, associated with one or more ADUs) in the second flow.

[0364] o 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 (eg, for accelerated transmission and / or delivery).

[0365] -Third Expected Time of Arrival (ETA) Threshold

[0366] ○ For example, the third ETA threshold may be associated with a second duration expected for receiving one or more PDUs (e.g., associated with one or more ADUs) in the first flow and / or the second flow and / or a third duration (e.g., exceeding and / or greater than a normal duration, such as for accelerating delayed PDUs and / or deciding whether to discard PDUs or transmit PDUs with a best effort configuration).

[0367] - Number of PDUs per ADU expected in the first and second streams

[0368] o For example, the first flow and the second flow may be associated with an application and / or a service.

[0369] o For example, a first flow may have N PDUs per ADU, and a second flow may have M PDUs per ADU (e.g., where N and M may be different integer values). - One or more forwarding configurations with different priority values ​​(e.g., LCH and / or radio

[0370] Loading)

[0371] o 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 forwarding configuration and the second forwarding configuration may be associated with a default priority value and / or an alternate priority value.

[0372] - Identifiers and / or other parameters to be detected in the PDUs in the first and second streams

[0373] o For example, information indicating a timestamp and / or a sequence number may be detected in the PDU.

[0374] o For example, the PDUs in the first and second flows may carry (eg, in a packet header) the same or similar identifiers and / or IDs, such as when the flows are associated with the same application and / or service.

[0375] o For example, the PDUs in the first and second streams may carry (e.g., in a packet header)

[0376] An identifier and / or ID indicating an association with an ADU in a corresponding flow. As an example, one or more PDUs associated with an ADU may carry information related to the ADU (eg, an ADU ID and / or a data type of the ADU).

[0377] o For example, the WTRU may use timestamp information (eg, in a packet header) to determine timing information associated with a PDU and / or ADU (eg, arrival time, packet creation time, departure time, and / or remaining time for transmitting the PDU).

[0378] o For example, the WTRU may use a sequence number (e.g., in a packet and / or PDU header)

[0379] and / or ADU information (eg, ADU ID) to determine whether the PDU is the first PDU, the second PDU, or the Nth PDU associated with the ADU.

[0380] In certain representative embodiments, after receiving the configuration information, the WTRU may receive one or more PDUs associated with the ADU in the first data stream from an associated device and / or function. For example, the WTRU may identify that one or more PDUs in the first stream 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. For example, the first PDU may be received by the WTRU at the SDAP layer or at a buffer associated with the first LCH. The WTRU may use a default forwarding configuration (e.g., a default priority value associated with the first LCH), such as when transmitting the PDU to the gNB in ​​the UL, to transmit one or more PDUs in the first data stream (e.g., the first LCH).

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

[0382] In certain representative embodiments, the WTRU may associate a first duration with the reception of a first PDU associated with an ADU in a first data stream. For example, the first duration may correspond to or may be based on a first ETA threshold. The WTRU may determine the number of PDUs associated with the ADU in the first stream (e.g., based on a sequence number in the PDU) that may be received before the first duration has elapsed (e.g., after the first duration has elapsed). The WTRU may (e.g., also) determine the number of PDUs associated with another ADU that were received in a second stream before the first duration has elapsed (e.g., after the first duration has elapsed).

[0383] In certain representative embodiments, the WTRU may start a second timer and / or a third timer after receiving a first PDU in a first data stream. For example, the second timer and / or the third timer may run (e.g., respectively) for a duration up to a second ETA threshold and / or a third ETA threshold. In one example, the WTRU may start the first timer, the second timer, and the third timer simultaneously, and the WTRU may let the timers run for a duration up to their respective ETA thresholds. In another example, the WTRU may start the timers sequentially, wherein the second timer may be started after the first timer expires (e.g., at the first ETA threshold), and / or the third timer may be started after the second timer expires (e.g., at the second ETA threshold). For example, the WTRU may let the second timer and / or the third timer run for a duration up to their respective ETA thresholds (e.g., the second threshold and the third threshold).

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

[0385] In certain representative embodiments, 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, a WTRU (e.g., an XR WTRU) may perform any of the following actions (e.g., any combination):

[0386] - For example, when a last PDU associated with the ADU in the first flow and / or one or more PDUs associated with the ADU in the 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):

[0387] ○ Using a corresponding default forwarding configuration associated with the first flow and / or the second flow (e.g., using a default priority value associated with the first LCH and / or the second LCH), such as when transmitting PDUs in the UL to the gNB, transmitting 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.

[0388] For example, when one or more PDUs associated with the ADUs in the first flow and / or one or more PDUs associated with the ADUs in the 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 an end of a second ETA threshold (e.g., before expiration of a second timer or before a second duration has elapsed):

[0389] o based on the time instances when different (e.g. batches of) PDUs of the first flow are received,

[0390] Determining a priority to be assigned to one or more PDUs (e.g., including a last PDU) associated with an ADU in a first flow. For example, different PDUs of the first flow may include batches of PDUs received before and after a first ETA threshold (e.g., after a first duration has elapsed). For example, the WTRU may determine a time instance when a PDU in the first flow is received based on the timestamp information.

[0391] o Based on the reception time of the PDUs in the first batch in the first stream (e.g., after

[0392] The priority to be assigned to one or more PDUs (e.g., including the last PDU) of the first stream received after the first ETA threshold based on the reception time of the PDUs in the second batch of the first stream (e.g., PDUs received before the duration associated with the first ETA threshold) and the reception time of the PDUs in the second batch of the first stream (e.g., PDUs received after the duration associated with the first ETA threshold has elapsed). For example, the priority may be determined and / or assigned such that the time difference between the last PDU in the first batch of the first stream (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 duration associated with the ETA threshold has elapsed) by determining a compensation delay value that allows the delayed PDUs to be transmitted in the UL more quickly than using a default priority value.

[0393] o Calculate the compensation delay value (e.g., by subtracting the first ETA threshold from the time difference)

[0394] For example, the priority to be assigned to the PDU in the second batch may be determined based on the mapping relationship between the calculated compensation delay value and the priority to be assigned. For example, the mapping relationship between the compensation delay and the priority may be determined by

[0395] The WTRU receives as (eg, as part of) configuration information.

[0396] o Use the default value associated with the second flow, such as when transmitting PDUs in the UL to the gNB

[0397] The first LCH may further include a forwarding configuration (eg, using a default priority value associated with the second LCH) and transmitting one or more PDUs associated with the ADU in the second flow.

[0398] o In the case where the WTRU is pre-configured with one or more forwarding configurations, the forwarding

[0399] The configurations may be associated with different priority values ​​and / or may be pre-configured with at least a forwarding configuration having a priority value that matches the determined priority value to compensate for the latency of the PDUs in the second batch in the first flow, selecting the forwarding configuration having the matching priority value. For example, the WTRU may transmit the PDUs in the first flow in the UL (e.g., in the second batch) to the gNB using the selected forwarding configuration.

[0400] o In the event that the WTRU may not have found and / or determined at least one active forwarding configuration (e.g., preconfigured and / or activated), the active forwarding configuration may be associated with a priority value matching the determined priority value to compensate for the latency of the PDUs in the second batch in the first flow, or a forwarding configuration with a matching priority may be determined to be unavailable. For example, the WTRU may convey in an indication the determined priority value to be assigned to the forwarding configuration.

[0401] ○ After receiving information from the network indicating configuration and / or activation of the selected forwarding configuration, such as when transmitting PDUs in the UL to the gNB, the PDUs in the second batch in the first flow are transmitted using the configured / activated forwarding configuration.

[0402] - For example, after a second ETA threshold (e.g., after a second timer expires or

[0403] After the second duration has elapsed) and / or before the third ETA threshold has expired (e.g., before the third timer expires or before the third duration has elapsed) the WTRU receives a

[0404] When one or more PDUs are associated with an ADU in the second stream:

[0405] o Determining a priority to assign to one or more PDUs (e.g., including a last PDU) associated with the ADU in the second stream based on a time instance when different batches of PDUs of the second stream are received. For example, different batches may be received before and after a first ETA threshold and / or a second ETA threshold (e.g., an elapsed duration). For example, the WTRU may determine the time instance when the PDU in the second stream is received based on the timestamp information.

[0406] o Determine a priority to be assigned to one or more PDUs (e.g., including the last PDU) of the second stream received after the second ETA threshold (e.g., after the second duration has passed) based on the reception time of the PDUs in the first batch of the second stream (e.g., PDUs received before the first ETA threshold and / or the second ETA threshold or before the first duration and / or the second duration has passed) and based on the reception time of the PDUs in the second batch of the second stream (e.g., PDUs received after the second ETA threshold or after the second duration has passed). For example, the priority may be determined so that the time difference between the last PDU in the first batch (e.g., at "t1") and the last PDU in the second batch of the second stream (e.g., at "t2") is less than or equal to the second ETA threshold.

[0407] o Calculate the compensation delay value, such as by subtracting the first ETA threshold from the time difference (e.g., t2-t1-first ETA threshold). For example, the WTRU may determine the priority to be assigned to the PDUs in the second batch based on a mapping relationship between the calculated compensation delay value and the priority to be assigned.

[0408] o In the event that the WTRU may be pre-configured with one or more forwarding configurations that may be associated with different priority values ​​and / or at least pre-configured with a forwarding configuration having a priority value that matches the determined priority value, to compensate for the latency of the PDUs in the second batch in the second flow, the forwarding configuration having the matching priority value is selected. For example, the WTRU may transmit the PDUs in the second batch in the second flow to the gNB using the selected forwarding configuration, such as in the UL.

[0409] o In the event that the WTRU may not have found and / or determined at least one active forwarding configuration (e.g., preconfigured and / or activated) that may be associated with a priority value matching the determined priority value to compensate for latency of the PDUs in the second batch in the second flow, or a forwarding configuration with a matching priority may be determined to be unavailable, transmitting information to the network indicating a request to configure and / or activate a forwarding configuration with the determined priority value. For example, the WTRU may transmit the determined priority value in an indication to be assigned to, for example, a forwarding configuration.

[0410] o Upon receiving an indication from the network indicating configuration and / or activation of a selected forwarding configuration, transmitting the PDUs in the second batch in the second stream using the configured and / or activated forwarding configuration, such as when transmitting the PDUs in the UL.

[0411] - After a second ETA threshold (e.g., after expiration of a second timer or after a

[0412] (2) after the WTRU receives one or more PDUs in the first stream and / or

[0413] or upon reception by the WTRU of one or more PDUs in the second flow after a third ETA threshold (e.g., after expiration of a third timer or after a third duration has expired):

[0415] ○ Transmitting information to the gNB (e.g., in AS layer signaling, MAC CE and / or UCI) indicating that the PDU in the first flow and / or the second flow is received after the second ETA threshold and / or the third ETA threshold (e.g., the reception time exceeds the second timer and / or the third timer, or the reception time is after the second duration and / or the third duration has elapsed).

[0416] ○ Upon receiving an indication (e.g., from a gNB) indicating that an available and / or activated forwarding configuration (e.g., LCH) with an indicated priority value is to be used to transmit the PDUs in the first stream and / or the second stream, transmit the PDUs in the first stream and / or the second stream using the forwarding configuration with the corresponding indicated priority value, such as when the PDUs are transmitted in the UL.

[0417] o Upon receiving (e.g., from the gNB) an indication to use a best-effort forwarding configuration (e.g.,

[0418] When transmitting the PDUs in the UL, in the event that an indication is given on the WTRU that the PDUs in the first flow and / or the second flow are transmitted via the WTRU LCH, the WTRU may transmit the PDUs in the first flow and / or the second flow using an available forwarding configuration having a highest priority value and / or having a best effort priority value.

[0419] ○ Upon receiving (e.g., from a gNB) an indication to discard PDUs in the first stream and / or the second stream, discard the PDUs and / or not transmit the PDUs (such as in the UL to the gNB).

[0420] Satisfy QoS requirements based on association between multiple flows

[0421] In certain representative embodiments, the WTRU may determine one or more actions to be performed with respect to a plurality of data flows (e.g., a first flow and a second flow). For example, upon determining an association between one or more UL and / or DL ​​data flows (e.g., based on an indication related to a traffic characteristic 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).

[0422] For example, the WTRU may determine (e.g., enable) an association of one or more PDUs (e.g., PDU sets and / or ADUs) from different data streams to be forwarded and / or delivered (e.g., in a coordinated manner). One or more (e.g., joint) QoS requirements (e.g., any of a synchronization time window, latency, and / or data rate) may be common and applicable to one or more associated streams that may be satisfied (e.g., between different data streams). In one example, any action performed by the WTRU based on the determined association between the multiple streams may correspond to ensuring synchronization of data in the data streams during transmission and / or reception. For example, any of the actions that may be performed by the WTRU may include any of the following: selecting and / or changing a resource (e.g., forwarding) configuration for forwarding and / or delivering data in different data streams, selecting and / or changing forwarding configuration parameters for forwarding and / or delivering data in different data streams, and / or transmitting information indicating the selected and / or changed forwarding configuration and / or forwarding configuration parameters (e.g., transmitted to the network and / or higher layers).

[0423] In certain representative embodiments, associations between different data flows may be detected by the WTRU. The WTRU may detect associations between different data flows at different layers (such as the application layer, the NAS layer) and / or at any access layer (e.g., radio bearer, SDAP, PDCP, MAC, PHY). For example, when an association between flows is detected at the SDAP layer (e.g., based on receiving an indication from a higher layer / application of a common ID in a PDU indicating two flows), the WTRU may perform certain actions (e.g., by selecting a set of parameters configured at the MAC layer) for forwarding the PDU in the second flow, such as when certain service and / or QoS related events (e.g., latency increases above a threshold) are detected while forwarding the PDU in the first flow.

[0424] As another example, the association between data streams may vary and / or be determined at a combination of different dimensions and / or domains, including a time domain (e.g., the association may apply over a time window and / or duration), a frequency domain (e.g., the association may apply when transmission and / or reception is performed on a set of channels, carriers, links, and / or frequency resources), and / or a spatial domain (e.g., a common location and / or area that the data streams may originate from or be destined / to, and / or a common set of beams used to transmit and / or receive the streams). Upon determining any change in the association between data streams in different dimensions and / or domains, the WTRU may perform certain actions. Any indication and / or trigger that may be configured in the WTRU for determining an association between one or more data streams in the UL and / or DL, and / or corresponding actions for ensuring coordinated transmission / reception of associated streams may include any of the following:

[0425] - Changes in achievable and / or expected QoS

[0426] o For example, the WTRU may determine whether one or more flows may be associated and / or whether corresponding actions may be performed upon detecting certain changes in achievable and / or expected QoS-related measurements in any associated flow (e.g., latency and / or data rate increases above a threshold, and / or latency and / or data rate decreases below a threshold);

[0427] -Changes in channel / link measurements

[0428] ○ For example, the WTRU may determine whether any actions may be performed when sending and / or receiving data in different associated streams, such as upon detecting certain changes in measurements related to the channel, link and / or beam used during the transmission and / or reception of the data stream (e.g., RSRP measurements increase and / or decrease above or below a threshold). For example, upon detecting a deterioration in measurements made on a first channel (e.g., CSI-RS associated with a first resource set and / or beam set) used to send data in a first stream, the WTRU may perform certain actions (e.g., drop and / or suspend transmission) when sending data in a second stream using a second channel (e.g., a second resource set and / or beam set). For example,

[0429] The WTRU may perform actions for sending data in the second flow regardless of any degradation that the second channel may be experiencing.

[0430] - Receive instructions from the network and / or higher layers

[0431] ○ For example, the WTRU may determine whether any action can be performed after 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., multiple changes) related to traffic forwarding and / or data delivery in any associated flow.

[0432] The indications and / or notifications may include any of status reports, feedback (e.g., HARQ ACK / NACK), flow control indications, error rates (e.g., PER for a PDU or a set of PDUs), and / or uncertainty information (e.g., due to estimation and / or prediction of QoS). For example, the WTRU may use one or more indications and / or notifications to determine whether the associated flows can meet (e.g., joint) QoS requirements.

[0433] -Timer / Periodic

[0434] o For example, the WTRU may be configured with a timer (e.g., duration and / or periodicity) for determining whether any action can be performed.

[0435] When the WTRU detects one or more associated events (e.g., a delay between the reception of a first PDU in a first stream and a first PDU in a second stream is greater than (or less than) a threshold), a timer (e.g., a duration and / or a periodicity) may be applied. As an example, the WTRU may start a timer (e.g., determine a duration and / or a periodicity) upon detecting an associated event.

[0436] or the beginning of an interval) and / or may be triggered upon expiration of a timer (e.g., after a duration and / or

[0437] As another example, the WTRU may be configured to determine (e.g., periodically) whether an action may be performed based on (e.g., periodically) determining an association between one or more flows in the UL and / or DL.

[0438] In certain representative embodiments, the WTRU may perform actions to ensure that the joint QoS requirements are met based on the determination of association between data flows during UL transmission and / or DL ​​reception. For example, the WTRU may perform any one of one or more of the following actions (e.g., a combination):

[0439] - Perform QoS compensation during data forwarding in the associated flow:

[0440] o For example, a WTRU may be configured with one or more resource (e.g., forwarding) configurations

[0441] (e.g., radio bearer configuration, LCH configuration, and / or resource configuration such as configuration grant, BWP). Upon detecting any event that may affect synchronization and / or association between flows during data transmission and / or reception (e.g., actual QoS is different from expected QoS), the WTRU may select a pre-configured forwarding configuration to compensate for the change in QoS in one or more associated flows.

[0442] 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 forwarding configuration (e.g., a new configuration grant with a higher periodicity and / or payload size). The WTRU may select a forwarding configuration based on a determination of a difference between delays incurred by PDUs in an associated second flow and an associated first flow (e.g., the PDUs in the first flow may be sent to catch up with the PDUs in the second flow while reducing and / or minimizing the difference in delay). For example, the WTRU may transmit a request to the network to activate a (e.g., pre-configured) forwarding configuration and

[0443] and / or configuring a (eg, new) forwarding configuration to compensate for an indication of QoS.

[0444] o For example, upon detecting delayed transmission of one or more PDUs in a first stream, the WTRU may decide whether to transmit and / or discard transmission of one or more PDUs in an associated second stream (e.g., based on one or more criteria). The WTRU may determine whether to receive PDUs in a first stream when reception of PDUs in an associated second stream may be delayed (e.g., based on one or more criteria). Criteria (e.g., conditions) used to make a determination (e.g., whether to transmit, receive, discard and / or skip a PDU)

[0445] This may include a degree of association between the flows (e.g., fully or partially associated based on an association value), a priority and / or importance of the PDUs in the associated flows, and / or an amount of difference between QoS achievable by the PDUs in the associated flows. For example, when a priority value of a PDU in a second flow is greater than a threshold, such as when a delay during transmission and / or reception of a PDU in a first flow is detected, the WTRU may decide to transmit and / or receive the PDU. For example, when a priority value of a PDU in a second flow is less than a threshold, the WTRU may decide to discard transmission of a PDU in a second flow and / or skip reception of a PDU in a second flow when the PDU in the first flow is delayed.

[0446] - re-adjust / re-align the QoS in the associated flows, and / or

[0447] ○ For example, when a change in the achievable QoS in one or more other associated flows is detected (e.g., during data transmission and / or reception), the WTRU may determine an adjustment amount (e.g., readjustment and / or realignment) that may be applied to the QoS of one or more flows.

[0448] o For example, when the WTRU detects that the QoS (e.g., data rate and / or latency) in a first flow increases or decreases 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 an associated second flow, such as based on an association between the flows. If 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 (e.g., similar or corresponding) alignment and / or adjustment amount to the QoS in the second flow, such as by indicating a change in the forwarding configuration to the network to align the QoS and / or change the forwarding configuration parameters to match the determined amount (e.g., aligning the QoS so that the QoS in both flows matches).

[0449] o For example, the WTRU may determine an offset for a start time (e.g., a start time of a slot, mini-slot, subframe, frame, or other TTI) for periodic data transmission of a first stream using a first resource (e.g., a first configured grant) based on a determination of a (e.g., similar or corresponding) offset for starting periodic data transmission of an associated second stream using a second resource (e.g., a second configured grant).

[0450] The WTRU may transmit to the network (e.g., in RRC, MAC CE, and / or UCI)

[0451] An indication of an offset determined for the first configuration authorization configuration and / or the second configuration authorization configuration.

[0452] - transmits instructions and / or information about associated flows to the network

[0453] o For example, the WTRU may transmit (e.g., in an RRC, MAC CE, and / or UCI) one or more indications to the network 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., ensuring synchronization and / or association of different flows). The one or more indications may include any of: a request to help synchronize the 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.

[0454] Instructions for changing resource configuration

[0455] In certain representative embodiments, the WTRU may transmit one or more indications (e.g., in RRC, MAC CE, and / or UCI) to the network. For example, the WTRU may transmit information indicating any of the following: an inability to determine and / or select an appropriate forwarding configuration, updating QoS during subsequent transmission and / or reception of a set of one or more previously transmitted PDUs in different flows, and / or discarding a set of one or more previously transmitted PDUs.

[0456] In certain representative embodiments, the WTRU may be configured with one or more resource configurations. The one or more resource configurations may include one or more configuration 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 for ensuring that data transmission in the UL and / or reception in the DL of one or more associated streams can be performed within the synchronous RTT window. The SPS configuration may include one or more SPS parameters (e.g., start offset time, periodicity, payload size), such as for ensuring that data transmission in the UL and / or reception in the DL of one or more associated streams can be performed within the synchronous RTT window. The RTT delay (e.g., for a given data stream) may be measured between the transmission of one or more PDUs (e.g., a PDU set or ADU) in the UL and the reception of one or more PDUs (e.g., a PDU set or ADU) in the DL. For example, the RTT delay may be measured between the transmission of one or more PDUs in the UL during the active time of the CG configuration and the reception of one or more PDUs in the DL during the active time of the SPS configuration (e.g., associated with the UL transmission).

[0457] In certain representative embodiments, the synchronization 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 (e.g., associated) first stream and the transmission and reception of one or more PDUs (e.g., PDU sets or ADUs) in a (e.g., associated) second stream. The WTRU may be configured with (e.g., joint) QoS requirements. For example, the QoS requirements may ensure that the synchronization RTT window (e.g., multi-stream RTT time difference between multiple streams) remains above (or below) a threshold. The WTRU may be configured to monitor whether any changes are observed in the per-stream RTT of each stream and / or the multi-stream RTT time difference (e.g., between different associated streams). Based on the monitoring, the WTRU may determine whether any changes may be applied to the parameters of the resource configuration (e.g., CG and / or SPS configuration) and / or select a set of (e.g., new or pre-configured) resource configurations (e.g., CG configurations and / or SPS configurations) that ensure that the (e.g., joint) QoS requirements are met (e.g., the RTT time difference is below the threshold and / or remains within a certain range).

[0458] In certain representative embodiments, the WTRU may be configured with one or more resource configurations by the network based on statistical information related to the RTT delay of different associated flows (e.g., average, standard deviation, minimum, maximum). For example, the WTRU may provide and / or indicate the statistical information in auxiliary 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 configuration grant (CG) configurations and / or one or more semi-persistent scheduling (SPS) configurations. For example, the WTRU may (e.g., also) be configured with (1) one or more per-flow RTT thresholds for one or more flows (e.g., corresponding to the maximum or minimum difference in delay from an average / expected RTT delay value) and / or (2) one or more multi-flow RTT time difference thresholds between different associated flows. For example, the WTRU may (e.g., also) be configured with information indicating an association between a per-flow RTT threshold and / or a multi-flow RTT threshold and a resource configuration (e.g., a CG and / or SPS configuration). For example, the information may (e.g., also) indicate the effectiveness of using any of the CG and / or SPS configurations when sending and / or receiving data within a per-stream RTT threshold and / or within a multi-stream RTT threshold. As another example, the information may (e.g., also) indicate parameters (e.g., offset values, periodicity) of the CG and / or SPS configurations that may be changed, such as to realign the CG and / or SPS configurations with changes in per-stream RTT and / or multi-stream RTT.

[0459] In certain representative embodiments, one or more (e.g., triggering) events and / or conditions may be monitored by the WTRU. Monitoring of events and / or conditions may be performed by the WTRU to determine whether any resource configuration and / or parameters of resource configuration (e.g., for CG and / or SPS) may be changed, such as to meet per-stream RTT delay and / or multi-stream RTT delay. For example, the (e.g., triggering) events and / or conditions may include any of the following:

[0460] - Connection and / or session (re)configuration

[0461] o For example, when receiving and / or sending an RRC connection with one or more associated flows,

[0462] Any signalling message associated with (re)configuration of RRC state, PDU session and / or application layer session;

[0463] o For example, when changing the RRC state of the WTRU from RRC CONNECTED to RRC INACTIVE or IDLE, or vice versa;

[0464] - Receipt of higher layer and / or application layer indications

[0465] o For example, when an indication is received from any higher layer, from one or more PDUs of one or more associated flows (e.g., information in the headers of the one or more PDUs), and / or from network information indicating any of the following changes in upcoming data that may be sent and / or received using either the CG configuration and / or the SPS configuration:

[0466] ■ Data type (e.g., the upcoming frame changes from a P / B frame to an I frame);

[0467] ■ the priority, importance and / or relative priority and / or importance of a data type (e.g., I-frame or P-frame);

[0468] ■ Higher layer frame failure (e.g., the application layer failed to decode an I frame);

[0469] ■ Traffic characteristics (e.g., the number of PDUs in a PDU set is expected or determined to be above or below a threshold, the PDB 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 increases above or decreases below a threshold);

[0470] ■ 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);

[0471] ■ QFI and / or any QoS indication and / or marking (e.g., a QFI value is expected or determined to be greater than or less than a threshold);

[0472] - Duration, interval and / or periodicity

[0473] o For example, the WTRU may determine whether any of the CG configuration and / or SPS configuration may be changed when a timer (e.g., duration and / or interval) configured to monitor per-stream RTT latency and / or multi-stream RTT latency is started and / or elapses. 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);

[0474] -Change and / or update the data flow of each application

[0475] o For example, when one or more (e.g., new) flows are added and / or (e.g., existing) flows associated with an application are released;

[0476] - Jitter measurement

[0477] o For example, when a measured jitter value in one or more data streams (e.g., the difference between an expected time slot or other TTI when data is expected to be received and an actual time slot or other TTI when data is actually received) is above or below a threshold;

[0478] - Radio link measurements

[0479] o For example, when RSRP, RSRQ, and / or RSSI measurements of a signal, channel, beam, carrier, and / or link, etc. (e.g., associated with one or more data streams transmitted and / or received by the WTRU) are above and / or below a threshold;

[0480] - Changes in mobility, and / or

[0481] o 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;

[0482] -Changes in power saving configuration

[0483] o For example, when any of the parameters and / or configurations associated with CDRX and / or DRX (eg, cycle duration, on-time, and / or inactive time) used during transmission and / or reception of data in different streams is changed.

[0484] In certain representative embodiments, the WTRU may determine a per-stream RTT and / or multi-stream RTT delay for associated data streams. For example, if the WTRU is configured with one or more resource (e.g., CG and / or SPS) configurations, the WTRU may determine a per-stream RTT and / or multi-stream RTT delay based on a measurement of the time difference between the transmission and / or reception of PDUs in different associated streams or based on another indication received from a higher layer and / or the network. For example, the WTRU may compare the measured per-stream RTT and / or multi-stream RTT delay relative to a (e.g., configured) threshold set to determine whether any resource (e.g., CG and / or SPS) configuration is valid for sending and / or receiving data. For example, if the WTRU determines that the per-stream RTT and / or multi-stream RTT delay is above and / or below a configured threshold set, the WTRU may transmit to the network (e.g., via an RRC message, MAC CE and / or UCI) an indication and / or request to change parameters of the resource (e.g., CG and / or SPS) configuration or select a (e.g., new) resource (e.g., CG and / or SPS) configuration so that data transmission and / or reception in different streams can be aligned with the determined per-stream RTT delay and / or multi-stream RTT delay.

[0485] In one example, when it is determined that the per-stream RTT delay of a first stream is above a threshold, the WTRU may infer a similar and / or corresponding (e.g., comparable) change in the per-stream RTT delay of an associated second stream. When determining the change in the per-stream RTT delay, the WTRU may determine one or more updates and / or changes to the resource (e.g., CG and / or SPS) configuration and / or its parameters that may be used to (re)align the transmission / reception of the PDUs in the two streams (e.g., the first stream and the second stream) so that the multi-stream RTT delay remains below the threshold. The WTRU may transmit (e.g., explicitly or implicitly) an indication of the determined change to the resource (e.g., CG and / or SPS) configuration to the network (e.g., in an RRC, MAC CE, and / or UCI), and / or perform data transmission and / or reception in a different data stream with an updated and / or changed resource configuration. For example, after receiving an indication and / or confirmation (e.g., explicitly or implicitly) from the network (e.g., in an RRC, MAC CE, and / or DCI), the WTRU may perform data transmission and / or reception in a different data flow with an updated and / or changed resource configuration. As another example, the WTRU may perform data transmission and / or reception in a different data flow with an updated and / or changed resource configuration after a timer has expired (e.g., a duration has elapsed).

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

[0487] exist Figure 2, the WTRU 202 may receive a PDU 206, 208, 212, 214 from the WTRU 102-a and / or the WTRU 102-b (e.g., from a previous ADU of the first flow and / or the second flow) before the first threshold and the second threshold have been passed. The WTRU 202 may continue to send (e.g., forward) the PDU 206, 208, 212, 214 using the first resource configuration. For example, the first resource configuration may be a configuration grant (CG) resource configuration that includes resources for a plurality of transmit opportunities 222, 224, 226, etc. Figure 2 , the WTRU 202 may use the transmit opportunity 222 to transmit the PDUs 206, 208, 212, 214 to the base station 204. For example, the first transmit opportunity 222 may ensure synchronization between the first stream and the second stream such that, from the perspective of the base station 204, the PDUs 208, 206, 212, 214 transmitted using the first transmit opportunity 222 are received at the base station 204 within a third threshold 230 (e.g., latency between PDUs, ADUs, and / or streams).

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

[0489] exist Figure 3In the example, the WTRU 202 may receive PDUs 206, 208, 212, 214 from the WTRU 102-a and / or the WTRU 102-b (e.g., from a previous ADU of the first flow and / or the second flow) after the first threshold has been passed and before the second threshold has been passed. The WTRU 202 may continue to send (e.g., forward) the PDUs 206, 212, 214 using the first resource configuration. For example, the first resource configuration may be a configuration grant (CG) resource configuration that includes resources for a plurality of transmit opportunities 222, 224, 226, etc. ... Figure 3 , the WTRU 202 may use the transmit opportunity 222 to send the PDUs 206, 212, 214 to the base station 204. Since the WTRU 202 receives the PDU 208 after the first threshold 218 but before the second threshold 220, the WTRU 202 may continue to send (e.g., forward) the PDU 208 using the second resource configuration. For example, the second resource configuration may be a configuration grant (CG) resource configuration that includes resources for multiple transmit opportunities 302, 304, etc. Figure 3 2, the WTRU 202 may use the transmit opportunity 302 (e.g., after the transmit opportunity 222) to transmit the PDU 208 to the base station 204. For example, the use of the transmit opportunities 222 and 302 may ensure synchronization between the first stream and the second stream such that, from the perspective of the base station 204, the PDUs 206, 212, 214 transmitted by the WTRU 202 are received at the base station 204 within a third threshold 230 (e.g., latency between PDUs, ADUs, and / or streams).

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

[0491] exist Figure 4 , the WTRU 202 may receive the PDU 206, 212, 214 from the WTRU 102-a and / or the WTRU 102-b (e.g., from a previous ADU of the first flow and / or the second flow) before the first threshold and the second threshold have been passed. The WTRU 202 may receive the PDU 208 after the first threshold and the second threshold have been passed (e.g., outside the synchronization time window). The WTRU 202 may continue to send (e.g., forward) the PDUs 206, 208, 212, 214 using the first resource configuration. For example, the first resource configuration may be a configuration grant (CG) resource configuration that includes resources for multiple transmission opportunities 222, 224, 226, etc. Figure 4 2, the WTRU 202 may use the transmit opportunity 222 to transmit the PDUs 206, 212, 214 to the base station 204. For example, the first transmit opportunity 222 may ensure synchronization between the first stream and the second stream such that the PDUs 206, 212, 214 transmitted using the first transmit opportunity 222 are received at the base station 204 within a third threshold 230 (e.g., latency between PDUs, ADUs, and / or streams) from the perspective of the base station 204. In addition, the WTRU 202 may use the transmit opportunity 224 to transmit at least the PDU 208 to the base station 204. Since the PDU 208 is received after the first threshold and the second threshold, synchronization between the first stream and the second stream may not be ensured such that the PDU 208 is received at the base station 204 outside or after the third threshold 230.

[0492] In certain representative embodiments, multiple streams may be synchronized on a per PDU basis and / or on a per ADU basis, such as Figures 2 to 4 In other representative embodiments, stream synchronization may be performed on a basis other than PDUs or ADUs, such as but not limited to PDU aggregations.

[0493] Figure 5 is a process diagram illustrating an example process for synchronizing multiple streams. In certain representative embodiments, Figure 5 The process in may generally be implemented by a WTRU 102 (such as WTRU 202). At 502, the WTRU 102 may send (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 the 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) at 506 one or more PDUs of a first ADU of the first flow and one or more PDUs of a second ADU of the second flow. At 508, the WTRU 102 may send (e.g., to or towards the base station 204) the one or more PDUs of the first ADU of the first flow using the first resource configuration. At 510, if (1) the last PDU of the second ADU of the second stream is received after a first time threshold has passed since the last PDU of the first ADU of the first stream was received and (2) the last PDU of the second ADU of the second stream is received before a second time threshold has passed since the last PDU of the first ADU of the first stream was received, the WTRU 102 may use a second resource configuration to send at least the last PDU of the second ADU of the second stream.

[0494] In certain representative embodiments, the first resource configuration may be a first configuration authorization configuration, and the second resource configuration may be a second configuration authorization configuration. For example, the size of the transmission opportunities (e.g., time and / or frequency resources) associated with the first resource configuration is greater than the size of the transmission opportunities associated with the second resource configuration. For example, the first resource configuration may include a first plurality of transmission opportunities having a first periodicity, and the second resource configuration may include a second plurality of transmission opportunities having a second periodicity less than the first periodicity.

[0495] In certain representative embodiments, sending one or more PDUs of a first ADU of a first stream using a first resource configuration may include sending one or more PDUs of the first ADU of the first stream using a (e.g., a single) transmission opportunity according to the first resource configuration and one or more PDUs of a second ADU received before the last PDU of the second ADU.

[0496] In certain representative embodiments, at least a last PDU of a second ADU of a second flow sent using a second resource configuration has a timing offset after one or more PDUs of a first ADU of a first flow sent using a first resource configuration.

[0497] In certain representative embodiments, the first resource configuration may be associated with the first flow and / or the second flow. 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.

[0498] In certain representative embodiments, the ADUs of the first stream and the ADUs of the second stream are received by a WTRU 102 from another WTRU 102 (eg, using sidelink resources).

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

[0500] Figure 6 is a process diagram illustrating another example process for synchronizing multiple streams. In certain representative embodiments, Figure 6 The process in may be generally implemented by a WTRU 102 (such as WTRU 202). Figure 6, the WTRU 102 may send (e.g., to a base station) 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 602. 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 a first ADU of the first flow and one or more PDUs of a second ADU of the second flow. Following 606, the WTRU may send (e.g., to or towards the base station) the one or more PDUs of the first ADU of the first flow using a first transmission opportunity indicated by the first resource configuration at 608. At 610, if (1) the last PDU of the second ADU of the second stream is received after a first time threshold and a second time threshold have passed since the last PDU of the first ADU of the first stream was received, the WTRU 102 may use a second transmission opportunity indicated by the first resource configuration to send at least the last PDU of the second ADU of the second stream.

[0501] In certain representative embodiments, the first resource configuration may be a first configuration authorization configuration, and / or the second resource configuration may be a second configuration authorization configuration. For example, the size of the transmission opportunity (e.g., time and / or frequency resources) associated with the first resource configuration may be greater than the size of the transmission opportunity associated with the second resource configuration. For example, the first resource configuration may include a first plurality of transmission opportunities having a first periodicity, and / or the second resource configuration may include a second plurality of transmission opportunities having a second periodicity less than the first periodicity.

[0502] In certain representative embodiments, one or more PDUs of a first ADU of a first stream sent using a first sending opportunity of a first resource configuration may include at least one other PDU received before a last PDU of a second ADU of a second stream sent using the first sending opportunity of the first resource configuration.

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

[0504] In certain representative embodiments, the ADUs of the first stream and the ADUs of the second stream are received by a WTRU 102 from another WTRU 102 (eg, using sidelink resources).

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

[0506] Figure 7 is a process diagram illustrating an example process for synchronizing multiple streams. In certain representative embodiments, Figure 7 The processes in may generally be implemented by a base station, such as 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 an ADU of the first flow and an ADU of the second flow. At 704, the base station may transmit information to the WTRU indicating any of a first resource configuration, a second resource configuration, a first time threshold, and / or a second time threshold. At 706, the base station may receive (e.g., from the WTRU 102) one or more PDUs of a 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 a last PDU of a second ADU of the second flow using the second resource configuration. For example, receiving a last PDU of a second ADU of a second stream using a second resource configuration may indicate (e.g., to a base station) that WTRU 102 received the last PDU of the second ADU of the second stream (1) after a first threshold has passed since WTRU 102 received the last PDU of the first ADU of the first stream and (2) before a second threshold has passed since WTRU 102 received the last PDU of the ADU of the first stream.

[0507] Figure 8 is a process diagram illustrating another example process for synchronizing multiple streams. In certain representative embodiments, Figure 8The processes in 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 stream and a second stream and (2) a maximum time difference between an ADU of the first stream and an ADU of the second stream. 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 stream using a first transmit opportunity 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 stream using a second transmit opportunity of the first resource configuration. For example, receiving at least a last PDU of the second ADU in the second stream using the second transmit opportunity may indicate (e.g., to the base station) that the WTRU 102 received a last PDU of the second ADU of the second stream after a first threshold and a second threshold have passed since the WTRU 102 received the last PDU of the first ADU of the first stream.

[0508] Fig. 9 is a process diagram illustrating an example of sending multiple streams using priority levels. In certain representative embodiments, Fig. 9 The process in may generally be implemented by a WTRU 102 (such as WTRU 202). At 902, the WTRU 102 may receive (e.g., from a base station) first information indicating a first time threshold, a second time threshold, and / or any one of 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 a higher layer) a first protocol data unit (PDU) of a first flow. At 906, the WTRU 102 may send (e.g., to or toward a base station) the 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 a higher layer) a second PDU of a second flow. At 910, the WTRU 102 may determine a priority level of the second PDU based on a reception time of the second PDU, a reception time of the first PDU, the first time threshold, and the second time threshold. At 912, the WTRU 102 may send a second PDU for the second flow using one of the plurality of resource configurations associated with the determined priority level.

[0509] In certain representative embodiments, the determination of the priority level of the second PDU may be based on the difference between the reception time of the second PDU and the reception time of the first PDU as described herein, the first time threshold, and the second time threshold. For example, if the difference is less than the first time threshold, the determined priority level may be the first priority level. The transmission of the second PDU of the second stream may use the first resource configuration associated with the first priority level. For example, the transmission of the first PDU and the transmission of the second PDU may use one (e.g., a single) transmission opportunity indicated by the first resource configuration.

[0510] In certain representative embodiments, if the difference is greater than the first time threshold and less than the second time threshold, the determined priority level may be the second priority level. For example, the transmission of the second PDU of the second stream may use a second resource configuration associated with the second priority level from among the plurality of resource configurations. For example, the transmission of the first PDU may use a first transmission opportunity indicated by the first resource configuration, and the transmission of the second PDU may use a second transmission opportunity indicated by the second resource configuration (e.g., after the first transmission opportunity and / or offset from the first transmission opportunity). For example, the second transmission opportunity may be offset in time from the first transmission opportunity.

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

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

[0513] In certain representative embodiments, the information included in the second ADU information is associated with the information included in the first ADU information.

[0514] Fig.10 is a process diagram illustrating an example of receiving multiple streams using priority levels. In certain representative embodiments, Fig.10The processes in may generally be implemented by a base station, such as the gNB 180. At 1002, the base station may send (e.g., to the WTRU 102) first information indicating a first time threshold, a second time threshold, and / or any one of a plurality of resource configurations associated with 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 for sending the second PDU (e.g., by the WTRU 102) 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 the base station) a relationship between a reception time of the second PDU (e.g., performed by the WTRU 102), a reception time of the first PDU (e.g., performed by the WTRU 102), the first time threshold, and the second time threshold.

[0515] Fig.11 is a process diagram illustrating an example process for adjusting resource configuration information to synchronize multiple streams. In certain representative embodiments, Fig.11 The process in may generally be implemented by a WTRU 102, such as WTRU 202. At 1102, the WTRU 102 may receive (e.g., from a base station) information indicating any of one or more first resource configurations, one or more second resource configurations, and / or a time threshold. At 1104, the WTRU 102 may send (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, if 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 the time threshold, the WTRU 102 may send (e.g., to a base station) adjustment information for one or more parameters of any of the first resource configuration and / or the second resource configuration.

[0516] In certain representative embodiments, adjustment information may be determined (eg, by the WTRU 102) to ensure synchronization between flows. For example, the adjustment information may indicate changes to one or more parameters (such as to meet the joint QoS of the flows as described herein).

[0517] In certain representative embodiments, the first resource configuration may include one or more CG configurations. In certain representative embodiments, the second resource configuration may include one or more SPS configurations.

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

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

[0520] Fig.12 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams. In certain representative embodiments, Fig.12 The process in may generally be implemented by a WTRU 102, such as WTRU 202. At 1202, the WTRU 102 may receive (e.g., from a base station) information 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 send (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, if 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 the time threshold, the WTRU 102 may switch to sending the one or more PDUs associated with the first flow using at least the third resource configuration at 1208.

[0521] In certain representative embodiments, switching at 1208 may be determined (eg, by the WTRU 102) to ensure synchronization between flows. For example, switching may be performed to satisfy a joint QoS of the flows as described herein.

[0522] In certain representative embodiments, the first resource configuration and / or the third resource configuration may include one or more CG configurations. In certain representative embodiments, the second resource configuration may include one or more SPS configurations.

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

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

[0525] Fig.13 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams. In certain representative embodiments, Fig.13The process in may generally be implemented by a WTRU 102 (such as 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 send (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, if 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 the time threshold, the WTRU 102 may send information indicating that the RTT between the first PDU of the one or more PDUs associated with the first flow and the second PDU of the one or more PDUs associated with the second flow is greater than the time threshold. At 1310, the WTRU 102 may receive the one or more PDUs associated with the second flow using at least the third resource configuration after 1308.

[0526] In certain representative embodiments, switching at 1208 may be determined (eg, by the WTRU 102) to ensure synchronization between flows. For example, switching may be performed to satisfy a joint QoS of the flows as described herein.

[0527] In certain representative embodiments, the first resource configuration and / or the third resource configuration may include one or more CG configurations. In certain representative embodiments, the second resource configuration may include one or more SPS configurations.

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

[0529] Fig.14 is a process diagram illustrating an example process for adjusting resource configuration information to synchronize multiple streams. In certain representative embodiments, Fig.14The processes in may generally be implemented by a base station, such as gNB 180. At 1402, the base station may send (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 configuration and / or the second resource configuration. For example, the adjustment information may be associated with 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 being greater than the time threshold.

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

[0531] In certain representative embodiments, adjustment information may be determined in order to ensure synchronization between streams as described herein.

[0532] Fig.15 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams. In certain representative embodiments, Fig.15 The processes in may generally be implemented by a base station, such as gNB 180. At 1502, the base station may send (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 a 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 a 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 the base station) 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 the time threshold.

[0533] In certain representative embodiments, adjustment information may be determined for any of the resource configurations described herein. For example, the adjustment information may ensure that the RTT meets certain requirements of the stream. For example, the adjustment information may modify one or more parameters so that synchronization between the streams is ensured as described herein.

[0534] Fig.16 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams. In certain representative embodiments, Fig.16 The processes in may generally be implemented by a base station, such as the gNB 180. At 1602, the base station may send (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 (e.g., from the WTRU 102) one or more PDUs associated with the second flow using at least the third resource configuration.

[0535] In some representative embodiments, the use of the third resource configuration can ensure that the synchronization of the streams is met. For example, the use of the third resource configuration can reduce the RTT between the first stream and the second stream.

[0536] Fig.17 is a process diagram illustrating an example process for maintaining joint quality of service (QoS) for multiple flows. In certain representative embodiments, Fig.17The process in may generally be implemented by a WTRU 102 (such as WTRU 202). At 1702, the WTRU 102 may receive (e.g., from a base station) information indicating any of 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 send (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 any of 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, if the change in QoS associated with the second flow does not satisfy the joint QoS, the WTRU 102 may change any of the first resource configuration and / or the second resource configuration. At 1712, the WTRU 102 may send (eg, 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 changed first resource configuration and / or the changed second resource configuration.

[0537] In certain representative embodiments, the first resource configuration may be a first configuration authorization configuration, and / or the second resource configuration may be a second configuration authorization configuration. For example, the size of the transmission opportunity associated with the first resource configuration may be greater than the size of the transmission opportunity associated with the second resource configuration. For example, the first resource configuration may include a first plurality of transmission opportunities having a first periodicity (e.g., information indicating the first plurality of transmission opportunities), and / or the second resource configuration may include a second plurality of transmission opportunities having a second periodicity less than the first periodicity.

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

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

[0540] In certain representative embodiments, a PDU of a first stream may include one or more ADUs of the first stream, and / or a PDU of a second stream may include one or more ADUs of the second stream.

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

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

[0543] Fig.18 is a process diagram illustrating another example process for maintaining joint quality of service (QoS) for multiple flows. In certain representative embodiments, Fig.18 The processes in may generally be implemented by a WTRU 102 (such as WTRU 202). At 1802, the WTRU 102 may receive (e.g., from a base station) information indicating any of 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 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 send (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 any of 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 send (e.g., to a base station) information indicating a change (e.g., adjustment) to either the first resource configuration and / or the second resource configuration.

[0544] In certain representative embodiments, the WTRU 102 may receive (e.g., from a base station) adjustment information associated with any of 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 any of the resource configurations. For example, the adjustment information may ensure that the flow meets the joint QoS.

[0545] In certain representative embodiments, the WTRU 102 may send (eg, to a base station) a third set of PDUs and a fourth set of PDUs using either the changed first resource configuration and / or the changed second resource configuration.

[0546] In certain representative embodiments, the first resource configuration may be a first configuration authorization configuration, and / or the second resource configuration may be a second configuration authorization configuration. For example, the size of the transmission opportunity associated with the first resource configuration may be greater than the size of the transmission opportunity associated with the second resource configuration. For example, the first resource configuration may include a first plurality of transmission opportunities having a first periodicity, and / or the second resource configuration may include a second plurality of transmission opportunities having a second periodicity less than the first periodicity.

[0547] In certain representative embodiments, any of the first resource configuration and / or the second resource configuration is associated with the first flow and / or the second flow.

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

[0549] In certain representative embodiments, a PDU of a first stream may include one or more ADUs of the first stream, and / or a PDU of a second stream may include one or more ADUs of the second stream.

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

[0551] 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 multi-flow synchronization.

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

[0553] Fig.19 is a process diagram illustrating another example process for synchronizing multiple streams. In certain representative embodiments, Fig.19The processes in may generally be implemented by a WTRU 102 (such as WTRU 202). At 1902, the WTRU 102 may send (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 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 send (e.g., to a base station) the one or more PDUs of the first flow using the first resource configuration. At 1910, if the last PDU of the second flow is received (1) after a first time threshold has passed since the associated PDU of the first flow was received and (2) before a second time threshold has passed since the associated PDU of the first flow was received, the WTRU 102 may use a second resource configuration to send (e.g., to a base station) at least the last PDU of the second flow.

[0554] Fig. 20 is a process diagram illustrating another example for sending multiple streams using priority levels. In certain representative embodiments, Fig. 20 The process in may generally be implemented by a WTRU 102 (such as TRU 202). At 2002, the WTRU 102 may receive (e.g., from a base station) reception information indicating a plurality of resource configurations associated with a plurality of priority levels. At 2004, the WTRU 102 may receive (e.g., from another WTRU 102 and / or a higher layer) 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 send (e.g., to a base station) the one or more PDUs of the first flow using a first resource configuration of the plurality of resource configurations. At 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, when the difference in reception time satisfies the first threshold, the priority level may be the first priority level. For example, when the difference in reception time satisfies the second threshold but does not satisfy the first threshold, the priority level may be the second priority level. For example, when the difference in reception time does not satisfy the first threshold and does not satisfy the second threshold, the priority level may be a third priority level. At 2010, the WTRU 102 may send (e.g., to a base station) at least one of the PDUs of the second flow using a second resource configuration associated with the determined priority level from among the plurality of resource configurations.

[0555] Fig.21 is a process diagram illustrating another example process for adjusting resource configuration information to synchronize multiple streams. In certain representative embodiments, Fig.21 The processes in may generally be implemented by a WTRU 102, such as WTRU 202. At 2102, the WTRU 102 may receive (e.g., from a base station) information indicating either a first resource configuration and a second resource configuration. At 2104, the WTRU 102 may send (e.g., to a base station) one or more PDUs associated with a 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 a second flow using the second resource configuration. At 2108, if the RTT between a first PDU associated with the first flow and a second PDU associated with the second flow is greater than a time threshold, the WTRU 102 may send (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.

[0556] Fig. 22 is a process diagram illustrating an example process for maintaining joint quality of service (QoS) for multiple flows. In certain representative embodiments, Fig. 22 The processes in may generally be implemented by a WTRU 102, such as WTRU 202. At 2202, the WTRU 102 may receive (e.g., from a base station) information indicating any of 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 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 send (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 any of 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, if the change in QoS associated with the first flow and / or the second flow does not satisfy the joint QoS, the WTRU 102 may change one or more parameters of either the first resource configuration and / or the second resource configuration. In another example, the WTRU 102 may select or receive another (e.g., third) resource configuration. At 2212, the WTRU 102 may send (e.g., to a base station) a third set of PDUs and a fourth set of PDUs for the first flow using either the changed first resource configuration and / or the changed second resource configuration. In another example, the third set of PDUs and / or the fourth set of PDUs may be sent using another (e.g., third resource configuration).

[0557] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. If the second PDU is received before the first duration has elapsed relative to receiving the first PDU, the WTRU 102 may transmit the second PDU using the second default forwarding configuration.

[0558] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. If the second PDU is received after the first duration has elapsed relative to receiving the first PDU and before the second duration has elapsed relative to receiving the first PDU, the WTRU 102 may transmit the second PDU using one of the plurality of forwarding configurations associated with a priority of the second flow that is higher than the priority associated with the second default forwarding configuration.

[0559] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. If the second PDU is received after a first duration has elapsed relative to receiving the first PDU and after a second duration has elapsed relative to 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 forwarding 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 forwarding configurations.

[0560] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. If the second PDU is received after a first duration has elapsed relative to receiving the first PDU and after a second duration has elapsed relative to receiving the first PDU, the WTRU may transmit information indicating a reception status associated with the second PDU. Thereafter, the WTRU 102 may receive information indicating that the second PDU is discarded.

[0561] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. If (1) a last PDU of the first ADU is received before a first duration has elapsed relative to the receipt of the first PDU of the first ADU and / or (2) a second PDU of the second ADU is received before a first duration has elapsed relative to the receipt of the first PDU of the first ADU, the WTRU may transmit the last PDU of the first ADU using the first default forwarding configuration and transmit the second PDU of the second ADU using the second default forwarding configuration.

[0562] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. The WTRU 102 may receive a third PDU corresponding to a first ADU of the first flow. If (1) the third PDU of the first ADU is received after a first duration has elapsed relative to the first PDU received the first ADU and before a second duration has elapsed relative to the first PDU received the first ADU and / or (2) the second PDU of the second ADU is received after a first duration has elapsed relative to the first PDU received the first ADU and before a second duration has elapsed relative to the first PDU received the first ADU, the WTRU 102 may transmit the third PDU using one of the plurality of forwarding configurations associated with a priority higher than the priority associated with the first default forwarding configuration and transmit the second PDU using the second default forwarding configuration.

[0563] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. If the second PDU is received after the first duration and the second duration have elapsed relative to receiving the first PDU and before the third duration has elapsed relative to receiving the first PDU, the WTRU 102 may transmit the second PDU using one of the plurality of forwarding configurations associated with a priority of the second flow that is higher than the priority associated with the second default forwarding configuration.

[0564] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. If the second PDU is received after the first duration and the second duration have elapsed relative to receiving the first PDU and before the third duration has elapsed relative to 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 forwarding 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 forwarding configurations.

[0565] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. If the second PDU is received after the first duration, the second duration, and the third duration have elapsed relative to receiving the first PDU and before the third duration has elapsed relative to 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 the plurality of forwarding 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 forwarding configurations.

[0566] In certain representative embodiments, the WTRU 102 may receive information indicating a first duration and a second duration and information indicating a plurality of forwarding configurations including a first default forwarding configuration associated with a first flow and a second default forwarding 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 forwarding configuration. The WTRU 102 may receive a second PDU corresponding to the second flow. If the second PDU is received after the first duration, the second duration, and the third duration have elapsed relative to receiving the first PDU and before the third duration has elapsed relative to receiving the first PDU, the WTRU 102 may transmit information indicating a reception status associated with the second PDU. Thereafter, the WTRU 102 may receive information indicating that the second PDU is discarded.

[0567] In certain representative embodiments, the WTRU 102 may receive information indicating a plurality of resource configurations, the plurality of resource configurations including a first resource configuration associated with a first stream and a second resource configuration associated with a second stream. The WTRU 102 may communicate (e.g., send or receive) a first protocol data unit (PDU) corresponding to the first stream using the first resource configuration. The WTRU 102 may communicate (e.g., send or receive) a second PDU corresponding to the second stream using the second resource configuration. If the round trip time (RTT) associated with either the first stream and / or the second stream is higher than a threshold, the WTRU 102 may determine a change to either the first resource configuration and / or the second resource configuration to reduce the RTT below the threshold. Thereafter, the WTRU 102 may use either the changed first resource configuration and / or the second resource configuration to send and / or receive one or more PDUs of either the first stream and / or the second stream. In other examples, the WTRU 102 may use QoS requirements in conjunction with or instead of RTT.

[0568] In certain representative embodiments, the WTRU 102 may receive information indicating a plurality of resource configurations, the plurality of resource configurations including a first resource configuration associated with a first stream and a second resource configuration associated with a second stream. The WTRU 102 may communicate (e.g., send or receive) a first protocol data unit (PDU) corresponding to the first stream using the first resource configuration. The WTRU 102 may communicate (e.g., send or receive) a second PDU corresponding to the second stream using the second resource configuration. If the round trip time (RTT) associated with either the first stream and / or the second stream is below a threshold, the WTRU may determine a change to either the first resource configuration and / or the second resource configuration to increase the RTT above the threshold. Thereafter, the WTRU may use either the changed first resource configuration and / or the second resource configuration to send and / or receive one or more PDUs of either the first stream and / or the second stream. In other examples, the WTRU 102 may use QoS requirements in conjunction with or instead of the RTT.

[0569] In certain embodiments and examples herein, processes are described that can be performed for multi-stream synchronization on a per-PDU basis and / or a per-ADU basis. In other examples, multi-stream synchronization can be performed on a per-PDU set basis.

[0570] in conclusion

[0571] Although features and elements are provided above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. The present disclosure is not limited to the specific embodiments described in this patent application, which are intended to be examples of various aspects. Many modifications and variations can be made without departing from the essence and scope of the present invention, as they will be obvious to those skilled in the art. Unless explicitly provided as such, any element, action or description used in the present application specification should not be understood as being essential or necessary to the present invention. According to the foregoing description, in addition to those listed herein, functionally equivalent methods and devices within the scope of the present disclosure will be obvious to those skilled in the art. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only to the terms of the appended claims and the full range of equivalent forms of such entitled claims. It should be understood that the present disclosure is not limited to a specific method or system.

[0572] For simplicity, the foregoing embodiments are discussed with respect to terminology and structure of infrared capable devices (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but may be applied to other systems using other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0573] It should also be understood that the terms used herein are used only for the purpose of describing specific embodiments and are not intended to be limiting. As used herein, the term "video" or the term "image" may mean any of a snapshot, a single image, and / or a plurality of images displayed on a time basis. For example, when referred to herein, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a plurality of embodiments of the WTRU; (iii) a wireless and / or wired (e.g., tetherable) device configured with (in particular) some or all of the structure and functionality of the WTRU; (iii) a wireless and / or wired device configured with less than all of the structure and functionality of the WTRU; or (iv), etc. This document is relative to Figures 1A to 1D Details of an exemplary WTRU are provided that may represent any WTRU described herein. As another example, various disclosed embodiments herein are described above and below as utilizing a head mounted display. Those skilled in the art will recognize that devices other than head mounted displays may be utilized, and some or all of the present disclosure and 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 adapted reality experience.

[0574] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via a wired or wireless connection) 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 built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0575] Variations of the methods, devices, and systems provided above are possible without departing from the scope of the present invention. In view of the various embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be considered to limit the scope of the following claims. For example, the embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery, etc.) that provides any suitable voltage.

[0576] In addition, in the embodiments provided above, processing platforms, computing systems, controllers and other devices including processors are indicated. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to the symbolic representations of actions and operations or instructions may be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as being "executed", "computer executed" or "CPU executed".

[0577] Those of ordinary skill in the art will appreciate that the actions and symbolic representations of operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits, which may result in the ultimate transformation of electrical signals or reduction of electrical signals and the retention of data bits at memory locations in the memory system, thereby reconfiguring or otherwise changing the operation of the CPU and performing other processing of signals. The memory location that holds the data bits is a physical location that has specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may also support the provided methods.

[0578] The data bits may also be maintained on computer-readable media, 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 the CPU. The computer-readable media may include cooperating or interconnected computer-readable media that reside solely on the processing system or distributed across multiple interconnected processing systems that may be local or remote relative to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories, and other platforms and memories may also support the provided methods.

[0579] In an exemplary 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 unit, a network element, and / or any other computing device.

[0580] There is little difference between hardware implementation and software implementation of various aspects of the system. The use of hardware or software is usually (but not always, because in some contexts, the choice between hardware and software may become important) a design choice that represents a trade-off between cost and efficiency. There may be various media (e.g., hardware, software, and / or firmware) that can implement the processes and / or systems and / or other technologies described herein, and the preferred media may vary with the context of the deployment process and / or system and / or other technologies. For example, if the implementer determines that speed and accuracy are most important, the implementer may choose a media that is primarily hardware and / or firmware. If flexibility is most important, the implementer may choose a specific implementation that is primarily software. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0581] The above detailed description has listed various embodiments of the device and / or process by using block diagrams, flow charts and / or examples. In the case where such block diagrams, flow charts and / or examples include one or more functions and / or operations, it should be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware or almost any combination thereof. In an embodiment, several parts of the subject matter described herein can be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs) and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be equivalently implemented in integrated circuits as a whole or in part as one or more computer programs running on one or more computers (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware or almost any combination thereof, and according to the present disclosure, designing circuits and / or writing software and / or firmware codes will be completely within the technical scope of those skilled in the art. Furthermore, those skilled in the art will appreciate that the mechanisms of the subject matter described herein can be distributed as a program product in a variety of forms, and that the illustrative embodiments of the subject matter described herein apply regardless of the specific type of signal-bearing medium used to actually perform the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable type media (such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memory, etc.); and transmission type media (such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.)).

[0582] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner set forth herein, and thereafter use engineering practices 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 can be integrated into a data processing system via a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system generally may include one or more of the following: a system unit housing; a video display device; a memory, such as a volatile memory and a non-volatile memory; a processor, such as a microprocessor and a digital signal processor; a computing entity, such as an operating system, a driver, a graphical user interface, and an application; one or more interactive devices, such as a touch pad or a screen; and / or a control system, including a feedback loop and a control motor (e.g., a feedback for sensing position and / or velocity, a control motor for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented using any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0583] The subject matter described herein sometimes shows different parts included in or connected to different other parts.It should be understood that such depicted architectures are only examples, and in fact many other architectures that achieve the same function can be realized.In a conceptual sense, any arrangement of parts that achieve the same function is effectively "associated" so that the desired function can be achieved.Therefore, any two parts that are combined to achieve a specific function in this article can be regarded as "associated" with each other so that the desired function can be achieved, regardless of the architecture or intermediate parts.Similarly, any two parts so associated can also be regarded as "operably connected" or "operably coupled" to each other to achieve the desired function, and any two parts that can be so associated can also be regarded as "operably coupleable" to each other to achieve the desired function.Specific examples of operable coupling include but are not limited to parts that can physically cooperate and / or physically interact and / or parts that can wirelessly interact and / or wirelessly interact and / or parts that can logically interact and / or parts that can logically interact.

[0584] With respect to substantially any plural and / or singular terms used herein, those skilled in the art may translate from the plural to the singular and / or from the singular to the plural as appropriate, as appropriate to the context and / or application. For clarity, various singular / plural arrangements may be explicitly listed herein.

[0585] It will be understood by those skilled in the art that, in general, the terms used herein, and particularly in the appended claims (e.g., the bodies of the appended claims), are generally intended to be "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", the term "comprising" should be interpreted as "including but not limited to", etc.). It will also be understood by those skilled in the art that if a specific number of an introduced claim recitation is intended, such intent will be explicitly stated in the claim, and in the absence of such a recitation, there is no such intent. For example, where only one item is intended, the term "single" or similar language may be used. To aid understanding, the following appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed as implying that any particular claim including such introduced claim recitations is limited to an embodiment including only one such recitation by the indefinite article "a" or "an" to introduce the claim recitation. This is true even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "a kind" (e.g., "a" and / or "a kind" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, one skilled in the art will recognize that such recitation should be interpreted as meaning at least the stated number (e.g., a bare recitation of "two recitations" without other modifiers means at least two recitations, or two or more recitations). In addition, in those instances where a convention similar to "at least one of A, B, and C, etc." is used, generally speaking, the meaning of such construction is that one skilled in the art will understand the convention (e.g., "a system having at least one of A, B, and C" will include, but is not limited to, a system having A alone, B alone, C alone, A and B simultaneously, A and C simultaneously, B and C simultaneously, and / or A, B, and C simultaneously, etc.). In those instances where a convention similar to "at least one of A, B, or C, etc." is used, generally speaking, the meaning of such construction is that one skilled in the art will understand the convention (e.g., "a system having at least one of A, B, or C" will include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). One skilled in the art will also understand that, in fact, any discrete words and / or phrases 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, any of the terms, or both of the terms.For example, the phrase "A or B" will 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 listing of multiple items and / or multiple categories of items is intended to include "any of," "any combination," "any multiples," and / or "any combination of multiples" of the items and / or categories of items, either alone 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 "quantity" is intended to include any quantity, including zero. And, as used herein, the term "plurality" is intended to be synonymous with "multiple."

[0586] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also described in terms of any individual member or subgroup of members of the Markush group.

[0587] As will be understood by those skilled in the art, for any and all purposes (such as for providing a written description), all ranges disclosed herein also encompass any and all possible subranges and combinations of their subranges. Any listed range can be easily identified as fully describing and enabling the same range to be divided into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein can be easily divided into a lower third, a middle third, and an upper third, etc. As will be understood by those skilled in the art, all languages ​​such as "up to", "at least", "greater than", "less than", etc. include the cited numbers and refer to ranges that can subsequently be divided into subranges as described above. Finally, as will be understood by those skilled in the art, ranges include each individual number. Thus, for example, a group having 1 to 3 units refers to a group having 1, 2, or 3 units. Similarly, a group having 1 to 5 units refers to a group having 1, 2, 3, 4, or 5 units, etc.

[0588] Furthermore, the claims should not be read as limited to the order or elements presented unless otherwise stated. Furthermore, the use of the term "means for..." in any claim is intended to invoke 35 U.S.C. § 112, 6 or means-plus-function claim format, and any claim without the term "means for..." is not intended to be so.

Claims

1. A method implemented by a wireless transmit / receive unit WTRU, the method comprising: receiving configuration information associated with an uplink (UL) service, the configuration information comprising information indicating a flow set and a timer amount; determining, for each flow in the set of flows, information including arrival times and associated characteristics of one or more sets of protocol data units (PDUs) associated with the corresponding flow; as well as Based on a timer associated with a timer amount that is no longer running for at least one flow in the flow set, auxiliary information is transmitted to a network entity, wherein the auxiliary information includes UL service information of the at least one flow indicating an identifier of the one or more PDU sets, the determined arrival time, and associated characteristics of the one or more PDU sets.

2. The method according to claim 1, further comprising: A plurality of PDUs included in one or more PDU sets are received from an application executed by the WTRU.

3. The method according to claim 2, further comprising: The plurality of received PDUs are transmitted as UL traffic, wherein at least one PDU of a corresponding set of the one or more PDU sets includes information identifying a corresponding flow.

4. The method according to claim 1, wherein: The information indicating the flow set includes a set of identifiers of the flows.

5. The method according to claim 1, wherein: The associated characteristics include any of an amount or range of jitter associated with one or more PDU sets of the corresponding flow, and / or a periodicity associated with one or more PDU sets of the corresponding flow.

6. The method according to claim 1, wherein: The one or more PDU sets are associated with the flow set.

7. The method according to claim 1, wherein: The PDU set includes a plurality of application data units ADUs, and the plurality of ADUs are associated with the flow set.

8. The method according to claim 1, further comprising: Based on headers of PDUs of a corresponding set of the one or more PDU sets, it is determined that the corresponding set is associated with a corresponding flow.

9. The method according to claim 1, wherein: The configuration information associated with the UL service is received via Radio Resource Control (RRC) signaling.

10. The method according to claim 1, wherein: The assistance information associated with the application is transmitted via Radio Resource Control (RRC) signaling.

11. The method according to claim 1, further comprising: After transmitting the auxiliary information, resource configuration information associated with the set of flows is received.

12. A wireless transmit / receive unit WTRU, comprising: The processor, memory and transceiver are configured to: receiving configuration information associated with an uplink (UL) service, the configuration information comprising information indicating a flow set and a timer amount, determining, for each flow in the set of flows, information including arrival times and associated characteristics of one or more sets of protocol data units (PDUs) associated with the respective flow, and Based on a timer associated with a timer amount that is no longer running for at least one flow in the flow set, auxiliary information is transmitted to a network entity, wherein the auxiliary information includes UL service information of the at least one flow indicating an identifier of the one or more PDU sets, the determined arrival time, and associated characteristics of the one or more PDU sets.

13. The WTRU of claim 12, wherein: The processor, memory and transceiver are configured to: A plurality of PDUs included in one or more PDU sets are received from an application executed by the WTRU.

14. The WTRU of claim 13 wherein: The processor, memory and transceiver are configured to: The plurality of received PDUs are transmitted as UL traffic, wherein at least one PDU of a corresponding set of the one or more PDU sets includes information identifying a corresponding flow.

15. The WTRU of claim 12 wherein: The information indicating the flow set includes a set of identifiers of the flows.

16. The WTRU of claim 12 wherein: The associated characteristics include any of an amount or range of jitter associated with one or more PDU sets of the corresponding flow, and / or a periodicity associated with one or more PDU sets of the corresponding flow.

17. The WTRU of claim 12 wherein: The one or more PDU sets are associated with the flow set.

18. The WTRU of claim 12 wherein: A plurality of application data units ADUs include the one or more PDU sets, and the plurality of ADUs are associated with the flow set.

19. The WTRU of claim 12 wherein: The processor, memory and transceiver are configured to: Based on headers of PDUs of a corresponding set of the one or more PDU sets, it is determined that the corresponding set is associated with a corresponding flow.

20. The WTRU of claim 12 wherein: Configuration information associated with the UL service is received via radio resource control (RRC) signaling.

21. The WTRU of claim 12 wherein: The assistance information associated with the application is transmitted via Radio Resource Control (RRC) signaling.

22. The WTRU of claim 12 wherein: The processor, memory and transceiver are configured to: After transmitting the auxiliary information, resource configuration information associated with the set of flows is received.

Images